Specifications

ManualsBrandsCisco ManualsComputer equipmentWS-X4515 - Supervisor Engine IV

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

Unknown Unknown Unknown Other

3 0001.6443.dd20 to 0001.6443.dd4f 0.0 Ok

4 0008.2138.d900 to 0008.2138.d92f 1.6 Ok

Make sure that the Supervisor Engine module properly seats in the backplane connector and that you have completely screwed down the Supervisor Engine installation screw. For more information, refer to the

Installing

and Removing the Supervisor Engine

section of the

document Installation

and Configuration Note for the Catalyst 4000 Family Supervisor Engine IV.

In order to identify whether the standby Supervisor Engine is faulty, issue the

redundancy reload peer

command from the active Supervisor Engine and through the console to the standby Supervisor Engine. Observe the bootup sequence in order to identify any hardware

failures. Currently, the active Supervisor Engine cannot access the power-on diagnostics results of the standby Supervisor Engine.

Make sure that these configurations are synchronized between the active and redundant Supervisor Engines:

{

Startup configuration

{

Boot variable

{

Configuration register

{

Calendar

{

VLAN database

If a software upgrade is performed on both the active and standby Supervisor Engines, check to determine if both Supervisor Engines run the same new software image. If the software images are not the same, upgrade the software image. Use the procedure in the

Performing

a Software Upgrade

section of Configuring Supervisor Engine Redundancy on the Catalyst 4507R.

If the standby Supervisor Engine still does not come on line, create a service request with Cisco

Technical Support. Use the log of the switch output that you collected from the above output and the troubleshoot steps.

Switch Has Reset or Rebooted on Own

This Common Reasons and Solutions section provides common reasons that your switch can reset without any manual intervention:

Common Reasons and Solutions

The switch can have had a software crash. In order to check if a software crash is the reason, issue the

more crashinfo:data

command.

The

more crashinfo:data

command displays the crash information from the last time that the switch crashed on the console or terminal. This command identifies the date and time of the last crash, which helps you determine if the reset that you experienced is because of the

crash that is on record.

The crashinfo:data are not present if the switch has never crashed. If the switch has crashed at least once, there is a record of the crash. Currently, there is no way to clear the crashinfo:data which exist in the memory. Make sure that the reset or reboot that you troubleshoot is

due to the crashinfo:data. In order to verify the cause, check the date and the time of the last crash, as this example shows:

Switch#

more crashinfo:data

Current time: 04/21/2000 19:58:10

Last crash: 04/21/2000 03:58:56

Build: 12.1(11b)EW, EARLY DEPLOYMENT

pc=006B14FC lr=006B14FC msr=0002B030 vector=00000700

!--- Output suppressed.

In order to display the standby Supervisor Engine crashinfo:data, issue the

more slavecrashinfo:data

command. This command displays any crashinfo:data that are on record in the current standby Supervisor Engine.

If the command indicates a software crash at the time that you suspect that the switch rebooted, the problem can be something other than a hardware failure. Contact Cisco

Technical Support with the output of these commands:

{

show tech-support

{

show logging

{

more crashinfo:data

Check the power source for the switch to make sure that the power source did not fail. If you use an uninterruptible power supply (UPS), make sure that the UPS does not have any problems.

If you are still unable to determine the problem, contact the Cisco

Technical Support Escalation Center.

Upgrade ROMmon (PROM Upgrade) and Cisco IOS Software Issues

If you have a Catalyst 4500/4000 series switch that runs Cisco IOS Software Release 12.1(12c)EW or earlier and you want to upgrade your switch to Cisco IOS Software Release 12.1(12c)EW1, you must also upgrade the Supervisor Engine III or IV ROMmon version to Cisco

IOS Software Release 12.1(12r)EW or later. If you need further assistance, refer to the

Upgrading the System Software

section of the Release Notes for the Catalyst 4500 Series Switch, Cisco IOS Release 12.1(20)EW2. If you still need assistance, contact the Cisco Technical

Support Escalation Center.

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

If you have dual Supervisor Engines in a Catalyst 4507R chassis and your ports 1/2 and 2/2 do not function, the problem is not a hardware problem. The system works as per the design. See this Common Reasons and Solutions section for further information:

Common Reasons and Solutions

In a Catalyst 4507R that uses Supervisor Engine IV modules, the design of the dual uplinks is to work when only one Supervisor Engine is present. This design means that if only one Supervisor Engine is present and is in slot 1, both ports 1/1 and 1/2 are functional. Also, if only

one Supervisor Engine is present and is in slot 2, ports 2/1 and 2/2 are functional. When dual Supervisor Engines are present, only ports 1/1 and 2/1 are functional and 1/2 and 2/2 are not functional. This lack of function is not a failure. For more information, refer to the

Supervisor

Engine Redundancy Guidelines and Restrictions

section of the document Configuring Supervisor Engine Redundancy on the Catalyst 4507R.

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

If your switch Supervisor Engine that runs Cisco IOS Software Release 12.1(11b)EW suddenly fails to work or unexpectedly reboots, the problem can be the bug that Cisco bug ID CSCdx94797 (

registered customers only

) describes. The fix is available in Cisco IOS Software

Release 12.1(11)EW1 or later. If you still need assistance, contact the Cisco Technical Support Escalation Center. For additional information about this issue, refer to the Field Notice: Catalyst 4000 Switches Defer 12.1(11b)EW Image - System Failure Possible.

Supervisor Engine III or IV Exhibits Packet Loss

If your system is a Catalyst 4500/4000 with Supervisor Engine III or IV and exhibits partial or full loss of network connectivity or packet loss, make sure to perform basic troubleshoot procedures to eliminate the common causes. The common causes include:

Bad cabling

A bad port

Speed and duplex mismatch

Network interface card (NIC) issues

If you troubleshoot these common reasons and you are not able to narrow down the problem, follow the troubleshoot steps in this section and capture the output of commands at each step. Contact Cisco Technical Support for troubleshoot assistance.

1. Issue the

show platform software interface all

command at the time that you observe the packet loss issue.

If you run software earlier than Cisco IOS Software Releases 12.1(8a)EW or 12.1(8a)EW1, issue the

show platform software interface all | include TxCrcErrors

command multiple times and look for increments in the

TxCrcErrors

counter. Here is an example:

cat4k#

show platform software interface all | include TxCrcErrors

TxCrcErrors: 1870

cat4k#

show platform software interface all | include TxCrcErrors

TxCrcErrors: 1920

cat4k#

If you run Cisco IOS Software Release 12.1(11b)EW or later, issue the

show platform software interface all | include DroppedBadPackets

command multiple times and look for increments in the

DroppedBadPackets

counter. Here is an example:

cat4k#

show platform software interface all | include DroppedBadPackets

DroppedBadPackets : 8004

cat4k#

show platform software interface all | include DroppedBadPackets

DroppedBadPackets : 8130

cat4k#

These counters are only visible if they have a nonzero value in them. Therefore, if you issue the command and do not see any output, your switch does not exhibit the problem. Here is an example:

cat4k#

show platform software interface all | include DroppedBadPackets

cat4k#

If you see increments in the

TxCrcErrors

DroppedBadPackets

counters, continue to Step 2.

2. If you run Cisco IOS Software Release 12.1(8a)EW or 12.1(8a)EW1, issue the

show platform cpuport all

command multiple times and look for increments in the

VlanZero

counter.

Here is an example:

cat4k#

show platform cpuport all | include VlanZero

VlanZero

130363 5 5 5 4

Cat4k#

cat4k#

show platform cpuport all | include VlanZero

VlanZero

130383 5 5 5 4

Cat4k#