Gigabit Route Processor Installation and Configuration

This configuration note describes the Gigabit Route Processor (GRP), which is used in the Cisco 12000 series of Gigabit Switch Routers (GSRs), and serves as the main system processor for the GSRs.

Document Contents

Following are the sections in this document:

The Cisco IOS software running your router contains extensive features and functionality that is documented in supporting publications. For additional information on configuring and maintaining the Cisco 12000 series routers and the GRP.

Cisco documentation and additional literature are available in a CD-ROM package that ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more up to date than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a one time package or through an annual subscription.
Refer to the following modular configuration and modular command reference publications, as appropriate for your configuration:
- Configuration Fundamentals Configuration Guide
- Configuration Fundamentals Command Reference
- Wide-Area Networking Configuration Guide
- Wide-Area Networking Command Reference
- Network Protocols Configuration Guide, Parts 1, 2, and 3
- Network Protocols Command Reference, Parts 1, 2, and 3
- Configuration Builder Getting Started Guide
- Troubleshooting Internetworking Systems
- Debug Command Reference
- System Error Messages
- Cisco IOS Software Command Summary
- Cisco Management Information Base (MIB) User Quick Reference
For hardware installation and maintenance information on the Cisco 12000 series routers, refer to the specific installation and configuration guide that shipped with your router.
For specific Cisco IOS software release information, refer to the Cisco IOS software release note for the software release you are running. (For the Cisco IOS software release that supports the GRP, refer to the section "Software Prerequisites" on page 9.)
To obtain general information about documentation, refer to the following sources:
- "Cisco Connection Online," on page 54.
- Cisco Systems Customer Service at 800 553-6387 or 408 526-7208. Customer Service hours are 5:00 a.m. to 6:00 p.m. Pacific time, Monday through Friday (excluding company holidays). You can also send e-mail to cs-rep@cisco.com.
- Cisco Information Packet that shipped with your router.

GRP Overview

Information about the Gigabit Route Processor (GRP) (see Figure 1), its components, functions and features, and its use as the main system processor for the Cisco 12000 series routers is presented in the following sections.

Product overview:

Figure 1: Gigabit Route Processor (Front Panel, Horizontal Orientation)

The GRP is available as Product Number GRP-B=, which includes one GRP, with 128 MB of DRAM (default configuration), and one 20-MB Flash memory card.

The primary functions of the GRP for Cisco 12000 series routers follow:

Loading the Cisco IOS software to all of the installed line cards at power up
Providing a console (terminal) port for router configuration
Providing an auxiliary port for other external equipment (such as modems)
Providing an IEEE 802.3, 10/100-megabits-per-second (Mbps) Ethernet port for Telnet functionality
Running routing protocols
Building and distributing routing tables to the line cards
Providing general system maintenance functions
Communicating with the line cards either through the switch fabric or through the maintenance bus (MBus)

: 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.

Cisco 12016---GRP plugs into slot 7 in the upper card cage, which has a different spacing than the other card slots. If the router is equipped with an optional, redundant GRP, it must be installed in the far left slot of the lower card cage (slot 8). If the router is not equipped with an optional, redundant GRP, a line card can be installed in slot 8 of the lower card cage.
Cisco 12012---GRP plugs into slot 0 in the upper card cage. In a dual GRP system, the second GRP is located in slot 11. This is the default factory configuration and is recommended to avoid heat related problems. The far right slot labeled Alarm card is reserved for the alarm card and is .
Cisco 12008---GRP plugs into any slot in the upper card cage in the Cisco 12008 except the middle two slots (which are reserved for the CSC cards and labeled CSC 0 and CSC 1).

The GRP contains the following components:

RISC processor---IDT R5000 Reduced Instruction Set Computing (RISC) processor used for the CPU. The CPU runs at an external bus clock speed of 100 MHz and an internal clock speed of 200 MHz.
DRAMM---Up to 256 megabytes (MB) of parity-protected, extended data output (EDO) dynamic random-access memory (DRAM) on two, 60-nanosecond (ns), dual in-line memory modules (DIMMs). 128 MB of DRAM is the minimum shipping configuration for the GRP.
SRAM---512 kilobytes (KB) of static random-access memory (SRAM) for secondary CPU cache memory functions. (SRAM is not user configurable or field upgradeable.)
NVRAM---512 KB of nonvolatile RAM (NVRAM). (NVRAM is not user configurable or field upgradeable.)
Memory---Most of the additional memory components used by the system, including onboard Flash memory and up to two Personal Computer Memory Card International Association (PCMCIA)-based Flash memory cards.
Sensors---Air-temperature sensors for environmental monitoring.

The Cisco IOS software images that run the Cisco 12000 series 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 PCMCIA cards (called Flash memory cards), which insert in the two PCMCIA slots (slot 0 and slot 1) on the front of the GRP. (See Figure 2.)

Note The onboard Flash memory (called bootflash) contains the Cisco IOS software boot image, and a Flash memory card contains the Cisco IOS software image.

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 reside in GRP Flash memory.

The Cisco 12000 series 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.

Note For specific Cisco IOS software requirements for the GRP, refer to the section "Software Prerequisites" on page 9.

Memory Components

GRP Memory component types are presented in Figure 2, GRP (Horizontal Orientation). Their functions are presented in Table 1, GRP Memory Components.

Figure 2: GRP (Horizontal Orientation)

Type	Size	Quantity	Description	Location
DRAM	64¹ to 256 MB	1 or 2	64- or 128 MB DIMMs (based on the required DRAM configuration) for main Cisco IOS software functions (default configuration is 128 MB²)	U39 (bank 1) U42 (bank 2)
SRAM³	512 KB (fixed)	---	SRAM for secondary CPU cache memory functions	---
NVRAM⁴	512 KB (fixed)	1	NVRAM for system configuration files	---
Flash memory	8 MB SIMM⁵	1	Contains Cisco IOS software images, system configuration files, and other user-defined files on the GRP	U17
	20⁶ MB PCMCIA-based	1 to 2	Contains Cisco IOS software images, system configuration files, and other user-defined files on up to two PCMCIA-based Flash memory cards⁷	PCMCIA slot 0 and slot 1
Flash boot ROM	512 KB	1	Flash EPROM for the ROM monitor program boot image	---

Table 1: GRP Memory Components

Type Size Quantity Description Location

DRAM

64¹ to 256 MB

1 or 2

64- or 128 MB DIMMs (based on the required DRAM configuration) for main Cisco IOS software functions (default configuration is
128 MB²)

U39 (bank 1)
U42 (bank 2)

SRAM³

512 KB (fixed)

---

SRAM for secondary CPU cache memory functions

---

NVRAM⁴

512 KB (fixed)

1

NVRAM for system configuration files

---

Flash memory

8 MB SIMM⁵

1

Contains Cisco IOS software images, system configuration files, and other user-defined files on the GRP

U17

20⁶ MB PCMCIA-based

1 to 2

Contains Cisco IOS software images, system configuration files, and other user-defined files on up to two PCMCIA-based Flash memory cards⁷

PCMCIA slot 0
and slot 1

Flash boot ROM

512 KB

1

Flash EPROM for the ROM monitor program boot image

---

¹ 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.
² Default DRAM configuration is 128 MB. Bank 1 (U39) must be populated first; user can use a one or both banks to configure DRAM up 256 MB.
³SRAM is not user configurable or field upgradeable.
⁴NVRAM is not user configurable or field upgradeable.
⁵SIMM socket is wired for Cisco's own design and does not accept industry-standard 80-pin Flash SIMMs.
⁶20-MB Flash memory card is the default shipping configuration.
⁷Type 1 and Type 2 PCMCIA cards can be used in either PCMCIA slot. Refer to Table 2 for specific, allowable PCMCIA card configurations.

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 256 MB available through DIMM upgrades.

Caution To prevent memory problems, DRAM DIMMs must be +3.3 VDC, 60-nanosecond (ns) EDO devices. Do not attempt to install other devices in the DIMM sockets. We recommend you use Cisco-approved memory options. (Refer to Table 16 in the section "Upgrading GRP Memory.")

The following DRAM upgrade kits for GRP and line cards are available (listed by product number):

64-MB DRAM upgrade kit (one 64-MB DIMM)---MEM-GRP/LC-64=
128-MB DRAM upgrade kit (one 128-MB DIMM)---MEM-GRP/LC-128=
256-MB DRAM upgrade kit (two 128-MB DIMMs)---MEM-GRP/LC-256=

Note MEM-GRP/LC-64= can be used to replace bank 1 or bank 2 in the 128-MB default configuration on the GRP line card. Cisco does not recommend using a 64-MB configuration on this card.

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 PCMCIA 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 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 contains the Cisco IOS software image. A Flash memory card is available as Product Number MEM-GRP-FL20=, which is a 20-MB PCMCIA Flash memory card that ships as a spare or as a part of a Cisco 12000 series system.

System Status LEDs

The two types of system status LEDs used on the GRP.

LED Indicators

The GRP has the following eight LED indicators:

2 PCMCIA activity LEDs (one LED per PCMCIA slot)---Each LED goes on when its PCMCIA slot is accessed. The LEDs receive power from the switched slot voltage.
4 RJ-45 Ethernet port LEDs---These LEDs are used in conjunction with the RJ-45 Ethernet connector. When the MII Ethernet port is in use, the LEDs are disabled. The LEDs indicate link activity (LINK), collision detection (COLL), data transmission (TX), and data reception (RX).
2 RJ-45 or MII Ethernet port selection LEDs---These two LEDs, when on, identify which of the two Ethernet connections you selected. When the RJ-45 port is selected, its LED is on, and the MII LED is off. When the MII port is selected, its LED is on, and the RJ-45 LED is off.

Alphanumeric LED Displays

The alphanumeric LED displays are organized as two rows of four characters each. The display content is controlled by the GRP's MBus module software. Both rows of the display are powered by the MBus module.

These alphanumeric LED displays provide system status messages that are displayed during the boot process and after the boot process is completed.

During the boot process, the alphanumeric LED displays 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:

Status of the GRP
System error messages
User-defined status/error messages

Soft Reset Switch

A soft reset switch provides a reset to the R5000's software on the GRP. You access the soft reset switch through a small opening in the GRP's faceplate. To depress the switch, you must insert a paperclip or a similar sharp pointed object into the opening.

Caution To prevent system problems or loss of data, use the soft reset switch only at the advice of Cisco service personnel.

PCMCIA Slots

The GRP has two PCMCIA slots available. Either slot can support a Flash memory card or an input/output (I/O) device as long as the PCMCIA device requires only +5 VDC.

Note The GRP does not support +3.3 VDC PCMCIA devices.

Specific combinations of different PCMCIA cards are supported by the GRP. (See Table 2.) Each PCMCIA slot has an ejector button for ejecting a PCMCIA card from the slot.

PCMCIA Slot 0 (Left Side)	PCMCIA Slot 1 (Right Side)
Type 1 or 2	Empty
Empty	Type 1 or 2
Type 1 or 2	Type 1 or 2

Table 2:

PCMCIA Slot 0 (Left Side) PCMCIA Slot 1 (Right Side)

Type 1 or 2

Empty

Empty

Type 1 or 2

Type 1 or 2

Type 1 or 2

PCMCIA Devices (with GRP Oriented Vertically)

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 EIA/TIA-232 was formerly RS-232.

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 two connection types:

RJ-45 receptacle--- 8-pin RJ-45 receptacle for either IEEE 802.3 10Base-T (10 Mbps) or IEEE 802.3u 100Base-TX (100 Mbps) connections.
MII receptacle---40-pin media independent interface (MII) receptacle that provides additional flexibility in Ethernet connections. The pinout of this standard 40-pin receptacle is defined by the IEEE 802.3u standard.

Note 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.

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.

Installation Prerequisites

We recommend that you do the following before beginning any of the procedures in this document:

Review electrical and telephonic safety and ESD-prevention guidelines to help you to avoid injury or damage to the equipment.
Ensure that your equipment configuration meets the minimum requirements for the upgrade or replacement you will perform, and that you have all the parts and tools you need.
If you plan to replace a GRP, back up your current configuration file to a remote server or Flash memory before you remove the GRP, to avoid having to reenter all your current configuration information manually. To back up the file, copy your configuration file to a Flash memory card or access a remote server. (For instructions on copying files to a Flash memory card, refer to the section "Copying Files to Flash Memory" on page 39.)
Do not install more than one GRP in the system.

Software Prerequisites

The GRP line card is initially supported in Cisco IOS Release 11.2(9)GS. See Cisco IOS release notes for more information.

You can use the show version and show hardware commands to display the current hardware configuration of the router, including the system software release that is currently loaded and running.

For complete descriptions of show commands, refer to the Configuration Fundamentals Configuration Guide and Configuration Fundamentals Command Reference publications, which are available on the Documentation CD-ROM or as printed copies.

If the displays indicate that the required system software is not available in your system, refer to the section "Cisco Connection Online" at the end of this configuration note for information on contacting customer service.

Safety Guidelines

The following sections provide safety guidelines you should follow when working with any equipment that connects to electrical power or telephone wiring.

Safety Warnings

Safety warnings appear throughout this publication in procedures that, if performed incorrectly, may harm you. A warning symbol precedes each warning statement.

Warning This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. To see translations of the warnings that appear in this publication, refer to the Regulatory Compliance and Safety Information document that accompanied this device.

Waarschuwing Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die lichamelijk letsel kan veroorzaken. Voordat u aan enige apparatuur gaat werken, dient u zich bewust te zijn van de bij elektrische schakelingen betrokken risico's en dient u op de hoogte te zijn van standaard maatregelen om ongelukken te voorkomen. Voor vertalingen van de waarschuwingen die in deze publicatie verschijnen, kunt u het document Regulatory Compliance and Safety Information (Informatie over naleving van veiligheids- en andere voorschriften) raadplegen dat bij dit toestel is ingesloten.

Varoitus Tämä varoitusmerkki merkitsee vaaraa. Olet tilanteessa, joka voi johtaa ruumiinvammaan. Ennen kuin työskentelet minkään laitteiston parissa, ota selvää sähkökytkentöihin liittyvistä vaaroista ja tavanomaisista onnettomuuksien ehkäisykeinoista. Tässä julkaisussa esiintyvien varoitusten käännökset löydät laitteen mukana olevasta Regulatory Compliance and Safety Information -kirjasesta (määräysten noudattaminen ja tietoa turvallisuudesta).

Attention Ce symbole d'avertissement indique un danger. Vous vous trouvez dans une situation pouvant causer des blessures ou des dommages corporels. Avant de travailler sur un équipement, soyez conscient des dangers posés par les circuits électriques et familiarisez-vous avec les procédures couramment utilisées pour éviter les accidents. Pour prendre connaissance des traductions d'avertissements figurant dans cette publication, consultez le document Regulatory Compliance and Safety Information (Conformité aux règlements et consignes de sécurité) qui accompagne cet appareil.

Warnung Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu einer Körperverletzung führen könnte. Bevor Sie mit der Arbeit an irgendeinem Gerät beginnen, seien Sie sich der mit elektrischen Stromkreisen verbundenen Gefahren und der Standardpraktiken zur Vermeidung von Unfällen bewußt. Übersetzungen der in dieser Veröffentlichung enthaltenen Warnhinweise finden Sie im Dokument Regulatory Compliance and Safety Information (Informationen zu behördlichen Vorschriften und Sicherheit), das zusammen mit diesem Gerät geliefert wurde.

Avvertenza Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle persone. Prima di lavorare su qualsiasi apparecchiatura, occorre conoscere i pericoli relativi ai circuiti elettrici ed essere al corrente delle pratiche standard per la prevenzione di incidenti. La traduzione delle avvertenze riportate in questa pubblicazione si trova nel documento Regulatory Compliance and Safety Information (Conformità alle norme e informazioni sulla sicurezza) che accompagna questo dispositivo.

Advarsel Dette varselsymbolet betyr fare. Du befinner deg i en situasjon som kan føre til personskade. Før du utfører arbeid på utstyr, må du vare oppmerksom på de faremomentene som elektriske kretser innebærer, samt gjøre deg kjent med vanlig praksis når det gjelder å unngå ulykker. Hvis du vil se oversettelser av de advarslene som finnes i denne publikasjonen, kan du se i dokumentet Regulatory Compliance and Safety Information (Overholdelse av forskrifter og sikkerhetsinformasjon) som ble levert med denne enheten.

Aviso Este símbolo de aviso indica perigo. Encontra-se numa situação que lhe poderá causar danos físicos. Antes de começar a trabalhar com qualquer equipamento, familiarize-se com os perigos relacionados com circuitos eléctricos, e com quaisquer práticas comuns que possam prevenir possíveis acidentes. Para ver as traduções dos avisos que constam desta publicação, consulte o documento Regulatory Compliance and Safety Information (Informação de Segurança e Disposições Reguladoras) que acompanha este dispositivo.

¡Advertencia! Este símbolo de aviso significa peligro. Existe riesgo para su integridad física. Antes de manipular cualquier equipo, considerar los riesgos que entraña la corriente eléctrica y familiarizarse con los procedimientos estándar de prevención de accidentes. Para ver una traducción de las advertencias que aparecen en esta publicación, consultar el documento titulado Regulatory Compliance and Safety Information (Información sobre seguridad y conformidad con las disposiciones reglamentarias) que se acompaña con este dispositivo.

Varning! Denna varningssymbol signalerar fara. Du befinner dig i en situation som kan leda till personskada. Innan du utför arbete på någon utrustning måste du vara medveten om farorna med elkretsar och känna till vanligt förfarande för att förebygga skador. Se förklaringar av de varningar som förkommer i denna publikation i dokumentet Regulatory Compliance and Safety Information (Efterrättelse av föreskrifter och säkerhetsinformation), vilket medföljer denna anordning.

Electrical Equipment

Follow these basic guidelines when working with any electrical equipment:

Before beginning any procedure requiring access to the chassis interior, locate the emergency power-off switch for the room in which you are working.
Disconnect all power and external cables before moving a chassis.
Do not work alone when potentially hazardous conditions exist; never assume that power has been disconnected from a circuit; always check.
Do not perform any action that creates a potential hazard to people or makes the equipment unsafe.
Carefully examine your work area for possible hazards such as moist floors, ungrounded power extension cables, and missing safety grounds.

Telephone Wiring

Use the following guidelines when working with any equipment that is connected to telephone wiring or to other network cabling:

Never install telephone wiring during a lightning storm.
Never install telephone jacks in wet locations unless the jack is specifically designed for wet locations.
Never touch uninsulated telephone wires or terminals unless the telephone line has been disconnected at the network interface.
Use caution when installing or modifying telephone lines.

Preventing Electrostatic Discharge Damage

Electrostatic discharge (ESD) damage, which can occur when components are improperly handled, can result in complete or intermittent failures. The GRP consists of a printed circuit card that is fixed in a metal carrier. Electromagnetic interference (EMI) shielding and connectors are integral components of the carrier. Although the metal carrier helps to protect the printed circuit card from ESD, use an ESD-preventive wrist or ankle strap whenever you handle any electronic system component.

Following are guidelines for preventing ESD damage:

Always use an ESD-preventive wrist or ankle strap and ensure that it makes good skin contact.
Connect the equipment end of the strap to one of the two ESD connection sockets located on the front edges of the upper card cage (Cisco 12012 or Cisco 12016); to the ESD connection socket located on the lower left edge of the upper card cage (Cisco 12008); or to bare metal on the frame.
When you install a GRP, use the ejector levers to properly seat the backplane connectors in the backplane, then tighten all captive installation screws. These screws prevent accidental removal, provide proper grounding for the system, and help to ensure that the backplane connectors are seated in the backplane.
Handle GRPs by the carrier handles and carrier edges only; never touch the GRP or any connector pins.
When you remove a GRP, place it component-side up on an antistatic surface or in a static shielding bag. Immediately place the GRP in a static shielding bag if you need to return it to the factory.
Avoid contact between electronic equipment and clothing. Antistatic straps only protect the equipment from ESD voltages on the body; ESD voltages on clothing can still cause damage.

Caution For safety, periodically check the resistance value of the antistatic strap. The measurement should be between 1 and 10 megohms.

List of 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.

3/16-inch flat-blade screwdriver for the captive installation screws that secure the GRP in its slot.
ESD-prevention equipment or the disposable ESD-preventive wrist strap included with all spares and upgrade kits.
Antistatic mat, foam pad, or bag for the removed GRP (place the removed GRP into an antistatic bag if you plan to return it to the factory, or on an antistatic mat or foam if you are replacing components and will reinstall the GRP).

Replacing GRP

The following sections describe the procedures for replacing a GRP in your system.

Cisco 12016 GSR chassis---has three integral card cages: the upper card cage, the lower card cage, and the switch fabric card cage. The upper card cage has eight user-configurable slots that support a combination of line cards and a GRP. The far left slot in the upper card cage is a dedicated slot for an alarm card. The far right slot (slot 7) in the upper card cage is reserved for the GRP. The remainder of the slots in the upper card cage (slots 0 through 6) can be populated with any of the line cards supported by the Cisco 12016 GSR. The far right slot in the lower card cage is dedicated to a second alarm card.

Note Note If the Cisco 12016 GSR is equipped with an optional, redundant GRP, it must be installed in the far left slot of the lower card cage (slot 8). If the router is not equipped with an optional, redundant GRP, a line card can be installed in slot 8 of the lower card cage.

Cisco 12012---GRP installs in slot 0 in the upper card cage. You may have an additional, secondary GRP installed in another card slot location if your router is configured with a GRP redundant processor.
Cisco 12008---GRP installs in any slot in the upper card cage except for the slots that are reserved for the CSCs, although Cisco recommends that the GRP be installed in slot 0.

Before beginning the procedures, verify that your system meets the minimum requirements as described in the section "Installation Prerequisites" on page 9.

When your system meets those requirements, proceed to the section "Removing a GRP" for instructions on removing the GRP, and then to the section "Installing a GRP" section, for reinstallation instructions.

Caution We recommend you do not remove a GRP while the system is operating. Removing the installed GRP from a system while the system is operating will cause the system to stop forwarding packets and might cause the system to cease network operation.

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 A GRP that is only partially removed from the backplane can halt the system.

Caution Before you replace the GRP, back up the running configuration to a Trivial File Transfer Protocol (TFTP) file server or an installed Flash memory card so that you can retrieve it later. If the configuration is not saved, the entire configuration will be lost---inside the NVRAM on the removed GRP---and you will have to reenter the entire configuration manually. For instructions on how to save the configuration file, refer to the section "Copying Files to Flash Memory" section. This procedure is not necessary if you are temporarily removing a GRP; lithium batteries will retain the configuration in memory until you replace the GRP in the system.

Figure 4 shows the ejector levers.

Figure 4: Ejector Levers and Captive Installation Screw (Cisco 12012 shown)

Use the following procedure to remove a GRP:

Step 1 Turn off system power.

Step 2 If you are replacing the GRP in a system with one GRP, copy the currently running configuration file to a TFTP server or Flash memory so that you can retrieve it later. (Refer to the section "Copying Files to Flash Memory" section.)

Step 3 Attach an antistatic wrist strap to yourself and to one of the two ESD connection sockets located on the front edges of the upper card cage (Cisco 12012 or Cisco 12016); to the ESD connection socket located on the lower left edge of the upper card cage (Cisco 12008); or to bare metal on the frame.

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 Using a 3/16-inch flat-blade screwdriver, loosen the two captive screws on the ends of the GRP. (See Figure 4a.)

Step 5 Place your thumbs on the ends of each of the ejector levers and simultaneously pull them both away from the GRP faceplate (in the direction shown in Figure 4b) to release the GRP from the upper card cage slot, and to dislodge the GRP edge connector from the backplane.

Step 6 Grasp the GRP faceplate with one hand and pull the GRP straight out of the slot, keeping your other hand under the GRP to guide it. (See Figure 4.) Keep the GRP edge connector parallel to the backplane. Avoid touching the GRP printed circuit board, components, or any edge connector pins.

Step 7 Place the removed GRP on an antistatic mat or foam. If you plan to return the GRP to the factory, immediately place it in an antistatic bag to prevent ESD damage.

This completes the GRP removal procedure. If you removed the GRP to replace memory devices, proceed to the appropriate section in this publication, or to your specific Cisco GSR installation and configuration guide.

To replace a GRP, proceed to the section, "Installing a GRP."

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 A GRP that is only partially connected to the backplane can halt the system.

Use the following procedure to install a GRP:

Step 1 Always use an ESD-preventive wrist or ankle strap and ensure that it makes good skin contact. Connect the equipment end of the strap to one of the two ESD connection sockets located on the front edges of the upper card cage (Cisco 12012 or Cisco 12016); to the ESD connection socket located on the lower left edge of the upper card cage (Cisco 12008); or to bare metal on the frame.

Step 2 Grasp the GRP faceplate with one hand and place your other hand under the carrier to support and guide it into an upper card cage slot. (See Figure 4.) Avoid touching the GRP printed circuit board, components, or any edge connector pins.

Step 3 Place the bus-connector edge of the GRP in the appropriate slot and align the notches along the edge of the carrier with the grooves at the top and bottom of the slot.

Step 4 While keeping the GRP edge connector parallel to the backplane, carefully slide the carrier into the slot until the GRP faceplate makes contact with the ejector levers, then stop.

Step 5 Using the thumb and forefinger of each hand to pinch each ejector lever, simultaneously push both ejectors toward the center of the GRP faceplate until they are perpendicular to the GRP faceplate. (See Figure 4a.)

Step 6 Using a 3/16-inch flat-blade screwdriver, tighten the captive screws on the ends of the GRP. The captive screws prevent the GRP from becoming partially dislodged from the backplane and ensure proper EMI shielding. (These captive screws must be tightened to meet EMI specifications.)

Step 7 If you disconnected the console terminal to remove the GRP, or if you are installing a new GRP, connect the console terminal to the console port. (Refer to the section "Connecting to the Console Port" on page 17.)

Step 8 Ensure that the console terminal is turned on.

Step 9 Turn on system power.

This completes the GRP replacement procedure.

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 to 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 and auxiliary ports are both asynchronous serial ports; any devices connected to these ports must be capable of asynchronous transmission. (Asynchronous is the most common type of serial device; for example, most modems are asynchronous devices.)

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 3 lists the pinout for this port.

Console Port Pin	Signal	Direction	Description
1	GND	---	Signal Ground
2	TxD	<---	Transmit Data (from DTE)
3	RxD	--->	Receive Data (to DTE)
6	DSR	--->	Data Set Ready (always on)
7	GND	---	Signal Ground
8	DCD	--->	Data Carrier Detect (always on)

Table 3: Console Port Pinout

Console Port Pin Signal Direction Description

1

GND

---

Signal Ground

2

TxD

<---

Transmit Data (from DTE)

3

RxD

--->

Receive Data (to DTE)

6

DSR

--->

Data Set Ready (always on)

7

GND

---

Signal Ground

8

DCD

--->

Data Carrier Detect (always on)

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 4 lists the pinout for this port.

Auxiliary Port Pin	Signal	Direction	Description
2	TxD	--->	Transmit Data (to DCE)
3	RxD	<---	Receive Data (from DCE)
4	RTS	--->	Request To Send (used for hardware flow control)
5	CTS	<---	Clear To Send (used for hardware flow control)
6	DSR	<---	Data Set Ready
7	GND	-	Signal Ground
8	CD	<---	Carrier Detect (used for modem control)
20	DTR	--->	Data Terminal Ready (used for modem control only)

Table 4: Auxiliary Port Pinout

Auxiliary Port Pin Signal Direction Description

2

TxD

--->

Transmit Data (to DCE)

3

RxD

<---

Receive Data (from DCE)

4

RTS

--->

Request To Send (used for hardware flow control)

5

CTS

<---

Clear To Send (used for hardware flow control)

6

DSR

<---

Data Set Ready

7

GND

-

Signal Ground

8

CD

<---

Carrier Detect (used for modem control)

20

DTR

--->

Data Terminal Ready (used for modem control only)

Connecting to the Ethernet Port

This section provides information you need to make connections to the Ethernet port on your GRP.

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 5 lists the pinout for the RJ-45 receptacle.

Figure 6: RJ-45 Receptacle and Plug (Horizontal Orientation)

Warning The ports labeled Ethernet, 10BASE-T, Token Ring, Console, and AUX are safety extra-low voltage (SELV) circuits. SELV circuits should only be connected to other SELV circuits. Because the BRI circuits are treated like telephone-network voltage, avoid connecting the SELV circuit to the telephone network voltage (TNV) circuits.

Pin	Description
1	TxD+
2	TxD-
3	RxD+
4	Termination Network
5	Termination Network
6	RxD-
7	Termination Network
8	Termination Network

Table 5: RJ-45 Receptacle Pinout

Pin Description

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 and 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 56 screw-type locks, called jackscrews (see in 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 6 lists the MII connector pinout and signals. MII cables and transceivers are not available from Cisco Systems, but are available commercially.

Pin¹	Signal	Input	Output	Input/Output	Description
14 to 17	TxD	---	Yes	---	Transmit Data
12	Tx_CLK	Yes	---	---	Transmit Clock²
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

Table 6: MII Receptacle Pinout

Pin¹ Signal Input Output Input/Output Description

14 to 17

TxD

---

Yes

---

Transmit Data

12

Tx_CLK

Yes

---

---

Transmit Clock²

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

¹Any pins not indicated are not used.
²The signals Tx_CLK and Rx_CLK are generated by the external transceiver.

Table 7 lists the cabling specifications for 100-Mbps transmission over unshielded twisted-pair (UTP) and shielded twisted-pair (STP) cables.

Note 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. Transmission speed is determined by the network to which the Ethernet interface is connected and is not user-configurable.

Parameter	RJ-45	MII
Cable specification	Category 5¹ UTP², 22 to 24 AWG³	Category 3, 4, or 5, 150-ohm UTP or STP, or multimode optical fiber
Cable length (maximum)	---	1.64 ft (0.5 m) (MII-to-MII cable⁴)
Segment length (maximum)	328 ft (100 m) for 100Base-TX	3.28 ft (1 m)⁵ or 1312 ft (400 m) for 100Base-FX
Network length (maximum)	656 ft (200 m)⁵(with 1 repeater)	---

Table 7: Specifications and Connection Limits for 100 Mbps Transmission

Parameter RJ-45 MII

Cable specification

Category 5¹ UTP², 22 to 24 AWG³

Category 3, 4, or 5, 150-ohm UTP or STP, or multimode optical fiber

Cable length (maximum)

---

1.64 ft (0.5 m) (MII-to-MII cable⁴)

Segment length (maximum)

328 ft (100 m) for 100Base-TX

3.28 ft (1 m)⁵ or 1312 ft (400 m) for 100Base-FX

Network length (maximum)

656 ft (200 m)⁵(with 1 repeater)

---

¹EIA/TIA-568 or EIA-TIA-568 TSB-36 compliant.
²Cisco Systems does not supply Category 5 UTP RJ-45 or 150-ohm STP MII cables or MII transceivers; these items are available commercially.
³AWG = American Wire Gauge. This gauge is specified by the EIA/TIA-568 standard.
⁴This is the cable between the MII port on the GRP and the appropriate transceiver.
⁵ This length is specifically between any two stations on a repeated segment.

Table 8 lists IEEE 802.3u physical characteristics for 100Base-TX.

Parameter	100Base-TX
Data rate (Mbps)	100
Signaling method	Baseband
Maximum segment length (meters)	100 m between DTE¹ and repeaters
Media	Category 5 UTP (for RJ-45) or MII
Topology	Star/Hub

Table 8: IEEE 802.3u Physical Characteristics

Parameter 100Base-TX

Data rate (Mbps)

100

Signaling method

Baseband

Maximum segment length (meters)

100 m between DTE¹ and repeaters

Media

Category 5 UTP (for RJ-45) or MII

Topology

Star/Hub

¹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:

MII connections---Attach an MII cable directly to the MII receptacle on the GRP or attach a 100Base-T transceiver with the media appropriate to your application to the MII port on the GRP. (See Figure 10.) Be sure to use the appropriate strain relief on cable connections.

RJ-45 connections---Attach the Category 5 UTP cable directly to the RJ-45 receptacle on the GRP. (See Figure 10.)

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 To prevent problems on your system and network, do not simultaneously connect RJ-45 and MII cables to one GRP's Ethernet interface. On a single GRP, only one Ethernet connection can be used at one time. Only connect cables that comply with EIA/TIA-568 standards. (Refer to Table 7 and Table 8 for cable recommendations and specifications.)

Step 10 Attach the network end of your RJ-45 or MII cable to your transceiver, switch, hub, repeater, DTE, or other external equipment. Be sure to use the appropriate strain relief on cable connections.

Note The Ethernet port does not provide external routing functions; it is designed primarily as a Telnet port into the Cisco 12000 series router, and for booting and/or accessing Cisco IOS software images over a network to which the Ethernet port is directly connected.

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 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

This completes the procedure for Ethernet cable connection.

GRP Boot Process Overview

The following sequence describes a typical GRP boot process:

System power is turned on.
MBus module receives +5 VDC and starts executing MBus software.
GRP determines the system configuration by sending a message over the MBus requesting all installed devices to identify themselves. The return response provides slot number, and card and component type. The GRP, line cards, and CSCs are then powered up.
GRP power-on-reset logic delays, which allows power and both local and CSC clocks to stabilize.
After the power-on reset is released, the GRP begins to execute the ROM monitor software.

: If the ROM monitor is configured to autoboot, it loads and boots the Cisco IOS software.
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.

When the Cisco IOS software boots, it polls all other cards in the system and powers them up, loading their Cisco IOS software as needed.
GRP waits for all other cards to finish their boot processes.

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 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. For both types of power supplies, the output fail LED should be off.

Step 2 Listen for the system blower modules in the Cisco 12012 or Cisco 12016, or fan trays in the Cisco 12008; you should immediately hear them operating. In a noisy environment, the Cisco 12012 or Cisco 12016 blowers or 12008 fans 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 one end of the GRP, near the ejector lever. (See Figure 12.)

Each 4-digit display is capable of showing system messages, and displays a sequence similar to that shown in Table 9.

Figure 12: GRP Alphanumeric LED Displays (Front Panel View)

LED Display	Indications
MRAM nnnn	GRP microcode loads into MBus random-access memory (RAM); where nnnn is the microcode version. For example, Microcode Version 1.17 displays as 0117.¹
MSTR RP	This GRP is enabled and recognized by the system.

Table 9: GRP Alphanumeric LED Display Sequences

LED Display Indications

MRAM
nnnn

GRP microcode loads into MBus random-access memory (RAM); where nnnn is the microcode version. For example, Microcode Version 1.17 displays as 0117.¹

MSTR
RP

This GRP is enabled and recognized by the system.

¹The version of microcode running on your GRP might be different.

Step 4 During the line card boot process, which occurs immediately after the GRP boots, observe the alphanumeric LED indicators on each line card. The system attempts to boot identical line cards in parallel. Further, 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 LED displays on the line cards is the same as on the GRP, which is shown in Figure 12.)

Each line card displays a sequence similar to that shown in Table 10.

Table 10: Line Card Alphanumeric LED Display Sequences

LED Display¹ Indication

FABL
WAIT

Line card waits for the fabric downloader to begin loading into DRAM.²

FABL
DNLD

Fabric downloader loads into DRAM.

FABL
STRT

Fabric downloader launches from DRAM.

FABL
RUN

Fabric downloader runs in DRAM.

IOS
DNLD

Cisco IOS software downloads.

IOS
STRT

Cisco IOS software launches.

IOS
UP

Cisco IOS software runs in DRAM.

IOS
RUN

Line card is enabled and ready for use.

¹The sequence shown in Table 10 might occur too quickly for you to view; therefore, this sequence is provided as a baseline for how the line cards should function at startup.
²The fabric downloader loads the Cisco IOS software image onto the line card.

You must meet the following criteria:

You have a Flash memory card installed in PCMCIA slot 0
Flash memory card contains a valid Cisco IOS software image
The software configuration register is set to 0x102.

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 (as shown in Step 6).

Otherwise, the system enters the ROM monitor and the appropriate prompt appears (rommon>); you must then proceed to Step 5.

Step 5 If the ROM monitor prompt (rommon>) appears, you must boot the Cisco IOS software image you want to use by entering the appropriate b command at the ROM monitor prompt (>):

b---Boots the default system software from onboard Flash memory (if it is present in onboard Flash memory)

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.

b flash---Boots the first file in the Flash memory card in PCMCIA slot 0
b slot0: filename---Boots the file filename from the Flash memory card in PCMCIA slot 0
b slot1: filename---Boots the file filename from the Flash memory card in PCMCIA slot 1
b filename [host]---Boots the file filename from the server host using TFTP

While the system boots, the console screen displays a script and system banner similar to the following:

Cisco Internetwork Operating System Software
IOS (tm) GS Software (GSR-P-MZ), Released Version 11.2(9)GS
Copyright (c) 1986-1997 by cisco Systems, Inc.
Compiled Sat 10-May-97 06:02a

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, 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]:

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.

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 LED indicators on the GRP (see Figure 13) and the behavior you should observe.

The LEDs on the GRP indicate system and GRP status, which Flash memory card slot is active, and which Ethernet connection is in use and what is occurring on the Ethernet interface. (A successful boot is indicated by the alphanumeric LED displays as shown in Table 9; however, this does not necessarily mean that the system has reached normal operation.)

The GRP has the following eight LED indicators:

2 PCMCIA activity LEDs (labeled Slot 0 and Slot 1)---one LED per PCMCIA slot--- Light when the slot is accessed. The LEDs receive power from the switched slot voltage.
4 RJ-45 Ethernet port LEDs (labeled LINK, COLL, TX, and RX)---Used in conjunction with the RJ-45 Ethernet connector. When the MII Ethernet port is in use, the LEDs are disabled. The LEDs indicate link activity (LINK), collision detection (COLL), data transmission (TX), and data reception (RX).
2 RJ-45 or MII Ethernet port selection LEDs (labeled MII and RJ-45)Two LEDs, when on, identify which one of the two Ethernet connections you selected. When the RJ-45 port is selected, its LED is on, and the MII LED is off. When the MII port is selected, its LED is on, and the RJ-45 LED is off.

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; a maximum usable bandwidth of approximately 20 Mbps can be expected if you are using 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.

Further, 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.

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 At the privileged-level prompt, enter configuration mode and specify that the console terminal is the source of the configuration subcommands as follows:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#

Step 2 At the configuration mode prompt, specify the Ethernet interface by entering the subcommand interface, followed by the type (ethernet) and port (0) as follows:

Router(config)# interface ethernet 0
Router(config-if)#

Step 3 Determine the physical Ethernet connection you want to use (RJ-45 or MII), then use the media-type type command as appropriate for your physical Ethernet connection:

Router(config-if)# media-type type

Where type is RJ45 or MII. The system default is RJ45.

Step 4 If IP routing is enabled on the system, you can assign an IP address and subnet mask to the interface with the ip address configuration subcommand, as in the following example:

Router(config-int)# ip address 1.1.1.10 255.255.255.0

Step 5 Add any additional configuration subcommands required to enable or disable routing protocols (such as the no ip mroute-cache command) and to set other interface characteristics.

Step 6 Change the shutdown state to up and enable the Ethernet interface as follows:

Router(config-int)# no shutdown

Step 7 When you have included all of the configuration subcommands to complete the configuration, press Ctrl-Z to exit configuration mode.

Step 8 Write the new configuration to nonvolatile memory as follows:

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 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?: yes
  Configure IP on this interface?: yes
    IP address for this interface: 3.3.1.1
    Number of bits in subnet field: 8
    Class A network is 3.0.0.0, 8 subnet bits; mask is 255.255.0.0
Configure CLNS on this interface?: yes

This completes the procedures for configuring the Ethernet port on a GRP installed in a Cisco 12000 series system.

Implementing 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 NVRAM.

Following are some reasons for changing the software configuration register settings:

To select a boot source and default boot filename

To enable or disable the Break function

To control broadcast addresses

To set the console terminal baud rate

To load operating software from Flash memory

To enable booting from a Trivial File Transfer Protocol (TFTP) server

To recover a lost password

To allow you to manually boot the system using the b command at the bootstrap program prompt

To force an automatic boot from the system bootstrap software (boot image) or from a default system image in onboard Flash memory, and to read any boot system commands that are stored in the configuration file in NVRAM

Table 11 lists the meaning of each of the software configuration memory bits, and Table 12 defines the boot field, specified as a binary number which consists of bits 0 through 3 of the software configuration register.

Caution To avoid confusion and possibly halting the Cisco 12000 series router, remember that valid configuration register settings might be combinations of settings and not just the individual settings listed in Table 11. For example, the factory default value of 0x0102 is a combination of settings.

Bit Number¹	Hexadecimal	Meaning
00 to 03	0x0000 to 0x000F	Boot field (see Table 12)
06	0x0040	Causes system software to ignore NVRAM contents
07	0x0080	OEM² 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.

Table 11: Software Configuration Register Bit Meanings

Bit Number¹ Hexadecimal Meaning

00 to 03

0x0000 to 0x000F

Boot field (see Table 12)

06

0x0040

Causes system software to ignore NVRAM contents

07

0x0080

OEM² 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

¹The factory default value for the configuration register is 0x0102. This value is a combination of the following: binary bit 8 = 0x0100 and binary bits 00 through 03 = 0x0002 (see Table 12).
²OEM = original equipment manufacturer

Table 12: Boot Field Explanation (Configuration Register Bits 00 to 03)

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.

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 The factory default configuration register setting for systems and GRP spares is 0x0102.

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:

When the boot field is set to 0, you must boot the operating system manually by issuing the boot command to the system bootstrap program, or rom monitor.
When the boot field is set to 1, the system boots the first image in the onboard bootflash single in-line memory module (SIMM).

You can enter the boot command only, or include additional boot instructions with the command such as the name of a file stored in Flash memory or a file that you specify for booting from a network server. If you use the boot command without specifying a file or any other boot instructions, the system boots from the default Flash image (the first image in onboard Flash memory). Otherwise, you can instruct the system to boot from a specific Flash image (using the boot system flash filename command), or boot from a network server by sending broadcast TFTP requests (using the boot system filename command), or 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.

Note If a bootable Cisco IOS software image exists in a Flash memory card installed in PCMCIA slot 0 or slot 1, the configuration register setting is overridden, and the bootable Cisco IOS software image will be booted instead of the default TFTP-bootable Cisco IOS software image (cisco2-grp through cisco17-grp).

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 Enter the enable command and your password to enter privileged level as follows:

Router> enable
Password: 
Router#

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:

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#

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 11), as in the following example:

Router(config)# 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, which 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:

Configuration register is 0x141 (will be 0x102 at next reload)

Step 6 Save your settings.

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.

Configuration Register Bit Meanings

The lowest 4 bits of the software configuration register (bits 3, 2, 1, and 0) form the boot field. (See Table 12.) 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 Cisco 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 13 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 term
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# config-register 0x0102
Router(config)# boot system flash [filename]
Crtl-z
Router#

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 13 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

Table 13: Default Boot Filenames

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, 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 14 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>

Table 14: Configuration Register Settings for Broadcast Address Destination

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 15 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
2400	1	1
1200	1	0

Table 15: System Console Terminal Transmission Rate Settings

Baud Bit 12 Bit 11

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 Memory Cards in the GRP

Procedures for using Flash memory cards in the Gigabit Route Processor (GRP) and information on the following Flash memory card functions is presented in the following sections:

Installing and Removing Flash Memory Card in GRP

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. (See Figure 14.)

Figure 14: Installing and Removing Flash Memory Card

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 procedures for installing 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. (See Figure 14a.)

Note

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 14b.)

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.

Use the following procedures for removing a Flash memory card:

Step 1 To eject the card, press the ejector button until the card is free of the connector at the back of the slot. (See Figure 14c.)

Step 2 Remove the card from the slot and place it in an antistatic bag to protect it.

Formatting Flash Memory Card

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.

Note In the following procedure, you are assumed to have already booted your router. Use only Type 1 or Type 2 Flash memory cards.

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 Flash Memory Card in GRP" on page 34.) If slot 0 is not available, use slot 1.

Step 2 Enter the format slot0: (or format slot1:) command as follows:

Router# format slot0:
All sectors will be erased, proceed? [confirm]
Enter volume id (up to 30 characters): MyNewCard
Formatting sector 1
Format device slot0 completed
Router#

Note

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 "More Information" 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 terminal
Router(config)# no boot system
Router(config)# boot system flash slot0:new.image
Router(config)# config-register 0x2102
Crtl-z
Router# copy running-config startup-config
Router# reload

When the system reloads, it will boot the Cisco IOS software image from the Flash memory card in slot 0.

Note In the preceding example, the configuration register value 0x2000 instructs the system to boot a default Cisco IOS software image from Flash memory. If a network boot fails, the value 0x0100 instructs the system to ignore a break, and the value 0x0002 instructs the system to look in Flash memory for this default Cisco IOS software image.

Software Commands Associated with Flash Memory

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

You can move 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# pwd
slot1
 
Router# cd slot0:
Router# pwd
slot0

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 fun1
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

Files 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.

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 that this special location has been erased (which must occur before any write operation).
b---Means that the data that is about to be written to this special location has been temporarily copied.
E---Signifies that the sector that was temporarily occupied by the data was erased.
S---Signifies that the data was written to its permanent location in Flash memory.
Z---Means this log was erased after the successful squeeze command operation.

: The squeeze command operation keeps a log of which of these functions has been performed, so that upon 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, 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:, 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 terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# boot system flash device: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 0x0102
Crtl-z
Router#

Copying 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.

Note In general, we recommend that you upgrade Cisco IOS software images in Flash memory one at a time; do not delete all known-good images at one time. Also, upgrade PCMCIA-based Flash memory separately from onboard Flash memory to avoid losing important Cisco IOS software images that are known to be good. (The onboard Flash memory is referred to as the bootflash.)

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.

Copying Cisco IOS Software Image into 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 Flash Memory Card" and "Specifying Cisco IOS Image Used to Boot the System" on page 37.)

To copy a Cisco IOS software image, use the procedure in this section, which is based on the following assumptions:

You have a formatted Flash memory card in your GRP.
You have a good, bootable Cisco IOS software image in the onboard Flash memory so you can start the router.
The bootable Cisco IOS software image you want to copy to the Flash memory card exists on a TFTP server to which you have access (meaning that you know its name and have connectivity to it), and at least one interface is available to access this server. To ensure access to a TFTP server, you need to configure one interface.
You know the filename of the image you want to copy into the Flash memory card.

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:

Router> en
Password:
Router# copy tftp:new.image slot0:new.image
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]
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
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 must now reboot the system.

This completes the procedure for copying a bootable image into a Flash memory card.

Copying Cisco IOS Software Images between Flash Memory Cards

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:

The new image on the new Flash memory card is image.new.
The old image in the Flash memory card in slot 0 is image.old.
The bootable image in onboard Flash memory is image.boot. (Use the Cisco IOS software image used by default to boot the system if no other images are available.)

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.

Note For this scenario, it is assumed that the new Cisco IOS software image will fit on the Flash memory card in slot 0 next to the old image. If there is not enough available space, use the delete command to delete files from the Flash memory card to make sufficient room for the new Cisco IOS software image; however, do not delete the image.old file. Then use the squeeze command to remove these deleted files from the Flash memory card. (For information on the squeeze command, refer to the section "Software Commands Associated with Flash Memory" on page 37.)

If, after you delete files and use the squeeze command, the two files cannot coexist on the Flash memory card 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 (with the file image.new) in slot 0. Proceed to Step 5 and use the command boot system flash slot0:image.new to designate the file image.new as the default boot 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 is used.)

Step 2 Enable the router as follows:

Router> en
Password:
Router#

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:

Router# 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:

Router# config t
Router(config)# no boot system
Router(config)# boot system flash slot0:image.new
Crtl-z
Router# copy running-config startup-config
Router# 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.

Copying System Configuration Files between GRP Memory and a Flash Memory Card

Copying a configuration file to a Flash memory card 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, and then to copy the configuration file from a Flash memory card back to NVRAM.

Note You cannot copy files directly into DRAM.

Copying Configuration File from GRP NVRAM to Flash Memory Card

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. Note that the environmental variable CONFIG_FILE must be pointing (set) to NVRAM, which is the system default.

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:

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 Enter the copy startup-config slot0:filename command as follows:

Router# copy startup-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]
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Router#

Note 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.

You can also copy the running configuration (located in DRAM) to a Flash memory card, as shown in the following section "

Copying Configuration File from GRP DRAM to Flash Memory Card

Step 3 Verify that the file was copied correctly using the dir command 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)
Router#

This completes the procedure for copying a configuration file between GRP NVRAM and a Flash memory card.

Copying Configuration File from GRP DRAM to Flash Memory Card

Following is an example of copying your running configuration file from GRP DRAM to a Flash memory card in PCMCIA slot 0 or slot 1.

You can use the command copy running-config [ slot0: | slot1: ]:filename, 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.

Use the copy running-config slot0:filename command as 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 was 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 example showing how to copy a configuration file from GRP DRAM to a Flash memory card.

Copying Configuration File from Flash Memory Card to GRP NVRAM

Following is an example of copying your startup configuration file from a Flash memory card in PCMCIA slot 0 or slot 1 back to NVRAM.

You can use the command copy [ slot0: | slot1: ]:filename startup-config, where [slot0 | slot1]:filename is the source of the file (Flash memory card), and startup-config is the destination (NVRAM).

Use the copy slot0:filename startup-config command as 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 example of copying a configuration file from a Flash memory card to NVRAM.

Recovering from Locked Blocks in Flash Memory Cards

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. (Refer to the section "Formatting Flash Memory Card" on page 36.)

Caution Formatting a Flash memory card causes data it contains to be lost.

Recovering Lost Password

This section provides information on how to recover a lost password.

The following overview describes this process:

Enter the show version command to note the existing software configuration register value.
Break to the bootstrap program prompt.
Change the configuration register to ignore NVRAM.

Note A key to recovering a lost password is to set the configuration register so that the contents of NVRAM are ignored (0x0040), allowing you to see your password.

Enter privileged level in the system EXEC.

Enter the show startup-config command to display the enable password.
Change the configuration register value back to its original setting.

Use the following procedure to recover a lost password.

Note If the enable password is encrypted, the following password recovery procedure will not work and you will have to reconfigure the system; you will not be able to reboot it. To reconfigure the system, use the displayed configuration, which is shown using the show startup-config EXEC command. (See Step 11.)

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 router. (To power cycle, turn off power, wait
5 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 5 seconds of turning on the router, press the Break key. This action causes the terminal to display the bootstrap program prompt as follows:

rommon 1>

Step 6 Set the configuration register to ignore the configuration file information as follows:

rommon 1> confreg
 
	Configuration Summary
enabled are:
console baud: 9600
boot: image specified by the boot system command
	or default to: cisco2-grp
 
do you wish to change the configuration? y/n [n]: y
enable "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]: y
change console baud rate? y/n [n]:
change boot characteristics? y/n [n]
 
	Configuration Summary
enabled are:
console baud: 9600
boot: image specified by the boot system command
	or default to: cisco2-grp
 
Do you wish to change the configuration? y/n [n]
 
You must reset or power cycle for the new config to take effect

Step 7 Initialize the router by entering the i command as follows:

rommon 1> i

The 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 Enter no in response to the system configuration dialog prompts until the following system message is displayed:

Press RETURN to get started!

Step 9 Press Return.

After some interface information displays, the prompt appears as follows:

Router>

Step 10 Enter the enable command to enter enabled mode.

The prompt changes to the following:

Router#

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:

Router# configure terminal
Enter 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 0x0102 (factory default) using the config-register 0x value command.

Step 13 Enter Ctrl-Z to exit configuration mode.

Step 14 Reboot the router and enable it using the recovered password.

This completes the procedure for recovering a lost password.

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 16.)

The default DRAM configuration is 128 MB (one 128-MB DIMM in U39).

Note The total number of memory devices per DIMM differs for each manufacturer. The DIMMs in the following illustrations are generic representations of the actual DRAM DIMMs for your GRP. To be assured that you are using the correct DIMMs, refer to the specific part or product numbers for your DRAM upgrade kit (see section on DRAM) and to the Cisco part numbers on the DIMMs. (See Table 16.)

Figure 15: Locations of GRP Memory Components

Note Each GRP DIMM socket has one plastic lever on one end, which you use to remove the DIMM from its socket. (See Figure 16.)

Before proceeding, ensure that you have the proper tools and ESD-prevention equipment available. To upgrade DRAM, you install DIMMs in one or two banks (U39 and U42). Table 16 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 Depending on your router's configuration and the protocols and features your system is running, you might require more than 128 MB of DRAM. Upgrade your system DRAM based on your current configuration, this potential requirement, and the information in Table 16.

Total DRAM	Product Numbers	DRAM Sockets	Number of DIMMs
64 MB¹	MEM-GRP/LC-64(=)	U39 (bank 1) or U42 (bank 2)	1 64-MB DIMM
128 MB	MEM-GRP/LC-64(=)	U39 (bank 1) and U42 (bank 2)	2 64-MB DIMMs
128 MB	MEM-GRP/LC-128(=)	U39 (bank 1) or U42 (bank 2)	1 128-MB DIMM
256 MB	MEM-GRP/LC-256(=)	U39 (bank 1) and U42 (bank 2)	2 128-MB DIMMs

Table 16: DRAM DIMM Configurations

Total DRAM Product Numbers DRAM Sockets Number of DIMMs

64 MB¹

MEM-GRP/LC-64(=)

U39 (bank 1)
or
U42 (bank 2)

1 64-MB DIMM

128 MB

MEM-GRP/LC-64(=)

U39 (bank 1) and U42 (bank 2)

2 64-MB DIMMs

128 MB

MEM-GRP/LC-128(=)

U39 (bank 1)
or
U42 (bank 2)

1 128-MB DIMM

256 MB

MEM-GRP/LC-256(=)

U39 (bank 1) and U42 (bank 2)

2 128-MB DIMMs

¹64 MB is the standard (default) DRAM configuration for the GRP.

.

Caution To prevent system and memory problems when installing DRAM, make sure that the card's DRAM DIMMS are +3.3VDC, 60-ns, EDO devices. Do not attempt to install other DRAM devices in the GRP's DIMM sockets.

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 To prevent ESD damage, handle DIMMs by the card edges only.

Use the following procedure to remove the existing DIMM(s):

Step 1 Turn off the system power.

Step 2 Attach an antistatic wrist strap to yourself and to one of the two ESD connection sockets located on the front edges of the upper card cage (Cisco 12012 or Cisco 12016); to the ESD connection socket located on the lower left edge of the upper card cage (Cisco 12008); or to bare metal on the frame.

Step 3 Remove the GRP. (Follow the steps in the section "Removing a GRP" on page 14.)

Step 4 Place the GRP on an antistatic mat or pad.

Step 5 Position the GRP so that the faceplate is toward you, and the backplane connector is away from you. (See Figure 15.)

Step 6 Locate the DRAM DIMMs on the GRP. The DIMMs occupy U39 (bank 1) and U42 (bank 2). (See Figure 15.)

Step 7 For the DIMM you want to remove, pull down the lever on the DIMM socket to release the DIMM from the socket. (See Figure 16.)

Figure 16: Using DIMM Socket Release Lever to Remove DIMMs

Step 8 When one end of the DIMM is released from the socket, grasp each end of the DIMM with your thumb and forefinger and pull the DIMM completely out of the socket. Handle the edges of the DIMM only (see Figure 17); avoid touching the memory module or pins and the metal traces, or fingers, along the socket edge.

Step 9 Place the DIMM in an antistatic bag to protect it from ESD damage.

Step 10 Repeat Steps 6 through 9 for the remaining DIMM, if required for your upgrade.

This completes the DIMM removal procedure. Proceed to "Installing New DIMMs" to install the new DIMMs.

Installing New DIMMs

This section provides the procedure for installing new DIMMs.

Caution DIMMs are sensitive components that can be shorted by mishandling; they are susceptible to ESD damage. Handle DIMMs by the edges only (see Figure 17); avoid touching the DIMMs, pins, or traces (the metal fingers along the connector edge of the DIMM).

Figure 17: Handling a DIMM

Use the following procedure to install the new DIMMs:

Step 1 Attach an antistatic wrist strap to yourself and to one of the two ESD connection sockets located on the front edges of the upper card cage (Cisco 12012 or Cisco 12016); to the ESD connection socket located on the lower left edge of the upper card cage (Cisco 12008); or to bare metal on the frame.

Step 2 Place the GRP on an antistatic mat or pad.

Step 3 Position the GRP so that the faceplate is toward you, and the backplane connector is away from you. (See Figure 15.)

Step 4 Remove a new DIMM from the antistatic bag.

Step 5 Hold the DIMM component-side up, with the connector edge (the metal fingers) closest to you. Hold the ends of the DIMM between your thumb and forefinger. (See Figure 17.)

Step 6 Tilt the DIMM to approximately the same angle as the socket and insert the entire connector edge into the socket.

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 Gently push the DIMM into the socket until the lever is flush against the side of the DIMM socket (see Figure 16), and the DIMM's backplane connector is fully inserted. If necessary, rock the DIMM gently back and forth to seat it properly.

Step 8 When the DIMM is installed, check that the release lever is flush against the side of the DIMM socket. If it is not, the DIMM might not be seated properly. If the DIMM appears misaligned, carefully remove it and reseat it in the socket. Push the DIMM firmly back into the socket until the release lever is flush against the side of the DIMM socket.

Caution When inserting DIMMs, use firm but not excessive pressure. If you damage a socket, you will have to return the GRP to the factory for repair.

Step 9 Repeat Steps 4 through 8 for the remaining DIMM, as required.

This completes the DIMM replacement procedure. Replace the GRP in the slot from which you removed it. (See the section "Installing a GRP" on page 16.) Then restart the system for an installation check.

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 The time required for the system to initialize might vary with different router configurations and DRAM configurations. Routers with 256 MB of DRAM might take longer to boot than those with less DRAM.

If the system fails to boot properly, or if the console terminal displays a checksum or memory error, check the following:

Ensure that all DIMMs are installed correctly. If necessary, shut down the system and remove the GRP to check the DIMMs. Look straight down on the DIMMs to inspect them at eye level. They should all be aligned at the same angle and the same height when properly installed. If a DIMM appears to stick out or rest in the socket at a different angle from the others, remove the DIMM and reinsert it. Then replace the GRP and reboot the system for another installation check.
DIMMs must be extended data output (EDO), +3.3VDC, 60-ns DRAM devices. The speed is printed along one edge of the DIMM.

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.

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.

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:

Turn the television or radio antenna until the interference stops.
Move the equipment to one side or the other of the television or radio.
Move the equipment farther away from the television or radio.
Plug the equipment into an outlet that is on a different circuit from the television or radio. (That is, make certain the equipment and the television or radio are on circuits controlled by different circuit breakers or fuses.)

Modifications to this product not authorized by Cisco Systems, Inc. could void the FCC approval and negate your authority to operate the product.

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 B and EN50082-2 standard requirements in Europe.

VCCI (Japan)

This is a class B product based on the standard of the Voluntary Control Council for Interference from Information Technology Equipment (VCCI). If this is used near a radio or television receiver in a domestic environment, it may cause radio interference. Install and use the equipment according to the instruction manual.

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

WWW: http://www.cisco.com
WWW: http://www-europe.cisco.com
WWW: http://www-china.cisco.com
Telnet: cco.cisco.com
Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.

For a copy of CCO's Frequently Asked Questions (FAQs), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

LED Display¹	Indication
FABL WAIT	Line card waits for the fabric downloader to begin loading into DRAM.²
FABL DNLD	Fabric downloader loads into DRAM.
FABL STRT	Fabric downloader launches from DRAM.
FABL RUN	Fabric downloader runs in DRAM.
IOS DNLD	Cisco IOS software downloads.
IOS STRT	Cisco IOS software launches.
IOS UP	Cisco IOS software runs in DRAM.
IOS RUN	Line card is enabled and ready for use.

Table of Contents

Gigabit Route Processor Installation and Configuration

RJ-45 Connections

MII Connections

Copying Configuration File from GRP NVRAM to Flash Memory Card

Copying Configuration File from Flash Memory Card to GRP NVRAM