Justin Freetage
2/14/15
Lab 5
TS1-6: IP ADDRESSING AND ROUTING
Table 1 IP Addressing Reference (Planned)
Device
Interface
IP Address
Mask
Default Gateway
R1
S/0/0/0
192.168.1.17
255.255.255.240
N/A

S0/0/1
192.168.1.97
255.255.255.240
N/A

Fa0/0
192.168.1.49
255.255.255.240
N/A
R2
S0/0/0
192.168.1.33
255.255.255.240
N/A

S0/0/1
192.168.1.18
255.255.255.240
N/A

Fa0/0
192.168.1.65
255.255.255.240
N/A
R3
S0/0/0
192.168.1.98
255.255.255.240
N/A

S0/0/1
192.168.1.34
255.255.255.240
N/A

Fa0/0
192.168.1.1
255.255.255.240
N/A
PC1
E0
192.168.1.62
255.255.255.240
192.168.1.49
PC2
E0
192.168.1.78
255.255.255.240
192.168.1.65
PC3
E0
192.168.1.14
255.255.255.240
192.168.1.1

Step 3: R1#ping 192.168.1.14 (PC3) did not work
Step 4: PC3 default gateway is wrong.
Step 5: All routers configurations are correct.
Step 6: R2>ping 192.168.1.14 (PC3) did not work All of the pings from R3 worked
Step 7: Tracing the route to 192.168.1.14 1 192.168.1.98 9msec 9msec 6msec
Step 8: 192.168.1.98 is assigned to R3’s S0/0/0 interface
Step 9: Yes
Step 10: R1#show ip route 192.168.1.14 Routing entry for 192.168.1.0/28 on Serial0/0/1
Step 11: S0/0/1 192.168.1.97
Step 12: C:\>ping 192.168.1.97 fails
Step 13: PC3 tracrt command show no successful routes.
Step 14: Physical Address. . . . . . . . . : 0200.0000.3333 IP Address . . . . . . . . . . . . : 192.168.1.14 Subnet Mask . . . . . . . . . . . : 255.255.255.240 Default Gateway . . . . . . . . . : 192.168.1.15 C:\>ping 192.168.1.15 failed
Step 15: No they are not the same. R3’s FastEthernet0/0 192.168.1.1 PC3’s Default Gateway 192.168.1.15
Step 18: R1-R3 link uses a PPP which advertises a /32 routes. The two /32 routes are R1’s S0/0/0 192.168.1.97 and R3’s S0/0/0 192.168.1.98
Step 19: The mask is configured to 255.255.255.224 instead of 255.255.255.240
Step 21: C:\>ping 192.168.1.78 works

Step 22: C:\>tracert 192.168.1.78 1 7ms 8ms 5ms 192.168.1.49 2 15ms 15ms 11ms 192.168.1.98 3 22ms 21ms 17ms 192.168.1.33 4 27ms 27ms 24ms 192.168.1.78
Step 23: R1# show ip route 192.168.1.78 192.168.1.98, on Serial0/0/1, which is on R3.
Step 24: Routing Information Sources: Gateway Distance Last Update 192.168.1.98 120 00:00:01
Step 26: Routing Information Sources: Gateway Distance Last Update 192.168.1.34 120 00:00:06 192.168.1.17 120 00:00:03
Step 27: Passive Interface(s): Serial0/0/1
Step 28: Passive-interface s0/0/1 Network 192.168.1.0
Table 2 Convenient Place to Record Root Causes and Solutions
1. PC3 default gateway has been set as 192.168.1.15 while on R3’s Fa0/0 interface has been set as 192.168.1.1.
Solution: Reconfigure PC3’s default gateway to match R3’s Fa0/0 interface.
2. R2’s Fa0/0 interface was configured with a mask of 255.255.255.224 but was planned with a mask of 255.255.255.240.
Solution: Reconfigure R2’s Fa0/0 interface to 192.168.1.65 255.255.255.240.
3. R2 has a passive-interface S0/0/1 configured. The command input tells this interface to not send any RIP updates through this interface.
Solution: Reconfigure R2’s RIP configurations with no passive-interface S0/0/1.

SB 3-1: EIGRP SERIAL CONFIGURATION I

Step 3: FastEthernet0/0 192.168.1.217 up up Serial0/0/1 192.168.1.210 up up
Step 5: It is the autonomous system number configured within R2.
Step 6: EIGRP is active on both Fa0/0 and S0/0/1.
Step 7: D 192.168.1.200/29 Serial0/0/1
Step 8: Interface Peers Un/Reliable SRTT Un/Reliable Flow Timer Routes Fa0/0 0 0/0 72 0/10 287 0 Se0/0/1 1 0/0 72 0/15 287 0
SB 3-2: EIGRP SERIAL CONFIGURATION II

Step 3: FastEthernet0/0 172.16.132.1 up up Serial0/0/1 192.168.82.10 up up
Step 4: Network 172.16.0.0 Network 192.168.82.0
Step 6: It is the autonomous system number configured within R2.
Step 7: Interface S0/0/1
Step 8: Interface Fa0/0
Step 10: D