Filter
Top Products
SONICWALL SONICOS ENHANCED 2.5 ADMINISTRATOR’S GUIDE
123
SonicPoint Provisioning Profiles
If via the SDP exchange the SonicOS device ascertains that the SonicPoint requires provisioning or a
configuration update (e.g. on calculating a checksum mismatch, or when a firmware update is
available), the Configure directive will engage a 3DES encrypted, reliable TCP based SonicWALL
Simple Provisioning Protocol (SSPP) channel. The SonicOS device will then send the update to the
SonicPoint via this channel, and the SonicPoint will restart with the updated configuration. State
information will be provided by the SonicPoint, and will be viewable on the SonicOS device
throughout the entire discovery and provisioning process.
SonicPoint States
SonicPoint devices can function in and report the following states:
• Initializing – The state when a SonicPoint starts up and advertises itself via SDP prior to it
entering into an operational or stand-alone mode.
• Operational – Once the SonicPoint has peered with a SonicOS device 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 device will
engage an SSPP channel to update the SonicPoint. During this brief process it will enter the
provisioning state.
• 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.
Provisioning
Operational
Updating
Firmware
Initializing
Rebooting
Provision
Failed
Firmware
Failed
Over-limit
Non-responsive
Safemode
SP over
limit>16
Power-Up
Checksum
mismatch
Firmware
mismatch
Checksum
Match
Success
Failed
Success
Failed
No SDP for 3
seconds
Reset/GUI
Command
No SDP for 5
seconds