You are on page 1of 16

CHAPTER

4

Troubleshooting
There are several ways to troubleshoot problems associated with installation and
performance. For instance, the LEDs on the front panel provide the quickest way to evaluate
the operation of the hub. The statistics provided by the Hub Manager or SNMP
management station can provide more details about the cause of connectivity and
performance problems. In addition, the power-on self-test (POST) determines if the hub is
functioning properly when powered up.
Potential problems and corrective actions are discussed under the following topics in this
chapter:




Diagnosing problems
Understanding POST results
Using the diagnostic console (FastHub 400M models only)
Where to access new firmware releases (FastHub 400M models only)

Diagnosing Problems
Table 4-1 lists symptoms, possible causes, and corrective actions associated with



Poor performance.
No connectivity.
No access to management interfaces. (FastHub 400M models only)

Troubleshooting 4-1

straight-through cables. Port statistics show excessive FCS. Excessive flooding of unicast packets to the switched uplink module Switched uplink module might have reached the maximum 1536 MAC addresses in memory and needs to be cleared. Run the adapter card diagnostic utility. or alignment errors. Reduce the cable length to within the recommended distances. or vice-versa. Reset the installed switched uplink module to clear the address table. FastHub 400 10/100 Series Installation and Configuration Guide .” for the correct pinouts and the proper use of crossover vs. the total distance between the two end stations exceeds the 100BaseT cabling guidelines. No connectivity Incorrect or bad cable. • Bad cable. • Let both ports autonegotiate port speed. See your 100BaseT repeater documentation for cabling guidelines. For 100BaseTX connections: • The distance between the port and the attached device exceeds 100 meters. Reduce the cable length to within the recommended distances. See Appendix B. Excessive errors found in port statistics.Diagnosing Problems Table 4-1 Common Problems and Their Solutions Symptom Possible Cause Resolution Poor performance or no links Incorrect speed settings for 10-Mbps and 100-Mbps connections. Bad adapter in attached device. Replace with a known good cable. For 10BaseT connections: The distance between the port and the attached device exceeds 100 meters. 4-2 • A crossover cable was used when straight-through was required. • If attached to a repeater. • Manually set the speed setting for the ports on both ends of the connection to match. late-collision. “Connector and Cable Specifications. Cabling distance exceeded.

• Enable the port through in-band or out-of-band management. RPS LED solid amber RPS not operational. Faulty cable. See the “Recovery Procedures Using the Diagnostic Console” section on page 4-6 of this chapter for firmware upgrade instructions. straight-through). Cable connection loose. Ensure both devices have power.Diagnosing Problems Table 4-1 Common Problems and Their Solutions (Continued) Symptom Possible Cause Resolution No management console access (FastHub 400M models only) Configuration problems. Port LED off Devices not powered up. See Appendix B. Troubleshooting 4-3 . Change the baud rate of the hub console port to match the management station. Replace the cable with a known good one. Port LED solid amber Port not forwarding. SYSTEM LED off Power cord not connected. port LEDs off Corrupt firmware. Plug in both ends of the power cord. The port might be disabled by management or the device at other end is malfunctioning. Verify the connection at both ends of cable. SYSTEM LED amber. Verify the cable type (crossover vs.” for pinout information. Verify port connection and check integrity of the connected devices. Incorrect wiring. jabber. Use the Diagnostic Console to reset the hub. “Connector and Cable Specifications. Verify that the RPS is connected properly to the hub and is connected to an AC power outlet. Incorrect baud rate. Port LED alternating green and amber Link fault. or isolated carrier integrity error. Autopartition. Wrong cable type. • Investigate the device that is connected to the disabled port on the hub.

but the amber port LED(s) indicate which test(s) failed. This section provides information about fatal and nonfatal POST failures and recovery procedures. the SYSTEM LED is amber. If a nonfatal failure occurs. If your hub has a fatal failure. the SYSTEM LED is amber. and the hub is still operational and can forward packets.Understanding POST Results Understanding POST Results As described in the “Powering Up the Hub and Running POST” section on page 2-6. Contact your Cisco representative or reseller for support. the hub runs ten tests each time it is powered up. For information on displaying POST results. see the “Starting Up the Hub and Displaying the POST Results” section on page 4-9. The hub diagnostic console displays a message that describes the POST results. 4-4 FastHub 400 10/100 Series Installation and Configuration Guide . The hub is not operational. Table 4-2 describes the individual tests and their associated LEDs. and one or more of the port LEDs are amber. but it might not operate optimally.

Checks the integrity of the checksum for the boot code. is correct or not. 3x Fatal—System image test. 10x Nonfatal—Timer test. Checks the functionality of the SDRAM. 6x Nonfatal—Network interrupt controller (NIC) channel test. Hub is not operational.Understanding POST Results Table 4-2 POST Test Descriptions Port LEDs Test 12x Fatal—Boot code test. Checks the internal loop-back function of the MDT channel. Checks the internal loop-back function for the UART channel. Hub is not operational. Checks if the configuration data stored in Flash memory is corrupted. Contact your Cisco representative or reseller for support. Troubleshooting 4-5 . Checks if the integrity of the system code. Contact your Cisco representative or reseller for support. Checks the functionality of the system timer. 9x Nonfatal—UART test. Contact your Cisco representative or reseller for support. 4x Nonfatal—Parameter block data (config data) test. 8x Nonfatal—Serial management bus (SMB) channel test. 7x Nonfatal—Management data tunnel (MDT) channel test. 11x Fatal—SDRAM test. Checks the internal loop-back function of the SPI channel. 5x Nonfatal—Serial peripheral interface (SPI) channel test. Hub is not operational. Checks the internal loop-back function of the SMB channel. which relies on the Flash ROM. Checks the internal loop-back function of the NIC channel.

The diagnostic console is a menu-drive interface that you can use to perform the following tasks: • • • • • 4-6 Start up the hub and display the POST results Recover from corrupted firmware Recover from a lost or forgotten password Reset the hub to factory defaults Reset the hub console port settings to the factory defaults FastHub 400 10/100 Series Installation and Configuration Guide .Recovery Procedures Using the Diagnostic Console Recovery Procedures Using the Diagnostic Console Note Access to the hub diagnostic console requires physical access to the hub.

Inc. Step 5 Press and hold in the Mode button.Accessing the Diagnostic Console Accessing the Diagnostic Console To display the diagnostic console. Note The recovery procedure runs at 9600 baud. Troubleshooting 4-7 . To display the diagnostic console properly. A display such as the one in Figure 4-1 appears. Step 4 Unplug the power cord from the back of the hub. Step 6 Release the Mode button 1 or 2 seconds after the LED above port 1x goes off. follow these steps: Step 1 Connect a management station with terminal emulation software (such as ProComm or Reflection) supporting the XMODEM Protocol to the hub console port. reconnect the power cord to the hub. make sure you set the line speed on the emulation software to 9600 baud. Ethernet address: 00-E0-1E-7E-B4-40 ------------------------------------------------Press Enter to continue. Step 2 Start up your emulation program. 1999 All rights reserved. and at the same time. Figure 4-1 Diagnostic Console Display Cisco FastHub 400 10/100 Series Diagnostic Console Copyright (c) Cisco Systems. Step 3 Set the line speed on the emulation software to 9600 baud.

00 [C] Continue with standard system start up [U] Upgrade operation firmware (XMODEM) [S] System debug interface Enter Selection: The firmware version used by the hub is displayed in the Boot firmware version field. 4-8 FastHub 400 10/100 Series Installation and Configuration Guide .Recovery Procedures Using the Diagnostic Console Using the Diagnostic Console .Systems Engineering Menu (Figure 4-2) provides options from which you can troubleshoot firmware problems and then bring up the firmware as usual.Systems Engineering Menu Diagnostic Console . To display this menu.00. press Enter from the Diagnostic Console Display.Systems Engineering Menu The Diagnostic Console . Figure 4-2 Diagnostic Console .Systems Engineering Boot firmware version: 1.

Loopback Test PASS Parameter Block Data Checksum Test PASS System Image Checksum Test PASS -----------------Power-On Self Test Completed----------------Starting application. enter C (the Continue with standard system start up option) from the Diagnostic Console . use the [C] option to exit the diagnostic console session and to bring up the firmware. Loopback Test PASS SPI Channel Int. After you have resolved firmware problems by using the [U] and [S] options on the Diagnostic Console . Figure 4-4 Example of a POST Failure Message -------------Performing Power-On Self Test (POST)------------POST Image Checksum Test PASS System DRAM Test PASS System Timer Test PASS UART Channel Int. Loopback Test FAIL SMB Channel Int.Systems Engineering Menu. Figure 4-3 is the POST message displayed when no POST failures are found during start up.. Loopback Test PASS SPI Channel Int.. Figure 4-3 Example of the POST Message with No POST Failures -------------Performing Power-On Self Test (POST)------------POST Image Checksum Test PASS System DRAM Test PASS System Timer Test PASS UART Channel Int. Loopback Test PASS NIC Channel Int.Using the Diagnostic Console . Figure 4-4 is an example message showing that the fourth POST test (nonfatal—UART test) failed.Systems Engineering Menu Starting Up the Hub and Displaying the POST Results To display the POST results. Loopback Test PASS SMB Channel Int.Systems Engineering Menu. Loopback Test PASS NIC Channel Int. Loopback Test PASS MDT Channel Int. Loopback Test PASS MDT Channel Int. Loopback Test PASS Parameter Block Data Checksum Test PASS System Image Checksum Test PASS -----------------Power-On Self Test Completed----------------- Troubleshooting 4-9 .

com. In both cases. Step 3 Start up your emulation program. follow these step: Step 1 Copy the hub firmware from Cisco Connection Online (CCO) to a temporary area on your management station. and it is possible to download the wrong file.cisco. New firmware releases can be downloaded from CCO.Systems Engineering Menu” section on page 4-8.cisco. FastHub 400 10/100 Series Installation and Configuration Guide . Step 4 Set the line speed on the emulation software to 9600 baud. To download the hub firmware via the XMODEM protocol.cisco. The procedure for downloading the firmware via XMODEM is largely dependent on the terminal emulation software you are using. and there is no connectivity. From the diagnostic console.Recovery Procedures Using the Diagnostic Console Recovering from Corrupted Firmware Hub firmware can be corrupted during an upgrade.com. the hub does not pass POST. Step 5 Display the diagnostic console as described in the “Accessing the Diagnostic Console” section on page 4-7 and “Using the Diagnostic Console . and www-europe. www-china. the Cisco Systems customer web site available at the following URLs: www.com. you can download the upgrade file from a management station to the hub via the XMODEM protocol. 4-10 Step 2 Connect the management station with terminal emulation software (such as ProComm or Reflection) supporting the XMODEM Protocol to the hub console port.

Systems Engineering Menu Step 6 Enter U (the Upgrade operation firmware (XMODEM) option) from the Diagnostic Console .Using the Diagnostic Console . or 5. Step 9 From your terminal emulation session: • • • Select the XMODEM protocol option.Systems Engineering Menu.Systems Engineering Menu. If you select the [0] option. 9600 bps 19200 bps 38400 bps 57600 bps 115200 bps Enter Selection: Step 7 Select a baud rate for the hub console port by entering 0. Note If you change the baud rate of the hub console port. 4. 1. Step 8 Change the baud rate of the management station to match the baud rate of the hub console port. 2. Specify the name of the hub upgrade file Use the appropriate command to transfer the upgrade file to the hub. the current baud rate of the hub console port is used. Troubleshooting 4-11 . 3. The following prompt is displayed: Change the hub console baud rate: [0] [1] [2] [3] [4] [5] No change to the baud rate. The following prompt is displayed: Are you ready to perform XMODEM download? [Y]es or [N]o: Entering N redisplays the Diagnostic Console . make sure the baud rate of the management station matches it.

the hub does not respond to commands for approximately 1 minute. Step 11 Enter C to start up the hub and run POST. the following message is displayed: XMODEM download completed. When the download is completed.. change the baud rate back to its original setting. Please wait. Note When downloading the firmware permanently to Flash memory. The hub then resets and begins using the new firmware. When POST is completed.Systems Engineering Menu is displayed. the firmware could get corrupted. Caution If you interrupt the transfer by turning the hub off and on. This is normal and correct. 4-12 FastHub 400 10/100 Series Installation and Configuration Guide .Recovery Procedures Using the Diagnostic Console Step 10 Enter Y. And then the Diagnostic Console . Step 12 If you had changed the baud rate of the management station on Step 8. Updating system image. the following prompt is displayed: System is setting the baud rate back to the original setting. The baud rate of the hub console port is changed back to its original setting. Do not turn off the hub.. The system starts the XMODEM download and the following prompt is displayed: Checking system.

Step 2 Start up your emulation program. Entering N when a password exists allows that password to remain valid. the following prompt is displayed if no IP information has been assigned to the hub: Continue with configuration dialog? [Y]es or [N]o: Troubleshooting 4-13 . You can then assign a password from the Home Page or from the CLI.Systems Engineering Menu. (b) Enter C (the Continue with standard system start up option) from the Diagnostic Console . To recover from a lost or forgotten password. Step 3 Set the line speed on the emulation software to 9600 baud.Using the Diagnostic Console . After you have selected Y or N. After POST completes.Systems Engineering Menu” section on page 4-8. the following prompt is displayed: If a password has already been assigned. or (a) Display the diagnostic console as described in the “Accessing the Diagnostic Console” section on page 4-7 and “Using the Diagnostic Console .Systems Engineering Menu Recovering from a Lost or Forgotten Password If you have forgotten or lost the hub password. the following prompt is displayed: Clear passwords? [Y]es or [N]o: • • Entering Y deletes the existing password from nonvolatile RAM (NVRAM). Step 4 You can either: (a) Unplug the power cord from the back of the hub and then power up the hub. follow these steps: Step 1 Connect a management station with terminal emulation software (such as ProComm or Reflection) supporting the XMODEM Protocol to the hub console port. you can use the diagnostic console to overwrite the password with a new password.

1. enter S (the System debug interface option) from the Diagnostic Console .System Debug Interface Memory I/O Return system to factory defaults Reset main console RS232 interface to 9600.Systems Engineering Menu. 4-14 FastHub 400 10/100 Series Installation and Configuration Guide .N Exit to Previous Menu Enter Selection: Note The [M] option on the Diagnostic Console .Recovery Procedures Using the Diagnostic Console Using the Diagnostic Console .System Debug Interface Menu is for Cisco personnel only. Figure 4-5 Diagnostic Console .System Debug Interface Menu Diagnostic Console [M] [F] [R] [X] .System Debug Interface Menu (Figure 4-5) provides system options for resetting the console port or the entire hub to the factory defaults.Systems Engineering Menu.System Debug Interface Menu The Diagnostic Console .8. The [X] option displays the Diagnostic Console . To display this menu. You can also use this menu to display the factory-installed management interface password.

The following prompt is displayed: Return system to factory defaults? [Y]es or [N]o: Entering N redisplays the Diagnostic Console .System Debug Interface Menu. This could happen. To reset to the hub to the factory defaults.Using the Diagnostic Console . Resetting the Hub Console Port to Factory Defaults To reset to the hub console port to the factory defaults.N option) from the Diagnostic Console .System Debug Interface Menu Resetting the Hub to the Factory Defaults There can be times when you need the diagnostic console even though the firmware is valid. Step 2 Enter Y. if the hub configuration prevents the firmware from executing properly and you cannot display the management interfaces.8. for example. follow these steps: Step 1 Enter F (the Return system to factory defaults option) from the Diagnostic Console . The following prompt is displayed: Return system to factory defaults? [Y]es or [N]o: Entering N redisplays the Diagnostic Console . Step 2 Enter Y. Troubleshooting 4-15 .System Debug Interface Menu.System Debug Interface Menu.1.System Debug Interface Menu. follow these steps: Step 1 Enter R (the Reset main console RS232 interface to 9600.

Recovery Procedures Using the Diagnostic Console 4-16 FastHub 400 10/100 Series Installation and Configuration Guide .