Hi Eric,

I haven't tried either of those but I will do as soon as.

I'm using names for the first and second controllers (I'm haven't spec'd a third due to the controllers being geographically distant).

These particular APs had been quite stable until I upgraded the controllers to said s/w version around a month ago, though APs on other upgraded controllers are fine. Also no matter where the APs are registered to they report (via WCS) that they are running vers 3.2.195.10 s/w, however interrogating the relevant controller directly says they are running vers 4.1.171.0.

I was also in the midst of adding some new APs; these were autonomous ones that I converted (at my desk) and specified the suspect controller for them to register with during the conversion, the new APs registered ok with the controller and I set the same controller as their primary and set them aside for installation. After your reply to my initial query I've booted one of the newly converted ones again and they have registered with a random controller elsewhere on our network (I'm using option 43) rather than their primary.

Apologies for the info overload, hopefully you can make some sense out of it.

Many Thanks

Scott

From WCS| configure controllers, select the controllers & do a refresh from network. Does WCS still show them as 3.2.195.10?

I had this same issue. I had 20 APs as 4.1.171.0 and 72 at 4.1.181.0 which is what the controllers are on. I ran an ap inventory report from WCS & sure enough, all 20 APs that were running 4.1.171.0 were bound to the same controller. A quick bounce of the controller took care of it. I went into WCS, ran the report again and all APs were at the current level. Must have not rebooted the controller after the upgrade.

Regarding the issue of the AP not going to the primary... perhaps the suspect controller is running in master mode; a no-no for a wireless network that is in production

Hi Eric,

Perhaps I should just upgrade to 4.1.181.0 and see if that resolves the problems.

Thanks

Scott

4.1.185 is out there as well (I have not yet tried it in our system)

Also, for the access points that have been upgraded from from Autonomous to LWAP, you may want to make sure that the security certificates/hashes are in each of the controllers that will be managing the LWAPs.

- John

Hi John,

Actually, I've had no problems with the converted APs (touch wood), however, I have tried loading the csv files produced by the upgrade tool into WCS and WCS says they are empty, opening them with Excel confirms it.

Scott

Hi John,

Yes - I've downloaded 4.1.185.0 from Cisco - I'll try it on the misbehaving controller and post the result.

Regards

Scott

What changes are in 4.1.185. I did not find any link for 4.1.185 release notes, 4.1.181 is the latest rel notes available.

It is at the bottom of the list for some reason.

Ah, thanks. I thought I was getting crazier than I already am

I've had similar problems on my blade. It seemed that the primary controller lost it's setting under Master Controller mode. This would happen seemingly random, though often during upgrades.

Reenabling the setting fixed the problem.

If I remember correctly I found a case of this somewhere on the cisco pages.