SonicOS 8 Access Points
- SonicOS8
- About Access Points
- Settings
- Synchronize Access Points
- Provisioning Overview
- Creating/Modifying Provisioning Profiles
- Adding/Editing a Provisioning Profile - Getting Started
- General Settings for Provisioning Profiles
- 5GHz/2.4GHz Radio Basic Settings for Provisioning Profiles
- 5GHz/2.4GHz Radio Advanced Settings for Provisioning Profiles
- Sensor Settings for WIDP in Provisioning Profiles
- Mesh Network Settings for Provisioning Profiles
- 3G/4G/LTE WWAN Settings for Provisioning Profiles
- Bluetooth LE Settings for Provisioning Profiles
- Deleting Access Point Profiles
- Product Specific Configuration Notes
- Managing Access Point Objects
- Firmware Management
- Floor Plan View
- Station Status
- Intrusion Detection Services
- Advanced IDP
- Packet Capture
- Virtual Access Points
- RF Monitoring
- RF Analysis
- RF Spectrum
- FairNet
- Wi-Fi Multimedia
- 3G/4G/LTE WWAN
- Bluetooth LE Devices
- Radio Management
- SonicWall Support
Provisioning Overview
SonicPoint/SonicWave Provisioning Profiles provide a scalable and highly automated method of configuring and provisioning multiple access points across a Distributed Wireless Architecture. SonicPoint/SonicWave Profile definitions include all of the settings that can be configured on a SonicWall access point, such as radio settings for the 2.4GHz and 5GHz radios, SSID’s, and channels of operation.
After you have defined a access point profile, you can apply it to a Wireless zone. Each Wireless zone can be configured with one access point profile. Any profile can apply to any number of zones. Then when an access point is connected to a zone, it is automatically provisioned with the profile assigned to that zone.
When an access point is first connected and powered up, it has a factory default configuration (IP address: 192.168.1.20
, username: admin, password: password). Upon initializing, the unit attempts to find a SonicOS device with which to peer. When a SonicOS device starts up, it also searches for access points through the SonicWall Discovery Protocol. If the access point and a peer SonicOS device find each other, they communicate through an encrypted exchange where the profile assigned to the relevant Wireless zone is used to automatically provision the newly added access point unit.
As part of the provisioning process, SonicOS assigns the discovered access point a unique name and records its MAC address, the interface, and zone on which it was discovered. If part of the profile, it can also automatically assign an IP address so that the access point can communicate with an authentication server for WPA-EAP support. SonicOS then uses the profile associated with the relevant zone to configure the 2.4GHz and 5GHz radio settings.
Note that changes to profiles do not affect units that have already been provisioned and are in an operational state. Configuration changes to operational access points can occur in two ways:
-
Through manual configuration changes
This option is the best choice when a single, or a small set of changes are to be made, particularly when that individual access point requires settings that are different from the profile assigned to its zone.
-
Through the "Auto Provisioning SonicWave Provisioning Profile"
This option is configured on the OBJECT | Match Objects > Zones | Wireless configuration page, After this option enabled, changes to the profile affects the unit. The following warning appears when the profile is edited: "Warning! This profile has been enabled to provision all associated SonicPoint/SonicWave devices within the same zone automatically."
-
Through un-provisioning
Deleting an access point effectively un-provisions the unit. It clears its configuration and places it into a state where it automatically engages the provisioning process anew with its peer SonicOS device. This technique is useful when the profile for a zone is updated or changed, and the change is set for propagation. It can be used to update firmware on access points, or to simply and automatically update multiple access points in a controlled fashion, rather than changing all peered access points at the same time, causing service disruptions.
Was This Article Helpful?
Help us to improve our support portal