After migrate Omada between ESX host gateway is disconnected, restart gateway help for few hours
After migrate Omada between ESX host gateway is disconnected, restart gateway help for few hours
Hi guys,
I need some support from TP-Link technicians with missing gateway in Omada. I migrate Omada VM between host and then (after few hours) connection with gateway was lost.
Environment:
Omada VM <-> ESX host <-> SG1008 switch <-> ER605v2 gateway
Info:
- no VLANs between Omada VM and gateway
- restart switch doesn't help
- restart Omada VM doesn't help
- restart gateway help for few hours
TP-Link, what data do you need to debug your software, where i can find them to do analysis?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Connection to gateway is lost... do you mean it shows disconnected in the controller? Or the VM physically disconnects from the network?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I think you don't red my post carefully. So i migrate VM between ESXi hosts, i don't made new Omada controler.
Anyway, where i can force readaption?
- Copy Link
- Report Inappropriate Content
I read your post... I'm just saying… Have you tried resetting your router and readopted to the newly moved vm. Sorry for mistyping my sentence.
There isn't a quick way of doing it, unless you press the reset button.
- Copy Link
- Report Inappropriate Content
This will be easiest way to resolve my issue, but as IT guy, i want to know why this happen and how i can mitigate this in future.
Anyway, in business there is no time for playing with support on forum, equipment have to work all the time.
- Copy Link
- Report Inappropriate Content
I see you are using Firmware Version: 2.2.0, this was probably withdrawn due to errors similar to the one you have. try and install Early Access Firmware Version: 2.1.4 which will replace Firmware Version: 2.2.0 ,
https://community.tp-link.com/en/business/forum/topic/615998
if you want to know why this happens, tell TP-Link if you find out, they don't know either :-) adopt provisioning and disconnect from the controller has been a never ending problem with the Omada routers.
In particular ER605. I have ER8411 and ER707-M2, they work to be a little better, but I have to restart them every now and then too.
- Copy Link
- Report Inappropriate Content
Thx for the links, i saw them before made a post here.
I'm wondering why TP-Link don't make any mechanism to collect data from gateway or controller to make analysis bundle or any better by the user with tech skills.
I will reboot gateway again i see for how long it help.
The worst side of using TP-Link product is support, which is no support (in most cases).
I'm pretty sure, they should test early access (in real life beta) firmware in TP-Link env. not a customer (most business ones).
Anyway, blocking access to gateway because you manage it by controller is stupic from design, simple restart or basic "actions" should be possible remotely when you loose connection by controller (as in my case).
- Copy Link
- Report Inappropriate Content
yes I agree, I don't get it either. it should be easy to add a reboot command in the http interface or via SSH. in most cases when the router disconnects from the controller is http or SSH available.
But they are slowly adding more features so there will probably be more logging and features in the future. it was also for a short time possible to restart the ER605 via SSH but this possibility disappeared, I think it was in a beta version that I don't remember the version of
- Copy Link
- Report Inappropriate Content
After restart of gateway, on controller i saw all steps from adopting, prov and configuration till connected status.
I'll let know for how long this help.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1041
Replies: 13
Voters 0
No one has voted for it yet.