Issues Resolved; Molex Break-Out Cable: E357317-S (Ul) Type Cl2 Ft4 30 Awg, Is Not Supported And Cause Port Flapping; Some Interfaces Of A Lag Across The Stack Do Not Update The Lag Counters; Dhcp Server Fatal Error Crash - Dell PowerConnect 5524 Release Notes
Hide thumbs
Also See for PowerConnect 5524:
- Getting started manual (20 pages) ,
- User manual (728 pages) ,
- System user's manual (738 pages)
Table of Contents
Advertisement
Issues Resolved
The following issues have been resolved in current firmware release (Version 4.1.0.16)
Description
Added support for 40G Molex
break-out cable
Some interfaces of a LAG across
the stack do not update the LAG
counters
DHCP Server Fatal Error crash
Device reboots with Fatal Error
with message
"SW3C_pcl_fft_entry_chk: illegal
function input – vpt"
LAG with XG type present speed
of 1,000 Mbps in GUI
Device does not present itself in
the SSH server as support SSH-
2.0-OpenSSH_5.9p1.RL
Copy image from stack unit to
master causes a system crash
Show LLDP neighbors per
interface cause crash
System Firmware Version 4.1.0.16
PowerConnect 5500 Series Release Notes
User Impact
When using the mentioned cable, ports is
flapping and traffic cannot be forwarded
Actual traffic is being forwarded, but counters
of some interfaces of LAG across the stack are
not updated.
When device function as DHCP server and
configuring the address pool (moving the
dynamic range, all connected hosts are
provided with static leases). After a while
device crash.
In some cases sending traffic denied by the
with the following
ACEs may cause reboot
message: SW3C_pcl_fft_entry_chk: illegal
function input - vpt id 8
User impact is cosmetic.
CLI output is presented as expected and traffic
across the stack runs as expected.
Device support SSH-2.0-OpenSSH_5.9p1.RL
but advertise itself as support old version:
SSH-2.0-OpenSSH_3.4p1.RL
When attempting to copy from a stack member
to the backup image on the master switch, the
stack will crash with a fatal error
Switch# copy unit://2/image image
When device receive LLDP packet with vendor
specific VLAN ID 0, it cause the device to
crash when presenting the show LLDP
neighbors per interface
Subject to Change Without Notice
Resolution
Issue resolved by adding
support
Issue resolved
Issue resolved
Issue resolved
Issue resolved
Issue resolved
Issue resolved - option is
not supported and has been
removed from CLI
command
Issue resolved
Page 3
Advertisement
Table of Contents
