IBM Systems Director VMControl

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

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

Chapter 1. About this publication
This publication provides instructions for installing and using IBM® Systems
Director VMControl and IBM Systems Director VMControl Image Manager. With
IBM Systems Director VMControl Image Manager you can capture, import, and
deploy virtual appliances in your environment. This documentation describes how
to use the Web interface as well as the command-line interface (smcli) to complete
tasks. You can also find troubleshooting information, and a reference section that
contains IBM Systems Director VMControl-specific requirements for Open
Virtualization Format (OVF) virtual appliance packages.
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, import, and
deploy virtual appliances in the data center.
Conventions and terminology

These notices are designed to highlight key information:
Note: These notices provide important tips, guidance, or advice.
Important: These notices provide information or advice that might help you avoid
inconvenient or difficult situations.
Attention: These notices indicate possible damage to programs, devices, or data.

An attention notice appears before the instruction or situation in which damage
can occur.
Publications and related information

You can view the same IBM Systems Director VMControl content that resides in
the Information Center in a PDF document. In addition to this documentation,
there is additional information related to IBM Systems Director VMControl.
To view a PDF file, you need Adobe Acrobat Reader, which can be downloaded for
free from the Adobe Web site at www.adobe.com/products/acrobat/readstep.html.
IBM Systems Director VMControl resources on the World Wide

Web
v IBM Systems Director VMControl information center
http://publib.boulder.ibm.com/infocenter/director/v6r1x/topic/vim_210/
fsd0_vim_main.html
Find information for installing and using IBM Systems Director VMControl.
v IBM Systems Director VMControl Web site
www.ibm.com/systems/management/director/plugins/imagemg/
See an overview of IBM Systems Director VMControl and links to download the
product.
v Windows® Systems Director Web site
© Copyright IBM Corp. 2009, 2009 1

www.ibm.com/systems/management/director/
Get overview information, demos, and downloads for the IBM Systems Director
product, as well as its plug-ins.
v IBM Systems and servers: Technical support page
www.ibm.com/systems/support/
Locate support for IBM hardware and systems-management software.
How to send your comments

Your feedback is important in helping to provide the most accurate and highest
quality information.
If you have any comments about this book or any other IBM Systems Director
publication, go to the IBM Systems Director information center Web site at
http://publib.boulder.ibm.com/infocenter/director/v6r1x/index.jsp. There you
will find the feedback page where you can enter and submit comments.
2 IBM Systems Director VMControl: Installation and User’s Guide

Chapter 2. IBM Systems Director VMControl V2.1
IBM Systems Director VMControl is designed to simplify the management of
workloads in your IT environment. 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.
Overview of IBM Systems Director VMControl

This section provides an overview of IBM Systems Director VMControl and IBM
Systems Director VMControl Image Manager, including accessibility and license
information.
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. 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.
v Edit z/VM virtual servers.
v Manage z/VM virtual servers.
The licensed portion of IBM Systems Director VMControl, IBM Systems Director
VMControl Image Manager, allows you to complete the following tasks.
v Discover existing image repositories in your environment and import external,
standards-based images into your repositories as virtual appliances.
v Capture a running virtual server that is configured just the way you want,
complete with guest operating system, running applications, and virtual server
definition. When you capture the virtual server, a virtual appliance is created in
one of your image repositories with the same definitions and can be deployed
multiple times in your environment.
v Import virtual appliance packages that exist in the Open Virtualization Format
(OVF) from the Internet or other external sources. After the virtual appliance
packages are imported, you can deploy them within your data center.
v Deploy virtual appliances quickly to create new virtual servers that meet the
demands of your ever-changing business needs.
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.
The IBM Systems Director VMControl Summary page guides you through the
tasks you need to complete to get started using the product: installing agents,
discovering or creating image repositories, and capturing or importing virtual
appliances. Once you are up and running, the Summary page gives you quick

access to the main tasks and views that you can utilize in IBM Systems Director
VMControl. The Summary page also helps you manage your license for IBM
Systems Director VMControl Image Manager.
When you have started using the tasks available in IBM Systems Director
VMControl, 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.
v Image Repositories – view all of the discovered image repositories in your
environment.
v Deployment History – view all of the virtual servers that have been created from
a specific virtual appliance. You can also perform management tasks on the
virtual servers from within this view.
Related reference
IBM Systems Director Downloads
Accessibility features
This topic provides information about the accessibility features of IBM Systems
Director VMControl.
Accessibility features help users who have a disability, such as restricted mobility
or limited vision, to use information technology products successfully. The IBM
Systems Director VMControl plug-in for IBM Systems Director supports the
accessibility features that are supported in IBM Systems Director. For more
information, see the Accessibility features for IBM Systems Director topic.
License information
This topic describes the licensing for IBM Systems Director VMControl, including
the details of which components are no-charge (free) and which components are
chargeable (for-fee).
IBM Systems Director VMControl includes a no-charge (free) function and an

optional chargeable (fee-based) function. The no-charge portion of the product
enables you to create and manage virtual servers for z/VM.
When you download, install, and begin using IBM Systems Director VMControl,
you are granted a 60-day evaluation license for IBM Systems Director VMControl
Image Manager. The evaluation license enables you to create, import, and deploy
virtual appliances in your environment. Once the evaluation license expires, you
must purchase a license in order to continue using IBM Systems Director
VMControl Image Manager. The 60-day evaluation period begins the first time you
begin using IBM Systems Director VMControl Image Manager. The number of days
left on the evaluation license appears on the bottom of the IBM Systems Director
VMControl summary page. The day the evaluation license expires is also
displayed, as well as information about obtaining a license.
If you allow the evaluation license to expire before purchasing a license for IBM
Systems Director VMControl Image Manager, you will no longer be able to create,
import, and deploy virtual appliances in your environment. However, when you
do purchase and install the license for IBM Systems Director VMControl Image
Manager, any image repositories and virtual appliances that you created during the
evaluation period will still be usable.

The IBM Systems Director VMControl Image Manager license is packaged on a
CD-ROM with authorization key and install program. Once you install the license,
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, review the
hardware and software requirements. Before using IBM Systems Director
VMControl Image Manager to import virtual appliance packages, capture virtual
servers, or deploy virtual appliances, review the requirements for each of those
tasks.
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.1.1.2 software. This topic describes hardware and software
requirements that are unique to IBM Systems Director VMControl.
For detailed information about the hardware and software requirements for IBM
Systems Director, see Hardware and software requirements for IBM Systems
Director.
Supported IBM® systems
IBM Systems Director VMControl is supported on all IBM® systems that are
supported by IBM Systems Director Server 6.1.1.2.
For detailed information on the systems supported by IBM Systems Director

Server, see Supported IBM systems and products.
Supported operating systems
IBM Systems Director VMControl is supported on all operating systems that are
For specific versions of these operating systems supported by IBM Systems

Director Server, see Operating systems supported by IBM Systems Director 6.1.1..
Supported virtualization software
The following virtualization software is supported for IBM Systems Director

VMControl:
v Hardware Management Console Version 7.3.4.2, PTF MH01181
Chapter 2. IBM Systems Director VMControl V2.1 5

Note: It is recommended that you always apply the latest available service pack.
The minimum service pack prerequisite is listed here.
v Integrated Virtualization Manager Version 2.1.0.10
v z/VM 5.4
Note: Ensure that the following PTFs for z/VM 5.4 are installed:
– UM32505
– UM32503
– UM32521
– UM32522
– UM32693
– UM32765
Additional prerequisites
v Ensure that you have the appropriate x11 libraries installed on your system.
These libraries are needed for IBM Systems Director VMControl installation. For
example, if you are running Red Hat Enterprise Linux 5.3, use the Red Hat
installation disks to install the shared library.
Note: For System z systems, xlibs must be installed in 64-bit mode. You can
obtain the libstdc++.so.5 file from the compat-libstdc++-33-3.2.3-61.s390x.rpm
packet.
v If you are running the IBM z/VM Manageability Access Point Agent that is
supported by IBM Systems Director 6.1.1.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.1.1.2.
In addition, 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. For more information, see Operating systems supported by IBM
Systems Director 6.1.1.
Related tasks
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.
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. 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 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 AIX mksysb image file associated with the virtual appliance package
that you want to import.
z/VM requirements for import
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.
v The image repository is discovered in IBM Systems Director.
v There is sufficient space in the image repository to store the image associated
with the virtual appliance package that you want to import.
v The virtual appliance package that you want to import was created for z/VM by
IBM Systems Director VMControl Capture or Import tasks.
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.
You can capture these types of virtual servers:

v IBM Power Systems (POWER5 and POWER 6) virtual servers (logical partitions)
running AIX 5.3 or AIX 6.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:

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.
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.
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.
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.
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.
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
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
v A virtual server on a Power Architecture BladeCenter server that is managed by
IVM

Note: You cannot perform the deploy, capture, or relocate tasks concurrently for
the same AIX virtual server. Wait until one of these tasks is complete before
beginning another.
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. Access status is listed as OK, and inventory is collected for the
HMC or IVM. If the virtual server has an operating system installed, it will be
overwritten when the virtual appliance is deployed.
v A NIM Master is running and is accessible by your IBM Systems Director Server.
v The NIM Master is able to access the target virtual server and the HMC or IVM
that manages it over the network.
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 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. See the Supported storage devices topic for a list of supported
storage devices.
– Local storage that is allocated from a storage pool hosted by the Virtual I/O
Server.
You can deploy a virtual appliance to a new virtual server when the following
Manager (IVM) that will manage the new virtual server is discovered in IBM
HMC or IVM.
v The NIM Master is running and is accessible by your IBM Systems Director
Server.
v A NIM Master has network access to the HMC or IVM that will manage the
new virtual server.
v The virtual server that you plan to create must have network access to the NIM
Master, and any firewalls must be preconfigured to allow the virtual server to
connect to the NIM Master.

Director:
storage devices.
Server.
System z and z/VM requirements for deploy
On a System z host system that is running the z/VM hypervisor, you can deploy
an empty virtual server to create a virtual server that does not include a virtual
appliance. 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. Subsequent requests for deployment are queued for
processing.
For any z/VM deployment, 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.
v The IBM z/VM Manageability Access Point Agent on the System z host system
is discovered in IBM Systems Director. Access status is listed as OK, and
inventory is collected.
v The virtual server that is the target of the deployment is powered off.
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, 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
v The IBM z/VM Manageability Access Point Agent contains a repository with
images.
v Inventory of the images in the repository has completed.
v Resources required for the image exist on the z/VM system, for example:
– Available network interfaces exist for use by the virtual server.
– Available volumes exist for use by the virtual server.
– If minidisks are required for virtual server storage, the directory manager
supporting the z/VM system must be configured to allocate minidisk
volumes with the Auto-Group option.
additional prerequisites are met:

images.
v Inventory is collected for the images in the repository.
v A virtual server that meets the criteria specified in the image exists and has been
discovered.
Note: If you are deploying to an existing virtual server, the operating system will
be overwritten. You cannot deploy a virtual appliance to z/VM service machines
with the following user IDs, as described in the table:
Table 1. 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. You can also uninstall IBM
Systems Director VMControl.

Hardware and software requirements
IBM Systems Director VMControl is installed on systems running IBM Systems
Director Server 6.1.1.2 software. This topic describes hardware and software
requirements that are unique to IBM Systems Director VMControl.
For detailed information about the hardware and software requirements for IBM
Systems Director, see Hardware and software requirements for IBM Systems
Director.
Supported IBM® systems
IBM Systems Director VMControl is supported on all IBM® systems that are
For detailed information on the systems supported by IBM Systems Director

Server, see Supported IBM systems and products.
Supported operating systems
IBM Systems Director VMControl is supported on all operating systems that are
For specific versions of these operating systems supported by IBM Systems

Director Server, see Operating systems supported by IBM Systems Director 6.1.1..
Supported virtualization software
The following virtualization software is supported for IBM Systems Director

VMControl:
v Hardware Management Console Version 7.3.4.2, PTF MH01181
The minimum service pack prerequisite is listed here.
v Integrated Virtualization Manager Version 2.1.0.10
v z/VM 5.4
Note: Ensure that the following PTFs for z/VM 5.4 are installed:
– UM32505
– UM32503
– UM32521
– UM32522
– UM32693
– UM32765
Additional prerequisites
v Ensure that you have the appropriate x11 libraries installed on your system.
These libraries are needed for IBM Systems Director VMControl installation. For
example, if you are running Red Hat Enterprise Linux 5.3, use the Red Hat
installation disks to install the shared library.

Note: For System z systems, xlibs must be installed in 64-bit mode. You can
obtain the libstdc++.so.5 file from the compat-libstdc++-33-3.2.3-61.s390x.rpm
packet.
v If you are running the IBM z/VM Manageability Access Point Agent that is
supported by IBM Systems Director 6.1.1.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.1.1.2.
In addition, 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. For more information, see Operating systems supported by IBM
Systems Director 6.1.1.
Related tasks
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. 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. When the evaluation license expires, 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.
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. 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.
Before installing IBM Systems Director VMControl, perform the following tasks:
v Make sure that you have installed IBM Systems Director version 6.1.1.1.
v Make sure that the target system satisfies all IBM Systems Director
VMControl-specific prerequisites. For information, see Hardware and software
requirements for IBM Systems Director.
v On Red Hat Enterprise Linux, SELinux must be disabled before installing IBM
Systems Director VMControl. To check SELinux status, enter the following
command: sestatus. If SELinux is not disabled, follow these steps:
1. Enter this command: #vi /etc/selinux/config
2. Disable SELinux by specifying SELINUX=disabled.
3. Enter this command to reboot the system: #reboot
4. Log on the system and enter this command to check SELinux status:
sestatus.
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:

1. Go to the IBM Systems Director Downloads Web Site at the following
address:
http://www.ibm.com/systems/management/director/plugins/actengmgr/
2. Click Download for the IBM Systems Director VMControl plug-in.
3. Select the package to download:
Operating system Download package

AIX SysDir_VMControl_2_1_AIX.tar.gz
®
Linux for pSeries SysDir_VMControl_2_1_Linux_Power.tar.gz
®
Linux for xSeries SysDir_VMControl_2_1_Linux_x86.tar.gz
®
Linux for zSeries SysDir_VMControl_2_1_Linux_System_z.tar.gz
Windows SysDir_VMControl_2_1_Windows.zip
4. 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.
5. To unzip and extract the contents of the installation package, 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.

For Windows:
unzip <package_name>
To install IBM Systems Director VMControl evaluation license, follow these steps:
1. Change to the directory in which the installation file is located.
2. Launch the IBM Systems Director VMControl program installation file.
Note: If you want to use the installation wizard to install on AIX and Linux,
you must launch the installation program in a graphics-enabled session. As an
alternative, 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.sh
Linux for pSeries Systems_Director_VMControl_2_1_Linux_Power.sh
Linux for xSeries Systems_Director_VMControl_2_1_Linux_x86.sh
Linux for zSeries Systems_Director_VMControl_2_1_Linux_System_z.sh
Windows Systems_Director_VMControl_2_1_Windows.exe
This launches the installation wizard and displays the Welcome page.
3. Follow the instructions in the installation wizard to install IBM Systems
Director VMControl. When the installation is complete, IBM Systems Director
VMControl is displayed in the IBM Systems Director Welcome page.

Installing IBM Systems Director VMControl permanent license
key
When the 60-day evaluation license for IBM Systems Director VMControl expires,
you can purchase a license to continue using IBM Systems Director VMControl
Image Manager. You can continue to use the no-charge function of IBM Systems
Director VMControl. If you purchase the license for IBM Systems Director
VMControl Image Manager, you must install the permanent license key to continue
using IBM Systems Director VMControl Image Manager.
The IBM Systems Director VMControl evaluation license must be installed before
you can install the permanent license key for IBM Systems Director VMControl.
On Red Hat Enterprise Linux, SELinux must be disabled before installing IBM
4. Log on the system and enter this command to check SELinux status: sestatus.
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. Go to the IBM Systems Director Downloads Web Site at the following address:
Operating system Download package

AIX SysDir_VMControl_2_1_AIX-full.tar.gz
Linux for pSeries SysDir_VMControl_2_1_Linux_Power-full.tar.gz
Linux for xSeries SysDir_VMControl_2_1_Linux_x86-full.tar.gz
Linux for zSeries SysDir_VMControl_2_1_Linux_System_z-full.tar.gz
Windows SysDir_VMControl_2_1_Windows-full.zip

VMControl. Be sure that you copy the correct package based on the operating
system that is running on the IBM Systems Director Server.
following command:
For AIX or Linux:

For Windows:

To install IBM Systems Director VMControl, follow these steps:
1. To start the installation, launch the IBM Systems Director VMControl program
executable file:
Note: If you want to use the installation wizard to install on AIX and Linux,
you must launch the installation program in a graphics-enabled session. As an
installation of IBM Systems Director VMControl.
Operating system Installation file name

AIX Systems_Director_VMControl_2_1_AIX-full.sh
Linux for pSeries Systems_Director_VMControl_2_1_Linux_Power-full.sh
Linux for xSeries Systems_Director_VMControl_2_1_Linux_x86-full.sh
Linux for zSeries Systems_Director_VMControl_2_1_Linux_System_z-full.sh
Windows Systems_Director_VMControl_2_1_Windows-full.exe
This launches the installation wizard and displays the Welcome page.
2. Follow the instructions in the installation wizard to install IBM Systems
Director VMControl. When the installation is complete, IBM Systems Director
VMControl is displayed in the IBM Systems Director Welcome page.
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. 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.
Before installing IBM Systems Director VMControl, perform the following tasks:
v Make sure that you have installed IBM Systems Director version 6.1.1.1.
v Make sure that the target system satisfies all IBM Systems Director
VMControl-specific prerequisites. For information, see Hardware and software
requirements for IBM Systems Director.
v On Red Hat Enterprise Linux, SELinux must be disabled before installing IBM
4. Log on the system and enter this command to check SELinux status:
sestatus.
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. Go to the IBM Systems Director Downloads Web Site at:

Operating system License Download package

AIX Evaluation SysDir_VMControl_2_1_AIX.tar.gz
Permanent SysDir_VMControl_2_1_AIX-full.tar.gz
Linux for pSeries Evaluation SysDir_VMControl_2_1_Linux_Power.tar.gz
Permanent SysDir_VMControl_2_1_Linux_Power-full.tar.gz
Linux for xSeries Evaluation SysDir_VMControl_2_1_Linux_x86.tar.gz
Permanent SysDir_VMControl_2_1_Linux_x86-full.tar.gz
Linux for zSeries Evaluation SysDir_VMControl_2_1_Linux_System_z.tar.gz
Permanent SysDir_VMControl_2_1_Linux_System_z-full.tar.gz
Windows Evaluation SysDir_VMControl_2_1_Windows.zip
Permanent SysDir_VMControl_2_1_Windows-full.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.
VMControl. Be sure that you copy the correct package based on the
operating system that is running on the IBM Systems Director Server.
following command:
For AIX or Linux:

For Windows:
When you perform an unattended installation of IBM Systems Director VMControl,

a response file provides answers to the questions that are posed by the installation
wizard.
To set up and run an unattended installation of IBM Systems Director VMControl,

follow these steps:
1. Open the installer.properties file in an ASCII text editor.
2. Use the comments in the installer.properties response file to modify the
response file.
3. Save the modified installer.properties response file.
4. Open a command prompt and change to the directory that contains the IBM
Systems Director VMControl installation file.

5. From the command prompt, enter the appropriate installation command:
Operating system License Installation command

AIX Evaluation ./Systems_Director_VMControl_2_1_AIX.sh -i silent
Permanent ./Systems_Director_VMControl_2_1_AIX-full.sh -i
silent
Linux for pSeries Evaluation ./Systems_Director_VMControl_2_1_Linux_Power.sh -i
silent
Permanent ./Systems_Director_VMControl_2_1_Linux_Power-
full.sh -i silent
Linux for xSeries Evaluation ./Systems_Director_VMControl_2_1_Linux_x86.sh -i
silent
Permanent ./Systems_Director_VMControl_2_1_Linux_x86-full.sh
-i silent
Linux for zSeries Evaluation ./Systems_Director_VMControl_2_1_Linux_System_z.sh
Permanent ./Systems_Director_VMControl_2_1_Linux_System_z-
full.sh -i silent
Windows Evaluation Systems_Director_VMControl_2_1_Windows.exe -i
silent
Permanent Systems_Director_VMControl_2_1_Windows-full.exe -i
silent
6. Check the appropriate log file to see if the installation completed successfully:
v For AIX and Linux:
/opt/ibm/director/VMControlManager/installLog.txt
v For Windows:
.../Director/VMControlManager/installLog.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, you must have a properly installed and configured
NIM master in your environment. This NIM master must be discovered, accessed,
and inventoried by your IBM Systems Director Server. Use these instructions to
properly prepare your NIM master.
Ensure that your system meets the following requirements:

v The system is running AIX version 6.1.3 or later
v The following filesets are installed:
– dsm.core
– openssh.base.client
– openssh.base.server
– openssh.license
– openssl.base
– openssl.license
v Common Agent version 6.1.1.1 or later is installed on the system
v The system has been discovered, accessed, and inventoried by your IBM Systems
Director Server
v The system must also be configured as a NIM master system. To configure your
system to be a NIM master, run the following command:

nim_master_setup -a device=path [-a disk=disk_name] -B
where path is the absolute path of the directory where the AIX bos.sysmgt
package can be found. Optionally, you can use the disk=disk_name attribute to
control which physical volume will hold the required /export/nim file system.
For example, if you are using a SAN for your /export/nim file system, you need
to use the disk=disk_name attribute.
Note: The nim_master_setup command can take 20 minutes or longer to run.

v If the NIM image repository (NIM Master) connects to IBM Systems Director
Server through one network adapter, and connects to the virtual server where
you plan to deploy a virtual appliance through a different network adapter,
complete the following steps to configure your networks for the deploy task.
1. Log on to the NIM Master.
2. When you ran nim_master_setup to configure your NIM Master, the
master_net network object was created for you to represent the network
associated with the NIM Master’s primary network interface. If the NIM
Master has a secondary interface that you will be using to deploy virtual
servers, then you will need to create one or more additional NIM network
definitions.
Note: Do not define a NIM network object name that begins with the name
of another NIM network object.
a. Define a NIM network object for the NIM Master’s secondary network
interface. For example:
nim -o define -t ent -a net_addr=1.2.3.4 -a snm=255.255.255.0 secondary_net
where 1.2.3.4 is the IP address of the network being defined, 255.255.255.0

is the subnet mask for the network, and secondary_net is the NIM network
object name that you are creating.For more information, see the Defining
NIM networks topic in the IBM Systems Information Center.
b. If the virtual server that you will be deploying is on the same network
as the NIM Master’s secondary interface, then skip this step. If it is on a
different network, then you must define another NIM network object for
the virtual server. For example:
nim -o define -t ent -a net_addr=2.2.3.4 -a snm=255.255.255.0 deploy_net
where 2.2.3.4 is the IP address of the network being defined, 255.255.255.0

is the subnet mask for the network, and deploy_net is the NIM object
name that you are creating.
3. Attach the secondary_net network object you created to the NIM Master
resource, for example:
nim -o change -a if2='secondary_net 1.2.3.4 0' -a cable_type2=N/A master
4. If you created a new deploy_net network, a static route must be established
between it and the secondary_net network object. For more information, see
the Establishing a static NIM route between networks topic in the IBM
Systems Information Center. You should also remove the default route on the
deploy_net network.
You can install the IBM Systems Director VMControl subagent for NIM in one of
two ways.

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

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. You
can start this wizard from the IBM Systems Director VMControl Summary page or
from IBM Systems Director’s Release Management task.
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, click Install Agents on the Summary
page. Then follow the instructions in the installation wizard to install the subagent
for NIM (CommonAgentSubagent_VMControl_NIM) on your NIM master system.
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, follow these steps:
1. In the IBM Systems Director navigation pane, expand Release management.
2. Click Agents.
3. On the Agents page, click Common Agent Subagent Packages.
4. From the Common Agent Subagent Packages view, select the subagent for
NIM.
5. Click Actions on the menu bar, and select Release Management > Install
Agent.
6. Follow the instructions in the installation wizard to install the subagent for
NIM (CommonAgentSubagent_VMControl_NIM) on your NIM master system.
To verify that the IBM Systems Director VMControl subagent for NIM installed
successfully, 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.log
where Director is the path where IBM Systems Director is installed.

manually
You can install the IBM Systems Director VMControl subagent for NIM manually
on the NIM master system in your environment.
To manually install IBM Systems Director VMControl subagent for NIM, follow
these steps:
1. On the IBM Systems Director Server, locate the subagent file,
CommonAgentSubagent_VMControl_NIM_2.1.0\
com.ibm.director.im.rf.nim.subagent.zip.

Note: The subagent file is located in the Director/tpm/repository/directory
where Director is the path where IBM Systems Director is installed. 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. Copy the file to a temporary directory on your NIM master system, such as
/tmp/site.
3. Log in to the NIM master system.
4. Change directory to the NIM master system bin directory: /opt/ibm/director/
agent/bin
5. Run the install tool with the following command:
./lwiupdatemgr.sh -installFeatures -featureId
com.ibm.director.im.rf.nim.subagent
-fromSite jar:file:/tmp/site/com.ibm.director.im.rf.nim.subagent.zip\!/site.xml
-toSite "file:/var/opt/tivoli/ep/runtime/agent/subagents/eclipse/"
6. To verify that the IBM Systems Director VMControl subagent for NIM installed
successfully, check the following error log for messages beginning with DNZIMN:
Director/agent/logs/*.log
7. 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 stop
Director/agent/runtime/agent/bin/endpoint.sh start
Installing the IBM z/VM Manageability Access Point Agent

Use these instructions to perform pre-installation tasks and to install the IBM
z/VM Manageability Access Point Agent on each z/VM system that you want to
manage with IBM Systems Director.
Important: The following instructions provide examples for you to follow to

perform pre-installation tasks and to install the IBM z/VM Manageability Access
Point Agent. It is recommended that you also refer to documentation specific to
your applications and any external security manager that you might be using, as
necessary.
The following prerequisites must be met before you complete the tasks described
in this topic:
v z/VM 5.4 is installed and all service has been applied (including PTFs UM32505,
UM32503, UM32521, UM32522, UM32693 and UM32765) or a higher version that
also supports the IBM z/VM Manageability Access Point Agent.
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.
To prepare your z/VM system for installation and to install the IBM z/VM
Manageability Access Point Agent, you will perform the following tasks:

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.

...
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
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

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
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 *
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

DIR2PROD: Copy of 492 disk to 491 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.
DIR2PROD: Copy of 41F disk to 11F disk has started.
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: Normal Termination.
d. 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.
To update PROFILE EXEC, complete the following steps:

1. Log on to AUTOLOG1 in a non-disruptive manner.
a. Log on to AUTOLOG1.
b. When you see VM READ in the lower left corner of the screen, type
access (noprof
and press Enter. This prevents the existing PROFILE EXEC from running
and ensures that you are not logged off before you can edit the PROFILE
EXEC file.
2. 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.
a. Run the following command to open the PROFILE EXEC file:
xedit profile exec
b. Use the following example as a guide in editing the PROFILE EXEC file.
Add the lines indicated in bold type to your PROFILE EXEC file if they do
not exist already.

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.
To start DirMaint, complete the following steps:

1. Log on to DIRMAINT.
2. 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.
If you do not see the line of text that indicates the process is waiting for work,
refer to any error messages and resolve them.
3. Run the following command to disconnect from DirMaint:
#cp disconnect
Test DirMaint
You must test DirMaint to ensure that it is ready for use.
To test DirMaint, complete the following steps:

1. Log on to MAINT.
2. Run the following command.
This is the universal DirMaint command that requires no authority:
dirm news
DVHXMT1191I Your NEWS request has been sent for processing.
Ready; T=0.03/0.03 22:39:23
DVHREQ2288I Your NEWS request for MAINT at * has been accepted.
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; with RC = 0.
3. Edit the AUTHFOR CONTROL file on the DirMaint 01DF (Filemode=E) disk to
grant MAINT universal authority to issue all DirMaint commands.

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 VSMREQIU * 140A 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. Run the following command so that passwords are no longer required for
every command.
Note: You will be prompted for the MAINT password.

dirm needpass no
Ensure that the output indicates a return code of 0, for example, RC = 0.

5. Perform an additional test to ensure that DirMaint is working.
a. Run the following command to send a file that contains an overview of the
directory entry to the MAINT reader:
dirm rev
DVHXMT1191I Your REVIEW request has been sent for processing.
Ready; T=0.03/0.03 11:45:46
DVHREQ2288I Your REVIEW request for MAINT at * has been accepted.
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; with RC
DVHREQ2289I = 0.
where 0017 is the spool ID number of the file being sent to the MAINT
reader.
b. 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.

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. Quit out of the file by pressing F3.

d. Run the following command to log off of MAINT:
logoff
Successful completion of DIRM REV confirms that DirMaint is running.
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.
To configure the Systems Management Application Programming Interface (API),

complete the following steps:
1. Log on to user ID VSMWORK1.
2. Run the following commands to access the disks:
#CP IPL CMS
access (noprof
set filepool VMSYS
access VMSYS:VSMWORK1. B
3. Create the VSMWORK1 AUTHLIST file to include the ZVMMAPLX user ID.
The ZVMMAPLX user ID is predefined in the user directory and designed to
manage the z/VM manageability access point server.
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.
VSMWORK1 AUTHLIST B1 F 195 Trunc=195 Size=6 Line=1 Col=1 Alt=1
==== * * * Top of File * * *
==== DO.NOT.REMOVE DO.NOT.REMOVE
==== MAINT ALL
==== VSMPROXY ALL
==== VSMWORK1 ALL
==== ZVMMAPLX ALL
==== * * * End of File * * *
4. Save the file with the FILE subcommand.

5. Update the directory entry for VSMREQIU to have 512M of memory.
For example:
USER VSMREQIU XXXXXXXX 512M 512M G

where XXXXXXXX is the password for the VSMREQIU user ID.
6. 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.
IBM Systems Director relies on DirMaint to allocate minidisks out of a preferred

pool of DASD volumes. These DASD volume pools are defined in the EXTENT
CONTROL file. This file provides a template of how the disk spaces should be
allocated. Additionally, system and device default values are defined for use
during disk allocation operations.
To customize the EXTENT CONTROL file, complete the following steps:

1. Log on to MAINT.
2. Update the EXTENT CONTROL file with the new DASD that will be under the
control of your directory manager.
a. If you have an existing copy of the EXTENT CONTROL file on your A disk,
you might want to back it up. Run the following command to create a
backup of the EXTENT CONTROL file:
copy extent control a = contorig =
b. Run the following command to fetch the EXTENT CONTROL file from
DIRMAINT:
dirm send extent control
DVHXMT1191I Your SEND request has been sent for processing.
Ready; T=0.03/0.03 10:50:34
DVHREQ2288I Your SEND request for MAINT at * has been accepted.
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; with RC = 0.
c. 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.
File EXTENT CONTROL A1 replaced by EXTENT CONTROL E1 received from DIRMAINT at
System_A
where System_A is your z/VM system.

d. Run the following command to edit the EXTENT CONTROL file that is on
the MAINT 191 disk:
xedit extent control a

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. 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).
00035 *
00036 * ********************************************************************
00037 :REGIONS.
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.
00061 :GROUPS.
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.
00069 :EXCLUDE.
00070 * UserId Address
00071 MAINT 012*
00072 SYSDUMP1 012*
00073 :END.
e. Run the following command to send the EXTENT CONTROL file back to
DIRMAINT:
dirm file extent control
PUN FILE 0074 SENT TO DIRMAINT RDR AS 0045 RECS 0051 CPY 001 0 NOHOLD
DVHXMT1191I Your FILE request has been sent for processing.
Ready; T=0.03/0.04 15:51:17
DVHREQ2288I Your FILE request for MAINT at * has been accepted.
DVHRCV3821I File EXTENT CONTROL E2 has been received; RC = 0.
DVHREQ2289I Your FILE request for MAINT at * has completed; with RC = 0.
f. Run the following commands to reload the EXTENT CONTROL file. This
process refreshes the DIRMAINT memory and enables the changes to the
EXTENT CONTROL to take effect:
dirm rlde

DVHXMT1191I Your RLDEXTN request has been sent for processing.
Ready; T=0.03/0.03 15:54:47
DVHREQ2288I Your RLDEXTN request for MAINT at * has been accepted.
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; with RC =
DVHREQ2289I 0.
(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.
If you decide to re-IPL the system, 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.
Note: This task assumes that you are using a VSWITCH as your network
connection. However, other comparable types of network connections can be used.
You need one z/VM manageability access point on each z/VM system on which
you want to use IBM Systems Director z/VM management functions. You should
have no more than one z/VM manageability access point per z/VM system.
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. The
ZVMMAPLX default user ID definition contains a default VSWITCH named
VSWID1, and it contains default values for the size and label of a minidisk. The
default VSWITCH name and default values for the minidisk often need to be
modified. You need to ensure that the VSWITCH defined in the ZVMMAPLX user
ID is accessible. Also, you need ensure there is sufficient disk space available for
the ZVMMAPLX virtual server. Use the following example as a guide to changing
the default values.
The example shows a minidisk with 3338 cylinders, which is the size of a 3390
Mod 3 DASD. Formatting a disk of this size for Linux results in about 2.2 GB of
disk space. After Linux is installed, the remaining disk space would be insufficient.
Therefore, the file in the user directory is modified to specify a minidisk that is
backed by a 3390 Mod 9 DASD with 10016 cylinders. This configuration results in
almost 7 GB of disk space. The example also shows that the default VSWITCH
name of VSWID1 is modified to the name of a VSWITCH that has been created
previously, for example, VSW1.
You might need to add a significant amount of disk space if the z/VM
manageability access point will contain an image repository. For example, a large
file system could be mounted over /var/opt/ibm, as the stored images are below
this directory. You can add more disk space now to prepare for an image
repository, or you can add disk space later.
To configure the ZVMMAPLX user ID, complete the following steps:

1. Run the following command to modify the user directory:
dirm for zvmmaplx get

DVHXMT1191I Your GET request has been sent for processing.
Ready; T=0.03/0.03 14:44:53
DVHREQ2288I Your GET request for ZVMMAPLX at * has been accepted.
DVHGET3304I Directory entry ZVMMAPLX is now locked.
RDR FILE reader_file_number SENT FROM DIRMAINT PUN WAS 0931 RECS 0019 CPY 001 A
NOHOLD NOKEEP
DVHREQ2289I Your GET request for ZVMMAPLX at * has completed; with RC
DVHREQ2289I = 0.
2. 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.
File ZVMMAPLX DIRECT A0 replaced by ZVMMAPLX DIRECT A0 received from DIRMAINT at
System_A
where System_A is your z/VM system.

3. 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.
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. Edit the file as follows:

v Specify a VSWITCH that is appropriate for your installation. You can change
the VSWITCH name of VSWID1 to the name of a VSWITCH that has been
created previously, for example, VSW1.
Note: Ensure that you update the VSWITCH to enable the ZVMMAPLX
machine to access the VSWITCH.
v Define a minidisk for the virtual server by changing the size and label for
the minidisk to the values appropriate for your system.
5. Run the following command to update the user directory:
dirm for zvmmaplx replace

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.
Ready; T=0.03/0.03 14:57:47
DVHREQ2288I Your REPLACE request for ZVMMAPLX at * has been accepted.
DVHBIU3450I The source for directory entry ZVMMAPLX has been updated.
DVHBIU3424I The next ONLINE will take place immediately.
DVHDRC3451I The next ONLINE will take place via delta object directory.
DVHBIU3428I Changes made to directory entry ZVMMAPLX have been placed
DVHBIU3428I online.
DVHREP3603I Directory entry ZVMMAPLX is now unlocked.
DVHREQ2289I Your REPLACE request for ZVMMAPLX at * has completed; with
DVHREQ2289I RC = 0.
6. 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. This task installs Linux with
the root file system onto minidisk 150.
To install Linux on the ZVMMAPLX user ID, complete the following steps:
1. To install Linux, refer to the following documentation:
v Installation documentation for your Linux distribution. For information
about the supported Linux distributions, see Supported operating systems.
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)
2. If the Linux system is not already running, log on to the ZVMMAPLX user ID
to start the Linux system.
Ensure that required RPMs are installed

You must verify that all of the required RPMs for your Linux distribution are
installed on the Linux running on the ZVMMAPLX user ID.
The following RPMs are the minimum required levels of RPMs that you need to
install.
Ensure that the required RPMs are installed for the operating system you are
running:

Table 2. RPMs required for various operating system installations
Installation scenario Required RPMs
Red Hat Enterprise Linux version 5.3 for 64-bit v compat-libstdc++-295-2.95.3-
IBM System z 85.s390.rpm
v compat-libstdc++-33-3.2.3-
61.s390.rpm
v expect-5.43.0-5.1.s390.rpm
v libX11-1.0.3-9.el5.s390.rpm
v libXp-1.0.0-8.1.el5.s390.rpm
v libxml2-2.6.26-2.1.2.7.s390.rpm
v libxslt-1.1.17-2.el5_2.2.s390.rpm
v pam-0.99.6.2-4.el5.s390.rpm
v star-1.5a75-2.s390x.rpm
v xorg-x11-xauth-1.0.1-2.1.s390x.rpm
SUSE Linux Enterprise Server 9 SP 4 for 64-bit v compat-2004.7.1-1.2.s390x.rpm
IBM System z
v compat-32bit-9-
200407011411.s390x.rpm
v expect-5.42*.rpm
v libxml2-2.6.7-28.7.s390x.rpm
v libxml2-32bit-9-
200412202205.s390x.rpm
v libxslt-1.1.2.58.7.s390x.rpm
v pam-32bit-0.99.3.0-29.4.s390x.rpm
v pam-modules-32bit-10-
2.2.s390x.rpm
v star-1.5final-28.19.s390x.rpm
v XFree86-libs-32bit-9-
200512021711.s390x.rpm
SUSE Linux Enterprise Server 10 SP 2 for 64-bit v compat-32bit-2006.1.25-
IBM System z 11.2.s390x.rpm
v expect-5.42*.rpm
v libxml2-2.6.23-15.8.s390x.rpm
v libxml2-32bit-2.6.23-15.8.s390x.rpm
v libxslt-1.1.15-15.2.s390x.rpm
v pam-32bit-0.99.3.0-29.4.s390x.rpm
v pam-modules-32bit-10-
2.2.s390x.rpm
v star-1.5final-28.19.s390x.rpm
v xorg-x11-libs-32bit-6.9.0-
50.14.s390x.rpm
v xorg-x11-6.9.0-50.14.s390x.rpm
1. Run the following command to determine whether the RPMs are installed:
rpm -qa
2. If the RPMs are not installed, ensure that you install them.
Ensure that required Linux kernel 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.
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. To
verify whether these patches are on your system, and to obtain these patches,
contact the service provider for your Linux distribution. The next update release of
your Linux distribution after the releases stated in the following table should
contain these patches.
Table 3. Kernel levels and patches required for various operating system installations
Installation scenario Required kernel levels and patches
Red Hat Enterprise Linux version 5.3 for 64-bit v Red Hat Enterprise Linux bug
IBM System z 487697 - af_iucv: consolidated
Bugzilla for miscellaneous af_iucv
fixes.
v Red Hat Enterprise Linux bug
503240 - iucv: provide second
per-cpu IUCV command parameter
block.
SUSE Linux Enterprise Server 9 SP 4 for 64-bit Minimum kernel level 2.6.5-7.317,
IBM System z plus patch 54-01 from Novell bug
516789 - SLES 9 SP4 - IBM LTC
zSeries Maintenance Patches (#54).
SUSE Linux Enterprise Server 10 SP 2 for 64-bit Minimum kernel level 2.6.16.60-0.39.3,
IBM System z plus patches 30-02 and 30-03 from
Novell bug 493578 - SLES 10 SP2 -
IBM LTC zSeries Maintenance patches
(#30).
Ensure that the kernel module af_iucv is properly loaded

You must verify that the kernel module af_iucv is properly loaded.
To ensure that the kernel module af_iucv is properly loaded, complete the
following steps:
1. Run the following command:
lsmod |grep af
If the module was properly loaded, running the command will produce results
similar to the following output:
af_iucv 150624 0
iucv 111192 1 af_iucv
If you do not receive this output, the module was not loaded and you need to
perform the next step.
2. Load the module.
a. Run the following command to load the module:
modprobe af_iucv
b. 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=""

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 (the virtual server on which the IBM z/VM
Manageability Access Point Agent runs) requires the following z/VM privclasses
and commands.
Table 4. 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, the ZVMMAPLX virtual
server must have the ability to link to other virtual servers without specifying a
password. This can be done by specifying the LNKNOPAS option in the directory
entry for the ZVMMAPLX user ID. When LNKNOPAS is specified, password
authorization may still be required when an external security manager (ESM) is
installed.

For more information about external security manager authorizations, refer to the
documentation for your external security manager. For documentation related to
RACF®, refer to Shelf: z/VM V5R4.0.
Install the Platform Agent

You must install the IBM Systems Director Platform Agent on the Linux that runs
on your ZVMMAPLX user ID.
Refer to Installing Platform Agent to install the IBM Systems Director Platform
Agent on your z/VM system.
Install the IBM z/VM Manageability Access Point Agent

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

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

h. If a tar file was created, change to the directory /var/opt/ibm/zvmmap/
repository/images. Run the following command:
i. If a tar file was created, extract the contents of the tar file. Run the following
command:
tar -xf /var/opt/ibm/zvmmap/repository/images.tar
j. If a tar file was created, remove the tar file.
k. Run the following commands to start the Platform Agent services:
/etc/init.d/ibmsa start
/etc/init.d/cimlistenerd start
/etc/init.d/tier1slpinst start
/etc/init.d/cimserverd start
Uninstalling IBM Systems Director VMControl

You can uninstall IBM Systems Director VMControl from your environment.
To uninstall IBM Systems Director VMControl, follow these steps:

1. Launch the IBM Systems Director VMControl program uninstallation file.
Note: If you want to use the wizard to uninstall from AIX and Linux, you
must launch the uninstallation program in a graphics-enabled session. As an
uninstallation of IBM Systems Director VMControl.
Option Description
AIX or Linux /opt/ibm/director/<VMControl_directory>/
uninstall/Uninstall
Tip: To perform an unattended
uninstallation, enter the following command:
./Uninstall -i silent
Windows <VMControl_directory>\uninstall\
Uninstall.exe
Tip: To perform an unattended
uninstallation, enter the following command:
uninstall.exe -i silent
This launches the uninstallation wizard.

2. Follow the steps in the uninstallation wizard to uninstall IBM Systems Director
VMControl.
Uninstalling IBM z/VM Manageability Access Point Agent

You can use the mapuninstall command to uninstall the IBM z/VM Manageability
Access Point Agent.
Complete the following steps to uninstall either just IBM z/VM Manageability
Access Point Agent or both IBM z/VM Manageability Access Point Agent and
Platform Agent:

CAUTION:
If the repository of virtual appliances has not been relocated from the default
location, the repository and its contents will be permanently deleted when the
IBM z/VM Manageability Access Point Agent is uninstalled. If you want the
repository to remain after you uninstall the IBM z/VM Manageability Access
Point Agent, you can relocate the repository now. For more information about
relocating the image repository, see the relocation step in ″Install the IBM z/VM
Manageability Access Point Agent.″
v Uninstall IBM z/VM Manageability Access Point Agent but keep Platform Agent
running:
1. Type the following command and press Enter:
/opt/ibm/zvmmap/bin/mapuninstall
2. When the uninstallation has completed successfully, 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. Open the /opt/ibm/director/bin/diruninstall script in an ASCII text editor.
2. Set the zVMMAP variable setting to “1”.
3. Save the modified diruninstall script.
4. Type the following command and press Enter:
install_root/bin/diruninstall
where install_root represents the root directory of your IBM Systems Director
installation.
Updating IBM Systems Director VMControl

IBM Systems Director update manager plug-in enables you to acquire, install, and
manage updates, as well as to monitor your systems to ensure that they remain
current.
Use the IBM Systems Director update manager plug-in to update IBM Systems
Director VMControl. For information, see Updating IBM Systems Director.
After installing updates for IBM Systems Director VMControl, you can view the
updates on the IBM Systems Director Welcome page.
Managing workloads in your virtual environment

With IBM Systems Director VMControl, you can capture, import, and deploy
virtual appliances within your environment. First you need to create an image
repository.
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 following pieces to your IBM Systems Director VMControl environment must
be in place for you to use the IBM Systems Director VMControl Image Manager

portion of the product.
v Image repositories - The images that are part of your virtual appliances are
stored in image repositories that you create.
v Agents - For IBM Systems Director VMControl to be able to see the images in
your repositories, you have to install agents on the repository systems. These
agents are specific to your environment (NIM or z/VM).
v Discovery - IBM Systems Director VMControl discovers your image repositories
and views the images that are in them as virtual appliances.
For more information, refer to the IBM Systems Director VMControl requirements
for your specific environment.
Creating and discovering image repositories for NIM

This topic provides information about how to set up your NIM environment for
IBM Systems Director VMControl.
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:

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. Images must be imported or captured after
completing the following steps.
1. Ensure that you have at least one image repository that is suitable for the
virtual appliances that you plan to import and deploy. If you do not have an
image repository, then you need to create one. For more information, refer to
the instructions for preparing and configuring the NIM master in ″Installing
IBM Systems Director VMControl subagent for NIM.″
2. Ensure that the appropriate IBM Systems Director VMControl Image Manager
agent software is installed on the system that hosts your image repository.
Note: Before you install the agent software, you must discover and request
access to the host system (the NIM master), and you must know the name of
that host system.
Click Install Agents... to install the agent software. For more information, see
″Installing IBM Systems Director VMControl subagent for NIM.″
3. Click Discover Virtual Appliances... to discover your repositories and virtual
appliances. Virtual appliances already present in your repositories, that have
been imported or captured using IBM Systems Director VMControl Image
Manager, will be detected by IBM Systems Director VMControl Image Manager.
Additional virtual appliances can be added to your repositories by using the
Import task in IBM Systems Director VMControl Image Manager.
Also, existing virtual servers and mksysb image files can be added to your
repositories as virtual appliances by using the Capture task in IBM Systems
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.
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:

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. Images must be imported or captured after
completing the following steps.
1. Ensure that the appropriate IBM Systems Director VMControl Image Manager
agent software is installed on the system that will host your image repository.
Refer to ″Installing the z/VM manageability access point agent″ to install the
agent software.
2. Ensure that you have at least one image repository that is suitable for the
virtual appliances that you plan to deploy. You might have created an image
repository when you installed the z/VM manageability access point agent. If
you do not have an image repository, then you need to create one. See the
section below for details.
3. Click Discover Virtual Appliances... to discover your repositories and virtual
appliances. 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. Additional virtual appliances can be added to your
repositories by using the Import and Capture tasks in IBM Systems Director
VMControl Image Manager.
Creating an image repository for z/VM
To create an image repository for z/VM, you need to install the z/VM
manageability access point agent. During the installation process, ensure that a
sufficient amount of disk space is provided for the image repository. When
providing disk space for the image repository, consider the size and number of the
images that you plan to create. The location of the image repository can be a
symbolic link so that the repository is not removed when the z/VM manageability
access point agent is removed. For more information, see ″Installing z/VM
manageability access point agent.″

Related tasks
Import
The Import task enables you to import a virtual appliance package, storing the
virtual appliance it contains in IBM Systems Director. You can then deploy the
virtual appliance into your data center.
A virtual appliance package is a representation of a virtual server that contains a

configured, tested operating system and middleware and software applications,
along with the metadata that describes the virtual server.
IBM Systems Director VMControl can import virtual appliance packages that use
the Distributed Management Task Force (DMTF) Open Virtualization Format
(OVF), which is a platform independent and open packaging and distribution
format for virtual appliances. For more information on OVF, see the Open
Virtualization Format Specification available from the DMTF Web site at:
http://www.dmtf.org/standards/published_documents/DSP0243_1.0.0.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, typically with a .ova extension.
You can import virtual appliance packages containing the following virtual server
images:
v AIX mksysb images for IBM POWER logical partitions
The following diagram shows how a virtual appliance package can be imported to
create a new virtual appliance.
1. A user selects a virtual appliance package, virtual appliance package A, to import.
The virtual appliance package can reside either on the Internet, on your IBM
Systems Director Server, or on a Web server that is accessible to your IBM
Systems Director Server.
2. Importing virtual appliance package A results in a virtual appliance, virtual
appliance A, stored on IBM Systems Director Server.
3. Virtual appliance A contains the metadata that describes the virtual server, and a
reference to Image A. Image A contains a fully configured and tested operating
system and software applications for the virtual server and is stored in an
image repository.
4. Virtual appliance A is displayed in a list of virtual appliances that can be
deployed into an environment.

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. The following name and URI formats are
supported:
Power Systems requirements for import
met:
v A NIM master is running and is accessible by your IBM Systems Director Server.
store the AIX mksysb image file associated with the virtual appliance package
that you want to import.

z/VM requirements for import
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.
v The image repository is discovered in IBM Systems Director.
v There is sufficient space in the image repository to store the image associated
with the virtual appliance package that you want to import.
v The virtual appliance package that you want to import was created for z/VM by
IBM Systems Director VMControl Capture or Import tasks.
Related concepts
“Creating and discovering image repositories” on page 41
Related tasks
Related reference
importva command
Capture
The capture task enables you to capture a virtual server or an existing AIX mksysb
image file to create a virtual appliance. 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.
You can capture these types of virtual servers:

The following diagram shows how a virtual server is captured to create a new
virtual appliance.
1. A user selects a virtual server to capture, virtual server A.
2. Capturing virtual server A results in a virtual appliance, virtual appliance A,
stored on IBM Systems Director Server.
3. Virtual appliance A is composed of metadata that describes the virtual server,
and a reference to Image A. Image A contains the full operating system and
software applications and is stored in an image repository.
4. Virtual appliance A is displayed in a list of virtual appliances that can be
deployed into an environment.

Power Systems requirements for capture
You can capture a Power Systems virtual server to create a virtual appliance in the
Hardware Management Console (HMC) or Integrated Virtualization Manager
(IVM)
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.
store the captured virtual server.
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.

v The virtual server has at least one virtual Ethernet adapter.
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
IBM Systems Director VMControl captures one z/VM virtual server at a time.
Subsequent requests for capturing a virtual server are queued for processing.

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:
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.

Power Systems server requirements for deploy
You can deploy a virtual appliance to create or overwrite a virtual server in the
IVM
Note: You cannot perform the deploy, capture, or relocate tasks concurrently for
the same AIX virtual server. Wait until one of these tasks is complete before
beginning another.
v The HMC or IVM that manages the target virtual server is discovered in IBM
HMC or IVM. If the virtual server has an operating system installed, it will be
overwritten when the virtual appliance is deployed.
v A NIM Master is running and is accessible by your IBM Systems Director Server.
v The NIM Master is able to access the target virtual server and the HMC or IVM
that manages it over the network.

Director:
storage devices.
Server.
You can deploy a virtual appliance to a new virtual server when the following
Manager (IVM) that will manage the new virtual server is discovered in IBM
HMC or IVM.
v The NIM Master is running and is accessible by your IBM Systems Director
Server.
v A NIM Master has network access to the HMC or IVM that will manage the
new virtual server.
v The virtual server that you plan to create must have network access to the NIM
Master, and any firewalls must be preconfigured to allow the virtual server to
connect to the NIM Master.
Director:
storage devices.
Server.
System z and z/VM requirements for deploy
On a System z host system that is running the z/VM hypervisor, you can deploy
an empty virtual server to create a virtual server that does not include a virtual
appliance. 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. Subsequent requests for deployment are queued for
processing.
For any z/VM deployment, 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.
v The IBM z/VM Manageability Access Point Agent on the System z host system
is discovered in IBM Systems Director. Access status is listed as OK, and
inventory is collected.
v The virtual server that is the target of the deployment is powered off.
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, 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
images.
v Inventory of the images in the repository has completed.
v Resources required for the image exist on the z/VM system, for example:
– Available network interfaces exist for use by the virtual server.
– Available volumes exist for use by the virtual server.
– If minidisks are required for virtual server storage, the directory manager
supporting the z/VM system must be configured to allocate minidisk
volumes with the Auto-Group option.
additional prerequisites are met:
images.
v Inventory is collected for the images in the repository.
v A virtual server that meets the criteria specified in the image exists and has been
discovered.
Note: If you are deploying to an existing virtual server, the operating system will
be overwritten. You cannot deploy a virtual appliance to z/VM service machines
with the following user IDs, as described in the table:

Table 5. 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
Supported storage devices
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. You can then deploy the virtual appliance into your data center.
The Import wizard can import virtual appliance packages containing the following
virtual server images:
v AIX mksysb images for IBM POWER logical partitions
To import a virtual appliance package, follow these steps:

1. From the IBM Systems Director VMControl Summary page, click Import.

2. Follow the instructions in the Import wizard to import a virtual appliance
package.
3. In the Scheduler window, click OK to import the virtual appliance package
immediately. You can also schedule this task for a later time.
Related concepts
“Creating and discovering image repositories” on page 41
Related reference
importva command
“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, created with AIX or NIM
commands, to create a virtual appliance. You can then deploy the virtual appliance
into your data center.
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.
The following name and URI formats are supported:

v repos://path/file (any IBM Systems Director Server)
To capture the mksysb image file, 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, 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.mksysb

v From a Web server:
-F http://path/mksysb_filename
Example:
-F http://www.acmeimages.com/mksysb/favorite.mksysb
v From your AIX or Linux IBM Systems Director Server, specify either of the
following:
– -F /path/mksysb_filename
– -F file://path/mksysb_filename
Examples:
-F /tmp/mystuff/favorite.mksysb
-F file://tmp/mystuff/favorite.mksysb
v From your Windows IBM Systems Director Server, specify either of the
following:
– -F c:\path\mksysb_filename
– -F file://c/path/mksysb_filename
Examples:
-F c:\tmp\mystuff\favorite.mksysb
-F file://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.mksysb
If the-A attribute_list option is not specified, the following default attributes

will be used:
-A “cpushare=1.0,memsize=1024”
Note: The value of memsize is in megabytes.
Tip: To see the valid values for attribute_list, use the lscustomization command as
follows:
smcli lscustomization -a capture -r 1234
Examples:
This example captures the existing mksysb image file, favorite.mksysb, from NIM
master image repository 1234, assigns the name MyFavoriteVA, and specifies that
the virtual server should have 2.1 CPUs and 4 GB of memory.
smcli captureva -r 1234 -F repos://images/nim/mksysb/favorite.mksysb
-n MyFavoriteVA -A “cpushare=2.1,memsize=4096”
This example captures the mksysb image file, production.mksysb, from

c:\localpath and assigns the name ProductionVA to the resulting virtual
appliance.
smcli captureva -F c:\localpath\production.mksysb -n ProductionVA
After capturing the image, you have a virtual appliance that you can deploy into
your environment. 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.

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. You can then deploy the virtual appliance into your data center.
The Capture wizard can capture these types of virtual servers:

To capture a virtual server, follow these steps:

1. From the IBM Systems Director VMControl summary page, click Capture.
2. Follow the instructions in the Capture wizard to select and capture a virtual
server to create a virtual appliance.
3. In the Scheduler window, click OK to capture the virtual server immediately.
You can also schedule this task for a later time.
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). The wizard guides you through the deployment process.
The Deploy task is available for the following platforms:

1. From the IBM Systems Director VMControl summary page, click Deploy.
Note: You can also access the Deploy wizard using the following methods:
v In the Virtual Appliance view, right-click a virtual appliance and select
Deploy.
v In Resource Navigator, right-click a host system or virtual server and select
Deploy.
2. Complete the instructions in the Deploy wizard to deploy a virtual appliance or
empty virtual server.
3. In the Scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

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,
you can use features of IBM Systems Director to create, edit, and delete them.
For more information, see ″Deploying a virtual appliance or empty virtual server,″
″Editing virtual servers″ or ″Deleting a virtual server permanently.″
Related tasks
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,
you can use manual methods to perform tasks such as copying, deleting, and
modifying your virtual appliances.
Deleting a virtual appliance

You can delete a virtual appliance in a NIM or z/VM environment.
See the instructions for your environment.
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.
To delete a virtual appliance containing an AIX mksysb image, complete the

following steps:
1. From the IBM Systems Director VMControl summary page in the Web
interface, perform the following steps:
a. Click virtual appliances. The Virtual Appliances page is displayed.
b. Select the virtual appliance that you want to delete, click Actions from the
menu bar, and select Related Resources → Software Image.
c. Make note of the leading characters of the software image name that
comprise the Appliance_ID. For example, if the software image name is
63dc39f0-a329-4696-bfb3-2851eca1350d.file1, the Appliance_ID is
63dc39f0-a329-4696-bfb3-2851eca1350d. You will use the Appliance_ID that
you identify in Step 2b on page 59.
2. From your IBM Systems Director VMControl NIM master, perform the
following steps as the root user:

a. Change to the appliances directory using the following command:
cd /export/nim/appliances
b. 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. (See Step 1c on page 58.)
In the output, look for the subdirectory named appliance-n (where n is an
integer), and note this subdirectory name.
c. 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.
d. 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.
a. Click Discover virtual appliances, specify the NIM master as the target,
and click OK.
b. Click virtual appliances. The Virtual Appliances page is displayed.
c. Verify that the virtual appliance you removed is no longer displayed.
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.
To delete a virtual appliance, complete the following steps:

1. From the IBM Systems Director systems management command-line interface,
perform the following steps:
a. 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.1
Description:Linux 197- 8June
b. Using the DisplayName property, locate the virtual appliance to be deleted.

Make note of its ApplianceId property, for example:

e250ed78-3101-4f32-b29d-373c7a4da0fd
2. From the Linux system in which the IBM z/VM Manageability Access Point
Agent is installed, perform the following steps:
a. Log on as root.
d. Run the following command to remove the directory that corresponds to
the software image name:
rm -rf Appliance_ID

want to delete.
e. Run the following commands to start the Platform Agent services:
a. Click Discover virtual appliances, specify the Linux system in which the
IBM z/VM Manageability Access Point Agent is installed, as the target, and
click OK.
c. Verify that the virtual appliance you removed is no longer displayed.
Copying a virtual appliance

You can copy a virtual appliance in a NIM or z/VM environment.
See the instructions for your environment.
Copying a NIM virtual appliance:
Since IBM Systems Director VMControl supports just one NIM master in the IBM
Systems Director VMControl environment, copying a virtual appliance from one
NIM repository to another repository is not applicable.
However, you can store multiple copies of the same virtual appliance in one NIM
repository by importing the virtual appliance package multiple times, or by
capturing the same virtual server or existing mksysb image file multiple times.
Copying a z/VM virtual appliance:
You can copy a z/VM virtual appliance within the same repository, or you can
copy a z/VM virtual appliance from one repository to another repository.
Copying a z/VM virtual appliance within the same repository:

Perform manual steps to copy a z/VM virtual appliance within the same
repository.
To copy a z/VM virtual appliance within the same repository, perform the
following steps:
properties:
smcli lsva -l
VA-197
ChangedDate:2009-06-08T18:22:05-05:00
SpecificationId:1
OID:6585
DisplayName:VA-197
Id:6585
b. Using the DisplayName property, locate the virtual appliance to be copied.

e250ed78-3101-4f32-b29d-373c7a4da0fd
2. From the Linux system in which the IBM z/VM Manageability Access Point
Agent is installed, perform the following steps:
a. Log on as root.
d. 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, for
example:
28399609-2cbc-4ca3-8c63-191f808010fe
e. 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.
f. 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

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.
g. Run the following commands to start the Platform Agent services:
click OK.
c. Verify that the virtual appliance you copied, is displayed.
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.
To copy a z/VM virtual appliance from one repository to another repository,

properties:
smcli lsva -l
VA-197
ChangedDate:2009-06-08T18:22:05-05:00
SpecificationId:1
OID:6585
DisplayName:VA-197
Id:6585
b. Using the DisplayName property, locate the virtual appliance to be copied.

e250ed78-3101-4f32-b29d-373c7a4da0fd
2. From the source Linux system in which the IBM z/VM Manageability Access
Point Agent is installed, perform the following steps:
a. Log on as root.

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.
e. Run the following command to create a tar file that contains the contents of
the directory:
tar -cf appliance.tar *
3. From the target Linux system in which the IBM z/VM Manageability Access
a. Log on as root.
d. 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, for
example:
28399609-2cbc-4ca3-8c63-191f808010fe
e. 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.
f. 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.
g. Transfer the tar file into the directory that corresponds to the appliance ID
in your target repository.
h. Run the following command to extract the contents of the tar file:
tar -xf appliance.tar
i. Run the following command to remove the tar file:
rm appliance.tar
j. Run the following commands to start the Platform Agent services:
4. From the source Linux system in which the IBM z/VM Manageability Access

a. Run the following command to remove the tar file:
rm appliance.tar
b. Run the following commands to start the Platform Agent services:
click OK.
c. Verify that the virtual appliance you copied, is displayed.
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.
To modify the OVF descriptor for a virtual appliance that contains an AIX mksysb
image, complete the following steps:
a. Click virtual appliances. The Virtual Appliances page is displayed.
b. Select the virtual appliance that you want to modify, click Actions from the
menu bar, and select Related Resources → Software Image.
c. Make note of the leading characters of the software image name that
comprise the Appliance_ID. For example, if the software image name is
63dc39f0-a329-4696-bfb3-2851eca1350d.file1, the Appliance_ID is
63dc39f0-a329-4696-bfb3-2851eca1350d. You will use the Appliance_ID that
you identify in Step 2a.
2. From your IBM Systems Director VMControl NIM master, perform the
following steps as the root user:
a. 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

want to modify. (See Step 1c.)
b. Make a copy of the .ovf file found in the /export/nim/appliances/
Appliance_ID directory and store it in a safe location, in case you need to
retract your changes.
c. Manually edit the .ovf file found in the /export/nim/appliances/
Appliance_ID directory.
a. Click Discover virtual appliances, specify the NIM master as the target,
and click OK.

c. Verify that the virtual appliance you modified is still listed. If you made
changes to the name or description of the virtual appliance, they should be
reflected in the list.
Note: If the virtual appliance is no longer listed, then your changes to the
.ovf file have rendered it non-compliant and IBM Systems Director
VMControl will not recognize it as a valid virtual appliance. If this happens,
try restoring the original .ovf file that you saved in step 2b on page 64.
Then retry step 3 on page 64. Your virtual appliance should be listed again.
You can then try step 2 on page 64 again, being particularly careful at step
2c on page 64 to make compliant changes only.
Backing up and restoring virtual appliances in NIM repositories

To back up and restore the virtual appliances in a NIM repository, you can create a
tar file of the virtual appliances, use a compression tool such as Gzip, and the
System Management Interface Tool (SMIT).
Perform the following steps to back up and restore the virtual appliances stored in
a NIM master repository.
Note: You must be logged on to the NIM master system as the root user to
complete this procedure.
1. Tar and gzip the directories /tftp and /export/nim to create a tarball, for
example, nimrf.tar.gz.
a. Run the following command to create a tar file:
tar -cvf /usr/nimrf.tar "/export/nim/appliances" "/tftpboot"
where nimrf is the name that you want to assign to your virtual appliance
backup.
b. Run the following command to compress the tar file:
gzip /usr/nimrf.tar
c. The result is /usr/nimrf.tar.gz that contains the virtual appliances known
to the NIM master.
2. Create a backup file of the NIM database using the SMIT interface. Run the
following command to create a backup, for example master.bk.
smit nim_backup_db
Using the SMIT interface, create a backup such as to /etc/objrepos/master.bk,

where master.bk is the name you assign to the virtual appliance backup.
3. Store nimrf.tar.gz and master.bk on some other system for safe keeping.
4. To restore the backup to a different NIM master, select an AIX system that has
the nim.master fileset installed, but is not configured in any way.
5. Create the /tftpboot and /export/nim file systems manually if they do not
exist. Make sure they are empty before continuing.
6. Run the following commands to unzip and extract /usr/nimrf.tar.gz. that you
created on the backup system.
gunzip /usr/nimrf.tar.gz
tar -xf /usr/nimrf.tar "/export/nim/appliances"
tar -xf /usr/nimrf.tar "/tftpboot"
7. Use the SMIT interface to restore the NIM database backup that you created,
master.bk in this example, using the following command:
smit nim_restore_db

8. Perform virtual appliance discovery. The NIM repository and the restored
virtual appliances should be discovered on the NIM master system where you
restored the NIM database.
Troubleshooting and support

This topic provides troubleshooting information for IBM Systems Director
VMControl.
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, there might be temporary files
or processes left behind in the temporary directory.
Problem
Installing IBM Systems Director VMControl multiple times might result in large
numbers of temporary files and processes remaining in the temporary directory.
These remaining files and processes can cause performance problems and use
needed disk space.
Resolution
Delete the temporary files and stop the processes in the /tmp folder to free disk
space on your system.
IBM Systems Director VMControl installer results in error state

This problem affects IBM Systems Director VMControl running on an AIX
management server.
Problem
While installing IBM Systems Director VMControl, you selected to restart IBM
Systems Director Server. IBM Systems Director Server is now in an Error state.
Investigation
You can check whether IBM Systems Director Server is in an error state by using
the smstatus command.
Resolution
If IBM Systems Director Server is in an Error state, you can use the smstart
command or restart IBM Systems Director Server to return IBM Systems Director
Server to a normal state.

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.
Problem
When installing IBM Systems Director VMControl subagent for NIM using the
Agent Installation wizard, you receive one of the following error messages:
v COPDEX040E: An unexpected deployment engine exception occurred.
v COPDEX123E: The workflow threw a MissingOperatingSystemException
exception.
Explanation
There might be several reasons for this error. Use the information in the following
table to determine the cause of the error and solve the problem:
Table 6. 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. <director>/agent/logs/trace-log-0.xml
error log for a message beginning with
DNZIMN. The message describes why the
installation failed. One possible reason is
that you have not met all of the
requirements for IBM Systems Director
VMControl subagent for NIM.
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. and Common Agent remain synchronized.
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.
feature has already been installed.
v Remove the agent system from IBM
Systems Director Server, rediscover it, and
install IBM Systems Director VMControl
subagent for NIM using the Agent
Installation wizard.

Table 6. 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. and ensure that the CAS protocol is active
for this system. To check if the CAS protocol
is active, follow these steps:
1. Click Navigate Resources.
2. Click the All Operating Systems group.
3. Click agent system.
4. Check if CAS appears next to Protocols.
Related tasks
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.
Problem
When you attempt a manual installation of IBM Systems Director VMControl

subagent for NIM, you see the following message:
Requested operation cannot be performed because it would invalidate the
current configuration.
Resolution
To correct this problem, ensure that the system you are installing the agent on has
been updated to IBM Systems Director version 6.1.1.1.
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.
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. The z/VM virtual servers are displayed in the IBM Systems Director Web
interface, and the appropriate access state is listed for each virtual server.
You restart IBM Systems Director Server. When you view the virtual servers in
IBM Systems Director, you notice that the access state for each of the z/VM virtual
servers is Unknown.
Explanation
This is a known limitation of IBM Systems Director VMControl Image Manager.

The IBM Systems Director Web interface indicates the incorrect access state of

Unknown for z/VM virtual servers after restarting IBM Systems Director Server.
However, normal management functions through the Web interface are not
adversely affected. For example, you can continue to use the Web interface to
power on, power off, capture, deploy, 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.
In addition, you can refer to the State column in the Web interface to determine
whether the virtual server is Started or Stopped.
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.
Problem
You try to discover a NIM master that is not currently configured to be the image
repository for IBM Systems Director VMControl, and the task fails.
Explanation
IBM Systems Director VMControl can only recognize one NIM master as an image
repository. Multiple NIM master image repositories are not supported.
If you want to use a different NIM master as your image repository, you need to
first remove the current NIM master from the IBM Systems Director database.
Then you can discover, access, and collect inventory for the new NIM master.
Resolution
To remove a NIM master from the IBM Systems Director database, you must
remove both the Server and Operating System managed objects that represent the
NIM master.
To use a new NIM master, ensure that the new NIM master is properly configured.
For more information, see “Installing IBM Systems Director VMControl subagent
for NIM.″ Then, discover, request access, and collect inventory for the new NIM
master.
Related tasks
Task fails after copying a scheduled job

This problem affects any IBM Systems Director VMControl Image Manager task.

Problem
After scheduling a task such as capture or deploy, you copy the job to create a
duplicate scheduled job. To copy the job, you use the Create Like option under
Active and Scheduled Jobs. When the new scheduled job runs, the task fails with
a Null Pointer Exception error.
Explanation
The required parameters are not being passed to the duplicate task.
Resolution
This is a known limitation of IBM Systems Director VMControl Image Manager.

Do not run the task by copying the scheduled job.
Import from a network shared volume fails

This problem affects the Import task on IBM Systems Director Server running on
Windows.
Problem
You try to import an OVF package, as a set of files or as a compressed OVA, from
IBM Systems Director Server that is running on Windows. The files to be imported
are on a network share and the path is provided in UNC (Universal Naming
Convention) format, for example, \\computername\share\path. The import task
fails with the following error, even when the file exists:
OVF File FileName not found.
where FileName is the name of the OVF package.
Explanation
By default, IBM Systems Director Server runs as a Windows service as user

LocalSystem; this user does not normally have enough permissions to access a
network share.
Resolution
Run IBM Systems Director Server as the Administrator user, or another user with
authority to access the network share.
To change the user to Administrator, complete the following steps:

1. From the Windows Start menu, open Control Panel → Administrative Tools →
Services.
2. Right-click IBM Systems Director Server and select Properties.
3. On the Log On page, change the user from LocalSystem to Administrator.
4. Restart the IBM Systems Director Server service.
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.3 or 6.1.

Problem
When capturing a IBM Power Systems virtual server, the task fails. 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, by performing the following actions:
v In the IBM Systems Director navigation pane, click Task Management → Active
and Scheduled Jobs. Determine whether another capture or deploy task to the
same virtual server was running when your task started.
v Look in file /var/adm/ras/nimlog on the NIM master. Determine whether a
mksysb task was running when your task started.
Explanation
The capture task will not complete successfully on the target system if another
operation, such as a capture, deploy, or NIM mksysb task, is already running on
that system.
Resolution
Wait until the pre-existing task is complete. Then, try the capture task again.
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.
Problem
When capturing a z/VM virtual server, the task fails. An error message indicates
that there is a failure to access an LVM volume group.
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. This can occur when both systems have
volume groups that were cloned from the same source.
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. This can occur when default names or conventions are used. For example,
both systems might have volume groups with a generic name, such as opt-vg.
Resolution
If you are using LVM, 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.

v Give the volume groups system-unique names. Or, 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.
Capture task fails and indicates SSH connection problems

This problem affects the capture task when targeted to a z/VM virtual server.
Problem
When capturing a z/VM virtual server, the task fails. An error message indicates
that an SSH connection to the capture target could not be established.
Explanation
This problem can occur for one of the following reasons:

v The capture target is unreachable, for example, if the capture target is on a
different network than the z/VM manageability access point.
v The capture target is unresponsive, for example, if the capture target fails to boot
properly and start up network services.
v The capture target is configured to reject root log-ins through SSH.
v The capture target is missing proper credentials for recognizing and granting
access to the z/VM manageability access point.
Resolution
Perform one or more of the following actions:

v If the capture target is offline, or in a non-networked run-level, IPL the capture
target and ensure that it completes the boot process.
v If the capture target is configured to reject SSH connections or remote root
log-ins, edit /etc/ssh/sshd_conf on the capture target to permit them.
v Remove any lines for the capture target from the known_hosts file on the z/VM
v Remove any lines for the z/VM manageability access point in the
authorized_keys file on the capture target. Then, add an entry for the z/VM
manageability access point to the authorized_keys file using the contents of the
/root/.ssh/ibm_zvmmap_id-rsa.pub key 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.pub, then create a key pair using
ssh_keygen.
v If the capture target is not connected to a network that is accessible from the
z/VM manageability access point, you must connect it to such a network before
performing the capture task.
v You can run the following script to accomplish several of the preceding
troubleshooting steps:

#!/bin/bash
###############################################################################
# Adds the /root/.ssh/ibm_zvmmap_id_rsa.pub ssh public key to remote_server's #
# authorized_keys list. #
# #
# @param $1: The IP address or hostname of the remote server to be accessed. #
###############################################################################
##### START EXECUTION #########################################################
remote_server=$1
hostname=$(hostname)
# Go to root's .ssh directory.
cd /root/.ssh
# Create a "zvmmap" RSA key if one doesn't already exist.
if [[ ! -f /root/.ssh/ibm_zvmmap_id_rsa ]]; 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.
sed -i "/^${remote_server}/d" known_hosts
# Remotely touch the remote server's authorized_keys file to make sure it will
# be there, remove any existing key entries for this host, and append this
# host's public key to the remote server's authorized_key file.
key="$(cat ibm_zvmmap_id_rsa.pub)"
ssh root@${remote_server} "mkdir /root/.ssh;

cd /root/.ssh;
touch authorized_keys;
sed -i \"/.*${hostname}$/d\" authorized_keys;
echo \"${key}\" >> authorized_keys"
# Test the connection.
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.
cd -
exit 0
##### END OF SCRIPT ###########################################################
Capture or deploy of virtual server hangs

This problem affects the capture or deploy task when capturing from, or deploying
to, a Linux virtual server on System z.
Problem
When capturing from, or deploying to, a Linux virtual server on System z, the job
hangs indefinitely. This problem can occur when using either the IBM Systems
Director Web interface or the IBM Systems Director systems management
command-line interface.

Explanation
The capture or deploy task can hang when a lock file is created, but not deleted,
by a previous capture or deploy job that stops abruptly. For example, this problem
can occur when the previous job is stopped manually, 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
To resolve the problem, complete the following steps:

1. Log on to the z/VM manageability access point system.
2. Run the following commands to stop the IBM z/VM Manageability Access
Point Agent:
3. 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.3 or 6.1.
Problem
When you try to capture a virtual appliance from a Power Systems virtual
machine, 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>.
Explanation
This problem can occur if the machine you are trying to capture was previously
deployed or captured, using a different hostname. When you attempt to capture
the machine using a different hostname, a new NIM machine object cannot be
created because the existing machine object already has the same MAC address.
NIM cannot store two machines with the same MAC address.
Resolution
Complete the following steps to remove the existing NIM machine object from the
NIM master manually. Then you can attempt to capture it again.
1. In the Web interface, check the properties of the machine that you are
attempting to capture. Locate the MAC Address property.
2. Log on to the NIM master as root user.
3. 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.

4. 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. When the NIM machine is removed, you can attempt the capture task again.
Capture from file fails when using HTTP protocol

This problem occurs when you attempt to capture an image file that is larger than
2,147,483,647 bytes using HTTP protocol.
Problem
When you attempt to capture an image file using HTTP protocol, a

getContentLength error occurs.
Explanation
This problem occurs when you attempt to capture an image file that is larger than
2,147,483,647 bytes using HTTP protocol.
Resolution
Download the image file to disk using a Web browser or some other means. Try
the capture task again, 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.
Problem
A Red Hat Enterprise Linux server fails to boot after it is deployed. In addition, an
error similar to the following example is displayed:
/bin/mingetty: error while loading shared libraries:
libc.so.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, through a z/VM manageability access point on which an old version of
the star command was installed. Old versions of the star command contain a bug
that prevents the extended attributes for soft links from being correctly written on
deploy. Consequently, SELinux denies access to these files.
Resolution
Either disable SELinux on the capture target by setting it to permissive mode in

the /etc/selinux/config file, or upgrade the star installation on the z/VM
manageability access point to version 1.5 (final).

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

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

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

3) In the output, look at the Physloc column for each vhost device. The
Physloc column contains the virtual slot number of the virtual SCSI
server adapter used by the vhost. For example, a row such as vhost0
U9133.55A.10DA01G-V1-C2 contains C2 at the end. This indicates that the
vhost0 device is using the virtual SCSI server adapter in virtual slot 2.
The number X in CX at the end of the vhost identifier is the virtual slot
number.
4) If you find the virtual slot recorded above in output of the lsmap
command, then record the vhost for that virtual slot.
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.
d. When you are done removing all the virtual SCSI server adapters and the
corresponding vhost devices, restart the Virtual I/O Server partition. If you
do not want to restart the Virtual I/O Server, 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.
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.
Problem
During the deploy operation, the SSH key exchange fails. The dkeyexch command
returns an unknown status and you receive an error similar to the following:
DNZIMN867E Could not exchange SSH key with 9.12.28.87 due to the following error:
2760-287 [dkeyexch] Internal error - exchange script returns unknown error: 1.
Resolution
Rerun the dkeyexch command on your NIM master to exchange the SSH keys.
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.12.28.87
In this example, you are exchanging the SSH key on an Integrated Virtualization
Manager (IVM) access point. You can use the dkeyexch command to exchange the
key on other access points, such as the Hardware Management Console (HMC).
For more information, see the man page for the dkeyexch command.
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.
Problem
When you are using the Deploy wizard to deploy a virtual appliance in a Power
Systems environment, you select a target system and receive the following error:
DNZIMN107E: An error occurred during the deploy operation.

Resolution
This error can occur when IBM Systems Director has not completed the inventory
collection process for the target system. You can either wait for the process to
complete, or you can explicitly perform the collect inventory task on the target
system. When inventory collection is complete for the target system, you can
attempt the deploy task again.
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).
Problem
When attempting to use the deploy task to target a system that is managed by
HMC or IVM, you receive the following message:
DNZIMN871E Another operation is in progress. Unable to lock HMCName for deployment.
Explanation
Some deploy tasks fail when multiple deploy tasks are scheduled simultaneously
to partitions that are managed by the same HMC or IVM.
Resolution
A lock timeout may occur if too many deploy tasks are scheduled concurrently for
a given HMC or IVM. To avoid the lock timeout, schedule the deploy tasks to be 5
to 10 minutes apart so that the NIM master can complete its processing.
Product panel of Deploy wizard is blank

This problem is encountered when attempting to deploy a virtual appliance that is
in a NIM repository.
Problem
When you attempt to deploy a virtual appliance that is in a NIM repository, the
Product panel of the Deploy wizard does not contain any fields that you can edit.
When you click Finish and complete the wizard, you receive the following error
DNZIMC706E An unexpected error has occurred. See the error log for more information.
Explanation
The OVF for the virtual appliance does not contain a Product section with user
editable properties. The NIM deploy requires three properties to be set in the top
level product section of the OVF. These properties are:
<ovf:Property ovf:key="networkport.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.RASDID.gateway" ovf:type="string"

<ovf:Label>Static default gateway.</ovf:Label>
<ovf:Description>Static default gateway.</ovf:Description>
</ovf:Property>
<ovf:Property ovf:key="networkport.RASDID.netmask" ovf:type="string"
<ovf:Label>Static network.</ovf:Label>
<ovf:Description>Static network.</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. For example, 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.</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. 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.ibm.ovf.vim.2"
vim:instance="" vim:key="networkport.RASDID.ip"/>
<vim:NetworkBootIpAddress vim:class="com.ibm.ovf.vim.2"
vim:instance="" vim:key="networkport.RASDID.ip"/>
</ovf:OperatingSystemSection>
</ovf:VirtualSystem>
Resolution
The original OVF should be modified so it contains the required properties and
then be re-imported.
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.
Problem
When attempting to deploy a virtual appliance from a NIM repository to an

existing virtual server, you receive the following error:
DNZIMN882E The deploy task is not progressing and has timed out.
Explanation
If the NIM image repository (NIM Master) connects to IBM Systems Director
Server through one network adapter, and connects to the virtual server where you
plan to deploy the virtual appliance through a different network adapter, the
secondary adapter might not be configured correctly.

Resolution
Complete the following steps to create a secondary NIM network resource and
configure NIM to use this secondary adapter:
1. Log on to the NIM Master.
2. When you ran nim_master_setup to configure your NIM Master, the master_net
network object was created for you to represent the network associated with
the NIM Master’s primary network interface. If the NIM Master has a
secondary interface that you will be using to deploy virtual servers, then you
will need to create one or more additional NIM network definitions.
Note: Do not define a NIM network object name that begins with the name of
another NIM network object.
a. Define a NIM network object for the NIM Master’s secondary network
interface. For example:
nim -o define -t ent -a net_addr=1.2.3.4 -a snm=255.255.255.0 secondary_net
where 1.2.3.4 is the IP address of the network being defined, 255.255.255.0 is

the subnet mask for the network, and secondary_net is the NIM network
object name that you are creating.For more information, see the Defining
NIM networks topic in the IBM Systems Information Center.
b. If the virtual server that you will be deploying is on the same network as
the NIM Master’s secondary interface, then skip this step. If it is on a
different network, then you must define another NIM network object for the
virtual server. For example:
nim -o define -t ent -a net_addr=2.2.3.4 -a snm=255.255.255.0 deploy_net
where 2.2.3.4 is the IP address of the network being defined, 255.255.255.0 is

the subnet mask for the network, and deploy_net is the NIM object name
that you are creating.
3. Attach the secondary_net network object you created to the NIM Master
resource, for example:
nim -o change -a if2='secondary_net 1.2.3.4 0' -a cable_type2=N/A master
4. If you created a new deploy_net network, a static route must be established
between it and the secondary_net network object. For more information, see the
Establishing a static NIM route between networks topic in the IBM Systems
Information Center. You should also remove the default route on the deploy_net
network.
5. 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, or add it to /etc/hosts on the NIM Master.
When you have completed these steps, attempt to deploy the virtual appliance to
the virtual server again.

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.
Problem
When attempting to deploy a virtual appliance from a NIM repository to a new

virtual server, you receive the following error:
DNZIMN882E The deploy task is not progressing and has timed out.
Explanation
The deployment of a new AIX virtual server fails if the server does not have
network connectivity to the NIM Master, or if the virtual server cannot get
thorough a firewall to the NIM Master.
Resolution
Complete the following steps:

1. Ensure that there is network connectivity between the virtual server and the
NIM Master.
2. 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.
Alternatively, you can choose a different NIM Master that is within the same
firewall as the virtual server, to serve as the image repository.
3. Retry the deploy task after the network and firewall have been configured
correctly.
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.
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, the DNZIMC763E message is
displayed on the Minidisks page.
Explanation
IBM Systems Director VMControl populates the Deploy wizard with values from
the source virtual server or virtual appliance. However, you need to provide
additional information about the minidisks that will be created for the new virtual
server.

Resolution
To resolve the problem, complete the following steps:

1. From the Minidisks page, select one of the minidisks and click Edit.
2. On the Edit Minidisk page, complete the following information for the minidisk
that will be created for the new virtual server:
a. In the Disk Allocation Type field, select the type.
b. In the Disk ID field, select the ID.
3. Click OK to return to the Minidisks page.
4. Repeat steps 1-3 for each minidisk listed in the table.
Then, continue using the Deploy wizard.
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.
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. The size of the minidisk
must be changed to a different size before creating the new virtual server.
Explanation
The negative one (-1) for the size of the minidisk indicates that the minidisk is
using the remaining space on the volume. z/VM indicates this in the user
directory as END. IBM Systems Director shows this as negative one (-1) for the
size. When creating a minidisk for a virtual server, a valid size is required.
Negative one is not accepted.
Resolution
Specify the appropriate size for the minidisk that is being created. Log on the
virtual machine and query the device, for example, query 191.
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.
Problem
When you deploy a virtual appliance in a Power Systems environment, 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.
Explanation
When using the Deploy wizard or the command-line interface, you can specify
both an IP address and a hostname for the target virtual server. If the IP address
and hostname do not map to one another through DNS or /etc/hosts on the NIM
master, then the IP address takes precedence. In this situation, the hostname for the

new virtual server does not change to the name you specified in the Deploy
wizard or command-line interface.
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.
Unable to edit virtual server properties related to virtual CPU

This problem affects the edit task when targeted to a z/VM virtual server.
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. 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.
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. The IBM z/VM Manageability Access Point Agent attempted to modify
the CPU statement and one did not exist. The modification did not occur.
Resolution
On z/VM use the directory manager to add a CPU statement to the user directory
for the virtual server. When the CPU statement is added to the user directory for
the virtual server, 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.
Problem
When editing a System z virtual server or creating a new virtual server based on
an existing virtual server, the virtual processors do not indicate that a processor is
dedicated.
Explanation
The property indicating that the virtual processor is dedicated is not returned with
the proper value. The value is always shown as not dedicated.
Resolution
This is a current known limitation.

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.
Problem
When you attempt the edit virtual server task for active and stored settings of a
System z virtual server, the minidisks associated with the virtual server are
attempted to be modified, although you did not request the minidisk change.
Explanation
The minidisk modification attempt occurs because of a difference between the

active and stored settings for the minidisks. The modification will not succeed.
Resolution
Edit the active and stored settings separately.
Unable to set virtual processor to dedicated with edit virtual

server
virtual server.
Problem
When editing a System z virtual server, the dedicated property cannot be set for
virtual processors that are added or modified.
Explanation
The minidisk modification attempt occurs because of a difference between the

active and stored settings for the minidisks. The modification will not succeed.
Resolution
This is a current known limitation for IBM Systems Director VMControl.
You can update the z/VM user directory for the virtual server using the z/VM
directory manager. Specify the DEDICATED option on the CPU statement for the
virtual server.
Editing virtual server to add virtual switch or guest LAN

results in error
virtual server.
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, an error is returned for
the job. The error indicates an unexpected error with return code 204, reason code

20 from Virtual_Network_Adapter_Connect_LAN.
Explanation
The network interface was successfully added. The return code and reason code
indicate that the device was automatically coupled to the LAN by the z/VM
control program. The IBM Systems Director Server is not updated with information
on the resource changes. 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.
Deploy to a NIM Master fails with error DNZIMN868E

Problem
When you try to deploy a virtual appliance to a NIM Master, 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>. 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, delete the existing NIM machine from the NIM Master
manually and try the deploy again. Follow these steps to remove the existing NIM
machine from the NIM Master:
1. Log on to the NIM Master as the root user.
nim -Fo reset <name of the NIM machine that you want to delete>
nim -Fo deallocate -a subclass=all <name of the NIM machine that you want to delete>
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.
Problem
After you uninstall an IBM Systems Director VMControl agent, either the IBM
Systems Director VMControl subagent for NIM or the IBM Systems Director z/VM
manageability access point agent, 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.

Explanation
There is no automatic mechanism for IBM Systems Director Server to be notified

when the IBM Systems Director VMControl agents are uninstalled. Therefore,
when the agents are uninstalled, IBM Systems Director Server continues to allow
you to interact with the image repository and virtual appliances to a degree.
However, any actions you attempt to perform against the image repository or
virtual appliances (such as discover, capture, or deploy) will fail, since IBM
Systems Director Server is no longer able to perform these IBM Systems Director
VMControl actions on the image repository system.
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.
Attention: Completing the following steps will cause all history and automatic
event automation for the managed system to be lost.
1. 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. Rediscover and request access to the managed system again, if you still require
access when it no longer contains the image repository.
Related tasks
Removing a resource
Performing a system discovery
Reference
This section provides reference information for IBM Systems Director VMControl,
including commands and OVF specifications.
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.
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.
deployva
Use the deployva command to deploy a virtual appliance into a new or
existing virtual server as a workload.

importva
Use the importva command to import a virtual appliance into IBM
Systems Director VMControl Image Manager.
lscapsrv
Use the lscapsrv command list servers that you can capture as virtual
appliances.
lscustomization
Use the lscustomization command to list attributes that you can customize
for a virtual appliance when you run the captureva, deployva, or importva
commands.
lsdeploytargets
Use the lsdeploytargets command to list the target servers or hosts on
which you can deploy a virtual appliance workload.
lsrepos
Use the lsrepos command to list repositories.
lsva Use the lsva command to list virtual appliances.
How to read syntax diagrams

Review the conventions used in syntax diagrams to understand the command
descriptions.
Syntax diagrams consists of options, option arguments, and operands.

Options
Options indicate input that affects the behavior of the base command (for
example, -l specifies long output) or required input that you can specify in
different ways (for example, you can target objects using either -n name OR
-N groupname OR -ac objectclass). Options consist of either a hyphen and
single letter (for example, -h) or two hyphens and multiple letters (for
example, --help). The single letter format is the short form of the multiple
letter format, and the two formats are functionally interchangeable when
issuing a command.
Option arguments
Some options are followed by one or more option arguments that specify a
value for the option. For example, with -file file_name, file_name
specifies the name of the file on or with which to take action.
Operands
Operands are parameters at the end of a command that specify required
user input.
Syntax diagrams adhere to the following conventions:

v Options and operands that are enclosed in brackets ([]) are optional. Do not
include these brackets in the command.
v Options and operands that are enclosed in braces ({}) are required. Do not
include these braces in the command.
v Options and operands that are not enclosed in either brackets or braces are
required.
v Operands and option arguments that are italicized must be replaced with actual
values.
v The names of options are case sensitive and must be typed exactly as shown.
v Options preceded by two dashes (--) must be specified in their entirety.

v A pipe (|) character signifies that you can or must, depending on the enclosing
characters, choose one option or the other. For example, [a | b] indicates that
you can choose either a or b, but not both. Similarly, {a | b} indicates that you
must choose either a or b.
v An ellipsis (...) signifies that you can repeat the operand and option argument
on the command line.
v A dash (-) represents standard output.
captureva command
Use the captureva command to capture a virtual appliance from a virtual server or
from an existing AIX mksysb image file.
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

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.
FlagsOptions
-A | --attribute ″key=value [, ...]″
Assigns values to one or more customizable attributes, where key is the
attribute key and value is the new attribute value.
Tips:
v You can use the lscustomization command to list all customizable attributes.
– To list the customizable attributes for capturing a virtual server, 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, run the following command:
smcli lscustomization -a capture -r repository
Note: Customization is not supported when performing the capture task on

z/VM.
v Separate the key-value pairs with commas (for example,
″cpushare=2.1,memsize=4096″).
v The attributes and attribute values are not locale specific.
-D | --description ″description″
Specifies descriptive text that you supply for the object that is created. If the
description contains special characters such as spaces or commas, enclose the
description in quotation marks.

-F | --fileLocation ″file_location″
Specifies the name or URI of an existing mksysb image file that you want to
capture. If the name or URI contains spaces, 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)
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.
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.
Note: This option is not supported when performing the capture task on
z/VM.
-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 for the virtual appliance that is created. If the name contains
special characters such as spaces, enclose the name in quotation marks.
-r | --repository repository
Specifies the unique ID (OID) of the targeted repository object.
Specify the unique ID as a decimal or hexadecimal value (for example, 123 or
0x7b).
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.
0x7b).
Tip: Use the lscapsrv command with the -o option to list the name and OID of
all servers that you can capture.
-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 47: The virtual appliance could not be created.
v 60: An illegal parameter was used.
v 125: The command terminated.

Examples
1. Capture the workload from a server
This example illustrates how to capture the workload from server 123.
smcli captureva -v -s 123 -r 345 -n "XYZLpar" -D "Production server"
2. Capture an image on a NIM master
This example illustrates how to capture an existing AIX mksysb image residing
on your NIM master.
smcli captureva -v -r 345 -F repos://tmp/old.mksysb -n "oldImage"
Related tasks
“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.
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.
Tip: To deploy an empty virtual server, which is a function that is available in the
IBM Systems Director Web interface deploy wizard, run the mkvs command.
FlagsOptions
-a | --action {deploy_existing | deploy_new}
Specifies the target action. The following deployment actions are supported:
deploy_existing
This action deploys a virtual appliance to an existing virtual server.
deploy_new
This action deploys a virtual appliance to a newly created virtual
server on the specified host system.
Tips:
v You can use the lscustomization command to list all customizable attributes.
– To list the customizable attributes for deploying a virtual appliance to an
existing virtual server, run the following command:
smcli lscustomization -a deploy_existing -V virtualAppliance -s server

– To list the customizable attributes for deploying a virtual appliance to a
new virtual server, 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, the following minimum set of customizable attributes are
required:
deploy_existing case
– product.AIX1.com.ibm.ovf.vim.2.networkport.6.ip
– product.AIX1.com.ibm.ovf.vim.2.networkport.6.netmask
– product.AIX1.com.ibm.ovf.vim.2.networkport.6.gateway
deploy_new case
– product.AIX1.com.ibm.ovf.vim.2.networkport.6.ip
– product.AIX1.com.ibm.ovf.vim.2.networkport.6.netmask
– product.AIX1.com.ibm.ovf.vim.2.networkport.6.gateway
– product.AIX1.com.ibm.ovf.vim.2.system.hostname
– poolstorages
v If you are deploying a virtual appliance that contains a Linux image for
z/VM, the following minimum set of customizable attributes are required:
deploy_existing case
– Operating system information for the host name, domain name,
and time zone
– Operating system information for each network interface that was
captured in the image, which includes the IP address, gateway
address, 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, domain name,
and time zone
– Operating system information for each network interface that was
captured in the image, which includes the IP address, gateway
address, subnet mask, and use of DHCP
-h | -?
ignored.
--help

Tips:
ignored.
v de: German
v en: English
v es: Spanish
v fr: French
v it: Italian
v ja: Japanese
v ko: Korean
Tips:
-s | --server {server | host}
Specifies the unique ID (OID) of the targeted server or host object.
0x7b).
Tips:
v Use the lsdeploytargets command with the -o option to list all servers and
hosts.
v If the deploy_existing action is specified, then you must specify an existing
virtual server.
v If the deploy_new action is specified, then you must specify a virtualization
host system.
-v | --verbose
-V | --virtualAppliance virtual_appliance
Specifies the unique ID (OID) of the targeted virtual appliance object on which
you want to take action.
0x7b).
Tip: Use the lsva -l command to list all virtual appliance IDs.

Exit status

v 62: Deployment of the virtual appliance failed.
v 65: An illegal customization format was used.
Examples
1. 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).
smcli deployva -v -s 123 -V 345 -a deploy_new -A
"poolstorages=rootvg:VIOS vioserver,
virtualnetworks[Virtual Network 1]=hostVnet:ETHERNET0/1,
product.AIX1.com.ibm.ovf.vim.2.system.hostname=dir44,
product.AIX1.com.ibm.ovf.vim.2.networkport.6.ip=1.22.33.44,
product.AIX1.com.ibm.ovf.vim.2.networkport.6.hostname=dir44,
product.AIX1.com.ibm.ovf.vim.2.networkport.6.netmask=255.255.255.192,
product.AIX1.com.ibm.ovf.vim.2.networkport.6.gateway=5.22.33.254,
product.AIX1.com.ibm.ovf.vim.2.networkport.6.dns1.ip=5.44.3.2"
2. 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.
smcli deployva -v -s 975 -V 348 -a deploy_existing -A
"product.AIX1.com.ibm.ovf.vim.2.networkport.6.ip=1.22.33.44,
product.AIX1.com.ibm.ovf.vim.2.networkport.6.netmask=255.255.255.192,
product.AIX1.com.ibm.ovf.vim.2.networkport.6.gateway=5.22.33.254"
3. 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.
smcli deployva -v -a deploy_existing -V 4677 -s 4091 -A
product.LINUX235.com.ibm.ovf.vim.2.zvm.5.networkport.eth0.usedhcp=false,
product.LINUX235.com.ibm.ovf.vim.2.zvm.5.networkport.eth0.ip=5.66.77.88,
product.LINUX235.com.ibm.ovf.vim.2.zvm.5.networkport.eth0.gateway=5.66.77.99,
product.LINUX235.com.ibm.ovf.vim.2.zvm.5.networkport.eth0.netmask=
255.255.255.128,
product.LINUX235.com.ibm.ovf.vim.2.zvm.5.networkport.eth0.dns1.ip=8.7.6.55,
product.LINUX235.com.ibm.ovf.vim.2.zvm.5.networkport.eth0.registerindns=true,
product.LINUX235.com.ibm.ovf.vim.2.zvm.5.networkport.eth0.hostname=gses88,
product.LINUX235.com.ibm.ovf.vim.2.zvm.5.networkport.eth0.domainname=
spot.abc.com,
product.LINUX235.com.ibm.ovf.vim.2.zvm.5.system.hostname=gses88,
product.LINUX235.com.ibm.ovf.vim.2.zvm.5.system.domainname=spot.abc.com,
product.LINUX235.com.ibm.ovf.vim.2.zvm.5.timezone.offset=-0400

Related tasks
importva command
Use the importva command to import a virtual appliance into IBM Systems
SyntaxSynopsis
smcli importva {-h | -? | --help} [-L language]
smcli importva [-L language] [-v] -F fileLocation -r repository [-n name]

Description
The importva command imports a virtual appliance in Open Virtualization Format

(OVF) into IBM Systems Director VMControl Image Manager, making it available
for deployment. Virtual appliances in either OVF package form (TAR file or
set-of-files) are acceptable.
FlagsOptions
Tips:
v To list all customizable attributes for the importva command, use the
following command:
smcli lscustomization -a import -F fileLocation -r repository
-D | --description ″description″
Specifies descriptive text that you supply for the object that is created. If the
description contains special characters such as spaces or commas, enclose the
description in quotation marks.
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 .ova file (an OVF package in TAR format) that you want to import.
If the name or URI contains spaces, enclose it in quotation marks. The
following name and URI formats are supported:
only)

only)
-h | -?
ignored.
--help
Tips:
ignored.
v de: German
v en: English
v es: Spanish
v fr: French
v it: Italian
v ja: Japanese
v ko: Korean
Tips:
-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.

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
Exit status

v 63: Importation of the virtual appliance failed.
v 73: An illegal name change was attempted.
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
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.

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 | -?
ignored.
--help
Tips:
ignored.
-l | --long
Displays all attributes of the specified object.
v de: German
v en: English
v es: Spanish
v fr: French
v it: Italian
v ja: Japanese
v ko: Korean
Tips:
-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.

-v | --verbose
Exit status

v 69: An invalid criteria was used.
v 70: Creation of a list of servers that can be captured failed.
Examples
1. Display servers that you can capture
This example illustrates how to display a list of servers that you can capture.
smcli lscapsrv -v
2. Display servers and object IDs that you can capture
This example illustrates how to display a list of servers, along with their object
IDs, that you can capture.
smcli lscapsrv -v -o
Related tasks
lscustomization command
Use the lscustomization command to list attributes that you can customize for a
virtual appliance when you run the captureva, deployva, or importva commands.
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. You must specify an action, then the action that you specify determines
which other options you must or can specify. After you determine the attributes

that you can customize for a virtual appliance, you can specify those attributes in
the -A option of the captureva, deployva, or importva command.
The lscustomization command produces output in the format of the following

example:
cpushare
Value: 1.0
Min: 0.1
Max: 0.0
Increment: 0.1
Description: Number of virtual processors
memsize
Value: 1024
Increment: 1
IncrementType: LINEAR
Description: Memory (MB)
In this example, cpushare and memsize are the names of the customizable
attributes. The Value property indicates the default value of each attribute. The
other properties then provide information about how you can customize the
attribute. Here, cpushare has a default value of 1.0. This means that, if you do not
provide a customized value, the virtual appliance will expect a virtual server with
exactly one virtual processor (and zero fractional virtual processors). However, if
you choose to customize this attribute, you must specify 0.1 or a value that is
higher than 0.1 by an increment of 0.1. Therefore, you can specify -A
"cpushare=2.3" when using the deployva command, but you cannot specify -A
"cpushare=0.009" (because it does not meet the minimum value criteria) or -A
"cpushare=4" (because it is a simple integer, which is not the correct form).
FlagsOptions
-a | --action {capture | deploy_existing | deploy_new | import}
capture
This action displays the virtual appliance attributes that you can
specify when using the captureva command.
deploy_existing
specify when using the deployva -a deploy_existing command.
deploy_new
specify when using the deployva -a deploy_new command.
import
specify when using the importva command.
format) or .ova file (an OVF package in TAR format). If the name or URI
contains spaces, enclose it in quotation marks. The following name and URI
formats are supported:

only)
only)
-h | -?
ignored.
--help
Tips:
ignored.
v de: German
v en: English
v es: Spanish
v fr: French
v it: Italian
v ja: Japanese
v ko: Korean
Tips:
0x7b).
Tip: To list all repository names and OIDs, use the lsrepos command with the
-o option.

-s | --server {server | host}
Specifies the unique ID (OID) of the targeted server or host object.
0x7b).
Tips:
v Use either the lscapsrv or lsdeploytargets command, depending on the
specified -a option value, to list servers or hosts.
v If you will run captureva to capture an existing AIX mksysb image file, do
not specify the -s option on lscustomization.
v If the capture action is specified, then specify a server, but only if you intend
to run captureva to capture an existing virtual server.
v If the deploy_existing action is specified, then you must specify an existing
virtual server.
v If the deploy_new action is specified, then you must specify a virtualization
host system.
-v | --verbose
0x7b).
Exit status

v 72: Creation of a list of customizable attributes failed.
Examples
1. 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.
smcli lscustomization -v -a capture -r 722
Note: Use this format before running smcli captureva -r repository -n name
-F fileLocation.

2. Display customizable attributes for a virtual appliance that you can capture
from a virtual server and store in a repository
appliance that you intend to capture from existing virtual server 456 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.
3. 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.
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. 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.
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.
5. Display customizable attributes for a virtual appliance that you can import
from the Internet and store in a repository
appliance that you intend to import from the Internet and store in repository
722.
smcli lscustomization -v -a import -F http://www.acmeimages.com/aix/aix61.ova
-r 722
Note: Use this format before running smcli importva -F fileLocation -r

repository.
Related tasks
lsdeploytargets command
Use the lsdeploytargets command to list the target servers or hosts on which you
can deploy a virtual appliance workload.
SyntaxSynopsis
smcli lsdeploytargets {-h | -? | --help} [-L language]
smcli lsdeploytargets [-L language] [-v] [-l] [-o] [-d delimiter_symbol] -a

{deploy_existing | deploy_new} [-V virtualAppliance]

Description
The lsdeploytargets command displays a list of existing servers or hosts to which

you can deploy virtual appliances.
FlagsOptions
-a | --action {deploy_existing | deploy_new}
deploy_existing
This action indicates that you want a list of existing virtual servers that
can accommodate the specified virtual appliance.
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.
ignored.

-h | -?
ignored.
--help
Tips:
ignored.
-l | --long
v de: German
v en: English
v es: Spanish
v fr: French
v it: Italian
v ja: Japanese

v ko: Korean
Tips:
-o | --oid
-v | --verbose
0x7b).
Exit status

v 71: Creation of a list of deployable targets failed.
Examples
1. 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.
smcli lsdeploytargets -v -a deploy_existing -V 322
2. Display hosts on which you can create new virtual servers and deploy a
virtual appliance

This example illustrates how to display a list of hosts on which you can create
new virtual servers and deploy virtual appliance 322.
smcli lsdeploytargets -v -a deploy_new -V 322
Related tasks
lsrepos command
Use the lsrepos command to list repositories.
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. The list of
repositories that is returned depends on the filtering parameters that are passed on
the command. If you specify an action, then the action that you specify determines
which other options you must or can specify:
v To display a list of all repositories, do not specify an action.
v To display a list of repositories that are available to store captured workloads for
a virtual server, pass the capture action and the OID of the virtual server object.
v To display a list of repositories that are available for importing an OVF file,
specify the import action and the OVF file name.
FlagsOptions
-a | --action {capture | import}
capture
This action lists repositories that can store the virtual appliance created
by capturing the workload on the specified server.
import
This action lists the repositories to which you can import the specified
OVF file.
ignored.

format) or .ova file (an OVF package in TAR format). If the name or URI
contains spaces, enclose it in quotation marks. The following name and URI
formats are supported:
only)
only)
-h | -?
ignored.
--help
Tips:
ignored.
-l | --long
v de: German
v en: English
v es: Spanish
v fr: French
v it: Italian
v ja: Japanese
v ko: Korean
Tips:

-o | --oid
-s | --server server
Specifies the unique ID (OID) of the targeted server object.
0x7b).
Tip: Use the lscapsrv command with the -o option to list the name and OID of
all servers that you can capture.
-v | --verbose
Exit status

v 66: Creation of a list of importable repositories failed.
v 68: Creation of a list of repositories that can be captured failed.
Examples
1. Display all repositories
This example illustrates how to display a list of all repositories.
smcli lsrepos -v
2. 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.
smcli lsrepos -v -a capture -s 123
3. 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.ova..
smcli lsrepos -v -a import -F "/tmp/joe.ova"

Related tasks
lsva command
Use the lsva command to list virtual appliances.
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 results that are
returned depend on the options that are specified.
FlagsOptions
ignored.

-h | -?
ignored.
--help
Tips:
ignored.
-l | --long
v de: German
v en: English
v es: Spanish
v fr: French
v it: Italian

v ja: Japanese
v ko: Korean
Tips:
-o | --oid
-v | --verbose
Exit status

Examples
1. Display all virtual appliances
This example illustrates how to display a list of all virtual appliances.
smcli lsva -v
2. Display all virtual appliances and object IDs
This example illustrates how to display a list of all virtual appliances and their
object IDs.
smcli lsva -v -o
Related tasks
OVF specifications for IBM Systems Director VMControl

With IBM Systems Director VMControl, you can import a virtual appliance
package that conforms to the Distributed Management Task Force (DMTF) Open
Virtualization Format (OVF). This virtual appliance package or OVF package is a

representation of a virtual server that contains a configured, tested operating
system and middleware and software applications, along with the metadata that
describes the virtual server. 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.
Related concepts
Related tasks
OVF package requirements

An OVF package is a representation of a virtual server that contains a configured,
tested operating system and middleware and software applications, 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, typically with a .ova extension.
OVF packages to be imported must satisfy the following requirements:

v If the OVF package is in TAR file format, the order of files in a TAR package
must conform to what is specified in the DMTF Open Virtualization Format
Specification.
This specification is available from the DMTF Web site at: http://
www.dmtf.org/standards/published_documents/DSP0243_1.0.0.pdf
v OVF packages must contain a single virtual system, not a virtual system
collection.
v OVF packages that define configurations by using the DeploymentOptionSection
element and the ovf:configuration attribute on any Item elements can be
imported, but only the default configuration is processed when the virtual
appliance is deployed. Captured OVF packages will not specify a
DeploymentOptionSection nor ovf:configuration attributes on any Item
elements.
v OVF packages that use localization can be imported, but the localized strings
will be ignored and only the strings in the default language will be used when
the virtual appliance is deployed. The OVF packages captured will not specify
localized strings.
v OVF packages that use string bundle files can be imported, but the string bundle
files are ignored when the virtual appliance is deployed. The OVF packages
captured will not specify string bundle files.
v OVF packages that use file chunking cannot be imported.
v OVF packages that contain networks must have a network description.
v OVF packages must contain a deployable image.
v OVF packages with no image files cannot be imported.
v OVF packages must contain a virtual hardware section.
There are several extension elements to the Item (RASD) element and to other
sections of the OVF descriptor file. For information on these extension elements,
see “XML schema definition (XSD) files for OVF descriptor” on page 115.

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, but is limited to always use the
″normal″ value of the range. Captured OVF packages do not specify ranges.
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. This section is required for importing an
OVF package and is created on capture.
– LinuxLVMSection
This is a z/VM extension section in the OVF descriptor file that describes the
configuration of Linux Logical Volume Manager (LVM), if used. This section
is required for importing an OVF package and is created on capture, if LVM
is used by the LinuxFileSystemSection.
– The VirtualSystemType element within the System element of the
VirtualHardwareSection must have the value IBM:zVM:LINUX.
– The ovf:id attribute of the OperatingSystemSection must have the value 36 to
indicate LINUX.
– The ovf:format attribute of any Disk elements in the DiskSection that
reference image files must have the value http://www.ibm.com/xmlns/ovf/
diskformat/s390.linuxfile.exustar.gz and the referenced image files must
use the EXUSTAR archive format to store the Linux files.
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. For
information on these extension elements, see “XML schema definition (XSD) files
for OVF descriptor” on page 115.
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.
– The compression type of the file must either not be set or be set to identity,
which means no compression.
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.

Note: The only disk format that is supported by NIM is http://www.ibm.com/
xmlns/ovf/diskformat/power.aix.mksysb.
v There is only one system and it has one and only one mksysb image.
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. The HostResource element must
specify a disk that has the mksysb format. The disk specified must reference a file
in the File element of the References section.
There are several extension elements to the Item (RASD) element and to other
sections of the OVF descriptor file. For information on these extension elements,
see “XML schema definition (XSD) files for OVF descriptor.”
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.
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, which is a platform independent and open packaging and
distribution format for virtual appliances.
For more information on the OVF standard, see the Open Virtualization Format
Specification available from the DMTF Web site at: http://www.dmtf.org/
standards/published_documents/DSP0243_1.0.0.pdf
v IBM Systems Director VMControl requirements and restrictions for importing
OVF packages
For information on these requirements and restrictions, see “OVF package
requirements” on page 113.
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. To use these files, save the
XSD files to a local directory. Then use an XML editor to create an OVF
descriptor file or modify the contents of one of the sample OVF descriptor files.
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.
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. You can
download the OVF Editor from the following Web site: http://
www.alphaworks.ibm.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.
This topic contains these XSD files that you can use to create or modify an OVF
descriptor file.
These files are available to download from the IBM Systems Director VMControl
information center at the following Web site:

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, to Power Systems, and
to z/VM. Save the XSD files that you need to create or modify an OVF descriptor
file for your environment.
Description XSD file

Extensions to the OVF descriptor that are ibm-vim2_2.1.0.xsd
common across the IBM Systems Director
VMControl platforms, except for any
extensions to ovf:System (VSSD) and
ovf:Item (RASD) elements.
Extensions to the ovf:Item (RASD) element ibm-vim2-rasd_2.1.0.xsd
of the OVF Descriptor that are common
across the IBM Systems Director VMControl
platforms.
Extensions to ovf:Item (RASD) that are ibm-vim2-phyp3-rasd_2.1.0.xsd
specific to POWER Hypervisor™.
Extensions to the OVF Descriptor that are ibm-vim2-zvm5_2.1.0.xsd
specific to the z/VM platform, except for
any extensions to the ovf:System (VSSD)
and ovf:Item (RASD) elements.
Extensions to the ovf:Item (RASD) element ibm-vim2-zvm5-rasd_2.1.0.xsd
of the OVF Descriptor that are specific to the
z/VM platform.
Extensions to the ovf:System (VSSD) ibm-vim2-zvm5-vssd_2.1.0.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. You can copy and
modify this file to create your own OVF descriptor file.
<?xml version="1.0" encoding="UTF-8"?>
<ovf:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1"
xmlns="http://schemas.dmtf.org/ovf/envelope/1"
xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData"
xmlns:vim="http://www.ibm.com/xmlns/ovf/extension/vim/2"
xmlns:vimphyp="http://www.ibm.com/xmlns/ovf/extension/vim/2/phyp/3"
xmlns:vimphyprasd="http://www.ibm.com/xmlns/ovf/extension/vim/2/phyp/3/rasd"
xmlns:vimrasd="http://www.ibm.com/xmlns/ovf/extension/vim/2/rasd"
xmlns:vssd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData"
xsi:schemaLocation="http://www.ibm.com/xmlns/ovf/extension/vim/2 ibm-vim2_2.1.0.xsd
http://schemas.dmtf.org/ovf/envelope/1 dsp8023_1.0.0.xsd
http://www.ibm.com/xmlns/ovf/extension/vim/2/phyp/3/rasd ibm-vim2-phyp3-rasd_2.1.0.xsd
http://www.ibm.com/xmlns/ovf/extension/vim/2/rasd ibm-vim2-rasd_2.1.0.xsd" xml:lang="en-US">
<ovf:References>
<ovf:File ovf:href="image1.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.ibm.com/xmlns/ovf/diskformat/power.aix.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>

</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.
Its presence indicates that the virtual system needs to be booted after deployment,
to run first-boot customization.</ovf:Info>
</ovf:InstallSection>
<ovf:VirtualHardwareSection
ovf:transport="http://www.ibm.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,
0.5 processing units.</rasd:ElementName>
<rasd:Limit>10</rasd:Limit>
<rasd:Reservation>10</rasd:Reservation>
<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.</rasd:ElementName>
<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>
</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.</rasd:ElementName>
</ovf:Item>
</ovf:VirtualHardwareSection>
<ovf:ProductSection ovf:class="com.ibm.ovf.vim.2">
<ovf:Info>This product section provides information about the entire package.</ovf:Info>
<ovf:Product>The name of the product.</ovf:Product>
<ovf:Vendor>IBM</ovf:Vendor>
<ovf:Version>1.0</ovf:Version>
<ovf:FullVersion>1.0</ovf:FullVersion>
<ovf:Category>TCP/IP Network Settings</ovf:Category>
<ovf:Property ovf:key="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.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:Property ovf:key="networkport.6.ip" ovf:type="string" ovf:userConfigurable="true">
<ovf:Label>Static IP address for the network adapter
on "Virtual Network 1".</ovf:Label>
<ovf:Description>Static IP address for the network adapter
on "Virtual Network 1".</ovf:Description>
</ovf:Property>
<ovf:Property ovf:key="networkport.6.hostname" ovf:type="string"
<ovf:Label>Short hostname for the IP address of the network adapter
<ovf:Description>Short hostname for the IP address of the network adapter
</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
<ovf:Description>Use DHCP for the network adapter
</ovf:Property>
<ovf:Property ovf:key="networkport.6.gateway" ovf:type="string"
<ovf:Label>Static default gateway for the network adapter
<ovf:Description>Static default gateway for the network adapter
</ovf:Property>
<ovf:Property ovf:key="networkport.6.netmask" ovf:type="string"
<ovf:Label>Static network mask for the network adapter
<ovf:Description>Static network mask for the network adapter
</ovf:Property>
<ovf:Property ovf:key="networkport.6.dns1.ip" ovf:type="string"
<ovf:Label>IP address of primary DNS server for the network adapter
<ovf:Description>IP address of primary DNS server for the network adapter
</ovf:Property>
<ovf:Property ovf:key="networkport.6.dns2.ip" ovf:type="string"
<ovf:Label>IP address of secondary DNS server for the network adapter
<ovf:Description>IP address of secondary DNS server for the network adapter
</ovf:Property>
<ovf:Property ovf:key="networkport.6.domainname" ovf:type="string"
<ovf:Label>DNS domain name for the IP address of the network adapter
<ovf:Description>DNS domain name for the IP address of the network adapter
</ovf:Property>
<vim:Description>Description of the product.</vim:Description>
</ovf:ProductSection>
<ovf:ProductSection ovf:class="com.ibm.ovf.vim.2.nim.6" ovf:instance="1">
<ovf:Info>NIM-specific settings</ovf:Info>
<ovf:Product>AIX</ovf:Product>
<ovf:Vendor>IBM</ovf:Vendor>
<ovf:Version>1.0</ovf:Version>
<ovf:FullVersion>1.0</ovf:FullVersion>
<ovf:Category>NIM-specific settings</ovf:Category>
<ovf:Property ovf:key="nim.Resource" ovf:type="string"
<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, or Resource
of class "resources" can be specified, except: mksysb, spot, lpp_source,
ovf_vm, master, lpp_source</ovf:Description>
</ovf:Property>
<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.ibm.ovf.vim.2" vim:instance=""

vim:key="networkport.6.ip"/>
<vim:NetworkBootIpAddress vim:class="com.ibm.ovf.vim.2" vim:instance=""
vim:key="networkport.6.ip"/>
</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. You can copy and modify this file to create your
own OVF descriptor file.
<?xml version="1.0"?>
<ovf:Envelope xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:vimzvm="http://www.ibm.com/xmlns/ovf/extension/vim/2/zvm/5"
xmlns:vimzvmvssd="http://www.ibm.com/xmlns/ovf/extension/vim/2/zvm/5/vssd"
xmlns:vimzvmrasd="http://www.ibm.com/xmlns/ovf/extension/vim/2/zvm/5/rasd"
xsi:schemaLocation="http://www.ibm.com/xmlns/ovf/extension/vim/2/zvm/5/vssd ibm-vim2-zvm5-vssd_2.1.0.xsd
http://www.ibm.com/xmlns/ovf/extension/vim/2/zvm/5/rasd ibm-vim2-zvm5-rasd_2.1.0.xsd
http://www.ibm.com/xmlns/ovf/extension/vim/2 ibm-vim2_2.1.0.xsd
http://www.ibm.com/xmlns/ovf/extension/vim/2/rasd ibm-vim2-rasd_2.1.0.xsd
http://www.ibm.com/xmlns/ovf/extension/vim/2/zvm/5 ibm-vim2-zvm5_2.1.0.xsd"
xml:lang="en-us">
<ovf:References>

<ovf:File ovf:id="EXAMPLE2:/boot"
ovf:href="EXAMPLE2_boot.star.gz"
ovf:compression="gzip"/>
<ovf:File ovf:id="EXAMPLE2:/opt"
ovf:href="EXAMPLE2_opt.star.gz"
<ovf:File ovf:id="EXAMPLE2:/"
ovf:href="EXAMPLE2.star.gz"
</ovf:References>
<ovf:DiskSection>

<ovf:Info>Disk-related information for the Linux file systems included
within this package.</ovf:Info>
<ovf:Disk ovf:diskId="EXAMPLE2:/boot"
ovf:capacity="104841216"
ovf:capacityAllocationUnits="byte"
ovf:fileRef="EXAMPLE2:/boot"
ovf:format="http://www.ibm.com/xmlns/ovf/diskformat/s390.linuxfile.exustar.gz"/>
<ovf:Disk ovf:diskId="EXAMPLE2:/opt"
ovf:fileRef="EXAMPLE2:/opt"
<ovf:Disk ovf:diskId="EXAMPLE2:/"
ovf:fileRef="EXAMPLE2:/"
<ovf:Disk ovf:diskId="EXAMPLE2:swap"
ovf:capacityAllocationUnits="byte"/>
</ovf:DiskSection>

<ovf:Info>The networks to which virtual network ports connect when deploying this package.</ovf:Info>
<ovf:Network ovf:name="network1">
<ovf:Description>

A network to which the virtual system in the package is to be connected (default description).
</ovf:Description>
</ovf:Network>
<ovf:VirtualSystem ovf:id="EXAMPLE2">

<ovf:Info>A virtual system to be created when deploying this package.</ovf:Info>
<ovf:Name>EXAMPLE2</ovf:Name>

<ovf:Info>The virtual hardware requirements of the target virtual system.</ovf:Info>
<ovf:System>

<vssd:ElementName>z/VM system: EXAMPLE2</vssd:ElementName>

<vssd:InstanceID>system-EXAMPLE2</vssd:InstanceID>
<vssd:VirtualSystemType>IBM:zVM:LINUX</vssd:VirtualSystemType>

<vimzvmvssd:PrivilegeClasses>BEG</vimzvmvssd:PrivilegeClasses>

<vimzvmvssd:MaxMemory>1048576</vimzvmvssd:MaxMemory>
<vimzvmvssd:MaxMemoryUnits>byte*2^10</vimzvmvssd:MaxMemoryUnits>

<vimzvmvssd:IPLSource>0100</vimzvmvssd:IPLSource>

<vimzvmvssd:Options>LNKNOPAS LANG AMENG</vimzvmvssd:Options>
</ovf:System>

<ovf:Item>
<rasd:ElementName>Share for CPU type CP</rasd:ElementName>
<rasd:InstanceID>cpushare-cp</rasd:InstanceID>
<rasd:ResourceSubType>CP</rasd:ResourceSubType>
<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>
</ovf:Item>
<ovf:Item>
<rasd:ElementName>Share for CPU type ICF</rasd:ElementName>
<rasd:InstanceID>cpushare-icf</rasd:InstanceID>
<rasd:ResourceSubType>ICF</rasd:ResourceSubType>
</ovf:Item>
<ovf:Item>
<rasd:ElementName>Share for CPU type ZAAP</rasd:ElementName>
<rasd:InstanceID>cpushare-zaap</rasd:InstanceID>
<rasd:ResourceSubType>ZAAP</rasd:ResourceSubType>

</ovf:Item>
<ovf:Item>
<rasd:ElementName>Share for CPU type ZIIP</rasd:ElementName>
<rasd:InstanceID>cpushare-ziip</rasd:InstanceID>
<rasd:ResourceSubType>ZIIP</rasd:ResourceSubType>
</ovf:Item>

<ovf:Item>
<rasd:Address>00</rasd:Address>
<rasd:ElementName>CPU 00</rasd:ElementName>
<rasd:InstanceID>cpu-00</rasd:InstanceID>
</ovf:Item>
<ovf:Item>
</ovf:Item>

<ovf:Item>
<rasd:ElementName>Memory</rasd:ElementName>
<rasd:InstanceID>memory</rasd:InstanceID>
<rasd:AllocationUnits>byte*2^10</rasd:AllocationUnits>
</ovf:Item>

<ovf:Item>
<rasd:Connection>network1</rasd:Connection>
<rasd:ElementName>Network Interface eth0</rasd:ElementName>
<rasd:InstanceID>network-interface-eth0</rasd:InstanceID>

<vimzvmrasd:IOProtocol>ibm:qdio</vimzvmrasd:IOProtocol>

<vimzvmrasd:Layer>3</vimzvmrasd:Layer>

<vimzvm:NetworkPortConfigProposal vimzvm:nicdev="eth0"/>
</ovf:Item>

<ovf:Item>
<rasd:ElementName>Disk: 0100</rasd:ElementName>
<rasd:InstanceID>disk-0100</rasd:InstanceID>

<rasd:ResourceSubType>ibm:z:3390</rasd:ResourceSubType>


<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>
</ovf:Item>
<ovf:Item>
</ovf:Item>
<ovf:Item>
</ovf:Item>
<ovf:Item>
</ovf:Item>
<ovf:Item>
<vimzvmrasd:DiskTechnology>vdisk</vimzvmrasd:DiskTechnology>
<vimzvmrasd:AccessMode>MR</vimzvmrasd:AccessMode>
</ovf:Item>
<ovf:Item>

</ovf:Item>

<ovf:ProductSection>
<ovf:Info>This section describes the OVF package itself.</ovf:Info>
<ovf:Product ovf:msgid="translateID22">ExampleWithLVM</ovf:Product>
<vim:Description ovf:msgid="translateID23">Example system with LVM volume groups.</vim:Description>
<ovf:ProductSection ovf:class="com.ibm.ovf.vim.2.zvm.5">
<ovf:Info>This section describes the customizable properties of this virtual system.</ovf:Info>
<ovf:Product>Red Hat Enterprise Linux Server release 5.3 on z/VM.</ovf:Product>
<ovf:Category>General Settings</ovf:Category>
<ovf:Property ovf:key="timezone.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:Property ovf:key="networkport.eth0.usedhcp"
ovf:type="boolean"
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.eth0.ip"
ovf:type="string"
<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.eth0.gateway"
ovf:type="string"
<ovf:Label>Default gateway for eth0</ovf:Label>
<ovf:Description>Default gateway for eth0, if not using DHCP (IP V4 or V6 format)</ovf:Description>
</ovf:Property>
<ovf:Property ovf:key="networkport.eth0.netmask"
ovf:type="string"
<ovf:Label>Network mask for eth0</ovf:Label>
<ovf:Description>Network mask for eth0, if not using DHCP (IP V4 or V6 format)</ovf:Description>
</ovf:Property>
<ovf:Property ovf:key="networkport.eth0.dns1.ip"
ovf:type="string"
<ovf:Label>IP address of primary DNS server for eth0</ovf:Label>
<ovf:Description>
IP address of primary DNS server for eth0, if not using DHCP (IP V4 or V6 format)
</ovf:Description>
</ovf:Property>
ovf:type="string"
<ovf:Label>IP address of secondary DNS server for eth0</ovf:Label>
<ovf:Description>
IP address of secondary DNS server for eth0, if not using DHCP (IP V4 or V6 format)
</ovf:Description>
</ovf:Property>
<ovf:Property ovf:key="networkport.eth0.registerindns"
ovf:type="boolean"
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.eth0.hostname"
ovf:type="string"
<ovf:Label>Hostname for eth0</ovf:Label>
<ovf:Description>Hostname for eth0</ovf:Description>
</ovf:Property>
<ovf:Property ovf:key="networkport.eth0.domainname"
ovf:type="string"
<ovf:Label>Domain name for eth0</ovf:Label>
<ovf:Description>Domain name for eth0</ovf:Description>
</ovf:Property>
<ovf:Property ovf:key="system.hostname"
ovf:type="string"
<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.domainname"
ovf:type="string"
<ovf:Label>DNS domain name for the system</ovf:Label>
<ovf:Description>DNS domain name for the system</ovf:Description>
</ovf:Property>
<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.6.18-128.el5">
<ovf:Info>Information about the operating system in the virtual system.</ovf:Info>
<ovf:Description>Red Hat Enterprise Linux Server release 5.3</ovf:Description>
<ovf:Info>
Indicates that the system needs to be booted after deployment to run first-boot customization.
</ovf:Info>
<vimzvm:LinuxFileSystemSection ovf:required="true">

<ovf:Info>
Defines how the image files (containing Linux file system content)
are deployed to Linux mount points.
Optionally, provides a configuration proposal for each file system.
</ovf:Info>
<vimzvm:FileSystem vimzvm:diskRef="EXAMPLE2:/boot"
vimzvm:mountPoint="/boot">
<vimzvm:ConfigProposal>

<vimzvm:LinuxMount vimzvm:devSpec="LABEL=/boot1"
vimzvm:mountOptions="defaults"
vimzvm:dump="1"
vimzvm:fsckPassNo="2"/>
<vimzvm:LinuxFileSystem vimzvm:type="ext3"
vimzvm:label="/boot1"/>

<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:LinuxMount vimzvm:devSpec="/dev/VG0/LV4opt"
vimzvm:dump="1"

vimzvm:label=""/>

<vimzvm:LinuxLogicalVolume vimzvm:lvName="LV4opt"
vimzvm:vgName="VG0"
vimzvm:lvSize="4227858432"
vimzvm:lvSizeUnits="byte"/>
<vimzvm:FileSystem vimzvm:diskRef="EXAMPLE2:/"
vimzvm:mountPoint="/">
<vimzvm:LinuxMount vimzvm:devSpec="/dev/VG0/LV4slash"
vimzvm:dump="1"
vimzvm:label=""/>
<vimzvm:LinuxLogicalVolume vimzvm:lvName="LV4slash"
vimzvm:vgName="VG0"
<vimzvm:FileSystem vimzvm:diskRef="EXAMPLE2:swap"
vimzvm:mountPoint="swap">
<vimzvm:LinuxMount vimzvm:devSpec="/dev/VG0/LV4swap"
vimzvm:dump="0"
<vimzvm:LinuxFileSystem vimzvm:type="swap"
vimzvm:label=""/>
<vimzvm:LinuxLogicalVolume vimzvm:lvName="LV4swap"
vimzvm:vgName="VG0"
</vimzvm:LinuxFileSystemSection>
<vimzvm:LinuxLVMSection ovf:required="false">

<ovf:Info>
Defines a configuration proposal for the Linux LVM2. The volume groups
defined here are referenced by the Linux file system configuration proposals in the
LinuxFileSystemSection. The physical volumes defined here reference logical disks,
or Item elements of ResourceType=31 (LogicalDisk).
</ovf:Info>
<vimzvm:VolumeGroup vimzvm:name="VG0"
vimzvm:vgOptions="wz--n-">

<vimzvm:PhysicalVolume vimzvm:devNode="/dev/disk/by-path/ccw-0.0.0100-part2"
vimzvm:pvOptions="a-">
</vimzvm:PhysicalVolume>

</vimzvm:VolumeGroup>
</vimzvm:LinuxLVMSection>
</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. You can copy
and modify this file to create your own OVF descriptor file.
<?xml version="1.0"?>
<ovf:Envelope xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:vimzvm="http://www.ibm.com/xmlns/ovf/extension/vim/2/zvm/5"
xmlns:vimzvmvssd="http://www.ibm.com/xmlns/ovf/extension/vim/2/zvm/5/vssd"
xmlns:vimzvmrasd="http://www.ibm.com/xmlns/ovf/extension/vim/2/zvm/5/rasd"
xsi:schemaLocation="http://www.ibm.com/xmlns/ovf/extension/vim/2/zvm/5/vssd ibm-vim2-zvm5-vssd_2.1.0.xsd
http://www.ibm.com/xmlns/ovf/extension/vim/2/zvm/5/rasd ibm-vim2-zvm5-rasd_2.1.0.xsd
http://www.ibm.com/xmlns/ovf/extension/vim/2 ibm-vim2_2.1.0.xsd
http://www.ibm.com/xmlns/ovf/extension/vim/2/rasd ibm-vim2-rasd_2.1.0.xsd
http://www.ibm.com/xmlns/ovf/extension/vim/2/zvm/5 ibm-vim2-zvm5_2.1.0.xsd"
xml:lang="en-us">
<ovf:References>

<ovf:File ovf:id="EXAMPLE1:/"
ovf:href="EXAMPLE1.star.gz"
</ovf:References>
<ovf:DiskSection>

<ovf:Info>Disk-related information for the Linux file systems included within this package.</ovf:Info>
<ovf:Disk ovf:diskId="EXAMPLE1:/"
ovf:fileRef="EXAMPLE1:/"
<ovf:Disk ovf:diskId="EXAMPLE1:swap1"
<ovf:Disk ovf:diskId="EXAMPLE1:swap2"
</ovf:DiskSection>

<ovf:Info>The networks to which virtual network ports connect when deploying this package.</ovf:Info>

<ovf:Description>
</ovf:Description>
</ovf:Network>
<ovf:Description>
</ovf:Description>
</ovf:Network>
<ovf:VirtualSystem ovf:id="EXAMPLE1">

<ovf:Info>A virtual system to be created when deploying this package.</ovf:Info>
<ovf:Name>EXAMPLE1</ovf:Name>

<ovf:Info>The virtual hardware requirements of the target virtual system.</ovf:Info>
<ovf:System>

<vssd:ElementName>z/VM system: EXAMPLE1</vssd:ElementName>

<vssd:InstanceID>system-EXAMPLE1</vssd:InstanceID>
<vssd:VirtualSystemType>IBM:zVM:LINUX</vssd:VirtualSystemType>

<vimzvmvssd:PrivilegeClasses>G</vimzvmvssd:PrivilegeClasses>

<vimzvmvssd:MaxMemory>393216</vimzvmvssd:MaxMemory>
<vimzvmvssd:MaxMemoryUnits>byte*2^10</vimzvmvssd:MaxMemoryUnits>

<vimzvmvssd:IPLSource>0100</vimzvmvssd:IPLSource>

<vimzvmvssd:Options>APPLMON</vimzvmvssd:Options>
</ovf:System>

<ovf:Item>
<rasd:ElementName>Share for CPU type CP</rasd:ElementName>
<rasd:InstanceID>cpushare-cp</rasd:InstanceID>
</ovf:Item>
<ovf:Item>
<rasd:ElementName>Share for CPU type IFL</rasd:ElementName>
<rasd:InstanceID>cpushare-ifl</rasd:InstanceID>
<rasd:ResourceSubType>IFL</rasd:ResourceSubType>
</ovf:Item>
<ovf:Item>
<rasd:ElementName>Share for CPU type ICF</rasd:ElementName>
<rasd:InstanceID>cpushare-icf</rasd:InstanceID>
<rasd:ResourceSubType>ICF</rasd:ResourceSubType>

</ovf:Item>
<ovf:Item>
<rasd:ElementName>Share for CPU type ZAAP</rasd:ElementName>
<rasd:InstanceID>cpushare-zaap</rasd:InstanceID>
<rasd:ResourceSubType>ZAAP</rasd:ResourceSubType>
</ovf:Item>
<ovf:Item>
<rasd:ElementName>Share for CPU type ZIIP</rasd:ElementName>
<rasd:InstanceID>cpushare-ziip</rasd:InstanceID>
<rasd:ResourceSubType>ZIIP</rasd:ResourceSubType>
</ovf:Item>

<ovf:Item>
</ovf:Item>
<ovf:Item>
</ovf:Item>
<ovf:Item>
</ovf:Item>

<ovf:Item>
<rasd:ElementName>Memory</rasd:ElementName>
<rasd:InstanceID>memory</rasd:InstanceID>
<rasd:AllocationUnits>byte*2^10</rasd:AllocationUnits>
</ovf:Item>

<ovf:Item>





</ovf:Item>
<ovf:Item>
</ovf:Item>

<ovf:Item>






</ovf:Item>
<ovf:Item>
</ovf:Item>
<ovf:Item>
</ovf:Item>

<ovf:ProductSection>
<ovf:Info>This section describes the OVF package itself.</ovf:Info>
<ovf:Product ovf:msgid="translateID22">ExampleWithoutLVM</ovf:Product>
<vim:Description ovf:msgid="translateID23">An example system with no LVM volume groups.</vim:Description>
<ovf:ProductSection ovf:class="com.ibm.ovf.vim.2.zvm.5">
<ovf:Info>This section describes the customizable properties of this virtual system.</ovf:Info>
<ovf:Product>SUSE Linux Enterprise Server 11 on z/VM.</ovf:Product>
<ovf:Category>General Settings</ovf:Category>
<ovf:Property ovf:key="timezone.offset"
ovf:type="uint16"
ovf:value="-0400">
<ovf:Label>Timezone Offset</ovf:Label>
<ovf:Description>Timezone Offset</ovf:Description>
</ovf:Property>
ovf:type="boolean"
ovf:value="false">
</ovf:Property>
ovf:type="string"
</ovf:Property>
ovf:type="string"
</ovf:Property>
ovf:type="string"
</ovf:Property>
ovf:type="string"
<ovf:Description>
</ovf:Description>
</ovf:Property>
ovf:type="string"
<ovf:Description>
</ovf:Description>
</ovf:Property>
ovf:type="boolean"
ovf:value="true">
</ovf:Property>
ovf:type="string"
</ovf:Property>
ovf:type="string"

</ovf:Property>
ovf:type="boolean"
ovf:value="false">
</ovf:Property>
ovf:type="string"
</ovf:Property>
ovf:type="string"
</ovf:Property>
ovf:type="string"
</ovf:Property>
ovf:type="string"
<ovf:Description>
</ovf:Description>
</ovf:Property>
ovf:type="string"
<ovf:Description>
</ovf:Description>
</ovf:Property>
ovf:type="boolean"
ovf:value="true">
</ovf:Property>
ovf:type="string"
</ovf:Property>
ovf:type="string"
</ovf:Property>
<ovf:Property ovf:key="system.hostname"
ovf:type="string"
<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.domainname"
ovf:type="string"
<ovf:Label>DNS domain name for the system</ovf:Label>
<ovf:Description>DNS domain name for the system</ovf:Description>
</ovf:Property>
<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.6.27.19-5-default">

<ovf:Info>Information about the operating system in the virtual system.</ovf:Info>
<ovf:Description>SUSE Linux Enterprise Server 11</ovf:Description>
<ovf:Info>
Indicates that the system needs to be booted after deployment to run first-boot customization.
</ovf:Info>
<vimzvm:LinuxFileSystemSection ovf:required="true">

<ovf:Info>
Defines how the image files (containing Linux file system content) are deployed
to Linux mount points.
</ovf:Info>
<vimzvm:FileSystem vimzvm:diskRef="EXAMPLE1:/"
vimzvm:mountPoint="/">

<vimzvm:LinuxMount vimzvm:devSpec="/dev/disk/by-path/ccw-0.0.0100-part1"
vimzvm:mountOptions="acl,user_xattr"
vimzvm:dump="1"
vimzvm:label=""/>

<vimzvm:FileSystem vimzvm:diskRef="EXAMPLE1:swap1"
vimzvm:dump="0"
vimzvm:label=""/>

<vimzvm:FileSystem vimzvm:diskRef="EXAMPLE1:swap2"
vimzvm:dump="0"
vimzvm:label=""/>
</vimzvm:LinuxFileSystemSection>
<vimzvm:LinuxLVMSection ovf:required="false">

<ovf:Info>
Defines a configuration proposal for the Linux LVM2.
The volume groups defined here are referenced by the Linux file system configuration proposals
in the LinuxFileSystemSection.
The physical volumes defined here reference logical disks, i.e.,
Item elements of ResourceType=31 (LogicalDisk).

</ovf:Info>
</vimzvm:LinuxLVMSection>
</ovf:Envelope>
Processor settings
This topic provides information about using IBM Systems Director VMControl to
specify processor settings for z/VM virtual servers.
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, 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. With CPU affinity on, z/VM will dispatch a virtual server’s
virtual processors on real processors that match their types. If no matching real
processors exist, z/VM will simulate these processors, but dispatch them on real
processors of type CP; this condition is called ″CPU affinity suppressed.″ With
CPU affinity off, z/VM will dispatch virtual processors of types other than the
primary processor type on real processors, regardless of the existence of matching
real processors. The primary processor type of a z/VM system is IFL if all of its
real processors are of type IFL. Otherwise, the primary processor type is CP.
CPU affinity also affects the way in which the share of processor capacity is
determined. If CPU affinity is on, the minimum and maximum share of processor
capacity is determined separately for each real processor type that is dispatched to
the virtual server. If CPU affinity is off, these shares are determined at the level of
the virtual server and are then used for all processor types.
Share values
You can specify share values for a virtual server to control the amount of processor
cycles (i.e. processor capacity) the virtual server receives. Share values are specified
for all processor types together. Each such share value consists of a minimum share
and a maximum share.
Note that while share values control the processor capacity directly, they indirectly
also influence access to other types of system resources when they are constrained.
Specifically, 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.
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. When the total processor

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

only once. The characters must be letters or numbers in the range 1 - 6. The
privilege classes chosen for the virtual server should be a subset of the classes
defined for the z/VM system.
You can also specify options to define special characteristics for the virtual server.
Options are added to the OPTION control statement in the directory entry for the
virtual server.
The server password is restricted to a maximum of 8 characters and may contain

no blank spaces.
For more information, refer to Redefining Command Privilege Classes in z/VM:

CP Planning and Administration (SC24-6083).
IPL settings
When creating a new virtual server, you can specify IPL setting for starting the
virtual server. You can designate the virtual device number or the named saved
system as the IPL source.
You can also specify parameters (parms) and load parameters (loadparms). Read
the following information for details about parameters and load parameters. For
more information, refer to the IPL command in z/VM: CP Commands and Utilities
Reference (SC24-6081-07).
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, including trailing blanks.
If you are IPLing a device, the parameter string is inserted into the virtual
server registers, four bytes per register, starting with register 0. If the string
is less than 64 bytes, a single byte of binary zeros is inserted following the
string. If you omit the Parameters operand, the virtual server registers are
unchanged. If you are IPLing a named saved system that was defined with
the PARMREGS=m-n option on the DEFSYS command, the parameter
string is inserted into the virtual server registers m through n, which are
first initialized to binary zeros.
If you are IPLing a named saved system that was defined with the
PARMREGS=NONE option on the DEFSYS command, specifying the
PARM option results in an error message being issued and in the
command not being processed.
If you are IPLing a named saved system that was defined without the
PARMREGS=m-n option on the DEFSYS command, the parameter string is
inserted into the virtual server registers 0 through 15. The registers are not
first initialized to binary zeros. If you omit the Parameters operand, the
virtual server registers are unchanged.
Load parameters
Specifies a 1– to 8-character load parameter. If fewer than eight characters
are specified, the load parameter is left-justified and padded with blanks. If
LOADPARM is not specified, a load parameter of eight EBCDIC blanks is
formed.

The load parameter is converted to upper case and may include only the
upper case alphabetic characters (A-Z), digits 0-9, the period, and the
blank.
The load parameter may be retrieved by the guest operating system during
its IPL sequence. Its use is determined by the guest operating system, such
as indicating the nucleus to be loaded during the IPL sequence.

Chapter 3. Notices
This information was developed for products and services offered in the U.S.A.
IBM® may not offer the products, services, or features discussed in this document
in other countries. Consult your local IBM® representative for information on the
products and services currently available in your area. Any reference to an IBM®
product, program, or service is not intended to state or imply that only that IBM®
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM® intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM® may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM®
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation

Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, 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, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. 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.
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. 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.
IBM® may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

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, should contact:
IBM Corporation
MW9A/050
5600 Cottle Road
San Jose, CA 95193
U.S.A.
Such information may be available, subject to appropriate terms and conditions,

including in some cases, 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, IBM® International Program License Agreement, or any equivalent
agreement between us.
Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. 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. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM® has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM’s future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of
International Business Machines Corporation in the United States, other countries,
or both. These and other IBM trademarked terms are marked on their first
occurrence in this information with the appropriate symbol (® or ™), indicating US
registered or common law trademarks owned by IBM at the time this information
was published. Such trademarks may also be registered or common law

trademarks in other countries. A complete and current list of IBM trademarks is
available on the Web at www.ibm.com/legal/copytrade.shtml.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered
trademarks or trademarks of Adobe Systems Incorporated in the United States,
and/or other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United

States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of

others.
Chapter 3. Notices 139

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
deploy requirements 9
deployva 93
display
hosts 105
servers 99
target servers 105
virtual appliances 111
H
hardware requirements 5, 13
I
import
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


Printed in USA

IBM Systems Director VMControl

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

IBM Systems Director VMControl

Hochgeladen von

Copyright:

Verfügbare Formate

IBM Systems Director VMControl

IBM Systems Director VMControl

© Copyright IBM Corp. 2009, 2009 iii

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

Who should read this book

Conventions and terminology

Note: These notices provide important tips, guidance, or advice.

Attention: These notices indicate possible damage to programs, devices, or data.

Publications and related information

IBM Systems Director VMControl resources on the World Wide

© Copyright IBM Corp. 2009, 2009 1

How to send your comments

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

Overview of IBM Systems Director VMControl

IBM Systems Director VMControl in conjunction with IBM Systems Director

© Copyright IBM Corp. 2009, 2009 3

IBM Systems Director VMControl includes a no-charge (free) function and an

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

Planning for IBM Systems Director VMControl

Hardware and software requirements

Supported IBM® systems

For detailed information on the systems supported by IBM Systems Director

Supported operating systems

For specific versions of these operating systems supported by IBM Systems

Supported virtualization software

The following virtualization software is supported for IBM Systems Director

Chapter 2. IBM Systems Director VMControl V2.1 5

IBM Systems Director VMControl Import requirements

Requirements for import

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

Power Systems requirements for import

z/VM requirements for import

IBM Systems Director VMControl Capture requirements

You can capture these types of virtual servers:

Chapter 2. IBM Systems Director VMControl V2.1 7

Note: You cannot capture an image from a secure Web server.

Power Systems requirements for capture

z/VM requirements for capture

The following prerequisites must be met to capture a z/VM virtual server:

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

IBM Systems Director VMControl Deploy requirements

Power Systems server requirements for deploy

Chapter 2. IBM Systems Director VMControl V2.1 9

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

System z and z/VM requirements for deploy

For any z/VM deployment, the following prerequisites must be met:

Chapter 2. IBM Systems Director VMControl V2.1 11

v $ALLOC$ v BLDRACF v VSMPROXY v GSKADMIN v X25IPI

Installing and uninstalling IBM Systems Director VMControl

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

Supported IBM® systems

For detailed information on the systems supported by IBM Systems Director

Supported operating systems

For specific versions of these operating systems supported by IBM Systems

Supported virtualization software

The following virtualization software is supported for IBM Systems Director

Chapter 2. IBM Systems Director VMControl V2.1 13

Installing IBM Systems Director VMControl

Installing IBM Systems Director VMControl evaluation license

Tip: You can temporarily disable SELinux by entering the following

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

Operating system Download package

4. Copy the downloaded installation package to a local drive on each IBM

where <package_name> is the file name of the installation package.