1 / 4

Short Pipe Model with Nested TTL and No PHP Processing -slide 45

Short Pipe Model with Nested TTL and No PHP Processing -slide 45. A. B. C. D. E. F. G. H. From the TTL perspective, the treatment for a Pipe Model LSP is identical to the Short Pipe Model without PHP (RFC3443). PW. LSP 3. LSP 2. LSP 1. TTL=n. TTL=n-1. Stack going into pipe. TTL=m.

casper
Télécharger la présentation

Short Pipe Model with Nested TTL and No PHP Processing -slide 45

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. Short Pipe Model with Nested TTL and No PHP Processing -slide 45 A B C D E F G H From the TTL perspective, the treatment for a Pipe Model LSP is identical to the Short Pipe Model without PHP (RFC3443). PW LSP3 LSP2 LSP1 TTL=n TTL=n-1 Stack going into pipe TTL=m TTL=m-1 TTL=m-1 TTL=m-2 Stack received at H TTL=k TTL=k-1 TTL=k-2 TTL=k-2 TTL=k-2 TTL=k-2 TTL=k-3 TTL=k-3 TTL=j TTL=j TTL=j TTL=j TTL=j TTL=j TTL=j TTL=j Bottom of stack

  2. Pipe Model with Cascaded TTL Processing =Slide 49 LSP PW A B C C’ D E PW Stack going into pipe Stack received at E TTL=k TTL=k-1 TTL=n TTL=n-1 TTL=n-1 TTL=j TTL=j TTL=j-1 TTL=m TTL=m TTL=m m <= j-1

  3. MEP MEP MEP MEP Multi segment Transport example PW over LSP-slide17 CE CE Attachment circuit Attachment circuit Carrier 1 Carrier 2 PE P P PE PE P PE UNI NNI UNI end to end PW OAM (no PW stitching shown) MEP MEP end to end LSP OAM MEP MIP MIP MEP segment LSP OAM (inter carrier) segment LSP OAM (carrier 1) segment LSP OAM (carrier 2) MEP MIP MIP MIP MEP • A segment is between MEPs • OAM is end to end or per segment • In SDH/OTN and Ethernet segment OAM is implemented using Tandem Connection Monitoring (TCM) • The OAM in each segment is independent of any other segment • Recovery actions (Protection or restoration) are always between MEPs i.e. per segment or end to end MEP: Maintenance End Point MIP: Maintenance Intermediate Point Note: A policing function (traffic management/shaping) is normally co located with a MEP at a business boundary (UNI/NNI)

  4. MEP MEP Nested LSP segment example - slide18 Carrier 1 Region 1 Region 2 PE PE CE P PE P PE PE UNI INNI NNI end to end PW OAM (no PW stitching shown) MEP end to end LSP OAM MEP MIP MIP segment LSP OAM (inter carrier) Carrier 1 LSP OAM segment MEP MEP MIP MIP carrier 1 region 1 LSP OAM segment carrier 1 region 2 LSP OAM segment MEP MEP MEP MIP MEP • 3 LSP OAM levels + PW OAM • end to end LSP + 2 nested segment LSP levels(Carrier 1 + regions 1/2) • Nested segments are supported by Tandem Connection Monitoring (TCM) in SDH/OTN and Y.1731

More Related