4268 Storage partition migration is paused due to configuration error.

Explanation

This error is raised for any host or controller validation failure that is encountered during storage partition migration.
Event ID 051032
This event is raised at the target system for unhealthy login or discovery status of hosts in the partition.
Event ID 051422
This event is raised if all controllers in the system are not online, which affects the availability post migration.
Event ID 051047, 051048, 051049

This event is raised if any validation failure encountered during partition migration. Check the corresponding event text to identify where the validation failure occurred.

Event ID 51059

This event is raised if the connectivity configuration at the source system and desired target system is not suitable for partition migration.

Event ID 51060
This event is raised if the connectivity configuration at the desired target system and disaster recovery linked system are not suitable for partition migration.

User response

Perform the following actions to fix the respective event:
For event ID 051032

If you have fixed the issues on the target cluster, use the following command to continue the migration:

chpartition -migrationaction fixeventwithchecks <partition_id>

This continues the migration procedure from source system with the host validations checks.

If you want to continue the migration even if the host validation fails (in scenarios where the hosts are known to be down or to load balance partitions across the systems), use the following command to force the storage partition migration overriding any host validations:
chpartition -migrationaction fixeventskipchecks <partition_id>
If you do not want to continue the migration, or need some time to fix the host and networking issues on the target and reattempt the migration at a later point, use the following command to trigger the rollback operation at the target system:
chpartition -override -location <source_system> <partition_id>
For event ID 051422

If all the reported issues are fixed, use the following command to continue with the migration:

chpartition -migrationaction fixeventwithchecks <partition_id>

If you do not want to migrate, use the following command to cancel the migration:

chpartition -override -location <source_system> <partition_id>
For event ID 051047
  • Fix the event with the following command:
    chpartition -migrationaction fixeventwithchecks <partition_id>
  • You can abort the migration by using the following command: 
    chpartition -override -location <source_system> <partition_id>
  • You can cancel the rollback by using the following command. 
    chpartition -migrationaction cancelrollback <partition_id>
For event ID 051048
  • Fix the event with the following command:
    chpartition -migrationaction fixeventwithchecks <partition_id>
  • You can abort the migration by using the following command:
    chpartition -override -location <source_system> <partition_id>
For event ID 051049
  • Fix the event with the following command:
    chpartition -migrationaction fixeventwithchecks <partition_id>
  • You can abort the migration by using the following command:
    chpartition -override -location <source_system> <partition_id>
For event ID 51059
To continue the partition migration, remove any TCP/IP partnership between the source system and desired target system, and mark this event as resolved after you complete either of the following actions:
  • Manually create either a Fibre Channel or short-distance partnerships using RDMA between the source and target system by using the management GUI or CLI.
  • Or, configure the source system and desired target system with the preferred connectivity, such as Fibre Channel or short-distance partnerships using RDMA. For configuration procedure, see Partnerships.
Migration operation detects the following configurations on systems and creates partnership automatically after the event is resolved:
  • For Fibre Channel connectivity: Systems must be visible to each other, whereas configuring custom FC port masks is optional.
  • For Ethernet connectivity: Systems are configured with highspeedreplication type portsets that can be used for automatic partnership creation.
For event ID 51060
To continue the partition migration, mark this event as resolved after either of the following actions:
  • Manually create either a TCP/IP, Fibre Channel, or short-distance partnerships using RDMA between the target system and disaster recovery linked system by using the management GUI or CLI.
  • Or, configure the target system and disaster recovery linked system with the preferred connectivity, such as TCP/IP, Fibre Channel, or short-distance partnerships using RDMA. For configuration procedure, see Partnerships.
Migration operation detects the following configurations on systems and creates partnership automatically after the event is resolved:
  • For Fibre Channel connectivity: Systems must be visible to each other, whereas configuring custom FC port masks is optional.
  • For Ethernet connectivity: Systems are configured with replication or highspeedreplication type portsets that can be used for automatic partnership creation.