|
|
This chapter provides the following sections that describe potential problems and provide corrective actions:
Table 5-1 lists symptoms, possible causes, and corrective actions associated with
| Symptom | Possible Cause | Resolution |
|---|---|---|
Incorrect full-duplex settings for 10BaseT and 100BaseT connections. Full-duplex status is shown with the Mode button and the FDUP LED. Check the port statistics:
|
| |
|
Port statistics show excessive FCS, late-collision, or alignment errors. For 100BaseTX connections:
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. | |
No connectivity | Incorrect or bad cable.
|
See "Connectors and Cables," for the correct pinouts and the proper use of crossover vs. straight-through cables. Replace with a known good cable. |
Configuration problems. | Use the Diagnostic Console - System Debug Interface Menu to reset the switch. | |
Incorrect baud rate. | Use the Diagnostic Console - System Debug Interface Menu to reset the modem parameters to their factory defaults. | |
Unable to join a switch cluster | Use the CDP Configuration/Status Menu to enable CDP version 2. | |
Faulty connection to the command switch. | Use the [S] Show Neighbor option on the CDP Configuration/Status Menu, or use the CDP Management Page to display the devices connected to the switch. | |
Command switch is not running IOS Release 12.0(5)XP software or higher. | Upgrade the command switch with the correct firmware. | |
There are already 15 cluster members under the command switch. | Decide whether to replace an existing cluster member with the switch or to add the switch to a different switch cluster. | |
| Mismatched cluster configuration between the member switch and the command switch. Switch was removed from the cluster by using one of the following methods from the member switch:
| Note We recommend using the command-switch management interfaces to remove member switches from a cluster instead of using the previously mentioned methods (such as using the reset to factory defaults option from the management console).
|
RPS not operational. | Verify that the RPS is connected properly to the switch and is connected to an AC power outlet. For information about the RPS, see the Cisco RPS documentation. | |
Verify the connection of both ends of the power cord. | ||
Power supply failure. |
| |
SYSTEM LED is amber; port status LEDs off | See the "Recovering from Corrupted Firmware" section of this chapter for firmware upgrade instructions. | |
Devices not powered up. | Ensure both devices have power. | |
Verify the connection at both ends of the cable. | ||
Wrong cable type. | Verify the cable type (crossover vs. straight-through). | |
Incorrect wiring. | See "Connectors and Cables," for pinout information. | |
Faulty cable. | Replace the cable with a known good one. | |
Port LED alternating green and amber | Link fault. |
|
Port LED amber | Port not forwarding. |
|
Shielded twisted-pair cable is the most commonly used cable in Token-Ring environments. The media interface connectors (MICs) and baluns---used to connect shielded twisted-pair and unshielded twisted-pair cabling---create a loopback when they are disconnected; the loopback might cause anomalies with the switch.
To prevent loopback problems when using shielded twisted-pair cabling in a Token-Ring network environment, make sure the MICs and baluns are never left unconnected when they are part of a link connected to the switch (see Figure 5-1).
As described in the "Powering Up and Using POST to Test the Switch" section, the switch runs 13 tests each time it is powered up. This section provides information about fatal and nonfatal POST failures and recovery procedures.
If a nonfatal failure occurs, the SYSTEM LED is amber, and the switch is still operational and can forward packets, but it might not operate optimally. The Management Console Logon Screen displays the POST failure message that identifies the nonfatal failure(s) detected. For information about displaying POST results, see the "Starting Up the Switch and Displaying the POST Results" section.
If your switch has a fatal failure, the SYSTEM LED is amber, and one or more of the port LEDs are amber. The switch is not operational, but the amber port LED(s) indicate which test(s) failed.
Table 5-2 describes the individual tests and their associated LEDs.
| Port LEDs | Test |
|---|---|
16x | Fatal---ECU DRAM test. Switch is not operational. |
15x | Not used during POST. |
14x | Not used during POST. |
13x | Not used during POST. |
12x | Fatal---Forwarding engine test. Switch is not operational. |
11x | Fatal---Forwarding engine SRAM test. Switch is not operational. |
10x | Fatal---Packet DRAM test. Switch is not operational. |
9x | Fatal---ISLT ASIC test. Switch is not operational. |
8x | Fatal---Port control/status test. Switch is not operational. |
7x | Fatal---System timer interrupt test. Switch is not operational. |
6x | Fatal---CAM SRAM test. Switch is not operational. |
5x | Nonfatal---Real-time clock test. If this test failed, the switch forwards packets. However, if the switch unexpectedly shuts down, it cannot restart itself automatically. |
4x | Nonfatal---Console port test. If this test failed, you cannot access the management console through the console port. You can still Telnet to the management console. |
3x | Fatal---Content addressable memory test. Switch is not operational. |
2x | Nonfatal---Built-in address test. If this test failed, the switch uses the default Ethernet address of the switch and begins forwarding packets. |
1x | Nonfatal---Port loopback test. If this test failed, some functionality to one or more ports is lost. The switch disables any port(s) that failed this test, and the failure message on the Management Console Logon Screen indicates which port(s) did not pass this test. Connect only to ports that passed this test. |
The diagnostic console is a menu-drive interface that you can use to perform the following tasks:
To display the diagnostic console, follow these steps:
Step 1 Connect a management station with terminal emulation software (such as ProComm, HyperTerminal, tip, or minicom) supporting the XMODEM Protocol to the switch console port. For information about connecting to the console port, see the "Connecting to the Console Port" section.
Step 2 Start up the emulation program.
Step 3 Set the line speed on the emulation software to 9600 baud.
Step 4 Unplug the power cord from the back of the switch.
Step 5 Press and hold in the Mode button, and at the same time, reconnect the power cord to the switch.
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 5-2 appears.
------------------------------------------------- Cisco Systems Diagnostic Console Copyright(c) Cisco Systems, Inc. 1999 All rights reserved. Ethernet Address: 00-E0-1E-7E-B4-40 ------------------------------------------------- Press enter to continue.
The Diagnostic Console - Systems Engineering Menu (Figure 5-3) provides options from which you can troubleshoot firmware problems and then restart the switch as usual.
To display this menu, press Enter from the Diagnostic Console Logon Screen.
Diagnostic Console- Systems Engineering Operation firmware version:9.00.00 Status: valid Boot firmware version:3.02 [C] Continue with standard system start up [U] Upgrade operation firmware (XMODEM) [S] System Debug Interface Enter Selection:
Operation firmware version---The version of the switch firmware.
Status---Valid or invalid. If the firmware is not valid, the [C] Continue with standard system start up option is not displayed, and the following warning is displayed:
WARNING!!! Operation Firmware is invalid
Upgrade firmware to enable switch operation.
Boot firmware version---Current version of the write-protected part of the firmware that supports the diagnostic console.
[C] Continue with standard system start up---Use this option after you have resolved the firmware problems with the [U] Upgrade operation firmware (XMODEM) or [S] System Debug Interface option. The system exits the diagnostic console and restarts.
[U] Upgrade operation firmware---Initiate a firmware upgrade. This option works with XMODEM and uses the default RS-232 parameters: 9600 baud, 8 data bits, 1 stop bit,
no parity, no flow control. You are prompted to choose a baud rate of 9600 or 57600 for the download. The console baud rate returns to 9600 immediately after the download.
Instead of using XMODEM, you can use 1KXMODEM to significantly reduce the download time.
[S] System Debug Interface---Display the Diagnostic Console - System Debug Interface Menu shown in Figure 5-5.
To display the POST results, enter the [C] Continue with standard system start up option from the Diagnostic Console - Systems Engineering Menu. For example, a POST failure message, such as the one in Figure 5-4, is displayed on the Management Console Logon Screen. In this example, ports 1x to 8x and port Ax (or port A) failed test 1 (nonfatal---port loopback test).
After you have resolved any firmware problems by using the [U] Upgrade operation firmware (XMODEM) option on the Diagnostic Console - Systems Engineering Menu to reinstall the firmware, use the [C] Continue with standard system start up option on the Diagnostic Console - Systems Engineering Menu to restart the switch.
If a nonfatal failure occurs, the SYSTEM LED turns amber.
Catalyst 1900 Management Console Copyright (c) Cisco Systems, Inc.1993-1999 All rights reserved. Standard Edition Software Ethernet address: 00-E0-1E-7E-B4-40 PCA Number: 73-2239-01 PCA Serial Number: SAD01200001 Model Number: WS-C1924-A System Serial Number: FAA01200001 ------------------------------------------------- *** Power On Self Test (POST) failed *** *** Failed Test(s): 1 *** Failed Port(s): 1 2 3 4 5 6 7 8 A 1 user(s) now active on Management Console. Press any key to continue.
 | Caution If you interrupt the transfer by turning the switch off and on, the firmware could get corrupted. |
From the diagnostic console, you can download the upgrade file from a management station to the switch by using the XMODEM protocol. The procedure for downloading the firmware through XMODEM is largely dependent on the terminal emulation software you are using.
To download the switch firmware by using the XMODEM protocol, follow these steps:
Step 1 Copy the switch 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 that is using terminal emulation software (such as ProComm, HyperTerminal, tip, or minicom) that supports the XMODEM Protocol to the switch console port.
Step 3 Start up the 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 and the "Using the Diagnostic Console - Systems Engineering Menu" section.
Step 6 Enter the [U] Upgrade operation firmware (XMODEM) option from the Diagnostic Console - Systems Engineering Menu.
Step 7 Enter [Y]es at the prompt to confirm the download:
Do you wish to continue with the download process, [Y]es or [N]o?
It can take up to 1 minute to erase the existing firmware.
Entering [N]o redisplays the Diagnostic Console - Systems Engineering Menu.
Step 8 You are then prompted to choose a transmission speed. Enter 9 (for 9600)
or 5 (for 57600):
Do you wish to upgrade at [9]600 (console speed) or [5]7600?
After you select the transmission speed, the following prompt appears:
Waiting for image at the configured baud rate.
Step 9 From your terminal emulation session:
The system starts the XMODEM download.
Step 10 When the upgrade is complete, the Diagnostic Console Logon Screen is displayed, and the switch returns to 9600 baud. Change the baud rate on the management station back to 9600 baud, if necessary.
Step 11 Press Return to display the Diagnostic Console - Systems Engineering Menu, and enter the [C] Continue with standard system start up option from the Diagnostic Console - Systems Engineering Menu to restart the switch with the upgraded firmware.
If you have lost or forgotten the switch password, you can clear the existing password and assign a new password.
To recover from a lost or forgotten password, follow these steps:
Step 1 Power-cycle the switch.
After POST completes, the follow prompt is displayed:
Do you wish to clear the passwords? [Y]es or [N]o:
Step 2 Enter [Y]es to delete the existing password from nonvolatile RAM (NVRAM). You can then assign a password from the switch management interfaces (management console or CLI).
Entering [N]o maintains the existing password as valid.
The Diagnostic Console - System Debug Interface Menu (Figure 5-5) provides system options for resetting the console port or the entire switch to the factory defaults.
To display this menu, enter the [S] System Debug Interface option from the Diagnostic Console - Systems Engineering Menu.
Diagnostic Console- System Debug Interface [G] Generic I/O [M] Memory (CPU) I/O [F] Return system to factory defaults [R] Reset main console RS232 interface to 9600,8,1,N [P] POST diagnostic console [X] Exit to Previous Menu Enter Selection:
[G] Generic I/O---For Cisco personnel only.
[M] Memory (CPU) I/O---For Cisco personnel only.
[F] Return system to factory defaults---Return the switch to its factory settings. All static and dynamic addresses are removed, as are the IP address and all other configurations. Enter [Y]es or [N]o, and press Return. The changes take effect when the switch is reset.
[R] Reset main console RS232 interface to 9600, 8, 1, N---Use this option if you have lost the management console connection because of an improper modem configuration. When the switch is reset, the default RS-232 configuration is used.
[P] POST diagnostic console---For Cisco personnel only.
There can be times when you need the diagnostic console even though the firmware is valid. This could happen, for example, if the switch configuration prevents the firmware from executing properly and you cannot display the management interfaces.
To reset to the switch to the factory defaults, follow these steps:
Step 1 Enter the [F] 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]o redisplays the Diagnostic Console - System Debug Interface Menu.
Step 2 Enter [Y]es.
To reset to the switch console port to the factory defaults, follow these steps:
Step 1 Enter the [R] 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]o redisplays the Diagnostic Console - System Debug Interface Menu.
Step 2 Enter [Y]es.
Posted: Thu Oct 28 19:59:28 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.