|
|
To set the system calendar, use the calendar set privileged EXEC command.
calendar set hh:mm:ss day month year| hh:mm:ss | Current time in hours (24-hour format), minutes, and seconds. |
| day | Current day (by date) in the month. |
| month | Current month (by name). |
| year | Current year (no abbreviation). |
Privileged EXEC.
Once you set the calendar, the system clock is automatically set when the system is restarted or when the clock read-calendar EXEC command is issued. The calendar maintains its accuracy, even after a power failure or system reboot has occurred. The time specified in this command is relative to the configured time zone.
In the following example, the system calendar is manually set to 1:32 p.m. on July 9, 1996.
Switch# calendar set 13:32:00 9 July 1996
clock read-calendar
clock set
clock summer-time
clock timezone
clock update-calendar
To set the default Flash device for the system, use the cd EXEC command.
cd device| device | Valid devices are as follows The colon (:) is required:
· bootflash: This device is the internal Flash memory. · slot0: This device is the first PCMCIA slot on the ASP card. · slot1: This device is the second PCMCIA slot on the ASP card and is the default. |
The slot0 is the initial default device and the default device when you omit the device argument.
EXEC.
For all EXEC commands that have an optional device argument, the system uses the device specified by the cd command when you omit the optional device argument. For example, the dir command contains an optional device argument and displays a list of files on a Flash memory device. When you omit this device argument, the system shows a list of the files on the Flash device specified by the cd command.
The following example sets the default device to the Flash memory card inserted in slot 0 of the ASP card.
Switch# cd slot0:
copy
delete
dir
pwd
show flash
undelete
To enable Cisco Discovery Protocol (CDP) on an interface, use the cdp enable interface configuration command. Use the no form of this command to disable CDP on an interface.
cdp enableThis command has no arguments or keywords.
Disabled.
Interface configuration.
This command only applies to LANE interfaces.
CDP must be enabled on each interface to send or receive CDP information.
In the following example, CDP is enabled on Ethernet interface 2/0/0.
Switch(config)#interface ethernet 2/0/0Switch(config-if)#cdp enable
To specify the amount of time the receiving device should hold a CDP packet from your switch before discarding it, use the cdp holdtime global configuration command. Use the no form of this command to revert to the default setting.
cdp holdtime seconds| seconds | Specifies the hold time to be sent in the CDP update packets. |
180 seconds.
Global configuration.
CDP packets are sent with time-to-live, or hold time, that is nonzero after an interface is enabled and a hold time of 0 immediately before an interface is idled down.
The CDP hold time must be set to a higher number of seconds than the time between CDP transmissions, which is set using the cdp timer command.
In the following example, the CDP packets being sent from your device should be held by the receiving device for 60 seconds before being discarded. You might want to set the hold time lower than the default setting of 180 seconds if information about your device changes often and you want the receiving devices to purge this information more quickly.
Switch# cdp holdtime 60
To enable CDP on your switch, use the cdp run global configuration command. Use the no form of this command to disable CDP.
cdp runThis command has no arguments or keywords.
Enabled.
Global configuration.
CDP is enabled on your switch by default, which means the switch receives CDP information. However, to receive CDP packets, it must be enabled on interfaces using the cdp enable interface configuration command.
In the following example, CDP is disabled for the switch.
Switch# no cdp run
To specify how often your switch sends CDP updates, use the cdp timer global configuration command. Use the no form of this command to revert to the default setting.
cdp timer seconds| seconds | Specifies how often your switch sends CDP updates. |
60 seconds.
Global configuration.
The trade-off with sending more frequent transmissions is obtaining up-to-date information at the expense of using network bandwidth more often.
In the following example, CDP updates are sent from your switch every 80 seconds, which is less frequent than the default setting of 60 seconds. Make this change if you are concerned about preserving bandwidth.
Switch# cdp timer 80
To create a script that places a call over a modem, use the chat-script global configuration command. To disable the specified chat script, use the no form of this command.
chat-script script-name expect-send| script-name | Name of the chat script. |
| expect-send | Content of the chat script. |
No chat scripts are defined.
Global configuration.
Chat scripts are used in dial-on-demand routing to give commands to dial a modem and commands to log on to remote systems. The defined script is used to place a call over a modem.
Some characteristics of chat scripts are as follows:
It is recommended that one chat script (a "modem" chat script) be written for placing a call and another chat script (a "system" or "login" chat script) be written to log onto remote systems, where required.
A suggested chat script naming convention is as follows:
vendor-type-modulationIn other words, the syntax of the chat-script command becomes the following:
Switch(config)# chat-script vendor-type-modulation expect send
For example, if you have a Telebit T3000 modem that uses V.32bis modulation, you name your chat script as follows:
Switch(config)# telebit-t3000-v32bis
For example, the chat-script command could become the following:
Switch(config)# chat-script telebit-t3000-v32bis ABORT ERROR ABORT BUSY ABORT "NO ANSWER" "" "AT H" OK "AT DT \T" DIALING \c TIMEOUT 30 CONNECT \c
For example, you could have script names like the following:
Adhering to this naming convention allows you to use partial chat script names with regular expressions to specify a range of chat scripts that can be used. This is particularly useful for dialer rotary groups and is explained further in the next section.
Chat scripts are in the form expect send, where the send string following the hyphen is executed if the preceding expect string fails. Each send string is followed by a return unless it ends with \c. ^x gets translated into the appropriate control character, and \x gets translated into x if \x is not one of the special sequences listed in Table 3-1.
See the book entitled Managing uucp and Usenet by Tim O'Reilly and Grace Todino for more information about chat scripts.
The escape sequences used in chat scripts are listed in Table 3-1.
| Escape Sequence | Description |
|---|---|
| "" | Expect a null string. |
| EOT | Send an end-of-transmission character. |
| BREAK | Cause a BREAK. This is sometimes simulated using line speed changes and null characters and might not work on all systems. |
| \c | Suppress new line at the end of the send string. |
| \d | Delay for 2 seconds. |
| \K | Insert a BREAK. |
| \n | Send a new line or linefeed character. |
| \p | Pause for 1/4 second. |
| \r | Send a return. |
| \s | Send a space character. |
| \t | Send a table character. |
| \\ | Send a backslash (\) character. |
| \T | Replaced by phone number. |
| \q | Reserved, not yet used. |
Sample supported expect-send pairs are described in Table 3-2.
| Expect and Send Pair | Function |
|---|---|
| ABORT string | Starts scanning for the string in the input; if it is seen, this indicates that the chat script has failed. |
| TIMEOUT time | Sets the time to wait for input, in seconds. The default is 5 seconds. |
As an example of how expect-send pairs function, if the modem reports BUSY when the number is busy, you can indicate that you want the attempt stopped at this point by including ABORT BUSY in your chat script.
ABORT sink instead of ABORT ERROR means that the system stops abruptly when it sees sink instead of when it sees ERROR.
After the connection is established and Return is pressed, a second Return is often required before the prompt appears.
You might include the following as part of your chat script:
ssword:-/r-ssword
This means that after the connection is established you want "ssword" to be displayed. If it is not displayed, send a Return again after the timeout passes.
The following example shows the chat-script command being used to create a chat script named t3000.
Switch(config)# chat-script t3000 ABORT ERROR ABORT BUSY ABORT "NO ANSWER" "" "AT H" OK "AT DT \T" DIALING \c TIMEOUT 30 CONNECT \c
To clear the counters of an access list, use the clear access-list counters privileged EXEC command.
clear access-list counters access-list-number| access-list-number | Access list number from 0 to 1299 for which to clear the counters. |
Privileged EXEC.
Some access lists keep counters that count the number of packets that pass each line of an access list. The show access-lists command displays the counters as a number of matches. Use the clear access-list counters command to restart the counters for a particular access list to 0.
The following example clears the counters for access list 101.
Switch# clear access-list counters 101
To manually clear a temporary access list entry from a dynamic access list, use the clear access-template EXEC command.
clear access-template [access-list-number] [dynamic-name] [source] [destination]| access-list-number | (Optional) Number of the dynamic access list from which the entry is to be deleted. |
| dynamic-name | (Optional) Name of the dynamic access list from which the entry is to be deleted. |
| source | (Optional) Source address in a temporary access list entry to be deleted. |
| destination | (Optional) Destination address in a temporary access list entry to be deleted. |
EXEC.
This command is related to the lock-and-key access feature. Use this command to clear any temporary access list entries that match the parameters you define.
The following example clears any temporary access list entries with a source of 133.20.1.12 from the dynamic access list named vendor.
Switch(config)# clear access-template vendor 133.20.1.12
access-list (extended)
access-template
To delete all dynamic entries from the ARP cache, to clear the fast-switching cache, and to clear the IP route cache, use the clear arp-cache privileged EXEC command.
clear arp-cacheThis command has no arguments or keywords.
Privileged EXEC.
The following example removes all dynamic entries from the ARP cache and clears the fast-switching cache.
Switch# clear arp-cache
To clear PNNI-related data, use the clear atm pnni privileged EXEC command.
clear atm pnni statistics floodingThis command has no keywords or arguments.
Privileged EXEC.
atm pnni node
show atm pnni node
To release a specified SVC, use the clear atm vc privileged EXEC command.
clear atm-vc card/subcard/port vpi vci| card/subcard/port | Card number, subcard number, and port number of the ATM interface. |
| vpi | Virtual path identifier of the signaling SVC to clear. |
| vci | Virtual channel identifier of the signaling SVC to clear. |
Privileged EXEC.
The following is an example of the clear atm-vc command, which releases interface 3/1/0 on VPI 0 and VCI 99.
Switch# clear atm-vc atm 3/1/0 0 99
To reset CDP traffic counters to zero (0) on your switch, use the clear cdp counters privileged EXEC command.
clear cdp countersThis command has no arguments or keywords.
Privileged EXEC.
In the following example, the CDP traffic counters are displayed and then cleared. The show cdp traffic output shows that all of the traffic counters that were reset to zero (0).
Switch#show cdp trafficCDP counters : Packets output: 2571, Input: 0 Hdr syntax: 0, Chksum error: 0, Encaps failed: 0 No memory: 0, Invalid packet: 0, Fragmented: 0 Switch#clear cdp countersSwitch#show cdp trafficCDP counters : Packets output: 0, Input: 0 Hdr syntax: 0, Chksum error: 0, Encaps failed: 0 No memory: 0, Invalid packet: 0, Fragmented: 00
clear cdp table
show cdp traffic
To clear the table that contains CDP information about neighbors, use the clear cdp table privileged EXEC command.
clear cdp tableThis command has no arguments or keywords.
Privileged EXEC.
In the following example, the CDP table is cleared. The output of the show cdp neighbors command shows that all information has been deleted from the table.
Switch#clear cdp tableCDP-AD: Deleted table entry for neon.cisco.com, interface Ethernet 2/0/0 Switch#show cdp neighborsCapability Codes: R - switch, T - Trans Bridge, B - Source Route Bridge S - Switch, H - Host, I - IGMP Device ID Local Intrfce Holdtme Capability Platform Port ID
clock update-calendar
show cdp neighbors
It is recommended that you only use this command for debugging purposes because it clears all counters displayed in the show interface and show controllers commands. To clear the interface counters, use the clear counters privileged EXEC command.
clear counters [atm | ethernet | null]| atm | (Optional) Specifies the ATM interface. |
| ethernet | (Optional) If the type is lex, clears the interface counters on the Ethernet interface. |
| null | (Optional) Specifies the null interface. |
Privileged EXEC.
This command clears all the current interface counters from the interface unless the optional arguments type and number are specified to clear only a specific interface type (ATM, Ethernet, and so on).
The following example illustrates how to clear all interface counters.
Switch# clear counters
To clear the values of dialer statistics for one or more serial or BRI interfaces configured for DDR, use the clear dialer privileged EXEC command.
clear dialerThis command has no keyword or arguments.
Privileged EXEC.
If the interface keyword and the arguments are not used, dialer statistics are cleared on all interfaces.
The following example clears the dialer statistics.
Switch# clear dialer
To delete entries from the host-name-and-address cache, use the clear host privileged EXEC command.
clear host {name | *}| name | Particular host entry to remove. |
| * | Removes all entries. |
Privileged EXEC.
The host name entries are cleared in running memory.
The following example clears all entries from the host name-and-address cache.
Switch# clear host *
To reset the hardware logic on an interface, use the clear interface privileged EXEC command.
clear interface type number| type | Specifies the interface type; it is one of the keywords listed in Table 3-3. |
| number | Specifies the port, connector, or interface card number. See Table 3-3 for each range. |
Privileged EXEC.
Under normal circumstances, you do not need to clear the hardware logic on interfaces.
| Keyword | Interface Type | Interface Numbers |
|---|---|---|
| atm | ATM interface | Specify card/subcard/port |
| async | Async interface | 0-1 |
| ethernet | Ethernet interface | Specify card/subcard/port 2/0/0 |
| null | Null interface | 0-0 |
The following example resets the interface logic on ATM interface 1/0/1.
Switch# clear interface atm 1/0/1
To clear the active or checkpointed database when IP accounting is enabled, use the clear ip accounting privileged EXEC command.
clear ip accounting [checkpoint]| checkpoint | (Optional) Clears the checkpointed database. |
Privileged EXEC.
You can also clear the checkpointed database by issuing the clear ip accounting command twice in succession.
The following example clears the active database when IP accounting is enabled.
Switch# clear ip accounting
ip accounting
ip accounting-list
ip accounting-threshold
ip accounting-transits
show ip interface
To delete the cache table entries, use the clear ip cache privileged EXEC command.
clear ip cache address prefix [address_mask]| address prefix | (Optional) Specifies the IP address. |
| address_mask | Required if address prefix is specified. |
Privileged EXEC.
To delete entries from the neighbor table, use the clear ip eigrp neighbors EXEC command.
clear ip eigrp neighbors [ip-address | type number]| ip-address | (Optional) Address of the neighbor. |
| type number | (Optional) Interface type and number. Specifying these arguments removes from the neighbor table all entries learned via this interface. |
EXEC.
The following example removes the neighbor whose address is 160.20.8.3.
Switch# clear ip eigrp neighbors 160.20.8.3
To redirect an IP cache, use the clear ip redirect privileged EXEC command.
clear ip redirectThis command has no keywords or arguments.
Privileged EXEC.
To remove one or more routes from the IP routing table, use the clear ip route EXEC command.
clear ip route {network [mask] | *}| network | Network or subnet address to remove. |
| mask | (Optional) Network mask associated with the IP address you want to remove. |
| * | Removes all entries. |
EXEC.
The following example removes a route to network 132.5.0.0 from the IP routing table.
Switch# clear ip route 132.5.0.0
To clear the dynamic LE ARP table or a single LE ARP entry of the LANE client configured on the specified subinterface or emulated LAN, use the clear lane le-arp privileged EXEC command.
clear lane le-arp [interface card/subcard/port[.subinterface-number] [mac-address]| interface card/subcard/port | (Optional) CPU interface (ATM2/0/0) for the LANE client whose LE ARP table or entry is to be cleared. |
| .subinterface-number | (Optional) Subinterface for the LANE client whose LE ARP table or entry is to be cleared. |
| mac-address mac-address | (Optional) Media Access Control (MAC) address of the entry to be cleared from the LE ARP table. |
| name elan-name | (Optional) Name of the emulated LAN for the LANE client whose LE ARP table or entry is to be cleared. Maximum length is 32 characters. |
Privileged EXEC.
This command only removes dynamic LE ARP table entries. It does not remove static LE ARP table entries.
If you do not specify an interface or an emulated LAN, this command clears all the LANE ARP tables of any LANE client in the switch.
If you specify a major interface (not a subinterface), this command clears all the LANE ARP tables of every LANE client on all the subinterfaces of that interface.
Use of this command also removes the fast-cache entries built from the LANE ARP entries.
The following example clears all the LANE ARP tables for all clients on the switch.
Switch#clear lane le-arp
The following example clears all the LANE ARP tables for all LANE clients on all the subinterfaces of interface 2/0/0.
Switch# clear lane le-arp interface 2/0/0
The following example clears the entry corresponding to MAC address 0800.AA00.0101 from the LE ARP table for the LANE client on the emulated LAN called red.
Switch#clear lane le-arp name red 0800.aa00.0101
The following example clears all dynamic entries from the LE ARP table for the LANE client on the emulated LAN called red.
Switch# clear lane le-arp name red
To manually read the calendar into the system clock, use the clock read-calendar privileged EXEC command.
clock read-calendarThis command has no arguments or keywords.
Privileged EXEC.
When the calendar is rebooted, the calendar is automatically read into the system clock. However, you can use this command to manually read the calendar setting into the system clock. This command is useful if the cdp enable command has been used to change the setting of the calendar.
In the following example, the system clock is configured to set its date and time by the calendar setting.
Switch#clock read-calendar
cdp enable
clock set
clock update-calendar
ntp update-calendar
To manually set the system clock, use the clock set privileged EXEC command.
clock set hh:mm:ss day month year| hh:mm:ss | Current time in hours (24-hour format), minutes, and seconds. |
| day | Current day (by date) in the month. |
| month | Current month (by name). |
| year | Current year (no abbreviation). |
Privileged EXEC.
Generally, the system is synchronized by a valid outside timing mechanism, such as an NTP clock source. If you have a switch with calendar capability, you do not need to set the system clock. Use this command if no other time sources are available. The time specified in this command is relative to the configured time zone.
In the following example, the system clock is manually set to 1:32 p.m. on July 9, 1996.
Switch#clock set 13:32:00 July 9, 1996
cdp enable
clock read-calendar
clock summer-time
clock timezone
To select a transmit clock source for a physical device of a port, use the clock-source interface configuration command.
clock-source clockmodetype| clockmodetype | Specifies loop-timed | network-derived | free-running as the clock mode type. |
free-running.
Interface configuration.
This subcommand allows selection of the transmit clock source for a port's physical device. The network-derived parameter only applies to SONET interfaces. Currently, OC-12 does not support loop-timed mode.
The following example enables loop-time clocking mode.
Switch(config-if)# clock-source looptimed
To configure the system to automatically switch to summer time (daylight saving time), use one of the formats of the clock summer-time configuration command. Use the no form of this command to configure the switch not to automatically switch to summer time.
clock summer-time zone recurring [week day month hh:mm week day month hh:mm [offset]]| zone | Name of the time zone (PDT, ...) to be displayed when summer time is in effect. |
| week | Week of the month (1 to 5 or last). |
| day | Day of the week (Sunday, Monday, ...). |
| date | Date of the month (1 to 31). |
| month | Month (January, February, ...). |
| year | Year (1996 to 2035). |
| hh:mm | Time (24-hour format) in hours and minutes. |
| offset | (Optional) Number of minutes to add during summer time (default is 60). |
Summer time is disabled. If clock summer-time zone recurring is specified without parameters, the summer time rules default to United States rules. Default of offset is 60.
Global configuration.
Use this command to automatically switch to summer time (for display purposes only). Use the recurring form of the command if the local summer time rules are of this form. Use the date form to specify a start and end date for summer time if you cannot use the first form.
In both forms of the command, the first part of the command specifies when summer time begins, and the second part specifies when it ends. All times are relative to the local time zone. The start time is relative to standard time. The end time is relative to summer time. If the starting month is after the ending month, the system assumes that you are in the Southern Hemisphere.
In the following example, summer time starts on the first Sunday in April at 02:00 and ends on the last Sunday in October at 02:00.
Switch#clock summer-time PDT recurring first Sunday April 2:00 last Sunday October 2:00
To set the time zone for display purposes, use the clock timezone global configuration command. To set the time to Coordinated Universal Time (UTC), use the no form of this command.
clock timezone zone hours [minutes]| zone | Name of the time zone to be displayed when standard time is in effect. |
| hours | Hours offset from UTC. |
| minutes | (Optional) Minutes offset from UTC. |
UTC.
Global configuration.
The system internally keeps time in UTC, so this command is used only for display purposes and when the time is manually set.
In the following example, the time zone is set to Pacific Standard Time and is offset 8 hours behind UTC.
Switch#clock timezone PST -8
cdp enable
clock set
clock summer-time
show clock
To set the calendar from the system clock, use the clock update-calendar privileged EXEC command.
clock update-calendarThis command has no arguments or keywords.
Privileged EXEC.
If the system clock and calendar are not synchronized and the system clock is more accurate, use this command to update the calendar to the correct date and time.
In the following example, the current time is copied from the system clock to the calendar.
Switch# clock update-calendar
clock read-calendar
ntp update-calendar
To change the switch configuration register settings, use the config-register global configuration command.
config-register value| value | Hexadecimal or decimal value that represents the 16-bit configuration register value you want to use the next time the switch is restarted. The value range is from 0x0-0xFFFFFFFF (0 to 65535 in decimal). |
The default is 0x10F, which causes the switch to boot from Flash memory and the Break key to be ignored.
Global configuration.
The lowest four bits of the configuration register (bits 3, 2, 1, and 0) form the boot field. The boot field determines if the switch boots manually, from Flash, or the network. Bit 8 controls the console Break key; when set to 1, it causes the Break key to be ignored. The remaining bits control other features of the switch and are typically set to 0.
To change the boot field value and leave all other bits set to their default values, follow these guidelines:
For more information about the configuration register bit settings and default filenames, see the appropriate switch hardware installation guide.
In the following example, the configuration register is set to boot the system image from Flash memory.
Switch# config-register 0x010F
boot system
show boot
show version
To enter global configuration mode, use the configure privileged EXEC command. You must be in global configuration mode to enter global configuration commands.
configure {memory | network | overwrite-network | terminal}| memory | Executes the commands stored in memory. |
| network | The copy rcp running-config or copy tftp running-config command replaces the configure network command. If you use rcp, see the copy rcp command for more information on copy rcp running-config. If you use TFTP, see the copy tftp command for more information on copy tftp running-config. |
| overwrite-network | Overwrites an NV memory from the TFTP network host. |
| terminal | Executes configuration commands from the terminal. |
No default.
Privileged EXEC
If you do not specify terminal or memory, the switch prompts you for the source of configuration commands. If you specify terminal, the switch executes the commands you enter at the system prompts.
If you specify memory, the switch executes the commands pointed to by the config_file environment variable. The config_file environment variable specifies the device and filename of the configuration file that the switch uses to configure itself during initialization. Possible devices are as follows:
To view the contents of the config_file environment variable, use the show boot command. To modify the config_file environment variable, use the boot config command and then save your changes by issuing the copy running-config startup-config command.
After you enter the configure command, the system prompt changes from switch-name# to switch-name(config)#, indicating that you are in global configuration mode. To leave global configuration mode and return to the privileged EXEC prompt, press ^Z.
In the following example, the switch is configured from the terminal.
Switch# configure terminal
Configuring from terminal, memory, or network [terminal]?
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#
In the following example, a switch runs the commands pointed to by the config_file environment variable.
Switch#configure memory
boot config
copy running-config
show boot
show running-config
show startup-config
To open a specific terminal connection, use the connect EXEC command.
connect ip-address type| ip-address | Is the ip address. |
| type | Defined as the following:
· /debug - Enables telnet debugging mode. · /line - Enables telnet line mode. · /noecho - Disables local echo. · /route: - Enables telnet source route mode. · /source-interface - Specifies source interface. · /stream - Enables stream processing. · 0-65535 - Identifies a specific port number. · bgp - Enables Border Gateway Protocol (179). · chargen - Enables character generator (19). · cmd - Enables remote commands (rcmd, 514). · daytime - Specifies daytime (13). · discard - Specifies discard (9). · domain - Specifies domain Name Service (53). · exec - Enables the exec (rsh, 512). · finger - Enables finger (79). · ftp - Enables File Transfer Protocol (21). · ftp-data - Enables FTP data connections (used infrequently, 20). · gopher - enables gopher (70). · hostname - Defines NIC hostname server (101). · irc - Enables Internet Relay Chat (194). |
| type (continued) | · klogin - Enables Kerberos login (543).
· kshell - Enables Kerberos shell (544). · login - Enables login (rlogin, 513). · lpd - Enables printer service (515). · nntp - Enables Network News Transport Protocol (119). · pop2 - Enables Post Office Protocol v2 (109). · pop3 - Enables Post Office Protocol v3 (110). · smtp - Enables Simple Mail Transport Protocol (25). · sunrpc - Enables Sun Remote Procedure Call (111). · syslog - Enables Syslog (514). · tacacs - Enables TAC Access Control System (49). · talk - Enables talk (517). · telnet - Enables telnet (23). · time - Enables time (37). · uucp - Enables UNIX-to-UNIX Copy Program (540). · whois - Enables nickname (43). · www - Enables World Wide Web (HTTP, 80). |
EXEC.
To return to the EXEC mode from monitor mode, use the cont monitor command.
contThis command has no arguments or keywords.
ROM monitor.
Use this command when the system is in monitor mode and you want to return it to EXEC mode to use the system image instead of reloading. The pound sign (#) indicates monitor mode. Typically, the system is in monitor mode when you manually load a system image or perform diagnostic tests. Otherwise, you are never in this mode.
 | Caution While in monitor mode, the software is suspended until you issue either a reset or the cont command. |
In the following example, the cont command takes you from monitor mode to EXEC mode:
Rommon# cont
To copy any file from a Flash device to another destination, use the following copy EXEC command.
copy device:filename {rcp | running-config | startup-config | tftp}| device: | Specifies a device:filename as the source or destination of the copy operation. The device is optional; but when it is used, the colon (:) is required. Valid devices are as follows:
· bootflash: This device is the internal Flash memory. · slot0: This device is the first PCMCIA slot on the ASP card. · slot1: This device is the second PCMCIA slot on the ASP card and is the default. The filename is the name of the source or destination file. You must always provide a source filename. You can omit the destination filename, in which case the system uses the source filename. Wildcards are not permitted. The maximum filename length is 63 characters. |
| rcp | Specifies a copy operation to a network server using rcp. |
| running-config | Specifies the currently running configuration as the destination of the copy operation. |
| startup-config | Specifies the configuration used for initialization as the destination of the copy operation. The config_file environment variable specifies the startup configuration. |
| tftp | Specifies a TFTP server as the destination of the copy operation. |
If you omit the source or destination device, the switch uses the default device specified by the cd command. If you omit the destination filename, the switch uses the source filename.
EXEC.
The copy commands generally copy a file from a source to a destination. Some invalid combinations exist. Specifically, you cannot copy a running configuration to a running configuration, a startup configuration to a startup configuration, or TFTP to RCP.
When the destination is specified by the config_file or BOOTLDR environment variable, the switch prompts you for confirmation before proceeding with the copy. When the destination is the only valid image in the BOOT environment variable, the switch also prompts you for confirmation before proceeding with the copy.
The config_file environment variable specifies the configuration used during switch initialization. The BOOTLDR environment variable specifies the Flash device and filename containing the reboot image for booting. The BOOT environment variable specifies a list of bootable images on various devices. To view the contents of environment variables, use the show boot command. To modify the config_file environment variable, use the boot config command. To modify the BOOTLDR environment variable, use the boot bootldr command. To modify the BOOT environment variable, use the boot system command. To save your modifications, use the copy running-config startup-config command.
If you do not specify a source or destination device, the switch uses the default device specified by the cd command.
The following example copies the switch-config1 file from the internal Flash memory of a switch to the switch-backupconfg file on the Flash memory card inserted in the first slot of the ASP card.
Switch#copy bootflash:switch-config1 slot0:switch-backupconfig
In the following example, the switch copies the switch-config file from the Flash memory card inserted in slot 0 of the ASP card to the startup configuration.
Switch# copy slot0:switch-config startup-config
boot config
copy running-config
delete
dir
show boot
verify
To copy a file from Flash memory to another destination, use one of the following copy flash EXEC commands.
copy flash {rcp | tftp | device:}| rcp | Specifies a copy operation to a network server using RCP. |
| tftp | Specifies a TFTP server as the destination of the copy operation. |
| device | Specifies a device:filename as the destination of the copy operation. The device argument is optional; but when it is used, the colon (:) is required. Valid devices are as follows:
· bootflash: This device is the internal Flash memory. · slot0: This device is the first PCMCIA slot on the ASP card. · slot1: This device is the second PCMCIA slot on the ASP card and is the default. The filename argument is the name of the destination file. You must always provide a source filename. You can omit the destination filename, in which case the system uses the source filename. Wildcards are not permitted. The maximum filename length is 63 characters. |
If you omit the destination device, the switch uses the default device specified by the cd command. If you omit the destination filename, the switch uses the source filename.
EXEC.
The copy flash command copies from one of the three Flash memory devices. The system prompts you to enter a specific device and filename. You can enter one of the following as the source device:
You must follow the source device with a colon (:) and a filename.
Use the copy flash rcp command to copy a system image from Flash memory to a network server using RCP. You can use the copy of the system image as a backup copy. You can also use it to verify that the copy in Flash memory is the same as the original file.
The RCP software requires that a client send the remote username on each RCP request to the server. When you issue the copy flash rcp command, by default the switch software sends the remote username associated with the current TTY if that name is valid. For example, if the user is connected to the switch through Telnet and was authenticated through the username command, the switch software sends that username as the remote username.
If the TTY username is invalid, the switch software uses the switch host name as both the remote and local usernames.
To specify a different remote username to be sent to the server, use the ip rcmd remote-username command. You can also specify the path of an existing directory along with the remote username.
| 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, 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, the switch 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 does not execute successfully when a default remote username is used. |
If you copy the system image to a personal computer used as a file server, the computer must support the rsh protocol.
Use the copy flash tftp command to copy a system image from Flash memory to a TFTP server. As with the copy flash rcp command, you can use the copy of the system image as a backup or to verify that the copy in Flash is the same as the original file.
The copy commands generally copy a file from a source to a destination. Some invalid combinations exist. Specifically, you cannot copy a running configuration to a running configuration, a startup configuration to a startup configuration, or TFTP to RCP. If you do not specify a source or destination device, the switch uses the default device specified by the cd command.
When the destination is also specified by the config_file environment variable, the switch prompts you for confirmation before proceeding with the copy. The config_file environment variable specifies the configuration used during switch initialization. To view the contents of the config_file environment variable, use the show boot command. To modify the config_file environment variable, use the boot config command. To save your modifications to the config_file environment variable, use the copy running-config startup-config command.
The following example shows how to use the copy flash rcp command.
Switch#configure terminalSwitch#iprcmd remote-usernamenetadmin1Ctrl-ZSwitch#copy flash rcpSystem flash directory, partition 2: File Length Name/status 1 984 junk [1048 bytes used, 8387560 available, 8388608 total] Address or name of remote host [223.255.254.254]? Source file name?junkDestination file name [junk]?junkVerifying checksum for 'junk' (file # 1)... OK Copy 'junk' from Flash to server as 'junk'? [yes/no]y- Upload to server done Flash copy took 0:00:00 [hh:mm:ss]
You see a spinning line during the copy process.
The following example illustrates how to use the copy flash rcp command when copying from a particular partition of Flash memory.
Switch# copy flash rcp
System flash partition information:
Partition Size Used Free Bank-Size State Copy-Mode
1 4096K 2048K 2048K 2048K Read Only RXBOOT-FLH
2 4096K 2048K 2048K 2048K Read/Write Direct
[ Type ?number for partition directory; ? for full directory; q to abort]
Which partition? [default = 1]
The system prompts you if there are two or more partitions. If the partition entered is not valid, the process terminates. You have the option to enter a partition number, a question mark (?) for a directory display of all partitions, or a question mark and a number (?number) for a directory display of a particular partition. The default is the first partition.
System flash directory, partition 2: File Length Name/status 1 3459720 master/igs-bfpx.100-4.3 [3459784 bytes used, 734520 available, 4194304 total] Address or name of remote host [ABC.CISCO.COM]? Source file name?
The file is copied from the partition given by the user earlier.
Destination file name [default = source name]?
Verifying checksum for 'master/igs-bfpx.100-4.3' (file # 1)... OK
Copy 'master/igs-bfpx.100-4.3' from Flash to server
as 'master/igs-bfpx.100-4.3'? [yes/no] yes
The following is sample output from the copy flash tftp command.
Switch#copy flash tftp:
Enter source file name: bootflash:test-image
Enter destination file name [test-image]: tftpboot/backup-image
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Address or name of remote host []? 172.20.46.50
!
The following example illustrates how to use the copy flash tftp command when copying from a particular partition of Flash memory.
Switch# copy flash tftp
System flash partition information:
Partition Size Used Free Bank-Size State Copy-Mode
1 4096K 2048K 2048K 2048K Read Only RXBOOT-FLH
2 4096K 2048K 2048K 2048K Read/Write Direct
[Type ?number for partition directory; ? for full directory; q to abort]
Which partition? [default = 1]
The system prompts you if there are two or more partitions. If the partition entered is not valid, the process terminates. You have the option to enter a partition number, a question mark (?) for a directory display of all partitions, or a question mark and a number (?number) for a directory display of a particular partition. The default is the first partition.
System flash directory, partition 2: File Length Name/status 1 3459720 master/igs-bfpx.100-4.3 [3459784 bytes used, 734520 available, 4194304 total] Address or name of remote host [ABC.CISCO.COM]? Source file name?
The file is copied from the partition given by the user earlier.
Destination file name [default = source name]?
Verifying checksum for 'master/igs-bfpx.100-4.3' (file # 1)... OK
Copy 'master/igs-bfpx.100-4.3' from Flash to server
as 'master/igs-bfpx.100-4.3'? [yes/no] yes
The following example shows how to use the copy flash command.
Switch#copy flash slot0:new-config
boot config
boot system flash
config-register
copy running-config startup-config
ip rcmd remote-username
show boot
To copy a file from a network server to the switch or to another destination using rcp, use one of the following copy rcp EXEC commands.
copy rcp [ device {running-config | startup-config | tftp } ]| device | Specifies a device:filename as the destination of the copy operation. The device is optional, but when used, the colon (:) is required. Valid devices are as follows:
· bootflash: This device is the internal Flash memory. · slot0: This device is the first PCMCIA slot on the ASP card. · slot1: This device is the second PCMCIA slot on the ASP card and is the default. The filename is the name of the destination file. You must always provide a source filename. You can omit the destination filename, in which case the system uses the source filename. Wildcards are not permitted. The maximum filename length is 63 characters. |
| rcp | Specifies a server as the destination of the copy operation. |
| 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. |
| tftp | Specifies a TFTP server as the destination of the copy operation. |
EXEC.
If you omit the destination device, the switch uses the default device specified by the cd command. If you omit the destination filename, the switch uses the source filename.
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 switch software sends the username associated with the current TTY if that name is valid. For example, if the user is connected to the switch through Telnet and the user was authenticated through the username command, the switch software sends that username as the remote username.
If the TTY username is invalid, the switch software uses the switch 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, 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, the switch 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 does not execute successfully when a default remote username is used. |
If you copy a bootstrap image, system image, or configuration file from a personal computer used as a file server, the remote host computer must support rsh protocol.
Use the copy rcp bootflash command to copy a bootstrap image from a network server to Flash memory using RCP. The switch prompts for the name or address of the server and the name of the file to be copied. It provides an option to erase existing Flash memory before writing onto it and allows you to confirm the erasure. The entire copying process takes several minutes and differs from network to network.
Before loading the switch from Flash memory, verify that the checksum of the bootstrap image in Flash memory matches the checksum listed in the README file that was distributed with the system software image.
The checksum of the bootstrap image in Flash memory is displayed at the bottom of the screen when you issue the copy rcp bootflash command. The README file was copied to the server automatically when you installed the system software.
| Caution If the checksum value does not match the value in the README file, do not reboot the switch. Reissue the copy rcp bootflash command and compare the checksums again. If the checksum is repeatedly wrong, copy the original bootstrap image back into Flash memory before you reboot the switch from Flash memory. If you have a corrupted image in Flash memory and try to boot from Flash, the switch starts the system image (assuming booting from a network server is not configured). |
Use the copy rcp running-config command to copy a configuration file from a network server to the switch's running configuration environment using RCP. You can copy either a host configuration file or a network configuration file. Accept the default value of host to copy and load a host configuration file containing commands that apply to one network server in particular. Enter network to copy and load a network configuration file containing commands that apply to all network servers on a network.
Use the copy rcp startup-configuration command to copy a host or network configuration file from a network server to the switch's startup configuration environment using RCP. Accept the default value of host to copy and store a host configuration file containing commands that apply to one network server in particular. Enter network to copy and store a network configuration file containing commands that apply to all network servers on a network.
The command copies a configuration file from the network server to the location specified by the config_file environment variable. The config_file environment variable specifies the configuration used during switch initialization.
The copy commands generally copy a file from a source to a destination. Some invalid combinations exist. Specifically, you cannot copy a running configuration to a running configuration, a startup configuration to a startup configuration, or TFTP to RCP.
The copy rcp command generally copies a file from a network server to another destination using RCP.
When the destination is also specified by the config_file environment variable, the switch prompts you for confirmation before proceeding with the copy. To view the contents of the config_file environment variable, use the show boot command. To modify the config_file environment variable, use the boot config command. To save your modifications, use the copy running-config startup-config command.
The following example shows sample output resulting from copying a system image into a partition of Flash memory. The system prompts only if there are two or more read/write partitions or one read-only and one read/write partition and dual-Flash bank support in boot ROMs. If the partition entered is not valid, the process terminates. You have the option to enter a partition number, a question mark (?) for a directory display of all partitions, or a question mark and a number (?number) for a directory display of a particular partition. The default is the first read/write partition.
Switch# copy rcp flash
System flash partition information:
Partition Size Used Free Bank-Size State Copy-Mode
1 4096K 2048K 2048K 2048K Read Only RXBOOT-FLH
2 4096K 2048K 2048K 2048K Read/Write Direct
[Type ? no for partition directory; ? for full directory; q to abort]
Which partition? [default = 2]
If the partition is read-only and has dual-Flash bank support in boot ROM, the session continues as shown in the following display.
**** NOTICE **** Flash load helper v1.0 This process will accept the copy options and then terminate the current system image to use the ROM based image for the copy. Routing functionality will not be available during that time. If you are logged in via telnet, this connection will terminate. Users with console access can see the results of the copy operation. ---- ******** ---- Proceed? [confirm] System flash directory, partition 1: File Length Name/status 1 3459720 master/igs-bfpx.100-4.3 [3459784 bytes used, 734520 available, 4194304 total] Address or name of remote host [255.255.255.255]?131.108.1.1Source file name?master/igs-bfpx-100.4.3Destination file name [default = source name]?
The file is copied into the partition given by the user earlier.
Loading master/igs-bfpx.100-4.3 from 131.108.1.111: !
Erase flash device before writing? [confirm]
Flash contains files. Are you sure? [confirm]
Copy 'master/igs-bfpx.100-4.3' from TFTP server
as 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yes
If the partition is read-write, the session continues as follows.
System flash directory, partition 2:
File Length Name/status
1 3459720 master/igs-bfpx.100-4.3
[3459784 bytes used, 734520 available, 4194304 total]
Address or name of remote host [255.255.255.255]? 131.108.1.1
Source file name? master/igs-bfpx.100-4.3
Destination file name [default = source name]?
The file is copied into the partition given by the user earlier.
Accessing file 'master/igs-bfpx.100-4.3' on ABC.CISCO.COM...
Loading master/igs-bfpx.100-4.3 from 131.108.1.111: !
Erase flash device before writing? [confirm]
Flash contains files. Are you sure? [confirm]
Copy 'master/igs-bfpx.100-4.3' from TFTP server
as 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yes
The following example uses the copy rcp device command to copy the switch-image file from a network server using RCP to the Flash memory card inserted in slot 0 of the ASP card.
Switch#copy rcp slot0:switch-image
boot config
boot system flash
config-register
copy flash rcp
copy running-config rcp
copy running-config startup-config
copy startup-config rcp
ip rcmd remote-username
show boot
To copy the switch's running configuration file to another destination, use the copy running-config EXEC commands.
copy running-config {rcp | startup-config | tftp | device}| rcp | Specifies a server as the destination of the copy operation. |
| startup-config | Specifies the configuration used for initialization as the destination of the copy operation. |
| tftp | Specifies a TFTP server as the destination of the copy operation. |
| device | Specifies a device:filename as the destination of the copy operation. The device is optional, but when used, the colon (:) is required. Valid devices are as follows:
· bootflash: This device is the internal Flash memory. · slot0: This device is the first PCMCIA slot on the ASP card. · slot1: This device is the second PCMCIA slot on the ASP card and is the default. The filename is the name of the destination file. You must always provide a source filename. You can omit the destination filename, in which case the system uses the source filename. Wildcards are not permitted. The maximum filename length is 63 characters. |
EXEC.
If you omit the destination device, the switch uses the default device specified by the cd command. If you omit the destination filename, the switch uses the source filename.
Save the configuration file to your startup configuration. This setup saves the configuration to the location specified by the config_file environment variable.
The copy running-config-config startup-config command replaces the write memory command. The copy running-config rcp or copy running-config tftp command replaces the write network command.
boot config
boot system flash
config-register
copy flash rcp
copy running-config rcp
To copy the switch's startup configuration file to another destination, use one of the following copy startup-config EXEC commands.
copy startup-config {rcp | running-config | tftp | device:}| 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. |
| tftp | Specifies a TFTP server as the destination of the copy operation. |
| device | Specifies a device:filename as the destination of the copy operation. The device argument is optional, but when it is used, the colon (:) is required. Valid devices are as follows:
· bootflash: This device is the internal Flash memory. · slot0: This device is the first PCMCIA slot on the ASP card. · slot1: This device is the second PCMCIA slot on the ASP card and is the default. The filename argument is the name of the destination file. You must always provide a source filename. You can omit the destination filename, in which case the system uses the source filename. Wildcards are not permitted. The maximum filename length is 63 characters. |
If you omit the destination device, the switch uses the default device specified by the cd command. If you omit the destination filename, the switch uses the source filename.
EXEC.
The copy commands generally copy a file from a source to a destination. Some invalid combinations exist. Specifically, you cannot copy a running configuration to a running configuration, a startup configuration to a startup configuration, or TFTP to RCP.
This command copies the configuration file pointed to by the config_file environment variable to another destination. To view the contents of the config_file environment variable, use the show boot command. To modify the config_file environment variable, use the copy running-config startup-config command.
The rcp protocol requires that a client send the remote username of an rcp request to the server. When you issue the copy startup-config-rcp command, by default, the switch software sends the username associated with the current TTY if that name is valid. For example, if the user is connected to the switch software through Telnet and the user was authenticated through the username command, the switch sends that username as the remote username.
To specify a different remote username to be sent to the server, use the ip rcmd remote-username command. You can also specify the path of an existing directory along with the remote username.
| 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, 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, the switch 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 does not execute successfully when a default remote username is used. |
If you copy the configuration file to a personal computer used as a server, the computer must support the rsh protocol.
The following example uses the copy startup-config command to copy the startup configuration file (specified by the config_file environment variable) to a Flash memory card inserted in slot 0 of the ASP card.
Switch# copy startup-config slot0:switch-config
The following is sample output from the copy startup tftp command.
Switch# copy startup tftp
Remote host []? 172.20.46.50
Name of configuration file to write [Switch-config]? tftpboot/test-config
Write file tftpboot/test-config on host 172.20.46.50? [confirm]
Writing tftpboot/test-config !! [OK]
boot config
copy rcp
copy running-config
ip rcmd remote-username
show boot
To copy a file from a TFTP server to the switch or to another destination, use one of the following copy tftp EXEC commands.
copy tftp {running-config | startup-config | device:}| 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. |
| device | Specifies a device:filename as the destination of the copy operation. The device is optional, but when used, the colon (:) is required. Valid devices are as follows:
· bootflash: This device is the internal Flash memory. · slot0: This device is the first PCMCIA slot on the ASP card. · slot1: This device is the second PCMCIA slot on the ASP card and is the default. The filename is the name of the destination file. You must always provide a source filename. You can omit the destination filename, in which case the system uses the source filename. Wildcards are not permitted. The maximum filename length is 63 characters. |
If you omit the destination device, the switch uses the default device specified by the cd command. If you omit the destination filename, the switch uses the source filename. If you enter a cd command to the device, then that device becomes the default. For example, if you enter cd slot0: and then enter copy tftp bootflash, then "flash" now means slot0.
EXEC.
Refer to the following guidelines.
Table 3-4 describes the characters that you might see during processing of the copy tftp command.
| Character | Description |
|---|---|
| ! | An exclamation point indicates that the copy process is taking place. Each exclamation point indicates that ten packets (512 bytes each) have been successfully transferred. |
| . | A period indicates the copy process timed out. Many periods in a row typically mean that the copy process might fail. |
| O | An uppercase O indicates a packet was received out of order and the copy process might fail. |
| e | A lowercase e indicates a device is being erased. |
| E | An uppercase E indicates an error and the copy process might fail. |
| V | A series of uppercase Vs indicates the progress during the verification of the image checksum. |
When you enter the copy tftp flash command, the Flash memory checksum image displays on the bottom of the screen. Before booting from Flash memory, verify this checksum identifier matches the checksum listed in the README file that was distributed with the system software image. You can find the README file on the TFTP server.
The copy commands generally copy a file from a source to a destination. Some invalid combinations exist. Specifically, you cannot copy a running configuration to a running configuration, a startup configuration to a startup configuration, or TFTP to RCP.
The following example shows how to use the copy tftp bootflash command.
Switch#copy tftp bootflashBoot flash directory: File Length Name/status 1 2622607 c4500-xboot [2622672 bytes used, 1571632 available, 4194304 total] Address or name of remote host [255.255.255.255]? 223.255.254.254 Source file name? c4500-xboot.101 Destination file name [c4500-xboot.101]? Accessing file 'c4500-xboot.101' on 223.255.254.254... Loading c4500-xboot.101 from 223.255.254.254 (via Ethernet0): ! [OK] Erase flash device before writing? [confirm] Flash contains files. Are you sure you want to erase? [confirm] Copy 'c4500-xboot.101' from TFTP server into bootflash as 'c4500-xboot.101' WITH erase? [yes/no]yesErasing device... eeeeeeeeeeeeeeee ...erased Loading c4500-xboot.101 from 223.255.254.254 (via Ethernet0): !!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK - 2622607/4194304 bytes] Verifying checksum... OK (0xE408) Flash copy took 0:00:10 [hh:mm:ss]
boot config
boot system
copy flash
show boot
verify
To assign a custom queue list to an interface, use the custom-queue-list interface configuration command. To remove a specific list or all list assignments, use the no form of this command.
custom-queue-list list| list | Number of the custom queue list you want to assign to the interface; an integer from 1 to 16. |
No custom queue list is assigned.
Interface configuration.
Only one queue list can be assigned per interface. Use this command in place of the priority-list queue-limit command (not in addition to it). Custom queuing allows a fairness not provided with priority queuing. With custom queuing, you can control the interface's available bandwidth when it is unable to accommodate the aggregate traffic enqueued. Associated with each output queue is a configured byte count, which specifies how many bytes of data should be delivered from the current queue by the system before the system moves on to the next queue. When a particular queue is being processed, packets are sent until the number of bytes sent exceeds the queue byte count or until the queue is empty.
In the following example, custom queue list number 3 is assigned to async interface 0.
Switch(config)#interface async 1Switch(config-if)#custom-queue-list 3
queue-list default
queue-list interface
queue-list protocol
queue-list queue byte-count
queue-list queue limit
queue-list stun
|
|