AP Management from Controller
Summit WM3000 Series Controller System Reference Guide482
● Mesh Support on page 485
For an understanding of how support should be configured for the Access Point and its connected
controller, see “How the AP Receives its Configuration” on page 488.
For an overview of how to configure both the Access Point and controller for basic connectivity and
operation, see “Establishing Controller Managed AP Connectivity” on page 489.
AP Management
An AP can be adopted, configured and managed from the wireless controller.
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.
** 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.
Code Data Type
List of Controller IP addresses
(separate by comma, semi-colon, or space delimited)
189 String
Controller FQDN 190 String
AP35xx Encryption IPSec Passphrase (Hashed)
**
191 String
AP35xx controller discovery mode
1 = auto discovery enable
2 = auto discover enabled (using IPSec)
192 String
To Next Page
Loading...