[Top] [All Lists]

RE: [nv-l] SNMPv2 traps and data collection on Windows (was netmon not r

To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] SNMPv2 traps and data collection on Windows (was netmon not responding)
From: James Shanks <jshanks@us.ibm.com>
Date: Thu, 20 Oct 2005 13:05:38 -0400
Delivery-date: Thu, 20 Oct 2005 18:06:10 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
In-reply-to: <20051020135627.EE8D327128@smtpintpos.ustri.com>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Hello Praveen,

You asked this question in your last append on netmon not responding.  It
probably should been asked in a separate posting since it has nothing to do
with netmon.  So I'm responding to it in this one.
Here's what you asked:

> One more help needed from you is SNMPv2 trap support on Windows
> Converting to this what are the benefits I will get.
> In my environment to monitor the VPN tunnel status almost all the mibs
> v2mibs. If  I load snmpv2 enabling the snmpv2 trap is required? And also
> put an snmp collect for the snmpv2 mibs loaded.

The question that has be answered first is, "What do the vendors who
provide the SNMP agents on your VPN equipment provide?"  I cannot answer
that.  You will have to find out.  Some can respond to either SNMPv1 or
SNMPv2, and some will let you configure them with what you want.  Don't ask
me though.  I have no expertise with configuring Cisco, or Nortel, or
whomever else might supply your hardware.  Other list users might know,
however, so you could ask a more specific question about configuring them
and see whether anyone responds.

In order for you to get traps from those devices they will have to be
configured to know where to send them as well, so one way or another,
someone has to configure them.  If they will only send their traps in
SNMPv2 format, then you will have to configure your NetView for Windows to
receive SNMPv2 traps in the manner that the Release Notes tell you.  If you
do not, then you will never see those SNMPv2 traps in NetView's event
browser or trapd.log.  They will be thrown away or perhaps flagged as
invalid traps.   If the devices can send SNMPv1 traps, then you do not need
to alter your default NetView for Windows configuration.

The same thing holds true for data collection.  Many companies,
particularly Cisco, offer SNMPv1 versions of their SNMPv2 MIBs.  If you can
get an SNMPv1 copy then you can load it with the standard MIB loader,
loadmib, and then use the collect utility to tell snmpcollect what to

If you cannot get an SNMPv1 copy of the MIB, then you can load it the
loadmibv2 loader, and browse it with the browserv2 browser.  You can use
that browser to see what kind of data the agent will return to your
If the data type is Integer, Counter, or Gauge, then you can manually
configure the snmpCol.conf file to get snmpcollect to gather that data.
Otherwise, you will be forced to write your own script or bat file to
gather the data, using snmpwalk or snmpget.  Most agents are capable of
responding in both SNMPv1 or SNMPv2 format, depending on how they are
queries, and if these are like that then the scripts will work.  If not,
then I'm afraid that you are just out of luck in the current release of
NetView.  Full SNMPv2 support is not yet available.


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

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

Archive operated by Skills 1st Ltd

See also: The NetView Web