Using USB storage in SRX series when upgrading JUNOS Software

SUMMARY:
The USB slot in SRX series can be used to copy from/to USB storage to internal flash memory when upgrading or
troubleshooting.
* SRX100 : 1 slot
* SRX210/240 : 2 slots
* SRX650 : 2 slot on SRE
* SRX3400/3600 : 2 slots on SFB and 2 slots on each RE
* SRX5600/5800 : 2 slots on each RE

PROBLEM OR GOAL:
Using USB storage in SRX series when upgrading JUNOS Software

CAUSE:
SOLUTION:
In order to copy JUNOS software installation package (e.g., junos-srxxxx-xxx.tgz) from USB storage to
internal flash memory, follow the below steps:
1. Insert a USB storage to PC.
2. Copy a JUNOS Software installation package (e.g., "junos-srxxxx-xxx.tgz") from PC to USB storage (USB storage
is formatted FAT16 or FAT32)
3. Insert the USB storage to one of USB slot(s) in SRX series
4. Issue the following commands in shell mode (the root privillage is required)

root@% mkdir /var/tmp/usb (any directory name can be used as mounted

directory)
root@% mount -t msdos /dev/da[N]s1 /var/tmp/usb
### [N] is discussed later.
5. Verify the contents of USB storage in the mounting point (/var/tmp/usb).

root@% pwd
/cf/var/tmp/usb
root@% ls
junos-srxxxx-xxx.tgz
root@%
6. Copy the file from USB storage to internal flash

root@% cp /var/tmp/usb/junos-srxxxx-xxx.tgz /root/.

Or it's possible to upgrade JUNOS software from the USB storage directly.

root> request system software add /var/tmp/usb/junos-srxxxx-xxx.tgz

<options...>
In order to recognize device name in SRX series.
When a USB storage is inserted in a USB slot. the system shows the infomation of inserted device name on the
console or can be verified it using "dmesg" command.

For example,
When the system displays the following message, the device name is "/dev/da2s1" in this case.

----------------------------------------------------root@% umass1: SanDisk MobileMate Micro, rev 2.00/94.07, addr 4

da2 at umass-sim1 bus 1 target 0 lun 0
da2: <Generic STORAGE DEVICE 9407> Removable Direct Access SCSI-0 device
da2: 40.000MB/s transfers
da2: 982MB (2012160 512 byte sectors: 64H 32S/T 982C)
----------------------------------------------------Note that the device name is not related with the used slot or module number. It is considered that the number of
device such as da1 and da2 increments as the device is mounted.
But the beginning number of device differs on platform. So it's highly recommended to confirm the number of device
everytime a new device is inserted.
For more information about the Junos Software Installation refer to [KB16652] SRX Getting Started - Junos Software
Installation/Upgrade .

EX/SRX/J/MX] How to mount a USB drive on the EX/J/SRX/MX series

platforms
SUMMARY:
This article provides information on how to mount a USB drive on an EX/J/SRX/MX series device and copy files to or
from the device via the USB drive.

PROBLEM OR GOAL:
How to mount a USB drive on an EX/J/SRX/MX series device and copy files to or from the device via the USB drive.

CAUSE:
SOLUTION:

1.

The following procedure allow users to mount a USB device on EX/J/SRX/MX devices. This can be helpful if network
connectivity is unavailable and you need to copy files to or from the device.
Enter the shell as root:

2.
3.
4.

user@switch> start shell user root

Password:
root@switch%

5.

Before inserting the USB device, perform the following:

6.
7.
8.
9.

root@% ls /dev/da*
/dev/da0 /dev/da0s1c /dev/da0s2a /dev/da0s3 /dev/da0s3e
/dev/da0s1 /dev/da0s1f /dev/da0s2c /dev/da0s3c
/dev/da0s1a /dev/da0s2 /dev/da0s2f /dev/da0s3d

10.

Insert the USB drive in the USB port. The following output will be displayed:

11.
12.
13.
14.
15.
16.

root@% umass1: TOSHIBA TransMemory, rev 2.00/1.00, addr 3

da2 at umass-sim1 bus 1 target 0 lun 0
da2: <TOSHIBA TransMemory 5.00> Removable Direct Access SCSI-0 device
da2: 40.000MB/s transfers
da2: 983MB (2013184 512 byte sectors: 64H 32S/T 983C)

17.
18.
19.
20.

root@% ls /dev/da*
/dev/da0 /dev/da0s1c /dev/da0s2a /dev/da0s3 /dev/da0s3e
/dev/da0s1 /dev/da0s1f /dev/da0s2c /dev/da0s3c /dev/da2
/dev/da0s1a /dev/da0s2 /dev/da0s2f /dev/da0s3d /dev/da2s1
Note: '/dev/da2s1' is the USB drive.

21.

Create a directory for the USB drive to mount to:

root@% mkdir /var/tmp/usb

22.

Mount the USB drive to the /var/tmp/usb directory:

23.
24.
25.

root@% mount_msdosfs /dev/da2s1 /var/tmp/usb

root@% ls /var/tmp/usb
images.tgz
Note: 'ls /var/tmp/usb' will show all the files in the USB drive.

26.

Copy any of the USB files to the /var/tmp/usb directory:

27.
28.

root@% cp /var/tmp/usb/images.tgz /var/tmp

root@% ls /var/tmp
images.tgz
The images.tgz file from the USB is successfully copied to the /var/tmp directory.

29.

Now unmount the USB drive after the file is completely copied:

30.
31.
32.
33.

root@% umount /var/tmp/usb

root@% umass1: at uhub0 port 1 (addr 3) disconnected
(da1:umass-sim1:1:0:0): lost device
(da1:umass-sim1:1:0:0): removing device entry
umass1: detached

[SRX/J-series] How to copy a file from one node to another node in a

JSRP chassis cluster
SUMMARY:
This article provides information on how to copy a file from one node to another node in a JSRP chassis cluster.

PROBLEM OR GOAL:
When the chassis cluster is enabled, you may want to transfer a file from one node to another node. For example, if a
secondary node is not reachable via FXP0 and you want to move the Junos image from one node to another node to
upgrade both of the nodes.
Another example is when debug log files are collected on the secondary node (node1), but node1 does not
have FXP0connected to a management network. So, they cannot be retrieved. However, the primary node (node0)
has FXP0connected to the management network. The workaround is to copy the debug log files that are captured
on node1 tonode0. Then the files can be retrieved from the network for further analysis.

CAUSE:
SOLUTION:
Peform the following procedure:
1.

Check the status of the chassis cluster by using the following command:

>show chassis cluster status

The target node should not be shown as lost. If it is, then check if the CTRL Link is up or not or the other device is
powered on or not.
2.

Check if the Fabric link is up or not by using the following command:

>show interfaces terse fab*

Or

>show interfaces terse | match fab

The fabric links should be shown as Admin up and Link up. If not, then check the cables/lights on the ports and
reseat
them.
If the other node is down, then reboot it. After the reboot, check Steps 1 and 2. If the links still do not show up, then
refer to KB20687 - Troubleshooting steps to correct a Fabric Link that is down in a Chassis Cluster.
3.

After you have confirmed that the target node and fabric link are up, proceed with the copying of the file. For
this example, assume that the source file is /var/tmp/abc.log and the target directory is /var/log/. Also, assume that
the
target
node
is node1:
Use

either

of

the

following

methods:

Via the CLI:

>file copy /var/tmp/abc.log node1:/var/log/

Or
Run the following commands, as per the order, via the shell:

>start
shell
%rcp -T /var/tmp/abc.log node1:/var/log/

user

root

Note: The first method is faster than the second method; RCP is slower.
4.

If the commands in Step 3 fail, then the last resort method is via USB. Assuming that the source node
is node0and the target node is node1, perform the following procedure:

a.

Insert a MSDOS/FAT formatted USB drive in node0 and wait for the device ID to show up. Assume
that it shows up as da1.

b.

Mount the USB drive via the shell and copy the file by using the following commands:

d.

Remove the USB drive.

e.

Insert the USB drive in node1.

c. %mount -t msdosfs /dev/da1s1 /mnt

%cp /var/tmp/abc.log /mnt/
This command will copy the file to the USB drive

f.
5.
a.

Mount the USB drive and copy it's content to node1 by performing step b. The source will
be /mnt/abc.logand the target will be /var/log// .
To verify the presence of the file in node1 from node0 itself, perform the following procedure:
Logon to node1 by using the following command:

> request routing-engine login node 1

For high-end devices, use the following command via the shell:

%rlogin -Jk -T node1

b.

Now check the target directory in node1:

>file list /var/log/ details | match abc.log

The file should be displayed, if the process is successful.

http://www.juniper.net/techpubs/en_US/junos14.2/topics/task/troubleshooting/tr
oubleshooting-logs-compressing.html
https://forum.ivorde.com/juniper-srx-how-to-collect-rsi-request-supportinformation-to-provide-it-to-juniper-tac-t14671.html
http://kb.juniper.net/InfoCenter/index?page=content&id=KB21781