Cisco Nexus 3000 Series NX-OS Release Notes, Release 6.0(2)U2(1)
Cisco Nexus 3000 Series Switches
Cisco Nexus 3100 Series Switches
Twinax Cable Support on Cisco Nexus 3000 Switches
Cisco QSFP 40-Gbps Bidirectional Short-Reach Transceiver
IP-in-IP Encapsulation and Decapsulation Tunnel Support
BGP remove-private-as Enhancements
ICMP Unreachables Support to Set Source Interface
Static MAC Address Configuration
QoS Group Mapping to Priority Group
Command Options for WRED Drop Probability, Cap-Average and Queue Weight
Advertising IPv6 Routes Over IPv4 Peers
Default Interface Configuration
Disabling BGP Dampening with Redistribution
Cisco Plug-in for OpenFlow Release 1.1
Upgrade and Downgrade Guidelines
Upgrade Path to Release 6.0(2)U2(1)
Resolved Caveats in Cisco NX-OS Release 6.0(2)U2(1)
Open Caveats in Cisco NX-OS Release 6.0(2)U2(1)
Known Behaviors in Cisco NX-OS Release 6.0(2)U2(1)
Obtaining Documentation and Submitting a Service Request
Release Date: December 16, 2013
Part Number: OL-29565-05 D0
Current Release: Cisco NX-OS Release 6.0(2)U2(1)
This document describes the features, caveats, and limitations for Cisco Nexus 3000 Series and Cisco Nexus 3100 Series switches. Use this document in combination with documents listed in the “Obtaining Documentation and Submitting a Service Request” section.
Note Release notes are sometimes updated with new information about restrictions and caveats. See the following website for the most recent version of the Cisco Nexus 3000 Series release notes: http://www.cisco.com/c/en/us/support/switches/nexus-3000-series-switches/products-release-notes-list.html
Note Table 1 shows the online change history for this document.
Several new hardware and software features are introduced for the Cisco Nexus 3000 Series and Cisco Nexus 3100 Series devices 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:
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:
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.
For information about the Cisco Nexus 3000 Series, see the Cisco Nexus 3000 Series Hardware Installation Guide.
The Cisco Nexus 3100 Series switches are high-performance, high-density, ultra-low-latency Ethernet switches that provide line-rate Layer 2 and Layer 3 switching. In Cisco NX-OS Release 6.0(2)U2(1), the Cisco Nexus 3100 Series includes the Cisco Nexus 3132 switch.
The Cisco Nexus 3132 switch is a 1RU, 40-Gbps QSFP-based switch that supports 32 fixed 40-Gbps QSFP+ ports. It also has 4 SFP+ ports that can be internally multiplexed with the first QSFP port. Each QSFP+ port can operate in the default 40-Gbps mode or 4 x 10-Gbps mode, up to a maximum of 104 10-Gbps ports.
Each switch includes dual redundant power supply units, four redundant fans, one 10/100/1000 management port, and one console port. Each switch can be ordered with either forward (port-side exhaust) airflow or reverse (port-side intake) airflow for cooling. It supports both AC and DC power supplies. All combinations of power (AC/DC) and airflow (forward/reverse) are available. The Cisco Nexus 3100 Series switches run the Cisco NX-OS software.
For information about the Cisco Nexus 3000 Series, see the Cisco Nexus 3100 Series Hardware Installation Guide.
This section includes the following topics:
Cisco NX-OS Release 6.0(2)U2(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 2 shows the hardware supported by the Cisco NX-OS Release 6.x software. Table 3 shows the hardware supported by the Cisco NX-OS 5.x releases.
Table 4 shows the transceivers supported by the Cisco NX-OS Release 6.x software. Table 5 shows transceivers supported by the Cisco NX-OS 5.x releases.
Table 2 Hardware Supported by Cisco NX-OS Release 6.x Software
X1 |
||||||||
Cisco Nexus 3048 fan module with forward airflow (port-side exhaust) |
||||||||
Cisco Nexus 3048 fan module with reverse airflow (port-side intake) |
||||||||
Nexus 3064-T 500W forward airflow (port side exhaust) AC power supply |
||||||||
Nexus 3064-T 500 W reverse airflow (port side intake) AC power supply |
||||||||
Cisco Nexus 3064-X forward airflow (port-side exhaust) AC power supply |
||||||||
Cisco Nexus 3064-X reversed airflow (port-side intake) AC power supply |
||||||||
Cisco Nexus 3064-X forward airflow (port-side exhaust) DC power supply |
||||||||
Cisco Nexus 3064-X forward airflow (port-side intake) DC power supply |
||||||||
Cisco Nexus 3064 fan module with forward airflow (port-side exhaust); also used in the Cisco Nexus 3016 |
||||||||
Cisco Nexus 3064 fan module with reverse airflow (port-side intake); also used in the Cisco Nexus 3016 |
||||||||
Cisco Nexus 3000 power supply with forward airflow (port-side exhaust) |
||||||||
Cisco Nexus 3000 power supply with reverse airflow (port-side intake) |
||||||||
Cisco Nexus 2000 power supply with forward airflow (port-side exhaust) |
||||||||
Cisco Nexus 2000 DC power supply with reverse airflow (port-side intake) |
Transceivers
2
|
|||
---|---|---|---|
QSFP-4x10G-AC7M3 |
|||
QSFP-4x10G-AC10M 1 |
|||
QSFP-H40G-ACU7M 1 |
|||
QSFP-H40G-ACU10M 1 |
|||
40GBASE-CSR4 QSFP transceiver module with multifiber push-on (MPO) connector 300 m |
QSFP-40G-CSR4 1 |
||
40GBASE-CSR4 QSFP transceiver module with MPO connector 300 m (using fiber splitter cables) |
QSFP-40G-CSR4 1 |
||
40GBASE-SR4 QSFP transceiver module with MPO connector 100 m |
QSFP-40G-SR4 1 |
||
40GBASE-SR4 QSFP transceiver module with MPO connector 100 m (using fiber splitter cables) |
QSFP-40G-SR4 1 |
||
40GBASE-LR4 QSFP transceiver module with LC connector 10 km (using single mode fiber) |
|||
10GBASE-DWDM long-range transceiver module 80 km with single mode duplex fiber |
|||
10GBASE-ZR SFP+ module (single-mode fiber [SMF])4 |
SFP-10G-ZR 2 |
||
10GBASE-DWDM SFP+ module (single-mode fiber [SMF]) 2 |
10-2767-01 2 |
||
10GBASE-CU SFP+ cable 2 m (Twinax cable) 3 |
SFP-H10GB-CU2M5 |
||
10GBASE-CU SFP+ cable 2.5 m (Twinax cable) 3 |
SFP-H10GB-CU2-5M 3 |
||
SFP-10G-AOC1M 4 |
|||
SFP-10G-AOC3M 4 |
|||
SFP-10G-AOC5M 4 |
|||
SFP-10G-AOC7M 4 |
|||
GLC-BX-D 4 |
|||
GLC-BX-U 4 |
|||
GLC-LH-SM 4 |
|||
GLC-LH-SMD 4 |
|||
GLC-SX-MM 3 |
|||
GLC-SX-MMD6 |
|||
1000BASE-T SFP7 |
GLC-T 4 |
||
1000BASE-T SFP transceiver module with extended operating temperature range |
SFP-GE-T 4 |
||
100BASE-FX SFP module for Gigabit Ethernet ports GLC-GE-100FX8 |
10-2019-02 5 |
QSFP-4x10G-AC7M9 |
||||||||
QSFP-4x10G- |
||||||||
QSFP-H40G- |
||||||||
QSFP-H40G- |
||||||||
40GBASE-CSR4 QSFP transceiver module with MPO connector 300 m |
QSFP-40G-CSR4 1 |
|||||||
40GBASE-CSR4 QSFP transceiver module with MPO connector 300 m (using fiber splitter cables) |
QSFP-40G-CSR4 1 |
|||||||
40GBASE-SR4 QSFP transceiver module with MPO connector 100 m |
QSFP-40G-SR4 1 |
|||||||
40GBASE-SR4 QSFP transceiver module with MPO connector 100 m (using fiber splitter cables) |
QSFP-40G-SR4 1 |
|||||||
10GBASE-ZR SFP+ module (single-mode fiber [SMF])10 |
SFP-10G-ZR 2 |
|||||||
10GBASE-DWDM SFP+ module (single-mode fiber [SMF]) 2 |
10-2767-01 2 |
|||||||
10GBASE-CU SFP+ cable 2 m (Twinax cable) 3 |
SFP-H10GB- |
|||||||
10GBASE-CU SFP+ cable 2.5 m (Twinax cable) 3 |
SFP-H10GB- |
|||||||
SFP-10G-AOC1M 4 |
||||||||
SFP-10G-AOC3M 4 |
||||||||
SFP-10G-AOC5M 4 |
||||||||
SFP-10G-AOC7M 4 |
||||||||
1000BASE-T SFP12 |
GLC-T 4 |
|||||||
GLC-SX-MM 3 |
||||||||
GLC-SX-MMD 5 |
||||||||
GLC-LH-SM 4 |
||||||||
GLC-LH-SMD 4 |
||||||||
GLC-BX-U 4 |
||||||||
GLC-BX-D 4 |
||||||||
1000BASE-T SFP transceiver module with extended operating temperature range |
SFP-GE-T 4 |
|||||||
100BASE-FX SFP module for Gigabit Ethernet ports GLC-GE-100FX13 |
10-2019-02 5 |
9.Supported on the Cisco Nexus 3016, Cisco Nexus 3064-X, Cisco Nexus 3064-TQ, Cisco Nexus 3064, and Cisco Nexus 3064-E 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:
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.
The Cisco QSFP 40-Gbps Bidirectional (BiDi) transceiver is a short-reach pluggable optical transceiver with a duplex LC connector for 40-GbE short-reach data communications and interconnect applications by using multimode fiber (MMF). The Cisco QSFP 40-Gbps BiDi transceiver offers a solution that uses existing duplex MMF infrastructure for 40-GbE connectivity. With the Cisco QSFP 40-Gbps BiDi transceiver, customers can upgrade their network from 10-GbE to 40-GbE without incurring any fiber infrastructure upgrade cost. The Cisco QSFP 40-Gbps BiDi transceiver can enable 40-GbE connectivity in a range of up to 100 meters over OM3 fiber, which meets most data center reach requirements. It complies with the Multiple Source Agreement (MSA) QSFP specification and enables customers to use it on all Cisco QSFP 40-Gbps platforms and achieve high density in a 40-GbE network. It can be used in data centers, high-performance computing (HPC) networks, enterprise and distribution layers, and service provider transport applications.
This section describes the new features introduced in Cisco NX-OS Release 6.0(2)U2(1). This section includes the following topics:
Cisco NX-OS Release 6.0(2)U2(1) supports the new hardware listed in this section.
All Cisco Nexus 3000 Series switches are supported by Cisco NX-OS Release 6.0(2)U2(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)U2(1) includes the following new software features:
Priority Flow Control (PFC) is a mechanism that prevents frame loss due to congestion. PFC functions on a per class-of-service (CoS) basis. When a buffer threshold is exceeded due to congestion, PFC sends a pause frame that indicates which CoS value needs to be paused.
Policy-based routing allows you to configure a defined policy for IPv4 and IPv6 traffic flows, lessening reliance on routes derived from routing protocols. All packets received on an interface with policy-based routing enabled are passed through enhanced packet filters or route maps. The route maps dictate the policy, determining where to forward packets.
IP tunnels can encapsulate a same-layer or higher-layer protocol and transport the result over IP through a tunnel created between two devices. This release introduces IP-in-IP encapsulation and decapsulation as carrier protocols. It also introduces Point-to-Point IP-in-IP Tunnel Encapsulation and Decapsulation and Multi-Point IP-in-IP Tunnel Decapsulation as tunnel types.
This release add two new keywords to the existing remove-private-as command - all and replace-as.
When the eBGP Next-Hop Unchanged feature is configured, BGP sends routes to an eBGP multihop peer without modifying the next hop attribute. This feature provides flexibility when designing and migrating networks. It can be used only between eBGP peers configured as multihop.
The Network Time Protocol (NTP) synchronizes the time of day among a set of distributed time servers and clients so that you can correlate events when you receive system logs and other time-specific events from multiple network devices.
You can configure an interface IP address for ICMP source IP field to handle ICMP error messages. When ICMP packets are constructed in a network stack, the packets will use the configured interface IP address.
Through this feature, you can filter ingress traffic at source ports by using ACLs so that they mirror only those packets of information that match the ACL criteria.
You can change the default MAC address of the Layer 3 interface by using the mac-address command from the interface configuration mode. A static MAC address can be configured on SVI, Layer 3 interfaces, port channels, Layer 3 subinterfaces, and tunnel interfaces.
You can now monitor the real-time status of the shared buffer, per port at ingress as well as egress.
You can monitor the Tx and Rx counters for PFC-enabled devices either at an interface level or at a per priority (COS) level for each interface. Currently, PFC frame counters are supported only on the following switches:
You can configure the threshold for using shared buffers at egress and ingress based on the alpha value.
By default, the priority-group number is assigned by the system. However, you can override it and map it to a QoS group by using the priority-group command.
New command options are now available to control the WRED and ECN frame dropping and marking parameters when queue usage is between minimum and maximum thresholds.
ACL logging allows you to monitor traffic flows that hit specific access control lists (ACLs). A flow table maintains the number of hits per flow.
IPv6 addresses are now advertised over IPv4 eBGP peers, thus allowing IPv6 traffic to be routed over a preestablished IPv4 eBGP connection.
You now have a single command to revert to the default configuration of an interface.
Cisco NX-OS Release 6.0(2)U2(1) introduces fast reboot. During fast reboot, the system image that runs on the CPU reloads the new image and runs it without a CPU or firmware reset. Although there is a brief disruption in traffic during fast reboot, it enables a switch to reload faster than during cold reboot. Currently, fast reboot is supported only with limited configurations and topologies on the following switches:
To compare the hardware and software configuration of all interfaces in a VLAN and display the results, use the following command:
To compare the hardware and software configuration of all ports in a port channel and display the results, use the following command:
To compare the software and hardware configuration of L3 interfaces and display the results, use the following command:
Note The L3 interface checker works only on the physical interface.
To compare the software and hardware link state of interfaces and display the results, use the following command:
To compare the software and hardware configuration of the spanning tree state of a VLAN and display the results, use the following command:
To display the results of the forwarding inconsistency checker for IPv4 or IPv6 routes, use the following command:
Use the test forwarding inconsistency command to start the forwarding inconsistency checker and the test forwarding inconsistency stop command to end the forwarding inconsistency checker.
Cisco NX-OS Release 6.0(2)U2(1) introduces software error recovery (SER) for soft errors in the internal memory tables of the forwarding engine.
The startup configuration file is stored as an ASCII text file and all commands in the configuration file are run during the next bootup to generate the binary configuration file.
Cisco NX-OS Release 6.0(2)U2(1) supports a minimum guaranteed number of entries for L2, L3 host, LPM tables, and a 256K x 105 bit shared table.
Cisco NX-OS Release 6.0(2)U2(1) supports hashing for transit NVGRE traffic. You can configure the switch to include the GRE Key field present in the GRE header in hash computations when NVGRE traffic is forwarded over a port channel or an Equal Cost Multipath (ECMP).
The resilient hashing system for Cisco Nexus 3100 Series switches maps traffic flows to physical ports. In case a link fails, the flows assigned to the failed link are redistributed uniformly among the working links. The existing flows through the working links are not rehashed and their packets are not delivered out of order.
In NX-OS Release 6.0(2)U2(1), you can operate QSFP ports as either 40-GbE or 4 x10-GbE modes on Cisco Nexus 3132 switches.
SVI Autostate Disable enables the Switch Virtual Interface (SVI) to be in the “up” state even if no interface is in the “up” state in the corresponding VLAN.
When an IGP metric of redistributed routes into BGP changes, BGP has internal dampening that prevents an immediate route update to the BGP peers. It affects how BGP handles IGP metric changes reported for redistributed routes. BGP dampens these changes through a batch process with a 10 minutes delay. The dampen-igp-metric command allows the user to adjust this delay or remove it altogether for quicker response to these changes.
Cisco NX-OS Release 6.0(2)U2(1) supports Cisco Plug-in Version 1.1 for OpenFlow. Cisco Plug-in for OpenFlow creates TCP/IP connections to controllers based on OpenFlow Switch Specification Version 1.0.1 (Wire Protocol 0x01).
Cisco Plug-in for OpenFlow resides on the switch and the controllers reside on a server, external to the switch. Flow management and any network management are either part of the controller or accomplished through the controller. Cisco Plug-in for OpenFlow maintains databases for configurations on the logical switch, OpenFlow-enabled interfaces, and flows. The interface database contains the list of OpenFlow-enabled interfaces on the logical switch, and the flow database contains the list of flows on the logical switch as well as the interface programmed to forward traffic.
This release includes all the necessary infrastructure to support the Cisco Plug-in for OpenFlow. This infrastructure includes support for the installation of the Cisco Plug-in for OpenFlow as a Virtual Services container, support for matches and actions defined by version 1.0 of the OpenFlow protocol, and support for connectivity to the Cisco Extensible Network Controller (XNC).
Cisco Nexus 3000 Series switches completely support One Platform Kit (onePK) Turbo API in Cisco NX-OS Release 6.0(2)U2(1). 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 by using a set of controlled APIs that share the same programming model and style. For more information, see the following URL:
Ensure that you use the install all command to upgrade the switch software from one Cisco NX-OS release to another.
Cisco Nexus 3000 Series switches that use software versions older than Cisco NX-OS Release 5.0(3)U5(1) need to be updated to Cisco NX-OS Release 5.0(3)U5(1) before they are upgraded to Cisco NX-OS 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 to Cisco NX-OS Release 6.0(2)U2(1) 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.
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 Search page where you can find details about each caveat.
This section includes the following topics:
Table 6 lists descriptions of resolved caveats in Cisco NX-OS Release 6.0(2)U2(1). The record ID links to the Cisco Bug Search page where you can find details about the caveat.
Table 7 lists descriptions of open caveats in Cisco NX-OS Release 6.0(2)U2(1). The record ID links to the Cisco Bug Search page where you can find details about the caveat.
Table 7 Cisco NX-OS Release 6.0(2)U2(1) —Open Caveats
Large core files are split into 3 or more files. For example:
To decode the multiple core files, first club the files to a single file as demonstrated below:
$ cat 1405964207_0x101_fwm_log.3679.tar.gz* > 1405964207_0x101_fwm_log.3679.tar.gz
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:
ftp://ftp.cisco.com/pub/mibs/supportlists/nexus3000/Nexus3000MIBSupportList.html
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:
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
The command references are available at the following URL:
http://www.cisco.com/en/US/products/ps11541/prod_command_reference_list.html
The technical references are available at the following URL:
http://www.cisco.com/en/US/products/ps11541/prod_technical_reference_list.html
The configuration guides are available at the following URL:
http://www.cisco.com/en/US/products/ps11541/products_installation_and_configuration_guides_list.html
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
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.
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.