Syringa Session3-5 CarrierEthernet Ciena RGregory

Carrier Ethernet Technology and Standards Update
Presented by: Rick Gregory Senior Systems Consulting Engineer May 25,2011
Ciena Confidential and Proprietary
Carrier Ethernet: Evolution, Defined
Ethernet Evolution Timeline

1970s to today
1973 1982 1985 1999 2000s Metcalfe & Boggs of Xerox PARC invented ALOHA packet-based network access protocol over a wired shared medium 3 Mb/s operation The Ethernet Blue Book Digital, Intel, Xerox (DIX) 10Mb/s operation based on the Xerox PARC concepts IEEE 802.3 Carrier Sense Multiple Access w/ Collision Detection (CSMA/CD) Formal standards definition, based on Blue Book Gigabit Ethernet standards ratified for use over copper twisted pair; vendors also implement fiber optic versions; 1000Base-T IEEE 802.3ab Fiber standards ratified for single and multimode fiber; speeds evolve to 10, 40 and (eventually) 100Gbps
Ethernet Evolution Events

Effect: Carrier Ethernet becomes Leading Transport Technology
Events Effects International standardization Unrivaled success in enterprise Ethernet is the first global network access technology Access, metro, and wide-area applications
Large number of component and equipment manufacturers Mature, transparent layer 2 technology
Lowest cost per megabit; < 8 per megabit for triple-speed NIC Simple plug-and-play installation
Ethernet over any mediaany service over Ethernet
Basic Ethernet Bridging

Unknown Destination Multicast Broadcast
(IEEE 802.1D)
Forwarding Table Address

A B C D E F
Port
1 2 2 3 3 3
A switch builds forwarding table by LEARNING where each station is (relative to itself) by watching the SA of packets it receives.
Four Important Concepts/Operations (upon switch receipt of a packet):

1. 2. 3. 4. LEARNING: The Source MAC Address (SA) and port number, if not known FORWARDING: Looking up Destination Address (DA) in table and sending to correct port FILTERING: Discarding packets if destination port = receiving port FLOODING: Sending to all other ports if DA is unknown, multicast or broadcast
Ethernets Evolution
Bandwidth Transmission Collisions Broadcast Domain Prioritization Topology Cabling Utilization Distance Originally 10 Mbps, then 100M Half Duplex Yes (CSMA/CD) Entire LAN None Bus Coax Less Than 30% Due to Collisions Limited by CSMA/CD Propagation Time Now 1 Gbps, 10G, 40G, 100G Full Duplex No Collisions (Full Duplex) VLAN Controlled 802.1p E-LAN, E-Tree, E-Line (Access, Trunks) UTP, Optical (Access, Trunks) Approaching 100% Limited Only by Media Characteristics
Standards: Current, Forthcoming, and Direction
Scaling Ethernetbeyond 802.1ad (Q-in-Q)

Preferred: Large number of customers Reality: One MAC domain for customer and Provider results in large forwarding table size 48-bit MAC address (no prefixing as in IP address) Every network switch needs to learn Destination Address (DA) of customer switches Preferred: Customer Isolation/Transparency Reality: One L2 broadcast domain for customer and provider Broadcast storms in one customers network can affect other customers and provider as well Preferred: Million+ service instances Reality: Limited VLAN space, i.e., only 4095 (i.e., 212-1) 802.1ad (Q-in-Q) suggested 16million+ instances but forwarding only to same S-tag (4095!) Preferred: Deterministic behavior for services Reality: p bit for priority but no bandwidth guarantee & arbitrary forwarding/backup paths Data plane dependent on address table, vlan partition, spanning tree, bandwidth contention
Ethernet Transport at Layer 2 & 2.5: Approaches to COE

VLAN and Stacked VLAN (Q-in-Q) Cross-Connects Explicit forwarding paths using VLAN based classification. Tunneling via VLAN tag encapsulations and translations. Defined in IEEE 802.1Q and IEEE 802.1ad specifications. Standards completed. Provider Backbone Bridging (PBB-TE) and Provider Backbone Bridging (PBB) Explicitly forwarding paths using MAC + VLAN tag. Tunneling via MAC-in-MAC encapsulations. Defined in IEEE 802.1Qay and IEEE 802.1ah specifications. Standards completed. E-SPRing Shared Ethernet Ring Topology based Protocol mechanism that delivers sub-50ms in IEEE 802.1Q and IEEE 802.1ad (Q-inQ) Ethernet Networks. Defined in ITU G.8032 specification. Standards completed. MPLS & VPLS/H-VPLS Widely deployed in the core, less so in the metro / access. Uses pseudo wire emulation edge-to-edge (PWE3) for Ethernet and multi-service tunneling over IP/MPLS. Can be point-to-point or multi-point (VPLS). Defined in IETF RFC 4364 (formerly 2547bis) and Dry Martini (IETF RFC 2026). Standards completed. Provider Link State Bridging (PLSB) Adds a SPB (Shortest Path Bridging) using IS-IS for loop suppression to make Ethernet fit for a distributed mesh and point to multi-point routing system. PBB-TE/PBB along with PLSB can operate side-by-side in the same network infrastructure. PLSB is optimized for Any to Any E-LAN and Point to Multi-Point E-Tree Network Topology Service delivery. Defined in IEEE 802.1aq specification. Standards to be completed. Target completion approximately 2H 2011. MPLS-TP Formerly know as T-MPLS (defined by ITU-T). New working group formed in IETF now called MPLSTP. Transport-centric version of MPLS for carrying Ethernet services based on PWE3 and LSP Ciena Confidential and Proprietary constructs. Defined in IETF RFC 5654. Standard to be completed. Target completion approximately 1H 2012. 9
Whats Next in Carrier Ethernet ?

802.1aq PLSB G.8032 802.1Qay PBB-TE Y.1731 Performance Management 802.1ag Fault Management 802.1ah PBB Robust L2 Control Plane Ethernet Shared Ring Resiliency
Traffic Engineered Ethernet Tunnels
Proactive Performance Management
Service and Infrastructure CFM Diagnostics Scalable, Secure Dataplane
Ethernet has steadily evolved to address more robust networking infrastructures

10
CESD Technology and Mechanisms OAM And QOS Ethernet Service Monitoring
March 2010
11
Predictable Resilience
Create a stable network, that remains stable as it scales
Design
Ciena is the leader in Connection-oriented Ethernet (COE) and provides a range of carrier-class
resiliency schemes (RSTP, MPLS, PBB-TE)

COE tunnels (PBB-TE, MPLS-TP (future)) are connection-oriented and traffic engineered Provides deterministic performance for predicable SLAs Better resiliency & stability of provider networks
802.1Q/ad domains protected using 802.1w RSTP with 50 ms restoration

PBB-TE domain supporting sub-50 ms protection (via 802.1ag Connectivity Check Messages)
12
Granular Bandwidth Control

Controlled & measurable for predictable QoS
CIR/EIR
Design
Specific service identification with rich L1-L2 classification
20/0 10/100 20/100
Voice VLAN MAC DA B L2VPN 80/200 50/100
Segmented bandwidth via a hierarchy of virtual ports Flexible priority resolution for CoS mapping
DENY IP SA 192.168.1.23 10/40 20/55
MAC SA A TCP port 80 Flow Interface
30/100
Sub-Port
Traffic profiles and traffic management at all levels in the hierarchy Specify CIR/CBS, EIR/EBS, Color Aware profiles Allows efficient service upgrades Enhance revenue with Service Stratification
(e.g. Combo of (e.g. Dept TCP/UDP port, VLAN IP DSCP, MAC, range) etc.)
Logical Port
(e.g. all the client ports of a Business)
13
Comprehensive OAM
Operate
Reduce the cost to run the network and keep services profitable
Complete standards-based Operations, Administration, and Maintenance (OAM) offering provides visibility, manageability, and controls
Proactive SLA assurance, rapid fault isolation and minimized downtime Includes L2 and L3 based performance measurement capability as a way to differentiate services
Layer 3 SLA Monitoring & Metrics: Delay, Jitter
IETF RFC 5357 TWAMP Two-Way Active Measurement Protocol
Layer 2 SLA Monitoring & Metrics: Delay, Jitter, Frame Loss
ITU-T Y.1731 Ethernet OAM
Service Heartbeats, End-to-End & Hop-by-Hop fault detection
IEEE 802.1ag CFM Connectivity Fault Management
Enhanced troubleshooting, rapid network discovery
IEEE 802.3ah EFM Physical Link
14
Technology Options for Packet Transport

Packet transport Subscriber Management IP/MPLS Service Edge & Core Metro access & aggregation Application Service Management
Routing, i.e., forward IP packets IP -over- {IPsec, GRE -over-} MPLS IP -over- {IPsec, GRE -over-} IP MPLS -over- L2TPv3 -over- IP Ethernet -over- L2TPv3 -over- IP
MPLS (L3) IP
Bridging, i.e., forward Ethernet frames based on MAC DA Ethernet -over- Ethernet: PBB Ethernet -over- MPLS: VPWS & VPLS Switching, i.e., forward of Ethernet frames based on tunnel label Ethernet -over- Ethernet: PBB-TE Ethernet -over- MPLS-TP
PBB MPLS (L2) PBB-TE MPLS-TP
Goal: cost-effective, high-performance transport

15
Mechanisms to Build the Carrier Grade Enterprise Ethernet Network
PBB PBB
IEEE 802.1ah PBB (MAC in MAC) Secure Customer Separation Service/Tunnel Hierarchy Reduced Network State
PBB-TE PBB-TE
IEEE 802.1Qay Ethernet Tunneling Deterministic Service Delivery QoS & Traffic Engineering Resiliency & Restoration
Ethernet Ethernet OAM OAM

Connectivity / Service Checks ITU Y.1731 Performance Metrics Complete Fault Management 802.1ag
16
Performance Monitoring and Connectivity Fault Management
17
Maturing Ethernet OAM into a Transport Technology

Fault Management Functions Y.1731 CCM Continuity Check LBM/LRM Loopback LTM/LTR Link Trace AIS Alarm Indication Signal RDI Remote Defect Indication LCK Locked Signal TST Test Signal MCC Maintenance Comms. Channel VSM/EXM Vendor/Experimental OAM Performance Management Functions Y.1731 FLR Frame Loss Ratio FD Frame Delay FDV Frame Delay Variation 802.3ah (2005) Link Management Functions
Discovery Link Monitoring Remote Failure Detect Rate Limiting Remote Loopback
802.1ag 802.1ag
A Partial List of Completed and Evolving Standards

IEEE 802.1Qay for PBB-TE Connection Oriented Ethernet IEEE 802.3ah EFM defines link level diagnostics and OAM ITU Y.1731 OAM functions and mechanisms for Ethernet based networks IEEE 802.1ag Connectivity Fault Management, a subset of Y.1731 MEF10 and Y.1731 describe Packet PM MEF16 describes EthernetLocal Management Interface (LMI) ITU G.8031 Ethernet Protection Switching draft-fedyk-gmpls-ethernetPBB-TE-01.txt for Control Plane
True Ethernet transport must maintain important functions from the TDM Transport Environment Traffic Engineering for deterministic bandwidth utilization Network planning: Bandwidth resources & traffic placement Performance monitoring & statistics collection Fault sectionalization & propagation mechanisms Trace & loopback facilities Local Link Management Control plane for automated end-to-end provisioning and resiliency
MEF UNI and LMI

E LMI Status E-LMI VLAN mapping E-LMI BW Admission MEF-ENNI Remote Loopback
18
PBB / PBB-TE management

802.1ag Properties
802.1ag has the concept of maintenance levels (hierarchy). This means that OAM activity at one level can be transparent at a different level. 802.1ag has clear address and level information in every frame. When one looks at an 802.1ag frame, one knows exactly Where it originated from (SA MAC) Where is it going (DA MAC) Which maintenance level is it What action/functionality does this frame represent. Design Inherently address the OAM aspects for MP2MP connectivity (e.g. VLANs)
19
The New Ethernet OAM

Standards-based IEEE 802.1ag and ITU Y.1731
Maintenance End Point = MEP Maintenance Intermediate Point = MIP
802.1ag Maintenance levels/hierarchy

customer demarcs Adapt Service OAM (SID) UNI Link Link OAM Adapt UNI Link
Continuity Check (Fault)

Multicast/unidirectional heartbeat
Trunk OAM
Loopback (MEP/MIP Fault Connectivity)

Unicast bi-directional request/response
MEP
Edge Switch
Link OAM
MIP
Transit Switch
MEP
Edge Switch
Link OAM
Traceroute (MEP/MIP Link Trace - Isolation)

Trace nodes in path to a specified target
NNI Link
NNI Link
Discovery
Service (e.g. all PEs supporting common service instance) Network (e.g. all devices common to a domain)
Performance Monitoring
Frame Delay Frame Delay Variation Frame Loss
Conceptually: -monitor the trunk or the service or both Service

802.1ag
Trunk
802.1ag
Built-in and on-switch

20
Carrier Ethernet Technology and Standards Update PBB/PBB-TE/E-SPRing G.8032/PLSB and MPLS/VPLS/HVPLS/MPLS-TP
Presented by: Rick Gregory Senior Systems Consulting Engineer May 25,2011
21
Provider Backbone Bridging (PBB) IEEE 802.1ah
22
Provider Backbone Bridge Introduction

IEEE 802.1ah is the Provider Backbone Bridge standard
Payload C-VID S-V DA SA I-SID B-VID B-DA B-SA 802.1ah

Provider Backbone Bridges
Also known as Mac In Mac (MiM) encapsulation PBB solves several of todays Ethernet challenges
Service Scalability up to 16 millions VPNs Customer Segregation Overlapping VLANs supported MAC Explosion Customer MAC addresses only learned at edge Security Customer BPDUs are transparently switched
23
Ethernet FramesBefore and After

Payload Payload Payload
Ethertype Ethertype Ethertype
Payload
Ethertype
C-VID
Ethertype
C-VID
Ethertype
VID
Ethertype
S-VID
Ethertype
S-VID
Ethertype
SA DA
SA DA
SA DA
SA DA I-SID
Ethertype
Pre-existing (unchanged) New (backbone)
802.1
SA = Source MAC address DA = Destination MAC address VID = VLAN ID C-VID = Customer VID S-VID = Service VID I-SID = Service ID B-VID = Backbone VID B-DA = Backbone DA B-SA = Backbone SA
basic
802.1Q
tagged VLAN
802.1ad
QinQ Provider Bridge
B-VID
Ethertype
B-SA B-DA
802.1ah
MACinMAC PBB
24
802.1ah PBB Encapsulation Header as used by PBB-TE

B-DA MAC B-SA MAC Tunnel Ethertype 0x88A8 B-TAG P D C E B-VID P I Service Ethertype 0x88C8 P C P
D A S A
I-TAG D R R E E E I-SID I S1 S2
Backbone Destination MAC address Field Backbone-DA Backbone-SA B-TAG Ether-type B-VID B-TAG DEI B-TAG PCP I-SID I-TAG Ether-type RES1 RES2 I-TAG DEI I-TAG PCP
Backbone Source MAC address
58 Bit Tunnel Address Size Value 6 bytes 6 bytes 2 bytes 12 bits 1 bit 3 bits 24 bits 2 bytes 2 bits 2 bits 1 bit 3 bits Tunnel destination MAC address. This must be a Unicast address only. Multicast MAC addresses are not allowed to be specified for this field. Tunnel source MAC address used to identify this node in the network. 0x88A8 (default) Tunnel VID (802.1Q compliant). Drop Eligibility Indicator: 1=Drop eligible, 0=Not drop eligible Tunnel Priority Code Point (0-7) Service identifier (1 16 million) 0x88C8 (default) Dont care Dont care Drop Eligibility Indicator: 1=Drop eligible, 0=Not drop eligible Service Priority Code Point (0-7)
25
PBB: Solving Current Ethernet Challenges

Ethernet Challenges: Service Scalability Customer Segregation MAC explosions, Storms Broadcast
Up to 16 million service instances using 24 bit service ID ISID Overlapping V-LANs supported Stops MAC Explosions and Broadcast Storms at MACin-MAC Demarcation Point Customer MAC is completely separate from Backbone MAC
Learning, Forwarding, Flooding Control
Architected to build E-LAN, E-Tree and E-Line services

26
Provider Backbone Bridging With Traffic Engineering (PBB-TE) IEEE 802.1Qay
27
PBB-TE (IEEE 802.1Qay)
MPLS Services
(RFC 2547 VPN, PWs etc.)
Ethernet Services
(EVPL, ELAN, ELINE, Multicast)
PBB-TE
> Keep existing Ethernet, MPLSFR/ATMANY & ALL services > Capitalize on Ethernet as transport for significant savings > Existing network-friendly solution!
28
PBB-TE
PBB E-LINE
Traffic engineered PBB-TE trunks

PBB
Ethernet Metro
E-LINE
P2P traffic engineered trunks based on existing Ethernet forwarding principles Reuses existing Ethernet forwarding plane Simple L2 networking technology Tunnels can be engineered for diversity, resiliency or load spreading 50 ms recovery with fast IEEE 802.1ag CFM OAM
29
PBB-TE
Solving Current Ethernet Challenges
Ethernet Challenges:
Full segregation in P2P model
Customer Segregation Traffic engineering Spanning Tree challenges: Stranded bandwidth Poor convergence MAC explosions Security
End to End TE With QoS & 50 ms recovery Disable STP No blocked links Fast 802.1ag convergence
MAC Explosions Eliminated Backbone MAC is Completely Different Than Customer MAC
30
Provider Link State Bridging (PLSB) IEEE 802.1aq
31
Introducing.PLSB
PBB-TE is a trivial change to the Ethernet dataplane that has huge Benefits Explicit enforcement of configured operation Ability to have non STP based VLANs Similarly PLSB requires a further trivial change with huge Benefits Adding loop suppression to make Ethernet fit for a distributed routing system PBB-TE, PLSB and existing Ethernet control protocols can operate side-byside in the same network infrastructure Consequence of ability to virtualize many network behaviors on a common Ethernet base.
32
PLSB Approach
If Ethernet is going to be there.use it! Take advantage of Ethernets more capable data plane Virtual partitions (VLANS), scalable multicast, comprehensive OAM PLSB uses a Single (1) Link State Control Plane protocol IS-IS IS-IS topology and service info (B-MAC and I-SID information) Integrate service discovery into the control plane PLSB nodes use link state information to construct unicast and per service (or I-SID) multicast connectivity
Combines well-known networking protocol with well-known data plane to build an efficient service infrastructure
33
VPLS Operation
Typical VPLS Implementation:
Required for Auto-Discovery
Separate RR topologies (to help scale) Eases burden of statically managing VSI PWEs
VPN Protocols
BGP-AD
Signal PWEs
N2 manual session creation
E-LDP
Base LDPs: build LSP tunnels

Redundant to IGP (same paths)
Tunnel LSP Protocols
LDP or RSVP-TE
Base IGP: Topology

Required for network topology knowledge
IGP (IS-IS or OSPF)
Physical Links
Link layer headers striped off, label lookup per node
SONET, SDH, Ethernet, etc
VPLS CONTROL PLANE

34
PLSB Operation
PLSB Implementation:
One IGP for Topology & Discovery Tunnel + VPN Protocols -One protocol now provides - Auto-discovery - Fast fault detection - Network healing - Shortest path bridging - Intra-AS only Link State Protocol - Dijkstra's algorithm for best path - No VSI awareness required at Edge - Once Standardized Ciena could deploy - Own I.P. from MEN acquisition - Target IEEE 802.1aq Ratification 2H 2011
PLSB (IS-IS)
Ethernet
Physical Links: - Link layer headers reused as a label lookup through every node
Minimizing control plane = Minimized complexity = Reduced cost

35
PPB/PBB-TE and PLSB Delivers

E-LAN Any to Any E-LINE Point to Point CESD CESD
E-TREE Point to Multi-Point
CESD
Characteristics: PLSB 200-500ms resiliency PBB-TE 50ms resiliency Optimized per service multicast Feature Rich OAM SLA and Service Monitoring Latency Monitoring No Spanning Tree Protocol Value: Simplest Operations Model Less Overhead and Network Layering Most Cost Effective Equipment Efficient Restoration
36
Ethernet Shared Ring (E-SPRing) ITU G.8032
37
G.8032 Objectives and Principles

Use of standard 802 MAC and OAM frames around the ring. Uses standard 802.1Q (and amended Q bridges), but with xSTP disabled. Ring nodes supports standard FDB MAC learning, forwarding, flush behaviour and port blocking/unblocking mechanisms. Prevents loops within the ring by blocking one of the links (either a pre-determined link or a failed link). Monitoring of the ETH layer for discovery and identification of Signal Failure (SF) conditions. Protection and recovery switching within 50 ms for typical rings. Total communication for the protection mechanism should consume a very small percentage of total available bandwidth.
38
ITU G.8032 Ethernet Rings

a.k.a. E-SPRing (Ethernet Shared Protection Rings) E-SPRing Values
Efficient connectivity (P2P, multipoint, multicast) Rapid service restoration (<50 msecs) Server layer technology agnostic (runs over Ethernet, OTN, SONET/SDH, etc) Client layer technology agnostic (802.1 (Q, PB, PBB, PBB-TE), IP/MPLS, L3VPN, etc) Fully Standardized (ITU-T SG15/Q9 G.8032) Scales to a large number of nodes and high bandwidth links (GE, 10G, 40G, 100G)
E-Line, E-LAN, E-Tree
Major Ring
Fault
Sub Ring
Sub Ring Sub Ring
Deterministic 50ms Protection Switching

Full service compatibility
Grow ring diameter, nodes, bandwidth
Multi-Layer Aggregation with Dual Homing
39
The Ciena G.8032 Solution

FORWARDING PLANE CONTROL PLANE
Sub-50ms protection for E-LINE, E-TREE, and E-LAN services CONTROL PLANE Guarantees loop freeness with prevention of frame duplication and reorder service delivery Utilizes existing IEEE defined FORWARDING PLANE Bridging and IEEE 802.3 MAC Supports IEEE 802.1Q, 802.1ad, and 802.1ah
MANAGEMENT PLANE
Ciena G.8032 solution MIB Generic Information Model Supports Ethernet OAMPLANE MANAGEMENT (802.1ag, Y.1731) fault and performance management Operator commands (e.g., manual/force switch, DNR, etc.)
STANDARDIZED
ITU-T Q9/15 G.8032 (ERP) IEEE STANDARDIZED 802.3 MAC IEEE 802.1Q, 802.1ad, 802.1ah Ethernet OAM IEEE 8021.ag Ethernet OAM ITU-T Y.1731
Ciena PORTFOLIO
Carrier Ethernet: 318x, 3190, 3911, 3916, 3920, 3930, 3931, Ciena 5140, 5150 3940, 3960, PORTFOLIO Transport: OME 6500, OM 5K, OME 6110/6130/6150
NETWORKING SCALABLE
Physical/server layer agnostic Supports SCALABLE rings heterogeneous Leverages Ethernet BW, cost, and time-to-market curve (1GbE10GbE40GbE100GbE) Dedicated rings Ring interconnect via shared node NETWORKING and dual node Dual-homed support to provider network technologies (e.g., PB, PBB, PBB-TE, MPLS, etc.)
40
Example G.8032 Network Applications

Wireless Backhaul
N x T1/E1s CO
Business Services Private Build

Metro Packet Transport
BSC Voic e Branch Office #2
Ethernet
HQ Data
Ethernet
Access G.8032
Metro/Collector G.8032
Metro/Collector G.8032
RNC
T1/E1s
Data
PBX
Standalone G.8032
PSTN
Access G.8032 Metro Packet Transport Other Core Technology
Ethernet
BSC Voic e
PBX
T1/E1s T1/E1s
Ethernet
Data RNC
PBX
Branch Office #3
Branch Office #1
Business Services - Access

Branch Office #1
Business Services DSL Aggregation

HQ Data
Ethernet Ethernet
Metro Packet Transport
PBX T1/E1s
Ethernet
Metro/ Collector G.8032
Branch Office #2 Ethernet T1/E1s PBX Branch Office #3 Ethernet T1/E1s
Metro/ Collector G.8032
PSTN
Access G.8032 Metro Packet Transport Other Core Technology
Standalone G.8032
HQ
Ethernet
Metro Core LAG
Data
Ethernet

PBX
PSTN
41
General G.8032 Concepts
42
What is a Channel Block?

Blocking Port
A Channel block can be an ingress/egress rule

placed on a G.8032 node port The Channel block rule specifies that any traffic with a VID received over this port within a given VID space should be discarded NOTE: The Channel block function prevents traffic from being forwarded by the G.8032 node, however, it does not prevent traffic from being received by Higher Layer Entities (e.g., G.8032 Engine) on that node Each G.8032 ringlet needs at least a single channel block installed F
Channel Block Function
43
What is a Ringlet (a.k.a. Virtual Ring)?

A Ringlet is a group of traffic flows over the ring that share a common provisioned channel block NOTE: It is assumed that each traffic flow has a VLAN associated with it The traffic flows within a Ringlet is composed of A single ringlet control VID (R-APS VID) A set of traffic VIDs A group of traffic flows over the ring can be identified by a set of VIDs Multiple Ringlets on a given Ring can not have overlapping VID space
Ringlet 2 Ringlet 1
44
Please view in animation mode
G.8032 E-SPRing Failure/Restoration

1
A
2
B
F E D
F E D
a) Normal configuration
b) Ring span failure occurs
3
A B
4
A B
F E D
F E D
R-APS messages
R-APS messages
c) LOS detected d) Port blocking applied e) APS message issued
f) R-APS causes forwarding database flush g) Ring block removed
45
VI
WTR
R-APS(NR)
R-APS(NR)
Recovery Events
E
Guard Timer
D
Guard Timer
8. Ring span recovery detected 9. Tx R-APS(NR) and start Guard Timer
10. When RPL owner Rx R-APS(NR), it starts WTR timer.
VII
VIII
R-APS(NR,RB)
11. When WTR expires, RPL block installed, Tx R-APS(NR,RB) 12. Nodes flush FDB when Rx R-APS(NR,RB) 13. Nodes remove port block when Rx R-APS(NR,RB)
14. Normal configuration
46
G.8032 Product Specifications
47
G.8032 E-Spring Interconnections

a
Phase 1
Standalone Ring
Phase 1
Standalone Rings, LAG interconnect
E-SPRing
E-SPRing1
E-SPRing2
Phase 1
If each ring is different Virtual Switch
Phase 2
Dual-Homed Rings (Major and Minor rings)
E-SPRing1
E-SPRing2
E-SPRing1
E-SPRing2
e
E-SPRing
Phase 2
Dual-Homed Ring
Dual Homing
48
Phase 2 Availability
Chaining Rings and R-APS Protocol

Major-Ringlets and Sub-Ringlets are used to chain rings.
Dual-Homed Rings (Major and Minor rings) are not supported in SAOS 6.8
There can be only one R-APS session running for a given VID Group on a ring span.
On a Sub-Ringlet, the provisioned block for the data path is at the RPL owner (or on each side of a link fault), and the control path ALWAYS has its blocks where the SubRinglet is open.
Data Path example
Control Path example
MajorRinglet
MajorRinglet
SubRinglet
E E
SubRinglet
E E
49
G.8032 Terms and Concepts

Ring Protection Link (RPL) Link designated by mechanism that is blocked during Idle state to prevent loop on Bridged ring RPL Owner Node connected to RPL that blocks traffic on RPL during Idle state and unblocks during Protected state Link Monitoring Links of ring are monitored using standard ETH CC OAM messages (CFM) Signal Fail (SF) Signal Fail is declared when ETH trail signal fail condition is detected No Request (NR) No Request is declared when there are no outstanding conditions (e.g., SF, etc.) on the node Ring APS (R-APS) Messages Protocol messages defined in Y.1731 and G.8032 Automatic Protection Switching (APS) Channel - Ring-wide VLAN used exclusively for transmission of OAM messages including R-APS messages
50
Ring Idle State

A. Physical topology has all nodes connected in a ring
ETH-CC ETH-CC ETH-CC ETH-CC ETH-CC
RPL
ETH-CC
RPL Owner
ETH-CC
the RPL (link between 6 & 1 in figure) C. Logical topology has all nodes connected without a loop. D. Each link is monitored by its two adjacent nodes using ETH CC OAM messages E. Signal Failure as defined in Y.1731, is trigger to ring protection Loss of Continuity Server layer failure (e.g. Phy Link Down)
ETH-CC ETH-CC
ETH-CC ETH-CC
2 3
1 4
RPL
6 5
Physical topology 2 3 1 4 6 5
Logical topology
51
ETH-CC
B. ERP guarantees lack of loop by blocking
Protection Switching Link Failure

A. Link/node failure is detected by the nodes adjacent to the failure. B. The nodes adjacent to the failure, block the failed link and report this failure to the ring using R-APS (SF) message C. R-APS (SF) message triggers RPL Owner unblocks the RPL All nodes perform FDB flushing A. Ring is in protection state B. All nodes remain connected in the logical topology.
RPL
RPL Owner
R-APS(SF)
R-APS(SF)
R-APS(SF)
R-APS(SF)
2 3 2 3
52
1 4 1 4
RPL
1 4 1 4
RPL
6 5 6 5
3 5 Physical topology 6 5 2 3
Logical topology
Protection Switching Failure Recovery

A. When the failed link recovers, the traffic is kept blocked on the nodes adjacent to the recovered link B. The nodes adjacent to the recovered link transmit R-APS(NR) message indicating they have no local request present C. When the RPL Owner receives RAPS(NR) message it Starts WTR timer D. Once WTR timer expires, RPL Owner blocks RPL and transmits R-APS (NR, RB) message E. Nodes receiving the message perform a FDB Flush and unblock their previously blocked ports F. Ring is now returned to Idle state 3
R-APS(NR, RB)
RPL
RPL Owner
R-APS(NR,R-APS(NR) RB)
R-APS(NR)
R-APS(NR)
R-APS(NR)
2 3
1 4
RPL
6 5
1 4 1 4
RPL
6 5 6 5
3 Physical topology 6 5 2 3
1 4
Logical topology
53
Multi Protocol Label Switching (Layer 3 IETF RFC 4364 / aka 2547bis) (Layer 2 IETF RFC 2026 / Dry Martini) (Layer 2 IETF RFC 5654 / MPLS-TP) (MPLS/VPLS or PBB/PBB-TE)
54
Ethernet Access Network Choices

Legacy Ethernet (No MEF compliance) Carrier Class Ethernet (MEF compliance) 1. Connection-less Ethernet 802.1Q or 802.1ad or 802.1ah: VLANs 1. Connection Oriented Ethernet 802.1Qay (PBB-TE): VLANs MPLS-TP: Traffic Engineered PWs over LSP IP control plane based IP or MPLS VPNs IP VPN: Ethernet over L2TPv3 over IP MPLS VPN: Ethernet PW or VLAN over LSP
1.
55
MPLS vs. Ethernet Data Plane (+OAM)

MPLS metro network L3 (IP/MPLS): terminate Ethernet & forward IP frames over IP PW in MPLS LSP over Ethernet port L2 (VPLS/VPWS, MPLS-TP): forward Ethernet frames over Ethernet PW in MPLS LSP over Ethernet port Multiple, varied data planes: IP, PW, LSP, Ethernet complex hw/sw interactions resulting in higher cost1 complex OAM MPLS-TP LSP OAM yet to be defined
Packet transport
Subscriber Management IP/MPLS Service Edge & Core
Metro access & aggregation
Application Service Management
Ethernet (PBB-TE) metro network L2: forward Ethernet frames over Ethernet EVCs over Ethernet port Fewer data planes and OAM levels Ethernet Service and Network/Link Simpler hw/sw for >40% lower cost2 IP awareness for dataplane behavior but no need for OAM at IP layer Less complex OAM using 802.1ag and Y.1731 for Ethernet service and network/tunnel layers Ethernet (PB, PBB) can enable Pt-Mpt and MptMpt, in addition to Pt-Pt
Reid, Willis, Hawkins, Bilton (BT), IEEE Communications Magazine, Sep 2008 2 (40-60% less) McKinsey & Co., Jan 2008; (40% less) CIMI Corp, Jul 2008
1
IP, Ethernet PW LSP Ethernet Complex
Service Network
IP, Ethernet VLAN (EVC) Ethernet Simpler
Data Plane
56
MPLS vs. Ethernet Control Plane (+OAM)

MPLS metro network Complex link-by-link label swapping inherent source of unreliability1 Complex L3 control plane for PW/LSP signaling/routing (& PW stitching at core edge) PW/LSP labels: LDP or BGP LSP setup: RSVP-TE (signaling), OSPFTE (routing) MPLS-TP can avoid L3 control plane; use complex NMS-based link-by-link LSP config instead Complex protocol couplings resulting in processing complexity and higher opex3
Packet transport
Subscriber Management IP/MPLS Service Edge & Core
Metro access & aggregation
Application Service Management
Ethernet (PBB-TE) metro network Complete, global Ethernet header BEBs SA/DA+BVID for tunnel No label switched path setup needed E2E visibility, connectivity verification Simpler L2 control plane for discovery only No distributed routing/signaling needed Metro hub-&-spoke (vs. core mesh) affords explicit failure mode config4 <=9 such modes in large metro 12% lower opex (future: up to 44%)4 Simpler OAM: reliable & lower opex1,3
Ethernet provides just enough control & data plane functionality to meet all service needs while containing cost and complexity
3 4
Seery, Dunphy, Ovum-RHK, Dec 2006 CIMI Corp., Netwatcher newsletter, Jul 2008
57
PBB/PBB-TE or VPLS/MPLS?
Caution: Unscientific poll results
Ethernet is the new paradigm
Deterministic Transport with OAM&P
Light Reading webinar: Building Converged Services Infrastructure http://www.lightreading.com/webinar_archive.asp?doc_id=28415
PBB-TE perceived to offer cost advantages CO-Ethernet is one option
Light Reading webinar: PBB-TEs Winning Ways http://www.lightreading.com/webinar_archive.asp?doc_id=28511
Light Reading webinar: Building Converged Services Infrastructure http://www.lightreading.com/webinar_archive.asp?doc_id=28415
58
PB/PBB/PBB-TE and MPLS Tunnel Inter-working

Ingress and egress virtual interfaces provide greatest flexibility and interoperability with existing and emerging technologies Dual-tag push/pop/swap enables multi-protocol interworking (e.g., PBB-TE, MPLS) Standard IEEE and popular Cisco-proprietary protocol handling enable robust L2VPNs
IEEE and Cisco proprietary L2 control frame tunneling
Access / Aggregation Q-in-Q or
Metro MPLS H-VPLS or PBB/TE
Core
MEF UNI
PBB/PBB-TE Dual tag push/pop/swap
EVC EVC
Q-in-Q or PBB-TE Tunnel Q-in-Q or PBB-TE Tunnel
MPLS LSP Q-in-Q or PBB-TE Tunnel

EVC
EVC (PW) EVC (PW)
Seamless interworking between PB (Q-in-Q), PBB/PBB-TE and MPLS simplifies the handoff between domains
59
PBB-TE provides cost-effective robust packet transport, but why not combine that with IP/Ethernet service intelligence on one node?
i.e. IP Routing isnt deterministic, but it has useful service layer functions multicast, differentiated services treatment Why not use IP/MPLS nodes? IP for services Multicast L3 Prioritization MPLS for services VPLS: Mpt-Mpt VPWS: Pt-Pt MPLS-TP for transport Pt-Pt Need a Carrier Ethernet Switch that combines IP/service-aware switching while retaining carrier-grade packet transport qualities!
Because Carrier Ethernet Switches are >40% lower cost than IP/MPLS Carrier Ethernet Switch/Routers
(40-60% less) McKinsey & Co., Jan 2008 (40% less) CIMI Corp, July 2008
60
Ethernet data plane

Functions Ethernet Aggregation PBB-TE / PBB Native Ethernet (E-o-E) with less overhead. Scalability with 24-bit I-Sid MPLS-TP Same as MPLS. Need PW & tunnel headers (E-o-PW/LSP-o-E). Can nest aggregation layers. May help with scaling Forwarding labels Unique end-to-end: DA+B-Vid Same as MPLS. Scales as # of endpoints (nodes) + service classes, (tunnel) labels can be per hop or end-to-end if any. May scale as # of links + service classes, if any. Need coordination across links along a path
Transparency & Separate MAC address space (provider/Backbone Transparent transport for Ethernet clients Isolation vs. customer) No MAC learning defined but possible MAC learning can be enabled for PBB-TEs B-vid space Topology ELINE (Point-Point): Yes ETREE (Point- Multipoint): Yes ELAN (Multipoint): Yes ELINE (Point-Point): : Yes ETREE (Point- Multipoint): : Yes ELAN (Multipoint): Needs either Pt-Mpt or full mesh of Pt-Pt LSP tunnels. May use VPLS model but need complex MPLS control plane & also requires either Pt-Mpt or full mesh of PtPt PWs. Complex: additional PW/LSP layers. Nested tunnels can introduce OAM/provisioning complexity
Layering, Partitioning, Hierarchy Peering
Simple: Backbone MAC address space w.r.t. Customer MAC address space
MEFs ENNI and CoS IA are work in progress for Work in progress. Peering with MPLS network may mean service level. IEEE already provides interface and complex MPLS control plane. Also, need PW signaling endlink models to-end. PW capability along with protocol zoo for ATM/FR IW
other services Adjunct platforms where needed to achieve ATM/FR IW. Possible to use PWs if necessary
61
Ethernet Management plane

PBB-TE / PBB OAM Reuse 802.1ag/Y1731. MPLS-TP Use 802.1ag/Y.1731 for Ethernet EVC
(a) CCM needs to use unicast DA (allowed by 802.1ag PW/LSP is work in progress and already defined in Y.1731). Also, MIPs need to intercept if DA is of MIP. (b) LBM/LBR in most cases, will use same VID in forward and reverse direction and so no issues. (c) LTM/LTR is possible if MIPs can intercept/ignore frames as needed. New TLV with MIP DA to be defined
End-to-End visibility MEG levels
I-Sid for service (EVC) DA+B-vid for tunnel
PW/LSP is work in progress
Less oam levels: Ethernet customer flow, Ethernet EVC,More oam levels: Ethernet customer flow, Ethernet operator and transport / link EVC, LSP tunnel(s), operator and transport / link End-to-end (1+1, m:n), IEEE Link Aggregation G.8031/G.8032 Transport network like using APS for 1+1/m:n PW and LSP level, span/segment/end-to-end may use fast re-route if control plane present
Protection
62
MPLS Protocols (net-net)

MPLS Provides: Virtually unlimited service scalability Eliminates MAC table explosions 50 ms resiliency OAM Traffic Engineering Bandwidth guarantees MPLS Requires IGP+TE RSVP-TE FRR BFD PWE3 control plane VPLS control plane H-VPLS/ MS-PW for scalability MPLS forwarding plane upgrades
Requires RSVP-TE + FRR everywhere OAM relies on the control plane Limited performance monitoring Requires DS-TE for multiple bandwidth pools
PBB-TE eliminates these protocols
Increased OPEX Increased CAPEX
MPLS control plane server cards 63
PBB/PBB-TE Protocols (net-net)

Carrier Ethernet Service Delivery Provides: Virtually unlimited service scalability Eliminates MAC table explosions 50 ms resiliency Service OAM Traffic Engineering Bandwidth guarantees Sub 50 ms recovery with PBB-TE Deterministic and scalable in-band OAM Standardized performance monitoring PBB-TE provides traffic engineering and bandwidth guarantees Standardized Ethernet forwarding and OAM No changes to the hardware No huge learning curve Still just forwarding Ethernet Enterprise demands Simplicity
64
Carrier Ethernet Delivers: Provider Backbone Bridging Provider Backbone Bridging with TE IEEE 802.1ag, ITU Y.1731
Positioning Carrier Ethernet to Enterprise Customer
65
Packet Access Comparison

Key aspects Connectionless Ethernet IP VPNs MPLS
Interoperability - Ethernet MEF Ethernet UNI/ENNI MEF Ethernet Services Interoperability - other MPLS NNI ATM/FR/TDM/MPLS UNI Transparency Address & control protocols Scalability Network & Services (Pt-Pt & MPt) Reliability 50-100msec protection Disjoint Working/Protect paths
Connection Oriented Ethernet

MPLS-TP
(Work In Progress)
PBB/PBB-TE

Need IWF, dry Martini
Need IWF (L2TP, GRE)

FRR 1+1 L3 L2
TBD TBD

Need IWF, dry Martini
Need IWF (L2TP, GRE)
Manageability Fault sectionalization Service & Network OAM/PM Deterministic Perf/QoS Guaranteed rate, latency/jitter/loss
and Confidential and Proprietary Low CapEx CienaOpEx
66
Positioning Carrier Ethernet to Enterprise

1. 2.
VPLS/H-VPLS/MPLS
Multiple VPN & Tunneling Control Plane Protocols Optimized for Large Carrier Customers with MPLS backbone and IP/MPLS knowledgeable and trained Engineering Staff
1. 2.
PBB/PBB-TE/E-SPRing
spend (low cost plug & play Network)
PBB-TE/PBB/E-SPRing Forwarding Plane Only Optimized for Enterprise Customers looking to minimize OPEX and CAPEX
3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15.
Requires Extensive Engineering 2 to 3 9s SLAs Ethernet Service Delivery Second/s to Sub-second Restoration (R-STP/FRR) Q-in-Q Stacked VLANs 4096 maximum High priced MPLS HW and SW based Routers Requires strong L3/IP/MPLS Knowledge/Config Locked into a Vendors MPLS Products/Solution Desire to fill unused capacity Higher % sales of L3VPN Solving core not aggregation Desire protocols to provision Techs trained for L3/IP config Difficult to deploy @ customer 1. 2. 3. Field techs not trained Higher $$$ CPE More complex configuration
3.
CCIE type skills Not Required (+ Ethernet and SONET knowledgeable Engineers Get it !)
4. 5. 6. 7. 8. 9. 10.
Need to Lease Fiber (Typically unless you already own) High Reliability, Resiliency, Scalability, and Simplicity 4 to 5 9s SLAs Ethernet Service Delivery Sub 50ms Protection Switching / Restoration (IEEE 802.1ag) Ethernet is the single End to End Protocol Language Spoken Excellent OAM (Y.1731 and 802.1ag) Jitter/Latency Stop MAC/VLAN explosions and Broadcast Storms (Separate MAC Tables Customer LAN & Backbone)
11.
Minimizes MAC Learning and Distribution/Forwarding (True MAC learning Demarcation between LAN and MAN/WAN)
12. 13. 14. 15. 16.
16 Million VPNs (IEEE 802.1ah Mac-in-Mac), PBB only Low CAPEX and OPEX Economics SONET Like Skill sets to Configure and Manage Network Ethernet Open Standards 3rd Party Vendor Interop benefits Transport over GE Microwave
67
Carrier Ethernet Service Delivery

Summary
Increased Simplicity with universally acknowledgeable Ethernet MAC Ethernet MAC is the single End to End Protocol Language (No Multi-Protocol Translation, Ethernet only) Sub 50ms Protection Switching / Restoration (IEEE 802.1ag Network Continuity Message that is tunable) Traffic engineered tunnels with B-MACs B-VID pcp (p-bit) Classification Prioritization Monitor Performance End to End (Varying Delay-Jitter/Delay-Latency/Loss) in and out of Network at Layer 2 Loop Back Message / Link Trace Message (SONET like) Loopback troubleshoot testing on Ethernet Stop MAC/VLAN explosions and Broadcast Storms Minimize MAC Learning and MAC Distribution (Separate MAC Demarc between LAN and MAN/WAN) 24 bit ISID delivers 16 Million VPNs (IEEE 802.1ah Mac-in-Mac) Only learns and forwards based on Backbone MAC Addresses (LAN MAC learning stays in the LAN) Lower OPEX, SONET and/or Ethernet Engineering Skill sets/experience to Configure and Manage Network Lower CAPEX, Open to inter-operate with any 3rd Party Ethernet Products, Ethernet Price Points Ethernet Switch Where You Can IP/MPLS Route Where You Must Improved Reliability with IEEE 802.1ag QoS (Quality of Service) without Control Plane Complexity with IEEE 802.1Qay PBB-TE Superior OAM with IEEE 802.1ag and ITU Y.1731
Enhanced Network Control applying IEEE 802.1ah MACinMAC Backbone
Massive Scalability with IEEE 802.1ah MACinMAC Backbone Frames
Lower OPEX and CAPEX plus Open Standards inter-operability benefits
Key Message to Customer
68
Carrier Ethernet Service Delivery Value Proposition
1. Scalable
Eliminate control plane restrictions Deployable on Optical and Broadband NEs
1. Operationally Sound, Easier to Troubleshoot

Better OAM tools: 802.1ag vs. VCCV/LSP-PING Fewer Moving Parts: No IGP, MPLS signaling etc. Consistent Operations Model with PMO Easier transition of workforce Consistent use of Metro OSS systems
1. Number # 1 with 20% Market Share in the Layer 2 CEAD Ethernet over Fiber Market, Light Reading July 14, 2010 www.lightreading.com/document.asp?doc_id=194390 2. SLA / Performance Measurement Built In Simplified Network Layering
Ethernet is the faceplate and network layer
1. Lower CAPEX
Ethernet based infrastructure that rides Ethernet cost curves
69
Thank you ! (Q & A)
70
G.8032 Terms and Concepts

Ring Protection Link (RPL) Link designated by mechanism that is blocked during Idle state to prevent loop on Bridged ring RPL Owner Node connected to RPL that blocks traffic on RPL during Idle state and unblocks during Protected state Link Monitoring Links of ring are monitored using standard ETH CC OAM messages (CFM) Signal Fail (SF) Signal Fail is declared when ETH trail signal fail condition is detected No Request (NR) No Request is declared when there are no outstanding conditions (e.g., SF, etc.) on the node Ring APS (R-APS) Messages Protocol messages defined in Y.1731 and G.8032 Automatic Protection Switching (APS) Channel - Ring-wide VLAN used exclusively for transmission of OAM messages including R-APS messages
71
G.8032 Timers
G.8032 specifies the use of different timers to avoid race conditions and unnecessary switching operations WTR (Wait to Restore) Timer Used by the RPL Owner
to verify that the ring has stabilized before blocking the RPL after SF Recovery
Hold-off Timers Used by underlying ETH layer to filter

out intermittent link faults Faults will only be reported to the ring protection mechanism if this timer expires
72
Controlling the Protection Mechanism

Protection switching triggered by Detection/clearing of Signal Failure (SF) by ETH CC OAM Remote requests over R-APS channel (Y.1731) Expiration of G.8032 timers R-APS requests control the communication and states of the ring nodes Two basic R-APS messages specified - R-APS(SF) and R-APS(NR) RPL Owner may modify the R-APS(NR) indicating the RPL is blocked: R-APS(NR,RB) Ring nodes may be in one of two states Idle normal operation, no link/node faults detected in ring Protecting Protection switching in effect after identifying a signal fault
73
Signaling Channel Information

ERP uses R-APS messages to manage and coordinate the protection switching R-APS defined in Y.1731 - OAM common fields are defined in Y.1731.
Version 00000 for this version of Recommendation OpCode defined to be 40 in Y.1731 Flags 00000000 should be ignored by ERP
1 2 3 4
1 5 .. 37 last
MEL
Version (0)
OpCode (R-APS = 40)
Flags (0)
TLV Offset (32)
R-APS Specific Information (32 octets)
[optional TLV starts here; otherwise End TLV]
Defined by Y.1731
Defined by G.8032
Non-specified content
End TLV (0)
74
R-APS Specific Information

Specific information (32octets) defined by G.8032 Request/Status(4bits) 1011 = SF | 0000 = NR | Other = Future Status RB (1bit) Set when RPL is blocked (used by RPL Owner in NR) Status DNF (1bit) Set when FDB Flush is not necessary (Future) NodeID (6octets) MAC address of message source node (Informational) Reserved1(4bits), Status Reserved(6bits), Reserved2(24octets) - Future development
1 8 7
2 6 5 4 3 2 1 8 7 6 5 4 3 2 1 8 7 6 5
3 4 3 2 1 8 7 6 5
4 4 3 2 1
Request /State
Reserved 1 RB DNF
Status Status Reserved
Node ID (6 octets)
(Node ID) Reserved 2 (24 octets)
75
Items Under Study

G.8032 is currently an initial recommendation that will continue to be enhanced. The following topics are under study for future versions of the recommendation:
a) b) c) d) e) f) g) h) RPL blocked at both ends configuration of the ring where both nodes Interconnected rings scenarios: shared node, shared links connected to the RPL control the protection mechanism Support for Manual Switch administrative decision to close down a link and force a recovery situation are necessary for network maintenance Support for Signal Degrade scenarios SD situations need special consideration for any protection mechanism Non-revertive mode Allows the network to remain in recovery configuration either until a new signal failure or administrative switching RPL Displacement Displacement of the role of the RPL to another ring link flexibly in the normal (idle) condition In-depth analysis of different optimizations (e.g., FDB flushing) Etc.
76

Syringa Session3-5 CarrierEthernet Ciena RGregory

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Syringa Session3-5 CarrierEthernet Ciena RGregory

Hochgeladen von

Copyright:

Verfügbare Formate

Carrier Ethernet Technology and Standards Update

Ciena Confidential and Proprietary

Carrier Ethernet: Evolution, Defined

Ciena Confidential and Proprietary

Ethernet Evolution Timeline

Ciena Confidential and Proprietary

Ethernet Evolution Events

Ethernet over any mediaany service over Ethernet

Ciena Confidential and Proprietary

Basic Ethernet Bridging

Forwarding Table Address

Four Important Concepts/Operations (upon switch receipt of a packet):

Ciena Confidential and Proprietary

Standards: Current, Forthcoming, and Direction

Ciena Confidential and Proprietary

Scaling Ethernetbeyond 802.1ad (Q-in-Q)

Ciena Confidential and Proprietary

Ethernet Transport at Layer 2 & 2.5: Approaches to COE

Whats Next in Carrier Ethernet ?

Traffic Engineered Ethernet Tunnels

Proactive Performance Management

Service and Infrastructure CFM Diagnostics Scalable, Secure Dataplane

Ethernet has steadily evolved to address more robust networking infrastructures

resiliency schemes (RSTP, MPLS, PBB-TE)

802.1Q/ad domains protected using 802.1w RSTP with 50 ms restoration

Granular Bandwidth Control

Specific service identification with rich L1-L2 classification

20/0 10/100 20/100

Voice VLAN MAC DA B L2VPN 80/200 50/100

DENY IP SA 192.168.1.23 10/40 20/55

MAC SA A TCP port 80 Flow Interface

Layer 2 SLA Monitoring & Metrics: Delay, Jitter, Frame Loss

ITU-T Y.1731 Ethernet OAM

Service Heartbeats, End-to-End & Hop-by-Hop fault detection

IEEE 802.1ag CFM Connectivity Fault Management

Enhanced troubleshooting, rapid network discovery

IEEE 802.3ah EFM Physical Link

Ciena Confidential and Proprietary

Technology Options for Packet Transport

PBB MPLS (L2) PBB-TE MPLS-TP

Goal: cost-effective, high-performance transport

Mechanisms to Build the Carrier Grade Enterprise Ethernet Network

Ethernet Ethernet OAM OAM

Ciena Confidential and Proprietary

Performance Monitoring and Connectivity Fault Management

Ciena Confidential and Proprietary

Maturing Ethernet OAM into a Transport Technology

A Partial List of Completed and Evolving Standards

MEF UNI and LMI

Ciena Confidential and Proprietary

PBB / PBB-TE management

Ciena Confidential and Proprietary

The New Ethernet OAM

802.1ag Maintenance levels/hierarchy

Continuity Check (Fault)

Loopback (MEP/MIP Fault Connectivity)

Traceroute (MEP/MIP Link Trace - Isolation)

Conceptually: -monitor the trunk or the service or both Service

Ciena Confidential and Proprietary

Built-in and on-switch

Ciena Confidential and Proprietary

Provider Backbone Bridging (PBB) IEEE 802.1ah

Ciena Confidential and Proprietary