|
|
Product Number: LC-OC12-DS3(=), LC-OC12-DS3-B(=)
This publication contains instructions for installing and configuring the channelized OC-12 to DS3 line card (OC12-DS3) in a Cisco 12000 series Gigabit Switch Router (GSR) to enable direct termination of isolated DS3 circuits on the router.
This section contains important information about additional documentation, Cisco IOS software configuration, safety, and technical support. It also describes important operating considerations for your line card.
 |
Note You can access Cisco IOS software documentation and hardware installation and maintenance documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, and http://www-europe.cisco.com. If you are reading Cisco documentation on the World Wide Web, you can submit comments electronically. Click Feedback on the toolbar, and then select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments. |
The Cisco Documentation CD-ROM package provides comprehensive documentation on the entire Cisco product line. The CD-ROM package contains documents in both Adobe portable document format (PDF), viewable with Adobe Acrobat Reader, and hypertext markup language (HTML) files, viewable with a Web browser.
The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly; therefore, it might be more up to date than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription.
For hardware installation and maintenance information on the Cisco 12000 series routers, refer to the installation and configuration guide that shipped with your Cisco 12000 series router.
Also refer to the field-replacable unit (FRU) publications that describe how to install, maintain, and replace router subsystems, such as cooling fans, power supplies, chassis backplanes, and so on.
The Cisco IOS software that runs on your router contains extensive features and functionality.
For Cisco IOS software configuration information and support, refer to the configuration and command reference publications in the Cisco IOS software configuration documentation set that corresponds to the Cisco IOS software release installed on your Cisco hardware. You can also refer to the Cisco IOS software release notes for the version of Cisco IOS software you are using on your router.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Refer to "Cisco Connection Online," at the end of this publication, for complete information on how to obtain support through CCO.
You can also contact Cisco Customer Service at 800 553-6387 or 408 526-7208 (U.S.). Customer Service hours are 5:00 a.m. to 6:00 p.m. Pacific time, Monday through Friday (excluding company holidays). You can also send e-mail to cs-rep@cisco.com.
You may also find useful information in the Cisco Information Packet that shipped with your router.
The Cisco 12000 series router must have at least one clock and scheduler card (CSC) installed that provides a one-quarter bandwidth to support the requirements of the OC12-DS3 line cards. Refer to the appropriate Cisco 12000 series router Installation and Configuration Guide for more information about your router.
Before you begin the procedures in this publication, review the safety guidelines in this section to avoid injuring yourself or damaging the equipment.
For information on regulatory compliance and safety, refer to the Regulatory Compliance and Safety Information publication that shipped with your linecard. This publication contains important safety information that you must read and understand before attempting to install, remove, or modify any hardware in your Cisco 12000 series router.
Safety warnings appear throughout this publication in procedures that, if performed incorrectly, may harm you. A warning symbol precedes each warning statement. The following paragraph is an example of a safety warning. It identifies the warning symbol and associates it with a bodily injury hazard. The remaining paragraphs in this section are translations of the initial safety warning.
 |
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. |
|
Warning For Australian installations, this customer equipment must be installed and maintained by service personnel as defined by the Australia and New Zealand standard, AS/NZS 3260. Incorrect connection of equipment to the General Purpose Outlet could result in a hazardous situation. Safety requirements are not fulfilled unless the equipment is connected to a wall socket outlet with protective ground. |
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.
Electrostatic discharge (ESD) damage, which can occur when electronic cards or components are improperly handled, results in complete or intermittent failures. The OC12-DS3 line card consists of a printed circuit card that is fixed in a metal carrier. Electromagnetic interference (EMI) shielding and connectors are integral components of the carrier. Although the metal carrier helps to protect the board from ESD, use a preventive ESD strap whenever you are handling a line card.
Following are guidelines for preventing ESD damage:
 |
Caution For safety, periodically check the resistance value of the ESD strap. The measurement should be between 1 and 10 megohms. |
The Cisco 12000 series Gigabit Switch Routers provide high-speed, high-volume routing of packets and ATM cells. The Cisco 12000 series includes the following platforms, all sharing a similar architecture:
The GSR architecture offers the following features and capabilities in providing support to IP-based local-area networks (LANs) and wide-area networks (WANs):
In addition, the system allows for redundant, field-replaceable units (FRUs).
The OC12-DS3 line card provides 12 channels of DS3 multiplexed over a single 622-Mbps OC-12 port. The OC12-DS3 line card interfaces through an Add Drop Multiplexer (ADM) with other DS3 line cards at DS3 line rates in a configuration that usually consists of a Cisco 7200 series router and a Cisco 7500 series router configured with the POET port adapter, or a third-party T3 DSU such as Digital Link, Larscom, or Kentrox.
The OC12-DS3 line card interfaces with the Cisco 12000 series GSR switch fabric and provides one OC-12 duplex SC single-mode intermediate-reach Synchronous Optical Network (SONET) connection. (See Figure 1)
You can configure and monitor each of the following features that the OC12-DS3 line card supports on a per channel basis:
Each line card has the following main components:
Figure 2 shows a high-level block diagram of the OC12-DS3 line card.
The single-mode transceiver provides a full-duplex, 622-Mbps, 1300-nm, laser-based SONET compliant interface. With a power rating of -15 to -8 dBm (transmission) and -28 to -8 dBm (receiving), the single-mode transceiver operates at a distance of up to 15 km. The actual distance in any given case depends on the quality of the fiber attached to the transceiver. The single-mode interface meets both IEC 825 and CDRH Class I safety standards.
The burst buffer (512 KB) prevents the dropping of packets when there are instantaneous increases in the number of back-to-back small packets being transmitted at DS3 line rates. Burst buffers provide high throughput and smooth out the arriving packet burst for the Layer 3 switch processor.
Each line card has two silicon queuing engines: receive and transmit. The receive engine moves packets from the burst buffer to the switch fabric, and the transmit engine moves packets from the switch fabric to the transmit interface.
When an incoming IP packet is clocked into the silicon queuing engine, the silicon queuing engine verifies the packet's integrity by checking the cyclic redundancy check (CRC) value, transfers the IP packet to buffer memory, and then tells the Layer 3 switching accelerator the location of the IP packet. At the same time, the forwarding processor tells the silicon queuing engine the virtual output queue where the IP packet is to be placed.
Each virtual output queue represents a line card. This placement of the IP packets in a virtual output queue is based on the decision made by the forwarding processor. There is one virtual output queue for each line card, plus a dedicated virtual output queue for multicast service.
The transmit silicon queuing engine moves the packet from the switch fabric to the transmit buffer and then to the transmit interface.
The silicon queuing engine controls the placement of IP packets in buffer memory as well as their removal from buffer memory. The default packet buffer memory is 32 MB, which includes 16 MB of receive (Rx) buffers and 16 MB of transmit (Tx) buffers. The buffer memory can be increased to 64 MB of receive buffers and 64 MB of transmit buffers. The buffers can support delays comparable to the longest round trip delays measured in the Internet at OC-12c/STM-1c line rates.
The Layer 3 switching accelerator assists the forwarding processor. It is a specially designed application-specific integrated circuit (ASIC) that optimizes access to the Layer 2 and Layer 3 information within each packet. This access process must be executed as rapidly as possible, which is why an ASIC is used.
A forwarding processor makes forwarding decisions based on the information in the Cisco Express Forwarding (CEF) table and the Layer 2 and Layer 3 information in the packet. The Gigabit Route Processor (GRP) constantly updates forwarding information in the forwarding table based on the latest information in the routing table. The forwarding processor is an R5000 RISC processor operating at 200 MHz.
Once the forwarding decision has been made, the forwarding processor notifies the silicon queuing engine, which places the packet in the proper queue.
This partitioning between the Layer 2 switching accelerator and the forwarding processor blends the high throughput of hardware-accelerated forwarding with the flexibility of software-based routing.
The switch fabric interface is the same 1.25-Gbps, full-duplex data path to the switching fabric that is used by the GRP. Once a packet is in the proper queue, the switch fabric interface issues a request to the master clock scheduler on the clock scheduler card. The scheduler issues a grant and transfers the packet across the switching fabric.
A maintenance bus (MBus) module on the line card responds to requests from the master MBus module on the GRP. The line card MBus module can report temperature and voltage information to the master MBus module. In addition, the MBus module on the line card contains the ID-EEPROM, which stores the serial number, hardware revision level, and other information about the card.
Each line card maintains CEF tables. These tables, derived from routing tables maintained by the GRP, are used by the line card processor to make forwarding decisions. Large networks may require more DRAM to support large CEF tables. For information on adding memory to a line card, see the document Cisco 12000 Series Gigabit Switch Router Memory Replacement Instructions.
This section provides information to help you prepare to install and configure the OC12-DS3 line card and contains safety and ESD-prevention guidelines. The following sections describe prerequisites and preparation information:
We recommend that you do the following before beginning any of the procedures in this publication:
You need the following tools and parts to remove and replace a line card. If you need additional equipment, contact your service representative for ordering information.
There are two versions of the OC12-DS3 line card.
The show version, show diag, 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 Configuration Fundamentals Configuration Guide and Configuration Fundamentals Command Reference publications, which are available on CCO, the Documentation CD-ROM, or as printed copies.
In the following example of the show version command, the running system software, Release 11.2(11)GS2, is displayed in italics.
Router# show version Cisco Internetwork Operating System Software IOS (tm) GS Software (GSR-P-M), Experimental Version 12.0(19990920:194311) [ama] Copyright (c) 1986-1999 by cisco Systems, Inc. Compiled Mon 06-Dec-99 11:55 by anewday Image text-base: 0x60010908, data-base: 0x60F92000 ROM: System Bootstrap, Version 11.2(9)GS5, [tamb 176] RELEASE SOFTWARE) BOOTFLASH: GS Software (GSR-BOOT-M), Version 11.2(9)GS4, RELEASE SOFTWARE)
(Remainder of displayed text omitted from example)
The show diag command displays the line card microcode version, as in the following example:
Router# show diag
SLOT 0 (RP/LC 0 ): 6 Port Packet over DS3
MAIN: type 47, 800-5022-01 rev 77 dev 0
HW config: 0x00 SW key: 00-00-00
PCA: 73-3847-02 rev 72 ver 2
HW version 1.0 S/N SAK0316005J
MBUS: MBUS Agent (1) 73-2146-07 rev B0 dev 0
HW version 1.2 S/N CAB031112A2
Test hist: 0x00 RMA#: 00-00-00 RMA hist: 0x00
DIAG: Test count: 0x00000001 Test results: 0x00000000
MBUS Agent Software version 01.40 (RAM) (ROM version is 01.33)
Using CAN Bus A
ROM Monitor version 10.00
Fabric Downloader version used 13.04 (ROM version is 13.04)
Primary clock is CSC 1
Board is analyzed
Board State is Line Card Enabled (IOS RUN )
Insertion time: 00:00:10 (1d15h ago)
DRAM size: 33554432 bytes
FrFab SDRAM size: 16777216 bytes
ToFab SDRAM size: 16777216 bytes
(Remainder of displayed text omitted from example.)
If the screen output indicates that the system software is running a version earlier than Cisco IOS Release 12.0(5)S, check the contents of Flash memory to determine whether the required images are available on your system. The show flash command displays a list of all files stored in Flash memory. If you do not have the correct software version, contact Cisco customer service.
The OC12-DS3 line card has a hardware revision level of 73-5452-01 A0 or later. The hardware revision number is printed on a label affixed to the component side of the card. You can also display the hardware revision number by using the show diag and show hardware commands.
The SONET specification for fiber-optic transmission defines single-mode fiber. Signals can travel farther through single-mode fiber than through multimode fiber.
The maximum distance for single-mode installations is determined by the amount of light loss in the fiber path. Good quality single-mode fiber with very few splices can carry an OC-12 signal 9.3 miles (15 km) or more. If your environment requires the signal to travel close to the typical maximum distance (as listed in Table 1), you should use an optical time domain reflectometer (OTDR) to measure the power loss.
| Transceiver | Power Budget | Transmit Power | Receive Power | Typical Maximum Distance |
|---|---|---|---|---|
Single mode | 12 dB | -15 to -8 dBm1 at 1270 to 1380 nm2 | -28 to -8 dBm | 9.3 miles (15 km) |
| 1dBm = decibels per milliwatt 2nm = nanometer |
The OC12-DS3 line card is available with the memory options described in Table 2 and Table 3. Refer to the Cisco 12000 Series Gigabit Switch Router Memory Replacement Instructions publication for installation procedures if you are upgrading or replacing line card memory.
| Product Option | Description |
|---|---|
MEM-DFT-GRP/LC-64 | 64 MB (default) |
MEM-GRP/LC-128 | 128 MB (orderable upgrade) |
Table 3 lists the available configurations and associated product numbers of SDRAM DIMMs for upgrading transmit and receive buffer memory on Cisco 12000 series GSR line cards.
| Packet Memory Size | DIMM Modules1 | Cisco Product Number |
64 MB | 2 32-MB DIMMs | MEM-LC-PKT-642 |
128 MB | 2 64-MB DIMMs | MEM-LC-PKT-1283 |
This section describes the line card slot locations in the following Cisco 12000 series routers:
Before installing your line card into the router, verify that a line card slot is available.
Figure 3 shows the location of the line card slots in the Cisco 12016 GSR. The Cisco 12016 GSR chassis has three integral card cages: the upper card cage, the lower card cage, and the switch fabric card cage. You can install line cards in the upper or lower card cage.
The upper card cage has eight user-configurable slots that support the following types of cards in the quantities indicated:
|
Note If the router is equipped with an optional, redundant GRP, it must be installed in the far left slot of the lower card cage (slot 8). If the router is not equipped with an optional, redundant GRP, a line card can be installed in slot 8 of the lower card cage. |
The lower card cage in the Cisco 12016 GSR has eight user-configurable slots, numbered 8 through 15, that support the following types of cards in the quantities indicated:
|
Note The lower card cage is an inverted, or head-down, copy of the upper card cage, meaning cards are installed the same way they are installed in the upper card cage, but in an inverted or head-down orientation. |
Figure 4 shows the location of the line card slots in the Cisco 12012 GSR. The Cisco 12012 GSR upper card cage contains 12 slots that accommodate the following types of cards in the quantities indicated:
Cisco 12000 series line cards---From one to eleven line cards of different types can be installed in the line card slots in the upper cage (slots 0 through 12). Although you can install a line card in slot 0, the established convention is for the primary GRP to occupy this slot. Figure 4 shows a OC12-DS3 line card installed in slots 2 and 3, respectively.
Figure 5 shows the location of the line card slots in the Cisco 12008 GSR. The Cisco 12008 GSR upper card cage contains ten slots that accommodate the following types of cards in the quantities indicated:
Use a single-mode optical-fiber interface cable to connect your Cisco 12000 series router to another router or switch. In general, single-mode cables are yellow. Cables are available from the following cable vendors: AMP, Anixter, AT&T, Red-Hawk, and Siemens.
|
Note Single-mode optical-fiber cables are not available from Cisco Systems. |
For SONET single-mode optical-fiber connections, use one duplex SC-type connector (see Figure 6) or two simplex SC-type connectors (see Figure 7).
Attach either one duplex fiber cable or two simplex fiber cables between the line card and the device to which the line card is connected. Observe the receive (Rx) and transmit (Tx) cable relationship shown in Figure 8.
|
Warning Invisible laser radiation can be emitted from the aperture of the port when no cable is connected. Avoid exposure to laser radiation and do not stare into open apertures. |
|
Warning Class 1 laser product. |
The cable-management system in the Cisco 12000 series router organizes the interface cables entering and exiting the system, keeping them out of the way and free of sharp bends. Excessive bending in an interface cable can degrade performance and possibly harm the cable.
The cable-management system consists of two separate components:
Figure 9 shows a generic cable-management tray and cable-management bracket mounted on a Cisco 12012 GSR. The cable-management tray on the Cisco 12008 GSR is similar in form and function to the cable-management tray on the Cisco 12012 GSR.
|
Note When shipped with spare line card orders, the cable management bracket is not attached to the line card. You must attach the cable-management bracket to the line card before you insert the line card into the GSR. |
|
Caution Do not use the cable-management bracket as a handle to pull out or push in the line card. The cable-management bracket is designed to hold the interface cables and may break if you use the bracket to push, pull, or carry the line card after it is removed from the GSR. |
Figure 10 shows a cable-management bracket for the OC12-DS3 line card.
The Cisco 12016 has a cable-management tray for the upper card cage that is positioned above the upper line card slots, and a cable-management tray for the lower card cage that is positioned below the lower line card slots. In addition, there are vertical cable troughs on either side of the card cages that keep the cables organized and secured. Figure 11 shows the location of the upper and lower cable-management trays for the Cisco 12016 router.
This section describes the procedure for installing or replacing a line card in a Cisco 12000 series router. (Read the following section, "Guidelines for Line Card Removal and Installation," before removing a line card while power to the system is on.)
|
Note The procedures in the following sections use illustrations of a Cisco 12012 GSR to support the descriptions of removing and installing line cards. Although the card cages of the Cisco 12000 series routers differ in the number of card slots, the designated use of slots and the process of removing and installing a line card are basically the same. Therefore, separate procedures and illustrations for the Cisco 12016 GSR and Cisco 12008 GSR are not included in this publication. |
You can remove and replace line cards while the system is operating; you do not need to issue software commands or reset the system power. This functionality allows you to add, remove, or replace line cards 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.
When you install a line card, the system automatically downloads the necessary software from the GRP. After that, the system brings online only those interfaces that match the current configuration and were previously configured as up. You must configure all others with the configure command. (For line card configuration information, see the section "Configuring the OC12-DS3 Line Card,".)
|
Caution The system can indicate a hardware failure if you do not follow proper procedures. To avoid erroneous failure messages, remove or insert only one line card at a time. Allow at least 15 seconds for the system to complete the preceding tasks before removing or inserting another line card. |
Each line card has two ejector levers that allow you to release the card from its backplane connector when you are removing the line card, and to firmly seat the line card in its backplane connector when you are installing the line card. The ejector levers align and seat the card connectors in the backplane. (See Figure 12.)
When you remove a line card, always use the ejector levers to ensure that the card connector pins disconnect from the backplane in the logical sequence expected by the system. Any card that is only partially connected to the backplane can halt the system.
Similarly, when you install a line card, always use the ejector levers to ensure that the card is correctly aligned with the backplane connector, the card connector pins make contact with the backplane in the correct order, and the card is fully seated in the backplane. A card that is only partially seated in the backplane will cause the system to hang and, subsequently, crash.
Line cards support online insertion and removal (OIR), which means that you can remove and replace line cards while the system remains powered up.
|
Note Before you remove a line card, Cisco recommends that you use the shutdown command to disable the interfaces to prevent anomalies when you reinstall the new or reconfigured line card. When you shut down an interface, it is designated as administratively down in the show command display. |
To remove a line card, use Figure 12 as a reference and perform the following procedure:
Step 2 Disconnect the cable connectors from the line card ports.
Step 3 Disconnect and remove the line card cables and line card cable-management bracket.
|
Note Do not remove the cables from the line card cable-management bracket. |
Step 4 Use a Phillips screwdriver to loosen the captive screw at each end of the line card faceplate. (See Figure 12a.)
|
Caution When you are removing a line card, always use the ejector levers to ensure that the card connector pins disconnect from the backplane in the logical sequence expected by the system. A card that is only partially connected to the backplane can halt the system. |
Step 5 Simultaneously pivot the ejector levers away from each other to release the line card from the backplane connector. (See Figure 12b.)
Step 6 Grasp the ejector levers and pull the line card halfway out of the slot.
Step 7 Grasp the line card faceplate with one hand and pull the line card straight out of the slot, keeping your other hand under the line card to guide it. (See Figure 12c.) Avoid touching the line card printed circuit board, components, or any connector pins.
Step 8 Place the removed line card on an antistatic mat or foam pad, or place it in an antistatic bag if you plan to return it to the factory.
Step 9 If the line card slot is to remain empty, install a line card blank (Cisco product number 800-03004-01) to keep dust out of the chassis and to maintain proper airflow through the line card compartment. Secure the line card blank to the chassis by tightening its captive screws.
A line card slides into any available line card slot and connects directly to the backplane.
If you install a new line card, you must first remove the line card blank from the available slot. Refer to the procedures in the previous section, "Removing a Line Card."
|
Note You can install the line card in any available line card slot. For information on line card slot locations, refer to the section "Cisco 12000 Series Line Card Slot Locations," earlier in this publication. |
|
Caution The system can indicate a hardware failure if you do not follow proper procedures. Remove or insert only one line card at a time. Allow at least 15 seconds for the system to complete the preceding task before removing or inserting another line card. |
Use the following procedure to install a line card:
Step 2 Attach an ESD wrist strap to your wrist and to the ESD connection socket on the chassis or to a bare metal surface on the chassis or frame.
Step 3 Choose an available slot for the line card, and verify that the line card's interface cable is long enough for you to connect the line card to any external equipment. Use the fiber optic cable connectors to connect the local line card Rx and Tx ports. Use the fiber optic cable connectors to connect the line card Rx and Tx ports to other devices.
|
Caution To prevent ESD damage, handle line cards by the card carrier edges only. |
Step 4 Grasp the faceplate of the line card with one hand and place your other hand under the card carrier to support the weight of the card; position the card for insertion into the card cage slot. Avoid touching the line card printed circuit board, components, or any connector pins.
Step 5 Carefully slide the line card into the slot until the ejector levers make contact with the edges of the card cage, then stop. Make sure the ejector lever hooks catch the lip of the card cage. (See Figure 13.)
|
Caution When you are installing a line card, always use the ejector levers to ensure that the card is correctly aligned with the backplane connector, that the card connector pins make contact with the backplane in the correct order, and the card is fully seated in the backplane. A card that is only partially seated in the backplane will cause the system to hang and, subsequently, crash. |
Step 6 Simultaneously pivot both ejector levers toward each other until they are perpendicular to the line card faceplate. This action firmly seats the card in the backplane.
Step 7 Use a Phillips screwdriver to tighten the captive screw on each end of the line card faceplate to ensure proper EMI shielding and to prevent the line card from becoming partially dislodged from the backplane. (These screws must be tightened to meet EMI specifications.)
|
Caution To ensure that there is adequate space for additional line cards, always tighten the captive installation screws on each newly installed line card before you insert any additional line cards. These screws also prevent accidental removal and provide proper grounding and EMI shielding for the system. |
Step 8 Reinstall the line card cable-management bracket (see Figure 12, shown previously):
a. Unhook the line card cable-management bracket from the chassis cable-management tray or bracket.
b. Position the line card cable-management bracket over the front of the line card faceplate.
c. Insert and tighten the captive screw at each end of the line card cable-management bracket to secure the bracket to the line card.
Step 9 Plug the cable connectors into their original ports on the line card faceplate.
This section contains the following procedures:
|
Note The cable-management bracket provided with your line card may have a different number of cable clips or a different clip design than that shown in the installation diagram. (See Figure 14.) The installation instructions are the same for all types of cable-management brackets. |
In the following procedure, we assume that you have installed a new line card in the router. You must also install a line card cable-management bracket on the OC12-DS3 Line Card line card. See Figure 10 for the cable-management bracket that is specific to the OC12-DS3 Line Card line card.
To install a line card cable-management bracket on a line card, perform the following steps:
Step 2 Attach the line card cable-management bracket to the line card as follows:
a. Position the line card cable-management bracket over the front of the line card faceplate.
b. Insert and tighten the captive screw at each end of the line card cable-management bracket to secure the bracket to the line card.
Step 3 Connect the interface cable to the line card port. (See Figure 14a.)
Step 4 Carefully press the interface cable into the cable clip on the end of the cable standoff. (See in Figure 14b.) Avoid any kinks or sharp bends in cable.
To remove the interface cables from a line card cable-management bracket and to remove the cable-management bracket from a line card, perform the following steps:
Step 2 On a piece of paper, note the current interface cable connections to the ports on each line card.
Step 3 Starting with the interface cable for the bottom port on the line card (for cards with multiple ports), disconnect the cable from the line card port. (See Figure 15a.)
Step 4 Proceeding upward, remove the interface cable from the cable clip on the end of the cable standoff. (See Figure 15b.)
Repeat Step 3 through Step 4 for any other interface cables on the line card ports, then proceed to Step 5.
Step 5 Loosen the captive installation screw at each end of the line card cable-management bracket and remove the bracket from the line card.
After you have installed the line card and connected the interface cables, verify that the line card is working properly by checking the LEDs on the faceplate of the line card. Each OC12-DS3 line card provides the following two types of LEDs (see Figure 1) for monitoring the operating status of the line card:
During a typical line card boot process
To verify that the line card is working properly, perform the following operational checks:
There are two, four-digit alphanumeric LED displays at one end of the faceplate, near the ejector lever. These LEDs display messages telling you the state of the card. In general, the LEDs do not turn on until the GRP has discovered and powered up the card. It is normal for a message displayed as part of a sequence or process to appear too briefly to be read. Table 4 and Table 5 list the alphanumeric LED messages.
As it boots, the line card displays a sequence of messages that is similar to that shown in Table 4.
| LED Display1 | Meaning | Source |
|---|---|---|
MROM | The MBus microcode begins to execute; nnnn is the microcode version number. For example, microcode version 1.33 or above would display as 01172. This display might not be visible because it occurs for only a brief time. | MBus controller |
LMEM | Low memory on the line card is being tested. | Line card ROM monitor |
LROM | Low memory test has been completed. | Line card ROM monitor |
BSS | Main memory is being initialized. | Line card ROM monitor |
RST | The contents of the reset reason register are being saved. | Line card ROM monitor |
IO | Reset I/O register is being accessed. | Line card ROM monitor |
EXPT | Interrupt handlers are being initialized. | Line card ROM monitor |
TLB | TLB is being initialized. | Line card ROM monitor |
CACH | CPU data and instruction cache is being initialized. | Line card ROM monitor |
MEM | The size of main memory on the line card is being discovered. | Line card ROM monitor |
LROM | The ROM is ready for the download attempt. | Line card ROM monitor |
ROMI | The ROM image is being loaded into line card memory. | GRP IOS software |
FABL | The line card is waiting for the loading of the fabric downloader.3 | GRP IOS software |
FABL | The fabric downloader is being loaded into line card memory. | GRP IOS software |
FABL | The fabric downloader is being launched. | GRP IOS software |
FABL | The fabric downloader has been launched and is running. | GRP IOS software |
IOS | The Cisco IOS software is being downloaded into line card memory. | GRP IOS software |
IOS | The Cisco IOS software is being launched. | GRP IOS software |
IOS | The Cisco IOS software is running. | GRP IOS software |
IOS | The line card is enabled and ready for use. | GRP IOS software |
| 1The LED sequence shown in Table 4 might occur too quickly for you to read; therefore, this sequence is provided in this tabular form as a baseline for how the line cards should function at startup. 2The version of MBus microcode running on your system might be different. 3The fabric downloader loads the Cisco IOS software image onto the line card. |
Table 5 lists other messages displayed on the line card alphanumeric LED.
| LED Display | Meaning | Source |
|---|---|---|
MRAM | The MBus microcode begins to execute; nnnn is the microcode version number. For example, microcode version 1.17 would display as 01171. This display might not be visible because it shows for only a brief time. | MBus controller |
MAL | Card malfunction. | GRP |
PWR | Card not powered. | GRP |
PWR | Card powered. | GRP |
IN | In reset. | GRP |
RSET | Reset complete. | GRP |
MBUS | MBus agent downloading. | GRP |
MBUS | MBus agent download complete. | GRP |
ROMI | Getting ROM images. | GRP |
ROMI | Acquisition of ROM image complete. | GRP |
MSTR | Waiting for mastership determination. | GRP |
CLOK | Waiting for slot clock configuration. | GRP |
CLOK | Slot clock configuration done. | GRP |
FABL | Loading fabric downloader2 complete. | GRP |
FABI | Waiting for fabric initialization to complete. | GRP |
IOS | Downloading of Cisco IOS software is complete. | GRP |
BMA | Cisco IOS software BMA error. | GRP |
FIA | Cisco IOS fabric interface ASIC configuration error. | GRP |
CARV | Buffer carving failure. | GRP |
DUMP | Line card requesting a core dump. | GRP |
DUMP | Line card dumping core. | GRP |
DUMP | Line card core dump complete. | GRP |
DIAG | Diagnostic mode. | GRP |
FDAG | Downloading field diagnostics. | GRP |
FDAG | Launching field diagnostics. | GRP |
POST | Launching power-on self-test (POST). | GRP |
UNKN | Unknown state. | GRP |
| 1The version of MBus microcode running on your system might be different. 2The fabric downloader loads the Cisco IOS software image onto the line card. |
Next to the port on the OC12-DS3 line card are two green LEDs labeled Active and Carrier. See Figure 1. These LEDs signal the status of the port (see Table 6).
| LED State | Explanation | |
| Active | Carrier | |
Off | Off | Card is off. |
On | Off | Card is on. |
On | On | Controller is up. |
The status LEDs on the line card might not go on until you have configured the line card interfaces (or turned them on if they were shut down). In order to verify correct operation of the interface, complete the configuration procedures for the line card (refer to the section "Configuring the OC12-DS3 Line Card,").
If the Active LED on a line card does not come on, verify the following conditions:
To verify that the line card is connected correctly, perform the following procedure:
Step 2 When the reinitialization is complete, verify that the Active LED on the OC12-DS3 line card is on and remains on. If the LED does stay on, proceed to Step 5. If the Active LED does not stay on, proceed to the next step.
Step 3 If the Active LED on the OC12-DS3 line card fails to go on, determine if the OC12-DS3 line card board connector is fully seated in the backplane. Loosen the captive installation screws, and firmly pivot the ejector levers toward each other until both are perpendicular to the OC12-DS3 line card faceplate. Tighten the captive installation screws.
After the system reinitializes the interfaces, the Active LED on the OC12-DS3 line card should go on. If the Active LED goes on, go to Step 5. If the Active LED does not go on, go to the next step.
Step 4 If the Active LED still fails to go on, remove the OC12-DS3 line card and try installing it in another available line card slot.
Step 5 Use the show interfaces command to verify the status of the interface. (If the interface is not configured, you must use the procedures in the section "Configuring the OC12-DS3 Line Card.")
If an error message displays on the console terminal, refer to the appropriate reference publication for error message definitions. If you experience other problems that you are unable to solve, contact a service representative for assistance.
For more information on troubleshooting and diagnostics, consult the installation and configuration guide that came with your Cisco 12000 series router.
The following sections provide information for configuring and verifying the configuration. Examples are also included.
After you verify that the new OC12-DS3 line card is installed correctly (the Active LED goes on), use the configure command to configure the new OC-12 controller. A Cisco 12000 series router identifies a controller by slot/port.
The current OC-12 controller configurable parameter settings are displayed as part of the show controller oc12 number/0 command, as in the following example:
Router# show controller oc12 1/0
OC12_CH_DS31/0
The current state of the controller is up
Current configurable parameter settings:
Clock source is LINE, Payload scrambling is ON
Loopback is NONE
Router#
(Remainder of displayed text omitted from example)
Table 7 shows the default OC-12 controller configuration of an OC12-DS3 line card in a Cisco 12000 series router. In controller configuration mode, select an OC-12 controller for configuration using the controller oc12 slot/port command.
| Parameter | Configuration Command | Default Value |
|---|---|---|
Clock source | [no] clock source [internal | line] | line |
Encapsulation | [no] scramble | scramble |
Loop internal | [no] loopback [internal | line] | no loopback |
Shutdown | [no] shutdown | no shutdown |
The following steps make up a basic controller configuration for the OC12-DS3 line card on a Cisco 12000 series router.
Router# configure terminal Router(config)#
Step 2 Enter controller configuration mode by entering the controller OC-12 slot/port global configuration command and specify the router slot number and port number:
Router(config)# controller OC12 1/0 Router(config-controller)#
Step 3 Set the clock source by entering the clock source controller configuration command and specify line or internal:
Router(config-controller)# [no] clock source {line | internal}
Router(config-controller)#
Use the no form of this command to restore the default value, line.
Step 4 To change the OC-12 controller payload scrambling:
Router(config-controller)# [no] scramble Router(config-controller)#
Use the no form of this command to remove scrambling. The default value is scrambling.
Step 5 To change the OC-12 controller loopback mode:
Router(config-controller)# [no] loopback {line | internal}
Router(config-controller)#
Use the no form of this command to remove the loop.
Step 6 To change the shutdown state to up and enable the controller, enter the no shutdown controller configuration command:
Router(config-controller)# [no] shutdown Router(config-controller)#
The no shutdown command passes an enable command to the OC12-DS3 line card. It also causes the line card to configure itself based on the previous configuration commands sent.
After you verify the OC-12 controller configuration, you can configure the associated DS3 channel and serial interfaces on the OC-12 controller. Be prepared with the information you will need, such as the interface IP address.
The following sections describe how to enable an interface and specify IP routing. You may also need to enter other configuration commands, depending on your system configuration requirements. For descriptions of configuration commands and the configuration options available, refer to the appropriate software publications listed in the section "Important Information."
A Cisco 12000 series router identifies an interface on the OC12-DS3 line card by its chassis slot number, line card port number, and DS3 channel number, in the format slot/port:channel. For example, the slot/port:channel# address of the first DS3 serial interface on an OC12-DS3 line card installed in line card slot 1 is 1/0:1. The port number is 0.
Table 7 shows the default DS3 serial interface configuration of an enabled line card. At the prompt, specify the new interface to configure by entering the interface command, followed by the type (serial) and slot/port:channel#.
| Parameter | Configuration Command | Default Value |
|---|---|---|
Cyclic Redundancy Check | crc [16 | 32] | 16 |
Encapsulation | encapsulation [hdlc | ppp] | hdlc |
Framing | framing {c-bit | m13} | c-bit |
Idle character mode | [no] idle-character [flags | marks] | flags |
Invert data | [no] invert data | No invert data |
Keepalive | [no] keepalive | keepalive |
Maximum transmission unit (mtu) | [no] mtu bytes | 4470 bytes |
Transmitter delay | [no] transmitter-delay # of idle characters | 0 |
Use the following procedures to configure the OC12-DS3 line card:
Router> enable Router#
Press the Return key after each configuration step, unless otherwise noted.
Step 2 Enter global configuration mode by entering the configure terminal command:
Router# configure terminal Router(config)#
Step 3 Select an OC-12 controller for configuration by entering the controller oc12 global configuration command and specify the chassis slot and port number:
Router(config)# controller oc12 slot/port Router(config-controller)#
Step 4 Specify framing by selecting the DS3 channel number, then enter the ds3 channel framing c-bit controller configuration command:
Router(config-controller)# ds3 1 framing c-bit Router(config-controller)#
Step 5 Enable payload scrambling by selecting the DS3 channel number and by entering the ds3 channel scramble controller configuration command:
Router(config-controller)# ds3 1 scramble Router(config-controller)#
Step 6 To exit controller configuration mode, enter the exit command to return to global configuration mode:
Router(config-controller)# Router(config)#
Step 7 At the global configuration mode prompt, specify the new interface to configure by entering the interface command, followed by the type (serial) and slot/port:channel# (line card slot number/port number:channel number). The prompt changes to interface configuration mode. The following example is for an OC12-DS3 line card in chassis slot 1:
Router(config)# interface serial 1/0:1 Router(config-if)#
Step 8 Assign an IP address and subnet mask to the interface with the ip address configuration command, as in the following example:
Router(config-if)# ip address 10.1.2.3 255.0.0.0 Router(config-if)#
Step 9 Turn off keepalive messages:
Router(config-if)# no keepalive Router(config-if)#
Although some encapsulations benefit from keepalive processing (e.g., HDLS), the Cisco 12000 series routers do not require keepalive messages.
Step 10 Change the shutdown state to up and enable the interface:
Router(config-if)# no shutdown Router(config-if)#
The no shutdown command passes an enable command to the OC12-DS3 line card. It also causes the line card to configure itself based on the previous configuration commands sent.
Step 11 Add any other configuration commands required to enable routing protocols and adjust the interface characteristics.
Step 12 When you have included all of the configuration commands to complete the configuration, type end or enter ^Z (hold down the Control key while you press Z) to exit configuration mode.
Step 13 Write the new configuration to memory:
Router# copy running-config startup-config Router#
The system displays an OK message when the configuration has been stored.
After you have completed your configuration, you can check it using show commands. For an explanation of show commands, see the section "Using show Commands to Check System Status".
The OC12-DS3 line card consists of high-density DS3 service through twelve channels that provide DS3 interfaces through fiber-optic connectors for the Cisco 12000 series Gigabit Switch Router (GSR). There are two sides to the network, a local (near-end) side and a remote (far-end) side. The OC12-DS3 line card supports three third-party data service unit (DSU) vendors, Digital-Link, Kentrox, and Larscom, and Internet Service Provider (ISP)-provided DS3 lines to enable connections between a GSR and another device.
You can connect the local (near-end) DS3 port to the remote (far-end) DS3 port using a third-party DSU. Then use the telnet command from the local DS3 port to communicate with the remote DS3 port to verify the DSU mode settings. If necessary, change the DSU mode settings on the local DS3 port to match the DSU mode settings on the remote DS3 port. When the local and remote DS3 ports are configured with matching DSU mode settings, you can start passing data traffic between the near-end and the far-end of the network.
If the telnet command does not allow the local DS3 port to communicate with the remote DS3 port, it indicates that the DSU mode settings on the local and remote DS3 ports do not match using a third-party DSU. You can establish direct communication by removing the third-party DSU between the local and remote DS3 ports, and using the default DSU mode, Cisco. When you establish a direct connection between the local and remote DS3 ports, you can use Cisco IOS software commands that are specific to the Cisco Remote Connection Management feature to verify the DSU mode settings on the remote DS3 port, see Table 7. After the local and remote DS3 configuration settings match and you verify network connectivity, you can reinsert a third-party DSU into the configuration.
The Cisco Remote Connection Management feature is Cisco-proprietary. It works only with the channelized OC12-DS3 line card and the 6DS3-SMB or 12DS3-SMB line cards in Cisco 12000 series routers.
Table 9 shows the default DS3 channel configuration of an enabled OC12-DS3 line card. In controller configuration mode, select an OC-12 controller for configuration using the controller oc12 slot/port command.
| Parameter | Configuration Command | Default Value |
|---|---|---|
DS3 channel, framing mode | [no] ds3 channel# framing [c-bit | m13] | c-bit |
DS3 channel, dsu mode | [no] ds3 channel# dsu mode [cisco | digital-link | kentrox | larscom] | cisco |
DS3 channel, dsu subrate bandwidth | [no] ds3 channel# dsu bandwidth Kilobits/sec | 44210 |
DS3 channel, remote requests | [no] ds3 channel# dsu remote accept | accept |
DS3 channel, far-end DSU bandwidth | [no] ds3 channel# dsu remote fullrate | user-configured value |
DS3 channel, payload scrambling | [no] ds3 channel# scramble | no scramble |
DS3 channel, loopback mode | [no] ds3 channel# loopback [local | network | remote] | no loopback |
DS3 channel, BERT testing | [no] ds3 channel# bert pattern [2^15 | 2^20 | 2^23 | 0s | 1s ] interval [1-1440] | no BERT |
|
Note You can use Cisco Remote Connection Management only if (1) both ends of the DS3 line are configured for C-bit parity mode, and (2) the FEAC message from the DS3 payload source terminal to the DS3 payload sink terminal is delivered unaltered. |
The Cisco Remote Connection Management feature uses two Cisco-proprietary DS3 C-bit parity Far-End Alarm and Control (FEAC) messages that are not used in the American National Standards Institute (ANSI) standard. Table 10 explains the commands that generate the FEAC messages.
| Confirmation Message | FEAC Code | Default Value | Commands |
|---|---|---|---|
DEFAULT_SUBRATE_CONFIG | 0x0CFF | fullrate | Router (config-if)# dsu remote fullrate |
REMOVE_DEFAULT_SUBRATE_CONFIG | 0x08FF | user-configured | Router (config-if)# dsu remote fullrate |
|
Note The local port and the remote port must have matching configuration. |
The following sections explain how to use Cisco IOS commands for Cisco Remote Connection Management. Table 9 lists the command parameters.
You can use telnet to determine the DSU mode settings on the remote DS3 port. Once you verify the remote DS3 port settings, you can change the local configuration parameters so that DSU mode settings are the same on both the local and remote DS3 ports. You can set the DSU bandwidth to accept or reject the incoming remote requests from the local DS3 port by entering the dsu remote accept interface configuration command.
The DSU mode supports three third-party DSU vendors---Digital-Link, Kentrox, and Larscom---and the default DSU mode, Cisco. If you use a DSU to make the connection between the Cisco 12000 series router and another device, the local DS3 port configuration must match the remote DS3 port configuration. Therefore, if the remote DS3 port uses the Kentrox vendor, a request is sent to the local DS3 port to change the DSU mode to Kentrox, by manually entering the dsu mode configuration command and specifying the Kentrox DSU. If you make a direct connection between a Cisco 12000 series router and another device, you can use the default DSU mode, Cisco. See Figure 16 for configuration examples.
The local and remote DS3 ports must also agree on whether to use a subrate or fullrate sending and receiving rate, because the speed of the sending and receiving rate is regulated by the DSU mode. If the sending and receiving rates do not match, they will not work. Subrates are specific to DSU modes and must be configured appropriately. The subrate sending and receiving rate is slower and less expensive than the faster, more expensive, fullrate. You can synchronize the local and remote DS3 ports sending and receiving rates by entering the dsu remote interface configuration command.
The DSU bandwidth range is from 0 to 44210 kbps. The local port and the remote port must have matching configuration. Therefore, if you reduce the effective bandwidth to 3000 on the local port, you must do the same on the remote port by entering the dsu bandwidth interface configuration command.
Payload (data) scrambling converts the data received by the local or remote DS3 ports from any of the three supported third-party DSU vendor modes (Digital-Link, Kentrox, and Larscom) as well as the default, Cisco mode. To enable payload scrambling on the local and remote DS3 ports, you must enter the scramble interface configuration command. If you do not enter the scramble command, payload scrambling remains disabled by default on the local and remote DS3 ports.
The OC12-DS3 line card uses a 16-bit Cyclic Redundancy Check by default, but also supports a 32-bit CRC to detect errors in transmitted data. You can set the CRC by entering the crc interface configuration command. The router that sends the data divides the bits in the frame message by a predetermined number to calculate a frame check sequence (FCS). Before sending the data, the router appends the FCS value to ensure that the frame message contents are exactly divisible by a predetermined number. The router that receives the data divides the frame message by the same predetermined number and calculates the FCS. If the result is not 0, the router that receives the data assumes that a transmission error occurred and sends a request to the router to resend the data.
|
Note When enabling a 16-bit or 32-bit CRC on a local interface, ensure that the remote device is also configured for a 16-bit or 32-bit CRC. |
The only exception for matching local and remote DS3 port configurations is that the clock sources must be set opposite each other. Therefore, if you enter the clock source line interface configuration command for the local DS3 port, you must enter clock source internal for the remote DS3 port. The ADM clock source is configured to internal.
In interface configuration mode, specify DS3 framing by entering the framing [c-bit | m13] interface configuration. Use the no form of this command to return to the default, c-bit framing.
Figure 16 shows two OC12-DS3 line card configuration examples. In the first example, the OC12-DS3 line card is channel 1 in router slot 1, is connected to a Cisco 7500 router with an HSSI port through an external DSU.
In the second example, the OC12-DS3 line card is channel 5 in router slot 1, is connected to a Cisco 7200 router with a T3 serial port adapter with integrated DSUs/CSUs.
The following example shows a typical configuration for a channel, associated with an OC12-DS3 line card, that is connected to a Cisco 7200 series router with a T3 serial port adapter (see Figure 16):
Router# configure terminal Router(config)# interface serial 1/0:5 Router(config-if)# dsu mode cisco Router(config-if)# dsu bandwidth 44210 Router(config-if)# framing c-bit Router(config-if)# no scramble Router(config-if)# crc 16 Router(config-if)# keepalive Router(config-if)# ip address 1.1.5.1 255.255.255.0 Router(config-if)# no shutdown
Each Cisco 12000 series line card maintains information about its configuration, traffic, errors, and so on. You can access this information by using the show commands. Following are descriptions and examples of the show commands.
Router#show interfaces serial 1/0:1 Serial1/0:1 is up, line protocol is up Hardware is OC12-Channelized-to-DS3 channel Internet address is 101.5.1.2/24 MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec, rely 255/255, load 1/255 Encapsulation HDLC, crc 16, loopback not set Keepalive set (10 sec) Last input 00:00:05, output 00:00:03, output hang never Last clearing of "show interface" counters 1d16h Queueing strategy: fifo 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 18617 packets input, 1537679 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 parity 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 16834 packets output, 2198122 bytes, 0 underruns 0 output errors, 0 applique, 0 interface resets 0 output buffer failures, 0 output buffers swapped out 0 carrier transitionsRouter#
Router# attach slot 1 slot1# enable slot1#
Router# show controllers oc12 1/0 OC12_CH_DS31/0 The current state of the controller is up Current configurable parameter settings: Clock source is INTERNAL, Loopback is NONE SECTION LOF = 0 LOS = 0 RDOOL = 0 BIP(B1) = 0 Active Alarms: None LINE AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0 Active Alarms: None PATH 1 AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 Active Alarms: None S1S0 = 02, C2 = 04 PATH TRACE BUFFER : STABLE PATH 2 AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 Active Alarms: None S1S0 = 03, C2 = FF PATH TRACE BUFFER : STABLE Router#
Verify the Cisco Remote Connection Management configuration by entering the show controllers oc12 slot/port:channel# command, as shown in the following example:
Router# show controllers oc12 1/0:1 Controller OC12 1/0, interface Serial1/0:1 (DS3 channel 1) cdb = 0x616BED10, base_hwidb = 0x613B5540, hwidb = 0x613B6520 ssb = 0x616C46A0, ds = 0x616C43E8 Line state is up rxLOS inactive, rxLOF inactive, rxAIS inactive txAIS inactive, rxRAI inactive, txRAI inactive Current configurable parameter settings: Loopback is none, Framing is c-bit DSU mode is cisco, DSU bandwidth limit is 44210 Payload scrambling is disabled, CRC is 16 Bert pattern is disabled, Bert interval is 0 Transmitter delay is 0, Encapsulation is HDLC Idle character is flags, Invert data is disabled Remote fullrate has no request outstanding Remote accept is enabled, MTU is 4470 MIB information: Data in current interval (366 seconds elapsed): 0 Line Code Violations, 0 P-bit Coding Violations 0 C-bit Coding Violations 0 P-bit Err Secs, 0 P-bit Sev Err Secs 0 Sev Err Framing Secs, 0 Unavailable Secs 0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Sev Err Secs No alarms detected. Router#
Router# show controllers oc12 detail OC12_CH_DS31/0 The current state of the controller is up Current configurable parameter settings: Clock source is INTERNAL, Loopback is NONE SECTION LOF = 0 LOS = 0 RDOOL = 0 BIP(B1) = 0 Active Alarms: None LINE AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0 Active Alarms: None PATH 1 AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 Active Alarms: None S1S0 = 02, C2 = 04 PATH TRACE BUFFER : STABLE 61 6D 69 74 2D 62 66 72 00 00 00 00 00 00 00 00 anew-day........ 00 00 00 00 00 00 00 00 53 65 72 69 61 6C 35 2F ........Serial5/ 30 3A 31 00 00 00 31 30 31 2E 35 2E 31 2E 31 00 0:1...101.5.1.1. 00 00 00 00 00 00 30 30 30 30 30 30 30 30 0D 0A ......00000000.. PATH 2 AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0 LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0 Active Alarms: None S1S0 = 03, C2 = FF PATH TRACE BUFFER : STABLE FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ Router
Router# show running-config Building configuration... Current configuration: ! ! No configuration change since last restart ! version 12.0 no service pad service timestamps debug uptime service timestamps log uptime no service password-encryption service internal ! clock timezone PST -8 clock summer-time PDT recurring clock calendar-valid ! ip subnet-zero ip ftp source-interface Ethernet0 ip ftp username anewday ip ftp password anewday no ip domain-lookup ip host apark 201.205.254.254 frame-relay switching clns routing ! controller OC12 1/0 clock source internal ! ! interface Serial0/0 ip address 100.0.0.0 255.255.255.0 no ip directed-broadcast ! interface Serial0/1 ip address 100.1.1.1 255.255.255.0 no ip directed-broadcast encapsulation ppp crc 32 dsu mode kentrox ! interface Serial0/2 ip address 100.2.2.2 255.255.255.0 no ip directed-broadcast dsu mode larscom dsu bandwidth 30000 clock source internal !
(Remainder of displayed text omitted from example)
The OC12-DS3 line card supports loopback modes for both the OC-12 controller and for each of the associated DS3 channels. Specify the loopback mode by entering one of the loopback interface configuration commands shown in Table 11. Use the no form of this command to restore the default value, no loopback, which represents the normal operation between the local end (Tx) and the remote end (Rx).
| Loopback modes | Configuration Mode | Command |
|---|---|---|
Diagnostic or local loopback | loopback local | Router(config-if)# loopback local |
Network loopback | loopback network | Router(config-if)# loopback network |
Remote loopback | loopback remote | Router(config-if)# loopback remote |
Default value | default value | Router(config-if)# no loopback |
Figure 17 shows data flows for the various loopback modes.
The OC-12 controller supports two loopback modes:
Router(config-controller)# loopback internal Router(config-controller)#
Router(config-controller)# loopback line Router(config-controller)#
The DS3 channel supports three loopback modes:
Router(config-controller)# ds3 1 loopback local Router(config-controller)#
Router(config-controller)# ds3 1 loopback network Router(config-controller)#
Router(config-controller)# ds3 1 loopback remote Router(config-controller)#
You can set one local DS3 serial port to BERT mode while the remaining local serial ports continue to transmit and receive normal traffic. A Bit Error Rate Test (BERT) checks communication between the local and the remote DS3 ports. If traffic is not being transmitted or received, create a back-to-back loopback BERT test and send out a predictable stream to ensure that you receive the same data that was transmitted. To determine if the remote DS3 serial port returns the bert pattern unchanged, the system administrator for the remote router must manually set the remote DS3 serial port to loopback network line, while you enter a bert pattern interface configuration command at specified time intervals on the local DS3 serial port.
The following example shows the output from a back-to-back loopback BERT test. The router types are a Cisco 12012 series GSR on the local (near-end), and a Cisco 12008 series router on the remote (far-end). Keepalive is disabled, while the loopback network line test runs between both routers. Clock source is set to internal on the local serial port 8, in slot 1 with IP address 10.0.0.2. Clock source is set to line on the remote serial port 5, in slot 1 with IP address 11.0.0.1. A BERT pattern is entered between local serial port 8/1 and remote serial port 5/1:
clock source internal----------clock source line no keepalive -------------------loopback network line----------no keepalive Router:[gsr-1] -----------------[mfr-1] [BERT Pattern] Serial8/1----------------------Serial5/1 [11.0.0.2]---------------------[11.0.0.1] Router(config)# interface serial 6/0 Router(config-if)# bert pattern 2^23 interval 10 Router(config-if)#
Table 12 lists the BERT patterns, explains how to invoke them, and specifies test intervals between 1 to 1140 minutes long. The no bert pattern interface configuration command terminates an ongoing BERT test and returns the local and remote DS3 serial ports to the default value.
| BERT Pattern | To Invoke | Command |
|---|---|---|
2^15 | A pseudo-random repeating pattern that is 32767 bits long | Router (config-if)# bert pattern 2^15 interval 10 |
2^20 | A pseudo-random repeating pattern that is 1048575 bits long | Router (config-if)# bert pattern 2^20 interval 10 |
qrss 2^20 | A quasi-random signal source | Router (config-if)# bert pattern qrss |
2^23 | A pseudo-random repeating pattern that is 8388607 bits long | Router (config-if)# bert pattern 2^23 interval 10 |
Following is an example of the bert pattern command and specified time intervals that will cause the BERT to send the pseudo-random pattern 2^23 and repeat on the first DS3 channel for 10 minutes:
Router# configure terminal Router(config)# interface serial 1/0:1 Router(config-if)# bert pattern 2^23 interval 10 Router(config-if)# end Router(config)# end Router#
To insert intentional errors into the BERT test stream, use the following command syntax: bert errors [no-of-errors], where the no-of-errors default is 1 and the range is 1 to 255, inclusive. The following example shows the command used to insert 5 errors into the current BERT test stream that is running the pseudo-random pattern 2^23 that repeats on the first DS3 channel for 10 minutes:
Router# configure terminal Router(config)# interface serial 1/0:1 Router(config-if)# bert pattern 2^23 interval 10 Router(config-if)# bert errors 5 Router(config-if)# end Router(config)# end Router#
When the DS3 serial port is running a BERT, the serial port state is down, and only BERT data is passed. You can use show commands shown in Table 13 to verify if the line card state is up or down.
| Commands | Explanation |
|---|---|
show controller serial n/port | Shows the current controller status, where n is the slot number. |
show controller serial 1/0 bert | Shows the fields of a BERT test that is still in progress. |
The following output indicates that BERT is enabled with a pattern of 2^23 and an interval of 10 minutes:
Router# show controller serial 1/0:1 bert Interface Serial1/0 (DS3 port 1) BERT information: State :enabled (sync'd) Pattern :2^23 Interval :10 minutes Time remaining :00:09:44 Total errors :0 Time this sync :00:00:10 Errors this sync :0 Sync count :1 Router#
|
Note The bit error test patterns from the serial ports on a OC12-DS3 line card are framed test patterns; therefore, they are inserted into the payload of a framed T3 signal. |
The following example shows the information of a BERT test that is still in progress:
Router# show controller OC12 serial 1/0:1 bert Interface Serial1/0:1 (DS3 port 1) BERT information: State :enabled (sync'd) Pattern :2^23 Interval :10 minutes Time remaining :00:01:44 Total errors :0 Time this sync :00:08:10 Errors this sync :0 Sync count :1 Router#
|
Note When the DS3 is running a BERT, the Total Bit Errors value is not valid if the Status field is Not Sync. |
The following is an example of a screen display from a completed BERT test:
Router# show controller OC12 serial 1/0:1 bert Interface Serial1/0:1 (DS3 port 1) BERT information: State :disabled (sync'd, completed) Pattern :2^23 Interval :10 minutes Time remaining :00:00:00 Total errors :0 Time this sync :00:09:54 Errors this sync :0 Sync count :1 Router#
Table 14 provides explanations of the BERT display fields in the previous examples:
| Bert Information | Explanation |
|---|---|
State: enabled (not synchronized | BERT is active, but the hardware has not currently synchronized. Errors are counted only when the hardware has synchronized. |
State: enabled (synchronized) | BERT is active, and the hardware has synchronized. Any errors encountered are counted. |
State: disabled (not synchronized, failed) | BERT test is finished and the test resulted in failure, either because the hardware never synchronized or the PLIM (physical layer interface module) declared the test a failure. |
State: disabled (synchronized, completed) | BERT test is finished because the interval expired. |
State: disabled (synchronized, aborted) | BERT test is finished as a result of a user request (for example, no bert) |
Pattern | Can be any one of the supported BERT patterns. |
Interval | Can be any value from 1 to 1440 (units are in minutes). |
Time remaining | Can be any value from 1 second to the interval provided, formatted as hh:mm:ss. |
Total errors | The total number of errors encountered while the hardware is synchronized. |
Time this synchronization | If the hardware is currently synchronized, the amount of time since synchronization began, formatted as hh:mm:ss. If it is not currently synchronized but was synchronized earlier, indicates the amount of time that the last or most recent synchronization period lasted; formatted as hh:mm:ss. |
Errors this synchronization | If the hardware is currently synchronized, the number of errors encountered during the current sync period. If it is not currently synchronized but was synchronized earlier, the number of errors encountered during the last or most recent synchronization period. |
Synchronization count | The number of times synchronization was achieved. |
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.
You can determine whether your equipment is causing interference by turning it off. If the interference stops, it was probably caused by the Cisco equipment or one of its peripheral devices. If the equipment causes interference to radio or television reception, try to correct the interference by using one or more of the following measures:
Modifications to this product not authorized by Cisco Systems, Inc. could void the FCC approval and negate your authority to operate the product.
This class A digital apparatus complies with Canadian ICES-003.
Cet appareil numerique de la classe A est conforme a la norme NMB-003 du Canada.
This is a class B product based on the standard of the Voluntary Control Council for Interference from Information Technology Equipment (VCCI). If this is used near a radio or television receiver in a domestic environment, it may cause radio interference. Install and use the equipment according to the instruction manual.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
|
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com. |
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
Posted: Wed Jul 19 19:15:01 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.