Thanks James,
Could you please clarify a couple of things.
(1) If I want actionsvr to page the ruleset must be in ESE.automation,is
this right.
(2) If I set the event stream to block and remove the forward,how will my
rule pass events on to TEC?
Surely TEC will only recieve node down events,would I have to enable every
event one by one to forward to TEC?
I have qualified the full path name ,as I explained paging works from the
trap action.It does not work from the ruleset.
The nvaction.alog has an error : A service port for the actionserver is not
defined in the /etc/services.Trying port 1670.
Using port 1670 for registration.
Seems like this is the problem.Can you tell me what port to set it too?
regards Arthur
-----Original Message-----
From: James Shanks [mailto:James_Shanks@TIVOLI.COM]
Sent: Wednesday, January 19, 2000 1:11 AM
To: NV-L@UCSBVM.UCSB.EDU
Subject: Re: node down ruleset not paging.
A few things:
(1) Never, ever, put a ruleset into ESE.automation if it has a Forward in
it, or
if the initial event stream node is set to PASS, or you will eventually hang
all
ruleset processing. The actionsvr daemon who runs these rulesets in
ESE.automation has no display and cannot display event sent to him; they
must
come with an action instruction, a command. If he gets unconnected events,
they
just fill up his socket until he hangs, and then nvcorrd hangs because his
outgoing socket fills too.
(2) If you use an action node, always fully-qualify the name of the
executable
you wish to run because the daemons do not share your path. Most of them do
not
even have /usr/OV/bin in their path.
(3) I have seen ruleset paging work on Solaris 2.6 so I would guess you have
a
set-up problem. Whether you include your paging command in an Action node
or
use the Paging Node in a ruleset, the actual paging is done by actionsvr.
He
has a log where all his output goes: /usr/OV/log/nvaction.alog (and .blog
when
the alog gets too big -- it always starts on alog and if there is already
data
there, copies it to blog on startup). So look there for error messages.
James Shanks
Tivoli (NetView for UNIX) L3 Support
"Boulieris, Arthur" <Arthur.Boulieris@NZ.UNISYS.COM> on 01/17/2000 09:27:46
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: node down ruleset not paging.
hello,
I have been following the thread on node down node up and decided to
implement it.
My current implementation is an action from the trap configuration which
looks like /usr/OV/bin/nvpage 1234@Carrier $3 $2.This works fine only get
too many pages that arent real outages.
I then decided to try my luck at correlating an event.
I have an event stream pass by default.It goes to two trap settings,node
down and node up then to a reset on match.The reset is hostname on slot
1(node down) equals hostname on slot 2 (node up).My poll interval is 5
minutes so my reset time 7 minutes.
then I want a page.I have tried configuring an action using the same as
above which works fine for the trap,it doesnt however work for the rule.I
made sure the ruleset was in /usr/OV/conf/ESE.automation ,stopped and
started all daemons.
I then set up an administrator and tried using the pager node .I had the
operator and the message was $3 $2.This too didnt work.The end of the rule
has a forward node.
If I set up an event window in control desk it appears that the rule works,
the node down is only displayed after 7 minutes if a node up hasnt
happened.It would appear that the problem is paging
Im running netview 5.1.2 on solaris 2.6.
What am I doing wrong here,all seems too easy but it dont work????
thanks ab
Arthur Boulieris
Implementation & Support
Systems Management
<<...>>
------
Attachments are virus free!
This message has been scanned for viruses at the originating end by
Nemx Anti-Virus for MS Exchange Server/IMC
http://www.nemx.com/products/antivirus
|