Ethernet Ring Protectiont e et g otect o(G.8032)

Feb. 23. 2011Actus Networks, Inc.

www actusnetworks comwww.actusnetworks.com

Ethernet Ring Protection

• ERP Standard (G.8032 2010)– Protection switching on Eth layer – Reliable solution

High Scalability– Prevent any loops by blocking mechanism– Use OAM (R-APS) frames for protection– Disable STP

Standard MAC FDB

– High Scalability – Revertive mode/Non-revertive behavior– Administrator commands– Timer– Standard MAC FDB

• Mac learning, Forwarding, Flush, Port blocking/unblocking

– Failure detection : Physical Link Failure, CCM

Timer– WTR : Wait Restore Timer– Guard Timer – Holdoff Timer

– Sing ring protection– Multi-ring protection with VC and non-VC

channelMultiple ERP instances– Multiple ERP instances

– Compatible with G.8032 V1– Sub 50ms protection switching– Media Independent : NR/RB(2)NR/RB(2)

SubRPL blockNR/RB(1)NR/RB(1) Mainp

10/100/1000/10000Mbps– Automatic, Forced and Manual switching

NR/RB(2)NR/RB(2)Ring/ ( )

Tx NR/RBRing

2Actus Networks, Inc. Property

Software portability

d l h d• Modules– ERP Engine block

OS abstraction layer

• Switching devices– BCM56330

BCM56228– OS abstraction layer– Hardware abstraction layer– CLI block

– BCM56228– LSI APP340– LSI APP3330

– SNMP MIB

• Operating Systems– Others

• Actus supportg y– Linux 2.6

• TEST bed– Porting– Performance tuning

C i i ifi– BCM56330– MPC8314

– Customization on specific hardware platform

3Actus Networks, Inc.

Single ring – Failure

• MAC generic protectionp

– Store-and-forward – FDB Flush and

Flooding– Management of loop-

prevention block– 50-ms protection– Scalable– In-band signaling– All Ethernet services– Same MAC/PHY

hardware (803.3)– Compatible with PBB

d E h OAMand Eth OAM

• Not RPR (802.17)

4

Ref: J. Ryoo et al. IEEE Comm. Mag., Sept. 2008.http://www.ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=4623718&isnumber=4623694

Single ring – Recovery

5

Interconnected ring

• Ring and Subring model– Subring - ERP ring connected to other ring(s) or network through

interconnection nodes.– R-APS channels are not shared across ring interconnections

6Actus Networks, Inc.

Interconnected ring

• Operation Principle– Failure in the Ring : R-APS on its ring only. Flush and flooding are

li it d ithi th ilimited within the ring.– No action in the subring

7

Interconnected ring

• Operation PrincipleFailure in a Subring : First R APS acts on the subring Flush and– Failure in a Subring : First R-APS acts on the subring. Flush and flooding restore the FDB.

– Interconnection Node: Transmit R-APS(event) message in the ring

8

Features – G.8032 2010

• Performance– Protection switching time less than 50msg

• Under less than 1200km of ring fiber and fewer than 16 ERP Nodes

– In case of interconnected rings and multiple instances, protection switching time may exceed 50msswitching time may exceed 50ms

• Revertive/non-revertive behavior• Ability to block RPL at both ends of link• Multi-ring protection• Flush propagation

M lti l ERP i t• Multiple ERP instances• Interoperability with ERPv1• Support operator commands - MS/FS/ClearSupport operator commands MS/FS/Clear

• Support timers– WTR/Holdoff/WTB/Guard timers

9Actus Networks, Inc.

G.8032 Standard – Current State

• Latest revision approved in March 2010• Normative clauses in G.8032 are almost finished.o at e c auses G.803 a e a ost s ed.• Discussions

– E-to-E service resilience• Other technologies over G.8032• Non ERP node in ERP ring

Reduced consumption of VID– Reduced consumption of VID– Flush optimization– RPL owner Electiono e ect o– Etc

10Actus Networks, Inc.

Features – G.8032 2010 implementation

• Implementation based on standardSection Title Implemented Comments

Clause 1~7 Definitions, Ring protection characteristic YesClause 8 Ring protection conditions and commands Yes

Clause 9 Ring protection architectures Yes ERP Node modelArchitectures

Clause 10 Protection control protocol Yes All ERP logicsERP control process

Clause I~III Ring protection objectives YesAppendix IV Consideration for different times YesAppendix V Interconnected rings example YesAppendix VI Protection switching for multiple ERP instances Yes

Appendix VII Guidelines for the configuration of VIDs and Ring-IDs of R-APS channels Yes

Different VIDs for different ERP instances appliedapplied

Appendix VIII Flush optimization No Actus patent pending schemes applied

Appendix X Minimizing segmentation in interconnected rings No Planned

11Actus Networks, Inc.

Appendix XI End-to-end service resilience Yes

Features – ACTUS specific

• Flush optimization– Protection switching time is independent of # of MAC entriesProtection switching time is independent of of MAC entries– Minimum flush operation in interconnected ring

• Support a non ERP nodepp– Study item of G.8032. Ongoing discussions in SG15/Q9.

• Dual homing• ERP MIB• Port Trunking

12Actus Networks, Inc.

Actus Contributions for G.8032

• ACTUS consents more than 20 contributions in ITU-G SG15/Q9SG 5/Q9– Cooperation with ETRI, KAIST, and SKT

• Contributions– Failure recovery in non-revertive mode

f– Use of guard timer – Backward compatibility between ERP v1 and ERP v2– Protection switching performance analysis– Protection switching performance analysis– Flush optimization– RPL owner election– Support a non ERP node– Reporting problems: Ring segmentation problem, Black holing

di i l– Editorial

13Actus Networks, Inc.

Patents• Failure recover method in non revertive mode of Ethernet ring

network – pendingP i i hi h d i l i l E h i k• Protection switching method in multiple Ethernet ring network– Patented

• Filtering Database Flush Methods in Ethernet Ring ProtectionFiltering Database Flush Methods in Ethernet Ring Protection Network - patent Pending

• Method providing multi technology services in Ethernet ring t knetwork

– PCT patent pending

• Method of solving FDB inconsistency - pendingg y p g

• RPL owner election - pending• Flush optimization - pending

14Actus Networks, Inc.