Dell Networking 7048 Release Note page 65

5.1.0.1 firmware release notes
Hide thumbs Also See for Networking 7048:
Table of Contents

Advertisement

PowerConnect 8132/8164/8132F/8164F/8024/8024F/M8024/M8024-k/
M6220/M6348/7024/7048/7024P/7048P/7024F/7048R/7048R-RA
Release Notes
Summary
User Impact
The stack will stop passing traffic if all switches
PC7048P, in a stack will
in the stack are rebooted simultaneously.
error out when all
rebooted at the same
time.
Jumbo frames cause
Transmit Errors is seen on port channel, but not
on the members of the port channel. Counters
transmit errors on port
remain inaccurate.
channel
PC8024F Stacking -
CLI/WebUI shows the stack-ports counters value
as zero after stack is formed.
CLI/WebUI : stack-ports
counters value is always
zero
CLI command "no snmp-
CLI command "no snmp-server community-
server community-
group" is not available.
group" doesn't work
Dot1x ias local
The internal database feature, which is a Dell
authentication method
specific feature, is not working correctly because
not working
this feature requires a user to authenticate using
MD5, which is not supported by Windows at this
time.
"ipv6 pim join-prune
CLI command ""ipv6 pim join-prune interval 30"
interval" command is not
does not change the default interval value from
working
60
Incorrect status being
When PowerConnect 8024F combo ports 21 and
reported with show
22 are used for stacking, the show interfaces
interfaces commands
status command and show interfaces media-type
commands report the status to be Detached and
Down.
Power supply
There is no impact to the user.
descriptions should be
modified as "Internal"
and "Remote" or
"External" for main and
secondary power
supplies respectively in
show system.
M8024-k Internal ports
Network operators may experience a single
are up during most of the
bounce during reboots of the M8024-k.
switch POST
M8024, M6220,
CSR may be rejected by Certificate Authority
M8024k, PC8024F -
Extra Lines and Tabs in
CSR Cause CA
Submittal Troubles
Sflow configurations do
The operator entered a sflow command that takes
not get saved to the
a timeout value which makes the sflow
config
configuration valid only for a fixed period of
time. As the configuration is temporary (bound
by the timeout value), it is not shown in running-
config. Storing the vale in the running
config/startup config would be an error as the
time period may have already expired.
System Firmware Version 5.1.0.1
Workaround
If this situation happens, it is recommended
that each power switch be rebooted in sequence
with a four to five minute interval between
each reboot.
None – Inaccurate transmit errors do not cause
functional issues.
None – Stack-Ports counter values as zero
doesn't affect the PC8024F stacking
functionality.
None
Use any other form of dot1x authentication.
None
None
None
None
Users can hand edit the CSR to left align all
rows and eliminate blank lines before
submission to the CA.
The configuration will show in the running
config if the command is used with the
"notimeout" option, e.g.
sflow 1 destination owner 1 notimeout
Page 63

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents