www.nmcgroups.com
Table of Contents
MPLS Backhaul Network
MPLS L3 VPN
Backhaul Concept
QinQ
H-VPLS
TPS Service
Residential
xDSL
WiBro Service
AS (PE)
Active Spoke LSP
FTTH
ES (PE)
VPN Service
MPLS Backbone
Enterprise
Internet Service
ER
WiBro
CO
POP
DSLAM
H-VPLS
QinQ
ES (PE)
AS (PE)
Active Spoke LSP
ADSL2+
ER
VPLS
MTU-S
PON
ONT
OLT
VPLS
PE-rs
BS
BRAS
L2 SW
CO
POP
Q-in-Q
EMS
Mgmt PVC (0/34)
RG/
IAD
GE port
VC-LSP=Per DSLAM
C-VID=Service ID
VSI
S-VID=DSLAM ID
Voice VLAN (3)
VC-LSP to VSI
Tunnel-LSP=PE to PE
GE port
S-VID=DSLAM ID
EMS
PON
CPE
S-VID to VSI
GE port
S-VID=OLT ID/RAS ID C-VID=Service ID
VSI
GE port
VSI
S-VID=DSLAM ID
Voice VLAN (3)
C-VID=Service ID
ER
VC-LSP=Per OLT/Per BS
S-VID=OLT ID/RAS ID
Voice VLAN (3)
VSI
S-VID=OLT ID/RAS ID
Voice VLAN (3)
C-VID=Service ID
GE port
VSI
S-VID=DSLAM ID
Internet VLAN (5)
C-VID=Service ID
VSI
S-VID=OLT ID/RAS ID
Internet VLAN (5)
C-VID=Service ID
BRAS
QinQ
CE
DSLAM
QinQ
ES (PE)
AS (PE)
ER
ADSL2+
MTU-S
CE
OLT
PE-rs
BS
L2 SW
POP
CO
Q-in-Q
S-VID to VSI
GE port
VC-LSP to VSI
Tunnel-LSP=PE to PE
VPN-A
GE port
C-VID=Defined by User
S-VID=Enterprise ID (VPN-A)
VSI
S-VID=Enterprise ID (VPN-A)
S-VID=Enterprise ID (VPN-B)
VSI
S-VID=Enterprise ID (VPN-B)
GE port
C-VID=Defined by User
CPE
VC-LSP=Per Enterprise VPN (VPN-B)
VPN-B
CPE
VPN-C
ER
GE port
S-VID=Enterprise ID (VPN-C)
VSI
S-VID=Enterprise ID (VPN-C)
S-VID=Enterprise ID (VPN-D)
VSI
S-VID=Enterprise ID (VPN-D)
CPE
VC-LSP=Per Enterprise VPN (VPN-D)
VPN-D
CPE
AS
ES
ER
AN
AS
ES
ER
VRRP
VRRP Master
Load Balancing
BRAS
AN
AS
ES
BRAS
VRRP Master
ER
AN
AS
ES
ER
VRRP Master
Load Balancing
Load Balancing
BRAS
AS
ES
VRRP Master
ER
BRAS
AS
ES
ER
VRRP Master
Load Balancing
BRAS
BRAS
PE1.CTY1
Metro Ethernet
Backhaul City 1
PE1.CTY5
Metro Ethernet
City 5
Backhaul
PE2.CTY1
PE1.CTY2
CR1
CR2
PE2.CTY5
Metro Ethernet
Backhaul City 2
PE1.CTY6
PE2.CTY2
Metro Ethernet
City 6 Backhaul
PE1.CTY3
Metro Ethernet
City 3
Backhaul
PE2.CTY6
PE2.CTY3
PE1.CTY7
CR3
Metro Ethernet
Backhaul
PE1.CTY4
City 7
Metro Ethernet
City 4
Backhaul
MPLS L2 VPN
Per-Enterprise VPN
Enterprise VPWS VPN
Enterprise VPLS VPN
PE2.CTY7
PE2.CTY4
Metro Ethernet
Backhaul
PE
PE
Metro Ethernet
Backhaul
ADSL Case
BRAS
PE
DSLAM
AS
Residential
Internet Access
PPPoE
Residential
Voice
DHCP
Residential
Video
DHCP
ES
VRF
VRF
VRF
PE/SAR
PE2
PE3
PE/BR
VRF
VRF
MPLS L3 Voice VPN (LSP to PE: Data)
Enterprise
A Single PVC
Internet Access
Static/Public Subnet
Enterprise
A Single PVC
L3 VPN
Private Addressing and Routing
Enterprise
A Single PVC
L2 VPN (PtP)
Private Addressing and Routing
A Single PVC
Enterprise
L2 VPN (PtMP)
Private Addressing and Routing
VRF
VRF
Per-Enterprise VLAN
(C-VID=null, S-VID=Ent. A)
Per-Enterprise VLAN
(C-VID=null, S-VID=Ent. B)
Per-Enterprise VLAN
(C-VID=Private Use, S-VID=Ent. C)
VRF
VRF
VRF
VRF
VRF
VRF
VSI
VRF
VSI
VSI
VSI
VSI
VSI
VSI
Per-Enterprise VLAN
(C-VID=Private Use, S-VID=Ent. D)
H-VPLS
VSI
VSI
VSI
VSI
VSI
VSI
VSI
VSI
10
FTTH Case
BRAS
PE
OLT
AS
Residential
Internet Access
DHCP
C-VID=Internet(5)
Residential
Voice
DHCP
C-VID=Voice(3)
Residential
Video
DHCP
ES
PE/BR
VRF
VRF
VRF
PE/SAR
PE2
PE3
VRF
MPLS L3 Internet VPN (LSP to PE:P2P)
VRF
MPLS L3 Voice VPN (LSP to PE: Data)
C-VID=Video(4)
Enterprise
C-VID=Ent. A
Internet Access
Static/Public Subnet
Enterprise
C-VID=Ent. B
L3 VPN
Private Addressing and Routing
Enterprise
C-VID=Ent. C
L2 VPN (PtP)
Private Addressing and Routing
C-VID=Ent. D
Enterprise
L2 VPN (PtMP)
Private Addressing and Routing
VRF
VRF
Per-Enterprise VLAN
(C-VID=null, S-VID=Ent. A)
Per-Enterprise VLAN
(C-VID=null, S-VID=Ent. B)
Per-Enterprise VLAN
(C-VID=Private Use, S-VID=Ent. C)
VRF
VRF
VRF
VRF
VRF
VRF
VSI
VRF
VSI
VSI
VSI
VSI
VSI
VSI
Per-Enterprise VLAN
(C-VID=Private Use, S-VID=Ent. D)
H-VPLS
VSI
VSI
VSI
VSI
VSI
VSI
VSI
VSI
11
WiBro Case
PE
BS
AS
ES
L3 ASN-GW
GRE tunnel
PE/BR
VRF
VRF
VRF
PE/SAR
PE2
PE3
DHCP
Residential
Internet Access
CID=Internet CID
Residential
Voice
CID=Voice CID
Residential
Video
VRF
VRF
MPLS L3 Voice VPN (LSP to PE: Data)
CID=Video CID
VRF
VRF
12
VPN Service
MPLS L3 VPN
MPLS L2 VPN
13
Metro Ethernet
Backhaul City 1
CE
VPN A
PE1.CTY5
City 5
Metro Ethernet
Backhaul
City 6
Metro Ethernet
Backhaul
PE2.CTY1
PE1.CTY2
CR1
CE
CR2
PE2.CTY5
Metro Ethernet
Backhaul City 2
CE
PE1.CTY6
PE2.CTY2
PE1.CTY3
Metro Ethernet
Backhaul City 3
CE
PE2.CTY6
PE2.CTY3
PE1.CTY7
CR3
Metro Ethernet
PE1.CTY4
City 7 Backhaul
Metro Ethernet
City 4
Backhaul
CE
PE2.CTY7
PE2.CTY4
CE
Copyright 2002-2013 NMC Consulting Group. All rights reserved.
PE
PE
CE
14
Out(port/label)
IP Route
2/17
PATH
ERO = {CR2, PE1.CTY5}
PATH
ERO = {PE1.CTY5}
RESV
Label = 20
RESV
Label = 3
MPLS Table
MPLS Table
In(port/Label) Out(port/label)
3/17
In(port/Label) Out(port/label)
6/20
2/20
CR1
5/3
CR2
PE1.CTY1
PE1.CTY5
Tunnel LSP
PE2.CTY1
PE2.CTY5
CR3
Constraint-Based Routing
Extended IGP
(OSPF-TE, IS-IS TE)
Routing Table
Traffic Engineering
Database (TED)
Constrained Shortest
Path First (CSPF)
User
Constraints
Explicit Route
RSVP Signaling
16
PE1.CTY5
12
VRF Green
Destination BGP Next Hop Inner Label
10.1.2.0/24
Site-1, VPN-A
10.1.1.0/24
IS-IS
CE1
Site-1, VPN-B
10.1.1.0/24
RIP
CE1
PE1.CTY5
IGP (IS-IS)
advertises
IPv4 route
10
VRF Green
CR1
CR2
VRF Green
IGP (IS-IS)
advertises
IPv4 route
PE1.CTY1
Metro Ethernet
City1
Backhaul
CE
MP-iBGP
Destination = RD_Green:10.1.2/24
Label = 10
BGP Next Hop = PE1.CTY5
Route Target = Green
PE1.CTY5
City5
PE2.CTY1
PE2.CTY5
PE
CR3
PE
Site-2, VPN-A
10.1.2.0/24
IS-IS
CE2
Metro Ethernet
Backhaul
Site-2, VPN-B
10.1.2.0/24
CE2
RIP
CE
17
MPLS L3 VPN for Enterprise: Forwarding Customer Traffic Across the BGP/MPLS Backbone
VRF Green
Destination BGP Next Hop Inner Label
10.1.2.0/24
PE1.CTY5
10
VRF Yellow
Destination BGP Next Hop Inner Label
10.1.2.0/24
PE1.CTY5
12
CR1
25
MPLS Table
In
Out
Incoming
(port/label) (port/label) (port/Inner label)
1/25
Site-1, VPN-A
10.1.1.0/24
IS-IS
CE1
Site-1, VPN-B
10.1.1.0/24
RIP
MPLS Table
VRF Green
3/30
if2
CR2
CR1
10.1.2.5
1/10
VRF Green
PE1.CTY5
PE1.CTY1
Metro Ethernet
Backhaul City 1
IGP Label(25)
VPN Label(10)
PE2.CTY1
Outgoing
interface
IGP Label(30)
VPN Label(10)
IGP Label(0)
10.1.2.5
VPN Label(10)
10.1.2.5
City 5
10.1.2.5 PE2.CTY5
CE1
10.1.2.5
Site-2, VPN-A
10.1.2.0/24
IS-IS
CE2
Metro Ethernet
Backhaul
Site-2, VPN-B
10.1.2.0/24
RIP
CE2
CR3
18
V
T
M
I
Per-Enterprise
Hierarchical shaping
(PIR/CIR)
Eth10
PE1.CTY5
Application
Classification
(5-Tuple)
RT Voice
RT Video
Mission Critical
Best Effort
RT Voice
RT Video
Mission Critical
Best Effort
V
T
M
I
S-VID
200
5Mbps shaper
Per-Enterprise
Hierarchical shaping
(PIR/CIR)
Customer
Classification
(VC-Label)
S-VID
201
Eth20
S-VID
201
VPN A
VPN A
PE1.CTY5
A pair of VC-LSPs
S-VID 200/Eth20
PE1.CTY1
CE1
S-VID 200/Eth10
City 5
Metro Ethernet
Backhaul City 1
CR1
CR2
CE2
Metro Ethernet
Backhaul
PE2.CTY5
PE2.CTY1
A pair of VC-LSPs
VPN A
A pair of VC-LSPs
RT Voice
RT Video
Mission Critical
Best Effort
PE1.CTY7
PE1.CTY7
CR3
V
T
M
I
CE3
S-VID 200/Eth30
City 7
S-VID
200
Metro Ethernet
Backhaul
PE2.CTY7
5Mbps shaper
Per-Enterprise
Hierarchical shaping
(PIR/CIR)
Eth30
S-VID
201
Copyright 2002-2013 NMC Consulting Group. All rights reserved.
19
PE
Metro Aggregation
VPN Routing (OSPF, RIP, Static, etc.)
PE
IP/MPLS Backbone
Metro Aggregation
CE
IGP (IS-IS)
VLL/
H-VPLS
H-VPLS
vc-lsp 100
CR1
VRF Green
CR2
VRF Green
S-VID 100
Site-1, VPN-A
Headquarter
CE1
S-VID 100
Metro Ethernet
Backhaul
S-VID 100
PE1.CTY1
PE1.CTY5
S-VID 100
City 5
PE2.CTY1
Site-2, VPN-A
Branch Office
CE2
Metro Ethernet
Backhaul
PE2.CTY5
VRF Green
vc-lsp 200
CR3
20
There are no constraints on the address plan used by each VPN customer. The customer can use either globally
unique or private IP address spaces. From the service provider's perspective, different customers can have
overlapping address spaces.
The CE router at each customer site does not directly exchange routing information with other CE routers. Customers
do not have to deal with inter-site routing issues because inter-site routing issues are the responsibility of the service
provider.
VPN customers do not have a backbone or a virtual backbone to administer. Thus, customers do not need
management access to PE or P routers.
Providers do not have a separate backbone or virtual backbone to administer for each customer VPN. Thus, providers
do not require management access to CE routers.
The policies that determine whether a specific site is a member of a particular VPN are the policies of the customer.
The administrative model for RFC 2547bis VPNs allows customer policies to be implemented by the provider alone or
by the service provider working together with the customer.
The VPN can span multiple service providers. While this capability of BGP/MPLS VPNs is important, this paper does
not describe inter-provider VPN solutions.
Without the use of cryptographic techniques, security is equivalent to that supported by existing Layer 2 (ATM or
Frame Relay) backbone networks.
Service providers can use a common infrastructure to deliver both VPN and Internet connectivity services.
Flexible and scalable QoS for customer VPN services is supported through the use of the experimental bits in the
MPLS shim header or by the use of traffic engineered LSPs (signaled by RSVP).
The RFC 2547bis model is link layer (Layer 2) independent.
21
26K
26K
2.4K
50K
4K
500K
4K
Juniper M-series
22
IP/MPLS Backbone
Metro Aggregation
PW (vc-lsp)
PW Signaling (Martini Signaling: Targeted LDP)
Tunnel Signaling (LDP/RSVP-TE)
VLL/
H-VPLS
Site-1, VPN-A
IGP (IS-IS)
PE1.CTY1
CR1
VLL/
H-VPLS
CR2
PE1.CTY5
Site-2, VPN-A
CE1
CE2
Metro Ethernet
City 1
Backhaul
Site-1, VPN-B
City 5
Metro Ethernet
Backhaul
PE2.CTY1
PE2.CTY5
CE1
Site-2, VPN-B
CE2
CR3
Standard:
RFC 4448 (Martini), Encapsulation Methods for Transport of Ethernet over MPLS Networks, April 2006
RFC 4447 (Martini), Pseudowire Setup and Maintenance Using LDP, April 2006
23
VCID (Virtual Circuit ID) represents the provisioned ID for the circuit between the (Ethernet port + VLAN
ID) entities provisioned in the 2 PEs (PE1.CTY1 and PE1.CTY5)
PE1.CTY5 configured:
Local S-VID200 on Ethernet20 to
be configured with VCID 2400
going to PE1.CTY1.
PE1.CTY1 configured:
Local S-VID200 on Ethernet30 to
be configured with VCID 2400
going to PE1.CTY5.
Site-1, VPN-A
S-VID 200/Eth30
CR1
PE1.CTY1
CR2
PE1.CTY5
CE2
Metro Ethernet
Backhaul City 1
Metro Ethernet
City 5
Backhaul
Tunnel LSP
PE2.CTY1
Site-1, VPN-B
PE2.CTY5
CE1
PE1.CTY1
Site-1, VPN-A
CR2
PE1.CTY5
S-VID 200/Eth20
Vc-label 2000
Metro Ethernet
Backhaul City 1
Site-2, VPN-B
CE2
CR3
S-VID 200/Eth30
CE1
Tunnel LSP
Site-2, VPN-A
CE2
Metro Ethernet
City 5
Backhaul
PE2.CTY1
Site-1, VPN-B
PE2.CTY5
CE1
VCID 2400
Port VLAN(S-VID) VC-Label Tunnel Label
30
Site-2, VPN-A
S-VID 200/Eth20
CE1
200
2000
100
CR3
Site-2, VPN-B
CE2
200
2000
100
MPLS Table
In
Out
(port/label) (port/label)
1/25
Site-1, VPN-A
PE1.CTY1
CE1
CR1
3/30
CR2
PE1.CTY5
S-VID 200/Eth30
S-VID 200/Eth20
Vc-label 2000
Metro Ethernet
Backhaul City 1
Site-2, VPN-A
CE2
Tunnel LSP
Metro Ethernet
City 5
Backhaul
PE2.CTY1
Site-1, VPN-B
PE2.CTY5
CE1
Site-2, VPN-B
CE2
CR3
D-MAC/S-MAC
C-VID
IP Packet
D-MAC/S-MAC
Tunnel Label(25)
Tunnel Label(30)
Tunnel Label(0)
D-MAC/S-MAC
D-MAC/S-MAC
S-VID(200)
C-VID
IP Packet
S-VID(200)
VC Label(10)
VC Label(10)
VC Label(10)
C-VID
D-MAC/S-MAC
D-MAC/S-MAC
D-MAC/S-MAC
C-VID
IP Packet
S-VID
S-VID
S-VID
IP Packet
C-VID
C-VID
C-VID
IP Packet
IP Packet
IP Packet
25
A customer traffic is
classified to the application
level and mapped to 4 Traffic
class
PE1.CTY1
V
T
M
I
S-VID
200
5Mbps shaper
PE1.CTY5
Application
Classification
RT Voice
Per-Enterprise
Hierarchical shaping
(PIR/CIR)
Eth30
V
T
M
I
RT Voice
RT Video
RT Video
Mission Critical
Mission Critical
Best Effort
Best Effort
5Mbps shaper
Per-Enterprise
Hierarchical shaping
(PIR/CIR)
Customer
Classification
S-VID
201
S-VID
200
Eth20
S-VID
201
3Mbps shaper
3Mbps shaper
S-VID
202
S-VID
202
20Mbps shaper
20Mbps shaper
PE1.CTY1
CE1
CR1
CR2
PE1.CTY5
S-VID 200/Eth30
S-VID 200/Eth20
PW
Metro Ethernet
Backhaul City 1
Site-2, VPN-A
CE2
Tunnel LSP
Metro Ethernet
City 5
Backhaul
PE2.CTY1
Site-1, VPN-B
PE2.CTY5
CE1
Site-2, VPN-B
CE2
CR3
26
VPLS Service
Metro Aggregation
IP/MPLS Backbone
Metro Aggregation
Per-enterprise VLAN(QinQ)
VLL/
H-VPLS
IGP (IS-IS)
Site-1, VPN-A
VSI
CR1
VLL/
H-VPLS
CR2
PE1.CTY1
VSI
PE1.CTY5
CE1
Site-2, VPN-A
CE2
Metro Ethernet
City 1
Backhaul
Site-1, VPN-B
CE1
Martini signaling
T-LDP
DU-LDP
Metro Ethernet
City 5
Backhaul
PE2.CTY1
PE2.CTY5
PE1.CTY3
PE1.CTY7
VSI
VSI
City 7
CR3
PE2.CTY3
Site-2, VPN-B
CE2
PE2.CTY7
Standard:
RFC 4762: Virtual Private LAN Service (VPLS) Using LDP Signaling, Jan. 2007
RFC 4761: RFC 4761 on Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling, Jan. 2007
RFC 4664: Framework for Layer 2 Virtual Private Networks (L2VPNs), Sep. 2006
27
VSI Green
PE1.CTY5
VSI Green
PE1.CTY1
CE
VSI Violet
Metro Ethernet
Backhaul City 1
CR1
City 5
CE
Metro Ethernet
Backhaul
CR2
CE
PE2.CTY5
CE
PE2.CTY1
VSI Violet
VSI Green
PE1.CTY7
CE
CR3
Metro Ethernet
City 7 Backhaul
VSI Violet
CE
PE2.CTY7
28
PE1.CTY5
PE1.CTY1
CE
S-VID 200/Eth20
S-VID 200/Eth10
CE
Metro Ethernet
City5 S-VID
300/Eth20
Backhaul
Metro Ethernet
City1
Backhaul
CR2
CR1
PW12
CE
CE
PE2.CTY5
PE2.CTY1
PE1.CTY7
S-VID 200/Eth30
CE
CR3
City7
Metro Ethernet
Backhaul
CE
PE2.CTY7
Local
Local
Local
Remote
Tunnel to PE1.CTY5(vc-lsp102)
Local
Remote
Tunnel to PE1.CTY5(vc-lsp302)
Remote
Tunnel to PE1.CTY7(vc-lsp103)
Remote
Tunnel to PE1.CTY1(vc-lsp201)
Remote
Tunnel to PE1.CTY1(vc-lsp301)
Remote
Tunnel to PE1.CTY7(vc-lsp203)
29
Tunnel Label(25)
S-MAC = M1
VC Label(102)
S-VID = 200
D-MAC = M2
C-VID = 100
S-MAC = M1
S-VID = 200
M1
CE
PE1.CTY1
IP Packet
PE1.CTY5
CR1 IP Packet
CE
S-VID 200/Eth20
C-VID = 100
S-VID 200/Eth10
M2
CR2
Metro Ethernet
City5 S-VID
300/Eth20
Backhaul
Metro Ethernet
City1
Backhaul
CE
CE
D-MAC = M2
PW12
PE2.CTY5
S-MAC = M1
PE2.CTY1
M3
S-VID = 300
D-MAC = M2
Tunnel Label(15)
S-MAC = M1
VC Label(103)
S-VID = 200
D-MAC = M2
C-VID = 100
S-MAC = M1
IP Packet
S-VID = 200
C-VID = 100
IP Packet
PE1.CTY7
S-VID 200/Eth30
M4
CE
CR3
C-VID = 100
City7
IP Packet
Metro Ethernet
Backhaul
CE
PE2.CTY7
Local
Remote
Tunnel to PE1.CTY5(vc-lsp102)
Remote
Tunnel to PE1.CTY7(vc-lsp103)
M1
Local
Remote
Tunnel to PE1.CTY1(vc-lsp201)
Remote
Tunnel to PE1.CTY7(vc-lsp203)
M1
Local
Remote
Tunnel to PE1.CTY5(vc-lsp302)
Remote
Tunnel to PE1.CTY1(vc-lsp301)
Once the VPLS instance with vc-id 1000 has been created, the first packets can be sent and the MAC learning process starts.
Assume M1 is sending a packet to PE1.CTY5 destined for M2 (M2 and M1 are each identified by a unique MAC address).
PE1.CTY1 receives the packet and learns (from the source MAC address) that M1 can be reached on local port Eth 10, S-VID 200; it stores this information in the FIB for vc-id
1000.
PE1.CTY1 does not yet know the destination MAC address M2, so it floods the packet to PE1.CTY5 with VC label 102 (on the corresponding MPLS outer tunnel) and to
PE1.CTY7 with VC label 103 (on the corresponding MPLS outer tunnel).
PE1.CTY5 learns from VC label 201 that M1 is behind PE1.CTY1; it stores this information in the FIB for vc-id 1000.
PE1.CTY7 learns from VC label 302 that M1 is behind PE1.CTY1; it stores this information in the FIB for vc-id 1000.
Copyright 2002-2013 NMC Consulting Group. All rights reserved.
30
S-MAC = M2
VC Label(201)
S-VID = 200
D-MAC = M1
C-VID = 100
S-MAC = M2
CE
PE1.CTY1
IP Packet
PE1.CTY5
S-VID = 200
M1
D-MAC = M1
Tunnel Label(12)
CR1 IP Packet
CE
S-VID 200/Eth20
C-VID = 100
S-VID 200/Eth10
M2
CR2
Metro Ethernet
City5 S-VID
300/Eth20
Backhaul
Metro Ethernet
City1
Backhaul
PW12
CE
PE2.CTY5
CE
M3
PE2.CTY1
D-MAC = M1
S-MAC = M2
M4
S-VID = 200
PE1.CTY7
C-VID = 100
S-VID 200/Eth30
IP Packet
CR3
City7
FIB for VPLS 1000 (PE1.CTY1)
MAC Location
Interface
M1
Local
M2
Remote
Tunnel to PE1.CTY5(vc-lsp102)
Remote
Tunnel to PE1.CTY7(vc-lsp103)
CE
Metro Ethernet
Backhaul
CE
PE2.CTY7
M2
Local
Local
M1
Remote
Tunnel to PE1.CTY1(vc-lsp201)
Remote
Tunnel to PE1.CTY7(vc-lsp203)
Local
Remote
Tunnel to PE1.CTY5(vc-lsp302)
Remote
Tunnel to PE1.CTY1(vc-lsp301)
PE1.CTY5 strips off label 102, does not know the destination M2 and floods the packet on ports Eth 20, S-VID 200 and Eth20, S-VID 300; PE1.CTY5 does not flood the packet
to PE1.CTY7 because of the split horizon rule.
PE1.CTY7 strips off label 103, does not know the destination M2 and sends the packet on port Eth30, S-VID 200; PE1.CTY7 does not flood the packet to PE1.CTY5 because of
the split horizon rule.
M2 receives the packet.
When M2 receives the packet from M1, it replies with a packet to M1:
PE1.CTY5 receives the packet from M2 and learns that M2 is on local port Eth 20, S-VID 200; it stores this information in the FIB for vc-id 1000.
PE1.CTY5 already knows that M1 can be reached via PE1.CTY1 and therefore only sends the packet to PE1.CTY1 using VC label 201.
PE1.CTY1 receives the packet for M1; it knows that M1 is reachable on port Eth 10, S-VID 200.
31
V
T
M
I
PE1.CTY5
Application
Classification
Per-Enterprise
Hierarchical shaping
(PIR/CIR)
Eth10
RT Voice
RT Video
Mission Critical
Best Effort
RT Voice
RT Video
Mission Critical
Best Effort
V
T
M
I
5Mbps shaper
Per-Enterprise
Hierarchical shaping
(PIR/CIR)
Customer
Classification
S-VLAN
201
PE1.CTY5
S-VID 200/Eth20
PE1.CTY1
S-VID 200/Eth10
Metro Ethernet
Backhaul
City5
Metro Ethernet
City1
Backhaul
Eth20
S-VLAN
201
PW12
CE
S-VID
200
CR1
CR2
CE
CE
PE2.CTY5
CE
PE2.CTY1
PW23
PE1.CTY7
S-VID 200/Eth30
CE
CR3
City7
V
T
M
I
S-VID
200
Metro Ethernet
Backhaul
CE
PE2.CTY7
5Mbps shaper
Per-Enterprise
Hierarchical shaping
(PIR/CIR)
Eth30
S-VLAN
201
Copyright 2002-2013 NMC Consulting Group. All rights reserved.
32
26K
26K
2.4K
50K
16K
2K
850K
Juniper M-series
33
MPLS Protection
34
Primary LSP
CR1
3. Network Impairment
2. RSVP Patherr and Resvtear
unicast to ingress PE
CR1 Primary LSP
CR2
PE1.CTY5
PE1.CTY1
CR3
PE2.CTY1
CR2
PE1.CTY5
PE1.CTY1
CR3
PE2.CTY1
PE2.CTY5
2. Normal Operation
Primary LSP
RSVP Hello
Secondary LSP
4. Protection Switching
Primary LSP
RSVP Hello
CR1
CR1
CR2
PE1.CTY5
PE1.CTY1
PE2.CTY1
CR3
Secondary LSP
Copyright 2002-2013 NMC Consulting Group. All rights reserved.
PE2.CTY5
Secondary LSP
RSVP Hello
1. Outage
1) Link Failure
2) Node Failure (RSVP Hello)
CR2
PE1.CTY5
PE1.CTY1
PE2.CTY1
CR3
PE2.CTY5
PE2.CTY5
Secondary LSP
35
3. Network Impairment
LSP CR2
1. Outage
1) Link Failure
2) Node Failure (RSVP Hello)
CR2
PE1.CTY5
PE1.CTY1
PE2.CTY1
PE2.CTY5
PE1.CTY5
PE1.CTY1
CR3
PE2.CTY1
PE2.CTY5
4. Re-optimization
Detours LSPs
CR3
2. Normal Operation
RSVP Hello
RSVP Hello
CR1
RSVP Hello
CR2
PE1.CTY5
PE1.CTY1
PE2.CTY1
PE2.CTY5
CR3
Copyright 2002-2013 NMC Consulting Group. All rights reserved.
36
LSP1
CR1
CR2
PE1.CTY1
LSP2
PE2.CTY1
LSP1
1. Link Failure
CR1
CR2
Bypass
Path
PE2.CTY3
PE1.CTY1
PE2.CTY5
PE1.CTY7
LSP2
PE2.CTY1
PE1.CTY5
CR3
PE2.CTY7
PE1.CTY5
When an outage occurs, the router immediately upstream from the link
outage switches protected traffic to the bypass link, then signals the link
failure to the ingress router.
Bypass Path
PE2.CTY3
CR3
LSP1: PE1.CTY3-to-PE1.CTY5
PE2.CTY5
PE1.CTY7
Like fast reroute, link protection provides local repair and restores
connectivity faster than the ingress router switching traffic to a standby
secondary path.
PE2.CTY7
However, unlike fast reroute, link protection does not provide protection
against the failure of the downstream neighbor.
LSP2: PE1.CTY1-to-PE1.CTY7
37
Link Failure
2. PE1.CTY3 switches all LSP
traffic to the NHOP bypass link
1. Link Failure
LSP1
PE1.CTY3
LSP1
CR1
NHOP
bypass
PE2.CTY3
PE1.CTY1
CR2
PE1.CTY7
LSP2
CR3
1. Node Failure
PE1.CTY3
LSP1
CR1
CR2
NNHOP
bypass
PE2.CTY3
PE1.CTY1
PE2.CTY1
PE1.CTY5
PE2.CTY5
PE1.CTY7
LSP2
PE2.CTY7
Node Failure
LSP1: PE1.CTY3-to-PE1.CTY5
LSP2: PE1.CTY3-to-PE1.CTY7
CR3
PE2.CTY5
PE1.CTY7
PE1.CTY5
PE2.CTY5
PE1.CTY1
PE2.CTY1
NNHOP
bypass
LSP2
PE2.CTY1
PE1.CTY5
CR2
NHOP
bypass
PE2.CTY3
PE1.CTY3
CR1
CR3
PE2.CTY7
38
End of Document
39
00
01
02
03
04
05
06
07
08
09
10
11
12
13
eMBMS/Mobile IPTV
CDN/Mobile CDN
Transparent Caching
BSS/OSS
Services
Cable TPS
Voice/Video Quality
IMS
Policy Control/PCRF
IPTV/TPS
LTE
Mobile
Network
Mobile WiMAX
Carrier WiFi
LTE Backaul
Data Center Migration
Carrier Ethernet
FTTH
Wireline
Network
Data Center
Metro Ethernet
MPLS
IP Routing
40