Release Notes

64 System Firmware Version 5.1.1.7
Summary
User Impact
Workaround
OOB static IP entry
cannot be the same as the
DHCP assigned IP
address
After receiving an IP address from the DHCP
server, the switch gives an error and will not
allow an attempt to add a static IP address and
gateway that is the same as the DHCP IP address.
Use a different IP address than the DHCP
address given.
Release 4.2.2.3
Summary
User Impact
Workaround
Stack member units port
display is missing in
web GUI.
Wrong id for the power LED is displayed.
None
WebUI sFlow Polling
page issues.
sFlow>Sampler configuration and sFlow>Poll
Configuration don't work for ports Gig1/0/1 -
1/0/9.
None
Release 4.2.1.3
Summary User Impact Workaround
"show interfaces
switchport " command
shows incorrect General
Mode Tagged VLANs
value
Some general mode VLANs tagged to the
interface may not be displayed using this
command.
Use “show vlan” command to interfaces. No
other workaround.
M6220 OOB interface
unreachable after
failover
On a failover on a M6220 stack the OOB
interface may not be available.
Recovers when the master is restored.
CLI command "show ip
dhcp snooping binding"
not displaying client
information.
"show ip dhcp snooping binding" not displaying
client information. "show ip dhcp snooping
statistics" does not display correct message
counts.
None
OOB interface
configured with default
IP via Setup Wizard
though told not to do so.
The setup wizard does not honor selection to not
setup OOB IP address.
OOB IP address will need to be setup
manually.
DHCPv6 - M6220,
PC/M 8024/k - Client
Solicits do Not Seem to
Make it to the Server /
Relay
By looking at the counters, the client believes it
is sending solicits; but, the relay and the server
never see the solicitations.
None
Release 4.2.0.4
Summary User Impact Workaround
File modification date &
time is not getting
updated with current
time & date.
When internal files are modified, they do not get
the current time stamp.
None
SNMP walk is not
successful while doing
walk on root port.
SNMP walk on the root port times out.
Do not do SNMP walks using root port.
FIP sessions are getting
disconnected for VLAN
switchport mode change
with default vlan
settings.
Users are unlikely to change either the default
VLAN or the FIP VLAN while sessions are
active.
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.