This document describes the features, bugs, and limitations for Cisco Nexus 3500 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 bugs. See the following website for the most recent version of the Cisco Nexus 3500 Series release notes: http://www.cisco.com/c/en/us/support/switches/nexus-3000-series-switches/products-release-notes-list.html.
Table 1 shows the online change history for this document.
Table 1. Online History Change
Revision |
Date |
Description |
A0 |
June 15, 2015 |
Created NX-OS Release 6.0(2)A4(6) release notes |
Upgrade and Downgrade Guidelines
Obtaining Documentation and Submitting a Service Request
Several new hardware and software features are introduced for the Cisco Nexus 3548 switch to improve the performance, scalability, and management of the product line. Cisco NX-OS Release 6.0 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.
This section includes the following topics:
■ Cisco Nexus 3500 Series Switches
The Cisco Nexus 3500 platform is an extension of the Cisco Nexus 3000 Series of 100M, 1, 10, and 40 Gigabit Ethernet switches built from a switch-on-a-chip (SoC) architecture. Switches in the Cisco Nexus 3500 series include Algorithm Boost (or Algo Boost) technology that is built into the switch application-specific integrated circuit (ASIC). Algo Boost allows the Cisco Nexus 3548 switch to achieve Layer 2 and Layer 3 switching latencies of less than 200 nanoseconds (ns). In addition, Algo Boost contains several innovations for latency, forwarding features, and performance visibility, including two configurable modes for low latency:
■ Normal mode: This mode is suitable for environments needing low latency and high scalability.
■ Warp mode: This mode consolidates forwarding operations within the switching ASIC, lowering latency by up to an additional 20 percent compared to normal operation..
Active buffer monitoring accelerates the collection of buffer utilization data in hardware, allowing significantly faster sampling intervals. Even on the lowest-latency switches, data packets can incur a millisecond or more of latency during periods of congestion. Previous buffer utilization monitoring techniques were based entirely on software polling algorithms with polling with higher polling intervals that can miss important congestion events.
The Cisco Nexus 3548 switch is the first member of the Cisco Nexus 3500 platform. As a compact one-rack-unit (1RU) form-factor 10 Gigabit Ethernet switch, the Cisco Nexus 3548 switch provides line-rate Layer 2 and Layer 3 switching at extremely low latency. The switch runs Cisco NX-OS software that has comprehensive features and functions that are widely deployed globally. The Cisco Nexus 3548 contains no physical layer (PHY) chips, which allows low latency and low power consumption. The switch supports both forward and reversed airflow and both AC and DC power inputs.
The Cisco Nexus 3524 switch is a Cisco Nexus 3548 switch, but with only 24 ports active and can be upgraded to use all 48 ports. As a compact one-rack-unit (1RU) form-factor 10 Gigabit Ethernet switch, the Cisco Nexus 3548 switch is the lowest entry point for main-stream top-of-rack (TOR) data center deployments which offers line-rate Layer 2 and Layer 3 switching with a comprehensive feature set, including Algo Boost technology, and ultra-low latency.
For information about the Cisco Nexus 3500 Series, see the Cisco Nexus 3500 Series Hardware Installation Guide.
This section includes the following topics:
■ Memory Requirements
■ Hardware Supported
The Cisco NX-OS Release 6.0(2)A4(6) software requires 203 MB of flash memory.
Cisco NX-OS Release 6.0(2)A4(6) supports the Cisco Nexus 3500 Series switches. You can find detailed information about supported hardware in the Cisco Nexus 3500 Series Hardware Installation Guide.
Table 2 shows the hardware supported by Cisco NX-OS Release 6.0(2)A4(6) software.
Table 2. Hardware Supported by Cisco NX-OS Release 6.0(2)A4(6) Software.
Hardware |
Part Number |
Supported Software Release |
Cisco Nexus 3500 Series |
|
|
Cisco Nexus 3548 switch |
||
Cisco Nexus 3524 switch |
||
Cisco Nexus 2000 or Nexus 3000 individual fan, forward airflow (port side exhaust |
||
Cisco Nexus 2000 or Nexus 3000 individual fan, reversed airflow (port side intake) |
||
Cisco Nexus 2000 or Nexus 3000 400W AC power supply, forward airflow (port side exhaust) |
||
Cisco Nexus 2000 or Nexus 3000 400W AC power supply, reversed airflow (port side intake) |
||
Cisco Nexus 2000 or Nexus 3000 400W DC power supply, forward airflow (port side exhaust) |
||
Cisco Nexus 2000 or Nexus 3000 350W DC power supply, reversed airflow (port side intake) |
||
Transceivers |
||
10-Gigabit |
||
10GBASE-ZR SFP+ module (single-mode fiber [SMF]) |
||
10GBASE-CU SFP+ cable 1.5 m (Twinax cable) |
||
10GBASE-CU SFP+ cable 2 m (Twinax cable) |
||
10GBASE-CU SFP+ cable 2.5 m (Twinax cable) |
||
Active optical cable 1 m |
||
Active optical cable 3 m |
||
Active optical cable 5 m |
||
Active optical cable 7 m |
||
10GBASE-DWDM long-range transceiver module 80 km with single mode duplex fiber |
||
10GBASE-DWDM long-range transceiver module 80 km with single mode duplex fiber |
||
10GBASE-SR SFP+ module (multimode fiber [MMF]) |
||
10GBASE-LR SFP+ module (single-mode fiber [SMF]) |
||
Cisco 10GBASE-ER SFP+ Module for SMF |
||
10GBASE-CU SFP+ cable 1 m (Twinax cable) |
||
10GBASE-CU SFP+ cable 3 m (Twinax cable) |
||
10GBASE-CU SFP+ cable 5 m (Twinax cable) |
||
Active Twinax cable assembly, 7 m |
||
Active Twinax cable assembly, 10 m |
||
1-Gigabit Ethernet |
||
1000BASE-T SFP |
||
Gigabit Ethernet SFP, LC connector EX transceiver (MMF) |
||
Gigabit Ethernet SFP, LC connector ZX transceiver (MMF) |
||
1000BASE-T SFP |
||
Gigabit Ethernet SFP, LC connector SX transceiver (MMF) |
||
Gigabit Ethernet SFP, LC connector SX transceiver (MMF) |
||
Gigabit Ethernet SFP, LC connector LX/LH transceiver (SMF) |
||
Gigabit Ethernet SFP, LC connector LX/LH transceiver (SMF) |
||
100-Megabit Ethernet |
||
1000BASE-T SFP transceiver module with extended operating temperature range |
||
100BASE-FX SFP module for Gigabit Ethernet ports GLC-GE-100FX |
This section lists the new and changed features and includes the following topics:
Cisco NX-OS Release 6.0(2)A4(6) does not include new hardware.
All Cisco Nexus 3000 Series switches are supported by Cisco NX-OS Release 6.0(2)A4(6). 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. This release does not include any new software features.
■ Ensure that you use the install all command to upgrade the switch software from one Cisco NX-OS release to another.
■ If a custom CoPP policy is applied after upgrading to Cisco NX-OS Release 6.0(2)A1(1) or later, and if the Nexus 3548 switch is downgraded to Cisco NX-OS Release 5.0, where changes to the CoPP policy are not permitted, the custom CoPP policy is retained and cannot be modified.
The following are the known limitations for Cisco NX-OS Release 6.0(2)A4(6). See the appropriate bugs in the Cisco Bug Search Tool.
■ IGMP packets, which are filtered by report policies on the local switch on which IGMP filtering is enabled, will still get forwarded to the peer switch (See CSCup50141).
■ Counters for the warp SPAN destination port do not work. To check these counters, connect another switch to the destination ports (See CSCuq66372).
■ In a vPC setup, because of a hardware limitation, non-RPF traffic for (S,G) that comes in on the RPF interface for (*,G) hits the (*,G) entry instead of being treated as (S,G) non-RPF traffic and dropped. (S,G) non-RPF traffic is then incorrectly forwarded by (*,G) entry, thus causing traffic duplication. To avoid duplication of Layer 3 multicast traffic by sending the (S,G) RP-bit prune, run the ip pim pre-build-spt command (See CSCun34760).
■ While performing Online Insertion Removal (OIR) on the cable or optics of a 40G bundle, you must perform the following sequence of steps for the OIR to be successful (See CSCuq93225):
1. Disable (shut) the 40G port
2. Change the speed from 40G to 10G
3. Perform an OIR on the cable or optics
4. Change the speed from 10G to 40G
5. Re-enable (no shut) the port
The open and resolved bugs for this release are accessible through the Cisco Bug Search Tool. This web-based tool provides you with access to the Cisco bug tracking system, which maintains information about bugs and vulnerabilities in this product and other Cisco hardware and software products.
Note: You must have a Cisco.com account to log in and access the Cisco Bug Search Tool. if you do not have one, you can register for an account.
For more information about the Cisco Bug Search Tool, see the Bug Search Tool Help & FAQ.
■ Resolved Bugs in this Release
Table 3 lists descriptions of resolved bugs in Cisco NX-OS Release 6.0(2)A4(6). You can use the record ID to search Cisco Bug Search Tool for details about the bug.
Table 3 Cisco NX-OS Release 6.0(2)A4(6) – Resolved Bugs
Record Number |
Resolved Bug Headline |
Provide more options to control behavior if the Cisco Nexus 3500 shuts down all interfaces. |
|
After some time of normal operation, Nexus Data Broker (NDB) is suddenly no longer reachable through the GUI. |
|
The Cisco Nexus 3548 interface counter shows inconsistent values with steady traffic. |
|
BFD/HSRP traffic does not go through the CISCO Nexus 3548 switch because BFD echo packets are dropped due to a hardware limitation. |
|
The Cisco Nexus 3500 does not process the packets received on an access vPC port. This happens only when a dot1q header with VLAN id as 0 is received. |
|
This bug is to remove the hardware multicast hw-hash CLI command from the Nexus 3000/3500 releases. This command is not supported in these platforms. |
|
When a Nexus 3500, configured as hardware profile forwarding-mode warp, is upgraded from 6.0(2)A1(1) to 6.0(2)A3(1), it reverts back to hardware profile forwarding-mode normal and needs warp to be reconfigured. This takes another reload to fix. |
|
In the Nexus 3500 vPC setup, the switch drops ARP (reply) packets destined to the peer's physical MAC address. |
|
A Cisco Nexus 3548 router that is an intermediate router in a PIM sparse-mode network may send data packets toward the resource provider (RP) including when the RP is not part of the SPT. |
|
After some time of normal operation, Nexus Data Broker (NDB) is suddenly no longer reachable through the GUI. OpenFlow switches using the underlying XNC as a controller report a connection failure to the controller. |
|
The following log is displayed: %USER-2-SYSTEM_MSG: unknown enum 254 – vsh. |
|
When the buffer threshold is reached, the syslog is printed. However, when the threshold drops below the threshold, the syslog is not printed. |
|
The hardware profile buffer monitor cannot be seen in the running-config. |
|
The python shell and python functionality is broken in 6.0(2).A4(1) and later releases. |
|
The ERSPAN IP filter is matching traffic that is not source interface traffic. |
|
When a change is performed on one of the interfaces on a Cisco Nexus 3000, which affects PTP on the interface, it may affect PTP on other interfaces on the switch. |
|
Cisco Nexus 3000 does not properly encrypt the tacacs-server key. |
|
On a Nexus 3000, the /var/sysmgr is increasing in utilization over time. |
|
When a Cisco Nexus 3548 and IOS router (with any version) creates a BFD BGP neighbor, neighbor flapping was seen frequently. |
|
CoPP (including BFD) does not work after upgrading to 6.0(2)A6(1) or 6.0(2)A4(5) on N3500 platforms. |
|
When OpenFlow is configured to send traffic RXed on an interface out to a group of interfaces, this forwarding may not take place. |
|
After changing the transceiver from 1G to 10G, The Cisco Nexus 3548 does not send any packets. |
|
An MTC_USD process core occurs when active buffer monitor CLIs are issued. |
|
When a loopback interface address is configured as a rendezvous point, the PIM register message received from the FHR is not processed. This results in traffic loss to all downstream devices. |
|
OpenFlow programmed flows are not getting retained after reloading the switch. |
|
A kernel panic is observed on the Cisco Nexus 3548 6.0(2)A4(5) release. |
Table 4 lists descriptions of open bugs in Cisco NX-OS Release 6.0(2)A4(6). You can use the record ID to search the Cisco Bug Search Tool for details about the bug.
Table 4 Cisco NX-OS Release 6.0(2)A4(5) —Open Bugs
Record Number |
Open Bug Headline |
SFP insertion/removal limitation on Nexus 3548. |
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 3548 switch. The MIB Support List is available at the following FTP sites:
fftp://ftp.cisco.com/%2Fpub/mibs/supportlists/nexus3548/Nexus3548MIBSupportList.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
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.
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)
© 2015 Cisco Systems, Inc. All rights reserved.