|
Ticket ID: SIXXS #9376622 Ticket Status: Remote Problem PoP: usqas01 - OCCAID Inc. (Ashburn, Virginia)
uslax02 can't reach usqas01 and vice versa
![[us]](/s/countries/us.gif) Shadow Hawkins on Tuesday, 14 May 2013 03:24:27
Hi,
I am having an issue where two of my tunnels cannot speak to each other. From the traceroutes I've done, the issue seems to be somewhere on a trans-continental link between LA and DC.
My NIC handle: MHC1-SIXXS
The tunnel IDs: T12632 (usqas01) and T107194 (uslax02)
I can reach both PoPs successfully, as well as reach Google from each PoP; they simply cannot see each other.
I am also aware that SixXS probably cannot resolve this problem directly, but has a much better chance of contacting the right people to report the problem.
Thanks!
From uslax02 to usqas01:
error@yaungol ~ $ traceroute6 2001:4830:1600:80bf::2
traceroute to 2001:4830:1600:80bf::2 (2001:4830:1600:80bf::2), 30 hops max, 80 byte packets
1 gw-37.lax-02.us.sixxs.net (2607:f878:fe00:24::1) 1.217 ms 1.454 ms 1.445 ms
2 uslax02.sixxs.net (2607:f878:3:400::2) 1.440 ms 1.430 ms 1.423 ms
3 2607:f878:3:a::1 (2607:f878:3:a::1) 2.513 ms 2.522 ms 3.108 ms
4 2607:f878::1d0 (2607:f878::1d0) 3.328 ms 3.328 ms 3.319 ms
5 2400:8800:7f02::1 (2400:8800:7f02::1) 58.719 ms 55.300 ms 59.927 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 *^C
From usqas01 to uslax02:
error@underground ~ $ traceroute6 yaungol
traceroute to yaungol (2607:f878:fe00:24::2), 30 hops max, 80 byte packets
1 2001:4830:1600:80bf::1 (2001:4830:1600:80bf::1) 0.474 ms 0.521 ms 0.597 ms
2 gw-192.qas-01.us.sixxs.net (2001:4830:1600:bf::1) 47.673 ms 48.137 ms 51.556 ms
3 sixxs-asbnva-gw.customer.occaid.net (2001:4830:e6:7::2) 52.164 ms 52.331 ms 52.673 ms
4 sixxs-gw.hotnic.us.occaid.net (2001:4830:e6:7::1) 53.422 ms 53.803 ms 53.956 ms
5 10gigabitethernet2-2.core1.ash1.he.net (2001:504:0:2::6939:1) 63.321 ms 63.052 ms 62.760 ms
6 2400:8800:5f01:14::1 (2400:8800:5f01:14::1) 62.450 ms 55.801 ms 55.139 ms
7 * * 2400:8800:5f04:1::2 (2400:8800:5f04:1::2) 85.915 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * *^C
uslax02 can't reach usqas01 and vice versa
Shadow Hawkins on Tuesday, 14 May 2013 14:09:48
This problem seems to be larger than just between those two POPs, I am on usmia01
and am having similar issues as are demonstrated by these traceroutes:
king:~# traceroute6 ftp.debian.org
traceroute to klecker-ftp.debian.org (2001:610:1908:b000::148:12) from 2607:f878:ff00:1e::2, port 33434, from port 52140, 30 hops max, 60 bytes packets
1 gw-31.mia-01.us.sixxs.net (2607:f878:ff00:1e::1) 54.467 ms 53.421 ms 54.430 ms
2 2607:f878:4:80::2 (2607:f878:4:80::2) 55.198 ms 66.145 ms 54.470 ms
3 2607:f878:4:2d::1 (2607:f878:4:2d::1) 66.215 ms 55.200 ms 54.394 ms
4 2607:f878::180 (2607:f878::180) 56.985 ms 55.211 ms 56.060 ms
5 2400:8800:5f04:1::1 (2400:8800:5f04:1::1) 56.167 ms 56.134 ms 54.673 ms
6 2400:8800:5f01:14::2 (2400:8800:5f01:14::2) 84.627 ms 86.413 ms 88.347 ms
7 100gigabitethernet7-1.core1.nyc4.he.net (2001:470:0:299::2) 89.019 ms 91.882 ms 94.355 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
king:~# traceroute6 sixxs.net
traceroute to gatey.sixxs.net (2620:0:6b0:a:250:56ff:fe99:78f7) from 2607:f878:ff00:1e::2, port 33434, from port 52034, 30 hops max, 60 bytes packets
1 gw-31.mia-01.us.sixxs.net (2607:f878:ff00:1e::1) 53.331 ms 53.431 ms 61.768 ms
2 2607:f878:4:80::2 (2607:f878:4:80::2) 54.343 ms 61.875 ms 55.070 ms
3 2607:f878:4:2d::1 (2607:f878:4:2d::1) 61.871 ms 56.683 ms 70.167 ms
4 2607:f878::180 (2607:f878::180) 56.724 ms 104.980 ms 54.307 ms
5 2400:8800:5f04:1::1 (2400:8800:5f04:1::1) 71.150 ms 55.200 ms 56.321 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
king:~# traceroute6 security.debian.org
traceroute to saens.debian.org (2607:ea00:101:3c0b:207:e9ff:fe00:e595) from 2607:f878:ff00:1e::2, port 33434, from port 52013, 30 hops max, 60 bytes packets
1 gw-31.mia-01.us.sixxs.net (2607:f878:ff00:1e::1) 54.579 ms 63.531 ms 56.727 ms
2 2607:f878:4:80::2 (2607:f878:4:80::2) 63.600 ms 56.803 ms 53.825 ms
3 2607:f878:4:2d::1 (2607:f878:4:2d::1) 57.374 ms 56.458 ms 54.601 ms
4 2607:f878::180 (2607:f878::180) 56.492 ms 55.191 ms 54.747 ms
5 2400:8800:5f04:1::1 (2400:8800:5f04:1::1) 67.354 ms 55.759 ms 55.586 ms
6 eq-exchange.tr01-asbnva01.transitrail.net (2001:504:0:2:0:1:1164:1) 102.137 ms 102.184 ms 98.721 ms
7 * * *
8 * * *
9 * * *
uslax02 can't reach usqas01 and vice versa
Shadow Hawkins on Wednesday, 15 May 2013 05:31:38
As of now I have connectivity restored in both directions.
|
Posting is only allowed when you are