Not sure if others have had same issues with 7.4.100.60 version wlc code but here a new "feature" found on it. We've got about 50 old 1130 AG accesspoints (AIR-LAP1131AG-E-K9) now some of them got totally lost with a power outtage we had lately. One site has 25 of these and 15 of them went stone cold.
After some serious testing of these blacked out AP:s I found out that there must be some serious code bugs with the PoE on these AP:s. Some of the 1130:s started to recover with just repluging in them to PoE+ capable switch, some just woke up with a swap from Cisco Poe switch to HP ProCurve poe switch. Some did not respond to external power at all, in any circumstances nor did they respond to being plugged to HP or any Cisco PoE capable switch. They were plugged / unplugged for any time between 5 to 60+ minutes. Only thing that made these AP:s responsive was to get these plugged on to a 2960S poe+ capable switch.
Cisco Small business 8port switches got their interfaces into fault mode when these AP:s were connected. HP switches (two different models were tested on site) at times responded to these AP:s with few seconds of LED blink, or no response at all.
Any case, all AP:s do seem to get back on line after just beeing plugged to PoE+ capable switch and there after beeing replugged to their place on standard PoE capable switch. Cisco 3560 IOS switch did make those AP:s to function properly, or it did not do any change to their stone cold status.
I would not be as unhappy with this as I am, if the Prime 1.3 would perform better but hey it is really browser picky piece of software. It was really disapointing to update from 7.1. WCS to Prime 1.3 as its functionality on daily tasks got so picky with the browser and actually at times it seems to be able to do things, and at times it says it did what it was supposed to do but hey, nothing happens and deeper in the log files you find SNMP errors with the task you just thought went along flawlessly. Say add a new VLAN to two separate WLC with prime, yes. it does it on both WLC:s. If you go to WLC to see if that VLAN is there, with the IP-address providen, yes it is there.
Then you move along and configure the WLAN interface to use these VLAN interfaces, and Prime tells you that the task to publish this set of WLAN settings is successfully added to task queue. Then you go and see if WLC:s have those WLANS defined and boom. no sign of them any where around. You check the task info (of publishing that wlan to wlc:s) on Prime and now it tells you Prime could not perform SNMP task to deliver those settings to WLC:s. Yippikayee.. And you do that few times again from scratch and in vain. Finally you, as an smart admin that you are, you just write those settings to WLC:s one at the time and there after you put the Prime back to work and you fetch the configuration from WLC:s to Prime and now you are back up to date with configurations.
I'm most certain this was way easier with the WCS. Too sad it does not support these 2600 and 1600 ap:s we have :/
Point of this post. Peeps, when upgrading from old environments, please skip this 1.3 prime and 7.4.100.60 wlc-version and get more robust software. We did this upgrade last summer, in a tight timeframe, and now it backfires.. Gotta do some upgrading again.
Message was edited by: Pekka Halonen Forgot 3560 series poe switch from the writeout..
