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...
Join us live on Tuesday, March 9 at 10 am PT (and on demand after) as we take a closer look at the WAN architecture innovations that Cisco has to offer.
We'll take your questions live during the broadcast (and after), so post them below in the comments.
Hello everybody,I am newbies with setting cisco switch.I downloaded Catalyst 2960-X Switch Getting Started Guide but I can't access to Device Manager - Express Setup according to guide.If you follow the instructions and try to keep all LEDs (exc...
To participate in this event, please use the button to ask your questions
Ask questions from Monday, March 8 to Friday, March 19, 2021
All the knowledge of these four experts at your disposal!
Cisco Software-Defined Wide Area Network (SD-WAN) provid...
Community Live- ISR1100X-4G and ISR1100X-6G Platform Overview and Architecture
(Live event - Tuesday, 23 March, 2021 at 10:00 am Pacific/ 1:00 pm Eastern / 7:00 pm Paris)-
This event will have place on Tuesday 23rd, March 2021 at 10:00 hrs PDT&...