Hide Navigation Pane
Show Navigation Pane
Download
SHA1
Creating Core Dump Files
You can enable the system to create a core dump file if a module fails. You can choose to send the core dump file to an FTP server or save the file to NVS. Juniper Networks Customer Service can then access the core dump file and analyze it to determine what went wrong. Local core dumps—stored in NVS—are enabled by default. You can enable the core dump from Boot mode or Global Configuration mode.
 | Caution: Create a core dump file only under the direction of Juniper Networks Customer Service. Network function can be disrupted if you create a core dump file while the system is running in a network. |
On the E120 and E320 routers, the failure of some components on a line module generates multiple core dumps to provide more complete information about system state at the time of the failure. Other E Series routers generate only a single core dump for line module failures. When you contact Juniper Networks Customer Service for assistance, send all of the generated core dump files.
This section describes the following:
Enabling the Core Dump from Boot Mode
To enable the core dump from Boot mode:
- Access Boot mode by reloading the SRP module; then press the mb key sequence (case insensitive) during the countdown.
- Specify where the system should transfer the core dump
file. To send the file to an FTP server, enter the IP address of the
FTP server and the name of the directory on the server to which the
system will transfer the file. To send the core dump file to NVS memory,
use the local keyword. Local core dumps—stored in NVS—are
enabled by default.:boot##exception dump 192.168.56.7 CORE_DUMPS
- Set the IP address and mask of the system interface over
which you want to send the core dump file. You can optionally include
an IP address mask.:boot##exception source 10.10.33.8 255.255.255.0
- Specify the gateway through which the system sends the
core dump file to the FTP server. :boot##exception gateway 192.168.12.3
- (Optional) Set a username and password for FTP access
to the server where you transferred the core dump file. The default
settings are the username anonymous and no password. You can specify
the number 8 before the username and before the password to encrypt
these values. By default, the username and password are not encrypted.:boot##exception protocol ftp user_name user_password
- Reload the operating system. You can reload the system
software (.rel) file and the configuration (.cnf) file.:boot##reload
Note: Reloading the standby SRP causes high availability to be temporarily disabled until the standby SRP reloads and resynchronizes with the active SRP.
Enabling the Core Dump from Global Configuration Mode
To enable the core dump from Global Configuration mode:
- Access Global Configuration mode.
- Specify where the system should transfer the core dump
file. To send the file to an FTP server, enter the IP address of the
FTP server and the name of the directory on the server to which the
system will transfer the file. To send the core dump file to NVS memory,
use the local keyword. Local core dumps—stored in NVS—are
enabled by default.host1(config)#exception dump 192.168.56.7 CORE_DUMPS
- Set the IP address and mask of the system interface over
which you want to send the core dump file. You can optionally include
an IP address mask.host1(config)#exception source 10.10.33.8 255.255.255.0
- Specify the gateway through which the system sends the
core dump file to the FTP server. host1(config)#exception gateway 192.168.12.3
- (Optional) Set a username and password for FTP access
to the server where you want to transfer the core dump file. The default
settings are the username anonymous and no password. You can specify
the number 8 before the username and before the password to encrypt
these values. By default, the username and password are not encrypted.host1(config)#exception protocol ftp username userpassword
- (Optional) View parameters associated with creating a
core dump file. You can reload the system software (.rel) file and
the configuration (.cnf) file.host1(config)#reload
Note: Reloading the standby SRP causes high availability to be temporarily disabled until the standby SRP reloads and resynchronizes with the active SRP.
