Description

This article shows how to collect request support information (RSI) and logs (var/log/) from both SRX Chassis Cluster nodes. 

Symptoms

When investigating SRX Chassis Cluster issues, it is often necessary to collect RSI and Logs out of both cluster nodes. Having the support information only from one node is not enough to troubleshoot cluster issues since it only gives the view of events from only one node's perspective. 

Solution

Assuming node 0 is the redundancy group 0 primary node: 

 

1-Save RSI in the primary routing engine /var/log/ directory: 

 

{primary:node0}
root@SRX0> request support information | save /var/log/RSI_NODE_0.txt | no-more
Wrote 23903 lines of output to '/var/log/RSI_NODE_0.txt'

 

2-Save /var/log/ logs of primary RE in the /var/tmp/ directory: 

 

{primary:node0}
root@SRX0> file archive compress source /var/log/* destination /var/tmp/NODE_0_LOGS_RSI.tgz
/usr/bin/tar: Removing leading `/' from member names

 

3-Move to the secondary routing engine: 

 

{primary:node0}
root@SRX0> start shell
root@SRX0% rlogin -T node1

 

4-Save RSI in the secondary routing engine /var/log/ directory: 

 

{secondary:node1}
root@SRX1>request support information | save /var/log/RSI_NODE_1.txt | no-more

 

5-Save /var/log/ logs of secondary RE in the /var/tmp/ directory: 

 

{secondary:node1}
root@SRX1> file archive compress source /var/log/* destination /var/tmp/NODE_1_LOGS_RSI.tgz

 

6-Copy secondary RE logs to the primary RE: 

 

{secondary:node1}
root@SRX1> file copy /var/tmp/NODE_1_LOGS_RSI.tgz node0:/var/tmp/NODE_1_LOGS_RSI.tgz                                        

7-Move back to the primary RE: 

 

{secondary:node1}
root@SRX1> exit

root@SRX1% exit
logout
rlogin: connection closed

 

8-Make sure both files are present in the primary RE and extract them:  

 

{primary:node0}
root@SRX0> file list /var/tmp/
/var/tmp/:
NODE_1_LOGS_RSI.tgz ---> Contains secondary node RSI and logs
NODE_0_LOGS_RSI.tgz ---> Contains primary node RSI and logs 

 

Now the files can be directly copied from Node 0 to any local host by using FTP, SCP, JWEB, or a mounted USB.

Note: FTP, SSH and HTTP are configured under the system services  stanza. For mounting a USB, refer to:  [Junos] How to mount a USB drive on EX/SRX/MX/QFX Series platforms to import/export files


Note : 

When a non-root user tries to generate an archive file for /var/log, the process may either fail or create an archive with partial log files. This occurs due to permission restrictions on files under /var/log/hostlogs/.
This is by design, as the /var/log/hostlogs/ directory requires root-level access. When a non-root user needs to archive /var/log/*, it is necessary to exclude this directory.

Workaround: Use the option to exclude the /var/log/hostlogs/ directory. 
 Example: file archive compress source /var/log/* destination /var/tmp/logs_yyyy-mm-dd.tgz exclude /var/log/hostlogs
 Reference : KB96178 [juniper.net]



 


Modification History
11/05/2024 Article created