The document conventions describe text formatting conventions, command syntax conventions, and
important notice formats used in Brocade technical documentation.
Text formatting conventions
Text formatting conventions such as boldface, italic, or Courier font may be used in the flow of the text
to highlight specific words or phrases.
Format
bold text
italic text
Courier font
Description
Identifies command names
Identifies keywords and operands
Identifies the names of user-manipulated GUI elements
Identifies text to enter at the GUI
Identifies emphasis
Identifies variables and modifiers
Identifies paths and Internet addresses
Identifies document titles
Identifies CLI output
Identifies command syntax examples
Command syntax conventions
Bold and italic text identify command syntax components. Delimiters and operators define groupings of
parameters and their logical relationships.
Convention
bold textIdentifies command names, keywords, and command options.
valueIn Fibre Channel products, a fixed value provided as input to a command
option is printed in plain text, for example, --show WWN.
[ ]
{x| y| z}
x | y
< >
...
\
Syntax components displayed within square brackets are optional.
Default responses to system prompts are enclosed in square brackets.
A choice of required parameters is enclosed in curly brackets separated by
vertical bars. You must select one of the options.
In Fibre Channel products, square brackets may be used instead for this
purpose.
A vertical bar separates mutually exclusive elements.
Nonprinting characters, for example, passwords, are enclosed in angle
brackets.
Repeat the previous element, for example, member[member...].
Indicates a “soft” line break in command examples. If a backslash separates
two lines of a command input, enter the entire command at the prompt without
the backslash.
Notes, cautions, and warnings
Notes, cautions, and warning statements may be used in this document. They are listed in the order of
increasing severity of potential hazards.
NOTE
A Note provides a tip, guidance, or advice, emphasizes important information, or provides a reference
to related information.
ATTENTION
An Attention statement indicates a stronger note, for example, to alert you when traffic might be
interrupted or the device might reboot.
CAUTION
A Caution statement alerts you to situations that can be potentially hazardous to you or cause
damage to hardware, firmware, software, or data.
DANGER
A Danger statement indicates conditions or situations that can be potentially lethal or
extremely hazardous to you. Safety labels are also attached directly to products to warn of
these conditions or situations.
Visit the Brocade website to locate related documentation for your product and additional Brocade
resources.
You can download additional publications supporting your product at www.brocade.com. Select the
Brocade Products tab to locate your product, then click the Brocade product name or image to open the
individual product page. The user manuals are available in the resources module at the bottom of the
page under the Documentation category.
To get up-to-the-minute information on Brocade products and resources, go to MyBrocade. You can
register at no cost to obtain a user ID and password.
Release notes are available on MyBrocade under Product Downloads.
White papers, online demonstrations, and data sheets are available through the Brocade website.
Getting technical help
Brocade resources
You can contact Brocade Support 24x7 online, by telephone, or by e-mail.
For product support information and the latest information on contacting the Technical Assistance
Center, go to http://www.brocade.com/services-support/index.html.
Use one of the following methods to contact the Brocade Technical Assistance Center.
OnlineTelephoneE-mail
Preferred method of contact for nonurgent issues:
•My Cases through MyBrocade
•Software downloads and
licensing tools
•Knowledge Base
Document feedback
Required for Sev 1-Critical and Sev
2-High issues:
•Continental US:
1-800-752-8061
•Europe, Middle East, Africa,
and Asia Pacific: +800-AT
FIBREE (+800 28 34 27 33)
•For areas unable to access toll
free number: +1-408-333-6061
•Toll-free numbers are available
in many countries.
support@brocade.com
Please include:
•Problem summary
•Serial number
•Installation details
•Environment description
To send feedback and report errors in the documentation you can use the feedback form posted with
the document or you can e-mail the documentation team.
Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and
completeness of this document. However, if you find an error or an omission, or you think that a topic
needs further development, we want to hear from you. You can provide feedback in two ways:
•Through the online feedback form in the HTML documents posted on www.brocade.com.
•By sending your feedback to documentation@brocade.com.
Provide the publication title, part number, and as much detail as possible, including the topic heading
and page number if applicable, as well as your suggestions for improvement.
● About This Document........................................................................................................9
● What’s new in this document.......................................................................................... 10
● How command information is presented in this guide.....................................................10
About This Document
Introduction
This guide includes procedures for configuring the software. The software procedures show how to
perform tasks using the CLI. This guide also describes how to monitor Brocade products using statistics
and summary screens.
Supported Hardware
This guide supports the following product families from Brocade:
•FastIron X Series devices (chassis models):
‐FastIron SX 800
‐FastIron SX 1600
•Brocade FCX Series (FCX) Stackable Switch
•Brocade ICX™ 6610 (ICX 6610) Stackable Switch
•Brocade ICX 6430 Series (ICX 6430)
•Brocade ICX 6450 Series (ICX 6450)
•Brocade ICX 6650 Series (ICX 6650)
•Brocade TurboIron 24X Series
•Brocade ICX 7750 Series (ICX 7750)
For information about the specific models and modules supported in a product family, refer to the
hardware installation guide for that product family.
NOTE
The Brocade ICX 6430-C switch supports the same feature set as the Brocade ICX 6430 switch unless
otherwise noted.
NOTE
The Brocade ICX 6450-C12-PD switch supports the same feature set as the Brocade ICX 6450 switch
unless otherwise noted.
This document includes the information from FastIron software release 08.0.10b.
Summary of Enhancements in FastIron release 08.0.10bTABLE 1
FeatureDescriptionLocation
A new command has been added:
store-and-forward.
Support for Outbound rate
shaping.
The store-and-forward command
changes the switch mode to store-andforward.
Outbound rate shaping is supported
on ICX 7750 devices.
See store-and-forward on page
94.
See Configuring outbound rate
shaping for a LAG port on page 52
and Configuration notes for rate
shaping on page 50.
How command information is presented in this guide
For all new content, command syntax and parameters are documented in a separate command
reference section at the end of the publication.
In an effort to provide consistent command line interface (CLI) documentation for all products, Brocade
is in the process of preparing standalone Command References for the IP platforms. This process
involves separating command syntax and parameter descriptions from configuration tasks. Until this
process is completed, command information is presented in two ways:
•For all new content included in this guide, the CLI is documented in separate command pages.
The new command pages follow a standard format to present syntax, parameters, usage
guidelines, examples, and command history. Command pages are compiled in alphabetical order
in a separate command reference chapter at the end of the publication.
•Legacy content continues to include command syntax and parameter descriptions in the chapters
where the features are documented.
If you do not find command syntax information embedded in a configuration task, refer to the
command reference section at the end of this publication for information on CLI syntax and usage.
Lists the the individual BrocadeFastIron switches and the Quality of Service (QoS) features they
support.
The following table lists the individual BrocadeFastIron switches and the Quality of Service (QoS)
features they support. These features are supported in the Layer 2 and Layer 3 software images,
except where explicitly noted.
FeatureICX 6430ICX 6450FCXICX 6610ICX 6650FSX 800
FSX 1600
802.1p Quality of Service (QoS): Strict
Priority (SP), Weighted Round Robin
(WRR), Combined SP and WRR, 8
priority queues
Quality of Service (QoS) features are used to prioritize the use of bandwidth in a switch. When QoS
features are enabled, traffic is classified as it arrives at the switch, and processed through on the basis
of configured priorities. Traffic can be dropped, prioritized for guaranteed delivery, or subject to limited
delivery options as configured by a number of different mechanisms.
This chapter describes how QoS is implemented and configured in FastIron devices.
Classification is the process of selecting packets on which to perform QoS, reading the QoS
information, and assigning a priority to the packets. The classification process assigns a priority to
packets as they enter the switch. These priorities can be determined on the basis of information
contained within the packet or assigned to the packet as it arrives at the switch. Once a packet or
traffic flow is classified, it is mapped to a forwarding priority queue.
Packets on Brocade devices are classified in up to eight traffic classes with values from 0 to 7.
Packets with higher priority classifications are given a precedence for forwarding.
ICX 7750
08.0.10
Processing of classified traffic
The trust level in effect on an interface determines the type of QoS information the device uses for
performing QoS. The Brocade device establishes the trust level based on the configuration of various
features and whether the traffic is switched or routed. The trust level can be one of the following:
•Ingress port default priority.
•Static MAC address.
•Layer 2 Class of Service (CoS) value - This is the 802.1p priority value in the Ethernet frame. It
can be a value from 0 through 7. The 802.1p priority is also called the Class of Service .
•Layer 3 Differentiated Services Code Point (DSCP) - This is the value in the six most significant
bits of the IP packet header 8-bit DSCP field. It can be a value from 0 through 63. These values
are described in RFCs 2472 and 2475. The DSCP value is sometimes called the DiffServ value .
The device automatically maps the DSCP value of a packet to a hardware forwarding queue.
Refer to Viewing QoS settings on page 41.
•ACL keyword - An ACL can also prioritize traffic and mark it before sending it along to the next
hop. This is described under "QoS options for IP ACLs" section in the FastIron Ethernet SwitchSecurity Configuration Guide .
Given the variety of different criteria, there are many possibilities for traffic classification within a
stream of network traffic. For this reason, the priority of packets must be resolved based on which
criteria takes precedence. Precedence follows the schemes illustrated in the Determining a packettrust level - FSX devices through Determining a packet trust level - FCX, and ICX devices figures.
Determining the trust level of a packet
Packet trust level is determined differently on FSX devices than on FCX, and ICX series devices.
The following figure illustrates how FSX devices determine the trust level of a packet.
The Determining a packet trust level - FSX devices figure is not applicable to the third generation FSX
interface modules. To determine the trust level of a packet for the SX-FI48GPP, SX-FI-24GPP, SXFI-24HF, SX-FI-2XG, and SX-FI-8XG modules, refer to the Determining a packet trust level - SX-FI48GPP, SX-FI-24GPP, SX-FI-24HF, SX-FI-2XG, and SX-FI-8XG modules figure.
As shown in the flowchart, the first criteria considered is whether the packet matches on an ACL that
defines a priority. Next, it checks if trust DSCP is enabled on the port. If this is not the case, the packet
is next classified based on the static MAC address. If this is not true and the packet is tagged, the
packet is classified with the 802.1p CoS value. If none of these is true, the packet is next classified
based on the ingress port default priority or the default priority of zero (0).
FIGURE 1 Determining a packet trust level - FSX devices
The Determining a packet trust level - SX-FI48GPP, SX-FI-24GPP, SX-FI-24HF, SX-FI-2XG, and SXFI-8XG modules figure illustrates how the SX-FI48GPP, SX-FI-24GPP, SX-FI-24HF, SX-FI-2XG, and
SX-FI-8XG modules determine the trust level of a packet. The marking process for these modules is
similar to the marking process for other FastIron SX modules. However, there are major differences
between these modules and other FastIron SX modules.
•For the SX-FI48GPP, SX-FI-24GPP, SX-FI-24HF, SX-FI-2XG, and SX-FI-8XG modules, static
MAC priority takes higher precedence than VLAN priority. For other FastIron SX modules, VLAN
priority takes higher precedence over static MAC priority.
•For other FastIron SX modules, the priority of the dynamically learned MAC address is inherited
from the default port priority. For the SX-FI48GPP, SX-FI-24GPP, SX-FI-24HF, SX-FI-2XG, and
SX-FI-8XG modules, the priority of the dynamically learned MAC address is not inherited from the
default port priority because it is not desirable to allow the port priority to take precedence over
the VLAN priority. All dynamically learned MAC addresses are assigned a priority of 0 in the SX-
FI48GPP, SX-FI-24GPP, SX-FI-24HF, SX-FI-2XG, and SX-FI-8XG modules. Therefore, configuring
a static MAC with a priority of 0 has no effect on QoS marking.
FIGURE 2 Determining a packet trust level - SX-FI48GPP , SX-FI-24GPP, SX-FI-24HF, SX-FI-2XG,
and SX-FI-8XG modules
The following figure illustrates how FCX, and ICX series devices determine the trust level of a packet.
As shown in the flowchart, the first criteria considered is whether the packet matches on an ACL that
defines a priority. If this is not the case and the MAC address of the packet matches a static entry, the
packet is classified with the priority of the static MAC entry. If neither of these is true, the packet is next
Once a packet is classified, it is mapped to a forwarding queue. For all products except the SXF148GPP interface module and ICX 6430 switch, there are eight queues designated from 0 through 7.
The internal forwarding priority maps to one of these eight queues. For the SX-Fl48GPP interface
module and ICX 6430 switch, internal forwarding priority maps to four forwarding queues. The mapping
between the internal priority and the forwarding queue cannot be changed.
The following tables show the default QoS mappings for FCX platforms that are used if the trust level for
CoS or DSCP is enabled. For information on the SX-Fl48GPP interface module, refer to Queues for the
SX-FI48GPP interface module on page 20. For information on default QoS mappings for the ICX 6430
switch, refer to Queues for the ICX 6430 switch on page 22.
Mapping between the DSCP value and forwarding queue cannot be changed. However, mapping
between DSCP values and other properties can be changed as follows:
•DSCP to internal forwarding priority mapping - You can change the mapping between the
DSCP value and the internal forwarding priority value from the default values shown in the above
tables. This mapping is used for CoS marking and determining the internal priority when the trust
level is DSCP. Refer to Changing the DSCP to internal forwarding priority mappings on page 34.
•VLAN priority (802.1p) to hardware forwarding queue - You can change the mapping between the
802.1p value and hardware forwarding queue from the default value. Refer to Changing the VLAN
priority 802.1p to hardwareforwarding queue mappings on page 35.
QoS for Brocade stackable devices
Brocade FastIron units in a traditional stack support QoS. Units in a stack communicate the stack
topology information and other proprietary control information through the stacking links. For more
information about stacking links and traditional stack technology, refer to the FastIron Ethernet SwitchStacking Configuration Guide .
In addition to control information, the stacking links also carry user network data packets. In a traditional
stack topology, the priority of stacking-specific control packets is elevated above that of data path
packets, preventing loss of control packets, and timed retries that affect performance. This prioritization
also prevents stack topology changes that may occur if enough stack topology information packets are
lost.
Traditional stack technology reserves one QoS profile to provide a higher priority for stack topology and
control traffic.
QoS for Brocade stackable devices
QoS profile restrictions in a traditional stack
In a stacking topology, because CoS level 7 is reserved for stacking, quality profiles for qosp7 cannot
be configured. If an attempt is made to configure a profile for qosp7, the system ignores the
configuration.
NOTE
This applies only when the device is operating in stacking mode. It does not apply to stand-alone
devices.
QoS behavior for trusting Layer 2 (802.1p) in a traditional stack
By default, Layer 2 trust is enabled. Because priority 7 is reserved for stacking control packets, any
ingress data traffic with priority 7 is mapped to internal hardware queue 6. All other priorities are
mapped to their corresponding queues.
QoS behavior for trusting Layer 3 (DSCP) in a traditional stack
When the trust dscp mode is enabled, packets arriving with DSCP values 56 to 63 are mapped to
internal hardware queue 6. All other DSCP values are mapped to their corresponding internal hardware
queues.
QoS behavior on port priority and VLAN priority in a traditional stack
Port priority has a higher precedence than the 802.1p priority examination. If port priority is set to 7, all
incoming traffic is mapped to internal hardware queue 6.
QoS behavior for 802.1p marking in a traditional stack
When stacking is not enabled on a device, all priorities are mapped to their corresponding queues
without restrictions.
QoS behavior for 802.1p marking in a traditional stack
By default, 802.1p marking is not enabled in a traditional stack. Outgoing tagged traffic will not be
marked based on the hardware queue into which ingress traffic was classified. 802.1p marking can be
achieved using ACL. For configuration syntax, rules, and examples of QoS marking, refer to the "QoS
options for IP ACLs" section in the FastIron Ethernet Switch Security Configuration Guide .
QoS queues
Brocade devices support the eight QoS queues (qosp0 through qosp7) listed in the following table.
QoS queues TABLE 6
QoS priority levelQoS queue
0qosp0 (lowest priority queue)
1qosp1
2qosp2
3qosp3
4qosp4
5qosp5
6qosp6
7qosp7 (highest priority queue)
The queue names listed in the table are the default names. If desired, you can rename the queues as
shown in Renaming the queues on page 39.
Packets are classified and assigned to specific queues based on the criteria shown in the figures
described in the Determining the trust level of a packet section.
For FCX and ICX devices, ingress packets are classified into the eight priorities, which map to eight
hardware queues or traffic classes (TCs) based on the priority. Exceptions to this model are the SXFI48GPP and SX-FI-8XG interface modules and the ICX 6430 switch as explained in the following
sections.
Queues for the SX-FI48GPP interface module
The SX-FI48GPP interface module consists of two separate hardware Network Processors (NPs). The
front-end NP supports four hardware queues, and the back-end NP supports eight hardware queues.
Ingress packets are classified into eight priorities mapped into four hardware queues. In the egress,
traffic is destined to two adjacent network ports (for example, ports 1/1 and 1/2), and aggregated into
one 1-GbE port in the back-end NP. The two network ports share the same hardware queues, and
therefore they have the same buffer and descriptor limits and scheduling algorithm for transmission.
Ingress packets are classified into eight QoS priority levels at the front-end NP of the SX-FI48GPP
module. The eight priorities are mapped into four hardware queues based on the priority queue
configuration in the following table. QoS priority 7 is the highest priority, and QoS 0 is the lowest priority.
Priority queues for the SX-F148GPP TABLE 7
QoS priority levelHardware queues
(traffic classes)
00
10
21
31
42
52
63
73
QoS classification occurs in two iterations; initially in the front-end NP, followed by the back-end NP.
The back-end NP has the same classification and marking capabilities of existing FastIron SX interface
modules, but the front-end NP does not support ACL and static MAC priority. The front-end NP supports
basic QoS features, such as port priority, QoS-ToS mapping, 802.1p to priority mapping, 802.1p
override, and trust DSCP mode.
The default scheduling configuration for Weighted Round Robin (WRR), Hybrid WRR and Strict Priority
(SP), and SP mode for the eight QoS priority queues mapped to the four hardware queues is described
under Default scheduling configuration for the SX-FI48GPP module on page 36.
Queues for the SX-FI-8XG interface module
The SX-FI-8XG interface module consists of two separate hardware Network Processors (NP). The
front-end NP supports 8 hardware queues, and the back-end NP supports eight hardware queues. In
the egress, traffic is destined to four adjacent ports (for example, ports 1/1 to 1/4), and aggregated into
one 10GbE port in the back-end NP. The four network ports share the same hardware queues;
therefore, they have the same buffer and descriptor limits and scheduling algorithm for transmission.
QoS classification occurs in two iterations; initially in the front-end NP, followed by the back-end NP.
The back-end NP has the same classification and marking capabilities of existing FSX interface
modules, however, the front -end NP does not support ACL and static MAC priority. The front-end NP
supports basic QoS features, such as port priority, qos-tos mapping, 802.1p to priority mapping, 802.1p
override, and trust-dscp mode.
For the ICX 6430 switch, ingress packets are classified into eight QoS priority levels. These are
mapped internally to four hardware forwarding queues or traffic classes as shown in the following
table. QoS priority 7 is the highest priority, and QoS 0 is the lowest QoS priority (qosp) level.
QoS priority levelHardware queues
00
10
21
31
41
Priority queues for the ICX 6430 TABLE 8
(Traffic classes)
52
62
73
For the ICX 6430 switch, internal forwarding priority maps to hardware forwarding queues 0 through 3.
The mapping between the internal priority and hardware forwarding queue cannot be changed. The
following tables show the default QoS mappings that are used if the trust level for CoS or DSCP is
enabled. Mappings are the same for stand-alone and stacking systems.
Default QoS mappings for ICX 6430, columns 0 to 15 TABLE 9
DSCP value0 1234 5678 9101112121415
802.1p (CoS) value0 0000 0001 1111111
DSCP value01 2345 6789 101112121415
Internal forwarding priority0 0000 0001 1111111
Forwarding queue0 0000 0000 0000000
Default QoS mappings for ICX 6430, columns 16 to 31 TABLE 10
Mapping between DSCP value and forwarding queue cannot be changed. However, mapping between
DSCP values and other properties can be changed as follows:
•DSCP to internal forwarding priority mapping - You can change the mapping between the
DSCP value and the internal forwarding priority value from the default values shown in the above
tables. This mapping is used for CoS marking and determining the internal priority when the trust
level is DSCP. Refer to Changing the DSCP to internal forwarding priority mappings on page 34.
•VLAN priority (802.1p) to hardware forwarding queue - You can change the mapping between the
802.1p value and hardware forwarding queue from the default value. Refer to Changing the VLAN
priority 802.1p to hardwareforwarding queue mappings on page 35
User-configurable scheduler profile
The user-configurable scheduler profile is a template that defines either the scheduling mechanism or
scheduling profile (weights assigned to the queues) or both for the egress queues. A configured userconfigurable scheduler profile for egress queues can be applied to any hardware device. The default
QoS is applicable to the entire system. If the scheduler profile is configured using the qos mech strict
command, all devices in the system will be configured with the strict priority. The user-configurable
scheduler profile is applicable only to the specific devices, leaving the remaining devices running default
QoS. On any device, the user-configurable scheduler profile has high priority over the default QoS. On
any device, user-configurable scheduler profile has high priority over the default QoS. The userconfigurable scheduler profile should be in line with default QoS commands in both stacking and standalone systems.
On Brocade ICX 7750 devices, scheduler profiles are applied at the port, rather than at the device
(port region), level. See the description of the scheduler-profile command for more information.
User-configurable scheduler profile configuration
Configuring a user-configurable scheduler profile involves, selecting a proper mechanism and
appropriate weights for the traffic classes (TCs) corresponding to that mechanism. It is highly
recommended that you let the system use the default scheduling mechanism unless user knows what
parameters you intend to modify and for what reasons.
There are two ways of creating a user-configurable scheduler profile. The scheduler-profile can be
created either by specifying a mechanism (WRR, Strict, or Mixed) or by specifying weights.
The user-configurable scheduler profile can be created by specifying a mechanism. There are three
available mechanisms:
•Strict Priority (SP)
•Weighted Round Robin (WRR)
•Mixed (combination of SP and WRR)
Following is the command format for creating a profile while specifying a mechanism.
The user_profile_name variable is the name of the profile you are creating.
Profile qosp0 through qosp7 are the default queue names.
The w0 through w7 variables are the assigned weights.
If you create a profile specifying only the weights (qosp0 through qosp7) without specifying the
mechanism, the default mechanism is used. The default mechanism for stacking systems is Mixed ,
and WRR for stand-alone systems.
If you change the profile mechanism, the weights also get changed according to the mechanism. The
weights can be modified according to the following requirements:
•If the mechanism is changed to WRR , the default system weights get assigned
•If the mechanism is changed to Mixed , the default mix weights get assigned
•If the mechanism is changed to Strict , the weights are ignored and remain untouched.
Scheduler-profile modifications take effect dynamically on an active profile. The operational defaults
for all scheduling types for stacking and stand-alone systems are listed in the Default values forscheduling type for stacking and stand-alone systems (for FCX and ICX 6450 platforms) table.
Displaying the user-configurable scheduler profile configuration
To display the specified user-configurable scheduler profile configuration, use the show scheduler profileuser_profile_name command.
The user_profile_name variable is the name of the profile you are creating.
The following tables show the default values for the scheduling type for ICX 6650 platforms.
Default values for scheduling type for ICX 6650 platformsTABLE 15
SPSP JumboWRRWRR JumboMixedMixed Jumbo
TC0SPSP381515
TC1SPSP381515
TC2SPSP381515
TC3SPSP381515
TC4SPSP381515
TC5SPSP382525
TC6SPSP78SPSP
TC7SPSP7544SPSP
ICX 6430 platforms
The following table shows the default values for scheduling type for stacking and stand-alone ICX
6430 platforms. The lowest weighted priority is for qosp0, while the highest is for qosp7.
Note that values are provided for QoS priority (QSP) levels. The weights applied to the traffic class
(TC) are the sum of the weights of the QSP levels that map to that TC. For example, QSP0 and QSP1
map to TC0. If the weight for QSP0 is 6 and the weight for QSP1 is 6, then the weight for TC0 is 12.
Refer to the Priority queues for the ICX 6430 table for QoS priority to traffic class mapping.
Default values for scheduling type for stacking systems (for ICX 6430 platforms)TABLE 16
Default values for scheduling type for stacking systems (for ICX 6430 platforms)
(Continued)
Default values for scheduling type for stand-alone systems (for ICX 6430 platforms)TABLE 17
SPSP JumboWRRWRR JumboMixedMixed Jumbo
QSP7SPSP7544SPSP
QoS priorities-to-traffic assignment
By default, all traffic is in the best-effort queue (qosp0) and is honored on tagged ports on all FastIron
switches. You can assign traffic to a higher queue based on the following:
•Incoming port (sometimes called the ingress port )
•Static MAC entry
When you change the priority, you specify a number from 0 through 7. The priority number specifies the
IEEE 802.1 equivalent to one of the eight QoS queues on Brocade devices. The numbers correspond to
the queues as shown in the QoS queues table.
Although it is possible for a packet to qualify for an adjusted QoS priority based on more than one of the
criteria, the system always gives a packet the highest priority for which it qualifies. Thus, if a packet is
entitled to the premium queue because of its IP source and destination addresses, but is entitled only to
the high queue because of its incoming port, the system places the packet in the premium queue on the
outgoing port.
Changing a port priority
To change the QoS priority of port 1/1 to the premium queue (qosp7), enter the following commands.
Use the following command to configure a MAC entry and assign the entry to a priority queue.
Syntax:[no] static-mac-address mac-addr ethernet port [ prioritynum ]
The mac-addr is the MAC address.
The prioritynum variable can be from 0 through 7 and specifies the IEEE 802.1 equivalent to one of
the eight QoS queues.
Buffer allocation and threshold for QoS queues
By default, Brocade IronWare software allocates a certain number of buffers to the outbound transport
queue for each port based on QoS priority. The buffers control the total number of packets permitted in
the outbound queue for the port. If desired, you can increase or decrease the maximum number of
outbound transmit buffers allocated to all QoS queues, or to specific QoS queues on a port or group of
ports. For more information, refer to the FastIron Ethernet Switch Platform and Layer 2 SwitchingConfiguration Guide.
NOTE
On ICX 6650 devices, you cannot increase or decrease the maximum number of outbound transmit
buffers allocated to all QoS queues, or to specific QoS queues on a port or group of ports.
802.1p priority override
You can configure a port to ignore the 802.1p priority for traffic classification for an incoming packet.
When this feature is enabled, packets will be classified as follows:
•If the packet matches an ACL that defines the priority, then ACL priority will be used.
•If the packet source or destination MAC address matches a configured static MAC address with
priority, then static MAC priority will be used.
•If the ingress port has a configured priority, then port priority will be used.
•If the other situations do not apply, the configured or default port priority (0) will be used.