|
|
This chapter provides detailed descriptions of the commands used to load and copy system images and microcode images. System images contain the system software. Microcode images contain microcode to be downloaded to various hardware devices.
| Old Command | New Command |
|---|---|
| copy erase flash | erase flash |
| copy verify or copy verify flash | verify flash
or verify |
| copy verify bootflash | verify bootflash |
For configuration information and examples, refer to the "Loading and Maintaining System Images and Microcode" chapter in the Configuration Fundamentals Configuration Guide.
The verify or verify flash command replaces this command. Refer to the descriptions of the verify and verify flash commands for more information.
The verify bootflash command replaces this command. Refer to the description of the verify bootflash command for more information.
To copy a Cisco IOS image from a local or remote computer (such as a PC, Macintosh, or UNIX workstation) to Flash memory on a Cisco 3600 series router using the Xmodem protocol, use the copy xmodem EXEC command.
copy xmodem device:[partition-number:][filename]| device | One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory · slot0--Flash memory card in PCMCIA slot 0 · slot1--Flash memory card in PCMCIA slot 1 |
| partition-number | (Optional) Partition number of the destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the destination file. |
EXEC
This command first appeared in Cisco IOS Release 11.2 P.
The copy tftp flash: and copy rcp flash: commands are much faster than the copy xmodem flash: command. Use the copy xmodem flash: command only if you do not have access to a TFTP or rcp server.
This copy operation is performed through the console or AUX port. The AUX port, which supports hardware flow control, is recommended.
No output is displayed on the port over which the transfer is occurring. You can use the logging buffered command to log all router messages sent to the console port during the file transfer.
The following command initiates a file transfer from a local or remote computer to the router's internal Flash memory using the Xmodem protocol:
copy xmodem flash:
You can use the master indexes or search online to find documentation of related commands.
To copy a Cisco IOS image from a local or remote computer (such as a PC, Macintosh, or UNIX workstation) to Flash memory on a Cisco 3600 series router using the Ymodem protocol, use the copy ymodem EXEC command.
copy ymodem device:[partition-number:][filename]| device | One of the following devices, which must be followed by a colon (:):
· flash--Internal Flash memory · slot0--Flash memory card in PCMCIA slot 0 · slot1--Flash memory card in PCMCIA slot 1 |
| partition-number | (Optional) Partition number of the destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the destination file. |
EXEC
This command first appeared in Cisco IOS Release 11.2 P.
The copy tftp flash: and copy rcp flash: commands are much faster than the copy ymodem flash: command. Use the copy ymodem flash: command only if you do not have access to a TFTP or rcp server.
This copy operation is performed through the console or AUX port. The AUX port, which supports hardware flow control, is recommended.
No output is displayed on the port over which the transfer is occurring. You can use the logging buffered command to log all router messages sent to the console port during the file transfer.
The following command initiates a file transfer from a local or remote computer to the router's internal Flash memory using the Ymodem protocol:
copy ymodem flash:
You can use the master indexes or search online to find documentation of related commands.
To specify the location of the microcode that you want to download from Flash memory into the writable control store (WCS) on a Cisco 7000 series with RSP7000 or Cisco 7500 series, use the microcode global configuration command. Use the no form of this command to load the microcode bundled with the system image.
microcode interface [flash file-id [slot] | system [slot]]| interface | One of the following interface processor names: aip, cip, eip, feip, fip, fsip, hip, mip, sip, sp, ssp, trip, vip, or vip2. |
| flash | (Optional) If the flash keyword is specified, a file-id argument is required, unless you are using the no microcode interface flash command. |
| filename | (Optional) Filename of the microcode in Flash memory that you want to download. This argument is only used with the flash keyword. If you use the flash keyword, the name of the microcode file in Flash is required unless the command is no microcode interface flash. (This command results in the same default condition as the command microcode interface rom, which indicates that the card should be loaded from its onboard ROM microcode.) |
| file-id | Specifies a device:filename of the microcode file to download. The colon (:) is required. Valid devices are as follows:
· bootflash--Internal Flash memory. · slot0--First PCMCIA slot. · slot1--Second PCMCIA slot. Slave devices such as slaveslot0 are invalid. The slave's file system is not available during microcode reloads. The filename is the name of the microcode file. |
| slot | Number of the slot. Range is 0 to 15. |
| system | (Optional) If system is specified, the router loads the microcode from the microcode bundled into the system image you are running for that interface type. |
The default is to load from the microcode bundled in the system image.
Global configuration
This command first appeared in Cisco IOS Release 11.0.
When using HSA for simple hardware backup, ensure that the master and slave RSP card contain the same microcode image in the same location when the router is to load the interface processor microcode from a flash file-id. Thus, if the slave RSP becomes the master, it will be able to find the microcode image and download it to the interface processor.
In the following example, all FIP cards will be loaded with the microcode found in Flash memory file fip.v141-7 when the system is booted, when a card is inserted or removed, or when the microcode reload global configuration command is issued. The configuration is then written to the startup configuration file.
Router(config)#microcode fip flash slot0:fip.v141-7 Router(config)#endRouter#copy running-config startup-config
You can use the master indexes or search online to find documentation of related commands.
To signal to the Cisco 7000 series with RSP7000 or Cisco 7500 series that all microcode configuration commands have been entered and the processor cards should be reloaded, use the microcode reload global configuration command.
microcode reloadThis command has no arguments or keywords.
Global configuration
This command first appeared in Cisco IOS Release 10.3.
You must be in configuration mode to enter this command. Immediately after you enter the microcode reload command and press Return, the system reloads all microcode. Global configuration mode remains enabled; after the reload is complete, enter the exit command to return to the EXEC system prompt.
In the following example, all controllers are reset, the specified microcode is loaded, and the CxBus complex is reinitialized according to the microcode configuration commands that have been written to memory:
Router# configure terminal Router(config)# microcode reload Router(config)# end
You can use the master indexes or search online to find documentation of related commands.
To view the system console output generated during the Flash load helper operation, use the show flh-log privileged EXEC command.
show flh-logThis command has no arguments or keywords.
Privileged EXEC
This command first appeared in Cisco IOS Release 10.3.
If you are a remote Telnet user performing the Flash upgrade without a console connection, this command allows you to retrieve console output when your Telnet connection has terminated due to the switch to the ROM image. The output indicates what happened during the download, and is particularly useful if the download fails.
The following is sample output from the show flh-log command:
Router#show flh-log%FLH: abc/igs-kf.914 from 172.16.1.111 to flash...System flash directory:FileLength Name/status1 2251320abc/igs-kf.914[2251384 bytes used, 1942920 available, 4194304 total]Accessing file 'abc/igs-kf.914' on 172.16.1.111...Loading from 172.16.13.111:Erasing device...... erasedLoading from 172.16.13.111:- [OK -2251320/4194304 bytes]Verifying checksum... OK (0x97FA)Flash copy took 79292 msecs%FLH: Re-booting system after downloadLoading abc/igs-kf.914 at 0x3000040, size = 2251320 bytes [OK]F3: 2183364+67924+259584 at 0x3000060Restricted Rights LegendUse, duplication, or disclosure by the Government issubject to restrictions as set forth in subparagraph(c) of the Commercial Computer Software - RestrictedRights clause at FAR sec. 52.227-19 and subparagraph(c) (1) (ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS sec. 252.227-7013.cisco Systems, Inc.170 West Tasman DriveSan Jose, California 95134Cisco Internetwork Operating System SoftwareCisco IOS (tm) GS Software (GS7), Version 11.0Copyright (c) 1986-1995 by cisco Systems, Inc.Compiled Tue 06-Dec-94 14:01 by smithImage text-base: 0x00001000, data-base: 0x005A9C94cisco 2500 (68030) processor (revision 0x00) with 4092K/2048K bytes ofmemory.Processor board serial number 00000000DDN X.25 software, Version 2.0, NET2 and BFE compliant.ISDN software, Version 1.0.Bridging software.Enterprise software set supported. (0x0)1 Ethernet/IEEE 802.3 interface.2 Serial network interfaces.--More--1 ISDN Basic Rate interface.32K bytes of non-volatile configuration memory.4096K bytes of processor board System flash (Read ONLY)
To show the microcode bundled into a Cisco 7000 series with RSP7000 or Cisco 7500 series system, use the show microcode EXEC command.
show microcodeThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.0.
The following is sample output from the show microcode command:
Router# show microcode Microcode bundled in system Card Microcode Target Hardware Description Type Version Version ---- --------- --------------- ----------- SP 2.3 11.x SP version 2.3 EIP 1.1 1.x EIP version 1.1 TRIP 1.2 1.x TRIP version 1.2 FIP 1.4 2.x FIP version 1.4 HIP 1.1 1.x HIP version 1.1 SIP 1.1 1.x SIP version 1.1 FSIP 1.1 1.x FSIP version 1.1
On the Cisco 1600 series, Cisco 3600 series, and Cisco 7000 family, to verify the checksum of a file on a Flash memory device, use the verify EXEC command. This command replaces the copy verify and copy verify flash commands.
verify [device:] filename (Cisco 7000 family)| device: | (Optional for Cisco 7000 family) Device containing the file whose checksum is being verified. The colon (:) is required. Valid devices are as follows:
· flash--Internal Flash memory in the Cisco 1600 series and Cisco 3600 series. This is the only valid device for the Cisco 1600 series. · bootflash--Internal Flash memory in the Cisco 7000 family. · slot0--First PCMCIA slot on the Cisco 3600 series and Cisco 7000 family. · slot1--Flash memory in the second PCMCIA slot on the Cisco 3600 series and Cisco 7000 family. · slavebootflash--Internal Flash memory on the slave RSP card of a Cisco 7507 or Cisco 7513 configured for HSA. · slaveslot0--First PCMCIA slot of the slave RSP card on a Cisco 7507 or Cisco 7513 configured for HSA. · slaveslot1--Second PCMCIA slot of the slave RSP card on a Cisco 7507 or Cisco 7513 configured for HSA. When you omit this argument, the system verifies the checksum of the specified file on the current working device. |
| filename | Name of a file on the specified Flash device. The file can be of any type. The maximum filename length is 63 characters. The filename is optional for the Cisco 1600 series and Cisco 3600 series. |
| partition-number | (Optional) Partition number to verify. You must enter a colon (:) after the partition number if a filename follows it. |
The current working device is the default device.
EXEC
This command first appeared in Cisco IOS Release 11.0.
Use the verify command to verify the checksum of a file before using it. When you omit the device: argument, the system verifies the checksum of the specified file on the current working device.
The following example verifies the gsxx file on the Flash memory card inserted in slot 0:
verify slot0:gsxx
The following example verifies the checksum of the file alz, located in the fourth partition of the Flash memory card in slot 0 of a Cisco 3600 series router:
Router#verify slot0:4PCMCIA Slot0 flash directory, partition 4: File Length Name/status 1 2205860 dirt/images/c3600-d-mz 2 1711128 dirt/images/c3600-i-mz.test 3 850 alz [3918032 bytes used, 276272 available, 4194304 total] Name of file to verify?alzVerifying checksum for 'alz' (file # 3)... OK
The following example verifies the checksum of the file alz, located in the fourth partition of the Flash memory card on a Cisco 1600 series:
Router#verify flash:4System flash directory, partition 4: File Length Name/status 1 2205860 dirt/images/c1600-d-mz 2 1711128 dirt/images/c1600-i-mz.test 3 850 alz [3918032 bytes used, 276272 available, 4194304 total] Name of file to verify?alzVerifying checksum for 'alz' (file # 3)... OK
You can use the master indexes or search online to find documentation of related commands.
cd
copy flash
copy verify
ip rcmd remote-username
pwd
show flash
To verify the checksum of a boot image in boot Flash memory, use the verify bootflash EXEC command. This command replaces the copy verify bootflash command.
verify bootflashThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.0.
You can use this command only on routers that have two banks of Flash: one bank for the boot image and the second bank for the system image.
Each boot software image that is distributed on disk uses a single checksum for the entire image. This checksum is displayed only when the image is copied into Flash memory; it is not displayed when the image file is copied from one disk to another.
The README file, which is included with the image on the disk, lists the name, file size, and checksum of the image. Review the contents of the README file before loading or duplicating the new image so that you can verify the checksum when you copy it into Flash memory or onto a server.
To display the contents of boot Flash memory, use the show bootflash command. The Flash contents listing does not include the checksum of individual files. To recompute and verify the image checksum after the image has been copied into Flash memory, use the verify bootflash command. When you enter the command, the system prompts you for the filename to verify. By default, it prompts for the last file (most recent) in Flash. Press Return to recompute the default file checksum, or enter the name of a different file at the prompt.
The following example verifies the boot file c4500-xboot:
Router# verify bootflash
Boot flash directory:
File name/status
1 c4500-xboot
[1387336 bytes used, 2806968 bytes available]
Name of file to verify? c4500-xboot
Verifying checksum for 'c4500-xboot' (file # 1)... [OK]
You can use the master indexes or search online to find documentation of related commands.
copy bootflash tftp
copy mop bootflash
copy tftp bootflash
erase bootflash
show flh-log
To verify the checksum of Flash memory, use the verify flash EXEC command. This command replaces the copy verify and copy verify flash commands.
verify flashThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 10.3.
The verify flash command is not supported on the Cisco 1600 series, Cisco 3600 series, Cisco 7000 series with RSP7000 and the Cisco 7500 series.
Each system software or microcode image that is distributed on disk uses a single checksum for the entire image. This checksum is displayed only when the image is copied into Flash memory; it is not displayed when the image file is copied from one disk to another.
The README file (which is included with the image on the disk) lists the name, file size, and checksum of the image. Review the contents of the README file before loading or duplicating the new image so that you can verify the checksum when you copy it into the Flash memory or onto a TFTP server.
To display the contents of Flash memory, use the show flash command. The Flash content listing does not include the checksum of individual files. To recompute and verify the image checksum after the image file is copied into Flash memory, use the verify flash command. When you enter the command, the screen prompts you for the filename to verify. By default, it prompts for the last file in Flash (most recent). Press Return to recompute the default file checksum, or enter the filename of a different file at the prompt.
The following example verifies the file gsxx in Flash memory:
Router#verify flashName of file to verify [gsxx]?Verifying via checksum...vvvvvvvvvvvvvvvvvvvvvvvvvvvvvFlash verification successful. Length = 1923712, checksum = 0xA0C1
The following example verifies an image when more than one Flash memory partition exists:
Router#verify flashSystem flash partition information: Partition Size Used Free Bank-Size State Copy-Mode 1 4096K 2048K 2048K 2048K Read Only RXBOOT-FLH 2 4096K 2048K 2048K 2048K Read/Write Direct [Type ?for partition directory; ? for full directory; q to abort]
The system will prompt only if there are two or more read/write partitions. If the partition entered is not valid, the process terminates. You can enter a partition number, a question mark (?) for a directory display of all partitions, or a question mark and a number (?number) for directory display of a particular partition. The default is the first partition.
File Length Name/status
1 3459720 master/igs-j.111.1.0
[3459784 bytes used, 734520 available, 4194304 total]
Name of file to verify? master/igs-j.111.1.0
Verifying checksum for 'master/igs-j.111.1.0' (file # 1)... OK
You can use the master indexes or search online to find documentation of related commands.
show flash
verify
To copy a Cisco IOS image to a Cisco 1600 series or Cisco 3600 series router using the ROM monitor and the Xmodem or Ymodem protocol, use the xmodem ROM monitor command.
xmodem [-c] [-y] [-e] [-f] [-r] [-x] [-s data-rate] [filename]| -c | (Optional) CRC-16 checksumming, which is more sophisticated and thorough than standard checksumming. |
| -y | (Optional) Uses Ymodem protocol for higher throughput. |
| -e | (Optional) Erases the first partition in Flash memory before starting the download. This option is only valid for the Cisco 1600. |
| -f | (Optional) Erases all of Flash memory before starting the download. This option is only valid for the Cisco 1600. |
| -r | (Optional) Downloads the file to DRAM. The default is Flash memory. |
| -x | (Optional) Do not execute Cisco IOS image on completion of the download. |
| -s data-rate | (Optional) Sets the console port's data rate during file transfer. Values are 1200, 2400, 4800, 9600, 19200, 38400, and 115200 bps. The default rate is specified in the configuration register. This option is only valid for the Cisco 1600 series. |
| filename | (Optional) Filename to copy. This argument is ignored when -r is specified, because only one file can be copied to DRAM. On the Cisco 1600 series, files are loaded to the ROM for execution. |
Xmodem protocol with 8-bit CRC, file downloaded into Flash memory and executed on completion.
ROM monitor
This command first appeared in Cisco IOS Release 11.2 P.
The Cisco 3600 series does not support XBOOT functionality. If your Cisco IOS image is erased or damaged, you cannot load a new image over the network.
Use the xmodem ROM monitor command to download a new system image to your router from a local personal computer (such as a PC, Mac, or UNIX workstation), or a remote computer over a modem connection, to the router's console port. The computer must have a terminal emulation application that supports these protocols.
For the Cisco 3600 series, your router must have enough DRAM to hold the file being transferred, even if you are copying to Flash memory. The image is copied to the first file in internal Flash memory. Any existing files in Flash memory are erased. There is no support for partitions or copying as a second file.
For the Cisco 1600 series, if you include the -r option, your router must have enough DRAM to hold the file being transferred. To run from Flash, an image must be positioned as the first file in Flash memory. If you are copying a new image to boot from Flash, erase all existing files first.
 | Caution A modem connection from the telephone network to your console port introduces security issues that you should consider before enabling the connection. For example, remote users can dial into your modem and access the router's configuration settings. |
The following example uses the xmodem -c filename ROM monitor command to copy the file new-ios-image from a remote or local computer:
rommon >xmodem -c new-ios-imageDo not start the sending program yet... File size Checksum File name 1738244 bytes (0x1a8604) 0xdd25 george-admin/c3600-i-mz WARNING: All existing data in bootflash will be lost! Invoke this application only for disaster recovery. Do you wish to continue? y/n [n]:yesReady to receive file new-ios-image ...
You can use the master indexes or search online to find documentation of related commands.
|
|