[Contents] [Prev] [Next] [Index] [Report an Error]

Enabling Eight Queues on ATM2 IQ Interfaces

By default, ATM2 IQ PICs on T-series and M320 platforms are restricted to a maximum of four egress queues per interface. You can enable eight egress queues on ATM2 IQ interfaces by including the max-queues-per-interface statement at the [edit chassis fpc slot-number pic pic-number] hierarchy level:



[edit chassis fpc slot-number pic pic-number]

max-queues-per-interface (4 | 8);

The numerical value can be 4 or 8.

If you include the max-queues-per-interface statement, all ports on the ATM2 IQ PIC use the configured maximum.

When you include the max-queues-per-interface statement and commit the configuration, all physical interfaces on the ATM2 IQ PIC are deleted and re-added. Also, the PIC is taken offline and then brought back online immediately. You do not need to manually take the PIC offline and online. You should change modes between four queues and eight queues only when there is no active traffic going to the ATM2 IQ PIC.

For general information about configuring up to eight forwarding classes and queues on PICs other than ATM2 IQ PICs, see Configuring Up to Eight Forwarding Classes.

Note: When you are considering enabling eight queues on an ATM2 IQ interface, you should note the following:

ATM2 IQ interfaces using Layer 2 circuit trunk transport mode support only four CoS queues.
ATM2 IQ interfaces with MLPPP encapsulation support only four CoS queues.
You can configure only four RED profiles for the eight queues. Thus, queue 0 and queue 4 share a single RED profile, as do queue 1 and queue 5, queue 2 and queue 6, and queue 3 and queue 7. There is no restriction on EPD threshold per queue.
The default chassis scheduler allocates resources for queue 0 through queue 3, with 25 percent of the bandwidth allocated to each queue. When you configure the chassis to use more than four queues, you must configure and apply a custom chassis scheduler to override the default. To apply a custom chassis scheduler, include the scheduler-map-chassis statement at the [edit class-of-service interfaces at-fpc/pic/*] hierarchy level. For more information about configuring and applying a custom chassis scheduler, see Associating the Scheduler Map with the Packet Forwarding Component Queues.

[Contents] [Prev] [Next] [Index] [Report an Error]