On October 23rd, 2014, we updated our
By continuing to use LinkedIn’s SlideShare service, you agree to the revised terms, so please take a few minutes to review them.
Matt Chilek VP, Software Development SoftLayer Technologies, Inc email@example.com AS36351 2607:f0d0::
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 2 SoftLayer Technologies, Inc 10/12/2010
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 domain http://bgp.he.net/ipv6-progress-report.cgi 4 SoftLayer Technologies, Inc 10/12/2010
Implementation Problems Network hardware Provider support Allocation scheme Tracking application Operations support Customer adoption 5 SoftLayer Technologies, Inc 10/12/2010
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.
6 SoftLayer Technologies, Inc 10/12/2010
S1. Network hardware
Firmware or software upgrades?
Solution: Staggered maintenance
Limited feature sets?
Solution: Use what you have to get it done. 7 SoftLayer Technologies, Inc 10/12/2010
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 8 SoftLayer Technologies, Inc 10/12/2010
S2. Provider support 9 SoftLayer Technologies, Inc 10/12/2010 LOTS OF PEERING! + others
P3. Allocation scheme Almost no published “best” practices No best practices for our organizational complexity 10 SoftLayer Technologies, Inc 10/12/2010
S3. Allocation scheme Best practices?!! Solution: Went with our own… /40: region /48: router /64: host 11 SoftLayer Technologies, Inc 10/12/2010
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. 12 SoftLayer Technologies, Inc 10/12/2010
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 14 SoftLayer Technologies, Inc 10/12/2010
P5. Operations support 16 SoftLayer Technologies, Inc 10/12/2010
“Uh, that’s a lot of numbers and letters and stuff” – anonymous support technician
S5. Operations support 17 SoftLayer Technologies, Inc 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.
P6. Customer adoption Why should customers start adopting? Our external customer typically doesn’t understand the size of the IPv6 address space 18 SoftLayer Technologies, Inc 10/12/2010
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! 19 SoftLayer Technologies, Inc 10/12/2010