Help - Search - Members - Calendar
Full Version: Connection issues & ATT
The Planet Forums > System Administration > Network
ajz4221
The Planet techs: Is it possible for your DCOps to force a server to route through another ISP?
I don't want to bother tech support yet.

I have been monitoring one of my servers' I can hardly use since this past Saturday due to 96% packet loss.
It isn't really The Planet's issue because there is hardly any packet loss monitoring the same server from H2 data center. So, since it isn't the server, it is clearly AT&T (plus the trace routes show the issue before it reaches DLLSTX4).
I don't have an issue with DLLSTX6 or H2.
Packets travel via AT&T to these data centers without issue (which I find kind of funny).

Of course, the word "trace route" and "packet loss" is greek to the people at AT&T.
It isn't even worth talking to them unless you are a customer with over a $1 million contract.
(Although, that might not even be enough).

Edit - the IP of AT&T with the issue appears to be [ 12.83.10.120 ] Shreveport, Louisiana.
I route through the same IP to get to H2 and it works fine.
Just starts loosing packets to DLLSTX4 from there.
Reverse from DLLSTX4 packet loss occurs at 65.83.239.88 in Atlanta, GA. (hop after the above in reverse).
If anyone is ever bored at TP, maybe you can pull your weight at AT&T and see what might be up.
wcharnock
QUOTE (ajz4221 @ Feb 24 2009, 06:40 PM) *
The Planet techs: Is it possible for your DCOps to force a server to route through another ISP?
I don't want to bother tech support yet.

I have been monitoring one of my servers' I can hardly use since this past Saturday due to 96% packet loss.
It isn't really The Planet's issue because there is hardly any packet loss monitoring the same server from H2 data center. So, since it isn't the server, it is clearly AT&T (plus the trace routes show the issue before it reaches DLLSTX4).
I don't have an issue with DLLSTX6 or H2.
Packets travel via AT&T to these data centers without issue (which I find kind of funny).

Of course, the word "trace route" and "packet loss" is greek to the people at AT&T.
It isn't even worth talking to them unless you are a customer with over a $1 million contract.
(Although, that might not even be enough).

Edit - the IP of AT&T with the issue appears to be [ 12.83.10.120 ] Shreveport, Louisiana.
I route through the same IP to get to H2 and it works fine.
Just starts loosing packets to DLLSTX4 from there.
Reverse from DLLSTX4 packet loss occurs at 65.83.239.88 in Atlanta, GA. (hop after the above in reverse).
If anyone is ever bored at TP, maybe you can pull your weight at AT&T and see what might be up.


I've asked some of my engineers to get in touch with you to look at this. PM me if you don't hear from someone in the next day or so.
ChrisP
ajz4221,

Can you open a ticket with traceroutes to and from the affected server as well as to and from one of the unaffected servers? I will need to see the path before being able to determine what we can do to assist you with this.

Thanks.
ajz4221
I will send the ticket number to you Chris.
Thanks.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.