Professional Documents
Culture Documents
So please make sure that your topology is fully working and pinging from PC-A to PC-C before you
come to next class. Router 1941 model and Switch 2960 are being used in this topology.
Server 1 PC 1
Following are the CLI command configuration details for R1, R2 and R3. [Please take note that these commands are review from your previous unit VU21988.]
Gateway of last resort is not set Gateway of last resort is not set Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks 10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks 10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks
C 10.1.1.0/30 is directly connected, Serial0/0/0 C 10.1.1.0/30 is directly connected, Serial0/0/0 O 10.1.1.0/30 [110/128] via 10.2.2.2, 01:19:45, Serial0/0/1
L 10.1.1.1/32 is directly connected, Serial0/0/0 L 10.1.1.2/32 is directly connected, Serial0/0/0 C 10.2.2.0/30 is directly connected, Serial0/0/1
O 10.2.2.0/30 [110/128] via 10.1.1.2, 01:17:34, Serial0/0/0 C 10.2.2.0/30 is directly connected, Serial0/0/1 L 10.2.2.1/32 is directly connected, Serial0/0/1
192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks L 10.2.2.2/32 is directly connected, Serial0/0/1 O 192.168.1.0/24 [110/129] via 10.2.2.2, 01:19:45, Serial0/0/1
C 192.168.1.0/24 is directly connected, GigabitEthernet0/1 O 192.168.1.0/24 [110/65] via 10.1.1.1, 01:19:18, Serial0/0/0 192.168.3.0/24 is variably subnetted, 2 subnets, 2 masks
L 192.168.1.1/32 is directly connected, GigabitEthernet0/1 O 192.168.3.0/24 [110/65] via 10.2.2.1, 01:19:18, Serial0/0/1 C 192.168.3.0/24 is directly connected, GigabitEthernet0/1
O 192.168.3.0/24 [110/129] via 10.1.1.2, 01:17:34, Serial0/0/0 L 192.168.3.1/32 is directly connected, GigabitEthernet0/1
R2#
R1# R3#
Following are the IP setup for PC-A and PC-C:
PC-A PC-C
Following are output of successful ping and reply between PC-A and PC-C and vice versa.
Pinging from PC-A (Server1) to PC-C (PC1) Pinging from PC-C (PC1) to PC-A (Server1)
NOTE: NOTE:
Make sure that PC-A (Server1) and ping PC-C (PC1) successfully. Make sure that PC-C (PC1) and ping PC-A (Server1) successfully.
Following is the output of “tracert” or tracing the route from PC-A to PC-C and vice versa.
Tracert from PC-A (Server1) to PC-C (PC1) Tracert from PC-C (PC1) to PC-A (Server1)
NOTE: NOTE:
While tracing the routes, take note of the hopping IP addresses or gateways. While tracing the routes, take note of the hopping IP addresses or gateways.