Zenoss adds extra 0 to some imported MIBs

[gcollis]

gcollis [http://community.zenoss.org/people/gcollis] created the discussion

"Zenoss adds extra 0 to some imported MIBs"

To view the discussion, visit: http://community.zenoss.org/message/68793#68793

--------------------------------------------------------------
Hi,

Zenoss is adding some MIB's e.g. cpqRack-mib into zenoss with an extra "0"'s in their OID, so when an event is sent to zenoss with that OID that event is not translated/matched to the OID correctly.

e.g.

MIB is loaded in zenoss with
cpqRackServerBladeInserted2     1.3.6.1.4.1.232.0.22051    notification

But trap comes from the device as 1.3.6.1.4.1.232.22051

Can this be fixed/worked around, to make the MIBS/OID's match correctly?

The fix in older versions of zenoss was to add these MIBs to "expandableV1Prefixes" list in zentrap.py - this no longer exists in later versions of zenoss

http://community.zenoss.org/message/27886#27886 http://community.zenoss.org/message/27886

I am using zenoss version 2.5.2

Thanks,
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/68793#68793]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]