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

Page 104

Advertising
background image

90

Multi-Service IronWare QoS and Traffic Management Configuration Guide

53-1003037-02

Configuring QoS

4

Configuring an Ingress decode PCP policy map
Once you have named an Ingress PCP Decode Policy Map using the pcp 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 PCP bits of an incoming packet and setting them to correspond to a
value of 0 to 7 of the device’s internal priority. 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 PCP Policy Map, first specify name of the policy map and
then populate the values in the Ingress Decode PCP Policy Map using the pcp-value command as
shown in the following.

Brocade(config)# qos-mapping

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

Brocade(config-qos-mapping-pcp-decode)# pcp-value 7 to priority 3 drop-precedence

2

Syntax: [no] pcp-value pcp-value [pcp-value] to priority priority-value [drop-precedence dp-value]

The pcp-value variable specifies the value of the PCP bits within the packet header of the incoming
packets. You can optionally specify multiple pcp-value variables if you want to specify more than
one value to map to the same internal priority and drop precedence. Where PCP 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 that the
packets with the previously specified pcp-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 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
0. Please note, when generating the configuration file a value for drop precedence will only be
shown for non-zero 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 “3” and a drop precedence of “2” to Ingress packets that have a PCP value of “7”.

Brocade(config-qos-mapping-pcp-decode)# pcp-value 7 to priority 3

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-pcp-decode)# no pcp-value 7 to priority 3

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

“Default QoS mappings”

on page 79.

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.

Advertising