fast reroute for triple play networks
play

Fast Reroute for Triple Play Networks Sachin Natu Product - PowerPoint PPT Presentation

Building Smart Broadband Networks TM Fast Reroute for Triple Play Networks Sachin Natu Product Management March 2006 IPTV Service Requirements IPTV Network Design Fast Reroute / Convergence Solutions - MPLS FRR - IGP Fast Convergence -


  1. Building Smart Broadband Networks TM Fast Reroute for Triple Play Networks Sachin Natu Product Management March 2006

  2. IPTV Service Requirements IPTV Network Design Fast Reroute / Convergence Solutions - MPLS FRR - IGP Fast Convergence - NextHop FRR 2

  3. IPTV catching on 1600 1400 1200 1000 Asia Pac IPTV subscribers 800 Americas ('000s) Europe 600 400 200 Worldwide, eight IPTV providers have 0 50,000 or more subscribers Q4 2004 Q2 2005 IPTV subscribers grew 40% 500 in first-half 2005 to 1.47 million 400 IPTV 300 subscribers at mid-2005 ('000s) 200 100 0 PCCW FastWeb Chunghwa Qwest Free (France) France Telecom China Telecom Telefonica Source: Point Topic BroadBand User Service 3

  4. IPTV High Availability Requirements Step 6 In Service SW Upgrade Step 5 Session Level Reliability Step 4 Routing Protocol Reliability Step 3 Modular Software Step 2 Separation of Forward & Control Step 1 Hardware Redundancy 4

  5. Protection Needs � Mission critical applications � Delay sensitive services such as VoIP, high quality video, Pseudo Wire services � L3VPN, L2VPN, VPLS networks mainly use IP and LDP � Goal is to minimize packet loss when network elements fail 5

  6. IPTV Service Requirements IPTV Network Design Fast Reroute / Convergence Solutions - MPLS FRR - IGP Fast Convergence - NextHop FRR 6

  7. IPTV Broadband Architecture NSP Network NSP-1 PPPoE or IP for current & new serivices IP, ATM or Ethernet NSP-2 BNG AN PC ATM, Ethernet RG TV Set-Top IP IPoE, Multicast streaming IPoE, IPTV Network IGMP control traffic STB * Multicast streaming IGMP control traffic IGMP Control RG Coordinate subscriber MC traffic with subscriber PC BNG PPPoE, Unicast information via MAC address PPPoE, or via the PPPoE session. IGMP Proxy Subscriber sessions IGMP Termination IPoE, Multicast streaming IGMP control traffic AN PPPoE, Unicast IGMP Snooping 7

  8. IPTV Network Architecture PC RG TV Data Network Set-Top Internet PC RG NSP-2 TV Set-Top IP PC RG TV Set-Top IPTV Network PC RG TV DSLAM Service Node Set-Top 8

  9. IPTV Network Ring Design IP, MPLS Backbone 2 1 3 4 Separate OSPF area 6 Fast IGP convergence 5 BFD as link failure detection 8 7 10 9 11 12 9

  10. IPTV Service Requirements IPTV Network Design Fast Reroute / Convergence Solutions - MPLS FRR - IGP Fast Convergence - NextHop FRR 10

  11. Ring Design Fast Restoration Solution – Fast Restoration… � How fast is fast ? 50 msec. ? � How fast is needed ? – Handle non MPLS TE traffic when traffic engineering is non-goal – Be simple, in terms of mechanism, development, configuration, computation, deployment and maintenance 11

  12. 1. Detection Delay 2. Propagation Delay Fast Restoration Steps 3. Calculation Delay 1 2 3 4 Detection Delay is time 6 5 independant of the Fast Restoration solution used. 8 7 10 x 9 11 12 1. Media dependant a. SDH, SONET: b. Ethernet: 802.1ag Ethernet OAM 2. Light Out 3. Media in-dependant a. Bidirectional Forward Detection (BFD) 12

  13. 1. Detection Delay 2. Propagation Delay Fast Restoration Steps 3. Calculation Delay 1 2 3 4 Propagation Delay very 6 5 dependant on the Fast Restoration solution used. 8 7 10 x 9 11 12 1. Internal in Box a. is part of all solutions b. internal architecture dependant 2. Across the Network a. MPLS FRR: Not relevant b. IGP Fast Convergence: Protocol optimization dependant c. Nexthop FRR: Not relevant 13

  14. 1. Detection Delay 2. Propagation Delay Fast Restoration Steps 3. Calculation Delay 1 2 3 4 Calculation Delay very 6 5 dependant on the Fast Restoration solution used. 8 7 10 x 9 11 12 1. Box dependant a. MPLS FRR: Not relevant b. IGP Fast Convergence: Protocol optimization dependant c. Nexthop FRR: Not relevant 14

  15. MPLS FRR in the Ring RFC 4090 Pros: – Switch-over time less than 50 milliseconds Cons: – Complication of setup MPLS TE LSPs – Issues of supporting IP unicast, multicast and LDP traffic – MPLS TE network needs constant tuning Repair Time: ”Detection Delay” + ”Internal Propagation Delay” Internal + Detection Delay Propagation Delay 15

  16. IGP Fast Convergence Pros: – Simple solution, based on “normal” IP routing – Protect all types of traffic Cons: – Convergence time dependant of failure place – Does not meet the 50 msec magic number requirement Repair Time: ”Detection Delay” + (n * ”Internal Propagation Delay”) + ”Calculation Delay” + + 1 DD PD CD + 2 PD CD + n PD CD 16

  17. IGP Fast Convergence Forwarding Plane Routing PIM Detection Protocol LDP � IGP MUST be implemented in a ”event driven” mode to allow for immidiate SPF calculation � IGP MUST be implemented with a ”fall back” to timer SPF calculation in case of network instability � PIM MUST be implemented in a mode to remember join & leave messages from unexpected interfaces � LDP MUST advertise all labels to everybody, and make it the responsibility of the receiver to discard labels. 17

  18. Next-Hop Fast ReRoute Solution Pros: – Switch-over time less than 50 milliseconds – Protect all types of traffic Cons: – Multicast PIM and LDP protocol enhancement for node protection (This is required by any next-nexthop solution, so not a real-life cons. but more a fact of life) Repair Time: ”Detection Delay” + ”Internal Propagation Delay” Internal + Detection Delay Propagation Delay 18

  19. Next-Hop Fast ReRoute Solution � Nexthop Fast ReRoute (NFRR) can perform fast re-route for any type of traffic in the event of a link/node failure or a nexthop unreachable. � The protected traffic can be IP, MPLS, unicast or multicast. � The re-routed traffic can either be destined to the nexthop router or to the next-nexthop router. RSVP explicitly routed LSPs are used as a tool to perform the local patch for minimizing the packet loss. � The LDP protocol only needs to know label mapping for the adjacent peers and there is no way for an LSR to learn the adjacent peer's downstream label mapping. As such an LDP extension that allows an LSR to discover the next- nexthop label mapping from its downstream peers is needed for node-protection using the NFRR solution. � A PIM node knows the direct downstream neighbors, but currently it has no mechanism to learn the downstream nodes of the adjacent neighbors, or the next- nexthop downstream nodes. As such an PIM-SM extension to allow a PIM node to discover its next-nexthop downstream neighbors is needed for node-protection using the NFRR solution. 19

  20. Summary Detection Delay is part of all Fast Restoration solutions, so select a fast, scalable non media dependant solution like BFD. New technology and processor performance have made IP Fast Convergence a valid ”Fast Reroute” solution for IP and LDP traffic in 100s of msec failover. A MPLS Fast Reroute implementation like ”NFRR” is needed to create a common Fast Reroute solution for all kind of traffic and 10s of msec failover. 20

  21. TM Building Smart Broadband Networks www.redback.com www.redback.com 21

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend