Chapter 4. Functional comparison 111
p5570lp01(root)/> lsnim -l p5570lp03_mksysb
p5570lp03_mksysb:
class = resources
type = mksysb
Rstate = ready for use
prev_state = unavailable for use
location = /export/p5570lp03/p5570lp03.mksysb
version = 6
release = 1
mod = 6
oslevel_r = 6100-06
alloc_count = 0
server = master
creation_date = Wed Sep 28 18:16:45 2011
Virtual Appliance attributes as shown by lsva -l command:
p5570lp01(root)/> smcli lsva -l -q name=p5570lp03_mksysb_NIM
p5570lp03_mksysb_NIM
TrunkId:2
ClassName:com.ibm.usmi.datamodel.virtual.VirtualAppliance
RevisionVersion:1.1
Description:
ChangedDate:2011-09-28T18:17:53-04:00
TrunkName:p5570lp03_mksysb_NIM
DisplayName:p5570lp03_mksysb_NIM
CreatedDate:2011-09-28T18:17:52-04:00
SpecificationId:1
SpecificationVersion:1.1
OID:11499
Guid:3B8E6D1FEA3233AA9C100D44F3E1EE5A
ApplianceId:bf7ad9de-fdc5-45fb-9bd2-ad6a726f0e01
ObjectType:VirtualAppliance
Link between the mksysb NIM resource and the virtual appliance is based on a
file in VA-s vmcontrol directory:
p5570lp01(root)/export/nim/appliances/bf7ad9de-fdc5-45fb-9bd2-ad6a726f0e01> ls
-l *
-rw-r--r-- 1 root system 10037 Sep 28 18:17
bf7ad9de-fdc5-45fb-9bd2-ad6a726f0e01.ovf
vmcontrol/:
total 0
-rw-r--r-- 1 root system 0 Sep 28 18:17
mksysb.p5570lp03_mksysb
-rw-r--r-- 1 root system 0 Sep 28 18:17
user_defined_resource.p5570lp03_mksysb
112 IBM CSM to IBM Systems Director Transformation Guide
Check smcli lscustomization for attributes that can be changed and incorporated into
the created virtual appliance. One of these attributes is the disksize, which tells the size
of the virtual disk to be created in case of a new deployment. Example 4-10 shows the
attributes that can be changed when capturing a NIM resource. The image repository
object ID was 10826, which can be checked with the smcli lsrepos -o command.
Example 4-10 Customization attributes for the smcli captureva command
# smcli lscustomization -a capture -r 10826
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)
disksize
Value: 0
Increment: 1
IncrementType: LINEAR
Description: Disk Size (bytes)
VMControl can also capture images as operating system backup for a running operating
system that is discovered by Systems Director, as shown in Example 4-11. The Common
Agent does not have to be installed on the server, but the HMC has to be managed
(discovered and inventory collected) by Systems Director. This operation is managed by
the NIM master, which calls remote NIM commands on the virtual server’s operating
system.
If the virtual server is already a NIM client, then that definition will be used to manage it. If
not, then a new standalone machine is defined. In any case, after the capture the NIM
machine definition is removed.
Example 4-11 Capture a running AIX system
Capture command:
p5570lp01(root)/> smcli captureva -v -r 26950 -n p5570lp03_mksysb_cap -s 0x549b
Tue Jan 10 09:06:29 EST 2012 captureva Operation started.
Get capture customization data
Call capture function
Call capture command executed. Return code= 27,211
Tue Jan 10 09:15:54 EST 2012 captureva Operation took 564 seconds.
NIM operations started to create NIM mksysb resource:
p5570lp01(root)/export/nim/appliances> ps -ef|grep p5570lp03
Chapter 4. Functional comparison 113
root 3801240 7143634 0 09:06:47 - 0:00
/usr/lpp/bos.sysmgt/nim/methods/m_mkbosi -aforce=yes -t mksysb -a server=master
-a
location=/export/nim/appliances/04a61ed1-1bd0-482b-b69c-3423636a5946/image1.mks
ysb -a mk_image=yes -a source=p5570lp03 -a mksysb_flags=X e appliance-4_image-1
root 7143634 6029548 0 09:06:47 - 0:00 nim -Fo define -t mksysb -a
server=master -a
location=/export/nim/appliances/04a61ed1-1bd0-482b-b69c-3423636a5946/image1.mks
ysb -a mk_image=yes -a source=p5570lp03 -a mksysb_flags=X e appliance-4_image-1
Process tree on client system to capture:
p5570lp03(root)/> proctree 11141300
3342474 /usr/sbin/srcmstr
11337850 /usr/sbin/nimsh -s
3145822 /usr/sbin/nimsh -s
7012430 /bin/ksh /usr/lpp/bos.sysmgt/nim/methods/c_nimpush
/usr/lpp/bos.sysmgt/nim/meth
11141300 /bin/ksh /usr/lpp/bos.sysmgt/nim/methods/c_mkbosi
-aserver=p5570lp01 -alocation
5439522 /bin/ksh /usr/bin/savevg -i -f /tmp/11141300.mnt0/image1.mksysb -X
-e rootvg
4980752 backbyname -i -q -v -Z -p -U -f /tmp/11141300.mnt0/image1.mksysb
10223808 /usr/bin/cat /tmp/mksysb.5439522/.archive.list.5439522
11075626 /bin/ksh /usr/bin/savevg -i -f /tmp/11141300.mnt0/image1.mksysb -X
-e rootvg
10813538 /usr/bin/sleep 10
Virtual Appliance attributes as shown by lsva -l command:
p5570lp01(root)/> smcli lsva -l -q "name=p5570lp03_mksysb_cap"
p5570lp03_mksysb_cap
TrunkId:6
ClassName:com.ibm.usmi.datamodel.virtual.VirtualAppliance
RevisionVersion:1.1
Description:
ChangedDate:2012-01-10T09:15:52-05:00
TrunkName:p5570lp03_mksysb_cap
DisplayName:p5570lp03_mksysb_cap
CreatedDate:2012-01-10T09:15:52-05:00
SpecificationId:1
SpecificationVersion:1.1
OID:27211
Guid:3CD08D612A0B3CA8894497F8647BB034
ApplianceId:04a61ed1-1bd0-482b-b69c-3423636a5946
ObjectType:VirtualAppliance
NIM resource defined for mksysb:
p5570lp01(root)/> lsnim -l appliance-4_image-1
appliance-4_image-1:
class = resources
114 IBM CSM to IBM Systems Director Transformation Guide
type = mksysb
arch = power
Rstate = ready for use
prev_state = unavailable for use
location =
/export/nim/appliances/04a61ed1-1bd0-482b-b69c-3423636a5946/image1.mksysb
version = 6
release = 1
mod = 6
oslevel_r = 6100-06
alloc_count = 0
server = master
creation_date = Tue Jan 10 09:15:43 2012
source_image = p5570lp03
Link between the mksysb NIM resource and the virtual appliance is based on a
file in VA-s vmcontrol directory:
p5570lp01(root)/> ls -l
/export/nim/appliances/04a61ed1-1bd0-482b-b69c-3423636a5946
total 0
-rw------- 1 root system 13655 Jan 10 09:15
04a61ed1-1bd0-482b-b69c-3423636a5946.ovf
-rw-r--r-- 1 root system 3895910400 Jan 10 09:15 image1.mksysb
drwx--x--x 2 root system 256 Jan 10 09:15 vmcontrol/
p5570lp01(root)/> ls -l
/export/nim/appliances/04a61ed1-1bd0-482b-b69c-3423636a5946/vmcontrol
total 0
-rw------- 1 root system 0 Jan 10 09:15
mksysb.appliance-4_image-1
New NIM resources (LPP source, mksysb) are created and a set of files and directories
are also created as part of the appliance package in the /export/nim/appliances
directory.
Removing the node from the CSM cluster does not remove the NIM machine defined for it,
and even the CSM post-install customization script can remain allocated as a NIM
resource. This will prevent a successful capture operation, because the machine definition
cannot be removed from NIM (because VMControl removes it automatically) until there
are resources allocated to it.
Unexport all parent directories and remove them from
/etc/exports file which is under the
default virtual appliance directory:
/export/nim/appliances as the automatic NFS export
which is started by the NIM master will fail and the mksysb command on the node will not
be able to write into the new virtual appliance directory which has
rwxr-xr-x (755) access
rights.
? Deploy
Note: Capturing a running virtual server (LPAR) will create an mksysb that contains
only the rootvg and even if the rootvg spans multiple disks, the virtual appliance
definition will contain only one disk, albeit big enough to hold the whole rootvg.
Chapter 4. Functional comparison 115
Install the operating system using the appliance and the corresponding NIM resources.
VMControl will call all necessary NIM operations and create additional NIM resource
definitions to install the operating system.
Other DSM-provided operations are also started from the NIM server to control the
installation process—for example, key exchanges between the NIM server and HMC, and
MAC address collection.
In a CSM cluster beside others, the systemid, getadapters, csm2nimnodes, csmsetupnim
and netboot commands are doing what is automated in VMControl.
The customizable attributes used by VMControl to set up the deployed operating system
depend on the type of deployment. To check what attributes are available, use the smcli
lscustomization command. Many of the attributes are explained in 4.5.2, “Post-install
customization” on page 118.
There are two types of deployment operations:
–The smcli -a deploy_new command creates a new virtual server or LPAR definition,
so this will need to set the processor, memory, and virtual disk information also. In this
deployment mode the host or server system pool can be specified as a target with the
-s flag. The creation of the new LPAR is controlled by the following customization
methods:
• Some of the attributes can be specified at capture time, which will determine the
attributes used at deployment as shown in Example 4-12. These will be
incorporated into the virtual appliance definition. You can find them in the OVF file
created for the virtual appliance.
• Additional customization attributes can be specified with the -A flag of the smcli
deploy -a deploy_new command.
• A customization file can be specified with the -F flag.
For further explanation and examples, see IBM Systems Director VMControl
Implementation Guide on Power Systems, SG24-7829.
–The smcli -a deploy_existing command deploys an operating system onto an
existing virtual server or LPAR. In this case the LPAR basic virtualization attributes can
not be changed by the deployment operation. In this mode one or more virtual servers
can be specified with the -s flag.
When you run a deploy operation, VMControl provides the IP addresses the NIM server
should use for key exchanges. It is possible that the HMC’s IP address used for
communication with the managed systems is provided. The NIM server will not be able to
communicate with HMC using that address and gives back the error that is shown in
Example 4-12. In this case, HMC has the IP address 10.0.0.1 set for communication with
the service processors of the managed systems.
Example 4-12 Deployment error because of failing communication between NIM server and HMC
p5570lp01(root)/export/nim/cust> smcli deployva -a deploy_existing -V 11703 -s
10765 -F /export/nim/cust/cust_for_p5570lp02_>
DNZIMC032E Error occurred during deploy operation.
DNZIMN105E An error occurred starting the virtual server to prepare it for
deployment.
Note: We had to remove the network interface definition from Systems Director, which
belongs to the HMC.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.