3Com 4007 Release Note - page 28
28
C
HAPTER
3: R
ELEASE
I
SSUES
F
OR
M
ANAGEMENT
M
ODULES
Corrected Problems
in Release 3.0.0
This section describes problems that were corrected in EME software
Release 3.0.0.
■
The condition that caused the EME to excessively ARP from its
10BASE-T port when you inserted it into a multinetted subnetwork
has been corrected. (27009)
■
The EME no longer deletes the module’s BladeConfig.X.Y file from the
file system when you use the default filename with the
upload
command. (23456)
■
If you have two switch fabric modules in the chassis and one is not
functioning properly, you can use the
set power slot
disable
command to power off the switch fabric module that is not
functioning correctly instead of physically removing the module from
the chassis. (23135)
■
When you enter the
show module
command and the supported files field displays
none
, you no longer
have to reset the module. The supported file types appear after the
module comes up.
■
After you reset the chassis, and during the system start-up procedures,
the system may display the following message:
os socket err
. You
can ignore this message. The system continues the start-up
procedures as usual.
■
You no longer see an
os socket err
message while the EME is
processing multiple commands over a Telnet session and the time to
process the command has been reduced.
■
You no longer see an
os socket err
message after you reset the
chassis and during the system start-up procedures. (27650 and
29672)
■
The EME now recognizes all file types. In previous releases, if you were
going to hot swap a module, or download software to a module, the
EME sometimes did not recognize certain file types.
■
The EME deletes a software image from its file system after
successfully downloading software to a switching module from an
external file server.
■
Transcend
®
network management software now correctly interprets
SNMP trap information. (29657)
■
Bursty multicast or broadcast traffic no longer causes EME
performance problems. (24014 and 27383)