how to find out what cause the error in the log?

Unanswered Question
Dec 28th, 2007
User Badges:

The core layer of mynetwork is cisco6509.

the distribution is cisco 4500/3600 series

the access layer is bay switchs.

- - - - - -

recently, I found lots error info frequently appears in "sh log" result.

It appears like this :

Dec 28 14:44:19.738: %EARL_L3_ASIC-SP-STDBY-3-INTR_WARN: EARL L3 ASIC: Non-fatal

interrupt Packet Parser block interrupt

Dec 28 14:44:19.735: %EARL_L3_ASIC-SP-3-INTR_WARN: EARL L3 ASIC: Non-fatal inter

rupt Packet Parser block interrupt

Dec 28 14:44:46.406: %MLS_STAT-SP-4-IP_CSUM_ERR: IP checksum errors

Dec 28 14:44:47.074: %MLS_STAT-SP-STDBY-4-IP_CSUM_ERR: IP checksum errors

- - - -

My questions is how to find out what cause this problem and locate the damn source.

= = = =

I found no answer in cisco tech docs and google.I will very appreciate thanks for any suggestions.

= = = = = = =

(please forgive my poor english)

(~_~)

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
smothuku Fri, 12/28/2007 - 00:52
User Badges:
  • Silver, 250 points or more

Hi ,


I got little info for you.


%MLS_STAT-4-IP_CSUM_ERR: IP checksum errors

The system has received one or more packets with IP checksum errors.


Recommended Action: Copy the error message exactly as it appears on the console or in the system log. Enter the show mls statistics command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from theshow mls statistics command output, contact your Cisco technical support representative and provide the representative with the gathered information.


Related documents- No specific documents apply to this error message.


%EARL_L3_ASIC-3-INTR_WARN: EARL L3 ASIC: Non-fatal interrupt [chars]

This message indicates that the EARL L3 ASIC detected an unexpected non-fatal condition.


Recommended Action: If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.


Related documents- No specific documents apply to this error message.


Better contact Cisco TAC to resolve this issue asap.


Thanks,

satish


Actions

This Discussion