Linux Controller adopts and forgets

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Linux Controller adopts and forgets

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Linux Controller adopts and forgets
Linux Controller adopts and forgets
2019-11-29 04:42:20 - last edited 2019-12-02 00:48:44
Model: EAP225-Outdoor  
Hardware Version: V1
Firmware Version: 1.6.0 Build 20190722 Rel. 63596

Help

 

I just moved from a Windows based controller to a CentOS 7 based controller.  Now whenever I adopt an access point (First AP attempted is EAP225-Oudoor with latest firmware), the controller adopts it, and start "Provisioning".  Then it goes back to "Pending". The log tab reports that the AP "connected to LAN" and then reports that the AP "was forgotten".  I have tried logging into the AP and resetting it.  I have also gone to the AP and reset it via the reset button on the device.

 

If it matters:

There are only 2 APs on the network.  The other is an EAP245, and still holds the config from the Windows controller (which is off at the moment).

 

I just don't know where to look for more details or what to do.

  0      
  0      
#1
Options
1 Accepted Solution
Re:Linux Controller adopts and forgets-Solution
2019-11-29 22:49:20 - last edited 2019-12-02 00:48:44

@GaKoppel 

 

Finaaly fixed my issue!!!!

 

Looks like it may have been confilicting SSIDs.

 

So as I was migrating with a desire for little/no downtime, I move all the settings to my new controller.  I had 1 AP (the EAP245) still operating while I was migrating the EAP225-outdoor.  My latest thought was that as a part of provisioning, the contoller configured the wireless networks on the migrated AP(EAP225-outdoor) and the SSIDs conflicted with the non-migrated AP (EAP245).

 

Once I logged into my old controller and "forgot" the last AP (the EAP245), I was able to provision and fully adopt the APs. 

 

I could not find any info in any log files to help in this diagnosis.  So it ha been guess and check for 2 days.  SOOOO glad to have this behind me.

Recommended Solution
  0  
  0  
#4
Options
4 Reply
Re:Linux Controller adopts and forgets
2019-11-29 12:03:17

@GaKoppel, sounds to me like the Omada Controller fails to save the state on disk. Which controller version did you install? How did you install the controller? Using the TAR version or the deb-package? Do you start it as the root user?

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#2
Options
Re:Linux Controller adopts and forgets
2019-11-29 14:28:49

@R1D2 

 

I am running version 3.2.1 on CentOS 7 installed from the .tar.gz package.

 

I installed the package with sudo, so everything should be run as root.  I checked the file tree and it is owned by root:root

 

The omada processes are being run as root. 

  0  
  0  
#3
Options
Re:Linux Controller adopts and forgets-Solution
2019-11-29 22:49:20 - last edited 2019-12-02 00:48:44

@GaKoppel 

 

Finaaly fixed my issue!!!!

 

Looks like it may have been confilicting SSIDs.

 

So as I was migrating with a desire for little/no downtime, I move all the settings to my new controller.  I had 1 AP (the EAP245) still operating while I was migrating the EAP225-outdoor.  My latest thought was that as a part of provisioning, the contoller configured the wireless networks on the migrated AP(EAP225-outdoor) and the SSIDs conflicted with the non-migrated AP (EAP245).

 

Once I logged into my old controller and "forgot" the last AP (the EAP245), I was able to provision and fully adopt the APs. 

 

I could not find any info in any log files to help in this diagnosis.  So it ha been guess and check for 2 days.  SOOOO glad to have this behind me.

Recommended Solution
  0  
  0  
#4
Options
Re:Linux Controller adopts and forgets
2019-11-30 00:48:37 - last edited 2019-11-30 13:04:03

@GaKoppel. great it works now. I had set up CentOS 8 in a virtual box, but it seems that it lacks support for jsvc, so I considered to set up CentOS 7 next - I always wanted to take a look at CentOS anyway, seems like this is a pretty cool descendant of RedHat Linux. 

 

But note that Omada Controller should not run on a device connected wirelessly to the EAPs, it should run on a system which has a wired network connection. Then Omada controller ensures that only one controller is running in the same LAN. During migration you just could turn off the old controller while configuring the new controller.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  1  
  1  
#5
Options