Having conducted more surveys then a belt will allow notches you start to find ways to improve your survey skill set with accuracy and speed. One of these ways came to me completely by accident one day many years ago at lunch.

If you are new to surveys or perhaps you have a few hundred already under your belt. The common theme to a good active survey is to understand your lowest powered clients and sensitive applications and their limitations. It is also important to understand the environment in which these devices will operate. Then calibrate your survey cards to these lower devices, which can be tricky for someone with limited experience.

There are many decent tools in which you can conduct active site surveys. One of these tools in which I am very familiar with is AirMagnet Surveyor. But never ever assume ANY old wifi card is OK to conduct a survey. In fact, when conducting active surveys you want to use the identical card or one very close to which will be used by your customer.

Example -- If you are surveying for Vocera B2000, Cisco 7921,7925, Ascom i75 deployment you don’t want to roll in with a 200mW card or a crappy chipset and let it run loose!?

When I survey for a Voice assessment I like to use that device during my assessment. Why? Because you know WITHOUT QUESTION how that phone / vocera badge / ascom phone will operate.

When I survey for a Vocera deployments, I will use the badge in survey mode in combination with AirMagnet. I will wear the badge around my neck enter the room, door closed and my back to the door and see what the Vocera badge is telling me. You will be surprised when you see what a pcmcia card reads and what the badge reads! In fact the majority of Vocera deployment failures is due to poor assessments. Thus the reason why Vocera has pulled in the assessment portion for their deployments.

Same holds true for handset deployments with Cisco, Ascom and others. These devices have a site survey mode as well. I will put these devices in site survey mode and use in combination with AirMagnet. Then one day at lunch many years ago I attached my Cisco handset to my laptop! Light bulb went off! What better way to survey and easily see the phones survey readings!

I hope you find this helpful during your surveys as well!

DHCP address assignment required is one of those check boxes that make you go huh, while you scratch your head, if you don't know how it works. Cisco's best pratice for voice is to disable this feature. However, keep in mind,  if DHCP Addr. Assignment Required is selected, clients must obtain an IP address via DHCP. Any client with a static IP address is not allowed on the network.

request/renew every time they associate to the WLAN before they are allowed to send or receive other

After having worked on countless Cisco WLAN VoIP deployments a general rule of thumb from Cisco TAC is to disable TKIP countermeasure on ALL voice WLANs and lessen the timer for DATA WLANs. Again this is all subject to your comfort level and performance requirements. Personally, I can't say I have ever seen this to be an issue or had an issue that was directly related to the countermeasure. But something to chew on!

TKIP countermeasure mode can occur if the Access Point receives 2 message integrity check (MIC) errors within a 60 second period. When this occurs, the Access Point will de-authenticate ALL TKIP clients associated to that 802.11 radio and holdoff any clients for the countermeasure holdoff time (default = 60 seconds).

(Cisco Controller)config wlan security <tkip> hold-down <seconds> <wlan id>

Note:  Configures TKIP MIC countermeasures hold-down timer (0-60 seconds)

The following command disables TKIP countermeasure on WLAN 1 

(Cisco Controller) >config wlan security tkip hold-down 0 1

When using EAP-FAST you want to insure you give the client enough time to obtain the PAC. By default the WLC is set to only 2 seconds. However I noticed with code 6.0.188.0 it is set to 30 seconds by default. This command can only be configed from the CLI of the WLC.

When using EAP-FAST, the IEEE 802.1X timeout on the controller must be increased (default = 2 seconds) in order for the client to obtain the PAC via automatic provisioning. The default timeout on the Cisco ACS server is 20 seconds, which is the recommended value.