Hi Paul I think it is a phsyical problem with this chases , may be due to the position or electrical conditions causes some sort of biasing for memory ASIC and leads to this reload loop
you can start check chaises postition , electrical isolation , grounding and supply and tenperature and if it didn't work , might be persistent problem with backplane best regards --Ibrahim On Sat, May 9, 2009 at 9:51 PM, Paul Stewart <[email protected]> wrote: > Hi folks. > > > > I posted about this before and was told it was either bad memory or bad sup > cards.. Have a pair of 7606's with sup720-3bxl . these errors occur on one > system and not the other. To top it off, we got these same errors showing > up a couple of times now on 6509 with sup2/msfc2 recently.. > > > > May 9 07:16:21: %SYSTEM_CONTROLLER-SP-STDBY-3-ERROR: Error condition > detected: TM_DATA_PARITY_ERROR > > May 9 07:16:21: %SYSTEM_CONTROLLER-SP-STDBY-3-EXCESSIVE_RESET: System > Controller is getting reset so frequently > > > > Both 7606 chassis are running 12.2(33)SRA7 and this also occurred when they > were running SXF train. We have many 6500's and only one of them so far > has exhibited the same errors and it is running 12.2(18)SXF16 > > > > Just looking for thoughts. we swapped spare supervisors between the 7600 > showing issues and the one that doesn't log any errors, kicked it over and > still see these issues.. Bad chassis?? > > > > Are these errors critical in nature or more just informative? > > > > Thanks for your time, > > > > Paul > > > > > > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
