|
|
This chapter describes first-time startup procedures for the Cisco AccessPath-TS3 Integrated Access System. It assumes you have installed the AccessPath-TS3 system as described in the Cisco AccessPath-TS3 Integrated Access System Hardware Installation and Configuration Guide and Regulatory Compliance and Safety Information for the Cisco AccessPath-TS3 Integrated Access System.
If your AccessPath-TS3 system does not include the APM, or if you prefer to configure the AccessPath-TS3 system via the command-line interface (CLI), follow the instructions in this chapter.
When adding components to the AccessPath-TS3 system, make sure the new component is running a compatible Cisco IOS software image; if it is not, install that software image before proceeding. For information on the correct Cisco IOS software images for each component, see the document Release Notes for the Cisco AccessPath-TS3 Integrated Access System. For instructions on installing Cisco IOS software, see the appropriate software configuration guide on the Documentation CD-ROM or on Cisco Connection Online (CCO).
Note Release notes for each release of the Cisco IOS software are included on the Documentation CD-ROM shipped with the AccessPath-TS3 system and on the web via CCO.
The System Controller facilitates access to the CLI of all components in the AccessPath-TS3 system.
You can connect to the System Controller in the following ways:
Note For information about how to attach a terminal or modem to the System Controller, see Chapter 9, "Configuring a Modem for the AccessPath-TS3 System," and the Cisco AccessPath-TS3 Integrated Access System Hardware Installation and Configuration Guide.
All components in the AccessPath-TS3 system are configured through the System Controller. Because the console port of each component in the AccessPath-TS3 system is connected to a serial port on the System Controller, an administrator can gain access to each component by Telnetting to a specific port on the System Controller.
Each time you power on the System Controller, it goes through the following boot sequence:
1. The System Controller initiates a power-on self-test diagnostics to verify basic operation of the CPU, memory, and interfaces.
2. The system bootstrap software executes and searches for a valid Cisco IOS image (router operating system software). The source of the Cisco IOS image (Flash memory or a Trivial File Transfer Protocol [TFTP] server) is determined by the configuration register setting. The factory-default setting for the configuration register is 0x2102, which indicates that the System Controller should attempt to load a Cisco IOS image from Flash memory.
3. If, after five attempts, a valid Cisco IOS image is not found in Flash memory, the System Controller reverts to boot ROM mode (which is used to install or upgrade a Cisco IOS image).
4. If a valid Cisco IOS image is found, the System Controller searches for a valid configuration file.
5. If a valid configuration file is not found in nonvolatile random-access memory (NVRAM), the System Controller runs one of the following:
(a). AutoInstall—Which runs DNS lookup, bootp request, and TFTP load request for network-confg, then router-confg or routername-confg over the serial interface.
(b). System Configuration Dialog—Which guides you through a configuration via a series of prompts.
For normal System Controller operation, there must be a valid Cisco IOS image in Flash memory and a configuration file in NVRAM.
The first time you boot your System Controller, you will need to configure the System Controller interfaces and then save the configuration to a file in NVRAM. See the next section "Configuring the System Controller for the First Time" for interface configuration information.
Note If you are not familiar with the CLI and Cisco IOS software, see the Configuration Fundamentals Configuration Guide for more information, or see Chapter 1, "Cisco IOS Software and the EXEC Facility Fundamentals."
You can configure the System Controller using one of the following procedures:
This chapter shows you how to use the System Configuration Dialog and then the configuration mode to configure the System Controller and Access Servers.
Timesaver Acquire the correct network addresses from your network plan before you begin to configure the System Controller. |
If you do not plan to use AutoInstall, make sure all the WAN cables are disconnected from the System Controller. The System Controller will attempt to run AutoInstall whenever you power it on if there is a WAN connection with both ends active, and the System Controller does not have a configuration file stored in NVRAM. It can take several minutes for the System Controller to determine that it is not connected to a remote bootp or TFTP host.
If your System Controller does not have a configuration (setup) file and you are not using AutoInstall, the System Controller will automatically start the setup command facility. An interactive dialog called the System Configuration Dialog appears on the console screen. This dialog helps you navigate through the configuration process by prompting you for the configuration information necessary for the System Controller to operate.
Many prompts in the System Configuration Dialog include default answers, which are included in square brackets following the question. To accept a default answer, press Return; otherwise, enter your response, followed by a Return.
This section gives an example configuration using the System Configuration Dialog. When you are configuring your System Controller, respond as appropriate for your network.
Note At any time during the System Configuration Dialog, you can request Help by typing a question mark (?) at a prompt.
Before proceeding with the System Configuration Dialog, obtain from your system administrator the node addresses and the number of bits in the subnet field (if applicable) of the System Controller interfaces. For more information about IP addresses and subnets, see the Internetworking Technology Overview publication, which is on the Documentation CD-ROM, the World Wide Web, or you can order the printed document.
Note You can run the System Configuration Dialog any time you are at the privileged EXEC prompt (#) by entering the setup command.
Take the following steps to configure the System Controller using the System Configuration Dialog:
(For more information, see the Cisco AccessPath-TS3 Integrated Access System Hardware Installation and Configuration Guide.)
The default parameters for the console port are 9600 baud, 8 data bits, no parity, and 1 stop bit.
After about 30 seconds, information similar to the following is displayed on the console screen.
Note The messages displayed vary, depending on the interfaces on the rear panel of the System Controller and the Cisco IOS release and feature set you selected. The screen displays in this section are for reference only and might not exactly reflect the screen displays on your console.
Step 2 Press Return or enter yes to begin the configuration process.
Step 3 When the System Configuration Dialog asks whether you want to view the current configuration, press Return to accept the default entry (yes) in square brackets:
Step 4 Configure the host name:
Step 5 Enter an enable secret password:
The enable password is used when the enable secret password does not exist. For maximum security, be sure the passwords are different. If you enter the same password for both, the System Controller will accept your entry, but will display a warning message indicating that you should enter a different password.
Step 6 Enter the enable and virtual terminal passwords:
Step 7 Press Return to accept Simple Network Management Protocol (SNMP) management, or enter no to refuse it:
Step 8 In the following example, the System Controller is configured for IP. Configure the appropriate protocols for your System Controller using the example configuration that follows:
The Ethernet interfaces are configured to allow connection to a LAN. To configure the interface parameters, you need to know the Ethernet interface network addresses. To plan your network addressing, see the Cisco AccessPath-TS3 Integrated Access System IP Address Map quick reference guide, which came with your AccessPath-TS3 system.
Take the following steps to configure an Ethernet interface to allow communication over a LAN:
Step 2 Determine which protocols you want to support on the LAN interface and enter the appropriate responses. In the following example, the system is being configured for IP:
Step 3 If there is more than one LAN interface on your System Controller, repeat this procedure to configure the second and subsequent LAN interfaces.
You have now entered a basic configuration. You can now use the CLI to enter the rest of the configuration file for the System Controller. Proceed to the next section for additional configuration instructions.
The asynchronous ports, logging, security, and auxiliary port configurations still need to be set using the CLI.
The following steps provide an example of how to complete the configuration of the System Controller:
The System Controller enters global configuration mode, indicated by the CMS01(config)# prompt.
Step 2 Enter the commands shown below so that the resulting configuration file is similar to the following. The user-defined parameters are shown in bold.
Step 3 After you complete the configuration, press Ctrl-Z to exit configuration mode.
Step 4 Write the new configuration to memory as follows:
The system displays a confirmation message when the configuration is saved:
For more information about configuring the System Controller, see the Cisco 3640 Router Installation and Configuration Guide.
To verify the System Controller information:
Your AccessPath-TS3 system comes with a CD-ROM that contains sample configuration files for each of the AccessPath-TS3 components. You can copy these files to your TFTP server, edit them using a text editor and the configurations in Appendix A, "Sample Configurations," as examples, and download them to each component using TFTP. These configurations can also be loaded onto the AccessPath-TS3 system using the optional APM software. For this procedure, see the Installing Cisco AccessPath Manager document.
Note This solution requires that the AccessPath-TS3 system have a functional connection to a network with a TFTP server.
To copy a configuration file from a TFTP server to NVRAM, perform the following steps while logged into the System Controller:
Step 2 Enter or confirm the IP address of the remote TFTP server:
Step 3 Specify the source filename. In this example, the UNIX filename cms01-confg is entered to copy the cms01-confg file:
Step 4 Review the configuration to ensure it is really what you want to load:
The System Controller displays the configuration loaded from the TFTP server and should look like the sample configuration for a System Controller located in Appendix A, "Sample Configurations."
Step 5 Reload the System Controller as follows:
The System Controller displays the reload messages. Watch for error messages during the configuration load. The reload is done over a copy of the running configuration to prevent the configurations from merging. This ensures a clean reload and configuration.
Step 6 Repeat this procedure for each AccessPath-TS3 device.
This section describes how to connect to an Access Server, substitute your own IP addresses for the placeholder addresses in the configuration file, and configure interfaces. The instructions describe how to connect to the console port on each Access Server using a Telnet connection through the System Controller.
In the following example, the System Controller, at IP address 192.168.1.56, connects to the Access Server AS01 on port 2001:
Step 2 Turn ON the Access Server.
The Access Server automatically goes into setup mode. Type Ctrl-C to quit setup mode so you can manually enter the configuration.
Step 3 Enter enable mode.
In the following example, the user enters enable mode (without entering a password, because none is set yet):
Step 4 Write the Access Server configuration to the terminal to view it (and for reference when configuring IP addresses):
Step 5 Enter global configuration mode and enter the host name, the IP address, and subnet mask for interface Fast Ethernet 0, and enter exit:
Repeat this procedure to configure each of the Access Server.
Note The previous procedure does not cover all of the steps required for an Access Server configuration. For more information, see the Cisco AS5300 Universal Access Server Software Configuration Guide.
You have now completed a basic configuration. To continue your configuration process, proceed to any of the following chapters or the appendix (depending on what you want to configure):
Posted: Tue Jan 21 04:18:13 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.