Simplified remote restart and migration considerations

Learn how to use the --requirerr option of the migrlpar command by using the Hardware Management Console (HMC) command-line interface.

When the mobile partition is not capable of the simplified version of the remote restart feature and the destination server does not support the simplified version of the remote restart feature, the following scenarios apply:
  • When you do not specify any override value, the migration operation succeeds and the mobile partition is not capable of the simplified version of the remote restart feature after the migration operation completes.
  • When you specify a value 1 for the override, the migration operation fails.
  • When you specify a value 2 for the override, the migration operation succeeds and the mobile partition is not capable of the simplified version of the remote restart feature after the migration operation completes.
When the mobile partition is not capable of the simplified version of the remote restart feature and the destination server supports the simplified version of the remote restart feature, the following scenarios apply:
  • When you do not specify any override value, the migration operation succeeds and the mobile partition is not capable of the simplified version of the remote restart feature after the migration operation completes.
  • When you specify a value 1 for the override, the migration operation succeeds and the remote restart capability of the mobile partition is enabled after the migration operation completes.
  • When you specify a value 2 for the override, the migration operation succeeds and the remote restart capability of the mobile partition is enabled after the migration operation completes.
When the mobile partition is capable of the simplified version of the remote restart feature and the destination server does not support the simplified version of the remote restart feature, the following scenarios apply:
  • When you do not specify any override value, the migration operation fails.
  • When you specify a value 1 for the override, the migration operation fails.
  • When you specify a value 2 for the override, the migration operation succeeds and the mobile partition is not capable of the simplified version of the remote restart feature after the migration operation completes.
When the mobile partition is capable of the simplified version of the remote restart feature and the destination server supports the simplified version of the remote restart feature, the following scenarios apply:
  • When you do not specify any override value, the migration operation succeeds and the remote restart capability of the mobile partition is retained after the migration operation completes.
  • When you specify a value 1 for the override, the migration operation succeeds and the remote restart capability of the mobile partition is retained after the migration operation completes.
  • When you specify a value 2 for the override, the migration operation succeeds and the remote restart capability of the mobile partition is retained after the migration operation completes.

When the source and destination servers are managed by different Hardware Management Consoles, and when the destination HMC is at a version earlier than 8.5.0, and if you specify the --requirerr option, the migration operation fails.




Last updated: Tue, March 12, 2019