Migrating user accounts manually

During the upgrade from SAN Volume Controller Console version 4.3.1 to version 5.1.0, the installation program attempts to migrate user accounts currently defined on the cluster. If the migration of those accounts fail with the installation program, you can manually migrate the user accounts by using the pmigrate.bat file in the support folder in the directory that you specified to install the SAN Volume Controller Console. The manual method provides detailed messages to indicate the possible cause of the failure.

You must run the manual migration command while the cluster is still running version 4.3.1. After you upgrade the SAN Volume Controller cluster to version 5.1.0, you cannot migrate users.

Note: If the cluster that you are migrating user accounts from is behind a firewall, ensure that you authenticate to the firewall before you attempt to migrate user accounts manually.

The pmigrate.bat file is launched from a Windows® command prompt and has the following format:

pmigrate PasswordFile=<Location of proxy CIMOM password file>
RoleFile=<Location of proxy CIMOM role file>
CimomIPAddress=<eCIMOM address> CimomPassword=<eCIMOM password>
[CimomUser=<eCIMOM username>]

In this format, the CIMOM password is the administrator password for the cluster and the CIMOM IP address is the cluster IP address. The installation program preserves the CIMOM password in the cimserver.passwd file and preserves the CIMOM role definitions in the roles.txt file. Both of these files are stored in the latest backup directory. When you specify these files, include the absolute path to the directory that they are contained in. The eCIMOM username must be superuser. To migrate user accounts manually, follow these steps:

At a Windows command prompt, enter the following command:

 "C:\Program Files\IBM\svcconsole\support\pmigrate.bat"
      PasswordFile="C:\Program Files\IBM\svcconsole\backup009
      \cimserver.passwd"
      RoleFile="C:\Program Files\IBM\svcconsole\backup009\roles.txt"
      CimomUser=superuser
      CimomIPAddress=1.1.1.1
      CimomPassword=mypassword

In this example, the backup directory is backup009, the CIMOM password file is named cimserver.passwrd, and the CIMOM roles file is named roles.txt.

This example migrates the user accounts successfully with the following results:

SVC Command Line Utility Version IBM-SVC-SMIS-Agent-5.1.0 
	Returning default value AgentDirectory=<C:\Program Files\IBM\svcconsole\cimom>
	Customization property file=<C:\Program 
    Files\IBM\svcconsole\cimom\svcutil.properties> is not present.
	Found CimomIPAddress=<1.1.1.1>  on command line
	Returning default value CimomIPPort=<5989>
	Returning default value CimomProtocol=<https://>
	Found CimomUser=<superuser> on command line
	Connected to: https://1.1.1.1:5989
	Found PasswordFile=<C:\Program Files\IBM\svcconsole\backup009\cimserver.passwd>
    on command line.
	Found 	RoleFile=<C:\Program Files\IBM\svcconsole\backup009\roles.txt> on 
    command line.
	Enumerating instances of:IBMTSSVC_ObjectManager
	Enumerating instances of:IBMTSSVC_Cluster
	CIM_AGENT_INFORMATION: Connected to CIM Agent running on cluster <MyCluster> at 
    software version <4.3.	1.7>
	Enumerating instances of:IBMTSSVC_User
	>>> Invoking method: makeEncrypted
	with input parameters:
	[0] : CIMArgument(name=name, value="newadmin")
	[1] : CIMArgument(name=encryptedPassword, value="admin1")
	[2] : CIMArgument(name=role, value=0)
	<<< Method <makeEncrypted> returned value: 0 	ADD_USER_SUCCESS: Successfully 
    added user <newadmin> with role <Administrator(0)>
>>> Invoking method: makeEncrypted
	with input parameters:
	[0] : CIMArgument(name=name, value="newmonitor")
	[1] : CIMArgument(name=encryptedPassword, value="monitor1")
	[2] : CIMArgument(name=role, value=3)
	<<< Method <makeEncrypted> returned value: 0
	ADD_USER_SUCCESS: Successfully added user <newmonitor> with role <Monitor(3)>
	Restarting CIM Agent....
	Sending shutdown message to CIM Agent
	>>> Invoking method: BeginShutdown
	CIMOM appears to have exited during shutdown call

If the manual migration fails, error messages are displayed in the migration results. Table 1 describes the all the possible error messages that are generated when user account migration fails.

Table 1. Error messages for user account migration and resolutions
Migration Error	Resolution
Customization property file <****> is not present.	Indicates a minor migration problem that does not need to be resolved.
Invalid hostname: "https://1.1.1.1.1"	Enter the current IP address and protocol for the cluster.
ERROR: Could not find the file <***>	Indicates that the password or role file does not exist in the specified backup directory.
Exception in thread "main" org.sblim.wbem.cim.CIMTransportException: EXT_ERR_UNBLE_TO_CONNECT; nested exception is:	Indicates the connection problem to the cluster. This error can occur if there is a network connection problem or if the username or password is not valid. Verify your connection and username and password information.