HP Insight Orchestration 6.
© Copyright 2008, 2010 Hewlett-Packard Development Company, L.P. Acknowledgments Microsoft, Windows, Windows NT, Windows Server, Windows XP, and Vista are U.S. registered trademarks of Microsoft Corporation. VMware, VMware Server, GSX Server, ESX Server, and VMotion are trademarks of VMware, Inc. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Java is a US trademark of Sun Microsystems, Inc.
Table of Contents 1 Introduction......................................................................................................................7 Usage scenarios.......................................................................................................................................7 Automated infrastructure design provisioning and management........................................................7 Insight Orchestration and the HP Insight Dynamics solution.................................
Insight Orchestration approach to storage reservation and allocation...........................................45 Configuring Storage Provisioning Manager (SPM) in Virtualization Manager.............................46 4 Insight Orchestration provisioning and allocation....................................................53 Insight Orchestration lifecycle operations............................................................................................53 Create service operation..........................
7 Troubleshooting............................................................................................................77 Verifying the CMS configuration..........................................................................................................77 Synopsis...........................................................................................................................................77 Checks provided with Insight Orchestration....................................................
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.
fulfillment of self-service requests, and uses Insight software to monitor the health and utilization of the managed environment. Integrate Architects and administrators integrate Insight Orchestration with existing IT processes by modifying or creating Operations Orchestration workflows to customize the Insight Orchestration automation. They can link to approval processes, extend operating system deployment and server configuration, and integrate the SAN management processes with server deployment.
Orchestration server pools, managing the available networks and software inventory, approving user requests, and modifying user service infrastructures as required (for example to migrate logical servers between server blades to support maintenance activities on the physical environment). An administrator also performs manual tasks within a semi-automated operation. • User Uses the Self Service Portal to create infrastructure services from templates.
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/insightsoftware/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. Classes of Insight Orchestration users There are three classes of Insight Orchestration users.
2. Log in to the Operations Orchestration administrator account using the following credentials: • Username: admin • Password: the Insight Orchestration administrator password specified during Insight Orchestration installation NOTE: If the Insight Orchestration administrator password is subsequently changed, the change is not reflected in Operations Orchestration. 3. 4. After you log in, a tree appears in the left panel. Expand Configuration, and then expand System Properties.
HP Insight Software 6.2 Installation and Configuration Guide located at http://www.hp.com/go/ insightdynamics/docs. Insight Orchestration supports the un-licensing of Integrity servers from Insight Orchestration. To free an Insight Orchestration Integrity license, enter the vselicense command: % vselicense -r hpio -n For more information, see the vselicense manpage.
2. 3. 4. 16 Rename the new folder, for example, HPIO RHEL54 BL BFS. Copy the Deploy ProLiant System Configuration (BL BFS) job from the HP Deployment Toolbox/2→Hardware Configuration folder, and paste it into the new folder created.
5. 6. To create a job folder for each required operating system, repeat this procedure. To enable adding computers to the domain during provisioning, configure the Insight Control server deployment domain authorization using Tools→Options→Domain Accounts. Enclosures are discovered by Systems Insight Manager through the iLO IP address of the enclosure. Be sure to use the iLO credentials of the Onboard Administrator enclosure as the WBEM credentials. 7. 8.
2. 18 a. Right-click the Erase ProLiant Hardware job under the HP Deployment Toolbox→ Hardware Configuration folder, and then select Copy from the menu. b. 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. 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. Modify the Power Control task to shutdown instead of reboot in the default Erase job: a. Select the Power Control task, and then click Modify. b. Select the Shut down (if available) option, and then click Finish.
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.
b. To enable tftp and bootps services, edit /etc/inetd/conf, and uncomment the "tftp" and "bootps" lines and then run: inetd –c Depending on the client being installed (for example, if the client has a graphics card or keyboard attached), you may be prompted to identify the keyboard language. To avoid this, edit /var/ opt/ignite/config.local by adding the following line: kdblang="PS2_DIN_US_English" NOTE: Only HP-UX release 11.
Orchestration\conf. The following table shows the default values for each hypervisor type. If you exceed these values, virtual logical server provisioning might fail unexpectedly. Hypervisor Default number of virtual maximum concurrent requests ESX* esx.max.concurrent.requests=10 Hyper-V hyperv.max.concurrent.requests=5 Integrity VM integrityvm.max.concurrent.requests=5 NOTE: * The following ESX versions are supported: 3.5, 3i, 4 Classic, and 4i.
NOTE: Insight Orchestration uses only Accelerated Virtual I/O (AVIO) network devices for Integrity VM. An Integrity VM cannot be configured with a connection to a local virtual network through Insight Orchestration. Only vswitches connected to a physical NIC are recognized by Insight Orchestration. Insight Orchestration identifies Integrity VM virtual networks using vswitch names, which are limited to eight characters.
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 6.2 supports VLAN tagging with Hyper-V VM guests. VLAN tagging support requires using HP Network Configuration Utility (NCU) to create vNICS for each VLAN on the Hyper-V hosts and an associated Hyper-V virtual switch.
2. Configure HP NCU to present a vNIC for each VLAN ID. 1. 2. 3. Log into the Hyper-V server (select Start->Control Panel-> HP Network Configuration Utility). On the Ethernet Devices tab, select the NIC carrying multiple VLAN IDs. Select the VLAN(802.1Q) button, and then select the VLAN tab.
4. Select Add, and complete the following for each VLAN ID that needs to have a vNIC created. NOTE: • • 3. You need to know which VLAN IDs will be used on the selected NIC. Enter a descriptive name for the VLAN in the VLAN Name field (this is the name that will be used when configuring the Hyper-V virtual switch). Enter the VLAN ID in the VLAN Id field. To create a Hyper-V virtual switch for each VLAN ID, do the following for each Hyper-V VM host.
Creating VMM templates VMM templates are not utilized for ESX hosts. Insight Orchestration uses VMware templates as deployment targets for ESX. In order to create VMware templates, see Familiarizing yourself with ESX server and the task Create golden master (template) virtual disks in the Administration Guide for VMware ESX Server 2. NOTE: Template-based provisioning is not available for Integrity VM.
2. 3. 4. 5. 6. 7. 8. Click Deploy→Virtual Machine→Templates→Create Virtual Machine Template. The Step 1: Select Source Virtual Machine screen appears. Select a virtual machine from the list, and then click Next. The Step 2: Select VM Template Repository Host screen appears. Select the host that will receive the new VMM template, and then click Next. The Step 3: Specify the template Name and select VM Template Repository Folder screen appears.
7. Restart the Windows Service: HP Insight Orchestration. Customization requirements Insight Orchestration relies on sysprep to enable customization of Windows systems. Customization includes operations such as changing the hostname, applying the Windows license key on first boot, and setting the IP address. To automate Windows system deployments and apply the Windows license key automatically, you must edit the sysprep.inf file.
Creating SAN-backed storage 1. 2. 3. Verify that the target enclosures have been successfully discovered by Systems Insight Manager. Create a VC domain group which 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.
To add or modify storage pool entries, see your HP Virtualization Manager documentation. Insight Orchestration uses the tags selected from the Tag List (see the screenshot below) in the Storage Pool Entry 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.
then set up resources to allow provisioning. To log in to the Insight Orchestration, in Systems Insight Manager, select Tools→Insight Orchestration. After a short loading screen, the Insight Orchestration console appears. The Insight Orchestration console initially displays the Home tab with summary information. NOTE: When the Requests tab is first displayed, no requests will be displayed until an administrator or user has submitted a request and the request is in-progress or completed.
On the Edit Networks page, you can add information about the network and which IP resources are available. NOTE: Depending on your configurations, 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.
4. After adding the appropriate information to the tabbed areas on the left side of the Edit Networks screen, you can add IP ranges for use by Insight Orchestration. • • 5. To add DHCP address space, click the up arrow in the DHCP Addresses area, or enter the number of DHCP addresses you want to make available to Insight Orchestration. To add static address space, click New. A dialog appears for you to enter a range. Enter a Start and End address (inclusive), and then click OK.
and verify that every user to whom you want to grant Insight Orchestration access is a member of the appropriate user group in Windows: HPIO_Administrators, HPIO_Architects, HPIO_Users. You cannot modify any settings on this tab. Configuring server pools Insight Orchestration server pools are groups of resources that Insight Orchestration users use to submit requests to create new infrastructure services or add to existing infrastructure services.
2. In 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. 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.
5. Before Insight Orchestration can use the new pool, you must assign users to the pool. To assign users, select the pool in the list, and then click Modify Users. The Modify Pool Users page appears. 6. Select the user in the Unassigned Users 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 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 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 Manager (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 “serverInfo.
nic0 00:1E:0B:CC:61:B0 vlan84-dhcp-pxe-sa true ProLiant DL380 G5 Windows 32000 4 3000 2
updates the persisted inventory record for the server thereby enabling Insight Orchestration to include the server as a part of its inventory. As the servers are processed, they become visible in Insight Orchestration’s “Servers” interface. • :\Program Files\HP\Insight Orchestration\esa_extensions\ server \uuidHostMapper.xml “uuidHostMapper.xml” is the final XML file used in the reference implementation.
The workflow receives the server’s identity and examines the “uuidHostMapper.xml” file to determine which management processor to communicate with and perform the power operation. The workflow also 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.
Within OO Studio, select the System Accounts folder and then select the appropriate account (in this case “ILOUser”). Then select the lock icon to check out the account for editing. Assign the required user name and password that is to be used for the iLO account. When you are done, click the lock icon a second time to check in the account change. Finally, you must declare any new server models to be managed in Insight Orchestration.
SUPPORTED_MODELS=bl280c SUPPORTED_MODELS=bl460c SUPPORTED_MODELS=bl465c SUPPORTED_MODELS=bl480c SUPPORTED_MODELS=bl490c SUPPORTED_MODELS=bl495c SUPPORTED_MODELS=bl680c SUPPORTED_MODELS=bl685c SUPPORTED_MODELS=bl860c SUPPORTED_MODELS=bl870c SUPPORTED_MODELS=bl890c SUPPORTED_MODELS=HP xw8400 Workstation After making the changes to the blade_models.properties file, it is necessary to restart the Insight Orchestration Windows service for the changes to take effect.
the storage pool. It will then examine the initiator WWNs that were associated with each of the storage pool entries and perform the required assignment to the server in order to enable server visibility within the SAN to the set of SAN volume targets defined by the storage pool entries. This approach has the advantage of still being able to separate the boot and data storage visibility to the server during OS provisioning without requiring any access to the existing SAN management interfaces.
NOTE: Whenever a request that was paused for manual storage provisioning is continued, Insight Orchestration will re-enter the reservation algorithm, applying the same logic to satisfy both the boot and data disk requirements for the logical server. Using the pattern above, the following priority is observed when trying to satisfy the storage requirements: 1. 2. 3.
SPM has the concept of unmanaged arrays. 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 the ability for SPM to perform certain storage operations such as gathering property information, changing the hostmode, or performing LUN masking.
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. 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.
The process is initiated by selecting Modify→Logical Server Storage Pools from Virtualization Manager. This presents the screen above where the target portability group is selected (in this case a Virtual Connect Domain Group) and a new entry is added: In order to make use of the SPM catalog, select Use Catalog Storage followed by a brief description of the storage that is required and then select Show Candidates. The result is a list of SAN volumes known to SPM which meet the specified criteria.
For more detailed information on the use cases and a more exhaustive look at how storage is managed within Virtualization Manager, see the Storage Provisioning Manager User Guide and the Logical Server Management Best Practices white paper or contact your HP service representative.
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.
After successfully completing a Create Service operation, the provisioned Insight Orchestration infrastructure service is available for the duration of the lease period and you can access the servers through the network.
• • SAN administrator cannot create the disks Insight Orchestration administrator rejects the request Add data disk to group operation The Add data disk to group operation adds private or shared data disks to an existing infrastructure service. Insight Orchestration provisions and allocates the storage to their attached servers.
After successfully completing the operation, the physical server blades are allocated and configured into existing server profiles, physical and virtual servers are powered on, and the servers return to normal operation. If the operation fails, the servers are not available to activate. Change lease operation The Change Lease Period operation enables you to modify the starting or ending dates of the service. You can also extend or reduce the lifetime of the service.
Manual processes within the lifecycle operations The execution of the Insight Orchestration lifecycle operations might require you, as an Insight Orchestration administrator, to perform manual tasks. If defined, Insight Orchestration invokes an Operations Orchestration workflow to initiate, remind, or otherwise facilitate a manual task and generates a Systems Insight Manager event. You can use Workflow integration or the Insight Orchestration console interface to signal completion of a manual task.
— — — — Makes the new disk visible to the servers Powers up the servers Executes custom actions Sends notifications • Data disk scrubbing If a Create Service operation uses manual operating system deployment, the corresponding Delete service operation requires disks to be scrubbed manually. The Insight Orchestration administrator is notified and the operation pauses until the Insight Orchestration administrator scrubs the disks attached to the servers being deprovisioned and continues the operation.
between VCDomain Groups is uncertain. The Insight Orchestration algorithm verifies VCDomain group boundaries by backtracking, incrementally building candidate solutions for allocation, and abandoning each partial candidate as soon as it determines that it cannot possibly complete the allocation. If the subnet does not have enough servers attached to the network associated to the VCDomain Group, the subnet allocated to a network is abandoned.
Edit the Create Boot Environment and add the export kernparm=mpath kernel parameter. After updating the job, you are able to deploy both Red Hat Enterprise Linux 5.2 and Red Hat Enterprise Linux 5.3 to a multi-path LUN. Customizable allocation process Insight Orchestration performs automated resource allocation using a built-in allocation mechanism, as described above. This built in allocator is the default allocation mechanism. In addition, version 6.
• • • • • • package package-name imports globals functions queries rules The order in which the elements are declared is not important, except for the package name. If you declare a package name, it must be the first element in the rule file. Example: Rule to verify server memory criteria package com.hp.hpio.controller.policy; import java.util.List; import java.lang.Integer; import com.hp._2007.ess.sw.model.infrastructureutilityschema.LogicalServer; import com.hp._2007.ess.sw.model.
}else{ return false; } /* -------------- CUSTOM LOGIC ----------------------*/ Customizing existing rules The advantage of providing a rules based allocation fitting process is that you can customize the existing rules to change the business logic by modifying the CUSTOM LOGIC portion of the code. You can modify or delete existing rules, or add new custom rules. Rules are written in Java and the Drools syntax. Available hooks for customizing: • SubnetPolicyCheck.
$subnet : Subnet() from $resLst; // call new user defined function with required arguments // function has to return true in case of success or false // in case of failure.
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.
• 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. • Collaborate with the business units to register user accounts for access to the Self Service Portal. • Assign one or more resource pools to each self-service user, authorizing the user to deploy service templates using a given pool of hardware resources.
• Servers 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 • Networks • Software folders.
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. 2. On the CMS at a Command Prompt, type cd /conf/console/mks scp –r @:/usr/lib/vmware/webAccess/tomcat/apache-tomcat-*/webapps/ui/plugin/*.
You can access Self Service Portal from the desktop or a browser. To access Self Service Portal from the desktop, do the following: 1. 2. Open a web browser on the CMS where Systems Insight Manager is installed. 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/.
For more information on using Self Service Portal, see the Self Service Portal online-help system by clicking the? button in the upper-right portion of the Self Service Portal window.
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. For more information, see your Operations Orchestration Studio documentation.
5. Select the Save file radio button, then click Save File to save the file to your hard drive. Installing a remote instance of Operations Orchestration Studio To install Operations Orchestration Studio on a remote computer: 1. 2. 3. 4. 5. 74 Navigate to the directory where you saved the application and double-click EmbeddedStudioInstaller-7.51.exe to launch the installer. On the Welcome dialog, click Next to begin the installation.
• • • 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 computers To configure Operations Orchestration Studio on a remote computer 1. 2. 3. 4.
In Operations Orchestration on the CMS, you might have to set the following Operations Orchestration system properties with the appropriate SMTP values: 76 Name Example Value Notes HpioSmtpHost 127.0.0.1 If SMTP is on another server, replace 127.0.0.
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 VSE Management→Check CMS Configuration.
Checks provided with Insight Orchestration Name Description HPIO Database Responsiveness Validates the Insight Orchestration configuration file for database communication HPIO Responsiveness Verifies the communication between Insight Orchestration and Systems Insight Manager HPIO User Groups Configured Verifies if Insight Orchestration user groups are properly configured in Windows for basic operations HPIO ToolBox Configured in HPSIM Verifies if Insight Orchestration user groups are properly confi
• • 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.
• A Create request fails, but the service is still listed in the Service tab in “Reserved” state, and no resources are allocated. Failure message Unable to allocate servers and networks in the same Virtual Connect Domain Group. Either more available servers are required, or could not match existing servers against memory size, disk space and processor count requirements.
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 I cannot create a storage pool on HP Insight Dynamics because the VCDG is not listed on the Storage Pools screen. Possible cause VCDG is using factory default MAC/WWN settings. Action HP Insight Dynamics and Insight Orchestration do not support VCDG with factory default MAC/WWN settings. Logical servers require portable WWNs and MAC addresses that can be moved from blade server to blade server.
Issue Physical server provisioning using Insight Control server deployment fails during the final personalization step when the CMS is configured with an automatic proxy configuration script in IE. Possible cause Using Insight Orchestration for physical server deployments via HP Insight Control server deployment fails during the final personalization step. This can occur when there is a problem or delay communicating with the automatic configuration script configured in Microsoft Internet Explorer.
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.
• Storage Pool Entries defined from VSE UI may might not appear under the Storage page in the Insight Orchestration UI Failure message Error deploying logical server from _ls realized by vm:///vmfs/volumes/....vmx/. Copy virtual machine failed: Unable to access file [inactive-datastore-name]vmware-template-name/vmware-template-name.vmdk. In the message above, “/...
Issue VMware ESX hosts are licensed but do not show up in Insight Orchestration Unassigned pool. Possible cause The hosts with virtual machine management cannot register because they only have base ESX licenses. Action 1. In SIM's Deploy→License Manager..., apply full ESX license(s). 2. In SIM's Configure→Insight Control virtual machine management→Register VM Host..., re-register the VM Hosts, for example: a. Select collection: ESX VM Hosts b. Click View Contents c. Click Apply d. Click Next e.
Issue Storage Pool Entries defined in ID-VSE UI may not be shown under Storage page in HP IO console. Possible cause • The HP IO console's Storage page has not been refreshed since changes are made in ID-VSE's Manage Storage Pool page. • The storage pool entry is filtered out because it is invalid for HP IO to use. Action • Refresh the HP IO Storage page.
Issue Insight Orchestration did not correctly erase the disk during deprovisioning. Possible cause The Insight Control server deployment erase disk job name is not correct. Action For Insight Orchestration to correctly erase the disk content when deprovisioning physical servers using a non-English server deployment version, there must be an English Erase ProLiant ML/DL/BL Array Configuration {LinuxPE} job under the Server Deployment Toolbox\1 – Hardware Configuration\Array\ server deployment folder.
If a physical server was selected and the infrastructure service was provisioned by Insight Orchestration, check if its status is not standby. Issue In some circumstances, when processing a create request for a template containing a network specified by attributes and a virtual logical server group, Insight Orchestration may be unable to successfully reserve resources even though they exist.
• What messages do I see when a paused boot disk deployment is cancelled by an administrator? Issue What messages do I see when a paused boot disk deployment is cancelled by an administrator? Possible cause — Action When an administrator cancels a boot disk allocation that is paused, Insight Orchestration may display two messages on the Request page: • first message indicates that the boot disk deployment was canceled by an administrator, for example: “ Request for 3Tier_infra_1 has been canceled by
• Some template XML hand-editing errors, for example, Duplicate Logical Server Group boot order, are not caught during Insight Orchestration Designer's Import of a template from XML. 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 I use 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.
Issue Entering a hostname in the network WINS setting causes a Windows customization to fail. Possible cause — Action To resolve this issue, enter either an IP address or leave the network WINS setting blank. Issue My resources do not show up in Insight Orchestration Unassigned Pool. Possible cause Resources are added to Insight Orchestration Unassigned Pool when Insight Orchestration recognizes they are available in your system, licensed, and configured correctly. Action To display VM Hosts: 1.
• • Server.Error.Request Details: null Please make sure the Insight Orchestration service is running and try again. With IE6, launching Designer from Insight Orchestration console can cause sporadic Designer interface failures. Insight Orchestration console in Systems Insight Manager displays the following message: “The HP Insight Orchestration tool cannot be displayed.
Issue Designer error dialog message: A fatal error occurred while initializing the Designer. The error that was returned was: ERROR (code = -1, Key = null): Server.Error.Request Details: null Please make sure the Insight Orchestration service is running and try again. Possible cause Occurs when launching Designer from Console (using the Template tab Edit buttons). Action To workaround this issue, launch Designer using a browser at https://:51443/hpio/designer and open the desired template.
• • • • • You may encounter Integrity firmware blade corruption during provisioning of the following Integrity blades: BL870c, BL870c i2, BL890c, or BL860c i2. Blades that are not in use are shown in IO server pools, but IO does not allocate the blades for provisioning. No virtual resources are displayed under the HP IO Servers tab. A check in HPIO's ioassist failed to communicate with Insight Orchestration, generating a TimeoutException.
Issue VI3 server is not configured in Systems Insight Manager or becomes unavailable. Insight Orchestration may generate a large number of these messages causing the Insight Orchestration log file to grow very rapidly.
Issue I cannot access the VMware console using Firefox. Possible cause The VMware console browser plug-in does not support Mozilla 3.x. Action To enable VM console access from Mozilla 3.x clients: 1. Install the IE tab Mozilla plug-in located at https://addons.mozilla.org/en-US/firefox/addon/ 1419. 2. In your Mozilla browser, select Tools→IE Tab Options. 3. In the URL field of the IE Tab Options screen, enter https://*/hpio/controller/html/vmwConsole*, and then click Add.
Issue You may encounter 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 No virtual resources are displayed under the HP IO Servers tab. Possible cause Five minutes after clicking HP IO UI Servers refresh button, the HPIO Servers tab still shows no virtual hosts (you can see a TimeoutException from the HPIO getVMHostServerPools call in the stack trace within the hpio-controller.log file on the CMS).
1. Power on the server blade. You might need to cycle the power if the server blade is stuck. 2. Make sure that the attached boot LUN erases, by doing one of the following: • Run the Erase ProLiant ML/DL/BL Array Configuration {LinuxPE} job from the Insight Control server deployment console. This is the preferred option. • Alternatively power on the server blade, then press F9, and select Advanced Options→Erase Boot Disk. 3. Verify that the server blade is powered off after completing the above step.
NOTE: In previous versions of Insight software the “Delete Logical Server” option was presented as the “Delete with Unrecoverable” option and the “Unmanage Logical Server” option was presented as the “Delete with Recoverable” option.
Configuring storage pool entries, FC zones, and disk array presentations The following procedure is the HP recommended approach for configuring storage pool entries, FC zones, and disk array presentations. 1. Create a storage pool entry within HP Insight Dynamics using the storage pool management screen from in HP Insight Dynamics. In this example, the storage pool entry is defined as follows: In this example, the storage pool entry name is “e5_win_BD_05”.
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.
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.
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 VMHost. Login in to the Virtual Center server which is providing management for the VMHost(s) and perform the following changes: 1.
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.
1. 2. Select Start->All Programs->Hewlett-Packard->Operations Orchestration->HP Operations Orchestration Studio. At the login prompt, log in to the Operations Orchestration administrator account using the following credentials: 1. Username: admin 2. Password: the Insight Orchestration administrator password specified during Insight Orchestration installation 3. 4. In the tree displayed in the left pane, expand Library, then expand System Properties.
8 Support and other resources Information to collect before contacting HP Be sure to have the following information available before you 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 United Stat
Typographic conventions Related documents Documentation and support For support, software updates, and additional information on HP Insight Orchestration and other products used with Insight Orchestration, see the following websites: • HP Insight Orchestration website at http://www.hp.com/go/insightorchestration. • HP Insight Control website at http://www.hp.com/go/hpsim • Insight Control website at http://www.hp.com/go/ice • HP Insight Dynamics website at 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.
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. Insight Control server deployment A multi-server deployment tool that enables IT administrators to easily deploy large numbers of servers in an unattended, automated fashion.
• • • • 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 Virtual Server Environment. 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.
Orchestration. You can use workflows to define integration with your IT processes, including approvals, manual operating system deployment, manual storage provisioning, and sending notifications. workflow A set of linked actions that automate customer-specific IT tasks on an Insight Orchestration-provisioned service. Operations Orchestration workflows are created, modified, and saved using Operations Orchestration, Studio, the workflow designer embedded in Insight Orchestration.
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.
NOTE: These parameters are required in the workflow definition even if the parameters are not used within the workflow. Insight Orchestration and Operations Orchestration communication Insight Orchestration uses HTTPS communication with the Operations Orchestration Server to invoke Operations Orchestration workflows and pass any data needed by the workflow. The Operations Orchestration Server may be located on the same CMS as Insight Orchestration, or may be on a separate server.
Service actions Service actions are the stages of infrastructure service that may invoke an Operations Orchestration workflow.
Index access, 65 accessing Designer, 65 Insight Orchestration console, 67 Operations Orchestration, 73 Self Service Portal, 69 add disks, 55 add servers, 54 administrator, 8 allocation, 57, 58 allocation rules, 60 approval, 57 architect, 8 automated provisioning, 59 overview, 66 Requests tab, 67 Servers tab, 68 Services tab, 67 Software tab, 68 Storage tab, 68 tasks, 66 Templates tab, 67 Users tab, 68 CPU shares, 110 create service, 53 creating job folders, 15 storage, 30 VMM templates, 27 customization, 2
automation, 7 console, 66 console interface, 67 designing, 7 integration, 8 lifecycle operations, 53 operation, 7 product, 7 provisioning, 7 Self Service Portal, 69 Self Service Portal interface, 70 user, 9 users, 8 I Insight Control, 7 Insight Control server deployment job folders, 17 Insight Control virtual machine management, 7 Insight Orchestration benefits, 7 features, 7 Insight Orchestration applications, 65 Insight Orchestration console access, 67 installation, 11 J job folders, 15, 17 L lease per
T templates, 27 timeout value, 31 troubleshooting Designer operations, 96 flexing services, 91 miscellaneous issues, 98 Operations Console operations, 92 physical service creation, 79 physical service deletion, 89 role specific operations, 92 Self Service Portal operations, 95 server operations, 91 service creation, 79 service deletion, 89 service operations, 91 virtual service creation, 86 virtual service deletion, 90 working with services, 79 U uninstall, 11 usage scenario, 7 user configuration, 13 users
