Have you tried doing an extended ping with the source of the ping as the loopback address of router B. You are not advertising the p2p 192.168.27.x networks - is there a route on C for B's 192.168.27.0/30 network ? If not and the ping goes out with a source of 192.168.27.2 then C does not how to get back.
Thanks for the help. I tried doing an extended ping with src as the loopback and that didn't work. Unless I was doing it wrong. I did however advertise the wan networks and that worked. Thanks for the help.
If you send an ping from router C it will have as source address 192.168.27.9. This address is unknown for router B. Try an extended ping to router B with source address loopback0 on router C. This should get an reply.
I think since the routers are advertising only their loopback addresses, RouterB doesn't know hot to get to RouterC's Serial interface therefore the next hope is unreachable (it has to use Router C's serial address to get to the loopback interface. on RouterA you should add next-hop self command for the neigbors. if you use that, the router will have valid next hop address
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...