Cisco router would you like to terminate autoinstall

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. Failure to change the IP addresses in the router that you are configuring remotely with Telnet will result in duplicate IP addresses on the LAN when the next router loads the default configuration file.

In this situation you will not be able to use Telnet to connect to either router. You must disconnect one of the routers before you can resolve this problem. You must include the commands for configuring passwords for remote Telnet access and access to privileged EXEC mode if you are going to access the routers remotely to complete their configurations save their configuration files to NVRAM.

The filenames used for the default network configuration file are router-confg or router. The router. 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. Instead of downloading configuration files, you can choose to provision your own Tool Command Language TCL installation script to complete the AutoInstall process.

Your TCL script may retrieve a configuration file or an image from a file server and reload it on the device.

You can provision your network to support AutoInstall using several different combinations of devices and services. For example:. The TCL script provides a flexible way to complete the installation of the device, allowing you to complete the configuration by programming the script.

This module focuses on some of the most common methods for provisioning AutoInstall. You can decrease the time that the AutoInstall process takes to complete by only connecting the interface on the networking device that you want to use for AutoInstall until the AutoInstall process has finished. The following figure shows the basic flow of the AutoInstall process using the configuration files. 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.

DHCP adds the capability of automatic allocation of reusable network addresses and additional configuration options. Additionally, this feature allows for the uploading of configuration files using unicast TFTP. This feature enables you to program the device to get information about what to download, to choose the type of file server, and to choose the required file transfer protocol.

Instead of allowing the DHCP server to return the image and the configuration file and downloaded from a file server, you have the flexibility to place the information about image and configuration file location under the control of an external server. This flexibility allows the device itself to retrieve this information from the external server during the installation process.

This feature allows you to download a Tool Command Language TCL script instead of the configuration file and to use the script to make the device operational. The script can consult a third-party server for information before downloading the image, configuration file, and other required files. The script location must be provisioned in the DHCP server, along with the other usual options, such as network and host-specific configuration files, needed in an AutoInstall setup.

If you choose script-based deployment, you can program and execute the installation process on the device itself instead of having the installation process driven by a centralized server. The script uses the available FTPs to communicate with the configuration server, and these protocols are supported by the platform system code. Script commands that are required to perform script tasks should be supported by the platform code system.

The script-based deployment is triggered when there is no startup configuration in NVRAM upon powering up. In all cases, you must verify and save the configuration on the networking device after the AutoInstall process is complete.

If you do not save the configuration, you must repeat the entire process. SDM remains on the device. Connect the console cable, shipped with your device, from the console port on the device to a serial port on your PC.

Refer to the hardware installation guide for the device for instructions. Connect the power supply to the device, plug the power supply into a power outlet, and turn on the device.

Refer to the quick start guide for the device for instructions. Use Hyperterminal or a similar terminal emulation program on your PC, with the following terminal emulation settings, to connect to the device:.

Initiates the reload process. The device will initiate the AutoInstall process after it finishes the reload process. Refer to the figure below for the sample network used in this task. The IP address that will be assigned to Serial 0 on R2 Specifies the serial interface that connects to the device that is being set up with AutoInstall and enters interface configuration mode. This interface is used as a layer 2 switch interface in this configuration.

It is not an IP layer 3 endpoint. Therefore it does not require an IP address. Only the Frame Relay commands and keywords required for this task are described in this task. Only the ATM commands and keywords required for this task are described in this task. Configures the PVC. Use the show connection name r2 command to verify whether the Service Interworking Connection is up. The output of the show connection name r2 command indicates that the Service Interworking Connection is up.

R2 is the other endpoint. R4 is not directly connected to the Frame Relay network. The IP address is assigned to the multipoint subinterface in Step 9. Creates the ATM multipoint virtual subinterface and enters subinterface configuration mode.

This IP address is used to replace the In this example the device is R2. In order for R4 to be able to forward IP traffic between network Only the RIP commands and keywords required for this task are described in this task.

Enter your password if prompted. Species the ATM interface and enters interface configuration mode. You must have a network configuration named network-confg file with the ip host r2 The AutoInstall process can take several minutes to complete. This problem does not adversely affect the AutoInstall process. If you have logging enabled on your TFTP server the log should contain messages similar to the following text:. Copy the running configuration to the startup configuration with the copy running-config startup-config command.

Look for error messages on the TFTP server indicating that the files were not found. A very common mistake is that the. Your operating system might be hiding the extension for known file types when you browse the TFTP root directory. Disable the Hide file extensions for known file types option. Test the connectivity in your network by configuring R2 with the configuration file that you created.

You can copy the configuration for R2 to R2 by pasting it into the console terminal session. After you have copied the configuration to R2, try to ping 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 A common mistake with TFTP servers is that they are configured to receive files but not to send them. If the IP connectivity appears to be working and the TFTP server is configured correctly, verify that you entered the ip helper-address ip-address command on R4 correctly.

This task uses the network in the figure below. 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. If you want to determine the value for the client identifiers automatically, you do not need to perform this task.

You must know the MAC address of the Ethernet interface that will be used to connect the device to the LAN during the AutoInstall process to determine the client identifier manually.

To determine the client identifier manually requires connecting a terminal to the device, and powering it on, so that you can enter the show interface interface-type interface-number command. The format is nullcisco Use the show interface interface-type interface-number command to display the information and statistics for a Fast Ethernet interface. The format of the client identifier for this interface is nullcisco The table below shows the values for converting characters to their hexadecimal equivalents.

Use the show interface interface-type interface-number command to display the information and statistics for Ethernet 0 on R4. The format of the client identifier for this interface is nullciscoe0. Using the values for converting characters to their hexadecimal equivalents in the first table above, the client identifier for Ethernet 0 on R4 is shown in the last row of the table below.

Use the show interface interface-type interface-number command to display the information and statistics for Ethernet 0 on R3. The format of the client identifier for this interface is: nullciscoe0. Using the values for converting characters to their hexadecimal equivalents in the first table above, the client identifier for Ethernet 0 on R3 is shown in the last row of the table below.

Use the show interface interface-type interface-number command to display the information and statistics for Ethernet 0 on R2. Using the values for converting characters to their hexadecimal equivalents in the first table above, the client identifier for Ethernet 0 on R2 is shown in the last row of the table below. You have now determined the values for the client identifiers on each device.

The final step is to add a period after each group of four characters working from the left to the right as shown below:. If you determined the value for the client identifiers manually, you do not need to perform this task. 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. Do not place the network-confg or router configuration files r4-confg, r3-confg, or r2-confg in the root directory of the TFTP server yet.

You do not want any of the routers to load these files until you have ensured that each router will obtain the correct IP address from the DHCP server so that the router will load the correct configuration file.

This task is broken down into subtasks. The following example shows how to configure IP routing on R4. Store the configuration file on the TFTP server with the name r2-confg.

This server should be the only DHCP server that is accessible by the routers that you will be using AutoInstall to set up. The following example shows how to configure the ip dhcp excluded-address command to exclude every IP address except The following example shows how to verify the configuration on R1. Verify that the configuration file has the IP addresses for the Ethernet interfaces and the ip helper-address ip-address command.

The following example shows how to enable the debug ip dhcp server events command on R1. 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.

The following example shows how to identify the value for the client identifier on each of the routers. The following step is repeated for each of the routers. You should have only one of the routers powered-on at any time.

When you have identified the value of the client identifier field for the router, turn the router off and proceed to the next router.

Connect R4 to the Ethernet network and power it on. The following message is displayed on the terminal connected to R1 when R4 is assigned the IP address Copy the client identifier Keep the text file open for the next two routers.

Connect R3 to the Ethernet network and power it on. The following message is displayed on the terminal connected to R1 when R3 is assigned the IP address Keep the text file open for the final router. Connect R2 to the Ethernet network and power it on.

The following message is displayed on the terminal connected to R1 when R2 is assigned the IP address You have determined the values for the client identifiers on each router. The following example shows how to remove the temporary DHCP pool on the router that is no longer required.

If the interface cannot download a configuration file successfully after three attempts, the interface does not attempt further. The first configuration file that is downloaded and installed successfully triggers a reboot of the controller. After the reboot, the controller runs the newly downloaded configuration. Note: This configuration example uses the host name to determine the file name of the configuration file on the TFTP server. Make sure to set the subnet mask correctly for your network settings.

Note: You might want to exclude IP addresses within this range that have been previously assigned to other devices so that the same addresses are not used twice.

Set the lease duration to a value that is appropriate for your network. This value determines how often the IP address of a device expires and must be renewed by the device. Click the Yes, I want to configure these options now radio button, and click Next.

Type the IP address of the default gateway, and click Add in order to configure the default gateway. All devices need a default gateway configured.

This gateway is the router interface nearest to the devices, which has an interface on the same IP subnet as the device and is where the devices send IP packets if the receiving device is not on the same IP subnet as the sending device. The new DHCP scope is now created. However, it is not yet Active and does not assign IP addresses. Complete these steps in order to add the TFTP option to the scope:. In order to activate this option, right-click Scope Options , and choose Configure Options. We recommend that you use the enable secret command because it uses an improved encryption algorithm.

If you configure the enable secret command, it takes precedence over the enable password command; the two commands cannot be in effect simultaneously. Optional Sets a local password to control access to various privilege levels. Specifies an additional layer of security over the enable password command. By default, the privileged EXEC command interpreter waits 10 minutes to detect user input before timing out.

When you configure the console line, you can also set communication parameters, specify autobaud connections, and configure terminal operating parameters for the terminal that you are using. Configures the console line and starts the line configuration command collection mode.

Displays the running configuration file. The following example shows how to set the console idle privileged EXEC timeout to 2 minutes 30 seconds:. The following example shows how to set the console idle privileged EXEC timeout to 30 seconds:. The router provides an Ethernet management port named GigabitEthernet0. The purpose of this interface is to allow users to perform management tasks on the router.

It is an interface that should not and often cannot forward network traffic. It ca, however, be used to access the router through Telnet and SSH to perform management tasks on the router. The interface is most useful before a router begins routing, or in troubleshooting scenarios when other forwarding interfaces are inactive.

Note he following aspects of the management ethernet interface:. This isolates the traffic on the management interface away from the forwarding plane. The basic configuration is like other interfaces; however, there are many forwarding features that are not supported on these interfaces. No forwarding features can be configured on the GigabitEthernet0 interface as it is only used for management.

This sections shows how to assign an IP address and interface description to an Ethernet interface on your router. For information on interface numbering, see the software configuration guide for your router. Displays a brief status of the interfaces that are configured for IP. Specifies the Ethernet interface and enters interface configuration mode. Optional Adds a description to an interface configuration. The description helps you remember what is attached to this interface. The description can be useful for troubleshooting.

Sets a primary IP address for an interface. Verify that the Ethernet interfaces are up and configured correctly.

This section describes how to specify a default route with IP routing enabled. The Cisco IOS-XE software uses the gateway router as a last resort if it does not have a better route for a packet and if the destination is not a connected network. This section describes how to select a network as a default route a candidate route for computing the gateway of last resort. The way in which routing protocols propagate the default route information varies for each protocol. When IP routing is configured, the system will use a configured or learned route to forward packets, including a configured default route.

A router might not be able to determine the routes to all other networks. To provide complete routing capability, the common practice is to use some routers as smart routers and give the remaining routers default routes to the smart router. Smart routers have routing table information for the entire internetwork. These default routes can be passed along dynamically, or can be configured into the individual routers. Most dynamic interior routing protocols include a mechanism for causing a smart router to generate dynamic default information that is then passed along to other routers.

If a router has an interface that is directly connected to the specified default network, the dynamic routing protocols running on the router generates or sources a default route. In the case of RIP, the router will advertise the pseudonetwork 0.

In the case of IGRP, the network itself is advertised and flagged as an exterior route. A router that is generating the default for a network may also need a default of its own. One way a router can generate its own default is to specify a static route to the network 0.

When default information is being passed along through a dynamic routing protocol, no further configuration is required. The system periodically scans its routing table to choose the optimal default network as its default route. In the case of RIP, there is only one choice, network 0. In the case of IGRP, there might be several networks that can be candidates for the system default. The Cisco IOS-XE software uses both administrative distance and metric information to determine the default route gateway of last resort.

The selected default route appears in the gateway of last resort display of the show ip route EXEC command. If dynamic default information is not being passed to the software, candidates for the default route are specified with the ip default-network global configuration command. In this usage, the ip default-network command takes an unconnected network as an argument. If this network appears in the routing table from any source dynamic or static , it is flagged as a candidate default route and is a possible choice for the default route.

If the router has no interface on the default network, but does have a route to it, it considers this network as a candidate default path. The route candidates are examined and based on administrative distance and metric, the best one is chosen. The gateway to the best default path becomes the gateway of last resort. Enables privileged EXEC mode. Enter your password if prompted. Selects a network as a candidate route for computing the gateway of last resort.

Creates a static route to network 0. Displays the current routing table information. Verify that the gateway of last resort is set. Virtual terminal vty lines are used to allow remote access to the router. This section shows you how to configure the virtual terminal lines with a password, so that only authorized users can remotely access the router.

By default, the router has five virtual terminal lines. However, you can create additional virtual terminal lines. If you want to secure the virtual terminal lines vty with an access list, see the Access Control Lists: Overview and Guidelines. Starts the line configuration command collection mode for the virtual terminal lines vty for remote console access.

Verify that you bave properly configured the virtual terminal lines for remote access. From another network device, attempt to open a Telnet session to the router. Verifies that you can remotely access the router and that the virtual terminal line password is correctly configured. The following example shows how to configure virtual terminal lines with a password:. After you configure the vty lines, follow these steps:.

This section describes how to enter line configuration mode for the auxiliary line. How you configure the auxiliary line depends on your particular implementation of the auxiliary AUX port. See the following documents for information on configuring the auxiliary line:. Starts the line configuration command collection mode for the auxiliary line.

See the Technical Specifications Note and sample configurations to configure the line for your particular implementation of the AUX port. This section describes how to verify network connectivity for your router.

Diagnoses initial network connectivity. To verify connectivity, ping the next hop router or connected host for each configured interface to. Logs in to a host that supports Telnet.