[c-nsp] 6500 parity error

[Ian Cox]

At 09:49 AM 6/24/2005 -0400, Jon Lewis wrote:
>I just got one of these on one of our 6509s.
>
>%SYSTEM_CONTROLLER-SP-3-ERROR: Error condition detected: TM_DATA_PARITY_ERROR
>
>Googling or searching cio for %SYSTEM_CONTROLLER-SP-3-ERROR: yields 0
>hits.  Searching cio for TM_DATA_PARITY_ERROR turned up 2 hits (one for
>the 6500, one for the 7600, probably the same data) for 12.1E software.

http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/12_1e/msgguide/emsg.htm#wp1185555

>Error Message    MISTRAL-SP-3-ERROR: Error condition detected:
>[chars]
>
>Explanation    The most common errors from the Mistral ASIC on the
>supervisor engine are TM_DATA_PARITY_ERROR and TM_NPP_PARITY_ERROR.
>Possible causes of these parity errors are random static discharge or
>other external factors.
>
>In 12.2(18)SXD3, is SYSTEM_CONTROLLER-SP-3-ERROR = MISTRAL-SP-3-ERROR ?

Yes, the name was changed to be more generic than have ASIC codenames 
so people outside development and test know what the error message refer to.


>Would this be from the memory on the SUP2 (not the MSFC2 memory)?

No. There are two System controllers, one for the RP and another for 
the SP. It is the SP System Controller that is reporting the error.


Ian

>----------------------------------------------------------------------
>  Jon Lewis                   |  I route
>  Senior Network Engineer     |  therefore you are
>  Atlantic Net                |
>_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
>_______________________________________________
>cisco-nsp mailing list  cisco-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/