|
From: Jeroen v. I. <j.v...@ut...> - 2015-05-18 13:58:03
|
On 05/12/2015 07:01 PM, Andy Ruhl wrote: > On Tue, May 12, 2015 at 8:35 AM, Jeroen van Ingen > <j.v...@ut... <mailto:j.v...@ut...>> wrote: > > 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. > > > Thanks! > > The G8052 and G8264 firmware comes with the MIB files. I put them in the > netdisco-mibs directory but I was unaware that I had to do something else. > > I'm trying to figure out SNMP::Info but not getting very far. Can you > point me in the right direction? It depends. Are the models similar enough to share most of the vendor specific code or are they so different (eg completely different operating system or acquired / OEM'ed from different companies) that each model or group of models should be put in a separate device class? For example: depending on the model, an HP switch is classified as SNMP::Info::Layer2::HP4000 (old ProCurve models with only menu driven interface), SNMP::Info::Layer2::HP (more current ProCurve models that also have a CLI and differ in SNMP support), SNMP::Info::Layer2::HPVC for VirtualConnect interconnects in blade chassis and SNMP::Info::Layer3::H3C for HP switches running Comware operating system. Without any information about the (dis)similarities between the platforms and without seeing the MIB contents it's hard to advise or assist you. Can you provide a bit more background / info on the various models and can you upload the MIBs that you'd need in a Sourceforge ticket for netdisco-mibs ? Regards, Jeroen van Ingen ICT Service Centre University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands |