FP QoS configuration
FP4 or later ingress and egress queue reallocation
FP4 or later forwarding planes support the reallocation of queues between ingress and egress. Queues can be reallocated either from ingress to egress, or from egress to ingress. The reallocation is performed in sets of 8k (8192) queues, with the requirement that a minimum of 8k queues must be allocated at both ingress and egress. The ingress and egress buffer pool sizes are not affected by the queue reallocation.
The queue allocation is configured using a named FP resource policy that is created using the fp-resource-policy command within the QoS configuration branch and is applied under the card>fp context. The system supports up to 15 policies, including the system-created default policy that cannot be modified or deleted and is applied by default to all FP4 or later forwarding planes. The default policy allocates 128k queues to ingress and 128k queues to egress.
The queue allocation within the FP resource policy is configured as follows:
configure
qos
fp-resources-policy policy-name
queues
ingress-percent-of-total percent-of-total-queues
The ingress-percent-of-total command specifies the percentage of the total number of queues allocated to ingress queues, with the remainder being allocated to egress queues. The percentage is configured as an integer to two decimal places with a range from 4.00 to 97.00 (values outside of this range are not applicable because of the requirement of a minimum of 8k queues are ingress and egress).
Queues can be allocated in sets of 8k queues. If the percentage configured results in the queue allocation not being a multiple of 8k, the number of queues at ingress is rounded down to the next 8k boundary, and consequently the number of queues at egress is rounded up to the next 8192 boundary, both while respecting the minimum at ingress and egress. For example, if the ingress-percent-of-total is configured to 27%, that calculates to 70778.88 queues, the number of ingress queues would be rounded down to 65536 queues and the number of egress queues rounded up to 196608.
FP resource policies are applied to a forwarding plane as follows:
configure
card slot-number
fp fp-number
fp-resources-policy name
An FP resource policy that is applied to an FP cannot be deleted.
The queue allocation can be modified by either applying a differently named FP resource policy to an FP, and this includes removing an applied user-created FP resource policy to return to the default policy, or modifying the ingress-percent-of-total command that also includes removing this parameter to return to its default configuration in the policy applied to an FP. The system then checks whether requested queue allocation is achievable based on the current ingress and egress queue consumption on the related FP. If the requested queue allocation is not achievable, the command fails.
When the queue allocation is modified, the system immediately resets the associated cards, XIOMs, and MDAs to reallocate the queues, with the following exceptions:
When the system boots and reads the configuration file, the queue allocation within the file is used without requiring an additional reset or reboot.
When the queue allocation is modified on a 7750 SR-1, the system does not automatically reset the card or MDA; it is the user's responsibility to save the configuration and immediately reboot the system.
If the card, XIOM or MDA is provisioned but not equipped, the modification is accepted and is immediately active.
When redundancy mechanisms are used that spans FPs, for example LAGs, it is recommended that the same queue allocation is applied to all related FPs.
FP resource policies can be displayed using a show command, with the details of the configured ingress-percent-of-total command and the associations on which FPs it is applied. The name of the FP resource policy applied to an FP can be displayed using the show card slot-number detail command. For example, the FP resource policy below allocates the minimum number of queues to ingress and the maximum number of queues to egress, and is applied to card 1 FP 1:
*A:PE# show qos fp-resource-policy "ingress-8k-egress-248k" detail
===============================================================================
FP Resource Policy
===============================================================================
Policy Name : ingress-8k-egress-248k
Description : (Not Specified)
-------------------------------------------------------------------------------
Queues
-------------------------------------------------------------------------------
Ingress Percent of total : 4.00
-------------------------------------------------------------------------------
FP Resource Policy Associations
-------------------------------------------------------------------------------
Card-FP
-------------------------------------------------------------------------------
1-1
-------------------------------------------------------------------------------
No. of Associations : 1
-------------------------------------------------------------------------------
===============================================================================
*A:PE# show card 1 detail | match expression "FP|FP Resource Policy"
FP 1 Specific Data
FP Resource Policy : ingress-8k-egress-248k
Generation : FP4
FP 2 Specific Data
FP Resource Policy : default
Generation : FP4
FP 3 Specific Data
FP Resource Policy : default
Generation : FP4
FP 4 Specific Data
FP Resource Policy : default
Generation : FP4
*A:PE#
When an FP resources policy is applied to change the queue allocation, the resulting queue allocation can be displayed using the tools dump resource-usage card slot-num fp fp-number command:
*A:PE# tools dump resource-usage card 1 fp 1 | match expression "Ingress Queues|Egress Queues"
Ingress Queues | 8192 535 7657
Egress Queues | 253952 108 253844
*A:PE#