|
|
This chapter describes the initial system startup process, and provides the procedures for performing a basic configuration of your Cisco 12012 Gigabit Switch Router (GSR).
This chapter contains the following sections:
After you complete the final check, proceed to the following section to start up the system.
This section describes the initial system startup processes and procedures.
Use the following procedure to start your system:
Step 1 Turn ON each installed power supply by turning its system power switch to the ON (|) position. For AC-input power supplies, the green AC OK LED should go on. For DC-input power supplies, the green input OK LED should go on.
Step 2 Listen for the blower modules; you should immediately hear them operating. In a noisy environment the blower modules might be difficult to hear; therefore, place your hand in front of the exhaust vents to verify that the blower modules are operating.
Step 3 During the GRP boot process, observe the GRP alphanumeric LED displays, which are located at the end of the GRP. (See Figure 4-1.)
Each 4-digit display is capable of showing system messages and displays a sequence that is similar to that shown in Table 4-1.
| LED Display | Indication |
|---|---|
MRAM | GRP microcode loads into MBus random-access memory (RAM); where nnnn is the microcode version. For example, Microcode Version 1.17 displays as 0117.1 |
MSTR | This GRP is enabled and recognized by the system. Assumes a valid Cisco IOS software version is running. |
Step 4 During the line card boot process, which occurs immediately after the GRP boots, observe the alphanumeric LED indicators on each line card. Line cards boot successfully from left to right. (The physical location of the alphanumeric LED displays on the line cards is the same as on the GRP, shown in Figure 4-1.)
Each line card displays a sequence that is similar to that shown in Table 4-2.
| LED Display1 | Indication |
FABL | The line card waits for the fabric downloader to begin loading into DRAM.1 |
FABL | The fabric downloader loads into DRAM. |
FABL | The fabric downloader launches from DRAM. |
FABL | The fabric downloader runs in DRAM. |
IOS | The Cisco IOS software downloads. |
IOS | The Cisco IOS software launches. |
| LED Display | Indications |
IOS | The Cisco IOS software runs in DRAM. |
IOS | The line card is enabled and ready for use. |
Step 5 If the ROM monitor prompt (>) appears, you then have to boot the Cisco IOS software image you want to use by entering the appropriate b command at the ROM monitor prompt (>):
 | Caution To prevent system problems, use the b flash command option carefully; otherwise, you might instruct the system to boot a non-Cisco IOS software image from Flash memory. |
After you boot a Cisco IOS software image, proceed to Step 6. (For additional information on system boot functionality, refer to the section "Manually Booting the System," later in this chapter.)
Step 6 While the system boots from the appropriate Cisco IOS software image, the console screen displays a script and system banner similar to the following:
Observe the system startup banner. When you start up an unconfigured system for the first time, the system automatically enters the setup facility, which determines which interfaces are installed and prompts you for configuration information for each one.
On the console terminal, after the system displays the system banner and hardware configuration, you will see the following System Configuration Dialog prompt:
--- 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 '[]'.
Continue with configuration dialog? [yes/no]:
You have the option of proceeding with the setup facility or exiting from setup and using configuration commands to configure global (system-wide) and interface-specific parameters. You do not have to configure the interfaces immediately; however, you cannot enable the interfaces or connect them to any networks until you have configured them. (For configuration information, refer to the section "Configuring the Cisco 12012," later in this chapter.)
The interface-specific LEDs on the line cards might not go on until you have configured the line card interfaces. To verify correct operation of each line card interface, complete the first-time setup procedures and configuration, then refer to the LED descriptions in the configuration notes for each line card to check the status of the interfaces.
If the system does not complete each of the preceding steps, proceed to the chapter "Troubleshooting the Installation," in this publication, for troubleshooting recommendations and procedures.
This information in this section is required only if the system does not boot automatically from a specified default Cisco IOS software image.
The system is administered using the Cisco command interpreter, called the EXEC. You must boot and log in to the system 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 privileged mode, you must enter the enable secret password, which is optional, but must first have been saved in memory. (For information on using passwords, refer to Step 5 and Step 6 in the section "Configuring the Global Parameters," later in this chapter.)
At the ROM monitor prompt, view the contents of onboard Flash memory using the following command:
rommon 1> dir bootflash:
File size Checksum File name
3277967 bytes (0x32048f) 0x6b331e30 Cisco 12012 gsr-p-mz.112-8
rommon 2>
Also, view the Flash memory PCMCIA card in slot 0 or slot 1 using the following command:
rommon 2> dir slot0:
File size Checksum File name
3054276 bytes (0x2e9ac4) 0x97788495 Cisco 12012 gsr-p-mz.112-8
rommon 3>
Locate the Cisco IOS software image that you want to boot and boot from this image using the following commands, as appropriate:
rommon 3>boot slot0:filename
or...
rommon 3>boot slot1:filename
or...
rommon 3>boot bootflash:filename
If you did not change the configuration register setting, the next reload will revert to the default configuration register setting. (The factory default configuration register setting for systems and for GRP spares is 0x0102.)
You can a complete a basic configuration of the Cisco 12012 system using one of the procedures described in the following sections:
At initial startup, the Cisco 12012 defaults to the setup facility; the system automatically goes into the setup facility. (The setup command facility functions exactly the same as a completely unconfigured system functions when you first boot it up. You can run the setup facility any time you are at the enable prompt (#) by entering the setup command.)
Two parameters of the system configuration are considered during setup: global parameters and interface parameters.
The primary difference between what you see with the setup facility and what you see with the setup command facility is that with the latter, any current system configuration defaults are displayed in square brackets [ ] as you move through the setup command process and are queried by the system to make changes.
For example, during the setup facility for a POS interface, assuming the interface has not been configured, you will see the following:
Configuring interface POS4/0: Is this interface in use?:yesConfigure IP on this interface?:yes
Note that no default or current conditions are shown in square brackets [ ].
Conversely, you will see the following during the setup command facility, assuming the POS interface has been configured and you are being queried by the system to change it:
Configuring interface POS4/0: Is this interface in use?[yes]:yesConfigure IP on this interface?[yes]:yes
Note that the default or current conditions of the interface are shown in square brackets [ ].
Proceed to the following section to configure the system using the setup facility or the setup command facility. Differences are clearly noted.
When you first start the setup facility or enter the setup command, you are queried by the system to configure the global parameters. The global parameters are used for controlling system-wide settings.
Use the following procedure to boot the Cisco 12012 and enter the global parameters:
Step 1 Connect a console terminal to the console port on the GRP, and then boot the system to the user EXEC prompt (Router>).
Step 2 When you have booted the system, the following information appears after about 30 seconds. (This information is similar to what should appear on your console screen.) When you see this information displayed, you have successfully booted your system:
Step 3 Enter yes or press Return when asked if you want to enter the configuration dialog and if you want to see the current interface summary. Press Return to accept the default (yes):
In the following example of a yes response (during the setup facility), the partial summary shows a Cisco 12012 system at first-time startup; that is, nothing has been configured, and the following summary reflects this.
Interface IP-Address OK? Method Status Protocol Ethernet0 unassigned YES unset administratively down down POS3/0 unassigned YES unset administratively down down POS3/1 unassigned YES unset administratively down down POS3/2 unassigned YES unset administratively down down POS3/3 unassigned YES unset administratively down down ATM4/0 unassigned YES unset administratively down down (Additional displayed text omitted from this example.)
In the following example of a yes response (during the setup command facility), the partial summary shows a Cisco 12012 system in which some interfaces have already been configured, and the following summary reflects this.
Interface IP-Address OK? Method Status Protocol Ethernet0 3.3.1.1 YES NVRAM up up POS3/0 2.1.1.1 YES NVRAM up up POS3/1 2.1.1.2 YES NVRAM up up POS3/2 2.1.1.3 YES NVRAM up up POS3/3 2.1.1.4 YES NVRAM up up ATM4/0 1.1.1.2 YES NVRAM up up (Additional displayed text omitted from this example.)
Step 4 Choose which protocols to support on your interfaces. For Internet Protocol (IP)-only installations, you can accept the default values for most of the questions.
A typical minimal configuration using IP follows, and continues through Step 10:
Router
Step 5 Enter the enable secret password when the following is displayed, and make a note of this password for future reference:
barney
Step 6 Enter the enable password when the following is displayed, and make a note of this password for future reference:
wilma
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.
The enable secret password functionality is available for Cisco 12000 series systems. You must enter the correct password to gain access to privileged-level commands. When you are running from the boot ROM monitor, the enable password might be used depending on your boot 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.
Step 7 Enter the virtual terminal password when the following is displayed, and make a note of this password for future reference:
bambam
Step 8 In most cases you will use IP routing. If so, you must also select an interior routing protocol. You can specify Interior Gateway Routing Protocol (IGRP) to operate on your system using setup.
Enter yes (the default) or press Return to configure IP, and then select IGRP:
199
Step 9 Enter yes or no to accept or refuse SNMP management:
Step 10 Enter yes or no to accept or refuse CLNS management:
yes
As a review of what you have done, the following sample display includes a continuous listing of all configuration parameters you selected in Steps 4 through 10. These parameters and their defaults are shown in the order in which they appeared on your console terminal.
Router
barney
wilma
bambam
yes
yes
199
yes
yes
This completes the portion of the setup facility for configuring global parameters. The setup facility continues for configuring interfaces; refer to the following section.
This section provides steps for configuring installed interfaces (using the setup facility or setup command facility) to allow communication over your external networks. To configure the interface parameters, you need your interface network addresses, subnet mask information, and you need to know which protocols you want to configure; consult with your network administrator for this information. (For additional interface configuration information on each of the line cards available for the Cisco 12012, refer to the individual configuration notes that shipped with your line cards.)
Use the following procedure to configure the interfaces installed in your Cisco 12012:
yes
yes
3.3.1.1
8
yes
Step 2 The Packet-Over-SONET (POS) interfaces allow connections to external OC-3/STM-1 or OC-12/STM-4 networks. In the following example, the system is being configured for a POS interface using IP. Respond as appropriate for your needs, using your own address and subnet mask for the setup prompts. (Also refer to Step 3, which shows this same interface being configured for IP unnumbered; use whichever step is most appropriate for your needs.)
yes
yes
no
2.1.1.1
0
yes
For more complete POS interface configuration information, refer to the configuration notes Quad OC-3c/STM-1c Packet-Over-SONET Line Card Installation and Configuration (Document Number 78-4333-xx) and OC-12c/STM-4c Packet-Over-SONET Line Card Installation and Configuration (Document Number 78-4341-xx) that accompanied your Quad OC-3c/STM-1c and OC-12c/STM-4c POS line cards, respectively.
Step 3 In the following example, the system is being configured for a POS interface using IP unnumbered. Respond as appropriate for your needs:
yes
yes
yes
ethernet0
yes
Repeat Step 2 and Step 3 for each POS interface you need to configure; then, if you have ATM interfaces installed, proceed to Step 4. Otherwise, proceed to Step 5 to check and verify your configuration parameters.
Step 4 The Asynchronous Transfer Mode (ATM) interfaces allow connections to external OC-12/STM-4 networks. In the following example, the system is being configured for an ATM interface using IP. Respond as appropriate for your needs, using your own address and subnet mask for the setup prompts:
yes
yes
1.1.1.2
0
For more complete ATM interface configuration information, refer to the configuration note OC-12c/STM-4c Asynchronous Transfer Mode Line Card Installation and Configuration (Document Number 78-4344-xx) that accompanied your OC-12c/STM-4c ATM line card.
Repeat Step 4 for each ATM interface you need to configure; then, to check and verify your configuration parameters, proceed to Step 5.
Step 5 When your interface configuration is complete (you reach and respond to the configuration dialog for the last installed interface), check and verify the entire list of configuration parameters, which should be displayed on your console terminal and end with the following query:
A no response places you back at the enabled mode prompt (#) and you will need to reissue the setup command to reenter your configuration. A yes response writes the running configuration to NVRAM, as follows:
yes
After you press the Return key, the following prompt will appear:
This completes the procedures for configuring global parameters and interface parameters in your system using the setup facility or setup command. Your Ethernet, POS, and ATM interfaces are now available for limited use.
If you want to modify the currently saved configuration parameters after the initial configuration, enter the setup command; or, to perform more complex configurations, enter configuration mode and use the configure command.
Router> sh version
Cisco Internetwork Operating System Software
IOS (tm) GS Software (GSR-P-MZ), Released Version 11.2(8)GS [biff-bfr_112]
Copyright (c) 1986-1997 by cisco Systems, Inc.
Compiled Mon 25-Aug-97 20:13 by biff
Image text-base: 0x60010900, data-base: 0x604FE000
ROM: System Bootstrap, Version 11.2(8)GS [biff-bfr_112], RELEASED SOFTWARE
BOOTFLASH: GS Software (GSR-BOOT-M), Released Version 11.2(8)GS [biff-bfr_112 1913]
Router uptime is 20 days, 12 hours, 16 minutes
System restarted by reload
System image file is "biff/gsr-p-mz", booted via tftp from 1.1.1.254
cisco GRP (R5000) processor (revision 0x00) with 65536K bytes of memory.
Processor board ID 00000000
R5000 processor, Implementation 35, Revision 2.1 (512KB Level 2 Cache)
Last reset from power-on
X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.
1 Single-port OC12c ATM controller (1 ATM).
1 four-port OC3 POS controller (4 POS).
1 Ethernet/IEEE 802.3 interface(s)
1 ATM network interface(s)
4 Packet over Sonet network interface(s)
507K bytes of non-volatile configuration memory.
20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).
8192K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x0102
Router#
For additional interface configuration information, refer to the configuration notes that accompanied your line cards. For more information on specific system configurations, refer to the section "If You Need More Configuration Information," later in this chapter.
You can configure the Cisco 12012 system manually (via configuration mode) if you prefer not to use the setup facility. Use the following procedure to configure the Cisco 12012 system manually:
Step 1 Connect a console terminal to the console port of your GRP.
Step 2 When you are asked if you want to enter the initial dialog, answer no to go into the normal operating mode of the Cisco 12012 as follows:
no
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:
enable
The prompt will change to the privileged EXEC prompt (#) as follows:
Step 4 At the enable prompt (#), enter the config terminal command to enter configuration mode from the terminal as follows:
config terminal
At the prompt, enter the interface type slot/port command to enter interface configuration mode as follows:
Router(config)# interface type slot/port
Router(config-if)#
In either of these configuration modes, you can enter any changes to the Cisco 12012 configuration. Press Ctrl-Z to exit either configuration mode.
Step 5 Save your settings. (Refer to the section "Saving the Running Configuration Settings and Reviewing Your Configuration," later in this chapter.)
You can check the configuration settings you entered or changes you made by entering show running-config command at the enable prompt (#) as follows:
Router# show running-config . . . Router#
To store the configuration or changes to your startup configuration in NVRAM, enter copy running-config startup-config at the enable prompt (#) as follows:
Router# copy running-config startup-config
This command saves the configuration settings that you created in configuration mode. If you fail to do this, your configuration will be lost the next time you reload the system. To display information stored in NVRAM, use the show startup-config EXEC command.
The following sample output shows a typical system configuration:
Router# sh startup-config
Using 1133 out of 520184 bytes
!
version 11.2
no service udp-small-servers
no service tcp-small-servers
!
hostname Router
!
enable password wilma
ip cef distributed switch
ip host biff 3.3.3.254
!
interface Ethernet0
ip address 3.3.1.1 255.255.0.0
no ip mroute-cache
!
interface POS3/0
ip address 2.1.1.1 255.0.0.0
no keepalive
crc 16
no cdp enable
!
interface POS3/1
ip address 2.1.1.2 255.0.0.0
no keepalive
crc 16
no cdp enable
!
interface POS3/2
ip address 2.1.1.3 255.0.0.0
no keepalive
crc 32
no cdp enable
!
interface POS3/3
ip address 2.1.1.4 255.0.0.0
no keepalive
crc 32
no cdp enable
!
interface ATM4/0
ip address 15.0.0.15 255.0.0.0 secondary
ip address 1.1.1.2 255.0.0.0
atm pvc 1 0 64 aal5snap
atm pvc 2 0 72 aal5mux ip 155000 155000 1
atm pvc 3 1 90 aal5snap 312000 312000 1
atm pvc 4 0 108 aal5snap
atm pvc 10 0 144 aal5mux ip 155000 155000 1
atm pvc 11 1 91 aal5snap 310000 310000 1
map-group atm1
!
no ip classless
ip route 2.5.4.254 255.255.255.255 Ethernet0
!
map-list atm1
ip 1.1.1.1 atm-vc 1
ip 1.1.1.3 atm-vc 2
ip 1.1.1.4 atm-vc 4
ip 15.0.0.1 atm-vc 3
ip 15.0.0.5 atm-vc 10
ip 15.0.0.6 atm-vc 11
no logging trap
!
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
password bambam
login
!
end
This section contains information on the following additional configuration, troubleshooting, and maintenance tasks:
The Cisco 12012 system uses a 16-bit software configuration register, which allows you to set specific system parameters. Settings for the software configuration register are written into NVRAM.
Following are some reasons for changing the software configuration register settings:
Table 4-3 lists the meaning of each of the software configuration memory bits, and Table 4-4 defines the boot field, which consists of bits 0 through 3 of the software configuration register and is specified as a binary number.
| Caution To avoid confusion and possibly halting the Cisco 12012, remember that valid configuration register settings might be combinations of settings and not just the individual settings listed in Table 4-3. For example, the factory default value of 0x0102 is a combination of settings. |
| Bit Number2 | Hexadecimal | Meaning |
|---|---|---|
| 00 to 03 | 0x0000 to 0x000F | Boot field (see Table 4-4) |
| 06 | 0x0040 | Causes system software to ignore NVRAM contents |
| 07 | 0x0080 | OEM1 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 |
| 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 filename for booting over the network. Enables boot system commands that override the default filename. |
Bits 0 through 3 of the software configuration register form the boot field, specified as a binary number.
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:
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 send a direct TFTP request to a specific server (using the boot system filename ip-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 located in PCMCIA slot 0 or slot 1 on the GRP. 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.
To form this filename, the system starts with cisco and links the octal equivalent of the boot field value and the processor type in the following format: cisco<bootfieldvalue>-<processorname>; for example, cisco2-grp. The system uses this 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.
Use the following procedure to change the configuration register while running the system software:
Step 1 Enter the enable command and your password to enter privileged level as follows:
enable
Step 2 Enter the configure terminal command at the privileged-level system prompt (#), also called the enabled prompt. You are prompted, as shown in the following example:
conf t
Step 3 Set the contents of the configuration register by entering the config-register value configuration command, where value is a hexadecimal number preceded by 0x (see Table 4-3), as in the following:
config-register 0xvalue
Step 4 Exit configuration mode by entering Ctrl-Z. The new value settings are saved to memory; however, the new settings do not take effect until the system software is reloaded by rebooting the system.
Step 5 Display the configuration register value currently in effect and that will be used at the next reload by entering the show version EXEC command. The value is displayed on the last line of the screen display, as in the following example:
Step 6 Save your settings. (Refer to the section "Saving the Running Configuration Settings and Reviewing Your Configuration," later in this chapter. However, note that configuration register changes take effect only after the system reloads, such as when you issue a reload command from the console.)
Step 7 Reboot the system. The new configuration register value takes effect with the next system boot.
This completes the procedure for making configuration register changes.
The lowest four bits of the software configuration register (bits 3, 2, 1, and 0) form the boot field. (See Table 4-4.) The boot field specifies a number in binary form. If you set the boot field value to 0, you must boot the operating system manually by entering the b command at the bootstrap prompt (>).
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 system boots the Cisco IOS software as directed by that value. If there is no boot system command, the Cisco 12012 forms a default boot filename for booting from a network server. (See Table 4-5 for the format of these default filenames.) In the following example, the software configuration register is set to boot the system from onboard Flash memory and to ignore Break at the next reboot of the system:
Router#conf termEnter configuration commands, one per line. End with CNTL/Z. Router(config)#config-register 0x0102Router(config)#boot system flash[filename]Ctrl-zRouter#
The server creates a default boot filename as part of the automatic configuration process. To form the boot filename, the server starts with the name cisco and adds the octal equivalent of the boot field number, a hyphen, and the processor-type name (grp).
Table 4-5 lists the default boot filenames. A boot system configuration command in the configuration file in NVRAM overrides the default filename created for booting over the network.
| Action/File Name | Bit 3 | Bit 2 | Bit 1 | Bit 0 |
|---|---|---|---|---|
| Bootstrap mode | 0 | 0 | 0 | 0 |
| Default software | 0 | 0 | 0 | 1 |
| cisco2-grp | 0 | 0 | 1 | 0 |
| cisco3-grp | 0 | 0 | 1 | 1 |
| cisco4-grp | 0 | 1 | 0 | 0 |
| cisco5-grp | 0 | 1 | 0 | 1 |
| cisco6-grp | 0 | 1 | 1 | 0 |
| cisco7-grp | 0 | 1 | 1 | 1 |
| cisco10-grp | 1 | 0 | 0 | 0 |
| cisco11-grp | 1 | 0 | 0 | 1 |
| cisco12-grp | 1 | 0 | 1 | 0 |
| cisco13-grp | 1 | 0 | 1 | 1 |
| cisco14-grp | 1 | 1 | 0 | 0 |
| cisco15-grp | 1 | 1 | 0 | 1 |
| cisco16-grp | 1 | 1 | 1 | 0 |
| cisco17-grp | 1 | 1 | 1 | 1 |
Bit 8 controls the console Break key. Setting bit 8 (the factory default) causes the system to ignore the console Break key. Clearing bit 8 causes the system to interpret the Break key as a command and to force the system into the bootstrap monitor, thereby halting normal operation. Regardless of the setting of the break enable bit, a break will cause a return to the ROM monitor during the first few seconds (approximately five seconds) of booting.
Bit 9 is unused. Bit 10 controls the host portion of the IP broadcast address. Setting bit 10 causes the processor to use all zeros; clearing bit 10 (the factory default) causes the processor to use all ones. Bit 10 interacts with bit 14, which controls the network and subnet portions of the broadcast address.
Table 4-6 shows the combined effect of bits 10 and 14.
| Bit 14 | Bit 10 | Address (<net> <host>) |
|---|---|---|
| Off | Off | <ones> <ones> |
| Off | On | <zeros> <zeros> |
| On | On | <net> <zeros> |
| On | Off | <net> <ones> |
Bits 11 and 12 in the configuration register determine the data transmission rate of the console terminal. Table 4-7 shows the bit settings for the four available rates. (The factory-set default data transmission rate is 9600.)
| Baud | Bit 12 | Bit 11 |
|---|---|---|
| 9600 | 0 | 0 |
| 4800 | 0 | 1 |
| 1200 | 1 | 0 |
| 2400 | 1 | 1 |
Bit 13 determines the server response to a bootload failure. Setting bit 13 causes the server to load operating software from Flash memory after five unsuccessful attempts to load a boot file from the network. Clearing bit 13 causes the server to continue attempting to load a boot file from the network indefinitely. By factory default, bit 13 is cleared to 0.
This section provides information on how to recover a lost password. Following is an overview:
Use the following procedure to recover a lost password.
Step 1 Attach an ASCII terminal to the GRP console port.
Step 2 Configure the terminal to operate at 9600 bps, 8 data bits, no parity, 2 stop bits (or to whatever settings the console port is set).
Step 3 Enter the show version command to display the existing configuration register value. Note this value for later use in Step 13.
Step 4 If Break is disabled, power cycle the Cisco 12012. (To power cycle, turn off power, wait five seconds, and then turn it on again.) If Break is enabled on the router, press the Break key or send a break by holding down the Control key and pressing the right square bracket key (^]), then proceed to Step 5.
Step 5 Within five seconds of turning on the router, press the Break key. This action causes the terminal to display the bootstrap program prompt as follows:
Step 6 Set the configuration register to ignore the configuration file information as follows:
confreg
y
y
Step 7 Initialize the router by entering the i command as follows:
i
The router will power cycle, the configuration register will be set to ignore the configuration file, and the router will boot the boot system image and prompt you with the system configuration dialog as follows:
Step 8 Enter no in response to the system configuration dialog prompts until the following system message is displayed:
Step 9 Press Return. After some interface information displays, the prompt appears as follows:
Step 10 Enter the enable command to enter enabled mode. The prompt changes to the following:
Step 11 Enter the show start-up config EXEC command to display the enable password in the configuration file.
Step 12 Enter the configure terminal command at the EXEC prompt. You are prompted as follows:
configure terminal
Step 13 Change the configuration register value back to its original value (noted from Step 3) or change it to a value of 0x0102 (factory default) using the config-register 0x value command.
Step 14 Exit configuration mode by entering Ctrl-Z.
Step 15 Reboot the router and enable it using the recovered password.
This completes the procedure for recovering a lost password.
This section describes procedures for using Flash memory cards in the Gigabit Route Processor (GRP), and contains information on the following Flash memory card functions:
The GRP has two PCMCIA slots--slot 0 and slot 1--into which you can install a Flash memory card. The slots are positioned with slot 0 on the left and slot 1 on the right (refer to Figure 4-2).
Both slots can be used at the same time. The following procedure is a generic one and can be used for a Flash memory card in either slot position.
Use the following procedure to install and remove a Flash memory card:
Step 1 Facing the GRP front panel, hold the Flash memory card with the connector end of the card toward the slot and the label facing right.
Step 2 Insert the card into the appropriate slot until the card completely seats in the connector at the back of the slot and the ejector button pops out toward you (see Figure 4-2b).
Note that the card does not insert all the way inside the GRP; a portion of the card remains outside of the slot. Do not attempt to force the card past this point.
Step 3 To eject the card, press the appropriate ejector button until the card is free of the connector at the back of the slot. (See Figure 4-2c.)
Step 4 Remove the card from the slot and place it in an antistatic bag to protect it.
The Flash memory card that shipped with your router contains the Cisco IOS software image you need to boot your router. In some cases, you might need to insert a new Flash memory card and copy images or backup configuration files onto it. Before you can use a new Flash memory card, you must format it.
| Caution The following formatting procedure erases all information on the Flash memory card. To prevent the loss of important data that might be stored on a Flash memory card, proceed carefully. If you want to save the data on a Flash memory card, copy the data to a server before you format the card. |
Use the following procedure to format a new Flash memory card:
Step 1 Insert the Flash memory card into slot 0. (Use the procedure in the section "Installing and Removing the Flash Memory Card in a GRP," earlier in this chapter.) If slot 0 is not available, use slot 1.
Step 2 Enter the format slot0: (or format slot1:) command as follows:
format slot0:
MyNewCard
The new Flash memory card is now formatted and ready to use.
For complete command descriptions and configuration information, refer to the Configuration Fundamentals Command Reference and the Configuration Fundamentals Configuration Guide. (For information on obtaining these publications, refer to the section "If You Need More Configuration Information," later in this chapter.)
Use the following series of commands to specify that a Cisco IOS software image is bootable. (In this example, the file named new.image.) Note that, since the configuration register must be set to 0x2102, the config-register command is part of the sequence.
Router#config terminalRouter(config)#no boot systemRouter(config)#boot system flash slot0:new.imageRouter(config)#config-register 0x2102Ctrl-zRouter#copy running-config startup-configRouter#reload
When the system reloads, it will boot the Cisco IOS software image from the Flash memory card in slot 0.
Following are software commands related to the onboard Flash memory on the GRP and the Flash memory cards.
You can determine which memory media you are accessing using the pwd command as follows:
Router# pwd
slot0
Router#cd slot1:Router#pwdslot1 Router#cd slot0:Router#pwdslot0
You can list the directory of Flash memory media using the dir [device-name] command, where device-name can be slot0:, slot1:, or bootflash:. An example of the dir command follows:
Router# dir
-#- -length- -----date/time------ name
1 4601977 May 10 1997 09:42:19 myfile1
6 679 May 10 1997 05:43:56 todays-config
7 1 May 10 1997 09:54:53 fun1
You can delete a file from any Flash memory media using the delete filename command, where filename is any file within Flash memory. An example of deleting the file fun1 from the Flash memory card in slot 0 follows:
Router#delete fun1Router#dir-#- -length- -----date/time------ name 1 4601977 May 10 1997 09:42:19 myfile1 6 679 May 10 1997 05:43:56 todays-config
Files that are deleted are marked as deleted, but still occupy space in Flash memory. The squeeze device-name command (where device-name can be slot0:, slot1:, or bootflash:) removes them permanently and pushes all other undeleted files together to eliminate spaces between them.
An example of the squeeze command follows:
Router# squeeze slot0:
All deleted files will be removed, proceed? [confirm]
Squeeze operation may take a while, proceed? [confirm]
ebESZ
To prevent loss of data due to sudden power loss, the "squeezed" data is temporarily saved to another location of Flash memory, which is specially used by the system.
In the preceding command display output, the character "e" means this special location has been erased (which must be performed before any write operation). The character "b" means that the data that is about to be written to this special location has been temporarily copied. The character "E" signifies that the sector that was temporarily occupied by the data has been erased. The character "S" signifies that the data was written to its permanent location in Flash memory.
The configuration register setting 0x0101 tells the system to boot the default image (the first image) from onboard Flash memory, but not reset the Break disable or check for a default filename to be booted over the network. The configuration register setting 0x0102 tells the system to boot from Flash memory if netboot fails, disable Break, and check for a default netboot filename.
For more information on the copy tftp:filename [bootflash: | slot0: | slot1: ]:filename command and other related commands, refer to the set of configuration fundamentals configuration and reference publications.
To enable booting from Flash memory, set configuration register bits 3, 2, 1, and 0 to a value between 2 and 15 in conjunction with the boot system flash device:filename configuration command, where device is bootflash:, slot0:, or slot1:, and filename is the name of the file from which you want to boot the system. (For a detailed configuration register information, refer to the section "Manually Booting the System," earlier in this chapter.)
To enter configuration mode while in the system software image and specify a Flash filename from which to boot, enter the configure terminal command at the enable prompt as follows:
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)#boot system flashdevice:filename
To disable Break and enable the boot system flash device:filename command, enter the config-register command with the value shown in the following example:
Router(config)#config-reg 0x0102Ctrl-zRouter#
| Caution You cannot copy a new Cisco IOS software image into Flash memory while the system is running from Flash memory. |
Use the command copy tftp:filename [ bootflash: | slot0: | slot1: ]:filename for the copy procedure, where tftp:filename is the source of the file, and [ bootflash: | slot0: |
slot1: ]:filename is the destination in onboard Flash memory or on either of the Flash memory cards.
An example of the copy tftp:filename command follows:
Router# copy tftp:myfile1 slot0:myfile1
20575008 bytes available on device slot0, proceed? [confirm]
Address or name of remote host [1.1.1.1]?
Loading new.image from 1.1.1.1 (via Ethernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 7799951/15599616 bytes]
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Router#
In the preceding example, the exclamation points (!!!) appear as the file is downloaded, and the "C" characters signify calculation of the cyclic redundancy check (CRC) value, which is a verification that the file has been correctly downloaded to the Flash memory card.
You can copy a Cisco IOS software image into Flash memory; however, you must first format the Flash memory card and make the image in the Flash memory card bootable. (If you have not already done this, refer to the sections "Formatting a Flash Memory Card" and "Specifying the Cisco IOS Image Used to Boot the System," which appear earlier in this chapter.)
To copy a Cisco IOS software image, use the following procedure, which assumes the following:
Use the following procedure to copy a bootable image into the Flash memory card:
Step 1 Boot the router and allow it to initialize.
Step 2 Enable the router and copy the image new.image to the Flash memory card in slot 0, using the following series of commands:
en
copy tftp:new.image slot0:new.image
In the preceding example, the exclamation points (!!!) appear as the file is downloaded, and the "C" characters signify calculation of the cyclic redundancy check (CRC) value, which is a verification that the file has been correctly downloaded to the Flash memory card. You must now reboot the system.
This completes the procedure for copying a bootable image into a Flash memory card.
As future releases of Cisco IOS software become available, you will receive these images either as a file booted from a network server, a file on floppy disk, or a file on a Flash memory card.
The following scenario describes how to use a newly released Cisco IOS software image on a Flash memory card in a system that has an older image on a Flash memory card in slot 0 and a default boot Cisco IOS software image in the onboard Flash memory.
For this scenario, the filenames are as follows:
You will copy the new Cisco IOS software image from the new Flash memory card onto the Flash memory card that contains the old Cisco IOS software image.
Use the following procedure to copy bootable Cisco IOS software images between Flash memory cards:
Step 1 Boot the router. (For this example, the file image.boot will be used by default.)
Step 2 Enable the router as follows:
en
Step 3 Insert the new Flash memory card in slot 1.
Step 4 Use the following command to copy the file image.new in slot 1 to the Flash memory card in slot 0, only if there is enough memory space for the two images to coexist:
copy slot1:image.new slot0:image.new
You can also enter the previous command as copy slot1:image.new slot0:.
Step 5 Use the following series of commands to designate the file image.new (in the Flash memory card in slot 0) as the default boot image:
config t
no boot system
boot system flash slot0:image.new
Ctrl-z
copy running-config startup-config
reload
When the system reloads, it will boot the file image.new from the Flash memory card in slot 0.
This completes the procedure for copying bootable images between Flash memory cards.
Use the procedures in the following sections to first copy the configuration file from either NVRAM or DRAM to a Flash memory card, and then to copy the configuration file from a Flash memory card back to NVRAM.
Use the following procedure to copy a configuration file from GRP NVRAM to a Flash memory card:
Step 1 Use the show boot command to display the current setting for the environmental variable CONFIG_FILE as follows:
show boot
The preceding example shows that the environmental variable CONFIG_FILE is set for NVRAM, by default.
Step 2 Enter the copy startup-config slot0:filename command as follows:
copy startup-config slot0:myfile2
Step 3 Verify the file was copied correctly using the dir command as follows:
dir slot0:
This completes the procedure for copying a configuration file between GRP NVRAM and a Flash memory card.
You can use the command copy running-config [ slot0: | slot1: ]:filename for the copy procedure where running-config is the file's source (the temporary configuration in DRAM), and [slot0: | slot1: ]:filename is the file's destination in either of the Flash memory cards.
An example of the copy startup-config slot0:filename command follows:
Router# copy running-config slot0:myfile2
20575008 bytes available on device slot0, proceed? [confirm]
Address or name of remote host [1.1.1.1]?
Loading new.image from 1.1.1.1 (via Ethernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 7799951/15599616 bytes]
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Router#
In the preceding example, the exclamation points (!!!) appear as the file is copied. The "C" characters signify calculation of the checksum--a verification that the file has been correctly copied.
Use the dir command to verify the file was copied correctly as follows:
Router# dir slot0:
-#- -length- -----date/time------ name
1 5200084 May 10 1997 19:24:12 gsr-p-mz.112-8
3 1215 May 10 1997 20:30:52 myfile1
4 6176844 May 10 1997 23:04:10 gsr-p-mz.112-8.1
5 1186 May 10 1997 16:56:50 myfile2
9197156 bytes available (11381148 bytes used)
This completes the procedure for copying a configuration file from GRP DRAM to a Flash memory card.
Use the command copy [ slot0: | slot1: ]:filename startup-config for this copy procedure, where [slot0 | slot1 ]:filename is the source of the file (Flash memory card), and startup-config is the destination (NVRAM).
An example of the copy slot0:filename startup-config command follows:
Router# copy slot0:myfile startup-config
[ok]
Router#
Use the copy startup-config running-config command to ensure that the startup configuration file, now stored in NVRAM, is the default running configuration file used by the system as follows:
Router# copy startup-config running-config
Router#
%SYS-5-CONFIG_I: Configured from memory by console
Router#
This completes the procedure for copying a configuration file from the Flash memory card to NVRAM.
A locked block in Flash memory cards occurs when power is lost or a Flash memory card is unplugged during a write or erase operation. When a block of Flash memory is locked, it cannot be written to or erased, and the operation will consistently fail at a particular block location. The only way to recover from locked blocks is to reformat the Flash memory card with the format command.
| Caution Formatting a Flash memory card will cause existing data to be lost. |
After you have installed the Cisco 12012 hardware, checked all external connections, turned on the system power, allowed the system to boot up, and minimally configured the system, you might need to perform more complete and complex configurations that are beyond the scope of this text.
For specific information on more complex system and interface configuration, and, if necessary, troubleshooting, refer to the publications listed in the section "If You Need More Configuration Information."
The Cisco IOS software running the Cisco 12012 system contains extensive features and functionality. The effective use of many of many of these features is easier if you have more information at hand.
To obtain information about documentation, refer to the following:
|
|