Displaying SDR Area
The SDR non-volatile storage area is displayed in the following hex format. A Sensor Record
Number X header separates the data, 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 then followed by the same data in ASCII format,
non/printable characters (ch < 32 || ch > 126) are substituted by a '.'.
Example:
Reading SDR Repository, please wait.........
Displaying SDR area
Reading SDR Record #1
0E 00 10 01 37 20 00 0F 05 00 10 F1 F8 02 01 85
02 00 00 00 04 00 00 C4 02 00 08 30 C2 07 91 95
8E FF 00 1B 1B 00 99 95 00 8A 8E 02 02 00 01 CC
53 43 53 49 2D 42 2D 54 65 72 6D 33
Reading SDR Record #2
0E 40 10 01 30 20 00 13 05 00 10 F1 F8 04 01 05 .@..0 ..........
00 00 00 20 29 00 00 1E 02 00 00 00 00 00 00 00
00 FF 00 03 03 00 00 00 00 42 49 02 02 00 01 C5
46 41 4E 2D 32
User Specified CFG File
The utility is normally invoked with the command line parameter of /CFG ["Filename"] where the
"filename" can be any accepted character filename string. This feature loads the indicated CFG
file. The utility uses the entries in the configuration file to probe the hardware and to select the
proper Sensor Data Records to be programmed into non-volatile storage. If the argument /CFG is
used without a filename, then the default file 'MASTER.CFG' is used, if it exists.
Loads Specified FRU File
The normal method of loading one or more FRU files is through the use of a configuration file.
Each FRU file name is specified using the FRUNAME configuration command. The first time a
FRU file is programmed, all areas in the FRU file need to be written, and this initialization should
be done in manufacturing. The FRUSDR utility does not support first time programming of
FRU areas.
Once the FRU file has been initially programmed, then the FRUSDR utility may be used to update
specific FRU areas and fields. The user may not change the size of any FRU area from the size
defined in the original FRU Header. Through the use of a configuration file, each area of the FRU
may selectively be programmed. The FRU information written to the non-volatile storage device is
verified after programming and an appropriate message is displayed. For more detailed information
on creating and using a configuration file see "Configuration File" on page 82.
In the FRU file header there exists a pad byte that may be any one-byte value without directly
causing an error, this pad byte is used in calculating the header checksum. If the header checksum
is incorrect, then a message is displayed so indicating.
80
....7 ..........
...........0....
................
SCSI-B-Term3
...
)...........
.........BI.....
FAN-2
Intel® SR870BN4 Server System Product Guide
Need help?
Do you have a question about the SR870BN4 - Server Platform - 0 MB RAM and is the answer not in the manual?
Questions and answers