Honeywell HX3 User Manual page 165

Parameter Default
Ad Hoc Channel 1
Aggressive Scan On
CCX or CCX BG: Off
Features A: Optimized
WMM Off
Auth Server Type 1
TTLS Inner Auto-EAP
Method
PMK Caching Standard
Description
Use this parameter when the Radio Mode profile parameter is set to Ad Hoc.
Specifies the channel to be used for an Ad Hoc connection to another client
device. If a channel is selected that is not supported by the by the radio, the
default value is used.
Options are:
1 through 14 (the 2.4GHz channels)
36, 40, 44, 48 (the UNII-1 channels)
When set to On and the current connection to an AP weakens, the radio
aggressively scans for available APs.
Aggressive scanning works with standard scanning (set through Roam
Trigger, Roam Delta and Roam Period). Aggressive scanning should be set
to On unless there is significant co-channel interference due to overlapping
APs on the same channel.
Options are: On, Off
Use of Cisco Compatible Extensions (CCX) radio management and AP
specified maximum transmit power features.
Options are:
Full - Use Cisco IE and CCX version number, support all CCX features. The
option known as "On" in previous versions.
Optimized –Use Cisco IE and CCX version number, support all CCX features
except AP assisted roaming, AP specified maximum transmit power and
radio management.
Off - Do not use Cisco IE and CCX version number.
Cisco IE = Cisco Information Element.
Use of Wi-Fi Multimedia extensions.
Options are: On, OffDevices running Windows XP can change the default
value. Devices running all other OS cannot change the default value.
Specifies the type of authentication server.
Options are: Type 1 (ACS server) and Type 2 (non-ACS server)
Authentication method used within the secure tunnel created by EAP-TTLS.
Options are:
AUTO-EAP (Any available EAP method)
MSCHAPV2
MSCHAP
PAP
CHAP
EAP-MSCHAPV2
Type of Pairwise Master Key (PMK) caching to use when WPA2 is in use.
PMK caching is designed to speed up roaming between APs by allowing the
client and the AP to cache the results of 802.1X authentications, eliminating
the need to communicate with the ACS server. Standard PMK is used when
there are no controllers. The re-authentication information is cached on the
original AP. The client and the AP use the cached information to perform the
four-way handshake to exchange keys. Opportunistic PMK (OPMK) is used
when there are controllers. The re-authentication information cached on the
controllers. The client and the controller behind the AP use the cached
information to perform the four-way handshake to exchange keys.
If the selected PMK caching method is not supported by the network
infrastructure, every roam requires full 802.11X authentication, including
interaction with the ACS server.
If the active profile is using WPA2 CCKM, the global PMK Caching setting is
ignored and the client attempts to use CCKM.
Options are: Standard, OPMK
This change does not take effect until after a Suspend/Resume cycle.
9 - 13