Controllerless Networks

last person joined: yesterday 

Instant Mode - the controllerless Wi-Fi solution that's easy to set up, is loaded with security and smarts, and won't break your budget
Back to discussions
Expand all | Collapse all

Cloud service controllers don't need Instant AP in Remote Site?

This thread has been viewed 1 times

  • 1.  Cloud service controllers don't need Instant AP in Remote Site?

    Posted Sep 17, 2014 08:51 AM

    Hello. I wonder the network deployment using cloud service controllers.

    If cloud service controllers(7005/7010) will be deployed in branch sites,

    can I install general APs for remote service, not instant APs ?

     

     



  • 2.  RE: Cloud service controllers don't need Instant AP in Remote Site?

    EMPLOYEE
    Posted Sep 17, 2014 09:23 AM
    Yes, I deploy smaller 7005/7010 controllers in branch offices for some situations (heavy Lync, etc). I do regular campus APs though since they're terminated on that controller.


  • 3.  RE: Cloud service controllers don't need Instant AP in Remote Site?

    Posted Sep 18, 2014 04:11 AM

    Thanks.

    I have another question.

    When 7005/7010 controllers will be installed in Branch offices, does it need to put mobility controller in HQ?

    In case of that, controllers in branch offices are operating as slave, and a controller in HQ operates as Master, is it right ? 

    (Master means that it can config other controller(slave))

     

    Or, If not, are 7005/7010 controllers configured by Management System(Airwave in Center) ?



  • 4.  RE: Cloud service controllers don't need Instant AP in Remote Site?
    Best Answer

    Posted Sep 23, 2014 04:39 AM

    Hi Jeewson!

     

    That depends on your needs. If you have common configuration on the branches I'd probably use a dedicated master in a central site, make it redundant if budget allows, and configure the branchcontrollers as locals(slave).

     

    Give each location their own AP-group where you specify them to terminate on the local controller in the AP system profile.

     

    The other option you're mentioning is running an "all-master" deployment where each location will operate as a standalone master, they could be centrally configured through Airwave. This is a less common way to do it, I'd say personally.