Welcome, Guest. Please login or register.

Author Topic: Module inventory improvements  (Read 2250 times)

rufer

  • Guest
Module inventory improvements
« on: September 23, 2009, 10:02:52 AM »
I propose the following improvements in libsnmp sub Modules:

1) always trim leading/trailing spaces of strings. Reason: Many of our (OEM) SFP modules report serial numbers with a lot of leading/trailing spaces
2) if the module has no module model, use module description as module model. Reason: Most SFP report no module model (ex Cisco Catalyst 3560, 3750) but only a module description.
3) if the module serial number is identical to the module model, use module description as module model. Reason: Some SFP report their serial number (and some spaces...) as their module model.

Example using a Catalyst 3750-48TS-S:

Catalyst 3750 stack members (chassis types) are correctly listed under:
1.3.6.1.2.1.47.1.1.1.1.13
example:
1.3.6.1.2.1.47.1.1.1.1.13.1001 = WS-C3750-48TS-S
So far so good. But SFP modules contain no module model under:
1.3.6.1.2.1.47.1.1.1.1.13
but they contain something under module description:
1.3.6.1.2.1.47.1.1.1.1.2
example:
1.3.6.1.2.1.47.1.1.1.1.2.1059 = 1000BaseSX SFP

Now if I wanted both in the module inventory, I need 2). Because some weird SFP report their serial number leaded by some spaces as module model, I need 3)
In my case the modifications work for all devices I have.

Greetings
Rufer

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2687
    • View Profile
    • NeDi
Re: Module inventory improvements
« Reply #1 on: September 23, 2009, 10:56:54 PM »
I did some work with model and description to get SN of SFPs in modular switches (modules use classvalue 9 where as SFP/GBIC use 10 in entity mib). Can you send me a snmpwalk of such a stack, with that I can verify this works with  my approach? Stripping spaces should not be a problem...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo