SonicWALL SonicPoint Deployment Best Practices Guide
Overview
This document will guide you through the design, installation, deployment, and configuration issues regarding SonicWALL’s SonicPoint wireless access points. The information covered in this guide will allow site administrators to properly deploy SonicPoints in environments of any size. This document will also cover any related external issues that are required for successful operation and deployment. Please note that SonicWALL cannot provide any direct technical support for any of the third-party
Ethernet switches referenced in this document. 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 in this doc, as we do not have direct relationships with most of these manufacturers. 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: http://www.procurve.com/alliance/members/sonicwall.htm. Prerequisites
SonicPoints require the use of SonicOS Enhanced versions 3.0 and above on the
SonicWALL UTM Appliance; newer versions of SonicOS Enhanced require public Internet access in order for the UTM Appliance to download and update the SonicPoint firmware images. If the device does not have public Internet access, you will need to obtain and download the SonicPoint firmware manually.
One or more SonicWALL SonicPoint or SonicPoint-G wireless access points.
If you are using a PoE switch to power the SonicPoint, it must be an 802.3af-compliant
Ethernet switches. Vendor-specific switch programming notes can be found towards the end of this technote for HP, Cisco, Dell, and D-Link. If not, you will need to use the power adapter that ships with the