-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cisco Nexus 9396 #34
Comments
I've pushed a commit to recognise this but two issues:
Thanks, |
I'm having a tough time duplicating, but someone on Cisco-NSP was able to follow the OID chain to get a real model number. https://puck.nether.net/pipermail/cisco-nsp/2017-February/104635.html I've gone and looked for as much information as I could find on this. Per that thread, it looks like Cisco's ENTITY-MIB is the "most" helpful in explaining what things are. I do plan on submitting TAC request on the device not responding to the OID specified in sysObjectID . snmpbulkwalk -c [redacted] -v 2c [redacted] ENTITY-MIB::entPhysicalModelNameENTITY-MIB::entPhysicalModelName.10 = STRING: N9K-C9396PX snmpbulkwalk -c [redacted] -v 2c [redacted] ENTITY-MIB::entPhysicalDescrENTITY-MIB::entPhysicalDescr.10 = STRING: Fabric Stack Root snmpbulkwalk -c [redacted] -v 2c [redacted] ENTITY-MIB::entPhysicalSerialNumENTITY-MIB::entPhysicalSerialNum.10 = STRING: [redacted] show inventoryNAME: "Chassis", DESCR: "Nexus9000 C9396PX Chassis" NAME: "Slot 1", DESCR: "1/10G SFP+ Ethernet Module" NAME: "Slot 2", DESCR: "40G Ethernet Expansion Module" NAME: "Power Supply 1", DESCR: "Nexus9000 C9396PX Chassis Power Supply" NAME: "Power Supply 2", DESCR: "Nexus9000 C9396PX Chassis Power Supply" NAME: "Fan 1", DESCR: "Nexus9000 C9396PX Chassis Fan Module" NAME: "Fan 2", DESCR: "Nexus9000 C9396PX Chassis Fan Module" NAME: "Fan 3", DESCR: "Nexus9000 C9396PX Chassis Fan Module" snmpbulkwalk -c [redacted]-v 2c [redacted] ENTITY-MIB::entPhysicalModelNameENTITY-MIB::entPhysicalModelName.10 = STRING: N3K-C3548P-10GX snmpbulkwalk -c [redacted] -v 2c [redacted] ENTITY-MIB::entPhysicalDescrENTITY-MIB::entPhysicalDescr.10 = STRING: Fabric snmpbulkwalk -c [redacted] -v 2c [redacted] ENTITY-MIB::entPhysicalSerialNumENTITY-MIB::entPhysicalSerialNum.10 = STRING: [redacted] show inventoryNAME: "Chassis", DESCR: "Nexus 3548 Chassis" NAME: "Module 1", DESCR: "48x10GE Supervisor" NAME: "Fan 1", DESCR: "Chassis fan module" NAME: "Fan 2", DESCR: "Chassis fan module" NAME: "Fan 3", DESCR: "Chassis fan module" NAME: "Fan 4", DESCR: "Chassis fan module" NAME: "Power supply 1", DESCR: "AC power supply" NAME: "Power supply 2", DESCR: "AC power supply" |
https://supportforums.cisco.com/discussion/11591541/model-number-oid Here's a post from Cisco on why they don't answer properly. |
Is there anything I can do to move this forward? Having full support for the Nexus switches (common in IXPs) would be nice. |
I have this as recognising the model as |
n9000 is fine by me, partially because I'm lazy, partially because I wouldn't know what I was doing and partially because it's close enough. |
2017-04-18T11:13:11-05:00 DEBUG (7) [65.182.164.62]: Logger instantiated |
Shite, committed an error - now fixed. |
It no longer craps out when polling the switches. The 3548 shows the unused optics, whereas the 9000 does not. I'm checking out it's support of the IANA MAU MIB. The MAC address page craps out. I also can't get the switches to add if I give a different hostname\name. Is there some logging I can increase the verbosity of to get that sort of information? laravel.log had when I was SNMP polling the existing switches, but nothing when trying to add the new ones. |
I got a different error this time on the 9396 and the 3548. Maybe I had a typo in a previous attempt. Could not interpret switch system description string - most likely because no platform interpretor exists for it. Please see this OSS_SNMP page and consider adding one. Otherwise use the the manual add method. |
Can you confirm the system descriptions? |
It looks like Cisco changed stuff.... root@ixpm:/srv/ixpmanager# snmpget -c MwIX -On -v 2c 210-9396 .1.3.6.1.2.1.1.1.0 |
The 9000 adds correctly, but the 3548 still fails with that same error. Could not interpret switch system description string - most likely because no platform interpretor exists for it. Please see this OSS_SNMP page and consider adding one. Otherwise use the the manual add method. |
@MHammett - I have a specific unit test (see here) for the sys desc you gave me for the 3548 and it's passing. So possibilities are:
Separately, this is neither an INEX nor an IXP Manager project so not appropriate for IXP Manager issues re a few posts above. |
I believe the problem here was that the sysDescr that @MHammett pasted had some adjacent spaces collapsed. I investigated this issue and found the specific switch Mike is using returns a sysDescr string with three spaces prior to the "Compiled" portion of the string. I submitted a pull request to modify the regexp to allow a variable number of spaces in this location of the string. |
Thanks @nschrenk - pulled and merged 🍻 |
root@Indy-IXPM:/home/mhammett# snmpget -c [redacted] -On -v 2c [redacted] .1.3.6.1.2.1.1.1.0
.1.3.6.1.2.1.1.1.0 = STRING: "Cisco NX-OS(tm) n9000, Software (n9000-dk9), Version 6.1(2)I2(2b), RELEASE SOFTWARE Copyright (c) 2002-2013 by Cisco Systems, Inc. Compiled 8/7/2014 15:00:00"
root@Indy-IXPM:/home/mhammett# snmpget -c [redacted] -On -v 2c [redacted] .1.3.6.1.2.1.1.2.0
.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.9.12.3.1.3.1508
I'm not sure which OID is needed, but they all had the same response:
root@Indy-IXPM:/home/mhammett# snmpwalk -c [redacted] -On -v 2c [redacted] | grep SAL1833YM4Y
.1.3.6.1.2.1.47.1.1.1.1.11.10 = STRING: "SAL1833YM4Y"
.1.3.6.1.2.1.47.1.1.1.1.11.22 = STRING: "SAL1833YM4Y"
.1.3.6.1.2.1.47.1.1.1.1.11.149 = STRING: "SAL1833YM4Y"
root@Indy-IXPM:/home/mhammett# ^C
root@Indy-IXPM:/home/mhammett# snmpget -c [redacted] -On -v 2c [redacted] .1.3.6.1.2.1.47.1.1.1.1.11.149
.1.3.6.1.2.1.47.1.1.1.1.11.149 = STRING: "SAL1833YM4Y"
root@Indy-IXPM:/home/mhammett# snmpget -c [redacted] -On -v 2c [redacted] .1.3.6.1.2.1.47.1.1.1.1.11.10
.1.3.6.1.2.1.47.1.1.1.1.11.10 = STRING: "SAL1833YM4Y"
root@Indy-IXPM:/home/mhammett# snmpget -c [redacted] -On -v 2c [redacted] .1.3.6.1.2.1.47.1.1.1.1.11.22
.1.3.6.1.2.1.47.1.1.1.1.11.22 = STRING: "SAL1833YM4Y"
The text was updated successfully, but these errors were encountered: