Wireless Access

Hello Guys,

I am migrating a customer from Release 6 to release 8. They have AP325 with LACP striping configured in release 6.

I want to reuse the configuration in my new setup

I configured this on my Managed Network level; but it seems that it is not completely working. Only users on 2.4 GHz can connect on an open SSID. And when we are connecting to a 802.1X enabled SSID our authentication isn't working anymore; once we disabled LACP striping, all is working again.

My configuration is => LACP striping IP  = LMS IP1

I have 2 controllers so I configured on managed network level:

LACP striping IP controller1: LMS controller1+1

LACP striping IP controller2: LMS controller2+1

We also use HA redundancy

I wanted to configure clustering (since I read that this would resolve this by itself) but I lost my confidence in clustering, when I had 2 customers in a L2 setup where clients connected to controller 2 when APs are connected to controller 1, couldn't connect to the WLAN anymore after enabling clustering.

Striping LMS IP can no longer be used to stripe the traffic as each AP has GRE tunnels to more than one
managed device. Therefore, starting from ArubaOS 8.2.0.0, Cluster LACP is used to stripe traffic on a per-UAC
ArubaOS 8.3.0.0 | User Guide Controller Clustering | 330
331 | Controller Clustering ArubaOS 8.3.0.0 | User Guide
basis. That is, in a cluster setup, the clients or users on the same AP are steered to different UACs and the traffic
is striped to these UACs.
When cluster is enabled, striping IP is not used even if it is a single-node cluster; the striping of traffic for the
Ethernet interfaces is according to the UAC node.
For a non-cluster setup, the striping LMS IP is used in the same way as before.

Anyone saw any of these 2 issues before? (so LACP Striping issue and Clustering issue?

Kind regards,

Ok, forget my question; I will configure Clustering; I just found the problem of my clustering setup; it is related to a bug of HA; but also valid for clustering (same errors in user-debug)

Symptom: A client fails to connect to an SSID. The log file for the event lists the reason as Capability requested by STA unsupported by AP.
Scenario: This issue occurs during a failover in a High Availability (HA) setup, when no Virtual Local Area Network (VLAN) is assigned for a Virtual Access Point (VAP) profile and the VAP is
configured in tunnel mode.
Workaround: Configure a VLAN ID in the VAP profile by using the vlan CLI command.

Hey Thomas,

I have AP345 setup for LACP striping and although it is working, I question the need for the LMS-IP's in the AP System Profile. 

Our customer is running 8.5.x in Cluster setup. Typically with a Cluster Setup, you dont use LMS in the AP-System profile. However the LACP setup requires it.. I think. 

How do you have your AP-System profile configed?

If anyone from Aruba is reading, can you reference a guide or article that breaks this down for a CLUSTER setup. I can only find 8x documentation for old-shool HA Setup or even older Master/Standy with LMS Failover. 

Helps if I read the actual User-Guide. Page 365 of the 8.5 User Guide has a note that states "The lms-ip value in ap-system-profile will be used as a key to look up entries in ap-lacp profile.". 

So it appears it is indeed needed.