|
|
When modifying your routing environment, you need to perform some general startup tasks. For example, you can modify the configuration register boot field to tell the Mutilayer Switch Feature Card (MSFC) if and how to load a system image upon startup. Or, instead of using the default system image and configuration file to start up, you can specify a particular system image and configuration file that the MSFC uses to start up.
This chapter contains these sections:
Two MSFC images are provided on the MSFC bootflash: a boot loader image and a system image. The boot loader image is a limited function system image that has network interface code and end-host protocol code. The system image is the main Cisco IOS software image with full multiprotocol routing support.
As shipped, the MSFC is configured to boot the boot loader image first, which then boots the system image from the bootflash. However, if a Flash PC card is available on the supervisor engine, we recommend that you store all new system images (upgrades) on the supervisor engine Flash PC card instead of the bootflash on the MSFC. The boot loader image must stay on the MSFC bootflash.
 | Caution Do not erase the boot loader image; this image must always remain as the first image on the MSFC bootflash as it is always used as the first image to boot. |
To store the system image on the supervisor Flash PC card, you need to change the configuration on the MSFC to boot the MSFC from the appropriate image on the Flash PC card by adding the following global command to the MSFC configuration:
boot system flash sup-slot0:system_image
In the above example, system_image is the name of the desired image on the supervisor Flash PC card.
By following this recommendation, there is really no need to store new system images on the bootflash. If desired, you can update the system image on the bootflash from an image on the supervisor engine Flash PC card by entering these commands:
delete bootflash:old_system_image squeeze bootflash: copy sup-slot0:new_system_image bootflash:
Configuration information resides in two places when the MSFC is operating: the default (permanent) configuration in NVRAM and the running (temporary) memory in RAM. The default configuration always remains available; NVRAM retains the information even when the power is shut down. The current information is lost if the system power is shut down. The current configuration contains all nondefault configuration information that you added by using the configure command or the setup command facility, or by editing the configuration file.
The copy running-config startup-config command adds the current configuration to the default configuration in NVRAM, so that it is saved if power is shut down. Whenever you make changes to the system configuration, enter the copy running-config startup-config command to save the new configuration.
If you replace the MSFC, you need to replace the entire configuration. If you upload (copy) the configuration file to a remote server before removing the MSFC, you can retrieve it later and write it into NVRAM on the new MSFC. If you do not upload the configuration file, you need to use the configure command to reenter the configuration information after you install the new MSFC.
Saving and retrieving the configuration file is not necessary if you are temporarily removing an MSFC that you are going to reinstall; the lithium batteries retain the configuration in memory. This procedure requires privileged-level access to the EXEC command interpreter, which usually requires a password.
Before you upload (copy) the running configuration to the TFTP file server, ensure the following:
To store information on a remote host, enter the privileged write network EXEC command. This command prompts you for the destination host address and a filename and then displays the instructions for confirmation. When you confirm the instructions, the MSFC sends a copy of the currently running configuration to the remote host. The system default is to store the configuration in a file called by the name of the MSFC with -confg appended. You can either accept the default filename by pressing Return at the prompt, or enter a different name before pressing Return.
Follow these steps to upload (copy) the currently running configuration to a remote host:
Step 1 Check if the system prompt displays a pound sign (#) to indicate the privileged level of the EXEC command interpreter.
Step 2 Enter the ping command to check the connection between the MSFC and the remote host.
Step 3 Enter the write term command to display the currently running configuration on the terminal and ensure that the configuration information is complete and correct. If it is not correct, enter the configure command to add or modify the existing configuration.
Step 4 Enter the write net command. The EXEC command interpreter prompts you for the name or IP address of the remote host that is to receive the configuration file. (The prompt might include the name or address of a default file server.)
Router# write net Remote host []?
Step 5 Enter the name or IP address of the remote host. In this example, the name of the remote server is servername:
Router# write net Remote host []? servername Translating "servername"...domain server (1.1.1.1) [OK]
Step 6 Note that the EXEC command interpreter prompts you to specify a name for the file that is to hold the configuration. By default, the system appends -confg to the MSFC name to create the new filename. Press Return to accept the default filename, or enter a different name for the file before pressing Return. In the following example, the default is accepted:
Name of configuration file to write [Router-confg]? Write file Router-confg on host 1.1.1.1? [confirm] Writing Router-confg .....
Step 7 Note that before the MSFC executes the copy process, it displays the instructions you entered for confirmation. If the instructions are not correct, enter n (no) and then Return to abort the process. To accept the instructions, press Return or y (yes) and then Return, and the system begins the copy process. In the following example, the default is accepted:
Write file Router-confg on host 1.1.1.1? [confirm] Writing Router-confg: !!!! [ok]
While the MSFC copies the configuration to the remote host, it displays a series of exclamation points (! ! !) or periods (. . .). The ! ! ! and [ok] indicate that the operation is successful. A display of . . . [timed out] or [failed] indicates a failure, which would probably be due to a network fault or the lack of a writable, readable file on the remote file server.
Step 8 Note that if the display indicates that the process was successful (with the series of ! ! ! and [ok]), the upload process is complete. The configuration is safely stored in the temporary file on the remote file server.
If the display indicates that the process failed (with the series of . . . as shown in the following example):
Writing Router-confg .....
your configuration was not saved. Repeat the preceding steps, or select a different remote file server and repeat the preceding steps.
If you are unable to copy the configuration to a remote host successfully, contact your network administrator or see the "Cisco Connection Online" section for instructions on contacting the technical assistance center.
To upload the configuration file to the supervisor engine Flash PC card in PCMCIA slot 0, perform this task:
| Task | Command |
|---|---|
Step 1 At the EXEC prompt, enter enable mode. | Router> enable |
Step 2 Copy the startup configuration file to slot 0. | Router# copy startup-config sup-slot0:file_name |
Step 3 Copy the running configuration file to slot 0. | Router# copy running-config sup-slot0:file_name |
After you install the new MSFC, you can retrieve the saved configuration and copy it to NVRAM. Enter configuration mode and specify that you want to configure the MSFC from the network. The system prompts you for a host name and address, the name of the configuration file stored on the host, and confirmation to reboot using the remote file.
Follow these steps to download (retrieve) the currently running configuration from a remote host:
Step 1 Check if the system prompt displays a pound sign (#) to indicate the privileged level of the EXEC command interpreter.
Step 2 Enter the ping command to verify the connection between the router and the remote host.
Step 3 At the system prompt, enter the configure network command and press Return to enter configuration mode. Specify that you want to configure the system from a network device (instead of from the console terminal, which is the default).
Router# configure network
Step 4 Note that the system prompts you to select a host or network configuration file. The default is host; press Return to accept the default.
Host or network configuration file [host]?
Step 5 Note that the system prompts you for the IP address of the host. Enter the IP address or name of the remote host (the remote file server to which you uploaded the configuration file).
IP address of remote host [255.255.255.255]? 1.1.1.1
Step 6 Note that the system prompts you for the configuration filename. When uploading the file, the default is to use the name of the MSFC with the suffix -confg (router-confg in the following example). If you specified a different filename when you uploaded the configuration, enter the filename; otherwise, press Return to accept the default.
Name of configuration file [router-confg]?
Step 7 Note that before the system reboots with the new configuration, it displays the instructions you entered for confirmation. If the instructions are not correct, enter n (no), and then press Return to cancel the process. To accept the instructions, press Return, or y, and then Return.
Configure using router-confg from 1.1.1.1? [confirm] Booting router-confg from 1.1.1.1: ! ! [OK - 874/16000 bytes]
While the MSFC retrieves and boots from the configuration on the remote host, the console display indicates whether or not the operation was successful. A series of !!!! and [OK] (as shown in the preceding example) indicate that the operation was successful. A series of . . . and [timed out] or [failed] indicate a failure (which would probably be due to a network fault or an incorrect server name, address, or filename). The following is an example of a failed attempt to boot from a remote server:
Booting Router-confg ..... [timed out]
Step 8 Proceed to the next step if the display indicates that the process was successful.
If the display indicates that the process failed, verify the name or address of the remote server and the filename, and repeat the preceding steps. If you are unable to retrieve the configuration, contact your network administrator or see the "Cisco Connection Online" section for instructions on contacting the technical assistance center.
Step 9 Enter the write term command to display the currently running configuration on the terminal. Review the display and ensure that the configuration information is complete and correct. If it is not, verify the filename and repeat the preceding steps to retrieve the correct file, or use the configure command to add or modify the existing configuration. (See the appropriate software documentation for the configuration options available for the system, the individual interfaces, and specific configuration instructions.)
Step 10 When you have verified that the currently running configuration is correct, enter the copy running-config startup-config command to save the retrieved configuration in NVRAM. Otherwise, you will lose the new configuration if you restart the system.
This completes the procedure for downloading (retrieving) the configuration file.
To download the configuration file from the supervisor engine Flash PC card in PCMCIA slot 0, perform this task:
| Task | Command |
|---|---|
Step 1 At the EXEC prompt, enter enable mode. | Router> enable |
Step 2 Copy the stored running configuration file to the MSFC running configuration. | Router# copy sup-slot0: file_name running-config |
Step 3 Copy the stored startup configuration file to the MSFC running configuration | Router# copy sup-slot0:file_name startup-config |
To enter configuration mode, enter the configure command at the privileged EXEC prompt. The MSFC responds with this prompt asking you to specify the terminal or memory, or a file stored on a network server (network) as the source of configuration commands:
Configuring from terminal, memory, or network [terminal]?
These tasks are described in the following sections:
The MSFC accepts one configuration command per line. You can enter as many configuration commands as you want.
You can add comments to a configuration file describing the commands you have entered. Precede a comment with an exclamation point (!). Because comments are not stored in NVRAM or in the active copy of the configuration file, comments do not appear when you list the active configuration with the show running-config EXEC command. Also, when the startup configuration is NVRAM, comments do not show up when you list the startup configuration with the show startup-config EXEC command. Comments are stripped out of the configuration file when it is loaded onto the MSFC. However, you can list the comments in configuration files stored on a TFTP or rcp server.
When you configure the MSFC from the terminal, the MSFC executes the commands you enter at the system prompts. To configure the MSFC from the terminal, perform this task:
| Task | Command |
|---|---|
Step 1 Enter configuration mode and select the terminal option. | configure terminal |
Step 2 Enter the necessary configuration commands. | See the "Configuring InterVLAN Routing on the MSFC" section. |
Step 3 Quit configuration mode. | ^Z |
Step 4 Save the configuration file to your startup configuration. This step saves the configuration to the location specified by the CONFIG_FILE environment variable. | copy running-config startup-config |
The following command configures the MSFC to execute the configuration specified by the CONFIG_FILE environment variable.
To configure the MSFC to execute the configuration specified by the CONFIG_FILE environment variable, perform this task in privileged EXEC mode:
| Task | Command |
|---|---|
Configure the MSFC to execute the configuration specified by the CONFIG_FILE environment variable. | configure memory |
To configure the MSFC by retrieving and modifying a configuration file stored on one of your network servers, perform this task:
| Task | Command |
|---|---|
Step 1 Enter configuration mode with the network option. | copy rcp running-config or copy tftp running-config |
Step 2 At the system prompt, select a network or host configuration file. The network configuration file contains commands that apply to all network servers and terminal servers on the network. The host configuration file contains commands that apply to one network server in particular. | host or network |
Step 3 At the system prompt, enter the optional IP address of the remote host from which you are retrieving the configuration file. | ip-address |
Step 4 At the system prompt, enter the name of the configuration file or accept the default name. | filename |
Step 5 Confirm the configuration filename that the system supplies. | y |
To configure the MSFC by retrieving and modifying a configuration file stored in the supervisor engine Flash PC card, perform this task:
| Task | Command |
|---|---|
Step 1 At the EXEC prompt, enter enable mode. | Router> enable |
Step 2 At the privileged EXEC prompt, enter global configuration mode. | Router# configure terminal |
Step 3 Specify the filename to be copied from slot 0 on the supervisor engine to the MSFC running configuration. | Router# copy sup-slot0:file_name running-config |
This task loads a configuration file directly into the location specified by the CONFIG_FILE environment variable without affecting the running configuration.
To copy a configuration file directly to the startup configuration, perform this task in EXEC mode:
| Task | Command |
|---|---|
Load a configuration file directly into the location specified by the CONFIG_FILE environment variable. | copy rcp startup-config or copy tftp startup-config |
Posted: Fri Apr 14 12:31:49 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.