Filter
Top Products
Configuration Software and Utilities 55
Using Specified CFG File
The utility can be run with the command line parameter of -cfg filename.cfg. The filename can be
any DOS accepted, eight-character filename string. The utility loads the specified CFG file and
uses the entries in the configuration file to probe the hardware and to select the proper SDRs to load
into nonvolatile storage.
Displaying Utility Title and Version
The utility displays its title:
FRU & SDR Load Utility, Version X.XX
Where X.XX is the revision number for the utility.
Configuration File
The configuration file is in ASCII text. 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 SDRs into the nonvolatile storage of the BMC and possibly generic
FRU devices. Some of the commands may be interactive and require you to make a choice.
Prompting for Product Level FRU Information
Through the use of a Configuration File, the utility may prompt you for FRU information.
Filtering Sensor Data Record From the SDR File
The MASTER.SDR file has all the possible SDRs for the system. These records may need to be
filtered based on the current product configuration. The configuration file directs the filtering of
the SDRs.
Updating the SDR Nonvolatile Storage Area
After the utility validates the header area of the supplied SDR file, it updates the SDR repository
area. Before programming, the utility clears the SDR repository area. The SDR file is loaded via
the .cfg File. Then the utility filters all tagged SDRs depending on the product configuration set in
the Configuration File. Non-tagged SDRs are automatically programmed. The utility also copies
all written SDRs to the SDR.TMP file. It contains an image of what was loaded, and the TMP file
is also useful for debugging the server.
Updating FRU Nonvolatile Storage Area
After the configuration is determined, the utility updates the FRU nonvolatile storage area. First it
verifies the Common Header area and checksum from the specified FRU file. The Internal Use
Area is read out of the specified .FRU file and is programmed into the nonvolatile storage. The
Chassis, Board, Product and MultiRecord areas are read out of the specified .FRU file, if they exist,
then those areas are programmed into the FRU nonvolatile storage. All the areas are also written to
the FRU.TMP file, which is useful for debugging the server.
Updating SMB FRU Nonvolatile Storage Area
After programming the BMC FRU area, the corresponding SMB fields are automatically updated
when the server is re-booted.