Refer to the exhibit. R1#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is 184.108.40.206 to network 0.0.0.0
D 220.127.116.11/24 [90/160000] via 18.104.22.168, 00:05:55, Ethernet1/0
22.214.171.124/24 is variably subnetted, 4 subnets, 2 masks
D 126.96.36.199/24 is summary, 00:05:55, Null0
C 188.8.131.52/32 is directly connected, Loopback1
C 184.108.40.206/32 is directly connected, Loopback2
C 220.127.116.11/32 is directly connected, Loopback20
18.104.22.168/27 is subnetted, 3 subnets
C 22.214.171.124 is directly connected, Ethernet1/0
C 126.96.36.199 is directly connected, Ethernet0/0
C 188.8.131.52 is directly connected, Ethernet2/0
D*EX 0.0.0.0/0 [170/2174976] via 184.108.40.206, 00:05:55, Ethernet0/0
[170/2174976] via 220.127.116.11, 00:05:55, Ethernet0/0
How would you confirm on R1 that load balancing is actually occurring on the default-network (0.0.0.0)?
Use ping and the show ip route command to confirm the timers for each default network resets to 0.
Load balancing does not occur over default networks; the second route will only be used for failover.
Use an extended ping along with repeated show ip route commands to confirm the gateway of last resort address toggles back and forth.
Use the traceroute command to an address that is not explicitly in the routing table.