AP's not connected in controller software
My setup:
2 TPLINK Omada EAP245 Access points
Omada controller: 3.2.10
What I have done:
On a laptop where the software runs with the 2 AP's visible and connected, I made a backup from the setup.
On a PC (with cabled lan connection to the same network as where the 2 AP's are connected to) I restored the backup file.
The 2 AP's are visible, with the right IP addresses. I can ping the 2 AP's.
But the problem: they won't get come to the status "connected".
Does the device where the controller software runs, need a wifi connection?
Do I miss something?
Thanks in advance.
-MichelvE
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@MichelvE Yep, that's how I've gotten it to work in the past; there's also a dedicated migration process that you can do assuming the controllers are the same version.
Instructions for that are here:
How to migrate Omada Controller with the Migration feature | Omada Network Support
- Copy Link
- Report Inappropriate Content
@MichelvE What firmware version do the EAP245s have? Did anything change aside from just restoring the backup?
Also, what is the hardware version of the EAPs? That should be visible on the label of the devices. (see here for an example: How to tell TP-Link Device Hardware Versions Apart - Business Community)
- Copy Link
- Report Inappropriate Content
@NeilR_M
Thanks for your response.
Hardware version = 3.0
Firmware version = 2.4.0 Build 20200117 Rel. 39932
I had the AP's connected in the software on one laptop.
I made a backup on the laptop, restored that file on the Omada Controller on the desktop PC
I restarted the AP's.
I can ping the AP's from the desktop PC.
Does the device need to be connected through Wifi? Or can the device also be connected via lan cable in order to get the AP's connected?
- MichelvE
- Copy Link
- Report Inappropriate Content
@MichelvE As long as the new controller is on the same network (wired and wireless can share the same LAN/subnet), you should be able to see the devices. Did you forget the devices from the old controller and then try adopting them in the new one?
- Copy Link
- Report Inappropriate Content
@NeilR_M
No I did not "forget" them on the old controller.
I did a test earlier with another laptop and that went well without "forget and adopt".
Is the normal way: first forget on the old controller and then adopt on the new controller?
Then I can actually forget the backup and restore trick.
- MichevE
- Copy Link
- Report Inappropriate Content
@MichelvE Restoring the backup makes sure that the configurations are already on the controller when you try to adopt, but you are free to do whichever one works best for you!
- Copy Link
- Report Inappropriate Content
@NeilR_M
Oke, so the normal way should be:
* restore a backup
* Adopt the AP's on the new controller after they are "forgotten" on the old controller.
Is that correct?
- Michel
- Copy Link
- Report Inappropriate Content
@MichelvE Yep, that's how I've gotten it to work in the past; there's also a dedicated migration process that you can do assuming the controllers are the same version.
Instructions for that are here:
How to migrate Omada Controller with the Migration feature | Omada Network Support
- Copy Link
- Report Inappropriate Content
@NeilR_M
Thank you very much for the willing and patience to help.
It's totally clear now!
- MichelvE
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 141
Replies: 8
Voters 0
No one has voted for it yet.