Configuring ingress decode exp policy maps – Brocade Multi-Service IronWare QoS and Traffic Management Configuration Guide (Supporting R05.6.00) User Manual

Page 105

Advertising
background image

Multi-Service IronWare QoS and Traffic Management Configuration Guide

91

53-1003037-02

Configuring QoS

4

For example: the following command has been used to set the priority map to assign an
internal priority of “4” and a drop precedence of “2” to Ingress packets that have a PCP value
of “6”.

Brocade(config-qos-mapping-pcp-decode)# pcp-value 6 to priority 4

drop-precedence 2

To set the drop-precedence value back to the default value, use the [no] option with the
previous command, as shown in the following.

Brocade(config-qos-mapping-pcp-decode)# no pcp-value 6 to priority 4

drop-precedence 2

After this command is executed, the priority value will remain at 4 and the drop-precedence
value will be returned to the default drop-precedence value for pcp-value 6, as described in the
default map tables that are defined in

“Default QoS mappings”

on page 79.

Configuring Ingress decode EXP Policy maps

The following procedures are used when configuring an Ingress Decode EXP Policy Map:

Naming an Ingress Decode EXP Policy Map

Configuring an Ingress Decode EXP Policy Map

Naming an Ingress decode EXP policy map
Once you are in the QoS configuration level, can define the name of a Ingress Decode EXP Policy
Map using the exp decode-map command, as shown in the following.

Brocade(config)# qos-mapping

Brocade(config-qos-mapping)# exp decode-map Customer1

Syntax: [no] exp decode-map map-name

The no option is used to delete a currently configured Ingress Decode EXP Policy Map. If the Ingress
Decode EXP Policy Map is currently in use, the no command will be rejected and an error message
will be displayed.

The map-name variable specifies the name of the Ingress Decode EXP Policy Map that you are
defining. It can be up to 64 characters in length. You can specify the same Ingress Decode EXP
Policy Map for different types of policy maps. For example, you can use the same name for an
Ingress Decode DSCP Policy Map and an Ingress Decode EXP Policy Map.

NOTE

The name “default-map” cannot be used because it is reserved for standard mappings as described
in

“Default QoS mappings”

on page 79.

Configuring an Ingress decode EXP policy map
Once you have named an Ingress Decode EXP Policy Map using the exp decode-map command,
you can set the values of the named policy map. Setting the values in a policy map involves
specifying the value of the EXP bits of an incoming packet and setting them to correspond to a
value of 0 to 7 of the device’s internal priority value. Optionally, you can set a drop precedence
value of 0 to 3 in addition to the internal priority value.

To set the values of an Ingress Decode EXP Policy Map, first specify name of the policy map and
then populate the values in the policy map using the exp-value command as shown in the following.

Advertising