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

Multi-Service IronWare Switching Configuration Guide 283
53-1003036-02
Backbone Edge Bridge (BEB) operation
11
Customer to ISID mapping
There are two types of Customer to ISID Mapping. 1:1 Customer to ISID Mapping and N:1 Customer
to ISID Mapping. Brocade NetIron XMR and Brocade MLX series only support one single flooding
domain per SI regardless of which mapping is chosen. 1:1 Customer to ISID mapping is supported
by default. Brocade NetIron XMR and Brocade MLX series will also support S-VLAN Keep Mode to
inter-operate with Brocade NetIron CES and Brocade NetIron CER and other vendors on the same
PBB network that supports the N:1 Customer to ISID mapping.
Regardless of which type of mapping is chosen, Brocade NetIron XMR and Brocade MLX series will
always strip the incoming S-Tag and add the S/C-Tag as it goes out on the BEB's S/C-Tag endpoint
based on what is configured and not based on what is received. Optionally the S-Tag TPID value can
also be “translated” based on the exiting port's configured Ethernet Type value.
1:1 Customer to ISID mapping
With 1:1 customer to ISID mapping, a single customer is mapped to an ISID value. There may be
many S-Tag endpoints configured under the same SI, but they are all considered as belonging to
one customer. The BEB strips the S-Tag at the ingress of the BEB and inserts the S-Tag at the
egress of the BEB. There is no S-TAG in the PBB frame when it traverses the PBB network. Any PBB
instance configured in the system is considered as one SI which implies one single flooding
domain.
Figure 45 shows an example of a 1:1 customer to ISID mapping.