Cisco Nexus 3000 Series NX-OS Release Notes, Release 6.0(2)U4(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
Support for XML and JSON Output
DHCP Client Discovery with IPv6
Statistics Collection on Interfaces
Support for In-band or Out-band Addresses as Source IP Address
Cisco Plug-in for OpenFlow Release 1.1.5
Upgrade and Downgrade Guidelines
Upgrade Path to Release 6.0(2)U4(1)
Resolved Caveats in Cisco NX-OS Release 6.0(2)U4(1)
Open Caveats in Cisco NX-OS Release 6.0(2)U4(1)
Known Behaviors in Cisco NX-OS Release 6.0(2)U4(1)
Obtaining Documentation and Submitting a Service Request
Release Date: September 18, 2014
Current Release: Cisco NX-OS Release 6.0(2)U4(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.
Added the following note: 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. |
||
Removed bug Id (CSCuq92481) from “Limitations”. |
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(2), the Cisco Nexus 3100 Series includes the Cisco Nexus 3132 and Nexus 3172 switches.
The Cisco Nexus 3172PQ switch is a 10-Gbps Enhanced Small Form-Factor Pluggable (SFP+)–based ToR switch with 48 SFP+ ports and 6 Enhanced Quad SFP+ (QSFP+) ports.
The Cisco Nexus 3172TQ switch is a 10GBASE-T switch with 48 10GBASE-T ports and 6 Quad SFP+ (QSFP+) ports.
Each SFP+ port can operate in 100-Mbps, 1-Gbps, or 10-Gbps mode, and each QSFP+ port can operate in native 40-Gbps or 4 x 10-Gbps mode. This switch is a true physical-layer-free (phy-less) switch that is optimized for low latency and low power consumption.
The Cisco Nexus 3132Q 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 3100 Series, see the Cisco Nexus 3000 Series Hardware Installation Guide.
This section includes the following topics:
Cisco NX-OS Release 6.0(2)U4(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
|
||||
---|---|---|---|---|
40GBASE-CR4 QSFP+ direct-attach copper cable, 7 meters active |
||||
40GBASE-CR4 QSFP+ direct-attach copper cable, 8 meters active |
||||
40GBASE-CR4 QSFP+ direct-attach copper cable, 9 meters active |
||||
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) |
||||
Cisco QSFP to SFP/SFP+ Adapter (QSA) module with 10GBASE-DWDM |
||||
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-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-SX-MMD6 |
||||
GLC-BX-D 4 |
||||
GLC-BX-U 4 |
||||
GLC-LH-SM 4 |
||||
GLC-LH-SMD 4 |
||||
GLC-SX-MM 3 |
||||
GLC-SX-MMD 5 |
||||
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)U4(1). This section includes the following topics:
Cisco NX-OS Release 6.0(2)U4(1) supports the new hardware listed in this section.
The Cisco Nexus 3132Q-X switch has the following hardware specifications:
All Cisco Nexus 3000 Series switches are supported by Cisco NX-OS Release 6.0(2)U4(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)U4(1) includes the following new software features:
With the introduction of RFC 5549 in Cisco NX-OS Release 6.0(2)U4(1), you can configure an IPv4 address family for a neighbor with an IPv6 address.
On Cisco Nexus devices, command-line interfaces (CLIs) are run only on the device. NX-API improves the accessibility of these CLIs by making them available outside of the switch by using HTTP/HTTPS. You can use this extension to the existing Cisco Nexus CLI system on the Cisco Nexus 3000 Series devices. NX-API supports show commands, configurations, and Linux Bash.
Cisco NX-OS Release 6.0(2)U4(1) introduces support for XML and JSON output for several commands. See the Cisco Nexus 3000 Series NX-OS Programmability Guide for a complete list of supported commands.
Cisco NX-OS Release 6.0(2)U4(1) introduces the show queuing command to display the queuing information configured for all interfaces. It includes shaper configuration information for each class, the control queue Tx and drop statistics for each port, and WRED drop packet counts. This release also supports the output of this command in XML.
Starting with Cisco NX-OS Release 6.0(2)U4(1), Cisco Nexus 3000 Series switches support Python version 2.7.5
This release also introduces protection for Cisco NX-OS resources through the Cisco NX-OS Sandbox layer of software and through the CLI role-based access control (RBAC).
You can now configure the IPv4 or IPv6 address of a DHCP client on a management interface, or a physical Ethernet interface.
You can use the load-interval command to obtain bit-rate and packet-rate statistics for three different durations.
You can set the statistics collection intervals on the following types of interfaces:
This command sets the sampling interval for such statistics as packet rate and bit rate on the specified interface.
You can use the show interface brief command to display a brief summary of the interface configuration information.
The following enhancements were made to BGP:
Cisco NX-OS Release 6.0(2)U4(1) supports the following copy command enhancements:
Cisco NX-OS Release 6.0(2)U4(1) introduces support for two TLVs, IPv4 and IPv6.
You can explicitly specify the management IPv4 or IPv6 address to be sent in the LLDP management TLV. This address can be one of the following:
Beginning with Cisco NX-OS Release 6.0(2)U4(1), BGP allows an IPv4 prefix to be carried over an IPv6 next-hop. The IPv6 next-hop is leveraged to remove neighbor discovery (ND) related traffic from the network. To do this, the MAC address is embedded in the IPv6 address. Such an address is called a MAC Embedded IPv6 (MEv6) address.
Cisco NX-OS Release 6.0(2)U4(1) allows you to enable BGP graceful restarts (GR) with fast reboot. You can now use the fast-reload trigger-gr command to enable BGP GR. Use this command only when all BGP peers are GR-capable.
This release also supports the use of non-interruptive fast reboot. You can now use the fast-reload non-interruptive command to run fast-reload without any prompts.
Beginning with Cisco NX-OS Release 6.0(2)U4(1), you can bypass password and basic POAP configuration by using the skip option at the POAP prompt.
When you use the skip option, no password will be configured for the admin user. The copy running-config startup-config command will be blocked until a valid password is set for the admin user.
You can now filter out the IPv6 packets that are captured by using the ethanalyzer local interface inbound-low capture-filter “ip6” command.
The configuration synchronization (config-sync) feature allows you to configure one switch profile and have the configuration be automatically synchronized to the peer switch.
You can configure the source interface to be used with the following:
In addition to the NX-OS CLI, Cisco Nexus 3000 Series switches support access to the Bourne-Again SHell (Bash). Bash interprets commands that you enter or commands that are read from a shell script. Using Bash enables access to the underlying Linux system on the switch and to manage the system.
Cisco NX-OS Release 6.0(2)U4(1) supports Cisco Plug-in Version 1.1.5 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) and OpenFlow Switch Specification Version 1.3.0 (Wire Protocol 0x04).
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 OpenFlow Switch Specification Version 1.3.0. This release also includes the following enhancements:
This command configures the protocol version. The supported values for version-info are:
– 1.0—Configures device to connect to 1.0 controllers only
– 1.3—Configures device to connect to 1.3 controllers only
– negotiate—Negotiates the protocol version with the controller. The device uses 1.3 for negotiation.
The default value is negotiate.
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)U4(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.
In Cisco NX-OS Release 6.0(2)U2(2), the default interface name in LLDP MIB is in short form. To make it long form, you must set lldp portid-subtype to 1. In Cisco NX-OS Release 6.0(2)U2(3), this behavior was reversed. The default interface name in LLDP MIB is now in long form. To make it short form, you must set lldp portid-subtype to 0.
If you have set lldp port-subtype to 1 and you are upgrading to Cisco NX-OS Release 6.0(2)U2(4), ensure that you set lldp port-subtype to 0.
The following are the known limitations for Cisco NX-OS Release 6.0(2)U4(1):
This is expected behavior. Each chunk should be in XML format for you to parse it and extract everything inside the <body> tag. This is done so that it can be later concatenated with similar output from all the chunks of the CLI XML output. After all the chunks are concatenated to get the complete XML output for the CLI, this complete XML output can be parsed for any parameter.
The following workaround is recommended to address this issue:
– Concatenate the <body> outputs from each chunk
– Replace all the html tags (& lt; and & gt;) with < and >
– Parse for any XML tag needed
This can also happen if you create a checkpoint, then create a new user-defined class and insert the new class before any other existing class (See CSCup56505).
The following workarounds are recommended to address this issue:
– Run setup after upgrading to a new release.
– Always insert the new classes at the end before a rollback.
– Any trunk port in the VLAN is treated as an IGMP snooping Active Port.
– Access ports in the VLAN are not treated as IGMP snooping Active ports.
– The FWM multicast flood-list for VLAN contains all trunk ports and mrouter ports.
The following workarounds are recommended to address this issue:
– Use the show ip igmp snooping vlan x command to see the Active Ports.
– Use the show platform fwm info vlan x command to see the flood-list.
Thereafter, if the last configured command is removed, the switch does not get configured with the command that was configured first.
1405964207_0x101_fwm_log.3679.tar.gzaa
1405964207_0x101_fwm_log.3679.tar.gzab
1405964207_0x101_fwm_log.3679.tar.gzac
As a workaround, the following UNIX command combines the files into a single file:
cat 1405964207_0x101_fwm_log.3679.tar.gz* > 1405964207_0x101_fwm_log.3679.tar.gz
Subsequently,.tar.gz can be used as a normal core tar ball file.
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)U4(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)U4(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)U4(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 following 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.