Added the following footnote: GLC-SX-MMD is supported on all Cisco Nexus 3000 Series Switches except for the Cisco Nexus 3064-T. Please refer to the comparability matrix for all the supported platforms.
Several new hardware and software features are introduced for the Cisco Nexus 3000 Series device to improve the performance, scalability, and management of the product line. Cisco NX-OS Release 6.x also supports all hardware and software supported in Cisco NX-OS Release 5.1 and Cisco NX-OS Release 5.0.
Cisco NX-OS 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 that run 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 that is 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 Quad Small Form-Factor Pluggable (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, one 100/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 Cisco NX-OS software.
2.OIR is supported for all optical modules and transceivers in Cisco NX-OS Release 6.02 and later releases.
3.Supported on the Cisco Nexus 3016, Cisco Nexus 3064-X, Cisco Nexus 3064-TQ, Cisco Nexus 3064, and Cisco Nexus 3064-E switches.
4.Supported on the Cisco Nexus 3064-E and Cisco Nexus 3064-X switches.
5.Supported on the Cisco Nexus 3048, Cisco Nexus 3064-X, Cisco Nexus 3064, and Cisco Nexus 3064-E switches.
6.GLC-SX-MMD is supported on all Cisco Nexus 3000 Series Switches except for the Cisco Nexus 3064-T. Please refer to the comparability matrix for all the supported platforms.
7.Supported on the Cisco Nexus 3048, Cisco Nexus 3064-E, and Cisco Nexus 3064-X switches.
8.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.
Note The Cisco Nexus 3000 supports 1,000 and 10,000 speeds while using SFP+ with Cisco QSA [CVR-QSFP-SFP10G] (and a maximum of 6 QSAs). The 100 speed is not supported on the SFP+ along with QSA, but using any speed 100 is supported on the SFP+.
Table 5 Transceivers Supported by Cisco NX-OS Release 5.x Software
9.Supported on the Cisco Nexus 3016, Cisco Nexus 3064-X, Cisco Nexus 3064-TQ, Cisco Nexus 3064, and Cisco Nexus 3064-E switches.
10.Supported on the Cisco Nexus 3064-E and Cisco Nexus 3064-X switches.
11.Supported on the Cisco Nexus 3048, Cisco Nexus 3064-X, Cisco Nexus 3064, and Cisco Nexus 3064-E switches.
12.Supported on the Cisco Nexus 3048, Cisco Nexus 3064-E, and Cisco Nexus 3064-X switches.
13.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 Series switches.
If the attached interconnect (transceiver) is a copper SFP+ twinax or QSFP+ twinax cable:
Verify the transceiver SPROM to match the Cisco magic code.
If the check succeeds, bring up the interface. Otherwise, print the following warning message appears stating that a non-Cisco transceiver is attached and that you should 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. The Cisco NX-OS 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 6.0(2)U1(1). This section includes the following topics:
All Cisco Nexus 3000 Series switches are supported by Cisco NX-OS Release 6.0(2)U1(1). Cisco NX-OS interoperates with any networking operating system, including Cisco IOS software, that conforms to the networking standards listed in the product data sheet.
Cisco NX-OS Release 6.0(2)U1(1) is a major new release that includes the following new software features:
Executive Mode Required for show BFD and show BFDc Commands
For consistency across platforms, you can now enter the show bfd and show bfdc commands in EXEC mode only.
To promote path diversity and reduce multi-exit discriminator (MED) oscillations, you can configure BGP Additional Paths so that multiple paths in the same peering session advertise the same prefix without the new paths replacing any previous paths.
Select Layer 3 as the Default Port Mode
Default Layer 3 Mode allows you to select Layer 3 as the default port mode when the switch is reloaded without a start-up configuration. This feature prevents packets from being forwarded before you have confirmed the port mode.
You can select the default port mode in the first setup script as shown in the following command:
With new commands, you can configure the number of times that neighbor unreachability detection (NUD) resends neighbor solicitations (NSs), configure Neighbor Discovery (ND) to glean an entry from an unsolicited neighbor advertisement (NA), or configure the length of time before an IPv6 ND cache entry expires.
Logging-Source Interface Command Enhancement
When you configure the loopback option for the Logging-Source Interface command, you no longer need to insert a space between the loopback command and the designated interface number (1 to 1023).
Wild Card Mask in permit ip Command
In previous releases, a wildcard mask was incorrectly applied as a net mask in the following command context:
permit ip src-ip wildcard mask dst-ip wildcard mask
Starting with this release, the mask will be treated correctly as a wildcard mask.
One Platform Kit (onePK)
The Cisco Nexus 3000 Series Switch supports a Controlled Availability release of onePK. One Platform Kit (onePK) is a cross platform API and software development kit that enables you to develop applications that interact directly with Cisco networking devices. onePK provides you access to networking services using a set of controlled APIs that share the same programming model and style. For more information, see the following URL:
In Power-On Auto-Provisioning, you can now use the MAC address to identify the new switch in the Client Option field during the DHCP Discovery phase. The MAC address also appears on the shipping label for the new switch.
Precision Time Protocol
This release introduces certain Precision Time Protocol (PTP) capabilities and commands. PTP is a time synchronization protocol for nodes that are distributed across a network. Its hardware timestamp provides greater accuracy than other time synchronization protocols such as the Network Time Protocol (NTP).
Q-in-Q VLAN Tunnel
The 802.1Q tunneling feature allows service providers to use a single VLAN to support customers who have multiple VLANs. Customer VLAN IDs are preserved and traffic from different customers is segregated within the service-provider infrastructure even when the customers appear to be on the same VLAN. The 802.1Q tunneling expands VLAN space by using a VLAN-in-VLAN hierarchy and tagging the tagged packets.
Virtual Port Channel
A Virtual Port Channel (vPC) peer link is an ip IGMP snooping command parameter that allows you to configure a static connection to a virtual port channel (vPC) peer link. By default, the vPC peer link is considered a multicast router port, and the multicast packet is sent to the peer link for each receiver VLAN.
VRF Route Leaking
With an Enterprise license and Border Gateway Protocol (BGP) enabled, Virtual Routing and Forwarding (VRF) route leaking is allowed in a VRF-lite scenario, based on certain configuration guidelines and limitations. With VRF route leaking, you can import IP prefixes from the global routing table (the default VRF) into any other VRF by using an import policy. The VRF import policy uses a route map to specify the prefixes to be imported into a VRF. IP prefixes that are imported into a VRF through this import policy cannot be re-imported into another VPN VRF. The maximum number of prefixes that can be imported from the default VRF is controlled by a limit that you configure.
Upgrade and Downgrade Guidelines
Upgrade Path to Release 6.0(2)U1(1)
Cisco Nexus 3000 Series switches that use software versions older than Release 5.0(3)U5(1) need to be updated to Release 5.0(3)U5(1) before they are upgraded to Release 6.0(2).
Cisco NX-OS Release 5.0(3)U3(1) does not support a software upgrade from Cisco NX-OS Release 5.0(3)U2(2c). If you want to upgrade through this path, see CSCty75328 for details about how to work around this issue.
Note It is recommended that you upgrade by using Cisco NX-OS install procedures.
In Cisco NX-OS Release 5.0(3)U3(1), support for IPv6 has been added in Control Plane Policing (CoPP). To enable redirection of IPv6 control packets to the CPU, you must configure IPv6 CoPP on the system. Entering the write erase command on a device that runs Release 5.0(3)U3(1) automatically applies CoPP on the device and ensures that all IPv4 and IPv6-related CoPP configuration is set up 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.
Cisco NX-OS Release 6.0(2)U1(1) has the following limitation:
In Cisco NX-OS releases older than Cisco NX-OS Release 6.0(2)U1(1), you can use the ip igmp join-group command to bind a Nexus 3000 Series switch to a multicast group. The switch generates an Internet Group Management Protocol (IGMP)-join for the specified group, and any multicast packets destined to the group are sent to the CPU. If there are receivers connected to the Nexus 3000 Series switch, which request for the group, then a copy of the packet is also sent to the receiver.
In Cisco NX-OS Release 6.0(2)U1(1) and higher releases, you cannot use the ip igmp join-group command to program any Outgoing Interface Lists (OILs) in the hardware. Even if there are receivers that request for the stream, no packets are sent to them. To bind a Nexus 3000 Series switch to a multicast group, use the ip igmp static-oif command instead of the ip igmp join-group command.
You can use the ip igmp join-group command only if the ip routing multicast enforce-rpf command, which is hidden, is enabled. This command can only be enabled if LISP is not in use, and LISP is not available on Nexus 3000 Series switches.
Link Level Flow Control (LLFC) is not supported on Cisco Nexus 3000 series and Cisco Nexus 3100 series switches.
Open and resolved caveat record numbers are provided with links to the Bug Toolkit where you can find details about each caveat.
The Cisco Management Information Base (MIB) list includes Cisco proprietary MIBs and many other Internet Engineering Task Force (IETF) standard MIBs. These standard MIBs are defined in Requests for Comments (RFCs). To find specific MIB information, you must examine the Cisco proprietary MIB structure and related IETF-standard MIBs supported by the Cisco Nexus 3000 Series switch. The MIB Support List is available at the following FTP sites:
To provide technical feedback on this document, or to report an error or omission, please send your comments to email@example.com. We appreciate your feedback.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
Subscribe to the What’s New in Cisco Product Documentation 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)