Cisco Nexus 3000 Series NX-OS Release Notes, Release 9.3(6)

Cisco Nexus 3000 Series NX-OS Release Notes, Release 9.3(6)

This document describes the features, issues, and exceptions of Cisco NX-OS Release 9.3(6) software for use on Cisco Nexus 3000, 3100, 3200, 3400-S, 3500 and 3600 platform switches. For more information, see Related Content.

Note: The Cisco Nexus 34180YC and 3464C switches are not supported in Cisco NX-OS Release 9.3(6).

Note: 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.

Table 1: Online History Change

 

 

Contents

■      New Software Features

■      New Hardware Features

■      Release Versioning Strategy

■      Open Issues

■      Resolved Issues

■      Known Issues

■      Device Hardware

■      Upgrade and Downgrade

■      MIB Support

■      Exceptions

■      Supported Optics

■      Related Content

■      Documentation Feedback

■      Legal Information

 

 

New Software Features

Table 2: New Software Features

 

New Hardware Features

Cisco NX-OS Release 9.3(6) does not include any new hardware.

Release Versioning Strategy

Cisco Nexus 9000 Series switches and Cisco Nexus 3000 Series switches use the same NX-OS binary image also called the “unified" image. The binary image covers all the variations of the Cisco Nexus 3000 and 9000 series switches. Cisco NX-OS Release 9.2(1) was the first release that adopted unified version numbering. With unified version numbering, the platform designator is obsolete.

Moving forward for the previously identified platforms, we will be adopting the simplified 3-letter versioning scheme. For example, a release with X.Y(Z) would mean:

X – Unified release major

Y – Major / Minor release

Z – Maintenance release (MR)

Where the Z = 1 is always the first FCS release of a Major/Minor release.

An example of a previous release number is: 7.0(3)I7(4). In this format, the ‘I’ is the platform designator.

Note: In order to accommodate upgrade compatibility from an older software version that is expecting a platform designator, when the install all command is entered or the show install all impact command is entered, the version string appears as 9.3(6)I9(1). The “I9(1)” portion of the string can be safely ignored. It will later appear as 9.3(6).

Note: Cisco NX-OS Release 9.3(6) runs on all Cisco Nexus 3000 Series switches except the Cisco Nexus 34180YC and 3464C switches.

Open Issues

The following tables lists the open issues for Cisco Nexus 3000 Series switches in Cisco NX-OS Release 9.3(6). Click the Bug ID to search the Cisco Bug Search Tool for additional information about the bug.

■      Open Issues in Cisco Nexus 3000, 3100, 3200 and 3400-S Switches

■      Open Issues in Cisco Nexus 3500 Switches

Table 3: Open Issues in Cisco Nexus 3000, 3100, 3200 and 3400-S Series Switches

Resolved Issues

The following tables list the resolved issues for Cisco Nexus 3000 Series switches in Cisco NX-OS Release 9.3(6). Click the Bug ID to search the Cisco Bug Search Tool for additional information about the bug.

■      Resolved Issues in Cisco Nexus 3000, 3100, 3200 and 3400-S Switches

■      Resolved Issues in Cisco Nexus 3500 Switches

Table 4: Resolved Issues in Cisco Nexus 3000, 3100, 3200, and 3400-S Series Switches

 

Table 5: Resolved Issues in Cisco Nexus 3500 Series Switches

 

 

Known Issues

The following tables lists the known behaviors in Cisco Nexus 3000 Series switches in Cisco NX-OS Release 9.3(6). Click the bug ID to search the Cisco Bug Search Tool  for details about the bug.

Table 6: Known Behaviors in Cisco Nexus 3000 and 3100 Series Switches

 

Large core files are split into 3 or more files. For example:

■      1405964207_0x101_iftmc_log.3679.tar.gzaa

■      1405964207_0x101_iftmc_log.3679.tar.gzab

■      1405964207_0x101_iftmc_log.3679.tar.gzac

 

To decode the multiple core files, first club the files to a single file:

$ cat 1405964207_0x101_iftmc_log.3679.tar.gz* > 1405964207_0x101_iftmc_log.3679.tar.gz

Table 7: Known Behaviors in Cisco Nexus 3500 Series Switches

 

 

Device Hardware

The following tables list the Cisco Nexus 3000 Series hardware that Cisco NX-OS Release 9.3(6) supports. For additional information about the supported hardware, see the Hardware Installation Guide for your Cisco Nexus 3000 Series devices.

 

■      Cisco Nexus 3000 and 3100 Series Switches

■      Cisco Nexus 3000 and 3100 Series fans and fan trays and Power Supplies

■      Cisco Nexus 3200 Series Switches

■      Cisco Nexus 3400-S Series Switches

■      Cisco Nexus 3500 Series Switches

■      Cisco Nexus 3500 Series fans and fan trays, and Power Supplies

■      Cisco Nexus 3600 Series Switches

 

Table 8: Cisco Nexus 3000 and 3100 Series Switches

 

Table 9: Cisco Nexus 3000 and 3100 Series Fans, Fan Trays and Power Supplies

 

Table 10: Cisco Nexus 3200 Series Switches

 

Table 11: Cisco Nexus 3400-S Series Switches

 

Table 12: Cisco Nexus 3500 Series Switches

 

Table 13: Cisco Nexus 3500 Series Fans, Fan Trays and Power Supplies

 

 

Table 14: Cisco Nexus 3600 Series Switches

 

Upgrade and Downgrade

Upgrading Cisco Nexus 3000 and 3100 Series Switches

To perform a software upgrade for Cisco Nexus 3000 and 3100 Series switches that run in N3K mode, follow the instructions in the Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.3(x).

To perform a software upgrade for Cisco Nexus 3100 Series switches that run in N9K mode, follow the instructions in the Cisco Nexus 9000 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.3(x).

This section includes the following topics:

■      Upgrade Path to Cisco NX-OS Release 9.3(6)

■      Guidelines and Limitations - Upgrade

Upgrade Path to Cisco NX-OS Release 9.3(6)

For the list of platforms and releases that support a non-disruptive In-Service Software Upgrade (ISSU) to Cisco NX-OS Release 9.3(6), see the Cisco NX-OS ISSU Support Matrix.

The following disruptive upgrade paths are supported:

·       For Cisco Nexus 3000 and 3100 Series switches (except Cisco Nexus 3048, 3132C-Z, 3164Q, 31128PQ, and 3100-V switches), use one of the two following upgrade paths:

·       Release 6.0(2)U5(1) -> Release 6.0(2)U6(10) -> Release 7.0(3)I7(8) -> Release 9.3(6)

·       Release 9.2(1) -> Release 9.2(4) -> Release 9.3(6)

 

·       For Cisco Nexus 3048 switches, use one of the two following upgrade paths:

·       Release 6.0(2)U5(1) -> Release 6.0(2)U6(10) -> Release 7.0(3)I7(8) -> Release 9.3(6)

·       Release 9.2(1) -> Release 9.2(4) -> Release 9.3(6)

 

·       For Cisco Nexus 3132C-Z Series switches:

Release 9.2(2) or later -> Release 9.3(6)

·       For Cisco Nexus 3164Q, 31128PQ, and 3100-V switches:

Release 7.0(3)I2(1) or later -> Release 9.3(6)

 

·       For Cisco Nexus 3264C-E switches:

Release 9.2(1) -> Release 9.3(6)

 

Upgrade Guidelines and Limitations

The following guidelines and limitations are applicable when you upgrade to Cisco NX-OS Release 9.3(6):

■      Cisco Nexus 3048, 3064, 3132 (except for the N3K-C3132Q-V), and 3172 platform switches with a model number that does not end in -XL must run a “compact” NX-OS software image due to limited bootflash space. This “compact” image can be created using the NX-OS Compact Image procedure; alternatively, a compact NX-OS software image can be downloaded directly from Cisco's Software Download website. This requirement does not apply to any other model of Cisco Nexus 3000 or 3100 series switch. This requirement does not apply to the Nexus 3132Q-V switch.

■      The MD5/SHA512 checksum published on Cisco's Software Download website for a compact NX-OS software image may not match the MD5/SHA512 checksum of a compact image created through the NX-OS Compact Image procedure.

■      The only supported method of upgrading is install all from Release 6.0(2)U6(3a) or later due to the need to upgrade the BIOS. Without the Release 9.3(6) BIOS, the 9.3(2) image will not load.

■      While performing a non-disruptive ISSU, VRRP and VRRPV3 will display the following messages:

·       If VRRPV3 is enabled:

2015 Dec 29 20:41:44 MDP-N9K-6 %$ VDC-1 %$ %USER-0-SYSTEM_MSG: ISSU ERROR: Service "vrrpv3" has sent the following message: Feature vrrpv3 is configured. User can change vrrpv3 timers to 120 seconds or fine tune these timers based on upgrade time on all Vrrp Peers to avoid Vrrp State transitions. – sysmgr

·       If VRRP is enabled:

2015 Dec 29 20:45:10 MDP-N9K-6 %$ VDC-1 %$ %USER-0-SYSTEM_MSG: ISSU ERROR: Service "vrrp-eng" has sent the following message: Feature vrrp is configured. User can change vrrp timers to 120 seconds or fine tune these timers based on upgrade time on all Vrrp Peers to avoid Vrrp State transitions. – sysmgr

■      Change the port mode from oversubscribed to line-rate and then reload the switch:

§  On Nexus 31108PC-V and 31108TC-V switches, change from 48x10g+6x100g to 48x10g+4x100g+2x40g.

§  On Nexus 3132Q-V switches change from 32x40g or 26x40g to 24x40g.

■       Change the switching-mode from cut-through to store-and-forward and then reload the switch.

■      An error occurs when you try to perform an ISSU if you changed the reserved VLAN without entering the copy running-config save-config and reload commands.

■      Subinterfaces cannot be used as network ports.

§  Cisco Nexus 3000-XL platforms do not support breakout using speed 10000 CLI command. Use the interface breakout module 1 port <num> map 10g-4x CLI command instead.

§  Chunking is enabled while displaying XML output for any CLI, and html tags (& lt; and & gt;) are displayed instead of < and > both on the sandbox and while running the Python script (See CSCup84801).

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

■      If you use the write erase command, you cannot view the output for the show startup feature command. To view the startup configuration, you must then use the show startup-config command. This limitation will remain until you run the copy running-config startup-config command. After that, the show startup-config feature command will display the feature-only configuration output as expected (See CSCuq15638).

■      A Python traceback is seen while running the show xml command by using the Python shell. The exception type is httplib.IncompleteRead. This happens when you use Python scripts to leverage the NXAPI for retrieving switch data through XML or JSON. You should handle the exceptions in your Python scripts (See CSCuq19257).

■      While upgrading to a new release, when you create a checkpoint without running the setup script, the checkpoint file does not contain the copp-s-mpls class. After you run the write erase command and reload the switch, the copp-s-mpls class is created when the default configuration is applied. When a rollback is done to this checkpoint file, it detects a change in the CoPP policy and tries to delete all class-maps. Because you cannot delete static class-maps, this operation fails, and, in turn, the rollback also fails.

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.

 

■      When both the ip icmp-errors source and ip source intf icmp error commands are configured, then the command that is configured last takes effect.

Thereafter, if the last configured command is removed, the switch does not get configured with the command that was configured first.

■      Users who upgrade to 9.3(2) need to run the set-up script if they want to enable the MPLS static or the VRRpv3 feature.

■      The following Cisco Nexus 9000 features are not supported on the Cisco Nexus 3100 Series switches in N3K or N9K mode:

·       FEX

·       Multicast PIM Bidir

·       Port VLAN (PV) switching and routing support for VXLAN

·       Auto-Config

·       Secure login enhancements:

·   Ability to block login attempts and enforce a quiet period

·   Ability to restrict the maximum login sessions per user

·   Ability to restrict the password length

·   Ability to prompt the user to enter a password after entering the username

·   Ability to hide the shared secret used for RADIUS or TACACS+ authentication or accounting

·   SHA256 hashing support for encrypted passwords

·       SHA256 algorithm to verify operating system integrity

·       Non-hierarchical routing mode

·       NX-API REST

■      Link Level Flow Control (LLFC) is not supported on Cisco Nexus 3000 series and Cisco Nexus 3100 series switches.

■      You can disable IGMP snooping either globally or for a specific VLAN.

■      You cannot disable IGMP snooping on a PIM enabled SVIs. The warning message displayed is: IGMP snooping cannot be disabled on a PIM enabled SVIs. There are one or more VLANs with PIM enabled.

■      The Cisco Nexus 3000 Series switches (non-XL platforms, having 4 GB RAM) cannot tftpboot non-compacted 9.3(2) software image from the loader prompt. Hence, you must keep one working image in the bootflash. Tftp of non-compacted can be supported only on the Cisco Nexus Series switches having 8 GB or more RAM (XL platform).

■      Enhanced ISSU to Cisco NX-OS Release 9.3(6) is not supported.

■      The following switches do not support an ISSU (nondisruptive upgrade) to Cisco NX-OS Release 9.3(6):

·       3016Q

·       3048TP

·       3064PQ, 3064PQ-E, 3064PQ-X, and 3064TQ

·       3132Q, 3132Q-X, 3172PQ, and 3172TQ

■      Before performing an ISSU to Cisco NX-OS Release 9.3(6), you must configure the BGP graceful restart timer to 180 seconds for Cisco Nexus 3132Q-XL, 3132Q-V, 3172PQ-XL, 3172TQ-XL, N3K-C3232C, and N3K-C3264Q-S platform switches.

■      If you downgrade the Cisco Nexus device from Cisco NX-OS Release 9.3(6) to the previous NX-OS releases by setting the boot variables and reloading the switch, all earlier configurations of the segment-routing mpls will be lost.

Upgrading Cisco Nexus 3200 and 3400-S Series Switches

To perform a software upgrade, follow the instructions in the Cisco Nexus 3400-S Series NX-OS Software Upgrade and Downgrade Guide, Release 9.3(x).

Upgrade Path to Cisco NX-OS Release 9.3(6)

For the list of platforms and releases that support a non-disruptive In-Service Software Upgrade (ISSU) to Cisco NX-OS Release 9.3(6), see the Cisco NX-OS ISSU Support Matrix.

The following disruptive upgrade paths are supported:

§  For Cisco Nexus 3232C and 3264Q switches:

                                  Release 7.0(3)I3(1) or later -> Release 9.3(6)

§  For Cisco Nexus 3264C-E switches:

                                  Release 9.2(1) or 9.2(2) -> Release 9.3(6)

§  For Cisco Nexus 3408-S and 3432D-S switches:

    Release 9.2(2t) to 9.2(2v) -> Release 9.3(6)

  Release 9.2(2v) -> Release 9.3(6)

 

Upgrading Cisco Nexus 3500 Series Switches

To perform a software upgrade, follow the instructions in the Cisco Nexus 3500 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.3(x). This section includes the following topics:

■      Upgrade Path to Cisco NX-OS Release 9.3(6)

■      Guidelines and Limitations - Upgrade

Upgrade Path to Cisco NX-OS Release 9.3(6)

The following disruptive upgrade paths are supported for the XL platforms:

§  Release 7.0(3)I7(2) or later -> Release 7.0(3)I7(8) -> Release 9.3(6)

§  Release 9.2(1) -> Release 9.2(4) -> Release 9.3(6)

 

The following disruptive upgrade paths are supported for the non-XL platforms:

·       Release 6.0(2)A8(2) or later -> Release 6.0(2)A8(7b) or later -> Release 7.0(3)I7(8) or later -> 9.3(6)

·       Release 6.0(2)A8(2) or later -> Release 6.0(2)A8(7b) or later -> Release 9.2(4) or later -> 9.3(6)

·       Release 6.0(2)A7(2a) or earlier -> Release 6.0(2)A8(9) -> Release 7.0(3)I7(8) or later -> Release 9.3(6)

·       Release 6.0(2)A7(2a) or earlier - > Release 6.0(2)A8(7b) or later -> Release 9.2(4) or later -> 9.3(6)

Upgrade Guidelines and Limitations

The following guidelines and limitations are applicable when you upgrade from Cisco NX-OS Release 7.0(3)I7(2) or later to Cisco NX-OS Release 9.3(6):

■      If a custom CoPP policy is applied after upgrading to Cisco NX-OS Release 7.0(3)I7(2) 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.

■      copy r s and reload is not a supported method for an upgrade.

■      You must run the setup script after you upgrade to Cisco NX-OS Release 9.3(6).

■      Cisco Nexus 3548 and 3548-X platform switches must run a “compact” NX-OS software image due to limited bootflash space. This “compact” image can be created using the NX-OS Compact Image procedure; alternatively, a compact NX-OS software image can be downloaded directly from Cisco's Software Download website. This requirement does not apply to the Cisco Nexus 3548-XL switch.

■      The MD5/SHA512 checksum published on Cisco's Software Download website for a compact NX-OS software image may not match the MD5/SHA512 checksum of a compact image created through the NX-OS Compact Image procedure.

■      install all is the only upgrade method supported because of a BIOS upgrade requirement.

■      The following limitations are applicable when you upgrade from Cisco NX-OS Release 6.0(2)A8(7b), 6.0(2)A8(8), or 6.0(2)A8(9) to Cisco NX-OS Release 9.3(6):

o    If Cisco Catalyst devices are connected via a vPC to a pair of Nexus 3500 switches with the vPC peer switch feature enabled, a partial or complete network outage may be caused as a result of the Cisco Catalyst devices error-disabling their port-channel interfaces due to EtherChannel Guard. To prevent this from happening, we recommend that you temporarily disable the EtherChannel Guard feature on vPC-connected Cisco Catalyst devices while the Nexus 3500 devices are being upgraded. For more information, see CSCvt02249.

 

Upgrading Cisco Nexus 3600 Series Switches

To perform a software upgrade, follow the instructions in the Cisco Nexus 3600 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.3(x).

Upgrade Path to Cisco NX-OS Release 9.3(6)

The following disruptive upgrade paths are supported:

■      Release 9.2(1) or 9.2(2)-> Release 9.3(6)

■      Release 7.0(3)F3(4) -> Release 9.3(6)*

■      Release 7.0(3)F3(3c) -> Release 9.3(6)*

■      Release 7.0(3)F3(3) -> Release 7.0(3)F3(4) -> Release 9.3(6)*

* These upgrade paths require write erase and reload.

MIB Support

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

Exceptions

The following features are not supported for the Cisco Nexus 3232C and 3264Q switches:

■      3264Q and 3232C platforms do not support the PXE boot of the NX-OS image from the loader.

■      Automatic negotiation support for 25-Gb and 50-Gb ports on the Cisco Nexus 3232C switch.

■      Cisco Nexus 2000 Series Fabric Extenders (FEX)

■      Cisco NX-OS to ACI conversion (The Cisco Nexus 3232C and 3264Q switches operate only in Cisco NX-OS mode.)

■      DCBXP

■      Designated router delay

■      DHCP subnet broadcast is not supported

■      Due to a Poodle vulnerability, SSLv3 is no longer supported

■      Enhanced ISSU. NOTE: Check the appropriate guide to determine which platforms support Enhanced ISSU.

■      FCoE NPV

■      Intelligent Traffic Director (ITD)

■      MLD

■      NetFlow

■      PIM6

■      Policy-based routing (PBR)

■      Resilient hashing

■      SPAN on CPU as destination

■      Virtual port channel (vPC) peering between Cisco Nexus 3232C or 3264Q switches and Cisco Nexus 9300 platform switches or between Cisco Nexus 3232C or 3264Q switches and Cisco Nexus 3100 Series switches

■      VXLAN IGMP snooping

Supported Optics

To determine which transceivers and cables are supported by Cisco Nexus 3000 Series switches, see the Transceiver Module (TMG) Compatibility Matrix.

To see the transceiver specifications and installation information, see https://www.cisco.com/c/en/us/support/interfaces-modules/transceiver-modules/products-installation-guides-list.html.

 

Related Content

Cisco Nexus 3000 Series documentation: Cisco Nexus 3000 Series switch documentation

Cisco Nexus 3000 and 9000 Series NX-API REST SDK User Guide and API Reference: Cisco Nexus 3000 and 9000 Series NX-API REST SDK User Guide and API Reference

Cisco Nexus OpenConfig YANG Reference, Release 9.3(x): Cisco Nexus OpenConfig YANG, Release 9.3(x)

Licensing information:

Cisco NX-OS Licensing Guide

Cisco Nexus 9000 and 3000 Series NX-OS Switch License Navigator

 

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.

Legal Information

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)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2021 Cisco Systems, Inc. All rights reserved.