Diagnostic Test Description for Intel CDM v 2.0 Diagnostic Provider

Contents

Objective

Overview

Terms and Definitions

Abbreviations and Acronyms

Diagnostic Test Descriptions

EEPROM Test

FIFO Test

Adapter Register Test

Loop-back Test

Execution of IS_EXLUSIVE diagnostics

Implementation of ‘delete_instance’ for associations class

Objective

This document describes all supported diagnostics by Intel CDM v2.0 Provider. Possible user scenarios are described in order to deliver knowledge of what to do when the diagnostics return an error.

Overview

The Intel CDM v2.0 Provider is the CDM-compliant Diagnostics Provider for Intel’s Ethernet adapter cards only. CDM Provider makes use of CDM architecture to expose the diagnostics for network adapters (NIC’s) through CIM Object Manager (CIMOM). A client application, running a layer above CIMOM, can query the standard CIM interface for diagnostics data and execute diagnostic tests. CDM allows the client application to:

This Provider is based on CIM Schema 2.26.

Terms and Definitions

Term

Definition

CDM
(Common Diagnostic Model)

CDM is an architecture and methodology for exposing system diagnostics instrumentation through the CIM standard interface.

CIM
(Common Information Model)

CIM is an extensible object oriented schema for system management being developed by the Distributed Management Task Force (DMTF), and is evolving, industry-wide, as the basis for system management architectures.

MOF
(Managed Object Format)

A language for defining CIM classes and instances. The MOF format offers a textual means of adding data to the CIMOM repository. The MOF eliminates the need to write code, thus providing a simple and fast technique for modifying the CIMOM repository.

MOF File

A text file that contains definitions of classes and instances using the Managed Object Format (MOF) language.

CIM Schema

A collection of class definitions that describe managed objects in a particular environment.

Abbreviations and Acronyms

 

Abbreviation

Description

CIM

Common Information Model

CDM

Common Diagnostics Model

CIMOM

CIM Object Manager

CMPI

Common Management Provider Interface

CUDL

Common Utilities Diagnostic Library
(part of the Quartzville SDK)

DMTF

Distributed Management Task Force

FW

Firmware

HW

Hardware

ME

Managed Element

MOF

Managed Object Format

MSE

Managed System Element

NAL

NIC Abstraction Layer
(part of the Quartzville SDK)

NIC

Network Interface Card

QV

Intel Quartzville SDK

SW

Software

Diagnostic Test Descriptions

EEPROM Test

The EEPROM test re-calculates the EEPROM checksum on the adapter and matches it against the checksum stored in the adapters EEPROM checksum word.  If the re-calculated checksum does not match the checksum found in the EEPROM, then the test will fail. If this test fails, it can also indicate either an inability to read/write the EEPROM or that the EEPROM needs to be reconfigured using one of the Intel-supplied EEPROM configuration tools.  On some hardware, this test also ensures that the EEPROM size word is written correctly.

User Scenarios

Scenarios of EEPROM test pass/fail

Test

Description

PASS

Diagnostic test passed. If the transmission through a network adapter still does not work, please check the network cable.

FAIL

Diagnostic test failed. One of the probable causes is improper check sum of EEPROM image. The steps, which are recommended:

  1. Contact Intel technical support and obtain appropriate EEPROM image and software in order to update the whole EEPROM image data.
  2. Repeat the EEPROM diagnostic test.
  3. If repeated test still fails it means that the hardware is damaged.

FIFO Test

The FIFO test reads and writes special test patterns to the internal FIFO on the network adapter and checks to see if the same patterns that went into the FIFO came back out.  This test helps to verify that the adapter’s onboard FIFO memory is valid. If this test fails, it indicates that the FIFO is not working correctly.  This test is limited to the adapters that allow read/write access to the FIFO directly.

User Scenarios

Scenarios of EEPROM test pass/fail

Test

Description

PASS

Diagnostic test passed.

If the transmission through a network adapter still does not work, please check the network cable.

FAIL

Diagnostic test failed.

Any of the returned values indicate that the hardware is damaged and there is not a way to resolve this problem.

If possible, reinsert the network adapter card into the slot and if the repeated diagnostic test still fails please contact Intel Technical Support.

Adapter Register Test

This test will, on most adapters, read and write known values into the register set into register offsets that will allow this. The values are read back and verify that the register memory is operating as expected.  Some adapters may substitute a self-test for this test. Currently, the PRO/100 series adapter does this.

User scenarios

Scenarios of Adapter Register test pass/fail

Test

Description

PASS

Diagnostic test passed.

If the transmission through a network adapter still does not work, please check the network cable.

FAIL

Diagnostic test failed.

Any of returned values indicate that the hardware is damaged and there is not a way to resolve this problem.

If possible, reinsert the network adapter card into the slot and if repeated diagnostic test still fails please contact Intel Technical Support.

Loop-back Test

This test decides which kind of loop-back test should be executed: MAC loop-back or PHY loop-back tests. The manner in which the test is executed is always the same. This test sends 20000 packets in each of 3 separate test passes. The first pass sends packets full of only 0’s. The second pass sends packets full of only 1’s. The third pass uses a marching data pattern (0x00, 0x01, 0x02 … 0xFF). The packets are fully validated. The test will fail if any sent packet is not received or if a single data validation failure occurs.

User Scenarios

Scenarios of Loopback test pass/fail

Test

Description

PASS

Diagnostic test passed.

If the transmission through a network adapter still does not work, please check the network cable.

FAIL

Diagnostic test failed.

Any of returned values indicate that the hardware is damaged and there is not a way to resolve this problem.

Execution of IS_EXLUSIVE diagnostics

Some of the diagnostic tests have the IS_EXLUSIVE characteristic set. In a case when the user is trying to execute the same diagnostic two or more times the CDMv2 Provider checks if are there any jobs which are in progress and are connected with this diagnostic test. In this case Intel CDMv2 Provider returns ‘Failed’ (4). This case was secure because when those executions of diagnostics test contain a Loop Control parameter set to the value greater than value 1, only one iteration of loop was uninterrupted and finally the loop-diagnostics for two executions were made alternately.

Implementation of ‘delete_instance’ for associations class

The following association classes always return DELETE_INSTANCE_OK when the method ‘delete_instance’ is called: