Brocade MLX Series and NetIron Family (Supporting Multi-Service IronWare R05.6.xx) - Manual (Page 23)

Brocade MLX Series and NetIron Family Documentation Updates 15
53-1003301-07
HQoS for LAG traffic overview
1
Checking for HQoS for VPLS configurations on ports
Example 1:
Brocade #show run int e 3/3
interface ethernet 3/3
hqos service-policy output policy-1
hqos-map flow-1-1.flow-2-1.flow-3-1 match vpls 5000 peer 1.1.1.2
enable
After a successful configuration on PE11, the show command output indicates that HQoS will be
applied to traffic coming from VPLS 5000 endpoint and going to VPLS peer 1.1.1.2 on the MPLS
interface eth 3/3.
Example 2:
Brocade #show run int e 4/1
interface ethernet 4/1
hqos service-policy output policy-1
hqos-map flow-1-1.flow-2-1.flow-3-1 match vlan 100
enable
After a successful configuration on PE11, the show command output indicates that HQoS will be
applied to traffic coming from peer 1.1.1.2 and going to VPLS 5000 endpoint, interface eth 4/1.
HQoS for LAG traffic overview
This feature allows you to support HQoS for LAG traffic, where the traffic could be to or from the
VPLS cloud. The HQoS map is applied on the MPLS uplink. Traffic coming from a VPLS end-point
that is part of a LAG, and going out of the MPLS uplink will be processed for HQoS.
Feature highlights
HQoS over LAG is supported for VPLS Endpoint, Local VPLS, and MPLS VPLS Uplink.
• When LAG is undeployed, the HQoS Configuration on the primary and all secondary ports will
be retained.
• Addition of a new port to the LAG is allowed, if and only if, the HQoS Configuration of the newly
added port is identical to that of the primary port of the deployed LAG.
• Removal of a port from the deployed LAG with HQoS configuration will retain the HQoS
Configuration on the port which is being removed from the LAG.
• Before the HQoS configuration is applied on the primary port of a deployed LAG, and the
configuration is replicated on all the secondary ports of the LAG, the following checks are
made.
• It is ensured that the resources are available (per TM).
• All member ports are 8x10G ports that support HQoS when the policy is applied. Different
kinds of 10G ports are not mixed.
• If the member port list contains ports that are not HQoS capable, the CLI command flags
an error and disallows the command execution.
• When unbinding an HQoS policy from a port, HQoS policy is removed from all member
ports and resources are de-allocated from all the member ports.