Installation and User's Guide

Transcription

1 IBM Systems Director VMControl Installation and User's Guide Version 2 Release 3

2

3 IBM Systems Director VMControl Installation and User's Guide Version 2 Release 3

4 ii IBM Systems Director VMControl: Installation and User's Guide

5 Contents Chapter 1. About this publication Who should read this book Conentions and terminology Chapter 2. IBM Systems Director VMControl V Oeriew of IBM Systems Director VMControl... 3 What's new in IBM Systems Director VMControl. 4 Understanding the components of your IBM Systems Director VMControl enironment... 5 License information Accessibility features Planning for IBM Systems Director VMControl.. 14 Hardware and software requirements IP6 compliance Supported SMI-S proiders Supported irtualization enironments Recommendations for configuring IBM Power Systems that are using IBM Systems Director VMControl Preparing your Power Systems enironment for serer system pools Installing and uninstalling IBM Systems Director VMControl Hardware and software requirements Downloading IBM Systems Director VMControl 53 Installing IBM Systems Director VMControl.. 53 Installing IBM Systems Director VMControl agents and subagents Uninstalling IBM Systems Director VMControl 79 Uninstalling IBM z/vm Manageability Access Point Agent Upgrading and migrating to IBM Systems Director VMControl Updating IBM Systems Director VMControl Naigating and managing VMControl resources.. 85 Managing storage Storage system pools oeriew Managing storage using IBM Systems Director VMControl and IBM Tioli Storage Productiity Center Managing storage system pools Managing irtual serers Creating a irtual serer Editing a irtual serer Permanently deleting a irtual serer Relocating irtual serers Managing power operations on irtual serers 101 Managing irtual appliances and workloads Creating and discoering image repositories Deleting image repositories Getting started with irtual appliances and workloads Managing irtual appliances Managing irtual appliances with Tioli Proisioning Manager for Images Managing workloads Managing serer system pools Configuring SAN storage for serer system pools Creating serer system pools Renaming a serer system pool Serer system pool optimization Adding hosts to serer system pools Remoing a host from a serer system pool Putting a host into maintenance mode Remoing a host from maintenance mode Permanently deleting a serer system pool Troubleshooting and support Installation troubleshooting Import troubleshooting Capture troubleshooting Deploy troubleshooting Virtual serer troubleshooting Virtual appliance troubleshooting Reference VMControl commands OVF specifications for IBM Systems Director VMControl Publications and related information How to send your comments Chapter 3. Notices Trademarks Index Copyright IBM Corp. 2009, 2010 iii

6 i IBM Systems Director VMControl: Installation and User's Guide

7 Chapter 1. About this publication Who should read this book Conentions and terminology This publication proides instructions for installing and using IBM Systems Director VMControl Express Edition, IBM Systems Director VMControl Standard Edition, and IBM Systems Director VMControl Enterprise Edition. Use VMControl to manage irtual serers, irtual appliances, workloads, and system pools across multiple hardware platforms and irtualization enironments from one location. This documentation describes how to use the Web interface as well as the command-line interface (smcli) to complete tasks. You can also find troubleshooting information, and a reference section that contains IBM Systems Director VMControl-specific requirements for Open Virtualization Format (OVF) irtual appliance packages. This book is for system administrators and operators using the IBM Systems Director VMControl plug-in for IBM Systems Director to capture, import, and deploy irtual appliances in the data center. These notices are designed to highlight key information: Note: These notices proide important tips, guidance, or adice. Important: These notices proide information or adice that might help you aoid inconenient or difficult situations. Attention: These notices indicate possible damage to programs, deices, or data. An attention notice appears before the instruction or situation in which damage can occur. Copyright IBM Corp. 2009,

8 2 IBM Systems Director VMControl: Installation and User's Guide

9 Chapter 2. IBM Systems Director VMControl V2.3.1 IBM Systems Director VMControl is designed to simplify the management of workloads in your IT enironment. Use IBM Systems Director VMControl Express Edition, IBM Systems Director VMControl Standard Edition, and IBM Systems Director VMControl Enterprise Edition to manage irtual serers, irtual appliances, workloads, and system pools across multiple hardware platforms and irtualization enironments from one location. Oeriew of IBM Systems Director VMControl This section proides an oeriew of IBM Systems Director VMControl Express Edition, IBM Systems Director VMControl Standard Edition, and IBM Systems Director VMControl Enterprise Edition, including accessibility and license information. IBM Systems Director VMControl is a cross-platform suite of products that assists you in rapidly deploying irtual appliances to create irtual serers that are configured with the operating system and software applications that you want. It also enables you to group resources into system pools, which enable you to centrally manage and control the different workloads in your enironment. VMControl Express Edition includes features that were formerly part of IBM Systems Director irtualization manager. It enables you to complete the following tasks: Create irtual serers. Edit irtual serers. Manage irtual serers. Relocate irtual serers. IBM Systems Director VMControl Standard Edition is a licensed feature of VMControl. VMControl Standard Edition enables you to complete the following tasks: Discoer existing image repositories in your enironment and import external, standards-based images into your repositories as irtual appliances. Capture a running irtual serer that is configured just the way you want, complete with guest operating system, running applications, and irtual serer definition. When you capture the irtual serer, a irtual appliance is created in one of your image repositories with the same definitions and can be deployed multiple times in your enironment. Import irtual appliance packages that exist in the Open Virtualization Format (OVF) from the Internet or other external sources. After the irtual appliance packages are imported, you can deploy them within your data center. Deploy irtual appliances quickly to create new irtual serers that meet the demands of your eer-changing business needs. Create, capture, and manage workloads. IBM Systems Director VMControl Enterprise Edition allows you to complete the following tasks. Create serer system pools, which enable you to consolidate your resources and workloads into distinct and manageable groups. Copyright IBM Corp. 2009,

10 Deploy irtual appliances into serer system pools. Manage serer system pools, including adding hosts or additional storage space and monitoring the health of the resources and the status of the workloads in them. Group storage systems together using storage system pools to increase resource utilization and automation. Manage storage system pools by adding storage, editing the storage system pool policy, and monitoring the health of the storage resources. You are granted a 60-day ealuation period for VMControl Standard Edition and VMControl Enterprise Edition when you download and install VMControl. For more information, see the License Information topic. The IBM Systems Director VMControl Summary page guides you through the tasks you need to complete to get started using the product: installing agents, discoering or creating image repositories, capturing or importing irtual appliances. Once you are up and running, the Summary page gies you quick access to the main tasks and iews that you can use in IBM Systems Director VMControl. The Summary page also helps you manage your licenses for VMControl Standard Edition and VMControl Enterprise Edition. For more information, see "Naigating and managing VMControl resources." Related information: IBM Systems Director Downloads What's new in IBM Systems Director VMControl IBM Systems Director VMControl Version and IBM Systems Director VMControl Version proide a number of new features and enhancements. Before using IBM Systems Director and VMControl See the "Read me before using IBM Systems Director and Systems Director plug-ins" page on the IBM Systems Director wiki to find out about known limitations and requirements (including their solutions or workarounds) for IBM Systems Director and Systems Director plug-ins, including VMControl. Functional enhancements for VMControl VMControl proides the following functional enhancement: Support for deploying to existing irtual serers that use N-port ID Virtualization (NPIV). This support is restricted to HMC-managed systems in a NIM-based Power Systems irtualization enironment. Note: VMControl supports NPIV-attached disk only for storage deices managed by IBM Tioli Storage Productiity Center. Functional enhancements for VMControl VMControl proides seeral functional enhancements including the following tasks and commands: Support for integration with Tioli Proisioning Manager for Images: Support for discoering the Tioli Proisioning Manager for Images serer. Support for Tioli Proisioning Manager for Images launch-in-context tasks for VMware and Hyper-V irtual appliances. 4 IBM Systems Director VMControl: Installation and User's Guide

11 Support for storage copy serices-based AIX on Power Systems: Support for import, capture, deploy, and relocate, and for serer and storage system pools. Support for creating Power irtual serers that use preexisting storage olumes. Support for deploying to new irtual serers that use preexisting storage in the following Power Systems enironments: AIX using NIM AIX and Linux using storage copy serices (SCS) Support for creating and deleting image repositories using the new Create and Delete Image Repository wizards. This function is supported in storage copy serices (SCS) enironments. Support for z/vm : Support for the following workload functions: create, edit, delete, start, stop, and capture. Support for host and irtual serer performance-related monitors with z/vm 6.1. Support for IP6 in all irtualization enironments. Support for deleting a preiously deployed workload, and for permanently remoing the irtual serers and irtual disks of a workload. Support for placing irtual serers into a serer system pool when grouping the irtual serers into a workload for Power Systems. Support for optimizing a serer system pool manually or on an automatic repeating basis to improe performance. Support for image repositories with storage copy serices functions, which can increase the speed of the deploy operation. New CLI commands: chtpmfisr lstpmfisr lsaquery mkrepos mkaquery rmrepos rmaquery rmworkload For more information about the new CLI commands, see VMControl commands. Support for these functions aries among irtualization enironments and depends on whether you install the Express, Standard, or Enterprise Edition of IBM Systems Director VMControl. For more information, see Oeriew of IBM Systems Director VMControl and Supported irtualization enironments. Related information: Read this before installing IBM Systems Director and Systems Director plug-ins Understanding the components of your IBM Systems Director VMControl enironment IBM Systems Director VMControl enables you to manage arious components in your irtualization enironment. Chapter 2. IBM Systems Director VMControl V

12 Related information: Managing irtual enironments Virtual serers A irtual serer is associated with a host system. The host must be part of a irtualization enironment that is supported in IBM Systems Director. An operating system and other software can be installed on a irtual serer. In a Power Systems enironment, a irtual serer is called a logical partition or partition. In z/vm and VMware enironments, irtual serers are often called irtual machines. A irtual serer is the logical equialent of a physical platform. After IBM Systems Director discoers a host, it continues the discoery process for all the irtual serers that are associated with the host. After irtual serers are discoered, they can be powered on and turned off through IBM Systems Director. In addition, you can edit resources that are assigned to irtual serers, and in some irtualization enironments you can relocate a irtual serer from one host to another. You can also create additional irtual serers to meet your needs. The following diagram shows a irtual serer with an operating system and software application installed. Virtual appliances A irtual appliance is a ready-to-deploy operating system and software package that is stored by IBM Systems Director VMControl. A irtual appliance contains an image of a full operating system, and can contain software applications and middleware. A irtual appliance also contains metadata describing the irtual serer that the image requires. VMControl enables you to capture a irtual appliance from a irtual serer already deployed with an image, capture a irtual appliance from a single-irtual serer workload, or import a irtual appliance package that was created outside of VMControl. The following diagram shows a irtual appliance. 6 IBM Systems Director VMControl: Installation and User's Guide

13 Importable irtual appliance packages must conform to the Distributed Management Task Force (DMTF) Open Virtualization Format (OVF). They also must abide by the limitations and restrictions imposed by VMControl. For more information, see "OVF specifications for VMControl." You can deploy a irtual appliance to a host, to a serer system pool, or to existing irtual serers. When you deploy a irtual appliance to a host or a serer system pool, a new irtual serer is created for you. Additionally, the deploy operation in VMControl creates a workload to represent the deployed irtual appliance. The information described in this topic applies in a Power Systems enironment. Some limitations exist in other enironments. Workloads A workload represents one or more irtual serers that can be monitored and managed as a single entity. For example, you can manage a workload that might contain both a web serer and a database serer. You can start and stop a workload, and thus the irtual serers it contains, as one entity. You can monitor the oerall state and status of the workload by iewing the Workloads dashboard. A workload is automatically created when you deploy a irtual appliance. You can also create a workload by grouping one or more irtual serers that are not already part of an existing workload. The following diagram shows a workload created when a irtual appliance is deployed. The resulting workload contains a single irtual serer. Chapter 2. IBM Systems Director VMControl V

14 The following diagram shows a workload created by grouping three irtual serers. A workload must meet the following specifications: An application instance can be part of only one workload. For example, an application instance such as a database cannot be shared by more than one workload. A workload can consist of only irtual serers. A workload cannot consist of physical machines. 8 IBM Systems Director VMControl: Installation and User's Guide

15 A workload can consist of only irtual serers that meet the requirements for being captured. All irtual serers in a workload must either be members of a serer system pool, or must exist outside of a serer system pool. A workload cannot consist of both types of irtual serers. A workload in a serer system pool that supports the resilience policy can only contain irtual serers that also support the resilience policy. For information about the resilience policy, see "Relocating irtual serers using the resilience policy." To create a workload by grouping one or more irtual serers, use the Group as Workload wizard. You can specify certain criteria for the workload that you want to create. Then, you can select one or more irtual serers that match the criteria and add them to the workload. You can choose from the following criteria: This workload can be captured After selecting this option, you can select a single irtual serer from a filtered list of irtual serers that support the VMControl capture task. After the workload is created, you can capture it and deploy it in the future. This workload can be actiated for resilience policy and its irtual serers will be managed by the serer system pool After selecting this option and selecting a serer system pool that will manage the irtual serers, you can select additional irtual serers from a filtered list of irtual serers that support the resilience policy. System pools A system pool groups similar resources, so that you can manage the resources within the system pool as a single unit. You can create storage system pools and serer system pools. To use storage system pools and serer system pools together, you must first create the storage system pool. Then, when creating a serer system pool, you can select the storage system pool to be used as shared storage for the serer system pool. You can perform basic tasks such as creating and deleting system pools and adding and remoing resources from the system pools. Additional system pool functions are aailable, depending on the type of system pool you hae created. Storage system pools: A storage system pool groups similar storage subsystems with the goal of better resource usage and workload resilience. A storage system pool automates placement within the storage system pool to simplify workload deployment operations. When irtual serers are relocated from one host to another host in a serer system pool, or when a irtual serer is deployed into a serer system pool, the associated storage system pool can simultaneously reallocate storage to maintain workload resilience. Storage system pools enable the use of storage tiers when storage subsystems hae storage pools of differing RAID leels. All storage subsystems within the storage system pool must be part of the same actie zone configuration. Storage subsystems can be members of multiple storage system pools. Chapter 2. IBM Systems Director VMControl V

16 You use the Create Storage System Pool wizard to combine storage and filter storage based on criteria, such as the zone membership. The following diagram shows three storage subsystems in a storage system pool. Storage system pool tasks With IBM Systems Director VMControl you can perform the following storage system pool tasks: Create a storage system pool View a real-time dashboard to iew storage system pools; iew aggregated storage utilization; and check the status of all the resources managed by your storage system pool View and modify the default storage policy for a storage system pool Rename a storage system pool Optimize the serer system to improe performance Add storage subsystems to a storage system pool Permanently delete a storage system pool Related concepts: Storage system pools oeriew Serer system pools: A serer system pool logically groups similar hosts with the goal of better resource usage and workload resilience. A serer system pool comprises multiple hosts and their associated irtual serers, along with attached shared storage. A serer system pool facilitates the deployment of new workloads including automatic placement, as well as relocation of irtual serers from one host to other hosts in the serer system pool. By relocating irtual serers within a serer system pool, you can maintain the high aailability and resilience of your workloads. You use the Create Serer System Pool wizard to group hosts and filter hosts based on their capabilities, such as lie relocation. The following diagram shows three hosts and attached, shared storage in a serer system pool. 10 IBM Systems Director VMControl: Installation and User's Guide

17 Serer system pool criteria A serer system pool must meet the following criteria: A serer system pool groups similar hosts. For example, a serer system pool can contain hosts that are managed by Hardware Management Consoles (HMCs), or it can contain hosts that are managed by Integrated Virtualization Managers (IVMs), but the serer system pool cannot contain both types of hosts. A host can be a member of only one serer system pool. All hosts in a serer system pool must use the same shared storage. A serer system pool that supports a workload's resilience policy must contain hosts that are capable of lie irtual serer relocation. All hosts in a serer system pool must be compatible to share workloads based on specific criteria required by each platform. VMControl helps you create serer system pools with compatible hosts. When you select an initial host for your serer system pool, VMControl proides a list of compatible hosts from which you can select other hosts to add to the serer system pool. Serer system pool tasks With IBM Systems Director VMControl you can perform the following serer system pool tasks: Create a serer system pool View a real-time dashboard to iew serer system pools; iew monitors such as CPU utilization; and check the status of all the resources managed by your serer system pool Rename a serer system pool Add and remoe hosts from a serer system pool Permanently delete a serer system pool Enter and exit maintenance mode for the hosts in the serer system pool Deploy a irtual appliance to the serer system pool Relocation, resilience, and automation in a serer system pool IBM Systems Director VMControl can detect problems that occur in your serer system pool. For example, your serer system pool might experience resource shortages, high CPU utilization, or hardware failures related to processors, memory subsystems, power source, or storage. When these types of problems occur in your serer system pool, irtual serers can be relocated from one host to another host Chapter 2. IBM Systems Director VMControl V

18 to ensure that your workloads remain resilient. You can perform the relocation task manually, you can actiate the resilience policy for the workloads in your serer system pool for relocation that is initiated by the serer system pool, or you can create an automation plan to relocate irtual serers based on eents of your choosing. For more information about relocating irtual serers within a serer system pool, see Relocating irtual serers. License information Licensing for IBM Systems Director VMControl, includes both no-charge (free) and chargeable (for-fee) components. IBM Systems Director VMControl contains a no-charge (free) function and two optional chargeable (fee-based) functions. With the no-charge portion of the product, you can create and manage irtual serers. When you download, install, and begin using IBM Systems Director VMControl Express Edition, you are granted a 60-day ealuation period for IBM Systems Director VMControl Standard Edition and IBM Systems Director VMControl Enterprise Edition. During the ealuation period, you can create, import, and deploy irtual appliances in your enironment and create and manage system pools. When the ealuation period expires, you must purchase a license to continue using VMControl Standard Edition or VMControl Enterprise Edition. The 60-day ealuation period begins the first time you use VMControl Standard Edition or VMControl Enterprise Edition. The number of days left in the ealuation period is displayed on the bottom of the summary page. The day the ealuation period expires is also displayed, as well as information about obtaining a license. If you preiously installed IBM Systems Director VMControl Express Edition V2.3, and you install IBM Systems Director VMControl Express Edition V2.3.1, the 60-day ealuation of IBM Systems Director VMControl Standard Edition and IBM Systems Director VMControl Enterprise Edition does not restart. Instead, the ealuation period for the V2.3.1 is inherited from the V2.3 installation. For example, if you hae 40 days remaining in the ealuation period, installing IBM Systems Director VMControl Express Edition V2.3.1 results in a 40-day ealuation period of that update. Only installing a release leel restarts the 60-day ealuation period. If the ealuation period to expires before you purchase a license for VMControl Standard Edition or VMControl Enterprise Edition, your access to the features that these products proide changes as follows: 12 IBM Systems Director VMControl: Installation and User's Guide

19 Table 1. Access to product features when the ealuation period expires When the ealuation period expires for... You are still able to... You are no longer able to... VMControl Standard Edition View irtual appliances Delete irtual appliances Discoer image repositories Deploy agents View workloads Delete workloads Group by workload Delete repositories Discoer Tioli Proisioning Manager for Images serer VMControl Enterprise Edition View serer and storage system pools Rename and remoe hosts from serer system pools Delete storage system pools Rename storage system pools Deploy irtual appliances Capture Import View, or create workloads Create repositories Use Tioli Proisioning Manager for Images launch-in-context tasks for VMWAre and Hyper-V irtual appliances Create a serer or storage system pool Deploy to serer system pools Monitor serer and storage system pools Add hosts to serer system pools or capacity to storage system pools Edit an existing serer system pool Relocate one or all irtual serers in a serer system pool Enter or exit maintenance mode for hosts in a serer system pool Actiate a resilience policy on a workload Howeer, when you purchase and install the licenses for VMControl Standard Edition or VMControl Enterprise Edition, any image repositories, irtual appliances, or system pools that you created during the ealuation period are still usable. To purchase a license, contact your IBM representatie, an IBM Business Partner, or IBM Americas Call Centers at 800-IBM-CALL. After you purchase a license, you will receie a CD-ROM containing a permanent license key and installation program. After you install the license key, VMControl Standard Edition and VMControl Enterprise Edition function just as they did during the ealuation period. VMControl uses a per-processor or per-serer charging metric, depending on platform. For Power Systems, a processor license is required for eery processor on eery serer being managed by the program. Serers are categorized as small, medium, or large based on criteria such as serer model. For System z serers, a serer license is required for eery serer being managed by VMControl, based on Chapter 2. IBM Systems Director VMControl V

20 the number of Integrated Facility for Linux (IFLs) in use on the serer. Contact your IBM marketing representatie or IBM Business Partner for detailed licensing and pricing information. Related information: IBM Systems Director Downloads IBM Systems Director VMControl Standard Edition Web page IBM Systems Director VMControl Enterprise Edition Web page Accessibility features This topic proides information about the accessibility features of IBM Systems Director VMControl. Accessibility features help users who hae a disability, such as restricted mobility or limited ision, to use information technology products successfully. The IBM Systems Director VMControl plug-in for IBM Systems Director supports the accessibility features that are supported in IBM Systems Director. When using JAWS screen reader with VMControl, follow these tips to improe JAWS usability: Access IBM Systems Director Serer using a supported Mozilla Firefox browser. Enable accessibility features in the IBM Systems Director Web interface: 1. Open Settings > Naigation Preferences. 2. Turn on the following options: Enable tables for accessibility Play sound when data on the page changes Use resource table iew as default iew for topology perspecties 3. Click OK or Apply to sae your settings. For more information, see the Accessibility features for IBM Systems Director topic. Planning for IBM Systems Director VMControl Before installing or using IBM Systems Director VMControl, reiew the hardware, software, and SMI-S proider requirements and the irtualization enironments that VMControl supports and tasks supported for each irtualization enironment. You can also find information about planning for each irtual enironment and learn how you can prepare for creating and using system pools. Related tasks: Installing IBM Systems Director VMControl Installing IBM Systems Director VMControl agents and subagents Hardware and software requirements IBM Systems Director VMControl is installed on systems running IBM Systems Director Serer ersion This topic describes hardware and software requirements that are unique to IBM Systems Director VMControl. For detailed information about the hardware and software requirements for IBM Systems Director, see Hardware and software requirements for IBM Systems Director. 14 IBM Systems Director VMControl: Installation and User's Guide

21 Supported IBM systems IBM Systems Director VMControl is supported on all IBM systems that are supported by IBM Systems Director Serer For detailed information about the systems supported by IBM Systems Director Serer, see Supported IBM systems and products. Supported operating systems IBM Systems Director VMControl is supported on all operating systems that are supported by IBM Systems Director For specific ersions of these operating systems supported by IBM Systems Director Serer, see Operating systems supported by IBM Systems Director Additional prerequisites To use the IBM Systems Director VMControl installation program in a graphical, interactie wizard mode on an IBM Systems Director Serer that is running AIX or Linux, ensure that your system is graphics-enabled. If you want to use the installation program in a non-graphical, silent mode, your system need not be graphics-enabled. Note: For System z systems, xlibs must be installed in 64-bit mode. You can obtain the libstdc++.so.5 file from the compat-libstdc s390x.rpm packet. If you are running the IBM z/vm Manageability Access Point Agent that is supported by IBM Systems Director (or earlier), you must uninstall the agent and install the ersion of the IBM z/vm Manageability Access Point Agent that is supported by IBM Systems Director In addition, ensure that you hae installed a supported ersion of Linux on the z/vm system where you plan to install the IBM z/vm Manageability Access Point Agent. For more information, see Operating systems supported by IBM Systems Director To manage irtual appliances from IBM Systems Director VMControl with Tioli Proisioning Manager for Images, you must first install Tioli Proisioning Manager for Images. For more details, see "Installation requirements" in the IBM Tioli information center. Related information: Performance Tuning and Scaling Guide for IBM Systems Director 6.2 Installation requirements IP6 compliance IBM Systems Director VMControl ersion is IP6 compliant. To find out about general IP6 compliance for IBM Systems Director, see "IP6 compliance." Then, read the following information to understand the restrictions or prerequisites that pertain to VMControl. With VMControl, you can create irtual serers on the types of irtualization hosts shown in the following table. Howeer, the support for specific hosts depends on the networking characteristics of those hosts. Some might hae one or more IP4 network connections, one or more IP6 network connections, one or more dual Chapter 2. IBM Systems Director VMControl V

22 stack network connections, or a combination of these types of connections. The following table describes the leel of IP6 support proided by VMControl Express Edition: Table 2. IP4/6 support proided by VMControl Express Edition Virtualization host type Leel of support or restriction Power Systems No known restrictions VMware (ESX4.x, ESXi 4.x, Sphere 4.x running on Windows Serer 2008, Enterprise, Standard, and Datacenter x64 Editions) Windows Serer 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled, Release 2 IP4 and IP4/6 dual stack support only IP4 and IP4/6 dual stack support only Xen IP4 support only z/vm No known restrictions With VMControl Standard Edition and VMControl Enterprise Edition, you can capture and deploy irtual serers. Howeer, there are restrictions on the IP configurations of the network connections that those irtual serers hae. The following table describes the leel of IP6 support proided by VMControl Standard Edition and VMControl Enterprise Edition when deploying irtual serers. (Capture support is less restrictie in some cases, but deploying the irtual appliances resulting from capture is subject to the same leel of support or restrictions shown below.) Table 3. IP4/6 support proided by VMControl Standard Edition and VMControl Enterprise Edition Virtual serer type Leel of support or restriction Power Systems For NIM-based deploys of AIX irtual serers: Single stack, static IP4 only For storage copy serices (SCS)-based deploys of AIX or Linux irtual serers: Single stack, static IP4, static IP6, or IP6 autoconf OR dual stack, static IP4 with IP6 autoconf only z/vm Single stack, static IP4, IP4 DHCP, or static IP6 only Related information: IP6 (Power Systems) Redbooks wiki IP6 compliance Supported SMI-S proiders IBM Systems Director VMControl and IBM Tioli Storage Productiity Center support different ersions of SMI-S proiders. The following table shows the leels of SMI-S proiders that IBM Systems Director VMControl and IBM Tioli Storage Productiity Center support. For more information, see "Managing storage using IBM Systems Director VMControl." 16 IBM Systems Director VMControl: Installation and User's Guide

23 SMI-S proider LSI G5.02 LSI GG.33 Supported storage deices DS3XXX DS4XXX DS5XXX DS3XXX DS4XXX DS5XXX Support in IBM Systems Director VMControl Support in IBM Tioli Storage Productiity Center Yes Yes Related tasks: Managing storage Supported irtualization enironments This topic lists the irtualization enironments supported by IBM Systems Director VMControl, and the tasks supported in each enironment. Virtualization enironment Supported tasks Create, edit, and delete irtual serers Relocate irtual serers Import irtual appliance packages Capture irtual serers Capture workloads Deploy irtual appliances Start, stop, and delete workloads Create, edit, and delete workloads Create, edit, and delete serer system pools AIX on IBM Power Systems that are under the control of the Hardware Management Console or the Integrated Virtualization Manager Linux on IBM Power Systems that are under the control of the Hardware Management Console or the Integrated Virtualization Manager VMware Center and VMware ESX or ESXi managed by VMware Center or VMware VirtualCenter VMware ESX Windows Serer 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes z/vm Yes Yes Yes 2 Yes 1 Yes 1 1. For systems that are capable of actie partition mobility, with the ActieMobility property set to True. 2. This irtualization enironment does not support encapsulating irtual serers into system pool management in group as workload. Chapter 2. IBM Systems Director VMControl V

24 The following topics proide more information about the support and requirements for each of these irtual enironments. Power Systems requirements and support This topic describes the requirements and support for AIX and Linux irtual appliances, irtual serers, and workloads in the Power Systems irtualization enironment. Related tasks: Preparing to install IBM Systems Director VMControl NIM subagent Installing IBM Systems Director VMControl agents and subagents Requirements and support for AIX using NIM: This topic describes the requirements and support for AIX irtual appliances, irtual serers, and workloads in a Power Systems irtualization enironment that relies on AIX Network Installation Manager (NIM). The following diagram shows a Power Systems irtualization enironment for AIX irtual appliances, irtual serers, and workloads that rely on NIM. IBM Systems Director Serer is installed on a supported serer. IBM Systems Director VMControl Standard Edition or IBM Systems Director VMControl Enterprise Edition is installed on the IBM Systems Director Serer. At least one NIM master is aailable. IBM Systems Director Common Agent and the VMControl NIM subagent are installed on the NIM master. IBM Systems Director Serer recognizes this NIM master as a VMControl image repository. The /export/nim file system in which the irtual appliances are stored must not be NFS mounted to the NIM master. The NIM master exports this file system itself, and NFS does not support export of a mounted file system. 18 IBM Systems Director VMControl: Installation and User's Guide

25 At least one IBM Power 5, 6, or 7 serer or blade exists to host irtual serers that you can capture from and deploy to using VMControl. For blades and low-end Power serers, omit the HMC from the diagram; instead, an Integrated Virtualization Manager (IVM) on the VIOS partition is used. If manual or automated irtual serer relocation capabilities are needed, multiple IBM Power 6 or 7 serers are required. The IBM Power serer is typically attached to a SAN as shown in the diagram, and the SAN is used for the irtual disks of the irtual serers hosted by the IBM Power serer. If you expect to use VMControl Enterprise Edition serer system pools or expect to be able to do irtual serer relocation on your own, then a SAN is required. If not, then disks local to the IBM Power serer and irtualized by the Virtual I/O Serer (VIOS) can be used as an alternatie. Though not shown in the diagram, multiple VIOS partitions and MPIO are supported. Note: The image repository is shown as a stand-alone serer in the diagram. Howeer the image repository can also be on the same IBM Power serer that hosts the AIX irtual serers that you can capture from and deploy to using VMControl. Supported AIX and firmware ersions You must use the following AIX and firmware ersions in this enironment: IBM Systems Director Serer You can use any IBM Systems Director Serer V6.2.1 with IBM Systems Director VMControl V2.3.1 installed. If the IBM Systems Director Serer is an AIX system, you can use any ersion of AIX that is supported by IBM Systems Director Serer V NIM master The NIM master must be AIX 6.1 TL03 or newer. Hardware Management Console (HMC) For POWER5, POWER6 and POWER7, use a minimum of HMC V7R7.2 and all aailable updates. Virtual I/O Serer (VIOS) For POWER5 and POWER6, use a minimum of VIOS and all aailable updates. For POWER7, use a minimum of VIOS and all aailable updates. Virtual appliances You can capture any AIX 5.3, AIX 6.1, or AIX 7.1 irtual serer or workload as a irtual appliance, and you can import or deploy any AIX 5.3, AIX 6.1, or AIX 7.1 irtual appliance. For information about the latest fixes for required software, see "Required Fix Leels for VMControl Dependencies." Supported tasks In this enironment, you can perform these tasks: Create, edit, and delete irtual serers Relocate irtual serers Import a irtual appliance package containing an AIX mksysb image Chapter 2. IBM Systems Director VMControl V

26 Capture an AIX workload or irtual serer, an AIX mksysb image file or NIM resource, or an AIX lpp_source directory or NIM resource Deploy an AIX mksysb or lpp_source irtual appliance Group irtual serers to create a workload Start, stop, and edit a workload Create, edit, and delete system pools Related information: Required Fix Leels for VMControl Dependencies Understanding how VMControl uses AIX NIM: This topic proides an oeriew of how IBM Systems Director VMControl automates AIX NIM for importing, capturing, deploying, and deleting irtual appliances. NIM is widely used to install AIX on Power Systems serers. VMControl support for AIX irtual appliances that contain mksysb and lpp_source images relies on NIM. This topic describes how VMControl uses NIM and eliminates, in most cases, the need to run any NIM commands yourself. VMControl automates the use of NIM. Role of the NIM master There can be one, or more, NIM master in the IBM Systems Director enironment that seres as avmcontrol image repository, and is instrumental in importing, capturing, deploying, and deleting AIX irtual appliances. For each AIX irtual appliance in VMControl, there is a mksysb file or lpp_source directory, and a corresponding NIM mksysb or lpp_source resource on a NIM master. NIM masters that are used by VMControl need minimal configuration. After you set up and discoer your NIM masters, you generally do not need to log on to these NIM masters to create NIM resources or to run NIM commands. VMControl creates the NIM resources and calls the NIM and AIX commands required to accomplish its import, capture, deploy, and delete tasks. Note: IBM Systems Director VMControl update manager also relies on a NIM master for updating AIX systems. VMControl and update manager can use the same NIM master, or separate ones. Import When an AIX irtual appliance package is imported into VMControl, the mksysb file within it is stored on a NIM master in a irtual appliance subdirectory of /export/nim/appliances, along with some other files. Additionally, on the NIM master, VMControl creates the NIM mksysb resource corresponding to the mksysb file using the nim -o define -t mksysb command. Capture With VMControl, you can capture an LPAR running AIX as a irtual appliance containing a mksysb image. To accomplish this capture, VMControl runs commands on the source LPAR and on the NIM master, as necessary. On the source LPAR, VMControl might run the niminit, nimclient, and other commands. On the NIM master, VMControl might run the nimquery and other commands, and 20 IBM Systems Director VMControl: Installation and User's Guide

27 ultimately runs nim -o define -t mksysb to capture the AIX image and create the NIM mksysb resource. VMControl also creates and populates a new irtual appliance subdirectory under /export/nim/appliances. With VMControl, you can also capture a preexisting mksysb file or NIM mksysb resource, or a preexisting lpp_source directory or NIM lpp_source resource, as a irtual appliance. This capability exists in the VMControl command-line interface only with the capturea command. To accomplish this type of capture, VMControl uses an appropriate form of the nim -o define -t mksysb/lpp_source command. As part of the capture operation, VMControl creates and populates a new irtual appliance subdirectory under /export/nim/appliances. Deploy To deploy an AIX irtual appliance, containing a NIM mksysb or lpp_source image, VMControl runs many commands on the NIM master. These commands can include dpasswd, dkeyexch, and dgetmacs. Additionally, VMControl calls the nim -o define and nim -o change commands as necessary to create or update hmc or im, cec, ent, spot, bosinst_data, image_data, adapter_def, script, and standalone NIM resources. Ultimately, VMControl calls nim -o bos_inst to deploy the mksysb or lpp_source image to the target LPAR. Delete To permanently delete an AIX irtual appliance, VMControl remoes the corresponding mksysb or lpp_source resource by running a nim -o remoe command on the NIM master. Furthermore, VMControl remoes the corresponding irtual appliance subdirectory and all its contents from /export/nim/appliances. If the irtual appliance was captured from a preexisting NIM mksysb or lpp_source resource, that resource is not remoed. Similarly, if the irtual appliance was captured from a preexisting mksysb file or lpp_source directory, that file or directory is not remoed. NIM resources This section describes in more detail the NIM resources used by VMControl, and the impact on any NIM resources you might hae created. Generally, because VMControl automates the use of NIM, its use of the NIM master is priileged and it creates, changes, and remoes resources as needed. If VMControl needs any resources that you might hae manually created, VMControl changes and remoes them as necessary. VMControl uses the following NIM resources: standalone resources The standalone resources represent irtual serers. During a capture operation, VMControl remoes the preexisting standalone resource, if present, and creates one itself. When the capture completes, successfully or not, the standalone resource is remoed. During a deploy operation, VMControl creates the required standalone resource if necessary. If the required standalone resource exists, VMControl uses it rather than creating one; howeer VMControl generally changes a preexisting standalone as necessary to perform the deploy. When the Chapter 2. IBM Systems Director VMControl V

28 deploy completes, successfully or not, VMControl remoes the standalone resource, irrespectie of whether it was created or preexisted. ent resources VMControl creates and changes these resources as needed. If ent resources preexist, VMControl uses and changes them as needed. After ent resources exist, whether you hae created them manually or VMControl has created them, VMControl neer remoes them. hmc, im, and cec resources VMControl creates and changes these resources as needed. If they preexist, VMControl uses and changes them as needed. After they exist, whether you hae created them manually or VMControl has created them, VMControl neer remoes them. mksysb and lpp_source resources Any mksysb and lpp_source resources that you might hae created manually are neer remoed by VMControl. When you capture a irtual serer running AIX or import a irtual appliance package containing an AIX image, VMControl creates a mksysb resource while constructing the irtual appliance. If you permanently delete that irtual appliance, VMControl remoes the mksysb resource it had created. If you capture a preexisting mksysb file or lpp_source directory, VMControl creates the corresponding mksysb or lpp_source resource while constructing the irtual appliance. If you permanently delete that irtual appliance, VMControl remoes the mksysb or lpp_source resource it had created. spot resources Any spot resources that you might hae created manually are neer remoed by VMControl. During a deploy operation, VMControl creates a spot for a irtual appliance if none exist. If a spot exists, VMControl uses it rather than creating a spot. When the deploy completes, successfully or not, VMControl leaes the spot intact. If you permanently delete a irtual appliance, the spot that VMControl created for it, if any, is remoed. If the irtual appliance has a spot that you had created, it is not remoed. This latter case pertains to irtual appliances captured from user-created mksysb resources that hae user-created spots. bosinst_data, image_data, and adapter_def resources Generally, these resources are newly created on each deploy, and remoed when the deploy completes, successfully or not. If you create one or more of these resources manually, they are ignored unless you specify them through the optional, deploy-time NIM Resource or Resource Group property of VMControl. The bosinst_data, image_data, and adapter_def resources that you hae created manually, if any, are neer remoed by VMControl. script resources VMControl creates a script resource named mc_config and uses it for all deploys. This script resource is neer remoed. nim_script resource VMControl creates the nim_script if it does not exist and uses it for all 22 IBM Systems Director VMControl: Installation and User's Guide

29 deploys. If the nim_script exists, VMControl ensures that it points to /export/nim/scripts. The nim_script resource is neer remoed. Related concepts: Creating and discoering NIM image repositories for AIX Related tasks: Installing IBM Systems Director VMControl agents and subagents Import support and requirements in a NIM-based Power Systems irtualization enironment: This topic describes the support and requirements for importing an AIX mksysb irtual appliance package in a NIM-based Power Systems irtualization enironment. You can import a irtual appliance package containing an AIX mksysb image for IBM Power irtual serers (logical partitions). You can import this type of irtual appliance package when the following requirements are met: Your irtualization enironment is configured as described in "Requirements and support for AIX using NIM." The irtual appliance package is an Open Virtualization Format (OVF) package containing one, rootg-only AIX mksysb image, and the description of one, single-disk Power irtual serer to accommodate the image. There is sufficient space on the NIM master image repository under /export/nim/appliances to store the AIX mksysb image file associated with the irtual appliance package that you want to import. Related reference: OVF package requirements Capture support and requirements in a NIM-based Power Systems irtualization enironment: This topic describes the support and requirements for capturing AIX irtual appliances in a NIM-based Power Systems irtualization enironment. The result of this capture operation is a irtual appliance that you can deploy to create a new irtual serer. You can create a irtual appliance by capturing any of the following sources: A irtual serer (logical partition) or a workload that contains a irtual serer running AIX or higher You can capture these irtual serers or workloads in the following enironments: A irtual serer (logical partition) on a Power Systems serer that is managed by Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM) A irtual serer on a Power Architecture BladeCenter serer that is managed by IVM Notes: Only single-irtual serer workloads can be captured. Only the root olume group (rootg) of the irtual serer is captured. If rootg spans multiple irtual disks, metadata for just a single irtual disk is saed, albeit large enough to hold the entire rootg. Chapter 2. IBM Systems Director VMControl V

30 When capturing a NIM master and deploying it as a irtual appliance, the deployed irtual serer is not automatically configured to be a NIM master. You must configure the NIM master after it is deployed. For more information, see "Preparing to install IBM Systems Director VMControl NIM subagent." You can use either the VMControl Capture wizard or the Systems Management command-line interface (smcli) capturea command to capture a irtual serer or workload. An existing mksysb image file. You can capture an existing mksysb image file from the following locations: Your IBM Systems Director Serer Your NIM master A Microsoft Windows serer that is sharing the file (if your IBM Systems Director Serer is a Windows system) A web serer Note: You cannot capture an image from a secure web serer. An existing lpp_source directory on your NIM master An existing NIM mksysb resource on your NIM master An existing NIM lpp_source resource on your NIM master Note: You must use the Systems Management command-line interface (smcli) capturea command to capture a mksysb image or resource or an lpp_source resource, or directory. You can perform these capture operations when the following requirements are met: Your NIM-based Power irtualization enironment is configured as described in "Requirements and support for AIX using NIM." The following additional requirements apply when capturing a irtual serer or workload containing a single irtual serer: There is sufficient space under /export/nim/appliances on the VMControl NIM master image repository to store the irtual appliance image that is created by the capture operation. Your VMControl NIM master image repository system is running and has network connectiity to the irtual serer you want to capture. The instance of AIX running on the irtual serer is able to resole the NIM master host name with DNS or the /etc/hosts file. The instance of AIX running on the irtual serer is at a leel that is equal to or lower than the AIX leel that is running on the NIM master. The Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM) that manages the irtual serer that you want to capture is discoered, accessed, and inentoried in IBM Systems Director. Access status is listed as OK. The Power serer hosting the irtual serer must be inentoried in IBM Systems Director. The irtual ethernet adapters of the irtual serer must be connected to the default irtual network switch (ETHERNET0). The irtual serer that you want to capture is running and is discoered in IBM Systems Director. Access status is listed as OK. 24 IBM Systems Director VMControl: Installation and User's Guide

31 The irtual serer that you want to capture is not a full system partition, or the only partition on the host to which all host resources are dedicated. If you are managing multiple NIM masters, the irtual serer that you want to capture is not another NIM master. A NIM master can be captured only if that same NIM master is used as the image repository on which to store the resulting irtual appliance. The maximum file size on the irtual serer is set to unlimited. Notes: You cannot perform the deploy, capture, or relocate tasks concurrently for the same irtual serer. Wait until one of these tasks is complete before beginning another. Single-irtual disk Open Virtualization Format (OVF) packages, irtual serers, and irtual appliances are supported. Single irtual serer OVF packages and irtual appliances are supported. For AIX mksysb OVF packages and irtual appliances, only the rootg olume group is supported. For additional information about using VMControl in a Power Systems enironment, see "VMControl Power Information" in the IBM Systems Director Best Practices Wiki. Related information: VMControl Power Information Deploy support and requirements in a NIM-based Power Systems irtualization enironment: This topic describes the support and requirements for deploying AIX irtual appliances in a NIM-based enironment. You can deploy an AIX mksysb or lpp_source irtual appliance to a new or existing irtual serer in the following enironments: A irtual serer (logical partition) on a Power Systems serer that is managed by Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM). A irtual serer on a Power Architecture BladeCenter serer that is managed by IVM Notes: When capturing a NIM master and deploying it as a irtual appliance, the deployed irtual serer is not automatically configured to be a NIM master. You must configure the NIM master after it is deployed. For more information, see "Preparing to install IBM Systems Director VMControl NIM subagent." You cannot perform the deploy, capture, or relocate tasks concurrently for the same irtual serer. Wait until one of these tasks is complete before beginning another. Deploying to an existing irtual serer You can deploy a irtual appliance to an existing irtual serer when the following requirements are met: Your NIM-based Power irtualization enironment is configured as described in "Requirements and support for AIX using NIM." Chapter 2. IBM Systems Director VMControl V

32 IBM Systems Director VMControl has recognized the NIM master as an image repository in the enironment, the irtual appliance image is present on the NIM master, and VMControl has discoered the image. The NIM master has network access to the target irtual serer and the Hardware Management Console (HMC) or IVM that manages it. If there is a firewall between the NIM master and the HMC, ports 22 and 9735 must be opened in the firewall for SSH and remote irtual terminal communication between the NIM master and the HMC. If there is a firewall between the NIM master and the IVM, ports 22 and 23 must be opened in the firewall for SSH and telnet communication between the NIM master and the IVM. For NIM-based deploys to work for HMC-managed irtual serers, the HMC Remote Virtual Terminal must be enabled, and its port 9735 opened in the HMC firewall. To configure NIM-based deploys for the HMC, perform the following steps: 1. In the HMC Naigation Area, click HMC Management, Connectiity and Remote Virtual Terminal. In the dialog that opens, enable remote irtual terminal connections. 2. Under HMC Management, click Connectiity and Change Network Settings. 3. In Network Settings window, click the LAN Adapters tab. 4. Select the LAN adapter that is on the same network as your NIM master, and click Details. 5. In the LAN Adapter Details window, click the Firewall Settings tab. Verify that VTTY 9735:tcp / is in the lower table. If it is there, you can click Cancel. If it is not there, select VTTY 9735:tcp in the upper table and click Allow incoming. VTTY 9735:tcp / is added to the lower table. 6. Click OK. The host name for the primary and secondary network interfaces of the irtual serer where you want to deploy the irtual appliance can be resoled from the NIM master. Either define the host name on the name serer, or add it to /etc/hosts on the NIM master. The HMC or IVM that manages the target irtual serer is discoered in IBM Systems Director. Access status is listed as OK, and inentory is collected for the HMC or IVM. The irtual serer is not a full system partition, or the only partition on the host to which all host resources are dedicated. The irtual serer has at least as many processors and as much memory as the irtual appliance needs. The irtual serer has irtual I/O as described below; irtual serers with only physical I/O cannot be used. The irtual serer has at least one irtual disk large enough for the irtual appliance image. The irtual serer has at least as many irtual network adapters as the irtual appliance needs, and the irtual network adapters must be attached to networks in the same ratio as they are in the irtual appliance. For instance, if the irtual appliance has two network adapters on one network, and another network adapter on a different network, then the irtual serer must hae at least two irtual network adapters on one network, and at least one irtual network adapter on a different network. The irtual serer is actie. 26 IBM Systems Director VMControl: Installation and User's Guide

33 Before deploying a irtual appliance to a irtual serer with NPIV-attached disk, the following prerequisites must be met: 1. The irtual serers hae been configured to use irtual Fibre Channel adapters connected through VIOS irtual Fibre Channel adapters to an NPIV-capable VIOS physical Fibre Channel adapter. 2. Switch zoning has been configured. This means that any WWPN from a irtual Fibre Channel adapter must be manually configured in a zone to allow I/O access. 3. Storage olumes hae already been attached. This means that existing storage olumes that will be used to deploy to an existing irtual serer must be attached (LUN masked) to the WWPNs on the irtual Fibre Channel adapter. 4. Inentory has been collected on the following resources in this order: a. The HMC-managed host system b. The SAN storage controller c. The SAN switch Note: VMControl supports NPIV-attached disk only for storage deices managed by IBM Tioli Storage Productiity Center. Note: If the irtual serer has an operating system installed, it is oerwritten when the irtual appliance is deployed. Deploying to a new irtual serer You can deploy a irtual appliance to a new irtual serer on a host that you specify, or on a host in a serer system pool that you specify, when the following requirements are met: Your NIM-based Power irtualization enironment is configured as described in "Requirements and support for AIX using NIM." IBM Systems Director VMControl has recognized the NIM master as an image repository in the enironment, the irtual appliance image is present on the NIM master, and VMControl has discoered the image. The NIM master has network access to the HMC or IVM that manages the new irtual serer. If there is a firewall between the NIM master and the HMC, ports 22 and 9735 must be opened in the firewall for SSH and remote irtual terminal communication between the NIM master and the HMC. If there is a firewall between the NIM master and the IVM, ports 22 and 23 must be opened in the firewall for SSH and telnet communication between the NIM master and the IVM. For NIM-based deploys to work for HMC-managed irtual serers, the HMC Remote Virtual Terminal must be enabled, and its port 9735 opened in the HMC firewall. To configure NIM-based deploys for the HMC, perform the following steps: 1. In the HMC Naigation Area, click HMC Management, Connectiity and Remote Virtual Terminal. In the dialog that opens, enable remote irtual terminal connections. 2. Under HMC Management, click Connectiity and Change Network Settings. 3. In Network Settings window, click the LAN Adapters tab. Chapter 2. IBM Systems Director VMControl V

34 4. Select the LAN adapter that is on the same network as your NIM master, and click Details. 5. In the LAN Adapter Details window, click the Firewall Settings tab. Verify that VTTY 9735:tcp / is in the lower table. If it is there, you can click Cancel. If it is not there, select VTTY 9735:tcp in the upper table and click Allow incoming. VTTY 9735:tcp / is added to the lower table. 6. Click OK. The irtual serer that you plan to create must hae network access to the NIM master, and any firewalls must be preconfigured to permit the irtual serer to connect to the NIM master. The host name for the primary and secondary network interfaces of the irtual serer where you want to deploy the irtual appliance can be resoled from the NIM master. Either define the host name on the name serer used by the NIM master, or add it to the /etc/hosts file on the NIM master. The HMC or IVM that manages the new irtual serer is discoered in IBM Systems Director. Access status is listed as OK, and inentory is collected for the HMC or IVM. If you want the irtual disk of the new irtual to be allocated from, or use an existing olume in a SAN storage pool known to the Virtual I/O Serer, be sure that the storage resources comprising that SAN are discoered and accessible by IBM Systems Director. For example, discoer and access the fibre channel switch and its SMI-S proider, and the storage system and its SMI-S proider. Each VIOS on the target host that proides a path to the SAN storage must hae the same number of irtual slots aailable as the number of irtual appliances that you plan to deploy. If any one of these VIOS irtual serers does not hae enough irtual slots aailable, you need to increase the maximum number of irtual slots on the VIOS before running the Deploy task. Notes: If the target host serer has multiple Virtual I/O Serer (VIOS) partitions, and each VIOS partition has a path to the selected storage pool, the new irtual serer must be properly configured for multi-path I/O to storage. All irtual ethernet adapters created for the new irtual serer are connected to the default irtual switch (ETHERNET0). When you deploy a irtual appliance to a new irtual serer, the /etc/resol.conf file will be created by NIM on the target irtual serer. If you do not want the /etc/resol.conf file, you can remoe it. Single-irtual disk Open Virtualization Format (OVF) packages, irtual serers, and irtual appliances are supported. Single irtual serer OVF packages and irtual appliances are supported. For AIX mksysb OVF packages and irtual appliances, only the rootg olume group is supported. For additional information about using VMControl in a Power Systems enironment, see "VMControl Power Information" in the IBM Systems Director Best Practices Wiki. Related information: VMControl Power Information Relocation support and requirements in a Power Systems irtualization enironment: 28 IBM Systems Director VMControl: Installation and User's Guide

35 This topic describes the support and requirements for relocating irtual serers in a Power Systems irtualization enironment in IBM Systems Director VMControl. You can relocate irtual serers when the following requirements are met: The source and target in the irtualization enironment support Lie Partition Mobility. For information, see Chapter 3 in "IBM PowerVM Lie Partition Mobility." The source and target hosts are within the same system pool. Both the source and target host hae access to the same shared storage area network (SAN). Both the source and target host hae access to the same shared communications network. The target host has enough memory to support the irtual serer. The target host has enough processor resource to support the irtual serer. The target host must hae at least as many Virtual IO Serer (VIOS) partitions with paths to the SAN as the source host. It is not necessary for the VIOS partitions on the target host to hae the same number of paths to the SAN as the VIOS partitions on the source host. Howeer, the target host must proide as many VIOS partitions with paths to the SAN as the source has. Note: You cannot perform the deploy, capture, or relocate tasks concurrently for the same irtual serer. Wait until one of these tasks is complete before beginning another. Serer system pool support and requirements in a Power Systems irtualization enironment: This topic describes the support and requirements for serer system pools in a Power Systems irtualization enironment in IBM Systems Director VMControl. If you are creating resilient (highly aailable) serer system pools, your irtualization enironment must meet the following requirements: All hosts in each resilient serer system pool support Lie Partition Mobility. For information, see Chapter 3 in "IBM PowerVM Lie Partition Mobility." The hosts in the resilient serer system pool hae access to the same shared storage area network (SAN). The hosts in the resilient serer system pool hae access to the same shared communications network. You cannot combine systems with single Virtual IO Serer (VIOS) partitions and dual VIOS partitions in a single resilient serer system pool. Systems in a pool must all be single-vios systems, or they must all be dual-vios systems. Note: If you remoe the storage associated with your serer system pool from IBM Systems Director, the serer system pool and any associated workloads are no longer operational. For additional requirements for managing serer system pools, see Preparing your enironment for serer system pools." Chapter 2. IBM Systems Director VMControl V

36 Related tasks: Preparing your Power Systems enironment for serer system pools Related information: IBM PowerVM Lie Partition Mobility Storage system pool support and requirements in a Power Systems irtualization enironment: This topic describes the support and requirements for storage system pools in a Power Systems irtualization enironment in IBM Systems Director VMControl. If you are creating storage system pools, your irtualization enironment must meet the following requirements: You must hae a license for IBM Systems Director VMControl Enterprise Edition. VMControl includes the Storage system pools summary page where you can create and manage storage system pools. All storage subsystems within a storage system pool must be part of the same actie zone configuration. Zoning must be configured using World Wide Port Name (WWPN) zoning. Note: Zoning must be configured outside of IBM Systems Director. All storage deices must be discoered and hae inentory collected. SMI-S proiders enable discoery and communication with IBM Systems Director. Related concepts: Storage system pools oeriew Storage system pools Related tasks: Managing storage using IBM Systems Director VMControl and IBM Tioli Storage Productiity Center Requirements and support for AIX and Linux using storage copy serices (SCS): This topic describes the requirements and support for AIX and Linux irtual appliances, irtual serers, and workloads in a Power Systems irtualization enironment that relies on storage copy serices (SCS). The following diagram shows a Power Systems irtualization enironment for AIX and Linux irtual appliances, irtual serers, and workloads that relies on SCS. 30 IBM Systems Director VMControl: Installation and User's Guide

37 IBM Systems Director Serer is installed on a supported serer. IBM Systems Director VMControl Standard Edition or IBM Systems Director VMControl Enterprise Edition is installed on the IBM Systems Director Serer.IBM Systems Director VMControl is installed on the IBM Systems Director Serer. A Virtual I/O Serer (VIOS) partition exists on an IBM Power serer to host the image repository used to store the raw disk images associated with your AIX and Linux irtual appliances. Note: The IBM Power serer can be managed by Hardware Management Console (HMC) as shown in the diagram, or by Integrated Virtualization Manager (IVM). The IBM Systems Director Common Agent and VMControl Common Repository subagent are installed on the VIOS that you want to use as an image repository. All AIX and Linux irtual serers to be captured from or deployed to using VMControl hae their storage allocated from the SAN and proided through one or more VIOS partitions. These irtual serers must use irtual Ethernet connections proided through one or more VIOS partitions. These irtual serers must not hae any physical deices allocated from the IBM Power serer. Note: You can hae multiple repositories. Howeer, for repositories that are on separate IBM Power serers, the image repository irtual serers must hae access through a VIOS to the same shared SAN as the AIX and Linux irtual serers that they will capture and deploy. Chapter 2. IBM Systems Director VMControl V

38 Supported operating systems and firmware ersions You must use the following operating systems and firmware ersions in this SCS-based Power Systems irtualization enironment. IBM Systems Director Serer You can use any IBM Systems Director Serer V6.2.1 with VMControl Standard Edition or VMControl Enterprise Edition V2.3.1 installed. Hardware Management Console (HMC) For POWER5, POWER6 and POWER7, use a minimum of HMC V7R7.2 and all aailable updates. Virtual I/O Serer (VIOS) Use a minimum of VIOS and all aailable updates. POWER firmware For your POWER5 and POWER6 and serers, use a minimum of FW3.5 and all aailable updates. For POWER7 processor-based serers, use a minimum of FW7.2 and all aailable updates. For information about the latest fixes for required software, see "Required Fix Leels for VMControl Dependencies." Supported tasks In the SCS-based Power Systems irtualization enironment, you can perform these tasks: Create, edit, and delete irtual serers Relocate irtual serers Import irtual appliance packages containing an AIX or Linux raw disk image Capture an AIX or Linux workload or irtual serer (logical partition) Deploy an AIX or Linux raw disk image irtual appliance Group irtual serers to create a workload Start, stop, and edit a workload Create, edit, and delete system pools Related tasks: Installing IBM Systems Director VMControl agents and subagents Updating IBM Systems Director VMControl on page 82 Related information: Required Fix Leels for VMControl Dependencies Import support and requirements in an SCS-based Power irtualization enironment: This topic describes the support and requirements for importing an AIX or Linux raw disk image irtual appliance package in an SCS-based Power irtualization enironment. You can import a irtual appliance package containing AIX on Power Systems or Linux on Power Systems raw disk images for IBM POWER irtual serers (logical partitions). You can import any AIX ersion 5.3 or newer irtual appliance. You can import any Red Hat Enterprise Linux (RHEL) ersion 5.4 or newer or SUSE Linux Enterprise Serer (SLES) 10 Serice Pack 3 irtual appliance. Other ersions 32 IBM Systems Director VMControl: Installation and User's Guide

39 of AIX or Linux might work, but hae not been fully tested. You can import these types of irtual appliance packages when the following requirements are met: Your irtual enironment is configured as described in "Requirements and support for AIX and Linux using storage copy serices." The irtual appliance package is an Open Virtualization Format (OVF) package containing one AIX or Linux raw disk image and the description of one, single-disk Power irtual serer to accommodate the image. You hae a VMControl Virtual I/O Serer (VIOS) image repository whose associated storage system pool has sufficient space to store the imported irtual appliance image. See "Creating and discoering image repositories for AIX and Linux on Power Systems." Capture support and requirements in an SCS-based Power irtualization enironment: This topic describes the support and requirements for capturing an AIX or Linux irtual serer or workload in an SCS-based Power irtualization enironment. You can create a irtual appliance by capturing any of the following sources: An IBM Power Systems irtual serer (logical partition) or workload that contains a irtual serer that is running AIX 5.3 or newer. An IBM Power Systems irtual serer (logical partition) or workload that contains a irtual serer that is running SuSE Linux Enterprise Serer (SLES) 10 SP3 or newer, or Red Hat Enterprise Linux (RHEL) 5.4 or newer. Before you can capture a irtual serer or workload, ensure that the following additional requirements are met: Your enironment is configured as described in "Requirements and support for AIX and Linux using storage copy serices." You hae a VMControl Virtual I/O Serer (VIOS) image repository whose associated storage system pool has sufficient space to store the imported irtual appliance image. See "Creating and discoering image repositories for AIX and Linux on Power Systems." The irtual serer uses irtual I/O and irtual storage. If you want your Linux irtual serer to hae multiple paths to storage (MPIO), you must configure Linux for MPIO on the root deice before capturing the irtual serer. Tip: The default Red Hat Enterprise Linux configuration creates a restrictie blacklist for all WWPN entries. This list must be remoed to enable deployment of a captured image. The configuration is described in the following Red Hat Enterprise Linux document: Using Deice-Mapper Multipath: Chapter 4.2 Configuration File Blacklist Before capturing SUSE Linux irtual serers, ensure that deices are mounted by deice name or UUID, not by -id. For information about this change, see document on the Noell Support website. A suitable actiation engine is installed and enabled on the irtual serer. The actiation engine must hae these characteristics: It must expect the Open Virtualization Format (OVF) enironment document transported at deploy time to be named of-en.xml and be located in the root directory of a irtual optical drie. It must able to process the following OVF enironment document properties per network interface instance: - com.ibm.of.im.2.networkport.instanceid.ip Chapter 2. IBM Systems Director VMControl V

40 - com.ibm.of.im.2.networkport.instanceid.usedhcp - com.ibm.of.im.2.networkport.instanceid.ip6autoconf - com.ibm.of.im.2.networkport.instanceid.gateway - com.ibm.of.im.2.networkport.instanceid.netmask - com.ibm.of.im.2.networkport.instanceid.mac Depending on the origin of the irtual serer that you want to capture, it might or might not hae a suitable actiation engine in it already; and if present, it might or might not be enabled. If an actiation engine is already present, ensure that it is enabled. If the irtual serer has no actiation engine, you can install and enable any suitable one. VMControl ships basic actiation engines for AIX and Linux that you can use. To install and enable an actiation engine, perform these steps: - AIX: 1. Get the AIX Actiation Engine package, ae aix.rpm, from theibm Systems Director Serer from ${DIRECTOR_HOME}/proddata/actiationengine/power/ 2. Transfer ae aix.rpm to the irtual serer that you want to capture, and install it using the natie rpm command. 3. Enable the AIX Actiation Engine with the /opt/ibm/power_ae/ae o enable of-en.xml command. - Linux: 1. Get the Linux Actiation Engine package for your platform from the IBM Systems Director serer from ${DIRECTOR_HOME}/proddata/ actiation-engine/power/ Red Hat Enterprise Linux: ae linux-rhel.rpm SUSE Linux: ae linux-sles.rpm 2. Transfer the Linux Actiation Engine package to the irtual serer that you want to capture, and install it using the natie rpm command. 3. Enable the Linux Actiation Engine with the /opt/ibm/power_ae/ae o enable of-en.xml command. The operating system on the irtual serer that you want to capture is discoered, accessed, and inentoried by your IBM Systems Director Serer. On Red Hat Enterprise Linux, the network configuration for the irtual serer must be temporarily remoed by completing the following steps: 1. Record and sae the current network configuration settings for the irtual serer. You will need this information to reconfigure the network later. Do NOT sae the file with your network configuration information to the irtual serer that you plan to capture; sae the file to another location. Complete the following steps on your irtual serer: Run the following command: ifconfig -a Record the network configuration settings for each adapter. Run the following command: netstat -rn Record the configuration of the default ( ) route from the output. 2. To remoe the network configuration, run the following script on your irtual serer: /opt/ibm/power_ae/ae-wipeconfig This script is included in the ae linux-rhel.rpm package. 34 IBM Systems Director VMControl: Installation and User's Guide

41 Note: If you want to use this irtual serer after you hae captured it, you must reconfigure the network and set up the host name again. For more information, refer to your Red Hat Enterprise Linux documentation. Tip: To see a list of the interfaces in the /usr/sbin/system-config-network-tui tool, you must create an ifcfg-eth* file for each interface that you want to configure. To create an ifcfg-eth* file, run the following command: echo DEVICE=eth0 > /etc/sysconfig/network-scripts/ifcfg-eth0 where eth0 is the name of your ethernet deice. A irtual appliance created by capturing a irtual serer whose storage is accessed through a single VIOS must only be deployed to a irtual serer with a single path to its storage. Similarly, a irtual appliance created by capturing a irtual serer whose storage is accessed through multiple Virtual I/O Serers must only be deployed to a irtual serer with multiple paths to its storage. If you work in both single and multiple VIOS enironments, it is suggested that you use a naming scheme or description to distinguish your irtual appliances as single or multiple VIOS. The Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM) that manages the irtual serer that you want to capture is discoered, accessed, and inentoried in IBM Systems Director. Access status is listed as OK. The Power serer hosting the irtual serer must be inentoried in IBM Systems Director. The irtual ethernet adapters of the irtual serer must be connected to the default irtual network switch (ETHERNET0). The irtual serer is powered off. For additional information about using VMControl in a Power Systems enironment, see "VMControl Power Information" in the IBM Systems Director Best Practices Wiki. Related concepts: Creating and discoering image repositories for AIX and Linux on Power Systems Related information: VMControl Power Information Deploy support and requirements in an SCS-based Power irtualization enironment: This topic describes the support and requirements for deploying an AIX or Linux raw disk image irtual appliance in an SCS-based Power irtualization enironment. You can deploy an AIX or Linux raw disk image irtual appliance to a new or existing irtual serer in the following enironments: A irtual serer (logical partition) on a Power Systems serer that is managed by Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM). A irtual serer on a Power Architecture BladeCenter serer that is managed by IVM. Deploying to an existing irtual serer Chapter 2. IBM Systems Director VMControl V

42 Your enironment is configured as described in "Requirements and support for AIX and Linux using storage copy serices." You hae a VMControl Virtual I/O Serer (VIOS) image repository containing at least the AIX or Linux raw disk image irtual appliance that you want to deploy. See "Creating and discoering image repositories for AIX and Linux on Power Systems," and either "Import support and requirements in a SCS-based Power irtualization enironment" or "Capture support and requirements in a SCS-based Power irtualization enironment." You hae discoered, requested access, and inentoried the operating system of a VIOS that proides irtual I/O to the irtual serer, and access is listed as OK. VMControl must hae access to the VIOS operating system to create a irtual optical drie through which customization alues get passed to the actiation engine in the newly deployed workload. Note: The discoered VIOS can hae the Common Agent installed, but it is not necessary; SSH access is sufficient. The irtual serer has at least as many processors and as much memory as the irtual appliance needs. The irtual serer has irtual I/O as described in the following bullets; irtual serers with physical I/O only cannot be used. The irtual serer has only one irtual disk, and it is large enough for the irtual appliance image. Further, the irtual disk must be on SAN accessible by the VMControl VIOS image repository being used. The irtual serer has at least as many irtual network adapters as the irtual appliance needs, and the irtual network adapters must be attached to networks in the same ratio as they are in the irtual appliance. For instance, if the irtual appliance has two network adapters on one network, and another network adapter on a different network, the irtual serer must hae at least two irtual network adapters on one network, and at least one irtual network adapter on a different network. The HMC or IVM that manages the target irtual serer is discoered in IBM Systems Director. Access status is listed as OK, and inentory is collected for the HMC or IVM. The irtual serer is not a full system partition, or the only partition on the host to which all host resources are dedicated. The irtual serer is powered off. Notes: If the irtual serer has an operating system installed, it is oerwritten when the irtual appliance is deployed. If the irtual disk is bigger than the irtual appliance image size, the area of the existing disk that is greater than the image size is not initialized. Any data that was on that existing disk is still there. To preent surfacing existing data, you must initialize the uninitialized part of the storage olume by another method. Deploying to a new irtual serer You can deploy a irtual appliance to a new irtual serer on a host that you specify, or on a host in a serer system pool that you specify, when the following requirements are met: Your enironment is configured as described in "Requirements and support for AIX and Linux using storage copy serices." 36 IBM Systems Director VMControl: Installation and User's Guide

43 You hae a VIOS image repository containing at least the AIX or Linux raw disk image irtual appliance that you want to deploy. See "Creating and discoering image repositories for AIX and Linux on Power Systems," and either "Import support and requirements in a SCS-based Power irtualization enironment" or "Capture support and requirements in a SCS-based Power irtualization enironment." The HMC or IVM that manages the new irtual serer is discoered in IBM Systems Director. Access status is listed as OK, and inentory is collected for the HMC or IVM. You hae discoered, requested access, and inentoried the operating system of a VIOS that proides irtual I/O to the irtual serer, and access is listed as OK. VMControl must hae access to the VIOS operating system to create a irtual optical drie through which customization alues get passed to the actiation engine in the newly deployed workload. Note: The discoered VIOS can hae the Common Agent installed, but it is not necessary; SSH access is sufficient. If you want the irtual disk of the new irtual serer to be allocated from, or use an existing olume in a SAN storage pool known to the VIOS, be sure that the storage resources comprising that SAN are discoered and accessible by IBM Systems Director. For example, discoer and access the fibre channel switch and its SMI-S proider, and the storage system and its SMI-S proider. Each VIOS on the target host that proides a path to the SAN storage must hae the same number of irtual slots aailable as the number of irtual appliances that you plan to deploy. If any one of these VIOS irtual serers does not hae enough irtual slots aailable, you need to increase the maximum number of irtual slots on the VIOS before running the Deploy task. Notes: If the target host serer has multiple VIOS partitions, and each VIOS partition has a path to the selected storage pool, the new irtual serer is properly configured for multi-path I/O to storage. All irtual ethernet adapters created for the new irtual serer are connected to the default irtual switch (ETHERNET0). Single-irtual disk Open Virtualization Format (OVF) packages, irtual serers, and irtual appliances are supported. Single irtual serer OVF packages and irtual appliances are supported. Tip: The deployed irtual serer starts upon completion of the deploy. A irtual optical deice is used for irtual serer customization information. Starting the new or existing irtual serer at the end of the deploy runs the actiation engine that is using information proided through the irtual optical deice and performs whateer customization is required. For additional information about using VMControl in a Power Systems enironment, see "VMControl Power Information" in the IBM Systems Director Best Practices Wiki. Related information: VMControl Power Information Relocation support and requirements in a Power Systems irtualization enironment: Chapter 2. IBM Systems Director VMControl V

44 This topic describes the support and requirements for relocating irtual serers in a Power Systems irtualization enironment in IBM Systems Director VMControl. You can relocate irtual serers when the following requirements are met: The source and target in the irtualization enironment support Lie Partition Mobility. For information, see Chapter 3 in "IBM PowerVM Lie Partition Mobility." The source and target hosts are within the same system pool. Both the source and target host hae access to the same shared storage area network (SAN). Both the source and target host hae access to the same shared communications network. The target host has enough memory to support the irtual serer. The target host has enough processor resource to support the irtual serer. The target host must hae at least as many Virtual IO Serer (VIOS) partitions with paths to the SAN as the source host. It is not necessary for the VIOS partitions on the target host to hae the same number of paths to the SAN as the VIOS partitions on the source host. Howeer, the target host must proide as many VIOS partitions with paths to the SAN as the source has. Note: You cannot perform the deploy, capture, or relocate tasks concurrently for the same irtual serer. Wait until one of these tasks is complete before beginning another. Serer system pool support and requirements in a Power Systems irtualization enironment: This topic describes the support and requirements for serer system pools in a Power Systems irtualization enironment in IBM Systems Director VMControl. If you are creating resilient (highly aailable) serer system pools, your irtualization enironment must meet the following requirements: All hosts in each resilient serer system pool support Lie Partition Mobility. For information, see Chapter 3 in "IBM PowerVM Lie Partition Mobility." The hosts in the resilient serer system pool hae access to the same shared storage area network (SAN). The hosts in the resilient serer system pool hae access to the same shared communications network. You cannot combine systems with single Virtual IO Serer (VIOS) partitions and dual VIOS partitions in a single resilient serer system pool. Systems in a pool must all be single-vios systems, or they must all be dual-vios systems. Note: If you remoe the storage associated with your serer system pool from IBM Systems Director, the serer system pool and any associated workloads are no longer operational. For additional requirements for managing serer system pools, see Preparing your enironment for serer system pools." 38 IBM Systems Director VMControl: Installation and User's Guide

45 Related tasks: Preparing your Power Systems enironment for serer system pools Related information: IBM PowerVM Lie Partition Mobility Storage system pool support and requirements in a Power Systems irtualization enironment: This topic describes the support and requirements for storage system pools in a Power Systems irtualization enironment in IBM Systems Director VMControl. If you are creating storage system pools, your irtualization enironment must meet the following requirements: You must hae a license for IBM Systems Director VMControl Enterprise Edition. VMControl includes the Storage system pools summary page where you can create and manage storage system pools. All storage subsystems within a storage system pool must be part of the same actie zone configuration. Zoning must be configured using World Wide Port Name (WWPN) zoning. Note: Zoning must be configured outside of IBM Systems Director. All storage deices must be discoered and hae inentory collected. SMI-S proiders enable discoery and communication with IBM Systems Director. Related concepts: Storage system pools oeriew Storage system pools Related tasks: Managing storage using IBM Systems Director VMControl and IBM Tioli Storage Productiity Center VMware requirements and support This topic describes the requirements and support for the VMware Center irtualization enironment in IBM Systems Director VMControl. The following diagram shows a irtualization enironment with VMware Center managing VMware ESX and VMware ESXi hosts. Chapter 2. IBM Systems Director VMControl V

46 IBM Systems Director Serer is installed on a supported serer. IBM Systems Director VMControl is installed on the IBM Systems Director Serer. Note: To launch the VMware Infrastructure Client or the VMware Sphere Client from IBM Systems Director VMControl, the client must be installed on the IBM Systems Director Serer system and on any system that you use to log in to the IBM Systems Director Web interface. VMware Center is installed on an x86-compatible system. IBM Systems Director Common Agent and the VMware Center subagent are also installed on the system. VMware ESX exists to host irtual serers that you can manage using VMControl. Note: VMware ESX is managed by VMware Center. VMware ESXi exists to host irtual serers that you can manage using VMControl. Note: VMware ESXi is managed by VMware Center. The following diagram shows the VMware ESX irtualization enironment. 40 IBM Systems Director VMControl: Installation and User's Guide

47 IBM Systems Director Serer is installed on a supported serer. IBM Systems Director VMControl is installed on the IBM Systems Director Serer. VMware ESX exists to host irtual serers that you can manage using VMControl. IBM Systems Director Common Agent and the VMware ESX subagent are installed on the VMware ESX system. Supported ersions VMControl supports the following irtualization software: VMware Center 4.x VMware ESXi 4.x (managed by VMware Center) VMware ESX 4.x (managed by VMware Center) For information about the latest fixes for required software, see "Required Fix Leels for VMControl Dependencies." Supported tasks In the VMware Center irtualization enironment, you can perform the following tasks: Create, edit, and delete irtual serers Create a DataCenter or Cluster using the Create Virtual Farm wizard Add a host to a DataCenter or Cluster using the Add host to farm function Remoe a host from a DataCenter or Cluster using the Remoe host from farm function Relocate irtual serers Chapter 2. IBM Systems Director VMControl V

48 Put a host into maintenance mode Remoe a host from maintenance mode In a VMware ESX irtualization enironment or in a irtualization enironment where VMware ESXi or ESX is not managed by VMware Center, you can perform the following tasks: Create, edit, and delete irtual serers Relocate irtual serers Related tasks: Installing IBM Systems Director VMControl agents and subagents Related information: Required Fix Leels for VMControl Dependencies Windows Serer 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled requirements and support This topic describes the requirements and support for the Windows Serer 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled irtualization enironment in IBM Systems Director VMControl. The following diagram shows the Windows Serer 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled irtualization enironment. IBM Systems Director Serer is installed on a supported system. IBM Systems Director VMControl is installed on the IBM Systems Director Serer. 42 IBM Systems Director VMControl: Installation and User's Guide

49 Windows Serer 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled is installed on an x86-compatible system. IBM Systems Director Common Agent or Platform Agent is installed on the irtual serer. Supported ersions VMControl supports Windows Serer 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled, Release 2 irtualization software. For information about the latest fixes for required software, see "Required Fix Leels for VMControl Dependencies." Supported tasks In this enironment, you can create, edit, and delete irtual serers. Related information: Required Fix Leels for VMControl Dependencies z/vm irtualization requirements and support This topic describes the requirements and support for the z/vm irtualization enironment in IBM Systems Director VMControl. The following diagram shows the z/vm irtualization enironment. IBM Systems Director Serer is installed on a supported serer. IBM Systems Director VMControl is installed on the IBM Systems Director Serer. IBM Systems Director Platform Agent and the IBM z/vm Manageability Access Point Agent are installed on the irtual serer. An image repository has been created on the irtual serer. Chapter 2. IBM Systems Director VMControl V

50 A z/vm directory manager has been configured on the IBM System z serer that is running z/vm. Supported ersions VMControl supports the same ersions of z/vm irtualization software as IBM Systems Director Serer ersion For information about the latest fixes for required software, see "Required Fix Leels for VMControl Dependencies." Supported tasks In the z/vm irtualization enironment, you can perform these functions: Create, edit, and delete irtual serers Import irtual appliance packages Note: Single irtual serer OVF packages and irtual appliances are supported. Capture workloads Group irtual serers to create workloads Capture irtual serers Deploy and delete irtual appliances Start, stop, delete, and edit workloads Related tasks: Installing IBM Systems Director VMControl agents and subagents Related information: Required Fix Leels for VMControl Dependencies z/vm import requirements: This topic describes the requirements for importing a irtual appliance package into a z/vm irtualization enironment in IBM Systems Director VMControl. You can import a irtual appliance package containing Linux on System z images for z/vm. You can import this type of irtual appliance package when the following requirements are met: The IBM z/vm Manageability Access Point Agent is installed on the System z host system where you want to store the imported irtual appliance package. The image repository is discoered in IBM Systems Director. There is sufficient space in the image repository to store the image associated with the irtual appliance package that you want to import. The irtual appliance package that you want to import was created for z/vm by IBM Systems Director VMControl Capture or Import tasks. Related reference: OVF package requirements z/vm capture requirements: This topic describes the requirements for capturing a irtual serer in a z/vm irtualization enironment in IBM Systems Director VMControl. 44 IBM Systems Director VMControl: Installation and User's Guide

51 You can capture z/vm irtual serers (z/vm guests) running Linux on System z. You can capture these irtual serers if the following requirements are met: An IBM z/vm Manageability Access Point Agent has been installed on a irtual machine that runs in the same z/vm host as the target of the capture. The System z host system (the serer on which IBM z/vm Manageability Access Point Agent runs) has been discoered with IBM Systems Director. Access status is listed as OK, and inentory is collected. The discoery of the IBM z/vm Manageability Access Point Agent causes the System z host to be discoered. Collection of inentory is performed against the IBM z/vm Manageability Access Point Agent. The irtual serer has been discoered with IBM Systems Director. Access status is listed as OK, and inentory has been collected. The irtual serer is running. The irtual serer permits remote root logins. The z/vm manageability access point is able to establish an SSH connection to the irtual serer using the IP address used by the IBM Systems Director Serer to access the target system. The disk partitions must be configured appropriately and must include a file system in /etc/fstab. Specifically, when a disk partition is using any one of the following configurations, the disk partition that precedes that disk partition must also use one of the following configurations: Configured as a Linux file system listed in /etc/fstab Configured as a Linux swap partition listed in /etc/fstab Configured as an LVM physical olume used by a olume group containing a olume listed in /etc/fstab Note: You cannot capture a irtual serer with an LVM system that has olume group names or logical olume UUIDs that match, and therefore conflict with, olume group names or olume UUIDs on the z/vm manageability access point. Similarly, you cannot capture a irtual serer that has been cloned from the z/vm manageability access point or from the same source as the z/vm manageability access point if the z/vm manageability access point is configured with one or more LVM logical olumes. IBM Systems Director VMControl captures one z/vm irtual serer at a time. Subsequent requests for capturing a irtual serer are queued for processing. z/vm deploy requirements: This topic describes the requirements for deploying a irtual appliance in a z/vm irtualization enironment in IBM Systems Director VMControl. On a System z host system that is running the z/vm hyperisor, you can deploy an empty irtual serer to create a irtual serer that does not include a irtual appliance. You can also deploy a irtual appliance to a new or existing irtual serer. IBM Systems Director VMControl deploys one z/vm irtual serer or irtual appliance at a time. Subsequent requests for deployment are queued for processing. For any z/vm deployment, the following prerequisites must be met: Chapter 2. IBM Systems Director VMControl V

52 The IBM z/vm Manageability Access Point Agent is installed on the z/vm host where the deployment is to occur. The IBM z/vm Manageability Access Point Agent on the System z host system is discoered in IBM Systems Director. Access status is listed as OK, and inentory is collected. The irtual serer that is the target of the deployment is powered off. You can deploy or create an empty irtual serer when the following additional prerequisite is met: If you plan to deploy a irtual serer that uses minidisks for storage, the directory manager supporting the z/vm system must be configured to allocate minidisk olumes with the Auto-Group option. You can deploy a irtual appliance to create a irtual serer when the additional prerequisites are met: The IBM z/vm Manageability Access Point Agent contains a repository with images. Inentory of the images in the repository is complete. Resources required for the image exist on the z/vm system, for example: Aailable network interfaces exist for use by the irtual serer. Aailable olumes exist for use by the irtual serer. If minidisks are required for irtual serer storage, the directory manager supporting the z/vm system must be configured to allocate minidisk olumes with the Auto-Group option. You can deploy a irtual appliance to an existing irtual serer when the following additional prerequisites are met: The IBM z/vm Manageability Access Point Agent contains a repository with images. Inentory is collected for the images in the repository. A irtual serer that meets the criteria specified in the image exists and has been discoered. Note: If you are deploying to an existing irtual serer, the operating system is oerwritten. You cannot deploy a irtual appliance to z/vm serice machines with the following user IDs, as described in the table: 46 IBM Systems Director VMControl: Installation and User's Guide

53 Table 4. z/vm serice machines that are restricted from the deploy task z/vm serice machines restricted from deploy task $ALLOC$ BLDRACF VSMPROXY GSKADMIN X25IPI $DIRECT$ BLDSEG VSMREQIN IMAP 5VMRAC40 $SYSCKP$ CMS1 VSMREQIU IMAPAUTH RACFSMF $SYSWRM$ CMSBATCH VSMSERVE LDAPSRV RACFVM $PAGE$ DISKACNT VSMWORK1 LPSERVE RACMAINT $SPOOL$ EREP VSMWORK2 MPROUTE AUTOLOG2 $TDISK$ LGLOPR VSMWORK3 NAMESRV IBMUSER ROOT MIGMAINT ZVMMAPLX NDBPMGR SYSADMIN DAEMON MONWRITE 4OSASF40 NDBSRV J BIN OP1 OSADMIN1 PORTMAP 5VMRSC40 SYS OPERATNS OSADMIN2 REXECD RSCS ADM OPERATOR OSADMIN3 RXAGENT1 RSCSAUTH NOBODY OPERSYMP OSAMAINT SMTP RSCSDNS DEFAULT SYSDUMP1 OSASF SNALNKA XCHANGE MAINT SYSMAINT 5VMTCP40 SNMPD 5VMDIR40 AVSVM SYSMON TCPIP SNMPQE DATAMOVE TSAFVM VMRMADMN TCPMAINT SNMPSUBA DIRMAINT GCS VMRMSVM ADMSERV SSLSERV DIRMSAT GCSXA VMSERVR DHCPD TFTPD 5VMPTK40 AUDITOR VMSERVS DTCVSW1 UFTD PERFSVM AUTOLOG1 VMSERVU DTCVSW2 VMKERB 5VMHCD40 BLDCMS VMUTIL FTPSERVE VMNFS CBDIODSP BLDNUC Recommendations for configuring IBM Power Systems that are using IBM Systems Director VMControl This topic contains recommendations for configuring irtualized enironments on IBM Power Systems. These recommendations are intended to enhance your use of the Adanced PowerVM irtualization features and will result in a Power Systems enironment that is suited for management with IBM Systems Director and IBM Systems Director VMControl. These recommendations can enhance IBM Power Systems irtualized configurations as follows: Improe aailability by proiding redundant physical and irtual I/O paths Improe performance for storage and network I/O Improe utilization of processor and memory hardware Result in enironments that are fully irtualized Simplify storage and SAN management Proide irtual serer (also known as logical partition, or LPAR) configurations that support relocation and resilient VMControl system pools Proide irtualized configurations that are compatible with VMControl Standard Edition for deploying new irtual serers and workloads Chapter 2. IBM Systems Director VMControl V

54 Virtual I/O Serer (VIOS) resilience Virtual I/O Serer (VIOS) resilience is proided by establishing a dual VIOS configuration on an IBM Power System. Dual VIOS and redundant deices improe the aailability of irtual I/O resources and can proide improed software maintenance and hardware replacement strategies. Since an AIX or Linux irtual serer can be a client of one or more Virtual I/O Serers at a time, a good strategy to improe aailability for AIX 5L or Linux irtual serers is to connect them to two Virtual I/O Serers. This technique proides a redundant configuration for each of the irtual serer connections to the external Ethernet network or storage resources by proiding the irtual serer with access to the same resources through multiple Virtual I/O Serers. This is like haing redundant physical adapters connected directly into the irtual serer. The resulting configuration improes the aailability of Virtual I/O resources and can proide improed software maintenance and hardware replacement strategies. For information about redundant VIOS configurations, refer to the following resources: Virtual I/O Serer Redundancy Considerations IBM System p Adanced POWER Virtualization Best Practices. See "Dual Virtual I/O Serers configurations." PowerVM Virtualization on IBM System p: Introduction and Configuration Fourth Edition Adanced POWER Virtualization on IBM System p Virtual I/O Serer Deployment Examples Power Systems Virtual I/O Serer Shared Processors and Processor Pools Shared processors are physical processors whose processing capacity is shared among multiple irtual serers. By default, all physical processors that are not dedicated to specific irtual serers are grouped in a shared processor pool. Allocating processor resource from a shared processor pool to irtual serers typically helps you to achiee the best utilization of hardware processor resources. Using shared processor pools proides a great deal of flexibility in how processor resource is allocated to irtual serers. For example, a irtual serer can be set up to exceed its normal processor allocation when there is unused processor power aailable in the shared processor pool. In addition, the use of multiple shared processor pools proides a better mechanism to manage processor utilization and licensing. Multiple shared processor pools allow you to limit the processor usage of the irtual serers that belong to the shared processor pools. Features such as Multiple Shared-Processor Pool (MSPP) technology enable software endors to proide new and innoatie licensing terms. MSPP technology proides a mechanism to define pools of processors supporting different licensed software. Within this shared processor pool all the irtual serers can be uncapped, allowing them flexibility within the license boundary set by the MSPP. For more information about shared processor and shared processor pool configurations, see the following resources: 48 IBM Systems Director VMControl: Installation and User's Guide

55 IBM System p Adanced POWER Virtualization (PowerVM) Best Practices PowerVM Virtualization on IBM System p: Introduction and Configuration Fourth Edition Adanced POWER Virtualization on IBM System p Virtual I/O Serer Deployment Examples Shared processors Shared processor pool management Enhanced Network Aailability Shared Ethernet adapter failoer and network interface backup are two methods that can be used to improe irtual I/O network aailability to irtual serers. Shared Ethernet Adapter (SEA) failoer offers Ethernet redundancy to the irtual serer at the Virtual I/O Serer leel. In an SEA failoer configuration two Virtual I/O Serers hae the bridging functionality of the Shared Ethernet Adapter. They use a control channel to determine which of them is supplying the Ethernet serice to the client. If one SEA loses access to the external network through its physical Ethernet adapter or if one Virtual I/O Serer is shut down for maintenance it will automatically fail oer. Network Interface Backup (NIB) in the irtual serer can be used to achiee network redundancy when using two Virtual I/O Serers. An EtherChannel (link aggregation) with only one primary adapter and one backup adapter is operating in Network Interface Backup mode. The irtual serer uses two irtual Ethernet adapters to create an EtherChannel that consists of one primary adapter and one backup adapter. The interface is defined on the EtherChannel. If the primary adapter becomes unaailable, the Network Interface Backup switches to the backup adapter. For more information about these methods for improing the aailability of irtual network configurations, see the following resources: Scenario: Configuring Network Interface Backup in Virtual I/O clients without VLAN tagging Scenario: Configuring Shared Ethernet Adapter failoer Link Aggregation or EtherChannel deices IBM System p Adanced POWER Virtualization (PowerVM) Best Practices. See "Dual Virtual I/O Serers configurations." PowerVM Virtualization on IBM System p: Introduction and Configuration Fourth Edition. See "Shared Ethernet redundancy." IBM PowerVM Virtualization Managing and Monitoring. See "Virtual network management." Integrated Virtual Ethernet Adapter Technical Oeriew and Introduction Enhanced Storage Aailability When setting up irtualized enironments, using multi-path I/O for irtual serers that are receiing I/O through the Virtual I/O Serer (VIOS) irtual serer proides the most highly aailable and automated aailability solution for storage resources. Multi-Path I/O proides increased aailability of irtual SCSI resources by proiding redundant paths to those resources. Chapter 2. IBM Systems Director VMControl V

56 Multiple irtual SCSI or irtual fibre channel adapters can be configured in the irtual serer to access the same disk through multiple Virtual I/O Serers. Further redundancy can be implemented in the Virtual I/O Serer by implementing multiple physical fibre channel adapters in each Virtual I/O Serer. This redundancy proides multiple paths through two different physical fibre channel cards in each Virtual I/O Serer. The resulting configuration proides irtual serers with redundancy for physical fibre channel hardware failures. For more information about strategies for improing the aailability of irtual storage configurations, see the following resources: Multipath I/O Redundancy Considerations IBM System p Adanced POWER Virtualization (PowerVM) Best Practices. See "Introduction to Virtual I/O Serer resilience" and "Storage". PowerVM Virtualization on IBM System p: Introduction and Configuration Fourth Edition. See "Virtual SCSI redundancy." IBM PowerVM Virtualization Managing and Monitoring. See "Virtual storage management." Relocation-enabled Virtual Serer Enironments Establishing an enironment that is capable of irtual serer relocation (PowerVM mobility) requires a fully irtualized enironment that uses shared SAN and requires that systems hae mutual access to one or more physical networks. VMControl's resilience policy uses lie irtual serer relocation to proide highly aailable enironments for planned and unplanned outages and proides resilient system pools by using irtual serer relocation technology. An important Power Systems recommendation to consider is enablement of your irtual enironment for irtual serer relocation. VMControl's relocation serices and resilient system pools are based on lie partition mobility support, which is a component of the PowerVM Enterprise Edition hardware feature. VMControl's resilient system pools proide a mechanism to relocate indiidual irtual serers and all the irtual serers on a host for both planned and unplanned system outages. Een if you are not currently using irtual serer relocation or resilient system pools, some planning can ease the transition to using these serices in the future. Lie partition mobility requires the use of irtual I/O that is proided to the irtual serer through the Virtual I/O Serer. Use of dedicated physical adapters such as host Ethernet adapter (HEA) or physical host bus adapter (HBA) is not permitted in a relocation-enabled enironment. In addition, the host source and target systems in a relocation operation must hae access to shared SAN storage that contains both the operating system image and any application data. If storage adapters that support NPIV are aailable, the use of NPIV in a relocation enironment simplifies the storage proisioning required to support relocation. For more information about requirements for lie irtual serer relocation or partition mobility on Power Systems, see the following resources: Lie Partition Mobility Power Systems Lie Partition Mobility IBM PowerVM Lie Partition Mobility 50 IBM Systems Director VMControl: Installation and User's Guide

57 IBM PowerVM Virtualization Managing and Monitoring. See PowerVM Lie Partition Mobility." Preparing your Power Systems enironment for serer system pools Before you use IBM Systems Director VMControl to create and manage serer system pools, you need to prepare your enironment. To prepare your enironment for serer system pools, complete the following steps: 1. Set up your storage enironment so that all the hosts in the serer system pool are connected to the same shared storage. 2. Ensure that you are using storage deices that are supported by IBM Systems Director. For more information, see "Supported storage deices." 3. Discoer and collect inentory on your storage deices. For more information, see the following topics: "Discoering and collecting inentory for storage deices" "Managing storage using IBM Systems Director VMControl and IBM Tioli Storage Productiity Center" 4. Ensure that you understand Serial Attached SCSI (SAS) zone configurations. For detailed information, see "Managing IBM BladeCenter SAS zone configuration." This information pertains to IBM BladeCenter installations. Howeer, you can apply this information to other types of systems and to external switches. 5. Familiarize yourself with "IBM System p Adanced POWER Virtualization (PowerVM) Best Practices." 6. If you want your serer system pool to support resilience, ensure that all the pre-requisites for lie partition mobility are met. For more information, see Chapter 3 in "IBM PowerVM Lie Partition Mobility." 7. To learn more about serer system pools in VMControl, read "Serer system pools." Related reference: Serer system pool support and requirements in a Power Systems irtualization enironment on page 29 Related information: IBM System p Adanced POWER Virtualization (PowerVM) Best Practices IBM PowerVM Lie Partition Mobility IBM Systems Director VMControl Implementation Guide on IBM Power Systems Installing and uninstalling IBM Systems Director VMControl IBM Systems Director VMControl is a separately installable IBM Systems Director plug-in that you can download from the IBM Web site. You can install IBM Systems Director VMControl and the agents necessary to use IBM Systems Director VMControl Standard Edition and IBM Systems Director VMControl Enterprise Edition. You can also uninstall VMControl. Chapter 2. IBM Systems Director VMControl V

58 Related tasks: Updating IBM Systems Director VMControl on page 82 Hardware and software requirements IBM Systems Director VMControl is installed on systems running IBM Systems Director Serer ersion This topic describes hardware and software requirements that are unique to IBM Systems Director VMControl. For detailed information about the hardware and software requirements for IBM Systems Director, see Hardware and software requirements for IBM Systems Director. Supported IBM systems IBM Systems Director VMControl is supported on all IBM systems that are supported by IBM Systems Director Serer For detailed information about the systems supported by IBM Systems Director Serer, see Supported IBM systems and products. Supported operating systems IBM Systems Director VMControl is supported on all operating systems that are supported by IBM Systems Director For specific ersions of these operating systems supported by IBM Systems Director Serer, see Operating systems supported by IBM Systems Director Additional prerequisites To use the IBM Systems Director VMControl installation program in a graphical, interactie wizard mode on an IBM Systems Director Serer that is running AIX or Linux, ensure that your system is graphics-enabled. If you want to use the installation program in a non-graphical, silent mode, your system need not be graphics-enabled. Note: For System z systems, xlibs must be installed in 64-bit mode. You can obtain the libstdc++.so.5 file from the compat-libstdc s390x.rpm packet. If you are running the IBM z/vm Manageability Access Point Agent that is supported by IBM Systems Director (or earlier), you must uninstall the agent and install the ersion of the IBM z/vm Manageability Access Point Agent that is supported by IBM Systems Director In addition, ensure that you hae installed a supported ersion of Linux on the z/vm system where you plan to install the IBM z/vm Manageability Access Point Agent. For more information, see Operating systems supported by IBM Systems Director To manage irtual appliances from IBM Systems Director VMControl with Tioli Proisioning Manager for Images, you must first install Tioli Proisioning Manager for Images. For more details, see "Installation requirements" in the IBM Tioli information center. 52 IBM Systems Director VMControl: Installation and User's Guide

59 Related information: Performance Tuning and Scaling Guide for IBM Systems Director 6.2 Installation requirements Downloading IBM Systems Director VMControl You can download IBM Systems Director VMControl from the IBM website. To download IBM Systems Director VMControl, follow these steps: 1. Go to the IBM Systems Director Downloads website at the following address: 2. Click Download for the IBM Systems Director VMControl plug-in. 3. Select the download package for the operating system that is running on your IBM Systems Director Serer: Operating system AIX Linux for pseries Linux for xseries Linux for zseries Windows Download package SysDir_VMControl_Linux_AIX.tar.gz SysDir_VMControl_Windows.zip 4. Copy the download package to a directory or folder on the IBM Systems Director Serer where you can extract the contents of the package. Related tasks: Updating IBM Systems Director VMControl on page 82 Installing IBM Systems Director VMControl You can install the IBM Systems Director VMControl plug-in on your IBM Systems Director Serer by running the installation program in a graphical, interactie wizard mode, or in a non-graphical, silent mode. Either mode installs the no-charge function of IBM Systems Director VMControl and starts a 60 day ealuation period for IBM Systems Director VMControl Standard Edition and IBM Systems Director VMControl Enterprise Edition. When the ealuation period expires, you can continue using the no-charge function of IBM Systems Director VMControl and you can purchase and install permanent license keys to continue using IBM Systems Director VMControl Standard Edition and IBM Systems Director VMControl Enterprise Edition. Related reference: Planning for IBM Systems Director VMControl on page 14 Installing IBM Systems Director VMControl using the installation wizard Use the installation program in a graphical, interactie wizard mode to install the IBM Systems Director VMControl plug-in on your IBM Systems Director Serer. This installation gies you access to the no-charge function of IBM Systems Director VMControl and starts a 60 day ealuation period for IBM Systems Director VMControl Standard Edition and IBM Systems Director VMControl Enterprise Edition. Before installing the IBM Systems Director VMControl plug-in, perform the following tasks: Chapter 2. IBM Systems Director VMControl V

60 Make sure that IBM Systems Director ersion is installed. Make sure that the target system satisfies all IBM Systems Director VMControl-specific prerequisites. For information, see Hardware and software requirements on page 14. Download the IBM Systems Director VMControl plug-in to your IBM Systems Director Serer. For information, see Downloading IBM Systems Director VMControl on page 53. Extract the contents of the download package as follows: For AIX or Linux, enter the following command: gzip -cd <package_name> tar -xf - where <package_name> is the file name of the installation package. For Windows, right-click the <package_name>, and extract the files from the installation package. On Red Hat Enterprise Linux, SELinux must be disabled before installing IBM Systems Director VMControl. To check SELinux status, enter the sestatus command. If SELinux is not disabled, temporarily disable SELinux by entering the /usr/sbin/setenforce 0 command. To install the IBM Systems Director VMControl plug-in and the 60-day ealuation license for IBM Systems Director VMControl Standard Edition and IBM Systems Director VMControl Enterprise Edition, follow these steps: 1. Change to the directory or folder that contains the extracted installation package files. 2. Start the IBM Systems Director VMControl program installation file. Note: If you install IBM Systems Director VMControl on an AIX or Linux serer and plan to use the installation wizard, you must start the installation program from a graphics-enabled session. Operating system AIX Linux for pseries Linux for xseries Linux for zseries Windows Installation file name IBMSystemsDirector-VMControl-Setup.sh IBMSystemsDirector-VMControl-Setup.exe The installation wizard starts and displays the Welcome page. 3. Follow the instructions in the installation wizard to install IBM Systems Director VMControl. Ensure that you restart the IBM Systems Director Serer. 4. Optional: You can check the appropriate log file to see if the installation completed successfully: For AIX and Linux: /opt/ibm/director/vmcontrolmanager/installlog.txt For Windows:..\Director\VMControlManager\installLog.txt where Director is the path where IBM Systems Director is installed. When the installation is complete, IBM Systems Director VMControl is displayed in the IBM Systems Director Welcome page. 54 IBM Systems Director VMControl: Installation and User's Guide

61 To use IBM Systems Director VMControl Standard Edition and IBM Systems Director VMControl Enterprise Edition, you must set up an image repository and install the appropriate VMControl agent or subagent. For information, see Installing IBM Systems Director VMControl agents and subagents on page 59. Installing IBM Systems Director VMControl silently Use the installation program in a non-graphical, silent mode to install theibm Systems Director VMControl plug-in on your IBM Systems Director Serer. This installation gies you access to the no-charge function of IBM Systems Director VMControl and starts a 60 day ealuation period for IBM Systems Director VMControl Standard Edition and IBM Systems Director VMControl Enterprise Edition. Before installing IBM Systems Director VMControl, perform the following tasks: Make sure that IBM Systems Director ersion is installed. Make sure that the target system satisfies all IBM Systems Director VMControl-specific prerequisites. For information, see Hardware and software requirements on page 14. Download the IBM Systems Director VMControl plug-in to your IBM Systems Director Serer. For information, see Downloading IBM Systems Director VMControl on page 53. Extract the contents of the download package as follows: For AIX or Linux, enter the following command: gzip -cd <package_name> tar -xf - where <package_name> is the file name of the installation package. For Windows, right-click the <package_name>, and extract the files from the installation package. On Red Hat Enterprise Linux, SELinux must be disabled before installing IBM Systems Director VMControl. To check SELinux status, enter the sestatus command. If SELinux is not disabled, temporarily disable SELinux by entering the /usr/sbin/setenforce 0 command. To install the IBM Systems Director VMControl plug-in and the 60-day ealuation license for IBM Systems Director VMControl Standard Edition and IBM Systems Director VMControl Enterprise Edition, follow these steps: 1. Open the installer.properties file in an ASCII text editor. 2. Use the comments in the installer.properties response file to modify the response file. 3. Sae the modified response file. 4. Open a command prompt. 5. Change to the folder or directory that contains the IBM Systems Director VMControl installation file, the response file, and the other extracted IBM Systems Director VMControl installation package files. 6. At the command prompt, run the installation command for the operating system that is running on your IBM Systems Director Serer: Chapter 2. IBM Systems Director VMControl V

62 Operating system AIX Linux for pseries Linux for xseries Linux for zseries Windows Installation command./ibmsystemsdirector-vmcontrol-setup.sh -i silent.\ibmsystemsdirector-vmcontrol-setup.exe -i silent If installation problems occur, an error message is displayed. For details about the installation error, scroll to the bottom of the log file specified in the error message. 7. Restart IBM Systems Director Serer manually by running the smstop and smstart commands. If you already set START_SERVER=true in the installer.properties file, then IBM Systems Director Serer will restart automatically. To check the progress of manual or automatic restart, run the smstatus command until it indicates an Actie status. After you restart IBM Systems Director Serer, IBM Systems Director VMControl is displayed on the IBM Systems Director Welcome page. To use IBM Systems Director VMControl Standard Edition and IBM Systems Director VMControl Enterprise Edition, you must set up an image repository and install the appropriate VMControl agent or subagent. For information, see Installing IBM Systems Director VMControl agents and subagents on page 59. Installing IBM Systems Director VMControl permanent license key using the installation wizard At the end of the 60-day ealuation period, you must purchase a license to continue using IBM Systems Director VMControl Standard Edition and IBM Systems Director VMControl Enterprise Edition. You can continue to use the no-charge function of IBM Systems Director VMControl Express Edition. To purchase a license, contact your IBM representatie, an IBM Business Partner, or IBM Americas Call Centers at 800-IBM-CALL. After you purchase a license, you will receie a CD-ROM containing a permanent license key. You must then install the key to continue using IBM Systems Director VMControl Standard Edition or IBM Systems Director VMControl Enterprise Edition. Before installing the permanent license key, perform the following tasks: Purchase the permanent license key for IBM Systems Director VMControl Standard Edition or IBM Systems Director VMControl Enterprise Edition. You receie a CD-ROM that you can use to install the key. Note: When you purchase and install the license for IBM Systems Director VMControl Enterprise Edition, you also get the license for IBM Systems Director VMControl Standard Edition. Your permanent license key for IBM Systems Director VMControl V2.3 continues to be alid for V Extract the contents of the compressed file on the CD-ROM. On Red Hat Enterprise Linux, SELinux must be disabled before installing IBM Systems Director VMControl. To check SELinux status, enter the sestatus command. If SELinux is not disabled, temporarily disable SELinux by entering the /usr/sbin/setenforce 0 command. 56 IBM Systems Director VMControl: Installation and User's Guide

63 To install the permanent license key for IBM Systems Director VMControl Standard Edition or IBM Systems Director VMControl Enterprise Edition, follow these steps: 1. To start installing, start the IBM Systems Director VMControl program file for the operating system that is running on the IBM Systems Director Serer. Operating system AIX Installation file name IBM Systems Director VMControl Standard Edition Systems_Director_VMControl_Standard_Edition_AIX.sh IBM Systems Director VMControl Enterprise Edition Systems_Director_VMControl_Enterprise_Edition_AIX.sh Linux for pseries IBM Systems Director VMControl Standard Edition Systems_Director_VMControl_Standard_Edition_Linux_Power.sh IBM Systems Director VMControl Enterprise Edition Systems_Director_VMControl_Enterprise_Edition_Linux_Power.sh Linux for xseries IBM Systems Director VMControl Standard Edition Systems_Director_VMControl_Standard_Edition_Linux_x86.sh IBM Systems Director VMControl Enterprise Edition Systems_Director_VMControl_Enterprise_Edition_Linux_x86.sh Linux for zseries IBM Systems Director VMControl Standard Edition Systems_Director_VMControl_Standard_Edition_Linux_System_z.sh IBM Systems Director VMControl Enterprise Edition Systems_Director_VMControl_Enterprise_Edition_Linux_System_z.sh Windows IBM Systems Director VMControl Standard Edition Systems_Director_VMControl_Standard_Edition_Windows.exe IBM Systems Director VMControl Enterprise Edition Systems_Director_VMControl_Enterprise_Edition_Windows.exe Note: If you install IBM Systems Director VMControl on an AIX or Linux serer and plan to use the installation wizard, you must start the installation program from a graphics-enabled session. The program file starts the installation wizard and displays the Welcome page. 2. Follow the instructions in the installation wizard to install the permanent license key for IBM Systems Director VMControl Standard Edition or IBM Systems Director VMControl Enterprise Edition. Installing the IBM Systems Director VMControl permanent license key silently At the end of the 60-day ealuation period, you must purchase a license to continue using IBM Systems Director VMControl Standard Edition and IBM Systems Director VMControl Enterprise Edition. You can continue to use the no-charge function of IBM Systems Director VMControl Express Edition. To purchase a license, contact your IBM representatie, an IBM Business Partner, or IBM Americas Call Centers at 800-IBM-CALL. After you purchase a license, you Chapter 2. IBM Systems Director VMControl V

64 will receie a CD-ROM containing a permanent license key. You must then install the key to continue using IBM Systems Director VMControl Standard Edition or IBM Systems Director VMControl Enterprise Edition. Before installing IBM Systems Director VMControl, perform the following tasks: Purchase the permanent license key for IBM Systems Director VMControl Standard Edition or IBM Systems Director VMControl Enterprise Edition. You receie a CD-ROM that you can use to install the key. Note: When you purchase and install the license for IBM Systems Director VMControl Enterprise Edition, you also get the license for IBM Systems Director VMControl Standard Edition. Your permanent license key for IBM Systems Director VMControl V2.3 continues to be alid for V Extract the contents of the compressed file on the CD-ROM. On Red Hat Enterprise Linux, SELinux must be disabled before installing IBM Systems Director VMControl. To check SELinux status, enter the sestatus command. If SELinux is not disabled, temporarily disable SELinux by entering the /usr/sbin/setenforce 0 command. To install the permanent license key for IBM Systems Director VMControl Standard Edition or IBM Systems Director VMControl Enterprise Edition silently, use a response file to specify information that the installation program requires. To install the permanently license key silently, follow these steps: 1. Open the installer.properties file in an ASCII text editor. 2. Use the comments in the installer.properties response file to modify the response file. 3. Sae the modified installer.properties response file. 4. Open a command prompt and change to the directory that contains the IBM Systems Director VMControl installation file and the response file. 5. From the command prompt, enter the appropriate installation command: Operating system License Installation command AIX Linux for pseries Linux for xseries VMControl Standard Edition VMControl Enterprise Edition VMControl Standard Edition VMControl Enterprise Edition VMControl Standard Edition VMControl Enterprise Edition./Systems_Director_VMControl_Standard_Edition_AIX.sh -i silent./systems_director_vmcontrol_enterprise_edition_aix.sh -i silent./systems_director_vmcontrol_standard_edition_linux_power.sh -i silent./systems_director_vmcontrol_enterprise_edition_linux_power.sh -i silent./systems_director_vmcontrol_standard_edition_linux_x86.sh -i silent./systems_director_vmcontrol_enterprise_edition_linux_x86.sh -i silent 58 IBM Systems Director VMControl: Installation and User's Guide

65 Operating system License Installation command Linux for zseries Windows VMControl Standard Edition VMControl Enterprise Edition VMControl Standard Edition VMControl Enterprise Edition./Systems_Director_VMControl_Standard_Edition_Linux_System_z.sh -i silent./systems_director_vmcontrol_enterprise_edition_linux_system_z.sh -i silent Systems_Director_VMControl_Standard_Edition_Windows.exe -i silent Systems_Director_VMControl_Enterprise_Edition_Windows.exe -i silent Installing IBM Systems Director VMControl agents and subagents Before you can use IBM Systems Director VMControl Standard Edition and IBM Systems Director VMControl Enterprise Edition, you need to set up an image repository and install the appropriate VMControl agent or subagent on the system that hosts the image repository. This topic proides information about preparing your image repository and installing the agent or subagent. You can install a VMControl subagent by using the installation wizard or you can manually install the subagent. If you are installing IBM Systems Director z/vm manageability access point agent, follow the specific directions for installing that agent. Related concepts: Understanding how VMControl uses AIX NIM on page 20 Creating and discoering NIM image repositories for AIX Related tasks: Updating IBM Systems Director VMControl on page 82 Related reference: Requirements and support for AIX and Linux using storage copy serices (SCS) on page 30 Planning for IBM Systems Director VMControl on page 14 Power Systems requirements and support on page 18 VMware requirements and support on page 39 z/vm irtualization requirements and support on page 43 Related information: Required Fix Leels for VMControl Dependencies Preparing to install IBM Systems Director VMControl NIM subagent In order for IBM Systems Director VMControl to manage irtual appliances that contain AIX mksysb or lpp_source images, you must hae a properly installed and configured NIM master in your enironment. Use these instructions to properly prepare your NIM master. Ensure that your system meets the following requirements: The system is running AIX ersion or later Chapter 2. IBM Systems Director VMControl V

66 The following filesets are installed: dsm.core openssh.base.client openssl.base Note: To check for these filesets on the NIM master, run the following commands: lslpp -l grep dsm lslpp -l grep openssh lslpp -l grep openssl The system has been discoered, accessed, and inentoried by your IBM Systems Director Serer The system must also be configured as a NIM master system. To configure your system to be a NIM master, run the following command: nim_master_setup -a deice=path [-a disk=disk_name] -B where path is the absolute path of the directory where the AIX bos.sysmgt package can be found. Optionally, you can use the disk=disk_name attribute to control which physical olume holds the required /export/nim file system. For example, if you are using a SAN for your /export/nim file system, you need to use the disk=disk_name attribute. Note: The nim_master_setup command can take 20 minutes or longer to run. If the NIM image repository (NIM Master) connects to IBM Systems Director Serer through one network adapter, and connects to the irtual serer where you plan to deploy a irtual appliance through a different network adapter, complete the following steps to configure your networks for the deploy task. 1. Log on to the NIM Master. 2. When you ran nim_master_setup to configure your NIM Master, the master_net network object was created for you to represent the network associated with the NIM Master's primary network interface. If the NIM Master has a secondary interface that you will be using to deploy irtual serers, then you will need to create one or more additional NIM network definitions. Note: Do not define a NIM network object name that begins with the name of another NIM network object. a. Define a NIM network object for the NIM Master's secondary network interface. For example: nim -o define -t ent -a net_addr= a snm= secondary_net where is the IP address of the network being defined, is the subnet mask for the network, and secondary_net is the NIM network object name that you are creating.for more information, see the Defining NIM networks topic in the IBM Systems Information Center. b. If the irtual serer that you will be deploying is on the same network as the NIM Master's secondary interface, then skip this step. If it is on a different network, then you must define another NIM network object for the irtual serer. For example: nim -o define -t ent -a net_addr= a snm= deploy_net 60 IBM Systems Director VMControl: Installation and User's Guide

67 where is the IP address of the network being defined, is the subnet mask for the network, and deploy_net is the NIM object name that you are creating. 3. Attach the secondary_net network object you created to the NIM Master resource, for example: nim -o change -a if2= secondary_net a cable_type2=n/a master 4. If you created a new deploy_net network, a static route must be established between it and the secondary_net network object. For more information, see the Establishing a static NIM route between networks topic in the IBM Systems Information Center. You should also remoe the default route on the deploy_net network. Related reference: Hardware and software requirements Requirements and support for AIX using NIM Requirements and support for AIX and Linux using storage copy serices (SCS) VMware requirements and support Power Systems requirements and support on page 18 Installing IBM Systems Director VMControl subagents using the installation wizard You can access and install IBM Systems Director VMControl subagents for NIM, Center, and Common Repository using the IBM Systems Director Agent Installation wizard. You can start this wizard from the VMControl Summary page or from the IBM Systems Director Release Management task. Before you can install the subagent for your irtualization enironment, erify the following prerequisites: Ensure that the architecture, and operating system type and leel of the target system is supported for the subagent you want to install. For more information, see "Requirements and support for AIX using NIM", "Requirements and support for AIX and Linux using storage copy serices (SCS)", or "VMware Center requirements and support." If you are installing the NIM subagent, ensure that the IBM Systems Director Common Agent is installed on your target NIM master. If you are installing the Common Repository subagent to a supported Virtual I/O Serer (VIOS) system, the VIOS system already has a suitable Common Agent; howeer, consider updating VIOS to the latest aailable firmware leel. If you are installing the VMware Center 4.x subagent, ensure that the IBM Systems Director Common Agent is installed on your target Windows system. Note: For more information, see "Installing Common Agent." Note the name of the host system on which you want to install the subagent. Ensure that the host system has been discoered, accessed, and inentoried by your IBM Systems Director Serer. Note the name of the subagent that you want to install. You can install one of the following subagents: NIM subagent: CommonAgentSubagent_VMControl_NIM VMware Center 4.x subagent: CommonAgentSubagent_VSM_VC4x VMware VirtualCenter 2.x subagent: CommonAgentSubagent_VSM_VC2x Chapter 2. IBM Systems Director VMControl V

68 VMware ESX 4.x subagent: CommonAgentSubagent_VSM_ESX4x VMware ESX 3.x subagent: CommonAgentSubagent_VSM_ESX3x Common Repository subagent: CommonAgentSubagent_VMControl_CommonRepository Notes: Ensure that the system clocks on the IBM Systems Director Serer and the target system match as closely as possible. If the system clocks do not match closely enough, installation of the Common Repository subagent might fail. If you are installing this subagent on a system that is running Red Hat Enterprise Linux 5.4, ensure that the file system has a unique Volume Group (VG) name such as ICPVolGroup. The default Volume Group name for the file system is VolGroup00. To check the Volume Group name, run the gdisplay command and check the VG Name entry. Installing from the VMControl Summary page To install a VMControl subagent from the VMControl Summary page, follow these steps: 1. On the Summary page, click Install Agents. 2. On the Welcome page of the Agent Installation wizard, click Next. 3. On the Agents page, click Common Agent Subagent Packages. 4. From the Common Agent Subagent Packages iew, select the subagent that you want to install. 5. Follow the instructions in the installation wizard to install the subagent for your irtualization enironment. Installing from the IBM Systems Director Release Management task To install a VMControl subagent from the IBM Systems Director Release Management task, follow these steps: 1. In the IBM Systems Director naigation pane, expand Release management. 2. Click Agents. 3. On the Agents page, click Common Agent Subagent Packages. 4. From the Common Agent Subagent Packages iew, select the subagent that you want to install. 5. Click Actions on the menu bar, and select Release Management > Install Agent. 6. Follow the instructions in the installation wizard to install the subagent for your irtualization enironment: If the VMControl subagent installation fails, check the following error logs for detailed error messages: AIX or Linux: director/agent/logs/*.xml Windows: Director\agent\logs\*.xml where Director is the path where IBM Systems Director is installed. Note: To erify that the subagent for NIM installed successfully, check the error log for messages beginning with DNZIMN: 62 IBM Systems Director VMControl: Installation and User's Guide

69 Installing IBM Systems Director VMControl subagents manually You can locate VMControl subagents on IBM Systems Director Serer and install them manually on host systems in your enironment. Before you can install the subagent for your irtualization enironment, erify the following prerequisites: Ensure that the architecture, and operating system type and leel of the target system is supported for the subagent you want to install. For more information, see "Requirements and support for AIX using NIM", "Requirements and support for AIX and Linux using storage copy serices (SCS)", or "VMware Center requirements and support." If you are installing the NIM subagent, ensure that the IBM Systems Director Common Agent is installed on your target NIM master. If you are installing the Common Repository subagent to a supported Virtual I/O Serer (VIOS) system, the VIOS system already has a suitable Common Agent; howeer, consider updating VIOS to the latest aailable firmware leel. If you are installing the VMware Center 4.x subagent, ensure that the IBM Systems Director Common Agent is installed on your target Windows system. Note: For more information, see "Installing Common Agent." If you are installing the Common Repository subagent on a system that is running Red Hat Enterprise Linux (RHEL) 5.4, ensure that the file system has a unique Volume Group (VG) name such as ICPVolGroup. The default Volume Group name for the file system is VolGroup00. To check the Volume Group name, run the gdisplay command and check the VG Name entry. To manually install VMControl subagents, follow these steps: 1. Copy the VMControl subagent to the host system by following these steps: a. Locate the subagent file. Each subagent has a directory that begins with CommonAgentSubagent_ For example, the NIM subagent is in directory CommonAgentSubagent_VMControl_NIM_ Each directory has one compressed file that contains the feature for that subagent. The default location is as follows: AIX or Linux: /opt/ibm/director/packaging/agent Windows: C:\Program Files\IBM\Director\packaging\agent b. Copy the appropriate compressed file to a temporary directory on the host system, such as C:\temp\site or /tmp/site. For example, C:\temp\site\com.ibm.director.im.rf.nim.subagent.zip 2. Install the VMControl subagent on the host system by following these steps: a. Change directory to the host system bin directory for your operating system: AIX or Linux: /opt/ibm/director/agent/bin Windows: C:\Program Files\ibm\Director\agent\bin b. Run the installation program as follows: Note: Line indents indicate a continuation of the preceding line. The entire installation command must be typed on one line. Chapter 2. IBM Systems Director VMControl V

70 NIM subagent./lwiupdatemgr.sh -installfeatures -featureid com.ibm.director.im.rf.nim.subagent -fromsite jar:file:/tmp/site/com.ibm.director.im.rf.nim.subagent.zip\!/site.xml -tosite "file:/ar/opt/tioli/ep/runtime/agent/subagents/eclipse/" Common Repository subagent:./lwiupdatemgr.sh -installfeatures -featureid com.ibm.director.im.cr.agent.installer -fromsite jar:file:/tmp/site/com.ibm.director.im.cr.agent.installer.zip\!/site.xml -tosite "file:/opt/ibm/director/agent/runtime/agent/subagents/eclipse/" VMware Center 4.x subagent.\lwiupdatemgr -installfeatures -featureid com.ibm.director.sm. c4x.agent -fromsite jar:file:/c:/temp/site/smc4x_subagent.zip!/site.xml -tosite "file:/c:/program files/ibm/director/agent/runtime/agent/ subagents/eclipse/" where tmp/site or temp/site is the name of the temporary directory you hae created. 3. If the VMControl subagent installation fails, check the following error logs for detailed error messages: AIX or Linux: director/agent/logs/*.xml Windows: Director\agent\logs\*.xml where Director is the path where IBM Systems Director is installed. 4. Stop and restart the Common Agent to actiate the VMControl subagent by running the following script files: AIX or Linux: director/agent/runtime/agent/bin/endpoint.sh restart Windows: Director\agent\runtime\agent\bin\endpoint.bat restart where Director is the path where IBM Systems Director is installed. Installing the IBM z/vm Manageability Access Point Agent Use these instructions to perform pre-installation tasks and to install the IBM z/vm Manageability Access Point Agent on each z/vm system that you want to manage with IBM Systems Director. Important: The following instructions apply only to a z/vm system for which the following is true: The configuration of the system has not been substantially changed since installation. The z/vm system will use z/vm Directory Maintenance Facility (DirMaint) to manage the user directory, and DirMaint has not yet been configured or started. DirMaint is only one of seeral aailable directory manager products. You are not using an external security manager (ESM) product. If these assumptions are not alid, perform the tasks described in these examples using the documentation proided by z/vm, the directory manager product, and the external security manager product, where applicable. In cases of conflict, the documentation proided by these products should be considered the authoritatie reference. The following prerequisites must be met before you complete the tasks described in this topic: z/vm 5.4, 6.1, or a higher z/vm ersion that supports the IBM z/vm Manageability Access Point Agent is installed The following PTFs that are required for the IBM z/vm Manageability Access Point Agent must be installed: 64 IBM Systems Director VMControl: Installation and User's Guide

71 Table 5. z/vm 5.4 and 6.1 PTFs APAR number Component name PTF number for z/vm 5.4 PTF number for z/vm 6.1 VM64514 CMS UM32505 Not required VM64515 CMS UM32503 Not required VM64516 CMS UM32521 Not required VM64517 CMS UM32522 Not required VM64596 CMS UM32693 Not required VM64677 CMS UM32765 UM32766 VM64595 DIRM UV61088 Not required VM64762 DIRM UV61099 UV61100 VM64813 CMS Not required UM33229 VM64822 CP Not required UM33246 VM64904 CMS Not required UM33269 VM64917 CMS Not required UM33302 VM64956 CMS Not required UM33380 VM65003 CMS Not required UM33435 Note: z/vm 6.1 supports host and irtual serer performance related monitors with APAR VM Howeer, host and irtual serer performance related monitor support is not aailable for systems running z/vm 5.4. TCP/IP is enabled and working A VSWITCH or comparable network connection is aailable to use Related tasks: Updating IBM Systems Director VMControl on page 82 Configure and start DirMaint: You must configure DirMaint for basic use and start it so you can use it to manage the user directory. To configure DirMaint, complete the following steps: Configure and start DirMaint. For z/vm 5.4, configure and start DirMaint following the instructions in the section Configuring the Directory Maintenance Facility in the manual z/vm V5R4.0 Getting Started with Linux on System z9 and zseries (SC ), omitting the subsection: Step for modifying the OPERATOR's directory entry. For z/vm 6.1, configure and start DirMaint following the instructions in the section Configuring the Directory Maintenance Facility in the manual z/vm V6R1.0 Getting Started with Linux on System z (SC ), omitting the subsection: Step for modifying the OPERATOR's directory entry Note: The DirMaint a-disk maintains a file which logs actiity between the z/vm Systems Management API and DirMaint. This file on the disk is periodically pruned, eery nine days. Howeer, the IBM Systems Director extended discoery function for z/vm can cause a higher rate of actiity than expected and cause this disk to fill up before the prune interal. If the disk becomes full, DirMaint becomes unresponsie. Both DirMaint and SMAPI must be restarted, and the DirMaint Chapter 2. IBM Systems Director VMControl V

72 a-disk must either be increased in size or the 1SAPI REQUESTS file pruned. Issue the DIRM ENABLE command to allow DirMaint to resume updating the directory. Configure Systems Management API serer enironment: You must configure the z/vm Systems Management Application Programming Interface (API) serer enironment for basic use, and for use specifically by the IBM z/vm Manageability Access Point Agent. For z/vm 5.4, additional information about configuring the z/vm Systems Management API serer enironment can be found in: The section Installation and Configuration in the manual z/vm V5R4.0 Systems Management Application Programming (SC ). The section DirMaint Support for Systems Management APIs in the manual z/vm V5R4.0 Directory Maintenance Facility Tailoring and Administration Guide (SC ). For z/vm 6.1, additional information about configuring the z/vm Systems Management API serer enironment can be found in: The section Installation and Configuration in the manual z/vm V6R1 Systems Management Application Programming (SC ). The section DirMaint Support for Systems Management APIs in the manual z/vm V6R1 Directory Maintenance Facility Tailoring and Administration Guide (SC ). The section Configuring z/vm for an Ensemble in the manual z/vm V6R1 CP Planning and Administration (SC ). To configure the z/vm Systems Management API serer enironment, complete the following steps: 1. Select from the following options: If the z/vm System API serer enironment is configured for the Unified Resource Manager or a VSMGUARD irtual machine has been configured, you must use the manuals listed aboe to complete the z/vm Systems Management API configuration. If you are not using a Unified Resource Manager or VSMGUARD configuration, you can use the manuals listed aboe for background information. Then continue with the next step to complete the configuration steps. 2. Log on to MAINT. 3. Modify the PROFILE EXEC file of worker serer VSMWORK1 to access the DirMaint interface minidisk as follows: a. If user VSMWORK1 is logged on or disconnected, run the following command to log it off: force smwork1 b. Run the following commands to link and access VSMWORK1's 191 minidisk: link smwork mr access 091 z c. Optional: Run the following command to sae a copy of the current PROFILE EXEC file: copyfile profile exec z = newfiletype = (olddate d. Edit PROFILE EXEC: 66 IBM Systems Director VMControl: Installation and User's Guide

73 xedit profile exec z e. Add the three lines shown below in bold: PROFILE EXEC Z1 V 130 Trunc=130 Size=137 Line=0 Col=1 Alt= ***TopofFile*** /**********************************************************************/ /* A New for z/vm Version 5 Release */ /**********************************************************************/ /* */ /* Sample PROFILE EXEC for a Virtual Systems Management API */ /* worker irtual machine. */ /* */ /* Change actiity */ /* */ allow more memory for smapi serers */ /**********************************************************************/ CP SP CONS * START CP SET CONCEAL OFF CP SET CONCEAL ON EXEC DIRMAINT EXECLOAD EXEC DIRMAINT DEFAULT MENUS DISABLED EXEC DIRMAINT DEFAULT PROMPTS DISABLED ====> f. Run the following command to sae the file and exit: file g. Run the following command to release and detach VSMWORK1's 191 minidisk: release z (detach 4. For z/vm 6.1, modify the profile of worker serers VSMWORK2 and VSMWORK3 by repeating step 3 on page 66 for each serer. 5. Configure DirMaint to allow the worker serers to use the ASUSER prefix keyword without supplying a password, and to enable asynchronous update notifications as follows: a. Run the following command to create the CONFIGSM DATADVH file: xedit configsm datadh a b. Add the following lines: CONFIGSM DATADVH A1 F 80 Trunc=80 Size=5 Line=0 Col=1 Alt= ***TopofFile*** ALLOW_ASUSER_NOPASS_FROM= VSMWORK1 * ALLOW_ASUSER_NOPASS_FROM= VSMWORK2 * ALLOW_ASUSER_NOPASS_FROM= VSMWORK3 * ASYNCHRONOUS_UPDATE_NOTIFICATION_EXIT.UDP= DVHXNE EXEC ASYNCHRONOUS_UPDATE_NOTIFICATION_EXIT.TCP= DVHXNE EXEC ***EndofFile*** c. Run the following XEDIT subcommand to sae the file and exit: file d. Run the following command to place the file on the appropriate DirMaint minidisk: dirmaint file configsm datadh a = = d 6. Configure the DirMaint command to set authorizations as follows: If the z/vm system is at ersion 5.4 or 6.1 prior to application of APAR VM64820, run the following commands to allow the worker serer Chapter 2. IBM Systems Director VMControl V

74 VSMWORK1-3 to use specific DirMaint commands and to allow the user ZVMMAPLX to use specific DirMaint commands: dirmaint for all authfor smwork1 cmdleel 140a cmdset a dirmaint for all authfor smwork1 cmdleel 150a cmdset a dirmaint for all authfor smwork2 cmdleel 140a cmdset a dirmaint for all authfor smwork2 cmdleel 150a cmdset a dirmaint for all authfor smwork3 cmdleel 140a cmdset a dirmaint for all authfor smwork3 cmdleel 150a cmdset a dirmaint for all authfor zmmaplx cmdleel 140a cmdset adghops dirmaint for all authfor zmmaplx cmdleel 150a cmdset adghops If the z/vm system is not at ersion 5.4 or 6.1 prior to application of APAR VM64820, run the following commands to allow the worker serer VSMWORK1-3 to use specific DirMaint commands: dirmaint for all authfor smwork1 cmdleel 140a cmdset adghops dirmaint for all authfor smwork1 cmdleel 150a cmdset adghops dirmaint for all authfor smwork2 cmdleel 140a cmdset adghops dirmaint for all authfor smwork2 cmdleel 150a cmdset adghops dirmaint for all authfor smwork3 cmdleel 140a cmdset adghops dirmaint for all authfor smwork3 cmdleel 150a cmdset adghops 7. Authorize the Systems Management API requests as follows: a. Run the following command to access the appropriate SFS directory: access msys:smwork1. z (forcerw b. Optional: Run the following command to sae a copy of the current VSMWORK1 AUTHLIST file: copyfile smwork1 authlist z = newfiletype = (olddate c. Run the following XEDIT subcommand to edit the VSMWORK1 AUTHLIST file: xedit smwork1 authlist z d. Run the following XEDIT subcommand to allow the full width of each line to be displayed: set erify 1 * e. Add the line shown in italics, making sure to place the keywords in columns 1, 66, and 131 as in the existing lines: VSMWORK1 AUTHLIST Z1 F 195 Trunc=195 Size=4 Line=0 Col=1 Alt= ***TopofFile*** DO.NOT.REMOVE DO.NOT.RE MOVE DO.NOT.REMOVE MAINT ALL ALL VSMPROXY ALL ALL ZVMMAPLX ALL ALL ***EndofFile*** Tip: The suggested way to add this line with the keywords in the correct columns is to copy an existing line, possibly using the XEDIT " (DUPLICATE) prefix subcommand, and oertype the existing keywords as appropriate. f. Run the following XEDIT subcommand to sae the file and exit: 68 IBM Systems Director VMControl: Installation and User's Guide

75 file g. Run the following command to release the directory: release z 8. Update the irtual storage sizes of certain z/vm Systems Management API serers as follows: a. Run the following commands to update the maximum and initial irtual storage sizes of user VSMREQIU: dirmaint for smreqiu maxstorage 128m dirmaint for smreqiu storage 128m b. Run the following commands to update the maximum and initial irtual storage sizes of user VSMWORK1: dirmaint for smwork1 maxstorage 128m dirmaint for smwork1 storage 128m c. Run the following commands to update the maximum and initial irtual storage sizes of user VSMWORK2: dirmaint for smwork2 maxstorage 128m dirmaint for smwork2 storage 128m d. Run the following commands to update the maximum and initial irtual storage sizes of user VSMWORK3: dirmaint for smwork3 maxstorage 128m dirmaint for smwork3 storage 128m 9. Modify the PROFILE EXEC file of user AUTOLOG1 so that the z/vm Systems Management API enironment is started when z/vm is started as follows: a. If user AUTOLOG1 is logged on or disconnected, run the following command to log it off: force autolog1 b. Run the following commands to link and access AUTOLOG1's 191 minidisk: link autolog mr access 091 z c. Optional: Run the following command to sae a copy of the current PROFILE EXEC file: copyfile profile exec z = newfiletype = (olddate d. Run the following command to edit the PROFILE EXEC file: xedit profile exec z e. Add the two lines shown in bold: Chapter 2. IBM Systems Director VMControl V

76 PROFILE EXEC Z1 V 130 Trunc=130 Size=16 Line=0 Col=1 Alt= ***TopofFile*** /***************************/ /* Autolog1 Profile Exec */ /***************************/ Address Command CP XAUTOLOG VMSERVS CP XAUTOLOG VMSERVU CP XAUTOLOG VMSERVR CP XAUTOLOG DTCVSW CP XAUTOLOG DTCVSW CP XAUTOLOG TCPIP CP XAUTOLOG DIRMAINT CP XAUTOLOG DATAMOVE CP SLEEP 30 SEC CP XAUTOLOG VSMWORK CP LOGOFF ***EndofFile*** f. Run the following XEDIT subcommand to sae the file and exit: file g. Run the following command to release and detach AUTOLOG1's 191 minidisk: release z (detach 10. Run the following command to start the z/vm Systems Management API serer enironment: xautolog smwork1 11. Run the following command to log off: logoff Configure ZVMMAPLX user ID: You must configure the ZVMMAPLX user ID by updating the user directory. Note: This task assumes that you are using a VSWITCH as your network connection. Howeer, other comparable types of network connections can be used. You need one z/vm manageability access point on each z/vm system on which you want to use IBM Systems Director z/vm management functions. You should hae no more than one z/vm manageability access point per z/vm system. A z/vm guest irtual serer named ZVMMAPLX is predefined in the z/vm user directory and is designed to be used for the z/vm manageability access point. The ZVMMAPLX default user ID definition contains a default VSWITCH named VSWID1, and it contains default alues for the size and label of a minidisk. The default VSWITCH name and default alues for the minidisk often need to be modified. You need to ensure that the VSWITCH defined in the ZVMMAPLX user ID is accessible. Also, you need ensure there is sufficient disk space aailable for the ZVMMAPLX irtual serer. Use the following example as a guide to changing the default alues. The example shows a minidisk with 3338 cylinders, which is the size of a 3390 Mod 3 DASD. Formatting a disk of this size for Linux results in about 2.2 GB of disk space. After Linux is installed, the remaining disk space would be insufficient. 70 IBM Systems Director VMControl: Installation and User's Guide

77 Therefore, the file in the user directory is modified to specify a minidisk that is backed by a 3390 Mod 9 DASD with cylinders. This configuration results in almost 7 GB of disk space. The example also shows that the default VSWITCH name of VSWID1 is modified to the name of a VSWITCH that has been created preiously, for example, VSW1. You might need to add a significant amount of disk space if the z/vm manageability access point will contain an image repository. For example, a large file system could be mounted oer /ar/opt/ibm, as the stored images are below this directory. You can add more disk space now to prepare for an image repository, or you can add disk space later. To configure the ZVMMAPLX user ID, complete the following steps: 1. Log on to MAINT. 2. Run the following command to modify the user directory: dirmaint for zmmaplx get You should see results that are similar to the following output: DVHXMT1191I Your GET request has been sent for processing. Ready; T=0.03/ :44:53 DVHREQ2288I Your GET request for ZVMMAPLX at * has been accepted. DVHGET3304I Directory entry ZVMMAPLX is now locked. RDR FILE reader_file_number SENT FROM DIRMAINT PUN WAS 0931 RECS 0019 CPY NOHOLD NOKEEP DVHREQ2289I Your GET request for ZVMMAPLX at * has completed; with RC DVHREQ2289I = A 3. Run the following command to receie the directory entry from the reader: receie reader_file_number zmmaplx direct a (rep where reader_file_number is the reader file number specified in the output of the DIRMAINT GET command. You should see results that are similar to the following output: File ZVMMAPLX DIRECT A0 replaced by ZVMMAPLX DIRECT A0 receied from DIRMAINT at System_A where System_A is your z/vm system. 4. Run the following command to open the file: xedit zmmaplx direct The file should look like the following example: Note: The LNKNOPAS and LANG AMENG options are required for the setup of this irtual serer. Chapter 2. IBM Systems Director VMControl V

78 USER ZVMMAPLX DRCT 512M 1G ABCEG IPL 0150 OPTION LNKNOPAS LANG AMENG CONSOLE SPOOL 00C 2540 READER * SPOOL 00D 2540 PUNCH A SPOOL 00E 1403 A LINK MAINT RR LINK MAINT 019D 019D RR LINK MAINT 019E 019E RR NICDEF 7000 TYPE QDIO LAN SYSTEM VSWID1 MDISK $$$LNX MR 5. Edit the file as follows: Specify a VSWITCH that is appropriate for your installation. You can change the VSWITCH name of VSWID1 to the name of a VSWITCH that has been created preiously, for example, VSW1. Note: Ensure that you update the VSWITCH to enable the ZVMMAPLX machine to access the VSWITCH. Define a minidisk for the irtual serer by changing the size and label for the minidisk to the alues appropriate for your system. 6. Run the following command to update the user directory: dirmaint for zmmaplx replace You should see results that are similar to the following output: PUN FILE 0595 SENT TO DIRMAINT RDR AS 0932 RECS 0023 CPY NOHOLD NOKEEP DVHXMT1191I Your REPLACE request has been sent for processing. Ready; T=0.03/ :57:47 DVHREQ2288I Your REPLACE request for ZVMMAPLX at * has been accepted. DVHBIU3450I The source for directory entry ZVMMAPLX has been updated. DVHBIU3424I The next ONLINE will take place immediately. DVHDRC3451I The next ONLINE will take place ia delta object directory. DVHBIU3428I Changes made to directory entry ZVMMAPLX hae been placed DVHBIU3428I online. DVHREP3603I Directory entry ZVMMAPLX is now unlocked. DVHREQ2289I Your REPLACE request for ZVMMAPLX at * has completed; with DVHREQ2289I RC = 0. Install Linux on the ZVMMAPLX user ID: You must install Linux on the ZVMMAPLX user ID. This task installs Linux with the root file system onto minidisk 150. To install Linux on the ZVMMAPLX user ID, complete the following steps: 1. To install Linux, refer to the following documentation: Installation documentation for your Linux distribution. For information about the supported Linux distributions, see Supported operating systems. z/vm V5R4.0 Getting Started with Linux on System z9 and zseries (SC ) z/vm V6R1.0 Getting Started with Linux on System z (SC ) Virtualization Cookbooks: z/vm and Linux on IBM System z The Virtualization Cookbook for Red Hat Enterprise Linux 5.2 (SG ) 72 IBM Systems Director VMControl: Installation and User's Guide Note: The installation process for Red Hat Enterprise Linux 5.3 might be slightly different than the process described in this cookbook.

79 z/vm and Linux on IBM System z The Virtualization Cookbook for SLES 10 SP2 (SG ) 2. If the Linux system is not already running, log on to the ZVMMAPLX user ID to start the Linux system. Ensure that required RPMs are installed: You must erify that all of the required RPMs for your Linux distribution are installed on the Linux running on the ZVMMAPLX user ID. The following RPMs are the minimum required leels of RPMs that you must install. Ensure that the required RPMs are installed for the operating system you are running: Table 6. RPMs required for arious operating system installations Installation scenario Required RPMs for Platform Agent and Required RPMs for Platform Agent and later releases Red Hat Enterprise Linux ersion 5.3 for IBM System z 64- bit compat-libstdc s390.rpm compat-libstdc s390.rpm expect s390.rpm compat-libstdc s390x.rpm expect s390x.rpm libxml s390x.rpm libx el5.s390.rpm libxp el5.s390.rpm libxml s390.rpm libxslt el5_2.2.s390.rpm libxslt el5_2.2.s390x.rpm pam el5.s390.rpm star-1.5a75-2.s390x.rpm pam el5.s390.rpm star-1.5a75-2.s390x.rpm xorg-x11-xauth s390x.rpm SUSE Linux Enterprise Serer 9 SP 4 for IBM System z 64- bit compat s390x.rpm compat-32bit s390x.rpm Not supported. expect-5.42*.rpm libxml s390x.rpm libxml2-32bit s390x.rpm libxslt s390x.rpm pam-32bit s390x.rpm pam-modules-32bit s390x.rpm star-1.5final s390x.rpm XFree86-libs-32bit s390x.rpm Chapter 2. IBM Systems Director VMControl V

80 Table 6. RPMs required for arious operating system installations (continued) Installation scenario SUSE Linux Enterprise Serer 10 SP 2 for IBM System z SUSE Linux Enterprise Serer 11 for IBM System z 64- bit 64- bit Required RPMs for Platform Agent and compat-32bit s390x.rpm expect-5.42*.rpm libxml s390x.rpm libxml2-32bit s390x.rpm libxslt s390x.rpm pam-32bit s390x.rpm pam-modules-32bit s390x.rpm star-1.5final s390x.rpm xorg-x11-libs-32bit s390x.rpm xorg-x s390x.rpm Required RPMs for Platform Agent and later releases compat s390x.rpm expect s390x.rpm libxml s390x.rpm libxslt s390x.rpm pam-32bit s390x.rpm star-1.5final s390x.rpm Not supported. libstdc bit s390x.rpm libgcc43-32bit _ s390x.rpm expect s390x.rpm libxml s390x.rpm libxslt s390x.rpm pam-32bit s390x.rpm star-1.5final s390x.rpm 1. Run the following command to determine whether the RPMs are installed: rpm -qa 2. If the RPMs are not installed, ensure that you install them. Ensure that required Linux kernel leels and patches are installed: You must ensure that all of the required kernel leels and patches for your Linux distribution are installed on the Linux running on the ZVMMAPLX user ID. Ensure that the following kernel leels and patches are installed for any Linux systems on which the IBM z/vm Manageability Access Point Agent is installed. To erify whether these patches are on your system, and to obtain these patches, contact the serice proider for your Linux distribution. The next update release of your Linux distribution after the releases stated in the following table should contain these patches. 74 IBM Systems Director VMControl: Installation and User's Guide

81 Table 7. Kernel leels and patches required for arious operating system installations Installation scenario Red Hat Enterprise Linux ersion 5.3 for IBM System z SUSE Linux Enterprise Serer 9 SP 4 for IBM System z SUSE Linux Enterprise Serer 10 SP 2 for IBM System z Required kernel leels and patches 64-bit Red Hat Enterprise Linux bug af_iuc: consolidated Bugzilla for miscellaneous af_iuc fixes. Red Hat Enterprise Linux bug iuc: proide second per-cpu IUCV command parameter block. 64-bit Minimum kernel leel , plus patch from Noell bug SLES 9 SP4 - IBM LTC zseries Maintenance Patches (#54). 64-bit Minimum kernel leel , plus patches and from Noell bug SLES 10 SP2 - IBM LTC zseries Maintenance patches (#30). Ensure that the kernel module af_iuc is properly loaded: You must erify that the kernel module af_iuc is properly loaded. To ensure that the kernel module af_iuc is properly loaded, complete the following steps: 1. Run the following command: lsmod grep af If the module was properly loaded, running the command will produce results similar to the following output: af_iuc iuc af_iuc If you do not receie this output, the module was not loaded and you need to perform the next step. 2. Load the module. a. Run the following command to load the module: modprobe af_iuc b. Configure the module to load eery time the system is booted: For SUSE Linux: 1) Open the following file: /etc/sysconfig/kernel 2) Look for the following line: MODULES_LOADED_ON_BOOT="" 3) Change the line as follows: MODULES_LOADED_ON_BOOT="af_iuc" For Red Hat Linux: 1) Create the following file: /etc/rc.modules Chapter 2. IBM Systems Director VMControl V

82 2) Add the following line to the file: modprobe af_iuc 3) Set the following permission to the file: chmod +x /etc/rc.modules Ensure that the appropriate priilege classes are defined for the ZVMMAPLX user ID: You must gie the ZVMMAPLX user ID the necessary priilege classes or authorize the user ID to issue the commands through the external security manager. The ZVMMAPLX irtual serer (the irtual serer on which the IBM z/vm Manageability Access Point Agent runs) requires the following z/vm priclasses and commands. Table 8. Priilege class and commands required by the ZVMMAPLX irtual serer Priilege Class Command A QUERY CPUAFFINITY SET CPUAFFINITY SET SHARE B ATTACH QUERY QUERY LAN QUERY OSA QUERY SYSTEM QUERY TDISK QUERY VSWITCH C SET PRIVCLASS QUERY PRIVCLASS 1 E INDICATE USER QUERY PRIVCLASS 1 QUERY SHARE G DETACH LINK QUERY MDISK QUERY USERID QUERY VIRTUAL DASD 'any' QUERY USERS 1 This command is aailable to both C and E users. Howeer, you only need to authorize the ZVMMAPLX user ID to one ersion of the command. In addition to the priilege classes listed in the table, the ZVMMAPLX irtual serer must hae the ability to link to other irtual serers without specifying a password. This can be done by specifying the LNKNOPAS option in the directory 76 IBM Systems Director VMControl: Installation and User's Guide

83 entry for the ZVMMAPLX user ID. When LNKNOPAS is specified, password authorization may still be required when an external security manager (ESM) is installed. For more information about external security manager authorizations, refer to the documentation for your external security manager. For documentation related to RACF, refer to Shelf: z/vm V5R4.0 or Shelf: z/vm V6R1.0. Install the Platform Agent: You must install the IBM Systems Director Platform Agent on the Linux that runs on your ZVMMAPLX user ID. Refer to Installing Platform Agent to install the IBM Systems Director Platform Agent on your z/vm system. Install the IBM z/vm Manageability Access Point Agent: You must obtain the installation package, extract the contents of the package, run the installation script, and erify the installation on the Linux that runs on your ZVMMAPLX user ID. To install the IBM z/vm Manageability Access Point Agent, complete the following steps: 1. Obtain the following installation package: SysDir6_2_1_zVM_Map_Agent_System_z.tar.gz The installation package files are aailable from the IBM Systems Director download Web page at downloads/. From the IBM Systems Director Downloads Web page, complete the following steps: a. Click Agents. b. Click Choose and download Common or Platform Agents to install manually. c. Log on using your uniersal IBM user ID and password. d. Accept the license agreement. e. On the Downloads page for IBM Systems Director Agents for Manual Deployment, scroll down to the Agents for IBM Systems Director Serers section, and select IBM z/vm Manageability Access Point Agent for System z. f. Click Download now. 2. Copy the installation package to the Linux that runs on your ZVMMAPLX user ID. 3. To extract the contents of the installation package, type the following command: tar -zxf SysDir6_2_1_zVM_Map_Agent_System_z.tar.gz 4. Change directory to the FILES subdirectory by running the following command: cd FILES 5. Start the installation by running the following script as root user:./dir _zmmapagent_linux.sh Chapter 2. IBM Systems Director VMControl V

84 6. If the installation process runs without errors, erify whether the IBM z/vm Manageability Access Point Agent installed successfully by checking for the ersion.zmmap file in the /opt/ibm/zmmap directory. Note: An alternate method of ensuring that IBM z/vm Manageability Access Point Agent is installed is to run the following command that is appropriate for the leel of Platform Agent that is installed: Platform Agent /opt/ibm/icc/bin/cimcli ei IBMzVM_HostOperatingSystem Platform Agent x /opt/ibm/icc/cimom/bin/cimcli ei IBMzVM_HostOperatingSystem 7. Ensure IBM z/vm Manageability Access Point Agent has an Internet Protocol ersion 4 (IP4) address which is contacted by the directory manager (for example, DirMaint). If the IBM z/vm Manageability Access Point Agent has multiple IP4 addresses configured on the system, then the directory manager must be able to send notifications to any of the addresses. The IP address registered with the directory manager for this notification can be configured using a configuration file named map_agent.conf and must be located in the /etc/opt/ibm/zmmap/.cimm/ folder. The file must contain the IP4 address in the following format: DirMgr_Notification_Ipaddr=<Ip Address> For example: DirMgr_Notification_Ipaddr= Run one of the following commands to further erify that the IBM z/vm Manageability Access Point Agent installed successfully: x Platform Agent is installed: /opt/ibm/icc/cimom/bin/cimcli ei IBMzVM_HostOperatingSystem Platform Agent is installed: /opt/ibm/icc/bin/cimcli ei IBMzVM_HostOperatingSystem You should see output that is like the following example: path= IBMzVM_HostOperatingSystem.CreationClassName="IBMzVM_HostOperatingSystem", CSCreationClassName="IBMzVM_HostComputerSystem",CSName="VM1",Name="VM1" //Instance of IBMzVM_HostOperatingSystem instance of IBMzVM_HostOperatingSystem{...} where... represents a number of omitted lines in the form of <name> = <alue>. 9. Optional: Relocate the irtual appliance repository. The IBM z/vm Manageability Access Point Agent contains a repository of captured and imported irtual appliances. After you install the IBM z/vm Manageability Access Point Agent, the repository is located at /ar/opt/ibm/zmmap/repository/images on the Linux system in which the IBM z/vm Manageability Access Point Agent is installed. Attention: A repository in this default location is remoed when the agent is uninstalled. If you want the repository to remain after you uninstall the IBM z/vm Manageability Access Point Agent, or if you want the repository to exist in a different location (where more file system space is aailable, for example), you can relocate the repository. Use the following instructions to relocate the repository, either immediately after installation or at a later time. 78 IBM Systems Director VMControl: Installation and User's Guide

85 To relocate the irtual appliance repository, complete the following steps: a. Log on as root to the Linux system in which the IBM z/vm Manageability Access Point Agent is installed. b. Run the following commands to stop the Platform Agent serices. /etc/init.d/cimsererd stop /etc/init.d/tier1slpinst stop /etc/init.d/cimlistenerd stop /etc/init.d/ibmsa stop (Platform Agent x only) /etc/init.d/paslpd stop (Platform Agent only) c. Run the following command to change to the directory /ar/opt/ibm/zmmap/repository/images: cd /ar/opt/ibm/zmmap/repository/images d. If the directory is not empty, create a tar file containing its contents in the parent directory. Run the following command: tar -cf../images.tar * e. Run the following command to change to the directory /ar/opt/ibm/zmmap/repository: cd /ar/opt/ibm/zmmap/repository f. Run the following command to remoe the images directory: rm -rf images g. Run the following command to create an images directory that is a symbolic link to the desired location: ln -s repository_location images where repository_location is the desired location for the repository. h. If a tar file was created, change to the directory /ar/opt/ibm/zmmap/ repository/images. Run the following command: cd /ar/opt/ibm/zmmap/repository/images i. If a tar file was created, extract the contents of the tar file. Run the following command: tar -xf /ar/opt/ibm/zmmap/repository/images.tar j. If a tar file was created, remoe the tar file. k. Run the following commands to start the Platform Agent serices: /etc/init.d/ibmsa start (Platform Agent x only) /etc/init.d/paslpd start (Platform Agent only) /etc/init.d/cimlistenerd start /etc/init.d/tier1slpinst start /etc/init.d/cimsererd start Uninstalling IBM Systems Director VMControl You can uninstall IBM Systems Director VMControl from your enironment. To uninstall VMControl, follow these steps: Note: Due to an uninstallation limitation, if you hae installed a VMControl x update, you must use the unattended uninstallation procedure. 1. Choose from the following options: AIX or Linux Run the VMControl program uninstallation file: /opt/ibm/director/vmcontrolmanager/uninstall/uninstall.sh Chapter 2. IBM Systems Director VMControl V

86 Note: The preious command starts uninstallation in GUI mode. Ensure that you run this command in a graphics-enabled session. As an alternatie, you can use the command line to perform an unattended uninstallation of VMControl. Tip: To perform an unattended uninstallation, enter the following command:./uninstall -i silent Windows Use the Add or Remoe Programs function, or run the uninstall.exe file from C:\Program Files\IBM\Director\VMControlManager\uninstall to remoe VMControl. The uninstallation wizard starts. Tip: To perform an unattended uninstallation, enter the following command: uninstall.exe -i silent 2. Follow the steps in the uninstallation wizard to uninstall VMControl. Uninstalling IBM z/vm Manageability Access Point Agent You can use the mapuninstall command to uninstall the IBM z/vm Manageability Access Point Agent. Complete the following steps to uninstall either just IBM z/vm Manageability Access Point Agent or both IBM z/vm Manageability Access Point Agent and Platform Agent: CAUTION: If the repository of irtual appliances has not been relocated from the default location, the repository and its contents will be permanently deleted when the IBM z/vm Manageability Access Point Agent is uninstalled. If you want the repository to remain after you uninstall the IBM z/vm Manageability Access Point Agent, you can relocate the repository now. For more information about relocating the image repository, see the relocation step in "Install the IBM z/vm Manageability Access Point Agent." Uninstall IBM z/vm Manageability Access Point Agent but keep Platform Agent running: 1. Type the following command and press Enter: /opt/ibm/zmmap/bin/mapuninstall 2. When the uninstallation has completed successfully, you should see the following message: Remoal of zvmmap was successful Uninstall IBM z/vm Manageability Access Point Agent and Platform Agent together: 1. Open the /opt/ibm/director/bin/diruninstall script in an ASCII text editor. 2. Set the zvmmap ariable setting to Sae the modified diruninstall script. 4. Type the following command and press Enter: install_root/bin/diruninstall where install_root represents the root directory of your IBM Systems Director installation. 80 IBM Systems Director VMControl: Installation and User's Guide

87 Upgrading and migrating to IBM Systems Director VMControl You can upgrade and migrate from IBM Systems Director VMControl to VMControl by following the steps in this topic. To update IBM Systems Director VMControl to VMControl 2.3.1, see "Updating IBM Systems Director VMControl." To upgrade and migrate from VMControl ersion to VMControl ersion 2.3.1, begin by upgrading and migrating your IBM Systems Director management serer to Then upgrade and migrate the VMControl plug-in on your IBM Systems Director management serer to Last, and this step is optional in some cases, upgrade and migrate your VMControl agents and subagents. Details for each step follow. 1. Upgrade and migrate from IBM Systems Director management serer to V To use VMControl 2.3.1, your IBM Systems Director management serer must be at See "Installing, upgrading, and migrating IBM Systems Director." Note: After you upgrade and migrate to IBM Systems Director 6.2.1, you will not be able to access VMControl again until you complete step Upgrade and migrate your VMControl plug-in to To upgrade and migrate your VMControl plug-in to 2.3.1, follow the VMControl installation procedure. See "Installing and uninstalling IBM Systems Director VMControl." Note: If you hae a permanent license key for VMControl installed already, your license key is honored by VMControl and you can ignore the license key information in the VMControl installation topics. After upgrading and migrating VMControl, restart IBM Systems Director to iew the upgrade on the IBM Systems Director Welcome page. 3. Upgrade and migrate your VMControl agents and subagents: If you hae VMControl VMware Center 4.x subagents, you can continue using them as is, or upgrade and migrate them to the leel, minimally. If you want access to all VMControl capabilities, upgrading and migrating your VMControl Center 4.x subagents to the leel is required. To upgrade and migrate your VMControl Center 4.x subagents to the leel, uninstall your existing subagents using: lwiupdatemgr -uninstallfeature -featureid com.ibm.director.sm.c4x.agent -ersion 6.1.2, and follow the instructions in "Installing IBM Systems Director VMControl agents and subagents" to install the new ones. If you hae VMControl 2.2 NIM subagents, you can continue using them as is, or upgrade and migrate them to the or leel. If you want access to all VMControl capabilities, migrating your VMControl NIM subagents to the leel is required. To upgrade and migrate VMControl NIM subagents to 2.3.1, complete the following procedures. Note: To update VMControl NIM subagents to 2.3.1, see "Updating IBM Systems Director VMControl." Upgrade and migrate the Common Agent on the NIM master to the IBM Systems Director leel by first upgrading it to the leel using the IBM Systems Director Agent Installation wizard or install script, and then updating it to the leel by using Update Manager. See "Installing Common Agent and Upgrading the IBM Systems Director agents." Upgrade and migrate the VMControl NIM subagent to the leel by using the IBM Systems Director Agent Installation wizard to install the Chapter 2. IBM Systems Director VMControl V

88 VMControl NIM subagent, or by manually transferring the VMControl NIM subagent installation script to the NIM master and running it. See "Installing IBM Systems Director VMControl agents and subagents." If you hae IBM z/vm Manageability Access Point agents, you can continue using them as is, or upgrade and migrate them to the 6.2 leel, minimum. If you want access to all VMControl capabilities, upgrading and migrating your IBM z/vm Manageability Access Point agents to the leel is required. To upgrade and migrate your IBM z/vm Manageability Access Point agents to the leel, follow the instructions in "Installing the IBM z/vm Manageability Access Point Agent." Related tasks: Updating IBM Systems Director VMControl Related information: Installing IBM Systems Director VMControl Installing IBM Systems Director Installing IBM Systems Director VMControl agents and subagents Updating IBM Systems Director VMControl You can update IBM Systems Director VMControl to VMControl by following the steps in this topic. You can also update VMControl x itself with updates as they become aailable. To upgrade and migrate from VMControl to VMControl 2.3.1, see "Upgrading and Migrating to IBM Systems Director VMControl " To update VMControl itself with updates as they become aailable, rely on IBM Systems Director update manager. With IBM Systems Director update manager, you can acquire, install, and manage VMControl updates. Update manager also enables you to monitor your systems for needed updates by automatically checking for aailable product updates and identifying which systems need attention. To update VMControl to VMControl 2.3.1, begin by updating youribm Systems Director management serer to the Then update the VMControl plug-in on your IBM Systems Director management serer to Last, and this step is optional in some cases, update your VMControl agents and subagents. Details for each step follow. 1. Update your IBM Systems Director management serer to To use VMControl 2.3.1, your IBM Systems Director management serer must be at See "Updating IBM Systems Director." Note: After you update to IBM Systems Director 6.2.1, you will not be able to access VMControl again until you complete step Update your VMControl plug-in to To update your VMControl plug-in to 2.3.1, follow the VMControl installation procedure, or use IBM Systems Director update manager. See "Installing and uninstalling IBM Systems Director VMControl," or "Updating IBM Systems Director." Note: If you hae a permanent license key for VMControl installed already, your license key is honored by VMControl After installing updates for VMControl, restart IBM Systems Director to iew the updates on the IBM Systems Director Welcome page. 82 IBM Systems Director VMControl: Installation and User's Guide

89 3. Update your VMControl agents and subagents: To use VMControl 2.3.1, your VMControl agents and subagents must be at their or leels, minimally. The VMControl Common Repository subagent is the exception; it must be 'moed' to a Virtual I/O Serer (VIOS) system and be at the leel. To use all VMControl capabilities, your VMControl VMware Center 4.x subagents must be at the leel, your VMControl NIM subagents must be at the leel, your IBM z/vm Manageability Access Point Agents must be at the leel, and your Linux on Power images repositories must be 'moed' to VIOS systems and hae the VMControl Common Repository subagent. Note: To upgrade and migrate VMControl VMware Center 4.x subagents, upgrade and migrate VMControl NIM subagents to 2.3.1, and to upgrade and migrate IBM z/vm Manageability Access Point Agents to 6.2.1, see "Upgrading and migrating to IBM Systems Director VMControl " If you hae VMControl VMware Center 4.x subagents, you can continue using them as is, or update them to the leel. Updating your VMControl Center 4.x subagents to the leel is required if you want access to all VMControl capabilities. To update your VMControl Center 4.x subagents to the leel, uninstall your existing subagents using: lwiupdatemgr -uninstallfeature -featureid com.ibm.director.sm.c4x.agent -ersion 6.1.0, and follow the instructions in "Installing IBM Systems Director VMControl agents and subagents" to install the new ones. If you hae VMControl NIM subagents, you can continue using them as is, or update to the leel. Updating your VMControl NIM subagents to the leel is required if you want access to all VMControl capabilities. To update your VMControl NIM subagents to the leel, follow this procedure: Update the IBM Systems Director Common Agent on the NIM master to the IBM Systems Director leel by using Update Manager. See "Updating IBM Systems Director." Update the VMControl NIM subagent to the leel by using the IBM Systems Director Agent Installation wizard to install the VMControl NIM subagent, or by manually transferring the VMControl NIM subagent installation script to the NIM master and running it. See "Installing IBM Systems Director VMControl agents and subagents." If you hae IBM z/vm Manageability Access Point Agents, you can continue using them as is, or update to the leel. If you want access to all VMControl capabilities, updating your IBM z/vm Manageability Access Point Agents to the leel is required. To update your IBM z/vm Manageability Access Point Agents to the leel, follow the instructions in "Installing the IBM z/vm Manageability Access Point Agent." If you hae a VMControl Linux on Power image repository, updating to VMControl requires you to stop using the Linux system that has been your Linux on Power image repository, and begin using a VMControl image repository on VIOS instead. See "Requirements and support for AIX and Linux using storage copy serices (SCS)" for an oeriew, and follow this procedure: Choose a VIOS system in your enironment to use as your VMControl image repository for Linux or AIX on Power raw disk image irtual appliances. The VIOS system you choose must be running VIOS 2.1.2, 2.1.3, or 2.2 firmware with all the latest updates and patches. Further, it Chapter 2. IBM Systems Director VMControl V

90 must hae access to the LUNs storing the raw disk images of the irtual appliances that your VMControl Linux on Power image repository holds. Follow steps 1 through 4 in "Creating and discoering VIOS image repositories for AIX and Linux on Power Systems." When you finish these steps, your new VMControl image repository will be ready to use, and the Linux on Power irtual appliances that you preiously had are present in your new image repository. The Linux system that had been your VMControl Linux on Power image repository is no longer recognized by the VMControl plug-in as an image repository, and will not be used by VMControl any more. You can remoe it from IBM Systems Director, or start using it for some other purpose. Verify that the new VMControl image repository is aailable on the VIOS by completing the following steps: a. On the VMControl summary page, click the Virtual Appliances tab. b. Under Where to store:, click Image Repositories. c. In the Image Repositories (View Members) iew, check the Managed by: field to locate the VIOS that you chose to use for the new image repository. In the Name field, note that the name of the VIOS image repository is the same as the name of the VMControl Linux on Power image repository. For example, if your VMControl Linux on Power image repository was named VirtualSererLinux, then your new VIOS image repository will also be named VirtualSererLinux. You can optionally change the name of the VIOS image repository to reflect the VIOS on which the VMControl image repository resides. d. To change the name of the VIOS image repository, complete the following steps: 1) In the Image Repositories (View Members) iew, click the name of the new image repository. 2) On the General tab, click Edit. 3) On the Edit Properties page, edit the name of the image repository and click OK. 84 IBM Systems Director VMControl: Installation and User's Guide

91 Related concepts: Creating and discoering VIOS image repositories for AIX and Linux on Power Systems Related tasks: Upgrading and migrating to IBM Systems Director VMControl Installing and uninstalling IBM Systems Director VMControl Installing IBM Systems Director VMControl agents and subagents Installing the IBM z/vm Manageability Access Point Agent Related reference: Requirements and support for AIX and Linux using storage copy serices (SCS) Related information: Updating IBM Systems Director Downloading IBM Systems Director VMControl Installing IBM Systems Director VMControl Naigating and managing VMControl resources You can iew a summary of the resources managed by VMControl and the status of those irtual resources. You can also access common management tasks for managing your irtual resources. Information about this summary page is refreshed automatically when there are any changes. To iew the VMControl summary, follow these steps: 1. In the IBM Systems Director naigation area, click Welcome. 2. On the Welcome page, click Manage, scroll to the VMControl section, and click the VMControl section heading. The VMControl summary page is displayed. This page contains the following information: Resources The number of irtual appliances, workloads, and serer system pools currently defined for VMControl. Actie Status This table indicates the problem and compliance status for all systems that VMControl has discoered: Jobs This table indicates the status for all VMControl jobs: 3. View the Basics page. From this page, you can start the following tasks: Set up irtualization management Discoer irtual appliances Create image repository Import irtual appliance packages Capture a irtual serer or workload to create a irtual appliance Access Storage System Pools summary page Discoer TPM for Images serer Migrate serer from TPM for Images to VMControl Note: This task is only displayed after you discoer TPM for Images Serer. Chapter 2. IBM Systems Director VMControl V

92 On this page, you can also iew the License section. This section proides information about the VMControl licenses that are installed and the time left in the ealuation period for any ealuation licenses. From this section, you can start the following tasks: Install agents Purchase licenses Check for any aailable VMControl updates Launch the VMControl information center 4. Click the Workloads tab. This page displays the status for all workloads. From this page you can start the following tasks: Deploy a irtual appliance View actie and scheduled jobs Create a workload View workloads and members If you select a workload and click View Dashboard, you can iew additional information about the workload and perform additional workload management tasks. 5. Click the Virtual Appliances tab. This page displays the irtual appliances that you can deploy, the irtual serers, hosts, and systems into which you can deploy a irtual appliance, the workloads and irtual serers that you can capture, and the image repositories that are aailable for storing irtual appliances. From this page you can start the following tasks: Deploy a irtual appliance Capture a irtual serer or workload to create a irtual appliance Import a irtual appliance package View actie and scheduled jobs View irtual appliance ersions Create an image repository 6. Click the Serer System Pools tab. This page displays status for your serer system pools. From this page you can start the following tasks: View a health summary, monitors, and problems for your serer system pools Create a serer system pool View serer system pools and members View storage system pools and members If you select a serer system pool and click View Dashboard, you can iew additional information about the serer system pool and perform additional serer system pool management tasks. 7. Click the Virtual Serers/Hosts tab. This page displays status and details about your irtual serers and hosts. From this page, you can start the following tasks: View irtual serers and hosts Open the Performance Summary iew View and create irtual farms View and create relocation plans Relocate any or all irtual serers on a host 86 IBM Systems Director VMControl: Installation and User's Guide

93 Managing storage With VMControl, you can configure, manage, and monitor some aspects of the storage resources in your enironment. These storage resources might include fibre channel switches, storage subsystems, IBM BladeCenter storage, and storage system pools. VMControl allocates storage as needed when performing functions such as importing a irtual appliance package or capturing a irtual serer. Related reference: Supported SMI-S proiders on page 16 Storage system pools oeriew Storage system pools functionality is part of IBM Systems Director VMControl and enhances the base storage management function of IBM Systems Director by proiding the capability to group similar storage subsystems to create storage system pools. The Storage system pools summary page proides quick links to tasks and iews that are part of the base functions of IBM Systems Director, such as discoery and the Storage Management summary page. Storage system pools build on these base functions and proide the ability to group similar storage subsystems and automate placement within the storage system pool to simplify workload deployment operations. You can create storage system pools from storage that is managed by IBM Systems Director or storage that is managed by IBM Tioli Storage Productiity Center. IBM Tioli Storage Productiity Center and the IBM Systems Director Storage Control plug-in proide the additional capability of managing enterprise storage systems, such as the IBM System Storage DS8000, the IBM System Storage SAN Volume Controller, and the IBM Storwize V7000. Before you can start creating storage system pools, you must ensure that SMI-S proiders are in place to facilitate communication between IBM Systems Director and the storage deices, and that those storage deices are discoered and hae inentory collected. The following example describes the required components graphically. Chapter 2. IBM Systems Director VMControl V

94 IBM Systems Director and VMControl, which includes the Storage system pools summary page, is installed on the management serer The Hardware Management Console, the Power Systems that it manages, and the Virtual I/O Serer are discoered SMI-S proiders are installed or embedded in the storage deices (fibre channel switches and SAN storage) and then discoered Data is communicated between the VIOS and the SAN storage through the fibre channel switch, and optionally the SAN Volume Controller IBM Systems Director manages and communicates with the storage deices through the SMI-S proiders, the HMC, and optionally IBM Tioli Storage Productiity Center 88 IBM Systems Director VMControl: Installation and User's Guide

95 Note: IBM Systems Director and IBM Tioli Storage Productiity Center support different ersions of SMI-S proiders for DS3000, DS4000, and DS5000 storage deices. For more information, see "Supported SMI-S proiders." Additionally, all storage subsystems within a storage system pool must be part of the same actie zone configuration. Storage system pools require that you use World Wide Port Name (WWPN) zoning. After you discoer and collect inentory on storage resources, you can use the Storage system pools summary page, Storage System Pool Dashboard, and the storage system pool iews to manage and monitor your storage resources. Related concepts: Storage system pools Related tasks: Managing storage using IBM Systems Director VMControl and IBM Tioli Storage Productiity Center Related reference: Supported SMI-S proiders Related information: Managing and configuring storage IBM Systems Director Storage Control Discoering and collecting inentory for storage deices Managing storage using IBM Systems Director VMControl and IBM Tioli Storage Productiity Center IBM Systems Director VMControl enables you to use IBM Tioli Storage Productiity Center to manage your enterprise storage systems. IBM Systems Director VMControl uses the remote API capabilities of IBM Tioli Storage Productiity Center 4.1 (and later releases) to collect inentory on and proision your storage system, which creates seamless and integrated storage management. IBM Tioli Storage Productiity Center Basic Edition is required for certain types of storage subsystems, such as DS8000 and SAN Volume Controller. No other components of IBM Tioli Storage Productiity Center are required for storage management integration with VMControl. To use this capability, you must first install and configure an IBM Tioli Storage Productiity Center (TPC) serer for your storage system, which includes the storage controllers as well as their fibre channel switches. You hae options for discoering the TPC serer depending on the TPC serer configuration. To use TPC to proision storage such as DS3000, DS4000, and DS5000, ensure that you use a supported proider. For information about supported proiders, see "Supported SMI-S proiders" and "4.1.x - Supported Storage Products List." If you want IBM Systems Director VMControl to access all the storage controllers and fibre channel switches that TPC is managing without limiting the management to specific resources using a storage resource group (SRG), you can use basic system discoery. This method of system discoery requires that your TPC serer meets the following configuration requirements: TPC was installed using default alues. Chapter 2. IBM Systems Director VMControl V

96 The TPC DB2 administrator password matches the password of the TPC user ID. If the TPC serer meets the preious criteria, complete the following steps to discoer it. 1. On the IBM Systems Director welcome page, click Discoery Manager. 2. On the discoery manager summary page, click System discoery under Common tasks. 3. On the System Discoery page, complete the required fields and click Discoer. If you want IBM Systems Director VMControl to access only a specific group of resources, then create a storage resource group (SRG) in IBM Tioli Storage Productiity Center 4.1 for the resources that you want to use, including alid storage subsystems and fabrics configuration. If the switches are configured without the fabric, all of the zoning configuration information is unaailable in IBM Systems Director. After the storage resource group is created, use system discoery in IBM Systems Director to discoer the TPC serer. IBM Systems Director VMControl isolates its actiity on the TPC serer to just those resources in the identified storage resource group, which proides access control across these two software managers. You can discoer the IBM Tioli Storage Productiity Center serer with a customized storage resource group by creating a discoery profile, which captures the details about your IBM Tioli Storage Productiity Center serer. Note: It is recommended that only one discoery profile be created for a TPC serer and its associated storage resource group. If multiple profiles exist, only the first applied profile is used. If you want to change the SRG contents, use the TPC serer to edit and modify the storage resource group equipment membership. Then collect inentory for the farm to discoer the new equipment that you added to the SRG. 1. On the IBM Systems Director welcome page, click Discoery Manager. 2. On the discoery manager summary page, click System discoery under Common tasks. 3. On the System Discoery page, click Create new profile to launch the Discoery Profile wizard. 4. Complete the wizard using the following information: a. On the Profile Properties page, specify a name for the profile and select Farm for the System type and All for the System subtype. Click Next. b. On the Protocol Selection page, select Tioli Storage Productiity Center (TPC) Discoery. Click Next. c. On the next two pages, specify the configuration information for your TPC DB2 serer and TPC serer. d. On the Group Selection page, select the storage resource group that you want to be able to work with in IBM Systems Director VMControl e. Optional: On the Access Request page, select whether to proide credentials for unlocking the HTTP and Telnet Remote Serice Access Points (RSAPs) on the switch. Note: When using system discoery, switches are discoered and populated using four Remote Serice Access Points (RSAPs): SNMP, TPC, HTTP, and Telnet. 5This populates all necessary properties of the switch fabrics, such as zoning and port configuration, for IBM Systems Director. The HTTP and 90 IBM Systems Director VMControl: Installation and User's Guide

97 Telnet RSAPs are not configured as part of the discoery process. Therefore IBM Systems Director indicates Partial Access to the switch. This condition does not affect the function of IBM Systems Director VMControl and can be safely ignored. You can manually unlock the switch by proiding HTTP and Telnet credentials on this page. f. Reiew your selections on the summary page and click Finish to create the profile. When you complete the wizard, you can use the profile that you created to discoer and collect inentory on the set of storage resources that TPC is managing. This includes the storage subsystem information (storage controller, pool, olumes), as well as the fibre channel switch zone and zoneset information. Once these resources are discoered, you can use them in IBM Systems Director VMControl. To update the inentory of your storage and switch resources, collect inentory on the system you discoered using the profile you created. This system will hae a system type of Farm. Related reference: Supported SMI-S proiders Related information: Installing the IBM Tioli Storage Productiity Center family 4.1.x - Supported Storage Products List Working with storage resource groups Help to Find the Supported Products and Platforms Interoperability Matrix Links Changing the default time limit for inentory collection The default time limit on inentory collection is 25 minutes. If you hae a large IBM Tioli Storage Productiity Center enironment (more than approximately 8,000 SAN olumes), inentory collection in your enironment might exceed 25 minutes. This topic describes how to change the default discoery time limit. You can increase the default discoery time limit by updating the perf.extended.discoery.timeout property in one of the IBM Systems Director property files. The alue of this property is set in minutes. A time limit of 60 minutes is a recommended if you hae oer approximately 8,000 SAN olumes. If you hae oer 100,000 SAN olumes, then it is recommended the time limit be set to 100 minutes. To change the alue to 60 minutes permanently, do the following: 1. Edit the following file: C:\Program Files\IBM\Director\lwi\conf\oerrides\ USMIKernel.properties 2. If the perf.extended.discoery.timeout already exists, change its alue to 60. Otherwise, add the following line to the file: perf.extended.discoery.timeout= Restart the IBM Systems Director serer. Managing storage system pools A storage system pool enables you to group similar storage subsystems. With IBM Systems Director VMControl, you can create a storage system pool of selected Chapter 2. IBM Systems Director VMControl V

98 storage subsystems, add storage to the storage system pool, permanently delete a storage system pool, and edit a storage system pool policy. Naigating and managing storage system pool resources You can iew a summary of the storage resources managed by VMControl and the status of those resources. You can also access common management tasks for managing your storage resources. Information about this summary page is refreshed automatically when there are any changes. To iew the Storage system pools summary, follow these steps: 1. In the IBM Systems Director naigation area, click Welcome. 2. On the Welcome page, click Manage, scroll to the VMControl section, and click the Storage system pools link included below the VMControl section heading. The Storage system pools summary page is displayed. 3. View the Basics page. From this page, you can start the following tasks: Discoer storage systems Collect inentory for storage systems On this page, you can also iew the License section. This section proides information about the VMControl licenses that are installed and the time left in the ealuation period for any ealuation licenses. From this section, you can start the following tasks: Purchase licenses Check for any aailable VMControl updates Launch the VMControl information center 4. Click the Storage System Pools tab. This page displays the status for all storage system pools. From this page you can start the following tasks: View a health summary, monitors, and problems for your storage system pools Create a storage system pool View storage system pools and members If you select a storage system pool and click View Dashboard, you can iew additional information about the storage system pool. Storage system pool policy A storage system pool uses a storage system pool policy to determine how storage olumes are allocated within a storage system pool. The storage system pool policy allocates storage based on RAID leel and storage pool preference settings. By default, the policy settings are as follows: RAID leel RAID leel 5; Not required Storage pool preference No storage pool preference; Not required Required indicates that this setting must be satisfied when allocating storage. If no storage satisfies this requirement, the storage allocation fails. If Required is not selected, the policy attempts to allocate storage that satisfies this requirement. If no storage satisfies this requirement, other aailable storage is allocated. 92 IBM Systems Director VMControl: Installation and User's Guide

99 To edit the priority of the policy settings, as well as the default setting alues, select a storage pool and click Edit Storage Policy. Editing a storage system pool policy You can edit a storage system pool policy to specify how storage will be allocated within the pool. The storage system pool policy allocates storage based on RAID leel and storage pool preference settings. To edit the storage system pool policy, follow these steps: 1. From the IBM Systems Director VMControl summary page, click the Basics tab. 2. Click Storage system pools under Virtualization tasks. 3. From the Storage System Pools tab, select an existing storage system pool and click Edit Storage Policy. 4. Follow the instructions on the Edit Storage Policy panel to modify the storage system pool policy. For more information see the "Storage system pool policy" topic listed below. Related concepts: Storage system pool policy Creating storage system pools You can use the Create Storage System Pool wizard to create a storage system pool that is composed of one or more storage subsystems. Before creating a storage system pool, ensure that you hae discoered and collected inentory on your storage deices. To create a storage system pool, follow these steps: 1. From the IBM Systems Director VMControl summary page, click the Basics tab. 2. Click Storage system pools under Virtualization tasks. 3. From the Storage System Pools summary page, click the Storage System Pools tab and click Create. 4. Follow the instructions in the Create Storage System Pool wizard to create a storage system pool that is composed of selected storage subsystems. Related information: Discoering and collecting inentory for storage deices mkstsyspool command Adding storage to storage system pools You can use the Add Storage wizard to add one or more storage systems to an existing storage system pool. Before adding storage subsystems to a storage system pool, ensure that you hae discoered and collected inentory on your storage deices. To add storage subsystems to a storage system pool, follow these steps: 1. From the IBM Systems Director VMControl summary page, click the Basics tab. 2. Click Storage system pools under Virtualization tasks. 3. From the Storage System Pools summary page, click the Storage System Pools tab. 4. Select an existing storage system pool and click Add Storage. Chapter 2. IBM Systems Director VMControl V

100 Managing irtual serers 5. Follow the instructions in the Add Storage wizard to add one or more storage systems to the storage system pool. The Add Storage wizard filters the storage systems that you can select to add to the storage system pool. Only storage systems that are compatible with the existing storage system pool are displayed. Tip: If a storage subsystem you want to add to the storage system pool is not aailable to add, check your switch zoning to erify that the storage subsystem you want to add is in the same zone as the aailable storage subsystems. Related information: Discoering and collecting inentory for storage deices addsttopool command Deleting a storage system pool If you no longer require a storage system pool, you can delete it. If you perform this task, the storage system pool cannot be rediscoered. Instead, the storage system pool must be re-created. Deleting a storage system pool does not delete the storage systems comprising the storage pool. Storage systems that are members of the storage system pool continue to exist but are no longer grouped. To permanently delete a storage system pool, complete the following steps: 1. From the IBM Systems Director VMControl summary page, click the Basics tab. 2. Click Storage system pools under Virtualization tasks. 3. In the Storage System Pools iew, select the storage pool you want to delete and select Delete. 4. Follow the instructions to delete the storage system pool. Related information: rmstsyspool command With IBM Systems Director VMControl, you can create, edit, delete, and relocate irtual serers from one host to another. In addition, you can group multiple irtual serers into a workload for aggregated monitoring. Creating a irtual serer You can use the Create Virtual Serer wizard to create a new irtual serer on a host. 1. In the IBM Systems Director naigation pane, click Resource Explorer to locate the host. 2. Select the host, click Actions from the menu bar, and click System Configuration > Create Virtual Serer. 3. Complete the instructions in the Create Virtual Serer wizard to set up a irtual serer. 4. In the Scheduler window, click OK to run the task immediately. You also can schedule to run this task at a later time. 94 IBM Systems Director VMControl: Installation and User's Guide

101 Related tasks: Creating a irtual serer Grouping irtual serers to create a workload Editing a irtual serer After you use IBM Systems Director VMControl to create or deploy a irtual serer, you can use IBM Systems Director to edit the irtual serer. For more information, see "Editing irtual serers" in the IBM Systems Director topic collection. Related tasks: Editing irtual serers Permanently deleting a irtual serer You can permanently delete a irtual serer from its associated host. For more information, see "Deleting a irtual serer permanently" in the IBM Systems Director topic collection. Related tasks: Deleting a irtual serer permanently Relocating irtual serers IBM Systems Director VMControl can relocate irtual serers in response to predicted hardware failures related to processors, memory subsystems, power source, or storage. You might also choose to relocate irtual serers for planned maintenance or downtime or to adjust resources to improe performance. Depending on the irtualization enironment that you are using and on the plug-ins you choose to install, you hae different options for relocating irtual serers. The following table shows the options for relocating irtual serers for each irtualization enironment. Relocation support Virtualization enironment IBM Power Systems that are under the control of the Hardware Management Console or the Integrated Virtualization Manager Microsoft Virtual Serer VMware Center with VMware ESX hosts or VMware ESXi hosts Static relocation in IBM Systems Director irtual farms Lie relocation in IBM Systems Director irtual farms Lie relocation in VMControl serer system pools Yes Yes Yes Yes No No No Yes No Chapter 2. IBM Systems Director VMControl V

102 VMware VirtualCenter with VMware ESX hosts or VMware ESXi hosts VMware ESX that is not being managed by VMware Center Windows Serer 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled Relocation support No Yes No Yes No No No No No Xen Yes Yes No z/vm No No No With static relocation, if the irtual serer is powered on, the relocation operation powers off the irtual serer at the beginning of the relocation process and powers the irtual serer on when the relocation is complete. With lie relocation, if the irtual serer is powered on, the relocation occurs without powering the serer off. IBM Systems Director proides lie relocation for irtual serers within irtual farms. IBM Systems Director VMControl proide lie relocation for irtual serers within serer system pools. The following table shows the differences in lie relocation support between IBM Systems Director and VMControl. Relocation features Relocate all irtual serers in a host Relocate one irtual serer at a time Relocate multiple irtual serers at the same time Automatic placement (VMControl determines the target irtual serer or host) Adisory placement (User can approe the relocation before it can occur) Virtual farm relocation IBM Systems Director Yes Yes No No 1 No Relocation type System pool relocation VMControl Relocate all irtual serers No Yes on predicted failure Relocation plans Yes No Fixed target (User determines the target irtual serer or host) Yes No Relocation automation Yes Yes 1. Except for VMware VirtualCenter 2.x and later. 96 IBM Systems Director VMControl: Installation and User's Guide Yes Yes Yes Yes Yes

103 With VMControl, you can choose from three options for relocation: You can manually relocate irtual serers at any time. You can actiate a resilience policy on your workload to relocate irtual serers automatically to preent predicted hardware failures from affecting the aailability of the workload. You can create an automation plan to relocate the irtual serers when certain eents occur. Related information: Relocating irtual serers Relocate Serer system pools in VMControl are like irtual farms in IBM Systems Director. Both are a logical grouping of like hosts that can contain multiple hosts and their associated irtual serers. Depending on the irtualization enironment that you hae and on the plug-ins you choose to install, IBM Systems Director proides either static relocation or lie relocation. With static relocation, if the irtual serer is powered on, the relocation operation powers off the irtual serer at the beginning of the relocation process and powers the irtual serer on when the relocation is complete. With lie relocation, if the irtual serer is powered on, the relocation occurs without powering the serer off. VMControl proides lie relocation. With VMControl, you can choose from three options for relocation: You can manually relocate irtual serers at any time. You can actiate a resilience policy on your workload to relocate irtual serers automatically to preent predicted hardware failures from affecting the aailability of the workload. You can create an automation plan to relocate the irtual serers when certain eents occur. Manual relocation You can choose to relocate one or more irtual serers from an existing host at any time. When you relocate irtual serers within IBM Systems Director irtual farms, you choose the relocation target. Howeer, when you relocate irtual serers within VMControl serer system pools, the relocation target is automatically identified. Policy-based relocation You can actiate a resilience policy on your workload. Then, VMControl can detect a predicted hardware failure problem related to processors, memory subsystems, power source, or storage and relocate irtual serers to another host in the serer system pool. If the policy is in Adise mode, which is the default, you must approe any resilience policy-based actions, including relocations, before they are performed. You are notified that a policy-based action requires approal through the problem status for the serer system pool. You can approe, delete, or ignore the proposed action. If you want VMControl to perform proposed policy-based actions without approal, you can edit the workload settings to perform policy-based actions without approal. Chapter 2. IBM Systems Director VMControl V

104 You might want to be notified by when a policy-based action requires your approal. In this case, you can set up the appropriate threshold and create an automation plan that sends you an when approal is required. Then, you can go to the Problems iew to find out more information about the proposed action. Automatic relocation VMControl serer system pools can predict hardware failure problems and relocate irtual serers to maintain resilience. Howeer, you might also want to monitor and adjust resources within your serer system pool. For example, you might want to monitor the hosts in your serer system pool for high CPU utilization. To do this, you can actiate a threshold to monitor high and low alues for CPU utilization in your workloads. Then, if the threshold is crossed, a message is displayed in the Serer system pools dashboard, and in the Problems iew. You can also create an automation plan to automatically relocate the irtual serers in your serer system pool when problems are detected or thresholds are crossed. For example, if you actiate a threshold for high CPU utilization, you can also create an automation plan that is triggered to relocate a irtual serer that is running at critical CPU utilization to a host that has adequate resources. By creating your own automation plans, you can choose from a larger selection of monitors and eent actions that help you maintain the health and resilience of your workloads. Relocating irtual serers manually You can choose to relocate one or more irtual serers from an existing host to another host in the serer system pool. IBM Systems Director VMControl chooses the target host from similarly configured hosts in the serer system pool and displays the proposed relocation actions. You can then accept or cancel the relocation operation. To relocate one or more irtual serers, follow these steps: 1. To relocate a single irtual serer, from the IBM Systems Director VMControl irtual serers iew, right-click the irtual serer that you want to relocate and select Relocate. To relocate all irtual serers from a host, right-click the host and select Relocate Virtual Serers. 2. Follow the instructions in the Relocate window. Related information: mcrelocate command Relocating irtual serers using the resilience policy You can actiate the resilience policy on a workload running in your serer system pool. The resilience policy enables IBM Systems Director VMControl to relocate irtual serers automatically to maintain the resilience (high aailability) of your workloads. When the resilience policy is actiated, IBM Systems Director VMControl can automatically relocate irtual serers when a predicted hardware failure is detected. VMControl moes irtual serers away from a failing host system, and relocates them to a host that the serer system pool determines has adequate resources. 98 IBM Systems Director VMControl: Installation and User's Guide

105 With VMControl you can initiate the resilience policy when you edit a workload. There are no additional steps required to set up or actiate the resilience policy. By default, you are asked to approe any policy-based action, such as relocation, before it is performed. To iew the proposed action, you can go to the Serer system pools dashboard or the Problems iew. To access the Problems iew, go to the IBM Systems Director naigation area, and click System Status and Health > Problems. From the Problems iew, you can approe, delete, or ignore the proposed action. You might want to be notified by when a policy-based action requires your approal. In this case, you can create an automation plan that sends you an when your approal is required. For more information about setting up notifications, see "Setting up notification when policy-based actions need approal." If you want to allow VMControl to perform the proposed action without your approal, you can edit the workload. Setting up notification when policy-based actions need approal: Use this topic to create an automation plan that notifies you by when a policy-based action requires your approal. When a policy-based action such as relocation requires your approal, you can iew the problem through the problem status for your serer system pool. Howeer, if you want to receie an to alert you that a policy-based action requires your approal, you can create an automation plan. Creating an automation plan includes selecting an eent that triggers an eent action. To create an automation plan for sending an notification (the eent action) when policy-based actions require your approal (the eent), follow these steps: 1. In the IBM Systems Director naigation pane, expand Automation and click Eent Automation Plans. 2. On the Eent Automation Plans page, click Create. 3. In the Eent Automation Plan wizard, the Welcome page is displayed. Click Next. 4. On the Name and description page, type a descriptie name for the eent automation plan that you are creating. For example, type Notification Plan. Optionally, you also can type a description of the plan. Click Next. 5. On the Targets page, select one or more system pools. The eent automation plan monitors these serer system pools for specific generated eents. Select the systems in the Aailable list and click Add to moe them to the Selected list. Click Next. 6. On the Eents page, select Common from the Eents list. 7. In the list of eent types, select Eent seerity, and select Fatal and Critical from the list of seerity leels. These selections ensure that any fatal or critical eent results in an being sent to you. Optionally, you can also create an eent filter by completing the following steps: a. In the naigation area, expand System Status and Health and click Eent Log. b. Select an Approal Required eent from the eent log, click Create Filter, and complete the information for the new eent filter. Chapter 2. IBM Systems Director VMControl V

106 After the eent filter is created, go back to the Eents page, select Adanced Eent Filters from the Eents list, and select the filter you created. This ensures that you receie an only when that type of eent occurs. 8. Click Next. 9. On the Eents actions page, click Create. 10. In the Create Actions window, select Send an (Internet SMTP) to create an eent action and click OK. 11. Type the information into the new eent action and click OK. 12. If the eent action that you selected includes the Test button, you can determine whether your settings are correct by clicking Test. 13. Click OK to sae the eent action. The automation plan is now created. Related information: Monitoring system status and health Managing thresholds Automating tasks Relocating irtual serers automatically IBM Systems Director VMControl serer system pools can detect predicted hardware failure problems related to processors, memory subsystems, power source, or storage and balance resources in the serer system pool to correct the problem. Once the problem is detected, the serer system pool can automatically relocate your irtual serers. Howeer, your serer system pool might encounter other types of problems for which you want to monitor, so that relocation or resource adjustments can occur for those problems, as well. For example, you might want to monitor the hosts in your serer system pool for high CPU utilization. In this case, you could actiate a threshold for each host, based on the CPU Utilization % irtualization monitor, and hae it create a critical eent when a certain utilization is reached. You can create an automation plan to relocate the irtual serers from the host with a critical eent (i.e. hardware problem, high CPU utilization) to a host that the serer system pool determines has adequate resources. By creating your own automation plan, you can choose from arious monitors and eent actions that can help you maintain the health and resilience of your workloads. Creating an automation plan includes selecting an eent that triggers an eent action. The following instructions proide an example of how to set up your enironment to relocate irtual serers automatically. Use this example as a guide in actiating thresholds and creating your own automation plan for relocation. For more comprehensie information, see the following topics: "Monitoring system status and health," "Managing thresholds," and "Automating tasks." To set up your enironment to relocate irtual serers automatically, follow these steps: 1. Actiate a threshold on a monitor, such as one of the irtualization monitors. For more information, see "Creating a threshold" and "Virtualization manager monitors." 2. Create an automation plan for relocating irtual serers (the eent action) when specified thresholds are exceeded (the eent), by completing the following steps: 100 IBM Systems Director VMControl: Installation and User's Guide

107 a. In the IBM Systems Director naigation pane, expand Automation and click Eent Automation Plans. b. On the Eent Automation Plans page, click Create. c. In the Eent Automation Plan wizard, the Welcome page is displayed. Click Next. d. On the Name and description page, type a descriptie name for the eent automation plan that you are creating. Optionally, you also can type a description of the plan. Click Next. e. On the Targets page, select one or more hosts that are members of the serer system pool. These hosts are the systems that the eent automation plan monitors for specific generated eents. Select the systems in the Aailable list and click Add to moe them to the Selected list. Click Next. f. On the Eents page, select Common from the Eents list. g. In the list of eent types, select Eent seerity, and select Fatal and Critical from the list of seerity leels. These selections ensure that predicted hardware failures that are fatal or critical trigger the automation plan. h. Click Next. i. On the Eents actions page, click Create. j. In the Create Actions window, select Start a program on the management serer to create an eent action and click OK. k. Type the name of the directory where the smcli commands are located on the management serer. For example, /opt/ibm/director/bin. l. Type smcli mcrelocate -E true -n system for the name of the program file, where system is the name of the system that would generate the eent and is the source of relocation. m. If the eent action that you selected includes the Test button, you can determine whether your settings are correct by clicking Test. n. Click OK to sae the eent action. The automation plan is now created. Related information: Monitoring system status and health Managing thresholds Automating tasks Creating a threshold Virtualization monitors Managing power operations on irtual serers IBM Systems Director VMControl supports power operations that you can perform on irtual serers. For more information, see "Managing power operations on irtual serers" in the IBM Systems Director topic collection. Chapter 2. IBM Systems Director VMControl V

108 Managing irtual appliances and workloads A workload is a deployed irtual appliance that allows you to monitor and manage one or more irtual serers as a single entity. With IBM Systems Director VMControl Standard Edition, you can capture, import, and deploy irtual appliances. Workloads are created by deploying irtual appliances or by grouping existing irtual serers as a workload. The first step in managing irtual appliances and workloads is creating an image repository. Related information: Commands Creating and discoering image repositories This topic proides information about how to set up your enironment for IBM Systems Director VMControl. The following pieces must exist in your VMControl enironment before you can use IBM Systems Director VMControl Standard Edition or IBM Systems Director VMControl Enterprise Edition to import irtual appliance packages, capture irtual serers, and deploy irtual appliances. Image repositories - Virtual appliances are stored in image repositories that you create. Agents - For VMControl to be able to see the images in your repositories, you must install agents on the repository systems. These agents are specific to your irtualization enironment (NIM-based Power Systems, SCS-based Power Systems,, or z/vm). Discoery - VMControl discoers your image repositories and the irtual appliances they store. For more information, refer to the VMControl requirements for your specific enironment. Creating and discoering image repositories for AIX and Linux on Power Systems This topic proides information about how to set up your AIX and Linux on Power Systems enironment for IBM Systems Director VMControl. 102 IBM Systems Director VMControl: Installation and User's Guide

109 For AIX, you hae two options: NIM image repositories and VIOS image repositories. You can set up your AIX enironment with either type or with both types. For Linux on Power Systems, you would set up one or more VIOS image repositories. Creating and discoering NIM image repositories for AIX: This topic proides information about how to set up an IBM Systems Director VMControl image repository for irtual appliances containing AIX mksysb and lpp_source images. There are seeral pieces to your VMControl enironment that must be in place for you to use the VMControl Standard Edition or VMControl Enterprise Edition portion of the product. These pieces are shown in the following image: Note: The images shown in the image repository are not created automatically when a new repository is created. Images must be imported or captured after completing the following steps. Follow these steps to get your enironment ready for VMControl Standard Edition or VMControl Enterprise Edition: 1. Ensure that you hae at least one NIM master in your enironment that can sere as your image repository. For information about the requirements for using a NIM master as an image repository in VMControl, as well as the instructions for preparing and configuring the NIM master, see "Preparing to install IBM Systems Director VMControl subagent for NIM." 2. Ensure that the appropriate VMControl subagent software is installed on the system that hosts your image repository. For information, see "Installing IBM Systems Director VMControl irtualization manager subagents using the installation wizard" or "Installing IBM Systems Director VMControl irtualization manager subagents manually." 3. From the VMControl summary page, go to the Basics page and click Discoer irtual appliances to discoer your repositories and irtual appliances. Virtual appliances already present in your repositories, that hae been imported or captured using VMControl, are detected by VMControl. Chapter 2. IBM Systems Director VMControl V

110 Additional irtual appliances can be added to your repositories by using the Capture and Import tasks in VMControl. For more information, see "Capturing a workload or irtual serer to create a irtual appliance" and "Importing a irtual appliance package." Related information: Discoering systems and collecting inentory data Preparing to install IBM Systems Director VMControl subagent for NIM Installing IBM Systems Director VMControl irtualization manager subagents using the installation wizard Installing IBM Systems Director VMControl irtualization manager subagents manually Network Installation Management Configuring the NIM master and creating basic installation resources Capturing a workload or irtual serer to create a irtual appliance Importing a irtual appliance package Creating and discoering VIOS image repositories for AIX and Linux on Power Systems: This topic proides information about how to set up a Virtual I/O Serer (VIOS) image repository for irtual appliances containing AIX or Linux on Power Systems raw images. There are seeral pieces to your VMControl enironment that must be in place for you to use the VMControl Standard Edition or VMControl Enterprise Edition portion of the product. These pieces are shown in the following image: Follow these steps to get your enironment ready for VMControl Standard Edition or VMControl Enterprise Edition: 1. Ensure that you hae set up a SAN storage pool and a Virtual I/O Serer (VIOS) that has access to this storage pool. These actions are performed outside of IBM Systems Director. 104 IBM Systems Director VMControl: Installation and User's Guide

111 In addition, you must ensure that the IBM Systems Director Common Agent is started on the VIOS, and that it will start wheneer the VIOS is rebooted. For information, see "Installing Common Agent on VIOS and IVM" on the IBM Systems Director Best Practices Wiki. 2. Discoer and request access to the storage and the operating system of the VIOS mentioned in Step Ensure that the appropriate VMControl Common Repository subagent software is installed on the VIOS that hosts your image repository. For information, see "Installing IBM Systems Director VMControl subagents using the installation wizard" or "Installing IBM Systems Director VMControl subagents manually." 4. Run full inentory collection on the operating system of the VIOS to gather information about the image repository subagent. 5. Create an image repository. From the VMControl summary page, go to the Virtual Appliances tab and click Create image repository. Follow the instructions in the Create Image Repository wizard. IBM Systems Director automatically discoers the image repository after it is created. You can add irtual appliances to your repositories by using the Capture and Import tasks in VMControl. The metadata associated with the irtual appliance will be stored in the image repository, and the image will be stored in the storage pool. For more information, see "Capturing a workload or irtual serer to create a irtual appliance" and "Importing a irtual appliance package." Related tasks: Updating IBM Systems Director VMControl on page 82 Discoering systems and collecting inentory data Installing IBM Systems Director VMControl irtualization manager subagents using the installation wizard Installing IBM Systems Director VMControl irtualization manager subagents manually Capturing a workload or irtual serer to create a irtual appliance Importing a irtual appliance package Related information: IBM Systems Director Best Practices Wiki Creating and discoering image repositories for z/vm This topic proides information about how to set up your z/vm enironment for IBM Systems Director VMControl. There are seeral pieces to your VMControl enironment that must be in place for you to use the VMControl Standard Edition or VMControl Standard Edition or VMControl Enterprise Edition portion of the product. These pieces are shown in the following image: Chapter 2. IBM Systems Director VMControl V

112 Note: The images shown in the image repository are not created automatically when a new repository is created. Images must be imported or captured after completing the following steps. Follow these steps to get your enironment ready for VMControl Standard Edition or VMControl Enterprise Edition: 1. Ensure that the appropriate VMControl agent software is installed on the system that will host your image repository. Refer to "Installing the z/vm manageability access point agent" to install the agent software. 2. Ensure that you hae at least one image repository that is suitable for the irtual appliances that you plan to deploy. You might hae created an image repository when you installed the z/vm manageability access point agent. If you do not hae an image repository, then you must create one. See the following section for details. 3. Click Discoer Virtual Appliances... to discoer your repositories and irtual appliances. Images already present in your repositories are detected by VMControl and are aailable to deploy as irtual appliances. Additional irtual appliances can be added to your repositories by using the Import and Capture tasks in VMControl. Creating an image repository for z/vm To create an image repository for z/vm, you need to install the z/vm manageability access point agent. During the installation process, ensure that a sufficient amount of disk space is proided for the image repository. When proiding disk space for the image repository, consider the size and number of the images that you plan to create. The location of the image repository can be a symbolic link so that the repository is not remoed when the z/vm manageability access point agent is remoed. For more information, see "Installing z/vm manageability access point agent." 106 IBM Systems Director VMControl: Installation and User's Guide

113 Related information: Installing z/vm manageability access point agents Discoering systems and collecting inentory data Deleting image repositories You can delete an image repository from your irtualization enironment. Deleting the image repository also deletes the irtual appliances in the repository. Note: Only an image repository in a storage copy serices (SCS)-based irtualization enironment can be deleted in this way. Use smcli commands to delete image repositories from other irtualization enironments. To delete an image repository, follow these steps: 1. In the Image Repositories iew, right click the image repository that you want to delete and select Delete Repository... If there are irtual appliances in the image repository, the resulting Delete Image Repository dialog displays a list of those irtual appliances that will be deleted if you delete this image repository. 2. Click OK to permanently delete the image repository and the irtual appliances in it. Getting started with irtual appliances and workloads Once you create your image repositories and discoer the images within them, you can start working with irtual appliances and workloads in your enironment. You can capture a ariety of sources to create irtual appliances, import irtual appliance packages, and deploy irtual appliances within your enironment. Importing a irtual appliance package You can use the Import wizard to import a irtual appliance package from the Internet or from other sources and store its component files to create a irtual appliance. You can then deploy the irtual appliance into your data center. The Import wizard can import irtual appliance packages containing the following irtual serer images: AIX mksysb images for IBM POWER logical partitions Linux on Power Systems raw disk images for IBM POWER logical partitions AIX raw disk images for IBM POWER logical partitions Linux on System z images for z/vm To import a irtual appliance package, follow these steps: 1. From the Basics or Virtual Appliances tab of the IBM Systems Director VMControl Summary page, click Import. 2. Follow the instructions in the Import wizard to import a irtual appliance package. You must specify a.of or.oa file. For information, see the "Import" topic. 3. In the Scheduler window, click OK to import the irtual appliance package immediately. You can also schedule this task for a later time. Chapter 2. IBM Systems Director VMControl V

114 Related reference: OVF specifications for IBM Systems Director VMControl Related information: Import: importa command A irtual appliance package is an industry-standard representation of a irtual serer that contains a configured, tested operating system and middleware and software applications, along with the metadata that describes the irtual serer. The Import task enables you to import a irtual appliance package, storing the irtual appliance it contains in IBM Systems Director VMControl Standard Edition or IBM Systems Director VMControl Enterprise Edition. You can then deploy the VMControl irtual appliance into your data center. The following diagram shows how a irtual appliance package can be imported to create a new irtual appliance. 1. A user selects a irtual appliance package, irtual appliance package A, to import. The irtual appliance package can reside either on your IBM Systems Director Serer or on a Web serer that is accessible to your IBM Systems Director Serer. 2. Importing irtual appliance package A results in a irtual appliance, irtual appliance A, stored by VMControl. 3. Virtual appliance A contains the metadata that describes the irtual serer, and a reference to Image A. Image A contains a fully configured and tested operating system and software applications for the irtual serer and is stored in a VMControl image repository. 4. After Virtual appliance A is imported, you can use VMControl to deploy Virtual appliance A one or more times into your enironment. 108 IBM Systems Director VMControl: Installation and User's Guide

115 IBM Systems Director VMControl can import irtual appliance packages that use the Distributed Management Task Force (DMTF) Open Virtualization Format (OVF), which is a platform independent and open packaging and distribution format for irtual appliances. For more information about OVF, see the Open Virtualization Format Specification aailable from the DMTF Web site at: The irtual appliance package can be in one of the following formats: A set of files (called set-of-file format) A single tar file containing the same set of files, typically with a.oa extension. You can import a irtual appliance package if the irtual appliance package is accessible from the system on which the IBM Systems Director Serer is running or can be accessed by using a URI. The following name and URI formats are supported: [relatiepath]file (any IBM Systems Director Serer) (any IBM Systems Director Serer) /localpath/file (IBM Systems Director Serer on AIX and Linux only) file:///localpath/file (IBM Systems Director Serer on AIX and Linux only) c:\localpath/file (IBM Systems Director Serer on Windows only) \\computername\path (IBM Systems Director Serer on Windows only) Chapter 2. IBM Systems Director VMControl V

116 file://c:/localpath/file (IBM Systems Director Serer on Windows only) where file must be a.of or.oa file. For more information, see "Import support and requirements" for your irtualization enironment. Related reference: OVF specifications for IBM Systems Director VMControl Related information: importa command NIM-based Power Systems import support and requirements SCS-based Power irtualization import support and requirements z/vm import requirements Capturing a source to create a irtual appliance You can capture from a ariety of sources to create a irtual appliance. You can then deploy the resulting irtual appliance to create a new irtual serer that is complete with a fully functional operating system and software applications. You can create a irtual appliance by capturing any of the following sources: irtual serer workload AIX mksysb image file AIX mksysb resource AIX lpp_source resource AIX lpp_source directory Capture: The Capture task enables you to capture from a ariety of sources to create a irtual appliance. You can then deploy the irtual appliance to create a new irtual serer that is complete with a fully functional operating system and software applications. The following diagram shows how a irtual serer or workload is captured to create a new irtual appliance. 1. A user selects a irtual serer or a workload that contains a single irtual serer to capture, irtual serer A. 2. Capturing irtual serer A results in a irtual appliance, irtual appliance A, stored by VMControl. 3. Virtual appliance A is composed of metadata that describes the irtual serer, and a reference to Image A. Image A contains the full operating system and software applications and is stored in a VMControl image repository. 4. After Virtual appliance A is captured, you can use VMControl to deploy Virtual appliance A one or more times into your enironment. 110 IBM Systems Director VMControl: Installation and User's Guide

117 You can create a irtual appliance by capturing any of the following sources: irtual serer workload AIX mksysb image file AIX mksysb NIM resource AIX lpp_source NIM resource AIX lpp_source directory For more information, see "Capture support and requirements" for your irtualization enironment. Related information: capturea command NIM-based Power Systems import support and requirements SCS-based Power irtualization capture support and requirements z/vm capture requirements Capturing a irtual serer or workload to create a irtual appliance: Use the Capture wizard to capture a irtual serer or a workload that contains a single irtual serer to create a new irtual appliance. Note: You can also use the Systems Management command-line interface (smcli) capturea command to capture a irtual serer or workload. To capture a irtual serer or a workload using the Capture wizard, follow these steps: Chapter 2. IBM Systems Director VMControl V