Identify root cause failure

Bedevere Curry · ‎07-29-2013

We have a Catos ver 6.3 running sup2 on slot 1 and 2. Trying to find out what caused the failure.

Reza Sharifi · ‎07-29-2013

The CPU seems to be running high. You should open a ticket with TAC and send them the "sh tech" for analysts.

HTH

Bedevere Curry · ‎07-29-2013

Not sure where you're getting high cpu but this is what I got from output interpret

CPU ANALYSIS
------------

NOTE: Since catalyst platforms perform most of packet forwarding in hardware,
the 'show proc cpu' command shows the CPU utilization of processes such as STP,
CDP, VTP etc., the traffic handled by the supervisor module.

INFO: Top processes by 5 minute utilization are:
  show_command          4.62%

Bedevere Curry · ‎07-29-2013

This is what I kind of wanted to know cause it's not very clear what exactly is the issue:

Exceptions: 1

Loaded NMP version: 6.3(5)

Reload same NMP version count: 11

Last Exception occurred on Jul 25 2013 19:33:23 ...

Software version = 6.3(5)

Error Msg:

PID = 0 Kernel an

EPC: 807807DC

Stack content:

sp+00: 81A45C20 85D99C00 00002425 00002627

sp+10: 00002829 00002A2B 00002425 00002627

sp+20: 00000829 8038DF58 00000000 00000000

WARNING: The log output indicates 1 exceptions.

This number tracks the number of exceptions in the program and the number of Non-Maskable

Interrupt (NMI) counters. It tracks error conditions that altered the normal

flow of the program. It also tracks changes in conditions that cause the microprocessor

to stop the current task and handle the situation through a different routine.

These exceptions are similar to interrupts. The NMI is a variant of an interrupt.

It is a high-priority interrupt that cannot be disabled by another interrupt

operation. Fatal exceptions (which are exceptions where packets cannot be forwarded),

are recorded on the NVRAM log.

TRY THIS: Reseat the Supervisor module and all the linecards