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

110 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
LAG formation rules
5
LAG formation rules
The LAG formation rules are mentioned below:
• The 10Gx24-DM module ports can only be part of LAGs exclusively consisting of 24x10G ports.
A LAG cannot have a mix of 24x10G module ports and any other 10G module ports.
• A port can only be a member of one LAG, and that LAG must be static, dynamic or a keep-alive
LAG.
• The maximum number of port members that may be assigned to a LAG is dependent on the
number of trunks specified by the system-max trunk-num value.
• The system supports up to 64 port IDs for Brocade NetIron CES and Brocade NetIron MLX
devices when snmp-server max-ifindex-per-module 64 is configured.
• All ports configured in a LAG must be of equal bandwidth. For example all 10 G ports.
• All ports configured in a LAG must be configured with the same port attributes.
• LAG formation rules are checked when a static or dynamic LAG is deployed.
• A LAG must have its primary port selected before it can be deployed.
• All ports configured in a LAG must be configured in the same VLAN.
• All ports must have the same PBR configuration before deployment. During deployment, the
configuration on the primary port is replicated to all ports. On undeployment, each port inherits
the same PBR configuration.
• All static LAG ports must have the same LACP BPDU forwarding configuration.
• A LAG member and an individual port cannot use the same name.
• VLAN and inner-VLAN translation
The LAG is rejected if any LAG port has VLAN or inner-VLAN translation configured
• Layer 2 requirements:
The LAG is rejected if the LAG ports:
• Do not have the same untagged VLAN component.
• Do not share the same SuperSpan customer ID (CID).
• Do not share the same VLAN membership or do not share the same uplink VLAN
membership
• Do not share the same protocol-VLAN configuration
• Are configured as mainly primary and secondary interfaces
• Static LAG deployment will fail if the if 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 of the secondary LAG port has any Layer 3 configurations, such as
IPv4 or IPv6 address, OSPF, RIP, RIPNG, IS-IS, and so on.
• Layer 4 (ACL) requirements:
• All LAG ports must have the same ACL configurations; otherwise, the LAG is rejected.
• A LAG cannot be deployed if any of the member ports has ACL-based mirroring configured
on it.
• A port with ACL-based mirroring configured on it cannot be added to a LAG.