Collect Crash Data for Routing Engine Daemons
To collect crash data for Routing Engine daemons, follow these steps:
- Check for Daemon Core Files
- List the Daemon Core Files
- Compress the Daemon Core Files
- Log Software Version Information
- Open a Case with JTAC
Check for Daemon Core Files
Purpose
If you observe disruption to routing protocol operation, system log operation, Simple Network Management Protocol (SNMP) operation, or other operations handled by Routing Engine daemons, check the /var/tmp directory for any daemon core files created around the time of the crash.
Action
To check the /var/tmp directory, use the following Junos OS CLI operational mode command:
Sample Output
user@host> file list detail /var/tmp total 1292622 drwxrwxrwt 3 root field 512 Dec 31 06:48 ./ drwxr-xr-x 21 root field 512 Mar 5 1999 ../ -rw-rw---- 1 root field 119713792 Nov 17 21:58 rpd.core.0 -rw-rw---- 1 root field 120782848 Nov 17 22:12 rpd.core.1
Meaning
The sample output lists the contents of the /var/tmp/ directory. Look for any daemon core files created around the time of the crash. In the example above, two core files are listed: rpd.core.0 and rpd.core.1.
Table 1 lists the major Routing Engine daemons supported by the Junos OS.
Table 1: Major Routing Engine Daemons
Executable Name | Definition | Description |
|---|---|---|
rpd | Routing protocol daemon | Provides routing protocol intelligence (Border Gateway Protocol [BGP], Intermediate System-to-Intermediate System [ISIS], Open Shortest Path First [OSPF], and so on). |
dcd | Device control daemon | Manages all interface devices. |
mgd | Management daemon | Provides user configuration access to the system. The CLI is a client of mgd. |
snmpd | Simple Network Management Protocol daemon | Provides remote network management information to the network management system. |
chassisd | Chassis daemon | Monitors and manages Flexible PIC Concentrator (FPC) slots and other environmental components. |
alarmd | Alarm daemon | Manages system alarm notifications. |
apsd | Automatic protection switching daemon | Provides SONET Automatic Protection Switching (APS) functionality. |
sampled | Traffic sampling daemon | Gathers traffic sampling information. |
vrrpd | Virtual Router Redundancy Protocol daemon | Provides Virtual Router Redundancy Protocol (VRRP) functionality. |
syslogd | System log daemon | Manages the router system logging operation. |
mib2d | MIB2 daemon | Management Information Base (MIB) subagent for MIB2. |
List the Daemon Core Files
Purpose
To list the daemon core files.
Action
To list the daemon core files, follow these steps:
- Exit from the CLI environment and create a UNIX-level
shell by entering the start shell command:user@host> start shell
- Type su and the root password when prompted. You are now in
the shell and the prompt is % instead of >, for
example:% su Password: ****
- Change the directory to /var/tmp and type ls -l, for example:root@host% cd /var/tmp root@host% ls -l
- Look for any daemon core files created around the time of the crash.
Sample Output
user@host> start shell
% su Password: **** root@host% cd /var/tmp root@host% ls -l total 1292618 -rw-rw---- 1 root field 119713792 Nov 17 21:58 rpd.core.0 -rw-rw---- 1 root field 120782848 Nov 17 22:12 rpd.core.1
Meaning
The sample output lists the contents of the /var/tmp directory and shows the current core file (rpd.core.1) and one previous core file (rpd.core.0) for the routing protocol daemon (rpd). For each daemon, you can have a total of five core files in the /var/tmp directory: the current core file and the four previous core files numbered 0 through 4 (from oldest to newest).
Compress the Daemon Core Files
Purpose
The gzip compression utility is used to compress the files if they are large. Files created using the gzip command end with the file extension .gz. Compress the core file if it is over 50 MB.
 | Note: Use lowercase for the gzip command when you are in the shell. You only need to compress the daemon core files when the tarball file is not created. |
Action
To compress the daemon core file with gzip, use the following command from the shell:
Sample Output
root@host% gzip rpd.core.0
gzip rpd.core.0
Meaning
The contents of the daemon core file are compressed into a single compressed file named daemon.number.gz. The gzip command preserves the mode, ownership, and timestamps of files when compressing or decompressing them.
Log Software Version Information
Purpose
To log the Junos OS version information.
Action
To log the Junos OS version information, use the following Junos OS CLI operational mode command:
Sample Output
user@host> show version
Hostname: host Model: m10 JUNOS Base OS boot [5.0R5] JUNOS Base OS Software Suite [5.0R5] JUNOS Kernel Software Suite [5.0R5] JUNOS Routing Software Suite [5.0R5] JUNOS Packet Forwarding Engine Support [5.0R5] JUNOS Crypto Software Suite [5.0R5] JUNOS Online Documentation [5.0R5] KERNEL 5.0R5 #0 built by builder on 2002-03-02 05:10:28 UTC MGD release 5.0R5 built by builder on 2002-03-02 04:45:32 UTC CLI release 5.0R5 built by builder on 2002-03-02 04:44:22 UTC CHASSISD release 5.0R5 built by builder on 2002-03-02 04:43:37 UTC DCD release 5.0R5 built by builder on 2002-03-02 04:42:47 UTC RPD release 5.0R5 built by builder on 2002-03-02 04:46:17 UTC SNMPD release 5.0R5 built by builder on 2002-03-02 04:52:26 UTC MIB2D release 5.0R5 built by builder on 2002-03-02 04:45:37 UTC APSD release 5.0R5 built by builder on 2002-03-02 04:43:31 UTC VRRPD release 5.0R5 built by builder on 2002-03-02 04:52:34 UTC ALARMD release 5.0R5 built by builder on 2002-03-02 04:43:24 UTC PFED release 5.0R5 built by builder on 2002-03-02 04:46:06 UTC CRAFTD release 5.0R5 built by builder on 2002-03-02 04:44:30 UTC SAMPLED release 5.0R5 built by builder on 2002-03-02 04:52:20 UTC ILMID release 5.0R5 built by builder on 2002-03-02 04:45:21 UTC BPRELAYD release 5.0R5 built by builder on 2002-03-02 04:42:41 UTC RMOPD release 5.0R5 built by builder on 2002-03-02 04:46:11 UTC jkernel-dd release 5.0R5 built by builder on 2002-03-02 04:41:07 UTC jroute-dd release 5.0R5 built by builder on 2002-03-02 04:41:21 UTC jdocs-dd release 5.0R5 built by builder on 2002-03-02 04:39:11 UTC
Meaning
The sample output shows the hostname, router model, and the different Junos OS packages, processes, and documents.
Open a Case with JTAC
Problem
To open a case with JTAC, follow these steps:
Solution
- Send an e-mail to support@juniper.net, and include the information from the show version command.
- At the support engineer’s request, ftp the vmcore.number.gz file to a case-number directory at ftp.juniper.net. To ftp the core file to a directory, follow
these steps:
- At the shell prompt, enter ftp ftp.juniper.net.
- At the name prompt, enter anonymous.
- At the password prompt, enter your e-mail address as the password.
- At the ftp prompt, enter the cd pub/ incoming string.
- Enter the mkdir case-number command, where the case-number is the value of the case you opened with JTAC, for example, 1999-1231-9999. If a directory has already been created, continue with the next step.
- Enter the cd case-number command.
- Enter the binary command so that the file transfer is in binary and not ASCII.
- Enter the put vmcore.0.gz command.
Meaning
The following output is an example of copying a core file from the shell to an ftp directory at ftp.juniper.net:
Sample Output
root@host% ftp ftp.juniper.net Connected to colo-ftp.juniper.net. 220 colo-ftp.juniper.net FTP server (Version 6.00LS) ready. Name (ftp.juniper.net: root): anonymous 331 Guest login ok, send your email address as password. Password: **** 230 Guest login ok, access restrictions apply. ftp> cd pub/ incoming 250 CWD command successful ftp> mkdir 1999-1231-9999 257 MKD command successful. ftp> cd 1999-1231-9999 250 CWD command successful. ftp> bin 200 Type set to I. ftp> put vmcore.0.gz
Meaning
The sample output shows that there is a connection to ftp.juniper.net, that the login name and password were entered, and that the core file was successfully copied from the shell to an ftp directory at ftp.juniper.net.
