You need to re-start actionsvr. He is the one who loads and runs those
rulesets in the background. After he is restarted you should be able to
see the successful loads in /usr/OV/log/nvaction.alog as well as any
results written to stdout or stderr.
Just as side note I always add when someone indicates that they have just
started using background rulesets. If you already know, then great, but
others may not. Remember that your background rulesets should not have a
Forward or a Resolve in them, because actionsvr does not have a display,
and all of them should have the initial event stream node (the "purple
pizza") set to "Block". Otherwise, actionsvr will get a ton of events he
doesn't know what to do with (he has no way to dequeue those which do not
have an associated action) and they will eventually fill up his sockets
and cause the entire event process to start backing up -- first actionsvr,
then nvcorrd, then trapd. One by one they will slow and stop.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group
"Dejan Mijailovic" <dejan.mijailovic@inquent.com>
04/08/2002 11:20 AM
To: <nv-l@lists.tivoli.com>
cc:
Subject: [nv-l] rulesets and ESE.automation
Hi people. A quick question about ruleset and ESE.automation for NetView
7.1
on Solaris 7.
What is the next step after configuring and adding the ruleset inside
ESE.automation file.
Do I need to restart some ov processes and agents or do nothing?
Thanks
Dejan Mijailovic
InQuent Technologies inc.
e-mail: dejan.mijailovic@inquent.com
http://www.inquent.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)
|