Deployment Guide
Table Of Contents
- Table of Contents
 - Preface
 - About Extreme Campus Controller Deployment
 - Configuring DHCP, NPS, and DNS Services
 - Centralized Site with a Captive Portal
 - Centralized Site with AAA Network
 - Deploying a Mesh Network
 - Configuring an External NAC Server for MBA and AAA Authentication
 - Manage RADIUS Servers for User Authentication
 - External Captive Portal on a Third-Party Server
 - Access Control Rule Admin Portal Access
 - Deploying Centralized Web Authentication
 - Deploying ExtremeCloud IQ - SE as an External Captive Portal
- Deployment Strategy
 - Configuring an External Captive Portal Network
 - Editing the Configuration Profile for Network and Roles
 - Extreme Campus Controller Default Pass-Through Rule
 - Adding Extreme Campus Controller as a Switch to ExtremeCloud IQ - Site Engine
 - Editing the Unregistered Policy on ExtremeCloud IQ - Site Engine
 - Editing the ExtremeCloud IQ - Site Engine Profile for Policy and Location-Based Services
 
 - Deploying an ExtremeGuest Captive Portal
 - Deploying Client Bridge
 - Deploying an Availability Pair
 - Deploying Universal APs
 - Extreme Campus Controller Pair with ExtremeLocation and AirDefense
 - ECP Local Authentication
 - PHP External Captive Portal, Controller’s Firewall Friendly API
 - Index
 
Deploying an Availability Pair
Deploying an Availability Pair on page 182
Deploying an Availability Pair
Extreme Campus Controller provides the availability feature to maintain service availability in the event
of an outage. The Availability Pair feature allows both AP and Client statistics to be available on both
sides of the High Availability configuration.
Before you begin:
1. Enable NTP on both Extreme Campus Controller appliances. Go to Administration > System >
Network Time and select NTP.
2. On the primary Extreme Campus Controller, go to Administration > System > Availability and select
Paired.
3. Configure the following parameters:
Role
Primary
Peer IP Address
The data port IP address of the second Extreme Campus Controller.
Note
The Peer IP address must refer to a physical topology of the peer appliance. It can be
the IP address of a physical port or the IP address of a Lagged interface. Configuring
availability against a service topology such as the IP address (L3) of a
Bridged@Controller appliance is not supported.
Auto AP Balancing
Select Active - Passive
In a Availability Pair, an AP establishes an active tunnel to one appliance and a backup tunnel to
the other appliance. The active tunnel is used to pass the client data over tunneled topologies.
• In an Active-Active configuration, approximately half of the APs establish an active tunnel to
the primary appliance. The remaining APs establish an active tunnel to the backup appliance,
spreading the load across the Availability Pair.
• In an Active-Passive configuration, all APs establish an active tunnel to the primary
appliance. The secondary appliance is used for failover only.
In either configuration, however, most parameters can be configured on either appliance in
the availability pair.
182
Extreme Campus Controller Deployment Guide for version 5.46.03










