This blog takes a look at how to upgrade IBM Systems Director to version 6.3.3.
In my prevoius blog entry, I highlighted some of the new features of version 6.3.3 of IBM Systems Director. In this blog entry, I'll walk through the update process.
Version 6.3.3 is an update release and, as such, there's no DVD ISO or installation archive available. To obtain version 6.3.3, you must follow the update Systems Director process provided in the Systems Director management server. Updates to 6.3.3 are supported from 6.3.0, 6.3.1, and 6.3.2.
The first step is to start the update process. Systems Director provides several ways to do this, but the easiest is probably to click the link at the top of the Systems Director home page (outlined in red):
When you click that link, Systems Director will go out to Fix Central and see if any updates are available. Once the check is complete, the list of available updates will be displayed:
Clicking Download and Install will kick off the update. Note that a dialog box will be displayed advising you that a backup of Systems Director should be made prior to the installation. If you want to do this, you'll need to cancel the update process, shut down Systems Director, and run the command smsave to save the Systems Director data.
Selecting OK from the backup advisory dialog box will display the scheduler, which lets you run the update now or schedule it for a later date/time. The status of the update can be followed through the Task Management function:
When the update is complete, a message will be displayed on the Home page indicating that Systems Director needs to be restarted for the update to take effect:
At this point, log off of the web interface and issue the smtop command to stop Systems Director, followed by the smstart command.
If the smstatus –r command is used to monitor the status of Systems Director, it should output the following:
Once Systems Director is active, logging back in and reviewing the home page should validate that the new version has been installed:
NOTE: If the update fails, check the "Defects" section of this blog entry. There are some cases in which the update needs to be applied more than once.
If your version of Systems Director server has a later release of the Common Agent than the server code itself (which is a fairly unusual situation), the update to 6.3.3 will fail. For example, if you have version 6.3.2 of the management sever but version 6.3.3 of the CAS agent, then an attempt to upgrade the management server will fail. The solution in this case is to uninstall the Common Agent from the management server prior to updating the Systems Director server code.
There are situations in which the Systems Director update might need to be applied more than once. If the update fails on the Installing updates step, check the error log for "prerequisite” messages such as the following:
In this case, the Systems Director home page will show that Systems Director needs to be restarted for updates to be applied. Shut down and restart Systems Director, then go through the update process a second time. Once all of the prerequisites are resoled (it took two updates in my case), the full update to 6.3.3 is complete and the version indication is updated on the Systems Director home page.