34
S
ONIC
WALL S
ONIC
P
OINT
A
DMINISTRATOR
’
S
G
UIDE
:
4
In the Stand-Alone Management Interface, on the System > Firmware page, enter the IP address
or path of the location of the firmware file.
5
Enter the username and password for the FTP site, and click
Upload New Firmware
.
SonicPoint States
SonicPoint devices can function in and report the following states:
•
Initializing
: The state when a SonicPoint starts up and advertises itself using SDP prior to it
entering into an operational or Stand-Alone Mode.
•
Operational:
Once the SonicPoint has peered with a SonicOS security appliance and has its
configuration validated, it will enter into a operational state, and will be ready for clients.
•
Provisioning
: If the SonicPoint configuration requires an update, the SonicOS security appliance
will engage an SSPP channel to update the SonicPoint. During this brief process it will enter the
provisioning state.
•
Safe Mode
: Safe Mode can be engaged by depressing the reset button, or from the SonicOS peer
device. Placing a SonicPoint into Safe Mode 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 security appliance 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 security appliance detects that it has a firmware update
available for a SonicPoint, it will use SSPP to update the SonicPoint’s firmware.
•
Over-Limit: By default, up to 16 SonicPoint devices can be attached to each Wireless Zone
interface on a SonicOS device. If more than 16 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 16 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 security appliance
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
: If a SonicPoint security appliance cannot find or be found by a SonicOS
security appliance 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
security appliance that is sending Discovery packets, it will leave Stand-Alone Mode, and will enter
into a Managed Mode. The Stand-Alone Mode configuration will be retained.