Doing a little experimentation on what Jim is talking about,
should give you the info you're looking for.
$NVA - is going to be the device that sent the trap.
Write a small script that prints out to a file "$NVATTR_1..n,
where n probably is less than 5.
Force the device to send a trap.
Look at the contents of the file, and decide on what attributes
you'll need. I do this all of the time, and it works well.
Since you'll probably be looking at different attributes and
keywords depending upon device... you might also want to
print out the enterprise, and use this to setup the strings
you'll be searching for (unless the trap numbers are unique
enough).
Regards,
Gary Boyles
-----Original Message-----
From: James Shanks [mailto:James_Shanks@TIVOLI.COM]
Sent: Tuesday, December 22, 1998 3:07 PM
To: NV-L@UCSBVM.UCSB.EDU
Subject: Re: cisco traps 2
I am not certain what you are asking. NVATTR_2 refers to the second
variable of the trap, as used in a ruleset. It will always refer to the
contents of the second variable, no matter whose trap it is. If you are
asking, "Is there a variable in a Cisco trap which always contains the
hostname of the sending device?", then I don't know the answer to that
question. But if it is in a variable, then you can reference the variable
as $NVATTR_x, where x is an integer from 1 - 50. If it is not in a
variable, but you need the sender's origin, you reference that as $NVA.
These variable assignments are discussed in the NetView Administrator's
Guide.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Oren Mamok <orenm@ns.tadiran.com> on 12/22/98 09:26:16 AM
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: cisco traps 2
Thank you all,
I configured the trapd to recieve smnp over udp through port 162
and not 412. It all working well i'm recieving cisco's traps.
Is there a way to isolate the cisco trap's varaiables like NVATTR_2 in NV ?
Greetings,Oren.
|