I am very happy you are asking these questions.
Allow me to further articulate what we are trying to engineer here.
There is a SNMP agent on the Siteminder policy server that will send traps.
We are hoping to use Netview to interpret those traps so that we can forward
those events on to the Tivoli Enterprise Console's Event Server for
I was under the impression in order to define events for TEC process, traps
need to go to Netview. What really got me excited is that I can build events
based on the SNMP traps received.
Thank you for the spirited conversation and collaboration. This is fun! :-)
Sr. Systems Programmer
Enterprise Systems Management
Waste Management Incorporated
"Proud Sponsor of NASCAR"
From: John Bruer [mailto:email@example.com]
Sent: Friday, August 01, 2003 10:19 AM
To: Edwards, JT - ESM
Cc: 'firstname.lastname@example.org'; Qureshi, Fawad
Subject: Re: [nv-l] Loading SNMP v2 MIBs
"Edwards, JT - ESM" <JEdwards3@wm.com> writes:
> I am afraid that Netview will be unable to natively monitor some of the
> specifics we are looking for from this application. Hence, the reason we
> pursuing usage of this MIB. It contains specific information about the
> health of this application.
> Things like:
> Authenication failures
> Policy decisions made by the server
> Active Directory tranactions
I'm afraid I still don't understand. Will you be receiving traps from
this application's SNMP agent? Will you be polling this SNMP agent?
In SNMP, those are your two options -- wait for an agent to send an
SNMP trap to signal trouble, or periodically do SNMP GET's from the
agent to see if things are okay.
NetView does primarily 3 things to automatically monitor hosts in a
hands-off setup where you don't have an operator pointing and clicking
through a mib browser:
o pings em (not applicable to application monitoring though)
o Periodically snmpwalk a subset of the SNMP agent's MIB for
o Can use snmpcollect to poll specific mib values on the agent
or combinations of values/formula to see if anything has
exceeded a threshold.
And none of these three things actually requires that a mib be loaded
The only benefits to loading mibs into NetView are:
o allows you to use an snmp mib browser to interactively point
and click your way through the hierarchy and do sets and
gets on those values from a target SNMP agent/device
o it assigns names to numeric OID values in certain log files,
snmpwalks and in trapd.log (but I'm not even sure if that
applies to the v2 mib tree)
o The snmpcollect GUI uses the v1 mib browser to allow you to
interactively specify an OID for data collections and
thresholds settings. This does not apply to snmpv2 mibs
though--for collections on v2 mibs you have to manually
place the snmpv2 OID into snmpCol.conf becaus the browser
won't get ya there.
So I'm left questioning still "why is it you want to load snmp v2 mibs
into netview, and do you really need to do it to get where you want to
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)