Dell POWERCONNECT 5524P Release-opmerkingen - Pagina 10

Blader online of download pdf Release-opmerkingen voor {categorie_naam} Dell POWERCONNECT 5524P. Dell POWERCONNECT 5524P 15 pagina's. Powerconnect 5500 series
Ook voor Dell POWERCONNECT 5524P: Aan de slag handleiding (20 pagina's)

Dell POWERCONNECT 5524P Release-opmerkingen

GUI problem in VLAN pages

Voice VLAN and LAGs

vulnerabilities and DoS attacks
reported on SSH service
The following is a list of issues resolved between 4.1.0.05 and 4.1.0.08 firmware release.
Description
PowerConnect 55xxP having
problem providing power when using
Shortel IP230G phones (PSE/PTR
issue - 213880)
PC55xx - speed not listed for 10Gb
ports in Web GUI unless page was
refreshed.
PC55XX MIB OIDs for optical
transceivers conversion from bBm to
mWatt is mistaken
Routed traffic in the device is using
the port MAC as the SMAC instead
of the device MAC
Web GUI displays tagged VLANs as
Inactive configuration
System Firmware Version 4.1.0.16
PowerConnect 5500 Series Release Notes
"apply" and "cancel" button disappear from VLAN
port setting edit page if interface includes
command to remove certain VLANs
Device crashes when Adding Voice VLAN
enabled ports to a LAG
Reports of SSH vulnerabilities on device
User Impact
The Shortel IP230G phones don't work.
Issue was related to phone
requesting/consuming power beyond the limit
of the class it was advertising
In Web GUI the current speed of the 10Gb
ports is not presented
Wrong mWatt values are displayed in CLI and
Web GUI
In some rare cases this behavior would affect
the ability of end stations to use the switch
interface as a default gateway.
Wrong configuration is being shown to the
user. CLI displays accurate information.
Subject to Change Without Notice
Issue resolved
Issue resolved
Upgrade to OpenSSH
version 5.9
Resolution
Additional global option was
added to allow switch to
provide power up to the
max limit of 15.4W
regardless of device POE
class.
Issue resolved
Issue resolved
Issue resolved. Device
base MAC is always used
as SMAC when routing
traffic
Issue resolved
Page 7