Cisco Nexus 3000 Series NX-OS Release Notes, Release 9.3(3)
This document describes the features, issues, and limitations of Cisco NX-OS Release 9.3(3) software for use on Cisco Nexus 3000, 3100, 3200, 3400-S, 3500 and 3600 switches. For more information, see Related Documentation.
Note: The Cisco Nexus 34180YC and 3464C platform switches are not supported in Cisco NX-OS Release 9.3(3).
Table 1: Online History Change
Date |
Description |
October 19, 2020 |
Updated the Upgrading Cisco Nexus 3000 Series Switches section. |
March 13, 2020 |
Updated upgrade path section to reflect the limitations of CSCvt02249. |
Dec 23, 2019 |
Created the release note for Release 9.3(3). |
■ Obtaining Documentation and Submitting a Service Request
Table 2: New Software Features
Feature |
Description |
802.1x |
Introduced this feature for Cisco Nexus 3548 Series switches.
For more details, see the Cisco Nexus 3000 Series NX-OS Security Configuration Guide, Release 9.3(x). |
ACL – Consistency Checker for BRCM Platforms: |
Added support for the following platforms: § N3K-C3016Q-40GE § N3K-C3048TP-1GE § N3K-C3064PQ-10GE § N3K-C3064PQ-10GX § N3K-C3064T-10GT § N3K-C3132C-Z For more details, see the Cisco Nexus 3000 Series NX-OS Security Configuration Guide, Release 9.3(x). |
BFD for BGP Dynamic Peers (IPv4/IPv6) |
Added BFD support for BGP IPv4 and IPv6 prefix peers for all Cisco Nexus 3000 Series switches. For more details, see the Cisco Nexus 3000 Series NX-OS Unicast Routing Configuration Guide, 9.3(x) |
Buffer Drop Capture |
Added support for the Buffer Drop Capture.
For more details, see the Cisco Nexus 3400-S Series NX-OS Programmability Guide, Release 9.3(3). |
Buffer Latency Capture |
Added support for the Buffer Latency Capture.
For more details, see the Cisco Nexus 3400-S Series NX-OS Programmability Guide, Release 9.3(3). |
BGP Attribute Filtering and Enhanced Error handling |
Added the ability to configure the following BGP attribute features for all Cisco Nexus 3000 Series switches in order to provide an increased level of security: § Path attribute treat-as-withdraw: Allows you to treat-as-withdraw a BGP update from a specific neighbor if the update contains a specified attribute type. The prefixes contained in the update are removed from the routing table. § Path attribute discard: Allows you to remove specific path attributes in a BGP update from a specific neighbor. Enhanced attribute error handling: Prevents peer sessions from flapping due to a malformed update.
For more details, see the Cisco Nexus 3000 Series NX-OS Unicast Routing Configuration Guide, 9.3(x) |
BGP Graceful Restart |
Added graceful restart support and the ability to configure a timeout value for BGP prefix peers using the timers prefix-peer-timeout command.
For more details, see the Cisco Nexus 3000 Series NX-OS Unicast Routing Configuration Guide, 9.3(x) |
Unnumbered BGP with IPv6 Link-local peering (5549) for EBGP |
Introduced this feature for all Cisco Nexus 3000 Series switches. This feature enables you to set up BGP sessions using an interface name as a BGP peer (rather than IP addresses).
For more details, see the Cisco Nexus 3000 Series NX-OS Unicast Routing Configuration Guide, 9.3(x) |
Breakout Modes Support |
Added support for breakout modes in Cisco Nexus 3600 switches with N3K-C3636C-R and N3K-C36180YC-R line cards.
For more details, see the Cisco Nexus 3600 Series NX-OS Interfaces Configuration Guide, Release 9.3(x) |
Cisco Nexus 3500 Consistency Checker Commands |
Added support for Layer 2 and Layer 3 consistency checker support for unicast and multicast routes.
For more details, see the Cisco Nexus 3548 Switch NX-OS Multicast Routing Configuration Guide, Release 9.3(x) |
Consistency Checker Enhancements |
Added VXLAN consistency checker commands.
For more details, see the Cisco Nexus 9000 Series NX-OS Troubleshooting Guide, Release 9.3(x).
|
ECMP Resilient Hashing |
Added support for the following platforms: § N3K-C3164Q § N3K-C31108PC-V, N3K-C31108TC-V, N3K-C3132Q-V § N3K-C3264C-E For more details, see the Cisco Nexus 3000 Series NX-OS Interfaces Configuration Guide, Release 9.3(x) |
Extended Event Log Storage |
Introduced support for extended on-switch and off-switch event logging file storage. For more details, see the following guides: · Cisco Nexus 3000 Series NX-OS System Management Configuration Guide, Release 9.3(x) · Cisco Nexus 3400-S NX-OS System Management Configuration Guide 9.3(x) · Cisco Nexus 3548 Switch NX-OS System Management Configuration Guide, Release 9.3(x) · Cisco Nexus 3600 NX-OS System Management Configuration Guide, Release 9.3(x) |
VXLAN TRM |
Layer 3 Tenant Routed Multicast (TRM) is added for the Cisco Nexus 3132C-Z switches.
For more details, see the Cisco Nexus 3600 NX-OS VXLAN Configuration Guide, Release 9.3(x). |
Multicast Virtual Private Networks (MVPNs) |
Introduced this feature for Cisco Nexus 3600 platform switches.
For more details, see Cisco Nexus 3600 NX-OS Label Switching Configuration Guide, Release 9.3(x) |
N3K-STR2K9 license |
Added support for the Cisco Nexus 3408-S and 3432D-S platform switches.
For more details, see Cisco NX-OS Licensing Guide. |
Native 50G Speed |
Added support for native 50G speed on Cisco Nexus 3432D-S switches.
For more details, see the Cisco Nexus 3400-S NX-OS Interfaces Configuration Guide, Release 9.2(2). |
NX-OS Advantage license |
Added support for the Cisco Nexus 3132Q (excluding the 3132Q-40GE), 3172, 3172PQ, 3172TQ, 31128PQ, 3100-V, 3232C, 3264Q, 3548, 3548-CR, and 3548-XL switches.
For more information, see Cisco NX-OS Licensing Guide. |
Smart Software Licensing |
Introduced smart licenses for all Cisco Nexus 3000 Series switches except the Cisco Nexus 3016 and 3064 platform switches. Smart Software Licensing is a cloud-based licensing end-to-end platform that consists of tools and processes that authorize the usage and reporting of Cisco products. This feature captures order information and communicates with the Cisco Cloud License Service through the Smart Call Home transport media to complete product registration and authorization. In the Smart Software Licensing model, you can activate licensed products without the use of a special software key or upgrade license file.
For more details, see Cisco NX-OS Licensing Guide. |
SSX Counters |
Added support for the SSX Counters.
For more details, see the Cisco Nexus 3400-S Series NX-OS Programmability Guide, Release 9.3(3). |
Cisco NX-OS Release 9.3(3) does not include any new hardware.
Cisco Nexus 9000 Series switches and the Cisco Nexus 3000 Series switches use the same NX-OS binary image also called the “unified" image. The binary image covers the Cisco Nexus 9300 and 9500 and Cisco Nexus 3100, 3200, 3400-S, 3500, and 3600 platform 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(3)I9(1). The “I9(1)” portion of the string can be safely ignored. It will later appear as 9.3(3).
Note: Cisco NX-OS Release 9.3(3) is the first release that runs on all Cisco Nexus 3000 Series switches, including the Cisco Nexus 3400-S platform switches. The Cisco Nexus 34180YC and 3464C platform switches are not supported in Cisco NX-OS Release 9.3(3).
The following tables lists the Open Issues in Cisco Nexus 3000, 3100, 3200, 3400-S, 3500 and 3600 Series switches in Cisco NX-OS Release 9.3(3). 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
■ Open Issues in Cisco Nexus 3600 Switches
Table 3: Open Issues in Cisco Nexus 3000, 3100, 3200 and 3400-S Series Switches
Bug ID |
Description |
Headline: Installation of N3K-LAN2K9 license on Nexus 3264C-E and Nexus 3464C switches, but the LAN features work. Symptom: Installation of N3K-LAN2K9 license on Nexus 3264C-E and Nexus 3464C switches, but the LAN features work. Workaround: LAN license N3K-LAN2K9 on N3K-C3264C-E and N3K-C3464C will see an error when installing this license (please add the error message here). LAN features will still work. |
|
Headline: Installation of N3K-STR1K9 on Nexus 34180YC and Nexus 3132C-Z fails, but the telemetry features work. Symptom: Installation of N3K-STR1K9 on Nexus 34180YC and Nexus 3132C-Z fails, but the telemetry features work. Workaround: License installation fails, telemetry features will work. |
|
Headline: N3K-C3408-S: Delayed linkup observed with 100g CR4 on Portflap/OiR. Symptoms: CR4 copper 100G cables sometimes, may experience higher link up times when connected between N3K-C3408-S and N9K Switches. Link up time varies depending upon different Peers. This happens only when auto-negotiation is enabled. The issue may or may not be seen across all the ports. Workarounds: Disable auto-negotiation and apply force speed. |
Table 5: Open Issues in Cisco Nexus 3600 Series Switches
Bug ID |
Description |
|
Headline: FCS error or link flap on N3K-C3636C-R with QSFP-100G-CU3M and QSFP-100G40G-BIDI in same BV. Symptom: 10 FCS error in a 12-hour period on the port with copper cable. Workaround: Split cables across different port mappings. |
Headline: During boot up, the device or QSFP-100G may show an extra interface link reset. Symptom: Traffic outage. Workaround: None. |
|
Headline: Traffic outage when switching 4x25G --> 2x50G --> 4x25G soft-breakout.
Symptom: This problem is seen only when the following transition occurs: 4x25G --> 2x50G --> 4x25G. Workaround: Reload the module. |
The following tables list the Resolved Issues in Cisco Nexus 3000, 3100, 3200, 3400-S, 3500 and 3600 Series switches in Cisco NX-OS Release 9.3(3). 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
■ Resolved Issues in Cisco Nexus 3600 Switches
Table 6: Resolved Issues in Cisco Nexus 3000, 3100, 3200, and 3400-S Series Switches
Bug ID |
Description |
Headline: Cisco Nexus 3100-V Series switch Buffer Wedge/Lockup: All Control-Plane Protocols Failing & Ports Unable to Pass Traffic Symptom: A Cisco Nexus 3100-V Series switch may experience a condition in which the ingress/egress buffers become "stuck" (unable to dequeue frames). This will lead to a condition where, depending on the specific queue experiencing the issue, all traffic may fail to pass in or out of the devices. Common symptoms will be failure of all control-plane protocols, input or output discards on multiple/all interfaces, RewriteEngineLoopback diagnostic failure, and low to near-zero ingress/egress utilization on impacted interfaces. Workaround: Reload the impacted device. |
|
Headline: Cisco Nexus 3000 upgrade to 7.0(3)i7(7) drops to switch boot after reloading for an upgrade. Symptom: When upgrading with a compact or a full image on N3K-C3172 or N3K-C3132 to 7.0(3)i7(7), after required reload for the upgrade, the Cisco Nexus 3000 switch comes up in switch boot prompt. After gaining local access and loading 7.0(3)i7(7) from switch boot, the Cisco Nexus 3000 switch comes up in 7.0(3)i7(7). If the Cisco Nexus 3000 switch hits the issue and is downgraded back, with BIOS also downgraded, it does not go to switch boot again when re-upgraded. Workaround: When the switch is reloaded for the upgrade and if it comes up in switch boot prompt, reload the system once again from switch boot prompt. |
|
Headline: Default CoPP policy not applied after upgrade. Symptom: Cisco Nexus 3000 switches fail to apply default CoPP policy after an upgrade to 7.0(3)I7(x). This result in drop of control packets. Workaround: Run setup command to install default CoPP policy. |
|
Headline: Spanning tree configuration disappear from show run switch profile after initial sync. Symptom: The spanning-tree port type disappear from 'show run switch-profile' after initial sync but it does manage to add into 'show run' between two synchronised device. At same time, if we try to delete spanning-tree port type from one of the devices, it will not delete from the other one. So, spanning-tree port type is out of sync right after initial commit. Workaround: None. |
|
Headline: Crash due to high rate parity error correction. Symptom: Switch experienced high rate parity error correction while running 7.0(3)I4(7) but did not see this issue. Customer upgraded the switch to 7.0(3)I7(6) and experienced high rate parity error correction and that crashed the switch. Workaround: None |
|
Headline: Cisco Nexus 9000 and/or Cisco Nexus 3000 devices experiencing show VLAN errors for long VLAN names. Symptom: Cisco Nexus 9000 / 3000 device is experiencing show VLAN errors for long VLAN names. Workaround: Avoid VLAN long names or disregard show VLAN output with errors. |
|
Headline: GLC-LH-SMD inside CVR-QSFP-SFP10G (QSA) inserted in Cisco Nexus 3100 may not come up as expected. Symptom: When a GLC-LH-SMD 1G SFP transceiver inside of a CVR-QSFP-SFP10G (QSA) QSFP+ transceiver is inserted in a 40G QSFP+ interface of a Nexus 3100 device, the link may not reliably come up as expected within NX-OS. These symptoms can particularly be observed after a reload of the Nexus 3100 device, although other scenarios exist where the interface may not come up as expected. The device at the remote end of the down/down link may report that the link is up/up as expected. Furthermore, the RX/ingress counters of the affected interface on the Nexus 3100 device may report that traffic is being received, while the TX/egress counters of the affected interface do not report any traffic being sent out of the link. Workaround: Bounce the affected interface using the following configuration brings up the link. Switch# configure terminal Switch(config)# interface Ethernet1/49/1 Switch(config-if)# shutdown Switch(config-if)# no shutdown
|
|
Headline: GLC-LH-SMD inside CVR-QSFP-SFP10G (QSA) inserted in a Cisco Nexus 3100 switch may not come up after OIR. Symptom: When a GLC-LH-SMD 1G SFP transceiver inside a CVR-QSFP-SFP10G (QSA) QSFP+ transceiver is inserted in a 40G QSFP+ interface of a Cisco Nexus 3100 switch, the link may not come up as expected within NX-OS after the GLC-LH-SMD transceiver is removed, then re-inserted inside the CVR-QSFP-SFP10G. Workaround: To proactively avoid encountering this issue, avoid removing and re-inserting the GLC-LH-SMD transceiver from the CVR-QSFP-SFP10G. To work around this issue after encountering it, remove the CVR-QSFP-SFP10G while the GLC-LH-SMD is still inside, then re-insert the CVR-QSFP-SFP10G while the GLC-LH-SMD is still inside. Bounce the affected interface using the following configuration: Switch# configure terminal Switch(config)# interface Ethernet1/51/1 Switch(config-if)# shutdown Switch(config-if)# no shutdown
|
Table 7: Resolved Issues in Cisco Nexus 3500 Series Switches
Bug ID |
Description |
Headline: Cisco Nexus 3500 switches output buffer block stuck. Symptom: Output buffer block gets stuck by one interface on Cisco Nexus 3548 switch running 6.0(2)A8(8), resulting in broadcast/multicast traffic not egressing multiple ports in the same buffer block. Workaround: Only known temporary workaround is to move the interfaces to another buffer block or reload the switch. |
|
Headline: Cisco Nexus 3500 device may drop packets when refreshing NAT HW entry after sampling timeout expire. Symptom: NAT TCP flow may experience TCP retransmission and low performance. Workaround: Use static NAT or increase sampling-timeout to be longer that time it takes for NAT TCP flow to finish. |
|
Headline: Cisco Nexus 3500 switch ACL match counters will not increment as expected on NAT interface. Symptom: Match counters for ACL applied on NAT interface will not increment. Match counters may also change abruptly. Workaround: N/A |
|
Headline: SNMP traps truncating ifalias to 64 chars on Cisco Nexus 3500 Switches. Symptom: N3K-C3548P-10GX running 7.0(3)I7(6). SNMP traps that use ifalias are sent with a maximum length of 64 bytes. snmpalk for ifalias OIDs return full length (up to 255 bytes). Workaround: None. |
|
Headline: Fail to break-in ports on Cisco Nexus 3548, error 'SFP is of different type at "Link length support for copper"'. Symptom: When trying to use a break-in configuration (e.g. taking 4 x 10 Gbps and combining to 40 Gbps), we see failures when we use a mix of transceivers from different manufacturers (Cisco based: Avago/Finisar/Oplink/Accelink). This results in an interface that stays down with a sfpA error. Impacted Platform: N3K-C3548P-10GX. Workaround: Use transceivers that all share the same value for "length". |
|
Headline: Shutting down SVI breaks Peer-Gateway resulting in traffic black-holing. Symptom: When shutting down SVI on vPC peers, traffic is being sent out via peer-link and then drop by the vPC loop avoidance. Workaround: Create a dummy SVI and do " shut / no shut". |
|
Headline: After the transceiver is changed from 1G to 10G, the link does not come up. Symptom: After the transceiver is changed from 1G to 10G, the link does not come up. Connections: N3K-C3548P-10GX <----------------------->N3K-C3048TP-1GE When the transceivers are swapped from a 1000base SFP to a 10Gbase-SR SFP, the link does not come up. Either the status link will show an error (linkFlapErrDisabled) or the link will not be connected.
Workaround: - Remove 1G SFP from the devices. - Change the speed of the interface to auto or manual (to 10G). - Reload the switches. - Insert 10G SFP at both the ends. |
|
Headline: The show system internal access-list command does not show range information. Symptom: A Cisco Nexus 3500 switch running i7 code may not show the correct statistics when you have an access-list configured with statistics per-entry and layer four port ranges. Workaround: None. |
Table 8: Resolved Issues in Cisco Nexus 3600 Series Switches
Bug ID |
Description |
Headline: IS-IS Hellos not forwarded on Cisco Nexus C36180YC-R switch. Symptom: ISI-S hellos are not being forwarded. Customer has IS-IS on ASRs. Adjacency came up fine when customer replaced N3K with WS-C3850-12XS-E (same configuration). Workaround: None. |
The following tables lists the known behaviors in Cisco Nexus 3000, 3100, 3200, 3400-S, 3500 and 3600 Series switches in Cisco NX-OS Release 9.3(3). Click the bug ID to search the Cisco Bug Search Tool for details about the bug.
Table 9: Known Behaviors in Cisco Nexus 3000 and 3100 Series Switches
Bug ID |
Description |
Headline: With switchport mac-learn disable command, MACs are still learnt on VNI enabled VLAN. Symptom: switchport mac-learn disable command/ configuration has no effect on VNI enabled VLAN. Workaround: None. |
|
Headline: The MPLS SR outputs stats incremented for all FECs with same next-hop during POP (swap with 3). Symptom: For Broadcom ASIC Based Trident series platform, In the MPLS SR topology the TX output stats are getting incremented for all FEC with same next hop. Workaround: None. |
|
Headline: N3K-C34180YC: Non default Etherype settings not working. Symptom: switchport dot1q ethertype command not configurable on N3K-C34180YC. Workaround: None. |
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 10: Known Behaviors in Cisco Nexus 3500 Series Switches
Bug ID |
Description |
|
Headline: MTC does not support random-detect ECN. It only supports dctcp ecn. Unsupported cli has been removed for MTC. Symptom: MTC does not support random-detect ECN. It only supports dctcp ecn. Unsupported cli has been removed for MTC Workaround: Cisco Nexus 3500 switches support the command dctcp; but does not support random-detect ecn. The unsupported command (random-detect ecn) is removed in Cisco NX-OS Release 9.3(3). However, you may not get warnings or errors when you configure the command in releases earlier to Cisco NX-OS Release 9.3(3) and then upgrade to Cisco NX-OS Release 9.3(3). The unsupported command is retained in the running-configuration in such cases. |
The following tables list the Cisco Nexus 3000 Series hardware that Cisco NX-OS Release 9.3(3) 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
■ Cisco Nexus 3200 Series Switches
■ Cisco Nexus 3400-S Series Switches
■ Cisco Nexus 3500 Series Switches
■ Cisco Nexus 3500 Series fans and fan trays
■ Cisco Nexus 3600 Series Switches
Table 11: Cisco Nexus 3000 and 3100 Series Switches
Product ID |
Description |
N3K-C3048TP-1GE |
Cisco Nexus 3048 switch |
N3K-C3064PQ |
Cisco Nexus 3064 switch |
N3K-C3064PQ-10GE |
Cisco Nexus 3064-E switch |
N3K-C3064PQ-10GX |
Cisco Nexus 3064-X switch |
N3K-C3064TQ-10GT |
Cisco Nexus 3064-TQ switch |
N3K-C31108PC-V |
Cisco Nexus 31108PC-V switch |
N3K-C31108TC-V |
Cisco Nexus 31108TC-V |
N3K-C31128PQ-10GE |
Nexus 31128PQ, 96 x 10 Gb-SFP+, 8 x 10-Gb QSFP+, 2-RU switch. |
N3K-C3132C-Z |
Cisco Nexus 3132C-Z switch |
N3K-C3132Q-40GE |
Cisco Nexus 3132Q switch |
N3K-C3132Q-40GX |
Cisco Nexus 3132Q-X switch |
N3k-C3132Q-V |
Cisco Nexus 3132Q-V switch |
N3K-C3132Q-XL |
Cisco Nexus C3132Q-XL switch |
N3K-C3164Q-40GE |
Cisco Nexus 3164Q, 64 x 40-Gb SFP+, 2-RU switch |
N3K-C3172PQ-10GE |
Cisco Nexus 3172PQ switch |
N3K-C3172PQ-XL |
Cisco Nexus C3172PQ-XL switch |
N3K-C3172TQ-10GT |
Cisco Nexus 3172TQ switch |
N3K-C3172TQ-XL |
Cisco Nexus C3172TQ-XL switch |
Table 12: Cisco Nexus 3000 and 3100 Series Fans, Fan Trays and Power Supplies
Product ID |
Description |
N2200-PAC-400W |
Cisco Nexus 2000 or Nexus 3000 400W AC power supply, forward airflow (port side exhaust) |
N2200-PAC-400W-B |
Cisco Nexus 2000 or 3000 400W AC power supply with reverse airflow (port-side intake). |
N2200-PDC-400W |
Cisco Nexus 2000 or Nexus 3000 400W DC power supply, forward airflow (port side exhaust) |
N3K-C3048-FAN |
Cisco Nexus 3048 fan module with forward airflow (port-side exhaust) |
N3K-C3048-FAN-B |
Cisco Nexus 3048 fan module with reverse airflow (port-side intake) |
N3K-C3064-X-BA-L3 |
Cisco Nexus 3064-X reversed airflow (port-side intake) AC power supply |
N3K-C3064-X-BD-L3 |
Cisco Nexus 3064-X forward airflow (port-side intake) DC power supply |
N3K-C3064-X-FA-L3 |
Cisco Nexus 3064-X forward airflow (port-side exhaust) AC power supply |
N3K-C3064-X-FD-L3 |
Cisco Nexus 3064-X forward airflow (port-side exhaust) DC power supply |
N3K-PDC-350W-B |
Cisco Nexus 2000 DC power supply with reverse airflow (port-side intake) |
N3K-PDC-350W-B |
Cisco Nexus 2000 or Nexus 3000 350W DC power supply, reversed airflow (port side intake) |
NXA-FAN-30CFM-B |
Cisco Nexus 2000 or Nexus 3000 individual fan, reversed airflow (port side intake) |
NXA-FAN-30CFM-F |
Cisco Nexus 2000 or Nexus 3000 individual fan, forward airflow (port side exhaust |
NXA-PAC-500W |
Cisco Nexus 3064-T 500W forward airflow (port-side exhaust) AC power supply |
NXA-PAC-500W-B |
Cisco Nexus 3064-T 500W reverse airflow (port-side intake) AC power supply |
Table 13: Cisco Nexus 3200 Series Switches
Product ID |
Description |
C1-N3K-C3232C |
Cisco Nexus 3232C switch. |
N3K-C3264C-E |
Cisco Nexus 3264C-E switch. |
N3K-C3264Q |
Cisco Nexus 3264Q switch. |
Table 14: Cisco Nexus 3400-S Series Switches
Product ID |
Description |
N3K-C3408-S |
Cisco Nexus 3408-S switch with 32 ports of QSFP-DD. |
N3K-C3432D-S |
Cisco Nexus 3432D-S switch with 32ports of QSFP-DD. |
Table 15: Cisco Nexus 3500 Series Switches
Product ID |
Description |
N3K-C3524P-10G |
Cisco Nexus 3524 switch |
N3K-C3524P-10GX |
Cisco Nexus 3524 switch, 24 SFP+ |
N3K-C3524P-XL |
Cisco Nexus 3524-XL switch |
N3K-C3548P-10G |
Cisco Nexus 3548 switch |
N3K-C3548P-10GX |
Cisco Nexus 3548x switch, 48 SFP+ |
N3K-C3548P-XL |
Cisco Nexus 3548-XL switch |
Table 16: Cisco Nexus 3500 Series Fans, Fan Trays and Power Supplies
Product ID |
Description |
N2200-PAC-400W |
Cisco Nexus 2000 or Nexus 3000 400W AC power supply, forward airflow (port side exhaust) |
N2200-PAC-400W-B |
Cisco Nexus 2000 or Nexus 3000 400W AC power supply, reversed airflow (port side intake) |
N2200-PDC-400W |
Cisco Nexus 2000 or Nexus 3000 400W DC power supply, forward airflow (port side exhaust) |
N3K-PDC-350W-B |
Cisco Nexus 2000 or Nexus 3000 350W DC power supply, reversed airflow (port side intake) |
NXA-FAN-30CFM-B |
Cisco Nexus 2000 or Nexus 3000 individual fan, reversed airflow (port side intake) |
NXA-FAN-30CFM-F |
Cisco Nexus 2000 or Nexus 3000 individual fan, forward airflow (port side exhaust |
Table 17: Cisco Nexus 3600 Series Switches
Product ID |
Description |
N3K-C3636C-R |
The Cisco Nexus 3636C-R is a 1 rack unit (RU) switch with 36 100-Gigabit QSFP28 ports, 40-Gigabit QSFP, 2 management ports, 1 console port, and 1 USB port. The switch supports both port-side exhaust and port-side intake airflow schemes. The switch has two power supplies, one for operations and the other for redundancy. Both power supplies must be either AC power supplies or DC power supplies. |
N3K-C36180YC-R
|
The Cisco Nexus 36180YC-R is a 1 rack unit (RU) switch with 48 1/10/25-Gigabit SFP ports and 6 40-Gigabit QSFP/100-Gigabit QSFP28 ports, 1 management port, 1 console port, and 1 USB port. The switch supports both port-side exhaust and port-side intake airflow schemes. The switch has two power supplies, one for operations and the other for redundancy. Both power supplies must be either AC power supplies or DC power supplies. |
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(3)
■ Guidelines and Limitations - Upgrade
· A non-disruptive standard ISSU is supported from Cisco NX-OS Release 7.0(3)I7(7) or later releases to a Cisco NX-OS 9.2(X) or Cisco NX-OS 9.3(X) releases. This behaviour is valid only for the Nexus 3000 Series Switches (4GB platforms only).
· Cisco Nexus 3132Q-XL, 3172PQ-XL, and 3172TQ-XL switches support an ISSU to Cisco NX-OS Release 9.3(1) and later releases. For the list of platforms and releases that support a non-disruptive In-Service Software Upgrade (ISSU) to Cisco NX-OS Release 9.3(3), see the Cisco NX-OS ISSU Support Matrix.
The following disruptive upgrade paths are supported:
· For Cisco Nexus 3048 switches, use one of the two following upgrade paths:
· Release 6.0(2)U5(1) -> Release 6.0(2)U6(2a) -> Release 6.0(2)U6(10) -> Release 7.0(3)I7(8) -> Release 9.3(3)
· Release 9.2(1) -> Release 9.2(4) -> Release 9.3(3)
· 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(3)
· Release 9.2(1) -> Release 9.2(4) -> Release 9.3(3)
· For Cisco Nexus 3132C-Z Series switches:
Release 9.2(2) -> Release 9.3(3)
· For Cisco Nexus 3164Q, 31128PQ, and 3100-V switches:
Release 7.0(3)I2(1) or later -> Release 9.3(3)
· For Cisco Nexus 3264C-E switches:
Release 9.2(1) -> Release 9.3(3)
The following guidelines and limitations are applicable when you upgrade to Cisco NX-OS Release 9.3(3):
■ 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(3) 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(3) is not supported.
■ The following switches do not support an ISSU (nondisruptive upgrade) to Cisco NX-OS Release 9.3(3):
· 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(3), you must configure the BGP graceful restart timer to 180 seconds for Cisco Nexus 3132Q-XL, 3172PQ-XL, 3172TQ-XL, and 3132Q-V platform switches.
■ If you downgrade the Cisco Nexus device from Cisco NX-OS Release 9.3(3) 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.
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).
For the list of platforms and releases that support a non-disruptive In-Service Software Upgrade (ISSU) to Cisco NX-OS Release 9.3(3), 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(3)
§ For Cisco Nexus 3264C-E switches:
Release 9.2(1) or 9.2(2) -> Release 9.3(3)
§ For Cisco Nexus 3408-S and 3432D-S switches:
Release 9.2(2t) to 9.2(2v) -> Release 9.3(3)
Release 9.2(2v) -> Release 9.3(3)
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(3)
■ Guidelines and Limitations - Upgrade
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(3)
§ Release 9.2(1) -> Release 9.2(4) -> Release 9.3(3)
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(3)
· Release 6.0(2)A8(2) or later -> Release 6.0(2)A8(7b) or later -> Release 9.2(4) or later -> 9.3(3)
· 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(3)
· Release 6.0(2)A7(2a) or earlier - > Release 6.0(2)A8(7b) or later -> Release 9.2(4) or later -> 9.3(3)
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(3):
■ 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(3).
■ For Cisco Nexus 3548 and 3548-X switches, you must compact the software image before you upgrade from earlier releases to Cisco NX-OS Release 9.3(3). For the Cisco Nexus 3548-XL switch, compaction is not required.
■ 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 Releases 6.0(2)A8(7b), 6.0(2)A8(8), or 6.0(2)A8(9) to Cisco NX-OS Release 9.3(3):
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.
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).
The following disruptive upgrade paths are supported:
■ Release 9.2(1) or 9.2(2)-> Release 9.3(3)
■ Release 7.0(3)F3(4) -> Release 9.3(3)*
■ Release 7.0(3)F3(3c) -> Release 9.3(3)*
■ Release 7.0(3)F3(3) -> Release 7.0(3)F3(4) -> Release 9.3(3)*
* These upgrade paths require write erase and reload.
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
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
■ FCoE NPV
■ Intelligent Traffic Director (ITD)
■ Enhanced ISSU. NOTE: Check the appropriate guide to determine which platforms support Enhanced ISSU.
■ MLD
■ NetFlow
■ PIM6
■ Policy-based routing (PBR)
■ Port loopback tests
■ 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
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.
The entire Cisco Nexus 3000 Series NX-OS documentation set is available at the following URL:
For Cisco Nexus 3000 Series switches that operate in N9K mode, see the Cisco Nexus 9000 Series NX-OS documentation:
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)
© 2020 Cisco Systems, Inc. All rights reserved.