7513 problem

[mohammedmahmoud]

Dear all,

My 7513 suffered from the following problem (snapshoot taken from sh logging) and afterwards all the VIPs restarted, is it a memory problem or what ???

Aug 21 17:06:40: %RSP-3-ERROR: MD error 0000008000004000

-Traceback= 403E55C4 403E5CA8 403E5DD8 403E73DC 403AF588

Aug 21 17:06:40: %RSP-3-ERROR: SRAM parity error (bytes 0:7) 10

-Traceback= 403E5698 403E5CA8 403E5DD8 403E73DC 403AF588

Thanks in advance.

[marikakis]

Please have a look at the Recommended Actions section of the following document:

http://www.cisco.com/en/US/products/hw/routers/ps341/products_tech_note09186a0080094793.shtml#recommend

Perhaps you could open a case if you are not satisfied with the above approach.

Those issues are normally not easily (if ever) resolved. It might even be "cosmic radiation" to blame:

http://www.cisco.com/en/US/products/hw/routers/ps341/products_tech_note09186a0080094793.shtml#softvshard

Many people enjoy reading that, when it's not their router spontaneously crashing!

[colin]

These issues have been around since day dot, and were fixed with the introduction of ECC memory into RSPs and VIPs.

A basic precis of the link is:

1) If it happens once or rarely, it's a single bit

parity error, and should just be dealth with as

a reload with no probably failure on the RSP/

VIP.

2) If it continually occurs, replace the memory on

the affected card. If it continues to happen

replace the affected line card.

Opening a TAC case on PMPE will not get you far really, unless you have the part under contract. Then ask for a replacement after following the troubleshooting procedures.

A card failure would probably present as a cbus stall.

Hope that helps,

-colin.

[mohammedmahmoud]

Hi Colin,

Thanks for your reply i think if it happens again, i'll replace the memory on the RSP.

Thanks very much.