Download as PDF, PPTX
More Related Content
![Optical Transport SDN by Peter Landon [APRICOT 2015]](https://cdn.slidesharecdn.com/ss_thumbnails/opticaltransportsdnv41425346265-150302200248-conversion-gate01-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Dont forget-the-control-plane
Dont forget-the-control-plane
- 1. MPLS-TP Don’t Forget theControl Plane! Pat Moore Metaswitch Networks Network Technologies Division pat.moore@metaswitch.com Visit us at stand 205
- 2. Metaswitch Expertise Previously DataConnection Ltd. (DCL) • Network Protocol source code since 1983 Customers • 1st portable GMPLS protocol solution • 1st portable O-UNI protocol solution • 1st portable LMP protocol solution • 1st portable G.709 OTN protocol solution • 1st portable MPLS-TP protocol solution Copyright © Metaswitch Networks | www.metaswitch.com | 1
- 3. Agenda • MPLS-TP managementprovisioned vs. control plane • The benefits of an MPLS-TP control plane • Where does it fit? Copyright © Metaswitch Networks | www.metaswitch.com | 2
- 4. MPLS-TP Management Provisioned •Full centralized control of • Each LSP • Each hop of each LSP • Each backup LSP • Packet LSP and PW sublayers • Intelligence resides in the NOC • Simple and predictable • Works well in simple topologies Copyright © Metaswitch Networks | www.metaswitch.com | 3
- 5. MPLS-TP with aControl Plane • As management provisioned • Same OAM • Plus a control plane • Both modes can co-exist • One-touch provisions entire LSP • Intelligence resides in NEs • Auto-discovery of NEs and topology • Auto-tracking of available capacity • Route calculation • Signalling of LSP • Automated operation Reduced OPEX Copyright © Metaswitch Networks | www.metaswitch.com | 4
- 6. Agenda • MPLS-TP managementprovisioned vs. control plane • The benefits of an MPLS-TP control plane • Where does it fit? Copyright © Metaswitch Networks | www.metaswitch.com | 5
- 7. Automated Discovery • IGP(e.g. OSPF) used to auto-discover NEs and links • Opaque LSAs flood link attributes • Available bandwidth • Latency • Whatever is important in your network • Standard TE extensions to OSPF and IS-IS Copyright © Metaswitch Networks | www.metaswitch.com | 6
- 8. Link Bundling • Newlink detected by local NEs • No change in network topology • IGP floods increased capacity on bundled link • Improved IGP scalability • Signalling chooses component link to use for each LSP Copyright © Metaswitch Networks | www.metaswitch.com | 7
- 9. Automated LSP Setup •Ingress NE processes LSP setup request (egress, bandwidth, etc.) • OSPF-TE route calculation runs on ingress NE • GMPLS signalling sets up each NE on the MPLS-TP path • Standard GMPLS extensions to RSVP-TE • Targeted LDP signalling used for PW layer Copyright © Metaswitch Networks | www.metaswitch.com | 8
- 10. Automated Protection andRestoration • Various GMPLS protection and restoration schemes • Mesh Restoration and Segment Recovery defined • Linear and Ring Protection underway • Substantial automation • Automated diverse route calculations for 1:N protection • Automated placement of branch and merge points • Automated reversion when primary LSP recovers • Intelligent use of backup LSP for low priority traffic Copyright © Metaswitch Networks | www.metaswitch.com | 9
- 11. On-demand Provisioning • LSPSetup request does not have to come from NOC • E.g. router acting as client to MPLS-TP layer • Router requests extra network capacity at its attached NE • User-to-Network Interface (UNI) • Client-server model between network layers Copyright © Metaswitch Networks | www.metaswitch.com | 10
- 12. Control Plane Extensionsand Benefits • OAM signalling • Enables NEs to agree what OAM mechanisms are to be used • No spurious alarms as OAM start is synchronized with end-to-end LSP activation Reduced OPEX • Management <–> Control Plane hand-off • Management-established LSPs transitioned to control plane • …and vice-versa Facilitates network migration • Multi-segment pseudowire • Adapting existing MS-PW to the MPLS-TP profile Supports more diverse deployment scenarios • Standards baked Copyright © Metaswitch Networks | www.metaswitch.com | 11
- 13. Agenda • MPLS-TP managementprovisioned vs. control plane • The benefits of an MPLS-TP control plane • Where does it fit? Copyright © Metaswitch Networks | www.metaswitch.com | 12
- 14. Typical Deployment Scenario Service MS-PW Static Static LSP Signalled LSP Static LSP Static S-PE S-PE T-PE T-PE Access Access Backbone • Three MPLS-TP domains shown • Backbone uses control plane • Access uses management provisioning • MS-PW crosses domains to provide the end-to-end service Copyright © Metaswitch Networks | www.metaswitch.com | 13
- 15. Commonality Across NetworkLayers • Multiple layers can include • MPLS-TP transport service sublayer (e.g. PW for L2 Ethernet service) • MPLS-TP transport sublayer • TDM layer (OTN ODU) • WDM layer (OTN OCh) • Each Carrier uses only the layers it needs • Only use a layer if it adds value • Other layers possible • GMPLS is common Copyright © Metaswitch Networks | www.metaswitch.com | 14
- 16. Conclusion: Don’t Forgetthe Control Plane • MPLS-TP control plane is beneficial • It brings significant automation and reduced OPEX • Management provisioned and control plane NEs will co-exist in many networks • Many vendors building NEs with both management and control plane provisioning • Standards are in place • GMPLS has been around for years • Common GMPLS technology across layers • Coherent management Come see • Same look and feel Metaswitch MPLS-TP at the EANTC Live Demo Copyright © Metaswitch Networks | www.metaswitch.com | 15
- 17. Thank you pat.moore@metaswitch.com Visit us at stand 205