29
Erik Romijn http://www.ripe.net RIPE Network Coordination Centre RIPE 55, Amsterdam, The Netherlands, October 2007 RIS update Erik Romijn <[email protected]> Information Services Team RIPE NCC 1

RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

  • Upload
    others

  • View
    0

  • Download
    0

Embed Size (px)

Citation preview

Page 1: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

Erik Romijn http://www.ripe.net

RIPE Network Coordination Centre

RIPE 55, Amsterdam, The Netherlands, October 2007

RIS update

Erik Romijn <[email protected]>

Information Services TeamRIPE NCC

1

Page 2: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 20072

What is RIS?

• Routing Information Service

• Looking glass with history

• Collects routing information (BGP)- 590 peers

- 14 collectors running Quagga bgpd

- Peering from AS 12654

• 3 months data in MySQL database

• Query tools at http://www.ripe.net/ris/

Page 3: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

What is RIS?

• All raw data available for download- Standard format (MRT)

• Generates statistics reports

• Notification system: MyASN- Notifies you when someone else announces your prefix

3

Page 4: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

What is RIS?

• For each collector:- Three “RIB” dumps a day: all prefixes seen at that time

- “Update” dumps every 5 minutes: all updates seen

- Stored in MySQL database and as raw data (MRT)

• Beacon and anchor routes announcedfrom collectors- Beacons are 2hrs on, 2hrs off

- Anchors are always-on

- One anchor, one beacon per collector

- Beacons and anchors also on IPv6

4

Page 5: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

Erik Romijn http://www.ripe.net

RIPE Network Coordination Centre

RIPE 55, Amsterdam, The Netherlands, October 2007

RIS status

5

Page 6: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

14 Remote Route Collectors (RRCs)

6

Running

Setup

Page 7: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

How many peers?

7

0

100

200

300

400

500

600

700

2003

2004

2005

2006

2007

Removing inactive peers

Page 8: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

Session distribution: IPv6 and IPv4

• Most IPv6 is full table

8

Page 9: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

How much raw data?

9

0GB

200GB

400GB

600GB

800GB

2000

2001

2002

2003

2004

2005

2006

2007

16GB each month

Page 10: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

MySQL database size (3 months of data)

10

200GB

300GB

400GB

500GB

600GB

700GB

800GB

Mar

ch ‘0

6

June

‘06

Sept.

‘06

Dec. ‘0

6

Mar

ch ‘0

7

June

‘07

Sep ‘0

7

(approximate values)

Page 11: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

Average hosts per month on website

11

0

2,500

5,000

7,500

10,000

12,500

15,000

July

‘06

Sep. ‘0

6

Nov. ‘0

6

Jan

‘07

Mar

‘07

May

‘07

Jul ‘0

7

Sep ‘0

7

Tools Raw data

Page 12: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

Other interesting numbers

• Prefixes seen (some IGP in here):- IPv4: 253,450

- IPv6: 1190

• Multiple originating AS prefixes (excluding 6to4):- IPv4: 1462 from 1061 ASes

- IPv6: 8 from 26 ASes

• Single-homed ASes: 8182 (30%)

• Average AS path length: 6.23 ASes

• Least stable prefix: 1,194,574 updates per week

• More on http://ris.ripe.net/weekly-report/

12

Page 13: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

Erik Romijn http://www.ripe.net

RIPE Network Coordination Centre

RIPE 55, Amsterdam, The Netherlands, October 2007

What keeps us busy?

13

Page 14: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

Debogonising project

• IANA assigns new /8 to RIR

• RIS announces set of prefixes from /8

• RIS measures reachability of prefixes and sets up pingable addresses

• Participating RIRs:- AfriNIC

- APNIC

- LACNIC (since October 2007)

- RIPE NCC14

Page 15: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

How do we measure visibility?

15

AS3 AS4

AS1 AS2

RIS

RIS

Normal prefixNew prefix

Conclusion: AS2 is likely to be filtering

AS5

3 out of 4 do not filter, 75% visible

Page 16: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

But, what do we see?

16

0%

20%

40%

60%

80%

100%

Start

End

Page 17: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

Our “problem” with debogonising

• Every graph looks the same:- A roughly straight line around 90%

• Why?- Almost everyone updates before we start measuring

(several days in most cases)

- Few ASes filter bogons

- Our measurements or method are inaccurate

• Test: start measurements as early as possible- July 25, 2007: 94/8 and 95/8 allocated to RIPE NCC

- RIS announced prefixes within 10 minutes after IANA registry update

17

Page 18: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

Visibility of 95/8, first 54 hours

18

70.0%

72.5%

75.0%

77.5%

80.0%

82.5%

85.0%

87.5%

90.0%

17:4

021

:40

1:40

5:40

9:40

13:4

018

:40

23:4

0

Cymru bogon filter update

Conclusions:• 75% of our dataset does not filter• Most filters are updated within 48hHowever, dataset is only 105 ASes..

Page 19: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 200719

RIS screenshot, RIPE 36, May 2000

Page 20: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 200720

After 7 years...

Page 21: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

Presentation of data

• Basics have been the same since ~2000- Long lists of text

- Very useful, but not very attractive

• Some useful queries could not be answered- Prefixes originated from an AS

- Visibility of a prefix

• Project started to improve presentation- In a reasonably short time

21

Page 22: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 200722

About RIPE NCC | Contact | Search | Sitemap

Routing Information Service

you are here: home -> RIPE NCC Projects -> RIS

RIS:

RIS Home Page

Tools

Statistics

RIS Raw Data

Documentation

RIS Analysis Links Page

Related Sites

Contact Us

Send Feedback

All comments and suggestions to improve our tools are welcome, please let us know.

AS dashboard: AS 3333

Query for a different AS, or for a prefix: Query

RIPE-NCC-AS RIPE Network Coordination Centre [ Whois data ]

Note: this is not a production service (yet). Performance is not yet at a sufficient level. The purpose of this service is to serve as prototype to collectfeedback on our new way of presenting data.

Overview Prefixes Upstreams AS path lengths Whois Former bogon filtering Update graphs

Prefix size distribution

Average AS path length to each collector

Upstream distribution

About RIPE NCC | Site Map | LIR Portal | About RIPE | Contact | © RIPE NCC. All rights reserved.

Page 23: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 200723

Still prototype!http://ris.ripe.net/dashboard/<as/prefix>

Page 24: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 200724

Page 25: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 200725

Page 26: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

Erik Romijn http://www.ripe.net

RIPE Network Coordination Centre

RIPE 55, Amsterdam, The Netherlands, October 2007

Next steps

26

Page 27: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

Performance

• The RIS database is >700GB

• We would like to make it faster

• Hardware and software are due for updating

• Existing database setup can be optimised further

• Next project: improve the RIS database architecture:- Better performance

- More scalable

- Easier to maintain

- More redundancy

27

Page 28: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

RIPE Network Coordination Centre

Erik Romijn http://www.ripe.netRIPE 55, Amsterdam, The Netherlands, October 2007

Feedback is welcome

• What do you think of our new (and existing) tools?

• What data do you want from RIS?

• Why do you use RIS?

• Talk to us:- In person at the meeting

- On [email protected]

28

Page 29: RIPE 54 RIS update · -“Update” dumps every 5 minutes: all updates seen-Stored in MySQL database and as raw data (MRT) • Beacon and anchor routes announced from collectors-Beacons

Erik Romijn http://www.ripe.net

RIPE Network Coordination Centre

RIPE 55, Amsterdam, The Netherlands, October 200729

Questions?