12-07-2010 04:56 AM
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
12-14-2010 06:23 AM
12-14-2010 06:40 AM
I've had opened a similar case for a problem that I saw in 188.8.131.52 and 184.108.40.206. For me, this problem was fixed in 220.127.116.11.
I had a meeting with a senior TAC engineer last week and asked him if the rebooting issues from 18.104.22.168 and 22.214.171.124 were still in the 5.0 train. I was told that 126.96.36.199 incorporated those changes.
Also, you can run the following command from the CLI of the controller where the AP is connected:
show ap debug system-status ap-name "
TAC will ask you for this output and it should confirm what you're seeing on your syslog server.
Hope this helps!