Hardware aggregate shapers are applicable to subscriber management only. This means that for other objects, such as SAP and queue-groups, only software-driven HQoS can be used. Hardware aggregate shapers and software-driven HQoS can coexist on the same FP.
Enable hardware aggregate shapers on a specific FP, use the following classic CLI command:
config>qos>fp-resource-policy>aggregate-shapers auto-creation
Similarly, to enable hardware aggregate shapers on a specific FP, use following MD-CLI command:
configure qos fp-resource-policy name aggregate-shapers auto-creation true
This causes a reboot of the corresponding FP and the allocation of queue-sets in blocks of eight. This occurs for all objects already configured on the FP, regardless of how many queues they effectively use. If there are not enough queues to perform the allocation, the commit command fails in MD-CLI.
The auto-creation command does not force subscriber hosts to use a hardware aggregate shaper. Even if this command is enabled, subscriber hosts on the specified FP still uses traditional HQoS if it is configured. Any hardware aggregate shaper-related configuration in the SAP egress profile, SLA profile, and sub-profile is ignored except in the scheduler class configuration, where by default, expedited and non-expedited classes are mapped into scheduling classes as follows.
Non-expedited class queues map to sched-class 4.
Expedited class queues map to sched-class 6.
Enable hardware aggregate shapers for subscribers, the following classic CLI command is required:
config>qos>fp-resource-policy>aggregate-shapers hw-agg-shaping subscribers
Similarly, for MD-CLI, the following command is required:
configure qos fp-resource-policy name aggregate-shapers subscribers true
Enable the use of hardware aggregate shaping on all ports of the FP.
Classic CLI command:
config>qos>fp-resource-policy>ports hqos-mode hw-agg-shaping
MD-CLI command:
configure qos fp-resource-policy name ports hqos-mode hw-agg-shaping true
Classic CLI example:
*A:SR-1s-test>config>qos>fp-resource-policy# info
----------------------------------------------
aggregate-shapers
auto-creation
hw-agg-shapers subscribers
exit
ports
hqos-mode hw-agg-shaping
exit
----------------------------------------------
*A:SR-1s-test>config>qos>fp-resource-policy#
In MD-CLI, it is recommended (but not required) to execute these commands in a single commit.
(ex)[/configure qos fp-resource-policy "test"]
aggregate-shapers {
auto-creation true
hw-agg-shapers {
subscribers true
}
}
ports {
hqos-mode hw-agg-shaping
}
After the commands above are applied to a specific FP, all subscriber hosts created on this FP use hardware aggregate shaping and any traditional HQoS-related configuration is ignored.
SAP and queue group objects always use traditional HQoS configuration whether they are created on the same or different ports as subscriber hosts. Any hardware aggregate shaping configuration associated with a SAP or queue group is ignored.