IBM Information Archive Version 2.1.0.1 Readme

Readme file for: IBM® Information Archive®
Product/Component Release: 2.1.0.1
Update Name: Not applicable
Fix ID: ia-2.1.0.1_upgrade
Publication Date: 4 May 2011
Last modified date: 4 May 2011

Contents:

Download location. 1

Prerequisites. 2

Management console server 2

RSM server 3

Corequisites. 5

Upgrade preparation: 6

Enhanced Remote Mirroring. 6

Downloading files. 6

Preparing the appliance. 7

Running the upgrade. 8

Installing the optional Index and Search feature. 9

Installing the co-requisite firmware updates. 9

Performing necessary tasks after upgrade. 9

Management console server 9

Information Archive Administrative interface. 9

DS Storage Manager: Verify the Storage LUNS are on the “preferred path”. 10

IBM Systems Director 11

RSM for Storage server: 12

Management Console Server 12

Known problems and workarounds. 13

Appendix A: Resolving “Not on Preferred path” errors. 13

Copyright and trademark information. 14

Document change history. 15

Download location

You must download and install the following files to upgrade to Information Archive version 2.1.0.1:

·         ia-2.1.0.1_upgrade1.zip

·         ia-2.1.0.1_upgrade2.zip

Download these files from the following location :
http://www.ibm.com/systems/support/storage/disk/InformationArchive

Prerequisites

Before you start the Information Archive 2.1 upgrade, complete the following steps:

Management console server

1)      Current IA version: Ensure that your appliance is running Information Archive version 1.2 or higher. To view the appliance code level:

a)      Log onto the Information Archive administrative interface.

b)      In the Suite Name table on the Welcome page, click IBM Information Archive.

c)      On the About page, expand the Appliance Details section. The Release row in the table shows the code version. Write down this version number for use in later sections of this upgrade readme.

2)      Initial Configuration Wizard (ICW): The ICW must have been run before you can upgrade the appliance. For instructions, see the Installing and Configuring IBM Information Archive publication.

a)      If you configure the appliance for file archive collections, you might see the following message in the ICW:
CTJIW0151W The following IP addresses are already in use: <server_IP_addresses>. Specify different IP addresses and retry the action.
This message might occur even though the IP addresses are not actually in use.

Action: Click Finish again. If the error message is not shown, the IP addresses are not in use and the initial error can be safely ignored.

If the error message is shown again after clicking Finish the second time, the IP addresses are in use and you must specify different IP addresses.

b)      This information is also described in IBM Technote 1470833. Review this technote in case additional details have been added to it since this README was published:
https://www-304.ibm.com/support/docview.wss?uid=swg21470833

3)      Domain name and Primary Domain Name Server (DNS) fields:
Ensure that a domain name and primary DNS server are specified for the appliance. To verify or add these values, complete the following steps in the Information Archive administrative interface:

a)      In the navigation tree, click System Management.

b)      In the General Settings section of the Appliance Overview page, click Properties.

c)      In the properties notebook, open the IP Settings page and ensure that a value is specified in the Domain Name and Primary DNS Server fields.

d)      If a domain name does not exist in the Domain Name field:

i)        Enter a domain name.

ii)       If your network is not configured with a domain name, enter “example.domain.com” as a domain name.

e)      If an IP address is not specified in the Primary DNS Server field:

i)        Enter a primary DNS server IP address.  

ii)       Note: if your network does not use a DNS server, enter the IP address of the management console server.

f)        If you changed the Domain name or Primary DNS Server fields, click OK or Apply to save the changes.
Note: When you click OK or Apply, the following message might be shown:
CTJIM1000E: An unidentified error occurred: ‘the host name, iarsm1 was not found in /etc/hosts ‘.
If this message is shown, click OK or Apply again to save the configuration changes.

g)      This information is also described in IBM Technote 1444585. Review this technote in case additional details have been added to it since this README was published:
https://www-304.ibm.com/support/docview.wss?uid=swg21444585

RSM server

Ensure that values are configured correctly in the Connection Information page:

1)      To verify or add these values, log on to the RSM for Storage GUI in one of the following ways:

a)      Using the administrative interface:

i)        Log on to the administrative interface.

ii)       Expand Information Archive Management in the navigation tree.

iii)     Click Service Tools.

iv)     Click Open Remote Support Manager.

b)      Using a direct connection:

i)        Access the IBM Information Archive keyboard video mouse (KVM) console.

ii)       Press the PrtSc key to open the KVM console menu. Select iarsm1 to connect to the RSM for Storage server.

iii)     Log on to the RSM for Storage server with the admin user ID and password.

iv)     Click the Manage icon on the server desktop to open the RSM for Storage interface.

v)      Click any link to receive a logon prompt.

2)      Navigate to the Connection Information page.

a)      Click Update System Configuration

b)      Click Connection Information

c)      The first field in the Connection Information page is “IP address of SMTP server, or DIRECT”.

i)        If the value of the field is “DIRECT” continue to the “Remote Access Connections” step.

ii)       If the field contains an IP address, verify that the IP address can be successfully pinged. For example:

(1)   Open a Konsole session

(2)   Run the command: ping –c 2 <IP_address>
where <IP_address> is the address that is shown in the “IP address of SMTP server, or DIRECT”” field. For example:
iarsm1:~ # ping –c 2 9.12.34.567

(3)   If the ping command is successful, it will include two lines that look similar to this:
64 bytes from <IP_address>: icmp_seq=1 ttl=126 time=0.354 ms

(4)   If the ping command is not successful, it might include a “Destination Host Unreachable”, “100% packet loss”, or “unknown host” message:

(a)    Record the current IP address in this field so you can restore the value after the upgrade

(b)   Change the field contents to: DIRECT

iii)     Continue to the Remote Access Connections step

d)      Remote Access Connections: In the Remote Access Connections section, ensure that the “For a remote SSH” connection table is completed. The field “External IP Address IBM should use:” must contain a value. By default, the following address is configured: 172.31.3.250. If remote access has been enabled, this field might contain the external IP address of the RSM for Storage server.

i)        If this field does not contain a value, use 172.31.3.250. This IP address cannot be used for external SSH access, but allows the Information Archive upgrade to run on the RSM for Storage server.

ii)       Note: Although the "External IP Address IBM should use" field is optional for the RSM for Storage application itself, Information Archive requires a value in this field so that the appliance can communicate with the RSM for Storage server using its internal SSH network.

e)      If you modified the contents of any field in the Connection Information window, click the Update Configuration button at the bottom of the Connection Information page

Corequisites

Check the current IA version that you obtained in the Management console server section of this upgrade readme.

If the current IA version is 2.1.0.0 (or is at a level of 2.1.0.0 where additional 2.1.0.0 e-fixes have been applied):

·        The co-requisite firmware updates for the System x servers and Fibre Channel switches will have either been installed at the factory or they will have been updated as a required part of an upgrade to 2.1.0.0.

·        You do not need to have ECA 001 installed after the upgrade to 2.1.0.1 completes.

If the current IA version is 1.2.<x>, where <x> is a fix-level of IA 1.2:

·        You must contact IBM to arrange for the co-requisite firmware updates for the System x servers and Fibre Channel switches. These updates must be applied by an IBM service representative after you upgrade the software and before the appliance can be used at the 2.1 level.

·        IMPORTANT:  When you contact IBM, request the installation of Machine Type 2231 ECA 001. Depending on the number of servers in the appliance, the firmware update can take several hours to complete after the software is upgraded. It is imperative that you coordinate this update well in advance of starting the software upgrade.

Upgrade preparation:

Enhanced Remote Mirroring

If you are using an Enhanced Remote Mirroring (ERM) configuration, you must upgrade both of the mirrored appliances. Upgrade the secondary appliance first. After the secondary appliance is successfully upgraded, upgrade the primary appliance. The upgrade instructions apply for both the primary and secondary appliances.

Downloading files

Before upgrading Information Archive, complete the following steps:

1)      Download the following compressed files from the IBM support website:

a)      ia-2.1.0.1_upgrade1.zip

b)      ia-2.1.0.1_upgrade2.zip

2)      Verify the download by checking the MD5 sum of each of these compressed files against the value in the md5sum.txt file.

3)      If you have purchased a license for the optional Index and Search feature, download the license installation file from the IBM Passport Advantage website or order an installation DVD from the website. You can install this feature after running the 2.1 upgrade or at a later time.

4)      Burn the upgrade files to a DVD or transfer them to another form of media that can be mounted on the management console server. For example, you can use a USB flash drive.

Preparing the appliance

1)      Schedule a time to stop all I/O activity during the upgrade. The software upgrade takes four to six hours to complete. The firmware upgrade takes several additional hours. Contact IBM to determine the specific amount of time required to complete the firmware upgrade.

2)      Transfer the following compressed packages to the management console server in the appliance using the method of your choice:

a)      ia-2.1.0.1_upgrade1.zip

b)      ia-2.1.0.1_upgrade2.zip

3)      Log on to the Information Archive administrative interface with a user account that has the IA System Administrator role assigned and complete the following steps from the System Management page:
Important: These steps do not apply for the secondary appliance in an Enhanced Remote Mirroring configuration.

a)      Suspend all collections.

b)      Put each cluster node into maintenance mode.

4)      Log on to the management console server with the iaadmin user ID and password

5)      Right-click the desktop and click xterm to open a command prompt

6)      Complete the following steps from an xterm command line:

a)      Verify the file transfer by checking the MD5 sum of each of these compressed files against the value in the md5sum.txt file.

b)       Extract the contents of the upgrade packages to the / tmp directory. It is important that the files be extracted using the iaadmin user ID. For example:
iaadmin@iamconsole1:/tmp> unzip ia-2.1.0.1_upgrade1.zip
iaadmin@iamconsole1:/tmp> unzip ia-2.1.0.1_upgrade2.zip

c)      If no collections have been created, turn off all tracing by using the ia_service.py command on the management console server. For example:
iaadmin@iamconsole1:/tmp> /opt/ tivoli/tiam/bin/ia_service.py -r trace -c gpfs -l disable

If any collections exist, skip this step.

Running the upgrade

Important: If the current IA version that you recorded in the Corequisites section is 1.2.<x>, where <x> is a fix-level of IA 1.2: After you upgrade the software, an IBM service representative must upgrade the appliance firmware. Arrange for the IBM service representative to arrive at your location approximately four hours after you start this procedure.

If the current IA version is 2.1.0.0 (or is at a level of 2.1.0.0 where additional 2.1.0.0 e-fixes have been applied), you do not need to have ECA 001 installed after the upgrade.

1)    To start the upgrade, run the following steps from an xterm command line on the management console server.

a)    Change to the directory that was created when you extracted the upgrade packages. For example:
iaadmin@iamconsole1:~> cd /tmp/ia-2.1.0.1

b)      Run the iaupgrade.sh script from this directory. For example:
iaadmin@iamconsole1:/tmp/ia-2.1.0.1>
/opt/tivoli/tiam/bin/iaupgrade.sh

c)      When prompted, enter the iscadmin password.

d)      You will be prompted to continue the upgrade. If any warnings are shown during the prerequisite check, consider resolving these issues before you proceed. When you are ready to proceed , type "Y" and press Enter.

Tip: If a message is shown that says the upgrade process is unable to restart one or more servers, follow the instructions in the message to manually restart the servers.
Tip: Do not press Enter more times than necessary during the upgrade because this can inadvertently cancel the upgrade process. If this occurs, restart the upgrade by repeating step 2.

2)      When the upgrade is complete, the following message is shown:
Upgrade completed successfully
After this message is shown, the management console server is automatically restarted.

3)    After the management console server restarts:

a)    Log on to the server with the iaadmin user ID and password

b)    Open an xterm window.

c)      Run the iaversion command from the xterm window. For example:
iaadmin@iamconsole1:~> iaversion

d)      Ensure that the correct version number is shown in the command output: 2.1.0.1

Installing the optional Index and Search feature

The Index and Search feature is available as a separately licensed package. If you have purchased the license and downloaded the installation package, use the QuickStart Guide to install the feature after the upgrade to 2.1.0.1 finishes. You can also install the Index and Search feature at a later time.

Installing the co-requisite firmware updates

If the “Current IA version” that you recorded in the Corequisites section is 1.2.<x>, (where <x> is a fix-level of IA 1.2):

·        The co-requisite firmware updates for the System x servers and Fibre Channel switches (Machine Type 2231 ECA 001) must be installed by an IBM service representative at this time. Ensure that the IBM service representative has updated the firmware and started the appliance components before you continue to the next section.

Performing necessary tasks after upgrade

After the Information Archive 2.1 software upgrades and firmware updates are installed, complete the following steps.

Management console server

1)      Log on to the management console server with the iaadmin user ID and password.

2)      For a primary appliance of a mirrored pair: If the upgrade was done on the primary appliance and mirroring was suspended before the upgrade:

The upgrade automatically resumes the mirror. If you do not want mirroring to continue, you must suspend mirroring again after the upgrade.

Important: Suspend the mirror before resuming collections in the following steps.

Information Archive Administrative interface

If the primary DNS server value was “empty” in the appliance properties “IP settings” panel before the upgrade and was reset to use the management console server IP address in preparation for the upgrade, it must be cleared before resuming collections.

Complete the following steps to clear the DNS server value:

Important: Clear the DNS value only if you modified the DNS setting before the upgrade:

1)      Log on to the Information Archive administrative interface with a user account that has the IA System Administrator role assigned.

2)      In the navigation tree, click System Management.

3)      In the General Settings section of the Appliance Overview page, click Properties.

4)      In the properties notebook, open the IP Settings page.

5)      Clear the Primary DNS server field and click OK or Apply.

DS Storage Manager: Verify the Storage LUNS are on the “preferred path”

During an upgrade to version 2.1.0, the SAN switch firmware and SAN switch configuration is updated and resets the switch. The software might not switch the drive back to its preferred path, which causes the 'Logical Drive Not On Preferred Path' error. This error can cause performance issues and might prevent SAN switch firmware updates if the switch detects the “Not on Preferred Path” error. To determine if the storage units have this condition:

1)      Log on to the management console server with the iaadmin user id.

2)      Open the DS Storage Manager interface:

a)      Right-click the desktop and click xterm

b)      When the xterm window opens, enter the following command: sudo SMclient For example:
iaadmin@iamconsole1:~> sudo SMclient

Note: If a message is displayed that includes this text:
“unable to open display “:0.0”

start an X Windows session with this command:
ssh –X iaadmin@iamconsole1

Then run the sudo SMclient command again.

3)      When the IBM System Storage DS Storage Manager window opens, click the Devices tab.

4)      If a red X is shown for any of the storage controllers in the left pane, right-click the red X and select Manage Storage Subsystem.

NOTE: If a 'Storage Subsystem Password Not Set' window opens, click No.

5)      At the top of the 'iastoragex - IBM System Storage DS ES (Subsystem Management)' window, click Storage Subsystem -> Recovery Guru.

6)      An 'iastoragex - Recovery Guru' page opens. Look under 'Summary' for the 'Logical Drive Not On Preferred Path' errors.

7)      Repeat steps 4-6 for each storage subsystem with a red X, and make note of which subsystems show the error.

8)      If any storage subsystems have this problem, follow the steps in Appendix A: Resolving “Not on Preferred path” errors

IBM Systems Director

Verify that IBM System Director reports that all servers show an Access status of “OK”. Access the IBM Systems Director logon by using one of the following methods:

1)      Using the administrative interface:

a)      Log on to the administrative interface.

b)      Expand Information Archive Management in the navigation tree.

c)      Click Service Tools.

d)      In the IBM Systems Director section, click Open IBM Systems Director.
Tips:

i)        If you are prompted to restore the last session or start a new session because the browser closed unexpectedly, click Start New Session.

ii)       If the following message is shown, select Accept this certificate temporarily for this session and click OK:
Website Certified by an Unknown Authority

iii)     If the following error message is returned, ignore the error and click OK:
Security Error: Domain Mismatch

e)      Using a direct connection:

i)        Open a web browser.

ii)       Enter the following URL:
https://name_or_ip:8422/ibm/console
where name_or_ip is the external host name or IP address of the Information Archive management console server.

2)      Log on using the iaadmin user ID and password.

3)      Select the Navigate Resources link in the left navigator

4)      Select the All Systems group in the Navigate Resources panel

5)      The management console server, all cluster node servers and the RSM for Storage server (Type: Operating System) should show an Access status of “OK”. If any of these servers shows a status of Offline, this will cause a hardware warning to be shown in the Information Archive administrative interface’s Health Monitor window.

If any servers show a status of Offline, run the following command from an xterm session on the management console server for each server that is showing offline:
iaadmin@iamconsole1:~> ia_service.py -r director -c agent -a config -n <server_name>
where <server_name> is one of:
iamconsole1
ianode1
ianode2
ianode3
iarsm1

Note that this command takes a couple of minutes to finish running and will display a message similar to this when it completes:
CTJIB1023I Command to config IBM Director completed successfully. 

RSM for Storage server:

1)      Restore any values in the  RSM for Storage application that were changed before the upgrade:
If you changed the IP address of SMTP server, or DIRECT” before the upgrade on the RSM for Storage application’s Connection information page:

a)      Log back onto the RSM for Storage application.

b)      Change the value of the IP address of SMTP server, or DIRECT” field back to its original contents, and save the configuration

Management Console Server

1)      Primary or standalone appliance: Important: The following three steps do not apply for the secondary appliance in an Enhanced Remote Mirroring configuration.

a)      Log on to the Information Archive administrative interface

b)      Resume all collections.

c)      Take each cluster node out of maintenance mode.

2)      Open an xterm prompt on the management console server and delete the directories where the upgrade files were unzipped. For example:

iaadmin@iamconsole1:~> rm - rf /tmp/ia-2.1.0.1

3)      Run the verify_wellness command from an xterm prompt on the management console server. For example:
iaadmin@iamconsole1:~> verify_wellness

To troubleshoot any errors, see the IBM Information Archive Service Guide.

Known problems and workarounds

There are no additional known problems or workarounds.

Appendix A: Resolving “Not on Preferred path” errors

WARNING:  I/O errors can occur if the following procedure is not followed correctly.

1)      After diagnosing the error using the steps in the DS Storage Manager: Verify the Storage LUNS are on the “preferred path” section, close the 'Recovery Guru' and 'Subsystem Management' windows in the DS Storage Manager interface.

NOTE: Proceed with the following steps only if the 'Logical Drive Not On Preferred Path' error appears in the DS Storage Manager interface for one or more storage subsystems.

2)      Verify that both Fibre Channel switches are operational.

3)      Stop all I/O on the affected storage subsystems.

4)      Log onto the Information Archive administrative interface with the iscadmin user ID.

5)      Click Information Archive Management > System Management.

6)      Under 'Collections', suspend all collections that are associated with the affected storage subsystems.

7)      Return to the DS Storage Manager interface, select one of the affected disk storage subsystems, right-click it, and select Manage Storage Subsystem.
NOTE: If a 'Storage Subsystem Password Not Set' window opens, click No.

8)      At the top of the 'Subsystem Management' window, click Advanced > Recovery > Redistribute Logical Drives.

9)      When prompted, select OK.
NOTE: A progress indicator is shown as each logical drive is configured to its preferred path.

10)  Close the 'Subsystem Management' window and repeat steps 7 - 9 for each affected disk storage subsystem.

11)  After the preferred-path errors are corrected on all affected disk storage subsystems, close the DS Storage Manager interface.

12)  Resume all collections that are suspended and begin I/O operations again.

13)  Close all windows.

14)  Right-click the desktop, click fluxbox menu > Exit.

Copyright and trademark information

http://www.ibm.com/legal/copytrade.shtml

Notices

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

IBM, the IBM logo, and ibm.com are trademarks of IBM Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml .

Other company, product, or service names may be trademarks or service marks of others.

THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.

Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions:

·         the Excluded Components are provided on an "AS IS" basis

·         IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

·         IBM will not be liable to you or indemnify you for any claims related to the Excluded Components

·         IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.

Document change history


Last updated : 12 June
2011

Original publication: 4 May 2011