Prev: want to buy SPA-4XOC3-POS-V2 today
Next: PIX minimal setup for pinging out the inside
From: Ethan Mao on 16 Dec 2009 23:48
i found this error in syslog when i check the cisco 6509 today.

"Nov 7 08:52:28: %MISTRAL-3-ERROR: Error condition detected:
TM_DATA_PARITY_ERROR"

this appears only one time, and i checked the cisco.com, and found
this explanation:
"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."

has anyone had come across this error before? do i have to do anything
except monitoring the switch syslog to confirm whether the error
message was an isolated one?
From: bod43 on 17 Dec 2009 14:47
On 17 Dec, 04:48, Ethan Mao <maoyix...(a)gmail.com> wrote:
> i found this error in syslog when i check the cisco 6509 today.
>
> "Nov  7 08:52:28: %MISTRAL-3-ERROR: Error condition detected:
> TM_DATA_PARITY_ERROR"
>
> this appears only one time, and i checked the cisco.com, and found
> this explanation:
> "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."
>
> has anyone had come across this error before? do i have to do anything
> except monitoring the switch syslog to confirm whether the error
> message  was an isolated one?

I wouldn't be concerned unless the message was repeated.
 | 
Pages: 1
Prev: want to buy SPA-4XOC3-POS-V2 today
Next: PIX minimal setup for pinging out the inside