|
|
This document provides instructions for installing the Cisco AccessPath-LS3 Integrated Access System. The system consists of a number of individual components and a set of cables. The instructions are for the integrated system, for additional information about the individual system components, see the documents listed in "Related and Referenced Documents."
This document contains the following sections:
| 1See also any applicable configuration notes, updates, and release notes.
2These documents are not shipped in printed format with the Cisco AccessPath-LS3 Integrated Access System. They are, however, available on the Documentation CD-ROM, the World Wide Web, or you can order them (see the section "Cisco Connection Online" for ordering information). |
Before you can configure the AccessPath-LS3 software, use the instructions in the document Cisco AccessPath-LS3 Integrated Access System Hardware Installationand Configuration to install the hardware.
Configuring the AccessPath-LS3 system requires the following steps:
After you complete these tasks, you can use the AccessPath-LS3 system to provide network access.
The Cisco IP addressing spreadsheet that follows (Figure 1) can help you set IP addresses for your AccessPath-LS3 system. Use the spreadsheet along with the following explanation to plan IP addressing for your AccessPath-LS3 system.
Note The private network numbers shown in the sample configuration files later in this document use addresses assigned directly from the IP addressing spreadsheets. These exact addresses may be used for internal networks but should never be made available over the Internet.
The columns in the IP addressing spreadsheet are used as follows:
Double lines, are used to assist with aligning subnet boundaries.
Each stack member's Ethernet and Fast Ethernet interfaces require an IP address assignment. Because Ethernet is broadcast, these IP assignments must come from a contiguous block that begins and ends at some power of 2 boundary. In addition, this block must be big enough to accommodate all possible interfaces in the biggest AccessPath configuration (21 Access Server Shelves).
Note The addressing scheme was developed to accommodate the AccessPath system, which can have up to 21 Access Server Shelves. The spreadsheet shown in Figure 1 has been scaled down for the AccessPath-LS3 system, which can have up to 4 Access Server Shelves.
For the AccessPath System, a block of 32 addresses is needed, of which the first and last are not usable for IP assignments, so 30 usable IP addresses remain. The Ethernet group addresses are at the beginning of the management network, and the Fast Ethernet addresses are at the beginning of the first network (Net-1).
The remaining address space is required for the stack host-specific or 32-bit subnet addresses and could be anywhere on any network. They do not technically have to be contiguous; however, this addressing scheme tries to keep things uniform in order to simplify management and support.
The Loopback 0 interfaces need IP addresses, which are assigned in a block below the Fast Ethernet network addresses. Again, they do not have to be in a contiguous block, but we chose to do this to help reduce the number of routes.
Next, addresses are assigned to the Access Server Shelf pools. Pool assignments are kept within the defined 24-bit subnet addresses, starting and stopping on power of 2 boundaries. The resulting assignments allow for only 8 E1 interfaces per 24-bit subnet network. Because an Access Server Shelf can have a Quad E1 card, each pool should accommodate up to 120 addresses. This fits nicely in a 25-bit network, therefore each 24-bit subnet network would have 2 pools. In a T1 configuration, the pool consists of only 96 addresses in each range, but the ranges are the same, only 2 per 24-bit network. See the spreadsheet for details.
A block of 64 contiguous addresses is assigned as management or failover network addresses. The first 32 addresses comprise a 26-bit subnet which is used for the Ethernet (broadcast) interfaces inside the stack. The remaining IP numbers in this group are host-specific or 32-bit subnet addresses and are used for nonbroadcast interfaces for management traffic, such as Loopback 1 interfaces or AUX port peer IP assignments.
This group of management addresses is assigned based on the starting address. This starting address can take on any value in its first three octets but the fourth octet must be 0, 64, 128, or 192. The spreadsheet shows the group that starts at .0. If another value for the fourth octet is chosen, simply add it to the value indicated on the spreadsheet to arrive at the actual address. For example, starting at 64 would mean that the peer address for the Eth1/0 port on the Cisco 3640 would become xxx.xxx.xxx.93 (xxx.xxx.xxx.64 + xxx.xxx.xxx.29).
Note The use of management/failover network addresses requires an additional 10-Mbps segment with a hub or switch.
In order to minimize the number of data broadcasts with each routing update, we implemented summary address statements on each interface. Each pool is summarized as a 25-bit subnet network. For example, if you transcribe this into Cisco IOS configuration commands using an EIGRP process number of 4000 and a network address of 172.21.107.0, the command becomes:
ip summary-address eigrp 4000 172.21.107.0 255.255.255.128
This addressing scheme uses Variable Length Subnet Masking (VLSM) to conserve IP address space, and therefore limits our choice of internal routing protocols to those with VLSM support. OSPF, static routes, and IS-IS support variable-length subnet masks (VLSMs).
Each time you power on the router, it goes through the following boot sequence:
1. The router goes through 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 router 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 router 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, then the router searches for a valid configuration file.
5. If a valid configuration file is not found in NVRAM, the router runs the System Configuration Dialog so you can configure it manually. For normal router operation, there must be a valid Cisco IOS image in Flash memory and a configuration file in NVRAM.
The first time you boot your router, you will need to configure the router interfaces and then save the configuration to a file in NVRAM. See the next section "Configuring the Console Router Shelf for the First Time" for interface configuration information. See the section "Saving Configuration Changes" later in this document for information on how to save the router configuration to NVRAM.
You can configure the Console Router Shelf using one of the following procedures, which are described in this section:
This document instructs you to use the System Configuration Dialog and then the Configuration mode to configure the Console Router Shelf. You will then use the configuration mode to configure the Access Server Shelves.
Timesaver Acquire the correct network addresses from your network plan before you begin to configure the router. |
If you are not familiar with Cisco IOS software, refer to the Configuration Fundamentals Configuration Guide, which is on the Documentation CD-ROM, the web, or you can order the printed document for more information.
If you do not plan to use AutoInstall, make sure all the WAN cables are disconnected from the router. The router will attempt to run AutoInstall whenever you power it on if there is a WAN connection on both ends and the router does not have a configuration file stored in NVRAM. It can take several minutes for the router to determine that AutoInstall is not connected to a remote Transmission Control Protocol/Internet Protocol (TCP/IP) host.
If your router does not have a configuration (setup) file and you are not using AutoInstall, the router 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 router 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.
This section gives an example configuration using the System Configuration Dialog. When you are configuring your router, respond as appropriate for your network.
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 router ports. For more information about IP addresses and subnets, refer to the Internetworking Technology Overview publication, which is on the documentation CD-ROM, the web, or you can order the printed document.
Note You can run the Configuration Dialog any time you are at the privileged EXEC prompt (#) by entering the setup command.
Take the following steps to configure the router using the System Configuration Dialog:
(For more information, refer to the section "Connecting to the Console Port on the Console Router Shelf" in Cisco AccessPath-LS3 Integrated Access System Hardware Installation and Configuration document.
The default parameters for the console port are 9600 baud, 8 data bits, no parity, and 1 stop bits.
Step 2 After about 30 seconds, information similar to the following is displayed on the console screen.
The messages displayed vary, depending on the interfaces on the rear panel of the router and the Cisco IOS release and feature set you selected. The screen displays in this section are for reference only and may not exactly reflect the screen displays on your console.
Step 3 Press Return or enter yes to begin the configuration process.
Step 4 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 5 Configure the host name.
Step 6 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 router will accept your entry, but will display a warning message indicating that you should enter a different password.
Step 7 Enter the enable and virtual terminal passwords:
Step 8 Press Return to accept Simple Network Management Protocol (SNMP) management, or enter no to refuse it:
Step 9 In the following example, the router is configured for Internet Protocol (IP). Configure the appropriate protocols for your router 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.
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 router, repeat this procedure to configure the second and subsequent LAN interfaces.
The Fast Ethernet interface is configured to allow connection to a 100BaseT LAN. To configure the interface parameters, you need to know the Fast Ethernet interface network addresses.
Take the following steps to configure a Fast Ethernet interface to allow communication over a LAN:
Step 2 Determine which protocols you want on the LAN interface and enter the appropriate responses. (You must have previously enabled these protocols as part of global configuration.) In the following example, the interface is being configured for IP:
Step 3 If there is more than one LAN interface on your router, repeat this procedure to configure the second and subsequent LAN interfaces.
The serial interfaces are configured to allow connection to WANs through a CSU/DSU. All serial ports are initially configured as synchronous ports. After the initial configuration is completed, configure the serial ports you plan to use as asynchronous ports using the physical-layer command in configuration mode.
Take the following steps to configure the serial port(s):
Step 2 Determine which protocols you want on the synchronous serial 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 serial interface on your router, repeat this procedure to configure the remaining serial interfaces.
Step 4 The configuration you entered is now displayed and you are asked if you want to use the displayed configuration. If you enter no, you will lose the configuration information you just entered and you can begin the configuration again. If you enter yes, the configuration will be entered and saved in the startup configuration:
You have now entered a basic configuration. You will use the command-line interface to enter the rest of the configuration file for the Console Router Shelf. Proceed to the next section for additional configuration instructions.
The asynchronous ports, logging, security, and aux port configurations still need to be set using the command-line interface.
The following steps provide an example of how to complete the configuration of the Router Shelf.
The router enters global configuration mode, indicated by the CRS01(config)# prompt.
Step 2 Enter commands so that the resulting configuration file is similar to the one shown below. 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.
Step 5 Enter the disable command to return to the user level:
Step 6 Enter the show commands to check the configuration.
For more information about configuring the Console Router Shelf, refer to the Cisco 3640 Router Installation and Configuration Guide. If you need assistance, see the last section "Cisco Connection Online."
Your AccessPath-LS3 system comes with a CD that contains sample configuration files for each of the AccessPath-LS3 components. You can copy these files to your TFTP server, edit them using a text editor and the configurations in the following sections as examples, and download them to each component using TFTP.
Note This solution requires that the AccessPath-LS3 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 (example uses a Cisco 3640):
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 crs01-confg is entered to copy the crs01-confg file:
Step 4 Review the configuration to insure it is really what you want to load.
The router displays the configuration loaded from the TFTP server and should look like the sample configuration on page 10.
Step 5 Reload the router, as follows:
The router displays the reload messages. Watch for error messages during the configuration load. The reload is done over a copy to prevent the configurations from merging. This ensures a clean reload and configuration.
Step 6 Repeat this procedure for each AccessPath-LS3 device.
This section describes how to connect to an Access Server Shelf, substitute your own IP addresses for the placeholder addresses in the configuration file, and configure interfaces. The instructions describe connecting to the console port on each Access Server Shelf using a Telnet connection through the Console Router Shelf. This is only possible if have the 16-port asynchronous module installed in the Console Router Shelf. If you do not have this module, you must connect a console to the console port on each Access Server, refer to the Cisco AS5300 Universal Access Server Hardware Installation Guide for detailed instructions.
This section also includes a sample configuration for each Access Server Shelf.
In the following example the Console Router Shelf, at IP address 172.21.105.56, connects to the Access Server Shelf AS01 on port 2001:
Step 2 Turn on the Access Server Shelf.
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 Shelf configuration to the terminal to view it (and for reference when configuring IP addresses).
Step 5 Enter global configuration mode and enter the hostname, the IP address, and subnet mask for interface Ethernet 0, and enter exit.
Configure each of the Access Server Shelves similarly. See the following sections for additional configuration details.
Note The previous procedure does not cover all of the steps required for an Access Server Shelf configuration. For more information, refer to the Cisco AS5300 Universal Access Server Software Configuration Guide.
Use the sample configuration below to configure AS01. You will have to Telnet to AS01 using port 2001 (if you have the 16-port asynchronous module installed in the Console Router Shelf) or you must connect a console to the console port on the access server. Enter the configuration mode as described in the previous section. The user-defined parameters are shown in bold.
This configuration is for a typical United States PRI/T1 installation.
Note The sample configuration file for Access Server Shelf 01 contains additional comment lines beyond those shown in the other Access Server Shelf sample files. Refer to the AS01 example if you need a better understanding of the basic design of the Access Server Shelf configurations.
Use the sample configuration below to configure AS02. You will have to Telnet to AS02 using port 2002 (if you have the 16-port asynchronous module installed in the Console Router Shelf) or you must connect a console to the console port on the access server. Enter the configuration mode as described in the section, "Configuring the Access Server Shelves." The user-defined parameters are shown in bold.
This configuration is for a typical United States PRI/T1 installation.
Use the sample configuration below to configure AS03. You will have to Telnet to AS03 using port 2003 (if you have the 16-port asynchronous module installed in the Console Router Shelf) or you must connect a console to the console port on the access server. Enter the configuration mode as described in the section, "Configuring the Access Server Shelves." The user-defined parameters are shown in bold.
This configuration is for a typical United States PRI/T1 installation.
Use the sample configuration below to configure AS04. You will have to Telnet to AS04 using port 2004 (if you have the 16-port asynchronous module installed in the Console Router Shelf) or you must connect a console to the console port on the access server. Enter the configuration mode as described in the section, "Configuring the Access Server Shelves."
This configuration is for a typical United States PRI/T1 installation.
After each of the AccessPath-LS3 components is configured you must connect the system to a network and configure security. Making the network connection is discussed in the Cisco 3640 Router Installation and Configuration Guide and security is discussed in theCisco AccessPath Integrated Access System Software Configuration Guide. If you need assistance, see the next section "Cisco Connection Online."
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO 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 CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.
Posted: Tue Jan 21 00:51:33 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
