34
C
HAPTER
3: R
ELEASE
I
SSUES
Known Problems
This section describes problems that are known to exist in Layer 2
switching module operational software Release 3.0.
The numbers that appear in parentheses at the end of some descriptions
are for internal 3Com use only.
System
■
At the Administration Console, entering a seemingly valid command
string (two or more commands taken from menus and nested
submenus) may not work. If this situation occurs, enter commands
separately from one menu prompt at a time.
■
Some Release 3.0.x features may become unstable when the
associated switch devices are polled by Enterprise VLAN Manager,
Address Tracker, and other Transcend applications that poll the bridge
address MIB tables. These features and protocols include Trunk
Control Message Protocol (TCMP) and Spanning Tree Protocol (STP)
topology changes.
3Com recommends that you use these Transcend management
applications only for configuration and problem isolation purposes.
When you use these applications, SNMP polling can contribute to
unexpected events in the configuration associated with TCMP and
STP. (29371 and 29797)
For information about controlling the Transcend Enterprise VLAN
Manager and Address Tracker management applications, see the
“General Functional Limitations” section, problem NMDww04250, in the
Transcend Network Control Services Readme files for the February 2000
Update.
Management
■
When you are prompted to “wait” for a reset to take place, do not
attempt to start a new connection during this delay. Wait until control
returns you to the Administration Console prompt before you start a
new connection.
■
After you enter an
nvdata reset
command (or initiate a trunk group
definition or deletion), there is a delay before the module resets.The
following MIB-II counters do not increment:
■
inReceives
■
tcpOutRsts
■
udpOutDatagrams
■
udpNoPorts