Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, for Cisco NX-OS Release 5.0(2)N1(1) and NX-OS Release 5.0(2)N2(1) OL-22747-02, December 2010)

Send documentation comments to [e-mail]
23
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, for Cisco NX-OS Release 5.0(2)N1(1) and NX-OS Release 5.0(2)N2(1)
OL-22747-02
Caveats
Workaround: Change the running configuration to make the pause no-drop configuration for
class-fcoe same as the checkpointed configuration.
• CSCti87913
Symptom: A Cisco Nexus 5000 Series switch may not be able to login any servers after following
steps:
a. Performing an ISSU to the Cisco NX-OS 5.0(2)N1(1) release from a previous release with
feature fcoe configuration enabled.
b. Disabling feature fcoe and then re-enabling feature fcoe.
c. Copying all the feature fcoe configurations back.
Workaround: The recommended step after issuing the no feature fcoe command to reload the
switch. Subsequently feature fcoe can be re-enabled and configurations copied without facing this
issue.
• CSCti92741
Symptom: On a Cisco Nexus 5000 Series switch, show port-resources module x may display
incorrect information for Total bandwidth and Total shared bandwidth.
Workaround: None. It is a display issue with no impact on functionality.
• CSCti97003
Symptom: Rollback fails and output of show rollback log exec contains following:
...
...
--------------------------------------------------------------------------------
`config sync `
`no switch-profile ta1 all-config`
--------------------------------------------------------------------------------
time: Thu, 19:20:04 16 Sep 2010
Status: (null)
Verification successful...
Proceeding to delete switch-profile. This might take a while depending on amount of
configuration under a switch-profile.
Please avoid other configuration changes during this time.
Deletion of switch profile failed
...
...
Workaround: As a best configuration practice with switch-profile, if a policy-map is configured
inside switch-profile then it is referred only inside switch-profile. Similarly, if a policy map is
configured outside the switch-profile then it is not referred inside switch-profile.
• CSCti99872
Symptom: After ISSU, if an existing vsan is deleted and recreated, then the vfcs on that vsan goes
into to an error disabled state.
Workaround: Perform a shut/no shut of the vfc to help it recover.
• CSCtj05044
Symptom: On a Cisco Nexus 5000 Series switch, IGMP groups are not relearnt after VLAN
deletion and addition on a VLAN which is SPAN source. The VLAN has to be configured as a SPAN
source on a Cisco Nexus 5000 Series switch.
Workaround: Avoid using the VLAN as a SPAN source.
• CSCtj10460