以太网环保护交换协的议(ERPS).pptVIP

G.8032Ethernet Ring Protection OverviewMarch, 2008ITU-T Q9 – SG 15;Agenda;ITU-T SG15/Q9 G.8032 Recommendation;G.8032 Objectives and Principles;G.8032 Terms and Concepts;G.8032 Timers;Controlling the Protection Mechanism;Physical topology has all nodes connected in a ring ERP guarantees lack of loop by blocking the RPL (link between 6 1 in figure) Logical topology has all nodes connected without a loop. Each link is monitored by its two adjacent nodes using ETH CC OAM messages Signal Failure as defined in Y.1731, is trigger to ring protection Loss of Continuity Server layer failure (e.g. Phy Link Down);Protection Switching ? Link Failure;Protection Switching ? Failure Recovery;Signaling Channel Information;R-APS Specific Information;Items Under Study;;Backup;G.8032 Basic Functions;ERP Functionality Decomposition;State Machine;State Machine;Switching Triggers;Ethernet Rings and the RPL;RPL Owner receives SF message and unblocks its end of RPL link [row 3] Stable State – SF messages on the ring Further SF messages trigger no further action [row10];When node C and D expire the guard timer, they may accept the new R-APS messages that they receive. [in guard timer] At expiration of WTR timer, RPL owner blocks its end of the RPL, sends, NR RB message [row 11] Each node that receives the NR,RB message it flushes its FDB. When Nodes C and D receive NR RB message , they remove block on their blocked ports. [row 13] Stable normal condition all nodes in Idle state