Cisco Nexus 9000 Series NX-OS Release Notes, Release 9.3(4)

Available Languages

Download Options

PDF (1.0 MB)
View with Adobe Reader on a variety of devices

Updated:June 30, 2020

Bias-Free Language

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. Learn more about how Cisco is using Inclusive Language.

Date	Description
April 25, 2024	Added CSCwh50989 to Open Issues.
June 30, 2020	Added CSCvu20429 to Open Issues.
May 14, 2020	Added CSCvs50843 to Resolved Issues.
May 2, 2020	Added CSCvt68363 to Resolved Issues.
April 29, 2020	Cisco NX-OS Release 9.3(4) became available.

Bug ID	Description
CSCvj63603	Headline: OC ACL: delete ipv4 ace with hop-limit configs fails Symptoms: When we have an ACE with hop-limit configs that were configured through the CLI and you try to delete it through NETCONF, it returns 'List delete failed' error, instead of deleting that entry from the configs. Workarounds: Create ACE through netconf (or) Delete ACE through CLI
CSCvm11554	Headline: PTP High correction on slave when master have SVI which have IGMP Connected Group Membership Symptoms: When SVI on a PTP master switch receives an IGMP membership report and creates IGMP entries, PTP High correction issues occur. %PTP-2-PTP_HIGH_CORR: Slave port Eth1/X High correction -125750482(nsec) This issue is applicable only to Cisco Nexus 9500-R platforms. Workarounds: A or B A. - Remove PIM config from PTP VLAN SVI B. - Use other VLAN to PTP instead of VLAN used for multicast
CSCvn07656	Headline: ACL Stats - Packet hitting an ACE entry with log option will be counted twice Symptoms: With ACL logging enabled on the ingress ACL, each packet hit is counted twice in TCAM stats. Once for the original packet and once for the SUP copy. Workarounds: None
CSCvp02447	Headline: Snmpbulkwalk/getnext periodic slowness seen in PFC-EXT-mibs. Symptoms: None Workarounds: None
CSCvp20546	Headline: Multiste EVPN Scale-after multiple flaps of NVE mac address is out of sync between BGP and L2RIB Symptoms: MAC table is pointing to incorrect NH after multiple NVE flaps Workarounds: Clear ip arp force-delete or clear ipv6 nd force-delete (if v6 host) and clear MAC address table
CSCvp75031	Headline: Nexus 9300 - Block CLI to configure sub-interface with 40G uplink ports Symptoms: Sub-interfaces are not supported for 40G uplinks ports with 1st generation Cisco Nexus 9300 platform switches. BUM (broadcast, multicast, unknown unicast) traffic might not egress local ports after VXLAN decapsulation of such traffic. Not all traffic is impacted depending on internal load-balancing of traffic between internal ASICs. Workarounds: Do not use sub-interfaces for 40G uplinks ports. You can have sub-interfaces on 10G downstream ports.
CSCvq15147	Headline: Interface BW not accounting unicast BW after SSO switchover Symptoms: After a switchover, the unicast fabric bandwidth does not get reserved on fabric links. Workarounds: Flapping the fabric interface should fix it.
CSCvq33024	Headline: TRM Multisite: traffic drop on BGW after restarting ngmvpn Symptoms: TRM traffic loss for 1-2 seconds. Workarounds: None
CSCvq44103	Headline: 25g AOC/LR/SR Cable type is shown as unknown Symptoms: Cable type is shown as "unknown" for 25G SFP- LR, SR, and AOC cables. However, for copper 25G cables 'cable type' is displayed as CA-L, CA-N and CA-S accordingly. Workarounds: There is no workaround for this problem.
CSCvr75903	Headline: Sequence timeout seen at reload with VXLAN PBR -- SVI flap optimizations needed. Symptoms: The system might experience a sequence timeout that might cause the L2alredirect loopback test to fail, rpm verification to fail, or a DHCP snoop hardware programming failure. When hit on the vPC secondary, this situation might result in vPC VLANs getting suspended on primary. Workarounds: Once the issue is hit, you can shut/no-shut the MCT link in vPC primary or operational primary to bring up the suspended VLANS. Also, to avoid getting into this situation, you may use GIR (graceful insertion and removal) to isolate the 9500, upgrade the chassis, and after all modules are up, insert the switch in to the network.
CSCvr76803	Headline: Netstack core seen in non-destructive ISSU using FQDN for NTP Symptoms: FQDN for NTP server and ND ISSU on T2 ToR Workarounds: Do not use FQDN for NTP Servers. Use IP Address.
CSCvs15713	Headline: FC 48 ports entitlement tag is consumed even with 16 or less ports are configured Symptoms: FC 48 ports entitlement tag is consumed irrespective of the number of FC ports acquired. Workarounds: None. This will not impact the functionality of ports.
CSCvs28295	Headline: MPLS entries present after no feature-set mpls command Symptoms: After entering the "no feature-set mpls" command, the output of the "show for adjacency mpls stats" command is not empty. Workarounds: Reload the box.
CSCvs41360	Headline: N9K-C93600CD-GX: Extra Flaps seen after Multiple reloads/flaps on different Optics on Gearbox Ports Symptoms: One Extra Flap seen after Multiple reloads/flaps on different Optics on ports 1-24 of N9K-C93600CD-GX. Similar extra flap seen after Multiple reloads/flaps on QSFP-100G-PSM4 and QSFP-100G-FR of N9K-9364C-GX. Workarounds: None
CSCvs49263	Headline: Traffic outage when switching 4x25G --> 2x50G --> 4x25G soft-breakout, control plane is fine Symptoms: PIXMC-SDB would be wrong Breakout third port LTL will be assigned 2nd port ifidx Workarounds: Reload module.
CSCvs50407	Headline: Multicast traffic drop due to NF flag set. Symptoms: On T2-EoR that is part of a vPC pair, ND-ISSU (modular) is done from 7.0.(3)I4(0) to 9.3(3) and there is a loss of multicast traffic towards receivers on L3 interfaces. That is, non vPC-SVI OIF. Workarounds: Use an intermediate ISSU from 7.0(3)I4(0) to 9.3(2) on both vPC peers, and then an ISSU from 9.3(2) to 9.3(3).
CSCvt06466	Headline: N9K-C9364C-GX: 100G CRC (1/50,53, AOC 1M/5M) after 61st/16th reload Symptoms: During reload loop we observed that one of the lanes on a couple of ports on a particular board (port 53) that one of the lanes of the port shows low SNR compared to other lanes of that same port. Due to this low SNR, CRC is seen on that lane. Issue is seen only with one board and only when AOC cable is connected. Workarounds: Flap the port to recover.
CSCvt18150	Headline: BootupPortLoopback is not running consistently for 4x10G Breakout on Native 400G Ports Symptoms: The Gold bootup port loopback test remains untested if the port is in 4x10 breakout mode. Workarounds: To get the bootup test working on a port, un-breakout the port and reload the card.
CSCvt28463	Headline: N9K-93XX-GX: Delayed link up between Gearbox Ports to bear valley on Peer for 40G AOC ports Symptoms: 40G AOC connection from N9K-C9364C-GX to N9K-C9364C (port 49 to 64) or N9K-C9336C-FX2 (port 1 to 6, 33 to 36) might see a longer link up time. Workarounds: Use port 1 to 48 on N9K-C9364C or port 7 to 32 on N9K-C9336C-FX2, or use other 40G optics than AOC.
CSCvt43179	Headline: IPv6 BGP neighborship fails to come up (Idle state) on N9K-C93180YC-FX Symptoms: Below syslogs are seen on the device: %BGP-3-SOCKBIND: bgp- [1592] Cannot bind local socket for peer 2000:x:x:x Cannot assign requested address Workarounds: Shut/Unshut L3 IPv6 interface
CSCvt49337	Headline: N9K-C9364C-GX: 100G (1/50 AOC1M, 1/56 PSM4) steady state flap after 61st/multiple reload Symptoms: When tested with a reload loop, on one of the reloads the link flaps in steady state. Workarounds: Flap the port to recover.
CSCvt56182	Headline: Cisco NX-OS 9.3(3) to 9.3(4): ND ISSU on LXC TOR causing transient traffic drop Symptoms: Cisco NX-OS 9.3(3) to 9.3(4): ND ISSU on LXC TOR causing transient traffic drop when we have the BFD enabled as the BFD is going down and coming up during the ND ISSU Workaround: Remove the BFD and re-add.
CSCvt78096	Headline: BGW reload can cause 200+ sec packet loss Symptoms: Reloading BGW can cause 200+sec packet loss Workarounds: None
CSCvt78821	Headline: Global \| Nexus 9k 7.0(3)I7(5a) L2 Multicast traffic delivery issues Symptoms: After NXOS upgrade in a C9508 from 7.0(3)I5(2) code to 7.0(3)I7(5a) code, Layer 2 Multicast traffic is not being forwarded to Layer 2 access ports belonging to igmp snooping groups in a specific VLAN, this occurs when there is an SVI configured in shutdown state in that specific VLAN with ip pim sparse-mode in the switch. Workarounds: Delete ip pim sparse-mode in SVI.
CSCvu20429	Headline: Storm control commands broadcast/muliticast added to interface configs after non disruptive ISSU Symptoms: After multiple non disruptive ISSUs, the following commands were added to the interface configuration causing complete connectivity issues. For instance, non-disruptive ISSU was performed as below versions and all L2/L3 interfaces were added with below commands. I7.0(3)I4(1) > 7.0(3)I7(7)> 7.0(3)I7(8) interface Ethernet1/17 link transmit reset-skip no link dfe adaptive-tuning storm-control broadcast level pps 0 <- added after the upgrade storm-control multicast level pps 0 <- added storm-control unicast level pps 0 <- added switchport virtual-ethernet-bridge <- added Workarounds: Reconfigure the same commands on effected ports and then remove it as indicated below. configure terminal interface e1/17 storm-control broadcast level pps 0 storm-control multicast level pps 0 storm-control unicast level pps 0 switchport virtual-ethernet-bridge config t int eth 1/17 no storm-control broadcast level pps 0 no storm-control multicast level pps 0 no storm-control unicast level pps 0 no switchport virtual-ethernet-bridge Or Write erase and reapply the original configurations.
CSCwh50989	Headline: Custom COPP causing transit traffic to be punted to the CPU on Nexus 9300-GX2 Symptoms: When custom-COPP policy contains ACL rules which match on Layer 4 destination or source port, transit traffic also hits the COPP and the packets are copied to CPU. This causes duplication of traffic as CPU also routes the copied packets to the destination. Workarounds: Custom COPP policy using src/dst match mitigates punt for transit traffic.

Bug ID	Description
N/A	Interface: The output format for the exec command CLI show vpc orphan-ports has changed from the 7.0(3)F3(4) release to the 9.3(4) release.
N/A	FEX: MTU 9216 is the default value for FEX fabric ports-channels.
N/A	FEX: MTU 9216 is the only allowed value to be configured on FEX fabric port-channels. Configuring any other value will throw an error.
CSCvp87914	FEX: If the MTU value on a FEX fabric port-channel was set to 9216 before upgrading to Cisco NX-OS Release 9.3(4), the show running config command will not display the MTU config as it is the new default in Cisco NX-OS Release 9.3(4). Due to this, the show running-config diff command displays the difference which is expected.
N/A	Programmability: Release 9.3(4) brings in a new kernel and new processes.
N/A	Programmability: Interface counter statistics are grouped together in the XML/JSON output. The output for the show interface-counters command in JSON format has changed.
N/A	Programmability: NX-API does not support insecure HTTP by default.
N/A	Programmability: NX-API does not support weak TLSv1 protocol by default.
N/A	Security: Stronger ciphers are used in this release.
N/A	Security: A new command, no service password-recovery is supported.
N/A	Security: Only one version out of v4 and v6 versions of the uRPF command can be configured on an interface. If one version is configured, all the mode changes must be done by the same version. The other version is blocked on that interface. Cisco Nexus 9300-EX, 9300-FX, and 9300-FX2 platform switches do not have this limitation and you can configure v4 and v6 version of urpf cmd individually.

Bug ID	Description
CSCvu02712	Intermittent CRC errors are seen on Cisco Nexus N9K-C9236C retimer ports (1-8 and 29-36), when connected to Cisco Nexus N9K-C93600CD-GX 100G native ports (25-28) and broken out to 4x25G. The issue is not seen in non-breakout 100G mode. Workaround: Avoid these connections. Ports 9-28 on the Cisco Nexus N9K-C9236C can be used instead.
CSCvt41915	ISIS route is deleted from kernel when ip unnumbered config is deleted and added back in quick succession (within say 30 seconds) Recovery: ip unnumbered config deletion and addition should be done within the 60-second window to be safe. If issue is hit, recovery is to flap the interface with the shut command followed by the no shut command.
CSCvr20128	The issue happens for pinned static routes only. These routes don't get installed in the kernel. So, BGP sessions over these routes might not work. A ping from Bash will not work. Recovery: If the issue is seen, pinned static routes can be deleted and added back. Also, entering the clear ip route vrf <vrf-name> command can be done to recover from the issue. Further Problem Description: 1. The issue happens for pinned static routes only. Pinned static routes is a feature borrowed from Catalyst 6000 IOS platforms and not many customers use it on Cisco Nexus 9000. 2. There are 3 flavors of the issue a. Pinned static route could have a next hop which is not in the subnet of the IP address configured on the interface. In this case, kernel canâETMt installs the route irrespective of when Netstack sends the route programming request because, the next hop is not in the same subnet of the interface IP address. b. Pinned static route could have some next hops. But on the interface, there is no global IPv6 address configured. It has only a link-local address configured. In this case also, kernel canâETMt install the route irrespective of when Netstack sends the route programming request because the next hop is not in the same subnet of the interface IP address. c. Pinned static route could have a next hop which is in the same subnet of the IP address configured on the interface. In this case, the kernel can install the route only if Netstack sends a route programming request after it programs the IP address to the kernel. While programming the route, the kernel determines that the next hop is already programmed. This is a very specific case of pinned static routes.
CSCvc95008	On Cisco Nexus 9300-EX, 9348GC-FXP, 93108TC-FX, 93180YC-FX, 9336C-FX2, 93216TC-FX2, 93360YC-FX2, 93240YC-FX2, 92348GC-X, C93108TC-EX-24, C93108TC-FX-24, C93180YC-EX-24, C93180YC-FX-24, 9316D-GX, 9364C-GX, and 93600CD-GX switches, when 802.1q EtherType has changed on an interface, the EtherType of all interfaces on the same slice will be changed to the configured value. This change is not persistent after a reload of the switch and will revert to the EtherType value of the last port on the slice.
CSCvr92708	CoPP violations can be seen under class-map copp-system-p-class-l2-default and access-group copp-system-p-acl-mac-undesirable in an MVPN setup on a PE device. This can cause an impact to MVPN control plane functionality for packets such as MSDP and PIM register messages, in case of a large number of MVPN PE devices and MDT groups. You can create a custom CoPP policy with an increased "cir" value until no CoPP violation is seen for that class.
CSCvr95514	Per-VRF Configuration of MDT MTU size is not supported on MVPN PE devices on N9K-X9636C-R/RX, N3K-C36180YC-R, N3K-C3636C-R platforms. While, Tunnel MTU size is not configurable interface MTU for the core facing interface can be configured to control port-level MTU. MDT tunnel is capable of carrying up to jumbo MTU size of 9192 (excluding tunnel header), provided interface MTU for the core-facing interface also supports jumbo MTU.
CSCvr92710	CMIS standards prescribe delays at each state as mentioned by the QSFP-DD firmware on those optics. If you are using those optics with delays, you will see a higher link-up time.
CSCvr14625	CMIS standards prescribe delays at each state as mentioned by the QSFP-DD firmware on those optics. If you are using those optics with delays, you will see a higher link-up time.
CSCvr13930	The Cisco Nexus 9300-GX ASIC does not support FC-FEC on the second lane of 50x2 breakout port. This is due to an ASIC limitation. The second link cannot come up when 50x2 breakout is done. Workarounds: You must configure RS-FEC with 50x2 breakout.
CSCvr11900	Multicast routes used by Data MDT are not deleted immediately on MVPN PE (where Encapsulation takes place) after all the customer (VRF) traffic stops which use the same Data MDT. They may stay up for 15 minutes and then get deleted.
N/A	When large files, for example NX-OS, images are copied to USB, the following message is printed: 2019 Jul 2 15:49:47 Molti_A %$ VDC-1 %$ Jul 2 15:49:46 %KERN-3-SYSTEM_MSG: [ 8032.291555] INFO: task vsh.bin:9418 blocked for more than 120 seconds. – kernel 2019 Jul 2 15:49:47 Molti_A %$ VDC-1 %$ Jul 2 15:49:46 %KERN-3-SYSTEM_MSG: [ 8032.291560] Tainted: P O 4.1.21-WR8.0.0.28-standard #1 - kernel 2019 Jul 2 15:49:47 Molti_A %$ VDC-1 %$ Jul 2 15:49:46 %KERN-3-SYSTEM_MSG: [ 8032.291561] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. - kernel As long as these messages correspond to a copy operation to USB, this message can be ignored.
N/A	In the NX-API sandbox, whenever XML or JSON output is generated for the show run command or the show startup command, the output contains additional characters. For example, </nf:source> <============nf: is extra <namespace> : extra characters are seen with XML and JSON from NX-API.
N/A	When you upgrade a Cisco Nexus 9000 device to Cisco NX-OS Release 9.3(4), if a QSFP port is configured with the manual breakout command and is using a QSA, the configuration of the interface Ethernet 1/50/1 is no longer supported and will need to be removed. To restore the configuration, you must manually configure the interface Ethernet 1/50 on the device.
N/A	Due to the design of airflow, back-to-front fans requires fan speed to be run at full speed all the time. You might also see fan speeds increase from 40% to 70% post-upgrade. This applies to the following PIDs: N9K-C9272Q, N9K-C9236C, N9K-C93180YC-FX, N9K-C93180TC-FX, N9K-C9364C, N3K-C36180YC-R, N9K-C9336C-FX2, N9K-C9332C. This change is made as of cisco NX-OS Release 7.0(3)I7(3). If your PID is not listed, please contact Cisco TAC for additional verification.
N/A	PTP is not supported on the 96136YC-R line card or for line cards on the Cisco Nexus 9504 switch.
N/A	The following features are not supported on the Cisco Nexus 3464C and 9364C switches. ■ 100 G port cannot support breakout (HW limitation) ■ FEX ■ ISSU ■ Segment routing ■ Tetration (HW limitation)
N/A	■ The following feature is not supported on the Cisco Nexus 9332C: o uRPF
N/A	Only the following switches support QSFP+ with the QSFP to SFP/SFP+ adapter (40 Gb to 10 Gb): ■ N9K-C93120TX ■ N9K-C93128TX ■ N9K-C9332PQ ■ N9K-C9372PX ■ N9K-C9372PX-E ■ N9K-C9372TX ■ N9K-C9396PX ■ N9K-C93108TC-EX ■ N9K-C93108TC-FX ■ N9K-C93180YC-EX ■ N9K-C93180YC-FX
N/A	The Cisco Nexus 9300 platforms support for the QSFP+ breakout has the following limitations: ■ 1 Gb and 10 Gb can be supported using the QSFP-to-SFP Adapter on 40-Gb uplink ports on Cisco Nexus 9300 platform switches in NX-OS. ■ For the Cisco Nexus 9332PQ switch, all ports except 13-14 and 27-32 can support breakout.
N/A	The following switches support the breakout cable (40 Gb ports to 4x10-Gb ports): ■ N9K-C9332PQ ■ N9K-X9436PQ ■ N9K-X9536PQ ■ N9K-C93180LC-EX—last four ports are breakout capable (10x4, 24x4, 50x2) ■ N9K-C93180YC-EX ■ N9K-C93108TC-EX ■ N9K-X9732C-EX line card ■ N9K-X9732C-FX line card ■ N9K-X97160YC-EX ■ N9K-C93180YC-EX ■ N9K-C93108TC-EX ■ N9K-C93180YC-FX ■ N9K-C93108TC-FX ■ N9K-C9348GC-FXP
N/A	Limitations for ALE (Application Link Engine) uplink ports are listed at the following location: Limitations for ALE 40G Uplink Ports on Cisco Nexus 9000 Series Switches
N/A	Nested VXLAN is not supported on a Layer 3 interface or on a Layer 3 port-channel interface in Cisco NX-OS Release 9.3(4) and prior releases.
CSCwi99525	On Cisco Nexus N2K-C2348TQ HIFs fail to utilize redundant Port-Channel links, to NIF, during link failover events.

Product ID	Description
N9K-C9504	7.1-RU modular switch with slots for up to 4 line cards in addition to two supervisors, 2 system controllers, 3 to 6 fabric modules, 3 fan trays, and up to 4 power supplies.
N9K-C9508	13-RU modular switch with slots for up to 8 line cards in addition to two supervisors, 2 system controllers, 3 to 6 fabric modules, 3 fan trays, and up to 8 power supplies.
N9K-C9516	21-RU modular switch with slots for up to 16 line cards in addition to two supervisors, 2 system controllers, 3 to 6 fabric modules, 3 fan trays, and up to 10 power supplies.

Product ID	Description	Maximum Quantity
Product ID	Description	Cisco Nexus 9504	Cisco Nexus 9508	Cisco Nexus 9516
N9K-X9736C-FX	Cisco Nexus 9500 36-port 40/100 Gigabit Ethernet QSFP28 line card	4	8	16
N9K-X9732C-FX	Cisco Nexus 9500 32-port 40/100 Gigabit Ethernet QSFP28 line card	4	8	16
N9K-X9732C-EX	Cisco Nexus 9500 32-port 40/100 Gigabit Ethernet QSFP28 line card	4	8	16
N9K-X9736C-EX	Cisco Nexus 9500 36-port 40/100 Gigabit Ethernet QSFP28 line card	4	8	16
N9K-X9788TC-FX	Cisco Nexus 9500 48-port 1/10-G BASE-T Ethernet and 4-port 40/100 Gigabit Ethernet QSFP28 line card	4	8	16
N9K-X97160YC-EX	Cisco Nexus 9500 48-port 10/25-Gigabit Ethernet SFP28 and 4-port 40/100 Gigabit Ethernet QSFP28 line card	4	8	16

Product ID	Description	Minimum	Maximum
N9K-C9504-FM-E	Cisco Nexus 9504 100-Gigabit cloud scale fabric module	4	5
N9K-C9508-FM-E	Cisco Nexus 9508 100-Gigabit cloud scale fabric module	4	5
N9K-C9508-FM-E2	Cisco Nexus 9508 100-Gigabit cloud scale fabric module	4	5
N9K-C9516-FM-E	Cisco Nexus 9516 50-Gigabit cloud scale fabric module	4	5
N9K-C9516-FM-E2	Cisco Nexus 9516 100-Gigabit cloud scale fabric module	4	5

Supervisor	Description	Quantity
N9K-SUP-A	1.8-GHz supervisor module with 4 cores, 4 threads, and 16 GB of memory	2
N9K-SUP-A+	1.8-GHz supervisor module with 4 cores, 8 threads, and 16 GB of memory	2
N9K-SUP-B	2.2-GHz supervisor module with 6 cores, 12 threads, and 24 GB of memory	2
N9K-SUP-B+	1.9-GHz supervisor module with 6 cores, 12 threads, and 32 GB of memory	2

Cisco Nexus Switch	Description
N9K-C9336C-FX2	1-RU switch with 36 40-/100-Gb Ethernet QSFP28 ports.
N9K-C93216TC-FX2	2-RU switch with 96 100M/1G/10G RJ45 ports, 12 40/100-Gigabit QSFP28 ports, 2 management ports (one RJ-45 and one SFP port, 1 console, port, and 1 USB port.
N9K-C93240YC-FX2	1.2-RU Top-of-Rack switch with 48 10-/25-Gigabit SFP28 fiber ports and 12 40-/100-Gigabit Ethernet QSFP28 ports.
N9K-C93360YC-FX2	2-RU switch with 96 10-/25-Gigabit SFP28 ports and 12 40/100-Gigabit QSFP28 ports
N9K-C93108TC-FX	1-RU Top-of-Rack switch with 48 100M/1/10GBASE-T (copper) ports and 6 40-/100-Gigabit QSFP28 ports
N9K-C93108TC-FX-24	1-RU 24 1/10GBASE-T (copper) front panel ports and 6 fixed 40/100-Gigabit Ethernet QSFP28 spine-facing ports.
N9K-C93180YC-FX	1-RU Top-of-Rack switch with 10-/25-/32-Gigabit Ethernet/FC ports and 6 40-/100-Gigabit QSFP28 ports. You can configure the 48 ports as 1/10/25-Gigabit Ethernet ports or as FCoE ports or as 8-/16-/32-Gigabit Fibre Channel ports.
N9K-C93180YC-FX-24	1-RU 24 1/10/25-Gigabit Ethernet SFP28 front panel ports and 6 fixed 40/100-Gigabit Ethernet QSFP28 spine-facing ports. The SFP28 ports support 1-, 10-, and 25-Gigabit Ethernet connections and 8-, 16-, and 32-Gigabit Fibre Channel connections.
N9K-C93108TC-EX	1-RU Top-of-Rack switch with 48 10GBASE-T (copper) ports and 6 40-/100-Gigabit QSFP28 ports
N9K-C93108TC-EX-24	1-RU 24 1/10GBASE-T (copper) front panel ports and 6 40/100-Gigabit QSFP28 spine facing ports.
N9K-C93180LC-EX	1-RU Top-of-Rack switch with 24 40-/50-Gigabit QSFP+ downlink ports and 6 40/100-Gigabit uplink ports. You can configure 18 downlink ports as 100-Gigabit QSFP28 ports or as 10-Gigabit SFP+ ports (using breakout cables)
N9K-C93180YC-EX	1-RU Top-of-Rack switch with 48 10-/25-Gigabit SFP28 fiber ports and 6 40-/100-Gigabit QSFP28 ports
N9K-C93180YC-EX-24	1-RU 24 1/10/25-Gigabit front panel ports and 6-port 40/100 Gigabit QSFP28 spine-facing ports
N9K-C92160YC-X	1-RU Top-of-Rack switch with 48 10-/25-Gigabit SFP+ ports and 6 40-Gigabit QSFP+ ports (4 of these ports support 100-Gigabit QSFP28 optics).
N9K-C92300YC	1.5-RU Top-of-Rack switch with 48 10-/25-Gigabit SFP28 ports and 18 fixed 40-/100-Gigabit QSFP28 ports.
N9K-C92304QC	2-RU Top-of-Rack switch with 56 40-Gigabit Ethernet QSFP+ ports (16 of these ports support 4x10 breakout cables) and 8 100-Gigabit QSFP28 ports.
N9K-C9236C	1-RU Top-of-Rack switch with 36 40-/100-Gigabit QSFP28 ports (144 10-/25-Gigabit ports when using breakout cables)
N9K-C92348GC-X	The Cisco Nexus 92348GC-X switch (N9K-C92348GC-X) is a 1RU switch that supports 696 Gbps of bandwidth and over 250 mpps. The 1GBASE-T downlink ports on the 92348GC-X can be configured to work as 100-Mbps, 1-Gbps ports. The 4 ports of SFP28 can be configured as 1/10/25-Gbps and the 2 ports of QSFP28 can be configured as 40- and 100-Gbps ports. The Cisco Nexus 92348GC-X is ideal for big data customers that require a Gigabit Ethernet ToR switch with local switching.
N9K-C9272Q	2-RU Top-of-Rack switch with 72 40-Gigabit Ethernet QSFP+ ports (35 of these ports also support 4x10 breakout cables for 140 10-Gigabit ports)
N9K-C9316D-GX	1-RU switch with 16x400/100/40-Gbps ports.
N9K-C9332C	1-RU fixed switch with 32 40/100-Gigabit QSFP28 ports and 2 fixed 1/10-Gigabit SFP+ ports.
N9K-C9364C	2-RU Top-of-Rack switch with 64 40-/100-Gigabit QSFP28 ports and 2 1-/10-Gigabit SFP+ ports. - Ports 1 to 64 support 40/100-Gigabit speeds. - Ports 49 to 64 support MACsec encryption. Ports 65 and 66 support 1/10 Gigabit speeds.
N9K-C9364C-GX	2-RU fixed-port switch with 64 100-Gigabit SFP28 ports.
N9K-C93120TX	2-RU Top-of-Rack switch with 96 1/10GBASE-T (copper) ports and 6 40-Gigabit QSFP+ ports
N9K-C93128TX	3-RU Top-of-Rack switch with 96 1/10GBASE-T (copper) ports and an uplink module up to 8 40-Gigabit QSFP+ ports
N9K-C9332PQ	1-RU switch with 32 40-Gigabit Ethernet QSFP+ ports (26 ports support 4x10 breakout cables and 6 ports support QSFP-to-SFP adapters)
N9K-C9348GC-FXP	Nexus 9300 with 48p 100M/1 G, 4p 10/25 G SFP+ and 2p 100 G QSFP
N9K-C9372PX	1-RU Top-of-Rack switch with 48 1-/10-Gigabit SFP+ ports and 6 40-Gigabit QSFP+ ports
N9K-C9372PX-E	An enhanced version of the Cisco Nexus 9372PX-E switch.
N9K-C9372TX	1-RU Top-of-Rack switch with 48 1-/10GBASE-T (copper) ports and 6 40-Gigabit QSFP+ ports
N9K-C9372TX-E	An enhanced version of the Cisco Nexus 9372TX-E switch.
N9K-C9396PX	2-RU Top-of-Rack switch with 48 1-/10-Gigabit Ethernet SFP+ ports and an uplink module with up to 12 40-Gigabit QSFP+ ports
N9K-C9396TX	2-RU Top-of-Rack switch with 48 1/10GBASE-T (copper) ports and an uplink module with up to 12 40-Gigabit QSFP+ ports
N9K-C93600CD-GX	1-RU fixed-port switch with 28 10/40/100-Gigabit QSFP28 ports (ports 1-28), 8 10/40/100/400-Gigabit QSFP-DD ports (ports 29-36)

Product ID	Description
N9K-M4PC-CFP2	Cisco Nexus 9300 uplink module with 4 100-Gigabit Ethernet CFP2 ports. For the Cisco Nexus 93128TX switch, only two of the ports are active. For the Cisco Nexus 9396PX and 9396TX switches, all four ports are active.
N9K-M6PQ	Cisco Nexus 9300 uplink module with 6 40-Gigabit Ethernet QSFP+ ports for the Cisco Nexus 9396PX, 9396TX, and 93128TX switches.
N9K-M6PQ-E	An enhanced version of the Cisco Nexus N9K-M6PQ uplink module.
N9K-M12PQ	Cisco Nexus 9300 uplink module with 12 40-Gigabit Ethernet QSPF+ ports.

Cisco Nexus 9000 Series NX-OS Release Notes, Release 9.3(4)

Available Languages

Download Options

Bias-Free Language

New Software Features

New Hardware Features

Release Versioning Strategy

Open Issues

Resolved Issues

Known Issues

Behavior Changes for Cisco Nexus 9504 and 9508 Switches with -R Line Cards

General Known Issues

Device Hardware

Optics

FEX Modules

Cisco Network Insights for Data Center

Upgrade and Downgrade

Exceptions

Cisco Nexus 9316D-GX, 9364C-GX and 93600D-GX Switches

Cisco Nexus 9200, 9300-EX, and 9300-FX Platform Switches

Cisco Nexus 9500 Platform N9K-X9408PC-CFP2 Line Card and 9300 Platform Switches

N9K-X96136YC-R Line Card

N9K-X9736C-FX Line Card

Nexus 9500 Cloud Scale (EX/FX) Line Cards

Related Content

Documentation Feedback

Legal Information

Was this Document Helpful?

Contact Cisco

This Document Applies to These Products