Customizing the Toolkit Environment

Customize the configuration of target servers: Though all platforms use the same configuration file, regardless of the platform model, you can modify the configuration file to use a different file for each platform or MAC address.

The sample scripts included in SSTK (deploy.sh, linux-setup.sh, etc.) use the same configuration files (sstk.conf, acu.ini, hba-emulex.ini, hba-qlogic.ini, conrep.xml, conrep.dat) for all target servers. You can edit and customize the scripts to use a hardware attribute (such as a MAC address, serial number, server model, etc.) as an index. For example, you can modify the deploy.sh script to apply a specific ACU configuration (acu-rx2620.ini, acu-rx4640.ini, etc.) to each server depending on its model.

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 might not be necessary.

Customize the Linux kernel: HP recommends that you use the kernel shipped with the toolkit because it has been tested on all supported HP Integrity servers.Using the SSTK Deployment Workflow