1 / 12

PBB-TE Infrastructure Protection Switching Operation

Joint ITU-T/IEEE Workshop on The Future of Ethernet Transport (Geneva, 28 May 2010). PBB-TE Infrastructure Protection Switching Operation. Bob Sultan, Huawei Technologies. Topics. Review PBB-TE Forwarding The Infrastructure Segment and IPG Monitoring the Segment Provisioning an IPG

hollie
Download Presentation

PBB-TE Infrastructure Protection Switching Operation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Joint ITU-T/IEEE Workshop on The Future of Ethernet Transport(Geneva, 28 May 2010) PBB-TE Infrastructure Protection Switching Operation Bob Sultan, Huawei Technologies

  2. Topics • Review PBB-TE Forwarding • The Infrastructure Segment and IPG • Monitoring the Segment • Provisioning an IPG • Infrastructure Protection Switching

  3. PBB-TE Forwarding (ESP) FDB D Filtering Database (FDB) B <DA, VID> <DA, VID> Port Out Port Out <E, 7> P1 <E, 7> P2 P2 ESP X P2 A B D E P1 P1 C P2 P3 P1 FDB C P3 P3 <DA, VID> Port Out <E, 7> P3 • Ethernet Switched Path (ESP) forwarding is based on provisioned 2-tuple <Destination MAC, VLAN Identifier> and associated outbound local port;

  4. A pair of counterdirectional congruent PtP ESPs form a PtP Traffic Engineered Service Instance (TESI); IPS also applies to linear portions of PtMP TESIs; PBB-TE Forwarding (TESI) FDB D Filtering Database (FDB) B <DA, VID> <DA, VID> Port Out Port Out <E, 7> P1 <E, 7> P2 <A, 8> P2 <A, 8> P1 P2 ESP x P2 A B D E P1 P1 C P2 P3 P1 ESP y FDB C P3 TESI P3 <DA, VID> Port Out <E, 7> P3 <A, 8> P1 4 Geneva, 28 May 2010

  5. A segment is specified by a sequence of ports: Green: B.P2 – C.P1 – C.P3 – D.P2 Red: F.P2 – G.P1 – G.P2 – H.P2 Bridge terminating a segment contains exactly one port associated with that segment; Segment P2 ESP x P2 A B D E P1 P1 C P2 P3 P1 P3 P3 P1 P1 F P2 H P2 G P1 P2 5 Geneva, 28 May 2010

  6. The state of an Infrastructure Segment is monitored by a Maintenance Association (MA) specific to that Segment; Distinct type of MA; not the same as the PBB-TE MA associated with a TESI; Terminates at PBP vs. CBP; Down MEPs vs. Up MEPs; Segment Monitoring CCM CCM CCM CCM CCM CCM Green MEP Green MEP Green Segment MA A B D E C 6 Geneva, 28 May 2010

  7. Non-overlapping segments having the same pair of segment endpoint bridges (SEB) form an IPG; A Bridge maintains a table for each IPG terminating in that Bridge (just one shown in this figure); The table contains a list of 2-tuples representing traffic provisioned to follow one of the Infrastructure Segments which is known as the Working Segment; Infrastructure Protection Group (IPG) I J SEB SEB A B D E C Working Segment IPG IPG <I, 9> <J, 11> F H G <E, 7> <A, 6> 7 Geneva, 28 May 2010

  8. Protection Segment The Protection Segment provides an alternate path for traffic associated with the listed 2-tuples for the IPG; The IPG maintains the local port numbers associated with the Working and Protection Segments respectively; I J SEB SEB P2 P2 A B D E C Working Segment P3 P3 IPG IPG WS: P2 WS: P2 PS: P3 Protection Segment PS: P3 F H G <I, 9> <J, 11> <A, 6> <E, 7> 8 Geneva, 28 May 2010

  9. Protection Segment Provisioning Same list of 2-tuples at F, G, H; but provisioned as if traffic was forwarded on Protection Segment; FDB B <DA, VID> Port Out <E, 7> P2 <A, 8> P1 I J <J, 11> P2 <I, 9> P4 P4 P2 P2 A B D E C P1 P3 P3 IPG WS: P2 IPG P1 PS: P3 WS: P2 F H P2 G <I, 9> PS: P3 <A, 6> <J, 11> FDB F <E, 7> <DA, VID> Port Out <E, 7> P2 <A, 8> P1 <J, 11> P2 <I, 9> P1 9 Geneva, 28 May 2010

  10. Infrastructure Protection Switching Protection switch triggered by detection of state change in IPG Segment or manually; Requires FDB update only at endpoint bridges; Update only entries with 2-tuple in IPG list; FDB D FDB B <DA, VID> Port Out <DA, VID> Port Out P3 <E, 7> P1 <E, 7> P2 <A, 8> P2 P3 <A, 8> P1 I J <J, 11> P4 <J, 11> P2 P3 <I, 9> P2 <I, 9> P4 P3 P4 P4 P2 X P2 A B D E C P1 P1 P3 P3 IPG IPG WS: P2 WS: P2 P1 PS: P3 PS: P3 F H P2 G <I, 9> <J, 11> <A, 6> <E, 7> 10 Geneva, 28 May 2010

  11. Further Points The IPS State Machine is identical to the TESI Protection State Machine Except for the lowest-level functions that update the FDB outbound port values instead of changing the mapping from backbone service instance to BVID; The TESI Protection State Machine is similar, but not identical, to the G.8031 State Machine; IPS specifies optional M:1 protection, deployed by using an alternate Protection Segment when a Protection of higher priority is not available; IPS supports the nesting of IPGs but this requires appropriate provisioning of hold-off timer values; Further, the MA associated with the outer IPG must be provisioned to be protection switched by the inner IPG when a failure of the inner IPG occurs; 11 Geneva, 28 May 2010

  12. Thank You 12 Geneva, 28 May 2010

More Related