If there is no firewall between the router and the network host to which you copied the release files, you can transfer the software release files from the network host to the router via the FTP server or by issuing the copy command. To transfer files via the FTP server, refer to the previous section, Installing Software When a Firewall Exists. This section describes how to transfer files by issuing the copy command.
If you use the copy command to transfer the files, the network host must be an FTP server. This command activates an FTP client on the router.
For this network configuration, you can install the software in the normal command line interface (CLI) operational mode or in boot mode.
For this procedure, you must access the CLI through either the local console or a Telnet session. If you have not yet configured the router to support Telnet, then you must use the local console.
To install the software, perform the following tasks. (See Table 14.)
Table 14: Software Installation Procedure When a Firewall Does Not Exist
Before you install the software, obtain the following information:
The system will be unavailable during the installation process.
To access this mode via the CLI:
Typically, you configure IP on the Fast Ethernet interface of the SRP module. To configure IP on an interface:
- host1#show version
- host1#show ip interface fastEthernet 6/0
- host1#show ip interface fastEthernet 6/0/0
![]() |
Note: If an IP interface is not configured, an Invalid interface message appears. |
If the interface already has an IP address, go to Step 5. Otherwise, proceed with Step 4.
- host1#configure
- Configuring from terminal or file [terminal]?
- Enter configuration commands, one per line. End with CNTL/Z.
- host1(config)#interface fastEthernet 6/0
- host1(config-if)#ip address ipAddress [ mask ]
- host1#configure
- Configuring from terminal or file [terminal]?
- Enter configuration commands, one per line. End with CNTL/Z.
- host1(config)#interface fastEthernet 6/0/0
- host1(config-if)#ip address ipAddress [ mask ]
To configure access to the network host:
- host1#ping ipAddress
If the router can reach the network host, go to the next section. Otherwise, go to Step 2.
- host1#show ip route
If the appropriate route is displayed, go to Step 4. Otherwise, proceed with Step 3.
- host1#configure
- Configuring from terminal or file [terminal]?
- Enter configuration commands, one per line. End with CNTL/Z.
- host1(config)#ip route ipNetwork networkMask ipNextHop
- host1#show host
If the network host is listed, go to Step 8. Otherwise, proceed with Step 6.
- host1#configure
- Configuring from terminal or file [terminal]?
- Enter configuration commands, one per line. End with CNTL/Z.
- host1(config)#host hostName ipAddress ftp loginname password
- host1#ping hostname
If the router cannot reach the network host, verify that you correctly performed the previous steps in this procedure and that the network host is operational.
If you downloaded the software from the Juniper Networks Web site as a .zip file, uncompress the files to a directory, and copy the release files to the network host.
If you are accessing the release files from one of the software CDs, you must mount the CD. The way you mount the CD on the network host depends on the type of network host you use, the operating system, and the way your network is configured. To find out how to mount a CD on the network host, review the manual for the operating system, or contact your network administrator.
To copy the software release file to the router, use the copy command.
Be sure to specify the correct software release (.rel) filename for the router you are using, as described in Identifying the Software Release File.
![]() |
Note: The destination file must have a .rel extension. |
For example:
- host1#copy hostname:/cdrom/x-y-z/erx_x-y-z.rel
erx_x-y-z.rel
The software release is copied from the network host to the router. This process can take several minutes.
To save the current configuration, use the copy running-configuration command:
- host1#copy running-configuration filename.cnf
To reboot the system using the newly installed software:
- host1#configure
- Configuring from terminal or file [terminal]?
- Enter configuration commands, one per line. End with CNTL/Z.
- host1(config)#
- host1(config)#boot system erx_x-y-z.rel
The following message appears when you issue this command:
- WARNING: We recommend that you copy the current running-
configuration to a file prior to reloading a different release of
software.
- host1#show boot
If the old software version is still listed, verify that you completed the previous steps correctly.
- host1#reload
The following message appears when you issue this command:
- WARNING: Execution of this command will cause the system
to reboot. Proceed with reload? [confirm]
The system reboots. The reboot might take longer than normal because line modules initialize with the old version of the software, acquire the new version from the SRP module, and reinitialize. When you observe the LEDs on the line modules, the line modules appear to boot twice.
To install the software in Boot mode, you must access the CLI via the local console.
To install the software, perform the following tasks. (See Table 15.)
Table 15: Software Installation Procedure in Boot Mode
Before you install the software, obtain the following information:
The system will be unavailable during the installation process.
To access Boot mode from the local console:
Information on the reloading process appears.
This action puts the CLI in Boot mode and the :boot## prompt appears.
![]() |
Note: If you do not press the key sequence mb before the countdown ends, the reloading process continues and returns the CLI to the normal User Exec mode. |
When you assign an IP address to the router in Boot mode, the address is configured on the Fast Ethernet port of the primary SRP module. To assign an Internet address to the router, use the ip address command.
- :boot##ip address ipAddress [ mask ]
To configure access to the network host:
- :boot##ip gateway ipAddress
- :boot##show host
If the network host is listed, go to the next section. Otherwise, proceed with Step 3.
- :boot##host hostName
ipAddress ftp login-name
password
Use the host command to specify the network host name and IP address.
To ensure that the IP addresses are properly activated, you must reset the SRP module. To reset the SRP module, issue the reload command from the :boot## prompt or depress the recessed module reset button located on the front of the module.
Depressing the module reset button on the SRP module is equivalent to rebooting the router and causes all of the line modules to reboot.
If you downloaded the software from the Juniper Networks Web site as a .zip file, uncompress the files to a directory, and copy the release files to the network host.
If you are accessing the release files from one of the software CDs, you must mount the CD. The way you mount the CD on the network host depends on the type of network host you use, the operating system, and the way your network is configured. To find out how to mount a CD on the network host, review the manual for the operating system, or contact your network administrator.
To copy the software release file to the router, use the copy command.
Be sure to specify the correct software release (.rel) filename for the router you are using, as described in Identifying the Software Release File.
![]() |
Note: The destination file must have a .rel extension. |
For example:
- :boot##copy hostname:/cdrom/x-y-z/erx_x-y-z.rel
erx_x-y-z.rel
The software release is copied from the network host to the router. This process can take several minutes.
To reboot the system using the newly installed software:
- :boot##boot system erx_x-y-z.rel
The following message appears when you issue this command:
- WARNING: We recommend that you copy the current running-configuration
to a file prior to reloading a different release of software.
- :boot##reload
The following message appears when you issue this command:
- WARNING: Execution of this command will cause the system
to reboot. Proceed with reload? [confirm]
The system reboots. The reboot might take longer than normal because line modules initialize with the old version of the software, acquire the new version from the SRP module, and reinitialize. When you observe the LEDs on the line modules, the line modules appear to boot twice.