[Top] [All Lists]

Re: [nv-l] ruleset in Unix

To: <nv-l@lists.us.ibm.com>
Subject: Re: [nv-l] ruleset in Unix
From: "Bill Evans" <wvevans@epix.net>
Date: Sat, 17 Apr 2004 11:56:30 -0400
Delivery-date: Sat, 17 Apr 2004 17:11:19 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
References: <OF7E27A035.BF39AE0B-ON65256E79.0011D3C2@dcmds.co.in>
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
With apologies to my friend James, he does take weekends off and some of us don't.  Everything he described applies but I doubt that either of us considered the case that all ports are not equal on a router until now.  To answer your follow-on question:
Slightly more steps involved for multi-port routers.  Yes, they're all multi-port but the interesting ones are those with one port on the NetView side and multiple ports facing the real world (aka network).  On those two port routers it's uninteresting because when the network facing port fails the router is "marginal" but effectively non-operational and when the NetView facing port is down we see both down and the transition from marginal to down is instantaneous.  For the general case we see:
1.Interface is down
2. router is marginal
2a. All  other interfaces go down.
3.router is down

and for up sequence

1.interface is up
2. router is marginal
2a. All other interfaces come up  
3. router is up
Your final paragraph describes a situation which shows interest in only one interface. 
That says just automate on the Interface DOWN for that one interface, Match the Interface UP for that interface and invoke an action node to send the mail if the match does not happen. on each of the input legs put a Trap node to select the two traps of interest and a node to verify if it's the interface you're interested in.  Atrribute or Smartset may be able to do the job with some research.  
Implementing that last node, picking the proper interface, may just be hard enough that it's worth feeding ALL traps from the router in question to a script (Action Node) and do the processing there. Rulesets are not that rich a progamming language. 
Bill Evans

----- Original Message -----
Sent: Friday, April 16, 2004 11:27 PM
Subject: Re: [nv-l] ruleset in Unix

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


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


                    James Shanks                                                                                      
                    <jshanks@us.ibm.c        To:     nv-l@lists.us.ibm.com                                            
                    om>                      cc:                                                                      
                    Sent by:                 Subject:     Re: [nv-l] ruleset in Unix                                  
                    04/15/2004 07:41                                                                                  
                    Please respond to                                                                                 

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
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

 Sent by: owner-nv-l@lists.us.ibm.com                                     
 04/15/2004 12:04 AM                                  m                   
             Please respond to                                     Subject
                   nv-l                               [nv-l] ruleset in   


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


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.

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web