provider ethernet vlan cross connect
DESCRIPTION
Provider Ethernet VLAN Cross ConnectTRANSCRIPT
Provider Ethernet Network Challenges
Business and residential customers require an SLA with guaranteed bandwidth, jitter and delay
Network resiliency with ~50ms recovery
Huge number of MAC addresses in a single EThernet domain
Scalable VLAN networks to provide dedicated VLAN per customer in wholesale solutions
Networks and services must be secured
Networks should be kept simple to minimize CAPEX
Metro Aggregation
Voice
IP/MPLS
ISPs
ASPs
VLAN Cross Connect Taking Ethernet One Step Further
Connection-Oriented technique
Enables traffic engineering and fast recovery
Resolves MAC scalability
Resolves VLAN scalability
Inherent subscriber identification
Resolves security issues
Keep the Network simple
Metro Aggregation
Voice
IP/MPLS
ISPs
ASPs
VLAN Cross Connect
Service Model
At the boundary of the VLAN-XC domain, the VLAN ID of the outer tag (C-tag or S-Tag) can be used to associate the frame with a particular VLAN-XC connection.
If required, the outer tag (C-tag or S-tag) is preserved and transparently transported within the VLAN-XC domain
Destination MAC Source MAC Ether Type / Len Data FCSC-tag
Destination MAC Source MAC Ether Type / Len Data FCSS-tag C-tag
Concept
Standard VLAN Bridging: Switching based on MAC addresses and VLANs
VLAN Cross Connect: Cross Connect according to the ingress port and the VLAN-XC Tag, regardless of the MAC addresses
VLAN Cross Connect coexists with standard VLAN bridging, even on the same port
VLAN Cross Connect eliminates MAC learning per VLAN
VLAN Cross Connect enables up to 16M connections per port
IngressPort i
Destination MAC Source MAC VLAN Tag Ether Type / Len Data FCS
Destination MAC Source MAC VLAN Tag Ether Type / Len Data FCS
Ingress Layer 2 packet
Bridging / VLAN Cross Connect Selector
Destination MAC Source MAC TPID Ether Type / Len Data FCSTCI
PCPCFI
VLAN ID
Destination MAC PCPCFI
VLAN ID Ingress Port PCPCFI
VXC ID
VLAN-XC MethodBridging Method
802.1Q/ah Tagged FrameFrame's Outer 802.1Q VLAN Tag
VLAN ID of the frame’s outer VLAN tag acts as method selector
Frame Semantic
VLAN Cross Connect identifier has local port scope
Frame format as defined in IEEE 802.1Q
VLAN Cross Connect tagged frame allows up to 4K VLANs per port
Destination MAC Source MAC TPID Ether Type / Len Data FCSTCI
PCPCFI
VXC ID12-bit VLAN Cross Connect IDup to 4K VLANs per port
VXC-TAG
Extended VLAN Cross Connect
Frame Format as defined in IEEE 802.1ad
VLAN Cross Connect tagged frame allows up to 16M VLANs per port
Frame Semantic
Destination MAC Source MAC TPID Ether Type / Len Data FCSTCI
PCPCFI
VLAN ID
TPID TCI
PCPCFI
VLAN ID
EVXC ID24-bit VLAN Cross Connect ID
up to 16M VLANs per Port
EVXC-TAG
Process Example
BridgePort 4
Port 3
Port 2
Port 1 Port 5
Port 6
Port 7
Port 8
Cross ConnectVID=10
VID=10
VID=30
VID=40
VID=40
VID=50
VID=120
VID=130
VID=130
VID=50
VID=110
VID=140
VID=50
In Port Ingress VLAN OUt Port Egress VLAN
1 10 7 110
2 10 5 120
3 30 5 130
3 40 6 130
4 40 7 140
4 50 Bridging according to MAC Destination and VLAN ID 50
Network Reference Model
Provider Edge Nodes (PE-Nodes) reside at the boundary of the provider network and create / terminate VLAN-XC connections
Provider Internal Nodes (P-Nodes) perform VLAN Cross Connect switching
PE-Node
PE-Node
PE-Node
PE-NodeP-Node
P-Node P-Node
P-Node
P-Node
VLAN Cross Connect with CE-VLAN Preservation Example
Destination MAC
Source MAC
CE-VLAN
Destination MAC
Source MAC
VXC=1024
CE-VLAN
Destination MAC
Source MAC
VXC=236
CE-VLAN
Destination MAC
Source MAC
VXC=2636
CE-VLAN
Destination MAC
Source MAC
CE-VLAN
L2
Frame
L2
Frame
L2
Frame
L2
Frame
L2
Frame
VLAN Cross Connect Connection
PE-Node PE-NodeP-NodeP-Node
Port 6Port 3 Port 2 Port 8 Port 4 Port 12 Port 6 Port 9
Extended VLAN Cross Connect Example
Destination MAC
Source MAC
CE-VLAN
Destination MAC
Source MAC
EVXC=12045
CE-VLAN
Destination MAC
Source MAC
EVXC=645
CE-VLAN
Destination MAC
Source MAC
VXC=15320
CE-VLAN
Destination MAC
Source MAC
CE-VLAN
L2
Frame
L2
Frame
L2
Frame
L2
Frame
L2
Frame
VLAN Cross Connect Connection
PE-Node PE-NodeP-NodeP-Node
Port 6Port 3 Port 2 Port 8 Port 4 Port 12 Port 6 Port 9
Traffic Engineering
VLAN Cross Connect enables traffic engineering
Can be implemented using a domain-wide provisioning tool
GMPLS control plane once standardized
Site A Site B
E-line between two business customer sites
Selected bridged path for traffic between Site A and Site B
Traffic-engineerred path with guaranteed QoS
VLAN Cross Connect Network Resiliency
1:1 Global Protection with extra traffic
Pre-provisioned backup paths using network-wide provisioning tools
Sub-50ms recovery
Revertive or non-revertive mode
GMPLS resiliency mechanisms could be applied once GMPLS for Ethernet is standardized ( include Fast Reroute)
1:1
Protected XC
Backup XC
Scalability
VLAN Cross Connect can be naturally extended to work with hierarchical domains using tunneling
Uses standard VLAN stacking
MACEVXCTag
MACEVXCTag
MACEVXCTag
MACEVXCTag
MACEVXCTag
EVXCTag
MACEVXCTag
EVXCTag
Level n+1
Level n Level n
Provider Ethernet VLAN Cross Connect by Philippe Klein, Nurit Sprecher - Siemens Surpass Carrier Ethernet Jan 2006
IEEE Standard 802.3 ,CSMA/CD Ethernet
IEEE Standard 802.1Q ,Virtual LAN
IEEE Standard 802.1ad ,Q-in-Q
IEEE Standard 802.1ah draft ,MAC-in-MAC
Reference Documents