strange reload of standby msfc

Unanswered Question
Feb 5th, 2009

Hi,

I have two 6509 running as pair in two rooms.Both have TWO sup2 msfc as active and stanby.some how the both the standby sup2 reloaded same time on both switches,but we saw only parity eror on 1st switch active sup. any idea?

SW1

Feb 5 14:01:57 GMT: %MISTRAL-3-ERROR: Error condition detected: TM_DATA_PARITY_ERROR

Feb 5 14:01:31 GMT: %RUNCFGSYNC-6-SYNCEVENT:

Syncing Running Configuration to the Non-Designated Router

Feb 5 14:01:32 GMT: %RUNCFGSYNC-6-SYNCEVENT:

Syncing Startup Configuration to the Non-Designated Router

SW2

Feb 5 14:01:31 GMT: %RUNCFGSYNC-6-SYNCEVENT:

Syncing Running Configuration to the Non-Designated Router

Feb 5 14:01:32 GMT: %RUNCFGSYNC-6-SYNCEVENT:

Syncing Startup Configuration to the Non-Designated Router

REGARDS,

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
mchin345 Wed, 02/11/2009 - 14:17

This error: %RUNCFGSYNC-6-SYNCEVENT: states a running configuration synchronization event has occurred. No action required for this error.

But this Mistral-3-Error is the most common errors from the Mistral ASIC on the MSFC are TM_DATA_PARITY_ERROR, SYSDRAM_PARITY_ERROR, SYSAD_PARITY_ERROR, and TM_NPP_PARITY_ERROR. Possible causes of these parity errors are random static discharge or other external factors.

Actions

This Discussion