NETWORKING NOTES 1 IOS-XE VPLS

_____ ___ __ __ __ __ ___ __ __

\_ \/___\/ _\ \ \/ / /__\ /\ /\/ _ \/ / / _\
/ /\// //\ \ _____\ / /_\ \ \ / / /_)/ / \ \
/\/ /_/ \_// _\ \_____/ \//__ \ V / ___/ /____\ \
\____/\___/ \__/ /_/\_\__/ \_/\/ \____/\__/

Interface Configuration for VPLS ........................................................ 3

> Only EFP Based Config Supported .................................................................... 3
> Legacy EFP Centric Config .......................................................................... 3
> Replacement Bridge-Domain Based Config ............................................................. 3
Manual VFI Configuration for VPLS ....................................................... 4
> Legacy L2 VFI Based Config ......................................................................... 4
> Replacement L2VPN VFI and Bridge-Domain Based Config ............................................... 4
> VPN ID ............................................................................................. 4
VPLS BGP Autodiscovery Configuration (with LDP Signaling) ............................... 6
> BGP Autodiscovery, LDP Signaling ................................................................... 6
> Legacy L2 VFI Based Config ......................................................................... 6
> Replacement L2VPN VFI and Bridge-Domain Based Config ............................................... 6
> Route Distinguisher ................................................................................ 7
> Route Target ....................................................................................... 7
> VPLS Identifier .................................................................................... 8
> NLRI Contents ...................................................................................... 8
VPLS BGP Autodiscovery Configuration (with BGP Signaling) ............................... 9
> BGP Autodiscovery, BGP Signaling ................................................................... 9
> Legacy L2 VFI Based Config ......................................................................... 9
> Replacement L2VPN VFI and Bridge-Domain Based Config ............................................... 9
> Route Distinguisher ................................................................................ 9
> Route Target ...................................................................................... 10
> VPLS Identifier ................................................................................... 10
> VE ID ............................................................................................. 10
> Label Block Size .................................................................................. 10
Manual H-VPLS Configuration ............................................................ 12
> Spoke PW are Access Interfaces .................................................................... 12
> Legacy L2 VFI Based Hub Config .................................................................... 12
> Replacement L2VPN VFI and Bridge-Domain Based Config .............................................. 12

2018 N E W A G E Q U A N T A
NETWORKING NOTES 2 IOS-XE VPLS

2018 N E W A G E Q U A N T A
NETWORKING NOTES 3 IOS-XE VPLS

Interface Configuration for VPLS

> Only EFP Based Config Supported

>> Ethernet Flow Point or Service Instances must be configured under the interface

>> VPLS local interface must be tied to a bridge-domain

>> This implies that sub-interface based configuration cannot be used

>> I.e. only service instance based configuration may be used

> Legacy EFP Centric Config

>> Bridge-domain is configured under the interface

>> This also means that the bridge-domain cannot be globally configured

>>> Major implication is that VFI config will also be of the same type

interface GigabitEthernet3
!
service instance 100 ethernet
encapsulation dot1q 100
bridge-domain 100
!

> Replacement Bridge-Domain Based Config

>> Bridge domain is global

>> EFP and VFI will now be members of the BD

interface GigabitEthernet3
!
service instance 100 ethernet
encapsulation dot1q 100
!
bridge-domain 100
member GigabitEthernet3 service-instance 100

2018 N E W A G E Q U A N T A
NETWORKING NOTES 4 IOS-XE VPLS

Manual VFI Configuration for VPLS

> Legacy L2 VFI Based Config

>> Bridge-domain is configured under the L2 VFI

>> This also means that the bridge-domain cannot be globally configured

>>> Major implication is that EFP config will also be of the same type
l2 vfi VPLS100 manual
vpn id 100
bridge-domain 100
neighbor 5.5.5.5 encapsulation mpls
neighbor 4.4.4.4 encapsulation mpls
neighbor 19.19.19.19 encapsulation mpls

> Replacement L2VPN VFI and Bridge-Domain Based Config

>> Bridge domain is global

>> VFI and EFP will now be members of the BD

l2vpn vfi context VPLS100

vpn id 100
member 19.19.19.19 encapsulation mpls
member 5.5.5.5 encapsulation mpls
member 4.4.4.4 encapsulation mpls
!
bridge-domain 100
member vfi VPLS100

> VPN ID
>> In the case of manual VFI configuration, VPN ID provided the automatic value of PW-ID or the VC-ID

>> If a VC-ID is not specified in the neighbor or member statement, the VPN ID value is used

>> These values can still be incongruous from the VPN ID, via manual configuration

!L2VPN example shown but idea applies to legacy L2 VFI config as well
l2vpn vfi context VPLS100
vpn id 100
member 4.4.4.4 200 encapsulation mpls
2018 N E W A G E Q U A N T A
NETWORKING NOTES 5 IOS-XE VPLS

member 19.19.19.19 encapsulation mpls

member 5.5.5.5 encapsulation mpls
!Only 4.4.4.4 will use VCID 200, rest of the neighbors us 100

2018 N E W A G E Q U A N T A
NETWORKING NOTES 6 IOS-XE VPLS

VPLS BGP Autodiscovery Configuration (with LDP Signaling)

> BGP Autodiscovery, LDP Signaling

>> RFC 6074

>> BGP in this configuration is only used to exchange VPN IDs and PW endpoints

>> The actual PW is still established with LDP

>> Config is more scalable since BGP concepts such as RRs can be used

>> NLRI exchanged is the standard BGP L2VPN VPLS NLRI (e.g. with Label Blocks and offsets)

>> The information contained therein is simply ignored

> Legacy L2 VFI Based Config

>> Bridge-domain is configured under the L2 VFI

>> This also means that the bridge-domain cannot be globally configured

>>> Major implication is that EFP config will also be of the same type
l2 vfi BGP_VPLS_100 autodiscovery
vpn id 100
bridge-domain 100
router bgp 100
no bgp default ipv4-unicast
neighbor 2.2.2.2 remote-as 100
neighbor 2.2.2.2 update-source Loopback0
neighbor 4.4.4.4 remote-as 100
neighbor 4.4.4.4 update-source Loopback0
!
address-family l2vpn vpls
neighbor 2.2.2.2 activate
neighbor 4.4.4.4 activate
exit-address-family
!

> Replacement L2VPN VFI and Bridge-Domain Based Config

>> Bridge domain is global

>> VFI and EFP will now be members of the BD

2018 N E W A G E Q U A N T A
NETWORKING NOTES 7 IOS-XE VPLS

l2vpn vfi context BGP_VPLS_100

vpn id 100
autodiscovery bgp signaling ldp
bridge-domain 100
member GigabitEthernet3 service-instance 100
member vfi BGP_VPLS_100
router bgp 100
no bgp default ipv4-unicast
neighbor 4.4.4.4 remote-as 100
neighbor 4.4.4.4 update-source Loopback0
neighbor 5.5.5.5 remote-as 100
neighbor 5.5.5.5 update-source Loopback0
!
address-family l2vpn vpls
neighbor 4.4.4.4 activate
neighbor 5.5.5.5 activate
exit-address-family

> Route Distinguisher

>> RD value is auto-derived by default

>> The format is ASN:VPN-ID

>> There does not seem to be a way to manually assign an RD

> Route Target

>> Auto-derived by default

>>> Format is the same as the auto-derived RD

l2 vfi BGP_VPLS_100 autodiscovery
no auto-route-target
!
l2vpn vfi context BGP_VPLS_100
vpn id 100
autodiscovery bgp signaling ldp
no auto-route-target

>> Can also be configured manually (like L3VPNs)

l2 vfi BGP_VPLS_100 autodiscovery

2018 N E W A G E Q U A N T A
NETWORKING NOTES 8 IOS-XE VPLS

route-target export 100:100

route-target import 100:100
!
l2vpn vfi context BGP_VPLS_100
vpn id 100
autodiscovery bgp signaling ldp
route-target export 100:100
route-target import 100:100

> VPLS Identifier

>> Added as an Ext-Community to the NLRI (L2VPN Identifier 0x0A)

>> Auto-Derived by default, same format as the RD and RT

>> Must match for the NLRI to be accepted in a VFI

>> If there is a mismatch, “DENIED due to: extended community not supported;” debug message is seen

>> Manual configuration

l2 vfi BGP_VPLS_100 autodiscovery

vpls-id 100:100
!
l2vpn vfi context BGP_VPLS_100
autodiscovery bgp signaling ldp
vpls-id 100:100

> NLRI Contents

>> RD:IP of the advertising PE

>> WS cannot decipher this properly

>> Distinguished from VPLS BGP NLRI by its length (96 vs 136)

2018 N E W A G E Q U A N T A
NETWORKING NOTES 9 IOS-XE VPLS

VPLS BGP Autodiscovery Configuration (with BGP Signaling)

> BGP Autodiscovery, BGP Signaling

>> True VPLS BGP based signaling based on RFC 4761

>> Configuration is more involved (obviously) than LDP signaled BGP AD

> Legacy L2 VFI Based Config

>> All research points to this configuration not supported

> Replacement L2VPN VFI and Bridge-Domain Based Config

>> Bridge domain is global

>> VFI and EFP will now be members of the BD

l2vpn vfi context BGP_VPLS_100

vpn id 100
autodiscovery bgp signaling bgp
ve id 1001
bridge-domain 100
member GigabitEthernet3 service-instance 100
member vfi BGP_VPLS_100
router bgp 100
no bgp default ipv4-unicast
neighbor 4.4.4.4 remote-as 100
neighbor 4.4.4.4 update-source Loopback0
neighbor 5.5.5.5 remote-as 100
neighbor 5.5.5.5 update-source Loopback0
!
address-family l2vpn vpls
neighbor 4.4.4.4 activate
neighbor 4.4.4.4 suppress-signaling-protocol ldp
neighbor 5.5.5.5 activate
neighbor 5.5.5.5 suppress-signaling-protocol ldp
exit-address-family

> Route Distinguisher

>> RD value is auto-derived by default

>> The format is ASN:VPN-ID

2018 N E W A G E Q U A N T A
NETWORKING NOTES 10 IOS-XE VPLS

>> For BGP based signaling, RD can be changed manually

l2vpn vfi context BGP_VPLS_100

autodiscovery bgp signaling bgp
rd 5.5.5.5:100

> Route Target

>> Auto-derived by default

>>> Format is the same as the auto-derived RD

l2vpn vfi context BGP_VPLS_100
vpn id 100
autodiscovery bgp signaling ldp
no auto-route-target

>> Can also be configured manually (like L3VPNs)

l2vpn vfi context BGP_VPLS_100

vpn id 100
autodiscovery bgp signaling ldp
route-target export 100:100
route-target import 100:100

> VPLS Identifier

>> Concept is not relevant here and hence not configurable

> VE ID
>> Mandatory value that must be configured

>> Advertised in the NLRI as VE-ID/CE-ID

>> Each PE must have a unique VE-ID per VPLS VFI

l2vpn vfi context BGP_VPLS_100

autodiscovery bgp signaling bgp
ve id 1001

> Label Block Size

>> Optional value (default of 10 is used, LBO used as needed by peer VE IDs)
2018 N E W A G E Q U A N T A
NETWORKING NOTES 11 IOS-XE VPLS

>> Can be manually configured

l2vpn vfi context BGP_VPLS_100

autodiscovery bgp signaling bgp
ve range 100

2018 N E W A G E Q U A N T A
NETWORKING NOTES 12 IOS-XE VPLS

Manual H-VPLS Configuration

> Spoke PW are Access Interfaces

>> This is achieved by disabling the Split-Horizon rule on Spoke PWs

>> The rule is still in place on PWs to other Hubs

>>> Thus the Hubs must be configured with a full-mesh of PWs

>> Spoke configuration is unchanged except for one key difference

>>> Instead of LDP peering with all other PEs, the only peering will be with the Access Hub
> Legacy L2 VFI Based Hub Config
>> Similar in most regards except:

>>> May or may not have physical ACs in the VFI (Typical configuration will not have ACs)
>>> PWs configured to the spokes will be configured with “no-split-horizon”
l2 vfi HVPLS_100_HUB manual
vpn id 100
bridge-domain 100
neighbor 4.4.4.4 encapsulation mpls no-split-horizon
neighbor 2.2.2.2 encapsulation mpls no-split-horizon
neighbor 6.6.6.6 encapsulation mpls

> Replacement L2VPN VFI and Bridge-Domain Based Config

>> Need to be cognizant of where the ACs are configured in this type of config

>>> ACs are configured directly under the BD

>>> This implies that the Spoke PWs will also be configured directly under the BD
>>> No concept of separate ‘no-split-horizon’ keyword
>>> Configuration under the BD turn SH off automatically
#Hub PWs
l2vpn vfi context HVPLS_100_HUB
vpn id 100
member 3.3.3.3 encapsulation mpls
!
#Spoke PWs along with ACs
bridge-domain 100
2018 N E W A G E Q U A N T A
NETWORKING NOTES 13 IOS-XE VPLS

member vfi HVPLS_100_HUB

member 5.5.5.5 100 encapsulation mpls

2018 N E W A G E Q U A N T A