|
|
Product Numbers: MEM-I/O-FLD32M=, MEM-I/O-FLD48M=, MEM-I/O-FLD128M=, MEM-RSP-FLD48M=, MEM-RSP-FLD128M=, MEM-7100-FLD48M=, MEM-7100-FLD128M=
This configuration note is a standalone publication that provides instructions for installing, removing, and using Flash Disks in Cisco products that have PC Card slots--formerly called Personal Computer Memory Card International Association (PCMCIA) slots. (For a list of Cisco products that support the Flash Disk--and how they support it--see the "Hardware Requirements" section. For Cisco IOS software requirements, see the "Software Requirements" section.)
Flash Disks provide from 32 to 128 megabytes (MB) of storage space for your configuration files, Cisco IOS software images, and so forth. (For a more complete discussion of Flash Disk features, see the "Product Description" section.)
This configuration note includes the following sections:
Your system and the Cisco IOS software running on it contain extensive features and functionality. For information on Cisco IOS software and for general installation and maintenance information for your system, use the following resources:
 |
Note You can access Cisco IOS software documentation and hardware installation and maintenance documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com. If you are reading Cisco documentation on the World Wide Web, you can submit comments electronically. Click Feedback on the toolbar and then select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments. |
This section describes installation prerequisites you should observe before you can use the Flash Disk in your system, and includes the following subsections:
The Flash Disk provides file storage for the Cisco products listed in the section "Hardware Requirements" if these systems are running Cisco IOS Release 12.0(2) or a later release of 12.0. The RSP8 requires Cisco IOS Release 12.0(9)S or a later release of 12.0.
Using the Flash Disk requires that you upgrade the rxboot image to Cisco IOS Release 12.0(2) or a later release of 12.0. (For additional information regarding rxboot image requirements, see the "Compatibility Requirements" section.)
|
Note The Flash Disk is supported as the primary boot medium for RSP4-, RSP8-, and NPE-300-based systems only. In all other systems, you should use the Flash Disk side by side with linear Flash memory. Although it is possible to boot from a Flash Disk, you must maintain a bootable image on a linear Flash memory card to ensure that your system is bootable if the boot flash memory software image becomes corrupted. |
You can use the Flash Disk for file storage in the PC Card slots of the following Cisco products:
|
Note The 48 MB and 128 MB Flash Disk are not supported with the NPE-100, NPE-150, or NPE-200 in a Cisco 7200 series system router or Cisco uBR7200 series universal broadband router. |
For convenience throughout this publication, the input/output controller (I/O controller),
Route Switch Module (RSM), Network Processing Engine (NPE), the RSP4, and the RSP8 are referred to as the system processor. Specific differences are clearly noted.
You need some or all of the following tools and parts to install a Flash Disk:
|
Note For RSP4 boot ROM upgrade requirements, see the Important Note on page 5. For a discussion of Flash Disk compatibility issues that you must consider, see the "Compatibility Requirements" section following. For specific tools and parts requirements for the RSP4 boot ROM upgrade, see the "Upgrading the ROM Monitor Software Image on the RSP4" section. |
This section discusses Flash Disk compatibility and use between supported systems.
|
Note Flash Disks are not supported by the Route Processors (RPs) used in earlier Cisco 7000 series systems. Use of the Flash Disk in these earlier Cisco 7000 series systems requires that the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI) be installed. The Flash Disk is supported as the primary boot medium for RSP4-, RSP8-, and NPE-300-based systems only. In all other systems, you should use the Flash Disk side by side with a linear Flash memory card. Although it is possible to boot from a Flash Disk, you must maintain a bootable image on a linear Flash memory card to ensure that your system is bootable if the boot flash memory software image becomes corrupted. |
The format command places a processor-specific library on the Flash Disk so that the ROM monitor software can read the Flash memory media; therefore, if you want to use the boot or dir commands at the ROM monitor prompt (rommon>), then you might need to reformat your Flash Disk if it was not already formatted on a like system processor.
|
Note Reformatting is required only if you plan to enter boot and dir commands at the ROM monitor prompt (rommon>) on the RSP4, or RSP8. The Cisco IOS software can otherwise read and use Flash Disks formatted on any system processor, in any system processor listed in the "Hardware Requirements" section. |
To ensure Flash Disk compatibility between systems, should you need to enter the boot or dir commands at the RSP4, or RSP8 ROM monitor prompt (rommon>), we strongly recommend that you observe the following requirements:
The read-only memory (ROM) monitor image on your system performs important functions and as its name implies, is run from ROM. This image gains control at reset or power on, or after a nonrecoverable event (such as a bus error). The ROM monitor software image has a rudimentary user interface that is recognizable by way of the ROM monitor prompt (rommon>). The ROM monitor software image has console drivers and trap handlers for parity and bus errors; however, the ROM monitor does not have any network interface code and it cannot boot an image over the network.
|
Note The ROM monitor is only able to load an image from boot flash memory, linear Flash memory cards, or a Flash Disk (in RSP4-, RSP8-, and NPE-300-based systems only). |
By default, and as a result of a reset or power on, the ROM monitor loads the rxboot image from boot flash memory. If the ROM monitor cannot find a bootable image in boot flash memory, it searches the PC Card-based devices (such as linear Flash memory cards or Flash Disks) for the first bootable image. Normally, this would be the boot image (such as rsp-boot-mz or c7200-boot-mz).
The boot image, when loaded, looks in the boot environment variables--stored in nonvolatile random-access memory (NVRAM)--to determine the location of the Cisco IOS software image and the configuration to use.
The operation of the boot environment variables is described in the "Boot Environment Variables" section, which follows.
The contents of the boot environment variables, which are stored in the configuration file in NVRAM, determine the actions your system takes on bootup. To see the current settings of these variables, use the show boot command as follows:
System> show boot BOOT variable = CONFIG_FILE variable = Current CONFIG_FILE variable = BOOTLDR variable does not exist Configuration register is 0x100
|
Note The show boot command in Cisco IOS Release 12.0. and above is show bootvar. |
Following are explanations for each of these boot environment variables:
System# configure terminal Enter configuration commands, one per line. End with CTRL-Z. System(config)# boot system disk0:rsp-p-mz.12-0
System# configure terminal Enter configuration commands, one per line. End with CTRL-Z. System(config)# boot system config disk0:configfile
System# configure terminal Enter configuration commands, one per line. End with CTRL-Z. System(config)# boot bootldr bootflash:rsp-boot-mz
System# configure terminal Enter configuration commands, one per line. End with CTRL-Z. System(config)# config-register 0x102
This section applies to the following users:
All RSP4 users must upgrade all of the following software images to be able to boot from the Flash Disk:
For all RSP4 users, the following preconditions are assumed:
We strongly recommend that you use the following upgrade process with a new unformatted Flash Disk.
|
Note If you have an RSP4, follow Step 1 through Step 8. If you have any system other than an RSP4- or NPE-300-based system, follow Step 2 through Step 8. |
|
Note A boot ROM upgrade is only required for RSP4-based systems. |
Step 2 Format your onboard Flash memory--called boot flash memory. (See the format command description in Table 2 on page 17.)
Step 3 Upgrade your onboard Flash memory by copying the Release 12.0 rxboot image (such as rsp-boot-mz or c7200-boot-mz) into onboard Flash memory. (See the "copy Command" section.)
Step 4 Copy the Release 12.0 software image from onboard Flash memory to the linear Flash memory card in your system processor's PC Card slot. (See the "copy Command" section.)
Step 5 Change the boot variables in your configuration file to point to the new Cisco IOS image in your linear Flash memory card. (See the preceding section, "Boot Environment Variables," and the "Making a Flash Disk-Based Software Image the Bootable Software Image" section.)
Step 6 Reboot your system to load the Release 12.0 software image from the linear Flash memory card in your system processor.
Step 7 Insert a Flash Disk. (See the "Installing a Flash Disk" section.)
Step 8 With your system running Cisco IOS Release 12.0(2), format the blank Flash Disk. (See the format command description in Table 2 on page 17, and the "format Command" section.)
You should now be able to store configuration files and Cisco IOS software images on your Flash Disk.
If you have an RSP4- or NPE-300-based system, you should now be able to boot from any Cisco IOS software images you store on your Flash Disk.
|
Note To boot from Cisco IOS software images stored on a Flash Disk in an RSP4-, RSP8-, or NPE-300 based system, you must first copy the appropriate Cisco IOS software image to the Flash Disk. (See the "copy Command" section, the "Enabling Booting from a Flash Disk" section, and the "Making a Flash Disk-Based Software Image the Bootable Software Image" section.) |
Following are safety guidelines that you should follow when working with any equipment that connects to electrical power, or which might be sensitive to electrostatic discharge (ESD) damage.
Follow these basic guidelines when working with any electrical equipment:
Electrostatic discharge (ESD) damage, which can occur when electronic cards or components are improperly handled, results in complete or intermittent failures.
Use the following guidelines for preventing ESD damage:
 |
Warning For safety, periodically check the resistance value of the antistatic strap. The measurement should be between 1 and 10 megaohms (Mohms). |
Flash Disks are Flash memory-based devices that conform to the PC Card (formerly PCMCIA) standard, and which present an ATA (AT Attachment) interface to the system. This interface complies with the ANSI ATA Interface Document X3T13.1153 D Rev. 9 specification.
The Flash Disk is more flexible than linear Flash memory because the Flash Disk has controller circuitry which allows it to emulate a hard disk and which automatically maps out bad blocks and performs automatic block erasure. Further, the Flash Disk provides the capability to allocate noncontiguous sectors, which eliminates the need for the squeeze command (previously required with linear Flash memory cards).
The Flash Disk provides increased Flash-based memory space--32 to 128 MB--for storage of system configuration files, Cisco IOS software images, and other types of system-related files. The Flash Disk Table 1 provides memory information for the Flash Disk.
| Memory Size | Product Number |
|---|---|
32 MB | MEM-I/O-FLD32M1 |
48 MB | MEM-I/O-FLD48M1 |
128 MB | MEM-I/O-FLD128M1 |
| 1These products are also available as Flash Disk upgrades. To order an upgrade, add an equal sign (=) after the Product Number, for example, MEM-I/O-FLD128M= |
The Cisco IOS File System feature provides a single interface to all file systems your system uses:
|
Note A complete discussion of the Cisco IOS File System feature is beyond the scope of this publication. For information about this feature, refer to the Configuration Fundamentals Configuration Guide and Configuration Fundamentals Command Reference publications for Cisco IOS Release 12.0. These publications are available on the Documentation CD-ROM and through Cisco Connection Online (CCO). (To obtain the Documentation CD-ROM, see the "Documentation CD-ROM" section. To access CCO, see the "Cisco Connection Online" section.) |
The Flash Disk is a Type-II PC Card device. This means that you can install up to two Flash Disks in system processors with two PC Card slots; there are no PC Card slot-height restrictions related to the Flash Disk. Further, the PC Card slots in which you install the Flash Disk are either vertically oriented or horizontally oriented, depending on the system you are using and the system processor installed in it; therefore, this section provides the following two Flash Disk installation procedures:
Determine how your system is oriented, and then use the appropriate procedure.
Use the show version command to verify that a Flash Disk-compatible version of Cisco IOS software is running on your system:
System> show version Cisco Internetwork Operating System Software IOS (tm) 7200 Software (C7200-J-M), Released Version 12.0(2) Copyright (c) 1986-1998 by cisco Systems, Inc. (Additional displayed text omitted from this example.)
The procedure in this section is for inserting and ejecting a Flash Disk in systems in which the PC Card slots are vertically oriented. The procedure is generic and can be used for a Flash Disk in either PC Card slot position (slot 0 or slot 1). You do not need to turn off system power for this procedure.
Use the following procedure to install and eject a Flash Disk in systems with horizontally oriented PC Card slots:
Hold the Flash Disk with its connector end toward the PC Card slot and its front label facing to the right.
The Flash Disk is keyed and cannot be seated the wrong way. The ejector button does not pop out if the Flash Disk is not completely inserted.
Step 2 Insert the Flash Disk into the PC Card slot until the Flash Disk completely seats in the connector at the rear of the slot and the ejector button pops out toward you.
(See b.)
The Flash Disk does not insert all the way inside the PC Card slot. A portion of the Flash Disk remains outside the slot. Do not attempt to force the Flash Disk past this point.
Step 3 To eject a Flash Disk, press the ejector button--located below the slot--until the Flash Disk is free of the connector at the rear of the PC Card slot. (See c.)
Step 4 Remove the Flash Disk from the slot and place it in an antistatic bag.
This completes the procedure for installing a Flash Disk in a vertically oriented system. Proceed to the "Working with a Flash Disk" section.
The procedures in this section describe how to insert and eject a Flash Disk in systems in which the PC Card slots are horizontally oriented. The following two procedures are discussed:
Determine the system you have and use the appropriate procedure. (For a list of systems that support the Flash Disk, see the "Hardware Requirements" section.) You do not need to turn off system power for these procedures.
Use the following procedure to install and eject a Flash Disk in a Cisco 7100 series router:
To ensure protection from electromagnetic interference (EMI), the PC Card slots have a cover that is secured with a captive screw.
Step 2 Use a 3/16-inch flat-blade screwdriver to loosen the captive screw that secures the PC Card slot cover; lift the cover to reveal the PC Card slots. (See Figure 2.)
Step 3 Hold the Flash Disk with its connector end toward the PC Card slot and its back label facing up. (See Figure 3a.)
The Flash Disk is keyed. The ejector button does not pop out if the Flash Disk is not completely inserted.
Step 4 Insert the Flash Disk into the PC Card slot until the Flash Disk completely seats in the connector at the rear of the slot, and the ejector button pops out toward you.
(See Figure 3b.)
The Flash Disk does not insert all the way inside the PC Card slot; a portion of the Flash Disk remains outside the slot. Do not attempt to force the Flash Disk past this point.
Step 5 Close the cover and use a 3/16-inch flat-blade screwdriver to tighten the captive screw.
Step 6 To eject a Flash Disk, lift the PC Card slot cover and press the ejector button--located to the left of the slot. (See Figure 3c.)
Step 7 Remove the Flash Disk from the PC Card slot, and place it in an antistatic bag.
Step 8 Close the cover and use a 3/16-inch flat-blade screwdriver to tighten the captive screw.
This completes the procedure for installing a Flash Disk in a Cisco 7100 series router. Proceed to the "Working with a Flash Disk" section.
Use the following procedure to install and eject a Flash Disk in all other systems that have horizontally oriented PC Card slots:
Step 2 Hold the Flash Disk with its connector end toward the PC Card slot and its front label up.
The Flash Disk is keyed and cannot be seated the wrong way. The ejector button does not pop out if the Flash Disk is not completely inserted.
Step 3 Insert the Flash Disk into the PC Card slot until the Flash Disk completely seats in the connector at the rear of the slot, and the ejector button pops out toward you.
(See Figure 4b).
The Flash Disk does not insert all the way inside the PC Card slot; a portion of the Flash Disk remains outside the slot. Do not attempt to force the Flash Disk past this point.
Step 4 To eject a Flash Disk, press the appropriate ejector button--located to the right of the slot-- until the Flash Disk is free of the connector at the rear of the PC Card slot.
(See Figure 4c.)
Step 5 Remove the Flash Disk from the slot and place it in an antistatic bag.
This completes the procedure for installing a Flash Disk in a horizontally oriented system. Proceed to the following section, "Working with a Flash Disk."
This section provides basic instructions for working with a Flash Disk in your system. Detailed descriptions of more complex Flash Disk options and the Cisco IOS File System feature are beyond the scope of this publication and can be found in the following Cisco IOS Release 12.0 publications:
|
Note These and all publications are available on the Documentation CD-ROM and Cisco Connection Online (CCO). To obtain the Documentation CD-ROM, see the "Documentation CD-ROM" section. To access CCO, see the "Cisco Connection Online" section. |
This section includes the following subsections:
|
Note You can only boot from a Cisco IOS software image stored in a Flash Disk using the following systems: RSP4- and RSP8-based Cisco 7500 series systems, and NPE-300-based systems. (The NPE-300-based systems include the Cisco 7204VXR and the Cisco 7206VXR routers.) In all other systems, booting from Flash Disk-based Cisco IOS software images is not supported. You can use Flash Disks for simple storage in all the systems listed in the "Hardware Requirements" section. |
This section lists some of the basic software commands you can use with the Flash Disk. Examples of these commands are included in the sections that follow.
The Flash Disk and other memory devices and locations in your system are defined as file systems, which are locations where you can store, use, or retrieve files and software images. (See the brief discussion about Cisco IOS file systems on page 9.)
You can use Flash Disks in either one or both of the PC Card slots on your system processor, or you can use one Flash Disk in one PC Card slot and a linear Flash memory card in the adjacent PC Card slot. Flash Disks in PC Card slots 0 and 1 are referred to as disk0: and disk1:, respectively, whereas linear Flash memory cards in PC Card slots 0 and 1 are referred to as slot0 and slot1:, respectively.
The following partial output of the show file systems command shows a sample system with a Flash Disk--called disk0:--installed in PC Card slot 0 and a linear Flash memory card--called slot1:--installed in PC Card slot 1:
System# show file systems
File Systems:
Size(b) Free(b) Type Flags Prefixes
(Additional displayed text omitted from this example.)
48755200 48747008 flash rw disk0:
7995392 4717276 flash rw slot1:
Table 2 lists the software commands that you can use with the Flash Disk.
|
Note You can use other arguments with some of the commands listed in Table 2; however, in Table 2 and throughout this publication, command arguments are limited to those that apply to the Flash Disk and related file systems. For a discussion of additional command arguments, refer to the Configuration Fundamentals Command Reference publication, in the chapter "File Management Commands." |
| Command and Arguments | Description | ||
|---|---|---|---|
cd [disk0: | disk1:]directory-name | Changes current directory. | ||
copy [disk0: | disk1:]source-filename | Copies from one file to another.
| ||
delete [disk0: | disk1:]filename | Deletes a file. | ||
dir [/all | disk0: | disk1:] | Lists files on a file system. | ||
format [flash: | bootflash: | disk0: | disk1:] | Formats a file system.
| ||
mkdir [disk0: | disk1:]directory-name | Creates a new directory. | ||
pwd | Displays current working directory. | ||
rename [disk0: | disk1:]filename | Renames a file. | ||
rmdir [disk0: | disk1:]directory-name | Removes an existing directory. | ||
show [disk0: | disk1:] | Lists information about Flash Disk format and geometry. |
This section provides examples of some of the basic software commands you can use with the Flash Disk. See Table 2 for optional arguments you can use with some of the following commands:
To display information about Flash Disk format and geometry, use the command:
show [disk0: | disk1:]
System# show disk0: ******** ATA Flash Card Geometry/Format Info ******** ATA CARD GEOMETRY Number of Heads: 16 Number of Cylinders 840 Sectors per Cylinder 32 Sector Size 512 Total Sectors 430080 ATA CARD FORMAT Number of FAT Sectors 105 Sectors Per Cluster 16 Number of Clusters 26822 Number of Data Sectors 429536 Base Root Sector 338 Base FAT Sector 128 Base Data Sector 370 Router#
where:
To determine which PC Card slot you are accessing, use the pwd command:
System# pwd disk0:/ System#
The preceding example indicates that you are currently in the working directory called disk0:, which is the Flash Disk in PC Card slot 0.
To move back and forth between installed Flash Disks, use the cd command by defining a specific path name. Then to verify your working directory, use the pwd command:
System# cd disk1: System# pwd disk1:/ System# cd disk0: System# pwd disk0:/
You can also move up (or back) one level in the Flash Disk directory hierarchy using the cd .. command, and then verify your working directory with the pwd command:
System# pwd disk1:daily_dir/ System# cd .. System# pwd disk1:/ System#
To list the directory structure and contents of the Flash Disk from which you are currently working, use the dir command with no arguments:
System# dir Directory of disk1:/ 1 drw- 0 Jul 25 1998 10:23:11 daily_dir 2 drw- 0 Jul 25 1998 10:28:37 access_lists 48755200 bytes total (48742912 bytes free) System#
Note that the size of the Flash Disk is shown in the output of the dir command. (A 48-MB Flash Disk is shown in this example.) You can also view the contents of other directories and file systems using specific optional arguments with the dir command. (See Table 2.)
To format a new Flash Disk, use the format [disk0: | disk1:] command.
|
Note You must format a new Flash Disk before you can use it. If you plan to use a Flash Disk that was formatted and used on another type of system, see the "Compatibility Requirements" section to determine if you need to reformat the Flash Disk first. |
 |
Caution The formatting procedure erases all information on the Flash Disk. To prevent the loss of important data that might be stored on a Flash Disk, proceed carefully. If you want to save data that is currently on your Flash Disk, copy the data to a TFTP server or to another Flash Disk before you format the new Flash Disk. A Flash Disk that was shipped as part of a configured system contains a Flash Disk-compatible Cisco IOS software image; therefore, you do not need to format it to use it in the system in which it was shipped. |
|
Note A spare Flash Disk is shipped blank; therefore, you must format it before you can use it. |
Use the following procedure to format a new Flash Disk using the format command. (The procedure assumes you have already booted your system.)
If slot 0 is not available, use slot 1.
Step 2 Use the format disk0: command to format the Flash Disk in PC Card slot 1 as follows:
System# format disk0: Format operation may take a while. Continue? [confirm] Format operation will destroy all data in `disk0:'. Continue? [confirm] Format:Drive communication & 1st Sector Write OK... Writing Monlib sectors..................................................................... ....................... Monlib write complete Format:All system sectors written. OK... Format:Total sectors in formatted partition:81760 Format:Total bytes in formatted partition:49861120 Format:Operation completed successfully. Format of disk0:complete
|
Note A 48-MB Flash Disk was formatted in this example. |
The new Flash Disk is now formatted and ready to use in the system on which you formatted it.
(For specific formatting and compatibility requirements, see the "Compatibility Requirements" section.)
To copy an image from a Flash Disk to another file system or from another file system to the Flash Disk, use the copy command:
copy [tftp: | bootflash: | disk0: | disk1:]source-filename [tftp: | bootflash: | disk0: | disk1:]destination-filename
where:
The following assumptions are made for this command:
|
Note You might need to copy a new image to a Flash Disk whenever a new Cisco IOS software release or a new Cisco IOS software maintenance release becomes available. You can use the copy command for this purpose. |
Use the following procedure to copy a file (called new.image in this example) located on a Flash Disk--called disk1:--in PC Card slot 1 to the Flash Disk--called disk0:--in PC Card slot 0:
Step 2 To copy the image new.image to Flash Disk disk0:, use the following series of commands:
System> enable Password: System# copy disk1:new.image disk0:new.image 3393 bytes copied in 0.548 secs# System#
In the preceding example, the 3393-byte file new.image was copied to the Flash Disk in PC Card slot 0 in approximately one-half second.
Step 3 Verify that the file new.image is now on the Flash Disk in PC Card slot 0:
System# pwd disk0:/ System# dir Directory of disk0:/ 1 -rw- 3393 Jul 26 1998 17:44:47 new.image 48755200 bytes total (48747008 bytes free) System#
To create a directory on the Flash Disk, use the mkdir command. The following example shows how to create a directory called daily_dir on the Flash Disk in PC Card slot 1, and then verify that it was created:
System# mkdir disk1:daily_dir Created dir disk1:daily_dir System# dir Directory of disk1:/ 1 drw- 0 Jul 25 1998 10:15:43 daily_dir 48755200 bytes total (48751104 bytes free) System#
|
Note If you create a directory and place a file in it that you plan to access or use later on, be sure to define the entire directory path to the file as you enter the appropriate software commands. For example, if you placed the file itsa.file into the directory daily_dir on the Flash Disk in PC Card slot 1, you must designate the entire directory path as follows: disk1:daily_dir/itsa.file. Otherwise, the system might not be able to locate this file. |
To remove a directory from the Flash Disk, use the rmdir command. The following example shows how to remove the directory daily_dir from the Flash Disk in PC Card slot 1, and then verify that it was removed:
System# rmdir disk1:daily_dir Delete disk1:daily_dir? [confirm] y Removed dir disk1:daily_dir System# dir Directory of disk1:/ No files in directory. 48755200 bytes total (48751104 bytes free) System#
To delete a file from a Flash Disk, use the delete command. Use the dir command to find the file you want to delete, and then use the delete command to delete it.
The following example shows how to find a file (called fun1) on the Flash Disk in PC Card slot 0, delete the file, and then verify that it is deleted:
System# dir Directory of disk0:/ 1 drw- 0 May 10 1998 09:54:53 fun1 48755200 bytes total (48742912 bytes free)
Step 2 Delete the file fun1:
System# delete disk0:fun1
Step 3 Verify that the file fun1 is deleted:
System# dir Directory of disk0:/ No files in directory. 48755200 bytes total (48742912 bytes free) System#
This section explains how to enable booting from a Flash Disk.
|
Note You can only boot from a Cisco IOS software image stored in a Flash Disk using the following systems: RSP4- and RSP8-based Cisco 7500 series systems, and NPE-300-based systems. (NPE-300-based systems include the Cisco 7204VXR and the Cisco 7206VXR routers.) In all other systems, booting from Flash Disk-based Cisco IOS software images is not supported. You can use Flash Disks for simple storage in all the systems listed in the "Hardware Requirements" section. |
To enable booting from a Flash Disk, set configuration register bits 3, 2, 1, and 0 to a value between 2 and 15 in conjunction with the boot system [disk0: | disk1:]filename configuration command. This section includes only descriptions of boot commands specific to the Flash Disk. (You can use either the slotn: argument or the diskn: argument for boot commands.)
Following are definitions of the various Flash Disk-related boot commands:
|
Note As you enter boot commands, pay attention to how you use the Spacebar, which influences the way your system interprets the commands. Also, ensure that you define the entire path to a file as you enter the boot commands; otherwise, the system might not be able to find the file. |
For example, notice the difference in the following correct and incorrect commands:
System(config)# boot system disk0:myfile
Based on the preceding correct command, the system boots the file specified (myfile).
System(config)# boot system disk0: myfile
Based on the preceding incorrect command, the system finds the filename field blank because there is a space after disk0:. In this case, the system ignores the filename argument and boots the first file on the Flash Disk, which might not be the file called myfile.
Use the following procedure to enable booting the file myfile from a Flash Disk:
System# configure terminal Enter configuration commands, one per line. End with CTRL-Z. System(config)# boot system disk0:myfile
Step 2 Enable the boot system disk0:myfile command using the config-register command with the hexadecimal value shown in the following example:
System(config)# config-reg 0x2102
This command, with the hexadecimal value 0x2102, results in the following:
Step 3 Press Ctrl-Z to exit configuration mode:
System(config)# Crtl-Z System#
Step 4 Save the new configuration to NVRAM using the copy system:running-config nvram:startup-config command as follows:
System# copy system:running-config nvram:startup-config
This section explains how to make a Flash Disk-based Cisco IOS software image a bootable image.
|
Note You can only boot from a Cisco IOS software image stored in a Flash Disk using the following systems: RSP4- and RSP8-based Cisco 7500 series systems, and NPE-300-based systems. (NPE-300-based systems include the Cisco 7204VXR and the Cisco 7206VXR routers.) In all other systems, booting from Flash Disk-based Cisco IOS software images is not supported. You can use Flash Disks for simple storage in all the systems listed in the "Hardware Requirements" section. |
After you copy a software image to the Flash Disk, use the following series of commands to make the image bootable (the file named new.image in this example). The software image in this example is located on the Flash Disk in PC Card slot 0. Note that the config-register command is also a part of this command sequence because you must set the configuration register to 0x2102 to enable loading an image from the Flash Disk.
System# config terminal System(config)# no boot system System(config)# boot system disk0:new.image System(config)# config-register 0x2102 Ctrl-Z System# copy system:running-config nvram:startup-config System# reload
When the system reloads, it boots the image new.image from the Flash Disk in slot 0.
This section provides the procedure for upgrading your ROM monitor software image by replacing the boot ROM device on your RSP4 with a new boot ROM device.
|
Note The procedure in this section is required only if you need to boot a Cisco IOS software image from the Flash Disk in your RSP4 when the system is executing from the ROM monitor software image. If you require this capability, your ROM monitor software image must be Release 12.0(2) or a later release of 12.0 and you must upgrade it as required. |
|
Caution Replacing the boot ROM device on your system processor might make your current configuration file stored in NVRAM unreadable and unusable. Before removing the system processor and installing the new boot ROM device, we strongly recommend that you save your configuration file to a TFTP server or to a linear Flash memory card, and then retrieve it after you install the new device. |
The following tools and parts are required for this boot ROM upgrade procedure:
|
Caution A PLCC-type boot ROM device does not have pins that plug into the socket; instead, the contacts are on the sides of the boot ROM device and along the inner sides of the socket. Therefore, you cannot use a flat-blade screwdriver to remove a PLCC-type boot ROM device. Forcing a screwdriver or other tool between the boot ROM and the sides of the socket to pry out the boot ROM might damage the component or the socket or both. You must use a PLCC-type extractor tool. |
Use the following procedure to replace the boot ROM device on your RSP4:
Step 2 Turn off system power and remove the RSP4. (For the procedure for removing your RSP4, refer to the installation and configuration publication that shipped with your Cisco 7500 series system or your RSP4.)
Step 3 Place the RSP4 flat on an antistatic mat or surface and locate the boot ROM device.
(See Figure 5.)
Step 4 Carefully remove the new boot ROM device from its packaging and verify that it is the correct version for this upgrade. Return the new device to its packaging.
Step 5 Note the orientation of the installed boot ROM device so that you can install the new device with the same orientation.
Step 6 Place the angled tips of the PLCC-type IC extractor tool beneath the corners of the boot ROM device and carefully remove the device. (See Figure 6.) Note the orientation of the boot ROM device.
Step 7 Remove the new boot ROM device from its packaging.
Step 8 Align the new boot ROM device with the PLCC socket; use the same orientation as the old boot ROM device.
Step 9 Gently press the boot ROM into the PLCC socket. (See Figure 7.) The boot ROM device is properly installed when the top of the device is flush with the top of the socket.
This completes the procedure for replacing the boot ROM device on an RSP4.
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
Language | E-mail Address |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.
Posted: Wed Aug 16 10:20:28 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.