Cisco 12008 Gigabit Switch Router Installation and Configuration Guide
Observing System Startup and Performing a Basic Configuration
Downloads: This chapterpdf (PDF - 439.0KB) The complete bookPDF (PDF - 5.95MB) | Feedback

Observing System Startup and Performing a Basic Configuration

Table Of Contents

Observing System Startup and Performing a Basic Configuration

Sources of Cisco IOS Software

Checking Conditions Prior to System Startup

Starting the System and Observing Initial Conditions

Configuring the Cisco 12008

Using the Setup Facility or the Setup Command

Configuring Global Parameters

Sample Display of Global Parameters

Configuring Network Interfaces

Checking the Software Version Number and the Installed Interfaces

Using the Global Configuration Mode

Verifying the Running Configuration Settings

Example of Running Configuration Settings for Quad OC-3 POS Interface

Example of Running Configuration Settings for OC-12 POS Interface

Example of Running Configuration Settings for OC-12 ATM Interface

Saving the Running Configuration Settings to NVRAM

Reviewing the Running Configuration Settings

Performing Other Configuration Tasks

Configuring the Software Configuration Register

Boot Field Settings and the Use of the Boot Command

Changing the Software Configuration Register Settings

Meaning of Bits in the Software Configuration Register

Recovering a Lost Password

Using Flash Memory Cards in the RP

Installing and Removing a Flash Memory Card in a RP

Formatting a Flash Memory Card

Specifying a Cisco IOS Image for Booting the System

Console Commands Associated with Flash Memory Use

Enabling Booting from Flash Memory

Copying Files to a Flash Memory Medium

Copying a Cisco IOS Software Image onto a Flash Memory Card

Copying Cisco IOS Software Images between Flash Memory Cards

Copying System Configuration Files between RP Memory and a Flash Memory Card

Recovering from Locked Blocks in Flash Memory Cards

What to Do Next?

If You Need More Configuration Information


Observing System Startup and Performing a Basic Configuration


This chapter describes the initial system startup process and provides procedures for performing a basic configuration for your Cisco 12008.

This chapter contains the following sections:

Sources of Cisco IOS Software

Checking Conditions Prior to System Startup

Starting the System and Observing Initial Conditions

Configuring the Cisco 12008

Using the Setup Facility or the Setup Command

Using the Global Configuration Mode

Verifying the Running Configuration Settings

Saving the Running Configuration Settings to NVRAM

Reviewing the Running Configuration Settings

Performing Other Configuration Tasks

Configuring the Software Configuration Register

Recovering a Lost Password

Using Flash Memory Cards in the RP

What to Do Next?

If You Need More Configuration Information

This chapter will help you to

Configure your router so that it can access the network

Enable other hosts in the network to remotely access your system by means of a Telnet connection

Detailed configuration procedures for all of the line cards and network interfaces that you can install in your Cisco 12008 are beyond the scope of this document. Such information can be found in the configuration publications listed in the later section entitled "If You Need More Configuration Information." In particular, for the Cisco 12000 series line card(s), you can refer to the configuration note(s) that shipped with your system.

Sources of Cisco IOS Software

A default Cisco IOS software image for your Cisco 12008 is available through any one of the following internal/external sources:

Onboard Flash memory single inline memory module (SIMM) on the Route Processor (RP)—The latest Cisco IOS software image is pre-loaded into the Flash memory SIMM at the factory prior to router shipment. The Flash memory SIMM is also referred to as nonvolatile random access memory (NVRAM). This type of memory retains its contents when system power is turned off.

Flash memory card—A Flash memory card inserted in a Personal Computer Memory Card Industry Association (PCMCIA) slot on the RP can serve as an external storage medium for a default Cisco IOS software image.

TFTP server—A Trivial File Transfer Protocol (TFTP) server in the network can also function as an external source of a default Cisco IOS software image. A valid Cisco IOS software image can be downloaded from such a remote host by means of a Telnet connection.

Checking Conditions Prior to System Startup

Before attempting to start up your system, verify that the following conditions exist:

All line cards in the upper card cage are fully inserted into their slots; all captive installation screws on the line cards are tightened.

All clock and scheduler cards (CSCs) in the upper card cage are fully inserted.

All switch fabric cards (SFCs) in the lower card cage are fully inserted.

All interface cables are securely attached; where appropriate, adequate cable strain relief exists.

Source power for the power supply(ies) is properly connected.

The console terminal is connected to the console port on the RP.

The console is configured for the appropriate communications parameters and turned on. (In order for you to perform the initial configuration of a Cisco 12008, you must have a console terminal connected to the console port on the RP.)

The Flash memory card that shipped with your system is inserted in PCMCIA slot 0 on the RP.


Note   By default, a Flash memory card containing a valid Cisco IOS software image is inserted in PCMCIA slot 0 prior to shipment. Also, by default, the software configuration register is set to 0x0102, causing the system to boot automatically from the Cisco IOS software image stored on the Flash memory card.


After verifying the above conditions, proceed to the next section to start up your Cisco 12008.

Starting the System and Observing Initial Conditions

This section describes the initial system startup processes and procedures.

To start up your Cisco 12008, perform the following steps:


Step 1 Apply power to each installed power supply by turning its rotary power switch fully clockwise to the ON (|) position.

As power is applied to the AC-input power supply(ies), both the green AC INPUT OK LED and the red OUTPUT FAIL LEDs go on momentarily. Refer to in Chapter 1 for the location of these LEDs on the AC-input power supply faceplate. Once system power stabilizes, the red OUTPUT FAIL LED should go off and remain so; the green AC INPUT OK LED, however, should remain on, indicating that normal power conditions exist in the router.

As power is applied to the DC-input power supply(ies), both the green INPUT OK LED and the red OUTPUT FAIL LEDs go on briefly. Refer to in Chapter 1 for the location of these LEDs on the DC-input power supply faceplate. Once system power stabilizes, the red OUTPUT FAIL LED should go off and remain so; the green INPUT OK LED, however, should remain on, indicating that normal power conditions exist in the router.

Step 2 Listen for the card cage fan tray and the power supply fan tray to power up; the fans in each fan tray should come up to full rotational speed in about 2 seconds.

The fans in both fan trays have two speeds - maximum and minimum. At initial application of system power, the fans run at maximum speed for a time until the system stabilizes. Then the fans revert to minimum speed, remaining in this state until an overtemperature condition or a card cage or power supply fan failure is detected by the router's MBus facility. Either type of error condition causes the fans in both fan trays to run at maximum speed.

In a noisy environment, the fan trays might be difficult to hear. In this case, you can place your hand behind the exhaust vents at the top rear of the router enclosure to determine if air is being expelled from the router.

Step 3 During the RP boot process, observe the two, 4-digit alphanumeric LEDs at the bottom of the RP faceplate (see Figure 4-1). Table 4-1 shows representative system messages that appear in the RP LEDs.

Figure 4-1 RP Alphanumeric LEDs (Partial Faceplate View)

Table 4-1 Typical Contents of the RP Alphanumeric LEDs

LED Display
Meaning
Source

MROM
nnnn

The MBus microcode begins to execute; nnnn is the microcode version number. For example, microcode version 1.17 would display as 0117.1 This display might not be visible, since it occurs briefly.

MBus controller

LMEM
TEST

Low memory on the RP is being tested.

RP rommon

MEM
INIT

The size of main memory on the RP is being discovered.

RP rommon

RP
RDY

The system is operational and ready to execute basic IOS commands at the ROM monitor prompt (rommon>).

RP rommon

RP
UP

A valid Cisco IOS image is running.

RP IOS

MSTR
RP

The RP is enabled and recognized as the system master. A valid Cisco IOS image is running.

RP IOS

1 The version of MBus microcode running on your system might be different.


Step 4 During the line card boot process, which occurs immediately following that of the RP, observe the alphanumeric LEDs on each line card.

The alphanumeric LEDs on a line card are also located at the bottom of the line card faceplate (see ).

Figure 4-2 Line Card Alphanumeric Displays (Partial View Shown)

shows typical contents of these line card alphanumeric LEDs. The LED display sequence shown in this table might occur too quickly to be seen; this sequence is provided to show the order of initialization and how the line cards function at startup.

Table 4-2 Typical Contents of the Line Card Alphanumeric LEDs

Line Card LED Display
Meaning
Source

MROM
nnnn

The MBus microcode begins to execute; nnnn is the microcode version number. For example, microcode version 1.17 would display as 0117.1 This display might not be visible, since it occurs briefly.

MBus controller

LMEM
TEST

Low memory on the line card is being tested.

LC rommon

MEM
INIT

The size of main memory on the line card is being discovered.

LC rommon

ROMI
GET

The ROM image is being loaded into line card memory.

RP IOS

FABL
WAIT

The line card is waiting for the loading of the fabric downloader.2

RP IOS

FABL
DNLD

The fabric downloader is being loaded into line card memory.

RP IOS

FABL
STRT

The fabric downloader is being launched.

RP IOS

FABL
RUN

The fabric downloader has been launched and is running.

RP IOS

IOS
DNLD

The Cisco IOS software is being downloaded into line card memory.

RP IOS

IOS
STRT

The Cisco IOS software is being launched.

RP IOS

IOS
UP

The Cisco IOS software is running.

RP IOS

IOS
RUN

The line card is enabled and ready for use.

RP IOS

1 The version of MBus microcode running on your system might be different.

2 The fabric downloader loads the Cisco IOS software image onto the line card.



Note   If a Flash memory card containing a valid Cisco IOS software image is inserted in PCMCIA slot 0 and the software configuration register is set to 0x0102 (the factory default setting), the system automatically boots using this image. The system then enters the setup facility, prompting you to perform a basic system configuration by means of an interactive script (see Step 9). Otherwise, the system remains at the ROM monitor prompt (rommon>), enabling you to enter configuration commands at the console terminal. In this case, proceed with Step 5.


Step 5 If the ROM monitor prompt (rommon>) appears, you must boot a Cisco IOS software image manually by issuing the boot command. The various forms of the boot command are described briefly below:

boot—This form of the boot command (without an argument) boots the default Cisco IOS software image present in the onboard Flash memory SIMM. This image is pre-loaded into the SIMM at the factory prior to router shipment.


Caution   
To prevent problems, issue the boot flash command with care. Ensure that the Flash memory card in PCMCIA slot 0 contains a valid Cisco IOS image; otherwise, you could instruct the system to boot other than a valid image from the Flash memory card. To examine the contents of a Flash memory card, issue a directory slot0: command.

boot flash—This form of the boot command does not specify a particular PCMCIA slot. Therefore, the system assumes by default that the Flash memory card is inserted in slot 0; accordingly, the system boots the first file found in the Flash memory card in slot 0.

boot slot0: filename—This form of the boot command boots the specified file from the Flash memory card in PCMCIA slot 0.

boot slot1: filename—This form of the boot command boots the specified file from the Flash memory card in PCMCIA slot 1.

boot filename [host]This form of the boot command boots the specified file from a host TFTP server in the network.

Step 6 To locate a desired Cisco IOS software image for manually booting the router from the ROM monitor prompt (rommon>), first determine the contents of the onboard Flash memory SIMM (NVRAM) on the RP by issuing the directory command:

rommon 1> dir bootflash:
   File size                  Checksum      File name
   3277967 bytes (0x32048f)   0x6b331e30    gsr-p-mz.112-9.GS4
rommon 2> 

If the onboard Flash memory SIMM contains the desired Cisco IOS boot image, proceed to Step 8. Otherwise, continue with Step 7.

Step 7 If a Flash memory card is presently inserted in PCMCIA slot 0 or slot 1 (or both), determine the contents of the card(s) by issuing the appropriate form of the following command:

rommon 2> dir slot0: | slot1:
   File size                  Checksum      File name
   3054276 bytes (0x2e9ac4) 0x97788495      gsr-p-mz.112-9.GS4
rommon 3> 

If you find the desired Cisco IOS boot image in a Flash memory card, proceed with Step 8.

Step 8 After locating the desired Cisco IOS software image for manually booting the router, select the appropriate form of the boot command from the following list and issue it at the ROM monitor prompt:

rommon 3> boot bootflash:gsr-p-mz.112-9.GS4

This command boots the specified file from the onboard Flash memory SIMM (NVRAM) on the RP.

rommon 3> boot slot0:gsr-p-mz.112-9.GS4

This command boots the specified file from the Flash memory card in PCMCIA slot 0.

rommon 3> boot slot1:gsr-p-mz.112-9.GS4

This command boots the specified file from the Flash memory card in PCMCIA slot 1.

rommon 3> boot tftp:gsr-p-mz.112-9.GS4 <ip-address> 

This command boots the specified file from the host TFTP boot server in the network.


Note   If you have not changed the contents of the software configuration register, the factory default setting of 0x0102 in this register causes the system to boot Cisco IOS software from a Flash memory card inserted in PCMCIA slot 0 the next time you boot the router.


After manually booting the router using the boot command, as outlined above, continue with the following steps.

Step 9 As the system boots the Cisco IOS software image, the console displays a system banner and script similar to the following:

Cisco Internetwork Operating System Software
IOS (tm) GS Software (GSR-P-MZ), Released Version 11.2(8)GS
Copyright (c) 1986-1997 by Cisco Systems, Inc.
Compiled Sat 10-May-97 06:02a

Observe the system startup banner. When you first start up an unconfigured system, it automatically enters the setup facility. The setup facility detects the network interfaces installed in the router and prompts you for configuration information for each one.

For example, after the system displays the system banner and hardware configuration, the following system configuration script appears:

         --- System Configuration Dialog ---

At any point you may enter a question mark '?' for help.
Use ctrl-c to abort configuration dialog at any prompt.
Default settings are in square brackets '[]'.

Continue with configuration dialog? [yes/no]:

The system asks you if you want to continue with the configuration dialog. If you answer yes, the system proceeds with the interactive script for the setup facility. If you answer no, the system exits from the setup facility. In this case, you must issue configuration commands at the console terminal to configure the system and network interface parameters.

You need not configure the network interfaces immediately; however, you cannot connect to a network until you configure the interfaces for operation in your networking environment. To do this, refer to the following section entitled "Configuring the Cisco 12008."

Configuring the Cisco 12008

The information in this section applies only if the system does not boot automatically on startup from a specified default Cisco IOS software image.

The Cisco 12008 is administered by means of a command language interpreter called the EXEC. You must boot the router and log in to the system before you can issue commands to the EXEC.

For security purposes in issuing commands, the EXEC has two levels of access:

User EXEC mode—On startup of the Cisco IOS software, the system presents the user EXEC mode prompt:

Router>

Privileged EXEC mode—If you enter an enable secret password (which must first have been saved in memory) at the user EXEC mode prompt, the system changes to the privileged EXEC mode prompt (Router#), as indicated below:

Router> enable
password: xxxxxxxxx
Router# 

For information about using passwords, refer to Step 5 and Step 6 in the section entitled "Configuring Global Parameters."

You can perform a basic configuration for your Cisco 12008 using either of the following methods:

Method 1—Using the setup facility or the setup command.

At initial startup of a completely unconfigured router, the system automatically defaults to the setup facility, which enables you to begin manually configuring your router. The setup facility presents a structured, interactive script that guides you through the process of manually configuring your router.

You can invoke the setup facility at any time by issuing the setup command at the privileged EXEC mode prompt (Router#), thus making available to you the same configuration script that appears automatically at initial startup of an unconfigured router.

You can issue the setup command at any time; the premise for doing so is that you want to alter some previously entered configuration information.

The setup facility is described in the section entitled "Using the Setup Facility or the Setup Command."

Method 2—Using the global configuration mode.

If you prefer not to use the interactive script of the setup facility to configure your router, you can still configure your router manually using the global configuration mode. This facility, which requires you to issue configuration commands on a line-by-line basis at the console without being prompted by a configuration script, is described in the section entitled "Using the Global Configuration Mode."

You can use whichever method suits your operating style and your knowledge of network configuration requirements. The advantage in using the setup facility is that the system guides you through the configuration process through an interactive script that minimizes the likelihood of errors.

To configure the Cisco 12008 to operate in your networking environment, you will need to obtain the correct network addresses from your system administrator or your network plan.

Using the Setup Facility or the Setup Command

You must consider the following types of parameters during the initial manual configuration of your router:

Global (system-wide) parameters

Network interface (line card) parameters

As noted earlier, you can establish the above parameters using the setup facility (as presented to you automatically at initial system startup), or you can issue the setup command at any time at the privileged EXEC prompt (Router#) to activate the setup facility.

The only observable difference between the configuration script displayed when you use the setup facility automatically on startup and that displayed when you issue the setup command is that the latter displays any existing (previously entered) system configuration defaults within square brackets [ ].

For example, during the configuration of a POS interface by means of the setup facility at startup (assuming that the interface has not previously been configured), you will see a display in the following form as you proceed through the script and respond to queries:

Configuring interface POS4/0:
  Is this interface in use?: yes
  Configure IP on this interface?: yes

No default or current parameters are enclosed within square brackets [ ] in the configuration dialog in this instance.

Conversely, when you issue the setup command at the privileged EXEC mode prompt (assuming that the POS interface has been previously configured and you are being queried by the system for changes), you will see a display in the following form:

Configuring interface POS4/0:
  Is this interface in use?[yes]: yes
  Configure IP on this interface?[yes]: yes

The default or current parameters applicable to the interface are enclosed within square brackets [ ].

Proceed to the following sections to configure the global and line card interface parameters for your system.

Configuring Global Parameters

When you first enter the setup facility or issue the setup command, you are queried by the system to configure global parameters for your router.

To boot the system and establish global configuration parameters, perform the following steps:


Step 1 Connect a console terminal to the console port on the RP.

Step 2 Boot the system to display the user EXEC prompt (Router>).

After about 30 seconds, the following display appears on the console, indicating that you have successfully booted the system:

System Bootstrap, Version 11.2(8)GS [biff 571], RELEASED SOFTWARE
Copyright (c) 1994-1997 by Cisco Systems, Inc.

Restricted Rights Legend
 
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

           Cisco Systems, Inc.
           170 West Tasman Drive
           San Jose, California 95134-1706

Cisco Internetwork Operating System Software
IOS (tm) GS Software (GSR-P-MZ), Released Version 11.2(8)GS [biff-
bfr_112]
Copyright (c) 1986-1997 by Cisco Systems, Inc.
Compiled Mon 25-Aug-97 20:13 by biff
Image text-base: 0x60010900, data-base: 0x604FE000

Cisco 12008/GRP (R5000) processor (revision 0x00) with 65536K 
bytes of memory.
Processor board ID 00000000
R5000 processor, Implementation 35, Revision 2.1 (512KB Level 2 
Cache)
Last reset from power-on
1 clock scheduler card(s)
3 switch fabric card(s)
2 four-port OC3 POS controllers (8 POS).
5 OC12 POS controllers (5 POS).
1 Ethernet/IEEE 802.3 interface(s)
13 Packet over Sonet network interface(s)
507K bytes of non-volatile configuration memory.

20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
8192K bytes of Flash internal SIMM (Sector size 256K).
Notice: NVRAM invalid, possibly due to write erase.

Note   The first two sections of the above configuration script (containing the banner screen and the installed hardware listing) appear only at initial system startup. On subsequent uses of the setup command facility, the setup script begins with the following system configuration dialog.


         --- System Configuration Dialog ---

At any point you may enter a question mark '?' for help.
Use ctrl-c to abort configuration dialog at any prompt.
Default settings are in square brackets '[]'.

Continue with configuration dialog? [yes/no]: yes

Enter yes when queried if you want to continue with the configuration dialog.


Note   The examples in this section represent a continuation of the console display for the setup facility or the setup command.


Step 3 Enter yes when asked if you wish to enter the initial configuration dialog and if you wish to see the current interface summary:

Would you like to enter the initial configuration dialog? [yes]: 
yes

First, would you like to see the current interface summary? [yes]: 
yes 

Pressing Return in either case accepts the default response [yes].

The following sample display results from a yes response to the current interface summary query that is entered while you are using the setup facility. The display shows that no interfaces have been configured:

Interface   IP-Address      OK? Method Status                Protocol
Ethernet0   unassigned      YES unset  administratively down down
POS3/0      unassigned      YES unset  administratively down down
POS3/1      unassigned      YES unset  administratively down down
POS3/2      unassigned      YES unset  administratively down down
POS3/3      unassigned      YES unset  administratively down down
ATM4/0      unassigned      YES unset  administratively down down

.
.
.

The following sample display results from a yes response to the current interface summary query that is entered while you are using the setup command. The display shows that some interfaces have already been configured.

Interface   IP-Address      OK? Method Status                Protocol
Ethernet0   3.3.1.1         YES NVRAM  up                    up
POS3/0      2.1.1.1         YES NVRAM  up                    up
POS3/1      2.1.1.2         YES NVRAM  up                    up
POS3/2      2.1.1.3         YES NVRAM  up                    up
POS3/3      2.1.1.4         YES NVRAM  up                    up
ATM4/0      1.1.1.2         YES NVRAM  up                    up

.
.
.

Step 4 Select the protocols that you intend to support for your network interfaces.

For IP-only installations, you can accept the default values for most of the questions.

A typical minimum configuration procedure using IP follows and continues through Step 8:

Configuring global parameters: 

Enter host name [Router]: Router

Step 5 Enter the enable secret password when prompted to do so:

The enable secret is a one-way cryptographic secret used
instead of the enable password when it exists.

Enter enable secret [<Use current secret>]: barney

For future use, make a note of this password.

Step 6 Enter the enable password when prompted to do so:

The enable password is used when there is no enable secret
and when using older software and some boot images.

 Enter enable password: wilma

For future use, make a note of this password also.

The commands available at the user EXEC level are a subset of those available at the privileged EXEC level. Because many privileged EXEC commands are used to establish system parameters, you should password-protect these commands to prevent their unauthorized use.

The enable secret password functionality is available for all Cisco 12000 series Gigabit Switch Routers. You must enter the correct password to gain access to privileged-level commands. When you are running from the ROM monitor (rommon>), the enable password can be used, depending on your boot ROM level.

For maximum security, the enable secret and the enable password should be different. If you use the same password for both the enable secret and enable functions during the setup process, the system accepts it but issues a warning indicating that you should enter a different password.

An enable secret password can contain from 1 to 25 uppercase and lowercase alphanumeric characters; an enable password can contain any number of uppercase and lowercase alphanumeric characters.

In either case, you cannot use a number as the first character. Spaces, however, are valid password characters. For example, "two words" is a valid password. Leading spaces are ignored, but trailing spaces are recognized.

Step 7 Enter the virtual terminal password when prompted to do so:

Enter virtual terminal password: bambam

For future use, make a note of this password.

Step 8 In most cases, you will use IP routing as the network layer protocol. If you specify IP, you must also specify an interior routing protocol.

Enter yes (the default) or press Return to configure IP; do likewise to select the Interior Gateway Routing Protocol (IGRP) as the interior routing protocol. Specify the IGRP autonomous system number, as follows:

 Configure IP? [yes]: yes
    Configure IGRP routing? [yes]: yes
      Your IGRP autonomous system number [1]: 199

Note   For complete information about IP routing and autonomous system numbers, refer to the appropriate software configuration publications listed in the section entitled "If You Need More Configuration Information." The Ethernet interface does not support external routing functions.


Step 9 Enter yes or no to the following query to accept or refuse Simple Network Management Protocol (SNMP) management:

  Configure SNMP Network Management? [yes]:
    Community string [public]:

Note   SNMP is the most widely supported standard for managing networks. SNMP provides a means to access and set configuration and run-time parameters and to monitor and control network elements for routers and communication servers. For more information about SNMP, refer to the appropriate software configuration publications listed in the section entitled "If You Need More Configuration Information."


Step 10 Enter yes or no to the following query to accept or refuse Connectionless Network Service (CLNS) management:

  Configure CLNS? [no]: yes
    CLNS router tag [area_1]:
    CLNS domain [49]:
    CLNS area [0001]:
CLNS station id [0027.25E9.B640]:

Note   CLNS is an Open System Interconnection (OSI) layer service that does not require a circuit to be established before transmitting data. For more complete information about CLNS, refer to the appropriate software configuration publications listed in the section entitled "If You Need More Configuration Information."


On completion of this procedure, you have successfully established the router's global configuration parameters.

Sample Display of Global Parameters

The following sample display lists the global parameters that you entered in Step 3 through Step 10 in the preceding section.

The display indicates the order in which the parameters and their defaults appear on your console terminal.

Configuring global parameters:

Enter host name: Router
Enter enable secret: barney
Enter enable password: wilma
Enter virtual terminal password: bambam
Configure IP?: yes
    Configure IGRP routing?: yes
      Your IGRP autonomous system number [1]: 199
Configure SNMP Network Management?: yes
    Community string [public]:
Configure CLNS? [no]: yes
    CLNS router tag [area_1]:
    CLNS domain [49]:
    CLNS area [0001]:
    CLNS station id [0027.25E9.B640]:

Configuring Network Interfaces

This section presents procedures for configuring the network interfaces for the RP and the installed line cards through use of the setup facility or the setup command. Once configured, the RP and line cards can communicate with external networks.

To configure the interface parameters for the RP and installed line cards, you need the following information:

Interface network addresses

Subnet masks

Protocols to be configured

To obtain this information, consult your network administrator.

For additional interface configuration information for the RP and each of the line cards installed in your Cisco 12008, refer to the configuration note that shipped with each card.


Note   The sample configuration dialog in this section continues the script displayed when you used the setup facility or the setup command in establishing the system's global parameters (see the section entitled "Configuring Global Parameters"). The output shown in this section is only an example; your configuration dialog might be different, depending on how you configure your router.


To configure the Ethernet interfaces on the RP and the network interfaces for the installed line cards, perform the following steps:


Step 1 Configure the RP Ethernet interfaces.

The RJ-45 and MII receptacles on the faceplate of the GRP are IEEE 802.3u- compliant interfaces. The RJ-45 receptacles on the faceplate of the PRP are IEEE 802.3u-compliant interfaces. These IEEE interfaces provide connectivity to Ethernet networks.

In the following example, the system is being configured for an Ethernet interface that will use the IP network layer protocol. (The Ethernet interface does not support external routing functions.)

In the following configuration dialog, respond to the queries according to your own configuration requirements. Use your IP address and subnet mask in responding to the setup prompts.

Configuring interface Ethernet0:
  Is this interface in use?: yes
  Configure IP on this interface?: yes
    IP address for this interface: 3.3.1.1
    Number of bits in subnet field: 8
    Class A network is 3.0.0.0, 8 subnet bits; mask is 255.255.0.0
  Configure CLNS on this interface?: yes

Step 2 Configure the line card interfaces.

The Packet-Over-SONET (POS) line card interfaces enable connections to be made to external OC-3/STM-1 or OC-12/STM-4 networks.

In the following sample configuration dialog for a Quad OC-3c POS line card, respond to the queries according to your configuration requirements. Use your IP address and subnet mask in responding to the setup prompts.

Also, consider Step 3 below, which shows this same Quad OC-3c POS line card interface being configured for IP unnumbered; perform whichever step is appropriate to your configuration requirements.

Configuring interface POS4/0:
  Is this interface in use?: yes
  Configure IP on this interface?: yes
  Configure IP unnumbered on this interface?: no
    IP address for this interface: 2.1.1.1
    Number of bits in subnet field: 0
    Class A network is 2.0.0.0, 0 subnet bits; mask is 255.0.0.0
  Configure CLNS on this interface?: yes

Note   For POS interfaces, the cyclic redundancy check (CRC) is 32-bits by default.



Note   For POS interfaces, the encapsulation protocol is HDLC by default.


For more complete POS interface configuration information, refer to the documents entitled Quad OC-3c/STM-1c Packet-Over-SONET Line Card Installation and Configuration (document number 78-4333-02) and OC-12c/STM-4c Packet-Over-SONET Line Card Installation and Configuration (document number 78-4341-02). These documents accompanied the shipment of your Quad OC-3c/STM-1c and OC-12c/STM-4c POS line cards, respectively.

Step 3 Configure the POS line card interface(s).

In the following sample configuration dialog, a Quad OC-3c POS line card interface is being configured to use IP unnumbered:

Configuring interface POS4/0:
  Is this interface in use?: yes
  Configure IP on this interface?: yes
  Configure IP unnumbered on this interface?: yes
    Assign to which interface: ethernet0
  Configure CLNS on this interface?: yes

Repeat Step 2 or Step 3, as required, to individually configure each port on every Quad OC-3c POS line card installed in your system.

If you have an ATM line card installed in your router, proceed with Step 4; otherwise, skip to Step 5.

Step 4 Configure the ATM line card interface(s).

Asynchronous Transfer Mode (ATM) interfaces enable connections to external OC-12/STM-4 networks.

In the following example, an ATM line card is being configured to use IP. Respond to the configuration dialog, as appropriate for your configuration. Use your address and subnet mask for the setup prompts.

Configuring interface parameters:

Configuring interface ATM1/0:
  Is this interface in use?: yes
  Configure IP on this interface?: yes
    IP address for this interface: 1.1.1.2
    Number of bits in subnet field: 0
    Class A network is 1.0.0.0, 0 subnet bits; mask is 255.0.0.0

Note   You might have to establish additional configuration parameters for the installed ATM line cards if you want to fully utilize them. The new parameters would be used in such activities as the configuring of permanent virtual circuits (PVCs).


For more complete configuration information for ATM line cards, refer to the document entitled OC-12c/STM-4c Asynchronous Transfer Mode Line Card Installation and Configuration (document number 78-4344-02) that accompanied the shipment of your OC-12c/STM-4c ATM line card.

Repeat Step 4 for each installed ATM line card. To display and verify the ATM line card configuration parameters, proceed with Step 5.

Step 5 When you have completed entering the configuration information for all of the installed line cards, the following configuration query is displayed:

Use this configuration? [yes/no]:

At this point, you should visually verify all of the configuration parameters displayed on your console terminal.

Answer yes if you want to save the running configuration file to NVRAM and display the following additional output:

Use this configuration? [yes/no]: yes
[OK]
Use the enabled mode `configure' command to modify this 
configuration.
Press RETURN to get started!

After you press Return, the system reverts to the user EXEC prompt:

Router>

Answer no to the configuration query to return to the privileged EXEC mode prompt (Router#). You must reissue the setup command and enter the appropriate RP and line card configuration information.

On completion of this procedure, you have manually configured the global system parameters and the network interface parameters using the setup facility or the setup command. Your Ethernet, POS, and ATM interfaces are now available for limited use.

If you wish to modify the currently saved configuration information (after you complete the preceding procedure), issue the setup command at the privileged EXEC mode prompt (Router#) at any time.

To perform more complex configuration tasks, you can enter the configure command at the privileged EXEC mode prompt (Router#), which establishes the global configuration mode [Router(config)#]. This mode is described in the section entitled "Using the Global Configuration Mode."

Checking the Software Version Number and the Installed Interfaces

To determine the current version of the Cisco IOS software running on your router, issue the show version command at the user EXEC prompt (Router>).

This command causes the Cisco IOS version number to be displayed, as well as other information, including the hardware installed in the system, the names and sources of system image files, and the contents of the software configuration register.

A typical sample display resulting from the issuance of the show version command follows:

Router>show version
Cisco Internetwork Operating System Software
IOS (tm) GS Software (GSR-P-MZ), Released Version 11.2(8)GS [biff-
bfr_112]
Copyright (c) 1986-1997 by Cisco Systems, Inc.
Compiled Mon 25-Aug-97 20:13 by biff
Image text-base: 0x60010900, data-base: 0x604FE000

ROM: System Bootstrap, Version 11.2(8)GS [biff-bfr_112], RELEASED 
SOFTWARE
BOOTFLASH: GS Software (GSR-BOOT-M), Released Version 11.2(8)GS [biff-
bfr_112 1913]

Router uptime is 20 days, 12 hours, 16 minutes
System restarted by reload
System image file is "biff/gsr-p-mz", booted via tftp from 1.1.1.254

Cisco 12008/GRP (R5000) processor (revision 0x00) with 65536K bytes of 
memory.
Processor board ID 00000000
R5000 processor, Implementation 35, Revision 2.1 (512KB Level 2 Cache)
Last reset from power-on
1 clock scheduler card(s)
3 switch fabric card(s)
1 Single-port OC12c ATM controller (1 ATM).
1 four-port OC3 POS controller (4 POS).
1 Ethernet/IEEE 802.3 interface(s)
1 ATM network interface(s)
4 Packet over Sonet network interface(s)
507K bytes of non-volatile configuration memory.

20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
8192K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x0102

Using the Global Configuration Mode

If you prefer not to use the interactive script of the setup facility, you can manually configure your router using the global configuration mode. The global configuration mode enables you to enter configuration commands on a line-by-line basis from the console terminal.

To configure your router using the configuration mode, perform the following steps:


Step 1 Connect a console terminal to the console port on the faceplate of the RP.

Step 2 When asked if you want to enter the initial dialog, answer no. This causes the router to enter the user EXEC mode. After a few seconds, the user EXEC mode prompt (Router>) appears:

Would you like to enter the initial dialog? [yes]: no
Router>

Step 3 At this prompt, enter the enable command to establish the privileged EXEC mode:

Router> enable
Router#

Note   Configuration changes can be made only in the privileged EXEC mode.


Step 4 At the privileged EXEC mode prompt, enter the config terminal command to enter the global configuration mode:

Router# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#

At the global configuration mode prompt, enter the interface type slot/port command to enter the interface configuration mode:

Router(config)# interface type slot/port
Router(config-if)#

This command accepts either POS or ATM as the type argument.

In either the global configuration mode or the interface configuration mode, you can change the router's configuration parameters.

To exit either mode, type Ctrl-Z.

Step 5 Save your configuration settings, as described in the section entitled "Saving the Running Configuration Settings to NVRAM."

Your router is now minimally configured and able to boot using the currently established configuration information.

To display a list of the configuration commands available to you, enter a question mark (?) at the global configuration mode prompt (Router(config)#) or press the help key.

Verifying the Running Configuration Settings

You may want to verify the running configuration settings or any changes made to the running configuration settings before they are saved. To do so, issue the show running-config command at the privileged EXEC mode prompt.

Typical output from this command is shown in the following sections for the following types of line cards:

Quad OC-3c/STM-1c POS

OC-12c/STM-4c POS

OC-12c/STM-4c ATM

Example of Running Configuration Settings for Quad OC-3 POS Interface

The show running-config command typically displays output in the following form for a Quad OC-3c/STM-1c POS interface installed in slot 7:

Ohm#sh run
Building configuration...
 
Current configuration:
!
version 11.2
no service pad
no service udp-small-servers
no service tcp-small-servers
!
hostname Ohm
!
enable secret 5 $1$W6K5$W/p5Bq6IPLGJ/hS9VVP1g.
enable password lab

interface POS7/0
 ip address 11.1.1.1 255.255.255.0
 crc 32
 clock source internal
!
interface POS7/1
 no ip address
 no ip route-cache cef
 no ip route-cache
 shutdown
 crc 32
!
interface POS7/2
 no ip address
 no ip route-cache cef
 no ip route-cache
 shutdown
 crc 32
!
interface POS7/3
 no ip address
 no ip route-cache cef
 no ip route-cache
 shutdown
 crc 32

Example of Running Configuration Settings for OC-12 POS Interface

The show running-config command typically displays output in the following form for an OC-12 POS interface installed in slot 6:

Turing#sh run
Building configuration...
 
Current configuration:
!
version 11.2
no service pad
no service udp-small-servers
no service tcp-small-servers
!
hostname Turing

-----------!
enable password lab
!
no ip domain-lookup
ip host ray 172.27.136.253
ip host crusty 171.69.209.28
!

!
interface POS6/0
 ip address 12.1.1.1 255.255.255.0
 crc 32   
!         

Example of Running Configuration Settings for OC-12 ATM Interface

The show running-config command typically displays output in the following form for an OC-12 ATM interface installed in slot 6:

Turing#sh run
Building configuration...
 
Current configuration:
!
version 11.2
no service pad
no service udp-small-servers
no service tcp-small-servers
!
hostname Turing

-------------!
enable password lab
!
no ip domain-lookup
ip host ray 172.27.136.253
ip host crusty 171.69.209.28
!

!
interface POS6/0
 ip address 12.1.1.1 255.255.255.0
 crc 32   
!         

Saving the Running Configuration Settings to NVRAM

To save the running configuration settings to NVRAM, enter the following command at the privileged EXEC mode prompt (Router#):

Router# copy running-config startup-config

As an alternative, you can also use the following command to save the running configuration settings:

Router# write memory

Either command saves to NVRAM the configuration settings that you created while in the global configuration mode.

If you fail to take this step, your configuration settings will be lost the next time you reload the system.

Reviewing the Running Configuration Settings

To display the running configuration settings stored in NVRAM, issue the show startup-config command at the privileged EXEC mode prompt. This command displays output in the following form:

Router# show startup-config
Using 1133 out of 520184 bytes
!
version 11.2
no service udp-small-servers
no service tcp-small-servers
!
hostname Router
!
enable password wilma
ip cef distributed switch
ip host biff 3.3.3.254
!
interface Ethernet0
 ip address 3.3.1.1 255.255.0.0
 no ip mroute-cache
!
interface POS3/0
 ip address 2.1.1.1 255.0.0.0
 no keepalive
 crc 16
 no cdp enable
!
interface POS3/1
 ip address 2.1.1.2 255.0.0.0
 no keepalive
 crc 16
 no cdp enable
!
interface POS3/2
 ip address 2.1.1.3 255.0.0.0
 no keepalive
 crc 32
 no cdp enable
!
interface POS3/3
 ip address 2.1.1.4 255.0.0.0
 no keepalive
 crc 32
 no cdp enable
!
interface ATM4/0
 ip address 15.0.0.15 255.0.0.0 secondary
 ip address 1.1.1.2 255.0.0.0
 atm pvc 1 0 64 aal5snap
 atm pvc 2 0 72 aal5mux ip 155000 155000 1
 atm pvc 3 1 90 aal5snap 312000 312000 1
 atm pvc 4 0 108 aal5snap
 atm pvc 10 0 144 aal5mux ip 155000 155000 1
 atm pvc 11 1 91 aal5snap 310000 310000 1
 map-group atm1
!
no ip classless
ip route 2.5.4.254 255.255.255.255 Ethernet0
!
map-list atm1
 ip 1.1.1.1 atm-vc 1
 ip 1.1.1.3 atm-vc 2
 ip 1.1.1.4 atm-vc 4
 ip 15.0.0.1 atm-vc 3
 ip 15.0.0.5 atm-vc 10
 ip 15.0.0.6 atm-vc 11
no logging trap
!
!
line con 0
 exec-timeout 0 0
line aux 0
line vty 0 4
 password bambam
 login
!
end

Performing Other Configuration Tasks

This section presents procedures for performing the following additional configuration tasks:

Configuring the Software Configuration Register

Recovering a Lost Password

Using Flash Memory Cards in the RP

Configuring the Software Configuration Register

The software configuration register is a 16-bit register in NVRAM that you use to define specific system parameters.You can set or change the contents of this register to accomplish the following tasks:

Define boot sources for the default Cisco IOS software, assigning them in the following order of precedence:

Flash memory card inserted in PCMCIA slot 0

TFTP server in the network

Flash memory SIMM (NVRAM) on the RP

Boot image stored within the operating environment, which you access by means of an appropriate form of the boot command issued at the ROM monitor prompt (rommon>)

Define a default boot filename.

Enable or disable the Break function.

Control broadcast addresses.

Set the console terminal baud rate.

Recover a lost password.

Force an automatic boot using a boot image.

When you first power on the router, a boot image called the RP ROM monitor is executed, resulting in the display of the ROM monitor prompt (rommon>). At this prompt, you have access to a limited set of commands that enable you to set values in the software configuration register and to perform a number of other tasks.

The RP ROM monitor is loaded into the RP Flash ROM during board manufacture. You can use it to boot the system from local Flash memory devices; the RP ROM monitor software can be upgraded in the field, if necessary.

Read boot system commands from the configuration file stored in NVRAM.

defines the bits in the software configuration register. The factory default value for the software configuration register is 0x0102. This value is a combination of the following: binary bit 8 = 0x0100 and binary bits 00 through 03 = 0x0002 (see ).


Caution   
To avoid confusion, note that valid software configuration register values may be combinations of settings, rather than the individual settings listed in . For example, the factory default value 0x0102 for the software configuration register is actually a composite of settings in this register.

Table 4-3 Definition of Bits in the Software Configuration Register 

Bit Number
Hexadecimal Value
Meaning/Function

00 through 03

0x0000 to 0x000F

Comprises the boot field for defining the source of a default Cisco IOS software image required to run the router (see ).

06

0x0040

Causes system software to ignore the contents of NVRAM.

07

0x0080

The OEM1 bit is enabled.

08

0x0100

The Break function is disabled.

09

0x0200

Use a secondary bootstrap.

10

0x0400

Internet Protocol (IP) broadcast with all zeros.

11 and 12

0x0800 to 0x1000

Defines the console baud rate (the default setting is 9600 baud).

13

0x2000

Boots the default Flash memory software if the network boot fails.

14

0x4000

IP broadcasts do not have network numbers.

15

0x8000

Enables diagnostic messages and ignores the contents of NVRAM.

1 OEM stands for original equipment manufacturer.



specifies the content of the boot field, which defines a source for booting the default Cisco IOS software image required to run the router. The content of the boot field is specified as a binary number.

Table 4-4 Definition of Bits in Boot Field of Software Configuration Register

Boot Field Bits
Meaning

00

On power up, the system remains at the ROM monitor prompt (rommon>), awaiting a user command to boot the system manually.

01

On power up, the system automatically boots the first system image found in the onboard Flash memory single inline memory module (SIMM) on the RP.

02 to 0F

On power up, the system boots automatically from a default Cisco IOS software image stored on a TFTP server in the network. For this setting, it is assumed that the Ethernet port on the RP is configured and operational. A default Cisco IOS software image is typically kept on a Cisco "Help Desk" server in the network for ready access by anyone needing a boot image. This setting also enables boot system commands that override the default filename.


Boot Field Settings and the Use of the Boot Command

The four low-order bits of the software configuration register (bits 3, 2, 1, and 0) form a boot field that defines the source of a Cisco IOS software image for booting the router.

You can set or change the contents of the boot field by issuing the config-register command at the global configuration mode prompt [Router(config)#].


Note   The factory default setting for the software configuration register (and RP spares) is 0x0102.


When the boot field is set to either 0 or 1 (0-0-0-0 or 0-0-0-1), the system ignores any boot instructions in the system configuration file and one of the following occurs, depending on the boot field setting:

When the boot field is set to 0, you must boot the system manually by issuing the boot command at the ROM monitor prompt (rommon>). You can issue the boot command with or without arguments.

If you issue the boot command without an argument (that is, without specifying a file or any other boot instructions), the system automatically boots using the default image in the Flash memory SIMM on the RP.

If you issue the boot command with arguments (that is, by instructing the system to boot from a specific source), the following options are available to you:

You can instruct the system to boot from a specific Flash SIMM image (by issuing the boot system flash filename command), or you can instruct the system to boot from a specific image stored on a PCMCIA Flash memory card (by issuing the boot <slot #:> <imagename> command).

You can instruct the system to boot from a network TFTP server either by sending broadcast TFTP requests (by issuing a boot system filename command), or by sending a direct request to a specific network TFTP server (by issuing a boot system filename ip-address command).

When the boot field is set to 1, the system automatically boots using the first image found in the onboard Flash SIMM on the RP.

If you set the boot field to any bit pattern other than 0 or 1, the router uses the software configuration register settings to compute a filename from which to boot a default system image stored on a network TFTP server.

To form this filename, the system starts with cisco and links the octal equivalent of the boot field value and the processor type in the following format:

cisco<bootfieldvalue>-<processorname> 

This format, for example, would yield the following range of typical filenames:

cisco2-grp 

.
.
.

cisco17-grp

or

cisco2-prp 

.
.
.

cisco17-prp

The system would use a filename in this range from which to boot a default system image stored on a network TFTP server.

However, if the configuration file contains boot instructions, the system uses these instructions to boot the system, rather than using the filename it computed from the software configuration register settings.


Note   If a bootable Cisco IOS software image exists in a Flash memory card inserted in PCMCIA slot 0 or slot 1, the software configuration register boot field setting is overridden and the system boots from the Cisco IOS software image in the Flash memory card, rather than from a network TFTP image (that is, from a computed filename in the range from cisco2-grp through cisco17-grp).


Changing the Software Configuration Register Settings

To change the software configuration register settings while running system software, perform the following steps:


Step 1 Enter the enable command and your password at the user EXEC mode prompt to establish the privileged EXEC mode:

Router> enable
Password: 
Router#

Step 2 Enter the configure terminal command at the privileged EXEC mode prompt to establish the global configuration mode:

Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# 

Step 3 Set the contents of the software configuration register by entering the config-register value command at the global configuration mode prompt, where value is a hexadecimal number preceded by 0x.

Consult the hexadecimal column in for the possible settings to enter as the 4-bit value parameter.

The config-register value command takes the following form:

Router(config)# config-register 0xvalue

Step 4 Exit the global configuration mode by entering Ctrl-Z:

Router(config)# config-register 0xvalue
Router(config)# Ctrl-Z
Router#

The new contents of the software configuration register are saved to NVRAM. However, these new settings do not take effect until you reload the system or reboot the router.

Step 5 To display the software configuration register setting that is currently in effect as a result of Step 3 (and which will be used at the next reboot of the router), issue the show version command at the privileged EXEC mode prompt:

Router#sh ver

.
.
.

#Configuration register is 0x141 (will be 0x102 at next reload)

The last line of the resulting display shows both the current configuration register setting and the new setting that will take effect when the system is reloaded or rebooted.

Step 6 Save the software configuration register setting, as described in the section entitled "Saving the Running Configuration Settings to NVRAM."

Step 7 Reboot the router.

The software configuration register setting takes effect only after you reload the system, such as when you issue the reload command from the console or reboot the router.

This completes the procedure for changing the contents of the software configuration register. You can set the boot field to enable any desired manual or automatic boot function.

Meaning of Bits in the Software Configuration Register

As described earlier, the four low-order bits in the software configuration register (bits 3, 2, 1, and 0) make up the boot field (see ). This field specifies a number in binary form.

If you set the boot field value to 0, you must boot the system manually by entering the boot command at the ROM monitor prompt (rommon>).

If you set the boot field value to 0x2 through 0xF and a valid boot system command is stored in the configuration file, the system boots the Cisco IOS software image as directed by that value. If no boot system command is present in the configuration file, the system computes a default boot filename for booting from a network TFTP server.

In the following example, the software configuration register has been set to boot the system from the Flash memory SIMM on the RP and to ignore the Break function at the next reboot of the router:

Router# conf term
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# config-register 0x0102
Router(config)# boot system flash [filename]
Ctrl-z
Router# 

With the configuration register thus set to "0x0102," the system computes a default boot filename. In forming this filename, the system starts with cisco and appends the octal equivalent of the boot field number, a hyphen, and the processor type (grp or prp).

Table 4-5 lists the range of possible computed default filenames for booting over the network. Note, however, that a valid boot system configuration command stored in the NVRAM configuration file overrides any computed default filename for booting over the network.

Table 4-5 Default Boot Filenames Computed from Boot Field Bits

Action/File Name
Bit 3
Bit 2
Bit 1
Bit 0

Bootstrap mode

0

0

0

0

Default software

0

0

0

1

cisco2-grp or cisco2-prp

0

0

1

0

cisco3-grp or cisco3-prp

0

0

1

1

cisco4-grp or cisco4-prp

0

1

0

0

cisco5-grp or cisco5-prp

0

1

0

1

cisco6-grp or cisco6-prp

0

1

1

0

cisco7-grp or cisco7-prp

0

1

1

1

cisco10-grp or cisco10-prp

1

0

0

0

cisco11-grp or cisco11-prp

1

0

0

1

cisco12-grp or cisco12-prp

1

0

1

0

cisco13-grp or cisco13-prp

1

0

1

1

cisco14-grp or cisco14-prp

1

1

0

0

cisco15-grp or cisco15-prp

1

1

0

1

cisco16-grp or cisco16-prp

1

1

1

0

cisco17-grp or cisco17-prp

1

1

1

1


The significance of other important bits in the software configuration register is described in the following paragraphs.

Bit 8 of the software configuration register controls the console Break function key. Setting bit 8 (the factory default) causes the system to ignore the console Break key. Conversely, clearing bit 8 causes the system to interpret activation of the Break key as a command, forcing the system into the ROM monitor mode (rommon>) and halting normal system operation. Regardless of the setting of the break enable bit in the software configuration register, activation of the Break key causes a return to the ROM monitor prompt during approximately the first 5 seconds of booting.

Bit 10 of the software configuration register controls the host portion of the IP broadcast address. Setting bit 10 causes the processor to use all zeros in the host portion of the IP broadcast address; clearing bit 10 (the factory default) causes the processor to use all ones. Bit 10 interacts with bit 14, which controls the network and subnet portions of the IP broadcast address.

Table 4-6 shows the combined effect of bits 10 and 14.

Table 4-6 Software Configuration Register Settings for Broadcast Address Destination

Bit 14
Bit 10
Address (net) (host)

Off

Off

(ones) (ones)

Off

On

(zeros) (zeros)

On

On

(net) (zeros)

On

Off

(net) (ones)


Bits 11 and 12 of the software configuration register determine the line (baud) rate of the console terminal. Table 4-7 shows the settings in this register that equate to the four available console baud rates. The factory default transmission rate for the console terminal is 9600 baud.

Table 4-7 Console Baud Rate Settings

Baud Rate
Bit 12
Bit 11

9600

0

0

4800

0

1

1200

1

0

2400

1

1


Bit 13 of the software configuration register determines the system's response to a bootload failure. Setting bit 13 causes the system to load Cisco IOS software from Flash memory after five unsuccessful attempts to load a boot file from the network TFTP server. Clearing bit 13 causes the system to continue attempting to load a boot file from the network TFTP server indefinitely. By default, bit 13 in the software configuration register is set to 0 at the factory prior to router shipment.

summarizes the functions of all of the bits in the software configuration register.

Recovering a Lost Password

This section tells you how to recover a lost password. The following is a general outline of the password recovery process:

1 Issue the show version command to determine the current contents of the software configuration register.

2 Break to the ROM monitor prompt (rommon>).

3 Change the software configuration register setting to 0x0040. This setting causes the system to ignore the contents of NVRAM, enabling you to see your password.

4 Enter the privileged EXEC mode.

5 Enter the show startup-config command to display the enable password.

6 Change the software configuration register value back to its original setting.

To recover a lost password, perform the following steps.


Note   If the enable password is encrypted, the following procedure will not work for password recovery and you will have to reconfigure the system before attempting a reboot. To reconfigure the system, use the displayed configuration, as revealed by issuing the show startup-config command in the privileged EXEC mode (see Step 11).



Step 1 Attach an ASCII terminal to the RP console port.

Step 2 Configure the terminal to operate at 9600 baud, 8 data bits, no parity, and 2 stop bits (or to whatever settings the console port is currently set).

Step 3 Enter the show version command at the privileged EXEC mode prompt to display the current software configuration register setting:

Router#show version

.
.
.

Make a note of this current configuration setting, as displayed in the last line of the show version command output. You may need this value for later use (in Step 13).

Step 4 If the Break function is disabled, power cycle the router by turning off power to the power supply(ies), waiting 5 seconds, and then restoring power.

If the Break function is enabled, press the Break key or send a break signal by holding down the Control key and pressing the right square bracket key (^]).

Step 5 Within 5 seconds of power being restored to the router, press the Break key. This action causes the terminal to display the ROM monitor prompt, as follows:

rommon 1> 

Step 6 Set the software configuration register to ignore the configuration file information, as indicated in the following sample display:

rommon 1> conf reg

	Configuration Summary
enabled are:
console baud: 9600
boot: image specified by the boot system command
or default to: cisco2-grp

do you wish to change the configuration? y/n [n]: y
enable "diagnostic mode"? y/n [n]:
enable "use net in IP bcast address"? y/n [n]:
enable "load rom after netbootfails"? y/n [n]:
enable "use all zero broadcast"? y/n [n]:
enable "break/abort has effect?" y/n [n]:
enable "ignore system config info?" [n]: y
change console baud rate? y/n [n]:
change boot characteristics? y/n [n]

Configuration Summary
enabled are:
console baud: 9600
boot: image specified by the boot system command
or default to: cisco2-grp

do you wish to change the configuration? y/n [n]

You must reset or power cycle for the new config to take effect

Step 7 Initialize the router by entering the initialize command at the ROM monitor prompt:

rommon 1> i

The router power cycles, the software configuration register is set to ignore the configuration file, and the router boots the system image and displays the system configuration dialog:

         --- System Configuration Dialog --- 

.
.
.

Step 8 Enter no in response to the system configuration dialog prompts until the following instruction is displayed:

Press RETURN to get started!

Step 9 Press Return.

After the interface configuration information is displayed, the user EXEC mode prompt appears:

Router>

Step 10 Issue the enable command at the user EXEC mode prompt to enter the privileged EXEC mode:

Router> enable
Router#

Step 11 Enter the show start-up config command at the privileged EXEC mode prompt to display the enable password in the configuration file:

Router# show start-up config

.
.
.

Step 12 Issue the configure terminal command at the privileged EXEC mode prompt to enter the global configuration mode:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#

Step 13 Change the software configuration register setting back to its original value (as noted earlier from Step 3). Alternatively, change this value to 0x0102 (the factory default) by issuing the config-register 0xvalue command:

Router(config)# config-register 0xvalue
Router(config)#

Step 14 Exit the global configuration mode by entering Ctrl-Z:

Router(config)# Ctrl-Z
Router#

Step 15 Reboot the router and enable it using the recovered password.

Using Flash Memory Cards in the RP

This section presents procedures for using Flash memory cards in the Route Processor (RP). The following topics are covered in this section:

Installing and Removing a Flash Memory Card in a RP

Formatting a Flash Memory Card

Specifying a Cisco IOS Image for Booting the System

Console Commands Associated with Flash Memory Use

Enabling Booting from Flash Memory

Copying Files to a Flash Memory Medium

Copying a Cisco IOS Software Image onto a Flash Memory Card

Copying Cisco IOS Software Images between Flash Memory Cards

Copying System Configuration Files between RP Memory and a Flash Memory Card

Recovering from Locked Blocks in Flash Memory Cards

Installing and Removing a Flash Memory Card in a RP

The RP has two PCMCIA slots (see )—slot 0 on the left and slot 1 on the right—that accommodate the Flash memory cards that are used for storing system software images. Both PCMCIA slots can be used simultaneously.

To install a Flash memory card, perform the following steps:


Step 1 Facing the RP faceplate, hold the Flash memory card with the connector end of the card toward the slot and the label facing to the right (see a).

Step 2 Insert the card into the slot until the card is completely seated in the connector at the back of the slot (see Figure 4-3b). The ejector button pops out when the card is seated.


Note   The Flash memory card is keyed for proper insertion. The ejector button will not pop out unless the card is properly inserted. Part of the card remains outside the slot, even when it is properly seated. Do not attempt to force the card deeper into the slot after the ejector button pops out.


To remove a Flash memory card, perform the following steps:


Step 1 To eject the card, press the ejector button to free the card from the connector at the back of the slot (see Figure 4-3c).

Step 2 Remove the card from the slot and place it in an antistatic bag for ESD protection.

Figure 4-3 Installing and Removing a Flash Memory Card

Formatting a Flash Memory Card

The Flash memory card that shipped with your router contains the default Cisco IOS image for booting your router.

In some cases, you might need to insert a new Flash memory card and copy images or backup configuration files to the card. However, before using a new Flash memory card, you must format it.


Note   For the following procedure, it is assumed that you have already booted your router and that it is fully operational. Use only Type 1 or Type 2 Flash memory cards with the PCMCIA slots on the RP.



Caution   
The formatting procedure erases all information on a Flash memory card. If you want to save any data on a Flash memory card, copy the data to a server or another Flash memory card before formatting the card.

To format a new Flash memory card, perform the following steps:


Step 1 Insert the Flash memory card into PCMCIA slot 0 or slot 1.

In this procedure, slot 0 is used.

Step 2 Enter the format slot0: (or format slot1:) command at the privileged EXEC mode prompt:

Router# format slot0:
All sectors will be erased, proceed? [confirm]
Enter volume id (up to 30 characters): MyNewCard
Formatting sector 1
Format device slot0 completed
Router#

Note   In this example, a 20-MB Flash memory card is being used. At the "Formatting sector" line in the sample display above, the system begins to count backward from 160 (the number of sectors on a 20-MB Flash memory card); when the count reaches "1," the formatting process is complete.


The new Flash memory card is now ready for use.

Specifying a Cisco IOS Image for Booting the System

Use the procedure in this section to identify a particular Cisco IOS software image (named new.image) that is to be made bootable from a Flash memory card.

The software configuration register must be set to "0x2102" during this procedure in order for the image to boot from a Flash memory card; accordingly, the config-register command must be included in the command sequence, as shown below:

Router# config terminal
Router(config)# no boot system
Router(config)# boot system flash slot0:new.image
Router(config)# config-register 0x2102
Ctrl-z
Router# copy running-config startup-config
Router# reload

When you issue the reload command, the specified file (new.image) on the Flash memory card inserted in PCMCIA slot 0 is used to boot the system.

If one of the following software configuration register settings were to be specified in the preceding example, the system would behave as described below:

0x2000—The system would boot a default Cisco IOS software image from a Flash memory card (if the network boot fails).

0x0100—The system would ignore the Break function.

0x0101—The system would boot the default image (the first image found) from the onboard Flash memory SIMM on the RP. This setting also tells the system that it should not reset the Break disable function, nor should it check for a default filename for booting over the network.

0x0002—The system would look in the Flash memory SIMM on the RP for a default Cisco IOS software image.

0x0102—The system would check for a default netboot filename, boot from a Flash memory card (if the netboot operation fails), and disable the Break function.

Console Commands Associated with Flash Memory Use

This section outlines the console commands for using the onboard Flash memory SIMM on the RP and the PCMCIA Flash memory cards.

To determine the type of Flash memory medium currently in effect for access, issue the pwd command at the privileged EXEC mode prompt:

Router# pwd
slot0

To change from one type of Flash memory access to another, issue the change directory (cd device-name) command, where device-name can be slot0:, slot1:, or bootflash:.

Sample uses of the change directory command follow:

Router# cd slot1:
Router# pwd
slot1
Router# cd slot0:
Router# pwd
slot0
Router# cd bootflash:
Router# pwd
bootflash
Router# 

To list the directory contents of the Flash memory medium being used, issue the directory (dir [device-name]) command at the privileged EXEC mode prompt, where device-name can be slot0:, slot1:, or bootflash:.

A sample use of the directory command follows:

Router# dir
-#- -length- -----date/time------ name
1   4601977  May 10 1997 09:42:19 myfile1
6   679      May 10 1997 05:43:56 todays-config
7   1        May 10 1997 09:54:53 fun1

To delete a file from a Flash memory medium, issue the delete (delete filename) command at the privileged EXEC mode prompt, where filename represents any Flash memory file.

An example of deleting the file fun1 from the current Flash memory directory follows:

Router# delete fun1
Router# dir
-#- -length- -----date/time------ name
1   4601977  May 10 1997 09:42:19 myfile1
6   679      May 10 1997 05:43:56 todays-config

Files that are deleted from the current Flash memory directory are marked as such, but they still occupy space in the Flash memory directory.

To permanently remove deleted files from a Flash memory directory but leave undeleted files intact, issue the squeeze device-name command at the privileged EXEC mode prompt, where device-name can be slot0:, slot1:, or bootflash:.

The squeeze command permanently removes deleted files and makes all other undeleted files contiguous, thus conserving storage space.

A sample squeeze command follows:

Router# squeeze slot0:
All deleted files will be removed, proceed? [confirm]
Squeeze operation may take a while, proceed? [confirm]
ebESZ

To prevent loss of data due to sudden power loss, the "squeezed" data is temporarily saved to another Flash memory area reserved specifically for system use.

In the preceding command display output, the character "e" in the last line indicates that the special Flash memory area has been erased. This erase operation must be accomplished before any write operation to the special Flash memory area can begin.

The character "b" indicates that the data about to be written to the special Flash memory area has been temporarily copied.

The character "E" signifies that the sector temporarily occupied by the data has been erased.

The character "S" signifies that the data has been written to its permanent location in Flash memory.


Note   During the squeeze operation, the system maintains a log identifying which of the squeeze functions has been accomplished so that the system can return to the proper place and continue the operation in the event of a power failure.


The character "Z" indicates that the log has been erased following the successful squeeze operation.

Enabling Booting from Flash Memory

To enable booting from Flash memory, set the boot field in the software configuration register (bits 3 through 0) to a value between 2 and 15. These values are used with the boot system flash device:filename command, where device can be slot0:, slot1:, or bootflash:, and filename is the name of the file you want the system to boot.

For more detailed information about setting values in the software configuration register, refer to the earlier section entitled "Configuring the Software Configuration Register."

To enter the global configuration mode (while the system is running) and specify a Flash filename from which to boot the system, enter the configure terminal command at the privileged EXEC mode prompt:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# boot system flash device:filename

To disable the Break function and enable the boot system flash device:filename command, issue the config-register command at the global configuration mode with the configuration register value shown below:

Router(config)# config-reg 0x0102
Ctrl-z
Router#

Copying Files to a Flash Memory Medium

It is a good idea to copy a new Cisco IOS software image to a Flash memory medium (1) when a new image becomes available or (2) when you want to back up the image.

The information in this section enables you to copy any type of file to the Flash memory SIMM on the RP or to a PCMCIA Flash memory card inserted in either slot 0 or slot 1.


Caution   
You cannot copy a new Cisco IOS software image into the onboard Flash memory SIMM (also referred to as bootflash) while the system is running from onboard Flash memory.


Note   When you upgrade Cisco IOS software images in Flash memory, do so one at a time; it is not good practice to delete all valid images in Flash memory at once. Also, to avoid losing valid Cisco IOS images, you should upgrade PCMCIA-based Flash memory separately from the onboard Flash SIMM on the RP.


To copy a file to Flash memory, issue the following command at the privileged EXEC mode prompt:

Router# copy tftp:filename [ bootflash: | slot0: | slot1: ]:filename

where:

The argument tftp:filename specifies the source and name of the file to be copied.

The variable [bootflash: | slot0: | slot1: ]:filename specifies the destination and name of the file to be copied. The option bootflash specifies that the file is to be copied to the onboard Flash memory SIMM on the RP; the option slot0: specifies that the file is to be copied to the PCMCIA Flash memory card in slot 0; the option slot 1: specifies that the file is to be copied to the PCMCIA Flash memory card in slot 1.

Typical output generated by a copy tftp:filename command follows:

Router# copy tftp:myfile1 slot0:myfile1
20575008 bytes available on device slot0, proceed? [confirm]
Address or name of remote host [1.1.1.1]?
Loading new.image from 1.1.1.1 (via Ethernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 7799951/15599616 bytes]
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Router#

In this example, the exclamation points (!!!) appear as the source file is being downloaded to the destination device. The "C" characters indicate that a cyclic redundancy check (CRC) is being calculated during the downloading process. The CRC verifies that the file has been correctly downloaded to the destination device (the Flash memory card inserted in PCMCIA slot 0).

Copying a Cisco IOS Software Image onto a Flash Memory Card

You can copy a Cisco IOS software image onto a Flash memory card at any time for later use.

However, you must first format the Flash memory card that you intend to use in the copy operation. If you have not already formatted the card, refer to the earlier section entitled "Formatting a Flash Memory Card."

The following assumptions apply for the Flash memory card copying procedures in this section:

You have a formatted Flash memory card inserted in a PCMCIA slot in the RP.

You know the name of the file you want to copy to the Flash memory card.

You have a valid, bootable Cisco IOS software image stored in the onboard Flash memory SIMM, enabling you to start the router.

The bootable Cisco IOS software image that you want to copy to the Flash memory card in the PCMCIA slot exists on a TFTP server somewhere in the network.

You have access to the network TFTP server by means of a configured and fully functional network interface on your system.

To ensure access to the network TFTP server, you must configure one network interface using the setup command facility.

For instructions on using the TFTP facility, refer to the section entitled "Using the Setup Facility or the Setup Command." You can also refer to the document entitled Configuration Fundamentals Configuration Guide.

To copy a bootable image onto a Flash memory card, perform the following steps:


Step 1 Boot the router and allow it to initialize.

Step 2 Issue the enable command at the user EXEC mode prompt to establish the privileged EXEC mode:

Router> enable
Password:

Router#

Step 3 Copy the file named new.image to the Flash memory card inserted in PCMCIA slot 0 by issuing the following command:

Router# copy tftp:new.image slot0:new.image
20575008 bytes available on device slot0, proceed? [confirm]
Address or name of remote host [1.1.1.1]?
Loading new.image from 1.1.1.1 (via Ethernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 7799951/15599616 bytes]
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCC
Router#

In this example, the exclamation points (!!!) appear as the source file is being downloaded (copied) to the destination device. The "C" characters indicate that a CRC is being calculated during the downloading process. The CRC verifies that the file has been correctly copied to the destination device (the Flash memory card inserted in PCMCIA slot 0).

Step 4 Reboot the system.

This completes the procedure for copying a bootable image onto a Flash memory card.

Copying Cisco IOS Software Images between Flash Memory Cards

As future releases of Cisco IOS software become available, you will receive each image as a file booted from a network TFTP server, as a file on floppy disk, or as a file on a Flash memory card.

The procedures in this section tell you how to use a newly released Cisco IOS software image on a Flash memory card in a system that has (1) an older Cisco IOS image residing on a Flash memory card inserted in PCMCIA slot 0 and (2) a default Cisco IOS software boot image stored in the onboard Flash memory SIMM on the RP.

In this procedure, you will be copying an updated Cisco IOS software image from a new Flash memory card onto a Flash memory card containing an old Cisco IOS software image.

For purposes of this procedure, the following filenames apply:

image.new—The new image on the new Flash memory card.

image.old—The old image on the old Flash memory card inserted in slot 0.

image.boot—The bootable Cisco IOS software image stored in the onboard Flash memory SIMM. (This image is used by default to boot the system if no other bootable image is available.)


Note   In this procedure, it is assumed that the new Cisco IOS software image will fit on the old Flash memory card inserted in slot 0, together with the old image. If sufficient space is not available for both images on the old Flash memory card, use the delete command to delete files from the old Flash memory card; however, do not delete the image.old file. After deleting files, use the squeeze command to permanently remove the deleted files from the old Flash memory card. (For information on the use of the squeeze command, refer to the section entitled "Console Commands Associated with Flash Memory Use." If, after you delete files and use the squeeze command, the two files still cannot coexist on the Flash memory card in slot 0, remove this card, place it in an antistatic bag for ESD protection, and store it in a safe place. Insert the new Flash memory card (containing image.new) in slot 0. Proceed to Step 5 in the following procedure and issue the command boot system flash slot0:image.new to designate the file image.new as the new default Cisco IOS software boot image.


To copy a bootable Cisco IOS software image between Flash memory cards, perform the following steps:


Step 1 Boot the router.

In this procedure, the file named image.boot is the default boot image.

Step 2 Enable the router to bring up the privileged EXEC mode prompt:

Router> enable 
Password:
Router# 

Step 3 Insert the new Flash memory card in PCMCIA slot 1.

Step 4 Issue the following command to copy the file image.new in slot 1 to the Flash memory card inserted in PCMCIA slot 0.


Note   Take this step only if sufficient space is available on the old slot 0 Flash memory card to accommodate the new image (in addition to the old image it already contains).


Router# copy slot1:image.new slot0:image.new

You can also enter this command in the following form to achieve the same result:

Router# copy slot1:image.new slot0:

In the latter case, the name of the file is carried along with the copied image.

Step 5 Issue the following commands to designate the file named image.new (in the Flash memory card in slot 0) as the new default system image for boot purposes:

Router# config t
Router(config)# no boot system
Router(config)# boot system flash slot0:image.new
Ctrl-z
Router# copy running-config startup-config
Router# reload

When the system reloads, the file image.new is booted from the Flash memory card inserted in slot 0.

This completes the procedure for copying a bootable image between Flash memory cards inserted in the PCMCIA slots.

Copying System Configuration Files between RP Memory and a Flash Memory Card

Copying a configuration file to a Flash memory card inserted in PCMCIA slot 0 or slot 1 might be required if you do not have access to a TFTP server on which you can temporarily store a configuration file.

To copy a system configuration file, consult the following sections, as appropriate:

Copying a Configuration File from NVRAM to a Flash Memory Card

Copying a Configuration File from DRAM to a Flash Memory Card

Copying a Configuration File from a Flash Memory Card to NVRAM

Copying a Configuration File from NVRAM to a Flash Memory Card

To copy a configuration file from NVRAM to a Flash memory card, perform the following steps:


Step 1 Issue the show boot command at the privileged EXEC mode prompt to display the current setting for the environmental variable CONFIG_FILE:

Router# show boot

[display text omitted]

CONFIG_FILE variable =
Current CONFIG_FILE variable =

[display text omitted]

The absence of any notation following the CONFIG_FILE variable statement in this sample display indicates that the environmental variable is pointing to NVRAM (the system default).

Step 2 To invoke the copy operation, issue a copy command in the following form at the privileged EXEC mode prompt:

copy startup-config [slot0: | slot1: ]:filename

where:

startup-config is the source of the file to be copied (NVRAM)

[slot0: | slot1: ]:filename is the destination of the file (the Flash memory card in either slot 0 or slot 1) and its name.

To initiate the copy operation at the privileged EXEC mode prompt, issue the following command:

Router# copy startup-config slot0:myfile2
20575008 bytes available on device slot0, proceed? [confirm]
Address or name of remote host [1.1.1.1]?
Loading new.image from 1.1.1.1 (via Ethernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 7799951/15599616 bytes]
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCC
Router#

Note   In this example, the exclamation points (!!!) appear as the file is being copied. The "C" characters signify the calculation of the CRC. The CRC verifies that the file has been copied correctly.


Step 3 To further verify that the configuration file was copied correctly to the Flash memory card inserted in slot 0, issue the directory command:

Router# dir slot0:
-#- -length- -----date/time------ name
1   5200084  May 10 1997 19:24:12 gsr-p-mz.112-8
3   1215     May 10 1997 20:30:52 myfile1
4   6176844  May 10 1997 23:04:10 gsr-p-mz.112-8.1
5   1186     May 10 1997 16:56:50 myfile2

9197156 bytes available (11381148 bytes used)
Router#

Copying a Configuration File from DRAM to a Flash Memory Card

To copy a configuration file from DRAM to a Flash memory card, perform the following steps:


Step 1 Issue the command for copying a configuration file from DRAM to a Flash memory card. The command takes the following form:

copy startup-config [slot0: | slot1: ]:filename

where:

copy startup-config specifies the source file to be copied from DRAM.

[slot0: | slot1: ]:filename specifies the destination of the configuration file to be copied (the Flash memory card inserted in either slot 0 or slot 1) and its name.

To initiate the copy operation, issue the following command at the privileged EXEC mode prompt:

Router# copy running-config slot0:myfile2
20575008 bytes available on device slot0, proceed? [confirm]
Address or name of remote host [1.1.1.1]?
Loading new.image from 1.1.1.1 (via Ethernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 7799951/15599616 
bytes]
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Router#


Note   In this example, the exclamation points (!!!) appear as the file is being copied. The "C" characters signify the calculation of the CRC. The CRC verifies that the file has been copied correctly.


Step 2 To further verify that the file was copied correctly, issue the directory command at the privileged EXEC mode prompt:

Router# dir slot0:
-#- -length- -----date/time------ name
1   5200084  May 10 1997 19:24:12 gsr-p-mz.112-8
3   1215     May 10 1997 20:30:52 myfile1
4   6176844  May 10 1997 23:04:10 gsr-p-mz.112-8.1
5   1186     May 10 1997 16:56:50 myfile2

9197156 bytes available (11381148 bytes used)

Copying a Configuration File from a Flash Memory Card to NVRAM

To copy a configuration file from a Flash memory card inserted in PCMCIA slot 0 or slot 1 to NVRAM, perform the following steps:


Step 1 Issue the command for copying a configuration file from a Flash memory card to NVRAM. This command takes the following form:

copy [ slot0: | slot1: ]:filename startup-config

where:

[ slot0: | slot1: ]:filename is the source of the file to be copied (the Flash memory card inserted in PCMCIA slot 0 or slot 1).

startup-config is the destination (NVRAM) of the file to be copied.

To initiate the copy operation, issue the following command at the privileged EXEC mode prompt:

Router# copy slot0:myfile startup-config 
[ok]
Router#

Step 2 Issue the following command to ensure that the startup configuration file, now stored in NVRAM, is designated as the default running configuration file for the system:

Router# copy startup-config running-config
Router#
%SYS-5-CONFIG_I: Configured from memory by console
Router#

Recovering from Locked Blocks in Flash Memory Cards

A locked block in a Flash memory card occurs when power is lost or a Flash memory card is removed during a write or erase operation. The only way to recover from locked blocks in a Flash memory card is to reformat the card using the format command.


Caution   
Formatting a Flash memory card erases all data on the card.

When a block of Flash memory is locked, it cannot be written to or erased. Any attempt to do so will consistently fail at the blocked location.

What to Do Next?

After you have installed the Cisco 12008, checked all external connections, turned on system power, allowed the system to boot up, and minimally configured the system, you might need to perform additional configuration tasks. For more detailed information about configuring the router and its interfaces, refer to the publications listed in the following section.


Note   For additional information about the Cisco 12000 series line cards, refer to the individual line card configuration note(s) for your installed line cards.


If You Need More Configuration Information

Additional information about Cisco IOS software is available from the following sources:

The Documentation CD-ROM.

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more up to date than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or through an annual subscription.

The section entitled "Obtaining Documentation."

Customer Service at 800 553-6387 or 408 526-7208. Customer Service hours are 5:00 a.m. to 6:00 p.m. Pacific time, Monday through Friday (excluding company holidays). You can also send e-mail to cs-rep@cisco.com.

The Cisco Information Packet that shipped with your router.

For systems with Cisco IOS Release 11.2(8)GS or later, refer to the following modular configuration and command reference publications, as appropriate, for your system configuration:

Configuration Fundamentals Configuration Guide

Configuration Fundamentals Command Reference

Wide-Area Networking Configuration Guide

Wide-Area Networking Command Reference

Network Protocols Configuration Guide, Parts 1, 2, and 3

Network Protocols Command Reference, Parts 1, 2, and 3

Configuration Builder Getting Started Guide

Troubleshooting Internetworking Systems

Debug Command Reference

System Error Messages

Cisco IOS Software Command Summary

Cisco Management Information Base (MIB) User Quick Reference

For additional line card interface configuration information, refer to the following publications:

The configuration note Quad OC-3c/STM-1c Packet-Over-SONET Line Card Installation and Configuration (document number 78-4333-02) that shipped with your Quad OC-3c/STM-1c POS line card

The configuration note OC-12c/STM-4c Packet-Over-SONET Line Card Installation and Configuration (document number 78-4341-02) that shipped with your OC-12c/STM-4c POS line card

The configuration note OC-12c/STM-4c Asynchronous Transfer Mode Line Card Installation and Configuration (document number 78-4344-02) that shipped with your OC-12c/STM-4c ATM line card

For additional information about the GRP, refer to the configuration note Gigabit Route Processor Installation and Configuration (document number 78-4339-02) that shipped with your GRP.

For additional PRP information, refer to the configuration note Performance Route Processor (PRP) Installation and Configuration (Document Number 78-13302-xx) that accompanied your PRP.