Using Configuration Tools

Cisco IOS includes a number of configuration tools that simplify the process of setting up the initial configuration of a router or access server. This chapter describes the following configuration tools:

• Using AutoInstall

• Using Setup for Configuration Changes

• Using Other Configuration Tools

For a complete description of the configuration tools commands in this chapter, refer to the "Configuration Tools Commands" chapter in the Configuration Fundamentals Command Reference. To locate documentation of other commands, use the command reference index or search online.

Using AutoInstall

This section provides information about AutoInstall, a procedure that allows you to configure a new router automatically and dynamically. The AutoInstall procedure involves connecting a new router to a network where an existing router is preconfigured, turning on the new router, and enabling it with a configuration file that is automatically downloaded from a Trivial File Transfer Protocol (TFTP) server.

The following sections provide the requirements for AutoInstall and an overview of how the procedure works. To start the procedure, see the "Perform the AutoInstall Procedure" section.

AutoInstall Requirements

For the AutoInstall procedure to work, your system must meet the following requirements:

• Routers must be physically attached to the network using one or more of the following interface types: Ethernet, Token Ring, Fiber Distributed Data Interface (FDDI), serial with High-Level Data Link Control (HDLC) encapsulation, or serial with Frame Relay encapsulation. HDLC is the default serial encapsulation. If the AutoInstall process fails over HDLC, the Cisco IOS software automatically configures Frame Relay encapsulation.

• The existing preconfigured router must be running Software Release 9.1 or later. For AutoInstall over Frame Relay, this router must be running Cisco IOS Release 10.3 or later.

• The new router must be running Software Release 9.1 or later. For AutoInstall over Frame Relay, the new router must be running Cisco IOS Release 10.3 or later.

• You must complete procedure 1 and either procedure 2 or 3:

  • Procedure 1: A configuration file for the new router must reside on a TFTP server. This file can contain the full configuration or the minimum needed for the administrator to Telnet into the new router for configuration. In addition, make sure to complete one of the following procedures.

  • Procedure 2: A file named network-confg also must reside on the server. The file must have an Internet Protocol (IP) host name entry for the new router. The server must be reachable from the existing router.

  • Procedure 3: An IP address-to-host name mapping for the new router must be added to a Domain Name System (DNS) database file.

• If the existing router is to help automatically install the new router via an HDLC-encapsulated serial interface using Serial Line Address Resolution Protocol (SLARP), that interface must be configured with an IP address whose host portion has the value 1 or 2. (AutoInstall over Frame Relay does not have this address constraint.) Subnet masks of any size are supported.

• If the existing router is to help automatically install the new router using a Frame Relay-encapsulated serial interface, that interface must be configured with the following:

  • An IP helper address pointing to the TFTP server. In the following example, 171.69.2.75 is the address of the TFTP server:

  ip helper 171.69.2.75
  

  • A Frame Relay map pointing back to the new router. In the following example, 172.21.177.100 is the IP address of the new router's serial interface, and 100 is the PVC identifier:

  frame-relay map ip 172.21.177.100 100 dlci
  

• If the existing router is to help automatically install the new router via an Ethernet, Token Ring, or FDDI interface using BOOTP or Reverse Address Resolution Protocol (RARP), a BOOTP or RARP server also must be set up to map the new router's Media Access Control (MAC) address to its IP address.

• IP helper addresses might need to be configured to forward the TFTP and DNS broadcast requests from the new router to the host that is providing those services.

Using a DOS-Based TFTP Server

AutoInstall over Frame Relay and other WAN encapsulations support downloading configuration files from UNIX-based and DOS-based TFTP servers. Other booting mechanisms such as RARP and SLARP also support UNIX-based and DOS-based TFTP servers.

How AutoInstall Works

Once the requirements for using AutoInstall are met, the dynamic configuration of the new router occurs in the following order:

1. The new router acquires its IP address. Depending on the interface connection between the two routers and/or access servers, the new router's IP address is dynamically resolved by either SLARP requests or BOOTP or RARP requests.
   
   
2. The new router resolves its name through network-confg, cisconet.cfg, or DNS.
   
   
3. The new router automatically requests and downloads its configuration file from a TFTP server.
   
   
4. If a host name is not resolved, the new router attempts to load router-confg or ciscortr.cfg.
   

Acquiring the New Router's IP Address

The new router (newrouter) resolves its interface's IP addresses by one of the following means:

• If newrouter is connected by an HDLC-encapsulated serial line to the existing router (existing), newrouter sends a SLARP request to existing.

• If newrouter is connected by an Ethernet, Token Ring, or FDDI interface, it broadcasts BOOTP and RARP requests.

• If newrouter is connected by a Frame Relay-encapsulated serial interface, it first attempts the HDLC automatic installation process and then attempts the BOOTP or RARP process over Ethernet, Token Ring, or FDDI. If both attempts fail, the new router attempts to automatically install over Frame Relay. In this case, a BOOTP request is sent over the lowest numbered serial or HSSI interface.

The existing router (existing) responds in one of the following ways depending on the request type:

• In response to a SLARP request, existing sends a SLARP reply packet to newrouter. The reply packet contains the IP address and netmask of existing. If the host portion of the IP address in the SLARP response is 1, newrouter configures its interface using the value 2 as the host portion of its IP address and vice versa. (See Figure 5.)

A BOOTP or RARP server must have already been set up to map newrouter's MAC address to its IP address. If the BOOTP server does not reside on the directly attached network segment, routers between newrouter and the BOOTP server can be configured with the ip helper-address command to allow the request and response to be forwarded between segments, as shown in Figure 6.

AutoInstall over Frame Relay is a special case in that the existing router acts as a BOOTP server and responds to the incoming BOOTP request. Only a helper address and a Frame Relay map need to be set up. No MAC-to-IP address map is needed on the existing router.

Resolving the IP Address to the Host Name

The new router resolves its IP address-to-host name mapping by sending a TFTP broadcast requesting the file network-confg, as shown in Figure 7.

The network-confg file is a configuration file generally shared by several routers. In this case, it is used to map the IP address of the new router (just obtained dynamically) to the name of the new router. The file network-confg must reside on a reachable TFTP server and must be globally readable.

ip host newrouter 131.108.10.2

If newrouter does not receive a network-confg or a cisconet.cfg file, or if the IP address-to-host-name mapping does not match the newly acquired IP address, newrouter sends a DNS broadcast. If DNS is configured and has an entry that maps newrouter's SLARP, BOOTP, or RARP-acquired IP address to its name, newrouter successfully resolves its name.

Downloading the New Router's Host Configuration File

After the router successfully resolves its host name, newrouter sends a TFTP broadcast requesting the file newrouter-confg or newrouter.cfg. The name newrouter-confg must be in all lowercase letters, even if the true host name is not. If newrouter cannot resolve its host name, it sends a TFTP broadcast requesting the default host configuration file router-confg. The file is downloaded to newrouter, where the configuration commands take effect immediately.

When using AutoInstall over Frame Relay, you are put into setup mode while the AutoInstall process is running. If the configuration file is successfully installed, the setup process is terminated. If you expect the AutoInstall process to be successful, either do not respond to the setup prompts or respond to the prompts as follows:

Would you like to enter the initial configuration dialog? [yes]: no
Would you like to terminate autoinstall? [yes]: no

If you do not expect the AutoInstall process to be successful, create a configuration file by responding to the setup prompts. The AutoInstall process is terminated transparently.

You will see the following display as the AutoInstall operation is in progress:

Please Wait. AutoInstall being attempted!!!!!!!!!!!!!!!!!!!

If the host configuration file contains only the minimal information, you must connect using Telnet into existing, from there connect via Telnet to newrouter, and then run the setup command to configure newrouter. Refer to the "Using Setup for Configuration Changes" section later in this chapter for details on the setup command.

If the host configuration file is complete, newrouter should be fully operational. You can enter the enable command (with the system administrator password) at the system prompt on newrouter, and then issue the copy running-config startup-config command to save the information in the recently obtained configuration file into nonvolatile random-access memory (NVRAM) or to the location specified by the CONFIG_FILE environment variable. If it must reload, newrouter simply loads its configuration file from NVRAM.

If the TFTP request fails, or if newrouter still has not obtained the IP addresses of all its interfaces, and those addresses are not contained in the host configuration file, then newrouter enters setup mode automatically. Setup mode prompts you for manual configuration of the Cisco IOS software at the console. The new router continues to issue broadcasts to attempt to learn its host name and obtain any unresolved interface addresses. The broadcast frequency will dwindle to every 10 minutes after several attempts. Refer to the "Using Setup for Configuration Changes" section later in this chapter for details on the setup command.

Perform the AutoInstall Procedure

To dynamically configure a new router using AutoInstall, complete the following tasks. Steps 1, 2, and 3 are completed by the central administrator. Step 4 is completed by the person at the remote site.

Step 1 Modify the existing router's configuration to support the AutoInstall procedure.

Step 2 Set up the TFTP server to support the AutoInstall procedure.

Step 3 Set up the BOOTP or RARP server if needed. A BOOTP or RARP server is required for AutoInstall using an Ethernet, Token Ring, FDDI, or Frame Relay-encapsulated serial interface. With a Frame Relay-encapsulated serial interface, the existing router acts as the BOOTP server. A BOOTP or RARP server is not required for AutoInstall using an HDLC-encapsulated serial interface.

Step 4 Connect the new router to the network.

Modify the Existing Router's Configuration

You can use any of the following types of interfaces:

• An HDLC-encapsulated serial line (the default configuration for a serial line)

• An Ethernet, Token Ring, FDDI interface

• A Frame Relay-encapsulated serial line

Use an HDLC-Encapsulated Serial Interface Connection

In the following example, the existing router's configuration file contains the commands needed to configure the router for AutoInstall on a serial line using HDLC encapsulation:

Router# configure terminal
interface serial 0
 ip address 172.31.10.1 255.255.255.0
 ip helper-address 172.31.20.5
 Ctrl-Z
Router(config)# copy running-config startup-config

Use an Ethernet, Token Ring, or FDDI Interface Connection

In the following example, the existing router's configuration file contains the commands needed to configure the router for AutoInstall on an Ethernet interface:

Router# configure terminal
interface Ethernet 0
 ip address 172.31.10.1 255.255.255.0
 ip helper-address 172.31.20.5
 Ctrl-Z
Router(config)# copy running-config startup-config

Use a Frame Relay-Encapsulated Serial Interface Connection

In the following example, the existing router's configuration file contains the commands needed to configure the router for Frame Relay AutoInstall on a serial line:

Router# configure terminal
interface serial 0
 ip address 172.31.20.20 255.255.255.0
 encapsulation frame-relay
 frame-relay map ip 172.31.10.1 255.255.255.0 48
 ip helper-address 172.31.20.5

Set Up the TFTP Server

For AutoInstall to work correctly, the new router must be able to resolve its host name and then download a name-confg or a name.cfg file from a TFTP server. The new router can resolve its host name by using a network-confg or a cisconet.cfg file downloaded from a TFTP server or by using the DNS.

To set up a TFTP server to support AutoInstall, complete the following tasks. Step 2 includes two ways to resolve the new router's host name. Use the first method if you want to use a network-config file to resolve the new router's host name. Use the second method if you want to use DNS to resolve the new router's host name.

The name-confg or the name.cfg file can contain either the new router's full configuration or a minimal configuration.

The minimal configuration file is a virtual terminal password and an enable password. It allows an administrator to Telnet into the new router to configure it. If you are using BOOTP or RARP to resolve the address of the new router, the minimal configuration file must also include the IP address to be obtained dynamically using BOOTP or RARP.

You can use the copy running-config tftp command to help you generate the configuration file that you will download during the AutoInstall process.

You can save a minimal configuration under a generic newrouter-confg file. Use the ip host command in the network-confg or cisconet.cfg file to specify newrouter as the host name with the address you will be dynamically resolving. The new router should then resolve its IP address, host name, and minimal configuration automatically. Use Telnet to connect to the new router from the existing router and use the setup facility to configure the rest of the interfaces. For example, the line in the network-confg or cisconet.cfg file could be similar to the following:

ip host newrouter 131.108.170.1

enable-password letmein
!
line vty 0
password letmein
!
end

The following minimal network configuration file maps the new router's IP address, 131.108.10.2, to the host name newrouter. The new router's address was learned via SLARP and is based on the existing router's IP address of 131.108.10.1.

ip host newrouter 131.108.10.2

Set Up the BOOTP or RARP Server

If the new router is connected to the existing router using an Ethernet, Token Ring, or FDDI interface, you must configure a BOOTP or RARP server to map the new router's MAC address to its IP address. If the new router is connected to the existing router using a serial line with HDLC encapsulation or if you are configuring AutoInstall over Frame Relay, the tasks in this section are not required.

To configure a BOOTP or RARP server, complete one of the following tasks:

The following host configuration file contains the minimum set of commands needed for AutoInstall using RARP. It includes the IP address that will be obtained dynamically via BOOTP or RARP during the AutoInstall process. When RARP is used, this extra information is needed to specify the proper netmask for the interface.

interface ethernet 0
 ip address 131.108.10.2 255.255.255.0
enable-password letmein
!
line vty 0
 password letmein
!
end

Connect the New Router to the Network

Connect the new router to the network using either an HDLC-encapsulated or Frame Relay-encapsulated serial interface or an Ethernet, Token Ring, or FDDI interface. After the router successfully resolves its host name, newrouter sends a TFTP broadcast requesting the file name-confg or name.cfg. The router name must be in all lowercase, even if the true host name is not. The file is downloaded to the new router, where the configuration commands take effect immediately. If the configuration file is complete, the new router should be fully operational. To save the complete configuration to NVRAM, complete the following tasks in privileged EXEC mode:

Caution Verify that the existing and new routers and/or access servers are connected before entering the copy running-config startup-config EXEC command to save configuration changes. Use the ping EXEC command to verify connectivity. If an incorrect configuration file is downloaded, the new router will load NVRAM configuration information before it can enter AutoInstall mode.

If the configuration file is a minimal configuration file, the new router comes up, but with only one interface operational. Complete the following steps to connect to the new router and configure it:

Using Setup for Configuration Changes

The setup command facility is an interactive facility that allows you to perform first-time configuration and other basic configuration procedures on all routers. The facility prompts you to enter basic information needed to start a router functioning quickly and uneventfully.

Although the setup command facility is a quick way to "set up" a router, you can also use it after first-time startup to perform basic configuration changes. This section focuses on the following:

• How to use the setup command facility after first-time startup

• How to use the streamlined setup facility

Refer to your hardware platform's user guide for more information on how to use setup for first-time startup.

Whenever you use the setup command facility, be sure that you know the following:

Setup Command Facility Task List

You can perform the tasks in the following sections to make configuration changes using the setup command facility. Both tasks are optional.

• Use Setup after First-Time Startup

• Use the Streamlined Setup Facility

Use Setup after First-Time Startup

The command parser allows you to make very detailed changes to your configurations. However, some major configuration changes do not require the granularity provided by the command parser. In these cases, you can use the setup command facility to make major enhancements to your configurations. For example, you might want to use setup to add a protocol suite, to make major addressing scheme changes, or to configure a newly installed interface. Although you can use the command parser to make these major changes, the setup command facility provides you with a high-level view of the configuration and guides you through the configuration change process.

Additionally, if you are not familiar with Cisco products and the command parser, the setup command facility is a particularly valuable tool because it asks you the questions required to make configuration changes.

To enter the setup command facility, perform the following task in privileged EXEC mode:

When you enter the setup command facility after first-time startup, an interactive dialog called the System Configuration Dialog appears on the system console screen. The System Configuration Dialog guides you through the configuration process. It prompts you first for global parameters and then for interface parameters. The values shown in brackets next to each prompt are the default values last set using either the setup command facility or the configure command.

To return to the privileged EXEC prompt without making changes and without running through the entire System Configuration Dialog, press Ctrl-C.

When you complete your changes, the setup command facility shows you the configuration command script that was created during the setup session. It also asks you if you want to use this configuration. If you answer Yes, the configuration is saved to NVRAM. If you answer No, the configuration is not saved and the process begins again. There is no default for this prompt; you must answer either Yes or No.

The following example shows how to use the setup command facility to configure interface serial 0 and to add ARAP and IP/IPX PPP support on the asynchronous interfaces:

Router# setup
         --- System Configuration Dialog ---
At any point you may enter a question mark '?' for help.
Use ctrl-c to abort configuration dialog at any prompt.
Default settings are in square brackets '[]'.
Continue with configuration dialog? [yes]: 
First, would you like to see the current interface summary? [yes]: 
Interface          IP-Address      OK?  Method    Status                 Protocol
Ethernet0          172.16.72.2     YES  manual    up                     up      
Serial0            unassigned      YES  not set   administratively down  down    
Serial1            172.16.72.2     YES  not set   up                     up    
Configuring global parameters:
  Enter host name [Router]: 
The enable secret is a one-way cryptographic secret used
instead of the enable password when it exists.
  Enter enable secret []: 
The enable password is used when there is no enable secret
and when using older software and some boot images.
  Enter enable password [ww]: 
  Enter virtual terminal password [ww]: 
  Configure SNMP Network Management? [yes]: 
    Community string [public]: 
  Configure DECnet? [no]: 
  Configure AppleTalk? [yes]: 
    Multizone networks? [no]: yes
  Configure IPX? [yes]: 
  Configure IP? [yes]: 
    Configure IGRP routing? [yes]: 
      Your IGRP autonomous system number [15]: 
  Configure Async lines? [yes]: 
    Async line speed [9600]: 57600
    Configure for HW flow control? [yes]: 
    Configure for modems? [yes/no]: yes
      Configure for default chat script? [yes]: no
    Configure for Dial-in IP SLIP/PPP access? [no]: yes
      Configure for Dynamic IP addresses? [yes]: no 
      Configure Default IP addresses? [no]: yes
      Configure for TCP Header Compression? [yes]: no
      Configure for routing updates on async links? [no]: 
    Configure for Async IPX? [yes]: 
    Configure for Appletalk Remote Access? [yes]: 
      AppleTalk Network for ARAP clients [1]: 20
      Zone name for ARAP clients [ARA Dialins]: 
Configuring interface parameters:
Configuring interface Ethernet0:
  Is this interface in use? [yes]: 
  Configure IP on this interface? [yes]: 
    IP address for this interface [172.16.72.2]: 
    Number of bits in subnet field [8]: 
    Class B network is 172.16.0.0, 8 subnet bits; mask is /24
  Configure AppleTalk on this interface? [yes]: 
    Extended AppleTalk network? [yes]: 
    AppleTalk starting cable range [1]: 
    AppleTalk ending cable range [1]: 
    AppleTalk zone name [Sales]: 
    AppleTalk additional zone name: 
  Configure IPX on this interface? [yes]: 
    IPX network number [1]: 
Configuring interface Serial0:
  Is this interface in use? [no]: yes
  Configure IP on this interface? [no]: yes
  Configure IP unnumbered on this interface? [no]: yes
    Assign to which interface [Ethernet0]: 
  Configure AppleTalk on this interface? [no]: yes
    Extended AppleTalk network? [yes]: 
    AppleTalk starting cable range [2]: 3
    AppleTalk ending cable range [3]: 3
    AppleTalk zone name [myzone]: ZZ Serial
    AppleTalk additional zone name: 
  Configure IPX on this interface? [no]: yes
    IPX network number [2]: 3
Configuring interface Serial1:
  Is this interface in use? [yes]: 
  Configure IP on this interface? [yes]: 
  Configure IP unnumbered on this interface? [yes]: 
    Assign to which interface [Ethernet0]: 
  Configure AppleTalk on this interface? [yes]: 
    Extended AppleTalk network? [yes]: 
    AppleTalk starting cable range [2]: 
    AppleTalk ending cable range [2]: 
    AppleTalk zone name [ZZ Serial]: 
    AppleTalk additional zone name: 
  Configure IPX on this interface? [yes]: 
    IPX network number [2]: 
Configuring interface Async1: 
    IPX network number [4]: 
    Default client IP address for this interface [none]: 172.16.72.4 
Configuring interface Async2:
    IPX network number [5]: 
    Default client IP address for this interface [172.16.72.5]: 
Configuring interface Async3:
    IPX network number [6]: 
    Default client IP address for this interface [172.16.72.6]: 
Configuring interface Async4:
    IPX network number [7]: 
    Default client IP address for this interface [172.16.72.7]: 
Configuring interface Async5:
    IPX network number [8]: 
    Default client IP address for this interface [172.16.72.8]: 
Configuring interface Async6:
    IPX network number [9]: 
    Default client IP address for this interface [172.16.72.9]: 
Configuring interface Async7:
    IPX network number [A]: 
    Default client IP address for this interface [172.16.72.10]: 
Configuring interface Async8:
    IPX network number [B]: 
    Default client IP address for this interface [172.16.72.11]: 
Configuring interface Async9:
    IPX network number [C]:  
    Default client IP address for this interface [172.16.72.12]:  
Configuring interface Async10:
    IPX network number [D]: 
    Default client IP address for this interface [172.16.72.13]: 
Configuring interface Async11:
    IPX network number [E]: 
    Default client IP address for this interface [172.16.72.14]: 
Configuring interface Async12:
    IPX network number [F]: 
    Default client IP address for this interface [172.16.72.15]: 
Configuring interface Async13:
    IPX network number [10]: 
    Default client IP address for this interface [172.16.72.16]: 
Configuring interface Async14:
    IPX network number [11]: 
    Default client IP address for this interface [172.16.72.17]: 
Configuring interface Async15:
    IPX network number [12]: 
    Default client IP address for this interface [172.16.72.18]: 
Configuring interface Async16: 
    IPX network number [13]: 
    Default client IP address for this interface [172.16.72.19]:  
The following configuration command script was created:
hostname Router
enable secret 5 $1$krIg$emfYm/1OwHVspDuS8Gy0K1
enable password ww
line vty 0 4
password ww
snmp-server community public
!
no decnet routing
appletalk routing
ipx routing
ip routing
!
line 1 16
speed 57600
flowcontrol hardware
modem inout
!
arap network 20 ARA Dialins
line 1 16
arap enable
autoselect
!
! Turn off IPX to prevent network conflicts.
interface Ethernet0
no ipx network
interface Serial0
no ipx network
interface Serial1
no ipx network
!
interface Ethernet0
ip address 172.16.72.2 255.255.255.0
appletalk cable-range 1-1 1.204
appletalk zone Sales
ipx network 1
no mop enabled
!
interface Serial0
no shutdown
no ip address
ip unnumbered Ethernet0
appletalk cable-range 3-3
appletalk zone ZZ Serial
ipx network 3
no mop enabled
!
interface Serial1
no ip address
ip unnumbered Ethernet0
appletalk cable-range 2-2 2.2
appletalk zone ZZ Serial
ipx network 2
no mop enabled
!
Interface Async1
ipx network 4
ip unnumbered Ethernet0
peer default ip address 172.16.72.4
async mode interactive
!
Interface Async2
ipx network 5
ip unnumbered Ethernet0
peer default ip address 172.16.72.5
async mode interactive
!
Interface Async3
ipx network 6
ip unnumbered Ethernet0
peer default ip address 172.16.72.6
async mode interactive
!
Interface Async4
ipx network 7
ip unnumbered Ethernet0
peer default ip address 172.16.72.7
async mode interactive
async dynamic address
!
Interface Async5
ipx network 8
ip unnumbered Ethernet0
peer default ip address 172.16.72.8
async mode interactive
!
Interface Async6
ipx network 9
ip unnumbered Ethernet0
peer default ip address 172.16.72.9
async mode interactive
!
Interface Async7
ipx network A
ip unnumbered Ethernet0
peer default ip address 172.16.72.10
async mode interactive
!
Interface Async8
ipx network B
ip unnumbered Ethernet0
peer default ip address 172.16.72.11
async mode interactive
!
Interface Async9
ipx network C
ip unnumbered Ethernet0
peer default ip address 172.16.72.12
async mode interactive
!
Interface Async10
ipx network D
ip unnumbered Ethernet0
peer default ip address 172.16.72.13
async mode interactive
!
Interface Async11
ipx network E
ip unnumbered Ethernet0
peer default ip address 172.16.72.14
async mode interactive
!
Interface Async12
ipx network F
ip unnumbered Ethernet0
peer default ip address 172.16.72.15
async mode interactive
!
Interface Async13
ipx network 10
ip unnumbered Ethernet0
peer default ip address 172.16.72.16
async mode interactive
!
Interface Async14
ipx network 11
ip unnumbered Ethernet0
peer default ip address 172.16.72.17
async mode interactive
!
Interface Async15
ipx network 12
ip unnumbered Ethernet0
peer default ip address 172.16.72.18
async mode interactive
!
Interface Async16
ipx network 13
ip unnumbered Ethernet0
peer default ip address 172.16.72.19
async mode interactive
!
router igrp 15
network 172.16.0.0
!
end
Use this configuration? [yes/no]: yes
Building configuration...
Use the enabled mode 'configure' command to modify this configuration.      
Router#

Use the Streamlined Setup Facility

The streamlined setup command facility is available only if your router is running from ROM monitor and has RXBOOT ROMs installed. The following routers can have this type of ROM installed:

• Cisco 2500 running the IGS-RXBOOT image

• Cisco 3000 running the IGS-RXBOOT image

• Cisco 4000 running the XX-RXBOOT image

• Other routers running the RXBOOT image

The streamlined setup command facility permits your router to load a system image from a network server when there are problems with the startup configuration. The Cisco IOS software automatically puts you in the streamlined setup command facility when your router is accidentally or intentionally rebooted (or you are attempting to load a system image from a network server) after any of the following circumstances:

• You issued an erase startup-config command, thereby deleting the startup configuration file.

• You have bit 6 (ignore NVRAM configuration) set in the configuration register.

• Your startup configuration has been corrupted.

• You configured the router to boot from a network server (the last four bits of the configuration register are not equal to 0 or 1) and there is no Flash or no valid image in Flash.

• You configured the router to boot the RXBOOT image.

The streamlined setup command facility differs from the standard setup command facility because the streamlined facility does not ask you to configure global router parameters. You are prompted only to configure interface parameters, which permit your router to boot.

The following example shows a router entering the streamlined setup command facility:

         --- System Configuration Dialog ---
Default settings are in square brackets '[]'.
Configuring interface IP parameters for netbooting: 

Configuring interface Ethernet0:
  Is this interface in use? [yes]: 
  Configure IP on this interface? [yes]:
    IP address for this interface: 192.195.78.50
    Number of bits in subnet field [0]: 5
    Class C network is 192.195.78.0, 5 subnet bits; mask is 255.255.255.248
Configuring interface Serial0:
  Is this interface in use? [yes]: 
  Configure IP on this interface? [yes]:
    IP address for this interface: 192.195.78.34
    Number of bits in subnet field [5]:
    Class C network is 192.195.78.0, 5 subnet bits; mask is 255.255.255.248

Using Other Configuration Tools

You can also you configure the Cisco IOS using one of the following tools:

• ClickStart

• ConfigMaker

For more information on using these configuration tools, refer to the documentation shipped with your product or configuration tool.

ClickStart

ClickStart enables you to configure and monitor a router using a World Wide Web browser. ClickStart can be used to configure a router to connect a small office or home PC to the Internet or to another network. In this environment, your PC is connected to the router via an Ethernet connection. You configure the router to dial your Internet service provider, and your Internet service provider supplies an ISDN, Frame Relay, or Asynchronous Serial connection to the Internet. You do not need to have an extensive background in networks and routers to configure your router using ClickStart.

You can use ClickStart to configure a Cisco 1003 or Cisco 1004 ISDN router running Cisco IOS Release 11.0(6) or later software, or Cisco IOS Release 11.1(2) or later software. You can also use ClickStart to configure a Cisco 1005 Frame Relay or Asynchronous Serial router running Cisco IOS Release 11.1(5) or later software. ClickStart is also available for the Cisco 1600 series and Cisco 700 series.

ConfigMaker

Use Cisco ConfigMaker on a Windows 95 or Windows NT system to quickly and easily configure Cisco 1000 series, Cisco 1600 series, Cisco 2500 series, and Cisco 3600 series routers and access servers from a single PC. Use this application to create a network of devices, make connections between devices, automatically assign addresses, and deliver configurations to routers by using the COM port on the computer. Cisco ConfigMaker is designed for resellers and network administrators of small to medium-sized businesses who are proficient in LAN fundamentals and basic network design.

ConfigMaker makes configuring a High-Level Data Link Control (HDLC), Frame Relay or ISDN wide-area network connection between routers or the Internet as easy as drawing a network diagram. The tool guides users step-by-step through network design and addressing tasks and automatically delivers configuration files to individual routers on the network. ConfigMaker provides a graphical view of the entire network and lets the user build network diagrams using standard copy/paste, drag/drop and online editing functions. ConfigMaker enables the user to monitor router and network configuration status at a glance with simple color codes.