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 69
Summary
User Impact
Workaround
Read/write user allowed
read only access when
authentication method is
used as TACACS.
The user always gets Read-Only access if using
TACACS as a means for HTTP authentication,
even if the TACACS user is Read/Write capable.
User can configure the same TACACS user
locally and use LOCAL authentication method
for HTTP. The user will be able to get access
based on the local user access level (Read-write
or Read-only).
TFTP gives no reason for
file download failures.
Generic failure message is issued. Administrators can ping the TFTP server from
the switch. Administrators should ensure the
TFTP server is available, the requested file is
available, and the permissions are set correctly.
CLI command stack-port
config rejection does not
display the cause.
If a user enters an invalid interface, a generic
error message is issued.
Utilize the show stack-port command to
identify stack port configuration issues.
The 'acct-port' command
does not have 'no'
version.
The user can configure the acct-port to the
default using the positive form of the command
Configure the acct-port to the default using the
acct-port 1813 command in Radius accounting
mode.
Non-configuration file
getting loaded to startup-
config through HTTP.
Switch does not utilize invalid configuration file
information. Earlier versions of startup-config are
not available for fallback when overwritten with
an invalid startup-config.
In this case, an invalid configuration file was
downloaded (on purpose) via the web. When
the switch rebooted, it detected that the
configuration file was invalid and overwrote
the start-up config with the default
configuration (an empty configuration). Users
are advised to maintain off-line copies of
switch configurations.
A v6 ping with the v4
header destination address
set to 224.0.0.2 (all routers
addr) is not responded to.
Users are not able to ping over 6to4 tunnels using
IPv6 addresses.
Users can send pure IPv4 pings to the other end
of the tunnel.
Certain packets match
system rules that elevate
the priority for protocol
packets.
Packets may be transmitted out of order when
using priority flow control. Additionally, if the
queue that the packets are put on is not enabled
for lossless PFC, then the packets can be
transmitted even when the port was told to pause.
This may have an effect on connections that
expect packet order to be maintained, e.g. FCoE.
None.