@R1D2 

R1D2 wrote

@APRC-P3-Tel, why would you want to reboot APs and OC200 each day? We run EAPs and Omada Controller without a scheduled reboot for years now, only restarted after a firmware update. For example, one of our Omada software controllers now runs for 771 days w/o a reboot (on Linux, not Windows).

We could not believe that  such a VFM product like EAP/Omada will not have bugs.  Old wives tales ;-))

We thought that maybe their could be some memory leaks or other issues not worth immediate debugging when we installed our first set of 7 EAP115 and EAP-110 outdoor APs two years back.  It was an experiment then, testing of the waters. TpLink did not have a brand reputation as Cisco, Aruba or Ruckus. So we just let the system reboot everyday at night (when no is practically using the APs), so that if any *latent fault has taklen place in software, it gets recovered at night, and does not impact usage the next day.  Like  cleaning your house everyday. 

We have had this setup in place for 2 years now. Our Controllers are never restarted daily, mostly because such a configuration was never there in the first place and that we use Controller and Mobile Application for monitoring AP health/liveliness, otherwise we would have surely treated them in same way as APs. And every new AP added (we have 59 now and 30-40 more in planning) is just inheriting this configuration, by virture of being added to same site. 

Frankly though, we have  *never encountered any issue in last 2 years of use, except one with EAP-110 outdoor which got triggered oncewe moved from Auranet Controller to Omada Controller, which was addressed by a firmware upgrade (not otherwise available in India for download or through controller) you suggested.  Everything downtiem otherwise was our config mistake or UPS power failure to PoE switches or some external cause.

any inputs on the below query:

(3) Can two portals share authentication data, if device roams from one Hotspot to another (both using SMS authentication) on same controller ?

APRC-P3-Tel wrote

We are using EAPs with OC200 controllers. We are now doing some pilot testing with Portal SMS authentication and Twilio SMS integration worked after regulatory compliance requirements were handled. The authentication validity period is kept at 30 days now.

 

Our APs go for nigthly reboots at X:00 AM daily. However no such configuration is available or done manually for OC200 (They seem rock stable for now without reboots).

 

For SMS authentication, we want to know:

 

(1) Is the SMS authentication data stored in OC200 or Cloud or both ?

(2) What is the persistence of SMS data ? If our Controller reboots (power cycling/failure/manual-reboot), will we drop the authentication data and users get challenged again even if 30 day authentication has not expired ?

(3) Can two portals share authentication data, if device roams from one Hotspot to another ()both using SMS authentication) on same controller ?

 

 

 

@APRC-P3-Tel 

When the EAPs are managed by the same Oamda Controller, the authentication information of the client devices will be stored by the Omada Controller. Therefore, when the client devices roam among the EAPs, they can share the authentication data. 

forrest wrote

@APRC-P3-Tel 

When the EAPs are managed by the same Oamda Controller, the authentication information of the client devices will be stored by the Omada Controller. Therefore, when the client devices roam among the EAPs, they can share the authentication data. 

@forrest : Does this hold true about roaming on two different portal authenticated SSIDs (Wifi networks) on the same controller ? Will the client/guest be asked to enter passwords again or go through SMS OTP authentication all over again ?

@APRC-P3-Tel 

When the client devices are roaming between different SSIDs, these clients need to authenticate all SSID first. That is, when the client pass  the autehntication of one SSID, if the client connects to another SSID, it should pass the authentication, or it cannot connect to the second SSID.