Tuesday, 5 June 2012
DLS0#traceroute 166.56.1.1
Type escape sequence to abort.
Tracing the route to 166.56.1.1
1 10.0.0.2 16 msec 4 msec 31 msec
2 192.17.5.1 32 msec 33 msec 17 msec
3 160.45.34.1 78 msec 37 msec 50 msec
4 166.56.1.1 49 msec 97 msec 94 msec
DLS0#traceroute 192.168.101.1
Type escape sequence to abort.
Tracing the route to 192.168.101.1
1 192.168.101.1 32 msec 16 msec 31 msec
DLS0#ping
Protocol [ip]:
Target IP address: 166.56.1.1
Repeat count [5]: 50
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 192.168.101.2
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 50, 100-byte ICMP Echos to 166.56.1.1, timeout is 2 seconds:
Packet sent with a source address of 192.168.101.2
!!!!!!!!!!!!!!!!!!!!!!!!!.........................
Success rate is 50 percent (25/50), round-trip min/avg/max = 19/44/78 ms
DLS0#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is not set
10.0.0.0/24 is subnetted, 1 subnets
C 10.0.0.0 is directly connected, Port-channel 2
16.0.0.0/24 is subnetted, 2 subnets
R 16.16.20.0 [120/7] via 10.0.0.2, 00:00:28, Port-channel 2
R 16.16.30.0 [120/7] via 10.0.0.2, 00:00:28, Port-channel 2
160.45.0.0/30 is subnetted, 1 subnets
R 160.45.34.0 [120/2] via 10.0.0.2, 00:00:28, Port-channel 2
164.24.0.0/30 is subnetted, 1 subnets
R 164.24.5.0 [120/5] via 10.0.0.2, 00:00:28, Port-channel 2
165.15.0.0/30 is subnetted, 1 subnets
R 165.15.20.0 [120/2] via 10.0.0.2, 00:00:28, Port-channel 2
166.56.0.0/30 is subnetted, 1 subnets
R 166.56.1.0 [120/3] via 10.0.0.2, 00:00:28, Port-channel 2
169.10.0.0/24 is subnetted, 3 subnets
R 169.10.10.0 [120/4] via 10.0.0.2, 00:00:28, Port-channel 2
R 169.10.15.0 [120/4] via 10.0.0.2, 00:00:28, Port-channel 2
R 169.10.55.0 [120/4] via 10.0.0.2, 00:00:28, Port-channel 2
170.16.0.0/24 is subnetted, 1 subnets
R 170.16.30.0 [120/3] via 10.0.0.2, 00:00:28, Port-channel 2
172.16.0.0/30 is subnetted, 4 subnets
R 172.16.1.0 [120/4] via 10.0.0.2, 00:00:28, Port-channel 2
R 172.16.2.0 [120/3] via 10.0.0.2, 00:00:28, Port-channel 2
R 172.16.3.0 [120/3] via 10.0.0.2, 00:00:28, Port-channel 2
R 172.16.4.0 [120/3] via 10.0.0.2, 00:00:28, Port-channel 2
172.30.0.0/24 is subnetted, 1 subnets
R 172.30.6.0 [120/6] via 10.0.0.2, 00:00:28, Port-channel 2
R 192.17.5.0/24 [120/1] via 10.0.0.2, 00:00:28, Port-channel 2
C 192.168.10.0/24 is directly connected, Vlan10
C 192.168.15.0/24 is directly connected, Vlan15
C 192.168.20.0/24 is directly connected, Vlan20
C 192.168.55.0/24 is directly connected, Vlan55
192.168.101.0/24 is variably subnetted, 2 subnets, 2 masks
R 192.168.101.0/24 [120/4] via 10.0.0.2, 00:00:28, Port-channel 2
C 192.168.101.0/30 is directly connected, FastEthernet0/3
209.165.201.0/30 is subnetted, 1 subnets
R 209.165.201.0 [120/4] via 10.0.0.2, 00:00:28, Port-channel 2
DLS0#
NB****
Well, I have decided to look for a network with more devices to see the impact of convergence, where routing & topology tables are large. This is also due to the number of devices I can avail to myself since these days the MIT lab is busy. The only disadvantage is that some commands are not incorporated in packet tracer.
No comments:
Post a Comment