|
From: Jeroen v. I. <j.v...@ut...> - 2015-05-12 15:35:53
|
> Sorry, this is an OS version, not model number problem as the previous > subject states. > > Some more info. Here is discover with -DISQ for the device that works: > > SNMP::Info::_global agSoftwareVersion : > IBM-GbTOR-10G-L2L3-MIB::agSoftwareVersion.0 : > .1.3.6.1.4.1.26543.2.7.4.1.1.1.10.0 > > Here's the same info for one that doesn't: > > SNMP::Info::_global agSoftwareVersion : > IBM-GbTOR-10G-L2L3-MIB::agSoftwareVersion.0 : > .1.3.6.1.4.1.26543.2.7.4.1.1.1.10.0 > SNMP::Info::_global(agSoftwareVersion) NOSUCHOBJECT at > /home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discover.pm line 152. > > That's the wrong MIB file for that device. I put the correct MIB files > in the netdisco-mibs/ibm directory. How do I get netdisco to use the > correct one? Is that even the problem? SNMP::Info determines what SNMP objects to query for each device, eg to determine the os_ver. Looks like all three IBM switch models are classified as SNMP::Info::Layer3::IBMGbTor devices, which always requests the object IBM-GbTOR-10G-L2L3-MIB::agSoftwareVersion.0 (.1.3.6.1.4.1.26543.2.7.4.1.1.1.10.0) to determine the software version. The IBM-GbTOR-10G-L2L3-MIB in netdisco-mibs however seems specific to the G8124 model. What MIBs should be used for models other than the G8124 ? They would have to be included in netdisco-mibs and SNMP::Info has to be updated to use the correct MIBs and objects for each model. Regards, Jeroen van Ingen ICT Service Centre University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands |