19.07.2013 Views

CCNA Complete Guide 2nd Edition.pdf - Cisco Learning Home

CCNA Complete Guide 2nd Edition.pdf - Cisco Learning Home

CCNA Complete Guide 2nd Edition.pdf - 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.

- Both protocols utilize a 12-bit VLAN ID field, and hence support the same number of VLANs.<br />

ISL Header<br />

(26 bytes)<br />

ISL Header<br />

Encapsulated<br />

Ethernet Frame<br />

CRC<br />

(4 bytes)<br />

ISL Trailer<br />

Figure 7-2: Trunking Protocol Encapsulation Formats<br />

- Below shows the trunking actions for different types of switch port modes:<br />

Switch Port Mode Trunking Action<br />

access Never try to trunk.<br />

trunk Permanent trunking mode – always becomes a trunk link even if the<br />

interface at the other end is not configured as a trunk port.<br />

dynamic desirable Trunks to trunk, dynamic desirable, and dynamic auto interfaces.<br />

dynamic auto Trunks to trunk and dynamic desirable interfaces.<br />

Note: A trunk link will never be established if the interfaces at both ends of a trunk link were<br />

configured as the dynamic auto mode!<br />

- The switchport nonegotiate interface subcommand prevents an interface from generating<br />

Dynamic Trunking Protocol (DTP) frames, which are used for trunking negotiation.<br />

- Per-VLAN Spanning Tree Plus (PVST+) allows each VLAN to have its own instance of<br />

spanning tree. Figure 7-3 shows 6 interfaces on 3 switches with 2 VLANs. STP parameters in<br />

each VLAN are configured to block different interfaces in different spanning trees for VLAN<br />

2 and VLAN 3 on SW3. SW3 would use the link to SW1 for traffic in VLAN 3 and link to SW2<br />

for traffic in VLAN 2. STP will converge to find a new path for a VLAN if one of the links fails.<br />

Figure 7-3: Per-VLAN Spanning Tree Plus (PVST+)<br />

- 802.1Q defines a VLAN on a trunk as the native VLAN, where frames associated with the<br />

native VLAN are not tagged. A switch recognizes a native VLAN frame when a frame<br />

without 802.1Q tag is received from an 802.1Q trunk. ISL does not have this concept –<br />

every frame will be encapsulated and has an ISL header.<br />

52<br />

Dest Src Data FCS<br />

Original<br />

Frame<br />

Dest Src Tag Data FCS<br />

802.1Q Tag<br />

SW1 SW2<br />

Forwarding – VLAN 3 Forwarding – VLAN 2<br />

Blocking – VLAN 2<br />

SW3<br />

Blocking – VLAN 3<br />

Tagged<br />

Frame<br />

VLAN 3<br />

VLAN 2<br />

Root Bridge<br />

Root Bridge<br />

(Odd VLANs) (Even VLANs)<br />

(eg: 1. 3. 5) (eg: 2, 4, 6)<br />

Copyright © 2008 Yap Chin Hoong<br />

yapchinhoong@hotmail.com

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

Saved successfully!

Ooh no, something went wrong!