Wired Intelligent Edge

Hi:

We have enabled the 802.11k profile on our 3400 controller with ArubaOS 6.4.3.6, and configured the Beacon Report Request profile.  However, any changes we make to the Beacon Report Request profile are not being reflected by the actual Beacon Report Request being sent from the AP-104 to the STA (verified with wireshark).  It seems only the 802.11k values or default Beacon Report Request profile values are used.

The STA is 802.11k-capable.  In fact, the AP-104 does not send the Beacon Report Request to the STA when 802.11k on the STA is disabled.

Specifically, changing the following parameters in the Beacon Report Request profile have no effect:

-          Channel

-          Meas duration

-          Meas mode

-          ESSID

-          Reporting Detail

The AP-104 always sends the following parameters in the Beacon Report Request:

-          Channel: as per the higher level 802.11K profile

-          Meas mode: as per the higher level 802.11K profile

-          Meas duration: always 20 for active, or 100+ for passive

-          Rand interval: always 0

-          BSSID: always the broadcast address

-          Reporting detail: always 1

-          Reporting condition: always 0

-          SSID: always KRVLW (this is the AP SSID in the WLAN profile)

Do we somehow need to associate the Beacon Report Request profile to the virtual AP profile?  If so, how do we do it (we could not find it in the documentation)?  Or is this an known issue?

when you are editing the 802.11k profile, click on "show references" to see what Virtual APs the 802.11k profile is associated to.

Hi Colin:

Thanks for your fast response!

We verified the 802.11k profile was properly associated to the virtual AP.

I should point out that when we make changes to the 802.11k profile (e.g. time between beacon report requests, measurement channel, measurement mode), we *do* see those changes reflected in the beacon report measurement request sent by the AP-104.  Our issue is that any changes to the Beacon Report Request profile itself have no effect (they seem to be ignored). 

This brings up another question:  Why are there settings for "measurement mode for beacon reports" and "beacon report request channel" in *both* the 802.11k profile and Beacon Report Request profiles?

Best regards,

Dennis

Those are all good questions.  I think you should open a case with TAC to get them answered.  I am not convinced that feature is used much.