North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: Possible explanations for a large hop in latency
We had a similar situation going from Minneapolis to Kansas City via Chicago. Normal latency from Minneapolis to Chicago via Level3 MPLS network is about 14msec RTT. When the the circuit from Minneapolis to Chicago went out for one reason or another, our MPLS link went from Minneapolis to Tulsa, to Dallas, and then to Chicago.. That added a little latency in the path from Minneapolis to Chicago.. We didn't need to exceed the SLA in order to cry foul. They didn't intentionally create an inefficient path.. The problem was recognized and fixed the same day. Latency on an MPLS circuit is the cumulative latency on the Label Switch Path, and a number of the hops are invisible. The latency per hop is still the same... you just can't see that your traffic is travelling to say Denver or Dallas. Tim Peiffer Network Support Engineer Networking and Telecommunications Services University of Minnesota/NorthernLights GigaPOP Frank Bulk - iNAME wrote: Thanks for the added information.
|