Installing Software When A Firewall Does Not Exist; Installing Software In Normal Operational Mode - Juniper SYSTEM BASICS - CONFIGURATION GUIDE V 11.1.X Configuration Manual

JUNOSe 11.1.x System Basics Configuration Guide
3.
4.
5.

Installing Software When a Firewall Does Not Exist

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" on page 127. 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.

Installing Software in Normal Operational 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 13 on page 133.)
132
Installing Software When a Firewall Does Not Exist
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.
Press Ctrl+z to return to Privileged Exec mode.
Verify that the router is ready to boot with the new software release.
host1#show boot
If the old software version is still listed, verify that you completed the previous
steps correctly.
Run the reload command.
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.