Cisco Catalyst 9400 not showing the operating system version

We noticed that our Cisco Catalyst 9400 devices do not show a version number for operating system:

Operating System = Cisco IOS

LibreNMS does show this:

Cisco IOS Software [Fuji], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 16.9.2, RELEASE SOFTWARE (fc4) Technical Support: http://www.cisco.com/techsupport Copyright © 1986-2018 by Cisco Systems, Inc. Compiled Mon 05-Nov-18 19:32 by mcpre

Does anyone else have this issue? Do we need to check a different OID?

Thanks,

Tristan

could u make an snmp walk dump, i think if some1 whants to add it it needs to look at some OID’s

Same on 9500 and 9200s - it was on my list to have a look at. It’s the same code across all the 9x family, albeit a cut-down version on the 9200s, so should be a simple fix once we find the cuplrit.

This looks the best place to pull it from. On a 9200:

 /usr/bin/snmpbulkwalk -v2c -c public -OsqnU -M /opt/librenms/mibs device .1.3.6.1.4.1.9.9.249.1.1.1.1

    .1.3.6.1.4.1.9.9.249.1.1.1.1.2.1000 "CAT9K_LITE_IOSXE"
    .1.3.6.1.4.1.9.9.249.1.1.1.1.3.1000 "CAT9K_LITE_IOSXE"
    .1.3.6.1.4.1.9.9.249.1.1.1.1.4.1000 "IP|SSH|3DES"
    .1.3.6.1.4.1.9.9.249.1.1.1.1.5.1000 "16.9.2"
    .1.3.6.1.4.1.9.9.249.1.1.1.1.6.1000 1
    .1.3.6.1.4.1.9.9.249.1.1.1.1.7.1000 "Cisco IOS Software [Fuji], Catalyst L3 Switch Software (CAT9K_LITE_IOSXE), Version 16.9.2, RELEASE SOFTWARE (fc4)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2018 by Cisco Systems, Inc.
    Compiled Mon 05-Nov-18 18:14 by mcpre"

And a VSS (stackwise-virtual) pair of 9500s:

/usr/bin/snmpbulkwalk -v2c -c public -OsqnU -M /opt/librenms/mibs device .1.3.6.1.4.1.9.9.249.1.1.1.1

    .1.3.6.1.4.1.9.9.249.1.1.1.1.2.1000 "CAT9K_IOSXE"
    .1.3.6.1.4.1.9.9.249.1.1.1.1.2.2000 "CAT9K_IOSXE"
    .1.3.6.1.4.1.9.9.249.1.1.1.1.3.1000 "CAT9K_IOSXE"
    .1.3.6.1.4.1.9.9.249.1.1.1.1.3.2000 "CAT9K_IOSXE"
    .1.3.6.1.4.1.9.9.249.1.1.1.1.4.1000 "IP|SLA|IPv6|IS-IS|FIREWALL|PLUS|QoS|HA|NAT|MPLS|VPN|LEGACY PROTOCOLS|3DES|SSH|APPN|IPSEC"
    .1.3.6.1.4.1.9.9.249.1.1.1.1.4.2000 "IP|SLA|IPv6|IS-IS|FIREWALL|PLUS|QoS|HA|NAT|MPLS|VPN|LEGACY PROTOCOLS|3DES|SSH|APPN|IPSEC"
    .1.3.6.1.4.1.9.9.249.1.1.1.1.5.1000 "16.11.1"
    .1.3.6.1.4.1.9.9.249.1.1.1.1.5.2000 "16.11.1"
    .1.3.6.1.4.1.9.9.249.1.1.1.1.6.1000 1
    .1.3.6.1.4.1.9.9.249.1.1.1.1.6.2000 1
    .1.3.6.1.4.1.9.9.249.1.1.1.1.7.1000 "Cisco IOS Software [Gibraltar], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 16.11.1, RELEASE SOFTWARE (fc3)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2019 by Cisco Systems, Inc.
    Compiled Thu 28-Mar-19 09:42 by mcpre"
    .1.3.6.1.4.1.9.9.249.1.1.1.1.7.2000 "Cisco IOS Software [Gibraltar], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 16.11.1, RELEASE SOFTWARE (fc3)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2019 by Cisco Systems, Inc.
    Compiled Thu 28-Mar-19 09:42 by mcpre"

Here is the same output from a Cisco C9300:

$ snmpwalk -c public -v2c -OsqnU -M /opt/librenms/mibs 192.168.2.46 .1.3.6.1.4.1.9.9.249.1.1.1.1
.1.3.6.1.4.1.9.9.249.1.1.1.1.2.3000 “CAT9K_IOSXE”
.1.3.6.1.4.1.9.9.249.1.1.1.1.2.4000 “CAT9K_IOSXE”
.1.3.6.1.4.1.9.9.249.1.1.1.1.3.3000 “CAT9K_IOSXE”
.1.3.6.1.4.1.9.9.249.1.1.1.1.3.4000 “CAT9K_IOSXE”
.1.3.6.1.4.1.9.9.249.1.1.1.1.4.3000 “IP|SLA|IPv6|IS-IS|FIREWALL|PLUS|QoS|HA|NAT|MPLS|VPN|LEGACY PROTOCOLS|3DES|SSH|APPN|IPSEC”
.1.3.6.1.4.1.9.9.249.1.1.1.1.4.4000 “IP|SLA|IPv6|IS-IS|FIREWALL|PLUS|QoS|HA|NAT|MPLS|VPN|LEGACY PROTOCOLS|3DES|SSH|APPN|IPSEC”
.1.3.6.1.4.1.9.9.249.1.1.1.1.5.3000 “16.9.2”
.1.3.6.1.4.1.9.9.249.1.1.1.1.5.4000 “16.9.2”
.1.3.6.1.4.1.9.9.249.1.1.1.1.6.3000 1
.1.3.6.1.4.1.9.9.249.1.1.1.1.6.4000 1
.1.3.6.1.4.1.9.9.249.1.1.1.1.7.3000 “Cisco IOS Software [Fuji], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 16.9.2, RELEASE SOFTWARE (fc4)
Technical Support: http://www.cisco.com/techsupport
Copyright © 1986-2018 by Cisco Systems, Inc.
Compiled Mon 05-Nov-18 19:32 by mcpre”
.1.3.6.1.4.1.9.9.249.1.1.1.1.7.4000 “Cisco IOS Software [Fuji], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 16.9.2, RELEASE SOFTWARE (fc4)
Technical Support: http://www.cisco.com/techsupport
Copyright © 1986-2018 by Cisco Systems, Inc.
Compiled Mon 05-Nov-18 19:32 by mcpre”

And here is the output from a Cisco C9400:

$ snmpwalk -c public -v2c -OsqnU -M /opt/librenms/mibs 192.168.2.29 .1.3.6.1.4.1.9.9.249.1.1.1.1
.1.3.6.1.4.1.9.9.249.1.1.1.1.2.5000 “CAT9K_IOSXE”
.1.3.6.1.4.1.9.9.249.1.1.1.1.2.6000 “CAT9K_IOSXE”
.1.3.6.1.4.1.9.9.249.1.1.1.1.3.5000 “CAT9K_IOSXE”
.1.3.6.1.4.1.9.9.249.1.1.1.1.3.6000 “CAT9K_IOSXE”
.1.3.6.1.4.1.9.9.249.1.1.1.1.4.5000 “IP|SLA|IPv6|IS-IS|FIREWALL|PLUS|QoS|HA|NAT|MPLS|VPN|LEGACY PROTOCOLS|3DES|SSH|APPN|IPSEC”
.1.3.6.1.4.1.9.9.249.1.1.1.1.4.6000 “IP|SLA|IPv6|IS-IS|FIREWALL|PLUS|QoS|HA|NAT|MPLS|VPN|LEGACY PROTOCOLS|3DES|SSH|APPN|IPSEC”
.1.3.6.1.4.1.9.9.249.1.1.1.1.5.5000 “16.9.3”
.1.3.6.1.4.1.9.9.249.1.1.1.1.5.6000 “16.9.3”
.1.3.6.1.4.1.9.9.249.1.1.1.1.6.5000 1
.1.3.6.1.4.1.9.9.249.1.1.1.1.6.6000 1
.1.3.6.1.4.1.9.9.249.1.1.1.1.7.5000 “Cisco IOS Software [Fuji], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 16.9.3, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright © 1986-2019 by Cisco Systems, Inc.
Compiled Wed 20-Mar-19 08:02 by mcpre”
.1.3.6.1.4.1.9.9.249.1.1.1.1.7.6000 “Cisco IOS Software [Fuji], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 16.9.3, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright © 1986-2019 by Cisco Systems, Inc.
Compiled Wed 20-Mar-19 08:02 by mcpre”

Hi @alanbboyd @tristanbob
Please open an issue here with all details required :


Thanx

This has been asked before… example: https://github.com/librenms/librenms/issues/8244 & https://github.com/librenms/librenms/issues/9725

The current MIB is available here ftp://ftp.cisco.com/pub/mibs/v2/CISCO-PRODUCTS-MIB.my

Hi @ManOfLard
Unless you checked the SNMP replies of the complete family, we don’t know yet if solving the issue you mentionned would also solve the issue with 9400.
That would be better to open a new issue with the full data, and link it to the 2 previous issue, so the community member who decides to contribute for 1 of the 3 issues would also check the 2 others.

As you know, LibreNMS is contributor based, so anybody (including all readers of this post :slight_smile: ) can contribute. We’ll be glad to help.

I’m more than happy to provide for the Catalyst 9200/9300 - but I cannot see exactly what path to follow to provide it (docs.librenms starts down the scripts/new-os path…

But I don’t see the generated file and after being asked “Base discovery file created,ctrl+c to exit now otherwise please enter the MIB name including path (url is also fine) for us to check for sensors:” - I guess nothing happens after I hit ctrl-c if I don’t provide the MIB (and according to Cisco’s MIB locator there are around 40 MIBs for the device…which 39 to ignore?)

The other pathways are closed to me because use of pastebin (for example) is a breach of policy leading to dismissal… and I rather like my job :smiley:

I would suggest to run the discovery part with verbose and debug (-v and -d) and find out why the standard Cisco recognition pattern is not hit. That is probably a very small change that is needed to make those behave the same as all other devices of the Cisco Catalog. Best would be to compare with a working device as close as possible to the 9200/9300.

@PipoCanaja ok - help me out here - I have heaps of these devices, I’m ready to do this. Rather than simply closing down the issue on github, how about some feedback on why it’s not usable. Feels very much like a punch in the face after 3 months of nothing.

Sorry for the lack of details in the PR. It is now more verbose :slight_smile: No matter what, the goal is definitly to improve this discovery with ASRs :slight_smile:

As per github - Catalyst 9k series is not ASR 9k series… Apples & oranges!

All right, then, as stated in the issue, let’s try once again to gather the necessary data so that somebody can add support without having the realbox in front of his eyes.

Hopefully I’ll get enough time to run this discovery on a test device & stack for both Catalyst 9200 & 9300 (helpful to do it for different IOS XE versions? They all appear to suffer from the same parsing failure)

Yep, but the OID providing the information might not be the same for both so 2 of those snmpwalks would be good to.