|
|
Product Numbers: CX-FEIP2-2TX= and CX-FEIP2-2FX=
This configuration note is a standalone publication that provides instructions for installing and configuring the second-generation Fast Ethernet Interface Processor (FEIP2) in all Cisco 7500 series routers, and in Cisco 7000 series routers using the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI). (For specific compatibility requirements, refer to the section "Software and Hardware Prerequisites," on page 3.)
Included in this configuration note are steps for FEIP2 hardware installation and cable connection, and basic FEIP2 configuration steps and examples. A table of contents is included so you can more easily find what you need.
For additional descriptions of interface subcommands and configuration options available for Fast Ethernet (FE) interfaces, refer to the appropriate Cisco IOS software configuration and command reference publications listed in the section "If You Need More Information" on page 2.
This configuration note includes the following sections:
The Cisco IOS software running your router contains extensive features and functionality. The effective use of many of many of these features is easier if you have more information at hand. For additional information on configuration, the following documentation resources are available:
This section provides software and hardware requirements for a successful FEIP2 installation, a list of parts and tools you need to perform the installation, and includes safety and ESD-prevention guidelines to help you avoid injury and damage to the equipment. This section also provides a detailed description of the online insertion and removal (OIR) function to help you perform online installation successfully and avoid error message and system restarts. If you are installing a new FEIP2, and, therefore, preparing your site and planning network connections, be sure to review the Fast Ethernet descriptions and interface cable distance limitations, in the section "Fast Ethernet Overview" on page 9.
The FEIP2 operates with the CyBus in the Cisco 7500 series and requires that the host routers are running Cisco IOS Release 11.1(10)CA or later.
The FEIP2 operates with the CxBus in the Cisco 7000 series routers providing these routers have the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI) installed, and requires that the host routers are running Cisco IOS Release 11.1(10)CA or later. For proper operation with the FEIP2, we recommend that your RSP or RSP7000 has at least 32 MB of DRAM.
| Cisco IOS Subset Images | Description |
|---|---|
rsp-ajv-mz.111-10.CA.bin | Enterprise plus APPN |
rsp-jv-mz.111-10.CA.bin | Enterprise |
rsp-pv-mz.111-10.CA.bin | Internet Service Provider |
 | Caution Before you attach an MII transceiver to an MII receptacle on your FEIP2, ensure that your MII transceiver responds to physical sublayer (PHY) address 0 per section 22.2.4.4. "PHY Address" of the IEEE 802.3u specification; otherwise, interface problems might result. Confirm that this capability is available on your MII transceiver with the transceiver's vendor or in the transceiver's documentation. If a selection for "Isolation Mode" is available, we recommend you use this setting (if no mention is made of "PHY addressing"). |
| Caution To prevent system problems, do not simultaneously connect cables to the RJ-45 (or SC) and MII receptacles on a single FEIP2, FE interface. Each FE interface (100BASE-FX or 100BASE-TX) can have either an MII attachment or an RJ-45 (or SC) attachment, but not both. The MII and RJ-45 (or SC) receptacles represent two physical connection options for one FE interface. |
Following are safety guidelines that you should follow when working with any equipment that connects to electrical power or telephone wiring.
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.
Follow these basic guidelines when working with any electrical equipment:
Electrostatic discharge (ESD) damage, which can occur when electronic cards or components are improperly handled, results in complete or intermittent failures.
Use the following guidelines for preventing ESD damage:
| Caution For safety, periodically check the resistance value of the antistatic strap. The measurement should be between 1 and 10 megohms. |
This section describes mechanical functions of system components, emphasizes the importance of following correct procedures to avoid unnecessary board failures, and is for background only; specific procedures follow in the section "FEIP2 Installation" on page 25.
You can remove and replace interface processors while the system is operating; you do not need to notify the software or reset the system power. This functionality enables you to add, remove, or replace interface processors with the system online, which provides a method that is seamless to end users on the network, maintains all routing information, and ensures session preservation.
After an interface processor is reinstalled, the system brings on line only interfaces that match the current configuration and were previously configured as up; all others require that you configure them with the configure command.
| Caution The system can indicate a hardware failure if you do not follow proper procedures. Remove or insert only one interface processor at a time. Allow at least 15 seconds for the system to complete the preceding tasks before removing or inserting another interface processor. Disrupting the sequence before the system completes its verification can cause the system to interpret hardware failures. |
Cisco 7000 series and Cisco 7500 series routers have ejector levers located on the ends of the interface processor slots. (See Figure 1a.) The function of the ejector levers is to align and seat the card connectors in the backplane. Failure to use the ejector levers and insert the interface processor properly can disrupt the order in which the pins make contact with the card or interface processor. Follow the FEIP2 installation and removal instructions carefully, and review the following examples of incorrect insertion practices and their results:
Use the ejector levers when removing an interface processor to ensure that the backplane connector pins disconnect from the interface processor in the sequence expected by the system. Any interface processor that is only partially connected to the backplane can hang the bus. Steps for correctly performing OIR are included with the following procedures for installing and removing the FEIP2.
The show controllers cbus command displays the currently loaded and running microcode version for each interface processor, and FEIP2. The show startup-config EXEC command shows the current system instructions for loading microcode at startup.
Software and interface processor microcode images are carefully optimized and bundled to work together. Overriding the bundle can result in system incompatibilities. We recommend that you use the microcode included in the software bundle. For a complete description of microcode and downloading procedures, refer to the section "Upgrading FEIP2 Microcode" on page 41.
The term Ethernet is commonly used for all carrier sense multiple access/collision detection (CSMA/CD), local-area networks (LANs) that generally conform to Ethernet specifications, including Fast Ethernet under IEEE 802.3u.
IEEE 802.3u is well suited to applications where a local communication medium must carry sporadic, occasionally heavy traffic at high peak data rates. Stations on a CSMA/CD LAN can access the network at any time. Before sending data, the station listens to the network to see if it is already in use. If it is, the station waits until the network is not in use, then transmits; this is half-duplex operation.
A collision occurs when two stations listen for network traffic, hear none, and transmit very close to simultaneously. When this happens, both transmissions are damaged, and the stations must retransmit. The stations detect the collision and use backoff algorithms to determine when they should retransmit. Both Ethernet and IEEE 802.3u are broadcast networks, which means that all stations see all transmissions. Each station must examine received frames to determine if it is the intended destination and, if it is, to pass the frame to a higher protocol layer for processing.
IEEE 802.3u specifies the following different physical layers for 100BASE-T:
Each physical layer protocol has a name that summarizes its characteristics in the format speed/signaling method/segment length, where speed is the LAN speed in megabits per second (Mbps), signaling method is the signaling method used (either baseband or broadband), and segment length is typically the maximum length between stations in hundreds of meters. Therefore, 100BASE-T specifies a 100-Mbps, baseband LAN with maximum network segments.
This section provides specifications for IEEE 802.3u 100BaseT. Table 1-1 provides cabling specifications for 100BaseTX Fast Ethernet transmission over UTP and foil twisted-pair (FTP), and 100BaseFX Fast Ethernet over fiber-optic cables. It also summarizes IEEE 802.3u 100BaseTX and 100BaseFX physical characteristics. Also see Figure 1.
| Parameter | 100BASE-TX | 100BASE-FX Multimode | 100BASE-FX Single Mode |
|---|---|---|---|
Cable specification | 62.5/125 multimode optical fiber | 9/125 micron single-mode optical fiber | |
Maximum segment length (half-duplex)3 | 100 m | 412 m | N/A |
Maximum segment length (full-duplex)3 | 100 m | 2000 m | 10,000 m |
Maximum network length (half-duplex, one repeater)4 | 200 m | 272 m | N/A |
Data rate | 100 Mbps | 100 Mbps | 100 Mbps |
Signaling method | 4B/5B block coded, scrambled, with MLT-3 line coding | 4B/5B block coded, with NRZI line coding | 4B/5B block coded, with NRZI line coding |
Connector | SC-type: dual simplex or single duplex for RX and TX | RJ-45 (ISO/IEC 60603-7:-1990 | Single mode SC-type: dual simplex or single duplex for RX and TX |
Topology | Star/hub | Star/hub | Star/hub |
| 1EIA/TIA-568 or EIA-TIA-568 TSB-36 compliant. 2Cisco does not supply Category 5 UTP RJ-45 cables. However, they are available commercially. 3Data Terminal Equipment (DTE to DTE), see Figure 1. 4DTE to Repeater to DTE, see Figure 1. |
Table 3 lists the cabling specifications for 100-Mbps Fast Ethernet transmission over UTP, STP, and fiber-optic cables. Table 4 summarizes IEEE 802.3u 100BASE-T physical characteristics for 100BASE-TX and 100BASE-FX.
| Parameter | RJ-45 | MII | SC-Type |
|---|---|---|---|
Cable specification | Category 3, 4, or 5, 150-ohm UTP or STP, or multimode optical fiber | 62.5/125 multimode optical fiber | |
Maximum cable length | - | 1.64 ft (0.5 m) (MII-to-MII cable4) | - |
Maximum segment length | 328 ft (100 m) for 100BASE-TX | 3.28 ft (1 m)5 or 1,312 ft (400 m) for 100BASE-FX | 328 ft (100 m) |
Maximum network length | 656 ft (200 m)5 (with 1 repeater) | - | 656 ft (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. Both 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 FE interface and the appropriate transceiver. 5This length is specifically between any two stations on a repeated segment. |
| Parameter | 100BASE-FX | 100BASE-TX |
|---|---|---|
Data rate (Mbps) | 100 | 100 |
Signaling method | Baseband | Baseband |
Maximum segment length (meters) | 100 m between repeaters | 100 m between DTE1 and repeaters |
SC-type: dual simplex or single duplex for Rx and Tx | RJ-45MII | |
Topology | Star/hub | Star/hub |
| 1DTE = data terminal equipment. |
The Cisco 7000 series consists of the Cisco 7000 and Cisco 7010 routers. The FEIP2 operates in the Cisco 7000 series routers if these routers have the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI) installed. (For software and hardware requirements, refer to the section "Software and Hardware Prerequisites" on page 3.)
Network interfaces reside on modular interface processors, including the FEIP2, which are inserted into interface processor slots and provide a direct connection between external networks and the high-speed CxBus in the Cisco 7000 series. The Cisco 7000 series supports any combination of available network interface types.
In the 7-slot Cisco 7000, slot 5 is reserved for the RSP7000 (7000 RSP slot shown in Figure 3), which contains the system processor and performs packet switching functions, and slot 6 is reserved for the RSP7000CI (7000 CI slot shown in Figure 3), which contains all of the environmental monitoring functions for the Cisco 7000. The remaining five slots (slots 0 through 4) are for interface processors including the FEIP2.
In the 5-slot Cisco 7010, slot 3 is reserved for the RSP7000, which contains the system processor and performs packet switching functions, and slot 4 is reserved for the RSP7000CI, which contains all of the environmental monitoring functions for the Cisco 7010. The remaining three slots (slots 0 through 2) are for interface processors including the FEIP2.
The Cisco 7500 series includes the Cisco 7505, Cisco 7507, and Cisco 7513 routers. The FEIP2 operates in the Cisco 7500 series routers. (For software and hardware requirements, refer to the section "Software and Hardware Prerequisites" on page 3.)
Network interfaces reside on modular interface processors, including the FEIP2, which are inserted into interface processor slots and provide a direct connection between external networks and the high-speed CyBus in the Cisco 7500 series. The Cisco 7500 series supports any combination of available network interface types.
Figure 5 shows the interface processor end of the Cisco 7505. In the 5-slot Cisco 7505, one slot (4) is reserved for the Route Switch Processor (RSP1 or RSP4), which contains the system processor and performs packet switching functions. Slots 0 through 3 are for interface processors including the FEIP2.
Figure 6 shows the interface processor end of the Cisco 7507 router. In the 7-slot Cisco 7507, up to two slots (2 and 3) are reserved for the Route Switch Processor (RSP2 or RSP4), which contains the system processor and performs packet switching functions. Slots 0 and 1 and 4 through 6 are for interface processors including the FEIP2.
Figure 7 shows the interface processor end of the Cisco 7513 router. In the Cisco 7513, up to two slots (6 and 7) are reserved for the second generation Route Switch Processor (RSP2 or RSP4), which contains the system processor and performs packet switching functions. Slots 0 through 5 and 8 through 12 are for interface processors including the FEIP2.
The FEIP2 is a dual-port, fixed configuration interface processor that provides two, 100-Mbps, IEEE 802.3u Fast Ethernet (FE) interface interfaces.
The FEIP2 is available in the following fixed configurations:
| Caution To prevent system problems, we recommend that you not attempt to remove an FEIP2's FE interface and replace it with another, nor attempt to mix 100BASE-TX and 100BASE-FX FE interfaces on the same FEIP2. |
| Caution To prevent system problems, do not simultaneously connect cables to the RJ-45 (or SC) and MII receptacles on a single FEIP2 FE interface. Each FE interface (100BASE-FX or 100BASE-TX) can have either an MII attachment or an RJ-45 (or SC) attachment, but not both. The MII and RJ-45 (or SC) receptacles represent two physical connection options for one FE interface. |
The FEIP2 contains the enabled LED and a bank of three status LEDs for each of the two FE interfaces (located between the two receptacles on each FE interface). After system initialization, the enabled LED goes on to indicate that the FEIP2 has been enabled for operation. (The LEDs are shown in Figure 10.)
The following conditions must be met before the enabled LED goes on:
If any of these conditions is not met, or if the initialization fails for other reasons, the enabled LED does not go on.
Following are the three status LEDs and an explanation of what each indicates:
The two interface receptacles on each Fast Ethernet interface are a single MII, 40-pin, D-shell type receptacle, and a single RJ-45 receptacle (or SC-type for FEIP2-2FX optical-fiber connections). (See the FEIP2-2TX in Figure 11 and the FEIP2-2FX in Figure 12.)
You can use either one receptacle or the other; only one receptacle can be used at one time. Each connection supports IEEE 802.3u interfaces compliant with the 100BASE-X and 100BASE-T standards. The RJ-45 connection does not require an external transceiver. The MII connection requires an external physical sublayer (PHY) and an external transceiver. Cisco Systems does not supply Category 5 UTP RJ-45 cables; these cables are available commercially.
| Caution To prevent system problems, do not simultaneously connect cables to the RJ-45 (or SC) and MII receptacles on a single FEIP2, FE interface. Each FE interface (100BASE-FX or 100BASE-TX) can have either an MII attachment or an RJ-45 (or SC) attachment, but not both. The MII and RJ-45 (or SC) receptacles represent two physical connection options for one FE interface. |
The RJ-45 connection does not require an external transceiver. The MII connection requires an external physical sublayer (PHY) and an external transceiver. Figure 13 shows the RJ-45 cable connectors. RJ-45 cables are not available from Cisco Systems, but are available from commercial cable vendors. Table 5 lists the pinouts and signals for the RJ-45 connectors.
| Warning The ports labeled "Ethernet," "10BaseT," "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. |
Table 5 lists the pinouts and signals for the FEIP2-2TX's RJ-45 connectors.
| Pin | Description |
|---|---|
1 | Receive Data + (RxD+) |
2 | RxD- |
3 | Transmit Data + (TxD+) |
6 | TxD- |
Depending on your RJ-45 interface cabling requirements, use the pinouts in Figure 14 and Figure 15.
Figure 16 shows the duplex SC connector (one required for both transmit and receive), and Figure 17 shows the simplex SC connector (two required, one for each transmit and receive) used for 100BASE-FX optical-fiber connections on the FEIP2-2FX. These multimode, SC-type, optical-fiber cables are commercially available; they are not available from Cisco Systems.
Depending on the type of media you use between the MII connection on the FE interface and your switch or hub, the network side of your 100BASE-T transceiver should be appropriately equipped with ST-type connectors (for optical fiber), BNC connectors, and so forth. Figure 18 shows the pin orientation of the female MII connector on the FE interface.
The MII receptacle (on both the FEIP2-2FX and FEIP2-2TX) uses 2-56 screw-type locks, called jackscrews (shown in Figure 18), to secure the cable or transceiver to the MII port. MII cables and transceivers have knurled thumbscrews (screws you can tighten with your fingers) that you fasten to the jackscrews on the FEIP2'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 18 shows the MII female connector.
Table 6 lists the MII connector pinout and signals. MII cables are available commercially; they are not available from Cisco Systems. Table 6 refers to MII cables used between the MII connector on the FEIP2 and an appropriate transceiver. The connection between this transceiver and your network can be Category 3, 4, or 5, 150-ohm UTP or STP, or multimode optical fiber.
| Pin1 | In | Out | In/Out | Description |
|---|---|---|---|---|
14-17 | - | Yes | - | Transmit Data (TxD) |
12 | Yes | - | - | Transmit Clock (Tx_CLK)2 |
11 | - | Yes | - | Transmit Error (Tx_ER) |
13 | - | Yes | - | Transmit Enable (Tx_EN) |
3 | - | Yes | - | MII Data Clock (MDC) |
4-7 | Yes | - | - | Receive Data (RxD) |
9 | Yes | - | - | Receive Clock (Rx_CLK) |
10 | Yes | - | - | Receive Error (Rx_ER) |
8 | Yes | - | - | Receive Data Valid (Rx_DV) |
18 | Yes | - | - | Collision (COL) |
19 | Yes | - | - | Carrier Sense (CRS) |
2 | - | - | Yes | MII Data Input/Output (MDIO) |
22-39 | - | - | - | Common (ground) |
1, 20, 21, 40 | - | - | - | +5.0 volts (V) |
| 1Any pins not indicated are not used. 2Tx_CLK and Rx_CLK are generated by the external transceiver. |
The following sections describe the procedures for removing or installing an FEIP2 in the Cisco 7000 series or Cisco 7500 series routers. The functionality is the same for each router model; therefore, the term the chassis is used except where specific model issues arise.
The online insertion and removal function allows you to install and remove an FEIP2 without first shutting down the system; however, you must follow the instructions carefully. Failure to insert the FEIP2 properly can cause system error messages indicating a board failure. For a complete description of recommended guidelines for interface processor installation and removal, refer to the section "Guidelines for Interface Processor Installation and Removal" on page 7.
Each unused interface processor slot must contain an interface processor filler (which is an interface processor carrier without an interface board) to keep dust out of the chassis and to maintain proper air flow through the interface processor compartment. If you are installing a new FEIP2 that is not a replacement, you must first remove the interface processor filler from an unused slot; to do so proceed to the next section "Removing an Interface Processor or Interface Processor Filler." If you are replacing an FEIP2, proceed to the section "Removing an FEIP2."
If you plan to replace a currently installed interface processor with an FEIP2, attach an ESD-preventive wrist strap between you and any unpainted chassis surface; interface processor fillers do not require protection from ESD. Select an interface processor slot for the new FEIP2 and remove the interface processor or interface processor filler as follows:
Step 1 Use a screwdriver to loosen the captive installation screws on the interface processor or interface processor filler. (See Figure 1.)
Step 2 Place your thumbs on both ejector levers and simultaneously pull them both outward to release the filler from the backplane connector (in the opposite direction from that shown in Figure 1c).
Step 3 Grasp the handle with one hand and pull the card straight out of the slot, keeping your other hand under the carrier to guide it. (See Figure 19.) Keep the carrier parallel to the backplane.
Step 4 Store the interface processor or interface processor filler for future use.
To help prevent dust and contaminants from entering the chassis, do not leave the interface processor slot open. Immediately proceed to the section "Installing an FEIP2" on page 27.
You need not shut down the interface or the system power when removing an FEIP2 or interface processor.
If you have a Cisco 7507 or a Cisco 7513 with an RSP2 configured as the system slave, we strongly recommend that you use the following procedure to remove and replace an interface processor:
Step 1 Remove the slave RSP2.
Step 2 Wait 15 seconds.
Step 3 Remove and replace the interface processor using the procedures in this publication.
Step 4 Wait 15 seconds.
Step 5 Reinsert the slave RSP2.
If you are replacing a failed FEIP2, remove the existing board first, then install the new FEIP2 in the same slot. If you are replacing a currently installed interface processor with an FEIP2, remove the existing board first, then install the new FEIP2 in the same slot.
Figure 19 shows proper handling of an interface processor during installation.
To remove an FEIP2 or interface processor, follow these steps:
Step 1 Attach an ESD-preventive wrist strap between you and any unpainted chassis surface.
Step 2 If you are replacing a failed FEIP2, disconnect all cables from the FEIP2 ports; however, if you are only moving an FEIP2 to another slot, this step is not necessary.
Step 3 Use a screwdriver to loosen the captive installation screws at both ends of the board. (See Figure 1.)
| Caution Always use the ejector levers to remove or install the FEIP2. Failure to do so can cause erroneous system error messages indicating a board failure. |
Step 4 Place your thumbs on the ejector levers and simultaneously pull both of the ejectors outward (in the opposite direction from that show in Figure 1c) to release the FEIP2 from the backplane connector.
Step 5 Use the board's handle to carefully pull it straight out of the slot, keeping your other hand under the carrier to guide it. (See Figure 19.) Keep the board parallel to the backplane.
Step 6 Place the removed board on an antistatic mat or foam pad, or place it in an antistatic container if you plan to return it to the factory.
Step 7 If the interface processor slot is to remain empty, install a filler (MAS7K-BLANK) to keep dust out of the chassis and to maintain proper air flow inside the chassis. Do not leave the interface processor slot open. Immediately proceed to the section "Installing an FEIP2."
The FEIP2 slides into the open interface processor slot and connects directly to the backplane. The interface processors are keyed to guide pins on the backplane, so the FEIP2 can be installed only in an interface processor slot.
Figure 1 shows the functional details of inserting an interface processor and using the ejector levers. Figure 19 shows proper handling of an interface processor during installation.
Follow these steps to install an FEIP2:
Step 1 Ensure that a console terminal is connected to the console port (on the RSP or RSP7000) and that your console is turned ON.
Step 2 Hold the FEIP2 handle with one hand and place your other hand under the carrier to support the FEIP2 and guide it into the slot. (See Figure 19.) Avoid touching the card or any connector pins.
| Caution To prevent ESD damage, handle interface processors by the handles and carrier edges only. |
Step 3 Place the back of the FEIP2 in the slot and align the notch on the carrier with the groove in the slot. (See Figure 1.)
Step 4 While keeping the FEIP2 parallel to the backplane, carefully slide it into the slot until the back of the faceplate makes contact with the ejector levers, then stop. (See Figure 1b.)
Step 5 Using your thumbs, simultaneously push both ejector levers inward until the FEIP2 is pushed entirely into its slot. (See Figure 1c.)
Step 6 Tighten both of the captive installation screws.
| Caution To ensure proper electromagnetic interference (EMI) isolation for the chassis, make certain to tighten the captive installation screws on each FEIP2 immediately after you install it and before proceeding with the installation of each remaining FEIP2 or other interface processor. |
The MII and RJ-45 (or SC) receptacles represent two physical connection options for one FE interface. Each FEIP2 has two FE interfaces. On a single FE interface, you can use either the RJ-45 (or SC for FEIP2-2FX) connection or the MII connection. You can use the RJ-45 (or SC for FEIP2-2FX) connection on one FE interface and the MII connection on the other.
Connect RJ-45, SC (FEIP2-2FX), or MII cables as follows:
Step 1 If you have MII connections, attach an MII cable directly to the MII port on the FEIP2 or attach a 100BASE-T transceiver, with the media appropriate to your application, to the MII port on the FEIP2. (See Figure 20 for FEIP2-2TX or Figure 21 for FEIP2-2FX.)
| Caution Before you attach an MII transceiver to an MII receptacle on your FEIP2, ensure that your MII transceiver responds to physical sublayer (PHY) address 0 per section 22.2.4.4. "PHY Address" of the IEEE 802.3u specification; otherwise, interface problems might result. Confirm that this capability is available on your MII transceiver with the transceiver's vendor or in the transceiver's documentation. If a selection for "Isolation Mode" is available, we recommend you use this setting (if no mention is made of "PHY addressing"). |
If you have RJ-45 connections, attach the Category 5 UTP cable directly to one of the RJ-45 ports on the FEIP2. (See Figure 20 for FEIP2-2TX or Figure 21 for FEIP2-2FX.) The FEIP2 is an end station device and not a repeater. You must connect the FE interface to a repeater or hub.
If you have an SC connection (FEIP2-2FX), attach a cable directly to the SC port on one of the FEIP2-2FX's interfaces. (See Figure 21.) Use either one duplex SC connector, or two simplex SC connectors, and observe the correct relationship between the receive (RX) and transmit (TX) ports on the FEIP2-2FX and your repeater.
Step 2 For the 100BASE-TX RJ-45 connections, attach the ferrite bead to the RJ-45 cable (at either end), as shown in Figure 22.
| Caution The ferrite bead prevents electromagnetic interference (EMI) from affecting the 100BASE-TX-equipped system and is a required component for proper system operation. |
| Caution To prevent problems on your FEIP2 and network, do not simultaneously connect RJ-45 (or SC) and MII cables to one FE interface. On a single FE interface, only one network connection can be used at one time. Only connect cables that comply with EIA/TIA-568 standards. (Refer to Table 3 and Table 4, on page 12, for cable recommendations and specifications.) |
Step 3 Attach the network end of your RJ-45 (or SC) or MII cable to your 100BASE-T transceiver, switch, hub, repeater, DTE, or other external 100BASE-T equipment.
Step 4 Repeat Steps 1 through 3 for the second FE interface as required.
This completes the FEIP2 cable installation.
The FEIP2 has four status LEDs on its faceplate that indicate status on each FE port. (See Figure 23.)
After you connect cables, observe the LED states and the console display as the router initializes. When the system has reinitialized all interfaces, the enabled LED on the FEIP2 should go on. (For complete descriptions of the FEIP2 LEDs, refer to the section "FEIP2 LEDs" on page 20.)
The console screen will also display a message as the system discovers each interface during its reinitialization. After system initialization, the enabled LED goes on to indicate that the FEIP2 is enabled for operation.
The following conditions must be met before the FEIP2 is enabled:
If any of these conditions is not met, the enabled LED does not go on.
Verify that the FEIP2 is connected correctly as follows:
Step 1 While the system reinitializes each interface, observe the console display messages and verify that the system discovers the FEIP2. The system should recognize the FEIP2's interfaces but leaves them configured as down.
Step 2 When the reinitialization is complete, verify that the enabled LED on each FEIP2 FE interface is on and remains on. If the LED does stay on, proceed to Step 5. If the enabled LED does not stay on, proceed to the next step.
Step 3 If an enabled LED fails to go on, suspect the that the FEIP2 board connector is not fully seated in the backplane. Loosen the captive installation screws, then firmly push the top ejector down while pushing the bottom ejector up until both are parallel to the FEIP2 faceplate. Tighten the captive installation screws. After the system reinitializes the interfaces, the enabled LED on the FEIP2 should go on. If the enabled LED goes on, proceed to Step 5. If the enabled LED does not go on, proceed to the next step.
Step 4 If an enabled LED still fails to go on, remove the FEIP2 and try installing it in another available interface processor slot.
If the enabled LED goes on when the FEIP2 is installed in the new slot, suspect a failed backplane port in the original interface processor slot.
If the enabled LED still fails to go on, but other LEDs on the FEIP2 go on to indicate activity, proceed to Step 5 to resume the installation checkout and suspect that the enabled LED on the FEIP2 has failed.
If no LEDs on the FEIP2 go on, suspect that the FEIP2 is faulty.
If the enabled LED still does not go on, do not proceed with the installation. Contact a service representative to report the faulty equipment and obtain further instructions.
Step 5 Use the show interfaces or show controllers cbus command to verify the status of the FEIP2's interfaces. (If the interfaces are not configured, you must configure them using the procedures in the section "Configuring the Fast Ethernet Interfaces.")
After you verify that the new FE interface is installed correctly (the enabled LED goes on), use the privileged-level configure command to configure the new interfaces. Be prepared with the information you need, such as the following:
For a summary of the configuration options available and instructions for configuring the FE interfaces on the FEIP2, refer to the appropriate configuration publications listed in the section "If You Need More Information" on page 2.
The configure command requires privileged-level access to the EXEC command interpreter, which usually requires a password. Contact your system administrator if necessary to obtain EXEC-level access.
In the router, physical port addresses specify the actual physical location of each interface port on the router interface processor end. (See the example of an FEIP2-2TX shown in Figure 24.) This address is composed of a three-part number in the format interface processor slot number/adapter number/interface port number.
Interface ports on the FEIP2 maintain the same address regardless of whether other interface processors are installed or removed. However, when you move an FEIP2 to a different slot, the first number in the address changes to reflect the new interface processor slot number.
Figure 24 shows the interface processor slots and interface ports of a sample Cisco 7505 system. On the FEIP2-2TX, the first FE interface number is 0 and the second is 1. For example, on the FEIP2 in slot 3 (shown in Figure 24), the address of the left (first) FE interface is 3/0/0 (interface processor slot 3, FE interface 0, and interface port 0). The address of the right (second) FE interface is 3/1/0 (interface processor slot 3, FE interface 1, and interface port 0).
You can identify interface ports by physically checking the slot/adapter/interface port location on the back of the router or by using software commands to display information about a specific interface or all interfaces in the router.
This section describes a basic configuration. Press the Return key after each step unless otherwise noted. At any time you can exit the privileged level and return to the user level by entering disable at the prompt as follows:
Router# disable Router>
Following is a basic configuration procedure:
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 prompt, specify the first interface to configure by entering the subcommand interface, followed by the type (fastethernet) and slot/port (interface processor slot number/0). The example that follows is for the interface port of the first FE interface port, on an FEIP2 in interface processor slot 1:
Router(config)# interface fa 1/0/0
Step 3 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 4 Add any additional configuration subcommands required to enable routing protocols and set the interface characteristics.
Step 5 Change the shutdown state to up and enable the interface as follows:
Router(config-int)# no shutdown
Step 6 Configure additional FE interfaces as required.
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#
Following are descriptions and examples of the commands for configuring FE interface 3/0/0. Descriptions are limited to fields that are relevant for establishing and verifying the configuration. After configuring the new FE interface, use show commands to display the status of the new interface or all interfaces, or to verify changes you have made.
Depending on the requirements for your system configuration and the protocols you plan to route on the interface, you might also need to enter other configuration subcommands. For complete descriptions of configuration subcommands and the configuration options available for FE interfaces, refer to the publications listed in the section "If You Need More Information" on page 2.
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# Router(config)# interface fastethernet 3/0/0 Router(config-if)# full-duplex Ctrl-z Router#
Router# sh int fa 3/0/0 FastEthernet 3/0/0 is administratively up, line protocol is up (display text omitted) Encapsulation ARPA, loopback not set, keepalive not set, fdx, 100BaseTX
To return the interface to half-duplex operation, use the no full-duplex configuration command, as follows:
Router# config t Enter configuration commands, one per line. End with CNTL/Z. Router(config)# int fa 3/0/0 Router(config-if)# no full-duplex Ctrl-z Router#
Router# sh int fa 3/0/0 FastEthernet3/0/0 is administratively up, line protocol is up (display text omitted) Encapsulation ARPA, loopback not set, keepalive not set, hdx, 100BaseTX (display text omitted)
The RJ-45 connection is the default for FEIP2-2TX (or SC for FEIP2-2FX). To change to an MII connection and then verify it, use the following series of commands, including the media-type configuration command:
Router# config t Enter configuration commands, one per line. End with CNTL/Z. Router(config)# int fa 3/0/0 Router(config-if)# media-type mii Ctrl-z Router# sh int fa 3/0/0 FastEthernet3/0/0 is administratively up, line protocol is up (display text omitted) Encapsulation ARPA, loopback not set, keepalive not set, hdx, MII (display text omitted)
Use the media-type 100 configuration command to return the interface to its default state for RJ-45 or SC (fiber-optic) connections.
After configuring the new interface, use the show commands to display the status of the new interface or all interfaces and the ping command to check connectivity.
The following steps use show commands to verify that the new interfaces are configured and operating correctly.
Step 1 Use the show version command to display the system hardware configuration. Ensure that the list includes the new interfaces.
Step 2 Display all the current interface processors and their interfaces with the show controllers cbus command. Verify that the new FEIP2 appears in the correct slot.
Step 3 Specify one of the new interfaces with the show interfaces type slot/adapter/interface command and verify that the first line of the display specifies the interface with the correct slot number. Also verify that the interface and line protocol are in the correct state: up or down.
Step 4 Display the protocols configured for the entire system and specific interfaces with the show protocols command. If necessary, return to configuration mode to add or remove protocol routing on the system or specific interfaces.
Step 5 Display the running configuration file with the show running-config command. Display the configuration stored in NVRAM using the show startup-config command. Verify that the configuration is accurate for the system and each interface.
If the interface is down and you configured it as up, or if the displays indicate that the hardware is not functioning properly, ensure that the network interface is properly connected and terminated. If you still have problems bringing the interface up, contact a service representative for assistance.
To display information about a specific interface, use the show interfaces command with the interface type and port address in the format show interfaces [type slot/adapter/port].
Following is a partial-display example of how the show interfaces command displays status information (including the physical slot and port address) for the interface you specify. In this example, most of the status information for each interface is omitted, and an FE interface in interface processor slot 3 is shown:
Router# sh int fastethernet 2/0/0 FastEthernet2/0/0 is administratively down, line protocol is down Hardware is cyBus FastEthernet Interface, address is 0000.0ca5.2380 (bia 0000) MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255 Encapsulation ARPA, loopback not set, keepalive set (10 sec), hdx, 100BaseTX (additional displayed text omitted from this example)
Router# show interfaces fastethernet 2/0/0
FastEthernet2/0/0 is administratively down, line protocol is down
Hardware is cyBus FastEthernet Interface, address is 0000.0ca5.2380 (bia 0000)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec), hdx, 100BaseTX
ARP type: ARPA, ARP Timeout 4:00:00
Last input 3:08:43, output 3:08:42, output hang never
Last clearing of "show interface" counters 2:58:36
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 watchdog, 0 multicast
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets, 0 restarts
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
(additional displayed text omitted from this example)
The show controllers cbus command displays information about all of the interface processors in your router, including the FEIP2. Following is an example of the show controllers cbus command used with a Cisco 7500 series system:
Router# show controllers cbus
MEMD at 40000000, 2097152 bytes (unused 8256, recarves 1, lost 0)
RawQ 48000100, ReturnQ 48000108, EventQ 48000110
BufhdrQ 48000128 (2357 items), LovltrQ 48000148 (6 items, 1632 bytes)
IpcbufQ 48000158 (16 items, 4096 bytes)
IpcbufQ_classic 48000150 (8 items, 4096 bytes)
3570 buffer headers (48002000 - 4800FF10)
pool0: 11 buffers, 256 bytes, queue 48000130
pool1: 1168 buffers, 1536 bytes, queue 48000138
pool2: 4 buffers, 1568 bytes, queue 48000140
(additional displayed text omitted from this example)
slot2: FEIP2, hw 2.4, sw 21.40, ccb 5800FF40, cmdq 48000090, vps 8192
software loaded from system
IOS (tm) VIP Software (SVIP-DW-M), Released Version 11.1(10)CA [biff 138]
ROM Monitor version 17.0
FastEthernet2/0/0, addr 0003.0b33.f540 (bia 0003.0b33.f540)
gfreeq 48000138, lfreeq 480001C0 (1536 bytes), throttled 0
rxlo 4, rxhi 438, rxcurr 0, maxrxcurr 2
txq 48001A00, txacc 48001A02 (value 259), txlimit 259
FastEthernet2/1/0, addr 0003.0b33.f548 (bia 0003.0b33.f548)
gfreeq 48000138, lfreeq 480001C8 (1536 bytes), throttled 0
rxlo 4, rxhi 438, rxcurr 0, maxrxcurr 0
txq 48001A08, txacc 48001A0A (value 0), txlimit 259
(additional displayed text omitted from this example)
Following is an example of the show version command used with a Cisco 7500 series system:
Router# show version Cisco Internetwork Operating System Software IOS (tm) GS Software (RSP-JV-M), Released Version 11.1(10)CA [biff 135] Copyright (c) 1986-1997 by cisco Systems, Inc. Compiled Mon 10-Mar-97 10:06 by biff Image text-base: 0x600108A0, data-base: 0x60982000 ROM: System Bootstrap, Version 11.1(2) [biff 2], RELEASE SOFTWARE (fc1) ROM: GS Bootstrap Software (RSP-BOOT-M), Version 10.3(8), RELEASE SOFTWARE (fc2) Router uptime is 23 minutes System restarted by reload System image file is "biff/rsp-jv-mz", booted via tftp from 223.255.254.254 cisco RSP2 (R4600) processor with 32768K bytes of memory. R4700 processor, Implementation 33, Revision 1.0 Last reset from power-on G.703/E1 software, Version 1.0. SuperLAT software copyright 1990 by Meridian Technology Corp). Bridging software. X.25 software, Version 2.0, NET2, BFE and GOSIP compliant. TN3270 Emulation software (copyright 1994 by TGV Inc). Chassis Interface. (additional displayed text omitted from this example) 1 FEIP2 controller (2 FastEthernet). 2 FastEthernet/IEEE 802.3 interfaces. (additional displayed text omitted from this example) 123K bytes of non-volatile configuration memory. 8192K bytes of Flash PCMCIA card at slot 0 (Sector size 128K). 8192K bytes of Flash internal SIMM (Sector size 256K). No slave installed in slot 7. Configuration register is 0x0
To determine which type of interfaces are installed on an FEIP2 in your system, use the show diag slot command. Specific interface information is displayed, as shown in the following example of an FEIP2 in interface processor slot 2:
Router# show diag 2
Slot 2:
Physical slot 2, ~physical slot 0xD, logical slot 2, CBus 0
Microcode Status 0x4
Master Enable, LED, WCS Loaded
Board is analyzed
Pending I/O Status: None
EEPROM format version 1
FEIP2 controller, HW rev 2.4, board revision D0
Serial number: 03700746 Part number: 73-1684-03
Test history: 0x00 RMA number: 00-00-00
Flags: cisco 7000 board; 7500 compatible
EEPROM contents (hex):
0x20: 01 20 02 04 00 38 78 0A 49 06 94 03 00 00 00 00
0x30: 68 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00
Slot database information:
Flags: 0x4 Insertion time: 0x9B8 (00:17:10 ago)
Controller Memory Size: 8 MBytes DRAM, 1024 KBytes SRAM
PA Bay 0 Information:
Fast-Ethernet PA, 1 ports, 100BaseTX-ISL
EEPROM format version 1\
HW rev 1.0, Board revision A0
Serial number: 04622911 Part number: 73-1688-03
PA Bay 1 Information:
Fast-Ethernet PA, 1 ports, 100BaseTX-ISL
EEPROM format version 1
HW rev 1.0, Board revision A0
Serial number: 03540609 Part number: 73-1688-03
In the preceding example, the two FE interfaces on the FEIP2 are clearly marked 100BaseTX.
For additional Fast Ethernet command descriptions and examples, refer to the publications listed in the section "If You Need More Information" on page 2.
The packet internet groper (ping) command allows you to verify that an interface port is functioning properly and to check the path between a specific port and connected devices at various locations on the network. This section provides brief descriptions of the ping command. After you verify that the system and FEIP2 have booted successfully and are operational, you can use this command to verify the status of interface ports. Refer to the publications listed in the section "If You Need More Information" on page 2, for detailed command descriptions and examples.
The ping command sends an echo request out to a remote device at an IP address that you specify. After sending a series of signals, the command waits a specified time for the remote device to echo the signals. Each returned signal is displayed as an exclamation point (!) on the console terminal; each signal that is not returned before the specified time-out is displayed as a period (.). A series of exclamation points (!!!!!) indicates a good connection; a series of periods (.....) or the messages [timed out] or [failed] indicate that the connection failed.
Following is an example of a successful ping command to a remote server with the address 1.1.1.10:
Router# ping 1.1.1.10 <Return> Type escape sequence to abort. Sending 5, 100-byte ICMP Echoes to 1.1.1.10, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/15/64 ms Router# If the connection fails, verify that you have the correct IP address for the server and that the server is active (powered on), and repeat the ping command.
For complete descriptions of interface subcommands and the configuration options available for FEIP2-related interfaces, and which support FEIP2 functionality, refer to the publications listed in the section "If You Need More Information" on page 2.
You can download microcode to Flash memory by copying the TFTP image of a microcode version to Flash memory. When the microcode image is stored in Flash memory, you have to configure the router to use that image via the microcode vip2 flash command, then you can use the microcode reload command to manually load the new microcode file. You can then use the configure command to instruct the system to load the new image automatically at each system boot.
To compare the size of the microcode image and the amount of Flash memory available, you must know the size of the new microcode image. The image size is specified in the README file that is included on the floppy disk with the new image.
Follow these steps to download (copy) a microcode version from a TFTP server to Flash memory:
Step 1 To display the total amount of Flash memory present, its location, any files that currently exist in Flash memory and their size, and the amount of Flash memory remaining, use the show flash command. Following is an example of the output that is displayed:
Router# show flash -#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name 1 \ FFFFFFFF B4A18E0B 3F6494 30 4023316 Jun 26 1994 19:44:29 image/file/1 2 .. FFFFFFFF 8075AA5D 4118B4 23 111518 Jun 29 1994 11:05:57 image/file/2 12044568 bytes available (8533736 bytes used)
Step 2 Compare the amount of available Flash memory (last line in the preceding example) to the size of the new microcode image on the floppy disk. If you attempt to copy in a new image, and the size of the new image exceeds the available space in Flash, only part of the new image is copied, and the following error message is displayed:
buffer overflow - xxxx/xxxx
where xxxx/xxxx is the number of bytes read in/number of bytes available.
Step 3 After you verify that there is sufficient space available in Flash memory for the new image, use the command copy tftp:filename [ flash | slot0 | slot1 ]:filename to copy an image to Flash memory. (tftp:filename is the file's source and [flash | 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:vip11-1 slot0:vip11-1 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 Ethernet1/0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 7799951/15599616 bytes] CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC Router#
Step 4 Use the show flash command to verify that the microcode has been copied to Flash. The output should display the filename of the image you copied to Flash (vip11-1 in the following example):
Router# show flash -#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name 1 .. FFFFFFFF B4A18E0B 3F6494 30 4023316 Jun 26 1994 19:44:29 image/file/1 2 .. FFFFFFFF 8075AA5D 4118B4 23 111518 Jun 29 1994 11:05:57 image/file/2 3 .. FFFFFFFF EEA1FEEB 8436E8 22 600516 Oct 10 1995 19:35:25 vip11-1 7646052 bytes available (16179788 bytes used)
Step 5 To ensure that the new microcode is used when you reboot the system, add the appropriate commands to the configuration file. To modify the configuration file, enter configuration mode by issuing the configure terminal command as follows:
Router# config t Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
Step 6 Specify that you are changing the microcode for the FEIP2 (microcode vip2), and that it is to load from Flash memory (flash slot0 or slot1). Then add the filename of the new microcode image to be loaded from Flash:
Router(config)# microcode vip2 flash slot0:vip11-1
Step 7 To exit configuration mode, press Ctrl-Z.
Step 8 Copy the new configuration to nonvolatile random-access memory (NVRAM):
Router# copy running-config startup-config
Step 9 To load the new microcode immediately, you can issue the microcode reload configuration command (you must be in configuration mode to enter this command):
Router# config t Enter configuration commands, one per line. End with CNTL/Z. Router(config)# microcode reload
Immediately after you enter the microcode reload command and press Return, the system reloads all microcode. configuration mode remains enabled; after the reload is complete, press Ctrl-Z to exit from configuration mode and return to the system prompt.
Step 10 To verify that the FEIP2 is using the correct microcode, issue the show startup-config or show controllers cbus command, which indicates the currently loaded and running microcode version for each interface processor.
Router# show controllers cbus
This completes the procedure for downloading microcode to Flash memory.
The following sections provide sources for obtaining documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following sites:
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Cisco documentation is available in the following ways:
Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS (6387).
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
P3 and P4 level problems are defined as follows:
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
If you have a priority level 1 (P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
P1 and P2 level problems are defined as follows:
Posted: Mon Oct 14 13:31:26 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.