|
From: Andy R. <ac...@gm...> - 2015-05-18 15:58:35
|
On Mon, May 18, 2015 at 6:57 AM, Jeroen van Ingen < j.v...@ut...> wrote: > 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 ? > > Pretty sure that they should be similar. They software releases for them are usually numbered very similarly, and from a configuration standpoint they work the same. Andy |