nv-l
[Top] [All Lists]

Re: mib2trap and SNMPV2 (was Re: Problem with nvaddtrapdconf)

To: nv-l@lists.tivoli.com
Subject: Re: mib2trap and SNMPV2 (was Re: Problem with nvaddtrapdconf)
From: "Prokott, Joe" <Joe.Prokott@WESTGROUP.COM>
Date: Wed, 4 Nov 1998 15:46:44 -0600
Reply-to: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Sender: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
James,

mib2trap did not work.  An output file of zero size was created.  I will be
reporting this to support.

Joe

-----Original Message-----
From: James_Shanks@TIVOLI.COM [mailto:James_Shanks@TIVOLI.COM]
Sent: Wednesday, November 04, 1998 12:19 PM
To: NV-L@UCSBVM.UCSB.EDU
Subject: Re: mib2trap and SNMPV2 (was Re: Problem with nvaddtrapdconf)


Joe -

Have you tried running mib2trap against this MIB?   I took a look at the
parsing routine in mib2trap and I saw that it does parse NOTIFICATION-TYPE,
but I declined to continue my investigation into what happens after that.
So I may have been wrong about only looking for TRAP-TYPE before.

What can you do if mib2trap doesn't handle it?  Two major choices
(1) Call Support and report it and perhaps it will get fixed later on
(2) Do any one of a number of things you did with Version 4 of NetView
where there was no mib2trap
     a.  Look for doc from the vendor and add the trap to trapd.conf using
the GUI or addtrap.
     b.  Read the MIB and figure out what the enterprise id should be and
then with the NOTIFICATION-TYPE defs, add traps for that enterprise (looks
like they are generic 6 and specific 1 and 2 per the def below) based on
what it tells you (not much).  Since you don't know what variables will be
provided from the definition below, you will still have to use $* to see
them all.
     c.  Wait for the traps to arrive and use the information provided in
the "NO FMT FOUND" trap to define them.  Unless there are more NOTIFICATION
sections, the MIB says there are just these two.

Even with mib2trap, the odds are good you are still going to have to
configure the traps after you start getting them, since you won't know what
severity to place on them or whether you should send them to TEC,  and so
on.   New product usage is always like that.

James Shanks
Tivoli (NetView for UNIX) L3 Support



"Prokott, Joe" <Joe.Prokott@WESTGROUP.COM> on 11/03/98 12:02:51 PM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L@UCSBVM.UCSB.EDU>

To:   NV-L@UCSBVM.UCSB.EDU
cc:    (bcc: James Shanks)
Subject:  Re: mib2trap and SNMPV2 (was Re: Problem with nvaddtrapdconf)





James,

The MIB is the IBM Network Dispatcher MIB.  I have included the part of
this
MIB in question below.  I do want to have to query for the traps.  I just
want the traps to be sent when they occur on the system.  I assume NV will
need a format for these SNMPv2 just like the SNMPv1 traps.  The question
now
is how do I get these SNMPv2 traps identified as "NOTIFICATION-TYPE" to
into
a valid format in the /usr/OV/conf/C/trapd.conf file?


-- ==========================
-- || The Trap Definitions ||
-- ==========================
indHighAvailStatus NOTIFICATION-TYPE
   OBJECTS { hasState }
   STATUS  current
   DESCRIPTION
       "This trap announces that the value of the high availability
        status state (hasState) variable has changed.  The possible
        values of hasState and their respective meanings are:
         -idle,   (0) this machine is routing packets and is not trying
                      to establish contact with its partner Network
                      Dispatcher
         -listen, (1) high availability has just started and
                      network dispatcher is listening for partner,
         -active, (2) this machine is routing packets.
         -standby,(3) this machine is monitoring the active machine.
         -preempt,(4) transitory state during switch from primary to backup
         -elect,  (5) network dispatcher is negotiating with partner
                      for who will primary or backup
         -no_exec,(6) the executor is not running"
   ::= { dispatcherMibTraps 1 }

indSrvrGoneDown NOTIFICATION-TYPE
   OBJECTS { ssActiveConns }
   STATUS  current
   DESCRIPTION
       "This trap announces that the weight for the server specified
        by the csAddr, psNum, ssAddr portion of the Object Identifier
        has gone to zero, The last known number of active connections
        for the server is sent in the trap.

        This trap indicates that, as far as Network Dispatcher can
        determine, the specified server has gone down."
   ::= { dispatcherMibTraps 2 }
-- end dispatcherMibTraps

===============================

Joe Prokott - West Group
Network Architect
610 Opperman Drive
St. Paul, MN  55123
Phone: 651-687-4536
Fax: 651-687-6946
E-mail: joe.prokott@westgroup.com


-----Original Message-----
From: James_Shanks@TIVOLI.COM [mailto:James_Shanks@TIVOLI.COM]
Sent: Monday, November 02, 1998 4:30 PM
To: NV-L@UCSBVM.UCSB.EDU
Subject: Re: mib2trap and SNMPV2 (was Re: Problem with nvaddtrapdconf)


mib2trap specifically looks for TRAP-TYPE and that's all
Traps in trapd.conf are organized by enterprise -- the oid of who is
sending it, regardless of what it is about.  So an agent implementing
SNMPV2 would have to include any traps under his enterprise.

And most SNMPV2 data is made available via SNMPGET rather than by trap, so
I'm afraid I am not aware of what a NOTIFICATION-TYPE is in this regard.
What MIB are you looking at?

James Shanks
Tivoli (NetView for UNIX) L3 Support

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

Archive operated by Skills 1st Ltd

See also: The NetView Web