The “cisco_link_*” traps are
from the agent on the Cisco box. They are not part of the status polling
done by NetView but independent notifications from the device software.
Leslie’s post is still accurate, NetView
does nothing with agent originated traps in it’s default state except to
pass them along for display. Unless you implement something to process
them that’s all there is.
In my system we have them set to “log
only” so they’re there if we need to reconstruct the history of
some failure but otherwise don’t find them useful. Our installation
only monitors the switches and not the devices beyond the switches. We
find the “cisco_link” traps are usually associated with
workstations when they are powered up and down.
We could use them in relation to our core
switches but in that case they’re not needed since we’re actively monitoring
the devices on the far side of our core links.
-----Original Message-----
From: owner-nv-l@lists.us.ibm.com
[mailto:owner-nv-l@lists.us.ibm.com] On
Behalf Of Alaa Farrag
Sent: Sunday, August
07, 2005 9:12 AM
To: The nv-l mailing list
Subject: [nv-l] cisco_link_down
and status polling
Is there any special action the
netview takes when it receives a cisco_link_down or a cisco_link_up trap
(status polling)?
I found the following old post by
Leslie Clark:
" Netview does not automatically do anything other than report, via the
Events Display, unsolicited traps from devices in the network. You are free to
customize those traps and do what you think is best."
I would like to know if this is
valid uptill now?