High Scale QoS IOM: QoS, Service, and Network Configuration

Each queue can be independently shaped by configuring its PIR and attaching it to a primary shaper scheduling class. Alternatively, it can be shaped together with other queues in the same HSQ queue group as part of a WRR group. The WRR group can have a configured rate, and also needs to be attached to a primary shaper scheduling class.

There are eight queues and two WRR groups available within an HSQ queue group, which attach to the six primary shaper scheduling classes. Only one object (queue or WRR group) per HSQ queue group can attach to a scheduling class at any time, so to make use of all queues in an HSQ queue group, at least three queues must be attached to a WRR group. Queues and WRR groups can remain unattached from a scheduling class, in which case the related queues discard all received packets.

The queue PIR is configured under the queue within a SAP egress QoS policy for services, in a network queue policy for network interfaces, or in an egress queue group template for both access and network egress queue group instances. The queue CIR is ignored when the policy is applied to an HSQ IOM. The per-WRR group PIR is configured within the same policies under the hs-wrr-group context. Queue and WRR group PIR use packet-based accounting (L2 rate), which can be adjusted using the queue packet-byte-offset parameter for SAP egress and egress queue group instances.

The attachment of a queue or WRR group to a scheduling class is configured within an hs-attachment-policy. A default hs-attachment-policy (which is not configurable) is created by the system and is applied to all SAP egress QoS policies, network queue policies, and egress queue group templates. The default policy has queues 1 to 3 attached to WRR group 1, which is attached to scheduling class 1, and queues 4 to 8 attached directly to scheduling classes 2 to 6.

When creating a new hs-attachment-policy, the following rules apply to the queue and WRR attachment:

• A queue must be attached to a scheduling class, or a WRR group, which is also attached to a scheduling class, so as to forward packets.

• Only one queue or WRR group can be attached to a scheduling class per HSQ queue group.

• Queues can only be attached to scheduling classes in an ascending order; for example, if queue 2 is attached to scheduling class 2, then queue 1 cannot attach to scheduling classes 3 to 6.

• The queue identifiers must be contiguous when attaching queues to a WRR group.

• Queues attached to WRR group 1 must have lower queue identifiers than those attached to WRR group 2.

• The maximum number of queues attached to a WRR group is six: six to group 1 or six to group 2, or six to a combination of groups 1 and 2.

• WRR group 2 can only be attached to a scheduling class after WRR group 1 has at least one attached queue and has been attached to a scheduling class.

• WRR group 2 must be attached to a higher scheduling class than WRR group 1.

A per-HSQ queue group aggregate shapes traffic forwarded by all the queues in its associated HSQ queue group to an aggregate rate. This is applicable to SAP egress queues, and to both access and network egress queue group instances. It is not applicable to network egress queues.

The per-HSQ queue group aggregate PIR is configurable as an egress aggregate rate limit applied under a SAP or a port access or network egress queue group instance. The HSQ queue group PIR uses packet-based accounting (L2 rate), which can be adjusted using the queue packet-byte-offset parameter for SAP egress and egress queue group instances.

When using HSQ queue groups with access or network egress queue group instances on 100G ports, the hs-turbo parameter can be configured under the port queue group instance to allow the corresponding HSQ queue group queues to achieve a higher throughput. The hs-turbo parameter is not applicable to 10G ports and so is ignored when configured under a queue group instance on a 10G port.

A primary shaper aggregate shapes the traffic forwarded by all of the HSQ queue groups connected to the primary shaper to an aggregate rate.

User-configured primary shapers are not applicable to SAP egress HSQ queue groups, network egress HSQ queue groups, or both access and network egress queue group instance HSQ queue groups. However, the hierarchy shown in Egress HSQ IOM Scheduling Hierarchy is always conformed to, so by default these HSQ queue groups always connect to a system-created per-port default primary shaper that has its aggregate PIR rate set to the maximum rate, so as not to constrain the traffic rate at this level.

The system also instantiates a primary shaper, again with its aggregate PIR set to the maximum rate, when the first egress SAP or pseudowire SAP (PW-SAP) is associated with a secondary shaper. This primary shaper is then used by all HSQ queue groups associated with that secondary shaper. User-configured primary shaper aggregates are applicable to ESM, which is beyond the scope of this chapter.

Secondary shapers are aimed at providing QoS control for traffic forwarded to a specific downstream device, such as an access node.

A secondary shaper aggregate shapes the traffic forwarded by all of its connected primary shapers (and HSQ queue groups). Secondary shapers are applicable to SAP egress queues, but not to network egress or to both access and network egress queue group instance HSQ queue groups. The hierarchy shown in Egress HSQ IOM Scheduling Hierarchy is always conformed to, so by default all primary shapers (and their HSQ queue groups) always connect to a system-created per-port default secondary shaper that has its aggregate PIR rate set to the maximum rate, so as not to constrain the traffic rate at this level. Secondary shaper aggregates are also applicable to ESM, which is beyond the scope of this chapter.

Multiple HS secondary shapers can be created under the config>port>ethernet>egress context using the hs-secondary-shaper statement. The HS secondary shaper aggregate PIR is configured under the associated secondary shaper. A default hs-secondary-shaper is applied under each HSQ egress port with an aggregate PIR rate max, which can be configured if required. The secondary shaper PIR uses frame-based accounting (L1 rate) and is not affected by a queue packet-byte-offset parameter.

SAP egress HSQ queue groups are connected to an HS secondary shaper using the hs-secondary-shaper parameter under a queue override, which is configured under the SAP egress context. When the first egress SAP or PW-SAP is associated with a user-configured HS secondary shaper, the system instantiates a default primary shaper for that secondary shaper.

Each of the six scheduling classes can be individually shaped within an HS secondary shaper. The HS secondary shaper scheduling class PIR is configured under the associated secondary shaper. The default HS secondary shaper scheduling class PIRs are set to max and can also be modified. The secondary shaper scheduling class PIR uses frame-based accounting (L1 rate) and is not affected by a queue packet-byte-offset parameter.

A per-port aggregate shapes the traffic forwarded by its connected secondary shapers, that is, all the traffic egressing out of the physical port. It is applicable to SAP egress, network egress, and both access and network egress queue group instance traffic. A default HS scheduler policy (which is not configurable) is applied to all ports.

A user-defined HS scheduler policy can be created in which the port aggregate PIR (max-rate) can be configured and the policy then applied under the config>port>ethernet>egress context. Only a single HS scheduler policy is supported on each port. The port aggregate PIR uses frame-based accounting (L1 rate) and is not affected by a queue packet-byte-offset parameter.

An alternative to configuring a per-port aggregate is to configure an egress-rate on the port. This provides more granular control as it is configured in kb/s (whereas the per-port aggregate is in Mb/s). The HSQ egress-rate is based on the Ethernet size of the packet including the IFG (Inter-Frame-Gap) and preamble.

Each of the six scheduling classes can also be individually shaped per port by configuring a scheduling class PIR within an HS scheduler policy. The scheduling classes can also be grouped in a single WRR group at each egress port with each class being assigned a weight within the group.

The scheduling class identifiers must be contiguous within the WRR group and the group is scheduled at the scheduling class of its highest member scheduling class. Both the scheduling class PIR and the WRR group PIR are set to max in the default HS scheduler policy, with the WRR group being unused. The port scheduling class PIR uses frame-based accounting (L1 rate) and is not affected by a queue packet-byte-offset parameter.

The root pools represent the total number of available buffers that can be provisioned. Up to 16 root pools can be configured, each having an allocation weight to determine its allocation of the available buffers. A root pool with an allocation weight of zero is not allocated any buffers. Root pools cannot oversubscribe the real buffers on the IOM. The use of multiple root pools provides buffer isolation between the queues using each root pool. At least one root pool (root pool 1) must be assigned buffers by having a non-zero allocation weight.

A high watermark is maintained for the buffer usage in each root pool. A slope policy is applied to each root pool to handle congestion control, the default being the _tmnx_hs_default slope policy. Root pools are configured per FP in an hs-pool-policy applied under card>fp>egress. Root pools 1 and 2 have an allocation weight of 75 and 25, respectively, in the default hs-pool-policy, with the remaining pools having a weight of 0.

The mid pools are an abstract pool mapping mechanism. Each mid pool can be parented to a single parent root pool using its parent-root-pool parameter. Mid pools cannot be parented to a root pool without buffers and mid pools are unused if not parented to a root pool. Up to 16 mid pools are available and at least one mid pool must be parented to a root pool for its queues to buffer packets. The number of buffers in a mid pool is configured as a percentage of its parent root pool size using the allocation-percent parameter.

Mid pools can facilitate buffer isolation by being mapped to different root pools. Mapping multiple mid pools to the same root pool allows the buffers of that root pool to be shared by those child mid pools, and if the sum of the child mid pool allocation percent is greater than 100, then the root pool will be oversubscribed accordingly.

An oversubscription factor can also be applied to each mid pool (using the port-bw-oversub-factor parameter) to permit its child class pools to oversubscribe it. This does not change the size of the mid pool, but allows the mid pool size to be increased in the calculation of each of its child port class pools.

A high watermark is maintained for the buffer usage in each mid pool. A slope policy is applied to each mid pool to handle congestion control, the default being the _tmnx_hs_default slope policy. Mid pools are configured per FP egress in an hs-pool-policy applied under card>fp>egress. In the default hs-pool-policy, mid pools 1 to 4 are parented to root pool 1 with allocation percentages of 40, 35, 30, and 25; mid pools 5 and 6 are parented to root pool 2 with allocation percentages of 80 and 20; and mid pools 7 to 16 are not parented to any root pool. All mid pools have a port-bw-oversub-factor of 1.

Port class pools, as the name implies, are per-class pools that exist at the port level. There are two sets of port class pools per port: six standard port class pools and six alternative port class pools. The alternative set of port class pools enables additional flexibility for both buffer isolation and oversubscription by providing a simple mechanism to parent queues to different port class pools and, therefore, to different mid and root pools.

HSQ queue group queues are statically assigned to the port class pool associated with the scheduling class that they have been attached to (via a WRR group, if used): scheduling class 1 to port class pool 1, up to scheduling class 6 to port class pool 6. Port class pools are configured in an hs-port-pool-policy, which is applied under config>port>ethernet>egress. A default hs-port-pool-policy in which only the standard port class pools are used is applied to all HSQ ports.

Queues can be assigned to an alternative class pool (again based on the associated scheduling class) using the hs-alt-port-class-pool parameter under the queue in the SAP egress QoS policy, network queue policy, or egress queue group template.

Each port class pool parents to a single mid pool using its parent-mid-pool parameter. Port class pools are unused if not parented to a mid pool. Each port class pool must be parented to a mid pool that is parented to a root pool for queues to buffer packets. Port class pools can facilitate buffer isolation by being parented to different mid pools that are parented to different root pools. The standard port class pools are parented to their respective mid pool (port class pool 1 to mid pool 1, up to port class pool 6 to mid pool 6) in the default hs-port-pool-policy, with the alternative port class pools not parented to any mid pool.

The oversubscription of port class pools in a mid pool can be achieved by configuring the port-bw-oversub-factor under the parent mid pool (in the hs-pool-policy), which is multiplied by the size of the mid pool when calculating the size of each child class pool.

A weight is configurable per port to handle the allocation of buffers to different class pools parented to the same mid pool. This is configured using the allocation port-bw-weight under the class pool statement, where the weight configured for a port class pool is divided by the sum of the weights of the port class pools parented to the same mid pool, to determine the proportion of the allocated buffers for that port class pool. It is also possible to configure an explicit-percent for a port class pool, in which case that port class pool will be allocated the configured explicit percentage of the mid pool (without any mid pool port-bw-oversub-factor being applied).

If there are multiple port class pools parented to the same mid pool, their buffer allocation is determined using the weighting mechanism based on the port class pool allocation port-bw-weight parameter. Port class pools configured with an explicit-percent have a weight of zero (that is, they do not participate in the weighting buffer allocation). The port class pools in the default hs-port-pool-policy are configured with an allocation port-bw-weight of 1.

The port class pools are sized dynamically to provide a fair share of a mid pool size to each of its child port class pools, based on the potential bandwidth represented by each port on which the port class pools exist. The first step is to determine the usable bandwidth of each port. The mid pool buffers are then shared between its child port class pools, based on their related port usable bandwidth. An oversubscription factor is then applied to allow the port class pools to oversubscribe their mid pool. Finally, each port mid pool buffer allocation is shared between the child port class pools on that port.

No buffers are allocated to port class pools if there are no SAPs or network interfaces configured on that port and the port is shutdown. The details of the port class pool sizing calculation are as follows (examples of each are shown in the Buffer Pools configuration section):

1. Determine each port bandwidth value.

   1. This is the minimum of the port current line rate, the port egress-rate limit, and the hs-scheduler-policy max-rate configured on the port.

   2. The port bandwidth may be further modified by the port modify-buffer-allocation-rate egr-percentage-of-rate command, which can increase or decrease the port bandwidth by the specified percent. This allows the port to have a higher or lower bandwidth derived weight, based on how the port is being used, instead of bandwidth alone.

2. Determine each port portion of each mid pool.

   The port class pools are configured to map to the mid pools, so it is possible that not every port will have a port class pool associated with a mid pool. This requires that the system perform the relative bandwidth calculations separately per mid pool. A port without any port class pools associated with a mid pool will have a port portion of zero for that mid pool.

   Per mid pool, each port portion of the mid pool size is calculated based on:

   Port_Portion = (Port_Adj_Bw / Sigma_Mid_Pool_Ports_Adj_Bw) * Mid_Pool_Size

   Where:

   • Port_Adj_Bw is calculated in (1).

   • Sigma_Mid_Pool_Ports_Adj_Bw is the sum of the adjusted bandwidths for all ports, with port class pools mapped to the mid pool that are not sized configured with explicit-percent (see (4)).

   • Mid_Pool_Size is the mid pool parent root pool size multiplied by the mid pool allocation weight.

3. Modify the mid pool sizes by their port-bw-oversub-factor.

   The port bandwidth weighting mechanism allocates 100% of the mid pool size to the associated port class pools. To allow the port class pools to oversubscribe their parent mid pool, the mid pool port-bw-oversub-factor parameter can be used to increase the apparent size of the mid pool (this does not change the mid pool size) in the calculation in (2). This potentially provides a more efficient use of the mid pool available buffers since it is not expected that all port class pools will be using their allotted size simultaneously.

4. Determine each port class pool share of the mid pool port share.

   Multiple port class pools on the same port may be mapped to the same mid pool. This requires a mechanism to distribute the portion of the mid pool allocated to each port class pool on that port.

   Each port class pool allocation port-bw-weight parameter is used to determine how much of the port mid pool is given to each port class pool associated with the mid pool. A port class pool is allocated the portion of its mid pool size multiplied by its port class pool port-bw-weight divided by the sum of the port-bw-weight for all port class pools associated with that mid pool on that port.

   Alternatively, port class pools can be sized using an explicit-percent of the actual mid pool size (without applying the port-bw-oversub-factor). These class pools are assigned a port-bw-weight equal to zero, causing them to be excluded from the port portion distribution. It is expected (but not required) that either port bandwidth-based sizing or explicit percent-based sizing will be used, with concurrent use of both mechanisms being transitory in nature.

Whenever one of the inputs to the preceding calculations changes, the bandwidth weighted sizes for the corresponding pool class pools are recalculated.

A high watermark is maintained for the buffer usage in each port class pool. A slope policy is applied to each port class pool to handle congestion control, the default being the _tmnx_hs_default slope policy.

HSQ queue group queues always operate in WRED per queue mode, supporting three WRED slopes. The total number of buffers usable by the queue is limited by the queue MBS configuration, and each packet profile type (exceed, out, in) is limited by the respective slope configuration (exceed, low, high) in the applied slope policy, if the slope is not shutdown. For a buffer to be allocated, the applicable WRED slope processing (if enabled) must accept the packet, the MBS must not be exceeded, and there must be available buffers in its parent port class pool, mid pool, and root pool.

The regular mbs queue parameter configuration is used within SAP egress QoS policies and egress queue group templates, using the regular defaults. In the network queue policy, the MBS is configured using the hs-mbs parameter, which allows a different default to be used, with its value calculated based on a percentage of one second of the queue PIR converted to bytes (the regular mbs parameter is ignored in the network queue policy). The queue CBS and drop tail configuration is ignored on an HSQ queue group queue.

A default slope (named _tmnx_hs_default) is applied to each HSQ queue, using the policy parameter on the hs-wred-queue statement within a SAP egress QoS policy, network queue policy, and egress queue group template. A user-configured regular slope policy can be applied using the same parameter and statement. The highplus-slope and time-average-factor in the applied slope policy are ignored on HSQ queue group queues.

The HSQ root and mid pools for an IOM are configured in an HS pool policy, which is applied under card>fp>egress.

An HS pool policy is configured as follows:

configure
    qos
        hs-pool-policy <policy-name> [create]
            description <description-string>
            mid-tier
                mid-pool <mid-pool-id>
                    allocation-percent <percent-of-parent-pool>
                    parent-root-pool <root-pool-id>
                    port-bw-oversub-factor <oversubscription-factor>
                    slope-policy <policy-name>
            root-tier
                root-pool <root-pool-id>
                    allocation-weight <pool-weight>
                    slope-policy <policy-name>
            system-reserve <percent-of-buffers>

Where (in order):

<policy-name>        : [32 chars max]
<description-string> : [80 chars max]
<mid-pool-id>        : [1..16]
<percent-of-parent*> : [0.01..100.00]
<root-pool-id>       : [1..16]
<oversubscription-*> : [1..10]
<policy-name>        : [32 chars max]
<root-pool-id>       : [1..16 | none]
<pool-weight>        : [0..100]
<policy-name>        : [32 chars max]
<percent-of-buffers> : [1.00..30.00]

A default HS pool policy is created by the system with the following configuration:

If a new HS pool policy is created, its initial configuration is as follows:

The HS pool policy (hs-pool-pol-1) used for this example is shown following. Root pool 1 and mid pool 1 have been reserved for network protocol traffic and are not used. Root pool 2 and mid pool 2 are used for queue 7 traffic, root pool 3 and mid pool 3 are used for queue 6 traffic, and root pool 4 and mid pool 4 are used for queue 1 and queue 2 (WRR group 1) traffic. The buffer allocation for each pool is based on the expected traffic volumes.

Root pool 4 and mid pool 4 have a more aggressive slope policy (hs-slope-1) than the default HSQ slope policy (_tmnx_hs_default). The default HSQ slope policy is as follows (the HSQ slopes use the instantaneous queue depth so the time-average-factor is ignored and the highplus-slope is also ignored):

*A:PE-1>config>qos# slope-policy "_tmnx_hs_default"
*A:PE-1>config>qos>slope-policy# info detail
----------------------------------------------
            description "Default HS slope policy."
            highplus-slope
                shutdown
                start-avg 100
                max-avg 100
                max-prob 100
            exit
            high-slope
                start-avg 100
                max-avg 100
                max-prob 100
                no shutdown
            exit
            low-slope
                start-avg 90
                max-avg 90
                max-prob 100
                no shutdown
            exit
            exceed-slope
                start-avg 80
                max-avg 80
                max-prob 100
                no shutdown
            exit
            time-average-factor 7

The slope policy hs-slope-1 is configured as follows:

A:PE-1>config>qos# slope-policy "hs-slope-1"
A:PE-1>config>qos>slope-policy# info
----------------------------------------------
            highplus-slope
                shutdown
            exit
            high-slope
                start-avg 85
                max-avg 100
                no shutdown
            exit
            low-slope
                no shutdown
            exit
            exceed-slope
                shutdown
            exit

Mid pool 4 has been configured to allow a 4 times oversubscription by its child class pools.

Root pools 5 to 16 and mid pools 5 to 16 are unused.

HS pool policy hs-pool-pol-1 is summarized as follows:

The HS pool policy hs-pool-pol-1 is configured as follows:

A:PE-1>config>qos>hs-pool-policy# info
----------------------------------------------
            root-tier
                root-pool 1
                    allocation-weight 5
                exit
                root-pool 2
                    allocation-weight 10
                exit
                root-pool 3
                    allocation-weight 20
                exit
                root-pool 4
                    allocation-weight 65
                    slope-policy "hs-slope-1"
                exit
            exit
            mid-tier
                mid-pool 1
                    allocation-percent 100.00
                exit
                mid-pool 2
                    parent-root-pool 2
                    allocation-percent 100.00
                exit
                mid-pool 3
                    parent-root-pool 3
                    allocation-percent 100.00
                exit
                mid-pool 4
                    parent-root-pool 4
                    allocation-percent 100.00
                    port-bw-oversub-factor 4
                    slope-policy "hs-slope-1"
                exit
                mid-pool 5
                    parent-root-pool none
                exit
                mid-pool 6
                    parent-root-pool none
                exit
                mid-pool 7
                    parent-root-pool none
                exit
                mid-pool 8
                    parent-root-pool none
                exit
                mid-pool 9
                    parent-root-pool none
                exit
                mid-pool 10
                    parent-root-pool none
                exit
                mid-pool 11
                    parent-root-pool none
                exit
                mid-pool 12
                    parent-root-pool none
                exit
                mid-pool 13
                    parent-root-pool none
                exit
                mid-pool 14
                    parent-root-pool none
                exit
                mid-pool 15
                    parent-root-pool none
                exit
                mid-pool 16
                    parent-root-pool none
                exit
            exit

The HS pool policy is shown as follows:

*A:PE-1# show qos hs-pool-policy "hs-pool-pol-1"

===============================================================================
HS Pool Policy Information
===============================================================================
Policy Name             : hs-pool-pol-1
Description             : (Not Specified)
System Reserve          : 5.00

-------------------------------------------------------------------------------
Root Pool Information
-------------------------------------------------------------------------------
Pool Id                 : 1             Allocation Weight   : 5
Slope Policy            : _tmnx_hs_default

Pool Id                 : 2             Allocation Weight   : 10
Slope Policy            : _tmnx_hs_default

Pool Id                 : 3             Allocation Weight   : 20
Slope Policy            : _tmnx_hs_default

Pool Id                 : 4             Allocation Weight   : 65
Slope Policy            : hs-slope-1

Pool Id                 : 5             Allocation Weight   : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 6             Allocation Weight   : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 7             Allocation Weight   : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 8             Allocation Weight   : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 9             Allocation Weight   : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 10            Allocation Weight   : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 11            Allocation Weight   : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 12            Allocation Weight   : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 13            Allocation Weight   : 0
Slope Policy            : _tmnx_hs_default
Pool Id                 : 14            Alloc
ation Weight   : 0
Slope Policy            : _tmnx_hs_default
Pool Id                 : 15            Allocation Weight   : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 16            Allocation Weight   : 0
Slope Policy            : _tmnx_hs_default

-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
Mid Pool Information
-------------------------------------------------------------------------------
Pool Id                 : 1             Allocation Percent  : 100.00
Port BW Oversub Factor  : 1             Parent Root Pool    : 1
Slope Policy            : _tmnx_hs_default

Pool Id                 : 2             Allocation Percent  : 100.00
Port BW Oversub Factor  : 1             Parent Root Pool    : 2
Slope Policy            : _tmnx_hs_default

Pool Id                 : 3             Allocation Percent  : 100.00
Port BW Oversub Factor  : 1             Parent Root Pool    : 3
Slope Policy            : _tmnx_hs_default

Pool Id                 : 4             Allocation Percent  : 100.00
Port BW Oversub Factor  : 4             Parent Root Pool    : 4
Slope Policy            : hs-slope-1

Pool Id                 : 5             Allocation Percent  : 1.00
Port BW Oversub Factor  : 1             Parent Root Pool    : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 6             Allocation Percent  : 1.00
Port BW Oversub Factor  : 1             Parent Root Pool    : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 7             Allocation Percent  : 1.00
Port BW Oversub Factor  : 1             Parent Root Pool    : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 8             Allocation Percent  : 1.00
Port BW Oversub Factor  : 1             Parent Root Pool    : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 9             Allocation Percent  : 1.00
Port BW Oversub Factor  : 1             Parent Root Pool    : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 10            Allocation Percent  : 1.00
Port BW Oversub Factor  : 1             Parent Root Pool    : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 11            Allocation Percent  : 1.00
Port BW Oversub Factor  : 1             Parent Root Pool    : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 12            Allocation Percent  : 1.00
Port BW Oversub Factor  : 1             Parent Root Pool    : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 13            Allocation Percent  : 1.00
Port BW Oversub Factor  : 1             Parent Root Pool    : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 14            Allocation Percent  : 1.00
Port BW Oversub Factor  : 1             Parent Root Pool    : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 15            Allocation Percent  : 1.00
Port BW Oversub Factor  : 1             Parent Root Pool    : 0
Slope Policy            : _tmnx_hs_default

Pool Id                 : 16            Allocation Percent  : 1.00
Port BW Oversub Factor  : 1             Parent Root Pool    : 0
Slope Policy            : _tmnx_hs_default

-------------------------------------------------------------------------------
===============================================================================
*A:PE-1#

This HS pool policy is configured for the HSQ IOM as follows:

A:PE-1# configure card 3
A:PE-1>config>card# info
----------------------------------------------
        card-type iom4-e-hs
        fp 1
            egress
                hs-pool-policy "hs-pool-pol-1"
            exit
        exit
        no shutdown
----------------------------------------------
A:PE-1>config>card#

The association of this HS pool policy is shown as follows:

*A:PE-1# show qos hs-pool-policy "hs-pool-pol-1" association

===============================================================================
HS Pool Policy Information
===============================================================================
Policy Name             : hs-pool-pol-1
Description             : (Not Specified)
System Reserve          : 5.00

-------------------------------------------------------------------------------
Card Forwarding Plane (FP) Associations
-------------------------------------------------------------------------------
Card                FP
-------------------------------------------------------------------------------
3                   1
-------------------------------------------------------------------------------
===============================================================================
*A:PE-1#

The resulting system and user-provisioned pool information is shown following. This output shows the total buffer allocation, number of allocated buffers, available buffer allocation, and buffer high watermarks for the system pools and user-provisioned pools. The output shows the hierarchy of the root and mid pools, with their applied slope policy and the related instantaneous slope drop probabilities (as a percentage):

*A:PE-1# show hs-pools 3 fp 1 egress

===============================================================================
HS Pools Card Forwarding Plane Information
===============================================================================
Card               : 3                  FP                 : 1

-------------------------------------------------------------------------------
System Pool Information
-------------------------------------------------------------------------------

Total Buffers      : 209412 KB          Allocated          : 0 KB
Available          : 209412 KB          High Water Mark    : 0 KB

-------------------------------------------------------------------------------
Buffer Pool Hierarchy Information
-------------------------------------------------------------------------------

Root Pool : 1
|  Total               : 198942 KB   Allocated         : 0 KB
|  Available           : 198942 KB   High Water Mark   : 0 KB
|  Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|  Excd-Slope Drop Prob: 0
|  Hs Slope Policy     : _tmnx_hs_default
|
|--- Mid Pool : 1
|     | Total               : 198942 KB   Allocated         : 0 KB
|     | Available           : 198942 KB   High Water Mark   : 0 KB
|     | Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|     | Excd-Slope Drop Prob: 0
|     | Hs Slope Policy     : _tmnx_hs_default
|     |
Root Pool : 2
|  Total               : 397886 KB   Allocated         : 0 KB
|  Available           : 397886 KB   High Water Mark   : 0 KB
|  Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|  Excd-Slope Drop Prob: 0
|  Hs Slope Policy     : _tmnx_hs_default
|
|--- Mid Pool : 2
|     | Total               : 397886 KB   Allocated         : 0 KB
|     | Available           : 397886 KB   High Water Mark   : 0 KB
|     | Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|     | Excd-Slope Drop Prob: 0
|     | Hs Slope Policy     : _tmnx_hs_default
|     |
Root Pool : 3
|  Total               : 795772 KB   Allocated         : 0 KB
|  Available           : 795772 KB   High Water Mark   : 0 KB
|  Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|  Excd-Slope Drop Prob: 0
|  Hs Slope Policy     : _tmnx_hs_default
|
|--- Mid Pool : 3
|     | Total               : 795772 KB   Allocated         : 0 KB
|     | Available           : 795772 KB   High Water Mark   : 0 KB
|     | Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|     | Excd-Slope Drop Prob: 0
|     | Hs Slope Policy     : _tmnx_hs_default
|     |
Root Pool : 4
|  Total               : 2586262 KB  Allocated         : 0 KB
|  Available           : 2586262 KB  High Water Mark   : 0 KB
|  Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|  Excd-Slope Drop Prob: 0
|  Hs Slope Policy     : hs-slope-1
|
|--- Mid Pool : 4
|     | Total               : 2586262 KB  Allocated         : 0 KB
|     | Available           : 2586262 KB  High Water Mark   : 0 KB
|     | Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|     | Excd-Slope Drop Prob: 0
|     | Hs Slope Policy     : hs-slope-1
|     |

The HSQ port class pools for a port are configured in an HS port pool policy, which is applied under config>port>ethernet>egress.

An HS port pool policy is configured as follows:

configure
    qos
        hs-port-pool-policy <policy-name> [create]
            description <description-string>
            std-port-class-pools
                class-pool <std-class-pool-id>
                    allocation explicit-percent <percent-of-parent-pool>
                    allocation port-bw-weight <pool-weight>
                    parent-mid-pool <mid-pool-id>
                    slope-policy <policy-name>
            alt-port-class-pools
                class-pool <alt-class-pool-id>
                    allocation explicit-percent <percent-of-parent-pool>
                    allocation port-bw-weight <pool-weight>
                    parent-mid-pool <mid-pool-id>
                    slope-policy <policy-name>

Where (in order):

<policy-name>        : [32 chars max]
<description-string> : [80 chars max]
<std-class-pool-id>  : [1..6]
<percent-of-parent*> : [0.01..100.00]
<pool-weight>        : [1..100]
<mid-pool-id>        : [1..16 | none]
<policy-name>        : [32 chars max]
<alt-class-pool-id>  : [1..6]
<percent-of-parent*> : [0.01..100.00]
<pool-weight>        : [1..100]
<mid-pool-id>        : [1..16 | none]
<policy-name>        : [32 chars max]

A default HS pool policy is created by the system with the following configuration:

Newly created HS port pool policies have the following parameters:

The HS port pool policy used for traffic in this example is shown following. Only port class pools 1, 4, 5, and 6 are used, which are parented to mid pools 4, 3, 2, and 1, respectively. As scheduling classes 2 and 3 are unused, their associated standard port class pools are not parented to a mid pool. The alternative port class pools are also unused, so are not parented to a mid pool. Standard port class pools 4 to 6 use the default HSQ slope policy with standard port class pool 1 using slope policy hs-slope-1.

The HS port pool policy is configured as follows:

*A:PE-1>config>qos# hs-port-pool-policy "hs-port-pool-pol-1"
*A:PE-1>config>qos>hs-port-pool-policy# info
----------------------------------------------
            std-port-class-pools
                class-pool 1
                    parent-mid-pool 4
                    slope-policy "hs-slope-1"
                exit
                class-pool 2
                    parent-mid-pool none
                exit
                class-pool 3
                    parent-mid-pool none
                exit
                class-pool 4
                    parent-mid-pool 3
                exit
                class-pool 5
                    parent-mid-pool 2
                exit
            exit

The HS port pool policy is shown as follows:

*A:PE-1# show qos hs-port-pool-policy "hs-port-pool-pol-1"

===============================================================================
HS Port Pool Policy Information
===============================================================================
Policy Name             : hs-port-pool-pol-1
Description             : (Not Specified)

-------------------------------------------------------------------------------
Standard Port Class Pool Information
-------------------------------------------------------------------------------
Class Id                : 1             Parent Mid Pool     : 4
Alloc Port BW Weight    : 1             Alloc Explicit Prcnt: 0.00
Slope Policy            : hs-slope-1

Class Id                : 2             Parent Mid Pool     : 0
Alloc Port BW Weight    : 1             Alloc Explicit Prcnt: 0.00
Slope Policy            : _tmnx_hs_default

Class Id                : 3             Parent Mid Pool     : 0
Alloc Port BW Weight    : 1             Alloc Explicit Prcnt: 0.00
Slope Policy            : _tmnx_hs_default

Class Id                : 4             Parent Mid Pool     : 3
Alloc Port BW Weight    : 1             Alloc Explicit Prcnt: 0.00
Slope Policy            : _tmnx_hs_default

Class Id                : 5             Parent Mid Pool     : 2
Alloc Port BW Weight    : 1             Alloc Explicit Prcnt: 0.00
Slope Policy            : _tmnx_hs_default

Class Id                : 6             Parent Mid Pool     : 1
Alloc Port BW Weight    : 1             Alloc Explicit Prcnt: 0.00
Slope Policy            : _tmnx_hs_default

-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
Alternate Port Class Pool Information
-------------------------------------------------------------------------------
Class Id                : 1             Parent Mid Pool     : 0
Alloc Port BW Weight    : 1             Alloc Explicit Prcnt: 0.00
Slope Policy            : _tmnx_hs_default

Class Id                : 2             Parent Mid Pool     : 0
Alloc Port BW Weight    : 1             Alloc Explicit Prcnt: 0.00
Slope Policy            : _tmnx_hs_default

Class Id                : 3             Parent Mid Pool     : 0
Alloc Port BW Weight    : 1             Alloc Explicit Prcnt: 0.00
Slope Policy            : _tmnx_hs_default

Class Id                : 4             Parent Mid Pool     : 0
Alloc Port BW Weight    : 1             Alloc Explicit Prcnt: 0.00
Slope Policy            : _tmnx_hs_default

Class Id                : 5             Parent Mid Pool     : 0
Alloc Port BW Weight    : 1             Alloc Explicit Prcnt: 0.00
Slope Policy            : _tmnx_hs_default

Class Id                : 6             Parent Mid Pool     : 0
Alloc Port BW Weight    : 1             Alloc Explicit Prcnt: 0.00
Slope Policy            : _tmnx_hs_default

-------------------------------------------------------------------------------
===============================================================================
*A:PE-1#

The preceding HS port pool policy applied to ports 3/1/1 and 3/1/2 is shown as follows:

*A:PE-1# show qos hs-port-pool-policy "hs-port-pool-pol-1" association

===============================================================================
HS Port Pool Policy Information
===============================================================================
Policy Name             : hs-port-pool-pol-1
Description             : (Not Specified)

-------------------------------------------------------------------------------
Port Ethernet Egress Associations
-------------------------------------------------------------------------------
3/1/1
3/1/2
-------------------------------------------------------------------------------
===============================================================================
*A:PE-1#

The remaining ports (3/1/[3..10]) are unused in this example, so their port class pools are not parented, by applying the following HS port pool policy to each:

*A:PE-1>config>qos# hs-port-pool-policy "no-class-pools"
*A:PE-1>config>qos>hs-port-pool-policy# info
----------------------------------------------
            std-port-class-pools
                class-pool 1
                    parent-mid-pool none
                exit
                class-pool 2
                    parent-mid-pool none
                exit
                class-pool 3
                    parent-mid-pool none
                exit
                class-pool 4
                    parent-mid-pool none
                exit
                class-pool 5
                    parent-mid-pool none
                exit
                class-pool 6
                    parent-mid-pool none
                exit
            exit

The HS port pool policies applied to the ports on card 3 are configured as follows:

configure
    port 3/1/1
        ethernet
            egress
                hs-port-pool-policy "hs-port-pool-pol-1"
    port 3/1/2
        ethernet
            egress
                hs-port-pool-policy "hs-port-pool-pol-1"
    port 3/1/[3..10]
        ethernet
            egress
                hs-port-pool-policy "no-class-pools"

The pools created on port 3/1/1, after applying the preceding HS pool policy and HS port pool policies, are shown following. The root and mid pools in this output are the same as in the show hs-pools 3 fp 1 egress output; these pools are configured per FP so are the same for all ports. The additional information shows the details of the port class pools on this port and to which mid pools they are parented:

*A:PE-1# show hs-pools port 3/1/1 egress

===============================================================================
HS Pools Port Information
===============================================================================
Port               : 3/1/1

-------------------------------------------------------------------------------
System Pool Information
-------------------------------------------------------------------------------

Total Buffers      : 209412 KB          Allocated          : 0 KB
Available          : 209412 KB          High Water Mark    : 0 KB

-------------------------------------------------------------------------------
Buffer Pool Hierarchy Information
-------------------------------------------------------------------------------

Root Pool : 1
|  Total               : 198942 KB   Allocated         : 0 KB
|  Available           : 198942 KB   High Water Mark   : 0 KB
|  Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|  Excd-Slope Drop Prob: 0
|  Hs Slope Policy     : _tmnx_hs_default
|
|--- Mid Pool : 1
|     | Total               : 198942 KB   Allocated         : 0 KB
|     | Available           : 198942 KB   High Water Mark   : 0 KB
|     | Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|     | Excd-Slope Drop Prob: 0
|     | Hs Slope Policy     : _tmnx_hs_default
|     |
|     |--- Std Port Class Pool : 6
|     |      Total               : 99470 KB    Allocated         : 0 KB
|     |      Available           : 99470 KB    High Water Mark   : 0 KB
|     |      Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|     |      Excd-Slope Drop Prob: 0
|     |      Hs Slope Policy     : _tmnx_hs_default
|     |
Root Pool : 2
|  Total               : 397886 KB   Allocated         : 0 KB
|  Available           : 397886 KB   High Water Mark   : 0 KB
|  Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|  Excd-Slope Drop Prob: 0
|  Hs Slope Policy     : _tmnx_hs_default
|
|--- Mid Pool : 2
|     | Total               : 397886 KB   Allocated         : 0 KB
|     | Available           : 397886 KB   High Water Mark   : 0 KB
|     | Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|     | Excd-Slope Drop Prob: 0
|     | Hs Slope Policy     : _tmnx_hs_default
|     |
|     |--- Std Port Class Pool : 5
|     |      Total               : 198942 KB   Allocated         : 0 KB
|     |      Available           : 198942 KB   High Water Mark   : 0 KB
|     |      Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|     |      Excd-Slope Drop Prob: 0
|     |      Hs Slope Policy     : _tmnx_hs_default
|     |
Root Pool : 3
|  Total               : 795772 KB   Allocated         : 0 KB
|  Available           : 795772 KB   High Water Mark   : 0 KB
|  Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|  Excd-Slope Drop Prob: 0
|  Hs Slope Policy     : _tmnx_hs_default
|
|--- Mid Pool : 3
|     | Total               : 795772 KB   Allocated         : 0 KB
|     | Available           : 795772 KB   High Water Mark   : 0 KB
|     | Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|     | Excd-Slope Drop Prob: 0
|     | Hs Slope Policy     : _tmnx_hs_default
|     |
|     |--- Std Port Class Pool : 4
|     |      Total               : 397886 KB   Allocated         : 0 KB
|     |      Available           : 397886 KB   High Water Mark   : 0 KB
|     |      Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|     |      Excd-Slope Drop Prob: 0
|     |      Hs Slope Policy     : _tmnx_hs_default
|     |
Root Pool : 4
|  Total               : 2586262 KB  Allocated         : 0 KB
|  Available           : 2586262 KB  High Water Mark   : 0 KB
|  Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|  Excd-Slope Drop Prob: 0
|  Hs Slope Policy     : hs-slope-1
|
|--- Mid Pool : 4
|     | Total               : 2586262 KB  Allocated         : 0 KB
|     | Available           : 2586262 KB  High Water Mark   : 0 KB
|     | Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|     | Excd-Slope Drop Prob: 0
|     | Hs Slope Policy     : hs-slope-1
|     |
|     |--- Std Port Class Pool : 1
|     |      Total               : 4194302 KB  Allocated         : 0 KB
|     |      Available           : 4194302 KB  High Water Mark   : 0 KB
|     |      Hi-Slope Drop Prob  : 0           Lo-Slope Drop Prob: 0
|     |      Excd-Slope Drop Prob: 0
|     |      Hs Slope Policy     : hs-slope-1
|     |

The following show commands are available to display the pool configuration and queue details:

show hs-pools port <port-id> egress
show hs-pools port <port-id> egress network-queues
show hs-pools port <port-id> egress queue-group <queue-group-name> 
                             [instance <instance-id>]
show hs-pools port <port-id> egress sap <sap-id>
show hs-pools port <port-id> egress subscriber <sub-ident-string>

The root and mid pool information in each command is the same as in the command show hs-pools <card-slot-number> fp <forwarding-plane> egress but the commands also show the port class pool information on the specified port, together with the queue information for that port.

The logic to size the root, mid, and port class pools is described in the Buffer Management section.

Root pools are sized using their allocation-weight parameter, which is divided by the sum of all root pool allocation-weight to give the portion of the total user-provisioned buffers allocated to the root pool.

The mid pools are sized using their allocation-percent parameter, which is a percentage of their parent root pool size.

The port class pools size calculation has more factors. The following output shows the effect of the different sizing parameters on the port class pools size. The steps are:

• An HS pool policy and HS port pool policies are applied to an HSQ IOM and its ports to configure one root pool with one child mid pool that has one child standard port class pool on port 3/1/1. Each pool has the same size matching the total available buffers:

  *A:PE-1# show hs-pools port 3/1/1 egress | 
                match "Root Pool : 1" post-lines 26 | match "Pool" post-lines 1
  Root Pool : 1
  |  Total               : 3978866 KB  Allocated         : 0 KB
  |--- Mid Pool : 1
  |     | Total               : 3978866 KB  Allocated         : 0 KB
  |     |--- Std Port Class Pool : 1
  |     |      Total               : 3978866 KB  Allocated         : 0 KB
  

• A standard port class pool is added to port 3/1/2, causing the mid pool size to be shared between port class pool 1 on port 3/1/1 and 3/1/2:

  *A:PE-1# configure port 3/1/2 ethernet egress 
                                 hs-port-pool-policy "hs-port-pool-policy-test"
  *A:PE-1# show hs-pools port 3/1/1 egress | 
                match "Root Pool : 1" post-lines 26 | match "Pool" post-lines 1
  Root Pool : 1
  |  Total               : 3978866 KB  Allocated         : 0 KB
  |--- Mid Pool : 1
  |     | Total               : 3978866 KB  Allocated         : 0 KB
  |     |--- Std Port Class Pool : 1
  |     |      Total               : 1989432 KB  Allocated         : 0 KB
  *A:PE-1# show hs-pools port 3/1/2 egress | match "Root Pool : 1" post-lines 26 | match "Pool" post-lines 1
  Root Pool : 1
  |  Total               : 3978866 KB  Allocated         : 0 KB
  |--- Mid Pool : 1
  |     | Total               : 3978866 KB  Allocated         : 0 KB
  |     |--- Std Port Class Pool : 1
  |     |      Total               : 1989432 KB  Allocated         : 0 KB
  

• The egress rate is set on port 3/1/1 (which is a 10 Gb/s port) to 5 Gb/s. This reduces the size of the port class pools on port 3/1/1 to one-third of the mid pool size and increases the size of the port class pools on port 3/1/2 to two-thirds of the mid pool size, after which the egress rate is removed:

  *A:PE-1# configure port 3/1/1 ethernet egress-rate 5000000
  *A:PE-1# show hs-pools port 3/1/1 egress | 
                match "Root Pool : 1" post-lines 26 | match "Pool" post-lines 1
  Root Pool : 1
  |  Total               : 3978866 KB  Allocated         : 0 KB
  |--- Mid Pool : 1
  |     | Total               : 3978866 KB  Allocated         : 0 KB
  |     |--- Std Port Class Pool : 1
  |     |      Total               : 1326288 KB  Allocated         : 0 KB
  *A:PE-1# show hs-pools port 3/1/2 egress | 
                match "Root Pool : 1" post-lines 26 | match "Pool" post-lines 1
  Root Pool : 1
  |  Total               : 3978866 KB  Allocated         : 0 KB
  |--- Mid Pool : 1
  |     | Total               : 3978866 KB  Allocated         : 0 KB
  |     |--- Std Port Class Pool : 1
  |     |      Total               : 2652576 KB  Allocated         : 0 KB
  *A:PE-1# configure port 3/1/1 ethernet no egress-rate
  

• The egr-percentage-of-rate is set to 200% on port 3/1/1 to increase its port class pool to two-thirds of the mid pools size and reduce the port class pool on port 3/1/2 to one-third of the mid pools size, after which the egr-percentage-of-rate is removed:

  *A:PE-1# configure port 3/1/1 modify-buffer-allocation-rate egr-percentage-of-rate 200
  *A:PE-1# show hs-pools port 3/1/1 egress | 
                match "Root Pool : 1" post-lines 26 | match "Pool" post-lines 1
  Root Pool : 1
  |  Total               : 3978866 KB  Allocated         : 0 KB
  |--- Mid Pool : 1
  |     | Total               : 3978866 KB  Allocated         : 0 KB
  |     |--- Std Port Class Pool : 1
  |     |      Total               : 2652576 KB  Allocated         : 0 KB
  *A:PE-1# show hs-pools port 3/1/2 egress | 
                match "Root Pool : 1" post-lines 26 | match "Pool" post-lines 1
  Root Pool : 1
  |  Total               : 3978866 KB  Allocated         : 0 KB
  |--- Mid Pool : 1
  |     | Total               : 3978866 KB  Allocated         : 0 KB
  |     |--- Std Port Class Pool : 1
  |     |      Total               : 1326288 KB  Allocated         : 0 KB
  *A:PE-1# configure port 3/1/1 modify-buffer-allocation-rate 
                                no egr-percentage-of-rate
  

• Standard port class pool 2 is parented to the mid pool with a port-bw-weight set to 2. The port-bw-weight of port class pool 1 is the default of 1. This causes this port mid pool size to be shared in a 1:2 ratio between port class pool 1 and 2 on both ports 3/1/1 and 3/1/2 (only port 3/1/1 is shown). The total port class pool size is shown in the second step preceding, that is, 1989432 kbytes.

  *A:PE-1# configure qos hs-port-pool-policy "hs-port-pool-policy-test"
  *A:PE-1>config>qos>hs-port-pool-policy# std-port-class-pools 
                                                class-pool 2 parent-mid-pool 1
  *A:PE-1>config>qos>hs-port-pool-policy# std-port-class-pools 
                                      class-pool 2 allocation port-bw-weight 2
  *A:PE-1>config>qos>hs-port-pool-policy# exit all
  *A:PE-1# show hs-pools port 3/1/1 egress | 
                match "Root Pool : 1" post-lines 47 | match "Pool" post-lines 1
  Root Pool : 1
  |  Total               : 3978866 KB  Allocated         : 0 KB
  |--- Mid Pool : 1
  |     | Total               : 3978866 KB  Allocated         : 0 KB
  |     |--- Std Port Class Pool : 1
  |     |      Total               : 663144 KB   Allocated         : 0 KB
  |     |--- Std Port Class Pool : 2
  |     |      Total               : 1326288 KB  Allocated         : 0 KB
  

• "The two port class pools 1 and 2 on port 3/1/1 are modified to use an explicit-percent of 40% and 60%, respectively:

  *A:PE-1# configure qos hs-port-pool-policy "hs-port-pool-policy-test"
  *A:PE-1>config>qos>hs-port-pool-policy# std-port-class-pools 
                                    class-pool 1 allocation explicit-percent 40
  *A:PE-1>config>qos>hs-port-pool-policy# std-port-class-pools 
                                    class-pool 2 allocation explicit-percent 60
  *A:PE-1>config>qos>hs-port-pool-policy# exit all
  *A:PE-1# show hs-pools port 3/1/1 egress | 
                match "Root Pool : 1" post-lines 47 | match "Pool" post-lines 1
  Root Pool : 1
  |  Total               : 3978866 KB  Allocated         : 0 KB
  |--- Mid Pool : 1
  |     | Total               : 3978866 KB  Allocated         : 0 KB
  |     |--- Std Port Class Pool : 1
  |     |      Total               : 1591546 KB  Allocated         : 0 KB
  |     |--- Std Port Class Pool : 2
  |     |      Total               : 2387318 KB  Allocated         : 0 KB 
  

To assist with sizing the buffer pools, each pool has a high watermark, which can be displayed using the show hs-pools command and cleared using the following commands:

clear card <slot-number> fp <[1..2]> hs-pool high-water-mark
clear card <slot-number> fp <[1..2]> hs-pool high-water-mark mid-pool <[1..16]>
clear card <slot-number> fp <[1..2]> hs-pool high-water-mark root-pool <[1..16]>
clear card <slot-number> fp <[1..2]> hs-pool high-water-mark system
clear port <port-id> hs-pool high-water-mark 
                                      { [standard <1..6>] | [alternate <1..6>] }

The HSQ ingress and non-HSQ egress line cards support a stable-pool-sizing command under card>fp, which avoids pool sizes changing when MDAs and ports are configured.

An equivalent effect can be achieved at the egress of an HSQ by creating two sets of root pools and two sets of mid pools in the hs-pool-policy applied to the IOM under card>fp>egress. The first set of mid pools parent to the first set of root pools and the second set of mid pools parent to the second set of root pools. Then create two hs-port-pool-policies: one applied to the ports on the first MDA with its port class pools parented to the first set of mid pools and the other applied to the ports on the second MDA with its port class pools parented to the second set of mid pools. This provides deterministic pool sizing independent of MDAs being inserted or removed.

Further control at the port class level can be obtained by using port class pool explicit-percent based sizing to eliminate the effect of changing port states, including bandwidth changes.

The root pools cannot oversubscribe the user-provisioned buffers, but the mid pools can oversubscribe their root pool and the port class pools can oversubscribe their mid pool.

The following configuration and output shows the oversubscription possibilities.

The default HS pool policy is applied to the HSQ IOM, so root pools 1 and 2 are allocated 75% and 25% of the user-provisioned buffers:

*A:PE-1>config>qos>hs-pool-policy# info detail |
                      match expression " root-pool 1$| root-pool 2$" post-lines 1
                root-pool 1
                    allocation-weight 75
                root-pool 2
                    allocation-weight 25

*A:PE-1# show hs-pools 3 fp 1 egress | match "Root Pool" post-lines 1
Root Pool : 1
|  Total               : 2984148 KB  Allocated         : 0 KB
Root Pool : 2
|  Total               : 994716 KB   Allocated         : 0 KB

If a new HS pool policy is applied to this IOM, only one root pool is allocated buffers with an allocation weight of 100:

*A:PE-1>config>qos>hs-pool-policy$ info detail | 
                      match expression " root-pool 1$" post-lines 1
                root-pool 1
                    allocation-weight 100

*A:PE-1# show hs-pools port 3/1/1 egress | match "Root Pool : 1" post-lines 1
Root Pool : 1
|  Total               : 3978866 KB  Allocated         : 0 KB

Root pool 16 is configured with the same allocation weight of 100, causing the two root pools to share the available user-provisioned buffers:

*A:PE-1>config>qos>hs-pool-policy# info detail | 
                      match expression " root-pool 1$| root-pool 16$" post-lines 1
                root-pool 1
                    allocation-weight 100
                root-pool 16
                    allocation-weight 100

*A:PE-1# show hs-pools port 3/1/1 egress | match "Root Pool : 1" post-lines 1
Root Pool : 1
|  Total               : 1989432 KB  Allocated         : 0 KB
Root Pool : 16
|  Total               : 1989432 KB  Allocated         : 0 KB

Mid pool 16 is parented to root pool 16 with an allocation percent of 100, so it has the same number of allocated buffers as root pool 16:

*A:PE-1>config>qos>hs-pool-policy# info detail | 
      match expression " root-pool 16$| mid-pool 16$" post-lines 2 | 
      match invert-match slope
                root-pool 16
                    allocation-weight 100
                mid-pool 16
                    parent-root-pool 16
                    allocation-percent 100.00

*A:PE-1# show hs-pools port 3/1/1 egress | 
               match "Root Pool : 16" post-lines 19 | match "Pool" post-lines 1
Root Pool : 16
|  Total               : 1989432 KB  Allocated         : 0 KB
|--- Mid Pool : 16
|     | Total               : 1989432 KB  Allocated         : 0 KB

Mid pool 15 is also parented to root pool 16 with an allocation percent of 100, causing both mid pools 15 and 16 to have the same number of allocated buffers as root pool 16; therefore, the root pool is oversubscribed two times:

*A:PE-1>config>qos>hs-pool-policy# info detail | 
     match expression " root-pool 16$| mid-pool 15$| mid-pool 16$" post lines 2 | 
     match invert-match slope
                root-pool 16
                    allocation-weight 100
                mid-pool 15
                    parent-root-pool 16
                    allocation-percent 100.00
                mid-pool 16
                    parent-root-pool 16
                    allocation-percent 100.00

*A:PE-1# show hs-pools port 3/1/1 egress | 
              match "Root Pool : 16" post-lines 19 | 
              match "Pool" post-lines 1
Root Pool : 16
|  Total               : 1989432 KB  Allocated         : 0 KB
|--- Mid Pool : 15
|     | Total               : 1989432 KB  Allocated         : 0 KB
|--- Mid Pool : 16
|     | Total               : 1989432 KB  Allocated         : 0 KB

An HS port pool policy is applied to port 3/1/1 with standard port class pool 1 parented to mid pool 16 with an allocation port-bw-weight of 1. This port class pool has the same number of allocated buffers as mid pool 16:

*A:PE-1>config>qos>hs-port-pool-policy>std-port-class-pools# info
----------------------------------------------
                class-pool 1
                    parent-mid-pool 16
                exit

*A:PE-1# show hs-pools port 3/1/1 egress | 
                  match "Root Pool : 16" post-lines 26 | match "Pool" post-lines 1
Root Pool : 16
|  Total               : 1989432 KB  Allocated         : 0 KB
|--- Mid Pool : 15
|     | Total               : 1989432 KB  Allocated         : 0 KB
|--- Mid Pool : 16
|     | Total               : 1989432 KB  Allocated         : 0 KB
|     |--- Std Port Class Pool : 1
|     |      Total               : 1989432 KB  Allocated         : 0 KB

The port-bw-oversub-factor is set to 2 for mid pool 16 in the HS pool policy, after which the size of mid pool 16 does not change. However, its apparent size for the calculation of its port class pool doubles, which causes the size of port class pool 1 to be twice that of mid pool 16, thereby oversubscribing it:

*A:PE-1>config>qos>hs-pool-policy# info
----------------------------------------------
            root-tier
                root-pool 16
                    allocation-weight 100
                exit
            exit
            mid-tier
                mid-pool 15
                    parent-root-pool 16
                    allocation-percent 100.00
                exit
                mid-pool 16
                    parent-root-pool 16
                    allocation-percent 100.00
                    port-bw-oversub-factor 2
                exit
            exit

*A:PE-1# show hs-pools port 3/1/1 egress |
              match "Root Pool : 16" post-lines 26 | 
              match "Pool" post-lines 1
Root Pool : 16
|  Total               : 1989432 KB  Allocated         : 0 KB
|--- Mid Pool : 15
|     | Total               : 1989432 KB  Allocated         : 0 KB
|--- Mid Pool : 16
|     | Total               : 1989432 KB  Allocated         : 0 KB
|     |--- Std Port Class Pool : 1
|     |      Total               : 3978864 KB  Allocated         : 0 KB

A second standard port class pool, pool 2, on port 3/1/1 is parented to mid pool 16. The two port class pools share the buffer allocation equivalent to two times that of mid pool 16:

*A:PE-1>config>qos>hs-port-pool-policy>std-port-class-pools# info
----------------------------------------------
                class-pool 1
                    parent-mid-pool 16
                exit
                class-pool 2
                    parent-mid-pool 16
                exit
*A:PE-1# show hs-pools port 3/1/1 egress | 
              match "Root Pool : 16" post-lines 33  | 
              match "Pool" post-lines 1
Root Pool : 16
|  Total               : 1989432 KB  Allocated         : 0 KB
|--- Mid Pool : 15
|     | Total               : 1989432 KB  Allocated         : 0 KB
|--- Mid Pool : 16
|     | Total               : 1989432 KB  Allocated         : 0 KB
|     |--- Std Port Class Pool : 1
|     |      Total               : 1989432 KB  Allocated         : 0 KB
|     |--- Std Port Class Pool : 2
|     |      Total               : 1989432 KB  Allocated         : 0 KB

The proportion of buffers available to the port class pools can be modified by configuring their allocation port-bw-weight. If the allocation port-bw-weight of port class pool 2 is set to 2, the port class pools will be allocated buffers in a 2:1 ratio:

*A:PE-1>config>qos>hs-port-pool-policy>std-port-class-pools# info
----------------------------------------------
                class-pool 1
                    parent-mid-pool 16
                exit
                class-pool 2
                    parent-mid-pool 16
                    allocation port-bw-weight 2
                exit

*A:PE-1# show hs-pools port 3/1/1 egress | 
              match "Root Pool : 16" post-lines 33 | 
              match "Pool" post-lines 1
Root Pool : 16
|  Total               : 1989432 KB  Allocated         : 0 KB
|--- Mid Pool : 15
|     | Total               : 1989432 KB  Allocated         : 0 KB
|--- Mid Pool : 16
|     | Total               : 1989432 KB  Allocated         : 0 KB
|     |--- Std Port Class Pool : 1
|     |      Total               : 1326288 KB  Allocated         : 0 KB
|     |--- Std Port Class Pool : 2
|     |      Total               : 2652576 KB  Allocated         : 0 KB

A third standard port class pool, pool 3, is parented to mid pool 16 with an allocation port-bw-weight of 2. Port class pools 1, 2, and 3 share the oversubscribed mid pool 16 size in a ratio of 1:2:2:

*A:PE-1>config>qos>hs-port-pool-policy>std-port-class-pools# info
----------------------------------------------
                class-pool 1
                    parent-mid-pool 16
                exit
                class-pool 2
                    parent-mid-pool 16
                    allocation port-bw-weight 2
                exit
                class-pool 3
                    parent-mid-pool 16
                    allocation port-bw-weight 2
                exit

*A:PE-1# show hs-pools port 3/1/1 egress | 
              match "Root Pool : 16" post-lines 40 | 
              match "Pool" post-lines 1
Root Pool : 16
|  Total               : 1989432 KB  Allocated         : 0 KB
|--- Mid Pool : 15
|     | Total               : 1989432 KB  Allocated         : 0 KB
|--- Mid Pool : 16
|     | Total               : 1989432 KB  Allocated         : 0 KB
|     |--- Std Port Class Pool : 1
|     |      Total               : 795772 KB   Allocated         : 0 KB
|     |--- Std Port Class Pool : 2
|     |      Total               : 1591544 KB  Allocated         : 0 KB
|     |--- Std Port Class Pool : 3
|     |      Total               : 1591544 KB  Allocated         : 0 KB

Standard port class pool 1, 2, and 3 are now configured with an allocation explicit-percent of 80%, 60%, and 60% respectively. This allocates these percentages of mid pool 16 real size to port class pools 1, 2, and 3, which oversubscribed the mid pool by 100%. The mid pool 16 oversubscription factor is not applied.

*A:PE-1>config>qos>hs-port-pool-policy>std-port-class-pools# info
----------------------------------------------
                class-pool 1
                    parent-mid-pool 16
                    allocation explicit-percent 80.00
                exit
                class-pool 2
                    parent-mid-pool 16
                    allocation explicit-percent 60.00
                exit
                class-pool 3
                    parent-mid-pool 16
                    allocation explicit-percent 60.00
                exit

*A:PE-1# show hs-pools port 3/1/1 egress | 
              match "Root Pool : 16" post-lines 40 |
              match "Pool" post-lines 1
Root Pool : 16
|  Total               : 1989432 KB  Allocated         : 0 KB
|--- Mid Pool : 15
|     | Total               : 1989432 KB  Allocated         : 0 KB
|--- Mid Pool : 16
|     | Total               : 1989432 KB  Allocated         : 0 KB
|     |--- Std Port Class Pool : 1
|     |      Total               : 1591544 KB  Allocated         : 0 KB
|     |--- Std Port Class Pool : 2
|     |      Total               : 1193658 KB  Allocated         : 0 KB
|     |--- Std Port Class Pool : 3
|     |      Total               : 1193658 KB  Allocated         : 0 KB

Each configuration uses the same four queues:

• Queue 7 at scheduling class 5

• Queue 6 at scheduling class 4

• Queues 1 and 2 in WRR group at scheduling class 1

The low-burst-max-class is configured to be class 1, to match the scheduling class of WRR group 1. This results in queues 1 and 2 being subject to the low burst limit threshold.

HSQ queue group queues can be attached to scheduling classes or to WRR groups, which can then be attached to a scheduling class. The eight queues and two WRR groups in an HSQ queue group can also be unattached (not attached to any scheduling class, or for queues, to any WRR group). This is configured using an hs-attachment-policy:

configure
    qos
        hs-attachment-policy <policy-name> [create]
            description <description-string>
            low-burst-max-class <class>
            queue <queue-id> sched-class <class-id>
            queue <queue-id> unattached
            queue <queue-id> wrr-group <wrr-group-id>
            wrr-group <group-id> sched-class <class-id>

Where (in order):

<policy-name>        : [32 chars max]
<description-string> : [80 chars max]
<class>              : [1..6]
<queue-id>           : [1..8]
<class-id>           : [1..6]
<wrr-group-id>       : [1..2]
<group-id>           : [1..2]
<class-id>           : [1..6]

When a queue or WRR group is unattached, the related queues discard all received packets.

When a queue is attached to a WRR group, the weight of that queue within the group is configured under the queue in the SAP egress QoS policy, network queue policy, and egress queue group template.

When a queue is attached to a WRR group, the following queue parameters are ignored. The corresponding configuration is applied to the entire WRR group in the SAP egress QoS policy for services, network queue policy for network interfaces, and egress queue group templates for both access and network egress queue group instances:

• adaptation-rule

• hs-class-weight

• percent-rate

• rate

A default hs-attachment-policy is created by the system and applied by default to all SAP egress QoS policy for services, to all network queue policy for network interfaces, and to all egress queue group templates for both access and network egress queue group instances. The default policy is not configurable.

*A:PE-1>config>qos# hs-attachment-policy "default"
*A:PE-1>config>qos>hs-attachment-policy# info detail
----------------------------------------------
            no description
            low-burst-max-class 6
            queue 1 wrr-group 1
            queue 2 wrr-group 1
            queue 3 wrr-group 1
            queue 4 sched-class 2
            queue 5 sched-class 3
            queue 6 sched-class 4
            queue 7 sched-class 5
            queue 8 sched-class 6
            wrr-group 1 sched-class 1
            wrr-group 2 unattached

To use a user-defined policy, a new HS attachment policy must be created and applied to the appropriate SAP egress QoS policy, network queue policy, or egress queue group template. A newly created policy has all queues and WRR groups unattached and the low-burst-max-class set to 6:

*A:PE-1# configure qos hs-attachment-policy hs-att-policy-new create
*A:PE-1>config>qos>hs-attachment-policy$ info detail
----------------------------------------------
            no description
            low-burst-max-class 6
            queue 1 unattached
            queue 2 unattached
            queue 3 unattached
            queue 4 unattached
            queue 5 unattached
            queue 6 unattached
            queue 7 unattached
            queue 8 unattached
            wrr-group 1 unattached
            wrr-group 2 unattached

The hs-attachment-policy used for this example is as follows (queue 8 is reserved to be attached to scheduling class 6 for network protocol traffic, but is not used in this example):

*A:PE-1>config>qos# hs-attachment-policy "hs-att-pol-1"
*A:PE-1>config>qos>hs-attachment-policy# info detail
----------------------------------------------
            no description
            low-burst-max-class 1
            queue 1 wrr-group 1
            queue 2 wrr-group 1
            queue 3 unattached
            queue 4 unattached
            queue 5 unattached
            queue 6 sched-class 4
            queue 7 sched-class 5
            queue 8 sched-class 6
            wrr-group 1 sched-class 1
            wrr-group 2 unattached

An HS attachment policy is shown as follows:

*A:PE-1# show qos hs-attachment-policy "hs-att-pol-1"

===============================================================================
HS Attachment Policy Information
===============================================================================
Policy Name             : hs-att-pol-1
Description             : (Not Specified)
Low Burst Max Class     : 1

-------------------------------------------------------------------------------
Queue               Scheduling Class              WRR Group
-------------------------------------------------------------------------------
1                   (Not-Applicable)              1
2                   (Not-Applicable)              1
3                   unattached                    unattached
4                   unattached                    unattached
5                   unattached                    unattached
6                   4                             (Not-Applicable)
7                   5                             (Not-Applicable)
8                   6                             (Not-Applicable)

-------------------------------------------------------------------------------
WRR Group           Scheduling Class
-------------------------------------------------------------------------------
1                   1
2                   unattached
===============================================================================
*A:PE-1#

It is also possible to show the associations for each policy:

*A:PE-1# show qos hs-attachment-policy "hs-att-pol-1" association

===============================================================================
HS Attachment Policy Information
===============================================================================
Policy Name             : hs-att-pol-1
Description             : (Not Specified)
Low Burst Max Class     : 1

-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
Network-Queue Policy
-------------------------------------------------------------------------------
10

Sap-Egress Policy
-------------------------------------------------------------------------------
10
20

Egress Queue-Group Templates
-------------------------------------------------------------------------------
queue-group-1

-------------------------------------------------------------------------------
===============================================================================

HS secondary shapers are only applicable to SAP egress in the context of this chapter (not to network egress or egress access and network queue group instances). However, because secondary shapers can also be used by subscribers, they are included with the generic configuration aspects.

Secondary shapers are aimed at providing QoS control for traffic forwarded to a specific downstream device, such as an access node. Multiple HS secondary shapers can be configured on an egress port.

An aggregate rate and per-scheduling class rates are configurable for each secondary shaper. A low-burst-max-class parameter is also available to provide granular control over the scheduling behavior of which queues (via a WRR group, if used) use the low burst limit threshold and which use the high burst limit threshold.

Secondary shapers are configured on each port under the config>port>ethernet>egress context:

configure
    port <port-id>
        ethernet
            egress
                hs-secondary-shaper <secondary-shaper-name>
                    description <description-string>
                    aggregate
                        low-burst-max-class <class>
                        rate <rate>
                    class <class-number>
                        rate <rate>

Where (in order):

<port-id>            : slot/mda/port
<secondary-shaper-*> : [32 chars max]
<description-string> : [80 chars max]
<class>              : [1..6]
<class-number>       : [1..6]
<rate>               : [1..100000000|max] Kbps
<rate>               : [1..100000000|max] Kbps

A default HS secondary shaper is applied to all egress HSQ ports with the rates set to max and the low-burst-max-class set to 6. It is possible to modify the configuration of the default HS secondary shaper.

*A:PE-1>config>port>ethernet>egress# hs-secondary-shaper "default"
*A:PE-1>config>port>ethernet>egress>hs-sec-shaper# info detail
----------------------------------------------
                    no description
                    aggregate
                        rate max
                        low-burst-max-class 6
                    exit
                    class 1
                        rate max
                    exit
                    class 2
                        rate max
                    exit
                    class 3
                        rate max
                    exit
                    class 4
                        rate max
                    exit
                    class 5
                        rate max
                    exit
                    class 6
                        rate max
                    exit

An HS secondary shaper is configured on port 3/1/2 with a rate of 100 Mb/s for scheduling class 1 and a low-burst-max-class set to 1:

*A:PE-1>config>port>ethernet>egress# hs-secondary-shaper "hs-sec-shaper-1"
*A:PE-1>config>port>ethernet>egress>hs-sec-shaper# info detail
----------------------------------------------
                    no description
                    aggregate
                        rate max
                        low-burst-max-class 1
                    exit
                    class 1
                        rate 100000
                    exit
                    class 2
                        rate max
                    exit
                    class 3
                        rate max
                    exit
                    class 4
                        rate max
                    exit
                    class 5
                        rate max
                    exit
                    class 6
                        rate max
                    exit

This is shown, in this case with its associations, as follows:

*A:PE-1# show port 3/1/2 hs-secondary-shaper "hs-sec-shaper-1" associations

===============================================================================
Ethernet Port 3/1/2 Egress HS Secondary Shaper Information
===============================================================================
Policy Name        : hs-sec-shaper-1
Description        : (Not Specified)
Rate               : max
Low Burst Max Class: 1

-------------------------------------------------------------------------------
Class                                   Rate
-------------------------------------------------------------------------------
1                                       100000 Kbps
2                                       max
3                                       max
4                                       max
5                                       max
6                                       max
-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
Service Associations
-------------------------------------------------------------------------------
Service ID                Service Type               SAP
-------------------------------------------------------------------------------
1                         IES                        3/1/2:1
-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
Subscriber Associations
-------------------------------------------------------------------------------
Subscriber ID
-------------------------------------------------------------------------------
No Subscriber Associations Found.
-------------------------------------------------------------------------------
===============================================================================
*A:PE-1#

All HS secondary shapers on a port can be shown using the same command, but omitting the shaper name and following parameter.

It is also possible to show the forwarding statistics related to an HS secondary shaper:

*A:PE-1# show port 3/1/2 hs-secondary-shaper "hs-sec-shaper-1" statistics

===============================================================================
Ethernet Port 3/1/2 Egress HS Secondary Shaper Information
===============================================================================
Policy Name        : hs-sec-shaper-1

------------------------------------------------------------------------
Statistics Information
------------------------------------------------------------------------

------------------------------------------------------------------------
                        Packets                 Octets
Class 1
    Forwarded         : 4000                    592000

Class 2
    Forwarded         : 0                       0

Class 3
    Forwarded         : 0                       0

Class 4
    Forwarded         : 1000                    148000

Class 5
    Forwarded         : 1000                    148000

Class 6
    Forwarded         : 0                       0

Aggregate
    Forwarded         : 6000                    888000

------------------------------------------------------------------------
===============================================================================
*A:PE-1#

These statistics are cleared using the following command:

clear port 3/1/2 hs-secondary-shaper "hs-sec-shaper-1" statistics

The SAP egress queues in an HSQ queue group can be associated with a secondary shaper by configuring an egress queue override under the SAP and specifying the name of the secondary shaper. In addition, when using PW-SAPs, an HS secondary shaper can be applied to the egress of a PW port to control the PW-SAP egress traffic over that PW. See the SAP Egress section for configuration details.

If the user configures an HS secondary shaper on a port, the system instantiates a default primary shaper for that secondary shaper (which is used by all HSQ queue groups sending traffic to the secondary shaper) when the first egress SAP or PW-SAP is associated with that HS secondary shaper.

The current traffic rates through the secondary shapers on a port are shown, as follows, where the default interval is 1 second:

show qos hs-scheduler-hierarchy port <port-id> 
              [hs-secondary-shaper <shaper-name>] [interval <time-in-seconds>]
show qos hs-scheduler-hierarchy port <port-id> 
              [interval <time-in-seconds>] hs-secondary-shapers

The output shows the current aggregate traffic rate and the current traffic rate for each scheduling class:

*A:PE-1# show qos hs-scheduler-hierarchy port 3/1/2 
                      hs-secondary-shaper "hs-sec-shaper-1"

===============================================================================
Hs Scheduler Hierarchy Information
===============================================================================
Hs Sched Policy Name         : default

Port Max-Rate : 137 Mbps
Hs-Sec-Shaper:hs-sec-shaper-1 Agg-Rate : 57516 Kbps

Scheduler Priority 6
  Scheduler Class 6  Rate : 0 Mbps
    Hs-Sec-Shaper:hs-sec-shaper-1 Class 6 Rate : 0 Kbps

Scheduler Priority 5
  Scheduler Class 5  Rate : 22 Mbps
    Hs-Sec-Shaper:hs-sec-shaper-1 Class 5 Rate : 11422 Kbps

Scheduler Priority 4
  Scheduler Class 4  Rate : 45 Mbps
    Hs-Sec-Shaper:hs-sec-shaper-1 Class 4 Rate : 22797 Kbps

Scheduler Priority 3
  Scheduler Class 3  Rate : 0 Mbps
    Hs-Sec-Shaper:hs-sec-shaper-1 Class 3 Rate : 0 Kbps

Scheduler Priority 2
  Scheduler Class 2  Rate : 0 Mbps
    Hs-Sec-Shaper:hs-sec-shaper-1 Class 2 Rate : 0 Kbps

Scheduler Priority 1
  Scheduler Class 1  Rate : 69 Mbps
    Hs-Sec-Shaper:hs-sec-shaper-1 Class 1 Rate : 23296 Kbps
===============================================================================
*A:PE-1# 

A single HS scheduler policy can be applied to an egress HSQ port to configure an aggregate rate (max-rate) and per-scheduling class rates on that port. In addition, contiguous scheduling classes can be configured with weights in a WRR group, which can also be configured with a rate. The WRR group is scheduled at the scheduling class of its highest member scheduling class. The max-rate caps the scheduling class and group rates if its rate is lower.

The rates configured within an HS scheduler policy are applicable to all types of traffic (SAP egress, network egress, and egress queue group instances) exiting that port.

An HS scheduler policy is configured as follows:

configure
    qos
        hs-scheduler-policy <policy-name> [create]
            description <description-string>
            group <group-id> rate <rate>
            max-rate <rate>
            scheduling-class <class-id> group <group-id> [weight <weight-in-group>]
            scheduling-class <class-id> rate <rate>

Where (in order):

<policy-name>        : [32 chars max]
<description-string> : [80 chars max]
<group-id>           : [1]
<rate>               : [1..100000|max] Mbps
<rate>               : [1..100000|max] Mbps
<class-id>           : [1..6]
<group-id>           : [1]
<weight-in-group>    : [1..127]
<rate>               : [1..100000|max] Mbps

A default HS scheduler policy is applied to all egress HSQ ports and all its rates are set to max. It is not possible to modify the default HS scheduler policy.

*A:PE-1>config>qos# hs-scheduler-policy "default" 
*A:PE-1>config>qos>hs-scheduler-policy# info detail
----------------------------------------------
            description "Default hs scheduler QoS policy"
            max-rate max
            group 1 rate max
            scheduling-class 1 rate max
            scheduling-class 2 rate max
            scheduling-class 3 rate max
            scheduling-class 4 rate max
            scheduling-class 5 rate max
            scheduling-class 6 rate max

A newly created HS scheduler policy has the same configuration as the default policy.

An HS scheduler policy with a rate of 5 Gb/s for scheduling class 1 is applied to port 3/1/1:

*A:PE-1# configure qos
*A:PE-1>config>qos# hs-scheduler-policy "hs-sched-pol-1"
*A:PE-1>config>qos>hs-scheduler-policy# info detail
----------------------------------------------
            no description
            max-rate max
            group 1 rate max
            scheduling-class 1 rate 5000
            scheduling-class 2 rate max
            scheduling-class 3 rate max
            scheduling-class 4 rate max
            scheduling-class 5 rate max
            scheduling-class 6 rate max
----------------------------------------------
*A:PE-1>config>qos>hs-scheduler-policy# exit all
*A:PE-1# configure port 3/1/1 ethernet egress hs-scheduler-policy "hs-sched-pol-1"
*A:PE-1#

The preceding policy is shown as follows:

*A:PE-1# show qos hs-scheduler-policy "hs-sched-pol-1"

===============================================================================
HS Scheduler Policy Information
===============================================================================
Policy Name             : hs-sched-pol-1
Description             : (Not Specified)
Max Rate                : max

-------------------------------------------------------------------------------
Scheduling Class    Rate                Group               Weight in Group
-------------------------------------------------------------------------------
1                   5000 Mbps           0                   1
2                   max                 0                   1
3                   max                 0                   1
4                   max                 0                   1
5                   max                 0                   1
6                   max                 0                   1
-------------------------------------------------------------------------------
Group               Rate
-------------------------------------------------------------------------------
1                   max
===============================================================================
*A:PE-1#

The ports associated with this policy are as follows:

*A:PE-1# show qos hs-scheduler-policy "hs-sched-pol-1" association

===============================================================================
HS Scheduler Policy Information
===============================================================================
Policy Name             : hs-sched-pol-1
Description             : (Not Specified)
Max Rate                : max

-------------------------------------------------------------------------------
Port Ethernet Egress Associations
-------------------------------------------------------------------------------
3/1/1
-------------------------------------------------------------------------------
===============================================================================
*A:PE-1# 

The current traffic rates through the port aggregate, scheduling class, and WRR group shapers are shown, as follows, where the default interval is 1 second:

show qos hs-scheduler-hierarchy port <port-id> [interval <time-in-seconds>] 
          queue-group <queue-group-name> instance <instance-id> {access|network}
show qos hs-scheduler-hierarchy sap <sap-id> egress [interval <time-in-seconds>]
show qos hs-scheduler-hierarchy subscriber <sub-ident> egress 
                                                    [interval <time-in-seconds>]

The output shows the current aggregate traffic rate and the current traffic rates for each scheduling class:

*A:PE-1# show qos hs-scheduler-hierarchy port 3/1/1

===============================================================================
Hs Scheduler Hierarchy Information
===============================================================================
Hs Sched Policy Name         : hs-sched-pol-1

Port Max-Rate : 659 Mbps

Scheduler Priority 6
  Scheduler Class 6  Rate : 0 Mbps

Scheduler Priority 5
  Scheduler Class 5  Rate : 127 Mbps

Scheduler Priority 4
  Scheduler Class 4  Rate : 254 Mbps

Scheduler Priority 3
  Scheduler Class 3  Rate : 0 Mbps

Scheduler Priority 2
  Scheduler Class 2  Rate : 0 Mbps

Scheduler Priority 1
  Scheduler Class 1  Rate : 277 Mbps
===============================================================================
*A:PE-1# 

The HS scheduler policy parameters can be overridden under the port policy configuration:

configure
    port <port-id>
        ethernet
            egress
                hs-scheduler-overrides [create]
                    group <group-id> rate <rate>
                    max-rate <rate>
                    scheduling-class <class> rate <rate>
                    scheduling-class <class> weight <weight-in-group>

Where (in order):

<port-id>            : slot/mda/port
<group-id>           : [1..1]
<rate>               : [1..100000|max] Mbps
<rate>               : [1..100000|max] Mbps
<class>              : [1..6]
<rate>               : [1..100000|max] Mbps
<class>              : [1..6]
<weight-in-group>    : [1..127]