03-22-2012 06:03 AM
We have a ticket open but TAC reports no one else has seen this (using version 18.104.22.168, 22.214.171.124, 126.96.36.199 or 188.8.131.52):
At some point after the controller comes up (anywhere from 1 day to 4 weeks), user traffic just stops passing 'through' the controller. Management/ping/etc. all work fine but nothing related to 'wireless' traffic passes. Until 184.108.40.206, traffic would eventually start passing again on it's own. Since 220.127.116.11, I have to reboot to get traffic to pass again. This is on an M3 controller.
Since the issue doesn't appear with version 18.104.22.168, I feel like I can eliminate hardware and 'environmental' issues?
Anyone else seen anything like this? TAC appears to be stumped (a first for me in over 8 years).
03-22-2012 06:07 AM
Do you have anything monitoring that controller, like Airwave? That would help considerably.
Traffic should NOT just stop...
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
03-22-2012 06:10 AM
Yes. The only thing we can determine with Airwave thus far is the number of connected users starts dropping and amount of data passing through goes down. One time we had ~1900 users on and less than 1 mb passing through.
03-22-2012 08:10 AM
DO you see any Crash in the controller?
"show switchinfo" will give you the answer. Also see if there is any spike in CPU or processes on the time of issue.
Principal Network Engineer
Customer Advocacy | Aruba Networks Inc.
Did something you read in the Community solve a problem for you? If so, click "Accept as Solution" in the bottom right hand corner of the post.
03-23-2012 08:16 AM
TAC and I figured it out finally. It's a combination of things but basically comes down to Airwave. It was making changes which weren't needed but based on AOS differences it appeared (to Airwave) they were needed.
Airwave was trying to delete what it thought was a duplicate line in the validuser ACL. The net effect is it deleted both of the rules which resulted in a default deny rule to take effect. The duplication is a result of how ACLs are done with regards to IPv4 and v6 (one for each) whereas older versions of code only put in a line for v4. The Airwave configuration was build using the older code so 1 line was correct.