Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 160)

130 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
Deploying a LAG
5
Use the port-name option with the appropriate [text] variable to specify the named port within the
LAG that you want to configure the sampling rate for.
The num variable specifies the average number of packets from which each sample will be taken.
The software rounds the value you enter up to the next odd power of 2. This can be a value
between 512 - 1048576.
Configuring a dynamic LAG within a VRF
In release 3.8.00, support was added for dynamic LAGs within a VRF. When configuring a dynamic
LAG within a VRF, the following must be considered:
• The dynamic LAG must be configured before adding it to a VRF.
• Before the LAG is deployed, all members must be in the default VRF.
• After the LAG is deployed, all LAG ports are in the LACP BLOCK state until the LACP protocol
completes negotiation with the other end of the LAG.
• Once the LACP protocol negotiation is completed with the other end of the LAG, all the LAG
ports are set to the FORWARD state.
• When a dynamic LAG within a VRF is undeployed, the primary port will stay in the VRF where
the LAG was configured and the secondary ports of the LAG will return to the default VRF.
The following example uses the LAG and VRF commands to configure a LAG within a VRF.
Brocade(config)# lag red dynamic
Brocade(config-lag-red)# primary-port 3/2
Brocade(config-lag-red)# ports ethernet 3/1 ethernet 7/2
Brocade(config-lag-red)# exit
Brocade(config)# interface ethernet 3/2
Brocade(config-if-e10000-3/2)# vrf forwarding VPN1
Brocade(config)# lag red dynamic
Brocade(config-lag-red)# deploy
Configuring multicast dynamic load rebalancing on a LAG
In multicast, each forwarding (S,G) entry that has a Link Aggregation Group (LAG) port as an
Outgoing Interface (OIF) is allocated only one of the member ports of the LAG for forwarding
purposes. This member port is referred to as the forwarding port of the OIF of the (S,G) entry. A LAG
is said to have balanced Multicast flows if all its member ports carry outgoing traffic for the same
number of forwarding entries.
There are two ways of applying this feature, through a global configuration command that will force
dynamic load rebalancing at all times, or via an exec level command that will trigger dynamic load
rebalancing on demand.
Limitations
• The load balancing metric is determined by the number of forwarding (S,G) entries per LAG
member port. Dynamic rebalancing attempts to balance this metric. This does not necessarily
guarantee that multicast traffic bandwidth (bytes/sec) will be equally balanced across all
member ports.