snmp-info icon indicating copy to clipboard operation
snmp-info copied to clipboard

Incorrect model information for Extreme XOS devices

Open kingtrw opened this issue 5 years ago • 1 comments

I have three models of Extreme switch running XOS 22.5.1.7 in my environment. Netdisco is not correctly listing the model information for these devices.

I have done an SNMP walk and found that the model info is accessible via SNMP, but possibly not on the normal OIDs.

Switch model: Extreme X620-16t Netdisco listed model: extremeProduct.232 SNMP: Name/OID: .1.3.6.1.2.1.47.1.1.1.1.2.1; Value (OctetString): X620-16t SNMP: Name/OID: .1.3.6.1.2.1.47.1.1.1.1.2.3; Value (OctetString): X620-16t

Switch model: Extreme X460G2-24t-10G4 Netdisco listed model: extremeProduct.197 SNMP: Name/OID: .1.3.6.1.2.1.47.1.1.1.1.2.1; Value (OctetString): X460G2-24t-10G4 SNMP: Name/OID: .1.3.6.1.2.1.47.1.1.1.1.2.3; Value (OctetString): X460G2-24t-10G4

Switch model: Extreme Summit X440G2-24p-10G4 Netdisco listed model: summitVer2Stack SNMP: Name/OID: .1.3.6.1.2.1.47.1.1.1.1.2.1; Value (OctetString): Stack SNMP: Name/OID: .1.3.6.1.2.1.47.1.1.1.1.2.3; Value (OctetString): X440G2-24p-10G4

Stacking is NOT enabled on the X460 or X620, but it IS enabled on the X440 which I believe accounts for the difference in form of the Netdisco listed models -- but I have done an SNMP walk on the switches and cannot find the value that Netdisco is using in the output. It looks like .1.3.6.1.2.1.47.1.1.1.1.2.1 changes to 'Stack' when stacking is enabled, so .1.3.6.1.2.1.47.1.1.1.1.2.3 seems to be consistently the 'correct' model identifier.

This is a low priority issue as I know how to relate the displayed value to the actual value when I look at the inventory information, but I thought I'd submit it anyway.

Software Version App::Netdisco 2.46.1 SNMP::Info 3.70 DB Schema 63 PostgreSQL 9.6.18 Perl 5.16.3

Thanks!

Updated to fix some errors

kingtrw avatar Jul 30 '20 10:07 kingtrw

These switches have now been decomissioned so I have no way of testing this - so I'm entirely okay with it being closed as we're not going to get any extremes again.

kingtrw avatar Jul 03 '23 13:07 kingtrw