Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Checklist for Collecting Crash Data

    Problem

    Table 1 provides links commands for collection crash data.

    Solution

    Table 1: Checklist for Collecting Crash Data

    Tasks

    Command or Action

    Understand Crash Data Collection
    Collect Crash Data for a Routing Engine Kernel
    1. Check the Routing Engine Core Files

    file list detail /var/crash

    1. Clear the NVRAM Contents
     

    start shell
    su
    root password
    cd /var/crash
    ls -l

    gzip vmcore.number

    To unzip the vmcore file:
    gzip -d vmcore.number.gz

    show version

    support@juniper.net
    ftp ftp.juniper.net

    Collect Crash Data for Routing Engine Daemons 
    1. Check for Daemon Core Files

    file list detail /var/tmp

    1. Collect and Send Routing Engine Crash Data to JTAC
     

    start shell
    su
    root password
    cd /var/tmp
    ls -l

    gzip daemon-executable-name.core.number

    show version

    support@juniper.net
    ftp ftp.juniper.net

    Collect Crash Data for the Packet Forwarding Engine Microkernel
    1. Display the Crash Stack Traceback and Registration Information

    start shell
    su
    root password
    vty component-executable-name
    show nvram
    show syslog messages

    1. Clear the NVRAM Contents

    start shell
    su
    root password
    vty component-executable-name
    clear nvram

    1. Check Packet Forwarding Engine Microkernel Core Files

    file list detail /var/crash

    1. Collect and Send Routing Engine Crash Data to JTAC
     

    start shell
    su
    root password
    cd /var/crash
    ls -l

    gzip filename

    show version

    support@juniper.net
    ftp ftp.juniper.net

    Published: 2013-02-25