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

112 Multi-Service IronWare QoS and Traffic Management Configuration Guide
53-1003037-02
Configuring QoS
4
Configuring support for super aggregate VLANs
In a super-aggregate VLAN application, you can optionally configure an untagged interface to copy
the QOS bits from the tag value set by the edge device to the tag value set by the core device. This
is only supported if the incoming packet has ETYPE 0x8100. This can be configured using the qos
decode-cvlan-pcp command as shown in the following.
Brocade(config)# interface ethernet 10/1
Brocade(config-if-e10000-10/1)qos decode-cvlan-pcp
Syntax: [no] qos decode-cvlan-pcp
NOTE
The command aggregated-vlan-copy-cos is available at the physical interface level to copy the COS
value from the internal to the external VLAN tag (for SAV). This command will be automatically
migrated to the new command qos decode-cvlan-pcp.
Configuring port-level QoS commands on LAG ports
When applying port-level QoS commands to ports in a LAG, the rules can differ according the
following:
• For port-level QoS Configurations where QoS Values are Applied Directly to the Port. These
commands include the followings: priority, priority force, drop-precedence, drop-precedence
force.
• For Port-level QoS configurations using commands that begin with the qos keyword. These
commands include: qos use-dei, qos dscp decode-policy, qos pcp decode-policy, qos exp
decode-policy, qos dscp force, qos pcp force, qos exp force, qos dscp encode-policy, qos pcp
encode-policy, and qos exp encode-policy.
LAG configuration rules where QoS values are applied directly to the port
In port-level QoS Configurations where QoS values are applied directly to the port, the
considerations listed below must be followed.
1. Each port that is configured into the LAG, must have the same priority, priority force,
drop-precedence, and drop-precedence force configuration.
If you try to configure a LAG with ports that have a different configuration for these commands,
the LAG deployment will fail and you will get an error message as shown in the following.
Brocade(config)# lag mylag static
Brocade(config-lag-mylag)# ports eth 10/1 to 10/2
Brocade(config-lag-mylag)# primary 10/1
Brocade(config-lag-mylag)# deploy
port 10/1 priority is 5, but port 10/2 priority is 0
Error: port 10/1 and port 10/2 have different configurations
LAG mylag deployment failed!
Brocade(config-lag-mylag)#
2. If you have already formed a LAG with the same configuration, you can change the
configuration by making changes to the LAG’s primary port.
3. If the LAG configuration is deleted, each of the port in the LAG (primary and secondary) will
inherit the QoS configuration of the primary port.