11.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 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 enables the context to modify Queue parameters associated with a particular queue.

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, 8 queues (1 to 8) are created and associated to different FCs on the SAPs to which this sap-egress policy is attached. SAP egress policy allows the user to define the queue parameters for the eight queues.

This command specifies the remarking policy ID to use for marking packets on service egress (also known as, SAP egress).

The remarking policy ID must be associated with the appropriate sap-egress policy and remarking must be enabled in the sap-egress policy to enable marking of packets sent out of the SAP. Only remarking policy of type dot1p, or dot1p-lsp-exp-shared is allowed to be used when the remark policy is associated with sap-egress. See Summary of Remark Policy and Attachment Points for 7210 SAS-Mxp for more information on remark policies.

Note: On the 7210 SAS-Mxp, remarking is user configurable and supports SAP-based marking per SAP and port-based marking per access port. For more information about access port-based marking capabilities, see Summary of Remark Policy and Attachment Points for 7210 SAS-Mxp and Access Egress QoS Policies on 7210 SAS-Mxp.

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, the default remark policy is used to mark packets sent out. If no remark policy is executed and remarking is disabled, packets are not remarked.

This command enables the system to remark egress packets sent out of service egress (also known as Access SAP egress).

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 sap-egress QoS policy, the remark policy associated with sap-egress QoS policy is used to determine the FC to dot1p mapping to use for marking packets sent out of access ports.

Refer the remark policy that can be used to configure FC to priority bit markings in different QoS policies associated with different service entities, in the chapter on Remark Policies. See Summary of Remark Policy and Attachment Points for 7210 SAS-Mxp for more information.

The no form of this command disables remarking.

This command configures the scope as exclusive or template. The policy’s scope cannot be changed if the policy is applied to an interface multiple ports.

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

This command associates the specified queue management policy with this queue.

The queue management policy is used to specify the queue buffer parameters and queue slope policy parameters.

The no form of this command associates the default SAP egress queue management policy with this queue.

This command determines whether the queue operates in strict or weighted mode.

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

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 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 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 when the queue-mode is set to weighted.

For queues configured in weighted mode, the CIR of the queues are met if bandwidth is available and the configured weights are considered in the PIR loop. The configured weight determines the proportion of available bandwidth that is given to this queue in comparison to other queues configured in weighted mode.

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

This command configures the scope as exclusive or template. The policy’s scope cannot be changed if the policy is applied to an interface multiple ports.

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