Update: Adding NetApp's OID into there did indeed fix the issue. ----- Original Message ----- From: "James Pulver" <[email protected]> To: "General discussion of using zenoss system" <[email protected]> Sent: Thursday, February 5, 2009 1:09:56 PM GMT -06:00 US/Canada Central Subject: Re: [zenoss-users] Importing MIBs
I believe so. This has been a recurring issue recently on the forums. -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University Kristofer wrote, On 2/5/2009 12:49 PM: > I think I may have found what I'm looking for in the zentrap.py code: > > # Some vendors form their trap MIBs to insert a 0 before the > # specific part of the v1 trap, but the device doesn't actually > # send the 0. Unfortunately we have to make explicit exceptions > # for these to get the OIDs decoded properly. > expandableV1Prefixes = ( > '1.3.6.1.2.1.17', # Spanning Tree Protocol > '1.3.6.1.4.1.1916', # Extreme Networks > '1.3.6.1.4.1.6247', # Comtech > '1.3.6.1.4.1.8072', # Net-SNMP > '1.3.6.1.4.1.12394.1.2', # Rainbow > ) > > I presume I just need to add NetApp's t othe list. > > ----- Original Message ----- > From: "Kristofer" <[email protected]> > To: "zenoss-users" <[email protected]> > Sent: Thursday, February 5, 2009 11:27:36 AM GMT -06:00 US/Canada Central > Subject: [zenoss-users] Importing MIBs > > I'm attempting to import the NETWORK-APPLIANCE-MIB (from both NetApp, > and http://www.oidview.com/mibs/789/NETWORK-APPLIANCE-MIB.html -- I've > tried both). > > There are no errors or anything when it imports, but I am seeing an issue. > > I have configured the NetApp to send traps to Zenoss. I had a trap come > in as "netapp.224" (which from the MIB is > "scsitgtPartnerPathMisconfigured", and looking on oidview.com the OID is > 1.3.6.1.4.1.789.224). > > The MIB in Zenoss has an extra zero in it: 1.3.6.1.4.1.789.0.224 > > I've gone farther and looked at the actual MIB file itself: > > scsitgtPartnerPathMisconfigured TRAP-TYPE > ENTERPRISE netapp > VARIABLES {productTrapData, productSerialNum} > DESCRIPTION > "SCSI Target: FCP Partner Path Misconfigured" > > ::= 224 > > and at the top of the MIB file, "netapp" is defined as > > netapp OBJECT IDENTIFIER ::= { enterprises 789 } > > So I believe that the "correct" oid for this should be the one found on > oidview.com (without the zero), and that Zenoss is adding an extra "0" > just before the .224, causing the OID's to not match. > > Which is correct? Why do they not match? And how do I fix it? > > I'll admit, I don't know a ton about SNMP, so I may be looking at this > wrong. I would greatly appreciate any feedback I can receive. > > Thanks, > Kristofer > > > _______________________________________________ zenoss-users mailing > list [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users > > > ------------------------------------------------------------------------ > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
