|
|
Cisco IOS Release 11.2(5)P provides software support for the Cisco 1600 series of modular access routers. This feature chapter explains how to display information about system images and configuration files; how to copy these images and files to and from Flash memory, network servers, and remote PCs; how to configure the boot device; and how to reallocate main memory and shared memory. It also contains an update to the Cisco IOS command reference publications.
The modular design of Cisco 1600 series routers allows you to configure or reconfigure the router with the types of interfaces that your network needs.
This document makes use of the following terms:
Image or system image--The Cisco IOS image.
Flash memory PC card or PCMCIA card--A Flash memory card that is inserted in to a Personal Computer Memory Card International Association (PCMCIA) slot. This card is used to store system images and configuration files.
Cisco 1600 series routers contain the following memory systems:
The following platforms are supported:
This section explains optional Cisco 1600 series configuration tasks as described in the following list:
The only Flash memory device in Cisco 1600 series routers is the Flash memory PC card, identified by the keyword flash. This keyword is always followed by a colon.
Some commands also include a partition number or a filename, in the form device:[partition-number:][filename]. If a filename follows the partition number, you must also enter a colon after the partition number.
For example, flash: means internal Flash memory; flash:1 means the first partition in internal Flash memory; and flash:1:c1601-i-mz.112-5P means a particular file in the first partition in internal Flash memory.
To display information about system software, system image files, and configuration files, enter the following commands in EXEC mode:
Refer to the Cisco IOS Release 11.2 configuration guides and command references for examples of these commands.
The Flash memory content listing does not include the checksum of individual files. To recompute and verify the image checksum after the image is copied into Flash memory, enter the following command in EXEC mode:
| Task | Command |
|---|---|
| Recompute and verify the image checksum after the image is copied into a Flash memory device. | verify flash:[partition-number:][filename] |
For an example of how to verify the checksum of a file, see the "Configuration Examples" section later in this chapter.
To partition Flash memory, enter the following command in global configuration mode:
| Task | Command |
|---|---|
| Partition Flash memory | partition flash: [number-of-partitions][partition-size] |
The number of partitions that you can create in a Flash memory device equals the number of banks in the device. Enter the show flash:all command to view the number of banks on the Flash memory card. The number of partition size entries you set must be equal to the number of specified partitions. For example, the partition flash: 2 4 4 command configures two partitions to be 4 MB in size each. The first 4 corresponds to the first partition; the second 4 corresponds to the second partition.
This task succeeds only if the router has at least two banks of Flash memory and the partitioning does not split an existing file in Flash memory across two or more partitions.
You can download a file, such as a configuration file or a Cisco IOS image, from a Trivial File Transfer Protocol (TFTP), remote copy protocol (rcp), or Maintenance Operation Protocol (MOP) network server to a local Flash memory device. To download the file, enter one of the following commands in EXEC mode:
| Task | Command |
|---|---|
| Download a file from a TFTP server into a Flash partition. | copy tftp flash:[partition-number:][filename] |
| Download a file from an rcp server into a Flash partition. | copy rcp flash:[partition-number:][filename] |
| Download a file from a MOP server into a Flash partition. | copy mop flash:[partition-number:][filename] |
One of the following prompts displayed after the command indicates how the file can be downloaded:
If the file can be downloaded into more than one partition, you are prompted for the partition number. To obtain help, enter any of the following at the partition number prompt:
During a copy operation, a pound sign (#) means that a Flash memory device is being cleared and initialized. An exclamation point (!) means that ten packets have been transferred successfully. A series of "V" characters means that a checksum verification of the file is occurring after the file is written to Flash memory. An "O" means an out-of-order packet. A period (.) means a timeout.
To interrupt a copy operation, press Ctrl-^ or Ctrl-Shift-6. The operation terminates, but any partial file copied remains until Flash memory is erased.
For the minimum version of Cisco IOS software that runs on your Cisco 1600 series router, see your router installation guide and configuration notes.
Be sure there is enough space available before copying a file to Flash memory. Use the show flash command, and compare the size of the file you want to copy to the amount of Flash memory available. If the space available is less than the amount needed, the copy command is partially executed, but the entire file is not copied into Flash memory. The failure message "buffer overflow - xxxx/xxxx" appears, where xxxx/xxxx is the number of bytes read from the source file and the number of bytes available on the destination device.
The router gives you the option of erasing the existing contents of Flash memory before writing to it. If there is no free Flash memory available, or if no files have ever been written to Flash memory, the erase routine is required before new files can be copied. The software informs you of these conditions and prompts you for a response.
Filenames in Flash memory can be up to 63 characters long; they are not case sensitive and are always converted to lowercase. A prompt alerts you when a file with the same name as the one you want to copy (regardless of case) already exists in Flash memory. If you proceed with the copy, the old file is "deleted." The old file still resides in Flash memory, but it is rendered unusable in favor of the newer version, and the show flash command lists it with a "deleted" tag. If you terminate the copy process before it is finished, the newer file is marked "deleted" because the file was not copied completely and is not valid. In this case, the original file in Flash memory remains valid.
For an example of how to copy a file from a remote TFTP, rcp, or MOP server to the router, refer to the "Configuration Examples" section later in this chapter.
To clear the contents of your startup configuration, enter the following command in EXEC mode:
| Task | Command |
|---|---|
| Clear the contents of your startup configuration. This command erases the contents of NVRAM. | erase startup-config |
To erase a saved configuration from Flash memory, enter one of the following commands in EXEC mode:
| Task | Command |
|---|---|
| Erase a specified configuration file, all files, or all files in a partition. | erase flash:[partition-number] |
When you erase (or, equivalently, delete) a file, the system software marks the file as deleted, allowing you to recover it later with the undelete command as long as the file has not been overwritten.
For an example of how to erase a file from Flash memory, see the "Configuration Examples" section later in this chapter.
To copy a configuration file from a TFTP server, rcp server, or Flash memory directly to your startup configuration in NVRAM or your running configuration, enter one of the following commands in EXEC mode:
| Task | Command |
|---|---|
| Load a configuration file directly into NVRAM. | Choose one of the following commands. Your choice is dependent on where the source file is located: |
For an example of how to copy a file directly to the startup or running configuration, see the "Configuration Examples" section later in this chapter.
To configure the router to function as a TFTP server, enter the following command in global configuration mode:
| Task | Command |
|---|---|
| Configure the router and specify a Flash memory device and filename. | tftp-server flash [flash:][partition-number:]filename |
The partition number and filename correspond to the Exit configuration mode and save the configuration information to your startup configuration.
This section explains how to configure your Cisco 1600 series router to boot from Flash memory or from a network server.
If your router is configured to boot automatically, but it does not find a valid system image, or if its configuration file is corrupted at startup, it enters ROM monitor mode. You can use the ROM monitor to load a system image manually from one of the following devices:
You can also configure the router to enter ROM monitor mode directly by setting the boot bits to 0 in the configuration register.
To boot manually from Flash memory, complete the following tasks:
For examples of how to boot from Flash memory, see the "Configuration Examples" section later in this chapter.
To boot manually from a network file, complete the following tasks in EXEC mode:
For an example of how to boot from a network file, see the "Configuration Examples" section later in this chapter.
To configure a router to boot automatically from an image in Flash memory, perform the following tasks:
| Task | Command |
|---|---|
| Step 1 Enter global configuration mode. | configure terminal |
| Step 2 Enter the filename of an image on a Flash memory PC card. | boot system flash [flash:][partition-number:] filename |
| Step 3 Set the configuration register to enable loading of the system image from Flash memory. | config-register value |
| Step 4 Exit configuration mode. | ^Z |
| Step 5 Save the configuration file to your startup configuration in NVRAM. | copy running-config startup-config1 |
| Step 6 Optionally, verify the contents of the startup configuration. | show startup-config |
| Step 7 Power-cycle and reboot the router to ensure that it boots properly. | reload |
If you enter more than one image filename, the router tries them in the order entered.
To remove a filename from the configuration file, enter the no boot system flash filename command.
When you have configured the router to boot from Flash memory, you might want to revert to booting from ROM in case you do not yet need this functionality, you choose to boot from a network server, or you do not yet have the proper image in Flash memory. To revert to booting from ROM, enter the no boot system flash global configuration command.
If you do not have access to a network server and need to download a system image (to update it, or if all the system images in Flash memory somehow are damaged or erased), you can copy an image from a local or remote computer (such as a PC, UNIX workstation, or Macintosh) using the Xmodem or Ymodem protocols. This function is primarily used as a disaster recovery mechanism.
Xmodem and Ymodem are common protocols used for transferring files and are included in applications such as Windows 3.1 (TERMINAL.EXE), Windows 95 (HyperTerminal), Windows NT 3.5x (TERMINAL.EXE), Windows NT 4.0 (HyperTerminal), and Linux UNIX freeware (minicom).
Xmodem and Ymodem downloads are slow, and you should use them only when you do not have access to a network server. You can speed up the transfer by setting the console port speed to 115200 bps.
On Cisco 1600 series routers, Xmodem and Ymodem file transfers are performed from the ROM monitor over the console port, using the following command:
xmodem [-y] [-c] [-e] [-f] [-r] [-x] [-sdata-rate][filename]
Here the -y option uses the Ymodem protocol; -c provides CRC-16 checksumming; -e erases the first partition in Flash memory; -f erases all of Flash memory; -r downloads the file to DRAM (the default is Flash memory); -x prevents the image from executing after download; and -s sets the console port data rate.
The computer from which you transfer the Cisco IOS image must be running terminal emulation software and the Xmodem or Ymodem protocol.
For an example of how to recover a system image, see the next section, "Configuration Examples."
This section documents the following list of software configuration examples:
The following example verifies the checksum of the file c1600-i-mz.test in the fourth partition of the Flash memory card:
Router#verify flash:System 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]4System flash directory, partition 4: File Length Name/status 1 2205860 dirt/images/c1600-d-mz 2 1711128 c1600-i-mz.test 3 850 alz [3918032 bytes used, 276272 available, 4194304 total] Name of file to verify?c1600-i-mz.testVerifying checksum for 'c1600-i-mz.test' (file # 2)... OK
You can copy a configuration file or Cisco IOS image from a TFTP server either with or without specifying its destination partition and filename in the command line. This section describes both methods.
To copy a file from a TFTP server to a Flash memory location specified in the command line, follow these steps:
Step 1 If you are copying a system software image, make a backup copy of the current image. See the section "Copy a File from a Flash Memory Device to a Server Example" later in this chapter for instructions.
Step 2 Enter the copy tftp flash: command, and include the destination partition and destination filename options in the command line:
copy tftp flash:1:c1600-i-mz
In this example, the router reports one partition and one file in Flash memory:
Step 3 Enter or confirm the IP address of the remote TFTP server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 4 Enter or confirm the source filename on the remote server:
If you entered a destination filename in the command line, this filename is interpreted as the source filename by default. In this case, press Enter. If you want to specify a source filename, enter the complete UNIX path name, such as newios/1600/c1600-i-mz, after the question mark (?).
Step 5 Decide whether you want to erase existing files in Flash memory during the copy operation. Press Enter to confirm erasing the files:
Step 6 You are asked again to confirm erasing the files in Flash memory:
Enter yes when the system software asks you one more time to confirm the copy operation before the file is copied:
yes
The system software loads the file from the remote server, copies it into the router's Flash memory, and verifies the copy:
The duration of the copy operation is displayed in hours, minutes, and seconds:
To copy a file from a TFTP server to a Flash memory location that is not specified in the command line, follow these steps:
Step 1 If you are copying a system software image, make a backup copy of the current image. See the section "Copy a File from a Flash Memory Device to a Server Example" later in this chapter for instructions.
Step 2 Enter the copy tftp flash: command without specifying the destination partition and destination filename:
copy tftp flash:
The contents of Flash memory are displayed. In this case, two partitions are present:
Step 3 Specify the destination partition to copy the remote file into. The first partition is the default. Press Enter to accept the default setting:
The file c1600-i-mz already exists in this partition:
Step 4 Enter or confirm the IP address of the remote TFTP server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 5 Enter the complete UNIX path name of the source file. In this example, the path name /images/1600/c1600-i-mz is entered to copy the file c1600-i-mz:
/images/1600/c1600-i-mz
Step 6 By default, the entire source path name is entered as the destination filename. To shorten or change this filename, enter the new name after the question mark (?) and press Enter:
images/1600/c1600-i-mz]?
The remote file is accessed and loaded using interface Ethernet 0:
Step 7 Decide whether you want to erase the existing files in Flash memory during the copy operation. Press Enter to confirm erasing the files:
Step 8 You are asked again to confirm erasing the files in Flash memory:
Step 9 Enter yes when the system software asks you one more time to confirm the copy operation before Flash memory is erased and the file is copied:
yes
You can copy a file from a remote rcp server either with or without specifying its destination partition (and, optionally, its filename) in the command line. This section describes both methods.
For the rcp command to execute properly, an account must be defined on the network server for the remote username configured on the router. The path for all files and images to be copied begins at the remote user's home directory.
By default, the router software sends the remote username associated with the current TTY process, if that name is valid. For example, if the user is connected to the router through Telnet and was authenticated through the username command, the router software sends the Telnet username as the remote username. If the remote username is invalid, the software uses the router host name as both the remote and local usernames.
You can override the default remote username by using the ip rcmd remote-username command. 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.
To copy a file from a remote rcp server to a specified Flash partition, follow these steps:
Step 1 If you are copying a system software image, make a backup copy of the current image. See the section "Copy a File from a Flash Memory Device to a Server Example" later in this chapter for instructions.
Step 2 Enter the copy rcp command, specifying the destination device (flash:) and partition
(3 in this example):
copy rcp flash:3
Step 3 Enter or confirm the IP address of the remote rcp server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 4 Enter the complete UNIX path name of the source file. In this example, the path name /tftpboot/gate/c1600-i-mz is entered to copy the file c1600-i-mz:
/tftpboot/gate/c1600-i-mz
Step 5 By default, the entire source path name is entered as the destination filename. To shorten or change this filename, enter the new name after the question mark (?) and press Enter:
Step 6 Decide whether you want to erase the existing files in Flash memory during the copy operation. Press Enter to confirm erasing the files:
Step 7 You are asked again to confirm erasing the files in Flash memory:
Step 8 Enter yes when the system software asks you one more time to confirm the copy operation before Flash memory is erased and the file is copied:
yes
To copy a file from a remote rcp server to a Flash memory PC card without specifying a destination partition and filename, follow these steps:
Step 1 If you are copying a system software image, make a backup copy of the current image. See the section "Copy a File from a Flash Memory Device to a Server Example" later in this chapter for instructions.
Step 2 Enter the copy rcp flash: command:
copy rcp flash:
Because a destination partition and destination filename were not specified in the command line, you will be prompted for these values during the copy operation. The router reports that there are four partitions in the PC card and lists their read and write permissions:
Step 3 Specify the destination partition to copy the remote file into. The first partition is the default. Press Enter to accept the default setting:
The file c1600-j-mz already exists in partition 1:
Step 4 Enter or confirm the IP address of the remote rcp server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 5 Enter the complete UNIX path name of the source file. In this example, the path name /tftpboot/gate/c1600-i-mz is entered to copy the file c1600-i-mz:
/tftpboot/gate/c1600-i-mz
Step 6 By default, the entire source path name is entered as the destination filename. To shorten or change this filename, enter the new name after the question mark (?) and press Enter:
Step 7 Decide whether you want to erase the existing files in Flash memory during the copy operation. Press Enter to confirm erasing the files:
Step 8 You are asked again to confirm erasing the files in Flash memory:
Step 9 Enter yes when the system software asks you one more time to confirm the copy operation before Flash memory is erased and the file is copied:
yes
In the following example, the system image routerimage, which already exists in Flash memory, is copied from a MOP server. There is enough space in Flash memory to copy the new file without erasing any existing files.
Step 1 If you are copying a system software image, make a backup copy of the current image. See the section "Copy a File from a Flash Memory Device to a Server Example" later in this chapter for instructions.
Step 2 Enter the copy mop flash: command:
copy mop flash:
The contents of Flash memory are displayed. In this case, two partitions are present:
Step 3 Specify the partition device you want to copy the remote file into. The first partition is the default. Press Enter to accept the default setting:
The router reports that one partition and two files exist in Flash memory:
Step 4 Enter the name of the source file:
routerimage
Step 5 By default, the source filename is entered as the destination filename. To shorten or change this filename, enter the new name after the question mark (?) and press Enter:
Step 6 Decide whether you want to erase the existing files in Flash memory during the copy operation. Press Enter to confirm erasing the files:
Step 7 You are asked again to confirm erasing the files in Flash memory:
Step 8 Enter yes when the system software asks you one more time to confirm the copy operation before Flash memory is erased and the file is copied:
yes
The following example erases all files in the second partition in Flash memory:
Router#erase flash:2System flash directory, partition 2: File Length Name/status 1 1711088 dirt/gate/c1600-i-mz [1711152 bytes used, 15066064 available, 16777216 total] Erase flash device, partition 2? [confirm] Are you sure? [yes/no]:yesErasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
The following example copies the file ios-upgrade-1 from partition 4 of the Flash memory PC Card to the router's startup configuration:
Router#copy flash:4:ios-upgrade-1 startup-configCopy 'ios-upgrade-1' from flash device as 'startup-config' ? [yes/no]yes[OK]
You can copy a file or system image from Flash memory to a TFTP or rcp network server for distribution or backup. This section shows examples of both.
In some implementations of TFTP, you must 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.
You can copy a configuration file or Cisco IOS image to a TFTP server either with or without specifying the source partition and filename in the command line. This section gives examples of several alternatives.
In this example, the source partition number is specified in the command line.
Step 1 Enter the copy flash:2 tftp command, identifying the source partition as partition 2 of the Flash memory PC card:
copy flash:2 tftp
Step 2 Enter or confirm the IP address of the remote TFTP server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 3 Enter the source filename:
your-ios
Step 4 Enter the destination UNIX path name on the TFTP server:
/sysadmin/images/server-ios
yes
In this example, the source partition number and filename are specified in the command line.
Step 1 Enter the copy flash: tftp command, including the source partition and filename:
copy flash:4:your-ios tftp
The system software does not display Flash memory contents because all required information is specified in the command line.
Step 2 Enter or confirm the IP address of the remote TFTP server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 3 Enter the destination UNIX path name on the TFTP server:
dirt/images/c1600-j-mz
yes
To copy a system image from a Flash card to a remote TFTP server, follow these steps:
Step 1 Enter the copy flash: tftp command:
copy flash: tftp
The system software displays the contents of the Flash memory PC card.
Step 2 Specify the partition that contains the source file. Partition 1 is the default setting:
1
The file "your-ios" is shown in partition 1:
Step 3 Enter or confirm the IP address of the remote TFTP server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 4 Enter the source filename:
your-ios
Step 5 Enter the destination UNIX path name on the TFTP server:
dirt/sysadmin/your-ios
Step 6 Confirm that the copy settings are correct:
yes
You can also copy a system image from Flash memory to an rcp network server. If you copy the system image to a personal computer used as a file server, the computer must support the rcp protocol.
For the rcp command to execute properly, an account must be defined on the network server for the remote username configured on the router. The path for all files and images to be copied begins at the remote user's home directory.
By default, the router software sends the remote username associated with the current TTY process, if that name is valid. For example, if the user is connected to the router through Telnet and was authenticated through the username command, the router software sends the Telnet username as the remote username. If the remote username is invalid, the software uses the router host name as both the remote and local usernames.
You can override the default remote username by using the ip rcmd remote-username command. 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.
You can copy a Cisco IOS image to an rcp server either with or without specifying the source partition and filename in the command line. This section describes both methods.
To copy a file from the Flash memory PC card to an rcp server without specifying the source partition and filename in the command line, follow these steps:
Step 1 Enter the copy flash: rcp command:
copy flash: rcp
Step 2 Enter the IP address of the remote host. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 3 Enter the source file that you want to copy from the Flash memory PC card:
your-ios
Step 4 Confirm or rename the UNIX destination path name and filename:
/sysadmin/images/your-ios
Step 5 Confirm that the copy settings are correct:
yes
In this example, the source partition number and filename are specified in the command line.
Step 1 Enter the copy flash: rcp command, specifying the partition number and filename:
copy flash:1:your-ios
Step 2 Enter the IP address of the rcp server. The IP address of the last remote device the router accessed is displayed in brackets as the default. Press Enter to accept the bracketed value:
Step 3 Enter the destination path name and filename:
/sysadmin/images/your-ios
Step 4 Confirm that the copy settings are correct:
yes
The following command instructs the ROM monitor to boot the first file in the first partition of Flash memory:
> boot flash:
This command instructs the ROM monitor to boot the first file in the second partition of the Flash memory card:
> boot flash:2:
In this example, the ROM monitor boots the file named imagename from the third partition of the Flash memory card:
> boot flash:3:imagename
The following command fails to specify a valid device type, so the ROM monitor invokes the boot helper to boot a system image.
> boot flash
In the following example, the router is booted manually from the network file network1:
> boot network1
The following example shows a file transfer using the Xmodem protocol. To use the Ymodem protocol, include the -y option with the xmodem command.
If you include the -r option (download to DRAM), your router must have enough DRAM to hold the file being transferred. To run from Flash memory, an image must be positioned as the first file in Flash memory. If you are copying a new image to boot from Flash memory, erase all existing files first.
 | Caution A modem connection from the telephone network to your console port introduces security issues that you should consider before enabling the connection. For example, remote users can dial into your modem and access the router's configuration settings. |
Step 1 Place a Cisco IOS software image on the remote computer's hard drive. You can download an image from Cisco Connection Online (CCO) or from the Documentation CD-ROM.
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.
Step 2 To transfer from a remote computer, connect a modem to the console port of your Cisco 1600 series router and to the standard telephone network. The modem and console port must communicate at the same speed, which can be from 1200 to 115200 bps, depending on the speed supported by your modem. Use the confreg ROM monitor command or the -s option to configure the console port transmission speed for the router.
Connect a modem to the remote computer and to the telephone network. The remote computer dials through the telephone network and connects to the router.
To transfer from a local computer, connect the router's console port to a serial port on the computer, using a null-modem cable. The console port speed configured on the router must match the transfer speed configured on the local computer.
Step 3 You should see a ROM monitor prompt in the terminal emulation window:
Enter the xmodem ROM monitor command, along with any desired copy options and, optionally, the filename of the Cisco IOS image. The image loads into Flash memory by default; to download to DRAM instead, use the -r option. The image is normally executed on completion of the file transfer; to prevent execution, use the -x option. The -c option specifies CRC-16 checksumming, which is more sophisticated and thorough than standard checksumming, if it is supported by the computer:
xmodem -s 115200 -c new-ios-image
yes
Step 4 Start an Xmodem send operation with the remote computer's terminal emulation software. This is the computer that is sending the system image to the router. See your emulation software application's manual for instructions on how to execute a Xmodem or Ymodem file transfer.
Step 5 The Cisco IOS image is transferred to the router and executed. If you are transferring from a remote computer, the computer maintains control of your console port even after the new Cisco IOS image is running. To release control to a local terminal, reconfigure the speed of the router's console port to match the speed of the local terminal by entering the speed bps configuration command from the remote computer at the router prompt:
configure terminal
line 0
speed 9600
The remote connection is broken, and you can disconnect the modem from the console port and reconnect the terminal line.
This section describes ROM monitor and Cisco IOS commands that are new or modified, or have special syntax or usage for Cisco 1600 series routers. All other commands used with these routers are documented in the Cisco IOS Release 11.2 command references.
This section includes the following commands:
To boot the router manually, use the boot ROM monitor command:
boot [flash:][partition-number:][filename]If you enter the boot command and press Enter, the router boots from ROM.
Enter this command when your router cannot find boot configuration information in NVRAM. To reach the ROM monitor prompt (>), use one of the following methods:
In this example, the router is booted manually from ROM:
> boot
In the following example, a router boots the file routertest from a network server with IP address 172.19.15.112:
> boot routertest 172.19.15.112
The following example shows the ROM monitor booting the first file in the first Flash memory partition:
> boot flash:
continue
To specify the system image that the router loads at startup, use one of the following boot system global configuration commands. Use the no form of this command to remove the startup image specification.
boot system flash [flash:][partition-number:] filename| flash | Boots the router from Flash memory. If you omit all optional arguments, the router searches Flash memory for the first bootable image. |
| partition-number | (Optional) Boots the router from the specified Flash partition. If you do not specify a filename, the first valid file in the partition is loaded. |
| filename | (Optional with boot system flash) Name of the image file to load at startup (case-sensitive for network files). |
If you configure the router to boot from a network server, but do not specify a system image file, the router uses the configuration register settings to determine a default filename. The default boot filename starts with the word cisco, followed by the octal equivalent of the boot field number in the configuration register, followed by a hyphen (-) and the router model. See your router installation and configuration guide for further information on the configuration register and default filename. See also the confreg and config-register commands in the Cisco IOS command references.
If you omit all optional arguments, the router searches Flash memory for the first bootable image. If you enter a partition but not a filename, the first valid file in the partition is loaded.
Global configuration
The boot system command modifies the BOOT environment variable in the running configuration. This variable specifies a list of bootable images on various devices. You must save the environment variable to your startup configuration, using the copy running-config startup-config command, to place the information under ROM monitor control the next time you reboot. To view the contents of the BOOT environment variable, use the show boot command.
If an entry in the BOOT environment variable list specifies an invalid device, the router skips that entry.
Each time you write a new software image to Flash memory, you must delete the existing filename in the configuration file and then add a new line. To remove a single entry from the bootable image list, use the no form of the command to add it. To eliminate all entries in the bootable image list, use the no boot system command. Entering this command sets the BOOT environment variable to a null string. You can then redefine the list of bootable images using boot system commands. Remember to save your changes to the startup configuration with the copy running-config startup-config command.
To rearrange the order of the entries in the BOOT environment variable, enter the no boot system command and then reenter the list.
This example boots from the image file igs-bpx-l in partition 2 of Flash memory:
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)#boot system flash flash:2:igs-bpx-l
config-register
copy
ip rcmd remote-username
show boot
To copy any file from a Flash device to another destination, use the following copy EXEC command.
copy flash:[partition-number:][filename] {tftp | rcp | running-config | startup-config}| flash | Copy from Flash memory. |
| partition-number | (Optional) Partition number of the source or destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the source or destination file. |
| tftp | Copy to a TFTP server. |
| rcp | Copy to a rcp server. |
| running-config | Copy to the currently running configuration. |
| startup-config | Copy to the startup configuration in NVRAM. |
If you omit the destination filename, the software uses the source filename.
EXEC
On Cisco 1600 series routers, the local Flash memory device is a Flash memory PC card inserted in a PCMCIA slot.
The following example copies a file in Flash memory to a TFTP server:
copy flash: tftp
To copy a file from a MOP server to the router, use one of the following the copy mop EXEC commands:
copy mop flash:[partition-number:][filename]| flash | Copy to Flash memory. |
| partition-number | (Optional) Partition number of the source or destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the source or destination file. |
EXEC
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.
The following example copies a file from a MOP server to the local Flash memory on a Cisco 1600 series router.
copy mop flash:
verify
To copy a file from a network server to the router or to another destination using rcp, use the copy rcp command:
copy rcp flash:[partition-number:][filename] | running-config | startup-config}| flash | Copy to Flash memory. |
| partition-number | (Optional) Partition number of the source or destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the source or destination file. |
| 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. |
If you omit the destination filename, the router uses the source filename.
EXEC
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 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.
| Caution The remote username must be associated with an account on the destination server. If you do not use the ip rcmd remote-username command to specify the name of a remote user associated with an account on the server, then the remote username associated with the current TTY process must be associated with an account on the server. If there is no username for the current TTY process, then the host name must be associated with an account on the server. If the network administrator of the destination server did not establish accounts for the remote username used, this command will not execute successfully when a default remote username is used. |
The following example copies a file from a rcp server to local Flash memory.
copy rcp flash:
To copy the running configuration file to Flash memory, use the copy running-config command:
copy running-config flash:[partition-number:][filename]| flash | Copy to Flash memory. |
| partition-number | (Optional) Partition number of the source or destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the source or destination file. |
If you omit the destination filename, the router uses the source filename.
EXEC
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.
The following example copies the running configuration from the router to local Flash memory:
copy running-config flash:
verify
To copy startup configuration file to Flash memory, use the copy startup-config EXEC command:
copy startup-config flash:[partition-number:][filename]| flash | Copy to Flash memory. |
| partition-number | (Optional) Partition number of the source or destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the source or destination file. |
If you omit the destination filename, the router uses the source filename.
EXEC
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.
The following example copies the startup configuration to Flash memory:
copy startup-config flash:
verify
To copy a file from a TFTP server to the router or to another destination, use the copy tftp command:
copy tftp {flash:[partition-number:][filename] | running-config | startup-config}| flash | Copy to Flash memory. |
| partition-number | (Optional) Partition number of the source or destination Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of the source or destination file. |
| 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. |
If you omit the destination filename, the router uses the source filename.
EXEC
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.
Before booting from Flash memory, verify that the checksum of the image in Flash memory matches the checksum listed in the README file that was distributed with the system software image. The checksum of the image in Flash memory is displayed at the bottom of the screen when you issue the copy tftp command. The README file was copied to the TFTP server automatically when you installed the system software image.
The following example copies a file from a TFTP server to local Flash memory:
copy tftp flash:
To erase a stored configuration, use the erase EXEC command:
erase flash:[partition-number]| flash | Erase the contents of Flash memory. |
| partition-number | (Optional) The partition number to erase. |
EXEC
You cannot erase a single filename. You can erase only the entire Flash memory card or a specified partition.
The following example erases all of partition 2 in Flash memory:
Router#erase flash:2System flash directory, partition 2: File Length Name/status 1 1711088 dirt/images/c1600-i-mz [1711152 bytes used, 15066064 available, 16777216 total] Erase flash device, partition 2? [confirm] Are you sure? [yes/no]:yesErasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
boot config
delete
show boot
show startup-config
undelete
To separate Flash memory into partitions, use the partition global configuration command. Use the no form of this command to undo partitioning and to restore Flash memory to one partition.
partition flash:[number-of-partitions][partition-size]| flash | Specify Flash memory. |
| number-of-partitions | (Optional) Number of partitions in Flash memory. |
| partition-size | (Optional) Size of each partition. The number of partition size entries must be equal to the number of specified partitions. |
Flash memory consists of one partition.
If the partition size is not specified, partitions of equal size are created.
Global configuration
To undo partitioning, use the partition flash:1 or no partition flash: command. If there are files in a partition other than the first, you must erase the partition using the erase flash: command before reverting to a single partition.
When creating two partitions, you must not truncate a file or cause a file to spill over into the second partition.
The following example divides the Flash memory card into two partitions, each 4 MB in size:
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)#partition flash: 2 4 4
The following example creates four partitions of equal size in the card:
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)#partitionflash: 4
To display the contents of Flash memory, use the show flash command:
show flash: [all | chips | detailed | err | partition number | summary]| all | (Optional) Shows names and sizes of all system image files stored in Flash memory, including those that are invalid. |
| chips | (Optional) Shows the bank each chip is in, and its code, size, and name. |
| detailed | (Optional) Shows detailed file directory information, 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 the specified partition. You can use this keyword only when Flash memory has multiple partitions. |
| summary | (Optional) Shows summary information, including partition size, bank size, state, and method by which files can be copied into each partition. You can use this keyword only when Flash memory has multiple partitions. |
EXEC
The show flash: command displays the type of Flash memory, the files in Flash memory, and the amount of Flash memory used and remaining.
The following example shows the state of the Flash memory PC card on a Cisco 1600 series router:
Router# show flash: all
System flash directory:
File Length Name/status
addr fcksum ccksum
1 3441784 c1640-j-mz.111-7.AA
0x40 0xE9DA 0xE9DA
[3442848 bytes used, 4946760 available, 8388608 total]
8192K bytes of processor board System flash (Read/Write)
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
1 2 89A2 1024KB INTEL 28F008SA
2 2 89A2 1024KB INTEL 28F008SA
3 2 89A2 1024KB INTEL 28F008SA
4 2 89A2 1024KB INTEL 28F008SA
The following example illustrates the show flash: chips command on a router that has Flash memory partitioned:
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
The following example illustrates the show flash: detailed command on a router whose Flash memory is partitioned:
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)
This example shows detailed information about a Flash card that has four partitions:
Router# show flash: detailed
System flash directory, partition 1:
File Length Name/status
addr fcksum ccksum
1 3142748 dirt/images/mars-test/c1600-j-mz.latest
0x40 0xB732 0xB732
[3142812 bytes used, 1051492 available, 4194304 total]
4096K bytes of System flash (Read/Write)
System flash directory, partition 2:
File Length Name/status
addr fcksum ccksum
1 3141700 /tftpboot/images/c1600-j-mz
0x40 0x84E 0x84E
2 850 startup-config
0x2FF0C4 0x16 0x16
[3142680 bytes used, 1051624 available, 4194304 total]
4096K bytes of System flash (Read/Write)
System flash directory, partition 3:
File Length Name/status
addr fcksum ccksum
1 1711088 /tftpboot/images/c1600-i-mz
0x40 0xF89A 0xF89A
[1711152 bytes used, 2483152 available, 4194304 total]
4096K bytes of System flash (Read/Write)
System flash directory, partition 4:
File Length Name/status
addr fcksum ccksum
1 2205860 dirt/images/c1600-d-mz
0x40 0x9501 0x9501
2 1711128 dirt/images/c1600-i-mz.test
0x21A924 0xDFE9 0xDFE9
3 850 alz
0x3BC57C 0x16 0x16
[3918032 bytes used, 276272 available, 4194304 total]
4096K bytes of System flash (Read/Write)
The following example illustrates the show flash: err command on a router that has Flash memory partitioned:
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
The following example shows detailed information about the second partition in Flash memory:
Router# show flash: partition 2
System flash directory, partition 2:
File Length Name/status
1 1711088 dirt/images/c1600-i-mz
[1711152 bytes used, 15066064 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)
The following example illustrates the show flash: summary command on a router that has Flash memory partitioned. The partition in the Read Only state is the partition from which the Cisco IOS image is being executed:
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
To display information about the ISDN Basic Rate Interface (BRI) belonging to a Cisco 1600 series router, use the show controllers bri privileged EXEC command.
show controllers bri number| number | Interface number. The value is 0 or 1. |
Privileged EXEC
The following is sample output from the show controllers bri command on a Cisco 1600 series router:
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
Table 3 describes the significant fields in the display.
| 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. |
To display the performance report for a 56 kbps 4-wire CSU/DSU in a Cisco 1602 router, use the show service-module privileged EXEC command.
show service-module serial number| number | Interface number 0 or 1. |
Privileged EXEC
The following example is sample output from the show service-module serial command on a Cisco 1600 series router:
Router# show service-module serial 1
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,
Table 4 describes the possible fields that can be created by the show service-module serial command for Cisco 1600 series routers. Not all the fields described in this table are shown in the example, because output fields are displayed as necessary by the network conditions.
| Field | Description |
|---|---|
| Module type | The type of 4-wire serial module installed in the router. Only the data rates 56- and 64-kbps are supported. |
| Connection state | The current state of the serial interface. |
Receiver has no alarms | Alarms detected by the interface. 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). |
| 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. |
clear service-module
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.
snmp-server enable traps [trap-type] [trap-option]No traps are enabled.
If you enter this command with no keywords, the default is to enable all trap types.
Global configuration
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.
The following example enables the router to send Frame Relay and environmental monitor traps.
snmp-server enable trap frame-relay snmp-server enable trap envmon temperature
snmp-server host
snmp trap illegal-address
To configure a router or a Flash memory device on the router as a TFTP server, enter the tftp-server global configuration command. This command replaces the tftp-server system command. To remove a previously defined filename, use the no tftp-server flash version of this command.
tftp-server flash [flash:][partition-number:]filename| flash | Assigns TFTP service to a file in Flash memory. |
| partition-number | (Optional) Partition number of the Flash memory device. You must enter a colon (:) after the partition number if a filename follows it. If a partition is not specified, the first partition is used. |
| filename | File the TFTP server uses in answering TFTP Read Requests. |
Disabled
Global configuration
You can specify multiple filenames by repeating the tftp-server command. The router sends a copy of the image in Flash memory to any client that sends a TFTP Read Request with this filename.
The following example enables a Cisco 1600 series router to operate as a TFTP server. The source file c1600-i-mz is in the second partition of Flash memory:
router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. router(config)#tftp-server flash flash:2:dirt/gate/c1600-i-mz
access-list
To verify the checksum of a file in Flash memory, use the verify EXEC command. This command replaces the copy verify and copy verify flash commands.
verify flash:[partition-number:][filename]| flash | Specify Flash memory. |
| partition-number | (Optional) Partition number to verify. You must enter a colon (:) after the partition number if a filename follows it. |
| filename | (Optional) Name of a file in specified Flash memory. |
The default device is the current working device.
EXEC
Use the verify command to verify the checksum of a file before using it. When you omit the flash: argument, the router verifies the checksum of the specified file on the Flash memory PC card.
The following example verifies the file gsxx on the Flash memory card:
verify flash:gsxx
The following example verifies the checksum of the file alz, located in the fourth partition of the Flash memory card:
Router#verify flash:4System flash directory, partition 4: File Length Name/status 1 2205860 dirt/images/c1600-d-mz 2 1711128 dirt/images/c1600-i-mz.test 3 850 alz [3918032 bytes used, 276272 available, 4194304 total] Name of file to verify?alzVerifying checksum for 'alz' (file # 3)... OK
cd
copy rcp
ip rcmd remote-username
pwd
show flash
To copy a Cisco IOS image to a Cisco 1600 series router using the ROM monitor and the Xmodem or Ymodem protocol, use the xmodem ROM monitor command:
xmodem [-y] [-c] [-e] [-f] [-r] [-x] [-s data-rate][filename]| -y | (Optional) Uses Ymodem protocol for higher throughput. |
| -c | (Optional) CRC-16 checksumming, which is more sophisticated and thorough than standard checksumming. |
| -e | (Optional) Erases the first partition in Flash memory before starting the download. |
| -f | (Optional) Erases all of Flash memory before starting the download. |
| -r | (Optional) Downloads the file to DRAM. The default is to Flash memory. |
| -x | (Optional) Do not launch Cisco IOS image on completion of the download. |
| -s data-rate | (Optional) Sets the console port's data rate during file transfer. Values are 1200, 2400, 4800, 9600, 19200, 38400, and 115200 bps. The default rate is specified in the configuration register. |
| filename | (Optional) Filename to copy. This argument is ignored when -r is specified, because only one file can be copied to DRAM. On the Cisco 1600 series, files are loaded to the ROM for execution. |
ROM monitor
Xmodem protocol with 8-bit CRC, file downloaded into Flash memory and executed on completion.
This command first appeared in Cisco IOS Release 11.2 P.
Use the xmodem ROM monitor command to download a new system image to your router from a local personal computer (such as a PC, Mac, or UNIX workstation), or a remote computer over a modem connection, to the router's console port. The computer must have a terminal emulation application that supports these protocols.
If you include the -r option, your router must have enough DRAM to hold the file being transferred.
To run from Flash, an image must be positioned as the first file in Flash memory. If you are copying a new image to boot from Flash, erase all existing files first.
| Caution A modem connection from the telephone network to your console port introduces security issues that you should consider before enabling the connection. For example, remote users can dial into your modem and access the router's configuration settings. |
The following example uses the xmodem -c filename ROM monitor command to copy the file new-ios-image from a remote or local computer:
rommon >xmodem -c new-ios-imageDo not start the sending program yet... File size Checksum File name 1738244 bytes (0x1a8604) 0xdd25 george-admin/c1600-i-mz WARNING: All existing data in bootflash will be lost! Invoke this application only for disaster recovery. Do you wish to continue? y/n [n]:yesReady to receive file new-ios-image...
For additional software configuration information for the Cisco 1600 series routers, refer to the following documents:
|
|