I had setup a static route in a complex network to influence the path it would take. I decided to use the loopback address of the destination router (which is 2-3 hops away), not the next hop. It was by complete accident that I did this (but seemed logical to me at the time) - I was at a customer site and was completely burned out on the project. It worked, but on my way home I started to think about what I did and questioned how this even worked.
I also wanted to add that they are using an IGP, so there is full reachability throughout the WAN. Now, from all my studies and everything I read, the only two ways this is supposed to work is by pointing your destination prefix and prefix mask to the "next-hop" or "exit interface"
I am guessing it worked because it couldn't validate the loopback address. I am curious if anyone has more insight as to why it worked, and if I am going to experience any unforseen issues with this configuration in the future.
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...