Filter
Top Products
SonicPoint > SonicPoints
528
SonicOS 5.8.1 Administrator Guide
You can change the file name of the SonicPoint image, but you should keep the extension
in tact (ex: .bin.sig).
Step 3 In the SonicOS user interface on your SonicWALL appliance, in the navigation pane, click
System and then click Administration.
Step 4 In the System > Administration screen, under Download URL, click the Manually specify
SonicPoint image URL checkbox to enable it.
Step 5 In the text box, type the URL for the SonicPoint image file on your local Web server.
Step 6 Click Accept.
Automatic Provisioning (SDP & SSPP)
The SonicWALL Discovery Protocol (SDP) is a layer 2 protocol employed by SonicPoints and
devices running SonicOS Enhanced. SDP is the foundation for the automatic provisioning of
SonicPoint units via the following messages:
• Advertisement – SonicPoint devices without a peer will periodically and on startup
announce or advertise themselves via a broadcast. The advertisement will include
information that will be used by the receiving SonicOS device to ascertain the state of the
SonicPoint. The SonicOS device will then report the state of all peered SonicPoints, and
will take configuration actions as needed.
• Discovery – SonicOS devices will periodically send discovery request broadcasts to elicit
responses from L2 connected SonicPoint units.
• Configure Directive – A unicast message from a SonicOS device to a specific SonicPoint
unit to establish encryption keys for provisioning, and to set the parameters for and to
engage configuration mode.
• Configure Acknowledgement – A unicast message from a SonicPoint to its peered
SonicOS device acknowledging a Configure Directive.
• Keepalive – A unicast message from a SonicPoint to its peered SonicOS device used to
validate the state of the SonicPoint.
If via the SDP exchange the SonicOS device ascert
ains 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 and SonicPointN States
SonicPoint and SonicPointN devices can function in and report the following states (in all states
listed below, SonicPoint refers to both SonicPoint and SonicPointN devices):
• 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.