adaptation-rule [cir adaptation-rule] [pir adaptation-rule]
no adaptation-rule
config>qos>sap-egress>queue
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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.
adaptation-rule pir closest cir closest
Specifies the adaptation rule and defines the constraints enforced when adapting the CIR rate defined using the queue queue-id rate command. The cir parameter requires a qualifier that defines the constraint used to derive the operational CIR rate for the queue. When the cir parameter is not specified, the default constraint applies. The max (maximum), min (minimum), and closest qualifiers are mutually exclusive. Table: Supported hardware rates and burst step sizes for CIR and PIR values on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-T lists the supported hardware step-size rates.
Specifies the adaptation rule and defines the constraints enforced when adapting the PIR rate defined using the queue queue-id rate command. The pir parameter requires a qualifier that defines the constraint used when deriving the operational PIR rate for the queue. When the pir command is not specified, the default constraint applies. The max (maximum), min (minimum), and closest qualifiers are mutually exclusive. Table: Supported hardware rates and burst step sizes for CIR and PIR values on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-T lists the supported hardware step-size rates.
queue queue-id create
config>qos>sap-egress
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
This command configures queue parameters.
Specifies the ID of the queue.
Keyword to create a network queue policy.
sap-egress policy-id [create]
config>qos
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
This command configures a SAP Egress policy. The SAP egress policy determines the QoS treatment to packets on service egress.
When the policy is created, by default only one queue is created. The user can create up to eight queues and associate each queue to different FCs on the SAPs to which this sap-egress policy is attached. A SAP egress policy allows the user to define the queue parameters for the eight queues.
1
Specifies the ID of the SAP Egress policy.
Keyword to create a SAP Egress policy
remark policy-id
no remark
config>qos>sap-egress
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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 Table: Summary of remark policy and attachment points for 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12 for more information on remark policies.
On the 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12, remarking is user configurable and supports SAP-based marking per SAP and port-based marking per access port. See Access egress QoS policies on 7210 SAS-Mxp and Table: Summary of remark policy and attachment points for 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12 for more information about access port-based marking capabilities.
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.
Specifies the remark policy.
no remarking
remarking
config>qos>sap-egress
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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 -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.
See Remark policies and Table: Summary of remark policy and attachment points for 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12 for more information about the remark policy that can be used to configure FC to priority bit markings in different QoS policies associated with different service entities.
The no form of this command disables remarking.
no remarking
scope {exclusive | template}
no scope
config>qos>sap-egress
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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.
template
Specifies that the policy can only be applied to one interface or port. If a policy with an exclusive scope is assigned to a second interface, an error message is generated. If the policy is removed from the exclusive interface, it will become available for assignment to another exclusive interface. The system default policies cannot be put into the exclusive scope. An error will be generated if scope exclusive is executed in any policies with a policy-id equal to default QoS policies are configured with template scope. An error is generated if you try to modify the scope parameter from template to exclusive scope on default policies.
Specifies that the policy can be applied to multiple interfaces or ports on the router.
[no] queue-mgmt name
config>qos>sap-egress>queue
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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.
Specifies the name of the queue management policy, up to 32 characters.
[no] queue-mode queue-mode
config>qos>sap-egress
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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.
weighted
Specifies the queue mode.
strict — Specifies that the scheduler schedules the queue in order of their priority in the two passes, the CIR loop and the PIR loop.
weighted — Specifies that the scheduler examines these queues in two passes - CIR loop and PIR loop. In the CIR loop, it distributes the available bandwidth to all the strict and then weighted queues in round-robin up to the configured CIR rate. It examines the weighted queues in the PIR loop, after examining all the strict queues and distributes the available bandwidth, if any, in the proportion of the configured weights.
rate cir cir-rate-in-kbps [pir pir-rate-in-kbps]
no rate
config>qos>sap-egress>queue
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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.
rate cir 0 pir max
Specifies the administrative CIR rate, in kilobits, for the queue. The cir parameter overrides the default administrative CIR used by the queue. If the rate command is not executed or the cir parameter is not explicitly specified, the default CIR value is used.
Specifies the administrative PIR rate, in kilobits, for the queue. When the rate command is executed, a PIR setting is optional. If the rate command is not executed, the default PIR of maximum value is used. The max default specifies the amount of bandwidth in kilobits per second (thousand bits per second). The max value is mutually exclusive to the pir-rate value.
[no] weight weight
config>qos>sap-egress>queue
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
This command configures the weight of the queue.
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 contending for bandwidth at the same priority level.
The no form of this command reverts the weight to the default value.
1
Specifies the value for the weight parameter. The value is an integer value which specifies the proportion of available bandwidth to be allocated to this queue relative to other queues.
scope {exclusive | template}
no scope
config>qos>sap-egress
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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.
template
Specifies that the policy can only be applied to one interface port. If a policy with an exclusive scope is assigned to a second interface an error message is generated. If the policy is removed from the exclusive interface, it will become available for assignment to another exclusive interface. The system default policies cannot be put into the exclusive scope. An error will be generated if scope exclusive is executed in any policies with a policy ID equal to 1.
Specifies that the policy can be applied to multiple interface ports on the router.
Default QoS policies are configured with template scope. An error is generated if you try to modify the scope parameter from template to exclusive scope on default policies.