Configuring an egress encode pcp policy map – Brocade Multi-Service IronWare QoS and Traffic Management Configuration Guide (Supporting R05.6.00) User Manual
Page 114
100
Multi-Service IronWare QoS and Traffic Management Configuration Guide
53-1003037-02
Configuring QoS
4
To set the values of an Egress Encode DSCP Policy Map, first specify name of the policy map and
then populate the values in the Egress Encode DSCP Policy Map using the priority command as
shown in the following.
Brocade(config)# qos-mapping
Brocade(config-qos-mapping)# dscp encode-map Customer1
Brocade(config-qos-mapping-dscp-encode)# priority 7 drop-precedence 2 to
dscp-value 3
Syntax: [no] priority priority-value [drop-precedence dp-value] [dp-value] to dscp-value dscp-value
The priority keyword together with the priority-value variable specifies the internal priority value that
egress packets will be marked from. The priority-value variable can be a value between 0 and 7. For
unspecified priority values, the default mapping values are used.
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 specify in addition to a priority
priority-value value. The dp-number variable can be a value between 0 and 3. Multiple dp-number
variables can be configured in a single command. The default value is “any” which means that drop
priorities 0 - 3 are assigned. If a drop precedence value is specified only for a subset of values, the
entries with unspecified values will be initialized as specified in the default mapping.
The dscp-value variable specifies the value that will be marked onto the DSCP bits within the
packet header of the outgoing packets. This applies to packets that match the priority and drop
precedence values specified in this command.
The [no] option allows you to negate a previously configured value and return to the default
mapping for the specified priority and drop precedence values.
Configuring an Egress encode PCP policy map
The following procedures are used when configuring an Egress Encode PCP Policy Maps:
•
Naming an Egress Encode PCP Policy Map
•
Configuring an Egress Encode PCP Policy Map
Naming an Egress encode PCP policy map
Once you are in the QoS configuration level, can define the name of an Egress Encode PCP Policy
Map using the pcp encode-map command, as shown in the following.
Brocade(config)# qos-mapping
Brocade(config-qos-mapping)# pcp encode-map Customer1
Syntax: [no] pcp encode-map map-name
The no option is used to delete a currently configured Egress Encode PCP Policy Map. If the 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 Egress Encode PCP Policy Map that you are
defining. It can be up to 64 characters in length. You can specify the same policy map name for
different types of policy maps. For example, you can use the same name for an Egress Encode PCP
Policy Map and an Egress Encode EXP Policy Map.
NOTE
The name “default-map” cannot be used because it is reserved for standard mappings as described
in