Hello! I have some AT&T MPLS sites under a managed contract with latency averaging 75-85 ms without any load. These sites are only 45 minutes away. What is considered normal/acceptable? Thanks,
On 11/15/12 12:54 -0600, Mikeal Clark wrote:
Hello!
I have some AT&T MPLS sites under a managed contract with latency averaging 75-85 ms without any load. These sites are only 45 minutes away. What is considered normal/acceptable?
I recently had a scenario with some MPLS sites within the state nearly doubling in latency (below 50ms round trip). Typically I see round trip latency in the 20-35ms range, and those sites are within about a 90 minute drive from each other (Oklahoma, mostly T1s). When I asked an AT&T tech to investigate, he did not see log entries to explain the increase or admit to any trouble, and stated that the service levels for these MPLS circuits allowed for 75-80ms and I don't recall if that was one way or round trip. He said that was to allow for coast to coast latency scenarios. Delay returned to typical levels about 4 days later, without explanation. -- Dan White
Acceptable from a technical standpoint (in that stuff works) or acceptable from an expected service standpoint? In the case of the former, MPLS can run over really high latencies, so you're nowhere near the limit. For the latter, 85ms would be highly unacceptable to me for a circuit to a site that's so close. I would think your traffic is either being routed really, really badly or their circuits are way over-subscribed. On Thu, Nov 15, 2012 at 10:54 AM, Mikeal Clark <mikeal.clark@gmail.com>wrote:
Hello!
I have some AT&T MPLS sites under a managed contract with latency averaging 75-85 ms without any load. These sites are only 45 minutes away. What is considered normal/acceptable?
Thanks,
-- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
On Nov 15, 2012, at 1:54 PM, Mikeal Clark wrote:
Hello!
I have some AT&T MPLS sites under a managed contract with latency averaging 75-85 ms without any load. These sites are only 45 minutes away. What is considered normal/acceptable?
MPLS as a technology should not add any significant delay as it is just a few bytes of label on the packet. What is the physical path of the circuits involved? Have you asked for the design of them? - Jared
On Thu, Nov 15, 2012 at 1:54 PM, Mikeal Clark <mikeal.clark@gmail.com> wrote:
I have some AT&T MPLS sites under a managed contract with latency averaging 75-85 ms without any load. These sites are only 45 minutes away.
I've noticed this with AT&T's MPLS product when dealing with the internal corporate network here. I don't know what they're doing wrong but it is so very wrong.
What is considered normal/acceptable?
Less than 10ms unless you're using a sub-T1 interface or going a very long distance. Regards, Bill Herrin -- William D. Herrin ................ herrin@dirtside.com bill@herrin.us 3005 Crane Dr. ...................... Web: <http://bill.herrin.us/> Falls Church, VA 22042-3004
--- On Thu, 11/15/12, William Herrin <bill@herrin.us> wrote:
From: William Herrin <bill@herrin.us> Subject: Re: MPLS acceptable latency? To: "Mikeal Clark" <mikeal.clark@gmail.com> Cc: "NANOG [nanog@nanog.org]" <nanog@nanog.org> Date: Thursday, November 15, 2012, 1:23 PM On Thu, Nov 15, 2012 at 1:54 PM, Mikeal Clark <mikeal.clark@gmail.com> wrote:
I have some AT&T MPLS sites under a managed contract with latency averaging 75-85 ms without any load. These sites are only 45 minutes away.
I've noticed this with AT&T's MPLS product when dealing with the internal corporate network here. I don't know what they're doing wrong but it is so very wrong.
circa 2007, noticed same thing: never below 90ms coast-to-coast across as13979. atm ds3 handoffs on both ends.
What is considered normal/acceptable?
Less than 10ms unless you're using a sub-T1 interface or going a very long distance.
Regards, Bill Herrin
-- William D. Herrin ................ herrin@dirtside.com bill@herrin.us 3005 Crane Dr. ...................... Web: <http://bill.herrin.us/> Falls Church, VA 22042-3004
Perhaps the network is "oldish" and there are BW bottlenecks that lead to queues on the switches/routers that results in higher latency. This would depend alot on the internal QoS strategy used by AT&T, the type of equipment used and the load in different parts of the network. The only way to know what happens inside their MPLS cloud is to get past support and ask someone from the technical staff. On 11/16/2012 12:06 AM, Randy wrote:
--- On Thu, 11/15/12, William Herrin <bill@herrin.us> wrote:
From: William Herrin <bill@herrin.us> Subject: Re: MPLS acceptable latency? To: "Mikeal Clark" <mikeal.clark@gmail.com> Cc: "NANOG [nanog@nanog.org]" <nanog@nanog.org> Date: Thursday, November 15, 2012, 1:23 PM On Thu, Nov 15, 2012 at 1:54 PM, Mikeal Clark <mikeal.clark@gmail.com> wrote:
I have some AT&T MPLS sites under a managed contract with latency averaging 75-85 ms without any load. These sites are only 45 minutes away. I've noticed this with AT&T's MPLS product when dealing with the internal corporate network here. I don't know what they're doing wrong but it is so very wrong. circa 2007, noticed same thing: never below 90ms coast-to-coast across as13979. atm ds3 handoffs on both ends.
What is considered normal/acceptable? Less than 10ms unless you're using a sub-T1 interface or going a very long distance.
Regards, Bill Herrin
-- William D. Herrin ................ herrin@dirtside.com bill@herrin.us 3005 Crane Dr. ...................... Web: <http://bill.herrin.us/> Falls Church, VA 22042-3004
participants (7)
-
Alex -
Dan White -
Jared Mauch -
Mike Hale -
Mikeal Clark -
Randy -
William Herrin