Archive for December, 2011

At Gartner Datacenter Conference this week…

I’ll be at the Gartner Datacenter conference in Las Vegas all this week. In my new role at work I’m no longer directly responsible for our US datacenters, but I will be helping to shape our world wide datacenter and networking strategies (among others). If the conference is anything like last year’s there will be LOT of “cloud” in addition to the core topic. It will be interesting to see updates on the major initiatives that large scale operations like Bank of America, eBay and others talked about last year.

The usual Twitter hashtag for the conference is #gartnerdc. If you’re interested in datacenters, “devops”, “green IT”, “orchestration” or “cloud”, I recommend that you follow the tag.

The IPv6 series will continue as usual next week with posts on Tuesday and Thursday.

Leave a comment

IPv6 – my first ping! (ping6 and traceroute6)

The next step after getting my IPv6 tunnel was to test connectivity through the tunnel. IPv6 still isn’t completely integrated into most Linux network tools, so there are IPv6 versions. For example, ping6 and traceroute6.

Since I still hadn’t selected a new home router, the fastest and easiest way to do the initial pings was to bring up a tunnel from my home Linux server, running Ubuntu 9 (more on that later).

I’ve been using Migrating to IPv6 as one of my primary references for this project, although I’ve probably read at least four or five other IPv6 books.

Fortunately for me, Hurricane provides sample configurations for your end of the tunnel.  You select your OS from a drop down list, and they give you the exact command lines to execute, with the proper IP addresses filled in.

In my case, the commands are:

# ifconfig sit0 up
# ifconfig sit0 inet6 tunnel ::$TUNNELEND
# ifconfig sit1 up
# ifconfig sit1 inet6 add $MYIPV6
# route -A inet6 add ::/0 dev sit1

These  commands create the two tunnel endpoints needed to encapsulate IPv6 in the IPv4 tunnel. The “sit0” and “site1” interfaces are part of the Simple Internet Transition mechanism defined in RFC 2893. $TUNNELEND is the IPv4 address of the tunnel endpoint at the tunnel broker. $MYIPV6 is the IPv6 address that they’ve assigned to my routed /64 network.

At this point, my local Linux host is “on” the public IPv6 network. Using ping6 and traceroute6 I can verify connectivity by poking at some well-known IPv6 sites.

Since I’ve done nothing with DNS (yet), I’ll have to use IPv6 addresses. The site is a well-known IPv6 site. Or I could use (not exactly, more on that later).

$ dig +short AAAA
$ dig +short aaaa

$ ping6 -c 3 2001:200:dff:fff1:216:3eff:feb1:44d7       #
PING 2001:200:dff:fff1:216:3eff:feb1:44d7(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes
64 bytes from 2001:200:dff:fff1:216:3eff:feb1:44d7: icmp_seq=1 ttl=55 time=175 ms
64 bytes from 2001:200:dff:fff1:216:3eff:feb1:44d7: icmp_seq=2 ttl=55 time=176 ms
64 bytes from 2001:200:dff:fff1:216:3eff:feb1:44d7: icmp_seq=3 ttl=55 time=165 ms

--- 2001:200:dff:fff1:216:3eff:feb1:44d7 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 165.834/172.634/176.718/4.864 ms

$ traceroute6 2001:200:dff:fff1:216:3eff:feb1:44d7      #
traceroute to 2001:200:dff:fff1:216:3eff:feb1:44d7 (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets
 1  2001:470:67:84:ba8d:12ff:fe57:9f38 (2001:470:67:84:ba8d:12ff:fe57:9f38)  0.378 ms  0.400 ms  0.510 ms
 2  2001:470:66:84::1 (2001:470:66:84::1)  30.653 ms  31.679 ms  33.852 ms
 3 (2001:470:0:206::1)  61.420 ms  61.954 ms  62.452 ms
 4 (2001:470:0:2f::2)  40.381 ms  42.268 ms  43.335 ms
 5 (2001:504:0:1::2914:1)  47.026 ms  48.668 ms  50.024 ms
 6 (2001:218:0:2000::aa)  169.124 ms  151.706 ms (2001:218:0:2000::8a)  130.998 ms
 7 (2001:218:0:2000::1b6)  151.985 ms (2001:218:0:2000::1ca)  151.376 ms (2001:218:0:2000::1b6)  198.101 ms
 8 (2001:218:0:2000::1de)  158.495 ms (2001:218:0:6000::10e)  143.385 ms (2001:218:0:2000::1de)  252.684 ms
 9 (2001:218:2000:5000::82)  162.951 ms (2001:218:0:6000::10e)  159.136 ms (2001:218:2000:5000::82)  166.994 ms
10 (2001:200:0:10::141)  168.056 ms (2001:218:2000:5000::82)  180.955 ms  173.537 ms
11 (2001:200:0:11::66)  165.998 ms (2001:200:0:10::141)  153.527 ms (2001:200:0:11::66)  149.147 ms
12 (2001:200:0:1c0a:218:8bff:fe43:d1d0)  147.916 ms (2001:200:0:11::66)  163.483 ms  168.776 ms
13 (2001:200:0:1c0a:218:8bff:fe43:d1d0)  169.996 ms 2001:200:dff:fff1:216:3eff:feb1:44d7 (2001:200:dff:fff1:216:3eff:feb1:44d7)  165.067 ms  166.418 ms

OK, I’ve verified basic IPv6 connectivity, now I just need a “real” router. Of course, I could continue to use my Linux host as the router, but that doesn’t meet my requirements. I need a solution that someone can deploy without having to add an additional computer to their network.

Leave a comment

%d bloggers like this: