AP Management from Controller
Mesh Support on page 485
●
For an understanding of how support should be configured for the Access Point and its connected
controller, see
For an overview of how to configure both the Access Point and controller for basic connectivity and
operation, see
AP Management
An AP can be adopted, configured and managed from the wireless controller.
NOTE
Configuration changes made on an AP35XX will not be updated on the controller. To change the AP configuration for
an AP35XX make the changes using the controller's interface.
An AP's wireless configuration can also be configured from the controller. However, non-wireless
features (DHCP, NAT, Firewall etc.) cannot be configured from the controller and must be defined using
the access point's resident interfaces before its controller adoption or through Extreme Networks Wireless
Management Suite (WMS).
Licensing
An adopted AP uses an existing license purchased with a controller.
Controller Discovery
An AP needs to connect to a controller to receive its configuration.
Auto Discovery using DHCP
Extended Global Options 189, 190, 191, 192 can be used or Embedded Option 43 - Vendor Specific
options can be embedded in Option 43 using the vendor class identifier.
List of Controller IP addresses
(separate by comma, semi-colon, or space delimited)
Controller FQDN
AP35xx Encryption IPSec Passphrase (Hashed)
AP35xx controller discovery mode
1 = auto discovery enable
2 = auto discover enabled (using IPSec)
** The AP35XX uses an encryption key to hash passphrases and security keys. To obtain the encryption
passphrase, configure an AP35XX with the passphrase and export the configuration file.
482
"How the AP Receives its Configuration" on page
"Establishing Controller Managed AP Connectivity" on page
488.
Code
189
190
**
191
192
Summit WM3000 Series Controller System Reference Guide
489.
Data Type
String
String
String
String