
PowerConnect 5500 Series Release Notes
System Firmware Version 4.1.0.16 Subject to Change Without Notice Page 12
The following is a list of issues resolved between 4.0.1.0 and 4.0.1.11 firmware release.
Description User Impact Resolution
EEE advertisement when EEE is
disabled
When EEE is disabled, the Auto-
negotiation advertises EEE capability of
the port. In case the link partner is EEE
enabled, but does not fully comply to
EEE standard, the auto-negotiation
process might fail causing the link to be
down.
When EEE is disabled, the auto-
negotiation process does not
advertise EEE capability.
Note that changing EEE state
(globally or on individual
interface) will cause link to toggle,
since auto negotiation
advertisement is being changed.
Devices stop to learn MAC
addresses after 49.7 days
After 49.7 days of operation, the device
stops re-learning MAC addresses. These
MACs which were previously learned will
not appear in MAC address table. As a
result traffic streams sent to previously
learned MAC addresses are treated as
unknown-unicast traffic and flooded
within the VLAN.
MAC address learning
mechanism was fixed so that
both learning new addresses and
re-learning existing addresses
are updating the MAC Address
database.
Slave unit up time wraps after
49.7 days
Slave unit sysUpTime (which can be
displayed in show system command in
CLI) wraps up after 49.7 days instead of
wrapping up after 497.1 days. As a
result, after operating for 49.7 days,
slave units (including backup master) will
begin re-counting sysUpTime from 0. No
actual reboot occurred
sysUpTime on slave unit is
calculated correctly and will wrap
up only after 497.1 days.
Fatal Error Loop - PC55xx
stacking issues
If 2 devices (when at least one of them
is a 24 port unit) with sequential MAC
are placed in the same stack – the stack
enters an endless reboot sequence and
does not converge
MAC addresses assignments for
device ports are calculated based
on absolute port number and not
on internal number.
The following issues have been resolved in firmware 4.0.1.0 release
Description User Impact Resolution
802.1X when spanning tree is
enabled
When spanning-tree is enabled on a
port, and portfast is disabled, the dot1x
authentication does not take place after
initial reload. This happens only with
Windows Vista workstations.
In the implementation of 802.1x,
software timers were modified to
better support Windows Vista
workstations.
POE LED might stay ON after
Overload
When connected POE devices overload
the ports, the amber POE LED is lit as
expected. In some cases, after the
overload condition is removed, the
amber POE LED on ports will stay lit until
a short polling cycle is complete. This is
a cosmetic issue, even when the amber
POE LED is lit, the device operates
correctly (e.g. the output of the CLI
command "show power inline
consumption" displays the actual
The POE LED status is cleared
after overload issue is resolved.
End of Release Notes