| To: | nv-l@lists.us.ibm.com |
|---|---|
| Subject: | Re: [nv-l] to handle traps |
| From: | James Shanks <jshanks@us.ibm.com> |
| Date: | Fri, 29 Oct 2004 11:20:04 -0400 |
| Delivery-date: | Fri, 29 Oct 2004 16:21:04 +0100 |
| Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
| In-reply-to: | <4182559D.3060406@alcatel.fr> |
| Reply-to: | nv-l@lists.us.ibm.com |
| Sender: | owner-nv-l@lists.us.ibm.com |
|
You'd write a ruleset to do that. Following on the suggestion by Francois, if your incoming trap has a specific id of, say 101, then you'd set that to "Log Only "in trapd.conf and kick off a script to issue a new trap with a new specific id that you make up yourself, say 201. You could use different numbers for the Up trap and the Down trap, and then write a ruleset using Trap Settings and Reset-On-Match to display just the ones you want. And you could override status there too. James Shanks Level 3 Support for Tivoli NetView for UNIX and Windows Tivoli Software / IBM Software Group |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [nv-l] Interface delete, James Shanks |
|---|---|
| Next by Date: | [nv-l] Master Map, Quinn, Bob |
| Previous by Thread: | Re: [nv-l] to handle traps, Gildas . Plouzennec |
| Next by Thread: | [nv-l] Master Map, Quinn, Bob |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web