CUSTOMER RELEASE NOTES
1/21/09 P/N: 9038177-27
Subject to Change Without Notice
Page: 18
of 28
F0615-O
KNOWN RESTRICTIONS AND LIMITATIONS:
Firmware Release 7.0.7.3:
802.11n adapter incompatibility with Spectralink Voice Protocol (SVP) enabled service profiles.
Description
—
Some 802.11n wireless adapters may experience packet loss on wireless services with the
Spectralink Voice Protocol enabled. This problem only exists when using the TRPZ-MP-432 with frame
aggregation enabled.
Workaround
—
When using SVP on the TRPZ-MP-432 disable frame aggregation.
The aggregate throughput exceeds the bandwidth limit of the SSID.
Description
—
Per SSID max-bw is only enforced within the scope of one radio. Therefore, if you configure
multiple SSIDs per radio and configure bandwidth management on the SSIDs, you can exceed the bandwidth for
each SSID.
Workaround
—
Configure bandwidth management on a per radio basis. The limits for service-profile max-bw
and service-profile cac-session are enforced independently on each radio.
Upgrading from MSS 6.0 to MSS 7.0 changes the antenna location from Indoor to Outdoor on the AP.
Description
—
If an AP is configured with the antenna location as Indoor and you upgrade the
MSS version from 6.0 to 7.0, the antenna location changes to Outdoor.
Workaround
—
Reconfigure the antenna with the proper location after upgrading the MSS version.
Changes to the DTD cause incompatibility with cluster configuration.
Description
—
MSS Cluster Configuration relies on configuration options being consistent between cluster
members. Changes to configuration options introduced between releases can result in synchronization problems
between cluster members.
Workaround
—
All RASs in a cluster configuration should have the same version of MSS.
Using the quickstart command on the TRPZ-MX-2800 incorrectly sets VLAN tag ID.
Description
—
When configuring the TRPZ-MX-2800 using the quickstart command, it is possible to configure
an invalid VLAN tag value for the default management VLAN.
Workaround
—
After completing the quickstart configuration, create a new VLAN with the correct VLAN tag.
Using the auto-ap feature does not allow load balancing on individual radios.
Description
—
When using the auto-ap feature, it is not possible to set all of the AP attributes. Per AP load
balancing control is not supported on auto-ap. The system global settings for load balancing applies to all
auto-aps.
Workaround
—
If you must configure a load-balance group for a specific AP, configure the AP as a regular AP.
Auto-aps do not behave correctly on cluster seed when the maximum number of APs are configured.
Description
—
When a cluster seed RBT-8xxx boots an auto-ap, it checks the seed configuration on the RBT-
8xxx to determine if the cluster can support any additiona
l AP‘s. If the system is already configured with the
maximum number of APs allowed, new auto-aps do not operate correctly.
Workaround
—
Reduce the number of configured APs in the cluster configuration.
Voice handsets can be sensitive to changes on an in-service SSID.
Description
—
Particular voice handsets are sensitive to changes made to an in-service SSID. This can result in
the handset operating with stale connection information.
Workaround
—
When using affected handsets, disable the Service Profile prior to making any configuration
changes.
Some RAS controllers show an incorrect CPU load.
Description
—
RAS controllers show an erroneous CPU load of 100% in the command line interface. This will
be fixed in the next version of MSS.
Workaround
—
None.
