|
|
This chapter describes how to administer and manage the Catalyst 6000 family switches.
This chapter consists of these sections:
The supervisor engine software includes a Telnet client application that you can use to access other devices in the network from the switch. The switch supports up to eight simultaneous Telnet sessions.
To Telnet to another device on the network from the switch, perform this task:
| Command | Purpose |
|---|---|
Router# telnet host [interface] | Open a Telnet session with a remote host. |
This example shows how to Telnet from the switch to a remote host:
Router# telnet 171.10.15.9 Trying 171.10.15.9 ... Open User Access Verification Username: barney Password: Cisco-fr> enable Password: Cisco-fr# Cisco-fr# logout
These sections describe how to use IP ping on the switch:
The switch supports IP ping, which you can use to test connectivity to remote hosts. If you attempt to ping a host in a different IP subnetwork, you must define a static route to the network or have IP routing configured to route between those subnets.
To stop a ping in progress, press Ctrl-C.
Ping returns one of the following responses:
To ping another device on the network from the switch, perform this task:
| Command | Purpose |
|---|---|
Router# ping [apollo | appletalk | clns | decnet | ip | ipx | srb | tag | vines | xns] host | Ping a remote host. |
This example shows how to ping an IP host:
Router# ping 172.20.52.3 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.20.52.3, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms Router#
This example shows how to ping a specific protocol and host:
Router# ping ip 171.69.115.9 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 171.69.115.9, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1024/1224/1340 ms Router#
These sections describe how to use IP traceroute on a Catalyst 6000 family switch:
You can use IP traceroute to identify the path that packets take through the network on a hop-by-hop basis. The command output displays all network layer (Layer 3) devices, such as routers, that the traffic passes through on the way to the destination.
Catalyst 6000 family switches can participate as the source or destination of the traceroute command but do not appear as a hop in the traceroute command output.
The traceroute command uses the Time To Live (TTL) field in the IP header to cause routers and servers to generate specific return messages. Traceroute starts by sending a User Datagram Protocol (UDP) datagram to the destination host with the TTL field set to 1. If a router finds a TTL value of 1 or 0, it drops the datagram and sends back an Internet Control Message Protocol (ICMP) time-exceeded message to the sender. Traceroute determines the address of the first hop by examining the source address field of the ICMP time-exceeded message.
To identify the next hop, traceroute sends a UDP packet with a TTL value of 2. The first router decrements the TTL field by 1 and sends the datagram to the next router. The second router sees a TTL value of 1, discards the datagram, and returns the time-exceeded message to the source. This process continues until the TTL is incremented to a value large enough for the datagram to reach the destination host (or until the maximum TTL is reached).
To determine when a datagram reaches its destination, traceroute sets the UDP destination interface in the datagram to a very large value which the destination host is unlikely to be using. When a host receives a datagram with an unrecognized interface number, it sends an ICMP port unreachable error to the source. This message indicates to the traceroute facility that it has reached the destination.
To trace the path packets take through the network, perform this task:
| Command | Purpose |
|---|---|
Router# traceroute [appletalk | clns | ip | ipx | oldvines | vines] host | Execute traceroute to trace the path packets take through the network. |
This example shows how to perform a traceroute to an IP host:
Router# traceroute 171.9.15.10 Type escape sequence to abort. Tracing the route to 171.69.115.10 1 172.2.52.1 0 msec 0 msec 4 msec 2 172.2.1.203 12 msec 8 msec 0 msec 3 171.9.16.6 4 msec 0 msec 0 msec 4 171.9.4.5 0 msec 4 msec 0 msec 5 171.9.121.34 0 msec 4 msec 4 msec 6 171.9.15.9 120 msec 132 msec 128 msec 7 171.9.15.10 132 msec 128 msec 128 msec Router#
You can display the configuration or status of any interface on any module in a Catalyst 6000 family switch using the show interfaces command.
To display the configuration or status for any interface, perform this task:
This example shows how to display the configuration and status of the Fast Ethernet interface 5/4:
Router# show interfaces fastethernet 5/4
FastEthernet5/4 is up, line protocol is up
Hardware is Cat6K 100Mb Ethernet, address is 0050.f0ac.3058 (bia 0050.f0ac.3058)
Description: "Router port"
Internet address is 172.20.52.106/29
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:01, output never, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1008 packets input, 58331 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
466 packets output, 60213 bytes, 0 underruns
0 output errors, 0 collisions, 3 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Router#
These sections describe how to use the Domain Name System (DNS) on the Catalyst 6000 family switches:
DNS is a distributed database with which you can map host names to IP addresses through the DNS protocol from a DNS server. When you configure DNS on the Catalyst 6000 family switch, you can substitute the host name for the IP address with all IP commands, such as ping, telnet, upload, and download.
To use DNS, you must have a DNS name server present on your network.
You can specify up to six DNS name servers on the switch. The first server specified is the primary server. The switch sends DNS queries to the primary server first. If the query to the primary server fails, the backup servers are queried.
Table 20-1 shows the default DNS configuration.
| Feature | Default Value |
|---|---|
DNS enable state | Disabled |
DNS default domain name | Null |
DNS servers | None specified |
These sections describe how to configure DNS on the Catalyst 6000 family switch:
To configure the DNS on the switch, perform these tasks:
| Command | Purpose |
|---|---|
Router(config)# ip domain-name name | Configure the IP domain name. |
Router(config)# ip name-server ip-address | Specify the IP address of up to six DNS servers. |
This example shows how to configure the IP domain name the switch should use to cisco.com:
Router(config)# ip domain-name cisco.com
This example shows how to configure the IP addresses to the IP domain name servers the switch should use as 171.69.2.132 and 198.92.30.32:
Router(config)# ip name-server 171.69.2.132 198.92.30.32
To disable DNS on the switch, perform this task:
| Command | Purpose |
|---|---|
Router(config)# no ip domain-lookup | Disable DNS on the switch. |
This example shows how to disable DNS on the switch:
Router(config)# no ip domain-lookup
To display the DNS configuration for the switch, perform this task:
| Command | Purpose |
|---|---|
Router# show running-config | Show the DNS configuration of the switch. |
This example shows how to display the IP domain name and the IP addresses of the IP domain name servers:
Router# show running-config Building configuration... ! (Information Deleted) ! ip subnet-zero no ip routing ip domain-name cisco.com ip name-server 171.9.2.132 ip name-server 198.2.3.32
The system name on the Catalyst 6000 family switch is a user-configurable string used to identify the device. The default configuration has no system name configured.
If you do not manually configure a system name, the system name is obtained through DNS if you configure the switch as follows:
1. Assign an interface an IP address that is mapped to the switch name on the DNS server
2. Enable DNS on the switch
3. Specify at least one valid DNS server on the switch
If the DNS lookup is successful, the DNS host name of the switch is configured as the system name of the switch and is saved in NVRAM. The domain name is removed.
If you have not configured a system prompt, the first 20 characters of the system name are used as the system prompt (a greater-than symbol [>] is appended). The prompt is updated whenever the system name changes, unless the prompt is manually configured using the prompt command.
The switch performs a DNS lookup for the system name whenever one of the following occurs:
If the system name is user configured, no DNS lookup is performed.
These sections describe how to statically configure the system name and prompt:
To configure the system name, perform this task:
| Command | Purpose |
|---|---|
Router(config)# hostname name-string | Statically set the system name. |
This example shows how to configure the system name to Labrouter:
Router(config)# hostname Labrouter
To display the system name configuration for the switch, perform this task:
| Command | Purpose |
|---|---|
Router# show running-config | Display the system name configuration. |
This example shows how to display the system name configuration:
Labrouter# show running-config Building configuration... Current configuration: ! version 12.0 service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname Labrouter !
To configure a static prompt on the switch, perform this task:
| Command | Purpose |
|---|---|
Router(config)# prompt string | Configure the CLI prompt to override the EXEC mode hostname. |
This example shows how to configure the EXEC CLI prompt to DocRouter:
Labrouter(config)# prompt DocRouter> Labrouter(config)# ^Z DocRouter>
You can specify the system contact and location to help you with resource management tasks.
To configure the system location information, perform this task:
| Command | Purpose |
|---|---|
Router(config)# location string | Configure the location information string. |
This example shows how to configure the location description on the switch:
Router(config)# location ELB documentation lab
To display the system location configuration for the switch, perform this task:
| Command | Purpose |
|---|---|
Router# show running-config | Display the system location configuration. |
This example shows how to display the location configuration of the switch:
Router# show running-config Building configuration... (Information Deleted) ! location ELB documentation lab ! (Information Deleted)
You can create a single or multiline message banner that appears on the screen when someone logs in to the switch. The first character following the banner motd command is used to delimit the beginning and end of the banner text. Characters following the ending delineator are discarded. After entering the ending delineator, press Return. The banner must be fewer than 255 characters.
To configure the banner displayed at login, perform this task:
| Command | Purpose |
|---|---|
Router(config)# banner motd string | Configure the login banner. |
This example shows how to configure a login banner for the switch using the # symbol as the beginning and ending delineator:
Router(config)# banner motd # This is a secure site only authorized users allowed. For access contact technical support. # Router(config)#
This example shows the banner displayed from the previous configuration:
Unix> telnet 172.2.5.4 Trying 172.2.5.4... Connected to 172.2.5.4. Escape character is '^]'. This is a secure site only authorized users allowed. For access contact technical support. User Access Verification Password:
To display the login banner configuration for the switch, perform this task:
| Command | Purpose |
|---|---|
Router# show running-config | Display the login banner configuration. |
This example shows how to display the login banner configuration of the system:
Router# show running-config Building configuration... Current configuration: (Information Deleted) banner motd ^C This is a secure site only authorized users allowed. For access contact technical support. ^C !
All Cisco routers and switches provide an array of time-of-day services. With these services, Cisco products can accurately keep track of the current time and date, to synchronize multiple products to the same time, and to provide time services to other systems. These sections describe the time and calendar tasks:
For detailed configuration information on configuring SNTP or Vines time service, refer to the IOS Configuration Fundamentals Configuration Guide:
The system clock can provide time to the following services:
The system clock keeps track of time internally based on Coordinated Universal Time (UTC), also known as Greenwich Mean Time (GMT). You can configure information about the local time zone and summer time (daylight saving time) so that the time is displayed correctly for to the local time zone.
The system clock keeps track of whether the time is "authoritative" or not (that is, whether it has been set by a time source considered to be authoritative). If it is not authoritative, the time is available only for display purposes and is not redistributed.
The Network Time Protocol (NTP) is designed to time-synchronize a network of machines. NTP runs over User Datagram Protocol (UDP), which runs over IP. NTP is documented in RFC 1305.
An NTP network usually gets its time from an authoritative time source, such as a radio clock or an atomic clock attached to a time server. NTP then distributes this time across the network. NTP is extremely efficient; no more than one packet per minute is necessary to synchronize two machines to within a millisecond of one another.
NTP uses the concept of a "stratum" to describe how many NTP hops away a machine is from an authoritative time source. A stratum 1 time server has a radio or atomic clock directly attached, a stratum 2 time server receives its time via NTP from a stratum 1 time server, and so on. A machine running NTP automatically chooses as its time source the machine with the lowest stratum number that it is configured to communicate with via NTP. This strategy effectively builds a self-organizing tree of NTP speakers.
NTP avoids synchronizing to a machine whose time may not be accurate by never synchronizing to a machine that is not in turn synchronized and by comparing the time reported by several machines, and not synchronizing to a machine whose time is significantly different than the others, even if its stratum is lower.
The communications between machines running NTP (known as "associations") are usually statically configured; each machine is given the IP address of all machines with which it should form associations. Accurate timekeeping is possible by exchanging NTP messages between each pair of machines with an association. However, in a LAN environment, NTP can be configured to use IP broadcast messages instead. This alternative reduces configuration complexity because each machine can simply be configured to send or receive broadcast messages. However, information flow is one-way only.
Cisco's implementation of NTP does not support stratum 1 service; it is not possible to connect to a radio or atomic clock. We recommend that time service for your network be derived from the public NTP servers available in the IP Internet.
If the network is isolated from the Internet, Cisco's implementation of NTP allows a machine to act as though it is synchronized via NTP, when in fact it has determined the time using other means. Other machines then synchronize to that machine via NTP.
When multiple sources of time (VINES, system calendar, manual configuration) are available, NTP is always considered to be more authoritative. NTP time overrides the time set by any other method.
A number of manufacturers include NTP software for their host systems, and a publicly available version for systems running UNIX and its various derivatives is also available. This software allows host systems to be time-synchronized as well.
Simple Network Time Protocol (SNTP) typically provides time within 100 milliseconds of the accurate time, but it does not provide the complex filtering and statistical mechanisms of NTP. In addition, SNTP does not authenticate traffic, although you can configure extended access lists to provide some protection. An SNTP client is more vulnerable to misbehaving servers than an NTP client and should only be used in situations where strong authentication is not required.
You can configure SNTP to request and accept packets from configured servers or to accept NTP broadcast packets from any source. When multiple sources are sending NTP packets, the server with the best stratum is selected. (See the "Network Time Protocol" section section for a description of strata.) If multiple servers are at the same stratum, a configured server is preferred over a broadcast server. If multiple servers pass both tests, the first one to send a time packet is selected. SNTP only chooses a new server if it stops receiving packets from the currently selected server, or if a better server (according to the above criteria) is discovered.
Time service is also available when Banyan VINES is configured. This protocol is a standard part of VINES. Cisco's implementation allows the VINES time service to be used in two ways. First, if the system has learned the time from some other source, it can act as a VINES time server and provide time to other machines running VINES. It also can use the VINES time service to set the system clock if no other form of time service is available.
All switches contain a battery-powered calendar system that tracks the date and time across system restarts and power outages. This calendar system is always used to initialize the system clock when the system is restarted. It can also be considered to be an authoritative source of time and be redistributed via NTP or VINES time service if no other source is available. If NTP is running, the calendar can be periodically updated from NTP, compensating for the inherent drift in the calendar time.
NTP services are enabled on all interfaces by default.
For detailed NTP configuration information, refer to the IOS Configuration Fundamentals Configuration Guide.
If you want to authenticate the associations with other systems for security purposes, perform this task:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| Router(config)# ntp authenticate | Enable the NTP authentication feature. | ||
| Router(config)# ntp authentication-key number md5 value1 | Define the authentication keys. | ||
| Router(config)# ntp trusted-key-number | Define trusted authentication keys. |
| 1Currently the only key type supported is md5. |
An NTP association can be a peer association (this system is willing to either synchronize to the other system or to allow the other system to synchronize to it), or it can be a server association (only this system synchronizes to the other system, and not the other way around). If you want to form an NTP association with another system, perform one of these tasks:
| Command | Purpose |
|---|---|
Router(config)# ntp peer ip-address [version number] [key keyid] [source interface] [prefer] | Form a peer association with another system. |
Router(config)# ntp server ip-address [version number] [key keyid] [source interface] [prefer] | Form a server association with another system. |
Note that only one end of an association needs to be configured; the other system can automatically establish the association.
The system can either send broadcast packets or listen to them on an interface-by-interface basis. The estimated round-trip delay for broadcast packets can also be configured. Perform one or more of these tasks if you want to use the broadcast feature:
| Command | Purpose |
|---|---|
Router(config)# ntp broadcast [version number] | Send NTP broadcast packets. |
Router(config)# ntp broadcast client | Receive NTP broadcast packets. |
Router(config)# ntp broadcastdelay microseconds | Adjust estimated delay. |
You can control NTP access on two levels by completing the tasks in this section.
To control access to NTP services, you can create an NTP access group and apply a basic IP access list to it. To do so, perform this task:
| Command | Purpose |
|---|---|
Router(config)# ntp access-group {query-only | serve-only | serve | peer} access-list-number | Create an access group and apply a basic IP access list. |
The access group options are scanned in the following order, from least restrictive to most restrictive:
1. peer---Allows time requests and NTP control queries and allows the system to synchronize itself to a system whose address passes the access list criteria.
2. serve---Allows time requests and NTP control queries, but does not allow the system to synchronize itself to a system whose address passes the access list criteria.
3. serve-only---Allows only time requests from a system whose address passes the access list criteria.
4. query-only---Allows only NTP control queries from a system whose address passes the access list criteria.
If the source IP address matches the access lists for more than one access type, the first type is granted. If no access groups are specified, all access types are granted to all systems. If any access groups are specified, only the specified access types are granted.
For details on NTP control queries, refer to RFC 1305 (NTP version 3).
NTP services are enabled on all interfaces by default. To disable NTP packets from being received through an interface, perform this task:
| Command | Purpose |
|---|---|
Router(config)# ntp disable | Disable NTP services on a specific interface. |
When the system sends an NTP packet, the source IP address is normally set to the address of the interface through which the NTP packet is sent. To configure a specific interface from which the IP source address is be taken, perform this task:
| Command | Purpose |
|---|---|
Router(config)# ntp source interface | Configure an interface from which the IP source address is to be taken. |
This interface is used for the source address for all packets sent to all destinations. If a source address is to be used for a specific association, use the source parameter on the ntp peer or ntp server command shown in the "Configuring NTP Associations" section.
To configure the system as an authoritative NTP server, even if the system is not synchronized to an outside time source, perform this task:
| Command | Purpose |
|---|---|
Router(config)# ntp master [stratum] | Configure the system as an authoritative NTP server. |
 | Caution Use the ntp master command with extreme caution. It is very easy to override valid time sources using this command, especially if a low stratum number is configured. Configuring multiple machines in the same network with the ntp master command can cause instability in timekeeping if the machines do not agree on the time. |
On systems that have calendars, you can configure NTP to periodically update the calendar.
To configure NTP to update the calendar, perform this task:
| Command | Purpose |
|---|---|
Router(config)# ntp update-calendar | Configure NTP to update the calendar. |
If no other source of time is available, you can manually configure the current time and date after the system is restarted. The time remains accurate until the next system restart. We recommend that you use manual configuration only as a last resort.
To set up time services, complete the tasks in the following sections as needed. If you have an outside source to which the switch can synchronize, you do not need to manually set the system clock.
If you have an outside source on the network that provides time services (such as an NTP server or VINES time service), you do not need to manually set the system clock.
To set the system clock (if you do not have a time service source configured), perform one of these tasks:
| Command | Purpose |
|---|---|
Router# clock set hh:mm:ss date month year or Router# clock set hh:mm:ss month date year | Set the system clock. |
This example shows how to configure the time and date on the switch:
Router# clock set 15:22:00 13 September 1999 Router#
To display the time and date configuration for the switch, perform this task:
| Command | Purpose |
|---|---|
Router# show clock [detail] | Display the time and date configuration. |
This example shows how to display the time and date configuration of the switch:
Router# show clock 15:24:28.199 UTC Mon Sep 13 1999 Router#
Some switches have a separate system calendar in addition to the system clock. The calendar can set the system time and control the system clock, as well as enable the switch to act as a time service for the network.
To set the system calendar, perform one of these tasks:
| Command | Purpose |
|---|---|
Router# calendar set hh:mm:ss day month year | Set the calendar (US format). |
Router# calendar set hh:mm:ss month day year | Set the calendar (Non-US format). |
This example shows how to set the calendar on the switch:
Router# calendar set 15:29:00 13 September 1999
To display the calendar configuration of the switch, perform this task:
| Command | Purpose |
|---|---|
Router# show calendar | Display the calendar configuration. |
This example shows how to display the calendar configuration of the switch:
Router# show calendar 15:32:30 UTC Mon Sep 13 1999 Router#
Although the system clock is always initialized from the calendar when the system is restarted, by default it is not considered to be authoritative and is not redistributed with NTP or VINES Time Service.
For detailed network time source configuration information, refer to the IOS Configuration Fundamentals Configuration Guide.
To set the calendar as authoritative, perform this task:
| Command | Purpose |
|---|---|
Router# clock calendar-valid | Enable the switch to act as a valid time source to which network peers can synchronize. |
To set the system clock to the new calendar setting, perform this task:
| Command | Purpose |
|---|---|
Router# clock read-calendar | Set the system clock from the calendar. |
To update the calendar with the new clock setting, perform this task:
| Command | Purpose |
|---|---|
Router# clock update-calendar | Set the calendar from the system clock. |
To monitor the clock, calendar, and NTP EXEC services, perform one of these commands:
| Command | Purpose |
|---|---|
Router# show calendar | Display the current calendar time. |
Router# show clock [detail] | Display the current system clock time. |
Router# show ntp associations [detail] | Display the status of NTP associations. |
Router# show ntp status | Display the status of NTP. |
Router# show sntp | Display information about SNTP. |
The Catalyst 6000 family switch software uses the Cisco IOS File System (IFS) software. With IFS, you can now access files on a storage device by specifying a filename and the file system containing the file. The following old command, for example, accesses the running-config and startup-config files:
Router# copy running-config startup-config
With IFS, you additionally specify the system containing the files using the syntax filesystem:filename. For example:
Router# copy system:running-config nvram:startup-config
The syntax filesystem:filename is called the file URL. In addition, you can use remote file systems, such as TFTP, FTP, and rcp, to specify additional options in the file URL, such as username, password, remote host, and so on. This way, you can enter all the required information at once without having to respond to prompts.
With IFS, some show commands have been replaced with more commands. For example:
Router# show running-config
has been replaced with this following command:
Router# more system:running-config
For complete information on using file URLs and the new IFS commands and syntax, refer to the Configuration Fundamentals Configuration Guide and the Configuration Fundamentals Command Reference publication.
File systems on the Catalyst 6000 family switch include read-only memory (RAM, or system), Flash memory (such as bootflash and the Flash PC cards in slot0 and slot1), and remote file systems (such as TFTP or rcp servers).
You can use the show file systems privileged EXEC command to display the valid file systems on your switch. For example:
Router# show file systems
File Systems:
Size(b) Free(b) Type Flags Prefixes
- - flash rw disk0:
- - flash rw disk1:
- - opaque rw null:
- - opaque rw system:
- - network rw tftp:
* 16384000 5949860 flash rw slot0: flash:
129004 129004 nvram rw const_nvram:
15990784 5578664 flash rw sup-bootflash:
126968 121606 nvram rw nvram:
15990784 6440392 flash rw bootflash:
- - network rw rcp:
- - network rw ftp:
Router#
Refer to the Configuration Fundamentals Configuration Guide for details on the following frequently performed tasks:
These sections list common tasks you perform to maintain system images and configuration files on your Catalyst 6000 family switch:
For detailed file system information, refer to the IOS Configuration Fundamentals Configuration Guide.
| Caution Do not erase the boot helper image (c6msfc-boot-mz) from the MSFC bootflash: device. The boot helper must be present for the switch to boot successfully. |
Perform these tasks to maintain configuration files:
For detailed file system information, refer to the IOS Configuration Fundamentals Configuration Guide.
Perform these tasks to maintain system image files:
This example shows how to copy the system image halley from a TFTP server to the slot0: Flash device:
Router# copy tftp:halley slot0:
This example shows how to copy the system image halley from the Flash device slot0: to the supervisor engine bootflash:
Router# copy slot0:halley sup-bootflash:
This example shows how to configure the switch to automatically boot the image halley from supervisor engine bootflash:
Router# config terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# boot system sup-bootflash:halley Router(config)#
For detailed file system information, refer to the IOS Configuration Fundamentals Configuration Guide.
Perform these tasks to reboot the Catalyst 6000 family switch and specify startup information:
For detailed file system information, refer to the IOS Configuration Fundamentals Configuration Guide.
The following file configuration file transfer options are also available:
For detailed file system information, refer to the IOS Configuration Fundamentals Configuration Guide.
Posted: Mon Jan 3 14:49:31 PST 2000
Copyright 1989-1999©Cisco Systems Inc.