7.7. Network QoS Policy Command Reference

This command creates a text description stored in the configuration file for a configuration context.

The description command associates a text string with a configuration context to help identify the context in the configuration file.

The no form of this command removes any description string from the context.

This command copies existing QoS policy entries for a QoS policy ID to another QoS policy ID.

The copy command is used to create new policies using existing policies and also allows bulk modifications to an existing policy with the use of the overwrite keyword.

This command specifies the remarking policy ID to use for marking packets on access-uplink port egress, network port egress, or hybrid port egress. The usage is as follows for different platforms.

For access-uplink ports, the remarking policy ID must be associated with the network QoS policy that is associated with the access-uplink port. Remarking must be enabled in the network QoS policy to enable marking of packets sent out of an access-uplink port. Only a remarking policy of type dot1p, dscp, or dot1p-dscp is allowed to be used when the remark policy is associated with access-uplink port egress. See Remark Policies for more information about remark policy types and its usage.

For network ports and hybrid ports, the remarking policy ID must be associated with the network QoS policy that is associated with the network port and hybrid port. Remarking must be enabled in the network QoS policy to enable marking of packets sent out of network IP interfaces that are configured on the network port or hybrid port. On network ports or hybrid ports, the dot1p bits are marked by default, irrespective of whether remarking is enabled or disabled. Only a remarking policy of type lsp-exp, dot1p, dscp, dot1p-dscp, dot1p-lsp-exp, or dot1p-dscp-lsp-exp is allowed when the remark policy is associated with network port egress. See Remark Policies for more information about remark policy types and their usage.

The no form of this command removes the explicit association of the remark policy and associates the default remark policy. If remarking is enabled and no remark policy is executed, then the default remark policy is used to mark sent packets. If no remark policy is executed and remarking is disabled, then packets are not remarked at all.

This command configured marking for packets. The marking functionality is as follows.

When remarking is enabled, the remark policy configured in the QoS policy context is used to determine the FC to QoS bit mapping. For example, when remarking is enabled in the network QoS policy and remark policy of type dot1p is configured in the network QoS policy, then the FC to Dot1p mapping is used to mark packets sent out of the port.

See Remark Policies for more information on how to configure remark policies.

The no form of this command disables remarking.

This command configures the network policy scope as exclusive or template.

The no form of this command reverts the scope of the policy to the default.

This command creates or edits a QoS network policy. The network policy functionality is as follows.

On the 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, the network QoS policy associated with access-uplink port has ingress and egress components. These components are described as follows.

On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, the network QoS policy associated with network ports or hybrid ports has ingress and egress components. These components are described as follows.

The default network policy ID 1 is associated with access-uplink ports that do not have an explicit user configured policy and cannot be modified or deleted. The default network policy ID 2 is associated with network ports and hybrid ports that do not have an explicit user configured policy and cannot be modified or deleted. The default network policies define default mapping for packet header bits to the FCs on ingress and the mapping of the FC to queues.

If a new network policy is created, only the default action, default queues for unicast and multipoint traffic, and egress forwarding class parameters are identical to the default policy. A new network policy does not contain the default QoS bit to FC mapping (e.g. dot1p-to-FC mapping or EXP to FC mapping) for network QoS policy. The default network policy can be copied using the copy command to create a new network policy that includes the default ingress dot1p to FC mapping, as appropriate. You can modify parameters or use the no modifier to remove an object from the configuration.

Any changes made to an existing policy, using any of the sub-commands, will be applied immediately to all the ports where this policy is applied. For this reason, when many changes are required on a policy, it is highly recommended that the policy be copied to a work area policy ID. That work-in-progress policy can be modified until complete and then written over the original policy ID. Use the config qos copy command to maintain policies in this manner.

The no form of this command deletes the network policy. A policy cannot be deleted until it is removed from all entities where it is applied. The default network policy policy-id 1 cannot be deleted.

This command enables the context to create or edit egress policy entries that specify the forwarding class to marking values maps to be instantiated when this policy is applied to the access-uplink port, network port, or hybrid port.

The forwarding class and profile states are mapped to marking values for all packets affected by the policy defined in this context.

This command specifies the forwarding class name. The forwarding class name represents an egress queue. The FC name represents a CLI parent node that contains sub-commands or parameters describing the marking criteria of packets flowing through it. The fc command overrides the default parameters for that forwarding class to the values defined in the network default policy.

The no form of this command removes the forwarding class to marking value association. The forwarding class reverts to the mapping defined in the default network policy.

This command enables the context to creates or edits policy entries that specify the QoS bits to forwarding class mapping for all packets.

When pre-marked packets ingress on a network port or hybrid port, the QoS treatment through the 7210 SAS is based on the mapping defined on the current node.

This command defines or edits the default action to be taken for packets do not match any of the configured classification entries. The default-action command specifies the forwarding class to which such packets are assigned.

Multiple default-action commands will overwrite each previous default-action command.

This command associates a dot1p classification policy to a forwarding class and profile state based on the dot1p bits in the packet. The dot1p classification policy contains entries used to map traffic received on access-uplink ports, or traffic received in the context of a network IP interface configured on a network port or hybrid port.

The no form of this command disables the use of this policy.

This command associates an IP DSCP classification policy to a forwarding class and profile state based on the IP DSCP bits in the packet. The IP DSCP classification policy contains entries used to map traffic received on access-uplink ports, or traffic received in the context of a network IP interface configured on a network port or hybrid port.

The no form of the policy disables the use of this policy.

This command associates an mpls-lsp-exp classification policy to a forwarding class and profile state based on the MPLS EXP bits in the MPLS packet. The mpls-lsp-exp classification policy contains entries used to map traffic received in the context of a network IP interface configured on a network port or hybrid port.

The no form of this policy disables the use of this policy.

This command creates a class instance of the forwarding class. Once the fc-name is created, classification actions can be applied and it can be used in match classification criteria.

The no form of this command removes all the explicit queue mappings for fc-name forwarding types. The queue mappings revert to the default meters for fc-name.

This command enables DEI based classification. When enabled for packets classified to this FC, the DEI bit is used to determine the ingress profile for the packet. Packets received with DEI bit set to zero are treated as in-profile and packets with DEI bit set to one are treated as out-of-profile packets.

When DEI based classification is enabled under the FC context, it overrules the profile values specified in the classification entry used to assign the FC.

The no form of this command disables use of DEI bit for classification of packets.

This command enables the context to modify queue parameters associated with a particular queue.

The queue ID to FC map is user defined. In other words, the user can map FC to queues identified by queue IDs as per their needs.

The no form of this command deletes the queue.

This command defines the method used by the system to derive the operational CIR and PIR rates when the queue is provisioned in hardware. For the cir and pir parameters, the system attempts to find the best operational rate depending on the defined constraint.

The no form of this command removes any explicitly defined constraints used to derive the operational CIR and PIR created by the application of the policy. When a specific adaptation-rule is removed, the default constraints for rate and cir apply.

This command specifies the CBS value (minimum depth of the queue).

The no form of this command reverts to the default value.

This command specifies the MBS value (maximum depth of the queue).

The no form of this command reverts to the default value.

This command defines the queue priority. The queue priority is used by the scheduler to determine the order of service in both the within-cir loop and within-pir loop. Higher priority queues are serviced before lower priority queues.

The no form of this command reverts to the default value.

This command defines the administrative Peak Information Rate (PIR) and the administrative Committed Information Rate (CIR) parameters for the queue. The PIR defines the maximum rate that the queue can transmit packets through the port. Defining a PIR does not necessarily guarantee that the queue can transmit at the intended rate. The actual rate sustained by the queue can be limited by over subscription factors or available egress bandwidth. The CIR defines the rate at which the system prioritizes the queue over other queues competing for the same bandwidth.

The rate command can be executed at anytime, altering the PIR and CIR rates for all queues created on the access ports.

The no form of this command reverts all queues created with the queue ID by association with the QoS policy to the default PIR(100) and CIR(0).

This command overrides the default slope-policy configuration for the queue. The specified slope policy name must exist as a current slope policy name. If the slope policy does not exist, the slope-policy command will fail. If a slope policy is currently associated with a queue, the slope policy cannot be removed from the system.

The slope policy contains the ring and non-ring high and low WRED slope definitions that will be used by the queue. See Buffer Pools for more information about ring and non-ring buffer pools and slope usage.

If the slope-policy command is not executed or the no slope-policy command is executed, the default slope policy will be associated with the queue.

The no form of this command reverts the queue to the default slope policy.

This command configures the weight of the queue.

The configured weight determines the proportion of available bandwidth that is given to this queue in comparison to other queues contending for bandwidth at the same priority level.

The no form of this command reverts the weight to the default.

This command enables the context to configure DSCP and dot1p marking values for select self-generated traffic.

This command configures DSCP and dot1p marking values for self-generated application traffic. When an application is configured using this command, the specified DSCP name or value is used for all packets generated by this application within the router instance in which it is configured. The instances can be base router or VPRN service.

The values configured in this command are used to perform the following actions.

Only one DSCP name or value can be configured per application. If multiple entries are configured, the subsequent entry overrides the previously configured entry.

The no form of this command reverts to the default value.

This command creates a mapping between the DSCP of the self-generated traffic and the forwarding class.

Self-generated traffic for configured applications that matches the specified DSCP will be assigned to the corresponding forwarding class. Multiple commands can be entered to define the association of some or all 64 DSCPs to a forwarding class.

All DSCP names that define a DSCP value must be explicitly defined.

The no form of this command removes the DSCP-to-FC association.