Tunnel Concentrator is supported by more than one Extreme Networks management software option. You can select from one of the following management options:

Note
Tunnel Concentrator supports ExtremeCloud IQ (Classic), but not ExtremeCloud IQ (New). All subsequent references in this document to ExtremeCloud IQ can be assumed to be referring to ExtremeCloud IQ (Classic), unless noted otherwise.The following table summarizes the management applications and provides information on which features are supported with which management option.
| Feature Support | Extreme Platform ONE Networking | ExtremeCloud IQ (Classic) | ExtremeCloud IQ Controller |
|---|---|---|---|
| IPsec-encrypted tunneling | Yes | No | Yes |
| RADIUS Authentication through Tunnel Policy | Yes | No | No |
| Tunnel Concentrator IP Address Pool | Yes | No | No |
| MTU Status | Yes | No | No |
| Tunnel Concentrator Redundancy | Up to six Tunnel Concentrators per user profile | Up to six Tunnel Concentrators per user profile |
Up to three Tunnel Concentrators per VLAN |
| LAG | Yes | Yes | Yes |
With either Extreme Platform ONE Networking or ExtremeCloud IQ, the management application uses an Inlets connection on TCP (HTTPS) port 8090. Access to the management entity is routed through the stack of the underlying Universal Compute Platform host. As a result, the routing stack configuration (i.e., the default gateway) path from the host is key to the connection path.
With ExtremeCloud IQ Controller, tunnels are configured and managed using the ExtremeCloud IQ Controller user interface. Tunnel Concentrator establishes an HTTPS connection to the controller on port 5825. The Concentrator uses stored read-only credentials to retrieve the configuration and to configure GRE/IPsec tunnels.

Note
To generate encryption and decryption keys when IPsec is deployed, the management entity generates a private, pre-shared key using the IKEv2 protocol and uses a secure connection to provision the key on Tunnel Concentrator and on the access points.