In Juniper Device Manager (JDM), the show system core-dump command lists the core dump files, but it is not clear where these files are located. This article explains where these files are located and how to find them.
show system core-dump
The request support information local command on the JDM lists the core dump files as follows:
request support information local
root@jdm> show system core-dumps /var/tmp/corefiles/*core* : -rw-r--r-- 1 root root 3179805 Jun 21 16:06 ipsec-nm.srxpfe.95.1529597202.core.tgz -rw-r--r-- 1 root root 1694150 Mar 1 16:46 jdm.jdmd.2328.1519922794.core.tgz -rw-r--r-- 1 root root 230992 May 3 17:06 jdm.mgd.2426.1525367185.core.tgz -rw-r--r-- 1 root root 435750 Feb 23 20:17 localhost.named.3666.1519417037.core.tgz -rw-r--r-- 1 root root 434369 Feb 2 20:50 localhost.named.3711.1517604646.core.tgz -rw-r--r-- 1 root root 441293 Feb 23 17:08 localhost.named.3789.1519405684.core.tgz /var/tmp/*core* : drwxr-xr-x 2 root root 4096 Jun 21 16:06 corefiles
The procedure is this article applies to NFX250 running nfx-2 software. For NFX250-Next Gen, NFX150, and NFX350, refer to KB34846 - [NFX] How to locate crash files on nfx-3 software [juniper.net] .
For NFX250 running nfx-2 software, the core dump files are located in hypervisor. To find these files, perform the following steps:
SSH to hypervisor.
cd to /var/tmp/corefiles to find the necessary files there.
cd
/var/tmp/corefiles
Example {master:0} root@jdm> ssh hypervisor Last login: Thu Jun 21 16:07:26 2018 from jdm root@local-node:~# cd /var/tmp/corefiles root@local-node:/var/tmp/corefiles# ls -l total 6280 -rw-r--r-- 1 root root 3179805 Jun 21 16:06 ipsec-nm.srxpfe.95.1529597202.core.tgz -rw-r--r-- 1 root root 1694150 Mar 1 16:46 jdm.jdmd.2328.1519922794.core.tgz -rw-r--r-- 1 root root 230992 May 3 17:06 jdm.mgd.2426.1525367185.core.tgz -rw-r--r-- 1 root root 435750 Feb 23 20:17 localhost.named.3666.1519417037.core.tgz -rw-r--r-- 1 root root 434369 Feb 2 20:50 localhost.named.3711.1517604646.core.tgz -rw-r--r-- 1 root root 441293 Feb 23 17:08 localhost.named.3789.1519405684.core.tgz root@local-node:/var/tmp/corefiles#
Example
{master:0} root@jdm> ssh hypervisor Last login: Thu Jun 21 16:07:26 2018 from jdm root@local-node:~# cd /var/tmp/corefiles root@local-node:/var/tmp/corefiles# ls -l total 6280 -rw-r--r-- 1 root root 3179805 Jun 21 16:06 ipsec-nm.srxpfe.95.1529597202.core.tgz -rw-r--r-- 1 root root 1694150 Mar 1 16:46 jdm.jdmd.2328.1519922794.core.tgz -rw-r--r-- 1 root root 230992 May 3 17:06 jdm.mgd.2426.1525367185.core.tgz -rw-r--r-- 1 root root 435750 Feb 23 20:17 localhost.named.3666.1519417037.core.tgz -rw-r--r-- 1 root root 434369 Feb 2 20:50 localhost.named.3711.1517604646.core.tgz -rw-r--r-- 1 root root 441293 Feb 23 17:08 localhost.named.3789.1519405684.core.tgz root@local-node:/var/tmp/corefiles#
2021-01-04: Added a link for log steering from Hypervisor to JDM
2021-07-09: Added text specifying this article is specific to Porter 2; also added referencing link to article for Porter 3