Table Of Contents
Cisco Nexus 3000 Series NX-OS Release Notes, Release 5.0(3)U3(1)
Cisco Nexus 3000 Series Switches
Twinax Cable Support on Cisco Nexus 3000 Switches
New Software Features in Cisco NX-OS Release 5.0(3)U3(1)
Resolved Caveats in NX-OS Release 5.0(3)U3(1)
Obtaining Documentation and Submitting a Service Request
Cisco Nexus 3000 Series NX-OS Release Notes, Release 5.0(3)U3(1)
Release Date: February 29, 2012Part Number: OL-26631-01 G0
Current Release: Cisco NX-OS Release 5.0(3)U3(1)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 DescriptionOL-26631-01
A0
February 29, 2012
Created NX-OS Release 5.0(3)U3(1) release notes.
B0
March 5, 2012
Updated the "New Software Features" section to include vPC Peer Link Enhancements.
C0
March 28, 2012
•Added the "Twinax Cable Support on Cisco Nexus 3000 Switches" section.
•Added an upgrade guideline to the "Upgrade Guidelines" section.
•Added open caveat CSCty75328.
D0
May 17, 2012
Added resolved caveat CSCtx63122.
E0
June 15, 2012
Updated supported versions in Table 1-3.
F0
June 21, 2012
Updated part number for Cisco Nexus 3048 switch.
Added Release 5.0(3)U2(2d) to Table 1-2.
G0
November 28, 2013
Updated resolved caveat CSCuh79034.
7
Contents
This document includes the following sections:
•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.
For information about the Cisco Nexus 3000 Series, see the Cisco Nexus 3000 Series Hardware Installation Guide.
System Requirements
This section includes the following topics:
•Twinax Cable Support on Cisco Nexus 3000 Switches
Memory Requirements
The Cisco NX-OS Release 5.0(3)U3(1) software requires 135MB of flash memory.
Hardware Supported
Cisco NX-OS Release 5.0(3)U3(1) supports the Cisco Nexus 3000 Series switches. You can find detailed information about supported hardware in the Cisco Nexus 3000 Series Hardware Installation Guide.
Table 1-2 shows the hardware supported by Cisco NX-OS Release 5.0(3)U3(1) software.
Table 1-3 shows the transceivers supported by Cisco NX-OS Release 5.0(3)U3(1) software.
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 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
This section describes the new features introduced in Cisco NX-OS Release 5.0(3)U3(1). This section includes the following topics:
New Hardware Features
Cisco NX-OS Release 5.0(3)U3(1) supports the Cisco Nexus 3064-X switch which is a 1 RU switch that supports 48 SFP+ ports and four QSFP+ ports. The Cisco Nexus 3064 delivers ultra-low nominal latency that allows customers to implement high-performance infrastructures for high-frequency trading workloads. It supports power-on auto provisioning and consumes low power of approximately 2W per port.
New Software Features
All Cisco Nexus 3000 Series switches are supported by Cisco NX-OS Release 5.0(3)U3(1). 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)U3(1)
Cisco NX-OS Release 5.0(3)U3(1) includes the following software features:
•PowerOn Auto Provisioning (POAP)
Embedded Event Manager (EEM)
The Embedded Event Manager (EEM) provides a central, policy-driven framework to detect and handle events in the system by monitoring events that occur on your device and taking action to recover or troubleshoot these events, based on your configuration.
EEM consists of three major components:
•Event statements
Events to monitor from another Cisco NX-OS component that may require some action, workaround, or notification.
•Action statements
An action that EEM can take, such as sending an e-mail or disabling an interface, to recover from an event.
•Policies
An event paired with one or more actions to troubleshoot or recover from the event.
Without EEM, each individual component is the responsible for detecting and handling its own events.
For more information, see the Cisco Nexus 3000 Series NX-OS System Management Configuration Guide.
PowerOn Auto Provisioning (POAP)
PowerOn Auto Provisioning (POAP) automates the process of upgrading software images and installing configuration files on Nexus switches that are being deployed in the network for the first time.
When a Nexus switch with the POAP feature boots and does not find the startup configuration, the switch enters POAP mode, locates a DHCP server and bootstraps itself with its interface, gateway, and DNS server IP addresses. It also obtains the IP address of a TFTP server or the URL of an HTTP server and downloads a configuration script that is run on the switch to download and install the appropriate software image and configuration file.
Note Starting with Cisco NX-OS Release 5.0(3)U3(1), all Cisco Nexus 3000 Series switches boot with POAP by default. You can get to a normal bootup by aborting the POAP bootup from the console.
POAP requires the following network infrastructure:
•A DHCP server to bootstrap the interface IP address, gateway address, bootfile name, TFTP server-name and DNS server. The DHCP information is used until the script execution phase completes.
•A TFTP or HTTP server containing the configuration script used to automate the software image installation and configuration process.
•One or more SCP, FTP, TFTP, or HTTP servers containing the desired software images and configuration files.
For more information, see the Cisco Nexus 3000 Series NX-OS Fundamentals Configuration Guide.
IPv6 Support
Cisco NX-OS Release 5.0(3)U3(1) supports the following IPv6 features:
•IP Version 6 Addressing Architecture
•An aggregated global unicast address format
•Neighbor discovery
•IPv6 stateless address autoconfiguration
•Internet Control Message Protocol (ICMPv6)
•Duplicate address detection
•Unique local IPv6 unicast addresses
•Hot-Standby Router Protocol (HSRP) for IPv6, including link-layer address as well as global IPv6 address support
•Ping6 and traceroute6
•OSPFv3 and BGP support for IPV6
•IPv6 RACLs
•IPv6 based QoS and IPv6 based CoPP
•IPv6 switching and routing support for multiple VRFs
The following IPv6 features are not supported in Cisco NX-OS Release 5.0(3)U3(1):
•Layer 3 multicast routing, including: PIMv6, MLDv1, and MLDv2
•RIPng and EIGRPv6
•Layer 2 IPv6 Multicast Snooping
•First Hop security for NX-OS
•IPv6 supports PACL and VACL are not supported
For more information see the Cisco Nexus 3000 Series NX-OS Unicast Routing Configuration Guide and the Cisco Nexus 3000 NX-OS Quality of Service Configuration Guide, Cisco Nexus 3000 Series NX-OS Fundamentals Configuration Guide, Cisco Nexus 3000 Series NX-OS Security Configuration Guide, and the Cisco Nexus 3000 Verified Scalability Guide.
Switching Modes
The switching mode determines whether a switch begins forwarding a frame as soon as the switch has read the destination details in the packet header or waits until the entire frame has been received and checked for cyclic redundancy check (CRC) errors before forwarding them to the network.
The switching mode is applicable to all packets being switched or routed through the hardware and can be saved persistently through reboots and restarts.
The switch operates in either of the following switching modes:
•Cut-Through Switching Mode
Cut-through switching mode is enabled by default. Switches operating in cut-through switching mode start forwarding the frame as soon as the switch has read the destination details in the packet header. A switch in cut-through mode forwards the data before it has completed receiving the entire frame.
The switching speed in cut-through mode is faster than the switching speed in store-and-forward switching mode.
•Store-and-Forward Switching Mode
When store-and-forward switching is enabled, the switch checks each frame for cyclic redundancy check (CRC) errors before forwarding them to the network. Each frame is stored until the entire frame has been received and checked.
Because it waits to forward the frame until the entire frame has been received and checked, the switching speed in store-and-forward switching mode is slower than the switching speed in cut-through switching mode.
For more information see the Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide.
BFD Over OSPF
Bidirectional Forwarding Detection (BFD) over OSPF is supported. In addition, the minimum timer interval has changed to 50 ms. Based on this timer interval, the maximum number of sessions is 272.
For more information, see the Cisco Nexus 3000 Series NX-OS Unicast Routing Configuration Guide.
BGP Enhancements
The following BGP enhancements are included in this release:
•Next-Hop Self Support for BGP Route Reflector Clients
A route-map to all outgoing routes for IBGP neighbors can set the next-hop as its own address. Route reflectors reflect the routes as is without changing the next-hop for routes received from IBGP neighbors. The configuration allows you to change the next-hop to itself.
•CLI allowas-in Keyword
Enables the allowas-in feature for BGP and configures the number of occurrences of the AS number. By default, the number of occurrences of the AS number is set to 3.
For more information, see the Cisco Nexus 3000 Series NX-OS Unicast Routing Configuration Guide.
Python Scripting Support
Cisco NX-OS Release 5.0(3)U3(1) supports scripting with Python. For additional information, see the Cisco Nexus 3000 Series Python API Reference Guide.
Feature Scheduler
The new scheduler feature command has been added to support cron jobs. For more information about the feature scheduler, see the Cisco Nexus 3000 NX-OS System Management Configuration Guide.
Minimum Links
You can configure the LACP minlinks feature to set the minimum amount of links in a LACP bundle before a port-channel is taken down. For more information about this feature, see the Cisco Nexus 3000 Series NX-OS Layer 2 Switching Configuration Guide.
SVI and VLAN Counters
The show interface vlan vlan-id counters command has been enhanced to correctly show input and output packet counts. For more information, see the Cisco Nexus 3000 Series Command Reference.
vPC Peer Link Enhancements
To accommodate non-scale deployments, a 1G link can now be used as a vPC peer link on the Cisco Nexus 3048 switch. For information about configuing a vPC, see the Cisco Nexus 3000 NX-OS Interfaces Configuration Guide.
Upgrade Guidelines
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 to upgrade through this path, see CSCty75328 for details about how to work around this issue.
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)U3(1).
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 NX-OS Release 5.0(3)U3(1)
Resolved Caveats in NX-OS Release 5.0(3)U3(1)
Table 1-4 lists descriptions of resolved caveats in Cisco NX-OS Release 5.0(3)U3(1). The record ID links to the Cisco Bug Toolkit where you can find details about the caveat.
Open Caveats
Table 1-5 lists descriptions of open caveats in Cisco NX-OS Release 5.0(3)U3(1). The record ID links to the Cisco Bug Toolkit where you can find details about the caveat.
Related Documentation
Documentation for the Cisco Nexus 3000 Series Switch is available at the following URL:
http://www.cisco.com/en/US/products/ps11541/tsd_products_support_series_home.html
The documentation set is divided into the following categories:
Release Notes
The release notes are available at the follwing URL:
http://www.cisco.com/en/US/products/ps11541/prod_release_notes_list.html
Installation and Upgrade Guides
The installation and upgrade guides are available at the following URL:
http://www.cisco.com/en/US/products/ps11541/prod_installation_guides_list.html
Command References
The command references are available at the following URL:
http://www.cisco.com/en/US/products/ps11541/prod_command_reference_list.html
Technical References
The technical references are available at the following URL:
http://www.cisco.com/en/US/products/ps11541/prod_technical_reference_list.html
Configuration Guides
The configuration guides are available at the following URL:
http://www.cisco.com/en/US/products/ps11541/products_installation_and_configuration_guides_list.html
Error and System Messages
The system message reference guide is available at the following URL:
http://www.cisco.com/en/US/products/ps11541/products_system_message_guides_list.html
Documentation Feedback
To provide technical feedback on this document, or to report an error or omission, please send your comments to nexus3k-docfeedback@cisco.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:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
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)
© 2012 Cisco Systems, Inc. All rights reserved.