SonicPoint Deployment Best Practices
529
SonicOS 5.8.1 Administrator Guide
• Safemode – Safemode can be engaged by depressing the reset button, or from the
SonicOS peer device. Placing a SonicPoint into Safemode returns its configuration to
defaults, disables the radios, and disables SDP. The SonicPoint must then be rebooted to
enter either a stand-alone, or some other functional state.
• Non-Responsive – If a SonicOS device loses communications with a previously peered
SonicPoint, it will report its state as non-responsive. It will remain in this state until either
communications are restored, or the SonicPoint is deleted from the SonicOS device’s table.
• Updating Firmware – If the SonicOS device detects that it has a firmware update available
for a SonicPoint, it will use SSPP to update the SonicPoint’s firmware.
• Downloading Firmware – The SonicWALL appliance is downloading new SonicPoint
firmware from the configured URL, which can be customized by the administrator. The
default URL is http://software.sonicwall.com.
• Downloading Failed – The SonicWALL appliance cannot download the SonicPoint
firmware from the configured URL.
• Writing Firmware – While the SonicPoint is writing new firmware to its flash, the progress
is displayed as a percentage in the SonicOS management interface in the SonicPoint status
field.
• Over-Limit – By default, up to 2 SonicPoint devices can be attached to the Wireless zone
interface. If more than 2 units are detected, the over-limit devices will report an over-limit
state, and will not enter an operational mode. The number can be reduced from 2 as
needed.
• Rebooting – After a firmware or configuration update, the SonicPoint will announce that it
is about to reboot, and will then do so.
• Firmware failed – If a firmware update fails, the SonicPoint will report the failure, and will
then reboot.
• Provision failed – In the unlikely event that a provision attempt from a SonicOS device
fails, the SonicPoint will report the failure. So as not to enter into an endless loop, it can
then be manually rebooted, manually reconfigured, or deleted and re-provisioned.
• Stand-alone Mode (not reported) – If a SonicPoint device cannot find or be found by a
SonicOS device to peer with, it will enter a stand-alone mode of operation. This will engage
the SonicPoint’s internal GUI (which is otherwise disabled) and will allow it to be configured
as a conventional Access Point. If at any time it is placed on the same layer 2 segment as
a SonicOS device that is sending Discovery packets, it will leave stand-alone mode, and
will enter into a managed mode. The stand-alone configuration will be retained.
SonicPoint Deployment Best Practices
This section provides SonicWALL recommendations and best practices regarding the design,
installation, deployment, and configuration issues for SonicWALL’s SonicPoint wireless access
points. The information covered allows site administrators to properly deploy SonicPoints in
environments of any size. This section also covers related external issues that are required for
successful operation and deployment.
SonicWALL cannot provide any direct technical support for any of the third-party Ethernet
switches referenced in this section. The material is also subject to change without SonicWALL’s
knowledge when the switch manufacturer releases new models or firmware that may invalidate
the information contained here. The only exception to this rule is Hewlett-Packard, as
SonicWALL is currently a member of HP’s ProCurve Alliance program, and works closely with
HP to ensure compatibility with the ProCurve switch product line.
Further information on this can be found at:
