Checking The Fru Data Integrity - Intel SR4850HW4 - Server Platform - 0 MB RAM Product Manual

Service Technicians Guide
After the FRUSDR Load Utility is run with the configuration file and updates are successful, a
single message is displayed and the utility exits. If the FRUSDR Load Utility fails, it exits with an
error message and an exit code.
Loading Specified FRU or SDR Files
The normal method of loading one or more FRU or SDR files is through the use of a configuration
file. In the configuration file, each FRU file name is specified using the FRUNAME configuration
command. Each SDR filename is specified after the SDRNAME configuration command.
Through the use of a configuration file, each area of the FRU or SDR may selectively be
programmed. The FRU information written to the non-volatile storage device is verified after
programming and an appropriate message is displayed. Typically, all possible Sensor Data Records
exist in one master SDR file. Through the configuration file, tags can be used to selectively choose
the SDR records that are to be programmed.
Comparing the FRU or SDR File
For the FRU, the configuration file command "COMPARE" validates information against that
which is in the non-volatile storage device. For the SDR, the configuration file command
"COMPARE" compares SDR information against that which is in the SDR Repository.
"COMPARE" does not program information. "COMPARE" is placed on the same line after the FRU
or SDR name to be compared.
The compare command performs a byte-by-byte comparison of the non-volatile storage device data
against that which is to be programmed. For FRUs, the internal use area is never compared; this
utility considers all bytes of the internal use area as dynamic and subject to change by the firmware.
In the board area, the manufacturing date and time, and the board area checksum are also not
compared, although the rest of the board area bytes are compared.
For SDRs, the first two bytes of each Sensor Data Record are ignored, because when the repository
was programmed, the first two SDR bytes were modified by the BMC and a pointer inserted. No
checksum is issued.

Checking the FRU Data Integrity

The FRUSDR Load Utility requires the FRU Common Header offsets to be correct. The Utility
checks the Common Header Area in each non-volatile storage device against the FRU file, and it
runs a checksum on it. If the Common Header Area in the FRU file is correct and matches that
which is in the non-volatile storage device, then the information is programmed. An incorrect
Common Header means the FRU area is corrupted or has not been initialized.
If the Internal Use Area of the BMC is loaded from the FRU file, then the BMC is cold reset to
force the BMC to re-initialize its internal copy of the Internal Use area from the FRU. This clears
both the SDR table and the System Event Log. All information in both areas is lost and the SDRs
must be reprogrammed.
Updating the FRU and SDR Non-Volatile Storage Area
FRU Update: After the system configuration is determined, a typical configuration file updates
the FRU non-volatile storage area. It first verifies the Common Header area and checksum from
the specified FRU file with that which is programmed in the FRU non-volatile storage device.
If specified, the Internal Use Area is then read from the specified FRU file and is programmed
114 Intel® Server Platforms SR4850HW4 & SR4850HW4/M Product Guide