IBM Systems Director V6.1 has been greatly enhanced to improve the usability of the product and is thoroughly restructured to provide a core base of management functions that easily accept functional plug-ins to enhance the manageability features. With these enhancements to the product, the typical migration path from IBM Systems Director V5.20 to the new Systems Director V6.1 is more complex than past migrations. To assist customers, IBM has developed and delivered a Migration Tool product that will assist in the migration effort. This article describes the key areas of data that must be recorded from the IBM Systems Director 5.20 code base, the best ways to capture the data, and the steps to migrate the data into the Systems Director V6.1 code base.
The IBM Systems Director Migration Tool can be used to migrate data only from IBM Systems Director V5.2 to a new installation of IBM Systems Director V6.1. Currently, this tool is only supported on the AIX®, Linux®, and Windows® operating systems. This article focuses on the AIX operating system. The scenario described in this article was tested using IBM Systems Director V5.20.2 on AIX V5.3 (5300-07-09-0920) and IBM Systems Director V6.1.1.1 on AIX V6.1 (6100-03-01-0921).
The process of migration is summarized in the following five steps:
- Migration planning
- Obtaining and installing IBM Systems Director V6.1
- Obtaining and installing IBM Systems Director migration tool
- Exporting data from IBM Systems Director V5.2
- Importing data into IBM Systems Director V6.1
The IBM Systems Director migration tool is used to migrate data from IBM Systems Director V5.20 to a new installation of IBM Systems Director V6.1. Both the IBM Director V5.20 system and the IBM Systems Director V6.1 systems must be running the same operating system on the same platform. However, care should be taken to ensure that IBM Systems Director V6.1 and IBM Systems Director V5.2 are installed on separate machines.
Obtaining and installing IBM Systems Director V6.1
Hardware and software requirements
IBM Systems Director on IBM Power Systems™ require IBM AIX V5.3 (supports TL06 Service Pack 4 or later) or IBM AIX V6.1 (supports TL01 Service Pack 1, or later).
Installing Common Agent on AIX
The agent installation package for AIX is a newer version than the one packaged with IBM Systems Director Server for AIX. Hence, it is recommended that you install the agent package before installing IBM Systems Director Server to ensure that the old agents are not installed as part of IBM Systems Director Server. If an agent with a lower version is installed on the server, it should be removed before installing the new agent.
The installation package for the Common Agent is available from the IBM Systems Director Downloads site (Refer Resources section). Download the installation package and extract the contents.
gzip -cd package_name | tar -xvf - |
where package_name is the file name of the download package.
To install the Common Agent, change to the folder where the installation package was unzipped and run the following command:
./dir6.1.0.3_commonagent_aix_vios.sh |
This command installs the Common Agent with the default settings. However, if the installation needs to be customized, the custom values should be provided as input for the install script in the form of a response file.
Run the following command to do a custom install:
./dir6.1.0.3_commonagent_aix_vios.sh -r response_file_path/response.rsp |
where response_file_path/response.rsp is the location for the response file.
Installing IBM Systems Director Server V6.1 on AIX
Download the installation package from the IBM Systems Director Downloads Web Site. The installation package is available from the IBM Systems Director Downloads site (Refer Resources section). Download the installation package and extract the contents as follows.
gzip -cd package_name | tar -xvf - |
where package_name is the file name of the download package.
To install the Director Server change to the folder where the installation package was unzipped and run the following command:
./dirinstall.server |
This command installs the Director Server with the default settings. However, if the installation needs to be customized, the custom values should be provided as input for the install script in the form of a response file.
Run the following command to do a custom install:
./dirinstall.server -r response_file_path/response.rsp |
where response_file_path/response.rsp is the location for response file.
Configure the agent manager to complete the installation of the director server:
/opt/ibm/director/bin/configAgtMgr.sh |
The following list shows a set of sample answers that were provided in our environment:
Enter the Resource Manager user ID that you would like to set for your Agent Manager: root-
Enter the Resource Manager password to set for your Agent Manager: < password > -
Verify the Resource Manager password to set for your Agent Manager:< re-enter password > -
Enter the Agent Registration password to set for your Agent Manager: < password > Verify the Agent Registration password to set for your Agent Manager: < re-enter password >-
Would you like to use an existing Agent Manager (yes or no)?< no >
Start IBM Systems Director by running the following command:
/opt/ibm/director/bin/smstart
To check the status of the Director Server run the following:
/opt/ibm/director/bin/smstatus -r
If the Director Server is running, this command returns Active.
Updating IBM System Director V6.1 to V6.1.0.2 or later
The Update manager utility can be used to obtain and install updates for IBM Systems Director. Ensure that you have collected the latest inventory for the IBM Systems Director Server.
To update IBM Systems Director, complete the following steps:
- Click the View updates link on the Welcome page in the upper-right corner.
- Click Check for updates to run or schedule a check for new updates. When the check for updates completes, the updates needed by the IBM Systems Director Server will be displayed in the table.
- Restart the server.
If your management server does not have a connection to the Internet, you can download IBM Systems Director updates from the IBM Fix Central Website (Refer to the Resources section). On the Fix Central page, select IBM Systems Director from the product drop-down list, select 6.1 for the version, and All for platforms and continue. On the next page, select the fix group that you would like to download, such as SysDir6_1_1_1. Also, make sure that the Include prerequisites and co-requisite fixes (you can de-select the ones you don't need later) option is selected and continue.
- Select I agree if you agree to the terms and conditions and download the updates.
- Copy the updates to the management server and use the update manager Import updates task to import the updates.
- From the View updates panel, select all updates and select the Install button to start the install wizard.
- Restart the server.
Obtaining and installing IBM Systems Director migration tool
The IBM Systems Director migration tool can be downloaded from the Web. Refer to the Resources section for download information. The migration tool is a zipped file named "IBMSystemsDirectorMigrationTool_6.1.zip," which contains the files migration-5.20.zip, migration-6.1.zip, and readme.txt. The migration-5.20.zip file should be copied to the IBM Systems Director V5.20 management server and the migration-6.1.zip file should be copied to the IBM Systems Director 6.1 management server.
The IBM Systems Director migration tool is used to migrate data from IBM Systems Director V5.20 to a fresh installation of IBM Systems Director V6.1. The IBM Systems Director V6.1 system to which the data should be migrated must be a fresh installation that has been updated to version 6.1.0.2. This update is performed from within IBM Systems Director V6.1 and requires that the system running IBM Systems Director V6.1 be discovered. After IBM Systems Director V6.1 has been upgraded, the data must be reset by running the smreset command from the command line.
The IBM Systems Director migration tool is a command-line utility that provides two commands, smexport and smimport. The smexport command is used to export IBM Systems Director V5.2's persistent data for migration to IBM Systems Director V6.1. The smimport command is used to import IBM Systems Director V5.2's persistent data for migration into IBM Systems Director V6.1.
The following data is migrated by the IBM Systems Director migration tool:
- Active Energy Manager data
- Configuration profiles
- Events
- Groups
- Level 0 agents
- Level 1 agents
- Level 2 agents
- Platform objects
- Relocation manager
- Virtualization manager
- Security
- SNMP devices
- Storage
- System status and health
- Updates
The data that is not migrated using the IBM Systems Director migration tool is shown below:
- Event logs
- Event subscriptions
- Inventory
- Process Monitors that are targeted to specific resources
- Resource Monitors and Resource Monitor tasks
- Group thresholds
- Update profiles used by update manager
- The updatePlatforms.txt file
Exporting data from IBM Systems Director V5.2
The smexport command is used to export IBM Systems Director V5.20 data to a directory. This data can be loaded onto a new IBM Systems Director V6.1 system.
The migration procedure assumes that the export portion of the IBM Systems Director migration tool is already unzipped in a local directory in the IBM Systems Director V5.2 Management Server that you are planning to migrate. This location will be referred to as "migration-tool-install" for the rest of this article. Before starting with the migration, the director server should be stopped and the data backed up. The twgstop and twgsave commands, respectively, can be used for stopping and backing up the data. Once the backup is completed the director server should be restarted again using the twgstart command.
Once the data backup is completed, the data can be exported. To export IBM System Director V5.20 data on an AIX system, run the smexport script in the migration tool package. Before running this command, ensure that the smexport command has the necessary execute permission. If it is not, execute permission should be provided to this file:
chmod 755 migration-tool-install/bin/smexport |
Run the smexport command. This command may take a long time to complete, depending on the amount of data to be exported:
migration-tool-install/bin/smexport -a |
If the command completes successfully, the migrated data will be available in the migration-tool-install/migration/DMIGXXXX directory, where DMIGXXXX will start from DMIG0000 and will be incremented by one for each invocation of the smexport command.
A log file, migration.log, is generated in the directory migration-tool-install/migration. Verify the log file to ensure that no errors occurred during the migration process. If there is no error reported in the log file, the exported data can be transferred to the freshly installed IBM Systems Director V6.1 Management Server using any standard copy program such as FTP. If the smexport command failed to export the data, reviewing the log file can provide additional information about the command failure.
Importing data into IBM Systems Director V6.1
The smimport command is used to import data from IBM Systems Director V5.20 that has been stored in a directory to a new IBM Systems Director V6.1 system. Prior to running the migration command, ensure that the IBM Systems Director patch 6.1.0.2 or later is applied. If not already done before, discover and unlock the operating system endpoint for the system that IBM Systems Director V6.1 is running on. After unlocking the server, log out of the Director Server. Run the smstop command to stop the IBM Director Server. After the IBM Systems Director server has completely stopped, run the smreset command to return IBM Systems Director Server to its installation default values. Once the reset command completes, restart the IBM Systems Director Server running the smstart command.
After the server has restarted, log in to the Director V6.1 Server and set the Auto Rename feature for the servers to no using the following steps:
- Select Settings from the GUI menu on the left.
- Select Auto Rename.
- Select Server and click the Edit button.
- Select No for auto rename after discovery.
- Save and close the menu and exit out of the Web interface.
Copy the exported data to the IBM Systems Director V6.1 management server using any standard copy program such as FTP to the following location: migration-tool-install/migration/.
To import IBM System Director V5.20 data to the new IBM Systems Director V6.1, run the smimport script in the migration tool package. Before running this command, ensure that the smexport command has the necessary execute permission. If it does not, execute permission should be provided to this file:
chmod 755 migration-tool-install/bin/smimport |
Run migration-tool-install/bin/smimport -a
command to import the data.
In order to import the migrated data into the new server from any location other than the default migration-tool-install/migration/ folder, use the parameter "-d" along with the smimport command:
migration-tool-install/bin/smimport -a -d migrated_data_location |
If the migration tool successfully completed the import of the data into
the new server, the message Migration tool processing
completed. will be displayed. If not, the migration.log file
should be analyzed to identify the error and the smreset and import
steps should be repeated.
Restart the IBM Systems Director Server V6.1 using the smstop and smstart commands.
Ensure that the /var/lock/subsys/lwi lock file doesn't exist before restarting the server. If the lock file is present, delete it before restarting the server.
The migration utility for both IBM Systems Director Server V5.20 and IBM Systems Director V6.1 can be uninstalled by deleting the migration-tool-install folder and its files.
Learn
- Learn about
Installing Common Agent on AIX
- See
Preparing
to install Common Agent on AIX to ensure that the requirements applicable to your system have been met.
- See
Preparing
to install IBM Systems Director Server on AIX to ensure that your management server meets the applicable requirements.
- For more information, see
Installing IBM Systems Director Server on AIX
-
IBM Systems Director Migration Tool
Get products and technologies
-
IBM Systems Director Downloads Web Site
-
IBM Systems Director Migration Tool Downloads Web Site
-
IBM Fix Central Web Site
Discuss
- Follow developerWorks on Twitter.
- Get involved in the My developerWorks community.
-
Participate in the AIX and UNIX forums:
- AIX Forum
- AIX Forum for developers
- Cluster Systems Management
- IBM Support Assistant Forum
- Performance Tools Forum
- Virtualization Forum
- More AIX and UNIX Forums

Bobichan P. John is an Advisory Software Engineer with 11 years of experience, of which 9 have been with IBM India. He has experience in requirement gathering, architecting, and designing software solutions and has done object-oriented analysis and design, SOA based design, development, and testing.

Biju T. Maniampadavathu has been with IBM for the last 10 years and is an Advisory Software Engineer at IBM India Software Labs (ISTL), Bangalore. Biju is currently focusing on the end to end testing of XSeries servers as part of the xPET initiative. Biju also works with the platform evaluation of _-Series servers as part of the pPET project. Prior to this, Biju has worked on Problem Determination solutions for the Distributed Computing domain, internationalization of host access products, and Java-based middleware technologies. Biju holds Masters Degrees in Computer Applications from NIT Calicut and Computer Science from Pace University, New York.
Comments (Undergoing maintenance)





