The Multi-Location Network Management Problem

Organizations with multiple physical locations face a network management challenge that grows exponentially with each new site: disparate equipment, inconsistent configurations, fragmented monitoring, and no centralized visibility. When something breaks at a remote location, the question 'what does the network look like right now?' often has no good answer.

UniFi's multi-site management architecture solves this by giving network administrators — and managed service providers — complete visibility and control over every site from a single interface.

UniFi Multi-Site Architecture

Hosted UniFi Network Server (UNMS)

The foundation of multi-site management is a centralized UniFi Network Server — either self-hosted on enterprise infrastructure or deployed on UniFi's hosted cloud service. All sites connect to this central controller, regardless of physical location. Remote APs, switches, and gateways phone home to the controller and remain manageable even if the local internet connection at a site is intermittent.

Site Isolation and Access Control

Each physical location is configured as a separate 'site' in the UniFi controller. Site isolation ensures that changes to one location's configuration do not affect other sites. RBAC (Role-Based Access Control) allows granular permission assignment — site administrators, read-only observers, and full system administrators can all operate within the same platform.

Standardized Deployment Templates

One of the most powerful features of multi-site management is configuration templating. When a new office location is added, the network configuration — VLANs, SSIDs, firewall rules, QoS policies — can be deployed from a master template in minutes, not days. This ensures consistency across locations and dramatically reduces the time required to bring new sites online.

  • Standard corporate SSID and security policies pushed to all sites simultaneously
  • VLAN numbering consistent across locations (critical for inter-site VPN functionality)
  • Firewall rule sets deployed from central policy, with local overrides permitted where needed
  • Monitoring thresholds and alerting configurations standardized across the portfolio

Remote Troubleshooting Capabilities

When an issue occurs at a remote site, the first response is remote diagnosis — not a technician dispatch. UniFi's multi-site platform provides:

  • Real-time client connectivity status across all sites
  • Packet capture on remote switches and APs without physical access
  • Remote CLI access to all managed devices
  • Historical event logs for root cause analysis
  • Speed test execution from remote gateway to verify ISP performance

In practice, approximately 80% of network issues can be diagnosed and resolved remotely. This translates directly into reduced mean time to resolution (MTTR) and lower operational costs.

MSP Deployment Model

For managed service providers managing multiple client networks, UniFi's multi-site architecture is purpose-built for the MSP model. Each client is a separate site with full isolation. Billing, reporting, and configuration management all happen from the same platform. The MSP's NOC team has full visibility; clients can be given read-only access to their own site dashboard.

Frequently Asked Questions

How many sites can a single UniFi controller manage?

UniFi's hosted controller has no practical architectural limit for site count. Self-hosted instances should be sized according to the total device count — a server handling 100 sites with 50 devices each (5,000 total devices) needs approximately 8 GB RAM and 4 CPU cores for comfortable operation.

What happens if the controller goes offline?

UniFi devices continue operating normally if the controller becomes unavailable. Clients stay connected, VLANs remain active, firewall rules continue enforcing. The controller is the management plane only — not the data plane. Configuration changes cannot be pushed during an outage, but existing operations are unaffected.

Can we manage clients on different subnets from the controller?

Yes, through L3 adoption. UniFi devices can be adopted and managed across different subnets using the controller's IP as the inform URL. This is standard for distributed enterprise deployments where each site has its own addressing scheme.