The debug that you posted is only debug of ip routing and it does not give a full picture of what is going on. My guess is that at 08:24:57.437 your track reported that 126.96.36.199 was no longer reachable via the next hop through FastEthernet0 which results in withdrawal of the default route through that interface. Can you get a debug output that combines ip routing and of the track activity?
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...