Bob -
I don't see anything which would prevent this from working, though I think all
your in-line actions should be actions. There is no reason to tie up nvcorrd
with sending emails and calling your telalert pager software when actionsvr
itself will do it better (actionsvr spawns a new process for each action so they
execute as nearly simultaneously as possible while in-line actions are done
serially by nvcorrd, which can slow down all of event processing). I take it
this ruleset is included in the ESE.automation file and that's why you recycled
actionsvr.
More likely you haven't got any Network Critical events to drive this yet,
But you can trace the execution if you like. Issue nvcdebug -d all and then
go look in the /usr/OV/log/nvcorrd.alog and .blog and you can see the trace of
the ruleset being executed.
James Shanks
Tivoli (NetView for UNIX) L3 Support
"Sandoval, Bob" <Bob.Sandoval@LATIMES.COM> on 12/29/99 01:14:48 PM
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/Tivoli Systems)
Subject: Problem w/rulesets
Can someone help me with this problem. I'm a bit green with this
application, but I thought I did everything required.
I created this on Tuesday 12/28. It originally was working as 3 separate
rulesets. One for the Action nodes for the displays and one for each of the
2 Inline Actions. After combining these rulesets into one and removing the
unwanted rulesets from production, I also stopped and started the actionsvr.
I checked the trapd.log, though I didn't see any Network Critical msgs I did
see messages reporting serial links down which were being reported through
Network Critical events.
I'd appreciate any information you can provide.
Thanks in advance..........
<<NetWork Critical RS.jpg>>
Bob Sandoval
Los Angeles Times
Information Technology
Network Engineering
213.237.5889
Bob.Sandoval@LaTimes.com
NetWork Critical RS.jpg
Description: JPEG File Interchange
|
