Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Troubleshooting Scenarios

This topic provides you troubleshooting information when you encounter issues while using SRX400 firewall series.

On SRX400 firewall series, you can use monitoring commands, log files, debugging (or trace options), packet capture for transit traffic through the firewall, or packet capture of control traffic to and from the firewall's Routing Engine. On Junos OS Evolved, debug collector provides a comprehensive snapshot of system configuration, routing, security, chassis health, diagnostics, logs, system files, core files, and hardware status (for example, re0 and fpc 0).

  • Trace options—The firewall device must support trace options for all processes, services, and protocols. Trace options are very useful during debugging and troubleshooting.

  • Debug collector—The debug collector information is captured in a separate file and is used by JTAC case or ticket.

  • Boot messages—An option must be provided to save boot messages in a file, such that user should be able to retrieve errors or messages displayed during boot process. For more information, see show system boot-messages.

For more troubleshooting information, see:

Trace Options

SRX400 firewall series supports trace options for all processes, services, and protocols.

In Junos OS Evolved, you use the show trace application application name to read and decode trace messages stored in the trace files at the application level.

Use the references below for more details on trace option:

Debug Collector and Logs

  • request system debug-info

    This command creates a compressed /var/tmp/debug_collector_#####_<date>.tar file on SRX400 firewall series.

  • In an MNHA deployment, you must run this command separately on each node.

    To upload large files to a JTAC support case using SFTP, see How to upload large files to a JTAC support case using SFTP.

Boot Messages

  • To see the boot messages for the most recent boot messages, run the show system boot-messages command.

    You can also find this information in /var/run/dmesg.boot.