SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1283961
Ticket Status: Resolved

PoP: uschi02 - Your.Org, Inc. (Chicago, Illinois)

uschi02 failover system misbehaving
[gb] Shadow Hawkins on Friday, 04 December 2009 09:48:02
[Admin edit, changed subject, old subject: uschi02 still seems to be broken] Hi, uschi02 just got marked as back up, but there appears to be no route past the pop's end of the tunnel: $ ping6 ipv6.google.com PING ipv6.google.com(pv-in-x93.1e100.net) 56 data bytes From gw-243.chi-02.us.sixxs.net icmp_seq=1 Destination unreachable: No route I get the same with both of the tunnels I have to uschi02. Coming the other way, the route dies inside he.net: $ mtr -nrc 10 -6 2001:4978:f:f2::2 HOST: specialbrew.localnet Loss% Snt Last Avg Best Wrst StDev 1. 2001:7b8:2ff:9c::1 0.0% 10 43.2 44.1 43.2 45.0 0.6 2. 2001:7b8:3:4f::2 0.0% 10 44.3 43.9 43.4 44.3 0.3 3. 2001:7f8:1::a500:6939:1 0.0% 10 45.2 45.9 44.7 48.8 1.1 4. 2001:470:0:3f::1 0.0% 10 60.2 57.6 52.7 67.5 5.1 5. 2001:470:0:3e::1 0.0% 10 121.1 122.0 120.6 127.7 2.0 6. 2001:470:0:4e::1 0.0% 10 152.1 149.1 142.8 153.8 4.0 7. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 Cheers, Andy
State change: confirmed Locked
[ch] Jeroen Massar SixXS Staff on Friday, 04 December 2009 09:47:34
Message is Locked
The state of this ticket has been changed to confirmed
uschi02 failover system misbehaving
[ch] Jeroen Massar SixXS Staff on Friday, 04 December 2009 09:48:37
Actually, the problem is that the failover system is misbehaving a bit, it is thus switching between the primary and backup system all the time. We are busy resolving this.
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Friday, 04 December 2009 19:17:11
Message is Locked
The state of this ticket has been changed to resolved

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker