4
W
IRELESS
LAN S
WITCH
M
ANAGER
(3WXM) V
ERSION
3.0 R
ELEASE
N
OTES
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 Set-
tings\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.
To send the problem report to 3Com Technical Sup-
port, create a zip archive of the problem report direc-
tory 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.
Set all RADIUS server parameters directly. You can use
a domain policy to configure all the RADIUS servers
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 fea-
ture.
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 num-