Various view issues in Omada SDN
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello together
I noticed that the Omanda SDN does not always display correct results.
Example:
I have a client01 which is directly connected to the switch port 10. The switch has the name "Server Room". However, in Omada SDN it shows that the client is connected to the switch on port 10 with the name " Office". This also happens when I change the port.
Other Example:
The server is connected to port 22 and the IPMI of the server is connected to the same switch on port 23. As you can see on the screenshot, the Omanda SDN shows different ports although the same device is connected to the same switch (Switch_Rack).
Also, devices are shown as online which are not connected at all. The devices are offline and have no active link to the switch.
The sorting of the ports does not work properly either. If I sort the ports in descending order, it looks like this:
It would also be welcome to be able to select them directly in the port overview as it is possible in the mobile app:
It seems to me that the Omana SDN software is not very well developed. I also have Ubiquti in use and there I do not know such problems.
Best regards,
donmartino77
Dear @donmartino77,
Thank you for your valued feedback!
I'll report the issues to the developer team for further investigation, before that, I'd like to check the things below:
Is there any non-SDN device connected in your network?
For the device named as "Office", what device it actually is, the EAP or another SDN switch?
Could you please draw a network diagram to show how the devices are actually connected with port number and device name?
Other Example:
The server is connected to port 22 and the IPMI of the server is connected to the same switch on port 23. As you can see on the screenshot, the Omanda SDN shows different ports although the same device is connected to the same switch (Switch_Rack).
Do you mean that the server connected to port22 of the SDN switch is showing as connected to the VPN Gateway on the controller?
Would it make any difference after the system has been running for a period of time?
Fae wrote
Dear @donmartino77,
Thank you for your valued feedback!
I'll report the issues to the developer team for further investigation, before that, I'd like to check the things below:
Is there any non-SDN device connected in your network?
For the device named as "Office", what device it actually is, the EAP or another SDN switch?
Could you please draw a network diagram to show how the devices are actually connected with port number and device name?
Other Example:
The server is connected to port 22 and the IPMI of the server is connected to the same switch on port 23. As you can see on the screenshot, the Omanda SDN shows different ports although the same device is connected to the same switch (Switch_Rack).
Do you mean that the server connected to port22 of the SDN switch is showing as connected to the VPN Gateway on the controller?
Would it make any difference after the system has been running for a period of time?
Is there any non-SDN device connected in your network?
No, I do not have any other network devices on my network. All switches and EAP are compatible with Omada SDN.
For the device named as "Office", what device it actually is, the EAP or another SDN switch?
This is a TL-SG3428 v2.0 switch with the latest firmware.
Could you please draw a network diagram to show how the devices are actually connected with port number and device name?
If I ever find the time, I can do that. The problem is, if the mapping of the ports in the SDN is not correct, I can not configure the switch ports correctly with VLAN etc..
Would it make any difference after the system has been running for a period of time?
No, it doesn't matter. I have had the device connected for over a week now and still the same incorrect information in the SDN.
Do you mean that the server connected to port22 of the SDN switch is showing as connected to the VPN Gateway on the controller?
Yes, but that is not the only device. There are other devices that have exactly the same problem.
Today I installed the firmware 1.1.1 for the VPN Gateway TL-ER7206 v1.0. Now the situation has become even worse. All these clients are running on the same Hyper-V host and on the same physical server on port 22:
The overview is also no longer correct:
The following overview would be correct:
