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

Page 102

Advertising
background image

88

Multi-Service IronWare QoS and Traffic Management Configuration Guide

53-1003037-02

Configuring QoS

4

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 DSCP policy map
Once you have named an Ingress Decode DSCP Policy Map using the dscp decode-map command,
you can set the values of the named Ingress Decode DSCP Policy Map. Setting the values in an
Ingress Decode DSCP Policy Map involves specifying the value of the DSCP 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 DSCP Policy Map, first specify name of the policy map and
then populate the values in the policy map using the dscp-value command as shown in the
following.

Brocade(config)# qos-mapping

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

Brocade(config-qos-mapping-dscp-decode)# dscp-value 32 to priority 5

drop-precedence 2

Syntax: [no] dscp-value dscp-value [dscp-value ] to priority priority-value [drop-precedence

dp-value]

The dscp-value variable specifies the value of the DSCP bits within the packet header of the
incoming packets. You can optionally specify multiple dscp-value variables if you want to specify
more than one value to map to the same internal priority and drop precedence. Where DSCP 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 dscp-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 DSCP 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 “4” and a drop precedence of “2” to Ingress packets that have a DSCP value of “40”.

Brocade(config-qos-mapping-dscp-decode)# dscp-value 40 to priority 4

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-dscp-decode)# no dscp-value 40 to priority 4

Advertising