cc/td/doc/product/access/acs_fix/cis2500/2509
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Configuring the Cisco 2500 Series Access Server

Configuring the Cisco 2500 Series Access Server

This chapter describes the procedures for configuring the Cisco 2500 series access server and contains the following sections:

To configure your console, you need to connect a terminal to the access server. Configuration requires access to the console port.

If You Need More Information

The Cisco IOS software running the access server contains extensive features and functionality. The effective use of many of many of these features is easier if you have more information at hand. We recommend to you the following resources:

Additional Publications

For more information on configuring the Cisco 2500 series access server, see the appendix "Internetworking Primer," or refer to the following publications:

These publications are available on UniverCD.

All Cisco technical documentation and additional literature are available on UniverCD, Cisco's online library of product information. UniverCD is updated and shipped monthly, so it might be more up to date than printed documentation. UniverCD is available both as a single CD and as an annual subscription. To order UniverCD, contact your local sales representative or call Customer Service.

Contacting Customer Service

To obtain general information about Cisco Systems, Cisco's products or documentation, or upgrades, call 800 553-6387 or 408 526-7208. Customer Service hours are 5:00 a.m. to 6:00 p.m. Pacific time, Monday through Friday (excluding company holidays). You can also send e-mail to cs-rep@cisco.com.

Using Cisco Information Online

Cisco Information Online (CIO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CIO to obtain additional content and services.

Available 24 hours a day, 7 days a week, CIO provides a wealth of standard and value-added services to Cisco's customers and business partners. CIO services include product information, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CIO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously--a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CIO (called "CIO Classic") supports Zmodem, Kermit, Xmodem, FTP, Internet e-mail, and fax download options, and is excellent for quick access to information over lower bandwidths. The WWW version of CIO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CIO in the following ways:

For a copy of CIO's Frequently Asked Questions (FAQ), contact  cio-help@cisco.com. For additional information, contact  cio-team@cisco.com.

Contacting the Technical Assistance Center

If you are a system administrator and need personal technical assistance with a Cisco product which is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447 or 408 526-7209, or send an e-mail message to tac@cisco.com. Emergency technical assistance (for network-down or severe network problems) is available 24 hours a day, 7 days a week.

When you contact the TAC for help, have the following information ready:

Contacting the European Technical Assistance Center

Cisco and its European Service Partners coordinate all customer service in Europe, including hardware and software telephone technical support, onsite service, and module exchange and repair. For more information, contact the European TAC.

European TAC numbers and e-mail address are as follows:

Booting the Access Server for the First Time

The access server is administered using the Cisco command interpreter, called the EXEC. You must log in to the access server before you can enter an EXEC command. For security purposes the EXEC has two levels of access to commands, user EXEC mode and privileged EXEC mode.

To enter the privileged mode you must enter the enable secret password on systems running Cisco Internetwork Operating System (Cisco IOS) Release 10.2(3) or later, or the enable password on systems running Cisco IOS releases prior to 10.2(3) or when using the boot ROM monitor.

Using the Enable Secret and the Enable Password

The commands available at the user level are a subset of those available at the privileged level. Because many privileged-level EXEC commands are used to set operating parameters, you should password-protect these commands to prevent unauthorized use.

There are two commands you can use to do this, depending on the release you have of the Cisco IOS software:

The enable secret password is available in Cisco IOS Release 10.2(3) or later. The enable secret password is not available before Release 10.2(3). The enable password is available in all releases. You must enter the correct password to gain access to privileged-level commands.

On systems running Release 10.2(3) or later, the enable secret password is used. when you are running from the boot ROM, the enable password might be used depending on your ROM level.

The passwords should be different for maximum security. If you enter the same password for both during the setup script, the system will accept it, but you will receive a warning message indicating that you should enter a different password.

An enable secret password can contain from 1 to 25 uppercase and lowercase alphanumeric characters; an enable password can contain any number of uppercase and lowercase alphanumeric characters. In both cases, a number cannot be the first character. Spaces are also valid password characters; for example, "two words" is a valid password. Leading spaces are ignored; trailing spaces are recognized.

If you lose or forget your enable password, see the section "Recovering a Lost Enable Password" in the chapter "Maintaining the Cisco 2500 Series Access Server."

Configuring the Access Server

You can configure the access server following one of the procedures described in the following sections:

Follow the procedure that best fits the needs of your network configuration.


Note You will need to acquire the correct network addresses from your system administrator or consult your network plan to determine correct addresses before you can complete the access server configuration. For details on network addressing, see the appendix "Internetworking Primer."

Before continuing the configuration process, check the current state of the access server by entering the show version command. The show version command will display the release of Cisco IOS software that is available on the access server.

Configuring the Access Server Using the Configuration Mode

You can configure the access server manually if you prefer not to use the setup facility or AutoInstall. Take the following steps to configure the access server manually:

Step 1 Connect a console terminal by following the instructions described in the section "Connecting the Console Terminal and Modem" in the chapter "Installing the Cisco 2500 Series Access Server" and then power up the access server.

Step 2 When you are asked if you would like to enter the initial dialog, answer no to go into the normal operating mode of the access server:

Step 3 After a few seconds you will see the user EXEC prompt (Router>). Type enable to enter enable mode. Configuration changes can only be made in enable mode:

The prompt will change to the privileged EXEC prompt:


Step 4 Enter the command config terminal at the enable prompt to enter configuration mode from the terminal:

You can now enter any changes to the configuration that are desired. Press Ctrl-Z to exit configuration mode. (See the appendix "Internetworking Primer" for configuration assistance.)


To see the currently operating configuration, enter the command show running-config at the # prompt if you are running Cisco IOS Release 11.0 or later. Enter the command write terminal at the # prompt if you are running a Cisco IOS release earlier than 11.0:

router# show running-config

To see the configuration in NVRAM, enter the command show startup-config at the enable prompt.

router# show config

To make your changes permanent, enter the command copy running-config startup-config at the enable prompt if you are running Cisco IOS Release 11.0 or later. Enter the command write memory if you are running a Cisco IOS release earlier than 11.0:

The results of the show running-config and show startup-config commands will differ if you have made changes to the configuration, but have not yet written them to NVRAM.

The access server is now configured and will boot with the configuration you have entered.

Configuring the Access Server Using AutoInstall

The AutoInstall process is designed to configure the access server automatically after connection to your WAN. In order for AutoInstall to work properly, a Transmission Control Protocol/Internet Protocol (TCP/IP) host on your network must be preconfigured to provide the required configuration files. The TCP/IP host may exist anywhere on the network, as long as the following two conditions are maintained:


  1. The host must be on the remote side of the access server's synchronous serial connection to the WAN.

  2. User Datagram Protocol (UDP) broadcasts to and from the access server and the TCP/IP host must be enabled.

This functionality is coordinated by your system administrator at the site where the TCP/IP host is located. You should not attempt to use AutoInstall unless the required files have been provided on the TCP/IP host. See the publication Access and Communication Server Configuration Guide for information on how AutoInstall works.

Take the following steps to prepare your access server for the AutoInstall process:

Step 1 Attach the synchronous serial cable to the access server.

Step 2 Turn on power to the access server.

The access server will load the operating system image from Flash memory. If the remote end of the WAN connection is connected and properly configured, the AutoInstall process will begin.


If the AutoInstall completed successfully, you may wish to write the configuration data to the access server's nonvolatile random-access memory (NVRAM). Perform the following step to complete this task:


Step 3 At the # prompt, enter the copy running-config startup-config command if you are running Cisco IOS Release 11.0 or later, or the write memory command if you are running a Cisco IOS release earlier than 11.0:

Taking this step will save the configuration settings that the AutoInstall process created in the access server. If you fail to do this, your configuration will be lost the next time you reload the access server.


Configuring the Access Server Manually Using the Setup Facility

If you do not plan to use AutoInstall, do not connect the access server's serial (WAN) cable to the channel service unit/data service unit (CSU/DSU). This will prevent the access server from attempting to run the AutoInstall process. The access server will attempt to run AutoInstall whenever you start it if the serial (WAN) connection is connected on both ends and the access server does not have a configuration stored in NVRAM. It can take several minutes for the access server to determine that AutoInstall is not set up to a remote TCP/IP host.

Once the access server has determined that AutoInstall is not configured, it will default to the setup facility. If the serial (WAN) cable is not connected, the access server will boot from Flash memory and go into the setup facility.


Note You can run the setup facility any time you are at the enable prompt (#) by entering the command setup.

Configuring the Global Parameters

When you first start the setup program you must configure the global parameters. The global parameters are used for controlling system-wide settings. Use the following procedure to enter the global parameters:

Step 1 Connect a console terminal by following the instructions in the section "Connecting the Console Terminal and Modem" in the chapter "Installing the Cisco 2500 Series Access Server" and then boot the access server to the EXEC prompt (Router>).

Step 2 When you have booted from Flash memory, the following information will appear after about 30 seconds. When you see this information displayed, you have successfully booted your access server:

Step 3 Enter yes or press Return when you are asked if you would like to enter the configuration dialog and if you would like to see the current interface summary. Press Return to accept the default (yes):

Step 4 Choose what protocols to support on your Ethernet or Token Ring interface. For IP-only installations, you can accept the default values for most of the questions. A typical configuration using IP, IPX, and AppleTalk follows:

Step 5 Enter the enable secret password, the enable password, and the virtual terminal password:

Enter yes or no to accept or refuse SNMP management:


The Simple Network Management Protocol (SNMP) is the most widely supported open standard for network management. It provides a means to access and set configuration and run-time parameters of routers and communication servers. SNMP defines a set of functions that can be used to monitor and control network elements.


Step 6 Determine if you will be using DECnet on your access server. If you are configuring for DECnet, enter the appropriate values for your area number, node number, and area routing:

Step 7 In most cases you will use IP routing. If you are using IP routing, you must also select an interior routing protocol. You can specify only one of two interior routing protocols to operate on your system using setup: Interior Gateway Routing Protocol (IGRP) or Routing Information Protocol (RIP).

Enter yes (the default) or press Return to configure IP, and then select an interior routing protocol for IP:


Step 8 In this example, routing will be enabled on AppleTalk and IPX; IP has already been selected:

Configuring the Asynchronous Interface

The access server is equipped with up to 16 asynchronous interfaces, which are referred to as lines in the setup dialog. The asynchronous lines must be configured to permit asynchronous devices to be connected to the access server. (See the sections "Asynchronous Protocols," and "Modems" in the appendix "Internetworking Primer.")

The asynchronous ports on the access server are configured to allow connection by TTY devices, Remote nodes, and Remote LANs.

A variety of devices can connect to the access server using the asynchronous lines. Terminals and remote nodes (such as PCs, Macintosh computers, workstations, and host systems) connect to the access server and make use of its services. The access server provides services allowing access to other asynchronous devices, such as printers, modems, or terminals.

The following steps configure the lines on the access server to permit use of the asynchronous lines by the access server or remote devices:

Step 1 Enter yes or press Return to configure asynchronous lines:

Step 2 Set the line speed and the flow control for the asynchronous lines. Hardware flow control must be configured to allow proper communications with modems.

For additional information on configuring modem connections see the section "Modems" in the appendix "Internetworking Primer."


Step 3 Enter yes if you will be connecting modems to your access server to allow remote sessions, and to configure your modems to use the default chat script:

Step 4 Configure your system to allow serial line internet protocol (SLIP) and Point-to-Point protocol (PPP) access, as follows:

For additional information on configuring SLIP and PPP connections, see the section "Asynchronous Protocols" in the appendix "Internetworking Primer."


Step 5 Enter yes or press Return at the AppleTalk remote access prompt to configure for AppleTalk, and then enter the AppleTalk network address and zone name for your AppleTalk clients.

ARA protocol uses an internal nonextended unique network number, and a zone name for ARA protocol clients. For additional information on configuring ARA protocol, see the section "Asynchronous Protocols" in the appendix "Internetworking Primer."


Step 6 Enter yes if you will be using IPX on your asynchronous lines, In this example, the access server will not be using IPX on the asynchronous lines:

Configuring the Ethernet or Token Ring Interfaces

Take the following steps to configure the Ethernet or Token Ring interface to allow communication over a LAN. To configure the interface parameters, you need to know your Ethernet or Token Ring interface network addresses.

Step 1 In the following example, the system is being configured for an Ethernet LAN using IP. Respond as follows (using your own addresses and mask) to the setup prompts:

Step 2 Enter yes if you will be using AppleTalk on the interface, enter yes to configure for extended AppleTalk networks, and then enter the cable range number. See the appendix "Internetworking Primer" for additional information on AppleTalk routing. Enter the zone name, and any other additional zones that will be associated with your local zone:

Step 3 Determine if you are going to enable IPX on this interface, enter the unique IPX network number. See the appendix "Internetworking Primer" for additional information on IPX routing:

Configuring the Synchronous Serial Interfaces

The synchronous serial interfaces are configured to allow connection to WANs through a CSU/DSU. Once the Ethernet or Token Ring port on your access server has been configured, take the following steps to configure the serial port:

Step 1 Enter yes to configure serial port 0:

Step 2 Determine what protocols you will allow on the synchronous serial interface and enter the appropriate responses:

Step 3 Configure the second synchronous serial interface as follows:

Entering the Asynchronous Interface Addresses

After the asynchronous lines have been configured and the routing protocols have been selected, enter the IP addresses for each asynchronous interface.

For information on asynchronous protocols, see the section "Asynchronous Protocols" in the appendix "Internetworking Primer," and for information on IP addressing, see the section "Desktop Protocols" in the appendix "Internetworking Primer."

Step 1 Enter the IP address for each of the asynchronous interfaces on the access server:

Step 2 The configuration you have entered is now displayed and you are asked if you want to use the displayed configuration. If you answer no, you can begin the configuration again. If you answer yes, the configuration will be entered and saved in the startup configuration:

The access server is now configured properly and is ready to use. Enter the command setup if you want to modify the parameters after the initial configuration. To perform more complex configurations, enter the command configure. For information on configuration, see the publication Access and Communications Servers Configuration Guide.

Checking Your Settings

You can check the value of the settings you have entered by entering at the # prompt the command show running-config if you are running Cisco IOS Release 11.0 or later, or the command write terminal if you are running a Cisco IOS Release earlier than 11.0:

router# show running-config
.
.
.
configuration register is 0x2102

To store the configuration or changes to your startup configuration, enter at the hostname# prompt the command copy running-config startup-config if you are running Cisco IOS Release 11.0 or later, or the command write memory if you are running a Cisco IOS release earlier than 11.0:

Hostname# copy running-config startup-config

Entering this command will save the configuration settings that the setup process created in the access server. If you fail to do this, your configuration will be lost the next time you reload the access server.

hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1997 © Cisco Systems Inc.