General FAQs for EAPs

How many devices can the Omada controller manage?

The management scale of the Omada Software Controller depends on the specifications of the computer running the application. The recommended baseline requirements of the Omada Controller host are: Intel I3 CPU, 2GB RAM, 10G HDD or above. This will increase as the number of managed devices increases. With these specifications, the recommended management scale of the Omada Software Controller is 500 devices.

 

How many SSIDs do EAP products support?

There is no limitation to the number of SSIDs in the Omada Controller. However, different EAP products support different numbers of SSIDs. For example, EAP245 supports 16 SSIDs (8 for each band). For detailed information on each model, please refer to the Specifications or datasheet for that model on the official website.

 

What operating systems can support the Omada Software Controller?

Currently, Microsoft Windows and 64-bit Linux operating systems, including Ubuntu 14.04/16.04/17.04, CentOS 6.x/7.x and Fedora 20 or above can support the Software Controller. Mac OSX is not supported at present.

 

Which ports does the Omada Controller use?

Port Number	Port Type	Purpose
8043	TCP	HTTPS
8088	TCP	HTTP
27001	UDP	Controller discovery
27002	TCP	Controller searching
27017	TCP	MongoDB server
29810	UDP	EAP discovery
29811-29813	TCP	EAP management, adoption, and upgrading

 

What is the Device Account? What is it used for?

The Device Account is the local administrator account for the Controller. When the Controller adopts a device, the local administrator account for the device is overwritten with the Device Account in the Controller settings.

 

What happens to EAPs when they are forgotten from the Controller?

When you forget an EAP in Omada Controller V2 or higher, the Controller will attempt to reset the EAP to factory settings. However, when you forget an EAP in Omada Controller V1, the EAP will keep the settings of the Omada Controller. The username and password of the EAP will also remain the same as the Device Account of the Omada Controller.

 

Should I keep the controller running after I have finished the configuration?

Once configured, EAPs will operate according to the Controller configuration even if they lose connection to the Omada Controller. However, some functions like captive portal and operation schedules will no longer work if the EAPs lose connection to the Controller.

 

Can the Omada controller manage EAPs in different subnets?

Yes, the Omada Controller supports L3 management. For more information, please refer to FAQ-1359 & FAQ-1360.

 

Can an EAP be managed by two different Omada Controllers?

No, an EAP can only be managed by one Omada controller. Additionally, one Omada controller is allowed to run in the same local area network.

 

If I restart the Omada controller, will the EAP device also reboot?

No, restarting the controller does not automatically reboot any managed devices.

 

Can I manage my EAP devices across the Internet?

Yes, please refer to FAQ-1361 & FAQ-1362 for more information.

 

Why can’t I log in to the EAP's management interface?

Usually there are two cases.

 

Case 1: The EAP is adopted by an Omada Controller

After the EAP is adopted by the Omada controller, you can only change the configurations and check the status of the EAP on the Omada controller. If you access the EAP's management interface, you will receive a 403 Forbidden error page.

 

Case 2: The username or password is incorrect

If adopted by an Omada Controller, the login credentials of the EAP will be set to the Device Account set in the Controller settings. If you are unable to access the Controller or forgot the credentials, a factory reset may be required.

 

Why won’t it redirect me to the portal page when I connect to the network?

If you cannot access the captive portal to authenticate, visit any HTTP page, and the EAP should redirect you to the portal page.

 

How do I reset an EAP to factory default?

With the device powered on, press and hold the RESET button for about 5 seconds until the LED flashes red/green/yellow alternatively twice, then release the button. The device will restore to factory default settings.

 

How do I reboot an EAP via the Omada Controller?

If you want to reboot some specific APs, please go to Devices and select the EAP you would like to reboot. Then click the Power icon next to the EAP. You can also configure a Reboot Schedule to set your EAPs to reboot at a specific time. This feature is compatible with all Omada Controllers except Omada Cloud/Central Essentials.