Re: [nv-l] Traps from IBM SAN Volume Controller

2005-02-14 09:13:40
Subject: Re: [nv-l] Traps from IBM SAN Volume Controller
From: Paul <pstroud AT bellsouth DOT net>
To: nv-l AT lists.us.ibm DOT com
Date: Mon, 14 Feb 2005 09:12:50 -0500
Ok so it sounds like either
a) the enterprise that the traps are coming in with does not match
those that the mib contained
b) the mib contained several specific traps, but not the particular ones
you are receiveing.

The trapd.log should give you all the information you need. On a unformatted trap it will dump the Enterprise ID and the Generic and Specific trap numbers. With those you should be able to determine if that particular trap was defined(obviously it was not, what is the problem, is it a different enterprise ID or did they not define the trap
that you are receiving).

Either way, you should be able to solve it by manually adding the trap definition if


mlelleby AT adelphia DOT net wrote:


You would be correct.  The script that contained the addtrap commands was run 

If I go into Options>Event Customization..SNMP and look for the Enterprise OID, 
I can see the 3 'specific traps' that were contained in the script file created by 
the mib2trap command.


---- Paul <pstroud AT bellsouth DOT net> wrote:
After you ran mib2trap did you actually run the commands that were created?
Did it complete successfully?


mlelleby AT adelphia DOT net wrote:

Good morning group-

I have been trying to configure the traps for this device as I have already 
loaded the MIB, ran the mib2trap to create the addtrap commands to add the 
traps from the mib into netview.

I then ran an 'event -e FMTCHG' to note the change to the trapd.conf file.

However, when the device sends a trap, it still comes in unformatted.

I have checked the trapd.conf and note that the traps taken from the mib and loaded into netview seem to be correct.
Any suggestions?