You are on page 1of 53

Advanced Topics and Future Directions

in MPLS

sbng@cisco.com
ttheera@cisco.com
limfung@cisco.com

Agenda
IETF Update
Transport Evolution
Ethernet Virtual Private Network
Segment Routing
Summary

2014 Cisco and/or its affiliates. All rights reserved.

IETF Update

Internet Engineering Task Force


Responsible for MPLS standardization
Six active working groups

MPLS
Layer 3 Virtual Private Networks (L3VPN)
Pseudowire Edge-to-Edge (PWE3)
Layer 2 Virtual Private Networks (L2VPN)
Common Control and Measurement Plane (CCAMP)
Path Computation Element (PCE)

Some MPLS related work also defined in IS-IS and OSPF working groups

2014 Cisco and/or its affiliates. All rights reserved.

MPLS Working Group


Defined MPLS architecture and base protocols (LDP, RSVP-TE)
Over 130 RFCs published to date
Mature set of IP/MPLS specifications for both unicast and multicast
Areas of focus
MPLS Transport Profile (MPLS-TP)
Seamless MPLS (building large scale, consolidated MPLS networks)

2014 Cisco and/or its affiliates. All rights reserved.

L2VPN WG
Mature specifications for:
- Virtual Private Wire Service (VPWS): point-to-point L2 service
- Virtual Private LAN Service (VPLS): multipoint-to-multipoint Ethernet service

New service definition:


- Virtual Private Multicast Service (VPMS): point-to-multipoint L2 service
Areas of focus
- Enhancing VPLS - Ethernet VPN (E-VPN) and PBB Ethernet VPN (PBB-EVPN)
- Optimizing E-Tree support over VPLS

2014 Cisco and/or its affiliates. All rights reserved.

ISIS WG
Responsible for IS-IS for IP
Current proposal to do MPLS label distribution (draft-previdi-filsfils-isissegment-routing)

Similar extensions expected in the OSFP working group

2014 Cisco and/or its affiliates. All rights reserved.

IETF Summary
Rich set of MPLS specifications covering
MPLS forwarding (unicast and multicast)
Layer-3 and layer-2 services (unicast and multicast)

Current main focus areas:

Seamless MPLS
MPLS transport profile (MPLS-TP)
L2VPN enhancements (PBB-EVPN, VPMS)
Segment Routing

2014 Cisco and/or its affiliates. All rights reserved.

Transport Evolution

Industry Trends
Many transport networks still based on SONET/SDH (circuit switching technology)
Packet-based growing fast and dominating traffic mix (driven by Video, Mobile, Cloud, application
migration to IP)
Increased changes in traffic patterns (mobility, cloud)
Transport networks migrating to packet switching for
Bandwidth efficiency (statistical multiplexing)
Bandwidth flexibility (bandwidth granularity, signaling)
Packet Network
(IP/MPLS)
Transport Network
(SONET/SDH)

Packet Network
(MPLS-TP)

2014 Cisco and/or its affiliates. All rights reserved.

11

Packet Transport Requirements


Connection-oriented packet-switching technology
Point-to-point (P2P) and point-to-multipoint (P2MP) transport
paths
Separation of control and management planes from data
plane
Deployable with or without a control plane

Should retain similar operational model of traditional


transport technologies
Multi-service (IP, MPLS, Ethernet, ATM, FR, etc)
Should support bandwidth reservation
Support for 1:1, 1:n, 1+1 protection with similar techniques to
traditional transport technologies
Support for In-band OAM
2014 Cisco and/or its affiliates. All rights reserved.

12

MPLS Transport Profile


Existing functionality
prior to MPLS
Transport profile

Existing functionality meeting


transport requirements

MPLS
Transport Profile
MPLS Forwarding
P2P / P2MP LSP
Pseudowire
Architecture
OAM
Resilicency
GMPLS
MP2P / MP2MP LSP
IP forwarding
ECMP

New
extensions
based on
transport
requirements

Extends MPLS to meet packet transport requirements


Identifies subset of MPLS supporting traditional transport
requirements
Data plane
Bidrectional P2P and unidirectional P2MP LSP (no LSP Merging)
In-band associated channel (G-Ach / GAL)

Control plane
Static
Dynamic (GMPLS)

OAM

In-band
Continuity check, remote defect indication
Connectivity verification and route tracing
Fault OAM (AIS/LDI, LKR)
Performance management

Resiliency
50ms switchover
Linear protection (1:1, 1+1, 1:N)
Ring protection

2014 Cisco and/or its affiliates. All rights reserved.

13

MPLS Transport and Service Options


MPLS-TP currently focuses on Layer-2/1services
Services (clients)
IPv4 Multicast

IPv4

IPv6

IPv4 VPN

IPv6 VPN

VPMS

VPWS

VPLS

Transport
IP/MPLS (LDP/RSVP-TE/BGP)

MPLS-TP (Static/RSVP-TE)

MPLS Forwarding
2014 Cisco and/or its affiliates. All rights reserved.

14

MPLS-TP Components

Forwarding
Plane

OAM

Protection

Control
Plane

Services

Bi-directional,
co-routed
LSPs
Static LSP
QoS

CC/RDI
On-demand
CV
Route Tracing
AIS/LDI/LKR
CFI (PW
Status)

Linear
protection (1:1,
1+1, 1:N)
Reversion
Wait-to-restore
timer

Static
Dynamic
(GMPLS)

Ethernet/VLAN
ATM
TDM
MS-PW
integration with
IP/MPLS

2014 Cisco and/or its affiliates. All rights reserved.

15

Multi-layer Routing (nLight Use Cases)

Dynamic Path Setup

Path Diversity
R2

R1

R1

R2
Packet
Domain

Packet
Domain
Disjoint paths

Signaled
lambda

R1

R1

R2

R2

Packet
Domain
Signaled
lambda

R3
Packet
Domain

Disjoint paths

Optical Domain

2014 Cisco and/or its affiliates. All rights reserved.

R3

Optical Domain

16

GMPLS Introduction
Generalized control plane for different types of network devices

Packet-Switch Capable (PSC)


Layer-2 Switch Capable (L2SC)
Time-Division-Multiplex Capable (TDM)
Lambda-Switch Capable (LSC)
Fiber-Switch Capable (FSC)

Two major models: peer (NNI) and overlay (UNI)


Different label formats depending on network type
Based on initial RSVP-TE, OSPF-TE and ISIS-TE extensions
Strict separation of control and forwarding planes
Supports bi-directional LSPs
IP based control plane
No IP based forwarding plane (no LDP)
2014 Cisco and/or its affiliates. All rights reserved.

17

GMPLS UNI Reference Model (IP+Optical)


Control plane interface
Client: UNI-C (packet)
Network: UNI-N (optical)

Separate packet and optical routing domains


Optical topology known to UNI-N but not to UNIC
UNI-C initiates LSP signaling

UNI

UNI

Head

Tail

UNI-C

UNI-C

Packet
Domain
RSVP

RSVP
UNI-N

UNI-N performs path computation through optical


domain
Common address space between UNI-C and
UNI-N to enable signaling
UNI honors administrative boundaries while
allowing controlled interaction

2014 Cisco and/or its affiliates. All rights reserved.

RSVP

RSVP

UNI-N

Optical Domain

Control plane

Forwarding plane

18

GMPLS UNI Dynamic Path Setup


Router can signal a path dynamically
through an optical (ONS 15454) network
using GMPLS
R1

R2
Packet
Domain

Signaled
lambda

R1

R2
Packet
Domain
Signaled
lambda

Router initiates signaling


ROADM computes path and signals
optical path

LSP state drives controller and physical


interface state on router
Support for HA including ISSU

Optical Domain

Router interface is fully layer-3 and Layer2 capable (including bundling)


Router interface may or may not run MPLS

2014 Cisco and/or its affiliates. All rights reserved.

19

Path Computation and Signaling


UNI-C (Head)

Initiates signaling (default lambda)


No explicit path (ERO) defined / signaled
Signaling initiated towards remote UNI-C (optical loopback or optical link address)
Bi-directional path (upstream and downstream labels)

UNI-N
Arrival of PATH message without ERO triggers path computation to destination across
optical domain
Establishment of optical path (trail) required for UNI signaling to proceed

2014 Cisco and/or its affiliates. All rights reserved.

20

Signaling Path Setup

UNI-C

UNI-N

1
UNI PATH
(upstream label = default lambda)

Head
initiates
tunnel
signaling

UNI-N

Optical path
computation, trail
signaling initiated
Trail Downstream PATH

Optical
impairment check

Optical
impairment check

Trail established

Trail Upstream PATH

UNI-C

Trail Downstream RESV

Trail established
6
UNI PATH ERROR
(upstream label = lambda)
UNI PATH
(upstream label = lambda)

Tunnel
established
8

UNI RESV
(Label = lambda)

2014 Cisco and/or its affiliates. All rights reserved.

Trail Upstream RESV

Per-hop optical
parameters

UNI PATH
(upstream label = lambda)

UNI RESV
(Label = lambda)

Tunnel
established

UNI PATH
(upstream label = lambda)
UNI RESV
(Label = lambda)

21

GMPLS UNI Diverse Path Setup


Router head can signal requirements
for path diversity against one or more
specific LSPs

R2
R1

ROADM includes path diversity


requirements in path computation
Source and destination of signaled
LSP may differ from LSP from which
diversity is required

Packet
Domain
Disjoint paths

R1

R3

R2

R3
Packet
Domain

Disjoint paths

Optical Domain

2014 Cisco and/or its affiliates. All rights reserved.

22

Diverse Path Computation and Signaling


UNI-C (Head)

Initiates signaling (default lambda)


No explicit path (ERO) defined/signaled
LSP exclusions (XRO) signaled to enable path diversity
Exclusions can be strict (MUST exclude) or best effort (SHOULD exclude)
Signaling initiated towards remote UNI-C (optical loopback or optical link address)
Bi-directional path (upstream and downstream labels)

UNI-N
Arrival of PATH message without ERO triggers optical path computation to destination
across optical domain
LSP exclusions used as additional input for optical path computation
Establishment of optical path (trail) required for UNI signaling to proceed
2014 Cisco and/or its affiliates. All rights reserved.

23

Signaling Diverse Path Setup

UNI-C

UNI-N

1
UNI PATH
(upstream label = default lambda)

Head
initiates
tunnel
signaling
including
LSP
exclusion

UNI-N

Optical path computation


subject to LSP exclusions,
trail signaling initiated
Trail Downstream PATH

Optical
impairment check

Optical
impairment check

Trail established

Trail Upstream PATH

UNI-C

Trail Downstream RESV

Trail established
6
UNI PATH ERROR
(upstream label = lambda)
UNI PATH
(upstream label = lambda)

Tunnel
established
8

UNI RESV
(Label = lambda)

2014 Cisco and/or its affiliates. All rights reserved.

Trail Upstream RESV

Per-hop optical
parameters

UNI PATH
(upstream label = lambda)

UNI RESV
(Label = lambda)

Tunnel
established

UNI PATH
(upstream label = lambda)
UNI RESV
(Label = lambda)

24

MPLS-TE and GMPLS Co-existence


Router would have two RSVP neighbors if
packet network runs MPLS-TE on DWDM
interface,
RSVP neighbor over physical interface for
MPLS TE signaling
RSVP neighbor over controller for GMPLS
signaling

RSVP
RSVP

R1

R2
Packet
Domain
Signaled
lambda

Separate RSVP refresh timers


High frequency for MPLS TE signaling

Optical Domain

Low frequency for GMPLS signaling


(lowest 232 ms or ~1.6 months)

2014 Cisco and/or its affiliates. All rights reserved.

25

Ethernet Virtual Private Network

Motivation
L2VPN (VPLS) used as data center
interconnect (DCI) solution

Ent DC1

Enterprise DCI back door

Ent DC2

Technology evolution requirements

Multi-homing
Scale (MAC-addresses, Number of Service Instances
Load balancing
Optimal Forwarding
Multicast optimization
Multi-tenancy

Enhancements bring benefits to other


VPLS applications

PE

CE

PE

SP NGN

DCPE

CE

DCPE
DCE

DCE

SP DC1

SP DC2
Standalone DCI network

Business services
Mobile backhaul

2014 Cisco and/or its affiliates. All rights reserved.

27

E-VPN At A Glance
MAC addresses learned in data-plane toward
access as before
Treat MAC addresses as routable addresses and
distribute them in BGP over MPLS/IP network
Receiving PE injects these MAC addresses into
forwarding table along with its associated
adjacency
When multiple PE nodes advertise the same
MAC, then multiple adjacency is created for that
MAC address in the forwarding table

BGP

PE

PE

PE

PE

When forwarding traffic for a given unicast MAC


DA, a hashing algorithm based on L2/L3/L4 hdr
is used to pick one of the adjacencies for
forwarding
Full-Mesh of PW no longer required !!
2014 Cisco and/or its affiliates. All rights reserved.

28
28

E-VPN Broadcast Example (e.g. ARP)


BGP

AGG1
PE1

AGG4
M2

PE3
MH-ID=3

M1

AGG5

AGG2

C-MAC2

MH-ID=1
C-MAC1
AGG3
MH-ID=2

AGG6
PE2

PE4

iBGP L2-NLRI
next-hop: n-PE1

<C-MAC1, Label 100>

Host M1 sends a message with MAC SA = M1 and MAC DA=bcast


PE1 learns M1 over its Agg2-PE1 AC and distributes it via BGP to other PE
devices
All other PE devices learn that M1 sits behind PE1
2014 Cisco and/or its affiliates. All rights reserved.

29

E-VPN Unicast Example


AGG1

AGG4
PE1

M1

M2

PE3

MH-ID=3

AGG5

AGG2
MH-ID=1

AGG3
MH-ID=2

AGG6
PE2

PE4
iBGP L2-NLRI

next-hop: n-PE4

<C-MAC2, Label 200>

Host M2 sends response with MAC SA = M2 and MAC DA = M1

PE4 learns M2 over its Agg5-PE4 AC and distributes it via BGP to other PE devices

PE 4 forwards the frame to PE1 since it has learned previously that M1 sits behind PE1

All other PE devices learn that M2 sits behind PE4

2014 Cisco and/or its affiliates. All rights reserved.

30

Ethernet Encapsulation Evolution


802.3

802.3

802.1Q

802.1Q

C-DA: Customer dest addr


C-SA: Customer src addr
C-TAG: Customer tag

802.1ad
PB

802.1ad
PB

802.1ah
PBB

Service Instances
(I-SID)
224=16,777,216

C-DA
C-SA

C-DA
C-SA
C-TAG

C-DA
C-SA
S-TAG
C-TAG

B-DA
B-SA
B-TAG
I-TAG
C-DA
C-SA
S-TAG
C-TAG

Payload

Payload

Payload

Payload

FCS

FCS

FCS

FCS

Service
Instances
(VID)
212=4,096

2014 Cisco and/or its affiliates. All rights reserved.

Service
Instances
(VID)
212=4,096

S-TAG: Service tag


B-DA: Backbone dest addr
S-SA: Backbone src addr
I-TAG: Service instance tag
VID: VLAN identifier (part of C-/S-/B-TAG)
I-SID: Backbone service instance identifier
(part of I-TAG)
PB: Provider Bridges
PBB: Provider backbone bridges

802.1Q/ad
service
Instances (212)
802.1ah
service
Instances (224)

31

Provider Backbone Bridges Ethernet Virtual


Private Network (PBB-EVPN) Solution Overview

Advertise local B-MAC addresses in BGP to all


other PEs that have at least one VPN in
common just like E-VPN

Single B-MAC to represent site ID

Can derive the B-MAC automatically from


system MAC address of LACP
Build a forwarding table from remote BGP
advertisements just like E-VPN (e.g.,
association of B-MAC to MPLS labels)

BE B
BE B
CE1

PE1

B-MAC Routes

LACP

PE3

MPLS

B-MAC = Site ID

802.1Qbp

PE2

PEs perform PBB functionality just like PBBVPLS


C-MAC learning for traffic received from ACs
and C-MAC/B-MAC association for traffic
received from core

2014 Cisco and/or its affiliates. All rights reserved.

32

PBB-EVPN: Avoiding C-MAC Address Flushing


2. Withdraw B-MAC1
PE1

VLAN 3

PE3

1
B-MAC1

MPLS/ IP

PE2

VPN

B-MAC

NH

Pref

RT3

B-MAC1

PE1

High

RT3

B-MAC1

PE2

Low

RT2

B-MAC1

PE1

Low

RT2

B-MAC1

PE2

High

RI
B

3. Remove

VLAN 2
C-MAC

VPN

B-MAC

NH

CM1

RT3

B-MAC1

PE1 PE2

CM2

RT2

B-MAC1

PE2

FIB

4 Update

B-MAC represents a site (Ethernet Segment)


Link, port, or node failure doesnt change the B-MAC address to C-MAC
address bindings only changes the next hop for that B-MAC

2014 Cisco and/or its affiliates. All rights reserved.

33

MAC Address Scalability


O(100) B-MACs

WAN

O(1M) C-MACs

DC Site 1
DC Site 2

DC Site
N

BGP MAC Advertisement Route Scalability


Multiple orders of magnitude difference between C-MAC & B-MAC addresses

C-MAC Address Confinement


With data plane C-MAC learning, C-MACs are never in RIB and are only present in FIB for active
flows
Whereas, with control plane C-MAC learning, C-MACs are always in RIB and maybe also in FIB
2014 Cisco and/or its affiliates. All rights reserved.

34

Comparison of L2VPN Solutions


VPLS

E-VPN

PBB-EVPN

Flow Based Load Balancing

No

Yes

Yes

Flow Based Multi-pathing

No

Yes

Yes

Geo-redundancy and Flexible Redundancy Grouping

No

Yes

Yes

All-Active Redundancy

Simplified Provisioning and Operation


Core Auto-Discovery

Yes

Yes

Yes

Access Multi-homing Auto-Discovery

No

Yes

Yes

New Service Interfaces

No

Yes

Yes

P2MP Trees

Yes

Yes

Yes

MP2MP Trees

No

Yes

Yes

Link/Port/Node Failure

Yes

Yes

Yes

MAC Mobility

Yes

Yes

Yes

Avoiding C-MAC Flushing

No

No

Yes

Support O(10 Million) MAC Addresses per DC

No

No

Yes

Confinement of C-MAC Learning

No

No

Yes

No

No

Yes

Optimal Multicast with LSM

Fast Convergence

Scalable for SP Virtual Private Cloud Services

Seamless Interworking
(TRILL/802.1aq/802.1Qbp/MST/RSTP
Guarantee C-MAC Transparency on PE

2014 Cisco and/or its affiliates. All rights reserved.

35

Segment Routing

Overview
Simple routing extensions (IS-IS / OSPF)
Increased network scalability and virtualization
Use packet encapsulation to reduce network state
Close integration between applications and network
Highly programmable
Highly responsive

Data plane agnostic (MPLS, IPv6)

draft-previdi-filsfils-isis-segment-routing
2014 Cisco and/or its affiliates. All rights reserved.

37

Segment Routing
Forwarding state (segment) is established by IGP
LDP and RSVP-TE are not required
Agnostic to forwarding dataplane: IPv6 or MPLS

MPLS Dataplane is leveraged without any modification


push, swap and pop: all what we need
segment = label

Source Routing
source encodes path as a label or stack of segments
two segments: node or adjacency

2014 Cisco and/or its affiliates. All rights reserved.

38

MPLS Control and Forwarding Operation with


Segment Routing
Services
BGP / LDP
PE1

PE2

IPv4

IPv6

IPv4
VPN

IPv6
VPN

VPWS

VPLS

LDP

RSV
P

BGP

Static

IS-IS

OSPF

Packet
Transport
PE1

IGP

2014 Cisco and/or its affiliates. All rights reserved.

PE2

MPLS Forwarding

No changes to
control or
forwarding plane

IGP label
distribution, same
forwarding plane

39

Adjacency Segments
9105
9107

9107

9101

9103

9103

9105

9105

9105

9107

9101

9103

9105

9105
A

9107

P
9105

9103

Nodes advertises adjacency label per link

9103

9105

9105

simple IGP extension

Only advertising node installs adjacency segment in data plane


Enables source routing along any explicit path (segment list)
2014 Cisco and/or its affiliates. All rights reserved.

40

Node Segment
FEC Z
push 65

swap 65
to 65

swap 65
to 65

A packet injected anywhere


with top label 65 will reach Z
via IGP shortest path

pop 65
D
Z

Packet
to Z

65

65

65

Packet
to Z

Packet
to Z

Packet
to Z

65

Packet
to Z

Nodes advertise a node segment


simple IGP extension

All remote nodes install node segment ids in data plane

2014 Cisco and/or its affiliates. All rights reserved.

41

Combining Segments
72

72

9003

9003

9003

65

65

65

Packet to Z

Packet to Z

Packet to Z

72
A

72
B

D
Pop
9003

Z
P

Packet to Z

65

Source Routing

65

65

65

Packet to Z

Packet to Z

Any explicit path can be expressed: ABCOPZ

2014 Cisco and/or its affiliates. All rights reserved.

42

Automated & Guaranteed FRR


IP-based FRR is guaranted in any
topology

Backbone

2002, LFA FRR project at Cisco


draft-bryant-ipfrr-tunnels-03.txt

Directed LFA (DLFA) is guaranteed


when metrics are symetric
No extra computation (RLFA)

C1

C2

E1

E4

1000
E2

E3

Simple repair stack


node segment to P node
adjacency segment from P to Q

Node segment
to P node

Default metric: 10
2014 Cisco and/or its affiliates. All rights reserved.

43

LFIB with Segment Routing


LFIB populated by IGP (ISIS / OSPF)
Forwarding table remains constant
(Nodes + Adjacencies) regardless of
number of paths

PE

PE

PE

Node
Segment
Ids

Adjacency
Segment
Ids

PE

P
PE

Other protocols (LDP, RSVP, BGP)


can still program LFIB

2014 Cisco and/or its affiliates. All rights reserved.

PE

PE

PE

In
Label

Out
Label

Out
Interface

L1

L1

Intf1

L2

L2

Intf1

L8

L8

Intf4

L9

Pop

Intf2

L10

Pop

Intf2

Ln

Pop

Intf5

Forwarding
table remains
constant

44

Application controls network delivers


2G from A to Z please

Tunnel AZ onto
{66, 68, 65}

66FULL
68
65

Path ABCOPZ is ok. I account the BW.


Then I steer the traffic on this path

The network is simple, highly programmable and responsive to rapid changes

2014 Cisco and/or its affiliates. All rights reserved.

45

Simple and Efficient Transport of


MPLS services
Efficient packet networks leverage ecmpaware shortest-path!
node segment!

Simplicity
one less protocol to operate
No complex LDP/ISIS synchronization to
troubleshoot

PE2

PE1

All VPN services ride on the node segment


to PE2

2014 Cisco and/or its affiliates. All rights reserved.

46

Simple Disjointness
Non-Disjoint Traffic
A sends traffic with [65]
Classic ecmp a la IP

Disjoint Traffic
A sends traffic with [111, 65]
Packet gets attracted in blue plane
and then uses classic ecmp a la IP

2014 Cisco and/or its affiliates. All rights reserved.

ECMP-awareness!

47

CoS-based TE
Tokyo to Brussels

data: via US: cheap capacity


VoIP: via Russia: low latency

CoS-based TE with SR
IGP metric set such as

> Tokyo to Russia: via Russia


> Tokyo to Brussels: via US
> Russia to Brussels: via Europe

Anycast segment Russia advertised by Russia core


routers

Tokyo CoS-based policy


Data and Brussels: push the node segment to Brussels
VoIP and Brussels: push the anycast node to Russia, push
Brussels

2014 Cisco and/or its affiliates. All rights reserved.

Node segment to Brussels


Node segment to Russia

48

Summary

Summary
New MPLS enhancements focus on

Increased deployment scale (unified MPLS)


Packet transport extensions (MPLS Transport Profile)
IP+Optical integration (GMPLS)
L2VPN (VPLS) efficiency and scaling (PBB-EVPN)
Highly scalable, programmable forwarding plane (Segment Routing)

New MPLS extensions to enhance


Packet transport (MPLS-TP)
Optical transport (GMPLS UNI)

PBB-EVPN defines BGP extensions to enhance scale and resiliency of existing VPLS
deployments and meet data centers requirements
Segment routing provides a control plane alternative for increased network scalability and
virtualization
2014 Cisco and/or its affiliates. All rights reserved.

50

PBB-EVPN: A Closer Look


DF Election with VLAN Carving
Prevent duplicate delivery of flooded frames.
Uses BGP Ethernet Segment Route.
Non-DF ports are blocked for flooded traffic
(multicast, broadcast, unknown unicast).
Performed per Segment rather than per (VLAN,
Segment).

Split Horizon for Ethernet Segment


Prevent looping of traffic originated from a multihomed segment.
Performed based on B-MAC source address rather
than ESI MPLS Label.

Aliasing
PEs connected to the same multi-homed Ethernet
Segment advertise the same B-MAC address.
Remote PEs use these MAC Route advertisements
for aliasing load-balancing traffic destined to C-MACs
reachable via a given B-MAC.
2014 Cisco and/or its affiliates. All rights reserved.

PE

PE

PE

PE

PE

PE

PE

PE

PE B-MAC1PE
B-MAC1
PE
51

PBB-EVPN: Dual Homed Device


PE1

PE3

VLAN 2, 3

B-MAC1

MPLS/
IP
PE2

VLAN 2,3

RT3

B-MAC1

PE1

RT3

B-MAC1

PE2

RT2

B-MAC1

PE1

RT2

B-MAC1

PE2

VPN

B-MAC

NH

RT3

B-MAC1

PE1, PE2

RT2

B-MAC1

PE1, PE2

RIB

FIB

Both PEs advertise the same B-MAC for the same Ethernet Segment.

Hashing used to load-balance traffic among next hops.

PE1 MAC Routes:

NH

Remote PE installs both next hops into FIB for associated B-MAC.

B-MAC

Each PE advertises a MAC route per Ethernet Segment (carries B-MAC associated with Ethernet Segment).

VPN

Route: RD11, B-MAC1, RT2, RT3

PE2 MAC Routes:

Route: RD22, B-MAC1, RT2, RT3

2014 Cisco and/or its affiliates. All rights reserved.

52

You might also like