HP Insight Control Server Provisioning 7.2 Online Help

3.3.17 Capture hardware settings of a server and deploy them to other servers
Insight Control server provisioning allows you to capture the configuration of various server hardware
components (such as the System ROM, HP Smart Array, iLO, and Fibre Channel HBA) and deploy
the captured configuration to other servers. In addition, you can customize the captured configuration
before redeploying it.
There are capture and deploy Build Plans for each of the various hardware component types
(System ROM, Smart Array, iLO), and they all work the same way. Note that Fibre Channel HBAs
also have capture and deploy Build Plans; they are slightly different and are covered in “Perform
a boot from SAN installation” (page 22).
Procedure 13 The typical sequence of steps when capturing and deploying configuration files:
1. Run the capture Build Plan on the server you want to capture
2. Rename the captured configuration file to something meaningful in your facility.
3. If desired, edit the captured configuration file to make customizations.
4. Make a copy of a Build Plan that deploys a configuration to your hardware type, and edit
that copy.
5. Replace the configuration file step in the Build Plan copy with your new configuration file.
Remember to copy any path parameters from the old step to the new one.
6. Save the Build Plan and run it on the server you wish to configure.
NOTE: Running a capture or deploy Build Plan will cause the target servers to reboot into the
service OS. Use caution when running these Build Plans on production servers.
NOTE: Capture and deploy Build Plans end with target servers left in the Linux service OS. You
can add steps to the Build Plan to leave the servers in a different state.
Capture
To capture a configuration, simply run one of the capture Build Plans against the managed server
you wish to capture. The capture Build Plan should require no modification at all. When the Build
Plan completes, a new configuration file will be listed in the Configuration Files main menu. The
file name will be the name of the file captured from the server (for example, iLO_Capture.xml),
followed by the internal server ID of the server the file was captured from (typically a six to nine
digit integer). As an example, a captured iLO configuration file could be
iLO_Capture.xml_106701. The server’s internal ID can be found on the server’s General
properties page.
Deploy
Sample deploy configuration Build Plans are provided for each hardware type. Although you can
run these unmodified, these are meant to be samples. You should make a copy of these samples
and replace the sample configuration file in the Build Plan with the configuration file you wish to
deploy. No other part of the deploy Build Plan should require modification.
3.3.18 Change a Build Plan’s timeout
By default, a Build Plan must complete in under two hours or the Build Plan will time out. If you
wish to change that time, you can override the default timeout value by adding a custom attribute
to the Build Plan. The name of the custom attribute is timeout and the value must be an integer
that represents the new timeout in seconds.
Note that the timeout custom attribute must be assigned to a Build Plan; a timeout custom
attribute defined at the facility level will be ignored.
See “Editing OS Build Plan custom attributes” (page 57) for additional information.
3.4 Scripts how do I ... ?
• “Create a new script” (page 31)
30 How Do I ... ?