02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

Single-Tag and Untagged Support on VLAN-Stack Trunk Ports<br />

<strong>FTOS</strong> 7.7.1 adds multi-purpose functionality to VLAN-Stack ports <strong>for</strong> <strong>the</strong> E-<strong>Series</strong> e.<br />

The E-<strong>Series</strong> VLAN-Stack trunk port can be configured to <strong>for</strong>ward IEEE 802.1Q frames (E<strong>the</strong>rtype<br />

0x8100), stacked VLAN frames (E<strong>the</strong>rtype 0x9100), and untagged frames.<br />

A typical Service Provider network does not exclusively carry double-tagged traffic. Almost all practical<br />

networks in today's world use some automated management and monitoring scheme that runs on a separate<br />

system via an IP network. For example, as shown below, a service provider might have single-tagged<br />

traffic with E<strong>the</strong>rtype 0x8100 to carry IP traffic <strong>for</strong> management and o<strong>the</strong>r services such as Telnet, FTP,<br />

SNMP, etc. Traditionally, a separate port with its own separate link was required to carry this 0x8100<br />

tagged traffic. Carrying single-tagged and untagged frames on VLAN-Stack trunk ports increases port<br />

efficiency by enabling a single interface to be configured to carry all three types of traffic.<br />

Figure 139 Single and Double-Tagged VLANs on VLAN-Stacking Trunk Port<br />

Customer VLANs<br />

0x9100 -- 2-tags<br />

0x8100 -- 1-tag<br />

Access Port Trunk Port<br />

Important Points to Remember <strong>for</strong> (<strong>for</strong> E-<strong>Series</strong> Only)<br />

• A VLAN-Stack trunk port can be part of a single-tagged VLAN, as well as<br />

VLAN-stack-compatible VLANs. For an 802.1Q tag, <strong>the</strong> port will maintain a separate Layer 2<br />

broadcast domain, which is distinct from o<strong>the</strong>r broadcast domains created <strong>for</strong> customer<br />

VLANs and o<strong>the</strong>r service provider VLANS.<br />

• When a VLAN-Stack trunk port is configured in hybrid mode, it will be allowed to be part of<br />

an untagged VLAN.<br />

• A trunk port that is part of a single-tagged VLAN will be allowed to configure an IP address.<br />

• Layer 3 protocols (VRRP, ARP, etc.) are supported on a VLAN-Stack trunk port when it is<br />

part of a single-tagged VLAN.<br />

For configuration details on using E-<strong>Series</strong> VLAN-Stacking ports <strong>for</strong> carrying single-tagged VLANs and<br />

<strong>for</strong> carrying untagged traffic, see <strong>the</strong> following configuration examples:<br />

• Making a port both a trunk port and part of a single-tagged VLAN on page 238<br />

• Making a hybrid port a trunk port and a member of o<strong>the</strong>r VLANs on page 239<br />

• Configuring an E-<strong>Series</strong> VLAN-Stack trunk port to tunnel customer BPDUs on page 240<br />

<strong>FTOS</strong> <strong>Configuration</strong> <strong>Guide</strong>, version 7.7.1.0 229<br />

fnA0001mp

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

Saved successfully!

Ooh no, something went wrong!