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]
27
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: Configure the egress points of Fibre channel traffic as SPAN sources on the Cisco
Nexus 5548 switch.
• CSCth69160
Symptom: The SVI on secondary VLAN does not work.
Workaround: Assign SVI to non Private VLANs
• CSCti11823
Symptom: The Cisco NX-OS version 4.2(1)N1() supports only 10 Gigabit Ethernet on the Nexus
2232 host ports. If the administrator plugs in 1Gig SFPs on Nexus 2232 host ports with Cisco
NX-OS 4.2(1)N1(1) running, the SFP validation fails, the LED blinks amber and the interface shows
LinkNotConnected. The administrator performs an ISSU from Cisco NX-OS 4.2(1)N1(1) to Cisco
NX-OS 4.2(1)N2(1) and the Cisco NX-OS 4.2(1)N2(1) version supports Gigabit Ethernet on Cisco
Nexus 2232 host ports. After ISSU, if the administrator configures speed 1000 on the interface with
Gigabit Ethernet SFP plugged in, the Gigabit Ethernet interface comes up (traffic flows) but the
Gigabit Ethernet port LED continues to blink amber. The LED should be green after and ISSU to
the Cisco NX-OS version 4.2(1)N2(1) and configuration of speed 1000.
Workaround:Unplug and re-plug SFP and the LED turns green.
• CSCtc62994
Symptom: With combining RBAC roles (multiple roles assigned to the same user account),
interface policies in those roles do not work on per role basis. In the example shown in this bug, user
lan-admin is assigned to the following 3 roles: LAN-admin, LAN-admin-ETH and LAN-admin-no.
Roles LAN-admin and LAN-admin-no include eth1/1 in their interface policy permit list and both
deny the shutdown command under their permitted interfaces.
Roles LAN-admin-ETH excludes eth1/1 from its interface policy permit-list and permits the
shutdown command under its permitted interfaces.
When all 3 roles are assigned to the user, lan-admin, the user should not be allowed to shutdown
interface eth1/1 but it currently can.
Workaround: Do not configure multiple roles for the same user account
• CSCtd31131
Symptom: If you change PVLAN configuration as follows very rapidly (less than 5 seconds
between any two commands), then the interface may end up in an err-disabled state.
DUT2(config-vlan)# vlan 421
DUT2(config-vlan)# private-vlan community
DUT2(config-vlan)# private-vlan isolated
DUT2(config-vlan)# private-vlan community
DUT2(config-vlan)# private-vlan isolated
Workaround: Shut the interface, followed by no shut if the interface recovers properly.
• CSCtf32340
Symptom: When you change the VSAN or Interface Scope of an existing Role via DM, a This entry
already exists error dialog is shown and the change is not applied
Workaround: Use the CLI to make the scope changes for the existing role.
• CSCtf79253