Gigabit Route Processor Installation and Configuration Note
Available Languages
Table Of Contents
Gigabit Route Processor
Installation and Configuration NoteCisco IOS Software Requirements
Translated Safety Warnings and Agency Approvals
Electromagnetic Compatibility Regulatory Statements
Class A Notice for Taiwan and Other Traditional Chinese Markets
Preventing Electrostatic Discharge
Working with Electrical Equipment
Connecting to the Console Port
Connecting to the Auxiliary Port
Connecting to the Ethernet Port
Ethernet Interface Receptacles, Cables, and Pinouts
Ethernet Interface Cable Connection Procedure
Starting the System and Observing Initial Conditions
Configuring the Ethernet Interface
Using Configuration Mode to Configure the Ethernet Interface
Using the setup Command Facility to Configure the Ethernet Interface
Implementing Additional Configuration and Maintenance Tasks
Configuring the Software Configuration Register
Boot Field Settings and the boot Command
Changing Configuration Register Settings
Configuration Register Bit Meanings
Flash Disks and Flash Memory Cards in the GRP
Installing and Removing Flash Memory Card or Flash Disk in GRP
ATA Flash Disk Boot Image Support Requirements
Formatting a Flash Memory Card or Flash Disk
Specifying Cisco IOS Image Used to Boot the System
Software Commands Associated with Flash Memory
Enabling Booting from Flash Memory
Copying a Cisco IOS Software Image into Flash Memory Card or Flash Disk
Copying Cisco IOS Software Images Between Flash Memory Cards or Flash Disks
Copying System Configuration Files Between GRP Memory and a Flash Memory Card or Flash Disk
Recovering from Locked Blocks in Flash Memory Cards or Flash Disks
Checking the DIMM Installation
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Gigabit Route Processor
Installation and Configuration Note
Product Numbers: GRP-B=, GRP=
Document Order Number: DOC-784339=
This hardware installation and configuration note describes the Gigabit Route Processor (GRP), the route processor for use in Cisco 12000 Series Routers.
Document Contents
Following are the sections in this document:
•
Starting the System and Observing Initial Conditions
•
•
•
•
Important Information
This section contains information about the following hardware and software requirements:
•
Router Information
For hardware installation and maintenance information on Cisco 12000 Series Routers, refer to the installation and configuration guide for your router. This includes information on card slot locations and other general requirements.
Supported Platforms
The GRP operates on all Cisco 12000 series Internet Routers with the following requirements:
•
•
•
•
•
•
GRP Redundancy
When two GRPs are installed in a Cisco 12000 Series Router, one GRP is the active GRP, and the other is the backup, or standby GRP. If the active GRP fails or is removed from the system, the standby GRP detects the failure and initiates a switchover. During a switchover, the standby GRP assumes control of the router, connects with the network interfaces, and activates the local network management interface and system console.
Note
Cisco IOS Software Requirements
For software configuration information, refer to the Cisco IOS software configuration and command reference publications for the installed Cisco IOS Release. Also refer to the Cisco IOS software release notes for additional information.
The GRP line card is supported in Cisco IOS Release 11.2(9)GS and later. GRP configurations with
512 MB of route memory are only compatible with Product Number GRP-B=. Cisco IOS Release 12.0(19)S or 12.0(19)ST or later and ROMMON Release 11.2 (181) or later are also required.The show version and show hardware commands display the current hardware configuration of the router, including the system software version that is currently loaded and running.
For complete descriptions of show commands, see the Cisco IOS Configuration Fundamentals Configuration Guide and the Cisco IOS Configuration Fundamentals Command Reference.
Related Documentation
For additional information, refer to these publications:
•
•
•
•
Product Overview
Information about the Gigabit Route Processor (GRP), its components, functions, and features, and its use as the system processor for Cisco 12000 Series Routers is presented in the following sections. Figure 1 shows the front view of the GRP.
Figure 1 Gigabit Route Processor (Front Panel, Horizontal Orientation)
Note
and later) does not require shielded cables for Class B compliance.
GRP Functions
The primary functions of the GRP for Cisco 12000 Series Routers follow:
•
•
•
•
•
•
•
•
The MBus connection allows the GRP to download a system bootstrap image, collect or load diagnostic information, and perform general, internal system maintenance operations. The switch fabric connection is the main data path for routing table distribution as well as for packets that are sent between line cards and the GRP.
GRP Components
The GRP contains the following components:
•
200 MHz.•
Note
•
•
•
•
Cisco IOS Software
The Cisco IOS software images that run the Cisco 12000 Series Router system reside in Flash memory, which is located on the GRP in the form of a single in-line memory module (SIMM), and on up to two Flash cards (called Flash memory cards or Flash disks), which insert into the two slots (slot 0 and slot 1) on the front of the GRP. (See Figure 2.)
Note
Figure 2 GRP (Horizontal Orientation)
Note
Storing the Cisco IOS images in Flash memory enables you to download and boot from upgraded
Cisco IOS software images remotely or from software images that reside in GRP Flash memory.The Cisco 12000 Series Router system supports downloadable system software for most
Cisco IOS software upgrades, which enables you to remotely download, store, and boot from a new Cisco IOS software image. The Cisco IOS software runs from within GRP DRAM.For specific Cisco IOS software requirements for the GRP, see the "Cisco IOS Software Requirements" section.
Memory Components
Figure 2 shows the locations of the various types of memory used on the GRP. GRP memory component types are presented in the following sections:
•
•
Their functions are presented in Table 1.
Table 1 GRP Memory Components
DRAM
1 or 2
64-, 128-, or 256-MB DIMMs (based on the required DRAM configuration) for main Cisco IOS software functions (default configuration is 128 MB3 )
U39 (bank 1)
U42 (bank 2)SRAM4
512 KB (fixed)
—
SRAM for secondary CPU cache memory functions
—
NVRAM5
512 KB (fixed)
1
NVRAM for system configuration files
—
Flash memory
8 MB SIMM6
1
Contains Cisco IOS software images, system configuration files, and other user-defined files on the GRP
U17
—
Flash memory7
1 to 2
Contains Cisco IOS software images, system configuration files, and other user-defined files on up to two Flash memory cards or Flash disks8
Flash disk
slot 0 and
slot 1Flash boot ROM
512 KB
1
Flash EPROM for the ROM monitor program boot image
—
1 64 MB of DRAM serves as a replacement for any DRAM DIMM slot on a minimum configuration of 128 MB (both slots populated) for the GRP.
2 GRP route memory configurations of 512 MB are only compatible with Product Number GRP-B=. Cisco IOS Release 12.0(19)S or 12.0(19)ST or later and ROMMON Release 11.2 (181) or later are also required.
3 Default DRAM configuration is 128 MB. Bank 1 (U39) must be populated first. You can use one or both banks to configure DRAM up to 512 MB.
4 SRAM is not user configurable or field upgradeable.
5 NVRAM is not user configurable or field upgradeable.
6 SIMM socket is wired for Cisco's own design and does not accept industry-standard 80-pin Flash SIMMs.
7 Cisco IOS Release 12.0(17)S or 12.0(17)ST or later is required, along with the corresponding boot images, for the GRP to function with a Flash disk.
8 Linear Flash memory cards and ATA Flash disks can be used in either (or both) Flash card slot(s).
DRAM
DRAM stores routing tables, protocols, and network accounting applications, and runs the Cisco IOS software. The standard (default) GRP configuration is 128 MB of extended data output (EDO) DRAM, with up to 512 MB available through DIMM upgrades.
Note
Caution
The following DRAM upgrade kits for the GRP and line cards are listed by product number:
•
•
•
The following DRAM upgrade kits for Product Number GRP-B= are available (listed by product number):
•
•
These kits are available only for Product Number GRP-B=. They are not compatible with any other Cisco product. See Table 14 for all requirements related to the 512-MB memory upgrade.
Note
SRAM
SRAM provides secondary CPU cache memory. The standard GRP configuration is 512 KB. Its principal function is to act as a staging area for routing table updates information to and from the line cards. SRAM is not user configurable or field upgradeable.
NVRAM
System configuration files, software configuration register settings, and environmental monitoring logs are contained in the 512-KB NVRAM, which is backed up with built-in lithium batteries that retain the contents for a minimum of 5 years. NVRAM is not user configurable or field-upgradeable.
Flash Memory
Both the onboard and Flash card-based Flash memory allow you to remotely load and store multiple Cisco IOS software and microcode images. You can download a new image over the network or from a local server and then add the new image to Flash memory or replace the existing files. You can then boot the routers either manually or automatically from any of the stored images.
Flash memory also functions as a Trivial File Transfer Protocol (TFTP) server to allow other servers to boot remotely from stored images or to copy them into their own Flash memory. The onboard Flash memory (called bootflash) contains the Cisco IOS software boot image, and the Flash memory card or Flash disk contains the Cisco IOS software image.
System Status LEDs
The two types of system status LEDs used on the GRP.
Status LEDs
The GRP has the following eight status LEDs:
•
•
•
Display LEDs
The alphanumeric display LEDs are organized as two rows of four characters each. The display content is controlled by the MBus software of the GRP. Both rows of the display are powered by the MBus module.
These alphanumeric display LEDs provide system status messages that are displayed during the boot process and after the boot process is completed.
During the boot process, the display LEDs are controlled directly by the MBus. After the boot process, they are controlled by the Cisco IOS software (via the MBus), and display messages designated by the Cisco IOS software.
The LED displays indicate the following:
•
•
•
Soft Reset Switch
A soft reset switch provides a reset to the R5000 software on the GRP. You access the soft reset switch through a small opening in the GRP faceplate. To depress the switch, insert a pape rclip or a similar object into the opening.
Caution
Flash Card Slots
The GRP includes two Flash card slots. Either slot can support an ATA Flash disk or a linear Flash memory card.
Note
All combinations of different Flash card devices are supported by the GRP. You can use ATA Flash disks, linear Flash memory cards, or a combination of the two. Each slot has an ejector button for ejecting a card from the slot.
Note
Asynchronous Serial Ports
Two asynchronous serial ports on the GRP, the console and auxiliary ports, allow you to connect external serial devices to monitor and manage the system. The console port is an Electronic Industries Association/Telecommunications Industry Association (EIA/TIA)-232 receptacle (female) that provides a data circuit-terminating equipment (DCE) interface for connecting a console terminal.
Note
The auxiliary port is an EIA/TIA-232 plug (male) that provides a data terminal equipment (DTE) interface; the auxiliary port supports flow control and is often used to connect a modem, a channel service unit (CSU), or other optional equipment for Telnet management.
Ethernet Port
The GRP has one Ethernet port available, using one of the following connection types:
•
•
Note
The transmission speed of the Ethernet port is auto-sensing and is determined by the network to which the Ethernet interface is connected; it is not user configurable. At the auto-sensed data transmission rate of 100 Mbps, the Ethernet port provides maximum usable bandwidth that is less than 100 Mbps; a maximum usable bandwidth of approximately 20 Mbps can be expected if you use either the MII or RJ-45 connection.
Preparing for Installation
Installation preparation is presented in the following sections:
•
•
•
•
Safety Guidelines
Before you perform any procedure in this publication, review the safety guidelines in this section to avoid injuring yourself or damaging the equipment.
The following guidelines are for your safety and to protect the equipment. The guidelines do not include all hazards. Be alert.
Note
Cisco 12000 Series Internet Routers publication (Document Number 78-4347-xx) for your router before installing, configuring, or maintaining the GRP.
•
•
•
•
•
•
Translated Safety Warnings and Agency Approvals
The complete list of safety warnings and agency approvals for the PRP is available in the Regulatory Compliance and Safety Information for Cisco 12000 Series Internet Routers publication (Document Number 78-4347-xx).
Electromagnetic Compatibility Regulatory Statements
FCC Class A Compliance
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.
Modifying the equipment without Cisco's authorization may result in the equipment no longer complying with FCC requirements for Class A digital devices. In that event, your right to use the equipment may be limited by FCC regulation and you may be required to correct any interference to radio or television communication at your own expense.
You can determine whether your equipment is causing interference by turning it off. If the interference stops, it was probably caused by the Cisco equipment or one of its peripheral devices. If the equipment causes interference to radio or television reception, try to correct the interference by using one or more of the following measures:
•
•
•
•
CISPR 22
This apparatus complies with EN55022 Class B radiated and conducted emissions requirements.
Canada
English Statement of Compliance
This class A digital apparatus complies with Canadian ICES-003.
French Statement of Compliance
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.
Europe (EU)
This apparatus complies with EN55022 Class A and EN55024 standards when used as ITE/TTE equipment, and EN 300 386-2 (EN55022 class B with shielded CAT5 Ethernet cable, non-central office equipment) for Telecommunications Network Equipment (TNE).
Class A Notice for Hungary
Class A Notice for Taiwan and Other Traditional Chinese Markets
VCCI Class A Notice for Japan
Class A Notice for Korea
Preventing Electrostatic Discharge
Electrostatic discharge (ESD) damage, which can occur when electronic cards or components are improperly handled, results in complete or intermittent failures. Electromagnetic interference (EMI) shielding is an integral component of the GRP. Cisco recommends using a ESD-preventive strap whenever you are handling a router or one of its components.
Following are guidelines for preventing ESD damage:
•
•
•
•
Working with Electrical Equipment
Follow these basic guidelines when working with any electrical equipment:
•
•
•
•
•
Required Tools and Parts
You need the following tools and parts to remove and replace a GRP. If you need additional equipment, contact a Cisco customer service representative for ordering information.
•
•
•
Replacing a GRP
The following sections describe the procedures for replacing a GRP in your system.
Before beginning the procedures, verify that your system meets the minimum requirements as described in the "Preparing for Installation" section.
When your system meets minimum requirements, proceed to the "Removing a GRP" section for instructions on removing the GRP, and then to the "Installing a GRP" section for reinstallation instructions.
Caution
Removing a GRP
When you remove a GRP from a slot, be sure to use the ejector levers, which help to ensure that the GRP is fully dislodged from the backplane connector. (See Figure 3.)
Figure 3 GRP Ejector Levers, Captive Installation Screws, and Upper Card Cage Slots (Cisco 12012 Shown)
Caution
Caution
Figure 4 shows the ejector levers.
Figure 4 Ejector Levers and Captive Installation Screw (Cisco 12012 shown)
To remove a GRP, follow these steps:
Step 1
Step 2
Step 3
If you are replacing a GRP, disconnect any devices that are attached to the console or auxiliary ports. If you are removing a GRP for maintenance and will reinstall the same one, you can leave the devices attached, provided that doing so will not strain the cables.
Step 4
(See Figure 4a.)Step 5
Step 6
Caution
Step 7
Installing a GRP
When you install a GRP, be sure to use the ejector levers, which help to ensure that the GRP is fully inserted in the backplane connector. (See Figure 3.) When you simultaneously push the ejector levers inward (toward the center of the GRP), the ejector levers push the GRP into the slot and ensure that the GRP backplane connector is fully seated in the backplane.
Caution
Use the following procedure to install a GRP:
Step 1
Step 2
Caution
Step 3
Step 4
Step 5
(See Figure 4a.)Step 6
Step 7
Step 8
Step 9
Step 10
Connecting to the Console Port
The system console port on the GRP is a DCE DB-25 receptacle for connecting a data terminal, which you must configure. The console port is labeled Console, as shown in Figure 5. Before connecting the console port, check your terminal's documentation to determine the baud rate of the terminal you plan to use. The baud rate of the terminal must match the default baud rate (9600 baud). Set up the terminal as follows: 9600 baud, 8 data bits, no parity, and 2 stop bits (9600, 8N2). The console port requires a straight-through EIA/TIA-232 cable. Use the console cable provided to connect the terminal to the console port on the GRP.
Figure 5 Console and Auxiliary Port Connections
Note
The console port on the GRP is an EIA/TIA-232, DCE DB-25 receptacle. Both Data Set Ready (DSR) and Data Carrier Detect (DCD) signals are active when the system is running. The console port does not support modem control or hardware flow control. Table 2 lists the pinout for this port.
Connecting to the Auxiliary Port
The auxiliary port on the GRP is an EIA/TIA-232 DTE, DB-25 plug for connecting a modem or other DCE device (such as a CSU/DSU or another router) to the router. The port is labeled Auxiliary. An example of a modem connection is shown in Figure 5. The asynchronous auxiliary port supports hardware flow control and modem control. Table 3 lists the pinout for this port.
Connecting to the Ethernet Port
Information you need to make connections to the Ethernet port on your GRP is presented in the following sections:
•
•
Ethernet Interface Receptacles, Cables, and Pinouts
The two Ethernet interface receptacles on the GRP are a single media independent interface (MII), 40-pin, D-shell type receptacle, and a single RJ-45 receptacle. The RJ-45 receptacle provides a media dependent interface (MDI) Ethernet port. You can use either one or the other, but not both at the same time.
Each connection supports IEEE 802.3 and IEEE 802.3u interfaces compliant with the 10BASE-T and 100BASE-TX standards. The transmission speed of the Ethernet port is auto-sensing and is determined by the network to which the Ethernet interface is connected; transmission speed is not user configurable.
RJ-45 Connections
Figure 6 shows the GRP RJ-45 receptacle and cable connectors. The RJ-45 connection does not require an external transceiver. The RJ-45 connection requires Category 5 unshielded twisted-pair (UTP) cables, which are not available from Cisco Systems, but are available from commercial cable vendors. Table 4 lists the pinout for the RJ-45 receptacle.
Figure 6 RJ-45 Receptacle and Plug (Horizontal Orientation)
Warning
Table 4 RJ-45 Receptacle Pinout
1
TxD+
2
TxD-
3
RxD+
4
Termination Network
5
Termination Network
6
RxD-
7
Termination Network
8
Termination Network
Depending on your RJ-45 cabling requirements, use the cable pinouts shown in Figure 7 or Figure 8.
Figure 7 Straight-Through Cable Pinout (Connecting MDI Ethernet Port to MDI-X Wiring)
Figure 8 Crossover Cable Pinout (for Connecting Two GRPs)
MII Connections
The MII connection requires an external physical sublayer (PHY) and an external transceiver. Depending on the type of media you use between the MII connection on the GRP and your switch or hub, the network side of your 100BASE-T transceiver should be appropriately equipped—with SC-type or ST-type connectors (for optical fiber), BNC connectors, and so forth. Figure 9 shows the pin orientation of the female MII receptacle on GRP.
The MII receptacle uses two screw-type locks, called jackscrews (see Figure 9), to secure the cable or transceiver to the MII port. MII cables and transceivers have knurled thumbscrews (screws that you can tighten with your fingers) that you fasten to the jackscrews on the GRP's MII connector. Use the jackscrews to provide strain relief for your MII cable. (The RJ-45 modular plug has strain relief functionality incorporated into the design of its standard plastic connector.)
Figure 9 MII Receptacle (Horizontal Orientation)
Table 5 lists the MII connector pinout and signals. MII cables and transceivers are not available from Cisco Systems, but are available commercially.
Table 5 MII Receptacle Pinout
14 to 17
TxD
—
Yes
—
Transmit Data
12
Tx_CLK
Yes
—
—
Transmit Clock2
11
Tx_ER
—
Yes
—
Transmit Error
13
Tx_EN
—
Yes
—
Transmit Enable
3
MDC
—
Yes
—
MII Data Clock
4 to 7
RxD
Yes
—
—
Receive Data
9
Rx_CLK
Yes
—
—
Receive Clock
10
Rx_ER
Yes
—
—
Receive Error
8
Rx_DV
Yes
—
—
Receive Data Valid
18
COL
Yes
—
—
Collision
19
CRS
Yes
—
—
Carrier Sense
2
MDIO
—
—
Yes
MII Data Input/Output
22 to 39
GND
—
—
—
Common ground
1, 20, 21, 40
V
—
—
—
+5.0 VDC
1 Any pins not indicated are not used.
2 The signals Tx_CLK and Rx_CLK are generated by the external transceiver.
Table 6 lists the cabling specifications for 100-Mbps transmission over unshielded twisted-pair (UTP) and shielded twisted-pair (STP) cables.
Note
Table 6 Specifications and Connection Limits for 100-Mbps Transmission
Cable specification
Category 3, 4, or 5, 150-ohm UTP or STP, or multimode optical fiber
Cable length (max)
—
1.64 ft (0.5 m) (MII-to-MII cable4 )
Segment length (max)
328 feet (100 m) for 100BASE-TX
3.28 ft (1 m)5 or 1312 ft (400 m) for 100BASE-FX
Network length (max
656 feet (200 m)5 (with 1 repeater)
—
1 EIA/TIA-568 or EIA-TIA-568 TSB-36-compliant.
2 Cisco Systems does not supply Category 5 UTP RJ-45 or 150-ohm STP MII cables or MII transceivers; these items are available commercially.
3 AWG = American Wire Gauge. This gauge is specified by the EIA/TIA-568 standard.
4 This is the cable between the MII port on the GRP and the appropriate transceiver.
5 This length is specifically between any two stations on a repeated segment.
Table 7 lists IEEE 802.3u physical characteristics for 100BASE-TX.
Table 7 IEEE 802.3u Physical Characteristics
Data rate (Mbps)
100
Signaling method
Baseband
Maximum segment length
100 m between DTE1 and repeaters
Media
Category 5 UTP (for RJ-45) or MII
Topology
Star/Hub
1 DTE = data terminal equipment.
Ethernet Interface Cable Connection Procedure
The RJ-45 and MII receptacles on the GRP represent two physical connection options for one Ethernet interface; therefore, you can use either the RJ-45 connection or the MII connection, but not both simultaneously. RJ-45 and MII cables are not available from Cisco Systems; they are available from outside commercial cable vendors.
Use the following procedure to connect cables to the GRP's Ethernet interface:
•
•
The Ethernet interface on the GRP is an end station device, not a repeater; therefore, you must connect the Ethernet interface to a repeater or hub.
Figure 10 Connecting MII or RJ-45 Cables to GRP (Vertical Orientation)
Caution
Caution
Figure 11 shows an example of the functionality of the Ethernet port. In this example, you cannot access Network 2.0.0.0 via the Ethernet port (E0) on the GRP in Router A; you can only access the hosts and Router C, which are in Network 1.0.0.0. (See dotted arrows in Figure 11.)
To access Network 2.0.0.0 from Router A, you must use an interface port on one of your line cards (in this example, a Packet-over-SONET (POS) line card in Router A) to go through Router B, through Router C, and into Network 2.0.0.0. (See solid arrows in Figure 11.)
Figure 11 Using the Ethernet Port on the GRP
GRP Boot Process Overview
The following sequence describes a typical GRP boot process:
1.
2.
3.
4.
5.
6.
or
If the ROM monitor is not configured to autoboot, you must enter the appropriate b command at the ROM monitor prompt (rommon>) to boot the Cisco IOS software.7.
8.
Starting the System and Observing Initial Conditions
This section describes the initial system startup processes and procedures.
Use the following procedure to start your system:
Step 1
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. For both types of power supplies, the output fail LED should be off.
Step 2
Step 3
The 4-digit displays show system messages and displays a sequence similar to that shown in Table 8.
Figure 12 GRP Alphanumeric Display LEDs (Front Panel View)
Table 8 GRP Alphanumeric Display LED Sequences
MRAM
nnnnGRP 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
RPThis GRP is enabled and recognized by the system.
1 The version of microcode running on your GRP might be different.
Step 4
The system attempts to boot identical line cards in parallel. Furthermore, the system boots line cards as soon as they are powered on and become available for a system boot. (The physical location of the alphanumeric display LEDs on the line cards is the same as on the GRP, which is shown in Figure 12.)
Refer to the appropriate line card installation and configuration note for complete details on line card display LED sequences.
You must meet the following criteria to successfully boot the GRP:
•
•
•
The system automatically boots this Cisco IOS software image. The system then enters the setup facility, where you are prompted to perform a basic configuration of the system.
Otherwise, the system enters the ROM monitor and the appropriate prompt appears (rommon>).
Step 5
•
•
•
Caution
•
•
•
•
Caution
While the system boots, the console screen displays a script and system banner similar to the following:
Cisco Internetwork Operating System SoftwareIOS (tm) GS Software (GSR-P-MZ), Released Version 11.2(9)GSCopyright (c) 1986-1997 by cisco Systems, Inc.Compiled Sat 10-May-97 06:02aStep 6
On the console screen, after the system displays the system banner and hardware configuration, the following System Configuration Dialog prompt appears:
--- 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]:Step 7
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.
The interface-specific LEDs on line cards might not go on until after you configure the line card interfaces. In order to verify correct operation of each 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.
Verifying Interface Status
This section provides functional descriptions of the status LEDs on the GRP (see Figure 13) and the processes you should observe.
The status LEDs on the GRP indicate system and GRP status, which Flash memory card or Flash disk slot is active, which Ethernet connection is in use, and what is occurring on the Ethernet interface. (A successful boot is indicated by the alphanumeric display LEDs as shown in Table 8; however, this does not necessarily mean that the system has reached normal operation.)
The GRP has the following eight LED indicators:
•
•
•
Figure 13 GRP LEDs (Partial Front Panel View)
Configuring the Ethernet Interface
The IEEE 802.3 Ethernet interface, located on the GRP, allows connections to external Ethernet networks and is capable of data transmission rates of 10 Mbps and 100 Mbps. At the auto-sensed data transmission rate of 100 Mbps, the Ethernet port provides maximum usable bandwidth that is less than 100 Mbps; expect a maximum usable bandwidth of approximately 20 Mbps for either the MII or RJ-45 connection. Transmission speed, which is not user configurable, is determined by the network to which the Ethernet interface is connected.
The Ethernet interface does not provide external routing functions; it is primarily designed as a Telnet port into the GRP, and for booting and/or accessing Cisco IOS software images over a network to which the Ethernet interface is directly connected.
Caution
The following sections provide two methods for configuring the Ethernet interface.
•
•
Using Configuration Mode to Configure the Ethernet Interface
Use the following procedure to perform a basic configuration of the Ethernet interface in configuration mode:
Step 1
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#Step 2
Router(config)# interface ethernet 0Router(config-if)#Step 3
Router(config-if)# media-type typewhere type is RJ45 or MII. The system default is RJ45.
Step 4
Router(config-int)# ip address 1.1.1.10 255.255.255.0Step 5
Step 6
Router(config-int)# no shutdownStep 7
Step 8
Router# copy running-config startup-config[OK]Router#
Using the setup Command Facility to Configure the Ethernet Interface
In the following example of an Ethernet configuration using the setup command facility, the Ethernet interface is configured using IP and CLNS. (In this example, you want to use IP, CLNS, and the default RJ-45 Ethernet connection.)
Enter the setup facility using the setup command and respond to prompts as appropriate for your needs, using your own address and mask for the setup prompts.
(Additional displayed text omitted from this example.)Configuring interface Ethernet0:Is this interface in use?: yesConfigure IP on this interface?: yesIP address for this interface: 3.3.1.1Number of bits in subnet field: 8Class A network is 3.0.0.0, 8 subnet bits; mask is 255.255.0.0Configure CLNS on this interface?: yesImplementing Additional Configuration and Maintenance Tasks
This section contains information on the following additional configuration, troubleshooting, and maintenance tasks:
•
•
Configuring the Software Configuration Register
The 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 non-volatile random access memory (NVRAM).
Following are some reasons for changing the software configuration register settings:
•
•
•
•
•
•
•
•
•
Table 9 provides descriptions of each of the software configuration memory bits, and Table 10 defines the boot field, specified as a binary number that consists of bits 0 through 3 of the software configuration register.
Caution
Table 9 Software Configuration Register Bit Descriptions
00 to 03
0x0000 to 0x000F
Boot field (see Table 10)
06
0x0040
System software ignores NVRAM contents
07
0x0080
OEM2 bit enabled
08
0x0100
Break disabled
09
0x0200
Use secondary bootstrap
10
0x0400
IP3 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 without network numbers
15
0x8000
Enable diagnostic messages and ignore NVRAM contents
1 The factory default value for the configuration register is 0x2102. This value is a combination of the following: binary bit 8 = 0x0100 and binary bits 00 through 03 = 0x0002 (see Table 10).
2 OEM = original equipment manufacturer
3 IP = Internet Protocol
Boot Field Settings and the boot Command
Bits 0 through 3 of the software configuration register form the boot field, specified as a binary number.
Note
Boot field—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:
•
or•
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 or Flash disks 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 format cisco<bootfieldvalue>-<processorname>; for example, cisco2-GRP. The system uses this filename to invoke the system image by booting over the network. 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.
Note
You must set the boot field for the boot functions you require.
Changing Configuration Register Settings
Use the following procedure to change the configuration register while running the system software:
Step 1
Router> enablePassword:Router#Step 2
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#Step 3
Router(config)# config-register 0xvalueStep 4
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
The value is displayed on the last line of the screen display, as in the following example:
Configuration register is 0x141 (will be 0x2102 at next reload)Step 6
Configuration register changes take effect only after the system reloads, such as when you issue a reload command from the console.
Step 7
Configuration Register Bit Meanings
The lowest four bits of the software configuration register (bits 3, 2, 1, and 0) form the boot field. (See Table 10.) 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, theCisco 12000 Series Router boots the system software as directed by that value. If there is no boot system command, the Cisco 12000 Series Router forms a default boot filename for booting from a network server. (See Table 11 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 0x2102Router(config)# boot system flash [filename]Crtl-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 11 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.
Note
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, which forces the system into the bootstrap (or ROM) monitor, thereby halting normal operation. Regardless of the setting of the break enable bit, a break causes a return to the ROM monitor during the first few seconds (approximately 5 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 12 shows the combined effect of bits 10 and 14.
Table 12 Configuration Register Settings for Broadcast Address Destination
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 13 shows the bit settings for the four available rates. (The factory-set default data transmission rate is 9600.)
Table 13 System Console Terminal Transmission Rate Settings
9600
0
0
4800
0
1
2400
1
1
1200
1
0
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.
Flash Disks and Flash Memory Cards in the GRP
Procedures for using Flash memory cards or Flash disks in the GRP and information on the Flash memory functions are presented in the following sections:
•
•
•
•
•
•
•
•
•
•
•
Installing and Removing Flash Memory Card or Flash Disk in GRP
The GRP has two Flash Card slots (slot 0 and slot 1), into which you can install a linear Flash memory card or an ATA Flash disk. The slots are positioned with slot 0 on the left and slot 1 on the right. (See Figure 14.)
Figure 14 Installing and Removing Flash Memory Card or Flash Disk
Both slots can be used at the same time. Use the following procedure to install a Flash memory card or Flash disk:
Step 1
Note
Step 2
Caution
Use the following procedure to remove a Flash memory card or Flash disk:
Step 1
Step 2
Notes About ATA Flash Disks
Note the following issues when using an ATA Flash disk with Cisco IOS Releases prior to 12.0(22)S:
•
•
•
Cisco IOS Release 12.0(22)S or later.ATA Flash Disk Boot Image Support Requirements
A boot image that supports the ATA file system must reside in bootflash. To enable booting from a Flash disk, set the configuration register bits to 0x2102 and add a boot system command to the configuration as follows:
Router(config)# config-reg 0x2102Router(config)#^ZRouter#write memRouter# configure terminalEnter configuration commands, one per line. End with CTRL-Z.Router(config)# boot system disk0:gsr-p-mz.120-19.S
Note
Formatting a Flash Memory Card or Flash Disk
The Flash memory card or Flash disk 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 or Flash disk and copy images or backup configuration files onto it. Before you can use a new Flash memory card or Flash disk, you must format it.
Note
Caution
To format a new Flash memory card or Flash disk, follow these steps:
Note
Step 1
Step 2
Router# format slot0:All sectors will be erased, proceed? [confirm]Enter volume id (up to 30 characters): NewCardFormatting sector 1Format device slot0 completedRouter#
Note
The new Flash memory card or Flash disk is now formatted and ready to use.
For complete command descriptions and configuration information, refer to the Configuration Fundamentals Command Reference, the Configuration Fundamentals Configuration Guide, and the Cisco 12000 Series Internet Router Flash Disk Information publications. (For information on obtaining these publications, see the "Obtaining Documentation" section.)
Specifying Cisco IOS Image Used to Boot the System
Use the following series of commands to specify that a Cisco IOS software image is bootable. (In this example, the file is named new.image.) Note that because 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 0x102Crtl-zRouter# copy running-config startup-configRouter# reloadWhen the system reloads, it will boot the Cisco IOS software image from the Flash memory card or
Flash disk in slot 0.
Note
Software Commands Associated with Flash Memory
Following are software commands related to the onboard Flash memory on the GRP and the Flash memory cards and Flash disks.
Note
Determine which memory media you are accessing using the pwd command as follows:
Router# pwdslot0Move between Flash memory media using the cd device-name command, where device-name can be slot1:, slot0:, or bootflash:. Examples follow:
Router# cd slot1:Router# pwdslot1Router# cd slot0:Router# pwdslot0You 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------ name1 4601977 May 10 1997 09:42:19 myfile16 679 May 10 1997 05:43:56 todays-config7 1 May 10 1997 09:54:53 fun1You 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 or Flash disk in slot 0 follows:
Router# delete fun1Router# dir-#- -length- -----date/time------ name1 4601977 May 10 1997 09:42:19 myfile16 679 May 10 1997 05:43:56 todays-configFiles that are deleted are marked as deleted, but still occupy space in Flash memory. The command squeeze device-name (where device-name can be slot0:, slot1:, or bootflash:) removes them permanently and pushes all other undeleted files together to eliminate spaces between them.
Note
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]ebESZTo prevent loss of data from sudden power loss, the "squeezed" data is temporarily saved to another location of Flash memory, which is specially used by the system.
The meanings of the characters in the preceding command display output as follows:
•
•
•
•
•
The squeeze command operation keeps a log of which of these functions was performed, so that in case of sudden power failure, it can return to the correct place and continue with the process.
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, then 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 and reference publications.
Enabling Booting from Flash Memory
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-name:filename configuration command, where device-name is bootflash:, slot0:, or slot1: (Flash memory cards), and bootflash:, disk0:, or disk 1: (ATA Flash disk cards) and filename is the name of the file from which you want to boot the system.
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 CTRL-Z.Router(config)#config-reg 0x2102Router(config)#boot system disk0:gsr-p-mz.120-17.SRouter(config)#^ZRouter#copy running-config startup-configCopying Files to Flash Memory
Copying a new Cisco IOS software image to Flash memory might be required whenever a new Cisco IOS software release or maintenance release becomes available. Copying a system configuration file might also be required if you want to keep a backup copy of it. Use the information in this section to copy any type of file to Flash memory.
Caution
Note
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 or Flash disks.
An example of the copy tftp:filename command follows:
Router# copy tftp:myfile1 slot0:myfile120575008 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]CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCRouter#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 or Flash disk.
Copying a Cisco IOS Software Image into Flash Memory Card or Flash Disk
You can copy a Cisco IOS software image into Flash memory; however, you must first format the Flash memory card or Flash disk and make the image in the Flash memory card or Flash disk bootable. (If you have not already done this, see the "Formatting a Flash Memory Card or Flash Disk" section and the "Specifying Cisco IOS Image Used to Boot the System" section.)
Note
Before you copy a Cisco IOS software image, you must do the following:
•
•
•
•
Use the following procedure to copy a bootable image into the Flash memory card or Flash disk:
Step 1
Step 2
Router> enablePassword:Router# copy tftp:new.image slot0:new.image20575008 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]CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCRouter#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 or Flash disk. You must now reboot the system.
Copying Cisco IOS Software Images Between Flash Memory Cards or Flash Disks
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 or Flash disk.
The following scenario describes how to use a newly released Cisco IOS software image on a Flash memory card or Flash disk in a system that has an older image on a Flash memory card or Flash disk 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 or Flash disk onto the Flash memory card or Flash disk that contains the old Cisco IOS software image.
Note
If, after you delete files and use the squeeze command, the two files cannot coexist on the Flash memory card or Flash disk in slot 0, remove this card (place it in an antistatic bag and store it in a safe place), and insert the new Flash memory card or Flash disk (with the file image.new) in slot 0. Proceed to Step 5 in the following procedure and use the command boot system flash slot0:image.new to designate the file image.new as the default boot Cisco IOS software image.
Note
Use the following procedure to copy bootable Cisco IOS software images between Flash memory cards or Flash disks:
Step 1
Step 2
Router> enablePassword:Router#Step 3
Step 4
Router# copy slot1:image.new slot0:image.newYou can also enter the previous command as copy slot1:image.new slot0:.
Step 5
Router# config tRouter(config)# no boot systemRouter(config)# boot system flash slot0:image.newCrtl-zRouter# copy running-config startup-configRouter# reloadWhen the system reloads, it will boot the file image.new from the Flash memory card or Flash disk in slot 0.
Copying System Configuration Files Between GRP Memory and a Flash Memory Card or Flash Disk
Copying a configuration file to a Flash memory card or Flash disk in PCMCIA slot 0 or slot 1 might be required if you do not have access to a TFTP server on which you can temporarily store your configuration file. You can then copy the configuration file back to NVRAM at any time. You can copy your startup configuration file (from NVRAM) or your running configuration file (from DRAM).
Use the procedures in the following sections to first copy the configuration file from either NVRAM or DRAM to a Flash memory card or Flash disk, and then to copy the configuration file from a Flash memory card or Flash disk back to NVRAM.
Note
Copying Configuration File from GRP NVRAM to Flash Memory Card or Flash Disk
You can use the command copy startup-config [slot0: | slot1:]filename for the copy procedure, where startup-config is the file's source (NVRAM), and [slot0: | slot1:]filename is the file's destination in either of the Flash memory cards or Flash disks. Note that the environmental variable CONFIG_FILE must be pointing (set) to NVRAM, which is the system default.
Note
Use the following procedure to copy a configuration file from GRP NVRAM to a Flash memory card or Flash disk:
Step 1
Router# show boot(display text omitted)CONFIG_FILE variable =Current CONFIG_FILE variable =(display text omitted)The preceding example shows that the environmental variable CONFIG_FILE is set for NVRAM, by default.
Step 2
Router# copy startup-config slot0:myfile220575008 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]CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCRouter#
Note
You can also copy the running configuration (located in DRAM) to a Flash memory card or Flash disk, as shown in the "Copying Configuration File from GRP DRAM to Flash Memory Card or Flash Disk" section.
Step 3
Router# dir slot0:-#- -length- -----date/time------ name1 5200084 May 10 1997 19:24:12 gsr-p-mz.112-83 1215 May 10 1997 20:30:52 myfile14 6176844 May 10 1997 23:04:10 gsr-p-mz.112-8.15 1186 May 10 1997 16:56:50 myfile29197156 bytes available (11381148 bytes used)Router#
Copying Configuration File from GRP DRAM to Flash Memory Card or Flash Disk
Following is an example of copying your running configuration file from GRP DRAM to a Flash memory card or Flash disk in PCMCIA slot 0 or slot 1.
Note
You can use the command copy running-config [slot0: | slot1:]filename (Flash memory card), or copy running-config [disk0: | disk1:]filename (Flash disks) 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 or Flash disks.
Step 1
Router# copy running-config slot0:myfile220575008 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]Router#In the preceding example, the exclamation points (!!!) appear as the file is copied.
Step 2
Router# dir slot0:-#- -length- -----date/time------ name1 5200084 May 10 1997 19:24:12 gsr-p-mz.112-83 1215 May 10 1997 20:30:52 myfile14 6176844 May 10 1997 23:04:10 gsr-p-mz.112-8.15 1186 May 10 1997 16:56:50 myfile29197156 bytes available (11381148 bytes used)
Copying Configuration File from Flash Memory Card or Flash Disk to GRP NVRAM
Following is an example of copying your startup configuration file from a Flash memory card or Flash disk in PCMCIA slot 0 or slot 1 back to NVRAM.
•
•
Step 1
Router# copy slot0:myfile startup-config[ok]Router#Step 2
Router# copy startup-config running-configRouter#%SYS-5-CONFIG_I: Configured from memory by consoleRouter#
Recovering from Locked Blocks in Flash Memory Cards or Flash Disks
A locked block in Flash memory cards or Flash disks occurs when power is lost, or a Flash memory card or Flash disk 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 or Flash disk with the format command. (See the "Formatting a Flash Memory Card or Flash Disk" section.)
Caution
Recovering Lost Password
This section provides information on how to recover a lost password.
The following overview describes this process:
1.
2.
3.
Note
4.
5.
6.
Use the following procedure to recover a lost password.
Note
Step 1
Step 2
Step 3
Step 4
Step 5
rommon 1>Step 6
rommon 1> confregConfiguration Summaryenabled are:console baud: 9600boot: image specified by the boot system commandor default to: cisco2-GRPdo you wish to change the configuration? y/n [n]: yenable "diagnostic mode"? y/n [n]:enable "use net in IP bcast address"? y/n [n]:enable "load rom after netbootfails"? y/n [n]:enable "use all zero broadcast"? y/n [n]:enable "break/abort has effect?" y/n [n]:enable "ignore system config info?" [n]: ychange console baud rate? y/n [n]:change boot characteristics? y/n [n]Configuration Summaryenabled are:console baud: 9600boot: image specified by the boot system commandor default to: cisco2-GRPDo you wish to change the configuration? y/n [n]You must reset or power cycle for the new config to take effectStep 7
rommon 1> iThe router power cycles, the configuration register is set to ignore the configuration file, and the router boots the boot system image and prompts you with the system configuration dialog as follows:
--- System Configuration Dialog ---Step 8
Press RETURN to get started!Step 9
After some interface information displays, the prompt appears as follows:
Router>Step 10
The prompt changes to the following:
Router#Step 11
Step 12
You are prompted as follows:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#Change the configuration register value back to its original value (noted from Step 3.)
Change it to a value of 0x2102 (factory default) using the config-register 0x value command.
Step 13
Step 14
Upgrading GRP Memory
This section provides the procedure for increasing the amount of extended data output (EDO) DRAM on a GRP by replacing up to two dual in-line memory modules (DIMMs). The system DRAM resides on up to two DIMMs on the GRP. The DRAM DIMM sockets are U39 (bank 1) and U42 (bank 2). (See Figure 15 and Table 14.)
The default DRAM configuration is 128 MB (one 128-MB DIMM in U39).
Note
Figure 15 Locations of GRP Memory Components
Note
Before proceeding, ensure that you have the proper tools and ESD-prevention equipment available. To upgrade DRAM, you will install DIMMs in one or two banks (U39 and U42). Table 14 lists the various available configurations of DRAM DIMMs, the number of DIMMs for each configuration, and the DRAM banks they occupy. Note which banks you should use, given the combinations of available DIMM sizes and the maximum DRAM you require.
Note
Table 14 GRP Memory Options
64 MB
MEM-GRP/LC-64=2
1 64-MB DIMM
U39 or U42
128 MB
MEM-GRP/LC-128=
1 128-MB DIMM
U39
256 MB
MEM-GRP/LC-256=3
2 128-MB DIMMs
U39 and U42
256 MB
MEM-GRP-256=4
1 256-MB DIMM
U39
512 MB
MEM-GRP-512=5
2 256-MB DIMMs
U39 and U42
1 Do not mix memory sizes. If installing 2 DIMMs, both DIMMs must be the same size.
2 For GRPs equipped with 64 MB, this option adds a second 64-MB DIMM for a total of 128 MB.
3 This product is no longer available. Replace it with Cisco Product Number MEM-GRP-256.
4 Only compatible with Product Number GRP-B=.
5 GRP route memory configurations of 512-MB are only compatible with Product Number GRP-B=. In addition, Cisco IOS Release 12.0(19)S or 12.0(19)ST or later and ROMMON Release 11.2 (181) or later are also required.
Note
Caution
Removing DIMMs
This section provides the procedure for removing DIMMs. As you remove DIMMs, place them on an antistatic mat or store them in an antistatic bag. You can use the DIMMs that you remove in other compatible equipment.
Caution
Use the following procedure to remove the existing DIMM(s):
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Figure 16 Using DIMM Socket Release Lever to Remove DIMMs
Step 8
Step 9
Step 10
Installing New DIMMs
This section provides the procedure for installing new DIMMs.
Caution
Caution
Figure 17 Handling a DIMM
Use the following procedure to install the new DIMMs:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Note the two notches (keys) on the connector edge of the DIMM. (See Figure 17.) These keys are intended to ensure correct orientation of the DIMM in the socket.
Step 7
Step 8
Caution
Step 9
Checking the DIMM Installation
After you install the new DIMMs and replace the GRP, turn on system power and allow the system to reboot.
Note
If the system fails to boot properly, or if the console terminal displays a checksum or memory error, check the following:
•
•
If after several attempts the system fails to restart properly, contact a service representative for assistance. Before you call, make note of any error messages, unusual LED states, or any other indications that might help solve the problem.
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
International Cisco websites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
Documentation Feedback
You can submit e-mail comments about technical documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.
Cisco TAC Website
The Cisco TAC website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year. The Cisco TAC website is located at this URL:
Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:
http://tools.cisco.com/RPF/register/register.do
Opening a TAC Case
Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:
http://www.cisco.com/tac/caseopen
For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.
To open a case by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete listing of Cisco TAC contacts, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
TAC Case Priority Definitions
To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.
Priority 1 (P1)—Your network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/go/marketplace/
•
http://cisco.com/univercd/cc/td/doc/pcat/
•
•
•
http://www.cisco.com/go/iqmagazine
•
•
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the installation and configuration guide for your Cisco 12000 Series Router.
Copyright © 2004 Cisco Systems, Inc. All rights reserved.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)