MPLS Path Management. Ikuo Nakagawa, Intec NetCore, Inc. Feb., 2005

Transcription

1 MLS ath Management Ikuo Nakagawa, Intec NetCore, Inc. Feb., 2005

2 resentation Outline Background MLS is / will be de facto standard of carrier class backbone To build a reliable & stable multi-service network MLS may be the best solution, at this moment On the other hand, there are lots of issues to operate MLS network In this presentation, we introduce MLS deployment cases Cutting edge implementation cases MLS trend as multi-service platform requirements for MLS network issues in MLS network operation MLS network management model Concept of MLS path management Correlation mechanism based on path Hierarchical MLS path management 2

3 Agenda MLS deployment Internet I-VN L2-VN LS service rotection MLS today Multi-service platform Requirements for MLS network Issues in MLS network management MLS network management model Concept of MLS path management rovisioning Assurance Usage Correlation in MLS path management Hierarchical MLS path management Conclusion 3

4 MLS deployment: Internet Outline: Using MLS in the IS s backbone, for TE (traffic engineering). Nowadays, protection (FRR, etc) is also useful. rotocols: RSV-TE Example: To control traffic flow in IS s backbone, e.g., even if User-1 / User-2 are sending traffic to the same destination User-X traffic from User-1 are transmitted through TE-ath-1 and traffic from User-2 are transmitted through TE-ath-2, respectively to split high volume traffic into different paths User-X (AS #999) Carrier s MLS backbone TE-ath-2 User-2 (AS #2) Router Router E E User-1 (AS #1) TE-ath-1 Router 4

5 MLS cases: I-VN Outline: I-VN (aka MLS-VN) is well known application of MLS. roviding multiple virtual user network over the MLS network. rotocols: RFC2547bis, LD (E-E), RSV-TE (Core), and so on. Example: Carrier s MLS backbone provides 2 individual VN using M-BG between E-E to exchange user routes using RSV and/or LD in control plane VRF B VRF A Customer-B Customer-B RSV or LD Carrier s MLS backbone E Customer-A Customer-A E VRF B M-BG E Customer-B VRF A VRF B VRF A Customer-A 5

6 MLS deployment: L2-VN (EoMLS, VLS) Outline: roviding layer 2 (Ethernet) services over MLS. Customers can use L2-pipe via MLS network. rotocols: Martini or Kompella over LD/RSV-TE. Example: Carrier s MLS network provides 2 L-2 (Ethernet) pipes using RSV-TE and/or LD in and E routers using Targeted LD or M-BG to establish L2 circuites Customer-B L2-ipes Carrier s MLS backbone RSV-TE or LD-DU with IG VFT B E Customer-B E Customer-A VFT B VFT A Targeted LD or M-BG over LS E VFT A Customer-A 6

7 MLS deployment: LS service Outline: roviding LS between user routers. (aka MLS-IX) user routers establish LS and ebg peer between each other user can exchange full routes (carrier does NOT care about routes) rotocols: RFC2547bis, LD, RSV-TE (Core) Example: Carrier s MLS backbone provides LS between user ISs Using RSV or LD between and E Using LD between user routers MLS control plane Carrier s MLS backbone IS B IS A RSV or LD E E IS C ebg peer carrier s MLS control plane LS between user routers 7

8 MLS deployment: rotection Outline: Mainly used in backbone rotect a LS by pre-defined backup LS 3 types: path protection, node protection, link protection changing path to pre defined backup LS makes service downtime shorter. rotocols: RSV-TE (Core), FRR and so on. Example: User s services (I, I-VN, L2-VN and so on) are provided over protected LSs a LS (black) has pre defined backup LS (red) with node protection, in this example In case of router failure, path change occurs (to red path) User services over MLS network Carrier s MLS backbone User E E E E Fast Reroute (node protection) 8

9 MLS today MLS is de fact standard for multi-service platform MLS allows to provide Internet (normal I traffic with or without TE) I-VN / L2-VN / LS service ATM / FR Migration legacy services with MLS technology Single MLS backbone provide multi-services Migrate not only I or I-VN but also Ethernet, ATM, FR, etc Carriers class reliability with MLS rotection technology provides reliable data-path Sharing bandwidth in backbone MLS backbone is a packet network TE (Traffic Engineering) enable bandwidth control for services. L2 I VN ATM FR VOI L2 I VN ATM FR VOI L2-BB I-BB VN-BB ATM-BB FR-BB STN MLS / I Backbone (Shared) Optical Fiber (hysical) Optical Fiber (hysical) 9 Operation and Management of MLS Core backbone is Key in the next generation!

10 MLS today Requirements for MLS network MLS network has a lot of requirements Because, it has to provide multi-services, e.g., Internet bandwidth, bandwidth and bandwidth >>> fat pipe I-VN / L2-VN / LS service latency should be same as light speed >>> network topology down time should be < 1[sec] in case of trouble >>> protection ATM or FR latency and jitter are critical to emulate services >>> network topology and queue mechanism shorter down time is also required, < 50[ms] in case of trouble >>> protection 10

11 MLS today Issues for managing ath in MLS network design path resources for traffic engineering is also a key God hand? Just a key guy in a network can design path resources Both of bandwidth and protection simulation is required But, it is hard to implement God hand operators have very few method to see paths operators always walk through CLI to manage path with a lot of human resources! even MLS ping / MLS trace do not provide enough information it provides only aliveness of a LS In other words, less tools exists to manage MLS network need visualization and a kind of database operators do NOT have much information about: relationship between services and path (service) hard to check I-VN information on LS relationship primary path / backup path (protection) hard to check backup path status relationship path and physical links hard to visualize MLS path w/ several information Do operators need to walk through CLI? 11

12 MLS network management model Action matrix for MLS network management (outline) 3 actions: provisioning, assurance and usage 3 layers: service, path and element ath management is most important in MLS network Elements generate paths for data traffic Any service is bound to a path on MLS network Service Delivery: Design, Configuration rovisioning Service Assurance: Event Monitoring Fault Management, SLA Service Usage: Accounting, Billing Usage Report Service: Internet, I/L2-VN ATM, FR, etc Service design User config. Service Activation Service monitoring Fault Management Trouble Ticket : Accounting Service usage monitor Billing, report ath: LD/TD LS TE/rotection LS design/config. rotection design ath Activation LS/ath Management ath Visualization rotection Monitoring ath availability trouble report status report Element: hysical Topology Nodes, Links hysical design Equipment/Link design installation and config. Node management hysical event monitor node/link down ort/link availability network report 12

13 ath rovisioning Backbone provisioning implementation of a new network or changing the network and E routers inventory, topology, signaling, IG/BG, etc. design & simulation of the network topology simulation of paths and their backup paths to reroute bandwidth parameters for each links or paths even when, changing or upgrading interfaces / circuits configuration generating router commands & consistency check installation of router commands etc Service provisioning for Service Order (SO) adding a new customer or deleting a customer E and (for managed services) routers several steps for each services (I-VN, L2-VN, ATM, FR, etc) configuration of user services basic I connectivity, signaling, IG/BG, VRF, VC defining services parameters such as QoS/CoS, bandwidth, etc configuration generating router commands & consistency check installation of router commands etc 13

14 ath Assurance Backbone monitoring & trouble shooting path monitoring & trouble shooting on and E routers anything which consist paths, e.g., inventory, topology, signaling, IG/BG, etc. monitoring: path visualization view logical path topology path status monitoring active, inactive, backup path traffic monitoring alarm monitoring for MLS LS trouble shooting: path status check (with active or passive check, ex: LS ping/trace) path consistency check etc Service monitoring & trouble shooting monitoring & trouble shooting of services: I-VN, L2-VN, ATM, FR, etc E and (for managed services) routers monitoring: basic I connectivity or service availability (active or passive monitoring) traffic monitoring QoS/CoS monitoring trouble shooting: testing service status, by both of MLS OAM, Service OAM checking consistency of routing or VRF instances etc 14

15 An example of MLS path visualization Operators need to manage really many paths visualization makes understanding paths easy many information related to path should be visualized, as well status, bandwidth, traffic, protection, and so 15

16 ath Usage Accounting & reporting mechanism are very specific for carriers or providers because it depends on user databases and business models Accounting & reporting of backbone network (for backbone design, etc) traffic monitoring for LS ( and E) LS bound for services (I-VN or L2-VN or LS-service) bandwidth monitoring for traffic engineering QoS/CoS monitoring for priority services statistics for path status or path changes downtime, delay, jitter, and so on for SLA (service level agreement) for the backbone etc Accounting & reporting of MLS services (for service management) accounting in E depends on services: I-VN, L2-VN, ATM, FR, etc monitoring: traffic per customer QoS/CoS overload statistics for services availability, traffic, errors (loss) for SLA (service level agreement) per customer etc 16

17 Correlation in MLS path management In case of trouble Operators have to describe the reason of the trouble Several layers exist in a MLS network lots of services (Internet, I-VN / L2-VN, ATM / FR, and so on) path, of course (by MLS signaling) elements (routers, circuits, and so on) Operators have to monitor and/or understand relationship between layers e.g., LS bound for services, elements which consists LS, and so on Correlation mechanism provides relationship between layers Service Management Monitoring user service status, e.g., quality, reliability and event handling. ath Management Correlation Monitoring path (LS or route) events. Handling route changes and traps. Element Management Correlation Monitoring node (router, switch) and links. Historical network management mechanisms/ 17

18 Correlation in MLS path management What s happen when a route has a trouble? when a router has a hardware trouble, e.g., element failure occurs paths which has the router on them, also have troubles, e.g., path re-route services provided over those paths also have influence Correlation works as following (as shown in figures): service management layers can detect an event alarm events (paths and elements), and notify status of service network (ex. using primary path or backup up, or down, etc) Service Management User and service info. (type, status) in DB Detecting service down. Notify/Report service down time. ath Management ath info. (status, backup) in DB Correlation Detecting path change. Backup status, reroute time. Element Management router, link information (config., status) in DB Correlation Detecting router/link failure or any physical failure. 18

19 Hierarchical MLS path management Hierarchical LS exists in a MLS network for example: services labels (for I-VN, L2-VN, etc) created by BG4 (Service) LS between E routers created by LD (Service Edge) LS for protection purpose created by RSV-TE (Core) aths for FRR and/or protected paths (Backup) We need operation and management for each paths need suitable information for each paths correlation of hierarchical LS is also required Users rotected Area (FRR) VNv4 BG MLS network LD LD RSV FRR Backup LD 3 label stacks or 4 label stacks with FRR 19

20 Conclusion Recently, MLS is / will be de facto standard of carriers backbone provides multi-service platform, such as Internet I-VN / L2-VN ATM / FR with protection technology (for reliability or stability) but, operators have lots of issues In MLS network management 3 actions and 3 layers exist to manage in MLS network provisioning, assurance and usage service, path and element MLS path management is a key correlation mechanism hierarchical MLS path management 20