3com 3CWXMUPA User Manual

Page 1

WIRELESS LAN SWITCH MANAGER (3WXM) VERSION 3.2.5 RELEASE NOTES

Software License Agreement

Before you use the 3WXM software, please ensure that you read the license agreement text. You can find the license.txt file on the CD-ROM that accompanies your product, or in the self-extracting exe that you have downloaded from the 3Com Web site.

What's New in 3WXM Version 3.2

3WXM Version 3.2 contains the following enhancements:

■ Support for new MAP models: AP7250, AP8250, and

AP8750

■ Support for more 802.11b/g channels for the IL

(Israel) country code

■ SSID support in location policies

■ Support for SNMP trap enhancements in MSS Ver-

sion 3.2.

Support for New MAP Models

You can configure the following new MAP models:

■ AP7250—Contains one 802.11b/g radio.

■ AP8250—Contains one 802.11b/g radio. It also has

the ability to have an additional radio installed in it.

■ AP8750—Contains one 802.11a radio and one

802.11b/g radio.

Additional Channel Support for Israel

3WXM Version 3.2 supports the expanded 802.11b/g channel set that is now allowed by Israel. In previous versions, channels 4 through 8 are supported. In Version

3.2, channels 1 through 13 are supported.

You can select the new channels when you create or modify a MAP or a radio. For example, you can select a channel when using the Create Distributed MAP wizard.

Part No. 735-9502-0016, Revision D Published June 2005

Page 2

2 WIRELESS LAN SWITCH MANAGER (3WXM) VERSION 3.2.5 RELEASE NOTES

SSID Support in Location Policies

MSS Version 3.2 enhances location polices by enabling you to set or change authorization attributes for a user after the user is authorized by AAA, based on the SSID the user is associated with. You can set or change the VLAN, inbound ACL (filter), or outbound ACL assigned to the user.

To configure a location policy, open the Modify WX Switch wizard for a WX switch, select the AAA page, and select Location Policy Rule. For configuration information, see the “Configuring Location Policies” section in the “Configuring Authentication, Authorization, and Accounting Parameters” chapter of the Wireless LAN Switch Manager Reference Manual.

Support for SNMP Trap Enhancements

MSS Version 3.2 has a new trap, and enhancements to another trap.

The new trap is ClientClearedTraps. MSS generates this trap when a client session is cleared. The enhanced trap is ClientAuthorizationSuccessTraps. In MSS Version 3.2, this trap includes the authentication type through which the user gained access to the network: dot1x, mac, web, or last-resort.

Information from these traps is displayed in the Monitor tab, in the Client Monitor window.

■ When an individual WX switch, MAP, or radio is

selected, the trap information is displayed in the Event Type column. Select an event to display its details in the Activity Details tab.

You must enable the Collect client connection & roaming traps option on the Monitoring Settings tab of the monitoring service, for information from the new and modified traps to appear in the Client Monitor window. In addition, the WX switches in the network plan must be in the list on the Monitored WXs tab and SNMP traps must be enabled on the switches. (For information, see the “Changing Monitoring Service Preferences” chapter of the Wireless LAN Switch Manager Reference Manual.)

Version Compatibility

This version of 3WXM has been verified against MSS Version 3.2.

Network plans created with 3WXM 3.0 are compatible with this version of 3WXM.

Supported Platform

Microsoft Windows Server 2003, Microsoft Windows XP with Service Pack 1 or higher, or Microsoft Windows 2000 with Service Pack 4.

■ When a Mobility Domain is selected in the Orga-

nizer panel, information from the ClientClearedTraps trap is displayed in the new Clears column of the Client Activity tab.

You must use the English version of the operating system. Operating system versions in other languages are not supported with 3WXM.

Page 3

Fixes for Known Faults in Version 3.2.3 3

Fixes for Known Faults in Version 3.2.3

Exception could occur while 3WXM was locating a rogue. (19108)

The fix for this issue includes a change to the interface. The rogue location panel is now separate from the rogue detection panel, so that rogue information is more clearly displayed. In addition, the floor view in the summary panel is no longer updated with the rogue location information.

Client Summary report for individual WX resulted in blank HTML page. (19468)

Exception occurred while 3WXM was generating a Rogue Detail report. (19634)

Listener data from directional antennas was not used for rogue detection. (19727)

Exception occurred when clicking on different users in client sessions. (19738)

Invalid activation keys were generated from some valid license keys, preventing 3WXM from working. (20636)

Fixes for Known Faults in Version 3.0

MAP model AP2750, if configured as a Distributed MAP, could not finish booting if the DHCP server took more than one second to send a DHCP Offer. (19048)

botched superblock messages were displayed during startup. (18564)

The display security acl hits command did not list any data when entered on a WX1200. (18473)

Memory fragmentation issue caused a system restart. (19046)

Changes to a custom WebAAA login page were not available until the switch was restarted. (18854)

Radio virtual base MAC addresses displayed instead of real base MAC addresses. (18709)

In MSS Version 3.x, the base MAC address displayed for a radio was the real address plus 2. For example, base MAC address 00:0b:0e:02:92:c0 was displayed as 00:0b:0e:02:92:c2. In MSS Version 3.2, the true base MAC address is shown. Note that a radio’s base MAC address is also used as the BSSID of the first SSID configured on the radio.

3WXM could not undo or redo object additions or deletions. (15910)

Page 4

4 WIRELESS LAN SWITCH MANAGER (3WXM) VERSION 3.2.5 RELEASE NOTES

Domain Policy manager did not correctly identify some changes, such as changes to the order of network access rules. (16383,16384,17692)

Extended character were not supported in CAD files. (17778)

When calculating MAP placement, selection of coverage vs capacity affected both areas in a shared area. (17982)

Upgrade from Beta version of 3.0 required a complete uninstall first. (18144)

Channel and power assignment used only default channel and power settings for third-party APs. (18346)

Image files were left over in nonvolatile storage when a switch was upgraded using 3WXM. (18349)

Accidentally enabling WPA on a clear SSID could result in a lost configuration. (18952, 19040)

Licensing

A licensed copy of 3WXM comes with a base license key, which is located inside the CD cover. To use 3WXM, you need to enter the base key and an activation key, which you obtain from 3Com. The base key and activation key enable you to manage up to 10 wireless LAN switches. To manage more than 10 wireless LAN switches, you also need an upgrade key

and

additional activation key

3Com.

If you are installing an evaluation copy, you still need to obtain an activation key from 3Com.

Each time you start 3WXM, it checks the license information. If the product is not licensed, the following dialog is displayed.

1 If you are installing a licensed copy, select Standard

Base Product and click Next. Go to step 2.

If you are installing an evaluation copy, select Time Limited Evaluation and click Next. Go to step 3.

, which you obtain from

Page 5

2 Type the license key that was supplied with the

3WXM CD, and click Next.

Licensing 5

4 Copy the activation key from the web page and

paste it into the Activation Key box of the Activation Key page.

5 If you plan to manage 10 or fewer wireless LAN

switches, click Finish. You are through with this pro- cedure.

If you are activating an evaluation copy, you can manage up to 10 wireless LAN switches. Click Finish to complete this procedure.

If you plan to manage more than 10 wireless LAN switches, click Next to display the following page and go to step 6.

3 Click Get Activation Key. A 3Com web page

appears. Enter your registration information (and the license key, if you are licensing a purchased copy) in order to obtain an activation key.

6 Type the upgrade license key in the License Key box

and click Next.

7 Click Get Activation Key to access the product acti-

vation key for your upgrade license. Register your upgrade license in order to obtain its activation key.

Page 6

6 WIRELESS LAN SWITCH MANAGER (3WXM) VERSION 3.2.5 RELEASE NOTES

8 Copy the activation key for the upgrade license

from the web page and paste it into the Activation Key box of the Activation Key page.

9 Click Finish.

Submitting Problem Reports

You can generate a problem report at any time by selecting Help > Report Problem in 3WXM.

To generate a problem report:

1 Do one of the following:

a In the Internal Application Error dialog box, click

Report Problem.

b Select Help > Report Problem.

The Report Problem to 3Com dialog box appears.

2 Fill out the information in the dialog box.

Provide your name, and enter as much detail as possible about the task you were performing when the problem occurred. You must provide the name of your company.

3 Click Save to store the problem report on the 3WXM

host.

The problem report is saved as a directory with a name containing the timestamp of the problem report (for example, Thu-Aug-19-13-04-11-PDT-2004). This directory is located in C:\Documents and Settings\user_home_directory\.3WXM\bugs, where user_home_directory is the home directory of the user that is running 3WXM at the time the problem report is generated.

Page 7

Known Problems 7

To send the problem report to 3Com Technical Support, create a zip archive of the problem report directory and send the archive as an attachment. For email information, see the “Obtaining Support for your Product” appendix in the Wireless LAN Switch Man- ager Reference Manual.

Known Problems

A non-administrative user cannot run 3WXM. (12155)

3WXM generates an exception if a user does not have administrative privileges on the 3WXM host. This issue involves the Java Virtual Machine (JVM) that is being used by 3WXM and should be resolved with a future release of JVM.

To use 3WXM, users must belong to a “Power Users” group or be added to the administrators group in the Windows operating system.

Default RADIUS parameters are not used for configuring a specific RADIUS server. (12301)

In the CLI, RADIUS parameters are implicitly inherited from the default set of RADIUS parameters. In 3WXM, a RADIUS server’s initial parameters are always set to the factory default, regardless of any changes made to the Default RADIUS Parameters Setup page.

and server groups for all the WX switches in the Mobility Domain.

Using the Undo feature in the Local & Network Changes dialog box does not restore a WX switch to its original Mobility Domain. (12676)

If you move a WX switch from one Mobility Domain to another, the WX switch is not moved back to the original Mobility Domain when you use the Undo feature.

Manually move the WX switch back to the original Mobility Domain.

When the VLAN name is composed entirely of numbers in ACL VLAN mappings imported from the CLI, 3WXM assumes that the VLAN name is a VLAN ID. (12682)

A VLAN can be specified in the CLI by its VLAN ID or its VLAN name. When the CLI command is imported into 3WXM, the VLAN reference type is not apparent. If the VLAN reference is composed entirely of numbers, 3WXM assumes that the reference is a VLAN ID. Otherwise, 3WXM assumes that the reference is a VLAN name.

Do not use VLAN names that consist entirely of numbers.

Set all RADIUS server parameters directly. You can use a domain policy to configure all the RADIUS servers

Page 8

8 WIRELESS LAN SWITCH MANAGER (3WXM) VERSION 3.2.5 RELEASE NOTES

Changes in the order of network or admin access rules are not displayed in Review Changes. (14191)

Network and admin access rules are organized in ordered lists. When changing the list order in 3WXM, the Review Changes dialog box does not show the new order of the access rules.

No workaround is required. This is a display anomaly in the Review Changes dialog box. Deployment and synchronization of ordered list changes are performed correctly.

Importing of a floor plan in JPEG format might fail with a color conversion exception. (14612)

On rare occasion, importing a floor plan in JPEG format might fail with the following Java exception:

sun.awt.image.ImageFormatException: Unsupported color conversion request.

This exception occurs because of unusual color palette settings in the file.

Using a JPEG editing tool, manually remove all extraneous information possible to remove the problematic color information. Alternatively, convert the JPEG file into a GIF file to import.

Size or location adjustments of shared coverage areas with identical dimensions might cause problems when you run Compute and Place. (14631)

top of the other. If you resize or move one of the coverage areas, the other coverage area is now a different shape or in a different location. Running Compute and Place might not work.

Use the dimension toolbar icon to set the center and size of each coverage area to identically match each other.

When importing a CAD file (DWG/DXF), any lines with arrowheads will display incorrectly. (15906)

When importing DXF or DWG CAD files with lines that have line ends (arrows, dots, and so on) the objects get imported with huge arrows at the ends of the lines.

Use a CAD program to remove any arrowheaded lines, or modify the line’s properties to not display an arrowhead. Alternatively, delete the line while in the Edit Content page of the Floor wizard in 3WXM.

3WXM incorrectly reports Mobility Domain configuration changes after deleting and re-uploading a WX switch. (16044)

If you delete a WX switch and re-upload the same switch, Review Local Changes erroneously reports that the seed and member switches need to be deployed. This may be confusing as the configuration to be deployed is identical to the current configuration.

When shared 802.11a and 802.11b/g coverage areas are created, one coverage area is directly placed on

No action is required. Deploy the indicated configurations to the WX switches.

Page 9

Known Problems 9

3WXM reports that changes have occurred even when the changes cancel each other out, but does not list the changes. (16212)

If you make a configuration change to a WX switch and then reverse the change before synchronizing 3WXM and the WX, 3WXM still reports that changes have occurred, but does not list any changes. For example, if you use the CLI to change the system description, then clear the change, the Local & Network Changes dialog shows Configuration changes in the Local Status field for the WX. However, no changes are listed when you select Review.

This issue is cosmetic and does not affect the configuration or operation of 3WXM or the switches.

3WXM does not support the Ctrl + drag-and-drop mouse operation. (16425)

Using characters that are not in the set of printable ASCII characters in the names or labels of image files in imported drawings could cause the files to become very large when saved, and could cause very slow performance of 3WXM. (17038, 18857)

If you have already imported a drawing that uses characters other than printable ASCII characters and you are experiencing either of these issues, contact 3Com Technical Support for assistance.

Polling interval for client session cannot be changed. (17585)

By default, 3WXM polls every 30 seconds for updates to information for clients on the watch list. In Version

3.2, this polling interval cannot be modified.

Enabling STP on an WX switch's management VLAN causes a configuration deployment to fail. (17668)

If you use 3WXM to enable STP on an WX switch's management VLAN, then deploy the configuration, the deploy fails. The failure occurs because the management interface must pass through the standard Listening and Learning states, which together take at least 30 seconds, before the interface can change to the Forwarding state. Until the interface reaches the Forwarding state, the switch cannot receive traffic, such as configuration deployment from 3WXM, on its management interface.

If this occurs, wait 30 seconds for the interface to reach the Forwarding state, then accept the WX switch's change in 3WXM.

Changing the unit of measurement of a drawing requires rescaling the drawing. (17941)

If you change the unit of measurement for a floor plan, 3WXM does not rescale the drawing accordingly. For example, if you change the unit of measurement from feet to meters, a 1-foot distance becomes a 1-meter distance.

If you change the unit of measurement, use the ruler icon to adjust the scale of the floor plan.

Page 10

10 WIRELESS LAN SWITCH MANAGER (3WXM) VERSION 3.2.5 RELEASE NOTES

Disabled radio on operational MAP does not turn red if the MAP or WX switch becomes unavailable. (18330)

In the Explore and Status Summary windows of the Monitor tab, the operational state of the equipment is indicated by color, and is also indicated in the Status column of the Status Summary window. For example, if a WX switch goes down, its icon turns red. However, if the MAP or WX switch for a disabled radio goes down, the radio does not turn red. In addition, the value in the Status column of the Status Summary window changes from Operational to Not Applicable. (It is normal for a disabled radio’s state to be Opera- tional, since disabled radios perform RF sweeps for rogue detection.)

This issue is cosmetic only and does not affect other information displayed for the equipment.

Daylight Savings Time or timezone changes are not automatically detected in 3WXM. (18422)

If a Daylight Savings Time or timezone change occurs on the host machine where 3WXM is running, displayed timestamps are not automatically updated in 3WXM.

This issue is actually a Java Virtual Machine (JVM) issue. The JVM does not detect date or time changes made at the OS level. See the following web page:

bugs.sun.com/bugdatabase/view_bug.do?bug_id=421 6582

Exit and restart 3WXM to place a date or time change made on the host machine that is running 3WXM into effect.

MAPs added to a coverage area do not immediately appear on the Objects to Place tab. (18680)

During planning, if you add MAPs to a coverage area, the MAPs appear in the upper left corner of the workspace, but they do not appear on the Objects to Place tab.

Click on the coverage area or select another wizard page, then reselect the Plan RF Coverage page. The MAPs appear on the Objects To Place tab.

List of Distributed MAP changes for verification does not include the complete form of one of the commands. (18695)

In the list of CLI commands 3WXM displays for review when you are planning to apply changes to a switch’s configuration, one of the commands for configuring a Distributed MAP, set dap num sticky-bit enable, is not displayed in its complete form. Instead, only set dap num is displayed.

This issue is cosmetic only and does not affect the configuration of the switch. The configuration on the switch contains the complete command and the command is not altered when you apply the configuration changes.

Page 11

Known Problems 11

Static IP routes created in a Domain Policy are not applied to WX switches. (18766)

If you create a static IP route in the Domain Policies for a Mobility Domain, and use the Policy Manager to apply the Domain Policies to an WX switch, the static route is not applied to the switch.

Configure the route on the individual switch.

Administrative names of MAPs can take a long time to be displayed in the RF Monitor window. (18838)

Default STP bridge priority for WX1200 is incorrect in 3WXM. (19711)

In MSS Version 3.2, the default STP bridge priority for the WX1200 is changed from 32768 to 49152. The default is correct in MSS. However, 3WXM still has the old default. This mismatch can result in the following issues:

■ If you deploy a configuration from 3WXM to the

WX1200, 3WXM changes the bridge priority back to 32768.

■ If you upload a WX1200 into 3WXM or synchro-

nize 3WXM with the network, the following verification error appears:

VLAN number and STP number do not match

To work around these issues, do the following:

■ Before deploying a configuration from 3WXM,

change the STP bridge priority for the switch in 3WXM to 49152.

■ After uploading a switch or synchronizing

changes, change the STP bridge priority in 3WXM to 49152.

3Com is a registered trademark of 3Com Corporation. The 3Com logo is a trademark of 3Com Corporation.

Mobility Domain, Mobility Point, Mobility Profile, Mobility System, Mobility System Software, MP, MSS, and SentrySweep are trademarks of Trapeze Networks, Inc.

Intel and Pentium are registered trademarks of Intel Corporation. Microsoft, MS-DOS, Windows, Windows XP, and Windows NT are registered trademarks of Microsoft Corporation.

All other company and product names may be trademarks of the respective companies with which they are associated.

Page 12

12 WIRELESS LAN SWITCH MANAGER (3WXM) VERSION 3.2.5 RELEASE NOTES