The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The two primary
functions of the Virtual Private LAN Service (VPLS) control plane are
autodiscovery and signaling. The VPLS BGP Signaling feature enables you to use
BGP as both an autodiscovery and a signaling protocol for VPLS, in accordance
with RFC 4761.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information,
see
Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module,
and to see a list of the releases in which each feature is supported, see the feature information table at the end of this
module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature
Navigator, go to
www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for VPLS BGP Signaling
You are familiar with the concepts in the “Configuring Virtual Private LAN Services” and the “VPLS Autodiscovery BGP Based”
modules of the
MPLS Layer 2 VPNs Configuration Guide
.
Information About VPLS BGP Signaling
Overview of VPLS BGP Signaling
Prior to the VPLS BGP Signaling feature, BGP was used for autodiscovery and Label Distribution Protocol (LDP) for signaling
in accordance with RFC 6074. The VPLS BGP Signaling feature enables you to use BGP as the control plane protocol for both
autodiscovery and signaling in accordance with RFC 4761.
As specified in RFC 4761, internal BGP (iBGP) peers will exchange update messages of the L2VPN AFI/SAFI with L2VPN information
to perform both autodiscovery and signaling. The BGP multiprotocol Network Layer Reachability Information (NLRI) consists
of a Route Distinguisher (RD), VPLS Endpoint ID (VE ID), VE Block Offset (VBO), VE Block Size (VBS), and Label Base (LB).
The figure below shows the format of the NLRI for RFC 4761.
Figure 1. RFC 4761 NLRI
Additional information, such as next-hop, route target (specified for a VPLS instance), and other Layer 2 data are carried
in the BGP extended community attributes. A route target-based import/export mechanism similar to L3VPN is performed by BGP
to filter L2VPN NLRIs of a particular VPLS instance.
Whether you use BGP signaling (RFC 4761) or LDP signaling (RFC 6074) depends on the commands you specify. To enable the VPLS
BGP Signaling feature, use the
autodiscovery bgp signaling bgp command in L2 VFI configuration mode. This command is supported on a per VPLS instance basis.
If a BGP session receives an invalid (that is, not matching the configuration) BGP update advertisement (update or withdraw),
it is ignored.
BGP’s main task in supporting VPLS is route distribution via the L2VPN address family and interactions with L2VPN. Interactions
between BGP and other components remain the same. Basic BGP functionalities like best-path selection, next-hop handling, and
update generation, continue to operate in the same manner with VPLS BGP signaling. BGP RT constraint works seamlessly with
the BGP VPLS Signaling feature.
The above example shows sample configuration on one PE. Similar configuration can be mirrored on other PEs.
Enables BGP signaling and discovery or LDP signaling and enters L2VPN VFI autodiscovery configuration mode.
Note
For the VPLS BGP Signaling feature use the
autodiscovery bgp signaling bgp command.
Step 6
ve idve-id
Example:
Device(config-vfi-autodiscovery)# ve id 1001
Specifies the VPLS endpoint (VE) device ID value. The VE ID identifies a VFI within a VPLS service. The VE device ID value
is from 1 to 16384.
Step 7
ve rangeve-range
Example:
Device(config-vfi-autodiscovery)# ve range 12
Specifies the VE device ID range value. The VE range overrides the minimum size of VE blocks. The default minimum size is
10. Any configured VE range must be higher than 10.
Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling
RFC 6074
Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)
Technical Assistance
Description
Link
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use
these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products
and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.
The following table provides release information about the feature or features described in this module. This table lists
only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise,
subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco
Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1. Feature Information for VPLS BGP Signaling
Feature Name
Releases
Feature Information
VPLS BGP Signaling
The VPLS BGP Signaling feature enables you to use BGP as both an autodiscovery and signaling protocol for VPLS, in accordance
with RFC 4761.
The following commands were introduced or modified:
autodiscovery (MPLS),
neighbor suppress-signaling-protocol,
show bgp l2vpn vpls, and
ve.
In Cisco IOS XE Release 3.8S, support was added for the Cisco ASR 903 router.
Feedback