it takes a very long time until PI (version 2.0) realizes that a switch is unavailable (around 5 minutes). In some cases, the affected device is up and running again and the NMS doesn't take a note about this. I already changed the Device Health Monitoring to poll the Device Availibility every 1 minute, but it doesn't fix this issue.
Furthermore, there is a heavy delay between the alert creation and sending the notification mail (around 20-30 minutes). And the next problem is, that a timestamp is missing inside the notification mail. So the network administrator get the mail with the "switch down"-alert which has been affected 30 minutes ago and you can't see when did that happen.
I hope we can correct this by any configuration changes...
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 ...