<![CDATA[Interface Names Cisco Devices]]>Hi all,

I'm in the final testing phase of some products for network management and netxms looks great 😉

But I have a problem with a Cisco Catalyst 6506. The Interface list looks like:

"ID" "Name" "Class" "Status"
"364" "long haul fiber gigabit ethernet" "interface" "normal"
"1624" "short wave fiber gigabit ethernet" "interface" "normal"
"1633" 10/100 utp ethernet (cat 3/5)" "interface" "normal"
"1634" 10/100 utp ethernet (cat 3/5)" "interface" "normal"
"1635" 10/100 utp ethernet (cat 3/5)" "interface" "normal"
"1636" 10/100 utp ethernet (cat 3/5)" "interface" "normal"
"1637" 10/100 utp ethernet (cat 3/5)" "interface" "normal"
"1638" 10/100 utp ethernet (cat 3/5)" "interface" "normal"

So I can not find which interface has a problem - there is no relation to the real port names.

But the Mib-Browser shows the information needed under .1.3.6.1.2.1.31.1.1.1.1 (ifname). When I walk the C6506 i receive the correct interface names (for example 4/1; 5/2).

Is it possible to get a correct list of my interfaces installed?

Version 0.2.21

Thanks in advance,

Greetings Tom

]]>https://forum.netxms.org/topic/340/interface-names-cisco-devicesRSS for NodeFri, 13 Nov 2026 14:48:53 GMTFri, 16 May 2008 07:53:49 GMT60<![CDATA[Reply to Interface Names Cisco Devices on Thu, 26 Jun 2008 08:19:13 GMT]]>I have implemented usage of ifXTable for interface names polling in version 0.2.22.

Best regards,
Victor

]]>https://forum.netxms.org/post/1949https://forum.netxms.org/post/1949Thu, 26 Jun 2008 08:19:13 GMT<![CDATA[Reply to Interface Names Cisco Devices on Fri, 16 May 2008 12:49:24 GMT]]>very nice, thank you!

Best regards,
Tom

]]>https://forum.netxms.org/post/1653https://forum.netxms.org/post/1653Fri, 16 May 2008 12:49:24 GMT<![CDATA[Reply to Interface Names Cisco Devices on Fri, 16 May 2008 11:33:21 GMT]]>You can't change this behaviour without changing the server code. I'll try to create a patch and send you for testing - I don't have access to big Cisco switches unfortunately.

Best regards,
Victor

]]>https://forum.netxms.org/post/1650https://forum.netxms.org/post/1650Fri, 16 May 2008 11:33:21 GMT<![CDATA[Reply to Interface Names Cisco Devices on Fri, 16 May 2008 10:57:25 GMT]]>Hi Victor,

thank you for the quick reply. Nice to hear that you will work on it. So I can use the workaround with descriptions for the important devices and wait for the update. Or is there a chance to modify the OID for a single device (even at the database?)?
If I can help you with some testing I would like to do so 🙂

Greetings Tom

]]>https://forum.netxms.org/post/1648https://forum.netxms.org/post/1648Fri, 16 May 2008 10:57:25 GMT<![CDATA[Reply to Interface Names Cisco Devices on Fri, 16 May 2008 10:18:29 GMT]]>Hello!

Looks like some Cisco switches need special handling for interface names. NetXMS server reads interface description from .1.3.6.1.2.1.2.2.1.2, which is standard interface MIB supported by all SNMP devices. As I see Catalyst 6500 returns description of the interface here, not the name as most devices do. In the next version I will add check for extended information under ifXTable (.1.3.6.1.2.1.31.1.1) and NetXMS server will use it when available. This should solve Cat 6500 problem (and possible for some other devices too).

Best regards,
Victor

]]>https://forum.netxms.org/post/1645https://forum.netxms.org/post/1645Fri, 16 May 2008 10:18:29 GMT<![CDATA[Reply to Interface Names Cisco Devices on Fri, 16 May 2008 09:59:28 GMT]]>ok, checking the release notes is always good 🙂

I changed the useinterfaceAliases Parameter to "1" and now I see the descriptions on the port when they was set.

But all ports without a description looks like the above list.

I could work around this now with using more descriptions like "5/1 Servername", but using another mib location would be nice.

]]>https://forum.netxms.org/post/1644https://forum.netxms.org/post/1644Fri, 16 May 2008 09:59:28 GMT