20WIRELESS LAN SWITCH AND CONTROLLER MSS VERSION 6.0.4.6 RELEASE NOTES

Client and Session Parameter

Supported Value

 

 

Active AAA sessions (clients trying to

WX4400: 2500

establish active connections) per WX

WX2200: 3200

switch

WX1200: 300

 

 

WXR100: 75

 

These are the suggested maximums.

 

The switch might be able to support

 

even more sessions, but performance

 

or system stability might be affected.

 

 

AAA users configured in local data-

WX4400: 999

base

WX2200: 999

 

 

WX1200: 250

 

WXR100: 250

 

 

Known Problems

System Configuration Issues

Adding a static VLAN with the same name as a VLAN whose traffic is being tunneled through the switch can cause the switch to restart.

(18367)

MSS can tunnel traffic for a VLAN through a WX switch that does not have that VLAN statically config- ured. If you attempt to add a static VLAN to a switch that is already tunneling traffic for a VLAN with the same name, the switch can restart.

To create the VLAN, clear the Mobility Domain configuration from the switch, create the VLAN, and then configure the Mobility Domain again.

The default value for RADIUS “deadtime” shown in the CLI help is incorrect. (41689)

The correct default value is 0.

When upgrading systems with large configurations, it may be necessary to save the configuration to a backup file. (41330)

When upgrading systems with very large configura- tions, for example, hundreds of APs or hundreds of users, it may be necessary to save the configuration to a backup file, generate a minimal configuration, perform the update, load the backup configuration from the command line, and then save the configuration.

Time and date do not synchronize with an NTP server, if the switch's NTP client is enabled before the NTP service is started on the server. (20382)

Using set ap <apnum> boot configuration commands. (38517)

The set ap <apnum> boot-configuration switch switch-ip cannot be set at the same time as set ap <apnum> boot-configuration switch name <switch-name> dns <ip addr>. The commands overwrite each other when used.

The auto-config feature does not work properly if the 3WXM server is unreachable when the auto-config feature is enabled. (44477)

To work around this issue, be sure that the 3WXM server is reachable from the wireless switch before you enable auto-config. If auto-config is enabled by default on the wireless switch, be sure that the 3WXM server is reachable before you boot the wireless switch.