is there a way to narrow the scope on the link down trap? i would like to be notified when "key" links such as network interconnects or servers go down without being deluged by traps when somebody powers off or moves a workstation. a method to select ports or interfaces that generate traps would be most useful. any ideas are appreciated.
This is possible. The default is to generate a trap for every port. You can switch it off as follows: interface FastEthernet0/1 no logging event link-status <-- disables event logging no snmp trap link-status <--disables the traps enter this on all lines in your config where traps & logging are not needed.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...