IDSM-2 error

Unanswered Question
Jul 14th, 2009
User Badges:

Received follow error after service module was restarted:


From diagnostics event -

07/13 13:08:10.573 E [2] komodo_plus_lb_pc_port[2/7]: check_ether_packet failed (err-code 43)


From sh log -

Jul 13 13:04:34: SP: The PC in slot 2 is shutting down. Please wait ...

Jul 13 13:05:04: SP: PC shutdown completed for module 2

Jul 13 13:05:14: %C6KPWR-SP-4-DISABLED: power to module in slot 2 set off (Reset)

Jul 13 13:08:09: %DIAG-SP-6-RUN_MINIMUM: Module 2: Running Minimal Diagnostics..

.

.Jul 13 13:08:11: %HA_EM-6-LOG: tmpsys:/eem_policy/Mandatory.go_bootup.tcl: GOLD

EEM TCL policy for boot up diagnostic

Jul 13 13:08:11: %DIAG-SP-3-MAJOR: Module 2: Online Diagnostics detected a Major

Error. Please use 'show diagnostic result <target>' to see test results.

Jul 13 13:08:11: %CONST_DIAG-SP-3-BOOTUP_TEST_FAIL: Module 2: TestPCLoopback fai

led on port(s) 3-4

Jul 13 13:08:11: %OIR-SP-3-LC_FAILURE: Module 2 has Major online diagnostic fail

ure, Card will be powered reset to re-run diagnostic. Please check sup-bootflash

diaginfo file for previous detailed diagnostic resu

Jul 13 13:08:12: %OIR-SP-3-PWRCYCLE: Card in module 2, is being power-cycled off

(Diagnostic Failure)

Jul 13 13:08:12: %C6KPWR-SP-4-DISABLED: power to module in slot 2 set off (Diagn

ostic Failure)

Jul 13 13:11:38: %DIAG-SP-6-RUN_MINIMUM: Module 2: Running Minimal Diagnostics..

.

.Jul 13 13:11:40: %HA_EM-6-LOG: tmpsys:/eem_policy/Mandatory.go_bootup.tcl: GOLD

EEM TCL policy for boot up diagnostic

Jul 13 13:11:40: %DIAG-SP-3-MAJOR: Module 2: Online Diagnostics detected a Major

Error. Please use 'show diagnostic result <target>' to see test results.

Jul 13 13:11:40: %CONST_DIAG-SP-3-BOOTUP_TEST_FAIL: Module 2: TestPCLoopback fai

led on port(s) 3-4

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
rhermes Tue, 07/14/2009 - 07:18
User Badges:
  • Gold, 750 points or more

Looks like your IDSM is sick. I'd open a TAC case to get it RMA'ed.



Farrukh Haroon Thu, 07/16/2009 - 00:00
User Badges:
  • Red, 2250 points or more

Try removing it from the chassis once and then reinsert.


If that does not work, and you cant re-image the module by any menas, go for RMA, as mentioned by the first responder.


Regards


Farrukh

mkelly26 Thu, 07/16/2009 - 00:51
User Badges:

Reseat was my first option as we couldn't access the module. Temporarily indicates good condition but then fails.

Replacement module on route.

Actions

This Discussion