Cisco uBR10012 Universal Broadband Router Troubleshooting Guide October 2004 Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
C O N T E N T S Preface vii Purpose Audience vii vii Document Organization viii Related Documentation viii Obtaining Documentation ix Cisco.
Contents PRE Module Not Supported 3-2 PRE-1 Module Status Screen 3-2 Booting Up with Redundant PRE-1 Modules PRE-1 Module Faults 3-3 3-4 Ethernet Connection Problems 3-6 Console Port Serial Connection Problems 3-7 Troubleshooting Common System Problems 3-8 Troubleshooting System Crashes 3-8 High CPU Utilization Problems 3-9 ARP Traffic 3-9 CPUHOG Errors 3-11 Debug and System Messages 3-11 Exec and Virtual Exec Processes 3-11 Interrupts are Consuming a Large Amount of Resources 3-12 Invalid Sched
Contents CHAPTER 5 Replacing or Recovering Passwords 7-1 Password Recovery Procedure Overview Password Recovery Procedure APPENDIX A Unsupported Commands 7-1 A-1 Unsupported Frame Relay Commands HCCP Commands MLPPP Commands A-2 Unsupported PPP Commands A-3 A-3 Spectrum Management Commands Unsupported Telco-Return Commands B A-1 A-2 Unsupported MPLS VPN Commands APPENDIX 7-1 A-3 A-3 Recommended Tools and Test Equipment B-1 Testing with Digital Multimeters and Cable Testers B-1 Test
Contents Cisco uBR10012 Universal Broadband Router Troubleshooting Guide vi OL-1237-01
Preface This guide documents processes and procedures for user level hardware troubleshooting on the Cisco uBR10012 universal broadband router. For complete configuration instructions, please refer to the Cisco uBR10012 Universal Broadband Router Software Configuration Guide and the documents listed in the “Related Documentation” section on page viii.
Preface Document Organization Document Organization The sections of this guide are as follows: Chapter Description Chapter 1, “Basic Troubleshooting Tasks and Startup Issues” Basic procedures that users should perform before undertaking a detailed troubleshooting analysis of the Cisco uBR10012 router or logging a case with the Cisco Technical Assistance Center (TAC).
Preface Obtaining Documentation For more information about the IOS software that runs on the Cisco uBR10012 router, see the Cisco IOS command reference books and configuration guides: • Cisco Broadband Cable Command Reference Guide—Describes the cable specific commands used on the Cisco uBR10012 router. See the following URL: http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/i ndex.htm • Cisco IOS Release 12.
Preface Obtaining Technical Assistance You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address: Cisco Systems Attn: Customer Document Ordering 170 West Tasman Drive San Jose, CA 95134-9883 We appreciate your comments.
Preface Obtaining Additional Publications and Information TAC Case Priority Definitions To ensure that all cases are reported in a standard format, Cisco has established case priority definitions. Priority 1 (P1)—Your network is “down” or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Preface Obtaining Additional Publications and Information • Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL: http://www.cisco.com/en/US/learning/index.
C H A P T E R 1 Basic Troubleshooting Tasks and Startup Issues This section describes the basic procedures that users should perform before undertaking a detailed troubleshooting analysis of the Cisco uBR10012 router or logging a case with the Cisco Technical Assistance Center (TAC).
Chapter 1 Basic Troubleshooting Tasks and Startup Issues Confirming the Hardware Installation Confirming the Hardware Installation Start troubleshooting the installation by issuing the show hardware command. The show hardware command displays all hardware components that are recognized by the system.
Chapter 1 Basic Troubleshooting Tasks and Startup Issues Displaying the Cisco IOS Software Version 2 Gigabit Ethernet/IEEE 802.3 interface(s) 4 Cable Modem network interface(s) 509K bytes of non-volatile configuration memory. 125440K bytes of ATA PCMCIA card at slot 1 (Sector size 512 bytes). 32768K bytes of Flash internal SIMM (Sector size 256KB).
Chapter 1 Basic Troubleshooting Tasks and Startup Issues Displaying System Environment Information Displaying System Environment Information Use the show environment command to display the basic system environment status, to verify the following: • Make sure the system operating temperature is equal to or less than 41° F at the inlet and 104° F degrees at the core (5° C and 40° C). • That the fan assembly module is installed in the chassis and operating properly.
Chapter 1 Basic Troubleshooting Tasks and Startup Issues Cisco uBR10012 System Startup Sequence Figure 1-1 Hardware Troubleshooting Flowchart Turn on PEM No PEM No Power OK LED on ? Correct input wiring Troubleshoot PEM Yes PRE No Status LEDs OK ? Yes ICC+ No Status LEDs OK ? Reseat PRE and restart System startup successful PRE No status LEDs OK? See section "PEM Faults" See section "PRE Module Faults" Yes Reseat TCC+ Yes Line card LEDs on ? Yes PEM No Power OK LED on ? Yes ICC+ status
Chapter 1 Basic Troubleshooting Tasks and Startup Issues Cisco uBR10012 System Startup Sequence Table 1-1 Cisco\ uBR10000 Series System Startup Sequence Startup Event Event Description PEM is powered off The Fault LED on each PEM is lit yellow to indicate that power is being supplied to the PEM but that the router is not turned on. Power on the Cisco uBR10012 router 1. The Power LED on each PEM is lit green. 2.
C H A P T E R 2 PEM Faults and Fan Assembly Failures The following sections provide methods for troubleshooting faults involving the Cisco uBR10012 DC Power Entry Modules (PEMs), the optional 2400W AC-input power shelf, and fan assembly module.
Chapter 2 PEM Faults and Fan Assembly Failures AC PEM Faults Figure 2-1 AC PEM Front Panel POWER AC power cord clips FAULT AC power plug 62520 AC power switch Table 2-1 AC PEM LEDs LED Color Description Power Green The PEM is on, is receiving power from the AC power source, and is providing power to the Cisco uBR10012 chassis (normal operations).
Chapter 2 PEM Faults and Fan Assembly Failures DC PEM Faults Table 2-2 Tip AC PEM Fault Symptoms and Corrective Action (continued) PEM experiences problems in one slot but operates normally in a different slot 1. Ensure that the input power to both slots is correct. 2. Verify that no connections have been made to the DC-power connectors underneath each PEM. 3. If the problem persists, contact Cisco TAC. Fault LED is lit yellow 1.
Chapter 2 PEM Faults and Fan Assembly Failures DC PEM Faults Figure 2-2 DC PEM Front Panel (original model, UBR10-PWR-DC) 56480 POWER MISWIRE FAULT Figure 2-3 DC PEM Front Panel (current model with alarm connector, UBR10-PWR-DC-M) 62518 POWER MISWIRE FAULT Cisco uBR10012 Universal Broadband Router Troubleshooting Guide 2-4 OL-1237-01
Chapter 2 PEM Faults and Fan Assembly Failures 2400W AC-Input Power Shelf Table 2-3 DC PEM LEDs LED Description Power (green) PEM is powered on and is operational. Fault (yellow) PEM is not operating correctly or the circuit breaker is in the OFF position. Miswire (yellow) Input DC power cables are wired incorrectly and should be reversed. Table 2-4 lists the DC PEM fault symptoms and corrective actions.
Chapter 2 PEM Faults and Fan Assembly Failures Other Electrical Problems The power shelf includes three 1200-watt (W) AC-input power modules that plug into a common power backplane in the 2400W AC-input power shelf. Two 1200W AC-input power modules are capable of powering a fully configured Cisco uBR10012 router. The third power module provides full redundancy.
Chapter 2 PEM Faults and Fan Assembly Failures Fan Assembly Module Faults Check the site for: • Improperly grounded equipment, particularly equipment racks and power grounds • Fluctuating voltage, which can result from excessive power drains caused by other equipment (such as air conditioning units) • Cable corrosion or defective power panels, circuit breakers or fuses, or cable connections • Undersized power cables or excessive power cable lengths • Excessive power demand on backup power systems
Chapter 2 PEM Faults and Fan Assembly Failures Fan Assembly Module Faults Figure 2-6 CISCO 10000 Fan Assembly Air Circulation Pattern POWER MISWIR E FAULT CISCO 10000 C O N S O LE C O N S O LE AU X AU X A C TIV IT Y E TH E LIN RN K ET 1 OT SL 0 OT SL 1 OT SL 0 OT SL A C TIV IT E TH Y E LIN RN E T K POWER MISWIR E FAULT ALARMS A C ALARMS O A C C R M IT A O R TA TU IL C L S O R M M IT A S IC JO IN O TA TU FA IL A L R R S 56430 FA A R PERFORMANCE ROUTING ENG
Chapter 2 PEM Faults and Fan Assembly Failures Fan Assembly Module Faults Table 2-6 Symptom Fans OK LED is not lit SINGLE FAN FAILURE LED is lit Fan Assembly Module Fault Indications and Recommended Action Steps to Take 1. Make sure the fan assembly module is fully inserted into the chassis. 2. Place your hand in front of the fan assembly module outlet to determine if the fans are operating.
Chapter 2 PEM Faults and Fan Assembly Failures Fan Assembly Module Faults Cisco uBR10012 Universal Broadband Router Troubleshooting Guide 2-10 OL-1237-01
C H A P T E R 3 Troubleshooting PRE-1 Modules This chapter describes how to troubleshoot Performance Routing Engine (PRE-1) modules. It provides information on troubleshooting PRE-1 fault states, the management Ethernet port, and the serial port.
Chapter 3 Troubleshooting PRE-1 Modules PRE Module Not Supported PRE Module Not Supported The Cisco uBR10012 router supports only the PRE-1 module in Cisco IOS Release 12.2(8)BC1, and later releases.
Chapter 3 Troubleshooting PRE-1 Modules Booting Up with Redundant PRE-1 Modules Table 3-1 LED Messages on the PRE-1 Modules (continued) Message Description IOS DRVR The Cisco IOS software is initializing the driver subsystems. IOS LIB The Cisco IOS software is initializing the subsystem libraries. IOS PROT The Cisco IOS software is initializing the protocol subsystems. IOS MGMT The Cisco IOS software is initializing the management subsystems.
Chapter 3 Troubleshooting PRE-1 Modules PRE-1 Module Faults • Verify that both PRE-1 modules are booting the same version of Cisco IOS software. Slight variations in the loading of different images could allow the slot B PRE-1 module to boot first. PRE-1 Module Faults The PRE-1 module provides the IP routing and forwarding functionality in the Cisco uBR10012 router. Thus, in a non-redundant PRE-1 configuration, a PRE-1 failure is a system failure.
Chapter 3 Troubleshooting PRE-1 Modules PRE-1 Module Faults Figure 3-1 CISCO 10000 CO NS OL PRE-1 Faceplate and LEDs LED Ethernet port LEDs Status Description Activity Green Packets are being transmitted and received. Off No activity. Green Carrier detected; the port is able to pass traffic. Off No carrier detected; the port is not able to pass traffic. PCMCIA slot 0 Green Slot 0 is active. PCMCIA slot 1 Critical, Major, and Minor LEDs Green Off Slot 1 is active. No alarm.
Chapter 3 Troubleshooting PRE-1 Modules Ethernet Connection Problems Table 3-2 PRE-1 Module Fault Indications and Recommended Action The PRE-1 initializes, but you cannot establish a console connection 1. Ensure that the terminal settings are properly set. 2. If you still cannot connect, check the console cable. Is it firmly connected? Is it the correct type of cable with proper connectors? 3. If the cable checks out and you cannot establish a console or Telnet session, reinsert the PRE-1 module.
Chapter 3 Troubleshooting PRE-1 Modules Console Port Serial Connection Problems Step 2 Check that the Ethernet port in question is assigned a valid IP address. For more information about configuring Ethernet ports, refer to the Cisco uBR10012 Universal Broadband Router Software Configuration Guide. If the cable, connections, power, and configuration all check out, and you still cannot connect to the Ethernet port on the module, replace the module in question.
Chapter 3 Troubleshooting PRE-1 Modules Troubleshooting Common System Problems Step 8 The console can be frozen if the PRE-1 process is generating a large volume of debug messages. If this is the case, hit the return key a couple of times and type no debug all to attempt to turn off the debug messages. This will not work if the router is in global configuration mode, but try typing do no debug all to execute this EXEC mode command in global configuration mode.
Chapter 3 Troubleshooting PRE-1 Modules Troubleshooting Common System Problems For additional information on troubleshooting system crashes, see the following URLs: • Troubleshooting Router Crashes, at the following URL: http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_tech_note09186a00800b4447 .shtml • Less Common Types of System Crashes, at the following URL: http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_tech_note09186a008010876d .
Chapter 3 Troubleshooting PRE-1 Modules Troubleshooting Common System Problems In addition, the Cisco CMTS router automatically monitors ARP traffic and enters the IP addresses found in ARP requests into its own ARP table, in the expectation that a device will eventually be found with that IP address. Unacknowledged IP addresses remain in the router’s ARP table for 60 seconds, which means that a large volume of ARP traffic can fill the router’s ARP table.
Chapter 3 Troubleshooting PRE-1 Modules Troubleshooting Common System Problems CPUHOG Errors The router displays a %SYS-3-CPUHOG error message when a process is using an excessive amount of processor cycles. For example, using the logging buffered command to allocate a significant amount of memory (for example, 200 MB) for log buffers could generate a %SYS-3-CPUHOG message, because allocating such an amount of memory requires a large amount of processor time.
Chapter 3 Troubleshooting PRE-1 Modules Troubleshooting Common System Problems For information on resolving problems with high CPU usage caused by the Exec and Virtual EXEC processes, see the document High CPU Utilization in Exec and Virtual Exec Processes, at the following URL: http://www.cisco.com/en/US/products/hw/routers/ps359/products_tech_note09186a00801c2ae4.
Chapter 3 Troubleshooting PRE-1 Modules Troubleshooting Common System Problems For more information, see the document Troubleshooting High CPU Utilization Due to Processes, at the following URL: http://www.cisco.com/en/US/products/hw/routers/ps359/products_tech_note09186a00801c2af6.shtml Problems with Access Lists The PRE-1 module could experience high CPU usage if the router has been configured with an access list (ACL) that is too complex or inefficiently written.
Chapter 3 Troubleshooting PRE-1 Modules Troubleshooting Common System Problems Cisco Internetwork Operating System Software IOS (tm) 10000 Software (UBR10K-P6-M), Experimental Version 12.2(20031215:22350] Copyright (c) 1986-2003 by cisco Systems, Inc. Compiled Mon 15-Dec-03 17:28 by mnagai Image text-base: 0x60008968, data-base: 0x61B80000 ROM: System Bootstrap, Version 12.0(9r)SL2, RELEASE SOFTWARE (fc1) BOOTLDR: 10000 Software (C10K-EBOOT-M), Version 12.
Chapter 3 Troubleshooting PRE-1 Modules Troubleshooting Common System Problems The most effective way of using the Output Interpreter tool is to capture the output of the show stacks and show tech-support commands and upload the output into the tool. If the problem appears related to a line card, you can also try decoding the show context command. Tip For more information on troubleshooting bus errors, see the Troubleshooting Bus Error Crashes document, at the following URL: http://www.cisco.
Chapter 3 Troubleshooting PRE-1 Modules Troubleshooting Common System Problems Fatal Alignment Errors If the alignment error was a fatal error, it displays a message similar to the following: %ALIGN-1-FATAL: Corrupted program counter error. ERROR: Slot 0, NPE300/IOFE2/VXR, CACHE, External Data Cache Memory Test: *** Data Expected= 0x99999999 *** Fatal alignment errors are most likely a hardware fault on the processor card. The card itself could be faulty, or the memory on the card could be faulty.
Chapter 3 Troubleshooting PRE-1 Modules Troubleshooting Common System Problems System returned to ROM by processor memory parity error at PC 0x60301298, address 0x0 at 17:19:47 PDT Mon Dec 15 2003 System restarted at 17:19:47 PDT Mon Dec 15 2003 ... Router# Parity errors can be categorized in two different ways: • Soft parity errors occur when an energy level within the DRAM memory changes a bit from a one to a zero, or a zero to a one.
Chapter 3 Troubleshooting PRE-1 Modules Troubleshooting Common System Problems The system also allocates public pools in a number of different sizes for more general use. If a packet requires special handling, or if a packet cannot be completely processed at interrupt time, the system copies the packet into a portion of contiguous memory in the public pool, so it can be processed switched. Tip Use the show buffers command to display the current status of the router’s particle pools.
Chapter 3 Troubleshooting PRE-1 Modules Troubleshooting Common System Problems Spurious Memory Accesses A spurious memory access occurs when a Cisco IOS software process attempts to access memory in the lowest 16 KB region of memory, which is a restricted location.
Chapter 3 Troubleshooting PRE-1 Modules Troubleshooting Common System Problems Cisco uBR10012 Universal Broadband Router Troubleshooting Guide 3-20 OL-1237-01
C H A P T E R 4 Troubleshooting Line Cards This chapter discusses troubleshooting faults on the following Cisco uBR10012 line cards: • General Information for Troubleshooting Line Card Crashes, page 4-2 • Troubleshooting the Timing, Communication, and Control Plus Card, page 4-8 • Troubleshooting the OC-12 Packet-Over-SONET Line Card, page 4-12 • Troubleshooting the OC-12 Dynamic Packet Transport Spatial Reuse Protocol WAN Card, page 4-14 • Troubleshooting the Cisco uBR10012 OC-48 DPT/POS Line Ca
Chapter 4 Troubleshooting Line Cards General Information for Troubleshooting Line Card Crashes General Information for Troubleshooting Line Card Crashes Line card crashes occur when the hardware or software encounter unexpected situations that are not expected in the current design. As a general rule, they usually indicate a configuration error, a software error, or a hardware problem. Table 4-1 lists the show commands that are most useful in collecting information to troubleshoot line card crashes.
Chapter 4 Troubleshooting Line Cards General Information for Troubleshooting Line Card Crashes Slot Slot Slot Slot Slot Slot Slot 5/1: 6/0: 6/1: 7/0: 7/1: 8/0: 8/1: 0 0 0 0 0 0 0 crashes crashes crashes crashes crashes crashes crashes Router# Step 6 After identifying the particular card that crashed, use the show context command again to display more information about the most recent crash.
Chapter 4 Troubleshooting Line Cards General Information for Troubleshooting Line Card Crashes Table 4-2 Step 8 SIG Value Types SIG Value SIG Name Error Reason 22 SIGERROR Fatal hardware error 23 SIGRELOAD Software-forced crash The vast majority of line card crashes are either Cache Parity Exception (SIG type=20), Bus Error Exception (SIG type=10), and Software-forced Crashes (SIG type=23).
Chapter 4 Troubleshooting Line Cards General Information for Troubleshooting Line Card Crashes • Hard parity errors occur when a hardware defect in the DRAM or processor board causes data to be repeatedly corrupted at the same address. In general, a hard parity error occurs when more than one parity error in a particular memory region occurs in a relatively short period of time (several weeks to months).
Chapter 4 Troubleshooting Line Cards General Information for Troubleshooting Line Card Crashes Step 2 If the results from the Output Interpreter indicate a hardware-related problem, try removing and reinserting the hardware into the chassis. If this does not correct the problem, replace the DRAM chips on the hardware. If the problem persists, replace the hardware.
Chapter 4 Troubleshooting Line Cards General Information for Troubleshooting Line Card Crashes If the crash is accompanied by %IPC-3-NOBUFF messages, see Troubleshooting IPC-3-NOBUFF Messages on the Cisco 12000, 10000 and 7500 Series, at the following URL: http://www.cisco.com/en/US/products/hw/routers/ps133/products_tech_note09186a00800945a1.s html • Hardware Problem—The card might not be fully inserted into its slot, or the card hardware itself could have failed.
Chapter 4 Troubleshooting Line Cards Troubleshooting the Timing, Communication, and Control Plus Card Troubleshooting the Timing, Communication, and Control Plus Card At least one working Timing, Communication, and Control Plus (TCC+) card must be installed in the Cisco uBR10012 router for normal operations. The TCC+ card acts as a secondary processor that performs the following functions: • Generates and distributes 10.24 MHz clock references to each cable interface line card.
Chapter 4 Troubleshooting Line Cards Troubleshooting the Timing, Communication, and Control Plus Card Table 4-3 TCC+ Card LEDs and Their Functions LED Status Description POWER Green Indicates that power is supplied to the TCC+ card. Off Power is off. Yellow Indicates that the CPU is in the bootup process, self-test, or downloading code. Green Indicates that the CPU has successfully completed the boot, self-test, and code download process, and that the TCC+ card is the active card.
Chapter 4 Troubleshooting Line Cards Troubleshooting the Timing, Communication, and Control Plus Card Table 4-4 TCC+ Card Faults and Recommended Responses Fault Type Response The show cable clock command shows that no TCC+ cards are installed: 1. Verify that at least one TCC+ card is installed in the chassis. If not, install a TCC+ card, because it is required for normal operations. Router# show cable clock 2.
Chapter 4 Troubleshooting Line Cards Troubleshooting the Timing, Communication, and Control Plus Card Table 4-4 TCC+ Card Faults and Recommended Responses Fault Type The show controllers clock-reference command displays compare errors between the two TCC+ cards installed in the Cisco uBR10012 router. The show controllers command for a cable interface displays the message “Timestamp is from local oscillator.
Chapter 4 Troubleshooting Line Cards Troubleshooting the OC-12 Packet-Over-SONET Line Card Troubleshooting the OC-12 Packet-Over-SONET Line Card Figure 4-2 describes the LEDs on the Cisco uBR10-1OC12/P-SMI OC-12 Packet-Over-SONET (POS) line card faceplate. Use these descriptions to verify the operation of the OC-12 POS line card.
Chapter 4 Troubleshooting Line Cards Troubleshooting the OC-12 Packet-Over-SONET Line Card Table 4-5 OC-12 POS Line Card Fault Indications and Recommended Action Fault Fail LED is lit indicating that the line card has failed Carrier LED is off and interface is enabled Fail LED blinks then lights steadily repeatedly or Card seems to be passing traffic (Tx/Rx lights), but cannot communicate with the PRE Corrective Action 1. Reinsert the line card. 2. Replace the line card. 3.
Chapter 4 Troubleshooting Line Cards Troubleshooting the OC-12 Dynamic Packet Transport Spatial Reuse Protocol WAN Card Troubleshooting the OC-12 Dynamic Packet Transport Spatial Reuse Protocol WAN Card Figure 4-3 shows and Table 4-6 describes the LEDs on the Cisco BR10-SRP-OC12SML Dynamic Packet Transport (DPT) Spatial Reuse Protocol (SRP) WAN card.
Chapter 4 Troubleshooting Line Cards Troubleshooting the OC-12 Dynamic Packet Transport Spatial Reuse Protocol WAN Card Table 4-6 Cisco uBR10-SRP-OC12SML DPT WAN Line Card LEDs (continued) LED Status Description RX PKTS (Packets) Blinking Green Indicates that the DPT port line has received a packet. This LED flickers in normal operation, indicating traffic. Off No traffic Amber Indicates that the DPT port line is in a pass-through state. Off Not active.
Chapter 4 Troubleshooting Line Cards Troubleshooting the Cisco uBR10012 OC-48 DPT/POS Line Card Troubleshooting the Cisco uBR10012 OC-48 DPT/POS Line Card The Cisco OC-48 DPT⁄ POS interface module has a pair of OC-48c, fiber-optic standard connector (SC) duplex ports that provide an SC connection for either the single-mode short-reach or single-mode long-reach version. Figure 4-4 shows the faceplate on the Cisco OC-48 DPT⁄ POS interface module, and Table 4-7 describes each LED.
Chapter 4 Troubleshooting Line Cards Troubleshooting the Cisco uBR10012 OC-48 DPT/POS Line Card Table 4-7 Cisco OC-48 DPT LED Status and Description LED Status Description SYNC Green Off Card synchronized to mate card Yellow Off Interface is wrapped Yellow Off DPT port line is in a pass-through state DPT port line not in pass-through state WRAP PASS THRU Card not synchronized Interface not wrapped Cisco uBR10012 Universal Broadband Router Troubleshooting Guide OL-1237-01 4-17
Chapter 4 Troubleshooting Line Cards Troubleshooting the Gigabit Ethernet Line Card Troubleshooting the Gigabit Ethernet Line Card Figure 4-5 describes the LEDs on the Cisco uBR10-1GE Gigabit Ethernet line card faceplate to help you verify correct operation. Make sure that the gigabit Ethernet Interface Converter (GBIC) type on the Cisco uBR10012 router matches the GBIC type at the other end of the fiber optic cable.
Chapter 4 Troubleshooting Line Cards Troubleshooting the Gigabit Ethernet Line Card Table 4-8 describes the gigabit Ethernet line card fault indications and suggests responses to each. Table 4-8 Gigabit Ethernet Line Card Faults and Recommended Responses Fault Type Response Fail LED is lit yellow indicating that a major fault has disabled the card Fail LED blinks then lights steadily repeatedly or Card seems to be passing traffic (Tx/Rx lights), but cannot communicate with the PRE 1.
Chapter 4 Troubleshooting Line Cards Troubleshooting the Gigabit Ethernet Line Card Cisco uBR10012 Universal Broadband Router Troubleshooting Guide 4-20 OL-1237-01
C H A P T E R 5 Replacing or Recovering Passwords This section describes how to recover a lost enable or console login password, and how to replace a lost enable secret password on the Cisco uBR10012 router. Note It is possible to recover the enable or console login password. The enable secret password is encrypted, however, and must be replaced with a new enable secret password. Password Recovery Procedure Overview The following is an overview of the steps in the password recovery procedure.
Chapter 5 Replacing or Recovering Passwords Password Recovery Procedure Step 2 Configure the terminal to operate at 9600 baud, 8 data bits, no parity, and 1 stop bit. Step 3 If you can log in to the router as a nonprivileged user, enter the show version command to display the existing configuration register value, then go to Step 6. If you cannot log in to the router at all, go to the next step. Step 4 Press the Break key or send a break signal from the console terminal.
Chapter 5 Replacing or Recovering Passwords Password Recovery Procedure Caution Step 12 Do not execute the next step unless you have determined you must change or replace the enable, enable secret, or console login passwords. Failure to follow the steps as shown might cause you to erase the router configuration. Enter the copy startup-config running-config command to load the startup configuration file into running memory. This action allows you to modify or replace passwords in the configuration.
Chapter 5 Replacing or Recovering Passwords Password Recovery Procedure Cisco uBR10012 Universal Broadband Router Troubleshooting Guide 5-4 OL-1237-01
A P P E N D I X A Unsupported Commands The following are lists of the commands that are present but not supported for the Cisco uBR10012 router in various releases of the Cisco IOS software.
Appendix A Unsupported Commands HCCP Commands • frame-relay map ip ip-address dlci [broadcast] [cisco | ietf] [nocompress] tcp header-compression {active | passive} • frame-relay mincir {in | out} bps • frame-relay traffic-rate average [peak] • frame-relay traffic-shaping • show frame-relay ip [rtp | tcp] header-compression [interface] HCCP Commands The following commands are supported in Cisco IOS Release 12.2(8)BC2 and later 12.2 BC releases.
Appendix A Unsupported Commands Unsupported MPLS VPN Commands Unsupported MPLS VPN Commands The following commands are not supported in any Cisco IOS software release. • ip vrf • ip vrf forwarding • mpls ip • mpls label-protocol ldp • show ip protocols vrf • show ip vrf • show ip route vrf Unsupported PPP Commands The following commands are not supported in any Cisco IOS software release.
Appendix A Unsupported Commands Unsupported Telco-Return Commands • cable telco-return spd factory-default • cable telco-return spd manual-dial • cable telco-return spd password • cable telco-return spd phonenum • cable telco-return spd ppp-authenticate • cable telco-return spd radius-realm • cable telco-return spd service-provider • cable telco-return spd threshold • cable telco-return spd username • debug cable telco-return • debug telco-return msg Cisco uBR10012 Universal Broadba
A P P E N D I X B Recommended Tools and Test Equipment Table B-1 lists the basic tools and test equipment necessary to perform general maintenance and troubleshooting tasks on the Cisco uBR10012 router. Table B-1 Recommended Tools and Test Equipment Equipment Description Number 2 Phillips and flat-head screwdrivers Small and medium-sized. Voltage tester Refer to the “Testing with Digital Multimeters and Cable Testers” section on page B-1.
Appendix B Recommended Tools and Test Equipment Testing with TDRs and OTDRs Test fiber-optic cable both before installation (on-the-reel testing) and after installation. Continuity testing of the fiber requires either a visible light source or a reflectometer. Light sources capable of providing light at the three predominant wavelengths, 850 nanometers (nm), 1300 nm, and 1550 nm, are used with power meters that can measure the same wavelengths and test attenuation and return loss in the fiber.
Appendix B Recommended Tools and Test Equipment Testing with Breakout Boxes, Fox Boxes, and BERTs/BLERTs Testing with Breakout Boxes, Fox Boxes, and BERTs/BLERTs Use breakout boxes, fox boxes, and bit/block error rate testers (BERTs/BLERTs) to measure the digital signals present at: • PCs • Printers • Modems • CSU/DSUs These devices can monitor data line conditions, analyze and trap data, and diagnose problems common to data communication systems.
Appendix B Recommended Tools and Test Equipment Testing with Network Analyzers Testing with Network Analyzers Use network analyzers (also called protocol analyzers) to decode protocol layers in a recorded frame and present the layers as readable abbreviations or summaries, detailing which layer is involved (physical, data link, and so forth) and the function each byte or byte content serves.
I N D EX cable power command A 4-8 cable proxy-arp command access-list compiled command access lists 3-13 cable testers 3-13 AC PEM faults OC-12 POS OC-12 DPT/SRP 4-14 CD LED 4-9 correctable 3-15 4-16 commands, unsupported 3-15 confreg command 3-16 console alphanumeric display list of messages messages 4-13 Cisco IOS, displaying version alignment errors fatal 4-4 Carrier LED ACTIVE LED TCC+ B-1 cache parity errors 2-1 to 2-3 3-10 console port 1-6 7-2 3-7 3-7 console probl
Index enable secret command hw-module slot reset command 7-3 environmental information, displaying Ethernet problems exec processes 4-7 1-4 3-6 I 3-11 interrupts spurious F 3-18 IP input processing 3-12 Fail LED Gigabit Ethernet 4-19 OC-12 POS line card OC-48 DPT/POS fallbacks L 4-13 4-16 LEDs 3-17 ACTIVE, OC-12 DPT/SRP fan assembly failures 2-7 ACTIVE, TCC+ fatal alignment errors 3-16 alarm faults 4-9 3-6 Carrier, OC-12 POS PRE-1 module 3-5 4-14 4-13 CD, OC-48 DPT/POS
Index PRE-1 module MPLS VPN commands 3-4 to 3-6 PRESENT, TCC+ 4-9 RX, OC-48 DPT/POS 4-16 RX CARRIER, OC-12 DPT/SRP RX PKTS, OC-12 DPT/SRP SRP, OC-48 DPT/POS Status 4-14 4-16 4-14 N network analyzers B-4 network monitors B-3 3-4 STATUS, OC-12 DPT/SRP STATUS, TCC+ TCC+ 4-14 O 4-9 SYNC, OC-48 DPT/POS 4-17 OC-12 DPT/SRP 4-8 transmit LEDs 4-12, 4-18 4-14 troubleshooting TX, OC-48 DPT/POS 4-16 WRAP, OC-48 DPT/POS LEDs 4-12 troubleshooting bus errors 4-5 4-4 LEDs 4-6 4-16 t
Index OC-12 DPT/SRP TCC+ Output Interpreter 4-14 show buffers 4-9 PPP commands show context 3-1 alphanumeric display faults show diag 3-3 1-6, 3-2 support for PRE-1 module and not PRE module PRE-1 module LEDs unlit 3-5 1-1, 1-2 show interface 3-6 show log PRE module 4-6 show region 3-14 show stacks 3-15, 4-5 show version support for PRE-1 module and not PRE module 3-2 PRESENT LED 7-1 3-1, 3-15, 4-4, 4-5, 4-7 1-3, 3-13, 3-16, 4-2, 7-1, 7-2 SIG type values slot problems 4-3 3
Index redundant PRE-1 modules T scheduler problems TCC+ 4-8 spurious interrupts troubleshooting TDR 3-12 software forced crashes LEDs 4-8 system crashes telco-return commands terminal settings test equipment 4-6 3-18 spurious memory accesses B-2 A-3 TCC+ B-1 B-2 Timing, Communication, and Control Plus card, see also TCC+ card tools and test equipment 3-8 4-8 test equipment time domain reflectometers 3-19 3-8 system problems 3-8 3-3 TTY lines B-1 3-11 TX LED OC-48 DPT/POS 4-16
Index Cisco uBR10012 Universal Broadband Router Troubleshooting Guide IN-6 OL-1237-01
