Here's an example of a trap with parameters.
/usr/OV/bin/snmptrap \
$NVSERVER .1.3.6.1.4.1.2.6.3.1 \
$HOSTNAME 6 58916871 1 \
.1.2.6.1.4.1.2.6.3.1.1.2.0 Integer 14 \
.1.2.6.1.4.1.2.6.3.1.1.2.0 OctetString $SELECTION_NAME \
.1.2.6.1.4.1.2.6.3.1.1.2.0 OctetString "Object status is" \
.1.2.6.1.4.1.2.6.3.1.1.2.0 OctetString $STATUS
The oid in the varbinds does not matter, really. Just make sure you have
sets
of three things: oid, datatype, and value. If the value has blanks, quote
it.
You might try the unsecure version of snmptrap (its on the security
directory, or service directory or something). It would skip the auth
check, and any rate.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
"Allison, Jason
(JALLISON)" To: "'nv-l'"
<nv-l@lists.tivoli.com>
<JALLISON@arinc.c cc:
om> Subject: RE: [nv-l] /usr/OV/bin
06/27/2002 04:02
PM
Thanks for the reply,
I have tried to run snmptrap in the background as well as interchanging the
'nohup' prefix. It still does not run 'quickly'. From another email it
seems the snmptrap command does other things before-hand then just 'send a
trap'.
My situation is a bit different. We are currently installing a 'Netcool'
probe on my Netview NMS boxes to ship over traps to an OpenView box. We
are
also applying a filter on the server side of Netcool so that OpenView will
only display our deemed set of 'Level I' traps. We are sending all of the
traps over so we may trend, baseline, etc at a later date.
As part of my unit testing for this effort, I wanted to write a simple tool
that would randomly send any and every defined trap in our trapd.conf as
quickly as possible. At that point I would throw in random non-defined
traps, illegal traps, etc. This would verify the filter was only
displaying
what we wanted it to on the Openview Box, trap formatting, trap throughput,
and Netcool's 'Store and Forward' capability. All-in-all I was hoping for
a
test tool to kick the cr@p out of the probe and what it is 'supposed' to
do.
The script works although I have not tried to implement the randomness yet
since the 'snmptrap' command is slower than I would like. It is quite the
hack-ish script, but nice enough that it generates some arrays of every
trap
definition in a trapd.conf file. I will probably go the route of the perl
script...that is until I find out perl is not installed on our AIX boxes
/sigh.
Still hoping someone knows how to use the snmptrap syntax to properly add
additional trap info or speed things up. I guess I could write a C program
for this...
Thanks all for the replies,
Jason Allison
Principal Engineer
ARINC Incorporated
Office: (410) 266-2006
FAX: (410) 573-3026
-----Original Message-----
From: Stephen Hochstetler [mailto:shochste@us.ibm.com]
Sent: Thursday, June 27, 2002 2:50 PM
To: nv-l@lists.tivoli.com
Subject: Re: [nv-l] /usr/OV/bin
Jason,
You can do this quickly in your scripts. At the end of each snmptrap
command, add the"&" to run it in the background -- then tell your script to
do this a 1000 times. You will pound your test NMS with 1000 traps pretty
quickly.
Kind regards,
Stephen Hochstetler shochste@us.ibm.com
International Technical Support Organization - Austin
Office - 512-436-8564 FAX - 512-436-8701
ITSO redbooks at http://www.redbooks.ibm.com
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
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)
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
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)
|