This article gives an explanation of some areas of the "request support information" ( RSI ) that are useful for quick analysis of a system.
The "request support information" command gives a large volume of output and it is not possible to read it line by line to analyze an issue. Therefore it is necessary to quickly navigate the output and to jump to the most useful information. To do so, collect an RSI use the following command from operational mode of an SRX device:
root@SRX> request support information | save /var/tmp/rsi_June30 | Note: You will see the cursor blinking showing that the box is writing the RSI information to the said file.
root@SRX> request support information | save /var/tmp/rsi_June30 |
root@SRX> request support information | save /var/tmp/rsi_June30 Wrote 17350 lines of output to '/var/tmp/rsi_June30' root@SRX>
Using a text editor you can search for each command noted below within the output of request support information: show version
show version
It is useful to know the version to search for any defects that might be related. You can do a PR search by version and keywords @ https://prsearch.juniper.net
show chassis routing-engine
Gives the CPU and memory utilization of the RE (control plane). Reference: show chassis routing-engine (View) Note: If Idle is 0 that means the CPU is at max utilization.
show security monitoring fpc
Gives the CPU, memory, session counts, and session bring up rate of each SPU (forwarding plane) Example: root@Source> show security monitoring Flow session Flow session CP session CP session FPC PIC CPU Mem current maximum current maximum 0 0 0 68 0 524288 0 0
Example: root@Source> show security monitoring Flow session Flow session CP session CP session FPC PIC CPU Mem current maximum current maximum 0 0 0 68 0 524288 0 0
root@Source> show security monitoring Flow session Flow session CP session CP session FPC PIC CPU Mem current maximum current maximum 0 0 0 68 0 524288 0 0
show system uptime
Gives the time the system has been online, last booted, last configured, as well as the current system time. Both nodes of a cluster should display correct times. (Note: there is a delay when the command is run for node0 vs. node1) Time last configured may give clues about any changes that could be related Example: root@Source> show system uptime Current time: 2019-07-01 11:57:15 UTC Time Source: LOCAL CLOCK System booted: 2019-06-30 12:29:00 UTC (23:28:15 ago) Protocols started: 2019-06-30 12:29:01 UTC (23:28:14 ago) Last configured: 2019-06-30 13:34:23 UTC (22:22:52 ago) by root 11:57AM up 23:28, 1 user, load averages: 0.09, 0.07, 0.03
root@Source> show system uptime Current time: 2019-07-01 11:57:15 UTC Time Source: LOCAL CLOCK System booted: 2019-06-30 12:29:00 UTC (23:28:15 ago) Protocols started: 2019-06-30 12:29:01 UTC (23:28:14 ago) Last configured: 2019-06-30 13:34:23 UTC (22:22:52 ago) by root 11:57AM up 23:28, 1 user, load averages: 0.09, 0.07, 0.03
show security flow session summary
Shows the current session count and max limit of the SPU's Reference: Monitoring Security Flow Sessions
show chassis fpc pic-status
Shows if the modules have fully come online yet or not. Reference: show chassis fpc (View)
show interfaces extensive
Interface counters such as L2 channel errors, Input DA rejects, TCP sequence error, No more sessions, PPS rates, speed/duplex, etc Reference: show interfaces
show chassis cluster status
If using cluster, check if redundancy group (RG) priorities are not 0, check if the redundancy groups are primary/secondary as expected. Reference: show chassis cluster status
show chassis cluster information
If using cluster, check if heartbeats & probes are sent & received, that cold synchronization has not failed, any failover reasons or interface monitoring events Reference: show chassis cluster information
show chassis cluster interfaces
If using cluster, check that control and fab links are up, reth interfaces are up, and child physical interfaces tracked by interface monitoring are up Reference: show chassis cluster interfaces
show security ipsec security-associations
If IPSec is configured, check VPN status Reference: show security ipsec security-associations
show system core-dumps
Check for any recent coredumps Reference: show system core-dumps
show system processes extensive
Check for any processes using high CPU, high memory, or excessive instances of the same process Sample command: show system processes extensive | except 0.0
show system processes extensive | except 0.0
show system statistics
For problems with traffic terminating/originating on the SRX itself, such as ARP, IPSec, TCP, UDP, IP, IGMP, etc
show interfaces queue
If using class of service, gives more details on interface drops Reference: show interfaces queue
show route brief
Check if route information is correct
show chassis alarms
Check for any general alarms raised Reference: show chassis alarms
show chassis fabric plane
High end only, check the connections between modules don't report errors Reference: show chassis fabric plane
show system storage
Check for available disk space on the / and /var partitions Reference: show system storage
show configuration
Delete any unnecessary traceoptions Reference: show configuration
show system commit
Check when the last commit was performed and by whom.
show system rollback
Usage : show system rollback compare 1 0 0 is the present configuration 1 is the last configuration Output shows some configuration in "+" and some configuration in "-" "+" configuration is the configuration that is added from 1 to 0 "-" configuration is the configuration that is deleted from 1 to 0 Reference: show system rollback
Usage : show system rollback compare 1 0
Output shows some configuration in "+" and some configuration in "-"
Reference: show system rollback
2019-07-23: added additional show commands and reference links.