PowerConnect 8024/8024F Release Notes
Page 6 System Firmware Version 3.1.4.16
Issues Resolved
Release 3.1.4.16
Description User Impact Resolution
In simple mode STP BPDU will pass
through from one port-aggregator to
the other port-aggregator
Switches receiving unwanted STP
BPDUs may shut the port down.
BPDU flooding set to disabled in
simple mode by default.
Switch is crashing when it is
connected to a CDP enabled CISCO
6509
The CISCO 6509 sends CDP PDUs
that are larger than expected which
can occasionally result in a switch
reboot.
Updated the local buffer to be
tolerant of larger packet sizes.
Interface metric not working on OSPF
When an OSPF interface is
configured as Passive, 8024F
advertises the interface metric (cost)
as 0, irrespective of cost configured.
Corrected to generate the proper
interface cost.
Displaying the wrong LACP system
MAC address in "show lacp port-
channel".
The incorrect MAC address was
shown for the partner switch in "show
lacp port-channel" CLI command
output.
Corrected to retrieve the proper
MAC address.
SNMP Agent becoming unresponsive. The switch will stop responding to
SNMP requests.
A semaphore now used to properly
control SNMP and CLI access to
common configuration data
structures.
TX DMA will timeout and cause the
switch to reboot.
The stack crashes with a crash dump
from the workQAdd2 task.
Corrected a heap memory
fragmentation problem when
processing DMA transactions.
H323 VoIP traffic crashes the switch
VoIP task processing was not allowing
other tasks to run causing a stalled
task to reboot the switch.
VoIP packets are not sent to the
switch CPU if the auto-VoIP feature
is administratively disabled.
LACP not working with Juniper EX-
4200 when supporting Non-Stop
Forwarding
The LAG will not establish because all
the LACP data units are dropped.
Dropped LACP data units were
caused by an incorrect packet
length. The packet length of 132
was changed to 128 in order to
conform to the standard.
Invalid SNMP query result on walking
ipAdEntNetMask.
Secondary Netmask configuration is
not displayed for an interface IP
Address, and the Netmask of the
primary IP Address is shown instead.
Changed the implementation of
ipmIpAdEntNetMaskGet to also take
the address parameter and look up
the specific Netmask.