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

Multi-Service IronWare Switching Configuration Guide 229
53-1003036-02
Application of a standalone ESI
8
Brocade(config)#show tag-type
Encap Current VLAN Tags Default VLAN Tags
----- ----------------- -----------------
cvlan 8100 8100
svlan 9100 88A8
isid 86B5 88E7
bvlan 9100 88A8
NOTE
The Brocade NetIron CES and Brocade NetIron CER require that the SVLAN and BVLAN tag types be
same. The default tag-type for bvlan and svlan is 0x88A8 for the Brocade NetIron CES and 0x8100
for Brocade MLX series devices. The BVLAN, SVLAN, or CVLAN cannot be configured separately on
the Brocade MLX series device as is done on the Brocade NetIron CES.
Application of a standalone ESI
You can use a standalone ESI to perform VLAN ID translation. For example:
Brocade(config)# vlan 5
Brocade(config-vlan-5)#tag eth 1/1
Brocade(config-vlan-5)#exit
Brocade(config)#vlan 6
Brocade(config-vlan-6)#tag eth 1/2
Brocade(config)#vlan 7
Brocade(config-vlan-7)#tag eth 1/3
Flood domain and VLAN translation
An ESI consisting of VLANs, can optionally be set up as a flood domain, serving two purposes:
• Flooding - Creates a domain where packets received on a port within the flood domain are sent
to all other ports in the group with proper VLAN translations.
• VLAN translation - This feature can be used for translating between SVLANs across a provider
boundary.
NOTE
While the flood domain includes multiple VLANs, spanning tree still works within the scope of each
VLAN separately. Therefore, loops spanning across VLANs will not get resolved.
NOTE
Multiple VLANs on same port cannot be added in a single flood domain ESI. However multiple VLANs
on different ports are allowed to be added.
System operation without flood domain
Figure 20 shows an ESI configuration with a single flood domain.
FIGURE 20 Single flood domain ESI