Important Information about FRUSDR STL2 Load Utility with Support Files Version TL-4.3.B Copyright (c) 2000-2001, Intel Corporation ALL RIGHTS RESERVED December 10, 2001 This document describes some specifics of the FRU & SDR Utility STL2 Package Version TL-4.3.B. This utility is used for updating the server management sub-system product level Field Replacement Unit (FRU), Sensor Data Repository (SDR), and the System Management (SM BIOS) non-volatile storage components. The FRUSDR utility is used to update the non-volatile storage device associated with the Baseboard Management Controller, which holds the SDR & FRU areas. The utility has the capability to generically handle FRU devices that may not be associated with the Baseboard Management Controller (BMC). Through the use of a configuration file, added features allow the user to control the execution path by probing hardware, for the STL2 this feature is not supported by the BIOS and firmware. The user may still request user input, and setting tags to provide filtering of FRU and SDR data. Multiple FRU and SDR files may also be processed at once. If the user receive an error concerning the FRU headers not matching, when trying to program a FRU file, this happens when the FRU file on the server is a non-compatible version with the one you are trying to program. In this case you should contact your vendor for support and get a system update package made to handle this problem. The FRUSDR utility fully supports IPMI 0.9 and IPMI 1.0 specifications. Be aware that both the FRU and SDR file formats have changed to support IPMI 1.0, and are not backward compatible. The utility will work correctly on either a IPMI 0.9 system or a IPMI 1.0 system, but mixed IPMI systems are not supported. Important Notes A. Install B. Parse the Command Line C. Display FRU, SDR, and SMB Information D. Temporary Files E. FRU Field Lengths F. Documentation G. Latest Changes Errata Items A. Unsupported Type Codes Important Notes A. Install The FRUSDR Loader is meant to be used as a DOS application on a server. The utility should be placed onto a bootable DOS floppy and the system rebooted prior to and after using. There is no need to actually install the application on to a server. Running the utility in a Window's DOS box is not supported and will provide incorrect results. Normal Command Line Use: A:> FRUSDR -CFG MASTER.CFG Note: Programming the BMC FRU internal use area clears the SDR repository. Therefore, the SDR repository must be reprogrammed after programming the BMC. Upon completion of programming the FRU and SDR areas, remove the floppy disk and reboot the server. B. Parsing the Command Line The FRUSDR Loader command line provides the following options: Usage: /? or /h Displays usage information. /d {smb,fru,sdr} Only displays requested area. /cfg filename.cfg Uses custom CFG file. /p Pause between blocks of data. Note: Users may alternatively use a '-' instead of the '/'. C. Display FRU, SDR, and SMB Information The SDR area can be displayed by using the -D SDR parameter with the FRUSDR command, such as FRUSDR -D SDR. The SM BIOS (SMB) area can be displayed with the -D SMB parameter with the FRUSDR command. Note: The system must be rebooted in order for the SM BIOS (SMB) changes to take effect. The -D FRU parameter will display the BMC FRU area by default. To view other FRU areas, additional addressing information must be provided: The -D FRU command may be followed with up to 16 device addresses. These device addresses are used to view up to 16 different FRU areas. The arguments following the "-D FRU" are in the same order and value as the NVS_TYPE, NVS_LUN, DEV_BUS and DEV_ADDRESS which may be found in the FRU file header of each FRU file. The LUN address is optional. If the LUN address is used, it must start with an 'L'. Usage: FRUSDR /d fru (device) [lun] (bus) (addr1) (addr2) (etc) Examples for the STL2 Server: 1. To display the STL2 SM BIOS area: C> FRUSDR /P /D SMB Note: You must reboot the system after programming the FRU area before the correct information will show-up in the SM-BIOS table. 2. To display the STL2 SDR's: C> FRUSDR /P /D SDR 3. To display the STL2 BMC FRU: C> FRUSDR /P /D FRU Note: If your system does not display the above FRU device, then it probably does not contain that device. D. Temporary Files: If you desire to create temporary files, you must use the undocumented "/tmp" switch on the command line, then when the FRUSDR Loader is executed, it creates temporary files that may be used to aid in recreating a problem, should one arise. The FRUSDR Loader does not remove the temporary files, the temporary files may be erased by the user after the FRUSDR Loader has completed. E. FRU Field Lengths If a user is going to develop their own Configuration, FRU or SDR files, then they need a thorough understanding of FRU areas and lengths. That discussion is beyond the scope of this document. Although, only a basic understanding of how the FRUSDR application uses FRU files is needed before one modifies information in a FRU field via a configuration file prompt. The governing FRU format and SM BIOS specification documents do not specify a maximum FRU field length. However, a length constraint does exist due to the limited amount of space available in the Non-Volatile Storage device containing these items. These maximum lengths are artificial since, if all strings were of the maximum length, the FRU file would overflow the FRU area. Therefore, the true maximum field length is actually controlled by the space available to the FRU file. As a rule, the length defined in the header of the FRU file and the sizes defined in each FRU area of the FRU file must not be altered. These were originally chosen so that the FRU file would fit into the FRU area. Often each FRU area does contain a certain amount of padding, which will allow an increase in the length of some strings. To be on the safe side, if FRU strings are modified, they should be kept at the same length as the current string in that FRU area. For fields such as the Asset Tag, for which data may not exist to fill the field, the length should be kept to as few characters as needed, not to exceed 31 characters. F. Documentation: Additional information on the FRUSDR Loader may be found in the Product Manual. G. Latest Changes: Added support for the SR2100 chassis and associated power supplies. Fixed the chassis name of the SR2000 chassis to SR2050. Errata Items A. Unsupported Type Codes In this release only ASCII and BCD Type field codes are supported. ASCII6, Binary and UNICODE Type Codes are not supported. Regarding SM BIOS (SMB) strings, only ASCII characters are supported in these fields.