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

Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 761
53-1003031-02
About the L2VPN VPLS address family
8
When VPLS auto-discovery is disabled for a VPLS instance, the system removes all auto-discovered
peers for the VPLS instance from the configuration. It then removes the route (local VPLS endpoint
address) from the BGP L2VPN route table and sends a “withdrawn” message to VPLS peers,
prompting them to remove the route and to disable VPLS auto-discovery. Finally, the system
updates the route target tree and sends a route refresh message for the L2VPN VPLS address
family.
About the L2VPN VPLS address family
The L2VPN VPLS address family is an integral part of BGP-based auto-discovery for VPLS, in that it
is the mechanism used by BGP4 to distribute information about VPLS endpoints. The L2VPN
address family is configured at the BGP configuration level of the CLI and supports the VPLS
Subsequent Address Family Identifier (SAFI), an address qualifier that provides additional
information about the Network Layer Reachability Information (NLRI) type for a given attribute.
BGP4 uses the L2VPN address family to build the BGP L2VPN Routing information Base (RIB). The
L2VPN database is updated each time a Layer 2 Virtual Forwarding Instance (VFI) is configured.
Information about configuring the L2VPN Address Family is in the section “Configuring the L2VPN
VPLS address family and activating the BGP4 peering session” on page 770.
Feature limitations and configuration notes
Consider the following feature limitations and configuration notes:
• VPLS must not be used when FDP is enabled.
• VPLS auto-discovery and manual configuration of VPLS peers are supported together on the
same device. However they are not supported together on the same VPLS instance.
• VPLS auto-discovery is not compatible in multi vendor environment. It must only be used
among Brocade MLX series and Brocade NetIron XMR devices.
Scalability
The following section describes the scalability:
• The maximum number of BGP4 peers that can support the L2VPN VPLS address family is
equal to the maximum number of BGP4 peers supported on the device.
• The maximum number of VPLS instances that can support BGP-based auto-discovery for VPLS
is equal to the maximum number of VPLS instances supported on the device.
• The maximum number of BGP-based auto-discovered peers supported per VPLS instance is
equal to the maximum number of unique VPLS or VLL peers or number of VPLS peers
supported on the device. When the system exceeds the default or manually-configured
maximum number of VPLS peers supported on the device, any new peering for VPLS
auto-discovery is rejected.