This chapter provides information to configure service egress QoS policies using the CLI.
Note: On the 7210 SAS-R6 and 7210 SAS-R12, only unicast traffic sent out of RVPLS SAPs uses per-SAP egress queues. BUM traffic sent out of RVPLS SAPs uses per-port egress queues. |
The service-egress policy defines the Service Level Agreement (SLA) for service packets as they egress on the access SAP. Service-egress QoS policies allow the definition of queue parameters along with a remark policy.
On the 7210 SAS-R6 and 7210 SAS-R12, service-egress QoS policies are available for use only when per-SAP egress queues (SAP based queuing mode) are used. It is not available when port-based queuing mode (that is, with per-access port egress queues) is in use.
Note: The 7210 SAS-R6 and 7210 SAS-R12, on port egress, use either port-based egress queuing and shaping or SAP-based egress queuing and shaping for all SAPs configured on the port. The config system global-resource-profile qos port-scheduler-mode command allows the user to select the mode for all SAPs configured on either access ports or hybrid ports. When port-scheduler-mode is enabled, the software uses eight egress queues per port (access port or hybrid port). See Schedulers for more information. When port-scheduler-mode is disabled, the software allocates eight egress queues per SAP, which are configured using service egress policies. |
To use per-SAP service-egress policies, the following must be configured.
A basic service-egress QoS policy must conform to the following:
To create a SAP-egress policy, define the following:
Use the following syntax to configure a SAP-egress policy.
The following is a sample SAP-egress policy configuration output.
The following is a sample SAP-egress policy configuration output.
Existing policies and entries can be edited through the CLI or NMS. The changes are applied immediately to all services where the policy is applicable.
To prevent configuration errors, perform the following.