Cisco 1538M 10/100 Installation and Configuration Guide
Troubleshooting
Downloads: This chapterpdf (PDF - 105.0KB) | Feedback

Troubleshooting

Table Of Contents

Troubleshooting

Initial Startup Problems

Problems After First Powerup

Understanding POST Results

Problems After Hub Is Running

Recovery Procedures Using the Diagnostic Console

Accessing the Diagnostic Console

Using the

Starting Up the Hub and Displaying the POST Results

Recovering from Corrupted Firmware

Recovering from a Lost or Forgotten Password

Using the

Resetting the Hub to the Factory Defaults

Resetting the Hub Console Port to Factory Defaults


Troubleshooting


This chapter describes problems that could occur with the Micro Hub, possible reasons for the problems, and possible steps to take to solve the problems. The problems are grouped into states from startup to a state where the hub is up and running.

Initial Startup Problems

lists problems that could occur after you connect the power cord for the first time.

Table 4-1 Initial Startup Problems

Symptom
Possible Problem
Possible Solutions

Power cord is connected to hub, but all LEDs, including the PWR LED, are off.

No power to hub.

Check both ends of the power cord to make certain that they are securely connected to the power receptacle on the hub and power outlet.

Make sure that the power outlet has power.

If both ends of the power cord are properly connected and the problem continues, the hub might have a faulty power supply. Contact your Cisco representative or reseller for support.


Problems After First Powerup

lists problems that could occur after the hub powers up for the first time.

Table 4-2 Problems After Hub Powers Up 

Symptom
Possible Problems
Possible Solutions

No link to a network device. (The front and back panel LEDs for the connecting port are off.)

A cable-related problem:

Cable is not compliant with specifications.

Damaged cable.

Improperly connected cable.

Perform the following tasks in the following order:

Make sure the connectors at both ends of the cable are securely seated.

Make sure you are using the right type of cable (straight-through or crossover):

If you are connecting a compatible router, server, PC, or workstation, use a straight-through Ethernet cable.

If you are connecting a hub or switch without an MDI/MDI-X button and you are not using the Micro Hub port 5, use a crossover Ethernet cable.

Make sure the cable is not physically damaged. If it is damaged, replace it with a similar cable.

Check the cable specifications in the "Ethernet Cable Specifications" on page B-3 to make sure cable you are using complies. If your cable does not comply with the specifications, that is, it is the wrong speed, wrong category, or exceeds maximum length, replace it with a cable that complies. (You can often verify the cable category by checking the marking on the outer sleeve or jacket of the cable.)

To make sure you have cabled the devices correctly, see the sections "Connecting a PC, Workstation, Router, or Server," "Connecting the Stacking Cables," and "Connecting Compatible Hubs and Switches to the Hub" in "."

(continued)
No link to a network device. (The front and back panel LEDs for the connecting port are off.)

Improper MDI/MDI-X connection with connecting device.

If the Micro Hub is connected to another hub or switch:

If you are using a straight-through cable from port 5, verify that the MDI/MDI-X switch is in the IN position.

If you are using a crossover cable from port 5, verify that the MDI/MDI-X switch is in the OUT position.

If the hub or switch is connected through a Micro Hub port other than port 5, use a crossover cable (unless the hub or switch also has a selectable MDI/MDI-X port).

If the hub is connected to a PC, terminal, router, or server:

Use a crossover cable if the port 5 MDI/MDI-X switch is in the IN position.

Use a straight-through cable if the port 5 MDI/MDI-X switch is in the OUT position.

 

Improperly functioning network interface card (NIC) on a PC or workstation.

Run the diagnostic supplied by the vendor on the NIC to determine if it is functioning properly. If it is not, replace it.

Incorrect or incomplete management information from managed hub.

Incorrect connection of stacking cables to stacking connectors.

Check that the top hub in the stack has a stacking cable connected only to its DOWN connector and that the other end of the cable is connected to the UP connector of the adjacent hub. See "Installing Micro Hubs in a Stack" on page 2-8 for connection instructions for the rest of the stack.


If the problem continues after these checks, contact your Cisco representative or reseller for support.

Understanding POST Results

As described in the "Using POST to Pretest the Hub Operation" section, the hub runs nine 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 POWER LED is amber, and a port LED is blinking green. The hub is not operational, and the console is unavailable, but the blinking port LED indicates which test failed. Contact your Cisco representative or reseller for support.

If a nonfatal failure occurs, the POWER LED is amber, and the hub is still operational and can forward packets, but it might not operate optimally. A POST failure message on the hub diagnostic console, such as the one in , is displayed. In this example, the message indicates the fourth POST test (nonfatal—UART test) failed. describes the individual tests and their associated LEDs.

For information on displaying POST results from the hub diagnostic console, see the "Starting Up the Hub and Displaying the POST Results" section.

Figure 4-1 Example of a POST Failure Message


Cisco Systems Diagnostic Console
Copyright(c) Cisco Systems, Inc. 1999
All rights reserved

Model : 1538 Micro Hub 10/100
Boot Firmware Version: 1.00.00
Ethernet Address: 00-E0-1E-7E-B4-40

------ Performing the 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. Loopback Test ............ PASS
MDT Channel Int. Loopback Test ............ PASS
NIC Channel Int. Loopback Test ............ PASS
SPI Channel Int. Loopback Test ............ PASS
System Image Checksum Test ................ PASS
------------ Power-On Self Test Completed ------------

Table 4-3 POST Test Descriptions

Port LEDs
Test

4

Fatal—Boot code test.

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

3

Fatal—SDRAM test.

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

2

Nonfatal—Timer test.

Checks the functionality of the system timer.

1

Nonfatal—UART test.

Checks the internal loop-back function for the UART channel.

8

Nonfatal—Serial management bus (SMB) channel test.

Checks the internal loop-back function of the SMB channel.

7

Nonfatal—Management data tunnel (MDT) channel test.

Checks the internal loop-back function of the MDT channel.

6

Nonfatal—Network interrupt controller (NIC) channel test.

Checks the internal loop-back function of the NIC channel.

5

Nonfatal—Serial peripheral interface (SPI) channel test.

Checks the internal loop-back function of the SPI channel.

4 and 5

Fatal—System 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.


Problems After Hub Is Running

Table 4-4 Problems After Hub Is Running 

Symptom
Possible Problems
Possible Solutions

Connection to a network device is lost. (The front- and back-panel LEDs for the connecting port are off.)

One of the following cable-related problems:

Disconnected cable.

Damaged cable.

Improperly functioning NIC on PC or workstation.

Make sure connectors at both ends of cable are securely seated.

Make sure the cable is not physically damaged. If it is damaged, replace it with a similar cable.

Run the diagnostic supplied by the vendor on the NIC to determine if it is functioning properly. If it is not, replace it.

If the problem continues after these checks, contact your Cisco representative or reseller.

Connection to a network device is lost. (The front-panel LED for the connecting port is solid amber.)

The hub might have automatically partitioned or separated the network device. For example, a hub could partition a network device if there are too many data collisions from the device.
(For more information on data collisions, also see the next entry in this table.)

Run the diagnostic supplied by the vendor on the network device to determine if it is functioning properly. If it is not, replace it. If the network device is not the problem, contact your Cisco representative or reseller.

Other than addressing the source of the problem, no action is required. Once the port receives a valid Ethernet packet, the network device resumes communication with the rest of the network.

One of the COL/ACT LEDs is blinking amber.

The data packets from two network devices are colliding on the network. The LED blinks longer as more collisions occur.

If one or a few collisions occur, no action is required.

If several collisions occur (the LED blinks yellow for a long time), try the following tasks in the following order:

Check to see if any ports on connected network devices are set to full-duplex mode. If this is the case, set the network device port to half-duplex mode.

Consider further segmenting or subnetting the existing segment. Further segmenting requires a switch and separating the network devices that are transmitting a high rate of data (for example, CAD stations) on different segments.


Recovery Procedures Using the Diagnostic Console


Note   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 defaults

Accessing the Diagnostic Console

To 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 Power up the hub.

Step 6 Within 5 seconds after power up, press Ctrl-x three times:

^x ^x ^x 

A display such as the one in Figure 4-2 appears.

Figure 4-2 Diagnostic Console Display


Cisco Systems Diagnostic Console
Copyright (c) Cisco Systems, Inc. 1999
All rights reserved.

Model: 1538 Micro Hub 10/100

Boot Firmware Version: 1.00.00
Ethernet Address: 00-E0-1E-7E-B4-40

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

Press enter to continue.

The firmware version used by the hub is displayed in the Boot firmware version field.

Using the

The (Figure 4-3) provides options from which you can troubleshoot firmware problems and then bring up the firmware as usual.

To display this menu, press any key from the (Figure 4-2).

Figure 4-3 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)
[B] Change the baud rate of the main console RS232 interface
[S] System debug interface

Enter Selection:

The firmware version used by the hub is displayed in the Boot firmware 
version field.

Starting Up the Hub and Displaying the POST Results

To display the POST results, as shown in Figure 4-1, follow these steps;


Step 1 Enter C (the Continue with standard system start up option) from the .

The following prompt is displayed:

Please reset your terminal application's baud rate to (9600, 8, 1, 
N) now before you leave the recovery procedure.

Press any key to continue.

Step 2 Reset the line speed on the emulation software to 9600 baud, 8 data bits, 1 stop bit, and no parity.

Step 3 Press any key to begin POST.

Recovering from Corrupted Firmware

Hub 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 modem 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.


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 5 Display the diagnostic console as described in the "Accessing the Diagnostic Console" section and "Using the" section.

Step 6 Enter B (the Change the baud rate of main console RS232 interface option) from the to temporarily change the baud rate of the hub console port.

The following prompt is displayed:

Change the baud rate of the main console RS232 interface to one of 
the following values. Change the setting of your terminal 
application to match the value you selected.

[1] 9600   bps
[2] 19200  bps
[3] 38400  bps
[4] 57600  bps

Enter Selection:

Note   Make sure the console settings of the hub and the management station match.


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

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

Step 9 From your emulation session, locate the hub upgrade file and use the appropriate command to transfer the file to the hub.

Step 10 Enter U (the Upgrade operation firmware (XMODEM) option) from the .

The following prompt is displayed:

The XMODEM protocol will be used to perform this firmware upgrade.
The user must initiate an XMODEM file transfer from the terminal
side using an appropriate terminal application specific command.

Do you wish to continue with the download process? [Y]es or [N]o:

Entering N redisplays the .

Step 11 Enter Y, and press Return.

The following prompt is displayed:

Starting XMODEM download...

Is a prompt displayed when download is completed?

Step 12 When the download is completed, the follow prompt is displayed:

XMODEM download completed.

Download Buffer Checksum Test..............Pass
Upgrade system image to Flash memory.......Pass

Press any key to continue.

Pressing any key displays the .


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.

Recovering from a Lost or Forgotten Password

If 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 and "Using the" section.

(b) Enter C (the Continue with standard system start up option) from the .

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) and displays prompts for assigning hub IP information.You can then assign a password from the or from the CLI.

Entering N when a password exists allows that password to remain valid, and the hub opens a CLI session.

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:

Using the

The (Figure 4-4) provides system options from which you can reset 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 .

Figure 4-4 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 (NVRAM Setting)

[X] Exit to Previous Menu

Enter Selection:

Note   The [M] Memory I/O option on the is for Cisco personnel only. The [X] Exit to Previous Menu option displays the .


Resetting the Hub to the Factory Defaults

There 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 .

The following prompt is displayed:

Return system to factory defaults? [Y]es or [N]o:

Entering N redisplays the .

Step 2 Enter Y.

Resetting the Hub Console Port to Factory Defaults

To 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 .

The following prompt is displayed:

Return system to factory defaults? [Y]es or [N]o:

Entering N redisplays the .

Step 2 Enter Y.