beautypg.com

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

Page 101

background image

Multi-Service IronWare QoS and Traffic Management Configuration Guide

87

53-1003037-02

Configuring QoS

4

Enabling a Port to Use the DEI bit – You can configure the device to use the DEI bit when
computing the drop precedence value for an incoming packet or encoding the DEI bit for
transmitted frame as described in

“Enabling a port to use the DEI bit for Ingress and Egress

processing”

on page 107.

Specifying the Trust Level and Enabling Marking – If you want to use the qos-tos trust and
qos-tos mark commands from pre-03.8.00 versions of the QoS feature, refer to

“Specifying the

trust level and enabling marking”

on page 108.

Support for Super Aggregate VLANS – If you want to use the enhanced QoS feature with Super
Aggregate VLANs, refer to

“Configuring support for super aggregate VLANs”

on page 112.

Support for QoS Configurations on LAG Ports – If you are configuring the enhanced QoS
feature on ports within a LAG, refer to

“Configuring port-level QoS commands on LAG ports”

on

page 112.

Configuring Ingress decode policy maps

Ingress Decode Policy Maps are created globally and are applied later either globally for all ports on
a device or locally to specific port. To create an Ingress Decode Policy Map, you must first enter the
QoS mapping configuration level of the command interface using the qos-mapping command, as
shown in the following.

Brocade(config)# qos-mapping

Configuration of each of the decode and encode mappings is described in the following sections:

Configuring Ingress Decode DSCP Policy Maps

Configuring Ingress Decode PCP Policy Maps

Configuring Ingress Decode EXP Policy Maps

Configuring Ingress decode DSCP policy maps

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

Naming an Ingress Decode DSCP Policy Map

Configuring an Ingress Decode DSCP Policy Map

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

Brocade(config)# qos-mapping

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

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

The no option is used to delete a currently configured Ingress Decode DSCP Policy Map. If the
Ingress Decode DSCP 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 DSCP Policy Map that you are
defining. It can be up to 64 characters in length. You can specify the same map-name for different
types of policy maps. For example, you can use the same name for an Ingress Decode DSCP Policy
Map and a Ingress Decode EXP Policy Map.