|
|
Product Numbers: GRP-B=, GRP=
Document Order Number: DOC-784339=
This hardware installation and configuration note describes the Gigabit Route Processor (GRP), the route processor for use in Cisco 12000 series Internet Routers.
Following are the sections in this document:
This section contains information about the following hardware and software requirements:
For hardware installation and maintenance information on Cisco 12000 series Internet Routers, refer to the installation and configuration guide for your router. This includes information on card slot locations and other general requirements.
The GRP operates on all Cisco 12000 series Internet Routers with the following requirements:
When two GRPs are installed in a Cisco 12000 series Internet Router, one GRP acts as the active GRP, and the other acts as a backup, or standby GRP. If the active GRP fails, or is removed from the system, the standby GRP detects the failure and initiates a switchover. During a switchover, the standby GRP assumes control of the router, connects with the network interfaces, and activates the local network management interface and system console.
 |
Note If your system includes redundant GRPs, both GRPs should have the same memory size. Redundancy is not supported when using a GRP and a PRP in the same chassis. Cisco strongly recommends that you avoid configuring your router using mixed route processor cards. Refer to the Route Processor Redundancy Plus for the Cisco 12000 Series Internet Router publication for more redundancy information. |
For software configuration information, refer to the Cisco IOS software configuration and command reference publications for the installed Cisco IOS Release. Also refer to the Cisco IOS software release notes for additional information.
The GRP line card is supported in Cisco IOS Release 11.2(9)GS and later. GRP configurations with
512 MB of route memory are only compatible with Product Number GRP-B= . In addition, Cisco IOS Release 12.0(19)S or 12.0(19)ST or later and ROMMON Release 11.2 (181) or later are also required.
The show version and show hardware commands display the current hardware configuration of the router, including the system software version that is currently loaded and running.
For complete descriptions of show commands, see the Cisco IOS Configuration Fundamentals Configuration Guide and the Cisco IOS Configuration Fundamentals Command Reference.
For additional information on the GRP, refer to these publications:
Information about the Gigabit Route Processor (GRP), its components, functions, and features, and its use as the system processor for Cisco 12000 series Internet Routers is presented in the following sections. Figure 1 shows the front view of the GRP.
The GRP is available as Product Number GRP-B=, which includes one GRP with 128 MB of dynamic random access memory (DRAM) and one 64-MB advanced technology attachment (ATA) Flash disk.
|
Note In order to maintain Class B EMI compliance, shielded cables must be used on the console and
auxiliary ports of the GRP. An updated version of the GRP (Product Number GRP-B=, Rev. F0 and later), does not require shielded cables for Class B compliance. |
The primary functions of the GRP for Cisco 12000 series Internet Routers follow:
The GRP contains the following components:
|
Note GRP route memory configurations of 512-MB are only compatible with Product Number GRP-B=. In addition, Cisco IOS Release 12.0(19)S or 12.0(19)ST or later and ROMMON Release 11.2 (181) or later are also required. |
The Cisco IOS software images that run the Cisco 12000 series Internet Router system reside in Flash memory, which is located on the GRP in the form of a single in-line memory module (SIMM) and on up to two PCMCIA cards (called Flash memory cards or Flash disks), 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 or Flash disk 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 that reside in GRP Flash memory.
The Cisco 12000 series Internet Router system supports downloadable system software for most
Cisco IOS software upgrades, which enables you to remotely download, store, and boot from a new Cisco IOS software image. The Cisco IOS software runs from within GRP DRAM.
For specific Cisco IOS software requirements for the GRP, see the"Cisco IOS Software Requirements" section.
Figure 2 shows the locations of the various types of memory used on the GRP. GRP memory component types are presented in the following sections:
Their functions are presented in Table 1.
| Type | Size | Quantity | Description | Location |
|---|---|---|---|---|
DRAM | 1 or 2 | 64-, 128-, or 256-MB DIMMs (based on the required DRAM configuration) for main Cisco IOS software functions (default configuration is 128 MB3) | U39 (bank 1) | |
SRAM4 | 512 KB (fixed) | — | SRAM for secondary CPU cache memory functions | — |
NVRAM5 | 512 KB (fixed) | 1 | NVRAM for system configuration files | — |
Flash memory | 8 MB SIMM6 | 1 | Contains Cisco IOS software images, system configuration files, and other user-defined files on the GRP | U17 |
— | Flash memory7 | 1 to 2 | Contains Cisco IOS software images, system configuration files, and other user-defined files on up to two Flash memory cards or Flash disks8 | Flash disk |
Flash boot ROM | 512 KB | 1 | Flash EPROM for the ROM monitor program boot image | — |
| 164 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. 2GRP route memory configurations of 512-MB are only compatible with Product Number GRP-B=. In addition, Cisco IOS Release 12.0(19)S or 12.0(19)ST or later and ROMMON Release 11.2 (181) or later are also required. 3Default DRAM configuration is 128 MB. Bank 1 (U39) must be populated first. You can use one or both banks to configure DRAM up to 512 MB. 4SRAM is not user configurable or field upgradeable. 5NVRAM is not user configurable or field upgradeable. 6SIMM socket is wired for Cisco's own design and does not accept industry-standard 80-pin Flash SIMMs. 7A 64 MB advanced technology attachment (ATA) Flash disk is the default shipping configuration. Cisco IOS Release 12.0(17)S or 12.0(17)ST or later is required, along with the corresponding boot images for the GRP to function with a Flash disk. 8Type 1, Type 2, and ATA PCMCIA cards can be used in either PCMCIA slot. (See Table 2 for specific, allowable PCMCIA card configurations.) |
DRAM stores routing tables, protocols, and network accounting applications, and runs the Cisco IOS software. The standard (default) GRP configuration is 128 MB of extended data output (EDO) DRAM, with up to 512 MB available through DIMM upgrades.
|
Note GRP route memory configurations of 512-MB are only compatible with Product Number GRP-B=. In addition, Cisco IOS Release 12.0(19)S or 12.0(19)ST or later and ROMMON Release 11.2 (181) or later are also required |
 |
Caution To prevent memory problems, DRAM DIMMs must be +3.3VDC, 60-nanosecond (ns) EDO devices. Do not attempt to install other devices in the DIMM sockets. Cisco recommends that you use Cisco-approved memory options. (See Table 14 in the "Upgrading GRP Memory" section.) |
The following DRAM upgrade kits for the GRP and line cards are listed by product number:
The following DRAM upgrade kits for Product Number GRP-B= are available (listed by product number):
|
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 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.
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.
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 trivial file transfer protocol (TFTP) server to allow other servers to boot remotely from stored images or to copy them into their own Flash memory. The onboard Flash memory (called bootflash) contains the Cisco IOS software boot image, and the Flash memory card or Flash disk contains the Cisco IOS software image. A 64-MB Flash disk ships by default with the GRP. Larger capacity Flash disks are also supported.
The two types of system status LEDs used on the GRP.
The GRP has the following eight status LEDs:
The alphanumeric display LEDs are organized as two rows of four characters each. The display content is controlled by the GRPs MBus module software. Both rows of the display are powered by the MBus module.
These alphanumeric display LEDs provide system status messages that are displayed during the boot process and after the boot process is completed.
During the boot process, the display LEDs are controlled directly by the MBus. After the boot process, they are controlled by the Cisco IOS software (via the MBus), and display messages designated by the Cisco IOS software.
The LED displays indicate the following:
A soft reset switch provides a reset to the R5000s software on the GRP. You access the soft reset switch through a small opening in the GRPs faceplate. To depress the switch, you must insert a paperclip or a similar object into the opening.
|
Caution To prevent system problems or loss of data, use the soft reset switch only on the advice of Cisco service personnel. |
The GRP includes two Flash disk slots. Either slot can support an ATA Flash disk or a linear Flash memory card. The GRP ships by default with one 64-MB ATA Flash disk.
|
Note The GRP only supports +5VDC Flash disk devices. It does not support +3.3VDC Flash disk devices. |
All combinations of different Flash devices are supported by the GRP. You can use ATA Flash disks, linear Flash memory cards, or a combination of the two. Each Flash disk slot has an ejector button for ejecting a card from the slot.
|
Note Linear Flash memory cards may not have the capacity to meet the requirements of your configuration. |
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.
The GRP has one Ethernet port available, using one of the following two connection types:
Installation preparation is presented in the following sections:
Before you perform any procedure in this publication, review the safety guidelines in this section to avoid injuring yourself or damaging the equipment.
The following guidelines are for your safety and to protect the equipment. The guidelines do not include all hazards. Be alert.
|
Note Review the safety warnings listed in the Regulatory Compliance and Safety Information for Cisco 12000 Series Internet Routers publication (Document Number 78-4347-xx) that supports your router before installing, configuring, or maintaining the GRP. |
The complete list of safety warnings and agency approvals for the PRP is available in the Regulatory Compliance and Safety Information for Cisco 12000 Series Internet Routers publication. (Document Number 78-4347-xx.)
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.
Modifying the equipment without Cisco's authorization may result in the equipment no longer complying with FCC requirements for Class A digital devices. In that event, your right to use the equipment may be limited by FCC regulation and you may be required to correct any interference to radio or television communication at your own expense.
You can determine whether your equipment is causing interference by turning it off. If the interference stops, it was probably caused by the Cisco equipment or one of its peripheral devices. If the equipment causes interference to radio or television reception, try to correct the interference by using one or more of the following measures:
This apparatus complies with EN55022 Class B radiated and conducted emissions requirements.
This class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.
This apparatus complies with EN55022 Class A and EN55024 standards when used as ITE/TTE equipment, and EN 300 386-2 (EN55022 class B with shielded CAT5 Ethernet cable, non-central office equipment) for Telecommunications Network Equipment (TNE).
Figyelmeztetés a felhasználói kézikönyv számára:
Ez a berendezés "A" osztályú termék, felhasználására és üzembe helyezésére a magyar EMC "A" osztályú követelményeknek (MSZ EN 55022) megfelelõen kerülhet sor, illetve ezen "A" osztályú berendezések csak megfelelõ kereskedelmi forrásból származhatnak, amelyek biztosítják a megfelelõ speciális üzembe helyezési körülményeket és biztonságos üzemelési távolságok alkalmazását.
This equipment is a class A product and should be used and installed properly according to the Hungarian EMC Class A requirements (MSZEN55022). The Class A equipment are derived for typical commercial establishments for which special conditions of installation and protection distance are used.
This is a Class A product. In a domestic environment this product may cause radio interference in which case you may be required to take adequate measures.
|
Note Bureau of Standards, Metrology and Inspection (BSMI) product approval license number is on the product label outside the system enclosure. |
This is a Class A product based on the standard of the Voluntary Control Council for Interference from Information Technology Equipment (VCCI). If this equipment is used near a domestic environment, radio disturbance may arise. When such trouble occurs, the user may be required to take corrective actions.
Class A device. This device is registered for EMC requirements for industrial use. The seller or buyer should be aware of this. If this type was sold or purchased by mistake, it should be replaced with a residential-use type.
Electrostatic discharge (ESD) damage, which can occur when electronic cards or components are improperly handled, results in complete or intermittent failures. Electromagnetic interference (EMI) shielding is an integral component of the GRP. Cisco recommends using a ESD-preventive strap whenever you are handling a router or one of its components.
Following are guidelines for preventing ESD damage:
Follow these basic guidelines when working with any electrical equipment:
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.
The following sections describe the procedures for replacing a GRP in your system.
Before beginning the procedures, verify that your system meets the minimum requirements as described in the "Preparing for Installation" section.
When your system meets minimum requirements, proceed to the "Removing a GRP" section for instructions on removing the GRP, and then to the "Installing a GRP" section for reinstallation instructions.
|
Caution We recommend that 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. |
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.)
|
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 or Flash disk 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, see the "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.
To remove a GRP, follow these steps:
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. (See the "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.
|
Caution 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.
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 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.)
|
Caution 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. (See the "Connecting to the Console Port" section.)
Step 8 Ensure that the console terminal is turned on.
Step 9 Turn on system power.
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.
The system console port on the GRP is a DCE DB-25 receptacle for connecting a data terminal, which you must configure. The console port is labeled Console, as shown in Figure 5. Before connecting the console port, check your terminal's documentation to determine the baud rate of the terminal you plan to use. The baud rate of the terminal must match the default baud rate (9600 baud). Set up the terminal as follows: 9600 baud, 8 data bits, no parity, and 2 stop bits (9600, 8N2). The console port requires a straight-through EIA/TIA-232 cable. Use the console cable provided to connect the terminal to the console port on the GRP.
|
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 2 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) |
The auxiliary port on the GRP is an EIA/TIA-232 DTE, DB-25 plug for connecting a modem or other DCE device (such as a CSU/DSU or another router) to the router. The port is labeled Auxiliary. An example of a modem connection is shown in Figure 5. The asynchronous auxiliary port supports hardware flow control and modem control. Table 3 lists the pinout for this port.
| 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) |
Information you need to make connections to the Ethernet port on your GRP is presented in the following sections:
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 10BaseT and 100BaseTX 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.
Figure 6 shows the GRP RJ-45 receptacle and cable connectors. The RJ-45 connection does not require an external transceiver. The RJ-45 connection requires Category 5 unshielded twisted-pair (UTP) cables, which are not available from Cisco Systems, but are available from commercial cable vendors. Table 4 lists the pinout for the RJ-45 receptacle.
 |
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 |
Depending on your RJ-45 cabling requirements, use the cable pinouts shown in Figure 7 and Figure 8.
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 100BaseT 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 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 GRPs 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.)
Table 5 lists the MII connector pinout and signals. MII cables and transceivers are not available from Cisco Systems, but are available commercially.
| Pin1 | Signal | Input | Output | Input/Output | Description |
|---|---|---|---|---|---|
14 to 17 | TxD | — | Yes | — | Transmit Data |
12 | Tx_CLK | Yes | — | — | Transmit Clock2 |
11 | Tx_ER | — | Yes | — | Transmit Error |
13 | Tx_EN | — | Yes | — | Transmit Enable |
3 | MDC | — | Yes | — | MII Data Clock |
4 to 7 | RxD | Yes | — | — | Receive Data |
9 | Rx_CLK | Yes | — | — | Receive Clock |
10 | Rx_ER | Yes | — | — | Receive Error |
8 | Rx_DV | Yes | — | — | Receive Data Valid |
18 | COL | Yes | — | — | Collision |
19 | CRS | Yes | — | — | Carrier Sense |
2 | MDIO | — | — | Yes | MII Data Input/Output |
22 to 39 | GND | — | — | — | Common ground |
1, 20, 21, 40 | V | — | — | — | +5.0 VDC |
| 1Any pins not indicated are not used. 2The signals Tx_CLK and Rx_CLK are generated by the external transceiver. |
Table 6 lists the cabling specifications for 100-Mbps transmission over unshielded twisted-pair (UTP) and shielded twisted-pair (STP) cables.
|
Note 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 3, 4, or 5, 150-ohm UTP or STP, or multimode optical fiber | |
Cable length (max) | — | 1.64 ft (0.5 m) (MII-to-MII cable4) |
Segment length (max) | 328 feet (100 m) for 100Base-TX | 3.28 ft (1 m)5 or 1312 ft (400 m) for 100Base-FX |
Network length (max | 656 feet (200 m)5 (with 1 repeater) | — |
| 1EIA/TIA-568 or EIA-TIA-568 TSB-36 compliant. 2Cisco Systems does not supply Category 5 UTP RJ-45 or 150-ohm STP MII cables or MII transceivers; these items are available commercially. 3AWG = American Wire Gauge. This gauge is specified by the EIA/TIA-568 standard. 4This is the cable between the MII port on the GRP and the appropriate transceiver. 5This length is specifically between any two stations on a repeated segment. |
Table 7 lists IEEE 802.3u physical characteristics for 100Base-TX.
| Parameter | 100Base-TX |
|---|---|
Data rate (Mbps) | 100 |
Signaling method | Baseband |
Maximum segment length | 100 m between DTE1 and repeaters |
Category 5 UTP (for RJ-45) or MII | |
Topology | Star/Hub |
| 1DTE = data terminal equipment. |
Use the following procedure to connect cables to the GRPs Ethernet interface:
The Ethernet interface on the GRP is an end station device, not a repeater; therefore, you must connect the Ethernet interface to a repeater or hub.
|
Caution To prevent problems on your system and network, do not simultaneously connect RJ-45 and MII cables to one GRPs 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 6 and Table 7 for cable recommendations and specifications.) |
|
Note The Ethernet port does not provide external routing functions; it is designed primarily as a Telnet port into the Cisco 12000 series Internet 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 (POS) line card in Router A) to go through Router B, through Router C, and into Network 2.0.0.0. (See solid arrows in Figure 11.)
The following sequence describes a typical GRP boot process:
1. System power is turned on.
2. MBus module receives +5VDC and starts executing MBus software.
3. 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.
4. GRP power-on-reset logic delay, which allows power and both local and CSC clocks to stabilize.
5. After the power-on reset is released, the GRP begins to execute the ROM monitor software.
6. If the ROM monitor is configured to autoboot, it loads and boots the Cisco IOS software.
or
If the ROM monitor is not configured to autoboot, you must enter the appropriate b command at the ROM monitor prompt (rommon>) to boot the Cisco IOS software.
7. 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.
8. GRP waits for all other cards to finish their boot processes.
This section describes the initial system startup processes and procedures.
Use the following procedure to start your system:
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 or fan trays in the router; you should immediately hear them operating. In a noisy environment, 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 display LEDs, which are located at one end of the GRP, near the ejector lever. (See Figure 12.)
The 4-digit displays show system messages, and displays a sequence similar to that shown in Table 8.
| LED Display | Description |
|---|---|
MRAM | GRP microcode loads into MBus random-access memory (RAM); where nnnn is the microcode version. For example, Microcode Version 1.17 displays as 0117.1 |
MSTR | This GRP is enabled and recognized by the system. |
| 1The 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 display LEDs 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 display LEDs on the line cards is the same as on the GRP, which is shown in Figure 12.)
See the appropriate line card installation and configuration note for complete details on line card display LED sequences.
You must meet the following criteria to successfully boot the GRP:
The system automatically boots this Cisco IOS software image. The system then enters the setup facility, where you are prompted to perform a basic configuration of the system.
Otherwise, the system enters the ROM monitor and the appropriate prompt appears (rommon>).
Step 5 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 (>):
|
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. |
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
Step 6 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 screen, after the system displays the system banner and hardware configuration, the following System Configuration Dialog prompt appears:
--- System Configuration Dialog ---At any point you may enter a question mark '?' for help.Use ctrl-c to abort configuration dialog at any prompt.Default settings are in square brackets '[]'.Continue with configuration dialog? [yes/no]:
Step 7 You 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.
This section provides functional descriptions of the status LEDs on the GRP (see Figure 13) and the processes you should observe.
The status LEDs on the GRP indicate system and GRP status, which Flash memory card or Flash disk slot is active, which Ethernet connection is in use, and what is occurring on the Ethernet interface. (A successful boot is indicated by the alphanumeric display LEDs as shown in Table 8; however, this does not necessarily mean that the system has reached normal operation.)
The GRP has the following eight LED indicators:
The IEEE 802.3 Ethernet interface, located on the GRP, allows connections to external Ethernet networks and is capable of data transmission rates of 10 Mbps and 100 Mbps. At the auto-sensed data transmission rate of 100 Mbps, the Ethernet port provides maximum usable bandwidth that is less than 100 Mbps; expect a maximum usable bandwidth of approximately 20 Mbps for either the MII or RJ-45 connection. Transmission speed, which is not user-configurable, is determined by the network to which the Ethernet interface is connected.
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.
Use the following procedure to perform a basic configuration of the Ethernet interface in configuration mode:
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 After you include all of the configuration subcommands necessary 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#
In the following example of an Ethernet configuration using the setup command facility, the Ethernet interface is configured using IP and CLNS. (In this example, you want to use IP, CLNS, and the default RJ-45 Ethernet connection.)
Enter the setup facility using the setup command and respond to prompts as appropriate for your needs, using your own address and mask for the setup prompts.
(Additional displayed text omitted from this example.) Configuring interface Ethernet0: Is this interface in use?: 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 section contains information on the following additional configuration, troubleshooting, and maintenance tasks:
The system uses a 16-bit software configuration register, which allows you to set specific system parameters. Settings for the software configuration register are written into non-volatile random access memory (NVRAM).
Following are some reasons for changing the software configuration register settings:
Table 9 provides descriptions of each of the software configuration memory bits, and Table 10 defines the boot field, specified as a binary number which consists of bits 0 through 3 of the software configuration register.
|
Caution To avoid confusion and possibly halting the Cisco 12000 series Internet Router, remember that valid configuration register settings might be combinations of settings and not just the individual settings listed in Table 9. For example, the factory default value of 0x0102 is a combination of settings. |
| Bit 1 | Hexadecimal | Description |
|---|---|---|
00 to 03 | 0x0000 to 0x000F | Boot field (see Table 10) |
06 | 0x0040 | System software ignores NVRAM contents |
07 | 0x0080 | OEM2 bit enabled |
08 | 0x0100 | Break disabled |
09 | 0x0200 | Use secondary bootstrap |
10 | 0x0400 | IP3 broadcast with all zeros |
11 to 12 | 0x0800 to 0x1000 | Console line speed (default is 9600 baud) |
13 | 0x2000 | Boot default Flash software if network boot fails |
14 | 0x4000 | IP broadcasts without network numbers |
15 | 0x8000 | Enable diagnostic messages and ignore NVRAM contents |
| 1The 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 10). 2OEM = original equipment manufacturer 3IP = Internet Protocol |
| Boot Field | Description |
|---|---|
00 | Stays at the system bootstrap prompt. |
01 | Boots the first system image in onboard Flash memory. |
02 to 0F | Specifies a default filename for booting over the network. Enables boot system commands that override the default filename. |
Bits 0 through 3 of the software configuration register form the boot field, specified as a binary number.
|
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:
You can enter the boot command only, or include additional boot instructions with the command such as the name of a file stored in Flash memory or a file that you specify for booting from a network server. If you use the boot command without specifying a file or any other boot instructions, the system boots from the default Flash image (the first image in onboard Flash memory).
Otherwise, you can instruct the system to boot from a specific Flash image (using the boot system flash filename command), or boot from a network server by sending broadcast TFTP requests (using the boot system filename command), or send a direct TFTP request to a specific server (using the boot system filename ip-address command).
You can also use the boot command to boot images stored in the Personal Computer Memory Card International Association (PCMCIA) Flash memory cards or Flash disks located in PCMCIA slot 0 or slot 1 on the GRP. If you set the boot field to any bit pattern other than 0 or 1, the system uses the resulting number to form a filename for booting over the network.
To form this filename, the system starts with cisco and links the octal equivalent of the boot field value and the processor type in the 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 or Flash disk 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.
Use the following procedure to change the configuration register while running the system software:
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 9), 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.
The lowest 4 bits of the software configuration register (bits 3, 2, 1, and 0) form the boot field. (See Table 10.) The boot field specifies a number in binary form. If you set the boot field value to 0, you must boot the operating system manually by entering the b command at the bootstrap prompt (>).
If you set the boot field value to 0x2 through 0xF and there is a valid boot system command stored in the configuration file, the Cisco 12000 series Internet Router boots the system software as directed by that value. If there is no boot system command, the Cisco 12000 series Internet Router forms a default boot filename for booting from a network server. (See Table 11 for the format of these default filenames.)
In the following example, the software configuration register is set to boot the system from onboard Flash memory and to ignore Break at the next reboot of the system:
Router# conf 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 11 lists the default boot filenames. A boot system configuration command in the configuration file in NVRAM overrides the default filename created for booting over the network.
|
Note If a bootable Cisco IOS software image exists in a Flash memory card or Flash disk 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). |
| 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 12 shows the combined effect of bits 10 and 14.
| Bit 14 | Bit 10 | Address (<net> <host>) |
|---|---|---|
Off | Off | <ones> <ones> |
Off | On | <zeros> <zeros> |
On | On | <net> <zeros> |
On | Off | <net> <ones> |
Bits 11 and 12 in the configuration register determine the data transmission rate of the console terminal. Table 13 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 |
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.
Procedures for using Flash memory cards or Flash disks in the GRP and information on the Flash memory functions are presented in the following sections:
The GRP has two PCMCIA slots (slot 0 and slot 1), into which you can install a Flash memory card or Flash disk. The slots are positioned with slot 0 on the left and slot 1 on the right. (See Figure 14.)
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 or Flash disk in either slot position.
Use the following procedures to install a Flash memory card or Flash disk:
|
Note The Flash memory card or Flash disk is keyed and cannot be seated the wrong way. The ejector button will not pop out if the card is not properly inserted. |
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.)
|
Caution The Flash memory card or Flash disk 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 to remove a Flash memory card or Flash disk:
Step 2 Remove the card from the slot and place it in an antistatic bag to protect it.
The following issues exist when using a 48-, 64-, or 128-MB ATA Flash disk:
A boot image that supports the ATA file system must reside in bootflash. To enable booting from a Flash disk, set the configuration register bits to 0x2102 and add a boot system command to the configuration as follows:
Router(config)# config-reg 0x2102 Router(config)#^Z Router#write mem Router# configure terminal Enter configuration commands, one per line. End with CTRL-Z. Router(config)# boot system flash disk0:gsr-p-mz.120-19.S
|
Note See the Cisco IOS online publication Loading and Maintaining System Images and Microcode for details on this procedure. |
The Flash memory card or Flash disk that shipped with your router contains the Cisco IOS software image you need to boot your router. In some cases, you might need to insert a new Flash memory card or Flash disk and copy images or backup configuration files onto it. Before you can use a new Flash memory card or Flash disk, you must format it.
|
Note In the following procedure, you are assumed to have already booted your router. Use only Type 1 or Type 2 Flash memory cards, or ATA Flash disks. |
|
Caution The following formatting procedure erases all information on the Flash memory card or Flash disk. To prevent the loss of important data that might be stored on a Flash memory card or Flash disk, proceed carefully. If you want to save the data on a Flash memory card or Flash disk, copy the data to a server before you format the card. |
To format a new Flash memory card or Flash disk, follow these steps:
|
Note The flash card command examples presented in this publication assume the use of a standard Type 1 or Type 2 Flash memory card. If you are using an ATA Flash disk, replace any commands containing either the slot0: or slot1: command argument with a disk0: or disk1: command argument. |
|
Note If using an ATA Flash disk, replace any commands that include a slot0: or slot1: command argument, with disk0: or disk1:. |
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): NewCard Formatting sector 1 Format device slot0 completed Router#
|
Note For this example, a 20 MB Flash memory card was used. At the line "Formatting sector," the system counts backward from 160 to 1. |
The new Flash memory card or Flash disk is now formatted and ready to use.
For complete command descriptions and configuration information, refer to the Configuration Fundamentals Command Reference, the Configuration Fundamentals Configuration Guide, and the Cisco 12000 Series Internet Router Flash Disk Information publications. (For information on obtaining these publications, see the "Important Information" section.)
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 or
Flash disk 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. |
Following are software commands related to the onboard Flash memory on the GRP and the Flash memory cards and Flash disks.
|
Note If using an ATA Flash disk, replace any commands that include a slot0: or slot1: command argument, with a disk0: or disk1: command argument. |
Determine which memory media you are accessing using the pwd command as follows:
Router# pwd slot0
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 46019