If you are already using an earlier release of IBM Spectrum Connect, you can upgrade to the newer version
without having to uninstall the previous one.
Before you begin
If needed, back up the current Spectrum Control Base or Spectrum Connect database by entering the following command.
sc_configuration backup -f /var/tmp/backup -k <key value> for IBM Spectrum Connect.
Note: The backup and restore procedure is allowed within the same version only. This means that it
is not possible to back up files from Spectrum Control Base version 2.2.1 and restore them in
version 3.0.3.
If you are using RHEL 6.x, upgrade to RHEL 7.x before upgrading Spectrum Connect.
Important: RHEL 6.x is no longer supported.
Verify that the following communication ports are open to ensure network connectivity between
VMware resources, Spectrum Connect and IBM storage
systems:
8440 (vCenter, vROps and vRO servers)
7778 (FlashSystem A9000/A9000R).
22 (storage systems that run IBM Spectrum
Virtualize)
8452 (DS8000)
Note: The 8443 port remains open after the Spectrum Connect upgrade, if the previous version was
configured to use this port. If you install the software package anew, the 8440 port is used. You
can change the default TCP port at any time by running a script, as explained in Changing the Spectrum Connect communication port. Moreover, certain upgrade scenarios, such as
using SELinux, may require additional configuration steps, as detailed in Performing first-time installation of Spectrum Connect.
Make sure that the 'ibmsc' user can access the /opt/ibm
and /var/log/sc folders.
Verify the version of your current Spectrum Connect
installation. IBM Spectrum Control Base Edition versions released before version 3.0.0 cannot be
upgraded to version 3.1.0 or later. This includes the IBM Storage Integration Server releases. You
must first upgrade the earlier release to version 3.0.3 and restart vSphere Web Client. Then you can
upgrade it to version 3.1.0 or later.
Perform the following procedure to upgrade Spectrum Connect:
Log out of the Spectrum Connect GUI and close the
browser.
On the Spectrum Connect side: download the newer
installation package and the IBM_Spectrum_Connect_Signing_Key_Pub.key file,
used for the package validation. See Downloading IBM Spectrum Connect software).
Copy the installation package and the public key files to a local folder on a current Spectrum Connect server.
Go to the local folder and then use the gpg --import
IBM_Spectrum_Connect_Signing_Key_Pub.key to import the IBM® GNU Privacy Guard (GPG) public key to validate the installation files. This ensures that
the files were received from IBM and were not manipulated in
any way by a third party.
Note: Downloading the install package from a trusted, SSL-protected resource, such as Fix Central,
ensures its authenticity and integrity. However, you can mark the key as trusted by entering
gpg --edit-key "IBM Spectrum Connect Signing Key", typing the
trust command and selecting option 5.
Extract the installation package file ('* ' represents the build number) :
# tar -xzvf IBM_Spectrum_Connect-3.7.0-*-x86_64.tar.gz
Depending on the operating system type, the following files are extracted:
ibm_spectrum_connect-3.7.0-*.bin – product BIN file.
ibm_spectrum_connect-3.7.0-xxxx-x86_64.bin.asc– digital signature
file for the BIN file verification.
Enter gpg --verify ibm_spectrum_connect-3.7.0-xxxx-x86_64.bin.asc
ibm_spectrum_connect-3.7.0-xxxx-x86_64.bin to verify the digital signature of the
installation files.
Go to the extracted directory and then use the rpm -U *.rpm command to run
and install all the complementary RPM files.
Enter chmod +x ibm_spectrum_connect-3.7.0-*.bin to authorize the
installation of the product BIN file.
Enter ./ibm_spectrum_connect-3.7.0-*.bin to start the upgrade.
Note: Make sure you login as root, or use sudo for the command.
Note: During the upgrade several configuration files are overwritten by newer versions (as
illustrated by the screen output below). If these files were changed in the previous versions, you
must apply the same changes to the new files, if you want to preserve the settings.
Review the license agreement which is displayed after you
run the installation file.
Enter 1 to accept the license agreement
and complete the installation:
Press Enter to continue viewing the license agreement, or enter "1" to accept
the agreement, "2" to decline it, "3" to print it, "4" to read non-IBM terms,
or "99" to go back.
1
Preparing to upgrade [ibm_storage_integration_server] to the new [ibm_spectrum_connect]
Stopping service ibm_storage_integration_server...
Renaming old user isis to ibmsc
Renaming old group isis to ibmsc
Upgrading [ibm_storage_integration_server] to the new [ibm_spectrum_connect]
Moving rpm configuration files to IBM Spectrum Connect
3 configuration files replaced by newer versions. The original files moved to:
/opt/ibm/ibm_spectrum_connect/conf.d/ibmsyslog.conf.saverpm
/opt/ibm/ibm_spectrum_connect/conf.d/nginx/sc_nginx.conf.saverpm
/opt/ibm/ibm_spectrum_connect/conf.d/vasa1/vasa_config.ini.saverpm
Moving Django key to IBM Spectrum Connect
Moving SSL Certificate to IBM Spectrum Connect
Configuring rsyslog
Setting up nginx
Migrating database to IBM Spectrum Connect
Configuring new service [ibm_spectrum_connect]
Update SC_UUID
Upgrading the extension of all registered vCenter servers...
Adding a default vCO server instance...
Starting Celery services ... [OK]
Starting Django service ... [OK]
Unconfiguring old service [ibm_storage_integration_server]
Installation completed successfully.
Log in (see Logging in) and click Settings > About to verify that the Spectrum Connect
version number has been updated.
Figure 1. Spectrum Connect version number
To avoid unauthorized access to Spectrum Connect
via GUI, it is strongly recommended to change the default password for the
'admin' user as soon as possible, as described in Changing the password of a Spectrum Connect user.
With the Spectrum Connect update, the IBM Storage Enhancements for VMware vSphere Web Client is upgraded
automatically for all connected vCenter servers. However, the following components must be updated
manually:
Note: During upgrade, Spectrum Connect overwrites
several configuration files. The previous versions of these files are renamed and kept in their
original locations. A backup version is renamed as
file_name.pre_previous_SCB_version_number. For example,
sc_nginx.conf from Spectrum Control Base (3.0.3) installation is renamed as
sc_nginx.conf.pre_3.0.3. Table 1 specifies
the files renamed during upgrade.
Table 1. Configuration files renamed during Spectrum Connect upgrade
