|
|
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 force the Cisco IOS software to wait before initiating a callback to a requesting client, use the callback forced-wait global configuration command.
callback forced-waitThis command has no arguments or keywords.
The forced waiting period is not set.
Global configuration
Use this command when the switch is calling back a modem that initiated a call, then dropped the connection, but requires a delay period before subsequent input is accepted.
The following example sets a waiting period during which a callback chat script is delayed from being sent on an outgoing target line.
Switch# callback-forced-wait
To configure the address mask for identifying valid bits of the called NSAP address field, use the called-address-mask diagnostic configuration command. To return the address mask to the default, use the no form of this command.
called-address-mask {atm-address-mask}
atm-address-mask | Denotes the valid bits in the called NSAP address. |
NULL
Diagnostics configuration
To match this selection criteria, a failed connect setup must have a called party address value equal to the configured called party address for all bits that are 1 in the value of the mask specified through the command. When the default value is retained, the rejected call matches the filter criteria for any called address in the rejected call.
The following example shows configuring a called address mask string.
Switch(cfg-atmsig-diag)# called-address-mask ff.ff.ff
To configure the NSAP format ATM address for the signalling diagnostics filter entry, use the called-nsap-address diagnostics configuration command. To remove any configured address, use the no form of this command.
called-nsap-address nsap-address
nsap-address | A 40-digit hexadecimal NSAP address. |
NULL
Diagnostics configuration
NSAP-format ATM end-system addresses have a fixed length of 40 hexadecimal digits. You should configure the address using the following dotted format:
xx.xxxx.xxxx.xxxx.xxxx.xxxx.xxxx.xxxx.xxxx.xxxx.xx
The following example shows setting a called NSAP address.
Switch(cfg-atmsig-diag)# called-nsap-address 47.111122223333444455556666.777788881111.00
To configure the address mask for identifying valid bits of the calling-nsap-address field in the signalling diagnostics filter entry, use the calling-address-mask diagnostics configuration command. To set to the default value, use the no form of this command.
calling-address-mask {atm-address-mask}
atm-address-mask | Use the address mask to denote the valid bits of the calling address field in the signalling diagnostics filter table entry. |
NULL
Diagnostics configuration
To match this selection criteria, a failed connect setup must have a calling party address value equal to the configured calling party address for all bits that are 1 in the value of the mask specified through the command. When the default value is retained, the rejected call matches the filter criteria for any calling address in the rejected call.
The following example shows a calling address mask.
Switch(cfg-atmsig-diag)# calling-address-mask ff.ff.ff
To configure the NSAP-format ATM address for the signalling diagnostics filter entry, use the calling-nsap-address diagnostics configuration command. To remove any configured address, use the no form of this command.
calling-nsap-address {nsap-address}
nsap-address | The 40-digit, hexadecimal NSAP address. |
NULL
Diagnostics configuration
NSAP-format ATM end-system addresses have a fixed length of 40 hexadecimal digits. You should configure the address using the following dotted format:
xx.xxxx.xxxx.xxxx.xxxx.xxxx.xxxx.xxxx.xxxx.xxxx.xx
The following example shows setting a calling NSAP address.
Switch(cfg-atmsig-diag)# calling-nsap-address 47.111122223333444455556666.777788881111.00
To filter ATM signalling call failures by connection type (point-to-point or point-to-multipoint), use the cast-type signalling diagnostics configuration command. To disable this feature, use the no form of this command.
cast-type {all | p2p | p2mp}
all | Set the cast type to point-to-point and point-to-multipoint. |
p2p | Point-to-point. |
p2mp | Point-to-multipoint. |
All
Diagnostics configuration
The following example shows call failures filtered by point-to-point connection.
Switch(cfg-atmsig-diag)# cast-type p2p
To set the default Flash device for the system, use the cd EXEC command.
cd device:
device | Valid devices are as follows; a colon (:) is required as part of the device specification: · 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
purge
show flash
undelete
To enable CDP on an interface, use the cdp enable interface configuration command. To disable CDP on an interface, use the no form of this command.
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/0
Switch(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. To revert to the default setting, use the no form of this command.
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. To disable CDP, use the no form of this command.
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. To revert to the default setting, use the no form of this command.
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 configure the AAL1 timing recovery clock for T1/E1 interfaces, use the ces aal1 clock interface configuration command.
ces aal1 clock {adaptive | srts | synchronous}
adaptive | Adjusts the output clock on a received AAL1 on first-in-first-out basis. Use in unstructured mode. |
srts | Adjusts the output clock on a received AAL1 on first-in-first-out basis. |
synchronous | Configures the timing recovery to synchronous for structured mode. |
Synchronous
Interface configuration
The clock mode must be synchronous for structured mode. In unstructured mode, use adaptive when a network-derived clock is not available.
Use srts when a network-derived clock is available but devices attached to the CES port use a different clock reference. The srts keyword samples the incoming clock, subtracts from the network clock, and sends the remainder in an AAL1 header. The clock is reconstructed during output by adding the residual to the network reference.
Use synchronous for all other modes.
The following command shows setting the AAL1 timing recovery clock to adaptive mode.
Switch(config-if)# ces aal1 clock adaptive
To configure the type of ces service, use the ces aal1 service interface configuration command.
ces aal1 service {structured | unstructured}
structured | Sets the type of service to structured (cross-connect). |
unstructured | Sets the type of service to unstructured (clear-channel). |
Unstructured
Interface configuration
The structured keyword means that each timeslot is an independent entity grouped into circuits, where each circuit has an independent PVC.
The unstructured keyword reduces the incoming serial data on the receiving end of the ATM network. The keyword also sets the service to single circuit, single PVC, where all timeslots are carried.
The following example shows changing the mode for the ces aal1 service command to structured.
Switch(config-if)# ces aal1 service structured
To configure the CES connection attributes, use the ces circuit interface command. To revert to the default setting, use the no form of this command.
ces circuit (0..31) [cas | cdv | circuit-name | partial-fill | shutdown | timeslots]
0..31 | Selects the circuit identification. For unstructured service, use 0. For T1 structure service, the range is 1 through 24. For E1 structure service, the range is 1 through 31. |
cas | Enables channel-associated signalling for structured service only. The default is no cas. |
cdv | Enables the peak-to-peak cell display variation requirement. The range for CDV is 1 thorough 65535 milliseconds. The default is 2000 milliseconds. |
circuit-name | Sets the ASCII name for the CES-IWF circuit. The string for the circuit name is 0 through 255. The default is CBRx/x/x:0. |
partial-fill | Enables the partial AAL1 cell fill service for structured service only. The range is 0 through 47. The default is 47. |
shutdown | Marks the CES-IWF circuit administratively down. The default is no shutdown. |
timeslots | Configures the timeslots for the CES-IWF circuit for structured service only. The range is 1 through 24 for T1. The range is 1 through 31 for E1. |
See the syntax descriptions.
Interface configuration
Channel-associated signalling provides information about the time slot (on or off the hook) and is updated once per multiframe.
The following example shows setting the structured service CDV range to 5000 milliseconds.
Switch(config-if)# ces circuit 3 cdv 5000
To configure a transmit clock source to the T1/E1 CES port adapter, use the ces dsx1 clock source interface configuration command.
ces dsx1 clock source {loop-timed | network-derived}
loop-timed | Configures the transmit clock to loop (rx-clock to tx-clock). |
network-derived | Configures the transmit clock to be derived from the network. |
network-derived
Interface configuration mode
The following example shows setting the clock source to loop-timed.
Switch(config-if)# ces dsx1 clock source loop-timed
To select the frame type for the data line, use the ces dsx1 framing interface configuration command.
ces dsx1 framing {e1_crc_mfCASlt | e1_crc_mflt | e1_lt | e1_mfCAS_lt}
e1_crc_mfCASlt | Configures the line type to e1_crc_mf: CAS enabled. |
e1_crc_mflt | Configures the line type to e1_crc_mf: CAS not enabled. |
e1_lt | Configures the line type to e1_lt. |
e1_mfCAS_lt | Configures the line type to e1_mf: CAS enabled. |
e1_lt
Interface configuration
Use this command in configurations where the switch communicates with the T1 fractional data line. The service provider determines which framing type is required for your circuit. Refer to the linecode command for information about E1 interfaces.
The following example shows setting the data line type to e1_mfCAS_lt.
Switch(config-if)# ces dsx1 framing e1_mfCAS_lt
To configure T1 port parameters, use the ces dsx1 lbo interface configuration command.
ces dsx1 lbo length
length | Specifies the cable length as one of the following: · 0-110 · 110-200 · 220-330 · 330-440 · 440-550 · 550-660 · 660_above · square_pulse} |
0-110
Interface configuration
Set the cable length to the desired number of feet on your system.
The following example shows setting the cable length to 440 feet using the ces dsx1 lbo interface configuration command.
Switch(config-if)# ces dsx1 lbo 440_550
To select the linecode type for the T1 or E1 line, use the ces dsx1 linecode interface configuration command.
ces dsx1 linecode {ami | b8zs | hdb3}
ami | Specifies the alternate mark inversion (AMI) as the linecode type. Valid for T1 or E1 interfaces. |
b8zs | Specifies B8Zs as the linecode type. Valid for the T1 interface only. |
hdb3 | Specifies the high-density bipolar 3 (HDB3) as the linecode type. Valid for the E1 interface only. |
The default for T1 is ami. The default for E1 is b8zs.
Interface configuration
Use this command in configurations where the switch communicates with the T1 fractional data line. The T1 service provider determines which linecode type, either ami or b8zs, is required for your circuit. The E1 service provider determines which linecode type, either ami or hdb3, is required for your circuit.
The following example specifies B8ZS as the linecode type for the T1 interface.
Switch(config-if)# ces dsx1 linecode b8zs
To configure loopback for the T1 or E1 circuit emulation port adapter module, use the ces dsx1 loopback interface configuration command.
ces dsx1 loopback {line | noloop | payload}
line | Sets the received signal to be looped at the line (does not penetrate line). |
noloop | Sets the interface to no loop. |
payload | Sets the received signal to be looped through the device and returned. |
noloop
Interface configuration
This command is useful when testing the circuit emulation port adapter module.
The following example shows setting the loopback to payload.
Switch(config-if)# ces dsx1 loopback payload
To configure the signalmode to robbedbit, use the ces dsx1 signalmode robbedbit interface configuration command. To revert to the default setting, use the no form of this command.
ces dsx1 signalmode robbedbit
no ces dsx1 signalmode robbedbit
This command has no keywords or arguments.
no
Interface configuration
A T1 frame consists of 24 time slots (DS0) that send at a rate of 64 kbps. T1 defines the ability to send signalling in-band on individual time slots by removing the low bit of each byte for signalling in robbedbit mode. This procedure allows 8 kbps for signalling and leaves 56 kbps for data.
In structured mode, you can send the T1 signalling information across the B-ISDN network. This means that after you set the port in robbedbit signalling mode, and enable CAS on individual circuits that need this type of service, you are robbing bits from the DS0. The system then puts the bits in the specified format to be sent across the B-ISDN network and reinserts them at the passive side on the CES-IWF connection.
To configure the destination port for the circuit, use the ces pvc interface configuration command.
ces pvc (0..31) {interface atm card/subcard/port | dest-atm-addr atm-addr vpi vci}
0..31 | Sets the type of service. For unstructured service, use 0. For T1 structured service, the range is 1 through 24. For E1 structure service, the range is 1 through 31. |
card/subcard/port | Card number, subcard number, and port number of the ATM interface. |
dest-atm-addr | Used to create a soft PVC and is specified at the string 0 through 255. |
vpi | Virtual path identifier of the destination PVC. |
vci | Virtual channel identifier of the destination PVC. |
Interface configuration
Use the interface option to create a hard PVC. Use the dest-atm-addr option to create a soft-PVC.
You must configure both sides of the CES circuits because the source (the active side in CES-IWF) time slots are not recognized at the destination (the passive side).
Each CES circuit has an ATM address. When configuring the source PVC, you need the destination ATM address. See the show ces address command.
The following example shows setting a hard PVC on interface ATM 1/0/0.
Switch(config-if)# ces pvc 31 interface atm 1/0/0
The following example shows setting an unstructured CES soft PVC.
Switch(config-if)# ces pvc 0 dest-atm-addr atm1/0/0 vpi 1 vci 1
The following example show setting a structured hard PVC.
Switch(config-if)# ces pvc 24 interface atm1/0/1 vpi 1 vci 1
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 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 on to 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:
chat-script vendor-type-modulation expect-sendFor example, if you have a Telebit T3000 modem that uses V.32bis modulation, you name your chat script as follows:
Switch(config)# telebit-t3000-v32bisFor 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 4-1.
See the book 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 4-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 two 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 4-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 five 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 "NO":
ssword:-/r-ssword
This means that after the connection is established you want "ssword" to be displayed. If it is not displayed, press Return again after the timeout.
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 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 reset 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 | Number of the dynamic access list from which the entry is to be deleted. |
dynamic-name | Name of the dynamic access list from which the entry is to be deleted. |
source | Source address in a temporary access list entry to be deleted. |
destination | 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, and to clear the fast-switching cache and 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 {debug packets | statistics {call | flooding | traffic}}
debug packets | Clear the PNNI debug memory blocks. |
call | Clear the PNNI call statistics. |
flooding | Clear the PNNI flooding statistics. |
traffic | Clear the PNNI traffic statistics. |
Privileged EXEC
The following example shows how to clear the PNNI flooding statistics.
Switch# clear atm pnni statistics flooding
Switch#
atm pnni node
show atm pnni local-node
To clear existing ATM signalling statistics, use the clear atm signalling statistics EXEC command.
clear atm signalling statistics [interface atm card/subcard/port]
card/subcard/port | Card, subcard, and port number of the ATM interface. |
EXEC
This command clears the statistics for all the interfaces or a specific interface.
show atm signalling statistics
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 signalling SVC to clear. |
vci | Virtual channel identifier of the signalling 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 were reset to zero (0).
Switch# show cdp traffic
CDP 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 counters
Switch# show cdp traffic
CDP 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 configure the release cause code value in the signalling diagnostics filter table entry, use the clear-cause diagnostic configuration command. To disable this feature, use the no format of this command.
clear-cause {clear-cause-code}
clear-cause-code | Decimal number denoting the release cause codes, as specified in the ATM Forum UNI 3.1 specification. |
0
Diagnostics configuration
Only the call failure records that match this configured clear-cause value are collected and stored. The default value zero (0) means the cause code is not considered during filtering.
The following example shows setting a value of 100.
Switch(cfg-atmsig-diag)# clear-cause value of 100
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 table
CDP-AD: Deleted table entry for neon.cisco.com, interface Ethernet 2/0/0 Switch# show cdp neighbors
Capability 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 [type card/subcard/port]
type | Specifies the interface type as atm, atm-p, cbr, ethernet, or null. |
card/subcard/port | Specifies the card, subcard, and port of the interface to clear. |
Privileged EXEC
This command clears all the current interface counters from the interface unless the optional arguments type and card/subcard/port 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 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 card/subcard/port
type | Specifies the interface type as atm, atm-p, cbr, ethernet, or null. |
card/subcard/port | Specifies the card, subcard, and port of the interface to clear. |
Privileged EXEC
Under normal circumstances, you do not need to clear the hardware logic on interfaces.
The following example resets the interface logic on ATM interface 1/0/1.
Switch# clear interface ATM 1/0/1
To delete the cache table entries, use the clear ip cache privileged EXEC command.
clear ip cache [address-prefix address-mask]
address prefix | Specifies the IP address. |
address-mask | Required if address prefix is specified. |
Privileged EXEC
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 | 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 LANE client counter configured on the specified LEC interface, use the clear lane client privileged EXEC command.
clear lane client join-cnt [interface atm card/subcard/port]
card/subcard/port | Specifies the LEC interface to clear. |
Privileged EXEC
If you do not specify an interface, this command clears all the counters of any LANE client in the switch.
When you specify an interface, this command clears all the LANE client counters on that interface.
The following example shows clearing the counters on ATM 1/0/0 interface using the clear lane client privileged EXEC command.
Switch# clear lane client join-cnt interface atm 1/0/0
lane database
show lane client
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 atm card/subcard/port [.subinterface-num] | name elan-name]
card/subcard/port | ATM interface for the LANE client whose LE ARP table or entry is to be cleared. |
.subinterface-num | Subinterface for the LANE client whose LE ARP table or entry is to be cleared. |
elan-name | Name of the emulated LAN for the LANE client whose LE ARP table or entry is to be cleared. Maximum length is 32 characters. |
mac-addr | MAC address of the entry to be cleared from the LE ARP table. |
seg-num | Segment number of the next-hop route descriptor. The segment number ranges from 1 to 4095. |
bridge-num | Bridge number of the next-hop route descriptor. The bridge number ranges from 1 to 15. |
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 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 red.
Switch# clear lane le-arp name red
The following example clears the dynamic entry from the LE ARP table for the LANE client with next-hop router descriptor segment number 1, bridge number 1, on the emulated LAN red.
Switch# clear lane le-arp name red route-desc segment 1 bridge 1
To force a LANE server on a specified subinterface or emulated LAN to drop the Control Direct and Control Distribute VCCs to a given LANE client and force the client to rejoin subject to the new bindings (after they have been changed), use the clear lane server privileged EXEC command.
clear lane server {interface card/subcard/port[.subinterface-num] | name elan-name}
card/subcard/port | Card, subcard, and port number of the ATM interface. |
subinterface-num | Subinterface on which the LANE server is configured. |
elan-name | Name of the emulated LAN on which the LANE server is configured. Maximum length is 32 characters. |
client-atm-addr | ATM address of the LANE client. |
lecid | LANE client ID. The LANE client ID is a value between 1 and 4096. |
mac-addr | MAC address of the LANE client. |
seg-num | Segment number of the next-hop route descriptor. The segment number ranges from 1 to 4095. |
bridge-num | Bridge number of the next-hop route descriptor. The bridge number ranges from 1 to 15. |
Privileged EXEC
After changing the bindings on the configuration server, enter this command on the LANE server. The LANE server will drop the Control Direct and Control Distribute VCCs to the LANE client. The client then asks the LANE configuration server for the location of the LANE server of the emulated LAN it is requesting to join.
If no LANE client is specified, all LANE clients attached to the LANE server are dropped.
The following example forces all the LANE clients on the emulated LAN named red to be dropped. The next time they try to join, they are forced to join a different emulated LAN.
Switch# clear lane server red
To clear the RIF cache, use the clear rif-cache privileged EXEC command.
clear rif-cacheThis command has no keywords or arguments.
Privileged EXEC
Some entries in the RIF cache are dynamically added, and others are static.
To add a LANE client address entry to the configuration servers configuration database, use the client-atm-address name database configuration command. To remove a client address entry from the table, use the no form of this command.
client-atm-address atm-address-template name elan-name
atm-address-template | Template that explicitly specifies an ATM address or a specific part of an ATM address and uses wildcard characters for other parts of the ATM address, enabling you to specify multiple addresses matching the explicitly specified part. Wildcard characters can replace any nibble or group of nibbles in the prefix, the ESI, or the selector fields of the ATM address. |
elan-name | Name of the emulated LAN. Maximum length is 32 characters. |
No address and no emulated LAN name are provided.
Database configuration
The effect of this command is to bind any client whose address matches the specified template into the specified emulated LAN. When a client comes up, it consults the LANE configuration server, which responds with the ATM address of the LANE server for the emulated LAN. The client then initiates join procedures with the LANE server.
Before this command is used, the emulated LAN specified by the elan-name argument must be created in the configuration server's database by using the name server-atm-address command.
If an existing entry in the configuration server's database binds the LANE client ATM address to a different emulated LAN, the new command is rejected.
This command affects only the bindings in the named configuration server database. It has no effect on the LANE components themselves.
The client-atm-address name command is a subcommand of the global lane database command. See the lane database command for information about creating the database, and the name server-atm-address command for information about binding the emulated LAN name to the servers ATM address.
ATM Addresses. A LANE ATM address has the same syntax as a network service access point (NSAP) but it is not a network-level address. It consists of the following:
Address Templates. LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character (nibble), and an ellipsis (...) to match any number of leading, middle, or trailing characters. The values of the characters replaced by wildcards come from the automatically assigned ATM address.
In LANE, a prefix template explicitly matches the prefix but uses wildcards for the ESI and selector fields. An ESI template explicitly matches the ESI field but uses wildcards for the prefix and selector.
With the Cisco implementation of LANE, the prefix corresponds to the switch, the ESI corresponds to the ATM interface, and the selector field corresponds to the specific subinterface of the interface.
The following example shows how to enter database configuration mode using the database lane_db.
Switch(config)# lane database lane_db
Switch(lane-config-database)#
The following example uses an ESI template to specify the part of the ATM address corresponding to the interface. This example allows any client on any subinterface of the interface that corresponds to the displayed ESI value, no matter where the switch is connected, to join the engineering emulated LAN.
Switch(lane-config-database)# client-atm-address ...0800.200C.1001.** name engineering
The following example uses a prefix template to specify the part of the ATM address corresponding to the switch. This example allows any client on a subinterface of any interface connected to the switch that corresponds to the displayed prefix to join the marketing emulated LAN.
Switch(lane-config-database)# client-atm-address 47.000014155551212f.00.00... name marketing
default-name
lane database
name server-atm-address
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 such as a port, use the clock source interface configuration command. To return the clock source to the default, use the no form of this command.
clock source [free-running | loop-timed | network-derived]
free-running | The tx clock is derived from the local oscillator on the PAM. |
loop-timed | The tx clock is derived from the receive (rx) clock. |
network-derived | The tx clock is derived from the port system clock specified at highest priority when using the network-clock-select global configuration command. |
network-derived
Interface configuration
This command applies to all interfaces except older versions of DS3/E3 and the 25-Mbps interfaces.
This subcommand allows selection of the transmit clock source for a port's physical device. Currently, all types of OC-12 PAMs do not support loop-timed mode.
When a tx clock port is set to free-running, if there is a local oscillator present on the PAM, the port uses the PAM's oscillator as the clock source. If there is no local oscillator present on the PAM, the port uses the ASP oscillator.
The following example shows how to enable the loop-timed clocking mode.
Switch(config-if)# clock source looptimed
To configure the system to automatically switch to daylight saving time, use one of the formats of the clock summer-time configuration command. To configure the switch not to automatically switch to daylight saving time, use the no form of this command.
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 | Number of minutes to add during summer time (default is 60). |
Summertime is disabled. If clock summer-time zone recurring is specified without parameters, the summertime rules default to United States rules. Default of offset is 60.
Global configuration
Use this command to automatically switch to summertime (for display purposes only). Use the recurring form of the command if the local summertime rules are of this form. Use the date form to specify a start and end date for summertime if you cannot use the first form.
In both forms of the command, the first part of the command specifies when summertime 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 summertime. If the starting month is after the ending month, the system assumes that you are in the Southern Hemisphere.
In the following example, summertime 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 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 | 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 log on to a host that supports Telnet or Rlogin, use the connect EXEC command.
connect host [port] [keyword] [option]
host | A host name or an IP address. |
port | A decimal TCP port number; the default is the Telnet router port (decimal 3) on the host. |
keyword | One of the keywords listed in Table 4-3. |
option | One or more of the options listed in Table 4-4. |
| Option | Description |
|---|---|
bgp | Border Gateway Protocol |
chargen | Character generator |
cmd rcmd | Remote commands |
daytime | Daytime |
discard | Discard |
domain | Domain Name Service |
echo | Echo |
exec | EXEC |
finger | Finger |
ftp | File Transfer Protocol |
ftp-data | FTP data connections (used infrequently) |
gopher | Gopher |
hostname | NIC hostname server |
ident | Ident Protocol |
irc | Internet Relay Chat |
klogin | Kerberos login |
kshell | Kerberos shell |
login | Login (rlogin) |
lpd | Printer service |
nntp | Network News Transport Protocol |
pim-auto-rp | Protocol-Independent Multicast auto-RP |
pop2 | Post Office Protocol v2 |
pop3 | Post Office Protocol v3 |
port | Destination LAT port name |
smtp | Simple Mail Transport Protocol |
sunrpc | Sun Remote Procedure Call |
syslog | Syslog |
tacacs | Specify TACACS security |
talk | Talk |
telnet | Telnet |
time | Time |
uucp | Unix-to-Unix Copy Program |
whois | Nickname |
www | World Wide Web (HTTP) |
| Option | Description |
|---|---|
/debug | Enables Telnet debugging mode. |
/line | Enables Telnet line mode. In this mode, the Cisco IOS software sends no data to the host until you press Return. You can edit the line using the standard Cisco IOS software command-editing characters. The /line keyword is only on the local switch. |
/noecho | Disables local echo for this connection. |
/route: | Specifies loose source routing. The path argument is a list of host names or IP addresses that specify network nodes and ends with the final destination. |
/source-interface | Specifies a source interface for this connection. |
/stream | Turns on stream processing, which enables a raw TCP stream with no Telnet control sequences. A stream connection does not process Telnet options and can be appropriate for connections to ports running UUCP and other non-Telnet protocols. |
EXEC and privileged EXEC
With the Cisco IOS software implementation of TCP/IP, you are not required to enter the connect, telnet, or rlogin commands to establish a terminal connection. You can just enter the learned host name---as long as the host name is different from a command word in the Cisco IOS software.
To display a list of the available hosts, enter the following command.
Switch# show hosts
To display the status of all TCP connections, enter the following command.
Switch# show tcp
The switch software assigns a logical name to each connection, and several commands use these names to identify connections. The logical name is the same as the host name, unless that name is already in use, or you change the connection name with the EXEC command name-connection. If the name is already in use, the Cisco IOS software assigns a null name to the connection.
The following examples both connect to a host with logical name host1.
Switch> connect host1
Switch> host1
To filter ATM signalling call failures by virtual circuit category, use the connection-category signalling diagnostics configuration command. To return the connection category to the default, use the no form of this command.
connection-category {all | soft-vc | soft-vp | switched-vc | switched-vp}
all | Set the connection category to soft-vc, soft-vp, switched-vc, and switched-vp. |
soft-vc | Soft virtual circuit. |
soft-vp | Soft virtual path. |
switched-vc | Switched virtual circuit. |
switched-vp | Switched virtual path. |
all
Diagnostics configuration
Use the atm signalling diagnostics command to enter diagnostics configuration mode.
In the following example, call failures are filtered by soft virtual circuits.
Switch(cfg-atmsig-diag)# connection-category soft-vc
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 copy privileged EXEC command.
copy {device:filename | source} {device:filename | destination}
device:filename | Specifies a device and 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. |
source/destination | Specifies a copy source or destination using rcp or TFTP, the running configuration, the startup configuration, or flash memory. Refer to to the copy flash, copy rcp, copy running-config, copy startup-config, and copy tftp commands. |
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.
Privileged 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 rxboot 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 flash
copy rcp
copy running-config
copy startup-config
copy tftp
delete
dir
show boot
verify
To copy a file from Flash memory to another destination, use the copy flash privileged EXEC command.
copy flash {rcp | tftp | device:filename}
rcp | Specifies a copy operation to a network server using rcp. |
tftp | Specifies a TFTP server as the destination of the copy operation. |
device:filename | 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.
Privileged 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 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 terminal
Switch# ip rcmd remote-username netadmin1
Ctrl-Z
Switch# copy flash rcp
System 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? junk
Destination file name [junk]? junk
Verifying 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 earlier by the user.
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 earlier by the user.
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 the copy rcp privileged EXEC command.
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. |
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.
Privileged 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 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. 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. 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.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.
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
cd
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 privileged EXEC command.
copy running-config {rcp | startup-config | tftp | device:filename}
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:filename | 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.
Privileged EXEC
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
cd
config-register
copy running-config startup-config
copy startup-config rcp
To copy the switch's startup configuration file to another destination, use the copy startup-config privileged EXEC command.
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. |
rcp | Specifies an rcp server 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.
Privileged 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-confg]? tftpboot/test-config Write file tftpboot/test-config on host 172.20.46.50? [confirm] Writing tftpboot/test-config !! [OK]
boot config
cd
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 the copy tftp privileged EXEC commands.
copy tftp {running-config | startup-config | device:filename}
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:filename | 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.
Privileged EXEC
Refer to the following guidelines.
Table 4-5 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 bootflash
Boot flash directory: File Length Name/status 1 2622607 ls1010-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? ls1010-xboot.101 Destination file name [ls1010-xboot.101]? Accessing file 'ls1010-xboot.101' on 223.255.254.254... Loading ls1010-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 'ls1010-xboot.101' from TFTP server into bootflash as 'ls1010-xboot.101' WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeee ...erased Loading ls1010-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
cd
copy flash
show flash
verify
|
|