Filter
Top Products
222 MPCMM0001 Chassis Management Module Software Technical Product Specification
FRU Update Utility
26.3 FRU Update Process
The FRU update process is controlled by the configuration file (not including forced FRU
recovery). The configuration file is capable of querying the system and user for information. The
configuration file can be modified to adjust how the FRU update proceeds. Because the update
process is controlled by a user modifiable file, the utility will perform a three part update process to
ensure a proper update is performed.
The first step is to read the file and validate the syntax of the commands. If there are any errors in
the configuration file, an error message will be displayed stating which line in the file had an error
and what that error was. The utility will exit after the first error has occurred.
The second step is to process the commands in the configuration file and validate them to the
hardware. This step will perform probing, gather user input, and read the FRU devices in the
chassis and perform the first verification of the FRUs. All update files will also be read and
validated at this time.
When validating the FRU file to use for the update, the utility will compare the IPMI FRU header
in the update file to the IPMI FRU header in the system hardware. If the headers are not equal, the
utility will exit with an error. This is a measure to ensure that the correct FRU file was chosen for
the location. If the user desires more verification that the FRU is for the correct device, probing
commands can be used in the configuration file to validate product IDs, manufacturer name, and
other fields.
The third step is to commit the changes to the system. The FRUs are written in the order they are
specified in the configuration file. If any FRU fails to write, the utility will exit and display an error
to why the FRU failed to update; none of the FRUs due to be updated after the failed FRU will be
updated. All FRUs successfully written before the failure will remain updated.
If, while writing to the FRU, the device times out with a communication error or the FRU write
command fails, the utility will attempt the command two more times. The communication layer
will also attempt each command three times before returning an error, for a total of nine retries per
IPMI command before exiting.
26.4 FRU Recovery Process
If the user is attempting to recover a corrupted FRU, they will use the forced FRU recovery option.
With this option, no FRU verification will be done with the target device’s FRU before the update
happens. No header comparison will be performed, and the target FRU information will not be read
and validated.
When doing a forced FRU recovery, all information on the target FRU WILL BE LOST and will be
replaced by the data in the recovery FRU file, including protected fields.
A FRU file to force onto the target device needs to be provided. The data in this FRU file will be
written onto the target device.