When a BPX VBR.3 connection is reporting "oflw clp0 dscd" with no other errors being reported and the PVC utilisation is minimal, less than 40%. What, why and which parameters causes the ingress Queue Engine (QE) to drop cells?
Also with VBR-nrt connections there is no VC_queue on ingress, so what function does the QE perform?
A few things I can think of here to troubleshoot this issue..
1. With VBR.3 , you are policing for compliance for SCR and and MAximum burst size on the second bucket. Have these values been played with to see if they help?
2. If using 2 port BXM OC-12, you may be running into a card limit problem when both ports are utilized as the both the ports share the QE. There is one ingress QE for ingress operation for both ports and one egress QE for egress operation on both ports.
3. Some times the card gets misprogrammed with older firmware w.r.t policing values. Does rerouting this connection, dncon-upcon, delcon-addcon or resetcd make the problem dissapear? If yes then you have hit a card misprogramming issue.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...