Cisco Cisco 5760 Wireless LAN Controller 릴리즈 노트
31
Release Notes for Cisco 5760 Controller, Cisco IOS XE Release 3.2.xSE
OL-28114-04
Caveats
•
CSCui47662
Segmentation fault crash in process cpf_msg_rcvq_process.
There is no workaround.
•
CSCuj25927
fFED crash on a WLC5760 controller running 3.2.2 SE.
There is no workaround.
•
CSCuj31006
Egress SSID policy does not install in FED.
The workaround is to use default QoS.
•
CSCuj51372
In rare cases, Mac Learning does not occur for either ports 1-24 or ports 25-48 on one stack member
in a switch stack. The other stack members are not affected.
in a switch stack. The other stack members are not affected.
The workaround is to reload the affected stack member.
Caveats Resolved in Cisco IOS XE Release 3.2.2SE
•
CSCud25890
The results of the snmp get command on the following MIBs in the cLWlanConfigTable are
inconsistent:
inconsistent:
–
cLWlanNACSupport
–
cLWlanScanDeferPriority
–
cLWlanNACPostureSupport
–
cLWlanWepKeyChange
The snmp set command on the cLWlanNACSupport MIB does not work.
The workaround is to use the show wlan name profile name command.
•
CSCud36670
The ranges for cLQd11aRadioMaxStreams/cLQd11bRadioMaxStreams and
cLQd11aClientMaxStreams/cLQd11aClientMaxStreams do not start at 0. This situation occurs
when you perform an snmp set on cLQd11aRadioMaxStreams or cLQd11bRadioMaxStreams under
cLQd11aCACConfig. The same situation exists for a Radio type.
cLQd11aClientMaxStreams/cLQd11aClientMaxStreams do not start at 0. This situation occurs
when you perform an snmp set on cLQd11aRadioMaxStreams or cLQd11bRadioMaxStreams under
cLQd11aCACConfig. The same situation exists for a Radio type.
There is no workaround.
•
CSCud53860
The snmp get command returns an incorrect value on bsnMobileStationWepState from
bsnMobileStationTable.
bsnMobileStationTable.
The workaround is to use the show wlan name profile-name command.
•
CSCud57372
After a roam operation, when you enter the show policy command, the police-conformed rate state
under a child policy is displayed incorrectly.
under a child policy is displayed incorrectly.
There is no workaround.