RE: [nv-l] Rulesets and Trap Customization - gotcha

2002-10-30 09:10:01
Subject: RE: [nv-l] Rulesets and Trap Customization - gotcha
From: "Davis, Donald" <donald.davis AT firstcitizens DOT com>
To: "'Leslie Clark'" <lclark AT us.ibm DOT com>, nv-l AT lists.tivoli DOT com
Date: Wed, 30 Oct 2002 09:10:01 -0500

A word of advise ---
Here's what I have seen happen with custom trap definitions based on event source:
I have configured a special "service transition" trap definition for a Cisco Content Switch (ArrowPoint) based upon the event source of a single switch.

When a trap is received from this switch I need to page a specific person.
I created a ruleset like this:

STREAM --> TRAP --> Action

The trap setting is for the custom trap for just this one device.
I have placed this rule in ESE.automation.
What results is that the person got paged for all service transition traps from all of my ArrowPoints.

The event source in the custom trap definition seems to be ignored by the ruleset.

I have changed my ruleset to the following, which works:

STREAM --> TRAP --> Attribute --> Action

The Attribute checks $2 for the name of the switch.

Don Davis

-----Original Message-----
From: Leslie Clark [mailto:lclark AT us.ibm DOT com]
Sent: Tuesday, October 29, 2002 11:16 PM
To: nv-l AT lists.tivoli DOT com
Subject: Re: [nv-l] Ruleset for Router Down and Router Unreachable

Do you know that you can select more than one event in the Trap Settings
function? nvcorrd does the 'or' for you. And of course you can have lots of
branches coming from the initial 'Event Stream' cube. It will just check
all in succession, and stop processing on each branch as soon as something


Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking


                      Cliff [email protected]                                                                                      

                      ll.com                   To:       nv-l AT lists.tivoli DOT com                                               


                      10/28/2002 09:17         Subject:  [nv-l]  Ruleset for Router Down and Router Unreachable              




Has anyone developed a ruleset to test for both the router down or
router unreachable conditions?  We have had times when we get router
unreachable but no router down and vice versa but do not want to have
two different rulesets which would each send a page for different events
on the same outage.

Clifford L. Crane - Technical Consultant
Excel Corporation IT Business Continuation
151 N. Main Street
Wichita, KS  67201
Phone (316)291-2899   Fax (316)261-5902
cliff crane AT cargill DOT com

This electronic mail and any files transmitted with it are confidential and are intended solely for the use of individual or entity to whom they are addressed. If you are not the intended recipient or the person responsible for delivering the electronic mail to the intended recipient, be advised that you have received this electronic mail in error and that any use, dissemination, forwarding, printing, or copying of this electronic mail is strictly prohibited. If you have received this electronic mail in error, please immediately notify the sender by return mail.


<Prev in Thread] Current Thread [Next in Thread>
  • RE: [nv-l] Rulesets and Trap Customization - gotcha, Davis, Donald <=