TroubleshootinTable 4-1 lists symptoms, possible causes, and corrective actions associated with

Poor performance. No connectivity. No access to management interfaces. (FastHub 400M models only)C H A P T E R 4

TroubleshootingThere 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 Problemsg 4-1

Diagnosing ProblemsTable 4-1 Common Problems and Their Solutions

Symptom Possible Cause ResolutionPoor performance or no links

Incorrect speed settings for 10-Mbps and 100-Mbps connections.

Let both ports autonegotiate port speed.

Manually set the speed setting for the ports on both ends of the connection to match.

Cabling distance exceeded.Port statistics show excessive FCS, late-collision, or alignment errors. For 100BaseTX connections: The distance between the port and the attached

device exceeds 100 meters. If attached to a repeater, the total distance between

the two end stations exceeds the 100BaseT cabling guidelines.

For 10BaseT connections: The distance between the port and the attached device exceeds 100 meters.

Reduce the cable length to within the recommended distances. See your 100BaseT repeater documentation for cabling guidelines.

Reduce the cable length to within the recommended distances.

Bad adapter in attached device.Excessive errors found in port statistics. Run the adapter card diagnostic utility.

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.

Reset the installed switched uplink module to clear the address table.

No connectivity Incorrect or bad cable. A crossover cable was used when straight-through

was required, or vice-versa.

Bad cable.

See Appendix B, Connector and Cable Specifications, for the correct pinouts and the proper use of crossover vs. straight-through cables.Replace with a known good cable.FastHub 400 10/100 Series Installation and Configuration Guide4-2

Diagnosing ProblemsNo management console access (FastHub 400M models only)

Configuration problems. Use the Diagnostic Console to reset the hub.

Incorrect baud rate. Change the baud rate of the hub console port to match the management station.

RPS LED solid amber

RPS not operational. Verify that the RPS is connected properly to the hub and is connected to an AC power outlet.

SYSTEM LED off Power cord not connected. Plug in both ends of the power cord.

SYSTEM LED amber;port LEDs off

Corrupt firmware. See the Recovery Procedures Using the Diagnostic Console section on page 4-6 of this chapter for firmware upgrade instructions.

Port LED off Devices not powered up. Ensure both devices have power.

Cable connection loose. Verify the connection at both ends of cable.

Wrong cable type. Verify the cable type (crossover vs. straight-through).

Incorrect wiring. See Appendix B, Connector and Cable Specifications, for pinout information.

Faulty cable. Replace the cable with a known good one.

Port LED alternating green and amber

Link fault.Autopartition, jabber, or isolated carrier integrity error.

Verify port connection and check integrity of the connected devices.

Port LED solid amber

Port not forwarding.The port might be disabled by management or the device at other end is malfunctioning.

Investigate the device that is connected to the disabled port on the hub.

Enable the port through in-band or out-of-band management.

Table 4-1 Common Problems and Their Solutions (Continued)Symptom Possible Cause Resolution Troubleshooting 4-3

Understanding POST ResultsUnderstanding POST ResultsAs described in the Powering Up the Hub and Running POST section on page 2-6, the hub runs ten tests each time it is powered up. This section provides information about fatal and nonfatal POST failures and recovery procedures.

If your hub has a fatal failure, the SYSTEM LED is amber, and one or more of the port LEDs are amber. The hub is not operational, but the amber port LED(s) indicate which test(s) failed. Contact your Cisco representative or reseller for support.If a nonfatal failure occurs, the SYSTEM LED is amber, and the hub is still operational and can forward packets, but it might not operate optimally. The hub diagnostic console displays a message that describes the POST results. For information on displaying POST results, see the Starting Up the Hub and Displaying the POST Results section on page 4-9.

Table 4-2 describes the individual tests and their associated LEDs. FastHub 400 10/100 Series Installation and Configuration Guide4-4

Understanding POST ResultsTable 4-2 POST Test Descriptions

Port LEDs Test12x FatalBoot code test.

Checks the integrity of the checksum for the boot code. Hub is not operational.Contact your Cisco representative or reseller for support.

11x FatalSDRAM test. Checks the functionality of the SDRAM. Hub is not operational.Contact your Cisco representative or reseller for support.

10x NonfatalTimer test. Checks the functionality of the system timer.

9x NonfatalUART test.Checks the internal loop-back function for the UART channel.

8x NonfatalSerial management bus (SMB) channel test.Checks the internal loop-back function of the SMB channel.

7x NonfatalManagement data tunnel (MDT) channel test.Checks the internal loop-back function of the MDT channel.

6x NonfatalNetwork interrupt controller (NIC) channel test.Checks the internal loop-back function of the NIC channel.

5x NonfatalSerial peripheral interface (SPI) channel test.Checks the internal loop-back function of the SPI channel.

4x NonfatalParameter block data (config data) test.Checks if the configuration data stored in Flash memory is corrupted.

3x FatalSystem image test. Checks if the integrity of the system code, which relies on the Flash ROM, is correct or not. Hub is not operational. Contact your Cisco representative or reseller for support. Troubleshooting 4-5

Recovery Procedures Using the Diagnostic ConsoleRecovery Procedures Using the Diagnostic ConsoleNote Access to the hub diagnostic console requires physical access to the hub.

The diagnostic console is a menu-drive interface that you can use to perform the following tasks:

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 defaultsFastHub 400 10/100 Series Installation and Configuration Guide4-6

Accessing the Diagnostic ConsoleAccessing the Diagnostic ConsoleTo display the diagnostic console, 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.

Step 2 Start up your emulation program.Step 3 Set the line speed on the emulation software to 9600 baud.

Note The recovery procedure runs at 9600 baud. To display the diagnostic console properly, make sure you set the line speed on the emulation software to 9600 baud.

Step 4 Unplug the power cord from the back of the hub.Step 5 Press and hold in the Mode button, and at the same time, reconnect the power

cord to the hub. Step 6 Release the Mode button 1 or 2 seconds after the LED above port 1x goes off. A

display such as the one in Figure 4-1 appears.

Figure 4-1 Diagnostic Console Display

Cisco FastHub 400 10/100 Series Diagnostic ConsoleCopyright (c) Cisco Systems, Inc. 1999All rights reserved.

Ethernet address: 00-E0-1E-7E-B4-40

-------------------------------------------------

Press Enter to continue. Troubleshooting 4-7

Recovery Procedures Using the Diagnostic ConsoleUsing the Diagnostic Console - Systems Engineering MenuThe 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.

To display this menu, press Enter from the Diagnostic Console Display.

Figure 4-2 Diagnostic Console - Systems Engineering Menu

Diagnostic Console - Systems Engineering

Boot firmware version: 1.00.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.FastHub 400 10/100 Series Installation and Configuration Guide4-8

Using the Diagnostic Console - Systems Engineering MenuStarting Up the Hub and Displaying the POST ResultsTo display the POST results, enter C (the Continue with standard system start up option) from the Diagnostic Console - Systems Engineering Menu. Figure 4-3 is the POST message displayed when no POST failures are found during start up. Figure 4-4 is an example message showing that the fourth POST test (nonfatalUART test) failed.After you have resolved firmware problems by using the [U] and [S] options on the Diagnostic Console - Systems Engineering Menu, use the [C] option to exit the diagnostic console session and to bring up the firmware.

Figure 4-3 Example of the POST Message with No POST Failures

-------------Performing Power-On Self Test (POST)-------------POST Image Checksum Test PASSSystem DRAM Test PASSSystem Timer Test PASSUART Channel Int. Loopback Test PASSSMB Channel Int. Loopback Test PASSMDT Channel Int. Loopback Test PASSNIC Channel Int. Loopback Test PASSSPI Channel Int. Loopback Test PASSParameter Block Data Checksum Test PASSSystem Image Checksum Test PASS-----------------Power-On Self Test Completed-----------------

Starting application...

Figure 4-4 Example of a POST Failure Message

-------------Performing Power-On Self Test (POST)-------------POST Image Checksum Test PASSSystem DRAM Test PASSSystem Timer Test PASSUART Channel Int. Loopback Test FAILSMB Channel Int. Loopback Test PASSMDT Channel Int. Loopback Test PASSNIC Channel Int. Loopback Test PASSSPI Channel Int. Loopback Test PASSParameter Block Data Checksum Test PASSSystem Image Checksum Test PASS-----------------Power-On Self Test Completed----------------- Troubleshooting 4-9

Recovery Procedures Using the Diagnostic ConsoleRecovering from Corrupted FirmwareHub firmware can be corrupted during an upgrade, and it is possible to download the wrong file. In both cases, the hub does not pass POST, and there is no connectivity.

From the diagnostic console, you can download the upgrade file from a management station to the hub via the XMODEM protocol. The procedure for downloading the firmware via XMODEM is largely dependent on the terminal emulation software you are using.

To download the hub firmware via the XMODEM protocol, follow these step:

Step 1 Copy the hub firmware from Cisco Connection Online (CCO) to a temporary area on your management station.

New firmware releases can be downloaded from CCO, the Cisco Systems customer web site available at the following URLs: www.cisco.com, www-china.cisco.com, and www-europe.cisco.com.

Step 2 Connect the management station with terminal emulation software (such as ProComm or Reflection) supporting the XMODEM Protocol to the hub console port.

Step 3 Start up your emulation program.

Step 4 Set the line speed on the emulation software to 9600 baud.

Step 5 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 section on page 4-8.FastHub 400 10/100 Series Installation and Configuration Guide4-10

Using the Diagnostic Console - Systems Engineering MenuStep 6 Enter U (the Upgrade operation firmware (XMODEM) option) from the Diagnostic Console - Systems Engineering Menu.

The following prompt is displayed: Change the hub console baud rate:

[0] No change to the baud rate.[1] 9600 bps[2] 19200 bps[3] 38400 bps[4] 57600 bps[5] 115200 bps

Enter Selection:

Step 7 Select a baud rate for the hub console port by entering 0, 1, 2, 3, 4, or 5.

If you select the [0] option, the current baud rate of the hub console port is used.

Note If you change the baud rate of the hub console port, make sure the baud rate of the management station matches it.

The following prompt is displayed:Are you ready to perform XMODEM download? [Y]es or [N]o:

Entering N redisplays the Diagnostic Console - Systems Engineering Menu.

Step 8 Change the baud rate of the management station to match the baud rate of the hub console port.

Step 9 From your terminal emulation session:

Select the XMODEM protocol option. Specify the name of the hub upgrade file Use the appropriate command to transfer the upgrade file to the hub. Troubleshooting 4-11

Recovery Procedures Using the Diagnostic ConsoleStep 10 Enter Y.

The system starts the XMODEM download and the following prompt is displayed:Checking system...Updating system image. Please wait.

When the download is completed, the following message is displayed: XMODEM download completed.

And then the Diagnostic Console - Systems Engineering Menu is displayed.

Step 11 Enter C to start up the hub and run POST.

When POST is completed, 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.

Step 12 If you had changed the baud rate of the management station on Step 8, change the baud rate back to its original setting.

Note When downloading the firmware permanently to Flash memory, the hub does not respond to commands for approximately 1 minute. This is normal and correct. Do not turn off the hub. The hub then resets and begins using the new firmware.

Caution If you interrupt the transfer by turning the hub off and on, the firmware could get corrupted. FastHub 400 10/100 Series Installation and Configuration Guide4-12

Using the Diagnostic Console - Systems Engineering MenuRecovering from a Lost or Forgotten PasswordIf you have forgotten or lost the hub password, you can use the diagnostic console to overwrite the password with a new password.

To recover from a lost or forgotten password, 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.

Step 2 Start up your emulation program.

Step 3 Set the line speed on the emulation software to 9600 baud.Step 4 You can either:

(a) Unplug the power cord from the back of the hub and then power up the hub.

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 section on page 4-8.

(b) Enter C (the Continue with standard system start up option) from the Diagnostic Console - Systems Engineering Menu.

After POST completes, the following prompt is displayed:

If a password has already been assigned, the following prompt is displayed:Clear passwords? [Y]es or [N]o:

Entering Y deletes the existing password from nonvolatile RAM (NVRAM). You can then assign a password from the Home Page or from the CLI.

Entering N when a password exists allows that password to remain valid.After you have selected Y or N, 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

Recovery Procedures Using the Diagnostic ConsoleUsing the Diagnostic Console - System Debug Interface MenuThe Diagnostic Console - System Debug Interface Menu (Figure 4-5) provides system options for resetting the console port or the entire hub to the factory defaults. You can also use this menu to display the factory-installed management interface password.

To display this menu, enter S (the System debug interface option) from the Diagnostic Console - Systems Engineering Menu.

Figure 4-5 Diagnostic Console - System Debug Interface Menu

Diagnostic Console - System Debug Interface

[M] Memory I/O[F] Return system to factory defaults[R] Reset main console RS232 interface to 9600,8,1,N[X] Exit to Previous Menu

Enter Selection:

Note The [M] option on the Diagnostic Console - System Debug Interface Menu is for Cisco personnel only. The [X] option displays the Diagnostic Console - Systems Engineering Menu.FastHub 400 10/100 Series Installation and Configuration Guide4-14

Using the Diagnostic Console - System Debug Interface MenuResetting the Hub to the Factory DefaultsThere can be times when you need the diagnostic console even though the firmware is valid. This could happen, for example, if the hub configuration prevents the firmware from executing properly and you cannot display the management interfaces.

To reset to the hub to the factory defaults, follow these steps:

Step 1 Enter F (the Return system to factory defaults option) from the Diagnostic Console - System Debug Interface Menu.

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.

Step 2 Enter Y.

Resetting the Hub Console Port to Factory DefaultsTo reset to the hub console port to the factory defaults, follow these steps:

Step 1 Enter R (the Reset main console RS232 interface to 9600,8,1,N option) from the Diagnostic Console - System Debug Interface Menu.

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.

Step 2 Enter Y. Troubleshooting 4-15

Recovery Procedures Using the Diagnostic ConsoleFastHub 400 10/100 Series Installation and Configuration Guide4-16

Starting Up the Hub and Displaying the POST ResultsRecovering from Corrupted FirmwareRecovering from a Lost or Forgotten PasswordResetting the Hub to the Factory DefaultsResetting the Hub Console Port to Factory Defaults

/ColorImageDict > /JPEG2000ColorACSImageDict > /JPEG2000ColorImageDict > /AntiAliasGrayImages false /CropGrayImages true /GrayImageMinResolution 300 /GrayImageMinResolutionPolicy /OK /DownsampleGrayImages true /GrayImageDownsampleType /Bicubic /GrayImageResolution 300 /GrayImageDepth -1 /GrayImageMinDownsampleDepth 2 /GrayImageDownsampleThreshold 1.50000 /EncodeGrayImages true /GrayImageFilter /DCTEncode /AutoFilterGrayImages true /GrayImageAutoFilterStrategy /JPEG /GrayACSImageDict > /GrayImageDict > /JPEG2000GrayACSImageDict > /JPEG2000GrayImageDict > /AntiAliasMonoImages false /CropMonoImages true /MonoImageMinResolution 1200 /MonoImageMinResolutionPolicy /OK /DownsampleMonoImages true /MonoImageDownsampleType /Bicubic /MonoImageResolution 1200 /MonoImageDepth -1 /MonoImageDownsampleThreshold 1.50000 /EncodeMonoImages true /MonoImageFilter /CCITTFaxEncode /MonoImageDict > /AllowPSXObjects false /CheckCompliance [ /None ] /PDFX1aCheck false /PDFX3Check false /PDFXCompliantPDFOnly false /PDFXNoTrimBoxError true /PDFXTrimBoxToMediaBoxOffset [ 0.00000 0.00000 0.00000 0.00000 ] /PDFXSetBleedBoxToMediaBox true /PDFXBleedBoxToTrimBoxOffset [ 0.00000 0.00000 0.00000 0.00000 ] /PDFXOutputIntentProfile () /PDFXOutputConditionIdentifier () /PDFXOutputCondition () /PDFXRegistryName () /PDFXTrapped /False

/Description > /Namespace [ (Adobe) (Common) (1.0) ] /OtherNamespaces [ > /FormElements false /GenerateStructure true /IncludeBookmarks false /IncludeHyperlinks false /IncludeInteractive false /IncludeLayers false /IncludeProfiles true /MultimediaHandling /UseObjectSettings /Namespace [ (Adobe) (CreativeSuite) (2.0) ] /PDFXOutputIntentProfileSelector /NA /PreserveEditing true /UntaggedCMYKHandling /LeaveUntagged /UntaggedRGBHandling /LeaveUntagged /UseDocumentBleed false >> ]>> setdistillerparams> setpagedevice