Ltl Parity Error
Contents |
Catalyst 6500 Series SwitchesTroubleshoot and AlertsTroubleshooting TechNotes Parity Errors Troubleshooting Guide Download Print Available Languages Download Options PDF (259.4 what is parity error KB) View with Adobe Reader on a variety of devices Updated:Jul ltl 2 ltl_parity_check 15, 2013 Document ID:116135 Document ID: 116135 Updated: Jul 15, 2013 Contributed by Shawn Wargo, Cisco Engineering. parity error cisco Download PDF Print Feedback Related ProductsCisco Catalyst 6500 Series Switches ContentsIntroductionBackgroundSoft ErrorsHard ErrorsCommon Error MessagesProcessorRAMASICLatest AdvancementsProcessorRAMASICSoftwareMSFC IBC Reset6700 Series 'Single-Bit Parity Error' ResetRecommendationsSoft Errors (SEU)Environmental AuditLatest parity error fix Firmware (Rommon)Thumb ScrewsHard Errors (Malfunction)Hardware (MTBF and EOL) AuditHardware DiagnosticsRelated Cisco Support Community DiscussionsIntroductionThis document describes soft and hard parity errors, explains common error messages, and recommends methods that help you avoid or minimize parity errors. Recent improvements in hardware and software design reduce parity problems as well. BackgroundWhat is a processor or memory parity error?Parity
System Returned To Rom By Processor Memory Parity Error At Pc
checking is the storage of an extra binary digit (bit) in order to represent the parity (odd or even) of a small amount of computer data (typically one byte) while that data is stored in memory. The parity value calculated from the stored data is then compared to the final parity value. If these two values differ, this indicates a data error, and at least one bit must have been changed due to data corruption.Within a computer system, electrical or magnetic interference from internal or external causes can cause a single bit of memory to spontaneously flip to the opposite state. This event makes the original data bits invalid and is known as a parity error.Such memory errors, if undetected, may have undetectable and inconsequential results or may cause permanent corruption of stored data or a machine crash.There are many causes of memory parity errors, which are classified as either soft parity errors or hard parity errors.Soft ErrorsMost parity errors are caused by electrostatic or magnetic-related e
Catalyst 6500 Series SwitchesTroubleshoot and AlertsTroubleshooting TechNotes Catalyst 6500 Series Switches: Identify a Module Affected by an LTL Parity Check Download Print Available Languages Download Options PDF (8.2 KB)
Imprecise Data Parity Error
View with Adobe Reader on a variety of devices Updated:Aug 16, 2013 Document parity error detected in vram ID:116435 Contents Introduction Prerequisites Requirements Components Used LTL Parity Check Request Identify the Affected Module Related Information Introduction This document high correctable ecc error rate detected cisco describes the method used in order to identify a module affected by a parity check on a Cisco Catalyst 6500 Series switch. Prerequisites Requirements Cisco recommends that you have knowledge of these topics: http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/116135-trouble-6500-parity-00.html Supervisor Engine 720 on Cisco Catalyst 6500 Series Switches Local Target Logic (LTL) parity check Components Used The information in this document is based on Cisco Catalyst 6500 Series switches that run Supervisor Engine 720. The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/116435-technote-product-00.html is live, make sure that you understand the potential impact of any command. LTL Parity Check Request You might encounter this log on a Catalyst 6500 Series switch: %LTL-SP-2-LTL_PARITY_CHECK: LTL parity check request for 0x33C9 The log indicates a parity check in the port ASIC/port index table Static Random-Access Memory (SRAM) used by some of the Catalyst 6500 Series modules. Identify the Affected Module In order to identify the module that encountered the parity check, transform the hexadecimal number seen in the log into a decimal. In this case,0x33C9 translates to decimal 13,257. Collect the output from the show diagnostic result module all detail command on the switch, and search for 13,257. It is listed as the LTL index for one of the modules. For example: 6500#show diagnostic result module all detailModule 1: CEF720 8 port 10GE with DFC SerialNo : XXXXXXXXXXOverall Diagnostic Result for Switch 1 Module 1 : PASSDiagnostic level at card bootup: minimalTest results: (. = Pass, F = Fail, U = Untested)___________________________________________________________________________1) TestOBFL ------------------------> .
May31,2011,3:05PM Post #1 of 2 (4579 views) Permalink %LTL-SP-2-LTL_PARITY_CHECK: LTL http://www.gossamer-threads.com/lists/cisco/nsp/148393 parity check request for 0x4B86. May 30 17:25:43: %LTL-SP-2-LTL_PARITY_CHECK: LTL parity check request for 0x4B86. Saw one of these on a 6500 with a Sup720-3BXL today, first time it's shown up in the logs.. Anything to be concerned about? Peter Kranz www.UnwiredLtd.com Desk: 510-868-1614 x100 Mobile: 510-207-0000 pkranz [at] unwiredltd _______________________________________________ parity error cisco-nsp mailing list cisco-nsp [at] puck https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ johgill at cisco May31,2011,3:24PM Post #2 of 2 (4386 views) Permalink Re: %LTL-SP-2-LTL_PARITY_CHECK: LTL parity check request for 0x4B86. [In reply to] Hi Peter, It's an error detection and recovery mechanism. Finding one error and correcting it (which is what has happened here) once ltl parity error in a while is not a bad thing. Possibly open a TAC case if you see it again soon. Once or twice a year is nothing to be concerned with though generally. Regards, John Gill cisco On 5/31/11 6:05 PM, Peter Kranz wrote: > May 30 17:25:43: %LTL-SP-2-LTL_PARITY_CHECK: LTL parity check request for > 0x4B86. > > Saw one of these on a 6500 with a Sup720-3BXL today, first time it's shown > up in the logs.. Anything to be concerned about? > > Peter Kranz > www.UnwiredLtd.com > Desk: 510-868-1614 x100 > Mobile: 510-207-0000 > pkranz [at] unwiredltd _______________________________________________ cisco-nsp mailing list cisco-nsp [at] puck https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ Index | Next | Previous | Print Thread | View Threaded Cisco BBA NAS NSP uBR VOIP Interested in having your list archived? Contact Gossamer Threads Web Applications & Managed Hosting Powered by Gossamer Threads Inc.
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 20 Oct 2016 10:07:44 GMT by s_wx1126 (squid/3.5.20)