Completing the migration
Check if the migration run successfully.
Check and complete the migration:
-
Make sure that the domain is started and that all nodes in the domain are online.
- Issue the lsrpdomain command to display the version of RSCT that is
active in the peer domain, and the mixed version status:
Name OpState RSCTActiveVersion MixedVersions TSPort GSPort SA_Domain Online 2.5.5.1 Yes 12347 12348
- Issue the lsrpnode command to display which version of RSCT that is
installed on the nodes. Keep in mind that all nodes must be online:
Name OpState RSCTVersion node01 Online 2.5.5.1 node02 Online 2.5.5.1 node03 Online 2.5.5.1
- If the RSCT peer domain is running in mixed version mode (
MixedVersions = Yes
) and all nodes are upgraded to the new release, update the active RSCT version by running theRSCT CompleteMigration
action on one of the nodes. Before you can run the action, review the RSCT migration preparation procedures in IBM® RSCT Administration Guide.To update theTo verify that the active RSCT version is updated, enter the lsrpdomain command again:RSCTActiveVersion
, make sure that all nodes are online. Enter the following command on one of the nodes:runact -c IBM.PeerDomain CompleteMigration Options=0
Name OpState RSCTActiveVersion MixedVersions TSPort GSPort SA_Domain Online 2.5.5.1 No 12347 12348
-
Run the samctrl -m command to activate the new features and to complete the migration. For more information about the command, see samctrl.
- If the migration was done from System Automation for Multiplatforms release 3.1, you must adjust
the value of the attribute
OperationalFlags
by entering the following command on one of the nodes:
To display the actual value of this attribute, enter:chrsrc -c IBM.CHARMControl OperationalFlags=8088
lsrsrc -c IBM.CHARMControl
The new code features are active if the value of the ActiveVersion
and the
InstalledVersion
of System Automation for Multiplatforms is the same for all nodes.