Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) - Manual (Page 477)

Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 453
53-1003031-02
Configuring VPLS instances
3
NOTE
On Brocade NetIron CES and Brocade NetIron CER devices, the route-only command must not be
configured on untagged MPLS uplinks when using it for VPLS or VLL. Otherwise, incoming VPLS or
VLL traffic is dropped.
NOTE
The Brocade NetIron CES and NetIron CER devices can only support 127 endpoints + peers in a
VPLS instance.
Configuring VPLS instances
This section explains how to set up VPLS instances.
Limitations
• In Brocade NetIron CES and Brocade NetIron CER devices, a CoS value configured during VPLS
instance creation is not used in the back-end. However, in Brocade NetIron XMR and Brocade
MLX series devices, the configured CoS value is carried in the MPLS label EXP field in case of
ingress PE.
• In Brocade NetIron CES and Brocade NetIron CER devices, the customer PCP/DSCP in the
outgoing packets through customer endpoint is replaced with the VCB Label EXP bits in the
MPLS packet. Therefore, PCP/DSCP bits cannot be preserved end-to-end.
• When more than 1000 VPLS instances, that share the same endpoint, are configured and
mapped to a single functional port; the functional port goes down and flaps certain protocols
like BFD & UDLD for shorter durations.