|
Ticket ID: SIXXS #1079511 Ticket Status: Resolved PoP: deham01 - Easynet (Hamburg)
Problem with tunnels terminated on deham01
![[de]](/s/countries/de.gif) Shadow Hawkins  on Wednesday, 06 May 2009 12:51:57
Following tunnels are offline:
T12416 (AICCU heartbeat)
T9161 (AICCU heartbeat)
T3900 (AICCU heartbeat))
T18323 (AICCU AYIYA)
aiccu test:
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.224.0.188)
### 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 212.224.0.188 (212.224.0.188) 56(84) bytes of data.
--- 212.224.0.188 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2012ms
As a logic consequence that the ipv4 is also not responding to ping-questions, i'm not able to ping any of my ipv6 endpoints on deham01.
My nic-handle is TK2325-RIPE. If you need any further informations, please message me.
Problem with tunnels terminated on deham01
Shadow Hawkins on Wednesday, 06 May 2009 12:53:05
Ah, while i wrote this ticket, the pop status went to down. Seems to be recognized by the system. If you need assistence in debugging that issue, feel free to message me.
Problem with tunnels terminated on deham01
Shadow Hawkins on Wednesday, 06 May 2009 12:57:49
Traceroute to the ipv4 of deham01:
dracula:~# traceroute 212.224.0.188
traceroute to 212.224.0.188 (212.224.0.188), 30 hops max, 40 byte packets
1 em0.cygni.hosting-server.cc (194.126.239.65) 0.234 ms 0.203 ms 0.171 ms
2 ve666.bbr1.dus1.de.inetbone.net (213.203.213.1) 10.594 ms 10.689 ms 10.667 ms
3 tge-2-1.bbr1.fra3.de.inetbone.net (213.203.213.77) 4.140 ms 4.152 ms 4.242 ms
4 te0-0-0-5.er10.ixfra.de.easynet.net (80.81.192.14) 5.345 ms 5.562 ms 5.317 ms
5 te0-0-0.gr10.isham.de.easynet.net (87.86.77.65) 14.430 ms 14.408 ms 14.003 ms
6 ge1-11.br2.isham.de.easynet.net (87.86.69.161) 14.469 ms 14.451 ms 14.286 ms
7 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 14.636 ms 14.473 ms 14.562 ms
8 * * *
After Hop 8 the trace ends. The trace came from 194.126.239.66.
Problem with tunnels terminated on deham01
Shadow Hawkins on Wednesday, 06 May 2009 13:16:15
deham01 is back and works again like a charm. Thanks!
Problem with tunnels terminated on deham01
The 'down' notification is only set after 5 minutes or more of down time, if at every miss of a packet it would be marked down directly things would be flapping a lot. There really is no intelligence in the forum like that.
State change: resolved
The state of this ticket has been changed to resolved
Problem with tunnels terminated on deham01
There can be many reasons why IPv4 would not respond. For instance if there would not be a route from you to that IP or when it gets filtered somewhere. As such, always include at least traceroutes.
|
![[ch]](/s/countries/ch.gif)
Posting is only allowed when you are