Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual
Page 176
146
Multi-Service IronWare Switching Configuration Guide
53-1003036-02
LAG formation rules
6
•
Are configured as MRP primary and secondary interfaces.
•
LAG deployment will fail if the LACP BPDU forwarding is disabled on the primary port and
enabled on one or more of the secondary ports.
Layer 3 requirements
The LAG is rejected if any secondary LAG ports have any Layer 3 configuration, such as IPv4s, OSPF,
RIP, RIPng, IS-IS, etc.
Layer 4 (ACL) requirements
•
All LAG ports must have the same ACL configurations; otherwise, the LAG is rejected.
•
A LAG cannot be deployed if a member port has ACL-based mirroring configured.
•
A port with ACL-based mirroring configured cannot be added to a LAG.
•
The device can support from 1-64 manually-configured LAGs.
•
Ports can be in only one LAG group. All the ports in a LAG group must be connected to the
same device at the other end. For example, if port 1/4 and 1/5 in Device 1 are in the same
LAG group, both ports must be connected to ports in Device 2 or in Device 3. You cannot have
one port connected to Device 2 and another port connected to Device 3.
•
All LAG member properties must match the primary port of the LAG with respect to the
following parameters:
•
Port tag type (untagged or tagged port)
•
Port speed and duplex
•
TOS-based configuration – All ports in the LAG must have the same TOS-based QoS
configuration before LAG deployment, During deployment the configuration on the primary
port is replicated to all ports and when deployment is ended, each port inherits the same
TOS-based QoS configuration.
You must change port parameters on the primary port. The software automatically applies the
changes to the other ports in the LAG.
•
Make sure the device on the other end of the LAG group can support the same number of links
in the LAG group.
•
Dynamic LAGs are not supported for ports that are member of a VLAN within an ESI. Static
LAGs are supported in such configurations.
displays an example of a valid, keepalive LAG link between two devices. A keepalive LAG
does not aggregate ports but uses LACP PDUs to check the connection status between the two
devices at either end of a LAG.