Table of Contents

n3k_rel_notes_503_u5_1b.fm

Cisco Nexus 3000 Series NX-OS Release Notes, Release 5.0(3)U5(1b)

Release Date: January 18, 2013

Current Release: Cisco NX-OS Release 5.0(3)U5(1b)

This document describes the features, caveats, and limitations for Cisco Nexus 3000 Series switches. Use this document in combination with documents listed in the “Obtaining Documentation and Submitting a Service Request” section.

Note Table 1-1 shows the online change history for this document.

Table 1-1 Online History Change

Part Number

Revision

Date

Description

OL-28183-03

A0

January 18, 2013

Created NX-OS Release 5.0(3)U5(1b) release notes.

B0

February 20, 2013

Updated support information for the Cisco Nexus 3064-TQ switch.

C0

September 18, 2013

Updated resolved caveat CSCuh79034.

Contents

This document includes the following sections:

- Introduction

- System Requirements

- New and Changed Features

- Upgrade Guidelines

- Limitations

- Caveats

- Obtaining Documentation and Submitting a Service Request

Introduction

The Cisco NX-OS software is a data center-class operating system built with modularity, resiliency, and serviceability at its foundation. Cisco NX-OS helps ensure continuous availability and sets the standard for mission-critical data center environments. The highly modular design of Cisco NX-OS makes zero-effect operations a reality and enables exceptional operational flexibility. Cisco NX-OS software offers the following benefits:

- Cisco NX-OS runs on all Cisco data center switch platforms: Cisco Nexus 7000, Nexus 5000, Nexus 4000, Nexus 3000, Nexus 2000, and Nexus 1000V Series switches.

- Cisco NX-OS software interoperates with Cisco products running any variant of Cisco IOS software and also with any networking operating system that conforms to common networking standards.

- Cisco NX-OS modular processes are triggered on demand, each in a separate protected memory space. Processes are started and system resources are allocated only when a feature is enabled. The modular processes are governed by a real-time preemptive scheduler that helps ensure timely processing of critical functions.

- Cisco NX-OS provides a programmatic XML interface based on the NETCONF industry standard. The Cisco NX-OS XML interface provides a consistent API for devices. Cisco NX-OS also provides support for Simple Network Management Protocol (SNMP) Versions 1, 2, and 3 MIBs.

- Cisco NX-OS enables administrators to limit access to switch operations by assigning roles to users. Administrators can customize access and restrict it to the users who require it.

Cisco Nexus 3000 Series Switches

The Cisco Nexus 3000 Series switches are high-performance, high-density, ultra-low-latency Ethernet switches that provide line-rate Layer 2 and Layer 3 switching. The Cisco Nexus 3000 Series includes the following switches:

- The Cisco Nexus 3064 switch is a 1 RU switch that supports 48 1- or 10-Gigabit downlink ports, four QSFP+ ports that can be used as a 40 Gigabit Ethernet port or 4 x10-Gigabit Ethernet ports, one 10/100/1000 management port, and one console port.

- The Cisco Nexus 3048 switch is a 1 rack unit (RU) switch that supports 48 10/100/1000 Ethernet server-facing (downlink) ports, four 10-Gigabit network-facing (uplink) ports, one100/1000 management port, and one console port.

- The Cisco Nexus 3016 is a 1 RU, 16-port QSFP+ switch. Each QSFP+ port can be used as a 40-Gigabit Ethernet port or 4 x10-Gigabit Ethernet ports.

Each switch includes one or two power supply units and one fan tray module, and each switch can be ordered with either forward (port-side exhaust) airflow or reverse (port-side intake) airflow for cooling. All platforms support both AC and DC power-supplies. All combinations of power (AC/DC) and airflow (forward/reverse) are available. The Cisco Nexus 3000 Series switches run the industry-leading Cisco NX-OS Software operating system.

System Requirements

This section includes the following topics:

- Memory Requirements

- Hardware Supported

- Twinax Cable Support on Cisco Nexus 3000 Switches

Memory Requirements

The Cisco NX-OS Release 5.0(3)U5(1b) software requires 135MB of flash memory.

Hardware Supported

.

shows the hardware supported by Cisco NX-OS Release 5.0(3) software.

shows the transceivers supported by Cisco NX-OS Release 5.0(3) software.

Table 1-2 Hardware Supported by Cisco NX-OS Release 5.0(3)Software

Supported Cisco NX-OS Release

Hardware

Part Number

5.0(3)U5(1b)

5.0(3)U5(1a)

5.0(3)U5(1)

5.0(3)U4(1)

5.0(3)U3(2b)

5.0(3)U3(2a)

5.0(3)U3(2)

5.0(3)U3(1)

5.0(3)U2(2d)

5.0(3)U2(2c)

5.0(3)U2(2b)

5.0(3)U2(2a)

5.0(3)U2(2)

5.0(3)U2(1)

5.0(3)U1(2a)

5.0(3)U1(2)

5.0(3)U1(1d)

Cisco Nexus 3000 Series

Cisco Nexus 3016 switch

N3K-C3016Q-40GE

X

X

X

X

X

—

—

Cisco Nexus 3048 switch

N3K-C3048TP-1GE

X

X

X

X

—

—

—

Cisco Nexus 3064-TQ switch

N3K-C3064TQ-10GT

X1

—

—

—

—

—

—

Cisco Nexus 3064-X switch

N3K-C3064PQ-10GX

X

X

X

—

—

—

—

Cisco Nexus 3064-E switch

N3K-C3064PQ-10GE

X

X

X

X

X

X

—

Cisco Nexus 3064 switch

N3K-C3064PQ

X

X

X

X

X

X

X

Cisco Nexus 3048 fan module, Forward airflow (port-side exhaust)

N3K-C3048-FAN

X

X

X

X

—

—

—

Cisco Nexus 3048 fan module, Reverse airflow (port-side intake)

N3K-C3048-FAN-B

X

X

X

X

—

—

—

Nexus 3064-T 500W forward airflow (port side exhaust) AC power supply

NXA-PAC-500W

X

X

—

—

—

—

—

Nexus 3064-T 500W reverse airflow (port side intake) AC power supply

NXA-PAC-500W-B

X

X

—

—

—

—

—

Nexus 3064-T 400W forward airflow (port side exhaust) DC power supply

N2200-PDC-400W

X

X

—

—

—

—

—

Nexus 3064-T 350W reverse airflow (port side intake) DC power supply

N3K-PDC-350W-B

X

X

—

—

—

—

—

Cisco Nexus 3064-X forward airflow (port-side exhaust), AC power supply

N3K-C3064-X-FA-L3

X

X

X

—

—

—

—

Cisco Nexus 3064-X reversed airflow (port-side intake), AC power supply

N3K-C3064-X-BA-L3

X

X

X

—

—

—

—

Cisco Nexus 3064-X forward airflow (port-side exhaust), DC power supply

N3K-C3064-X-FD-L3

X

X

X

—

—

—

—

Cisco Nexus 3064-X forward airflow (port-side intake), DC power supply

N3K-C3064-X-BD-L3

X

X

X

—

—

—

—

Cisco Nexus 3064 fan module, Forward airflow (port-side exhaust); also used in the Cisco Nexus 3016

N3K-C3064-FAN

X

X

X

X

X

X

X

Cisco Nexus 3064 fan module, Reverse airflow (port-side intake); also used in the Cisco Nexus 3016

N3K-C3064-FAN-B

X

X

X

X

X

X

X

Cisco Nexus 3000 power supply, Forward airflow (port-side exhaust)

N2200-PAC-400W

X

X

X

X

X

X

X

Cisco Nexus 3000 power supply, Reverse airflow (port-side intake)

N2200-PAC-400W-B

X

X

X

X

X

X

X

Cisco Nexus 2000 power supply, Forward airflow (port-side exhaust)

N2200-PDC-400W

X

X

X

X

X

X

X

Cisco Nexus 2000 DC power supply, Reverse airflow (port-side intake)

N3K-PDC-350W-B

X

X

X

X

X

X

X

1.Recommended release for the Cisco Nexus 3064-TQ switch is Cisco NX-OS Release 5.0(3)U5(1c).

1.Recommended release for the Cisco Nexus 3064-TQ switch is Cisco NX-OS Release 5.0(3)U5(1c).

Table 1-3 Transceivers Supported by Cisco NX-OS Release 5.0(3)Software

Supported Cisco NX-OS Release

Transceivers

Part Number

5.0(3)U5(1b)

5.0(3)U5(1a)

5.0(3)U5(1)

5.0(3)U4(1)

5.0(3)U3(2b)

5.0(3)U3(2a)

5.0(3)U3(2)

5.0(3)U3(1)

5.0(3)U2(2c)

5.0(3)U2(2b)

5.0(3)U2(2a)

5.0(3)U2(2)

5.0(3)U2(1)

5.0(3)U1(2)

5.0(3)U1(2a)

5.0(3)U1(1a)

5.0(3)U1(1b)

5.0(3)U1(1d)

QSFP

Active copper splitter cable 7m

QSFP-4x10G-AC7M2

X

—

—

—

—

—

—

Active copper splitter cable 10m

X

—

—

—

—

—

—

Active copper QSFP transceiver module 7m

X

—

—

—

—

—

—

Active copper QSFP transceiver module 10m

X

—

—

—

—

—

—

40GBASE-CSR4 QSFP transceiver module with mpo connector 300 m

X

X

—

—

—

—

—

40GBASE-CSR4 QSFP transceiver module with mpo connector 300 m (using fiber splitter cables)

X

X

—

—

—

—

—

40GBASE-SR4 QSFP transceiver module with mpo connector 100 m

X

X

X

X

X

X

X

40GBASE-SR4 QSFP transceiver module with mpo connector 100 m (using fiber splitter cables)

X

X

X

X

X

X

X

40GBASE-CR4 passive copper cable, 1 m

QSFP-H40G-CU1M

X

X

X

X

X

X

X

40GBASE-CR4 passive copper cable, 3 m

QSFP-H40G-CU3M

X

X

X

X

X

X

X

40GBASE-CR4 passive copper cable, 5 m

QSFP-H40G-CU5M

X

X

X

X

X

X

X

QSFP to 4xSFP10G passive copper splitter cable, 1 m

QSFP-4SFP10G-CU1M

X

X

X

X

X

X

X

QSFP to 4xSFP10G passive copper splitter cable, 3 m

QSFP-4SFP10G-CU3M

X

X

X

X

X

X

X

QSFP to 4xSFP10G passive copper splitter cable, 5 m

QSFP-4SFP10G-CU5M

X

X

X

X

X

X

X

Revision 2 copper splitter cables 3m

QSFP-4SFP10G-CU3 (Rev. 2)

X

—

—

—

—

—

—

Revision 2 copper splitter cables 5m

QSFP-4SFP10G-CU5 (Rev. 2)

X

—

—

—

—

—

—

10-Gigabit

10GBASE-SR SFP+ module (multimode fiber [MMF])

SFP-10G-SR

X

X

X

X

X

X

X

10GBASE-LR SFP+ module (single-mode fiber [SMF])

SFP-10G-LR

X

X

X

X

X

X

X

10GBASE-ER SFP+ module (single-mode fiber [SMF])

SFP-10G-ER

X

X

X

X

X

X

X

10GBASE-ZR SFP+ module (single-mode fiber [SMF])3

X

X

X

—

—

—

—

X

X

X

—

—

—

—

10GBASE-CU SFP+ cable 1 m (Twinax cable)

SFP-H10GB-CU1M

X

X

X

X

X

X

X

10GBASE-CU SFP+ cable 3 m (Twinax cable)

SFP-H10GB-CU3M

X

X

X

X

X

X

X

10GBASE-CU SFP+ cable 5 m (Twinax cable)

SFP-H10GB-CU5M

X

X

X

X

X

X

X

SFP-H10GB-CU2M4

X

X

—

—

—

—

—

X

X

—

—

—

—

—

Active Optical cable 1m

X

—

—

—

—

—

—

Active Optical cable 3m

X

—

—

—

—

—

—

Active Optical cable 5m

X

—

—

—

—

—

—

Active Optical cable 7m

X

—

—

—

—

—

—

1-Gigabit Ethernet

1000BASE-T SFP5

X

X

X

X

X

X

X

Gigabit Ethernet SFP, LC connector SX transceiver (MMF)

X

X

X

X

X

X

X

Gigabit Ethernet SFP, LC connector SX transceiver (MMF)

GLC-SX-MMD

X

X

—

—

—

—

—

Gigabit Ethernet SFP, LC connector LX/LH transceiver (SMF)

X

X

X

X

X

X

X

1000BASE-LX/LH SFP transceiver module for MMF and SMF

X

—

—

—

—

—

—

1000Base BX fiber transceiver

X

—

—

—

—

—

—

1000Base BX fiber transceiver

X

—

—

—

—

—

—

1000BASE-T SFP transceiver module with extended operating temperature range

X

—

—

—

—

—

—

100 Mbps Ethernet

100BASE-FX SFP module for Gigabit Ethernet ports GLC-GE-100FX6

GLC-GE-100FX

X

X

X

X

X

X

X

2.Supported on the Cisco Nexus 3016, Cisco Nexus 3064-X, Cisco Nexus 3064-T, Cisco Nexus 3064, and Cisco Nexus 3064-E switches.

2.Supported on the Cisco Nexus 3016, Cisco Nexus 3064-X, Cisco Nexus 3064-T, Cisco Nexus 3064, and Cisco Nexus 3064-E switches.

3.Supported on the Cisco Nexus 3064-E and Cisco Nexus 3064-X switches.

3.Supported on the Cisco Nexus 3064-E and Cisco Nexus 3064-X switches.

4.Supported on the Cisco Nexus 3048, Cisco Nexus 3064-X, Cisco Nexus 3064, and Cisco Nexus 3064-E switches.

4.Supported on the Cisco Nexus 3048, Cisco Nexus 3064-X, Cisco Nexus 3064, and Cisco Nexus 3064-E switches.

5.Supported on the Cisco Nexus 3048, Cisco Nexus 3064-E, and Cisco Nexus 3064-X switches.

5.Supported on the Cisco Nexus 3048, Cisco Nexus 3064-E, and Cisco Nexus 3064-X switches.

6.Supported on the Cisco Nexus 3064, Cisco Nexus 3064-E, and Cisco Nexus 3064-X switches. For the GLC-GE-100FX, only part number 10-2019-02 is supported.

6.Supported on the Cisco Nexus 3064, Cisco Nexus 3064-E, and Cisco Nexus 3064-X switches. For the GLC-GE-100FX, only part number 10-2019-02 is supported.

Twinax Cable Support on Cisco Nexus 3000 Switches

Starting with Cisco Release NX-OS 5.0(3)U1(1), the following algorithm is used to detect copper SFP+ twinax, QSFP+ twinax, and QSFP+ splitter cables on Cisco Nexus 3000 switches.

If the attached interconnect (transceiver) is a copper SFP+ twinax or QSFP+ twinax cable:

- Verify the transceiver SPROM to match Cisco magic code.

- If the check succeeds, bring up the interface; else print the following warning message stating that a non-Cisco transceiver is attached and try to bring up the port.

2009 Oct 9 01:46:42 switch %ETHPORT-3-IF_NON-CISCO_TRANSCEIVER: Non-Cisco transceiver on interface Ethernet1/18 is detected.

If the attached transceiver is a QSFP+ splitter cable, then no special check is performed. Software tries to bring up the port.

The following disclaimer applies to non-Cisco manufactured and non-Cisco certified QSFP copper splitter cables:

If a customer has a valid support contract for Cisco Nexus switches, Cisco TAC will support twinax cables that are a part of the compatibility matrix for the respective switches. However, if the twinax cables are not purchased through Cisco, a customer cannot return these cables through an RMA to Cisco for replacement.

If a twinax cable that is not part of the compatibility matrix is connected into a system, Cisco TAC will still debug the problem, provided the customer has a valid support contract on the switches. However TAC may ask the customer to replace the cables with Cisco qualified cables if there is a situation that points to the cables possibly being faulty or direct the customer to the cable provider for support. Cisco TAC cannot issue an RMA against uncertified cables for replacement.

New and Changed Features

This section describes the new features introduced in Cisco NX-OS Release 5.0(3)U5(1b). This section includes the following topics:

- New Supported Hardware

- New Software Features

New Supported Hardware

Cisco NX-OS Release 5.0(3)U5(1b) does not include new hardware.

New Software Features

All Cisco Nexus 3000 Series switches are supported by Cisco NX-OS Release 5.0(3)U5(1b). Cisco NX-OS interoperates with any networking OS, including Cisco IOS software, that conforms to the networking standards mentioned in the product data sheet.

New Software Features in Cisco NX-OS Release 5.0(3)U5(1b)

Cisco NX-OS Release 5.0(3)U5(1b) is a patch release that includes bug fixes. It does not include new software features.

Upgrade Guidelines

for details about how to work around this issue.

Note This restriction does not apply to Cisco NX-OS Release 5.0(3)U3(2a) and Cisco NX-OS Release 5.0(3)U3(2).

In Cisco NX-OS Release 5.0(3)U3(1), support for IPv6 has been added in CoPP. To enable redirection of IPv6 control packets to the CPU, IPv6 CoPP must be configured on the system. Performing the write erase command on a device running Release 5.0(3)U3(1) automatically applies CoPP on the device and ensures that all IPv4 and IPv6 related CoPP configuration is setup correctly.

If you upgrade from a Cisco NX-OS release that does not support the CoPP feature to a release that does support the CoPP feature, you must run the setup utility after the upgrade to enable CoPP on the device.

If you upgrade from Cisco NX-OS Release 5.0(3)U2(2) (which supports the CoPP feature) to Cisco NX-OS Release 5.0(3)U3(1) (which adds CoPP classes for IPv6 support), you must run the setup script to enable the IPv6 CoPP feature on the device.

Limitations

There are no known limitations for Cisco NX-OS Release 5.0(3)U5(1b).

Caveats

Open and resolved caveat record numbers are provided with links to the Bug Toolkit where you can find details about each caveat.

This section includes the following topics:

- Resolved Caveats in Cisco NX-OS Release 5.0(3)U5(1b)

- Open Caveats in Cisco NX-OS Release 5.0(3)U5(1b)

Resolved Caveats in Cisco NX-OS Release 5.0(3)U5(1b)

lists descriptions of resolved caveats in Cisco NX-OS Release 5.0(3)U5(1b). The record ID links to the Cisco Bug Toolkit where you can find details about the caveat.

Table 1-4 Cisco NX-OS Release 5.0(3)U5(1b)—Resolved Caveats

Record Number

Resolved Caveat Headline

CSCtf29790

IPv6 neighbor discovery does not work correctly in a vPC topology.

CSCtl04576

TACACS could not register with CFS on feature enable:0x80b30020.

CSCtz32293

Even though TACACS servers are reachable, the following message appears: %TACACS-3-TACACS_ERROR_MESSAGE: All servers failed to respond

CSCud19813

Loss of TACACS authentication occurs intermittently on a Cisco Nexus 3000 Series switch.

CSCud73520

Add support to get all VLANs through the CISCO-VTP-MIB.

CSCud75519

MRIB core triggered by SNMP walk.

CSCud76323

The default duplex setting should not be displayed in the running configuration.

CSCue09836

The Cisco Nexus 3064 switch experienced a memory parity error after bootup.

CSCuh79034

High CPU utilization due to bcm_usd and syslogd causing protocol flaps.

Note This caveat was resolved in Cisco NX-OS Release 5.0(3)U5(1g)

Open Caveats in Cisco NX-OS Release 5.0(3)U5(1b)

lists descriptions of open caveats in Cisco NX-OS Release 5.0(3)U5(1b). The record ID links to the Cisco Bug Toolkit where you can find details about the caveat.

Table 1-5 Cisco NX-OS Release 5.0(3)U5(1b —Open Caveats

Record Number

Open Caveat Headline

CSCtz64709

A Cisco Nexus 3000 Series switch incorrectly forwards an echo request from an unspecified (::) address.

CSCub91054

command.

CSCub91090

A Cisco Nexus 3000 Series switch IPv6 route is impacted by a down interface.

CSCuc21712

A SPAN buffer does not use the complete configured buffer.

CSCuc29982

Ports become active when configured with the wrong speed and a GLC-SX-MMD or GLC-LH-SMD SFP is inserted in a Cisco Nexus 3000 Series switch.

CSCuc31412

Layer 3 routed ports are added as part of Layer 2 VLANs in hardware.

CSCuc32159

EIGRP routes that are learned through a Layer 3 port channel take approximately 20 seconds to converge on the failure of the Layer 3 port channel.

CSCuc34673

When shutting a range of all uplink ports on a Cisco Nexus 3048 switch where a GLC-BX-U SFP was inserted, the ports appear up on the peer switch.

CSCuc35912

Multicast traffic is duplicated with ECMP enabled.

CSCuc44153

A MAC address is not learned, but ARP is resolved on reload of both vPC peers.

CSCuc44353

In a Multicast Source Discovery Protocol (MSDP) configuration, different values are shown for ipMcastNexthopRouteProtocol.

CSCuc50368

SNMP CLI does not accept the AES authentication password.

CSCuc50968

A dual Protocol Independent Multicast (PIM) designated router (DR) scenario stops working in a vPC after subsequent reloads.

CSCuc56928

The initial PowerOn Auto Provisioning (POAP) discovery phase fails a few times before successful POAP iteration.

CSCuc57875

Syslog is not using the outgoing interface address as the source interface when the logging source-interface is modified.

CSCuc58104

An FP entry programming issue occurs with DHCP relay.

CSCuc59987

The interface storm control counter does not show the suppress value.

CSCuc64329

A route map is misinterpreted when used in configuring the rp-address in Protocol Independent Multicast (PIM).

CSCuc67363

command does not display the tunnel interface.

CSCuc70495

vrf command.

CSCuc71247

PVLAN vPC ports are inactive on the secondary switch with the reason “VLAN is not configured on remote vPC.”

CSCuc73455

Authentication fails on the AAA server with -while loopback interface is the global source-interface.

CSCuc77993

The SVI interface remains up with autostate enabled when all the interfaces are down.

CSCud79588

Last single port flaps in 64x10G mode for sometime and then stays up.

CSCue13321

TCAM exhaustion after creating 127 VRFs.

Related Documentation

Documentation for the Cisco Nexus 3000 Series Switch is available at the following URL:

The documentation set is divided into the following categories:

Release Notes

The release notes are available at the follwing URL:

Installation and Upgrade Guides

The installation and upgrade guides are available at the following URL:

Command References

The command references are available at the following URL:

Technical References

The technical references are available at the following URL:

Configuration Guides

The configuration guides are available at the following URL:

Error and System Messages

The system message reference guide is available at the following URL:

Documentation Feedback

. We appreciate your feedback.

Obtaining Documentation and Submitting a Service Request

, which also lists all new and revised Cisco technical documentation, at:

as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

© 2013 Cisco Systems, Inc. All rights reserved.