|
|
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:
This chapter will help you to
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.
A default Cisco IOS software image for your Cisco 12008 is available through any one of the following internal/external sources:
Before attempting to start up your system, verify that the following conditions exist:
After verifying the above conditions, proceed to the next section to start up your Cisco 12008.
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 Figure 1-6 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 Figure 1-7 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 GRP boot process, observe the two, 4-digit alphanumeric LEDs at the bottom of the GRP faceplate (see Figure 4-1). Table 4-1 shows representative system messages that appear in the GRP LEDs.
| GRP LED Display | Meaning | Source |
|---|---|---|
MROM | 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 | Low memory on the GRP is being tested. | RP rommon |
MEM | The size of main memory on the GRP is being discovered. | RP rommon |
RP | The system is operational and ready to execute basic IOS commands at the ROM monitor prompt (rommon>).
| RP rommon |
RP | A valid Cisco IOS image is running. | RP IOS |
MSTR | The GRP is enabled and recognized as the system master. A valid Cisco IOS image is running. | RP IOS |
Step 4 During the line card boot process, which occurs immediately following that of the GRP, 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).
Table 4-2 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.
| Line Card LED Display | Meaning | Source |
|---|---|---|
MROM | 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 | Low memory on the line card is being tested. | LC rommon |
MEM | The size of main memory on the line card is being discovered. | LC rommon |
ROMI | The ROM image is being loaded into line card memory. | RP IOS |
FABL | The line card is waiting for the loading of the fabric downloader.2 | RP IOS |
FABL | The fabric downloader is being loaded into line card memory. | RP IOS |
FABL | The fabric downloader is being launched. | RP IOS |
FABL | The fabric downloader has been launched and is running. | RP IOS |
IOS | The Cisco IOS software is being downloaded into line card memory. | RP IOS |
IOS | The Cisco IOS software is being launched. | RP IOS |
IOS | The Cisco IOS software is running. | RP IOS |
IOS | The line card is enabled and ready for use. | RP IOS |
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:
 | 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. |
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 GRP by issuing the directory command:
dir bootflash:
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:
dir slot0: | slot1:
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 GRP.
boot slot0:gsr-p-mz.112-9.GS4This command boots the specified file from the Flash memory card in PCMCIA slot 0.
rommon 3> boot slot1:gsr-p-mz.112-9.GS4This 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.
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:
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."
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:
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:
Router#), thus making available to you the same configuration script that appears automatically at initial startup of an unconfigured router.
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.
You must consider the following types of parameters during the initial manual configuration of your router:
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?:yesConfigure 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]:yesConfigure 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.
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 GRP.
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:
Enter yes when queried if you want to continue with the configuration dialog.
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:
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:
Router
Step 5 Enter the enable secret password when prompted to do so:
barney
For future use, make a note of this password.
Step 6 Enter the enable password when prompted to do so:
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:
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:
199
Step 9 Enter yes or no to the following query to accept or refuse Simple Network Management Protocol (SNMP) management:
Step 10 Enter yes or no to the following query to accept or refuse Connectionless Network Service (CLNS) management:
yes
On completion of this procedure, you have successfully established the router's global configuration 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.
Router
barney
wilma
bambam
yes
yes
199
yes
yes
This section presents procedures for configuring the network interfaces for the GRP and the installed line cards through use of the setup facility or the setup command. Once configured, the GRP and line cards can communicate with external networks.
To configure the interface parameters for the GRP and installed line cards, you need the following information:
To obtain this information, consult your network administrator.
For additional interface configuration information for the GRP and each of the line cards installed in your Cisco 12008, refer to the configuration note that shipped with each card.
To configure the Ethernet interfaces on the GRP and the network interfaces for the installed line cards, perform the following steps:
Step 1 Configure the GRP Ethernet interfaces.
The RJ-45 and MII receptacles on the faceplate of the GRP 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.
yes
yes
3.3.1.1
8
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.
yes
yes
no
2.1.1.1
0
yes
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:
yes
yes
yes
ethernet0
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.
yes
yes
1.1.1.2
0
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:
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:
yes
After you press Return, the system reverts to the user EXEC prompt:
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 GRP and line card configuration information.
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."
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
Router>
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 GRP.
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:
no
Step 3 At this prompt, enter the enable command to establish the privileged EXEC mode:
enable
Step 4 At the privileged EXEC mode prompt, enter the config terminal command to enter the global configuration mode:
config terminal
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."
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.
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:
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
!
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
!
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 !
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.
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
This section presents procedures for performing the following additional configuration tasks:
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:
rommon>)
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.
| Caution To avoid confusion, note that valid software configuration register values may be combinations of settings, rather than the individual settings listed in Table 4-3. For example, the factory default value 0x0102 for the software configuration register is actually a composite of settings in this 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 Table 4-4). |
| 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. |
Table 4-4 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.
| 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 GRP. |
| 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 GRP 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. |
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)#].
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:
rommon>). You can issue the boot command with or without arguments.
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
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.
Step 1 Enter the enable command and your password at the user EXEC mode prompt to establish the privileged EXEC mode:
enable
Step 2 Enter the configure terminal command at the privileged EXEC mode prompt to establish the global configuration mode:
conf t
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 Table 4-3 for the possible settings to enter as the 4-bit value parameter.
The config-register value command takes the following form:
config-register 0xvalue
Step 4 Exit the global configuration mode by entering Ctrl-Z:
config-register 0xvalue
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:
sh ver
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.
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 Table 4-4). 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.
Router#conf termEnter configuration commands, one per line. End with CNTL/Z. Router(config)#config-register 0x0102Router(config)#boot system flash[filename]Crtl-zRouter#
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).
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.
| 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 | 0 | 0 | 1 | 0 |
| cisco3-grp | 0 | 0 | 1 | 1 |
| cisco4-grp | 0 | 1 | 0 | 0 |
| cisco5-grp | 0 | 1 | 0 | 1 |
| cisco6-grp | 0 | 1 | 1 | 0 |
| cisco7-grp | 0 | 1 | 1 | 1 |
| cisco10-grp | 1 | 0 | 0 | 0 |
| cisco11-grp | 1 | 0 | 0 | 1 |
| cisco12-grp | 1 | 0 | 1 | 0 |
| cisco13-grp | 1 | 0 | 1 | 1 |
| cisco14-grp | 1 | 1 | 0 | 0 |
| cisco15-grp | 1 | 1 | 0 | 1 |
| cisco16-grp | 1 | 1 | 1 | 0 |
| cisco17-grp | 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.
| 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.
| 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.
Table 4-3 summarizes the functions of all of the bits in the software configuration register.
This section tells you how to recover a lost password. The following is a general outline of the password recovery process:
rommon>).
To recover a lost password, perform the following steps.
Step 1 Attach an ASCII terminal to the GRP 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:
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:
conf reg
y
y
Step 7 Initialize the router by entering the initialize command at the ROM monitor prompt:
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:
Step 8 Enter no in response to the system configuration dialog prompts until the following instruction is displayed:
Step 9 Press Return.
After the interface configuration information is displayed, the user EXEC mode prompt appears:
Step 10 Issue the enable command at the user EXEC mode prompt to enter the privileged EXEC mode:
Step 11 Enter the show start-up config command at the privileged EXEC mode prompt to display the enable password in the configuration file:
Step 12 Issue the configure terminal command at the privileged EXEC mode prompt to enter the global configuration mode:
configure terminal
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:
Step 14 Exit the global configuration mode by entering Ctrl-Z:
Step 15 Reboot the router and enable it using the recovered password.
The GRP has two PCMCIA slots (see Figure 4-3)--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 GRP faceplate, hold the Flash memory card with the connector end of the card toward the slot and the label facing to the right (see Figure 4-3a).
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.
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.
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.
| 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:
format slot0:
MyNewCard
The new Flash memory card is now ready for use.
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 terminalRouter(config)#no boot systemRouter(config)#boot system flash slot0:new.imageRouter(config)#config-register 0x2102Crtl-zRouter#copy running-config startup-configRouter#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:
This section outlines the console commands for using the onboard Flash memory SIMM on the GRP and the PCMCIA Flash memory cards.
Router# pwd
slot0
Sample uses of the change directory command follow:
Router#cd slot1:Router#pwdslot1 Router#cd slot0:Router#pwdslot0 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 fun1Router#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.
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.
The character "Z" indicates that the log has been erased following the successful squeeze operation.
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 terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)#boot system flashdevice: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 0x0102Crtl-zRouter#
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 GRP 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. |
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 GRP; 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).
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:
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:
enable
Router#
Step 3 Copy the file named new.image to the Flash memory card inserted in PCMCIA slot 0 by issuing the following command:
copy tftp:new.image slot0:new.image
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.
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 GRP.
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:
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:
enable
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.
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:
config t
no boot system
boot system flash slot0:image.new
Crtl-z
copy running-config startup-config
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.
To copy a system configuration file, consult the following sections, as appropriate:
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:
show boot
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:
copy startup-config slot0:myfile2
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:
dir slot0:
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#
Step 2 To further verify that the file was copied correctly, issue the directory command at the privileged EXEC mode prompt:
dir slot0:
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:
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:
copy slot0:myfile startup-config
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:
copy startup-config running-config
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.
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.
Additional information about Cisco IOS software is available from the following sources:
|
|