Can't find what you need?

• Ask the Community
• Create a Case
Reset Search



What is the difference between the two crash files? core.{ProcessName}.{ProcessId}.gz and core.nvram.{digit}

« Go Back


TitleWhat is the difference between the two crash files? core.{ProcessName}.{ProcessId}.gz and core.nvram.{digit}
What is the difference between the two crash files that are generated when switch experiences process crash and consequently a reboot?
EXOS Platforms
Following table explains the differences and similarities between the two files that are generated with when a switch experiences a crash. These files are stored in the switch's internal memory and can be retrieved anytime as long as the files are retained in the memory space. 

Core. {ProcessName} . {ProcessId} . gz
  • When a process expereinces crash, a core-dump file is created and stored in the management module (chassis platforms) or summit memory space. For example if a cliMaster process is crashed in MSM-A, the file will be created as :  core.cliMaster.1312.MSM-A.gz
  • Along with the ‘.gz’ file, ‘core.nvram’ file is also created for the process crash which is visible in the show tech output.
  • Process crash files (.gz) are created separately and can be uploaded via ‘upload debug’ command.
  • .gz file has more details about the process crash which is analyzed further by Engineering.
  • Once uploaded via ‘upload debug’, the core file is removed from the switch to free up the memory.
  • The file can also be TFTP’d from the internal memory but it is not removed from switch memory if TFTP method is used compared to upload debug.
  • The number of process crash (.gz) files depend on the available memory on any given platform.
Core.nvram. {digit]
  • When kernel oops happens or memory depletion occurs, Core.nvram file is created with the crash info – no coredump (.gz) is created in such scenarios.
  • This crash info is stored in NVRAM as name implies and file is created as : core.nvram.1
Note : sequence number starts with ‘1’ and increment continuously
  • Core.nvram file is part of the show tech output or it can be viewed via “show debug system-dump” CLI.
  • This file can be deleted with ‘clear debug system-dump’ CLI to free up the memory.
  • The file can also be captured via ‘upload debug’ command.
  • No more than two NVRAM files can be stored in the allocated space.
  • Kernel oops NVRAM files are hard to decode and generally take more time to get to the root cause.
Additional notes



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255