1 / 33

New Services from the RIPE NCC

New Services from the RIPE NCC. Henk Uijterwaal RIPE NCC New Projects Group NANOG-26, Eugene, OR October 29, 2002. Outline. 2 services from the RIPE NCC Test Traffic Measurements Routing Information Service Follow-up on talks at the Winter 2000 meeting. Part 1 Test Traffic Measurements.

rfreda
Download Presentation

New Services from the RIPE NCC

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. New Services from theRIPE NCC Henk Uijterwaal RIPE NCC New Projects Group NANOG-26, Eugene, OR October 29, 2002

  2. Outline • 2 services from the RIPE NCC • Test Traffic Measurements • Routing Information Service • Follow-up on talks at the Winter 2000 meeting

  3. Part 1Test Traffic Measurements

  4. TTM 101 • Project to do performance measurements on the Internet • Delay • Loss • Routing • One way, active, “real” traffic • Inter-provider networks only • Hard for individual provider • Techniques can be used for internal networks though • Scientifically defendable, well defined standards • IETF IPPM, RFC’s: 2330, 2679, 2680, ...

  5. TTM Service Goals • Black box • No configuration by the user • No user access • Guarantees well-defined environment for the measurements • Easy to install, little maintenance • Available to the entire community All you have to do, is to look at the results

  6. Test-box Locations

  7. CDMA Clocks • Independent clock source necessary • Installing a GPS clock is not always easy • Any alternatives to GPS? • CDMA • 3rd generation mobile phone standard • Phones needs a time signal • GPS Sync’ed base stations broadcast time signal • Can this be used for TTM?

  8. CDMA Clocks • Yes! Same accuracy • Praecis CT • “Phone without speaker, mike and keypad” • http://www.endruntechnologies.com • Works everywhere your cell phone works • Simply mount on a wall • $0.02 installation costs

  9. Alarms and near real-time plots • So-far, 6-30 hour delay between collection and plots on the web • All kinds of reasons why this is too slow: • Angry customer • Alarm from the box • … • Interface for this, recent plots, few minutes delay • Public Demo: http://tt01.ripe.net:10259/ • Also gives access to configuration and status information

  10. User Interface

  11. Current Measurements Rate, target, packet size Status Who set this up: TTM Crew You (somebody at your site) They (somebody at the other side) User Interface • Data volume (bits/second)

  12. Daily report

  13. Daily Report (2)

  14. IP-Delay Variations or Jitter • For some applications, the absolute delay does not really matter • However, packets should arrive with constant intervals • Voice over IP • Video on demand • Metric and Plots

  15. Trends • Delay over 6 months  Night Morning Afternoon  Evening • Content provider with new customers • Intended for capacity planning Median Delay April 1 November 1

  16. IPv6 version • IPv6 networks so-far • Tunneled over v4 • Performance monitoring was an afterthought • Several native IPv6 network now operational • Interested in performance measurements from the start • Use existing products: RIPE NCC TTM • Porting • -testing, production version by December

  17. Bandwidth • The next measurement to be added • 2 Parameters: • C: Total Capacity • A: Available Bandwidth • Method based on packet dispersion • Available on the box

  18. Part 2Routing Information Service

  19. RIS 101 • 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

  20. Motivation • Something is wrong with your routing • Current tools: • Log in to your router • Use a looking glass on other routers • 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)

  21. Goals of the RIS • Set up route collectors that collect BGP announcements between AS’s • Time-stamp and store in a data-base • Set up interactive queries to database • Giant looking glass with history • Network reachability from other networks • Provide raw data and statistics • for reality checks, RRCC project • to generate trend analysis • Available to the Community

  22. 9 Route Collectors RIPE NCC LINX AMS-IX SPINX CIXP VIX Netnod MAE-West NSPIXP2 200 peering sessions Route Collectors

  23. Growing by about 250/month in 2002 More and more sites are multi-homed AS’s seen

  24. CDF for the number of peers

  25. Simple queries • AS by time • RIB for an AS at a given time • Announcements since then • Prefix by time • AS in use • Is your AS seen anywhere? • Startup, registration • Plots • Number of updates • Prefix distribution • …

  26. Hyperlinked “Host spots” webpage(Most active prefixes)

  27. “Host spots” webpage(Most active prefixes) (2) Updates during the queried period: Type Prefix Time Peer AS Path A 193.73.204.0/24 2002-10-01 00:00:03 64.211.147.146 3549 701 702 15623 A 193.73.204.0/24 2002-10-01 00:00:04 64.211.147.146 3549 701 702 15623 A 193.73.204.0/24 2002-10-01 00:00:05 64.211.147.146 3549 701 702 15623 A 193.73.204.0/24 2002-10-01 00:00:12 64.211.147.146 3549 701 702 15623 A 193.73.204.0/24 2002-10-01 00:02:00 64.211.147.146 3549 701 702 15623 A 193.73.204.0/24 2002-10-01 00:02:30 64.211.147.146 3549 701 702 15623 A 193.73.204.0/24 2002-10-01 00:02:54 64.211.147.146 3549 701 702 15623 A 193.73.204.0/24 2002-10-01 00:03:28 64.211.147.146 3549 701 702 15623 A 193.73.204.0/24 2002-10-01 00:06:38 64.211.147.146 3549 701 702 15623 A 193.73.204.0/24 2002-10-01 00:06:39 64.211.147.146 3549 701 702 15623 A 193.73.204.0/24 2002-10-01 00:06:43 64.211.147.146 3549 701 702 15623 A 193.73.204.0/24 2002-10-01 00:07:11 64.211.147.146 3549 701 702 15623 A 193.73.204.0/24 2002-10-01 00:07:39 64.211.147.146 3549 701 702 15623 A 193.73.204.0/24 2002-10-01 00:08:00 64.211.147.146 3549 701 702 15623

  28. MartiansThe list you don’t want to be on... • Prefixes not allowed by draft-manning-dsua • Loopback • RFC1918 space • Class D/E-space, … • Usually private addresses leaking into the public space • Daily list with prefixes and origins

  29. BGP Beacons • Prefixes intentionally announced at known times by each route collector • Announced at 0, 4, 8, 12, 16, 20 GMT • Withdrawn at 2, 6, 10, 14, 18, 22 GMT • Prefix 195.80.(224+n).0/24 • N=0…8 for the RRC’s • Part of the RIS AS 12654 • Intended for flapping and dampening studies • Active since 30/9/2002

  30. MyAS • Currently: user has to visit our webpages • Reverse approach: • List AS’s and prefixes • Warn if something happens to them • Prototype RIPE44

  31. Participate in TTM or RIS? • TTM • Buy a test-box, sign service contract, pay invoice • http://www.ripe.net/test-traffic/Host_testbox/ • Plug and play • Start looking at the data • RIS • Send peering details to ris-peering@ripe.net or • Fill in form at http://www.ris.ripe.net/cgi-bin/peerreq.cgi • 1 or 2 days to set this up

  32. TTM http://www.ripe.net/test-traffic Papers Presentations “For future test-box hosts” ttm@ripe.net: TTM Crew @ NCC tt-wg@ripe.net: RIPE WG on this topic (Majordomo) RIS http://www.ripe.net/ris/ris-index.html Presentations Access to the data ris@ripe.net: RIS Crew @ NCC routing-wg@ripe.net: RIPE WG on this topic (Majordomo) URL’s, Contact Addresses

  33. Questions, Discussion

More Related