We have a Verizon MPLS network and are experiencing voice quality issues. I know voice packets are being dropped from Remote Office A to Central Office B.
Besides the LLQ configuration on the VzB PE interface output (towards remove office A), there is also a policing configuration that VzB applies on the input, to match the priorityt queue size for voice. In the Verizon MPLS PE router at Office A, while we're not apparently exceeding the priority queue, the VzB router reports that it is dropping packets under the policing configuration:
Class-map: realtime (match-any)
3857612 packets, 739935430 bytes
5 minute offered rate 107000 bps, drop rate 0 bps
Match: ip dscp cs5 (40) ef (46)
3857612 packets, 739935430 bytes
5 minute rate 107000 bps
Priority: 400 kbps, burst bytes 10000, b/w exceed drops: 0
police:
cir 400000 bps, bc 12500 bytes
conformed 3826365 packets, 733152282 bytes; actions:
transmit
exceeded 31247 packets, 8249690 bytes; actions:
drop
conformed 107000 bps, exceed 0 bps
For polcing, since we're not exceeding CIR, then I believe this is inferring that we must be exceed "bc" of 12500 bytes- can someone verify this? Is anyone familiar with VzB Policing (I'm also trying to get VzB to answer this, but thought I'd ask what others' experience is with this). If this is the case, ordering more CIR for the priority queue won't fix it; somehow I'd have to get VzB to increase the bc size, which I do not know if that is orderable. Or perhaps the bc size is a default value generated, based upon the size of the CIR, and ordering a larger CIR may drive the bc value higher?
Thanks for any/all input.
