Ticket ID: SIXXS #8509226 Ticket Status: Works for Me PoP: decgn01 - NetCologne Gesellschaft fur Telekommunikation mbH (Cologne)
netcologne Pop down?
Carmen Sandiego on Sunday, 30 December 2012 00:17:33
Hello,
i have two Tunnels (T110110 and T10619). The Tunnel-Pop fr T110110 is Netcologne and this tunnel isn't working anymore. When i switch to T10619 on my local machine (Easynet) everything works fine.
Aiccu test:
[root@afrilymp ~]# aiccu test
Tunnel Information for T110110:
POP Id : decgn01
IPv6 Local : 2001:4dd0:ff00:108d::2/64
IPv6 Remote : 2001:4dd0:ff00:108d::1/64
Tunnel Type : 6in4-heartbeat
Adminstate : enabled
Userstate : enabled
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (10.1.0.2)
### This should return so called 'echo replies'
### If it doesn't then check your firewall settings
### Your local endpoint should always be pingable
### It could also indicate problems with your IPv4 stack
PING 10.1.0.2 (10.1.0.2) 56(84) bytes of data.
64 bytes from 10.1.0.2: icmp_seq=1 ttl=64 time=0.038 ms
64 bytes from 10.1.0.2: icmp_seq=2 ttl=64 time=0.033 ms
64 bytes from 10.1.0.2: icmp_seq=3 ttl=64 time=0.030 ms
--- 10.1.0.2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.030/0.033/0.038/0.007 ms
######
Did this work? [Y/n] y
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (78.35.24.124)
### These pings should reach the PoP and come back to you
### In case there are problems along the route between your
### host and the PoP this could not return replies
### Check your firewall settings if problems occur
PING 78.35.24.124 (78.35.24.124) 56(84) bytes of data.
64 bytes from 78.35.24.124: icmp_seq=1 ttl=59 time=12.8 ms
64 bytes from 78.35.24.124: icmp_seq=2 ttl=59 time=12.7 ms
64 bytes from 78.35.24.124: icmp_seq=3 ttl=59 time=12.5 ms
--- 78.35.24.124 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 12.561/12.697/12.803/0.101 ms
######
Did this work? [Y/n] y
####### [3/8] Traceroute to the PoP (78.35.24.124) over IPv4
### This traceroute should reach the PoP
### In case this traceroute fails then you have no connectivity
### to the PoP and this is most probably the problem
traceroute to 78.35.24.124 (78.35.24.124), 30 hops max, 60 byte packets
1 netconnect.box (10.1.0.1) 0.406 ms 0.671 ms 0.820 ms
2 e120-scsto1.netcologne.de (195.14.226.59) 13.696 ms 13.796 ms 14.771 ms
3 81.173.197.73 (81.173.197.73) 14.317 ms 14.792 ms 15.063 ms
4 core-sto2-vl427.netcologne.de (78.35.33.221) 15.185 ms 15.370 ms 15.514 ms
5 core-eup2-t32.netcologne.de (87.79.17.29) 16.416 ms 16.424 ms 16.918 ms
6 sixxs-pop1.netcologne.net (78.35.24.124) 16.638 ms 12.564 ms 13.054 ms
######
Did this work? [Y/n] y
###### [4/8] Checking if we can ping IPv6 localhost (::1)
### This confirms if your IPv6 is working
### If ::1 doesn't reply then something is wrong with your IPv6 stack
PING ::1(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.033 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.037 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.043 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.033/0.037/0.043/0.008 ms
######
Did this work? [Y/n] y
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:4dd0:ff00:108d::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:4dd0:ff00:108d::2(2001:4dd0:ff00:108d::2) 56 data bytes
64 bytes from 2001:4dd0:ff00:108d::2: icmp_seq=1 ttl=64 time=0.050 ms
64 bytes from 2001:4dd0:ff00:108d::2: icmp_seq=2 ttl=64 time=0.037 ms
64 bytes from 2001:4dd0:ff00:108d::2: icmp_seq=3 ttl=64 time=0.045 ms
--- 2001:4dd0:ff00:108d::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.037/0.044/0.050/0.005 ms
######
Did this work? [Y/n] y
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4dd0:ff00:108d::1)
### This confirms the reachability of the other side of the tunnel
### If it doesn't reply then check your interface and routing tables
### Don't forget to check your firewall of course
### If the previous test was succesful then this could be both
### a firewalling and a routing/interface problem
PING 2001:4dd0:ff00:108d::1(2001:4dd0:ff00:108d::1) 56 data bytes
--- 2001:4dd0:ff00:108d::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2000ms
######
Did this work? [Y/n] n
In wireshark i can see the outgoing ICMP-Packages on the tunnel interface when pinging 2001:4dd0:ff00:108d::1 but i get no response, so the pop seems to be down.
Can you please check this?
Thank you
Felix Becker
decgn01 Pop down
Shadow Hawkins on Sunday, 30 December 2012 00:32:39
I got the same issue with the decgn01 PoP.
My tunnel ID is T110222.
When I run 'aiccu test' it also gets stuck at [6/8].
netcologne Pop down?
Carmen Sandiego on Sunday, 30 December 2012 00:42:57
works again for me (about 30 minutes after the failure). No more problems here. Sorry for the noise.
State change: worksforme
Jeroen Massar on Sunday, 30 December 2012 06:13:43
The state of this ticket has been changed to worksforme
Posting is only allowed when you are logged in. |