Troubleshooting Topology in Controller Is Not Recognized Properly

Troubleshooting Topology in Controller Is Not Recognized Properly

Troubleshooting Topology in Controller Is Not Recognized Properly
Troubleshooting Topology in Controller Is Not Recognized Properly
2 weeks ago - last edited 2 weeks ago

This Article Applies to:

 

Easy Smart switch without LLDP support. Or third-party switch.

 

Issue Description:

 

If your model does not support LLDP or only supports LLDP forwarding, the topology will not display properly in the Controller GUI.

 

Troubleshooting:

 

1. Examine your model.

 

If your model is an unmanaged(-able) switch, it is likely it does not support LLDP(802.1ab LLDP/ LLDP-MED) natively. It will not be able to display the topology properly regardless of the connected devices compatibility which may support LLDP.

 

2. Check compatibility with LLDP.

 

If your model is not a TP-Link Omada managed((referring to specifically L3 and) L2+ manageable) switch, or a third-party switch that does not specifically list compatibility with the LLDP, 802.1ab LLDP/ LLDP-MED, then it may not properly display the topology.

 

3. Check if your device has an IP address.

 

If you have made sure that the router, switch and AP are all properly configured and supported with the LLDP, but the client is not displayed properly, please consider if the device is connected properly to the system.

 

Note that the Controller display is not instantly synced. There may be a delay before you see the device showing in the client list or the topology. Please wait for a while before you check it again.

You may also reboot the networking devices or reconnect your device to the network to refresh its status.

 

Conclusion:

 

We have witnessed certain cases where third-party switches are used in the network and the topology is not properly recognized as well. We were not able to locate the reason and did not resolve this issue until the user replaced the switch with ours. 

 

We highly recommend you use a switch that supports LLDP. If you expect to get your network configured properly with the Omada Controller, we recommend you consider a full setup of Omada devices.

 

For the network design of the switch, see the guide: Data Center Network Switch Design - Switch Layer Hierarchy

It is recommended that you use an SG2000 series or ES200 series switch which supports LLDP natively as your Aggregation Layer switch and an unmanaged switch as the Access Layer.

 

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.

 

Update Log:

 

Dec 12th, 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.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  1      
  1      
#1
Options