Configuring the CMS

Licensing Insight Orchestration

Log in to HP SIM.
Click DeployLicense Manager to launch License Manager.
Click Add Licenses. The Add License screen appears.
Enter your Insight Orchestration license key, and click Process. If the license key is valid, the license details appear.
Click Apply Licenses.
To select the target systems, select All Servers, ProLiant Blades, or virtual machine hosts, and then click View contents. A list of servers available to Insight Orchestration displays.
Select one or more servers, and then click Apply.
To continue licensing the selected servers, click Next.
Insight Orchestration supports ProLiant c-Class blades as physical servers or virtual machine hosts, and ProLiant ML and DL servers as virtual machine hosts. If a server is not valid for use by Insight Orchestration, the server is labeled with a red No and removed from the list.
Select one or more of the servers, and then click Select License.
Select a license with available seats, and then click Apply License.
The servers are licensed for Insight Orchestration. If any of the selected servers require additional license keys, a warning message displays the required products.
To use Insight Orchestration, a managed server must be licensed with:
- Insight Orchestration
- Insight Dynamics — VSE
- Insight Control Environment for BladeSystem (ICE BL)
- Insight Control Environment (ICE) for virtual machine hosts running on ProLiant DL or ML servers
- Virtual Connect Enterprise Manager – enclosure licenses
- Rapid Deployment Pack
Each of these products requires a separate license key. For more information on the installation and licensing of these products, see the product documentation.

Virtual provisioning

Virtual provisioning requires a correctly configured and licensed virtual machine host that is discovered and visible in HP SIM. You can run either ESX or Hyper-V on the virtual machine host.

If your environment utilizes ESX3i, HP recommends setting the virtual.max.concurrent.requests attribute in the hpio.properties file to 4.

Setting up the virtual machine switch

To add a network for use by the virtual machines provisioned through Insight Orchestration, do the following:

Open VMWare Infrastructure Client, enter the IP and credentials of your Virtual Infrastructure Server, and then click Login.
For each ESX/ESX3i virtual machine host in your ESX cluster, do the following:
1. Select the virtual machine host in the left navigation pane on the left.
2. Select the Configuration tab
3. Click Networking.
4. Click Add Networking.
5. For connection type, a select Virtual Machine, and click then click Next.
6. Depending on the network configuration of your virtual machine host, either select an existing virtual switch or select Create a virtual switch, and click Next.
7. In Port group properties, enter a name for your network in Network Label, and depending on the network configuration of your virtual machine host, enter a VLAN ID.
  Insight Orchestration identifies networks based on the name you enter. If you plan to add this network to VirtualConnect, then the name must be identical for Insight Orchestration to recognize the network as the same network.
8. Click Next.
Click Finish.
Repeat the process for each network.

Creating VMM templates

You can utilize an ESX or Hyper-V virtual machine as the source material for a VMM template without any additional steps. However, to provision recoverable logical servers:

For ESX, verify that the Enable HA option is enabled in the cluster settings section of the VMware Infrastructure 3 server. For more information, see your VMware Infrastructure 3 documentation.
For Hyper-V, deploy your Hyper-V virtual machine host in a Windows cluster. For more information, see your Windows documentation.
When using Hyper-V, do not use a Hyper-V VMM template created from a virtual machine with Snapshot. VMM templates created from a virtual machine with Snapshot, do not display on the Software tab of the Insight Orchestration console, preventing the successful creation of a Insight Orchestration template.

To create VMM templates from virtual machines, using HP SIM:

Click DeployVirtual Machine TemplatesCreate Virtual Machine Template. The Step 1: Select Source Virtual Machine screen appears.
Select a virtual machine from the list, and click Next. The Step 2: Select VM Template Repository Host screen appears.
Select the ESX host that will receive the new VMM template, and click Next. The Step 3: Specify the template Name and select VM Template Repository Folder screen appears.
In Template Name, enter a name for the template and specify a location for the template.
To store the VMM template, in the target folder, select Browse and select a virtual machine Host data store folder.
Click Next. The Step 4: Confirm Details screen appears.
Click Run Now. The task results appear.
VMM template creation might take from 5 minutes up to 30 minutes to complete.

Microsoft Windows customization requirements

Insight Orchestration customizes the Windows operating system for each Windows virtual machine it provisions. Windows virtual machine customization is supported by combining two sources of information and passing them to VMM. VMM passes the information to ESX and Hyper-V for customization. This information includes:

Specific attributes from the service template such as hostname.
Contents of the Insight Orchestration sysprep.inf file, located at C:\Program Files\HP\Insight Orchestration\conf\Sysprep.inf. An Insight Orchestration administrator can edit this file to specify additional customizations for Windows virtual machines.

To enable this customization on:

VMware VirtualCenter 2.0, install the Microsoft Sysprep tools on the Virtual Center management server in the sysprep folder: C:\Program Files\VMware\VMware VirtualCenter2.0\resources\windows\sysprep.
VMware VirtualCenter 2.5, install the Microsoft Sysprep tools on the Virtual Center management server in the sysprep folder: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\sysprep\1.1.
Microsoft Hyper-V, install the Microsoft Sysprep tools on the HP central management server in HP VMM sysprep folder:
- Windows 2003: Virtual Machine Management Pack Install Location\sysprep\2003
- Windows 2000: Virtual Machine Management Pack Install Location\sysprep\2000
- Windows XP: Virtual Machine Management Pack Install Location\sysprep\xp

If not installed, the sysprep folder does not exist and is required for Windows virtual machines. For more information, see the VMware VirtualCenter and the Installing the Microsoft Sysprep Tools article in the VMware Infrastructure 3 Online Library.

Physical provisioning

Physical provisioning requires:

Applying a patch to the Rapid Deployment Pack server to avoid scheduling issues
Virtual Connect Domain Groups available on Virtual Connect Enterprise Manager (VCEM)
Creating Rapid Deployment Pack job folders
Creating SAN-backed storage

Applying the Rapid Deployment Pack server patch

For Insight Orchestration to work correctly with Rapid Deployment Pack, you must apply the patch Rapid Deployment Pack discussed in article number 00000203 on the ProLiant Essentials Rapid Deployment Pack Knowledge Base website.

Verifying virtual domain groups

Insight Orchestration requires virtual domain groups, to create a virtual domain group or verify an existing group, see your Virtual Connect Enterprise Manager user documentation.

Creating Rapid Deployment Pack job folders

For each operating system that Insight Orchestration will use to deploy physical servers, create a top-level Rapid Deployment Pack job folders:
1. Create a top-level Rapid Deployment Pack job folder for each operating system, by right-clicking in the empty space of the Jobs panel and selecting New Folder from the list.
2. Rename the new folder created, for example, Boot From SAN Windows 2003 Enterprise.
3. Copy the Deploy ProLiant BL System Configuration (Boot From SAN) {LinuxPE} job from the Server Deployment ToolboxHardware ConfigurationSystem folder:
4. Paste the job into your new folder.
5. Modify the OS/PSP job in the created folder by right-clicking the job, and then selecting Properties in the menu. Do not modify the default OS/PSP job under the Server Deployment folder.
6. From the Job Properties windows, delete all items and associated reboot tasks preceding the Deploy System Configuration and Deploy Array Configuration until you see the Distribute Disk Image or Start Install task. Do not delete any task after the Distribute Disk Image or Start Install task..
7. To save the changes, click OK.
  After you complete this process, you can use the new folder for physical server deployment through Insight Orchestration.
8. To create a job folder for each required operating system, repeat this procedure.
Modify the existing Erase ProLiant ML/DL/BL Array Configuration {LinuxPE} job. HP recommends making a copy of the original Rapid Deployment Pack job before modifying it. In the Run this script section:
1. Modify Wipe Disk script (the first task):
  - Change export mode=quick to export mode=regular (or leave do not changed this attribute, if you prefer a quick disk scrubbing.)
  - Change export disknum=none to export disknum=all
2. To confirm the changes, click Next and Finish.
3. Delete the Erase Array Configuration task (the second task).
4. Modify the Power Control task (the last task), changing the power control method to Shut down (if available), and then to confirm the change, click Next and Finish.
5. Click OK.
To enable adding computers to the domain during provisioning, configure the Rapid Deployment Pack domain authorization using ToolsOptionsDomain Accounts.
Enclosures are discovered by HP SIM through the iLO IP address of the enclosure. Be sure to use the iLO credentials of the Onboard Administrator enclosure as the WBEM credentials.
In Insight Dynamics — VSE, create storage pool entries for automated SAN boot provisioning. You must know the storage array port WWN/LUN (World Wide number/Logical Unit number) number when creating the entries. If you do not know these settings, you can modify them after creating storage LUNs and zones. See “Creating SAN-backed storage”.
Manually configure storage LUN presentation and zoning using the virtual HBA WWN in VC profiles used when creating the storage pool entries. HP recommends creating a spreadsheet to track storage mapping.

During provisioning, the server blade should see a SAN volume when booting. If it does not, check your storage configuration settings.

Creating SAN-backed storage

Verify that the target enclosures have been successfully discovered by HP SIM.
Create a VC domain group which includes the target enclosures in VCEM.
Refresh Insight Dynamics — VSE, synchronizing it with VCEM. To refresh Insight Dynamics — VSE:
1. Using HP SIM, select, Logical ServersToolsRefresh.
  
  The Refresh Server Resource Information page appears.
2. Select Refresh of Virtual Connect Resources, and then click Refresh.
Click ModifyLogical Server Storage Pools.
Select the target domain group from the Virtual Connect Domain list.

If a domain group does not appear, verify that steps 1 through 3 were performed correctly.

To add or modify storage pool entries, see your HP Virtualization Manager documentation.

Insight Orchestration uses the comma-separated tags (optional) specified in the storage volume properties to match the logical disk tags provided in the template designer. If you specify logical disk tags in the template design, only volumes with the exact tags are allocated. If you do not provide logical disk tag information, the allocation process ignores the storage volume tags.

For non-Flex-FC (default) configurations, Insight Orchestration only requires adding the boot disk to the storage pool entry for the initial automated operating system provisioning. After provisioning the service infrastructure, you can add data disks to the same storage pool entry.

For Flex-FC configuration, see the Insight Orchestration white paper on Flex-FC located on the HP Insight Orchestration website.

You can save storage pool entries without entering the Volume Path Settings, however be sure to modify these entries, after you receive the LUN information from your SAN administrator. HP recommends using WWN based SAN switch zoning for c-Class blades with virtual connect.