WFS709TP Quick Start Guide Table of Contents Minimum requirements for a WFS709TP Deployment .......................................................... 2 Initial Setup using existing DHCP server.................................................................................. 4 Initial Setup Configuring the WFS709TP as a DHCP server ................................................ 6 Provisioning Access Points....................................................................................................
Minimum requirements for a WFS709TP Deployment At the very least, in a hardware level, to deploy the WFS709TP controller you will need one or more compatible access points, WGL102 and WAGL102. (Note that WG102 and WAG102 APs can be upgraded with a Lightweight image to work with the WFS709TP, refer to the Appendix at the end of this document for more information).
All communication done between the Access Points and the Wireless Controller is done at Layer 3, and for the Access Points to be accessible in the initial setup it is necessary to have a device capable of offering IP addressing by using DHCP. The WFS709TP controller is capable itself of serving as a DHCP server, therefore we will cover both possible deployment scenarios in this document – using the WFS709TP as the DHCP server, or using an already existing server in the network.
Initial Setup using existing DHCP server Most existing networks will have already a device offering IP addressing via DHCP, so for this deployment example, we will assume there is an existing DHCP server in the network and we will use it to allow communication between the WFS709TP controller and the Access Points. Log to the controller by accessing it through it’s default IP address, 192.168.0.250, and configure the initial settings. Please note that if your PC is in a different network than 192.168.0.
After this configuration is done, the test lights on the Access Points should flicker off after a couple of minutes and they should show in the network summary page as unprovisioned:
Initial Setup Configuring the WFS709TP as a DHCP server NOTE: Most existing networks will have already a device offering IP addressing via DHCP, be sure to that no other device is offering this service before you configure your Wireless Controller as a DHCP server, as having two DHCP servers in the same network will cause network communication issues.
Even though there are access points connected to the controller, they will not be detected. Without the DHCP server in the current network, the access points are not able to communicate with the controller. Until the WFS709TP is configured to offer DHCP or there is another server in the network with that service, you won’t be able to see the Access Points and their test light will remain on. Go to Configuration -> Advanced -> Controller -> General and then click on the DHCP tab.
NOTE: Be sure to tick the box “Enable DHCP Server” and click Apply after all settings are input. Changes will not take affect until the Apply button is clicked. After this is set up, you will notice the test light in the connected Access Points will flicker off and they’ll be listed in the Network Summary.
Provisioning Access Points To provision the access points, go to Configuration -> Basic -> Access Point Installation Wizard. Select Layer 2 as discovery method. Click next through the different wizard screens, confirming all your APs are detected, until you get the option to “Provision Now”. Click on this button and wait for the provisioning process to occur. Note that the APs will be rebooted after the process is complete.
Appendix: Converting WG102 and WAG102 to WFS709TP compatible firmware If you have existing WG102 or WAG102 access points, you can load a Lightweight Firmware image to make them compatible with the WFS709TP. Please note that this process is not reversible and will make the Access Points unusable without a WFS709TP controller.
