cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Bookmark
|
Subscribe
|
1941
Views
0
Helpful
2
Replies

WRR Queue Configurations

Mokhalil82
Level 4
Level 4

Hi 

I am in the process of upgrading a 6500 to a 6800X. Many ports on the existing 6500 have the WRR Queues configured as below. The new core does not accept some of those lines and my knowledge regarding WRR is currently limited. Is it essential that WRR is configured properly on the new core? Will mis-configuration drop traffic or cause any loss of connectivity. I have servers, access switches etc connected to these ports

 wrr-queue bandwidth 5 25 70 
 wrr-queue queue-limit 5 25 40 
 wrr-queue random-detect min-threshold 1 80 100 100 100 100 100 100 100 
 wrr-queue random-detect min-threshold 2 80 100 100 100 100 100 100 100 
 wrr-queue random-detect min-threshold 3 50 60 70 80 90 100 100 100 
 wrr-queue random-detect max-threshold 1 100 100 100 100 100 100 100 100 
 wrr-queue random-detect max-threshold 2 100 100 100 100 100 100 100 100 
 wrr-queue random-detect max-threshold 3 60 70 80 90 100 100 100 100 
 mls qos trust dscp

 

Thanks

1 Accepted Solution

Accepted Solutions

Joseph W. Doherty
Hall of Fame
Hall of Fame

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.

Posting

6500 QoS depends very much on the line card, so just listing wrr-queue settings doesn't provide the whole picture.

The sup2T in the 6800x has additional queuing features.

What you should really do, is determine what your logical QoS policy is (which might be figured out by "reverse engineering" your 6500 QoS), determine if that's what you want, then define sup2T policies to do the same or what you want.

Unlikely that a "bad" QoS configuration will cause loss of connectivity, but a "bad" QoS configuration can be adverse to traffic.

View solution in original post

2 Replies 2

Joseph W. Doherty
Hall of Fame
Hall of Fame

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.

Posting

6500 QoS depends very much on the line card, so just listing wrr-queue settings doesn't provide the whole picture.

The sup2T in the 6800x has additional queuing features.

What you should really do, is determine what your logical QoS policy is (which might be figured out by "reverse engineering" your 6500 QoS), determine if that's what you want, then define sup2T policies to do the same or what you want.

Unlikely that a "bad" QoS configuration will cause loss of connectivity, but a "bad" QoS configuration can be adverse to traffic.

Thanks Joseph

Think il have to figure out my existing QOS, do some reading and apply that to the 6800x.