Professional Documents
Culture Documents
Pwe VPLS
Pwe VPLS
infrastructure
native network native
network network
customer customer
network physical link network
end to end
edge to edge
provider
network
customer customer
network network
emulated link
Ethernet Ethernet
IP
conventional model:
Ethernet is a LAN technology
– last 100m
– 10s of hosts
IP is a WAN technology
– data transported in native IP
– different L2 technologies for last segment
modern Ethernet wants to be more
service
provider
network
emulated link
C C C
C CE
CE
C C
C C C
C provider network CE
CE
C C
Key
C Customer router/switch
customer 2 network CE Customer Edge router/switch customer 1 network
P Provider router/switch
PE Provider Edge router/switch Y(J)S PWE-VPLS Slide 13
L3 encapsulation
for simplicity, let’s think of an IP network :
the traditional architecture uses the following packet formats:
WAN
Eth hdr IP hdr payload Eth FCS Eth hdr IP hdr payload Eth FCS
WAN
Eth hdr IP hdr payload Eth FCS Eth hdr IP hdr payload Eth FCS
SP
network
192.115.243.19
Security
Private IP addresses
Multiple higher-layer protocols
SP resource requirements
Complex provider - customer relationship
Y(J)S PWE-VPLS Slide 15
MPLS solves IP address problem
192.115.243.19
2 1
MPLS
network
1 MPLS label
192.115.243.19 IP header
payload
Pure IP
– IPSec tunnel
– L2TP tunnel
MPLS L3VPN
– RFC4364 (ex 2547bis)
MPLS L2VPN
– VPWS / VPLS
Y(J)S PWE-VPLS Slide 17
Pseudowires
Customer
Edge
provider’s
(CE) PSN Customer
Edge
Customer
Edge Provider Provider (CE)
Edge Edge
(CE)
(PE) (PE) Customer
Customer Edge
native
Edge service
native PseudoWires (CE)
service
(CE) (PWs)
Y(J)S PWE-VPLS Slide 20
Provider Network Architecture
provider network is composed of:
• Provider routers (P routers)
• Provider edge routers (PE routers)
P P
router router
PE PE
P
router native
native router router service
service
A tunnel P
may contain router
many PWs
CE CE
scaling problem:
requires large number of LSPs
P-routers need to be aware of customer networks
CE CE
ACs transport tunnel ACs
CE PE PE CE
CE CE
PWs are bidirectional
PSN / multiplexing
payload
tunnel PW control
Payload
label(s) label word
L2TPv3 PSN
IP header (5*4 B)
session ID (4 B)
optional cookie (4 or 8 B)
control word (4 B)
payload
Y(J)S PWE-VPLS Slide 28
PWE Control Word
0000 flags FRG Length Sequence Number
0000
– Identifies packet as PW (not IP)
– used to ensure ECMP mechanisms don’t interfere with proper functioning
– 0001 for PWE OAM (VCCV)
Flags (4 b)
– not all encapsulation define
– used to transport native service fault indications
FRG
– may be used to indicate payload fragmentation
00 = unfragmented 01 = 1st fragment
10 = last fragment 11 = intermediate fragment
Length (6 b)
– used when packet may be padded by L2
Sequence Number (16 b)
– used to detect packet loss / misordering
Y(J)S PWE-VPLS Slide 29
Other Standards Bodies
ITU-T SG13
– Y.1411, Y.1412, Y.1413, Y.1414, Y.1415, Y.1452,
Y.1453, X.84
ITU-T SG15
– G.769, G.8261
MFA Forum (MPLS – Frame Relay – ATM)
– TDM over MPLS using AAL1 IA 4.0
– I.366.2 over MPLS IA 5.0
– af-aic-0178
PSN
Steps in TDMoIP
The synchronous bit stream is segmented
LAN LAN
WAN
Ethernet Ethernet
WAN
not Ethernet
Y(J)S PWE-VPLS Slide 38
Tunneling Ethernet frames
Ethernet Ethernet
X
Ethernet inside X
tunnel PW control
Ethernet Frame
label label word
P P
PE PE
P P P
based on LDP
– targeted LDP is used to communicate with opposite end-point
– 2 new FECs for PWs
– new TLVs added for PW-specific functionality
– associates two labels with PW
FEC 128
– both end-points of PW must be provisioned with a unique (32b) value
– each PW end-point independently initiates LSP set up
– LSPs bound together into a single PW
FEC 129
– used when autodiscovering PW end-points
– each end-point has attachment identifier (AI) …
P P P P
T-PE S-PE T-PE
P P P P P P
AC PE AC
CE PE CE
provider
network
AC
CE PE
PE AC CE
V B CE
CE B V
V B CE
CE
V B CE
CE
CE B V
CE
V B CE
CE
a packet from a CE:
may be sent back to a CE
may be sent to a PE via a PW
a packet from a PE:
is only sent to a CE (split horizon)
is sent to a particular CE based on 802.1D bridging
Y(J)S PWE-VPLS Slide 58
VPLS code module
VPLS signaling
establish PWs between PEs per VPLS
VPLS autodiscovery
locates PEs participating in VPLS instance
PE CE
CE PE
? PE CE
BGP LDP
multiprotocol (IPv4, IPv6, IPX, MPLS) MPLS only
highly complex protocol simpler protocol
provides routing / label distribution only label distribution
built-in autodiscovery mechanism extendable for autodiscovery
version (3 or 4)
my AS – identifier of autonomous system
hold time – max time (sec) between receipt of messages
BGP ID – sender’s BGP identifier
op len – length (bytes) of optional parameters
opt parameters - TLVs
Withdrawn Routes – list of routes no longer to be used (NLRI format- see below)
len prefix
(1B) (variable)
flags
O – optional/well-known bit
if 1 must be recognized by all BGP implementations
if W=1 and unrecognized attribute, BGP sends notification and session closed
T – transitive/nontransitive bit
if 1 and attribute unrecognized it is passed along, else silently ignored
well-known attributes are always transitive
type code
ORIGIN, AS_PATH, NEXT_HOP, MED, LOCAL_PREF,
AGGREGATOR, COMMUNITY, ORIGINATOR_ID…
Y(J)S PWE-VPLS Slide 68
BGP NOTIFICATON
version – presently 1
length - PDU length, excluding version and length fields
LDP-ID – identifies label space of sending LDP peer
– LSR-ID(4B) globally unique LSR ID
– label space ID (2B) for per-port label spaces
(zero for per-platform label spaces)
messages – zero or more TLVs (see next page)
mandatory optional
type length message-ID parameters parameters
(2B) (2B) (4B) (variable) (variable)
3.2
Y(J)S PWE-VPLS Slide 73
Provisioning VPLS
U-PE CE
PE
CE
PE MTU VPLS