Complete the tasks in the following task flow on the ExtremeCloud IQ (Classic) interface to provision tunneling using Tunnel Concentrator.
Before you Begin
Tunnel Concentrator must be installed already with ExtremeCloud IQ selected as management entity. For details, see Installation.
You must have a Network Policy and SSIDs configured on ExtremeCloud IQ already. For help with these configuration elements, see the ExtremeCloud IQ (Classic) User Guide.
| Procedure | Description | |
|---|---|---|
| 1 | Quick Add Tunnel Concentrators | Onboard your Tunnel Concentrators to ExtremeCloud IQ. |
| 2 | Configure Tunnel Concentrator Service | Configure a service that uses a single instance of Tunnel Concentrator or a redundant HA pair of instances. |
| 3 | Configure Tunnel Policy | (Optional) If you want Layer 2 roaming, configure a Tunnel Policy that points to your Tunnel Concentrator service. |
| 4 | Configure User Profile with Tunnel Concentrator | Assign the Tunnel Concentrator service to a User Profile. |
| 5 | Configure SSIDs with Tunnel Concentrator User Profile | Assign your Tunnel Concentrator User Profile(s) to wireless SSIDs. |
| 6 | Deploy Network Policy | Complete a delta push to deploy the Network Policy to affected devices. |
Note
Each Tunnel Concentrator Service can reference up to two Tunnel Concentrator devices.
Primary and backup Tunnel Concentrators must belong to the same network policy.
For a redundant Tunnel Concentrator, the IP addresses of both the primary and redundant Tunnel Concentrators must belong to the same subnet as the Tunnel IP Address/CIDR.
The Gateway IP Address must belong to the same subnet as the Tunnel IP Address/ CIDR.
Alternative Configuration Flow
If you don't want Layer 2 roaming, and aren't configuring a Tunnel Policy, you can use a streamlined configuration where you assign all settings from the Network Policy. See ExtremeCloud IQ (Classic) Configuration Example (Alternative Flow) for a configuration example that uses this approach.