HP Insight Orchestration 6.3 User Guide Abstract This document provides an overview of Insight Orchestration, which delivers advanced template-driven design, provisioning, and ongoing operations for multi-node, multi-tier infrastructure services.
© Copyright 2009 – 2011 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Introduction...............................................................................................6 Usage scenarios.......................................................................................................................6 Automated infrastructure design provisioning and management......................................................6 Insight Orchestration and the HP Insight Dynamics solution.............................................................
Configuring Insight Orchestration storage management...........................................................46 Insight Orchestration approach to storage reservation and allocation........................................48 Configuring Storage Provisioning Manager (SPM) in Virtualization Manager.............................48 4 Insight Orchestration provisioning and allocation..........................................54 Insight Orchestration lifecycle operations............................................
Copying keystore file after upgrading Operations Orchestration..........................................79 Specifying SMTP credentials and system properties.....................................................................80 7 Troubleshooting........................................................................................82 Verifying the CMS configuration...............................................................................................82 Synopsis......................................
1 Introduction HP Insight Orchestration extends HP Insight Dynamics to provide rapid provisioning and repurposing of infrastructure services from shared resource pools using a Self Service Portal.
A self service user selects an existing template and then requests infrastructure provisioning from it, against an assigned pool of resources. An administrator can approve or deny this request, and monitor its progress.
NOTE: In this release, you can view and assign only explicitly named users and groups that are included in the HPIO_* Windows groups (described in “Classes of Insight Orchestration users and groups” (page 10)). Users or subgroups within these named groups are not visible, nor can they be directly assigned to resources.
2 Installation Installing Insight Orchestration Insight Orchestration is installed through the HP Insight Software Installer. When using the installer, be sure to select all the required software and have the HP Insight Control and SMTP parameters available to use during installation. For more information, see HP Insight Software Installation and Configuration Guide on the Insight Software DVD. To locate the most current version of this document on the web, go to http://www.hp.com/go/insightdynamics/docs.
3 Configuration Configuring Insight Orchestration users in Windows The HP Insight Software Installer adds the user who installed the system to the HPIO_Administrators group. To add users to Insight Orchestration user groups, use your computer management or administrative tools. For example, in Windows Server 2003 click Start→Administrative Tools→Computer Management, and expand Users and Groups.
Configuring a federated CMS environment An Insight Orchestration federated CMS environment is one where multiple management servers cooperatively share the responsibility for managing a larger number of resources than can be managed by a single server.
2. Enable federated CMS in the hpio.properties file a. On the primary CMS, in Windows Explorer, navigate to C:\Program Files\HP\ Insight Orchestration\conf b. Edit hpio.properties c. Change the federated.io property to federated.io=true and save the file. 3. Configure the Systems Insight Manager federated CMS list on the primary CMS a. On the primary CMS, in Systems Insight Manager, select Options→Federated CMS Configuration… b. Click Add CMS… c.
3. Configure logical server management to increase memory allocation If a primary or a secondary CMS will manage more than 1000 nodes, increase the logical server management JVM heap size. a. On each CMS that is configured to manage more than 1000 nodes, in Windows Explorer, navigate to C:\Program Files\HP\Virtual Server Environment\conf\lsa b. Edit hp_lsa_service.conf c. Change wrapper.java.maxmemory=1024 to wrapper.java.maxmemory=2048, and save the file. 4.
NOTE: If the Insight Orchestration administrator password is subsequently changed using the Systems Insight Manager Reconfigure CMS Tools (mxreconfig), the changed Insight Orchestration administrator password is not reflected in Operations Orchestration Studio and database. Manually change the Operations Orchestration Studio and database passwords as follows. 1. Execute the following commands from the command prompt: mxpassword -m -x MxDBUserPassword= mxpassword -m -x io.db.
Verify that the HpioCmsIP property is set to the IP address or the Fully Qualified Domain Name (FQDN) of the CMS. If the IP address or FQDN is not set or is incorrect, double-click in the value area for HpioCmsIP and enter the correct IP address or FQDN. 5. (Optional) Configure email addresses. During the Insight Software installation process, you are only able to specify one From and one To email address for all email messages.
Configuring deployment servers Insight Orchestration supports the following server deployment platforms for provisioning: • Insight Control server deployment (physical provisioning) • Ignite-UX (physical and virtual provisioning) • HP Server Automation (physical and virtual provisioning) Discovering deployment servers Insight Orchestration provisioning requires software deployment servers to be discovered or rediscovered. To discover a deployment server in Systems Insight Manager: 1.
folder highlighted in the following screenshot, enter 01 in front of the 1st job, Deploy ProLiant System Configuration (BL BFS); enter 02 in front of the 2nd job, DeployRHEL 5.4 x64 (EN-US); enter 03 in front of the 3rd job, Install HP Management Agents for RHEL 5 x64. For Direct-Attached Storage (DAS) OS deployment, do not include the Deploy ProLiant System Configuration (BL BFS) job in the job folder. 5. 6. To create a job folder for each required operating system, repeat this procedure.
a. 18 Configuration Right-click the Erase ProLiant Hardware job under the HP Deployment Toolbox→ Hardware Configuration folder, and then select Copy from the menu.
b. 2. Right-click the HP Deployment Toolbox→Hardware Configuration folder, and then select Paste from the menu. Delete tasks 1, 3, 4, and 6 from the default Erase job: a. Double-click the Erase ProLiant Hardware job. The Job Properties window appears.
b. 3. 20 In the Job Properties window, keep the Ctrl key pressed while selecting tasks 1, 3, 4, and 6 (the tasks will highlight as shown below), and then click Delete.
a. Select the Power Control task, and then click Modify. b. Select the Shut down (if available) option, and then click Finish.
Configuration
c. In the Job Properties window, make sure that the modified Erase ProLiant Hardware job displays, then click OK to close the window. Configuring Ignite-UX Insight Orchestration supports Ignite-UX version C.7.11.439 (HP-UX 11.31 1009) or later for HP-UX 11iv3 deployment. (HP-UX 11iv3 0709 or later is required for Integrity VM.) The Ignite server must have NFS configured as well as the tftp and bootps services enabled in /etc/inetd.conf. a.
NOTE: Only HP-UX release 11.31 1003 or greater can be installed on the following Integrity blades: • BL860c i2 • BL870c i2 • BL890 • BL890c i2 The complete list of documentation for Ignite-UX is available at http://hp.com/go/ignite-ux. Integrity VM Guest Kit installation The Integrity VM Guest Kit must be set up on the Ignite-UX server in order to properly ignite an HP-UX guest.
Setting up virtual machine networks Network names are correlated across hypervisor and Virtual Connect technologies to allow an infrastructure service to be provisioned with logical servers of different types configured on the same network. Employing this capability requires the eight-character limit imposed by Integrity VM to be extended to the other hypervisor and VC configurations in the managed environment.
4. 5. 6. Click Add. In the Name field, enter the name of the network. Under Connection Type, select the network interface from the External drop-down list. NOTE: If you intend to use this network on the management system, select Allow management operation system to share the network adapter. 7. Select OK. Using VLAN tags in a Hyper-V VM network Insight Orchestration supports VLAN tagging with Hyper-V VM guests.
CAUTION: For any given virtual switch, all VMs must use either a tagged network or a non-tagged network across all hosts. Mixing tagged and non-tagged Hyper-V VMs on the same virtual network will result in network failures. HP recommends that you maintain a homogenous network environment among cooperating Hyper-V hosts. To achieve this, for all uses of a named virtual switch, use a tagged network on all hosts or use an untagged network on all hosts. 3.
NOTE: Template-based provisioning is not available for Integrity VM. Insight Orchestration utilizes a Hyper-V virtual machine as the source material for a VMM template without any additional steps. However, to provision recoverable logical servers, deploy your Hyper-V virtual machine host in a Windows cluster. For more information, see your Windows documentation. The following constraints apply when using VMM templates.
• If a Storage Volume Name is specified in the Insight Orchestration template, all disks for all VMs in the server group will be allocated to the datastore that matches the Storage Volume Name. • If there are no shared disks, no Storage Volume Names, and no linked clones, then each VM in the server group and its disks may be allocated to different hosts on different datastores, or to the same host and different datastores, based on free space.
• Contents of the Insight Orchestration sysprep.inf file, located at ..\Program Files\ HP\Insight Orchestration\conf\sysprep\Sysprep_sample.inf. An Insight Orchestration administrator can edit sysprep files based on the sample file to specify additional customizations for Windows virtual machines. To enable customization on: • VMware vCenter 4.
Creating SAN-backed storage 1. 2. 3. Verify that the target enclosures have been successfully discovered by Systems Insight Manager. Create a Virtual Connect domain group that includes the target enclosures in VCEM. Refresh HP Insight Dynamics, synchronizing it with VCEM. To refresh HP Insight Dynamics: a. Using Systems Insight Manager, select, Tools→Logical Servers→Refresh. The Refresh Server Resource Information page appears. b. 4.
5. Select the target Virtual Connect portability group from the Portability Group list. To add or modify storage pool entries, see HP Insight Virtualization Manager Software with Logical Server Management User Guide at HP Insight Dynamics Information Library. Insight Orchestration uses the tags selected from the Tag List in the Storage Pool Entry to match the logical disk tags provided in the Insight Orchestration Designer.
Insight Orchestration fully supports the Flex-FC configuration and defaults to that configuration for storage. Insight Orchestration requires separating the boot disk storage pool entry, private data disk storage pool entry, and shared data disk storage pool entry. You can save storage pool entries without entering the Volume & Path Definition. However, be sure to modify these entries after you receive the LUN information from your SAN administrator.
A timeout occurs if any individual logical server provisioning takes longer than the time specified as measured from when the actual provisioning starts, not from when the create request started. Configuring Insight Orchestration resources in Systems Insight Manager After installing Insight Orchestration, a member of the HPIO_Administrators Windows group can log in to Insight Orchestration through Systems Insight Manager. HPIO_Administrators can then set up resources to allow provisioning.
You can use only configured networks for Insight Orchestration provisioning. HP Insight Dynamics provides network information to Insight Orchestration. For each network you want to use with Insight Orchestration, you must add DHCP and/or static address ranges. If your networks do not correctly appear, see “Troubleshooting” (page 82). 2. Select a network, and then click View/Edit. On the Edit Networks page, you can add information about the network and which IP resources are available.
NOTE: Depending on your configuration, not all fields are required. The user interface helps guide you through the process. The left area of the screen also has DNS and Windows Settings tabs. 3. On the DNS tab, enter the DNS Domain (required), DNS Servers, and DNS Search Suffixes (optional.) The Windows Settings tab enables you to enter optional Windows information such as domain and WINS information. 4.
5. When you are finished setting up a network, click Save. The network is now ready to use with Insight Orchestration. Verifying Insight Orchestration users and groups The Users tab contains a list of all users and groups authorized to use Insight Orchestration.
2. In New pool name, enter a descriptive name. You can select servers from any pool. When you first configure Insight Orchestration, however, only the Unassigned pool displays resources. 3. 38 To select a server, select it in the list on the left, and then click the >> button. You will see the server move to the list on the right.
NOTE: You cannot move unlicensed server blades or virtual machine hosts from the Unassigned pool. You can move resources to a pool only after the resource is licensed for use by Insight Orchestration. For more information, see “Licensing Insight Orchestration” (page 15). 4. After selecting the resources for the pool, click Save. The pool now appears on the Servers tab. Selecting the pool displays the allocated resources. 5.
6. Select the user in the Unassigned Users/Groups list and then click >>. Repeat this process for each user you want to assign to the pool. Click Save. The Servers page reappears. To verify that the users are assigned to the pool, select the pool. A list of the assigned users and groups appears at the bottom of the screen.
NOTE: The Operations Orchestration workflow authoring tool (OO Studio) may be used to extend the functionality of the reference workflow to support additional management processors as required. Configuring ESA password in Virtualization Manager Modify ..\Program Files\HP\Virtual Server Environment\conf\esa.properties to include the Operations Orchestration 'Admin' password: esa.oo.admin.password= After making the changes to the esa.
The “inventoryList.xml” file is read from the file system and its contents are then sent directly to the ESA web service. The ESA web service processes the returned XML document and hands it back to Logical Server Management (LSM), which functions as the upper level inventory manager. LSM will then make a second workflow call for each server. ..\Program Files\HP\Insight Orchestration\esa_extensions\server\ serverInfo.xml The file serverInfo.
1 68 1 nic0 00:1E:0B:CC:61:B0 vlan84-dhcp-pxe-sa true ProLiant DL380 G5
For each server in the “inventoryList.xml” file, the “Get Server Info” workflow is invoked. The workflow extracts the detailed server definition from “serverInfo.xml”, and then uses the server’s management processor to determine the current power state. The server management processor operations are invoked through additional workflows. The persisted power state is updated if required and the resulting server record is returned as an XML document to the ESA web service.
makes use of the “serverInfo.xml” record to determine the server’s model so that the correct power operation is performed. The same call back pattern is used. At the completion of the workflow, the terminal state of the operation and status information is returned to the ESA web service. Configure management credentials for power control An additional step is required to configure the management credentials for power control. The reference implementation ships with built-in system accounts.
a. b. Edit ..\Program Files\HP\Insight Orchestration\conf\ blade_models.properties file. Add the new server model. The server model string is the string entered in the serverInfo.xml file. See the following example that adds HP xw8400 Workstation.
Manual storage provisioning means that either no storage has been pre-provisioned or that only a subset of the storage has been pre-provisioned for a logical server. At the service creation time, Insight Orchestration attempts to locate and allocate the storage resources. When no storage resources are found, the overall request pauses for the administrator to manually provision the required storage.
For more information about SPM, see HP Storage Provisioning Manager (SPM) User Guide and the HP Logical Server Management Best Practices white paper at HP Insight Dynamics Information Library. Insight Orchestration approach to storage reservation and allocation A key step in the service creation process involves both a reservation and allocation phase for all resources required by the service template. Following are the storage reservation and allocation steps.
The concept of unmanaged arrays is included in SPM. Any pre-presented SAN volume can be manually entered into the SPM interface, creating a catalog entry which can be matched against a Storage Pool Entry to provide logical server storage suitable for use by Insight Orchestration. A managed array enables SPM to perform certain storage operations such as gathering property information, changing the hostmode, or performing LUN masking. Managed arrays can be used for “Dynamic” SAN volume allocation automation.
The system then communicates with the Command View server through SMI-S and enumerates the arrays that are visible to the Command View server. You then select one or more arrays for import. Once the array has been imported, view and select the SAN volumes that are visible on the array and select the volume(s) to be included in the catalog. The following screens show this progression. Select the array(s) to be imported. For each array, select the volume(s) to be imported.
The Insight Orchestration “Static” SAN volume automation approach involves SAN volumes that are pre-masked to one more initiator WWNs within the SAN, and zoning is also pre-configured. These pre-created volumes are then imported into SPM and made available. SPM has a pre-populated catalog that is used to fulfill storage requests. SPM also provides support for “Dynamic” SAN volume automation.
In order to use the SPM catalog, select the appropriate operating system, boot volume, size, and RAID level, then select Show Candidates. The result in the Candidates drop-down menu is a list of SAN volumes known to SPM which meet the specified criteria.
After selecting the desired entry, the storage pool entry can be saved and can then be used for future service provisioning requests. If the SPM catalog entry authorizes it, Insight Orchestration is able to dynamically adjust the LUN masking and if necessary the host mode for the storage pool entry.
4 Insight Orchestration provisioning and allocation Insight Orchestration lifecycle operations Insight Orchestration covers the IT lifecycle, from the initial design of system configurations to the ultimate repurposing of assets. It enables IT resource request to be handled in a systemic manner than leverages standard configurations, self service provisioning tools, and automated approval processes.
• Allocates the boot disk (physical and virtual) • Obtains approval • Creates virtual machine or blade server profile • Deploys the operating system and other software to boot disk • Configures the virtual hardware • Customizes the operating system (networking, sysprep) • Allocates the physical data disks • Provisions the servers for data disks • Boots the servers • Executes custom actions • Sends notifications After successfully completing a Create Service operation, the provisioned I
• Allocates IP addresses • Allocates the boot disk (physical and virtual) • Obtains approval • Creates virtual machine or blade server profile • Deploys the operating system and other software to boot disk • Configures the virtual hardware • Customizes the operating system (networking, sysprep) • Allocates the physical data disks • Provisions the servers for data disks • Boots the servers • Executes custom actions • Sends notifications After successfully completing the operation, Ins
Deactivate servers in group operation The Deactivate servers in group operation places the selected servers in standby and removes them from service. During this operation, Insight Orchestration: • Validates the request • Deallocates the servers (server blades) • Powers off the servers • Executes custom actions • Sends notifications After successfully completing the operation, Insight Orchestration deallocates the physical server blades, making them available for other uses.
After successfully completing a Change Lease Period operation, Insight Orchestration modifies the lease period for the infrastructure and updates the allocation of each resource for the new lease period. If a resource is not available or an administrator rejects the request, the Change Lease Period operation fails. When a lease on an infrastructure service expires, Insight Orchestration will deactivate the service.
A service template typically assigns a server deployment or virtual machine software to a group of servers, however it is possible (though not typical) to define a service template without assigning server deployment or virtual machine software to a group of servers. In this case, the Create Service and Add servers to group operations pause to allow the Insight Orchestration administrator to deploy the operating system manually.
Automated allocation Allocation is the process of finding the resources to match to the logical objects described in a template. An Insight Orchestration template is the logical specification of an infrastructure service using template components known as logical objects, enabling the user to provision an infrastructure service from resources. In Insight Orchestration templates, logical objects are specified either by attribute value or by name.
from SAN support in Insight Orchestration requires that the Deploy ProLiant System Configuration (BL BFS) server deployment job (from HP Deployment Toolbox\Hardware Configuration folder) be placed in the job folder. After having provisioned HP-UX to an Integrity blade and after the newly provisioned server is discovered by Systems Insight Manager, the new Systems Insight Manager node needs to be authorized to run the CMS tools as follows: 1.
pre-defined entry points (or hooks), enabled state, and the corresponding rule files. A sample entry in the policy.xml file is shown in the following figure. • The name PhysicalServerPolicyCheck.applyFitting in the figure indicates the entry point or hook for the physical server fitting process. • The enabled flag, enables or disables the rule-based fitting for this hook. • The provides the list of rule files to apply during the fitting process.
rule "INIT" salience 1000 when pVO : PolicyExecutionVO(); then insert(pVO.getAllocationEntry().getServiceEntity()); insert(pVO.getResultMap()); insert(pVO.
• EsxDiskPolicyCheck.applyFitting • HypervDiskPolicyCheck.applyFitting • DasDiskPolicyCheck.applyFitting • SoftwarePolicyCheck.applyFitting Writing a new rule file Open a new drl file in a text editor, add the different sections of a rule file (as shown in “Rule file” (page 62)), and add the new rule logic. • Package—The name of the package and is always com.hp.hpio.controller.policy. • Import—Declares the use of any other Java classes required to write the rule business logic.
LogicalSubnet logicalSubnet, Subnet subnet, PolicyExecutionVO pVO) { // Custom message. pVO.doesNotMatch(subnet, HPIOMessage.get(HPIOBundleKey.ALLOCATION_CRITERIA_CUSTOM, “Failure message”)); boolean match=true; /* -------------- CUSTOM LOGIC ----------------------*/ /* -------------- CUSTOM LOGIC ----------------------*/ return match; } Deploying rules 1. 2. 3. Make sure that the rule file is valid (using the iopolicyassist tool). Copy the validated rule file to /conf/policy/ directory.
Fixed cost for templates and services Insight Orchestration allows a template architect to add a fixed cost to a template, in addition to server, network, and storage costs. Examples of fixed costs are power or setup costs. Enter a fixed cost in Designer by clicking the Cost tab in a template, and entering a value in the Fixed Cost text box.
Assigning cost and billing information 67
Global cost unit for all templates You can convert the global cost unit for a template by right clicking in a blank area of the template design area and selecting Convert Template to use Global Cost Units. This menu selection is enabled only if the cost unit for the template is different from the global cost unit defined by the cost.units.global.value property in the hpio.properties file. This difference can occur if: • you import a template with a different cost unit than the cost unit set in hpio.
5 Using Insight Orchestration applications Overview Insight Orchestration applications support the roles of architect, administrator, and user. • Designer enables an architect to plan and design multi-server, multi-tier infrastructures using a drag-and-drop interface. • Console enables an administrator to deploy, manage and monitor the overall behavior of Insight Orchestration and its users, templates, services and resources.
• Have appropriate authorizations to use HP Insight Orchestration on the CMS. • Be a member of the HPIO_Architects or HPIO_Administrators group on a Windows system. You can access Designer from the desktop or a browser. To access Designer from the desktop, do the following: 1. Open a web browser on the CMS where Systems Insight Manager is installed. 2. From the desktop, double-click the Insight Orchestration Designer icon.
resources and business needs as requests are fulfilled or denied. For example, as an administrator, you: • View status, progress, and details of completed and executing requests • View available resources • Approve or reject requests • Perform pool management To accomplish these tasks as an administrator, you: • Create resource pools for hosting services based on standardized templates and the business forecast.
Interface overview The Insight Orchestration console displays the following tabs: • Home Displays an overview of Insight Orchestration operations providing statistics, resource usage, and links to access Insight Orchestration tasks. • Templates Displays all the available templates and enables you to view the details of a template, edit a template, create a new template, delete a template, submit a template for provisioning, and assign users to a template.
Displays a list of available server resources, and enables you to view server details and manage server resources, create new server pools, and manage the users of a server pool. • Storage Displays a list of available storage resources, and enables you to view storage details and manage storage resources. • Users Displays a list of current users and groups, the resources assigned to each user and group, and role. • Networks Displays the available networks and enables you to configure these networks.
For Internet Explorer (IE) version 7 or later, telnet console must be enabled by editing the registry on the client. Configuration Enabling VM console In order to enable VM console access to deployed VMs in the Insight Orchestration console and Self Service Portal, complete the following steps to copy the VMware MKS browser plug-ins from an ESX 3.5 update 3 server: 1. On the CMS at a command prompt, type cd /conf/console/mks 2.
You can access Self Service Portal from the desktop or a browser. To access Self Service Portal from the desktop, do the following: 1. Open a web browser on the CMS where Systems Insight Manager is installed. 2. From the desktop, double-click the Insight Orchestration Self Service Portal icon. To access Self Service Portal using a browser, navigate to https://localhost:51443/hpio/portal/.
• My Services Displays a list of your infrastructure services and enables you to view details and request changes to the service. • My Pools Displays a list of the resource pools available to you to use in service provisioning requests. • My History Displays a list of system and important event notices, including the date and time of the event, the result, and description of the event result.
6 Using Operations Orchestration Overview The HP Operations Orchestration Studio enables you to create custom workflow processes and attach them to infrastructure service templates. This chapter provides a general overview of Operations Orchestration and some examples. Insight Orchestration defines integration points for Operations Orchestration workflows that run each time a specific operation is invoked, regardless of the template or infrastructure service involved in the operation.
NOTE: The correct version of Operations Orchestration Studio is installed on the CMS based on the OS type (32-bit or 64-bit) during the installation of Insight Orchestration. However, the gear icon in the Workflows tab allows you to download only the 32-bit version of Operations Orchestration Studio. If you have a 64-bit CMS, install the 64-bit version of Operations Orchestration Studio available on the Insight Software DVD #2, in the /hpio folder. 5.
• In the Host Name or IP Address field, enter the IP address of the Operations Orchestration CMS machine from which you downloaded Operations Orchestration Studio. • In the HTTP Port Number (usually 80 or 8080) field, change the value to 16080. • In the HTTPS Port Number (usually 443 or 8443) field, change the value to 16443. Configuring Operations Orchestration Studio on a remote computer To configure Operations Orchestration Studio on a remote computer: 1.
Specifying SMTP credentials and system properties Operations Orchestration Studio requires an SMTP server. Insight Orchestration uses Operations Orchestration during the execution of Insight Orchestration requests notifying users about the progress of Insight Orchestration processes including approval, manual operating system deployment, manual storage provisioning, disk scrubbing, storage removal and notifications.
Approval emails sent to the Insight Orchestration administrator includes a URL to be followed for approval. The URL can be followed only once. However, if you do not want an Operations Orchestration workflow to run when approval is required, modify the hpio.properties file and change oo.service.approval.action.enabled = true to oo.service.approval.action.enabled = false. To change the contents of the approval email, for example, to remove the URL, modify the “Approval/Email/Send Approval Email” workflow.
7 Troubleshooting Verifying the CMS configuration Insight Orchestration utilizes the vseassist tool and the Systems Insight Manager Diagnose menu to help you identify and resolve any CMS configuration issues. The Check CMS Configuration task performs configuration checks on the CMS. To run this task, from the Systems Insight Manager menu, select Diagnose→Troubleshoot Insight Dynamics→Check CMS Configuration.
Assign a valid user or user group to the HPIO_Users group. (...
• WARN—A configuration problem was found. The problem will not necessarily prevent correct operation, but it may limit or restrict operation of some features. • N/A—Not Applicable: the check does not apply to this type of system. IOAssist execution timeout The default timeout value for each IOAssist check is two minutes.
failure status. Failure: Exception creating connection to: 15.2.50.138; nested exception is: java.net.NoRouteToHostException: No route to host: connect. Or: Task for logical server has failed. Logical server job completed with a failure status.f Failure: no such object in table. • Manual Storage Provisioning email states that more data LUNs than are required should be added. • Cannot add servers to an existing service using a Static IP address.
Failure message Task for logical server …. Failure: At least one OS or software deployment has failed. Check the deployment service to diagnose the details. Possible cause • Problem with a LUN allocated to server or firmware issue on server • Insight Control server deployment Erase ProLiant ML/DL/BL Array Configuration {LinuxPE} job has not been modified for Insight Orchestration. Action To verify the LUN and/or server firmware: 1.
Failure message Task for logical server has failed. Job has exceeded its timeout value of minutes. Marking the job as failed. Possible cause • Server blade firmware. • Errors in storage presentation, multipath or zoning configuration, or failed components. • Timeout value for create logical server request is too short Additional possible causes if using the Insight Control deployment server.
Failure message • Could not find server with serial number . • Task for logical server has failed. Logical server job completed with a failure status. Failure: Exception creating connection to: 15.2.50.138; nested exception is: java.net.NoRouteToHostException: No route to host: connect. • Task for logical server has failed. Logical server job completed with a failure status. Failure: no such object in table.
Issue A provisioning request remains paused during a manual storage allocation (approximately 5%), and a storage pool entry cannot be created in Insight Dynamics because the VC Domain Group is not listed on the Storage Pools screen. Possible cause VCDG is using factory default MAC/WWN settings. HP Insight Dynamics and Insight Orchestration do not support a VCDG with factory default MAC/WWN settings.
following steps can be followed to disable the installation of Insight Management WBEM providers. Insight Management SNMP agents continue to provide management capabilities when WBEM providers are not installed. 1. Edit the install.cmd file, found under \ rdp\deployment server\hpfeatures\hpagents-ws\components folder, and remove the following two lines. • call :installsc wbem%PROCESSOR_ARCHITECTURE% • if %cpresult% geq 1 set /a cpresults=cpresults+1 2. Save the file.
Issue Server reservation and allocation fail with the following messages, even though servers exist in the assigned pool that will satisfy the template requirements. • Reservation failed for logical server . Unable to find a physical server with the following requirements: There are no valid available targets to provision the service. Check if the targets in the selected pools are in maintenance. • Unable to allocate servers and networks in the same Virtual Connect Domain Group.
• Valid users are no longer associated with templates. • Provisioning a virtual machine failed with a VM must be powered off for customization error message. • Provisioned VMs fail due to improper VM host hardware configuration. • VM host server blade is not returned to server pool as Unused when VM host service is deleted. • Task for logical server has failed. Failure: Service console load average on the source server is greater than the threshold value.
For ESX: 1. Use the vCenter client to browse the ESX server's datastore. 2. Navigate to the directory and delete the offending directory and directory contents. For Hyper-V: 1. Connect to the Hyper-V Hypervisor. 2. Delete the VM from the Hyper-V Manager. 3. Navigate to the directory and delete the offending directory and directory contents. If Server Automation (SA) deployment was used to provision the VMs: 1. Remove the ESX and/or Hyper-V VMs using the preceding steps. 2. Connect to the SA server. 3.
The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click OK to restart the computer, and then restart the installation. Possible cause • The environment is not completely configured. • The virtual machine used in the Insight Control virtual machine management template was not powered off properly. • The vCenter or vSphere is not configured properly for successful customization.
Issue When a template is created and a virtual data disk is named using invalid or double byte characters, the request is not submitted, and the following error message is displayed: Invalid logical disk name for disk . A logical disk name may contain only the following characters: A-Z, a-z, 0-9, '_', '-' and ' '. Other characters are not allowed. Physical data disks and boot disks can contain localized names.
Issue Provisioning a virtual machine failed with a VM must be powered off for customization error message. Possible cause The Insight Control virtual machine management template that is being used was created when the virtual machine was in a suspended state. Action Provisioning will fail during customization with an error message if the virtual machine management template is created when the virtual machine is in a suspended state and then used in Insight Orchestration.
2. Unregister the VM host: ..\Program Files\HP\Insight Control virtual machine management\clientapi\bin>cli unregisterAgent -host 3. Retrieve the list of IP addresses registered as VM hosts: ..\Program Files\HP\Insight Control virtual machine management\clientapi\bin>cli getHostIds 4. Verify that the VM host IP address is no longer listed. Issue Storage Pool Entries defined in Insight Dynamics may not be shown under the Storage page in Insight Orchestration console.
NOTE: If you use the mxnode command, you must also enter the root/ for the provisioned server into the global credentials for Systems Insight Manager (Options→Security→Credential→Global Credentials).
for this issue, and the problem will surface as a server reservation failure message. The issue applies only to virtual logical servers. • From the Insight Dynamics logical server perspective, clicking on the Manage this logical server with HP Insight Orchestration icon displays the following message: Could not find a provisioned infrastructure service with the specified logical server in Insight Orchestration.
Deactivate, activate, power off, or power on operations Troubleshooting items addressed in this section: • Messages displayed when a paused boot disk deployment is cancelled by an administrator.
• Importing a template XML file that was created in a later release of IO into a previous release and backward compatibility Failure issue Insight Orchestration console in Systems Insight Manager displays: “ The HP Insight Orchestration tool cannot be displayed. Problem: Failed to login to the Insight Orchestration service from Systems Insight Manager. ” Possible cause The Windows user logging in is not a member of the HPIO_Administrators group.
Issue Request details displays allocated when a reservation process finishes. Possible cause Resources are reserved Action Insight Orchestration displays an “allocated” message when resources are reserved for a provisioning request. If this message appears for a scheduled provisioning operation, the resources are only reserved for the future lease period.
Issue The memory resources allocated to a virtual machine host are not available after using the Deactivate servers operation. Possible cause When virtual infrastructures or individual servers are deactivated, Insight Orchestration does not recognize the memory previously allocated to the logical servers as available to allocate to other virtual machines. Action — Issue A step in the Request Details is shown as having failed.
• Create Request fails for my Published template. Issue My Linux server does not list a recently added data disk. Possible cause The server was not rebooted. Action When adding a new data disk to an existing service, if the servers are physical Linux servers or the data disks are added manually (for example, Multi-initiator NPIV is not used), you must reboot the Linux server before the disks are available. Issue Entering a hostname in the network WINS setting causes a Windows customization to fail.
Designer Troubleshooting items addressed in this section: • After period of inactivity, the emplate appears available to edit, until saving the template is attempted. • Special characters do not validate in Cost units field in Designer. • A virtual IP address can be assigned only to the first network connected to the server group. • Troubleshooting communication failures. • Fatal error occurred while initializing the Designer.
Issue Designer error dialog message: A fatal error occurred while initializing the Designer. Please make sure the Insight Orchestration service is running and try again. Possible cause Occurs when launching Designer from the Console (using the Template tab Edit buttons). Action Launch Designer using a browser at https://:51443/hpio/designer and open the desired template. Issue With IE6, launching Designer from Insight Orchestration console can cause sporadic Designer interface failures.
• Reservation failed for logical network . The IP address(es) xx.xx.xx.xxx must be included in the static IP address range set for the network. • Template access restrictions for users and architects. • hpio.properties changes are not requiring Insight Orchestration service restart. • Integrity firmware blade corruption during provisioning of the following Integrity blades: BL870c, BL870c i2, BL890c, or BL860c i2.
Issue Insight Orchestration email messages such as approval and notification) are not sent. Possible cause • SMTP configuration parameters are not correct. • SMTP credentials are not correct. • SMTP server is not responding. • CMS is not able to communicate with SMTP server. Action • Make sure that the SMTP configuration parameters and credentials are correct. See “Specifying SMTP credentials and system properties” (page 80). • Check CMS and SMTP server connectivity.
keeps logging an error that Insight Control virtual machine management is not configured to communicate with vCenter. Action • Register the credentials with Insight Control virtual machine management using the Systems Insight Manager Options→VMware® vCenter Settings menu. • Verify that the “VMware vCenter Management Webservices” service is started.
Designer Workflows tab allows you to download only the 32-bit version of Operations Orchestration Studio. Possible cause You attempted to install the 32-bit version of Operations Orchestration Studio on a 64-bit CMS. Action If you have a 64-bit CMS, install the 64-bit version of Operations Orchestration Studio available on the Insight Software DVD #2, in the /hpio folder. Issue Cannot access the VMware console using Firefox.
The above are hpio.properties entries that Self Service Portal, Designer and the IO console in SIM read directly. Issue Integrity firmware blade corruption during provisioning of the following Integrity blades: BL870c, BL870c i2, BL890c, or BL860c i2. Possible cause Insight Orchestration issues power cycle operations during provisioning and deprovisioning when deploying Integrity blades. If a power cycle operation happens before the boot process completes, the blade HBA firmware could become corrupted.
Issue Not all virtual resources are displayed under the Servers tab. Possible cause Five minutes after clicking the refresh button, the Servers tab still shows no virtual hosts. (You can see a TimeoutException from the getVMHostServerPools call in the stack trace within the hpio-controller.log file on the CMS).
The server profile and boot disk are preserved, enabling an administrator to determine the cause of the failure and perform any required maintenance before returning the server blade to a user pool. Manual clean-up of the failed server blade depends on the deployment server used to provision it. For Insight Control server deployment: 1. Power on the server blade. You might need to cycle the power if the server blade is stuck. 2. 3. 4.
4. Move the server blade out of the Insight Orchestration Maintenance pool. a. In the Insight Orchestration console (accessed from Systems Insight Manager), select the original server blade pool and click Modify. b. Move the failed server from the Insight Orchestration Maintenance Pool back to your server blade pool and then save the pool. Manual clean-up process (virtual) When Insight Orchestration deploys a virtual machine, it creates a directory structure into which the virtual machine is provisioned.
In this example, the storage pool entry name is “e5_win_BD_05”. The figure highlights the SAN which is being connected to, as well as the target, and the initiator WWNs. 2. Go to the storage fabric and create the zone. In this example, a switch which exists in “san3” above is connected. The zone should have the same name as the storage pool entry, as is shown by the highlighted entry.
3. Go to the disk array management interface (in this case CommandView managing an EVA) and create a host entry and present the LUN. In the first figure, the host entry that is created on the EVA uses the same name as the storage pool entry. The host entry is assigned the initiator WWN identified in the storage pool entry: 4.
In this example, only a single vdisk is required by the storage pool entry. The names are kept the same across the storage pool entry, the FC zone, the host entry on the array, and the vdisk. This approach supports a strong correlation of the resources in the different tools. It is also possible to define a storage pool entry with multiple LUNs. In this case, the naming of the vdisk could follow a pattern of a common prefix (for example, e10_vc_w2k_1, 2, 3, 4, and so on).
1. To correct this issue, press the CTRL+Q keys to launch the HBA Fast!UTIL utility. After you enter the utility, the following screen appears: 2. On this screen, press the Enter key. Pressing Enter corrects NVRAM and generates a new checksum. During this process and server reboot, Virtual Connect continues to supply the HBA configuration parameters preventing data loss. After pressing Enter the following screen appears, indicating that the NVRAM has been corrected.
3. Press the ESC key to exit the utility. The following screen appears: 4. Press the Enter key to reboot the system. When the system reboots, all the HBA configuration parameters are resupplied by Virtual Connect and your server returns to normal operation. Increasing VMware Service console memory and CPU shares The memory and CPU shares that are allocated to the VMware Service console may be increased to obtain better performance on the VM host.
NOTE: For troubleshooting purposes, VMware recommends that you increase the service console RAM to 800MB. g. Click OK. The changes do not take effect until the ESX host is rebooted. For more information on rebooting an ESX host, see the following VMware KB article: http:// kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC& externalId=1003501. 2. Increase the number of CPU shares assigned to the ESX 3.X or ESX 4.X Service console: a.
j. Click OK to apply the values. NOTE: Increasing the reservation value for console may affect the available CPU cycles for the virtual machines on the host. Resources not displaying - Increasing timeouts Issue One or more types of Insight Orchestration resources (for example, virtual networks) are not displayed in Insight Orchestration's user interfaces.
• timeout.get.deployment.services For example, to increase the fetch subnets timeoutfrom the default value of 5 minutes to 15 minutes, modify the line: timeout.get.subnets = 5 to be: timeout.get.subnets = 15 Editing ESA flows when OO is not installed in the default path If Insight Orchestration is installed in other than the default path (..\Program Files\HP\ Insight Orchestration), the workflows operations must be edited to reference the path where IO is installed.
5. 6. 7. Double-click the “Readfile” operation. In the Inspector grid, click the arrow button on the right side and edit the path displayed in the Constant Value field to match the actual path. Click Save to save the path, then check in and save the flow with the updated information.
8 Support and other resources Information to collect before contacting HP Be sure to have the following information available before you call contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support: • In the United States, see the Customer Service / Contact
HP authorized resellers For the name of the nearest HP authorized reseller, see the following sources: • In the United States, see the HP U.S. service locator web site: http://www.hp.com/service_locator • In other locations, see the Contact HP worldwide web site: http://welcome.hp.com/country/us/en/wwcontact.html Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, send a message to: docsfeedback@hp.
Related information Documentation and support The latest versions of manuals and white papers for HP Insight Dynamics and related products can be downloaded from the HP Web. Documents for HP Insight Dynamics software can be found at http://www.hp.com/go/insightdynamics/docs. For more information about HP Insight Orchestration and related products and solutions, visit the following HP websites: • HP Insight Orchestration website at http://www.hp.
Glossary administrator A user who manages users, resource pools, and self service requests through HP Insight Orchestration console. allocation A request is assigned server, storage, and network resources based on the criteria defined in the template, resource pools assigned to the user, and the current reservations or allocations of resources completed by Insight Orchestration. approvals A permission given to a user-generated request by an administrator.
HP Systems Insight Manager An HP systems and resources monitoring and management product. IE See Internet Explorer. infrastructure service A running configuration of infrastructure resources that is designed to run a business application such as a multi-tier web application. It is also referred to as a service or service instance. Infrastructure resources include server blades, virtual machines, SAN disks, networks, and IP addresses.
• Delete a service • Deactivate a server • Activate a server • Update a service to add servers • Update a service to add storage • Change the lease period resource pool A group of physical and virtual resources managed by HP Insight Dynamics. An administrator controls resource utilization by allowing users access to resource pools. RSCN See Registered State Change Notification. Self Service Portal A web application that enables you to create infrastructure services from published templates.
WINS See Windows Internet Name Service. workflow Defines a set of additional actions that execute customer-specific IT tasks. Workflows are designed using Operations Orchestration, the workflow designer embedded in Insight Orchestration. You can use workflows to define integration with your IT processes, including approvals, manual operating system deployment, manual storage provisioning, and sending notifications.
A HP Operations Orchestration communication security This appendix describes the security of the interaction between HP Insight Orchestration and HP Operations Orchestration. HP Insight Orchestration integrates with HP Operations Orchestration. Operations Orchestration provides customizable workflows that can be called at various points during the life of an infrastructure service.
• User Token – The security token to be used in calls back to Insight Orchestration. • Date – Date and time at which the flow was triggered by Insight Orchestration. NOTE: These parameters are required in the workflow definition even if the parameters are not used within the workflow.
• Service Recovery • Service Fail Action Service actions Service actions are the stages of infrastructure service that may invoke an Operations Orchestration workflow.
Index A access, 69 accessing Designer, 69 Insight Orchestration console, 71 Operations Orchestration, 77 Self Service Portal, 74 add disks, 56 add servers, 55 administrator, 8 allocation, 58, 59, 60 allocation rules, 61 approval, 58 architect, 8 automated provisioning, 60 B benefits, 6 boot disk, 58 browser access, 69 Insight Orchestration console, 71 Self Service Portal, 74 C change lease, 57 checksum error correcting, 117 CMS configuration, 82 configuration customization, 29 ESX, 24 federated CMS, 11 ne
HPIO_Architects, 10 HPIO_Users, 10 I Insight Control, 6 Insight Control server deployment job folders, 17 Insight Control virtual machine management, 6 Insight Orchestration benefits, 6 features, 6 Insight Orchestration applications, 69 Insight Orchestration console access, 71 installation, 9 J job folders, 16, 17 L SMTP values, 80 overview administrator, 8 allocation, 60 architect, 8 automation, 6 console, 70 console interface, 72 designing, 6 integration, 7 lifecycle operations, 54 operation, 7 produc
storage pool entries configuration, 114 support, 126 system properties, 13 Systems Insight Manager settings, 34 T templates, 27 timeout value, 33 troubleshooting Console operations, 100 Designer operations, 105 flexing services, 99 miscellaneous issues, 106 physical service creation, 84 physical service deletion, 97 role specific operations, 100 Self Service Portal operations, 103 server operations, 100 service creation, 84 service deletion, 97 service operations, 100 virtual service creation, 91 virtual s
