Nexus N9K-C9372PX reboot reason Kernel Panic

[nareh84]

hi,

yesterday I got an alert and found out that one of the nexus (two nexus in vpc) rebooted itself. when i did show version, i can see the last reboot reason as  Kernel Panic. System version: 9.3(7) (nxos.9.3.7.bin). i can see licmgr when i use show process log message and the time is around the same when the issue happened. i think this switch was up for 642 days.

N9K-Prim# show core
VDC Module Instance Process-name PID Date(Year-Month-Day Time)
--- ------ -------- --------------- -------- -------------------------
N9K-Prim# show processes log
VDC Process PID Normal-exit Stack Core Log-create-time
--- --------------- ------ ----------- ----- ----- ---------------
1 licmgr 19545 N N N Mon Feb 27 22:38:58 2023

N9K-Prim# sh system resources
Load average: 1 minute: 0.47 5 minutes: 0.51 15 minutes: 0.50
Processes : 638 total, 1 running
CPU states : 14.83% user, 7.92% kernel, 77.23% idle
CPU0 states : 8.33% user, 9.37% kernel, 82.29% idle
CPU1 states : 12.00% user, 12.00% kernel, 76.00% idle
CPU2 states : 11.34% user, 7.21% kernel, 81.44% idle
CPU3 states : 27.55% user, 3.06% kernel, 69.38% idle
Memory usage: 16399576K total, 5493292K used, 10906284K free
Kernel vmalloc: 0K total, 0K free
Kernel buffers: 95552K Used
Kernel cached : 3596944K Used
Current memory status: OK

any suggestions?

[M02@rt37]

Hello @nareh84 

Kernel panics can be caused by a variety of factors, including hardware failures, software bugs, and configuration issues.

Do you have verified that all hardware components on the Nexus switch are functioning properly ?

Are there any known bugs or issues with the current software version?

Check the system logs on the Nexus switch to see if there are any error messages or warnings that may indicate the cause of the kernel panic.

If you are unable to identify the cause of the kernel panic or resolve the issue on your own, consider opening a case with Cisco support. They can provide more advanced troubleshooting and assistance to help you resolve the issue.