One other thing to note :)

Cisco uses several flavors of link down traps - depending on what IOS
and what options you can receive this trap with anywhere from 2 - 6
variables. Is it possible that the field you are concerned with may not
be where you expect it?

There is a command to force the router to use static indexing on the
interfaces and a command to force it to use OSI compliant traps. I don't
do routers any more so the command escapes me but these are a couple of
caveats to link down traps from Cisco enterprise.

-----Original Message-----
From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT 
com]
On Behalf Of Paul
Sent: Tuesday, April 05, 2005 8:17 AM
To: nv-l AT lists.us.ibm DOT com
Subject: Re: [nv-l] Ruleset

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