This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
flush timer. Total 1000 test ping packets. On average, 566.1 packets are received,
433.9 packets are lost. The convergence time is 867.8 seconds.
5.4 Discussion
The main goal is to examine the convergence behavior for OSPF, RIP and redistribution
between the two. First, we break the hub link to simulate an Ethernet failure. Ten
measurements are recorded for the three RIP timers cases. The result shows that the
amount of traffic loss during the OSPF convergence is very close in each of the cases
(14s in Section 5.1, 11.8s in Section 5.4.1.1, 11.6s in Section 5.4.2.1). This insensitive
variation to the RIP timer is expected.
Next, we loose the connection to the R2’s serial port to simulate a loss to the FR VC.
Once again, the RIP convergence time is about two minutes for the three different cases
(105.6s in Section 5.2, 119.8s in Section 5.4.1.2, 119.6 in Section 5.4.2.2). “Triggered
33
update”, a standard mechanism of RIP, causes an immediate update when any routing
changes is detected. Hence, the result is independent from the RIP timers.
Finally, we examine the convergence behavior of the redistribution between OSPF and
RIP. According to the experimental result, the convergence time is sensitive to the
setting of the RIP timers. Larger timer values cause a slower convergence, and vice
versa. The routing tables converge in 472s for the default timers. Decreasing these
values yields a faster convergence time (138.2s). Doubling these values result a slower
convergence time (8678.8s). For a company that has a dynamic network, it is
recommended to set the timers to smaller values to improve the convergence time.
34
6. Conclusions
Routing tables across the entire network should converge in minimum time in order to
avoid excessive traffic loss. This is the main interest of this project. We also discussed
IP addressing and the various components of the routing table. Next, we conducted an
experiment that examines the behavior of the routing protocols, RIP and OSPF. We
investigated the routing convergence under three different situations and concluded that
OSPF converges in about 10 seconds when there is a broken Ethernet connection, while
RIP converges in a minute when there is a failure FR VC.
We also observed that the RIP timers impact the RIP/OSPF redistribution convergence
behavior significantly. We recommend that a shorter RIP timers be programmed
whenever possible. Otherwise, the end devices (PC, work station or servers) should be
programmed with a longer idle time-out whenever the WAN connection involves a multi-
routing protocol because the convergence requires up to several hundred seconds.
35
7. References
[1] H. Benjamin and T. Thomas, Routing and Switching. Scottsdale, AZ: Coriolis, 2000, pp. 192-193. [2] A. Caslow, Cisco Certification: Bridges, Routers & Switches for CCIEs. Upper Saddle River, NJ: Prentice Hall PTR, 1998, pp. 373-410. [3] Certification Zone documentation on OSPF: http://www.certificationzone.com (14 Oct. 2001). [4] Cisco System, OSPF documentation: http://www.cisco.com/warp/public/104/1.html (14 Oct. 2001). [5] Cisco System, Introduction Cisco Router Configuration. Indianapolis, IN: Cisco Press, 1998. [6] L. Chappell, Advanced Cisco Router Configuration. Indianapolis, IN: Cisco Press, 1999, pp. 280-296. [7] J. Doyles, Routing TCP/IP, Vol. 1. Indianapolis, IN: Cisco Press, 1998, pp. 191-228. [8] B. Halabi, Internet Routing Architectures 2nd Edition. Indianapolis, IN: Cisco Press, 2000, pp. 57-64. [9] J. Moy, “OSPF Version 2,” RFC 2328, Apr. 1998: http://www.ietf.org/rfc/rfc2328.txt (14 Oct. 2001). [10] M. Saterlee and S. Hutnik, Cisco CCIE All-in-One Lab Study Guide. New York, NY: Oracle Press, 1999, pp. 456-461. [11] J. Walrand and P. Varaiya, High-Performance Communication Networks. San Francisco, CA: Morgan Kaufmann Publisher, 2000, pp. 163-165.
36
Appendix A
Code Listing
The configurations of a Cisco router are divided into different sections. Lines that follow
the “interface” command (e.g., “interface serial 1”) are the configuration for that
particular interface. Lines that follow the “router ospf” or “router rip” commands are the
settings for the OSPF and RIP protocols.
Interface Commands:
“encapsulation frame-relay” – use Frame Relay as a layer 2 protocol to encapsulate the
packets
“ip address 1.1.1.1” – set the IP address for that particular interface
“frame-relay interface-dlci 102” – use FR VC 102 for that interface
“frame-relay traffic-rate 128000” – set the bandwidth for the specified VC to be 128kbps
“no keepalive” – assume the link is always operational without sending any keepalive
Routing Protocol Commands:
“timers basic 60 360 360 480” – set the RIP timers
“redistribute ospf 7” – redistribute OSPF process 7 into RIP
“network 4.0.0.0” – include interfaces with IP address 4.0.0.0 to 4.255.255.255 to RIP
“network 192.168.1.0 0.0.0.255 area 0” – include all the interfaces with IP address
between 192.168.1.0 to 192.168.1.255 to OSPF’s Area 0
37
Cisco routers have empty configurations originally. We configured the routers such that
they are suitable for the needs of this network protocol convergence project. The
configurations of the seven Cisco routers plus the Frame Relay Switch that produce the
experiment result are listed. Lines begin with an “!” denote comments.
Router FR ! This router behaves like a FR switch. ! There are two PVCs, one from R1 to R2 and one from R1 to R3. ! Enable this router to be a FR switch frame-relay switching ! Connected to the main site R1 ! One PVC to R2 and another PVC to R3 interface Serial1 encapsulation frame-relay clockrate 64000 frame-relay intf-type dce frame-relay route 102 interface Serial2 201 frame-relay route 103 interface Serial3 301 ! Connected to the site R2 with a PVC to R1 interface Serial2 encapsulation frame-relay clockrate 64000 frame-relay intf-type dce frame-relay route 201 interface Serial1 102 ! Connected to the site R3 with a PVC to R1 interface Serial3 encapsulation frame-relay clockrate 64000 frame-relay intf-type dce frame-relay route 301 interface Serial1 103
38
Router R1
! this is the main office’s routers and connect between the ATM network and the FR network ! Loopback interface for management purpose interface Loopback0 ip address 1.1.1.1 255.255.255.0 ! connected to the fully-meshed ATM link interface Ethernet0 ip address 10.1.1.1 255.255.255.0 ! FR interfaces; One 128k VC to R2 and one 256k VC to R3 interface Serial0 ip address 192.168.1.1 255.255.255.0 encapsulation frame-relay ip ospf network point-to-multipoint frame-relay traffic-shaping frame-relay interface-dlci 102 class VC_128k frame-relay interface-dlci 103 class VC_256k ! OSPF process; FR interface is in Area 0; ATM interface is in Area 1 ! Perform summarization of IP address for network 67.1.0.0/16 and 192.168.1.0/24 router ospf 7 redistribute connected subnets route-map loopback network 10.1.1.0 0.0.0.255 area 1 network 192.168.1.0 0.0.0.255 area 0 area 0 range 192.168.1.0 255.255.255.0 area 1 range 67.1.0.0 255.255.0.0 ! access-list and route-map for redistributing the loopback interface to the OSPF routing process ip access-list standard loopback permit 1.1.1.0 0.0.0.255 route-map loopback permit 10 match ip address loopback ! Traffic Shaping the FR VC to the desired Bandwidth map-class frame-relay VC_128k frame-relay traffic-rate 128000 map-class frame-relay VC_256k frame-relay traffic-rate 256000
39
Router R2 ! R2 is a leg for the FR site. It also connects to ISP#2 using a T1 link. ! Loopback interface for management purpose interface Loopback0 ip address 2.2.2.2 255.255.255.0 ! FR interfaces; 128k VC to R1 interface Serial0 ip address 192.168.1.2 255.255.255.0 encapsulation frame-relay ip ospf network point-to-multipoint frame-relay traffic-shaping frame-relay class VC_128k ! T1 connection to ISP#2 interface Serial1 ip address 172.16.1.2 255.255.255.0 ! OSPF Routing process; FR interface is in Area 0 ! Redistributing between the RIP and OSPF ! ISP#2 (RIP)’s ntwk that is redistruted back to OSPF would have AD=152 router ospf 7 redistribute connected subnets route-map loopback redistribute rip subnets network 192.168.1.0 0.0.0.255 area 0 distance 152 0.0.0.0 255.255.255.255 3 ! RIP routing process for the S1 Interface ! Also, change the timers and redistributed from the OSPF process. ! The OSPF network that is redistrubuted to RIP would have AD=153 router rip timers basic 60 360 360 480 redistribute connected metric 10 route-map loopback redistribute ospf 7 network 172.16.0.0 default-metric 7 distance 152 0.0.0.0 255.255.255.255 7 ! access-list and route-map for redistributing the loopback interface to the OSPF routing process ip access-list standard loopback permit 2.2.2.0 0.0.0.255 route-map loopback permit 10 match ip address loopback ! Traffic Shaping the FR VC to the desired Bandwidth map-class frame-relay VC_128k
40
frame-relay traffic-rate 128000 no frame-relay adaptive-shaping ! Access List that consists of the RIP network ! For redistributing between OSPF and RIP access-list 3 permit 4.0.0.0 0.255.255.255 access-list 3 permit 172.16.0.0 0.0.255.255 access-list 3 permit 208.1.1.0 0.0.0.255 access-list 3 permit 5.0.0.0 0.0.0.255 access-list 3 permit 137.1.0.0 0.0.255.255 ! Access List that consists of the RIP network ! For redistributing between OSPF and RIP access-list 7 permit 1.1.1.0 0.0.0.255 access-list 7 permit 2.2.2.0 0.0.0.255 access-list 7 permit 3.3.3.0 0.0.0.255 access-list 7 permit 6.6.6.0 0.0.0.255 access-list 7 permit 7.7.7.0 0.0.0.255 access-list 7 permit 10.1.1.0 0.0.0.255 access-list 7 permit 12.1.1.0 0.0.0.255 access-list 7 permit 67.1.6.0 0.0.0.255 access-list 7 permit 67.1.7.0 0.0.0.255 access-list 7 permit 192.168.1.0 0.0.0.255 Router R3 ! R3 is a leg for the FR site. It also connects to ISP#2 using a Ethernet link. ! Loopback interface for management purpose interface Loopback0 ip address 3.3.3.3 255.255.255.0 ! Ethernet connection to ISP#2 interface Ethernet0 ip address 137.1.1.3 255.255.255.0 ! FR interfaces; 128k VC to R1 interface Serial0 ip address 192.168.1.3 255.255.255.0 encapsulation frame-relay ip ospf network point-to-multipoint frame-relay traffic-shaping frame-relay class VC_256k ! OSPF Routing process; FR interface is in Area 0 ! Redistributing between the RIP and OSPF ! ISP#2 (RIP)’s ntwk that is redistruted back to OSPF would have AD=153 router ospf 7
41
redistribute connected subnets route-map loopback redistribute rip network 192.168.1.0 0.0.0.255 area 0 distance 153 0.0.0.0 255.255.255.255 3 ! RIP routing process for the E0 Interface ! Also, change the timers and redistributed from the OSPF process. ! The OSPF network that is redistrubuted to RIP would have AD=153 router rip timers basic 60 360 360 480 redistribute connected route-map loopback redistribute ospf 7 network 137.1.0.0 default-metric 3 distance 153 0.0.0.0 255.255.255.255 7 ! access-list and route-map for redistributing the loopback interface to the OSPF routing process ip access-list standard loopback permit 3.3.3.0 0.0.0.255 route-map loopback permit 10 match ip address loopback ! Traffic Shaping the FR VC to the desired Bandwidth map-class frame-relay VC_256k frame-relay traffic-rate 256000 no frame-relay adaptive-shaping ! Access List that consists of the RIP network ! For redistributing between OSPF and RIP access-list 3 permit 4.0.0.0 0.255.255.255 access-list 3 permit 172.16.0.0 0.0.255.255 access-list 3 permit 208.1.1.0 0.0.0.255 access-list 3 permit 5.0.0.0 0.0.0.255 access-list 3 permit 137.1.0.0 0.0.255.255 ! Access List that consists of the OSPF network ! For redistributing between OSPF and RIP access-list 7 permit 1.1.1.0 0.0.0.255 access-list 7 permit 2.2.2.0 0.0.0.255 access-list 7 permit 3.3.3.0 0.0.0.255 access-list 7 permit 6.6.6.0 0.0.0.255 access-list 7 permit 7.7.7.0 0.0.0.255 access-list 7 permit 10.1.1.0 0.0.0.255 access-list 7 permit 12.1.1.0 0.0.0.255 access-list 7 permit 67.1.6.0 0.0.0.255 access-list 7 permit 67.1.7.0 0.0.0.255 access-list 7 permit 192.168.1.0 0.0.0.255
42
Router R4 ! R4 located inside ISP#2. The interconnection between the ISP#2 is a T1 link. ! It also connects to ISP#1 R2 with a T1 link. ! Loopback interface for management purpose interface Loopback0 ip address 4.4.4.4 255.255.255.0 ! T1 connection between ISP#2 interface Serial0 ip address 208.1.1.4 255.255.255.0 clockrate 64000 ! T1 connection to ISP#1 interface Serial1 ip address 172.16.1.4 255.255.255.0 clockrate 64000 ! RIP routing process for all interfaces ! Also, change the timers router rip timers basic 60 360 360 480 network 4.0.0.0 network 172.16.0.0 network 208.1.1.0 Router R5 ! R5 located inside ISP#2. The interconnection between the ISP#2 is a T1 link. ! It also connects to ISP#1 R3 with an Ethernet link. ! Loopback interface for management purpose interface Loopback0 ip address 5.5.5.5 255.255.255.0 ! Ethernet connection to ISP#1 interface Ethernet0 ip address 137.1.1.5 255.255.255.0 ! T1 connection between ISP#2 interface Serial0 ip address 208.1.1.5 255.255.255.0 ! RIP routing process for all interfaces ! Also, change the timers router rip
43
timers basic 60 360 360 480 network 137.1.0.0 network 5.0.0.0 network 208.1.1.0 Router R6 ! This is a leg of the fully-meshed ATM link. ! It also has a connection to the other ATM site by an ethernet link. ! Loopback interface for management purpose interface Loopback0 ip address 6.6.6.6 255.255.255.0 ! connected to the fully-meshed ATM link interface Ethernet0 ip address 10.1.1.6 255.255.255.0 ! direct connection between the two ATM sites interface Ethernet1 ip address 12.1.1.6 255.255.255.0 ! user can be located on this ethernet interface interface Ethernet2 ip address 67.1.6.6 255.255.255.0 no keepalive ! OSPF process; all interfaces are in Area 1 router ospf 7 redistribute connected subnets route-map loopback network 12.1.1.0 0.0.0.255 area 1 network 10.1.1.0 0.0.0.255 area 1 network 67.1.6.0 0.0.0.255 area 1 ! access-list and route-map for redistributing the loopback interface to the OSPF routing process ip access-list standard loopback permit 6.6.6.0 0.0.0.255 route-map loopback permit 10 match ip address loopback
44
Router R7 ! This is a leg of the fully-meshed ATM link. ! It also has a connection to the other ATM site by an ethernet link. ! Loopback interface for management purpose interface Loopback0 ip address 7.7.7.7 255.255.255.0 ! connected to the fully-meshed ATM link interface Ethernet0/0 ip address 10.1.1.7 255.255.255.0 ! direct connection between the two ATM sites interface Ethernet0/1 ip address 12.1.1.7 255.255.255.0 ! user can be located on this ethernet interface interface Ethernet1/0 ip address 67.1.7.7 255.255.255.0 no keepalive ! OSPF process; all interfaces are in Area 1 router ospf 7 redistribute connected subnets route-map loopback network 10.1.1.0 0.0.0.255 area 1 network 12.1.1.0 0.0.0.255 area 1 network 67.1.7.0 0.0.0.255 area 1 ! access-list and route-map for redistributing the loopback interface to the OSPF routing process ip access-list standard loopback permit 7.7.7.0 0.0.0.255 route-map loopback permit 10 match ip address loopback
45
Appendix B
Routing Tables
The routing table of the routers with all links operational are listed in this section. Router R1 1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 1.0.0.0/8 [110/123] via 192.168.1.2, 00:00:52, Serial0 C 1.1.1.0/24 is directly connected, Loopback0 O E2 137.1.0.0/16 [110/123] via 192.168.1.2, 00:00:52, Serial0 2.0.0.0/24 is subnetted, 1 subnets O E2 2.2.2.0 [110/20] via 192.168.1.2, 00:00:52, Serial0 3.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 3.0.0.0/8 [110/123] via 192.168.1.2, 00:00:52, Serial0 O E2 3.3.3.0/24 [110/20] via 192.168.1.3, 00:00:52, Serial0 O E2 4.0.0.0/8 [110/123] via 192.168.1.2, 00:00:52, Serial0 O E2 5.0.0.0/8 [110/123] via 192.168.1.2, 00:00:52, Serial0 6.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 6.6.6.0/24 [110/20] via 10.1.1.6, 00:00:52, Ethernet0 O E2 6.0.0.0/8 [110/123] via 192.168.1.2, 00:00:52, Serial0 O E2 172.16.0.0/16 [110/321] via 192.168.1.3, 00:00:53, Serial0 67.0.0.0/8 is variably subnetted, 3 subnets, 2 masks O E2 67.0.0.0/8 [110/123] via 192.168.1.2, 00:00:53, Serial0 O 67.1.6.0/24 [110/20] via 10.1.1.6, 00:00:53, Ethernet0 O 67.1.7.0/24 [110/20] via 10.1.1.7, 00:00:53, Ethernet0 7.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 7.7.7.0/24 [110/20] via 10.1.1.7, 00:00:53, Ethernet0 O E2 7.0.0.0/8 [110/123] via 192.168.1.2, 00:00:53, Serial0 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 10.0.0.0/8 [110/123] via 192.168.1.2, 00:00:53, Serial0 C 10.1.1.0/24 is directly connected, Ethernet0 O E2 208.1.1.0/24 [110/123] via 192.168.1.2, 00:00:53, Serial0 12.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O 12.1.1.0/24 [110/20] via 10.1.1.6, 00:00:53, Ethernet0 [110/20] via 10.1.1.7, 00:00:53, Ethernet0 O E2 12.0.0.0/8 [110/123] via 192.168.1.2, 00:00:53, Serial0 192.168.1.0/24 is variably subnetted, 3 subnets, 2 masks C 192.168.1.0/24 is directly connected, Serial0 O 192.168.1.3/32 [110/64] via 192.168.1.3, 00:12:27, Serial0 O 192.168.1.2/32 [110/64] via 192.168.1.2, 00:12:27, Serial0
46
Router R2 1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 1.1.1.0/24 [110/20] via 192.168.1.1, 00:00:57, Serial0 R 1.0.0.0/8 [120/5] via 172.16.1.4, 00:00:06, Serial1 R 137.1.0.0/16 [120/2] via 172.16.1.4, 00:00:06, Serial1 2.0.0.0/24 is subnetted, 1 subnets C 2.2.2.0 is directly connected, Loopback0 3.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 3.3.3.0/24 [110/20] via 192.168.1.1, 00:00:57, Serial0 R 3.0.0.0/8 [120/5] via 172.16.1.4, 00:00:07, Serial1 R 4.0.0.0/8 [120/1] via 172.16.1.4, 00:00:07, Serial1 R 5.0.0.0/8 [120/2] via 172.16.1.4, 00:00:07, Serial1 6.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 6.6.6.0/24 [110/20] via 192.168.1.1, 00:00:57, Serial0 R 6.0.0.0/8 [120/5] via 172.16.1.4, 00:00:07, Serial1 172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks O E2 172.16.0.0/16 [152/321] via 192.168.1.1, 00:00:58, Serial0 C 172.16.1.0/24 is directly connected, Serial1 67.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O IA 67.1.0.0/16 [110/84] via 192.168.1.1, 00:00:58, Serial0 R 67.0.0.0/8 [120/5] via 172.16.1.4, 00:00:07, Serial1 7.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 7.7.7.0/24 [110/20] via 192.168.1.1, 00:00:58, Serial0 R 7.0.0.0/8 [120/5] via 172.16.1.4, 00:00:07, Serial1 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O IA 10.1.1.0/24 [110/74] via 192.168.1.1, 00:00:53, Serial0 R 10.0.0.0/8 [120/5] via 172.16.1.4, 00:00:07, Serial1 R 208.1.1.0/24 [120/1] via 172.16.1.4, 00:00:07, Serial1 12.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O IA 12.1.1.0/24 [110/84] via 192.168.1.1, 00:00:58, Serial0 R 12.0.0.0/8 [120/5] via 172.16.1.4, 00:00:07, Serial1 192.168.1.0/24 is variably subnetted, 3 subnets, 2 masks O 192.168.1.1/32 [110/64] via 192.168.1.1, 00:12:37, Serial0 C 192.168.1.0/24 is directly connected, Serial0 O 192.168.1.3/32 [110/128] via 192.168.1.1, 00:12:37, Serial0
47
Router R3 1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 1.0.0.0/8 [110/123] via 192.168.1.1, 00:01:05, Serial0 O E2 1.1.1.0/24 [110/20] via 192.168.1.1, 00:01:05, Serial0 137.1.0.0/16 is variably subnetted, 2 subnets, 2 masks O E2 137.1.0.0/16 [153/123] via 192.168.1.1, 00:01:05, Serial0 C 137.1.1.0/24 is directly connected, Ethernet0 2.0.0.0/24 is subnetted, 1 subnets O E2 2.2.2.0 [110/20] via 192.168.1.1, 00:01:05, Serial0 3.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 3.0.0.0/8 [110/123] via 192.168.1.1, 00:01:05, Serial0 C 3.3.3.0/24 is directly connected, Loopback0 R 4.0.0.0/8 [120/2] via 137.1.1.5, 00:00:57, Ethernet0 R 5.0.0.0/8 [120/1] via 137.1.1.5, 00:00:57, Ethernet0 6.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 6.6.6.0/24 [110/20] via 192.168.1.1, 00:01:05, Serial0 O E2 6.0.0.0/8 [110/123] via 192.168.1.1, 00:01:05, Serial0 R 172.16.0.0/16 [120/2] via 137.1.1.5, 00:00:57, Ethernet0 67.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O IA 67.1.0.0/16 [110/84] via 192.168.1.1, 00:01:05, Serial0 O E2 67.0.0.0/8 [110/123] via 192.168.1.1, 00:01:05, Serial0 7.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 7.7.7.0/24 [110/20] via 192.168.1.1, 00:01:05, Serial0 O E2 7.0.0.0/8 [110/123] via 192.168.1.1, 00:01:05, Serial0 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O IA 10.1.1.0/24 [110/74] via 192.168.1.1, 00:01:05, Serial0 O E2 10.0.0.0/8 [110/123] via 192.168.1.1, 00:01:05, Serial0 R 208.1.1.0/24 [120/1] via 137.1.1.5, 00:00:57, Ethernet0 12.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O IA 12.1.1.0/24 [110/84] via 192.168.1.1, 00:01:05, Serial0 O E2 12.0.0.0/8 [110/123] via 192.168.1.1, 00:01:05, Serial0 192.168.1.0/24 is variably subnetted, 3 subnets, 2 masks O 192.168.1.1/32 [110/64] via 192.168.1.1, 00:12:44, Serial0 C 192.168.1.0/24 is directly connected, Serial0 O 192.168.1.2/32 [110/128] via 192.168.1.1, 00:12:44, Serial0
48
Router R4 R 1.0.0.0/8 [120/4] via 208.1.1.5, 00:00:12, Serial0 R 137.1.0.0/16 [120/1] via 208.1.1.5, 00:00:12, Serial0 R 2.0.0.0/8 [120/4] via 208.1.1.5, 00:00:12, Serial0 R 3.0.0.0/8 [120/4] via 208.1.1.5, 00:00:12, Serial0 4.0.0.0/24 is subnetted, 1 subnets C 4.4.4.0 is directly connected, Loopback0 R 5.0.0.0/8 [120/1] via 208.1.1.5, 00:00:12, Serial0 R 6.0.0.0/8 [120/4] via 208.1.1.5, 00:00:12, Serial0 172.16.0.0/24 is subnetted, 1 subnets C 172.16.1.0 is directly connected, Serial1 R 67.0.0.0/8 [120/4] via 208.1.1.5, 00:00:12, Serial0 R 7.0.0.0/8 [120/4] via 208.1.1.5, 00:00:12, Serial0 R 10.0.0.0/8 [120/4] via 208.1.1.5, 00:00:12, Serial0 C 208.1.1.0/24 is directly connected, Serial0 R 12.0.0.0/8 [120/4] via 208.1.1.5, 00:00:14, Serial0 R 192.168.1.0/24 [120/4] via 208.1.1.5, 00:00:14, Serial0 Router R5 R 1.0.0.0/8 [120/3] via 137.1.1.3, 00:00:47, Ethernet0 R 2.0.0.0/8 [120/3] via 137.1.1.3, 00:00:47, Ethernet0 R 3.0.0.0/8 [120/3] via 137.1.1.3, 00:00:47, Ethernet0 R 4.0.0.0/8 [120/1] via 208.1.1.4, 00:00:36, Serial0 5.0.0.0/24 is subnetted, 1 subnets C 5.5.5.0 is directly connected, Loopback0 R 6.0.0.0/8 [120/3] via 137.1.1.3, 00:00:48, Ethernet0 R 7.0.0.0/8 [120/3] via 137.1.1.3, 00:00:48, Ethernet0 R 10.0.0.0/8 [120/3] via 137.1.1.3, 00:00:48, Ethernet0 R 12.0.0.0/8 [120/3] via 137.1.1.3, 00:00:48, Ethernet0 R 67.0.0.0/8 [120/3] via 137.1.1.3, 00:00:48, Ethernet0 R 192.168.1.0/24 [120/3] via 137.1.1.3, 00:00:48, Ethernet0 137.1.0.0/24 is subnetted, 1 subnets C 137.1.1.0 is directly connected, Ethernet0 R 172.16.0.0/16 [120/1] via 208.1.1.4, 00:00:37, Serial0 C 208.1.1.0/24 is directly connected, Serial0
49
Router R6 1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 1.1.1.0/24 [110/20] via 10.1.1.1, 00:01:37, Ethernet0 O E2 1.0.0.0/8 [110/123] via 10.1.1.1, 00:01:37, Ethernet0 2.0.0.0/24 is subnetted, 1 subnets O E2 2.2.2.0 [110/20] via 10.1.1.1, 00:01:37, Ethernet0 3.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 3.3.3.0/24 [110/20] via 10.1.1.1, 00:01:37, Ethernet0 O E2 3.0.0.0/8 [110/123] via 10.1.1.1, 00:01:37, Ethernet0 O E2 4.0.0.0/8 [110/123] via 10.1.1.1, 00:01:37, Ethernet0 O E2 5.0.0.0/8 [110/123] via 10.1.1.1, 00:01:37, Ethernet0 6.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 6.0.0.0/8 [110/123] via 10.1.1.1, 00:01:37, Ethernet0 C 6.6.6.0/24 is directly connected, Loopback0 7.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 7.0.0.0/8 [110/123] via 10.1.1.1, 00:01:37, Ethernet0 O E2 7.7.7.0/24 [110/20] via 12.1.1.7, 00:01:37, Ethernet1 [110/20] via 10.1.1.7, 00:01:37, Ethernet0 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 10.0.0.0/8 [110/123] via 10.1.1.1, 00:01:37, Ethernet0 C 10.1.1.0/24 is directly connected, Ethernet0 12.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 12.0.0.0/8 [110/123] via 10.1.1.1, 00:01:37, Ethernet0 C 12.1.1.0/24 is directly connected, Ethernet1 67.0.0.0/8 is variably subnetted, 3 subnets, 2 masks O E2 67.0.0.0/8 [110/123] via 10.1.1.1, 00:01:37, Ethernet0 C 67.1.6.0/24 is directly connected, Ethernet2 O 67.1.7.0/24 [110/20] via 12.1.1.7, 00:01:37, Ethernet1 [110/20] via 10.1.1.7, 00:01:37, Ethernet0 O IA 192.168.1.0/24 [110/10] via 10.1.1.1, 00:01:37, Ethernet0 O E2 137.1.0.0/16 [110/123] via 10.1.1.1, 00:01:37, Ethernet0 O E2 172.16.0.0/16 [110/321] via 10.1.1.1, 00:01:37, Ethernet0 O E2 208.1.1.0/24 [110/123] via 10.1.1.1, 00:01:37, Ethernet0
50
Router R7 1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 1.1.1.0/24 [110/20] via 10.1.1.1, 00:01:42, Ethernet0/0 O E2 1.0.0.0/8 [110/123] via 10.1.1.1, 00:01:42, Ethernet0/0 O E2 137.1.0.0/16 [110/123] via 10.1.1.1, 00:01:42, Ethernet0/0 2.0.0.0/24 is subnetted, 1 subnets O E2 2.2.2.0 [110/20] via 10.1.1.1, 00:01:42, Ethernet0/0 3.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 3.3.3.0/24 [110/20] via 10.1.1.1, 00:01:42, Ethernet0/0 O E2 3.0.0.0/8 [110/123] via 10.1.1.1, 00:01:42, Ethernet0/0 O E2 4.0.0.0/8 [110/123] via 10.1.1.1, 00:01:42, Ethernet0/0 O E2 5.0.0.0/8 [110/123] via 10.1.1.1, 00:01:42, Ethernet0/0 6.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 6.0.0.0/8 [110/123] via 10.1.1.1, 00:01:42, Ethernet0/0 O E2 6.6.6.0/24 [110/20] via 12.1.1.6, 00:01:42, Ethernet0/1 [110/20] via 10.1.1.6, 00:01:42, Ethernet0/0 O E2 172.16.0.0/16 [110/321] via 10.1.1.1, 00:01:43, Ethernet0/0 67.0.0.0/8 is variably subnetted, 3 subnets, 2 masks O E2 67.0.0.0/8 [110/123] via 10.1.1.1, 00:01:43, Ethernet0/0 O 67.1.6.0/24 [110/20] via 12.1.1.6, 00:01:43, Ethernet0/1 [110/20] via 10.1.1.6, 00:01:43, Ethernet0/0 C 67.1.7.0/24 is directly connected, Ethernet1/0 7.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 7.0.0.0/8 [110/123] via 10.1.1.1, 00:01:43, Ethernet0/0 C 7.7.7.0/24 is directly connected, Loopback0 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 10.0.0.0/8 [110/123] via 10.1.1.1, 00:01:43, Ethernet0/0 C 10.1.1.0/24 is directly connected, Ethernet0/0 O E2 208.1.1.0/24 [110/123] via 10.1.1.1, 00:01:43, Ethernet0/0 12.0.0.0/8 is variably subnetted, 2 subnets, 2 masks O E2 12.0.0.0/8 [110/123] via 10.1.1.1, 00:01:43, Ethernet0/0 C 12.1.1.0/24 is directly connected, Ethernet0/1 O IA 192.168.1.0/24 [110/10] via 10.1.1.1, 00:01:43, Ethernet0/0