Re: Frustrating loss of connectivity...

2003-10-13 Thread alex

 I am located in Madison, WI, and I have my mail/server machine geek.net
 co-located in Minneapolis on a business-class DSL line (1.5m/384k).  For
 the past couple of months, I'll lose connectivity for about 5 minutes
 several times a day.
snip
 
 Any thoughts or recommendations here?

RFO: Colocation with people who have business class DSL connectivity.

-alex



Re: Frustrating loss of connectivity...

2003-10-13 Thread Haesu

Hi, have you tried the return path traceroute... Like, run traceroute _From_ the 
server behind dsl and back to you? Having traceroutes done either way may be helpful 
often times b/c sometimes problems do rise on asymetric routing situation where 
provider is doing bgp with x no. of providers.

Please feel free to reply to me off list. I understand your frustration to get this 
out to bunch of engineers, but this may be clasifed as off-topic..

Thanks,
-hc

-- 
Haesu C.
TowardEX Technologies, Inc.
Consulting, colocation, web hosting, network design and implementation
http://www.towardex.com | [EMAIL PROTECTED]
Cell: (978)394-2867 | Office: (978)263-3399 Ext. 170
Fax: (978)263-0033  | POC: HAESU-ARIN

On Mon, Oct 13, 2003 at 10:33:26AM -0500, Robert A. Hayden wrote:
 
 Hey all,
 
 I apologize for posting this here, especially for what is essentially an
 end-user broadband issue, but I'm looking at what appears to be a link a
 few hops upstream from me that has been flapping frequently and I can't
 get our provider to look into it.
 
 I am located in Madison, WI, and I have my mail/server machine geek.net
 co-located in Minneapolis on a business-class DSL line (1.5m/384k).  For
 the past couple of months, I'll lose connectivity for about 5 minutes
 several times a day.
 
 We attempted to open a case with the DSL provider (covad), but they were
 only interested in addressing last-mile issues and we got nowhere.  Same
 applied when addressing it from my broadband end, since the disconnect is
 3 providers upstream.
 
 In any case, any thoughts on where I should go with this?  I could try 
 Level3, but I suspect they'll blow me off since I'm not a direct customer.  
 It's getting quite frustrating as I'm trying to move a few hundred mb back 
 and forth over the VPN and with that one link flapping it's become almost 
 impossible.
 
 Traceroute examples included below.  I left real IPs here since they are 
 all easily determined anyways:
 
 --
 
 TRACE #1:  From my home connection to Geek.NET when it's BROKEN, note 
 where it breaks.
 
 C:\tracert 66.166.71.243
 
 Tracing route to geek.net [66.166.71.243]
 over a maximum of 30 hops:
 
   124 ms10 ms29 ms  10.44.64.1
   211 ms10 ms11 ms  172.18.98.98
   319 ms22 ms43 ms  172.18.97.58
   416 ms14 ms15 ms  12.125.143.113
   558 ms34 ms47 ms  gbr2-a90s19.cgcil.ip.att.net [12.123.5.78]
   616 ms17 ms16 ms  tbr1-p013602.cgcil.ip.att.net [12.122.11.37]
   731 ms28 ms14 ms  ggr2-p310.cgcil.ip.att.net [12.123.6.65]
   816 ms   105 ms16 ms  so-1-1-0.edge1.Chicago1.Level3.net [209.0.227.77]
   921 ms21 ms33 ms  so-2-1-0.bbr2.Chicago1.level3.net [209.244.8.13]
  1032 ms19 ms14 ms  pos9-0.core1.Chicago1.level3.net [209.247.10.170]
  1120 ms31 ms48 ms  gige6-2.ipcolo2.Chicago1.Level3.net [209.244.8.30]
  1264 ms29 ms36 ms  unknown.Level3.net [209.247.226.26]
  13 *** Request timed out.
  14 *** Request timed out.
  ..
  30 *** Request timed out.
 
 Trace complete.
 
 --
 
 TRACE #2:  Same trace, but this time when it's working.
 
 C:\tracert 66.166.71.243
 
 Tracing route to geek.net [66.166.71.243]
 over a maximum of 30 hops:
 
   121 ms16 ms15 ms  10.44.64.1
   210 ms22 ms11 ms  172.18.98.98
   310 ms15 ms11 ms  172.18.97.58
   413 ms37 ms14 ms  12.125.143.113
   515 ms18 ms18 ms  gbr2-a90s19.cgcil.ip.att.net [12.123.5.78]
   626 ms15 ms19 ms  tbr1-p013602.cgcil.ip.att.net [12.122.11.37]
   736 ms39 ms14 ms  ggr2-p310.cgcil.ip.att.net [12.123.6.65]
   834 ms14 ms37 ms  so-1-1-0.edge1.Chicago1.Level3.net [209.0.227.77]
   917 ms14 ms14 ms  so-2-1-0.bbr2.Chicago1.level3.net [209.244.8.13]
  1017 ms13 ms14 ms  pos9-0.core1.Chicago1.level3.net [209.247.10.170]
  1118 ms15 ms16 ms  gige6-2.ipcolo2.Chicago1.Level3.net [209.244.8.30]
  1224 ms27 ms25 ms  unknown.Level3.net [209.247.226.26]
  1330 ms17 ms23 ms  192.168.5.66
  1449 ms52 ms   102 ms  172.18.57.242
  1591 ms40 ms39 ms  geek.net [66.166.71.243]
 
 Trace complete.
 
 ---
 
 Trace #3:  Final trace, from Geek.NET back to my home broadband host 
 (my home IP changed to 10.0.0.1 for this example).
 
 traceroute to 10.0.0.1 (10.0.0.1), 30 hops max, 38 byte packets
  1  r-66-166-71-241.CHCGILGM.covad.net (66.166.71.241)  1.050 ms  0.938 ms  0.891 ms
  2  172.31.255.253 (172.31.255.253)  24.068 ms  26.558 ms  26.169 ms
  3  192.168.5.65 (192.168.5.65)  22.466 ms  23.301 ms  22.528 ms
  4  gigabitethernet8-0-131.ipcolo1.Chicago1.Level3.net (209.247.34.177)  23.638 ms  
 23.263 ms  22.539 ms
  5  gige5-1.core1.Chicago1.Level3.net (209.244.8.17)  22.243 ms  23.256 ms  22.528 ms
  6  

Re: Frustrating loss of connectivity...

2003-10-13 Thread Valdis . Kletnieks
On Mon, 13 Oct 2003 11:48:39 EDT, [EMAIL PROTECTED] said:

 RFO: Colocation with people who have business class DSL connectivity.

Notice that although doing that sort of colo is often frowned upon, the DSL
isn't the issue here.  His direct provider is being responsive, but THEIR upstream
is failing to push the issue to the upstream-upstream.  So he's got a pipe from A,
who's talking to B, and B is unwilling/unable to get C to deal with C's problem.

So the problem becomes how to get C moving..

I'm sitting at the end of multiple OC-12s, and I've had similar problems myself,
where a problem at some provider in another country causes operational issues
for myself.  So it isn't a DSL-only issue.



pgp0.pgp
Description: PGP signature


Re: Frustrating loss of connectivity...

2003-10-13 Thread Haesu

Doh! silly me... I didn't read the whole email in the first time.. Sorry about useless 
post :(

-hc

-- 
Haesu C.
TowardEX Technologies, Inc.
Consulting, colocation, web hosting, network design and implementation
http://www.towardex.com | [EMAIL PROTECTED]
Cell: (978)394-2867 | Office: (978)263-3399 Ext. 170
Fax: (978)263-0033  | POC: HAESU-ARIN

On Mon, Oct 13, 2003 at 12:23:05PM -0400, Haesu wrote:
 
 Hi, have you tried the return path traceroute... Like, run traceroute _From_ the 
 server behind dsl and back to you? Having traceroutes done either way may be helpful 
 often times b/c sometimes problems do rise on asymetric routing situation where 
 provider is doing bgp with x no. of providers.
 
 Please feel free to reply to me off list. I understand your frustration to get this 
 out to bunch of engineers, but this may be clasifed as off-topic..
 
 Thanks,
 -hc
 
 -- 
 Haesu C.
 TowardEX Technologies, Inc.
 Consulting, colocation, web hosting, network design and implementation
 http://www.towardex.com | [EMAIL PROTECTED]
 Cell: (978)394-2867 | Office: (978)263-3399 Ext. 170
 Fax: (978)263-0033  | POC: HAESU-ARIN
 
 On Mon, Oct 13, 2003 at 10:33:26AM -0500, Robert A. Hayden wrote:
  
  Hey all,
  
  I apologize for posting this here, especially for what is essentially an
  end-user broadband issue, but I'm looking at what appears to be a link a
  few hops upstream from me that has been flapping frequently and I can't
  get our provider to look into it.
  
  I am located in Madison, WI, and I have my mail/server machine geek.net
  co-located in Minneapolis on a business-class DSL line (1.5m/384k).  For
  the past couple of months, I'll lose connectivity for about 5 minutes
  several times a day.
  
  We attempted to open a case with the DSL provider (covad), but they were
  only interested in addressing last-mile issues and we got nowhere.  Same
  applied when addressing it from my broadband end, since the disconnect is
  3 providers upstream.
  
  In any case, any thoughts on where I should go with this?  I could try 
  Level3, but I suspect they'll blow me off since I'm not a direct customer.  
  It's getting quite frustrating as I'm trying to move a few hundred mb back 
  and forth over the VPN and with that one link flapping it's become almost 
  impossible.
  
  Traceroute examples included below.  I left real IPs here since they are 
  all easily determined anyways:
  
  --
  
  TRACE #1:  From my home connection to Geek.NET when it's BROKEN, note 
  where it breaks.
  
  C:\tracert 66.166.71.243
  
  Tracing route to geek.net [66.166.71.243]
  over a maximum of 30 hops:
  
124 ms10 ms29 ms  10.44.64.1
211 ms10 ms11 ms  172.18.98.98
319 ms22 ms43 ms  172.18.97.58
416 ms14 ms15 ms  12.125.143.113
558 ms34 ms47 ms  gbr2-a90s19.cgcil.ip.att.net [12.123.5.78]
616 ms17 ms16 ms  tbr1-p013602.cgcil.ip.att.net [12.122.11.37]
731 ms28 ms14 ms  ggr2-p310.cgcil.ip.att.net [12.123.6.65]
816 ms   105 ms16 ms  so-1-1-0.edge1.Chicago1.Level3.net [209.0.227.77]
921 ms21 ms33 ms  so-2-1-0.bbr2.Chicago1.level3.net [209.244.8.13]
   1032 ms19 ms14 ms  pos9-0.core1.Chicago1.level3.net [209.247.10.170]
   1120 ms31 ms48 ms  gige6-2.ipcolo2.Chicago1.Level3.net [209.244.8.30]
   1264 ms29 ms36 ms  unknown.Level3.net [209.247.226.26]
   13 *** Request timed out.
   14 *** Request timed out.
   ..
   30 *** Request timed out.
  
  Trace complete.
  
  --
  
  TRACE #2:  Same trace, but this time when it's working.
  
  C:\tracert 66.166.71.243
  
  Tracing route to geek.net [66.166.71.243]
  over a maximum of 30 hops:
  
121 ms16 ms15 ms  10.44.64.1
210 ms22 ms11 ms  172.18.98.98
310 ms15 ms11 ms  172.18.97.58
413 ms37 ms14 ms  12.125.143.113
515 ms18 ms18 ms  gbr2-a90s19.cgcil.ip.att.net [12.123.5.78]
626 ms15 ms19 ms  tbr1-p013602.cgcil.ip.att.net [12.122.11.37]
736 ms39 ms14 ms  ggr2-p310.cgcil.ip.att.net [12.123.6.65]
834 ms14 ms37 ms  so-1-1-0.edge1.Chicago1.Level3.net [209.0.227.77]
917 ms14 ms14 ms  so-2-1-0.bbr2.Chicago1.level3.net [209.244.8.13]
   1017 ms13 ms14 ms  pos9-0.core1.Chicago1.level3.net [209.247.10.170]
   1118 ms15 ms16 ms  gige6-2.ipcolo2.Chicago1.Level3.net [209.244.8.30]
   1224 ms27 ms25 ms  unknown.Level3.net [209.247.226.26]
   1330 ms17 ms23 ms  192.168.5.66
   1449 ms52 ms   102 ms  172.18.57.242
   1591 ms40 ms39 ms  geek.net [66.166.71.243]
  
  Trace complete.
  
  ---
  
  Trace #3:  Final trace, from Geek.NET back to my home broadband host 
  (my home IP changed to 

RE: Frustrating loss of connectivity...

2003-10-13 Thread Sirius F. Crackhoe

I've seen a similar issue with a carrier in Boston, also within Level3. You
can give them a call, although I am sure someone will object, I have never
had a problem with them being helpful, even for a non customer.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Robert A. Hayden
Sent: Monday, October 13, 2003 11:33 AM
To: [EMAIL PROTECTED]


Hey all,

I apologize for posting this here, especially for what is essentially an
end-user broadband issue, but I'm looking at what appears to be a link a few
hops upstream from me that has been flapping frequently and I can't get our
provider to look into it.

I am located in Madison, WI, and I have my mail/server machine geek.net
co-located in Minneapolis on a business-class DSL line (1.5m/384k).  For the
past couple of months, I'll lose connectivity for about 5 minutes several
times a day.

We attempted to open a case with the DSL provider (covad), but they were
only interested in addressing last-mile issues and we got nowhere.  Same
applied when addressing it from my broadband end, since the disconnect is
3 providers upstream.

In any case, any thoughts on where I should go with this?  I could try
Level3, but I suspect they'll blow me off since I'm not a direct customer.  
It's getting quite frustrating as I'm trying to move a few hundred mb back
and forth over the VPN and with that one link flapping it's become almost
impossible.

Traceroute examples included below.  I left real IPs here since they are all
easily determined anyways:

--

TRACE #1:  From my home connection to Geek.NET when it's BROKEN, note where
it breaks.

C:\tracert 66.166.71.243

Tracing route to geek.net [66.166.71.243] over a maximum of 30 hops:

  124 ms10 ms29 ms  10.44.64.1
  211 ms10 ms11 ms  172.18.98.98
  319 ms22 ms43 ms  172.18.97.58
  416 ms14 ms15 ms  12.125.143.113
  558 ms34 ms47 ms  gbr2-a90s19.cgcil.ip.att.net [12.123.5.78]
  616 ms17 ms16 ms  tbr1-p013602.cgcil.ip.att.net [12.122.11.37]
  731 ms28 ms14 ms  ggr2-p310.cgcil.ip.att.net [12.123.6.65]
  816 ms   105 ms16 ms  so-1-1-0.edge1.Chicago1.Level3.net
[209.0.227.77]
  921 ms21 ms33 ms  so-2-1-0.bbr2.Chicago1.level3.net
[209.244.8.13]
 1032 ms19 ms14 ms  pos9-0.core1.Chicago1.level3.net
[209.247.10.170]
 1120 ms31 ms48 ms  gige6-2.ipcolo2.Chicago1.Level3.net
[209.244.8.30]
 1264 ms29 ms36 ms  unknown.Level3.net [209.247.226.26]
 13 *** Request timed out.
 14 *** Request timed out.
 ..
 30 *** Request timed out.

Trace complete.

--

TRACE #2:  Same trace, but this time when it's working.

C:\tracert 66.166.71.243

Tracing route to geek.net [66.166.71.243] over a maximum of 30 hops:

  121 ms16 ms15 ms  10.44.64.1
  210 ms22 ms11 ms  172.18.98.98
  310 ms15 ms11 ms  172.18.97.58
  413 ms37 ms14 ms  12.125.143.113
  515 ms18 ms18 ms  gbr2-a90s19.cgcil.ip.att.net [12.123.5.78]
  626 ms15 ms19 ms  tbr1-p013602.cgcil.ip.att.net [12.122.11.37]
  736 ms39 ms14 ms  ggr2-p310.cgcil.ip.att.net [12.123.6.65]
  834 ms14 ms37 ms  so-1-1-0.edge1.Chicago1.Level3.net
[209.0.227.77]
  917 ms14 ms14 ms  so-2-1-0.bbr2.Chicago1.level3.net
[209.244.8.13]
 1017 ms13 ms14 ms  pos9-0.core1.Chicago1.level3.net
[209.247.10.170]
 1118 ms15 ms16 ms  gige6-2.ipcolo2.Chicago1.Level3.net
[209.244.8.30]
 1224 ms27 ms25 ms  unknown.Level3.net [209.247.226.26]
 1330 ms17 ms23 ms  192.168.5.66
 1449 ms52 ms   102 ms  172.18.57.242
 1591 ms40 ms39 ms  geek.net [66.166.71.243]

Trace complete.

---

Trace #3:  Final trace, from Geek.NET back to my home broadband host (my
home IP changed to 10.0.0.1 for this example).

traceroute to 10.0.0.1 (10.0.0.1), 30 hops max, 38 byte packets
 1  r-66-166-71-241.CHCGILGM.covad.net (66.166.71.241)  1.050 ms  0.938 ms
0.891 ms
 2  172.31.255.253 (172.31.255.253)  24.068 ms  26.558 ms  26.169 ms
 3  192.168.5.65 (192.168.5.65)  22.466 ms  23.301 ms  22.528 ms
 4  gigabitethernet8-0-131.ipcolo1.Chicago1.Level3.net (209.247.34.177)
23.638 ms  23.263 ms  22.539 ms
 5  gige5-1.core1.Chicago1.Level3.net (209.244.8.17)  22.243 ms  23.256 ms
22.528 ms
 6  so-4-0-0.bbr2.Chicago1.level3.net (209.247.10.169)  22.883 ms  22.522 ms
21.514 ms
 7  so-7-0-0.edge1.Chicago1.Level3.net (209.244.8.14)  23.624 ms  23.530 ms
23.884 ms
 8  att-Level3-oc48.Chicago1.Level3.net (209.0.227.78)  23.853 ms  22.426 ms
23.137 ms
 9  tbr2-p014001.cgcil.ip.att.net (12.123.6.70)  25.277 ms  25.311 ms
23.857 ms 10  gbr6-p20.cgcil.ip.att.net (12.122.11.62)  24.244 ms  23.695 ms
24.001 ms
11  gar2-p370.cgcil.ip.att.net (12.123.5.221)  23.892 ms  23.012 ms  23.858
ms
12  12.125.142.122