Cisco Nexus 5000 Series Release Notes for Release 5.0(3)N2(2) (June 2011)

Send documentation comments to [e-mail]
12
Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Release Notes, for Cisco NX-OS Release 5.0(3)N2(2) and Release 5.0(3)N2(1)
Limitations
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 might occur. We recommend 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 that breaks the STP active path. To work around this issue, move all STP
roots on the MST region. However, the work around causes a nondisruptive ISSU to fail because
Non-Edge Designated Forwarding Ports are required for an ISSU. For additional information, see
CSCtf51577. For information topologies that a nondisruptive upgrade is supported, see to the Cisco
Nexus 5000 Series NX-OS Upgrade and Downgrade Guide.
• IGMP queries sent in CSCtf94558 are group-specific queries that are sent with the destination
IP/MAC address as the group's address.
GS queries are sent for IP address: 224.1.14.1 to 224.1.14.100 [0100.5E01.0E01 to
0100.5E01.0E64]
These are not link-local addresses. By default, they are not flooded by the hardware into the VLAN.
They are sent only to the ports that have joined this group.
This is expected behavior during an ISSU.
In another scenario, the IGMP global queries [dest IP 224.0.0.1] get flooded correctly in the VLAN.
Group-specific queries are not forwarded to ports other than the one that joined the group during
ISSU. The reason to forward group-specific queries toward hosts is to avoid having them leave the
group. However, if a group has not joined the group, then this is not an issue. If there is an interface
that has joined the group, then the queries are expected to make it to the host. While the behavior is
different when ISSU is not occurring, it is sufficient and works as expected and there is no impact
to traffic. For details, see CSCtf94558.
• The meaning of an MTU configuration has changed in Cisco NX-OS Release 4.2(1)N1(1) and
earlier releases. In releases earlier than Cisco NX-OS Release 4.2(1)N1(1), the configured MTU
included the Ethernet payload and Ethernet headers. In Cisco NX-OS Release 4.2(1)N1(1), the
configured MTU includes only the Ethernet payload and not the Ethernet headers. When upgrading
or downgrading between Cisco NX-OS Release 4.2(1)N1(1) and earlier releases, Cisco NX-OS
automatically converts the configuration to address this semantic change by adding or subtracting
38 to the MTU to address the Ethernet header size.