vhost3 U9113.550.65E3A0C-V3-C8 0x00000006

VTD vhdbromonts00 LUN 0x8100000000000000 Backing device hdbromonts00 Physloc

VTD vhdbromonts01 LUN 0x8200000000000000 Backing device hdbromonts01 Physloc $ $ rmdev -dev vhost3 -recursive vhdbromonts00 deleted vhdbromonts01 deleted vhost3 deleted

VTD vtscsi16 LUN 0x8100000000000000 Backing device beastielv Physloc

VTD vtscsi17 LUN 0x8200000000000000 Backing device hdisk15 Physloc U787B.001.DNW3897-P1-C4-T1-W5006048448930A41-L2000000000000

File: I:openssh.base.client I:openssh.base.server I:openssh.license I:openssh.msg.HU_HU I:openssh.msg.RU_RU I:openssh.msg.hu_HU I:openssh.msg.ru_RU […]

File: I:Java14.license I:Java14.sdk I:Java14_64.license I:Java14_64.sdk […]

This is perl, v5.8.7 built for aix

bosboot: Boot image is 23320 512 byte blocks.

Build the DLPAR on the Hardware Management Console

Log in to the HMC using the Java WSM (Web-based System Manager) client. Then, follow the illustrated guide:

  1. Set the logical name of the partition:
  2. Because a load manager is not needed, say so to the creation wizard:
  3. Provide a name for the default profile:
  4. Time to set the memory allocation sizes:
  5. Select the kind of logical partition, which is shared in this case:
  6. Choose the desired entitlement capacity settings,...
    ... the shared mode and the use of virtual CPU (or not):
  7. Select the I/O unit(s) and its(their) attribution(s) from the available hardware on the p550:
  8. Don't choose I/O pools (its purpose is for Mainframe installation only).
  9. Answer that virtual I/O cards are required and create two Ethernet I/O modules on the two local virtual networks port's ID, as for this one:
    Do the same thing for a SCSI I/O module, using the same port's ID for the local and remote card (on the Virtual I/O Server):
    Be sure to set them to required since the virtual SCSI adapter will host the boot disk and update the number of virtual cards slots, if necessary:
  10. The use of a power management partition is not needed here.
  11. Last, select the optional settings for the profil, e.g. activate the surveillance of the connections:

**Important note:**Don't forget to add a new virtual SCSI I/O module (of server type) on the VIOS in order to connect to the just created VIOC. If you made this modification dynamically on the running VIOS, please report the changes back to the corresponding profile or you will be in big trouble at the next VIOS reboot!

Manage and allocate the Virtual I/O Server resources

The new DLPAR will use one sort of VIOS resource: storage device(s).

Case #1: reuse an already existing virtual adapter

If we want to reuse the virtual adapter provided to the DLPAR, we need to clean things up a little. So, delete the corresponding virtual adapter and its virtual devices attached:

$ lsmap -vadapter vhost3
SVSA            Physloc                                      Client Partition ID
vhost6          U9113.550.65E3A0C-V3-C11                     0x00000000


Assuming we will use one local SCSI disk space to hold the OS and one SAN disk to host the application data, here are the required steps to configure the VIOS.

Create a logical volume for the OS and be sure to have an unused SAN disk:

$ mklv -lv beastielv rootvg 80
$ lsdev | grep hdisk15
hdisk15    Available EMC Symmetrix FCP MPIO RaidS

Insert the wanted storage resources in the virtual adapter:

$  mkvdev -vdev beastielv -vadapter vhost6
vtscsi16 Available
$  mkvdev  -vdev hdisk15 -vadapter vhost6
vtscsi17 Available
$ lsmap -vadapter vhost6
SVSA            Physloc                                      Client Partition ID
*** 36,41 ****
  #   Broadcast client, no authentication.
! broadcastclient
  driftfile /etc/ntp.drift
  tracefile /etc/ntp.trace
vhost6          U9113.550.65E3A0C-V3-C11                     0x00000008

VTD                   vtscsi17
LUN                   0x8200000000000000
Backing device        hdisk15
Physloc               U787B.001.DNW3897-P1-C4-T1-W5006048448930A41-L2000000000000

VTD                   vtscsi18
LUN                   0x8300000000000000
Backing device        hdisk16
Physloc               U787B.001.DNW3897-P1-C4-T1-W5006048448930A41-L3000000000000

VTD                   vtscsi19
LUN                   0x8400000000000000
Backing device        hdisk23
Physloc               U787B.001.DNW3897-P1-C4-T1-W5006048448930A41-L12000000000000

VTD                   vtscsi20
LUN                   0x8500000000000000
Backing device        hdisk24
Physloc               U787B.001.DNW3897-P1-C4-T1-W5006048448930A41-L13000000000000

... and remove the corresponding logical volume:

$ rmlv beastielv
Warning, all data contained on logical volume beastielv will be destroyed.
rmlv: Do you wish to continue? y(es) n(o)? y
rmlv: Logical volume beastielv is removed.

Resize the /tmp file system and the swap space logical volume

Because the operating system was installed from scratch and the file system sizes were automatically adapted to the underlying SCSI virtual disk (in fact a logical volume provided by the VIOS on a locally attached SCSI disk), some default values may not be relevant for day to day use, especially on machine of server type.

In that sense, the size of the /tmp file system may be changed to a more sensible setting:

# df -k /tmp
Filesystem    1024-blocks      Free %Used    Iused %Iused Mounted on
/dev/hd3            32768     32388    2%       10     1% /tmp
# chfs -a size=1024M /tmp
Filesystem size changed to 2097152
# df -k /tmp
Filesystem    1024-blocks      Free %Used    Iused %Iused Mounted on
/dev/hd3          1048576   1048044    1%       10     1% /tmp

In the same time, the swap space may be enlarge to grow the available VM on the system:

# lsps -al
# lsps -as
Total Paging Space   Percent Used
      512MB               1%
# lsvg rootvg | grep "PP SIZE"
VG STATE:           active                   PP SIZE:        16 megabyte(s)
# echo "(2048-512)/16" | bc
# chps -s 96 -a y hd6
# lsps -as
Total Paging Space   Percent Used
      2048MB               1%

Install and configure the backup software tool (TSM)

Please consult the following documentation: How to Add a New "tsmsched" Service on AIX 5L.

Put this machine under the ldm management tool

Don't forget to add the new machine in the ldm local site utility in order to be able to manage it and obtain some useful information get on a daily basis.

# ldmadd beastie

sysadm: access denied on beastie ...
Configuring sysadm's ssh authorized_keys file ... beastie done.

Checking some prerequisites on beastie ... 

Updating ldm agent files on beastie ...

Interesting additional reading