Controller Based WLANs

What is the strict compliance option in the Virtual AP Profile?

Product and Software: This article applies to all Aruba controllers and ArubaOS 2.x and 3.x.

 

Aruba checks the following compliance parameters if strict-compliance is enabled:

 

  •         Privacy Bit: The wireless station privacy profile in the "Capability Info" part of the 802.11 frame should match the AP privacy profile for a successful association.

Example:

 

If a wireless station is associating to an AP that is configured for static WEP and has the correct WEP key but does not set the "privacy bit" to 1 in its 802.11 header, then it will not be able to associate to the Aruba AP unless strict-compliance is disabled.

 

  •   Transmit Rates: The wireless station should have some 802.11 supported rates in common with the Aruba AP in its Association Request or else it will be denied unless strict-compliance is disabled.
  •   Short Preamble: If an 802.11b wireless station tries to associate with short preamble bit set in the 802.11 header when it is disabled on the Aruba AP, then it will be denied unless strict-compliance is disabled.

By default, strict-compliance is disabled. Keeping it disabled helps for better interoperability with any NIC (usually helps out legacy NICs, prior to 2004).

Version history
Revision #:
1 of 1
Last update:
‎07-09-2014 01:46 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.