This Article Applies to:

 

Omada switch with Static LAG and LACP supported.

 

Issue Description:

 

Static LAG or LACP does not link up or aggregate the speed.

 

Troubleshooting:

 

When LACP (Link Aggregation Control Protocol) or static LAG (Link Aggregation Group) is not functioning properly, common troubleshooting steps and checkpoints include:

 

1. Check Physical Connections:

 

Ensure that the aggregated ports are correctly connected to the corresponding devices, with no loose or damaged connections.

 

2. Port Status:

Confirm that the status of the participating ports is "up." You can check the port status using commands like show interfaces status.

 

3. Configuration Consistency:

Ensure that all ports participating in the aggregation have consistent configurations, including speed, duplex mode, and VLAN settings. LACP requires all ports to have the same configuration.

 

4. LACP Mode:

If using LACP, check the LACP mode (active or passive) to ensure that at least one end is in active mode to facilitate negotiation.

 

5. Device Compatibility:

Confirm that the connected devices support LACP (if using LACP) and that they are configured correctly.

 

6. Check MAC Addresses:

 

Ensure that the MAC address of the aggregated interface is correctly configured and unique to avoid conflicts.

 

7. Restart Aggregated Interfaces:

 

In some cases, restarting the aggregated interfaces or the device may resolve temporary issues.

 

Conclusion:

 

LACP and static LAG are pretty mature features. If you experience a problem with them, follow the steps above and examine one by one and in most cases you should resolve this issue yourself.

It is worth your attention that port speed, duplex, and VLAN are very important to create the link aggregation.

 

Note:

 

1. Configuration guides regarding static LAG and LACP:

How to configure LAG (LACP) on Omada Switches via Omada Controller

How to configure LACP on our Smart/ Managed Switch

How to configure 802.1Q VLAN for LAG ports on Smart and Managed switches using the new GUI

 

2. Related discussion and topics, and you may find resolved cases as well:

https://community.tp-link.com/en/business/forum/3?tagId=628

 

3. If the previous steps have not been able to resolve the issue, please collect the relevant information from the previous steps, and then seek the support team. Or post a new thread.

 

Update Log:

 

Jan 17th, 2024:

Release of this article.

 

Recommended Threads:

 

Troubleshooting Techniques for Laymen

Data Center Network Switch Design - Switch Layer Hierarchy

 

Feedback:

 

• If this was helpful, welcome to give us Kudos by clicking the upward triangle below.
• If there is anything unclear in this solution post, please feel free to comment below.
• If you encounter such an issue, please follow the troubleshooting above to check your settings. Besides, ensure your Omada Controller and Switch are running with the latest firmware.
• If the issue still exists after you try the suggestion above, please feel free to comment below or contact our support team with a detailed description of your issue and the steps you have tried.

 

Thank you in advance for your valuable feedback!

 

------------------------------------------------------------------------------------------------

Have other off-topic issues to report? 

Welcome to > Start a New Thread < and elaborate on the issue for assistance.