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

86 Multi-Service IronWare QoS and Traffic Management Configuration Guide
53-1003037-02
Configuring QoS
4
Configuring QoS
The QoS configuration process involves separate procedures for Ingress and Egress QoS
Processing as described in the following major sections.
Configuring Ingress QoS procedures
The following procedures are required to configure a Brocade device for Ingress QoS processing:
• Creating Ingress Decode Policy Maps – If you want the priority and drop precedence values
used within the device to be mapped to a specified value, you must create a Decode Priority
map as described in
“Configuring Ingress decode policy maps” on page 87.
• Binding Ingress Decode Policy Maps – If you want to apply an Ingress Policy Map other than
the default, you must bind the Ingress Policy Map either globally or to a specified interface as
described in
“Binding Ingress decode policy maps” on page 93.
• Configuring a Force priority – Where there are multiple QoS values that can be used to
determine the QoS level used on the device, the default policy is to determine the value used
by performing a merge as described in
“Stage 2 Determine if a priority value should be forced
or merged” on page 74. Otherwise, you can specify a value that you want used from either the
port or VLAN configured value or the DSCP, EXP or PCP values in the packets as described in
“Configuring a force priority” on page 96.
Configuring Egress QoS procedures
The following procedures are required to configure a Brocade device for Egress QoS processing:
• Creating Egress Encode Policy Maps – If you want the priority and drop precedence values of
packets leaving the device to be marked with a specified value, you must create an Encode
Priority map as described in
“Configuring Egress encode policy maps” on page 99.
• Binding Egress Encode Policy Maps – If you want to apply an Egress Policy Map other than the
default, you must bind the Egress Policy Map either globally or to a specified interface as
described in
“Binding an Egress encode EXP policy map” on page 102.
Configuring QoS procedures applicable to Ingress
and Egress
The following procedures are required to configure procedures applicable to both Ingress and
Egress QoS Processing on a Brocade device:
P1 New unassigned protocols.
P0 Existing unassigned protocols: GARP, L2-Trace.
TABLE 27 Network processor prioritized protocol packets (Continued)
Priority categorization Protocols