Observing System Startup and Performing a Basic Configuration

• All cards are completely inserted into their card cage slots, and all captive screws are tightened.

• All interface cable connections are secure and use cable strain relief, where provided.

• All the source power cables are fastened securely to the power shelf, and the opposite ends of all power cables are connected to the appropriate power source.

• A terminal device is connected to the console port on the GRP, powered on, and configured for 9600  bps, 8 data bits, no parity, and 2 stop bits (9600, 8N2). You must connect a terminal to the GRP to perform the initial configuration of the router.

• The Flash memory card that shipped with your router is installed in PCMCIA slot 0 of the GRP.

Step 1 Switch on all the circuit breakers that control power to the router's power shelf.

Step 2 Observe the power module LEDs:

• When an AC-input power supply is seated in its bay and is receiving appropriate source AC power, the LED labeled PWR OK should be on and the power supply fan should also be on. The LEDs labeled FAULT, TEMP, and ILIM should be off. This is normal behavior.

• When a DC-input power entry module is seated in its bay and is receiving appropriate source DC power, the LED labeled PWR OK should be on and the power entry module fan should also be on. The LEDs labeled FAULT and TEMP should be off. This is normal behavior.

Step 3 Visually check the two LEDs on the front of each blower module. When the blower module is operating correctly, the green LED labeled OK should be on and the red LED labeled FAIL should be off. Listen for the blowers in the blower modules; you should immediately hear them operating. In a noisy environment, the blowers might be difficult to hear, so you should place your hand in front of the exhaust vents near the top and bottom rear of the chassis to verify that the blowers are operating.

Step 5 Observe the status of the GRP interfaces using the GRP LEDs.

Table 4-2: Line Card Alphanumeric LED Display Sequences

LED Display1	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.2 This display might not be visible, because it occurs for only a brief time.	MBus controller
LMEM TEST	Low memory on the line card is being tested.	Line card ROM monitor
MEM INIT	The size of main memory on the line card is being discovered.	Line card ROM monitor
ROMI GET	The ROM image is being loaded into line card memory.	GRP IOS software
FABL WAIT	The line card is waiting for the fabric downloader to load.3	GRP IOS software
FABL DNLD	The fabric downloader is being loaded into line card memory.	GRP IOS software
FABL STRT	The fabric downloader is being launched.	GRP IOS software
FABL RUN	The fabric downloader has been launched and is running.	GRP IOS software
IOS DNLD	The Cisco IOS software is being downloaded into line card memory.	GRP IOS software
IOS STRT	The Cisco IOS software is being launched.	GRP IOS software
IOS UP	The Cisco IOS software is running.	GRP IOS software
IOS RUN	The line card is enabled and ready for use.	GRP IOS software

1The LED sequence shown in Table 4-2 might occur too quickly for you to view; therefore, this sequence is provided in this tabular form as a baseline for how the line cards should function at startup. 2The version of MBus microcode running on your system might be different. 3The fabric downloader loads the Cisco IOS software image onto the line card.

Step 7 If a Flash memory card containing a valid Cisco IOS software image has been inserted in PCMCIA slot 0 and the software configuration register is set to 0x0102 (the factory default setting), the router automatically boots using this image.

Cisco Internetwork Operating System Software
IOS (tm) GS Software (GSR-P-MZ), Released Version 12.0(8)S
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Mon 25-Oct-99 19:41
.
.
.
 

---

Note The actual system banner you see depends on the image version of the Cisco IOS software that the system is running. Your system banner may be different than what is shown in examples throughout this chapter.

---

         --- System Configuration Dialog ---
 
Continue with configuration dialog? [yes/no]:
 

The router uses the system configuration file to activate network connections to the GRP so that the router can be administered from a remote location, or to activate the line card network interfaces. Once configured, the GRP and line cards can communicate with external networks.

• Method 1---Using the setup facility or the setup command.

Router>
 

Router> enable
password: <password>
Router# 
 

The following example shows a setup session automatically invoked during the first-time startup of the router. During the first-time startup, the system displays the system banner information, then starts the System Configuration Dialog.

Cisco Internetwork Operating System Software
.
.
.
         --- System Configuration Dialog ---
 
Continue with configuration dialog? [yes/no]: Yes
 
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 '[]'.
 
Basic setup only configures enough connectivity
for management of the system, extended setup will ask you
to configure each interface of the system.
 
Would you like to enter basic management setup? [yes/no]: Yes
Configuring global parameters:
 
  Enter host name [Router]: Milo
 
  The enable secret is a password used to protect access to
  privileged EXEC and configuration modes. This password, after
  entered, becomes encrypted in the configuration.
  Enter enable secret [<Use current secret>]: barney
 
  The enable password is used when you do not specify an
  enable secret password, with some older software versions, and
  some boot images.
  Enter enable password: wilma
 
  The virtual terminal password is used to protect
  access to the router over a network interface.
  Enter virtual terminal password: bambam
  Configure SNMP Network Management? [no]:
 
Current interface summary
Interface   IP-Address      OK? Method Status                Protocol
Ethernet0   unassigned      YES unset  administratively down down
POS1/0      unassigned      YES unset  administratively down down
SDCC1/0     unassigned      YES unset  administratively down down
POS2/0      unassigned      YES unset  administratively down down
SDCC1/0     unassigned      YES unset  administratively down down
.
.
.
POS15/0     unassigned      YES unset  administratively down down
SDCC15/0    unassigned      YES unset  administratively down down
 
Enter interface name used to connect to the 
management network from the above interface summary: Ethernet0
 
Configuring interface Ethernet0:
Configure IP on this interface? Yes
  IP address for this interface: 172.16.72.2
  Subnet mask for this interface: 255.0.0.0
Class B network is 172.16.0.0, 8 subnet bits; mask is /24
 
The following configuration command script was created:
 
hostname Milo
enable secret 5 $1$krIg$emfYm/1OwHVspDuS8Gy0K1
enable password wilma
line vty 0 4
password bambam
no snmp server
!
no ip routing
!
interface Ethernet0
no shutdown
ip address 172.16.72.2 255.255.255.0
!
interface POS1/0
shutdown
no ip address
!
interface SDCC1/0
shutdown
no ip address
.
.
.
interface POS15/0
shutdown
no ip address
!
interface SDCC15/0
shutdown
no ip address
!
end
[0] Go to the IOS command prompt without saving this script.
[1] Return back to the setup without saving this config.
[2] Save this configuration to nvram and exit.
 
Enter your selection [2]:
 
Building configuration ...
 
Use the enabled mode `configure' command to modify this configuration.
 
Milo#
 
 

As explained earlier, you can set configuration parameters using the setup command facility (as presented to you automatically at initial system startup), or you can enter the setup command at any time at the privileged EXEC prompt to activate the setup facility.

The only observable difference between the configuration script displayed when the setup facility starts automatically on startup and the script displayed when you enter 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 using the setup facility at startup (assuming that the interface has not been configured previously), you will see a display in the following form as you proceed through the script and respond to queries:

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

In this example, the script does not display default or current conditions in square brackets [ ], because you entered the setup facility automatically at startup and there is no prior configuration information.

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

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

In this example, the script displays the default or current conditions of the interface in square brackets [ ], because you invoked the setup facility using the setup command and there is previous configuration information. When a system prompt contains an existing default value in square brackets, press Return to accept the default value, or type an alternate value and press Return.

• Host name for the router

• Passwords for the enable secret, enable, and virtual terminal security parameters

• Protocols used by the router

Host Name

The name you assign the router must follow the rules for ARPANET host names. It must start with a letter, end with a letter or digit, and have as interior characters only letters, digits, and hyphens. The name must consist of 63 or fewer characters. For more information, refer to RFC 1035, Domain Names---Implementation and Specifications.

Also, do not expect case to be preserved. Upper- and lowercase characters look the same to many internet software applications (often under the assumption that the application is doing you a favor). It may seem appropriate to capitalize a name the same way you might do in English, but conventions dictate that computer names appear all lowercase. For more information, refer to RFC 1178, Choosing a Name for Your Computer.

Passwords

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 set system parameters, you should password-protect these commands to prevent their unauthorized use. For information on how to establish password protection or configure privilege levels, refer to the "Configuring Passwords and Privileges" chapter in the Security Configuration Guide, which is one of the modular configuration publications in the Cisco IOS software configuration documentation set that corresponds to the Cisco IOS software release installed on your Cisco hardware.

The enable secret password functionality is available for 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, you can use the enable password, 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.

Make a note of all passwords you set, and store that information in a secure location for future reference.

Protocols

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 router, refer to the configuration note that shipped with each card.

GRP Ethernet Interfaces

The following configuration dialog example shows the system being configured for an Ethernet interface that will use the IP network layer protocol. (The Ethernet interface does not support external routing functions.) The IP address and subnet mask value are examples. The IP address and subnet mask value would be different.

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

Line Card Interfaces

Because of the wide variety of line cards supported by the GSR, you should refer to the configuration note that shipped with a particular card for interface configuration information. This section provides several brief examples to show the general way the setup facility handles line card interface configuration.

Configuring interface POS3/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

The following sample shows the same Quad OC-3c POS line card interface being configured for IP unnumbered.

Configuring interface POS3/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
 

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

If you want to modify the currently saved configuration information, you can enter the setup command at the privileged EXEC mode prompt (Milo#) at any time to start another System Configuration Dialog session.

Milo# show version
Cisco Internetwork Operating System Software
IOS (tm) GS Software (GSR-P-M), Version 12.0(n)S ...
Copyright (c) 1986-1999 by cisco Systems, Inc.
.
.
.
Milo uptime is 1 week, 5 days, 19 hours, 33 minutes
System returned to ROM by reload
System image file is ...
 
cisco 12016/GRP (R5000) processor (revision 0x00) with 262144K bytes 
   of memory.
R5000 CPU at 200 MHz, Implementation 35, Revision 2.1, 512KB L2 Cache
Last reset from power-on
 
1 Route Processor Card
2 Clock Scheduler Cards
.
.
.
5 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).
20480K bytes of Flash PCMCIA card at slot 1(Sector size 128K).
8192K bytes of Flash internal SIMM (Sector size 256K).
 
Milo#

To configure your router using global configuration mode, follow these steps:

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

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

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

Milo> enable
 

Depending on the system and the software version, you may be prompted for a password. The prompt will change to the privileged EXEC prompt as follows:

Milo#

---

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

---

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

In privileged EXEC mode, you can enter most of the configuration commands needed to change the system configuration. Press Ctrl-z to exit this configuration mode.

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

In interface configuration mode, you can enter the interface configuration commands to change the system configuration. Press Ctrl-z to exit interface configuration mode.

To display a list of the configuration commands available to you, enter a question mark (?) at the prompt or press the designated help key on the terminal keyboard while in configuration mode.

router# show running-config
Building configuration...
 
Current configuration:
!
version 12.0
no service pad
no service udp-small-servers
no service tcp-small-servers
!
hostname Milo
!
enable secret 5 $1$W6K5$W/p5Bq6IPLGJ/hS9VVP1g.
enable password twink
 
interface POS1/0
 ip address 10.1.1.1 255.255.255.0
 crc 32
 clock source internal
!
interface POS1/1
 no ip address
 no ip route-cache cef
 no ip route-cache
 shutdown
 crc 32
!
interface POS1/2
 no ip address
 no ip route-cache cef
 no ip route-cache
 shutdown
 crc 32
!
interface POS1/3
 no ip address
 no ip route-cache cef
 no ip route-cache
 shutdown
 crc 32

Milo# copy running-config startup-config
 

You can also use the following command to save the running configuration settings:

Milo# show startup-config
Using 5560 out of 520184 bytes
!
version 12.0
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname Milo
!
enable secret 5 $1$/5HX$OOvyhG2JYhNaCbPa45Wmn/
enable password wilma
ip cef distributed switch
ip host biff 10.3.3.254
!
interface Ethernet0
 ip address 10.3.1.1 255.255.0.0
 no ip mroute-cache
!
interface POS1/0
 ip address 10.1.1.1 255.0.0.0
 no keepalive
 crc 16
 no cdp enable
.
.
.
interface ATM3/0
 ip address 10.0.0.15 255.0.0.0 secondary
 ip address 10.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 10.5.4.254 255.255.255.255 Ethernet0
!
map-list atm1
 ip 10.1.1.1 atm-vc 1
 ip 10.1.1.3 atm-vc 2
 ip 10.1.1.4 atm-vc 4
 ip 10.0.0.1 atm-vc 3
 ip 10.0.0.5 atm-vc 10
 ip 10.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
Milo# 

• 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 on the network

  • Flash memory SIMM (NVRAM) on the GRP

  • Boot image stored within the operating environment, which you access by using an appropriate form of the boot command entered 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 GRP 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 GRP ROM monitor is loaded into the GRP Flash ROM when the GRP is manufactured. You can use it to boot the system from local Flash memory devices. The GRP ROM monitor software can be upgraded in the field, if necessary.

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

When the boot field is set to either 0 or 1 (0000 or 0001), 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 1, the system automatically boots using the first image found in the onboard Flash SIMM on the GRP.

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 the filename of a default system image stored on a network TFTP server. It uses that system image to boot the router.

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>
 

For example, the filename formation process would yield a range of typical filenames like the following:

cisco2-grp 
 
.
.
.
 
cisco17-grp
 

The system would use one of the filenames in this range to use in booting 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.

Milo> enable
Password: <password>
Milo#
 

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

Milo(config)# config-register 0xvalue
 

Milo# show version
 
.
.
.
 
Configuration register is 0x141 (will be 0x102 at next reload)
 

Step 7 Reboot the system.

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

Milo# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Milo(config)# config-register 0x0102
Milo(config)# boot system flash filename
Ctrl-Z
Milo# 
 

With the configuration register 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: Default Boot Filenames

Action/Filename	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 9 is not used.

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.

Milo# show version
 
.
.
.
 

rommon 1> 
 

rommon 1> config-register
 
	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
rommon 1>
 

rommon 1> initialize
 

The router goes through a power cycle. The software configuration register is set to ignore the configuration file. 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 some interface configuration information is displayed, the user EXEC mode prompt appears:

Milo>
 

Milo> enable
Password: <password>
Milo# 
 

---

Note The prompt changes from Milo> to Milo# to indicate the change in command mode.

---

Milo# show startup-config
 
.
.
.
 

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

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

Value is a hexadecimal number preceded by 0x, as in the following example:

Milo(config)# config-register 0x0102
 

Step 14 Exit global configuration mode by entering Ctrl-Z.

Milo(config)# Ctrl-Z
Milo#
 

Caution The following formatting procedure assumes you have already booted your router. The procedure erases all information on a Flash memory card. To prevent the loss of important data that might be stored on a Flash memory card, proceed carefully. If you want to save the data on a Flash memory card, copy the data to a server before you format the card.

To format a new Flash memory card, follow these steps:

Step 1 Insert the Flash memory card into slot 0 or slot 1. (This example uses slot 0.)

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

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

When you enter 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 accordingly:

• 0x2000---If the network boot fails, the system boots a default Cisco IOS software image from a Flash memory card.

• 0x0100---The system ignores the Break function.

• 0x0101---The system boots the default image (the first image found) from the onboard Flash memory SIMM on the GRP. 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 looks in the Flash memory SIMM on the GRP for a default Cisco IOS software image.

• 0x0102---The system disables the Break function and checks for a default TFTP server filename. If the network boot operation fails, the system boots from a Flash memory card.

Milo# pwd
slot0:
Milo#
 

In this example, the present working device you are accessing is on a PCMCIA Flash memory card inserted in slot 0 of the GRP.

Sample uses of the change dir command include:

Milo# cd slot1:
Milo# pwd
slot1:/
Milo# cd slot0:
Milo# pwd
slot0:/
Milo# cd bootflash:
Milo# pwd
bootflash:/
Milo# 
 

A sample use of the dir command follows:

Milo# dir
Directory of slot0:/
 
  1  -rw-     122015   Sep 30 1999 15:03:55 myfile1
  2  -rw-    2054979   Sep 30 1999 15:17:33 gsr-diag-mz.RELEASE28
  3  -rw-    6670560   Sep 30 1999 15:22:49 gsr-p-mz.p7
  4  -rw-       5560   Oct 08 1999 16:54:53 fun1
 
20578304 bytes total (9661756 bytes free)
Milo#

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

Milo# delete slot0:fun1
Milo# dir
Directory of slot0:/
 
  1  -rw-     122015   Sep 30 1999 15:03:55 myfile1
  2  -rw-    2054979   Sep 30 1999 15:17:33 gsr-diag-mz.RELEASE28
  3  -rw-    6670560   Sep 30 1999 15:22:49 gsr-p-mz.p7
 
20578304 bytes total (9661756 bytes free)
Milo#
 

Files that are deleted from the current Flash memory directory are removed from the directory list, but are not erased (they still occupy space in Flash memory). This feature allows you to recover a deleted file later using the undelete command.

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

An example of the squeeze command follows:

Milo# squeeze slot0:
All deleted files will be removed, Continue? [confirm]y
Squeeze operation may take a while, Continue? [confirm]y
Squeeze of slot0 complete
Milo# 
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" indicates that the sector temporarily occupied by the data has been erased.

The character "S" indicates 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.

Milo(config)# config-reg 0x0102
Ctrl-Z
Milo#

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, enter the following command at the privileged EXEC mode prompt:

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

where

tftp:filename

Specifies the source and name of the file to be copied.

[bootflash: | slot0: | slot1:] filename

Specifies the destination Flash medium and name for the new file. The destination Flash medium can be one of the following: bootflash:---Specifies that the file is to be copied to the onboard Flash memory SIMM on the GRP. slot0:---Specifies that the file is to be copied to the PCMCIA Flash memory card in slot 0. 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:

Milo# 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
Milo#
 

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

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 an older Cisco IOS image residing on a Flash memory card inserted in PCMCIA slot 0 and a default Cisco IOS software boot image stored in the onboard Flash memory SIMM on the GRP.

In this procedure, you will copy an updated Cisco IOS software image from a new Flash memory card onto a Flash memory card containing an old Cisco IOS software image. In this example, the following filenames apply:

• image.new---The new image on the new Flash memory.

• image.old---The old image on the old Flash memory card inserted in PCMCIA 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.)

To copy a bootable Cisco IOS software image between Flash memory cards, follow these steps:

Step 1 Boot the router.

For this example, the file named image.boot is the default boot image.

Step 2 Enter the enable command to enter privileged EXEC mode as follows:

Milo> enable
Password: <password>
Milo# 
 

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

---

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

---

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

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

Milo# copy slot1:image.new slot0:
 

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

Milo# configure terminal
Milo(config)# no boot system
Milo(config)# boot system flash slot0:image.new
Ctrl-Z
Milo# copy running-config startup-config
Milo# reload
 

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

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

Use the procedures in the following sections to first copy the configuration file from either NVRAM or DRAM to a Flash memory card, and then to copy the configuration file from a Flash memory card back to NVRAM.

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

To copy a configuration file named myfile2 from the NVRAM on the GRP to a Flash memory card in slot 0, follow these steps:

Step 1 Enter the show bootvar command at the privileged EXEC mode prompt to display the current setting for the environmental variable CONFIG_FILE, as follows:

Milo# show bootvar
.
.
.
CONFIG_FILE variable =
Current CONFIG_FILE variable =
.
.
.
Milo#
 

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 begin the copy operation, enter a copy command in the following form at the privileged EXEC mode prompt:

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

where

startup-config	Specifies the source of the file to be copied (NVRAM).
[slot0: | slot1:]filename	Specifies the destination of the file (the Flash memory card in either slot 0 or slot 1) and the name of the new file.

An example of the copy startup-config slot0:filename command follows:

Milo# 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
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Milo#

To copy the running configuration file from DRAM to a Flash memory card, follow these steps:

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

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

where

running-config	Specifies the source of the 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 the name of the new file.

An example of the copy running-config slot0:filename command follows:

Milo# 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]
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Milo#
 

---

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

---

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

Milo# 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)
Milo#
 

This completes the procedure for copying a running configuration file from the DRAM on the GRP to a Flash memory card.

Step 1 Enter 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	Specifies the source of the configuration file to be copied (the Flash memory card inserted in either PCMCIA slot 0 or slot 1) and the name of the new file.
startup-config	Specifies the destination (NVRAM) of the file to be copied.

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

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

Step 2 Use 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:

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

• Cisco Documentation CD-ROM package

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 as an annual subscription.

• For Cisco IOS software configuration information and support, refer to the modular configuration and modular command reference publications in the Cisco IOS software configuration documentation set that corresponds to the Cisco IOS software release installed on your Cisco hardware. You can also refer to the Cisco IOS software release notes for the version of Cisco IOS software you are using on your router.