Configure QoS Service Policy Map

The command creates the QoS service policy map configuration in the XCO database. This configuration is not pushed to the device. Configuration will only be pushed when the service policy map is associated with a QoS profile and the QoS profile is bound.

% efa policy qos service-policy-map create ?
  --name string        Name of the QoS service policy map
  --rule stringArray   Rule in format 
  “strict-priority[3],dwrr[25;25;25;25;0],class[default]”
		
Values of strict-priority as defined below
  <0  No strict priority queue; all are DWRR
1  Traffic Class 7 strict priority queue; rest are DWRR
2  Traffic Class 6 through 7 strict priority queues; rest are DWRR
3  Traffic Class 5 through 7 strict priority queues; rest are DWRR
4  Traffic Class 4 through 7 strict priority queues; rest are DWRR
5  Traffic Class 3 through 7 strict priority queues; rest are DWRR
6  Traffic Class 2 through 7 strict priority queues; rest are DWRR
7  Traffic Class 1 through 7 strict priority queues; rest are DWRR >

• For weights, the value list can have semicolon separated weights for traffic class queues which do not have strict priority. The sum of all the weights must equal to 100.
• SLXOS Default: All TC queues are strict priority. TC7 has the highest priority and TC0 has the lowest.

% efa policy qos service-policy-map update ?
  --name string        Name of the QoS service policy map
  --rule stringArray   Rule in format 
  “strict-priority[3],dwrr[25;25;25;25;0],class[default]”
		
Values of strict-priority as defined below
  <0  No strict priority queue
1  Traffic Class 7 strict priority queue
2  Traffic Class 6 through 7 strict priority queues
3  Traffic Class 5 through 7 strict priority queues
4  Traffic Class 4 through 7 strict priority queues
5  Traffic Class 3 through 7 strict priority queues
6  Traffic Class 2 through 7 strict priority queues
7  Traffic Class 1 through 7 strict priority queues>
Only “default” for class attribute is supported

The value list can have semicolon separated weights for traffic class queues which do not have strict priority. The sum of all the weights must equal to 100.

The following command updates the QoS service policy map named servicePolicy1 for strict priority value of 2 and new weights:

% efa policy qos service-policy-map update –-name servicePolicy1 –-rule “strict-priority[2],dwrr[50;25;25;0;0;0],class[default]”

Running the efa policy qos service-policy-map update command updates the configuration on the switch as follows.

S4(config-policymap-class)# do show running-config policy-map
policy-map servicePolicy1
 class default
  scheduler strict-priority 2 dwrr 50 25 25 0 0 0

% efa policy qos service-policy-map delete?
  --name string        Name of the QoS service policy map

The following command deletes the QoS service policy map servicePolicy1:

% efa policy qos service-policy-map delete –-name servicePolicy1

% efa policy qos service-policy-map list?
  --name string        Name of the QoS service policy map
  --ip   string	  IP Address

• The following command lists configuration details of the QoS service policy map servicePolicy1:
  

  % efa policy qos service-policy-map list –-name servicePolicy1 
  
  QoS Service Policy Map details:
  Name: servicePolicy1
  +------------------+-------------------+---------+
  |  Strict Priority |   DWRR weights    | Class   |
  +------------------+-------------------+---------+
  |         2        | 50,25,25,0,0,0    | default |
  +------------------+-------------------+---------+

• The following command lists configuration details of the QoS map servicePolicy1 along with the app state on specified devices:
  

  % efa policy qos service-policy-map list –-name servicePolicy1 –-ip 10.20.245.1-2
  QoS Service Policy Map details:
  Name: servicePolicy1
  +------------------+-------------------+---------+
  |  Strict Priority |   DWRR weights    | Class   |
  +------------------+-------------------+---------+
  |         2        | 50,25,25,0,0,0    | default |
  +------------------+-------------------+---------+
  
  Device Bindings:
  +----------------+----------------+
  |   IP Address   |   App State    |
  +----------------+----------------+
  |   10.20.245.1  |   cfg-in-sync  |
  +----------------+----------------+
  |   10.20.245.2  |   cfg-in-sync  |
  +----------------+----------------+