CCIE Lab分解实验练习(Plannet_Practice_Labs)_.Vol_2(5)

ccie,java,安全,教程,文集,资料,工具书

0/24 [110/85] via 140.4.100.1, 00:00:49, Ethernet0 140.4.56.0/24 [110/20] via 140.4.68.6, 00:00:51, Serial0 140.4.65.0/24 [110/20] via 140.4.68.6, 00:00:51, Serial0
C C C
140.4.68.0/24 is directly connected, Serial0 140.4.88.0/24 is directly connected, Ethernet1 140.4.100.0/28 is directly connected, Ethernet0
O IA 140.4.113.0/24 [110/84] via 140.4.100.1, 00:00:51, Ethernet0
B B 199.36.36.0/24 [20/0] via 140.4.6.6, 01:08:35 211.1.1.0/24 [200/0] via 170.1.1.254, 01:10:17
O E2 192.168.0.0/22 [110/20] via 140.4.88.35, 00:00:51, Ethernet1
B 208.0.0.0/4 [200/0] via 140.4.35.35, 01:10:17 In order for CK8 to reach the 199.36.36.0 network, it is going to send the packet to the next hop, 140.4.6.6. For CK8 to reach the 140.4.6.6 address, it is going to send the packet to CK6's Serial 0 interface, 140.4.68.6. Let's look at CK6's routing table to see what it is going to do with the packet:
170.1.0.0/24 is subnetted, 1 subnets O E2 170.1.1.0 [110/20] via 140.4.68.8, 00:07:10, Serial0
140.4.0.0/16 is variably subnetted, 16 subnets, 2 masks ……
O IA O IA 140.4.35.0/24 [110/75] via 140.4.68.8, 00:07:11, Serial0 140.4.36.0/24 [110/149] via 140.4.68.8, 00:07:11, Serial0
Study Guide From
IT认证部落 CCIE-LAB
C C
C O IA O IA O IA B B
140.4.56.0/24 is directly connected, Ethernet0 140.4.65.0/24 is directly connected, BRI0
140.4.68.0/24 is directly connected, Serial0 140.4.88.0/24 [110/74] via 140.4.68.8, 00:07:12, Serial0 140.4.100.0/28 [110/74] via 140.4.68.8, 00:07:12, Serial0 140.4.113.0/24 [110/148] via 140.4.68.8, 00:07:12, Serial0 199.36.36.0/24 [200/0] via 140.4.36.36, 01:16:00 211.1.1.0/24 [20/0] via 140.4.8.8, 01:16:00
O E2 192.168.0.0/22 [110/20] via 140.4.68.8, 00:07:12, Serial0
B 208.0.0.0/4 [20/0] via 140.4.8.8, 01:16:00 Looking at CK6, we see that, in order for it to reach the 199.36.36.0 network, it is going to use the next hop 140.4.36.36, and for CK6 to reach 140.4.36.36 it is going to send the route back to CK8, 140.4.68.8. There is a loop when we shut down CK6's Frame interface; CK6, CK8, and CAT1 will not be able to reach the 199.36.36.36address when CK6's Frame is down.
To fix this problem, use Policy Routing on CK8. Instead of having CK8 send the packets destined for 199.36.36.36 to CK6, we are going to have it send them to CK1. CK1 will forward the packets to CK13, which will finally forward them to CAT2. The first thing we are going to do is to create our access list. The access list is going to permit any traffic that is destined for the 199.36.36.36 address. CK8: access-list 150 permit ip any host 199.36.36.36 We are then going to create the route map that will set the packets next hop on CK1's Ethernet interface. The route map is going to match the access list that we
have created and then set those packets that are destined for 199.36.36.36 to have a next hop of 140.4.100.1. CK8: route-map FORBGP permit 10
m