WLAN Controller Installation

In centralized WLAN solutions, the WLAN controller should now be physically installed. This is important because it is this device that actually configures, manages, and "controls" the access points themselves. Without the controller present and operating, the access points will not function.

Access Point Configuration

Now that the access point has been physically installed, connected to your network, and powered, you can finalize its site-specific configuration. Depending upon the product you have deployed, access point configuration (and management) may be handled automatically by a so-called WLAN controller or WLAN switch, or you may need to configure the access points individually.

Access points that require individual configuration can be handled by your WLAN deployment vendor (if you have chosen one) or your own internal IT staff. In the former case, you will need to provide network access to your vendor, along with configuration details and security settings. As a result, many enterprises prefer to carry out this step themselves.

Access points that are automatically configured by a WLAN controller or WLAN switch are usaully easier to deploy. Each model (centralized, WLAN controller-based, or distributed, access point-based) has its advantages and disadvantages that you will have examined and evaluated during your architecture phase.

Testing

Once the access points have been installed and configured, you are ready to begin testing. This is a vital step in any deployment, as this allows you to detect any potential problems before the service is launched. This, in turn, avoids unnecessary support costs and helps reduce the TCO. Larger, multisite deployments may justify formalizing this into a systematic post-installation acceptance test, but even smaller-sized deployments should undertake some tests. The test plan should include

• Connectivity of access point to rest of the network

• Successful authentication (login)

• Successful roaming from AP to AP

• Throughput testing

• Validation of cell overlap

• Validation of coverage

Include a copy of the post-installation acceptance test as an addendum to the site survey document. That way you not only have a written record of the WLAN installation for that site, but you also have a copy of the test validating the settings and AP locations. This can be particularly important for wireless networks because many factors can change the environment. Troubleshooting may be aided by understanding what was known to work at the time of installation.

Client Installation

One of the final tasks that you must undertake is the actual installation of the client adaptors and software. This may require your users to self-install the software from a centralized server, or they may have the software preinstalled on their laptops. Many large enterprises have automatic software distribution frameworks (such as those provided by LANdesk, Microsoft SMS or Altiris), and these can be used to good effect. Even though some operating systems support wireless networking natively (such as Windows XP and MacOS), we recommend using dedicated client software provided by equipment manufacturers if possible as they provide richer feature sets and more detailed configuration capabilities. These tend to have significant additional features that both users and IT staff find useful.

Today, the majority of devices will have the wireless adaptor already embedded. This includes newer laptops and many ASDs. However, some devices may require you to provide a wireless adaptor, usually a PC card (PCMCIA) or sometimes a USB or CompactFlash card. The form factor is not important; rather it is a controlled method in distributing these to your user base. Ensure that the adaptors have been flashed and have the latest firmware, drivers, and software. This may present an additional challenge for embedded clients but should not be overlooked.

When you are distributing the client adaptors or software, make sure to provide a communication pack to the user. This should include FAQ, some information on the wireless technology and security you are adopting, the goals of the solution, and basic instructions on how to use the service, including calling technical support.

Production Launch

Your site is ready for production services. You have performed the site survey, installed the equipment and supporting infrastructure, configured the wireless settings, tested the service, distributed the client hardware, and communicated the status to your end users. Expect an initial surge of interest in the service and a high number of technical support calls. Ensure that your technical support organization is aware of and expecting any impending site launches. Ideally you should avoid too many service launches within a short period of time, because this will allow your first-and second-line support teams to handle the spike in cases. You may also encounter a few teething problems because production status may highlight some overlooked configuration errors and provide much more intensive "stress testing." You should allow for some technical resources (second-and even third-level support) to be available during the first week or two of usage. Close monitoring of the service is also recommended in the early stages. This will enable you to validate the design and detect problems early.