[j-nsp] Network-control queue counter increases on ccc-configured interface
p.mayers at imperial.ac.uk
Thu Jan 26 16:01:32 EST 2012
On 01/26/2012 06:47 PM, Keegan Holley wrote:
>>> That's not exactly accurate. Cisco's kit also has some queuing setup
>>> by default. The details vary by platform. Every cisco router I've
>>> worked with defaults to trusting incoming markings rather then
>>> rewriting them to best effort. So the cisco default is vaguely
>>> similar. Also, in order for someone to take advantage of this queue
>> No cisco router does this to my understanding, some cisco routers use TOS
>> values in punt path by default in attempt for rudimentary CoPP. But no
>> Cisco that I know or have tested has different transit scheduling per class
> The 6509 and the other L3 switch platforms (not sure about the nexus)
> come to mind here. Not sure about the CRS and ASR-9k though.
I don't think the 6500 defaults to trusting incoming markings.
It does setup queueing when you "mls qos", but nothing goes into the new
queues because the default port state is untrust. So it's sort of the
opposite to what happens on JunOS, if I'm understanding this thread.
More information about the juniper-nsp