QUESTION:In Nexus 9300, if there exists no route to 184.108.40.206, why is it not using default route, but instead using route to device originating EIGRP redistributed route for 220.127.116.11?
SITUATION: In remote backup datacenter, in the ASA there exists a static EIGRP redistributed route that allows the network to reach a remote subnet over a site-to-site VPN: ip route outside 172.16.3.0 255.255.255.0 18.104.22.168.
OK, but the network does not know how to get to 22.214.171.124; thus, I conclude the network devices will use the default routes that lead to the local gateways, not the backup datacenter ASA. I conclude I would need to add a route to 126.96.36.199 that pointed to the backup datacenter ASA.
BUT the data is showing that the devices are actually routing as I want-- to the remote datacenter ASA.
9K1# sh ip route 0.0.0.0/0, ubest/mbest: 1/0 *via 172.16.200.5 !!THIS IS THE DEFAULT ROUTE (to a different device than 172.16.200.1) . IT IS NOT BEING USED FOR THIS ROUTING (THOUGH IT SHOULD BE (?)) !!
9K1# sh ip eigrp topo 172.16.3.0/24
IP-EIGRP (AS 1): Topology entry for 172.16.3.0/24 State is Passive, Query origin flag is 1, 1 Successor(s), FD is 1306368 Routing Descriptor Blocks: 172.16.200.1 (Vlan8), from 172.16.200.1, Send flag is 0x0 !! 172.16.200.1 IS THE PATH TO THE DATACENTER ASA. IT IS NOT THE PATH TO THE DEFAULT ROUTE. !! Composite metric is (1306368/1306112), Route is External Vector metric: Minimum bandwidth is 100000 Kbit Total delay is 50030 microseconds Reliability is 255/255 Load is 66/255 Minimum MTU is 1400 Hop count is 3 Internal tag is 0 External data: Originating router is 172.16.8.1 !! THIS IS THE BACKUP DATACENTER ASA. !! AS number of route is 0 External protocol is Static, external metric is 0 ---
QUESTION: In Nexus 9300, if there exists no route to 188.8.131.52, why is it not using default route, but instead using route to device originating EIGRP redistributed route for 184.108.40.206?