HP Matrix Operating Environment 7.2

Transcription

1 HP Matrix Operating Environment 7.2 Installation and Configuration Guide for Provisioning with Virtual Resources Abstract This guide is for network or system administrators installing HP Matrix Operating Environment products to manage virtual resources. The instructions require knowledge of Windows network and server administration, including user and group control, and experience using virtual machine and hypervisor resources and templates. HP Part Number: Published: March 2013 Edition: 1

2 Copyright 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , 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. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Java is a registered trademark of Oracle and/or its affiliates. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. UNIX is a registered trademark of The Open Group. Warranty HP will replace defective delivery media for a period of 90 days from the date of purchase. This warranty applies to all Insight Management products.

3 Contents 1 Overview...6 HP Matrix Operating Environment setup and installation overview...6 Related information resources Before you begin...9 Verify Supported Hardware and Software...9 Verify or Install Hypervisors...9 Compiling the documentation and media...9 Collecting network connection information...10 Collecting management credentials...10 Planning and design for public cloud bursting Preparing the Central Management Server...12 Finalizing the Windows installation on the CMS server...12 Installing additional Windows components...14 Configuring SNMP and UAC...18 Installing an SPP...20 Configuring the management networks...20 Configuring firewalls...21 Installing Windows updates...24 Installing the remaining Insight Management software dependencies Installing Insight Management software on the CMS...28 Installing and configuring the CMS...28 Installing Matrix OE patches...42 Setting the Matrix Operating Environment home page...43 Tuning the Matrix Operating Environment for large scale production environments...44 Increasing JVM heap size...44 Increasing timeout value for virtual logical servers...45 Configuring ESX memory oversubscription...45 Configuring Microsoft SQL Server Configuring the CMS...47 Setting Matrix Operating Environment role authorization...47 Role authorization overview...47 Senior Administrators...47 Creating a Senior Administrators Users Group...47 Verifying Authorizations...48 Modifying authorization for Matrix infrastructure orchestration Administrators...49 User management overview...50 Adding user accounts to groups...51 Checking and setting primary network of the CMS...51 Configuring alerts for disk space usage Configuring discovery and credentials...54 Configuring credentials...54 Changing the Daily System Identification time...55 Defining discovery tasks...55 Troubleshooting discovery issues...60 Discovery order...61 Large system discovery...61 Contents 3

4 7 Configuring VMware vcenter and Microsoft System Center Virtual Machine Manager settings Configuring integration with deployment servers...64 Registering deployment servers Configuring and licensing with managed system setup wizard...66 Checklist...66 Using managed system setup wizard...66 Steps of the wizard Creating a virtual machine logical server...74 Importing virtual machines...75 Creating virtual machines Configuring Matrix infrastructure orchestration...81 Preparation...81 Configuring notifications and properties...81 Configuring for virtual machine provisioning...84 Verifying Microsoft Windows Sysprep...84 Installing Microsoft Sysprep tools...85 Example: Installing Windows 2003 Sysprep utilities...85 Excluding hypervisor local storage and system drives from storage provisioning for VM guests...86 Creating ESX virtual machine templates...87 Checking virtual machines...88 Creating templates for Hyper-V virtual machines...89 Creating a template from a virtual machine stored on a Hyper-V host...89 Using SCVMM templates...89 Preparing images for public cloud bursting...90 Configuring Matrix infrastructure orchestration resources...90 Infrastructure orchestration console overview...92 Verifying Matrix infrastructure orchestration users...93 Configuring server pools...93 Viewing and configuring networks...97 Trunk and VLAN networks Virtual Connect tunneled trunk configuration Virtual Connect mapped trunk configuration Configuring trunk and VLAN networks Configuring trunk and VLAN networks to enable support for Hyper-V VLAN tagging Configuring software resources VM templates Enabling template assignment restriction for specific service provider level users HP Server Automation HP Cloud Services and Amazon EC2 software Creating Matrix infrastructure orchestration templates and services Using infrastructure orchestration designer Creating a template with a virtual machine Creating a service request Approving and automating deployment Configuring multi-tenancy (optional) Creating an organization Assigning users to an organization Adding resources to an organization Troubleshooting Troubleshooting tools Contents

5 Using Insight managed system setup wizard Before running the Insight managed system setup wizard Running Insight managed system setup wizard Using vseassist Use cases Running the vseassist tool Diagnostics in vseassist Windows CMS checks Managed node checks Communication checks Using System Management Homepage troubleshooting tools Running Configure or Repair Agents Using Manage Communications Checking log files Verifying the CMS configuration Synopsis Checks provided with infrastructure orchestration Service provisioning Logical server features Troubleshooting procedures Agent and communication troubleshooting Matrix OE troubleshooting Matrix infrastructure orchestration troubleshooting Logical server troubleshooting Insight Control virtual machine management troubleshooting Support and other resources Information to collect before contacting HP How to contact HP Security bulletin and alert policy for non-hp owned software components Subscription service HP authorized resellers Related information Typographic conventions Documentation feedback A Configuring vcenter server accounts vcenter Server non-administrator required discovery permissions vcenter server non-administrator required role permissions Glossary Index Contents 5

6 1 Overview The HP Matrix Operating Environment provides an integrated graphical environment for managing physical servers, logical servers, virtual machines, server blades, npartitions, virtual partitions, applications, and workloads. This document provides Matrix OE setup and installation instructions specifically in support of virtual machine management. To support physical server provisioning with Matrix OE on HP BladeSystem with Virtual Connect, install and configure a more complete Matrix OE environment with the HP Installation and Startup Service (not covered in this document). Matrix OE as configured in this guide also forms the basis of a combined private and public cloud provisioning platform. Public cloud bursting is a feature that enables enterprises to provision public and private infrastructure resources in a seamless way. Once configured as described in this guide you may optionally continue on to integrate the environment to a public cloud partner. You'll find a list of additional documentation resources, including the public cloud partner configuration, at the end of this section. This guide makes use of a typical example hardware configuration as a baseline for describing the proper process for setup and configuration. The example hardware configuration referenced throughout the guide includes a Central Management Server (CMS), optional server blades, network and storage infrastructure, virtual environment management servers, and pre-existing hypervisor hosts. Note that your hardware environment might vary significantly from these examples. The environment into which Matrix OE will be integrated may also include pre-existing server deployment platforms such as HP Server Automation or HP Insight Control server deployment. This guide assumes you have configured a single management network that provides communications to the managed elements of the environment. You may have more than one management network and need to specify the appropriate network depending on the context. However, it is not necessary for the CMS to have network access to all the same networks that are defined on your hypervisors. It is usually only necessary to reach the hypervisor s management console and optionally one management network to any virtual machines you wish to proactively manage. The process described in this guide also assumes that some infrastructure services are supplied and those connection points and references will be identified in context. The instructions in this guide require you to have knowledge of the following: Windows Server administration fundamentals Windows user account and group creation, modification, and membership VMware ESX/ESXi, vcenter Server, and Microsoft SCVMM and Hyper-V hypervisor installation and configuration Creating and managing virtual machine templates and related virtual resources Networking concepts as required by the target environment HP Matrix Operating Environment setup and installation overview The solution requires the installation and setup of the CMS and Matrix Operating Environment software, and the licensing and registration of managed hypervisor hosts. To ensure a successful installation, you must install and set up the software in a particular manner. Even if you have already performed some of the steps in this guide, review the steps to make sure you correctly installed each component. 6 Overview

7 Product names Many of the HP software products used with HP Matrix have been updated and renamed. This document reflects those new product names wherever possible. There are some instances where the old name is referenced for practical purposes. New product name HP Matrix Operating Environment HP Insight Management HP Matrix Operating Environment infrastructure orchestration HP Matrix OE visualization Previous product name HP Insight Dynamics HP Insight Software HP Insight Orchestration HP Insight Virtualization Manager Related information resources In addition to this guide, the following table lists the documentation and other information resources available for Matrix components. Table 1 Information resources Component HP BladeSystem HP Insight Management HP Systems Insight Manager HP Insight Control Document HP blade server information: Insight Management Information Library: insightmanagement/docs HP Insight Management Installation and Configuration Guide HP Insight Management Quick Installation Guide HP Insight Management Getting Started Guide HP Insight Management Installation and Upgrade Release Notes HP Insight Management Support Matrix HP Insight Management Preinstallation Worksheet HP Insight Managed System Setup Wizard Getting Started Guide Managing HP servers through firewalls with Insight Software 6.0 or greater White Paper Use the Documentation tab from the Autorun screen on HP Insight Management DVD #1 for individual documentation for each component. Systems Insight Manager Information Library: insightmanagement/sim/docs HP Systems Insight Manager User Guide HP Systems Insight Manager Release Notes HP Systems Insight Manager Installation and Configuration Guide for Microsoft Windows HP Systems Insight Manager Command Line Interface Guide Insight Control Information Library: HP Insight Control Getting Started Guide HP Insight Control Release Notes HP Insight Management Installation and Upgrade Release Notes HP Insight Management Installation and Configuration Guide HP Insight Management Quick Installation Guide HP Insight Management Support Matrix Related information resources 7

8 Table 1 Information resources (continued) Component Document HP Insight Control Virtual Machine Management User Guide HP Insight Managed System Setup Wizard Getting Started Guide HP ilo HP Matrix Operating Environment HP ilo website: HP Integrated Lights-Out Release Notes HP ProLiant Integrated Lights-Out User Guide HP Integrity ilo Operations Guide HP ProLiant Integrated Lights-Out Scripting and Command Line Guide Matrix Operating Environment Information Library: matrixoe/docs HP Matrix Operating Environment Getting Started Guide HP Matrix Operating Environment Release Notes HP Matrix Operating Environment Infrastructure Orchestration User Guide HP Capacity Advisor User Guide HP Matrix OE Visualization Manager Software with Logical Server Management User Guide Operations Orchestration HP Operations Orchestration Software Installing and Upgrading Guide HP Operations Orchestration Software Administrator's Guide HP Operations Orchestration Software Central User's Guide HP Operations Orchestration Software System Requirements Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and HP Cloud Services or Amazon EC2 Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and Savvis Federated CMS Servicing hardware components HP Matrix Operating Environment Federated CMS Overview white paper, at Services Media Library: Server Automation Integrating HP Server Automation with HP BladeSystem Matrix/Insight Dynamics whitepaper at 4AA2-1216ENW.pdf HP Matrix Operating Environment Infrastructure Orchestration User Guide available at 8 Overview

9 2 Before you begin Verify Supported Hardware and Software You must verify support for the servers you plan to manage and the hardware onto which you plan to install the Insight Management software. It is important that you read and understand the Insight Management Support Matrix. It specifies supported hardware and software for the CMS (whether a physical or virtual server) as well as details for each managed hypervisor. Insight Management also supports specific third-party hardware servers and hypervisors as listed in the support matrix. Verify or Install Hypervisors The installation and configuration of Insight Management software described in this guide integrates with your virtualized environment. You may begin the instructions without access to an existing virtualization environment. However, to provision using local virtual resources, you will need access to at least one hypervisor host environment (including its management server) before starting the discovery process. For VMware, the Matrix Operating Environment is fully functional only after the hypervisor hosts are registered with a vcenter Server. For Microsoft hypervisor hosts, registration with an SCVMM server is recommended but not required. Matrix OE requires that your hypervisors meet the requirements in the Insight Management Support Matrix. HP recommends that you install VMware hosts on HP servers using an HP provided installation (ISO) image (available from that includes updated drivers and management providers. Alternatively, Matrix OE requires the proper version HP ESXi Offline Bundle for VMware be installed on those hosts. IMPORTANT: When the HP Network Configuration Utility (NCU) is used with Hyper-V for NIC teaming, the installation order of NCU and Hyper-V is critical. The Hyper-V role must be installed first and then the HP NCU. A common error is to deploy the OS and the SPP (which includes the NCU) and later add the Hyper-V role. This will result in an unstable network stack on the server. If a Hyper-V server has been built incorrectly, the only reliable remedy is to reinstall the complete OS stack in the correct way. HP strongly recommends that Microsoft and Linux hosts running on HP servers have the proper HP Service Pack for ProLiant (SPP) installed. Compiling the documentation and media Matrix Operating Environment component documentation, while delivered individually and in various formats, works as a system. These documents provide important decision-making steps for configuration. To identify and locate the latest documentation for Matrix Operating Environment products, see Table 1 (page 7). Review the published release notes in detail, particularly any updated prerequisites or additional required updates or patches. Check for relevant Customer Advisories on the HP Business Support Center before beginning the installation. You may add the HP Insight Management Software and HP Matrix Operating Environment Software to your subscribed product list or sign up for Subscriber's Choice at Verify Supported Hardware and Software 9

10 Gather all prerequisite Matrix Operating Environment required software media and verify correct versions of media prior to installation. Make sure that you have access to appropriate media for all of the listed software components and any necessary prerequisites. This includes: HP Service Pack for ProLiant (SPP) DVD (includes HP ProLiant Support Pack) from HP Insight Management DVD (two DVD set) or the latest Insight Management DVD ISO images, including the Matrix Operating Environment, from Microsoft Internet Explorer or Mozilla Firefox. See the HP Insight Management Support Matrix at for browser version support. Insight Management licenses for all software products that require them. You can find these license keys on the license entitlement certificate. The license entitlement certificate directs you to the HP License Key Delivery Service website ( which contains the information you need to redeem your license activation keys. You cannot apply an Insight Control license to a non HP server. On non HP servers, Insight Control virtual machine management is licensed through a separate Matrix OE license. For more information, see the HP Insight Management Getting Started Guide Prerequisite software: Adobe Flash Player v11 available at distribution3.html Microsoft.NET Framework 3.5 SP1 (read the installation instructions included later in this guide) Required Microsoft hotfix for Windows 2008 R2 or R2 SP1: NOTE: The Windows 2008 R2 or R2SP hotfix does not come with Windows updates and needs to be installed manually. Collecting network connection information Collect the network names and addresses for all the planned components of the Matrix system, including servers, management processors, and modules in the environment. For more information, as well as checklists and templates to help gather this data, see the HP Insight Management Preinstallation Worksheet available at NOTE: Insight Management software does not support certain characters in a CMS name. When choosing a CMS name, only use alphanumeric characters (a-z, 0-9) and a hyphen (-). The hostname should not start with a digit or a hyphen, and must not end with a hyphen. Limit the name to less than 15 characters. Collecting management credentials Create or obtain the following credentials for installing and configuring the solution: An administrator account to use for the installation and ongoing maintenance of the Insight Management Software. An account to use for services created during installation that will run in the background this is usually the same as the installation account. The credentials for any Onboard Administrator or Virtual Connect modules to be managed by the installed CMS 10 Before you begin

11 Administrative credentials for: Virtual environment management servers such as VMware vcenter Server or Microsoft SCVMM servers Managed hypervisor hosts Any virtual machines that you intend to actively manage If you intend to use a remote SQL Server database rather than the provided SQL Server Express, you will need credentials to access the remote database. Planning and design for public cloud bursting Public cloud bursting is a feature that enables enterprises to provision public and private infrastructure resources in a seamless way. Matrix OE supports bursting to: HP Cloud Services ( Amazon Elastic Compute Cloud (EC2) Savvis Symphony Virtual Private Data Center Matrix OE bursting capabilities share many of the same processes as local private resources: The same Matrix OE service template designer, operations console, and self-service portal is used in conjunction with the cloud provider-specific administrative interfaces. There are minor changes to the appearance of the Matrix OE user interfaces based on the configuration of the CMS for your cloud provider. You design Matrix OE service templates that may contain any mix of private-cloud or public-cloud resources. For HPCS and EC2, the cloud software inventory includes images filtered directly from the provider. In the case of Savvis, local software choices are shown as proxies for and mapped to images available on Savvis. Some cloud providers do not provide visibility or control of a server s network configuration. In these cases, the subnet in the Matrix OE resource inventory cannot be used to control sophisticated customization. The request, approval, and deployment process is the same for cloud-based service requests as for resources on the premises. Each supported bursting destination brings unique configuration processes and networking constraints. Some partners and destinations require public internet access and others require additional VPN access. Complete the configuration steps for HP Cloud Services, Savvis Symphony VPDC, or Amazon EC2 after you have finished the steps in this guide. For instructions on configuring these destinations, see Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and HP Cloud Services or Amazon EC2 and Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and Savvis. Planning and design for public cloud bursting 11

12 3 Preparing the Central Management Server Finalizing the Windows installation on the CMS server This section describes the required steps you must perform after installing Microsoft Windows to prepare a server to install Insight Management software. If you plan for your CMS to be member of a Microsoft Active Directory domain, join the domain prior to installing any Insight Management software. Also consider that any future migration from a standalone CMS to a cluster CMS will be easier if the standalone CMS and the future cluster CMS are members of the same Windows domain. However, starting in Matrix 7.0, data migration is supported between a workgroup CMS and a domain-based (cluster) CMS. Data migration between different Windows domains is not supported. A cluster CMS is always domain-based. A standalone CMS may be either workgroup or domain-based. Several key attributes of the CMS operating system can be modified after Insight Management is installed using the MXRECONFIG command in the CMS Reconfigure tool. For information on how to use the CMS Reconfigure Tool, see thehp Systems Insight Manager User Guide available at However, it is a best practice to verify that the attributes identified below are correct before installation: Hostname The IP address associated with the hostname Full name or domain, including FQDN Any DNS entries corresponding to the hostname and domain Follow these steps to finish the Windows networking configuration and data execution prevention settings on the CMS. 1. Configure the Computer name and DNS suffix for the CMS. While setting the name and workgroup or domain, also set the FQDN of the CMS. a. Browse to Server Manager. b. Click Change system properties in the server summary screen. c. Select the Computer Name tab. d. Click Change to change the server name. e. Click More and fill in the primary DNS suffix for the CMS. f. Clear the Change primary DNS suffix when domain membership changes checkbox. Once Insight Management software is installed, this cannot change even if the domain is changed. 2. Set the domain name and reboot (or wait until finished with the next step.) 12 Preparing the Central Management Server

13 3. If Data Execution Prevention (DEP) is enabled for all processes or except those explicitly listed, then change this configuration to be enabled for a limited system binaries and programs (OptIn) to install HP Insight Management. After installation, you could either keep this configuration in OptIn mode, or change it to OptOut mode and add Java.exe to the OptOut list. To change the DEP policy on Windows 2008 / Windows Server 2008 R2/Windows Server 2012: a. On the Control Panel System settings, click the Advanced system settings link. b. On the System Properties dialog box, click the Advanced tab. c. Click the Settings button in the Performance group. This displays the Performance Options dialog box. d. Choose the Data Execution Prevention tab. e. Select Turn on DEP for essential Windows programs and services only. f. Click OK to close the Performance Options window and again to close the System Properties window. g. Reboot the system to enable the new setting. Finalizing the Windows installation on the CMS server 13

14 Installing additional Windows components For Windows 2008: 1. Go to Server Manager (Start Menu Administrative Tools Server Manager). 2. Disable Internet Explorer Enhanced Security. Insight Management software browser-based operations are significantly easier to use when this is disabled. a. Select Configure IE ESC on the Server Manager Server Summary page. b. Turn off Internet Explorer Enhanced Security for both administrators and users, and click OK. 14 Preparing the Central Management Server

15 3. Add and configure the Application Server role: a. In the left pane of Server Manager, click Features, and then in the right pane click Add Features. b. Depending on your OS, do one of the following: for this OS... Windows 2008 R2 and R2 SP1 Windows 2008 SP2 do this Expand.NET Framework Features 2. Select only.net Framework Expand.NET Framework 3.0 Features 2. Select only.net Framework 3.0. NOTE: For Windows versions prior to Windows Server 2008 R2, download and install.net Framework 3.5 SP1 from the Microsoft website or install.net Framework using Windows Update. c. Scroll down and select SNMP Services if it has not already been selected. d. Click Next, and then click Install. For Windows 2012: 1. Browse to Server Manager (Start Menu Server Manager) Installing additional Windows components 15

16 2. Disable Internet Explorer Enhanced Security. Insight Management software browser-based operations are significantly easier to use when this is disabled. a. Click IE Enhanced Security Configuration on the Server Manager's Server Summary page. b. Select Off for both Administrators and Users In the Internet Explorer Enhanced Security Configuration screen and click OK. 16 Preparing the Central Management Server

17 3. Add and configure the Application Server role: a. Click Manage Add Roles and Features in the top menu of Server Manager. b. Click Next and the installation type screen appears. c. Select Role-based or feature-based installation and click Next. d. In the destination server, select the server that you are configuring in the server pool list and click Next. e. Click Next in the Roles screen. f. Select the following features in the Features screen: SNMP Service (also add the required features).net Framework 3.5 User Interfaces and Infrastructure (Desktop Experience item) g. Click Next. h. Click Specify an alternative source path in the Confirm installation selections screen. i. Access the alternate source path by opening the Window 2012 ISO file and pointing to a drive such as E:\sources\sxs. Click Next. Installing additional Windows components 17

18 Configuring SNMP and UAC For Windows 2008 and 2012: 1. Configure SNMP community names and traps. a. Select Start Menu Administrative Tools Services. b. Right-click SNMP Service and then select Properties. c. Select the Security tab. d. In the Accepted community names section, click Add. i. Select READ ONLY permission level for the community string in the Community Rights menu. ii. In the Community Name box, enter public or a specified case-sensitive community name. iii. Click Add. e. In the Accepted community names section, click Add. i. Select READ WRITE permission level for the community string in the Community Rights menu. ii. In the Community Name box, enter private or a specified case-sensitive community name. iii. Click Add. f. Under the Accept SNMP packets from these hosts, verify that localhost is listed. If it is missing: i. Enter localhost and click Add. ii. Confirm that localhost has been added under Accept SNMP packets from these hosts. g. Select the Traps tab. i. In the Community Name box, enter public or a specific case-sensitive community name. ii. Click Add to list. iii. Under Trap destinations, click Add. iv. For Hostname enter the primary IP address of the CMS, and click Add. h. Click OK to exit and apply. For Windows 2008: 18 Preparing the Central Management Server

19 2. Turn off the User Account Control. NOTE: You will need to restart Windows after making this change. a. For Windows 2008 SP2: i. Click Start and then click Control Panel. ii. In Control Panel, click User Accounts. iii. In the User Accounts window, click Turn User Account Control on or off. iv. Clear the User Account Control (UAC) to help protect your computer checkbox. v. Click OK. vi. Click Restart Now. b. For Windows Server 2008 R2 or Windows 2008 R2 SP1: i. Click Start Control Panel. ii. In Control Panel, if your view is set to display by Category, click System and Security and then click Change User Account Control Settings. iii. Drag the slider to Never notify. iv. Click OK. v. Click Restart Now. For Windows Server 2008 R2, Windows 2008 R2 SP1 and Windows 2012: 1. Click Start Control Panel 2. If your view is set to display by Category in the Control Panel, click System and Security and then click Change User Account Control Settings. 3. Drag the slider to Never notify. Configuring SNMP and UAC 19

20 4. Click OK. 5. To disable one Security Policy, run secpol.msc. 6. Expand Local Policies. 7. Click Security Options. 8. Set policy Account Control: Run all administrators in Admin Approval Mode to Disabled. 9. Click Restart Now. Installing an SPP For a CMS running on an HP server, you must install a compatible HP Service Pack for ProLiant (SPP) and finish any network configuration that is required to communicate with your hypervisor hosts and other managed nodes. Install both firmware updates and the online components for Windows using the HP Smart Update Manager. The installation of the SPP online components for Windows requires the SNMP Services feature. If your CMS is running in a virtual machine, there is no need to install the SPP. The SPP does not run on a guest operating system environment regardless of the hypervisor. Configuring the management networks To configure the management networks: 20 Preparing the Central Management Server

21 1. If you are using redundant networks on the CMS, use the HP Network Configuration Utility (NCU) to team them now (if you haven't already). If you plan to team your networks, you must complete that configuration prior to setting the attributes or network order for each network. NOTE: In a Flex-10 NIC environment, where all potential NICs are enumerated and visible to the Windows OS, the HP NCU is also useful in mapping the NICs to bays and ports. You can use this utility to identify which network connections can be disabled in Windows (this prevents unnecessary reports of a down network connection). 2. Select one network on the CMS to be primary. Usually this is the network that responds with a matching FQDN used when filling in the primary DNS suffix for the CMS in Configure Computer name and DNS suffix (page 12). Typically this should be the network used to communicate with hypervisors and management modules. 3. Configure the properties of each network connection as appropriate for your environment: a. Set the IP address, subnet mask, and the default gateway (if necessary). b. Set the DNS server IP address. c. In Advanced TCP/IP Settings, set the DNS suffix for this connection. d. On all except the primary network, you may want to clear the Register this connection s addresses in DNS and the Use this connection s DNS suffix in DNS registration checkboxes to prevent managed nodes from seeing multiple IP addresses and names for the CMS. 4. Prioritize the Network Order to prefer the primary network. If using NIC teaming, then you would select the connection that represents the team to be primary. a. Open the Network and Sharing Center. b. Click Change Adapter Setting (for Windows Server 2008 R2 or newer) or click Manage Network Connections (for Windows Server 2008 SP2.) c. Select Advanced Settings from the Advanced menu. (For Windows Server 2008, if the Advanced menu is not visible, press the Alt key to make the menu appear.) d. In the Connections box, highlight the primary network and click the up arrow on the right to move it all the way to the top. e. Click OK to close Advanced Settings. NOTE: The selection of the primary network has a significant effect on the behavior of HP SIM. Whenever possible, you should set the primary network to the network on which the CMS communicates to the managed nodes. In some network configurations, it is also necessary to lower the Interface Metric on the network's Advanced TCP/IP Settings properties dialog. 5. After a primary network has been configured for the CMS, confirm that forward and reverse lookups of the short and fully qualified name for the CMS behave correctly. All DNS lookups must resolve correctly before proceeding to the next chapter. Configuring firewalls The Insight Management software products depend on network connectivity between the management services and between the management services and the managed nodes. Host-based firewalls and port filtering solutions on the CMS and other management stations, on the managed nodes as well as intervening network based firewall products, can result in loss of management connectivity. Windows Server 2008, by default, enables its host based and blocks ports used by HP SIM Configure and Repair Agents tasks. Corporate security standards might also block management protocols, such as those used by Insight Control server deployment. HP recommends customers and service professionals familiarize themselves with Managing HP servers through firewalls with Insight Management software, available at NOTE: HP recommends that you temporarily turn off all of the Windows firewalls (Public, Private, and Domain). Configuring firewalls 21

22 To turn off all Windows firewalls for Windows 2008: 1. Open Server Manager and select Go to Windows Firewall. 2. Check the status of your firewall in the Overview section. If any firewalls are enabled, select Windows Firewall Properties. 22 Preparing the Central Management Server

23 3. If any profiles show that the firewall is on, click Windows Firewall Properties and then: a. In the Windows Firewall with Advanced Security Properties window, select the tab that corresponds with the firewalled profile. b. Change the firewall state to Off and then click Apply. c. Repeat the steps above for any profile that is on. 4. Click OK when finished. To turn off all Windows firewalls for Windows 2012: 1. Open Server Manager select Logical Server and click on the Windows Firewall link. 2. Browse to Server Manager (Start Menu Server Manager). 3. Click Windows Firewall on the Server Manager Server Summary page. Configuring firewalls 23

24 4. Click Turn Windows Firewall on or off. 5. Select Turn off Windows Firewall (not recommended) for both Private and Public network settings. 6. Click OK. Installing Windows updates Ensure the CMS date, time, and time zone are set correctly. 1. If your CMS is part of a Windows domain, it receives the correct time from the domain controller. Otherwise, you should specify an appropriate time source in the Control Panel under the Date and Time properties for Internet Time. 2. Update Windows and other software components using your standard IT practices (which may include use of Microsoft Windows Update and similar services). The CMS date and time 24 Preparing the Central Management Server

25 must be set correctly before executing Windows Update, otherwise the updates might not be allowed. CAUTION: Include only compatible service packs or updates. Check the HP Insight Management Support Matrix for more information at insightmanagement/docs. NOTE: If it has not already been installed using Windows Update and you are running a Windows 2008 R2 CMS, install the following Microsoft hotfix to prevent kernel sockets leaks: 3. HP strongly recommends that you disable automatic installation of Windows updates to reduce the possibility of introducing an incompatible patch or service pack. 4. HP suggests that your disable the automatic password expiration for the account used to install the Insight Management software and the account used for background services. If you need to change the password for these accounts, see Reconfiguring the CMS password in the HP Insight Control 7.2 Getting Started Guide. 5. Install any required convenience utilities, such as ISO tools, PuTTY, or HyperTerminal. Note that SSH and SCP will be included with the later installation of Matrix OE. Installing the remaining Insight Management software dependencies Insight Management Advisor, included on the HP Insight Management DVD, analyzes and tests your software and CMS environment to ensure that it meets installation criteria and gives steps for correcting identified problems. HP recommends that you run the Insight Management Advisor before you begin the installation or upgrade process. The test results help you identify target server issues or deficiencies that would cause conflicts with HP Systems Insight Manager and other integrated software products. You can run a complete suite of tests or test for specific software product issues. You can run the advisor at any time prior to the software installation, however detailed instructions on the specific selections required for this configuration are given in Chapter 4. Install the remaining software required to support Insight Management: Adobe Flash Player 11.x NOTE: For Windows 2008 and earlier: If you have a different version of Adobe Flash Player already installed, you will need to uninstall it and install the required version. Adobe Flash Player cannot be uninstalled using the Control Panel, use the uninstaller available from flash-player/kb/uninstall-flash-player-windows.html. For Windows 2012: Windows 2012 comes with Adobe Flash 11.x pre-installed after enabling the Desktop Experience Feature. Database installation The default Insight Management software installation, installs and uses the supplied Microsoft SQL Server Express Edition. If you are using SQL Express 2008 R2 from the DVD, you will also need.net 3.5 SP1 as installed earlier. Due to the limitations of Microsoft SQL Server Express Edition, HP recommends using Microsoft SQL Server Standard or Enterprise for medium and large environments. Installing the remaining Insight Management software dependencies 25

26 Additionally, for large environments, it is recommended that Microsoft SQL Server be deployed on a separate server. If you plan to use a separate Microsoft SQL Server, you need to install and prepare your database server environment before you proceed to the following section. NOTE: Skip this section if you plan to install SQL Express, included with HP Insight Management software. If you plan to use a separate Microsoft SQL Server, configure the model recovery type to Simple prior to the Insight Management installation. You will not have to modify the database recovery model for multiple components after the installation. To set the database recovery model: 1. Open SQL Server Management Studio and connect to the appropriate instance of the Microsoft SQL Server Database Engine. 2. In Object Explorer, click the server name to expand the server tree. 3. Expand Databases, and right-click the model database, and then click Properties to open the Database Properties dialog box. 4. In the Select a Page pane, click Options. 5. The current recovery model is displayed in the Recovery model list box. 6. Change the recovery model to Simple. 7. Repeat the instructions from Step 3 to Step 6for all other databases, including System databases. Configuring and tuning Microsoft SQL Server is beyond the scope of this guide. However, consider the following guidelines: If Microsoft SQL Server Standard or Enterprise Edition is installed on the CMS, the Maximum server memory used by SQL Server should be configured to be no larger than (PhysicalMemory minus 6 GB) / 2. For example, if the CMS has 32 GB of DRAM, then SQL Server should be configured to use no more than 13 GB. To configure the maximum server memory: 1. Open SQL Server management studio. 2. Right click SQL Server instance. 3. Select Properties. 4. Select Memory in the Server Properties dialog box. If Microsoft SQL Server Standard or Enterprise Edition is installed on a separate system, the Maximum server memory used by SQL Server should be configured to be no larger than (PhysicalMemory-6GB) Whether Microsoft SQL Server Standard or Enterprise Edition is installed on the CMS or on a separate server, then Maximum Degrees of Parallelism (MAXDOP) should be set as follows: For servers with 16 or fewer cores, set MAXDOP to 1. For servers with more than 16 cores, set MAXDOP to Open SQL Server Management Studio. 2. Right-click the SQL Server instance. 3. Select Properties. 4. Select Advanced in the Server Properties dialog box. If you plan to use a separate Microsoft SQL Server, you need to configure your SQL server environment to use static TCP/IP ports. To configure TCP/IP ports: 1. Open SQL Server Configuration manager and expand SQL Server Network Configuration. 26 Preparing the Central Management Server

27 2. Select Protocols for <your SQL server instance>. 3. In the right-hand screen, right-click TCP/IP and select Properties. 4. In the TCP/IP Properties window, select the IP Addresses tab. 5. Scroll to the bottom of the IP list. 6. Under IPAll a. Set TCP Dynamic Ports to blank (delete the 0). b. Set TCP Port to appropriate port (default is 1433) 7. Click OK. 8. Close SQL Server Configuration Manager. 9. Restart SQL services. Installing the remaining Insight Management software dependencies 27

28 4 Installing Insight Management software on the CMS This chapter describes the steps for installing HP Insight Management software on the CMS. Installing and configuring the CMS NOTE: As a best practice, it is recommended that an installation and service account be created to use when installing Insight Management software. IMPORTANT: Be sure any antivirus software has been disabled prior to installation of Insight Management software. Otherwise, the installation can take an extraordinarily long time or the installation might fail. To install the required software on the CMS: 1. Check the current HP Insight Management Installation and Upgrade Release Notes for updated pre-installation steps. Pay attention to required component updates, product patches, or newly released dependent or prerequisite products. 2. Connect to the CMS using either the ilo Remote Console or Microsoft Remote Desktop. If you use Remote Desktop, make sure to connect using the mstsc/console or /admin switch (depending on your client version). mstsc /admin /v: NOTE: Before proceeding, make sure that the system time and time zone are set correctly. 3. Mount the HP Insight Management DVD #1. If you are using an ISO utility, make sure it is set to automatically remount the ISO after a reboot; otherwise, you have to manually remount the image. If the main license agreement does not automatically launch, use AutoPlay to start the installation. Agree to the main license agreement. 4. Click Run Insight Management Advisor to confirm the CMS has met all the prerequisites. Insight Management Advisor should always be run before CMS installation to identify problems that may interfere with the installation. The Insight Management Advisor Welcome screen appears. 28 Installing Insight Management software on the CMS

29 5. For this specific configuration, you must click Filter... on the Insight Management Advisor Welcome screen, and then click Customize... on the Filter Selection screen. Select only the following components, and then click OK: HP Systems Insight Manager HP Insight Control licensing and reports HP Insight Control virtual machine management HP Matrix Operating Environment HP Matrix infrastructure orchestration HP Insight managed system setup wizard WMI Mapper Installing and configuring the CMS 29

30 NOTE: With these selections, the installer will check for a remote database. If none is detected, this warning appears: If you are installing a local SQL Server database, click No. Otherwise, click Yes. 6. Click Run Now to test all of the selected components. 7. After the tests complete, the results will be displayed and any issues will be indicated. To resolve issues, click on the test names to view a help file that explains the test, possible issues found, and ways to resolve the issues. You can execute the Insight Management Advisor as many times as necessary. 8. The Insight Management Advisor should return no issues found. Click Close to exit Insight Management Advisor and return to the HP Insight Management DVD welcome screen. NOTE: The Advisor may return a major issue associated with the Windows Update Check. This issue can be ignored if your CMS is intentionally isolated from the Internet. Click Close to exit Insight Management Advisor and return to the HP Insight Management DVD welcome screen. 9. Click Run Integrated Installer to launch the HP Insight Management Installer. Review the installation notes and click Yes to continue with the installation. 10. Leave all the selections unchecked and click Customize. 30 Installing Insight Management software on the CMS

31 11. On the Select components for install or upgrade screen, select Customize Insight Management component selection below to get the list of products available for installation. To begin, select all the components using the Check/uncheck all box. NOTE: You will be unable to select only the components required here if you begin with all the selections cleared. Installing and configuring the CMS 31

32 Clear all of the items except the following: WMI Mapper HP Systems Insight Manager HP Insight managed system setup wizard HP Insight Control virtual machine management HP Insight mxsync Utility HP Matrix Operating Environment capacity planning, configuration and workload management and HP Insight Capacity Advisor Consolidation software HP Matrix infrastructure orchestration HP Insight Control licensing and reports HP Insight Management Advisor NOTE: If you are using remote server deployment, do not select HP Insight Control server deployment (install locally or reuse remote installation). A remote server deployment must be configured only after the integrated installer completes. If the HP System Management Homepage was installed as part of the SPP online components, you cannot clear its selection. Leave it selected. Clearing some of the selected items will cause warnings to appear click OK for each one. Click Next when finished customizing the product installation list. The notices and warnings that appear are expected, and you can safely ignore them. 12. The HP Insight Management DVD #2 Selection screen appears when you are installing or upgrading components that reside on DVD #2. The items to be installed from DVD #2 appear on the screen. Make sure you choose the appropriate mechanism for presenting DVD #2 that corresponds to the drive or utility you are using. Click Next. 32 Installing Insight Management software on the CMS

33 13. The Check for prerequisites screen summarizes the items required for installation (and that were verified using the Insight Management Advisor). Click Next to proceed with the installation. 14. On the Installation directory screen, enter the directory to install the selected products. Use the default directory, unless otherwise required, and answer the installer configuration questions based on the components selected. Click Next to continue the installation. 15. Enter the credential information that Insight Management uses as sign-in credentials for the services it creates. Click Next. Installing and configuring the CMS 33

34 16. HP Insight Management searches for an existing database on the local system. If one is detected, Use Existing Microsoft SQL Server 2008 R2 SP1 or later is selected and the option to create a new database is disabled. Use the default database or enter the credentials for a remote database. If you are not using an existing database select Install Microsoft SQL Server 2008 Express R2 and enter the required credential information. Click Next. NOTE: If you are installing multiple CMSs that will share a common remote SQL server, you need to pick a unique database instance for each CMS. 34 Installing Insight Management software on the CMS

35 17. Automatic login is available for Insight Management installation functions that require a reboot. To enable auto-login after a reboot, select the Enable automatic sign-in checkbox and enter the administrator credentials. Click Next. 18. If the CMS requires an HTTP proxy server to reach the external internet, select the I use an HTTP proxy server checkbox and enter the proxy host and port information. If authentication is required to access the proxy server, select My proxy requires authentication and enter the proxy credential information. Click Next. Installing and configuring the CMS 35

36 19. Specify the port to be used for WMI data collection, discovery, and identification. Select Use default port. If you cannot use the default port, select Specify HTTPS port and identify the port. Click Next. 20. Click Change the product title to personalize the title or use the default values. Click Next. 36 Installing Insight Management software on the CMS

37 21. Matrix infrastructure orchestration requires a functional SMTP server configuration to send notifications and action requests. You can enter that information now during the installation or later during the configuration steps. If you choose to enter the SMTP information now, the SMTP server might be configured to require authentication. If authentication is required you should fill in the username and password fields, otherwise leave them blank. NOTE: If the SMTP server is not reachable during installation, or the credentials that you specified are not valid, then valid notification and server information must be entered manually in as described in Chapter 11: Configuring Matrix infrastructure orchestration. Click Next. Installing and configuring the CMS 37

38 22. Select the appropriate radio button for Matrix infrastructure orchestration deployment server configuration. If you have a remote physical deployment server configured, specify it now. Otherwise choose No deployment application. NOTE: For HP Server Automation, select Server Automation and then enter the credentials in the Remote Server Automation server information fields. Deployment servers must be up and accessible by the CMS during the installation process, or you will need to configure the settings for server automation manually after the installation completes. 38 Installing Insight Management software on the CMS

39 Click Next. NOTE: If you have a remote HP Insight Control server deployment server, configure that communication after the installation completes. See Chapter 8: Configuring integration with deployment servers. 23. An Installation summary screen shows all of the software components scheduled to be installed. Click Install to proceed with installation of components, and installation notes appear. Installing and configuring the CMS 39

40 Click Yes to continue the installation. A reboot will occur partway through the installation of the components. The installation continues automatically. NOTE: The system will normally auto-login and continue installing after the reboot unless that feature was not enabled in a previous step. Manual login will always be required to view the installation results. If you originally connected to the CMS using Microsoft Remote Desktop Connection, remember to reconnect using the mstsc /console or /admin switch (depending on your client version). 24. After installation is complete, review the Installation status screen to verify that all components were installed successfully. If there were errors, go to Installation errors (page 42). 40 Installing Insight Management software on the CMS

41 25. Click Next to bring up the Installation finished screen to confirm that all components were installed successfully. Click Close to exit the Insight Management Installer. The Insight Management software installation is complete. 26. Re-enable User Account Control (UAC) in the CMS. Installing and configuring the CMS 41

42 Installation errors If there were errors during the installation, they are indicated on the Installation Status screen. Click Next to bring up the Installation finished with errors! screen. 1. Click View the installation log file to review the errors. 2. Click Close to exit the Insight Management Installer. 3. Resolve the errors and rerun the Insight Management Installer to install the components that encountered the errors. NOTE: You may optionally run the Insight Management Advisor after the installation to verify the post-install status of the components. The post installation Insight Management Advisor might list a warning: The SQL browser service "SQLBrowser" is not running. To resolve this message, go to Windows Services to start the SQL Server Browser service. Installing Matrix OE patches HP might periodically release required updates or hotfixes. Before proceeding, visit the Matrix OE website to download and install any relevant updates. Such updates contain detailed instructions regarding their installation. Post-release updates are located on the Matrix OE website at NOTE: You will notice, from this point onward, that an internet browser session that opens a secure page on the CMS produces a security warning, such as "There is a problem with web site's security certificate." This is normal behavior for a self-signed web site certificate generated on a newly installed server. You can register the certificate in question with a locally trusted Certificate Authority or choose to trust the certificate implicitly. These operations are browser and site specific. 42 Installing Insight Management software on the CMS

43 Setting the Matrix Operating Environment home page You must replace the HP SIM home page with the Matrix Operating Environment home page on the CMS. In the following instructions, all path names reference C:\Program Files\HP\Systems Insight Manager\hpwebadmin\webapps\ROOT\mxportal\home. If you have installed to a different directory, make sure to replace C:\Program Files in the above path with the appropriate install directory. 1. Rename intro.jsp to intro_original.jsp. 2. Copy matrixhome.jsp to intro.jsp. 3. Delete the old class file (it will be recreated when you view the new page) C:\Program Files\HP\Systems Insight Manager\jboss\server\hpsim\work\jboss.web\ localhost\_\org\apache\jsp\mxportal\home\intro_jsp.class. 4. To view the changes, launch HP SIM and validate the home page and banner changes. NOTE: page." This home page displays as long as Options Home Page Settings is set to "Introductory Setting the Matrix Operating Environment home page 43

44 Tuning the Matrix Operating Environment for large scale production environments In the Matrix OE environment, if you presently have or anticipate more than 1000 managed nodes, changing the default configuration values for some software components can improve the performance of those components. Managed nodes include both physical and virtual resources. Increasing JVM heap size To change the JVM heap size: 1. Edit the following files to change the indicated parameter settings. Virtual machine management Configuration file name Parameter <MOE_INSTALL_DIR>\Insight Control virtual machine management\bin\windows\hpvmmsvc.conf wrapper.java.maxmemory=2048 Infrastructure orchestration Configuration file name Parameter <MOE_INSTALL_DIR>\Matrix infrastructure orchestration\hpio.conf wrapper.java.maxmemory=2048 HP Virtual Server Environment logical server administration (LSA) Configuration file name Parameter <MOE_INSTALL_DIR>\Virtual Server Environment\conf\lsa\hp_lsa_service.conf wrapper.java.maxmemory=2048 wrapper.java.additional.11=-xx:maxpermsize=128m NOTE: When modifying the LSA service configuration file wrapper.java.additional settings by creating a wrapper.additional.<n> entry, the <n> value must be unique. Take note of the lines that are in use and be sure to leave them intact. Lines that are commented out (#) are available for use, but it s possible that by un-commenting a wrapper.java.additional.<n> line you might activate an already existing setting of the same name. Preserve the sequential numbering of the wrapper.java.additional statements to avoid conflicts. HP strongly recommends that a backup is created of all files prior to modification. 2. Restart affected services on the CMS. Editing the above files affects several running services on the CMS. Restart the following services on the CMS: HP Insight Control virtual machine management HP Logical Server Automation HP Matrix infrastructure orchestration You may wait to restart this service if you intend to modify the ESX memory oversubscription. 44 Installing Insight Management software on the CMS

45 Increasing timeout value for virtual logical servers On activating or deactivating a large number of logical servers on Hyper-V hosts, there is a possibility that one or more fail with an error similar to the following: Task for Logical Server xxxxxx has failed. Job yyyyyyy has exceeded its timeout value of 30 minutes. Marking the job as failed. The situation occurs due to excessive load on a particular Hyper-V host at a particular point in time. To change the value of the virtual logical server, edit the following files in Matrix infrastructure orchestration to change the indicated parameter settings: Configuration file name Parameter <MOE_INSTALL_DIR>\Matrix infrastructure orchestration\conf\hpio.properties timeout.deactivate.virtual.logicalserver=60 timeout.resume.virtual.logicalserver=60 Configuring ESX memory oversubscription When Matrix infrastructure orchestration is used to provision services with ESX virtual machines, by default it uses memory oversubscription techniques to allow a larger number of virtual machines to be provisioned to an ESX host. The ESX virtual machines created by IO do not use memory reservation, and IO has a low requirement for free memory in the ESX host when it checks if a virtual machine fits in a specific host. (The default value is 2% of the virtual machine memory.) For example, if a service contains a virtual machine that requires 4GB of RAM, IO requires a VM Host to have approximately 82MB of available memory (2% of 4GB). Therefore, any VM Host with at least 82MB of available memory passes the memory check in the allocation phase of service provisioning. This strategy allows a larger number of virtual machines to be provisioned to an ESX host, but in some situations it might result in degradation of the virtual machine performance. This can happen when there are too many virtual machines in a specific VM Host, and the VM Host starts swapping the host memory to disk. If a more conservative memory oversubscription approach is desired, IO can be configured to use a more restrictive check of the available memory in the ESX host before provisioning a virtual machine. Increasing this configuration to 50% allows IO to be more conservative when provisioning ESX virtual machines, while still allowing some level of memory oversubscription. To change this configuration: 1. Edit hpio.properties in the default location at..\program Files\HP\Matrix infrastructure orchestration\conf\. 2. Locate the property esx.vm.requested.memory.max.percent and change the property to esx.vm.requested.memory.max.percent= Restart the Matrix infrastructure orchestration service and the new configuration will take effect. Changing this configuration does not affect services already provisioned. Configuring Microsoft SQL Server NOTE: Skip this section if you installed SQL Express, included with HP Insight Management software. Configuring Microsoft SQL Server 45

46 When using Microsoft SQL Server Standard or Enterprise Edition, verify that the database recovery model is set to Simple for each of the Insight Management software databases. This reduces the amount of database disk space required for the transaction log. To verify the database recovery model: 1. Open SQL Server Management Studio and connect to the appropriate instance of the Microsoft SQL Server Database Engine. 2. In Object Explorer, click the server name to expand the server tree. 3. Expand Databases, and, for each database (express, gwlm, hpio, Insight_v50_0_*, oo ), repeat steps a e below. a. Right-click the database, and then click Properties to open the Database Properties dialog box. b. In the Select a Page pane, click Options. c. The current recovery model is displayed in the Recovery model list box. d. Verify that the recovery model is set to Simple. e. Click OK. 46 Installing Insight Management software on the CMS

47 5 Configuring the CMS Setting Matrix Operating Environment role authorization Matrix infrastructure orchestration contains two levels of resource definition and user access, Service Provider and Organization. This section describes the process of customizing user and administrative authorizations at the Service Provider level. For instructions on configuring resources and users at the Organization level see the whitepaper Multi-Tenancy in HP Matrix Operating Environment Infrastructure Orchestration. Role authorization overview There are two main administrative roles defined in Matrix OE. Senior administrators: The user can modify user authorizations, apply licenses to systems, or perform other actions that require CMS Security settings. Matrix infrastructure orchestration administrators: The user can manager Matrix OE resources and service provider-level services. If VCEM is installed, the user has access to VCEM in a read-only mode. The steps described are based on configuring authorizations based on Windows user groups. While authorizations can be configured based on individual users, it is much simpler to manage authorizations when performed at a group level. In Senior Administrators (page 47), a Senior Administrator group called Administrators is created in Matrix OE. By default, Matrix OE has only a user, not a group, called Administrators. By default, Matrix OE has only an Administrator user and no Administrators group. After the group is created, toolboxes that represent capabilities are authorized for use by the Administrators group. Senior Administrators Creating a Senior Administrators Users Group Perform the following steps to configure the Windows Administrators group to have authorizations as Senior Administrator. 1. Login to HP SIM using the installation account or another account that has CMS Security authorization. 2. Select Options Security Users and Authorizations Click the Users tab. 4. Click New Group. 5. Enter the Group name as Administrators (this can be any local or domain group). 6. Enter the Domain as either the Active Directory domain or the local computer name. 7. From the Copy all authorizations of this user or [template] selection, choose [administrator-template]. 8. Make sure the CMS security access checkbox is checked. Setting Matrix Operating Environment role authorization 47

48 9. Click OK. The users group should be added as shown in the following screen. Verifying Authorizations As a result of copying authorizations from the administrator template, the new user group should have role authorizations correctly defined. To verify the authorizations: 1. Click the Authorizations tab. 2. In the Authorization for list, select user group 3. In the Select name list, select the new Administrators group that you just created. 48 Configuring the CMS

49 4. Verify the role authorizations for each table line item. Modifying authorization for Matrix infrastructure orchestration Administrators 1. On the Authorizations tab, select the user group HPIO_Administrators. 2. Click New to add new authorizations. 3. Select User Groups from the Select field. 4. Select the <computer or domain name>\hpio_administrators group checkbox. 5. Select the Manually Assign Toolbox and system/system group authorizations. 6. Choose from the following toolboxes to add default authorizations in the Select Toolbox(es) field: Capacity Advisor Full Rights HPIC ilo Tools Setting Matrix Operating Environment role authorization 49

50 System Setup System Utilities 7. Select All Managed Systems and CMS in the Select Systems field. 8. Click OK. NOTE: You might see the following: You can safely ignore this and continue. User management overview Matrix infrastructure orchestration is integrated with Microsoft Active Directory, a system that enables the management of identities, relationships, and security levels for systems, users and application settings in a network. This integration allows Windows Users Groups, as well as individual local users, to be given access to resources. When infrastructure orchestration is installed, three local User Groups (HPIO_Administrators, HPIO_Architects and HPIO_Users) are created. The CMS administrator populates the service provider roles by adding local Windows users and Active Directory users or groups to HPIO_Administrators, HPIO_Architects and HPIO_Users. When an organization is created, two local Windows groups are created with descriptions indicating the organization s name. These local groups have names of the form <organization_id>_administrators and <organization_id>_users (see Configuring multi-tenancy (optional) (page 119)). A group of users (for example, an Active Directory group) can be authorized to view and perform lifecycle operations in the same way that users are authorized. A user in a group is authorized based on the group's assignment to an HPIO role. NOTE: You can view and assign only directly named users and groups that are included in the HPIO Windows groups. Users or subgroups within these named groups are not visible, nor can they be directly assigned to resources. At the service provider level, there are three classes of Matrix infrastructure orchestration users. These classes are represented as CMS-local Windows user groups. These groups are: HPIO_Users HPIO_Architects HPIO_Administrators 50 Configuring the CMS can log on to Matrix infrastructure orchestration Self-Service Portal ( and initiate requests for provisioning using published templates. These requests require approval from an Administrator. have the privileges of the HPIO_Users group, and can access the Matrix infrastructure orchestration Designer ( to create, modify, and publish templates. have the privileges of the HPIO_Architects group, and can access Matrix infrastructure orchestration console through the HP SIM, initiate requests without requiring approval, modify infrastructure orchestration configuration items, configure networks and pools, grant users access to existing resources, and approve, reject, continue, or cancel requests. Can also access infrastructure

51 orchestration designer, infrastructure orchestration organization portal for any organization, and the infrastructure orchestration self service portal for any organization. NOTE: If you create a new user who also needs access to the HP SIM Audit log, the system administrator must give that user authorization to view the log using the HP SIM Users and Authorizations tool. Adding user accounts to groups The final step in configuring authorizations is adding user accounts to the desired groups. Create at least three Windows users and then add the user accounts to their respective HPIO Windows groups according to the desired level of authorizations. The following are examples of the user names for the different user groups. MatrixAdmin for HPIO_Administrators MatrixDesigner MatrixUser for HPIO_Architects for HPIO_Users Matrix infrastructure orchestration access Console Designer Self Service Portal Organization portal Group membership requirement 1 HPIO_Administrators HPIO_Administrators, or HPIO_Architects HPIO_Administrators, HPIO_Architects HPIO_Users, <organization-id>_administrators 2 and <organization-id>_users 2. HPIO_Administrators and <organization-id>_administrators 2 1 A user who is not a member of one of those groups is not authorized to use Matrix infrastructure orchestration regardless of the authorizations configured in HP SIM. 2 Users added to an organization. Users added to HPIO Microsoft Windows groups do not need to be explicitly added to HP SIM. They are automatically added to HP SIM when the user first logs in to HP SIM and are granted the authorizations assigned to the groups to which they belong. Users belonging to multiple groups in HP SIM receive the combined authorizations assigned to the groups in which they are members. You may also add Active Directory domain users or groups to any of the HPIO Windows groups described above. Checking and setting primary network of the CMS When you have multiple networks configured on the CMS, you need to ensure that the management network is set as the primary IP for the CMS. To check this: 1. Navigate to the HP SIM System page for the CMS by selecting Options View CMS System page. 2. Validate the CMS IP address, preferred name, and network name to ensure they are correct. 3. Select the Tools & Links tab 4. Under the HP Systems Insight Manager Pages section, click Edit System Properties 5. Verify that the Primary IP matches that of the management network previously set in the advanced networking settings. If not, change it to the IP of the management network. 6. Select the Prevent the Discovery process from changing this system name and the Prevent the Discovery process from changing this system's primary IP address checkboxes. Checking and setting primary network of the CMS 51

52 7. Click OK. Configuring alerts for disk space usage If the CMS or database servers run out of disk space, management functionality might be temporarily lost. Any operations in progress at the time of the failure might complete with errors. HP recommends proactively monitoring disk usage for the CMS and database server. One technique for monitoring disk space usage is to configure an HP SIM disk threshold alert. Such alerts can be easily configured for any system with HP System Management Homepage (HP SMH), including the CMS. NOTE: Threshold alerts can be set for a physical CMS only, where the HP System Management Homepage is installed (and not for virtual machines). When configuring disk thresholds, you will be prompted for a Warning threshold and a Critical threshold. You will also be prompted for a Reset threshold for each. The Reset threshold is the value below which disk utilization must drop before the corresponding alert threshold is rearmed. This prevents the generation of multiple alerts when utilization hovers near the alert threshold. The threshold rules are: (WarningThreshold + 3) CriticalThreshold 99 (ResetWarningThreshold + 2) WarningThreshold (ResetCriticalThreshold + 2) CriticalThreshold Thresholds are defined in terms of percent utilized. HP does not have specific recommendations for setting these thresholds. Their ideal values depend on your specific configuration, growth trends, and capacity management practices. In the absence of specific requirements, consider the following suggestions: CriticalThreshold = 90% or (DiskSize 10 GB) / DiskSize), whichever is less WarningThreshold = CriticalThreshold 5 ResetCriticalThreshold = CriticalThreshold 3 ResetWarningThreshold = WarningThreshold 3 To set a disk threshold alert for the CMS (or for the database server if it supports SMH): 52 Configuring the CMS

53 1. Launch the HP SMH on the CMS, and confirm that the data source is set to SNMP. If the data source is set to WBEM, change it to SNMP before you proceed. (Settings Select SMH Data Source Set SNMP) NOTE: If the message Could not set the disk threshold, the agent did not accept the request." displays, you must confirm that the data source is set to SNMP (not WBEM) on the HP SMH for the system. If SNMP is not available as a selection, you must configure the SNMP agent on the system. Use Configure Configure or Repair Agents, and select Install SNMP Agent (HP Insight Management Agents for Windows. 2. Determine the threshold values, as a percentage of total utilization, at which you would like to receive and to rearm the alerts. 3. In HP SIM's All Systems collection, select the CMS (and/or database server). 4. Go to Configure Disk Thresholds Set Disk Thresholds Set the threshold values determined previously. 6. Set a polling interval (note, the polling is local to the target node; polling does not generate traffic between the CMS and target node; the default 120 seconds is probably acceptable). 7. Click Run Now. NOTE: There is no need to schedule this task to run periodically. This procedure sets all the thresholds for all disks on the target system equally. If the target system has multiple disks, you might want to fine tune the threshold for each disk. NOTE: The following procedure requires a Java Runtime Environment and browser plugin to be present on the CMS. To fine tune the threshold for each disk: 1. In HP SIM All Systems collection, find the CMS (or database server) and click the link to visit the System Page. 2. On the System Page, click System Management Homepage. 3. Select Tasks Operating System File Space Used or Tasks System Server Configuration Threshold Information. 4. Set the threshold for each disk by moving the appropriate sliders or entering numeric values. 5. Click Save. You can also use the above steps to verify that the thresholds have been set. For more information, see HP SIM thresholds at hpsim-helpfiles/mxhelp/mxportal/en/usetools_diskthresholds.html. Configuring alerts for disk space usage 53

54 6 Configuring discovery and credentials Discovery is the process of finding systems in the management domain so that they can be managed from the CMS. HP SIM can automatically discover and identify systems attached to the network using information from management protocols such as SNMP, WMI, WBEM, SSH, and SSL. Create discovery tasks to limit discovery to specific network segments or IP address ranges, or to control the frequency that each task runs. Use discovery filters to prevent discovery of unwanted system types. In addition to discovery, you can optionally choose to have additional configuration done on the managed systems, as they are discovered, by configuring the settings using the Configure or Repair Agents(CRA) button. Use this to automatically configure the discovered server to send SNMP traps to the CMS, have the CMS subscribe to WBEM events, or allow the CMS to execute remote commands. Where this is appropriate in the following instructions, it will be identified as (Optional). If the servers you plan to run CRA on have not previously been managed, they may require the installation of Agentless Management Service, WBEM Providers, Insight Management Agents, or OpenSSH. Alternatively, manually configure WMI and/or SNMP on those operating systems. HP recommends that you configure this for all operating system discovery tasks except ESXi. For example, on an ESX 4.0 or 4.1 server CRA can be used to deploy the IM Agents and configure the SNMP Traps on that server. For more information about the options available for discover and configuration tasks, see the HP Systems Insight Manager User Guide. When HP SIM discovers a hypervisor host, it also attempts to discover the guest virtual machines for the host. Discovered guests are recognized and managed in HP SIM and in Matrix OE visualization (shown in Chapter 10) but will not be visible on the infrastructure orchestration self service portal or infrastructure orchestration console. IMPORTANT: Do not discover hosts on which your CMS, vcenter Server, SVCMM server, or other infrastructure server are guests unless you intend to license and manage the hosts. If you accidentally discover a host for an infrastructure virtual machine that you do not intend to license, remedial command line operations may be required. NOTE: For HP SIM to recognize and manage a server, it must support at least a machine-readable serial number. This restriction applies both to third-party servers running vcenter Server or SCVMM server. Configuring credentials To configure credentials common to many servers: 1. Go to Options Security Credentials Global Credentials. 2. Set the SNMP Read community string. HP recommends that you do not enter any global Sign-in Credentials unless you use a single small set of administrative credentials for all hypervisors, managed servers, management processors, and virtual machines. 3. Verify that the WMI Mapper settings are correct: a. Go to Options Protocol Settings WMI Mapper Proxy. b. Ensure the host name shown is the fully qualified domain name of the CMS associated with the IP address. c. If the IP address is not on the primary network, or if the host name does not match the FQDN of that IP address, then delete the existing proxy configuration and create a new one with the correct fully qualified domain name of the CMS. 54 Configuring discovery and credentials

55 Changing the Daily System Identification time By default, HP SIM creates a "Daily System Identification" task which executes automatically at 4:05 PM. To minimize conflicts with discovery tasks and with normal operations, this task should be scheduled to execute at a time when most systems are likely to be operational (such as, not during a maintenance window), but when other scheduled tasks and operational procedures are not likely to execute. To change the time at which the "Daily System Identification" task executes: 1. Go to Tasks & Logs View All Scheduled Tasks. 2. Select the Daily System Identification task. 3. Click Edit. 4. Click Schedule. 5. Change the time and then click Done. Defining discovery tasks In HP SIM, define a set of discovery tasks to use later during the setup and configuration process. Discovery should be performed incrementally and in the order described. Specifically discover the OA first, and then the other managed systems. HP recommends the use of Discover a group of systems option instead of Discover a single system even when there is only one server to discover. If the server IP address is changed later and you need to modify the discovery task, if you select the Discover a single system option, you will need to re-enter the credential even if it is not changed. When you select the Discover a group of systems option, the previously entered credentials continue working for the new IP addresses. NOTE: Discovering everything at the same time can cause a difficult diagnostic situation. HP recommends that you not use the Automatic Discovery task that was predefined for the entire network. If you have a set of IP ranges to be discovered automatically, make sure to exclude the CMS alternative IP address. NOTE: HP recommends setting no more than three credentials for each discovery task. This is to reduce the chance of account lockout when an inappropriate credential is tried too many times against one of the servers in the group. You might need to group the discovery tasks by credentials to accommodate this recommendation. To define a set of discovery tasks: Prepare for system discovery 1. Before performing the discovery tasks that follow, ensure all management processors and servers are properly configured in DNS. 2. If you plan to discover VMware ESXi 5.0 and above host servers with lockdown mode enabled: a. Open Option Discovery Configure general settings. b. Select the Automatically discover VMware ESX host server in lockdown enabled mode checkbox. c. Click OK. 3. Create a privileged user account remmgr on each of the VMware ESXi 4.x hosts that need to be managed by vcenter 4.x in lockdown enabled mode. NOTE: If a VMware ESXi 4.x host is managed by VMware vcenter 4.x in a lockdown mode, these hosts cannot be monitored and managed by providing the root credentials the privileged user account remmgr is required. The remmgr user must have root account privileges. Use the remmgr user credentials to discover and identify those hosts. Complete all the options below that apply to your environment. Changing the Daily System Identification time 55

56 Option 1: Define a discovery task for the OA only If your environment includes Virtual Connect enclosures, it is recommended to define a discovery task for the Onboard Administrators. This will automatically detect the relationship among the modules and blades. 1. Select Options Discovery. 2. Click on New. 3. Select Discover a group of systems. 4. Add a name, for example, Onboard Administrators. 5. Uncheck the automatic discovery checkbox. 6. Add the IP addresses (for both primary and standby) for the OAs you want to discover. 7. Click Credentials. 8. On the Sign In tab, set the appropriate Administrator credentials for the OAs in the username and password fields. NOTE: OA login credentials are case sensitive. 9. Also add the Virtual Connect Modules and ilo administrator credentials for all the blades in the enclosure. For each anticipated set of credentials, click <<Add and set the appropriate administrator credentials. (For example, if there is an Integrity blade in the enclosure, the default username for the Integrity ilo is admin). 10. Click on the SNMP tab. 11. Set the appropriate SNMP community string, if different than the global community string specified in the Global Credentials dialog box above. 12. Click OK. 13. Click Criticality and then select Non-Critical. 14. Click Save. 15. Click Run Now. 16. Verify that the task results show up in the same window and completed successfully. This should populate HP SIM with all HP BladeSystem enclosure modules and server blades. NOTE: Virtual Connect Fibre Channel modules will return the following minor error that can be safely ignored: Minor: Identification has detected that the value (NULL) in the cpqhoguid MIB is not a valid value for the UUID in HP SIM. For servers, verify that the latest supported HP Insight Management Agent is installed. For non-servers, verify that the latest supported firmware version is installed. Option 2: Define a discovery task for the VMware vcenter servers If there are ESX/ESXi servers being managed by the CMS, then define a discovery task for the VMware vcenter servers which manage these hosts. NOTE: All vcenter servers are required to be discovered first as managed systems before you configure vcenter settings in HP SIM. 1. Select Options Discovery. 2. Click New. 3. Select Discover a group of systems. 4. Add a name, for example, vcenters. 5. Uncheck automatic discovery. 6. Add the IP addresses for vcenter servers. 7. Click Credentials. 56 Configuring discovery and credentials

57 8. On the Sign In tab, set the appropriate Administrator credentials and click OK. NOTE: See Appendix A: Configuring vcenter server accounts (page 167) for how to configure a non-administrator user for access to resources through the vcenter server 9. Set the appropriate SNMP community string, if different than the global community string specified in the Global Credentials dialog box above. 10. Click Criticality and then select Non-Critical. 11. (OPTIONAL) Click Configure/Repair. a. Select the Configure newly managed systems checkbox. b. Select Use Sign-in credentials. Defining discovery tasks 57

58 c. Select the Create subscriptions for WBEM events checkbox. d. Select the Set read community string checkbox, and enter the desired community string. e. Select the Set traps to refer to this instance of HP Systems Insight Manager checkbox. f. Select the Configure a secure shell (SSH) access checkbox. g. Select Host based authentication. h. Select the Set trust relationship to Trust by Certificated checkbox. i. Click OK. 12. Click Save. 13. Click Run Now. 14. Verify the task results show up in the same window which indicates they completed successfully. NOTE: If your vcenter Server is running inside a Virtual Machine, the following Minor error can be safely ignored: Minor: The discovered VM guest is not associated with the VM host. Verify that the supported HP Insight Management Agents or WBEM providers are installed on the host, and verify that the host was discovered. Option 3: Define a discovery task for the SCVMM servers NOTE: SCVMM servers are required to be discovered first as managed systems before you configure SCVMM settings in HP SIM. 1. Select Options Discovery. Click New. 2. Select Discover a group of systems. 3. Add a name, for example, SCVMM. Uncheck Automatic discovery. 4. Add the IP addresses for domain SCVMM servers. Click Credentials. 5. On the Sign In tab, set the appropriate Administrator credentials. For SCVMM servers that are part of a domain, you must use domain credentials, not a local administrative account.set the appropriate SNMP community string, if different than the global community string specified in the Global Credentials dialog box above, and then Click OK. 6. Click Criticality and then select Non-Critical. 7. (OPTIONAL) Click Configure/Repair. a. Select the Configure newly managed systems checkbox. Click Use Sign-in credentials. b. Select the Create subscriptions for WBEM events checkbox. c. Select the Set read community string checkbox, and enter the desired community string. Select the Set traps to refer to this instance of HP Systems Insight Manager checkbox. d. Select the Configure a secure shell (SSH) access checkbox. Click Host based authentication. e. Select the Set trust relationship to Trust by Certificate checkbox. f. Click OK. 8. Click Save. 9. Click Run Now. Verify that the task results show up in the same window, which indicates they completed successfully. NOTE: When HP SIM discovers a hypervisor host, it also discovers the guest virtual machines for each host that volunteers guests. The credentials used for the guests are the same set used for the host. Therefore, you may need to balance your host discover task definitions with your various guest operating system credentials. Alternatively, you may create a separate discover task for your guests and not include any guest credentials in your host discover tasks. 58 Configuring discovery and credentials

59 Option 4a: Define one or more discovery tasks for the hypervisor host operating systems (non-esxi) Use this step for VMware ESX servers or Microsoft Hyper-V servers. For ESXi servers, use option 4b. 1. Select Options Discovery Click New. 3. Select Discover a group of systems. 4. Add a name such as Hypervisor Hosts non-esxi. 5. Uncheck the automatic discovery checkbox. 6. Add IP addresses for any VMware ESX or Microsoft Hyper-V hosts. Add IP addresses for both Microsoft Hyper-V hosts and guests. 7. Click Credentials. 8. On the Sign In tab, set the appropriate Administrator credentials (for example, root) for the hypervisor hosts in the User name and Password fields. For Hyper-V servers in a cluster, which are part of a domain, you must use domain credentials, not a local administrative account. 9. Also add the Administrator credentials for each guest that can be deployed onto these hosts. For each anticipated set of credentials, click <<Add and set the appropriate Administrator credentials for that guest. With the default horizontal discovery configuration, ESX VM guests will be discovered while discovering hosts. Click OK. 10. Click Criticality and then select Non-Critical. 11. (OPTIONAL) Click Configure/Repair. a. Select the Configure newly managed systems checkbox. b. Select Use Sign-in credentials. c. Select the Create subscriptions for WBEM events checkbox. NOTE: ignored. Subscribing to WBEM events might fail on ESX hosts. The failure can safely be d. Select the Set read community string checkbox, and enter the desired community string. e. Select the Set traps to refer to this instance of HP Systems Insight Manager checkbox. f. Select the Configure a secure shell (SSH) access checkbox. g. Select Host based authentication. h. Select the Set trust relationship checkbox. i. Click OK. 12. Click Save. 13. Click Run Now. 14. Verify the task results show up in the same window which indicates they completed successfully. This should populate Virtual Machine Hosts collections in HP SIM. Check the collection to ensure the VM guests are associated with the correct hosts. Option 4b: Define one or more discovery tasks for the hypervisor host operating systems (ESXi only) VMware ESXi servers only 1. Select Options Discovery Click New. 3. Select Discover a group of systems. 4. Add a name such as Hypervisor Hosts ESXi. 5. Uncheck the automatic discovery checkbox. 6. Add IP addresses for the VMware ESXi hosts. Defining discovery tasks 59

60 7. Click Credentials. 8. On the Sign In tab, set the appropriate Administrator credentials (for example, root) for the hypervisor hosts in the User name and Password fields. 9. Also add the Administrator credentials for each guest that can be deployed onto these hosts. For each anticipated set of credentials, click <<Add and set the appropriate Administrator credentials for that guest. With the default horizontal discovery configuration, ESX VM guests will be discovered while discovering hosts. Click OK. 10. Click Criticality and then select Non-Critical. 11. Click Save. 12. Click Run Now. 13. Verify the task results show up in the same window which indicates they completed successfully. This should populate Virtual Machine Hosts collections in HP SIM. Check the collection to ensure the VM guests are associated with the correct hosts. Option 5: Define discovery tasks for systems with non-hypervisor operating systems installed Skip this step if your environment only has a hypervisor operating system installed. 1. Select Options Discovery. 2. Click New. 3. Select Discover a group of systems. 4. Add a name, for example, Windows servers for <certain functions>. 5. Uncheck Automatic Discovery. 6. Add the IP addresses for servers. 7. Click Credentials. 8. On the Sign In tab, set the appropriate Administrator credentials and click OK. 9. Click Criticality and then select Non-Critical. 10. (OPTIONAL) Click Configure/Repair. a. Select the Configure newly managed systems checkbox. b. Click Use Sign-in credentials. c. Select the Create subscriptions for WBEM events checkbox. d. Select the Set read community string checkbox, and enter the desired community string. e. Select the Set traps to refer to this instance of HP Systems Insight Manager checkbox. f. Select the Configure a secure shell (SSH) access checkbox. g. Click Host based authentication. h. Select the Set trust relationship to Trust by Certificate checkbox. i. Click OK. 11. Click Save. 12. Click Run Now. 13. Verify the task results show up in the same window which indicates they completed successfully. Option 6: Define a discovery task that coincides with a DHCP scope that will be used by this environment Keep in mind that overlapping discovery tasks can be confusing to manage. Troubleshooting discovery issues These are issues that you may experience during discovery. 60 Configuring discovery and credentials

61 Discovery order For best results, HP recommends creating the following discovery tasks, and running them sequentially in the suggested order. 1. Onboard Administrator 2. vcenter and SCVMM servers 3. ESX hosts and Hyper-V hosts 4. Management Processors 5. Non-HyperVisor hosts 6. DHCP range If discovery tasks are run out of order, errors are likely. Typical errors due to running discovery tasks in an improper order include: Association errors For example, a server not associated with a management processor or virtual machine not associated with a virtual machine host. Credential errors Because discovery of systems can trigger additional discovery of associated systems or management processors, if the correct credentials are not supplied for the associated systems, their discoveries are likely to show errors. If you discover these associated systems with a subsequent discovery task containing the proper credentials, they should then complete successfully. Large system discovery If a discovery task discovers a very large number of systems, the re-identification done as part of Configure/Repair can consume resources long enough to cause a subsequent discovery task to time out which could result in discovery task in skipped status. If this occurs, re-run the skipped discovery task and any subsequent failed discovery tasks in the original order, starting from the task that timed out. You do not need to rerun tasks which completed prior to a skipped task. If you encounter subsequent failures of the same type: 1. Repeat this process, but introduce delays between the executions of the discovery tasks. 2. Consider breaking up the discovery tasks into multiple smaller ones so that the Configure/Repair action does not run long enough to cause a timeout of a discovery task. Troubleshooting discovery issues 61

62 7 Configuring VMware vcenter and Microsoft System Center Virtual Machine Manager settings To take full advantage of your hypervisors in the Matrix OE solution, configure connectivity with your VMware vcenter Server and/or Microsoft System Center Virtual Machine Manager. To deploy VMware virtual machines, access to at least one vcenter server with templates is required. However, you can deploy Microsoft virtual machines by either using templates on a Microsoft SCVMM server or by generating templates directly from VMs on a Hyper-V server. All operations within the Insight Management software will be performed using the configured accounts and authorizations as expressed in HP SIM and IO. The VME credentials used in this section are not required to be the same credentials used for the server discovery. NOTE: For new vcenter or SCVMM servers, you must discover the server before you configure settings. For information about how to create a discovery task for a vcenter or SCVMM server, see Configuring discovery and credentials (page 54). HP does not support a configuration that uses the same CMS or Insight Control server deployment server for the VMware vcenter server. Use the following instructions to check or change the settings, and to add new vcenter or SCVMM settings. 1. In HP SIM, select a vcenter or SCVMM server. If you have not made a selection a selection screen will appear. HP recommends that you only select one at a time. 2. Select Options VME Options Add or Edit VME Credentials If you have not already selected one, select the vcenter or SCVMM server as a target system. 4. On the Add or Edit VME Credentials screen, select vcenter or scvmm in the Protocol menu and fill in the port, user name, and password information for the vcenter or SCVMM server. Click OK. NOTE: For vcenter, the credentials must have the permissions listed in Configuring vcenter server accounts (page 167). For SCVMM servers, which are part of a domain, you must use domain credentials, not a local administrative account. 62 Configuring VMware vcenter and Microsoft System Center Virtual Machine Manager settings

63 5. To validate the VME settings, go to Options VME Options View VME Settings. 63

64 8 Configuring integration with deployment servers Matrix infrastructure orchestration supports the following server deployment platforms for provisioning: Insight Control server deployment (physical provisioning) Ignite-UX (physical and virtual provisioning) HP Server Automation (SA) (physical and virtual provisioning) The host IP address and credentials for the deployment servers used by infrastructure orchestration may have been entered during infrastructure orchestration installation in Chapter 4. Alternatively, configure the IP address and credentials after installation is complete as described in this section. IMPORTANT: Validate that your deployment server environment is functioning correctly and able to deploy your required operating systems to a virtual machine prior to integrating with Matrix OE. For more information on how to configure the HP Server Automation server in preparation for use with Matrix OE, see the white paper Integrating HP Server Automation with HP BladeSystem Matrix/Insight Dynamics available at Registering deployment servers If you want to add a deployment server after infrastructure orchestration is installed, first ping the server to ensure it is reachable from the CMS and then enter the following commands on the CMS: NOTE: If you copy and paste these commands, be sure to enter the dash (minus) key. In some cases, copying and pasting results in characters that appear to be the same but are incorrect. Insight Control server deployment mxnodesecurity a p dsc_rdp c username:password -t on -n <ipaddress of server deployment server> Ignite-UX mxnodesecurity a p dsc_ignite c username:password -t on -n <ipaddress of Ignite server> HP Server Automation (SA) or Insight Control server provisioning: mxnodesecurity a p dsc_sas c username:password -t on -n <ipaddress of HP Server Automation server> For more information on configuring deployment servers, see Configuring deployment servers in the HP Matrix Operating Environment 7.0 Infrastructure Orchestration User Guide available from the Insight Control Information Library at NOTE: In the following chapters, remember to configure the networks used by these deployment servers as a Boot Network 64 Configuring integration with deployment servers

65 IMPORTANT: If an HP Server Automation server is specified during the initial installation, the file opswclient.jar is copied from the SA core to the CMS to ensure version compatibility. If you instead register an HP Server Automation server after the installation as described in this section, you must also copy the file /opt/opsware/twist/extlib/client/opswclient.jar from the SA Core server to the CMS into C:\Program Files\HP\Systems Insight Manager\ lib. Overwrite any file of the same name (do not rename or otherwise leave any additional files in the folder on the CMS). Once the file opswclient.jar is properly copied, stop and restart HP SIM using the commands mxstop and mxstart. Registering deployment servers 65

66 9 Configuring and licensing with managed system setup wizard Checklist The Insight managed system setup wizard (MSSW) sets up selected systems with the appropriate agents, licenses and configuration steps for the managed features you specify. If you need to modify the configuration or management features on your systems, you can re-run this wizard to make changes. You can also use the wizard to diagnose configuration issues. WARNING! If you accidently discover a host outside the intended licensed environment that is associated with the CMS or a VME server, MSSW requires you to license that host. Once a host is discovered and the associations to its VMs are populated in HP SIM, you cannot remove that host or those associations without also removing all the hosted VMs. If one of those VMs is your CMS, you cannot delete it. If you are unable to remove such a host and all its associated VMs, enter mxnode r <host> x force at the command line to remove the unlicensed host and its associations from HP SIM. NOTE: Follow the instructions in this section to configure and license all the managed systems that you have discovered. Rerun the managed system setup wizard after installing any additional hypervisors and after installing any other server blade operating systems. Before you begin, review the following checklist to ensure your target systems are ready to be analyzed and configured by the managed system setup wizard. Verify that: Target systems are fully discovered. Valid credentials for target systems are stored within HP SIM. HP SIM discovery and identification was successful for all target systems. Ensure hypervisor host time remains synchronized with CMS all hypervisor hosts and their management servers must have a proper time source and remain in reasonable synchronization with the CMS. For example, each VMware ESX server has the ability to specify a set of NTP time servers. NTP protocol recommends that you use at least three distinct NTP servers. Using managed system setup wizard One instance of Insight managed system setup wizard can run at a time in HP SIM software. NOTE: You must set your web browser to allow HP SIM to open pop-up windows. Otherwise, the managed system setup wizard will not be able to start in a new window. Steps of the wizard Follow these steps to select and configure managed systems. 1. Select managed systems. In the System Collection, click Systems Shared System by Type Virtual Machine Hosts All Virtual Machine Hosts. Select all the hosts you want to license. NOTE: If you have an environment with servers that are not yet running a hypervisor host, be sure to include those in your selection otherwise they will not be licensed for future use. 66 Configuring and licensing with managed system setup wizard

67 2. Start the wizard. In the HP SIM top menu, select Configure Managed Systems Setup Wizard to start managed system setup wizard. An new window will open which displays the managed system setup wizard overview. Click Next. If you selected systems in HP SIM before running the wizard, then it operates on the selected systems. If you have not selected valid target systems, the wizard prompts you to select a target system using the Select Target Systems and Verify Target Systems screens in HP SIM. Steps of the wizard 67

68 3. Select and configure management features. You can begin by selecting features for all the systems you've selected. The wizard analyzes your current configuration, selects the dependencies, and excludes those features that are not appropriate for selected systems. As an alternate option, you can select features for each individual system. When you select a top-level feature such as HP Matrix Operating Environment the wizard might not be able to determine if some components or prerequisites are not required for each individual system. For example, installing OpenSSH is not required for Hyper-V hosts or VME servers (vcenter or SCVMM). Follow these steps to configure management features for the selected systems in the MSSW: a. In the Select Features step, specify the management features you would like to configure for managed systems you selected. The screen below shows the default view, which you can use to license multiple servers at once. For this environment, HP recommends that you select HP Matrix Operating Environment (which will also select HP Insight Control virtual machine management by default) as a minimal feature selection. WARNING! If you select Matrix OE for a hypervisor and HP Insight Control virtual machine management is not automatically added, this indicates that the discover task may not have properly identified the server as a hypervisor. You must inspect the discover task results to determine a proper action 68 Configuring and licensing with managed system setup wizard

69 NOTE: It is always a good practice to expand features to ensure the selection is done correctly. If you have chosen a Hyper-V host or a VME server and Matrix Operating Environment, the wizard attempts to install OpenSSH on the host. OpenSSH is not required to manage Hyper-V hosts or VME servers (vcenter or SCVMM). Therefore, you should expand HP SIM, and then expand Remote Command Execution, then deselect the Hyper-V host by name. NOTE: If you wish to license servers for future deployment of hypervisor hosts, be sure to expand the HP Matrix Operating Environment and HP Insight Control virtual machine management features and select those servers. When licensing servers individually, you see the screen below. b. In the Choose Options step, set options for selected management features that have them, overriding any default or previous settings. Steps of the wizard 69

70 c. In the Analyze Systems step, analyze each system to determine whether licenses, agents, or other configuration tasks are needed to enable the selected management features. i. Each result shows one of the following status: Success indicates the system is correctly configured for a selected management feature. ii. Configuration will occur Warning Failed indicates the system is not currently configured, and will be configured by the wizard in a following step. indicates the system is configured correctly, but some related configuration changes could be performed to make management better/easier/more complete. indicates the analysis could not be completed or there are problems with the system that cannot be corrected by the wizard. Typically, these result from the system being improperly discovered, having the wrong credentials, having a firewall preventing communication with the system, missing HP management agents on the system, and so forth. Correct any system operations which failed. When there is a failure in the step, you must correct the error or deselect the system before you can move on. Otherwise, the following message displays: 70 Configuring and licensing with managed system setup wizard

71 iii. After you correct each error, click Reanalyze to verify the error is corrected and then click Next. NOTE: You can also remove any systems with analysis failure status in order to move forward, but only if the system or the features for the system are not required. Note that removing a system from the wizard also results in removal of management features from other systems if those features have dependencies on the system you remove. d. In the Select Licenses step, select the available product license options, if any, required by the managed systems to enable management features. Click Add Licenses to add new license keys. For more information, see the HP Insight Managed System Setup Wizard Getting Started Guide. Steps of the wizard 71

72 e. In the Task Credentials step, enter any credentials required to perform configuration steps on managed systems if HP SIM does not already have them, for example, when SSH is not configured on the managed system. You can choose to enter the credentials by OS type or System Name. f. In the Summary step, review the summary of the operations that will be performed to enable the selected management features and initiate the configuration of the managed systems. When Run Now is selected in this step, the selected management features for each system are saved, needed licenses are applied, needed agents are installed, and other configuration steps are performed. 72 Configuring and licensing with managed system setup wizard

73 g. In the Results step, view the HP SIM task results for the configuration steps performed at the conclusion of the previous step. NOTE: You can also use the Tasks & Logs View Task Results menu to check managed system setup wizard results. Steps of the wizard 73

74 10 Creating a virtual machine logical server The following steps will verify that the logical server features are working correctly for the hypervisor hosts you licensed in the previous section. This chapter is optional. You may skip this chapter and proceed to Configuring Matrix infrastructure orchestration (page 81). Follow these steps to create a single VM logical server. 1. In HP SIM, select Tools Matrix OE visualization to view the Visualization tab. 2. Make sure that Matrix OE visualization is synchronized with recent virtual machine operations by selecting the visualization menu item Tools Logical Servers Refresh. Select the Insight Control virtual machine management (VMM) checkbox and click Refresh. 3. Wait for the refresh operation to complete. 4. Confirm that you can see your enclosure and Virtual Connect domain, including the virtual machine hosts. NOTE: If your environment does not have a VC domain you will not see a Virtual Connect Domain or Enclosure. 74 Creating a virtual machine logical server

75 Importing virtual machines If you already have a VM hypervisor with guests at this point, you can use the import feature rather than create. 1. Select a VM guest that is running. 2. Within Matrix OE visualization select Tools Logical Servers Import. 3. Specify a logical server name and click Import. Importing virtual machines 75

76 4. Confirm the logical server was created successfully. This allows an existing virtual machine to be managed as a logical server. However, these imported logical servers are not visible in the infrastructure orchestration self service portal or on the infrastructure orchestration console. Imported virtual machines can be managed as shown on the Matrix OE visualization screen. Creating virtual machines If you have not used the import feature, select the Create Logical Server menu from within Matrix OE visualization. 76 Creating a virtual machine logical server

77 1. Specify the Logical Server identity. a. Enter a logical server name and description. HP recommends using a suffix of _ls or -ls for the logical server name. Never use a logical server name that is currently or will be the same as a hostname. b. Set the Portability Group to a group with hypervisor like ESX as class type. c. Select the Logical Server Architecture HP ProLiant. d. Select an OS as appropriate. e. Select an OS Variation f. Enter a VM name. HP recommends constructing a meaningful convention in this field. When it is not entered, the logical server management tool automatically creates one based on the logical server name. g. Enter ESX VM version (optional). h. Click Next. 2. Specify compute resources for this logical server. This information will be used to create the virtual machine (customizing values in the template) 3. Specify the storage configuration for this logical server. Creating virtual machines 77

78 a. In the Select Storage Type field select File (VM) Storage Entry. b. Click Create Storage Entry. c. Click Add Storage. d. Enter the appropriate Storage Size for your OS. e. Click Save. f. Select the Data Store. i. For ESX, this is typically a SAN-based data store. Do not choose a local data store, otherwise VMware's VMotion will not operate correctly. ii. For Microsoft Hyper-V, the selection of storage depends on whether or not the VM will be part of a cluster. g. Click Next. 78 Creating a virtual machine logical server

79 4. Specify the network configuration for this logical server. a. Click Add Network and add at least one management network that communicates with the CMS. If you have a deployment server that you would also like to test, you may optionally enable the added network for PXE boot. Otherwise you may install the OS using virtual media through the vcenter or MS VMM server console access to the VM. b. Click Next. 5. Review the new Logical Server Summary. a. Correct any issues. b. Click Finish. c. Click Activate. 6. To verify that the Logical Server was successfully created, click Tools Logical Servers Activate and select the logical server. The Activate: Assign Logical Servers to Target Hosts screen appears. a. Select the appropriate host for this logical server. Leave Power on the VM enabled unless you are not prepared to provision the OS at this time. b. If the host you wish to select is not listed as a valid candidate, it may be listed in the Rejected Target Hosts list. You can hover over the host to determine the reason why it was rejected c. Click Activate. 7. Click Confirm to begin the activation. Creating virtual machines 79

80 8. Select the OS to deploy on the logical server. During the activation the VM is configured and powered on. Plan to present the media to the VM as it powers on, connect to its virtual console before continuing or set up virtual media access by modifying the VM guest properties. The vm you just created should display with a red arrow, as shown below. The red arrow indicates a Logical Server that provides management features available in the Visualization View including Move, Power On, Power Off, Deactivate, and Activate. 80 Creating a virtual machine logical server

81 11 Configuring Matrix infrastructure orchestration Preparation Complete the following checklist before you configure Matrix infrastructure orchestration: Matrix infrastructure orchestration relies on the Microsoft Sysprep tools to enable customization of deployed Windows systems. Customization includes operations such as changing the hostname, applying the Windows license key on first boot, and setting the IP address. Have available the user names to use for the three roles supported by Matrix infrastructure orchestration. Each of the HP supported bursting destinations requires specific additional steps beyond those described in this guide. For more information on how to complete the configuration for public cloud bursting, see the whitepapers Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and HP Cloud Services or Amazon EC2 or Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and Savvis available at NOTE: Matrix infrastructure orchestration populates its inventory of VM hosts, virtual storage and virtual networks from data gathered from hypervisor hosts that are registered with Insight Control virtual machine management. To configure resources for virtual provisioning, it is necessary to first install, configure, discover, and register with virtual machine management, at least one hypervisor host. Configuring notifications and properties After installation, you must verify that all HP Operations Orchestration system properties are set correctly. Follow the instructions in this section to verify notification and other addresses. The system properties and notification settings for , SMTP servers, and accounts are managed within HP Operations Orchestration (installed as part of Matrix infrastructure orchestration). 1. To launch Operations Orchestration, select Start All Programs Hewlett-Packard Orchestration Operations HP Operations Orchestration Studio. A login prompt displays. 2. Connect to the Operations Orchestration console using the following Operations Orchestration administrator credentials: Username: admin Password: the CMS installation administrator password specified during Matrix infrastructure orchestration installation. NOTE: If the CMS installation administrator password is subsequently changed, the change is not reflected in Operations Orchestration. 3. Expand Configuration, and then expand System Properties. 4. Display and verify the value of the following properties associated with notifications: HpioApprovalRecipients HpioApprovalSender HpioManualNetworkProvisioningRecipients HpioManualNetworkProvisioningSender HpioManualOsDeploymentRecipients HpioManualOsDeploymentSender Preparation 81

82 HpioManualStorageProvisioningRecipients HpioManualStorageProvisioningSender HpioNotificationRecipients HpioNotificationSender HpioSmtpHost HpioSmtpPort 5. To edit a property value, right-click on the properties and select Repository Check Out. The system properties that are checked out now also appear in the My Changes/Checkouts pane. Use Shift- and Ctrl-click to select multiple properties at one time. 6. Double-click the system property to view and modify its value in the right pane. 82 Configuring Matrix infrastructure orchestration

83 7. Verify that the HpioCmsIP property is set to the primary IP address or FQDN of the CMS. If the IP address is not set or incorrect, click in the Property Value area for HpioCmsIP, and enter the correct IP address. If your SMTP server requires authentication, also verify the value of the following credentials: Configuring notifications and properties 83

84 8. (Optional) Configure addresses: During the Insight Management software installation process, you can specify one From and at least one To address for each operation class or use the same addresses for all classes. The OO system properties screen displays all the classes of s sent by IO. You can reconfigure each of them to go to a different address (use a semicolon to separate multiple recipient addresses). 9. To save the modified property values before exiting OO, right-click System Properties in the My Changes/Checkouts pane, and select Check In Tree. Configuring for virtual machine provisioning Verifying Microsoft Windows Sysprep NOTE: Microsoft Windows Sysprep files are now supported with encrypted password. See the HP Matrix Operating Environment Infrastructure Orchestration User Guide for more information. Matrix infrastructure orchestration relies on Windows Sysprep to enable customization of Microsoft Windows virtual machines. 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 Matrix OE-supplied Sysprep.inf file. This edit enables Matrix OE to provision new Windows systems with no manual interaction. Without this edit, for example, a newly provisioned system may halt during first boot waiting for a key. Matrix infrastructure orchestration customizes the Windows OS for each Windows VM it provisions by combining two sources of information and passing them to HP Insight Control virtual machine management (VMM). VMM passes the information to ESX and Hyper-V for customization. This information includes: Specific attributes from the service template such as hostname. Contents of the Matrix OE Sysprep.inf file, located at C:\Program Files\HP\Matrix infrastructure orchestration\conf\sysprep\sysprep_sample.inf. An administrator creates the new sysprep.inf file and can edit sysprep files based on the sample file to specify additional customizations for Windows virtual machines, such as the Windows license key. You can then use these files while creating IO templates with corresponding Windows virtual machines. You should create one sysprep file for each version of Microsoft Windows, for example, NOTE: Do not delete or rename the Sysprep_sample.inf file. These files are always.inf files (and not.xml) for all versions of Windows. 1. Copy Sysprep_sample.inf to sysprep_w2k3_32bit.inf 2. Copy Sysprep_sample.inf to sysprep_w2k3_64bit.inf 3. Copy Sysprep_sample.inf to sysprep_w2k8.inf 4. Copy Sysprep_sample.inf to sysprep_w2k8r2.inf 5. Edit the product key and any other needed customization in the file. 6. To cause IO to automatically join new virtual machines to a Windows domain, add the domain administrator credentials, in clear text, to the Sysprep.inf file. If the credentials are not provided in the Sysprep.inf file, select None or Workgroup in the Edit Network dialog box. After deployment completes, a domain administrator can manually join the system to the domain. When defining networks in IO, set the MS Domain Type to Domain in the Windows Settings tab of the IO Edit Network dialog box. 84 Configuring Matrix infrastructure orchestration

85 Installing Microsoft Sysprep tools Only install the Microsoft Sysprep tools if you are provisioning Windows Server 2003 or earlier guests. NOTE: Provisioning the following does not require installation of Sysprep tools: Windows 2008 and higher VM guests Linux VM guests Table 2 Installing Sysprep tools To enable customization on: VMware vcenter 4.x VMware vcenter 5.0 Do the following: Install the Microsoft Sysprep tools on the vcenter management server. If vcenter Server is installed on Windows Server 2008 or higher, and you are provisioning a Windows 2003 or earlier guest, install the Sysprep tools in C:\ProgramData\VMware\VMware VirtualCenter\sysprep\<OS>. NOTE: C:\ProgramData may be a hidden folder. If vcenter Server is installed on an earlier Windows operating system, install the Sysprep tools in C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\sysprep\<OS>. where <OS> is the Windows guest operating system. Valid values are svr2003 and svr Microsoft Hyper-V (Windows 2003 VM guests) Install the Microsoft Sysprep tools on the CMS in the folder C:\Program Files\HP\Insight Control virtual machine management\sysprep\<os> where <OS> is the Windows guest operating system. Valid values are 2003 and For more information, see the VMware vcenter and Installing the Microsoft Sysprep Tools article in the VMware Infrastructure Online Library and the Updated System Preparation tool for Windows Server 2003 SP2 article at the Microsoft support website kbid= The contents of Microsoft \Support\Tools\Deploy.cab (not the.cab file) must be placed in the directories mentioned previously. Example: Installing Windows 2003 Sysprep utilities The following steps show one example that installs the Sysprep utilities to support Windows 2003 x Log on to the desktop of your vcenter server. Navigate to the folder indicated in Table 2 (page 85). For example, locate C:\ProgramData\VMware\VirtualCenter\sysprep\2003\. 2. Mount the Windows 2003 distribution ISO. 3. Open the \support\tools directory. Configuring for virtual machine provisioning 85

86 4. Copy the contents of deploy.cab into the installation location as listed in Table 2 (page 85). Be sure to extract the files from the.cab and do not copy the.cab file. The following screen shows the resulting directory on the vcenter server to support Windows 2003 x86 guests. Hyper-V and Windows 2003 For Hyper-V Windows 2003 VM guests, the Sysprep utilities must be installed on the CMS in the HP folder C:\Program Files\HP\Insight Control virtual machine management\ Sysprep\2003 or Excluding hypervisor local storage and system drives from storage provisioning for VM guests Create VM guests on shared storage, not storage that is only local to the host. This enables efficient movement when the VM guest is moved to another VM host. It is also a best practice to isolate the storage for VMs on a separate drive from any storage containing hypervisor system files. Doing so results in greater performance and lower risk of starving the hypervisor of required I/O bandwidth. Specifically, if multiple concurrent VM provisioning requests on the system drive of a hypervisor host were performed, the disk I/O could become saturated during the virtual hard drive replication, and cause the host to become unstable or unresponsive. Matrix infrastructure orchestration services can be configured to use specific datastores for provisioning VMs. Unless configured, IO considers all volumes on a hypervisor host for provisioning a VM. In order to prevent creating the VMs on the hypervisor local storage and/or system drives, you must verify that the local storage is excluded by performing the following steps. 1. Log into the CMS to modify the hpio.properties file. 2. Edit the C:\Program Files\HP\Matrix infrastructure orchestration\conf\ hpio.properties file. 3. In the hpio.properties file, locate the section titled VOLUMES TO EXCLUDE: 4. To exclude storage for a Hyper-V VM host, add the drive letters you want to exclude to the property volume.exclusion.list, for example: volume.exclusion.list =C:;Y:;Z: volume.exclusion.list =C:;Q:;C:\\\\ClusterStorage\\\\Volume1 5. To exclude storage for a VMware VM host, add the data store path that you want to exclude to the property volume.exclusion.list, for example, volume.exclusion.list =/vmfs/volumes/storage* 86 Configuring Matrix infrastructure orchestration

87 6. As needed, look up the list of possible disk names to exclude for VM hosts by browsing to the system status page for the VM host in question and then click Disk Partitions to expand the listing. An example of this is shown in the following screenshot. 7. The property can be present only once in the file, so use a semicolon to separate drive names when specifying multiple drives, such as when excluding storage for both Hyper-V and VMware hosts. The following example excludes system drives of Hyper-V and VMware in the most common deployment configurations: volume.exclusion.list =C:;/vmfs/volumes/Storage* 8. Save the file. 9. Restart the Matrix infrastructure orchestration service. Creating ESX virtual machine templates Matrix infrastructure orchestration uses VMware templates as a deployment source for ESX. For ESX VMs, create VMware templates in vcenter. For each Matrix OE service template, you will need to either create or select an existing VMware template. HP recommends you first deploy or convert the template to a VM to validate it prior to using it in a Matrix OE service template. A valid ESX template must contain running VMware Tools. Besides the required boot disk, the template may optionally include one or more data disks. Creating ESX virtual machine templates 87

88 Checking virtual machines To use the VMware vsphere Client tool to connect to VMware vcenter server: 1. Verify that the virtual machine guest which will be used as a source for the service template is correctly running the VMware Tools. This is shown by selecting the VM name and viewing the Summary tab. There are three lines corresponding to the output of the VMware Tools executing inside the guest OS. The status must be OK or Running and the other two lines must indicate a proper IP address and DNS name. Templates created in a prior version that indicate Running (Out-of-date) are also supported. 2. Check the guest properties to verify that the General Information has the Guest Operating System type selected correctly (for example, Microsoft Windows or Linux) including the specific variation or version (for example, Red Hat Enterprise Linux 5 32-bit). 3. Review the resource requirements for the VM to make sure they are set appropriately for future deployments. CPU and memory requirements will be customized by the Matrix OE service template. However, ensure that any unneeded media (such as a DVD) is unmounted and that the proper boot and data volumes are defined. 4. Cleanly shut down and power off the VM. Do not suspend it. 5. Clone or convert the VM to a template. 88 Configuring Matrix infrastructure orchestration

89 Creating templates for Hyper-V virtual machines Matrix infrastructure orchestration utilizes either a Hyper-V VM or an SCVMM template as the source material for an Insight Control virtual machine management that is in turn used to construct a Matrix OE service template. However, to provision recoverable logical servers, configure your Hyper-V VM host in a Windows cluster. For more information, see your Windows documentation. When using Hyper-V, do not use a Hyper-V virtual machine management template created from a VM with Snapshot. Insight Control virtual machine management templates created from a VM with Snapshot, do not display on the Software tab of the IO console, and are therefore not available to create a Matrix OE service template. A Hyper-V template must have a guest operating system installed, along with the Microsoft Integration Services Setup installed in the VM. NOTE: Matrix infrastructure orchestration can only deploy a Hyper-V virtual machine when the boot disk is defined as IDE Controller 0 Location 0 (ide0:0). Creating a template from a virtual machine stored on a Hyper-V host To create an Insight Control virtual machine management template from Hyper-V virtual machine, do the following: 1. Power off the VM you want to use in the virtual machine management template. As a best practice, cleanly power off the VM by accessing the VM and performing an OS shutdown rather than using a Hypervisor power off command. If the VM is in a suspended state when you create the template, provisioning fails during customization with an error message of VM must be powered off for customization. 2. In HP SIM click Deploy Virtual Machine Templates Create Virtual Machine Template. The Step 1: Select Source Virtual Machine screen appears. 3. Select a VM from the list, and click Next. The Step 2: Select VM Template Repository Host screen appears. 4. Select the host that will receive the new virtual machine management template, and click Next. The Step 3: Specify the template Name and select VM Template Repository Folder screen appears. 5. In Template Name, enter a name for the template and specify a location for the template. 6. To store the virtual machine management template, in the target folder, select Browse and select a VM host data store folder. A unique folder will be created at the location you specify using the original source VM name (not the new template name.) 7. Click Next. The Step 4: Confirm Details screen appears. 8. Click Run Now. The task results appear. VMM template creation can take from 5 minutes to 30 minutes to complete. Using SCVMM templates Matrix infrastructure orchestration enables the deployment of services using the Microsoft System Center Virtual Machine Manager (SCVMM) template library. This is accomplished by selecting an SCVMM Hyper-V template on the Software tab in an infrastructure orchestration service template. SCVMM templates are displayed on the infrastructure orchestration console Software tab after SCVMM is successfully registered in Insight Control virtual machine management. The SCVMM server itself is not representative of a server pool, nor is it licensed as a target for deployment. SCVMM is not a required component for Hyper-V deployment. SCVMM template deployment is an option that coexists with deployments of Insight Control virtual machine management Hyper-V templates. Creating templates for Hyper-V virtual machines 89

90 The following constraints apply when using SCVMM templates. Microsoft SCVMM 2008 R2 is required for this integration A subset of SCVMM templates are included in the IO inventory: Hyper-V templates with a single VM are included ESX and other hypervisor types are excluded Multi-server (SCVMM service) templates are excluded No explicit indication is given when a template is filtered from view Create SCVMM templates with the No Customization Required option. IO overwrites the SCVMM customization parameters with its own customization, and some SCVMM customization parameters could persist after IO customization, potentially creating a confusing result. VMs deployed using SCVMM in a Hyper-V cluster environment are enabled for high availability (HA) by default, even when the IO template specifies a non-ha VM. If the VM is later deactivated and reactivated, it will continue to be enabled for high availability. Preparing images for public cloud bursting HP supported bursting destinations have unique requirements that must be taken into account when creating templates: For HP Cloud Services and Amazon EC2, you may choose from a large collection of publicly available images and private images you create in your account. An image filter configuration determines which images are available to infrastructure orchestration. Using Matrix OE with Savvis requires client-provided images uploaded to Savvis. For more information, see the whitepapers Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and HP Cloud Services or Amazon EC2 and Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and Savvis available at Configuring Matrix infrastructure orchestration resources Before using infrastructure orchestration, you must use the infrastructure orchestration console to set up server pools and networks, and verify information in the Users and Software tabs. A member of the HPIO_Administrators Windows group can log on the infrastructure orchestration console through HP SIM. Matrix infrastructure orchestration administrators can then set up resources to allow provisioning. To log on the infrastructure orchestration console: 90 Configuring Matrix infrastructure orchestration

91 1. Select Tools Infrastructure orchestration. 2. The infrastructure orchestration console appears. Configuring Matrix infrastructure orchestration resources 91

92 Infrastructure orchestration console overview The infrastructure orchestration console enables you, as an administrator, to deploy, manage and monitor the overall behavior of IO and its users, templates, services, and resources. For example as an administrator you can: View status, progress, and details of completed and executing requests View resources Approve or reject pending requests Perform pool management The infrastructure orchestration console displays the following tabs: Home Templates Requests Displays an overview of Matrix infrastructure orchestration operations providing statistics, resource usage, and links to access IO tasks. Enables you to view details, and create services from published templates. Administrators and architects can also create, edit, and delete templates. Allows you to view and manage the requests generated while performing other tasks such as a service instantiation or a service deletion. NOTE: This tab is empty until an administrator or user has submitted a request and the request is in-progress or completed. Services Servers Storage Organization Users Networks Software Calendar Enables you to start, stop, restart, standby, view details, or delete service templates. Displays available server pools, including the name of the resource, pool details, and server details. A server pool is a set of resources that you can view and utilize when creating new infrastructure services. You can also view the current utilization of the resources in the pool and assess which resources are still available for use. Displays a summary of the Matrix OE visualization - Manage Storage Pools page, including the name of the resource, storage pool entries, and LUN information. From this screen, you can launch Matrix OE visualization to create, update, or manage the SPEs. Displays details about the organizations in the environment, and allows you to create and modify an organization, and assign resources, users and administrators to an organization. Enables you to view the users and the pools assigned to them, and provides links to the following setup Tasks: View Insight Audit Messages Modify IO Users and Groups Manage Console Authorizations Displays the available networks and enables you to configure these networks. These settings are critical and are used by the IO controller to make allocation decisions and to configure servers on service infrastructure creation. Enables you to view available Matrix infrastructure orchestration software and add annotations, such as the size of a software image, OS and processor architecture compatibility limitations, or notes. Enables you to search for and view utilization information for users, services, and templates, graphically displaying usage and conflicts. The calendar displays content relevant to the search context. For example, if you search for a user, the Schedule tab displays the services owned by that user, the 92 Configuring Matrix infrastructure orchestration

93 Availability tab displays the availability of the pools used by the services owned by the user, and the Utilization tab displays the resource utilization of the services owned by the user. Before using Matrix infrastructure orchestration, you must set up server pools and networks, and verify the Users and Software tabs using infrastructure orchestration console. Verifying Matrix infrastructure orchestration users The Users tab contains a list of all users authorized to use infrastructure orchestration. If you do not see the users that you expect, see User management overview (page 50) to verify that every user you want to grant infrastructure orchestration access is a member of the appropriate group. NOTE: An IO SOAP user is automatically added and will be shown on this tab. You cannot modify any settings on this tab. Configuring server pools Matrix infrastructure orchestration server pools are groups of resources from which users are entitled to make requests. Before initiating a request for the first time, new server pools must be created and users must be assigned to them. In addition to physical servers and VM Hosts, infrastructure orchestration can provision the following types of resources: ESX resource pools ESX resource pools are a type of compute resource created using VMware vcenter. Matrix infrastructure orchestration can use ESX resource pools to provision virtual machines on a standalone VM Host or in a cluster. ESX resource pools enable a cluster to be divided into logical pools of memory and CPU resources above the level of individual VM Hosts, so a VM Host or an ESXi cluster can be shared by multiple organizations. A pool containing an ESX resource pool must not contain any other type of compute resource. A provisioning request can specify the use of multiple pools, as long as any one pool containing an ESX resource pool is homogeneous. Virtual machines can be allocated into ESX resource pools or into pools that do not contain ESX resource pools. However, virtual machines cannot be allocated to VM Hosts and clusters where the resource pools are defined. Configuring Matrix infrastructure orchestration resources 93

94 Cloud resources Cloud resources represent an external resource or capacity offered by a cloud service provider. Cloud resources are manually configured resources, not discovered resources, and require special configuration for use within infrastructure orchestration. A cloud resource must be added to a pool in order to be used in a provisioning request. A pool containing a cloud resource must not contain any other type of compute resource. A provisioning request may specify the use of multiple pools, as long as any one pool containing a cloud resource is homogeneous. For more information, see Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and Savvis and Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and HP Cloud Services or Amazon EC2. When starting up Matrix infrastructure orchestration for the first time, two pools are automatically generated. The Unassigned pool contains all resources previously discovered by Matrix OE, and the Maintenance pool contains resources that have failed. These pools are available only to users assigned to the HPIO_Administrators group, and cannot be used for infrastructure service creation. Matrix infrastructure orchestration automatically populates the Unassigned pool with the resources identified by HP SIM. IO updates the information each hour. After you update the available resources, click Refresh to see your updates immediately. IMPORTANT: In a multi-tenancy environment, the resources defined in a server pool using an IO administrator account are only available at the Service Provider level and will not be available to tenant organizations. If you plan to define tenant organizations, leave the resources intended for those organizations in the Unassigned pool. Follow these steps to create a new server pool: 94 Configuring Matrix infrastructure orchestration

95 1. Select the Servers tab, and then click Create Pool. 2. In New Pool name, enter a descriptive name. You can select servers from any pool, however when you first configure IO, 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 VM hosts from the Unassigned pool. You can only move resources to a pool after the resource is licensed for use by IO. 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. Configuring Matrix infrastructure orchestration resources 95

96 5. Before users other than the administrator can use a 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 and you should see a list of the users in your environment. 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 and a list of the assigned users appears at the bottom of the screen. 96 Configuring Matrix infrastructure orchestration

97 Viewing and configuring networks The following types of networks are discovered in infrastructure orchestration: Networks defined in Virtual Connect Networks defined in a hypervisor VMware: port groups Hyper-V: virtual switches Integrity VM: virtual switches connected to a physical NIC Networks defined by the infrastructure orchestration administrator that identify VLANs carried on a VC tunneled trunk Networks associated with some public cloud bursting destinations (Savvis does not present its networks externally) See Setting up virtual machine networks in the HP Matrix Operating Environment Infrastructure Orchestration User Guide for additional information. When two or more hosts have the same network name, only one is shown in the infrastructure orchestration console Networks tab. Subnets with the same name are collapsed into a single subnet in IO. In the network details Associations tab, the Cluster/VC Domain Group shows the VCDG and the cluster or the host (if not in a cluster) where the network is visible. NOTE: Most cloud provider networks are preconfigured and generally useable without further modification. If you edit a cloud provider network, you will find that a value is already specified for the DNS domain that is not used. Also, only DHCP assignments are supported and you may optionally reduce the supplied range if you require. All cloud provider subnets will show as Public, Shareable, and IPv4. The remainders of the subnet configuration fields are not applicable to cloud providers. To view and configure physical and virtual networks, the infrastructure orchestration administrator must perform the following steps. 1. In the infrastructure orchestration console, select the Networks tab. Matrix OE provides information about configured networks to infrastructure orchestration. For each network to be used with infrastructure orchestration, add DHCP and/or static address ranges. If networks do not appear correctly, try the following: a. Refresh resources see the first three steps shown in Creating a virtual machine logical server (page 74). b. Refresh the servers on the server tab using the green icon. c. Refresh the networks on this network tab using the green icon. 2. Select each network you intend to use, and then click Edit Network. Configuring Matrix infrastructure orchestration resources 97

98 Add information about the network and available IP resources on the Edit Networks page. Depending on your configuration, not all fields are required. The user interface helps guide you through the process by highlighting required fields and indicating invalid values. When editing a network associated with a deployment server configured according the procedure in Chapter 8, select that server in the Deployment Server menu and select Yes for Boot Network. NOTE: Matrix infrastructure orchestration supports IPv6 with the following restrictions. Physical or virtual servers can be automatically provisioned using DHCP address pools. Automatic IPv6 address configuration using static assignment or an address range is not supported. This restriction applies only to network interfaces directly provisioned by IO using IO managed address pools. Automated (PXE based) OS deployment through IO is not supported on an IPv6 network. 3. On the DNS tab, enter the DNS Domain (required), DNS Servers, and DNS Search Suffixes (optional.) 98 Configuring Matrix infrastructure orchestration

99 On the Windows Settings tab, enter optional Windows information such as domain and WINS information. 4. After adding the appropriate information to the tabbed areas of the Edit Networks screen, add the IP ranges for use by infrastructure orchestration. To add DHCP address space, click the up arrow in the DHCP Addresses area, or enter the number of DHCP addresses to make available to infrastructure orchestration. To add static address space, click New. A dialog appears for the range. Enter a Start and End address (inclusive), and then click OK. Configuring Matrix infrastructure orchestration resources 99

100 5. When finished setting up a network, click Save. The network is now ready to use with infrastructure orchestration. Trunk and VLAN networks Cloud deployment environments and multi-tenancy environments require segmented networks for customer data separation. VLAN tags in network packets can be used for network segmentation for data separation. This enables a single wire to carry network packets from separate network broadcast domains that are efficiently managed by switching technology in the data center infrastructure and in virtualization hypervisors such as ESX and Hyper-V. In Matrix infrastructure orchestration: A trunk is a physical or virtual subnet that carries traffic with multiple tags. It requires a trunk or tunnel connection at the switch port level and a VLAN-aware network connection within the server OS. A trunk network cannot be a VLAN network. A trunk in infrastructure orchestration designer is a VLAN trunk representing a network connection that carries multiple VLANs to a blade. How that is satisfied during a provisioning request depends on the resources available to the candidate blades. For example, a trunk in designer may be configured on the target blade using either Virtual Connect networks mapped to a single port on the blade or a Virtual Connect tunneled trunk network that was defined in IO as carrying the desired networks. Port aggregations/teaming cannot be explicitly defined in infrastructure orchestration designer. Port aggregation/teaming is primarily an operating system configuration action (for example, adding the NICs to a vswitch). This is best accomplished through naming conventions and customized Operations Orchestration workflow scripts to configure the OS networking. A VLAN is carried by one or more Virtual Connect tunnel networks or other trunk networks in the environment. A VLAN cannot be a trunk network. Matrix infrastructure orchestration contains VLAN tagged network support to meet the following objectives: Enable IO to be used to deploy a VM Host with a multi-network trunk connected to a server blade network port Allow an IO administrator to manage and present trunk networks to be used in IO physical provisioning Allow an architect to create a physical service template that designates a trunk network Provision physical server blades with a trunk connected to at least one of the available NIC ports Enable Hyper-V VM provisioning to a Hyper-V server with a VLAN tagged virtual network switch Provide the VLAN ID when creating a Hyper-V VM on a VLAN tagged virtual switch Matrix infrastructure orchestration adds the ability to detail trunk networks and create templates that represent a trunk network connected to a Virtual Connect server blade. From these definitions IO is then able to orchestrate the creation of a Virtual Connect profile with a trunk connection. With properly configured networks, the service request contains sufficient information to enable HP Operations Orchestration workflows scripts to configure the Virtual Connect server blade for trunk aware applications, primarily VM Host clusters. 100 Configuring Matrix infrastructure orchestration

101 Virtual Connect tunneled trunk configuration HP Virtual Connect provides two types of network configurations to present a VLAN trunk to a VC server blade. The HP Virtual Connect Ethernet Cookbook illustrates these two configurations in scenarios 1:6 (mapped trunk) and 2:4 (tunneled trunk). A Virtual Connect tunneled trunk configuration passes tagged traffic through to the target interface unrestricted. The definitions of the VLANs can only be found on the LAN-side switch and configured in the host-side network stack. VC does not maintain any information on the VLANs. Configuration of the host requires knowledge of the VLANs to use. The definition of the VLANs must be supplied by the administrator in the infrastructure orchestration console or designer, and potentially from external sources, such as LAN management tools. Following is an example of a Virtual Connect tunnel trunk configuration. Configuring Matrix infrastructure orchestration resources 101

102 Physical networks discovered from Virtual Connect are represented as a subnet whether they are a single network or a tunneled trunk network carrying multiple subnets. Matrix infrastructure orchestration represents Virtual Connect networks based on the VC network configuration. Following are characteristics of tunneled trunk Virtual Connect networks: Subnets can be designated as a tunneled trunk Set of subnets carried on the tunneled trunk can be defined Tunneled trunks are designated as "Tunnel VLAN tags" in the network configuration All traffic from an uplink port is tunneled through VC to the downlink port without modifying VLAN tags Cannot be mapped to a multi-network VC profile NIC port Cannot be part of a shared uplink set Virtual Connect mapped trunk configuration A Virtual Connect mapped trunk configuration enables VC to play a more active role managing traffic on the VLANs, including designating one of the VLANs to handle untagged packets from the VM Host. This constitutes hybrid support for both tagged and untagged networks on the VM Host. Shared uplink sets (SUS) are commonly used in this configuration to provide a set of VLANs associated with the trunk. As in the tunneled VLAN trunk case, the list of VLANs must be supplied by the administrator in the infrastructure orchestration console or designer, a defined SUS, or from an external LAN management tool. Matrix infrastructure orchestration represents Virtual Connect networks based on the VC network configuration. Virtual Connect networks capable of being mapped are: Always single network subnets Multiple mapped subnets that are assigned to a single VC server blade NIC port creating a per-vc profile trunk For mapped trunks, each Virtual Connect network defined in the shared up-link set is discovered by Matrix infrastructure orchestration. The mapped trunk to the VC server blade is created as a multi-network containing a subset of the defined networks when the VC profile is created. 102 Configuring Matrix infrastructure orchestration

103 NOTE: In releases earlier than Virtual Connect 3.30, a VC module can be in "Map VLAN Tags" mode or "Tunnel VLAN Tags" mode. Beginning with Virtual Connect 3.30, modules are always in map mode, but a non-shared up-link set network can tunnel VLAN tags from an up-link port through to a down-link port. Configuring trunk and VLAN networks To define trunk and VLAN networks, perform the following steps. For information about support for Hyper-V VLAN tagging, see Configuring trunk and VLAN networks to enable support for Hyper-V VLAN tagging (page 104). 1. Define Virtual Connect networks using Virtual Connect Manager. Tunnel mode: Define each tunnel trunk in VC, which passes tagged packets unmodified. (There is no need to inform VC which VLANs are carried by the tunnel.) Map mode: Define all networks in VC. Each VLAN carried by an uplink is explicitly defined as a VC network. No VC network carries packets from multiple VLANs. 2. Discover Virtual Connect networks by refreshing the infrastructure orchestration console Networks tab. VC networks are displayed as Physical in the Type column. VC networks that are configured as tunnel VLAN tags are displayed as Trunk, Physical in the Type column. Configuring Matrix infrastructure orchestration resources 103

104 3. Define the VLANs that can be carried by one physical network. a. In the infrastructure orchestration console Networks tab, click Create Network. b. Specify a VLAN ID, and set Network Address, Network Mask, Default Gateway, MS Domain, and WINS Servers for that VLAN ID by clicking the appropriate tab and filling in the information. In a multi-home scenario where there are multiple default gateway options, IO determines the default gateway from the network connected to the NIC that is declared as primary. Each Physical network that carries one or more VLANs is a Trunk, Physical network. Newly defined VLANs appear in Networks table, with VLAN displayed in the Type Column. One, and only one, trunk per VLAN implies that a trunk carries either all possible VLANs to every cluster, or networks (such as a deployment network) cannot be shared between trunks in different clusters. Configuring trunk and VLAN networks to enable support for Hyper-V VLAN tagging VLAN tagging is the practice of inserting a VLAN ID into network data to identify the VLAN to which the data belongs. CAUTION: Combining tagged and untagged Hyper-V virtual machines on the same virtual network results in network failures. HP recommends that you maintain a homogeneous network environment among cooperating Hyper-V VM 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. If your environment is configured to use HP NCU to create vnics for each VLAN on Hyper-V VM Hosts (the supported method for VLAN tagging in previous releases), and you upgrade infrastructure orchestration to 7.0, network failures may occur on the Hyper-V VM guests if you attempt to use the new method of VLAN tagging described in the following procedure. The property promiscous.switch.compatibility is included in hpio.properties, located in the default location at..\program Files\HP\Matrix infrastructure orchestration\conf. This property allows administrators who have configured their environment for VLAN tagging using HP NCU to continue to use this method without reconfiguring their Hyper-V systems. 104 Configuring Matrix infrastructure orchestration

105 Table 3 VLAN tagging support using promiscous.switch.compatibility Default value of promiscous.switch.compatibility Set if... Method of VLAN tagging support used by IO with this setting TRUE IO is upgraded to 7.0 and the previous release implemented Hyper-V VLAN tagging support HP NCU is used to create vnics for each VLAN (6.2/6.3 method) FALSE FALSE IO is upgraded to 7.0 and the previous release did not implement Hyper-V VLAN tagging support IO 7.0 is a new installation Hyper-V VLAN discovered vswitch is marked as trunk in IO; VLANs carried by the Hyper-V virtual trunk are defined with VLAN IDs (7.0 method) Hyper-V VLAN discovered vswitch is marked as trunk in IO; VLANs carried by the Hyper-V virtual trunk are defined with VLAN IDs (7.0 method) Perform the following steps in the infrastructure orchestration console to enable support for VLAN tagging. This is the 7.0 or later method. 1. Discover virtual networks by refreshing the infrastructure orchestration console Networks tab. 2. On the Networks tab, select the 802.1Q network carrying multiple VLAN IDs and click Edit Network. 3. Select the Trunk tab. 4. Check the Trunk checkbox, and click Save. 5. Define the VLANs that can be carried by the Hyper-V virtual trunk network. a. On the Networks tab, click Create Network. b. Specify a VLAN ID, and set Network Address, Network Mask, Default Gateway, MS Domain, and WINS Servers for that VLAN ID by clicking the appropriate tab and filling in the information. c. Click Save. Configuring software resources VM templates Confirm that the software resources you intend to use in Matrix OE service templates are recognized by Matrix infrastructure orchestration. Click the Software tab and review the contents listed; you may select each row and inspect the details provided. Confirm that the VMware vcenter or Hyper-V VM templates you intend to use in Matrix OE service templates are recognized by Matrix infrastructure orchestration. By default, all templates are available to all users at the service provider level. To change this, see Enabling template assignment restriction for specific service provider level users (page 105). For public cloud bursting to Savvis, you must maintain a local VMware vcenter or Hyper-V template for each template that will be uploaded to Savvis. Any change to the Matrix OE recognized template location must be kept in sync with the configuration files that map the local (proxy) software choices to Savvis deployment images. In preparation of bursting to Savvis confirm that the VM templates you intend to map to Savvis templates are recognized by Matrix infrastructure orchestration. Enabling template assignment restriction for specific service provider level users To enable template assignment restriction for specific service provider level users, follow these steps: 1. Open the hpio.properties file in c:\program Files\HP\Matrix infrastructure orchestration\conf\. Configuring Matrix infrastructure orchestration resources 105

106 2. Change the template.access.restricted line from false to true. 3. Save the file. It is not necessary to restart services. HP Server Automation If you have configured an HP Server Automation deployment server, you should see software resources listed here with the Source Type of SA. HP Cloud Services and Amazon EC2 software If you have configured HPCS or EC2 adapters, you should see software resources listed here with the Source Type of Cloud. 106 Configuring Matrix infrastructure orchestration

107 12 Creating Matrix infrastructure orchestration templates and services Matrix OE infrastructure orchestration designer enables you to plan and design multi-server, multi-tier infrastructures using a drag-and-drop interface. The infrastructure can include virtual servers (either private or public cloud) and c-class server blades using Virtual Connect. Matrix OE infrastructure orchestration users can provision services using IO templates. In this section you will define and automatically deploy a service using Matrix OE infrastructure orchestration. So far, your environment is configured only to recognize local resources. However, the interfaces and processes described in this section are the same for both private resources and public cloud providers. Once configured to communicate with a supported bursting destination provider, the user interfaces will adjust to show cloud resources and related attributes, and disable some fields that do not apply. The overall process of designing and provisioning those services follows the same structure regardless of the destination. This guide describes configuring and testing a local (private) service. For instructions and examples on configuring a public cloud bursting destination see Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and HP Cloud Services or Amazon EC2 and Cloud bursting with HP CloudSystem Matrix infrastructure orchestration and Savvis. Using infrastructure orchestration designer From the CMS desktop, double-click the HP Matrix IO Designer icon. Connect using an account that has been granted membership in either the HPIO_Architects or HPIO_Administrators group. The infrastructure orchestration designer window contains three major frames: The Components frame displays the icons for the logical objects used to design a template. The Existing Templates frame provides a list of available templates. The right hand frame is a template design area that you use to build the template by dragging and dropping components on to it. In the following sections, you will be using only the components that represent virtual resources for deploying to hypervisor hosts (or bursting partners). Creating a template with a virtual machine The example here will help you create one very simple single-server service template that contains only a virtual machine. Using infrastructure orchestration designer 107

108 1. In the infrastructure orchestration designer window, click New to receive instructions on how to begin. 2. Drag one of each of the Virtual Server Group, and Network components onto the area where the instructions are displayed. After dropping the Virtual Server Group, a Virtual Storage boot disk will automatically be dropped next to it and connected. 3. Connect the Virtual Server Group to the Network. 108 Creating Matrix infrastructure orchestration templates and services

109 4. For each of the three components, right-click to use the pop-up menu and fill in the required attributes. Start by setting the network attributes for the Network (Network1). Select an appropriate network; there are no other attributes to specify. You can optionally include the cost values shown. 5. When finished with the attributes for the Network, use the pop-up menu and fill in the required attributes for the Virtual Server Group. Creating a template with a virtual machine 109

110 Edit the Group Name. TIP: When adding the Server Group Name, use short strings that have meaning within the service template. A number is appended to the server group name to indicate the name of a server within it. These names are only seen in infrastructure orchestration designer and administrator GUIs. For example: WebServer. You may optionally specify how many VMs and their resource requirements. Incomplete required items show on the pop up with a red "X." Verify the Server Type is Virtual. If High Availability is marked, during service creation the VMs in this group are provisioned to a clustered VM host and registered with an optional Server Health Check Operations Orchestration workflow. The optional Server Health Check workflow is not included in the default installation but can be created at a later time. If no clustered VM hosts are available, service creation would fail. 6. You must fill in the Network tab for the Virtual Server Group (SvrGrp1). There are three parts to the virtual machine's hostname. The first part is defined in this service template. The second part is specified by a user's service creation request. The third part is a numeric suffix based on the number of servers created for this server group. The help text shown explains that a "#" character is used in a template Hostname as a replacement string indicating where to place the requestor's portion of the hostname. Although the requestor replacement string is optional, if you do not use it then this template can only 110 Creating Matrix infrastructure orchestration templates and services

111 be provisioned once without generating duplicate hostnames. The replacement string can be positioned anywhere in the template hostname. Keep in mind that all the pieces must be short enough to fit into common network hostname restrictions. 7. For the Network Interface Assignment Type, choose the appropriate setting depending on how you configured the IO environment: DHCP Static Automatic Indicates that IP addresses are allocated dynamically to servers connected to the subnet using DHCP. Indicates that the architect assigns the IP addresses used by each server connected to the subnet. Using static IP addresses creates a one-off template that can only be provisioned one time. Indicates that IO automatically selects the static IP addresses to be allocated from the static IP address range set for the network. 8. On the Software tab, select the appropriate template to use. Only VM templates created using the procedure described earlier are listed. You also see the physical server deployment jobs, but they are unavailable for selection during the creation of a VM. Creating a template with a virtual machine 111

112 When you use a Windows template, you must also choose a sysprep file. Click the Change button. Customization choices display that correspond to the sysprep files you created in Configuring for virtual machine provisioning (page 84). After you select the template, if the Virtual Storage size is insufficient, it will be increased to at least the size of the template. 9. Set the attributes for the Virtual Storage. Note that the Storage Type must be Virtual. Notice that the Disk is bootable checkbox is already checked, which indicates that the software is required to be bootable. Storage Volume Names is an optional feature for the boot disk. Enter the VM host storage volume names separated by commas. During provisioning, IO allocates virtual storage from storage volumes with names that match the storage volume names of the boot disk. 112 Creating Matrix infrastructure orchestration templates and services

113 10. After you have completed these steps, note that Validation Status is green. If it is not green, click Show Issues and resolve those items. 11. Optionally, decide if you need to allow the service requestor to customize the attributes of the service at request time. Currently supported customizations include Network, Processors, Memory, Operating System and Storage Volume Name. Creating a template with a virtual machine 113

114 12. Select the Published box, name the template, and then click Save As. This template is now available for deployment by authorized users. Creating a service request The Matrix infrastructure orchestration Self Service Portal enables you to create infrastructure services from published templates. 1. From the CMS desktop, double-click the Matrix infrastructure orchestration Self Service Portal icon. 2. You must login using an account that is a member of the HPIO_Users group. 3. Click the Templates tab to see the available published templates. 4. Select a template. 5. To create the service request: a. Click Create Service. b. Enter the Service Name. This name is used by users, administrators, and in progress logs to identify this request. c. Enter the address to be notified of progress. Separate multiple addresses with commas or semicolons. Do not use a final semicolon after the last address. d. Enter a Hostname Completion string to be used to replace the "#" specified in the Virtual Server Group hostname field. 114 Creating Matrix infrastructure orchestration templates and services

115 e. Select the appropriate resource pool from the Available Server Pools, and click Submit. 6. Select the My Requests tab to view status of the request. After initial validation has completed and resources have been reserved, you will see your request is paused in the queue for approval. Creating a service request 115

116 Approving and automating deployment 1. To approve the service request, connect to HP SIM as the infrastructure orchestration administrator and use the Tools Infrastructure Orchestration menu to view the pending request queue. Click the Requests tab. 2. Select the Create request in the queue, and click Approve. After the job has been approved, it automatically proceeds to be built and deployed with no further interaction required. As provisioning proceeds, the requesting user can monitor progress of the deployment on the infrastructure orchestration self service portal My Requests tab. When the job completes, the requester receives an notification and their request queue status updates in sync with the administrators status. 116 Creating Matrix infrastructure orchestration templates and services

117 The VM is now fully available for use by the requester. The running service is visible in the infrastructure orchestration Services tab. The virtual machine current status and resources can also be seen in the HP Matrix OE visualization view. (From HP SIM, select Tools HP Matrix OE visualization.) As an Administrator, you might want to complete the recognition of the new Virtual Machine by initiating an HP SIM Discovery operation on the IP address now in use by the new guest. Alternatively, you can execute the discovery task for the host. Until the new guest is fully recognized on the network, it will be displayed using a generated name comprising of its VM Hostname, infrastructure orchestration service name, and the virtual machine name. Once discovered, all of the HP Matrix OE visualization attributes will be filled in. Approving and automating deployment 117

118 118 Creating Matrix infrastructure orchestration templates and services

119 13 Configuring multi-tenancy (optional) Multi-tenancy allows data center resources to be dynamically and securely shared among separate tenants by providing each organization with a virtual infrastructure orchestration system. In Matrix infrastructure orchestration, tenants are known as organizations. For detailed information, see the Multi-tenancy in HP Matrix OE Infrastructure Orchestration at Creating an organization Using the infrastructure orchestration console, the service provider administrator must create an organization in the Organization tab before an organization administrator can log in to the infrastructure orchestration organization administrator portal. An organization is created with a unique name and a unique identifier of the form org<string of decimal digits>. The organization identifier is used in the name of the local Windows Group on the CMS that contain the organization administrators and users. The organization identifier is unchanged when an organization is renamed. The local groups have names of the form <organization_id>_administrators and <organization_id>_users To create an organization: 1. From the infrastructure orchestration console Organization tab, click Create. The Create new Organization page appears. 2. In Organization Name, enter a name for the new organization. 3. Click Add. Creating an organization 119

120 4. (Optional) Add organization administrators. Enter the name of a local user, Windows Active Directory (AD) user, or Windows AD group, and click Add User or Add Group as appropriate. 5. (Optional) Add organization users. Enter the name of a local user, Windows AD user, or Windows AD group, and click Add User or Add Group as appropriate. 6. Click Close. To delete an organization, the organization must have no compute resources assigned to it, and all services must have been deleted. Assigning users to an organization Using the infrastructure orchestration console, the service provider administrator populates the organization's Administrators and Users groups by adding pre-existing local Windows users. If the CMS is part of a Windows domain, pre-existing Active Directory users and groups can also be added to the organization's Administrators and Users groups. When a Highly Available (HA) CMS fails over to a new node, the Matrix OE-created organization's Administrators and Users Windows groups for each organization are automatically created on the new node. Groups that are no longer valid for the currently active node are removed. Groups are not removed from inactive nodes (nodes in the cluster that are not currently used by the CMS). 120 Configuring multi-tenancy (optional)

121 NOTE: After any changes are made outside of the organization administrator portal, run ioexec sync Organizations, or wait for IO to synchronize the changes automatically. The default time interval is 600 seconds (10 minutes). To set another value, add the following line to the..\ Program Files\HP\Matrix infrastructure orchestration\conf\hpio.properties file. In this example, the new time interval is 1200 seconds (20 minutes). organization.sync.interval=1200 Adding resources to an organization The service provider administrator assigns a compute resource to an organization on the infrastructure orchestration console Organization tab. The newly created organization contains, by default, Maintenance and Unassigned pools. To be assigned to an organization, a compute resource must be in the service provider Unassigned pool, and cannot be in use. After it has been assigned to an organization, the compute resource appears in the organization s Unassigned pool. The Organization tab also allows resources to be removed from an organization. These removed compute resources move to the service provider s Unassigned pool. The service provider administrator can assign and unassign: A set of compute resources, where a compute resource can be a virtual machine host, a physical blade, an ESX Resource Pool or a Cloud Resource. A compute resource cannot be shared among organizations. The service provider and organization administrator can create resource pools. A compute resource can be assigned to or from an organization if it is not in use and it is in an Unassigned pool. Only an organization s Unassigned pool is visible to the service provider administrator. HP recommends that all nodes of a cluster are kept at the service provider level or assigned to the same organization. A set of networks. Networks can be assigned to multiple organizations. Sharing networks among organizations is not prevented by infrastructure orchestration; it is a service provider policy decision. The service provider administrator can assign a network to one or multiple organizations. An in-use network can be de-assigned from an organization. Any existing services are unaffected, but organization users can no longer create services that use the network. If the service provider policy forbids network sharing, then any services using the network must be deleted before the network is re-assigned to another organization. A set of infrastructure orchestration templates. IO templates can be assigned to multiple organizations. To assign or unassign resources: 1. From the infrastructure orchestration console Organization tab, select an organization. The organization name is displayed in the right Organization list. Only compute resources that are not in-use (are not supporting a service) can be moved. 2. From the Service Provider list, select a compute resource, network, or template. 3. Select one or more resources by expanding a tree and selecting a resource in the left Service Provider list and clicking the right arrow. This places the selected resource in the right Organization list, assigning the resource to the organization. Selecting a resource and clicking the left arrow unassigns the resource from the organization. Continue to select resources, using the arrows to adjust the resources assigned to the organization. Adding resources to an organization 121

122 4. Click Save. For more information about multi-tenancy, see the whitepaper Multi-Tenancy in HP Matrix Operating Environment Infrastructure Orchestration at Configuring multi-tenancy (optional)

123 14 Troubleshooting Troubleshooting tools To begin troubleshooting perform the following tasks: Verify that you have the supported versions of hardware, software, and firmware. For additional information, see the HP Insight Management Support Matrix at matrixoe/docs. Review known issues. For information, see the five sets of release notes in Table 1 (page 7). Ensure that DNS is configured for all managed systems. Without DNS configuration, issues can occur, such as HP Matrix OE logical server management failure and Matrix infrastructure orchestration deployment failure. Ensure time synchronization has been performed among the CMS, managed systems (including ESX hosts), VMware vcenter Server and System Center Virtual Machine Manager. Failure to do so results in errors in both vcenter and Insight Management. Ensure you have configured VMware vcenter Server and System Center Virtual Machine Manager settings in HP SIM including the credentials and URL for vcenter. Without this configuration, issues can occur, including infrastructure orchestration, VM provisioning failure. After these initial steps use the following tools to identify and correct additional potential issues. Using Insight managed system setup wizard The managed system setup wizard is useful for troubleshooting many kinds of problems, including licensing issues, agent installation and configuration, SSH configuration. The wizard s analysis page will determine what configuration is needed for the user s selected features. Some of these steps will be manual, but most will be performed automatically if you use the wizard. The managed system setup wizard eases configuration of systems for many Insight Management products and features. After you successfully complete the managed system setup wizard, the selected systems are configured with the management features you specify. The managed system setup wizard does the following: Configures agents necessary to enable the management features Applies software licenses as needed Completes any additional configuration steps You can run this wizard at any time to change the configuration or management features of your systems. You should run the wizard to configure a managed system each time its operating system is installed, updated, or changed. You can also use this wizard to diagnose configuration issues with your systems. Troubleshooting tools 123

124 Before running the Insight managed system setup wizard Before running the managed system setup wizard to configure and manage systems, you must have cleanly discovered all systems in HP SIM and have licenses available for all management features. The target systems of this wizard must be fully discovered and should have valid credentials stored within HP SIM. If credentials are not stored in HP SIM, you can enter credentials for the system during the Set Credentials step of the wizard. NOTE: The managed system setup wizard requires that systems be successfully discovered in HP SIM before running the wizard. You must provide software licenses for any products that require them. Licenses may be needed in the form of either 5x5 keys or Software Distributor license bundles (for HP-UX). For 5x5 keys, the managed system setup wizard presents a dialog for entering license keys to be consumed. You also can add 5x5 keys using the License Manager (select the DeployLicense Manager menu and click the Add Licenses button). Running Insight managed system setup wizard Using the Insight managed system setup wizard requires that you authorize the System Setup toolbox authorization in HP SIM on each managed system that will be configured using the managed system setup wizard. To add licenses using the managed system setup wizard you must have the following HP SIM Users tab option checked: User can configure CMS security access such as creating, modifying or removing other users. This option is configured using the Options Security Users & Authorizations menu. One instance of the managed system setup wizard can run at a time in HP SIM software. You can start the managed system setup wizard by selecting Configure Managed System Setup Wizard...from the HP SIM top menu to start the managed system setup wizard as shown in Figure 1 (page 124). If you have selected any systems in HP SIM then you are prompted to verify the target systems before the wizard begins. Otherwise you are prompted to select the target systems that the managed system setup wizard begins. Figure 1 Configure Managed System Setup Wizard The managed system setup wizard introduction page gives an overview of the wizard. Using vseassist The software tool vseassist, available from the HP SIM GUI or the vseassist command on the command line, verifies that Matrix Operating Environment components are installed, configured, 124 Troubleshooting

125 Use cases and operating correctly on the CMS. This reduces the time to fix the most common problems. Also, vseassist verifies communications between the CMS and selected managed nodes to: Ensure that communications paths are available. Exercise select providers and agents. Ensure that providers and agents produce expected results to selected tests. In addition, vseassist performs basic network configuration checks to ensure that there are no issues resolving the CMS host name or IP address. Finally, the vseassist tool verifies the configuration and operation of managed systems by executing vseassist on the managed node. Execute vseassist from the HP SIM graphical user interface, from the command line on the CMS, or from the command line on a managed node. You can use the vseassist tool to check the configuration and operation of the software in three ways: Verify the CMS configuration. Verify the communication between the CMS and selected managed nodes. Verify the configuration of selected managed nodes. This can be performed remotely from the CMS or directly on a managed node, as shown in Figure 2 (page 125). Figure 2 CMS to managed node communication Troubleshooting tools 125

126 Running the vseassist tool HP recommends the following diagnostic procedure to troubleshoot Matrix OE. 1. If you have administrative access to the CMS, execute the following command from the command line: VSEINSTALLDIR\bin\vseassist a where VSEINSTALLDIR is the location of the installation. The default install location is C:\Program Files\HP\Virtual Server Environment. As an alternative to running the vseassist a command which runs all verifications, you can select vseassist from the graphical user interface. This command verifies the following information: Matrix OE management software configuration on the CMS Communication with all systems in the All VSE Resources collection Matrix OE managed node software configuration on managed nodes The vseassist -a command may take multiple hours to complete. The time consumed is dictated by the number of managed nodes and their state. Improperly configured systems will take longer. 2. After running this command, see the summary output and examine the log file for any issues. The log file is located at: C:\Program Files\HP\Virtual Server Environment\logs Follow the resolution steps in the log to correct any issues. Check the configuration of the CMS, managed nodes, and CMS to managed node communication using the following steps: 1. Resolve all issues with the configuration of the CMS by performing one of the following steps: From the HP SIM graphical user interface, select Diagnose Troubleshoot Matrix Operating Environment Check CMS Configuration Alternatively, on the CMS command line enter: vseassist -c As the vseassist diagnostic tool is running, the results of each check will be displayed on the screen. Figure 3 (page 127) shows a CMS configuration verification. 126 Troubleshooting

127 Figure 3 CMS configuration verification example 2. After you have resolved all issues with the CMS configuration, find any communication issues between the CMS and managed nodes by performing one of the following steps: From the HP SIM graphical user interface, select the managed nodes, then from the Diagnose menu, select Troubleshoot Matrix Operating Environment Check CMS to Managed Node Communication. Alternatively, from the CMS command line, specify the HP SIM managed node names or system collection names to be tested using the following command: vseassist -l { -n nodename -g collectionname...} 3. After you have resolved the communication issues between the CMS and managed nodes, verify the Matrix OE software configuration on managed nodes by performing one of the following steps: Diagnostics in vseassist From the HP SIM graphical user interface, select the managed nodes, then from the Diagnose menu, select Troubleshoot Matrix Operating Environment Check Managed Node Configuration Alternatively, from the CMS command line, specify the HP SIM managed node names or system collection names to be tested using the following command: # vseassist -r { -n nodename -g collectionname...} This section describes the types of diagnostics performed by the vseassist tool. Troubleshooting tools 127

128 Windows CMS checks You can perform checks of the CMS configuration in two ways: Select Diagnose Troubleshoot Matrix Operating Enviornment Check CMS Configuration from the menu. Enter vseassist -c on the command line. The vseassist tool performs the following checks of the CMS configuration when invoked using the Check CMS Configuration menu or the vseassist c command: HP SIM running HP SIM memory configuration Matrix OE running Local host name resolution File system free space Java JRE installed HP Insight Control virtual machine management running HP Insight Control virtual machine management responsive Virtual Connect Enterprise Manager responsive If Matrix infrastructure orchestration is installed on the CMS, the vseassist tool automatically invokes an additional tool called ioassist to check the configuration of Matrix infrastructure orchestration. Using ioassist, these additional checks are performed: Sysprep files for virtual software customization exist HP SIM running and responding VM hosts and physical servers available and visible to infrastructure orchestration Deployable software available and visible to infrastructure orchestration Deployment servers available and visible to infrastructure orchestration Virtual Infrastructure servers available and visible to infrastructure orchestration Database running and responding Matrix infrastructure orchestration Windows groups exist The Matrix infrastructure orchestration Administrators user is authorized for infrastructure orchestration toolbox in HP SIM Networks available and visible to infrastructure orchestration Networks configured and ready for infrastructure orchestration usage Matrix infrastructure orchestration logical server management running and responding HP Operations Orchestration installed and configured for Matrix infrastructure orchestration Matrix infrastructure orchestration workflows imported into Operations Orchestration Insight Control virtual machine management running and responding Storage pools available for each existent VCDG Matrix infrastructure orchestration user pools exist and available as resources Matrix infrastructure orchestration user access to infrastructure orchestration user pools Matrix infrastructure orchestration templates available and published for infrastructure orchestration users 128 Troubleshooting

129 Managed node checks When you invoke the vseassist tool by selecting the Check Managed Node Configuration menu item or entering vseassist r on the command line, vseassist performs the following checks of managed node configurations: Windows managed nodes CMS host name resolution WMI running WMI responsive System type matches HP SIM system type Compare CMS and managed system nslookup SSH configuration validation File system free space Windows 2003 SP2 Installed Compare CMS and managed node time Utilization Provider validation Linux managed nodes CMS host name resolution HP Web-Based Enterprise Management running WBEM responsive System type matches HP SIM system type Compare CMS and managed system nslookup SSH configuration validation File system free space Check VMware ESX Version Compare CMS and managed node time Communication checks When you invoke the vseassist tool by selecting the Check CMS to Managed Node Communication menu item or typing vseassist l on the command line, vseassist performs the following checks of communication between the CMS and managed nodes: Managed system host name resolution WBEM port open WBEM authentication SSH port open SSH authentication SNMP port open Troubleshooting tools 129

130 Trial or permanent license applied Insight Control virtual machine management accessibility Matrix OE capacity planning data collection Check VMware ESX version Using System Management Homepage troubleshooting tools Running Configure or Repair Agents The Configure or Repair Agents feature enables you to configure or repair agents in Windows, Linux, HP-UX, and ESX hosts. The Configure or Repair Agents tool enables you to install agents or repair the communication problems between HP SIM and the systems you are managing. You can start the Configure or Repair Agent by selecting Configure Configure or Repair Agents...from the HP SIM menu as shown in Figure 4 (page 130). Figure 4 Configure or repair agents The Configure or Repair Agents feature adds the security and trap community strings and trust settings to the target systems, but it does not replace existing settings. Use the Replicate Agent Settings feature in HP SIM to replace existing settings and other settings on target systems. Use the Configure or Repair Agents tool to send test SNMP traps from Windows systems with Insight Management Agents and send WBEM test indications from Windows and HP-UX systems with WBEM providers installed. You can also configure WBEM certificates for HP-UX systems and WBEM/WMI users for Windows systems with WBEM Providers for Windows Server 2003 and Windows Server You can also use the Configure or Repair Agents tool to register a virtual machine host with Insight Control virtual machine management. The Configure or Repair Agents feature on a Windows CMS also enables you to install various agents and providers on an HP ProLiant or HP Integrity system with a Windows operating system, including: HP Web-Based Enterprise Management Providers for Windows Server 2003 and Windows Server 2008 OpenSSH HP VCA for Windows SNMP Insight Management Agentss for Windows To run Configure or Repair Agents against a system, you must have authorization to run the Configure or Repair Agents tool. You must have administrator privileges for Windows operating 130 Troubleshooting

131 systems on the target systems to configure or repair the agent settings. You must have root privileges for HP-UX and Linux systems. The SSH protocol is required to install the agent software to support the visualization and configuration features of HP Matrix OE visualization and to collect utilization data for Matrix OE capacity planning. If your environment precludes installing OpenSSH on the Windows server blades, see the white paper Insight Dynamics VSE without OpenSSH on HP ProLiant and Integrity Servers Running Microsoft Windows at SupportManual/c /c pdf. If you select Configure SSH access, you must select one of the following options: Host based authentication for SSH For this option to work, the user name and password provided must be an administrative level account. For Linux or HP-UX targets, it must be the root account and password. User based authentication on the managed system If you do not want all users that have login access to HP SIM to run the tool and you would like to control which users need to have access, this option is more secure. You can configure SSH only if the OpenSSH service is running on the managed systems. You can install OpenSSH on Windows operating systems by running Install Open SSH from Configure or Repair Agents or by selecting Deploy Deploy Drivers Firmware and Agents Install Open SSH. Using Manage Communications Sometimes running the Configure or Repair Agents tool is not sufficient. To troubleshoot communication problems between the CMS and targeted systems, use the Manage Communications feature of HP SIM at Configure Manage Communications as shown in Figure 5 (page 131). Figure 5 Manage Communications For each failed communication function, troubleshooting information is available. You can reconfigure certain communication settings, launch agents, and push certificates to target systems. For each selected target system, Manage Communications displays the following information: Communication status Manage Communications table Identification Identification status Events Ability to receive events Troubleshooting tools 131

132 Run Tools Version Control System type Operating system name Ability to run tools Availability of software and firmware inventory data Manage Communications main page buttons Advise and Displays diagnostic results and troubleshooting tips Repair Quick Repair Update Print Launches Configure and Repair Agents tool Refreshes communication status Creates printer-friendly version of lists in new window The communication status between the CMS and the targeted systems appears in the table. Place your mouse over a status icon to display available information explaining the status. If you click the status icon, the Advise and Repair section appears with the corresponding tab open. For example, if you click a status icon in the Run Tools column, the Run Tools tab opens in the Advise and Repair section instead of the default Identification tab. System Name This column contains the actual system name of selected systems. When you place the cursor over the system name, the FQDN appears, which helps differentiate between two or more systems that share the same system name. Identification The Identification column includes status information on the state of an identification process. Identification attempts to determine the system type, the management protocols a system supports using the configured credentials, and the operating system and version loaded, and other basic system attributes. The Identification column also indicates if the system is associated with another system. The status in this column is a roll-up of the status of all available protocols. The statuses are analyzed based on the status itself, the system type, the system operating system, and instrumentation options. Status icons do not appear for systems that cannot have a status, such as, complexes, enclosures, and racks. The identification status updates each time an identification task runs. Events The Events column indicates if the CMS can receive events from the target systems. This status reflects the sending of SNMP traps and WBEM indications. Run Tools The Run Tools column indicates if the CMS can run tools locally on target systems, such as HP System Management Homepage. Communication issues in this column usually relate to security and trust relationships. Version Control The Version Control column indicates the availability of the software and firmware inventory data for target systems. The status is collected and stored during data collection. This is only valid for Windows systems with a version control agent installed. System Type The System Type column displays the system type, for example, Server or Desktop. 132 Troubleshooting

133 The Unmanaged system type indicates systems that have no management protocol that HP SIM can detect, for example, systems with no SNMP, WBEM, DMI, or SSH. The Unknown system type indicates that none of the built-in or STM tasks could identify the system. However, some management protocol was detected on the system. Checking log files The following log files can help you understand system activities: Matrix infrastructure orchestration C:\Program Files\HP\Matrix infrastructure orchestration\logs hpio-controller.log Rolling logs Search for WARN, ERROR hpio.log Service startup Shutdown Logins Matrix OE C:\Program Files\HP\Virtual Server Environment\logs hp_lsa_service.log Service starts Stops vselog.log vselog.lsm.log LSM utility logs LSMUTIL is a script that you can run from the command line or from a DOS bat file. LSMUTIL reads information from the logical servers tables in the Matrix OE database. Based on the option you select, the script exports information about logical servers, storage pool entries, or managed resources. For a list of logical server, enter lsmutil list ls xml file ls.log For a list of storage pool entries, enter lsmutil list spe xml file spe.log For a list of managed resources, enter lsmutil list -cr xml file cr.log VMware logs HP recommends checking the VMware logs on the ESX hosts, which are managed by HP SIM. VMware logs are located on the ESX server at /var/log/vmware/hostd.log. For information about uploading the VMware log files, see the VMware Knowledge Base article Collecting diagnostic information for VMware Infrastructure SDK at the following website: To collect VMware log files, execute the vm-support a command. Troubleshooting tools 133

134 Insight Control virtual machine management event viewer logs Insight Control virtual machine management provides the following event logs from system drive\windows\system32\winevt\: Logs\Application.evtx Logs\System.evtx Microsoft-Windows-Hyper-V-VMMS-Admin Insight Control virtual machine management provides the following management logs C:\Program Files\HP\Insight Control virtual machine management\log\: vmm_controller.log hpvmmsvc.log Rolling logs Search for WARN, ERROR hpvmm.log Service startup Shutdown HP SIM C:\Program Files\HP\Systems Insight Manager\logs Mxdomainmgr.log Mx.log Verifying the CMS configuration Synopsis Matrix infrastructure orchestration utilizes the vseassist tool and the Systems Insight Manager Diagnose menu to help 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 Matrix OE Check CMS Configuration. Additionally, when installing infrastructure orchestration on the system, a set of checks related to the infrastructure orchestration configuration and resource availability execute to help identify any issues with the infrastructure orchestration configuration. IOAssist has its own command line interface. However, IOAssist is primarily used through vseassist, either through the Systems Insight Manager interface or through the vseassist command line interface (vseassist -c). For more information on vseassist, see the vseassist(1m) manpage and the Matrix Operating Environment help system. ioassist [ f <filter> ] [ o <output type> ] ioassist g <group id> [ f <filter> ] [ o <output type> ] ioassist c <check id> [ d] [ f <filter> ] [ o <output type> ] ioassist L <locale> Where: [ f <filter>] filters the output by levels. Valid entries are ALL, PASS, INFO, WARN, and FAIL. [ g <group id>] executes checks on a specific group. [ d] forces the execution of whole dependency checks (used only with c). 134 Troubleshooting

135 [ c <check id>] performs a verification of the check identified by the check identification number provided. [ L <locale>] displays output in the appropriate language (en for English, ja for Japanese). [ o <output type>] displays output in a format, DEFAULT or XML. [ l ] list the available checks and groups, or checks available for a given group. [ h ] Displays help and exits. Example: Running all checks in CLI..\Documents and Settings\Administrator>ioassist -g all HP IO Assist tool Executing checks... Checking group all Check: HP IO Database Responsiveness Result: PASS Actions: Check: HP SIM Responsiveness in Primary CMS Result: PASS Actions: Check: HP IO And Domain User Groups Configured Result: WARN Actions: There are no users or user groups in the HPIO_Architects group in the Primary CMS. Assign a valid user or user group to the HPIO_Architects group. There are no users or user groups in HPIO_Users group in the Primary CMS. Assign a valid user or user group to the HPIO_Users group. (...) Amount of checks executed: 18 Checks provided with infrastructure orchestration Name IO CMSs Communication IO Database Responsiveness IO Responsiveness IO User Groups Configured IO ToolBox Configured in HP SIM Insight Control virtual machine management software Responsiveness Virtual Infrastructure Server Configuration Deployment Services Logical Server Management Communication Description Verifies that the CMSs are communicating correctly in a federated environment Validates the infrastructure orchestration configuration file for database communication Verifies the communication between infrastructure orchestration and Systems Insight Manager Verifies if infrastructure orchestration user groups are properly configured in Windows for basic operations Verifies if infrastructure orchestration user groups are properly configured in Systems Insight Manager for infrastructure orchestration operations Verifies the communication between infrastructure orchestration and virtual machine management Verifies the virtual infrastructure server configuration in Systems Insight Manager Verifies if deployment servers are available for automatic operating system deployment Verifies if infrastructure orchestration is able to communicate with logical server management Verifying the CMS configuration 135

136 Name IO Network Configuration IO User Pools Configuration - Resources Availability IO User Pools Configuration - Users Assigned to Pools Operations Orchestration Workflows Configuration Virtual Software Customization IO Template Available and Published Storage pools assigned to VCDG Available Networks Servers Availability Available Software Description Verifies if at least one network is properly configured in infrastructure orchestration for provisioning with minimum required parameters Checks for the availability of resources on infrastructure orchestration User Pools (virtual and physical) Checks if there are users assigned to the infrastructure orchestration pools Checks available infrastructure orchestration workflows configured in Operations Orchestration Checks if virtual software customization is properly configured for automatic operating system deployment Checks if there are published and valid infrastructure orchestration templates Checks if there are Storage pools available on each VCDG for physical provisioning Checks if there are available physical, virtual, and mixed networks for provisioning Checks if there are virtual and physical servers available for infrastructure orchestration operations Verifies if deployment servers contain software for automatic operating system deployment For each check performed, one of the following status indicators displays: PASS No configuration issue was found. FAIL A serious configuration problem was found, which must be resolved for correct operation. WARN A configuration problem was found. The problem may 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. Service provisioning For assistance on specific issues encountered during service provisioning, see the troubleshooting information in the HP Matrix Operating Environment 7.2 Infrastructure Orchestration User Guide Logical server features For issues with the logical servers features in the HP Matrix OE visualization software, see the troubleshooting information in the HP Matrix Operating Environment 7.2 Logical Server Management User Guide. Troubleshooting procedures Agent and communication troubleshooting Install OpenSSH on Windows 2008 managed node through Configure or Repair Agents fails Issue When using Configure or Repair Agents to Install OpenSSH onto a managed node with Windows Server 2008 installed, the installation fails if you enable the UAC setting and you use a domain 136 Troubleshooting

137 account for the credentials. The installation works if you use the local admin (root) account for the managed node. Suggested actions Disable UAC on the managed node. For information, see the Microsoft TechNet article User Account Control Step-by-Step Guide available at the following website: Use the local admin account of the managed node for the credentials. A local user or domain account becomes locked out Issue When running discovery or identification tasks in HP SIM, a local user or domain account becomes locked out. Possible causes The credentials provided to HP SIM are incorrect. Suggested actions If using system credentials, verify that the credentials are correct for the managed nodes (sign-in credentials are used for WBEM/WMI access). 1. Open a command prompt on the CMS, and enter mxnodesecurity -l -p <sign-in> to see the names of the devices that have credentials manually set. If any of the managed node server names or IP addresses appear, then credentials have been manually set on the system and could potentially be incorrect. 2. In the Search box in HP SIM, type the name of the server in question from the command line output, and then access the System page for that device by clicking on the name. 3. Click Tools and Links, and then click System Credentials under the HP SIM Pages section. 4. Select the checkbox in the gray area to select all credentials, and then click Edit system credentials. 5. In the Sign In credentials section, if there is a user name listed, it was manually configured by a user. If there are no credentials listed, either the Discovery Task or Global Credentials are being used. 6. You can manually change the credentials by editing them and then clicking OK, or you can remove the username and password (and confirmation) data, and then click OK. If you remove the system credentials, HP SIM uses the Discovery (recommended) or Global credentials information, if configured. WBEM/WMI authentication and communication issues Issues HP SIM cannot connect to the WBEM/WMI data on a managed node. This causes HP Matrix OE visualization to display warnings on the utilization meters and prevents Matrix OE capacity planning from collecting utilization data from the managed systems. Matrix OE capacity planning reports a WBEM communication error such as: Capcollect report this Error: System information is not available from the WBEM provider. Collection from this system cannot proceed until this situation is corrected. Discovery tasks report invalid WBEM/WMI credentials. Vseassist reports a WBEM authentication failure. Troubleshooting procedures 137

138 Possible causes WMI Mapper settings are incorrect. The WBEM provider is not properly installed or configured on the managed node. The credentials provided to HP SIM are incorrect. Suggested actions 1. Verify that the WMI Mapper settings are correct: a. In HP SIM, verify that the WMI Mapper IP address is configured correctly in Options Protocol Settings WMI Mapper Proxy. The WMI Mapper IP address is the IP address of the CMS and must reside on a network subnet that has connectivity to all the managed systems. The host name shown must be the FQDN associated with that IP address. If the IP address is incorrect or does not match the host name, delete the WMI Mapper Proxy setting and enter a new one. b. Determine the FQDN by which HP SIM knows the CMS. In HP SIM, use the Search tool to find the CMS and mouse over the System Name to see the FQDN known to HP SIM. If the CMS FQDN does not match the host name shown in the WMI Mapper Proxy configuration screen, re-discover the CMS using the FQDN or IP address of the WMI Mapper: Navigate to Options Discovery. If necessary, create a new discovery task for the CMS using the FQDN or IP address of the WMI Mapper, and run that task. c. In the HP SIM All Systems view, select the CMS, and then select Options Identify Systems to run the Identify Systems task against the CMS. In the Task output, verify that the following message appears: Running WBEM rules based identification. Got ComputerSystem WBEM/WMI data from the system. This validates that the CMS is communicating to the WMI Mapper. 138 Troubleshooting

139 2. Ensure that the WBEM provider is not missing from the managed node. Run vseassist l n nodename (or select the managed systems from the HP SIM user interface, and then from the Diagnose menu, select Troubleshoot Matrix Operating Environment Check CMS to Managed Node Communication). If vseassist reports a WBEM authentication failure for the CMS, ensure that the FQDN by which HP SIM knows the CMS corresponds to the IP address of the WMI Mapper: Determine the FQDN by which HP SIM knows the CMS: In HP SIM, use the Search tool to find the CMS and mouse over the System Name to see the FQDN known to HP SIM. Determine the WMI Mapper settings: In HP SIM, navigate to Options Protocol Settings WMI Mapper Proxy. If a mismatch is determined, either reconfigure the WMI Mapper or re-discover the CMS using the FQDN or IP address of the WMI Mapper. For example, in HP SIM, navigate to Options Discovery. If necessary, create a new discovery task for the CMS using the FQDN or IP address of the WMI Mapper and run that task. 3. If the target system has been identified as WBEM enabled, but the credentials are failing for the target system, perform the following steps: Verify the credentials and identify the target system again. The password might be incorrect on the System Credentials page. To access, select Options Security Credentials System Credentials. Communication with HP SIM server has been lost Issues The HP SIM portal relies on the CMS to respond quickly to all requests. Browser performance degrades when CMS responses are delayed. The browser appears to lock up completely when CMS responses are delayed. The browser displays the message, Communication with the HP SIM server has been lost, even though the CMS might be responsive to other browser sessions. Possible causes This could be a temporary condition due to CMS or network congestion, or CMS restart. Retrying after a short period might resolve the issue. On a LAN, the browser receives a CMS response to most requests within 10 to 100 milliseconds. Requests that involve database queries or secondary network communication might take a few seconds to respond. There are situations that might result in particularly slow response times. For example: Viewing large collections of systems or events Specific and custom database queries taking an unexpectedly long time Many users simultaneously accessing a shared resource, such as the database Network delays Pages that retrieve data using WBEM or SNMP Webagent and display the results (for example, System Properties) can take a long time, especially when the requests are destined to time out. Troubleshooting procedures 139

140 Suggested actions By default, web browsers (such as Microsoft Internet Explorer 7 and earlier and Mozilla Firefox 2 and earlier) limit themselves to two simultaneous connections to a single web server. If two requests are outstanding, any additional requests wait until one of the current connections completes. This is by design and is in agreement with the HTTP 1.1 specification. Increase the maximum number of server connections in both Internet Explorer and Firefox. Though you can increase this number into the hundreds, HP recommends that you do not exceed 10 connections. For more information, see: How do I configure Internet Explorer to download more than two files at one time? available at the following website: For Firefox's Network.http.max-persistent-connections-per-server available at the following website: Restart the HP SIM service by restarting HP SIM in the Windows Services interface on the CMS. Notes: Other reasons why the browser might lose the connection with the CMS include the following: The CMS is shut down or restarted. The network connection between the browser and CMS is broken. If the system running the browser hibernates (or sleeps), it loses connection with HP SIM. If the browser is going through a web proxy, the proxy may be obtrusively slow to respond at some point over an extended period. For more information, see the following: HP SIM online help (troubleshooting) HP Systems Insight Manager User Guide at sim/docs No buffer space available, maximum connections reached Issue A CMS server running Windows Server 2008 R2 with infrastructure orchestration generates the following error while attempting to open a new socket connection: java.net.socketexception: No buffer space available (maximum connections reached?) Possible causes This error can occur after approximately 20 days or more of continuous operation. If this error occurs, additional sockets cannot be opened causing failures and preventing the Matrix OE software stack from functioning. NOTE: This is a known issue with certain Microsoft operating systems. Although this has been seen in Matrix OE, it has also been reported in other (non-hp) software programs. 140 Troubleshooting

141 As the failure occurs, the following error may be seen in the HP SIM log mxdomainmgr.0.log: 9/13/11 4:26:58 PM An error occurred during a workload repository operation. java.rmi.connectioexception: Exception creating connection to: CPVC-MTRX01.support.local; nested exception is: java.net.socketexception: No buffer space available (maximum connections reached?): connect (4 occurrences) Suggested actions Reboot the CMS. Microsoft has released a Hot Fix that prevents the error and messages from occurring while attempting to open a new socket connection. See the Knowledge Base Article , Kernel sockets leak on a multiprocessor computer that is running Windows Server 2008 R2 or Windows 7 at the following website: The Hot Fix that corrects the issue is included in the article with the process to apply the Hot Fix: For more information, see Customer Advisory c , HP Insight Dynamics - The HP Insight Dynamics Fails Due to Socket Exception No Buffer Space Available Error When Installed on HP ProLiant Servers Running Windows Server 2008 R2 or Windows Server 2008 R2 SP1 at the following website: Server blade serial number is not added on ESX or Hyper-V managed nodes Issue After HP SIM discovery, the blade's serial number is not added on the VMware ESX or Hyper-V nodes. Possible cause HP SIM does not have the enclosure and blade bay information to associate it to ESX or Hyper-V nodes. Suggested action 1. Discover the enclosure which is supporting the blade. 2. After discovery, go to HP SIM / All systems page and check if the bay was associated correctly. 3. If the problem persists, select the blade which does not have the serial number and start an identify request. From HP SIM, select Options Identify Systems. Insight Control virtual machine management registration for ESX or Hyper-V nodes fail Issue Insight Control virtual machine management registration for ESX or Hyper-V nodes fail. Possible cause For ESX, VMware vcenter settings are not configured in HP SIM. For Hyper-V, WMI proxy services are not running on Hyper-V. Troubleshooting procedures 141

142 Suggested actions For ESX: 1. Start discovery task for the vcenter server using the appropriate credentials. 2. From HP SIM, select Options VME options Add or edit VME Credentials. 3. Attempt Insight Control virtual machine management registration again. For Hyper-V: 1. Go to the Hyper-V server and start the WMI proxy services. a. Select Start WMI Mapper. b. Select Start WMI Performance Adapter. c. Select StartWindows Management Instrumentation. 2. Attempt Insight Control virtual machine management registration again. Matrix OE troubleshooting Matrix infrastructure orchestration troubleshooting Password is blank on provisioned VMs with Windows 2008 R2 and above provisioned VMs Issue If a VM is provisioned with Windows 2008 R2 or above from infrastructure orchestration without setting any password in the sysprep file, one of the following occurs: VM deployed on ESX/ESXi hosts boot up and users can log in with a blank password. VM deployed on Hyper-V boot up and prompt the user to set a password. Possible cause Microsoft removed the option password never Expires in Windows 2008 R2 and higher (as part of sysprep). VMware overrides the option prompt for a password on the next boot. Suggested actions Do one of the following: Specify an explicit password is specified in the Sysprep.ini file for any deployment of a VM that has an operating system Windows 2008 R2 or higher operating system, or Specify an empty string password in the sysprep.ini file, which results in the prompt for a password on the next boot from VMware. Microsoft SCVMM templates do not appear in the infrastructure orchestration software tab Issue Not all SCVMM templates are seen in the infrastructure orchestration software tab. Possible cause When SCVMM templates do not have the Virtualization Platform set to "Hyper-V", then these templates are not listed in the infrastructure orchestration software tab. 142 Troubleshooting

143 Suggested actions 1. Open the powershell command prompt for virtual machine management in the SCVMM server. 2. Type the following in the command prompt: get-vmmserver ComputerName localhost and then press Enter. get-template select -Property Name and then press Enter. This lists the templates in SCVMM. get-template select -Property Name, VirtualizationPlatform and then press Enter. The templates with Virtualization Platform as Hyper-V will be listed in the infrastructure orchestration software tab. Matrix infrastructure orchestration service creation fails in the target reconfiguration phase Issue Service creation intermittently fails when a service is created with Red Hat Enterprise Linux 6 OS. Possible causes During the service creation process, the target server fails to shut down in the reconfiguration phase due to an issue with the HP Health Agents versions 8.70 and older. Suggested actions 1. Identify the failed target servers in the Maintenance server pool. a. Browse to Tools Infrastructure orchestration from the HP Matrix Operating Environment browser window. b. Click on the Servers tab. c. Expand the server pool by name Maintenance. d. Note the names of servers in this server pool; these are the serial numbers of the servers. 2. Delete the logical servers from Matrix OE visualization. a. Browse to Tools HP Matrix OE visualization. b. Select Logical Server from the Perspective drop-down box. c. Identify the logical server entries where the name starts with Clean-me and contains the previously noted serial number. d. Select these logical servers and delete them by navigating to Delete Delete Logical Server from within the HP Matrix OE visualization screen. 3. After the logical servers are successfully deleted, move the servers from the Maintenance pool to an appropriate server pool. a. Navigate to Tools infrastructure orchestration Servers. b. Select the server pool where the servers from the maintenance pool will be moved. c. Click Modify Pool button. d. Select Maintenance from the drop-down list. e. Select the server that needs to be moved from the list displayed and click the >> button. f. Save the server pool. 4. Retry the service creation. Matrix infrastructure orchestration service creation fails with Error powering on logical server Issue A create service request fails for an ESX VM template with automatic OS deployment. The following error is displayed: Failure: Error powering on logical server. The start function on virtual machine vm-name failed: VMware ESX Server cannot open the virtual disk Troubleshooting procedures 143

144 disk-name for clustering. Please verify that the virtual disk was created using the 'thick' option. Cannot open the disk disk-name or one of the snapshot disks it depends on. Reason: Thin/TBZ disks cannot be opened in multiwriter mode. This error may occur when no virtual machine licenses are available on the target VM Host. Possible cause VMware ESX Server 3.5 is the target VM host, which is no longer supported by infrastructure orchestration. Suggested action Update the VM host to a supported version of ESX, or edit the infrastructure orchestration service and select a different resource pool that contains an ESX VM host with a supported version of ESX. For a list of supported versions, see HP CloudSystem Matrix Compatibility Chart at Matrix infrastructure orchestration service creation fails in the VM customization phase Issue The service creation failure is due to one of the following issues. Service creation fails when a Virtual Machine is created on a Hyper-V host. Service creation fails during the customization phase of deploying virtual machines. The VMware fault fault.customizationpending.summary displays in the Insight Control virtual machine management log files. Failure in customizing a Windows Server 2008 virtual machine. VM console displays the following error message: Windows could not parse or process the unattend answer file for pass [specialize]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup]. 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 causes Linux VMs are not supported by the Matrix Operating Environment. 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. The incorrect product key was specified for the operating system in the HPIO sysprep file. The Hyper-V host is configured with a password that contains or characters. Windows sysprep files are not added. Suggested actions Verify that you are provisioning a guest operating system supported by HP CloudSystem Matrix. For VMware ESX VMs, verify the source VM being used to create the template has the VMware Tools installed and configured. For Linux VM guests, ensure the vmware-config-tools.pl command was executed after installing the tools. 144 Troubleshooting

145 Verify the source VM being used to create the template has been stopped or paused (not suspended) before creating the template. Verify the source VM being used to create the template has been properly shut down before creating the template. When guests are not gracefully shutdown or halted it can cause customization phases to fail. Verify that the product key (and any other configuration option) being used in the HPIO sysprep file functions with the VM by performing the following test. In vcenter or vsphere: Locate the original VM that was used to create the Insight Control virtual machine management template that is experiencing the failure. Right-click the VM, and select Template Clone to Template. This action creates a vsphere template of the VM. Create a new VM from this vsphere template in vsphere. During the VM creation wizard, select the option to customize the VM and input the requested customization parameters. If this VM customization process fails, deployment in infrastructure orchestration will not be successful. Correct the vsphere customization issues, and create a new Insight Control virtual machine management template from the functional VM. Proceed with deployments from infrastructure orchestration. For VMware VMs, VMware vcenter Server must have Sysprep tools installed on the vcenter management server in the VMware VirtualCenter\sysprep\svrOS folder. For Microsoft Hyper-V, Microsoft Sysprep tools are required on the HP CMS in the Insight Control virtual machine management sysprep folder. Change the password on the Hyper-V host to something that does not contain or characters. 1. Select the Hyper-V host from the system list. 2. Edit the system credentials. Go to Options Security Credentials System Credentials and select the Hyper-V host from the list. 3. Change the sign-in credentials and save the new credentials. Wait a few minutes for the host to complete re-identification. 4. Start the Matrix infrastructure orchestration service request. Verify the Windows sysprep files have been added: For Hyper-V VMs running Windows, go to the CMS and copy the sysprep files to C:\ Program Files\HP\Insight Control virtual machine management\ Sysprep\2003. For VMware ESX VMs running Windows, go to the system which has Virtual Center installed and copy the sysprep files to the following paths: Virtual Center 4.x and 5.x: C:\Documents and Settings\All Users\ Application Data\VMware\VMware VirtualCenter\sysprep\svr2003 For more information about customization or configuration, see the HP Matrix Operating Environment Infrastructure Orchestration User Guide at NOTE: The HPIO C:\Program Files\HP\Matrix infrastructure orchestration\ conf\sysprep.inf file must be edited to specify additional customizations for Windows virtual machines. Without this edit, a newly provisioned system halts during first boot waiting for a key. For details, see HP Matrix Operating Environment Infrastructure Orchestration User Guide at Provisioned VMs fail due to improper VM host hardware configuration Issue Troubleshooting procedures 145

146 Microsoft Virtual Network Manager fails to load during rapid provisioning of VMs on ProLiant servers with Hyper-V Windows 2008 R2 SP1/SP2. The following error message displays: Task for logical server has failed, failure virtual machine hardware was not configured correctly. The customization of the provisioned VM's fail and the infrastructure orchestration service request fails. Suggested actions 1. Install HP NCU V10.20 or newer. For installation instructions, see the following website: cc=us&prodtypeid= &prodseriesid= & switem=mtx-5221f1131e1e46a49d795ccded&prodnameid= &swenvoid=4064& swlang=8&taskid=135&mode=3 2. Enable the TCP offload feature in the Hyper-V host. Access the Network Adapter Properties window for the VM host. Click the Advanced tab. Select the TCP offload options in the Property list and select Enable as the Value. Click OK. 146 Troubleshooting