Ah, now I understand. When you said "Event Source" I thought you meant the
Event Attribute ruleset node. But you haven't got one of those. The "event
source" you are talking about I'll wager is the item of that name in trapd.conf.
But that has no effect on a ruleset. trapd.conf affects only how the events
will be formatted, not how they will match in the ruleset. The two are almost
independent. nvcorrd gets the raw trap from trapd and has no idea what you put
in trapd.conf. What you have to do is construct an Event attribute block and use
that between the Node Down Trap Setting and the Reset.
James Shanks
Tivoli (NetView for UNIX and NT) L3 Support
"Evankovich, Debra A" <devanko@mtpower.com> on 05/30/2000 01:46:23 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: "'IBM NetView Discussion'" <nv-l@tkg.com>
cc: (bcc: James Shanks/Tivoli Systems)
Subject: RE: [NV-L] Ruleset for specific node down at 15 minutes
* The Event Stream is set to BLOCK.
* Two Trap Settings: 1-Node Down, 2-Node Up
* Reset on Match - 2 Equal 2, Delay Time: 15 minutes
* Two Actions - One generates email, one for paging.
The ruleset itself works for the node down >15 minutes (email and
page are generated). The only problem is the Event Source doesn't
limit the devices to the one in the list. I'll turn on the trace to see
what happens.
Thank you.
> -----Original Message-----
> From: James_Shanks@tivoli.com [SMTP:James_Shanks@tivoli.com]
> Sent: Tuesday, May 30, 2000 11:24 AM
> To: IBM NetView Discussion
> Subject: Re: [NV-L] Ruleset for specific node down at 15 minutes
>
>
>
> Event Attributes is how you would do it, and it sounds like you are doing
> it
> right. But you still haven't explained the whole ruleset. What is the
> Event
> Stream (the "purple pizza") set to, BLOCK or PASS? Should be BLOCK. What
> happens after the Reset-On-Match? Should be Forward.
>
> Or are you using this instead of forwardall.rs so that the Event Stream is
> set
> to "PASS" and the node after the Reset is "Resolve" or "Block"?
>
>
> You may want to turn on the nvcorrd trace by issuing "nvcdebug -d all"
> while
> your ruleset is running and look in the nvcorrd.alog and see what happens
> when
> the event comes in. The trace may be a bit confusing for the novice,
> however,
> since it is not documented. You will see that every incoming event is
> marked
> with " ===> Received a Trap", then continues with "===> Processing Event"
> and
> ends with "===> Finished with the Trap" so you can follow what happens to
> every
> one.
>
> James Shanks
> Tivoli (NetView for UNIX and NT) L3 Support
>
>
> "Evankovich, Debra A" <devanko@mtpower.com> on 05/30/2000 12:54:44 PM
>
> Please respond to IBM NetView Discussion <nv-l@tkg.com>
>
> To: "'nv-l@tkg.com'" <nv-l@tkg.com>
> cc: (bcc: James Shanks/Tivoli Systems)
> Subject: [NV-L] Ruleset for specific node down at 15 minutes
>
>
>
>
> Hi all,
>
> I'm trying to create a ruleset to detect specific node down >15 minutes
> and
> then generate a page and email. The problem is that the ruleset picks up
> every 'node down' instead of just the Event Source that is indicated.
>
> I created an event under Enterprise Name netView6000 for NodeDown15 by
> copying Specific Trap Number 58916865. I selected a
> node for the Event Source. I did the same for the NodeUP Specific Trap
> 58916864.
>
> The ruleset includes the new NodeDown15 and NodeUp Trap Settings for Input
> 1
> and 2 on a Reset on Match. Reset on
> Match is Attribute 1 (2) operator 'Equal to' Attibute 2 (2).
>
> Can someone tell me how to enable the ruleset to look only for the
> specified
> Event Source?
>
> Thanks!
>
> Debra
>
> Debra Evankovich
> Network Analyst
> Montana Power Company
> (406) 497-4510
> devanko@mtpower.com
>
>
>
>
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
>
>
>
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|