Intel STL2 Product Guide - Page 50

Using Specified CFG File, Filtering Sensor Data Record From the SDR File

Page 50 highlights

Displaying FRU Area The FRU area is displayed in ASCII format when the field is ASCII or as a number when the field is a number. Each FRU area displayed is headed with the FRU area designated name. Each field has a field name header followed by the field in ASCII or as a number. The Board, Chassis, and Product FRU areas end with an END OF FIELDS CODE that indicates there is no more data in this area. The Internal Use area is displayed in hex format, 16 bytes per line. Displaying SDR Area The SDR nonvolatile storage area is displayed in the following hex format. The data is separated by a Sensor Record Number X header, where X is the number of that sensor record in the SDR area. The next line after the header is the sensor record data in hex format delineated by spaces. Each line holds up to 16 bytes. The data on each line is followed by the same data in ASCII format; nonprintable characters are substituted by a period (.). 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. Nontagged 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. 50 Intel Server Board STL2 Product Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80

50
Intel Server Board STL2 Product Guide
Displaying FRU Area
The FRU area is displayed in ASCII format when the field is ASCII or as a number when the field
is a number.
Each FRU area displayed is headed with the FRU area designated name.
Each field
has a field name header followed by the field in ASCII or as a number.
The Board, Chassis, and
Product FRU areas end with an END OF FIELDS CODE that indicates there is no more data in this
area.
The Internal Use area is displayed in hex format, 16 bytes per line.
Displaying SDR Area
The SDR nonvolatile storage area is displayed in the following hex format.
The data is separated
by a Sensor Record Number X header, where X is the number of that sensor record in the
SDR area.
The next line after the header is the sensor record data in hex format delineated by
spaces.
Each line holds up to 16 bytes.
The data on each line is followed by the same data in
ASCII format; nonprintable characters are substituted by a period (.).
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.
Nontagged 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.