Omada Controller 5.0.30
Dear all,
looked for a midrange priced Controller Based WLAN Solution and installed the software based Controller Version on Debian 11 in an VMware 6.7 enviroment.
I did a lot of reasearch for my Scenarios and this looks not really a "Business Sultion".
- Adopting of "Devices" on different Subnet outside of the Controller subnet only via Java Script on a seperate Host.
- No reboot od the Controller software via GUI, or im absolut blind.
- does new Devices like my Test AP EAP265HD v1 have a static ip 192.168.0.254 or have i got a used one?
- The integrated log is alsolut useless, a adopt is only logged as "failed" no more infos.
Forum:
i can only choose Models i dont have, maybe someone has to update the Model list.
Do someone has Ideas to solve my topics?
thx a lot
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Dear @Rob23ik,
Rob23ik wrote
Forum:
i can only choose Models i dont have, maybe someone has to update the Model list.
Welcome to the TP-Link Business Community!
May I know which model number you tried to use?
From my try, Omada Controller and EAP265 HD are existed in the list once inputting "Omada" or "EAP265".
As this topic is mainly related to the Omada Controller, I've changed the Model number for you immediately.
- Copy Link
- Report Inappropriate Content
@Rob23ik Hi there,
1. Tplink provide a Utility to help controller adopt devices in different subnet:
https://www.tp-link.com/en/support/faq/2713/
2. No there is no reboot option. The controller provide Force Provision, which means the EAP will be disconnected and readopt.
ALso there is Forget device option. Once the controller forget the EAP it will also reset the EAP
3. 192.168.0.254 is fallback IP of the EAP. If you see this IP, means the EAP does not obtaion IP successfuly from your router.(DHCP did not work) It may have problem on communication with your Router.
The solution is:
1. Connect EAP to your router directly, it may solve the connection issue;
2. Connect your computer to the EAP via Ethernet cable(so no Router/switch anymore), and set up static IP on your computer like 192.168.0.100, subnet maksk 255.255.255.0. Then run the controller and adopt it. It's suggested to give EAP a static IP to the same subnet as your router.
- Copy Link
- Report Inappropriate Content
Hi @Hank21,
thx for your reply, i expected that the Controller itself is able to DHCP the AP´s, so now i learned its not.
I installed and configured a small DHCP Server on the Linux Controller to provide IP´s for provisioning and Mgmt. only.
So i also learned that TP-link Omada Controller is not able to ZTP without Additional Hardware or manual intervention, a Marketing Joke.
Cheers Rob23ik.
- Copy Link
- Report Inappropriate Content
Hi @Fae
when i start a new Thread im only able to choose some Archer Models and AP´s, i will attach a Screenshot.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 778
Replies: 5
Voters 0
No one has voted for it yet.