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.
This document describes the features, issues, and exceptions of Cisco NX-OS Release 10.2(6)M software for use on Cisco Nexus 9000 Series switches.
The new Cisco NX-OS Software Release and Image-naming Convention information is available here — Cisco NX-OS Software Strategy and Lifecycle Guide.
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.
The following table lists the changes to this document:
Date |
Description |
June 28, 2024 |
Added CSCwi92006 to the Open Issues section. |
April 25, 2024 |
Added CSCwh50989 to the Open Issues section. |
September 23, 2023 |
Added CSCwb53265 to the Resolved Issues section. |
September 01, 2023 |
Cisco NX-OS Release 10.2(6)M became available. |
New and Enhanced Software Features
There are no new or enhanced features introduced in Cisco NX-OS Release 10.2(6)M.
There are no new hardware features introduced in Cisco NX-OS Release 10.2(6)M.
For details on transceivers and cables that are supported by a switch, see the Transceiver Module (TMG) Compatibility Matrix.
Unsupported Features on N9K-C92348GC
Beginning with Cisco NX-OS Release 10.1(1), the following features are not supported on N9K-C92348GC:
● VXLAN
● SW/HW Telemetry
● NetFlow/Analytics
● iCAM
● PTP
● NX-SDK
● DME, Device YANG, OpenConfig YANG, gRPC, NETCONF, RESTCONF
Note: NXAPI CLI and XML Agent (NETCONF over SSH) are supported on this platform.
Release Image
In Cisco NX-OS Release 10.2(6)M, the following two 64-bit images are supported:
● The 64-bit Cisco NX-OS image filename that begins with "nxos64-cs” (for example, nxos64-cs.10.2.6.M.bin). This image is supported on all Cisco Nexus 9000 series fixed switches as well as 9000 Modular switches with FM-E/FM-E2/FM-G.
● The 64-bit Cisco NX-OS image filename that begins with "nxos64-msll” (for example, nxos64-msll.10.2.6.M.bin). This image is supported on Cisco Nexus 9000 -R and -R2 series modular switches.
The 32-bit image is no longer supported.
Open Issues
Bug ID |
Description |
Headline: Nexus 9000- python3 crashes being observed after upgrade Symptoms: Several python3 core files are created after upgrading to 10.2.4.M. You can use the command show cores to see the cores generated.
Nexus-switch# show cores VDC Module Instance Process-name PID Date(Year-Month-Day Time) --- ------ -------- --------------- -------- ------------------------- 1 1 1 python3 --
conf t clock timezone PST -8 0 end
After having completed this configuration, you need to check from shell that localtime file has been populated.
bash-4.4# ls -al /etc/localtime -rw-r--r-- 1 root root 132 Jul 5 11:49 /etc/localtime bash-4.4# cat /etc/localtime TZif2PSTTZif2t T
bash-4.4# bash-4.4# strings /etc/localtime TZif2 TZif2 bash-4.4# |
|
Headline: Nexus 9000: 'flowcontrol send on' is configured on Port-channel after removing FEX HIF member ports. switchport switchport mode trunk switchport trunk allowed vlan 2506 spanning-tree port type edge trunk flowcontrol send on <<<Flowcontrol configuration added this way cannot be modified. |
|
Headline: Nexus 9000: Policies Applied to NVE On Border Spine Affect BUM Multicast for non-NVE OIFs |
|
Headline: N9K NBM: OIL is missing form "show ip mroute" for a static NBM flows. |
|
Headline: N9K: command "power inline auto" does not seem to work for the class 4 powered devices. |
|
Headline: Mac moves seen after flapping a member of the peer-link |
|
Headline: VTEP flooding packet from fabric back to fabric in L3VNI with host dst mac |
|
Headline: Executing Control Plane Policy stats takes longer than expected on 93360YC-FX2. ottprdoobsw01a# sho clock ; show policy-map int control ; show clo 22:31:39.884 UTC Wed Aug 09 2023 Time source is NTP Control Plane <snip> 22:32:20.513 UTC Wed Aug 09 2023 Time source is NTP
As we can observe the qos statistics takes from 50 seconds to Service not responding -
ottprdoobsw01a(config)# qos sta ottprdoobsw01a(config)# end ottprdoobsw01a# show ver intern bui ; show cloc ; show policy-map int contro | no ; sho clo nxos image file: bootflash:///nxos64-cs.10.2.4.M-statsfinal.bin : S0 03:41:31.393 UTC Sat Aug 19 2023 Time source is NTP Control Plane <snip> 03:42:20.690 UTC Sat Aug 19 2023 Time source is NTP ottprdoobsw01a# show ver intern bui ; show cloc ; show policy-map int contro | no ; sho clo nxos image file: bootflash:///nxos64-cs.10.2.4.M-statsfinal.bin : S0 03:43:58.104 UTC Sat Aug 19 2023 Time source is NTP Control Plane <snip> 03:44:37.623 UTC Sat Aug 19 2023 Time source is NTP
ottprdoobsw01a# show ver intern bui ; show cloc ; show policy-map int contro | no ; sho clo nxos image file: bootflash:///nxos64-cs.10.2.4.M-statsfinal.bin : S0 03:45:03.357 UTC Sat Aug 19 2023 Time source is NTP Service not responding 03:46:03.793 UTC Sat Aug 19 2023 Time source is NTP |
|
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. |
|
Headline: all interfaces shown input/output rate as 0pps on N9K FX2 platform Symptoms: all interfaces shown input/output rate as 0pps on N9K-FX2 platform without any operations. Impact is on N9K-FX2 switches and does not impact the N3K. Workarounds: None. |
Bug ID |
Description |
Headline: Netconf core seen when performing netconf merge operation for ospf auth. Symptoms: The symptoms are as follows: 1. NX-API Sandbox freezes and configuration does not take place on the device. After waiting for approximately 10 minutes, it unfreezes; else, clear the netconf session. 2. The policyelem process crashes. 3. The device hangs. 4. Netconf process crashes. Workarounds: None |
|
Headline: BFD auth config not displayed in "show run" after upgrade to 9.3.10, without any functional impact |
|
Headline: Nexus: Configuring overlapping IPv6 address with different mask on L3 intf does not throw error
N9K-2-382(config-if)# int loop29 N9K-2-382(config-if)# ipv6 add 2001:db0::1/72 <<< 2001:db0::1/72 configured on loop29 N9K-2-382(config-if)# no shut N9K-2-382(config-if)# int loop31 N9K-2-382(config-if)# ipv6 address 2001:db0::1/73 Address already configured on interface loopback29 <<< warning seen when the IP is duplicated
N9K-2-382(config-if)# ipv6 add 2001:db0::1/68 Address already configured on interface loopback29 <<< warning seen when the IP is duplicated
N9K-2-382(config-if)# ipv6 add 2001:db0::3/68 <<< accepted without warning |
|
Headline: N9K OS installation with no-reload option can cause BFD down |
|
Headline: Improve telemetry trace tm-error "failure reason:Value too large" |
|
Headline: N9300 sends icmp Frag needed and DF set msg to NAT Inside global instead of inside local IP |
|
Headline: Telemetry subscription of DME path sys/ptp/correction as an event is not working |
|
Headline: Logging 2.0: reduce number of instances that autcollect run to reduce load on CLI/vsh |
|
Headline: N9K-C9504 after system switchover, static route(configured static route BFD) will disappear
N9K-C9504-2(config-if)# sh module Mod Ports Module-Type Model Status --- ----- ------------------------------------- --------------------- --------- 1 52 48x10/25G + 4x40/100G Ethernet Module N9K-X97160YC-EX ok 2 52 48x10/25G + 4x40/100G Ethernet Module N9K-X97160YC-EX ok 22 0 4-slot Fabric Module N9K-C9504-FM-E ok 23 0 4-slot Fabric Module N9K-C9504-FM-E ok 24 0 4-slot Fabric Module N9K-C9504-FM-E ok 26 0 4-slot Fabric Module N9K-C9504-FM-E ok 27 0 Supervisor Module N9K-SUP-B+ active * 28 0 Supervisor Module N9K-SUP-B+ ha-standby 29 0 System Controller N9K-SC-A standby 30 0 System Controller N9K-SC-A active
N9K-C9504-2(config-if)# sh ip route 172.168.1.0 IP Route Table for VRF "default" '*' denotes best ucast next-hop '**' denotes best mcast next-hop '[x/y]' denotes [preference/metric] '%<string>' in via output denotes VRF <string>
172.168.1.0/24, ubest/mbest: 1/0 *via 192.168.2.2, Eth1/22, [1/0], 00:19:37, static
N9K-C9504-2# sh bfd neighbors dest-ip 192.168.2.2
OurAddr NeighAddr LD/RD RH/RS Holdown(mult) State Int Vrf Type 192.168.2.1 192.168.2.2 1090519046/1090519042 Up 5504(3) Up Eth1/22 default SH
The information of the engine and Routing table BFD before the switchover that looks like all normal.
After C9504 switchover:
N9K-C9504-2# sh module Mod Ports Module-Type Model Status --- ----- ------------------------------------- --------------------- --------- 1 52 48x10/25G + 4x40/100G Ethernet Module N9K-X97160YC-EX ok 2 52 48x10/25G + 4x40/100G Ethernet Module N9K-X97160YC-EX ok 22 0 4-slot Fabric Module N9K-C9504-FM-E ok 23 0 4-slot Fabric Module N9K-C9504-FM-E ok 24 0 4-slot Fabric Module N9K-C9504-FM-E ok 26 0 4-slot Fabric Module N9K-C9504-FM-E ok 27 0 Supervisor Module N9K-SUP-B+ ha-standby 28 0 Supervisor Module N9K-SUP-B+ active * 29 0 System Controller N9K-SC-A standby 30 0 System Controller N9K-SC-A active
N9K-C9504-2# sh ip route 172.168.1.0 IP Route Table for VRF "default" '*' denotes best ucast next-hop '**' denotes best mcast next-hop '[x/y]' denotes [preference/metric] '%<string>' in via output denotes VRF <string>
Route not found <<<<<<<<<
N9K-C9504-2# sh bfd neighbors dest-ip 192.168.2.2
OurAddr NeighAddr LD/RD RH/RS Holdown(mult) State Int Vrf Type 192.168.2.1 192.168.2.2 1090519046/1090519042 Up 5504(3) Up Eth1/22 default SH
The information of the engine and Routing table BFD after the switchover, found The Static routing of 172.168.1.0 disappears. |
|
Headline: m9700::non-sysmgr cores are seen after topology configuration |
|
Headline: License information unavailable and showing error after ISSU
<pre> switch01# <b>show license usage</b> Could not get license usage: License server is busy. Please retry in a few seconds. switch01# <b>show license authorizations</b> Could not get data authorizations info: err=144
switch01# <b>show license status</b> Could not get utility info: err=1
show_utility_info failed Smart Licensing using Policy: Status: ENABLED
Could not get data privacy info: err=1 </pre> |
|
Headline: LC module goes to failure state while collecting show tech binary after ISSU
`show cores` VDC Module Instance Process-name PID Date(Year-Month-Day Time) --- ------ -------- --------------- -------- ------------------------- 1 10 1 fln_que 1201 2018-10-22 17:25:12 1 1 1 fln_que 1202 2018-10-22 17:25:26
`show module internal exceptionlog`
********* Exception info for module 10 ********
exception information --- exception instance 1 ---- Module Slot Number: 10 Device Id : 134 Device Name : System Manager Device Errorcode : 0x00000426 Device ID : 00 (0x00) Device Instance : 00 (0x00) Dev Type (HW/SW) : 04 (0x04) ErrNum (devInfo) : 38 (0x26) System Errorcode : 0x401e008a Service on linecard had a hap-reset Error Type : FATAL error PhyPortLayer : 0x0 Port(s) Affected : Error Description : fln_que hap reset DSAP : 0 (0x0) UUID : 1 (0x1) Time : Mon Oct 22 17:25:26 2018 (Ticks: 5BCDBAAE jiffies) |
|
Headline: SNMPd Crashes when Configuring 'event snmp-notification' EEM Script |
|
Headline: BGP AS not updated properly in Netflow flow cache |
|
Headline: PIM-Process Crash |
|
Headline: OSPF Process is increasing memory utilization
%OSPF-1-NOMEM: ospf-XXXX [16983] Malloc (65571 bytes) failed for: OSPF_MEM_CMI_SNAPSHOT %OSPF-4-SYSLOG_SL_MSG_WARNING: OSPF-1-NOMEM: message repeated 5 times in last 46375039 sec
> "MemUsed" is very close to the "MemLimit" for the OSPF process
# show processes memory sort
PID MemAlloc MemLimit MemUsed StackBase/Ptr Process ----- -------- ---------- ---------- ----------------- ---------------- 9035 1560645632 2066057164 2066014208 ffe3af40/ffe3a760 ospf >>> 9026 126746624 1451523033 719093760 fff470f0/fff46fd0 mrib 8816 153280512 1588493555 717537280 ffd696b0/ffd69180 igmp 8235 87703552 1419916377 700219392 ffa2e8e0/ffa2e540 arp 8861 208924672 1059769830 699904000 ffe15c20/ffe1409c monitor |
|
Headline: Deprecated OSPF Network Commands seen in the running-config after an upgrade. |
|
Headline: EIGRP distribution-list out allows route that should be denied after SSO |
|
Headline: Port LED is not working correctly for N9K-C9364D-GX2A |
|
Headline: Remove CLI to configure Fill Pattern as only IDLE is supported |
|
Headline: Static MACs conf on int NVE deleted from vPC secondary after int NVE shut/no shut on vPC primary
no vlan <vlan_id> vlan <vlan_id> vn-segment <segment-id>
mac address-table static <mac_address> vni <segment-id> interface nve 1 peer-ip <IP_address> |
|
Headline: IF-MIB : IFHIGHSPEED object returns wrong interface speed values for internal interfaces (ii x/y/z)
snmpwalk -v 2c -c test <ip_address> iso.3.6.1.2.1.31.1.1.1.15.1241513984 IF-MIB::ifHighSpeed.1241513984 = Gauge32: 42000 < --------- expecting 100000
`show hardware internal tah all-ieth-ports` is reporting 100G for both ieth and fp ports.
This problem is not seen if you query front-port interface like Eth1/1:
snmpwalk -v 2c -c test <ip_address> iso.3.6.1.2.1.31.1.1.1.15.436207616 IF-MIB::ifHighSpeed.436207616 = Gauge32: 100000 |
|
Headline: N_DEV-125 ipfib core is seen
%SYSMGR-SLOT7-2-SERVICE_CRASHED: Service "ipfib" (PID 14754) hasn't caught signal 11 (core will be saved). %SYSMGR-SLOT7-2-HAP_FAILURE_SUP_RESET: Service "ipfib" in vdc 1 has had a hap failure
This might cause a linecard unexpected reboot.
`show system reset-reason module x` Error code : 1075708042 Reset reason : ipfib hap reset => [Failures < MAX] : powercycle Service name : System manager Time stamp : At 12926 usecs after Tue Jun 13 15:16:04 2023
This is a case where routine used to delete routes has failed in HAL. When Mfib receives the response from HAL, it tries to delete the route again, causing a loop. In this case, trigger seems to be a route delete. |
|
Headline: POAP not listing all the breakout options supported |
|
Headline: N9K-C93180YC-FX3: GNSS LED is red when GPS/GNSS is not connected and SyncE not configured |
|
Headline: Generation of non-sysmgr core while collecting pss dump of a corrupted db |
|
Headline: Unable to unconfigure extcommunity-list , if we use the same in 2 route-map at a time
513E-A-17-N93180YC-FX-1(config)# no ip extcommunity-list standard list3 seq 10 permit 4byteas-generic transitive 100:200 513E-A-17-N93180YC-FX-1(config)# sh running-config rpm
!Command: show running-config rpm !Running configuration last done at: Fri Mar 17 02:13:18 2000 !Time: Fri Mar 17 02:13:22 2000
version 10.2(5) Bios:version 05.47 ip extcommunity-list standard list3 seq 10 permit 4byteas-generic transitive 100:200 route-map rmap5 permit 10 match extcommunity list3 route-map rmap6 permit 10 match extcommunity list3 |
|
Headline: Nexus C9364C-GX - Golden EPLD upgrade times out and resets with Fatal Module Error
N9K-C9364C-GX# install epld bootflash:[epld-image] module all golden ... The switch will be reloaded at the end of the upgrade Do you want to continue (y/n) ? [n] y
Proceeding to upgrade Modules.
Starting Module 1 EPLD Upgrade
Module 1 : MI FPGA [Programming] : 100.00% ( # of # sectors)
EPLD process seems to have exited unexpectedly 2700
Unable to communicate with the EPLD Process
Reloading Supervisor Module 1 ...
Last reset at [USECS] usecs after [DATE] Reason: Reset Requested due to Fatal Module Error System version: [IMAGE] Service: |
|
Headline: Nexus 9000 doesn't configure contact and location for snmp.
switch# conf t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# snmp-server location HEREDIA wrong length of value being set switch(config)# switch(config)# snmp-server location Alain wrong length of value being set |
|
Headline: Memory leak on acllog "acllog_net_l2_pkt_handle" |
|
Headline: There is mismatch between Scalability Doc and the threshold configured on the switch |
|
Headline: CLI CR failing with default radius server configs 1) CLI Config-Replace fails with default 'radius' server group 2) Default 'radius' entry is shown in running-config even after defaulting/removing its children config |
|
Headline: N9K VxLAN: MAC Mobility Sequence is not getting incremented for mac only bgp update · After moving host from one leaf to the other, mac mobility sequence is not getting incremented for mac only bgp update. · For Mac-ip MAC Mobility Sequence gets incremented. Workarounds: Use clear mac address-table dynamic address <address> command. |
|
Headline: Rx Pause enabled in h/w even when flow control is disabled in s/w causing pause frames to be honoured · Rx Pause enabled in hardware even when flow-control is disabled in Software causing pause frames to be honoured. · As these pause frames are honoured in the hardware, might cause packet drops/performance issues for both Unicast and Multicast Traffic. Workarounds: None |
|
Headline: snmpbulkget to ciscoEntityFRUControlMIB create invalid unicode in sh snmp internal event-his pktdump |
|
Headline: Memory leak at FEX unit |
|
Headline: Internal BGP routes are getting installed as External routes with an AD of 20 in the Routing Table
show bgp vrf all all Status: s-suppressed, x-deleted, S-stale, d-dampened, h-history, *-valid, >-best Path type: i-internal, e-external, c-confed, l-local, a-aggregate, r-redist, I-injected Origin codes: i - IGP, e - EGP, ? - incomplete, | - multipath, & - backup, 2 - best2
*>e10.0.0.0/24 192.168.0.1 0 64500 64501 ? * i 192.168.1.1 100 0 64500 64501 ? *|i 192.168.1.2 100 0 64500 64501 ? * i 192.168.1.3 100 0 64500 64501 ?
We can see that eBGP route with next hop 192.168.0.1 was selected as best (>) and iBGP route with next hop 192.168.1.2 as multipath (|). |
|
Headline: Maximum routes X warning-only starts dropping routes under VRF |
|
Headline: N9k | PBR Traffic may egress out via incorrect interfaces under certain conditions |
|
Headline: Nexus 9000 VxLAN virtual peer-link tunnel recovery failure.
<pre> N9k-SW01# show vpc brief <snip> Legend: (*) - local vPC is down, forwarding via vPC peer-link
vPC domain id : 1 Peer status : peer adjacency formed ok vPC keep-alive status : peer is alive Configuration consistency status : success Per-vlan consistency status : success Type-2 consistency status : success vPC role : secondary Number of vPCs configured : 10 Peer Gateway : Enabled Dual-active excluded VLANs : - Graceful Consistency Check : Enabled Auto-recovery status : Enabled, timer is off.(timeout = 360s) Delay-restore status : Timer is off.(timeout = 150s) Delay-restore SVI status : Timer is off.(timeout = 10s) Operational Layer3 Peer-router : Disabled Virtual-peerlink mode : Enabled
vPC Peer-link status --------------------------------------------------------------------- id Port Status Active vlans -- ---- ------ ------------------------------------------------- 1 Po500 up - </pre> - The switch shows ICMP connectivity and a route installed to the remote vMCT loopback IP - The switch shows vPC vlans in an error state due to "vPC peer is not reachable over cfs" <pre> N9k-SW01# show interface status err-vlans
-------------------------------------------------------------------------------- Port Name Err-Vlans Status -------------------------------------------------------------------------------- Po500 "vpc-peer-link" 1,1401-1404,1406-1407,1411- vPC peer is not 1412,1421,1424,1429-1430,14 reachable over 37-1440,3201-3207 cfs </pre> |
|
Headline: N9300-GX: One or more interfaces are configured with an all zero MAC |
|
Headline: LPM entry gets stuck after multiple bgp withdraws
show hardware internal tah l3 v4lpm prefix 20.20.48.0/24 table 1"
**EPE label *Flags: CC=Copy To CPU, SR=SA Sup Redirect, DR=DA Sup Redirect, TD=Bypass TTL Dec, DC=SA Direct Connect,DE=Route Default Entry, LI=Route Learn Info,HR=Host as Route Idx | vrf | ip/len | mpath | nump | base/l2ptr |cc|sr|dr|td|dc|de|li|hr| -----------|---------|--------------------------------|-------|-------|------------|--|--|--|--|--|--|--|--| 13/711 | 1 | x.x.x./24 | 0 | 0 | 0x50005 | | | | | | | | | <<<<<<<< "No ECMP" path entry not cleared 7/799 | 1 | x.x.x.x/24 | 1 | 2 | 0x400004e1 | | | | | | | | |. <<<<< new ECPM entry
1. Clear the route works as a temporary workaround, as this forces nxos to put the ECMP entry at the top. However, if another withdraw occurs we end up hitting the same condition.
clear ip route x.x.x.x/x
2. Clear the LPM entry works as a better workaround. However, if the constant withdraws continue it might end up hitting the same condition
Attach module 1 ; clear hardware internal tah l3 ipv4 tcam-bank z tcam-index y Idx | vrf | ip/len | mpath | nump | base/l2ptr |cc|sr|dr|td|dc|de|li|hr| -----------|---------|--------------------------------|-------|-------|------------|--|--|--|--|--|--|--|--| Z/Y | 1 | x.x.x.x/x | 1 | 2 | 0x------------ | | | | | | | | | |
|
Headline: 92348GC consuming -XF license instead of -GF license |
|
Headline: Unicast route create failed and N9K tahusd crashed After 1 second, service "tahusd" crashed.
2023 Feb 13 10:04:41.230 %$ %IPFIB-SLOT1-2-UFIB_ROUTE_CREATE: Unicast route create failed for INS unit 0, VRF: 1, xxx.xxx.xx.0/24, flags:0x0, intf:0x40000087, Error: Trie Hw write failed(220) 2023 Feb 13 10:04:41.230 %$ %IPFIB-SLOT1-2-UFIB_ROUTE_CREATE: Unicast route create failed for INS unit 0, VRF: 1, xxx.xxx.xx.0/24, flags:0x0, intf:0x40000087, Error: Trie Hw write failed(220) 2023 Feb 13 10:04:41.230 %$ %IPFIB-SLOT1-2-UFIB_ROUTE_CREATE: Unicast route create failed for INS unit 0, VRF: 1, xxx.xxx.xx.0/24, flags:0x0, intf:0x40000087, Error: Trie Hw write failed(220) 2023 Feb 13 10:04:42.245 %$ %SYSMGR-SLOT1-2-SERVICE_CRASHED: Service "tahusd" (PID 25057) hasn't caught signal 11 (core will be saved). 2023 Feb 13 10:04:42.248 %$ %SYSMGR-SLOT1-2-HAP_FAILURE_SUP_RESET: Service "tahusd" in vdc 1 has had a hap failure 2023 Feb 13 10:04:42.249 %$ %SYSMGR-SLOT1-2-LAST_CORE_BASIC_TRACE: fsm_action_become_offline: PID 10840 with message Could not turn off console logging on vdc 1 error: mts req-response with syslogd in vdc 1 failed (0xFFFFFFFF) . 2023 Feb 13 10:05:21.343 %$ %KERN-2-SYSTEM_MSG: [ 4542.138123] usd process 25057, uuid 1356 (0x54c) tahusd failed to send heartbeat - kernel
show system reset-reason 1) At 647356 usecs after Mon Feb 13 10:07:08 2023 Reason: Reset Requested due to Fatal Module Error Service: tahusd hap reset Version: 9.3(9)
* You may also observe UFIB_MULTIPATH_TABLE_EXHAUSTION: Unicast ecmp table exhausted. |
|
Headline: Certain interfaces shown input/output rate as 0pps on N9K GX platform 1.The issue can be cleared after flapped one of those ports. 2.Reactivate the DMA state with internal commands. 3.Connecting a new terminal to the port to which the DMA Group belongs will reactivate the DMA Group. |
|
Headline: xbar multicast show command causes 300MB of memory to be allocated
switch# show processes memory | i "All processes" All processes: MemAlloc = 20795484
switch# show system internal xbar mem-stats detail | i XBM_MEM_xbm_mcast_group_info_t switch# show system internal xbar multicast_id all switch# show system internal xbar mem-stats detail | i XBM_MEM_xbm_mcast_group_info_t 18 XBM_MEM_xbm_mcast_group_info_t 512 512 307761152 307761152
switch# show processes memory | i "All processes" All processes: MemAlloc = 21096364 |
|
Headline: SYSMGR-3-CFGWRITE_FAILED: Configuration copy failed due to 100% usage of startup-cfg 2023 Feb 10 13:17:11.746 N3k %PSS-0-PSS_WRITE_DATA_FAILURE: aclmgr: failed to write data to /var/sysmgr/startup-cfg/bin/aclmgr_start_cfg_user block 8785: partial write 2023 Feb 10 13:17:11.746 N3k%PSS-0-PSS_WRITE_DATA_FAILURE: aclmgr: failed to write data to /var/sysmgr/startup-cfg/bin/aclmgr_start_cfg_user block 8785: partial write (message repeated 1 time) 2023 Feb 10 13:17:11.746 N3k %PSS-0-PSS_WRITE_FAILURE: aclmgr: failed to write data: Operation not permitted 2023 Feb 10 13:17:11.760 N3k %SYSMGR-3-CFGWRITE_SRVFAILED: Service "aclmgr" failed to store its configuration (error-id 0x4048000C). 2023 Feb 10 13:17:11.927 N3k %SYSMGR-2-CFGWRITE_ABORTED: Configuration copy aborted. 2023 Feb 10 13:17:14.017 N3k %SYSMGR-3-CFGWRITE_FAILED: Configuration copy failed (error-id 0x401E0000).
switch# show system internal flash | in Mount|startup Mount-on 1K-blocks Used Available Use% Filesystem /var/sysmgr/startup-cfg 102400 90632 11768 89 none switch# |
|
Headline: BGP External-Fallover not working when TTL-Security is enabled eBGP non multihop sessions)
2023 Feb 20 09:50:47 N9K-2 %ETHPORT-5-IF_DOWN_PARENT_DOWN: Interface Ethernet1/47.3182 is down (Parent interface is down) 2023 Feb 20 09:50:47 N9K-2 %ETHPORT-5-IF_DOWN_ADMIN_DOWN: Interface Ethernet1/47 is down (Administratively down) 2023 Feb 20 09:51:03 N9K-2 %BGP-5-ADJCHANGE: bgp- [22583] (VPN_IC) neighbor 10.83.1.25 Down - sent: holdtimer expired error
|
|
Headline: Kernel panic due to "Fatal Module Error" after ND ISSU on N9K-C9348GC-FXP |
|
Headline: N9K CoPP logging drop threshold dropped count changes to a large value after upgrade to 64-bit image
On a 32-bit NXOS image, ex: nxos.7.0.3.I7.9.bin:
policy-map type control-plane copp-policy-strict-custom class copp-class-l3uc-data-custom logging drop threshold 7500 level 1
After upgrading to 64-bit image, nxos64-cs.10.3.2.F.bin:
policy-map type control-plane copp-policy-strict-custom class copp-class-l3uc-data-custom set cos 1 logging drop threshold 32212254720000 level 1
C93180YC-FX(config-pmap-c)# show policy-map int control-plane Control Plane
Service-policy input: copp-policy-strict-custom
class-map copp-class-l3uc-data-custom (match-any) match exception glean threshold: 32212254720000, level: 1
The logging drop drop-count increased to a large value after upgrading.
The new drop-count value cannot be overwritten or removed:
C93180YC-FX(config-pmap-c)# logging drop threshold 7500 level 1 C93180YC-FX(config-pmap-c)# do sh run | beg "class copp-class-l3uc-data-custom" class copp-class-l3uc-data-custom logging drop threshold 32212254720000 level 1
C93180YC-FX(config)# policy-map type control-plane copp-policy-strict-custom C93180YC-FX(config-pmap)# class copp-class-l3uc-data-custom C93180YC-FX(config-pmap-c)# no logging drop threshold 32212254720000 level 1 ^ % Invalid number, range is (1:80000000000) at '^' marker. · Remove logging drop threshold command from the configuration · Save the configuration Upgrade to the 64-bit image · Add logging drop threshold command to the configuration · Save the configuration
The following workaround is disruptive: · Enable one of the CoPP built in templates · Remove the custom CoPP policy configuration · Recopy the CoPP profile Configure a new logging drop threshold for each class |
|
Headline: N9K: "show spanning-tree internal info global" command output truncated "SWOVER Timeout" |
|
Headline: Nexus 9K Unexpected Reload due to Watchdog with High "ktah_nl_asic_isr" Interrupts
<pre>SWITCH# show system reset-reason ----- reset reason for module 1 (from Supervisor in slot 1) --- 1) At 431246 usecs after Sun Jan 1 00:00:00 2023 Reason: Watchdog Timeout Service: Version: 9.3(9)
SWITCH# show logging onboard stack (snip)
************************************************************** STACK TRACE GENERATED AT Sun Jan 1 00:00:00 2023 UTC ************************************************************** (snip)
<0>[XXXXXXXX.XXXXXX] NMI due to BROADWELL_FPGA_WDT_GPIO_LEVEL_MASK error (snip)
<6>[XXXXXXXX.XXXXXX] Dumping interrupt statistics <6>[XXXXXXXX.XXXXXX] CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 intrs/last_sec max_intrs/se (snip)
<6>[XXXXXXXX.XXXXXX] 50: 0 92735896 313 0 0 0 0 0 655 2871 PCI-MSI-edge ktah_nl_asic_isr</pre> |
|
Headline: show process memory should be available for network-operator role |
|
Headline: N9300 NBM related syslog does not comply with standard nxos syslog format |
|
Headline: Syslog %LICMGR-6-LOG_LICAPP_SMART_GLOBAL_CHANGE removal |
|
Headline: Revert reserved MAC blocking behavior for VRRP macs on SVIs |
|
Headline: N9K-C9364C Interface counters is stuck due to EDMA Channel Stuck
2022-12-14T19:16:54.663049000+09:00 [M 1] [tahusd] E_STRING [tahusd_edma_handle_dma_timer_event (2267)] inst = 0 EDMA Reserve Channel 6 Stuck 2022-12-14T19:16:54.663049000+09:00 [M 1] [tahusd] E_STRING [tahusd_edma_handle_dma_timer_event (2266)] inst = 0 EDMA Reserve Channel 6 Stuck |
|
Headline: n9k: urib core seen leaving only local routes on switch ``` %KERN-3-SYSTEM_MSG: [6867726.665799] (1:273:1)urib[3871]: rwsem_flush process/thread still exist (1:273:1009)urib:urib-dme-t[3894] - kernel %KERN-3-SYSTEM_MSG: [6867726.665814] (1:273:1)urib[3871]: rwsem_flush 1 threads still exist - kernel %SYSMGR-2-SERVICE_CRASHED: Service "urib" (PID 3871) hasn't caught signal 6 (core will be saved). ``` The switch remains up but since this process operated the Unicast RIB table, routing information is lost for a short moment. The tables will be repopulated and normal operation should resume. |
|
Headline: Memory leak under PIM_MEM_ECMP_REDIR_Q_ENTRY on Nexus9000 1. Identify any device and flow responsible for hundreds of thousands of ECMP Redir Queue entries using the CLI command "show ip pim internal ecmp-redir queue". 2. Block the problem IP(s) using an ACL caused the PIM_ECMP_REDIR_Q_ENTRY to stop growing. |
|
Headline: C93600CD-GX: VPC BGW peer reload might cause up to 20s of traffic Blackhole |
|
Headline: gnmic reply missing key-value pairs due to PropertyName=<> is_set=0 and is_default_defined=0 |
|
Headline: Credit Loss Recovery not triggered for FC interface with no transmit credits
The <b>show interface</b> output shows the affected interface is up but with 0 transmit credits available. Some frames may have been transmitted.
<pre> fc1/1 is up ... Port mode is F, FCID is 0x123456 ... Operating Speed is 8 Gbps ... 3107 frames output,186756 bytes 0 discards,0 errors ... 0 transmit B2B credit remaining 0 low priority transmit B2B credit remaining </pre>
The output of <b>slot 1 show logging onboard credit-loss</b> does not contain any recovery events for the interface. |
|
Headline: N9K: Error or incorrect result when computing multiple file hashes simultaneously |
|
Headline: Routes with BGP backup route will not get advertised to a BGP peer |
|
Headline: Show commands collected via NX-API have missing character with 8k fastcgi buffers. |
|
Headline: N9K BGP peer session stuck in Closing with AF LU prefix-priority high |
|
Headline: eBGP-Removing template peer-policy under l2vpn EVPN address-family deletes prefixes |
|
Headline: Stuck MDIO access with BV ports leads to missed HBs and USD kill. |
|
Headline: Storm-Control CC fail even though Policer/Burst values are correct |
|
Headline: Nexus 9000 pruning VLANs even when VTP Pruning is not enabled -------------------------------------------------------------------------------- Port Vlans in spanning tree forwarding state and not pruned -------------------------------------------------------------------------------- Eth1/1 none Eth1/45 none Eth1/53 none Eth1/54 none Po1 2000-2001,3600 Po2 2000-2001,3600 Po500 1,4-6,30-32,34-35,74,200-207,209-212,214,216,219-220,224-228,232-240,242-244,246-249,253,271-272,291,298,514,531,533,535,543,583,593,730,732-734,950,2000-2001,3600 no feature vtp feature vtp vtp domain cisco |
|
Headline: Object Tracking si not being created when using ip options
test# config t Enter configuration commands, one per line. End with CNTL/Z. test(config)# track 1 ip sla 1 reachability ERROR: % Object does not exist test(config)#
Accounting log shows:
Tue Apr 4 22:43:30 2023:type=update:id=10.21.66.63@pts/0:user=admin:cmd=configure terminal ; track 1 ip sla 1 reachability (FAILURE)
Also, when creating an ip sla and exiting it, an invalid mode is shown. test# config t Enter configuration commands, one per line. End with CNTL/Z. test(config)# ip sla 2 test(config-ip-sla)# exit ## Invalid mode ## # ## Invalid mode ## # ## Invalid mode ## # show ip int brief
IP Interface Status for VRF "default"(1) Interface IP Address Interface Status Vlan100 1.1.1.1 protocol-up/link-up/admin-up Vlan200 2.2.2.1 protocol-up/link-up/admin-up ## Invalid mode ## #
|
|
Headline: N9K: Install epld <image name> module all does not upgrade the system controller in slot 30 |
|
Headline: N9K FX3 VTEP does not perform VXLAN encapsulation when transmitting GRE packets |
|
Headline: Auto-complete for VRF name can cause unexpected config changes
For commands such as "show run vrf" or "vrf member" the auto-complete feature doesn't kick in but for the command "no vrf context" the auto-complete feature kicks in, it means that the switch will delete the VRF starting with that letter instead of showing a message that the VRF doesn't exist, this behavior can lead customer to delete a VRF by mistake causing network disruptions.
* For the following tests, type the first letter of the VRF's name and hit enter. Don't use TAB key.
------------------- 1. Starting with the following VRFs created: -------------------
SWITCH(config-if)# show vrf VRF-Name VRF-ID State Reason ANOTHERTEST 6 Up -- <<< default 1 Up -- management 2 Up --
------------------- 2. Checking the behavior with show run -------------------
SWITCH# show run vrf A
!Command: show running-config vrf A <<< Auto-complete didn't kick in
------------------- 3. Assigning a VRF to an interface -------------------
SWITCH(config)# inter e1/1 SWITCH(config-if)# vrf member A Warning: Deleted all L3 config on interface Ethernet1/1 VRF A does not exist. Create vrf to make interface Ethernet1/1 operational <<< Auto-complete feature is not triggered the switch logs a message
---------------- 4. Delete none-existing VRF "A" -----------------
SWITCH(config-if)# no vrf context A <<< "A" vrf doesn't exist but the switch will auto-complete and will delete vrf "ANOTHERTEST"
SWITCH(config)# show vrf VRF-Name VRF-ID State Reason default 1 Up -- management 2 Up --
No message was shown for the not existing VRF and due to auto-complete feature, the VRF starting with the letter A was deleted. · Make sure to write all the VRF name while deleting a VRF. Use TAB key to auto-complete, however this options is not always possible for example when using scripts for automation. |
|
Headline: Netflow traffic getting dropped under Custom CoPP class-default |
|
Headline: vsh.bin service crashed in Nexus 9k
2023 Apr 11 08:14:50.828 netb1d1-brtr040b %$ VDC-1 %$ %SYSMGR-2-LAST_CORE_BASIC_TRACE: : PID 8735 with message vsh.bin(non-sysmgr) crashed, core will be saved .
show cores VDC Module Instance Process-name PID Date(Year-Month-Day Time) --- ------ -------- --------------- -------- ------------------------- 1 1 1 vsh.bin 8735 2023-04-11 08:15:01 |
|
Headline: Seeing error logs on upgrade: invalid group file entry delete line 'aaa-db-operator:508:'? No |
|
Headline: VLAN Filter Allows an ACL with the 'log' keyword to be used when applied to a non-existent VLAN |
|
Headline: BGP core file generated after using "show l2vpn vpn route x.x.x.x" command 1) BGP core file generated on N9K after using the command: "show l2vpn vpn route x.x.x.x". 2) Asserts seen when displaying BGP routes
It was first documented in N9K running 10.2(4) but it can happen in non-patched version. The BGP core is generated with show l2vpn vpn route 0.0.0.0 but it might happen with other routes.
It can happen with the following logs when the show command is executed:
2023 Apr 21 19:11:05 sp4.tmp1 %BGP-3-ASSERT: bgp- [16130] ../routing-sw/routing/bgp/bgp_path.c:84: Assertion `bgp_path_base_has_ext_path(path_base)' failed. 2023 Apr 21 19:11:05 sp4.tmp1 %BGP-3-ASSERT: bgp- [16130] -Traceback:XXXXXXXXXXXXX 2023 Apr 21 19:11:05 sp4.tmp1 %KERN-3-SYSTEM_MSG: [ 1102.196122] (1:283:1003)bgp:bgp-mts[26675]: rwsem_flush process/thread still exist (1:283:1049)bgp:bgp-cli-tra[32084] - kernel 2023 Apr 21 19:11:05 sp4.tmp1 %KERN-3-SYSTEM_MSG: [ 1102.196126] (1:283:1003)bgp:bgp-mts[26675]: rwsem_flush 1 threads still exist - kernel 2023 Apr 21 19:11:05 sp4.tmp1 %SYSMGR-2-SERVICE_CRASHED: Service "bgp" (PID 16130) hasn't caught signal 11 (core will be saved). 2023 Apr 21 19:11:11 sp4.tmp1 %BGP-5-ADJCHANGE: bgp- [32090] (default) neighbor fe80::XXXX:XXXX:XXXX:XXXX Up <snip> 2023 Apr 21 19:11:18 sp4.tmp1 %BGP-5-ADJCHANGE: bgp- [32090] (default) neighbor fe80::af3:fbff:fe6a:33fe Up 2023 Apr 21 19:11:36 sp4.tmp1 %BGP-3-ASSERT: bgp- [32090] ../routing-sw/routing/bgp/bgp_path.c:84: Assertion `bgp_path_base_has_ext_path(path_base)' failed. 2023 Apr 21 19:11:36 sp4.tmp1 %BGP-3-ASSERT: bgp- [32090] -Traceback: XXXXXXXXXXXXX 2023 Apr 21 19:11:37 sp4.tmp1 %SYSMGR-2-SERVICE_CRASHED: Service "bgp" (PID 32090) hasn't caught signal 11 (core will be saved). 2023 Apr 21 19:11:43 sp4.tmp1 %BGP-5-ADJCHANGE: bgp- [1314] (default) neighbor fe80::XXXX:XXXX:XXXX:XXXX Up |
|
Headline: vsh.bin fails after setting a SPAN capture with thousands of source vlans on a single session
switch(config-monitor)# source vlan 31-3999 ^ reserved vlans 3968-3999 at '^' marker.
switch(config-monitor)# source vlan 31-3967 Warning: Tx Vlan Span is not supported
2023 Mar 8 10:10:07 switch %SYSMGR-2-LAST_CORE_BASIC_TRACE: : PID 19845 with message vsh.bin(non-sysmgr) crashed, core will be saved .
switch# show cores VDC Module Instance Process-name PID Date(Year-Month-Day Time) --- ------ -------- --------------- -------- ------------------------- 1 1 1 vsh.bin 19845 2023-03-08 10:10:07 |
|
Headline: Nexus 9000 - N2K HIF interface configurations erased while upgrading to NX-OS 10.2(4)
- Configurations on all N2K HIF interface configurations partially erased. - Interfaces were in inactive status, As 'switchport access vlan x' was missing from HIF interfaces.
Before the Upgrade: ------------------------ interface Ethernet102/1/17 description xxxxx switchport access vlan x spanning-tree port type edge no shutdown
After the Upgrade: ---------------------- interface Ethernet102/1/17 description xxxxxx switchport no shutdown
- Added missing configuration to problematic interfaces and the CLI was accepting missing configurations but configurations were not reflected in running-configuration. |
|
Headline: Block `evpn multisite dci-tracking` and `evpn multisite fabric-tracking` on BGW SVI
Site2-BGW1# show nve multisite dci-links Interface State --------- ----- Vlan144 Up <<<< SVI added to DCI tracking makes BGW think DCI connectivity is still present Ethernet1/2 Down |
|
Headline: NXOS: Special character ">" causing issues with clear-text key-string in key chain |
|
Headline: Debug message of PTP cause crash |
|
Headline: Enabling "feature intersight" on 10.2(4) or 10.2(5) leaves TCP Port 9002 open to telnet and http |
|
Headline: Configuring track in role-interface mode can cause vsh crash |
|
Headline: N9K - VPC ports stuck into STP BLK state on secondary VPC after vPC Fabric Peering sync is recovered
EVIDENCE:
- On secondary Nexus VPC, output from "show logging logfile" shows that vPC port-channel was unblock:
switch# show logging logfile <snip> %STP-2-VPC_PEER_LINK_INCONSIST_UNBLOCK: vPC peer-link inconsistency cleared unblocking port-channel100 MST0001. %STP-2-VPC_PEER_LINK_INCONSIST_UNBLOCK: vPC peer-link inconsistency cleared unblocking port-channel1 MST0001.
- Output from "show spanning-tree" show that vPC peer-link port-channel is in Forwarding state, but the vPC port-channel still in Blocking state:
switch# show spanning-tree mst <snip> Interface Role Sts Cost Prio.Nbr Type ---------------- ---- --- --------- -------- -------------------------------- Po1 Root FWD 20000 128.4096 (vPC peer-link) Network P2p <<<<<<<< Peer-link in Forwarding (FWD) state Po100 Desg BLK 200 128.4195 (vPC) Edge P2p <<<<<<<<<<<<<<<<<<<<< VPC port in Blocking (BLK) state |
|
Headline: VXLAN VLANs suspended by vpc consistency checker due to different replication mode and VNI type |
|
Headline: Reduce severity of syslog when mc-drop command is enabled |
|
Headline: OSPFv3 is adding a link-local forwarding address for NSSA type 7 originated routes |
|
Headline: N9K -FX3: VXLAN storm-control policer fabric bandwidth does not update after fabric link flap |
|
Headline: Ports of C93600CD-GX with QSA (10G) don't forward traffic |
|
Headline: Debug hardware internal command on N9K-C93360YC-FX2 causes tahusd crash |
|
Headline: N9300-FX3S/FX3 may randomly timeout syncE peer |
|
Headline: Fibre Channel snmp trap configuration causing CLI to hang switch(config)# snmp-server enable traps fcdomain dmDomainIdNotAssignedNotify ^CFailed to collect returned stimulus switch(config)#
switch(config)# feature interface-vlan ^CFailed to collect returned stimulus switch(config)#
switch(config)# vlan 10 ^V^CFailed to collect returned stimulus switch(config)# |
|
Headline: tahusd crash due to InPhi retimer quad port dead lock |
|
Headline: N9K: "radius-server key <>" missing after ND ISSU |
|
Headline: N9500-G - Total Power Allocated (budget) is incorrect calculation |
|
Headline: N9K Reset-Reason is not showing correctly after module power cycle |
|
Headline: Nexus 9500 -R modules incorrect outer DMAC after initialization |
|
Headline: FEX 2348UPQ brings hosts link too fast after powercycle causing traffic blackholing for around 1min. |
|
Headline: n9k/NXOS - QOS policer/CIR - traffic rate policed 1% below configured CIR |
|
Headline: %NFM-1-RTP_FLOW_ERROR_DETECTED - CLI execution slowness seen
This is because if large unique flows present, for every flow that become from lossless to lossy, a new syslog is logged. Same is true for lossy to lossless. |
|
Headline: duplicate bia seen on N9K - GX ports 1-24 gets unique BIA mac, then the same set of BIA macs are assigned for the next set of ports 25-48. LEAF35-PMN-SOLN-WOLFRIDGE(config)# sh system internal ethpm info all | inc "Backplane MAC address in GLDB" | sort | uniq -c | excl '1 Backp' 2 Backplane MAC address in GLDB: 10:b3:d6:bc:54:68 2 Backplane MAC address in GLDB: 10:b3:d6:bc:54:70 2 Backplane MAC address in GLDB: 10:b3:d6:bc:54:78 2 Backplane MAC address in GLDB: 10:b3:d6:bc:54:80 2 Backplane MAC address in GLDB: 10:b3:d6:bc:54:88 2 Backplane MAC address in GLDB: 10:b3:d6:bc:54:90 2 Backplane MAC address in GLDB: 10:b3:d6:bc:54:98 2 Backplane MAC address in GLDB: 10:b3:d6:bc:54:a0 2 Backplane MAC address in GLDB: 10:b3:d6:bc:54:a8 2 Backplane MAC address in GLDB: 10:b3:d6:bc:54:b0 2 Backplane MAC address in GLDB: 10:b3:d6:bc:54:b8 2 Backplane MAC address in GLDB: 10:b3:d6:bc:54:c0 LEAF35-PMN-SOLN-WOLFRIDGE(config)# |
|
Headline: 'ip dhcp relay' commands are not retained on SVI after changing VRF membership
N9K-1(config-if)# show run int vlan 10
!Command: show running-config interface Vlan10 !Running configuration last done at: Wed Mar 29 20:01:02 2023 !Time: Wed Mar 29 20:01:08 2023
version 10.3(3) Bios:version 08.39
interface Vlan10 no shutdown vrf member A ip address 10.1.1.1/24 ip pim sparse-mode ip pim border ip pim hello-interval 300000 ip dhcp relay address 129.132.128.135 ip dhcp relay address 129.132.128.199
N9K-1(config-if)#
N9K-1(config-if)# vrf member B Warning: Please ensure igmp snooping is enabled on the corresponding vlan, using the command 'show ip igmp snooping vlan <x>'. IGMP snooping MUST be enabled for correct forwarding functionality.
N9K-1(config-if)# end
[+] After changing the VRF membership for Vlan10 the 'ip dhcp relay' commands are gone
N9K-1# show run int vlan 10
!Command: show running-config interface Vlan10 !Running configuration last done at: Wed Mar 29 20:01:42 2023 !Time: Wed Mar 29 20:01:48 2023
version 10.3(3) Bios:version 08.39
interface Vlan10 no shutdown vrf member B ip address 10.1.1.1/24 ip pim sparse-mode ip pim border ip pim hello-interval 300000
N9K-1# conf t Enter configuration commands, one per line. End with CNTL/Z. N9K-1(config)# interface vlan 10 N9K-1(config-if)# ip dhcp relay address 129.132.128.135 N9K-1(config-if)# ip dhcp relay address 129.132.128.199 N9K-1(config-if)# end N9K-1# show run int vlan 10
!Command: show running-config interface Vlan10 !Running configuration last done at: Wed Mar 29 20:02:06 2023 !Time: Wed Mar 29 20:02:32 2023
version 10.3(3) Bios:version 08.39
interface Vlan10 no shutdown vrf member B ip address 10.1.1.1/24 ip pim sparse-mode ip pim border ip pim hello-interval 300000 ip dhcp relay address 129.132.128.135 ip dhcp relay address 129.132.128.199
N9K-1# |
|
Headline: Incorrect config-profile configuration cannot remove corresponding entry in vsh config |
|
Headline: 'ip dhcp relay' commands are not getting applied
N9K-2(config-if)# ip dhcp relay address 10.1.1.100 N9K-2(config-if)# ip dhcp relay address 10.1.1.200 N9K-2(config-if)# end N9K-2# show run int vlan 10
!Command: show running-config interface Vlan10 !Running configuration last done at: Tue Mar 21 19:03:51 2023 !Time: Tue Mar 21 19:03:55 2023
version 10.2(4) Bios:version 08.39
interface Vlan10 no shutdown vrf member B ip address 10.10.10.2/24 ip pim sparse-mode ip pim border ip pim hello-interval 300000
N9K-2#
Tue Mar 21 19:03:50 2023:type=update:id=console0:user=admin:cmd=configure terminal ; interface Vlan10 ; ip dhcp relay address 10.1.1.100 (REDIRECT) Tue Mar 21 19:03:50 2023:type=update:id=console0:user=admin:cmd=configure terminal ; interface Vlan10 ; ip dhcp relay address 10.1.1.100 (SUCCESS) Tue Mar 21 19:03:51 2023:type=update:id=console0:user=admin:cmd=configure terminal ; interface Vlan10 ; ip dhcp relay address 10.1.1.200 (REDIRECT) Tue Mar 21 19:03:51 2023:type=update:id=console0:user=admin:cmd=configure terminal ; interface Vlan10 ; ip dhcp relay address 10.1.1.200 (SUCCESS)
|
|
Headline: MSDP instability if VRF not enabled for BGP |
|
Headline: Configuration update aborted: request was aborted, post 10.4.1 bin to upg ND-ISSU |
|
Headline: Nexus 9000: Interface description including string "%n" or "%In" crash Service "port-profile"
----- switch(config-if)# interface Ethernet1/5 switch(config-if)# description % Inter XXXX-1001-XX % 2023 Jun 8 14:44:58 switch %$ VDC-1 %$ %SYSMGR-2-SERVICE_CRxSHED: Service "port-profile" (PID 16609) hasn't caught signal 11 (core will be saved). 2023 Jun 8 14:44:58 switch %$ VDC-1 %$ %USER-2-SYSTEM_MSG: ssnmgr_app_init called on ssnmgr up - aclmgr -----
You could see same issue with following strings as well. description %In description % In description %n description % n
After repeating to configure description with these strings several times, NXOS was reloaded. |
|
Headline: Several core files for the process sysmgr-cserver appear in the N9K.
<pre> SYSMGR-2-LAST_CORE_BASIC_TRACE: : PID 18491 with message sysmgr-cserver(non-sysmgr) crashed, core will be saved. SYSMGR-2-SERVICE_CRASHED: Service "System Manager (core-server)" (PID xxxxx) hasn't caught signal 11 (core will be saved). </pre>
And you can verify this with the output of show cores where the sysmgr-cserver will be: <pre> `show cores` VDC Module Instance Process-name PID Date(Year-Month-Day Time) --- ------ -------- --------------- -------- ------------ ------------- 1 1 1 sysmgr-cserver xxxx date 1 1 1 sysmgr-cserver xxxx date 1 1 1 sysmgr-cserver xxxx date </pre> |
|
Headline: N9K: NX-API ospfAdjEp.json cannot retrieve OSPF neighbors correctly after interface flapping |
|
Headline: Syslog to enable layer3 peer-router seen, even with no routing enabled on VPC VLAN's · Below log is being seen in # show logging log, even if no routing is enabled on VPC VLAN's · Suppressing syslog by "no layer3 peer-router syslog" has no impact"ipfib: Routing adjacency over vPC detected without required configuration. Please configure layer3 peer-router under the vPC domain. See https://cisco.com/go/l3pr for more information." Workarounds: · Enable "layer3 peer-router " under VPC configuration on both VPC peers Minor cosmetic thing, can be ignored |
|
Headline: Bi-dir traffic received on DF winner interface is dropped towards the RPF (RP) |
|
Headline: N9300 inconsistent ACE sequence number check causing NDB switch to be in NOTREADY state |
|
Headline: After ISSU upgrade performed with maintenance mode SVIs stay down
Example VLAN interface in problematic state: nexus9000# show interface vlan 3600 Vlan3600 is down (suspended), line protocol is down, autostate enabled
nexus9000# show system internal eltm event-history vxlan-error 2023-06-26T06:27:59.067882000+00:00 [M 1] [eltm] E_DEBUG Outer Bd Alloc failed Nve ifx 0x1a005e00, Overlay state = Up v4/v6 tid (0x1 80000001 1 0) en (0 0) 2023-06-23T13:39:01.222605000+00:00 [M 1] [eltm] E_DEBUG Failed to force alloc outer_bd 16 for vxlan infra vlan 3600 |
|
Headline: EvtLog: Evtlog decoder not working agargula@ag-ubuntu-ML1:~/snapshot-bin$ ./NexusEvtLogDecoder.10.2.5.I9.1.py -input ../snapshot.tar ERROR:root:Parsing Decode Table failed with exception(Expecting object: line 226341 column 1 (char 20287150)) ERROR:root:An error ('NoneType' object has no attribute 'keys') occurred during decode operation: /tmp/BLOGGERD0.939064446123/1-230622215047-230622215705-720109-Caaa-U181-M1-V1-I0-0-P13707-messages.gz @ ../snapshot.tar/20230622215659524263_evtlog_archive.tar |
|
Headline: On N9K switch SNMP polling unable to retrieve QSFP DOM values. |
|
Headline: Admin shut the interface "mgmt0", other end port remains up/flapping. |
|
Headline: ICAM scale table values inconsistent between IPv4 and IPv6 on 9364C |
|
Headline: ACL not programming in hardware with udp-relay config on Nexus 9000 slot 1 ======= ERROR: no ACL related hardware resources for vdc [1], vlan [210] |
|
Headline: EPBR crash @iscm_parse_ipv6_ace upon epbr ipv6 policy configuration with object groups The process crash triggers a reload of the Nexus 9000 switch. Following the reload the following information reports the reason of the crash.
N9K# show system reset-reason ----- reset reason for module 1 (from Supervisor in slot 1) --- 1) At 582169 usecs after Sat Jul 8 13:48:28 2023 Reason: Reset triggered due to HA policy of Reset Service: epbr hap reset Version: 10.3(3)
N9K# show core VDC Module Instance Process-name PID Date(Year-Month-Day Time) --- ------ -------- --------------- -------- ------------------------- 1 1 1 epbr 28608 2023-07-08 12:50:22 * 1 1 1 epbr 6054 2023-07-08 12:50:22 * 1 1 1 epbr 5998 2023-07-08 12:53:58 * HAP reset core restored on reload from previous boot |
|
Headline: Several core files for the process sysmgr-cserver appear in the N9K.
<pre> SYSMGR-2-LAST_CORE_BASIC_TRACE: : PID 18491 with message sysmgr-cserver(non-sysmgr) crashed, core will be saved. SYSMGR-2-SERVICE_CRASHED: Service "System Manager (core-server)" (PID xxxxx) hasn't caught signal 11 (core will be saved). </pre>
And we can verify this with the output of show cores where the sysmgr-cserver will be: <pre> `show cores` VDC Module Instance Process-name PID Date(Year-Month-Day Time) --- ------ -------- --------------- -------- ------------ ------------- 1 1 1 sysmgr-cserver xxxx date 1 1 1 sysmgr-cserver xxxx date 1 1 1 sysmgr-cserver xxxx date </pre> |
|
Headline: N9k | Host routes transition with Punt index in v4host table after route change 1) Traffic to certain IP addresses may end up having high response times or 2) Intermittent packet loss to certain HostsCoPP Drops may be seen depending upon the traffic rate for the class- copp-system-p-class-l3uc-dataData plane traffic to these impacted hosts are software switched/punted and is visible via Ethanalyzer. |
|
Headline: Port-security static binding gets stuck if the interface is converted to L3 before deleting config · Do not shut down the interface before converting it to L2. · Default the interface before converting it to L3. · Remove the static entry with the no command before converting the interface to L3. If the entry is stuck, disable and reenable the port-security feature. |
|
Headline: PBR in combination with a NULL 0 route not working properly , we see drops (UC_PC_CFG_TABLE_DROP) |
|
Headline: Nexus 9000: Redistributed Routes Are Not Removed from Routing Protocol when deleted from URIB. |
|
Headline: Remote Address not sent in TACACS Authorization packet when using NETCONF over SSH |
|
Headline: MSDP peer flapping |
|
Headline: Mac learning issue after reload with private vlan configuration. 1st Workaround – 1. Delete the Primary and Secondary VLAN 2. Delete the Interface level PVLAN config, in Lab setup, it is Eth1/3 3. Add VLAN configuration back 4. Add Interface configuration Back 5.MAC address will be learned
2nd Workaround – Add static Mac. |
|
Headline: Nexus 9500: Configuring "feature nv overlay" breaks non-VXLAN VLAN Multicast across FM-G modules |
|
Headline: SNMP reloaded unexpectedly without collecting the main thread on the core file |
|
Headline: NXOS - BGP Graceful Restart Helper ignores BFD down event when TCP FIN is received from restarting peer. |
|
Headline: N9k/icam system monitor - history do not have all entries present |
|
Headline: Evora crash when incorrect evora register is given. |
Bug ID |
Description |
On Cisco Nexus N2K-C2348TQ HIFs fail to utilize redundant Port-Channel links, to NIF, during link failover events. |
Device Hardware
The following tables list the Cisco Nexus 9000 Series hardware that Cisco NX-OS Release 10.2(6)M supports. For additional information about the supported hardware, see the Hardware Installation Guide for your Cisco Nexus 9000 Series device.
Table 1. Cisco Nexus 9500 Switches
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. |
Table 2. Cisco Nexus 9500 Cloud Scale Line Cards
Product ID |
Description |
Maximum Quantity |
||
Cisco Nexus |
Cisco Nexus |
Cisco Nexus |
||
N9K-X9716D-GX |
Cisco Nexus 9500 16-port 400-Gigabit Ethernet QSFP line card |
4 |
8 |
N/A |
N9K-X9736C-FX |
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 |
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 |
Table 3. Cisco Nexus 9500 R-Series Line Cards
Product ID |
Description |
Maximum Quantity |
|
Cisco Nexus 9504 |
Cisco Nexus 9508 |
||
N9K-X9636C-R |
Cisco Nexus 9500 36-port 40/100 Gigabit Ethernet QSFP28 line card |
4 |
8 |
N9K-X9636C-RX |
Cisco Nexus 9500 36-port 40/100 Gigabit Ethernet QSFP28 line card |
4 |
8 |
N9K-X9636Q-R |
Cisco Nexus 9500 36-port 40 Gigabit Ethernet QSFP line card |
4 |
8 |
N9K-X96136YC-R |
Cisco Nexus 9500 16-port 1/10 Gigabit, 32-port 10/25 Gigabit, and 4-port 40/100 Gigabit Ethernet line card |
4 |
8 |
N9K-X9624D-R2 |
Cisco Nexus 9500 24-port 400 Gigabit QDD line card |
Not supported |
8 |
Table 4. Cisco Nexus 9500 Cloud Scale Fabric Modules
Product ID |
Description |
Minimum |
Maximum |
N9K-C9504-FM-E |
Cisco Nexus 9504 100-Gigabit cloud scale fabric module |
4 |
5 |
N9K-C9504-FM-G |
Cisco Nexus 9500 4-slot 1.6Tbps 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-C9508-FM-G |
Cisco Nexus 9500 8-slot 1.6Tbps cloud-scale fabric module |
4 |
5 |
N9K-C9516-FM-E2 |
Cisco Nexus 9516 100-Gigabit cloud scale fabric module |
4 |
5 |
Table 5. Cisco Nexus 9500 R-Series Fabric Modules
Product ID |
Description |
Minimum |
Maximum |
N9K-C9504-FM-R |
Cisco Nexus 9504 100-Gigabit R-Series fabric module |
4 |
6 |
N9K-C9508-FM-R |
Cisco Nexus 9508 100-Gigabit R-Series fabric module |
4 |
6 |
N9K-C9508-FM-R2 |
Cisco Nexus 9508 400-Gigabit R-Series fabric module |
4 |
6 |
Table 6. Cisco Nexus 9500 Supervisor Modules
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 |
Note: N9K-SUP-A and N9K-SUP-A+ are not supported on Cisco Nexus 9504 and 9508 switches with -R line cards.
Table 7. Cisco Nexus 9500 System Controller
Product ID |
Description |
Quantity |
N9K-SC-A |
Cisco Nexus 9500 Platform System Controller Module |
2 |
Table 8. Cisco Nexus 9500 Fans and Fan Trays
Product ID |
Description |
Quantity |
N9K-C9504-FAN |
Fan tray for 4-slot modular chassis |
3 |
N9K-C9504-FAN2 |
Fan tray that supports the Cisco N9K-C9504-FM-G fabric module |
3 |
N9K-C9508-FAN |
Fan tray for 8-slot modular chassis |
3 |
N9K-C9508-FAN2 |
Fan tray that supports the Cisco N9K-C9508-FM-G fabric module |
3 |
N9K-C9516-FAN |
Fan tray for 16-slot modular chassis |
3 |
Table 9. Cisco Nexus 9500 Fabric Module Blanks with Power Connector
Product ID |
Description |
Minimum |
Maximum |
N9K-C9504-FAN-PWR |
Nexus 9500 4-slot chassis 400G cloud scale fan tray power connector |
1 |
2 |
N9K-C9508-FAN-PWR |
Nexus 9500 4-slot chassis 400G cloud scale fan tray power connector |
1 |
2 |
Table 10. Cisco Nexus 9500 Power Supplies
Product ID |
Description |
Quantity |
Cisco Nexus Switches |
N9K-PAC-3000W-B |
3 KW AC power supply |
Up to 4 Up to 8 Up to 10 |
Cisco Nexus 9504 Cisco Nexus 9508 Cisco Nexus 9516 |
N9K-PDC-3000W-B |
3 KW DC power supply |
Up to 4 Up to 8 Up to 10 |
Cisco Nexus 9504 Cisco Nexus 9508 Cisco Nexus 9516 |
N9K-PUV-3000W-B |
3 KW Universal AC/DC power supply |
Up to 4 Up to 8 Up to 10 |
Cisco Nexus 9504 Cisco Nexus 9508 Cisco Nexus 9516 |
N9K-PUV2-3000W-B |
3.15-KW Dual Input Universal AC/DC Power Supply |
Up to 4 Up to 8 Up to 10 |
Cisco Nexus 9504 Cisco Nexus 9508 Cisco Nexus 9516 |
Table 11. Cisco Nexus 9200 and 9300 Switches
Cisco Nexus Switch |
Description |
N9K-C9316D-GX |
1-RU switch with 16x400/100/40-Gbps ports. |
N9K-C9364C-GX |
2-RU fixed-port switch with 64 100-Gigabit SFP28 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) |
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-C9332C |
1-RU fixed switch with 32 40/100-Gigabit QSFP28 ports and 2 fixed 1/10-Gigabit SFP+ ports. |
N9K-C9332D-GX2B |
1-Rack-unit (1RU) spine switch with 32p 400/100-Gbps QSFP-DD ports and 2p 1/10 SFP+ ports. |
N9k-9348D-GX2A |
48p 40/100/400-Gigabit QSFP-DD ports and 2p 1/10G/10G SFP+ ports |
N9k-9364D-GX2A |
64p 400/100-Gigabit QSFP-DD ports and 2p 1/10 SFP+ ports |
N9K-C93180YC-FX3 |
48 1/10/25 Gigabit Ethernet SFP28 ports (ports 1-48) 6 10/25/40/50/100-Gigabit QSFP28 ports (ports 49-54) |
N9K-C93180YC-FX3S |
48 1/10/25 Gigabit Ethernet SFP28 ports (ports 1-48) 6 10/25/40/50/100-Gigabit QSFP28 ports (ports 49-54) |
N9K-C93360YC-FX2 |
2-RU switch with 96 10-/25-Gigabit SFP28 ports and 12 40/100-Gigabit QSFP28 ports |
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-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-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-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-C93108TC-FX3P |
1-RU fixed-port switch with 48 100M/1/2.5/5/10GBASE-T ports and 6 40-/100-Gigabit QSFP28 ports |
N9K-C9348GC-FXP* |
Nexus 9300 with 48p 100M/1 G, 4p 10/25 G SFP+ and 2p 100 G QSFP |
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 mbps. 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-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-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-C9336C-FX2 |
1-RU switch with 36 40-/100-Gb Ethernet QSFP28 ports |
N9K-C9336C-FX2-E |
1- RU switch with 36 40-/100-Gb QSFP28 ports |
*Note: For N9K-C9348GC-FXP the PSU SPROM is not readable when the PSU is not connected. The model displays as "UNKNOWN" and status of the module displays as "shutdown".
Table 12. Cisco Nexus 9200 and 9300 Fans and Fan Trays
Product ID |
Description |
Quantity |
Cisco Nexus Switches |
NXA-FAN-160CFM-PE |
Fan module with port-side exhaust airflow (blue coloring) |
3 |
|
NXA-FAN-160CFM-PI |
Fan module with port-side intake airflow (burgundy coloring) |
3 |
9364C [1] 93360YC-FX2 |
NXA-FAN-160CFM2-PE |
Fan module with port-side exhaust airflow (blue coloring) |
4 |
9364C-GX |
NXA-FAN-160CFM2-PI |
Fan module with port-side intake airflow (burgundy coloring) |
4 |
9364C-GX |
NXA-FAN-30CFM-B |
Fan module with port-side intake airflow (burgundy coloring) |
3 |
93108TC-EX |
NXA-FAN-30CFM-F |
Fan module with port-side exhaust airflow (blue coloring) |
3 |
93108TC-EX |
NXA-FAN-35CFM-PE |
Fan module with port-side exhaust airflow (blue coloring) |
4
6 |
92300YC [1]
9336C-FX2-E |
NXA-FAN-35CFM-PI |
Fan module with port-side intake airflow (burgundy coloring)
Fan module with port-side exhaust airflow (blue coloring) |
4
6
6 |
92300YC [1]
9316D-GX
9336C-FX2-E |
NXA-FAN-65CFM-PE |
Fan module with port-side exhaust airflow (blue coloring) |
3 |
|
NXA-FAN-65CFM-PI |
Fan module with port-side exhaust airflow (burgundy coloring) |
3 |
93240YC-FX2 |
Table 13. Cisco Nexus 9200 and 9300 Power Supplies
Product ID |
Description |
Quantity |
Cisco Nexus Switches |
NXA-PAC-500W-PE |
500-W AC power supply with port-side exhaust airflow (blue coloring) |
2 |
93108TC-EX |
NXA-PAC-500W-PI |
500-W AC power supply with port-side intake airflow (burgundy coloring) |
2 |
93108TC-EX |
NXA-PAC-650W-PE |
650-W power supply with port-side exhaust (blue coloring) |
2 |
92300YC |
NXA-PAC-650W-PI |
650-W power supply with port-side intake (burgundy coloring) |
2 |
92300YC |
NXA-PAC-750W-PE |
750-W AC power supply with port-side exhaust airflow (blue coloring) 1 |
2 |
9336C-FX2 |
NXA-PAC-750W-PI |
750-W AC power supply with port-side intake airflow (burgundy coloring) 1 |
2 |
9336C-FX2 |
NXA-PAC-1100W-PE2 |
1100-W AC power supply with port-side exhaust airflow (blue coloring) |
2 |
93240YC-FX2 |
NXA-PAC-1100W-PI2 |
1100-W AC power supply with port-side intake airflow (burgundy coloring) |
2 |
93240YC-FX2 |
NXA-PAC-1100W-PI |
Cisco Nexus 9000 PoE 1100W AC PS, port-side intake |
2 |
93108TC-FX3P |
NXA-PAC-1100W-PE |
Cisco Nexus 9000 PoE 1100W AC PS, port-side exhaust |
2 |
93108TC-FX3P |
NXA-PAC-1900W-PI |
Cisco Nexus 9000 PoE 1900W AC PS, port-side intake |
2 |
93108TC-FX3P |
NXA-PAC-1200W-PE |
1200-W AC power supply with port-side exhaust airflow (blue coloring) |
2 |
93360YC-FX2 |
NXA-PAC-1200W-PI |
1200-W AC power supply with port-side intake airflow (burgundy coloring) |
2 |
93360YC-FX2 |
N9K-PUV-1200W |
1200-W Universal AC/DC power supply with bidirectional airflow (white coloring) |
2 |
92300YC |
NXA-PDC-930W-PE |
930-W DC power supply with port-side exhaust airflow (blue coloring) |
2 |
93108TC-EX |
NXA-PDC-930W-PI |
930-W DC power supply with port-side intake airflow (burgundy coloring) |
2 |
93108TC-EX |
NXA-PDC-1100W-PE |
1100-W DC power supply with port-side exhaust airflow (blue coloring) |
2 |
93240YC-FX2 |
NXA-PDC-1100W-PI |
1100-W DC power supply with port-side intake airflow (burgundy coloring) |
2 |
93240YC-FX2 |
UCSC-PSU-930WDC |
930-W DC power supply with port-side intake (green coloring) |
2 |
93108TC-EX |
UCS-PSU-6332-DC |
930-W DC power supply with port-side exhaust (gray coloring) |
2 |
93108TC-EX |
NXA-PHV-1100W-PE |
1100-W AC power supply with port-side exhaust airflow (blue coloring) |
2 |
93240YC-FX2 |
NXA-PHV-1100W-PI |
1100-W AC power supply with port-side intake airflow (burgundy coloring) |
2 |
93240YC-FX2 |
NXA-PAC-2KW-PE |
2000-W AC power supply with port-side exhaust airflow (blue coloring) |
2 |
9364C-GX |
NXA-PAC-2KW-PI |
2000-W AC power supply with port-side intake airflow (burgundy coloring) |
2 |
9364C-GX |
NXA-PDC-2KW-PE |
2000-W DC power supply with port-side exhaust airflow (blue coloring |
2 |
9364C-GX |
NXA-PDC-2KW-PI |
2000-W DC power supply with port-side intake airflow (burgundy coloring) |
2 |
9364C-GX |
N2200-PAC-400W |
400-W AC power supply with port-side exhaust airflow (blue coloring) |
2 |
92348GC-X |
N2200-PAC-400W-B |
400-W AC power supply with port-side intake airflow (burgundy coloring) |
2 |
92348GC-X |
N2200-PDC-350W-B |
350-W DC power supply with port-side intake airflow |
2 |
92348GC-X |
N2200-PDC-400W |
400-W DC power supply with port-side exhaust airflow (blue coloring) |
2 |
92348GC-X |
Fabric Module and Line Card compatibility details are listed below.
Table 14. Cisco Nexus 9500 Cloud Scale Line Cards
Product ID |
N9K-C9504-FM-G |
N9K-C9508-FM-G |
N9K-C9504-FM-E |
N9K-C9508-FM-E |
N9K-C9508-FM-E2 |
N9K-C9516-FM-E2 |
N9K-X9716D-GX |
4 |
4 |
No |
No |
No |
No |
N9K-X9736C-FX |
5 |
5 |
5 |
5 |
5 |
5 |
N9K-X97160YC-EX |
4 |
4 |
4 |
4 |
4 |
4 |
N9K-X9788TC-FX |
4 |
4 |
4 |
4 |
4 |
4 |
N9K-X9732C-EX |
4 |
4 |
4 |
4 |
4 |
4 |
N9K-X9736C-EX |
4 |
4 |
4 |
4 |
4 |
4 |
N9K-X9732C-FX |
4 5 (n+1 redundancy) |
4 5 (n+1 redundancy) |
4 5 (n+1 redundancy) |
4 5 (n+1 redundancy) |
4 5 (n+1 redundancy) |
4 5 (n+1 redundancy) |
Table 15. Cisco Nexus 9500 R-Series Line Cards
Product ID |
N9K-C9504-FM-R |
N9K-C9508-FM-R |
N9K-X9636C-RX |
6 |
6 |
N9K-X9636Q-R |
4 6 (n+2 redundancy) |
4 6 (n+2 redundancy) |
N9K-X9636C-R |
5 6 (n+1 redundancy) |
5 6 (n+1 redundancy) |
N9K-X96136YC-R |
6 |
6 |
Table 16. Cisco Nexus 9500 R2-Series Line Cards
Product ID |
N9K-C9508-FM-R2 |
N9K-X9624D-R2 |
6 |
To determine which transceivers and cables are supported by a switch, see the Transceiver Module (TMG) Compatibility Matrix. To see the transceiver specifications and installation information, see the Install and Upgrade Guides.
Cisco Nexus Dashboard Insights for Data Center
Cisco NX-OS Release 10.2(6)M supports the Nexus Dashboard Insights on Cisco Nexus 9300-FX, 9300-FX2, 9300-FX3, 9300-GX, 9300-GX2, 9400, and 9800 platform switches and 9500 platform switches with -EX/FX/GX Line Cards. For more information, see the Cisco Nexus Insights documentation.
To perform a software upgrade or downgrade, follow the instructions in the Cisco Nexus 9000 Series NX-OS Software Upgrade and Downgrade Guide, Release 10.2(x). For information about an In Service Software Upgrade (ISSU), see the Cisco NX-OS ISSU Support Matrix.
Cisco Nexus 9000 Series documentation: Cisco Nexus 9000 Series Switches
Cisco NX-OS Software Release and Image-naming Convention: Cisco NX-OS Software Strategy and Lifecycle Guide
Cisco Nexus 9000 and 3000 Series NX-OS Switch License Navigator: Cisco Nexus 9000 and 3000 Series NX-OS Switch License Navigator
Cisco Nexus 9000 Series Software Upgrade and Downgrade Guide: Cisco Nexus 9000 Series NX-OS Software Upgrade and Downgrade Guide, Release 10.2(x)
Cisco Nexus 9000 Series FPGA/EPLD Upgrade Release Notes: Cisco Nexus 9000 Series FPGA/EPLD Upgrade Release Notes, Release 10.2(6).
Cisco Nexus 3000 and 9000 Series NX-API REST SDK User Guide and API Reference: Cisco Nexus NX-API Reference
Cisco NX-OS Supported MIBs: ftp://ftp.cisco.com/pub/mibs/supportlists/nexus9000/Nexus9000MIBSupportList.html
Supported FEX modules: Cisco Nexus 9000 Series Switch FEX Support Matrix
Licensing Information: Cisco NX-OS Licensing Guide and Cisco Nexus Smart Licensing Using Policy User Guide
When you downgrade from Cisco NX-OS Release 10.2(6)M to an earlier release, the features that use the ACI+NX-OS Essentials, Advantage, and add-on licenses or the Hardware Streaming Telemetry license continue to work in honor mode in the downgraded version. In addition, the output of the show license usage command continues to include entries for these unsupported licenses.
For more information, see the Cisco NX-OS Licensing Guide.
To provide technical feedback on this document, or to report an error or omission, please send your comments to nexus9k-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: https://www.cisco.com/c/en/us/about/legal/trademarks.html. 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. (1721R)
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.
© 2023 Cisco Systems, Inc. All rights reserved.