Packet Evolution in Transport Networks: MPLS Transport Profile (MPLS-TP) (IOS Advantage Webinar)

7,719 views

Published on

Detailed information on the evolution of SONET/SDH transport networks to more efficient packet transport networks based on MPLS Transport Profile (MPLS-TP).

Packet-based services are experiencing fast growth and now start to dominate the carrier traffic mix (driven by video, cloud and migration to IP). Packet services have also evolved to more dynamic traffic patterns (driven by mobile and cloud services). Traditional transport networks have relied on circuit technology and are rapidly becoming inefficient to carry packet traffic.

We’ll take a look at how new extensions to MPLS define a transport profile (MPLS-TP) that introduces packet technology while maintaining their traditional operational model. MPLS-TP enables the migration of SONET/SDH networks to packet technology in order to achieve better bandwidth efficiency and flexibility.

Published in: Technology, Education

Packet Evolution in Transport Networks: MPLS Transport Profile (MPLS-TP) (IOS Advantage Webinar)

  1. 1. Packet Evolution inTransport Networks –MPLS Transport Profile (MPLS-TP)José Liste – jliste@cisco.comHari Rakotoranto – hrakotor@cisco.comSantiago Álvarez – saalvare@cisco.comApril 2012© 2010 Cisco and/or its affiliates. All rights reserved. 1
  2. 2. •  Industry Dynamics and Motivations for Packet Transport•  Technology Overview•  Cisco MPLS-TP•  Use Cases•  Network Managementsaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 2
  3. 3. Before we dive in, how familiar am I with MPLS-TP?A.  Not familiarB.  Learning the technology and assessing applicability to my environmentC.  Fairly familiar with it and considering potential deployment in the futureD.  Fairly familiar with it, but not planning to deploy for nowsaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 3
  4. 4. Video/Voice •  15 billion networked Comm / Gaming devices in 2015, up from 7 Web / Other billion in 2010 Data Data •  IP traffic will grow 4-fold from 2010 to 2015 (32% File CAGR ) Sharing •  Mobile data traffic will grow 26-fold from 2010 to 2015 (92% CAGR ) Video •  IP traffic will reach an annual run rate of 965.5 Exabytes in 2015 (equivalent to 241 billion DVDs ) •  Mobile was 1% of total IP traffic in 2010, and will be 8% of total IP traffic in Source: Cisco Visual Networkin Index (VNI) www.cisco.com/go/vni 2015saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 4
  5. 5. •  Many transport networks still based on SONET/SDH (circuit switching technology)•  Packet-based growing fast and dominating traffic mix (driven by Video, Mobile, Cloud, application migration to IP)•  Increased changes in traffic patterns (mobility, cloud)•  Transport networks migrating to packet switching for Bandwidth efficiency (statistical multiplexing) Bandwidth flexibility (bandwidth granularity, signaling) Packet Network (IP/MPLS) Transport Network (SONET/SDH) Packet Network (MPLS-TP)saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 5
  6. 6.   Joint agreement between ITU- T and IETF to develop a transport profile based on MPLS Requirements  Packet transport requirements brought to IETF  MPLS forwarding, OAM, control plane, management and survivability extended at MPLS transport IETF extensions MPLS-TPsaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 6
  7. 7. •  Connection-oriented packet-switching technology•  Point-to-point (P2P) and point-to-multipoint (P2MP) transport paths•  Separation of control and management planes from data plane•  Deployable with or without a control plane•  Should retain similar operational model of traditional transport technologies•  Multi-service (IP, MPLS, Ethernet, ATM, FR, etc)•  Should support bandwidth reservation•  Support for 1:1, 1:n, 1+1 protection with similar techniques to traditional transport technologies•  Support for In-band OAMsaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 7
  8. 8. Existing functionality meeting •  Extends MPLS to meet packet transport Existing functionality transport requirements requirementsprior to MPLS Transport profile •  Identifies subset of MPLS supporting traditional transport requirements •  Data plane MPLS Bidrectional P2P and unidirectional P2MP LSP (no LSP Merging) In-band associated channel (G-Ach / GAL) Transport Profile •  Control plane New MPLS Forwarding Static MP2P / MP2MP LSP extensions P2P / P2MP LSP IP forwarding based on Dynamic (GMPLS) Pseudowire Architecture ECMP transport OAM requirements •  OAM Resilicency In-band GMPLS Continuity check, remote defect indication Connectivity verification and route tracing Fault OAM (AIS/LDI, LKR) Performance management •  Resiliency 50ms switchover Linear protection (1:1, 1+1, 1:N) Ring protection saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 8
  9. 9. MPLS-TP currently focuses on Layer-2/1services Services (clients) IPv4 Multicast IPv4 IPv6 IPv4 IPv6 VPMS VPWS VPLS VPN VPN Transport IP/MPLS (LDP/RSVP-TE/BGP) MPLS-TP (Static/RSVP-TE) MPLS Forwardingsaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 9
  10. 10. Applicability to Next Generation Network AAA DHCP,DN EMS NMS Service and Performance Mgmt Portal S OAM Subsystem Business Access! Aggregation! Edge! Multiservice Core! Corporat e Aggregatio Distribution n Node Node Residentia VoD TV SIP l Ethernet STB BNG Content Network 2G/3G MPLS-TP MPLS-TP IP/MPLS Business Node Aggregation Corporat e Network Core Core Network Residentia Business l DSL PE STB PON Business Corporat e Residentia Dark Fibre / CWDM / DWDM and ROADM l STB Option 1: MPLS TP for Aggregation Option 2: MPLS TP for Aggregation and Accesssaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 10
  11. 11. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 11
  12. 12. Forwarding OAM Protection Control Plane Services Plane   CC/RDI   Linear   Static   Ethernet/VLAN  Bi-directional, co-routed   On-demand protection (1:1,   Dynamic   ATM LSPs CV 1+1, 1:N) (GMPLS)   TDM  Static LSP   Route Tracing   Reversion   MS-PW  QoS   AIS/LDI/LKR   Wait-to-restore integration with   CFI (PW timer IP/MPLS Status)saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 12
  13. 13. •  Point to Point•  Static or signaled•  Bidirectional•  Generally, co-routed (same forward and reverse paths)•  In-band Generic Associated Channel (G-ACh)•  Ultimate hop popping (no explicit/implicit null)•  No equal cost multi-path (ECMP)•  Contained within a tunnel MPLS-TP LSP MPLS-TP G-ACh Tunnelsaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 13
  14. 14. •  Tunnel holds a working LSP and a protected LSP Working Protect (optional) •  LSPs may be configured with a bandwidth allocation •  Tunnel operationally UP if at least one LSP operationally UP (and not locked out) •  LSP operationally UP if OAM (Continuity Check) session operationally UP Working Protect MPLS-TP LSP LSP Tunnel •  LSP requires static configuration of LSP label imposition (output label and output G-ACh G-ACh link) •  LSP requires static configuration of LSP label disposition (input label)saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 14
  15. 15. •  Static configuration of forward and reverse LSP •  LSP defined using LSP ID Source Node Source tunnel number Destination Node Destination tunnel number LSP number MPLS-TP •  Semantics of source/destination locally LSP significant MPLS-TP G-ACh Tunnel •  Static configuration of label swapping (input label, output label and output LSP Input Output Output interface) Direction Label Label Interface Forward 323111 334111 Gi2/1 •  Static bandwidth reservation (optional) Reverse 343111 111 Gi2/4saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 15
  16. 16. •  In-band OAM packets (fate sharing)•  OAM functions can operate on an MPLS-TP network without a control plane•  Extensible framework (fault and performance management specifications ratified already)•  Independent of underlying technology•  Independent of PW emulated servicesaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 16
  17. 17. Label PW Label PW Associated G-ACh PW ACH 0 0 0 1 Version Reserved Channel Type Channel Header LSP OAM (ACH) Payload RFC 5085 G-ACh Label GAL 13 TC 1 1 Generic Associated Channel Label (GAL) ACH 0 0 0 1 Version Reserved Channel Type Associated Channel Header OAM Payload RFC 5586 •  OAM capabilities extended using a generic associated channel (G-ACh) based on RFC 5085 (VCCV) •  A G-ACh Label (GAL) acts as exception mechanism to identify maintenance packets •  GAL not required for pseudowires (first nibble as exception mechanism) •  G-ACh used to implement FCAPS (OAM, automatic protection switching (APS), signaling communication channel, management communication channel, etc)saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 17
  18. 18. PE1 P1 P2 PE2 •  Checks paths continuity between end points (no end point identity verification) •  Uses Bidirectional Forwarding Detection Bi-directional, co- (BFD) over G-ACh without IP/UDP headers BFD CC routed MPLS-TP LSP BFD CC (Interval x (Interval x •  BFD operates in asynchronous mode Multiplier) Label Multiplier) GAL •  LSP is UP when BFD session is UP ACH BFD •  Session initiation does not require bootstrapping (LSP Ping) BFD (Down) •  BFD diagnostics field provides remote BFD (Init) defect indication (RDI) function BFD (Up/Poll) •  BFD initiated using slow start (1s interval, BFD (Up/Final) BFD (Up) multiplier of 3) with poll/final sequence BFD (Up) BFD (Up) BFD (Up)saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 18
  19. 19. Oper Oper Up Up PE1 P1 P2 PE2 •  Failure indication sent by local end point to X remote end point •  Sent on direction opposite to failure Bi-directional, co- routed MPLS-TP LSP •  Uses existing BFD diagnostics field 0 - No Diagnostic Label GAL 1 - Control Detection Time Expired ACH 3 - Neighbor Signaled Session Down BFD 4 - Forwarding Plane Reset BFD (Up / 0) X BFD (Up / 0) 5 - Path Down BFD (Up / 0) X BFD (Up / 0) 7 - Administratively Down BFD (Up / 0) X BFD (Down / 1) BFD (Down / 3) X •  Diagnostics field indicates reason for last BFD (Down / 1) change in session state on an end point BFD (Init / 3) X BFD (Down / 1)saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 19
  20. 20. Admin Oper Down Down •  Fault notifications to enable alarm suppression PE1 P1 P2 PE2 and to trigger tunnel protection on end points X X •  Three notifications Link Down Indication (LDI) Bi-directional, co- routed MPLS-TP LSP Alarm Indication Signal (AIS) Lock Report (LKR) Label Label GAL GAL •  AIS signals a failure in the server layer ACH ACH Fault Fault •  LDI flag in AIS message indicates a fatal/ (LKR) (LDI) permanent failure in server layer LKR LDI •  LKR signals an administrative lock on server 1 per sec LKR LDI layer LKR LDI •  Fault messages generated by mid points 1 per fault refresh timer LKR LDI •  Fault messages processed by end points (default 20s) LKR LDI •  Three messages sent at 1 per sec to set/clear fault then continuous messages sent at a longer intervalsaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 20
  21. 21. Oper Oper Oper Oper Bidirectional Down Down X Down Down Fault X LDI LDI Oper Oper Oper Oper Unidirectional Down X Down Up Down Fault LDI RDI Oper Oper Oper OperUnidirectional Down Up X Up Down Black hole RDI Oper Admin Oper OperUnidirectional Down X Down Down Down X Shutdown LKR LDI MPLS-TP LSP Data linksaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 21
  22. 22. •  Uses LSP Ping over G-ACh for both CV and route tracing PE1 P1 P2 PE2 •  LSP Ping packets use IP/UDP encapsulation used in IP/MPLS •  IP forwarding NOT required Bi-directional, co- routed MPLS-TP LSP •  Only reply mode via control channel (G- ACh - 4) possible Label GAL ACH •  Only end points can send requests LSP Ping •  End points and mid points can send replies LSP Ping Echo Request •  End points use MPLS TTL expiration to TTL=255 LSP Ping send a request to a mid point (route Echo Reply tracing) TTL=255 LSP Ping •  New FECs defined for static LSP and Echo Request static pseudowire TTL=255 LSP Ping Echo Reply •  CV can be performed on an LSP TTL=255 regardless of its state (up/down)saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 22
  23. 23. •  Enables performance metrics for packet loss, delay and delay variation•  Defines two protocols Loss Measurement (LM) Delay Measurement (DM)•  Measuring capabilities One-way / two-way delay Loss - Direct (actual data) Loss - Inferred (test data) Delay variation Throughput•  Supports NTP and IEEE 1588 timestampssaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 23
  24. 24. Common IETF – Homogenous OAM frameworks at all layers OAMMobile Backhaul (2G/3G) BSC/RNC framework ATM/TDM TDM / ATM OAM MPLS Service OAM ATM/TDM PW (VCCV/LSP Ping/BFD) MPLS-TP IP/MPLS IETF MPLS-TP OAM PE P P PE P P PE IETF IP/MPLS OAM LSP LSP (LSP Ping, BFD, LDI/AIS/LKR, etc.) (LSP Ping/BFD) ITU-T – Heterogeneous OAM frameworks at transport layerMobile Backhaul (2G/3G) BSC/RNC ATM/TDM TDM / ATM OAM Operational complexity / MPLS Service OAM ATM/TDM PW inefficiency (VCCV/LSP Ping/BFD) MPLS-TP IP/MPLS ITU-T MPLS-TP OAM Proposal PE P P PE P P PE IETF IP/MPLS OAM (G.8113.1/Gtpoam – Y.1731 based) LSP LSP (LSP Ping/BFD) saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 24
  25. 25. Before Failure •  Relies on a disjoint working and a Working LSP Working LSP disjoint protect path between two (Up, Active) PE1 P1 (Up, Active) PE2 nodes •  Enables 1:1, 1:N, 1+1 protection Protect LSP P2 Protect LSP (Up, Standby) (Up, Standby) •  Protection switching can be triggered by Detected defect condition (LDI/AIS, During Failure LKR) Working LSP Working LSP Administrative action (lockout) (Down, Standby)(Down, Standby) PE1 P1 PE2 Far end request (lockout) Server layer defect indication (LOS) Protect LSP P2 Protect LSP Revertive timer (wait-to-restore) (Up, Active) (Up, Active) •  New protocol defined for protection state coordination (PSC) saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 25
  26. 26. •  Revertive mode always selects working LSP as active path if Working LSP Working LSP operationally up(Up, Standby) (Up, Standby) PE1 P1 PE2 •  Wait-to-restore (WTR) timer delaysWRT timer WRT timer selection of working LSP as active Protect LSP P2 Protect LSP path after protection trigger (Up, Active) (Up, Active) disappears (fault, lockout) •  Timer prevent excessive swapping between working and protect LSP due to intermittent defect •  Large WTR timer can provide non- revertive behavior (maximum WTR timer ~68 years) •  Restoration (selecting Working LSP as Active) should not result in packet losssaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 26
  27. 27. PE1 P1 P2 PE2•  MPLS-TP does not introduce any changes to MPLS QoS•  Coarse QoS•  Ingress node enforces contract Traffic Conditioning Per-Hop Behavior (conditioning) and performs   Classification   Classification aggregate marking on   Marking   Queuing incoming traffic   Policing   Queue Mgmt•  Packet header encodes packet   Shaping class (code point) Shim Header•  Class indicates service E-LSP required at each hop (per-hop Traffic Class (TC) / Experimental (EXP) – 3 bits behavior) L-LSP Label – 20 bits TC/ EXP – 3 bitssaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 27
  28. 28. •  Existing pseudowire MPLS-TP currently PW1 architecture applies to MPLS- focuses on Layer-2/1services PW2 LSP TP PW3 •  LSPs typically aggregate multiple servicesServices (clients) IPv4 IPv6 •  As usual, pseudowires can beIPv4 IPv6 VPMS VPWS VPLS VPN VPN signaled or established via manual configurationTransportIP/MPLS (LDP / RSVP-TE / MPLS-TP (Static / RSVP- BGP) TE) MPLS Forwardingsaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 28
  29. 29. Ethernet TDM ATMVirtual Private LAN Virtual Private Wire Service (VPWS) Service (VPLS) Ethernet Private Ethernet Virtual Circuit Emulation over AAL5 over Pseudowire LAN (EPLAN) Private Line (EVPL) PSN (CESoPSN) Unmuxed Muxed UNI Muxed UNI Muxed UNI UNI Structure Agnostic TDM Cell Relay with Packing Ethernet Virtual over Packet (SAToP) over Pseudowire Private LAN (EVPLAN) Ethernet Private Line (EPL) Muxed UNI Muxed UNI Muxed UNI Unmuxed UNIsaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 29
  30. 30. If I were to deploy MPLS-TP, I’d likely implement the followingservices(multiple choice)A.  Point-to-Point Ethernet (E-LINE)B.  Multipoint Ethernet (E-LAN)C.  ATMD.  TDME.  Othersaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 30
  31. 31. Access Aggregation Core Aggregation Access T-PE S-PE S-PE T-PE MPLS-TP IP/MPLS MPLS-TP Static PW Signaled PW Static PW Static Tunnel Signaled Tunnel Static Tunnel•  Multi-segment pseudowires (MS-PW) enable layer-2/-1 services over a combined MPLS- TP and IP/MPLS infrastructure•  S-PE switches traffic between a static and a dynamic segment•  MPLS-TP domain uses static LSP as PSN tunnel and static PW segment•  IP/MPLS domain uses signaled LSP (LDP or RSVP-TE) as PSN tunnel and signaled PW segmentsaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 31
  32. 32. •  Static MPLS-TP provides a simpler migration path for legacy transport networks•  Generalized MPLS (GMPLS) offers a proven control plane for MPLS-TP networks Packet•  A control plane increases Packet transport network intelligence transport (dynamic Dynamic services (static / no control plane) Legacy control Greater efficiency, resiliency and transport scalability plane) (circuit switched)•  GMPLS provides a generalized control plane for hierarchical traffic engineeringsaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 32
  33. 33. Would I be interested in a dynamic control plane fora packet transport network?A.  YesB.  No, Id rather operate a completely static transport networksaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 33
  34. 34. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 34
  35. 35. Network Management System Cisco Prime Access Aggregation Distribution/Edge Under consideration ASR903 ASR9000 CPT 600 / 200 / 50 7600saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 35
  36. 36. Area Functionality Forwarding Static Bi-directional LSP BFD CC On demand CV/Trace (LSP Ping Trace) OAM Fault OAM (AIS/LDI, LKR) Pseudowire status notification VCCV (Ping/Trace) Linear (1:1) Protection Lockout Pseudowire redundancy Admission Control Bandwidth Management / QoS MPLS DiffServ (E-LSP) Ethernet point-to-point Ethernet multipoint Services ATM TDM IP Integration with IP/MPLS static/dynamic PW switching (MS-PW)saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 36
  37. 37. PE1mpls tp router-id 172.16.255.1 MPLS-TP!bfd-template single-hop DEFAULT interval min-tx 10 min-rx 10 multiplier 3 PE2!interface Tunnel-tp10 In label (w): 321100 Tunnel description PE1<->PE3 Out label (w): 2100 definition no ip address no keepalive tp bandwidth 100000 tp destination 172.16.255.3 bfd DEFAULT PE1 PE3 working-lsp out-label 2100 out-link 201 Working LSP in-label 321100 lsp-number 0 In label (p): 341101 protect-lsp Out label (p): 314101 out-label 314101 out-link 204 Protect LSP in-label 341101 lsp-number 1 Static TP LSP!! (tunnel-tp10)interface GigabitEthernet2/1 ip address 172.16.0.1 255.255.255.252 mpls tp link 201 ipv4 172.16.0.2 ip rsvp bandwidth percent 100! TP LSP (Working) TP LSP (Protect)saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 37
  38. 38. PE3 interface tunnel-tp10 MPLS-TP description PE3<->PE1 Tunnel bandwidth 100000 definition destination 172.16.255.4 PE2 bfd min-interval 15 In label (w): 2200 multiplier 2 Out label (w): 321100 ! working-lsp Working LSP in-label 2200 out-label 321100 out-link 701 ! PE1 PE3 protect-lsp Protect LSP in-label 2201 out-label 323201 out-link 700 ! In label (p): 2201 ! Out label (p): 323201 rsvp interface GigabitEthernet0/0/0/0 bandwidth 10000000 Static TP LSP ! ! (tunnel-tp10) mpls traffic-eng interface GigabitEthernet0/0/0/0 tp link 700 next-hop ipv4 172.16.0.1 ! tp node-id 172.16.255.2 TP LSP (Working) ! ! TP LSP (Protect)saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 38
  39. 39. interface GigabitEthernet2/1 ip address 172.16.0.9 255.255.255.252 mpls tp link 201 ipv4 172.16.0.10 ip rsvp bandwidth percent 100!interface GigabitEthernet2/2 ip address 172.16.0.18 255.255.255.252 mpls tp link 202 ipv4 172.16.0.17 ip rsvp bandwidth percent 100!mpls tp lsp source 172.16.255.1 tunnel-tp 11 lsp protect destination 172.16.255.4 tunnel-tp 11 forward-lsp Forward LSP bandwidth 100000 in-label 323111 out-label 334111 out-link 201 reverse-lsp Reverse LSP bandwidth 100000 in-label 343111 out-label 111 out-link 202!saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 39
  40. 40. PE2rsvp interface GigabitEthernet0/0/0/0 MPLS-TP bandwidth 10000000 ! interface GigabitEthernet0/0/0/1 PE2 bandwidth 10000000 ! In label (w): 321100 In label (w): 2200! Out label (w): 2100 Out label (w): 321100mpls traffic-eng interface GigabitEthernet0/0/0/0 tp link 700 next-hop ipv4 172.16.0.1 ! interface GigabitEthernet0/0/0/1 PE1 PE3 tp link 701 next-hop ipv4 172.16.0.6 ! mid PE1-PE3 lsp-number 0 source 172.16.255.1 tunnel-id 10 destination 172.16.255.3 tunnel-id 10 forward-lsp bandwidth 1000000 Forward LSP Static TP LSP in-label 321100 out-label 321100 out-link 700 ! (tunnel-tp10) reverse-lsp bandwidth 1000000 Reverse LSP in-label 2200 out-label 321100 out-link 701 ! ! ! TP LSP (Working)! TP LSP (Protect)saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 40
  41. 41. PE1 Ethernet MPLS-TP Ethernet!pseudowire-static-oam class DEFAULT!pseudowire-class PW-Tunnel-tp10 encapsulation mpls Pseudowire/ PE2 protocol none Tunnel preferred-path interface Tunnel-tp10 association status protocol notification static DEFAULT! CE1 CE2interface GigabitEthernet2/6 description CONNECTS TO CE1 no ip address PE1 PE3 service instance 10 ethernet encapsulation dot1q 10 rewrite ingress tag pop 1 symmetric xconnect 172.16.255.3 10 encapsulation mpls E-LINE VLAN 10 VLAN 20 E-LINEmanual pw-class PW-Tunnel-tp10 mpls label 9110 9310 Static no mpls control-word PE PE pseudowire Static pseudowire ! Local label: PW Id 10 Local label:! 9110 9310 Static TP LSP (tunnel-tp10) TP LSP (Working) TP LSP (Protect)saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 41
  42. 42. ! Ethernet MPLS-TP Ethernetinterface GigabitEthernet0/0/0/18 description CONNECTS CE2!interface GigabitEthernet0/0/0/18.20 l2transport encapsulation dot1q 20 PE2 rewrite ingress tag pop 1 symmetric!l2vpn pw-class SS-PW-Tunnel-tp10 Pseudowire/ encapsulation mpls Tunnel CE1 CE2 transport-mode vlan association preferred-path interface tunnel-tp 10 ! PE1 PE3 ! xconnect group PE3 Static p2p PE1-PE3 pseudowire interface GigabitEthernet0/0/0/18.20 E-LINE VLAN 10 VLAN 20 E-LINE neighbor 172.16.255.1 pw-id 10 mpls static label local 9310 remote 9110 pw-class SS-PW-Tunnel-tp10 PE PE Static pseudowire ! Local label: PW Id 10 Local label: ! 9110 9310 ! Static TP LSP! (tunnel-tp10) TP LSP (Working) TP LSP (Protect)saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 42
  43. 43. •  Independent test report to be posted soon •  ASR 9000, CPT 600 and 7600 •  Comprehensive OAM (CC/RDI, AIS/LDI, LKR, LSP Ping/Trace) •  1:1 revertive linear protection with lockout •  E-LINE over combined MPLS-TP and IP/MPLS transport with end-to-end status notification using MS-PW •  Cisco Prime Network monitoringsaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 43
  44. 44. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 44
  45. 45. MPLS Extension to Access/Aggregation Access Aggregation Core Aggregation Access T-PE S-PE S-PE S-PE MPLS-TP MPLS-TP IP/MPLS SONET/SDH Metro Replacement Mobile Backhaul Metro RAN Packet Core PE PE SGW PE PE MPLS-TP MPLS-TP MME RNC NodeB / eNodeBsaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 45
  46. 46. T1/E1 - STMx L2/L3 VPN •  TDM/ATM based access Business SONET/SDH IP/MPLS •  No statistical multiplexing Corporate •  Static Provisioning Residential ADM •  50-ms Resiliency IP/ ADM SONET/SDH MPLS •  Ring or Point to Point STB ADM Core topology Mobile 2G/3G / LTE •  NMS Management •  SONET/SDH phy stats •  Ethernet Packet based VPWS L2/L3 VPN Transport Business MPLS-TP IP/MPLS •  Static Provisioning Corporate •  50-ms Resiliency Residential •  Ring, Mesh, P2P topology IP/ •  NMS Management MPLS-TP MPLS STB Core •  SONET/SDH phy stats on Mobile 2G/3G / LTE IPoDWDM© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 46
  47. 47. If I were to deploy MPLS-TP, I’d be migrating from(Multiple choice)A.  SONET/SDHB.  ATMC.  Native EthernetD.  Othersaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 47
  48. 48. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 48
  49. 49. Prime for IP Next Generation Network Architectures Cisco Prime IP NGN Suite Infrastructure Management MPLS and Carrier Ethernet Prime Central Prime Address Management (Core, Distribution, Access) Prime Fulfillment (Address Management and Configuration) Ran Backhaul Prime Network Prime Network Registrar (IPv6 and scalable Next Generation IPv6 Prime Optical DNS and DHCP Servers) Residential Services Prime Performance Manager Prime Access Registrar Optical Transport (Authentication, Authorization, Accounting)saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 49
  50. 50. ASR9000 7600ASR903 MPLS-TP Creation CPT50, CPT200, Wizard CTP600 Logical and Proactive Physical Monitoring Service Inventory View Fault Isolation  Complete device management (Physical and Logical) including single-click upgrades  Support point-and-click provisioning for Packet Transport including TP Tunnel Path Computation  Alarm De-duplication, Alarm Reduction and Correlation  Advanced troubleshooting tools (overlay, service view) enable MTTR reduction  E-OAM Monitoring and Configuration for services running over MPLS-TP  Extensive collection of statistic including Y.1731 for Ethernet Performance Management  Support released every other month with updated hardware support and releases saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 50
  51. 51. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 51
  52. 52. •  Traffic growth, device proliferation and cloud driving demand for packet services•  MPLS emerging as technology of choice to implement packet transport•  MPLS-TP extends MPLS to support operational model of traditional transport networks•  New IETF extensions part of MPLS architecture•  Cisco offers a complete solution for IP NGN aggregation with MPLS-TP as a transport alternativesaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 52
  53. 53. •  Implementing MPLS Transport Profile (IOS XR) http://cisco.com/en/US/docs/routers/asr9000/software/asr9k_r4.2/mpls/configuration/guide/ b_mpls_cg42asr9k_chapter_0110.html•  MPLS Transport Profile Configuration Guide (IOS) http://cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_transport_profile.html•  Cisco Prime for IP Next Generation Networks http://cisco.com/go/prime•  Cisco SP360: Service Provider Blog http://blogs.cisco.com/tag/mpls-tp/•  Cisco ASR9000 http://cisco.com/go/asr9000•  Cisco ASR903 http://cisco.com/en/US/products/ps11610/index.htmlsaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 53
  54. 54. IETF MPLS-TP General Definitions General Description Focus Area IETF RFC or WG documents JWT document JWT Report on MPLS-TP Architectural First milestone on MPLS-TP Joint RFC 5317 Considerations work by IETF/ITU-T IAB document Uncoordinated Protocol Dev. Inter-SDO coordination RFC 5704 Considered Harmful General MPLS-TP Terminologies Terminologies draft-ietf-mpls-tp-rosetta-stone Requirements and Frameworks Description and Focus Area IETF RFC or WG documents Requirements General MPLS-TP Requirements. RFC 5654 MPLS-TP OAM Requirements RFC 5860 MPLS-TP Network Management Requirements RFC 5951 Frameworks MPLS-TP Architecture Framework RFC 5921 MPLS-TP Network Management Framework RFC 5950 MPLS-TP OAM Architecture Framework RFC 4378 MPLS-TP Survivability Framework RFC 6372 MPLS-TP Control Plane Framework RFC 6373 MPLS-TP OAM Analysis draft-ietf-mpls-tp-oam-analysis© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 54
  55. 55. IETF MPLS-TP Data Plane, Protection Definitions MPLS-TP Protocols for Forwarding and Protection Function IETF RFC or WG documents Data Plane MPLS-TP Identifiers conformant to existing RFC 6370 ITU and compatible with existing IP/MPLS MPLS Label Stack Entry: RFC 5462 "EXP" renamed to "Traffic Class" MPLS Generic Associated Channel for In-band RFC 5586 OAM and control In-Band Data Communication for the MPLS- RFC 5718 TP MPLS TP Data Plane Architecture RFC 5960 MPLS-TP UNI-NNI RFC 6215 Protection MPLS-TP Linear Protection RFC 6378 MPLS-TP MIB Management Function IETF RFC or WG documents Management MPLS-TP MIB management overview draft-ietf-mpls-tp-mib-management-overview © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 55
  56. 56. IETF MPLS-TP OAM (FM and PM) Definitions MPLS-TP Fault Management (FM) OAM Functions OAM Functions Protocol Definitions IETF WG documents Proactive FM OAM Continuity Check (CC) Bidirectional Forwarding Detection RFC 6428 Functions (BFD) extensions Remote Defect Indication (RDI) Bidirectional Forwarding Detection (BFD) extensions Alarm Indication Signal (AIS) AIS message under G-Ach RFC 6427 Link Down Indication (LDI) Flag in AIS message Lock Report (LKR) LKR message under G-Ach Config MPLS-TP OAM using LSP Ping LSP-Ping draft-ietf-mpls-lsp-ping-mpls-tp- oam-conf On demand FM Continuity Verification (CV) LSP Ping and BFD Extensions RFC 6426 OAM Functions Loopback (LBM/LBR) 1) In-band Loopback in G-Ach RFC 6435 or 2) LSP Ping extensions Lock Instruct (LI) In-band Lock messages in G-ACh MPLS-TP Performance Management (PM) OAM Functions OAM Functions Protocol definitions IETF WG documents Proactive PM OAM Packet loss measurement (LM) LM and DM query messages RFC 6374 Functions and Packet delay measurement (DM) LM and DM query messages On demand PM OAM Throughput measurement Supported by LM Functions Delay Variation measurement Supported by DM© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 56
  57. 57. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 57
  58. 58. Global ID (operator) 4 octets (decimal) – AS Number Tunnel Number Default: 0 (non-global) 2 octets (decimal) Global scope Scope: Node ID Tunnel ID Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Num Scope: Global ID LSP Number 2 octets (decimal) Default: 0 (Working), 1 (Protect) Scope: Tunnel ID MPLS-TP LSP ID Src-Node_ID::Src-Tunnel_Num::Dst-Node_ID::Dst-Tunnel_Num::LSP_Num Scope: Global ID Router ID (Node ID) 4 octets (decimal) - Loopback scope: Global ID Link Number (Interface Number) 4 octets (decimal) scope: Node IDsaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 58
  59. 59. •  Static PWs require in-band CE PE P P PE CE status notification (no LDP notification BFD CC Bi-directional, co- BFD CC •  Existing PW Status TLV sent routed MPLS-TP LSP (Interval x (Interval x over G-ACh Multiplier) Label Multiplier) ACH OAM Msg •  Three messages sent at 1 per (Status) sec to set/clear fault thenStatic PW Status continuous messages sent at aStatic PW StatusStatic PW Status 1 per sec longer interval 1 per refreshStatic PW Status timer (default 30s)Static PW Statussaalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 59
  60. 60. Common IETF – Homogenous OAM frameworks at all layers OAM framework Ethernet Service OAM E-Line (CFM/Y.1731) MPLS Service OAM Ethernet PW (VCCV/LSP Ping/BFD) MPLS-TP IP/MPLS IETF MPLS-TP OAM PE P P PE P P PE IETF IP/MPLS OAM LSP LSP (LSP Ping, BFD, LDI/AIS/LKR, etc.) (LSP Ping/BFD) ITU-T – Heterogeneous OAM frameworks at transport layer Ethernet Service OAM E-Line (CFM/Y.1731) Operational complexity / MPLS Service OAM Ethernet PW inefficiency (VCCV/LSP Ping/BFD) MPLS-TP IP/MPLS ITU-T MPLS-TP OAM Proposal PE P P PE P P PE IETF IP/MPLS OAM (G.8113.1/Gtpoam – Y.1731 based) LSP LSP (LSP Ping/BFD)saalvare@cisco.com - © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 60
  61. 61. Thank you.

×