08-05-2009 01:59 PM
As a result, those users are taking up 2 sessions on the controller and sometimes we eventually top out at 256 user sessions.
I thought it might be the XP "build" that we use on the company laptops, but a brand new laptop with a raw (Microsoft standard) XP install (Service Pack 2) will exhibit the same behavior.
I was able to verify that the laptops are sending two packets with different source IP's but the same source MAC by running a WireShark capture on the test machine and reading through the saved capture file.
ArubaOS version 126.96.36.199
Aruba 800-16 controller.
All Aruba AP-60, AP-61, and AP-70 Access Points
Has anyone else seen this behavior?
Thanks in advance,
08-05-2009 02:19 PM
You'll need to configure and enable a "valid-user" ACLs which basically prevents these known wired networks from being placed into the user datapath, thus preventing the multiple entries and keeping you well under the max user count of the controller.
Should be referenced in the documentation.
08-09-2009 11:16 AM
There is no specific documentation about this, but the "validuser" acl is the way to deal with this. Details about the validuser ACL and how it can prevent 169.x.x.x and other undesirable addresses from entering the user table is listed in the knowledgebase on the support site, answer ID 40.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base