i'm busting the link from r5 to eigrp 1...
r6#ping 1.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 8/23/40 ms
r6#
*Sep 1 15:58:50: %DUAL-5-NBRCHANGE: EIGRP-IPv4 1: Neighbor 172.16.2.2 (FastEthernet0/1) is down: holding time expired
r6#ping 1.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/12/20 ms
r6#
of course it can still get to 1.1.1.1...
r1#sh ip route | excl L | incl loop
Gateway of last resort is not set1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 1.1.1.0/24 is directly connected, Loopback1
6.0.0.0/24 is subnetted, 1 subnets
O E2 6.6.6.0 [110/20] via 10.1.1.2, 00:53:48, FastEthernet0/0
10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
C 10.1.1.0/24 is directly connected, FastEthernet0/0
C 10.1.2.0/24 is directly connected, FastEthernet1/1
172.16.0.0/24 is subnetted, 2 subnets
O E2 172.16.1.0 [110/20] via 10.1.1.2, 00:53:48, FastEthernet0/0
O E2 172.16.2.0 [110/20] via 10.1.1.2, 00:53:48, FastEthernet0/0
O IA 192.168.1.0/24 [110/782] via 10.1.1.2, 01:49:17, FastEthernet0/0
O IA 192.168.2.0/24 [110/782] via 10.1.2.2, 01:30:15, FastEthernet1/1
and the routing table didn't change... expected...
the path did, naturally...
Record route:
(172.16.1.1)
(192.168.1.2)
(10.1.1.2)
(10.1.1.1)
(10.1.1.1)
(192.168.1.1)
(172.16.1.2)
(172.16.1.1) <*>
but now it's keeping that path after r5's link is back... makes sense...
Record route:
(172.16.1.1)
(192.168.1.2)
(10.1.1.2)
(10.1.1.1)
(10.1.1.1)
(192.168.1.1)
(172.16.1.2)
(172.16.1.1) <*>
so i'll shut r4 down and get it back to what it was originally...
Record route:
(172.16.2.1)
(192.168.2.2)
(10.1.2.2)
(10.1.2.1)
(10.1.2.1)
(192.168.2.1)
(172.16.2.2)
(172.16.2.1) <*>
so it flipped the path, but will it return to the round trip it took in the previous post when r4 comes back?
Record route:
(172.16.2.1)
(192.168.2.2)
(10.1.2.2)
(10.1.2.1)
(10.1.2.1)
(192.168.2.1)
(172.16.2.2)
(172.16.2.1) <*>
nope... it's stuck in the new path...
r1#sh ip route 6.6.6.6
Routing entry for 6.6.6.0/24
Known via "ospf 1", distance 110, metric 20, type extern 2, forward metric 782
Last update from 10.1.1.2 on FastEthernet0/0, 00:04:26 ago
Routing Descriptor Blocks:
10.1.2.2, from 192.168.2.2, 00:20:59 ago, via FastEthernet1/1
Route metric is 20, traffic share count is 1
* 10.1.1.2, from 192.168.1.2, 00:04:26 ago, via FastEthernet0/0
Route metric is 20, traffic share count is 1
now change the metric-type on r4 to e1...
redist eigrp 1 sub metric-type 1
r1#sh ip route 6.6.6.6
Routing entry for 6.6.6.0/24
Known via "ospf 1", distance 110, metric 802, type extern 1
Last update from 10.1.1.2 on FastEthernet0/0, 00:00:18 ago
Routing Descriptor Blocks:
* 10.1.1.2, from 192.168.1.2, 00:00:18 ago, via FastEthernet0/0
Route metric is 802, traffic share count is 1
Record route:
(172.16.1.1)
(192.168.1.2)
(10.1.1.2)
(10.1.1.1)
(10.1.1.1)
(192.168.1.1)
(172.16.1.2)
(172.16.1.1) <*>
it now prefers the e1 path...
note that it rides on the one's (3rd octet)...
r1#sh ip route | excl L | incl loop
Gateway of last resort is not set1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 1.1.1.0/24 is directly connected, Loopback1
6.0.0.0/24 is subnetted, 1 subnets
O E1 6.6.6.0 [110/802] via 10.1.1.2, 00:06:33, FastEthernet0/0
10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
C 10.1.1.0/24 is directly connected, FastEthernet0/0
C 10.1.2.0/24 is directly connected, FastEthernet1/1
172.16.0.0/24 is subnetted, 2 subnets
O E2 172.16.1.0 [110/20] via 10.1.2.2, 00:34:46, FastEthernet1/1
O E1 172.16.2.0 [110/802] via 10.1.1.2, 00:06:33, FastEthernet0/0
O IA 192.168.1.0/24 [110/782] via 10.1.1.2, 02:31:18, FastEthernet0/0
O IA 192.168.2.0/24 [110/782] via 10.1.2.2, 02:12:16, FastEthernet1/1
No comments:
Post a Comment