1 / 25

RIPE NCC Routing Information Service Status and plans

RIPE NCC Routing Information Service Status and plans. Arife Coltekin, Luigi Corsello, Daniel Karrenberg, Henk Uijterwaal, Matthew Williams Presented by Olaf Kolkman RIPE NCC New Projects Group RIPE41, Amsterdam, January 2002. Outline. Introduction Remote Route Collectors

cianna
Download Presentation

RIPE NCC Routing Information Service Status and plans

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. RIPE NCC Routing Information ServiceStatus and plans Arife Coltekin, Luigi Corsello, Daniel Karrenberg, Henk Uijterwaal, Matthew Williams Presented by Olaf Kolkman RIPE NCC New Projects Group RIPE41, Amsterdam, January 2002

  2. Outline • Introduction • Remote Route Collectors • Making the RIS more useful for daily operations • Data analysis • Conclusions

  3. What is the RIS? • AS1’s NOC gets a user complaint: • “Last night, I could not reach www.x.com.” • AS1’s NOC looks at the current routing tables • “Well, it works now” Router AS2 Router AS5 AS1 www.x.com User AS3 AS4

  4. Motivation • Problem with your (AS-level) routing • Current tools: • Log in to your router • Use a looking glass on other routers • All kinds of problems: • How to find right looking glass? • What if the looking glass cannot be reached either? • Accessing multiple LG’s takes a lot of time • No history mechanism • Solution: Routing Information Service (RIS)

  5. The RIS • Collects default-free time-stamped BGP announcements between AS’s and store them in a data base • At several points on the Internet • Set up interactive queries to database • Provide raw data • Provide analysis • Available to the Community

  6. Outline • Introduction • Remote Route Collectors • Making the RIS more useful for daily operations • Data analysis • Conclusions

  7. Remote Route Collectors • Collect BGP updates from all interested parties at an IX • 4 new collection points since last year • Next: • MAE-west • US east coast

  8. #Peering Sessions # Sessions 15 56 13 42 10 40 5 ? 181 • 0: RIPE-NCC • 1: LINX • 2: SFINX • 3: AMS-IX • 4: CIXP: Geneva • 5: VIX: Vienna • 6: NSPIXP2: Tokyo • 7: Netnod-IX (Stockholm)

  9. Your data in the RIS? • Yes, please! • Send peering information to: • rispeering@ripe.net • http://abcoude.ripe.net/ris/peerreg.cgi • The RIS will not announce any routes, nor will it send any traffic to your site

  10. Administrative stuff • RIS users lists: ris-users@ripe.net • Majordomo • Operational information • Announcements about changes in the RIS • Downtime • Problems with the data • Future: Discussion of problems when analyzing the data

  11. Outline • Introduction • Remote Route Collectors • Making the RIS more useful for daily operations • Data analysis • Conclusions

  12. Making the RIS more useful for daily operations • FAQ with answers • Manual • Typical examples/cases studies • Annotated screen dumps • Will add more cases • Let us know if this is useful

  13. Manual example

  14. Looking Glass on the boxes • There is a time-gap between data-collection and data-insertion • 1 hour • To cover this, we added a Looking Glass on the RRC • Standard Looking Glass code • Available on all rrc’s • Start from RIS homepage

  15. Top10 of most active prefixes • Generates lists of the most active prefixes • Announcements or withdrawals • Top10, 25 or 50 • 3, 6, 12 or 24 hours • Large number of updates may indicate a problem • CGI-script to find them • Available on demand • We will run it regular to produce a monthly top10 • http://abcoude.ripe.net/ris/topten.cgi

  16. Most active prefixes Most active prefixes

  17. Most active prefixes

  18. Most active prefixes • Next steps: • Top10 by origin AS • Look for Withdrawal-Announcement sequences • “Flaps” • Produce statistics

  19. Outline • Introduction • Remote Route Collectors • Making the RIS more useful for daily operations • Data analysis • Conclusions

  20. RISreport • First version released last summer • Wanted to add new plots • Scalability problems • Decided to re-implement the SQL2RRD tool • November-January • Switch over in the next weeks • Long list of variables that can be added

  21. RISreportComparison old/new New Old

  22. Total number of prefixes seen RRC0/NCC, RRC6/NSPIXP2, RRC1/LINX, RRC3/AMS-IX

  23. Outline • Introduction • Remote Route Collectors • Making the RIS more useful for daily operations • Data analysis • Conclusions

  24. Conclusions • FAQ and a manual, to make the RIS more useful for daily operations • New queries • More data • Next steps: • Extend RISreport • Flaps • Your feedback

  25. URL: http://www.ripe.net/ris Mail: ris@ripe.net (General info) ris-users@ripe.net (For people using the data) rispeering@ripe.net (To set up peerings) Questions, Discussion

More Related