I don't know how your actions could be processed twice unless you have a
duplicate path you are not aware of.
You can trace ruleset execution with the nvcdbug command. Try nvcdebug -d
all or nvcdebug -d actions and look at the output in the nvcorrd.alog.
That will show for each trap how many times the action is being called.
To trace your action, I would make the first executable line of your script
be set -x which will cause it to trace to the nvaction.log when it
executes.
James Shanks
Tivoli (NetView for UNIX) L3 Support
TAMAR SANDLER <tamars@ns.tadiran.com> on 01/10/99 05:36:20 AM
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)
Subject: actions
Hello all,
I created a ruleset to process a script acordding to a specific trap ( port
down for
instance) , somehow the action is being processed twice for each trap
( i can see that in the nvactiond.alog) the problem is that this script
supose to disable and enable ports and it doesn't working ( the duplication
i geuss).
any ideas ?
Greetings,Oren.
|
Hello all,
I created a ruleset to process a script
acordding to a specific trap ( port down for
instance) , somehow the action is being
processed twice for each trap
( i can see that in the nvactiond.alog)
the problem is that this script supose to disable and enable ports and it
doesn't working ( the duplication i geuss).
any ideas ?
Greetings,Oren.
|
|