A ruleset is one thing, a configured event is another. Which exactly are
you using? For a configured event, the ovactiond daemon would do the
action you configure in the command for automatic action window. Be sure
to use a full path name as the daemon does not share your environment.
ovactiond has a log, the /usr/OV/log/ovactiond.log, which can be consulted
for possible error messages along with successful ones.
For a ruleset, it is the actionsvr daemon who would execute your action.
This too should be specified with a full path name. Look in the
nvaction.alog/blog in /usr/OV/log for clues as to the problem. actionsvr
writes to the alog until it has 1000 lines, then to the blog, and then it
swaps bcak again. Every time the daemon is restarted the old alog is
copied to the blog, and the old blog discarded, so the daemon always starts
with a fresh alog.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
"Wang, Hui" <Hui.Wang@intria.com> on 11/23/2000 01:36:21 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 error,did not send pager when receive the event
Hi:
I have set up a event with Ebterprise ID: 1.3.6.1.4.1.2.6.12.5.1,Specific:
2700.It should send page to two pagers.I found that the action did not
work.I have refreshed the ovactiond and send event manually.For the same
ruleset file, the event 2100 work well and can send pager.I am afraid
something is wrong.Can you give me some ideas?Thks very much.
Regards.
Hui Wang
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|