Dell Networking 7048 Release Note page 64

Summary User Impact
SNMP walk is not SNMP walk on the root port times out.
successful while doing
walk on root port.
FIP sessions are getting Users are unlikely to change either the default
disconnected for VLAN VLAN or the FIP VLAN while sessions are
switchport mode change active.
with default vlan
settings.
OpenManage displays After the browser session timeout (default 10
incorrect session timeout minutes), OpenManage displays incorrect session
duration when using timeout duration in the message "Your session
secure HTTP had been inactive for more than 240 minutes",
which is the actual setting for telnet and ssh.
However, the actual timeout occurs after the
default period of 10 minutes, so the GUI message
is incorrect.
Cannot disable the SFS Even with SFS allow-downgrade disabled, the
"allow-downgrade" master will still push the older firmware to a
feature stack member running a newer version of code.
Console port locks up Radius authenticated Telnet login attempt when
when awaiting telnet Radius daemon stopped, causes console port to
Radius response be temporarily blocked until Radius timeout
expires.
Flowcontrol is in inactive Flowcontrol gets automatically disabled and if
state when connected to the ports have a need for Flowcontrol, there will
Partner(Randall) with be no pause frames sent.
combo ports.
7048R replacement Although the power supplies part number is the
power supplies reported same, the 7048R reports it as incompatible and
as incompatible thus the error message is incorrect. The power
supplies still works correctly.
PowerConnect 7048P : After a long period of time and numerous IP
poe_lldp.c(1741) 23137 phones connected and with at least 5 switches
%% Failed to get pairs connected as a stack, PoE error messages start
control filling the logs.
SNMP showing packets SNMP monitoring tool is pulling stats from
discarded while cli M8024 and shows very high discard receive rate
doesn't show the same. but switch doesn't say the same.
PC M6220 Running When master member was removed from and
configuration altered reinserted into an M1000e enclosure, some of the
after removal of stacking configuration was missing from running-config.
master, 4.1.0.19, 4.1.1.7
Stacked m8024-k or Customers downgrading a switch stack to a
8024/8024F switches version of code that does not support stacking are
running code that advised to:
supports Ethernet 1) Break apart the stack into individual units
stacking should not be 2) Clearing the saved config on each unit
downgraded to older 3) Renumber each unit to unit 1 using the switch
code that doesn't support X renumber 1 command
Ethernet stacking.
62
Workaround
Do not do SNMP walks using root port.
Do not change the FIP VLAN while sessions
are established. The reason is that after a
VLAN is re-assigned or even changed to
general mode, the sessions will of course be
disrupted since the FIP snooping occurs on the
VLAN and any change in this will cause
problems on the Cisco Nexus side and will
require an interruption and reestablishment of
the addressing from the CNAs on up.
Disregard the time in this GUI message.
Always make sure the master has the wanted
version loaded.
Wait for timeout or ensure Radius server is
reachable.
Re-enable Flowcontrol on Randall switch.
Ignore the error message, since there are no
functional issues with this power supply.
Maximum supported IP phones at this time is
64.
None.
Always write the config before removing
master.
Failure to follow these instructions may cause
units to crash when booted into the 4.1
firmware. To recover the switch, attach a serial
cable and enter the boot menu (press 2 - Start
Boot Menu at the prompt). From the boot
menu, select 10 - Restore configuration to
factory defaults, and then select 1 - Start
operational code
System Firmware Version 5.1.0.1