padmin viosupgrade failed during viosbr restore: "0590-105 The execution of a command failed ERROR- 'ArtexRules' are failed to restore"

Troubleshooting

Problem

viosbr restore failed with ArtexRules error after VIOS upgrade from 2.2.6 to 3.1 via padmin viosupgrade command.

Symptom

Status of the VIOS upgrade/migration operation after the VIOS partition has restarted:

    $ viosupgrade -q -l
    Welcome to viosupgrade tool.
    Getting status of node(s):
     
    viosupgrade FAILED
     
    Please see the vioupgrade status:
    ====================================
    Thu Mar 7 11:31:18 2019|STARTED
    Thu Mar 7 11:38:04 2019|TRIGGERED
    Thu Mar 7 08:52:20 2019|RESTORE
    Thu Mar 7 08:52:26 2019|FAILED
     
    Please see the viosbr restore status:
    ====================================
     
    Viosbr restore timestamp:
    Thu Mar 7 08:52:19 CST 2019
    License acceptance is successful
     
    Restoring the backup..
     
    Restore summary on pbws2802:
    Backedup Devices that are unable to restore/change
    ==================================================
    'ArtexRules'
     
    DEPLOYED or CHANGED devices:
    ============================
    Dev name during BACKUP                 Dev name after RESTORE
    ----------------------                 ----------------------
     
    Some error messages may contain invalid information
    for the Virtual I/O Server environment.
     
    0590-105 The execution of a command failed
    ERROR- 'ArtexRules' are failed to restore
    Errors have been detected during restoration.
    Details are in the log file : /home/ios/logs/restore_trace.out.
     viosbr restore failed..fix the issue and restart cluster (if exist) after restore is successful..
    Inittab entry is removed..

Cause

VIOS rules for EMC software were in place at the orginal VIOS Version (2.2) and a custom mksysb image including that software was not used for the upgrade. In this scenario, the following EMC filesets were installed at 2.2.6.

 EMC.CLARiiON.aix.rte      6.0.0.6 COMMITTED EMC CLARiiON AIX Support
 EMC.CLARiiON.fcp.MPIO.rte 6.0.0.6 COMMITTED EMC CLARiiON FCP MPIO Support
 EMC.Symmetrix.aix.rte     6.0.0.6 COMMITTED EMC Symmetrix AIX Support
 EMC.Symmetrix.fcp.MPIO.rte 6.0.0.6 COMMITTED EMC Symmetrix FCP MPIO Support

A VIOS upgrade involves doing a new and complete install. If the 3.1 mksysb image used for the migration was not customized to include the EMC software installed at version 2, then viosbr restore fails on 'ArtexRules'.

Environment

VIOS 2.2.6 with third-party storage software installed prior to upgrading to VIOS 3.1

Diagnosing The Problem

Determine if third-party storage software was installed at the original (2.2.6) VIOS level, such as the EMC filesets previously mentioned.

Resolving The Problem

Option 1 (workaround)

Install the third-party storage software (in this example, the missing EMC software).

Then, manually try viosbr restore.

Option 2 (official answer)

Create a custom 3.1 mksysb image to include the needed third-party software. Then retry the viosupgrade using the customized mksysb image.

Note: The custom mksysb must include the same storage version as the original 2.2.6 level.

To create the customized mksysb image, use the backupios command. See details at

Miscellaneous information about upgrading Virtual I/O Server

> VIOS image preparation

This will entail using the IBM 3.1 images from the Entitlement Software Support site to do a new and complete install of VIOS 3.1 as noted in the viosupgrade checklist > VIOS requirement #4. In short, you would want to create a temporary/dummy VIOS partition to install 3.1. Then, customize that new installed VIOS by installing the third-party software application(s) currently installed on the original 2.2.6 VIOS partition.

Once the storage software has been installed, you can create the custom mksysb by using the backupios command with the -mksysb option as noted on the previous reference. This is the mksysb image that can then be used to upgrade the existing VIOS 2.2.6 partitions to version 3.1.

Related Information

Managing EMC devices by using rules files

IBM PowerVM: Expected services when contacting IBM Support for VIOS versions th…

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"ARM Category":[{"code":"a8m0z000000bqzKAAQ","label":"VIOSUPGRADE-\u003E2.2.6 to 3.1"}],"ARM Case Number":"TS022963629","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0;3.1.1;3.1.2;3.1.3;3.1.4;4.1.0;4.1.1;4.1.2"}]

Tips