Intel SC450NX Product Guide - Page 72

Using Specified CFG File, FRU & SDR Load Utility, Version 2.0

Page 72 highlights

Displaying SDR Area The SDR nonvolatile storage area is displayed in the following hex format. The data are 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 are followed by the same data in ASCII format; nonprintable characters (ch < 32 || ch > 126) are substituted by a period (.). Example: To display the SDR area, type frusdr -d sdr and press . 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 that 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 2.0, Revision 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 run tasks needed to 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 might prompt you for FRU information. Filtering Records From the SDR File The MASTER.SDR file has all the possible SDRs for the system. These records might 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 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. The TMP file is also useful for debugging the server. 72

  • 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
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200

72
Displaying SDR Area
The SDR nonvolatile storage area is displayed in the following hex format.
The data are 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 are followed by the same data in ASCII format;
nonprintable characters (ch < 32 || ch > 126) are substituted by a period (.).
Example:
To display the SDR area, type
frusdr -d sdr
and press <Enter>.
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 that 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 2.0, Revision 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 run tasks needed to 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 might prompt you for FRU information.
Filtering Records From the SDR File
The MASTER.SDR file has all the possible SDRs for the system.
These records might 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 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.
The TMP file is also useful for debugging the server.