-
Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.4T
- Part 1: Using the Cisco IOS Command-Line Interface (CLI)
- Part 2: Configuration Using Setup and Autoinstall
- Part 3: Configuring Operating Characteristics for Terminals
- Part 4: Managing Connections, Menus, and System Banners
- Part 5: Using the Cisco IOS Integrated File System
- Part 6: Configuring Basic File Transfer Services
-
Part 7: Managing Configuration Files
-
Managing Configuration Files
-
Configuration Generation Performance Enhancement
-
Exclusive Configuration Change Access (Configuration Lock) and Access Session Locking
-
Configuration Replace and Configuration Rollback
-
Contextual Configuration Diff Utility
-
Configuration Change Notification and Logging
-
Configuration Logger Persistency
-
- Part 8: Loading and Maintaining System Images
- Part 9: Maintaining System Memory
- Part 10: Advanced Infrastructure Management
Table Of Contents
Using AutoInstall to Remotely Configure Cisco Networking Devices
Prerequisites for Using AutoInstall to Remotely Configure Cisco Networking Devices
Restrictions for Using AutoInstall to Remotely Configure Cisco Networking Devices
Information About Using AutoInstall to Remotely Configure Cisco Networking Devices
Services and Servers Used By AutoInstall: Dynamic Assignment of IP Addresses
Services and Servers Used By AutoInstall: IP-to-Hostname Mapping
Services and Servers Used By AutoInstall: Storage and Transmission of Configuration Files
Networking Devices Used by AutoInstall
Configuration Files Used by AutoInstall
Configuration Options for AutoInstall
Benefits of Using AutoInstall to Remotely Configure a Cisco Networking Device
AutoInstall Using DHCP for LAN Interfaces
AutoInstall over Frame Relay-ATM Interworking Connections
How to Use AutoInstall to Remotely Configure Cisco Networking Devices
Disabling the SDM Default Configuration File
Using AutoInstall with Frame Relay to ATM Service Internetworking
Configuring R6 for Frame Relay to ATM Service Internetworking
Verifying Frame Relay to ATM Service Internetworking on R6
Configuring R4 for Frame Relay to ATM Service Internetworking
Creating the Configuration File for R2
Verifying AutoInstall with Frame Relay to ATM Service Internetworking
Configuration Examples for Using AutoInstall to Remotely Configure Cisco Networking Devices
Using AutoInstall to Set Up Devices Connected to LANs: Example
Determining the Value for the DHCP Client Identifier Manually
Determining the Value for the DHCP Client Identifier Automatically
Creating a Private DHCP Pool for Each of The Routers
Creating Configuration Files for Each Router
Creating the network-confg file
Setting Up the Routers with AutoInstall
Saving the Configuration Files on The Routers
Removing the Private DHCP Address Pools from R1
Using AutoInstall to Set Up Devices Connected to WANs: Example
Feature Information for Using AutoInstall to Remotely Configure a Cisco Networking Device
Using AutoInstall to Remotely Configure Cisco Networking Devices
First published: November 28, 2005Last updated: May 2, 2008AutoInstall enables remote, automatic configuration of networking devices. AutoInstall is typically used to set up new networking devices remotely. You can, however, use AutoInstall to configure existing networking devices after you remove the configuration file from their NVRAM. The AutoInstall process uses pre-existing configuration files that are stored on a TFTP server.
In this module the term networking device means a router that runs Cisco IOS software. Also, the following terms are used interchangeably:
•
initial configuration and startup configuration
•
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for Using AutoInstall to Remotely Configure a Cisco Networking Device" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
•
•
•
•
•
Prerequisites for Using AutoInstall to Remotely Configure Cisco Networking Devices
•
•
–
–
•
•
•
•
•
Restrictions for Using AutoInstall to Remotely Configure Cisco Networking Devices
•
•
Information About Using AutoInstall to Remotely Configure Cisco Networking Devices
Before you configure or use AutoInstall, you should understand the following information:
•
AutoInstall
AutoInstall can be used to load a final full configuration, or a partial temporary configuration, on to a networking device that is being configured with AutoInstall.
Tip
The requirements for provisioning your network for AutoInstall, and the configuration options for provisioning AutoInstall are explained in these sections:
•
•
•
•
•
•
Services and Servers Used By AutoInstall: Dynamic Assignment of IP Addresses
The network must be able to provide the dynamic assignment of an IP address to the networking device that is being configured with AutoInstall. The type of IP address assignment server that is used depends on the type of connection that the networking that is being configured with AutoInstall has to the network.
AutoInstall uses these types of IP address servers:
DHCP Servers
Networking devices using AutoInstall over a LAN connection require a DHCP server to provide an IP address dynamically. This requirement applies to Ethernet, Token Ring, and FDDI interfaces. The network must be configured to provide IP connectivity between the DHCP server and any devices that are using AutoInstall over LAN connections.
DHCP (defined in RFC 2131) is an extension of the functionality provided by the Bootstrap Protocol (defined in RFC 951). DHCP provides the framework for passing configuration information to hosts on a TCP/IP network. DHCP adds the capability of automatic allocation of reusable network addresses and additional configuration options such as a router (gateway) IP address, a TFTP server IP address, the name of a boot file to load, and the domain name to use. DHCP servers can be configured on routers, UNIX servers, Microsoft Windows-based servers, and other platforms.
DHCP servers typically assign IP addresses from a pool of IP addresses randomly. It is possible for a device that uses DHCP to obtain its IP address to have a different IP address every time it is connected to the network. This creates a problem for the AutoInstall process when you want to ensure that a particular device is assigned a specific hostname during the AutoInstall process. For example, if you are installing routers on different floors in a remote site and each router is supposed to be assigned a name that indicates its location, such as ChicagoHQ-1st and ChicagoHQ-2nd, you need to ensure that each device gets the IP address that will be mapped to its correct hostname.
The process of ensuring that a device is assigned a specific IP address is referred to as creating a reservation. A reservation is a manually configured relationship between an IP address and a physical layer address of a LAN interface on the device. Many Cisco IOS-based devices do not use their MAC address when they request an IP address via DHCP. They use a much longer client identifier instead. Due to the complexity of identifying the client identifier so that you can preconfigure a reservation, and the complexity of finding out if the new device uses its MAC address or the client identifier, we recommend that you allow a new device to obtain an IP address without using a DHCP reservation first in order to discover if the device is using its MAC address or a client identifier. When you have learned how the new device is identifying itself to the DHCP server, you can make a note of the format and create a reservation for it. The next time the new device is rebooted it should obtain the IP address that you reserved to ensure that the new device is assigned the correct hostname. Refer to the information on creating DHCP reservations that was provided with your DHCP server software. The process for creating reservations using Cisco IOS based DHCP servers is explained in the "Using AutoInstall to Set Up Devices Connected to LANs: Example" section. This section includes instructions for identifying the client identifier before the device is connected to the network so that you can preconfigure the DHCP reservations.
Note
Note
For more information on DHCP services visit the IETF RFC site (http://www.ietf.org/rfc.html) and look for RFCs about DHCP. Most server operating systems support DHCP servers. Refer to the documentation that was provided with your operating system for more information.
SLARP Servers
A router that is being configured with AutoInstall over a serial interface using HDLC encapsulation will send a Serial Line ARP (SLARP) request for an IP address over the serial interface that is connected to the staging router.
The serial interface of the staging router must be configured with an IP address in which the host portion is 1 or 2, such as 192.168.10.1 or 192.168.10.2. The staging router will send a SLARP response to the router that is being configured with AutoInstall that contains the value that the staging router is not using. For example, if the interface on the staging router that is connected to the router that is being configured with AutoInstall is using 192.168.10.1 as its IP address, the staging router will send a SLARP response with a value of 192.168.10.2 to the router that is being configured with AutoInstall.
Tip
Figure 2 shows an example of SLARP.
In Figure 1, the IP address of serial interface 0 on the staging router (R2) is 192.168.10.1. SLARP therefore assigns the IP address 192.168.10.2 to serial interface 0 on the new device.
Figure 1 Using SLARP to Assign an IP Address to a New Device
Note
Tip
BOOTP Servers
A router that is being configured with AutoInstall over a serial interface using Frame Relay encapsulation will send a BOOTP request for an IP address over the serial interface that is connected to the staging router.
The staging router learns the correct IP address to provide in its BOOTP response to the router that is being configured with AutoInstall by examining the frame-relay map ip ip-address dlci command that is configured on the interface that it is using to connect to the router that is being configured with AutoInstall.
In Figure 2 R2 is the staging router. R2 has the frame-relay map ip 172.16.27.100 100 broadcast command configured on interface serial 0. When R2 receives the BOOTP request for an IP address from R3 during the AutoInstall process, R3 will reply with 172.16.27.100.
Figure 2 Example of Using BOOTP for Autoinstall Over a Frame Relay Network
Tip
Tip
Note
Services and Servers Used By AutoInstall: IP-to-Hostname Mapping
If you want the networking device to load a full configuration file during the AutoInstall process, the networking device must be able to determine its hostname so that it can request the configuration file that you created specifically for it.
The following caveats apply to the provisioning of IP address to hostname mapping for AutoInstall:
•
•
DNS Servers
DNS servers are used to provide a network service that maps hostnames to IP addresses and IP addresses to hostnames (reverse DNS lookups). Anytime that you use a hostname to initiate an IP connection to a host, your PC must determine the IP address that is assigned to the hostname that you want to contact. For example, when you visit Cisco's website (http://www.cisco.com/) your PC sends a DNS query to a DNS server to discover the current IP address that can be used to contact Cisco's website.
For more information on DNS services visit the IETF RFC site (http://www.ietf.org/rfc.html) and look for RFCs about DNS. The Name Server LookUp tool (nslookup) is very useful for learning more about DNS. There are several excellent websites available about nslookup that you can find by searching for them.
Services and Servers Used By AutoInstall: Storage and Transmission of Configuration Files
TFTP is a protocol used to transfer files between devices on a network. A TFTP server is a device that uses TFTP to transfer files to devices. TFTP servers can be configured on UNIX servers, Microsoft Windows-based PCs and servers, and other platforms.
Tip
Cisco routers use TFTP to load the configuration files that are required for AutoInstall. You must have a TFTP server deployed in your network to provide file storage and file transmission services to the devices that will be using AutoInstall.
For more information on TFTP services visit the IETF RFC site (http://www.ietf.org/rfc.html) and look for RFCs about TFTP. There are several excellent websites available about TFTP that you can find by searching for them. Several freeware and shareware versions of TFTP servers for various operating systems and hardware platforms are available from the Internet.
The following caveats apply to the provisioning of TFTP servers for AutoInstall:
•
•
ip helper-address
If the new device does not learn the IP address of the TFTP server via DHCP option 150, it will transmit the TFTP session initialization requests as network layer broadcasts using the IP destination broadcast address of 255.255.255.255. Routers block network layer broadcast datagrams which prevents the TFTP session initialization requests from reaching the TFTP server, and AutoInstall will fail. The solution to this problem is to use the ip helper-address address command. The ip helper-address address command changes the broadcast address of TFTP session initialization request from 255.255.255.255 to the address that is configured with the address argument. For example, the ip helper-address 172.16.29.252 command will change IP destination broadcast address of 255.255.255.255 to 172.16.29.252.
Networking Devices Used by AutoInstall
These networking devices are used by AutoInstall:
•
•
Device That Is Being Configured with AutoInstall
A device that is being configured with AutoInstall can be any Cisco IOS-based router that supports AutoInstall and does not have a configuration file in its NVRAM.
Staging Router
A staging router acts as an intermediary between the TFTP server (to which it must have IP connectivity) and a device that is being configured with AutoInstall when the new device and the TFTP server are connected to different networks. In Figure 3 R1 requires a staging router because it is connected to a different LAN segment than the TFTP server.
Staging routers are required in the following situations:
•
•
Figure 3 Example of AutoInstall That Requires a Staging Router
Staging routers are not required when the new device that is being configured with AutoInstall is connected to the same LAN segment as the TFTP and DHCP servers. In Figure 4 R2 does not require a staging server to use AutoInstall because it is on the same LAN segment as the TFTP server.
Figure 4 Example of AutoInstall That Does Not Require a Staging Router
Intermediate Frame Relay-ATM Switching Device (Optional)
An intermediate Frame Relay-ATM switching device is one that can perform both routing and switching operations. Frame Relay-ATM switching devices are used to connect Frame Relay and ATM networks.
The AutoInstall over Frame Relay-ATM Interworking Connections feature modifies the AutoInstall process to use Frame Relay encapsulation defined by the IETF standard instead of the Frame Relay encapsulation defined by Cisco.
Figure 5 shows an example topology using AutoInstall over Frame Relay-ATM Interworking Connections. Router R6 does the Frame Relay to ATM Service Internetworking (FRF8) conversion for Frame Relay DLCI 50 to ATM VPI/VCI 5/50. The LS1010 switch routes the VPI/VCI combination used by R6 (5/50) to the VPI/VCI combination used by R4 (6/60).
Figure 5 Example Topology for AutoInstall over Frame Relay-ATM Interworking Connections
Configuration Files Used by AutoInstall
A configuration file executes predefined commands and settings that enable a device to function in a network. The type of configuration file you choose determines many aspects of how you set up the network for AutoInstall.
These types of files are used by AutoInstall:
•
•
Network Configuration File
This is the first file that the AutoInstall process attempts to use. After the device has obtained an IP address it will try to discover its hostname by attempting to download a network configuration file that contains IP address to host name mappings.
If you want the device to learn its hostname from the network-confg file so that it can download a host-specific configuration file, you must add an entry for the device in the network-confg network configuration file. The syntax for the entry is ip host hostname ip-address where hostname is the name that you want the host to use and ip-address is the address that the host will receive from the IP address server. For example, if you want the new device to use the name Australia, and the IP address that was dynamically assigned the new device is 172.16.29.103, you need to create an entry in the network configuration file that contains the ip host australia 172.16.29.103 command.
The file names used for the network configuration file are network-confg or cisconet.cfg. Routers running AutoInstall will try to load the network-confg from the TFTP server first. If the network-confg is not found on the TFTP server, the AutoInstall process will attempt to load the cisconet.cfg file. The cisconet.cfg filename was used by DOS-based TFTP servers that only supported the old 8.3 file naming convention. We recommend that you use the network-confg filename to avoid the delay that is created when AutoInstall has to timeout attempting to load the network-confg before it attempts to load the cisconet.cfg file.
If you using autoinstall to setup multiple devices you can create one network configuration file that contains an entry for each of the devices.
Host-Specific Configuration File
Host-specific configuration files are a full configuration for each new device. If you decide to use host-specific files, you must create a separate file for each new device that you are using AutoInstall to setup.
The filenames used for the host-specific configuration files are name-confg or name.cfg where the word name is replaced by the hostname of the router. For example, the filename for a router named hqrouter is hqrouter-confg or hqrouter.cfg.
Routers running AutoInstall will try to load the host-specific configuration filename using the format name-confg from the TFTP server first. If the name-confg file is not found on the TFTP server, the AutoInstall process will attempt to load the name.cfg file. The name.cfg file name format was used by DOS based TFTP servers that only supported the old 8.3 file naming convention. We recommend that you use the name-confg filename to avoid the delay that is created when AutoInstall has to timeout attempting to load the name-confg before it attempts to load the name.cfg file.
Tip
Tip
Default Configuration File (Optional)
A default configuration file, which includes minimum configuration information allows you to telnet to the new device and configure it manually.
Tip
Figure 6 is an example of using the default configuration file to stage new routers for remote manual configuration. Routers A, B, and C are new routers that will be added to the network one at a time. You connect the first router and wait for it to load the default configuration file. The default configuration file must have enough information in it to allow the new router to communicate with the PC that you will be using to finish its configuration using a Telnet session. After the default configuration file is loaded on the new router, you can use Telnet to connect to the router to complete its configuration. You must assign a new, unique IP address to its interfaces so that the default configuration file can be used for configuring the next router.
Caution
Figure 6 Example of Using the Default Configuration File To Stage Routers For Remote Manual Configuration
Tip
The filenames used for the default network configuration file are router-confg or router.cfg. Routers running AutoInstall will try to load the router-confg from the TFTP server first. If the router-confg is not found on the TFTP server the AutoInstall process will attempt to load the router.cfg file. The router.cfg file name was used by DOS-based TFTP servers that only supported the old 8.3 file naming convention. We recommend that you use the router-confg filename to avoid the delay that is created when AutoInstall has to timeout while attempting to load the router-confg before it attempts to load the router.cfg file.
If you are using AutoInstall to configure LAN-attached devices, you can specify a different default boot filename in DHCP Option 067.
Configuration Options for AutoInstall
You can provision your network to support AutoInstall using several different combinations of devices and services. For example:
•
•
•
•
This module focuses on some of the most common methods for provisioning AutoInstall. Refer to the "How to Use AutoInstall to Remotely Configure Cisco Networking Devices" section for information on the most common methods for provisioning AutoInstall.
The AutoInstall Process
The AutoInstall process begins when a networking device that does not have any files in its NVRAM is connected to the network.
Timesaver
Figure 7 shows the basic flow of the AutoInstall process.
Figure 7 AutoInstall Process Flowchart
Benefits of Using AutoInstall to Remotely Configure a Cisco Networking Device
AutoInstall facilitates the deployment of Cisco routers by allowing you to manage the setup procedure for routers from a central location. The person responsible for physically installing the router does not require specific networking skills. The ability to physically install the router, connect the power and networking cables, and power it on are the only skills required by the installer. The configuration files are stored and managed on a central TFTP server. By using AutoInstall one skilled network technician based at a central site can manage the deployment of several routers in a short period of time.
Two enhancements to AutoInstall:
•
•
AutoInstall Using DHCP for LAN Interfaces
The AutoInstall Using DHCP for LAN Interfaces feature enhances the benefits of AutoInstall by replacing the use of the Bootstrap Protocol (BOOTP) with the use of the Dynamic Host Configuration Protocol (DHCP) for Cisco IOS AutoInstall over LAN interfaces (specifically Ethernet, Token Ring, and FDDI interfaces).
DHCP (defined in RFC 2131) is an extension of the functionality provided by the BOOTP (defined in RFC 951). DHCP provides the framework for passing configuration information to hosts on a TCP/IP network. DHCP adds the capability of automatic allocation of reusable network addresses and additional configuration options. In Cisco IOS Release 12.1(5)T, and later releases, the IP address procurement phase of the AutoInstall process is now accomplished using DHCP for Ethernet, Token Ring, and FDDI interfaces. Prior to this release, IP addresses for LAN interfaces were obtained using BOOTP or RARP during the AutoInstall process. Additionally, this feature allows for the uploading of configuration files using unicast TFTP.
AutoInstall over Frame Relay-ATM Interworking Connections
The AutoInstall over Frame Relay-ATM Interworking Connections feature further enhances the benefits of AutoInstall by allowing you to use a router with an ATM interface as a BOOTP server for new routers being connected at remote locations.
How to Use AutoInstall to Remotely Configure Cisco Networking Devices
This section describes the how to prepare a router for AutoInstall, and how to use AutoInstall with Frame Relay to ATM Service Internetworking. Additional examples for using AutoInstall for new routers connected to LANs, HDLC WANs, and Frame Relay networks that do not use Frame Relay to ATM Service Internetworking, are provided in the "Configuration Examples for Using AutoInstall to Remotely Configure Cisco Networking Devices" section.
In most cases you need to configure a staging router through which a new device running AutoInstall sends TFTP, BOOTP, and DNS requests.
Tip
•
•
Disabling the SDM Default Configuration File
Perform this task if SDM was pre installed on your device and you want to use AutoInstall to configure the device instead. SDM remains on the device.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Step 1
Step 2
Step 3
•
•
•
Step 4
Enter privileged EXEC mode.
enable
Router> enableRouter#Step 5
Erases the existing configuration in NVRAM.
Router# erase startup-configStep 6
Initiates the reload process. The router will initiate the AutoInstall process after it finishes the reload process.
Router# reload
Using AutoInstall with Frame Relay to ATM Service Internetworking
Refer to figure 8 for the sample network used in this task. Perform this task to configure routers R6, R4, and the LS1010 ATM switch so that AutoInstall can be used with Frame Relay to ATM Service Internetworking (FRF8) to setup router R2.
Tip
Figure 8 Example Topology for AutoInstall over Frame Relay/ATM Interworking Connections
This sections contains the following tasks:
•
•
•
•
•
•
Configuring R6 for Frame Relay to ATM Service Internetworking
Router R6 does the Frame Relay to ATM Service Internetworking (FRF8) conversion for Frame Relay DLCI 50 to ATM VPI/VCI 5/50.
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
hostname hostname
Example:Router(config)# hostname R6
In this example, the hostname is configured as R6.
Step 4
interface serial interface-number
Example:R6(config)# interface serial 3/0
Specifies the serial interface that connects to the router that is being setup with AutoInstall.
Step 5
no ip address
Example:R6(config-if)# no ip address
Removes an existing IP address.
Note
Step 6
encapsulation frame-relay ietf
Example:R6(config-if)# encapsulation frame-relay IETF
Enables and specifies the Frame Relay encapsulation method.
Note
Step 7
frame-relay interface-dlci dlci switched
Example:R6(config-if)# frame-relay interface-dlci 50 switched
Specifies that the Frame Relay data-link connection identifier (DLCI) is switched.
Step 8
frame-relay lmi-type ansi
Example:R6(config-if)# frame-relay lmi-type ansi
Specifies that the router should use Annex D defined by American National Standards Institute (ANSI) standard T1.617 as the LMI type.
Step 9
frame-relay intf-type dce
Example:R6(config-if)# frame-relay intf-type dce
Specifies that the router functions as a switch connected to a router.
Step 10
exit
Example:R6(config-if)# exit
Returns to global configuration mode.
Step 11
interface atm interface-number
Example:R6(config)# interface ATM4/0
Species the ATM interface and enters interface configuration mode.
Note
Step 12
no ip address
Example:R6(config-if)# no ip address
Removes an existing IP address.
Note
Step 13
atm pvc number 0 5 qsaal
Example:R6(config-if)# atm pvc 1 0 5 qsaal
Configures a PVC for QSAAL1 signaling.
Step 14
atm pvc number 0 16 ilmi
Example:R6(config-if)# atm pvc 2 0 16 ilmi
Configures a PVC for ILMI signaling.
Step 15
no atm ilmi-keepalive
Example:R6(config-if)# no atm ilmi-keepalive
Disables ATM ILMI keep alives.
Step 16
pvc vpi/vci
Example:R6(config-if)# pvc 5/50
Configures the PVC. When configuring PVCs, configure the lowest available VPI and VCI numbers first.
Note
Step 17
encapsulation aal5mux fr-atm-srv
Example:R6(config-if-atm-vc)# encapsulation aal5mux fr-atm-srv
Enables the Frame Relay and ATM internetworking service.
Step 18
exit
Example:R6(config-if-atm-vc)# exit
Exits PVC configuration mode and returns to interface configuration mode.
Step 19
exit
Example:R6(config-if)# exit
Returns to global configuration mode.
Step 20
connect name serial slot/port dlci atm slot/port vpi/vci service-interworking
Example:R6(config)# connect r2 serial3/0 50 ATM4/0 5/50 service-interworking
Creates the connection between the Frame Relay DLCI and the ATM PVC for the Frame Relay and ATM internetworking service.
Step 21
end
Example:R6(config)# end
Returns to privileged EXEC mode.
Examples
The following example shows how to configure R6 for Frame Relay to ATM Service Internetworking (FRF8).
!hostname R6!interface Serial3/0no ip addressencapsulation frame-relay IETFframe-relay interface-dlci 50 switchedframe-relay lmi-type ansiframe-relay intf-type dce!interface ATM4/0atm pvc 1 0 5 qsaalatm pvc 2 0 16 ilmino atm ilmi-keepalivepvc 5/50encapsulation aal5mux fr-atm-srv!connect r2 serial3/0 50 atm4/0 5/50 service-interworking!Verifying Frame Relay to ATM Service Internetworking on R6
In this example the output of the show connection name r2 command indicates that the Service Interworking Connection is up.
R6# show connection name r2FR/ATM Service Interworking Connection: r2Status - UPSegment 1 - Serial3/0 DLCI 50Segment 2 - ATM4/0 VPI 5 VCI 50Interworking Parameters -service translationefci-bit 0de-bit map-clpclp-bit map-deConfiguring R4 for Frame Relay to ATM Service Internetworking
R4 is one of the endpoints for Frame Relay to ATM Service Internetworking in this task. R2 is the other endpoint. R4 is not directly connected to the Frame Relay network. Therefore R4 requires only the ATM commands to act as the endpoint for Frame Relay to ATM Service Internetworking.
R4 is the core router that connects to the LAN with the TFTP server. R4 is the BOOTP server that will provide the IP address required for R2 (10.10.10.1/24) when R2 runs AutoInstall.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
hostname hostname
Example:Router(config)# hostname R4
In this example the hostname is configured as R4.
Step 4
interface ethernet module/slot/port
Example:R4(config)# interface ethernet 3/0/0
Species the Ethernet interface and enters interface configuration mode.
Step 5
ip address ip-address mask
Example:R4(config-if)# ip address 172.16.29.97 255.255.255.0
Specifies the IP address for the interface.
Step 6
interface atm interface-number
Example:R4(config)# interface atm0/0
Species the ATM interface and enters interface configuration mode.
Note
Step 7
no ip address
Example:R4(config-if)# no ip address
The main ATM interface does not require an IP address in this configuration. The IP address is assigned to the multipoint subinterface in Step 9.
Step 8
atm pvc number 0 5 qsaal
Example:R4(config-if)# atm pvc 1 0 5 qsaal
Configures a PVC for QSAAL1 signaling.
Step 9
atm pvc number 0 16 ilmi
Example:R4(config-if)# atm pvc 2 0 16 ilmi
Configures a PVC for ILMI signaling.
Step 10
no atm ilmi-keepalive
Example:R4(config-if)# no atm ilmi-keepalive
Disables ATM ILMI keep alives.
Step 11
interface atm slot/port.subinterface-number multipoint
Example:R4(config-if)# interface atm0/0.50 multipoint
Creates the ATM multipoint virtual sub-interface and enters sub-interface configuration mode.
Step 12
ip address ip-address mask
Example:R4(config-subif)# ip address 10.10.10.2 255.255.255.0
Specifies the IP address for the sub-interface.
Step 13
ip helper-address ip-address
Example:R4(config-subif)# ip helper-address 172.16.29.252
Specifies the IP address of the TFTP server. This IP address is used to replace the 255.255.255.255 IP destination broadcast address that R2 will use when it attempts to establish a connection to the TFTP server.
Step 14
pvc vpi/vci
Example:R4(config-if-atm-vc)# pvc 6/60
Configures the PVC. When configuring PVCs, configure the lowest available VPI and VCI numbers first.
Note
Step 15
protocol ip ip-address broadcast
Example:R4(config-if-atm-vc)# protocol ip 10.10.10.1 broadcast
Specifies the IP address of the device at the other end of this PVC. In this example the device is R2.
For this example this is the IP address that will be assigned by the BOOTP server on R4 to R2 during the AutoInstall process.
Step 16
end
Example:R4(config-if-atm-vc)# end
Returns to privileged EXEC mode.
Examples
The following example configures R4 as the core router for AutoInstall using Frame Relay to ATM Service Internetworking (FRF8).
!hostname R4!interface FastEthernet3/0/0ip address 172.16.29.97 255.255.255.0!interface ATM0/0no ip addressatm pvc 1 0 5 qsaalatm pvc 2 0 16 ilmino atm ilmi-keepalive!interface ATM0/0.50 multipointip address 10.10.10.2 255.255.255.0ip helper-address 172.16.29.252pvc 6/60protocol ip 10.10.10.1 broadcast!!Configuring IP Routing R4
In order for R4 to be able to forward IP traffic between network 172.16.29.0 and R2 after the AutoInstall process is complete, R4 needs to have IP routing configured.
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Examples
The following example shows how to configure IP routing on R4.
!router ripversion 2network 10.0.0.0network 172.16.0.0no auto-summary!Configuring the LS1010 Switch
This task describes how to configure an LS1010 switch to route the PVCs between R6 and R4. R6 is connected to ATM 3/1/1 on the LS1010 switch. R4 is connected to ATM 3/1/2 on the LS1010 switch.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Step 1
enable
Example:Switch> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Switch# configure terminal
Enters global configuration mode.
Step 3
interface atm module/slot/port
Example:Switch(config)# interface ATM3/1/2
Species the ATM interface and enters interface configuration mode.
Note
Step 4
atm pvc vpi vci interface atm interface-number vpi vci
Example:Switch(config-if)# atm pvc 6 60 interface ATM3/1/1 5 50
Configures a static PVC route
In this example a route for the PVC from R6 (5/50) to R4 (6/60) is configured.
Step 5
end
Example:Switch(config-if)# end
Returns to privileged EXEC mode.
Examples
The following example shows how to configure the LS1010 ATM switch to route the PVCs between R6 and R4.
!atm address 47.0091.8100.0000.0010.11b9.6101.0010.11b9.6101.00atm router pnnino aesa embedded-number left-justifiednode 1 level 56 lowestredistribute atm-static!interface ATM2/0/0no ip addressno ip directed-broadcastatm maxvp-number 0!interface ATM3/1/0no ip addressno ip directed-broadcastno atm ilmi-keepalive!interface ATM3/1/1no ip addressno ip directed-broadcastno atm ilmi-keepalive!interface ATM3/1/2no ip addressno ip directed-broadcastno atm ilmi-keepaliveatm pvc 6 60 interface ATM3/1/1 5 50!interface ATM3/1/3no ip addressno ip directed-broadcastno atm ilmi-keepalive!Creating the Configuration File for R2
This section provides the content for the configuration file for R2.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Step 1
!hostname R2!!enable secret 7gD2A0!interface Ethernet0no ip addressshutdown!interface Serial0ip address 10.10.10.1 255.255.255.0encapsulation frame-relay IETFframe-relay map ip 10.10.10.2 50 broadcastframe-relay interface-dlci 50frame-relay lmi-type ansi!interface Serial1no ip addressshutdown!!router ripversion 2network 10.0.0.0no auto-summary!ip http serverip classless!line vty 0 4password 87F3c0mlogin!endStep 2
Verifying AutoInstall with Frame Relay to ATM Service Internetworking
This task verifies the AutoInstall with Frame Relay to ATM Service Internetworking configuration by setting up R2, as shown in Figure 8, using AutoInstall.
Prerequisites
The following prerequisites must be met before you can perform this task:
•
•
•
•
•
Step 1
Use Hyperterminal or a similar terminal emulation program on your PC, with the following terminal emulation settings, to connect to the device:
•
•
•
Step 2
Step 3
Would you like to enter the initial configuration dialog? [yes/no]: noStep 4
Would you like to terminate autoinstall? [yes]: noAutoInstall will start.
Please Wait. Autoinstall being attempted over Serial0 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Step 5
This display output is from a successful Auto Installation process.
Note
Note
Press RETURN to get started!*Mar 1 00:00:11.155: %LINK-3-UPDOWN: Interface Ethernet0, changed state to up*Mar 1 00:00:11.159: %LINK-3-UPDOWN: Interface Serial0, changed state to up*Mar 1 00:00:11.527: %LINK-3-UPDOWN: Interface Serial1, changed state to down*Mar 1 00:00:12.271: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0,changed state to up*Mar 1 00:00:29.487: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0, changed state to down*Mar 1 00:00:32.347: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up*Mar 1 00:00:40.355: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to down*Mar 1 00:00:45.551: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up*Mar 1 00:01:58.499: %IP-5-WEBINST_KILL: Terminating DNS process*Mar 1 00:02:00.035: %LINK-5-CHANGED: Interface Ethernet0, changed state to administratively down*Mar 1 00:02:00.039: %LINK-5-CHANGED: Interface Serial1, changed state to administratively down*Mar 1 00:02:01.039: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down*Mar 1 00:02:50.635: %SYS-5-RESTART: System restarted --Cisco Internetwork Operating System SoftwareIOS (tm) 2500 Software (C2500-IS-L), Version 12.3(13a), RELEASE SOFTWARE (fc2)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2005 by cisco Systems, Inc.Compiled Tue 26-Apr-05 12:52 by ssearch*Mar 1 00:02:50.643: %SNMP-5-COLDSTART: SNMP agent on host Router is undergoinga cold start*Mar 1 00:03:54.759: %PARSER-4-BADCFG: Unexpected end of configuration file.*Mar 1 00:03:54.763: %SYS-5-CONFIG_I: Configured from tftp://172.16.29.252/network-confg by console*Mar 1 00:04:12.747: %SYS-5-CONFIG_I: Configured from tftp://172.16.29.252/r2-confg by consoleIf you have logging enabled on your TFTP server the log should contain messages similar to the following text:
Sent network-confg to (10.10.10.1), 76 bytesSent r2-confg to (10.10.10.1),687 bytesStep 6
Troubleshooting
If after approximately five minutes you do not see the %SYS-5-CONFIG_I messages and R2 has a factory default prompt of Router>, the AutoInstall process failed.
Step 1
Tip
Step 2
After you have copied the configuration to R2, try to ping 10.10.10.2. If this fails, you have a problem between R2 and R4. Verify the cabling, the status of the interfaces, and the configurations on the routers.
If R2 can ping 10.10.10.2, try pinging the TFTP server (172.16.29.252) from R2. If this fails, you have a configuration problem somewhere between R4 and the TFTP server. Verify the cabling, the status of the interfaces, and the configurations on the routers. Verify the IP address and IP default gateway on the TFTP server.
Tip
If R2 can ping the TFTP server (172.16.29.252), you probably have a problem with the TFTP server itself. A common mistake with TFTP servers is that they are configured to receive files but not to send them. Another common mistake on UNIX-based TFTP servers is that the files do not have the correct permissions. On a UNIX TFTP server the files should have permissions set to rw-rw-rw.
Step 3
Configuration Examples for Using AutoInstall to Remotely Configure Cisco Networking Devices
This section provides the following configuration examples:
•
•
Using AutoInstall to Set Up Devices Connected to LANs: Example
This task uses the network in Figure 9. This task will show how to use AutoInstall to setup routers R2, R3, and R4. Router R1 is the DHCP server that will be used to assign the IP address for Ethernet 0 on the new routers during the AutoInstall process.
Figure 9 Network Topology for Assigning AutoInstall Configuration Files For Specific Devices
Every DHCP client has a unique DHCP client identifier. The DHCP client identifier is used by DHCP servers to keep track of IP address leases and for configuring IP address reservations. You need to know the DHCP client identifier for each of the networking devices that you want to configure with AutoInstall so that you can configure the DHCP IP address reservations which will ensure that each device is provided with the correct IP address, and subsequently its unique configuration file. You can determine the DHCP client identifier manually or automatically.
To use AutoInstall to setup routers R2, R3, and R4, perform following tasks:
•
•
•
•
•
•
•
•
Determining the Value for the DHCP Client Identifier Manually
If you want to determine the value for the client identifiers automatically, you do not need to perform this task. Proceed to the "Determining the Value for the DHCP Client Identifier Automatically" section.
Tip
You must know the MAC address of the Ethernet interface that will be used to connect the router to the LAN during the AutoInstall process to determine the client identifier manually. This requires connecting a terminal to the router, and powering it on, so that you can enter the show interface interface-type interface-number command.
The client-identifier looks like this:
0063.6973.636f.2d30.3030.362e.3533.6237.2e38.6537.312d.4661.332f.30
The format is nullcisco-0006.53b7.8e71-fa3/0 where 0006.53b7.8e71 is the MAC address and fa3/0 is the short interface name for the interface that the IP address request is made for.
The values for the short-if-name field can be obtained from an SNMP workstation with the Cisco MIBs installed. This is an example of how to map ifIndex to an interface on Cisco IOS:
snmpwalk -c public ponch ifNameIF-MIB::ifName.1 = STRING: AT2/0IF-MIB::ifName.2 = STRING: Et0/0IF-MIB::ifName.3 = STRING: Se0/0IF-MIB::ifName.4 = STRING: BR0/0Use the show interface interface-type interface-number command to display the information and statistics for a FastEthernet interface.
R6> show interface fastethernet 3/0FastEthernet3/0 is up, line protocol is upHardware is AmdFE, address is 0006.53b7.8e71 (bia 0006.53b7.8e71)...R6>The MAC address for FastEthernet 3/0 on R6 is 0006.53b7.8e71. The format of the client identifier for this interface is nullcisco-0006.53b7.8e71-fa3/0.
Note
Table 1 shows the values for converting characters to their hexadecimal equivalents. The last row in Table 2 shows the client identifier for FastEthernet 3/0 on R6 (nullcisco-0006.53b7.8e71-fa3/0).
R4
Use the show interface interface-type interface-number command to display the information and statistics for Ethernet 0 on R4.
R4> show interface ethernet 0Ethernet0 is up, line protocol is upHardware is Lance, address is 00e0.1eb8.eb0e (bia 00e0.1eb8.eb0e)The MAC address for Ethernet 0 on R4 is 00e0.1eb8.eb0e. The format of the client identifier for this interface is nullcisco-00e0.1eb8.eb0e-et0.
Note
Using the values for converting characters to their hexadecimal equivalents in Table 1, the client identifier for Ethernet 0 on R4 is shown in the last row of Table 3.
R3
Use the show interface interface-type interface-number command to display the information and statistics for Ethernet 0 on R3.
R3> show interface ethernet 0Ethernet0 is up, line protocol is upHardware is Lance, address is 00e0.1eb8.eb73 (bia 00e0.1eb8.eb73)The MAC address for Ethernet 0 on R3 is 00e0.1eb8.eb73. The format of the client identifier for this interface is: nullcisco-00e0.1eb8.eb73-et0.
Using the values for converting characters to their hexadecimal equivalents in Table 1, the client identifier for Ethernet 0 on R3 is shown in the last row of Table 4.
R2
Use the show interface interface-type interface-number command to display the information and statistics for Ethernet 0 on R2.
R2> show interface ethernet 0Ethernet0 is up, line protocol is upHardware is Lance, address is 00e0.1eb8.eb09 (bia 00e0.1eb8.eb09)The MAC address for Ethernet 0 on R2 is 00e0.1eb8.eb09. The format of the client identifier for this interface is nullcisco-00e0.1eb8.eb09-et0.
Using the values for converting characters to their hexadecimal equivalents in Table 1, the client identifier for Ethernet 0 on R2 is shown in the last row of Table 5
You have now determined the values for the client identifiers on each router. The final step is to add a period after each group of four characters working from the left to the right as shown below:
•
•
•
What to Do Next
Save the values in a text file and proceed to the "Creating a Private DHCP Pool for Each of The Routers" section.
Determining the Value for the DHCP Client Identifier Automatically
If you determined the value for the client identifiers manually, you do not need to perform this task. Proceed to the "Creating a Private DHCP Pool for Each of The Routers" section.
This task will create a DHCP server on R1 that will provide only one IP address. This IP address will used by each new router in sequence while you determine the value of the router's client identifier. By limiting the IP address scope to a single IP address you avoid any possible confusion about which router you are working on. If somebody powers up another router that attempts to start the AutoInstall process, it will not be able to obtain an IP address.
Tip
This task is broken down into sub-tasks to make it easier to follow (all sub-tasks are required):
•
•
•
•
•
•
•
•
•
Configuring IP on the Interfaces on R1
Configure IP addresses on the Ethernet interfaces. Configure the ip helper-address ip-address command on Ethernet 0/1.
!interface Ethernet0/0ip address 172.16.29.99 255.255.255.0!interface Ethernet0/1ip address 172.16.28.99 255.255.255.0ip helper-address 172.16.29.252!Configuring a DHCP Pool on R1
Configure these commands to setup the temporary DHCP server on R1.
Note
!ip dhcp pool get-client-idnetwork 172.16.28.0 255.255.255.0!Excluding All But One of the IP Addresses from the DHCP Pool on R1
You need to ensure that there is only one IP address available from the DHCP server at any time. Configure the following command to exclude every IP address except 172.16.28.1 from the DHCP pool.
!ip dhcp excluded-address 172.16.28.2 172.16.28.255!Verifying The Configuration on R1
Verify that the configuration file for R1 has a DHCP server pool configured to provide a single IP address (172.16.28.1) to a DHCP client.
Verify that the configuration file has the IP addresses for the Ethernet interfaces and the ip helper-address ip-address command.
!ip dhcp excluded-address 172.16.28.2 172.16.28.255!ip dhcp pool get-client-idnetwork 172.16.28.0 255.255.255.0!interface Ethernet0/0ip address 172.16.29.99 255.255.255.0!interface Ethernet0/1ip address 172.16.28.99 255.255.255.0ip helper-address 172.16.29.252!Enabling debug ip dhcp server events on R1
You use the display output from the debug ip dhcp server events command on the terminal connected to R1 to identify the value of the client identifier for each router.
Enable the debug ip dhcp server events command on R1.
R1# debug ip dhcp server eventsIdentifying the Value for the Client Identifier on Each of the Routers
This step is repeated for each of the routers. You should only have one of the routers powered-on at any time. When you have identified the value of the client identifier field for the router, you will turn the router off and proceed to the next router.
R4
Connect R4 to the Ethernet network and power it on. The following message will be displayed on the terminal connected to R1 when R4 is assigned the IP address 172.16.28.1.
DHCPD: assigned IP address 172.16.28.1 to client 0063.6973.636f.2d30.3065.302e.3165.6238.2e65.6230.652d.4574.30.Copy the client identifier 0063.6973.636f.2d30.3065.302e.3165.6238.2e65.6230.652d.4574.30 to a text file and save it. Keep the text file open for the next two routers.
Turn off R4
Release the IP address binding for R4 from the DHCP pool on R1 using the clear ip dhcp binding * command on R1.
R1# clear ip dhcp binding *R1#01:16:11: DHCPD: returned 172.16.28.1 to address pool get-client-id.R3
Connect R3 to the Ethernet network and power it on. The following message will be displayed on the terminal connected to R1 when R3 is assigned the IP address 172.16.28.1.
DHCPD: assigned IP address 172.16.28.1 to client 0063.6973.636f.2d30.3065.302e.3165.6238.2e65.6237.332d.4574.30.Copy the client identifier 0063.6973.636f.2d30.3065.302e.3165.6238.2e65.6237.332d.4574.30 to the text file and save it. Keep the text file open for the final router.
Turn off R3.
Release the IP address binding for R3 from the DHCP pool on R1 using the clear ip dhcp binding * command on R1.
R1# clear ip dhcp binding *R1#01:16:11: DHCPD: returned 172.16.28.1 to address pool get-client-id.R2
Connect R2 to the Ethernet network and power it on. The following message will be displayed on the terminal connected to R1 when R2 is assigned the IP address 172.16.28.1.
DHCPD: assigned IP address 172.16.28.1 to client 0063.6973.636f.2d30.3065.302e.3165.6238.2e65.6230.392d.4574.30.Copy the client identifier 0063.6973.636f.2d30.3065.302e.3165.6238.2e65.6230.392d.4574.30 to the text file and save it.
Turn off R2
Release the IP address binding for R2 from the DHCP pool on R1 using the clear ip dhcp binding * command on R1.
R1# clear ip dhcp binding *R1#01:16:11: DHCPD: returned 172.16.28.1 to address pool get-client-id.Client Identifiers for R4, R3, and R2
You have determined the values for the client identifiers on each router.
•
•
•
Removing the DHCP Pool on R1 for Network 172.16.28.0/24
The temporary DHCP pool on the router is no longer required, and must be removed.
R1(config)# no ip dhcp pool get-client-idRemoving the Excluded Address Range From R1
The command for excluding all of the IP addresses except 172.16.28.1 from the DHCP pool on the router is no longer required, and must be removed.
R1(config)# no ip dhcp excluded-address 172.16.28.2 172.16.28.255
Creating a Private DHCP Pool for Each of The Routers
You need to create the private DHCP address pools for each router to ensure that each router is assigned the IP address that maps to its host name in the network-conf file.
!ip dhcp pool r4host 172.16.28.100 255.255.255.0client-identifier 0063.6973.636f.2d30.3065.302e.3165.6238.2e65.6230.652d.4574.30!ip dhcp pool r3host 172.16.28.101 255.255.255.0client-identifier 0063.6973.636f.2d30.3065.302e.3165.6238.2e65.6237.332d.4574.30!ip dhcp pool r2host 172.16.28.102 255.255.255.0client-identifier 0063.6973.636f.2d30.3065.302e.3165.6238.2e65.6230.392d.4574.30Creating Configuration Files for Each Router
Create the configuration files for each router and place them in the root directory of the TFTP server.
Tip
r2-confg
!hostname R2!enable secret 7gD2A0!interface Ethernet0ip address 172.16.28.102 255.255.255.0!interface Serial0ip address 192.168.100.1 255.255.255.252no shutdown!interface Serial1ip address 192.168.100.5 255.255.255.252no shutdown!no ip http serverip classlessip default-network 0.0.0.0ip route 0.0.0.0 0.0.0.0 Ethernet0!line vty 0 4password 5Rf1k9login!endr3-confg
!hostname R3!enable secret 7gD2A0!interface Ethernet0ip address 172.16.28.101 255.255.255.0!interface Serial0ip address 192.168.100.9 255.255.255.252no shutdown!interface Serial1ip address 192.168.100.13 255.255.255.252no shutdown!no ip http serverip classlessip default-network 0.0.0.0ip route 0.0.0.0 0.0.0.0 Ethernet0!line vty 0 4password 5Rf1k9login!endr4-confg
!hostname R3!enable secret 7gD2A0!interface Ethernet0ip address 172.16.28.101 255.255.255.0!interface Serial0ip address 192.168.100.9 255.255.255.252no shutdown!interface Serial1ip address 192.168.100.13 255.255.255.252no shutdown!no ip http serverip classlessip default-network 0.0.0.0ip route 0.0.0.0 0.0.0.0 Ethernet0!line vty 0 4password 5Rf1k9login!endCreating the network-confg file
Create the network-confg file with the ip host hostname ip-address commands that map the IP addresses that you will be assigning with the DHCP server to the hostname.
ip host r4 172.16.28.100ip host r3 172.16.28.101ip host r2 172.16.28.102Setting Up the Routers with AutoInstall
You are now ready to set up the three routers (R4, R3, and R2) using AutoInstall.
Connect a terminal to the routers if you want to monitor the progress of AutoInstall. Use Hyperterminal or a similar terminal emulation program on your PC, with the following terminal emulation settings, to connect to the device:
•
•
•
You should have the following files in the root directory of the TFTP server.
•
•
•
•
The TFTP server must be running.
Power on each router.
Timesaver
R4
The following is an excerpt of the messages that are displayed on R4's console terminal during the AutoInstall process:
Loading network-confg from 172.16.29.252 (via Ethernet0): ![OK - 76 bytes]Configuration mapped ip address 172.16.28.100 to r4Loading r4-confg from 172.16.29.252 (via Ethernet0): ![OK - 687 bytes]R3
The following is an excerpt of the messages that are displayed on R3's console terminal during the AutoInstall process:
Loading network-confg from 172.16.29.252 (via Ethernet0): ![OK - 76 bytes]Configuration mapped ip address 172.16.28.101 to r3Loading r3-confg from 172.16.29.252 (via Ethernet0): ![OK - 687 bytes]R2
The following is an excerpt of the messages that are displayed on R2's console terminal during the AutoInstall process:
Loading network-confg from 172.16.29.252 (via Ethernet0): ![OK - 76 bytes]Configuration mapped ip address 172.16.28.102 to r2Loading r2-confg from 172.16.29.252 (via Ethernet0): ![OK - 687 bytes]TFTP Server Log
The TFTP server log should contain messages similar to the following text.
Sent network-confg to (172.16.28.100), 76 bytesSent r4-confg to (172.16.28.100),687 bytesSent network-confg to (172.16.28.101), 76 bytesSent r3-confg to (172.16.28.101),687 bytesSent network-confg to (172.16.28.102), 76 bytesSent r2-confg to (172.16.28.102),687 bytesSaving the Configuration Files on The Routers
You must save the running configurations on each router to the startup configuration to ensure that the routers retain their configurations if they are ever power cycled.
R4
R1# telnet 172.16.28.100Trying 172.16.28.100 ... OpenUser Access VerificationPassword:R4> enablePassword:R4# copy running-config startup-configDestination filename [startup-config]?Building configuration...[OK]R4# exit[Connection to 172.16.28.100 closed by foreign host]R1#R3
R1# telnet 172.16.28.101Trying 172.16.28.101 ... OpenUser Access VerificationPassword:R3> enablePassword:R3# copy running-config startup-configDestination filename [startup-config]?Building configuration...[OK]R3# exit[Connection to 172.16.28.101 closed by foreign host]R1#R2
R1# telnet 172.16.28.102Trying 172.16.28.102 ... OpenUser Access VerificationPassword:R2> enablePassword:R2# copy running-config startup-configDestination filename [startup-config]?Building configuration...[OK]R2# exit[Connection to 172.16.28.102 closed by foreign host]R1#Removing the Private DHCP Address Pools from R1
The final step in the AutoInstall process is to remove the private DHCP address pools from R1.
R1(config)# no ip dhcp pool r4R1(config)# no ip dhcp pool r3R1(config)# no ip dhcp pool r2This is the final task, and step for Using AutoInstall to Setup Devices Connected to LANs.
Using AutoInstall to Set Up Devices Connected to WANs: Example
This section contains the following examples:
HDLC WAN Connections
This section uses the network in Figure 10. The section shows how to use AutoInstall to setup R4. R2 will use SLARP to provide R4 the IP address (192.168.20.2) required for AutoInstall.
Figure 10 Network Topology Using AutoInstall to Configure Routers Connected to HDLC WANs
The process for using AutoInstall to set up router R2 requires the following tasks:
•
•
•
•
Creating the Configuration for R4
Create the configuration file for R4 and save it on the TFTP server as r4-confg:
!hostname R4!enable secret 7gD2A0!interface Ethernet0ip address 10.89.45.1 255.255.255.0no shutdown!interface Serial0ip address 192.168.10.2 255.255.255.0no fair-queue!router ripversion 2network 168.192.0.0no auto-summary!ip http serverip classlessip default-network 0.0.0.0ip route 0.0.0.0 0.0.0.0 Serial0!line vty 0 4password 6T2daX9!endCreating the network-confg File
Create the network configuration file for R4 and save it on the TFTP server as network-confg:
ip host r4 192.168.10.2Configuring R1 and R2
Configure R1 and R2 using the following configurations:
R1
!hostname R1!enable secret 7gD2A0!interface Ethernet0/0ip address 172.16.29.99 255.255.255.0!interface Ethernet0/1ip address 172.16.28.99 255.255.255.0ip helper-address 172.16.29.252!router ripversion 2network 172.16.0.0no auto-summary!ip classlessip http server!line vty 0 4password 67F2SaB!endR2
!hostname R2!enable secret 7gD2A0!interface Ethernet0ip address 172.16.28.98 255.255.255.0!interface Serial1ip address 192.168.10.1 255.255.255.0clockrate 64000!router ripversion 2network 172.16.0.0network 192.168.10.0no auto-summary!ip http serverip classless!line vty 0 4password u58Hg1!endSetting Up R4 using AutoInstall
The network is now ready to use AutoInstall to setup R4. perform the following steps to setup R4.
Connect R4 to the HDLC WAN network.
Power R4 on.
The AutoInstall process should be complete in approximately 5 minutes.
TFTP Server Log
The TFTP server log should contain messages similar to the following text:
Sent network-confg to (192.168.10.2), 76 bytesSent r4-confg to (192.168.10.2),687 bytesSave the Configuration File on R4
You must save the running configurations on R4 to the startup configuration to ensure that R4 retains its configuration if it is ever power cycled.
R1# telnet 192.168.10.2Trying 192.168.10.2 ... OpenUser Access VerificationPassword:R4> enablePassword:R4# copy running-config startup-configDestination filename [startup-config]?Building configuration...[OK]R4# exit[Connection to 192.168.10.2 closed by foreign host]R1#Frame-Relay WAN Connections
This section uses the network in Figure 11. The section shows how to use AutoInstall to setup R4. R2 will use BOOTP to provide R4 the IP address (172.16.27.100) required for AutoInstall.
R2 uses 172.16.27.100 as the IP address to provide to R3 using BOOTP because this is the IP address in the frame-relay map ip 172.16.27.100 100 broadcast command on serial 0 that points to serial 0 on R3.
Figure 11 Network Topology for Using AutoInstall to Configure Routers Connected to Frame Relay WANs
The process for using AutoInstall to set up router R3 requires the following tasks:
•
•
•
•
Creating the Configuration for R3
Create the configuration file for R4 and save it on the TFTP server as r3-confg:
!hostname R3!enable secret 8Hg5Zc20!interface Ethernet0no ip addressshutdown!interface Serial0ip address 172.16.27.100 255.255.255.0encapsulation frame-relay IETFno fair-queueframe-relay map ip 172.16.27.99 101 broadcastframe-relay interface-dlci 101!interface Serial1no ip addressshutdown!router ripversion 2network 172.16.0.0no auto-summary!line vty 0 4password 67Td3alogin!endCreating the network-confg File
Create the network configuration file for R3 and save in on the TFTP server as network-confg:
ip host r3 172.16.27.100Configuring R1 and R2
Configure R1 and R2 using the following configurations:
R1
!hostname R1!enable secret 86vC7Z!interface Ethernet0/0ip address 172.16.29.99 255.255.255.0!interface Ethernet0/1ip address 172.16.28.99 255.255.255.0!router ripversion 2network 172.16.0.0no auto-summary!line vty 0 4password 6Gu8z0s!!endR2
!hostname R2!enable secret 67Hfc5z2!interface Ethernet0ip address 172.16.28.98 255.255.255.0ip helper-address 172.16.29.252!interface Serial0ip address 172.16.27.99 255.255.255.0ip helper-address 172.16.29.252encapsulation frame-relay IETFno fair-queueframe-relay map ip 172.16.27.100 100 broadcastframe-relay interface-dlci 100!interface Serial1no ip address!router ripversion 2network 172.16.0.0no auto-summary!line vty 0 4password 9Jb6Z3g!endSetting Up R3 using AutoInstall
The network is now ready to use AutoInstall to set up R3. perform the following steps to setup R4.
Connect R3 to the Frame Relay network.
Power R3 on.
The AutoInstall process should be complete in approximately 5 minutes.
TFTP Server Log
The TFTP server log should contain messages similar to the following text:
Sent network-confg to (172.16.27.100), 76 bytesSent r3-confg to (172.16.27.100),687 bytesSaving the Configuration File on R3
You must save the running configurations on R3 to the startup configuration to ensure that R3 retains its configuration if it is ever power cycled.
R1# telnet 172.16.27.100Trying 172.16.27.100 ... OpenUser Access VerificationPassword:R3> enablePassword:R3# copy running-config startup-configDestination filename [startup-config]?Building configuration...[OK]R4# exit[Connection to 192.168.10.2 closed by foreign host]R1#Additional References
The following sections provide references related to Using AutoInstall to Remotely Configure Cisco Networking Devices.
Related Documents
Frame Relay-to-ATM Service Interworking (FRF.8)
Frame Relay-ATM Interworking Supported Standards
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fwan_c/wcfapdx/wcfappa.htm
Configuring Frame Relay-ATM Interworking
/en/US/docs/ios/12_2/wan/configuration/guide/wcffratm_external_docbase_0900e4b1807540c4_4container_external_docbase_0900e4b180754467.html#15605
Overview of Cisco IOS Setup Mode and AutoInstall for configuring Cisco networking devices
Using Setup Mode to Configure a Cisco Networking Device
MIBs
RFCs
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature
—
Technical Assistance
Feature Information for Using AutoInstall to Remotely Configure a Cisco Networking Device
Table 6 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.2(1) or 12.0(3)S or a later release appear in the table.
Not all commands may be available in your Cisco IOS software release. For details on when support for a specific command was introduced, see the command reference documentation.
Cisco IOS software images are specific to a Cisco IOS software release, a feature set, and a platform. Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Note
Table 6 Feature Information for Using AutoInstall to Remotely Set Up a Cisco Networking Device
AutoInstall over Frame Relay-ATM Interworking Connections
12.2(4)T
The AutoInstall over Frame Relay-ATM Interworking Connections feature extends the functionality of the existing Cisco IOS AutoInstall feature. While AutoInstall over Frame Relay encapsulated serial interfaces has long been supported, this feature provides the same functionality when the central (existing) router has an ATM interface instead of a Frame Relay interface.
The following sections provide information about this feature:
•
•
No new or modified commands are introduced with this feature. All commands used with this feature are documented in the Cisco IOS Configuration Fundamentals Command Reference.
AutoInstall Using DHCP for LAN Interfaces
12.1(5)T
12.2(33)SRCThe AutoInstall Using DHCP for LAN Interfaces feature enhances the benefits of AutoInstall by replacing the use of the Bootstrap Protocol (BOOTP) with the use of the Dynamic Host Configuration Protocol (DHCP) for Cisco IOS AutoInstall over LAN interfaces (specifically Ethernet, Token Ring, and FDDI interfaces).
The following section provides information about this feature:
•
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.
