Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 271)

Multi-Service IronWare Switching Configuration Guide 241
53-1003036-02
About IEEE 802.1ad
9
In this display, the ESI named acme is an ESI of the encapsulation type CVLAN, which has two
members (VLANs). The acme ESI now has the santa ESI as a provider with an SVLAN encapsulation
type. The santa provider ESI is configured with VLAN ID 100.
This means that both CVLANs in the acme ESI receive a second SVLAN encapsulation (with a
tag-type value of SVLAN as globally configured) and a SVLAN ID of 100.
PB using untagged members
For the configuration shown in Figure 24 , you added a Customer ESI and a Provider ESI and bound
them together to provide PB service. This generic configuration can be used when a particular port
is shared between customers. However, if a port is completely owned by one customer, you can use
the following simple configuration to provide PB service.
Sample configuration 2
1. In this case, customer port 1/1 maps the customer’s 4K VLANs. The provider side port 1/2
uses SVLAN 100. All customer traffic from the provider side is appended with an SVLAN 100
tag, and for all traffic going to the provider side will have the SVLAN 100 tag removed.
Brocade(config)# interface ethernet 1/1
Brocade(config-if-e1000-1/1)# port-type provider-network
2. Configure customer ports as provider network ports instead of customer edge ports.
Brocade(config)# interface ethernet 1/2
Brocade (config-if-e1000-1/1)# port-type provider-network
3. Add customer ports as untagged ports so that any traffic tagged with the 8100 tag will also be
treated as untagged and will be appended with SVLAN 100.
Brocade(config)# esi ESI_1
Brocade(config)# esi ESI_1 encapsulation svlan
Brocade(config-esi-ESI_1)# vlan 100
Brocade(config-esi-ESI_1)# tagged ethernet 1/2
Brocade(config-esi-ESI_1)# untagged ethernet 1/1
Brocade(config-esi-ESI_1)# exit
SVLAN translation using flood domain configuration
The single-flood-domain command is used for SVLAN translation across provider domains.
FIGURE 25 SVLAN translation at an inter-provider boundary
In the configuration below, packets on port 1/3 with SVLAN=100 are translated to the port 1/4
with SVLAN=200 as the ports are in the same flood domain.