Release Notes

PowerConnect 8132/8164/8132F/8164F/8024/8024F/M8024/M8024-k/
M6220/M6348/7024/7048/7024P/7048P/7024F/7048R/7048R-RA
Release Notes
System Firmware Version 5.1.1.7 Page 75
When multiple partitions are present on
the flash drive, only the first partition is
accessible.
Minimal – users will typically re-partition flash drives to maximize space.
Web
Description
User Impact
Certain browser (IE) versions respond
slowly when displaying large lists of
information. In these cases, the “All”
display selection may not appear (is
disabled).
This behavior is a browser performance limitation. Users may select another
supported browser to enable “all” display functionality. Alternatively, the user
may utilize the page selector functions to display the appropriate page of
information.
Certain browser (FireFox) versions
automatically block popups after a
certain number of displays within a
session.
This behavior is a browser functionality issue. If popups are blocked, the web
interface will display errors/information using alerts. Users can disable popup
monitoring by browsing to about:config and set dom.popup_maximum to -1
File Management
Description
User Impact
CLI Comment Character
The '!' indicates the beginning of a comment. All characters following the '!' will
be treated as a comment (except when configuring a banner where the ! is
accepted at the beginning of a line)
Data Center – 4.2.0.4
Interoperability
Description
User Impact
VLAN request/Notification counters are
not incremented for priority tagged
packets
Low – FIP sessions are established and are displayed in the show commands.
FIP snooping VLAN request or VLAN response counters do not increment when
CNA sends priority tagged frames (i.e. VID 0). It is observed that certain CNAs
sometimes sends FIP VLAN discovery frames as 802.1Q tagged frames with
VID=0 and priority as FCoE priority. FSB snoops FIP packets which are
classified to any of FCoE enabled VLANs. In this case, the default VLAN (1) and
the configured FCoE VLAN. In general, VLAN request messages are exchanged
as untagged so gets associated with VLAN 1. In this case, the BROADCOM CNA
sends priority tagged FIP frames (VID=0) which do not match the FSB snooping
criteria because they do not get associated to any of the FCoE enabled VLANs
hence FCoE VLAN R
equest/Notification counters are not incremented for priority
tagged packets. These control frames are however are forwarded to FCF by FSB
in order to establish a successful session. FIP snooping bridge need to consider
forwarding priority tagged FIP frames to FCF as well in order to interoperate with
CNAs which could send priority tagged packets. The current FSB implementation
does this already.
Broadcom CNA only supports
configuration of VLAN via VLAN
Discovery process
Low – Most users prefer automatic setup of CNAs
The Broadcom CNA does not support manual configuration of VLAN. This
means that customers who prefer to set up their FCoE network manually will not
be able to do so if using BRCM CNAs.
FIP snooping bridge does not forward
the DCBX FIP tlv info from
configuration source
Low – No supported FCF supports this configuration option.
While working with QLogic, it is found that CNA sends two TLVs concerning the
FIP/FCoE traffic. It sends FIP TLV along with FCoE TLV with respective
priorities - in this case same priority for both. Although, it is not a normal use case
but can be used to have different treatment for control and data traffic. There can
be a use case where host or FCF can choose to create different priorities for