Brocade Multi-Service IronWare QoS and Traffic Management Configuration Guide (Supporting R05.6.00) User Manual
Page 106

92
Multi-Service IronWare QoS and Traffic Management Configuration Guide
53-1003037-02
Configuring QoS
4
Brocade(config)# qos-mapping
Brocade(config-qos-mapping)# exp decode-map Customer1
Brocade(config-qos-mapping-exp-decode)# exp-value 7 to priority 5 drop-precedence
2
Syntax: [no] exp-value exp-value [exp-value ] to priority priority-value [drop-precedence dp-value]
The exp-value variable specifies the value of the EXP bits within the packet header of the incoming
packets. You can optionally specify multiple exp-value variables if you want to specify more than
one value to map to the same internal priority and drop precedence values. Where EXP values
within a policy map are unspecified, the default mapping will be used.
The priority keyword together with the priority-value variable specifies the internal priority value that
the packets with the previously specified exp-value value will be mapped to. The priority-value
variable can be a value between 0 and 7. Please note, when generating the configuration file a
configured priority value that is the same as the value in the default priority map will not be shown.
The drop-precedence keyword is an optional parameter that allows you to specify a dp-number
variable that represents the drop precedence value that you want to assign to incoming packets
with the previously specified dp-value value. This value is specified in addition to a priority
priority-value value. The dp-number variable can be a value between 0 and 3. The default value is
the value described in the default EXP table. Please note, when generating the configuration file a
value for drop precedence will only be shown for non-default values.
When using the [no] option to negate a previously configured value of this command, observe the
considerations described below.
1. You can negate both the priority and drop-precedence values (returning them to their default
values) by using the [no] option with the original command only up to the priority value.
For example: the following command has been used to set the map to assign an internal
priority of “5” and a drop precedence of “2” to Ingress packets that have an EXP value of “7”.
Brocade(config-qos-mapping-exp-decode)# exp-value 7 to priority 5
drop-precedence 2
To set the priority and drop-precedence values back to the default values, use the [no] option
with the previous command up to where the priority value is configured, as shown in the
following.
Brocade(config-qos-mapping-exp-decode)# no exp-value 7 to priority 5
After this command is executed, the priority and drop-precedence values for exp-value 7 will be
returned to their default values as described in the default map tables that are defined in
2. You can negate the drop-precedence value (returning it to its default value) without changing
the currently configured priority value. This is done by using the [no] option with the original
command that includes both the priority and drop-precedence values.
For example: the following command has been used to set the priority map to assign an
internal priority of “5” and a drop precedence of “2” to Ingress packets that have a EXP value
of “7”.
Brocade(config-qos-mapping-exp-decode)# exp-value 7 to priority 5
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.