OcNOS Interfaces: Sensors Numbering
Hi Observium Team,
we noticed that when monitoring IPInfusion/OcNOS Routers (at least on Ufispace s9510-s28dc) the Interface Sensors naming is incorrect, some items are offset by 1, and others are not showing up.
For example, we have an interface with ifDescr="xe4" which is detected correctly in the ports/basic tab (see ports.png) - but in the Sensors tab it is detected as xe5 (see sensors.png - xe5 has no treansciever and is Admin Down on this device).
Other ports are not showing up in the Ports/Sensors section, but they do appear in Health/dBm (see dbm.png).
IPInfusion is starting the interface enumeration in ifDescr with 0 (ce0 is the first interface), and in the CMM-CHASSIS-MIB the interfaces are indexed by CmmTransIndex starting with 1.
For example, xe4 receive power is at: .1.3.6.1.4.1.36673.100.1.2.3.1.22.1.5.1 (notice cmmTransIndex = 5)
ce0 receive power: .1.3.6.1.4.1.36673.100.1.2.3.1.22.1.1.1 (notice cmmTransIndex = 1)
Is there any option to fix this?
Thank you in advance, kind regards,
Nicolas
Hi Nikolas,
need to check how interfaces associated with sensors.
But required full snmpdump from your device. Please read this doc and send me (out of list) dump from this device: https://docs.observium.org/developing/add_device/#snmp-dump
You also can send it me in our Discord channel: @landy https://discord.gg/GjpNXKWm8W
Nicolas Korten via observium wrote on 17.12.2025 08:42:
Hi Observium Team,
we noticed that when monitoring IPInfusion/OcNOS Routers (at least on Ufispace s9510-s28dc) the Interface Sensors naming is incorrect, some items are offset by 1, and others are not showing up.
For example, we have an interface with ifDescr="xe4" which is detected correctly in the ports/basic tab (see ports.png) - but in the Sensors tab it is detected as xe5 (see sensors.png - xe5 has no treansciever and is Admin Down on this device).
Other ports are not showing up in the Ports/Sensors section, but they do appear in Health/dBm (see dbm.png).
IPInfusion is starting the interface enumeration in ifDescr with 0 (ce0 is the first interface), and in the CMM-CHASSIS-MIB the interfaces are indexed by CmmTransIndex starting with 1.
For example, xe4 receive power is at: .1.3.6.1.4.1.36673.100.1.2.3.1.22.1.5.1 (notice cmmTransIndex = 5)
ce0 receive power: .1.3.6.1.4.1.36673.100.1.2.3.1.22.1.1.1 (notice cmmTransIndex = 1)
Is there any option to fix this?
Thank you in advance, kind regards,
Nicolas
observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
Thank you Mike, I sent the walk output via private email.
Kind regards,
Nicolas
Hi Nikolas,
thanks, I'm looking for fixes..
Nicolas Korten wrote on 09.01.2026 10:04:
Thank you Mike, I sent the walk output via private email.
Kind regards,
Nicolas
It's should be fixed for such Hardware and os version since revision 14529. Not sure how that will be correct for other hardware. This OS not have simple index (or identifier) in this table (DDM sensors) for correctly associate sensors to ports.
Nicolas Korten via observium wrote on 17.12.2025 08:42:
Hi Observium Team,
we noticed that when monitoring IPInfusion/OcNOS Routers (at least on Ufispace s9510-s28dc) the Interface Sensors naming is incorrect, some items are offset by 1, and others are not showing up.
For example, we have an interface with ifDescr="xe4" which is detected correctly in the ports/basic tab (see ports.png) - but in the Sensors tab it is detected as xe5 (see sensors.png - xe5 has no treansciever and is Admin Down on this device).
Other ports are not showing up in the Ports/Sensors section, but they do appear in Health/dBm (see dbm.png).
IPInfusion is starting the interface enumeration in ifDescr with 0 (ce0 is the first interface), and in the CMM-CHASSIS-MIB the interfaces are indexed by CmmTransIndex starting with 1.
For example, xe4 receive power is at: .1.3.6.1.4.1.36673.100.1.2.3.1.22.1.5.1 (notice cmmTransIndex = 5)
ce0 receive power: .1.3.6.1.4.1.36673.100.1.2.3.1.22.1.1.1 (notice cmmTransIndex = 1)
Is there any option to fix this?
Thank you in advance, kind regards,
Nicolas
observium mailing list -- observium@lists.observium.org To unsubscribe send an email to observium-leave@lists.observium.org
Hi Mike, thank you very much.
We did the upgrade to 26.1.14535 and I can confirm the sensors are working as expected now. Good job, thank you! Fortunately we do have support with IPInfusion, I asked your question about how to correlate the DDM table with the ports. If something useful comes across, I'll post here.
Thank you, kind regards,
Nicolas
Hi Again, I got a reply from IPInfusion support:
EEPROM table uses the TransIndex. It is a unique number associated with a port and always starts with “1“. There is another object in the same table “cmmTransFrontPanelPortNumber“ which can be mapped.
I checked on a few OcNOS devices we have, and I can grab the cmmTransFrontPanelPortNumber from the Interface name with this regex: /(xe|ce|cd)(?'cmmTransFrontPanelPortNumber'\d*)/
Thank you, kind regards,
Nicolas
________________________________________ From: Nicolas Korten Sent: Monday, January 12, 2026 9:43 AM To: Mike Stupalov; Observium Subject: Re: [Observium] OcNOS Interfaces: Sensors Numbering
Hi Mike, thank you very much.
We did the upgrade to 26.1.14535 and I can confirm the sensors are working as expected now. Good job, thank you! Fortunately we do have support with IPInfusion, I asked your question about how to correlate the DDM table with the ports. If something useful comes across, I'll post here.
Thank you, kind regards,
Nicolas
-- Nicolas Korten Dipl.-Ing. Systemtechnik und Dienste/EDV
komro GmbH
Am Innreit 2 DE-83022 Rosenheim
Telefon: +49 8031 365 7913 Telefax: +49 8031 365 7699
Mail: korten@komro.net / http://www.komro.net __________________________________________________________________________________________________________ Geschäftsführer: Dipl. Ing. Gert Vorwalder Vorsitz im Aufsichtsrat: Oberbürgermeister Andreas März Sitz der Gesellschaft: Rosenheim Registergericht: Traunstein, HRB-Nr. 10689 USt.-IdNr.: DE 188814299
Hinweise zur Verarbeitung Ihrer personenbezogenen Daten gem Art. 13 DSGVO: Verantwortlich für die Verarbeitung Ihrer personenbezogenen Daten im Rahmen des vorliegenden Kontakts ist die komro GmbH Weitere Informationen zur Verarbeitung Ihrer Daten, insbesondere zu den Ihnen zustehenden Rechten, können Sie unserer Homepage unter https://www.komro.net/datenschutz entnehmen oder auf jedem anderen Wege unter den o.g. Kontaktdaten bei uns erfragen.
participants (2)
-
Mike Stupalov -
Nicolas Korten