AIX > Administrator > Virtualization

Configuring PowerVC With Shared Storage Pools

Deploy a New AIX Partition

First, we navigate our way to the Images panel in PowerVC. And select the image we want to deploy (in this case gibossp_capture_2). Then click on Deploy as shown in Figure 18.

We are presented with a new panel where we can enter the name of the new virtual machine to be deployed and the IP address. We can also modify the CPU and memory assignment. Then we can click on Deploy to start building the new partition (Figure 19).

The deployment has now started, as shown in Figure 20.

A new virtual machine appears in the Virtual Machines panel, as shown in Figure 21. It is in a Building state.

After a few minutes the partition moves from a Building state shown in Figure 22 to an Active state shown in Figure 23.

After a short period of time the new partition is now Active and ready (OK).

For interest’s sake, we can view the VSCSI mappings and SSP configuration for the new partition.

$ lsmap -vadapter vhost6
SVSA            Physloc                    Client Partition ID
--------------- -------------------------- ------------------
vhost6          U8286.42A.214F58V-V1-C17   0x0000000d

VTD                   vtopt0
Status                Available
LUN                   0x8100000000000000
Backing device        /var/vio/VMLibrary/vopt_
Mirrored              N/A

VTD                   vtscsi3
Status                Available
LUN                   0x8200000000000000
Backing device        volume-boot-828642A_214F58V-
Mirrored              N/A

As you can see, there is a new vopt device assigned to the partition. This device is used by PowerVC and the activation engine to configure the new partition on first boot. The vopt maps to a file in the virtual media library. This file contains configuration information for the new host (i.e., IP address, default gateway, host name, etc.). The activation engine mounts the (virtual) cdrom device in the AIX partition and uses this configuration during its execution. After a period of time, the mapping is removed, once the activation engine configuration process is complete. Please refer to chmod666’s blog post for more detailed information.

$ r oem
# file /var/vio/VMLibrary/vopt_d683cba55bae42c9aecddfc34a488f10
commands text

# strings /var/vio/VMLibrary/vopt_d683cba55bae42c9aecddfc34a488f10
LINUX                           config-2
OpenStack Nova                                                                                                                                                                                                                GENISOIMAGE ISO 9660/HFS FILESYSTEM CREATOR (C) 1993 E.YOUNGDALE (C) 1997-2006 J.PEARSON/J.SCHILLING (C) 2006-2007 CDRKIT TEAM                                                                                                                 2014101113475800,2014101113475800,0000000000000000
iface eth0 inet static
: "d683cba5-5bae-42c9-aecd-dfc34a488f10", "availability_zone": "nova", 
"hostname": "", 
"launch_index": 0, "network_config": {"content_path": "/content/0000", 
"name": "network_config"}, "name": "gibopvc3"}

My new AIX partition is now up and running. I can see that I have to paths to my VSCSI disk, one from each VIOS.

[root@gibopvc3]/ # oslevel -s

[root@gibopvc3]/ # echo cvai | kdb -script
read vscsi_scsi_ptrs OK, ptr = 0xF1000000C01E4E20
(0)> cvai
Executing cvai command
vscsi0     0x000007 0x0000000000 0x0                s824vio2->vhost8
vscsi1     0x000007 0x0000000000 0x0                s824vio1->vhost6

End of execution for cvai command
(0)> Executing q command
[root@gibopvc3]/ #

PowerVC (and the activation engine) have automatically configured the IP address and hostname of the new partition.

[root@gibopvc3]/ # ifconfig -a
en0: flags=1e084863,480

Again, on the VIOS I can map the LU back to the associated vhost by looking for the LU UDID in the lsmap output.

SVSA            Physloc                                      Client Partition ID
--------------- -------------------------------------------- ------------------
vhost8          U8286.42A.214F58V-V2-C19                     0x0000000d

VTD                   vtscsi3
Status                Available
LUN                   0x8100000000000000
Backing device        volume-boot-828642A_214F58V-gibo326a7729a3ab465ba7ae959b66f87db9.
Mirrored              N/A

$ lu -list
POOL_NAME: olympic
LU_NAME                 SIZE(MB)    UNUSED(MB)  UDID
volume-boot-828642A_21~ 51200       50837       49dcdd9ad068729966f45045dbd50f92
gibbossp1               51200       48355       2c85a15aa486f3e22f989649185f0d25
volume-boot-828642A_21~ 51200       50903       fd1a51a9d1206c54cca1c1cccdcce409
volume-boot-828642A_21~ 51200       50834       a33914517d53a446ac3c61bd7dd6ffc3

From the Storage panel, under Storage Provider, I can see the new snapshot (captured image) under the voyager SSP (Figure 25).

If I click on the image name, I can view the properties of the image as well get a list of the virtual machines that are currently deployed from this image (Figure 26).

Easy and Fast

From now on, if we want to deploy a new AIX partition to do some testing, it’s extremely easy and fast! It really is a simple point-and-click operation and in a few minutes we have a new AIX environment ready for use.

Chris Gibson is an AIX and PowerVM specialist located in Melbourne, Australia. He is an IBM Champion for Power Systems, IBM CATE (Power Systems and AIX), and a co-author of several IBM Redbooks publications.

Like what you just read? To receive technical tips and articles directly in your inbox twice per month, sign up for the EXTRA e-newsletter here.

comments powered by Disqus



2019 Solutions Edition

A Comprehensive Online Buyer's Guide to Solutions, Services and Education.


A Closer Look at the IBM PowerVM 3.1 Update

IBM Systems Magazine Subscribe Box Read Now Link Subscribe Now Link iPad App Google Play Store
IBMi News Sign Up Today! Past News Letters