Table of Contents

Introduction
Platform Support
Interfaces Supported
New Software Features in Cisco IOS Release 11.1(7)AA
Display System Image and Configuration Information
Partition Flash Memory
Copy a File into a Flash Partition

Cisco 1600 and Cisco 3600 Copy TFTP Examples
Cisco 3600 Copy rcp Examples

Erase the Configuration Information
Copy a Configuration File Directly to the Startup Configuration
Copy System Images Between Flash Memory Devices

Copy Images Between Flash Devices Examples

Copy from a TFTP Server to Flash Memory

Copy TFTP Server Examples

Copy from an rcp Server to Flash Memory

Copy rcp Server Examples

Copy from a MOP Server to Flash Memory
Copy from Flash Memory to a TFTP Server
Copy from Flash Memory to an rcp Server
Configure a Flash Partition as a TFTP Server
Load from Flash Memory
Manually Load a System Image from the ROM Monitor

Manually Boot from Flash

Cisco 3600 Series Examples

Manually Boot from a Network File

Configure the Router to Automatically Boot from an Image in Flash Memory
Download a System Image Using Xmodem or Ymodem

Cisco IOS Xmodem Example
ROM Monitor Xmodem Example

Reallocate Packet Memory and Processor Memory

I/O Memory Example

Obtaining Service and Support
Cisco Connection Online

Configuration Notes for Cisco IOS Release 11.1—Cisco CPA1600 and Cisco CPA3600 Series Routers

November 4, 1996

This document provides additional information about Cisco Internetwork Operating System (Cisco IOS) support of Cisco CPA1600 series routers and Cisco CPA3600 series routers. Use this document to complement the information contained in the following two documents:

• Release Notes for Cisco IOS 11.1— Cisco CPA1600 Series Routers
  
  
• Release Notes for Cisco IOS 11.1— Cisco CPA3600 Series Routers
  
  

Introduction

These configuration notes contain the following sections:

• Platform Support
  
  
• Interfaces Supported
  
  
• New Software Features in Cisco IOS Release 11.1(7)AA
  
  
• Display System Image and Configuration Information
  
  
• Partition Flash Memory
  
  
• Copy a File into a Flash Partition
  
  
• Erase the Configuration Information
  
  
• Copy a Configuration File Directly to the Startup Configuration
  
  
• Copy System Images Between Flash Memory Devices
  
  
• Copy from a TFTP Server to Flash Memory
  
  
• Copy from an rcp Server to Flash Memory
  
  
• Copy from a MOP Server to Flash Memory
  
  
• Copy from Flash Memory to a TFTP Server
  
  
• Copy from Flash Memory to an rcp Server
  
  
• Configure a Flash Partition as a TFTP Server
  
  
• Load from Flash Memory
  
  
• Manually Load a System Image from the ROM Monitor
  
  
• Configure the Router to Automatically Boot from an Image in Flash Memory
  
  
• Reallocate Packet Memory and Processor Memory
  
  
• Obtaining Service and Support
  
  
• Cisco Connection Online
  
  

Platform Support

Cisco IOS Release 11.1(7)AA supports the following routers and access servers:

• Cisco CPA1600 series routers—Cisco 1601, Cisco 1602, Cisco 1603, and Cisco 1604
  
  
• Cisco CPA3600 series routers—Cisco 3640 and Cisco 3620
  
  

Interfaces Supported

Table 1 lists the interfaces supported in Cisco IOS Release 11.1(7)AA:

New Software Features in Cisco IOS Release 11.1(7)AA

Cisco IOS Release 11.1(7)AA adds support for the following new platforms and features:

• Cisco 1600 series routers, include the Cisco 1601, Cisco 1602, Cisco 1603, and Cisco 1604 routers. The Cisco 1600 series is a family of modular access routers for small offices connecting Ethernet LANs to the Internet and corporate intranets over one or two WAN connections. Interfaces supported include 10BaseT, asynchronous and synchronous serial, synchronous serial with integrated 56-kbps CSU/DSU, ISDN BRI S/T, and ISDN BRI U.
  
  
• Cisco 3600 series routers, which include the Cisco 3640 and Cisco 3620 routers. As modular solutions, these routers enable corporations to increase dialup density and take advantage of various current and emerging WAN technologies and networking capabilities such as dialup connectivity, LAN to LAN routing, data and access security, WAN optimization, and multimedia features.
  
  

  The Cisco 3640 is equipped with four network module slots. The Cisco 3620 has two slots. Each network module slot accepts a variety of network module interface cards, including LAN and WAN mixed media cards supporting Ethernet, Token Ring, and a variety of WAN technologies. These cards provide the foundation of LAN and WAN connectivity on a single network module. Additional applications are supported with a series of network module cards offering asynchronous and synchronous serial, ISDN PRI, and ISDN BRI interfaces. (See Table 1.)

The documentation in the sections below supplements the Configuring Fundamentals Configuration Guide. Included are configuration tasks and command reference documentation for the new features available on supported platforms. Pointers to chapter titles and sections are included so that you can update your printed manual.

On page 1-68 in the Configuration Fundamentals Configuration Guide, update the "Display System Image and Configuration Information" section with the corresponding new sections:

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:

Refer to the Configuration Fundamentals Command Reference publication for examples of these commands.

You can also use the o command in ROM monitor mode to list the configuration register settings on some models.

The Flash memory content listing does not include the checksum of individual files. To recompute and verify the image checksum when the image has been copied into Flash memory, complete the following task in EXEC mode:

You can verify the checksum of individual files on a Flash memory device on Cisco 1600 series and Cisco 3600 series routers. On the Cisco 3600 series, you can verify the checksum of a file located in internal Flash memory (flash:) or in 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 internal flash memory (flash:) only. 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.

On page 1-105 of the Configuration Fundamentals Configuration Guide, update the "Partition Flash Memory" section with the following new section:

Partition Flash Memory

To partition Flash memory, perform the following task in global configuration mode:

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.

Update the "Copy a File into a Flash Partition" section on page I-106 of the Configuration Fundamentals Configuration Guide with the following 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:

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:

• None—There is no known way to copy into the partition.
  
  
• RXBOOT-Manual—You must manually reload to the rxboot image in ROM to copy the image.
  
  
• RXBOOT-FLH—The copy is done automatically via the Flash load helper software in boot ROMs.
  
  
• Direct—The copy can done directly.
  
  

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:

• ?—Display the directory listings of all partitions.
  
  
• ?1—Display the directory of the first partition.
  
  
• ?2—Display the directory of the second partition.
  
  
• q—Quit the copy command.
  
  

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:

Step 1   Enter the copy tftp flash: command, and include the destination partition and destination filename options in the initial command line:

In this example, the system reports that one partition and one file exist in internal Flash memory:

---

Note The destination filename must be an alphanumeric expression. For example, the filename 1 is invalid.

---

Step 2   Enter or confirm the IP address of the remote TFTP server. The Cisco IOS software may show the IP address of the most recently used remote server in brackets ([]), if a remote server was recently accessed. In this case, press Enter.

Step 3   Enter or confirm the source filename on the remote server. If you entered a destination filename in the initial command line, this filename is interpreted as the source filename by default. In this case, press Enter. If the source filename exists several directory levels into the UNIX server, you must enter the complete UNIX path name such as newios/3600/c3600-i-mz after the question mark (?).

Step 4   Decide if you want to erase the existing files in Flash memory during the copy operation. Press Enter to confirm erasing the files. You are asked two times to confirm erasing the Flash twice.

The system software displays the copy operation to you a final time before the file is copied:

The system software loads, copies, and verifies the file from the remote server into the router. On the Cisco 3600 series routers, this file is copied into an internal Flash memory SIMM. On the Cisco 1600 series router, this file is copied into a Flash memory PC card. Depending on which platform you are using, the same flash keyword specifies two completely different device destination.

The duration of the copy operation is displayed in hours, minutes, and seconds:

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:

Step 1   Enter the copy tftp flash: command without the destination partition and destination filename options specified in the initial command line:

The contents of the system Flash memory are displayed. In this case, two partitions are present:

Step 2   Specify which partition on the local device you want to copy the remote file into. The first partition is the default. Press Enter to accept the default setting.

The file c3600-i-mz exists in this partition:

Step 3   Enter or confirm the IP address of the remote TFTP server. In this case, the system software automatically recalls that remote server 171.69.1.129 was the last remote device accessed by the router. Therefore it's displayed in brackets. Press Enter to accept the bracket entry.

Step 4   Specify the source filename. In this example, the UNIX path name images/3600/c3600-i-mz is entered to copy the file c3600-i-mz.

By default, the entire source path name is entered as the single destination filename. To shorten or change this filename, enter the new name after the question mark (?) and press Enter.

The remote file is accessed and loaded using Ethernet 1/0:

Step 5   Decide if you want to erase the existing files in Flash memory during the copy operation. Press Enter to confirm erasing the files. You are asked two times to confirm erasing the Flash:

The system software confirms the copy operation with you a final time before the Flash memory is erased and the file is copied:

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:

Step 1   Enter the copy rcp slot0: command. Since a destination partition and destination filename are not specified in the initial command line, you are prompted for these values during the copy operation.

The system displays four partitions with read and write permissions in the PC card.

Step 2   Specify which partition you want to copy the remote file into. The first partition is the default. Press Enter to accept the default setting:

The file c3600-j-mz exists in partition 1.

Step 3   Enter or confirm the IP address of the remote rcp server. The address of the last accessed server is displayed in brackets ([]). Confirm the displayed IP address by pressing Enter.

Step 4   Enter the UNIX path name that leads to the source file, which is c3600-i-mz in this example:

Step 5   Specify the destination filename. The Cisco IOS software uses the entire UNIX path that leads to the source file as the single destination filename by default. To shorten or change this filename, enter a new filename after the question mark (?) then press Enter.

Confirm erasing the entire contents of the Flash memory in the PC card. You are prompted three times before the copy operation is complete.

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:

Step 1   Enter the copy rcp slot0:3 command. The partition structure in your PC card may be different from the structure shown in this example. The 3 specifies the third partition in the PC card, which is used as the copy partition destination.

---

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

---

Step 2   Enter or confirm the IP address of the remote rcp server:

Step 3   Enter the source UNIX path name that leads to the file you want to copy:

Step 4   Specify the destination filename:

Step 5   Decide if you want to erase the contents of Flash memory and initiate the copy operation:

On page 1-68 of the Configuration Fundamentals Configuration Guide, update the "Clear the Configuration Information" section with the following new section:

Erase the Configuration Information

To erase a saved configuration from a specific Flash memory device on a Cisco 1600 or Cisco 3600 series router, complete the following task in EXEC mode:

For the device: argument on the Cisco 3600 series router, 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:). 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.

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

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 of the Configuration Fundamentals Configuration Guide, add the "Copy System Images Between Flash Memory Devices" section:

Copy System Images Between Flash Memory Devices

System images 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. Images are copied 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 on Cisco 3600 Series Routers

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:

Step 1   Enter the command that specifies the source and destination Flash devices for the copy operation:

The file structure for partition 1 of the internal Flash memory is displayed first.

The partition structure for the Flash memory PC card inserted in PCMCIA slot 0 is displayed next. In this case, a higher level display of the partitions is shown because no partition number is specified for the PC card in the initial command line.

Step 2   Specify which partition you want to copy the file into. The first partition is the default.

Step 3   Enter the UNIX path name that leads to the source file, which is new-ios in this example:

Step 4   Enter the destination filename that is copied on the PC card. The system software uses the specified source path name and filename as the default entry, which is shown in brackts ([]):

Step 5   Decide if you want to erase the existing Flash memory in the PC card:

Step 6   Confirm that the source filename, destination filename, and erase Flash options are correct:

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:

Step 1   Enter the command that specifies the source and destination Flash devices for the copy operation:

The contents of internal Flash memory are displayed.

Step 2   Specify which partition in internal Flash memory contains the source file. The default is the first partition.

The contents of the destination Flash memory on the PC card inserted in slot 1 is displayed:

Step 3   Specify the source filename, which is in internal Flash memory:

Step 4   Enter or confirm the destination filename, which is copied to the PC card. The source filename you entered in Step 3 is shown in brackets by default. Unless you specify otherwise, the source filename is used as the destination filename.

Step 5   Decide if you want to erase the existing Flash memory in the PC card:

On page 1-58 in the Configuration Fundamentals Configuration Guide, update 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 TFTP server to Flash memory, complete the following tasks:

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

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

The following example shows how to use the copy tftp flash command to copy a system image named gs7-k when Flash memory is too full to copy the file. The filename gs7-k can be in either lowercase or uppercase; the system sees GS7-K as gs7-k. If more than one file of the same name is copied to Flash, regardless of case, the last file copied becomes the valid file.

The exclamation point (!) indicates that the copy process is taking place. Each exclamation point (!) indicates that ten packets have been transferred successfully. A series of "V" characters indicates that a checksum verification of the image is occurring after the image is written to Flash memory.

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:

Step 1   Enter the copy tftp flash: command followed by the destination filename. The filename you enter is automatically entered in the source filename field.

The contents of internal Flash memory on the Cisco 3600 series is displayed. If you are using a Cisco 1600 series router, the contents of the Flash memory PC card is displayed.

Enter or confirm the IP address of the remote TFTP server. The system software automatically displays the IP address of the last accessed remote server by default.

Step 2   Enter or confirm the UNIX path name leading up to the source file on the remote server. By default the destination filename that you entered in the initial command line is shown in brackets ([]). To confirm this filename as the UNIX path and source filename, press Enter. In this case, a new entry is specified.

The file on the remote server is accessed and loaded on the router through Ethernet port 1/0.

Step 3   Decide if you want to erase the contents of the internal Flash memory device (Cisco 3600 series) or the Flash PC card (Cisco 1600 series):

Step 4   Confirm that your copy settings are correct.

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:

The exclamation point (!) indicates that the copy process is taking place. Each exclamation point (!) indicates that ten packets have been transferred successfully. A series of "V" characters indicates that a checksum verification of the image is occurring after the image is written to Flash memory.

In the following example, the Flash security jumper is not installed, so you cannot write files to Flash memory.

On page 1-61 of the Configuring 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

You can copy a system image from an rcp network server to Flash memory. For the rcp command to execute properly, an account must be defined on the network server for the remote username. You can override the default remote username sent on the rcp copy request by configuring the remote username. For example, if the system image resides in the home directory of a user on the server, you can specify that user's name as the remote username. The rcp protocol implementation copies the system image from the remote server relative to the directory of the remote username if the remote server has a directory structure, as do UNIX systems.

To copy a system image from an rcp server to Flash memory, complete the following tasks:

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:

Step 1   Enter the copy rcp flash: command. In this example, the partition number and destination filename is not specified in the initial command line.

The contents of the internal Flash memory (Cisco 3600 series) or the Flash memroy PC card (Cisco 1600 series) is displayed.

Step 2   Enter the IP address of the remote rcp server. The system software recalls the IP address of the last accessed remote device by default. To accept the IP address shown in the brackets ([]), press Enter:

Step 3   Enter the UNIX path name leading up to the source file on the remote server. If you enter a destination filename in the initial command line (Step 1), the filename is displayed here in brackets ([]).

Step 4   Specify the destination filename that will be created in the internal Flash memory (Cisco 3600 series) or the Flash memory PC card (Cisco 1600 series). The source filename you enter in Step 3 is shown here in brackets. In this case, the file is renamed to my-ios.

Step 5   Decide if you want to erase the contents of the Flash memory device during the copy operation:

Step 6   Confirm that the copy settings are correct:

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.

Step 1   Enter the copy rcp slot0: command followed by the destination partition and filename options. Include your own partition number and filename where appropriate.

The system software accesses partition 2 on the Flash memory PC card and displays its contents.

Step 2   Enter the IP address of the remote rcp server. Press Enter to accept the IP address shown in the brackets ([]).

Step 3   Enter or accept the UNIX path name that leads up to the source filename on the remote rcp server:

Step 4   Decide if you want to erase the contents of Flash memory on the PC card during the copy operation. Press Enter to erase the existing files.

Step 5   Confirm that the copy settings are correct:

The following example shows how to copy a system image named mysysim1 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.

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 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:

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.

On page 1-63 in the Configuration Fundamentals Configuration Guide, update the "Copy from a MOP Server to Flash Memory" section with the following new section:

Copy from a MOP Server to Flash Memory

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, update 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:

Step 1   Enter the copy slot0: tftp command. The source file is in a PC card inserted in PCMCIA slot 0.

The system software displays the contents of the PC card. If the partition number was specified in the initial command line, the software would display the contents of the specified partition only.

Step 2   Specify the partition that contains the source file. Partition 1 is the default setting.

The file your-ios is shown to exist in partition 1:

Step 3   Enter the IP address of the remote TFTP server. The system software displays the address of the last accessed server enclosed in brackets ([]) by default.

Step 4   Enter the source filename in partition 4 of the PC card.

Step 5   Enter the UNIX path name that leads up to the destination filename to be copied to the TFTP server:

Step 6   Confirm that the copy settings are correct:

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.

Step 1   Enter the copy slot0:2 tftp command. The PC card inserted in slot 0 contains the source file in partition 2.

Step 2   Enter or confirm the IP address of the remote TFTP server:

Step 3   Specify the source filename that resides in partition 2 of the Cisco 3600 series router:

Step 4   Specify the UNIX path name that leads to the destination file that is created on the TFTP server:

Step 1   Enter the copy slot0: tftp command with the source partition and filename options specified:

The system software does not display any of the Flash memory contents because all the required information is specified in the initial command line.

Step 2   Enter the IP address of the remote TFTP server:

Step 3   Enter the destination UNIX path name followed by the destination filename, which is copied to the remote server:

The following example uses the show flash all command to learn the name of the system image file and the copy flash tftp command to copy the system image to a TFTP server. The name of the system image file (xk09140z) is listed near the end of the show flash all output.

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.

Once you have configured Flash memory, you might want to configure the system (using the configure terminal command) with the no boot system flash configuration command to revert to booting from ROM. For example, you might want to revert to booting from ROM if you do not yet need this functionality, if you choose to boot from a network server, or if you do not have the proper image in Flash memory. After you enter the no boot system flash command, use the copy running-config startup-config command to save the new configuration command to the startup configuration.

On page 1-90 in the Configuration Fundamentals Configuration Guide, update 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:

Step 1   Enter the slot1: rcp command:

Step 2   Enter the IP address of the remote host:

Step 3   Specify the source file that you want to copy from the Flash memory PC card:

Step 4   Confirm or rename the UNIX destination path name and filename:

Step 5   Verify that the copy settings are correct:

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:

Step 1   Enter the copy slot1: rcp command with the partition number and filename options included:

Use you own partition number and filename where needed.

Step 2   Enter the IP address of the rcp server:

Step 3   Enter the destination path name and filename:

Step 4   Confirm that the copy operation information is correct:

On page I-107of 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, update the "Load from Flash Memory " section with the following new section:

Load from Flash Memory

Refer to the following sections to boot your Cisco 3600 from Flash. With a CSC-MC+ Flash memory card and CSC-MCI controller and appropriate cables, system software images can be written to Flash memory for booting. Depending on the hardware platform, Flash memory might be available as EPROMs, single in-line memory modules (SIMMs), or Flash memory cards. Check the appropriate hardware installation and maintenance guide for information about types of Flash memory available on a specific platform.

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.

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:

• Internal Flash memory
  
  
• A Flash memory PC card inserted in a PCMCIA slot
  
  
• A network server file
  
  

Cisco 3600 series routers do not use a dedicated boot helper image such as rxboot 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 memory device (for example, flash:, slot0:, and slot1:) specified by the boot command, whether the boot process is performed manually or automatically.

In Cisco 3600 series, no autobooting occurs and your configuration session is passed over to ROM monitor mode if the bootbits are set to 0 in the configuration register. If the bootbits are set to 1, the ROM monitor automatically boots the default boothelper 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 PCMCIA card inserted in slot 0. Finally, if the bootbits are set within the range of 2 to 15, the ROM monitor executes the boot commands set by the boot environment variable. This environment 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 memory devices: internal Flash memory, slot 0, and slot 1.

Manually Boot from Flash

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 3600 Series Examples

The following example enables the ROM monitor to boot the first file in the first partition of internal Flash memory:

The following 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 called 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.

Configure the Router to Automatically Boot from an Image in Flash Memory

To configure a router to automatically boot from an image in Flash memory, 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.

Cisco 3600 series routers do not support booting a Cisco IOS system image from boot flash memory. The possible boot variables correspond to internal Flash memory and Flash memory PC cards inserted in PCMCIA slots 0 or slot 1.

The following example shows how to configure the router to automatically boot from an image in Flash memory.

When you have successfully configured Flash memory, you might want to configure the system with the no boot system flash command to revert to booting from ROM. You might want to revert to booting from ROM if you do not yet need this functionality, if you choose to boot from a network server, or if you do not have the proper image in Flash memory.

On page 1-111 of the Configuration Fundamentals Configuration Guide, add the following new section:

Download a System Image Using Xmodem or Ymodem

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 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 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 can not 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 Router with Xmodem or Ymodem

Xmodem and Ymodem downloads occur very slowly. 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 memory 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:

Step 1   Place a Cisco IOS software image on the remote PC's hard drive. You can download an image from Cisco Connection Online or from a CD-ROM.

Step 2   Connect a modem from the AUX port of your Cisco 3600 series router to the standard telephone network. The AUX port is by default set to a speed of 9.6 Kbps, 2 stop bits, and no parity. You must have the modem-inout command configured on the router when using modems.

Step 3   At the EXEC prompt in the terminal emulator window of the remote PC, enter the copy xmodem flash command.

Step 4   Press the Return key to accept this Cisco IOS warning and specify if you want to use cyclic redundancy block checksumming (CRC), which verifies that your data has been correctly transferred from the PC to the router. If your PC does not support CRC checksumming, specify no at the prompt as shown in the example.

Step 5   Determine how many times the software receives a bad block of data before it declares the copy operation a failure. The [10] means that the default value is 10 retries. You can configure an unlimited number of retries. A higher number of retries may be needed for noisy telephone lines.

Step 6   Decide if you want the software to check if the file is a valid Cisco 3600 series image.

Once the transfer has begun and if the image is valid, the software then checks to see if enough Flash memory exists in the router to accommodate the transfer.

Step 7   Enter the destination filename. If you want the existing internal Flash memory erased before the file transfer, press the Return key.

Step 8   Start an Xmodem send operation on the PC terminal emulation software. Depending on the type of application you use, the emulation software may display the progress of the file transfer. If the software application supports Xmodem-1k (Xmodem with 1K size data blocks), you may use it for a faster transfer.

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.

Step 1   Configure transmit and receive speed on the modem to match the speed of your console port. The modem and console port must communicate at the same speed, which can be from 9.6 to 115.2 kbps depending on the speed supported by your modem. Use the confreg ROM monitor command to configure the console port transmission speed for the Cisco 3600 series routers.

Step 2   Connect the modem to the console port of your router. The other end of the modem connects to the standard telephone network. The remote PC dials through the network into the local modem and connects to the router.

Step 3   Issue the xmodem ROM monitor command with any required copy options specified on the router. For example, the -c option specifies CRC16 checksumming, which is supported by the remote PC.

Step 4   At this point, enable the terminal emulation software that runs on the PC to send the file using the Xmodem protocol. The modem speed cannot be changed while establishing a connection to your modem and running the Xmodem protocol.

The new Cisco IOS image loads into Flash memory by default and executes the image upon completion of the file transfer if the -x option is not specified (for example, the xmodem -x new-ios-image command is not configured). Downloads to DRAM memory are specified with the -r option. See the xmodem command's documentation in the Command

The remote PC maintains control of your console port even after the new Cisco IOS image is up and running.

Step 5   From the remote PC, reconfigure the speed of the router's console port to match the speed of the local terminal. This is done by issuing the speed line configuration command at the router prompt, where XXXX represents the terminal's speed:

Once this command is issued, the remote PC loses control of the console port. The remote connection is broken, and you can disconnect the modem from the console port and reconnect the terminal line.

In addition to downloading an image from a remote PC, you can download an image from a local PC by following these steps:

Step 1   Connect the PC serial COM port directly to the console port on your router.

Step 2   Run terminal emulation software on the PC and connect to the router console. You should now see a ROM monitor prompt on the terminal emulator. You may need to configure the terminal emulator to ignore RTS/DTR signals.

Step 3   Determine the transfer speed to run between the console port and the local PC carrying the Cisco IOS software image. The console speed on the router must match the transfer speed configured on your PC's terminal emulation software. You can configure the console port transmission speed with the confreg ROM monitor command.

Step 4   From the terminal emulation software window, enter ROM monitor mode:

Step 5   Run the Xmodem protocol and enter the xmodem -c filename command. The system software asks you to erase all files stored in internal Flash memory.

Enter the following command on the Cisco 1600 series routers. This command has the -s option specified, which configures the console speed for the duration of the Xmodem file transfer.

Step 6   From the local PC's terminal emulation software, run the Xmodem protocol to transfer the image to the router.

On page I-327 of the Configuration Fundamentals Configuration Guide, add the following new section:

Reallocate Packet Memory and Processor Memory

Depending on the number of network interfaces and the size of the Cisco IOS image you are running on a Cisco 3600 series router, you may need adjust the percentage of DRAM allocated to processor memory or packet memory.

The memory-size iomem command performs this function. If more buffers are needed, the packet memory must be increased. To accomodate larger Cisco IOS images, the processor memory must be increased.

To allocate different percentages of DRAM to the packet memory and processor memory, perform the following task in global configuration mode:

Display 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 probably 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 if you still need more 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, this means 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

Take the following steps to allocate 40 percent of the available DRAM to packet memory and the remaining 60 to processor memory. These values can fluctuate according to your configuration needs.

Step 1   Enter the show memory command, to see if you need to reallocate different percentages of packet and processor memory. Refer to the Free(b) column to see how much memory is available.

Step 2   Enter global configuration mode and enter the memory-size iomem 40 command:

Step 3   Write the new configuration to NVRAM.

Step 4   Enter the reload command to run the new image:

Obtaining Service and Support

For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your chassis.

For service and support for a product purchased directly from Cisco, use CCO.

Cisco Connection Online

CCO is Cisco Systems' primary, real-time support channel. SMARTnet 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, 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 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:

• WWW:  http://www.cisco.com.
  
  
• WWW:  http://www-europe.cisco.com.
  
  
• WWW:  http://www-china.cisco.com.
  
  
• Telnet:  cco.cisco.com.
  
  
• Modem:  From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and baud rates up to 14.4 kbps.
  
  

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Please use CCO to obtain general information about Cisco Systems, Cisco products, or upgrades. If CCO is not accessible, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

Posted: Tue Dec 17 18:45:57 PST 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.