19.07.2013 Views

CCNP TSHOOT 6.0 - Cisco Learning Home

CCNP TSHOOT 6.0 - Cisco Learning Home

CCNP TSHOOT 6.0 - Cisco Learning Home

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>CCNP</strong>v6 <strong>TSHOOT</strong><br />

within them. Trunk ports are not listed.<br />

show vlan id vlan# Displays whether the VLAN exists and, if so, which ports<br />

are assigned to it. Includes trunk ports on which the VLAN<br />

is allowed.<br />

show interfaces type/# Displays interface status, IP address/prefix, load, duplex,<br />

speed and packet statistics and errors.<br />

show interfaces trunk Displays all trunk ports, the operational status, trunk<br />

encapsulation, and native VLAN, as well as the list of<br />

allowed VLANs, active VLANs, and the VLANs in Spanning<br />

Tree Forwarding state for the trunk.<br />

show interfaces type/#<br />

switchport<br />

Checks all VLAN-related parameters for a specific interface<br />

(access ports and trunk ports).<br />

show etherchannel summary Displays port channels, the member ports, and flags<br />

indicating status.<br />

Lab 4-1 Sample Troubleshooting Flows<br />

The figure illustrates an example of a method that you could follow to diagnose and resolve Layer 2 problems.<br />

Sample Layer 2 Troubleshooting Flow<br />

No L3<br />

connectivity<br />

between<br />

adjacent<br />

devices<br />

Verify through<br />

connection testing<br />

(ping) and ARP<br />

cache checks<br />

Determine<br />

and verify L2<br />

path<br />

between<br />

devices<br />

Analyze packet<br />

captures<br />

Track frames<br />

and device<br />

MAC<br />

addresses<br />

along L2<br />

path<br />

Investigate<br />

links where<br />

path seems<br />

broken<br />

© 2009 <strong>Cisco</strong> Systems, Inc. All rights reserved. <strong>TSHOOT</strong> v1.0—15<br />

Usually, you start troubleshooting the Layer 2 connectivity between devices because you have discovered that<br />

there is no Layer 3 connectivity between two adjacent Layer 2 hosts, such as two hosts in the same VLAN or a<br />

host and its default gateway. The following are typical symptoms that could lead you to start examining Layer 2<br />

connectivity:<br />

• Failing pings between adjacent devices. (This can also be caused by a host-based firewall that is<br />

blocking pings.)<br />

All contents are Copyright © 1992–2010 <strong>Cisco</strong> Systems, Inc. All rights reserved. This document is <strong>Cisco</strong> Public Information. Page 13 of 24

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!