Guest

Cisco Catalyst 6500 Series Switches

Catalyst 6500 Series Switches: Identify a Module Affected by an LTL Parity Check

Introduction

This document 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:

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 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 detail

Module 1: CEF720 8 port 10GE with DFC SerialNo : XXXXXXXXXX

  Overall Diagnostic Result for Switch 1 Module 1 : PASS
  Diagnostic level at card bootup: minimal

  Test results: (. = Pass, F = Fail, U = Untested)
  ___________________________________________________________________________

    1) TestOBFL ------------------------> .

<snip>

    15) TestLtlFpoeMemoryConsistency ----> .

          Error code ------------------> 0 (DIAG_SUCCESS)

          Total run count -------------> 2889738

          Last test testing type ------> Health Monitoring

          Last test execution time ----> Mar 15 2013 02:06:57

          First test failure time -----> n/a

          Last test failure time ------> n/a

          Last test pass time ---------> Mar 15 2013 02:06:57

          Total failure count ---------> 0

          Consecutive failure count ---> 0

      LTL PARITY

          Ltl index -------------------> 13257

          Rbh value -------------------> 255

<snip>

Scroll through the output in order to discover the module that maps to this LTL, which is the module from which the log came.

Related Information

Updated: Aug 16, 2013
Document ID: 116435