1 / 19

Measurement of Routing Switch-over Time with Redundant Link

This presentation discusses the evaluation of switch-over time for redundant links in research networks, focusing on two cases: APII Fukuoka-Tokyo path and JP-US connection over TransPAC2/JGN II. The aim is to minimize service disruption in case of outages.

vstephens
Download Presentation

Measurement of Routing Switch-over Time with Redundant Link

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. Measurement of Routing Switch-over Time with Redundant Link August 25, 2005 NOC-Network Engineering Session Advanced Network Conference in Taipei Masaki Hirabaru (NICT),Teruo Nakai (KDDI),Yoshitaka Hattori (KDDI),Motohiro Ishii (QIC), and Yasuichi Kitamura (NICT)

  2. Motivations • Research Networks are getting complicated in the AP region. • Situation: many redundant (back-up) links with dynamic routing (instead of SONET or L-2 redundancy) • Evaluation: how fast they can switch over in case of outages • Improvement: how we can minimize service disruption time Two Cases APII Fukuoka-Tokyo Path over JGN II (Japan Domestic Part) JP-US Path over JGN II / TransPAC2 (at Tokyo)

  3. Routing Switchover from Link A to B Failure Resume Service Disruption Link A Link B Time packets reorder FailureDetection RoutingTransient Test Packet Train

  4. Case 1: APII Seoul-Tokyo Connection Seoul XP Korea Daejon 10G JGNII KOREN Taegu Tokyo XP Kwangju TransPAC2 Busan 10G Northern Route(1G) 2.5G SONET 1,000km APII/JGNII Southern Route(10G) Fukuoka Genkai XP Fukuoka Japan JGN II : L2 ServiceNo Fault Detection!=> L3 User-side Detection

  5. APII Fukuoka-Tokyo Configuration over JGN II iBGP Peering with loopback address apii-juniper 203.181.248.118 203.181.248.226 Northern Route (VLAN 1G) Kanazawa OSPF metric 90 Fukuoka 4/22 x 5/16(18) 203.181.248.117 x OSPF metric 9 tpr4 Okayama Osaka 203.181.248.225 Tokyo Southern Route (VLAN 10G) Switch (L2) Router (L3)

  6. Detecting Switchover Period #1 (APII) two maintenance outages 2005-04-22 Tokyo -> FukuokaNorthern RouteTraffic Graph Tokyo -> FukuokaSouthern RouteTraffic Graph 810 packets / sec = 10 Mbps (MTU 1500B UDP) ~ 1ms resolution Fukuoka -> Tokyo: time 2005/04/22 02:07:46-02:08:23 JST gap 37.1s loss 30264time 2005/04/22 04:02:38-04:03:15 JST gap 36.8s loss 29975Tokyo->Fukuoka: (Unsuccessful measurement)

  7. OSPF Hello Intervals Default: hello interval 10 secs dead interval 40 secs Proposal: hello interval 1 sec (minimum) dead interval 4 secs OSPF adjacency will be lost while parameters are inconsistent among peers. Another way would be using BFD available JUNOS 7.X.

  8. Detecting Switchover Period #2 (APII) Tokyo -> FukuokaNorthern Route Traffic Graph 2005-05-16 Tokyo -> FukuokaSouthern Route Traffic Graph 1000 packets / sec = 1 Mbps (58B UDP) ~ 1ms resolution Fukuoka -> Tokyo: time 2005/05/16 02:17:16-02:17:21 JST gap 5.6s loss 5637 Tokyo->Fukuoka: time 2005/05/16 02:17:16-02:17:20 JST gap 4.1s loss 4116

  9. Case 2:JP-US Connection over TransPAC2 / JGN II Michigan packets JGN II routes TransPAC2 Tokyo Packets are sent at MichiganRoutes are injected at Tokyo

  10. Tokyo - Michigan L3 Configuration AS237 141.211.0.0/16 ge-1-1-0x984 192.122.183.93 v-bin-arbl192.122.183.93 AS22335 192.122.182.18 206.220.240.154 ge-2-3-0x986192.122.183.197 Ann Arbor - Chicago 206.220.240.161 5ms AS22388 192.122.183.13 transpac-chi 192.203.116.9 192.122.182.18 80ms chinng198.32.11.97 AS7660 iplsng198.32.8.77 dnvrng198.32.8.13 kscyng198.32.8.81 snvang198.32.8.1 tpr4203.181.248.218 AS11537 losang 198.32.8.94 transpac-la 207.231.240.136 133.69.35.1 56ms JGN II Int’l and TransPAC2: - SONET OC-192 unprotected - L2 fault detection provided tpr5192.203.116.146 AS22388

  11. Detecting Switchover Period #3 (TransPAC2) * Announce /24 into the both JGN II and TransPAC2 LA -TokyoTransPAC2 Traffic Graph 100 packets / sec = 100 Kbps (58B UDP) ~ 10ms resolution 7/30 607 ms 8/02 647 ms Resume Failure TransPAC2 JGN II Time 5-10 packets reorders in 5-10 ms

  12. Detecting Switchover Period #4 (JGN II) * Announce /24 into the both JGN II and TransPAC2 100 packets / sec = 100 Kbps (58B UDP) ~ 10ms resolution 7/29 1448 ms 8/03 837ms Resume Failure JGN II TransPAC2 Time 45 ms (7/29)1773 ms (8/03) no reorders BGP down (Tokyo)

  13. Detecting Switchover Period #5 (TransPAC2) * Announce /24 for JGN II and /25 for TransPAC2133.69.35.0/24 and 133.69.35.0/25 100 packets / sec = 100 Kbps (58B UDP) ~ 10ms resolution 8/05 512 ms Resume Failure TransPAC2 JGN II Time No packets reorders

  14. Artificial Route Change 1) Keep announce a /24 route from Tokyo2) Announce the /25 route to another link, then 3) Withdraw the /25 route TimeAD = TimeS – TimeA TimeWD = TimeS – TimeW Michigan Michigan Chicago Packet(before) Chicago Packet(after) Times TimeA A W Tokyo Tokyo Packet(after) Packet(before) Timew Times

  15. A-1 Flap TransPAC 2 /24 JGN II A W /25 TransPAC2 TimeAD 196 ms TimeWD 193 ms A-2 Flap JGN II /24 TransPAC2 A W /25 JGN II TimeAD 2106 ms TimeWD 1922 ms

  16. Route Propagation Delays (1) Delays from Tokyo to Oregon Routeview 2152 2153 22388 7660 : 6 secs (via LA) 293 10764 22388 7660 : 5 secs (via LA) 10876 3701 4600 11537 22388 7660 7660 7660 : 23 secs (via CHI) 2152 2153 11537 22388 7660 7660 7660 : 36 secs (via CHI) No BGP Updates available in Abilene?

  17. Route Propagation Delays (2)- Tokyo to Seoul: BGP Peering Topology - AS17579 seoul AS11537 AS9270 daejon AS2907 10G JGNII AS7660 busan tokyo4 tokyo5 TransPAC2 10G koganei monitor generator (A / W) 2-hour intervals fukuoka AS64582 133.69.36.0/24http://mrtg.koganei.itrc.net/cgi-bin/bgproute2.cgi AS2523 Acknowledgement to JaeHwa Lee @ KOREN

  18. Route Propagation Delays (2) - Results - Announce delays (unit is millisecond) Withdraw delays (unit is millisecond)

  19. Summary • Avoid Ethernet multiple access device (L2 switch) • If no, decrease Hello (heartbeat) intervals, or use BDF • Inject alternates routes with longer prefixes • Loop-free alternates and fast reroute (future work) • Fast route propagation has been not well considered • Need overseas test points continuous 0.1Mbps traffic (10ms resolution) • Millisecond-order event timestamps (BGP updates, link failure, etc…) • Less restriction for IP options and ICMP • Global IP addresses for routers • Harmful route dampening • Route exits controlled by BGP Community Abilene / StarLight Router Proxy is helpful to check the routes.

More Related