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]
13
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
Limitations
Mod Sw Hw World-Wide-Name(s) (WWN)
--- -------------- ------ --------------------------------------------------
1 5.0(2)N1(1) 1.0 --
2 5.0(2)N1(1) 1.0 20:41:00:05:9b:23:40:c0 to 20:48:00:05:9b:23:40:c0
Mod MAC-Address(es) Serial-Num
--- -------------------------------------- ----------
1 0005.9b23.40d0 to 0005.9b23.40ef JAF1421DKRS
2 badb.414b.4245 to badb.414b.4254 JAF1432AKBE
For details, see the expansion modules section of the Cisco Nexus 5000 Series and Cisco Nexus 5500
Platform Hardware Installation Guide.
Limitations
This section describes the limitations for Cisco NX-OS Release 5.0(2)N1(1) and Cisco NX-OS
Release 5.0(2)N2(1).
• When upgrading from Cisco NX-OS Release 4.2(1)N1(1) and earlier releases, to any release, the
policy description is lost. This problem does not occur when upgrading from Cisco NX-OS
Release 4.2(1)N1(1) and later releases. After an upgrade, Cisco recommends that you reconfigure
the policy description. For details, see CSCth14225.
• Starting with Cisco NX-OS Release 4.2(1)N2(1), LACP fast timers are supported. If you downgrade
to an earlier release that does not support this feature, issuing the install all command displays the
following warning:
"Configuration not supported - Lacp fast rate is enabled",
"Use \"lacp rate normal\" on those interfaces"
Before downgrading to an earlier release, change the LACP rate to normal. If you ignore the warning
and force the installation, then it is possible that the leftover LACP rate fast configuration would
still be active with previous releases of software but the behavior would be unpredictable and link
flap may occur. It is recommended that you change the LACP rate setting to normal. For details, see
CSCth93787.
• When an FC SPAN destination port is changed from SD to F mode and back to SD mode on a NPV
switch, the port goes into an error-disabled state. Perform a shut/no-shut after the mode change
recovers the port. This issue occurs only in NPV mode. For details, see CSCtf87701.
• If you configure a Cisco Nexus 2248TP port to 100 Mbps instead of autonegotiation, autonegotiation
does not occur, which is expected behavior. Both sides of the link should be configured to both
hardwired speed or both autonegotiate.
no speed—Autonegotiates and advertises all speeds (only full duplex)
speed 1000—Autonegotiates only for a 802.3x pause
speed 100—Does not autonegotiate; pause cannot be advertised. The peer must be set to not
autonegotiate and fix at 100 Mbps (similar to the N2248TP)
For details, see CSCte81998.
• Given the implementation of a single CPU ISSU, the STP root on the PVST region with switches on
an MST region is not supported. The PVST simulation on the boundary ports go into a PVST SIM
inconsistent blocked state which breaks the STP active path. To workaround this issue, move all STP
roots on the MST region. However, the workaround causes a nondisruptive ISSU to fail because