Customizing The Toolkit Environment; Troubleshooting; Log File Format - HP Integrity rx1620 Deployment Manual

2. Launch the hardware configuration and software installation. If the target system is
cell-based you must create a hard partition for OS installation. Select the Windows
installation (win) option when prompted. The script runs utilities that configure the target
server hardware and then launches the software installation. After the process ends, verify
that the OS is up and running, and specify system settings to complete the installation.

Customizing the toolkit environment

After you have gained some familiarity with the SSTK, you might find yourself eager to take
advantage of its flexibility using your own scripts and customizations. HP suggests the following
ways in which you can extend the capabilities of the toolkit environment.
• Customize the configuration of target servers: The sample scripts use the data_files
directory for storing server configurations. This means that the same configuration is applied
to all target servers represented by a platform. You can also select target servers using a
different index and apply the configuration selectively. For example, you can specify a
unique configuration for each server using its MAC address as the index.
• Customize the Linux root file system: The rootfs.gz file enables the server to boot to the
toolkit environment with network connectivity. You can edit the network settings in the
packaged rootfs.gz file to accommodate your deployment, but this may not be necessary.
• Customize the Linux kernel: We recommend that you use the kernel shipped with the
toolkit because it has been tested on all supported Integrity servers. If you rebuild the kernel
or obtain a kernel from another distribution, you will need to do extensive testing to verify
that it runs with the hardware in HP Integrity servers.

Troubleshooting

SSTK uses a log mechanism to record errors and messages generated by the scripts. To generate
the log, write permission must be enabled for $REPOSITORY/data_files/log in the SSTK
repository.
SSTK creates a file, yyyymmdd-prodname-prodserial.log, where yyyymmdd is the current
date (yyyy = year, mm = month, and dd = day), prodname is the machine product name, and
prodserial is the product serial number.
For example, 20070615-server-Integrity-Virtual-Machine-VM00721000.log

Log file format

For each Action command executed with an SSTK script, the following type of entry is recorded
in the log file:
[14:43:03] Check repository contents and security
Command: check_repository
Return Value: 0
Standard output:
Standard error:
Security risk. Some folder(s) other than 'data_files' have write permission at the repository.
[14:43:05] done.
[14:43:05] Moving log to repository
Command: move_log2rep
Return Value: 0
Standard output:
Standard error:
[14:43:05] done.
[14:43:06] Copying toolkit and configuration files
Command: copy_toolkit
Return Value: 0
Standard output:
Standard error:
acu.ini not found.
hba-emulex.ini not found.
hba-qlogic.ini not found.
[14:43:07] done.
20 Overview