Beruflich Dokumente
Kultur Dokumente
Agenda
Agenda
Goal:
To allow the provider to carry customer layer-2 frames from one
endpoint to the other over an IP/MPLS infrastructure
Scenario:
The provider offers a service that allows the customer to connect
two CE devices at two sites as if they had a leased line between
them
Agenda
draft-martini-l2circuit-trans-mpls-07.txt
Distribution of VC labels via Label Distribution Protocol (LDP)
Introduces a new VC Forwarding Equivalency Class (FEC) Type
Length Value (TLV), to be used within Label Mapping
messages
draft-martini-l2circuit-encap-mpls-03.txt
Defines encapsulations for ATM, Frame Relay, Ethernet,
Ethernet VLAN, HDLC, and PPP
Format for Ethernet/VLAN Encapsulation:
PPP
or
Enet Hdr.
Tunnel
Label
VC
Label
Optional
Control
Word
Agenda
10
LSP
VC
PE-B
Foundry Proprietary - MPLS Layer 2 VPNs
12
Agenda
13
VC Label Assignment
PE-A
14
PE-B
Foundry Proprietary - MPLS Layer 2 VPNs
VC Label Signaling
PE-A
15
PE-B
16
Local label Y
Remote label X
PE-B
17
Forwarding Frames:
CE to Backbone
Apply VC and
tunnel labels
MPLS Backbone
CE interface
PE-A
Inbound lookup
based on VLAN & port number
or just port number
Outgoing MPLS Packet Format:
PPP
or
Enet Hdr.
18
Tunnel
Label
M
VC
Label
Y
Optional
Control
Word
Forwarding Frames:
Backbone to CE
MPLS Backbone
CE interface
PE-B
Incoming VC label Y indicates VLL
payload, which CE interface to send to,
and which VLAN-ID to use
Incoming MPLS Packet Format in the General Case:
PPP
or
Enet Hdr.
Tunnel
Label
N1
VC
Label
Y
Optional
Control
Word
VC
Label
Y
Optional
Control
Word
Agenda
20
Central Site
Router
UT
The VLAN-IDs on these
PEs are not required to
match with the central site
PE
T
Multinetting
w/ one subnet
to each remote
UT
Remote
T: tagged
UT: untagged
21
Customer 1
Site C
Customer 2
Site A
MPLS Backbone
Customer 1
Site A
22
Customer 2
Site C
Customer 1
Site B
Customer 2
Site B
Agenda
23
24
MPLS Backbone
Private
VLAN 10
Private
VLAN 20
Customer A
Site-2 CE Device
Customer A
Site-1 CE Device
tagged
LSP Tunnel
Virtual Circuit
PE-3
Private
VLAN 10
Private
VLAN 20
Customer A
Site-3 CE Device
25
Private
VLAN 10
Private
VLAN 20
Private
VLAN 10
Private
VLAN 20
Customer A
Site-2 CE Device
Customer A
Site-1 CE Device
tagged
PE-3
Private
VLAN 10
Private
VLAN 20
Customer A
Site-3 CE Device
26
Agenda
27
Service Terminology
28
Agenda
29
draft-lasserre-tls-mpls-00.txt:
Describes the forwarding of Ethernet/802.3 frames between
multiple customer sites, as if they were in the same layer-2
broadcast domain
Defines a new parameter VPN ID to identify PE routers
participating in the same customer VPN
draft-vkompella-ppvpn-vpsn-mpls-00.txt:
Describes MAC address learning and aging
Describes MAC address signaling
30
Functional Requirements
31
32
Possible scenarios:
Interaction with 802.1 GMRP
IGMP snooping
Static MAC multicast filters
33
Agenda
34
MPLS Backbone
SA
=X
VC
L
VC
Customer A
Site-1 CE Device
La b
a be
el =
Customer A
Site-2 CE Device
l=N
LSP Tunnel
PE-3
VPLS Forwarding
Table
Virtual Circuit
Customer A
Site-3 CE Device
35
Customer A
Site-1 CE Device
LSP Tunnel
Virtual Circuit
X
DA=
MPLS Backbone
DA
=X V
CL
a be
l=N
VC
La b
el =
M
Customer A
Site-2 CE Device
PE-3
VPLS Forwarding
Table
Customer A
Site-3 CE Device
36
Speeding up Convergence
For faster convergence:
Whenever a PE router learns a new MAC SA from the
customer side, it signals it using an LDP Address
message to its peers
Should a MAC SA age out or should the CE device get
disconnected, the PE sends an LDP Address Withdraw
message to its peers
37
MAC Signaling
PE-3 signals the new MAC to speed up convergence
PE-2
PE-1
Customer A
Site-1 CE Device
LSP Tunnel
Virtual Circuit
Customer A
Site-2 CE Device
L DP
Ms
g
Y
SA=
LD
P
Msg
MPLS Backbone
PE-3
New MAC?
Yes Notify peers.
Customer A
Site-3 CE Device
38
Facilitating Provisioning
39
VPN membership:
Each customer VPN is assigned a unique 7 octet
VPN ID
It is defined as a new interface parameter included
in the LDP messages defined in the Martini drafts
(VC FEC)
This allows PE routers to signal the VPNs they are
members of
Automatic discovery of VPLS capable routers:
IGP extensions might be used
Still in the works
Agenda
40
UT
Private
VLAN 10
Private
VLAN 20
UT
Customer A
Site-2 Router
PE-1
Private
VLAN 10
Private
VLAN 20
MPLS Backbone
Customer B
Site-2 Switch
Customer B
Site-1 Switch
UT
LSP Tunnel
Virtual Circuit
UT Untagged
T Tagged
41
PE-3
Private
VLAN 10
Private
VLAN 20
Customer A
Site-3 Router
Customer B
Site-3 Switch
2001 Foundry Networks, Inc.
The customer might run and manage their own instance of STP
The provider does not run STP on their backbone, they just carry the
customers BPDUs
STP
MPLS Backbone
STP
STP
Customer A
Site-1
STP
No STP
STP
STP
PE-3
PE-4
Customer A
Site-2
LSP Tunnel
Virtual Circuit
42
Agenda
43
Foundry offers a complete MPLS solution for the cost of the nearest
competitor!
44
The only vendor to offer a forklift free seamless migration path from
Layer 2 services right through to an MPLS enabled infrastructure.
RSVP/TE
Draft-Martini
Wire-speed ACLs and Extended ACLs
for Security and Control
RADIUS, AAA, TACACS, & TACACS+
support for Authentication and
Verification
45
Carrier-Class Features
Hot-swap capability enables
components to be added or removed
without service disruption
APS for SONET/SDH
Redundant Route Processors with
sub-second fail over
Redundant AC and/or DC Power
Load Balanced
Hot Swappable
Level 3 NEBS Tested
Investment Protection
All modules seamlessly work across
all NetIron and BigIron chassis
Consistent look and feel
10 Gbps Ready
Foundry Proprietary - MPLS Layer 2 VPNs
802.1s STP per VLAN group provides VLAN and STP scalability,
and utilizes dark fiber efficiently
46
47
Thank You!