Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace AIX
Created by Guest
Created on Jan 11, 2017

alt_disk_mksysb on aix

I was able to reproduce your problem in the lab system.
- The problem occurs with EtherChannel configuration.
- The problem doesn't occur with non-EtherChannel configuration.
To cut a long story short, it is a design limitation. The alt_disk_mksysb operation is not designed to be used for migration completely.
The details are as the following. When the alt_disk_mksysb operation is performed, it is designed to remove old customized ODM and reconfigure devices from the scratch at first boot time in the target alternate disk.
Network configuration exists in customized ODM of the mksysb file. With the alt_disk_mksysb operation, the network configuration will be removed in the target alternate disk.
The alt_disk_mksysb operation extracts old network configuration from the mksysb file and keeps them in a script file in the target alternate disk and execute the script at first boot time from the alternate disk to make the new configuration as close as possible to the old one.
In that way, other Ethernet adapters can be configured at boot time before running the script, so that the network configuration can be restored at first boot time from the target alternate disk.
However regarding the EtherChannel adapter, it can't be configured at boot time before running the script. So the script will fail to configure network configuration since there is no configured EtherChannel adapter.
So that is a design limitation with the alt_disk_mksysb operation. You cannot use your procedure for migration with EtherChannel configuration.
Since it is a design limitation, not a defect, we are not able to ask AIX development to change this through PMR process.
If you want EtherChannel configuration is supported under your migration procedure, you can raise a RFE(Request for enhancements) through the following link instead.

Idea priority Urgent
  • Guest
    Jul 24, 2018

    IBM has considered the request, and it will not be delivered in the future. If this request receives continued customer interest, it may be resubmitted for consideration after 12 months from the submit date.