Network queue policies define the ingress network queuing at the FP network node level. Network queue policies are also used at the Ethernet port and SONET/SDH path level to define network egress queuing.
There is one default network queue policy. Each policy can have up to 16 queues (unicast and multicast). The default policies can be copied but they cannot be deleted or modified. The default policy is identified as network-queue default. Default network queue policies are applied to the card FP ingress network and port Ethernet network. Other network queue QoS policies must be explicitly created and associated.
For information about the tasks and commands necessary to access the CLI and to configure and maintain devices, refer to the CLI Usage chapter in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Basic System Configuration Guide.
Network egress queues support port-scheduler parent priority-level associations. Using a port scheduler policy definition and mapping network queues to a port parent priority level, HQoS functionality is supported providing eight levels of strict priority and weights within the same priority. A network queue’s bandwidth is allocated using the within-CIR and above-CIR scheme normal for port schedulers.
Queue CIR and PIR percentages when port-based schedulers are in effect will be based on frame-offered-load calculations.
A network queue with a port parent association that exists on a port without a scheduler policy defined will be considered to be orphaned.
See Scheduler QoS Policies for more information about queue parental association scope.
A basic network queue QoS policy must conform to the following:
Configuring and applying QoS policies other than the default policy is optional. A default network queue policy is applied to the card FP ingress network and port Ethernet network.
To create a network queue policy, enter the configure qos network-queue command with an unused policy name followed by the create keyword. Once created, the parameters in the policy, such as a description, the mapping of forwarding classes to queues, and the queue properties can be configured.
Apply network queue policies to the following entities:
Use the following CLI syntax to apply a network queue policy to an FP ingress network:
The following output displays FP ingress network queue policy using the default policy.
Use the following CLI syntax to apply a network queue policy to an Ethernet port.
The following output displays the port configuration.
Use the following CLI syntax to apply a network queue policy to a SONET/SDH port:
The following output displays the port configuration.
The default network queue policy is named default and cannot be modified or deleted. The default policy parameters are shown below.
This section discusses network queue QoS policy service management tasks.
A network queue policy is associated by default with the card FP ingress network and port Ethernet network. The default policy can be replaced with a customer-configured policy, but cannot entirely be removed. When a QoS policy is removed, the policy association reverts to the default network-queue policy.
To delete a user-created network queue policy, enter the following commands:
To delete a network policy, enter the following commands:
An existing network queue policy can be copied, renamed with a new policy ID name, or used to overwrite an existing network queue policy. The overwrite option must be specified or an error occurs if the destination policy ID exists.
Existing policies, except the default policies, and entries in the CLI can be modified. The changes are applied immediately to all interfaces where the policy is applied. To prevent configuration errors, use the copy command to make a duplicate of the original policy to a work area, make the edits, then overwrite the original policy.