Quick summary of the $JOB as of 2/12/2010
I have had some major, incredibly important deadline pushed up by 5 days. We were supposed to disconnect the old datacenter on 2/20, and yesterday I found out we're turning the power off to the old facility on 2/15. Joy.
I was at the office from 1930 last night until 0400 this morning doing the first phase of a circuit migration (using AT&T's "Opt-E-MAN" WAN/Ethernet service). What should have been simple went really sideways and we encountered some significant problems. The irony of it all is that it turns out I had completely overthought the situation and made a simple, elegant solution vastly more complex than it needed to be. When I returned to the simple solution everything started working. Thankfully I realized this at around 0240 and reeled everything back in, successfully completing that stage of the trasition. Hooray for smoke breaks and my coworker NF who let me bounce thoughts off of him (and watched me draw with a whiteboard marker on a non-whiteboard surface. I'll be staring at that for the next 15 years).
Right after I fixed things up on the Opt-E-MAN I got some news from the good folks over at Hurricane Electric's IPv6 tunneling service that made me happy: the tunnel I had requested to $EMPLOYER's router should be fixed (it hadn't been working before). When I tested things out, it was! Not only did I have IPv6 connectivity on the most rudimentary level, my BGP session for IPv6 was also working! After I got home at around 0400, I couldn't sleep (surprise surprise, given the events of the evening) so I settled into the office and did some tinkering to see if I couldn't get $EMPLOYER's IPv6 allocation to be announced out to the global Internet (what little of it that speaks IPv6, anyway) via the Hurricane Electric tunnel. It took a bit of fiddling but eventually I was able to successfully announce 2620:0:1400::/42 out of my Juniper M10i router into the IPv6 Internet (all hail the MultiServices PIC).
So, over a year after I got $EMPLOYER a provider-independent IPv6 allocation, it is finally being announced into the Internet (from ASN 22734). The next step? I probably need to get the traffic through the firewall....
I was at the office from 1930 last night until 0400 this morning doing the first phase of a circuit migration (using AT&T's "Opt-E-MAN" WAN/Ethernet service). What should have been simple went really sideways and we encountered some significant problems. The irony of it all is that it turns out I had completely overthought the situation and made a simple, elegant solution vastly more complex than it needed to be. When I returned to the simple solution everything started working. Thankfully I realized this at around 0240 and reeled everything back in, successfully completing that stage of the trasition. Hooray for smoke breaks and my coworker NF who let me bounce thoughts off of him (and watched me draw with a whiteboard marker on a non-whiteboard surface. I'll be staring at that for the next 15 years).
Right after I fixed things up on the Opt-E-MAN I got some news from the good folks over at Hurricane Electric's IPv6 tunneling service that made me happy: the tunnel I had requested to $EMPLOYER's router should be fixed (it hadn't been working before). When I tested things out, it was! Not only did I have IPv6 connectivity on the most rudimentary level, my BGP session for IPv6 was also working! After I got home at around 0400, I couldn't sleep (surprise surprise, given the events of the evening) so I settled into the office and did some tinkering to see if I couldn't get $EMPLOYER's IPv6 allocation to be announced out to the global Internet (what little of it that speaks IPv6, anyway) via the Hurricane Electric tunnel. It took a bit of fiddling but eventually I was able to successfully announce 2620:0:1400::/42 out of my Juniper M10i router into the IPv6 Internet (all hail the MultiServices PIC).
So, over a year after I got $EMPLOYER a provider-independent IPv6 allocation, it is finally being announced into the Internet (from ASN 22734). The next step? I probably need to get the traffic through the firewall....