1 / 10

draft-koike-mpls-tp-temporal-hitless-psm-01

draft-koike-mpls-tp-temporal-hitless-psm-01. 28 th July. 2010 Maastricht Yoshinori Koike / NTT. Background. *Carrier Grade packet transport network requires MPLS-TP OAM function to be effective in maintenance operations.

saddam
Download Presentation

draft-koike-mpls-tp-temporal-hitless-psm-01

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. draft-koike-mpls-tp-temporal-hitless-psm-01 28th July. 2010 Maastricht Yoshinori Koike / NTT

  2. Background *Carrier Grade packet transport network requires MPLS-TP OAM function to be effective in maintenance operations *If some faults or un-expected events occur, quick actions and methods are mandatory in terms of transport network requirements.

  3. Network Objectives of transport network • The monitoring and maintenance of current transport paths has to be conducted in service without traffic disruption. • The monitored or managed transport path condition has to be exactly the same irrespective of any configurations necessary for maintenance.

  4. Why segment monitoring ? • Quick location of fault point & prompt handling of the problem • Segment monitoring function is mandatory in Delay Measurement and Loss Measurement • (DM and LM is supported only between MEP and MEP) • Diagnostic test and on-demand CV should be able to be conducted from an intermediate point of configured transport path.

  5. Use cases of temporal segment monitoring Use case 1) DM and LM Packet Delay/Loss NE1(LER1) NE2(LSR1) NE3(LSR2) NE4(LER2) CE2 CE1 Transport path Segment monitoring 1 No Fault Segment monitoring 2 Detect Fault Use case 2) Diagnostic test and on-demand CV Cost effective small box (Support a subset of functions) Originator of test packets NE2(LER1) NE3(LSR2) NE4(LER2) NE1 NE5 Segment monitoring 1 Segment monitoring 2

  6. Problem Statement regarding SPME In case of pre-configured segment monitoring (P-1) Increasing the bandwidth by the stacking shim header(s) (P-2) Increasing the identifier management of all MEPs and MIPs newly configured for SPME in the old MEG In case of temporal(on-demand) segment monitoring (P’-1) Changing the condition of the original transport path by changing the length of the MPLS frame (delay measurement and loss measurement can be sensitive) (P’-2) Disrupting client traffic over a transport path, if the SPME is temporally configured.

  7. Potential issue of SPME • There seems significant changes in the original transport path, if SPME is set for segment monitoring. • Performing monitoring function should not change the condition of target transport path A B C D E LBL= 110 LBL= 120 LBL= 130 Before Change of Inner label value Setting SPME LBL= 100 LBL= 999 LBL= 130 After LBL= 210 LBL= 220 Change of Inner label value Change of outer label value

  8. Conclusions • Request to include two network objectives in page 3 in the MPLS-TP OAM framework. In addition • Request solution for temporal & hitless path segment monitoring without problems like P-1, P-2, P’-1 and P’-2. (The solution may have to be considered independently from SPME issue) Note: This I-D is based on the liaison from ITU-T SG15, the solution is needed for the preparation of ITU-T MPLS-TP OAM Recommendation.

  9. Next Steps • Clarification of technical details of SPME and impacts on transport path in client layer • Solution for temporal and hitless path segment monitoring • Creating a new solution if problems are not solved by SPME • Clarification of applicable segments in both per-node model and per-interface model • Any possible patterns between MEP-MEP,MEP-MIP, MIP-MIP including internal NE monitoring • Segment of protected transport path used for protection

  10. Thank you Soliciting comments, feedback and suggestions for this draft from WG

More Related