Can't add gateway to management vlan
Hello all,
I am trying to move all Omada devices into a management VLAN following this FAQ. Everything works great until I try to reconnect the gateway to the controller, using its new address.
At step 5 of the FAQ, I am not able to discover any devices using the Omada Discovery Utility. Logging directly into the gateway to change the URL for the controller doesn't work for me either (Permission Denied: Omada Controller Software is running. Web Server is forbidden.).
Does someone have an idea on how I could tell my gateway the controllers new address?
Any help is much appreciated!
Best regards,
Josh
I am using the following devices:
Gateway: ER7206 or ER605 (I tried both)
Controller: OC200
Switch: TL-SG2428P
EAP: EAP620 HD
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @Yonash,
Yonash wrote
At step 5 of the FAQ, I am not able to discover any devices using the Omada Discovery Utility. Logging directly into the gateway to change the URL for the controller doesn't work for me either (Permission Denied: Omada Controller Software is running. Web Server is forbidden.).
Is the PC installed with the Omada Discovery Utility directly plugged into the Omada gateway?
Please ensure that the PC mentioned above is in the same subnet network with the Omada Gateway.
Note: The Omada Gateway does not support changing the management VLAN at present.
- Copy Link
- Report Inappropriate Content
Dear @Fae,
Thank you for your response. Yes, the computer was directly plugged into the Omada gateway and WiFi was disabled. I also tried different ports. Unfortunately, I wasn't able to discover any Omada device.
Best regards,
Josh
- Copy Link
- Report Inappropriate Content
Dear @Yonash,
Yonash wrote
Thank you for your response. Yes, the computer was directly plugged into the Omada gateway and WiFi was disabled. I also tried different ports. Unfortunately, I wasn't able to discover any Omada device.
If both the Discovery Utility and Omada Controller are installed on the same computer, please close the Omada Controller completely (Exit Directly) before you run the discovery utility since they cannot run at the same time on the same computer.
If you use a Windows PC to run the discovery utility, please refer to the step below to check the firewall settings.
- Copy Link
- Report Inappropriate Content
@Yonash Did you get anywhere with this as I was about to try doing it (MGMT VLAN) with a very similar setup to you (EAPs, R605 Router, OC200, TP-Link managed switches)?
- Copy Link
- Report Inappropriate Content
I have not yet found the time to try Fae's last hint and I am currently to busy right now to test it. If you have the time, trying to run the discovery utility with disabled firewall would be something worth checking out.
Best,
Josh
- Copy Link
- Report Inappropriate Content
I have a similar issue trying to follow the steps in that same FAQ (2814 about MGMT VLAN).
I actually tried to run the discovery utility before I enabled that VLAN and it doesn't discover anything.
PC (Win10 21H2 up to date) is in the same subnet as all my tp-link devices (ER605, SG2008P, OC200, SG2008, EAP245).
I moved it directly to a port in the gateway (although it shouldn't matter for now as all tp-link devices are still in the default LAN).
I'm not running the software controller anywhere.
I let Java through the firewall and also temporarily disabled the firewall with no luck.
Here's the output in the log file (a fixed font would be nice):
2022-05-22 12:44:16.274 INFO 11048 --- [main] c.t.u.d.DiscoveryUtilityApplication : Starting DiscoveryUtilityApplication using Java 1.8.0_333 on SB1 with PID 11048 (<path>omada-discovery-utility-5.0.8.jar started by *** in <path>)
2022-05-22 12:44:16.306 INFO 11048 --- [main] c.t.u.d.DiscoveryUtilityApplication : No active profile set, falling back to default profiles: default
2022-05-22 12:44:17.931 INFO 11048 --- [main] com.tplink.smb.ecsp.server.context.c : start schedule remove expire device... period = 10
2022-05-22 12:44:18.278 INFO 11048 --- [main] c.t.u.d.DiscoveryUtilityApplication : Started DiscoveryUtilityApplication in 2.674 seconds (JVM running for 3.361)
2022-05-22 12:44:18.290 WARN 11048 --- [main] c.t.utility.common.omadac.OmadacType : Failed to load omada.properties
2022-05-22 12:44:19.775 INFO 11048 --- [main] c.t.s.e.t.api.transport.AbstractServer : Start NettyUdpServer (...)
2022-05-22 12:44:19.869 INFO 11048 --- [main] c.t.u.discovery.DiscoveryUtilityRunner : going start DiscoveryUtility
Nothing else. How long does it typically take?
The yellow highlight is only a WARN so hopefully it's not the cause.
Are adopted devices still discoverable?
[Removed some content to get past external links detection]
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1280
Replies: 6
Voters 0
No one has voted for it yet.