Wireless Access

If you configure as a cluster then the RAPs will be load balanced across the cluster, same as CAPs.  Since the 9004 is limited to 32 APs, that means a cluster of four 9004 controllers is only going to handle 64 RAPs when running as a cluster.

The only way to handle 115 RAPs is to run each controller completely separately, with no more than 32 RAPs assigned to each controller.

Another option would be to use AOS 10 and Microbranch deployments instead.

If you configure as a cluster then the RAPs will be load balanced across the cluster, same as CAPs.  Since the 9004 is limited to 32 APs, that means a cluster of four 9004 controllers is only going to handle 64 RAPs when running as a cluster.

The only way to handle 115 RAPs is to run each controller completely separately, with no more than 32 RAPs assigned to each controller.

Another option would be to use AOS 10 and Microbranch deployments instead.

Because a cluster is going to utilize 50% of the cluster resources to provide redundancy through the secondary tunnels and connections.

Yes, you can manage controllers from the Mobility Conductor (MCR) and not have them in a cluster.

If you configure as a cluster then the RAPs will be load balanced across the cluster, same as CAPs.  Since the 9004 is limited to 32 APs, that means a cluster of four 9004 controllers is only going to handle 64 RAPs when running as a cluster.

The only way to handle 115 RAPs is to run each controller completely separately, with no more than 32 RAPs assigned to each controller.

Another option would be to use AOS 10 and Microbranch deployments instead.