|
|
To configure the address mask for identifying valid bits of the called NSAP address field, use the called-address-mask ATM signalling diagnostics 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
ATM signalling 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 ATM signalling 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
ATM signalling 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 ATM signalling 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
ATM signalling 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 ATM signalling 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
ATM signalling 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 ATM 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
ATM signalling diagnostics configuration
The following example shows call failures filtered by point-to-point connection.
Switch(cfg-atmsig-diag)# cast-type p2p
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 E1 or T1 data line, use the ces dsx1 framing interface configuration command.
(For E1) ces dsx1 framing {e1_crc_mfCASlt | e1_crc_mflt | e1_lt | e1_mfCAS_lt}To restore the default setting, use the no form of these commands.
e1_crc_mfCASlt | Configures the frame type to e1_crc_mf: CAS enabled. |
e1_crc_mflt | Configures the frame type to e1_crc_mf: CAS not enabled. |
e1_lt | Configures the frame type to e1_lt. |
e1_mfCAS_lt | Configures the frame type to e1_mf: CAS enabled. |
sf | Configures the frame type to super frame. |
esf | Configures the frame type to extended super frame. |
The default for E1 is el_lt. The default for T1 is esf.
Interface configuration
Use this command in configurations where the switch communicates with either the T1 or the E1 data line to configure the frame type for your circuit.
The following example shows setting the E1 data line frame 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.
(For E1) ces dsx1 linecode {ami | hdb3}
ami | Specifies the alternate mark inversion (AMI) as the linecode type. Valid for the 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 b8zs. The default for E1 is hdb3.
Interface configuration
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-address atm-address {vpi vpi-number | vci vci-number}}[retry-interval [first retry-interval] [maximum retry-interval]]
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-address | Used to create a soft PVC and is specified at the string 0 through 255. |
vpi vpi | Virtual path identifier of the destination PVC. |
vci vci | Virtual channel identifier of the destination PVC. |
retry-interval | To configure retry interval timers for a Soft-VC. |
first retry-interval | Retry interval for the first retry after the first failed attempt specified in milliseconds. If the first retry after the first failed attempt also fails, the subsequent attempts will be made at intervals computed using the first retry-interval as follows: (2 ** (k-1)) * first retry-interval Where the value of k will be 1 for the first retry after the first failed attempt and will be incremented by 1 for every subsequent attempt. [Range: 100 to 3,600,000 milliseconds] The default is 5,000 milliseconds. |
maximum | The maximum retry interval between any two attempts specified in seconds. Once the retry interval is computed in the first retry-interval and becomes equal to or greater than the maximum retry-interval configured, the subsequent retries will be done at regular intervals of maximum retry-interval seconds until the call is established. [Range: 1 to 65,535 seconds] The default is 60. |
Interface configuration
Use the interface option to create a hard PVC. Use the dest-address 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 atm 1/0/0 vpi 1 vci 1
The following example shows setting a structured hard PVC.
Switch(config-if)# ces pvc 24 interface atm 1/0/1 vpi 1 vci 1
To form a serial interface, or channel-group, by aggregating timeslots on a E1 line, use the channel-group controller configuration command. To delete a serial interface, use the no form of this command.
channel-group cgn {timeslots range | unframed}
cgn | Channel-group number. The range is 1 to 31. |
timeslots range | Specifies the timeslots assigned to the channel. The range is 1 to 31. A dash represents a range of timeslots; a comma separates timeslots. |
unframed | Configures an E1 interface as clear channel (unframed). |
Not applicable to E1
Controller configuration
If the serial interface has encapsulation set to Frame Relay, then the channel-group command works only if you shut down the interface and tear down all soft VCs. Otherwise, an error is returned.
The no form of this command is not allowed on an interface unless you shut down the interface and release all SVC legs of the soft VC.
The following example creates a logical serial port on interface 1/0/0:2.
Switch(config)# controller e1 1/0/0
Switch(config-control)# channel-group 2 timeslots 6-31
show controllers
show interface serial
more system:running-config
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 configure the release cause code value in the signalling diagnostics filter table entry, use the clear-cause ATM signalling diagnostics 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
ATM signalling 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
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 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 atm 0.
Switch# clear lane le-arp interface atm 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 drops the Control Direct and Control Distribute VCCs to a given LANE client and force the client to rejoin, subject to the new bindings, 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 drops 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. When they try to join again, they are forced to join a different emulated LAN.
Switch# clear lane server red
lane database
show lane server
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.
rif
rif timeout
show rif
To add a LANE client address entry to the configuration servers configuration database, use the client-atm-address name lane configuration server database 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.
Lane configuration server database
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
delay
lane database
name server-atm-address
To select a transmit clock source for a physical device such as a port, use the clock source controller 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 | reference}
free-running | The transmit clock is derived from the local oscillator on the port adapter. |
loop-timed | The transmit clock is derived from the receive (rx) clock. |
network-derived | The transmit clock is derived from the port system clock specified as highest priority when you use the network-clock-select global configuration command. |
reference | The oscillator on the processor is used as the transmit clock source. |
loop-timed
Controller configuration
This subcommand allows selection of the transmit clock source for the physical device of a port. Currently, all types of OC-12 port adapters do not support loop-timed mode.
When a transmit clock port is set to free-running, if there is a local oscillator present on the port adapter, the port uses the port adapter's oscillator as the clock source. If there is no local oscillator present on the port adapter, the port uses the processor oscillator.
The following example shows how to enable the reference clocking mode on an E1 interface.
Switch# config t
Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# controller e1 1/0/0
Switch(config-controller)# clock source reference
network-clock-select
show controllers
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 transmit clock is derived from the local oscillator on the port adapter. |
loop-timed | The transmit clock is derived from the receive (rx) clock. |
network-derived | The transmit clock is derived from the port system clock specified at highest priority when you use the network-clock-select global configuration command. |
loop-timed
Interface configuration
This command applies to all interfaces except older versions of the DS3/E3 and the 25-Mbps interfaces.
This subcommand allows selection of the transmit clock source for the physical device of a port. Currently, all types of OC-12 port adapters do not support loop-timed mode.
When a transmit clock port is set to free-running, if there is a local oscillator present on the port adapter, the port uses the port adapter's oscillator as the clock source. If there is no local oscillator present on the port adapter, the port uses the processor oscillator.
The following example shows how to enable the loop-timed clocking mode.
Switch(config-if)# clock source loop-timed
framing (interface configuration)
network-clock-select
To initialize the collection mode and specify at what time accounting data is recorded in the accounting file, use the collection-modes ATM accounting file subcommand. To disable the collection mode, use the no form of this command.
collection-modes [periodic] [on-release]
periodic | Data is recorded at recurring time intervals. |
on-release | Data is recorded on the release of a connection. |
ATM accounting file
atm accounting file
failed-attempts
min-age
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.
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 ATM 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
ATM signalling 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 set types of connections for atm accounting selection, use the connection-types ATM accounting selection command. To return the connection-type to the default, use the no form of this command.
connection-types [pvc | pvp | spvc-originator | spvc-target | spvp-originator | spvp-target |
pvc | Set the permanent virtual circuit. |
pvp | Set the permanent virtual path. |
spvc-originator | Set the originating SPVC. |
spvc-target | Set the target SPVC. |
spvp-originator | Set the originating SPVP. |
spvp-target | Set the target SPVP. |
svc-in | Set the incoming switched virtual circuit. |
svc-out | Set the outgoing switched virtual circuit. |
svp-in | Set the incoming switched virtual path. |
svp_out | Set the outgoing switched virtual path. |
The default value for the connection type is svc-in, svc-out, and svp-out.
ATM accounting selection
Changes to connection-types take effect immediately.
The following example shows specifying the connection types for ATM accounting selection index 1 as spvc-originator and spvp-originator.
Switch(config)# atm accounting selection 1
Switch(config-acct-sel)# connection-types spvc-originator spvp-originator
Switch(config-acct-sel)#
atm accounting selection
atm accounting collection
atm accounting file
list
To select a port on a Frame Relay port adapter, use the controller global configuration command.
controller e1 card/subcard/port
e1 | Port adapter. |
card/subcard/port | Specifies the card, subcard, and port of the E1 interface. The card number is displayed using the show interface command. The subcard number can be either |
Global configuration
Specify the controller to configure by entering the controller subcommand, followed by e1, and card/subcard/port.
The following example begins configuration of the E1 Frame Relay interface on card 11, subcard 0, and port 0 using the controller global configuration command.
Switch# config t
Switch(config)# controller e1 11/0/0
Switch(config-controlle)#
show controller e1show interface
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 processor card. · slot1: This device is the second PCMCIA slot on the processor 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 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 processor 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 processor 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
dialer-list list
Usage Guidelines
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 processor card. · slot1: This device is the second PCMCIA slot on the processor 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 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 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 processor card. · slot1: This device is the second PCMCIA slot on the processor 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 processor 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 processor card. · slot1: This device is the second PCMCIA slot on the processor 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 processor card. · slot1: This device is the second PCMCIA slot on the processor 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 processor 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 processor card. · slot1: This device is the second PCMCIA slot on the processor 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-1 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
|
|