BGP based Multi-homing in

VPLS

IETF-75

Bhupesh Kothari Wim Henderickx

Kireeti Kompella Florin Balus
 Status
draft-kothari-henderickx-l2vpn-vpls-multihoming-01.txt

Common BGP based multi-homing

procedures for LDP and BGP signaled
VPLS
Draft is based on:
draft-kompella-l2vpn-vpls-multihoming-02.txt
draft-henderickx-l2vpn-vpls-multihoming-00.txt
 Outline
Provisioning Model
Multi-homing NLRI
Designated Forwarder Election
Multi-AS VPLS
MAC Flush
 Background: BGP VPLS
PW infrastructure is created based on VE-
IDs (RFC 4761)
VE-ID=2
A VE-ID=1 PE2 C

PE1 BGP VPLS

B PE3
VE-ID=3

Single VE-ID on PE1 is sufficient for customer sites A and B

VE-ID is assigned per VPLS instance irrespective of ACs (no
customer site attached to PE3)
 Background: LDP VPLS
PW infrastructure is created based on
procedures defined in RFC 4762

A PE2 C

PE1 LDP VPLS

B PE3

PWs can be created either using FEC-128 or FEC-129

Procedures defined in this draft for LDP signaled VPLS do
not depend on use of BGP Auto-discovery
 Provisioning Model
Multi-homing Identifier (MH-ID): Same MH-ID must be
configured on PEs connected to the same customer site

MH-ID=10
PE3 B
PE1
Customer site A
dual-homed to
PE devices for
VPLS
redundancy A PE2 PE4 C

MH-ID=10
 Multi-homing NLRI
Use of NLRI defined in RFC 4761
VE-ID field in the NLRI is set to MH-ID
LB, OFF and LR are set to zero

MH-ID=10
PE3 B
PE1

VPLS
A PE2 PE4 C

MH-ID=10

MH-ID is not used to create PWs

 Designated Forwarder Election

PE1: Based on DF tie-breaking rules, PE1 is DF

MH-ID=10,
PREF=200
PE1
PE3 B
VPLS
Based on DF election,
A PE2 PE3 can chose to not
send traffic to PE2
AC is put in non-forwarding state (depends on whether
there are additional
PE2:
PE2 loses DF sites on PE2 or not)
MH-ID=10,
election; elected as
PREF=100
non-DF
 Multi-AS Procedures
For the tie-breaker, the loopback of the
PE originating the MH NLRI is needed
This may be overwritten in a multi-AS
environment (such as in option B)
To preserve this, we use the Route Origin
Extended Community
 Multi-AS Procedures
Local Pref is not passed across ASes
Again, this is needed for tie-breaking
To solve this, the VPLS Preference field in
the L2 info community is used
Compatibility between LP and VPLS Pref is
described in the document
 Multi-AS Procedures
For both BGP and LDP signaling, there
are three models for inter-AS operation
option A: direct, back-to-back connections
between ASes, with each AS treating the
other as a CE device
option B: ASBRs mediating the VPLS
option C: multi-hop eBGP connections
between RRs in each AS
This is completely analogous to IP VPNs
 MAC Flush
If the designated forwarder (PE1) for a
multi-homed CE goes down, remote PEs
(PE3) should flush the MACs they learned
from PE1
Ideally, this is done implicitly
However, if PE3 is not upgraded, it may not
flush; thus, in some cases, PE1 may have to
send an explicit flush to the remote PEs
 Next Steps
Propose to adopt this as WG document?
Questions/Comments?