www.cisco.com/univercd/cc/td/doc/product/core/cis7505/cicg7500/cicg75bc.htm#xtocid192697
It guides you through a basic router configuration, which is sufficient for you to access your network. Complex configuration procedures are beyond the scope of this text, and can be found in the configuration publications listed in the section " 45 If You Need More Configuration Information" on 46 page 4-51. It contains procedures and information that are applied globally to all Cisco 7500 series routers. The included examples might appear differently on your system depending on the Cisco IOS software release in use, and the model router being configured. Refer to the 47 "Cisco 7500 Series Product Overview" for information on Cisco IOS software release requirements. When configuring a Cisco 7576, you will configure router A and then router B. The following sections provide information for configuring your Cisco 7500 series router: * 48 Starting the System and Observing Initial Conditions * 49 Overview of Software Configuration Register Settings at Startup * 50 Configuring the Software Configuration Register * 51 Booting the Cisco 7500 Series Router for the First Time * 52 Using the Enable Secret and the Enable Password * 53 Recovering a Lost Password * 54 Configuring the Cisco 7500 Series System * 55 Implementing Other Configuration Tasks * 56 What Do I Do Now? Configuration requires access to the console port on each Route Switch Processor (RSP) in your router. Note You should also use the companion publication 59 Interface Processor Installation and Configuration Guide in conjunction with the basic configuration information in this chapter. Starting the System and Observing Initial Conditions This section describes the initial Cisco 7500 series system startup. When all interfaces are connected, perform a final check of all connections, then power up the router as follows: Step 1 Check the following components to make sure they are secure: * Each interface processor is inserted all the way into its slot, and all of the captive installation screws are tightened. Step 2 Check the console terminal to make sure it is connected to the console port and turned on. Step 3 Turn ON the power supply by turning the system power switch to the ON position. The green AC (or DC) OK and fan OK LEDs on each power supply should go on. After a few seconds, the red output fail LED will turn OFF. In a noisy environment, it is sometimes difficult to hear the fan or blower; If this indicator is not on after system initialization, an error has occurred. If necessary, refer to the appendix "Troubleshooting the Installation," in this publication, for troubleshooting procedures. Step 6 Wait until the system boot is complete before attempting to verify the status of interface processor indicators. During the boot process, the LED indicators on most of the interfaces go ON and OFF in irregular sequence. Some may go on, go out, and go on again for a short time. Some will stay on during the entire boot process if an interface is already configured and brought up, such as the EIP receive LED, which stays on as it detects traffic on the line. Step 7 Observe the LED indicators on the interface processors in your system. When the system boot is complete (a few seconds), the RSP begins to initialize the interface processors. During this initialization, the indicators on each interface processor behave differently (most flash ON and OFF). This RSP2 is system master Other RSP2 is not plugged in Compiled Wed 10-May-95 11:06 Step 8 Observe the system startup banner. When you start up the router for the first time, the system automatically enters the setup command facility, which determines which interfaces are installed and prompts you for configuration information for each one. Refer to the Getting Started' Guide for additional help. You do not have to configure the interfaces immediately; Many of the interface processor LEDs will not go on until you have configured the interfaces. To verify correct operation of each interface, complete the first-time startup procedures and configuration, then refer to the LED descriptions in the companion publication Interface Processor Installation and Configuration to check the status of the interfaces. If the system does not complete each of these steps, proceed to the appendix "Troubleshooting the Installation," in this publication, for troubleshooting recommendations and procedures. Overview of Software Configuration Register Settings at Startup Bits 0 through 3 of the software configuration register form the boot field, specified as a binary number. The factory default configuration register setting for systems is 0x102; When the boot field is set to either 0 or 1 (0-0-0-0 or 0-0-0-1), the system ignores any boot instructions in the system configuration file and the following occurs: * When the boot field is set to 1 (the factory default), the system boots the first image in the onboard bootflash single in-line memory module (SIMM). You can enter the boot command only, or include additional boot instructions with the command, such as the name of a file stored in Flash memory or a file that you specify for booting from a network server. If you use the boot command without specifying a file or any other boot instructions, the system boots from the default Flash image (the first image in onboard Flash memory). Otherwise, you can instruct the system to boot from a specific Flash image (using the boot system flash filename command), or boot from a network server by sending broadcast TFTP requests (using the boot system filename command), or by sending a direct TFTP request to a specific server (using the boot system filename address command). You can also use the boot command to boot images stored in the Personal Computer Memory Card International Association (PCMCIA) Flash memory cards in the RSP. If you set the boot field to any bit pattern other than 0 or 1, the system uses the resulting number to form a filename for booting over the network. The system uses the filename to invoke the system image by booting over the net. However, if the configuration file contains any boot instructions, the system uses those boot instructions instead of the filename it computed from the configuration register settings. You must set the boot field for the boot functions you require. Settings for the software configuration register are written into NVRAM. Following are some reasons for changing the software configuration register settings: * To select a boot source and default boot filename. For example, the factory default value of 0x0101 is a combination of settings. Table 4-1: Software Configuration Register Bit Meanings CAPTION: Bit Number 65 ^1 Hexadecimal Meaning 00 to 03 0x0000 to 0x000F Boot field (see 66 Table 4-2) 06 0x0040 Causes system software to ignore NVRAM contents 07 0x0080 OEM 67 ^2 bit enabled 08 0x0100 Break disabled 09 0x0200 Use secondary bootstrap 10 0x0400 Internet Protocol (IP) broadcast with all zeros 11 to 12 0x0800 to 0x1000 Console line speed (default is 9600 baud) 13 0x2000 Boot default Flash software if network boot fails 14 0x4000 IP broadcasts do not have network numbers 15 0x8000 Enable diagnostic messages and ignore NVRAM contents ^1The factory default value for the configuration register is 0x0101. This value is a combination of the following: bit 8 = 0x0100 and bits 00 through 03 = 0x0001 (see 68 Table 4-2). Table 4-2: Explanation of Boot Field (Configuration Register Bits 00 to 03) CAPTION: Boot Field Meaning 00 Stays at the system bootstrap prompt 01 Boots the first system image in onboard Flash memory 02 to 0F Specifies a default netboot filename Enables boot system commands that override the default netboot filename Configuration Register Bit Meanings The lowest four bits of the software configuration register (bits 3, 2, 1, and 0) form the boot field. If you set the boot field value to 0x2 through 0xF and there is a valid boot system command stored in the configuration file, the router boots the system software as directed by that value. If there is no boot system command, the router forms a default boot filename for booting from a network server. Router(config)# config-register 0x102 Router(config)# boot sys...
|