Tracing the route to kentnarrows (172.16.1.45)
1 duck (10.10.10.1) 208 msec 124 msec 56 msec
3 kentnarrows (172.16.1.45) 12 msec * 8 msec heron#trace knappsnarrows
Tracing the route to knappsnarrows (172.16.2.45)
2 knappsnarrows (172.16.2.45) 12 msec 4 msec 8 msec heron#show ip interface brief
IP-Address 10.10.10.2 172.16.2.2 172.16.2.9 172.16.2.17
OK? Method Status YES manual up YES manual up YES manual up YES manual up
Continues to baseline the other device s in the Troub le Ticket. Compare your ending configurations t final configs file. If you want to see more of my testing, refer to the tt1 layer 3 testing file.
Note that I separated discoverin g Layer 1 and Layer 2 from nayer 3 ia thi s Trouble Tiuket. I wantec moro emphasize a lay ered au2roach to discoveuy, configuration, and tro ubleshooting. It is helpful 1 understand wnether you have a aayer 2 or Layer 1 issue causing the problem or is in face it is some Layer 3 ar above.
Theping command is a quick test to help you decide whether you have connectivity or data-lin issues when you can't physically access equipment; it is a quick test of Layer 3 and below. Th< Cisco and UNIX traceroute command tests up through Layer 4 via User Datagram Protocol (UDP) packets, whereas Microsoft tracert command tests through Layer 3 with Internet Conti Message Protocol (ICMP) echos.
If you need more practice after nompleting the discovery lab, feel free to turn this Trouble Ticket in configuration !ab or vice versa. Actually, I highly recommend it. Practice makes perfect. You can er configurations on all devices and configure them from scratch as in Figure 10-3.
Was this article helpful?