Hi James
Thanks for the reply
I have got one little more query regarding the trap of router
What is the sequence of generation of trap when a particular port letus say
one seriel port goes down
Is the sequence is like this
1.Interface is down
2. router is marginal
3.router is down
and for up sequence
1.interface is up
2. router is marginal
3. router is up
so what will be the two event which we have to take into consideration when
we compare Reset-On-Match in the ruleset.
Actually I want if a particluar interface of a router goes down and comes
up within 5 minutes then the event should drop,otherwise the event will
pass through for mail generation.
I want both router trap and node up/down trap in one ruleset,Is it possible
please help
With Regards
John
James Shanks
<jshanks@us.ibm.c To: nv-l@lists.us.ibm.com
om> cc:
Sent by: Subject: Re: [nv-l] ruleset in
Unix
owner-nv-l@lists.
us.ibm.com
04/15/2004 07:41
PM
Please respond to
nv-l
The use of the various ruleset constructs, or nodes, as they are called,
are explained in the NetView Admin Guide. I'd start by reviewing that
material.
You are going to use the graphical ruleset editor, nvrsEdit, to construct
your ruleset. You might want to look at the samples and play with them in
the editor to get a feel of it.
Basically you are writing two rulesets (which could be later combined into
one) that are both very similar. The major construct in each is
Reset-On-Match. It does just what you describe. It holds an event for a
specified time period and if the designated match occurs, the event is
dropped; otherwise it is passed on.
For your Node down case
So you start with the Event Stream node, the thing that looks like a purple
pizza, set to Block events (so you can control when they are displayed) and
from that you have two Trap Settings, one for Node Down and one for Node
Up. The two Trap Settings are connected to the event stream but not to
each other as they represent parallel paths. The Node down connects then
to the Reset-On-Match in the Input 1 slot. The Node Up to the Input 2
slot. In the Reset, your matching attribute will the be hostname of the
incoming event, which for NetView is always Attribute 2 of the event. and
the time will be 5 minutes. On the output side of the Reset-On-Match you
will have an Action node. In it you will put the full path to a script you
will write to send the event text you want in e-mail. You would use the
UNIX sendmail command for that.
For your Router Marginal case, you have the same structure except that the
two TrapSettings are for Router Marginal, rather than Node Down, and Router
Up rather than Node Up
To activate your ruleset(s) you would put the name of them in
/usr/OV/conf/ESE.automation and restart actionsvr who will run them. You
can see the commands being logged in his logs, nvaction.alog and blog. You
can trace the action of the ruleset in the nvcorrd log, if you first issue
the command "nvcdebug -d all" to cause the trace to activate.
Hope this helps
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
john@cosmos.dcmds.co.in
Sent by: owner-nv-l@lists.us.ibm.com
To
nv-l@lists.us.ibm.co
04/15/2004 12:04 AM m
cc
Please respond to Subject
nv-l [nv-l] ruleset in
Unix
Hi,
I want to write a ruleset to take action whenever the down event recived it
should hold for 5 minutes,If Upevent is recived within 5 mins then both
events will dropped. If UP event is not recived,within the allowed time
then down event will trigger and mail is to be send.Also in the case of
router if ruter marginal event recieved it should block router down event
also for 5 minutes,if up event recieved within 5 min then both the event
should dropped,otherwise mail is to be generated
If any body has the idea then please help, I am a new user of Netview
with Regards
John
---------------------------------------------------------------------------
The information in this e-mail is the property of DCM DataSystems and may
be confidential and privileged. It is intended solely for the addressee and
access of this email by anyone else is unauthorised. If you are not the
intended receipient, any disclosure, copying, distribution or any action
taken in reliance of this message is prohibited and may be unlawful. If you
receive this message by error, please notify the sender immediately and
delete all copies of this message.
---------------------------------------------------------------------------
|