10.2. Service Egress 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 enables the context to configure a SAP egress policy. The SAP egress policy determines the QoS treatment to packets at service egress.

When the policy is created, by default there will be only one queue that is created. The user can create up to 8 queues and associate it to different FCs on the SAPs to which this SAP egress policy is attached. The SAP egress policy allows the user to define the queue parameters for the eight queues.

This command associates a dot1p classification policy, which contains entries used to map traffic sent on an access SAP to an FC and profile state, based on the dot1p bits in the packet.

When the dot1p classification policy is defined in a service egress QoS policy and associated with an access SAP egress, a packet sent out of the SAP is used to match with the dot1p values defined in this policy. If a match is found, the corresponding FC and profile are assigned to the packet.

Note: The FC and profile assigned by the dot1p entry match can be overridden by an IP precedence match or IP DSCP match. See Egress SAP FC and Profile Overrides for more information about the match hierarchy.

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

This command associates an IP DSCP classification policy, which contains entries used to map traffic sent on a SAP to an FC and profile state, based on the IP DSCP bits in the packet.

When the DSCP classification policy is defined in a service egress QoS policy and associated with an access SAP egress, a packet sent out of the SAP is used to match with the IP DSCP values defined in this policy. If a match is found, the corresponding FC and profile are assigned to the packet.

Note: The FC and profile assigned by the dot1p entry match or IP precedence entry match can be overridden by an IP DSCP match. See Egress SAP FC and Profile Overrides for more information about the match hierarchy.

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

This command creates a class instance of the forwarding class name. Once the fc-name is created, classification actions can be applied and 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 associates an IP DSCP classification policy with IP precedence entries used to map traffic sent out of a SAP to an FC and profile state based on the IP precedence bits in the packet.

When it is defined in a service egress QoS policy and associated with an access SAP egress, a packet sent out of the SAP is used to match with the IP precedence values defined in this policy. If a match is found, the corresponding FC and profile are assigned to the packet.

Note: The FC and profile assigned by the dot1p entry match can be overridden by an IP precedence match, and the FC and profile assigned by the IP precedence match can be overridden by an IP DSCP match. See Egress SAP FC and Profile Overrides for more information about the match hierarchy.

The no form of this command disables the use of the DSCP classification policy and IP precedence values.

This command enables the context to create a queue and modify queue parameters associated with a particular queue. The queue ID to FC map is user-defined.

The 7210 SAS-K 2F1C2T and 7210 SAS-K 2F6C4T support two, four, six, or eight queues per SAP.

The 7210 SAS-K 3SFP+ 8C supports four or eight queues per SAP.

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 cir and pir 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 the level to the default.

This command is used to override 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 defines the administrative PIR and the administrative 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 oversubscription 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 max default specifies the amount of bandwidth in kilobits per second. The max value is mutually exclusive to the pir-rate-in-kbps value.

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

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 configures the scope as exclusive or template. The scope of the policy cannot be changed if the policy is applied to multiple interface ports.

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