Pbb Evpn On Dual Homed Device/Multi Homed Device With Active/Active Per Flow Load-Balancing - Cisco ASR 9000 Series Configuration Manuallines

PBB EVPN on Dual Homed Device/Multi Homed Device with Active/Active per Flow load-balancing

Configuration on PE3:
interface GigabitEthernet 0/1/0/2.1 l2transport
encapsulation dot1q 200
l2vpn
pbb
bridge group gr1
bridge group gr2
!
router bgp 100
bgp router-id 1.1.1.3
address-family l2vpn evpn
!
neighbor 1.1.1.1
remote-as 100
address-family l2vpn evpn
PBB EVPN on Dual Homed Device/Multi Homed Device with Active/Active
per Flow load-balancing
This examples covers:
• PBB-EVPN service among three PEs in the same AS with a dual homed CE (behind PE1 and PE2) and
• PE1/PE2 configured to perform active/active per Flow loadbalancing allowing ingress traffic from the
• Example shows EVI carrying traffic from a single I-SID
• PBB I-SID values must match among PEs connected to a common dual homed site
• ICCP must be configured in PE1, PE2 using a new mode (mode singleton); where no ICCP neighbor is
• ESI must be identical on PEs connected to a common dual homed site. Example shows default behavior
• PBB source MAC must be the same on PEs connected to a dual homed site operating on active/active
• CE must be configured with one bundle interface that includes all member interfaces connecting to both
• BGP RD/RT auto-derived from BGP ASN and EVI ID
L2VPN and Ethernet Services Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 6.3.x
402
backbone-source-mac 00bb.00cc.00dd
bridge-domain bd1
interface GigabitEthernet0/1/0/2.1
pbb edge i-sid 300 core-bridge core_b1
bridge-domain core_bd1
pbb core
evpn evi 1000
a single homed CE (behind PE3)
same I-SID to be handled by both PEs
configured. Note that MLACP parameters such as system MAC/priority must be identical while MLACP
node ID must be unique on PE1/PE2
where ESI value is auto-derived from CE's LACP information
per flow load-balancing. Example shows default behavior where PBB source MAC value is auto-derived
from CE's LACP information
PEs
Implementing IEEE 802.1ah Provider Backbone Bridge