3Com 4007 Release Note - page 48
48
C
HAPTER
5: R
ELEASE
I
SSUES
FOR
L
AYER
2 S
WITCHING
M
ODULES
Corrected Problems
in Release 3.0.0
This section describes problems that relate to Layer 2 Switching Modules
and that were corrected in software Release 3.0.0.
System
■
The system no longer displays
os socket err
after you reset the
chassis and during the system start-up procedures. (27650 and
29672)
■
The 36-port 10/100BASE-TX Layer 2 modules (Model Numbers
3CB9LF36R and 3CB9LF36T) no longer experience port lockup due to
high port errors. (28668)
Management
■
Uploading a configuration file that already exists on the EME to a TFTP
server no longer removes the file from the EME file system, as shown
in the
show file
display. (23456)
Ethernet
■
The 36-port 10/100BASE-TX Layer 2 Fast Ethernet RJ-45 module
(Model Number 3CB9LF36R) no longer asserts because of port duplex
mode mismatch and TX underrun errors. (27365, 27362, and 29195)
■
Current autonegotiation status is now correctly reflected the first time
that you view the Ethernet summary and detail displays. (27864)
■
Whenever a non-switch fabric module is reset (with the
module nvData reset
command, by inserting the module into a
chassis, by doing a warm reset, by running service diagnostics, and so
forth) or a backplane port is disabled and then reenabled, the links to
the switch fabric module no longer go down on some occasions and
are now always reestablished. (30063)
Bridging
■
You can now list the bridge port address table and walk through MIBs
without causing Trunk Control Message Protocol (TCMP)-enabled
trunk ports to go down, or causing Spanning Tree Protocol (STP)
topology changes. (23076 and 24547)
■
When a port enters the Spanning Tree forwarding state, the root
bridge no longer erroneously sends a new root trap instead of a
topology change trap. (28665)
■
Enabling the Spanning Tree Protocol (STP) on a port that already had
STP enabled no longer results in an erroneous Spanning Tree topology
change trap. (28655)