Thanks for sharing the source and target levels. Unfortunately there seems to be no option to add '-D' to nimadm via playbook. You have to run the nimadm command to get the debug output.
Assuming the NIM server level you shared is same as the lpp_source level you are using for migration, it is not a recommended scenario to migrate to a level whose builddate (2446 in your case) is lower than what you already have (2520, which is your client level). So, you will have to pick 7.3 TL3 SP1 to migrate to.
Original Message:
Sent: Fri November 14, 2025 03:03 AM
From: Manoj Kumar
Subject: Error during OS migration from 7.2 to 7.3 in nimadm with ansible
This playbook calling nimadm role. Not sure how to add the '-D'.
Here is my source and target level. Please help to recreate.
root@nim_master:/# oslevel -s
7300-03-00-2446
root@nim_client:/# oslevel -s
7200-05-10-2520
------------------------------
Manoj Kumar
Original Message:
Sent: Fri November 14, 2025 02:18 AM
From: Saikrishna Akkela
Subject: Error during OS migration from 7.2 to 7.3 in nimadm with ansible
Hi Manoj,
I dont think nimadm prepares logs before this point of failure. Will you be able to run the nimadm with debug enabled? You just need to add the `-D` to your nimadm arguments.
If you can mention the exact source and target levels, we can try to recreate this.
------------------------------
Saikrishna Akkela
Original Message:
Sent: Thu November 13, 2025 08:27 AM
From: Manoj Kumar
Subject: Error during OS migration from 7.2 to 7.3 in nimadm with ansible
Hi Team,
We are getting error while try to migrate the OS from 7.2 to 7.3 with ansible through nimadm method. Kindly review the below playbook. It executes multiple phases successfully but on polling task gives the following error. Kindly help.
Error:
TASK [ibm.power_aix.nim_alt_disk_migration : ansible.builtin.debug] *******************************************************************************************************************************************
ok: [client -> nim_server] => {
"results": {
"ansible_job_id": "j986008711775.26870258",
"changed": true,
"failed": 0,
"finished": 0,
"results_file": "/.ansible_async/j986008711775.26870258",
"started": 1
}
}
TASK [ibm.power_aix.nim_alt_disk_migration : Polling until migration finishes (ignore FAILED RETRING messages)] ***********************************************************************************************
FAILED - RETRYING: [client -> nim_server]: Polling until migration finishes (ignore FAILED RETRING messages) (241 retries left).
FAILED - RETRYING: [client -> nim_server]: Polling until migration finishes (ignore FAILED RETRING messages) (240 retries left).
FAILED - RETRYING: [client -> nim_server]: Polling until migration finishes (ignore FAILED RETRING messages) (239 retries left).
FAILED - RETRYING: [client -> nim_server]: Polling until migration finishes (ignore FAILED RETRING messages) (238 retries left).
fatal: [client-> nim_master]: FAILED! => {"ansible_job_id": "j986008711775.26870258", "attempts": 5, "changed": true, "cmd": ["/usr/sbin/nimadm", "-c", "client", "-l", "AIX73TL3-lpp_source", "-s", "AIX73TL3_spot", "-j", "nimvg", "-Y", "-d", "hdisk5"], "delta": "0:04:09.602520", "end": "2025-11-13 08:02:42.603958", "finished": 1, "msg": "non-zero return code", "rc": 2, "results_file": "/.ansible_async/j986008711775.26870258", "start": "2025-11-13 07:58:33.001438", "started": 1, "stderr": "/usr/sbin/nimadm[1376]: Level: 0403-009 The specified number is not valid for this command.\n0505-151 nimadm: Error.", "stderr_lines": ["/usr/sbin/nimadm[1376]: Level: 0403-009 The specified number is not valid for this command.", "0505-151 nimadm: Error."], "stdout": "Initializing the NIM master.\nInitializing NIM client dsmppa003t.corpads.local.\nVerifying alt_disk_migration eligibility.\nCleaning up alt_disk_migration on the NIM master.", "stdout_lines": ["Initializing the NIM master.", "Initializing NIM client client.corpads.local.", "Verifying alt_disk_migration eligibility.", "Cleaning up alt_disk_migration on the NIM master."]}
PLAY RECAP ****************************************************************************************************************************************************************************************************
client: ok=74 changed=1 unreachable=0 failed=1 skipped=35 rescued=0 ignored=0
Playbook content:
---
- name: Perform AIX 7.2 to 7.3 alternate disk migration using nimadm
hosts: all
gather_facts: no
become: yes
collections:
- ibm.power_aix
vars:
nimadm_cache_vg: nimvg
nim_client: "{{ inventory_hostname }}"
target_disk: hdisk5
lpp_source: AIX73TL3-lpp_source
spot: AIX73TL3_spot
nim_master: nim_master
tasks:
- name: Run the nim_alt_disk_migration role to perform migration
block:
- include_role:
name: nim_alt_disk_migration
delegate_to: "{{ nim_master }}"
vars:
nim_alt_disk_migration_nim_client: "{{ nim_client }}"
nim_alt_disk_migration_target_disk:
disk_name: "{{ target_disk }}"
nim_alt_disk_migration_lpp_source: "{{ lpp_source }}"
nim_alt_disk_migration_spot: "{{ spot }}"
nim_alt_disk_migration_nimadm_cache_vg: "{{ nimadm_cache_vg }}"
#delegate_to: "{{ nim_master }}"
# register: nimadm_results
- name: Display migration outcome
ansible.builtin.debug:
var: nimadm_results
...
------------------------------
Manoj Kumar
------------------------------