cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
432
Views
0
Helpful
1
Replies

qos question - randon detect / tail drop

carl_townshend
Spotlight
Spotlight

Hi all

I see that by default Cisco routers use tail drop as the congestion avoidance technique, which I believe can cause the tcp global synchronization issues.

Is it best practice to set routers to use random detect (WRED)?

how com they don't come like this as default?

cheers

1 Accepted Solution

Accepted Solutions

Joseph W. Doherty
Hall of Fame
Hall of Fame

I see that by default Cisco routers use tail drop as the congestion avoidance technique, which I believe can cause the tcp global synchronization issues.

Not sure if tail drop was chosen as a congestion avoidance technique.

Is it best practice to set routers to use random detect (WRED)?

Unless you're a QoS expert, I recommend against using WRED for its primary purpose.  It's actually surprisingly difficult to get it to work optimally.  That said, WRED can be handy if you want to manage tiered drops.

how com they don't come like this as default?

Principally, I believe, because any "fancy" QoS can load up the CPU.  FIFO has the least overhead.  FIFO is also much simpler to implement, one reason why you often don't find WRED an option on Cisco switches.

PS:

BTW, another candidate for a better default congestion avoidance technique, I would suggest WFQ - ah but wait, Cisco too may have at one time thought that as on serial interfaces, 2 Mbps and under, WFQ was the default over single queue FIFO.

View solution in original post

1 Reply 1

Joseph W. Doherty
Hall of Fame
Hall of Fame

I see that by default Cisco routers use tail drop as the congestion avoidance technique, which I believe can cause the tcp global synchronization issues.

Not sure if tail drop was chosen as a congestion avoidance technique.

Is it best practice to set routers to use random detect (WRED)?

Unless you're a QoS expert, I recommend against using WRED for its primary purpose.  It's actually surprisingly difficult to get it to work optimally.  That said, WRED can be handy if you want to manage tiered drops.

how com they don't come like this as default?

Principally, I believe, because any "fancy" QoS can load up the CPU.  FIFO has the least overhead.  FIFO is also much simpler to implement, one reason why you often don't find WRED an option on Cisco switches.

PS:

BTW, another candidate for a better default congestion avoidance technique, I would suggest WFQ - ah but wait, Cisco too may have at one time thought that as on serial interfaces, 2 Mbps and under, WFQ was the default over single queue FIFO.

Review Cisco Networking for a $25 gift card