|
|
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.
| TimeSaver The preferred way to configure components in the AccessPath-TS3 system is by using the AccessPath Manager (APM), unless your AccessPath-TS3 system hardware supports 8 PRI per Access Server, in which case the preferred methoud is to use the AccessPath-TS3 Configurator. If your AccessPath-TS3 system includes the optional APM, you can use it to perform the first-time startup tasks described in this chapter. See the document Installing Cisco AccessPath Manager and the online help that comes as part of the APM software. |
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).
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:
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.
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.
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.
Take the following steps to configure the System Controller using the System Configuration Dialog:
Step 1 Connect a console terminal to the console port on the front panel of your System Controller, and then power ON the System Controller.
(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.
System Bootstrap, Version X.X(X) [XXXXX XXX], RELEASE SOFTWARE
Copyright (c) 1994-199X by cisco Systems, Inc.
C3600 processor with 16384 Kbytes of main memory
Main memory is configured to 64 bit mode with parity disabled
program load complete, entry point: 0x80008000, size: 0x30277c
Self decompressing the image : #################################################
################################################################################
################################################################################
#################### [OK]
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (XXXX-X-X), Version XX.X (XXX)_[XXXX XXX]
Copyright (c) 1986-199X by Cisco Systems, Inc.
Compiled Mon 01-Jul-9X 21:38 by XXXXX
Image text-base: 0x60008890, data-base: 0x605CA000
cisco 3640 (R4700) processor (revision 0x00) with 12288K/4096K bytes of memory.
Processor board ID 00000000
R4700 processor, Implementation XX, Revision X.X
Bridging software.
SuperLAT software copyright 1990 by Meridian Technology Corp).
X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.
TN3270 Emulation software (copyright 1994 by TGV Inc).
2 Ethernet/IEEE 802.3 interface.
2 Serial network interface(s).
DRAM configuration is 64 bits wide with parity disabled.
125K bytes of non-volatile configuration memory.
4096K bytes of processor board System flash (Read/Write)
Notice: NVRAM invalid, possibly due to write erase.
--- System Configuration Dialog ---
At any point you may enter a question mark '?' for help.
Use ctrl-c to abort configuration dialog at any prompt.
Default settings are in square brackets '[]'.
Would you like to enter the initial configuration dialog? [yes]:
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:
First, would you like to see the current interface summary? [yes]: Any interface listed with OK? value "NO" does not have a valid configuration Interface IP-Address OK? Method Status Protocol Ethernet1/0 unassigned NO unset up down Serial1/0 unassigned NO unset down down Ethernet1/1 unassigned NO unset up down
Step 4 Configure the host name:
Enter host name [Router]: CMS01
Step 5 Enter an enable secret password:
The enable secret is a one-way cryptographic secret password used instead of the enable password when it exists. Enter enable secret: secret123 The enable password is used when there is no enable secret password and when using older software and some boot images.
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:
Enter enable password: cisco Enter virtual terminal password: vterm1
Step 7 Press Return to accept Simple Network Management Protocol (SNMP) management, or enter no to refuse it:
Configure SNMP Network Management? [yes]: no
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:
Configure LAT? [no]: Configure AppleTalk? [no]: Configure DECnet? [no]: Configure IP? [yes]: Configure IGRP routing? [yes]: no Configure RIP routing? [no]: Configure CLNS? [no]: Configure IPX? [no]: Configure Vines? [no]: Configure XNS? [no]: Configure Apollo? [no]: Configure bridging? [no]: Configure Async lines? [yes]: no
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 1 Press Return or enter yes to configure the LAN interface:
Configuring interface parameters: Configuring interface Ethernet1/0: Is this interface in use? [yes]:
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:
Configure IP on this interface? [yes]: IP address for this interface: 192.168.1.29 Number of bits in subnet field [8]: 11 Class C network is 192.168.1.0, 11 subnet bits; mask is /27
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:
Step 1 Enter the config terminal command to enter configuration mode:
CMS01> enable Password: <password> CMS01# config terminal CMS01(config)#
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.
| TimeSaver Use the Tab after entering each command, and use the ? to see the command options. |
no service finger service timestamps debug datetime msec localtime show-timezone service timestamps log datetime msec localtime show-timezone service password-encryption no service udp-small-servers no service tcp-small-servers ! hostname sjcms01 ! aaa new-model aaa authentication login CONSOLE none aaa authentication login ADMIN radius local aaa authentication ppp ADMIN if-needed radius local aaa authorization network radius aaa accounting network start-stop radius aaa accounting connection start-stop radius aaa accounting exec start-stop radius enable password cisco1 enable secret secret123 ! ! for copy rcp config file username justincase password doublesecret ip rcmd remote-username APMadmin ip routing ! ip subnet-zero no ip source-route ip name-server 192.168.10.1 ip radius source-interface Loopback1 clock timezone GMT 0 ! interface Loopback 1 description "MGMT Network and Async129" ip address 172.16.2.56 255.255.255.255 ! interface Ethernet1/0 description "To Failover switch" ip address 172.16.2.24 255.255.255.224 no ip directed-broadcast no shutdown ! interface Ethernet1/1 description "To Primary switch" ip address 172.16.1.24 255.255.255.224 no ip directed-broadcast no shutdown ! interface Async 129 description "OSS Modem Incoming Call" ip unnumbered Loopback1 encapsulation ppp async dynamic address async mode interactive peer default ip address 172.16.2.63 no cdp enable no fair-queue ppp authentication chap callin ADMIN ! router ospf 4242 passive-interface Loopback1 network 172.16.2.0 0.0.0.63 area 21 network 172.16.1.0 0.0.0.63 area 21 ! ! ip classless ! ip http server logging trap debugging logging facility syslog ! logging source uses logging IP logging 192.168.10.1 logging source-interface Loopback1 no access-list 10 access-list 10 permit 192.168.10.1 ! snmp-server community public RO snmp-server community private RW 10 snmp-server trap-source Loopback1 snmp-server location NOC-Center snmp-server contact Network-Administrator snmp-server system-shutdown snmp-server host 192.168.10.1 sjcms01 radius-server host 192.168.10.8 auth-port 1645 acct-port 1646 ! radius-server key bananas ! line con 0 session-timeout 45 exec-timeout 45 0 login authentication CONSOLE transport preferred none line 1 32 session-timeout 60 no exec login authentication ADMIN modem InOut transport input all flowcontrol hardware line aux 0 exec-timeout 15 0 autoselect during-login autoselect ppp login authentication ADMIN modem InOut transport preferred none transport input none flowcontrol hardware speed 115200 line vty 0 4 session-timeout 45 exec-timeout 45 password cisco2 transport preferred none login authentication ADMIN ! ntp server 192.168.10.1 end
Step 3 After you complete the configuration, press Ctrl-Z to exit configuration mode.
Step 4 Write the new configuration to memory as follows:
CMS01# copy running-config startup-config
The system displays a confirmation message when the configuration is saved:
Building configuration... [OK] CMS01#
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.
To copy a configuration file from a TFTP server to NVRAM, perform the following steps while logged into the System Controller:
Step 1 Enter the copy tftp startup-config command without the destination partition and destination filename options specified in the initial command line:
CMS01# copy tftp startup-config
Step 2 Enter or confirm the IP address of the remote TFTP server:
Address of remote host [255.255.255.255]? 192.168.245.2
Step 3 Specify the source filename. In this example, the UNIX filename cms01-confg is entered to copy the cms01-confg file:
Name of configuration file [router-confg]? cms01-confg Configure using cms01-confg from 192.168.245.2? [confirm] y Loading cms01-confg from 192.168.245.2 (via Ethernet1/0): ! [OK - 3147/128975 bytes] [OK] CMS01# %SYS-5-CONFIG_NV: Non-volatile store configured from cms01-confg by console tftp from 192.168.245.2
Step 4 Review the configuration to ensure it is really what you want to load:
CMS01# show startup-config
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:
CMS01# reload Proceed with reload? [confirm] y *Feb 28 16:00:46.507 PST: %SYS-5-RELOAD: Reload requested
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.
Step 1 Telnet to the System Controller, and connect to the Access Server. Be sure that the Access Server is not powered on.
In the following example, the System Controller, at IP address 192.168.1.56, connects to the Access Server AS01 on port 2001:
# telnet 192.168.1.56 2001 Trying 172.21.105.56... Connected to 172.21.105.56. Escape character is '^]'.
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):
router> enable router#
Step 4 Write the Access Server configuration to the terminal to view it (and for reference when configuring IP addresses):
router# show running-config Current configuration: ! version 11.2 service timestamps debug datetime msec localtime show-timezone service timestamps log datetime localtime show-timezone service udp-small-servers service tcp-small-servers ! ...
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:
router# config term router(config)# hostname AS01 AS01(config)# interface fastethernet 0 AS01(config-if)# ip address 172.21.106.1 255.255.255.224 !Use an address from Net-1 in the IP Address Map. AS01(config-if)# exit AS01(config)#
Repeat this procedure to configure each of the Access Server.
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):
|
|
