You are on page 1of 150



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



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

ii IBM Systems Director VMControl: Installation and User’s Guide .

. . 4 problems . . 76 VMControl . . . . . . . . . . . . . . Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About this publication . 5 Capture or deploy of virtual server hangs . 88 in error state . . . . . 41 z/VM minidisk size is -1 when deploying . 79 Installing IBM Systems Director VMControl Deploy task fails with error DNZIMN107E . 57 guest LAN results in error . . . . . . . . . . . 12 Deploy image to new virtual server fails with Hardware and software requirements. . . . . . . 73 Hardware and software requirements . . . . . . . . . . . . . . . .Contents Chapter 1. 45 Unable to edit virtual server properties related to Capture . . . . . . . . . . . . 72 Planning for IBM Systems Director VMControl . . . . . . . . 70 Chapter 2. . . 2009 iii . 80 Point Agent . . 47 virtual CPU . . . 50 Virtual server processors are not marked Importing a virtual appliance package . 86 Capturing a virtual server to create a virtual Unable to set virtual processor to dedicated with appliance . . . . . . . 69 How to send your comments . . . . . . . . . . . . 57 edit virtual server . . . . . 86 Deploying a virtual appliance or empty virtual Editing virtual server to add virtual switch or server . . . 85 Deploy . . . . . . . . . . . . . 85 Capturing an existing mksysb image file to create Unexpected minidisk change attempted when a virtual appliance . . . . . . . . . . . . . 1 supported . . . . . . . . . 78 Installing IBM Systems Director VMControl . 68 Chapter 3. . . . . 1 Access state is Unknown for z/VM virtual servers Who should read this book . . . 138 © Copyright IBM Corp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Task fails after copying a scheduled job . 19 Multiple deploy tasks cause DNZIMN871E error 80 Installing the IBM z/VM Manageability Access Product panel of Deploy wizard is blank . . . . . . . . . . . . . . . . . . . 58 DNZIMN868E . . . . . . . . 58 Deploy to a NIM Master fails with error Managing virtual appliances. . 75 requirements . . . . . . . . . . . 5 Capture task fails with error DNZIMN018E . . . . . . . . . . 69 Import from a network shared volume fails . . . 84 Import . . . . . . . . . 75 IBM Systems Director VMControl Capture Red Hat Enterprise Linux server fails to boot requirements . . . . . . . . . . . 2009. . . . 1 after restarting IBM Systems Director Server . 67 Subagent for NIM installation fails when installing manually . . . . . 41 incorrect hostname . . .1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 subagent for NIM . 13 error DNZVMP001E . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Minidisks page . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Conventions and terminology . . . . 88 IBM Systems Director VMControl installer results IBM Systems Director VMControl commands . . . . 83 Updating IBM Systems Director VMControl . . . . . . . . . . . . . 87 processes behind . . . . . . 6 protocol . . . 86 Managing z/VM virtual servers . . . . 74 IBM Systems Director VMControl Import Capture from file fails when using HTTP requirements . . . . 55 editing virtual server . . . . . . . . . . . . . . IBM Systems Director Capture task fails with error DNZIMN018E or DNZIMN861E . . . . . . . . . . . . . . . . . . . . . . 22 Deploy to existing virtual server task times out 81 Uninstalling IBM Systems Director VMControl 40 Deploy to new AIX virtual server task times out 83 Uninstalling IBM z/VM Manageability Access Deploy wizard displays error DNZIMC763E on Point Agent . . 7 after deploy and shows permission errors for IBM Systems Director VMControl Deploy shared libraries . . . 1 Multiple NIM master image repositories not Publications and related information . . . . . . . . . . . . . . . . . . . . . . . 3 LVM volume group. 9 Deploy virtual server failures leaves resources Installing and uninstalling IBM Systems Director allocated . 137 Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Reference . . . . . . . . . . 87 Troubleshooting and support . . . . . . . . . . . . . 4 Capture task fails and indicates SSH connection License information . 71 Accessibility features . . . 70 VMControl V2. . . . . . . . 112 Installation wizard . . 66 OVF specifications for IBM Systems Director Subagent for NIM installation fails using Agent VMControl . . . . . . . . . . . 3 Capture task fails and indicates failure to access Overview of IBM Systems Director VMControl . . . . . . 84 Managing workloads in your virtual environment 41 Deploy task creates new virtual server with Creating and discovering image repositories . . . . . . . . . 54 dedicated . 66 Image repositories remain after IBM Systems IBM Systems Director VMControl installer leaves Director VMControl agents are uninstalled . . . . . 14 Deploy task fails with error DNZIMN867E . . . . . .

. . . . .Index . 141 iv IBM Systems Director VMControl: Installation and User’s Guide . . . . . . . . . .

and deploy virtual appliances in the data center. import. and a reference section that contains IBM Systems Director VMControl-specific requirements for Open Virtualization Format (OVF) virtual appliance packages. To view a PDF file. or advice. you need Adobe Acrobat Reader. v IBM Systems Director VMControl Web site www.com/products/acrobat/readstep. there is additional information related to IBM Systems Director VMControl. An attention notice appears before the instruction or situation in which damage can occur. Who should read this book This book is for system administrators and operators using the IBM Systems Director VMControl plug-in for IBM Systems Director to capture. In addition to this documentation.html Find information for installing and using IBM Systems Director VMControl. About this publication This publication provides instructions for installing and using IBM® Systems Director VMControl and IBM Systems Director VMControl Image Manager. This documentation describes how to use the Web interface as well as the command-line interface (smcli) to complete tasks. Attention: These notices indicate possible damage to programs.ibm.ibm. 2009. import. and deploy virtual appliances in your environment. Publications and related information You can view the same IBM Systems Director VMControl content that resides in the Information Center in a PDF document.com/infocenter/director/v6r1x/topic/vim_210/ fsd0_vim_main.com/systems/management/director/plugins/imagemg/ See an overview of IBM Systems Director VMControl and links to download the product.adobe. You can also find troubleshooting information. Conventions and terminology These notices are designed to highlight key information: Note: These notices provide important tips.Chapter 1. With IBM Systems Director VMControl Image Manager you can capture.boulder. 2009 1 . IBM Systems Director VMControl resources on the World Wide Web v IBM Systems Director VMControl information center http://publib. which can be downloaded for free from the Adobe Web site at www.html. devices. Important: These notices provide information or advice that might help you avoid inconvenient or difficult situations. or data. guidance. v Windows® Systems Director Web site © Copyright IBM Corp.

boulder.ibm.com/systems/management/director/ Get overview information.com/infocenter/director/v6r1x/index.ibm. demos. go to the IBM Systems Director information center Web site at http://publib. www. How to send your comments Your feedback is important in helping to provide the most accurate and highest quality information. 2 IBM Systems Director VMControl: Installation and User’s Guide . If you have any comments about this book or any other IBM Systems Director publication. There you will find the feedback page where you can enter and submit comments.ibm.jsp. v IBM Systems and servers: Technical support page www.com/systems/support/ Locate support for IBM hardware and systems-management software. as well as its plug-ins. and downloads for the IBM Systems Director product.

v Edit z/VM virtual servers.Chapter 2. v Capture a running virtual server that is configured just the way you want. IBM Systems Director VMControl V2. The licensed portion of IBM Systems Director VMControl. IBM Systems Director VMControl Image Manager supports deploying virtual appliances to the following platforms: v IBM® Power Systems™ servers (POWER5™ and POWER6™) that are managed by Hardware Management Console or Integrated Virtualization Manager v Linux® on System z® systems running on the z/VM® hypervisor IBM Systems Director VMControl enables you to complete the following tasks: v Create z/VM virtual servers. When you capture the virtual server.1 IBM Systems Director VMControl is designed to simplify the management of workloads in your IT environment. standards-based images into your repositories as virtual appliances. You are granted a 60-day evaluation license for IBM Systems Director VMControl Image Manager when you download and install IBM Systems Director VMControl. For more information. see the License Information topic. running applications. allows you to complete the following tasks. v Discover existing image repositories in your environment and import external. and virtual server definition. 2009 3 . Once you are up and running. Use IBM Systems Director VMControl and IBM Systems Director VMControl Image Manager to manage workloads across multiple hardware platforms and virtualization environments from one location. discovering or creating image repositories. The IBM Systems Director VMControl Summary page guides you through the tasks you need to complete to get started using the product: installing agents. v Deploy virtual appliances quickly to create new virtual servers that meet the demands of your ever-changing business needs. IBM Systems Director VMControl in conjunction with IBM Systems Director VMControl Image Manager is a cross-platform solution that assists you in rapidly deploying virtual appliances to create virtual servers that are configured with the operating system and software applications that you desire. v Manage z/VM virtual servers. Overview of IBM Systems Director VMControl This section provides an overview of IBM Systems Director VMControl and IBM Systems Director VMControl Image Manager. IBM Systems Director VMControl Image Manager. After the virtual appliance packages are imported. you can deploy them within your data center. a virtual appliance is created in one of your image repositories with the same definitions and can be deployed multiple times in your environment. and capturing or importing virtual appliances. complete with guest operating system. the Summary page gives you quick © Copyright IBM Corp. v Import virtual appliance packages that exist in the Open Virtualization Format (OVF) from the Internet or other external sources. including accessibility and license information. 2009.

as well as information about obtaining a license. Once the evaluation license expires. IBM Systems Director VMControl includes a no-charge (free) function and an optional chargeable (fee-based) function. import. For more information. to use information technology products successfully. The 60-day evaluation period begins the first time you begin using IBM Systems Director VMControl Image Manager. access to the main tasks and views that you can utilize in IBM Systems Director VMControl. including the details of which components are no-charge (free) and which components are chargeable (for-fee). any image repositories and virtual appliances that you created during the evaluation period will still be usable. and deploy virtual appliances in your environment. v Image Repositories – view all of the discovered image repositories in your environment. see the Accessibility features for IBM Systems Director topic. The day the evaluation license expires is also displayed. The IBM Systems Director VMControl plug-in for IBM Systems Director supports the accessibility features that are supported in IBM Systems Director. you will no longer be able to create. When you have started using the tasks available in IBM Systems Director VMControl. Related reference IBM Systems Director Downloads Accessibility features This topic provides information about the accessibility features of IBM Systems Director VMControl. you are granted a 60-day evaluation license for IBM Systems Director VMControl Image Manager. The no-charge portion of the product enables you to create and manage virtual servers for z/VM. The Summary page also helps you manage your license for IBM Systems Director VMControl Image Manager. However. If you allow the evaluation license to expire before purchasing a license for IBM Systems Director VMControl Image Manager. The evaluation license enables you to create. and begin using IBM Systems Director VMControl. import. 4 IBM Systems Director VMControl: Installation and User’s Guide . Accessibility features help users who have a disability. install. such as restricted mobility or limited vision. v Deployment History – view all of the virtual servers that have been created from a specific virtual appliance. When you download. you can use the following views to manage your image repositories and virtual appliances: v Virtual Appliances – view all of your virtual appliances and select them for deployment. You can also perform management tasks on the virtual servers from within this view. The number of days left on the evaluation license appears on the bottom of the IBM Systems Director VMControl summary page. when you do purchase and install the license for IBM Systems Director VMControl Image Manager. you must purchase a license in order to continue using IBM Systems Director VMControl Image Manager. and deploy virtual appliances in your environment. License information This topic describes the licensing for IBM Systems Director VMControl.

1. IBM Systems Director VMControl Image Manager will function just as it did during the evaluation period. Related reference IBM Systems Director Downloads IBM Systems Director VMControl Image Manager Web page Planning for IBM Systems Director VMControl Before installing or updating IBM Systems Director VMControl.1. Supported operating systems IBM Systems Director VMControl is supported on all operating systems that are supported by IBM Systems Director Server 6. For specific versions of these operating systems supported by IBM Systems Director Server.1.1.2. or deploy virtual appliances.1. see Hardware and software requirements for IBM Systems Director. For detailed information about the hardware and software requirements for IBM Systems Director. Supported virtualization software The following virtualization software is supported for IBM Systems Director VMControl: v Hardware Management Console Version 7. review the hardware and software requirements.2.1.2 software. capture virtual servers.3..1. IBM Systems Director VMControl V2.4. see Operating systems supported by IBM Systems Director 6. Before using IBM Systems Director VMControl Image Manager to import virtual appliance packages. PTF MH01181 Chapter 2. see Supported IBM systems and products.1. Once you install the license. This topic describes hardware and software requirements that are unique to IBM Systems Director VMControl. For detailed information on the systems supported by IBM Systems Director Server. The IBM Systems Director VMControl Image Manager license is packaged on a CD-ROM with authorization key and install program.1 5 . Related tasks “Installing IBM Systems Director VMControl” on page 14 “Installing IBM Systems Director VMControl subagent for NIM” on page 19 Installing z/VM manageability access point agents Hardware and software requirements IBM Systems Director VMControl is installed on systems running IBM Systems Director Server 6. Supported IBM® systems IBM Systems Director VMControl is supported on all IBM® systems that are supported by IBM Systems Director Server 6. review the requirements for each of those tasks.2.

Note: For System z systems.rpm packet.1. Related tasks “Installing IBM Systems Director VMControl subagent for NIM” on page 19 Installing z/VM manageability access point agents IBM Systems Director VMControl Import requirements This topic describes requirements for importing a virtual appliance package and storing its component files to create a virtual appliance. xlibs must be installed in 64-bit mode.5 file from the compat-libstdc++-33-3.1. In addition.2. v Integrated Virtualization Manager Version 2.1 (or earlier). you need to uninstall the agent and install the version of the IBM z/VM Manageability Access Point Agent that is supported by IBM Systems Director 6. You can obtain the libstdc++.so. use the Red Hat installation disks to install the shared library.1.1. Note: It is recommended that you always apply the latest available service pack.3-61.1. You can import virtual appliance packages containing the following virtual server images: v AIX® mksysb images for IBM POWER® logical partitions v Linux on System z images for z/VM Requirements for import You can import a virtual appliance package if the virtual appliance package is accessible from the system on which the IBM Systems Director Server is running or can be accessed by using a URI.1.4 are installed: – UM32505 – UM32503 – UM32521 – UM32522 – UM32693 – UM32765 Additional prerequisites v Ensure that you have the appropriate x11 libraries installed on your system.0. For example. ensure that you have installed a supported version of Linux on the z/VM system where you plan to install the IBM z/VM Manageability Access Point Agent.10 Note: It is recommended that you always apply the latest available service pack.4 Note: Ensure that the following PTFs for z/VM 5.s390x.2. For more information.3. The minimum service pack prerequisite is listed here. v z/VM 5.1. v If you are running the IBM z/VM Manageability Access Point Agent that is supported by IBM Systems Director 6. if you are running Red Hat Enterprise Linux 5. These libraries are needed for IBM Systems Director VMControl installation. The following name and URI formats are supported: 6 IBM Systems Director VMControl: Installation and User’s Guide . see Operating systems supported by IBM Systems Director 6.

1 7 . v The image repository is discovered in IBM Systems Director. z/VM requirements for import You can import a virtual appliance package when the following requirements are met: v The IBM z/VM Manageability Access Point Agent is installed on the System z host system where you want to store the imported virtual appliance package. multiple NIM Master image repositories are not supported. v [relativepath]file (any IBM Systems Director Server) v /localpath/file (IBM Systems Director Server on AIX and Linux only) v c:\localpath/file (IBM Systems Director Server on Windows only) v \\computername\path (IBM Systems Director Server on Windows only) v file://localpath/file (IBM Systems Director Server on AIX and Linux only) v file://c/localpath/file (IBM Systems Director Server on Windows only) v http://path/file (any IBM Systems Director Server) Power Systems requirements for import You can import a virtual appliance package when the following requirements are met: v A NIM master is running and is accessible by your IBM Systems Director Server. v The virtual appliance package that you want to import was created for z/VM by IBM Systems Director VMControl Capture or Import tasks. IBM Systems Director VMControl V2. v There is sufficient space in the image repository to store the image associated with the virtual appliance package that you want to import.1 v z/VM virtual servers (z/VM guests) running Linux on System z You can capture an existing mksysb image file from the following locations: Chapter 2. Note: IBM Systems Director VMControl can recognize just one NIM master as an image repository. Related concepts “Import” on page 45 Related tasks “Importing a virtual appliance package” on page 54 Related reference “OVF specifications for IBM Systems Director VMControl” on page 112 IBM Systems Director VMControl Capture requirements This topic describes requirements for capturing a virtual server or an AIX makesysb image file to create a virtual appliance. v IBM Systems Director VMControl has recognized the NIM master as an image repository in the environment. v There is sufficient space on the NIM master under /export/nim/appliances to store the AIX mksysb image file associated with the virtual appliance package that you want to import.3 or AIX 6. You can capture these types of virtual servers: v IBM Power Systems (POWER5 and POWER 6) virtual servers (logical partitions) running AIX 5.

v The System z host system (the server on which IBM z/VM Manageability Access Point Agent runs) has been discovered with IBM Systems Director. v Your IBM Systems Director Server v Your IBM Systems Director VMControl NIM master v A Microsoft® Windows server that is sharing the file (if your IBM Systems Director Server is a Windows system) v A Web server Note: You cannot capture an image from a secure Web server. v The virtual server is up and running AIX version 5. The discovery of the IBM z/VM Manageability Access Point Agent causes the System z host to be discovered. v The virtual server has at least one virtual Ethernet adapter. Collection of inventory is performed against the IBM z/VM Manageability Access Point Agent. Access status is listed as OK. Access status is listed as OK. multiple NIM Master image repositories are not supported. v IBM Systems Director VMControl has recognized the NIM master as an image repository in the environment. v The virtual server that you want to capture and the operating system running on it is discovered in IBM Systems Director. and inventory has been collected. v There is sufficient space on the NIM master under /export/nim/appliances to store the captured virtual server. Power Systems requirements for capture You can capture a Power Systems virtual server to create a virtual appliance in the following environments: v A virtual server (logical partition) on a Power Systems server that is managed by Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM) v A virtual server on a Power Architecture® BladeCenter® server that is managed by IVM You can capture a Power Systems virtual server when the following prerequisites are met: v A NIM master is running and able to access the virtual server over the network. or the only partition on the host to which all host resources are dedicated. Note: IBM Systems Director VMControl can recognize just one NIM master as an image repository.1. v The virtual server is not a full system partition.3 or AIX version 6. Access status is listed as OK. 8 IBM Systems Director VMControl: Installation and User’s Guide . and inventory is collected. z/VM requirements for capture The following prerequisites must be met to capture a z/VM virtual server: v An IBM z/VM Manageability Access Point Agent has been installed on a virtual machine that runs in the same z/VM host as the target of the capture. Access status is listed as OK. v The virtual server has been discovered with IBM Systems Director. v The Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM) that manages the virtual server is discovered in IBM Systems Director.

rpm v The disk partitions must be configured appropriately and must include a file system in /etc/fstab.s390x. Similarly.2.1.42-1.s390x. v The virtual server allows remote root logins. Related tasks “Capturing an existing mksysb image file to create a virtual appliance” on page 55 “Capturing a virtual server to create a virtual appliance” on page 57 IBM Systems Director VMControl Deploy requirements This topic describes requirements for deploying a virtual appliance. Specifically.fc6.rpm – perl-HTML-Parser-3.10-2.1. v The virtual server is running. You can deploy virtual appliances that have been captured or imported into IBM Systems Director VMControl to the following platforms: v IBM® Power Systems servers (POWER5 and POWER6) that are managed by Hardware Management Console or Integrated Virtualization Manager v Linux on System z systems running on the z/VM hypervisor Power Systems server requirements for deploy You can deploy a virtual appliance to create or overwrite a virtual server in the following environments: v A virtual server (logical partition) on a Power Systems server that is managed by Hardware Management Console or Integrated Virtualization Manager v A virtual server on a Power Architecture BladeCenter server that is managed by IVM Chapter 2.55-1. when a disk partition is using any one of the following configurations. v The z/VM manageability access point is able to establish an SSH connection to the virtual server using the IP address used by the IBM Systems Director Server to access the target system. Subsequent requests for capturing a virtual server are queued for processing.fc6.noarch.rpm – perl-libwww-perl-5.35-3.1 9 .1.noarch.s390x. v The following RPMs are installed on the virtual server: – perl-Compress-Zlib-1. IBM Systems Director VMControl captures one z/VM virtual server at a time.34-6.noarch.2. volume group names or volume UUIDs on the z/VM manageability access point.rpm – perl-XML-Parser-2.rpm – perl-HTML-Tagset-3. IBM Systems Director VMControl V2.1.rpm – perl-URI-1. 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 volume used by a volume group containing a volume listed in /etc/fstab Note: You cannot capture a virtual server with an LVM system that has volume group names or logical volume UUIDs that match.805-1. and therefore conflict with.1. you cannot capture a virtual server that has been cloned from the z/VM manageability access point.1.

or relocate tasks concurrently for the same AIX virtual server. If the virtual server has an operating system installed. You can deploy a virtual appliance to an existing virtual server when the following prerequisites are met: v The HMC or IVM that manages the target virtual server is discovered in IBM Systems Director. v The NIM Master is able to access the target virtual server and the HMC or IVM that manages it over the network. – Local storage that is allocated from a storage pool hosted by the Virtual I/O Server. See the Supported storage devices topic for a list of supported storage devices. Either define the hostname on the name server. v A supported storage configuration is available and discovered in IBM Systems Director: – SAN-based storage that is allocated from a storage pool hosted by the Virtual I/O Server. capture. and any firewalls must be preconfigured to allow the virtual server to connect to the NIM Master. and inventory is collected for the HMC or IVM. it will be overwritten when the virtual appliance is deployed. or add it to /etc/hosts on the NIM Master. v IBM Systems Director VMControl has recognized the NIM master as an image repository in the environment. v A NIM Master has network access to the HMC or IVM that will manage the new virtual server. v A NIM Master is running and is accessible by your IBM Systems Director Server. multiple NIM Master image repositories are not supported. Note: You cannot perform the deploy. Note: IBM Systems Director VMControl can recognize just one NIM master as an image repository. multiple NIM Master image repositories are not supported. v The hostname for the primary and secondary network interfaces of the virtual server where you want to deploy the virtual appliance can be resolved from the NIM Master. Access status is listed as OK. Note: IBM Systems Director VMControl can recognize just one NIM master as an image repository. and inventory is collected for the HMC or IVM. v The NIM Master is running and is accessible by your IBM Systems Director Server. v The virtual server that you plan to create must have network access to the NIM Master. You can deploy a virtual appliance to a new virtual server when the following prerequisites are met: v The Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM) that will manage the new virtual server is discovered in IBM Systems Director. v The virtual server is not a full system partition. 10 IBM Systems Director VMControl: Installation and User’s Guide . v IBM Systems Director VMControl has recognized the NIM master as an image repository in the environment. or the only partition on the host to which all host resources are dedicated. Access status is listed as OK. Wait until one of these tasks is complete before beginning another.

for example: – Available network interfaces exist for use by the virtual server. and inventory is collected. the following prerequisites must be met: v The IBM z/VM Manageability Access Point Agent is installed on the z/VM host where the deployment is to occur. the directory manager supporting the z/VM system must be configured to allocate minidisk volumes with the Auto-Group option. Access status is listed as OK. v A supported storage configuration is available and discovered in IBM Systems Director: – SAN-based storage that is allocated from a storage pool hosted by the Virtual I/O Server. v The virtual server that is the target of the deployment is powered off.1 11 . IBM Systems Director VMControl V2. System z and z/VM requirements for deploy On a System z host system that is running the z/VM hypervisor. v Resources required for the image exist on the z/VM system. Subsequent requests for deployment are queued for processing. v The IBM z/VM Manageability Access Point Agent on the System z host system is discovered in IBM Systems Director. See the Supported storage devices topic for a list of supported storage devices. You can also deploy a virtual appliance to a new or existing virtual server. IBM Systems Director VMControl deploys one z/VM virtual server or virtual appliance at a time. Either define the hostname on the name server. you can deploy an empty virtual server to create a virtual server that does not include a virtual appliance. the directory manager supporting the z/VM system must be configured to allocate minidisk volumes with the Auto-Group option. You can deploy a virtual appliance to create a virtual server when the additional prerequisites are met: v The IBM z/VM Manageability Access Point Agent contains a repository with images. v Inventory of the images in the repository has completed. You can deploy or create an empty virtual server when the following additional prerequisite is met: v If you plan to deploy a virtual server that uses minidisks for storage. – If minidisks are required for virtual server storage.v The hostname for the primary and secondary network interfaces of the virtual server where you want to deploy the virtual appliance can be resolved from the NIM Master. – Local storage that is allocated from a storage pool hosted by the Virtual I/O Server. For any z/VM deployment. You can deploy a virtual appliance to an existing virtual server when the following additional prerequisites are met: Chapter 2. or add it to /etc/hosts on the NIM Master. – Available volumes exist for use by the virtual server.

You cannot deploy a virtual appliance to z/VM service machines with the following user IDs. v The IBM z/VM Manageability Access Point Agent contains a repository with images. 12 IBM Systems Director VMControl: Installation and User’s Guide . z/VM service machines that are restricted from the deploy task z/VM service machines restricted from deploy task v $ALLOC$ v BLDRACF v VSMPROXY v GSKADMIN v X25IPI v $DIRECT$ v BLDSEG v VSMREQIN v IMAP v 5VMRAC40 v $SYSCKP$ v CMS1 v VSMREQIU v IMAPAUTH v RACFSMF v $SYSWRM$ v CMSBATCH v VSMSERVE v LDAPSRV v RACFVM v $PAGE$ v DISKACNT v VSMWORK1 v LPSERVE v RACMAINT v $SPOOL$ v EREP v VSMWORK2 v MPROUTE v AUTOLOG2 v $TDISK$ v LGLOPR v VSMWORK3 v NAMESRV v IBMUSER v ROOT v MIGMAINT v ZVMMAPLX v NDBPMGR v SYSADMIN v DAEMON v MONWRITE v 4OSASF40 v NDBSRV01 v 5684042J v BIN v OP1 v OSADMIN1 v PORTMAP v 5VMRSC40 v SYS v OPERATNS v OSADMIN2 v REXECD v RSCS v ADM v OPERATOR v OSADMIN3 v RXAGENT1 v RSCSAUTH v NOBODY v OPERSYMP v OSAMAINT v SMTP v RSCSDNS v DEFAULT v SYSDUMP1 v OSASF v SNALNKA v XCHANGE v MAINT v SYSMAINT v 5VMTCP40 v SNMPD v 5VMDIR40 v AVSVM v SYSMON v TCPIP v SNMPQE v DATAMOVE v TSAFVM v VMRMADMN v TCPMAINT v SNMPSUBA v DIRMAINT v GCS v VMRMSVM v ADMSERV v SSLSERV v DIRMSAT v GCSXA v VMSERVR v DHCPD v TFTPD v 5VMPTK40 v AUDITOR v VMSERVS v DTCVSW1 v UFTD v PERFSVM v AUTOLOG1 v VMSERVU v DTCVSW2 v VMKERB v 5VMHCD40 v BLDCMS v VMUTIL v FTPSERVE v VMNFS v CBDIODSP v BLDNUC Related concepts “Deploy” on page 50 Related tasks “Deploying a virtual appliance or empty virtual server” on page 57 Installing and uninstalling IBM Systems Director VMControl You can install IBM Systems Director VMControl and the agents necessary to use IBM Systems Director VMControl Image Manager. v Inventory is collected for the images in the repository. as described in the table: Table 1. the operating system will be overwritten. Note: If you are deploying to an existing virtual server. You can also uninstall IBM Systems Director VMControl. v A virtual server that meets the criteria specified in the image exists and has been discovered.

2. Supported IBM® systems IBM Systems Director VMControl is supported on all IBM® systems that are supported by IBM Systems Director Server 6.4.1 13 . PTF MH01181 Note: It is recommended that you always apply the latest available service pack. v z/VM 5. This topic describes hardware and software requirements that are unique to IBM Systems Director VMControl.1.1. see Operating systems supported by IBM Systems Director 6.10 Note: It is recommended that you always apply the latest available service pack.Hardware and software requirements IBM Systems Director VMControl is installed on systems running IBM Systems Director Server 6. v Integrated Virtualization Manager Version 2. Chapter 2.0. see Hardware and software requirements for IBM Systems Director. Supported operating systems IBM Systems Director VMControl is supported on all operating systems that are supported by IBM Systems Director Server 6. For example. use the Red Hat installation disks to install the shared library. IBM Systems Director VMControl V2.2.1. The minimum service pack prerequisite is listed here.3. see Supported IBM systems and products. For specific versions of these operating systems supported by IBM Systems Director Server.3.1.2. These libraries are needed for IBM Systems Director VMControl installation.4 are installed: – UM32505 – UM32503 – UM32521 – UM32522 – UM32693 – UM32765 Additional prerequisites v Ensure that you have the appropriate x11 libraries installed on your system.1.1.4 Note: Ensure that the following PTFs for z/VM 5..1.1. For detailed information about the hardware and software requirements for IBM Systems Director. Supported virtualization software The following virtualization software is supported for IBM Systems Director VMControl: v Hardware Management Console Version 7.2 software.1. if you are running Red Hat Enterprise Linux 5. For detailed information on the systems supported by IBM Systems Director Server.

1. To check SELinux status. follow these steps: 1. SELinux must be disabled before installing IBM Systems Director VMControl. Log on the system and enter this command to check SELinux status: sestatus. Related reference “Planning for IBM Systems Director VMControl” on page 5 Installing IBM Systems Director VMControl evaluation license You can use the installation program to install the evaluation license for IBM Systems Director VMControl.1. xlibs must be installed in 64-bit mode. v Make sure that the target system satisfies all IBM Systems Director VMControl-specific prerequisites.s390x. Related tasks “Installing IBM Systems Director VMControl subagent for NIM” on page 19 Installing z/VM manageability access point agents Installing IBM Systems Director VMControl You can install IBM Systems Director VMControl by using either the installation program or by using a response file to perform an unattended installation.2. If SELinux is not disabled. For more information. you can continue using the no-charge function of IBM Systems Director VMControl and you can purchase a license to continue using IBM Systems Director VMControl Image Manager. Enter this command: #vi /etc/selinux/config 2.3-61.2.1.1.1. see Operating systems supported by IBM Systems Director 6. you need to uninstall the agent and install the version of the IBM z/VM Manageability Access Point Agent that is supported by IBM Systems Director 6. Before installing IBM Systems Director VMControl.1.1. In addition. SELinux status should be disabled. Tip: You can temporarily disable SELinux by entering the following command: /usr/sbin/setenforce 0 v Download the IBM Systems Director VMControl installation program as follows: 14 IBM Systems Director VMControl: Installation and User’s Guide . v On Red Hat Enterprise Linux.rpm packet. Disable SELinux by specifying SELINUX=disabled. Note: For System z systems.5 file from the compat-libstdc++-33-3. Either method installs both the no-charge function of IBM Systems Director VMControl and a 60–day evaluation license for IBM Systems Director VMControl Image Manager. Enter this command to reboot the system: #reboot 4. perform the following tasks: v Make sure that you have installed IBM Systems Director version 6. This installation gives you access to the no-charge function of IBM Systems Director VMControl and a 60–day evaluation license for IBM Systems Director VMControl Image Manager.1 (or earlier). enter the following command: sestatus.1. For information. see Hardware and software requirements for IBM Systems Director. ensure that you have installed a supported version of Linux on the z/VM system where you plan to install the IBM z/VM Manageability Access Point Agent. v If you are running the IBM z/VM Manageability Access Point Agent that is supported by IBM Systems Director 6.1.so. You can obtain the libstdc++. When the evaluation license expires. 3.

Follow the instructions in the installation wizard to install IBM Systems Director VMControl. 3. IBM Systems Director VMControl is displayed in the IBM Systems Director Welcome page. 3.sh Linux for xSeries Systems_Director_VMControl_2_1_Linux_x86. When the installation is complete.gz Windows SysDir_VMControl_2_1_Windows. To install IBM Systems Director VMControl evaluation license. Change to the directory in which the installation file is located.zip 4. Be sure that you copy the correct package based on the operating system that is running on the IBM Systems Director Server. enter the following command: For AIX or Linux: gzip -cd <package_name> | tar -xvf - where <package_name> is the file name of the installation package.gz ® Linux for zSeries SysDir_VMControl_2_1_Linux_System_z. Launch the IBM Systems Director VMControl program installation file. To unzip and extract the contents of the installation package. Chapter 2. follow these steps: 1. For Windows: unzip <package_name> where <package_name> is the file name of the installation package.tar.tar.tar.sh Windows Systems_Director_VMControl_2_1_Windows. you can use the command line to perform an unattended installation of IBM Systems Director VMControl. Copy the downloaded installation package to a local drive on each IBM Systems Director Server on which you want to install IBM Systems Director VMControl. Note: If you want to use the installation wizard to install on AIX and Linux. 1. you must launch the installation program in a graphics-enabled session. 5.exe This launches the installation wizard and displays the Welcome page. As an alternative.com/systems/management/director/plugins/actengmgr/ 2. IBM Systems Director VMControl V2. Operating system Installation file name AIX Systems_Director_VMControl_2_1_AIX.gz ® Linux for pSeries SysDir_VMControl_2_1_Linux_Power.gz ® Linux for xSeries SysDir_VMControl_2_1_Linux_x86.ibm.1 15 . 2.sh Linux for zSeries Systems_Director_VMControl_2_1_Linux_System_z.sh Linux for pSeries Systems_Director_VMControl_2_1_Linux_Power. Go to the IBM Systems Director Downloads Web Site at the following address: http://www.tar. Click Download for the IBM Systems Director VMControl plug-in. Select the package to download: Operating system Download package AIX SysDir_VMControl_2_1_AIX.

enter the following command: For AIX or Linux: gzip -cd <package_name> | tar -xvf - where <package_name> is the file name of the installation package.gz Linux for zSeries SysDir_VMControl_2_1_Linux_System_z-full. 3.gz Windows SysDir_VMControl_2_1_Windows-full. follow these steps: 1. enter the following command: sestatus.com/systems/management/director/plugins/actengmgr/ 2. Go to the IBM Systems Director Downloads Web Site at the following address: http://www. The IBM Systems Director VMControl evaluation license must be installed before you can install the permanent license key for IBM Systems Director VMControl. 5. If SELinux is not disabled.tar.zip 4. For Windows: unzip <package_name> where <package_name> is the file name of the installation package.gz Linux for pSeries SysDir_VMControl_2_1_Linux_Power-full. Enter this command: #vi /etc/selinux/config 2. Enter this command to reboot the system: #reboot 4.tar. SELinux must be disabled before installing IBM Systems Director VMControl. you can purchase a license to continue using IBM Systems Director VMControl Image Manager. Log on the system and enter this command to check SELinux status: sestatus. To unzip and extract the contents of the installation package. 16 IBM Systems Director VMControl: Installation and User’s Guide . If you purchase the license for IBM Systems Director VMControl Image Manager. Click Download for the IBM Systems Director VMControl plug-in. Disable SELinux by specifying SELINUX=disabled. Be sure that you copy the correct package based on the operating system that is running on the IBM Systems Director Server.tar. 3. You can continue to use the no-charge function of IBM Systems Director VMControl. Tip: You can temporarily disable SELinux by entering the following command: /usr/sbin/setenforce 0 Download the IBM Systems Director VMControl installation program as follows: 1.tar. Select the package to download: Operating system Download package AIX SysDir_VMControl_2_1_AIX-full.gz Linux for xSeries SysDir_VMControl_2_1_Linux_x86-full.ibm. To check SELinux status. Copy the downloaded installation package to a local drive on each IBM Systems Director Server on which you want to install IBM Systems Director VMControl. On Red Hat Enterprise Linux. SELinux status should be disabled. you must install the permanent license key to continue using IBM Systems Director VMControl Image Manager. Installing IBM Systems Director VMControl permanent license key When the 60-day evaluation license for IBM Systems Director VMControl expires.

sh Linux for pSeries Systems_Director_VMControl_2_1_Linux_Power-full. SELinux must be disabled before installing IBM Systems Director VMControl. SELinux status should be disabled. 2. Performing an unattended installation of IBM Systems Director VMControl You can use a response file to perform an unattended installation of IBM Systems Director VMControl. Click Download for the IBM Systems Director VMControl plug-in. To start the installation.1. follow these steps: 1.ibm. 3.sh Windows Systems_Director_VMControl_2_1_Windows-full.com/systems/management/director/plugins/actengmgr/ 2.sh Linux for zSeries Systems_Director_VMControl_2_1_Linux_System_z-full.1 17 . This installation gives you access to the no-charge function of IBM Systems Director VMControl and a 60–day evaluation license for IBM Systems Director VMControl Image Manager. you can use the command line to perform an unattended installation of IBM Systems Director VMControl. Operating system Installation file name AIX Systems_Director_VMControl_2_1_AIX-full. IBM Systems Director VMControl V2.1. Before installing IBM Systems Director VMControl. For information. Disable SELinux by specifying SELINUX=disabled.1. Enter this command to reboot the system: #reboot 4. launch the IBM Systems Director VMControl program executable file: Note: If you want to use the installation wizard to install on AIX and Linux.sh Linux for xSeries Systems_Director_VMControl_2_1_Linux_x86-full. follow these steps: 1. As an alternative. see Hardware and software requirements for IBM Systems Director. Tip: You can temporarily disable SELinux by entering the following command: /usr/sbin/setenforce 0 v Download the IBM Systems Director VMControl installation program as follows: 1. To check SELinux status. Enter this command: #vi /etc/selinux/config 2. Log on the system and enter this command to check SELinux status: sestatus. Chapter 2. When the installation is complete. you must launch the installation program in a graphics-enabled session.exe This launches the installation wizard and displays the Welcome page.To install IBM Systems Director VMControl. IBM Systems Director VMControl is displayed in the IBM Systems Director Welcome page. perform the following tasks: v Make sure that you have installed IBM Systems Director version 6. If SELinux is not disabled. v Make sure that the target system satisfies all IBM Systems Director VMControl-specific prerequisites. v On Red Hat Enterprise Linux. Follow the instructions in the installation wizard to install IBM Systems Director VMControl. Go to the IBM Systems Director Downloads Web Site at: http://www. enter the following command: sestatus.

tar.zip Note: The IBM Systems Director VMControl evaluation license must be installed before you can install the permanent license key for IBM Systems Director VMControl.gz Permanent SysDir_VMControl_2_1_Linux_Power-full.gz Linux for pSeries Evaluation SysDir_VMControl_2_1_Linux_Power.gz Linux for zSeries Evaluation SysDir_VMControl_2_1_Linux_System_z.tar. Copy the downloaded installation package to a local drive on each IBM Systems Director Server on which you want to install IBM Systems Director VMControl. Be sure that you copy the correct package based on the operating system that is running on the IBM Systems Director Server.gz Windows Evaluation SysDir_VMControl_2_1_Windows. To set up and run an unattended installation of IBM Systems Director VMControl.gz Linux for xSeries Evaluation SysDir_VMControl_2_1_Linux_x86. 2. Save the modified installer. 5. 4.properties file in an ASCII text editor. Use the comments in the installer.zip Permanent SysDir_VMControl_2_1_Windows-full. follow these steps: 1. enter the following command: For AIX or Linux: gzip -cd <package_name> | tar -xvf - where <package_name> is the file name of the installation package.gz Permanent SysDir_VMControl_2_1_AIX-full. Open the installer. When you perform an unattended installation of IBM Systems Director VMControl.gz Permanent SysDir_VMControl_2_1_Linux_System_z-full.gz Permanent SysDir_VMControl_2_1_Linux_x86-full. 18 IBM Systems Director VMControl: Installation and User’s Guide .properties response file.tar.tar. 3. To unzip and extract the contents of the installation package. Open a command prompt and change to the directory that contains the IBM Systems Director VMControl installation file. 4.tar. a response file provides answers to the questions that are posed by the installation wizard. For Windows: unzip <package_name> where <package_name> is the file name of the installation package.tar.tar. 3.tar. Select the package to download: Operating system License Download package AIX Evaluation SysDir_VMControl_2_1_AIX.properties response file to modify the response file.

sh -i silent Permanent . To configure your system to be a NIM master.1. accessed.client – openssh.base.exe -i silent Permanent Systems_Director_VMControl_2_1_Windows-full.sh Permanent . Ensure that your system meets the following requirements: v The system is running AIX version 6./Systems_Director_VMControl_2_1_AIX-full.1. IBM Systems Director VMControl V2./Systems_Director_VMControl_2_1_Linux_Power./Systems_Director_VMControl_2_1_Linux_System_z.core – openssh./Systems_Director_VMControl_2_1_Linux_System_z- full.sh -i silent Linux for xSeries Evaluation .base../Systems_Director_VMControl_2_1_AIX.1 19 .server – openssh. 5.txt Installing IBM Systems Director VMControl subagent for NIM In order for IBM Systems Director VMControl to manage virtual appliances that contain AIX mksysb images./Systems_Director_VMControl_2_1_Linux_x86-full. accessed./Systems_Director_VMControl_2_1_Linux_Power- full.sh -i silent Linux for zSeries Evaluation ..sh -i silent Permanent .sh -i silent Permanent .txt v For Windows: .sh -i silent Windows Evaluation Systems_Director_VMControl_2_1_Windows.1 or later is installed on the system v The system has been discovered. Use these instructions to properly prepare your NIM master. enter the appropriate installation command: Operating system License Installation command AIX Evaluation . This NIM master must be discovered. you must have a properly installed and configured NIM master in your environment.license v Common Agent version 6.sh -i silent Linux for pSeries Evaluation . From the command prompt. and inventoried by your IBM Systems Director Server v The system must also be configured as a NIM master system. and inventoried by your IBM Systems Director Server.license – openssl. Check the appropriate log file to see if the installation completed successfully: v For AIX and Linux: /opt/ibm/director/VMControlManager/installLog.exe -i silent 6.1./Systems_Director_VMControl_2_1_Linux_x86./Director/VMControlManager/installLog. run the following command: Chapter 2.base – openssl.3 or later v The following filesets are installed: – dsm.

255. 1.255. 255.0 deploy_net where 2. If you created a new deploy_net network. you can use the disk=disk_name attribute to control which physical volume will hold the required /export/nim file system. Optionally. If it is on a different network. nim_master_setup -a device=path [-a disk=disk_name] -B where path is the absolute path of the directory where the AIX bos.2. Note: Do not define a NIM network object name that begins with the name of another NIM network object. then skip this step. 2.3. you need to use the disk=disk_name attribute. 255.sysmgt package can be found. then you must define another NIM network object for the virtual server.0 is the subnet mask for the network.255.4 -a snm=255. Note: The nim_master_setup command can take 20 minutes or longer to run. For example: nim -o define -t ent -a net_addr=2.3.2.255.3. then you will need to create one or more additional NIM network definitions. Log on to the NIM Master. a static route must be established between it and the secondary_net network object. and deploy_net is the NIM object name that you are creating. and secondary_net is the NIM network object name that you are creating. for example: nim -o change -a if2='secondary_net 1.4 -a snm=255.2. see the Defining NIM networks topic in the IBM Systems Information Center. Attach the secondary_net network object you created to the NIM Master resource.0 secondary_net where 1. a. 3. If the NIM Master has a secondary interface that you will be using to deploy virtual servers.3.255. b.255. For example. You can install the IBM Systems Director VMControl subagent for NIM in one of two ways. see the Establishing a static NIM route between networks topic in the IBM Systems Information Center.For more information.2. the master_net network object was created for you to represent the network associated with the NIM Master’s primary network interface. If the virtual server that you will be deploying is on the same network as the NIM Master’s secondary interface. You should also remove the default route on the deploy_net network. v If the NIM image repository (NIM Master) connects to IBM Systems Director Server through one network adapter.2.255.255. complete the following steps to configure your networks for the deploy task. Define a NIM network object for the NIM Master’s secondary network interface. When you ran nim_master_setup to configure your NIM Master. For example: nim -o define -t ent -a net_addr=1.4 0' -a cable_type2=N/A master 4. if you are using a SAN for your /export/nim file system.3.4 is the IP address of the network being defined. For more information. 20 IBM Systems Director VMControl: Installation and User’s Guide . and connects to the virtual server where you plan to deploy a virtual appliance through a different network adapter.0 is the subnet mask for the network.4 is the IP address of the network being defined.

Click Agents. Installing from the IBM Systems Director VMControl Summary page To install IBM Systems Director VMControl subagent for NIM from the IBM Systems Director VMControl Summary page. In the IBM Systems Director navigation pane. Chapter 2. Installing IBM Systems Director VMControl subagent for NIM manually You can install the IBM Systems Director VMControl subagent for NIM manually on the NIM master system in your environment. and select Release Management > Install Agent. From the Common Agent Subagent Packages view. Then follow the instructions in the installation wizard to install the subagent for NIM (CommonAgentSubagent_VMControl_NIM) on your NIM master system. select the subagent for NIM.rf. IBM Systems Director VMControl V2. expand Release management. 4.1. Installing from the IBM Systems Director Release Management task To install IBM Systems Director VMControl subagent for NIM from the IBM Systems Director Release Management task. click Install Agents on the Summary page. locate the subagent file. CommonAgentSubagent_VMControl_NIM_2. click Common Agent Subagent Packages.im.subagent. To manually install IBM Systems Director VMControl subagent for NIM.nim.0\ com. On the Agents page. follow these steps: 1.1 21 .log where Director is the path where IBM Systems Director is installed. You can start this wizard from the IBM Systems Director VMControl Summary page or from IBM Systems Director’s Release Management task. To verify that the IBM Systems Director VMControl subagent for NIM installed successfully. 3. follow these steps: 1. Follow the instructions in the installation wizard to install the subagent for NIM (CommonAgentSubagent_VMControl_NIM) on your NIM master system.zip.ibm. 6. 5.director. On the IBM Systems Director Server. sign on to the system on which you are installing the subagent and check the following error log for messages beginning with DNZIMN: Director/agent/logs/trace-log-0.Related reference “Planning for IBM Systems Director VMControl” on page 5 “Hardware and software requirements” on page 5 Related information “Subagent for NIM installation fails using Agent Installation wizard” on page 67 Installing IBM Systems Director VMControl subagent for NIM using the installation wizard You can install the IBM Systems Director VMControl subagent for NIM on your NIM master system using the IBM Systems Director Agent Installation wizard. Click Actions on the menu bar. 2.

director.im. Change directory to the NIM master system bin directory: /opt/ibm/director/ agent/bin 5.im.sh stop Director/agent/runtime/agent/bin/endpoint.director.sh -installFeatures -featureId com. UM32503./lwiupdatemgr. The following prerequisites must be met before you complete the tasks described in this topic: v z/VM 5.xml -toSite "file:/var/opt/tivoli/ep/runtime/agent/subagents/eclipse/" 6. Important: The following instructions provide examples for you to follow to perform pre-installation tasks and to install the IBM z/VM Manageability Access Point Agent.4 is installed and all service has been applied (including PTFs UM32505. UM32521.rf. 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.ibm. Restart the Common Agent to activate the IBM Systems Director IBM Systems Director VMControl subagent for NIM by running the following commands: Director/agent/runtime/agent/bin/endpoint.sh start where Director is the path where IBM Systems Director is installed.rf. 3. UM32522.zip\!/site.log where Director is the path where IBM Systems Director is installed. 7. UM32693 and UM32765) or a higher version that also supports the IBM z/VM Manageability Access Point Agent. Copy the file to a temporary directory on your NIM master system. as necessary. It is recommended that you also refer to documentation specific to your applications and any external security manager that you might be using. v TCP/IP is enabled and working v A VSWITCH or comparable network connection is available to use v You have read the documentation that is provided by your Linux distribution.ibm. To prepare your z/VM system for installation and to install the IBM z/VM Manageability Access Point Agent.subagent -fromSite jar:file:/tmp/site/com. you will perform the following tasks: 22 IBM Systems Director VMControl: Installation and User’s Guide . Note: The subagent file is located in the Director/tpm/repository/directory where Director is the path where IBM Systems Director is installed. To verify that the IBM Systems Director VMControl subagent for NIM installed successfully. Log in to the NIM master system. check the following error log for messages beginning with DNZIMN: Director/agent/logs/*. 4.nim. such as /tmp/site.subagent. The default location is as follows: v AIX or Linux /opt/ibm/director/tpm/repository v Windows C:\Program Files\IBM\Director\tpm\repository 2.nim. Run the install tool with the following command: .

Note: Several products can be used to manage the z/VM user directory. However,
DirMaint™ is the directory manager described in the following instructions.
v Configure DirMaint
v Update PROFILE EXEC on AUTOLOG1
v Start DirMaint
v Test DirMaint
v Configure Systems Management Application Programming Interface (API)
v Customize the EXTENT CONTROL file
v (Optional) Shutdown and re-IPL z/VM system
v Configure the ZVMMAPLX user ID
v Install Linux on the ZVMMAPLX user ID
v Ensure that required RPMs are installed
v Ensure that required Linux patches are installed
v Ensure that the kernel module af_iucv is properly loaded
v Ensure that an appropriate user class is defined for the ZVMMAPLX user ID
v Install the agent
v Install the IBM z/VM Manageability Access Point Agent

For additional information about installing and configuring Linux on the z/VM
system, refer to the following documentation:
v Documentation that is provided by your Linux distribution.
v z/VM V5R4.0 Getting Started with Linux on System z9® and zSeries
(SC24-6096-03)
v Virtualization Cookbooks:
– z/VM and Linux on IBM System z The Virtualization Cookbook for Red Hat
Enterprise Linux 5.2 (SG24–7492)

Note: The installation process for Red Hat Enterprise Linux 5.3 might be
slightly different than the process described in this cookbook.
– z/VM and Linux on IBM System z The Virtualization Cookbook for SLES 10
SP2 (SG24–7493)

Configure DirMaint
You must configure DirMaint so you can use it to manage the user directory.

To configure DirMaint, complete the following steps:
1. Configure DirMaint and the associated user IDs.
a. Log on to MAINT.
b. Edit the USER DIRECT file, so you can log on to the DIRMAINT,
DATAMOVE, and DIRMSAT user IDs.
Run the following command to open the USER DIRECT file:
xedit user direct

Change the passwords of the three user IDs from NOLOG to your chosen
passwords. The edited USER DIRECT file should look similar to the
following example.

Chapter 2. IBM Systems Director VMControl V2.1 23

...
USER DIRMAINT PASSWD_A 32M 64M BDG
...
USER DATAMOVE PASSWD_B 32M 128M BG
...
USER DIRMSAT PASSWD_C 16M 16M BG

where PASSWD_A, PASSWD_B, and PASSWD_C are the new passwords for
the DIRMAINT, DATAMOVE, and DIRMSAT user IDs, respectively.
c. Run the following command to bring your changes online:
directxa user

A message indicating that the directory is updated and online, should be
displayed.
2. Enable the DirMaint application:
a. Run the following SERVICE command on the MAINT user ID to enable the
DirMaint application:
service dirm enable

You should see results that are similar to the following output:
VMFSRV2760I SERVICE processing completed successfully

This process appends two lines to the end of your SYSTEM CONFIG file,
indicating that DirMaint is enabled. However, DirMaint must be configured
before it can be used for production.
b. Run the following command to log off of MAINT:
logoff
3. Access 5VMDIR40 disks.
a. Log on to 5VMDIR40.
b. Run the following command to access the 492 disk as E:
access 492 e
c. Run the following command to access test build minidisks:
dir2prod access_new 5vmdir40 dirm

You should see results that are similar to the following output:
DMSACP726I 492 E released
DIR2PROD: Normal Termination.

You can see that you have new minidisks accessed as J, K, and L, by
running the following command:
query disk

You should see results that are similar to the following output:

24 IBM Systems Director VMControl: Installation and User’s Guide

LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL
DRM191 191 A R/W 9 3390 4096 2 12-01 1608 1620
MNT5E5 5E5 B R/O 9 3390 4096 131 1290-80 330 1620
MNT51D 51D D R/W 26 3390 4096 284 1356-29 3324 4680
DIR1DF 1DF J R/W 9 3390 4096 13 20-01 1600 1620
DRM492 492 K R/W 15 3390 4096 269 1482-55 1218 2700
DRM41F 41F L R/W 8 3390 4096 50 641-45 799 1440
MNT190 190 S R/O 100 3390 4096 691 14784-82 3216 18000
MNT19E 19E Y/S R/O 250 3390 4096 1018 28192-63 16808 45000

d. Run the following command to access the 11F disk as Z:
access 11f z
e. Run the following command to link and access the MAINT 2CC disk:
vmlink maint 2cc

You should see results that are similar to the following output:
ENTER READ PASSWORD
DMSVML2060I MAINT 2CC linked as 0120 file mode X

f. Specify the password. The default password is READ; however it may have
been modified at your site.
g. Run the following command to copy the USER DIRECT file from MAINT
2CC to DIRMAINT 1DF as the file USER INPUT:
copyfile user direct x = input j
4. Edit the CONFIGSM DATADVH file.
a. Run the following command to create the file CONFIGSM DATADVH Z,
which is the main DirMaint configuration file:
xedit configsm datadvh z

Type the following text into the CONFIGSM DATADVH Z file:
ALLOW_ASUSER_NOPASS_FROM= DIRMAINT *
ALLOW_ASUSER_NOPASS_FROM= MAINT *
ALLOW_ASUSER_NOPASS_FROM= VSMWORK1 *
ALLOW_ASUSER_NOPASS_FROM= VSMWORK2 *
ALLOW_ASUSER_NOPASS_FROM= VSMWORK3 *
DATAMOVE_MACHINE= DATAMOVE vmnetid *
DISK_CLEANUP= YES
ONLINE= IMMED
RUNMODE= OPERATIONAL
ASYNCHRONOUS_UPDATE_NOTIFICATION_EXIT.UDP= DVHXNE EXEC
ASYNCHRONOUS_UPDATE_NOTIFICATION_EXIT.TCP= DVHXNE EXEC

b. Run the following command to release the z disk:
release z
c. Run the following commands so your configuration changes take effect.
access 492 e
dir2prod prod 5VMDIR40 dirm

You should see results that are similar to the following output:

Chapter 2. IBM Systems Director VMControl V2.1 25

DIR2PROD: Normal Termination. b. Log on to AUTOLOG1. Edit the PROFILE EXEC file on the AUTOLOG1 191 disk so that the DIRMAINT and DATAMOVE service machines are automatically started when the z/VM host is IPLed. This prevents the existing PROFILE EXEC from running and ensures that you are not logged off before you can edit the PROFILE EXEC file. Add the lines indicated in bold type to your PROFILE EXEC file if they do not exist already. To update PROFILE EXEC. d. a. Log on to AUTOLOG1 in a non-disruptive manner. type access (noprof and press Enter. Command: VMFCOPY * EXEC F = = G (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY * XEDIT F = = G (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY * DATADVH F = = G (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY * DATAADVH F = = G (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY * DATAKDVH F = = G (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY * DATAUDVH F = = G (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY * MSGADVH F = = G (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY * MSGKDVH F = = G (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY * MODULE F = = G (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY * NEWMAIL F = = G (PRODID 5VMDIR40%DIRM OLDDATE REPLACE DIR2PROD: Copy of 41F disk to 11F disk has completed. DIR2PROD: Copy of 492 disk to 491 disk has started. Run the following command to open the PROFILE EXEC file: xedit profile exec b. DIR2PROD: Copy of 41F disk to 11F disk has started. Command: VMFCOPY * EXEC E = = F (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY * REXX E = = F (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY * XEDIT E = = F (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY * DATADVH E = = F (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY * DATAADVH E = = F (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY * DATAUDVH E = = F (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY * MODULE E = = F (PRODID 5VMDIR40%DIRM OLDDATE REPLACE Command: VMFCOPY DVHPROFA * E = = F (PRODID 5VMDIR40%DIRM OLDDATE REPLACE DIR2PROD: Copy of 492 disk to 491 disk has completed. 2. 26 IBM Systems Director VMControl: Installation and User’s Guide . Run the following command to log off of 5VMDIR40: logoff Update PROFILE EXEC on AUTOLOG1 You must update PROFILE EXEC on AUTOLOG1 to log on to the DIRMAINT and DATAMOVE service machines and to re-IPL z/VM. complete the following steps: 1. Use the following example as a guide in editing the PROFILE EXEC file. When you see VM READ in the lower left corner of the screen. a.

refer to any error messages and resolve them. with RC = 0. Log on to MAINT. RDR FILE 0010 SENT FROM DIRMAINT PUN WAS 0010 RECS 0142 CPY 001 A NOHOLD NOKEEP DVHREQ2289I Your NEWS request for MAINT at * has completed. 3.03/0.03 22:39:23 DVHREQ2288I Your NEWS request for MAINT at * has been accepted. This is the universal DirMaint command that requires no authority: dirm news You should see results that are similar to the following output: DVHXMT1191I Your NEWS request has been sent for processing. 2. complete the following steps: 1. complete the following steps: 1. Ready. Log on to DIRMAINT. 3.1 27 . Run the following command. PROFILE EXEC A1 V 130 Trunc=130 Size=36 Line=0 Col=1 Alt=0 00000 * * * Top of File * * * 00001 /***************************/ 00002 /* Autolog1 Profile Exec */ 00003 /***************************/ 00004 'CP XAUTOLOG TCPIP' /* start up zVM TCPIP stack */ 00005 'CP XAUTOLOG VMSERVS' /* For SFS */ 00006 'CP XAUTOLOG VMSERVU' 00007 'CP XAUTOLOG VMSERVR' 00008 'CP XAUTOLOG DTCVSW1' /* Vswitch controller 1 */ 00009 'CP XAUTOLOG DTCVSW2' /* Vswitch controller 2 */ 00010 'CP XAUTOLOG DIRMAINT' /* Start DIRMAINT */ 00011 'CP XAUTOLOG DATAMOVE' /* and DATAMOVE for DIRMAINT */ 00012 'CP SLEEP 30 SEC' 00013 'CP XAUTOLOG VSMWORK1' /* For SMAPI */ 00014 'CP XAUTOLOG VMRMSVM' /* For VMRM */ 00015 'CP SET PF12 RET' /* set the retrieve key */ 00016 'CP LOGOFF' /* logoff when done */ 00017 * * * End of File * * * 3. Run the following command to log off of AUTOLOG1: logoff Start DirMaint Start DirMaint to perform management tasks on the user directory. Run the following command to disconnect from DirMaint: #cp disconnect Test DirMaint You must test DirMaint to ensure that it is ready for use. IBM Systems Director VMControl V2. Chapter 2. If you do not see the line of text that indicates the process is waiting for work. Edit the AUTHFOR CONTROL file on the DirMaint 01DF (Filemode=E) disk to grant MAINT universal authority to issue all DirMaint commands. Run the following command to start DirMaint: dvhbegin Ensure that the following line is displayed at the end of the output: DVHWAI2140I Waiting for work on 08/05/27 at 12:21:22. To start DirMaint. 2. T=0. To test DirMaint.

Note: You will be prompted for the MAINT password. a. Ready. You should see results that are similar to the following output: 28 IBM Systems Director VMControl: Installation and User’s Guide . Run the following command to view the file: peek 0017 where 0017 is the spool ID number of the file being sent to the MAINT reader.03/0. with RC DVHREQ2289I = 0. for example. RDR FILE 0017 SENT FROM DIRMAINT PUN WAS 0021 RECS 0487 CPY 001 A NOHOLD NOKEEP DVHREQ2289I Your REVIEW request for MAINT at * has completed. Run the following command so that passwords are no longer required for every command. where 0017 is the spool ID number of the file being sent to the MAINT reader. 5. dirm needpass no Ensure that the output indicates a return code of 0. The edited file should look like the following example: ALL MAINT * 140A ADGHMOPS ALL MAINT * 150A ADGHMOPS ALL VSMWORK1 * 140A ADGHMOPS ALL VSMWORK1 * 150A ADGHMOPS ALL VSMWORK2 * 140A ADGMHOPS ALL VSMWORK2 * 150A ADGMHOPS ALL VSMWORK3 * 140A ADGMHOPS ALL VSMWORK3 * 150A ADGMHOPS ALL VSMREQIU * 140A ADGMHOPS ALL VSMWORK3 * 150A ADGMHOPS ALL VSMREQIU * 140A ADGMHOPS ALL VSMREQIU * 150A ADGMHOPS ALL VSMREQIN * 140A ADGMHOPS ALL VSMREQIN * 150A ADGMHOPS ALL VSMPROXY * 140A ADGMHOPS ALL VSMPROXY * 150A ADGMHOPS ALL ZVMMAPLX * 140A ADGHMOPSQ ALL ZVMMAPLX * 150A ADGHMOPSQ 4. T=0. RC = 0.03 11:45:46 DVHREQ2288I Your REVIEW request for MAINT at * has been accepted. Run the following command to send a file that contains an overview of the directory entry to the MAINT reader: dirm rev You should see results that are similar to the following output: DVHXMT1191I Your REVIEW request has been sent for processing. b. Perform an additional test to ensure that DirMaint is working.

VSMWORK1 AUTHLIST B1 F 195 Trunc=195 Size=6 Line=1 Col=1 Alt=1 ==== * * * Top of File * * * ==== DO.REMOVE DO. d. IBM Systems Director VMControl V2. Configure Systems Management Application Programming Interface (API) You must configure the Systems Management Application Programming Interface (API) for use by the z/VM manageability access point.NOT.NOT. 5. Log on to user ID VSMWORK1. To configure the Systems Management Application Programming Interface (API). Save the file with the FILE subcommand. For example: USER VSMREQIU XXXXXXXX 512M 512M G Chapter 2. The ZVMMAPLX user ID is predefined in the user directory and designed to manage the z/VM manageability access point server. complete the following steps: 1. 2. Quit out of the file by pressing F3.REMOVE ==== MAINT ALL ==== VSMPROXY ALL ==== VSMWORK1 ALL ==== ZVMMAPLX ALL ==== * * * End of File * * * 4. Create the VSMWORK1 AUTHLIST file to include the ZVMMAPLX user ID. B 3. Update the directory entry for VSMREQIU to have 512M of memory. Run the following commands to access the disks: #CP IPL CMS access (noprof set filepool VMSYS access VMSYS:VSMWORK1.1 29 . Run the following command to create the VSMWORK1 AUTHLIST file: xedit vsmwork1 authlist B The VSMWORK1 AUTHLIST file should look like the following example: Note: The VSMWORK1 user ID is included because it is required for basic Systems Management Application Programming Interface (API) configuration. It is not specifically required for the IBM z/VM Manageability Access Point Agent. Run the following command to log off of MAINT: logoff Successful completion of DIRM REV confirms that DirMaint is running. USER MAINT XXXXXXXX 128M 1000M ABCDEFG ACCOUNT 1 SYSPROG IPL 190 MACH ESA NAMESAVE GCS VTAM OPTION MAINTCCW LNKS LNKE LNKNOPAS POSIXINFO UID 0 GNAME system XAUTOLOG AUTOLOG1 OP1 MAINT CONSOLE 0009 3215 T SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A * LINK CMSBATCH 195 801 WR * LINK AVSVM 191 802 WR c.

This file provides a template of how the disk spaces should be allocated. complete the following steps: 1. Additionally. Run the following command to edit the EXTENT CONTROL file that is on the MAINT 191 disk: xedit extent control a 30 IBM Systems Director VMControl: Installation and User’s Guide . You should see results that are similar to the following output: File EXTENT CONTROL A1 replaced by EXTENT CONTROL E1 received from DIRMAINT at System_A where System_A is your z/VM system. 2. If you have an existing copy of the EXTENT CONTROL file on your A disk. To customize the EXTENT CONTROL file. a. Log on to MAINT. 6.03 10:50:34 DVHREQ2288I Your SEND request for MAINT at * has been accepted. you might want to back it up. RDR FILE reader_file_number SENT FROM DIRMAINT PUN WAS 0008 RECS 0058 CPY 001 A NOHOLD NOKEEP DVHREQ2289I Your SEND request for MAINT at * has completed. T=0. c. with RC = 0. d. Run the following command to create a backup of the EXTENT CONTROL file: copy extent control a = contorig = b. Ready. Update the EXTENT CONTROL file with the new DASD that will be under the control of your directory manager. Run the following command to receive the file from the reader: receive reader_file_number = = a (rep where reader_file_number is the reader file number returned in the output of the DIRM SEND EXTENT CONTROL command. These DASD volume pools are defined in the EXTENT CONTROL file. IBM Systems Director relies on DirMaint to allocate minidisks out of a preferred pool of DASD volumes. system and device default values are defined for use during disk allocation operations. Run the following command to restart VSMWORK1: ipl cms 7. Run the following command to disconnect from VSMWORK1: #cp disconnect Customize the EXTENT CONTROL file You must customize the EXTENT CONTROL file to specify the appropriate DASD addresses and minidisk allocation method. Run the following command to fetch the EXTENT CONTROL file from DIRMAINT: dirm send extent control You should see results that are similar to the following output: DVHXMT1191I Your SEND request has been sent for processing.03/0. where XXXXXXXX is the password for the VSMREQIU user ID.

This process refreshes the DIRMAINT memory and enables the changes to the EXTENT CONTROL to take effect: dirm rlde You should see results that are similar to the following output: Chapter 2. RC = 0. T=0. DVHREQ2289I Your FILE request for MAINT at * has completed. e. Run the following commands to reload the EXTENT CONTROL file. IBM Systems Director VMControl V2.04 15:51:17 DVHREQ2288I Your FILE request for MAINT at * has been accepted. The following example shows a modified EXTENT CONTROL file where CP system-attached 3390 Mod 3 DASDs and 3390 Mod 9 DASDs have been added. 00070 * UserId Address 00071 MAINT 012* 00072 SYSDUMP1 012* 00073 :END. Ready. Run the following command to send the EXTENT CONTROL file back to DIRMAINT: dirm file extent control You should see results that are similar to the following output: PUN FILE 0074 SENT TO DIRMAINT RDR AS 0045 RECS 0051 CPY 001 0 NOHOLD DVHXMT1191I Your FILE request has been sent for processing. 00069 :EXCLUDE. 00038 *RegionId VolSer RegStart RegEnd Dev-Type Comments 00039 DM6350 DM6350 0001 END 3390-03 00040 DM6351 DM6351 0001 END 3390-03 00041 DM6352 DM6352 0001 END 3390-03 00042 DM6353 DM6353 0001 END 3390-03 00043 DM6354 DM6354 0001 END 3390-03 00044 DM6355 DM6355 0001 END 3390-03 00045 DM6356 DM6356 0001 END 3390-03 00046 DM6357 DM6357 0001 END 3390-03 00047 DM6358 DM6358 0001 END 3390-03 00048 DM6359 DM6359 0001 END 3390-03 00049 DM635A DM635A 0001 END 3390-03 00050 DM635B DM635B 0001 END 3390-03 00051 DM635C DM635C 0001 END 3390-03 00052 DM635D DM635D 0001 END 3390-03 00053 DM635E DM635E 0001 END 3390-03 00054 DM63B6 DM63B6 0001 END 3390-09 00055 DM63B7 DM63B7 0001 END 3390-09 00056 DM63B8 DM63B8 0001 END 3390-09 00057 DM63B9 DM63B9 0001 END 3390-09 00058 DM63BA DM63BA 0001 END 3390-09 00059 DM63BB DM63BB 0001 END 3390-09 00060 :END. f. DVHRCV3821I File EXTENT CONTROL E2 has been received.03/0. 00062 *GroupName RegionList 00063 POOL1 (ALLOCATE ROTATING) 00064 POOL1 DM6350 DM6351 DM6352 DM6353 DM6354 DM6355 DM6356 DM6357 00065 POOL1 DM6358 DM6359 DM635A DM635B DM635C DM635D DM635E 00066 POOL2 DM63B6 DM63B7 00067 POOL2 DM63B8 DM63B9 DM63BA DM63BB 00068 :END. Changes are indicated in bold and are described as follows: EXTENT CONTROL A2 V 80 Trunc=80 Size=85 Line=34 Col=1 Alt=0 00034 * None (yet). with RC = 0. 00035 * 00036 * ******************************************************************** 00037 :REGIONS. 00061 :GROUPS.1 31 .

the remaining disk space would be insufficient. To configure the ZVMMAPLX user ID. a large file system could be mounted over /var/opt/ibm. which is the size of a 3390 Mod 3 DASD. The example shows a minidisk with 3338 cylinders. the file in the user directory is modified to specify a minidisk that is backed by a 3390 Mod 9 DASD with 10016 cylinders. The ZVMMAPLX default user ID definition contains a default VSWITCH named VSWID1. If you decide to re-IPL the system. Also. You should have no more than one z/VM manageability access point per z/VM system. VSW1. ensure that you first notify all of your users. Configure ZVMMAPLX user ID You must configure the ZVMMAPLX user ID by updating the user directory. A z/VM guest virtual server named ZVMMAPLX is predefined in the z/VM user directory and is designed to be used for the z/VM manageability access point.2 GB of disk space. Note: This task assumes that you are using a VSWITCH as your network connection. After Linux is installed. This configuration results in almost 7 GB of disk space. complete the following steps: 1. The default VSWITCH name and default values for the minidisk often need to be modified. (Optional) Shutdown and re-IPL z/VM system You might want to shutdown and re-IPL the z/VM system to ensure that all of the previous steps will take effect and that DirMaint starts properly at IPL time. For example. DVHILZ3510I Starting DVHINITL with directory: USER DIRECT E DVHILZ3510I DVHINITL Parms: BLDMONO BLDDASD BLDLINK DVHIZD3528W One or more DASD volume control files (DV6220) were DVHIZD3528W created using default values for device characteristics - DVHIZD3528W $ALLOC$ 0A01 DVHREQ2289I Your RLDEXTN request for MAINT at * has completed. 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. other comparable types of network connections can be used. Run the following command to modify the user directory: dirm for zvmmaplx get 32 IBM Systems Director VMControl: Installation and User’s Guide . Therefore. for example. you need ensure there is sufficient disk space available for the ZVMMAPLX virtual server. as the stored images are below this directory. T=0. Use the following example as a guide to changing the default values. You can add more disk space now to prepare for an image repository.03/0. Ready. or you can add disk space later. and it contains default values for the size and label of a minidisk. You might need to add a significant amount of disk space if the z/VM manageability access point will contain an image repository. Formatting a disk of this size for Linux results in about 2. The example also shows that the default VSWITCH name of VSWID1 is modified to the name of a VSWITCH that has been created previously. However. DVHXMT1191I Your RLDEXTN request has been sent for processing.03 15:54:47 DVHREQ2288I Your RLDEXTN request for MAINT at * has been accepted. with RC = DVHREQ2289I 0. You need to ensure that the VSWITCH defined in the ZVMMAPLX user ID is accessible.

You should see results that are similar to the following output: File ZVMMAPLX DIRECT A0 replaced by ZVMMAPLX DIRECT A0 received from DIRMAINT at System_A where System_A is your z/VM system. 3. for example. Note: Ensure that you update the VSWITCH to enable the ZVMMAPLX machine to access the VSWITCH. DVHGET3304I Directory entry ZVMMAPLX is now locked. 5. T=0. v Define a minidisk for the virtual server by changing the size and label for the minidisk to the values appropriate for your system. RDR FILE reader_file_number SENT FROM DIRMAINT PUN WAS 0931 RECS 0019 CPY 001 A NOHOLD NOKEEP DVHREQ2289I Your GET request for ZVMMAPLX at * has completed.03/0.03 14:44:53 DVHREQ2288I Your GET request for ZVMMAPLX at * has been accepted. Ready. Run the following command to send the directory entry to the reader: receive reader_file_number zvmmaplx direct a (rep where reader_file_number is the reader file number specified in the output of the DIRM GET command. Edit the file as follows: v Specify a VSWITCH that is appropriate for your installation. USER ZVMMAPLX DRCT 512M 1G ABCEG IPL 0150 OPTION LNKNOPAS LANG AMENG SPOOL 00C 2540 READER * SPOOL 00D 2540 PUNCH A SPOOL 00E 1403 A LINK MAINT 0190 0190 RR LINK MAINT 019D 019D RR LINK MAINT 019E 019E RR NICDEF 7000 TYPE QDIO LAN SYSTEM VSWID1 MDISK 150 3390 001 3338 $$$LNX MR 4. VSW1. 2.1 33 . Run the following command to open the file: xedit zvmmaplx direct The file should look like the following example: Note: The LNKNOPAS and LANG AMENG options are required for the setup of this virtual server. You should see results that are similar to the following output: DVHXMT1191I Your GET request has been sent for processing. IBM Systems Director VMControl V2. Run the following command to update the user directory: dirm for zvmmaplx replace You should see results that are similar to the following output: Chapter 2. with RC DVHREQ2289I = 0. You can change the VSWITCH name of VSWID1 to the name of a VSWITCH that has been created previously.

03/0. 6. complete the following steps: 1.0 Getting Started with Linux on System z9 and zSeries (SC24-6096-03) v Virtualization Cookbooks: – z/VM and Linux on IBM System z The Virtualization Cookbook for Red Hat Enterprise Linux 5. DVHREQ2289I Your REPLACE request for ZVMMAPLX at * has completed. Ensure that the required RPMs are installed for the operating system you are running: 34 IBM Systems Director VMControl: Installation and User’s Guide .2 (SG24–7492) Note: The installation process for Red Hat Enterprise Linux 5. If the Linux system is not already running. DVHBIU3424I The next ONLINE will take place immediately. DVHBIU3450I The source for directory entry ZVMMAPLX has been updated. see Supported operating systems. DVHBIU3428I Changes made to directory entry ZVMMAPLX have been placed DVHBIU3428I online. To install Linux. with DVHREQ2289I RC = 0. Run the following commands to authorize ZVMMAPLX to issue DIRMAINT commands: dirm for all authfor zvmmaplx cmdl 140a cmds adghops dirm for all authfor zvmmaplx cmdl 150a cmds adghops Install Linux on the ZVMMAPLX user ID You must install Linux on the ZVMMAPLX user ID. v z/VM V5R4. DVHREP3603I Directory entry ZVMMAPLX is now unlocked.3 might be slightly different than the process described in this cookbook. refer to the following documentation: v Installation documentation for your Linux distribution. PUN FILE 0595 SENT TO DIRMAINT RDR AS 0932 RECS 0023 CPY 001 0 NOHOLD NOKEEP DVHXMT1191I Your REPLACE request has been sent for processing.03 14:57:47 DVHREQ2288I Your REPLACE request for ZVMMAPLX at * has been accepted. Ensure that required RPMs are installed You must verify that all of the required RPMs for your Linux distribution are installed on the Linux running on the ZVMMAPLX user ID. Ready. To install Linux on the ZVMMAPLX user ID. This task installs Linux with the root file system onto minidisk 150. – z/VM and Linux on IBM System z The Virtualization Cookbook for SLES 10 SP2 (SG24–7493) 2. For information about the supported Linux distributions. The following RPMs are the minimum required levels of RPMs that you need to install. log on to the ZVMMAPLX user ID to start the Linux system. DVHDRC3451I The next ONLINE will take place via delta object directory. T=0.

s390x.1.rpm v pam-0.7.rpm v xorg-x11-6.s390.3- 61.0-5.s390x.rpm v star-1.99.0.6.14.2.2.9.el5.s390.23-15.rpm SUSE Linux Enterprise Server 10 SP 2 for 64-bit v compat-32bit-2006.17-2.25- IBM System z 11.6.s390.2.rpm v libxml2-32bit-2.42*.rpm v pam-modules-32bit-10- 2.rpm v libxslt-1.s390x.1.1.2.rpm v libXp-1.s390.rpm v star-1.s390x.s390x.0- 50.rpm v xorg-x11-libs-32bit-6.3 for 64-bit v compat-libstdc++-295-2.6.rpm v libxml2-2.rpm SUSE Linux Enterprise Server 9 SP 4 for 64-bit v compat-2004.rpm v libxslt-1.rpm v libX11-1.s390x.rpm IBM System z v compat-32bit-9- 200407011411.s390x.4.rpm v expect-5.1-1.s390x.2.5a75-2.3.0-8.3-9.0-29.rpm v libxml2-2.s390x.s390.2. RPMs required for various operating system installations Installation scenario Required RPMs Red Hat Enterprise Linux version 5.rpm v libxml2-2.3. Chapter 2.rpm v libxslt-1.rpm v expect-5.s390x.0. Ensure that required Linux kernel levels and patches are installed You must ensure that all of the required kernel levels and patches for your Linux distribution are installed on the Linux running on the ZVMMAPLX user ID.rpm v expect-5.19.1.43.1 35 .Table 2.s390x. Run the following command to determine whether the RPMs are installed: rpm -qa 2.7.s390x.7.42*.s390.rpm 1.rpm v star-1.2.el5_2.rpm v libxml2-32bit-9- 200412202205.rpm v compat-libstdc++-33-3. If the RPMs are not installed.1.1.23-15.2.2-4.el5.19.7-28.2. ensure that you install them.5final-28.rpm v xorg-x11-xauth-1.4.s390x.15-15.s390x.s390x.9.5final-28.el5.6.rpm v pam-modules-32bit-10- 2.6.s390.7.rpm v pam-32bit-0.14.58.1.s390x.0-50.s390x.1.rpm v XFree86-libs-32bit-9- 200512021711.95.s390x.26-2.s390x.0-29.s390x.0. IBM Systems Director VMControl V2.rpm v pam-32bit-0.8.99.1-2.8.s390.99.3- IBM System z 85.

v Red Hat Enterprise Linux bug 503240 . Kernel levels and patches required for various operating system installations Installation scenario Required kernel levels and patches Red Hat Enterprise Linux version 5. IBM System z plus patch 54-01 from Novell bug 516789 . To verify whether these patches are on your system.6.60-0. Ensure that the following kernel levels and patches are installed for any Linux systems on which the IBM z/VM Manageability Access Point Agent is installed. complete the following steps: 1. a.39. Configure the module to load every time the system is booted: v For SUSE Linux: 1) Open the following file: /etc/sysconfig/kernel 2) Look for the following line: MODULES_LOADED_ON_BOOT="" 36 IBM Systems Director VMControl: Installation and User’s Guide . and to obtain these patches.iucv: provide second per-cpu IUCV command parameter block.6.16. Run the following command to load the module: modprobe af_iucv b. contact the service provider for your Linux distribution.3. IBM System z plus patches 30-02 and 30-03 from Novell bug 493578 . Ensure that the kernel module af_iucv is properly loaded You must verify that the kernel module af_iucv is properly loaded. SUSE Linux Enterprise Server 10 SP 2 for 64-bit Minimum kernel level 2. 2. The next update release of your Linux distribution after the releases stated in the following table should contain these patches. running the command will produce results similar to the following output: af_iucv 150624 0 iucv 111192 1 af_iucv If you do not receive this output.SLES 9 SP4 . To ensure that the kernel module af_iucv is properly loaded. Load the module. the module was not loaded and you need to perform the next step.SLES 10 SP2 - IBM LTC zSeries Maintenance patches (#30).af_iucv: consolidated Bugzilla for miscellaneous af_iucv fixes. SUSE Linux Enterprise Server 9 SP 4 for 64-bit Minimum kernel level 2.3 for 64-bit v Red Hat Enterprise Linux bug IBM System z 487697 .317. Table 3.IBM LTC zSeries Maintenance Patches (#54). Run the following command: lsmod |grep af If the module was properly loaded.5-7.

When LNKNOPAS is specified. This can be done by specifying the LNKNOPAS option in the directory entry for the ZVMMAPLX user ID. The ZVMMAPLX virtual server (the virtual server on which the IBM z/VM Manageability Access Point Agent runs) requires the following z/VM privclasses and commands. 3) Change the line as follows: MODULES_LOADED_ON_BOOT="af_iucv" v For Red Hat Linux: 1) Create the following file: /etc/rc.modules 2) Add the following line to the file: modprobe af_iucv 3) Set the following permission to the file: chmod +x /etc/rc.modules Ensure that the appropriate privilege classes are defined for the ZVMMAPLX user ID You must give the ZVMMAPLX user ID the necessary privilege classes or authorize the user ID to issue the commands through the external security manager. the ZVMMAPLX virtual server must have the ability to link to other virtual servers without specifying a password. password authorization may still be required when an external security manager (ESM) is installed. Table 4. Chapter 2. Privilege class and commands required by the ZVMMAPLX virtual server Privilege Class Command A SET CPUAFFINITY B ATTACH QUERY LAN QUERY OSA QUERY TDISK QUERY VSWITCH C SET PRIVCLASS E INDICATE USER QUERY SHARE SET SHARE G DETACH LINK QUERY MDISK QUERY USERID QUERY VIRTUAL DASD ’any’ QUERY USERS In addition to the privilege classes listed in the table. IBM Systems Director VMControl V2.1 37 .

type the following command: tar -zxvf SysDir6_1_1_zVM_Map_Agent_System_z.0./dir6. Refer to Installing Platform Agent to install the IBM Systems Director Platform Agent on your z/VM system. scroll down to the Agents for IBM Systems Director Servers section. Log on using your universal IBM user ID and password.ibm. d. f. complete the following steps: a. Change directory to the FILES subdirectory by running the following command: cd FILES 5. extract the contents of the package. On the Downloads page for IBM Systems Director Agents for Manual Deployment. run the following command to verify whether the IBM z/VM Manageability Access Point Agent installed successfully: # rpm -qa | grep zV 38 IBM Systems Director VMControl: Installation and User’s Guide . refer to Shelf: z/VM V5R4.com/systems/management/director/ downloads/. 3.sh 6. Copy the installation package to the Linux that runs on your ZVMMAPLX user ID. complete the following steps: 1. and select IBM z/VM Manageability Access Point Agent for System z.gz The installation package files are available from the IBM Systems Director download Web page at www. Start the installation by running the following script as root user: .1. refer to the documentation for your external security manager. For documentation related to RACF®.tar. To install the IBM z/VM Manageability Access Point Agent. To extract the contents of the installation package. For more information about external security manager authorizations. Install the Platform Agent You must install the IBM Systems Director Platform Agent on the Linux that runs on your ZVMMAPLX user ID. 2. Click Choose and download Common or Platform Agents to install manually.gz 4. If the installation process runs without errors. Accept the license agreement. and verify the installation on the Linux that runs on your ZVMMAPLX user ID.1-1_zvmmapagent_linux. e. run the installation script. Obtain the following installation package: SysDir6_1_1_zVM_Map_Agent_System_z.tar. c. Click Agents. b. Install the IBM z/VM Manageability Access Point Agent You must obtain the installation package. Click Download now. From the IBM Systems Director Downloads Web page.

b. Chapter 2..d/ibmsa stop c.1-1 7. Run the following command to remove the images directory: rm -rf images g. If the directory is not empty.d/cimserverd stop /etc/init.d/tier1slpinst stop /etc/init. create a tar file containing its contents in the parent directory. either immediately after installation or at a later time. Run the following command: tar -cf . The IBM z/VM Manageability Access Point Agent contains a repository of captured and imported virtual appliances.. You should see the following RPM in the output if the IBM z/VM Manageability Access Point Agent installed successfully: zVMMAP-6. If you want the repository to remain after you uninstall the IBM z/VM Manageability Access Point Agent. /etc/init.Name="VM1" //Instance of IBMzVM_HostOperatingSystem instance of IBMzVM_HostOperatingSystem{.tar * e.. Use the following instructions to relocate the repository..} where . Run the following commands to stop the Platform Agent services.CreationClassName="IBMzVM_HostOperatingSystem".1. represents a number of omitted lines in the form of <name> = <value>./images.CSName="VM1". To relocate the virtual appliance repository. Attention: A repository in this default location will be removed when the agent is uninstalled. Run the following command to change to the directory /var/opt/ibm/zvmmap/repository: cd /var/opt/ibm/zvmmap/repository f. you can relocate the repository. Log on as root to the Linux system in which the IBM z/VM Manageability Access Point Agent is installed. 8. for example). Optional: Relocate the virtual appliance repository.d/cimlistenerd stop /etc/init. IBM Systems Director VMControl V2. or if you want the repository to exist in a different location (where more file system space is available. the repository is located at /var/opt/ibm/zvmmap/repository/images on the Linux system in which the IBM z/VM Manageability Access Point Agent is installed. complete the following steps: a.1 39 . CSCreationClassName="IBMzVM_HostComputerSystem". Run the following command to change to the directory /var/opt/ibm/zvmmap/repository/images: cd /var/opt/ibm/zvmmap/repository/images d. Run the following command to further verify that the IBM z/VM Manageability Access Point Agent installed successfully: /opt/ibm/icc/cimom/bin/cimcli ei IBMzVM_HostOperatingSystem You should see output that is similar to the following example: path= IBMzVM_HostOperatingSystem. 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.. After you install the IBM z/VM Manageability Access Point Agent.

Launch the IBM Systems Director VMControl program uninstallation file. Uninstalling IBM z/VM Manageability Access Point Agent You can use the mapuninstall command to uninstall the IBM z/VM Manageability Access Point Agent. enter the following command: . Run the following command: cd /var/opt/ibm/zvmmap/repository/images i. If a tar file was created. If a tar file was created. k. To uninstall IBM Systems Director VMControl. 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: 40 IBM Systems Director VMControl: Installation and User’s Guide . Run the following commands to start the Platform Agent services: /etc/init. h. Option Description AIX or Linux /opt/ibm/director/<VMControl_directory>/ uninstall/Uninstall Tip: To perform an unattended uninstallation. Note: If you want to use the wizard to uninstall from AIX and Linux. Follow the steps in the uninstallation wizard to uninstall IBM Systems Director VMControl. you can use the command line to perform an unattended uninstallation of IBM Systems Director VMControl. As an alternative. If a tar file was created. remove the tar file. enter the following command: uninstall.tar j. change to the directory /var/opt/ibm/zvmmap/ repository/images. Run the following command: tar -xf /var/opt/ibm/zvmmap/repository/images.d/tier1slpinst start /etc/init.d/cimlistenerd start /etc/init. you must launch the uninstallation program in a graphics-enabled session.d/ibmsa start /etc/init.d/cimserverd start Uninstalling IBM Systems Director VMControl You can uninstall IBM Systems Director VMControl from your environment./Uninstall -i silent Windows <VMControl_directory>\uninstall\ Uninstall.exe -i silent This launches the uninstallation wizard.exe Tip: To perform an unattended uninstallation. 2. extract the contents of the tar file. follow these steps: 1.

For information. Updating IBM Systems Director VMControl IBM Systems Director update manager plug-in enables you to acquire. you can view the updates on the IBM Systems Director Welcome page. After installing updates for IBM Systems Director VMControl. and deploy virtual appliances within your environment. you should see the following message: Removal of zVMMAP was successful v Uninstall IBM z/VM Manageability Access Point Agent and Platform Agent together: 1. you can relocate the repository now. When the uninstallation has completed successfully. Use the IBM Systems Director update manager plug-in to update IBM Systems Director VMControl.″ v Uninstall IBM z/VM Manageability Access Point Agent but keep Platform Agent running: 1. install. Managing workloads in your virtual environment With IBM Systems Director VMControl. Set the zVMMAP variable setting to “1”. If you want the repository to remain after you uninstall the IBM z/VM Manageability Access Point Agent. The following pieces to your IBM Systems Director VMControl environment must be in place for you to use the IBM Systems Director VMControl Image Manager Chapter 2. IBM Systems Director VMControl V2.1 41 . 3. 4. 2. see Updating IBM Systems Director. as well as to monitor your systems to ensure that they remain current. import. and manage updates. Open the /opt/ibm/director/bin/diruninstall script in an ASCII text editor. CAUTION: If the repository of virtual appliances has not been relocated from the default location. see the relocation step in ″Install the IBM z/VM Manageability Access Point Agent. Type the following command and press Enter: install_root/bin/diruninstall where install_root represents the root directory of your IBM Systems Director installation. Type the following command and press Enter: /opt/ibm/zvmmap/bin/mapuninstall 2. First you need to create an image repository. Save the modified diruninstall script. Related reference Commands Creating and discovering image repositories This topic provides information about how to set up your environment for IBM Systems Director VMControl. the repository and its contents will be permanently deleted when the IBM z/VM Manageability Access Point Agent is uninstalled. For more information about relocating the image repository. you can capture.

For more information. v Image repositories .For IBM Systems Director VMControl to be able to see the images in your repositories. Creating and discovering image repositories for NIM This topic provides information about how to set up your NIM environment for IBM Systems Director VMControl. v Discovery . v Agents .IBM Systems Director VMControl discovers your image repositories and views the images that are in them as virtual appliances. These agents are specific to your environment (NIM or z/VM). portion of the product. refer to the IBM Systems Director VMControl requirements for your specific environment. These pieces are shown in the following image: 42 IBM Systems Director VMControl: Installation and User’s Guide . you have to install agents on the repository systems.The images that are part of your virtual appliances are stored in image repositories that you create. There are several pieces to your IBM Systems Director VMControl environment that have to be in place for you to use the IBM Systems Director VMControl Image Manager portion of the product.

These pieces are shown in the following image: Chapter 2. Note: Before you install the agent software. Click Install Agents.1 43 . If you do not have an image repository. then you need to create one. There are several pieces to your IBM Systems Director VMControl environment that have to be in place for you to use the IBM Systems Director VMControl Image Manager portion of the product. and you must know the name of that host system. will be detected by IBM Systems Director VMControl Image Manager.″ 3.Follow these steps to get your environment ready for IBM Systems Director VMControl Image Manager: Note: The images shown in the image repository are not created automatically when a new repository is created. Related tasks Discovering systems and collecting inventory data Installing IBM Systems Director VMControl Image Manager subagent for NIM Network Installation Management Configuring the NIM master and creating basic installation resources Creating and discovering image repositories for z/VM This topic provides information about how to set up your z/VM environment for IBM Systems Director VMControl. 1.. to install the agent software. you must discover and request access to the host system (the NIM master). Ensure that you have at least one image repository that is suitable for the virtual appliances that you plan to import and deploy. Virtual appliances already present in your repositories. For more information. Images must be imported or captured after completing the following steps. IBM Systems Director VMControl V2. to discover your repositories and virtual appliances. that have been imported or captured using IBM Systems Director VMControl Image Manager. Ensure that the appropriate IBM Systems Director VMControl Image Manager agent software is installed on the system that hosts your image repository. see ″Installing IBM Systems Director VMControl subagent for NIM. Also..″ 2.. refer to the instructions for preparing and configuring the NIM master in ″Installing IBM Systems Director VMControl subagent for NIM. Additional virtual appliances can be added to your repositories by using the Import task in IBM Systems Director VMControl Image Manager. existing virtual servers and mksysb image files can be added to your repositories as virtual appliances by using the Capture task in IBM Systems Director VMControl Image Manager. Click Discover Virtual Appliances.. For more information.

Follow these steps to get your environment ready for IBM Systems Director VMControl Image Manager: Note: The images shown in the image repository are not created automatically when a new repository is created. 2. Images must be imported or captured after completing the following steps.″ 44 IBM Systems Director VMControl: Installation and User’s Guide . Ensure that you have at least one image repository that is suitable for the virtual appliances that you plan to deploy. The location of the image repository can be a symbolic link so that the repository is not removed when the z/VM manageability access point agent is removed. Click Discover Virtual Appliances. ensure that a sufficient amount of disk space is provided for the image repository. See the section below for details. Additional virtual appliances can be added to your repositories by using the Import and Capture tasks in IBM Systems Director VMControl Image Manager. to discover your repositories and virtual appliances. Refer to ″Installing the z/VM manageability access point agent″ to install the agent software. During the installation process. see ″Installing z/VM manageability access point agent. When providing disk space for the image repository. consider the size and number of the images that you plan to create. 1. then you need to create one. Images already present in your repositories will be detected by IBM Systems Director VMControl Image Manager and will be available to deploy as virtual appliances. you need to install the z/VM manageability access point agent.. You might have created an image repository when you installed the z/VM manageability access point agent. Creating an image repository for z/VM To create an image repository for z/VM.. Ensure that the appropriate IBM Systems Director VMControl Image Manager agent software is installed on the system that will host your image repository. If you do not have an image repository. For more information. 3.

stored on IBM Systems Director Server.0. 3. on your IBM Systems Director Server. IBM Systems Director VMControl can import virtual appliance packages that use the Distributed Management Task Force (DMTF) Open Virtualization Format (OVF). storing the virtual appliance it contains in IBM Systems Director. virtual appliance package A. typically with a . Virtual appliance A contains the metadata that describes the virtual server. The virtual appliance package can reside either on the Internet. Chapter 2. IBM Systems Director VMControl V2. which is a platform independent and open packaging and distribution format for virtual appliances. A user selects a virtual appliance package. or on a Web server that is accessible to your IBM Systems Director Server. virtual appliance A. You can import virtual appliance packages containing the following virtual server images: v AIX mksysb images for IBM POWER logical partitions v Linux on System z images for z/VM The following diagram shows how a virtual appliance package can be imported to create a new virtual appliance. For more information on OVF. 2. see the Open Virtualization Format Specification available from the DMTF Web site at: http://www.pdf The virtual appliance package can be in one of the following formats: v A set of files (called set-of-file format) v A single TAR file containing the same set of files. tested operating system and middleware and software applications. Image A contains a fully configured and tested operating system and software applications for the virtual server and is stored in an image repository. along with the metadata that describes the virtual server.dmtf. 4.0.ova extension.org/standards/published_documents/DSP0243_1. Importing virtual appliance package A results in a virtual appliance. Virtual appliance A is displayed in a list of virtual appliances that can be deployed into an environment. A virtual appliance package is a representation of a virtual server that contains a configured.1 45 . Related tasks Installing z/VM manageability access point agents Discovering systems and collecting inventory data Import The Import task enables you to import a virtual appliance package. and a reference to Image A. to import. 1. You can then deploy the virtual appliance into your data center.

Note: IBM Systems Director VMControl can recognize just one NIM master as an image repository. v IBM Systems Director VMControl has recognized the NIM master as an image repository in the environment. The following name and URI formats are supported: v [relativepath]file (any IBM Systems Director Server) v /localpath/file (IBM Systems Director Server on AIX and Linux only) v c:\localpath/file (IBM Systems Director Server on Windows only) v \\computername\path (IBM Systems Director Server on Windows only) v file://localpath/file (IBM Systems Director Server on AIX and Linux only) v file://c/localpath/file (IBM Systems Director Server on Windows only) v http://path/file (any IBM Systems Director Server) Power Systems requirements for import You can import a virtual appliance package when the following requirements are met: v A NIM master is running and is accessible by your IBM Systems Director Server. v There is sufficient space on the NIM master under /export/nim/appliances to store the AIX mksysb image file associated with the virtual appliance package that you want to import. multiple NIM Master image repositories are not supported. Requirements for import You can import a virtual appliance package if the virtual appliance package is accessible from the system on which the IBM Systems Director Server is running or can be accessed by using a URI. 46 IBM Systems Director VMControl: Installation and User’s Guide .

and a reference to Image A. A user selects a virtual server to capture. v The image repository is discovered in IBM Systems Director. Virtual appliance A is composed of metadata that describes the virtual server.3 or AIX 6. Related concepts “Creating and discovering image repositories” on page 41 Related tasks “Importing a virtual appliance package” on page 54 Related reference importva command “OVF specifications for IBM Systems Director VMControl” on page 112 Capture The capture task enables you to capture a virtual server or an existing AIX mksysb image file to create a virtual appliance. Virtual appliance A is displayed in a list of virtual appliances that can be deployed into an environment. 2. You can capture these types of virtual servers: v IBM Power Systems (POWER5 and POWER 6) virtual servers (logical partitions) running AIX 5. Image A contains the full operating system and software applications and is stored in an image repository. stored on IBM Systems Director Server. virtual server A. 4. 3. 1.1 47 . v The virtual appliance package that you want to import was created for z/VM by IBM Systems Director VMControl Capture or Import tasks. Chapter 2. virtual appliance A. You can then deploy the resulting virtual appliance to create a new virtual server that is complete with a fully functional operating system and software applications. z/VM requirements for import You can import a virtual appliance package when the following requirements are met: v The IBM z/VM Manageability Access Point Agent is installed on the System z host system where you want to store the imported virtual appliance package. IBM Systems Director VMControl V2. v There is sufficient space in the image repository to store the image associated with the virtual appliance package that you want to import.1 v z/VM virtual servers (z/VM guests) running Linux on System z The following diagram shows how a virtual server is captured to create a new virtual appliance. Capturing virtual server A results in a virtual appliance.

Power Systems requirements for capture

You can capture a Power Systems virtual server to create a virtual appliance in the
following environments:
v A virtual server (logical partition) on a Power Systems server that is managed by
Hardware Management Console (HMC) or Integrated Virtualization Manager
(IVM)
v A virtual server on a Power Architecture BladeCenter server that is managed by
IVM

You can capture a Power Systems virtual server when the following prerequisites
are met:
v A NIM master is running and able to access the virtual server over the network.
v IBM Systems Director VMControl has recognized the NIM master as an image
repository in the environment.

Note: IBM Systems Director VMControl can recognize just one NIM master as
an image repository; multiple NIM Master image repositories are not supported.
v There is sufficient space on the NIM master under /export/nim/appliances to
store the captured virtual server.
v The Hardware Management Console (HMC) or Integrated Virtualization
Manager (IVM) that manages the virtual server is discovered in IBM Systems
Director. Access status is listed as OK.
v The virtual server that you want to capture and the operating system running
on it is discovered in IBM Systems Director. Access status is listed as OK.
v The virtual server is up and running AIX version 5.3 or AIX version 6.1.

48 IBM Systems Director VMControl: Installation and User’s Guide

v The virtual server has at least one virtual Ethernet adapter.
v The virtual server is not a full system partition, or the only partition on the host
to which all host resources are dedicated.

z/VM requirements for capture

The following prerequisites must be met to capture a z/VM virtual server:
v An IBM z/VM Manageability Access Point Agent has been installed on a virtual
machine that runs in the same z/VM host as the target of the capture.
v The System z host system (the server on which IBM z/VM Manageability Access
Point Agent runs) has been discovered with IBM Systems Director. Access status
is listed as OK, and inventory is collected.
The discovery of the IBM z/VM Manageability Access Point Agent causes the
System z host to be discovered. Collection of inventory is performed against the
IBM z/VM Manageability Access Point Agent.
v The virtual server has been discovered with IBM Systems Director. Access status
is listed as OK, and inventory has been collected.
v The virtual server is running.
v The virtual server allows remote root logins.
v The z/VM manageability access point is able to establish an SSH connection to
the virtual server using the IP address used by the IBM Systems Director Server
to access the target system.
v The following RPMs are installed on the virtual server:
– perl-Compress-Zlib-1.42-1.fc6.s390x.rpm
– perl-libwww-perl-5.805-1.1.1.noarch.rpm
– perl-HTML-Parser-3.55-1.fc6.s390x.rpm
– perl-URI-1.35-3.noarch.rpm
– perl-HTML-Tagset-3.10-2.1.1.noarch.rpm
– perl-XML-Parser-2.34-6.1.2.2.1.s390x.rpm
v 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 volume used by a volume group containing a
volume listed in /etc/fstab

Note: You cannot capture a virtual server with an LVM system that has volume
group names or logical volume UUIDs that match, and therefore conflict with,
volume group names or volume UUIDs on the z/VM manageability access point.
Similarly, you cannot capture a virtual server that has been cloned from the z/VM
manageability access point.

IBM Systems Director VMControl captures one z/VM virtual server at a time.
Subsequent requests for capturing a virtual server are queued for processing.

Chapter 2. IBM Systems Director VMControl V2.1 49

Related reference
captureva command

Deploy
The deploy task enables you to deploy a virtual appliance to a new or existing
virtual server, or you can you simply create a new virtual server without an
operating system and other software. You can customize various attributes for the
resulting virtual server, such as network settings.

You can deploy virtual appliances that have been captured or imported into IBM
Systems Director VMControl to the following platforms:
v IBM® Power Systems servers (POWER5 and POWER6) that are managed by
Hardware Management Console or Integrated Virtualization Manager
v Linux on System z systems running on the z/VM hypervisor

The following diagram describes graphically how a virtual appliance is deployed
to create a new virtual server that is complete with a fully functional operating
system and software stack.
1. A user selects a virtual appliance to deploy, virtual appliance A, from the virtual
appliances that are stored on IBM Systems Director Server.
2. Virtual appliance A contains a reference to Image A that is stored in the image
repository. Image A contains an operating system and software applications.
3. The user specifies a host system or existing virtual server where he wants to
deploy virtual appliance A.
4. When virtual appliance A is deployed, virtual server A is created with the
definitions detailed in virtual appliance A. Or the user might have selected to
deploy virtual appliance A to the existing virtual server A, in which case virtual
server A is overwritten with the operating system and software applications
defined in virtual appliance A.

50 IBM Systems Director VMControl: Installation and User’s Guide

and inventory is collected for the HMC or IVM. multiple NIM Master image repositories are not supported. If the virtual server has an operating system installed. Chapter 2. it will be overwritten when the virtual appliance is deployed. v The NIM Master is able to access the target virtual server and the HMC or IVM that manages it over the network. You can deploy a virtual appliance to an existing virtual server when the following prerequisites are met: v The HMC or IVM that manages the target virtual server is discovered in IBM Systems Director. capture. Note: IBM Systems Director VMControl can recognize just one NIM master as an image repository.1 51 . Access status is listed as OK.Power Systems server requirements for deploy You can deploy a virtual appliance to create or overwrite a virtual server in the following environments: v A virtual server (logical partition) on a Power Systems server that is managed by Hardware Management Console or Integrated Virtualization Manager v A virtual server on a Power Architecture BladeCenter server that is managed by IVM Note: You cannot perform the deploy. or relocate tasks concurrently for the same AIX virtual server. v A NIM Master is running and is accessible by your IBM Systems Director Server. Wait until one of these tasks is complete before beginning another. v IBM Systems Director VMControl has recognized the NIM master as an image repository in the environment. IBM Systems Director VMControl V2.

v A supported storage configuration is available and discovered in IBM Systems Director: – SAN-based storage that is allocated from a storage pool hosted by the Virtual I/O Server. – Local storage that is allocated from a storage pool hosted by the Virtual I/O Server. See the Supported storage devices topic for a list of supported storage devices. You can deploy a virtual appliance to a new virtual server when the following prerequisites are met: v The Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM) that will manage the new virtual server is discovered in IBM Systems Director. 52 IBM Systems Director VMControl: Installation and User’s Guide . See the Supported storage devices topic for a list of supported storage devices. v IBM Systems Director VMControl has recognized the NIM master as an image repository in the environment. v The virtual server is not a full system partition. v A NIM Master has network access to the HMC or IVM that will manage the new virtual server. and any firewalls must be preconfigured to allow the virtual server to connect to the NIM Master. or add it to /etc/hosts on the NIM Master. v A supported storage configuration is available and discovered in IBM Systems Director: – SAN-based storage that is allocated from a storage pool hosted by the Virtual I/O Server. – Local storage that is allocated from a storage pool hosted by the Virtual I/O Server. multiple NIM Master image repositories are not supported. v The hostname for the primary and secondary network interfaces of the virtual server where you want to deploy the virtual appliance can be resolved from the NIM Master. Either define the hostname on the name server. or the only partition on the host to which all host resources are dedicated. System z and z/VM requirements for deploy On a System z host system that is running the z/VM hypervisor. Either define the hostname on the name server. You can also deploy a virtual appliance to a new or existing virtual server. you can deploy an empty virtual server to create a virtual server that does not include a virtual appliance. v The NIM Master is running and is accessible by your IBM Systems Director Server. Note: IBM Systems Director VMControl can recognize just one NIM master as an image repository. or add it to /etc/hosts on the NIM Master. and inventory is collected for the HMC or IVM. v The hostname for the primary and secondary network interfaces of the virtual server where you want to deploy the virtual appliance can be resolved from the NIM Master. Access status is listed as OK. v The virtual server that you plan to create must have network access to the NIM Master.

For any z/VM deployment. v Resources required for the image exist on the z/VM system. the directory manager supporting the z/VM system must be configured to allocate minidisk volumes with the Auto-Group option.1 53 .IBM Systems Director VMControl deploys one z/VM virtual server or virtual appliance at a time. v The virtual server that is the target of the deployment is powered off. You cannot deploy a virtual appliance to z/VM service machines with the following user IDs. for example: – Available network interfaces exist for use by the virtual server. v Inventory is collected for the images in the repository. IBM Systems Director VMControl V2. v Inventory of the images in the repository has completed. v The IBM z/VM Manageability Access Point Agent on the System z host system is discovered in IBM Systems Director. You can deploy or create an empty virtual server when the following additional prerequisite is met: v If you plan to deploy a virtual server that uses minidisks for storage. v A virtual server that meets the criteria specified in the image exists and has been discovered. the following prerequisites must be met: v The IBM z/VM Manageability Access Point Agent is installed on the z/VM host where the deployment is to occur. Access status is listed as OK. as described in the table: Chapter 2. the directory manager supporting the z/VM system must be configured to allocate minidisk volumes with the Auto-Group option. – If minidisks are required for virtual server storage. – Available volumes exist for use by the virtual server. Subsequent requests for deployment are queued for processing. and inventory is collected. the operating system will be overwritten. You can deploy a virtual appliance to create a virtual server when the additional prerequisites are met: v The IBM z/VM Manageability Access Point Agent contains a repository with images. Note: If you are deploying to an existing virtual server. You can deploy a virtual appliance to an existing virtual server when the following additional prerequisites are met: v The IBM z/VM Manageability Access Point Agent contains a repository with images.

From the IBM Systems Director VMControl Summary page. follow these steps: 1. The Import wizard can import virtual appliance packages containing the following virtual server images: v AIX mksysb images for IBM POWER logical partitions v Linux on System z images for z/VM To import a virtual appliance package. You can then deploy the virtual appliance into your data center. Table 5. click Import. 54 IBM Systems Director VMControl: Installation and User’s Guide . z/VM service machines that are restricted from the deploy task z/VM service machines restricted from deploy task v $ALLOC$ v BLDRACF v VSMPROXY v GSKADMIN v X25IPI v $DIRECT$ v BLDSEG v VSMREQIN v IMAP v 5VMRAC40 v $SYSCKP$ v CMS1 v VSMREQIU v IMAPAUTH v RACFSMF v $SYSWRM$ v CMSBATCH v VSMSERVE v LDAPSRV v RACFVM v $PAGE$ v DISKACNT v VSMWORK1 v LPSERVE v RACMAINT v $SPOOL$ v EREP v VSMWORK2 v MPROUTE v AUTOLOG2 v $TDISK$ v LGLOPR v VSMWORK3 v NAMESRV v IBMUSER v ROOT v MIGMAINT v ZVMMAPLX v NDBPMGR v SYSADMIN v DAEMON v MONWRITE v 4OSASF40 v NDBSRV01 v 5684042J v BIN v OP1 v OSADMIN1 v PORTMAP v 5VMRSC40 v SYS v OPERATNS v OSADMIN2 v REXECD v RSCS v ADM v OPERATOR v OSADMIN3 v RXAGENT1 v RSCSAUTH v NOBODY v OPERSYMP v OSAMAINT v SMTP v RSCSDNS v DEFAULT v SYSDUMP1 v OSASF v SNALNKA v XCHANGE v MAINT v SYSMAINT v 5VMTCP40 v SNMPD v 5VMDIR40 v AVSVM v SYSMON v TCPIP v SNMPQE v DATAMOVE v TSAFVM v VMRMADMN v TCPMAINT v SNMPSUBA v DIRMAINT v GCS v VMRMSVM v ADMSERV v SSLSERV v DIRMSAT v GCSXA v VMSERVR v DHCPD v TFTPD v 5VMPTK40 v AUDITOR v VMSERVS v DTCVSW1 v UFTD v PERFSVM v AUTOLOG1 v VMSERVU v DTCVSW2 v VMKERB v 5VMHCD40 v BLDCMS v VMUTIL v FTPSERVE v VMNFS v CBDIODSP v BLDNUC Related tasks “Deploying a virtual appliance or empty virtual server” on page 57 Supported storage devices Discovering systems and collecting inventory data Discovering and collecting inventory for storage devices Related reference “deployva command” on page 93 Importing a virtual appliance package You can use the Import wizard to import a virtual appliance package from the Internet or from other sources and store its component files to create a virtual appliance.

2. click OK to import the virtual appliance package immediately. 3. The following name and URI formats are supported: v [relativepath]file (any IBM Systems Director Server) v /localpath/file (IBM Systems Director Server on AIX and Linux only) v c:\localpath/file (IBM Systems Director Server on Windows only) v \\computername\path (IBM Systems Director Server on Windows only) v file://localpath/file (IBM Systems Director Server on AIX and Linux only) v file://c/localpath/file (IBM Systems Director Server on Windows only) v http://path/file (any IBM Systems Director Server) v repos://path/file (any IBM Systems Director Server) To capture the mksysb image file. specify the -F fileLocation option as shown: v From your IBM Systems Director VMControl NIM master image repository: -F repos://path/mksysb_filename Example: -F repos://images/nim/mksysb/favorite. to create a virtual appliance. You can also schedule this task for a later time. You can then deploy the virtual appliance into your data center. created with AIX or NIM commands. Related concepts “Import” on page 45 “Creating and discovering image repositories” on page 41 Related reference importva command “OVF specifications for IBM Systems Director VMControl” on page 112 “IBM Systems Director VMControl Import requirements” on page 6 Capturing an existing mksysb image file to create a virtual appliance You can capture an existing mksysb image file.mksysb Chapter 2.1 55 . IBM Systems Director VMControl V2. use the systems management command-line interface (smcli) captureva command as follows: smcli captureva [-L language] [-v] -r repository -n name -F fileLocation [-D description] [-A attribute_list] To capture the mksysb image file from the following locations. Follow the instructions in the Import wizard to import a virtual appliance package. In the Scheduler window. You can capture an existing mksysb image file from the following locations: v Your IBM Systems Director Server v Your IBM Systems Director VMControl NIM master v A Microsoft Windows server that is sharing the file (if your IBM Systems Director Server is a Windows system) v A Web server Note: You cannot capture an image from a secure Web server.

specify either of the following: – -F c:\path\mksysb_filename – -F file://c/path/mksysb_filename Examples: -F c:\tmp\mystuff\favorite.mksysb v From an image file being shared by another Windows server: -F \\server_name\path\mksysb_filename Example: -F \\othersvr\somepath\favorite. you have a virtual appliance that you can deploy into your environment. smcli captureva -r 1234 -F repos://images/nim/mksysb/favorite. You can further customize the virtual appliance when you use either the Deploy wizard or the deployva command to prepare the virtual appliance for deployment.mksysb. assigns the name MyFavoriteVA.1. from NIM master image repository 1234.mksysb v From your AIX or Linux IBM Systems Director Server. Tip: To see the valid values for attribute_list.mksysb -F file://c/tmp/mystuff/favorite.memsize=1024” Note: The value of memsize is in megabytes.1 CPUs and 4 GB of memory. 56 IBM Systems Director VMControl: Installation and User’s Guide . v From a Web server: -F http://path/mksysb_filename Example: -F http://www. favorite. specify either of the following: – -F /path/mksysb_filename – -F file://path/mksysb_filename Examples: -F /tmp/mystuff/favorite. smcli captureva -F c:\localpath\production. use the lscustomization command as follows: smcli lscustomization -a capture -r 1234 Examples: This example captures the existing mksysb image file. and specifies that the virtual server should have 2.mksysb.memsize=4096” This example captures the mksysb image file. the following default attributes will be used: -A “cpushare=1. production.acmeimages. from c:\localpath and assigns the name ProductionVA to the resulting virtual appliance.mksysb -F file://tmp/mystuff/favorite.mksysb -n ProductionVA After capturing the image.mksysb v From your Windows IBM Systems Director Server.0.mksysb -n MyFavoriteVA -A “cpushare=2.com/mksysb/favorite.mksysb If the-A attribute_list option is not specified.

3 or AIX 6. follow these steps: 1. click Deploy. Note: You can also access the Deploy wizard using the following methods: v In the Virtual Appliance view. 2. 3. You can also schedule this task for a later time. Chapter 2. In the Scheduler window.1 57 . The Deploy task is available for the following platforms: v IBM® Power Systems servers (POWER5 and POWER6) that are managed by Hardware Management Console or Integrated Virtualization Manager v Linux on System z systems running on the z/VM hypervisor 1. 2. 3. The wizard guides you through the deployment process. You can then deploy the virtual appliance into your data center. The Capture wizard can capture these types of virtual servers: v IBM Power Systems (POWER5 and POWER 6) virtual servers (logical partitions) running AIX 5.1 v z/VM virtual servers (z/VM guests) running Linux on System z To capture a virtual server. Complete the instructions in the Deploy wizard to deploy a virtual appliance or empty virtual server. Related reference captureva command Capturing a virtual server to create a virtual appliance You can use the Capture wizard to capture a virtual server to create a new virtual appliance. Follow the instructions in the Capture wizard to select and capture a virtual server to create a virtual appliance. IBM Systems Director VMControl V2. v In Resource Navigator. In the Scheduler window. Related reference captureva command Deploying a virtual appliance or empty virtual server You can use the Deploy wizard to deploy a virtual appliance or to deploy an empty virtual server (a virtual server without an operating system and other software). click OK to run the task immediately. From the IBM Systems Director VMControl summary page. click OK to capture the virtual server immediately. click Capture. You also can schedule to run this task at a later time. right-click a virtual appliance and select Deploy. right-click a host system or virtual server and select Deploy. From the IBM Systems Director VMControl summary page.

For more information. To delete a virtual appliance containing an AIX mksysb image. you can use features of IBM Systems Director to create. Deleting a virtual appliance You can delete a virtual appliance in a NIM or z/VM environment. complete the following steps: 1. 2. b. and delete them. Deleting a virtual appliance containing an AIX mksysb image: You can delete a virtual appliance containing an AIX mksysb image from IBM Systems Director VMControl manually by performing tasks in IBM Systems Director and running commands on your IBM Systems Director VMControl NIM master. c. Related concepts “Deploy” on page 50 Related tasks “Managing z/VM virtual servers” Related reference “deployva command” on page 93 “IBM Systems Director VMControl Deploy requirements” on page 9 Managing z/VM virtual servers Once you use IBM Systems Director VMControl to create a z/VM virtual server. Click virtual appliances. From your IBM Systems Director VMControl NIM master. For example.″ Related tasks “Deploying a virtual appliance or empty virtual server” on page 57 Editing virtual servers Deleting a virtual server permanently Managing virtual appliances Depending on the type of virtual appliances that you manage in your data center. deleting. click Actions from the menu bar. edit. From the IBM Systems Director VMControl summary page in the Web interface.file1. and modifying your virtual appliances. perform the following steps as the root user: 58 IBM Systems Director VMControl: Installation and User’s Guide . and select Related Resources → Software Image. you can use manual methods to perform tasks such as copying. if the software image name is 63dc39f0-a329-4696-bfb3-2851eca1350d. see ″Deploying a virtual appliance or empty virtual server. You will use the Appliance_ID that you identify in Step 2b on page 59.″ ″Editing virtual servers″ or ″Deleting a virtual server permanently. Select the virtual appliance that you want to delete. See the instructions for your environment. perform the following steps: a. the Appliance_ID is 63dc39f0-a329-4696-bfb3-2851eca1350d. Make note of the leading characters of the software image name that comprise the Appliance_ID. The Virtual Appliances page is displayed.

locate the virtual appliance to be deleted. The Virtual Appliances page is displayed. c. perform the following steps: a. Remove the mksysb resource for the virtual appliance from the NIM master using the following command: nim -o remove appliance-n_image-1 where appliance-n is the subdirectory name you noted in the previous step. Click virtual appliances. complete the following steps: 1. Make note of its ApplianceId property.) In the output. From the IBM Systems Director VMControl summary page in the Web interface. 3. b. Change to the appliances directory using the following command: cd /export/nim/appliances b. and click OK. Deleting a z/VM virtual appliance: You can delete a z/VM virtual appliance from IBM Systems Director VMControl manually by running commands from the IBM Systems Director systems management command-line interface and on the Linux system in which the IBM z/VM Manageability Access Point Agent is installed. Run the following command to list the virtual appliances and their properties: smcli lsva -l VA-197 ChangedDate:2009-06-08T18:22:05-05:00 Guid:1F5A2F5F13B53EEAA7031D6C6B6BCA97 SpecificationId:1 OID:6585 DisplayName:VA-197 Id:6585 ApplianceId:e250ed78-3101-4f32-b29d-373c7a4da0fd ObjectType:VirtualAppliance SpecificationVersion:1. Verify that the virtual appliance you removed is no longer displayed. specify the NIM master as the target. Remove the virtual appliance directory using the following command: rm -rf Appliance_ID where Appliance_ID is the appliance ID of the virtual appliance that you are deleting. the appliance ID that you noted in 1c on page 58.1 59 . c. perform the following steps: a. To delete a virtual appliance.8June b.1 Description:Linux 197. d. IBM Systems Director VMControl V2. Click Discover virtual appliances. List the contents of the directory of the virtual appliance that you want to delete using the following command: ls -l Appliance_ID where Appliance_ID is the appliance ID of the virtual appliance that you want to delete. look for the subdirectory named appliance-n (where n is an integer). Using the DisplayName property. a. and note this subdirectory name. From the IBM Systems Director systems management command-line interface. (See Step 1c on page 58. for example: Chapter 2.

However. as the target. Run the following command to change to the directory /var/opt/ibm/zvmmap/repository/images: cd /var/opt/ibm/zvmmap/repository/images d. perform the following steps: a. Copying a NIM virtual appliance: Since IBM Systems Director VMControl supports just one NIM master in the IBM Systems Director VMControl environment. and click OK. From the IBM Systems Director VMControl summary page in the Web interface. Click virtual appliances. e250ed78-3101-4f32-b29d-373c7a4da0fd 2. or you can copy a z/VM virtual appliance from one repository to another repository. b. Copying a virtual appliance You can copy a virtual appliance in a NIM or z/VM environment. e. Run the following commands to start the Platform Agent services: /etc/init. Log on as root. Copying a z/VM virtual appliance within the same repository: 60 IBM Systems Director VMControl: Installation and User’s Guide . b. /etc/init.d/tier1slpinst stop /etc/init.d/ibmsa stop c.d/tier1slpinst start /etc/init. Run the following command to remove the directory that corresponds to the software image name: rm -rf Appliance_ID where Appliance_ID is the appliance ID of the virtual appliance that you want to delete.d/cimlistenerd stop /etc/init. c. copying a virtual appliance from one NIM repository to another repository is not applicable. Verify that the virtual appliance you removed is no longer displayed. From the Linux system in which the IBM z/VM Manageability Access Point Agent is installed. or by capturing the same virtual server or existing mksysb image file multiple times.d/cimserverd start 3. Click Discover virtual appliances. The Virtual Appliances page is displayed. Run the following commands to stop the Platform Agent services. See the instructions for your environment.d/cimlistenerd start /etc/init.d/ibmsa start /etc/init. specify the Linux system in which the IBM z/VM Manageability Access Point Agent is installed. perform the following steps: a.d/cimserverd stop /etc/init. Copying a z/VM virtual appliance: You can copy a z/VM virtual appliance within the same repository. you can store multiple copies of the same virtual appliance in one NIM repository by importing the virtual appliance package multiple times.

Using the DisplayName property. for example: 28399609-2cbc-4ca3-8c63-191f808010fe e.Perform manual steps to copy a z/VM virtual appliance within the same repository. /etc/init.8June b. Run the following command to create the directory that corresponds to the appliance ID in your target repository: mkdir Target_Appliance_ID where Target_Appliance_ID is the UUID (appliance ID) that you generated in Step 2d. IBM Systems Director VMControl V2. Make note of its ApplianceId property. Run the following commands to stop the Platform Agent services. locate the virtual appliance to be copied.d/cimlistenerd stop /etc/init.d/tier1slpinst stop /etc/init. b. perform the following steps: a. Run the following command to change to the directory /var/opt/ibm/zvmmap/repository/images: cd /var/opt/ibm/zvmmap/repository/images d. Run the following command to list the virtual appliances and their properties: smcli lsva -l VA-197 ChangedDate:2009-06-08T18:22:05-05:00 Guid:1F5A2F5F13B53EEAA7031D6C6B6BCA97 SpecificationId:1 OID:6585 DisplayName:VA-197 Id:6585 ApplianceId:e250ed78-3101-4f32-b29d-373c7a4da0fd ObjectType:VirtualAppliance SpecificationVersion:1. From the IBM Systems Director systems management command-line interface. From the Linux system in which the IBM z/VM Manageability Access Point Agent is installed. perform the following steps: 1. f.d/ibmsa stop c. Run the following command to copy the contents of the directory that corresponds to the appliance ID in your source repository to the directory that corresponds to the appliance ID in your target repository: cp -rp Source_Appliance_ID/* Target_Appliance_ID Chapter 2. Run the following command to generate a UUID in canonical form to be used as the appliance ID of the target virtual appliance: uuidgen You should see the UUID for the target virtual appliance as the output.1 61 . for example: e250ed78-3101-4f32-b29d-373c7a4da0fd 2.d/cimserverd stop /etc/init. To copy a z/VM virtual appliance within the same repository. Log on as root.1 Description:Linux 197. perform the following steps: a.

Run the following commands to start the Platform Agent services: /etc/init.d/cimlistenerd stop /etc/init. From the IBM Systems Director systems management command-line interface.d/cimserverd stop /etc/init.d/tier1slpinst stop /etc/init. perform the following steps: a. The Virtual Appliances page is displayed. Click virtual appliances. To copy a z/VM virtual appliance from one repository to another repository. Copying a z/VM virtual appliance from one repository to another repository: Perform manual steps to copy a z/VM virtual appliance from one repository to another repository. Click Discover virtual appliances. From the IBM Systems Director VMControl summary page in the Web interface.1 Description:Linux 197.8June b. as the target. where Source_Appliance_ID is the appliance ID for the source virtual appliance and Target_Appliance_ID is the UUID (appliance ID) that you generated in Step 2d on page 61. perform the following steps: a. /etc/init. Run the following command to list the virtual appliances and their properties: smcli lsva -l VA-197 ChangedDate:2009-06-08T18:22:05-05:00 Guid:1F5A2F5F13B53EEAA7031D6C6B6BCA97 SpecificationId:1 OID:6585 DisplayName:VA-197 Id:6585 ApplianceId:e250ed78-3101-4f32-b29d-373c7a4da0fd ObjectType:VirtualAppliance SpecificationVersion:1. is displayed.d/tier1slpinst start /etc/init. Run the following command to change to the directory /var/opt/ibm/zvmmap/repository/images: cd /var/opt/ibm/zvmmap/repository/images 62 IBM Systems Director VMControl: Installation and User’s Guide . Log on as root.d/cimlistenerd start /etc/init. g. Using the DisplayName property. Run the following commands to stop the Platform Agent services. specify the Linux system in which the IBM z/VM Manageability Access Point Agent is installed. perform the following steps: a. Make note of its ApplianceId property. Verify that the virtual appliance you copied. b. for example: e250ed78-3101-4f32-b29d-373c7a4da0fd 2. b. perform the following steps: 1. From the source Linux system in which the IBM z/VM Manageability Access Point Agent is installed.d/cimserverd start 3.d/ibmsa stop c.d/ibmsa start /etc/init. locate the virtual appliance to be copied. c. and click OK.

IBM Systems Director VMControl V2.d/cimlistenerd stop /etc/init. e. f. Run the following command to create a tar file that contains the contents of the directory: tar -cf appliance.tar i.tar * 3. /etc/init. From the source Linux system in which the IBM z/VM Manageability Access Point Agent is installed. Run the following commands to stop the Platform Agent services. Transfer the tar file into the directory that corresponds to the appliance ID in your target repository. Log on as root.1 63 .d/cimserverd stop /etc/init.d/ibmsa stop c. g. h.tar j. Run the following command to change to the directory that corresponds to the appliance ID in your target repository: cd Target_Appliance_ID where Target_Appliance_ID is the appliance ID for the target virtual appliance. perform the following steps: a.d/tier1slpinst stop /etc/init. Run the following command to extract the contents of the tar file: tar -xf appliance.d/cimserverd start 4. perform the following steps: Chapter 2. Run the following command to create the directory that corresponds to the appliance ID in your target repository: mkdir Target_Appliance_ID where Target_Appliance_ID is the UUID (appliance ID) that you generated in Step 3d.d/cimlistenerd start /etc/init.d/tier1slpinst start /etc/init. From the target Linux system in which the IBM z/VM Manageability Access Point Agent is installed.d/ibmsa start /etc/init. for example: 28399609-2cbc-4ca3-8c63-191f808010fe e. Run the following command to change to the directory /var/opt/ibm/zvmmap/repository/images: cd /var/opt/ibm/zvmmap/repository/images d. Run the following command to change to the directory that corresponds to the appliance ID in your source repository: cd Source_Appliance_ID where Source_Appliance_ID is the appliance ID for the source virtual appliance. Run the following commands to start the Platform Agent services: /etc/init. b. d. Run the following command to remove the tar file: rm appliance. Run the following command to generate a UUID in canonical form to be used as the appliance ID of the target virtual appliance: uuidgen You should see the UUID for the target virtual appliance as the output.

specify the Linux system in which the IBM z/VM Manageability Access Point Agent is installed. Make a copy of the . Modifying a virtual appliance containing an AIX mksysb image You can manually modify the OVF descriptor for a virtual appliance that contains an AIX mksysb image by performing tasks in IBM Systems Director and running commands on your IBM Systems Director VMControl NIM master.tar b. and click OK. and click OK. b. the Appliance_ID is 63dc39f0-a329-4696-bfb3-2851eca1350d. 3. The Virtual Appliances page is displayed. Run the following commands to start the Platform Agent services: /etc/init. Select the virtual appliance that you want to modify. Click virtual appliances. c. For example. a. c. click Actions from the menu bar. perform the following steps: a. is displayed. Click virtual appliances. Verify that the virtual appliance you copied.) b. From the IBM Systems Director VMControl summary page in the Web interface. Change to the appliances directory and access the virtual appliance that you want to modify using the following command: cd /export/nim/appliances/Appliance_ID where Appliance_ID is the appliance ID of the virtual appliance that you want to modify. You will use the Appliance_ID that you identify in Step 2a. b.ovf file found in the /export/nim/appliances/ Appliance_ID directory. To modify the OVF descriptor for a virtual appliance that contains an AIX mksysb image. perform the following steps: a.file1.d/cimserverd start 5.d/ibmsa start /etc/init. From the IBM Systems Director VMControl summary page in the Web interface. (See Step 1c. Run the following command to remove the tar file: rm appliance.d/cimlistenerd start /etc/init. The Virtual Appliances page is displayed. 2.ovf file found in the /export/nim/appliances/ Appliance_ID directory and store it in a safe location. as the target. if the software image name is 63dc39f0-a329-4696-bfb3-2851eca1350d. perform the following steps as the root user: a. complete the following steps: 1. c. specify the NIM master as the target. Click Discover virtual appliances. Click Discover virtual appliances. Manually edit the . The Virtual Appliances page is displayed.d/tier1slpinst start /etc/init. in case you need to retract your changes. and select Related Resources → Software Image. From your IBM Systems Director VMControl NIM master. Make note of the leading characters of the software image name that comprise the Appliance_ID. Click virtual appliances. 64 IBM Systems Director VMControl: Installation and User’s Guide . b. perform the following steps: a. From the IBM Systems Director VMControl summary page in the Web interface.

master fileset installed. Backing up and restoring virtual appliances in NIM repositories To back up and restore the virtual appliances in a NIM repository. 3. use a compression tool such as Gzip. Your virtual appliance should be listed again. IBM Systems Director VMControl V2. try restoring the original . Tar and gzip the directories /tftp and /export/nim to create a tarball.gz. Run the following command to compress the tar file: gzip /usr/nimrf. Run the following commands to unzip and extract /usr/nimrf. 1. Verify that the virtual appliance you modified is still listed. 6. that you created on the backup system.tar. Note: If the virtual appliance is no longer listed. master. where master. select an AIX system that has the nim. Store nimrf.gz that contains the virtual appliances known to the NIM master. If you made changes to the name or description of the virtual appliance.gz. 4. Run the following command to create a tar file: tar -cvf /usr/nimrf. for example master.tar "/export/nim/appliances" tar -xf /usr/nimrf. smit nim_backup_db Using the SMIT interface.tar. c. Create a backup file of the NIM database using the SMIT interface.tar.gz and master.tar "/export/nim/appliances" "/tftpboot" where nimrf is the name that you want to assign to your virtual appliance backup. gunzip /usr/nimrf. Run the following command to create a backup. being particularly careful at step 2c on page 64 to make compliant changes only.tar "/tftpboot" 7. Make sure they are empty before continuing. Use the SMIT interface to restore the NIM database backup that you created. 5.gz tar -xf /usr/nimrf.tar c.bk on some other system for safe keeping.bk in this example. nimrf.ovf file that you saved in step 2b on page 64.bk. you can create a tar file of the virtual appliances. a.tar. If this happens. Create the /tftpboot and /export/nim file systems manually if they do not exist. but is not configured in any way. You can then try step 2 on page 64 again.bk is the name you assign to the virtual appliance backup. they should be reflected in the list. and the System Management Interface Tool (SMIT). To restore the backup to a different NIM master. b.ovf file have rendered it non-compliant and IBM Systems Director VMControl will not recognize it as a valid virtual appliance. using the following command: smit nim_restore_db Chapter 2. Perform the following steps to back up and restore the virtual appliances stored in a NIM master repository.tar. 2. Then retry step 3 on page 64. then your changes to the . for example.bk. create a backup such as to /etc/objrepos/master. Note: You must be logged on to the NIM master system as the root user to complete this procedure.1 65 . The result is /usr/nimrf.

Problem Installing IBM Systems Director VMControl multiple times might result in large numbers of temporary files and processes remaining in the temporary directory. Resolution If IBM Systems Director Server is in an Error state. The NIM repository and the restored virtual appliances should be discovered on the NIM master system where you restored the NIM database. Perform virtual appliance discovery. you can use the smstart command or restart IBM Systems Director Server to return IBM Systems Director Server to a normal state. 8. IBM Systems Director VMControl installer results in error state This problem affects IBM Systems Director VMControl running on an AIX management server. IBM Systems Director Server is now in an Error state. you selected to restart IBM Systems Director Server. there might be temporary files or processes left behind in the temporary directory. Problem While installing IBM Systems Director VMControl. Investigation You can check whether IBM Systems Director Server is in an error state by using the smstatus command. Resolution Delete the temporary files and stop the processes in the /tmp folder to free disk space on your system. The following topics contain information about known problems related to IBM Systems Director VMControl and how to resolve them: IBM Systems Director VMControl installer leaves processes behind After installing IBM Systems Director VMControl. These remaining files and processes can cause performance problems and use needed disk space. 66 IBM Systems Director VMControl: Installation and User’s Guide . Troubleshooting and support This topic provides troubleshooting information for IBM Systems Director VMControl.

Problem When installing IBM Systems Director VMControl subagent for NIM using the Agent Installation wizard. Explanation There might be several reasons for this error.1 67 . <director>/agent/logs/trace-log-0. You see the following additional Ensure that the system clocks on the systems information: CWPWS8461E: The message was that contain IBM Systems Director Server expired: creation date of timestamp. Chapter 2. The message describes why the installation failed. Causes for installation errors and resolutions Cause or additional information Resolution You see the following additional Sign on to the system on which you are information: Unable to complete action for installing IBM Systems Director VMControl feature VMControl NIM Subagent Feature subagent for NIM and check the due to errors. feature has already been installed. You see the following additional There are two possible resolutions: information: An unexpected deployment v Install IBM Systems Director VMControl engine exception occurred: The subagent subagent for NIM manually. rediscover it. Use the information in the following table to determine the cause of the error and solve the problem: Table 6. v Remove the agent system from IBM Systems Director Server. you receive one of the following error messages: v COPDEX040E: An unexpected deployment engine exception occurred. One possible reason is that you have not met all of the requirements for IBM Systems Director VMControl subagent for NIM. IBM Systems Director VMControl V2. Related reference smstatus command smstart command Subagent for NIM installation fails using Agent Installation wizard Use this information if you see an error when attempting to install the IBM Systems Director VMControl subagent for NIM using the Agent Installation wizard.xml error log for a message beginning with DNZIMN. v COPDEX123E: The workflow threw a MissingOperatingSystemException exception. and Common Agent remain synchronized. and install IBM Systems Director VMControl subagent for NIM using the Agent Installation wizard.

Resolution To correct this problem.1. To check if the CAS protocol is active. Problem When you attempt a manual installation of IBM Systems Director VMControl subagent for NIM. Problem You discover all of the z/VM virtual servers on a z/VM host system by discovering and requesting access to the IBM z/VM Manageability Access Point Agent. you see the following message: Requested operation cannot be performed because it would invalidate the current configuration. Table 6. Related tasks Updating IBM Systems Director Access state is Unknown for z/VM virtual servers after restarting IBM Systems Director Server This problem affects z/VM virtual servers on System z. Related tasks “Installing IBM Systems Director VMControl subagent for NIM” on page 19 Subagent for NIM installation fails when installing manually Use this information if you receive an error when attempting to install IBM Systems Director VMControl subagent for NIM manually. Click the All Operating Systems group. Click agent system.1. 4. and the appropriate access state is listed for each virtual server. Click Navigate Resources. Check if CAS appears next to Protocols. When you view the virtual servers in IBM Systems Director. Explanation This is a known limitation of IBM Systems Director VMControl Image Manager. you notice that the access state for each of the z/VM virtual servers is Unknown. and ensure that the CAS protocol is active for this system. ensure that the system you are installing the agent on has been updated to IBM Systems Director version 6. follow these steps: 1. 3. 2. Causes for installation errors and resolutions (continued) Cause or additional information Resolution You see the following additional Ensure that the agent system has the IBM information: Cannot find the operating Systems Director Common Agent installed system installed on device. You restart IBM Systems Director Server. The z/VM virtual servers are displayed in the IBM Systems Director Web interface.1. The IBM Systems Director Web interface indicates the incorrect access state of 68 IBM Systems Director VMControl: Installation and User’s Guide .

and collect inventory for the new NIM master. Then you can discover. discover. Multiple NIM master image repositories are not supported. For example. For more information. Unknown for z/VM virtual servers after restarting IBM Systems Director Server. and collect inventory for the new NIM master. request access. and delete your z/VM virtual servers. Resolution You can view the correct status for your z/VM virtual servers by running the following command in the IBM Systems Director systems management command-line interface: smcli lssys -v -n VirtualServerName -l where VirtualServerName is the name of your z/VM virtual server. and the task fails. deploy. Explanation IBM Systems Director VMControl can only recognize one NIM master as an image repository. you can refer to the State column in the Web interface to determine whether the virtual server is Started or Stopped.1 69 . To use a new NIM master. In addition. IBM Systems Director VMControl V2. you must remove both the Server and Operating System managed objects that represent the NIM master. capture. ensure that the new NIM master is properly configured. Chapter 2. Related tasks “Installing IBM Systems Director VMControl subagent for NIM” on page 19 Task fails after copying a scheduled job This problem affects any IBM Systems Director VMControl Image Manager task.″ Then. Resolution To remove a NIM master from the IBM Systems Director database. If you want to use a different NIM master as your image repository. Multiple NIM master image repositories not supported This problem affects IBM Systems Director VMControl when attempting to discover a NIM master image repository in an IBM® Power Systems environment. normal management functions through the Web interface are not adversely affected. see “Installing IBM Systems Director VMControl subagent for NIM. access. you can continue to use the Web interface to power on. However. Problem You try to discover a NIM master that is not currently configured to be the image repository for IBM Systems Director VMControl. power off. you need to first remove the current NIM master from the IBM Systems Director database.

or another user with authority to access the network share. To change the user to Administrator. To copy the job. you use the Create Like option under Active and Scheduled Jobs. as a set of files or as a compressed OVA. Resolution This is a known limitation of IBM Systems Director VMControl Image Manager. Problem After scheduling a task such as capture or deploy. Explanation By default. When the new scheduled job runs. Capture task fails with error DNZIMN018E or DNZIMN861E This problem affects the capture task when targeted to a IBM Power Systems (POWER5 and POWER 6) virtual server running AIX 5. Restart the IBM Systems Director Server service. this user does not normally have enough permissions to access a network share. even when the file exists: OVF File FileName not found. change the user from LocalSystem to Administrator. from IBM Systems Director Server that is running on Windows. The import task fails with the following error. complete the following steps: 1. The files to be imported are on a network share and the path is provided in UNC (Universal Naming Convention) format. where FileName is the name of the OVF package. 2. 70 IBM Systems Director VMControl: Installation and User’s Guide . \\computername\share\path. Do not run the task by copying the scheduled job. From the Windows Start menu. Explanation The required parameters are not being passed to the duplicate task.1. 4. 3. Right-click IBM Systems Director Server and select Properties. IBM Systems Director Server runs as a Windows service as user LocalSystem.3 or 6. On the Log On page. Problem You try to import an OVF package. open Control Panel → Administrative Tools → Services. Import from a network shared volume fails This problem affects the Import task on IBM Systems Director Server running on Windows. the task fails with a Null Pointer Exception error. Resolution Run IBM Systems Director Server as the Administrator user. you copy the job to create a duplicate scheduled job. for example.

Resolution If you are using LVM. Determine whether another capture or deploy task to the same virtual server was running when your task started. deploy. such as opt-vg. click Task Management → Active and Scheduled Jobs. or NIM mksysb task. Problem When capturing a z/VM virtual server. Capture task fails and indicates failure to access LVM volume group This problem affects the capture task when targeted to a z/VM virtual server. Explanation The capture task will not complete successfully on the target system if another operation. This can occur when default names or conventions are used. One of the following messages is displayed in the job log: v DNZIMN018E v DNZIMN861E Investigation Determine whether another operation is conflicting with your task and causing the problem. Problem When capturing a IBM Power Systems virtual server. by performing the following actions: v In the IBM Systems Director navigation pane.1 71 . Determine whether a mksysb task was running when your task started. the task fails. remember to do the following: v Do not try to capture a virtual server that has been cloned from the same source virtual appliance that was used to create the z/VM manageability access point. Resolution Wait until the pre-existing task is complete. IBM Systems Director VMControl V2. the task fails. For example. Then. Chapter 2. try the capture task again. is already running on that system. This can occur when both systems have volume groups that were cloned from the same source. such as a capture. v Look in file /var/adm/ras/nimlog on the NIM master. both systems might have volume groups with a generic name. Explanation This problem usually indicates one of the following issues: v The volume group on the system that is the target of the capture has physical volumes with UUIDs that are identical to the UUIDs of physical volumes on the z/VM manageability access point. An error message indicates that there is a failure to access an LVM volume group. v The name of the volume group on the system that is the target of the capture conflicts with the name of a volume group on the z/VM manageability access point.

you must connect it to such a network before performing the capture task. then create a key pair using ssh_keygen. the task fails. for example. for example.pub key file on the z/VM manageability access point. check the names of the volume groups on the z/VM manageability access point and ensure that you do not use these names for any other virtual servers that you might want to capture.ssh/ibm_zvmmap_id-rsa. if the capture target is on a different network than the z/VM manageability access point. v The capture target is missing proper credentials for recognizing and granting access to the z/VM manageability access point. Problem When capturing a z/VM virtual server. v If the capture target is not connected to a network that is accessible from the z/VM manageability access point. add an entry for the z/VM manageability access point to the authorized_keys file using the contents of the /root/. v Give the volume groups system-unique names.pub. edit /etc/ssh/sshd_conf on the capture target to permit them. v If the capture target is configured to reject SSH connections or remote root log-ins. v You can run the following script to accomplish several of the preceding troubleshooting steps: 72 IBM Systems Director VMControl: Installation and User’s Guide . Resolution Perform one or more of the following actions: v If the capture target is offline. Explanation This problem can occur for one of the following reasons: v The capture target is unreachable. IPL the capture target and ensure that it completes the boot process. or in a non-networked run-level. v Remove any lines for the capture target from the known_hosts file on the z/VM manageability access point. v If the z/VM manageability access point does not have a key pair for ibm_zvmmap_id_rsa / ibm_zvmmap_id_rsa. Or. Then. Capture task fails and indicates SSH connection problems This problem affects the capture task when targeted to a z/VM virtual server. v The capture target is configured to reject root log-ins through SSH. if the capture target fails to boot properly and start up network services. v The capture target is unresponsive. v Remove any lines for the z/VM manageability access point in the authorized_keys file on the capture target. An error message indicates that an SSH connection to the capture target could not be established.

#!/bin/bash ############################################################################### # Adds the /root/. cd /root/.ssh # Create a "zvmmap" RSA key if one doesn't already exist. sed -i \"/. a Linux virtual server on System z. Problem When capturing from. # # # # @param $1: The IP address or hostname of the remote server to be accessed. if [[ ! -f /root/. sed -i "/^${remote_server}/d" known_hosts # Remotely touch the remote server's authorized_keys file to make sure it will # be there.*${hostname}$/d\" authorized_keys. Chapter 2. or deploying to. echo \"${key}\" >> authorized_keys" # Test the connection. key="$(cat ibm_zvmmap_id_rsa. ssh -i ibm_zvmmap_id_rsa \ -o BatchMode=yes \ -o ConnectTimeout=60 \ -l root $remote_server \ 'echo "SSH Connection Successfully Established"' # Go back to original directory. the job hangs indefinitely. a Linux virtual server on System z. cd /root/.ssh.ssh/ibm_zvmmap_id_rsa ]]. or deploying to. # ############################################################################### ##### START EXECUTION ######################################################### remote_server=$1 hostname=$(hostname) # Go to root's . then ssh-keygen -t rsa -N '' -f ibm_zvmmap_id_rsa fi # Remove the remote server from the "known hosts" file to make sure there are # no old and incorrect entries for that server. and append this # host's public key to the remote server's authorized_key file.ssh directory. This problem can occur when using either the IBM Systems Director Web interface or the IBM Systems Director systems management command-line interface. touch authorized_keys.1 73 .ssh/ibm_zvmmap_id_rsa. IBM Systems Director VMControl V2.pub)" ssh root@${remote_server} "mkdir /root/.pub ssh public key to remote_server's # # authorized_keys list. remove any existing key entries for this host.ssh. cd - exit 0 ##### END OF SCRIPT ########################################################### Capture or deploy of virtual server hangs This problem affects the capture or deploy task when capturing from.

using a different hostname. Log on to the NIM master as root user. complete the following steps: 1. Resolution To resolve the problem. 2. Run the following shell command to remove any lock files that were left behind: rm /tmp/disk_connection_lock /tmp/ovftool_metalock /tmp/ovftool_lock_* Capture task fails with error DNZIMN018E This problem affects the capture task when targeted to an IBM® Power Systems (POWER5 and POWER6) virtual server running AIX 5. but not deleted. In the Web interface. 74 IBM Systems Director VMControl: Installation and User’s Guide . Explanation This problem can occur if the machine you are trying to capture was previously deployed or captured. by a previous capture or deploy job that stops abruptly. When you attempt to capture the machine using a different hostname. Explanation The capture or deploy task can hang when a lock file is created. or due to a crash or forced shutdown of the virtual server on which the IBM z/VM Manageability Access Point Agent was running. Resolution Complete the following steps to remove the existing NIM machine object from the NIM master manually. 1.d/cimserverd stop 3. Problem When you try to capture a virtual appliance from a Power Systems virtual machine. check the properties of the machine that you are attempting to capture. 2. the task fails with the following message displayed in the job log: DNZIMN018E Could not define a NIM client for the specified server with object ID (OID) <OID>. Log on to the z/VM manageability access point system. Then you can attempt to capture it again. 3. For example.d/ibmsa stop /etc/init.3 or 6. this problem can occur when the previous job is stopped manually. a new NIM machine object cannot be created because the existing machine object already has the same MAC address. Locate the MAC Address property.1. Run the following commands to stop the IBM z/VM Manageability Access Point Agent: /etc/init. NIM cannot store two machines with the same MAC address. Run the following command to find out the name of the machine that has the same MAC address: lsnim -a if1 -t standalone The output lists the machine that you need to remove.d/tier1slpinst stop /etc/init.d/cimlistenerd stop /etc/init.

4. Problem A Red Hat Enterprise Linux server fails to boot after it is deployed. Capture from file fails when using HTTP protocol This problem occurs when you attempt to capture an image file that is larger than 2.6: cannot open shared object file: Permission denied Explanation This problem can occur when the Red Hat Enterprise Linux server that fails to boot was captured from a system with Security-Enhanced Linux (SELinux) enabled. Explanation This problem occurs when you attempt to capture an image file that is larger than 2. or upgrade the star installation on the z/VM manageability access point to version 1.5 (final). SELinux denies access to these files.483.so. Problem When you attempt to capture an image file using HTTP protocol. In addition. Resolution Download the image file to disk using a Web browser or some other means.1 75 . a getContentLength error occurs.647 bytes using HTTP protocol. IBM Systems Director VMControl V2. Resolution Either disable SELinux on the capture target by setting it to permissive mode in the /etc/selinux/config file. specifying the image from the disk location Red Hat Enterprise Linux server fails to boot after deploy and shows permission errors for shared libraries This problem affects the Red Hat Enterprise Linux server after it has been deployed. When the NIM machine is removed. Consequently.483. Try the capture task again. Chapter 2. you can attempt the capture task again. an error similar to the following example is displayed: /bin/mingetty: error while loading shared libraries: libc.147. Old versions of the star command contain a bug that prevents the extended attributes for soft links from being correctly written on deploy.647 bytes using HTTP protocol. through a z/VM manageability access point on which an old version of the star command was installed.147. Run the following commands to remove the NIM machine from the NIM master: nim -Fo reset <name of the NIM machine object that you want to remove> nim -Fo deallocate -a subclass=all <name of the NIM machine object that you want to remove> nim -Fo remove <name of the NIM machine object that you want to remove> 5.

locate the task activation log for the deploy task. Resolution Scenario 1 The virtual server was created. 1.” then there was an error in the process to create the virtual server or allocate storage resources to it. and then click the Logs tab. In the navigation area. In these error cases the virtual server or allocated resources remain on the HMC or IVM. does the task activation log contain an error message between DNZVMP050E and DNZVMP070E? v If you used the deployva command. you can remove the virtual server and associated storage resources. expand Inventory → Views → Virtual Servers and Hosts. In this case the virtual server is provisioned. If you attempt the deploy task again and the errors keep happening. Problem When you use the deploy to new virtual server task. Investigation If you used the Deploy wizard in the Web interface. click Task Management → Active and Scheduled Jobs. It should be removed along with its associated storage resources. Look for the virtual server on the host that was the target of the deploy task. Scenario 1 v If you used the Deploy wizard. The instructions are different based on the messages in the activation log. but IBM Systems Director did not receive notification about the new virtual server in the required time. Select your Deploy job. You should remove the virtual server and associated storage resources. Alternately. and you can deploy images to it. In the navigation area. If 76 IBM Systems Director VMControl: Installation and User’s Guide . does the task activation log contain the DNZIMN104E error message? v If you used the deployva command. but is unusable for deploy. In this case the virtual server and associated storage resources were not configured such that an image can be deployed. you might receive errors from the HMC or IVM as it performs the steps to create the virtual server and allocate resources to it. did you receive the DNZIMN104E error message? If you answered “Yes. did you receive an error message between DNZVMP050E and DNZVMP070E? If you answered “Yes. Deploy virtual server failures leaves resources allocated This problem affects the deploy to new virtual server task when targeted to a host system that is managed by Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM). Scenario 2 v If you used the Deploy wizard. The allocated resources are not deleted when the errors occur. This topic addresses two error scenarios. you will eventually run out of resources on the HMC or IVM.” then the virtual server and associated storage resources were successfully created.

Perform the deploy to existing virtual server task on the virtual server. If it doesn’t appear in 5 minutes. 4. click Inventory → Views → Platform Managers and Members. then in the Web interface. Select the host in Navigate Resources. Find the Storage Pools in the view. you don’t see it. Refer to the “Finding the storage volume allocated in the SAN“ in the Additional Information section for the steps to remove this volume. then select Topology → Storage. v If you used the Deploy wizard and there is a DNZVMP546I message in the task activation log. then continue to step 3. then the DNZVMP546I message contains the name of the virtual disk that was allocated. then perform the Security → Verify Connection (query vital properties) task on the HMC or IVM. Scenario 2 The virtual server was created along with the associated storage resources. Perform steps 2-3 of Scenario 1. v If you used the deployva command. If you selected a storage pool local to the Virtual I/O Server. select the host in Navigate Resources and perform the System Configuration → Edit Host task. 1. 2. In the resulting table of storage volumes. If you selected a storage pool located on a SAN. Wait for the virtual server to appear. and select the Pool where the volume was allocated. Perform the Permanently Delete Virtual Server task on the virtual server. No. On the selected Storage Pool: Related Resources → Storage Volume. To find the storage pools click Navigate Resources → All Systems. Refer to the “Finding the storage volume allocated in the SAN“ in the Additional Information section for the steps to remove this volume. Additional information Complete the following steps in Navigate Resources to find the storage volume allocated in the SAN: 1. then do the following: a. click Actions → Columns to add the Change Date column Chapter 2. Do you want to remove the virtual server and associated storage resources? a. 2. 5. 2. Look for the host system that was the target of the deploy task. Remove unassigned virtual disks until enough pool space is freed. You are done. You can either finish the image deploy by using the deploy to existing virtual server task. b. If you selected a storage pool located on a SAN. then the DNZVMP564I message gives the pool name where the storage volume was allocated. complete the following steps: a. and perform the System Configuration → Edit Host task to delete the virtual disk. then retrieve the storage pool name from the command line invocation. If you selected a storage pool local to the Virtual I/O Server.1 77 . Switch to the Resource View. or remove the virtual server and associated storage resources. Perform the Inventory → View and Collect Inventory → Collect Inventory (all inventory) task. 3. b. Yes. b. IBM Systems Director VMControl V2. In the navigation area of the Web interface. Remove any virtual disk that was allocated to the virtual server. select all Storage Arrays. 3.

Perform the Configuration → Manage Profiles task to edit the profile. For each Virtual I/O Server partition on the server. (See step 5. a. 5. On the Virtual Adapters tab. Any entry with a number in parentheses. b. but no partition name.) 4. 3. This is needed to remove the vhost (if any) in the steps below. which is the incorrect error message for the failure. and perform Operations → Perform VIOS Command. complete the following steps 1) Select the Virtual I/O Server partition. The following steps should be performed for each virtual SCSI server adapter to be removed. To remove any vhost device that was configured to use the removed adapter. Select the virtual SCSI server adapter to be removed. compare “Maximum virtual adapters” with “Number of virtual adapters. 6. c. and perform Actions → Delete. 78 IBM Systems Director VMControl: Installation and User’s Guide . Select the server that was the host system targeted by the deploy task. You are done for this Virtual I/O Server. Choose the storage volume with the change date at approximately the same time as the Deploy task was performed. Resolution Log on to the HMC Web console. look in the Connecting Partition column for the Server SCSI rows. 2. This is the virtual slot number of this adapter. View the partitions on this server.” If the number of virtual adapters equals the maximum then this Virtual I/O Server has no available virtual slots. The deploy to new virtual server task attempts to configure virtual SCSI on the Virtual I/O Server to make volumes available to the new virtual server. This topic explains the actual error and the resolution steps. Record the number in the Adapter ID column of the virtual SCSI server adapter to be removed. On the Virtual Adapters tab. and select System Management → Servers to view the servers. This involves allocating virtual SCSI server adapters in available virtual slots on the Virtual I/O Server. Investigation The most likely cause of the DNZVMP001E message is that one of the Virtual I/O Server partitions had no available virtual slots. Close the profile to save the changes. is a virtual SCSI server adapter that can be removed to free up a virtual slot. Problem The deploy image to new virtual server task might receive a DNZVMP001E error message. 2) Specify the lsmap –all command. you can increase the “Maximum virtual adapters” value instead. complete the following steps: 1. Perform the Remove task on this volume. If you don’t find virtual SCSI server adapters to remove. Restart the Virtual I/O Server partition after doing this. Deploy image to new virtual server fails with error DNZVMP001E This problem affects the deploy to new virtual server task when targeted to a host system that is managed by Hardware Management Console (HMC).

The number X in CX at the end of the vhost identifier is the virtual slot number. The Physloc column contains the virtual slot number of the virtual SCSI server adapter used by the vhost. you select a target system and receive the following error: DNZIMN107E: An error occurred during the deploy operation. For example. For more information. 4) If you find the virtual slot recorded above in output of the lsmap command. the SSH key exchange fails. When you are done removing all the virtual SCSI server adapters and the corresponding vhost devices. 5) Run the following command using the Perform VIOS command task: rmdev –dev vhostX where vhostX is the vhost that you identified in the previous step. such as the Hardware Management Console (HMC).12. You can use the dkeyexch command to exchange the key on other access points. This indicates that the vhost0 device is using the virtual SCSI server adapter in virtual slot 2.87 due to the following error: 2760-287 [dkeyexch] Internal error .28.exchange script returns unknown error: 1. 3) In the output.12. Resolution Rerun the dkeyexch command on your NIM master to exchange the SSH keys. Chapter 2. then you can use the Dynamic Logical Partitioning → Virtual Adapters task to remove the virtual SCSI Server adapter from the running Virtual I/O Server partition.1 79 .87 In this example. Problem During the deploy operation.55A. d. Deploy task fails with error DNZIMN107E This problem affects IBM Systems Director VMControl when attempting to deploy a virtual server in an IBM® Power Systems environment. Here is an example of running the dkeyexch command for the error shown: /opt/ibm/sysmgt/dsm/bin/dkeyexch -z -f /etc/ibm/sysmgt/dsm/config/passwd_9_12_28_87 -I ivm -H 9. restart the Virtual I/O Server partition.10DA01G-V1-C2 contains C2 at the end. then record the vhost for that virtual slot. IBM Systems Director VMControl V2. Problem When you are using the Deploy wizard to deploy a virtual appliance in a Power Systems environment. a row such as vhost0 U9133. you are exchanging the SSH key on an Integrated Virtualization Manager (IVM) access point. look at the Physloc column for each vhost device. Deploy task fails with error DNZIMN867E This problem affects IBM Systems Director VMControl when attempting to deploy a new virtual server in an IBM® Power Systems environment.28. see the man page for the dkeyexch command. The dkeyexch command returns an unknown status and you receive an error similar to the following: DNZIMN867E Could not exchange SSH key with 9. If you do not want to restart the Virtual I/O Server.

the Product panel of the Deploy wizard does not contain any fields that you can edit. To avoid the lock timeout. Problem When you attempt to deploy a virtual appliance that is in a NIM repository. you can attempt the deploy task again. These properties are: <ovf:Property ovf:key="networkport. Related tasks Collecting inventory Multiple deploy tasks cause DNZIMN871E error This problem affects deploy tasks that are targeted to Power Systems servers that are managed by Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM). Resolution This error can occur when IBM Systems Director has not completed the inventory collection process for the target system. or you can explicitly perform the collect inventory task on the target system. When inventory collection is complete for the target system. you receive the following message: DNZIMN871E Another operation is in progress. Explanation Some deploy tasks fail when multiple deploy tasks are scheduled simultaneously to partitions that are managed by the same HMC or IVM. The NIM deploy requires three properties to be set in the top level product section of the OVF. Problem When attempting to use the deploy task to target a system that is managed by HMC or IVM. Product panel of Deploy wizard is blank This problem is encountered when attempting to deploy a virtual appliance that is in a NIM repository.RASDID. Explanation The OVF for the virtual appliance does not contain a Product section with user editable properties. you receive the following error DNZIMC706E An unexpected error has occurred. schedule the deploy tasks to be 5 to 10 minutes apart so that the NIM master can complete its processing.gateway" ovf:type="string" 80 IBM Systems Director VMControl: Installation and User’s Guide .RASDID.ip" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Static IP address for the network adapter</ovf:Label> <ovf:Description>Static IP address for the network adapter</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport. See the error log for more information. You can either wait for the process to complete. When you click Finish and complete the wizard. Unable to lock HMCName for deployment. Resolution A lock timeout may occur if too many deploy tasks are scheduled concurrently for a given HMC or IVM.

and connects to the virtual server where you plan to deploy the virtual appliance through a different network adapter.</rasd:ElementName> <rasd:InstanceID>6</rasd:InstanceID> <rasd:ResourceType>10</rasd:ResourceType> <rasd:VirtualQuantity>1</rasd:VirtualQuantity> </ovf:Item> The OperatingSystemSection of the virtual system must also have the DiscoveryIpAddress and NetworkBootIpAddress set to reference the IP address property from the product section.ibm. for this RASD item the RASDID should be replaced with “6”: <ovf:Item> <rasd:Caption>Virtual Ethernet Adapter Allocation</rasd:Caption> <rasd:Connection>Virtual Network 1</rasd:Connection> <rasd:Description>Virtual Network 1</rasd:Description> <rasd:ElementName>Allocation of non-IEEE-aware virtual ethernet adapter on Virtual Network 1.1 81 . you receive the following error: DNZIMN882E The deploy task is not progressing and has timed out. IBM Systems Director VMControl V2. ovf:userConfigurable="true"> <ovf:Label>Static default gateway. For example.ovf.2" vim:instance="" vim:key="networkport.RASDID.netmask" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Static network.ip"/> <vim:NetworkBootIpAddress vim:class="com. Chapter 2.ibm.2" vim:instance="" vim:key="networkport.RASDID. Deploy to existing virtual server task times out This problem affects the deploy to existing virtual server task when you are deploying a virtual appliance from a Network Installation Management (NIM) image repository. the secondary adapter might not be configured correctly.ip"/> </ovf:OperatingSystemSection> </ovf:VirtualSystem> Resolution The original OVF should be modified so it contains the required properties and then be re-imported.</ovf:Label> <ovf:Description>Static default gateway.ovf. For example: <ovf:OperatingSystemSection ovf:id="9" ovf:version="6"> <ovf:Info>AIX 6 Guest Operating System</ovf:Info> <ovf:Description>IBM AIX 6</ovf:Description> <vim:DiscoveryIpAddress vim:class="com.</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.</ovf:Description> </ovf:Property> The RASDID should be substituted with the instance ID of the RASD item in the OVF that represents the main network adapter of the system.vim.vim. Explanation If the NIM image repository (NIM Master) connects to IBM Systems Director Server through one network adapter. Problem When attempting to deploy a virtual appliance from a NIM repository to an existing virtual server.</ovf:Label> <ovf:Description>Static network.RASDID.

2.255. or add it to /etc/hosts on the NIM Master.0 is the subnet mask for the network. 255.0 deploy_net where 2. 255.4 -a snm=255.2.2. If the virtual server that you will be deploying is on the same network as the NIM Master’s secondary interface.255.3.255. 3. Define a NIM network object for the NIM Master’s secondary network interface.3. For example: nim -o define -t ent -a net_addr=2. 2. When you have completed these steps.2. 82 IBM Systems Director VMControl: Installation and User’s Guide .0 secondary_net where 1.4 is the IP address of the network being defined. For example: nim -o define -t ent -a net_addr=1. and secondary_net is the NIM network object name that you are creating. You should also remove the default route on the deploy_net network. Log on to the NIM Master. a static route must be established between it and the secondary_net network object.255.4 0' -a cable_type2=N/A master 4. then skip this step. If it is on a different network. 5.3. If you created a new deploy_net network. Ensure that the hostname of the virtual server where you want to deploy the virtual appliance can be resolved from the NIM Master. Either define the hostname on the name server.3. If the NIM Master has a secondary interface that you will be using to deploy virtual servers. Note: Do not define a NIM network object name that begins with the name of another NIM network object.4 -a snm=255. Attach the secondary_net network object you created to the NIM Master resource. then you must define another NIM network object for the virtual server.4 is the IP address of the network being defined. b. Resolution Complete the following steps to create a secondary NIM network resource and configure NIM to use this secondary adapter: 1.For more information.255. see the Defining NIM networks topic in the IBM Systems Information Center. see the Establishing a static NIM route between networks topic in the IBM Systems Information Center. a. attempt to deploy the virtual appliance to the virtual server again.255.255. When you ran nim_master_setup to configure your NIM Master. then you will need to create one or more additional NIM network definitions.3.0 is the subnet mask for the network. the master_net network object was created for you to represent the network associated with the NIM Master’s primary network interface.255.2. For more information. for example: nim -o change -a if2='secondary_net 1. and deploy_net is the NIM object name that you are creating.

you receive the following error: DNZIMN882E The deploy task is not progressing and has timed out. the DNZIMC763E message is displayed on the Minidisks page. 3. Resolution Complete the following steps: 1. Explanation IBM Systems Director VMControl populates the Deploy wizard with values from the source virtual server or virtual appliance. Problem When you use the Deploy wizard to deploy a virtual appliance or an existing virtual server to create a new z/VM virtual server. Alternatively. to serve as the image repository. Explanation The deployment of a new AIX virtual server fails if the server does not have network connectivity to the NIM Master. However. Related tasks Defining NIM networks Establishing a static NIM route between networks Related reference “Deploy to new AIX virtual server task times out” Deploy to new AIX virtual server task times out This problem affects the deploy to new virtual server task when you are deploying a virtual appliance from a Network Installation Manager (NIM) image repository. IBM Systems Director VMControl V2. or if the virtual server cannot get thorough a firewall to the NIM Master. Ensure that there is network connectivity between the virtual server and the NIM Master. you need to provide additional information about the minidisks that will be created for the new virtual server. 2.1 83 . Ensure that any firewalls between the virtual server and the NIM Master are configured to allow the virtual server to communicate with the NIM Master. Problem When attempting to deploy a virtual appliance from a NIM repository to a new virtual server. you can choose a different NIM Master that is within the same firewall as the virtual server. Related reference “Deploy to existing virtual server task times out” on page 81 Deploy wizard displays error DNZIMC763E on Minidisks page This problem affects the deploy task when you are deploying a virtual appliance or an existing virtual server to create a new z/VM virtual server. Retry the deploy task after the network and firewall have been configured correctly. Chapter 2.

continue using the Deploy wizard. Repeat steps 1-3 for each minidisk listed in the table. then the IP address takes precedence. Resolution Specify the appropriate size for the minidisk that is being created. IBM Systems Director shows this as negative one (-1) for the size. for example. complete the following steps: 1. select the ID. If the IP address and hostname do not map to one another through DNS or /etc/hosts on the NIM master. you can specify both an IP address and a hostname for the target virtual server. In the Disk ID field. Explanation When using the Deploy wizard or the command-line interface. Explanation The negative one (-1) for the size of the minidisk indicates that the minidisk is using the remaining space on the volume. In the Disk Allocation Type field. When creating a minidisk for a virtual server. select the type. complete the following information for the minidisk that will be created for the new virtual server: a. Problem When you deploy a virtual appliance in a Power Systems environment. z/VM indicates this in the user directory as END. Problem The size of a minidisk is shown as -1 in the minidisk panel when deploying an empty virtual server based on an existing z/VM server. 2. Then. 4. The size of the minidisk must be changed to a different size before creating the new virtual server. In this situation. z/VM minidisk size is -1 when deploying This problem affects the deploy new virtual server task when it is based on an existing z/VM virtual server. b. On the Edit Minidisk page. 3. you notice that the new (target) virtual server does not have the new hostname that you specified in the Deploy wizard or the command-line interface. a valid size is required. query 191. select one of the minidisks and click Edit. the hostname for the 84 IBM Systems Director VMControl: Installation and User’s Guide . Deploy task creates new virtual server with incorrect hostname This problem affects IBM Systems Director VMControl when deploying a virtual appliance in an IBM® Power Systems environment. Click OK to return to the Minidisks page. Log on the virtual machine and query the device. Negative one is not accepted. From the Minidisks page. Resolution To resolve the problem.

Unable to edit virtual server properties related to virtual CPU This problem affects the edit task when targeted to a z/VM virtual server. IBM Systems Director VMControl V2. This problem occurs on a virtual server that does not have a CPU statement in the z/VM user directory entry for the virtual server. Resolution On z/VM use the directory manager to add a CPU statement to the user directory for the virtual server. the virtual processors do not indicate that a processor is dedicated. The modification did not occur. The IBM z/VM Manageability Access Point Agent attempted to modify the CPU statement and one did not exist. Resolution Ensure that the IP address and the hostname that you specify in the Deploy wizard or command-line interface resolve to one another in DNS or /etc/hosts on the NIM master. When the CPU statement is added to the user directory for the virtual server. Explanation The property indicating that the virtual processor is dedicated is not returned with the proper value. Problem When you attempt the edit virtual server task for the stored settings of a System z virtual server to change the dedicated/shared property. an error can occur indicating that the modification failed. Explanation A CPU statement is not required in the z/VM user directory for a user if the system has only one virtual CPU defined and it is defaulting to shared virtual processors. Resolution This is a current known limitation.1 85 . the IBM z/VM Manageability Access Point Agent can modify the CPU statement. Virtual server processors are not marked dedicated This problem affects the create virtual server and edit virtual server task when targeted to a System z virtual server. The value is always shown as not dedicated. Chapter 2. new virtual server does not change to the name you specified in the Deploy wizard or command-line interface. Problem When editing a System z virtual server or creating a new virtual server based on an existing virtual server.

the minidisks associated with the virtual server are attempted to be modified. Explanation The minidisk modification attempt occurs because of a difference between the active and stored settings for the minidisks. Editing virtual server to add virtual switch or guest LAN results in error This problem affects the edit virtual server task when it is targeted to a System z virtual server. the dedicated property cannot be set for virtual processors that are added or modified. Problem When you attempt the edit virtual server task for active and stored settings of a System z virtual server. You can update the z/VM user directory for the virtual server using the z/VM directory manager. Resolution This is a current known limitation for IBM Systems Director VMControl. The modification will not succeed. an error is returned for the job. Specify the DEDICATED option on the CPU statement for the virtual server. Explanation The minidisk modification attempt occurs because of a difference between the active and stored settings for the minidisks. Problem When editing a System z virtual server. Unable to set virtual processor to dedicated with edit virtual server This problem affects the edit virtual server task when it is targeted to a System z virtual server. Resolution Edit the active and stored settings separately. although you did not request the minidisk change. Unexpected minidisk change attempted when editing virtual server This problem affects the edit virtual server task when it is targeted to a System z virtual server. The modification will not succeed. The error indicates an unexpected error with return code 204. Problem When you use the edit virtual server task for a running System z server to add a virtual switch or guest LAN to active and stored settings. reason code 86 IBM Systems Director VMControl: Installation and User’s Guide .

MAC ID <MAC address of the system you are trying to deploy to> is already used by NIM machine <name of the existing NIM machine>. Resolution To resolve this problem.1 87 . 20 from Virtual_Network_Adapter_Connect_LAN. The IBM Systems Director Server is not updated with information on the resource changes. 2. An update will occur the next time inventory collection is performed on the IBM z/VM Manageability Access Point Agent or when a successful change is made to the virtual server that does not return an error. Resolution This is a current known limitation for IBM Systems Director VMControl. Log on to the NIM Master as the root user. the image repository hosted on that managed system is still known to IBM Systems Director and the corresponding virtual appliances still appear to be available. delete the existing NIM machine from the NIM Master manually and try the deploy again. IBM Systems Director VMControl V2. Explanation The network interface was successfully added. Problem After you uninstall an IBM Systems Director VMControl agent. Follow these steps to remove the existing NIM machine from the NIM Master: 1. either the IBM Systems Director VMControl subagent for NIM or the IBM Systems Director z/VM manageability access point agent. Run the following command: nim -Fo remove <name of the NIM machine that you want to delete> Image repositories remain after IBM Systems Director VMControl agents are uninstalled This problem affects the IBM Systems Director VMControl environment when the IBM Systems Director VMControl subagent for NIM or the IBM Systems Director z/VM manageability access point agent is uninstalled. Run the following command: nim -Fo deallocate -a subclass=all <name of the NIM machine that you want to delete> 4. Chapter 2. Deploy to a NIM Master fails with error DNZIMN868E Problem When you try to deploy a virtual appliance to a NIM Master. The return code and reason code indicate that the device was automatically coupled to the LAN by the z/VM control program. you see the following message: DNZIMN868E: Could not define NIM machine <name of the NIM machine you are trying to create with the deploy operation>. Run the following command: nim -Fo reset <name of the NIM machine that you want to delete> 3.

including commands and OVF specifications. Explanation There is no automatic mechanism for IBM Systems Director Server to be notified when the IBM Systems Director VMControl agents are uninstalled. deployva Use the deployva command to deploy a virtual appliance into a new or existing virtual server as a workload. 1. Therefore. IBM Systems Director VMControl commands IBM Systems Director VMControl includes a library of commands that you can use to perform many of the same workload-management operations that can be accomplished from the Web interface. if you still require access when it no longer contains the image repository. since IBM Systems Director Server is no longer able to perform these IBM Systems Director VMControl actions on the image repository system. 88 IBM Systems Director VMControl: Installation and User’s Guide . Resolution Complete the following steps to eliminate the image repository and associated virtual appliances from appearing after you have uninstalled the IBM Systems Director VMControl agent. capture. Rediscover and request access to the managed system again. any actions you attempt to perform against the image repository or virtual appliances (such as discover. when the agents are uninstalled. or deploy) will fail. IBM Systems Director Server continues to allow you to interact with the image repository and virtual appliances to a degree. However. smcli commands The following smcli commands are available for IBM Systems Director VMControl: captureva Use the captureva command to capture a virtual appliance from a virtual server or from an existing AIX mksysb image file. Related tasks Removing a resource Performing a system discovery Reference This section provides reference information for IBM Systems Director VMControl. Remove both the Server and Operating System managed objects that represent the managed system where one of the following IBM Systems Director VMControl agents was uninstalled: v IBM Systems Director VMControl subagent for NIM v IBM Systems Director z/VM manageability access point agent 2. Attention: Completing the following steps will cause all history and automatic event automation for the managed system to be lost.

IBM Systems Director VMControl V2. v Options and operands that are not enclosed in either brackets or braces are required. and the two formats are functionally interchangeable when issuing a command. For example. deployva. and operands.importva Use the importva command to import a virtual appliance into IBM Systems Director VMControl Image Manager. you can target objects using either -n name OR -N groupname OR -ac objectclass). v Options preceded by two dashes (--) must be specified in their entirety.1 89 . lscustomization Use the lscustomization command to list attributes that you can customize for a virtual appliance when you run the captureva. Chapter 2. The single letter format is the short form of the multiple letter format. v Operands and option arguments that are italicized must be replaced with actual values. lsdeploytargets Use the lsdeploytargets command to list the target servers or hosts on which you can deploy a virtual appliance workload. or importva commands. --help). How to read syntax diagrams Review the conventions used in syntax diagrams to understand the command descriptions. v Options and operands that are enclosed in braces ({}) are required. file_name specifies the name of the file on or with which to take action. lscapsrv Use the lscapsrv command list servers that you can capture as virtual appliances. -l specifies long output) or required input that you can specify in different ways (for example. Options Options indicate input that affects the behavior of the base command (for example. Options consist of either a hyphen and single letter (for example. Do not include these braces in the command. lsva Use the lsva command to list virtual appliances. lsrepos Use the lsrepos command to list repositories. Syntax diagrams adhere to the following conventions: v Options and operands that are enclosed in brackets ([]) are optional. with -file file_name. Option arguments Some options are followed by one or more option arguments that specify a value for the option. Syntax diagrams consists of options. option arguments. -h) or two hyphens and multiple letters (for example. v The names of options are case sensitive and must be typed exactly as shown. Operands Operands are parameters at the end of a command that specify required user input. Do not include these brackets in the command.

1. . {a | b} indicates that you must choose either a or b.. but not both. depending on the enclosing characters.. where key is the attribute key and value is the new attribute value. v The attributes and attribute values are not locale specific. Tips: v You can use the lscustomization command to list all customizable attributes.. -D | --description ″description″ Specifies descriptive text that you supply for the object that is created. v Separate the key-value pairs with commas (for example. enclose the description in quotation marks. run the following command: smcli lscustomization -a capture -r repository Note: Customization is not supported when performing the capture task on z/VM. Similarly. captureva command Use the captureva command to capture a virtual appliance from a virtual server or from an existing AIX mksysb image file. v A dash (-) represents standard output. For example.]″ Assigns values to one or more customizable attributes. ″cpushare=2.. [a | b] indicates that you can choose either a or b. FlagsOptions -A | --attribute ″key=value [.memsize=4096″). – To list the customizable attributes for capturing a virtual server. 90 IBM Systems Director VMControl: Installation and User’s Guide . run the following command: smcli lscustomization -a capture -r repository -s server – To list the customizable attributes for capturing an existing AIX mksysb image file. If the description contains special characters such as spaces or commas. choose one option or the other. v A pipe (|) character signifies that you can or must. v An ellipsis (.) signifies that you can repeat the operand and option argument on the command line. SyntaxSynopsis smcli captureva {-h | -? | --help} [-L language] smcli captureva [-L language] [-v] -r repository -n name -s server [-D description] [-A attribute_list] smcli captureva [-L language] [-v] -r repository -n name -F fileLocation [-D description] [-A attribute_list] Description The captureva command captures a workload from a virtual server or an existing AIX mksysb image file and stores the resulting virtual appliance in IBM Systems Director VMControl.

IBM Systems Director VMControl V2. a description of the command. --help Displays detailed information about the command. Note: -F repos://path/file refers to an AIX mksysb image file that is located on the repository that is identified by the -r option on your NIM master. v (AIX and Linux only) You can also display detailed help in the form of man pages using the man command_name command. If the name or URI contains spaces. -h | -? Displays the syntax and a brief description of the command. Note: This option is not supported when performing the capture task on z/VM.-F | --fileLocation ″file_location″ Specifies the name or URI of an existing mksysb image file that you want to capture. including the syntax. the options are ignored. -L | --lang language Specifies the language to use for the command. Tips: v If you specify additional options other than -L | --lang. enclose it in quotation marks.1 91 . and examples. the options are ignored. error codes. The following languages are supported: v de: German v en: English v es: Spanish v fr: French v it: Italian v ja: Japanese v ko: Korean v pt_BR: Brazilian Portuguese v zh_CN: Simplified Chinese Chapter 2. The following name and URI formats are supported: v -F [relativepath]file (any IBM Systems Director Server) v -F /localpath/file (IBM Systems Director Server on AIX and Linux only) v -F c:\localpath/file (IBM Systems Director Server on Windows only) v -F \\computername\path (IBM Systems Director Server on Windows only) v -F file://localpath/file (IBM Systems Director Server on AIX and Linux only) v -F file://c/localpath/file (IBM Systems Director Server on Windows only) v -F http://path/file (any IBM Systems Director Server) v -F repos://path/file (any IBM Systems Director Server) Note: The specified AIX mksysb image file is always copied to a new appliance directory under /export/nim/appliances on the NIM master. The original AIX mksysb image file remains unchanged. Tip: If you specify additional options other than -L | --lang. a description of the options and operands.

v 1: A usage error occurred. in this case. 123 or 0x7b). en is used). -r | --repository repository Specifies the unique ID (OID) of the targeted repository object. If this option is not specified. this command suppresses noncritical messages. irrespective of country code. v If you specify the language using the format language_country. v 47: The virtual appliance could not be created. v 0: The operation completed successfully. -v | --verbose Writes verbose messages to standard output. v 125: The command terminated. Tips: v Use the following command to list the specific repository that is needed to handle the server that you want to capture: smcli lsrepos -o -a capture -s server v Use the following command to find the unique ID of your NIM repository if you are capturing an existing AIX mksysb image file: smcli lsrepos -ol -s | --server server Specifies the unique ID (OID) of the targeted server object. including the environment variable DIR_LANG and operating-system settings. Specify the unique ID as a decimal or hexadecimal value (for example. 123 or 0x7b). Exit status The following table contains the codes returned by this command. where language is a supported language but country is a not a supported country code for that language (for example. en_US). v If you specify a language that is not supported. 92 IBM Systems Director VMControl: Installation and User’s Guide . v zh_TW: Traditional Chinese Tips: v This option overrides other mechanisms for specifying the locale. enclose the name in quotation marks. then the specified language is used (for example. v 60: An illegal parameter was used. v 27: A specified attribute is not valid. v 9: An invalid locale was used. -n | --name ″name″ Specifies a name for the virtual appliance that is created. v 29: The specified locale is not valid or not supported. Specify the unique ID as a decimal or hexadecimal value (for example. If the name contains special characters such as spaces. Tip: Use the lscapsrv command with the -o option to list the name and OID of all servers that you can capture. the default language is used and an error message is displayed. An error is not displayed.

Tip: To deploy an empty virtual server. smcli captureva -v -s 123 -r 345 -n "XYZLpar" -D "Production server" 2. SyntaxSynopsis smcli deployva {-h | -? | --help} [-L language] smcli deployva [-L language] [-v] -a {deploy_existing | deploy_new} -s server -V virtualAppliance [-A attribute_list] Description The deployva command deploys a virtual appliance into an existing virtual server or creates a virtual server and deploys a virtual appliance. deploy_new This action deploys a virtual appliance to a newly created virtual server on the specified host system.1 93 . – To list the customizable attributes for deploying a virtual appliance to an existing virtual server.mksysb -n "oldImage" Related tasks “Capturing an existing mksysb image file to create a virtual appliance” on page 55 “Capturing a virtual server to create a virtual appliance” on page 57 “Managing workloads in your virtual environment” on page 41 deployva command Use the deployva command to deploy a virtual appliance into a new or existing virtual server as a workload. Tips: v You can use the lscustomization command to list all customizable attributes. IBM Systems Director VMControl V2. -A | --attribute ″key=value [.. Capture an image on a NIM master This example illustrates how to capture an existing AIX mksysb image residing on your NIM master.. which is a function that is available in the IBM Systems Director Web interface deploy wizard. smcli captureva -v -r 345 -F repos://tmp/old. The following deployment actions are supported: deploy_existing This action deploys a virtual appliance to an existing virtual server. Capture the workload from a server This example illustrates how to capture the workload from server 123. FlagsOptions -a | --action {deploy_existing | deploy_new} Specifies the target action. run the mkvs command. run the following command: smcli lscustomization -a deploy_existing -V virtualAppliance -s server Chapter 2. where key is the attribute key and value is the new attribute value.Examples 1. .]″ Assigns values to one or more customizable attributes.

com. and time zone – Operating system information for each network interface that was captured in the image.networkport. a description of the options and operands.gateway – product. and time zone – Operating system information for each network interface that was captured in the image.vim.networkport. which includes the IP address.6. domain name.ovf.netmask – product. v The attributes and attribute values are not locale specific.vim.ibm.AIX1.2. error codes.hostname – poolstorages v If you are deploying a virtual appliance that contains a Linux image for z/VM.ovf. 94 IBM Systems Director VMControl: Installation and User’s Guide .2.vim.2.ovf. subnet mask. and use of DHCP deploy_new case – Network port information used to define the network interface to z/VM for all network interfaces that were captured in the image – Volume information used to define the volume to z/VM for all volumes that were captured in the image – Password information for the server that is created – Operating system information for the host name.vim.ovf.AIX1.netmask – product. and use of DHCP v Separate the key-value pairs with commas (for example. subnet mask.6.ibm.6.networkport.AIX1. and examples.6.vim.2.ip – product.ibm.vim. gateway address.ibm.gateway deploy_new case – product. – To list the customizable attributes for deploying a virtual appliance to a new virtual server.AIX1.com.2. which includes the IP address. ″cpushare=2. gateway address.com.memsize=4096″).2.AIX1.vim. --help Displays detailed information about the command.ibm.ovf.ip – product. the following minimum set of customizable attributes are required: deploy_existing case – product.com. run the following command: smcli lscustomization -a deploy_new -V virtualAppliance -s host v If you are deploying a virtual appliance that contains an AIX mksysb image for IBM Power.6.ovf. -h | -? Displays the syntax and a brief description of the command.com.com.networkport. Tip: If you specify additional options other than -L | --lang. domain name.2.AIX1.ovf.networkport.AIX1.system.ibm.1.ibm.6.networkport. the following minimum set of customizable attributes are required: deploy_existing case – Operating system information for the host name. a description of the command. the options are ignored. including the syntax.com.

including the environment variable DIR_LANG and operating-system settings. -V | --virtualAppliance virtual_appliance Specifies the unique ID (OID) of the targeted virtual appliance object on which you want to take action. Tips: v Use the lsdeploytargets command with the -o option to list all servers and hosts. Tip: Use the lsva -l command to list all virtual appliance IDs. v If you specify the language using the format language_country. An error is not displayed. v (AIX and Linux only) You can also display detailed help in the form of man pages using the man command_name command. en is used). If this option is not specified. then you must specify a virtualization host system. the options are ignored. Specify the unique ID as a decimal or hexadecimal value (for example. v If the deploy_existing action is specified. Chapter 2. -L | --lang language Specifies the language to use for the command. 123 or 0x7b). Tips: v If you specify additional options other than -L | --lang. irrespective of country code. where language is a supported language but country is a not a supported country code for that language (for example. -v | --verbose Writes verbose messages to standard output. this command suppresses noncritical messages. Specify the unique ID as a decimal or hexadecimal value (for example. IBM Systems Director VMControl V2. then you must specify an existing virtual server. the default language is used and an error message is displayed.1 95 . then the specified language is used (for example. -s | --server {server | host} Specifies the unique ID (OID) of the targeted server or host object. in this case. The following languages are supported: v de: German v en: English v es: Spanish v fr: French v it: Italian v ja: Japanese v ko: Korean v pt_BR: Brazilian Portuguese v zh_CN: Simplified Chinese v zh_TW: Traditional Chinese Tips: v This option overrides other mechanisms for specifying the locale. en_US). v If you specify a language that is not supported. 123 or 0x7b). v If the deploy_new action is specified.

2.com.com.ovf.2.zvm.timezone. Deploy a new z/VM workload into an existing virtual server This example illustrates how to deploy a new z/VM-based Linux workload (virtual appliance 4677) into an existing virtual server 4091.ovf.LINUX235.vim.com.ip=5.LINUX235.44.ovf.255.zvm.3.33.6.255.com. product.5.ibm.vim.com.ovf.2.ibm. smcli deployva -v -s 123 -V 345 -a deploy_new -A "poolstorages=rootvg:VIOS vioserver.vim.LINUX235.zvm.2.netmask=255.6.2.5.abc. v 1: A usage error occurred.AIX1.networkport. product.55.6.com.2" 2.networkport.ovf.6.networkport.ovf.com.com.33.AIX1.2.system.vim.dns1.networkport.88.AIX1.254" 3.ibm.22.eth0.ovf.com. product.AIX1. product.hostname=dir44.2.2.ibm.vim.domainname=spot. product.networkport. product.gateway=5.6.2.networkport.44.ovf.vim. Create a new server and deploy a new AIX workload This example illustrates how to create a new server on host 123 and deploy a new AIX workload (virtual appliance 345).2.offset=-0400 96 IBM Systems Director VMControl: Installation and User’s Guide . product.AIX1.ibm.vim.vim.networkport.zvm.ovf.domainname= spot. product. smcli deployva -v -a deploy_existing -V 4677 -s 4091 -A product.128. v 27: A specified attribute is not valid.ibm.ovf.ip=1.netmask=255.vim.LINUX235.6. product.5. v 29: The specified locale is not valid or not supported. v 0: The operation completed successfully.ibm.192.vim.vim. v 60: An illegal parameter was used.77.zvm.AIX1. product.system.vim.2.ibm.66.hostname=gses88. product.ovf.ovf.gateway=5.44.33.5.LINUX235.networkport.AIX1.ovf. Examples 1.com.com.vim.2.eth0.gateway=5.networkport.255.eth0.com.zvm.LINUX235.vim.com.eth0.2. Exit status The following table contains the codes returned by this command.6.99.com.5.com.ibm.77.com.255.vim.zvm.dns1.vim.ovf.com.5.abc.22.networkport. v 62: Deployment of the virtual appliance failed.AIX1.ovf.ibm.registerindns=true.vim.ibm.ip=8.com. product.networkport.hostname=gses88.ibm.22.ibm.6.192.2.33.254.ip=1. product.eth0.2.5.255.zvm.ibm.ip=5.ovf.5. product.LINUX235.5.LINUX235.networkport.2. v 9: An invalid locale was used. product.ovf.ibm. product.2.ovf.vim.com.netmask= 255.com.2.system.255.zvm.com. product.LINUX235.networkport.eth0.zvm.com.5. v 65: An illegal customization format was used.22.LINUX235.7.networkport.usedhcp=false. Deploy a new AIX workload into an existing virtual server This example illustrates how to deploy a new AIX workload (virtual appliance 348) into an existing virtual server 975.2.ibm.AIX1.ibm.ovf.ibm.eth0.networkport.2.LINUX235. v 125: The command terminated. virtualnetworks[Virtual Network 1]=hostVnet:ETHERNET0/1.zvm.66. smcli deployva -v -s 975 -V 348 -a deploy_existing -A "product.ibm.vim. product.5.6.eth0.networkport.hostname=dir44.ibm.vim.ovf.

v The attributes and attribute values are not locale specific. Tips: v To list all customizable attributes for the importva command. use the following command: smcli lscustomization -a import -F fileLocation -r repository v Separate the key-value pairs with commas (for example. IBM Systems Director VMControl V2. -F | --fileLocation ″file_location″ Specifies the name or URI of an existing ..ovf file (an OVF descriptor file which has references to the other files comprising an OVF package in set-of-files format) or .1. ″cpushare=2. SyntaxSynopsis smcli importva {-h | -? | --help} [-L language] smcli importva [-L language] [-v] -F fileLocation -r repository [-n name] [-D description] [-A attribute_list] Description The importva command imports a virtual appliance in Open Virtualization Format (OVF) into IBM Systems Director VMControl Image Manager.1 97 . Virtual appliances in either OVF package form (TAR file or set-of-files) are acceptable. making it available for deployment. If the name or URI contains spaces. enclose the description in quotation marks.ova file (an OVF package in TAR format) that you want to import. . If the description contains special characters such as spaces or commas. -D | --description ″description″ Specifies descriptive text that you supply for the object that is created.memsize=4096″). FlagsOptions -A | --attribute ″key=value [.. where key is the attribute key and value is the new attribute value. enclose it in quotation marks. The following name and URI formats are supported: v -F [relativepath]file (any IBM Systems Director Server) v -F /localpath/file (IBM Systems Director Server on AIX and Linux only) v -F c:\localpath/file (IBM Systems Director Server on Windows only) v -F \\computername\path (IBM Systems Director Server on Windows only) v -F file://localpath/file (IBM Systems Director Server on AIX and Linux only) Chapter 2.Related tasks “Capturing an existing mksysb image file to create a virtual appliance” on page 55 “Deploying a virtual appliance or empty virtual server” on page 57 “Managing workloads in your virtual environment” on page 41 importva command Use the importva command to import a virtual appliance into IBM Systems Director VMControl Image Manager.]″ Assigns values to one or more customizable attributes.

v -F file://c/localpath/file (IBM Systems Director Server on Windows
only)
v -F http://path/file (any IBM Systems Director Server)
-h | -?
Displays the syntax and a brief description of the command.

Tip: If you specify additional options other than -L | --lang, the options are
ignored.
--help
Displays detailed information about the command, including the syntax, a
description of the command, a description of the options and operands, error
codes, and examples.

Tips:
v If you specify additional options other than -L | --lang, the options are
ignored.
v (AIX and Linux only) You can also display detailed help in the form of man
pages using the man command_name command.
-L | --lang language
Specifies the language to use for the command.
The following languages are supported:
v de: German
v en: English
v es: Spanish
v fr: French
v it: Italian
v ja: Japanese
v ko: Korean
v pt_BR: Brazilian Portuguese
v zh_CN: Simplified Chinese
v zh_TW: Traditional Chinese

Tips:
v This option overrides other mechanisms for specifying the locale, including
the environment variable DIR_LANG and operating-system settings.
v If you specify the language using the format language_country, where
language is a supported language but country is a not a supported country
code for that language (for example, en_US), then the specified language is
used (for example, in this case, en is used). An error is not displayed.
v If you specify a language that is not supported, irrespective of country code,
the default language is used and an error message is displayed.
-n | --name ″name″
Specifies a name by which the imported virtual appliance should be known
within IBM Systems Director VMControl Image Manager. If the name contains
special characters such as spaces, enclose the name in quotation marks.

Note: You can set the name only if the OVF package does not already have a
name for the virtual appliance.
-r | --repository repository
Specifies the unique ID (OID) of the targeted repository object.

98 IBM Systems Director VMControl: Installation and User’s Guide

Specify the unique ID as a decimal or hexadecimal value (for example, 123 or
0x7b).

Tip: Use the following command to list the specific repository that is needed
to handle the file that you want to import:
smcli lsrepos -o -a import -F fileLocation
-v | --verbose
Writes verbose messages to standard output.
If this option is not specified, this command suppresses noncritical messages.

Exit status

The following table contains the codes returned by this command.
v 0: The operation completed successfully.
v 1: A usage error occurred.
v 9: An invalid locale was used.
v 27: A specified attribute is not valid.
v 29: The specified locale is not valid or not supported.
v 60: An illegal parameter was used.
v 63: Importation of the virtual appliance failed.
v 73: An illegal name change was attempted.
v 125: The command terminated.

Examples
1. Import a virtual appliance
This example illustrates how to import the virtual appliance in joe.ova, an OVF
package in TAR format.
smcli importva -v -F "/tmp/joe.ova" -r 123
Related tasks
“Importing a virtual appliance package” on page 54
“Managing workloads in your virtual environment” on page 41

lscapsrv command
Use the lscapsrv command list servers that you can capture as virtual appliances.

SyntaxSynopsis

smcli lscapsrv [-h | -? | --help] [-L language]

smcli lscapsrv [-L language] [-v] [-l] [-o] [-d delimiter_symbol]

Description

The lscapsrv command displays a list of servers that have workloads that you can
capture as virtual appliances.

FlagsOptions
-d | --delimiter ″delimiter_symbol″
Specifies the character or set of characters that separates output data, where
delimiter_symbol is a string of one or more characters. This command separates
data fields in a record by a comma followed by a space. Data records are
separated by the specified delimiter delimiter_symbol.

Chapter 2. IBM Systems Director VMControl V2.1 99

If you specify this option with the -l | --long option, the delimiter option is
ignored.

Tip: If the delimiter contains spaces, enclose it in quotation marks.
-h | -?
Displays the syntax and a brief description of the command.

Tip: If you specify additional options other than -L | --lang, the options are
ignored.
--help
Displays detailed information about the command, including the syntax, a
description of the command, a description of the options and operands, error
codes, and examples.

Tips:
v If you specify additional options other than -L | --lang, the options are
ignored.
v (AIX and Linux only) You can also display detailed help in the form of man
pages using the man command_name command.
-l | --long
Displays all attributes of the specified object.
-L | --lang language
Specifies the language to use for the command.
The following languages are supported:
v de: German
v en: English
v es: Spanish
v fr: French
v it: Italian
v ja: Japanese
v ko: Korean
v pt_BR: Brazilian Portuguese
v zh_CN: Simplified Chinese
v zh_TW: Traditional Chinese

Tips:
v This option overrides other mechanisms for specifying the locale, including
the environment variable DIR_LANG and operating-system settings.
v If you specify the language using the format language_country, where
language is a supported language but country is a not a supported country
code for that language (for example, en_US), then the specified language is
used (for example, in this case, en is used). An error is not displayed.
v If you specify a language that is not supported, irrespective of country code,
the default language is used and an error message is displayed.
-o | --oid
Displays the unique IDs (OIDs), in addition to other information, associated
with the targeted object.
The unique IDs are displayed as decimal values (for example, 123).

Note: You can combine this option with the -l | --long option.

100 IBM Systems Director VMControl: Installation and User’s Guide

v 9: An invalid locale was used.-v | --verbose Writes verbose messages to standard output. After you determine the attributes Chapter 2. along with their object IDs. smcli lscapsrv -v -o Related tasks “Managing workloads in your virtual environment” on page 41 lscustomization command Use the lscustomization command to list attributes that you can customize for a virtual appliance when you run the captureva. v 60: An illegal parameter was used. Examples 1. or importva commands. v 69: An invalid criteria was used. You must specify an action. Display servers and object IDs that you can capture This example illustrates how to display a list of servers. v 27: A specified attribute is not valid. Display servers that you can capture This example illustrates how to display a list of servers that you can capture. smcli lscapsrv -v 2. then the action that you specify determines which other options you must or can specify.1 101 . this command suppresses noncritical messages. v 29: The specified locale is not valid or not supported. deployva. v 125: The command terminated. v 70: Creation of a list of servers that can be captured failed. that you can capture. SyntaxSynopsis smcli lscustomization {-h | -? | --help} [-L language] smcli lscustomization [-L language] [-v] -a capture -r repository [-s server] smcli lscustomization [-L language] [-v] -a deploy_existing -V virtualAppliance -s server smcli lscustomization [-L language] [-v] -a deploy_new -V virtualAppliance -s host smcli lscustomization [-L language] [-v] -a import -F fileLocation -r repository Description The lscustomization command displays the customizable attributes for a virtual appliance. If this option is not specified. IBM Systems Director VMControl V2. Exit status The following table contains the codes returned by this command. v 0: The operation completed successfully. v 1: A usage error occurred.

-F | --fileLocation ″file_location″ Specifies the name or URI of an existing . However.1 or a value that is higher than 0. The lscustomization command produces output in the format of the following example: cpushare Value: 1.1 by an increment of 0. enclose it in quotation marks. if you do not provide a customized value. If the name or URI contains spaces.1 Description: Number of virtual processors memsize Value: 1024 Increment: 1 IncrementType: LINEAR Description: Memory (MB) In this example.009" (because it does not meet the minimum value criteria) or -A "cpushare=4" (because it is a simple integer. cpushare has a default value of 1. cpushare and memsize are the names of the customizable attributes. you can specify those attributes in the -A option of the captureva. deployva. deploy_existing This action displays the virtual appliance attributes that you can specify when using the deployva -a deploy_existing command.1 Max: 0.3" when using the deployva command. or importva command.ovf file (an OVF descriptor file which has references to the other files comprising an OVF package in set-of-files format) or . The other properties then provide information about how you can customize the attribute. Here. This means that. but you cannot specify -A "cpushare=0. that you can customize for a virtual appliance. The following deployment actions are supported: capture This action displays the virtual appliance attributes that you can specify when using the captureva command. if you choose to customize this attribute.ova file (an OVF package in TAR format).0 Increment: 0.0 Min: 0.1. The following name and URI formats are supported: v -F [relativepath]file (any IBM Systems Director Server) v -F /localpath/file (IBM Systems Director Server on AIX and Linux only) v -F c:\localpath/file (IBM Systems Director Server on Windows only) 102 IBM Systems Director VMControl: Installation and User’s Guide .0. which is not the correct form). FlagsOptions -a | --action {capture | deploy_existing | deploy_new | import} Specifies the target action. Therefore. you can specify -A "cpushare=2. deploy_new This action displays the virtual appliance attributes that you can specify when using the deployva -a deploy_new command. import This action displays the virtual appliance attributes that you can specify when using the importva command. you must specify 0. The Value property indicates the default value of each attribute. the virtual appliance will expect a virtual server with exactly one virtual processor (and zero fractional virtual processors).

irrespective of country code. and examples. including the syntax. IBM Systems Director VMControl V2. v (AIX and Linux only) You can also display detailed help in the form of man pages using the man command_name command. where language is a supported language but country is a not a supported country code for that language (for example. An error is not displayed.1 103 . --help Displays detailed information about the command. use the lsrepos command with the -o option. a description of the command. Tips: v If you specify additional options other than -L | --lang. -r | --repository repository Specifies the unique ID (OID) of the targeted repository object. Tip: To list all repository names and OIDs. then the specified language is used (for example. including the environment variable DIR_LANG and operating-system settings. Chapter 2. en is used). -L | --lang language Specifies the language to use for the command. the default language is used and an error message is displayed. 123 or 0x7b). Specify the unique ID as a decimal or hexadecimal value (for example. in this case. v If you specify the language using the format language_country. a description of the options and operands. the options are ignored. v If you specify a language that is not supported. the options are ignored. Tip: If you specify additional options other than -L | --lang. en_US). The following languages are supported: v de: German v en: English v es: Spanish v fr: French v it: Italian v ja: Japanese v ko: Korean v pt_BR: Brazilian Portuguese v zh_CN: Simplified Chinese v zh_TW: Traditional Chinese Tips: v This option overrides other mechanisms for specifying the locale. v -F \\computername\path (IBM Systems Director Server on Windows only) v -F file://localpath/file (IBM Systems Director Server on AIX and Linux only) v -F file://c/localpath/file (IBM Systems Director Server on Windows only) v -F http://path/file (any IBM Systems Director Server) -h | -? Displays the syntax and a brief description of the command. error codes.

-v | --verbose Writes verbose messages to standard output. then you must specify an existing virtual server. v 69: An invalid criteria was used. v If the deploy_existing action is specified. Specify the unique ID as a decimal or hexadecimal value (for example. depending on the specified -a option value. 123 or 0x7b). v 0: The operation completed successfully. v 1: A usage error occurred. 123 or 0x7b). -V | --virtualAppliance virtual_appliance Specifies the unique ID (OID) of the targeted virtual appliance object on which you want to take action. to list servers or hosts. Tips: v Use either the lscapsrv or lsdeploytargets command. Tip: Use the lsva -l command to list all virtual appliance IDs. v 29: The specified locale is not valid or not supported. smcli lscustomization -v -a capture -r 722 Note: Use this format before running smcli captureva -r repository -n name -F fileLocation. -s | --server {server | host} Specifies the unique ID (OID) of the targeted server or host object. Exit status The following table contains the codes returned by this command. v If you will run captureva to capture an existing AIX mksysb image file. Examples 1. Specify the unique ID as a decimal or hexadecimal value (for example. v 125: The command terminated. v If the deploy_new action is specified. then specify a server. v 27: A specified attribute is not valid. but only if you intend to run captureva to capture an existing virtual server. do not specify the -s option on lscustomization. this command suppresses noncritical messages. v If the capture action is specified. 104 IBM Systems Director VMControl: Installation and User’s Guide . If this option is not specified. v 60: An illegal parameter was used. v 72: Creation of a list of customizable attributes failed. then you must specify a virtualization host system. Display customizable attributes for a virtual appliance that you can capture from a mksysb image file and store in a repository This example illustrates how to display the customizable attributes for a virtual appliance that you intend to capture from an existing AIX mksysb image file and store in repository 722. v 9: An invalid locale was used.

acmeimages. Related tasks “Capturing an existing mksysb image file to create a virtual appliance” on page 55 “Managing workloads in your virtual environment” on page 41 lsdeploytargets command Use the lsdeploytargets command to list the target servers or hosts on which you can deploy a virtual appliance workload. Display customizable attributes for a virtual appliance that you can import from the Internet and store in a repository This example illustrates how to display the customizable attributes for a virtual appliance that you intend to import from the Internet and store in repository 722. smcli lscustomization -v -a capture -s 456 -r 722 Note: Use this format before running smcli captureva -r repository -n name -s server. smcli lscustomization -v -a deploy_existing -V 322 -s 456 Note: Use this format before running smcli deployva -a deploy_existing -s server -V virtualAppliance. 4. SyntaxSynopsis smcli lsdeploytargets {-h | -? | --help} [-L language] smcli lsdeploytargets [-L language] [-v] [-l] [-o] [-d delimiter_symbol] -a {deploy_existing | deploy_new} [-V virtualAppliance] Chapter 2. 5. Display customizable attributes for a virtual appliance that you can capture from a virtual server and store in a repository This example illustrates how to display the customizable attributes for a virtual appliance that you intend to capture from existing virtual server 456 and store in repository 722.1 105 . IBM Systems Director VMControl V2. Display customizable attributes for a virtual appliance that you can deploy to an existing virtual server This example illustrates how to display the customizable attributes for virtual appliance 322 that you intend to deploy to existing virtual server 456. 3. smcli lscustomization -v -a import -F http://www.2.ova -r 722 Note: Use this format before running smcli importva -F fileLocation -r repository. smcli lscustomization -v -a deploy_new -V 322 -s 123 Note: Use this format before running smcli deployva -a deploy_new -s host -V virtualAppliance.com/aix/aix61. Display customizable attributes for a virtual appliance that you can deploy to a new virtual server This example illustrates how to display the customizable attributes for virtual appliance 322 that you intend to deploy to a new virtual server on a host 123.

a description of the command. and examples. where delimiter_symbol is a string of one or more characters. The following deployment actions are supported: deploy_existing This action indicates that you want a list of existing virtual servers that can accommodate the specified virtual appliance. -l | --long Displays all attributes of the specified object. Data records are separated by the specified delimiter delimiter_symbol. error codes. This command separates data fields in a record by a comma followed by a space. Tip: If the delimiter contains spaces. the options are ignored. enclose it in quotation marks. FlagsOptions -a | --action {deploy_existing | deploy_new} Specifies the target action. Tip: If you specify additional options other than -L | --lang. deploy_new This action indicates that you want a list of host systems on which you can create a virtual server to accommodate the specified virtual appliance. v (AIX and Linux only) You can also display detailed help in the form of man pages using the man command_name command. Description The lsdeploytargets command displays a list of existing servers or hosts to which you can deploy virtual appliances. Tips: v If you specify additional options other than -L | --lang. -L | --lang language Specifies the language to use for the command. -d | --delimiter ″delimiter_symbol″ Specifies the character or set of characters that separates output data. -h | -? Displays the syntax and a brief description of the command. the delimiter option is ignored. If you specify this option with the -l | --long option. The following languages are supported: v de: German v en: English v es: Spanish v fr: French v it: Italian v ja: Japanese 106 IBM Systems Director VMControl: Installation and User’s Guide . including the syntax. a description of the options and operands. the options are ignored. --help Displays detailed information about the command.

v 69: An invalid criteria was used. Specify the unique ID as a decimal or hexadecimal value (for example. v 9: An invalid locale was used. v If you specify the language using the format language_country. v 0: The operation completed successfully. where language is a supported language but country is a not a supported country code for that language (for example. v 29: The specified locale is not valid or not supported. this command suppresses noncritical messages. including the environment variable DIR_LANG and operating-system settings. then the specified language is used (for example. v ko: Korean v pt_BR: Brazilian Portuguese v zh_CN: Simplified Chinese v zh_TW: Traditional Chinese Tips: v This option overrides other mechanisms for specifying the locale. An error is not displayed. IBM Systems Director VMControl V2. v 60: An illegal parameter was used. en is used). smcli lsdeploytargets -v -a deploy_existing -V 322 2. 123 or 0x7b). associated with the targeted object. Note: You can combine this option with the -l | --long option. irrespective of country code. Examples 1. Exit status The following table contains the codes returned by this command. -o | --oid Displays the unique IDs (OIDs). Tip: Use the lsva -l command to list all virtual appliance IDs. en_US). -v | --verbose Writes verbose messages to standard output. v 27: A specified attribute is not valid. v 125: The command terminated. Display servers on which you can deploy a virtual appliance This example illustrates how to display a list of servers on which you can deploy virtual appliance 322. -V | --virtualAppliance virtual_appliance Specifies the unique ID (OID) of the targeted virtual appliance object on which you want to take action. the default language is used and an error message is displayed. in addition to other information.1 107 . If this option is not specified. Display hosts on which you can create new virtual servers and deploy a virtual appliance Chapter 2. v 71: Creation of a list of deployable targets failed. v If you specify a language that is not supported. 123). in this case. v 1: A usage error occurred. The unique IDs are displayed as decimal values (for example.

This example illustrates how to display a list of hosts on which you can create new virtual servers and deploy virtual appliance 322. enclose it in quotation marks. pass the capture action and the OID of the virtual server object. import This action lists the repositories to which you can import the specified OVF file. The following deployment actions are supported: capture This action lists repositories that can store the virtual appliance created by capturing the workload on the specified server. SyntaxSynopsis smcli lsrepos [-h | -? | --help] [-L language] smcli lsrepos [-L language] [-v] [-l] [-o] [-d delimiter_symbol] smcli lsrepos [-L language] [-v] [-l] [-o] [-d delimiter_symbol] -a capture -s server smcli lsrepos [-L language] [-v] [-l] [-o] [-d delimiter_symbol] -a import -F fileLocation Description The lsrepos command displays a list of virtual appliance repositories. then the action that you specify determines which other options you must or can specify: v To display a list of all repositories. -d | --delimiter ″delimiter_symbol″ Specifies the character or set of characters that separates output data. Tip: If the delimiter contains spaces. FlagsOptions -a | --action {capture | import} Specifies the target action. where delimiter_symbol is a string of one or more characters. The list of repositories that is returned depends on the filtering parameters that are passed on the command. 108 IBM Systems Director VMControl: Installation and User’s Guide . specify the import action and the OVF file name. v To display a list of repositories that are available for importing an OVF file. do not specify an action. Data records are separated by the specified delimiter delimiter_symbol. This command separates data fields in a record by a comma followed by a space. If you specify an action. smcli lsdeploytargets -v -a deploy_new -V 322 Related tasks “Managing workloads in your virtual environment” on page 41 lsrepos command Use the lsrepos command to list repositories. If you specify this option with the -l | --long option. v To display a list of repositories that are available to store captured workloads for a virtual server. the delimiter option is ignored.

The following languages are supported: v de: German v en: English v es: Spanish v fr: French v it: Italian v ja: Japanese v ko: Korean v pt_BR: Brazilian Portuguese v zh_CN: Simplified Chinese v zh_TW: Traditional Chinese Tips: v This option overrides other mechanisms for specifying the locale. --help Displays detailed information about the command.1 109 . v If you specify the language using the format language_country. and examples.ovf file (an OVF descriptor file which has references to the other files comprising an OVF package in set-of-files format) or . including the syntax.ova file (an OVF package in TAR format). -L | --lang language Specifies the language to use for the command. the options are ignored. The following name and URI formats are supported: v -F [relativepath]file (any IBM Systems Director Server) v -F /localpath/file (IBM Systems Director Server on AIX and Linux only) v -F c:\localpath/file (IBM Systems Director Server on Windows only) v -F \\computername\path (IBM Systems Director Server on Windows only) v -F file://localpath/file (IBM Systems Director Server on AIX and Linux only) v -F file://c/localpath/file (IBM Systems Director Server on Windows only) v -F http://path/file (any IBM Systems Director Server) -h | -? Displays the syntax and a brief description of the command. enclose it in quotation marks. -l | --long Displays all attributes of the specified object. Tip: If you specify additional options other than -L | --lang. IBM Systems Director VMControl V2. a description of the command. If the name or URI contains spaces. including the environment variable DIR_LANG and operating-system settings. v (AIX and Linux only) You can also display detailed help in the form of man pages using the man command_name command. the options are ignored. where language is a supported language but country is a not a supported country Chapter 2. Tips: v If you specify additional options other than -L | --lang. error codes.-F | --fileLocation ″file_location″ Specifies the name or URI of an existing . a description of the options and operands.

Display all repositories This example illustrates how to display a list of all repositories. this command suppresses noncritical messages. en is used). smcli lsrepos -v -a capture -s 123 3. code for that language (for example. -v | --verbose Writes verbose messages to standard output. Display repositories to which you can import an object This example illustrates how to display a list of repositories to which you can import virtual appliance /tmp/joe. en_US). the default language is used and an error message is displayed. Examples 1. Specify the unique ID as a decimal or hexadecimal value (for example. -o | --oid Displays the unique IDs (OIDs). v 66: Creation of a list of importable repositories failed. The unique IDs are displayed as decimal values (for example. smcli lsrepos -v -a import -F "/tmp/joe. associated with the targeted object. Display repositories that can store captured objects This example illustrates how to display a list of repositories that are available to store captured virtual appliances for a virtual server with an ID of 123. in this case. v If you specify a language that is not supported.. v 68: Creation of a list of repositories that can be captured failed. v 1: A usage error occurred. -s | --server server Specifies the unique ID (OID) of the targeted server object. 123). 123 or 0x7b).ova. v 0: The operation completed successfully. then the specified language is used (for example. v 60: An illegal parameter was used. If this option is not specified. An error is not displayed. v 27: A specified attribute is not valid. smcli lsrepos -v 2. in addition to other information. irrespective of country code. Exit status The following table contains the codes returned by this command. v 29: The specified locale is not valid or not supported. v 125: The command terminated. v 69: An invalid criteria was used. Note: You can combine this option with the -l | --long option. Tip: Use the lscapsrv command with the -o option to list the name and OID of all servers that you can capture. v 9: An invalid locale was used.ova" 110 IBM Systems Director VMControl: Installation and User’s Guide .

FlagsOptions -d | --delimiter ″delimiter_symbol″ Specifies the character or set of characters that separates output data. including the syntax. Tips: v If you specify additional options other than -L | --lang. Tip: If the delimiter contains spaces. Tip: If you specify additional options other than -L | --lang. IBM Systems Director VMControl V2. --help Displays detailed information about the command. a description of the command. v (AIX and Linux only) You can also display detailed help in the form of man pages using the man command_name command. If you specify this option with the -l | --long option. -L | --lang language Specifies the language to use for the command. The results that are returned depend on the options that are specified. enclose it in quotation marks. a description of the options and operands. -h | -? Displays the syntax and a brief description of the command. This command separates data fields in a record by a comma followed by a space.1 111 . the options are ignored.Related tasks “Managing workloads in your virtual environment” on page 41 lsva command Use the lsva command to list virtual appliances. the options are ignored. Data records are separated by the specified delimiter delimiter_symbol. and examples. the delimiter option is ignored. where delimiter_symbol is a string of one or more characters. error codes. -l | --long Displays all attributes of the specified object. SyntaxSynopsis smcli lsva [-h | -? | --help] [-L language] smcli lsva [-L language] [-v] [-l] [-o] [-d delimiter_symbol] Description The lsva command displays a list of virtual appliances. The following languages are supported: v de: German v en: English v es: Spanish v fr: French v it: Italian Chapter 2.

Display all virtual appliances and object IDs This example illustrates how to display a list of all virtual appliances and their object IDs. v 0: The operation completed successfully. en is used). v If you specify a language that is not supported. -v | --verbose Writes verbose messages to standard output. v 27: A specified attribute is not valid. smcli lsva -v 2. Display all virtual appliances This example illustrates how to display a list of all virtual appliances. Examples 1. Note: You can combine this option with the -l | --long option. en_US). where language is a supported language but country is a not a supported country code for that language (for example. in this case. smcli lsva -v -o Related tasks “Managing workloads in your virtual environment” on page 41 OVF specifications for IBM Systems Director VMControl With IBM Systems Director VMControl. The unique IDs are displayed as decimal values (for example. -o | --oid Displays the unique IDs (OIDs). this command suppresses noncritical messages. v 29: The specified locale is not valid or not supported. v If you specify the language using the format language_country. the default language is used and an error message is displayed. v 1: A usage error occurred. v 125: The command terminated. This virtual appliance package or OVF package is a 112 IBM Systems Director VMControl: Installation and User’s Guide . If this option is not specified. you can import a virtual appliance package that conforms to the Distributed Management Task Force (DMTF) Open Virtualization Format (OVF). then the specified language is used (for example. An error is not displayed. Exit status The following table contains the codes returned by this command. v 9: An invalid locale was used. v 69: An invalid criteria was used. including the environment variable DIR_LANG and operating-system settings. in addition to other information. associated with the targeted object. 123). v ja: Japanese v ko: Korean v pt_BR: Brazilian Portuguese v zh_CN: Simplified Chinese v zh_TW: Traditional Chinese Tips: v This option overrides other mechanisms for specifying the locale. irrespective of country code.

IBM Systems Director VMControl V2.ova extension. For information on these extension elements. but only the default configuration is processed when the virtual appliance is deployed. typically with a .1 113 . but the string bundle files are ignored when the virtual appliance is deployed. The OVF packages captured will not specify localized strings. Related concepts “Import” on page 45 Related tasks “Importing a virtual appliance package” on page 54 OVF package requirements An OVF package is a representation of a virtual server that contains a configured. There are IBM Systems Director VMControl-specific requirements for the OVF package and specifications for the OVF XML descriptor file that describes the virtual server. v OVF packages must contain a deployable image.pdf v OVF packages must contain a single virtual system.0. v OVF packages must contain a virtual hardware section. Chapter 2. This specification is available from the DMTF Web site at: http:// www. v OVF packages that use string bundle files can be imported. along with the metadata that describes the virtual server. tested operating system and middleware and software applications. but the localized strings will be ignored and only the strings in the default language will be used when the virtual appliance is deployed.dmtf.org/standards/published_documents/DSP0243_1. v OVF packages that contain networks must have a network description.0. tested operating system and middleware and software applications. not a virtual system collection. v OVF packages with no image files cannot be imported. The OVF packages captured will not specify string bundle files. the order of files in a TAR package must conform to what is specified in the DMTF Open Virtualization Format Specification. There are several extension elements to the Item (RASD) element and to other sections of the OVF descriptor file. v OVF packages that use localization can be imported.representation of a virtual server that contains a configured. v OVF packages that define configurations by using the DeploymentOptionSection element and the ovf:configuration attribute on any Item elements can be imported. Captured OVF packages will not specify a DeploymentOptionSection nor ovf:configuration attributes on any Item elements. OVF packages to be imported must satisfy the following requirements: v If the OVF package is in TAR file format. along with the metadata that describes the virtual server. The OVF package can be in one of the following formats: v A set of files (called set-of-file format) v A single TAR file containing the same set of files. v OVF packages that use file chunking cannot be imported. see “XML schema definition (XSD) files for OVF descriptor” on page 115.

exustar. – The ovf:format attribute of any Disk elements in the DiskSection that reference image files must have the value http://www. OVF package requirements for z/VM OVF packages to be imported by z/VM are subject to the following additional requirements: v z/VM tolerates ranges in an OVF descriptor file. – LinuxLVMSection This is a z/VM extension section in the OVF descriptor file that describes the configuration of Linux Logical Volume Manager (LVM). Captured OVF packages do not specify ranges. This section is required for importing an OVF package and is created on capture. – The VirtualSystemType element within the System element of the VirtualHardwareSection must have the value IBM:zVM:LINUX.linuxfile. – The compression type of the file must either not be set or be set to identity. For more details on the specific extension sections in the OVF descriptor file. see the sample OVF descriptor files for Linux on z/VM: – “Sample OVF descriptor file for Linux on z/VM with Linux Logical Volume Manager (LVM)” on page 119 – “Sample OVF descriptor file for Linux on z/VM without Linux Logical Volume Manager (LVM)” on page 126 There are several z/VM-specific extension elements to the System (VSSD) and Item (RASD) elements and to other sections of the OVF descriptor file. OVF package requirements for NIM OVF packages to be imported by NIM are subject to the following additional requirements: v For every File reference in the Envelope element: – File size is specified and is greater than or equal to zero – A target file name can be derived from the href value by parsing it as a URI and getting the last value of the path element of the URI. This section is required for importing an OVF package and is created on capture. – The ovf:id attribute of the OperatingSystemSection must have the value 36 to indicate LINUX. see “XML schema definition (XSD) files for OVF descriptor” on page 115.gz and the referenced image files must use the EXUSTAR archive format to store the Linux files.com/xmlns/ovf/ diskformat/s390. v All of the formats specified on all of the VirtualDiskDescTypes element in the Envelope are supported by NIM and that there is one and only one disk that has the mksysb format. but is limited to always use the ″normal″ value of the range. if LVM is used by the LinuxFileSystemSection. For information on these extension elements. which means no compression. 114 IBM Systems Director VMControl: Installation and User’s Guide . if used.ibm. v OVF packages must contain the following z/VM specific extension sections in the OVF descriptor file: – LinuxFileSystemSection This is a z/VM extension section in the OVF descriptor file that describes the configuration of Linux file systems.

0. see “XML schema definition (XSD) files for OVF descriptor. Then use an XML editor to create an OVF descriptor file or modify the contents of one of the sample OVF descriptor files.0.com/tech/ovfsdk/download XML schema definition (XSD) files for OVF descriptor: XML schema definition (XSD) files define elements and attributes of the OVF descriptor file that are unique extensions for IBM Systems Director VMControl. You can download the OVF Editor from the following Web site: http:// www.1 115 . The specification for the OVF descriptor file is a combination of these things: v The Distributed Management Task Force (DMTF) Open Virtualization Format (OVF) standard. This means that there is one and only one VirtualHardwareSection in the VirtualSystem that has both a rasd:ResourceType element whose value is 31 (Logical Disk) and a HostResource element. see “OVF package requirements” on page 113. The HostResource element must specify a disk that has the mksysb format. For more information on the OVF standard. To use these files.ibm. v XML schema definition (XSD) files that define elements and attributes of the OVF descriptor file that are unique extensions for IBM Systems Director VMControl You can use both the XSD files and sample OVF descriptor files for Power and z/VM to create or modify an OVF descriptor file.pdf v IBM Systems Director VMControl requirements and restrictions for importing OVF packages For information on these requirements and restrictions. see the Open Virtualization Format Specification available from the DMTF Web site at: http://www. Note: The OVF Editor that is available from the alphaWorks® Web site supports the latest OVF standard and incorporates IBM Systems Director VMControl extensions and can be used to edit or create OVF descriptor files. There are several extension elements to the Item (RASD) element and to other sections of the OVF descriptor file. These files are available to download from the IBM Systems Director VMControl information center at the following Web site: Chapter 2.com/ xmlns/ovf/diskformat/power. Note: The only disk format that is supported by NIM is http://www.dmtf. The disk specified must reference a file in the File element of the References section.org/ standards/published_documents/DSP0243_1.aix. For information on these extension elements.mksysb.” OVF descriptor file specifications An OVF descriptor file is an XML file that contains all of the metadata about the OVF package and its contents. v There is only one system and it has one and only one mksysb image. This topic contains these XSD files that you can use to create or modify an OVF descriptor file.ibm. IBM Systems Director VMControl V2. which is a platform independent and open packaging and distribution format for virtual appliances. Using an XML editor with the XSD files displays a description of the OVF descriptor file elements and validates the OVF descriptor file that you create.alphaworks. save the XSD files to a local directory.

xsd of the OVF Descriptor that are specific to the z/VM platform.dmtf.1.1.com/xmlns/ovf/extension/vim/2/rasd" xmlns:vssd="http://schemas.com/xmlns/ovf/extension/vim/2/phyp/3" xmlns:vimphyprasd="http://www.com/xmlns/ovf/extension/vim/2/rasd ibm-vim2-rasd_2.1.mksysb" ovf:id="vimRef1" ovf:size="2337126400"/> </ovf:References> <ovf:DiskSection> <ovf:Info>Disk Section</ovf:Info> <ovf:Disk ovf:capacity="14472683520" ovf:capacityAllocationUnits="byte" ovf:diskId="vimRef1disk" ovf:fileRef="vimRef1" ovf:format="http://www. Extensions to ovf:Item (RASD) that are ibm-vim2-phyp3-rasd_2.ibm. and to z/VM.ibm. Save the XSD files that you need to create or modify an OVF descriptor file for your environment.0.xsd specific to the z/VM platform.0. Extensions to the OVF Descriptor that are ibm-vim2-zvm5_2. except for any extensions to ovf:System (VSSD) and ovf:Item (RASD) elements. <?xml version="1.xsd of the OVF Descriptor that are common across the IBM Systems Director VMControl platforms.0.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData" xsi:schemaLocation="http://www.com/xmlns/ovf/extension/vim/2" xmlns:vimphyp="http://www. Sample XSD files The XSD files shown in the following table define extensions for OVF descriptor files that are unique to IBM Systems Director VMControl.1.0.aix. You can copy and modify this file to create your own OVF descriptor file.com/xmlns/ovf/diskformat/power.dmtf.xsd common across the IBM Systems Director VMControl platforms. Extensions to the ovf:Item (RASD) element ibm-vim2-rasd_2.w3.0" encoding="UTF-8"?> <ovf:Envelope xmlns:xsi="http://www. Extensions to the ovf:System (VSSD) ibm-vim2-zvm5-vssd_2.0.xsd http://www.com/xmlns/ovf/extension/vim/2/phyp/3/rasd ibm-vim2-phyp3-rasd_2.dmtf.com/xmlns/ovf/extension/vim/2 ibm-vim2_2.ibm.org/ovf/envelope/1" xmlns="http://schemas.0.org/ovf/envelope/1" xmlns:rasd="http://schemas.0.dmtf.ibm.0.xsd http://schemas.ibm.1. to Power Systems. except for any extensions to the ovf:System (VSSD) and ovf:Item (RASD) elements.1.0.com/xmlns/ovf/extension/vim/2/phyp/3/rasd" xmlns:vimrasd="http://www.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData" xmlns:vim="http://www.1.ibm.0.ibm.mksysb" ovf:populatedSize="7236341760"/> </ovf:DiskSection> <ovf:NetworkSection> <ovf:Info>Network Section</ovf:Info> <ovf:Network ovf:name="Virtual Network 1"> <ovf:Description>Captured from virtual server ProductionServer connected to VLAN 1 on host IBM 9133 55A 12345 </ovf:Description> 116 IBM Systems Director VMControl: Installation and User’s Guide .0.org/2001/XMLSchema-instance" xmlns:ovf="http://schemas.ibm.1. Extensions to the ovf:Item (RASD) element ibm-vim2-zvm5-rasd_2.xsd element of the OVF Descriptor that are specific to the z/VM platform Sample OVF descriptor file for NIM: This topic contains a sample OVF descriptor file for NIM. Description XSD file Extensions to the OVF descriptor that are ibm-vim2_2.dmtf.xsd http://www.org/ovf/envelope/1 dsp8023_1.1.xsd specific to POWER Hypervisor™.xsd" xml:lang="en-US"> <ovf:References> <ovf:File ovf:href="image1.

</ovf:Info> </ovf:InstallSection> <ovf:VirtualHardwareSection ovf:transport="http://www. Its presence indicates that the virtual system needs to be booted after deployment.</rasd:ElementName> <rasd:InstanceID>2</rasd:InstanceID> <rasd:ResourceType>4</rasd:ResourceType> <rasd:VirtualQuantity>3145728</rasd:VirtualQuantity> <vimphyprasd:VirtualLimit>3145728</vimphyprasd:VirtualLimit> <vimphyprasd:VirtualReservation>3145728</vimphyprasd:VirtualReservation> </ovf:Item> <ovf:Item> <rasd:Caption>Virtual Disk Allocation</rasd:Caption> <rasd:Description>Virtual Disk Allocation</rasd:Description> <rasd:ElementName>Virtual Disk Allocation</rasd:ElementName> <rasd:HostResource>ovf:/disk/vimRef1disk</rasd:HostResource> <rasd:InstanceID>5</rasd:InstanceID> <rasd:ResourceType>31</rasd:ResourceType> </ovf:Item> <ovf:Item> <rasd:Caption>Virtual Ethernet Adapter Allocation</rasd:Caption> <rasd:Connection>Virtual Network 1</rasd:Connection> <rasd:Description>Virtual Network 1</rasd:Description> <rasd:ElementName>Allocation of non-IEEE-aware virtual ethernet adapter on Virtual Network 1.0</ovf:Version> <ovf:FullVersion>1.ibm.</rasd:ElementName> <rasd:InstanceID>6</rasd:InstanceID> <rasd:ResourceType>10</rasd:ResourceType> <rasd:VirtualQuantity>1</rasd:VirtualQuantity> </ovf:Item> </ovf:VirtualHardwareSection> <ovf:ProductSection ovf:class="com.</rasd:ElementName> <rasd:InstanceID>1</rasd:InstanceID> <rasd:Limit>10</rasd:Limit> <rasd:Reservation>10</rasd:Reservation> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>1</rasd:VirtualQuantity> <vimphyprasd:VirtualLimit>1</vimphyprasd:VirtualLimit> <vimphyprasd:VirtualReservation>1</vimphyprasd:VirtualReservation> <vimphyprasd:Quantity>10</vimphyprasd:Quantity> <vimphyprasd:ShareMode>cap</vimphyprasd:ShareMode> </ovf:Item> <ovf:Item> <rasd:AllocationUnits>byte * 2^10</rasd:AllocationUnits> <rasd:Caption>Memory Allocation</rasd:Caption> <rasd:ConsumerVisibility>2</rasd:ConsumerVisibility> <rasd:Description>Memory Allocation</rasd:Description> <rasd:ElementName>Allocation of 3072 MB of dedicated memory.5 processing units. to run first-boot customization.0</ovf:FullVersion> <ovf:Category>TCP/IP Network Settings</ovf:Category> <ovf:Property ovf:key="system.1 117 . IBM Systems Director VMControl V2. 0.vim.</ovf:Label> <ovf:Description>Short hostname for the system.2"> <ovf:Info>This product section provides information about the entire package.domainname" ovf:type="string" ovf:userConfigurable="true"> Chapter 2.hostname" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Short hostname for the system.</ovf:Product> <ovf:Vendor>IBM</ovf:Vendor> <ovf:Version>1.com/xmlns/ovf/transport/filesystem/etc/ovf-transport"> <ovf:Info>This section describes the virtual hardware requirements on the target virtual system</ovf:Info> <ovf:System> <vssd:ElementName>VirtualSystem</vssd:ElementName> <vssd:InstanceID>VirtualSystem</vssd:InstanceID> <vssd:VirtualSystemType>IBM:POWER:AIXLINUX</vssd:VirtualSystemType> </ovf:System> <ovf:Item> <rasd:AllocationUnits>percent</rasd:AllocationUnits> <rasd:Caption>Processor Allocation</rasd:Caption> <rasd:ConsumerVisibility>3</rasd:ConsumerVisibility> <rasd:Description>Processor Allocation</rasd:Description> <rasd:ElementName>Allocation of 1 virtual processors.</ovf:Description> </ovf:Property> <ovf:Property ovf:key="system.ibm.ovf.</ovf:Info> <ovf:Product>The name of the product. </ovf:Network> </ovf:NetworkSection> <ovf:VirtualSystem ovf:id="AIX1"> <ovf:Info>This section describes a virtual system to be created when deploying the package</ovf:Info> <ovf:InstallSection> <ovf:Info>This section provides information about the first time boot of the virtual system.

Virtual Network 1&quot.</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport. except: mksysb. master.Virtual Network 1&quot.resources&quot.6.ip" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>IP address of secondary DNS server for the network adapter on &quot.</ovf:Label> <ovf:Description>Static IP address for the network adapter on &quot. ovf_vm.Resource" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>NIM Resource or Resource Group</ovf:Label> <ovf:Description>Specify the name of an existing NIM Resource or NIM Resource Group to allocate during the deployment. Any defined NIM Resource Group.Virtual Network 1&quot.</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.0</ovf:FullVersion> <ovf:Category>NIM-specific settings</ovf:Category> <ovf:Property ovf:key="nim.Virtual Network 1&quot.Virtual Network 1&quot...</ovf:Label> <ovf:Description>Use DHCP for the network adapter on &quot..ovf.Virtual Network 1&quot.netmask" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Static network mask for the network adapter on &quot.6.</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.6..usedhcp" ovf:type="boolean" ovf:userConfigurable="false" ovf:value="false"> <ovf:Label>Use DHCP for the network adapter on &quot.hostname" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Short hostname for the IP address of the network adapter on &quot.6.ovf.ibm..vim...Virtual Network 1&quot.dns1..Virtual Network 1&quot. <ovf:Label>DNS domain name for the system.Virtual Network 1&quot..Virtual Network 1&quot.dns2..ip" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Static IP address for the network adapter on &quot.6.nim.</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.</ovf:Label> <ovf:Description>IP address of primary DNS server for the network adapter on &quot.2" vim:instance="" 118 IBM Systems Director VMControl: Installation and User’s Guide .</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport..</ovf:Label> <ovf:Description>Short hostname for the IP address of the network adapter on &quot. lpp_source..Virtual Network 1&quot.gateway" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Static default gateway for the network adapter on &quot.Virtual Network 1&quot.</ovf:Label> <ovf:Description>DNS domain name for the IP address of the network adapter on &quot.</ovf:Label> <ovf:Description>Static default gateway for the network adapter on &quot.</ovf:Description> </ovf:Property> <vim:Description>Description of the product.Virtual Network 1&quot.6. lpp_source</ovf:Description> </ovf:Property> </ovf:ProductSection> <ovf:OperatingSystemSection ovf:id="9" ovf:version="5"> <ovf:Info>AIX 5 Guest Operating System</ovf:Info> <ovf:Description>IBM AIX 5</ovf:Description> <vim:DiscoveryIpAddress vim:class="com.</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport..Virtual Network 1&quot.6" ovf:instance="1"> <ovf:Info>NIM-specific settings</ovf:Info> <ovf:Product>AIX</ovf:Product> <ovf:Vendor>IBM</ovf:Vendor> <ovf:Version>1.</vim:Description> </ovf:ProductSection> <ovf:ProductSection ovf:class="com. or Resource of class &quot.6.domainname" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>DNS domain name for the IP address of the network adapter on &quot.ibm..vim.</ovf:Label> <ovf:Description>DNS domain name for the system..0</ovf:Version> <ovf:FullVersion>1.</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport..ip" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>IP address of primary DNS server for the network adapter on &quot.Virtual Network 1&quot.</ovf:Label> <ovf:Description>IP address of secondary DNS server for the network adapter on &quot.Virtual Network 1&quot.2. can be specified.6.</ovf:Label> <ovf:Description>Static network mask for the network adapter on &quot. spot.

com/xmlns/ovf/extension/vim/2/zvm/5/rasd ibm-vim2-zvm5-rasd_2.com/xmlns/ovf/extension/vim/2/rasd ibm-vim2-rasd_2. Generally.0.ibm.com/xmlns/ovf/extension/vim/2/zvm/5/rasd" xsi:schemaLocation="http://www.com/xmlns/ovf/extension/vim/2/zvm/5/vssd ibm-vim2-zvm5-vssd_2.xsd" xml:lang="en-us"> <ovf:References> <!-. You can copy and modify this file to create your own OVF descriptor file.gz" ovf:compression="gzip"/> </ovf:References> <ovf:DiskSection> <!-.exustar.This section contains a list of the Linux file systems and swap spaces described by this package.2" vim:instance="" vim:key="networkport.6.star.xsd http://www.linuxfile. --> <ovf:File ovf:id="EXAMPLE2:/boot" ovf:href="EXAMPLE2_boot.dmtf.com/xmlns/ovf/extension/vim/2/zvm/5" xmlns:vimzvmvssd="http://www. --> <ovf:Info>The networks to which virtual network ports connect when deploying this package.gz"/> <ovf:Disk ovf:diskId="EXAMPLE2:/" ovf:capacity="6811549696" ovf:capacityAllocationUnits="byte" ovf:fileRef="EXAMPLE2:/" ovf:format="http://www.xsd http://www.org/2001/XMLSchema-instance" xmlns:vssd="http://schemas.gz" ovf:compression="gzip"/> <ovf:File ovf:id="EXAMPLE2:/opt" ovf:href="EXAMPLE2_opt.1.ibm.0. this will consist of filesystem images.vim.ibm.0.xsd http://schemas.xsd http://www.ibm.ibm.ibm.ibm.star.ibm.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData" xmlns:rasd="http://schemas. --> <ovf:Info>Disk-related information for the Linux file systems included within this package.com/xmlns/ovf/extension/vim/2 ibm-vim2_2.com/xmlns/ovf/diskformat/s390.gz"/> <ovf:Disk ovf:diskId="EXAMPLE2:/opt" ovf:capacity="4227858432" ovf:capacityAllocationUnits="byte" ovf:fileRef="EXAMPLE2:/opt" ovf:format="http://www.star. Network interfaces referring to the same "network" here (with their rasd:Connectionproperty) should be connected to the same network when deployed.com/xmlns/ovf/diskformat/s390.com/xmlns/ovf/diskformat/s390.ibm.exustar.linuxfile.1.ip"/> </ovf:OperatingSystemSection> </ovf:VirtualSystem> </ovf:Envelope> Sample OVF descriptor file for Linux on z/VM with Linux Logical Volume Manager (LVM): This topic contains a sample OVF descriptor file for Linux on z/VM that specifies Linux Logical Volume Manager.gz"/> <ovf:Disk ovf:diskId="EXAMPLE2:swap" ovf:capacity="1040187392" ovf:capacityAllocationUnits="byte"/> </ovf:DiskSection> <ovf:NetworkSection> <!-.0.gz" ovf:compression="gzip"/> <ovf:File ovf:id="EXAMPLE2:/" ovf:href="EXAMPLE2.exustar.com/xmlns/ovf/extension/vim/2/zvm/5/vssd" xmlns:vimzvmrasd="http://www.6.ibm.</ovf:Info> <ovf:Disk ovf:diskId="EXAMPLE2:/boot" ovf:capacity="104841216" ovf:capacityAllocationUnits="byte" ovf:fileRef="EXAMPLE2:/boot" ovf:format="http://www.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData" xmlns:vim="http://www.com/xmlns/ovf/extension/vim/2/zvm/5 ibm-vim2-zvm5_2.ibm.ibm.This section contains a list of files referenced by this OVF package.0.ibm.com/xmlns/ovf/extension/vim/2" xmlns:vimrasd="http://www.w3. <?xml version="1.dmtf.This section contains a list of logical networks to which any network interfaces described in this package are to be connected.dmtf.xsd http://www. IBM Systems Director VMControl V2.org/ovf/envelope/1" xmlns:xsi="http://www.0.1.com/xmlns/ovf/extension/vim/2/rasd" xmlns:vimzvm="http://www.0"?> <ovf:Envelope xmlns:ovf="http://schemas.</ovf:Info> <ovf:Network ovf:name="network1"> <ovf:Description> Chapter 2.ip"/> <vim:NetworkBootIpAddress vim:class="com. along with the size of the volumes which are to contain them and the file format of the image file (if relevant) with which they are to be populated.0.1.1.linuxfile.vim:key="networkport.ovf.org/ovf/envelope/1 dsp8023_1.dmtf.ibm.1 119 .

ibm. See the "MAXSTORAGE Directory Control Statement" section of the IBM z/VM "CP Planning and Administration" guide. such as "G" or "BEG". --> <ovf:Item> <rasd:ElementName>Share for CPU type CP</rasd:ElementName> <rasd:InstanceID>cpushare-cp</rasd:InstanceID> <rasd:ResourceSubType>CP</rasd:ResourceSubType> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>0</rasd:VirtualQuantity> <rasd:Weight>100</rasd:Weight> </ovf:Item> <ovf:Item> <rasd:ElementName>Share for CPU type IFL</rasd:ElementName> <rasd:InstanceID>cpushare-ifl</rasd:InstanceID> <rasd:ResourceSubType>IFL</rasd:ResourceSubType> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>0</rasd:VirtualQuantity> <rasd:Weight>100</rasd:Weight> </ovf:Item> <ovf:Item> <rasd:ElementName>Share for CPU type ICF</rasd:ElementName> <rasd:InstanceID>cpushare-icf</rasd:InstanceID> <rasd:ResourceSubType>ICF</rasd:ResourceSubType> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>0</rasd:VirtualQuantity> <rasd:Weight>100</rasd:Weight> </ovf:Item> <ovf:Item> <rasd:ElementName>Share for CPU type ZAAP</rasd:ElementName> <rasd:InstanceID>cpushare-zaap</rasd:InstanceID> <rasd:ResourceSubType>ZAAP</rasd:ResourceSubType> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>0</rasd:VirtualQuantity> <rasd:Weight>100</rasd:Weight> 120 IBM Systems Director VMControl: Installation and User’s Guide .com/xmlns/ovf/transport/filesystem/etc/ovf-transport"> <!-. --> <ovf:Info>The virtual hardware requirements of the target virtual system.This is a unique identifier for this element within the OVF file. --> <ovf:Info>A virtual system to be created when deploying this package.The disk from which the system is to be IPLed (booted). --> <vimzvmvssd:MaxMemory>1048576</vimzvmvssd:MaxMemory> <vimzvmvssd:MaxMemoryUnits>byte*2^10</vimzvmvssd:MaxMemoryUnits> <!-. For more information. refer to the "SHARE Directory Control Statement" section of the IBM z/VM "CP Planning and Administration" guide.List of z/VM guest privilege classes. --> <vssd:InstanceID>system-EXAMPLE2</vssd:InstanceID> <vssd:VirtualSystemType>IBM:zVM:LINUX</vssd:VirtualSystemType> <!-. --> <vimzvmvssd:PrivilegeClasses>BEG</vimzvmvssd:PrivilegeClasses> <!-. </ovf:Description> </ovf:Network> </ovf:NetworkSection> <ovf:VirtualSystem ovf:id="EXAMPLE2"> <!-. --> <vimzvmvssd:Options>LNKNOPAS LANG AMENG</vimzvmvssd:Options> </ovf:System> <!-.This is the name by which this element should be identified to users in a GUI interface.The following five items specify the "share" values for each of the processor types available on System z.This section sontains information describing the virtual server which can be deployed from this package. the share values used are relative (as opposed to absolute) and no limit is specified.This section contains the virtual hardware requirements of the target virtual system. --> <vssd:ElementName>z/VM system: EXAMPLE2</vssd:ElementName> <!-.Options to be passed at the time of IPL.The maximum virtual storage size to be allowed for this z/VM guest. See the "USER Directory Control Statement" section of the IBM z/VM "CP Planning and Administration" guide.</ovf:Info> <ovf:System> <!-.</ovf:Info> <ovf:Name>EXAMPLE2</ovf:Name> <ovf:VirtualHardwareSection ovf:transport="http://www. See the "IPL Directory Control Statement" section of the IBM z/VM "CP Planning and Administration" guide. A network to which the virtual system in the package is to be connected (default description). See the "OPTION Directory Control Statement" section of the IBM z/VM "CP Planning and Adminstration" guide. In this example. --> <vimzvmvssd:IPLSource>0100</vimzvmvssd:IPLSource> <!-.

--> <ovf:Item> <rasd:ElementName>Memory</rasd:ElementName> <rasd:InstanceID>memory</rasd:InstanceID> <rasd:ResourceType>4</rasd:ResourceType> <rasd:VirtualQuantity>1048576</rasd:VirtualQuantity> <rasd:AllocationUnits>byte*2^10</rasd:AllocationUnits> </ovf:Item> <!-. --> <vimzvmrasd:IOProtocol>ibm:qdio</vimzvmrasd:IOProtocol> <!-. --> <ovf:Item> <rasd:Address>0600</rasd:Address> <rasd:Connection>network1</rasd:Connection> <rasd:ElementName>Network Interface eth0</rasd:ElementName> <rasd:InstanceID>network-interface-eth0</rasd:InstanceID> <rasd:ResourceType>10</rasd:ResourceType> <rasd:VirtualQuantity>1</rasd:VirtualQuantity> <!-. For more information.The following seven items describe disks at the z/VM guest level. --> <vimzvmrasd:Layer>3</vimzvmrasd:Layer> <!-. For more information. Chapter 2. such as 3390 (ECKD) or 9336 (FBA).1 121 . --> <ovf:Item> <rasd:Address>0100</rasd:Address> <rasd:ElementName>Disk: 0100</rasd:ElementName> <rasd:InstanceID>disk-0100</rasd:InstanceID> <!-.This network interface is to be known to the Linux virtual server within this z/VM guest as "eth0". refer to the "NICDEF Directory Control Statement" section of the IBM z/VM "CP Planning and Administration" guide.The amount of memory to be allocated to this system at the time it is IPLed.This always says "count".Network interfaces in z/VM can be either QDIO or Hipersockets adapters. For more information. For more information. --> <rasd:VirtualQuantity>3338</rasd:VirtualQuantity> <!-.The size of the disk in the disk's native units.The "ResourceSubType" here is specifying a family of disk models. </ovf:Item> <ovf:Item> <rasd:ElementName>Share for CPU type ZIIP</rasd:ElementName> <rasd:InstanceID>cpushare-ziip</rasd:InstanceID> <rasd:ResourceSubType>ZIIP</rasd:ResourceSubType> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>0</rasd:VirtualQuantity> <rasd:Weight>100</rasd:Weight> </ovf:Item> <!-. IBM Systems Director VMControl V2. The remaining information is essentially boilerplate. --> <ovf:Item> <rasd:Address>00</rasd:Address> <rasd:ElementName>CPU 00</rasd:ElementName> <rasd:InstanceID>cpu-00</rasd:InstanceID> <rasd:ResourceSubType>CP</rasd:ResourceSubType> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>1</rasd:VirtualQuantity> </ovf:Item> <ovf:Item> <rasd:Address>01</rasd:Address> <rasd:ElementName>CPU 01</rasd:ElementName> <rasd:InstanceID>cpu-01</rasd:InstanceID> <rasd:ResourceSubType>CP</rasd:ResourceSubType> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>1</rasd:VirtualQuantity> </ovf:Item> <!-. refer to the "CPU Directory Control Statement" section of the IBM z/VM "CP Planning and Administration" guide. upon which Linux volumes can be created. which is to be connected to a Layer 3 (IP-address-based) network. --> <rasd:ResourceSubType>ibm:z:3390</rasd:ResourceSubType> <rasd:ResourceType>31</rasd:ResourceType> <!-.The following two items refer to actual virtual CPUs. Not a particularly useful unit. refer to the "MDISK Directory Control Statement" section of the IBM z/VM "CP Planning and Administration" guide.This sytem's network interface. All three are of type "CP". --> <vimzvm:NetworkPortConfigProposal vimzvm:nicdev="eth0"/> </ovf:Item> <!-. refer to the "STORAGE Directory Control Statment" section of the IBM z/VM "CP Planning and Administration" guide.The network layer can be either "2" or "3".

Possibile values include "R". but required for compatibility with some pre-existing data structures. --> <vimzvmrasd:VirtualQuantityUnits>count</vimzvmrasd:VirtualQuantityUnits> <!-. These values are described in full under the "MDISK" section in the "CP Planning and Administration Guide". Other sizes. "MR". "W". like "512" and "1024" are FBA block sizes. in bytes and as seen by a Linux system accessing that disk. Other options include "minidisk-devno". --> <vimzvmrasd:AccessMode>W</vimzvmrasd:AccessMode> </ovf:Item> <ovf:Item> <rasd:Address>0101</rasd:Address> <rasd:ElementName>Disk: 0101</rasd:ElementName> <rasd:InstanceID>disk-0101</rasd:InstanceID> <rasd:ResourceSubType>ibm:z:3390</rasd:ResourceSubType> <rasd:ResourceType>31</rasd:ResourceType> <rasd:VirtualQuantity>3338</rasd:VirtualQuantity> <vimzvmrasd:VirtualQuantityUnits>count</vimzvmrasd:VirtualQuantityUnits> <vimzvmrasd:VirtualResourceBlockSize>737280</vimzvmrasd:VirtualResourceBlockSize> <vimzvmrasd:DiskTechnology>minidisk-volser</vimzvmrasd:DiskTechnology> <vimzvmrasd:AccessMode>W</vimzvmrasd:AccessMode> </ovf:Item> <ovf:Item> <rasd:Address>0102</rasd:Address> <rasd:ElementName>Disk: 0102</rasd:ElementName> <rasd:InstanceID>disk-0102</rasd:InstanceID> <rasd:ResourceSubType>ibm:z:3390</rasd:ResourceSubType> <rasd:ResourceType>31</rasd:ResourceType> <rasd:VirtualQuantity>3338</rasd:VirtualQuantity> <vimzvmrasd:VirtualQuantityUnits>count</vimzvmrasd:VirtualQuantityUnits> <vimzvmrasd:VirtualResourceBlockSize>737280</vimzvmrasd:VirtualResourceBlockSize> <vimzvmrasd:DiskTechnology>minidisk-volser</vimzvmrasd:DiskTechnology> <vimzvmrasd:AccessMode>W</vimzvmrasd:AccessMode> </ovf:Item> <ovf:Item> <rasd:Address>0103</rasd:Address> <rasd:ElementName>Disk: 0103</rasd:ElementName> <rasd:InstanceID>disk-0103</rasd:InstanceID> <rasd:ResourceSubType>ibm:z:3390</rasd:ResourceSubType> <rasd:ResourceType>31</rasd:ResourceType> <rasd:VirtualQuantity>3338</rasd:VirtualQuantity> <vimzvmrasd:VirtualQuantityUnits>count</vimzvmrasd:VirtualQuantityUnits> <vimzvmrasd:VirtualResourceBlockSize>737280</vimzvmrasd:VirtualResourceBlockSize> <vimzvmrasd:DiskTechnology>minidisk-volser</vimzvmrasd:DiskTechnology> <vimzvmrasd:AccessMode>W</vimzvmrasd:AccessMode> </ovf:Item> <ovf:Item> <rasd:Address>0104</rasd:Address> <rasd:ElementName>Disk: 0104</rasd:ElementName> <rasd:InstanceID>disk-0104</rasd:InstanceID> <rasd:ResourceSubType>ibm:z:3390</rasd:ResourceSubType> <rasd:ResourceType>31</rasd:ResourceType> <rasd:VirtualQuantity>3238</rasd:VirtualQuantity> <vimzvmrasd:VirtualQuantityUnits>count</vimzvmrasd:VirtualQuantityUnits> <vimzvmrasd:VirtualResourceBlockSize>737280</vimzvmrasd:VirtualResourceBlockSize> <vimzvmrasd:DiskTechnology>minidisk-volser</vimzvmrasd:DiskTechnology> <vimzvmrasd:AccessMode>W</vimzvmrasd:AccessMode> </ovf:Item> <ovf:Item> <rasd:Address>0300</rasd:Address> <rasd:ElementName>Disk: 0300</rasd:ElementName> <rasd:InstanceID>disk-0300</rasd:InstanceID> <rasd:ResourceSubType>ibm:z:9336</rasd:ResourceSubType> <rasd:ResourceType>31</rasd:ResourceType> <rasd:VirtualQuantity>524288</rasd:VirtualQuantity> <vimzvmrasd:VirtualQuantityUnits>count</vimzvmrasd:VirtualQuantityUnits> <vimzvmrasd:VirtualResourceBlockSize>512</vimzvmrasd:VirtualResourceBlockSize> <vimzvmrasd:DiskTechnology>vdisk</vimzvmrasd:DiskTechnology> <vimzvmrasd:AccessMode>MR</vimzvmrasd:AccessMode> </ovf:Item> <ovf:Item> 122 IBM Systems Director VMControl: Installation and User’s Guide . --> <vimzvmrasd:VirtualResourceBlockSize>737280</vimzvmrasd:VirtualResourceBlockSize> <!-. "vdisk". The "737280" here refers to the size of a 3390 ECKD cylinder after low-level DASD formatting.The disk's access mode.The size of the disk's native unit. "WR". "RR". and "MW". --> <vimzvmrasd:DiskTechnology>minidisk-volser</vimzvmrasd:DiskTechnology> <!-. and "dedicated". "M".Disk provisioning/allocation method.

eth0. if not using DHCP (IP V4 or V6 format)</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.eth0.The product sections contain information describing this package and a listing of values which must be collected at deploy time to generate an OVF Environment file (this is an OVF Envelope file) to be used by the Activation Engine on the deployed system.</ovf:Product> <ovf:Category>General Settings</ovf:Category> <ovf:Property ovf:key="timezone.vim.zvm.eth0.dns1.2.</vim:Description> </ovf:ProductSection> <ovf:ProductSection ovf:class="com.eth0.ibm.eth0.gateway" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Default gateway for eth0</ovf:Label> <ovf:Description>Default gateway for eth0. <rasd:Address>0301</rasd:Address> <rasd:ElementName>Disk: 0301</rasd:ElementName> <rasd:InstanceID>disk-0301</rasd:InstanceID> <rasd:ResourceSubType>ibm:z:9336</rasd:ResourceSubType> <rasd:ResourceType>31</rasd:ResourceType> <rasd:VirtualQuantity>1048576</rasd:VirtualQuantity> <vimzvmrasd:VirtualQuantityUnits>count</vimzvmrasd:VirtualQuantityUnits> <vimzvmrasd:VirtualResourceBlockSize>512</vimzvmrasd:VirtualResourceBlockSize> <vimzvmrasd:DiskTechnology>vdisk</vimzvmrasd:DiskTechnology> <vimzvmrasd:AccessMode>MR</vimzvmrasd:AccessMode> </ovf:Item> </ovf:VirtualHardwareSection> <!-.</ovf:Info> <ovf:Product>Red Hat Enterprise Linux Server release 5.eth0. IBM Systems Director VMControl V2. if not using DHCP (IP V4 or V6 format) </ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.</ovf:Info> <ovf:Product ovf:msgid="translateID22">ExampleWithLVM</ovf:Product> <vim:Description ovf:msgid="translateID23">Example system with LVM volume groups. if not using DHCP (IP V4 or V6 format)</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.3 on z/VM.eth0.registerindns" ovf:type="boolean" ovf:userConfigurable="true" ovf:value="true"> <ovf:Label>Register eth0 with DNS server</ovf:Label> Chapter 2.dns2. if not using DHCP (IP V4 or V6 format) </ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.ip" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>IP address of secondary DNS server for eth0</ovf:Label> <ovf:Description> IP address of secondary DNS server for eth0.netmask" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Network mask for eth0</ovf:Label> <ovf:Description>Network mask for eth0.ip" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>IP address of primary DNS server for eth0</ovf:Label> <ovf:Description> IP address of primary DNS server for eth0.ip" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>IP Address for eth0</ovf:Label> <ovf:Description>IP Address for eth0.ovf.5"> <ovf:Info>This section describes the customizable properties of this virtual system.usedhcp" ovf:type="boolean" ovf:userConfigurable="true" ovf:value="false"> <ovf:Label>Use DHCP for eth0</ovf:Label> <ovf:Description>Use DHCP for eth0</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.offset" ovf:type="uint16" ovf:userConfigurable="true" ovf:value="-0400"> <ovf:Label>Timezone Offset</ovf:Label> <ovf:Description>Timezone Offset</ovf:Description> </ovf:Property> <ovf:Category>TCP/IP Network Settings</ovf:Category> <ovf:Property ovf:key="networkport. --> <ovf:ProductSection> <ovf:Info>This section describes the OVF package itself. if not using DHCP (IP V4 or V6 format)</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.1 123 .

eth0.The LinuxFileSystemSection defines a partition. provides a configuration proposal for each file system.hostname" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Short hostname for the system</ovf:Label> <ovf:Description>Short hostname for the system</ovf:Description> </ovf:Property> <ovf:Property ovf:key="system. and that partition will have a capacity of 2133 49152-byte tracks.</ovf:Info> <ovf:Description>Red Hat Enterprise Linux Server release 5.domainname" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>DNS domain name for the system</ovf:Label> <ovf:Description>DNS domain name for the system</ovf:Description> </ovf:Property> </ovf:ProductSection> <ovf:AnnotationSection> <ovf:Info>Additional annotation for the virtual system</ovf:Info> <ovf:Annotation>z/VM system: EXAMPLE2</ovf:Annotation> </ovf:AnnotationSection> <ovf:OperatingSystemSection ovf:id="36" kernel="2.domainname" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Domain name for eth0</ovf:Label> <ovf:Description>Domain name for eth0</ovf:Description> </ovf:Property> <ovf:Property ovf:key="system.eth0. with some additional information as required to recreate the original partitioning scheme and LVM configuration.18-128. </ovf:Info> </ovf:InstallSection> <vimzvm:LinuxFileSystemSection ovf:required="true"> <!-. --> <vimzvm:LinuxPartition vimzvm:partNum="1" vimzvm:partSize="2133" vimzvm:partSizeUnits="TRK" vimzvm:partBytesPerUnit="49152"/> <vimzvm:LogicalDiskRef vimzvm:itemRef="disk-0100"/> </vimzvm:ConfigProposal> </vimzvm:FileSystem> <vimzvm:FileSystem vimzvm:diskRef="EXAMPLE2:/opt" vimzvm:mountPoint="/opt"> <vimzvm:ConfigProposal> <vimzvm:LinuxMount vimzvm:devSpec="/dev/VG0/LV4opt" vimzvm:mountOptions="defaults" vimzvm:dump="1" vimzvm:fsckPassNo="2"/> 124 IBM Systems Director VMControl: Installation and User’s Guide . formatting. --> <ovf:Info> Defines how the image files (containing Linux file system content) are deployed to Linux mount points. and mounting scheme which is to be used to re-create the virtual server's Linux file systems.hostname" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Hostname for eth0</ovf:Label> <ovf:Description>Hostname for eth0</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.6.el5"> <ovf:Info>Information about the operating system in the virtual system. --> <vimzvm:LinuxMount vimzvm:devSpec="LABEL=/boot1" vimzvm:mountOptions="defaults" vimzvm:dump="1" vimzvm:fsckPassNo="2"/> <vimzvm:LinuxFileSystem vimzvm:type="ext3" vimzvm:label="/boot1"/> <!-.The information in these "ConfigProposal" elements essentially lines up with what is specified in /etc/fstab.This file system goes on the first partition of the z/VM guest's 0100 disk. </ovf:Info> <vimzvm:FileSystem vimzvm:diskRef="EXAMPLE2:/boot" vimzvm:mountPoint="/boot"> <vimzvm:ConfigProposal> <!-. <ovf:Description>Register IP address and long DNS hostname of eth0 with the DNS server</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport. Optionally.3</ovf:Description> </ovf:OperatingSystemSection> <ovf:InstallSection> <ovf:Info> Indicates that the system needs to be booted after deployment to run first-boot customization.

This section described the virtual server's LVM configuration. --> <ovf:Info> Defines a configuration proposal for the Linux LVM2. <vimzvm:LinuxFileSystem vimzvm:type="ext3" vimzvm:label=""/> <!-.0. --> <vimzvm:PhysicalVolume vimzvm:devNode="/dev/disk/by-path/ccw-0. The volume groups defined here are referenced by the Linux file system configuration proposals in the LinuxFileSystemSection.0102-part1" vimzvm:pvOptions="a-"> <vimzvm:LinuxPartition vimzvm:partNum="1" vimzvm:partSize="50068" vimzvm:partSizeUnits="TRK" vimzvm:partBytesPerUnit="49152"/> <vimzvm:LogicalDiskRef vimzvm:itemRef="disk-0102"/> </vimzvm:PhysicalVolume> Chapter 2.0100-part2" vimzvm:pvOptions="a-"> <vimzvm:LinuxPartition vimzvm:partNum="2" vimzvm:partSize="47935" vimzvm:partSizeUnits="TRK" vimzvm:partBytesPerUnit="49152"/> <vimzvm:LogicalDiskRef vimzvm:itemRef="disk-0100"/> </vimzvm:PhysicalVolume> <vimzvm:PhysicalVolume vimzvm:devNode="/dev/disk/by-path/ccw-0. </ovf:Info> <vimzvm:ConfigProposal> <vimzvm:VolumeGroup vimzvm:name="VG0" vimzvm:vgOptions="wz--n-"> <!-.This file system will be placed on an LVM logical volume named "LV4opt" in the volume group "VG0". --> <vimzvm:LinuxLogicalVolume vimzvm:lvName="LV4opt" vimzvm:vgName="VG0" vimzvm:lvSize="4227858432" vimzvm:lvSizeUnits="byte"/> </vimzvm:ConfigProposal> </vimzvm:FileSystem> <vimzvm:FileSystem vimzvm:diskRef="EXAMPLE2:/" vimzvm:mountPoint="/"> <vimzvm:ConfigProposal> <vimzvm:LinuxMount vimzvm:devSpec="/dev/VG0/LV4slash" vimzvm:mountOptions="defaults" vimzvm:dump="1" vimzvm:fsckPassNo="1"/> <vimzvm:LinuxFileSystem vimzvm:type="ext3" vimzvm:label=""/> <vimzvm:LinuxLogicalVolume vimzvm:lvName="LV4slash" vimzvm:vgName="VG0" vimzvm:lvSize="6811549696" vimzvm:lvSizeUnits="byte"/> </vimzvm:ConfigProposal> </vimzvm:FileSystem> <vimzvm:FileSystem vimzvm:diskRef="EXAMPLE2:swap" vimzvm:mountPoint="swap"> <vimzvm:ConfigProposal> <vimzvm:LinuxMount vimzvm:devSpec="/dev/VG0/LV4swap" vimzvm:mountOptions="defaults" vimzvm:dump="0" vimzvm:fsckPassNo="0"/> <vimzvm:LinuxFileSystem vimzvm:type="swap" vimzvm:label=""/> <vimzvm:LinuxLogicalVolume vimzvm:lvName="LV4swap" vimzvm:vgName="VG0" vimzvm:lvSize="1040187392" vimzvm:lvSizeUnits="byte"/> </vimzvm:ConfigProposal> </vimzvm:FileSystem> </vimzvm:LinuxFileSystemSection> <vimzvm:LinuxLVMSection ovf:required="false"> <!-.1 125 .0. IBM Systems Director VMControl V2. The physical volumes defined here reference logical disks.0101-part1" vimzvm:pvOptions="a-"> <vimzvm:LinuxPartition vimzvm:partNum="1" vimzvm:partSize="50068" vimzvm:partSizeUnits="TRK" vimzvm:partBytesPerUnit="49152"/> <vimzvm:LogicalDiskRef vimzvm:itemRef="disk-0101"/> </vimzvm:PhysicalVolume> <vimzvm:PhysicalVolume vimzvm:devNode="/dev/disk/by-path/ccw-0.0. or Item elements of ResourceType=31 (LogicalDisk).This volume group (VG0) is provisioned from the following five "physical" volumes.

</ovf:Info> <ovf:Disk ovf:diskId="EXAMPLE1:/" ovf:capacity="2460303360" ovf:capacityAllocationUnits="byte" ovf:fileRef="EXAMPLE1:/" ovf:format="http://www.0.dmtf.1.0103-part1" vimzvm:pvOptions="a-"> <vimzvm:LinuxPartition vimzvm:partNum="1" vimzvm:partSize="50068" vimzvm:partSizeUnits="TRK" vimzvm:partBytesPerUnit="49152"/> <vimzvm:LogicalDiskRef vimzvm:itemRef="disk-0103"/> </vimzvm:PhysicalVolume> <vimzvm:PhysicalVolume vimzvm:devNode="/dev/disk/by-path/ccw-0.xsd http://www.xsd http://www.0.com/xmlns/ovf/extension/vim/2/zvm/5/rasd" xsi:schemaLocation="http://www.1.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData" xmlns:rasd="http://schemas.ibm.dmtf.dmtf. along with the size of the volumes which are to contain them and the file format of the image file (if relevant) with which they are to be populated.1.exustar.0"?> <ovf:Envelope xmlns:ovf="http://schemas.star.1.ibm.</ovf:Info> 126 IBM Systems Director VMControl: Installation and User’s Guide .ibm.ibm.ibm.0.0104-part1" vimzvm:pvOptions="a-"> <vimzvm:LinuxPartition vimzvm:partNum="1" vimzvm:partSize="48568" vimzvm:partSizeUnits="TRK" vimzvm:partBytesPerUnit="49152"/> <vimzvm:LogicalDiskRef vimzvm:itemRef="disk-0104"/> </vimzvm:PhysicalVolume> </vimzvm:VolumeGroup> </vimzvm:ConfigProposal> </vimzvm:LinuxLVMSection> </ovf:VirtualSystem> </ovf:Envelope> Sample OVF descriptor file for Linux on z/VM without Linux Logical Volume Manager (LVM): This topic contains a sample OVF descriptor file for Linux on z/VM.0.linuxfile.xsd http://www.1.xsd" xml:lang="en-us"> <ovf:References> <!-.0.org/ovf/envelope/1" xmlns:xsi="http://www.0.ibm.0.This section contains a list of the Linux file systems and swap spaces described by this package.xsd http://www.This section contains a list of logical networks to which any network interfaces described in this package are to be connected.com/xmlns/ovf/extension/vim/2/zvm/5/vssd" xmlns:vimzvmrasd="http://www. Network interfaces referring to the same "network" here (with their rasd:Connection property) should be connected to the same network when deployed.ibm. --> <ovf:Info>Disk-related information for the Linux file systems included within this package.ibm.0.ibm.xsd http://schemas.w3.com/xmlns/ovf/extension/vim/2" xmlns:vimrasd="http://www.gz"/> <ovf:Disk ovf:diskId="EXAMPLE1:swap1" ovf:capacity="266203136" ovf:capacityAllocationUnits="byte"/> <ovf:Disk ovf:diskId="EXAMPLE1:swap2" ovf:capacity="532409344" ovf:capacityAllocationUnits="byte"/> </ovf:DiskSection> <ovf:NetworkSection> <!-.com/xmlns/ovf/extension/vim/2/zvm/5" xmlns:vimzvmvssd="http://www.com/xmlns/ovf/extension/vim/2/zvm/5 ibm-vim2-zvm5_2.This section contains a list of files referenced by this OVF package. <vimzvm:PhysicalVolume vimzvm:devNode="/dev/disk/by-path/ccw-0.com/xmlns/ovf/extension/vim/2/zvm/5/rasd ibm-vim2-zvm5-rasd_2.org/ovf/envelope/1 dsp8023_1. this will consist of filesystem images.ibm. Generally.com/xmlns/ovf/diskformat/s390. You can copy and modify this file to create your own OVF descriptor file.gz" ovf:compression="gzip"/> </ovf:References> <ovf:DiskSection> <!-.ibm.0.org/2001/XMLSchema-instance" xmlns:vssd="http://schemas.dmtf.com/xmlns/ovf/extension/vim/2/rasd ibm-vim2-rasd_2.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData" xmlns:vim="http://www. --> <ovf:Info>The networks to which virtual network ports connect when deploying this package.com/xmlns/ovf/extension/vim/2/zvm/5/vssd ibm-vim2-zvm5-vssd_2. --> <ovf:File ovf:id="EXAMPLE1:/" ovf:href="EXAMPLE1.com/xmlns/ovf/extension/vim/2/rasd" xmlns:vimzvm="http://www. <?xml version="1.com/xmlns/ovf/extension/vim/2 ibm-vim2_2.

IBM Systems Director VMControl V2.The following five items specify the "share" values for each of the processor types available on System z.The disk from which the system is to be IPLed (booted). --> <ovf:Item> <rasd:ElementName>Share for CPU type CP</rasd:ElementName> <rasd:InstanceID>cpushare-cp</rasd:InstanceID> <rasd:ResourceSubType>CP</rasd:ResourceSubType> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>0</rasd:VirtualQuantity> </ovf:Item> <ovf:Item> <rasd:ElementName>Share for CPU type IFL</rasd:ElementName> <rasd:InstanceID>cpushare-ifl</rasd:InstanceID> <rasd:ResourceSubType>IFL</rasd:ResourceSubType> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>0</rasd:VirtualQuantity> <rasd:Weight>100</rasd:Weight> </ovf:Item> <ovf:Item> <rasd:ElementName>Share for CPU type ICF</rasd:ElementName> <rasd:InstanceID>cpushare-icf</rasd:InstanceID> <rasd:ResourceSubType>ICF</rasd:ResourceSubType> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>0</rasd:VirtualQuantity> Chapter 2. such as "G" or "BEG". For more information. See the "USER Directory Control Statement" section of the IBM z/VM "CP Planning and Administration" guide.This is the name by which this element should be identified to users in a GUI interface. See the "OPTION Directory Control Statement" section of the IBM z/VM "CP Planning and Adminstration" guide. --> <vimzvmvssd:IPLSource>0100</vimzvmvssd:IPLSource> <!-. </ovf:Description> </ovf:Network> <ovf:Network ovf:name="network2"> <ovf:Description> A network to which the virtual system in the package is to be connected (default description). --> <ovf:Info>The virtual hardware requirements of the target virtual system. the share values used are relative (as opposed to absolute) and no limit is specified.</ovf:Info> <ovf:Name>EXAMPLE1</ovf:Name> <ovf:VirtualHardwareSection ovf:transport="http://www.This section contains the virtual hardware requirements of the target virtual system. </ovf:Description> </ovf:Network> </ovf:NetworkSection> <ovf:VirtualSystem ovf:id="EXAMPLE1"> <!-. --> <ovf:Info>A virtual system to be created when deploying this package. See the "IPL Directory Control Statement" section of the IBM z/VM "CP Planning and Administration" guide.1 127 .com/xmlns/ovf/transport/filesystem/etc/ovf-transport"> <!-. --> <vssd:ElementName>z/VM system: EXAMPLE1</vssd:ElementName> <!-. --> <vimzvmvssd:PrivilegeClasses>G</vimzvmvssd:PrivilegeClasses> <!-.This section contains information describing the virtual server which can be deployed from this package.ibm.This is a unique identifier for this element within the OVF file.</ovf:Info> <ovf:System> <!-.The maximum virtual storage size to be allowed for this z/VM guest. --> <vssd:InstanceID>system-EXAMPLE1</vssd:InstanceID> <vssd:VirtualSystemType>IBM:zVM:LINUX</vssd:VirtualSystemType> <!-. See the "MAXSTORAGE Directory Control Statement" section of the IBM z/VM "CP Planning and Administration" guide. <ovf:Network ovf:name="network1"> <ovf:Description> A network to which the virtual system in the package is to be connected (default description). --> <vimzvmvssd:Options>APPLMON</vimzvmvssd:Options> </ovf:System> <!-.List of z/VM guest privilege classes. --> <vimzvmvssd:MaxMemory>393216</vimzvmvssd:MaxMemory> <vimzvmvssd:MaxMemoryUnits>byte*2^10</vimzvmvssd:MaxMemoryUnits> <!-.Options to be passed at the time of IPL. refer to the "SHARE Directory Control Statement" section of the IBM z/VM "CP Planning and Administration" guide. In this example.

--> <vimzvmrasd:Layer>3</vimzvmrasd:Layer> 128 IBM Systems Director VMControl: Installation and User’s Guide . For more information.The network layer can be either "2" or "3". All three are of type "CP".The following two items describe this sytem's network interfaces.The amount of memory to be allocated to this system at the time it is IPLed. --> <vimzvmrasd:IOProtocol>ibm:qdio</vimzvmrasd:IOProtocol> <!-. The first is to be connected to a Layer 3 (IP-address-based) network. For more information. --> <ovf:Item> <!-. while the second is to be connected to a Layer 2 (MAC-address-based) network.The rasd:Address field is used for non-processor items to represent the virtual device channel with which the virtual hardware item is to be associated. The remaining information is essentially boilerplate.Network interfaces in z/VM can be either QDIO or Hipersockets adapters. refer to the "CPU Directory Control Statement" section of the IBM z/VM "CP Planning and Administration" guide. For more information. --> <rasd:Address>0600</rasd:Address> <rasd:Connection>network1</rasd:Connection> <rasd:ElementName>Network Interface eth0</rasd:ElementName> <rasd:InstanceID>network-interface-eth0</rasd:InstanceID> <rasd:ResourceType>10</rasd:ResourceType> <rasd:VirtualQuantity>1</rasd:VirtualQuantity> <!-. --> <ovf:Item> <rasd:Address>00</rasd:Address> <rasd:ElementName>CPU 00</rasd:ElementName> <rasd:InstanceID>cpu-00</rasd:InstanceID> <rasd:ResourceSubType>CP</rasd:ResourceSubType> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>1</rasd:VirtualQuantity> </ovf:Item> <ovf:Item> <rasd:Address>01</rasd:Address> <rasd:ElementName>CPU 01</rasd:ElementName> <rasd:InstanceID>cpu-01</rasd:InstanceID> <rasd:ResourceSubType>CP</rasd:ResourceSubType> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>1</rasd:VirtualQuantity> </ovf:Item> <ovf:Item> <rasd:Address>02</rasd:Address> <rasd:ElementName>CPU 02</rasd:ElementName> <rasd:InstanceID>cpu-02</rasd:InstanceID> <rasd:ResourceSubType>CP</rasd:ResourceSubType> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>1</rasd:VirtualQuantity> </ovf:Item> <!-. refer to the "STORAGE Directory Control Statment" section of the IBM z/VM "CP Planning and Administration" guide.The following three items refer to actual virtual CPUs. refer to the "NICDEF Directory Control Statement" section of the IBM z/VM "CP Planning and Administration" guide. --> <ovf:Item> <rasd:ElementName>Memory</rasd:ElementName> <rasd:InstanceID>memory</rasd:InstanceID> <rasd:ResourceType>4</rasd:ResourceType> <rasd:VirtualQuantity>393216</rasd:VirtualQuantity> <rasd:AllocationUnits>byte*2^10</rasd:AllocationUnits> </ovf:Item> <!-. <rasd:Weight>100</rasd:Weight> </ovf:Item> <ovf:Item> <rasd:ElementName>Share for CPU type ZAAP</rasd:ElementName> <rasd:InstanceID>cpushare-zaap</rasd:InstanceID> <rasd:ResourceSubType>ZAAP</rasd:ResourceSubType> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>0</rasd:VirtualQuantity> <rasd:Weight>100</rasd:Weight> </ovf:Item> <ovf:Item> <rasd:ElementName>Share for CPU type ZIIP</rasd:ElementName> <rasd:InstanceID>cpushare-ziip</rasd:InstanceID> <rasd:ResourceSubType>ZIIP</rasd:ResourceSubType> <rasd:ResourceType>3</rasd:ResourceType> <rasd:VirtualQuantity>0</rasd:VirtualQuantity> <rasd:Weight>100</rasd:Weight> </ovf:Item> <!-.

This always says "count". For more information. These values are described in full under the "MDISK" section in the "CP Planning and Administration Guide". --> <vimzvmrasd:AccessMode>W</vimzvmrasd:AccessMode> </ovf:Item> <ovf:Item> <rasd:Address>0300</rasd:Address> <rasd:ElementName>Disk: 0300</rasd:ElementName> <rasd:InstanceID>disk-0300</rasd:InstanceID> <rasd:ResourceSubType>ibm:z:9336</rasd:ResourceSubType> <rasd:ResourceType>31</rasd:ResourceType> <rasd:VirtualQuantity>524288</rasd:VirtualQuantity> <vimzvmrasd:VirtualQuantityUnits>count</vimzvmrasd:VirtualQuantityUnits> <vimzvmrasd:VirtualResourceBlockSize>512</vimzvmrasd:VirtualResourceBlockSize> <vimzvmrasd:DiskTechnology>vdisk</vimzvmrasd:DiskTechnology> <vimzvmrasd:AccessMode>MR</vimzvmrasd:AccessMode> </ovf:Item> <ovf:Item> <rasd:Address>0301</rasd:Address> <rasd:ElementName>Disk: 0301</rasd:ElementName> <rasd:InstanceID>disk-0301</rasd:InstanceID> <rasd:ResourceSubType>ibm:z:9336</rasd:ResourceSubType> <rasd:ResourceType>31</rasd:ResourceType> <rasd:VirtualQuantity>1048576</rasd:VirtualQuantity> <vimzvmrasd:VirtualQuantityUnits>count</vimzvmrasd:VirtualQuantityUnits> <vimzvmrasd:VirtualResourceBlockSize>512</vimzvmrasd:VirtualResourceBlockSize> <vimzvmrasd:DiskTechnology>vdisk</vimzvmrasd:DiskTechnology> <vimzvmrasd:AccessMode>MR</vimzvmrasd:AccessMode> </ovf:Item> </ovf:VirtualHardwareSection> <!-. like "512" and "1024" are FBA block sizes.The size of the disk in the disk's native units. "vdisk". "M". Possibile values include "R". Other sizes. refer to the "MDISK Directory Control Statement" section of the IBM z/VM "CP Planning and Administration" guide. IBM Systems Director VMControl V2.The disk's access mode. "RR". The "737280" here refers to the size of a 3390 ECKD cylinder after low-level DASD formatting.The size of the disk's native unit. but required for compatibility with some pre-existing data structures. --> <rasd:ResourceSubType>ibm:z:3390</rasd:ResourceSubType> <rasd:ResourceType>31</rasd:ResourceType> <!-.The product sections contain information describing this package and Chapter 2. --> <vimzvmrasd:DiskTechnology>minidisk-volser</vimzvmrasd:DiskTechnology> <!-.The "ResourceSubType" here is specifying a family of disk models. --> <rasd:VirtualQuantity>3338</rasd:VirtualQuantity> <!-. upon which Linux volumes can be created. --> <ovf:Item> <rasd:Address>0100</rasd:Address> <rasd:ElementName>Disk: 0100</rasd:ElementName> <rasd:InstanceID>disk-0100</rasd:InstanceID> <!-. such as 3390 (ECKD) or 9336 (FBA). "WR".1 129 . Other options include "minidisk-devno". in bytes and as seen by a Linux system accessing that disk.Disk provisioning/allocation method. --> <vimzvm:NetworkPortConfigProposal vimzvm:nicdev="eth0"/> </ovf:Item> <ovf:Item> <rasd:Address>0700</rasd:Address> <rasd:Connection>network2</rasd:Connection> <rasd:ElementName>Network Interface eth1</rasd:ElementName> <rasd:InstanceID>network-interface-eth1</rasd:InstanceID> <rasd:ResourceType>10</rasd:ResourceType> <rasd:VirtualQuantity>1</rasd:VirtualQuantity> <vimzvmrasd:IOProtocol>ibm:qdio</vimzvmrasd:IOProtocol> <vimzvmrasd:Layer>2</vimzvmrasd:Layer> <vimzvm:NetworkPortConfigProposal vimzvm:nicdev="eth1"/> </ovf:Item> <!-. and "MW".This network interface is to be known to the Linux virtual server within this z/VM guest as "eth0". Not a partucularly useful unit.The following three items describe disks at the z/VM guest level. --> <vimzvmrasd:VirtualResourceBlockSize>737280</vimzvmrasd:VirtualResourceBlockSize> <!-. --> <vimzvmrasd:VirtualQuantityUnits>count</vimzvmrasd:VirtualQuantityUnits> <!-. and "dedicated". "W". "MR". <!-.

registerindns" ovf:type="boolean" ovf:userConfigurable="true" ovf:value="true"> <ovf:Label>Register eth0 with DNS server</ovf:Label> <ovf:Description>Register IP address and long DNS hostname of eth0 with the DNS server</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.2.eth0.vim. if not using DHCP (IP V4 or V6 format) </ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.eth0.</ovf:Product> <ovf:Category>General Settings</ovf:Category> <ovf:Property ovf:key="timezone.zvm.netmask" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Network mask for eth0</ovf:Label> <ovf:Description>Network mask for eth0.5"> <ovf:Info>This section describes the customizable properties of this virtual system. if not using DHCP (IP V4 or V6 format) </ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport. a listing of values which must be collected at deploy time to generate an OVF Environment file (this is an OVF Envelope file) to be used by the Activation Engine on the deployed system.eth0.dns1.usedhcp" ovf:type="boolean" ovf:userConfigurable="true" ovf:value="false"> <ovf:Label>Use DHCP for eth0</ovf:Label> <ovf:Description>Use DHCP for eth0</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.</ovf:Info> <ovf:Product ovf:msgid="translateID22">ExampleWithoutLVM</ovf:Product> <vim:Description ovf:msgid="translateID23">An example system with no LVM volume groups.hostname" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Hostname for eth0</ovf:Label> <ovf:Description>Hostname for eth0</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.dns2. if not using DHCP (IP V4 or V6 format)</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.eth0.ovf.</ovf:Info> <ovf:Product>SUSE Linux Enterprise Server 11 on z/VM.ibm.offset" ovf:type="uint16" ovf:userConfigurable="true" ovf:value="-0400"> <ovf:Label>Timezone Offset</ovf:Label> <ovf:Description>Timezone Offset</ovf:Description> </ovf:Property> <ovf:Category>TCP/IP Network Settings</ovf:Category> <ovf:Property ovf:key="networkport. --> <ovf:ProductSection> <ovf:Info>This section describes the OVF package itself.eth0.ip" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>IP address of primary DNS server for eth0</ovf:Label> <ovf:Description> IP address of primary DNS server for eth0.</vim:Description> </ovf:ProductSection> <ovf:ProductSection ovf:class="com.eth0.eth0.eth0.eth0.ip" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>IP address of secondary DNS server for eth0</ovf:Label> <ovf:Description> IP address of secondary DNS server for eth0.ip" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>IP Address for eth0</ovf:Label> <ovf:Description>IP Address for eth0. if not using DHCP (IP V4 or V6 format)</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport. if not using DHCP (IP V4 or V6 format)</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.gateway" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Default gateway for eth0</ovf:Label> <ovf:Description>Default gateway for eth0.domainname" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Domain name for eth0</ovf:Label> <ovf:Description>Domain name for eth0</ovf:Description> 130 IBM Systems Director VMControl: Installation and User’s Guide .

registerindns" ovf:type="boolean" ovf:userConfigurable="true" ovf:value="true"> <ovf:Label>Register eth1 with DNS server</ovf:Label> <ovf:Description>Register IP address and long DNS hostname of eth1 with the DNS server</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.domainname" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>DNS domain name for the system</ovf:Label> <ovf:Description>DNS domain name for the system</ovf:Description> </ovf:Property> </ovf:ProductSection> <ovf:AnnotationSection> <ovf:Info>Additional annotation for the virtual system</ovf:Info> <ovf:Annotation>z/VM system: EXAMPLE1</ovf:Annotation> </ovf:AnnotationSection> <ovf:OperatingSystemSection ovf:id="36" kernel="2.ip" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>IP address of primary DNS server for eth1</ovf:Label> <ovf:Description> IP address of primary DNS server for eth1.domainname" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Domain name for eth1</ovf:Label> <ovf:Description>Domain name for eth1</ovf:Description> </ovf:Property> <ovf:Property ovf:key="system. if not using DHCP (IP V4 or V6 format)</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.dns1.ip" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>IP Address for eth1</ovf:Label> <ovf:Description>IP Address for eth1.1 131 .27.ip" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>IP address of secondary DNS server for eth1</ovf:Label> <ovf:Description> IP address of secondary DNS server for eth1.usedhcp" ovf:type="boolean" ovf:userConfigurable="true" ovf:value="false"> <ovf:Label>Use DHCP for eth1</ovf:Label> <ovf:Description>Use DHCP for eth1</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.eth1. if not using DHCP (IP V4 or V6 format) </ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.eth1.netmask" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Network mask for eth1</ovf:Label> <ovf:Description>Network mask for eth1.eth1.dns2.eth1.hostname" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Short hostname for the system</ovf:Label> <ovf:Description>Short hostname for the system</ovf:Description> </ovf:Property> <ovf:Property ovf:key="system.eth1. if not using DHCP (IP V4 or V6 format) </ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.hostname" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Hostname for eth1</ovf:Label> <ovf:Description>Hostname for eth1</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.19-5-default"> Chapter 2. </ovf:Property> <ovf:Property ovf:key="networkport.gateway" ovf:type="string" ovf:userConfigurable="true"> <ovf:Label>Default gateway for eth1</ovf:Label> <ovf:Description>Default gateway for eth1.eth1. if not using DHCP (IP V4 or V6 format)</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.eth1.eth1. IBM Systems Director VMControl V2. if not using DHCP (IP V4 or V6 format)</ovf:Description> </ovf:Property> <ovf:Property ovf:key="networkport.6.eth1.

This swap space will occupy the whole of the z/VM guest's 0300 disk. so this section is empty except for a description of what it would contain if it was relevant. --> <vimzvm:LinuxPartition vimzvm:partNum="1" vimzvm:partSize="50055" vimzvm:partSizeUnits="TRK" vimzvm:partBytesPerUnit="49152"/> <vimzvm:LogicalDiskRef vimzvm:itemRef="disk-0100"/> </vimzvm:ConfigProposal> </vimzvm:FileSystem> <vimzvm:FileSystem vimzvm:diskRef="EXAMPLE1:swap1" vimzvm:mountPoint="swap"> <vimzvm:ConfigProposal> <vimzvm:LinuxMount vimzvm:devSpec="/dev/disk/by-path/ccw-0.0. The physical volumes defined here reference logical disks. <ovf:Info>Information about the operating system in the virtual system. and that partition will have a capacity of 50055 49152-byte tracks. i.0301-part1" vimzvm:mountOptions="defaults" vimzvm:dump="0" vimzvm:fsckPassNo="0"/> <vimzvm:LinuxFileSystem vimzvm:type="swap" vimzvm:label=""/> <vimzvm:LogicalDiskRef vimzvm:itemRef="disk-0301"/> </vimzvm:ConfigProposal> </vimzvm:FileSystem> </vimzvm:LinuxFileSystemSection> <vimzvm:LinuxLVMSection ovf:required="false"> <!-.0100-part1" vimzvm:mountOptions="acl..user_xattr" vimzvm:dump="1" vimzvm:fsckPassNo="1"/> <vimzvm:LinuxFileSystem vimzvm:type="ext3" vimzvm:label=""/> <!-. </ovf:Info> </ovf:InstallSection> <vimzvm:LinuxFileSystemSection ovf:required="true"> <!-. </ovf:Info> <vimzvm:FileSystem vimzvm:diskRef="EXAMPLE1:/" vimzvm:mountPoint="/"> <vimzvm:ConfigProposal> <!-. formatting.</ovf:Info> <ovf:Description>SUSE Linux Enterprise Server 11</ovf:Description> </ovf:OperatingSystemSection> <ovf:InstallSection> <ovf:Info> Indicates that the system needs to be booted after deployment to run first-boot customization. 132 IBM Systems Director VMControl: Installation and User’s Guide .This system has no LVM volume groups. and mounting scheme which is to be used to re-create the virtual server's Linux file systems.0.e.The LinuxFileSystemSection defines a partition.The information in these "ConfigProposal" elements essentially lines up with what is specified in /etc/fstab. Item elements of ResourceType=31 (LogicalDisk). --> <ovf:Info> Defines how the image files (containing Linux file system content) are deployed to Linux mount points. The volume groups defined here are referenced by the Linux file system configuration proposals in the LinuxFileSystemSection. --> <ovf:Info> Defines a configuration proposal for the Linux LVM2.This file system goes on the first partition of the z/VM guest's 0100 disk. with some additional information as required to recreate the original partitioning scheme and LVM configuration.0. --> <vimzvm:LinuxMount vimzvm:devSpec="/dev/disk/by-path/ccw-0.0300-part1" vimzvm:mountOptions="defaults" vimzvm:dump="0" vimzvm:fsckPassNo="0"/> <vimzvm:LinuxFileSystem vimzvm:type="swap" vimzvm:label=""/> <!-. --> <vimzvm:LogicalDiskRef vimzvm:itemRef="disk-0300"/> </vimzvm:ConfigProposal> </vimzvm:FileSystem> <vimzvm:FileSystem vimzvm:diskRef="EXAMPLE1:swap2" vimzvm:mountPoint="swap"> <vimzvm:ConfigProposal> <vimzvm:LinuxMount vimzvm:devSpec="/dev/disk/by-path/ccw-0.

If CPU affinity is on. Each such share value consists of a minimum share and a maximum share. this condition is called ″CPU affinity suppressed. The primary processor type of a z/VM system is IFL if all of its real processors are of type IFL.1 133 . access to real memory and access to paging service are indirectly influenced by the minimum share of the virtual server if these system resources are constrained. IBM Systems Director VMControl V2. z/VM will simulate these processors. v Minimum share The minimum share determines the amount of processor capacity the z/VM system will offer to the virtual server as a minimum. the primary processor type is CP. they indirectly also influence access to other types of system resources when they are constrained.″ With CPU affinity off. the CPUAFFINITY setting of the z/VM guest) is used to determine whether simulation or virtualization is desired for the virtual processors of a virtual server. Note that while share values control the processor capacity directly. Share values You can specify share values for a virtual server to control the amount of processor cycles (i. Share values are specified for all processor types together. If no matching real processors exist.e. the minimum and maximum share of processor capacity is determined separately for each real processor type that is dispatched to the virtual server. these shares are determined at the level of the virtual server and are then used for all processor types. Specifically. With CPU affinity on. but dispatch them on real processors of type CP. z/VM will dispatch virtual processors of types other than the primary processor type on real processors. </ovf:Info> </vimzvm:LinuxLVMSection> </ovf:VirtualSystem> </ovf:Envelope> Processor settings This topic provides information about using IBM Systems Director VMControl to specify processor settings for z/VM virtual servers. If CPU affinity is off. z/VM will dispatch a virtual server’s virtual processors on real processors that match their types. CPU affinity also affects the way in which the share of processor capacity is determined. regardless of the existence of matching real processors. When the total processor Chapter 2. Otherwise. Processor type You can specify one of the following processor types for each virtual processor in your virtual server: v IFL (Integrated Facility for Linux processor) v CP (general-purpose Central Processor) v ICF (Internal Coupling Facility) v zAAP (IBM System z Application Assist Processor) v zIIP (IBM System z9 Integrated Information Processor and IBM System z10™ Integrated Information Processor) CPU affinity CPU affinity (that is. processor capacity) the virtual server receives.

Any processor capacity that is offered to but not consumed by a virtual server is available for other virtual servers. For example. – Hard limit . A privilege class consists of one or more characters each of which can occur 134 IBM Systems Director VMControl: Installation and User’s Guide . if defined. and a second virtual server (VM2) has a minimum relative share of 200. that represents the portion of the processor capacity available for absolute sharing. VM2 is being offered twice as much processor capacity as VM1 (when both are being offered their minimum).A maximum share is defined and acts as an upper limit regardless of free processor capacity. This is the default. one of which is dedicated. As a result. – Relative An integer value between 1 and 10000 that represents a weight for the virtual server relative to all virtual servers in the z/VM system that have a relative share defined. Otherwise.1% and 100%. minus the processor capacity of virtual servers that have an absolute share defined. The processor capacity available for absolute sharing is the total processor capacity of the z/VM system. minus those processors that are dedicated. a virtual server may consume less than its minimum share in such cases. if a virtual server has a minimum absolute share of 50% and the z/VM system has five real processors active. minus those processors that are dedicated. The equivalent absolute processor capacity (in real CPUs) of a virtual server is its relative share divided by the sum of the relative shares of all virtual servers in the z/VM system that have a relative share defined. – Soft limit . times the processor capacity (in real CPUs) available for relative sharing. v Relative and absolute share You can set relative or absolute values for minimum and maximum share. Note that the equivalent absolute processor capacity of a virtual server defined with relative shares depends on relative shares of the other virtual servers.A maximum share is defined and acts as an upper limit if there is contention for processor capacity. v Maximum share The maximum share. Privilege class and options The privilege class defines the privileges (functions and commands) for the virtual server. the virtual server may be offered more than the minimum share. The processor capacity available for relative sharing is the total processor capacity of the z/VM system. Server settings This topic provides information about using IBM Systems Director VMControl to specify server settings for z/VM virtual servers. For example. may act as an upper limit for the amount of processing capacity the z/VM system will allow the virtual server to consume. specified in whole percentages or tenths of percents. capacity of the z/VM system is not fully utilized. the virtual server is being offered an equivalent of two real processors as a minimum. the virtual server can consume more than its maximum share. if a virtual server (VM1) has a minimum relative share of 100. – Absolute A percentage value between 0. The following limit types can be specified for the maximum share: – No limit .A maximum share is not defined.

For more information.1 135 . which are first initialized to binary zeros. If LOADPARM is not specified. Load parameters Specifies a 1– to 8-character load parameter. the parameter string is inserted into the virtual server registers m through n. a load parameter of eight EBCDIC blanks is formed. four bytes per register. You can also specify parameters (parms) and load parameters (loadparms). The privilege classes chosen for the virtual server should be a subset of the classes defined for the z/VM system. the load parameter is left-justified and padded with blanks. For more information. the virtual server registers are unchanged. IBM Systems Director VMControl V2. If you are IPLing a named saved system that was defined without the PARMREGS=m-n option on the DEFSYS command. refer to Redefining Command Privilege Classes in z/VM: CP Planning and Administration (SC24-6083). a single byte of binary zeros is inserted following the string. refer to the IPL command in z/VM: CP Commands and Utilities Reference (SC24-6081-07). The server password is restricted to a maximum of 8 characters and may contain no blank spaces.only once. You can designate the virtual device number or the named saved system as the IPL source. IPL settings When creating a new virtual server. starting with register 0. Chapter 2. If you omit the Parameters operand. Parameters Specifies a parameter string up to 64 bytes long to pass to your virtual server in general purpose registers at completion of IPL. The parameter string begins with the first nonblank character and consists of all remaining characters that follow. If you omit the Parameters operand. If you are IPLing a named saved system that was defined with the PARMREGS=m-n option on the DEFSYS command. The characters must be letters or numbers in the range 1 . Options are added to the OPTION control statement in the directory entry for the virtual server. Read the following information for details about parameters and load parameters.6. the parameter string is inserted into the virtual server registers 0 through 15. the parameter string is inserted into the virtual server registers. specifying the PARM option results in an error message being issued and in the command not being processed. The registers are not first initialized to binary zeros. you can specify IPL setting for starting the virtual server. If the string is less than 64 bytes. the virtual server registers are unchanged. including trailing blanks. If you are IPLing a named saved system that was defined with the PARMREGS=NONE option on the DEFSYS command. If fewer than eight characters are specified. You can also specify options to define special characteristics for the virtual server. If you are IPLing a device.

digits 0-9. The load parameter may be retrieved by the guest operating system during its IPL sequence. and the blank. The load parameter is converted to upper case and may include only the upper case alphabetic characters (A-Z). Its use is determined by the guest operating system. the period. such as indicating the nucleus to be loaded during the IPL sequence. 136 IBM Systems Director VMControl: Installation and User’s Guide .

Minato-ku Tokyo 106-0032. IBM® may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. © Copyright IBM Corp. program. in writing. You can send license inquiries. Any functionally equivalent product. Changes are periodically made to the information herein. program. The materials at those Web sites are not part of the materials for this IBM® product and use of those Web sites is at your own risk. these changes will be incorporated in new editions of the publication. in writing.A. services. or service may be used. NY 10504-1785 U.Chapter 3. Some states do not allow disclaimer of express or implied warranties in certain transactions. The furnishing of this document does not grant you any license to these patents. THE IMPLIED WARRANTIES OF NON-INFRINGEMENT. Consult your local IBM® representative for information on the products and services currently available in your area. IBM® may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. this statement may not apply to you. IBM® may not offer the products. program. or service that does not infringe any IBM® intellectual property right may be used instead. BUT NOT LIMITED TO. or service is not intended to state or imply that only that IBM® product. therefore. to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk. IBM® may have patents or pending patent applications covering subject matter described in this document. contact the IBM® Intellectual Property Department in your country or send inquiries. This information could include technical inaccuracies or typographical errors. or service. INCLUDING. it is the user’s responsibility to evaluate and verify the operation of any non-IBM product.A. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. 2009. to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome. For license inquiries regarding double-byte (DBCS) information. Any reference to an IBM® product.S. EITHER EXPRESS OR IMPLIED.S. program. 2009 137 . or features discussed in this document in other countries. Notices This information was developed for products and services offered in the U. However.

brands. This information contains examples of data and reports used in daily business operations. other countries. Any performance data contained herein was determined in a controlled environment. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol (® or ™). Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged. or both. Therefore.S. subject to appropriate terms and conditions. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. compatibility or any other claims related to non-IBM products. payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM® under terms of the IBM® Customer Agreement. indicating US registered or common law trademarks owned by IBM at the time this information was published. IBM® has not tested those products and cannot confirm the accuracy of performance. or any equivalent agreement between us. To illustrate them as completely as possible. If you are viewing this information softcopy. some measurements may have been estimated through extrapolation.com® are trademarks or registered trademarks of International Business Machines Corporation in the United States. Furthermore. should contact: IBM Corporation MW9A/050 5600 Cottle Road San Jose. Actual results may vary. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. and represent goals and objectives only. CA 95193 U. and products. IBM® International Program License Agreement. the IBM logo. companies. the photographs and color illustrations may not appear. the results obtained in other operating environments may vary significantly. and ibm.A. All statements regarding IBM’s future direction or intent are subject to change or withdrawal without notice. their published announcements or other publicly available sources. Trademarks IBM. Information concerning non-IBM products was obtained from the suppliers of those products. Such information may be available. including in some cases. Users of this document should verify the applicable data for their specific environment. the examples include the names of individuals. Such trademarks may also be registered or common law 138 IBM Systems Director VMControl: Installation and User’s Guide .

other countries.trademarks in other countries. Microsoft and Windows are trademarks of Microsoft Corporation in the United States. Linux is a registered trademark of Linus Torvalds in the United States. Chapter 3. and/or other countries. and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States. or service names may be trademarks or service marks of others. Other company. other countries. PostScript. Notices 139 . Adobe. product.ibm. the Adobe logo. A complete and current list of IBM trademarks is available on the Web at www. or both. or both.shtml.com/legal/copytrade.

140 IBM Systems Director VMControl: Installation and User’s Guide

Index
C requirements, hardware and software
13
5,

capture requirements, import 6
virtual appliance 90
capture requirements 7
captureva 90
changing S
user properties 108 servers
commands displaying 99
captureva 90 software requirements 5, 13
deployva 93 specified operating environment 5, 13
importva 97 syntax diagram conventions 89
lscapsrv 99
lscustomization 101
lsdeploytargets 105 T
lsrepos 108 trademarks 138
lsva 111
conventions
syntax diagram 89
customize V
virtual appliances 101 virtual appliances
capturing 90, 108
customizing 101
D deploying 93
displaying 111
deploy importing 97
virtual appliance 93
deploy requirements 9
deployva 93
display
hosts 105
servers 99
target servers 105
virtual appliances 111

H
hardware requirements 5, 13

I
import
virtual appliance 97
import requirements 6
importva 97

L
legal notices 137
lscapsrv 99
lscustomization 101
lsdeploytargets 105
lsrepos 108
lsva 111

R
requirements, capture 7
requirements, deploy 9

© Copyright IBM Corp. 2009, 2009 141

142 IBM Systems Director VMControl: Installation and User’s Guide

.

 Printed in USA .