nv-l
[Top] [All Lists]

RE: [nv-l] error w/ mib2trap

To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] error w/ mib2trap
From: James Shanks <jshanks@us.ibm.com>
Date: Thu, 6 Apr 2006 08:38:09 -0400
Delivery-date: Thu, 06 Apr 2006 13:38:33 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <AD79F859134E49439B1BF655B50EB1DE02C4DF92@pccsseaex01.pemcocorp.net>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
-T is valid though it may not be documented at you level of code.  It tells
addtrap not to send the FMTCHG event to trapd. This flag is added by
mib2trap to prevent trapd from getting into a loop re-reading the
trapd.conf file when many new traps are being added at once.

You problem is the -i, not -T.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group


                                                                           
             "Glen Warn"                                                   
             <Glen.Warn@pemcoc                                             
             orp.com>                                                   To 
             Sent by:                  <nv-l@lists.us.ibm.com>             
             owner-nv-l@lists.                                          cc 
             us.ibm.com                                                    
                                                                   Subject 
                                       RE: [nv-l] error w/ mib2trap        
             04/05/2006 08:32                                              
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
             nv-l@lists.us.ibm                                             
                   .com                                                    
                                                                           
                                                                           




I think I fixed this.  After going thru each parameter I found there is no
T option for addtrap.  I also saw that the –i parameter wasn’t being
issued.  I did a search and replace on the –T with a –i
1.3.6.1.4.1.9.9.171.2 and reran the script.  It seems to have worked fine.
Does anyone have any input on the –T (specifically why would mib2trap put
it there?)  Not sure which of the 2 actually was the fix, but it did run
w/o error now.


From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On
Behalf Of Glen Warn
Sent: Wednesday, April 05, 2006 4:57 PM
To: nv-l@lists.us.ibm.com
Subject: [nv-l] error w/ mib2trap

Running NV 7.1.4 FP3 on RH AS.21

Have had this problem before, cannot recall work around.

Trying to get traps defined for CISCO-IPSEC-FLOW-MONITOR-MIB.my

Run mib2trap against it and works well (except for this warning at the
beginning)
Warning: The mib description doesn't seem to be consistent.
 Some nodes couldn't be linked under the "iso" tree.
 These nodes are left:

And this at the bottom
Enterprise object id not found for trap cikeTunnelStart, (6,1).Enterprise
object id not found for trap cikeTunnelStop, (6,2).Enterprise object id not
found
 for trap cikeSysFailure, (6,3).Enterprise object id not found for trap
cikeCertCrlFailure, (6,4).Enterprise object id not found for trap
cikeProtocolFailu
re, (6,5).Enterprise object id not found for trap cikeNoSa,
(6,6).Enterprise object id not found for trap cipSecTunnelStart,
(6,7).Enterprise object id not
 found for trap cipSecTunnelStop, (6,8).Enterprise object id not found for
trap cipSecSysFailure, (6,9).Enterprise object id not found for trap
cipSecSetUp
Failure, (6,10).Enterprise object id not found for trap cipSecEarlyTunTerm,
(6,11).Enterprise object id not found for trap cipSecProtocolFailure,
(6,12).En

Now that I have a script to run, I do but it returns this over and over
again.

Usage: /usr/OV/bin/addtrap -n enterprise-name
          -l trap-label
          -i ent-object-id
          -g gen-trap
          -s spec-trap
          -o source-ID
          -S severity-flag
          -t status-type
          -c category
          -F format-specification
         [-C command]
         [-d display] ]
         [-D description] ]
         [-N node list] ]
         [-e TEC Class Name] ]
         [-E TEC Slot Name] ]
         [-V TEC Slot Value] ]
         [-T do not send FMTCHG event to trapd ]
 If arguments contain space, use the double quotation mark.

Here is a sample from the beginning of the script.

/usr/OV/bin/addtrap -l cikeTunnelStart -g 6 -s 1 \
   -n cipSecMIBNotifications  \
   -o A  -c "LOGONLY" -t 0 \
   -S 1  \
   -T \
   -D "This notification is generated when an IPsec Phase-1
IKE Tunnel becomes active."  \
   -e cikeTunnelStart  \
   -F '$E $G $S $# args: $*'

I’ve also tried running the first step manually and it fails too.  Am
tinkering to see where but here is the command I’ve used.

/usr/OV/bin/addtrap -l cikeTunnelStart -g 6 -s 1 -n cipSecMIBNotifications
-o A  -c "LOGONLY" -t 0 -S 1 -T -D "This notification is generated when an
IPsec Phase-1 IKE Tunnel becomes active." -e cikeTunnelStart -F '$E $G $S
$# args: $*'


<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web