Known Problems
21
time. This can occur if the DHCP server that responds
to the DHCP request after the second reboot is not
the same server that responded to the first request.
This issue does not prevent the MAP from operating
normally but can make managing the MAP more diffi-
cult if the address the MAP receives the second time is
not predictable. To prevent the MAP from using more
than one address, use static address assignment in
your DHCP server.
An 802.11g radio might enter 802.11b protection
mode if an 802.11g radio advertises its 802.11b
and 802.11g rates separately. (17222)
Some third-party access points advertise the 802.11b
transmit data rates they support in one information
element (IE) and the extended 802.11g-only data
rates they support in another IE. An AP2750 802.11g
radio responds to this by assuming the other radio is
an 802.11b radio and enters 802.11b protection
mode.
To guard against interference, an 802.11b/g radio in
protection mode sends messages while 802.11g traf-
fic at higher data rates is being sent, to inform
802.11b devices about the 802.11g traffic and
reserve bandwidth for the traffic. Protection mode
affects overall traffic throughput due to the additional
messages sent by 802.11b/g radios.
When the radio enters protection mode, a message
such as the following appears in the WX switch’s log
buffer:
MAP Jul 09 21:01:36.845822 WARNING Port 5
ap_radio: 802.11b protection enabled due to
proximity to network with BSSID of
00:0b:0e:00:fd:c0
The display ap status command shows 802.11b
protection enabled after an 802.11b/g radio is
reconfigured for 802.11b or 802.11a. (15308)
If you reconfigure an 802.11b/g radio to support
802.11b (without 802.11g) or 8012.11a, the
display
ap status
command shows the radio’s state as con-
figure succeed (802.11b protect), even though pro-
tection mode is inapplicable because 802.11g is
disabled on the radio.
You can safely ignore the 802.11b protect indication
in the command output. This issue is cosmetic only
and does not affect the operation of the radio.
3WXM Issues
Deleting PEAP-MS-CHAP-V2 AAA methods in an
802.1X policy with 3WXM might not be reflected
on the WX switch. (14157)
If you specify multiple AAA methods (for example,
multiple server groups) for a PEAP-MS-CHAP-V2
802.1X policy, and you remove the last method with
3WXM, the WX switch might still use the removed
method. For example, if the 802.1X policy contains
the following methods, and you use 3WXM to
remove method sg3, the WX switch continues to use
sg3:
set authentication dot1x ssid any EXAMPLE\*
peap-mschapv2 sg1 sg2 sg3
