GigaNews gives IT pros cutting edge insight into the rapidly changing products and practices needed to succeed in the dynamic wireless LAN marketplace.
In this issue:
>>Updated Cisco Unified Wireless Networking v4.01
>>Tech Tip -- Pre-staging Lightweight APs for Specific Controllers
>>Best Practices -- Cisco Wireless LAN Design Guide
>>Bulk Cable & Connectors for Wi-Fi Applications
Training Corner >>
Cisco Unified Wireless Networking v4.01 >> GigaWave has just updated Cisco’s most popular wireless course – Cisco Unified Wireless Networking v4.01. Loaded with hands-on labs and the latest firmware release, this is an intense study of lightweight APs, controllers and how to plan, deploy and manage the Cisco advanced feature set.
View CUWN 4.01 Course Description
Cisco VoWLAN Course >>
This new curriculum is designed to give students the fundamental skills necessary to effectively design, deploy, and troubleshoot a VoWLAN solution. The VoWLAN course builds on the foundational skills taught in Cisco Wireless LAN Fundamentals and Cisco Voice with emphasis on developing skills utilizing Cisco Unified Wireless IP Phone 7920 and VoWLAN endpoints, site survey, wireless infrastructure, security, call control, and troubleshooting.
View VoWLAN Course Description
Tech tip >>
Pre-staging Lightweight APs for Specific Controllers on a Production Network
Cisco provides several convenient options to get lightweight access points (APs) to “settle” on a particular controller on a production network:
- Subnet broadcasts
DHCP, option 43
DNS resolution of the name CISCO-LWAPP-CONTROLLER
Configuration of a Master Controller
Each method is convenient, but sometimes conflicting. In a network that has multiple controllers on one flat subnet, APs can be very stubborn about which controller to associate with. So, the best way to get APs to connect to a particular controller is to pre-stage them from a controlled, laboratory-type network.
Steps to pre-stage a controller:
Set up a lab network. This network should have a single controller giving APs only one choice. This can be accomplished in three separate methods: randomly choose a controller to become the Master Controller, choose to set the DHCP option 43 or create a hostname record on the DNS server that is set to CISCO-LWAPP-CONTROLLER. Only one method is needed to be certain that with only one controller on the network, the AP will connect to it through the discovery process.
Important: Be certain that the controller on the lab network is given a name that is not used anywhere on the production network. The AP will remember the last controller name it received a configuration from. If the AP can’t find the named controller, it will look for another controller in which to connect.
When the AP appears on the lab network and associates to the lab controller, configure it for a primary and secondary controller with names that are on the production network. Because there are certain things a lightweight AP will remember after it reboots, it will remember its IP address (if static), hostname, whether or not 802.11h detected radar on a supported 5 GHz channel, the hostname of the last controller that gave it a configuration, and the primary and secondary controllers it was configured with in the lab network. The fact that those controllers can not be reached from the lab network is immaterial.
Be certain AP Fallback is enabled on the network. This is accomplished by going to Controller>General and enabling AP Fallback. AP Fallback guarantees that APs will return to their Primary Controllers whenever possible. This process can take a few minutes to complete.
Move the AP to the production network.
- The AP will first try to find the controller that last configured it. This will fail because that controller does not exist on this network.
- The AP will then try to find its primary controller. If the AP is on the production network, this should succeed.
White Paper >>