To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | Re: [nv-l] Ruleset |
From: | Paul <pstroud@bellsouth.net> |
Date: | Tue, 05 Apr 2005 09:16:32 -0400 |
Delivery-date: | Tue, 05 Apr 2005 14:16:18 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
In-reply-to: | <C353F42ACF29E240B9050B86F1852A4F0C273A@nlspm204.emea.corp.eds.com> |
References: | <C353F42ACF29E240B9050B86F1852A4F0C273A@nlspm204.emea.corp.eds.com> |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
User-agent: | Mozilla Thunderbird 1.0 (X11/20041206) |
David, You should be able to do this in a ruleset, make sure you are using the origin of the trap in the ruleset. For a netmon generated trap you would use $2(which is the failing node), but on an agent trap, you are going to want to use Origin(in the smartset rule node). However, you might find that the device is using an IP address that does not resolve to the hostname and this causes the SmartSet check to fail. This may be part of the problem but I cannot be sure. Paul Liu, David wrote: Dear list, I can use ruleset to exclude (filter) number of devices (smartset) from interface down event (NV internal trap 58916867), but not the Cisco_Link_down trap (generic 2, specific 0). Could anyone make a light for me? The strange thing is filter works, ruleset not. Regards, David Liu |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: [nv-l] nvcorrd restarts, Zoeckler, Eric A. |
---|---|
Next by Date: | RE: [nv-l] Ruleset, Barr, Scott |
Previous by Thread: | [nv-l] Ruleset, Liu, David |
Next by Thread: | RE: [nv-l] Ruleset, Barr, Scott |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web