Creating a Service Egress QoS Policy

After the policy is created, the policy’s behavior can be defined. In addition, the behavior of policy’s FC and queue can be changed from their default settings:

Define the following attributes to create a service egress policy:

a unique policy ID value — the system does not dynamically assign a value. Optionally, a policy name can be configured after the policy has been created.
a default queue for the service egress policy
the scope — the service egress policy must be defined as having either an exclusive scope for one-time use or a template scope that enables its use with multiple SAPs

Use the following CLI syntax to create a service egress QoS policy:

CLI Syntax:

config>qos
    sap-egress policy-id
        description description-string
        policy-name policy-name
        queue queue-id [queue-type]
        scope {exclusive|template}

Example:

*A:ALU-1>configure qos sap-egress 600 create
config>qos>sap-egress$ fc be create
config>qos>sap-egress>fc$ exit
config>qos>sap-egress$ policy-name ‟sap_egr_87”
config>qos>sap-egress$ queue 2 expedite create
config>qos>sap-egress>queue$ exit
config>qos>sap-egress# scope exclusive
config>qos>sap-egress# exit

The following output displays the service egress policy 600 configuration:

*A:ALU-1 config>qos# info
----------------------------------------------
#--------------------------------------------------
echo "QoS Policy Configuration"
#--------------------------------------------------
   ...
        sap-egress 600 create
            scope exclusive
            policy-name ‟sap_egr_87” 
            queue 1 create
            exit
            queue 2 expedite create
            exit
            fc be create
            exit
        exit
----------------------------------------------
*A:ALU-1