[j-nsp] Network-control queue counter increases on ccc-configured interface

[Gökhan Gümüş]

Thanks for the replies.
I do not have any CoS configuration on my router.
There is no Spanning-Tree is running between my device and customer device.
I have no idea what is causing an increment in the network-control queue.

Any ideas would be appreciated.

Thanks and regards,
Gokhan

On Thu, Jan 26, 2012 at 4:52 PM, Keegan Holley <keegan.holley at sungard.com>wrote:

> Well NC (network control) is a completely different queue than EF
> (expedited forwarding).  This could be normal.  Several things such as
> routing protocol updates are set to NC by default because it is
> network control traffic or part of the network control plane.  Such
> traffic should be prioritized during congestion to keep the paths
> stable.  I wouldn't use the NC queue for other traffic if you can
> avoid it and I wouldn't make this traffic best effort without figuring
> out what it is.  Is it possible that it's just a control protocol?  I
> know most routing protocols mark their hello's as NC. Spanning tree
> BPDU's might do the same but I can't remember off the top of my head.
>
>
> 2012/1/26 Gökhan Gümüş <ggumus at gmail.com>:
> > Dear Saku,
> >
> > Thanks for the reply.
> >
> > I checked the queues on the interface as seen below;
> >
> > LON> show class-of-service interface ge-2/0/4
> > Physical interface: ge-2/0/4, Index: 158
> > Queues supported: 8, Queues in use: 4
> >  Scheduler map: <default>, Index: 2
> >
> >  Logical interface: ge-2/0/4.0, Index: 216
> >
> > How can i use %100 BE by changing my config in Juniper?
> >
> > Thanks and regards,
> > Gokhan
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
>