Hi,
we are currently experiencing an issue where a pair of Nexus 5596UP's are crashing resulting in us having to power cycle the device to restore service. The crash seems to occur within 15 minutes of each other
The reset reason for the last two crashes is below.
Secondary crashed first:
sho system reset-reason
----- reset reason for Supervisor-module 1 (from Supervisor in slot 1) ---
1) At 671084 usecs after Tue Oct 1 12:14:11 2019
Reason: Reset Requested due to Fatal System Error
Service: Too many restarts of sysmgr
Version: 7.3(0)N1(1)
With the primary crashing shortly after:
At 668393 usecs after Tue Oct 1 12:31:01 2019
Reason: Reset Requested due to Fatal System Error
Service: Too many restarts of sysmgr
Version: 7.3(0)N1(1)
I was able to pull nvram logs from the latest crash which I have copied below.
Primary:
2019 Oct 1 12:30:45 HOSTNAME %$ VDC-1 %$ eem_policy_dir: (null): failed to connect cli
2019 Oct 1 12:30:49 HOSTNAME %$ VDC-1 %$ %SYSMGR-2-CORE_SAVE_FAILED: master_core_client_try_spawn: PID 2388 with message Unable to start core client
. Cannot allocate memory.
2019 Oct 1 12:31:01 HOSTNAME %$ VDC-1 %$ %KERN-0-SYSTEM_MSG: [977608.851588] Shutdown Ports.. - kernel
2019 Oct 1 12:31:01 HOSTNAME %$ VDC-1 %$ %KERN-0-SYSTEM_MSG: [977608.894040] writing reset reason 3, Too many restarts of sysmgr - kernel
Secondary:
2019 Oct 1 12:13:38 HOSTNAME-2 %$ VDC-1 %$ eem_policy_dir: (null): failed to connect cli
2019 Oct 1 12:16:42 HOSTNAME-2 %$ VDC-1 %$ %SYSLOG-2-SYSTEM_MSG : Syslogs wont be logged into logflash until logflash is online
2019 Oct 1 12:16:43 HOSTNAME-2 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files begin - clis
2019 Oct 1 12:16:45 HOSTNAME-2 %$ VDC-1 %$ %KERN-0-SYSTEM_MSG: [ 7.858071] I2C - Mezz present - kernel
I haven't been able to find anything bug related, and was hoping the forums might help identify the cause...
Thanks
Dan
