I have a IP SLA being tracking a primary interface of a remote 2951 router. When the the pings to 22.214.171.124 from the primary interface fail - it sends a UP->Down to the syslog buffer and then it triggers the Event Manager script and the backup interface comes up. And the opposite happens when the primary interface starts pinging 126.96.36.199 successfully.
The issue I was having was that when the primary interface was pinging to 188.8.131.52, every so often( like once a day) the ping would drop and it would trigger the Event Manager script - which would fail over to the backup and then quickly fail back to the primary but, the users would go down briefly. I had the tracking delay up and delay down set to 10 but, the frequency of the IP SLA set to 30. Now I have the frequency still set to 30 but I increased the tracking delay up and delay down to 180 - the max. I believe that will take care of the occassional ping lose.
This recovery time of 180 is a little long. The primary interface is connected to the VPN via a 50Mbs pipe. If I increased the IP SLA frequency to - say every second and decreased the tracking delay up and delay down to 10, first would it be taxing on the bandwidth and second, would the deleay down 10 delay up 10 be enough time for the occasional ping lose?
I used to run into this problem too when I was pinging networks outside of the ISP I was connected too.
To resolve this I started to ping the IP of the last HOP I had no control over such as the WAN interface connected to the PE (Provider edge layer 3 device) so if that link were to go down then I’m ok with the failover to go over the backup link. Pinging a remote site like 184.108.40.206, or 220.127.116.11 is great because they are well connected IP but at anytime they can go down but the internet be up.
Cisco recently announced availability of the latest release on the IOS-XE train – IOS-XE Gibraltar 17.4.1. This is a standard maintenance release supporting Switching, Wireless, SP-Access, Routing as well as IOT platforms with a sustaining support lifetim...
The primary purpose of a switch is to make forwarding decisions based on destination MAC address. The MAC address table is created with a list of destination MAC address for each connected device. In addition the switch port assigned and VLAN member...
Cisco Nexus 1000V cloud switch is a virtual appliance. It provides integration of physical and virtualized network infrastructure. Cisco Nexus 1000V switch is compatible with VMware ESX and vSphere (ESXi) hypervisors. There is a version for Microsoft Hype...
Selecting the proper lab training platform is fundamental to preparing for CCNA certification. Cisco CCNA is a foundational networking certification that requires knowledge of IOS configuration of multiple protocols. So where do you start and what lab tra...
(view in My Videos)
“Use Serviceability Features to Troubleshoot your Cat9K as a Cisco TAC Engineer”
This event took place on Tuesday 1st, December 2020 at 10hrs PDT
This event provides an introduction to the main Cat9K serviceability features. Serv...