When using profile-mode queues, traffic that is marked as in-profile on ingress and scheduled in the above-CIR loop will still be considered as in-profile at egress.

When an HQoS strategy using an egress port-scheduler has been deployed, Tier 1 receives its scheduling rates based on the amount of egress bandwidth available for each forwarding class.

The greater the difference between PIR and CIR rates in a queue, the less likely a CIR will be provided.

Packets scheduled out of high-priority queues in the default scheduler will have a lower chance of packet loss at the expense of incurring a higher probability of delay.

When using priority-mode queues, traffic that is marked as in-profile on ingress and scheduled in the above-CIR loop will be considered as in-profile at egress.