HP Insight Orchestration 6.
© Copyright 2009, 2010 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.
Table of Contents 1 Introduction...............................................................................................6 Usage scenarios.....................................................................................................................................6 Automated infrastructure design provisioning and management.....................................................................6 Important terms........................................................................................
Customizing existing rules.................................................................................................................50 Writing a new rule file......................................................................................................................50 Deploying rules...............................................................................................................................52 5 Using Insight Orchestration Designer..........................................
10 Support and other resources.....................................................................86 Information to collect before contacting HP...............................................................................................86 How to contact HP................................................................................................................................86 Registering for software technical support and update service............................................................
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.
Important terms • Infrastructure service A running configuration of infrastructure resources that is designed to run a business application such as a multi-tier web application. Infrastructure resources include server blades, virtual machines, SAN disks, networks, and IP addresses. It is also referred to as a service or service instance. • Template Specifies the requirements, or design, for an infrastructure service in terms of server groups, networks, and storage.
architect can also author and attach Operations Orchestration workflows to a template to automate additional IT tasks during the provisioning and ongoing management of the service infrastructure.
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 server deployment and SMTP parameters available to use during installation. For more information, see HP Insight Software 6.0 Installation and Configuration Guide on the Insight Software DVD #1 or at http://www.hp.com/go/insightsoftware/docs.
3 Configuration Configuring Insight Orchestration users in Windows During the Insight Orchestration installation process you are prompted to set up users or you can add users later using the Windows procedure below. The HP Insight Software Installer adds the user who installed the system to the HPIO_Administrators group. To add additional users to any Insight Orchestration user groups, use your computer management or administrative tools.
Verify that the HpioCmsIP property is set to the IP address of the CMS. If the IP address is not set or incorrect, double-click in the value area for HpioCmsIP and enter the correct IP address. 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 emails. The Operations Orchestration system properties screen displays all the classes of emails sent by Insight Orchestration.
Hypervisor Default virtual.max.concurrent.requests value ESX* 10 HyperV 10 NOTE: * The following ESX versions are supported: 3.5,3i, 4 Classic, and 4i. If you are using a mixed hypervisor environment, then you must set the value of virtual.max.concurrent.requests to the minimum of all the hypervisor values in the environment. For each virtual logical server, Insight Orchestration supports up to 14 private disks or 15 shared disks.
1. Power off the virtual machine you want to use in the VMM template. It is good practice to cleanly power off the virtual machine by accessing the virtual machine and performing an operating system shutdown rather than using a Hypervisor power off command. If the virtual machine is in a suspended state when you create the template, provisioning will fail during customization with an error message of “ VM must be powered off for customization ”. 2. 3. 4. 5. 6. 7. 8.
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. This edit enables Insight Orchestration to provision new Windows systems with no manual interaction.
should be set to 10. If you set the attribute to a greater value, then physical logical server provisioning might fail. Physical provisioning requires: • Available VC Domain groups on the Virtual Connect Enterprise Manager (VCEM) • Configuring server deployment platforms including Insight Controller server deployment, Ignite-UX, or HP Server Automation and creating job folders • Creating SAN-backed storage Verifying VC Domain groups Insight Orchestration requires virtual domain groups.
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. To enable adding computers to the domain during provisioning, configure the Insight Control server deployment domain authorization using Tools→Options→Domain Accounts.
1. Save a copy of the default Erase job: 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.
2. 18 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. 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.
3. 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.9.260 or greater. The Ignite server must have NFS configured as well as the tftp and bootps services enabled in /etc/inetd.conf. a. To setup NFS and export the directories Ignite needs, run: /opt/ignite/lbin/setup_server –n b.
3. 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. Select Refresh of Virtual Connect Resources and Refresh Storage Pool Entries, and then click Refresh. 4. Click Modify→Logical Server Storage Pools. 5. Select the target domain group from the Virtual Connect Domain list.
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 Settings, however be sure to modify these entries, after you receive the LUN information from your SAN administrator.
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. Before using Insight Orchestration, you must setup up server pools and networks, and verify the Users and Software tabs using Insight Orchestration console. Viewing and configuring networks 1. Click Networks.
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 requried. 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. 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. • 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 click then click OK.
Insight Orchestration automatically populates the Unassigned pool after installation with the resources identified by Systems Insight Manager. Physical resources are only available after a VCD Group is correctly created in VCEM. Insight Orchestration updates the information each hour. After you update the available resources, click refresh to see your updates immediately. 1. To create a new server pool, click Create Pool. 2. In Pool name, enter a descriptive name.
4. 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. 5. 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 and a list of the assinged users appears at the bottom of the screen.
inventory and for performing basic power control. Several server types and configurations may integrate into Insight Orchestration using ESA in Insight Dynamics. • Non-HP servers • HP rack mount servers • HP c-Class blades (not managed by Virtual Connect) For each of the server types referenced above, the following storage configurations are supported: Boot Disk • A SAN (Fiber Channel) attached disk • A local (direct attached) disk.
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 x86_64 true
• :\Program Files\HP\Insight Orchestration\esa_extensions\server \uuidHostMapper.xml “uuidHostMapper.xml” is the final XML file used in the reference implementation. It provides a mapping between the server records and the IP address at which the server’s management processor resides. The workflows which query and control power for the server require this mapping file to be in place for each server.
An additional step is required to configure the management credentials for power control. The reference implementation ships with two built-in system accounts one for iLO and one for Dell. OO Studio selects and configures the username and password for each of these accounts. The credentials are stored in an encrypted form within Operations Orchestration. Within OO Studio, select the System Accounts folder and then select the appropriate account (in this case “ILOUser”).
IA_64_MODELS=nb50000c SUPPORTED_MODELS=bl260c 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 second approach is called “Dynamic” SAN volume automation via LUN masking. In this approach, SAN volumes are pre-created but are not yet masked to one or more initiator WWNs. Zoning must be pre-configured. The SAN volumes are made available within Virtualization Manager’s storage pool as storage pool entries. At service creation, Insight Orchestration selects one storage pool entry.
manually fulfilled. If you use “Dynamic” SAN volume allocation automation, you must ensure the authorizations for the SPM catalog entries allow LUN masking and hostmode changes. Configuring Storage Provisioning Manager (SPM) in Virtualization Manager In order to make use of “Dynamic” SAN volume automation via LUN masking, it is necessary to configure SPM for access to one more arrays.
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 enumerate 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 add a new entry: 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 that 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 Proisioning 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 executes the following infrastructure lifecycle management operations: • Create service Automatically provision infrastructure based on the specification in a service template, using resources allocated from assigned pools • Delete service services • Add servers to group them • Add data disk to group Add data disks to an existing infrastructure service, allocating the disks and attachi
When executing the operation, Insight Orchestration: • Validates the request • Powers off the servers • Deletes the virtual machine or server blade profile • Scrubs the boot and data disks • Deallocates the servers (server blades and virtual machine hosts) • Deallocates the networks and IP addresses • Deallocates the boot and data disks • Executes custom actions • Sends notifications After successfully completing a Delete operation, the Insight Orchestration infrastructure service is destr
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.
event. You can use Workflow integration or the Insight Orchestration console interface to signal completion of a manual task. The manual tasks are associated with paused states in the Insight Orchestration automation and include: • Boot disk allocation When LUNs with the required attributes are not available for a Create Service or Add servers to group operation, disk allocation is blocked and the Insight Orchestration administrator is notified.
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. • Data disk deletion When configuring Insight Orchestration to perform manual storage provisioning, the Insight Orchestration administrator is notified at the end of a Delete service operation.
Insight Orchestration supports SAN boot or DAS boot OS deployment using Insight Control server deployment, HP Server Automation, and Ignite-UX. With Insight Control server deployment, boot 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.
• 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. When the customizable allocation process initiates, Insight Orchestration reads the policy.
* from PolicyExecutionVO passed to rule engine. * */ /* DO NOT MODIFY */ rule "INIT" salience 1000 when pVO : PolicyExecutionVO(); then insert(pVO.getAllocationEntry().getServiceEntity()); insert(pVO.getResultMap()); insert(pVO.
if(logicalMemorySizeMB.doubleValue() <= resourceMemorySizeMB.doubleValue()){ return true; }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.
Example: Custom rule rule "CustomRule1" when $pVO : PolicyExecutionVO( ); $resLst : List(); /* --------------- CUSTOM LOGIC ------------------ */ // Get service entity and resource objects. $logicalSubnet : LogicalSubnet(); $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.
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. Wherever applicable, update the hook information in the policy.xml file by modifying or adding the recently defined rule file. SubnetCheck.drl, newrulefile.
5 Using Insight Orchestration Designer Overview HP Insight Orchestration Designer enables you, as an architect, to plan and design multi-server, multi-tier infrastructures using a drag-and-drop interface. The infrastructure can include virtual servers, blades, and physical servers. Insight Orchestration users can provision services using Insight Orchestration templates.
6 Using Insight Orchestration console Overview The Insight Orchestration console enables you, as an administrator, to deploy, manage and monitor the overall behavior of Insight Orchestration and its users, templates, services and resources. Administrators also interact with the architects to ensure templates are compatible with existing resources and business needs as requests are fulfilled or denied.
For more information on using Insight Orchestration console, see the Insight Orchestration console help system. Console access to deployed servers Insight Orchestration supports console access to deployed servers from Insight Orchestration console and Self-Service Portal. Supported console types include Remote Desktop (RDP), telnet and VM console to ESX VMs. Limitations Telnet and RDP access depend upon network connectivity from the client to deployed servers.
7 Using Insight Orchestration Self-Service portal Overview The Self-Service portal enables you to create infrastructure services from published templates. To create infrastructure services: 1. Review the published templates and decide which template is appropriate for the current objectives. 2. Review your assigned pools and select the resources to use for your service 3. Submit a request to provision the service. 4. After the administrator approves the request, monitor the service provisioning execution.
8 Using Operations Orchestration 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.
• NIC1—A comma-separated list of the IP addresses for NIC1 for each active server in the group. • NIC2—A comma-separated list of the IP addresses for NIC2 for each active server in the group. • NIC3—A comma-separated list of the IP addresses for NIC3 for each active server in the group. Responses include: • Passed—A ping was successful on all servers. • Failed—A ping failed on one or more servers in the group. To utilize the workflow you must: • Verify your template has a recoverable server group.
Creating an infrastructure service instance Using the Self-Service portal or Insight Orchestration console, create a service instance of your template. After successfully provisioning a service from the template, Insight Orchestration executes the workflow for the server group in your template folder, for example Library/Hewlett-Packard/Insight Orchestration/Recovery/MyTemplate/SvrGrp1, periodically. The period between intervals is defined by the recovery.interval parameter in /conf/hpio.properties.
9 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.
Actions: There are no users in HPIO_Architects group in the CMS. Create a user and assign to HPIO_Architects group in the users and groups using Windows Computer Management. (...
• 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.
Action • Verify that the Insight Orchestration server pools referenced in the Create Request contain sufficient suitable servers taking into account all the server, storage and networking requirements of the template. • Check whether or not any servers were moved to the maintenance pool due to a previous provisioning failure. Check for “clean-me” logical servers. If there are any, perform a manual cleanup process. See “Manual clean-up process”.
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.
Action If you receive this email, you must add the LUN information to both the new server and the existing servers. You only need to add the LUN information to the HP Insight Dynamics storage pool entry for the new server. Issue I cannot add servers to an existing service using a Static IP address.
Possible cause Incorrect value of virtual.max.concurrent.requests Action In the hpio.properties file, set virtual.max.concurrent.requests to the correct value and restart Insight Orchestration and VMM. See “Configuring your environment for virtual provisioning”. Failure message The start function on virtual machine failed: There are not enough licenses installed to perform the operation. Possible cause ESX host not licensed.
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. To resolve this issue, you must power off the virtual machine before creating virtual machine management template from the virtual machine.
deployment job within the same folder, and then modify the Erase ProLiant ML/DL/BL Array Configuration {LinuxPE} job. For more information on modifying the job, see “Creating server deployment job folders”. Issue An infrastructure service has been deleted, but I did not delete it. Possible cause Insight Orchestration may be configured to remove infrastructure services when the lease period expires.
Action • If it is not a “clean-me” logical server then return to Insight Orchestration and issue an Activate servers request for the logical server. • If it is a “clean-me” logical server then perform a manual cleanup process for the logical server. See “Manual clean-up process”. Flexing services Troubleshooting items addressed in this section: ▲ Add data disk request fails Issue Add data disk request fails.
• A step in the Request Details is shown as having failed. • A request continues to process after being canceled. • Some of my virtual machine templates do not appear on the Software tab. • 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.
Action A user might not be able to log in to the Insight Orchestration console in Systems Insight Manager or the Insight Orchestration self-service portal after installing Insight Orchestration, or after moving the user from one Insight Orchestration user group to another, for example moving a user from the HPIO_Administrators to the HPIO_Users group. To resolve this issue, reboot the CMS. Issue When extending the lease period, the operation fails without stating a specific reason or error message.
Issue Some of my virtual machine templates do not appear on the Software tab. Cause Insight Orchestration only supports virtual machine templates with exactly one disk. Virtual machine templates with more than one disk do not appear on the Software tab. Action Modify your virtual machine template to contain only one disk.
Restore the communication or restart the provider service. Then refresh Insight Dynamics by using Systems Insight Manager, Tools→Logical Servers→Refresh. Select Refresh of Virtual Connect Resources or Refresh of Virtual Machine Resources as appropriate. Alternatively, as a workaround, you can change the number of polling intervals before a server is removed by changing the value of the server.keep.alive.rounds property in ..\Program Files\HP\Insight Orchestration\conf\hpio.properties.
Action • Verify that the Virtual Center credentials are correct on Systems Insight Manager. • Verify that the virtual machine hosts are correctly registered to Insight Control virtual machine management usage and are not reporting issues on Systems Insight Manager • Verify that HP Insight Dynamics is correctly displaying the resources (physical or virtual.
Issue In Systems Insight Manager, the Insight Orchestration error page The HP Insight Orchestration tool cannot be displayed appears when listing server pools exceeds a one-minute timeout. Possible cause • The physical server or virtual machine Hypervisor is not responding. • The Insight Orchestration service is down. • The network is slow or disconnected. • Verify that the physical servers and virtual machine Hypervisors are available • Verify that the Insight Orchestration service is started.
Possible cause Insight Orchestration provides a set of default values for the parameters listed below because some combinations can cause memory leaks. If you have made log4j customizations to Insight Orchestration v 1.0.2 and are upgrading to Insight Orchestration v 6.0, you could lose your customizations. Action Before installing the patch you should backup the following log4j parameters so that you can restore the customizations in the event of a patch uninstall. • log4j.appender.dailyFile=org.
Corrective procedures Manual clean-up process If an Insight Orchestration physical server deployment fails or Insight Orchestration delete service request fails, you must perform a manual cleanup process to fully erase the operating system from the boot disks, detach the blade from the storage, and return the blade to an Insight Orchestration server pool for a future provisioning request.
NOTE: Do not select the Unmanage Logical Server option. Doing so will cause the logical server storage pool entry to be modified so as to contain new WWNs without regard to presentation or zoning. Follow the procedure in “Configuring storage pool entries, FC zones, and disk array presentations” to resolve this issue. 3. 4. Verify that in Virtual Connect Enterprise Manager the VC profile associated with the failed server blade exists.
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 pre-fix (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 re-supplied 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.
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. 84 Increase the number of CPU shares assigned to the ESX 3.X or ESX 4.X Service console: a. Log in to VirtualCenter from the Virtual Infrastructure Client with a user that has administrative rights b. Select the VMHost from the left-hand side tree browser c. Select Configuration. d. Select System Resource Allocation.
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. Possible cause Due to a large number of resources to fetch, one or more of Insight Orchestration's resource fetch operations may have timed out, waiting for completion.
10 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
Command user input computer output Enter term variable value Command name or qualified command phrase. Commands and other text that you type. Text displayed by the computer. The name of a keyboard key. Note that Return and Enter both refer to the same key. A sequence such as Ctrl+A indicates that you must hold down the key labeled Ctrl while pressing the A key. Defined use of an important word or phrase. The name of an environment variable, for example PATH or errno.
Glossary administrator A user who manages users, resource pools, and self-service requests through HP Insight Orchestration console. approvals A permission given to a user-generated request by an administrator. Approvals occur during the allocation and provisioning phases of creating or updating a service.
Insight Orchestration console A web application (Systems Insight Manager plug-in) that enables you to deploy, manage, and monitor the overall behavior of Insight Orchestration and its users, templates, services, and resources. Internet Explorer (IE) Microsoft's web browser. Internet Protocol version 6 (IPv6) Internet Protocol version 6 is the next-generation Internet Protocol designated as the successor to IPv4. IPv6 See Internet Protocol version 6.
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. You can view the available templates, select a template that meets your provisioning requirements, and submit a service request.
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. World Wide Name (WWN) A unique identifier which identifies a particular Fibre Channel (FC), Advanced Technology Attachment (ATA) or Serial Attached SCSI (SAS) target. Each World Wide Name is an 8 byte identifier.
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.
For some Operations Orchestration flows, Insight Orchestration waits for a user response before moving to the next step of an infrastructure’s lifecycle (see “Administrative actions”). Insight Orchestration passes a unique, one time use User Token to these Operations Orchestration flows to Administrator-defined email recipients. This token is used to authenticate the user response.
• Insight Orchestration configuration file which specifies Operations Orchestration server and Operations Orchestration flows for administrative actions: C:\Program Files\HP\Insight Orchestration\conf\hpio.
Index A access, 53 accessing Designer, 53 Insight Orchestration console, 54 Operations Orchestration, 57 Self-Service portal, 56 add disks, 43 add servers, 42 administrator, 8 allocation, 7, 45, 46 allocation rules, 47 approval, 45 approvals, 7 architect, 7 automated provisioning, 46 B benefits, 6 boot disk, 45 browser access, 53 Insight Orchestration console, 54 Self-Service portal, 56 C change lease, 44 checksum error correcting, 81 CMS configuration, 60 configuration customization, 14 ESX, 11 networks,
infrastructure service, 7 infrastructure service creation, 59 Insight Control, 6 Insight Control server deployment job folders, 16 Insight Control virtual machine management, 6 Insight Orchestration benefits, 6 features, 6 Insight Orchestration console access, 54 installation, 9 console, 54 console interface, 54 Designer, 53 designing, 6 infrastructure service, 7 integration, 6 lease period, 7 lifecycle operations, 41 operation, 6 product, 6 provisioning, 6, 7 request, 7 resource pool, 7 Self-Service porta
software deployment, 8 storage, 20 storage pool entries configuration, 79 support, 87 system properties, 10 Systems Insight Manager settings, 22 T template, 7 templates, 12 terms, 7 timeout value, 22 troubleshooting Designer operations, 73 flexing services, 69 miscellaneous issues, 74 Operations Console operations, 69 physical service creation, 62 physical service deletion, 67 role specific operations, 69 Self-service portal operations, 72 server operations, 69 service creation, 62 service deletion, 67 ser
