# 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. 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.)

Table 13: Software Installation Procedure When a Firewall Does Not Exist

Obtain the required information for the installation. For routers that are currently operating, divert network traffic to another router. Access the Privileged Exec CLI command mode. Configure IP on an interface. Configure access to the network host. Copy the release files to the network host. Copy the software release file to the router. Save the current configuration. Reboot the system.

### Task 1: Obtain the Required Information

Before you install the software, obtain the following information:

- The password (if one is configured) that enables you to access Privileged Exec mode on the router
- The IP address of the network host
- The IP address of the router
- The IP address of the next hop to reach the destination network (for example, a gateway)
- The login name and password for the FTP server
- The procedure for copying the release files to the network host

### Task 2: Divert Network Traffic to Another Router

The system will be unavailable during the installation process.

### Task 3: Access Privileged Exec Mode

To access this mode via the CLI:

1. Issue the enable command.
   host1>enable
2. Type the password if the system prompts you.

### Task 4: Configure IP on an Interface

Typically, you configure IP on the Fast Ethernet interface of the SRP module. To configure IP on an interface:

1. Determine the slot number of the module.
   host1#show version
2. Determine the port number of the module.
3. Determine whether the interface already has an IP address.
   - On ERX7xx models, ERX14xx models, and the ERX310 router:
     host1#show ip interface fastEthernet 6/0
   - On the E120 and E320 routers:
     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.

4. Configure an IP address on the interface.
   - On ERX7xx models, ERX14xx models, and the ERX310 router:
     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 ]
   - On the E120 and E320 routers:
     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 ]
5. Press Ctrl+z to return to Privileged Exec mode.

### Task 5: Configure Access to the Network Host

To configure access to the network host:

1. Use the ping command to determine whether the router can reach the network host.
   host1# ping ipAddress

   If the router can reach the network host, go to the next section. Otherwise, go to Step 2.

2. Determine whether a route exists between the router and the network host.
   host1#show ip route

   If the appropriate route is displayed, go to Step 4. Otherwise, proceed with Step 3.

3. Configure a route to reach the network host.
   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
4. Press Ctrl+z to return to Privileged Exec mode.
5. Determine whether the router has been configured to recognize the network host.
   host1#show host

   If the network host is listed, go to Step 8. Otherwise, proceed with Step 6.

6. Add an entry to the Static Host Table so that the router can access the network host. Use the host command to specify the network hostname and IP address.
   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
7. Press Ctrl+z to return to Privileged Exec mode.
8. Use the ping command to determine whether the router can now reach the network host.
   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.

### Task 6: Copy the Release Files to the Network Host

If you downloaded the software from the Juniper Networks website 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 that you created from the downloaded software image package, 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.

### Task 7: Copy the Software Release File to the Router

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.

### Task 8: Save the Current Configuration

To save the current configuration, use the copy running-configuration command:

host1#copy running-configuration filename.cnf

### Task 9: Reboot the System

To reboot the system using the newly installed software:

1. Access Global Configuration mode.
   host1#configure Configuring from terminal or file [terminal]?Enter configuration commands, one per line. End with CNTL/Z. host1(config)#
2. Run the boot system command, specifying the .rel filename of the software release. For example:
   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.
3. Press Ctrl+z to return to Privileged Exec mode.
4. Make sure 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.

5. 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.

## Installing Software in Boot Mode

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 14.)

Table 14: Software Installation Procedure in Boot Mode

Obtain the required information for the installation. For routers that are currently operating, divert network traffic to another router. Access the Boot mode. Assign an IP address to the router. Configure access to the network host. Reset the SRP module. Copy the release files to the network host. Copy the software release file to the router. Reboot the system.

### Task 1: Obtain the Required Information

Before you install the software, obtain the following information:

- The IP address of the network host
- The IP address of the router
- The IP address of the next hop to reach the destination network (for example, a gateway)
- The login name and password for the FTP server
- The procedure for copying the release files to the network host

### Task 2: Divert Network Traffic to Another System

The system will be unavailable during the installation process.

### Task 3: Access the Boot Mode

To access Boot mode from the local console:

1. At the Privileged Exec prompt, type the reload command.

   Information on the reloading process appears.

2. When the countdown begins, press the key sequence mb.

   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.

### Task 4: Assign an IP Address

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 ]

### Task 5: Configure Access to the Network Host

To configure access to the network host:

1. Configure a gateway through which the router can reach the network host.
   :boot##ip gateway ipAddress
2. Determine whether the router has been configured to recognize the network host.
   :boot##show host

   If the network host is listed, go to the next section. Otherwise, proceed with Step 3.

3. Add an entry to the Static Host Table so that the router can access the network host.
   :boot##host hostName ipAddress ftp login-name password

   Use the host command to specify the network host name and IP address.

### Task 6: Resetting the SRP Module

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.

### Task 7: Copy the Release Files to the Network Host

If you downloaded the software from the Juniper Networks website 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 that you created from the compressed image bundle that you downloaded from the website, 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.

### Task 8: Copy the Software Release File to the Router

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.

### Task 9: Reboot the System

To reboot the system using the newly installed software:

1. Run the boot system command, specifying the .rel filename of the software release. For example:
   :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.
2. Run the reload command.
   :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.