Administering Cisco QoS for IP Networks

Chapter 7: Configuring Queuing and Congestion Avoidance

Introduction

Now that we have an understanding of the basic queuing and congestion avoidance mechanisms, it is time to become familiar with how these mechanisms are configured. This chapter describes how to reset an interface to its default queuing method, change its queuing method, and configure the queuing methods introduced in Chapter 6.

FIFO and weighted fair queuing require very little configuration, whereas priority and custom queuing configurations can range from extremely simple to quite complex. The level of complexity is almost entirely related to the access lists that control the functions of the queuing mechanisms, so it is important that you review access lists in detail before configuring these mechanisms.

The configurations shown in this chapter do not represent every possible configuration scenario or configuration option. If you need more information about configurations not shown in this chapter, there are many excellent examples on Cisco s Web site (www.cisco.com).

Configuring FIFO Queuing

FIFO is the default queuing mechanism for links with a speed greater than E1 (2.048 Mbps). On these links, no special configuration is required. However, on links of E1 speed or lower, weighted fair queuing is the default queuing mechanism. Thus, in order to make FIFO the queuing mechanism for these slower links, WFQ must be manually disabled.

Enabling FIFO

The interface command no fair-queue is used to disable WFQ when it is the default queuing mechanism. The following code disables WFQ so that FIFO can act as the queuing mechanism for that link:

Rosa<b class="bold">#show interface serial...

UNLIMITED FREE
ACCESS
TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Category: FIFO Memory
Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.