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

Multi-Service IronWare QoS and Traffic Management Configuration Guide 49
53-1003037-02
Configuring QoS
3
Configuring extended-qos-mode
The extended-qos-mode command should only be turned on when deploying CES/CER as MPLS PE
devices, if preserving passenger DSCP is required, when terminating VPLS/VLL traffic at the egress
end point.
NOTE
You must write this command to memory and perform a system reload for this command to take
effect.
NOTE
This command will reduce the hardware table size by half. If the existing configuration has already
used more the half of the hardware table size, this command will not succeed. This command will
only succeed if there is sufficient space in the hardware table.
You can revert to normal mode using the no extended-qos-mode command without losing
functionality or behavior.
Brocade(config)# extended-qos-mode
Syntax: [no] extended-qos-mode
Configuring port-level QoS commands on LAG ports
When applying port-level QoS commands to ports in a LAG, the rules can be different according the
configuration as described in the following:
• 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.
• Port-level QoS configurations using commands that begin with the qos keyword. These
commands include: qos dscp decode-policy, qos pcp decode-policy, qos exp decode-policy,
qos dscp force, qos pcp force, qos exp force, qos dscp encode on, and qos pcp encode on.
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)#