Configuration restrictions and guidelines
The following information describes restrictions and guidelines that you must follow when you configure link aggregations.
Aggregation member interface restrictions
When a port on one of the following types of module is assigned to an aggregation group, the other member ports must be on the same type of module.
FIP-240 (JH137A)/FIP-300 (JG671A)/FIP-310 (JG672A) module.
FIP-600 (JG360A) module.
SAP-4EXP (JG366A) module.
You cannot assign an interface to a Layer 2 aggregation group if any features inTable 4 are configured on the interface.
Table 4: Features incompatible with Layer 2 aggregation member interfaces
Feature on the interface
Reference
Port security
Port security in Security Configuration Guide
Service instance bound to a cross connect
MPLS L2VPN in MPLS Configuration Guide
Service instance bound to a VSI
VPLS in MPLS Configuration Guide
You cannot assign an interface to a Layer 3 aggregation group if any features inTable 5are configured on the interface.
Table 5: Features incompatible with Layer 3 aggregation member interfaces
Interface type
Reference
Interface bound to a cross connect
MPLS L2VPN in MPLS Configuration Guide
Interface bound to a VSI
VPLS in MPLS Configuration Guide
Do not assign a reflector port for port mirroring to an aggregation group. For more information about reflector ports, see Network Management and Monitoring Configuration Guide.
Layer 3 Ethernet subinterface restrictions
For a Layer 3 aggregate interface, the member interfaces in the aggregation group must be Layer 3 Ethernet interfaces or subinterfaces, but not both.
If you are assigning a Layer 3 Ethernet interface to an aggregation group, make sure it does not have subinterfaces. You cannot create subinterfaces on a Layer 3 Ethernet interface after it is assigned to an aggregation group.
If you are assigning a Layer 3 Ethernet subinterface to an aggregation group, follow these restrictions and guidelines:
You cannot assign Layer 3 Ethernet subinterfaces on a FIP-600 (JG360A) or SAP-4EXP (JG366A) module to a aggregation group.
Configure VLAN termination before you assign the subinterface to the aggregation group. You cannot modify the VLAN termination configuration after the subinterface is assigned to an aggregation group. The following are VLAN termination commands you might use:
vlan-type dot1q default
vlan-type dot1q untagged
vlan-type dot1q vid
vlan-type dot1q vid second-dot1q
For information about the VLAN termination commands, see "VLAN termination commands."
All Layer 3 Ethernet subinterfaces in an aggregation group must have the same VLAN termination configuration.
If you are assigning a subinterface to a dynamic aggregation group, specify only the outer VLAN ID when you use the vlan-type dot1q vid vlan-id-list [ loose ] command on that subinterface.
For a Layer 3 aggregate interface, aggregate subinterfaces and Layer 3 subinterfaces cannot coexist.
You cannot create aggregate subinterfaces on a Layer 3 aggregate interface if its aggregation group contains Layer 3 Ethernet subinterfaces.
You cannot assign Layer 3 Ethernet subinterfaces to an aggregation group if its aggregate interface has aggregate subinterfaces.
Configuration consistency requirements
You must configure the same aggregation mode at the two ends of an aggregate link.
For a successful static aggregation, make sure the ports at both ends of each link are in the same aggregation state.
For a successful dynamic aggregation, make sure the peer ports of the ports aggregated at one end are also aggregated. The two ends can automatically negotiate the aggregation state of each member port.
Miscellaneous
Deleting an aggregate interface also deletes its aggregation group and causes all member ports to leave the aggregation group.