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 .
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.
You are familiar with the concepts in the “Configuring Virtual Private LAN Services” and the “VPLS Autodiscovery BGP Based” modules of the .
Information About 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.
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.
How to Configure VPLS BGP Signaling
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 |
enable Example:
|
Enables privileged EXEC mode.
|
||
Step 2 |
configure terminal Example:
|
Enters global configuration mode. |
||
Step 3 |
l2vpn vfi context name Example:
|
Establishes a L2VPN virtual forwarding interface (VFI) between two or more separate networks and enters Layer 2 VFI configuration mode. |
||
Step 4 |
vpn id vpn-id Example:
|
Configures a VPN ID for the VPLS domain. |
||
Step 5 |
autodiscovery bgp signaling {bgp | ldp} [template template-name] Example:
|
Enables BGP signaling and discovery or LDP signaling and enters L2VPN VFI autodiscovery configuration mode.
|
||
Step 6 |
ve id ve-id Example:
|
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 range ve-range Example:
|
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. |
||
Step 8 |
exit Example:
|
Exits L2VPN VFI autodiscovery configuration mode and enters L2VPN VFI configuration mode. |
||
Step 9 |
exit Example:
|
Exits L2VPN VFI configuration mode and enters global configuration mode. |
||
Step 10 |
router bgp autonomous-system-number Example:
|
Enters router configuration mode to create or configure a BGP routing process. |
||
Step 11 |
bgp graceful-restart Example:
|
Enables the BGP graceful restart capability and BGP nonstop forwarding (NSF) awareness. |
||
Step 12 |
neighbor ip-address remote-as autonomous-system-number Example:
|
Configures peering with a BGP neighbor in the specified autonomous system. |
||
Step 13 |
address-family l2vpn [vpls] Example:
|
|
||
Step 14 |
neighbor ip-address activate Example:
|
Enables the neighbor to exchange information for the L2VPN VPLS address family with the local device. |
||
Step 15 |
neighbor ip-address send-community [both | standard | extended] Example:
|
|
||
Step 16 |
neighbor ip-address suppress-signaling-protocol ldp Example:
|
|
||
Step 17 |
end Example:
|
Exits address family configuration mode and returns to privileged EXEC mode. |
||
Step 18 |
show bgp l2vpn vpls {all | rd route-distinguisher} Example:
|
(Optional) Displays information about the L2VPN VPLS address family. |
Configuration Examples for VPLS BGP Signaling
l2vpn vfi context vfi1
vpn id 100
autodiscovery bgp signaling bgp
ve id 1001
ve range 10
!
!
router bgp 100
bgp graceful-restart
neighbor 209.165.200.224 remote-as 100
neighbor 209.165.200.224 update-source Loopback1
!
address-family l2vpn vpls
neighbor 209.165.200.224 activate
neighbor 209.165.200.224 send-community extended
neighbor 209.165.200.224 suppress-signaling-protocol ldp
exit-address-family
!
show bgp l2vpn vpls all
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 100:100
*>100:100:VEID-1001:Blk-1001/136 0.0.0.0 32768 ?
*>i 100:100:VEID-1003:Blk-1000/136 209.165.200.224 0 100 0 ?
Related Topic |
Document Title |
---|---|
Cisco IOS commands |
|
BGP commands: complete command syntax, command mode, defaults, command history, usage guidelines, and examples. |
|
Configuring Virtual Private LAN Services |
|
Configuring Access Port |
Configuring Virtual Private LAN Services, |
VPLS Autodiscovery BGP Based |
Standard/RFC |
Title |
---|---|
RFC 4761 |
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) |
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.
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 . |