nv-l

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

2005-02-14 09:50:40
Subject: Re: [nv-l] Traps from IBM SAN Volume Controller
From: Francois Le Hir <flehir AT ca.ibm DOT com>
To: nv-l AT lists.us.ibm DOT com
Date: Mon, 14 Feb 2005 09:50:55 -0500



As you can see, the oid for the trap you received
(1.3.6.1.4.1.2.6.159.201.2) is not the same as the one you defined (
1.3.6.1.4.1.2.6.190.0). You need to find the proper mib or trap definition
for the trap you are receiving.

Salutations, / Regards,

Francois Le Hir
Network Projects & Consulting Services
IBM Global Services
Phone: (514) 964 2145


                                                                           
             <[email protected]                                             
             a.net>                                                        
             Sent by:                                                   To 
             [email protected]         nv-l AT lists.us.ibm DOT com             
  
             us.ibm.com                                                 cc 
                                                                           
                                                                   Subject 
             02/14/2005 09:24          Re: [nv-l] Traps from IBM SAN       
             AM                        Volume Controller                   
                                                                           
                                                                           
             Please respond to                                             
                   nv-l                                                    
                                                                           
                                                                           




 Paul-

Here is the info from the trapd.log on the event in an attached file.

If you note, the specific trap is 1, which is defined in the script that
the mib2trap file created:

=>cat svctraps_3
/usr/OV/bin/addtrap -l tsveETrap -g 6 -s 1 \
   -n ibm2145TSVETraps -i 1.3.6.1.4.1.2.6.190.0 \
   -o A  -c "LOGONLY" -t 0 \
   -S 1  \
   -D "tsve error trap"  \
   -e tsveETrap  \
   -F '$E $G $S $# args: $*'
/usr/OV/bin/addtrap -l tsveWTrap -g 6 -s 2 \
   -n ibm2145TSVETraps -i 1.3.6.1.4.1.2.6.190.0 \
   -o A  -c "LOGONLY" -t 0 \
   -S 1  \
   -D "tsve warning trap"  \
   -e tsveWTrap  \
   -F '$E $G $S $# args: $*'
/usr/OV/bin/addtrap -l tsveITrap -g 6 -s 3 \
   -n ibm2145TSVETraps -i 1.3.6.1.4.1.2.6.190.0 \
   -o A  -c "LOGONLY" -t 0 \
   -S 1  \
   -D "tsve information trap"  \
   -e tsveITrap  \
   -F '$E $G $S $# args: $*'
srtri025:/usr/OV/snmp_mibs






---- Paul <pstroud AT bellsouth DOT net> wrote:
> 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
> necessary.
>
> Paul
>
>
> mlelleby AT adelphia DOT net wrote:
>
> >Paul-
> >
> >You would be correct.  The script that contained the addtrap commands
was run successfully.
> >
> >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.
> >
> >Mike-
> >
> >---- Paul <pstroud AT bellsouth DOT net> wrote:
> >
> >
> >>After you ran mib2trap did you actually run the commands that were
created?
> >>Did it complete successfully?
> >>
> >>Paul
> >>
> >>
> >>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?
> >>>
> >>>
> >>>
> >>>
> >>>
> >
> >
> >
> >
>
(See attached file: svc_trap.doc)

Attachment: svc_trap.doc
Description: MS-Word document