So I get a call from the HR department. Seems the payroll processor is experiencing a very performance accessing Abra over the MPLS WAN.
So I add an ACE in the QoS ACL for include the payroll processor’s computer so that her traffic will get marked as DSCP EF(46).
No improvement. Hmmm.
So then I setup a test across the WAN using the topology below…
I think trigger an extended ping on the source…
Notice the average round-trip time of 141ms. Also notice the (1) lost packet out of (500).
I then go to the edge routers to verify packet/marking and notice something interesting on the far end…
Notice the (500) packets marked EF.
So the traffic was dropped in the MPLS network after it egressed the far end router.
Then I think…hmm… maybe I should be doing this test from the near-side edge router….
Maybe the problem is CoS on the trunk link between my Core Switch and the near-side edge router?
Still a high amount of average latency (though no packet loss).
Turns out one of the server guys was copying a huge amount of data over the WAN. As soon as this data copy terminated the issue disappeared….
Do in fact seem Verizon is not policying traffic. Need to investigate what we’re paying for in Gold CAR.
No comments:
Post a Comment