nv-l
[Top] [All Lists]

Re: Getting the Event Log Message to a pager.

To: nv-l@lists.tivoli.com
Subject: Re: Getting the Event Log Message to a pager.
From: James Shanks <James_Shanks@TIVOLI.COM>
Date: Mon, 11 Jan 1999 12:02:28 -0500
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>
The Event Log Message as defined in trapd.conf is a construction and not
necessarily part of the incoming trap.  In some cases, all that Event Log
Message contains is the contents of a variable, $3 for example.  Then you
can reference that value in a ruleset as NVATTR_3.  But where a combination
of things is involved you will have to reconstruct it.  For example if the
Event Log Message is "Device $4 has lost power to port $5"  then you will
have to substitute $NVATTR_4 for $4 and $NVATTR_5 for $5 and pass the
entire string yourself as "Device $NVATTR_4 has lost power to port
$NVATTR_5".

James Shanks
Tivoli (NetView for UNIX) L3 Support



Mark van Kerkwyk <kerkwyk@COMTECH.COM.AU> on 01/11/99 12:31:06 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:  Getting the Event Log Message to a pager.





Hi , I know that the severity value isn't available as an environment
variable when executing an action or sending the trap to a pager, anyone
know of a way to access the Event Log Message as a variable ??

How else are we supposed to be able to page someone and supply a text
message describing what occurred ?

The only other way I can think of is use a script like the one someone sent
last week which extracted the severity level details out of trapd.conf on
the fly.

Mark

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

Archive operated by Skills 1st Ltd

See also: The NetView Web