Network-control queue counter increases on ccc-configured interface

01.26.12   |  
‎01-26-2012 03:48 AM

Dear all,


I have detected a strange behaviour on one of our ccc-configured gigabit ethernet interface.

I have a P2P ccc service and at one end strangely network-control queue counter is increasing as seen below.

There is no other ccc-configured service on the router is getting increment on their network-control queue.


LON> show configuration interfaces ge-2/0/4
apply-groups customer-template;
description "Customer-A";
gigether-options {
unit 0 {
    family ccc {
        policer {
            input 200m-bw-limit;
            output 200m-bw-limit;

LON> show configuration groups customer-template
interfaces {
    <*> {
        mtu 9188;
        encapsulation ethernet-ccc;
        unit 0 {
            family ccc;
 Queue counters:       Queued packets  Transmitted packets      Dropped packets
    0 best-effort           2674026389           2674026391                    0
    1 expedited-fo                   0                    0                    0
    2 assured-forw                   0                    0                    0
    3 network-cont                 832                  832                    0

Is there anybody has such experience on Juniper MX switches?


Thanks and regards,

Gokhan Gumus


Re: Network-control queue counter increases on ccc-configured interface

01.29.12   |  
‎01-29-2012 05:07 PM

Hi Gokhan,


There is a default class-of-service config on all interfaces, you can use 'show class-of-service interface' to see what schedulers and classifiers the interface is using. Traffic generated by the router will use the network-control queue, and traffic from your customers may also be classified in to this queue depending on your incoming classification configuration.


To avoid having traffic in this queue you should configure class-of-service classification on the ingress points of this service, this classification can then map all customer traffic to the BE queue. You may also need rewrite rules on the egress interfaces to make sure this traffic stays in the BE queue when it reaches the next router.