Specifications

ManualsBrandsCisco ManualsComputer equipmentWS-X4515 - Supervisor Engine IV

Troubleshooting Hardware and Related Issues on Catalyst 4500/4000 Switches Running Cisco IOS Software

Contents

Introduction

Prerequisites

Requirements

Components Used

Conventions

Supervisor Engine or Module Problems

Supervisor Engine LED Is Red or Status Indicates Faulty

Switch Is in a Continuous

Boot Loop, Freezes or Halts During Boot, Is in ROMmon Mode, or Does Not Have the System Image

Standby Supervisor Engine Module Is Not Online or Status

Indicates Other

Switch Has Reset or Rebooted on Own

Upgrade ROMmon (PROM Upgrade) and Cisco IOS Software Issues

Ports 1/2 and 2/2 Do Not Function with Dual Supervisor Engines in 4507R

Supervisor Engine III That Runs Cisco IOS Software Release 12.1(11b)EW Ceases to Work or Unexpectedly Reboots

Supervisor Engine III or IV Exhibits Packet Loss

Troubleshoot Error Messages in the Syslog or Console

Troubleshoot Module Failure to Come Online

Interface Problems

Workstation Is

Unable to Log In to the Network During Startup or Unable to Obtain the DHCP Address

Troubleshoot NIC

Compatibility Issues

Interface Is in errdisable Status

Troubleshoot Interface Errors

Interface Is Stuck in the Receive Direction on Ports That

Connect to Hubs or Other Devices

MAC Address of Directly Connected Port is Not Learned by the Remote Device

Power Supply and Fan Problems

Power Supply on a 4500 Chassis Is in errdisable State in the Output of the show power Command

Power Supply Fail LED

Is On

Fan Assembly Failed in the show environment status Command

Diagnostic Commands

show version

show module

show diagnostics online module

show diagnostics power-on

show power

show environment status

show interface interface-id status

show errdisable recovery

show interface interface-id counters error

NetPro Discussion Forums - Featured Conversations

Related Information

Introduction

This document discusses the troubleshoot of hardware and related common issues on Cisco Catalyst 4500/4000 switches with Supervisor Engine II+, III, IV, and V modules. This document does not cover Supervisor Engine I and II troubleshoot practices. For information on the

troubleshoot of Supervisor Engine I and II, refer to Hardware Troubleshooting for Catalyst 4000/4912G/2980G/2948G Series Switches.

The Supervisor Engine II+, III, IV, and V run Cisco IOS® Software only. This table describes the support of these Supervisor Engine modules in various chassis:

Note:

Supervisor Engine modules need to run Cisco IOS Software Release 12.1(12c)EW or later in order to run on the 45xx chassis. The Supervisor Engine IV first release is Cisco IOS Software Release 12.1(12c)EW.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

Catalyst 4500/4000 with a Supervisor Engine III and IV

Cisco IOS Software Release 12.1(12c)EW

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Supervisor Engine or Module Problems

Supervisor Engine LED Is Red or Status Indicates Faulty

If your switch Supervisor Engine LED is red or the status shows faulty, there can be a hardware problem. This Common Reasons and Solutions section provides common reasons for this problem and solutions:

Common Reasons and Solutions

Console into the Supervisor Engine and issue the

show diagnostics power-on

command, if you can issue the command. If the action returns a failure, create a service request with Cisco Technical Support for further assistance.

If the switch does not boot and fails self diagnostics during the boot sequence, capture the output. Then, create a Cisco Technical Support service request for further assistance.

If you do not see any hardware failure in the boot sequence or in the output of the

show diagnostics power-on

command, create a Cisco

Technical Support service request for further assistance.

Switch Is in a Continuous Boot Loop, Freezes or Halts During Boot, Is in ROMmon Mode, or Does Not Have the System Image

If your switch Supervisor Engine is in a continuous boot loop, freezes or halts during boot, is in ROM Monitor (ROMmon) mode, or does not have the system image, the problem is mostly likely not a hardware problem. This Common Reasons and Solutions section provides

common reasons for this problem and solutions to recover the switch:

Common Reasons and Solutions

The Supervisor Engine is in a continuous loop if you have not set the boot variable correctly and you have set the configuration register to 0x2102. For instructions on how to recover the Supervisor Engine, refer to the

Recovering from a Continuous Reboot

section of the

document Recover a Cisco IOS Catalyst 4500/4000 Series Switch from a Corrupt or Missing Image or in Rommon Mode.

The Supervisor Engine goes into ROMmon mode or fails to boot when the system image is either corrupt or absent. For instructions on how to recover the Supervisor Engine, refer to the

Recovering from a Corrupt or Missing Image

section of the document Recover a Cisco

IOS Catalyst 4500/4000 Series Switch from a Corrupt or Missing Image or in Rommon Mode.

The Supervisor Engine III, IV, and V have 64 MB of onboard system Flash, which should easily hold multiple system images. Therefore, have a backup image. In addition to the bootflash:, the Supervisor Engine supports up to 128 MB of compact Flash in the slot0: device. The

Supervisor Engine also provides for transfer via TFTP of the image from ROMmon mode, which enables faster recovery of absent or corrupt images.

Note:

The Supervisor Engine II+ has 32 MB of onboard system Flash.

Caution:

If you run Cisco IOS Software Release 12.1(12c)EW, your switch can crash if you try to use the compact Flash. Format the compact Flash before use. The resolution of this issue is in Cisco IOS Software Release 12.1(13)EW and later.

Standby Supervisor Engine Module Is Not Online or Status Indicates Other

Another issue is the failure of the standby Supervisor Engine module to come online. The status of

other

faulty

in the output of the

show module

command or an amber Status LED indicates this problem. This Common Reasons and Solutions section provides common

reasons:

Common Reasons and Solutions

Console into the standby Supervisor Engine in order to check whether it is in ROMmon mode or in continuous reboot. If the standby Supervisor Engine is in either of these two states, refer to Recover a Cisco IOS Catalyst 4500/4000 Series Switch from a Corrupt or Missing

Image or in Rommon Mode.

4507#

show module

Mod Ports Card Type Model Serial No.

----+-----+--------------------------------------+-----------------+-----------

1 2 1000BaseX (GBIC) Supervisor(active) WS-X4515 JAB0627065V

Standby Supervisor

3 48 10/100/1000BaseTX (RJ45) WS-X4448-GB-RJ45 JAB053606AG

TAC Notice:

What's

Changing on TAC Web

Help us help you.

Please rate this

document.

Excellent

Good

Average

Fair

Poor

This document solved

my problem.

Yes

Just browsing

Suggestions for

improvement:

(256 character limit)

Send

Supervisor Engine Model Chassis with Support

Supervisor Engine II+ (WS-X4013+=) 4006, 4503, 4506, 4507R

Supervisor Engine III (WS-X4014=) 4006, 4503, 4506

Supervisor Engine IV (WS-X4515=) 4006, 4503, 4506, 4507R

Supervisor Engine V (WS-X4516=) 4006, 4503, 4506, 4507R, 4510R

Summary of content (7 pages)

PAGE 1
Troubleshooting Hardware and Related Issues on Catalyst 4500/4000 Switches Running Cisco IOS Software Contents TAC Notice: What's Changing on TAC Web Help us help you.
PAGE 2
4 48 10/100BaseTX (RJ45)V WS-X4148-RJ45V JAE060800BL M MAC addresses Hw Fw Sw Status --+--------------------------------+---+------------+----------------+--------1 0009.e845.6300 to 0009.e845.6301 0.4 12.1(12r)EW( 12.1(12c)EW, EAR Ok 2 Unknown Unknown Unknown Other 3 0001.6443.dd20 to 0001.6443.dd4f 0.0 Ok 4 0008.2138.d900 to 0008.2138.d92f 1.
PAGE 3
Note: The VlanZero counter can increase even if the TxCrcErrors counter does not increase. This situation can indicate a different issue. Contact Cisco Technical Support for further assistance. If you run Cisco IOS Software Release 12.1(11b)EW or later, issue the show platform cpu packet statistics command multiple times and look for increments in the VlanZeroBadCrc counter.
PAGE 4
{ NSB83619—Address resolution failed { NSB83589—Failed to boot after 1 attempt { NSB70519—Failed to connect to a server See this Common Reasons and Solutions section in order to determine if you experience one of the common reasons: Common Reasons and Solutions The reason for these symptoms can be an interface delay that either Spanning Tree Protocol (STP), EtherChannel, trunking, or an autonegotiation delay causes.
PAGE 5
If you review and troubleshoot with the documents that this section references and you still have issues, contact Cisco Technical Support for further assistance. Interface Is Stuck in the Receive Direction on Ports That Connect to Hubs or Other Devices If certain interfaces are stuck in the receive direction when they connect to hubs or other devices, the problem can be the bug that Cisco bug ID CSCdx79678 ( registered customers only) describes.
PAGE 6
4 48 10/100BaseTX (RJ45)V JAE060800BL WS-X4148-RJ45V M MAC addresses Hw Fw Sw Status --+--------------------------------+---+------------+----------------+--------1 0009.e845.6300 to 0009.e845.6301 0.4 Ok 2 0009.e845.6302 to 0009.e845.6303 0.4 12.1(12r)EW( 12.1(12c)EW, EAR Ok 3 0001.6443.dd20 to 0001.6443.dd4f 0.0 Ok 4 0008.2138.d900 to 0008.2138.d92f 1.
PAGE 7
z errdisable z faulty The command output also contains the VLAN of the interface and the speed and duplex information. 4507#show interfaces gigabitethernet 1/1 status Port Gi1/1 Name Status notconnect Vlan 1 Duplex Speed Type auto 1000 No Gbic show errdisable recovery The show errdisable recovery command helps you to know the status of the automatic errdisable time-out configuration for each of the ErrDisable reasons.