[Contents] [Prev] [Next] [Index] [Report an Error]


Installing Software When a Firewall Exists

When a firewall separates the ERX system from the network host, you must FTP the software release files from the network host to the ERX system. In this case, you must configure the FTP server on the ERX system and ensure that FTP client software is installed on the network host.

For this network configuration, you must install the software from the normal operational mode of the command line interface (CLI). You can access the CLI through either the local console or a Telnet session. If you have not yet configured the ERX system to support Telnet, then you must use the local console. See Chapter 5, Accessing the ERX System, for information on using a local console or a Telnet session.

To install the software, perform the following tasks:

  1. Obtain the required information for the installation.
  2. Access the Privileged Exec CLI command mode.
  3. Configure IP on an interface.
  4. Mount the CD on the network host.
  5. Configure access to the network host.
  6. Enable the FTP server on the ERX system.
  7. Identify the files to transfer.
  8. Transfer the files to the user space on the ERX system.
  9. Install the software release file to the system space on the ERX system.
  10. Save the current configuration.
  11. Reboot the system.

Task 1: Obtain the Required Information

Before you install the software, obtain the following information:

Task 2: Access Privileged Exec Mode

To access this mode via the CLI:

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

Task 3: 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
  1. Determine the port number of the module.
  2. Determine whether the interface already has an IP address.
host1#show ip interface fastEthernet 6/0


Note: If an IP interface is not configured, you see the message "Invalid interface."

If the interface already has an IP address, go to step 5. Otherwise, proceed with step 4.

  1. Set an IP address on the interface.
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 ]
  1. Press <CTRL-Z>, to return to Privileged Exec mode.

Task 4: Mount the CD on the Network Host

The way you mount the CD on the network host depends on the type of computer you use, the operating system, and the network configuration. To find out how to mount a CD on the network host, review the manual for the operating system, or check with your network administrator.

Task 5: Configure Access to the Network Host

To configure access to the network host:

  1. Use the ping command to determine whether the ERX system can reach the network host.
host1#ping hostname

If the ERX system can reach the network host, go to the next section. Otherwise, go to step 2.

  1. Determine if a route exists between the ERX system and the network host.
host1#show ip route

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

  1. 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
  1. Press <CTRL-Z> to return to Privileged Exec mode.
  2. Determine whether the ERX system 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.

  1. Add an entry to the Static Host Table so that the ERX system can access the network host. The host command allows you to specify the network host name 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
  1. Press <CTRL-Z> to return to Privileged Exec mode.
  2. Use the ping command to determine whether the ERX system can now reach the network host.
host1#ping hostname

If the ERX system cannot reach the network host, verify that you performed the previous steps in this procedure correctly and that the network host is operational.

Task 6: Enable the FTP Server on the ERX System

The ERX system divides its vty resources among Telnet, SSH, and FTP services. Each FTP session requires one vty line, and the FTP service uses the authentication method configured for the vty line. If you configured more than one vty line for Telnet access, the FTP service will use one of those lines. If you configured only one line for Telnet access, configure another vty line. See Chapter 5, Accessing the ERX System.

To enable the FTP Server, use the ftp-server enable command.

host1(config)#ftp-server enable

Task 7: Identify the Files to Transfer

To identify all the files for the release, open the software release (.rel) file on the ERX software CD with a text editor. The software release file contains a list of all the files associated with the release. You must transfer the software release file and all the files it contains to the user space.

Task 8: Transfer Files to the User Space

To transfer the files for the release to the ERX user space, use the FTP client software on the network host to connect to the FTP server on the ERX system. Transfer the files to a subdirectory within the incoming directory. If you specify a subdirectory that does not exist, the ERX system creates the directory.



Note: Be sure to transfer the software release file and all the files it lists.

Task 9: Install Files on the System Space

Installing the software release file to the system space installs all files listed in the software release file. To install the software release file from the incoming directory in the ERX user space to the ERX system space, use the copy command.



Note: The destination file must have a .rel extension.

For example:

host1#copy /incoming/releases/x-y-z.rel x-y-z.rel

The software release will be copied from the network host to the ERX system. This process can take several minutes.

Task 10: Save the Current Configuration

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

host1#copy running-configuration filename.cnf

Task 11: 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)#
  1. Run the boot system command, specifying the .rel filename of the software release.

For example:

host1(config)#boot system x-y-z.rel

The following message appears when you execute this command:

WARNING: It is recommended that you copy the current 
running-configuration to a file prior to reloading a 
different release of software.
  1. Press <CTRL-Z> to return to Privileged Exec mode.
  2. Check that the ERX system 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.

  1. Run the reload command.
host1#reload

The following message appears when you execute this command:

WARNING: Execution of this command will cause the system to 
reboot. Proceed with reload? [confirm]

The system reboots. The reboot may 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.


[Contents] [Prev] [Next] [Index] [Report an Error]