User guide

Modifying a QoS Configuration
ExtremeWare 7.2e Installation and User Guide 121
port. Data is captured for a specified port and aggregated over all other ports in the system. The data
leaving the QoS monitor port does reflect the aggregate, but it also reflects the original data captured at
the ingress ports. Even if you attempt to change the priority using an access-list, the QoS monitor still
reflects the statistics before the access-list changed the traffic at the egress port.
For example, incoming traffic on a Summit 400-48t is set as follows:
• Port 2 with 802.1p priority set to 0
• Port 4 with 802.1p priority set to 2
• Port 6 with 802.1p priority set to 4
The traffic is designated to exit the switch at port 24.
If we send 100 packets on each of these ports and change the priority to 7 of all 802.1p, the output of the
show qosmonitor statistics command only displays the original statistics.
QoS Monitor Egress Queue Summary Tuesday Apr 6 17:48:51 2004
Port Q0 Q1 Q2 Q3 Q4 Q5 Q6 Q7
Xmts Xmts Xmts Xmts Xmts Xmts Xmts Xmts
==============================================================================
24 100 0 100 0 100 0 0 0
Displaying QoS Profile Information
The QoS monitor can also be used to verify the QoS configuration and monitor the use of the QoS
policies that are in place. To display QoS information on the switch, use the following command:
show qosprofile {<qosprofile>} {port <portlist>}
Displayed information includes:
• QoS profile name
• Priority
• A list of all ports to which the QoS profile is applied
• A list of all VLANs to which the QoS profile is applied
Additionally, QoS information can be displayed from the traffic grouping perspective by using one or
more of the following commands:
•
show fdb permanent—Displays destination MAC entries and their QoS profiles.
•
show switch—Displays hardware information.
•
show vlan—Displays the QoS profile assignments to the VLAN.
Modifying a QoS Configuration
If you make a change to the parameters of a QoS profile after implementing your configuration, the
timing of the configuration change depends on the traffic grouping involved. The following rules apply:
• For destination MAC-based grouping (other than permanent), clear the MAC FDB using the
command
clear fdb. This command should also be issued after a configuration is implemented, as
the configuration must be in place before an entry is made in the MAC FDB. For permanent