IBM Systems Director Storage Control
Installation and User's Guide
Version 4 Release 2
IBM Systems Director Storage Control
Installation and User's Guide
Version 4 Release 2
ii
IBM Systems Director Storage Control: Installation and User's Guide
Contents
IBM Systems Director Storage Control
4.2.3 . . . . . . . . . . . . . . . . 1
IBM Systems Director Storage Control 4.2.3 overview 1
What's New for IBM Systems Director Storage
Control 4.2.3 . . . . . . . . . . . . . 1
IBM Systems Director Storage Control 4.2.3 license
information . . . . . . . . . . . . . . 2
IBM Systems Director Storage Control 4.2.3
Hardware and software requirements . . . . . 2
Planning for IBM Systems Director Storage Control
4.2.3 . . . . . . . . . . . . . . . . . 4
Hardware requirements for IBM Systems Director
Storage Control 4.2.3. . . . . . . . . . . 4
Operating system and software requirements for
IBM Systems Director Storage Control 4.2.3 . . . 4
Supported SMI-S providers . . . . . . . . 5
Installing Storage Control 4.2.1.1 . . . . . . . . 6
Uninstalling IBM Systems Director Storage Control
4.2.3 . . . . . . . . . . . . . . . . . 8
Updating Storage Control . . . . . . . . . . 8
Updating Storage Control after migrating to
managed IBM DB2 database . . . . . . . . . 9
Managing storage with IBM Systems Director
Storage Control 4.2.3 . . . . . . . . . . . 10
Using IBM Systems Director Storage Control 4.2.3
with IBM Tivoli Storage Productivity Center . . 11
Adding a device to IBM Systems Director Storage
Control 4.2.3 . . . . . . . . . . . . . 11
Removing a device from IBM Systems Director
Storage Control 4.2.3 . . . . . . . . . . 12
Monitoring health with IBM Systems Director
Storage Control 4.2.3 . . . . . . . . . . 13
© Copyright IBM Corp. 2010, 2012
Managing storage using IBM Systems Director
VMControl and IBM Tivoli Storage Productivity
Center . . . . . . . . . . . . . . .
Troubleshooting IBM Systems Director Storage
Control 4.2.3 . . . . . . . . . . . . . .
Access type for remote service access point is
wrong . . . . . . . . . . . . . . .
Cannot communicate with Storage Control after
changing the IBM DB2 password . . . . . .
Cannot communicate with Storage Control after
changing the IBM Systems Director IP address .
Discovering (or adding) a SAN Volume
Controller or a Storwize family device in large
configurations fails due to timeout . . . . .
Cannot install or uninstall Storage Control on a
Linux or AIX system . . . . . . . . . .
Cannot install or uninstall Storage Control on a
Microsoft Windows system . . . . . . . .
Cannot receive alerts from IBM Systems Director
Cannot unlock IBM Flex System V7000 Storage
Node . . . . . . . . . . . . . . .
smcli mkdatasource hangs after a date change . .
Storage Control does not work after migrating to
IBM Systems Director 6.3 . . . . . . . . .
Storage Control installation hangs on an AIX
system . . . . . . . . . . . . . . .
Storage Control operations fail with SEVERE
TPC Exception: OutOfMemoryError . . . . .
13
16
16
17
17
19
20
22
24
25
25
26
26
26
Index . . . . . . . . . . . . . . . 29
iii
iv
IBM Systems Director Storage Control: Installation and User's Guide
IBM Systems Director Storage Control 4.2.3
Use these topics to learn about Storage Control.
IBM Systems Director Storage Control 4.2.3 overview
With the Storage Control plug-in, you can manage an expanded set of storage
subsystems and Fibre Channel switches.
Important: If you are not using IBM® DB2® managed by Systems Director, then
you must use one of these versions of IBM DB2 as the local database application
for Systems Director to use Storage Control:
v IBM DB2 Enterprise Edition v. 9.7
v IBM DB2 Enterprise Edition v. 9.7 with fix pack 4
That is, the correct version of DB2 must be installed on the same system as
Systems Director. Storage Control is not supported on any other databases.
You can use Storage Control to discover, collect inventory, and monitor the health
of your storage devices. These subsystems include, but are not limited to, the IBM
DS3000, DS4000®, and DS5000 families, the IBM DS8000® family (DS8100, DS8300,
DS8700, DS8800), the SAN Volume Controller, the IBM Storwize® V7000, Storwize
V3700, Storwize V3500, IBM Flex System™ V7000 Storage Node, IBM XIV®, QLogic
8 GB Fibre Channel switch, the Brocade Fibre Channel switches, and the McDATA
Sphereon and Intrepid switches. For the list of supported devices, see “Supported
storage devices.” “Supported storage devices” does not list the specific Brocade
switch models that are supported. For the list of supported Brocade switch models,
see the 4.2.x - Switch and Director - Supported Storage Products Matrix Web page.
Depending on the firmware levels of these devices, Storage Control supports
native interfaces to the device, which simplifies configuration setup and improves
device management reliability. These interfaces use Secure Shell (ssh) credentials.
For information about configuring these credentials, see the Storage Control
commands topic.
After the devices are discovered, they are be listed as being managed by Storage
Manager in Systems Director.
Storage Control uses IBM Tivoli® Storage Productivity Center technology. As such,
several of the device support and operating environment conditions are related to
IBM Tivoli Storage Productivity Center. When you use IBM Tivoli Storage
Productivity Center with IBM Systems Director Storage Control 4.2.3, IBM Tivoli
Storage Productivity Center version 4.2.3 is recommended.
Note: When Systems Director is configured in an LDAP environment, Storage
Control uses operating system authentication to communicate with the Systems
Director server.
See the following topics for more information about Storage Control.
What's New for IBM Systems Director Storage Control 4.2.3
Storage Control has the following new and updated functions:
© Copyright IBM Corp. 2010, 2012
1
v Added a Discover Storage wizard that makes it easy and straightforward to
discover the data sources for your storage devices and subsystems so Storage
Control can communicate with them. The Discover Storage wizard also is able to
establish SSH credentials at the time of discovery for the following devices: the
SAN Volume Controller; the IBM Storwize V7000, V3500, and V3700; and the
IBM Flex System V7000 Storage Node. (The SSH credential that is established
from the Discover Storage wizard also is used by VMControl advanced
operations.)
v Added a Show Discovery Details task that you can use to display, manage, and
remove discovered data sources.
v Added the smcli lsdatasource command that lists managed data sources. For
more information about lsdatasource, from a command line, run smcli
lsdatasource -h.
IBM Systems Director Storage Control 4.2.3 license
information
IBM Systems Director Storage Control 4.2.3 comes with an evaluation license that
lasts for 90 days. At any time, you can update to a full product license.
Evaluation license
The evaluation license for Storage Control includes a 90-day trial period. You can
discover, monitor the health status of, and add and remove devices, starting on the
day that you install Storage Control. At the end of the trial period, the monitoring
functions remain operational. You can view the health and configuration of the
device and monitor its capacity and utilization, and remove the device from the
Systems Director inventory. If the permanent key is not acquired and installed after
the trial period, you cannot use Storage Control to discover and add new devices
to Storage Control.
Permanent license
To install the permanent product license for Storage Control, you import the
license key. To import the license key, navigate to the Plug-ins tab of the Home
page, and click Import License Key.
Note: The location of the license pack might vary, depending on how you installed
Storage Control.
v The version of Storage Control that is shipped on a product CD includes a
license pack. To install the license key, refer to the directions included for the
product you purchased.
v If you downloaded Storage Control, you can order a product license that
includes the license key. In this case, after the key is emailed to you, you can use
the Import License Key task to import it.
IBM Systems Director Storage Control 4.2.3 Hardware and
software requirements
These topics list the requirements for installing Storage Control.
2
IBM Systems Director Storage Control: Installation and User's Guide
Hardware requirements for IBM Systems Director Storage
Control 4.2.3
These are the minimum hardware requirements for Storage Control.
Table 1. Storage Control minimum hardware requirements
Hardware Requirements
Processor
Installed Memory
Disk Storage
3 GHz
3 GB (Total requirement for
Systems Director, DB2, and
Storage Control)
5.15 GB
For AIX® or Linux
installations, the 5.15 GB
.8 GB RAM (Requirement for must be in these directories:
Storage Control only)
v /tmp - 2.15 GB
v /opt - 2.6 GB
v /home - 400 MB
v /etc - 10 KB
Operating system and software requirements for IBM Systems
Director Storage Control 4.2.3
Before installing Storage Control, ensure that your system meets these software
requirements.
Supported operating systems
The Storage Control plug-in supports most of the Red Hat Enterprise Linux,
Microsoft Windows, and AIX operating systems that Systems Director also
supports, with these exceptions: Red Hat Enterprise Linux on Power Systems™,
Red Hat Enterprise Linux on System z® systems, and SUSE Linux Enterprise.
The specified versions of the following operating systems are supported:
v AIX
AIX 5.3, POWER4, POWER5, and POWER6®
AIX 6.1, POWER4, POWER5, POWER6, and POWER7®
AIX 7.1, POWER5, POWER6, and POWER7
v Linux RHEL Base and Advanced Platform 5 (x86-64)
v Linux RHEL Base and Advanced Platform 6 (x86-64)
v Windows
Windows 2003 Standard Edition and Windows 2003 Enterprise Edition (x86
and x86-64)
Windows 2008 Standard Edition and Windows 2008 Enterprise Edition (x86
and x86-64)
Windows 2008 R2 Standard Edition and Windows 2008 R2 Enterprise Edition
(x86-64)
For more information about the supported operating systems, see the following
web page: 4.2.x - Platform Support: Agents, Servers, and GUI.
Software requirements
IBM Systems Director 6.2.1 or higher is required in order to use Storage Control.
IBM Systems Director Storage Control 4.2.3
3
Important: If you are not using IBM DB2 managed by Systems Director, then you
must use one of these versions of IBM DB2 as the local database application for
Systems Director to use Storage Control:
v IBM DB2 Enterprise Edition v. 9.7
v IBM DB2 Enterprise Edition v. 9.7 with fix pack 4
That is, the correct version of DB2 must be installed on the same system as
Systems Director. Storage Control is not supported on any other databases.
Storage Control supports the same SMI-S providers that are supported by IBM
Tivoli Storage Productivity Center. For details, see the Help to Find the Supported
Products and Platforms Interoperability Matrix Links website.
Planning for IBM Systems Director Storage Control 4.2.3
Use the information in this section to plan for using Storage Control.
Hardware requirements for IBM Systems Director Storage
Control 4.2.3
These are the minimum hardware requirements for Storage Control.
Table 2. Storage Control minimum hardware requirements
Hardware Requirements
Processor
Installed Memory
Disk Storage
3 GHz
3 GB (Total requirement for
Systems Director, DB2, and
Storage Control)
5.15 GB
For AIX or Linux
installations, the 5.15 GB
.8 GB RAM (Requirement for must be in these directories:
Storage Control only)
v /tmp - 2.15 GB
v /opt - 2.6 GB
v /home - 400 MB
v /etc - 10 KB
Operating system and software requirements for IBM Systems
Director Storage Control 4.2.3
Before installing Storage Control, ensure that your system meets these software
requirements.
Supported operating systems
The Storage Control plug-in supports most of the Red Hat Enterprise Linux,
Microsoft Windows, and AIX operating systems that Systems Director also
supports, with these exceptions: Red Hat Enterprise Linux on Power Systems, Red
Hat Enterprise Linux on System z systems, and SUSE Linux Enterprise.
The specified versions of the following operating systems are supported:
v AIX
AIX 5.3, POWER4, POWER5, and POWER6
AIX 6.1, POWER4, POWER5, POWER6, and POWER7
AIX 7.1, POWER5, POWER6, and POWER7
4
IBM Systems Director Storage Control: Installation and User's Guide
v Linux RHEL Base and Advanced Platform 5 (x86-64)
v Linux RHEL Base and Advanced Platform 6 (x86-64)
v Windows
Windows 2003 Standard Edition and Windows 2003 Enterprise Edition (x86
and x86-64)
Windows 2008 Standard Edition and Windows 2008 Enterprise Edition (x86
and x86-64)
Windows 2008 R2 Standard Edition and Windows 2008 R2 Enterprise Edition
(x86-64)
For more information about the supported operating systems, see the following
web page: 4.2.x - Platform Support: Agents, Servers, and GUI.
Software requirements
IBM Systems Director 6.2.1 or higher is required in order to use Storage Control.
Important: If you are not using IBM DB2 managed by Systems Director, then you
must use one of these versions of IBM DB2 as the local database application for
Systems Director to use Storage Control:
v IBM DB2 Enterprise Edition v. 9.7
v IBM DB2 Enterprise Edition v. 9.7 with fix pack 4
That is, the correct version of DB2 must be installed on the same system as
Systems Director. Storage Control is not supported on any other databases.
Storage Control supports the same SMI-S providers that are supported by IBM
Tivoli Storage Productivity Center. For details, see the Help to Find the Supported
Products and Platforms Interoperability Matrix Links website.
Supported SMI-S providers
IBM Systems Director VMControl and IBM Tivoli Storage Productivity Center
support different versions of SMI-S providers.
The following table shows the levels of SMI-S providers that IBM Systems Director
VMControl and IBM Tivoli Storage Productivity Center support. For more
information, see "Managing storage using IBM Systems Director VMControl."
Table 3. Levels of SMI-S providers required
SMI-S provider
Supported storage
devices
Support in IBM
Systems Director
VMControl
Support in IBM
Tivoli Storage
Productivity Center
IBM Network
AdvisorV11
IBM Flex System
FC5022 16 GB SAN
Scalable Switch
Yes
Yes
SANtricity SMI
Provider10.19.GG.xx
DS3XXX
DS4XXX
DS5XXX
Yes
Yes
SANtricity SMI
Provider10.10.G5.02
DS3XXX
DS4XXX
DS5XXX
Yes
—
IBM Systems Director Storage Control 4.2.3
5
Installing Storage Control 4.2.1.1
Storage Control expands the number of systems and switches you can manage
with Systems Director. Storage Control 4.2.1.1 must be installed before you apply
updates, including Storage Control 4.2.3.
Storage Control is a separately downloadable and installable plug-in available on
these platforms: Red Hat Enterprise Linux (RHEL), Microsoft Windows, and AIX.
Additionally, Storage Control is available on CD or as an .iso image, and might be
included with other products.
Storage Control 4.2.1.1 must be installed before you apply updates. (Storage
Control 4.2.3 is available only as an update.) Use the following directions to install
Storage Control 4.2.1.1. For instructions on applying updates, see “Updating
Storage Control.”
Note: If you install a new version of Storage Control on top of an existing version,
your data is preserved.
The specified versions of the following operating systems are supported:
v AIX
AIX 5.3, POWER4, POWER5, and POWER6
AIX 6.1, POWER4, POWER5, POWER6, and POWER7
AIX 7.1, POWER5, POWER6, and POWER7
v Linux RHEL Base and Advanced Platform 5 (x86-64)
v Linux RHEL Base and Advanced Platform 6 (x86-64)
v Windows
Windows 2003 Standard Edition and Windows 2003 Enterprise Edition (x86
and x86-64)
Windows 2008 Standard Edition and Windows 2008 Enterprise Edition (x86
and x86-64)
Windows 2008 R2 Standard Edition and Windows 2008 R2 Enterprise Edition
(x86-64)
For more information about the supported operating systems, see the following
web page: 4.2.x - Platform Support: Agents, Servers, and GUI.
Important: If you are not using IBM DB2 managed by Systems Director, then you
must use one of these versions of IBM DB2 as the local database application for
Systems Director to use Storage Control:
v IBM DB2 Enterprise Edition v. 9.7
v IBM DB2 Enterprise Edition v. 9.7 with fix pack 4
That is, the correct version of DB2 must be installed on the same system as
Systems Director. Storage Control is not supported on any other databases.
To install Storage Control, follow these steps.
1. Ensure that Systems Director 6.3 is installed and running.
2. Ensure that you are logged in to Systems Director with a user ID that has
administrative privileges.
3. Windows only: Restart the DB2 Management server.
a. Go to Start > Administrative Tools > Services.
6
IBM Systems Director Storage Control: Installation and User's Guide
b. Select DB2 Management Service from the services window and restart it.
4. If you want to download and install Storage Control, go to step 5. If you want
to install Storage Control from read-only media, such as a CD or mounted .iso
image, go to step 8.
5. From the Systems Director summary page, click the link Try Storage Control
in the upper right corner.
6. A download page opens. Download the appropriate file for your platform.
7. Extract the files to the directory where you want to install Storage Control,
then go to step 9.
Important: The path to the installation file cannot contain more than 89
characters. The 89 characters are in addition to the name of the setup file. Do
not count the characters in the file name setup.exe as part of the path length.
8. Copy the Storage Control installer directory from the CD or the mounted .iso
image into a temporary directory close to the system root (for example,
/SCInstall for AIX or Linux and C:\SCInstall for Windows).
Note: Storage Control cannot be installed from a read-only file system
because the installation process extracts files into the same directory where the
installation script runs.
9. Access a command window and navigate to the directory where you extracted
the files or where you copied the installer directory. Run the appropriate
script. If you do not want the license agreement to display, use the -i option
when you run the script. For example, StorageControlInstall.sh -i.
Important: If you are not using IBM DB2 managed by Systems Director, then
the DB2 user ID used must have DB2 Administrator privileges.
v On Microsoft Windows systems, run the script StorageControlInstall.bat.
v On Linux and AIX systems, run the script StorageControlInstall.sh.
If you see a Java™ installation error, the working directory path is too long.
Follow the instructions in step 5 on page 23 of the following topic: “Cannot
install or uninstall Storage Control on a Microsoft Windows system” on page
22.
10. Restart Systems Director as directed.
Notes:
v If you encounter any errors as you install Storage Control, see the
appropriate troubleshooting topic.
v The TPCAdmin group is created automatically when Storage Control is
installed, and is removed during an uninstall. However, if there are any
messages related to removing the group while performing this task, use
operating system commands to remove the TPCAdmin group.
– On Microsoft Windows systems, follow these steps:
a. Go to Start > Settings > Control Panel > Administrative Tools >
ComputerManagement.
b. The Computer Management window opens. In the left pane, under
Computer Management (Local), expand Local Users and Groups.
Click Groups. The groups are listed in the right pane.
c. Delete the TPCAdmin group.
d. Close the Computer Management window and the Administrative
Tools window.
IBM Systems Director Storage Control 4.2.3
7
– On Linux, use the groupdel command.
– On AIX, use the rmgroup command.
Uninstalling IBM Systems Director Storage Control 4.2.3
To uninstall Storage Control, follow these steps. You do not need to uninstall IBM
Systems Director if you uninstall Storage Control.
1. Ensure that Systems Director 6.3 is installed and running.
2. Ensure that you are logged in to Systems Director with a user ID that has
administrative privileges.
3. Run the appropriate script. This script was copied to your system when you
installed Storage Control.
v On Microsoft Windows systems, run this script. In the script, DIRHOME is
the directory where Storage Control is installed. It is usually C:\program
files\ibm\director.
DIRHOME\StorageControl\bin\UninstallStorageControl.bat
v On Linux and AIX systems, run this script. In the script, DIRHOMEis the
directory where Storage Control is installed. It is usually /opt/ibm/director.
DIRHOME/StorageControl/bin/UninstallStorageControl.sh
A message is shown after Storage Control has been uninstalled.
Notes:
v If you already uninstalled IBM Systems Director, the UninstallStorageControl file
is deleted. However, a copy of the file is saved when you download and extract
the Storage Control files. The file is saved to the location where you extracted
the files.
v The TPCAdmin group is created automatically when Storage Control is installed,
and is removed during an uninstall. However, if there are any messages related
to removing the group while performing this task, use operating system
commands to remove the TPCAdmin group.
– On Microsoft Windows systems, follow these steps:
1. Go to Start > Settings > Control Panel > Administrative Tools >
ComputerManagement.
2. The Computer Management window opens. In the left pane, under
Computer Management (Local), expand Local Users and Groups. Click
Groups. The groups are listed in the right pane.
3. Delete the TPCAdmin group.
4. Close the Computer Management window and the Administrative Tools
window.
– On Linux, use the groupdel command.
– On AIX, use the rmgroup command.
Updating Storage Control
When there are Storage Control software quality updates or feature function
updates, an update is made available.
Storage Control updates must be applied to an existing Storage Control
installation. To install Storage Control 4.2.1.1, see “Installing Storage Control
4.2.1.1”. To apply Storage Control updates, use the following directions.
8
IBM Systems Director Storage Control: Installation and User's Guide
The procedure for updating Storage Control depends on the version that is
installed. To determine the version of Storage Control installed, open the Plug-ins
tab of the IBM Systems Director Home page and scroll to the Storage Management
section. The Storage Control version is listed in the Storage Management section.
For versions higher than 4.2.1.152:
IBM Systems Director update manager plug-in enables you to acquire, install, and
manage updates, and to monitor your systems to ensure that they remain current.
Use the IBM Systems Director update manager plug-in to update your system. For
details, see “Updating IBM Systems Director.”
For versions 4.2.1.152 and earlier:
All Storage Control software updates are contained in the Storage Control
installation package. Therefore, to update Storage Control, download the updated
version of the plug-in file from http://www.ibm.com/systems/software/director/
downloads/plug-ins.html.
1. Determine the version of Storage Control that is installed.
Open the Plug-ins tab of the IBM Systems Director Home page and scroll to the
Storage Management section. The Storage Control version is listed in the
Storage Management section.
2. Go to the Storage Control download page and download the Storage Control
4.2.1.1 plug-in.
3. Install the updated plug-in.
a. Extract the downloaded image.
Important: The path to the installation file cannot contain more than 89
characters. The 89 characters are in addition to the name of the setup file.
Do not count the characters in the file name setup.exe as part of the path
length.
b. Run the StorageControlInstall file. If you do not want the license
agreement to display, use the -i option when you run the script. For
example, StorageControlInstall.sh -i
4. Restart IBM Systems Director server.
5. Use the IBM Systems Director update manager to update Storage Control to the
latest version.
Updating Storage Control after migrating to managed IBM DB2
database
The following procedure describes the steps required to use Storage Control after
you switch to using the managed IBM DB2 database for IBM Systems Director.
This procedure applies after you migrate your data from any database, including a
stand-alone version of IBM DB2, to the managed IBM DB2 database. The required
steps include upgrading to the newest version of Storage Control and
rediscovering your managed storage devices.
Note: To use IBM Systems Director Storage Control, the database must be installed
on the management server.
IBM Systems Director Storage Control 4.2.3
9
Perform the following steps after you complete the steps required to switch to
using the managed IBM DB2 database with Systems Director. For more
information, see “Switching to the managed IBM DB2 database.”
This procedure includes the following tasks:
1. Upgrade to the latest version of Storage Control
2. Stop Storage Control
3. Start Storage Control
4. Remove the Storage Control farm
5. Discover and unlock the Storage Control farm by using a discovery profile
6. Collect inventory on the Storage Control farm
After migrating to the managed IBM DB2 database, complete the previously listed
tasks by performing the following steps.
1. Upgrade to the latest version of Storage Control (4.2.1.1 or higher). For
information about downloading and installing the latest version of Storage
Control, see the Storage Control website.
2. Stop Storage Control by running the appropriate command on the management
server, where DIRHOME is the root directory of your IBM Systems Director
installation:
v On Windows: From a command prompt, run the following command:
DIRHOME\StorageControl\bin\stopStorageControl.bat
v On AIX or Linux: From the command line, run the following command:
DIRHOME/StorageControl/bin/stopStorageControl.sh
3. Start Storage Control by running the appropriate command on the management
server, where DIRHOME is the root directory of your IBM Systems Director
installation:
v On Windows: From a command prompt, run the following command:
DIRHOME\StorageControl\bin\startStorageControl.bat
v On AIX or Linux: From the command line, run the following command:
DIRHOME/StorageControl/bin/startStorageControl.sh
4. Remove the Storage Control farm. For more information about removing a
resource, see “Removing a resource” or “rmsys command.”
5. Rediscover and request access to the Storage Control farm:
v On Windows: Run system discovery, using a resource type of Farm, then
request access to the Storage Control farm. For more information, see
“Performing a system discovery” and “Accessing a secured system with
request access.”
v On AIX or Linux: On the management server, from a command line, run the
following command, where DIRHOME is the root directory of your IBM
Systems Director installation: DIRHOME/StorageControl/bin/
SCDiscoverUnlock.sh
Note: This command discovers and automatically requests access to the
Storage Control farm.
6. Collect inventory on the Storage Control farm. For more information about
collecting inventory, see “Collecting inventory” or “collectinv command.”
Managing storage with IBM Systems Director Storage Control 4.2.3
Use the information in this section to learn how to use IBM Systems Director
Storage Control 4.2.3 to manage storage.
10
IBM Systems Director Storage Control: Installation and User's Guide
Stopping and Starting Storage Control
When IBM Systems Director is stopped or started, Storage Control is also stopped
or started.
To manually stop or start Storage Control, run the appropriate script:
On Microsoft Windows systems, run one of these scripts. In the path, DIRHOME is
the directory where Storage Control is installed. It is usually C:\program
files\ibm\director.
DIRHOME\StorageControl\bin\stopStorageControl.bat
DIRHOME\StorageControl\bin\startStorageControl.bat
On Linux and AIX systems, run one of these scripts. In the path, DIRHOME is the
directory where Storage Control is installed. It is usually /opt/ibm/director.
DIRHOME/StorageControl/bin/stopStorageControl.sh
DIRHOME/StorageControl/bin/startStorageControl.sh
Using IBM Systems Director Storage Control 4.2.3 with IBM
Tivoli Storage Productivity Center
It is possible to use both the Storage Control plug-in and a IBM Tivoli Storage
Productivity Center server for storage management. However, they cannot be
installed on the same system. The difference in these environments is where you
perform the device discovery.
For example, you can use Storage Control to manage an IBM Storwize V7000 and
use IBM Tivoli Storage Productivity Center to manage a Cisco MDS 9124 Fibre
Channel switch.
If both Storage Control and IBM Tivoli Storage Productivity Center are configured
to manage the same device, IBM Systems Director lists the device once. It will be
managed by IBM Tivoli Storage Productivity Center.
Changing from Storage Control to IBM Tivoli Storage Productivity Center
In this scenario, assume that you are currently using Storage Control to manage a
device and want to use IBM Tivoli Storage Productivity Center instead. Follow
these steps to start using IBM Tivoli Storage Productivity Center:
1. From Systems Director, run the rmdatasource command, specifying the
appropriate data source. See rmdatasource command for details.
2. Collect inventory against the Storage Control Farm.
3. Open the IBM Tivoli Storage Productivity Center interface on the other system
and add the data source. See Collecting inventory for details.
4. From Systems Director, use the Advanced Discovery task to discover, request
access, and collect inventory against IBM Tivoli Storage Productivity Center.
5. IBM Tivoli Storage Productivity Center starts managing the device.
Adding a device to IBM Systems Director Storage Control
4.2.3
To use Storage Control to begin managing a device or subsystem, use the Discover
Storage task. Using Discover Storage makes it easy and straightforward to discover
IBM Systems Director Storage Control 4.2.3
11
the data sources for your storage devices and subsystems so Storage Control can
communicate with them. You also have the option to automatically collect
inventory on the discovered devices.
The term data source describes how the storage device is managed. Some data
sources are the location of the SMI-S provider for the device. For example, the data
source for a Brocade Fibre Channel switch is the location of the SMI-S provider for
the switch. Other data sources are the device itself. For example, for the current
firmware levels of the SAN Volume Controller and IBM Storwize V7000, the device
is the data source.
If you prefer to use a command-line interface or if you need to use scripting, use
the smcli mkdatasource command. The default behavior for the mkdatasource
command is to automatically collect inventory.
To discover your storage devices, complete the following tasks:
1. On the Storage Management summary page, in the Storage Tasks area, click
Discover Storage. The Discover Storage page displays.
2. Select the type of device that you want to discover, complete the required
information, then click Discover.
Note: To discover any of the supported devices in the Storwize family, select
the option that includes the IBM Flex System V7000.
Discover Storage automatically collects inventory for any discovered devices,
although you can choose not to collect inventory.
Note: After inventory is collected, inactive zone members that were created by
using a zone alias instead of WWPN are not shown.
Removing a device from IBM Systems Director Storage
Control 4.2.3
To stop using Storage Control to manage a storage device, use the Show Discovery
Details page to delete the associated data source.
Usually, you delete a data source only if you also physically remove the associated
storage device.
Note: If you prefer to use a command-line interface or if you need to use scripting,
use the smcli rmdatasource command.
To remove a storage device or subsystem (by deleting the associated data source),
complete the following tasks:
1. In any table that lists the resource that you want to remove, right-click the
resource, then select Show Discovery Details. The Show Discovery Details page
displays.
2. In the Data Source table, select the data source that you want to delete, then
click Delete. Storage Control can no longer communicate with the data source,
and the data source is removed from IBM Systems Director.
Note: Deleting a data source by using Show Discover Details automatically
collects inventory after the deletion completes. Collecting inventory is a
necessary step to ensure the complete cleanup of devices and information that
is associated with the deleted data source. If you use the rmdatasource
command, you need to manually collect inventory.
12
IBM Systems Director Storage Control: Installation and User's Guide
Monitoring health with IBM Systems Director Storage Control
4.2.3
You can use Storage Control to monitor the health of storage subsystems, storage
pools, storage volumes, and fabric switches. Run the inventory against the Storage
Control farm to see updated health status.
Follow these steps to retrieve the health and alert status for the devices that are
managed by Storage Control.
1. Select Resource Explorer > All Systems. Select the managed device for which
you want to get the latest health and alert status.
2. Discover and then unlock the device.
Note: At this point, TPC alerts are received from the farm, but not alerts
specific to any devices under this farm.
3. Select the farm that covers the selected device and collect inventory against it.
4. For DS3000, DS4000, and DS5000 TPC devices only: Under the farm,
right-click the DSnnnn device, and select Collect inventory.
Important: You must repeat this step each time you want to check for an event
on these devices.
5. TPC alerts for devices under the farm are now received.
The managed device has one of these alert levels:
Normal
The device is running normally. The Problems column shows a green
square and says “OK”.
Warning
The device has an issue that must be fixed. For example, the SAN Volume
Controller cluster might be turned off. The Problems column shows a
yellow triangle with an exclamation point and says “Warning”.
Critical
The device is not working. The Storage Control and storage system
administrators need to work together to resolve the issue. The Problems
column shows a red circle with an “x” in it, and says “Critical”.
If your device is not running normally, access its management interface for more
details about the error. You can launch the management interface for some devices
from the Systems Director user interface. For instructions, see the topic “Launching
an external storage management application.”
For example, assume that you are monitoring the status of a IBM Storwize V7000
system. If the system is working normally, the cluster nodes and storage volumes
are functioning and the health and alert status would be Normal. If you shut
down one of the cluster nodes, the health status of the IBM Storwize V7000 system
would be Critical.
Managing storage using IBM Systems Director VMControl and
IBM Tivoli Storage Productivity Center
IBM Systems Director VMControl enables you to use IBM Tivoli Storage
Productivity Center to manage your enterprise storage systems.
IBM Systems Director Storage Control 4.2.3
13
IBM Systems Director VMControl uses the remote API capabilities of IBM Tivoli
Storage Productivity Center 4.1 (and later releases) to collect inventory on and
provision your storage system, which creates seamless and integrated storage
management. IBM Tivoli Storage Productivity Center Basic Edition is required for
certain types of storage subsystems, such as DS8000 and SAN Volume Controller.
No other components of IBM Tivoli Storage Productivity Center are required for
storage management integration with VMControl.
To use this capability, you must first install and configure an IBM Tivoli Storage
Productivity Center server for your storage system, which includes the storage
controllers as well as their fibre channel switches. You have options for discovering
the server depending on the server configuration.
To use IBM Tivoli Storage Productivity Center to provision storage such as DS3000,
DS4000, and DS5000, ensure that you use a supported provider. For information
about supported providers, see "Supported SMI-S providers" and "4.1.x Supported Storage Products List."
VMControl support of NPIV requires either the use of IBM Systems Director
Storage Control 4.2.3, or IBM Tivoli Storage Productivity Center 4.2.1 or higher. If
usingIBM Tivoli Storage Productivity Center, both the SMI-S and SNMP services of
the fibre channel switch must be discovered and successfully added as data
sources to the IBM Tivoli Storage Productivity Center server.
If you want IBM Systems Director VMControl to access all the storage controllers
and fibre channel switches that IBM Tivoli Storage Productivity Center is
managing without limiting the management to specific resources using a storage
resource group (SRG), you can use basic system discovery. This method of system
discovery requires that your server meets the following configuration
requirements:
v IBM Tivoli Storage Productivity Center was installed using default values.
v The IBM Tivoli Storage Productivity Center DB2 administrator password
matches the IBM Tivoli Storage Productivity Center user ID password.
If the server meets the previous criteria, complete the following steps to discover
it.
1. On the IBM Systems Director Home page Start tab, click System Discovery.
2. On the System Discovery page, complete the required fields and click Discover.
If you want IBM Systems Director VMControl to access only a specific group of
resources, create a storage resource group (SRG) in IBM Tivoli Storage Productivity
Center for the resources that you want to use. You must include valid storage
subsystems and fabrics configurations. If the switches are configured without the
fabric, all of the zoning configuration information is unavailable in IBM Systems
Director. After the storage resource group is created, use system discovery in IBM
Systems Director to discover the IBM Tivoli Storage Productivity Center server.
IBM Systems Director VMControl isolates its activity on the server to just those
resources in the identified storage resource group, which provides access control
across these two software managers.
You can discover the IBM Tivoli Storage Productivity Center server with a
customized storage resource group by creating a discovery profile, which captures
the details about your IBM Tivoli Storage Productivity Center server.
14
IBM Systems Director Storage Control: Installation and User's Guide
Note: It is recommended that only one discovery profile is created for a server and
its associated storage resource group. If multiple profiles exist, only the first
applied profile is used. If you want to change the SRG contents, use the server to
edit and modify the storage resource group equipment membership. Then collect
inventory for the farm to discover the new equipment that you added to the SRG.
1. On the Start tab of the IBM Systems Director Home page, click System
Discovery.
2. On the System Discovery page, click Create new profile to launch the
Discovery Profile wizard.
3. Complete the wizard using the following information:
a. On the Profile Properties page, specify a name for the profile and select
Farm for the System type and All for the System subtype. Click Next.
b. On the Protocol Selection page, select Tivoli Storage Productivity Center
(TPC) Discovery. Click Next.
c. On the next two pages, specify the configuration information for your IBM
Tivoli Storage Productivity Center DB2 server and IBM Tivoli Storage
Productivity Center server.
d. On the Group Selection page, select the storage resource group that you
want to be able to work with in IBM Systems Director VMControl
e. Optional: On the Access Request page, select whether to provide credentials
for unlocking the HTTP and Telnet Remote Service Access Points (RSAPs)
on the switch.
Note: When using system discovery, switches are discovered and populated
using four Remote Service Access Points (RSAPs): SNMP, TPC, HTTP, and
Telnet. This populates all necessary properties of the switch fabrics, such as
zoning and port configuration, for IBM Systems Director. The HTTP and
Telnet RSAPs are not configured as part of the discovery process. Therefore
IBM Systems Director indicates Partial Access to the switch. This condition
does not affect the function of IBM Systems Director VMControl and can be
safely ignored. You can manually unlock the switch by providing HTTP and
Telnet credentials on this page.
f. Review your selections on the summary page and click Finish to create the
profile.
After completing the wizard, you can use the profile that you created to discover
and collect inventory on the set of storage resources that IBM Tivoli Storage
Productivity Center is managing. This includes the storage subsystem information
(storage controller, pool, volumes), as well as the fibre channel switch zone and
zoneset information. Once these resources are discovered, you can use them in IBM
Systems Director VMControl.
To update the inventory of your storage and switch resources, collect inventory on
the system you discovered using the profile you created. This system has a system
type of Farm.
Changing the default time limit for inventory collection
The default time limit on inventory collection is 25 minutes. If you have a large
IBM Tivoli Storage Productivity Center environment (more than approximately
8,000 SAN volumes), inventory collection in your environment might exceed 25
minutes. The following information describes how to change the default discovery
time limit.
IBM Systems Director Storage Control 4.2.3
15
You can increase the default discovery time limit by updating the
perf.extended.discovery.timeout property in one of the IBM Systems Director
property files. The value of this property is set in minutes. A time limit of 60
minutes is recommended if you have over approximately 8,000 SAN volumes. If
you have over 100,000 SAN volumes, then it is recommended the time limit be set
to 100 minutes.
In addition to the SAN volume, also consider SAN switch configuration. For a
general midrange SAN environment, where 10 switches with 20 zones are
configured, 90 minutes is a recommended limit. Scale the time limit according to
your actual configuration.
To change the value to 60 minutes permanently, perform the following actions:
1. Edit the following file: C:\Program Files\IBM\Director\lwi\conf\overrides\
USMIKernel.properties
2. If the perf.extended.discovery.timeout entry exists, change its value to 60.
Otherwise, add the following line to the file:
perf.extended.discovery.timeout=60.
3. Restart the IBM Systems Director server.
Troubleshooting IBM Systems Director Storage Control 4.2.3
Use the information in this section if you have problems with IBM Systems
Director Storage Control 4.2.3.
Brocade switch zone inventory might not be correctly collected when it contains
offline zone members. See this technote for a workaround: Brocade Switch Zone
Inventory May Not be Correctly Collected When it Contains Offline Zone
Members.
Access type for remote service access point is wrong
This problem might occur after performing an upgrade from IBM Systems Director
6.2 to Systems Director 6.3.2 and upgrading from Storage Control 4.2.1 to a more
recent version.
Problem
After performing an upgrade as described, the access type for the remote service
access point (RSAP) of a switch or storage device does not have the correct value
of TPC.
Resolution
To return the access type of the switch or storage device to TPC, complete the
following steps:
1. Remove the farm by right-clicking the resource and selecting Remove.
2. Run the following command, where install_root is the root directory of your
IBM Systems Director installation. :
v On AIX or Linux, run install_root/StorageControl/bin/
SCDiscoverUnlock.sh
v On Windows, run install_root\StorageControl\bin\SCDiscoverUnlock.bat
16
IBM Systems Director Storage Control: Installation and User's Guide
3. Collect inventory on the associated farm. From the Plug-ins tab on the Home
page, under Discovery Manager, click View and Collect Inventory. Complete
the fields on the View and Collect Inventory page to collect the farm inventory.
Cannot communicate with Storage Control after changing the
IBM DB2 password
If you changed the password that IBM Systems Director uses to access IBM DB2,
but Storage Control can no longer access IBM DB2, use this information to solve
the problem.
Problem
After the IBM DB2 password that is used by IBM Systems Director is changed,
Storage Control cannot access the Storage Control Farm. In this case, the
information that is stored in the Farm contains the old credentials, but the Farm
still has an access state of unlocked.
Resolution
Complete the following steps to refresh credential information for the farm:
1. Remove the farm by right-clicking the resource and selecting Remove.
Note: The farm that you want to remove has the same host name as the
management server and has a Type of StorageEnsemble.
2. Rediscover and unlock the farm that you removed in the first step:
v For AIX and Linux, run the following command, where install_root is the root
directory of your IBM Systems Director installation. :
install_root/StorageControl/bin/SCDiscoverUnlock.sh
v For Windows, create and run a discovery profile to discover and request
access to the farm. When you create the profile, be sure to specify the
following settings:
– TPC DB Configuration:
- IP Address: The management server address
- Port: 50010
- Database Name: TPCDB
- Database UserId: The Windows administrator user name
- Database Password: The password for the specified Windows
administrator user name
– TPC Server Configuration:
- TPC UserId: The Windows administrator user name
- TPC Password: The password for the specified Windows administrator
user name
– TPC Storage Resource Group Selection: Select ALL
– Access Request: Specify the Windows administrator user name and
password
Cannot communicate with Storage Control after changing the
IBM Systems Director IP address
If you changed the IP address of the management server and you can no longer
communicate with Storage Control, use this information to solve the problem.
IBM Systems Director Storage Control 4.2.3
17
Problem
The host IP address of IBM Systems Director was changed and now you cannot
communicate with Storage Control. Storage Control and IBM DB2 both need to be
updated with the new IP address.
Resolution
After a change to IP address of the management server breaks communication
between IBM Systems Director and Storage Control, complete the following steps
to restore communication:
1. Remove the farm by right-clicking the resource and selecting Remove.
Note: The farm that you want to remove has the same host name as the
management server and has a Type of StorageEnsemble.
2. Stop and then restart Storage Control by running the following command-line
commands, where install_root is the root directory of your IBM Systems
Director installation.
v For AIX and Linux, run the following commands:
install_root/StorageControl/bin/stopStorageControl.sh
install_root/StorageControl/bin/startStorageControl.sh
v For Windows, open a command-line window, then run the following
commands:
install_root\StorageControl\bin\stopStorageControl.bat
install_root\StorageControl\bin\startStorageControl.bat
3. Add the farm that you removed in the first step:
v For AIX and Linux, run the following command, where install_root is the root
directory of your IBM Systems Director installation. :
install_root/StorageControl/bin/SCDiscoverUnlock.sh
v For Windows, create and run a discovery profile to discover and request
access to the farm. When you create the profile, be sure to specify the
following settings:
– TPC DB Configuration:
- IP Address: The management server address
- Port: 50010
- Database Name: TPCDB
- Database UserId: The Windows administrator user name
- Database Password: The password for the specified Windows
administrator user name
– TPC Server Configuration:
- TPC UserId: The Windows administrator user name
- TPC Password: The password for the specified Windows administrator
user name
– TPC Storage Resource Group Selection: Select ALL
– Access Request: Specify the Windows administrator user name and
password
18
IBM Systems Director Storage Control: Installation and User's Guide
Discovering (or adding) a SAN Volume Controller or a
Storwize family device in large configurations fails due to
timeout
This problem might occur when you discover (or add) a SAN Volume Controller
or a device from the IBM Storwize family, when the device is part of a
configuration that contains more than 1,000 items (including mDisks, vDisks,
volumes, and mDiskExtents).
Problem
When you use the Discover storage task or the smcli command mkdatasource to
discover (or add) a SAN Volume Controller or a device from the Storwize family,
the task or command fails with the message “Complete with errors.” This problem
might occur when the number of items in the storage area network totals 1,000 or
more, including mDisks, vDisks, volumes, and mDiskExtents.
Resolution
To successfully discover and request inventory to a SAN Volume Controller or a
device from the IBMStorwize family that is an item in such a large configuration,
you must reconfigure certain properties for IBM Tivoli Storage Productivity Center
and IBM Systems Director.
Note: To complete the following tasks, you must have root authority to the
management server.
To configure the IBM Tivoli Storage Productivity Center and IBM Systems Director
properties to successfully discover and collect inventory on a SAN Volume
Controller or a Storwize family device, complete the following steps.
1. Configure the timeout value for the IBM Tivoli Storage Productivity Center
device probe to 8 hours by running the following command-line command on
the management server (where TPC_install_dir is the directory where you
installed IBM Tivoli Storage Productivity Center):
v On AIX and Linux: TPC_install_dir/cli/tpctool.sh setdscfg -user
<tpcuser> -pwd <tpcpassword> -url localhost:9550 -property
NAPI.Timeout.probe 28800000
v On Windows: TPC_install_dir\cli\tpctool.bat setdscfg -user <tpcuser>
-pwd <tpcpassword> -url localhost:9550 -property NAPI.Timeout.probe
28800000
2. Verify the IBM Tivoli Storage Productivity Center device probe time by running
the following command-line command on the management server:
v On AIX and Linux: TPC_install_dir/cli/tpctool.sh getdscfg -user
<tpcuser> -pwd <tpcpassword> -url localhost:9550 -property
NAPI.Timeout.probe
v On Windows: TPC_install_dir\cli\tpctool.bat getdscfg -user <tpcuser>
-pwd <tpcpassword> -url localhost:9550 -property NAPI.Timeout.probe
Note: For more information about configuring and verifying the IBM Tivoli
Storage Productivity Center device probe, see the following IBM Tivoli Storage
Productivity Center information center topic: “Setting timeout values for the
Device server.”
IBM Systems Director Storage Control 4.2.3
19
3. Stop and then restart Storage Control by running the following command-line
commands, where install_root is the root directory of your IBM Systems
Director installation.
v On AIX and Linux:
install_root/StorageControl/bin/stopStorageControl.sh
install_root/StorageControl/bin/startStorageControl.sh
v On Windows:
install_root\StorageControl\bin\stopStorageControl.bat
install_root\StorageControl\bin\startStorageControl.bat
Note: To verify that Storage Control stopped running, run the following
command-line commands (from the previously specified directory). On AIX
and Linux, run scstatus.sh. On Windows, run scstatus.bat.
4. Configure Systems Director to timeout after 8 hours when Systems Director
calls the IBM Tivoli Storage Productivity Center API. Open the following file
with a plain text editor:
v On AIX and Linux: install_root/data/
DefaultTpcConnectionSettings.properties
v On Windows: install_root\data\DefaultTpcConnectionSettings.properties
If the tpc.config.timeout entry exists, change the corresponding value to
28800000. Otherwise, add the following line to the file:
tpc.config.timeout=28800000
Note: For more information, see the following topic: “Changing the default
time limit for inventory collection.”
5. Change the Systems Director extended discovery timeout to 2 hours. Open the
following file with a plain text editor:
v
On AIX and Linux: install_root/lwi/conf/overrides/
USMIKernel.properties
v On Windows: install_root\lwi\conf\overrides\USMIKernel.properties
If the perf.extended.discovery.timeout entry exists, change the corresponding
value to 120. Otherwise, add the following line to the file:
perf.extended.discovery.timeout=120
6. For the changes to the properties files to take effect, you must restart the
management server. For more information, see Restarting IBM Systems Director
Server.
If you continue to encounter inventory timeout errors after completing the
preceding steps, increase the extended discovery timeout by using the procedure
that is described in step 5, then restart the management server.
Cannot install or uninstall Storage Control on a Linux or AIX
system
If you try to install or uninstall Storage Control and it fails, follow these steps to
solve the problem.
Details
You must do all of these steps to solve the problem:
Note: If an installation failed after a successful uninstall, follow the procedures in
steps 3 on page 21 and 4 on page 21.
20
IBM Systems Director Storage Control: Installation and User's Guide
1. Find the cause of your problem in “Possible failures.”
2. Follow the proper procedure listed in “Resolution.”
3. “Manually remove the files and settings that were left on the system” on page
22.
4. Try the action again.
Possible failures
1.
2.
3.
4.
There is not enough processor memory.
There is not enough disk space.
An incorrect version of DB2 is installed.
IBM Systems Director is not installed or is not running.
5. The installation succeeded, but with errors.
6. The install failed with this error:
IP_address is a loopback address, which discovery does not support.
DNZCLI0713E : (Run-time error) A valid IP address was not specified for
discovery. Specify the IP address in proper format and try again.
7. Storage Control was uninstalled, but the Storage Control Farm is still listed in
the IBM Systems Director console under All Systems.
Resolution
1. Before installing Storage Control, restart the DB2 Management server by
running these commands:
su - db2_instance_owner
db2stop
sb2start
2. Increase your systems physical memory to at least 3.0 GB.
3. Increase your disk space to at least 4.0 GB.
4. If you are not using IBM DB2 managed by Systems Director, then you must use
one of these versions of IBM DB2 as the local database application for Systems
Director so that you can use Storage Control:
v IBM DB2 Enterprise Edition v. 9.7
v IBM DB2 Enterprise Edition v. 9.7 with fix pack 4
That is, the correct version of DB2 must be installed on the same system as
Systems Director. Storage Control is not supported on any other databases.
5. Install IBM Systems Director and ensure that it is running.
6. If the install failed with the error DNZCLI0713E: ip_address is a loopback
address, which discovery does not support, follow these steps:
a. Ensure that your network configuration is correct.
b. Run the appropriate command and verify that it returns an appropriate IP,
not the loopback IP:
On AIX, run the command host `hostname`.
On Linux, run the command hostname -i.
c. Uninstall Storage Control.
d. Reinstall Storage Control.
7. Discover and request access to the Storage Control Farm object.
8. Navigate to the Storage Control Farm object, then select the object and click
Actions > Remove.
IBM Systems Director Storage Control 4.2.3
21
Manually remove the files and settings that were left on the
system
Follow these steps to remove the files and settings:
1. Stop the device server.
a. On AIX, run /opt/IBM/TPC/device/bin/aix/stopTPCF.sh.
b. On Linux, run /opt/IBM/TPC/device/bin/linux/stopTPCF.sh.
2. To clean up the product registry , delete the following directory:
/etc/Tivoli/TSRM.
3. To clean up the installation registry, delete the appropriate directory:
v On AIX, delete /usr/lib/objrepos/InstallShield/Universal/IBM-TPC.
v On Linux, delete /root/InstallShield/Universal/IBM-TPC.
4. AIX only: Remove the subsystem:
a. Run this command: lssrc -a to determine the name of the Storage Control
subsystem. The name is TSRMsrn, where n can be any number; usually it is
1.
b. Run this command: rmssys -s TSRMsrn, where n is the value determined
previously.
5. Drop the appropriate database:
a. Log in as a DB2 user, such as db2inst1.
b. Run this command to drop the database: “db2 drop db database_name”
TPCDB is the default name.
6. Delete the IBM Tivoli Storage Productivity Center installation directory:
/opt/IBM/TPC/.
7. Delete the TPCAdmin group by using the commands appropriate to your
operating system.
v On AIX, use the rmgroup command.
v On Linux, use the groupdel command.
Cannot install or uninstall Storage Control on a Microsoft
Windows system
If you try to install or uninstall Storage Control and it fails, follow these steps to
solve the problem.
Details
You must do all of these steps to solve the problem:
Note: If an installation failed after a successful uninstall, follow the procedures in
steps 3 and 4.
1. Find the cause of your problem in “Possible failures.”
2. Follow the appropriate procedure that is listed in “Resolution” on page 23.
3. “Manually remove the files and settings that were left on the system” on page
23.
4. Try the installation or uninstallation again.
Possible failures
There are several possible reasons that the task failed. The error message indicates
the cause of the problem.
22
IBM Systems Director Storage Control: Installation and User's Guide
1.
2.
3.
4.
5.
There is not enough processor memory.
There is not enough disk space.
An incorrect version of DB2 is installed.
IBM Systems Director is not installed or is not running.
Installing Storage Control brings up a Java launcher failure.
6. The installation succeeded, but with errors.
7. Storage Control was uninstalled, but the Storage Control Farm is still listed in
the IBM Systems Director console under All Systems.
Resolution
Perform the steps to correct each of the following issues, if applicable.
1. Before you install Storage Control, restart the DB2 Management server.
a. Go to Start > Administrative Tools > Services.
b. Select the DB2 Management Service from the services window and restart
it.
2. Increase your systems physical memory to at least 3.0 GB.
3. Increase your disk space to at least 4.0 GB.
4. If you are not using IBM DB2 managed by Systems Director, then you must use
one of these versions of IBM DB2 as the local database application for Systems
Director so that you can use Storage Control:
v IBM DB2 Enterprise Edition v. 9.7
v IBM DB2 Enterprise Edition v. 9.7 with fix pack 4
That is, the correct version of DB2 must be installed on the same system as
Systems Director. Storage Control is not supported on any other databases.
5. If you received a Java launcher failure, follow these steps:
a. Follow these instructions: “Manually remove the files and settings that were
left on the system.”
b. Install Storage Control again. Ensure that the path to the installation file,
setup.exe, is not longer than 89 characters.
Important: The 89 characters are in addition to the name of the setup file.
Do not count the characters in the file name setup.exe as part of the path
length.
6. Install IBM Systems Director and ensure that it is running.
7. Discover and request access to the Storage Control Farm object.
8. Navigate to the Storage Control Farm object, then select the object and click
Actions > Remove.
Manually remove the files and settings that were left on the
system
Because a problem with the installation or uninstallation occurred, some files and
settings that need to be removed were left on your system. You cannot try the
installation again until you complete the following steps to remove the files and
settings:
1. Using the Windows Services panel, stop the Device Server service. The service
is named IBM WebSphere® Application Server V6.1 - DeviceServer.
a. To access the Services panel, click Start > Control Panel > Administrative
Tools > Services.
IBM Systems Director Storage Control 4.2.3
23
b. In the right pane, browse for IBM WebSphere Application Server V6.1 DeviceServer. Right click the name of the service and select Stop.
Note: If Stop is unavailable, it is already stopped.
2. Delete these folders:
v C:\Program Files\Common Files\InstallShield\Universal\IBM-TPC
v C:\Program Files\IBM\TPC
3. Delete the specified keys from the Windows registry. Open a Windows
command prompt, then run the following command. After you run the
command, close the command prompt window:
v For 32-bit versions of Windows: REG DELETE HKEY_LOCAL_MACHINE\SOFTWARE\
IBM\Director\ExtInfo\SC /f
v For 64-bit versions of Windows: REG DELETE HKEY_LOCAL_MACHINE\SOFTWARE\
Wow64Node\IBM\Director\ExtInfo\SC /f
4. Use the DB2 Control Panel to drop the IBM Tivoli Storage Productivity Center
database.
a. Open a DB2 command-line window. Go to Start > Programs > IBM DB2 >
Command Line Tools > Command Line Processor.
b. Enter “list database directory”.
If the database TPCDB is listed, then enter “drop database TPCDB”.
c. Close the command-line window.
5. Remove the specified users and groups from the system:
a. Go to Start > Settings > Control Panel > Administrative Tools >
ComputerManagement.
b. The Computer Management window opens. In the left pane, under
Computer Management (Local), expand Local Users and Groups. Click
Users. The users are listed in the right pane.
c. Delete these users:
v TSRMSrvn, where n can be any number; usually it is 1.
v TPCUser.
d. Click Groups. The groups are listed in the right pane.
e. Delete the TPCAdmin group.
f. Close the Computer Management window and the Administrative Tools
window.
6. Restart the system.
Cannot receive alerts from IBM Systems Director
After you discover and unlock the Storage Control Farm, you will receive IBM
Tivoli Storage Productivity Center alerts for it. If you are not receiving the alerts,
try these steps.
Resolution
For non-LSI devices:
1. Run the “Verify Connection” task.
Note: By default, the connection interval is set to 15 minutes. Therefore, it
could take up to 15 minutes to receive an alert. You can change this value from
the settings window.
2. If you still cannot receive alerts, run inventory against the farm.
24
IBM Systems Director Storage Control: Installation and User's Guide
3. If there is still a problem, run inventory against the storage device.
For IBM System Storage® DS3000, DS4000, and DS5000 series:
1. Check the status of the IBM Tivoli Storage Productivity Center server and DB2.
2. Verify that the server and Systems Director can communicate properly.
v The first available port in the range 18888 - 18907 is used for retrieving
alerts. Ensure that there is at least one available port in that range.
v Verify that the client port is open and that the client listener is in listening
mode.
3. Collect inventory on the farm, then collect inventory for the storage device.
Cannot unlock IBM Flex System V7000 Storage Node
This problem might occur when you request access to (unlock) the IBM Flex
System V7000 Storage Node.
Problem
After you request access to the IBM Flex System V7000, the device remains
inaccessible.
Resolution
To successfully request access to the IBM Flex System V7000, try the complete the
following steps:
1. Verify that the user ID and password you used to access the device are correct.
If either or both are incorrect, request access again by using the correct user ID
and password.
2. Make sure that the user ID you used to access the device does not have a
Secure Shell (SSH) key configured. If the user ID has an SSH key configured,
try one of the following actions:
v Request access by using a different user ID that does not have an SSH key
configured.
v Remove the SSH key from the user ID, then request access again.
3. Verify that IBM Systems Director can successfully communicate with the IBM
Flex System V7000. For example, verify that a firewall does not block
communications. After you resolve any discovered communications problems,
request access again.
4. If the IBM Flex System V7000 was discovered before but requesting access
failed, remove the IBM Flex System V7000, then discover and request access to
the device again.
Note: Use the smcli lsdatasource command to see whether the device was
already discovered, then use the smcli rmdatasource command to remove it.
Otherwise, you must also discover the associated integrated management
module again.
5. Make sure that Storage Control is installed and configured correctly, then
request access again.
smcli mkdatasource hangs after a date change
The IBM Systems Director command smcli mkdatasource -c fabric hangs if the
operating system time was set forward.
IBM Systems Director Storage Control 4.2.3
25
Resolution
Restart the server to synchronize the time between IBM Systems Director Storage
Control 4.2.3 and IBM Systems Director.
Storage Control does not work after migrating to IBM Systems
Director 6.3
If you migrated from IBM Systems Director 6.2.1 to IBM Systems Director and now
Storage Control does not work, it is possible that Storage Control is still trying to
use the old database.
Resolution
1. Open your profile in /etc/profile.
2. Delete the values for these parameters:
PATH
LD_LIBRARY_PATH
LIBPATH
Note: You will have LD_LIBRARY_PATH or LIBPATH, not both.
3. Log out and log back in or restart your system for the changes to take effect.
Storage Control installation hangs on an AIX system
If you try to install IBM Systems Director Storage Control 4.2.x.x on an AIX
operating system, and the installation becomes unresponsive, use this information
to solve the problem.
Resolution
The installation hangs because there is insufficient run time memory. Follow these
steps to ensure that enough memory is available:
1. Check the available free memory and clear all unwanted processes by running
svmon -G.
2. Verify that the user limit for memory is set to unlimited by running ulimit -m.
If it is not set correctly, run ulimit -m unlimited.
3. Interrupt the installation by pressing Ctrl+C.
4. Clean up the incomplete Storage Control installation. For instructions, see the
following section of a related troubleshooting topic: “Manually remove the files
and settings that were left on the system” on page 22.
5. Restart the IBM Systems Director Storage Control 4.2.x.x installation.
Storage Control operations fail with SEVERE TPC Exception:
OutOfMemoryError
This problem might occur when you use Storage Control to manage a large SAN
environment or a high number of storage devices.
Problem
The time that is required to complete Storage Control operations, including
inventory collection, is uncommonly long and some operations fail with a SEVERE
TPC Exception: OutOfMemoryError in the associated job log.
26
IBM Systems Director Storage Control: Installation and User's Guide
Resolution
To prevent this error from occurring, increase the RAM that Storage Controluses by
completing the following steps:
1. Navigate to the server.xml file, which has the following default path:
v On AIX or Linux: /opt/IBM/TPC/device/apps/was/profiles/deviceServer/
config/cells/DefaultNode/nodes/DefaultNode/servers/server1/server.xml
v On Windows: \Program Files\IBM\TPC\device\apps\was\profiles\
deviceServer\config\cellsDefaultNode\nodes\DefaultNode\servers\
server1\server.xml
2. Open the server.xml file in a plain text editor.
3. Find the entry that begins with genericJvmArguments. The associated default
value is -Xmx512m, which represents the maximum size of the execution heap
for Storage Control, in megabytes. Change the value to include a higher
number, for example 1536, which would make the value -Xmx1586m, or about
1.5 GB.
4. Save and close the file.
5. Restart IBM Systems Director for the change to take effect.
IBM Systems Director Storage Control 4.2.3
27
28
IBM Systems Director Storage Control: Installation and User's Guide
Index
© Copyright IBM Corp. 2010, 2012
29
30
IBM Systems Director Storage Control: Installation and User's Guide
Printed in USA