Configuration File; Probing Product Configuration; Checking The Fru Data Integrity; Updating The Sdr Non-Volatile Storage Area - Intel SR870BN4 - Server Platform - 0 MB RAM Product Manual

Configuration File

A CFG file may be used by the utility. The configuration file is ASCII text and editable. The file
is parsed, then pertinent information is stored internally by the utility. The information obtained
from the configuration file is used to direct the execution path of the utility and to establish a
configuration for the product. The configuration file allows the user to override values contained in
an associated FRU file; it does not allow the user to add areas to a FRU file. One should think of
the FRU in the non-volatile storage device as containing the default values. If the user decides to
leave out FRU areas or fields during programming, then the information already contained in those
FRU areas or fields on the Server will remain.
The utility executes commands formed by the strings present in the configuration file. These
commands cause the utility to perform various tasks needed to ultimately load the proper Sensor
Data Records into the non-volatile storage of the BMC and possibly generic FRU devices. Some of
the commands are user interactive and require a choice to be made by the user.
For detailed information on the configuration file format, see the "FRU and SDR Load Utility Plus
Configuration File Format EPS."

Probing Product Configuration

Using the information in the configuration file, the utility can probe the product configuration. For
more information see page 82 on the configuration file format of the "FRU and SDR Load Utility
Plus Configuration File Format EPS."

Checking the FRU Data Integrity

The utility needs the FRU Common Header offsets to be correct. The Utility checks the Common
Header Area in each NVS device against the FRU file, and also runs a checksum on it. If the
Common Header Area in the FRU file is correct and matches what is in the NVS device, then the
information is programmed. An incorrect Common Header means the FRU area is corrupted or has
never been initialized.
If the Internal Use Area of the BMC is loaded from the FRU file, then the BMC will be cold reset.
This is so the BMC re-initializes its internal copy of the Internal Use area from the FRU. The effect
of re-initializing the Internal Use Area is that both the SDR table and the SEL (System Event Log)
table are cleared. All information in both areas is lost and the SDRs must be reprogrammed.

Updating the SDR Non-Volatile Storage Area

After the utility validates the header area of the supplied SDR file, then it updates the SDR
repository area. Before programming begins, the utility clears the SDR repository area. When
loading an SDR file from a Configuration File, the utility filters all tagged Sensor Data Records
using a list of tags determined by the user, which represent the product's configuration.
Non-tagged Sensor Data Records are automatically programmed.

Updating the FRU Non-Volatile Storage Area

After the system configuration is determined, a typical configuration file updates the FRU
non-volatile storage area. It will first verify the Common Header area and checksum from the
specified FRU file with what is programmed in the FRU non-volatile storage device. If specified,
the Internal Use Area is then read out of the specified FRU file and is programmed into the
82 Intel® SR870BN4 Server System Product Guide