Hi All,
It looks like the Amsterdam PoP is down. This is frustrating since we use this PoP for our school's IPv6 connectivity :( .
Does anybody know what's happening?
As fas as I can tell, connection was lost between 09:59 and 10:59 CET (I do a connection test every hour) http://tunnelbroker.net/status.php shows the PoP is down, so we'll just have to wait.
I guess if you're in a rush and all your clients get their IPv6-address dynamically, you could setup a tunnel to tserv5.lon1, tserv17.lon1 or tserv18.fra1. Those are the PoP's with the lowest pings from where I'm sitting.
Quote from: ohosipsix on March 11, 2010, 04:04:33 AM
As fas as I can tell, connection was lost between 09:59 and 10:59 CET (I do a connection test every hour) http://tunnelbroker.net/status.php shows the PoP is down, so I we'll just have to wait.
I guess if you're in a rush and all your clients get their IPv6-address dynamically, you could setup a tunnel to tserv5.lon1, tserv17.lon1 or tserv18.fra1. Those are the PoP's with the lowest pings from where I'm sitting.
Okay, I just requested a new tunnel.
Everything fine, but we've got quite a lot of IPv6-enabled servers with static addresses which are in an wrong subnet.
Does anybody know how I am able to reach those IPv6-enabled servers again now I've got v6-connectivity using a new PoP?
If they're local on your LAN, you have a couple of options.
A) use IPv4
B) Configure your router with static routes that routes that traffic to the correct location.
I sent a ticket into NOC about this. Is there any ETA? It would be good if one could simply switch the endpoint without losing tunnels. Thanks.
Seems a tech in NIKHEF doing an unrelated workorder, has de-cabled/knocked loose? our tunnel-server's ethernet patch. I'm waiting to hear back from them regarding this. No ETA.
Quote from: cholzhauer on March 11, 2010, 06:14:05 AM
If they're local on your LAN, you have a couple of options.
A) use IPv4
B) Configure your router with static routes that routes that traffic to the correct location.
A: Ironically we are just in the proces of migrating to IPv6 :) Clients are not configured yet to use the v6 server addresses though, so the problem isn't really that big. We're still waiting to get native IPv6.
B: Sounds interesting. I'll look into it! :D
Quote from: broquea on March 11, 2010, 07:45:10 AM
Seems a tech in NIKHEF doing an unrelated workorder, has de-cabled/knocked loose? our tunnel-server's ethernet patch. I'm waiting to hear back from them regarding this. No ETA.
So the downtime isn't really related to technical issues (software/hardware) as I first thought. Heck, this should be easy to fix :P . Hope they'll get to it soon at NIKHEF.
If you do go with B, you might want to put a route in there that prevents routing that range to the Internet, because technically, that range is no longer yours.
Hi
Any updates on this? It still seems to be down. Not complaining, just wondering if there's an ETA ;)
Thanks
Unbelievable. Frankfurt seems down too, right now :'( .
Let's jump to the next one.
Nevermind, my tunnel to Frankfurt is still up.
Don't know why the status page mentions it is down.
Quote from: hisken on March 11, 2010, 09:26:56 AM
Unbelievable. Frankfurt seems down too, right now :'( .
Let's jump to the next one.
Nevermind, my tunnel to Frankfurt is still up.
Don't know why the status page mentions it is down.
You have a BGP tunnel? Because those are the only tunnels on tserv18. You probably have one on tserv6, which are for regular tunnels. Also there was a traffic shift in Frankfurt that we've migrated away, so that down is actually a false positive that will be cleared in the next few polls.
Quote from: broquea on March 11, 2010, 09:38:42 AM
Quote from: hisken on March 11, 2010, 09:26:56 AM
Unbelievable. Frankfurt seems down too, right now :'( .
Let's jump to the next one.
Nevermind, my tunnel to Frankfurt is still up.
Don't know why the status page mentions it is down.
You have a BGP tunnel? Because those are the only tunnels on tserv18. You probably have one on tserv6, which are for regular tunnels. Also there was a traffic shift in Frankfurt that we've migrated away, so that down is actually a false positive that will be cleared in the next few polls.
Ah, missed that one, it's a regular tunnel indeed. Didn't see there was a second server in Frankfurt.
Hi,
Is there already an ETA for this issue (just wondering), as tserv11 currently has a downtime of about 9 hours.
Temporarily migrating AMS tunnels to LON, just to get them back up. Still waiting on AMS remote facility to complete our request, and will migrate the tunnels back to AMS once we've verified everything is operational.
FYI, this means no new tunnels get created on AMS until everything is migrated back.
Quote from: broquea on March 11, 2010, 04:20:57 PM
Temporarily migrating AMS tunnels to LON, just to get them back up. Still waiting on AMS remote facility to complete our request, and will migrate the tunnels back to AMS once we've verified everything is operational.
FYI, this means no new tunnels get created on AMS until everything is migrated back.
Thank you, everything is running fine again now! We really appreciate all your work!
Remote facility managed to reconnect cable, I'm making sure everything looks stable before migrating tunnels back to AMS.
AMS tunnels back on AMS tserv.
Wow. Nearly 24 hours to plug a cable back in? I hope that colo is giving HE a month of free service or something. ;)
I wonder if Sprint runs that colo...