Configuring Virtual LANs (VLANs)
December 2005
© Foundry Networks, Inc.
11 - 51
Configuration Rules
•
Since the uplink (to the provider cloud) and the edge link (to the customer port) must have different 802.1Q
tags, make sure the uplink and edge link are in different port regions. See “About Port Regions” on page 4-2
for a list of valid port regions.
•
If you configure a port with an 802.1Q tag-type, the Foundry device automatically applies the 802.1Q tag-type
to all ports within the same port region. Likewise, if you remove the 802.1Q tag-type from a port, the Foundry
device automatically removes the 802.1Q tag-type from all ports within the same port region.
•
X-Series devices support one configured tag-type per device along with the default tag-type of 8100. For
example, if you configure an 802.1Q tag of 9100 on ports 1 – 12, then later configure an 802.1Q tag of 5100
on port 15, the device automatically applies the 5100 tag to all ports in the same port region as port 15, and
also changes the 802.1Q tag-type on ports 1 – 12 to 5100.
•
802.1Q-in-Q tagging and VSRP are not supported together on the same device.
Enabling 802.1Q-in-Q Tagging
To enable 802.1Q-in-Q tagging, configure an 802.1Q tag on the untagged edge links (the customer ports) to any
value other than the 802.1Q tag for incoming traffic. For example, in Figure 11.20, the 802.1Q tag on the
untagged edge links (ports 11 and 12) is 9100, whereas, the 802.1Q tag for incoming traffic is 8100.
To configure 802.1 Q-in-Q tagging as shown in Figure 11.20, enter commands such as the following on the
untagged edge links of devices C and D:
FESX424 Switch(config)# tag-type 9100 e 11 to 12
FESX424 Switch(config)# aggregated-vlan
Note that since ports 11 and 12 belong to the port region 1 – 12, the 802.1Q tag actually applies to ports 1 – 12.
Syntax:
[no] tag-type <num> [ethernet [<slotnum>/] <port number> [to <port number>]]
The
<num>
parameter specifies the tag-type number and can be a hexadecimal value from 0 - ffff. The default is
8100.
The
<slotnum>
parameter is required on chassis devices.
The
ethernet <port number> to <port number>
parameter specifies the port(s) that will use the defined 802.1Q
tag. This parameter operates with the following rules:
•
If you specify a single port number, the 802.1Q tag applies to all ports within the port region. For example, if
you enter the command
tag-type 9100 e 1
, the Foundry device automatically applies the 802.1Q tag to ports
1 – 12 since all of these ports are in the same port region. You can use the
show running-config
command
to view how the command has been applied.
•
If you do not specify a port or range of ports, the 802.1Q tag applies to all Ethernet ports on the device.
Содержание FastIron Edge Switch X424
Страница 36: ...Foundry Configuration Guide for the FESX FSX and FWSX 2 12 Foundry Networks Inc December 2005...
Страница 56: ...Foundry Configuration Guide for the FESX FSX and FWSX 3 20 Foundry Networks Inc December 2005...
Страница 70: ...Foundry Configuration Guide for the FESX FSX and FWSX 4 14 Foundry Networks Inc December 2005...
Страница 198: ...Foundry Configuration Guide for the FESX FSX and FWSX 8 38 Foundry Networks Inc December 2005...
Страница 316: ...Foundry Configuration Guide for the FESX FSX and FWSX 12 26 Foundry Networks Inc December 2005...
Страница 334: ...Foundry Configuration Guide for the FESX FSX and FWSX 13 18 Foundry Networks Inc December 22 2005...
Страница 350: ...Foundry Configuration Guide for the FESX FSX and FWSX 15 12 Foundry Networks Inc December 2005...
Страница 458: ...Foundry Configuration Guide for the FESX FSX and FWSX 18 18 Foundry Networks Inc December 2005...
Страница 712: ...Foundry Configuration Guide for the FESX FSX and FWSX 22 32 Foundry Networks Inc December 2005...
Страница 760: ...Foundry Configuration Guide for the FESX FSX and FWSX A 34 Foundry Networks Inc December 2005...
Страница 796: ...Foundry Configuration Guide for the FESX FSX and FWSX C 18 Foundry Networks Inc December 2005...
Страница 820: ...Foundry Configuration Guide for the FESX FSX and FWSX E 10 Foundry Networks Inc December 2005...