To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | Re: [nv-l] Event forwarding to TEC |
From: | James Shanks <jshanks@us.ibm.com> |
Date: | Wed, 25 Feb 2004 14:01:18 -0500 |
Delivery-date: | Wed, 25 Feb 2004 19:07:14 +0000 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
In-reply-to: | <OFDFA04190.4EF3DF78-ON85256E45.0058C727-85256E45.0059C2B7@mead.com> |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
The two are deliberately independent. "LOG ONLY" refers to the local event displays, while the ruleset controls what events are sent to TEC. Last time I checked, the only things the TEC ruleset gets from trapd.conf are the T/EC Event Class and the Slot Mappings. James Shanks Level 3 Support for Tivoli NetView for UNIX and Windows Tivoli Software / IBM Software Group
In the event configuration window, when you select log only should that not simply just log the event into the trapd.log and not display it or forward it to TEC? And does the "Do not forward" button on the event configuration page get overridden by the ruleset that is defined for forwarding to TEC? We have switch analyzer running and it is what is being used as the ruleset for forwarding to TEC. But some of the events in the ITSL2 event config page are still being sent to TEC even thoiugh they are set as "LOG ONLY" ANy Thoughts? Chris Petrina |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | [nv-l] Location.conf from the Map, Christopher J Petrina |
---|---|
Next by Date: | [nv-l] Node Deleted, reamd |
Previous by Thread: | [nv-l] Event forwarding to TEC, Christopher J Petrina |
Next by Thread: | [nv-l] Location.conf from the Map, Christopher J Petrina |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web