03.02.2014 Views

Medianet Reference Guide - Cisco

Medianet Reference Guide - Cisco

Medianet Reference Guide - Cisco

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.

Network Availability Technologies<br />

Chapter 3<br />

<strong>Medianet</strong> Availability Design Considerations<br />

for a total of 30 bytes of encapsulation. ISL trunking can be configured on a switch port interface,<br />

as shown in Example 3-1. The trunking mode is set to ISL, and the VLANs permitted to traverse the<br />

trunk are explicitly identified; in this example, VLANs 2 and 102 are permitted over the ISL trunk.<br />

Example 3-1<br />

ISL Trunk Example<br />

Switch(config)#interface GigabitEthernet8/3<br />

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

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

Switch(config-if)# switchport trunk allowed 2, 102<br />

In contrast with ISL, 801.1Q does not actually encapsulate the Ethernet frame, but rather inserts a 4-byte<br />

tag after the source address field, as well as recomputes a new FCS, as shown in Figure 3-13. This tag<br />

not only preserves VLAN information, but also includes a 3-bit field for class of service (CoS) priority<br />

(which is discussed in more detail in Chapter 4, “<strong>Medianet</strong> QoS Design Considerations”).<br />

Figure 3-13<br />

IEEE 802.1Q Tagging<br />

Original Ethernet Frame<br />

DA SA TYPE/LEN DATA FCS<br />

Original Frame<br />

DA SA TAG TYPE/LEN DATA FCS<br />

Tagged Frame<br />

Inserted 4-Byte IEEE 802.1Q Tage<br />

Recomputed FCS<br />

228674<br />

IEEE 802.1Q also supports the concept of a native VLAN. Traffic sourced from the native VLAN is not<br />

tagged, but is rather simply forwarded over the trunk. As such, only a single native VLAN can be<br />

configured for an 802.1Q trunk, to preserve logical separation.<br />

Note<br />

Because traffic from the native VLAN is untagged, it is important to ensure that the same native VLAN<br />

be specified on both ends of the trunk. Otherwise, this can cause a routing blackhole and potential<br />

security vulnerability.<br />

IEEE 802.1Q trunking is likewise configured on a switch port interface, as shown in Example 3-2. The<br />

trunking mode is set to 802.1Q, and the VLANs permitted to traverse the trunk are explicitly identified;<br />

in this example, VLANs 3 and 103 are permitted over the 802.1Q trunk. Additionally, VLAN 103 is<br />

specified as the native VLAN.<br />

Example 3-2<br />

IEEE 802.1Q Trunk Example<br />

Switch(config)# interface GigabitEthernet8/4<br />

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

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

Switch(config-if)# switchport trunk allowed 3, 103<br />

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

Trunks are typically, but not always, configured in conjunction with EtherChannels, which allow for<br />

network link redundancy, and are described next.<br />

3-16<br />

<strong>Medianet</strong> <strong>Reference</strong> <strong>Guide</strong><br />

OL-22201-01

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

Saved successfully!

Ooh no, something went wrong!