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


Installing Software When a Firewall Does Not Exist

If there is no firewall between the ERX system and the network host on which you mount the software CD, you can transfer the software release files from the network host to the ERX system via the ERX FTP server or by issuing the copy command. To transfer files via the ERX 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 a hidden FTP client on the ERX system.

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 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. (For systems that are operating) Stop operation.
  3. Access the Privileged Exec CLI command mode.
  4. Configure IP on an interface.
  5. Configure access to the network host.
  6. Mount the CD on the network host.
  7. Copy the software release file to the ERX system.
  8. Save the current configuration.
  9. Reboot the system.

Task 1: Obtain the Required Information

Before you install the software, obtain the following information:

Task 2: Divert Network Traffic to Another System

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


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 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 ipAddress

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: Mount the CD on the Network Host

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 check with your network administrator.

Task 7: Copy the Software Release File

To copy the software release file to the ERX system, use the copy command.



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

For example:

host1#copy hostname:/cdrom/x-y-z/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 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)#
  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.

Installing Software in Boot Mode

To install the ERX software in Boot mode, you must access the CLI via the local console.

To install the software:

  1. Obtain the required information for the installation.
  2. Access the Boot mode.
  3. Assign an IP address to the ERX system.
  4. Configure access to the network host.
  5. Mount the CD on the network host.
  6. Copy the software release file to the ERX system.
  7. Reboot the system.

Task 1: Obtain the Required Information

Before you install the software, obtain the following information:

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.

  1. 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 ERX system in boot mode, the address is configured on the Fast Ethernet port of the primary SRP module. To assign an Internet address to the ERX system, 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, complete the following steps:

  1. Configure a gateway through which the ERX system will reach the network host.
:boot##ip gateway ipAddress
  1. Determine whether the ERX system 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.

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

The host command allows you to specify the network host name and IP address.

Task 6: Mount the CD on the Network Host

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 check with your network administrator.

Task 7: Copy the Software Release File

To copy the software release file to the ERX system, use the copy command.



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

For example:

:boot##copy hostname:/cdrom/x-y-z/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 8: 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 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. Run the reload command.
:boot##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]