16.06.2014 Views

Cisco CCNA Study Guide - Router Alley

Cisco CCNA Study Guide - Router Alley

Cisco CCNA Study Guide - Router Alley

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>CCNA</strong> <strong>Study</strong> <strong>Guide</strong> v2.62 – Aaron Balchunas<br />

248<br />

Native VLANs<br />

A native VLAN can also be configured on trunk ports:<br />

Switch(config)# interface fa0/24<br />

Switch(config-if)# switchport mode trunk<br />

Switch(config-if)# switchport trunk native vlan 42<br />

Frames from the native VLAN are not tagged when sent out trunk ports. A<br />

trunking interface can only be assigned one native VLAN. Only 802.1Q<br />

supports native VLANs, whereas ISL does not. (More accurately, ISL will<br />

tag frames from all VLANs, even if a VLAN is configured as native). The<br />

native VLAN should be configured identically on both sides of the 802.1Q<br />

trunk).<br />

Native VLANs are often configured when plugging <strong>Cisco</strong> VoIP phones into<br />

a Catalyst Switch (beyond the scope of this section). Native VLANs are also<br />

useful if a trunk port fails. For example, if an end user connects a computer<br />

into a trunk port, the trunking status will fail and the interface will<br />

essentially become an access port. The user’s computer will then be<br />

transparently joined to the Native VLAN.<br />

Native VLANs provide another benefit. A trunk port will accept untagged<br />

frames and place them in the Native VLAN. Consider the following<br />

example:<br />

Assume that both 802.1Q switches have trunk links configured to the non-<br />

802.1Q switch, and that the trunk ports are configured in Native VLAN 42.<br />

Not only will the 802.1Q switches be able to communicate with each other,<br />

the non-802.1Q switch will be placed in Native VLAN 42, and be able to<br />

communicate with any device in VLAN 42 on any switch.<br />

(Please note, that the author of this study guide finds the “benefit” of the<br />

above example of Native VLANs to be……dubious at best, and confusing<br />

as hell at worst).<br />

By default on all trunking interfaces, the Native VLAN is VLAN 1.<br />

* * *<br />

All original material copyright © 2013 by Aaron Balchunas (aaron@routeralley.com),<br />

unless otherwise noted. All other material copyright © of their respective owners.<br />

This material may be copied and used freely, but may not be altered or sold without the expressed written<br />

consent of the owner of the above copyright. Updated material may be found at http://www.routeralley.com.

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

Saved successfully!

Ooh no, something went wrong!