That fixed the problem. but created a whole lot of questions.
With a WiSM, which is actually two controllers, I have the two controllers set up as primary and secondary for each AP. I can only set the power options on the currently associated controller. So do I need to fail the AP over to the other controller, to set the power settings on it also? Or does the AP contain the settings, and will carry it over to the secondary controller should it's primary controller fail?
I would have hoped that these settings would have been in the WCS, so it could be duplicated across all my controllers for me. I do almost all of my LW wireless configurations on the WCS, and have it apply them to all controllers. This is why I hadn't found the AP power settings before, as I spend little time in the controllers web interface.
Another option (esp. if you are using 3rd-party mid-span injectors) with Cisco Non-PoE switches is to disable CDP (Cisco Discovery Protocol).
This is because, although the Cisco switch does not have PoE, it knows about it it from a CDP standard. So, when the AP/LWAP initially powers up (with radios off for minimal power draw), it asks about the PoE capability of the Cisco switch using CDP. The Cisco switch says, I don't have any.
So the LWAP stays half-powered (LWAP is on and can be remotely managed, but its radios are off). For Cisco 1131 LWAP access points, The indication of this half-power state is a rather bizarre solid orange color on the color ring of the 1131 (which Cisco describes as "Amber"). Once CDP is disabled (by either disabling it from the access point or the Cisco non-PoE ethernet switch) all you need to do is power down and power up the access point (or the power injector) and you are ready to go.
(Thanks to earlier post by ron_mckie - Dec 24, 2006, 5:57am PST)