Insight Control server provisioning allows you to capture the configuration of various server hardware components (such as the System ROM, HP Smart Array and iLO) 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 can be configured from a Build Plan, but because of the way these devices are configured, there is no capture functionality. See Perform a boot from SAN installation.
The typical sequence of steps when capturing and deploying configuration files:
-
Run the capture Build Plan on the server you want to capture
-
Rename the captured configuration file to something meaningful in your facility.
-
If desired, edit the captured configuration file to make customizations.
-
Make a copy of a Build Plan that deploys a configuration to your hardware type, and edit that copy.
-
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.
-
Save the Build Plan and run it on the server you wish to configure.
|
|
|
![[NOTE: ]](images/note.gif) |
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. |
|
|
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). iLO_Capture.xml_106701 is an example of a captured iLO. The server’s internal ID can be found on the Servers General properties screen.
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.