Cisco IOS Release 11.1 AA Release Note and Update to Configuration Guides and Command References
December 23, 1996
This document discusses the memory requirements, supported interfaces, and available feature sets for Cisco IOS Release 11.1 AA, up to and including Release 11.1(8)AA. It also provides configuration tasks and command reference documentation for the new features available on supported platforms.
Cisco IOS Release 11.1 AA is a platform-specific release. It consists of a limited number of feature-set images that provide new features or functionality to Cisco IOS Release 11.1 after Release 11.1(5). Release 11.1 AA does not replace Release 11.1; it provides an independent software release vehicle that includes all the software defect modifications of Cisco IOS Release 11.1(x), and it also includes software enhancements and new platform support.
Use Release 11.1 AA when your hardware specifically requires this release or when the features and functionality you need are provided only in this release.
This document is divided into the following sections:
Use this document in conjunction with the Release Notes for Cisco IOS Release 11.1 and the Cisco IOS Release 11.1 configuration guide and command reference publications, specifically the Configuration Fundamentals Configuration Guide, Configuration Fundamentals Command Reference, Access Services Configuration Guide, Access Services Command Reference. In addition, use the Cisco AS5200 Universal Access Server Installation Guide and Software Configuration Guide and the 12-Port Modem AT Command Set and Register Summary publication with the Cisco AS5200 access server.
This section describes the platforms, interfaces, and feature sets supported in
Cisco IOS Release 11.1(8)AA.
Cisco IOS Release 11.1(8)AA supports the following routers and access server:
Table 1 lists the interfaces supported in Cisco IOS Release 11.1(8)AA:
Table 1 : Interfaces Supported
| Interface | Cisco 1600 | Cisco 3600 | Cisco AS5200 |
|---|---|---|---|
| Ethernet (AUI) | Yes | Yes | Yes |
| Ethernet (10BaseT) | Yes | Yes | No |
| Synchronous serial | Yes | Yes | Yes |
| Asynchronous serial | Yes | Yes | Yes |
| Token Ring | No | Yes | No |
| ISDN BRI S/T | Yes | Yes | No |
| ISDN BRI U | Yes | Yes | No |
| ISDN PRI | No | Yes | Yes |
| Channelized T1 and E1 | No | Yes | Yes |
| Switched 56 kbps | Yes | No | No |
| Switched Digital Data Service (DDS) | Yes | No | No |
Table 1 lists the feature sets available in Cisco IOS Release 11.1(8)AA for the Cisco 3600 series and Cisco 1600 series.
The following feature sets table uses these conventions to identify features:
Table 3 lists the features sets available for the Cisco AS5200 universal access server.
| Feature Set | |||
|---|---|---|---|
| Feature
|
IP/Managed Modems | Desktop/
Managed Modems |
Enterprise/RMON/
Managed Modems |
| SNMP | X | X | X |
| RMON1 | --- | --- | X |
| Asynchronous support (SLIP) | X | X | X |
| CSLIP | X | X | X |
| ARA Protocol | --- | X | X |
| Frame Relay | X | X | X |
| SMDS | X | X | X |
| X.25 | X | X | X |
| ISDN | X | X | X |
| PPP | X | X | X |
| CPPP | X | X | X |
| HDLC | X | X | X |
| IP | X | X | X |
| RIP | X | X | X |
| RIPv2 | X | X | X |
| IGRP | X | X | X |
| Enhanced IGRP | X | X | X |
| OSPF | X | X | X |
| BGP | X | X | X |
| EGP | X | X | X |
| PIM | X | X | X |
| NHRP | X | X | X |
| ES-IS | --- | --- | X |
| IS-IS | --- | --- | X |
| Snapshot routing | X | X | X |
| NTP | X | X | X |
| Bridging (transparent and translational) | X | X | X |
| Multiring | X | X | X |
| LAN extension host | X | X | X |
| IPX | --- | X | X |
| NLSP | --- | X | X |
| IPXWAN 2.0 | --- | X | X |
| RTMP | --- | X | X |
| SMRP | --- | X | X |
| SRTP | --- | --- | X |
| AppleTalk Versions 1 and 2 | --- | X | X |
| AURP | --- | X | X |
| DECnet IV | --- | X | X |
| DECnet V | --- | --- | X |
| Apollo Domain | --- | --- | X |
| Banyan VINES | --- | --- | X |
| ISO CLNS | --- | --- | X |
| XNS | --- | --- | X |
| Lock-and-Key | X | X | X |
| MD5 routing authentication | X | X | X |
| Kerberized login | --- | --- | X |
| V.120 | --- | --- | X |
| SRB | --- | --- | X |
| RSRB | --- | --- | X |
| APPN | --- | --- | --- |
| FRAS BAN | --- | --- | X |
| DLSw (RFC 1795) | --- | --- | X |
| DLSw+ | --- | --- | X |
| SDLC | --- | --- | X |
| SDLLC | --- | --- | X |
| STUN | --- | --- | X |
| TG/COS | --- | --- | X |
| QLLC | --- | --- | X |
| Bisync | --- | --- | X |
| DSPU | --- | --- | X |
| NetView Native Service Point | --- | --- | X |
| Protocol translation | --- | --- | X |
| TN3270 | --- | --- | X |
| LAT | --- | --- | X |
| SRT bridging | --- | --- | X |
| XRemote | --- | --- | X |
| Telnet | X | X | X |
| PAD | X | X | X |
| AutoInstall | X | X | X |
| Modem autoconfiguring | --- | --- | X |
| Router monitoring | X | X | X |
| DHCP | X | X | X |
| NASI | --- | --- | --- |
| NetBEUI over PPP | --- | --- | --- |
| RADIUS | X | X | X |
| Modem Management | X | X | X |
Table 4 lists the minimum Flash and DRAM requirements for the Cisco 3600 series and Cisco 1600 series feature sets.
Table 4 : Minimum Memory Requirements for the Cisco 1600 Series and Cisco 3600 Series
| Feature Set | Cisco
Router Series |
Minimum
Flash |
Minimum DRAM |
| IP | Cisco 3600 | 4 MB | 16 MB |
| Cisco 1600 | 4 MB | 2 MB | |
| IP with IBM base | Cisco 3600 | 4 MB | 16 MB |
| IP with AppleTalk | Cisco 1600 | 4 MB | 2 MB |
| IP with AppleTalk Plus | Cisco 1600 | 6 MB | 4 MB |
| IP Plus | Cisco 1600 | 4 MB | 4 MB |
| IP/IPX | Cisco 3600 | 4 MB | 16 MB |
| Cisco 1600 | 4 MB | 2 MB | |
| IP/IPX Plus | Cisco 1600 | 6 MB | 4 MB |
| IP/IPX with IBM base | Cisco 3600 | 4 MB | 16 MB |
| IP/IPX with IBM base
and APPN |
Cisco 3600 | 4 MB | 32 MB |
| IP/IPX/AppleTalk | Cisco 1600 | 6 MB | 4 MB |
| IP/IPX/AppleTalk Plus | Cisco 1600 | 6 MB | 4 MB |
| Desktop | Cisco 3600 | 4 MB | 16 MB |
| Desktop with IBM base | Cisco 3600 | 4 MB | 24 MB |
| Enterprise | Cisco 3600 | 4 MB | 24 MB |
| Enterprise with APPN1 | Cisco 3600 | 8 MB | 32 MB |
Table 5 lists the minimum memory requirements for the feature sets available for the Cisco AS5200.
Table 5 : Minimum Memory Requirements for the Cisco AS5200
| Cisco AS5200 | Minimum Flash Memory | Minimum Main Memory | Release 11.1(8)AA Runs from |
|---|---|---|---|
| IP/Managed Modems Set | 8 MB Flash | 8 MB DRAM | Flash |
| Desktop/Managed Modems Set | 8 MB Flash | 8 MB DRAM | Flash |
| Enterprise/RMON/Managed Modems Set | 8 MB Flash | 8 MB DRAM | Flash |
New Software Features Supported in Release 11.1(8)AA
There are no new features introduced in Cisco IOS Release 11.1(8)AA.
New Software Features Supported in Release 11.1(7)AA
Cisco IOS Release 11.1(7)AA adds support for the following new platforms and features:
New Software Features Supported in Release 11.1(6)AA
Cisco IOS Release 11.1(6)AA adds support for the following new features for the Cisco AS5200:
This section describes possibly unexpected behavior by Release 11.1(8)AA. Unless otherwise noted, these caveats apply to all 11.1 AA releases up to and including 11.1(8)AA. The caveats listed here describe only the serious problems.
The complete list of caveats against Release 11.1 are available on Cisco Documentation CD, which is the Cisco library of product information on CD-ROM. On the CD, access the Cisco IOS 11.1 caveats in the Cisco IOS Release 11.1 database.
Release 11.1(7)AA Caveats/Release 11.1(8)AA Modifications
This section describes possibly unexpected behavior by Release 11.1(7)AA. Unless otherwise noted, these caveats apply to all 11.1 AA releases up to and including 11.1(7)AA. For additional caveats applicable to Release 11.1(7)AA, see the caveats sections for newer 11.1 AA releases. The caveats for newer releases precede this section.
All the caveats listed in this section are resolved in release 11.1(8)AA.
Release 11.1(6)AA Caveats/Release 11.1(7)AA Modifications
This section describes possibly unexpected behavior by Release 11.1(6)AA. Unless otherwise noted, these caveats apply to all 11.1AA releases up to and including 11.1(6)AA. For additional caveats applicable to Release 11.1(6)AA, see the caveats sections for newer 11.1 releases. The caveats for newer releases precede this section.
All the caveats listed in this section are resolved in release 11.1(7)AA.
Use of the DNS Name Service for alias lookups causes the router to reload. Lookups of canonical names do not exhibit this problem. [CSCdi73022]
Update to the Configuration Guides
This section provides updated documentation to the Configuration Fundamentals Configuration Guide and Access Services Configuration Guide. This section contains the following updates:
Pointers to chapter titles and sections are shown in italic typeface.
Update for the Cisco 3600 Series and Cisco 1600 Series Routers
This section contains updated documentation that includes new or modified Cisco IOS commands for the Cisco 1600 series and Cisco 3600 series routers.
On page 1-68 in the Configuration Fundamentals Configuration Guide, replace the "Display System Image and Configuration Information" section with the following new section:
Display System Image and Configuration Information
Perform the following tasks in EXEC mode to display information about system software, system image files, and configuration files:
| Task | Command |
|---|---|
| List the contents of the BOOT environment variable, the name of the configuration file pointed to by the CONFIG_FILE environment variable, and the contents of the BOOTLDR environment variable. | show boot (Cisco 7000 series and Cisco 7500 series only) |
| List the names of the Flash devices currently supported on the router. | show flash devices (Cisco 7500 series only) |
| List the configuration information stored in a specified file. | show file device:filename (Cisco 7000 series and Cisco 7500 series only) |
| List information about Flash memory, including system image filenames and amounts of memory used and remaining. | show flash |
| List information about Flash memory, including system image filenames, amounts of memory used and remaining, and Flash partitions.
The device: argument for the Cisco 1600 series and Cisco 3600 series specifies a Flash device. For the Cisco 3600 series, your choice of devices are internal Flash memory (flash) or a Flash memory PC card inserted one of two PCMCIA slots (slot0 or slot1). For the Cisco 1600 series, a PC card inserted in a PCMCIA slot is the only supported device, which is specified using the flash keyword. |
Enter one of the following commands:
|
| View the console output generated during the Flash load helper operation. | show flh-log |
| List the configuration information in running memory. | show running-config |
| List the startup configuration information. On all platforms except the Cisco 7000 series and Cisco 7500 series, the startup configuration is usually NVRAM. On the Cisco 7000 series and Cisco 7500 series, the CONFIG_FILE environment variable points to the startup configuration. | show startup-config |
| List the system software release version, configuration register setting, and so on. | show version |
Refer to the Configuration Fundamentals Command Reference for examples of these commands.
| Task | Command |
|---|---|
| Recompute and verify the image checksum after the image is copied into a Flash memory device. | Enter the command that corresponds to the type of platform you are using:
|
The checksum of individual files on Flash memory devices can be verified on a Cisco 1600 series, Cisco 3600 series, Cisco 7000 series, and Cisco 7500 series router. On the Cisco 3600 series, you can verify the checksum of a file located in internal Flash memory (flash) or a Flash memory PC card inserted in one of two PCMCIA slots (slot0 or slot1). On the Cisco 1600 series, you can verify the checksum of a file in a Flash memory PC card, which is specified using the flash device keyword. This card is the only Flash memory that exists on the Cisco 1600 series. On the Cisco 7000 series, you can verify the checksum of a file located in internal Flash (flash) or in the PCMCIA slot (slot0). On the Cisco 7500 series, you can verify the checksum of a file located in internal Flash (bootflash) or in one of the PCMCIA slots (slot0 and slot1).
When you enter the verify flash command on the Cisco 7000 series routers, the screen prompts you for the filename to verify. By default, it prompts for the last (most recent) file in Flash. Press Return to recompute the default file checksum, or enter the filename of a different file at the prompt. Note that the checksum for microcode images is always 0x0000.
The following example for the Cisco 7000 series routers illustrates how to use this command:
Router# verify flash Name of file to verify [gsxx]? Verifying via checksum... vvvvvvvvvvvvvvvvvvvvvvvvvvvvv Flash verification successful. Length = 1923712, checksum = 0xA0C1 Router#
The following example verifies the gsxx file on the Flash memory PC card inserted in slot 0 of a Cisco 7000's RP card or a Cisco 7500's RSP card:
Router# verify slot0:gsxx
The following Cisco 3600 series example verifies the checksum of the file c3600-i-mz.test, which is in the fourth partition of a Flash memory PC card inserted in PCMCIA slot 0.
Router# verify slot0: PCMCIA Slot0 flash Partition Size Used Free Bank-Size State Copy Mode 1 4096K 3069K 1026K 4096K Read/Write Direct 2 4096K 3069K 1026K 4096K Read/Write Direct 3 4096K 0K 4096K 4096K Read/Write Direct 4 4096K 3826K 269K 4096K Read/Write Direct [Type ?<no> for partition directory; ? for full directory; q to abort] Which partition? [default = 1] 4 PCMCIA Slot0 flash directory, partition 4: File Length Name/status 1 2205860 dirt/images/c3600-d-mz 2 1711128 c3600-i-mz.test 3 850 alz [3918032 bytes used, 276272 available, 4194304 total] Name of file to verify? c3600-i-mz.test Verifying checksum for 'c3600-i-mz.test' (file # 2)... OK
On page 1-105 in the Configuration Fundamentals Configuration Guide, replace the "Partition Flash Memory" section with the following new section:
To partition Flash memory, perform the following task in global configuration mode:
| Task | Command |
|---|---|
| Partition Flash memory. | Enter one of the following commands. Choose the command that corresponds to your router.
|
The device argument enables you to specify which Flash memory device you want to partition. For the Cisco 3600 series, your choices are internal Flash memory (flash) or Flash memory PC cards inserted in one of two PCMCIA slots (slot0 or slot1). On the Cisco 1600 series, partitions can be made only on a Flash memory PC card inserted in a PCMCIA slot, which is specified using the flash device keyword.
For the Cisco 1600 series and Cisco 3600 series, the number of partitions that you create in a single Flash device is equal to the number of banks present in the same device. Enter the show flash: all command to view the number of banks on the Flash memory device. The number of partition size entries you set is equivalent to the number of specified partitions. For example, the partition slot0: 2 8 8 command configures two partitions to be 8 MB large each. The first 8 corresponds to the first partition; the second 8 corresponds to the second partition. For all other platforms, the partition-size argument is equal to 1 or 2.
This task succeeds only if the system has at least two banks of Flash and the partitioning does not split an existing file in Flash memory across two or more partitions.
Replace the "Copy a File into a Flash Partition" section on page I-106 of the Configuration Fundamentals Configuration Guide with the following new section:
Copy a File into a Flash Partition
To download a file into a partition in internal Flash memory, perform one of the following tasks in EXEC mode:
| Task | Command |
|---|---|
| Download a file from a TFTP server into a Flash partition. | Enter one of the following commands. Choose the command that corresponds to your router.
|
| Download a file from a MOP server into a Flash partition. | Enter the command that corresponds to the platform you are using:
|
| Download a file from an rcp server into a Flash partition. | Enter the command that corresponds to the platform you are using:
|
Use the device argument on the Cisco 3600 series to specify which Flash memory device you want to serve as the copy destination. Your choices are internal Flash memory (flash) or a Flash memory PC card inserted in one of two PCMCIA slots (slot0 or slot1).
Flash memory on a Cisco 1600 series router runs from a Flash memory PC card, which is inserted in a PCMCIA slot. This card is the only Flash memory that exists on the Cisco 1600 series. You can write Cisco IOS images to the PC card by specifying the flash device. For example, use the copy tftp flash:, copy mop flash:, or copy rcp flash: commands.
The prompts displayed after you execute these tasks indicate the method by which the file can be downloaded into each partition. The possible methods are as follows:
If the image can be downloaded into more than one partition, you are prompted for the partition number. Enter any of the following at the partition number prompt to obtain help:
Cisco 1600 and Cisco 3600 Copy TFTP Examples
A Cisco IOS image can be copied with or without its destination partition and filename specified in the initial command line. Both methods are described in this example section.
To copy a Cisco IOS image from a TFTP server to a Flash memory location that is specified in the initial command line, perform the following steps:
To copy a Cisco IOS image from a TFTP server to a Flash memory location that is not specified in the initial command line, unlike the previous example, perform the following steps:
Cisco 3600 Copy rcp Examples
To copy a Cisco IOS image from a remote rcp server to a Flash memory PC card inserted in PCMCIA slot 0, perform the following steps:
To copy a Cisco IOS image from a remote rcp server to a Flash partition, which is specified in the initial command line, perform the following steps:
On page 1-68 in the Configuration Fundamentals Configuration Guide, replace the "Clear the Configuration Information" section with the following new section:
Clear the Configuration Information
To clear the contents of your startup configuration, perform the following task in EXEC mode:
On the Cisco 7000 series and Cisco 7500 series, when you use the erase startup-config command, the router erases or deletes the configuration pointed to by CONFIG_FILE environment variable. If this variable points to NVRAM, the router erases NVRAM. If the CONFIG_FILE environment variable specifies a Flash memory device and configuration filename, the router deletes the configuration file. That is, the router marks the file as "deleted," rather than erasing it. This feature allows you to recover a "deleted" file. Refer to the "Manage Flash Files" section for more information on recovering deleted files.
To erase a saved configuration from a specific Flash device on a Cisco 1600 series, Cisco 3600 series, Cisco 7000 series, or Cisco 7500 series router, complete the following task in EXEC mode:
For the device argument, specify which Flash memory device that serves as the copy destination. For the Cisco 3600 series routers, your choices are internal Flash memory (flash) or a Flash memory PC card inserted in one of two PCMCIA slots (slot0 or slot1). The Cisco 1600 series routers support erasing files in the PC card only, which is specied with the flash device keyword. You must include a colon (:) after the device type that you specify, regardless of which platform you are using.
As with the erase startup-config command, when you erase or delete a specific file, the system marks the file as deleted, allowing you to later recover a "deleted" file. If you omit the device name, the Cisco IOS software uses the default device specified by the cd command.
If you attempt to erase or delete the configuration file specified by the CONFIG_FILE or BOOTLDR environment variable, the system prompts you to confirm the deletion. Also, if you attempt to erase or delete the last valid system image specified in the BOOT environment variable, the system prompts you to confirm the deletion.
The following Cisco 1600 series and Cisco 3600 series example, erases all the file contents in the second partition in internal Flash memory:
On page 1-73 in the "Loading System Images, Microcode, and Configuration Files" chapter in the Configuration Fundamentals Configuration Guide, replace the "Copy a Configuration File Directly to the Startup Configuration" section with the following new section:
Copy a Configuration File Directly to the Startup Configuration
You can copy a configuration file directly to your startup configuration without affecting the running configuration. System images are copied from TFTP servers, rcp servers, MOP servers, or Flash memory devices (such as on the Cisco 3600 series and Cisco 7500 series).
On the Cisco 7000 series and Cisco 7500 series, this task loads a configuration file directly into the location specified by the CONFIG_FILE environment variable without affecting the running configuration. If the CONFIG_FILE environment variable specifies NVRAM, the command functions as on all other platforms.
To copy a configuration file directly to the startup configuration, perform the following task in EXEC mode:
For the device argument, specify the Flash device from which you are copying the system image to the startup configuration. Possible copy destinations for the Cisco 3600 series router include the internal Flash memory (flash) or a Flash memory PC card inserted in one of two PCMCIA slots (slot0 or slot1). The Cisco 1600 series routers support copying files from the Flash memory PC card inserted in the PCMCIA slot, which is specified using the flash keyword. A colon (:) must be entered immediately following the specified device type, regardless of which platform you are using. If a filename follows the partition number, you must also enter a colon after the partition number.
The following Cisco 3600 series example copies the file IOS-UPGRADE-1 from the Flash memory PC card inserted in PCMCIA slot 0 to the router's startup configuration:
The following Cisco 3600 series example copies the file new-ios from the fourth partition in the Flash memory PC card inserted in PCMCIA slot 0 to the router's startup configuration:
On page 1-94 in the Configuration Fundamentals Configuration Guide, add the "Copy System Images Between Flash Memory Devices" section:
Copy System Images Between Flash Memory Devices
System images that exist on Flash memory devices, such as internal Flash memory and Flash memory PC cards inserted in PCMCIA slots, can be copied between devices on Cisco 3600 series routers. This is done to create backup copies of working configurations and easily duplicate configurations for other routers. See Figure 1.
Figure 1 : Copying Cisco IOS Images Between Flash Memory Devices for the Cisco 3600 Series
To copy a configuration file between Flash memory devices on a Cisco 3600 series router, perform the following task in EXEC mode:
Use the copy device:[partition-number:][filename] device:[partition-number:][filename] command to copy system images between Flash memory devices on a Cisco 3600 series router. Optional Flash devices include internal Flash memory (flash) and Flash memory PC cards inserted in one of two PCMCIA slots (slot0 or slot1). In place of the device arguments for the Cisco 3600 series, specify the source Flash memory device and the destination Flash memory device. The first occurrence of the device argument in the copy command is the source file identifier. The second occurrence of the device argument is the destination file identifier. You must enter a colon (:) after each specified device type. If a filename follows the partition number, you must also enter a colon after the partition number.
Copy Images Between Flash Devices Examples
To copy a Cisco IOS image between Flash devices that are resident on the same router, perform the following steps:
To copy a file from internal Flash memory to a PC card without specifying a partition number or filename in the initial command line, perform the following steps:
On page 1-58 in the Configuration Fundamentals Configuration Guide, replace the "Copy from a TFTP Server to Flash Memory" section with the following new section:
Copy from a TFTP Server to Flash Memory
To copy a system image from a Trivial File Transfer Protocol (TFTP) server to Flash memory, complete the following tasks:
The server system image copied to the Flash memories for Cisco 3000, Cisco 4000, and Cisco 7000 series, must be at least Software Version 9.1 or later. For Cisco 2500 series, the server system image must be at least Software Release 9.21 or later.
For the copy tftp flash, copy tftp device:, and copy tftp file_id commands, the router gives you the option of erasing the existing Flash memory before writing to it. If there is no free Flash memory available, or if the Flash memory has never been written to, the erase routine is required before new files can be copied. The system will inform you of these conditions and prompt you for a response. Note that on the Cisco 7000 series, the Flash memory is erased at the factory before shipment.
When you issue the copy tftp flash command, the system prompts you for the IP address or domain name of the TFTP server. This server can be another router serving ROM or Flash system software images. The system then prompts you for the filename of the software image to copy.
The device argument on the copy tftp device:[partition-number:][filename] command specifies a Flash device to serve as the destination of the copy operation. On the Cisco 3600 series, you can choose flash, slot0, or slot1 as the specified Flash memory device. The options slot0 and slot1 correspond to PCMCIA slots 0 and 1. Bootflash memory is not supported on the Cisco 3600 series routers. On the Cisco 1600 series, only the PC card is supported. This card is specified with the flash device keyword, and it's the only Flash memory that exists on the Cisco 1600 series. A colon (:) must be entered immediately following the specified device type, regardless of which platform you are using. If a filename follows the partition number, you must also enter a colon after the partition number.
The file_id argument of the copy tftp file_id command specifies a device and filename as the destination of the copy operation. You can omit the device, entering only copy tftp filename. When you omit the device, the system uses the default device specified by the cd command. On the Cisco 7000 series, you can choose flash: or slot0: as the Flash memory device. On the Cisco 7500 series, you can choose bootflash:, slot0:, or slot1: as the Flash memory device.
If you attempt to copy a file into Flash memory that is already there, a prompt informs you that a file with the same name already exists. This file is "deleted" when you copy the new file into Flash. The first copy of the file still resides within Flash memory, but it is rendered unusable in favor of the newest version, and is listed with the "deleted" tag when you use the show flash command. If you terminate the copy process, the newer file is marked "deleted" because the entire file was not copied and is not valid. In this case, the original file in Flash memory is valid and available to the system.
Copy TFTP Server Examples
To copy a Cisco IOS system image from a TFTP server to a Cisco 3600 series or Cisco 1600 series router, which does not have partitioned Flash memory, perform the following steps:
The following example shows how to copy a system image named gs7-k into the current Flash configuration in which a file named gs7-k already exists:
You can copy normal or compressed images to Flash memory. You can produce a compressed system image on any UNIX platform using the compress command. Refer to your UNIX platform's documentation for the exact usage of the compress command.
The series of pound signs (#) indicates that each Flash device is being cleared and initialized---one per device. Different platforms use different ways of indicating that Flash is being cleared. The exclamation point (!) indicates that the copy process is taking place. Each exclamation point (!) indicates that ten packets have been transferred successfully. The series of "V" characters indicates that a checksum is being calculated. An "O" indicates an out-of-order packet. A period (.) indicates a timeout. The last line in the sample configuration indicates that the copy is successful.
On page 1-61 in the Configuration Fundamentals Configuration Guide, replace the "Copy from an rcp Server to Flash Memory" section with the following new section:
Copy from an rcp Server to Flash Memory
To copy a system image from an rcp server to Flash memory, complete the following tasks:
The copy command automatically displays the Flash memory directory, including the amount of free space. On Cisco 2500 series, Cisco 3000 series, and Cisco 4000 series, if the file being downloaded to Flash memory is an uncompressed system image, the copy command automatically determines the size of the file being downloaded and validates it with the space available in Flash memory.
The server system image copied to the Flash memories must be Cisco IOS Release 10.2 or later.
When you issue the copy rcp flash, copy rcp device:[partition-number:][filename], or copy rcp file_id command, the system prompts you for the IP address or domain name of the server. This server can be another router serving Flash system software images. The system then prompts you for the filename of the software image to copy. With the copy rcp flash command, the system also prompts you to name the system image file that will reside in Flash memory once the copy is complete. You can use the filename of the source file, or you can choose another name. For the device argument on the Cisco 3600 series, you can specify internal Flash memory (flash) or a Flash memory PC card inserted in one of two PCMCIA slots (slot0 or slot1). On the Cisco 1600 series, the only supported device type is the Flash memory PC card, which is specified by the flash keyword. This card is the only Flash memory that exists on the Cisco 1600 series. A colon (:) must be entered immediately following the specified device type, regardless of which platform you are using.
When free space is available in Flash memory, you are given the option of erasing the existing Flash memory before writing onto it. If no free Flash memory space is available, or if the Flash memory has never been written to, the erase routine is required before new files can be copied. The system informs you of these conditions and prompts you for a response. If you accept the erasure, the system prompts you again to confirm before erasing. Note that the Flash memory is erased at the factory before shipment.
If you attempt to copy a file into Flash memory that is already there, a prompt informs you that a file with the same name already exists. The older file is "deleted" when you copy the new file into Flash. The first copy of the file still resides within Flash memory, but it is rendered unusable in favor of the newest version, and is listed with the "deleted" tag when you use the show flash command. If you terminate the copy process, the newer file is marked "deleted" because the entire file was not copied. In this case, the original file in Flash memory is valid and available to the system.
Copy rcp Server Examples
To copy a Cisco IOS image from a rcp server to a Flash memory device on a Cisco 1600 series or Cisco 3600 series router, perform the following steps:
In this next Cisco 3600 series example, the destination partition number and filename in PCMCIA slot 0 are specified in the initial command line. In the previous example, the partition number and filename was provided during the copy operation.
The exclamation point (!) indicates that the copy process is taking place. Each exclamation point (!) indicates that ten packets have been transferred successfully.
On page 1-63 in the Configuration Fundamentals Configuration Guide, replace the "Copy from a MOP Server to Flash Memory" section with the following new section:
Copy from a MOP Server to Flash Memory
On all platforms except the Cisco 7500 series, you can copy a system image from a Maintenance Operation Protocol (MOP) server to Flash memory. To do so, perform the following task in EXEC mode:
In place of the device argument, specify the destination Flash device. On the Cisco 3600 series routers, you can specify the internal Flash memory (flash) or a Flash memory PC card inserted in one of two PCMCIA slots (slot0 or slot1). For the Cisco 1600 series, only the Flash memory PC card (flash) is supported. This card is the only Flash memory device that exists on the Cisco 1600 series routers. You must enter a colon (:) after the specified device type, regardless of the platform you are using. If a filename follows the partition number, you must also enter a colon after the partition number.
The following example shows sample output from the copy mop flash command. In this example, the system image routerimage, which already exists in Flash memory, is copied to Flash memory, and there is enough memory to copy the file without erasing any existing files.
On page 1-88 in the Configuration Fundamentals Configuration Guide, replace the "Copy from Flash Memory to a TFTP Server" section with the following new section:
Copy from Flash Memory to a TFTP Server
You can copy a system image to a TFTP network server. In some implementations of TFTP, you must first create a "dummy" file on the TFTP server and give it read, write, and execute permissions before copying a file over it. Refer to your TFTP documentation for more information.
To copy a system image to a TFTP network server, perform the following task in EXEC mode:
In place of the device argument, specify the Flash device that contains the source file. On the Cisco 3600 series routers, you can specify copying from internal Flash memory (flash) or a Flash memory PC card inserted in one of two PCMCIA slots (slot0 or slot1). For the Cisco 1600 series routers, only a PC card is supported, which is specified using the flash device keyword. This card is the only Flash memory that exists on the Cisco 1600 series. For each platform, you must enter a colon (:) after the specified device type. If a filename follows the partition number, you must also enter a colon after the partition number.
Copy Flash to TFTP Server Examples
To copy a system image from a PC card, which is inserted in a Cisco 3600 series router, to a remote TFTP server, perform the following steps:
In this next Cisco 3600 series example, the partition number is specified at the initial command line. Use you own partition numbers and filenames where appropriate.
The exclamation point (!) indicates that the copy process is taking place. Each exclamation point (!) indicates that ten packets have been transferred successfully. To stop the copy process, press Ctrl-^. Refer to the Troubleshooting Internetworking Systems publication for procedures on how to resolve Flash memory problems.
The following example uses the show flash [device:] command on a Cisco 7500 series to display the name of the system image file to copy. In the example, the Flash memory device containing the system image is the second PCMCIA slot. The file to copy is test. The example uses the copy file_id tftp command, to copy test to a TFTP server.
The exclamation point (!) indicates that the copy process is taking place. Each exclamation point (!) indicates that ten packets have been transferred successfully.
This procedure on the Cisco 7000 series also requires changing the processor's configuration register. Refer to the "Modify the Configuration Register Boot Field" section for instructions.
On page 1-90 in the Configuration Fundamentals Configuration Guide, replace the "Copy from Flash Memory to an rcp Server" section with the following new section:
Copy from Flash Memory to an rcp Server
You can also copy a system image from Flash memory to an rcp network server.
The rcp protocol requires that a client send the remote username on each rcp request to the server. When you copy an image from Flash memory to a network server using rcp, the Cisco IOS software sends the remote username associated with the current terminal process, if that name is valid. If the remote username is invalid, the software uses the router host name as both the remote and local usernames.
You can configure a different remote username to be sent to the server. If the network server has a directory structure, as do UNIX systems, the rcp protocol implementation writes the system image relative to the directory associated with the remote username on the network server.
For the rcp command to execute properly, an account must be defined on the destination server for the remote username.
To stop the copy process, press Ctrl-^. Refer to the Troubleshooting Internetworking Systems publication for procedures on how to resolve Flash memory problems.
If you copy the system image to a personal computer used as a file server, the computer must support the rcp protocol.
To copy the system image from Flash memory to a network server, perform the following tasks:
In place of the device argument, specify the Flash device that contains the source image file. For the Cisco 3600 series, you can specify copying a file from internal Flash memory (flash) or a Flash memory PC card inserted in one of two PCMCIA slots (slot0 or slot1). For the Cisco 1600 series, only a PC card is supported, which is specified with the flash device keyword. This card is the only Flash memory that exists on the Cisco 1600 series. You must enter a colon (:) after the specified device type, regardless of which platform you are using. If a filename follows the partition number, you must also enter a colon after the partition number.
To copy a file from a PC card inserted in the PCMCIA slot 1 on a Cisco 3600 series router, perform the following steps:
To copy a system image from a Cisco 3600 series Flash PC card to a remote rcp server, by specifying the source partition number and filename in the initial command line, perform the following steps:
On page I-107 of the Configuration Fundamentals Configuration Guide, replace the "Configure a Flash Partition as a TFTP Server" section with the following section:
Configure a Flash Partition as a TFTP Server
To configure a Flash partition as a TFTP server, perform one of the following tasks in global configuration mode:
In place of the device argument specify the Flash device that will be used as a TFTP server. On the Cisco 3600 series, your options include internal Flash memory (flash) or a Flash memory PC card inserted in one of two PCMCIA slots (slot0 or slot1). On the Cisco 1600 series, only a PC card is supported, which is specified by the flash device keyword. This card is the only Flash memory that exists on the Cisco 1600 series. A colon (:) must be entered immediately following the specified device type, regardless of which platform you are using. If a filename follows the partition number, you must also enter a colon after the partition number.
Once you have specified TFTP server operation, exit configuration mode and save the configuration information to your startup configuration.
On page 1-76 of the Configuration Fundamentals Configuration Guide, replace the "Load from Flash Memory" section with the following new section:
In the Cisco 3600 series, you can load a system image from internal Flash memory or a Flash memory PC card inserted in one of two PCMCIA slots.
In the Cisco 1600 series, system images are loaded from a Flash memory PC card, which is inserted in a PCMCIA slot. This card is the only Flash memory that exists on the Cisco 1600 series.
In the Cisco 7000 series, Flash memory is located on the RP card or a Flash memory PC card inserted in the PCMCIA slot. In the Cisco 7500 series, Flash memory is located on the RSP card or on a Flash memory PC card inserted in one of the PCMCIA slots (slot 0 or slot 1) of the RSP card. You can store or boot software images in Flash memory as necessary. Flash memory can reduce the effects of network failure by reducing dependency on files that can only be accessed over the network.
On page I-156 of the Configuration Fundamentals Configuration Guide, replace the "Manually Load a System Image from the ROM Monitor" section with the following new section:
Manually Load a System Image from the ROM Monitor
If your router does not find a valid system image or if its configuration file is corrupted at startup, the configuration register is set to enter ROM monitor mode and the system enters ROM monitor mode. Depending on which platform you are using, you can use the ROM monitor to manually load a system image from the following devices:
The Cisco 3600 series does not use a dedicated boot helper image such as rxboot that many other routers use to assist with the boot process. Instead the first system image in Flash memory is identified as the default boot helper. However, this default can be overriden by setting the BOOTLDR ROM monitor environment variable to point to another system image. The boot helper image is invoked any time the ROM monitor does not recognize a valid Flash device (for example, flash:, slot0:, and slot1:) specified by the boot command, whether the boot process is performed manually or automatically.
For the Cisco 3600 series, no autobooting occurs and your configuration session is passed over to ROM monitor mode if the boot bits are set to 0 in the configuration register. If the boot bits are set to 1, the ROM monitor automatically boots the default boot helper image, which is the first file in Flash memory. In this case, the BOOTLDR setting is ignored. If this boot attempt fails, the system attempts to boot the first file in the Flash memory PC card inserted in slot 0. Finally, if the boot bits are set within the range of 2 to 15, the ROM monitor executes the boot commands set by the boot environment variable. This environmental variable is set by the boot system command in the Cisco IOS software. If a boot attempt fails, the ROM monitor tries to boot the images in the order they are presented in the environment variable. If all attempts to boot images specified in the boot process fail, the ROM monitor resorts to booting the first image sequentially from the following Flash devices: internal Flash memory, slot 0, and slot 1.
To manually boot from Flash memory, complete the following tasks:
Replace the device argument on the Cisco 3600 series with Flash device that you want to boot from. Your choices are internal Flash memory (flash) or a Flash memory PC card inserted in a PCMCIA slot (slot0 or slot1). A colon (:) must be entered immediately following the specified device type, regardless of which platform you are using. If a filename follows the partition number, you must also enter a colon after the partition number.
Cisco 7000 Series and Cisco 7500 Series Examples In the following example, a router is manually booted from Flash memory. Because the optional filename argument is absent, the first file in Flash memory is loaded.
In the following example, the boot flash command is used with the filename gs7-k---the name of the file that is loaded:
Cisco 3600 Series Examples
The following example enables the ROM monitor to boot the first file in the first partition of internal Flash memory:
This example enables the ROM monitor to boot the first file in the first partition of a Flash memory PC card inserted in the PCMCIA slot 0:
The following example enables the ROM monitor to boot the first file in the second partition of a Flash memory PC card inserted in the PCMCIA slot 0:
In this example, the ROM monitor boots the file named imagename from the third partition of a Flash memory PC card inserted in the PCMCIA slot 0:
The following command normally boots the first image in Flash memory. However, because a valid device type is not specified for the ROM monitor (for example, flash:, slot0:, or slot1:), the boothelper is incurred to boot the system image.
Manually Boot from a Network File
To manually boot from a network file, complete the following tasks in EXEC mode:
In the following example, a router is manually booted from the network file network1:
In the following Cisco 3600 series example, the router netboots the file imagename. To netboot this file, the router invokes the boot helper image.
On page 1-80 of the Configuration Fundamentals Configuration Guide, replace the "Configure the Router to Automatically Boot from an Image in Flash Memory" section with the following new section:
Configure the Router to Automatically Boot from an Image in Flash Memory
To configure a router (including the Cisco 1600 series, Cisco 3000 series, Cisco 3600 series, Cisco 4000 series, Cisco 7000 series, and Cisco 7500 series routers) to boot from an image in Flash memory automatically, perform the following tasks:
If you enter more than one image filename, the router tries them in the order entered.
If a filename already appears in the configuration file and you want to specify a new filename, remove the existing filename with the no boot system flash filename command.
Unlike other routers, the Cisco 3600 series routers do not support booting a Cisco IOS system image from bootflash memory. The possible boot variables correspond to internal Flash memory and Flash memory PC cards inserted in PCMCIA slots 0 or slot 1.
On page 1-111 of the Configuration Fundamentals Configuration Guide, add the following new section:
Download a System Image Using Xmodem or Ymodem to a Cisco 3600 or Cisco 1600
If each system image loaded in the router is somehow damaged or erased and you do not have access to a TFTP server, copy a new Cisco IOS image from a local or remote computer (such as a PC, UNIX, or Macintosh) using the Xmodem or Ymodem protocols. The Cisco 3600 series routers do not support XBOOT functionality, which is a disaster recovery technique for the Cisco IOS software. The Xmodem and Ymodem protocols are used for transferring files and are included in the following applications: Windows 3.1 (TERMINAL.EXE), Windows 95 (HyperTerminal), Windows NT 3.5x (TERMINAL.EXE), Windows NT 4.0 (HyperTerminal), and Linux UNIX freeware (minicom).
Perform this file transfer using the Cisco IOS software or the ROM monitor software. The Cisco 1600 series routers support transferring files from the ROM monitor only. If all system images on the router are damaged or erased, you must download a new image using the ROM monitor software. From the Cisco IOS software, the AUX port, which supports hardware flow control, is recommended for image transfers from a remote or local PC. From the ROM monitor, the console port is used for image transfers from a remote or local PC. With the Cisco IOS software, the Xmodem or Ymodem file transfer occurs on the same port (AUX or console) from which you issue the copy xmodem or copy ymodem command. For example, issuing the copy xmodem command on the console port cannot initiate a file transfer through the AUX port. The command must be entered on the AUX port to initiate a transfer through the AUX port. See Figure 2.
Figure 2 : Copy a System Image to a Cisco 3600 or Cisco 1600 Router with Xmodem or Ymodem
Xmodem and Ymodem downloads are slow. Because of this, the preferred method for downloading images quickly over the network is with the copy tftp device: command. If the erase option is specified, all existing files in the Flash memory are replaced with the newer Flash image at the successful completion of the download operation.
To copy a Cisco IOS image from a PC to a router using the Xmodem protocol, perform one of the following EXEC or ROM monitor commands:
Use the copy xmodem flash EXEC command and xmodem ROM monitor command to copy an image if you do not have access to a TFTP or rcp server. Otherwise, use the copy tftp flash command to download a new Cisco IOS software image to your router.
The PC from which you will transfer the Cisco IOS image must be running terminal emulation software and the Xmodem or Ymodem protocol.
Refer to the "Cisco IOS Xmodem Example" and the "ROM Monitor Xmodem Example" in the section "I/O Memory Example" for an example configuration.
Cisco IOS Xmodem Example To transfer a Cisco IOS image from a remote PC running terminal emulation software and Xmodem software, perform the following steps:
To transfer a Cisco IOS image from a local PC, repeat the previous configuration using the AUX port. No modems are used in this file transfer. The AUX speed configured on the router must match the transfer speed configured on the local PC, which is configured within the terminal emulation software.
ROM Monitor Xmodem Example From within the ROM monitor mode, you can copy a new Cisco IOS image from a remote PC to a Cisco 3600 series or Cisco 1600 series router by performing these steps.
In addition to downloading an image from a remote PC, you can download an image from a local PC by following these steps:
On page I-327 of the Configuration Fundamentals Configuration Guide, add the following new section:
Reallocate Packet Memory and Processor Memory
To allocate different percentages of DRAM to the packet memory and processor memory, perform the following task in global configuration mode:
View your current memory level by entering the show memory command. If the value appearing in the Free(b) column in the I/O row is low, you need to allocate more packet memory. To display statistics for the buffers pool, use the show buffers command. If you are dropping packets because you have too few buffers and you already adjusted the buffers using the buffers configuration command, increase the packet memory percentage for more memory.
The valid packet memory percentage values are 25 (the default), 30, 40, and 50. The packet memory size will be the specified percentage of the total memory size, rounded down to the closest MB. The remaining memory will be the processor memory. The memory-size iomem command does not take effect until you save it to NVRAM using the copy running-config startup-config EXEC command and reload the router. However, when the command is initially entered at the command line, the Cisco IOS software checks whether the new memory redistribution will cause the currently running image to have insufficient memory. If this is the case, the following message appears:
When you enter the reload command to run a new image, the system recalculates the new processor and packet memory split. If the I/O memory percentage is configured too high and leaves insufficient processor DRAM for loading the image, the system automatically changes the percentages to one of the two alternative settings or to the default setting to load the image.
If the default, which has the smallest percentage of I/O memory, is still not sufficient for the image to run, then you do not have enough DRAM to run that particular subset image. The system will not repartition the memory if you do not configure the percentages to something other than the default.
I/O Memory Example Follow these steps to allocate 40% of the available DRAM to packet memory and the remaining 60% to processor memory. These values can fluctuate according to your configuration needs.
Update for the Cisco AS5200 Universal Access Server
This section contains updated documentation that includes new or modified Cisco IOS commands for the Cisco AS5200 access server.
On page I-185 in the Configuration Fundamentals Configuration Guide, add the following new section:
Configure Channelized T1 on the Cisco AS5200
The Cisco AS5200 Universal Access Server is an ISDN-capable access server that can make and receive ISDN and analog calls from remote clients needing access to network resources. The Cisco AS5200 has two T1 controllers, which can be configured individually.
On a Cisco AS5200, you can allocate the 24 available channels for channelized T1 in the following four ways:
To configure the T1 controllers in the Cisco AS5200, perform the tasks in the following sections:
Configure the T1 Controllers to Make and Receive Calls
Set parameters for a T1 controller to make and receive calls. To do so, perform the following steps beginning in global configuration mode:
Repeat Steps 1 through 7 to configure T1 controller 1, making sure in Step 5 to select T1 controller 1's line as the secondary clock source. You do not have to configure the timeslots in the same way on the two T1 controllers. You can configure the timeslots on this second controller as needed, no matter how you configured the timeslots in T1 controller 0.
Configure the ISDN D-Channel Serial Interfaces
Once you create the interfaces,two corresponding D channel serial interfaces are automatically created. Serial interface 0:23 is the D channel for T1 controller 0, and serial interface 1:23 is the D channel for T1 controller 1. You must configure each serial interface to receive and make calls.
To configure an ISDN D-Channel serial interface, perform the following steps beginning in global configuration mode:
Repeat Steps 1 through 3 for serial interface 1:23, which is the D channel on the second T1 controller.
On page I-292 of the Configuration Fundamentals Configuration Guide add the following new section to the "Channelized T1 Controller and Interface Examples" section:
Allocating Channels for Channelized T1
You can configure the 24 channels of a channelized T1 on a Cisco AS5200 to support ISDN PRI, robbed bit signaling, channel grouping, or a combination of all three.
Allocating all Channels for ISDN PRI
The following example shows you how to configure all 24 channels to support ISDN PRI on a Cisco AS5200:
Allocating all Channels for Robbed Bit Signaling Feature Group B
The following example shows you how to configure all 24 channels to support robbed bit signaling feature group b on a Cisco AS5200:
Allocating all Channels to Server as One Channel Group
The following example shows you how to configure all 24 channels as one channel group on a Cisco AS5200:
Mixing and Matching Channels
The following example shows you how to configure all 24 channels to support a combination of ISDN PRI, robbed bit signaling, and channel grouping. The range of timeslots that you allocate must match the timeslot allocations that your central office chooses to use. This is a rare configuration due to the complexity of aligning the correct range of timeslots on both ends of the connection.
The following configuration creates serial interfaces 0 to 9, which correspond to ISDN PRI timeslots 1 to 10 (shown as serial 1:0 through serial 1:9). The serial line 1:23 is the D channel, which carries the analog signal bits that dial a modem's phone number and determine if a modem is busy or available. The D channel is automatically created and assigned to timeslot 24.
Channelized T1 data is transmitted over timeslots 11 through 16, which are assigned to serial interface 1 and virtual channel group 11 (shown as serial 1:11) in the next configuration example. However, notice how the earlier attempt to configure channel group 1 is denied because timeslot 1 is used by the previous ISDN PRI group configuration:
The channel associated signal E&M feature group b is configured on virtual signal group 17 for the remaining 17 to 23 timeslots, which are used for incoming and outgoing analog calls. There is no specific interface, such as the serial interface show in the earlier examples, that corresponds to the timeslot range. Notice how channel number 12 can not be used to configure these timeslots, because it is used in the previously configured channel group range, which is timeslots 11 to 16.
In the Configuration Fundamentals Configuration Guide, Replace the "Configure Channelized E1" section on page I-177 of the "Configuring Interfaces" chapter with the following section:
Support for channelized E1 is provided on the following platforms:
Use the show controllers e1 EXEC command to display current E1 status. This command provides a report for each physical interface configured to support channelized E1.
Channelized E1 supports the following WAN protocols:
When a channelized E1 adapter is used for ISDN PRI, it can support DDR; when it is not used for ISDN PRI, it does not support DDR. Refer to the "Configuring ISDN" chapter in the Wide-Area Networking Configuration Guide for more information.
Using channelized E1 controller and serial interface configuration commands, you can perform the tasks in the following sections to configure channelized E1:
See the end of this chapter for Interface Configuration Examples.
To configure the E1 physical characteristics, you first define the location of the controller in the router. A Cisco 7000 router can have up to four MIP and eight CX-MIP-CE1 interfaces. A Cisco 7010 router can have up to three MIP and six CX-MIP-CE1 interfaces. The Cisco 4000 series routers can support up to three network processor module (NPM) cards, each with one interface when running it as a channelized interface card. However, when the card is used to run ISDN PRI, only one NPM can be used in the Cisco 4000 and two NPMs can be used in the Cisco 4500.
The Cisco AS5200 series routers can support one network processor module (NPM); each module supports two E1 physical interfaces.
Perform the following task in global configuration mode to define the E1 controller and to enter controller configuration mode:
Perform the following task in controller configuration mode to define the line code as either alternate mark inversion (AMI) or HDB3:
Define the Framing Characteristics
Perform the following task in controller configuration mode to define the framing characteristics as either CRC4 or no-CRC4, or as the version of E1 framing used in Australia only:
The clock source normally comes from the E1 line rather than from the router interface, but when you connect two routers back-to-back for testing purposes, one device supplies an internal clock source.
To define the clock source, perform the following task in controller configuration mode:
For the Cisco AS5200, you must define the clock source to enable timing on each E1 controller. Configure one E1 controller with the clock source line primary command. Configure the other E1 controller with the clock source line secondary command. Either controller can be used for a primary clock.
You can define up to 30 channel groups for each E1 physical interface. You must define the time slots that belong with each channel group. Channel groups are numbered 0 to 30, and time slots are numbered 1 to 31. Perform the following task in controller configuration mode to define the channel groups and time slots:
Working with your local service provider, you can create channel-groups with from 1 to 31 timeslots. These timeslots can be in any order, contiguous or noncontiguous. Channel-group speeds can be 48 kbps, 56 kbps, or 64 kbps; the default is 64 kbps if the speed is not specified. The speed you choose must match the speed specified by your service provider.
Defining a channel group creates a serial interface; defining multiple channel groups creates an equal number of serial interfaces that you can configure independently. The channel group numbers for each E1 controller can be arbitrarily assigned.
Configure the Channelized E1 Channel Groups
E1 channel groups support local loopback. You can enable local loopback for specified individual channel groups with the loopback local command. Local loopback loops the entire specified channel group both toward the line and toward the router.
E1 channel groups do not respond to any remote loopback codes; you cannot remotely loop an E1 channel group.
In the "Configuring Modems" section on page II-20 in the "Configuring Terminal Lines and Modem Support" chapter of the Access Services Configuration Guide, replace the "Monitor Modems and Enable Modem Events" section with the following section:
Monitor Modems and Enable Modem Events
You can view various modem statistics and configure modem events using the Cisco IOS software with the Cisco AS5200.
To show modem performance statistics, perform the following tasks in EXEC mode:
To create an asynchronous interface and use it as a group interface associated with a group of modems, refer to the "Configuring Interfaces" chapter in the Configuration Fundamentals Configuration Guide.
Update to the Command References
This section documents new and modified commands for the Configuration Fundamentals Command Reference and Access Services Command Reference. Refer to the Cisco IOS Release 11.1 configuration guide and command reference publications for additional configuration information.
This section presents commands alphabetically, however, the following list identifies the document and chapter to which they belong:
To boot the router manually, use the boot ROM monitor command.
Syntax Description
Default
If you enter the boot command and press Return, the router boots from ROM by default. For the Cisco 3600 series, the boot command boots the first image in Flash memory as the default.
If you enter the boot flash command without a filename, the first valid file in Flash memory is loaded.This is also true for the the Cisco 3600 series when the boot flash: command is configured.
For other defaults, see the Syntax Description section.
Command Mode
Usage Guidelines
Use this command only when your router cannot find the configuration information needed in nonvolatile random-access memory (NVRAM). To get to the ROM monitor prompt (>), enter the reload EXEC command, and then press the Break key during the first 60 seconds of startup, or change the boot bits in the configuration register to zero, for manual booting, and then issue the reload command.
Refer to the Cisco 7000 Hardware Installation and Maintenance publication for the correct jumper settings for the Cisco 7000 series.
Examples
In the following example, a router is manually booted from ROM:
The following Cisco 3600 series example shows the ROM monitor booting the first file in the first partition of internal Flash memory:
This example boots the first image file appearing in the first partition of a Flash memory PC card inserted in PCMCIA slot 0 on a Cisco 3600 series router:
The following example shows the boot flash command without the filename argument.The first valid file in internal Flash memory is loaded.
In the following example, the boot flash command is used with the filename gs7-k. That is the file that will be loaded.
In the following example, the boot flash flash command boots the relocatable image file igs-bpx-l from partition 2 in Flash memory:
Related Command
Syntax Description
Default If you do not specify a system image file with the boot system command, the router uses the configuration register settings to determine the default system image filename for booting from a network server. The router forms the default boot filename by starting with the word cisco and then appending the octal equivalent of the boot field number in the configuration register, followed by a hyphen (-) and the processor type name (cisconn-cpu). See the appropriate hardware installation guide for details on the configuration register and default filename. See also the command config-register. See also the "Syntax Description" section preceding this section.
On the Cisco 3600 series, Cisco 7000 series, Cisco 7200 series, and Cisco 7500 series, if you omit a keyword (flash, mop, rom, rcp, or tftp) from the boot system command, the system defaults to booting from a system image stored on a TFTP server.
Command Mode
Global configuration
Usage Guidelines
For this command to work, the config-register command must be set properly.
Enter several boot system commands to provide a fail-safe method for booting your router. The router stores and executes the boot system commands in the order in which you enter them in the configuration file. If you enter multiple boot commands of the same type---for example, if you enter two commands that instruct the router to boot from different network servers---then the router tries them in the order in which they appear in the configuration file. Except on the Cisco 3600 series routers, use the boot system rom command to specify use of the ROM system image as a backup to other boot commands in the configuration.
Each time you write a new software image to Flash memory, you must delete the existing filename in the configuration file with the no boot system flash filename command. Then add a new line in the configuration file with the boot system flash filename command.
You can boot the router from a compressed image on a network server. When a network server boots software, both the image being booted and the running image must fit into memory. Use compressed images to ensure that enough memory is available to boot the router. You can compress a software image on any UNIX platform using the compress command. Refer to your UNIX platform's documentation for the exact usage of the compress command. (You can also uncompress a system image with the UNIX uncompress command.)
The rcp protocol requires that a client send the remote username in an rcp request to a server. When the router executes the boot system rcp command, the Cisco IOS software sends the host name as the both the remote and local usernames by default. The rcp software searches for the system image to boot from the remote server relative to the directory of the remote username (if the server has a directory structure as UNIX systems do, for example).
Table 6 : Summary of Valid Boot System Commands Supported on Different Platforms
For the Cisco 3600 series, valid devices are flash:, slot0:, and slot1:. Since bootflash memory is not included in the Cisco 3600 series, booting from bootflash memory is not supported.
For the Cisco 7200 series and Cisco 7500 series, valid devices are bootflash, slot0, slot1, and tftp. On the Cisco 7200 series and Cisco 7500 series, the following forms of the boot system command specify a list of bootable images in the BOOT environment variable.
If an entry in the BOOT environment variable list does not specify a device, the router assumes the device is tftp. When tftp is the device, the router first loads the rxboot or boothelper image to boot the system image file from a network server. No rxboot image exists on the Cisco 3600 series routers. If an entry in the BOOT environment variable list specifies an invalid device, the router skips that entry. To view the contents of the BOOT environment variable, use the show boot command.
To remove a single entry from the bootable image list, use the no form of a specific command. For example, to remove the entry that specifies a bootable image on a Flash memory card inserted in the second slot of the RSP card, use the no boot system flash slot1:[filename] command. All other entries in the list remain.
To eliminate all entries in the bootable image list, use the no boot system command. Issuing this command sets the BOOT environment variable to a null string, wiping out all entries. At this point, you can redefine the list of bootable images using the previous boot system commands. Remember to save your changes to your startup configuration by issuing the copy running-config startup-config command.
Examples
The following example specifies the file New-IOS-image as the system image that the Cisco 3600 series routers load at startup. This file is located in the fourth partition of the Flash memory PC card inserted in PCMCIA slot 0.
The following example illustrates a list specifying two possible internetwork locations for a system image, with the ROM software being used as a backup. The boot system rom command does not apply to the Cisco 3600 series routers.
The following example boots the system boot relocatable image file igs-bpx-l from partition 2 of the internal Flash memory device:
The following example instructs the router to boot from an image located on the Flash memory PC card inserted in slot 0 of the Cisco 7000 RP card, Cisco 7200 NPE card, or the Cisco 7500 series RSP card:
Related Commands
config-register
Syntax Description
Default
Channel associated signaling is disabled.
Command Mode
Controller configuration
Usage Guidelines
Use this command to enable an Cisco AS5200 modem to receive and send incoming and outgoing analog calls through each T1 controller that is configured for a channelized T1 line, which has 24 possible channels.
Switched 56 digital calls are not supported in this feature.
Example
The following example configures all 24 channels with ear and mouth channel signaling with feature group b support on a Cisco AS5200:
Syntax Description
Default
T1 line clocking is taken from the T1 line for the Cisco 7000 family, and Cisco 4000 series routers.
Primary TDM clock source is taken from the T0 or E0 controller on the Cisco AS5200.
Secondary TDM clock source is taken from the T1 or E1 controller on the Cisco AS5200.
Command Mode
Controller configuration
Usage Guidelines
Use this command for MIP configuration for the Cisco 7000 family , and for NPM configuration for the Cisco 4000 series routers.
For the Cisco 7000 family, and Cisco 4000, this command is used in configurations where the interfaces are connected back-to-back, rather than to a T1 line, and one of the interfaces must provide a clocking signal. When the interface is connected to a channelized T1 line, this command need never be used.
To use the clocking coming in from a T1 or E1 line for the Cisco AS5200, configure the clock source line primary command on the controller that has the most reliable clocking. Configure the clock source line secondary command on the controller that has the next best known clocking. With this configuration, the primary line clocking is backed up to the secondary line if the primary clocking shuts down.
Example
The following example enables internal clocking:
The following example configures the Cisco AS5200 to use the T0 controller as the primary clocking source and the T1 controller as the secondary clocking source:
The following example configures the Cisco AS5200 to use the E0 controller as the primary clocking source and the E1 controller as the secondary clocking source:
Related Commands
framing
Syntax Description
Default
If you omit the source or destination device, the Cisco IOS software uses the default device specified by the cd command. If you omit the destination filename, the software uses the source filename.
Command Mode
EXEC
Usage Guidelines
Use the copy command with the Cisco 1600 series, Cisco 3600 series, Cisco 7000 series, Cisco 7200 series, and Cisco 7500 series.
Depending on which Cisco 3600 series device type you are using, you can identify the available device partitions by entering the show flash: command, show slot0: command, or the show slot1: command. By default, the Cisco IOS software uses the same source filename for the destination filename. However, you can assign a new filename during the copy operation.
When the destination is specified by the CONFIG_FILE or BOOTLDR environment variable, the router prompts you for confirmation before proceeding with the copy. When the destination is the only valid image in the BOOT environment variable, the router also prompts you for confirmation before proceeding with the copy.
The CONFIG_FILE environment variable specifies the configuration used during router initialization. The BOOTLDR environment variable specifies the Flash device and filename containing the rxboot image that ROM uses for booting. The BOOT environment variable specifies a list of bootable images on various devices. To view the contents of environment variables, use the show boot command. To modify the CONFIG_FILE environment variable, use the boot config command. To modify the BOOTLDR environment variable use the boot bootldr command. To modify the BOOT environment variable, use the boot system command. To save your modifications, use the copy running-config startup-config command.
If you do not specify a source or destination device, the router uses the default device specified by the cd command.
High System Availability (HSA) refers to how quickly your router returns to an operational status after a failure occurs. On the Cisco 7507 and Cisco 7513, you can install two RSP cards in a single router to improve system availability.
Examples for the Cisco 3600 Series
To copy files from a Flash device such as PCMCIA slot 1 to a TFTP server refer to the following configuration examples.
The following example copies the file c3600-i-mz from partition 1 of the Flash memory PC card inserted in PCMCIA slot 0 to the filename c3700-i-mz on a TFTP server, which has the IP address 171.69.1.129. Because the PC card inserted in PCMCIA slot 0 has multiple partitions and a partition number, and filename are not specified in the initital command line, you must provide this information during the interactive copy operation.
The Cisco IOS software prompts you for all information that is not specified in the initial command line. After you specify the source filename, the destination file is confirmed, verified, and copied.
The next Cisco 3600 series example copies the file IOS-UPGRADE-1 from the Flash memory PC card inserted in PCMCIA slot 0 to the running configuration on the same Cisco 3600 series router.
The following example copies the file running-config from the internal Flash memory's first partition to the the Flash memory PC card inserted in PCMCIA slot 1. When the new running-config file is transferred, a verify checksum is automatically performed and the file's copying time is displayed, which is 30 seconds as shown at the end of the example.
Examples for the Cisco 7000 Series, Cisco 7200 Series, and Cisco 7500 Series
The following example copies the router-config1 file from the internal Flash memory of a Cisco 7200 series or Cisco 7500 series router to the router-backupconfig file on the Flash memory card inserted in the first slot:
In the following example, the router copies the router-image file from the Flash memory card inserted in the slot 0 on a Cisco 7000 series, Cisco 7200 series, or Cisco 7500 series to the startup configuration:
The following example copies the NVRAM configuration file to the router-backupconfig file on the Flash memory card inserted in slot 0:
The following example copies the router-image file from the Flash memory card inserted in slot 1 of the master RSP card of a Cisco 7513 to slot 0 of the slave RSP card in the same Cisco 7513:
Related Commands
boot config
To copy a file from a MOP server to the router, use one of the following the copy mop EXEC commands:
Syntax Description
Command Mode
EXEC
Usage Guidelines
The Cisco 7500 series does not support the copy mop command.
Use the copy mop bootflash command to copy a bootstrap image from a MOP server to the internal Flash memory on a Cisco 4500 series router. The router prompts for the name of the image file. It provides an option to erase the existing boot image in Flash before writing the new image into Flash. If no free space is available, or if files have never been written to Flash memory, you must erase Flash memory before copying the MOP image.
You do not need to specify the address of a MOP server. The Cisco IOS software automatically solicits a MOP boot server for the specified file by sending a multicast file-request message.
The copying process takes several minutes; the actual time differs from network to network.
Use the copy mop flash command to copy a system image from a MOP server to internal Flash memory. MOP must be enabled on the relevant interfaces before you can use this command.
The router prompts for the MOP filename. It provides an option to erase existing Flash memory before writing onto it. The entire copying process takes several minutes and will differ from network to network.
Examples
If the partition is read-only and has dual Flash bank support in boot ROMs, the session continues as follows:
The file will be copied into the partition given by the user earlier:
If the partition is read-write, the session continues as follows:
The file will be copied into the partition given by the user earlier:
The following example shows how to use the copy mop bootflash command to copy the bootstrap image file1:
Related Commands
boot config
To copy a file from a network server to the router or to another destination using rcp, use one of the following copy rcp EXEC commands. The copy rcp running-config command replaces the configure network command. The copy rcp startup-config command replaces the configure overwrite-network command.
Syntax Description
Default
On the Cisco 7000 series and the Cisco 7500 series, if you omit the destination device, the router uses the default device specified by the cd command. If you omit the destination filename, the router uses the source filename.
Command Mode
EXEC
Usage Guidelines
The rcp protocol requires that a client send the remote username of an rcp request to the server. When you issue one of the copy rcp commands, by default the Cisco IOS software sends the username associated with the current TTY, if that name is valid. For example, if the user is connected to the router through Telnet and the user was authenticated through the username command, then the software sends that username as the remote username.
If the TTY username is invalid, the software uses the host name as the both the remote and local usernames. To specify a different remote username to be sent to the rcp server, use the ip rcmd remote-username command. You can also specify the path of an existing directory along with the remote username.
If you copy a bootstrap image, system image, or configuration file from a personal computer used as a file server, the remote host computer must support rsh protocol.
Use the copy rcp bootflash command to copy a bootstrap image from a network server to Flash memory on a Cisco 4500 router using rcp. The router prompts for the name or address of the server and the name of the file to be copied. It provides an option to erase existing Flash memory before writing onto it, and allows you to confirm the erasure. The entire copying process takes several minutes and differs from network to network.
Before loading the router from Flash memory, verify that the checksum of the bootstrap image in Flash memory matches the checksum listed in the README file that was distributed with the system software image.
The checksum of the bootstrap image in Flash memory is displayed at the bottom of the screen when you issue the copy rcp bootflash command. The README file was copied to the server automatically when you installed the system software.
Use the copy rcp flash to copy a system image from a network server to the router's internal Flash memory using rcp. The Cisco IOS software prompts for the address of the rcp server and rcp filename. When you issue this command, the system provides an option to erase existing Flash memory before writing onto it. The entire copying process takes several minutes and differs from network to network.
Use the copy rcp running-config command to copy a configuration file from a network server to the router's running configuration environment using rcp. You can copy either a host configuration file or a network configuration file. Accept the default value of host to copy and load a host configuration file containing commands that apply to one network server in particular. Enter network to copy and load a network configuration file containing commands that apply to all network servers on a network.
Use the copy rcp startup-configuration command to copy a host or network configuration file from a network server to the router's startup configuration environment using rcp. Accept the default value of host to copy and store a host configuration file containing commands that apply to one network server in particular. Enter network to copy and store a network configuration file containing commands that apply to all network servers on a network.
On all platforms except the Cisco 7000 series and the Cisco 7500 series, the copy rcp startup-config command copies a configuration file from the network server to NVRAM. On the Cisco 7000 series and Cisco 7500 series, the command copies a configuration file from the network server to the location specified by the CONFIG_FILE environment variable. The CONFIG_FILE environment variable specifies the configuration used during initialization.
On the Cisco 7000 series and the Cisco 7500 series, the copy rcp command generally copies a file from a network server to another destination using rcp. If you do not specify a source or destination device, the router uses the default device specified by the cd command.
On the Cisco 7000 series and the Cisco 7500 series, when the destination is also specified by the CONFIG_FILE environment variable, the router prompts you for confirmation before proceeding with the copy. To view the contents of the CONFIG_FILE environment variable, use the show boot command. To modify the CONFIG_FILE environment variable, use the boot config command. To save your modifications, use the copy running-config startup-config command.
High System Availability (HSA) refers to how quickly your router returns to an operational status after a failure occurs. On the Cisco 7507 and Cisco 7513, you can install two RSP cards in a single router to improve system availability.
On a Cisco 7507 or Cisco 7513 configured for HSA, the copy rcp startup-configuration command used with automatic synchronization disabled causes the system to ask you if you also want to copy the file to the slave's startup configuration. The default answer is yes. If automatic synchronization is enabled, the system automatically copies the file to the slave's startup configuration each time you use this command.
Examples
The following Cisco 3600 series example copies the file c3600-i-mz from the rcp server at IP address 171.69.1.129 to the Flash memory PC card inserted in PCMCIA slot 0. Since there is only one partition on this card, the Cisco IOS software uses this partition as the default. As the operation progresses, the Cisco IOS software asks you erase the files on the PC card to accomodate the incoming file.
The following example shows how to use the copy rcp bootflash command on a Cisco 4500 router:
The exclamation point (!) indicates that the copy process is taking place. Each exclamation point (!) indicates that ten packets have been transferred successfully.
The following example shows how to use the copy rcp flash command on a Cisco 4500 system. The interface might differ slightly on other systems. This example copies a system image named file1 from the netadmin1 directory on the remote server named SERVER1.CISCO.COM with an IP address of 131.108.101.101 to Flash memory. To ensure that enough Flash memory is available to accommodate the system image to be copied, the Cisco IOS software allows you to erase the contents of Flash memory first.
If the partition is read-only and has dual Flash bank support in boot ROM, the session continues as follows:
The file will be copied into the partition given by the user earlier:
If the partition is read-write, the session continues as follows:
The file will be copied into the partition given by the user earlier:
The following example shows how to use copy rcp startup-config command on a Cisco 4000 system. The interface might differ slightly on other systems. This example specifies a remote username of netadmin1. Then it copies and stores a host configuration file host2-confg from the netadmin1 directory on the remote server with an IP address of 131.108.101.101.
The following example uses the copy rcp file_id command to copy the router-image file from a network server using rcp to the Flash memory card inserted in slot 0 of the RP or RSP card:
Related Commands
boot config
To copy a file from a TFTP server to the router or to another destination, use one of the following copy tftp EXEC commands. The copy tftp running-config command replaces the configure network command. The copy tftp startup-config command replaces the configure overwrite-network command.
Syntax Description
Default
On the Cisco 7000 series and the Cisco 7500 series, if you omit the destination device, the router uses the default device specified by the cd command. If you omit the destination filename, the router uses the source filename.
Command Mode
EXEC
Usage Guidelines
The system prompts for the address of the TFTP server and TFTP filename if you do not provide them at the command line. When copying to internal Flash memory, the system provides an option to erase existing internal Flash memory before writing onto it. The entire copying process takes several minutes and differs from network to network.
High System Availability (HSA) refers to how quickly your router returns to an operational status after a failure occurs. On the Cisco 7507 and Cisco 7513, you can install two RSP cards in a single router to improve system availability.
Examples
The following example shows you how to copy the file c3600-i-mz from the TFTP server at IP address 171.69.1.129 to the internal Flash memory, which has one partition, in a Cisco 3600 series router. This entire operation takes 17 seconds to perform as indicated at the end of the example.
The following example shows how to use the copy tftp bootflash command:
The following example shows sample output of copying a system image named file1 into Flash memory:
If the partition is read-only and has dual Flash bank support in boot ROM, the session continues as follows:
The file will be copied into the partition given by the user earlier:
If the partition is read-write, the session continues as follows:
The file will be copied into the partition given by the user earlier:
Related Commands
boot config
To copy the running configuration file to another destination, use one of the following copy running-config EXEC commands. The copy running-config startup-config command replaces the write memory command. The copy running-config rcp or copy running-config tftp command replaces the write network command.
Syntax Description
Default
On the Cisco 7000, Cisco 7200, and Cisco 7500 series, if you omit the destination device, the router uses the default device specified by the cd command. If you omit the destination filename, the router uses the source filename.
Command Mode
EXEC
Usage Guidelines
On the Cisco 3600 series, you can copy the running configuration to the internal Flash memory or to a Flash memory PC card inserted in PCMCIA slot 1 or slot 0. During the copy operation, you have the opportunity to assign a new destination filename and erase the contents of the destination device.
You cannot copy a running configuration to a Flash partition from which you are currently running. For example, copy the new image to partition 2 if partition 1 is running the current system image. Otherwise, the copy operation will fail.
Use the copy running-config {rcp | tftp} command to copy the current configuration file to a network server using rcp or TFTP. The configuration file copy can serve as a backup copy. You are prompted for a destination host and filename.
The rcp protocol requires that a client send the remote username of an rcp request to the server. When you issue the copy running-config rcp command, the Cisco IOS software defaults to sending the username associated with the current TTY, if that name is valid. For example, if the user is connected to the router through Telnet and the user was authenticated through the username command, then the software sends that username as the remote username.
If the TTY username is invalid, the software uses the host name as both the remote and local usernames.
To specify a different remote username to be sent to the server, use the ip rcmd remote-username command. You can also specify the path of an existing directory along with the remote username.
If you copy the configuration file to a personal computer used as a file server, the computer must support the rsh protocol.
To run this command, the router must contain Flash memory.
If you issue the copy running-config startup-config command from a bootstrap system image, you receive a warning instructing you to indicate whether you want your previous NVRAM configuration to be overwritten and configuration commands lost. This warning does not appear if NVRAM contains an invalid configuration or if the previous configuration in NVRAM was generated by a bootstrap system image.
On the Cisco 7000 series, Cisco 7200 series, or Cisco 7500 series, the copy running-config startup-config command copies the currently running configuration to the location specified by the CONFIG_FILE environment variable. This variable specifies the device and configuration file used for initialization. When the CONFIG_FILE environment variable points to NVRAM or when this variable does not exist (such as at first-time startup), the software writes the current configuration to NVRAM. If the current configuration is too large for NVRAM, the software displays a message and stops executing the command. Use this command in conjunction with the reload command to restart the router with the configuration information stored in the CONFIG_FILE environment variable.
When the CONFIG_FILE environment variable specifies a valid device other than nvram: (that is, flash, bootflash, slot0, or slot1), the software writes the current configuration to the specified device and filename and stores a distilled version of the configuration in NVRAM. A distilled version of the configuration is one that does not contain access list information. If NVRAM already contains a copy of a complete configuration, the router prompts you to confirm the copy.
To view the contents of the CONFIG_FILE environment variable, use the show boot command. To modify the CONFIG_FILE environment variable, use the boot config command. To save your modifications to the CONFIG_FILE environment variable, use the copy running-config startup-config command.
High System Availability (HSA) refers to how quickly your router returns to an operational status after a failure occurs. On the Cisco 7507 and Cisco 7513, you can install two RSP cards in a single router to improve system availability.
Example for the Cisco 3600 Series
The following example copies the running configuration from the router to the Flash memory PC card inserted in PCMCIA slot 1. Unless you want to erase all files in the PC card, do not accept erasing the Flash device before writing.
Examples for the Cisco 4500 Series
The following example shows how to use the copy running-config rcp command on a Cisco 4500 system. The interface may differ slightly on other systems. This example specifies a remote username of netadmin1. Then it copies the running configuration file, named Rtr2-confg to the netadmin1 directory on the remote host with an IP address of 131.108.101.101.
The following example shows the copy running-config startup-config command and the warning the system provides if you are trying to save configuration information from bootstrap into the system:
Enter no to escape writing the configuration information to memory.
Examples for the Cisco 7000 Series, Cisco 7200 Series, and Cisco 7500 Series
In the following example the router copies the running configuration to the startup configuration specified by the CONFIG_FILE variable:
The following example copies the running configuration to a file named router-confg1 on the Flash memory card inserted in slot 0 on a Cisco 7000 series, Cisco 7200 series, or Cisco 7500 series:
Related Commands
boot config
Syntax Description
Default
On the Cisco 7000, Cisco 7200, and Cisco 7500 series, if you omit the destination device, the router uses the default device specified by the cd command. If you omit the destination filename, the router uses the source filename.
Command Mode
EXEC
Usage Guidelines
On the Cisco 3600 series, you can copy the startup configuration to the internal Flash memory or to a Flash memory PC card inserted in PCMCIA slot 1 or slot 0. During the copy operation, you have the opportunity to assign a new destination filename and erase the contents of the destination device.
You cannot copy a startup configuration to a Flash partition from which you are currently running. For example, copy the new image to partition 2 if partition 1 is running the current system image. Otherwise, the copy operation will fail.
On all platforms except the Cisco 7000, Cisco 7200, and Cisco 7500 series, this command copies the contents of the configuration file in NVRAM to a network server or to the currently running configuration.
On the Cisco 7000 series, Cisco 7200 series, and Cisco 7500 series, the command copies the configuration file pointed to by the CONFIG_FILE environment variable to another destination. To view the contents of the CONFIG_FILE environment variable, use the show boot command. To modify the CONFIG_FILE environment variable, use the boot config command. To save your modifications to the CONFIG_FILE environment variable, use this copy running-config startup-config command.
The rcp protocol requires that a client send the remote username of an rcp request to the server. When you issue the copy startup-config rcp command, by default the Cisco IOS software sends the username associated with the current TTY, if that name is valid. For example, if the user is connected to the router through Telnet and the user was authenticated through the username command, then the Cisco IOS software sends that username as the remote username.
If the TTY username is invalid, the software uses the host name as the both the remote and local usernames.
To specify a different remote username to be sent to the server, use the ip rcmd remote-username command. You can also specify the path of an existing directory along with the remote username.
If you copy the configuration file to a personal computer used as a server, the computer must support the rsh protocol.
High System Availability (HSA) refers to how quickly your router returns to an operational status after a failure occurs. On the Cisco 7507 and Cisco 7513, you can install two RSP cards in a single router to improve system availability.
Example for the Cisco 3600 Series
The following example copies the startup configuration to the second partition on the Flash memory PC card inserted in slot 0. Unless you want to erase all files in the PC card, do not accept erasing the Flash device before writing.
Example for the Cisco 4500 Series
Example for the Cisco 7000 Series, Cisco 7200 Series, Cisco 7500 Series
The following example uses the copy startup-config command to copy the startup configuration file (specified by the CONFIG_FILE environment variable) to a Flash memory card inserted in slot 0:
Related Commands
boot config
To copy a Cisco IOS image from a PC to a Cisco 3600 series router with the Xmodem protocol, use the copy xmodem flash EXEC command:
Syntax Description
There is no additional syntax for this command.
Default
Disabled
Command Mode
EXEC
Usage Guidelines
The copy tftp flash: and copy rcp flash: commands are recommended over the copy xmodem flash command. The Xmodem protocol transfers files slower than TFTP and rcp. Use the copy xmodem flash command if you do not have access to a TFTP or rcp server.
The new Cisco IOS image is transferred from a local or remote computer (such as a PC, Macintosh, or UNIX) to your router through the console or AUX port.
No output is displayed on the port from which the transfer is occuring. This is why the console port is not recommended for this operation. You may use the logging bufferred command to log all router messages sent to the console port during the file transfer.
You cannot copy a file to a Flash memory PC card inserted in a PCMCIA slot with this command.
Example
The following example initiates a file transfer from a local or remote PC to a router using the copy xmodem flash command:
To copy a Cisco IOS image from a PC to a Cisco 3600 series router with the Ymodem protocol, use the copy ymodem flash EXEC command:
Syntax Description
There is no additional syntax for this command.
Default
Disabled
Command Mode
EXEC
Usage Guidelines
The Ymodem protocol is very similar to the Xmodem protocol, but Ymodem transfers data faster since it uses larger sized file transfer data blocks.
The copy tftp flash: and copy rcp flash: commands are recommended over the copy xmodem flash command. The Xmodem protocol transfers files slower than TFTP and rcp. Use the copy xmodem flash command if you do not have access to a TFTP or rcp server.
The new Cisco IOS image is transferred from a local or remote PC to your router through the console or AUX port.
You cannot copy a file to a Flash memory PC card inserted in a PCMCIA slot with this command.
Example
The following example initiates a file transfer from a local or remote PC to a router using the copy ymodem flash command:
Syntax Description
Default
For the Cisco 7000 series, the initial default device is flash:. Otherwise, the default device is that specified by the cd command.
Command Mode
EXEC
Usage Guidelines
On the Cisco 3600 series, you cannot erase a specific filename. You can only erase an entire Flash device or a specific partition using the erase device:[partition] command. Devices to erase are internal Flash memory or a Flash memory PC card inserted in PCMCIA slot 0 or slot 1.
Use the erase startup-config command on all platforms to erase the startup configuration. On all platforms except the Cisco 7000 series, Cisco 7200 series, or Cisco 7500 series, this command erases the configuration stored in NVRAM.
When you use the erase startup-config command on the Cisco 7000 series, Cisco 7200 series, and the Cisco 7500 series, the router erases or deletes the configuration pointed to by CONFIG_FILE environment variable. The CONFIG_FILE environment variable specifies the configuration file used for initialization. If the CONFIG_FILE environment variable points to NVRAM, the router erases NVRAM. If the CONFIG_FILE environment variable specifies a Flash memory device and configuration filename, the Cisco IOS software deletes the configuration file. That is, the software marks the file as "deleted."
Use the erase device:[filename] command only with the Cisco 7000 series. This command functions like the delete command. That is, when you erase a specific file, the system marks the file as deleted, allowing you to later undelete an erased file. See the delete and undelete commands for more information. If you omit the device, the software uses the default device specified by the cd command.
If you attempt to erase the configuration file specified by the CONFIG_FILE or BOOTLDR environment variable, the system prompts you to confirm the deletion. Also, if you attempt to erase the last valid system image specified in the BOOT environment variable, the system prompts you to confirm the deletion.
Examples
The following example illustrates how to erase the configuration located in NVRAM or specified by the CONFIG_FILE environment variable:
The following example deletes the myconfig file from a Flash memory card inserted in the slot 0:
The following example erases all of partiton 2 in the Cisco 3600 series internal Flash memory.
Related Commands
boot config
Syntax Description
Default
DRAM is allocated to 75 percent for processor memory and 25 percent for packet memory.
Command Mode
Global configuration
Usage Guidelines
Currently in the Cisco IOS software, all available DRAM is sized as follows:
If you want to load larger Cisco IOS images, increase the processor memory. If you want more buffers, increase the packet memory. For example, the memory-size iomem 40 command allocates 40 percent of the available DRAM to packet memory and 60 percent to processor memory.
Example
The following configuration allocates 40 percent of the available DRAM to packet memory and the remaining 60 percent to processor memory.
Syntax Description
Default
Flash memory consists of one partition.
If this command is entered but the partition size is not specified, two partitions of equal size
Command Mode
Global configuration
Usage Guidelines
Although the software supports up to eight partitions, current hardware allows only two. To undo partitioning, use either the partition flash 1 or no partition flash command. If one or more files exist in the second partition, you must manually erase the second partition with the erase flash command before reverting to a single partition.
When creating two partitions, you must not truncate a file or cause the spillover of a file into the second partition.
Example
The following example creates two partitions of 4 MB each in Flash memory:
The following Cisco 3600 series example divides the Flash memory in the PC card, which is inserted in PCMCIA slot 0, into two partitions. Each parition is 8 MB large.
The following example creates four partitions of equal size in the PCMCIA card inserted in slot 0.
Use the show controller t1 privileged EXEC command on the Cisco 4000 series, Cisco 7000 family, Cisco 7500 series, and Cisco AS5200 series to display information about the T1 links supported by the Network Processor Module (NPM) (Cisco 4000) or the MultiChannel Interface Processor (MIP) (Cisco 7000).
Syntax Description
Command Mode
EXEC
Usage Guidelines
This command displays controller status that is specific to the controller hardware. The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
If you specify a slot and port number, each 15 minute period will be displayed.
Sample Display
The following is sample output from the show controller t1 command on the Cisco 7000 family:
Table 6 describes the show controller t1 display fields.
To display information about the ISDN Basic Rate Interface (BRI), use the show controllers bri privileged EXEC command.
Syntax Description
Command Mode
Privileged EXEC
Sample Display
The following is sample output from the show controllers bri command:
The following is sample output from the show controllers bri command on a Cisco 1600 series router:
Table 8 describes the significant fields in the display.
Table 8 : Show Controllers BRI Field Descriptions
To display the layout and contents of Flash memory, use one of the following show flash EXEC commands:
Syntax Description
Command Mode
EXEC
Usage Guidelines
The show flash command displays the type of Flash memory present, any files that might currently exist in Flash memory, and the amounts of Flash memory used and remaining.
For the Cisco 1600 series and Cisco 3600 series routers, you cannot abbreviate the device type in the command syntax. For example, to show the flash output you cannot enter the sh fla: command. You must enter the sh flash: command or the show flash: command.
For the Cisco 7000 series PCMCIA slot, Cisco 7200 series, and Cisco 7500 series, when you specify a PCMCIA slot as the device, the router displays the layout and contents of the Flash memory card inserted in the specified slot of the RP or RSP card. When you omit the device: argument, the router displays the default device specified by the cd command. Use the pwd command to show the current default device.
Sample Displays for the Cisco 1600, Cisco 3000, Cisco 3600, Cisco 7000, and Cisco 7500 Series
The following is sample output from the show flash command on the Cisco 3000, Cisco 3600, and Cisco 7000 series:
Table 9 describes the show flash display fields for the Cisco 3000 series and the internal Flash memory of the Cisco 7000 series.
Table 9 : Show Flash Field Descriptions
As the display shows, the Flash memory can store and display multiple, independent software images for booting itself or for TFTP server software for other products. This feature is useful for storing default system software. These images can be stored in compressed format (but cannot be compressed by the router).
To eliminate any files from Flash memory (invalidated or otherwise) and free up all available memory space, the entire Flash memory must be erased; individual files cannot be erased from Flash memory.
The following is a sample output from the show flash command on a router that has Flash memory partitioned:
The following is a sample output from the show flash all command on the Cisco 3000 series and the internal Flash memory of the Cisco 7000 series. The format of the display is different on different router models. The format of your display might differ.
Table 10 describes the show flash all display fields for the Cisco 3000 series and the Cisco 7000 series internal Flash memory.
Table 10 : Show Flash All Field Descriptions
The following is sample output for the show flash all command on a Cisco 3000 and Cisco 3600 series router that has Flash memory partitioned. However on the Cisco 3600, type the show flash: all command to retrieve this display.
Table 10 describes the additional fields in the display.
The following example shows detailed Flash information about the PCMCIA card inserted in slot 0 on a Cisco 3600 series router. This card has four partitions. Each partition contains files that can be copied to different types of Flash devices such as a remote TFTP server, another PCMCIA card in slot 1, the internal Flash memory, the running configuration, or the startup configuration:
The following example shows detailed information about the second partition located in internal Flash memory on the Cisco 3600 series:
The following are possible values for Copy-Mode:
The following example shows copy and file space information about about each partition in the PCMCIA card inserted in slot 1 of a Cisco 3600 series router.
The following sample output shows the show flash command on a Cisco 7000 series PCMCIA slot, Cisco 7200 series, or Cisco 7500 series:
If you do not use the cd command to change the present working device to slot 1, you can display the same sample output with the following command:
To show modem performance statistics on an Cisco AS5200, enable the show modem EXEC command.
Syntax Description
Command Mode
EXEC
Usage Guidelines
The keywords log, summary, and at-mode apply only to manageable modems.
The number of events that you can record and view with the show modem log command is defined using the modem buffer-size command. The events stored in the buffer wrap around the event queue. You cannot clear the modem event queue.
Use the clear modem counters command to reset modem counters and clear the modem summary report of modem statistics.
Sample Displays
The following display shows output information for the show modem command:
Table 12 describes the fields in the previous display.
Table 12 : Show Modem Field Descriptions
The following example shows the statistics and current configurations for the manageable modem 1/1. A dash (-) indicates a field that is not available on nonmanageable modems. An x indicates a field that is available and active on manageable modems.
Table 12 describes the fields in the previous display.
The following example displays example output for a nonmanageable modem. Notice that unavailable fields are marked with dashes (-):
The following example displays the call switching module information for modem 1/2:
Table 14 describes the most useful fields in the previous display.
Table 14 : Show Modem Call Switching Module Field Descriptions
The following example shows the event log status for a manageable modem and identifies the time elapsed since each modem event was performed (for example, 01:02:41 means the modem event occurred 1 hour, 2 minutes, and 41 seconds ago):
The following example shows the cumulative system statistics for all manageable modems on the universal access server:
Table 14 describes the fields in the previous display.
The following example shows the sample display for modem group 1, which is composed of modem 1/0 through modem 1/23:
The following example shows a sample display of version information for modem firmware, modem boot code, and the modem board hardware.
If version number is displayed as 0.0.0, make sure that out of band port status polling is functioning.
Table 15 describes the fields shown in the previous display for the show modem version command.
The following example shows all the directly connected sessions currently using the internal out-of-band ports on the integrated manageable modems:
The following example shows all the directly connected sessions currently using the internal out-of-band ports on the integrated manageable modems:
To enable the router to send SNMP traps, use the snmp-server enable global configuration command. The no form of this command disables sending SNMP traps.
Syntax Description
Defaults
No traps are enabled.
If you enter this command with no keywords, the default is to enable all trap types.
Command Mode
Global configuration
Usage Guidelines
Use the snmp-server enable command to specify which SNMP traps the router sends, and use the snmp-server host command to specify which host or hosts receive SNMP traps.
You must issue a separate snmp-server enable command for each trap type, including envmon and repeater.
Example
The following example enables the router to send Frame Relay and environmental monitor traps.
Related Commands
A dagger (†) indicates that the command is documented outside this chapter.
snmp-server host
Syntax Description
Default
Disabled
Command Mode
Global configuration
Usage Guidelines
You can specify multiple filenames by repeating the tftp-server command. The system sends a copy of the system image contained in ROM or one of the system images contained in Flash memory to any client that issues a TFTP Read Request with this filename.
If the specified filename1 or filename2 exists in Flash memory, a copy of the Flash image is sent. On systems that contain a complete image in ROM, the system sends the ROM image if the specified filename1 or filename2 is not found in Flash memory.
Images that run from ROM cannot be loaded over the network. Therefore, it does not make sense to use TFTP to offer the ROMs on these images.
On the Cisco 7000 series and Cisco 7500 series, the system sends a copy of the file contained on one of the Flash memory devices to any client that issues a TFTP Read Request with its filename.
Examples
In the following example, the system uses TFTP to send a copy of the version-10.3 file located in Flash memory in response to a TFTP Read Request for that file. The requesting host is checked against access list 22.
In the following example, the system uses TFTP to send a copy of the ROM image gs3-k.101 in response to a TFTP Read Request for the gs3-k.101 file:
In the following example, the system uses TFTP to send a copy of the version-11.0 file in response to a TFTP Read Request for that file. The file is located on the Flash memory card inserted in slot 0 of the RP or RSP card.
The following example enables a Cisco 3600 series router to operate as a TFTP server. The source file c3640-i-mz is in the second partition in the internal Flash memory.
In the next Cisco 3600 series example, the source file c3640-j-mz is in the second partition of a Flash memory PC card that is inserted in PCMCIA slot 0.
Related Command
A dagger (†) indicates that the command is documented outside this chapter.
access-list †
To verify the checksum of a file on a Flash device, use the verify EXEC command. This command replaces the copy verify and copy verify flash commands.
Syntax Description
Default
The current working device is the default device.
Command Mode
EXEC
Usage Guidelines
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.
Examples
The following example verifies the gsxx file on the Flash memory card inserted in slot 0:
The following Cisco 3600 series example verifies the checksum of the file named alz, which is located in the fourth partion of the Flash memory PC card inserted in PCMCIA slot 0.
Related Commands
cd
Syntax Description
Command Mode
ROM monitor
Default
Xmodem protocol with 8-bit CRC, which loads a file into Flash memory.
Usage Guidelines
The Cisco 3600 series does not support XBOOT functionality. This means that if your Cisco IOS image is somehow erased or not functioning properly, you cannot load a new system image over the network if your router reloads.
The Cisco 1600 series does support XBOOT functionality.
Use the xmodem ROM monitor command to download a new system image to your router using the Xmodem or Ymodem file transfer protocols. Your computer (such as a PC, Mac, or UNIX) must have a terminal emulation application that supports these protocols.
You can download a new file in two ways:
There are memory requirements that you should consider before you perform a copy operation. On the Cisco 3600 series routers, you must have enough DRAM present in your system to equal or surpass the size of the file being transferred, which is true even if you are copying to Flash memory. This is also true for the Cisco 1600 series if you have the -r option specified in the initial command line. If you are copying a file to Flash memory on a Cisco 3600 series, the destination file image will be copied as the first file positioned in Flash memory. Any files existing in Flash memory will be erased. No support for partitions or copying as a second file is supported. However for the Cisco 1600 series, multiple files are supported in Flash memory. An Image that runs from Flash on the Cisco 1600 series must be positioned as the first file in Flash memory. So if you want to copy a new run from Flash image to Flash, you must erase all existing files first.
For the Cisco 1600 series routers, you must have
Enabling a modem connection from the telephone network to your console port introduces security issues that you should consider before enable the connection. For example, remote users can dial into your modem and access the router's configuration settings.
Example
To copy the file new-ios-image from a remote or local PC to a router, use the xmodem -c filename ROM monitor command.
To display the performance report for an integrated CSU/DSU in a Cisco 2524 or Cisco 2525 router, use the show service-module privileged EXEC command.
Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
This command applies to the 2- and 4-wire 56/64-kbps CSU/DSU module and FT1/T1 CSU/DSU module. The performance-statistics keyword applies only to the FT1/T1 CSU/DSU module.
Examples
The following example shows CSU/DSU performance statistics for intervals 30 to 32. Each interval is 15 minutes long. All the data is zero because no errors were discovered on the T1 line:
The following example is sample output from the show service-module number command:
The following example is sample output from the show service-module serial command on a Cisco 1600 series router:
Table 16 Table 16 describes the fields displayed in the show service-module serial command.describes the fields displayed in the show service-module serial command.
Related Command
clear service-module
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional content and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, user documentation software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact ccohelp@cisco.com. For additional information, contact ccoteam@cisco.com.
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. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Router#
copy tftp flash:1:c3600-i-mz
System flash directory, partition 1:
File Length Name/status
1 1711088 current-ios
[1711152 bytes used, 2483152 available, 4194304 total]
The destination filename must be an alphanumeric expression. For example, the filename 1 is invalid.
Address or name of remote host [171.69.1.129]?
Source file name [c3600-i-mz]?
Accessing file 'c3600-i-mz' on 171.69.1.129...
Loading c3600-i-mz from 171.69.1.129 (via Ethernet1/0): ! [OK]
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'c3600-i-mz' from server
as 'c3600-i-mz' into Flash WITH erase? [yes/no]
yes
Erasing device... eeeeeeeeeeeeeeee ...erased
Loading c3600-i-mz from 171.69.1.129 (via Ethernet1/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 1711088/4194304 bytes]
Verifying checksum... OK (0xF89A)
Flash device copy took 00:00:17 [hh:mm:ss]
Router#
copy tftp flash:
System flash
Partition Size Used Free Bank-Size State Copy Mode
1 4096K 1671K 2424K 4096K Read/Write Direct
2 16384K 1671K 14712K 8192K Read/Write Direct
[Type ?<no> for partition directory; ? for full directory; q to abort]
Which partition? [default = 1]
System flash directory, partition 1:
File Length Name/status
1 1711088 c3600-i-mz
[1711152 bytes used, 2483152 available, 4194304 total]
Address or name of remote host [171.69.1.129]?
Source file name?
images/3600/c3600-i-mz
Destination file name [
images/3600/c3600-i-mz]?
Accessing file 'images/3600/c3600-i-mz' on 171.69.1.129...
Loading images/3600/c3600-i-mz from 171.69.1.129 (via Ethernet1/0): ! [OK]
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'images/3600/c3600-i-mz' from server
as 'images/3600/c3600-i-mz' into Flash WITH erase? [yes/no]
yes
Erasing device... eeeeeeeeeeeeeeee ...erased
Loading images/3600/c3600-i-mz from 171.69.1.129 (via Ethernet1/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 1711088/4194304 bytes]
Verifying checksum... OK (0xF89A)
Flash device copy took 00:00:17 [hh:mm:ss]
Router#
copy rcp slot0:
PCMCIA Slot0 flash
Partition Size Used Free Bank-Size State Copy Mode
1 4096K 3068K 1027K 4096K Read/Write Direct
2 4096K 1671K 2424K 4096K Read/Write Direct
3 4096K 0K 4095K 4096K Read/Write Direct
4 4096K 3825K 270K 4096K Read/Write Direct
[Type ?<no> for partition directory; ? for full directory; q to abort]
Which partition? [default = 1]
PCMCIA Slot0 flash directory, partition 1:
File Length Name/status
1 3142288 c3600-j-mz
[3142352 bytes used, 1051952 available, 4194304 total]
Address or name of remote host [171.69.1.129]?
Source file name?
/tftpboot/gate/c3600-i-mz
Destination file name [/tftpboot/gate/c3600-i-mz]?
Accessing file '/tftpboot/gate/c3600-i-mz' on 171.69.1.129...
Connected to 171.69.1.129
Loading 1711088 byte file c3600-i-mz: ! [OK]
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy '/tftpboot/gate/c3600-i-mz' from server
as '/tftpboot/gate/c3600-i-mz' into Flash WITH erase? [yes/no]
yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Connected to 171.69.1.129
Loading 1711088 byte file c3600-i-mz: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Verifying checksum... OK (0xF89A)
Flash device copy took 00:00:18 [hh:mm:ss]
Router#
copy rcp slot0:3
Because the partition number is identified in the initial command line, the system software does not show a higher level display of the partition structure, unlike the previous copy rcp example.
PCMCIA Slot0 flash directory, partition 3:
File Length Name/status
1 426 running-config
[492 bytes used, 4193812 available, 4194304 total]
Address or name of remote host [171.69.1.129]?
Source file name?
/tftpboot/gate/c3600-i-mz
Destination file name [/tftpboot/gate/c3600-i-mz]?
Accessing file '/tftpboot/gate/c3600-i-mz' on 171.69.1.129...
Connected to 171.69.1.129
Loading 1711088 byte file c3600-i-mz: ! [OK]
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy '/tftpboot/gate/c3600-i-mz' from server
as '/tftpboot/gate/c3600-i-mz' into Flash WITH erase? [yes/no]
yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Connected to 171.69.1.129
Loading 1711088 byte file c3600-i-mz: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK]
Verifying checksum... OK (0xF89A)
Flash device copy took 00:00:16 [hh:mm:ss]
Task
Command
Clear the contents of your startup configuration. On most platforms, this command erases the contents of NVRAM. On the Cisco 7000 series and Cisco 7500 series, this command erases the configuration specified by the CONFIG_FILE environment variable.
erase startup-config
Task
Command
Erase or delete a specified configuration file on a specified Flash device.
erase [device:]filename
or
delete [device:]filename
or
erase device:[partition-number]
(Cisco 1600 series and Cisco 3600 series only)
Router# erase slot0:myconfig
Router# delete slot0:myconfig
Router# erase flash:2
System flash directory, partition 2:
File Length Name/status
1 1711088 dirt/gate/c3600-i-mz
[1711152 bytes used, 15066064 available, 16777216 total]
Erase flash device, partition 2? [confirm]
Are you sure? [yes/no]: yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
...erased
Task
Command
Load a configuration file directly into NVRAM or directly into the location specified by the CONFIG_FILE environment variable.
copy rcp startup-config
or
copy tftp startup-config
or
copy device:[partition-number:][filename] startup-config
(Cisco 1600 series and Cisco 3600 series only)
Router# copy slot0:4:IOS-UPGRADE-1 startup-config
Copy 'IOS-UPGRADE-1' from flash device
as 'startup-config' ? [yes/no] yes
[OK]
Router# copy slot0:4:new-ios startup-config
Copy 'new-ios' from flash device
as 'startup-config' ? [yes/no] yes
[OK]
Task
Command
show device: [all | chips | detailed | err | partition number | summary]
copy device:[partition-number:][filename] device:[partition-number:][filename]
verify device: [partition-number:][filename]
Router#
copy flash:1 slot0:
System flash directory, partition 1:
File Length Name/status
1 3142748 dirt/admin/images/new-ios-1
[3142812 bytes used, 1051492 available, 4194304 total]
PCMCIA Slot0 flash
Partition Size Used Free Bank-Size State Copy Mode
1 4096K 1671K 2424K 4096K Read/Write Direct
2 4096K 3069K 1026K 4096K Read/Write Direct
3 4096K 1671K 2424K 4096K Read/Write Direct
4 4096K 3826K 269K 4096K Read/Write Direct
[Type ?<no> for partition directory; ? for full directory; q to abort]
Which partition? [default = 1]
PCMCIA Slot0 flash directory, partition 1:
File Length Name/status
1 1711088 /tftpboot/gate/c3600-i-mz
[1711152 bytes used, 2483152 available, 4194304 total]
Source file name?
dirt/admin/images/new-ios
Destination file name [dirt/admin/images/new-ios]?
Verifying checksum for 'dirt/admin/images/new-ios' (file # 1)... OK
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'dirt/admin/images/new-ios' from flash: device
as 'dirt/admin/images/new-ios' into slot0: device WITH erase? [yes/no]
yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 3142748/4194304 bytes]
Flash device copy took 00:00:50 [hh:mm:ss]
Verifying checksum... OK (0xB732)
Router#
copy flash: slot1:
System flash
Partition Size Used Free Bank-Size State Copy Mode
1 4096K 3070K 1025K 4096K Read/Write Direct
2 16384K 1671K 14712K 8192K Read/Write Direct
[Type ?<no> for partition directory; ? for full directory; q to abort]
Which partition? [default = 1]
System flash directory, partition 1:
File Length Name/status
1 3142748 dirt/network/mars-test/c3600-j-mz.latest
2 850 running-config
[3143728 bytes used, 1050576 available, 4194304 total]
PCMCIA Slot1 flash directory:
File Length Name/status
1 1711088 dirt/gate/c3600-i-mz
2 850 running-config
[1712068 bytes used, 2482236 available, 4194304 total]
Source file name?
running-config
Destination file name [running-config]?
Verifying checksum for 'running-config' (file # 2)... OK
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'running-config' from flash: device
as 'running-config' into slot1: device WITH erase? [yes/no]
yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
!
[OK - 850/4194304 bytes]
Flash device copy took 00:00:30 [hh:mm:ss]
Verifying checksum... OK (0x16)
Task
Command
See the instructions in the section "Copy System Images from Flash Memory to a Network Server."
Enter one of the following commands. Choose the command that corresponds to your router.
ip-address or name
filename
device
env-chassis# copy tftp flash
IP address or name of remote host [255.255.255.255]? dirt
Translating "DIRT"...domain server (255.255.255.255) [OK]
Name of file to copy ? gs7-k
Copy gs7-k from 131.108.13.111 into flash memory? [confirm]
Flash is filled to capacity.
Erasure is needed before flash may be written.
Erase flash before writing? [confirm]
Erasing flash EPROMs bank 0
Zeroing bank...zzzzzzzzzzzzzzzz
Verify zeroed...vvvvvvvvvvvvvvvv
Erasing bank...eeeeeeeeeeeeeeee
Erasing flash EPROMs bank 1
Zeroing bank...zzzzzzzzzzzzzzzz
Verify zeroed...vvvvvvvvvvvvvvvv
Erasing bank...eeeeeeeeeeeeeeee
Erasing flash EPROMs bank 2
Zeroing bank...zzzzzzzzzzzzzzzz
Verify zeroed...vvvvvvvvvvvvvvvv
Erasing bank...eeeeeeeeeeeeeeee
Erasing flash EPROMs bank 3
Zeroing bank...zzzzzzzzzzzzzzzz
Verify zeroed...vvvvvvvvvvvvvvvv
Erasing bank...eeeeeeeeeeeeeeee
Loading from 131.108.1.111: !!!!...
[OK - 1906676/4194240 bytes]
Verifying via checksum...
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvv
Flash verification successful. Length = 1906676, checksum = 0x12AD
Router#
copy tftp flash:my-new-ios
System flash directory:
File Length Name/status
1 1711088 c3600-j-mz
[1711152 bytes used, 2483152 available, 4194304 total]
Address or name of remote host [171.69.1.129]?
Source file name [my-new-ios]?
dirt/images/ios-image
Accessing file 'dirt/images/ios-image' on 171.69.1.129...
Loading dirt/images/ios-image from 171.69.1.129 (via Ethernet1/0): ! [OK]
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'dirt/gate/ios-image' from server
as 'my-new-ios' into Flash WITH erase? [yes/no]
yes
Erasing device... eeeeeeeeeeeeeeee ...erased
Loading dirt/images/ios-image from 171.69.1.129 (via Ethernet1/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 1711088/4194304 bytes]
Verifying checksum... OK (0xF89A)
Flash device copy took 00:00:17 [hh:mm:ss]
env-chassis# copy tftp flash
IP address or name of remote host [131.108.13.111]?
Name of file to copy ? gs7-k
File gs7-k already exists; it will be invalidated!
Copy gs7-k from 131.108.13.111 into flash memory? [confirm]
2287500 bytes available for writing without erasure.
Erase flash before writing? [confirm]n
Loading from 131.108.1.111: !!!!...
[OK - 1906676/2287500 bytes]
Verifying via checksum...
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
vvvvvvvvvvvvvvvvvvvvvvvvvvvvv
Flash verification successful. Length = 1902192, checksum = 0x12AD
Router# copy tftp flash
Flash: embedded flash security jumper(12V)
must be strapped to modify flash memory
Router# copy tftp:router-config slot0:new-config
Router# copy tftp flash
IP address or name of remote host [255.255.255.255]? server1
Name of tftp filename to copy into flash []? IJ09140Z
copy IJ09140Z from 131.131.101.101 into flash memory? [confirm] <Return>
xxxxxxxx bytes available for writing without erasure.
erase flash before writing? [confirm] <Return>
Clearing and initializing flash memory (please wait)####...
Loading from 101.2.13.110: !!!!...
[OK - 324572/524212 bytes]
Verifying checksum...
VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV...
Flash verification successful. Length = 1204637, checksum = 0x95D9
Tasks
Command
See the instructions in the section "Copy from Flash Memory to a TFTP Server."
configure terminal
ip rcmd remote-username username
^Z
Enter one of the following commands. Choose the command that corresponds to your router.
(Cisco 1600 series and Cisco 3600 series only)
ip-address or name
filename
Router#
copy rcp flash:
System flash directory:
File Length Name/status
1 426 running-config
[492 bytes used, 4193812 available, 4194304 total]
Address or name of remote host [171.69.1.129]?
Source file name?
/images/new-ios
Destination file name [images/new-ios]?
my-ios
Accessing file '/images/new-ios' on 171.69.1.129...
Connected to 171.69.1.129
Loading 1711088 byte file new-ios: ! [OK]
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy '/images/new-ios' from server
as 'my-ios' into Flash WITH erase? [yes/no]
yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Connected to 171.69.1.129
Loading 1711088 byte file new-ios: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK]
Verifying checksum... OK (0xF89A)
Flash device copy took 00:00:16 [hh:mm:ss]
Router#
copy rcp slot0:2:c3600-j-mz
PCMCIA Slot0 flash directory, partition 2:
File Length Name/status
1 1711128 c3600-i-mz.test
2 426 running-config
[1711684 bytes used, 2482620 available, 4194304 total]
Address or name of remote host [171.69.1.129]?
Source file name? [c3600-j-mz]?
/tftpboot/gate/c3600-j-mz
Accessing file '/tftpboot/gate/c3600-j-mz' on 171.69.1.129...
Connected to 171.69.1.129
Loading 3141700 byte file c3600-j-mz: ! [OK]
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy '/tftpboot/gate/c3600-j-mz' from server
as 'c3600-j-mz' into Flash WITH erase? [yes/no]
yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Connected to 171.69.1.129
Loading 3141700 byte file c3600-j-mz: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK]
Verifying checksum... OK (0x84E)
Flash device copy took 00:00:30 [hh:mm:ss]
Router1# configure terminal
Router1(config)# ip rcmd remote-username netadmin1
^Z
Router# copy rcp flash
System flash directory:
File name/status
1 mysysim1
[2076072 bytes used, 21080 bytes available]
Address or name of remote host[UNKNOWN]? 131.108.101.101
Name of file to copy? mysysim1
Copy mysysim1 from SERVER1.CISCO.COM?[confirm]
Checking for file `mysysim1' on SERVER1.CISCO.COM...[OK]
Erase Flash device before writing?[confirm]
Are you sure?[confirm]
Erasing device...ezeeze...erased.
Connected to 131.108.101.101
Loading 2076007 byte file mysysim1: !!!!...
[OK]
Verifying checksum... (0x87FD)...[OK]
Router#
Router1# configure terminal
Router1(config)# ip rcmd remote-username netadmin1
^Z
Router1# copy rcp slot0:router-image
Task
Command
Copy a boot image from a MOP server.
copy mop flash
or
copy mop device:[partition-number:][filename] (Cisco 1600 series and Cisco 3600 series only)
Router# copy mop flash
System flash directory:
File Length Name/status
1 984 router image[deleted]
2 984 router image
[2096 bytes used, 8386512 available, 8388608 total]
Source file name? routerimage
Destination file name [routerimage]?
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'routerimage' from server
as 'routerimage' into Flash WITH erase? [yes/no]yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Loading routerimage from 1234.5678.9abc via Ethernet0: !
[OK - 984/8388608 bytes]
Verifying checksum... OK (0x14B3)
Flash copy took 0:00:01 [hh:mm:ss]
Task
Command
Enter one of the following commands. Choose the command that corresponds to your router.
Enter the command that corresponds to the type of router or access server you are using:
ip-address or name
filename
copy slot0: tftp
PCMCIA Slot0 flash
Partition Size Used Free Bank-Size State Copy Mode
1 4096K 1671K 2424K 4096K Read/Write Direct
2 4096K 3068K 1027K 4096K Read/Write Direct
3 4096K 1671K 2424K 4096K Read/Write Direct
4 4096K 3825K 270K 4096K Read/Write Direct
[Type ?<no> for partition directory; ? for full directory; q to abort]
Which partition? [default = 1] 1
PCMCIA Slot0 flash directory, partition 1:
File Length Name/status
1 1711088 your-ios
[1711152 bytes used, 2483152 available, 4194304 total]
Address or name of remote host [171.69.1.129]?
Source file name?
your-ios
Destination file name [your-ios]?
dirt/sysadmin/your-ios
Verifying checksum for '/tftpboot/images/ios-1' (file # 1)... OK
Copy '/tftpboot/images/ios-1' from Flash to server
as 'dirt/sysadmin/ios-2'? [yes/no]
yes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upload to server done
Flash device copy took 00:00:23 [hh:mm:ss]
Enter the Router#
copy slot0:2 tftp
PCMCIA Slot0 flash directory, partition 2:
File Length Name/status
1 3141700 your-ios
[3141764 bytes used, 1052540 available, 4194304 total]
Address or name of remote host [171.69.1.129]?
Source file name?
your-ios
Destination file name [your-ios]?
/sysadmin/images/server-ios
Verifying checksum for 'your-ios' (file # 1)... OK
Copy 'your-ios' from Flash to server
as '/sysadmin/images/server-ios'? [yes/no]
yes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upload to server done
Flash device copy took 00:00:41 [hh:mm:ss]
In this next Cisco 3600 series example, the source device type, source partition number,
and source filename are specified in the initial command line.
Router#
copy slot0:4:your-ios tftp
Address or name of remote host [171.69.1.129]?
Destination file name [dirt/images/c3640-i-mz.test]?
dirt/images/c3640-j-mz
Verifying checksum for 'dirt/images/c3640-i-mz.test' (file # 2)... OK
Copy 'dirt/images/c3640-i-mz.test' from Flash to server
as 'dirt/images/c3640-j-mz'? [yes/no]
yes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upload to server done
Flash device copy took 00:00:20 [hh:mm:ss]
Router# show flash all
2048K bytes of flash memory on embedded flash (in XX).
ROM socket code bytes name
0 U42 89BD 0x40000 INTEL 28F020
1 U44 89BD 0x40000 INTEL 28F020
2 U46 89BD 0x40000 INTEL 28F020
3 U48 89BD 0x40000 INTEL 28F020
4 U41 89BD 0x40000 INTEL 28F020
5 U43 89BD 0x40000 INTEL 28F020
6 U45 89BD 0x40000 INTEL 28F020
7 U47 89BD 0x40000 INTEL 28F020
security jumper(12V) is installed,
flash memory is programmable.
file offset length name
0 0x40 1204637 xk09140z
[903848/2097152 bytes free]
Router# copy flash tftp
IP address of remote host [255.255.255.255]? 101.2.13.110
filename to write on tftp host? xk09140z
writing xk09140z !!!!...
successful tftp write.
Router#
Router#show flash slot1:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. 1 46A11866 2036C 4 746 May 16 1995 16:24:37 test
Router#copy slot1:test tftp
IP address of remote host [255.255.255.255]? 101.2.13.110
filename to write on tftp host? [test]y
writing test !!!!...
successful tftp write.
Router#
Task
Command
Enter one of the following commands. Choose the command that corresponds to your router.
(Cisco 7000 series PCMCIA slot and Cisco 7500 series only)
(Cisco 1600 series or Cisco 3600 series only)
(all other routers and access servers)
configure terminal
ip rcmd remote-username username
^Z
Enter one of the following commands. Choose the command that corresponds to your router.
(Cisco 1600 series and Cisco 3600 series only)
ip-address or name
filename
Router#
copy slot1: rcp
PCMCIA Slot1 flash directory:
File Length Name/status
1 1711088 your-ios
[1711152 bytes used, 2483152 available, 4194304 total]
Address or name of remote host [171.69.1.129]?
Source file name?
your-ios
Destination file name [your-ios]?
/sysadmin/images/your-ios
Verifying checksum for 'your-ios' (file # 1)... OK
Copy 'your-ios' from Flash to server
as '/sysadmin/images/your-ios'? [yes/no]
yes
Writing /sysadmin/images/your-iosj !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upload to server done
Flash device copy took 00:00:08 [hh:mm:ss]
router#
copy slot1:1:your-ios
Address or name of remote host [171.69.1.129]?
Destination file name [your-ios]?
/sysadmin/images/your-ios
Verifying checksum for 'your-ios' (file # 1)... OK
Copy 'your-ios' from Flash to server
as '/sysadmin/images/your-ios'? [yes/no]
yes
Writing /sysadmin/images/your-ios !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upload to server done
Flash device copy took 00:00:08 [hh:mm:ss]
Task
Command
Specify a file.
tftp-server flash filename1
Specify a file in the first partition of Flash.
tftp-server flash filename1
Specify a file in the specified partition of Flash.
tftp-server flash partition-number:filename1
or
tftp-server flash [device:][partition-number:]filename
(Cisco 1600 series and Cisco 3600 series only)
Task
Command
reload
Break1
config-register 0
reset
Enter one the following commands. Choose the command that corresponds to the type of router you are using:
(Cisco 3600 series only)
1 This key will not work on the Cisco 7000 unless it has Cisco IOS Release 10 boot ROMs.
> boot flash
F3: 1858656+45204+166896 at 0x1000
Booting gs7-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR [OK -
1903912/13765276 bytes]
F3: 1858676+45204+166896 at 0x1000
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
> boot flash gs7-k
F3: 1858656+45204+166896 at 0x1000
Booting gs7-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRR [OK - 1903912/13765276 bytes]
F3: 1858676+45204+166896 at 0x1000
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
System Bootstrap, Version 4.6(1012) [mlw 99], INTERIM SOFTWARE
Copyright (c) 1986-1992 by cisco Systems
RP1 processor with 16384 Kbytes of memory
>boot flash:
>boot slot0:
>boot slot0:2:
>boot slot0:3:imagename
>boot flash
Task
Command
reload
Break1
boot filename [ip-address]
1 This key will not work on the Cisco 7000 unless it has Cisco IOS Release 10 boot ROMs.
>boot network1
>boot imagename
Task
Command
configure terminal
Enter one of the following commands. Choose only the command that applies to your type of router or access server:
config-register value2
(command for all other platforms)
^Z
copy running-config startup-config3
show startup-config
reload
1 Bootflash memory is not included in the Cisco 3600 series routers. Booting from internal Flash memory or a Flash memory PC card inserted in one of two PCMCIA slots is supported.
2 Refer to the "Modify the Configuration Register Boot Field" section for more information on systems that can use this command to modify the software configuration register.
3 The write memory command also copies the running configuration to the startup configuration.
Router# configure terminal
Router (config)# boot system flash gsnew-image
Router (config)# config-register 0x102
^Z
Router# copy running-config startup-config
[ok]
Router# reload
[confirm]
%SYS-5-RELOAD: Reload requested
System Bootstrap, Version 4.6(0.16), BETA SOFTWARE
Copyright (c) 1986-1995 by cisco Systems
RP1 processor with 16384 Kbytes of memory
F3: 1871404+45476+167028 at 0x1000
Booting gsnew-image from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR [OK - 1916912/13767448 bytes]
F3: 1871404+45476+167028 at 0x1000
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134
GS Software (GS7), Version 10.2,
Copyright (c) 1986-1995 by cisco Systems, Inc.
Compiled Thu 05-Nov-94 14:16 by mlw
Task
Command
Copy a system image from a PC to Flash memory using the Cisco IOS software in EXEC mode.
copy xmodem flash
or
copy ymodem flash
Copy a system image from a PC to Flash memory using the ROM monitor software.
xmodem {-c | -y | -r | -x} [filename]
(Cisco 3600 series only)
or
xmodem {-y | -c | -e | -f | -r | -x } [-s baud-rate] [filename]
(Cisco 1600 series only)
Router#
copy xmodem flash
**** WARNING ****
x/ymodem is a slow transfer protocol limited to the current speed
settings of the auxiliary/console ports. The use of the auxilary
port for this download is strongly recommended.
During the course of the download no exec input/output will be
available.
---- ******* ----
Proceed? [confirm]
Use crc block checksumming? [confirm]
no
Max Retry Count [10]:
7
Perform image validation checks? [confirm]
Xmodem download using simple checksumming with image validation
Continue? [confirm]
System flash directory:
File Length Name/status
1 1738244 images/c3600-i-mz
[1738308 bytes used, 2455996 available, 4194304 total]
Destination file name ?
new-IOS-image
Erase flash device before writing? [confirm]
n
Copy '' from server
as 'new-IOS-image' into Flash WITHOUT erase? [yes/no]
yes
Ready to receive file...........
rommon >
xmodem -c new-IOS-image
Do 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 flash will be lost!
Invoke this application only for disaster recovery.
Do you wish to continue? y/n [n]:
yes
Ready to receive file new-IOS-image ...
Router#
configure terminal
Router-conf #
line 0
Router-conf-line #
speed xxxx
rommon 1 >
rommon 1 >
xmodem -c <filename>
Do 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 flash will be lost!
Invoke this application only for disaster recovery.
Do you wish to continue? y/n [n]:
yes
Ready to receive file new-IOS-image...
rommon 1 >
xmodem -s 115200 -c <filename>
Task
Command
Set the packet memory and processor memory percentages.
memory-size iomem packet-memory-percentage1
1 The default is 25% for packet memory and 75% for processor memory.
Warning: Attempting a memory partition that does not provide enough Processor memory for
the current image.If you write memory now, this version of software may not be able to run.
Router# show memory
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor 604DDEE0 7479584 1247232 6232352 6227568 6230244
I/O C00000 4194304 3442316 51988 751988 743636
Router#
configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
memory-size iomem 40
Router(config)#
exit
Router#
Router#
copy running-config startup-config
Building configuration...
[OK]
Router#
reload
rommon 1 >
b
program load complete, entry point: 0x80008000, size: 0x32ea24
Self decompressing the image : ###################################################################################################################################################################################################################################################### [OK]
Configured I/O memory percentage was too large; using 30 percent
For example, on the same channelized T1 you can configure the pri-group timeslots 1-10 command, channel-group 11 timeslots 11-16 command, and cas-group 17 timeslots 17-23 type e&m-fgb command. This is a rare configuration, because it requires you to align the correct range of timeslots on both ends of the connection.
Task
Command
controller t1 0
cablelength long dbgain-value dbloss-value
framing esf
linecode b8zs
clock source line primary 1
or
If you are not running ISDN, configure channels to accept voice calls.
or
If you are not running ISDN, configure channels for synchronous serial communications.
This step creates interfaces that you can configure.
pri-group timeslots 1-24
cas-group 1 timeslots 1-24 type e&m-fgb
channel-group 1 timeslots 1-24
fdl {att | ansi}
1 Configure the other T1 line as the secondary clock source.
Task
Command
interface serial 0:23
isdn incoming-voice modem 2, 3
dialer rotary-group number 4
1
2 Because some telcos charge more for ISDN data calls, you might want to configure the isdn incoming-voice isdn command to process ISDN calls as voice calls, which provides you with data service at a voice billing rate.
3 Native ISDN calls are directed like a protocol.
4 The address you will assign to the dialer interface is used for the hunt group provided by the phone comany.
AS5200(config)# controller T1 0
AS5200(config-controller)# pri-group timeslots 1-24
AS5200(config-controller)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:0, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:1, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:2, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:3, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:4, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:5, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:6, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:7, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:8, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:9, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:10, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:11, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:12, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:13, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:14, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:15, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:16, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:17, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:18, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:19, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:20, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:21, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:22, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:23, changed state to up
%LINK-3-UPDOWN: Interface Serial1:23, changed state to up
AS5200(config)# controller T1 0
AS5200(config-controller)# cas-group 1 timeslots 1-24 type e&m-fgb
AS5200(config-controller)#
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 1 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 2 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 3 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 4 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 5 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 6 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 7 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 8 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 9 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 10 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 11 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 12 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 13 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 14 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 15 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 16 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 17 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 18 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 19 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 20 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 21 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 22 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 23 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 24 is up
AS5200(config)# controller T1 0
AS5200(config-controller)# channel-group 1 timeslots 1-24
AS5200(config-controller)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:1, changed state to down
%LINK-3-UPDOWN: Interface Serial1:1, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:1, changed state to up
AS5200(config)# controller T1 0
AS5200(config-controller)# pri-group timeslots 1-10
AS5200(config-controller)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:0, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:1, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:2, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:3, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:4, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:5, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:6, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:7, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:8, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:9, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:23, changed state to up
%LINK-3-UPDOWN: Interface Serial1:23, changed state to up
AS5200(config-controller)# channel-group 1 timeslots 11-16
%Channel-group 1 is already an isdn channel
AS5200(config-controller)# channel-group 11 timeslots 11-16
AS5200(config-controller)#
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:11, changed state to down
AS5200(config-controller)#
%LINK-3-UPDOWN: Interface Serial1:11, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1:11, changed state to up
AS5200(config-controller)# cas-group 12 timeslots 17-23 type e&m-fgb
The channel has been assigned to pri or channel-group
AS5200(config-controller)# cas-group 17 timeslots 17-23 type e&m-fgb
AS5200(config-controller)#
Task
Command
Define the controller location in the Cisco 7000 family by slot and port number.
or
Define the controller location in the Cisco 4000 series by unit number, ranging from 0 through 2.
or
Define the controller location in the Cisco AS5200 series by unit number, ranging from 0 through 1.
controller e1 slot/port
controller e1 number
controller e1 number
Task
Command
Define the line code as either AMI or HDB3; HDB3 is the default.
linecode {ami | hdb3}
Task
Command
Define the framing characteristics as either CRC4 or no-CRC4.
framing {crc4 | no-crc4} [australia]
Task
Command
Define the clock source if you are connecting two cards back-to-back for testing purposes; the default source is the line.
clock source {line | internal} (Cisco 7000 family, Cisco 7500 series, and Cisco 4000 only)
Define the clock source for each E1 port.
clock source {line {primary | secondary} | internal} (Cisco AS5200 only)
Task
Command
Define the channel group number and, if needed, circuit speed.
channel-group number timeslots range [speed {48 | 56 | 64}]
Task
Command
Define the serial interface for an E1 channel group.
interface serial slot/port:channel-group (Cisco 7000 family)
interface serial number:channel-group (Cisco 4000 series, Cisco AS5200)
Task
Command
Show various performance statistics for a modem or group of modems.
show modem [slot/modem-port | group number]
Show the call switching module status for a modem or group of modems.
show modem csm [slot/modem-port | group number]
Show the event log status for a modem or group of modems.
show modem log [slot/modem-port | group number]1
Display version information for modem firmware, boot code, and modem hardware.
show modem version
Display the cumulative system statistics for all modems installed in the access server.
show modem summary1
Display all directly connected AT sessions active on the access server.
show modem at-mode1
1 This command does not apply to nonmanageable modems.
Valid Command Variations
Cisco 1600 Series
Cisco 3600 Series
Cisco 7000 Series
Cisco 7500 Series
All Other Platforms
boot
Yes
Yes
No
No
Yes
boot filename [ip-address]
Yes
Yes
Yes
Yes
Yes
boot flash [filename]
Yes
No
No
No
Yes
boot flash [device:] [partition-number:] [filename]
Yes
No
No
No
Yes
boot flash [device:filename]
Yes
No
Yes
No
No
boot device:[filename]
Yes
Yes
No
Yes
Yes
boot [device:] [partition-number:] [filename]
Yes
Yes
No
No
No
filename
When used in conjunction with the ip-address argument, the filename argument is the name of the system image file to boot from a network server. The filename is case sensitive.
(Optional) When used in conjunction with the flash keyword, the filename argument is the name of the system image file to boot from Flash memory. On all platforms except the Cisco 7000 series and Cisco 7500 series, the system obtains the image file from internal Flash memory. On the Cisco 7000 series and Cisco 7500 series, the device: argument specifies the Flash memory device from which to obtain the system image. See the device: argument later in this table for valid device values. The filename is case sensitive. Without filename, the first valid file in Flash memory is loaded.
ip-address
(Optional) IP address of the TFTP server on which the system image resides. If omitted, this value defaults to the IP broadcast address of 255.255.255.255.
flash
(Optional) Boots the router from Flash memory.
device
(Optional on all platforms except the Cisco 7500 series) On all platforms except the Cisco 3600, Cisco 7000, and Cisco 7500 series, the only valid value is flash.
On the Cisco 3600, Cisco 7000, and Cisco 7500 series, use these valid devices followed by a colon (:), which is required:
· flash---Internal Flash memory in the Cisco 3600 series and Cisco 7000 series.
· bootflash---Internal Flash memory in the Cisco 7500 series. The Cisco 3600 series does not support booting from bootflash memory.
· slot0---The Personal Computer Memory Card International Association (PCMCIA) slot on the Cisco 7000 series Route Processor (RP) card, the first PCMCIA slot on the Cisco 7500 series Route Switch Processor (RSP) card, or the first PCMCIA slot on the Cisco 3600 series.
· slot1---The second PCMCIA slot on the Cisco 7500 series RSP card or the Cisco 3600 series.
partition-number
(Optional) Boots the router from Flash memory with the optional filename of the image you want loaded from the specified Flash partition. If you do not specify a filename, the first valid file in the specified partition of Flash memory is loaded.
> boot
> boot routertest 131.108.15.112
>boot flash:
>boot slot0:
> boot flash
Booting gs7-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR [OK - 1903912/13765276 bytes]
> boot flash gs7-k
Booting gs7-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRR [OK - 1903912/13765276 bytes]
> boot flash flash:2:igs-bpx-l
no boot system flash [device:][partition-number:] filename
boot system mop filename [mac-address] [interface]
no boot system mop filename [mac-address] [interface]
boot system rom
no boot system rom
boot system [rcp | tftp] filename [ip-address]
no boot system [rcp | tftp] filename [ip-address]
no boot system
flash
On all platforms except the Cisco 7000 series, Cisco 7200 series, and Cisco 7500 series, this keyword boots the router from internal Flash memory. If you omit all arguments that follow this keyword, the system searches internal Flash for the first bootable image.
On the Cisco 7000, Cisco 7200, and Cisco 7500 series routers, this keyword boots the router from a Flash device, as specified by the device: argument. On the Cisco 7000 series, when you omit all arguments that follow this keyword, the system searches internal Flash and then the PCMCIA slots (starting with slot 0) for the first bootable image. On the Cisco 7200 series or Cisco 7500 series, when you omit all arguments that follow this keyword, the system searches the PCMCIA slot 0 for the first bootable image.
device
(Optional) Device containing the system image to load at startup. The colon (:) is required. Valid devices are as follows:
· flash---Internal Flash memory. Optionally, use this device on all platforms except the Cisco 7200 series or Cisco 7500 series. The flash option is the only valid device option for all platforms except the Cisco 3600, Cisco 7000, Cisco 7200, and the Cisco 7500 series. For the Cisco 7000 series, this device is the default if you do not specify a device. On the Cisco 1600 series, this device specfied a PC card.
· bootflash---Internal Flash memory in the Cisco 7200 series and Cisco 7500 series. The Cisco 3600 series does have bootflash memory.
· slot0---PCMCIA slot 0 on the Cisco 3600 series, Cisco 7000 series, Cisco 7200 series, and Cisco 7500 series. For the Cisco 7200 series and Cisco 7500 series, this device is the default if you do not specify a device.
· slot1---PCMCIA slot 1 on the Cisco 3600 series, Cisco 7200 series, and Cisco 7500 series.
partition-number
(Optional) Number of the Flash memory partition that boots the router with the image specified by the optional filename argument. If you do not specify a filename, the router loads the first valid file in the specified partition of Flash memory. This argument is not used with the Cisco 7000 series, Cisco 7200 series, and Cisco 7500 series.
filename
(Optional when used with boot system flash.) Name of the system image to load at startup. It is case sensitive. If you do not specify a filename, the router loads the first valid file in the specified Flash device, the specified partition of Flash memory, or the default Flash device if you also omit the device: argument.
mop
Boots the router from a system image stored on a Digital MOP server. This keyword is not supported on the Cisco 7200 series or Cisco 7500 series.
mac-address
(Optional) Media Access Control (MAC) address of the MOP server containing the specified system image file. If you do not include the MAC address argument, the router sends a broadcast message to all MOP boot servers. The first MOP server to indicate that it has the specified file is the server from which the router gets the boot image.
interface
(Optional) Interface the router uses to send out MOP requests to the MOP server. The interface options are async, dialer, ethernet, serial, and tunnel. If you do not specify the interface argument, the router sends a request out on all interfaces that have MOP enabled. The interface that receives the first response is the interface the router uses to load the software.
rom
Boots the router from ROM. This keyword is not supported on the Cisco 3600 series, Cisco 7200 series, or Cisco 7500 series.
rcp
(Optional) Boots the router from a system image stored on a network server using rcp. If you omit this keyword, the transport mechanism defaults to tftp.
tftp
(Optional) Boots the router from a system image stored on a TFTP server. This is the default when you do not specify any keyword (flash, mop, rom, tftp, or rcp).
ip-address
(Optional) IP address of the TFTP server containing the system image file. If omitted, this value defaults to the IP broadcast address of 255.255.255.255.
Command
Cisco 1600 Series
Support
Cisco 3600 Series
Support
Cisco 7000 Series
Support
Cisco 7200 Series
Support
Cisco 7500 Series
Support
boot system flash flash: [partition-number:] filename
Yes
Yes
No
No
No
boot system flash slot0: [partition-number:] filename
No
Yes
No
No
No
boot system flash slot1: [partition-number:] filename
No
Yes
No
No
No
boot system flash flash:[filename]
No
Yes
Yes
Yes
Yes
boot system flash slot0:[filename]
No
Yes
Yes
Yes
Yes
boot system mop filename [mac-address] [interface]
No
No
Yes
Yes
Yes
boot system rom
No
No
Yes
Yes
Yes
boot system tftp filename [ip-address]
No
Yes
Yes
Yes
Yes
boot system rcp filename [ip-address]
No
Yes
Yes
Yes
Yes
boot system flash bootflash:[filename]
No
No
No
Yes
Yes
boot system flash slot0:[filename]
No
Yes
No
Yes
Yes
boot system flash slot1:[filename]
No
Yes
No
Yes
Yes
boot system tftp filename [ip-address]
No
Yes
No
Yes
Yes
Router(config)# boot system flash slot0:4:dirt/images/New-IOS-image
boot system cs3-rx.90-1 192.31.7.24
boot system cs3-rx.83-2 192.31.7.19
boot system rom
boot system flash flash:2:igs-bpx-l
boot system flash slot0:new-config
copy rcp rcp
copy rcp tftp
copy rcp flash
copy rcp startup-config
copy rcp flash
ip rcmd remote-username
show boot
no cas-group channel-number [timeslots range] type signal-type
channel-number
Specifies a single channel group number, which can be between 0 and 23.
timeslots range
(Optional) Specifies a timeslot range of values from 1 to 24.
type signal-type
Specifies the type channel associated signaling. Choose one of the following signal types to configure:
e&m-fgb---Specifies ear and mouth channel signaling with feature group b support.
e&m-fgd---Specifies ear and mouth channel signaling with feature group d support.
fxs-loopstart--- Specifies foreign exchange system loopstart signaling support.
fxs-groundstart---Specifies foreign exchange system ground start signaling support.
sas-loopstart---Specifies specific access station loopstart signaling support.
sas-groundstart---Specifies specific access station ground start signaling support.
AS5200(config)# controller T1 0
AS5200(config-controller)# cas-group 1 timeslots 1-24 type e&m-fgb
AS5200(config-controller)#
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 1 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 2 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 3 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 4 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 5 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 6 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 7 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 8 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 9 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 10 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 11 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 12 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 13 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 14 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 15 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 16 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 17 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 18 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 19 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 20 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 21 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 22 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 23 is up
%DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 24 is up
no clock source line {primary | secondary}
line
Specifies the T1 or E1 line as the clock source.
internal
Specifies the MIP (Cisco 7000 family) or the NPM (Cisco 4000) as the clock source; for the Cisco AS5200, specifies internal clocking.
primary
Primary TDM clock source.
secondary
Secondary TDM clock source.
clock source internal
AS5200(config)# controller t1 0
AS5200(config-controller)# clock source line primary
AS5200(config-controller)# exit
AS5200(config)# controller t1 1
AS5200(config-controller)# clock source line secondary
AS5200(config)# controller e1 0
AS5200(config-controller)# clock source line primary
AS5200(config-controller)# exit
AS5200(config)# controller e1 1
AS5200(config-controller)# clock source line secondary
linecode
flash:
Specifies internal Flash memory.
partition-number
(Optional) On the Cisco 1600 series and Cisco 3600 series, specifies the partition number of the source or destination Flash device. You must enter a colon (:) after the partition number if a filename follows the partition number in the initial command line.
filename
(Optional) Specifies the name of the source or destination file.
tftp
Copy to a TFTP server using the Cisco 3600 series or Cisco 1600 series routers.
rcp
Copy to a rcp server using the Cisco 3600 series or Cisco 1600 series routers.
running-config
Specifies the currently running configuration as the destination of the copy operation.
startup-config
Specifies the configuration used for initialization as the destination of the copy operation. (Note that the CONFIG_FILE environment variable specifies the startup configuration on a Cisco 7000 series, Cisco 7200 series, and Cisco 7500 series.)
device
On the Cisco 3600 series, specifies the destination device of the copy operation. You must enter a colon (:) after the device type that you specify. The following devices are available for the Cisco 3600 series: flash, slot0, and slot1.
· flash---Internal Flash memory device on the Cisco 3600 series. A Flash memory PC card on the Cisco 1600 series.
· slot0---First PCMCIA slot device on the Cisco 3600 series.
· slot1---Second PCMCIA slot device on the Cisco 3600 series.
file-id
On the Cisco 7000 series, 7200, and Cisco 7500 series platforms, the file-id variable specifies a device:filename as the source or destination of the copy operation.
· flash---Internal Flash memory device on the Cisco 7000 series.
· bootflash--- Internal Flash memory device in the Cisco 7200 series and Cisco 7500 series. The Cisco 3600 series does not support copying an image from bootflash memory.
· slot0---First PCMCIA slot device on the Cisco 7000 series or the first PCMCIA slot on the Cisco 7200 series, and Cisco 7500 series.
· slot1---Second PCMCIA slot device on the Cisco 7200 series and Cisco 7500 series.
· nvram---Router's NVRAM device . If you specify NVRAM, omit the filename.
· slavebootflash---Internal Flash memory device on the slave RSP card of a Cisco 7507 or Cisco 7513 configured for HSA.
· slaveslot0---First PCMCIA slot device of the slave RSP card on a Cisco 7507 or Cisco 7513 configured for HSA.
· slaveslot1---Second PCMCIA slot device of the slave RSP card on a Cisco 7507 or Cisco 7513 configured for HSA.
· slavenvram---NVRAM device of the slave RSP card on a Cisco 7507 or Cisco 7513 configured for HSA. If you specify the slave NVRAM, omit the filename.
The filename is the name of the source or destination file. You must always provide a source filename. You can omit the destination filename, in which case the system uses the source filename. Wildcards are not permitted. The maximum filename length is 63 characters.
Router# copy slot0: tftp
PCMCIA Slot0 flash
Partition Size Used Free Bank-Size State Copy Mode
1 4096K 1671K 2424K 4096K Read/Write Direct
2 4096K 3068K 1027K 4096K Read/Write Direct
3 4096K 1671K 2424K 4096K Read/Write Direct
4 4096K 3825K 270K 4096K Read/Write Direct
[Type ?<no> for partition directory; ? for full directory; q to abort]
Which partition? [default = 1] 1
PCMCIA Slot0 flash directory, partition 1:
File Length Name/status
1 1711088 /tftpboot/cisco_rules/c3600-i-mz
[1711152 bytes used, 2483152 available, 4194304 total]
Address or name of remote host [171.69.1.129]?
Source file name? /tftpboot/cisco_rules/c3600-i-mz
Destination file name [/tftpboot/cisco_rules/c3600-i-mz]? dirt/cisco_rules/c3700-i-mz
Verifying checksum for '/tftpboot/cisco_rules/c3600-i-mz' (file # 1)... OK
Copy '/tftpboot/cisco_rules/c3600-i-mz' from Flash to server
as 'dirt/cisco_rules/c3700-i-mz'? [yes/no] yes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Upload to server done
Flash device copy took 00:00:23 [hh:mm:ss]
Router# copy slot0:4:IOS-UPGRADE-1 running-config
Copy 'IOS-UPGRADE-1' from flash device
as 'running-config' ? [yes/no] yes
Router# copy flash: slot1:
System flash
Partition Size Used Free Bank-Size State Copy Mode
1 4096K 3070K 1025K 4096K Read/Write Direct
2 16384K 1671K 14712K 8192K Read/Write Direct
[Type ?<no> for partition directory; ? for full directory; q to abort]
Which partition? [default = 1] <<enter return>>
System flash directory, partition 1:
File Length Name/status
1 3142748 dirt/images/mars-test/c3600-j-mz.latest
2 850 running-config
[3143728 bytes used, 1050576 available, 4194304 total]
PCMCIA Slot1 flash directory:
File Length Name/status
1 1711088 dirt/images/c3600-i-mz
2 850 running-config
[1712068 bytes used, 2482236 available, 4194304 total]
Source file name? running-config
Destination file name [running-config]? <<enter return>>
Verifying checksum for 'running-config' (file # 2)... OK
Erase flash device before writing? [confirm] <<enter return>>
Flash contains files. Are you sure you want to erase? [confirm] <<enter return>>
Copy 'running-config' from flash: device
as 'running-config' into slot1: device WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
...erased
!
[OK - 850/4194304 bytes]
Flash device copy took 00:00:30 [hh:mm:ss]
Verifying checksum... OK (0x16)
copy bootflash:router-config1 slot0:router-backupconfig
copy slot0:router-image startup-config
copy nvram: slot0:router-backupconfig
copy slot1:router-image slaveslot0:
copy rcp startup-config
delete
dir
show boot
slave auto-sync config
verify
device
On the Cisco 1600 series and Cisco 3600 series, specifies the destination device of the copy operation. You must enter a colon (:) after the device type that you specify. The following devices are available for the Cisco 3600 series: flash, slot0, and slot1. Only the flash device is supported on the Cisco 1600 series.
Device options are as follows:
· flash---Internal Flash memory device on the Cisco 3600 series. A Flash memory PC card on the Cisco 1600 series.
· slot0---First PCMCIA slot device on the Cisco 3600 series.
· slot1---Second PCMCIA slot device on the Cisco 3600 series.
partition-number
(Optional) On the Cisco 1600 series and Cisco 3600 series, specifies a partition number on the destination Flash memory device. You must enter a colon (:) after the partition number if a filename appears after this option in the initial command line.
filename
(Optional) On the Cisco 1600 series and Cisco 3600 series, specifies the destination filename. The maximum filename length is 63 characters.
bootflash
Specifies to copy a bootstrap image from a MOP server to internal Flash memory on a Cisco 4500 series. The Cisco 3600 series does not support copying an image from bootflash memory.
flash
Specifies internal Flash memory as the destination of the copy operation.
Router# copy mop flash
System flash directory:
File Length Name/status
1 984 file1 [deleted]
2 984 file1
[2096 bytes used, 8386512 available, 8388608 total]
Source file name? file1
Destination file name [file1]?
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'file1' from server
as 'file1' into Flash WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Loading file1 from 1234.5678.9abc via Ethernet0: !
[OK - 984/8388608 bytes]
Verifying checksum... OK (0x14B3)
Flash copy took 0:00:01 [hh:mm:ss]
Router# copy mop flash
System 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 ?<no> for partition directory; ? for full directory; q to abort]
Which partition? [default = 2]
**** NOTICE ****
Flash load helper v1.0
This process will accept the copy options and then terminate
the current system image to use the ROM based image for the copy.
Routing functionality will not be available during that time.
If you are logged in via telnet, this connection will terminate.
Users with console access can see the results of the copy operation.
---- ******** ----
Proceed? [confirm]
System flash directory, partition 1:
File Length Name/status
1 3459720 master/igs-bfpx.100-4.3
[3459784 bytes used, 734520 available, 4194304 total]
Source file name? master/igs-bfpx-100.4.3
Destination file name [default = source name]?
Loading master/igs-bfpx.100-4.3 from 131.108.1.111: !
Erase flash device before writing? [confirm]
Flash contains files. Are you sure? [confirm]
Copy 'master/igs-bfpx.100-4.3' from MOP server
as 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yes
System flash directory, partition 2:
File Length Name/status
1 3459720 master/igs-bfpx.100-4.3
[3459784 bytes used, 734520 available, 4194304 total]
Source file name? master/igs-bfpx.100-4.3
Destination file name [default = source name]?
Loading master/igs-bfpx.100-4.3 from 131.108.1.111: !
Erase flash device before writing? [confirm]
Flash contains files. Are you sure? [confirm]
Copy 'master/igs-bfpx.100-4.3' from MOP server
as 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yes
Router# copy mop bootflash
System flash directory:
File Length Name/status
1 984 file1 [deleted]
2 984 file1
[2096 bytes used, 8386512 available, 8388608 total]
Source file name? file1
Destination file name [file1]?
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'file1' from server
as 'file1' into Flash WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Loading file1 from 1234.5678.9abc via Ethernet0: !
[OK - 984/8388608 bytes]
Verifying checksum... OK (0x14B3)
Flash copy took 0:00:01 [hh:mm:ss]
boot system flash
cd
copy bootflash tftp
copy rcp bootflash
copy rcp tftp
delete
dir
erase bootflash
show boot
show bootflash
verify
verify bootflash
verify flash
bootflash
Specifies to copy a bootstrap image from a network server to Flash memory on a Cisco 4500 series using rcp.
device
On the Cisco 1600 series and Cisco 3600 series, specifies the destination device of the copy operation. You must enter a colon (:) after the device type that you specify. The following devices are available for the Cisco 3600 series: flash, slot0, and slot1. Only the flash device is available on the Cisco 1600 series.
· flash---Internal Flash memory device on the Cisco 3600 series. A Flash memory PC card on the Cisco 1600 series.
· slot0---First PCMCIA slot device on the Cisco 3600 series.
· slot1---Second PCMCIA slot device on the Cisco 3600 series.
partition-number
(Optional) On the Cisco 1600 series and Cisco 3600 series, specifies a partition number on the destination Flash memory device. You must enter a colon (:) after the partition number if a filename appears after this option in the initial command line.
filename
(Optional) On the Cisco 1600 series and Cisco 3600 series, specifies the destination filename. The maximum filename length is 63 characters.
flash
Specifies internal Flash memory as the destination of the copy operation. The Cisco 7500 series cannot use this keyword; all other platforms can.
running-config
Specifies the currently running configuration as the destination of the copy operation.
startup-config
Specifies the configuration used for initialization as the destination of the copy operation.
file_id
On the Cisco 7000 series, 7200, and Cisco 7500 series platforms, the file-id argument specifies a device:filename as the destination of the copy operation. The device argument is optional; but when it is used, the colon (:) is required.
Devices options are as follows:
· flash---Internal Flash memory on the Cisco 7000 series.
· bootflash---Internal Flash memory in the Cisco 7500 series.
· slot0---PCMCIA slot on the Cisco 7000 series RP card or the first PCMCIA slot on the Cisco 7500 series RSP card.
· slot1---Second PCMCIA slot on the Cisco 7500 series RSP card.
· nvram---Router's NVRAM. If you specify NVRAM, omit the filename. The colon (:) is required. The Cisco 7000 series cannot use this keyword.
· 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.
slavenvram---NVRAM of the slave RSP card on a Cisco 7507 or Cisco 7513 configured for HSA. If you specify the slave NVRAM, omit the filename.
The filename argument is the name of the destination file. You must always provide a source filename. You can omit the destination filename, in which case the system uses the source filename. Wildcards are not permitted. The maximum filename length is 63 characters.
Router# copy rcp slot0:
PCMCIA Slot0 flash
Partition Size Used Free Bank-Size State Copy Mode
1 4096K 3068K 1027K 4096K Read/Write Direct
2 4096K 1671K 2424K 4096K Read/Write Direct
3 4096K 0K 4095K 4096K Read/Write Direct
4 4096K 3825K 270K 4096K Read/Write Direct
[Type ?<no> for partition directory; ? for full directory; q to abort]
Which partition? [default = 1]
PCMCIA Slot0 flash directory, partition 1:
File Length Name/status
1 3142288 c3600-j-mz.test
[3142352 bytes used, 1051952 available, 4194304 total]
Address or name of remote host [171.69.1.129]?
Source file name? /tftpboot/images/c3600-i-mz
Destination file name [/tftpboot/images/c3600-i-mz]?
Accessing file '/tftpboot/images/c3600-i-mz' on 171.69.1.129...
Connected to 171.69.1.129
Loading 1711088 byte file c3600-i-mz: ! [OK]
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy '/tftpboot/images/c3600-i-mz' from server
as '/tftpboot/images/c3600-i-mz' into Flash WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Connected to 171.69.1.129
Loading 1711088 byte file c3600-i-mz:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!
Verifying checksum... OK (0xF89A)
Flash device copy took 00:00:18 [hh:mm:ss]
Router# configure terminal
Router(config)# ip rcmd remote-username netadmin1
Router(config)# Ctrl-Z
Router# copy rcp bootflash
Boot flash directory:
File Length Name/status
1 2622607 c4500-xboot
[2622672 bytes used, 1571632 available, 4194304 total]
Address or name of remote host [255.255.255.255]? 223.255.254.254
Source file name? c4500-xboot.101
Destination file name [c4500-xboot.101]?
Accessing file 'c4500-xboot.101' on 223.255.254.254...
Loading c4500-xboot.101 from 223.255.254.254 (via Ethernet0): -[OK]
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'c4500-xboot.101' from TFTP server into
bootflash as 'c4500-xboot.101' WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeee ...erased
Loading c4500-xboot.101 from 223.255.254.254 (via Ethernet0):!!!!...
[OK - 2622607/4194304 bytes]
Verifying checksum... OK (0xE408)
Flash copy took 0:00:10 [hh:mm:ss]
Router1# configure terminal
Router1(config)# rcmd remote-username netadmin1
Router(config)# Ctrl-Z
Router# copy rcp flash
System flash directory, partition 2:
File Length Name/status
1 984 file1 [deleted]
2 984 file1
[2096 bytes used, 8386512 available, 8388608 total]
Address or name of remote host [255.255.255.255]? 131.108.101.101
Source file name? file1
Destination file name [file1]?
Accessing file 'file1' on 131.108.101.101...
Loading dirt/ssangiah/file1 .from 131.108.101.101 (via Ethernet0): ! [OK]
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'file1' from server
as 'file1' into Flash WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Loading file1 from 131.108.101.101 (via Ethernet0): !
[OK - 984/8388608 bytes]
Verifying checksum... OK (0x14B3)
Flash copy took 0:00:01 [hh:mm:ss]
Router# copy rcp flash
System 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 ?<no> for partition directory; ? for full directory; q to abort]
Which partition? [default = 2]
**** NOTICE ****
Flash load helper v1.0
This process will accept the copy options and then terminate
the current system image to use the ROM based image for the copy.
Routing functionality will not be available during that time.
If you are logged in via telnet, this connection will terminate.
Users with console access can see the results of the copy operation.
---- ******** ----
Proceed? [confirm]
System flash directory, partition 1:
File Length Name/status
1 3459720 master/igs-bfpx.100-4.3
[3459784 bytes used, 734520 available, 4194304 total]
Address or name of remote host [255.255.255.255]? 131.108.1.1
Source file name? master/igs-bfpx-100.4.3
Destination file name [default = source name]?
Loading master/igs-bfpx.100-4.3 from 131.108.1.111: !
Erase flash device before writing? [confirm]
Flash contains files. Are you sure? [confirm]
Copy 'master/igs-bfpx.100-4.3' from TFTP server
as 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yes
System flash directory, partition 2:
File Length Name/status
1 3459720 master/igs-bfpx.100-4.3
[3459784 bytes used, 734520 available, 4194304 total]
Address or name of remote host [255.255.255.255]? 131.108.1.1
Source file name? master/igs-bfpx.100-4.3
Destination file name [default = source name]?
Accessing file 'master/igs-bfpx.100-4.3' on ABC.CISCO.COM...
Loading master/igs-bfpx.100-4.3 from 131.108.1.111: !
Erase flash device before writing? [confirm]
Flash contains files. Are you sure? [confirm]
Copy 'master/igs-bfpx.100-4.3' from TFTP server
as 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yes
Router# configure terminal
Router(config)# ip rcmd remote-username netadmin1
Router(config)# Ctrl-Z
Router# copy rcp running-config
Host or network configuration file [host]?
Address of remote host [255.255.255.255]? 131.108.101.101
Name of configuration file [Router-confg]? host1-confg
Configure using host1-confg from 131.108.101.101? [confirm]
Connected to 131.108.101.101
Loading 1112 byte file host1-confg:![OK]
Router#
%SYS-5-CONFIG: Configured from host1-config by rcp from 131.108.101.101
Router# configure terminal
Router(config)# ip rcmd remote-username netadmin1
Router(config)# Ctrl-Z
Router# copy rcp startup-config
Host or network configuration file [host]?
Address of remote host [255.255.255.255]? 131.108.101.101
Name of configuration file[rtr2-confg]? host2-confg
Configure using rtr2-confg from 131.108.101.101?[confirm]
Connected to 131.108.101.101
Loading 1112 byte file rtr2-confg:![OK]
[OK]
Router#
%SYS-5-CONFIG_NV:Non-volatile store configured from rtr2-config by
rcp from 131.108.101.101
copy rcp slot0:router-image
boot system flash
cd
copy rcp rcp
copy rcp startup-config
ip rcmd remote-username
show boot
verify flash
bootflash
Specifies to copy a bootstrap image from a TFTP server to internal Flash memory on a Cisco 4500 series.
device
On the Cisco 1600 series and Cisco 3600 series, specifies the destination device of the copy operation. You must enter a colon (:) after the device type that you specify. The following devices are available for the Cisco 3600 series: flash, slot0, and slot1. Only the flash device is available on the Cisco 1600 series.
· flash---Internal Flash memory device on the Cisco 3600 series. A Flash memory PC card on the Cisco 1600 series.
· slot0---First PCMCIA slot device on the Cisco 3600 series.
· slot1---Second PCMCIA slot device on the Cisco 3600 series.
partition-number
(Optional) On the Cisco 1600 series and Cisco 3600 series, specifies a partition number for the destination Flash memory device. You must enter a colon (:) after the partition number if a filename appears after this option in the initial command line.
filename
(Optional) On the Cisco 1600 series and Cisco 3600 series, specifies the destination filename. The maximum filename length is 63 characters.
flash
Specifies internal Flash memory as the destination of the copy operation. The Cisco 7500 series cannot use this keyword; all other platforms can.
running-config
Specifies the currently running configuration as the destination of the copy operation.
startup-config
Specifies the configuration used for initialization as the destination of the copy operation.
file_id
On the Cisco 7000 series and Cisco 7500 series, this arguement specifies a device:filename as the destination of the copy operation. The device argument is optional; but when it is used, the colon (:) is required.
Device options are as follows:
· flash---Internal Flash memory on the Cisco 7000 series.
· bootflash---Internal Flash memory in the Cisco 7500 series.
· slot0---PCMCIA slot on the Cisco 7000 series RP card or the first PCMCIA slot on the Cisco 7500 series RSP card.
· slot1---Second PCMCIA slot on the Cisco 7500 series RSP card.
· nvram---Router's NVRAM. If you specify NVRAM, omit the filename. The colon (:) is required.
· 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.
· slavenvram---NVRAM of the slave RSP card on a Cisco 7507 or Cisco 7513 configured for HSA. If you specify the slave NVRAM, omit the filename.
The filename argument is the name of the destination file. You must always provide a source filename. You can omit the destination filename, in which case the system uses the source filename. Wildcards are not permitted. The maximum filename length is 63 characters.
Router# copy tftp flash:
System flash
Partition Size Used Free Bank-Size State Copy Mode
1 4096K 1671K 2424K 4096K Read/Write Direct
2 16384K 1671K 14712K 8192K Read/Write Direct
[Type ?<no> for partition directory; ? for full directory; q to abort]
Which partition? [default = 1]
System flash directory, partition 1:
File Length Name/status
1 1711088 dirt/images/c3600-i-mz
[1711152 bytes used, 2483152 available, 4194304 total]
Address or name of remote host [171.69.1.129]?
Source file name? dirt/images/c3600-i-mz
Destination file name [dirt/images/c3600-i-mz]?
Accessing file 'dirt/images/c3600-i-mz' on 171.69.1.129...
Loading dirt/images/c3600-i-mz from 171.69.1.129 (via Ethernet1/0): ! [OK]
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'dirt/images/c3600-i-mz' from server
as 'dirt/images/c3600-i-mz' into Flash WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeee ...erased
Loading dirt/images/c3600-i-mz from 171.69.1.129 (via Ethernet1/0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 1711088/4194304 bytes]
Verifying checksum... OK (0xF89A)
Flash device copy took 00:00:17 [hh:mm:ss]
Router# copy tftp bootflash
Boot flash directory:
File Length Name/status
1 2622607 c4500-xboot
[2622672 bytes used, 1571632 available, 4194304 total]
Address or name of remote host [255.255.255.255]? 223.255.254.254
Source file name? c4500-xboot.101
Destination file name [c4500-xboot.101]?
Accessing file 'c4500-xboot.101' on 223.255.254.254...
Loading c4500-xboot.101 from 223.255.254.254 (via Ethernet0): ! [OK]
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'c4500-xboot.101' from TFTP server into
bootflash as 'c4500-xboot.101' WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeee ...erased
Loading c4500-xboot.101 from 223.255.254.254 (via Ethernet0): !!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 2622607/4194304 bytes]
Verifying checksum... OK (0xE408)
Flash copy took 0:00:10 [hh:mm:ss]
Router# copy tftp flash
System flash directory, partition 2:
File Length Name/status
1 984 file1 [deleted]
2 984 file1
[2096 bytes used, 8386512 available, 8388608 total]
Address or name of remote host [255.255.255.255]? 223.255.254.254
Source file name? file1
Destination file name [file1]?
Accessing file 'file1' on 223.255.254.254...
Loading dirt/ssangiah/file1 .from 223.255.254.254 (via Ethernet0): - [OK]
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'file1' from server
as 'file1' into Flash WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Loading file1 from 223.255.254.254 (via Ethernet0): !!!!...
[OK - 984/8388608 bytes]
Verifying checksum... OK (0x14B3)
Flash copy took 0:00:01 [hh:mm:ss]
Router# copy tftp flash
System 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 ?<no> for partition directory; ? for full directory; q to abort]
Which partition? [default = 2]
**** NOTICE ****
Flash load helper v1.0
This process will accept the copy options and then terminate
the current system image to use the ROM based image for the copy.
Routing functionality will not be available during that time.
If you are logged in via telnet, this connection will terminate.
Users with console access can see the results of the copy operation.
---- ******** ----
Proceed? [confirm]
System flash directory, partition 1:
File Length Name/status
1 3459720 master/igs-bfpx.100-4.3
[3459784 bytes used, 734520 available, 4194304 total]
Address or name of remote host [255.255.255.255]? 131.108.1.1
Source file name? master/igs-bfpx-100.4.3
Destination file name [default = source name]?
Loading master/igs-bfpx.100-4.3 from 131.108.1.111: !
Erase flash device before writing? [confirm]
Flash contains files. Are you sure? [confirm]
Copy 'master/igs-bfpx.100-4.3' from TFTP server
as 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yes
System flash directory, partition 2:
File Length Name/status
1 3459720 master/igs-bfpx.100-4.3
[3459784 bytes used, 734520 available, 4194304 total]
Address or name of remote host [255.255.255.255]? 131.108.1.1
Source file name? master/igs-bfpx.100-4.3
Destination file name [default = source name]?
Accessing file 'master/igs-bfpx.100-4.3' on ABC.CISCO.COM...
Loading master/igs-bfpx.100-4.3 from 131.108.1.111: !
Erase flash device before writing? [confirm]
Flash contains files. Are you sure? [confirm]
Copy 'master/igs-bfpx.100-4.3' from TFTP server
as 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yes
boot system flash
copy rcp tftp
show boot
verify
verify flash
rcp
Specifies a copy operation to a network server using rcp.
startup-config
Specifies the configuration used for initialization as the destination of the copy operation. The Cisco 4500 series cannot use this keyword.
tftp
Specifies a TFTP server as the destination of the copy operation.
device
On the Cisco 1600 series and Cisco 3600 series, specifies the destination device of the copy operation. You must enter a colon (:) after the device type that you specify. The following devices are available for the Cisco 3600 series: flash, slot0, and slot1. Only the flash device is available on the Cisco 1600 series.
· flash---Internal Flash memory device on the Cisco 3600 series. A Flash memory PC card on the Cisco 1600 series.
· slot0---First PCMCIA slot device on the Cisco 3600 series.
· slot1---Second PCMCIA slot device on the Cisco 3600 series.
partition-number
(Optional) On the Cisco 1600 series and Cisco 3600 series, specifies a partition number on the destination Flash memory device. You must enter a colon (:) after the partition number if a filename appears after this option in the initial command line.
filename
(Optional) On the Cisco 1600 series and Cisco 3600 series, specifies the destination filename. The maximum filename length is 63 characters.
file-id
On the Cisco 7000, Cisco 7200, Cisco 7500 series platforms, file_id contains the option device:filename as the destination of the copy operation. You must enter a colon (:) between each entry that you specify. Valid devices are as follows:
· flash---Internal Flash memory on the Cisco 7000 series.
· slot0---PCMCIA slot on the Cisco 7000 series or the first PCMCIA slot on the Cisco 7200, and Cisco 7500 series.
· slot1---Second PCMCIA slot on the Cisco 7200 series and Cisco 7500 series.
· bootflash---Internal Flash memory in the Cisco 7200 series and Cisco 7500 series. The Cisco 3600 series does not support copying an image from bootflash memory.
· nvram---Router's NVRAM. If you specify NVRAM, omit the filename. The colon (:) is required. The Cisco 7000 series cannot use this keyword.
· 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.
· slavenvram---NVRAM of the slave RSP card on a Cisco 7507 or Cisco 7513 configured for HSA. If you specify NVRAM, omit the filename.
The filename argument is the name of the destination file. You must always provide a source filename. You can omit the destination filename, in which case the system uses the source filename. Wildcards are not permitted. The maximum filename length is 63 characters.
Router# copy runnning-config slot1:
PCMCIA Slot1 flash directory:
File Length Name/status
1 1711088 dirt/images/c3600-i-mz
[1711152 bytes used, 2483152 available, 4194304 total]
Destination file name [running-config]?
Building configuration...
Erase flash device before writing? [confirm] no
Copy 'running-config'
as 'running-config' into flash device WITHOUT erase? [yes/no]
% Please answer 'yes' or 'no'. yes
!
[OK - 850/2483152 bytes]
Verifying checksum... OK (0x16)
Flash device copy took 00:00:00 [hh:mm:ss]
Router# configure terminal
Router(config)# ip rcmd remote-username netadmin1
Router(config)# Ctrl-Z
Router# copy running-config rcp
Remote host[]? 131.108.101.101
Name of configuration file to write [Rtr2-confg]?
Write file rtr2-confg on host 131.108.101.101?[confirm]
Building configuration...[OK]
Connected to 131.108.101.101
Router(boot)# copy running-config startup-config
Warning: Attempting to overwrite an NVRAM configuration written
by a full system image. This bootstrap software does not support
the full configuration command set. If you perform this command now,
some configuration commands may be lost.
Overwrite the previous NVRAM configuration?[confirm]
copy running-config startup-config
copy running-config slot0:router-confg1
cd
copy rcp
copy rcp running-config
copy rcp startup-config
ip rcmd remote-username
reload
show boot
rcp
Specifies a copy operation to a network server using rcp.
running-config
Specifies the currently running configuration as the destination of the copy operation.
tftp
Specifies a TFTP server as the destination of the copy operation.
device
On the Cisco 1600 series and Cisco 3600 series, specifies the destination device of the copy operation. You must enter a colon (:) after the Flash device type that you specify. The following devices are available for the Cisco 3600 series: flash, slot0, and slot1. Only the flash device is available on the Cisco 1600 series.
· flash---Internal Flash memory device on the Cisco 3600 series. A Flash memory PC card on the Cisco 1600 series.
· slot0---First PCMCIA slot device on the Cisco 3600 series.
· slot1---Second PCMCIA slot device on the Cisco 3600 series.
partition-number
(Optional) On the Cisco 1600 series and Cisco 3600 series, specifies a partition number on the destined Flash memory device. You must enter a colon (:) after the partition number if a filename appears after this option in the initial command line.
filename
(Optional) On the Cisco 1600 series and Cisco 3600 series, specifies the destination filename. The maximum filename length is 63 characters.
file-id
On the Cisco 7000, Cisco 7200, Cisco 7500 series platforms, file_id contains the option device:filename as the destination of the copy operation. You must enter a colon (:) between each entry that you specify. Valid devices are as follows:
· flash---Internal Flash memory on the Cisco 7000 series.
· slot0---PCMCIA slot on the Cisco 7000 series or the first PCMCIA slot on the Cisco 7200 series, and Cisco 7500 series.
· slot1---Second PCMCIA slot on the Cisco 7200 series and Cisco 7500 series.
· bootflash---Internal Flash memory in the Cisco 7200 series and Cisco 7500 series. The Cisco 3600 series does not support copying an image from bootflash memory.
· nvram---Router's NVRAM. If you specify NVRAM, omit the filename. The colon (:) is required. The Cisco 7000 series cannot use this keyword.
· 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.
· slavenvram---NVRAM of the slave RSP card on a Cisco 7507 or Cisco 7513 configured for HSA. If you specify the slave NVRAM, omit the filename.
The filename argument is the name of the destination file. You must always provide a source filename. You can omit the destination filename, in which case the system uses the source filename. Wildcards are not permitted. The maximum filename length is 63 characters.
Router# copy startup-config slot0:2
PCMCIA Slot0 flash directory, partition 2:
File Length Name/status
1 3141700 /tftpboot/images/c3600-j-mz
[3141764 bytes used, 1052540 available, 4194304 total]
Destination file name [startup-config]?
Erase flash device before writing? [confirm] n
Copy 'startup-config'
as 'startup-config' into flash device WITHOUT erase? [yes/no] yes
!
[OK - 850/1052540 bytes]
Verifying checksum... OK (0x16)
Flash device copy took 00:00:00 [hh:mm:ss]
Router# configure terminal
Router(config)# ip rcmd remote-username netadmin2
Router(config)# Ctrl-Z
Router# copy startup-config rcp
Remote host[]? 131.108.101.101
Name of configuration file to write [rtr2-confg]? <cr>
Write file rtr2-confg on host 131.108.101.101?[confirm] <cr>
![OK]
copy startup-config slot0:router-confg
copy rcp
copy rcp startup-config
ip rcmd remote-username
show boot
Router# copy xmodem flash
Router# copy ymodem flash
startup-config
On all platforms except the Cisco 7000 series, Cisco 7200 series, and Cisco 7500 series, erases the startup configuration in NVRAM.
On the Cisco 7000, Cisco 7200, and Cisco 7500 series, erases or deletes the configuration pointed to by the CONFIG_FILE environment variable.
device
(Optional on the Cisco 7000 series but required on the Cisco 1600 series and Cisco 3600 series)
Device containing the file or partition you want to erase. You must enter a colon (:) after the device type.
Valid devices are as follows:
· flash---Internal Flash memory on the Cisco 3600 and Cisco 7000 series. This device is the initial default device. A Flash memory PC card on the Cisco 1600 series.
· slot0---PCMCIA slot on the Cisco 7000 series RP card. This device is the first PCMCIA slot on the Cisco 3600 series.
· slot1---The second PCMCIA slot on the Cisco 3600 series.
partition-number
(Optional) On the Cisco 3600 series, specifies the partition number of the Flash memory device that you want to erase, as opposed to erasing the entire volume at once.
filename
Name of the file to delete on the Cisco 7000 series only. The files can be of any type. This command does not support wildcards in the filename.
erase startup-config
erase slot0:myconfig
Router# erase flash:2
System flash directory, partition 2:
File Length Name/status
1 1711088 dirt/images/c3600-i-mz
[1711152 bytes used, 15066064 available, 16777216 total]
Erase flash device, partition 2? [confirm]
Are you sure? [yes/no]: yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
...erased
delete
show boot
show startup-config
undelete
no memory-size iomem packet-memory-percentage
packet-memory-percentage
Specifies the percent of DRAM that you want allocated to the packet memory. Your choices are 25, 30, 40, or 50 percent
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# memory-size iomem 40
Router(config)# exit
Router# copy running-config startup-config
Building configuration...
[OK]
Router# reload
rommon 1 > b
program load complete, entry point: 0x80008000, size: 0x32ea24
Self decompressing the image :
#######################################################################################
#######################################################################################
######################################################################## [OK]
Configured I/O memory percentage was too large; using 30 percent
no partition flash
no partition flash
partition-number
Number of partitions in Flash memory.
partition-size
(Optional) Size of the partition in megabytes. The number of partition size entries you set is equal to the number of specified partitions.
device
Device on the Cisco 1600 series and Cisco 3600 series containing the system image to load at startup. The colon (:) is required. Valid devices are as follows:
· flash---Internal Flash memory on the Cisco 3600 series. A Flash memory PC card on the Cisco 1600 series.
· slot0---First PCMCIA slot on the Cisco 3600 series. The Cisco 1600 series does not support slot0.
· slot1---Second PCMCIA slot on the Cisco 3600 series. The Cisco 1600 series does not support slot1.
are created.
partition flash 2 4 4
Router(config)# partition slot0: 2 8 8
Router(config)# partition slot0: 4
slot
(Optional) Specifies the backplane slot number and can be 0, 1, 2, 3, or 4.
port
(Optional) Specifies the port number of the controller and can be 0 or 1.
number
(Optional) Specifies the unit number of the controller and can be 0 or 1.
Router# show cont t1
T1 4/1 is up.
No alarms detected.
Version info: Slot 1, HW: 0, Firmware: 1, NEAT PLD: 0, NR Bus PLD:1 <-- new
Framing is ESF, Line Code is AMI, Clock Source is line
Data in current interval (0 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations 0 Slip Secs, 0 Fr Loss Secs,
0 Line Err Secs, 0 Degraded Mins 0 Errored Secs, 0 Bursty Err Secs,
0 Severely Err Secs, 0 Unavail Secs
Total Data (last 79 15 minute intervals):
0 Line Code Violations, 0 Path Code Violations, 0 Slip Secs, 0 Fr Loss Secs,
0 Line Err Secs, 0 Degraded Mins, 0 Errored Secs, 0 Bursty Err Secs,
0 Severely Err Secs, 0 Unavail Secs
Router#
Field
Description
T1 0/0 is up.
The T1 controller 0 in slot 0 is operating. The controller's state can be up, down, administratively down. Loopback conditions are shown by (Locally looped) or (Remotely Looped).
No alarms detected.
Any alarms detected by the controller are displayed here. Possible alarms are as follows:
Transmitter is sending remote alarm.
Transmitter is sending AIS.
Receiver has loss of signal.
Receiver is getting AIS.
Receiver has loss of frame.
Receiver has remote alarm.
Receiver has no alarms.
Data in current interval (725 seconds elapsed)
Shows the current accumulation period, which rolls into the 24 hour accumulation every 15 minutes. Accumulation period is from 1 to 900 seconds. The oldest 15 minute period falls off the back of the 24-hr accumulation buffer
Line Code Violations
Indicates the occurrence of either a Bipolar Violation (BPV) or Excessive Zeros (EXZ) error event.
Path Code Violations
Indicates a frame synchronization bit error in the D4 and E1-noCRC formats, or a CRC error in the ESF and E1-CRC formats.
Slip Secs
Indicates the replication or deletion of the payload bits of a DS1 frame. A slip may be performed when there is a difference between the timing of a synchronous receiving terminal and the received signal.
Fr Loss Secs
Indicates the number of seconds an Out Of Frame (OOF) error is detected.
Line Err Secs
Line Errored Seconds (LES) is a second in which one or more Line Code Violation errors are detected.
Degraded Mins
A Degraded Minute is one in which the estimated error rate exceeds 1E-6 but does not exceed 1E-3.
Errored Secs
In ESF and E1-CRC links, an Errored Second is a second in which one of the following are detected: one or more Path Code Violations; one or more Out of Frame defects; one or more Controlled Slip events; a detected AIS defect.
For D4 and E1-noCRC links, the presence of Bipolar Violations also triggers an Errored Second.
Bursty Err Secs
A second with fewer than 320 and more than 1 Path Coding Violation error, no Severely Errored Frame defects and no detected incoming AIS defects. Controlled slips are not included in this parameter.
Severely Err Secs
For ESF signals, a second with one of the following errors: 320 or more Path Code Violation errors; one or more Out of Frame defects; a detected AIS defect.
For E1-CRC signals, a second with one of the following errors: 832 or more Path Code Violation errors; one or more Out of Frame defects.
For E1-nonCRC signals, a second with 2048 Line Code Violations or more.
For D4 signals, a count of 1-second intervals with Framing Errors, or an Out of Frame defect, or 1544 Line Code Violations.
Unavail Secs
A count of the total number of seconds on the interface.
number
Interface number. The value is 0 through 7 if the router has one BRI NIM or 0 through 15 if the router has two BRI NIMs.
Router# show controllers bri 0
BRI unit 0
D Chan Info:
Layer 1 is ACTIVATED
idb 0x32089C, ds 0x3267D8, reset_mask 0x2
buffer size 1524
RX ring with 2 entries at 0x2101600 : Rxhead 0
00 pak=0x4122E8 ds=0x412444 status=D000 pak_size=0
01 pak=0x410C20 ds=0x410D7C status=F000 pak_size=0
TX ring with 1 entries at 0x2101640: tx_count = 0, tx_head = 0, tx_tail = 0
00 pak=0x000000 ds=0x000000 status=7C00 pak_size=0
0 missed datagrams, 0 overruns, 0 bad frame addresses
0 bad datagram encapsulations, 0 memory errors
0 transmitter underruns
B1 Chan Info:
Layer 1 is ACTIVATED
idb 0x3224E8, ds 0x3268C8, reset_mask 0x0
buffer size 1524
RX ring with 8 entries at 0x2101400 : Rxhead 0
00 pak=0x421FC0 ds=0x42211C status=D000 pak_size=0
01 pak=0x4085E8 ds=0x408744 status=D000 pak_size=0
02 pak=0x422EF0 ds=0x42304C status=D000 pak_size=0
03 pak=0x4148E0 ds=0x414A3C status=D000 pak_size=0
04 pak=0x424D50 ds=0x424EAC status=D000 pak_size=0
05 pak=0x423688 ds=0x4237E4 status=D000 pak_size=0
06 pak=0x41AB98 ds=0x41ACF4 status=D000 pak_size=0
07 pak=0x41A400 ds=0x41A55C status=F000 pak_size=0
TX ring with 4 entries at 0x2101440: tx_count = 0, tx_head = 0, tx_tail = 0
00 pak=0x000000 ds=0x000000 status=5C00 pak_size=0
01 pak=0x000000 ds=0x000000 status=5C00 pak_size=0
02 pak=0x000000 ds=0x000000 status=5C00 pak_size=0
03 pak=0x000000 ds=0x000000 status=7C00 pak_size=0
0 missed datagrams, 0 overruns, 0 bad frame addresses
0 bad datagram encapsulations, 0 memory errors
0 transmitter underruns
B2 Chan Info:
Layer 1 is ACTIVATED
idb 0x324520, ds 0x3269B8, reset_mask 0x2
buffer size 1524
RX ring with 8 entries at 0x2101500 : Rxhead 0
00 pak=0x40FCF0 ds=0x40FE4C status=D000 pak_size=0
01 pak=0x40E628 ds=0x40E784 status=D000 pak_size=0
02 pak=0x40F558 ds=0x40F6B4 status=D000 pak_size=0
03 pak=0x413218 ds=0x413374 status=D000 pak_size=0
04 pak=0x40EDC0 ds=0x40EF1C status=D000 pak_size=0
05 pak=0x4113B8 ds=0x411514 status=D000 pak_size=0
06 pak=0x416ED8 ds=0x417034 status=D000 pak_size=0
07 pak=0x416740 ds=0x41689C status=F000 pak_size=0
TX ring with 4 entries at 0x2101540: tx_count = 0, tx_head = 0, tx_tail = 0
00 pak=0x000000 ds=0x000000 status=5C00 pak_size=0
01 pak=0x000000 ds=0x000000 status=5C00 pak_size=0
02 pak=0x000000 ds=0x000000 status=5C00 pak_size=0
03 pak=0x000000 ds=0x000000 status=7C00 pak_size=0
0 missed datagrams, 0 overruns, 0 bad frame addresses
0 bad datagram encapsulations, 0 memory errors
0 transmitter underruns
router# show controller b 0
BRI unit 0:
Layer 1 is ACTIVATED. (ISDN L1 State F7)
D Channel Information:
idb at 0x2089024, driver data structure at 0x20993DC
Siemens Chip Version 0x0
SIEMENS Registers:
Status Register [STAR]=0x48, Mode Register [MODE]=0xC9
Serial Port Control Register [SPCR]=0x0
Additional Feature Register [ADF2]=0x80
RX Buffer Descriptor is at 0xFF005E0, Buffer size 1524
pak=0x209AF04 data_ptr=0x2195928 partial_size=0x0
TX Buffer Descriptor is at 0xFF005EA
pak=0x0 data_ptr=0x0 partial_size=0x0
0 missed datagrams, 0 overruns
0 bad datagram encapsulations, 0 memory errors
0 transmitter underruns
B1 Channel Information:
Using SCC2, Microcode ver 3
idb at 0x208D508, driver data structure at 0x2098F6C
SCC Registers:
General [GSMR]=0x2:0x00000000, Protocol-specific [PSMR]=0x0
Events [SCCE]=0x0000, Mask [SCCM]=0x0000, Status [SCCS]=0x0006
Transmit on Demand [TODR]=0x0, Data Sync [DSR]=0x7E7E
SCC GENERAL PARAMETER RAM (at 0xFF00D00)
Rx BD Base [RBASE]=0x4C0, Fn Code [RFCR]=0x18
Tx BD Base [TBASE]=0x500, Fn Code [TFCR]=0x18
Max Rx Buff Len [MRBLR]=1524
Rx State [RSTATE]=0x18008240, BD Ptr [RBPTR]=0x4F8
Tx State [TSTATE]=0x18004348, BD Ptr [TBPTR]=0x500
SCC HDLC PARAMETER RAM (at 0xFF00D38)
CRC Preset [C_PRES]=0xFFFF, Mask [C_MASK]=0xF0B8
Errors: CRC [CRCEC]=0, Aborts [ABTSC]=0, Discards [DISFC]=0
Nonmatch Addr Cntr [NMARC]=0
Retry Count [RETRC]=0
Max Frame Length [MFLR]=1524
Rx Int Threshold [RFTHR]=0, Frame Cnt [RFCNT]=65497
User-defined Address 0000/0000/0000/0000
User-defined Address Mask 0x0000
RX ring with 8 entries at 0xFF004C0, Buffer size 1524
Rxhead = 0xFF004C0 (0), Rxp = 0x2098F88 (0)
00 pak=0x20FCED4 buf=0x21995A0 status=9000 pak_size=0
01 pak=0x20FCD24 buf=0x21A7358 status=9000 pak_size=0
02 pak=0x20FB5D4 buf=0x21A6CA0 status=9000 pak_size=0
03 pak=0x2100B08 buf=0x21A65E8 status=9000 pak_size=0
04 pak=0x20E2D64 buf=0x219DF88 status=9000 pak_size=0
05 pak=0x20F4BC0 buf=0x21A5F30 status=9000 pak_size=0
06 pak=0x20DA86C buf=0x2198EE8 status=9000 pak_size=0
07 pak=0x20FF48C buf=0x2199C58 status=B000 pak_size=0
TX ring with 2 entries at 0xFF00500, tx_count = 0
tx_head = 0xFF00500 (0), head_txp = 0x2098FE4 (0)
tx_tail = 0xFF00500 (0), tail_txp = 0x2098FE4 (0)
00 pak=0x0000000 buf=0x0000000 status=0000 pak_size=0
01 pak=0x0000000 buf=0x0000000 status=2000 pak_size=0
0 missed datagrams, 0 overruns
0 bad datagram encapsulations, 0 memory errors
0 transmitter underruns
B2 Channel Information:
Using SCC4, Microcode ver 3
idb at 0x2091AAC, driver data structure at 0x20991A4
SCC Registers:
General [GSMR]=0x2:0x00000000, Protocol-specific [PSMR]=0x0
Events [SCCE]=0x0000, Mask [SCCM]=0x000F, Status [SCCS]=0x0000
Transmit on Demand [TODR]=0x0, Data Sync [DSR]=0x7E7E
SCC GENERAL PARAMETER RAM (at 0xFF00F00)
Rx BD Base [RBASE]=0x580, Fn Code [RFCR]=0x18
Tx BD Base [TBASE]=0x5C0, Fn Code [TFCR]=0x18
Max Rx Buff Len [MRBLR]=1524
Rx State [RSTATE]=0x0, BD Ptr [RBPTR]=0x580
Tx State [TSTATE]=0x4000, BD Ptr [TBPTR]=0x5C0
SCC HDLC PARAMETER RAM (at 0xFF00F38)
CRC Preset [C_PRES]=0xFFFF, Mask [C_MASK]=0xF0B8
Errors: CRC [CRCEC]=0, Aborts [ABTSC]=0, Discards [DISFC]=0
Nonmatch Addr Cntr [NMARC]=0
Retry Count [RETRC]=0
Max Frame Length [MFLR]=1524
Rx Int Threshold [RFTHR]=0, Frame Cnt [RFCNT]=0
User-defined Address 0000/0000/0000/0000
User-defined Address Mask 0x0000
RX ring with 8 entries at 0xFF00580, Buffer size 1524
Rxhead = 0xFF00580 (0), Rxp = 0x20991C0 (0)
00 pak=0x20D76FC buf=0x2193790 status=9000 pak_size=0
01 pak=0x209A4B4 buf=0x21930D8 status=9000 pak_size=0
02 pak=0x20FF63C buf=0x2198830 status=9000 pak_size=0
03 pak=0x20F8430 buf=0x2198178 status=9000 pak_size=0
04 pak=0x20F8280 buf=0x2197AC0 status=9000 pak_size=0
05 pak=0x20FC400 buf=0x2197408 status=9000 pak_size=0
06 pak=0x20F5280 buf=0x219C4A8 status=9000 pak_size=0
07 pak=0x20F50D0 buf=0x219ECF8 status=B000 pak_size=0
TX ring with 2 entries at 0xFF005C0, tx_count = 0
tx_head = 0xFF005C0 (0), head_txp = 0x209921C (0)
tx_tail = 0xFF005C0 (0), tail_txp = 0x209921C (0)
00 pak=0x0000000 buf=0x0000000 status=0000 pak_size=0
01 pak=0x0000000 buf=0x0000000 status=2000 pak_size=0
0 missed datagrams, 0 overruns
0 bad datagram encapsulations, 0 memory errors
0 transmitter underruns
Field
Description
BRI unit 0
Interface type and unit number.
Chan Info
D and B channel numbers.
Layer 1 is ACTIVATED
Status can be DEACTIVATED, PENDING ACTIVATION, or ACTIVATED.
idb
ds
reset_mask
Information about internal data structures and parameters.
Siemens Chip Version 0x0
Information about ISDN tranceiver internals.
buffer size
Number of bytes allocated for buffers.
RX ring with - entries at -
Information about the Receiver Queue.
Rxhead
Start of the Receiver Queue.
pak
ds
status
pak_size
Information about internal data structures and parameters.
Using SCC2, Microcode ver 3
Information about usage of internal hardware.
SCC Registers
Information about internal hardware registers.
TX ring with - entries at -
Information about the Transmitter Queue.
tx_count
Number of packets to transmit.
tx_head
Start of the transmit list.
tx_tail
End of the transmit list.
missed datagrams
Incoming packets missed due to internal errors.
overruns
Number of times the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
bad frame addresses
Frames received with a cyclic redundancy check (CRC) error and noninteger number of octets.
bad datagram encapsulations
Packets received with bad encapsulation.
memory errors
Internal direct memory access (DMA) memory errors.
transmitter underruns
Number of times that the transmitter has been running faster than the router can handle.
device
(Required on the Cisco 1600 series and Cisco 3600 series but optional elsewhere) Specifies the device about which to show Flash information. You must enter a colon (:) after the device type that you specify.
Different routers and access servers use different device types, so read each device description below carefully. For example, the Cisco 1600 series supports only the flash device.
Valid devices are as follows:
· flash---Internal Flash memory in the Cisco 3600 series. A Flash memory PC card on the Cisco 1600 series.
· slot0---PCMCIA slot on the Cisco 7000 series or the first PCMCIA slot on the Cisco 3600 series, Cisco 7200 series, and Cisco 7500 series.
· slot1---Second PCMCIA slot on the Cisco 3600 series, Cisco 7200 series, and Cisco 7500 series.
· bootflash---Internal Flash memory in the Cisco 7200 series and Cisco 7500 series. The Cisco 3600 series does not support bootflash memory.
· 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.
all
(Optional) On all platforms except the Cisco 7000 series PCMCIA slot, Cisco 7200 series, and Cisco 7500 series, all shows complete information about Flash memory, including information about the individual ROM devices in Flash memory and the names and sizes of all system image files stored in Flash memory, including those that are invalidated.
On the Cisco 7000 series PCMCIA slot, Cisco 7200 series, and Cisco 7500 series, all shows the following information:
· The same information as that displayed by the dir command when you use the /all and /long keywords together.
· The same information as that displayed by the filesys keyword.
· The same information as that displayed by the chips keyword.
chips
(Optional) Shows information per partition and per chip, including which bank the chip is in plus its code, size, and name.
detailed
(Optional) Shows detailed file directory information per partition, including file length, address, name, Flash checksum, computer checksum, bytes used, bytes available, total bytes, and bytes of system Flash memory.
err
(Optional) Shows write or erase failures in the form of number of retries.
partition number
(Optional) Displays file memory information for a specific partition. If you specify the partition keyword, you must specify a partition number. You can use this keyword only when Flash memory has multiple partitions.
summary
(Optional) Shows summary information per partition, including the partition size, bank size, state, and method by which files can be copied into a particular partition. You can use this keyword only when Flash memory has multiple partitions.
filesys
(Optional) Shows the Device Info Block, the Status Info, and the Usage Info.
Router# show flash
4096K bytes of flash memory sized on embedded flash.
File name/status
0 ahp4/gs7-k
1 micro/eip1-0
2 micro/sp1-3
3 micro/trip1-1
4 micro/hip1-0
5 micro/fip1-1
6 flyspecked
7 spucode
8 tripucode
9 fipucode
10 eipucode
11 hipucode
12 sipucode
13 sp_q160-1
14 ahp4/sp160-3 [deleted]
15 ahp4/sp160-3
[682680/4194304 bytes free/total]
Field
Description
File
Number of file in Flash memory.
name/status
Files that currently exist in Flash memory.
bytes free
Amount of Flash memory remaining.
[deleted]
Flag indicating that another file exists with the same name or that the process has been abnormally terminated.
Router# show flash
System flash directory, partition 1:
File Length Name/status
1 3459720 master/igs-bfpx.100-4.3
[3459784 bytes used, 734520 available, 4194304 total]
4096K bytes of processor board System flash (Read Only)
System flash directory, partition 2:
File Length Name/status
1 3459720 igs-kf
[3459784 bytes used, 734520 available, 4194304 total]
4096K bytes of processor board System flash (Read/Write)
Router# show flash all
4096K bytes of flash memory sized on embedded flash.
Chip socket code bytes name
0 U63 89BD 0x040000 INTEL 28F020
1 U62 89BD 0x040000 INTEL 28F020
2 U61 89BD 0x040000 INTEL 28F020
3 U60 89BD 0x040000 INTEL 28F020
4 U48 89BD 0x040000 INTEL 28F020
5 U47 89BD 0x040000 INTEL 28F020
6 U46 89BD 0x040000 INTEL 28F020
7 U45 89BD 0x040000 INTEL 28F020
8 U30 89BD 0x040000 INTEL 28F020
9 U29 89BD 0x040000 INTEL 28F020
10 U28 89BD 0x040000 INTEL 28F020
11 U27 89BD 0x040000 INTEL 28F020
12 U17 89BD 0x040000 INTEL 28F020
13 U16 89BD 0x040000 INTEL 28F020
14 U15 89BD 0x040000 INTEL 28F020
15 U14 89BD 0x040000 INTEL 28F020
Flash file directory:
File name/status
addr length fcksum ccksum
0 gs7-k
0x12000080 2601100 0x4015 0x4015
1 micro/eip1-0
0x1227B14C 53364 0x0 0x0
2 micro/sp1-3
0x12288200 55418 0x0 0x0
3 micro/trip1-1
0x12295ABC 105806 0x0 0x0
4 micro/hip1-0
0x122AF84C 35528 0x0 0x0
5 micro/fip1-1
0x122B8354 97070 0x0 0x0
6 fsipucode
0x122CFEC4 6590 0x0 0x0
7 spucode
0x122D18C4 55418 0x0 0x0
8 tripucode
0x122DF180 105806 0x0 0x0
9 fipucode
0x122F8F10 97070 0x0 0x0
10 eipucode
0x12310A80 53330 0x60A1 0x60A1
11 hipucode
0x1231DB14 35528 0x0 0x0
12 sipucode
0x1232661C 54040 0x0 0x0
13 sp_q160-1
0x1233974 42912 0x0 0x0
14 ahp4/sp160-3 [deleted]
0x1233E154 55730 0x0 0x0
15 ahp4/sp160-3
0x1234BB48 55808 0x0 0x0
[682680/4194304 bytes free/total]
Field
Description
bytes of flash memory sized on embedded flash
Total amount of Flash memory present.
Chip
Identifies the ROM unit.
socket
Location of the ROM unit.
code
Vendor code identifying the vendor of the ROM unit.
bytes
Size of the ROM unit (in hex bytes).
name (in row beginning with Chip)
Vendor name and chip part number of the ROM unit.
security jumper, flash memory
Security jumper is/is not installed. Flash memory is programmable or read-only. If the security jumper is not installed, you will see the show flash display with a message indicating that the jumper is not installed.
File
Number of the system image file. If no filename is specified in the boot system flash command, the router boots the system image file with the lowest file number.
name/status
Filename and status of a system image file. The status [invalidated] appears when a file has been rewritten (recopied) into Flash memory. The first (now invalidated) copy of the file is still present within Flash memory, but it is rendered unusable in favor of the newest version. The [invalidated] status can also indicate an incomplete file that results from the user abnormally terminating the copy process, a network timeout, or a Flash memory overflow.
addr
Address of the file in Flash memory.
length
Size of the system image file (in bytes).
fcksum
Checksum recorded in Flash memory.
ccksum
Computer checksum.
[deleted]
Flag indicating that another file exists with the same name or that process has been abnormally terminated.
bytes free/total
Amount of Flash memory used/total amount of Flash memory.
Router# show flash all
4096K bytes of flash memory on embedded flash (in RP1).
security jumper(12V) is not installed,
flash memory is read-only.
file offset length name
0 0xDCD0 1903892 gs7-k [deleted]
1 0x1DEA24 1903912 gs7-k
[329908/4194304 bytes free]
Router# show flash all
System flash partition information:
Partition Size Used Free Bank-Size State Copy-Mode
1 4096K 3459K 637K 4096K Read Only RXBOOT-FLH
2 4096K 3224K 872K 4096K Read/Write Direct
System flash directory, partition 1:
File Length Name/status
addr fcksum ccksum
1 3459720 master/igs-bfpx.100-4.3
0x40 0x3DE1 0x3DE1
[3459784 bytes used, 734520 available, 4194304 total]
4096K bytes of processor board System flash (Read ONLY)
Chip Bank Code Size Name
1 1 89A2 1024KB INTEL 28F008SA
2 1 89A2 1024KB INTEL 28F008SA
3 1 89A2 1024KB INTEL 28F008SA
4 1 89A2 1024KB INTEL 28F008SA
Executing current image from System flash [partition 1]
System flash directory, partition2:
File Length Name/status
addr fcksum ccksum
1 3224008 igs-kf.100
0x40 0xEE91 0xEE91
[3224072 bytes used, 970232 available, 4194304 total]
4096K bytes of processor board System flash (Read/Write)
Chip Bank Code Size Name
1 2 89A2 1024KB INTEL 28F008SA
2 2 89A2 1024KB INTEL 28F008SA
3 2 89A2 1024KB INTEL 28F008SA
4 2 89A2 1024KB INTEL 28F008SA
Field
Description
Partition
Partition number in Flash memory.
Size
Size of partition in bytes.
Used
Number of bytes used in partition.
Free
Number of bytes free in partition.
Bank-Size
Size of bank in bytes.
State
State of the partition. It can be one of the following values:
Copy-Mode
Method by which the partition can be copied to:
Chip
Chip number.
Bank
Bank number.
Code
Code number.
Size
Size of chip.
Name
Name of chip.
Router# show flash chips
System flash partition 1:
4096K bytes of processor board System flash (Read ONLY)
Chip Bank Code Size Name
1 1 89A2 1024KB INTEL 28F008SA
2 1 89A2 1024KB INTEL 28F008SA
3 1 89A2 1024KB INTEL 28F008SA
4 1 89A2 1024KB INTEL 28F008SA
Executing current image from System flash [partition 1]
System flash partition 2:
4096K bytes of processor board System flash (Read/Write)
Chip Bank Code Size Name
1 2 89A2 1024KB INTEL 28F008SA
2 2 89A2 1024KB INTEL 28F008SA
3 2 89A2 1024KB INTEL 28F008SA
4 2 89A2 1024KB INTEL 28F008SA
Router# show flash detailed
System flash directory, partition 1:
File Length Name/status
addr fcksum ccksum
1 3224008 igs-kf.100
0x40 0xEE91 0xEE91
[3224072 bytes used, 970232 available, 4194304 total]
4096K bytes of processor board System flash (Read/Write)
System flash directory, partition 2:
File Length Name/status
addr fcksum ccksum
1 3224008 igs-kf.100
0x40 0xEE91 0xEE91
[3224072 bytes used, 970232 available, 4194304 total]
4096K bytes of processor board System flash (Read/Write)
Router# show slot0: detailed
PCMCIA Slot0 flash directory, partition 1:
File Length Name/status
addr fcksum ccksum
1 3142748 dirt/images/mars-test/c3600-j-mz.latest
0x40 0xB732 0xB732
[3142812 bytes used, 1051492 available, 4194304 total]
4096K bytes of processor board PCMCIA Slot0 flash (Read/Write)
PCMCIA Slot0 flash directory, partition 2:
File Length Name/status
addr fcksum ccksum
1 3141700 /tftpboot/images/c3600-j-mz
0x40 0x84E 0x84E
2 850 startup-config
0x2FF0C4 0x16 0x16
[3142680 bytes used, 1051624 available, 4194304 total]
4096K bytes of processor board PCMCIA Slot0 flash (Read/Write)
PCMCIA Slot0 flash directory, partition 3:
File Length Name/status
addr fcksum ccksum
1 1711088 /tftpboot/images/c3600-i-mz
0x40 0xF89A 0xF89A
[1711152 bytes used, 2483152 available, 4194304 total]
4096K bytes of processor board PCMCIA Slot0 flash (Read/Write)
PCMCIA Slot0 flash directory, partition 4:
File Length Name/status
addr fcksum ccksum
1 2205860 dirt/images/c3600-d-mz
0x40 0x9501 0x9501
2 1711128 dirt/images/c3600-i-mz.test
0x21A924 0xDFE9 0xDFE9
3 850 alz
0x3BC57C 0x16 0x16
[3918032 bytes used, 276272 available, 4194304 total]
4096K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Router# show flash err
System flash directory, partition 1:
File Length Name/status
1 37376 master/igs-bfpx.100-4.3 [invalid checksum]
[37440 bytes used, 4156864 available, 4194304 total]
4096K bytes of processor board System flash (Read/Write)
Chip Bank Code Size Name erase write
1 1 89A2 1024KB INTEL 28F008SA 0 0
2 1 89A2 1024KB INTEL 28F008SA 0 0
3 1 89A2 1024KB INTEL 28F008SA 0 0
4 1 89A2 1024KB INTEL 28F008SA 0 0
Executing current image from System flash [partition 1]
System flash directory, partition 2:
File Length Name/status
1 37376 master/igs-bfpx.100-4.3 [invalid checksum]
[37440 bytes used, 4156864 available, 4194304 total]
4096K bytes of processor board System flash (Read/Write)
Chip Bank Code Size Name erase write
1 2 89A2 1024KB INTEL 28F008SA 0 0
2 2 89A2 1024KB INTEL 28F008SA 0 0
3 2 89A2 1024KB INTEL 28F008SA 0 0
4 2 89A2 1024KB INTEL 28F008SA 0 0
Router# show flash: partition 2
System flash directory, partition 2:
File Length Name/status
1 1711088 dirt/images/c3600-i-mz
[1711152 bytes used, 15066064 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)
Router# show flash summary
System 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
Router# show slot1: summary
Partition Size Used Free Bank-Size State Copy Mode
1 4096K 0K 4095K 2048K Read/Write Direct
Router# cd slot1:
Router# show flash
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. 1 46A11866 2036C 4 746 May 16 1995 16:24:37 test
Router# show flash slot1:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. 1 46A11866 2036C 4 746 May 16 1995 16:24:37 test
Cyclops# show flash filesys slot1:
-------- F I L E S Y S T E M S T A T U S --------
Device Number = 1
DEVICE INFO BLOCK: test
Magic Number = 6887635 File System Vers = 10000 (1.0)
Length = 800000 Sector Size = 20000
Programming Algorithm = 4 Erased State = FFFFFFFF
File System Offset = 20000 Length = 7A0000
MONLIB Offset = 100 Length = A140
Bad Sector Map Offset = 1FFF8 Length = 8
Squeeze Log Offset = 7C0000 Length = 20000
Squeeze Buffer Offset = 7E0000 Length = 20000
Num Spare Sectors = 0
Spares:
STATUS INFO:
Writable
NO File Open for Write
Complete Stats
No Unrecovered Errors
Squeeze in progress
USAGE INFO:
Bytes Used = 36C Bytes Available = 79FC94
Bad Sectors = 0 Spared Sectors = 0
OK Files = 1 Bytes = 2EC
Deleted Files = 0 Bytes = 0
Files w/Errors = 0 Bytes = 0
Router# show flash chips bootflash:
******** RSP Internal Flash Bank -- Intel Chips ********
Flash SIMM Reg: 401
Flash SIMM PRESENT
2 Banks
Bank Size = 4M
HW Rev = 1
Flash Status Registers: Bank 0
Intelligent ID Code: 89898989 A2A2A2A2
Status Reg: 80808080
Flash Status Registers: Bank 1
Intelligent ID Code: 89898989 A2A2A2A2
Status Reg: 80808080
Router#
Router# cd bootflash:
Router# show flash all
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. FFFFFFFF 49B403EE 3D0510 21 3736719 May 30 1995 17:47:54 dirt/yanke/m
3865328 bytes available (3736848 bytes used)
-------- F I L E S Y S T E M S T A T U S --------
Device Number = 2
DEVICE INFO BLOCK: test
Magic Number = 6887635 File System Vers = 10000 (1.0)
Length = 800000 Sector Size = 40000
Programming Algorithm = 5 Erased State = FFFFFFFF
File System Offset = 40000 Length = 740000
MONLIB Offset = 100 Length = A270
Bad Sector Map Offset = 3FFFC Length = 4
Squeeze Log Offset = 780000 Length = 40000
Squeeze Buffer Offset = 7C0000 Length = 40000
Num Spare Sectors = 0
Spares:
STATUS INFO:
Writable
NO File Open for Write
Complete Stats
No Unrecovered Errors
Squeeze in progress
USAGE INFO:
Bytes Used = 390510 Bytes Available = 3AFAF0
Bad Sectors = 0 Spared Sectors = 0
OK Files = 1 Bytes = 390490
Deleted Files = 0 Bytes = 0
Files w/Errors = 0 Bytes = 0
******** RSP Internal Flash Bank -- Intel Chips ********
Flash SIMM Reg: 401
Flash SIMM PRESENT
2 Banks
Bank Size = 4M
HW Rev = 1
Flash Status Registers: Bank 0
Intelligent ID Code: 89898989 A2A2A2A2
Status Reg: 80808080
Flash Status Registers: Bank 1
Intelligent ID Code: 89898989 A2A2A2A2
Status Reg: 80808080
Cyclops#show flash chips bootflash:
******** RSP Internal Flash Bank -- Intel Chips ********
Flash SIMM Reg: 401
Flash SIMM PRESENT
2 Banks
Bank Size = 4M
HW Rev = 1
Flash Status Registers: Bank 0
Intelligent ID Code: 89898989 A2A2A2A2
Status Reg: 80808080
Flash Status Registers: Bank 1
Intelligent ID Code: 89898989 A2A2A2A2
Status Reg: 80808080
csm
(Optional) Shows the internal status of the call switching module.
log
(Optional) Shows the modem history event status performed on a manageable modem or group of modems.
slot/modem-port
(Optional) Specifies the location of a slot and modem port. If this number is not specified, statistics for all connected modems are displayed. Remember to include the forward slash (/) when entering this variable.
group number
(Optional) Specifies the location of a specific group of modems. If this number is not specified, statistics for all modems in the access server are displayed.
version
(Optional) Displays version information for modem firmware and boot code, and for modem hardware.
summary
(Optional) Displays a cumulative statistics report for all manageable modems dialing into and out of the network.
at-mode
(Optional) Displays all AT sessions connected to manageable modems.
AS5200# show modem
Inc calls Out calls Busied Failed No Succ
Mdm Usage Succ Fail Succ Fail Out Dial Answer Pct.
1/0 0% 0 0 0 0 0 0 0 0%
1/1 0% 0 0 0 0 0 0 0 0%
1/2 0% 0 0 0 0 0 0 0 0%
1/3 0% 0 0 0 0 0 0 0 0%
Field
Description
Mdm
Slot and modem port number. The following modem states can appear to the left of a slot/modem port number:
b---Modem was removed from service with the modem shutdown command or the modem busyout command.
R---Modem is held and isolated in a suspended state by the modem hold-reset command.
B---Modem is Bad*, Bad, or the downloaded firmware has failed.
D---Modem is currently downloading firmware.
T---Modem is conducting a back-to-back modem test.
*---Modem is connected or dialing.
Usage
Percentage of the total system uptime that all modems are in use.
Inc calls
Number of incoming calls that successfully and unsuccessfully connected to an available Cisco AS5200 integrated modem.
Out calls
Number of outgoing calls that successfully and unsuccessfully dialed out from an available Cisco AS5200 integrated modem.
Busied Out
Number of modems that have been manually removed from service.
Failed Dial
Number of modems that attempted to dial into the network but failed to make a connection.
No Answer
Number of modems that detected an incoming ring but failed to answer the call.
Succ Pct.
Successful connection percentage of total available modems.
AS5200# show modem 1/1
Mdm Typ Status Tx/Rx G Duration TX RX RTS CTS DSR DCD DTR
1/1 V34 Idle 1200/1200 0 01:39:59 x x x x x x x
Modem 1/1, AS5200 Manageable Modem
Firmware (Boot) Rev: 1.0.1 (0.0.2)
Modem config: Incoming and Outgoing
Protocol: Normal, Compression: None
Management config: status and AT session polling
TX signals: -17 dBm, RX signals: -33 dBm
Last clearing of "show modem" counters 00:11:34
0 incoming completes, 0 incoming failures,
0 outgoing completes, 0 outgoing failures,
0 failed dial attempts, 0 ring no answers, 0 busied outs
0 no dial tones, 0 dial timeouts, 0 watchdog timeouts
0 no carriers, 0 link failures, 0 resets
0 protocol timeouts, 0 protocol errors, 0 lost events
2400- 2400-14400 14400+
# of connections 0 0 0
Field
Description
Mdm
Slot and modem number.
Typ
Modulation type.
Status
Current status of the modem. Possible values include
Conn---Modem is connected to a remote host.
Bad---Inoperable state, which is configured by the modem bad command.
Bad*---Inoperable state, which is configured by the modem startup-test command during initial power-up testing.
Reset---Modem is in reset mode.
D/L---Modem is downloading firmware.
Bad FW---Downloaded modem firmware is not operational.
Busy---Modem is out of service and not available for calls.
Idle---Modem is ready for incoming and outgoing calls.
Tx/Rx
Transmission and receiving speed for the most recently connected call.
G
Modem group number assigned to the modem. The group number 0 means the modem is not part of any group.
Duration
Time duration of the current call or the last call.
Modem functions
The following modem functions are displayed on manageable modems. A field that is available and turned on is marked with an x. An unavailable field is marked with a dash (-).
TX---Transmit Data. The DTE transmits data to the DCE.
RX---Receive Data. The DCE receives data from the DTE.
RTS---Request To Send. The DTE signals to the DCE that the DTE accepts data into its buffers.
CTS---Clear To Send. The DCE signals to the DTE that the DCE accepts data into its buffers.
DSR---Data Set Ready. The modem is ready to start communication.
DCD---Data Carrier Detect. The DCE indicates to the DTE that a call is present and established with a remote modem. Dropping the DCD function terminates the session.
DTR---Data Terminal Ready. The DTE indicates to the DCE that it accepts calls.
Firmware
Installed modem firmware.
Modem config
Current modem configuration, which includes the fields Incoming, Outgoing, Incoming and Outgoing, and Unknown.
Protocol
Protocol the modem is running such as Normal, Direct, reliable/MNP, and reliable/LAPM (Link Access Procedure for Modems).
Compression
Compression algorithm running on the modem, such as None, V42bis, and MNP class 5.
Management config
Indicates if the modem is configured for out-of-band port polling.
TX signals
Analog signal levels that the modem transmits for signal-to-noise ratio.
RX signals
Analog signal levels that the modem receives for signal-to-noise ratio.
Last clearing of "show modem" counters
Last time the modem's counters were cleared using the clear modem counters command. A summary of modem events also appears.
# of connections
Speed summary of the number of calls that have connected since the system has been up. Speed categories are 2400, 2400 to 14400, and 14400+ bps.
AS5200# show modem 1/1
Mdm Typ Status Tx/Rx G Duration TX RX RTS CTS DSR DCD DTR
1/1 - Idle 19200/19200 0 00:01:05 - - - - - - -
Modem 1/1, AS5200 Non-Manageable Modem
Firmware (Boot) Rev: Unknown
Modem config: Unknown
Management config: Not Manageable Modem
Last clearing of "show modem" counters never
- incoming completes, - incoming failures
- outgoing completes, - outgoing failures,
0 failed dial attempts, 0 ring no answers, 0 busied outs
0 no dial tones, 0 dial timeouts, 0 watchdog timeouts
- no carriers, - link failures, 0 resets
- protocol timeouts, - protocol errors, - lost events
2400- 2400-14400 14400+
# of connections - - -
AS5200# show modem csm 1/2
MODEM_INFO: slot 1, port 2, unit 130, modem_mask=0x0004, modem_port_offset=0
tty_hwidb=0x00000000, modem_tty=0x004370A8, mgmt_tty=0x004370A8, modem_pool=0x0041D99C
csm_status(0): CSM_STATUS_UNLOCKED
csm_state(0x00000000)=CSM_OC_STATE, csm_event_proc=0x0005B448
invalid_event_count=0, wdt_timeout_count=0
wdt_timestamp_started is not activated
wait_for_dialing:False, wait_for_bchan:False
pri_chnl=TDM_ISDN_STREAM(s0, c0), modem_chnl=TDM_ISDN_STREAM(s0, c0)
dchan_idb_start_index=0, dchan_idb_index=0, call_id=0x0000, bchan_num=0
csm_event=CSM_EVENT_NONE, cause=0x0000, phone_num=
ring_indicator=0, oh_state=0, oh_int_enable=0, modem_reset=0
ring_no_answer=0, ic_failure=0, ic_complete=0
dial_failure=0, oc_failure=0, oc_complete=0
oc_busy=0, oc_no_dial_tone=0, oc_dial_timeout=0
remote_link_disc=0, busyout=0, modem_reset=0
call_duration_started=00:00:00, call_duration_ended=00:00:00,
total_call_duration=00:00:00
The calling party phone number = 4082968388
The called party phone number = 4085267406
Field
Description
MODEM_INFO
Displays internal data structure information.
csm_status
Displays the status of the call switching module. Possible displays include unlocked, active call, busyout req, shutdown, bad modem, modem hold, back-to-back, file downloading, and reset.
csm_state
Displays the current state of the call switching module. Possible states include idle and connected. Incoming calls are marked IC and outgoing calls are marked OC.
Modem counters
Counters for different modem events.
The calling party phone number
The called party phone number
Phone numbers for the dialing integrated modem and the remote modem.
AS5200# show modem log 1/1
Modem 1/1 Events Log:
00:02:41: Startup Response: Brasil Modem
Modem (boot) firmware = 1.0.23 (1.0.5)
00:02:41: Control Reply: 0xFE01
00:02:41: RS232 event:
RTS=On, DTR=Off, CTS=On
DSR=On, DCD=On, RI=Off, TST=Off
changes: RTS=No change, DTR=Changed, CTS=Changed
changes: DSR=Changed, DCD=Changed, RI=No change, TST=No change
00:02:41: Modem Activity event: Data Active
00:02:41: RS232 event:
RTS=On, DTR=Off, CTS=On
DSR=On, DCD=On, RI=Off, TST=Off
changes: RTS=No change, DTR=No change, CTS=No change
changes: DSR=No change, DCD=No change, RI=No change, TST=No change
00:02:42: Modem State event: Idle
00:02:42: End connection event: Retransmits for MNP block (TX/RX) = 0/0
Duration = 0:00:00, Number of TX/RX char = 0/0
Local Disc Reason = Unknown, Remote Disc Reason = Unknown
00:02:29: DTR event: DTR On
00:02:29: RS232 event:
RTS=On, DTR=On, CTS=On
DSR=On, DCD=On, RI=Off, TST=Off
changes: RTS=No change, DTR=Changed, CTS=No change
changes: DSR=No change, DCD=No change, RI=No change, TST=No change
00:02:34: ISDN outgoing called number: 16664200
00:02:34: Modem State event: Dialing/Answering
00:02:22: Modem State event: Waiting for Carrier
00:01:58: Modem State event: Connected
00:01:58: Connection event: TX/RX Speed = 26400/26400, Modulation = V34
Direction = Originate, Protocol = reliable/MNP, Compression = V42bis
00:01:58: Modem Analog signal event: TX = -13, RX = -14, Signal to noise = -40
00:01:58: RS232 event:
RTS=On, DTR=On, CTS=On
DSR=On, DCD=Off, RI=Off, TST=Off
changes: RTS=No change, DTR=No change, CTS=No change
changes: DSR=No change, DCD=Changed, RI=No change, TST=No change
00:00:57: Modem State event: Disconnecting
00:00:57: Modem Activity event: Data Active
00:00:57: End connection event: Retransmits for MNP block (TX/RX) = 0/0
Duration = 0:00:59, Number of TX/RX char = 30/2061
Local Disc Reason = Remote Link Disc, Remote Disc Reason = DTR Drop
00:00:57: Modem State event: Idle
AS5200# show modem summary
Incoming calls Outgoing calls Busied Failed No Succ
Usage Succ Fail Avail Succ Fail Avail Out Dial Ans Pct.
5% 2 0 12 0 0 0 0 0 0 100%
Fields
Descriptions
Incoming and Outgoing calls
Calls dialing into and out of the modem.
Busied Out
Total number of times the modems were taken out of service with the modem busy command or the modem shutdown command.
Failed Dial
Total number of attempts the modems did not hang up or there was no dial tone.
No Ans
Total number of times call ringing was detected, but the calls were not answered by a modem.
Succ Pct.
Successful connection percentage of total available modems.
AS5200# show modem group 1
Incoming calls Outgoing calls Busied Failed No Succ
Grp Usage Succ Fail Avail Succ Fail Avail Out Dial Ans Pct.
1 0% 0 0 24 0 0 24 0 0 0 0%
Modem Group 1: 1/0, 1/1, 1/2, 1/3, 1/4, 1/5, 1/6, 1/7, 1/8, 1/9, 1/10, 1/11, 1/12, 1/13,
1/14, 1/15, 1/16, 1/17, 1/18, 1/19, 1/20, 1/21, 1/22, 1/23
Router> show modem version
Modem module Firmware Boot
Mdm Number Rev Rev
1/0 0 Unknown (NP) Unknown (NP)
1/1 0 Unknown (NP) Unknown (NP)
1/2 0 Unknown (NP) Unknown (NP)
1/3 0 Unknown (NP) Unknown (NP)
1/4 0 Unknown (NP) Unknown (NP)
1/5 0 1.0.23 1.0.5
1/6 0 1.0.23 1.0.5
1/7 0 1.0.23 1.0.5
1/8 0 1.0.23 1.0.5
1/9 0 1.0.23 1.0.5
1/10 0 1.0.23 1.0.5
1/11 0 1.0.23 1.0.5
1/12 1 1.0.23 1.0.5
1/13 1 1.0.23 1.0.5
1/14 1 1.0.23 1.0.5
1/15 1 1.0.23 1.0.5
1/16 1 1.0.23 1.0.5
1/17 1 1.0.23 1.0.5
1/18 1 1.0.23 1.0.5
1/19 1 1.0.23 1.0.5
1/20 1 1.0.23 1.0.5
1/21 1 1.0.23 1.0.5
1/22 1 1.0.23 1.0.5
1/23 1 1.0.23 1.0.5
2/0 0 1.0.23 1.0.5
2/1 0 1.0.23 1.0.5
2/2 0 1.0.23 1.0.5
2/3 0 1.0.23 1.0.5
2/4 0 1.0.23 1.0.5
2/5 0 1.0.23 1.0.5
2/6 0 1.0.23 1.0.5
2/7 0 1.0.23 1.0.5
2/8 0 1.0.23 1.0.5
2/9 0 1.0.23 1.0.5
2/10 0 1.0.23 1.0.5
2/11 0 1.0.23 1.0.5
2/12 1 1.0.23 1.0.5
2/13 1 1.0.23 1.0.5
2/14 1 1.0.23 1.0.5
2/15 1 1.0.23 1.0.5
2/16 1 1.0.23 1.0.5
2/17 1 1.0.23 1.0.5
2/18 1 1.0.23 1.0.5
2/19 1 1.0.23 1.0.5
2/20 1 1.0.23 1.0.5
2/21 1 1.0.23 1.0.5
2/22 1 1.0.23 1.0.5
2/23 1 1.0.23 1.0.5
Modem board HW version info:
Slot 0:
Carrier card:
hw version= 1, number_of_ports= 24, max_modules= 2, max_oob_ports= 2
Modem Module 0:
number_of_modems= 12, option_bits= 1,
rev_num= 02.00, vendor_model_number= 01,
vendor_banner= Microcom MNP10 V34 Modem
Modem Module 1:
number_of_modems= 12, option_bits= 1,
rev_num= 02.00, vendor_model_number= 01,
vendor_banner= Microcom MNP10 V34 Modem
Slot 2:
Carrier card:
hw version= 0, number_of_ports= 24, max_modules= 2, max_oob_ports= 2
Modem Module 0:
number_of_modems= 12, option_bits= 1,
rev_num= 02.00, vendor_model_number= 01,
vendor_banner= Microcom MNP10 V34 Modem
Modem Module 1:
number_of_modems= 12, option_bits= 1,
rev_num= 02.00, vendor_model_number= 01,
vendor_banner= Microcom MNP10 V34 Modem
Router>
Fields
Descriptions
Mdm
Slot and port number for the specified modem.
Modem module number
Module number associated with the carrier card.
Firmware Rev
Modem firmware version, or one of the following:
Boot Rev
Modem boot version, or one of the following:
Modem board HW version info:
Modem hardware board information.
Slot
Slot number used for the carrier card.
Carrier card
Modem carrier card.
Hw version
Modem carrier card hardware version.
number_of_ports
Maximum number of modem ports that can be installed in the carrier card.
max_modules
Maximum number of modem modules that can be installed in a carrier card.
max_oob_ports
Maximum out-of-band ports used in the carrier card.
Modem Module
Modem module.
number_of_modems
Number of modems installed in the modem module.
option_bits
Signal level of the modem A-law and the U_law.
rev_num
Modem module version number.
vendor_model_number
Vendor modem model number.
vendor_banner
Type of banner displayed by the modem vendor.
AS5200# show modem at-mode
Active AT-MODE management sessions:
Modem User's Terminal
1/1 0 cty 0
AS5200# show modem at-mode
Active AT-MODE management sessions:
Modem User's Terminal
traps
Enables all traps.
trap-type
(Optional) Type of trap to enable. If no type is specified, all traps are sent (including envmon and repeater). It can be one of the following values:
· bgp---send Border Gateway Protocol (BGP) state change traps.
· config---send configuration traps.
· frame-relay---send Frame Relay traps.
· isdn---send ISDN traps.
When the isdn trap-type is used, you can specify call-information to enable an SNMP ISDN call information trap for the ISDN MIB subsystem, or you can specify isdnu-interface to enable an SNMP ISDN U interface trap for the ISDN U interface MIB subsystem.
Use the no form of this command to disable ISDN call-information or isdnu-interface.
· envmon---send Cisco enterprise-specific environmental monitor traps when an environmental threshold is exceeded. When envmon is selected, you can specify a trap-option.
· repeater---send Ethernet hub repeaters. When repeater is selected, you can specify a trap-option.
trap-option
(Optional) When envmon is used, you can either enable a specific environmental trap type or accept all trap types from the environmental monitor system. If no option is specified, all environmental types are enabled. It can be one or more of the following values: voltage, shutdown, supply, fan, and temperature.
When repeater is used, you can specify the repeater option. If no option is specified, all repeater types are enabled. It can be one or more of the following values:
· health---enable IETF Repeater Hub MIB (RFC 1516) health trap.
· reset---enable IETF Repeater Hub MIB (RFC 1516) reset trap.
snmp-server enable trap frame-relay
snmp-server enable trap envmon temperature
snmp trap illegal-address †
no tftp-server flash [device:][partition-number:]filename (Cisco 1600 series and Cisco 3600 series only)
no tftp-server flash device:filename (Cisco 7000 series and Cisco 7500 series only)
flash
Specifies TFTP service of a file in Flash memory.
partition-number
(Optional) Specifies TFTP service of a file in the specified partition of Flash memory. If the partition number is not specified, the file in the first partition is used. You must enter a colon (:) after the partition number if a filename follows this option in the initial command line.
filename1
Name of a file in Flash or in ROM that the TFTP server uses in answering TFTP Read Requests.
alias
Specifies an alternate name for the file that the TFTP server uses in answering TFTP Read Requests.
filename2
Alternate name of the file that the TFTP server uses in answering TFTP Read Requests. A client of the TFTP server can use this alternate name in its Read Requests.
access-list-number
(Optional) Basic IP access-list number. Valid values are 0 to 99.
device
Specifies TFTP service of a file on a Flash memory device in the Cisco 1600 series, Cisco 3600 series, Cisco 7000 series, or Cisco 7500 series. The colon (:) is required. Only the flash: device is supported on the Cisco 1600 series.
Valid devices are as follows:
· flash---Internal Flash memory on the Cisco 3600 series and Cisco 7000 series. A Flash memory PC card on the Cisco 1600 series.
· bootflash---Internal Flash memory in the Cisco 7500 series. Bootflash is not included in the Cisco 3600 series routers.
· slot0---PCMCIA slot on the Cisco 7000 series RP card or the first PCMCIA slot on the Cisco 7500 series RSP card. The first PCMCIA slot on a Cisco 3600 series.
· slot1---Second PCMCIA slot on the Cisco 7500 series RSP card. The second PCMCIA slot on a Cisco 3600 series.
· 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.
filename
Name of the file on a Flash memory device that the TFTP server uses in answering a TFTP Read Request. Use this argument only with the Cisco 1600 series, Cisco 3600 series, Cisco 7000 series, and Cisco 7500 series.
rom
Specifies TFTP service of a file in ROM.
tftp-server flash version-10.3 22
tftp-server rom alias gs3-k.101
tftp-server flash slot0:version-11.0
router(config)# tftp-server flash 2:dirt/gate/c3640-i-mz
router(config)# tftp-server flash slot0:2:dirt/gate/c3640-j-mz
device
(Optional on the Cisco 7000, Cisco 7200, and Cisco 7500 but required on the Cisco 1600 series and Cisco 3600 series). Device containing the file whose checksum is being verified. You must enter a colon (:) after the device type that you specify.
Different routers and access servers use different device types, so read each device description carefully. For example, the Cisco 1600 series supports the flash device option only.
Valid devices are as follows:
· flash---Internal Flash memory in the Cisco 3600 and Cisco 7000 series. A Flash memory PC card on the Cisco 1600 series.
· bootflash---Internal Flash memory in the Cisco 7200 series and Cisco 7500 series. The Cisco 3600 series does not have bootflash memory.
· slot0---PCMCIA slot on the Cisco 7000 series or the first PCMCIA slot on the Cisco 7200, Cisco 7500, and Cisco 3600 series.
· slot1---Second PCMCIA slot on the Cisco 7200, Cisco 7500, and Cisco 3600 series.
· 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.
partition-number
(Optional on the Cisco 1600 series and Cisco 3600 series only) Specifies the partition number of the Flash memory that you want to erase, as opposed to erasing the entire volume. Enter a colon (:) after the partition number if a filename appears after this option in the initial command line.
filename
(Optional on the Cisco 3600 series but required elsewhere) Name of a file on the specified Flash device. The file can be of any type. The maximum filename length is 63 characters.
verify slot0:gsxx
Router# verify slot0:4
PCMCIA 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? alz
Verifying checksum for 'alz' (file # 3)... OK
copy rcp
ip rcmd remote-username
pwd
show flash
-c
Specifies CRC16 checksumming for each block, which is more sophisticated and thorough than the standard simple checksumming.
-y
Specifies a file transfer using the Ymodem protocol, which gives you a higher throughput. Ymodem uses 1024 byte blocks whereas just Xmodem uses 128 byte blocks. Except for on the Cisco 1600 series, the Ymodem protocol sends additional information to the router such as the name and size of the file being transferred and automatically uses CRC checksumming.
-r
Specifies copying the file to DRAM. The default is to Flash memory.
-e
(Optional for the Cisco 1600 series) Erases Flash memory before starting the download. If there are other Flash memory partitions, this option erases the first partition only.
-f
(Optional for the Cisco 1600 series) Erases the entire Flash memory.
-x
Specifies not launching the Cisco IOS image upon completion of the download. The image can then be launched with the ROM monitor launch command.
-s baud-rate
(Optional for the Cisco 1600 series) Sets the console port's baud rate for the Cisco 1600 series during the file transfer. Optional baud rates are 1200, 2400, 4800, 9600, 19200, 38400, and 115200 baud. The default baud rate is specifed in the configuration register.
filename
Specifies the filename to copy. This argument is ignored when the -r option is specified, since only one file can be copied to DRAM. On the Cisco 1600 series, files are loaded to the ROM for execution.
rommon > xmodem -c new-ios-image
Do 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]: yes
Ready to receive file new-IOS-image ...
number
Interface number 0 or 1.
performance-statistics
(Optional) Displays the CSU/DSU performance statistics for the past 24 hours. This keyword applies only to the fractional T1/T1 module.
interval range
(Optional) Specifies the number of 15-minute intervals displayed. You can choose a range from 1 to 96, where each value represents the CSU/DSU activity performed in that 15-minute interval. For example, a range of 2-3 displays the performance statistics for the intervals two and three.
Router#sho service-module s 1 performance-statistics 30-32
Total Data (last 58 15 minute intervals):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in current interval (131 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 30:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 31:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in Interval 32:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Router1#show service-module serial 0
Module type is T1/fractional
Hardware revision is B, Software revision is 1.1 ,
Image checksum is 0x2160B7C, Protocol revision is 1.1
Receiver has AIS alarm,
Unit is currently in test mode:
line loopback is in progress
Framing is ESF, Line Code is B8ZS, Current clock source is line,
Fraction has 24 timeslots (64 Kbits/sec each), Net bandwidth is 1536 Kbits/sec.
Last user loopback performed:
remote loopback
Failed to loopup remote
Last module self-test (done at startup): Passed
Last clearing of alarm counters 0:05:50
loss of signal : 1, last occurred 0:01:50
loss of frame : 0,
AIS alarm : 1, current duration 0:00:49
Remote alarm : 0,
Module access errors : 0,
Total Data (last 0 15 minute intervals):
Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Data in current interval (351 seconds elapsed):
1466 Line Code Violations, 0 Path Code Violations
25 Slip Secs, 49 Fr Loss Secs, 40 Line Err Secs, 1 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 49 Unavail Secs
Router1#show service-module serial 1
Module type is 4-wire Switched 56
Hardware revision is B, Software revision is 1.00,
Image checksum is 0x44453634, Protocol revision is 1.0
Connection state: active,
Receiver has loss of signal, loss of sealing current,
Unit is currently in test mode:
line loopback is in progress
Current line rate is 56 Kbits/sec
Last user loopback performed:
dte loopback
duration 00:00:58
Last module self-test (done at startup): Passed
Last clearing of alarm counters 0:13:54
oos/oof : 3, last occurred 0:00:24
loss of signal : 3, current duration 0:00:24
loss of sealing curren: 2, current duration 0:04:39
loss of frame : 0,
rate adaption attempts: 0,
Module type is 4-wire Switched 56K in switched mode,
Connection state: Connected (Originating End)
Receiver has no alarms.
Current line rate is 56 Kbits/sec and role is DSU side,
Last clearing of alarm counters 02:57:40
oos/oof : 0,
loss of signal : 0,
loss of sealing current: 0,
CSU/DSU loopback : 0,
loopback from remote : 0,
DTE loopback : 0,
line loopback : 0,
Field
Description
Module type
The CSU/DSU module installed in the router. The possible modules are T1/fractional, 2-wire switched 56-kbps, and 4-wire 56/64-kbps.
Receiver has AIS alarm
Alarms detected by the FT1/T1 CSU/DSU module or 2- and 4-wire 56/64-kbps CSU/DSU modules.
Possible switched 56k alarms are as follows:
Unit is currently in test mode
Loopback tests are in progress.
Framing is ESF
Indicates frame type used on the line. Can be extended super frame or super frame.
Line code is B8ZS
Indicated line-code type configured. Can be alternate mark inversion (AMI) or binary 8-zero substitution (B8ZS).
Current clock source is line
Clock source configured on the line, which can be supplied by the service provider (line) or the integrated CSU/DSU module (internal).
Fraction has 24 timeslots
Number of timeslots defined for the FT1/T1 module, which can range from 1 to 24.
Net bandwidth
Total bandwidth of the line (for example, 24 timeslots multiplied by 64 kbps equals a bandwidth of 1536 kbps).
Last user loopback performed
Type and outcome of the last performed loopback.
Last module self-test (done at startup): passed
Status of the last self-test performed on an integrated CSU/DSU module.
Last clearing of alarm counters
List of network alarms that were detected and cleared on the CSU/DSU module.
Total data
Data in current interval
Shows the current accumulation period, which rolls into the 24-hour accumulation every 15 minutes. The oldest 15-minute period falls off the back of the 24-hour accumulation buffer.
Line code violations
Indicates the occurrence of either a bi polar violation or excessive zeroes error event.
Path code violations
Indicates a frame synchronization bit error in the D4 and E1-no CRC formats or a CRC error in the ESF and E1-CRC formats.
Slip secs
Indicates the replication or detection of the payload bits of a DS1 frame. A slip may be performed when there is a difference between the timing of a synchronous receiving terminal and the received signal.
Fr loss secs
Indicates the number of seconds an out of frame error is detected.
Line err secs
Line errored seconds is a second in which one or more line code violation errors are detected.
Errored secs
In ESF and E1-CRC links, an errored second is a second in which one of the following is detected: one or more path code violations; one or more out of frame defects; one or more controlled slip events; a detected AIS defect.
For D4 and E1-no CRC links, the presence of bi polar violation also triggers an errored second.
Bursty err secs
A second with fewer than 320 and more than 1 path coding violation errors. No severely errored frame defects or incoming AIS defects are detected. Controlled slips are not included in this parameter.
Severely err secs
For ESF signals, a second with one of the following errors: 320 or more path-code violation errors; one or more out of frame defects; a detected AIS defect.
For D4 signals, a count of 1-second intervals with framing errors, or an out of frame defect, or 1544 line-code violations.
Unavail secs
Total time the line was out of service.