Wireless Access

I updated my 3400 controllers on saturday to ver 6.4.2.4 

Now, in one site (Netherlands) that has 6 AP 105's, users now cannot connect to wireless using the main ssid. They can connect using the guest ssid.

24 other sities also using the same controller can connect fine using either ssid.

TAC support call could not come up with a reason for this.

In the logs on the controller... when a test laptop tries to connect i see this error...

MIC failed in WPA2 Key Message 2 from Station e8:b1:fc:a2:72:31 d8:c7:c8:1e:eb:b8 nlhoo1wlsap03

nlhoo1wlsap03=AP

e8:b1:fc:a2:72:31=MAC of test laptop in the affected office.

Any ideas?

I don't believe this is a client driver issue, as many other sites using company imaged laptops on the same controller are connecting fine. Also, the fact that the users in the affected office can connect to the guest ssid in the same office, but not the main ssid.

Also...in testing we did confirm the AP's can see the offsite DHCP server, as we put a laptop directly in one of the AP switch ports, and it did get an IP and "see" the internet.

Toddo,

If this is a preshared key network, that message is triggered when there is an incorrect preshared key.

There is no preshared key that I am aware of. 

We provision the APs when they are new, and basically just point them to the controller that they will connect to. I've never seen a key.

Auth is 802.1x  with AES encryption

Did you enable user debugging for all of those users?  MIC failed is not always a total failure.  If there is something that is keeping your users from connecting, it is usually more than that.

user-debug was on for the test laptop mac address only, as that was the only traffic being sent.

<logging level debugging user-debug (mac address of laptop).

the error i posted was the only entry i saw associated wit that laptop

Well, if all of the users cannot connect, we need to see their user debug to see if there are related or unrelated entries.  We don't want to assume that is the only reason devices are not connecting.

well...here's Arubas response....

But....Thank you though for your prompt replies  :)

 <<As discussed over the call We do see some known issues with bridge mode in 6.4.2.4 release notes, so the best option to bring back the network is to downgrade the controllers back to the old 6.3 code version.>>

Was the issue resolved in 6.3.x or 6.4.x?

bug 111273 was fixed in 6.4.2.5 and actually has nothing to do with mic fail errors.