PDF(133.6 KB) View with Adobe Reader on a variety of devices
ePub(83.3 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(92.9 KB) View on Kindle device or Kindle app on multiple devices
Updated:July 31, 2012
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
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.
Starting with Cisco Release NX-OS 5.0(3)U1(1), the following algorithm is used to detect SFP+ twinax cables on Cisco Nexus 3000 switches:
If the attached interconnect (transceiver) is a twinax cable:
Verify the transceiver SPROM to match Cisco magic code.
If the check succeeds, bring up the interface; else check whether the Vendor Part Number (PN) has been certified.
If the Vendor PN is certified, 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.
Starting with Cisco Release NX-OS 5.0(3)U3(1), the following algorithm is used to detect copper splitter (QSFP) cables on Cisco Nexus 3000 switches:
A Cisco Nexus 3000 switch allows any copper splitter (QSFP, connector type 0x21) cable to come up, however the following disclaimer applies to non-Cisco manufactured and non-Cisco certified QSFP copper splitter cables.
Cisco Service and Support
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
Cisco NX-OS Release 5.0(3)U3(2b) is a maintenance release that includes bug fixes. This release does not include new software features.
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 This restriction does not apply to Cisco NX-OS Release 5.0(3)U3(2b), 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.
There are no known limitations for Cisco NX-OS Release 5.0(3)U3(2b).
Open and resolved caveat record numbers are provided with links to the Bug Toolkit where you can find details about each caveat.
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)