Transcript
Page 1: Softlayer Technologies texasipv6taskforce

Matt ChilekVP, Software DevelopmentSoftLayer Technologies, [email protected]:f0d0::

Page 2: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 2

Background

• SoftLayer has around 32,000 physical servers under management

• These are clustered into 4,000 server ‘pods’• A group of pods is supported by a regional network core• Network cores are interconnected, and supported by a

network of POPs• Datacenters are located in Dallas, Seattle, Washington, DC• Current cumulative sustained IPv4 traffic of 222Gbps• Current IPv6 traffic: 50Mbps base, peak 200Mbps

10/12/2010

Page 3: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 3

Background

10/12/2010

Page 4: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 4

IPv6 initiative

• Began looking at IPv6 in 2008• Received ARIN allocation of /32• IPv6 initiative driven by long term planning, SoftLayer is an

early adopter• Beta tested IPv6 customers in fall 2008, plus hardware

upgrades• January 21, 2009 - GA launch• softlayer.com is currently a top 50 IPv6 website by both

host and raw domainhttp://bgp.he.net/ipv6-progress-report.cgi

10/12/2010

Page 5: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 5

Implementation Problems

• Network hardware• Provider support• Allocation scheme• Tracking application• Operations support• Customer adoption

10/12/2010

Page 6: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 6

P1. Network hardware

• Some equipment did not support IPv6, even in dual stack.• Some equipment did not support a dual stack without

firmware updates. • Some equipment supported IPv6, but had limited

implementation feature sets.

10/12/2010

Page 7: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 7

S1. Network hardware

• No IPv6?Solution: Tunnels

• Firmware or software upgrades?Solution: Staggered maintenance

• Limited feature sets?Solution: Use what you have to get it done.

10/12/2010

Page 8: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 8

P2. Provider support

• Initial trouble finding provider to support our implementation scheme

• Allocated a /32 from ARIN• Provider accepts /32 or larger• 3 datacenters, but don’t want to anycast• Ask ARIN for 2 more /32s, not going to happen*

*Before discrete network rules amendment

• Ended up anycast anyways• Provider finally allowed us to broadcast /36

10/12/2010

Page 9: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 9

S2. Provider support

10/12/2010

+ others

LOTS OF PEERING!

Page 10: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 10

P3. Allocation scheme

• Almost no published “best” practices • No best practices for our organizational complexity

10/12/2010

Page 11: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 11

S3. Allocation scheme

• Best practices?!!Solution: Went with our own…– /40: region– /48: router– /64: host

10/12/2010

Page 12: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 12

P4. Tracking application

• SoftLayer tracks and routes about 91,000 distinct IPv4 subnets assigned to customer hosts in the SoftLayer datacenter.

• Used “dense tree” tree for IPv4 tracking.

10/12/2010

Page 13: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 13

“Dense tree” tracking

/24

/25

/26

/27

/26 /26/26

/25

/27/27

/29

/28

/29

/29

/28

/29

/29

/28

/29

/29

/28

/29

/29

/28

/29

/29

/28

/29

/27 /27/27

10/12/2010

Page 14: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 14

S4. Tracking application

• Used “sparse tree” tree for IPv6 tracking– Fit into our existing data model with minor updates– Use existing search algorithms– Feels the same to the end user

10/12/2010

Page 15: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 15

“Sparse tree” tracking

/32

/40

/48/48 /48/48

/40

/64/64 /64/64

/64

/64

/64

/64

/64

/64

/64

/64 /64

10/12/2010

Page 16: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 16

P5. Operations support

10/12/2010

• “Uh, that’s a lot of numbers and letters and stuff” – anonymous support technician

Page 17: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 17

S5. Operations support

10/12/2010

• Make it look like your IPv4 tools!• Feels the same, looks the same, acts the same, therefore must

be the same.– It largely is the same.

• Automate as much as possible. Human brains can only carry so many numbers, and 32 is too many.

Page 18: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 18

P6. Customer adoption

• Why should customers start adopting? • Our external customer typically doesn’t understand the size of

the IPv6 address space

10/12/2010

Page 19: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 19

S6. Customer adoption

• Application wise, same as operations– We make it look like our IPv4 tools.

• We found a champion who loves to talk with and educate customers.

• Awesome! Users that are ordering it know how to use it! – Very few escalations.

• We made it easy to adopt– Low price (free)– Automated allocation and routing, no wait!

10/12/2010

Page 20: Softlayer Technologies texasipv6taskforce

SoftLayer Technologies, Inc 20

Questions?

10/12/2010

Page 21: Softlayer Technologies texasipv6taskforce

Matt ChilekSoftware [email protected]:f0d0::


Top Related