Noticed my IPv6 tunnel down and I can't ping the tunnel server any longer. Is something down?
PING 209.51.181.2 (209.51.181.2) 56(84) bytes of data.
^C
--- 209.51.181.2 ping statistics ---
30 packets transmitted, 0 received, 100% packet loss, time 29012ms
traceroute to 209.51.181.2 (209.51.181.2), 30 hops max, 40 byte packets
1 (omitted) 0.312 ms 0.247 ms 0.285 ms
2 * * *
3 (omitted) 10.684 ms 10.664 ms 10.930 ms
4 * * *
5 xe-9-1-0.edge1.Chicago2.Level3.net (4.71.248.1) 29.454 ms xe-11-2-0.edge1.Chicago2.Level3.net (4.71.248.13) 29.394 ms xe-9-1-0.edge1.Chicago2.Level3.net (4.71.248.1) 29.423 ms
6 vlan52.ebr2.Chicago2.Level3.net (4.69.138.190) 29.380 ms 27.530 ms vlan51.ebr1.Chicago2.Level3.net (4.69.138.158) 31.519 ms
7 ae-5.ebr2.Chicago1.Level3.net (4.69.140.193) 30.967 ms 26.337 ms 26.344 ms
8 ae-23-56.car3.Chicago1.Level3.net (4.68.101.167) 26.199 ms ae-13-55.car3.Chicago1.Level3.net (4.68.101.135) 31.241 ms ae-23-56.car3.Chicago1.Level3.net (4.68.101.167) 30.963 ms
9 glbx-level3-te.Chicago1.level3.net (4.68.110.194) 34.965 ms 35.062 ms 36.952 ms
10 HURRICANE-ELECTRIC-LLC-Ashburn.TenGigabitEthernet4-4.ar3.DCA3.gblx.net (64.214.121.170) 79.990 ms 79.614 ms 78.776 ms
11 10gigabitethernet1-2.core1.nyc4.he.net (72.52.92.85) 62.141 ms 61.978 ms 62.058 ms
12 10gigabitethernet1-2.core1.chi1.he.net (72.52.92.102) 62.173 ms 72.903 ms 72.850 ms
13 * * *
14 * * *
15 * * *
Please Retest.
Everything's fine now.
What happened? Changes, Upgrades, Etc?
"Etc"
Down again?
PING 209.51.181.2 (209.51.181.2) 56(84) bytes of data.
^C
--- 209.51.181.2 ping statistics ---
14 packets transmitted, 0 received, 100% packet loss, time 13011ms
traceroute to 209.51.181.2 (209.51.181.2)
...
12 atl-bb1-link.telia.net (213.248.80.145) 78.250 ms 78.789 ms 74.091 ms
13 hurricane-ic-129712-atl-bb1.c.telia.net (213.248.79.70) 82.285 ms 67.418 ms 76.510 ms
14 10gigabitethernet6-4.core1.ash1.he.net (72.52.92.157) 85.171 ms 85.301 ms 91.703 ms
15 10gigabitethernet1-2.core1.nyc4.he.net (72.52.92.85) 79.440 ms 74.508 ms 72.991 ms
16 10gigabitethernet1-2.core1.chi1.he.net (72.52.92.102) 81.310 ms 76.446 ms 82.993 ms
17 * * *
18 * * *
19 * * *
Back up.
Down again?
pork@main ~ $ traceroute 209.51.181.2
traceroute to 209.51.181.2 (209.51.181.2), 30 hops max, 40 byte packets
1 216.165.144.1 (216.165.144.1) 12.339 ms 13.198 ms 14.701 ms
2 mdtnwiallcr52-gi2-7.network.tds.net (64.50.226.77) 16.604 ms 17.552 ms 18.268 ms
3 10gigabitethernet4-1.core1.chi1.he.net (206.223.119.37) 24.902 ms 26.870 ms 27.873 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
...
C:\Documents and Settings\DSLUser>tracert6 2001:470:1f10:4d1::1
Tracing route to gawul00-1.tunnel.tserv9.chi1.ipv6.he.net [2001:470:1f10:4d1::1
from 2002:4515:63b6::4515:63b6 over a maximum of 30 hops:
1 * * * Request timed out.
2 15 ms 14 ms 14 ms r-csscplat-b380-3-core-vlan-1397.net.wisc.edu [2607:f388:0:20e::1]
3 14 ms 14 ms 14 ms r-cssc-b280c-9-core-vlan-2098.net.wisc.edu [2607:f388:0:20a::1]
4 14 ms 14 ms 14 ms r-peer-xe-2-0-0-1791.net.wisc.edu [2607:f388:0:201::2]
5 14 ms 26 ms 13 ms r-uwmadison-isp-xe-0-1-0-946.ipv6.wiscnet.net [2001:4e0:0:3003::1]
6 32 ms 32 ms 32 ms r-equinix-isp-xe-4-0-0-3997.ipv6.wiscnet.net [2001:4e0:0:202::2]
7 47 ms 47 ms 47 ms v219.core1.chi1.he.net [2001:470:0:f2::1]
8 88 ms 87 ms 87 ms 10gigabitethernet3-2.core1.sjc2.he.net [2001:470:0:3c::1]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
...
New hardware getting deployed tomorrow. Should resolve this, meantime waiting for remote facility to kick it.
Hardware getting swapped today, intended downtime.
Hardware/software upgrade completed.