IBM Support

Migrating multibos enabled AIX systems with nimadm

How To


Summary

Learn how to migrate multibos enabled AIX systems with nimadm to AIX 7.3.

Objective

The Redbook, IBM AIX Enhancements and Modernization (published 2020) https://www.redbooks.ibm.com/abstracts/sg248453.html, states:

"nimadm support for MultiBOS environments

With the multibos command, root-level administrator can create multiple instances of AIX on the same rootvg. The multibos setup operation creates a standby base operating system

(BOS) that boots from a distinct boot logical volume (BLV). This action creates two bootable sets of BOS on a rootvg.

Before AIX 7.2, the nimadm command did not support the migration of AIX instances that were configured for MultiBOS. With AIX 7.2, the nimadm command successfully performs

preservation or migration installations of AIX instances to the next level of AIX that is available."

Previously, prior to AIX 7.2, we have always required administrators to remove any multibos BOS instance that exists and ensure that the rootvg logical volumes are not using any bos_ LV names (and reboot if required). Then you could perform a nimadm operation. The AIX 7.1 (and earlier) documentation, https://www.ibm.com/docs/en/aix/7.1?topic=n-nimadm-command, stated the following:

"The nimadm command is not supported with the multibos command when there is a bos_hd5 logical volume."

You will not find this statement in the documentation for AIX 7.2 or later.

Given this limitation is removed starting with AIX 7.2, this document provides some examples of how to migrate an AIX 7.2 system, with multibos standby logical volumes and file systems, to AIX 7.3. Two of the most common scenarios are covered in this article.

Note: If you encounter a scenario not covered in this article, please contact IBM AIX support for guidance and assistance.

Steps

Scenario 1. NIMADM migration from AIX 7200-05-05-2246 to 7300-01-01-2246. Client rootvg is ‘multibos-enabled’ and booted from bos_hd5.

1. The AIX NIM client is running AIX 7.2 (7200-05-05-2246).

root@aixmig / # oslevel -s
7200-05-05-2246

2. The AIX NIM client's root volume group is multibos "enabled". There are two instances of AIX. The standby instance is not mounted.

root@aixmig / # lsvg -l rootvg
rootvg:
LV NAME             TYPE       LPs     PPs     PVs  LV STATE      MOUNT POINT
hd5                 boot       2       2       1    closed/syncd  N/A
hd6                 paging     32      32      1    open/syncd    N/A
hd8                 jfs2log    1       1       1    open/syncd    N/A
hd4                 jfs2       6       6       1    closed/syncd  /bos_inst            <<<< Standby multibos BOS instance, not mounted
hd2                 jfs2       147     147     1    closed/syncd  /bos_inst/usr        <<<< Standby multibos BOS instance, not mounted
hd9var              jfs2       11      11      1    closed/syncd  /bos_inst/var        <<<< Standby multibos BOS instance, not mounted
hd3                 jfs2       8       8       1    open/syncd    /tmp
hd1                 jfs2       1       1       1    open/syncd    /home
hd10opt             jfs2       2       2       1    closed/syncd  /bos_inst/opt <<<< Standby multibos BOS instance, not mounted
hd11admin           jfs2       8       8       1    open/syncd    /admin
lg_dumplv           sysdump    64      64      1    open/syncd    N/A
livedump            jfs2       16      16      1    open/syncd    /var/adm/ras/livedump
bos_hd5             boot       2       2       1    closed/syncd  N/A                
bos_hd4             jfs2       6       6       1    open/syncd    /
bos_hd2             jfs2       147     147     1    open/syncd    /usr
bos_hd9var          jfs2       11      11      1    open/syncd    /var
bos_hd10opt         jfs2       2       2       1    open/syncd    /opt
 

3. The AIX NIM client is booted from the multibos boot logical volume, i.e., bos_hd5. And the /, /usr, /var and /opt file systems are all mounted on LV names starting with bos_.

root@aixmig / # bootinfo -v
bos_hd5
root@aixmig / # mount
  node       mounted        mounted over    vfs       date        options
-------- ---------------  ---------------  ------ ------------ ---------------
         /dev/bos_hd4     /                jfs2   May 22 19:44 rw,log=/dev/hd8
         /dev/bos_hd2     /usr             jfs2   May 22 19:44 rw,log=/dev/hd8
         /dev/bos_hd9var  /var             jfs2   May 22 19:44 rw,log=/dev/hd8
         /dev/hd3         /tmp             jfs2   May 22 19:44 rw,log=/dev/hd8
         /dev/hd11admin   /admin           jfs2   May 22 19:44 rw,log=/dev/hd8
         /dev/hd1         /home            jfs2   May 22 19:44 rw,log=/dev/hd8
         /dev/bos_hd10opt /opt             jfs2   May 22 19:44 rw,log=/dev/hd8
         /proc            /proc            procfs May 22 19:44 rw
         /dev/livedump    /var/adm/ras/livedump jfs2   May 22 19:44 rw,log=/dev/hd8
         /ahafs           /aha             ahafs  May 22 19:44 rw

4. Before starting the nimadm operation we first remove the standby multibos instance.

root@aixmig / # multibos -R
Initializing multibos methods ...
Initializing log /etc/multibos/logs/op.alog ...
Gathering system information ...
+-----------------------------------------------------------------------------+
Remove Operation
+-----------------------------------------------------------------------------+
Verifying operation parameters ...
+-----------------------------------------------------------------------------+
Boot Partition Processing
+-----------------------------------------------------------------------------+
Active boot logical volume is bos_hd5.
Standby boot logical volume is hd5.
+-----------------------------------------------------------------------------+
Mount Processing
+-----------------------------------------------------------------------------+
Unmounting all standby BOS file systems ...
+-----------------------------------------------------------------------------+
File Systems
+-----------------------------------------------------------------------------+
Removing all standby BOS file systems ...
Removing standby BOS file system /bos_inst/opt
Removing standby BOS file system /bos_inst/var
Removing standby BOS file system /bos_inst/usr
Removing standby BOS file system /bos_inst
+-----------------------------------------------------------------------------+
Logical Volumes
+-----------------------------------------------------------------------------+
Removing all standby BOS logical volumes ...
Removing standby BOS logical volume hd5
+-----------------------------------------------------------------------------+
Bootlist Processing
+-----------------------------------------------------------------------------+
Verifying operation parameters ...
Setting bootlist to logical volume bos_hd5 on hdisk0.
ATTENTION: firmware recovery string for active BLV (bos_hd5):
boot /vdevice/v-scsi@30000002/disk@8100000000000000:4
Log file is /etc/multibos/logs/op.alog
Return Status = SUCCESS

We can confirm that the multibos instance is removed by running the multibos -S command and verifying it returns with a status of FAILURE.

root@aixmig / # multibos -S
Initializing multibos methods ...
Initializing log /etc/multibos/logs/op.alog ...
Gathering system information ...
multibos: 0565-077 Unable to locate standby BOS.

Log file is /etc/multibos/logs/op.alog
Return Status: FAILURE

Note: Failure to remove the multibos instance will cause nimadm to fail (in phase 11), with the following error message (when booted from bos_hd5):

0505-158 nimadm: WARNING, unexpected result from the awk_print command.
0505-184 nimadm: Error writing client boot image.

5. The root volume group no longer contains file systems starting with /bos_inst.

root@aixmig / # lsvg -l rootvg
rootvg:
LV NAME             TYPE       LPs     PPs     PVs  LV STATE      MOUNT POINT
hd6                 paging     32      32      1    open/syncd    N/A
hd8                 jfs2log    1       1       1    open/syncd    N/A
hd3                 jfs2       8       8       1    open/syncd    /tmp
hd1                 jfs2       1       1       1    open/syncd    /home
hd11admin           jfs2       8       8       1    open/syncd    /admin
lg_dumplv           sysdump    64      64      1    open/syncd    N/A
livedump            jfs2       16      16      1    open/syncd    /var/adm/ras/livedump
bos_hd5             boot       2       2       1    closed/syncd  N/A
bos_hd4             jfs2       6       6       1    open/syncd    /            
bos_hd2             jfs2       147     147     1    open/syncd    /usr
bos_hd9var          jfs2       11      11      1    open/syncd    /var
bos_hd10opt         jfs2       2       2       1    open/syncd    /opt

6. Start the nimadm operation. The NIM master is running AIX 7.3, 7300-01-01-2246.

nimmast# nimadm -j nimadmvg -c aixmig -s spotAIX73TL1SP1 -l AIX73TL1SP1 -d hdisk1 -Y

7. In Phase 11, nimadm will display a message stating, “0516-306 lslv: Unable to find  alt_hd5 in the Device”, however it will complete successfully.

 +-----------------------------------------------------------------------------+
Executing nimadm phase 11.
+-----------------------------------------------------------------------------+
Cloning altinst_rootvg on client, Phase 3.
Client alt_disk_install command: alt_disk_copy -j -M 7.3 -P3 -d "hdisk1"
## Phase 3 ###################
Verifying altinst_rootvg...
Modifying ODM on cloned disk.
0516-306 lslv: Unable to find  alt_hd5 in the Device
Configuration Database.
forced unmount of /alt_inst/var/adm/ras/livedump
forced unmount of /alt_inst/var/adm/ras/livedump
forced unmount of /alt_inst/var
forced unmount of /alt_inst/var
forced unmount of /alt_inst/usr
forced unmount of /alt_inst/usr
forced unmount of /alt_inst/tmp
forced unmount of /alt_inst/tmp
forced unmount of /alt_inst/opt
forced unmount of /alt_inst/opt
forced unmount of /alt_inst/home
forced unmount of /alt_inst/home
forced unmount of /alt_inst/admin
forced unmount of /alt_inst/admin
forced unmount of /alt_inst
forced unmount of /alt_inst
Changing logical volume names in volume group descriptor area.
Fixing LV control blocks...
Fixing file system superblocks...
Bootlist is set to the boot disk: hdisk1 blv=bos_hd5
 
+-----------------------------------------------------------------------------+
Executing nimadm phase 12.
+-----------------------------------------------------------------------------+
Cleaning up alt_disk_migration on the NIM master.
Cleaning up alt_disk_migration on client aixmig.

8. The AIX NIM client can now be rebooted into AIX 7.3 (from bos_hd5 in altinst_rootvg).

root@aixmig / # lspv
hdisk0          00f943f905265a62                    rootvg          active
hdisk1          00f943f9052659d1                    altinst_rootvg

root@aixmig / # bootlist -m normal -o
hdisk1 blv=bos_hd5 pathid=0
root@aixmig / # at now
shutdown -Fr
Job root.1684912676c0.a will be run at Wed May 24 03:17:56 EDT 2023.
;LPAR REBOOTS NOW
;
;AFTER REBOOT
...
*******************************************************************************
*                                                                             *
*                                                                             *
*  Welcome to AIX Version 7.3!                                                *
*                                                                             *
*                                                                             *
*  Please see the README file in /usr/lpp/bos for information pertinent to    *
*  this release of the AIX Operating System.                                  *
*                                                                             *
*                                                                             *
*******************************************************************************
root@aixmig / # oslevel -s
7300-01-01-2246
root@aixmig / # df
Filesystem    512-blocks      Free %Used    Iused %Iused Mounted on
/dev/hd4          196608     54616   73%     3783    36% /
/dev/hd2         5308416    376120   93%    55794    57% /usr
/dev/hd9var       360448    257816   29%      678     3% /var
/dev/hd3          262144    251680    4%       86     1% /tmp
/dev/hd11admin     262144    261416    1%        5     1% /admin
/dev/hd1           32768     32024    3%        7     1% /home
/dev/hd10opt       65536     27320   59%      221     7% /opt
/proc                  -         -    -        -      - /proc
/dev/livedump     524288    523552    1%        4     1% /var/adm/ras/livedump
/ahafs                 -         -    -       35     1% /aha

The migration of the multibos enabled AIX NIM client, with nimadm to AIX 7.3 is now complete for scenario 1.

Scenario 2. NIMADM migration from AIX 7200-05-05-2246 to 7300-01-01-2246. Client rootvg is ‘multibos-enabled’ and booted from hd5.

1. The AIX NIM client is running AIX 7.2 (7200-05-05-2246).

root@aixmig / # oslevel -s
7200-05-05-2246

2. The AIX NIM client's root volume group is multibos "enabled". There are two instances of AIX. The standby instance is currently not mounted.

root@aixmig / # lsvg -l rootvg
rootvg:
LV NAME             TYPE       LPs     PPs     PVs  LV STATE      MOUNT POINT
hd5                 boot       2       2       1    closed/syncd  N/A
hd6                 paging     32      32      1    open/syncd    N/A
hd8                 jfs2log    1       1       1    open/syncd    N/A
hd4                 jfs2       6       6       1    open/syncd    /
hd2                 jfs2       147     147     1    open/syncd    /usr
hd9var              jfs2       11      11      1    open/syncd    /var
hd3                 jfs2       8       8       1    open/syncd    /tmp
hd1                 jfs2       1       1       1    open/syncd    /home
hd10opt             jfs2       2       2       1    open/syncd    /opt
hd11admin           jfs2       8       8       1    open/syncd    /admin
lg_dumplv           sysdump    64      64      1    open/syncd    N/A
livedump            jfs2       16      16      1    open/syncd    /var/adm/ras/livedump
bos_hd5             boot       2       2       1    closed/syncd  N/A
bos_hd4             jfs2       6       6       1    closed/syncd  /bos_inst            <<<< Standby multibos BOS instance, not mounted
bos_hd2             jfs2       147     147     1    closed/syncd  /bos_inst/usr        <<<< Standby multibos BOS instance, not mounted
bos_hd9var          jfs2       11      11      1    closed/syncd  /bos_inst/var        <<<< Standby multibos BOS instance, not mounted
bos_hd10opt         jfs2       2       2       1    closed/syncd  /bos_inst/opt        <<<< Standby multibos BOS instance, not mounted

3. The AIX NIM client is booted from the legacy boot logical volume, i.e., hd5. And the /, /usr, /var and /opt file systems are all mounted on LV names starting with hd.

root@aixmig / # bootinfo -v
hd5
root@aixmig / # mount
  node       mounted        mounted over    vfs       date        options
-------- ---------------  ---------------  ------ ------------ ---------------
         /dev/hd4         /                jfs2   May 25 01:14 rw,log=/dev/hd8
         /dev/hd2         /usr             jfs2   May 25 01:14 rw,log=/dev/hd8
         /dev/hd9var      /var             jfs2   May 25 01:14 rw,log=/dev/hd8
         /dev/hd3         /tmp             jfs2   May 25 01:14 rw,log=/dev/hd8
         /dev/hd1         /home            jfs2   May 25 01:14 rw,log=/dev/hd8
         /proc            /proc            procfs May 25 01:14 rw
         /dev/hd10opt     /opt             jfs2   May 25 01:14 rw,log=/dev/hd8
         /dev/hd11admin   /admin           jfs2   May 25 01:14 rw,log=/dev/hd8
         /dev/livedump    /var/adm/ras/livedump jfs2   May 25 01:14 rw,log=/dev/hd8
         /ahafs           /aha             ahafs  May 25 01:14 rw

4. Before starting the nimadm operation we first mount the standby multibos instance file systems.

root@aixmig / # multibos -m
Initializing multibos methods ...
Initializing log /etc/multibos/logs/op.alog ...
Gathering system information ...
+-----------------------------------------------------------------------------+
BOS Mount Operation
+-----------------------------------------------------------------------------+
Verifying operation parameters ...
+-----------------------------------------------------------------------------+
Mount Processing
+-----------------------------------------------------------------------------+
Mounting all standby BOS file systems ...
Mounting /bos_inst
Mounting /bos_inst/usr
Mounting /bos_inst/var
Mounting /bos_inst/opt
Log file is /etc/multibos/logs/op.alog
Return Status = SUCCESS
root@aixmig / # mount
  node       mounted        mounted over    vfs       date        options
-------- ---------------  ---------------  ------ ------------ ---------------
         /dev/hd4         /                jfs2   May 25 01:14 rw,log=/dev/hd8
         /dev/hd2         /usr             jfs2   May 25 01:14 rw,log=/dev/hd8
         /dev/hd9var      /var             jfs2   May 25 01:14 rw,log=/dev/hd8
         /dev/hd3         /tmp             jfs2   May 25 01:14 rw,log=/dev/hd8
         /dev/hd1         /home            jfs2   May 25 01:14 rw,log=/dev/hd8
         /proc            /proc            procfs May 25 01:14 rw
         /dev/hd10opt     /opt             jfs2   May 25 01:14 rw,log=/dev/hd8
         /dev/hd11admin   /admin           jfs2   May 25 01:14 rw,log=/dev/hd8
         /dev/livedump    /var/adm/ras/livedump jfs2   May 25 01:14 rw,log=/dev/hd8
         /ahafs           /aha             ahafs  May 25 01:14 rw
         /dev/bos_hd4     /bos_inst        jfs2   May 25 18:27 rw,log=/dev/hd8    <<<< Standby multibos BOS instance mounted
         /dev/bos_hd2     /bos_inst/usr    jfs2   May 25 18:27 rw,log=/dev/hd8    <<<< Standby multibos BOS instance mounted
         /dev/bos_hd9var  /bos_inst/var    jfs2   May 25 18:27 rw,log=/dev/hd8    <<<< Standby multibos BOS instance mounted
         /dev/bos_hd10opt /bos_inst/opt    jfs2   May 25 18:27 rw,log=/dev/hd8    <<<< Standby multibos BOS instance mounted

Note: Failure to mount the standby multibos instance file systems will cause nimadm to fail (in phase 11), with the following error message (when booted from hd5):

alt_disk_copy: 0505-218 ATTENTION: init_multibos() returned an unexpected result.

5. The standby multibos file systems are now mounted under /bos_inst.

root@aixmig / # lsvg -l rootvg
rootvg:
LV NAME             TYPE       LPs     PPs     PVs  LV STATE      MOUNT POINT
hd5                 boot       2       2       1    closed/syncd  N/A
hd6                 paging     32      32      1    open/syncd    N/A
hd8                 jfs2log    1       1       1    open/syncd    N/A
hd4                 jfs2       6       6       1    open/syncd    /
hd2                 jfs2       147     147     1    open/syncd    /usr
hd9var              jfs2       11      11      1    open/syncd    /var
hd3                 jfs2       8       8       1    open/syncd    /tmp
hd1                 jfs2       1       1       1    open/syncd    /home
hd10opt             jfs2       2       2       1    open/syncd    /opt
hd11admin           jfs2       8       8       1    open/syncd    /admin
lg_dumplv           sysdump    64      64      1    open/syncd    N/A
livedump            jfs2       16      16      1    open/syncd    /var/adm/ras/livedump
bos_hd5             boot       2       2       1    closed/syncd  N/A
bos_hd4             jfs2       6       6       1    open/syncd    /bos_inst
bos_hd2             jfs2       147     147     1    open/syncd    /bos_inst/usr
bos_hd9var          jfs2       11      11      1    open/syncd    /bos_inst/var
bos_hd10opt         jfs2       2       2       1    open/syncd    /bos_inst/opt

Note: The active ODM is migrated. That is, in this scenario, the system is booted from hd5 and the root file system (/), is mounted on hd4. Therefore, even though the standby root file system (/bos_inst) has also been (manually) mounted, the nimadm migration will only migrate the AIX OS data located in the active (“booted”) rootvg file systems (i.e., hd4 /, hd2 /usr, hd9var /var and hd10opt /opt). The AIX OS data in the standby instance (under /bos_inst) is NOT targeted for migration to 7.3.

6. Start the nimadm operation. The NIM master is running AIX 7.3, 7300-01-01-2246.

nimmast# nimadm -j nimadmvg -c aixmig -s spotAIX73TL1SP1 -l AIX73TL1SP1 -d hdisk1 -Y

7. The nimadm operation will complete all phases successfully.

+-----------------------------------------------------------------------------+
Executing nimadm phase 11.
+-----------------------------------------------------------------------------+
Cloning altinst_rootvg on client, Phase 3.
Client alt_disk_install command: alt_disk_copy -j -M 7.3 -P3 -d "hdisk1"
## Phase 3 ###################
Verifying altinst_rootvg...
Modifying ODM on cloned disk.
forced unmount of /alt_inst/var/adm/ras/livedump
forced unmount of /alt_inst/var/adm/ras/livedump
forced unmount of /alt_inst/var
forced unmount of /alt_inst/var
forced unmount of /alt_inst/usr
forced unmount of /alt_inst/usr
forced unmount of /alt_inst/tmp
forced unmount of /alt_inst/tmp
forced unmount of /alt_inst/opt
forced unmount of /alt_inst/opt
forced unmount of /alt_inst/home
forced unmount of /alt_inst/home
forced unmount of /alt_inst/bos_inst/var
forced unmount of /alt_inst/bos_inst/var
forced unmount of /alt_inst/bos_inst/usr
forced unmount of /alt_inst/bos_inst/usr
forced unmount of /alt_inst/bos_inst/opt
forced unmount of /alt_inst/bos_inst/opt
forced unmount of /alt_inst/bos_inst
forced unmount of /alt_inst/bos_inst
forced unmount of /alt_inst/admin
forced unmount of /alt_inst/admin
forced unmount of /alt_inst
forced unmount of /alt_inst
Changing logical volume names in volume group descriptor area.
Fixing LV control blocks...
Fixing file system superblocks...
Bootlist is set to the boot disk: hdisk1 blv=hd5
+-----------------------------------------------------------------------------+
Executing nimadm phase 12.
+-----------------------------------------------------------------------------+
Cleaning up alt_disk_migration on the NIM master.
Cleaning up alt_disk_migration on client aixmig.

Note: Once the nimadm operation is finished, if you wish, you can unmount the standby multibos file systems at this point, (or you can leave them mounted). For example:

root@aixmig / # multibos -u
Initializing multibos methods ...
Initializing log /etc/multibos/logs/op.alog ...
Gathering system information ...
+-----------------------------------------------------------------------------+
BOS Unmount Operation
+-----------------------------------------------------------------------------+
Verifying operation parameters ...
+-----------------------------------------------------------------------------+
Mount Processing
+-----------------------------------------------------------------------------+
Unmounting all standby BOS file systems ...
Unmounting /bos_inst/opt
Unmounting /bos_inst/var
Unmounting /bos_inst/usr
Unmounting /bos_inst
Log file is /etc/multibos/logs/op.alog
Return Status = SUCCESS

8. The AIX NIM client can now be rebooted into AIX 7.3 (from hd5 in altinst_rootvg).

root@aixmig / # lspv
hdisk0          00f943f905265a62                    rootvg          active
hdisk1          00f943f9052659d1                    altinst_rootvg
root@aixmig / # bootlist -m normal -o
hdisk1 blv=hd5 pathid=0
root@aixmig / # at now
shutdown -Fr
Job root.1684912676c0.a will be run at Wed May 24 03:17:56 EDT 2023.
;LPAR REBOOTS NOW
;
;AFTER REBOOT
...
*******************************************************************************
*                                                                             *
*                                                                             *
*  Welcome to AIX Version 7.3!                                                *
*                                                                             *
*                                                                             *
*  Please see the README file in /usr/lpp/bos for information pertinent to    *
*  this release of the AIX Operating System.                                  *
*                                                                             *
*                                                                             *
*******************************************************************************
root@aixmig / # oslevel -s
7300-01-01-2246
root@aixmig / # df
Filesystem    512-blocks      Free %Used    Iused %Iused Mounted on
/dev/hd4          196608     54616   73%     3783    36% /
/dev/hd2         5308416    376120   93%    55794    57% /usr
/dev/hd9var       360448    257816   29%      678     3% /var
/dev/hd3          262144    251680    4%       86     1% /tmp
/dev/hd11admin     262144    261416    1%        5     1% /admin
/dev/hd1           32768     32024    3%        7     1% /home
/dev/hd10opt       65536     27320   59%      221     7% /opt
/proc                  -         -    -        -      - /proc
/dev/livedump     524288    523552    1%        4     1% /var/adm/ras/livedump
/ahafs                 -         -    -       35     1% /aha
root@aixmig / # lsvg -l rootvg
rootvg:
LV NAME             TYPE       LPs     PPs     PVs  LV STATE      MOUNT POINT
hd5                 boot       3       3       1    closed/syncd  N/A
hd6                 paging     32      32      1    open/syncd    N/A
hd8                 jfs2log    1       1       1    open/syncd    N/A
hd4                 jfs2       6       6       1    open/syncd    /
hd2                 jfs2       162     162     1    open/syncd    /usr
hd9var              jfs2       11      11      1    open/syncd    /var
hd3                 jfs2       8       8       1    open/syncd    /tmp
hd1                 jfs2       1       1       1    open/syncd    /home
hd10opt             jfs2       2       2       1    open/syncd    /opt
hd11admin           jfs2       8       8       1    open/syncd    /admin
lg_dumplv           sysdump    64      64      1    open/syncd    N/A
livedump            jfs2       16      16      1    open/syncd    /var/adm/ras/livedump
bos_hd5             boot       3       3       1    closed/syncd  N/A
bos_hd4             jfs2       6       6       1    closed/syncd  /bos_inst
bos_hd2             jfs2       147     147     1    closed/syncd  /bos_inst/usr
bos_hd9var          jfs2       11      11      1    closed/syncd  /bos_inst/var
bos_hd10opt         jfs2       2       2       1    closed/syncd  /bos_inst/opt

The old multibos standby instance file systems can be mounted/unmounted (with multibos -m/-u), but you will not be able to boot from the standby instance. You would need to remove and recreate the standby instance, on AIX 7.3, if you need to utilize a multibos environment again after migration.

Note: If you need to return to the previous version of AIX, that is 7.2, you can alter the bootlist to point to the old_rootvg. In this scenario, you would need to include the boot logical volume (blv) name, as there two instances of AIX in the old rootvg. In the example below we specify blv=hd5 so the system will reboot using the (original) hd5 BLV device:

root@aixmig / # lspv
hdisk0          00f943f905265a62                    old_rootvg
hdisk1          00f943f9052659d1                    rootvg          active
root@aixmig / # bootlist -m normal hdisk0
0514-229 bootlist: Multiple boot logical volumes found on disk 'hdisk0'.
        Use the 'blv' attribute to specify the one from which to boot
root@aixmig / # bootlist -m normal hdisk0 blv=hd5
root@aixmig / # bootlist -m normal -o
hdisk0 blv=hd5 pathid=0

The migration of the multibos enabled AIX NIM client, with nimadm to AIX 7.3 is now complete for scenario 2.

End of document.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB08","label":"Cognitive Systems"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG10","label":"AIX"},"ARM Category":[{"code":"a8m0z000000cvz3AAA","label":"Install-\u003EMigration"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"}],"Version":"7.2.0;7.3.0"}]

Document Information

Modified date:
07 June 2023

UID

ibm16999029

Page Feedback