This command does just what it says - disables fair queueing on the interface, which results in interface running FIFO. With older not-so-powerful routers like 2500 it was often necessary to disable fair queue on 2Mbps serial else router could be overloaded. Today this is hardly issue (many even run more sophisticated things like Class-Based Wheighted Fair Queue and Low Latency Queue), but if you see that your router has high CPU load (80 and above) _and_ 'sh proc cpu' shows that significant part of it spent handling interrupts (second number after / sign), then disabling fair-queue may help (but not necessarily).
In reverse, it's recommended to enable fair-queue on links slower than 2Mbps to provide more fair split of link bandwidth to the users.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...