Wireless Access

Hi

I've created a case with TAC aswell, but just wanted to share this here aswell in case anyone have experienced similar symptoms. 

I have 2 different customer, one which I've configured, the other configured by another tech (so human errors in configuration shouldn't be the cause).

both have Mobility Master, both run 8.2.0

both have2 controllers in cluster (#1 have Aruba7220 and #2 have Aruba 7240XM)

#1 have Clearpass for 802.1X and #2 have WIndows NPS.

Problem occurs on both EAP-TLS and PEAP-msChapv2 secured networks.

The problem starts with no warning. 

Some clients can't connect, others can

absolutely no hits in event viewer of either REJECT or ACCEPT in NPS or CLEARPASS

reboot controller #1 - everyting is back to normal.

And given that this is 2 different installations and customers, the seems TOO random for me.

we can ping NPS/Clearpass - but no auths show in logs. 

there have been no changes in networking topology the last couple of weeks 

all kinds of clients. MAC, WIndows, iOS, Android. Some work - some don't.

I've asked customers to both verify that they're on 8.2.0.1 and not 8.2.0

maybe this fixed bug report from 8.2.0.1 release is related to the errors

BUG REPORT 170217 170241

Symptom: Clients were unable to connect to an SSID when 802.11r
was enabled on the managed device. The fix ensures that the clients
successfully connect to the SSID without service interruption.
Scenario: This issue occurred when the clients attempted a full
802.1x authentication after an 802.11r roam. This issue was
observed in managed devices running ArubaOS 8.2.0.0.

Hi,

Check if the RADIUS server ip address in the MD has changed to 127.0.0.1 after upgrading to 8.2.0.0. Change it back to the IP address you used before.

IP-addresses is the same. This happens "all of a sudden" and a controller reboot fixed it. For a while. 

Looks like the error happens on both 8.2.0.0 and 8.2.0.1

I have done quite some with ArubaOS 8.x and 8.2.0.1. What you describe doesn't sound familiar, and I would encourage you to escalate this issue with Aruba TAC as clients not able to connect to a wireless network is a big problem that shouldn't occur.

The escalation procedure is explained in the TAC Quick Reference Guide.

Also, try to contact your local Aruba SE so that she or he is aware of your issues.

looks like this was a bug - fixed in AOS 8.2.0.2; 

from resolved issues - 8.2.0.2 release notes

Symptom: RADIUS authentication failed after upgrading the Mobility
Master to ArubaOS 8.2.0.1 when the managed device are in a cluster.
The fix ensures that the RADIUS authentication is successful.
Scenario: This issue occurred when configuring aaa authentication
servers for managed devices. This issue was observed in a cluster
setup running ArubaOS 8.2.0.1.

I had this exact issue, as well. Upgrading to 8.2.0.2 fixed mine. I am now having several other problems, but that is for a different thread :-)  AOS 8 has not been a smooth implementation, at all.

Random disconnects. Slowness. VLANs broadcasting or L2 multicasting to other VLANs. Its so random, its impossible to narrow down.