Activating hardware aggregate shapers

About this task

Hardware aggregate shapers are applicable to Ethernet and PXC port subscriber management only; 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.

Procedure

Use the following command to enable hardware aggregate shapers on a specific FP:
- classic CLI
```
configure qos fp-resource-policy aggregate-shapers auto-creation
```
- MD-CLI
```
configure qos fp-resource-policy aggregate-shapers auto-creation true
```
For chassis-based systems, this causes a reboot of the card on which the FP resides. For non-chassis-based systems, user must save the configuration and reboot the system manually. When the FP resource policy is in operation, the allocation of queue sets is 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 use 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.

Use the following command to enable hardware aggregate shapers for subscribers:

classic CLI

configure qos fp-resource-policy aggregate-shapers hw-agg-shaping subscribers

MD-CLI

configure qos fp-resource-policy  aggregate-shapers subscribers true

Use the following command to enable the use of hardware aggregate shaping on all ports of the FP:

classic CLI

configure qos fp-resource-policy ports hqos-mode hw-agg-shaping

MD-CLI

configure qos fp-resource-policy  ports hqos-mode hw-agg-shaping true

Example classic CLI

*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#

Example MD-CLI

[ex:/configure qos fp-resource-policy "test"]
A:admin@node-2#

    aggregate-shapers {
        auto-creation true
        hw-agg-shapers {
            subscribers true
        }
    }
    ports {
        hqos-mode hw-agg-shaping
    }

Nokia recommends that you execute these commands in a single commit.

What to do next

After the preceding commands 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.