Ibm system storage productivity center deployment guide sg247560

Front cover

IBM System Storage
Productivity Center
Deployment Guide
Understand the function and features
of IBM SSPC

Consolidate management of IBM
subsystems

Integrate SSPC in an existing
TPC environment

Mary Lovelace
Martin Jer
Patrick Ji
Danijel Paulin

ibm.com/redbooks

International Technical Support Organization

IBM System Storage Productivity Center Deployment
Guide

July 2008

SG24-7560-00

Note: Before using this information and the product it supports, read the information in “Notices” on
page vii.

First Edition (July 2008)

This edition applies to Version 3, Release 3, Modification 1 of TotalStorage Productivity Center Basic Edition
(product number 5608-B01) and IBM System Storage Productivity Center (product number 2805-MC2).

© Copyright International Business Machines Corporation 2008. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM Corp.

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
The team that wrote this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 1. System Storage Productivity Center introduction . . . . . . . . . . . . . . . . . . . . 1
1.1 SSPC overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.1 SSPC solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.2 TPC Basic Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1.3 SSPC hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1.4 SSPC deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 TPC Basic Edition versus Standard Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 When do you need SSPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3.1 DS8000 management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3.2 SVC management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.3 Building an SSPC server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4 Architecture of SSPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4.1 TPC Basic Edition components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.5 TPC key concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2. Planning for SSPC install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1 Collecting configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2 SSPC and TPC Basic Edition relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3 SSPC server options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.1 Options for SSPC server hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3.2 SSPC software options and licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4 Planning for the future . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4.1 Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4.2 Server sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.5 Building a SSPC like server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.6 SVC requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.7 Existing TPC environment and integration of SSPC . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.8 DS8000 Element Manager GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.9 Redundant SSPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.9.1 Single SSPC instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.9.2 Dual SSPC instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 3. SSPC initial setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.1 Initial SSPC setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.2 Change the host name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.2.1 Change the host name in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.2.2 Change host name in DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.2.3 Stop and start services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

© Copyright IBM Corp. 2008. All rights reserved. iii

3.3 Connect SVC Master Console to SVC Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 4. Building an SSPC server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.1 SSPC build basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.1.1 Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.2 Install IBM DB2 Enterprise Server Edition V9.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.2.1 Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.3 Installation of TPC V3.3.1 Basic Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.4 SVC Console and CIMOM Agent V4.2.1 installation . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.4.1 PuTTY installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.4.2 SVC Console and CIMOM Agent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.4.3 Connect SVC Master Console to SVC Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Chapter 5. Managing your SSPC appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
5.1 Securing your SSPC server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
5.1.1 Application security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
5.1.2 Operating system security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
5.1.3 Network security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
5.2 Upgrading your SSPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
5.3 Integrating your SSPC with an existing TPC environment . . . . . . . . . . . . . . . . . . . . . 102
5.3.1 Rollup reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.4 Backing up your SSPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Chapter 6. TPC Basic Edition functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
6.2 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
6.2.1 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
6.2.2 Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
6.2.3 Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
6.2.4 Graphical user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
6.2.5 Command-line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
6.3 Using TPC BE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
6.3.1 Starting the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
6.3.2 Using the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
6.3.3 Collecting data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
6.3.4 Adding CIMOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
6.3.5 DS8000 CIMOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
6.3.6 Adding in-band Fabric agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
6.3.7 Adding out of band Fabric agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
6.3.8 Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
6.4 Topology Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
6.4.1 Topology Viewer overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
6.4.2 Data Path Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
6.4.3 Managing storage subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
6.4.4 Managing fabrics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
6.5 Element Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
6.5.1 Storage subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
6.5.2 Switch Element Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
6.5.3 Tape Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
6.5.4 External tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Chapter 7. Upgrading SSPC and using additional functions . . . . . . . . . . . . . . . . . . . 187
7.1 Upgrading SSPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
7.1.1 TPC BE upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

iv IBM System Storage Productivity Center Deployment Guide

7.1.2 SVC GUI and CIMOM upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
7.2 Installing Agent Manager and deploying agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
7.2.1 Agent Manager installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
7.2.2 Device server and Data server registration with the Agent Manager . . . . . . . . . 205
7.2.3 Deploying Data and Fabric agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
7.3 Additional Standard Edition functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
7.3.1 Collecting storage usage and trending information. . . . . . . . . . . . . . . . . . . . . . . 210
7.3.2 Determining the availability of storage resources . . . . . . . . . . . . . . . . . . . . . . . . 210
7.3.3 Storage provisioning using SAN Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
7.3.4 Enterprise rollup reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Chapter 8. DS8000 GUI under Element Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
8.1 Launch DS8000 GUI from SSPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
8.2 What is new in the new DS8000 GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
8.2.1 Creating Extent Pools using the Automatic function . . . . . . . . . . . . . . . . . . . . . . 232
8.2.2 Delete Extent Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
8.2.3 Make Extent Pools: manual action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
8.2.4 Add capacity to an Extent Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
8.2.5 Remove capacity from Extent Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
8.2.6 Make volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
8.2.7 Assign Parallel Access Volumes (PAV) (alias volumes) . . . . . . . . . . . . . . . . . . . 275
8.2.8 Dynamic Volume Expansion on System z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
8.2.9 Dynamic Volume Expansion on Open Systems . . . . . . . . . . . . . . . . . . . . . . . . . 284

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
How to get Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Contents v

vi IBM System Storage Productivity Center Deployment Guide

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult
your local IBM representative for information on the products and services currently available in your area.
Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product, program, or service that does
not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to
evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The
furnishing of this document does not give you any license to these patents. You can send license inquiries, in
writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: 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 states 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.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm the
accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them
as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the sample
programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore,
cannot guarantee or imply reliability, serviceability, or function of these programs.

© Copyright IBM Corp. 2008. All rights reserved. vii

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines
Corporation in the United States, other countries, or both. These and other IBM trademarked terms are
marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US
registered or common law trademarks owned by IBM at the time this information was published. Such
trademarks may also be registered or common law trademarks in other countries. A current list of IBM
trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml

The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:
AIX® Passport Advantage® System z™
Chipkill™ Redbooks® Tivoli®
DB2® Redbooks (logo) ® TotalStorage®
DS6000™ System Storage™ WebSphere®
DS8000™ System Storage DS™ z/OS®
IBM® System x™

The following terms are trademarks of other companies:

Novell, SUSE, the Novell logo, and the N logo are registered trademarks of Novell, Inc. in the United States
and other countries.

Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporation and/or
its affiliates.

Java, JRE, JVM, Sun, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United
States, other countries, or both.

Microsoft, SQL Server, Windows Server, Windows, and the Windows logo are trademarks of Microsoft
Corporation in the United States, other countries, or both.

Intel Xeon, Intel, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks
of Intel Corporation or its subsidiaries in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

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

viii IBM System Storage Productivity Center Deployment Guide

Preface

IBM® System Storage™ Productivity Center (SSPC) is the next step in the IBM storage
strategy. This solution comprises hardware and software, combining device configuration
capabilities for the IBM System Storage DS8000™ and IBM System Storage SAN Volume
Controller (SVC) in an easy-to-use hardware console. SSPC extends the manageability of
these devices with the introduction and integration of IBM TotalStorage® Productivity Center
Basic Edition V3.3.1. Consolidating several hardware and software components on a single
tested system helps support consistent interoperability.

This IBM Redbooks® publication will provide an overview of IBM System Storage Productivity
Center (SSPC). It contains the information required to set up your SSPC server by taking you
through the initial customization of the server and then defining and launching Element
Managers through IBM TotalStorage Productivity Center (TPC) Basic Edition. Details on
using the functions of TPC BE are provided as well as upgrading your SSPC server (and TPC
BE) to a fully functional TPC Standard Edition. Managing IBM TotalStorage DS8000 using
TPC V3.3.1 is also covered in this book.

The team that wrote this book
This book was produced by a team of specialists from around the world working at the
International Technical Support Organization, San Jose Center.

Figure 1 The SSPC team: Martin, Mary, Danijel, Patrick

© Copyright IBM Corp. 2008. All rights reserved. ix

Mary Lovelace is a Consulting IT specialist at the International Technical Support
Organization. She has more than 20 years of experience with IBM in large systems, storage
and Storage Networking product education, system engineering and consultancy, and
systems support. She has written numerous Redbooks on TotalStorage Productivity Center
and z/OS® storage products.

Martin Jer is a Certified IT Storage Specialist in New York, working as a pre-sale advisor for
enterprise storage topics. He has more than 30 years of experience with IBM large systems,
storage systems, tape systems, and virtualization systems. His area of expertise is in the
design of storage solutions for mainframe and open systems.

Patrick Ji is an IBM Certified IT Architect working in Australia. He is also a Master Certified IT
Architect by The Open Group. He has over 10 years experience in the IT industry. His
background includes multiple IT domains, including storage, security, networks, Windows®,
UNIX®, databases, and programming. He also had three years of trading experience before
commencing his career in the IT industry. By combining business skills with IT skills, he
assists medium to large companies optimize IT strategies, delivering innovative solutions and
maximizing business values through IT investment.

Danijel Paulin is an IT Specialist in IBM Croatia, providing storage technical support. He has
nine years of experience in mainframe and storage environments. Before joining IBM Croatia
in 2003, he worked for a large bank in Croatia and was responsible for z/OS and storage
administration. His areas of expertise include IBM high-end disk and tape storage
subsystems and disaster recovery solutions using the capabilities and features of IBM
storage products.

Thanks to the following people for their contributions to this project:

Sangam Racherla
International Technical Support Organization, San Jose Center

Bob Haimowitz
International Technical Support Organization, Raleigh Center

Rich Conway
Dave Bennin
Don Brennan
International Technical Support Organization, Poughkeepsie Center

Yan Chu
Nancy Hobbs
Bryant Lee
Miki Walter
SSPC Team, San Jose

Jason Turner
SSPC Product Manager, Austin, Texas

Ivo Gomilsek
Infrastructure IT Architect for Storage Solutions in CEMAAS IMT

Mike Griese
Worldwide Technical Support Management for IBM TotalStorage Productivity Center

x IBM System Storage Productivity Center Deployment Guide

Become a published author
Join us for a two- to six-week residency program! Help write a book dealing with specific
products or solutions, while getting hands-on experience with leading-edge technologies. You
will have the opportunity to team with IBM technical professionals, Business Partners, and
Clients.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you
will develop a network of contacts in IBM development labs, and increase your productivity
and marketability.

Find out more about the residency program, browse the residency index, and apply online at:
ibm.com/redbooks/residencies.html

Comments welcome
Your comments are important to us!

We want our books to be as helpful as possible. Send us your comments about this book or
other IBM Redbooks in one of the following ways:
Use the online Contact us review Redbooks form found at:
ibm.com/redbooks
Send your comments in an e-mail to:
redbooks@us.ibm.com
Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. HYTD Mail Station P099
2455 South Road
Poughkeepsie, NY 12601-5400

Preface xi

xii IBM System Storage Productivity Center Deployment Guide

1

Chapter 1. System Storage Productivity
Center introduction
The IBM System Storage Productivity Center is an integrated hardware and software solution
that provides a single point of entry for managing IBM System Storage DS8000 systems, IBM
System Storage SAN Volume Controller clusters, and other components of your data storage
infrastructure.

In this chapter, the following topics are discussed:
SSPC overview
TPC Basic Edition versus Standard Edition
When do you need SSPC
Architecture of SSPC
TPC key concepts

© Copyright IBM Corp. 2008. All rights reserved. 1

1.1 SSPC overview
IBM System Storage Productivity Center (SSPC) is the next step in the IBM storage strategy.
This solution comprises hardware and software, combining device configuration capabilities
for the IBM System Storage DS8000 and IBM System Storage SAN Volume Controller (SVC)
in an easy-to-use hardware console. SSPC extends the manageability of these devices with
the introduction and integration of IBM TotalStorage Productivity Center Basic Edition V3.3.1.
Consolidating several hardware and software components on a single tested system helps
support consistent interoperability.

SSPC provides extended device configuration capabilities for IBM System Storage Devices
while at the same time consolidating management to a central platform. TPC Basic Edition
V3.3.1 allows you to manage the storage network, hosts, and physical disks in context, in
addition to basic device configuration. The complete SSPC offers the following capabilities:
Pre-installed and tested console: IBM has designed and tested SSPC to support
interoperability between server, software, and supported storage devices.
IBM System Storage DS8000 GUI integration: With TPC V3.3.1, the DS Storage Manager
GUI for the DS8000 is integrated with TPC for remote Web access.
IBM System Storage SAN Volume Controller (console and CIM agent V4.2.1): These
management components of SAN Volume Controller (SVC) are pre-installed on the SSPC
along with TPC Basic Edition, which together are designed to reduce the number of
management servers.
Automated device discovery: DS8000 and SVC storage devices can be automatically
discovered and configured into TPC environments. These devices are displayed in TPC
through a storage topology.
Asset and capacity reporting: TPC collects asset and capacity information from storage
devices on the SAN, which can be kept for historical reporting, forecasting, and used for
other tasks, such as analysis and provisioning.
Advanced Topology Viewer: Provides a linked graphical and detailed view of the overall
SAN, including device relationships and visual notifications.

IBM interviewed many DS8000 customers, support organizations, and Business Partners.
From those interviews came a list of requests for GUI enhancements and new features. Many
of the GUI enhancements are being implemented in the DS Storage Manager, such as
configurations involving hosts, extent pools, volume groups, long running tasks, and
navigation. The new features that were requested include a Topology Viewer, reporting, and
performance statics. The SSPC with TPC combination is the method by which these new
functions are offered. Rather than SSPC being labeled a storage management solution, it
should be thought of as the new management platform for the new DS8000 GUI, which can
be upgraded to a storage management solution.

1.1.1 SSPC solution
The IBM SSPC solution includes three components: SSPC hardware, IBM TPC V3.3.1 Basic
Edition, and SVC V4.2.1 Master Console and CIMOM. SSPC is a new integrated platform.
This solution includes TPC Basic Edition pre-installed and tested on IBM machine type 2805.

TPC Basic Edition provides:
Storage Topology Viewer
The ability to monitor, alert, report, and provision storage

2 IBM System Storage Productivity Center Deployment Guide

Status dashboard
IBM System Storage DS8000 GUI integration with TPC Basic Edition

The IBM System Storage Productivity Center (machine type 2805) includes the following
pre-installed software:
Microsoft® Windows 2003 Server Fix Pack 2
DB2® Enterprise Server Edition V9.1 with Fix Pack 2
IBM TotalStorage Productivity Center Basic Edition V3.3.1
IBM System Storage SAN Volume Controller (SVC) Console and CIMOM Agent V4.2.1

In addition, the DS8000 Storage Manager GUI can now be utilized inside the TPC GUI
environment. This provides the administrator with additional features inherent to TPC. New
DS8000 systems at the Release 3 level utilize TPC for remote Web access.

1.1.2 TPC Basic Edition
TPC Basic Edition is a new TPC package. It has TPC for Disk and TPC for Fabric without
performance functions. TPC Basic Edition V3.3.1 extends the device configuration
capabilities of IBM storage resources to a central platform. With TPC Basic Edition, you can
manage the storage network, hosts, and physical disks in context rather than by device. IBM
TotalStorage Productivity Center Basic Edition offers:
IBM System Storage DS8000 GUI integration
Automated device discovery
Asset and capacity reporting
Device configuration
Basic storage provisioning
Advanced Topology Viewer
Event management
Status dashboard

TPC Basic Edition V3.3.1 centralizes management of networked storage devices that
implement the SNIA Storage Management Interface Specification (SMI-S), which includes the
IBM System Storage DS™ family and IBM System Storage SAN Volume Controller (SVC). It
is designed to help reduce storage management complexity and costs and help improve data
availability through open standards (SMI-S).

TPC Basic Edition V3.3.1 users can easily upgrade to IBM TotalStorage Productivity Center
Standard Edition. IBM TotalStorage Productivity Center Standard Edition provides advanced
features, such as performance reporting, file-level capacity utilization, best practices-based
configuration management, and wizard-driven end-to-end storage provisioning.

TPC Basic Edition can easily be upgraded to the following:
IBM TotalStorage Productivity Center for Data – 5608-VC3
IBM TotalStorage Productivity Center for Disk – 5608-VC4
IBM TotalStorage Productivity Center for Fabric – 5608-VC1
IBM TotalStorage Productivity Center Standard Edition – 5608-VC0 (includes Disk, Data,
and Fabric)

Chapter 1. System Storage Productivity Center introduction 3

To use these features, the customer must purchase the appropriate software license. These
features are pre-installed on SSPC and are activated through license files. TPC for
Replication is not preloaded, although it can be installed on the SSPC server.

1.1.3 SSPC hardware
The hardware used by the SSPC solution is IBM System Storage Productivity Center
2805-MC2. It is a 1U rack-mounted server. It has the following initial configuration:
Initial processor: One Quad-Core Intel® Xeon Proc E5310 (1.60 GHz 8 MB L2 1066 MHz
80 W)
Memory: Four 1 GB PC2-5300 CL5 ECC DDR2 Chipkill™ FBDIMM 667 MHz sticks
Primary array hard disk drives: Two 146 GB 15K 3.5" SAS HDD RAID 1
Optical drive: CD-ROM Ultrabay Enhanced Drive
Ethernet: Dual integrated 10/100/1000 Mbps Ethernet
Microsoft Windows 2003 Enterprise Edition

This setup is designed to perform basic SSPC functions. If you plan to upgrade SSPC for
more functions, you can purchase the Performance Upgrade Kit to add more capacity to your
hardware.

1.1.4 SSPC deployment
There are three ways to deploy SSPC in your environment, which are:
Deploying the IBM SSPC solution.
Building your own SSPC server by installing TPC V3.3.1 and SVC V4.2.1 on your selected
hardware platform from the supported hardware list.
If you have already deployed TPC in your environment, you may upgrade your TPC to
V3.3.1 for SSPC equivalent functions.

1.2 TPC Basic Edition versus Standard Edition
TPC Basic Edition offers the same functions provided in TPC Limited Edition. However, TPC
Basic Edition is not restricted to 2 TB and there is a license charge for TPC Basic Edition.
There is no data size restriction with Basic Edition. TPC Limited has been withdrawn from
marketing.

TPC Basic Edition provides value in addition to the DS Storage Manager or SVC Console.
However, TPC Basic Edition is not a Storage Management solution. TPC Standard Edition
provides many more features. TPC Standard Edition provides greater reporting, disk
performance analysis, provisioning, predictive analysis, and SAN planning. TPC Standard
Edition is the industry leading Storage Resource Management and SAN Management
product in the industry.

Figure 1-1 on page 5 gives a detailed comparison between TPC Standard Edition and TPC
Basic Edition.


DS Storage SVC Admin TPC Basic TPC Standard
Function Manager Console Edition Edition
Storage Infrastructure Configuration/Status Reporting

Device Discovery/Configuration
Manage multiple DS8000s / SVCs from 1 User Interface
Topology Viewer and Storage Health Management
Provisioning, including Fabric zoning and Disk LUN
assignment
Configuration Management – Highlight configuration changes
over time periods, Best Practice recommendations, Storage
configuration planning and recommendations, Security
planner

Storage Reporting
Basic Asset & Capacity Reporting
Storage reporting on the relationships of computers, file
systems and DS8000 LUNs/volumes
Capacity Analysis/Predictive Growth
Customized and Detailed Capacity Reporting – including
Chargeback and Database Reporting
Performance Management
Performance Reporting/Thresholds
Volume Performance Advisor – Recommend DS8000
configuration based on performance workloads
Fabric performance reporting and monitor

Figure 1-1 Comparison between TPC Standard Edition and Basic Edition

1.3 When do you need SSPC
In this section, we discuss the options for deploying SSPC in your environment, when SSPC
is optional, and when it is required based on your configuration.

1.3.1 DS8000 management
New DS8000 series systems purchased after October 23, 2007 will need TPC V3.3.1 in order
to access the DS8000 GUI from any system other than the HMC. Existing DS8000
subsystems upgrading to R3 (DS8000 Licensed Machine Code [LMC] 5.3.0xx.xx, or later) do
not require SSPC. Customers will still see the enhancement made to the DS Storage
Manager but will not have the new features/GUI offered with SSPC.

Any TPC product at the V3.3.1 level (excluding TPC for Replication) will integrate the DS8000
Storage Manager GUI with TPC. With this new release of DS8000, several configuration
operations have been greatly improved. Additionally, TPC will provide tools requested by
many in the DS8000 community, such as Topology Viewer and asset and capacity reporting.

TPC Basic Edition V3.3.1 comes pre-installed on the new SSPC offering. SSPC was
specifically designed and tested with DS8000 and SVC customers in mind. In order to avoid
possible installation delays and potential technical issues, we recommend that if you do not
have TPC that you order SSPC.

If you already have TPC installed and configured in your environment (excluding TPC Limited
Edition users), you can use your existing TPC server and TPC software license to perform the
remote configuration of new DS8000s using the GUI. Of course, your TPC installation must
have IP connectivity to the new DS8000 in question. To do so, you need to upgrade your TPC
to V3.3.1. TPC V3.3.1 is the first release able to access the integrated DS8000 GUI remotely.
Without TPC V3.3.1, the new DS8000 GUI can only be accessed directly from the HMC.


Note: Keep in mind that TPC software is licensed by capacity. If an existing TPC customer
adds a new DS8000, they will likely need to purchase additional TPC capacity if they do
not have enough spare capacity.

If you are an existing TPC customer and not able to upgrade to V3.3.1 in time for your new
DS8000 installation, you have the following options:
Assuming you cannot upgrade TPC in time, you can temporary install TPC V3.3.1 on a
minimally sized server solely to access the new DS8000 GUI. Once you upgrade your
production TPC server to V3.3.1, the temporary TPC server can be decommissioned.
You can configure the DS8000 using the GUI directly from the HMC.
You can use the DS8000 CLI.
If the new DS8000 is going into a location without TPC, you may consider purchasing
SSPC for that new location.

1.3.2 SVC management
At this time, SSPC is an alternative to the current SVC master console. SSPC includes the
SVC V4.2.1 Master Console and CIMOM agent. It can manage up to two 8-node clusters.

If you have an existing SVC Master console, CIMOM, and clusters at a level prior to V4.2.1
you can upgrade to V4.2.1 to manage your SVC clusters. You do not need to purchase SSPC.

In the first half of 2008, SSPC will become compulsory for any new orders of SVC clusters.

1.3.3 Building an SSPC server
Apart from deploying the IBM SSPC solution, you can also build your own SSPC server by
installing SSPC software on your selected hardware platform from the SSPC supported
hardware list.

To build your own SSPC server, you need to install the following software in your server:
Microsoft Windows 2003 Release 2 Server Enterprise Edition
IBM DB2 Enterprise Server Edition V9.1 with Fix Pack 2
IBM TotalStorage Productivity Center V3.3.1 Basic Edition
IBM System Storage SAN Volume Controller Console and CIMOM agent V4.2.1

1.4 Architecture of SSPC
SSPC is built on SSPC 2805-MC2 and is running on Windows 2003 Release 2 Server
Enterprise Edition. SSPC has two main software components. One is SVC Console and
CIMOM V4.2.1. The other is TPC Basic Edition V3.3.1. TPC Basic Edition uses DB2
Enterprise Server Edition V9.1 as its database repository.


1.4.1 TPC Basic Edition components
TPC Basic Edition is the core component of SSPC. Figure 1-2 shows the high level
components of TPC Basic Edition, which includes the DB2 V9.1 database repository, TPC
GUI, Data server, Device server, and Element Manager for DS8000.

An Agent Manager can also be installed as an optional component. The Agent Manager can
be installed on either the SSPC server or a separate server.

O ptional C om ponent
E lem ent
DB
TP C M anager
A gent GUI for D S 8000
M anager

A gents D ata
S erver
C entral
C IM O M
TP C D B
A gents
D evice
S erver
O ut of B and
Fabric A gents
TP C B asic E dition

Figure 1-2 Components of TPC Basic Edition

Unlike TPC Standard Edition, TPC Basic Edition does not include TPC for Data. Therefore,
you cannot deploy Data agents with TPC Basic Edition.

Like TPC Standard Edition, TPC Basic Edition uses CIMOM agents and Out of Band Fabric
agents to gather information and provide configuration changes in your storage and fabric
devices.

TPC database
TPC database runs on IBM DB2 Enterprise Server Edition V9.1. It provides a central
repository for all TPC collected data.

TPC GUI
In the TPC environment, you have the following three ways to invoke the TPC GUI:
Invoking the TPC GUI installed on SSPC
Using the Java™ Webstart GUI by pointing your Internet browser to SSPC
Installing the TPC GUI on your own workstation.

Data server
The Data server hosts the control points for product scheduling functions, configuration, event
information, reporting, and graphical user interface support. It coordinates the communication
with agents and the data collection from agents that scan file systems and databases to
gather storage demographics and populate the TPC database with results.


Automated actions can be defined to drive functions, such as file system extension, data
deletion, TSM backup or archiving, or event reporting when defined thresholds are
encountered. The Data server is the primary contact point for all user interface functions.

The Data server also includes functions that schedule data collection and discovery for the
Device server.

Device server
The Device server discovers storage subsystems and SAN fabrics, and then it gathers
information about storage subsystems and SAN fabrics and analyzes their performance.

The Device server controls the communication with agents and the data collection from
agents that scan SAN fabrics. It is also responsible for the creation and monitoring of
replication relationships between storage devices.

Element Manager for DS8000
Element Manager for DS8000 is a new function for TPC. It communicates with the DS8000
R3 HMC and provides you an interface to manage your DS8000 at the device level. To use
Element Manager for DS8000, you need to switch to the DS8000 Element Manager
Perspective within the TPC GUI, add Element Manger, and launch DS the GUI by clicking the
provided link.

Agent Manager
The TPC Data agents and Fabric agents gather host, application, and SAN fabric information
and send it to the Data server and the Device server. Agent Manager is used to manage Data
agents and Fabric agents. The architecture of Agent Manager is based on Tivoli® Common
Agent Services (CAS). The Common Agent Services provides a way to deploy agent code
across multiple user machines or application servers throughout the enterprise. The deployed
agent code collects data from and performs operations on managed resources on behalf of
TPC.

In TPC Standard Edition, Agent Manager is used to deploy and manage both Data Agents
and Fabric agents to the managed servers. Because TPC for Data is not included in the TPC
Basic Edition, only Fabric agents can be deployed and managed by Agent Manager in TPC
Basic Edition.

1.5 TPC key concepts
In this section, we review some of the key concepts in TPC.

CIMOM agent
CIMOM agent uses Web-Based Enterprise Management (WBEM) and Storage Management
Initiative - Specification (SMI-S) architecture.

Web-Based Enterprise Management is a initiative of the Distributed Management Task Force
(DMTF) with the objective to enable the management of complex IT environments. It defines
a set of management and Internet standard technologies to unify the management of
complex IT environments.


The three main conceptual elements of the WBEM initiative are:
Common Information Model (CIM): CIM is a formal object-oriented modeling language
that is used to describe the management aspects of systems.
xmlCIM: This is a grammar to describe CIM declarations and messages used by the CIM
protocol.
HTTP and HTTPS: These specification are used as a way to enable communication
between a management application and a device that both use CIM.

Storage Management Initiative - Specification (SMI-S) was launched by the Storage
Networking Industry Association (SNIA) in mid-2002 to create and develop a universal, open
interface for managing storage devices, including storage networks. In the SMI-S model, the
CIM for storage management is fully adopted and enhanced to standardize the management
interfaces so that management applications can provide cross device management.

The TPC design follows the SMI-S architecture. Figure 1-3 shows how the CIMOM agent
works in a TPC environment.

CIM Client
( TPC )
CIM message is transferred between the CIM
client and the CIMOM by http/https encoded
with XML

CIMOM CIMOM uses the Provider to translate CIM
message into proprietary message to
Provider communicate with the Storage Devices

Proprietary message to communicate between
the Provider and the Storage Devices

Storage Devices

Figure 1-3 SMI-S architecture for TPC

In the SSPC environment, the CIMOM agent or the SVC clusters is integrated into SSPC. The
CIMOM agents of DS8000 are embedded into DS8000 HMC consoles. Therefore, in the
SSPC environment, there is no extra CIMOM hardware required for SVC and DS8000.

Out of Band Fabric agents
The function of Out of Band Fabric agent is to collect storage fabric information through a
TCP/IP channel. It relies on SNMP to collect and send the information required.

The SNMP architecture consists of both an SNMP agent and SNMP manager. An SNMP
agent is a piece of software running on an SNMP-capable network component. It responds to
the SNMP requests from an SNMP manager and provides the management functionality
defined in the subsystem. An SNMP manager manages the SNMP agents on behalf of an
administrator.

In the Out of Band Fibre Agents implementation, TPC functions as an SNMP manager and
manages the SNMP agent in each Fabric device.


Discovery function
TPC also implemented a discovery function. It can help administrators to automatically
discover the storage devices running in the same environment.

Based on the SMI-S architecture, the TPC discovery function is implemented using the
Service Location Protocol (SLP). Figure 1-4 shows a typical SLP deployment in the TPC
environment.

SLP User Agent (UA) is a process working on the behalf of the users to establish contact with
network services. The UA queries and retrieves service information from Service Agents
(SAs). In the TPC environment, the SLP UA runs within the TPC process.

SLP SA is a component working on behalf of one or more network services to broadcast the
availability of services. SA replies to the service requests of UA and provides requested
information about the services registered with the SA.

TPC Discovery Procedure:
TPC
1. UA embedded within TPC sending out multicast
SLP UA messages to the network and targeting all SLP
SAs within the multicast range with a single User
Datagram Protocol (UDP) message
1 2
2. SA embedded within the CIMOM receives a
service request, compares its own registered
SLP SA services with the requested service, and returns
matches to the UA using a unicast reply
CIMOM message.

Figure 1-4 Discovery architecture

To locate a service in the TPC environment, you define a service type you want in the TPC
GUI. Based on the general description of the services you have specified, TPC invokes SLP
UA to send out multicast messages to the whole network and targeting all SLP SAs within the
multicast range.

When an SLP SA receives a service request, it compares its own registered services with the
services requested and returns matches to the UA using a unicast reply message.

The SLP UA follows the same procedure and sends repeated multicast messages until no
new replies are received. The resulting set of discovered services, including their service URL
and any service attributes, are returned to TPC.

Tivoli Agent Manager
SSPC uses Tivoli Agent Manager to deploy and manage agents in selected servers to gather
server information. Tivoli Agent Manager has three components: Agent Manager, Common
Agent, and Subagent. Figure 1-5 on page 11 shows how SSPC, Agent Manager, and Agents
communicate with each other.


Agent
M anager Registration,
Agent Registry DB SSPC
SSPC
M anager Q uery DB
DB

SSPC
Registration, Native
Configuration Protocol
updates
Subagent Subagent
Data Fabric

Tivoli Com m on Agent

Server
Figure 1-5 Agent Manager overview

Agent Manager is the central component managing agents deployed in the environment. It
maintains its own database to keep the information about the managed agents.

Common Agent is installed on the systems to be managed. It is responsible for managing
Subagent on the system at the request of a managing system.

Subagent is used to provide system level function; this can be a Data agent or a Fabric agent.
By default, SSPC allows you to deploy Fabric agents on managed servers. If you upgrade
your SSPC to TPC Standard Edition, you can also deploy Data agents on managed servers.

The Fabric agents are installed on computer systems that have fiber optic connectivities
through HBAs into the SAN fabrics that you want to manage and monitor. The Fabric agents
collect fabric topology information, port state information, and zoning information. The Fabric
agents can also identify other SAN-attached devices if they are in the same zone. Using
operating system calls, the agents also collect information about the machine on which they
are installed. We recommend having a minimum of one Fabric agent installed per fabric zone.

The Data agents collect information from the machines or hosts on which they are installed.
The agents collect asset information, file and file system attributes, and any other information
needed from computer systems. Data agents can also gather information about database
managers installed on the servers, Novell® NDS tree information, and NAS device
information. Data agents are typically installed on all servers in the SAN that you want to
collect information from. This is because each server has a unique set of files and file
systems that TPC cannot track without an agent.


2

Chapter 2. Planning for SSPC install
The IBM System Storage Productivity Center is a platform for managing IBM storage devices.
The 2805 is an x86 server that is preloaded with IBM TotalStorage Productivity Center Basic
Edition. Through the integration and testing of software and hardware on a single platform,
you can begin to consolidate your storage management infrastructure.

SSPC V1.1 may seem like a simple server solution initially, but the environments it will go into
are not simple. They can be quite complex and need to be reviewed by people who are
knowledgeable about the DS8000, SVC, and TPC.

This chapter describes the information you will need before deploying your SSPC. It provides
considerations for ordering IBM System Storage Productivity Center Version 1.1. It also
provides considerations for future growth and building an SSPC-like server with your own
Windows server.


2.1 Collecting configuration information
Before installation, you must ensure that you have all the required hardware and software
configuration information. You also need to plan for power, environmental needs, and server
placement.
1. If you need a keyboard, mouse, and display, order this package with 2805-MC2 server.
2. Ensure there is space in your rack with adequate airflow. Refer to “Environment
requirements” in IBM System Storage Productivity Center Introduction and Planning
Guide, SC23-8824.
3. Order the correct power cord to connect to the rack power.
4. Note the EIA Location of the IBM System Storage Productivity Center server, and optional
keyboard, video, and mouse (Table 2-1).

Table 2-1 EIA Location of the SSPC and keyboard, video, and mouse
Item Slot Floor grid

SSPC hardware location within EIA Slot:_________________ Floor Grid:_______________
the frame

Keyboard, Video, Mouse EIA Slot:_________________ Floor Grid:_______________
switch location

5. When registering your Windows software running on the SSPC server, you will be asked
the name of the person who the software will be registered to and the name of the
organization that owns the SSPC server.
During initial power-on of the SSPC server, you will be prompted to enter the Windows
Server® 2003 Product Key. The key is listed on a sticker labeled “Windows SVR Ent 2003”
and is located on the outside of the top cover of the SSPC server. Record this value before
the server is installed in the rack. Record the information in Table 2-2.

Table 2-2 Windows 2003 software registration information
Field Entry Notes

Administrator’s name This is the name of the person
________________________ who will be registered for the
Windows Server 2003 software.

Organization ________________________ This is your company name.

Windows Server 2003 product Needed during initial
key configuration of the SSPC
server.

6. You will need information about the network configuration of the SSPC server, such as the
host name (MANNODE is the default and may not have to be changed) and the IP
address. Gather the required information listed in Table 2-3.

Table 2-3 IP address and host name
Field IP address or host name

SSPC Host Name:________________

SSPC IP address IP address: ____.____.____.____

Subnet Mask IP address: ____.____.____.____


Field IP address or host name

Default Gateway IP address: ____.____.____.____

Preferred DNS IP address: ____.____.____.____

Preferred DNS name suffix
Example: sspc.ibm.com

Alternate DNS IP address: ____.____.____.____

Alternate DNS name suffix
Example: ibm.com

7. SSPC provides an improved DS8000 and SVC configuration. Using TPC installed on your
SSPC server, you can add, manage, and launch the element managers for administering
storage subsystems. From a planning perspective, you should record the IP addresses of
the element managers to be launched in Table 2-4.

Table 2-4 DS8000 and SVC device information
Device type Attached device IP address

DS8000 System Name/ Host Name IP address:
SVC
__________________ ____.____.____.____
Other

SVC
__________________ ____.____.____.____
Other

SVC
__________________ ____.____.____.____
Other

SVC
__________________ ___.____.____.____
Other

SVC
__________________ ____.____.____.____
Other

SVC
__________________ ____.____.____.____
Other

8. There is no antivirus installed in the SSPC. You can install antivirus packages like Norton
or McAfee to meet your company’s security policy. You should also consider backup and
recovery procedures for the SSPC, as described in Chapter 5, “Managing your SSPC
appliance” on page 83.
9. There is no HBA installed in the SSPC because the TPC Server does not require an HBA.
When upgrading to TPC Standard Edition or TPC for Data customers, you need HBAs in
the computers being monitored, but there is not a requirement for one in the SSPC.

Chapter 2. Planning for SSPC install 15

2.2 SSPC and TPC Basic Edition relationship
IBM 2805 System Storage Productivity Center Model MC2 is a combination of hardware and
software that initially will support device configuration of the IBM System Storage DS8000
series, and the IBM System Storage SAN Volume Controller (SVC) 4.2.1. Aside from basic
device configuration, the integration of TPC provides SAN management capabilities for
numerous heterogeneous storage elements.

License considerations
IBM System Storage Productivity Center Version 1.1 consists of one IBM System Storage
Productivity Center server (machine type 2805) and one license of IBM TotalStorage
Productivity Center Basic Edition V3.3.1 software, which comes pre-installed on the 2805
server. IBM TotalStorage Productivity Center Basic Edition is licensed per management
server and is not based on capacity.

If you order one license of TPC Basic Edition, you are then entitled to install and use the TPC
Basic Edition code on one system only. There is no limit as to the number of DS8000 clients
you are entitled to. The SVC Master Console client is recommended to two clients due to this
CIMOM limitation.

If you want two SSPC servers, you need to order two licenses of TPC Basic Edition. You are
then entitled to install and use the TotalStorage Productivity Center Basic Edition server code
on two systems.

Existing TPC installations can use their existing TPC server and TPC software license to
perform the remote configuration of new DS8000s using the GUI once TPC is upgraded to
V3.3.1. The TPC installation must have IP connectivity to the new DS8000. Keep in mind that
TPC software is licensed by capacity. If an existing TPC customer adds a new DS8000, they
will likely need to purchase additional TPC capacity if they do not have enough spare
capacity.

2.3 SSPC server options
In this section, we describe the options available for SSPC hardware and software.

2.3.1 Options for SSPC server hardware
The 2805 IBM System Storage Productivity Center is a platform for managing IBM storage
devices. The 2805 is an IBM System x™ x3550 server that is preloaded with IBM
TotalStorage Productivity Center Basic Edition.

Figure 2-1 on page 17 shows the SSPC server as shipped. An IBM System Service
Representative (SSR) will install this in your rack and connect the power cord to it. You should
also run the Ethernet cable to the server and allow the SSR to plug in the cable.


Figure 2-1 SSPC server, 2805-MC2

The hardware of the SSPC server is a Machine Type 2805-MC2. It is an IBM System x x3550
1U high rack-mounted server. It has one Quad-Core Intel Xeon® Processor E5310 (1.60 GHz
8 MB L2 1066 MHz 80 W), 4 GB of memory, two 3.5" hard disk drives of 146 GB 15K rpm
SAS HDD in a RAID 1, optical drive CD-ROM, and dual integrated 10/100/1000 Mbps
Ethernet.

This hardware configuration is sized for the TPC Basic Edition. TPC Basic Edition is TPC for
Disk without the Disk performance function and TPC for Fabric. TPC Basic Edition does not
include TPC Data and there is no Agent Manager.

Performance Upgrade Kit
There is a Performance Upgrade Kit (Feature Code 1800) for the 2805-MC2. This
Performance Upgrade Kit doubles the CPU and RAM of the server. The SSPC server with
feature code 1800 will have two Quad-Core Intel Xeon Processors and 8 GB of memory. You
need to purchase the Performance Upgrade Feature if you plan to upgrade your SSPC to
TPC Standard Edition or install TPC for Replication on the SSPC server. TPC Standard
Edition consists of TPC for Disk, TPC for Fabric, TPC for Data, and Agent Manager. TPC for
Replication helps you manage the advanced copy services provided by IBM ESS model 800,
IBM DS8000, IBM DS6000™, and IBM SVC. The Performance Upgrade Feature provides
more system resources for the additional workload.

Optional console and keyboard
There is also a Console Keyboard/Display/Drawer (feature code 9100) for the SSPC. You
need this feature if you install the SSPC server in a rack without a display and a keyboard.

Figure 2-2 shows a listing of the SSPC server options.

Description Machine Model Feature
-------------------------------------- ------- ----- -------
System Storage Productivity Center 2805 MC2

Performance Upgrade Kit 1800

Console/Keyboard/Display/Drawer 9100

Figure 2-2 2805-MC2 hardware features


2.3.2 SSPC software options and licenses
The IBM System Storage Productivity Center (server) includes the following pre-installed
software:
Microsoft Windows 2003 Server Fix Pack 2
DB2 Enterprise Server Edition V9.1 with Fix Pack 2
IBM System Storage SAN Volume Controller (Console and CIM Agent V4.2.1)

TPC Basic Edition is TPC for Disk without the disk performance feature and TPC for Fabric.
TPC for Data is not installed. Agent Manager is on a CD but not installed.

TPC Basic Edition does not restrict the customer on the amount of managed storage; it is
unlimited. Keep in mind that if an existing TPC customer upgrades to TPC V3.3.1 and adds a
new DS8000, they will likely need to purchase additional TPC capacity if they do not have
enough spare capacity.

If the SSPC integrated TPC Basic Edition is upgraded to TPC for Disk, TPC for Fabric, TPC
for Data, or TPC Standard Edition, the license changes to a per TB model. The pricing
depends on what product is selected and the amount of managed storage. To upgrade the
TPC Basic Edition, a license for the additional function needs to be purchased and installed.

TPC for Data requires Agent Manager to be installed and Data agents deployed to hosts
where file information is to be collected.

The TPC for Fabric (in-band fabric) function will require the installation of Agent Manager and
at least one Fabric agent deployed per zone on hosts where in-band fabric information
collection is desired.

2.4 Planning for the future
TPC Basic Edition includes the following high level features:
IBM System Storage DS8000 series GUI integration
SAN Volume Controller Master Console and CIMOM
Storage topology viewer
Monitor, alert, report, and provision storage
Status dashboard

2.4.1 Licenses
All distributed software licenses include Software Maintenance (Software Subscription and
Technical Support) for a period of 12 months from the date of acquisition, providing a
streamlined way to acquire IBM software and ensure technical support coverage for all
licenses. Extending coverage, for a total of three years from date of acquisition, may be
elected.

TPC Basic Edition is licensed per management server and is not based on capacity. IBM
TotalStorage Productivity Center Basic Edition can be configured to access any number of
DS8000 GUIs. In most environments, a single SSPC can manage all the DS8000s within the
enterprise. Even in large enterprise environments, the SSPC is sized to handle the Topology
Viewer, along with asset and capacity reporting.


You order one IBM System Storage Productivity Center (machine type 2805) and one license
of TPC Basic Edition software, which comes pre-installed on the 2805 server. The 2805
server license does not include the software license. The separate purchase of the TPC Basic
Edition software license is required. You are entitled to use the software on the 2805 server
and no other system. If you want to run TPC Basic Edition server code on any other server,
you are required to first disable the code on the 2805 server.

Using an existing TPC license
Consider the scenario where you order one SSPC (machine type 2805). You have previously
purchased TPC for Disk and want to use your existing software entitlement on the 2805
server. Since the TPC for Disk software license is based on capacity, assuming you have not
reached the software entitlement limit, the remaining software entitlement can be utilized on
the 2805 server. If you have utilized your previously purchased software entitlement, then you
will need to make an additional purchase of the desired TPC package.

Supported platforms
IBM System Storage Productivity Center (machine type 2805) is only offered with the
Microsoft Windows 2003 Enterprise Edition operating system. Consequently, only the
Microsoft Windows version of IBM TotalStorage Productivity Center server is supported on
that server.

IBM TotalStorage Productivity Center code is supported on Windows, AIX®, and Linux®. The
purchase of the TPC Basic Edition license does entitle the customer to install the server code
on any of the supported operating systems. However, the SSPC (2805) server is only
supported when running Microsoft Windows 2003 Enterprise Edition.

2.4.2 Server sizing
The purchase and use of an additional TotalStorage Productivity Center Standard Edition will
necessitate a solution assurance review (SAR). TotalStorage Productivity Center Standard
Edition includes TPC for Disk, TPC for Data, and TPC for Fabric. TPC for Replication is a
separate software product for Advanced Copy Services. To size your server to handle your
workload, go to the TPC Web site at:
http://www-304.ibm.com/jct01004c/systems/support/storage/software/tpc/

Select a product, then click the Install/use tab. Click Best Practices and look for the
document titled “Server Sizing Charts.” You can also contact your IBM Tivoli Storage team.

2.5 Building a SSPC like server
You have the option to build your own SSPC like server. You can order the TPC Basic Edition
without the 2805-MC2. If you plan to order only the TPC Basic Edition software, you should
order through IBM Passport Advantage® using the order number listed in Figure 2-3.

Product Description
5608-B01 IBM TotalStorage Productivity Center Basic Edition V3.3.1 1 Year
5608-B04 IBM TotalStorage Productivity Center Basic Edition V3.3.1 3 Years
Figure 2-3 SSPC software product code


You can install TPC Basic Edition on your OEM Windows 2003 Enterprise Edition server. You
can choose a server with CPU, memory, and hard drive compatible with the IBM SSPC
server. IBM SSPC server hardware is listed in 2.3.1, “Options for SSPC server hardware” on
page 16.

The procedure to install the SSPC software is described in Chapter 4, “Building an SSPC
server” on page 45.

Java versions
The TPC Basic Edition has the IBM V1.4.2 JRE™ in the source code. Your OEM server may
not support the IBM V1.4.2 JRE. During install, you may encounter the error message shown
in Figure 2-4. To fix this Java error, you have to download and install the Version 1.4.2 Java
from the SUN Microsystem Web site.

Figure 2-4 Java error message

2.6 SVC requirements
At this time, SSPC is an alternative to the current SVC Master Console. SSPC includes SVC
V4.2.1 Master Console and CIMOM agent. It can manage up to two 8-node clusters.

If you have an existing SVC Master console and CIMOM and clusters at a level prior to
V4.2.1, you can upgrade to V4.2.1 to manage your SVC clusters. You do not need to
purchase SSPC.

In the first half of 2008, SSPC will become compulsory for any new orders of SVC clusters.

SSPC can manage up to two 8-node clusters. If you have more than two clusters, you need to
purchase an additional SSPC or install an additional SVC Master Console and CIMOM.

2.7 Existing TPC environment and integration of SSPC
Installations that have an existing TPC installation, with the exception of TPC Limited Edition,
will likely not need to order SSPC. TPC customers should upgrade to TPC V3.3.1 and use the
Element Manager in V3.3.1 to access the DS8000 GUI.

TPC V3.3.1 supports the following DB2 versions for the repository database:
DB2 Enterprise Server Edition Version 8.1 with Fix Pack 14 or
DB2 Enterprise Server Edition Version 9.1 with Fix Pack 2

If you have a server with TPC Limited Edition and want to upgrade to TPC Basic Edition or
another TPC package (TPC for Data, TPC for Disk, TPC for Fabric, or TPC Standard Edition),
you need to un-install TPC Limited Edition and DB2 and then install DB2 and TPC Basic
Edition or Standard Edition on this server.


Existing TPC installations can use their existing TPC server and upgrade to TPC V3.3.1 and
use the existing TPC software license to perform the management of new DS8000s using the
GUI and TPC functions. TPC software is licensed by capacity. If you add a new DS8000, you
may need to purchase additional TPC capacity.

If you have TPC running on an AIX or Linux server and want the Element Manager for the
new DS8000, you can upgrade to TPC V3.3.1 and use the Element Manager in TPC V3.3.1
on the AIX or Linux server. Only the SVC Master Console needs to run on a Windows server.

2.8 DS8000 Element Manager GUI
You can launch the Element Manager as described in Chapter 6, “TPC Basic Edition
functions” on page 105. The Element Manager allows you to access the DS8000s in your
enterprise. Each entry is one DS8000 with one login user ID and its password. The DS8000
user ID and password is also stored in the Element Manager.

In the Element Manager main window, select Select → Create Element Manger. The
window shown in Figure 2-5 will appear. Fill in the IP address, user ID, and password fields
and click OK. The Element Manager tests the connection, the login ID, and password, and
then keeps them. You need the password when you want to sign in next time. All you have to
do is click the Element Manager entry shown in Figure 2-5. For DS8000 Element Manager
security considerations, refer to “DS8000 Element Manager access” on page 91.

Figure 2-5 Create Element Manager


2.9 Redundant SSPCs
SSPC is a management server. If SSPC stops working, the storage subsystems it manages
are not impacted. The only impact is you cannot manage your storage subsystems from
SSPC. You have to use alternative management methods until your SSPC server is restored.
For example, you may have to go to your HMC to manage your DS8000. This may cause a
temporary inconvenience for storage administrators.

You can deploy two SSPC severs in your environment. You need to set up identical entries in
the Element Manager and for SVC Master Consoles. If one SSPC fails, you can switch to the
other SSPC using the URL of the second SSPC.

There is no heartbeat between the two SSPCs and there is no high availability for the two
SSPCs. There is no clustering of the two SSPCs.

2.9.1 Single SSPC instance
If the temporary SSPC outage is acceptable in your environment, you should choose a single
SSPC configuration. The advantage of this configuration is there is no duplication of SSPC in
the environment and initial setup cost is lower. A single SSPC configuration is outlined in
Figure 2-6. In this configuration, SSPC and the management interface of SVC and DS8000
are all connected to the same LAN. SSPC communicates with SVC and DS8000 through
Ethernet.

SSPC

LAN

SVC Cluster

DS8000

Internal
HMC

Figure 2-6 Single SSPC configuration

If the temporary outage is not acceptable in your environment, you may need dual SSPC
configuration. By introducing the second SSPC, the single point of failure can be removed. In
the situation where the first SSPC instance is not working, you can use the second SSPC to
manage your storage subsystems.

2.9.2 Dual SSPC instances
Dual SSPC configuration is outlined in Figure 2-7 on page 23. In this configuration, both
SSPC instances communicate with the SVC and DS8000 independently. There is no
communication between the two SSPCs by default. You must update any configuration
information (for example, adding additional DS8000 Element Managers, SVC Master
Consoles, or CIMOMs) on each SSPC.


If one SSPC stops working, you can go to the second SSPC and manage your systems from
there. This is equivalent to having have two remote controllers for your television. If one
remote controller stops working, you may simply use the other remote controller.

SSPC SSPC

LAN

SVC Cluster

DS8000

Internal
HMC

Figure 2-7 Dual SSPC configuration


3

Chapter 3. SSPC initial setup
This chapter takes you through the process of setting up the SSPC server when it is powered
up. We will go through the steps to set up the Windows environment, change the host name
of the server, and change the IP address.


3.1 Initial SSPC setup
Your CE will install the SSPC in the rack, connect the power to the SSPC server, and plug in
the Ethernet cable. The CE will also install the optional keyboard, video, and mouse to the
SSPC if ordered. After the system is installed, you must configure it before you can use it.

You will need the planning information described in Chapter 2, “Planning for SSPC install” on
page 13. You need to gather the information and fill in the forms. We will walk you through the
steps to set up the Windows Operating System with SSPC.

Push the power on switch and wait for Windows to boot up. The first window you will see is
Figure 3-1. Click Next to continue.

Figure 3-1 Windows setup window

In Figure 3-2 on page 27, check the I accept the agreement button and click Next to
continue.


Figure 3-2 License Agreement

The next window is the Regional and Language options, as shown in Figure 3-3. Check
Customize to update the Regional and Language Options.

Figure 3-3 Regional and Language Options

Chapter 3. SSPC initial setup 27

The next window is the Regional and Language Options, as shown in Figure 3-4. In the
Regional Options tab, you can specify the format of numbers, currencies, dates, and time.

After you have updated the Custom and Details, click Next to go to Figure 3-8 on page 30.
Update the Regional and Language Options for your installation environment.

Figure 3-4 Regional Options

Figure 3-5 on page 29 shows the Languages tab. Click Details to take you to the Text
Services and Input Languages window, as shown in Figure 3-6 on page 29.


Figure 3-5 Language tab

In the Text Services and Input Languages window, select the language for the SSPC from the
drop-down menu. In the Installed services window, select the keyboard languages for the
SSPC, as shown in Figure 3-6.

Figure 3-6 Text Services and Input Languages


Figure 3-7 shows the options of the Advanced tab. After you have made all the necessary
language changes, click Apply to continue.

Figure 3-7 Advanced tab

In Figure 3-8, enter the name of this SSPC server and your organization. The default host
name is MANNODE. In our installation, we chose SSPC for the server name.

Figure 3-8 Personalize Your Software window

Figure 3-9 on page 31 is where you enter the product license key information, as mentioned
in 2.1, “Collecting configuration information” on page 14.


The Windows Server 2003 Product Key is listed on a sticker labeled Windows SVR Ent 2003
located on the outside of the top cover of the SSPC. It was recorded in 2.1, “Collecting
configuration information” on page 14. Enter this value now and click Next to continue.

Figure 3-9 Product License Key window

The next window is the Licensing Modes window, as shown in Figure 3-10. We accepted the
defaults and click Next to continue. For detailed information, refer to the Microsoft Web site on
Licensing Overview for Windows Server 2003:
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/overview.mspx

Figure 3-10 Licensing Modes


The next window is the Computer Name and Administrator window shown in Figure 3-11.
Here is where you enter the SSPC host name and Administrator password. Install this
Windows Operating System for SSPC using MANNODE as the host name, as this is the
name used when building the SSPC image. Change the server name after the initial
customization. Fill in the space to the left of Computer name as MANNODE. Note that the
Administrator password is passw0rd by default. You must use the default of passw0rd when
you first log in to the SSPC even if you specify another password here.

Figure 3-11 Computer Name and Administrator Password

Figure 3-12 shows the Computer Name and Administrator Password fields filled in. Enter
MANNODE in the Computer name field. This is the host name for the SSPC. Click Next to
continue.

Figure 3-12 Computer Name and Administrator Password


The next window is the Date and Time Settings window. Update the Time Zone and Date &
Time fields to reflect your SSPC server environment. Click Next to continue.

Figure 3-13 Date and Time Settings

The next steps are to set up the network. You need the information in Table 2-3 on page 14 to
set up the IP address, net mask, default gateway, and DNS of the SSPC server. In the
Networking Settings window shown in Figure 3-14, select the Custom settings button and
click Next to continue.

Figure 3-14 Network Settings


The next window is Networking Components, as shown in Figure 3-15. Click Internet
Protocol (TCP/IP) and then click Properties to continue.

Figure 3-15 Update IP information

In Figure 3-16, check the Use the following IP address and Use the following DNS server
address buttons. Enter the IP address, Subnet mask, Default Gateway, Preferred DNS
server, and Alternate DNS server information that you noted in Table 2-3 on page 14. Click
Advanced to continue.

Figure 3-16 IP and DNS information

Clicking the DNS tab provides the option to enter the DNS server addresses, in order of use
and Append these DNS suffixes (in order): information, as shown in Figure 3-17 on page 35.
You can list the DNS servers by IP address that the server will query to resolve the DNS


domain names. You can also specify the DNS suffixes that will be searched, in the order they
are listed. When all the information is entered, click OK to continue.

Figure 3-17 DNS Suffix information

The next window is the Workgroup or Computer Domain, as shown in Figure 3-18. We
selected the default of a workgroup named WORKGROUP and click Next to continue.

Figure 3-18 Workgroup or Computer Domain

The next window shows that you have successfully completed the Windows Setup, as shown
in Figure 3-19. Click Finish to restart the SSPC in order for the options you specified to take
effect.


Figure 3-19 Windows Setup complete

When the SSPC reboot is complete, you will see the main IBM System Storage Productivity
Center window, as shown in Figure 3-20.

Figure 3-20 SSPC after Windows setup configurations


3.2 Change the host name
When you received your SSPC server, the default host name is MANNODE. In this section,
we describe the steps to change the host name of the SSPC server from the default of
MANNODE to SSPCSRV. Note that the SVC Master Console has the name MANNODE by
default. If you have an existing SVC Master console in your environment, this will cause a
conflict.

The steps we described here are to change the Windows operating system to the new host
name. Then change DB2 to the new host name. The screen captures show the steps to
change the host name from MANNODE to SSPCSRV.

If you decided to use a host name other than MANNODE, you may get an error message from
DB2 after reboot. The error message is SQL1042C, as shown in Figure 3-27 on page 40.
With the latest level of SSPC, this error message does not appear.

3.2.1 Change the host name in Windows
On your Windows desk top, point your mouse to the My Computer icon, right-click it, and
select Properties, as shown in Figure 3-21.

Figure 3-21 Select Properties on My Computer


The System Properties window appears. Click the Computer Name tab, as shown in
Figure 3-22.

Figure 3-22 Node name change

In the Computer Name window, click the Change button, as shown in Figure 3-23 on
page 39.


Figure 3-23 System Properties window Computer Name tab

Enter the new host name in the Computer name field, as shown in Figure 3-24. In our
environment, we want to change the name to SSPCSRV. Update the Workgroup information
for your installation if necessary and click OK to continue.

Figure 3-24 Computer Name Changes


A pop-up window informs you that you must reboot the system for the computer host name
change to take effect, as shown in Figure 3-25. Click OK to continue.

Figure 3-25 Computer Name Changes

In addition, you will receive a pop-up menu asking you to restart the system. Click Yes to start
the reboot of the computer.

Figure 3-26 System Settings Change

3.2.2 Change host name in DB2
After the system reboot, the Windows operating system has the new computer host name of
SSPCSRV, but DB2 still has the old host name. DB2 will issue error message SQL1012C, as
shown in Figure 3-27. Click OK to continue and then we will change the host name in DB2.

Figure 3-27 DB2 error message

The steps to change the host name in DB2 are:
1. Update the DB2 command.
2. Stop and then restart stop the IBM WebSphere® Application Server V6 - Device server
and IBM TotalStorage Productivity Center - Data server services.

Update DB2
Changing the host name in DB2 involves entering several DB2 commands.

To open a command prompt window, select Start → Run and enter cmd in the Run window.
Click OK to continue, as shown in Figure 3-28 on page 41.


Figure 3-28 Command prompt window

Change to the directory where your DB2 is installed. By default this is C:Program
FilesIBMSQLLIB. Enter the following commands, as shown in Figure 3-29:
db2extsec /u db2users /a db2admns
db2start

Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

C:Documents and SettingsAdministrator>cd Program FilesIBMSQLLIB

C:Program FilesIBMSQLLIB>db2extsec /u db2users /a db2admns

DB2EXTSEC: processing completed successfully.

C:Documents and SettingsAdministrator>db2start

SQL1063N DB2START processing was successful.

Figure 3-29 Issue DOS commands and response

3.2.3 Stop and start services
You have to stop and then restart two Windows services for the DB2 host name change to
take effect. First, we have to stop the IBM WebSphere Application Server V6 - Device server
and IBM TotalStorage Productivity Center - Data server.

Select Start → Settings → Control Panel → Administrative Tools → Services to locate
the Services window.


In the Services window, scroll down to locate the services, as shown in Figure 3-30.

Figure 3-30 Locate IBM WebSphere Application Server V6 - DeviceServer and IBM TotalStorage
Productivity Center - Data server

Point your mouse to the IBM WebSphere Application Server V6 entry, right-click it, and click
Stop to stop the WebSphere services, as shown in Figure 3-31 on page 43.


Figure 3-31 Stop IBM WebSphere Application Server V6 - Device server

Repeat this process for the IBM TotalStorage Productivity Center - Data server service, as
shown in Figure 3-32.

Figure 3-32 Stop IBM TotalStorage Productivity Center - Data server service


You need to restart the IBM WebSphere Application Server V6 - Device server and IBM
TotalStorage Productivity Center - Data server services. Again, locate the services, highlight
the service you want to start with your mouse, right-click it, and select Restart.

Once the services successfully restart, you have changed the host name and can log in to the
TotalStorage Productivity Center console.

3.3 Connect SVC Master Console to SVC Clusters
Before you can manage your SVC clusters, you need to add your SVC clusters to your SVC
Master Console. The SVC Console and CIMOM are preinstalled on the SSPC server. Unlike
the DS8000 Storage Manager interface, the SVC Console is not accessed through TPC
Productivity Center. Instead, the SVC Console is launched separately from the SSPC server
desktop.

SSH keys are generated by the SSH client software. This includes a public key, which is
uploaded and maintained by the cluster, and a private key that is kept private from the server
that is running the SSH client; in our case, this is the SSPC. These keys authorize specific
users to access the administration and service functions on the cluster. Each key pair is
associated with a user-defined ID string that can consist of up to 40 characters. Up to 100
keys can be stored on the cluster. New IDs and keys can be added and unwanted IDs and
keys can be deleted.

To use the CLI or SVC graphical user interface (GUI), an SSH client must be installed on that
system, the SSH key pair must be generated on the client system, and the client’s SSH public
key must be stored on the SVC cluster or clusters. The SVC Master Console (and therefore
the SSPC server) has the freeware implementation of SSH-2 for Windows called PuTTY
pre-installed. This software provides the SSH client function for users logged into the master
console who want to invoke the CLI or GUI to manage the SVC cluster.

As part of the installation of the SVC Master Console code, an SSH key pair is generated
using PuTTYgen. You can use this key pair or you can generate a new key pair. We
recommend you generate a new key pair.

For details on creating a new SSH key pair using PuTTY, refer to Figure 4-37 on page 69. For
details on loading the public key to the SVC cluster, refer to 4.4.3, “Connect SVC Master
Console to SVC Clusters” on page 73.


4

Chapter 4. Building an SSPC server
If you choose not to order the SSPC 2805-MC2, it is possible to build an SSPC like server.
You can also use the information in this chapter to rebuild your SSPC from the product CDs.
This chapter provides the detailed procedure on how to accomplish these tasks.


4.1 SSPC build basics
If you decide to build your own SSPC Server, you need to install the following software on
your server:
IBM TotalStorage Productivity Center V3.3.1 Basic Edition
IBM System Storage SAN Volume Controller Console and CIMOM agent Version 4.2.1
DB2 V9.1

Before starting to build your own SSPC Server, you need to verify that your server meets the
following requirements:
The server has been physically installed and connected to the network properly.
Microsoft Windows 2003 Release 2 Server Enterprise Edition has been installed and
configured properly on your server.

4.1.1 Installation overview
In TPC, you have the following installable components:
Database schema
Data server and Device server
Graphical user interface (GUI)
Command-line interface (CLI)
Data agent
Fabric agent

You need to install most of these components in order to get TPC to work. The CLI is
considered optional. If you are using a remote database for TPC, you must install the
database schema on that remote database after you have installed DB2 on that remote
machine.

You need to install Agent Manager before deploying Data agents or Fabric agents. With TPC
V3.3.1, Agent Manger is an optional component and is installed separately from TPC.

The GUI is installed wherever a user might wish to invoke TPC. TPC also supports a Java
Web based GUI, which gives you the option of not having to install the GUI when you want to
remotely use TPC.

The DB schema, Data server, Device server, agents, GUI, and CLI are all components of
TPC. They can be installed all at once or individually. If you install the components at different
times, you must install the components in this order:
1. DB2 (DB2 is required for Agent Manager and IBM TotalStorage Productivity Center.)
2. DB schema (This is installed using the IBM TotalStorage Productivity Center installation
program.)
3. Data server and Device server (This is installed using the IBM TotalStorage Productivity
Center installation program.)
4. Agent Manager (This is an optional component.)
5. Data agent, Fabric agent, GUI, or CLI (Data agent and Fabric agent can only be installed
if Agent Manager is installed.)


In this chapter, we install TPC without Agent Manger. As a result, the Data agent and Fabric
agent cannot be deployed. If deploying agents is required in your environment, refer to
Chapter 7, “Upgrading SSPC and using additional functions” on page 187.

4.2 Install IBM DB2 Enterprise Server Edition V9.1
When you install DB2, two groups are created:
DB2ADMNS: This group will have all the required user rights assigned for administrative
authority.
DB2USERS: This group will have user rights assigned for DB2 users.

For the DB2 users that need administrative authority, add them to the DB2ADMNS group. For
normal DB2 users, add them to the DB2USERS group. When you add a user ID to either
group, this user ID will have all the user rights required for that group; you do not have to
assign individual user rights to each user ID.

During DB2 installation, DB2 automatically creates a DB2 user ID with administrative
authority. The default user ID is db2admin. This user ID and password will be the default user
ID and password used to install TPC.

If you do not want to use the default user ID to install TPC, you can create a new
administrative user ID, for example, tpcadmin. If DB2 creates this user ID, this user ID will be
added to the DB2ADMNS group and the Windows Administrators group.

4.2.1 Steps
DB2 is installed using a setup wizard. The setup wizard leads you through the entire
installation process. To install DB2, follow these steps:

Log on with a user ID with Administrator authority on Windows. Insert the DB2 product CD
into the CD-ROM drive or use the unzipped DB2 installation image. AutoRun starts the
LaunchPad. The DB2 installation program (see Figure 4-1 on page 48) should start within 15
- 30 seconds if you have AutoRun mode set on your system. If the installation program does
not start, do one of the following steps:
Use a command prompt to change to the root of the DB2 install CD and enter
db2setup.exe.
Use Windows Explorer, open the root of the CD, and double-click db2setup.exe.

Chapter 4. Building an SSPC server 47

Figure 4-1 DB2 setup window

Select Install a Product and click Install Now under DB2 Enterprise Server Edition, as

Figure 4-2 DB2 production selection

The DB2 Setup wizard window is presented (see Figure 4-3 on page 49). Click Next to
continue.


Figure 4-3 DB2 welcome window

The next window is the License Agreement, as shown in Figure 4-4. Select I accept the
terms in the license agreement and click Next.

Figure 4-4 DB2 License Agreement


The next window allows you to select the installation type, as shown in Figure 4-5. Select
Typical as the installation type and click Next to continue.

Figure 4-5 DB2 installation type

In the next window, shown in Figure 4-6, select Install DB2 Enterprise Server Edition on
this computer and click Next to continue.

Figure 4-6 DB2 installation options

By default, DB2 setup wizard installs DB2 Enterprise Server Edition in the folder C:Program
FilesIBMSQLLIB. If you do not want the default folder, you can type in the directory of your


choice, as shown in Figure 4-7. In our installation, we accept the default. Click Next to
continue.

Figure 4-7 DB2 installation folder

By default, DB2 uses db2admin as the DB2 administrator user ID. If you do not want to use
db2admin, you can type the user ID of your choice. In our installation, we accepted the
default.

By default, Use the same user name and password for the remaining DB2 services is
checked. We accept the default. In Figure 4-8, type the password for db2admin and record it.
Click Next to continue.

Figure 4-8 DB2 user window


In the Configure DB2 instances window, the default instance is DB2. Leave the default
instance unchanged and click Next (see Figure 4-9).

Figure 4-9 DB2 instance window

By default, Prepare the DB2 tools catalog is unchecked. TPC does not require DB2 tools,
so we accept the default. If you later need DB2 tools for other applications, you can install
DB2 tools separately.

In Figure 4-10, make sure that Prepare the DB2 tools catalog is unchecked and click Next.

Figure 4-10 DB2 tools


By default, Set up your DB2 server to send notifications is checked. In our installation, we
uncheck it. If notification is required in your environment, you can enable it.

In Figure 4-11, uncheck Set up your DB2 server to send notifications and click Next.

Figure 4-11 E-mail notification window

By default, Enable operating system security is checked. It creates two user groups: one is
the DB2 administrators group and one is the DB2 users group, as shown in Figure 4-12.
DB2ADMNS is the default group name for the DB2 administrators group. DB2USERS is the
default group name for the DB2 users group. In our installation, we accept the default. If you
do not want the default group name, you can type the group name of your choice.


Figure 4-12 DB2 Administrators and Users group


In Figure 4-13, verify the DB2 installation information and click Install to continue.

Figure 4-13 DB2 installation information

Clicking the Install button starts the DB2 installation. Wait until the installation is finished
(Figure 4-14).

Figure 4-14 DB2 installation process

When installation process is finished, click Finish, as shown in Figure 4-15 on page 55.
Reboot your server to complete the DB2 installation.


Figure 4-15 Setup process completed

4.3 Installation of TPC V3.3.1 Basic Edition
TPC provides an installation program that guides you through the installation process. If you
are installing TPC using the electronic images, there are three installation images:
disk1: Contains all the TotalStorage Productivity Center components, except for the
remote Data agent bundles.
disk2: Contains the files to perform remote Data agent installations. These files are
automatically installed when you install the servers for TotalStorage Productivity Center.
Disk2 also contains the JVM™ for the Java Web Start application for the Device server.
disk3: Contains the files to perform local agent installations.

If you are installing TPC using DVD and CD, the DVD Contains disk1 and disk2 and the CD
contains disk3.

To start the TPC installation program with DVD, go to <DVD_drive>disk1 and double-click
setup.exe.

To start the TPC installation program with Windows electronic image, download the electronic
image into a directory, unzip the file, and run setup.exe from the source installation directory.


Once the installer is invoked, the Select a language window is displayed, as shown in
Figure 4-16. Select a language from the drop-down list and click OK to continue. This is the
language that is used for installing this product.

Figure 4-16 Language selection window

The next window is the Software License Agreement window, as shown in Figure 4-17. Read
the terms of the license agreement. If you agree with the terms of the license agreement,
select I accept the terms of the license agreement and click Next.

Figure 4-17 License Agreement window

The next window is the Select the type of installation window, as shown in Figure 4-18 on
page 58. You can install the IBM TotalStorage Productivity Center components using Typical
installation or Custom installation.

The Typical installation requires a minimum amount of input from the user who installs
TotalStorage Productivity Center. You install the components in groups on the local computer
by selecting Servers, Agents, Clients and Register with the agent manager. The following
list gives the components installed by each group:
Servers installs the database schema, Data server, and Device server.
Agents installs the Data agent and Fabric agent. (You can only select it when you have
previously installed Agent Manager.)
Clients installs the TotalStorage Productivity Center GUI and CLI.


Register with the agent manager registers the Device server and Data server with the
Agent Manager. (You can only select it when you have previously installed Agent
Manager.)

In the Custom installation, you can select the components required in your environment from
the following list:
Create database schema
Data server
GUI
Data Agent (if you have Agent Manager installed)
Device server
CLI
Fabric agent (if you have Agent Manager installed)
Agent Manager Registration (if you have Agent Manager installed)

You can only select Data Agent, Fabric agent, and Agent Manager Registration if you have
installed Agent Manager previously. If you select Data Agent or Fabric agent, the Agent
Manager Registration box is checked automatically.

The two installation modes also handle passwords differently. The following list gives the
passwords required for TPC installation:
Database administrator user ID and password for Data server and Device server to
connect to the database.
Database user ID and password to create database schema.
Host authentication password for Fabric agents to communicate with Device server. Host
authentication password is also used for TPC rollup reporting.
Data server Account Password for the Data server service. When you supply this
password, the TPC installation program uses the password you supplied to create the
Data server service account on Windows. Date server service runs under this service
account.
The WebSphere Application Server admin ID and Password is the user ID and password
required by the Device server to communicate with embedded WebSphere. This is only
used at installation time.

In the Custom installation, you are allowed to specify passwords for each password request
listed above. In the Typical installation, you can only specify one user ID and password. The
installation program uses the same password for each password request listed above.

In general, we recommend that for a production environment you use Custom installation for
installing IBM TotalStorage Productivity Center. Custom installation allows you to see what
components are being installed as well as set different passwords for user IDs.


In our installation, we select Custom installation, as shown In Figure 4-18, and click Next.

Figure 4-18 Installation type

Select Create database schema, Data Server, Device server, GUI, and CLI, and click Next
(Figure 4-19). In the default SSPC installation, there is no Agent Manager installed.
Therefore, Data Agent and Fabric agent cannot be installed.

Figure 4-19 Components to install


During the DB2 installation, you created the DB2 administrator name and password
(Figure 4-8 on page 51). In Figure 4-20, type the DB2 administrator name and password you
created and click Next.

Figure 4-20 DB2 administrator information

In Figure 4-21, type the same DB2 administrator name and password and click Next. Note
that the Create local database is checked and has a database name of TPCDB.

Figure 4-21 Database schema information


As shown in Figure 4-22, the installation program can pick up the Data server name and
Device server name itself. Verify that the server names are correct. The default server port is
9549. This is assigned to the Data server and port 9550 is assigned to the Device server.
Verify the ports are available on your server. If the ports are not available, you can specify a
different server port, for example, 9569, which means the Device server is assigned the next
higher port number, which is 9570 in this case.

You need to enter an operating system group name to associate with the TPC superuser. This
group must exist on your operating system before you install TPC. This group provides full
access to the TPC product. You can assign a user ID to this group on your operating system
and log in the TPC GUI using this user ID. By default, the Administrators group is
automatically assigned to the TPC superuser. In our installation, we accept the default.

Enter the password of your choice in Host authentication password and keep your password
in a safe place. You will need this password when you deploy Fabric agents. This password is
used by Fabric agents to communicate with the Device server. You will also need this
password if you configure rollup reporting. The master TPC server uses this password to
collect information from this server to generate rollup reports.

Data server Account Password is used when the TPC installation program creates a user ID
for Data server service account on Windows. During installation, TPC installation program
creates a user account called TSRMsrv1. The password you supplied will be the password for
TSRMsrv1. After the installation is finished, the Data server runs under the user account
TSRMsrv1. Type a password of your choice.

The WebSphere Application Server admin ID and password is the user ID and password
required by the Device server to communicate with embedded WebSphere. This is only used
at installation time. Type a user ID and password of your choice.


Figure 4-22 TPC information


The next window is a summary of the parameters you have specified in the wizard. In
Figure 4-23, verify the installation information and click Install.

Figure 4-23 Installation information

In Figure 4-24, installation starts. Wait until the next window appears.

Figure 4-24 Installation started


When TPC disk2 is required (Figure 4-25), provide the directory of TPC disk 2 and click OK.

Figure 4-25 TPC disk 2 required

When the TPC installation is finished (Figure 4-26), click Finish and reboot your server.

Figure 4-26 TPC installation finished

4.4 SVC Console and CIMOM Agent V4.2.1 installation
This topic covers the tasks of installing SVC console and CIMOM.

Before you install SVC console, you need to install PuTTY. SVC console uses PuTTY to
communicate with the SVC clusters. PuTTY has to be installed before the SVC console can
be installed.

The SVC console and CIMOM agent are installed by an installation program. You need to log
in as an administrator to run the installation program.


4.4.1 PuTTY installation
In our installation, we downloaded the SVC V4.2.1 code software from the IBM site. We put
the software in the directory D:IBM-SVC-SMIS-Agent-4.2.1.736.

To install PuTTY, go to the directory D:IBM-SVC-SMIS-Agent-4.2.1.736SSHClientPuTTY,
and run putty-0.58-installer.exe, as shown in Figure 4-27.
.

Figure 4-27 PuTTY directory for install

The Putty Setup Wizard Welcome window appears, as shown in Figure 4-28. Click Next.

Figure 4-28 Welcome window


By default, PuTTY is installed in the directory C:Program FilesIBMPuTTY. To choose a
different directory, click Browse and select a different directory. After selecting the
destination directory, click Next (Figure 4-29).

Figure 4-29 Destination directory

The PuTTY installation program creates shortcuts in the Start Menu folder. PuTTY is the
default folder for the shortcuts. To choose a different folder, click Browse and select a
different folder.

In our installation, we accept the default. Click Next to continue, as shown in Figure 4-30.

Figure 4-30 Start Menu Folder


In Figure 4-31, you can select additional tasks you want to perform. By default, only
Associate .PPL files (PuTTY Private Key) with Pageant and PuTTYgen is selected.


Figure 4-31 Additional Tasks

Verify the installation information and click Install, as shown in Figure 4-32.

Figure 4-32 Installation information

In Figure 4-33 on page 66, click Finish button and the installation is finished.


Figure 4-33 Installation finished

4.4.2 SVC Console and CIMOM Agent installation
To set up the SVC Console and CIMOM Agent, go to the folder where the SVC code is stored
(we stored it in the directory D:IBM-SVC-SMIS-Agent-4.2.1.736W2k) and click setup.exe. It
brings up the Welcome window shown in Figure 4-34. Click Next in the License Agreement
window.

Figure 4-34 Welcome window


The next window is the License Agreement, as shown in Figure 4-35. Select I accept the
terms of the license agreement and click Next.

Figure 4-35 License Agreement

By default, SVC Console is installed in c:Program FilesIBMsvcconsole. To choose a
different directory, click Browse and select a directory.


After selecting the destination directory, click Next, as shown in Figure 4-36.

Figure 4-36 Destination directory

In Figure 4-37 on page 69, you are prompted for a PuTTY private key. The generation of the
PuTTY private key is not part of the installation program. You can leave the installation
program in its current state, go to PuTTY key generation program to generate PuTTY keys,
and then go back to the installation program.

To generate PuTTY keys, you need to perform the following steps on your server:
1. Start the PuTTY Key Generator by selecting Start → Programs → PuTTY → PuTTYgen.
2. Click SSH2 RSA as the type of key to be generated. The default value for Number of bits
in a generated key is 1024. Accept the default value.
3. Click Generate.
4. Move the cursor around the blank area of the Key section to generate a random number.
5. Click Save public key to save the public key.
6. Click Save private key to save the private key. When prompted to confirm that you want to
create the key without a passphrase, click Yes.
7. Close the PuTTY Key Generator.

After you generate the PuTTY keys, go back to the installation program. Click Browse to
locate the PuTTY private key and click Next to continue.


Figure 4-37 PuTTY private key file name

In Figure 4-38 on page 70, you are prompted for the CIMOM communication protocols. The
default configuration is to use both HTTP and HTTPS. The default port number for HTTP is
5988 and the default port number for HTTPS is 5989. Verify that the ports are available in
your server. If the ports are not available, you can specify different ports.



Figure 4-38 CIMOM port number

Figure 4-39 lists the default port number for the embedded WebSphere Application Server.
Verify the listed ports are available in your server. If the ports are not available, you can
specify different ports. In our installation, we accept the default. Click Next in Figure 4-39.

Figure 4-39 Port number for WebSphere Application Server


Figure 4-40 shows the installation progress. Wait until it finishes.

Figure 4-40 Installation started

Figure 4-41, shows that the installation is successful. Click Next, as shown in Figure 4-41.

Figure 4-41 Successful installation


After you click the Next button in Figure 4-41 on page 71, the postinstall.txt document is
displayed, as shown in Figure 4-42. This document provides you the information about what
to do next. Go through the document and close the window when you are finished reading it.

Figure 4-42 Post installation tasks

In Figure 4-43, click Finish and reboot your computer.

Figure 4-43 Installation finished


The installation tasks are finished. Your server has the same software installation as the IBM
SSPC solution.

4.4.3 Connect SVC Master Console to SVC Clusters
Before you can manage your SVC clusters, you need to add your SVC clusters to your SVC
Master Console. This topic gives you the details on how to add an SVC cluster to your SVC
Master Console.

After you install the SVC Master Console, start your Web browser and point to your SVC
Master Console IP address using port number 9080:
http://<ip>:9080/ica/login

A Web page is displayed asking you for a login name and password. The default is superuser
as the login name and passw0rd as the password (Figure 4-44). These are the default login
name and password after your initial installation.

After you type in the login name and password, click OK to continue.

Figure 4-44 Login window


After you successfully log in, you have a navigation tree on the left side of your Web browser.
Click Users, which shows that you only have one default user after your initial installation,
which is superuser (see Figure 4-45). If you are serious about security and do not want to use
the default login name and password, you can use the Add a User function to add users of
your choice.

Figure 4-45 User management


After you finish your user account setup, click Clusters. It shows you the clusters managed by
this SVC Master Console (see Figure 4-46). At this moment, there are no SVC clusters
because you have not added any SVC clusters into your SVC Master Console. Click the GO
button next to the Add a Cluster function.

Figure 4-46 Cluster management


In Figure 4-47, type the IP address of your SVC cluster. It is important that you do not check
Create (Initialize) Cluster function unless you really need to initialize your clusters. It will
erase all your current cluster configuration.

After you type the IP address, click OK to continue.

Figure 4-47 Add a cluster

When the security alert in Figure 4-48 pops up, click Yes to accept it

Figure 4-48 Security Alert

In Figure 4-49 on page 77. type the login name and password of your SVC cluster and click
OK.


Figure 4-49 Login window

In Figure 4-50, click Browse in the Add Key section to load the public key you created during
the SVC Master Console installation. The details about public key generation is shown in
Figure 4-37 on page 69.

Figure 4-50 Add key


After you locate the public key, type a unique ID of your choice (see Figure 4-51). This ID is
going to be used in the SVC clusters to identify your SVC Master Console.

In the Access Level, select administrator. Then click the Add Key button.

Figure 4-51 Upload public key


In Figure 4-52, it shows that the SVC cluster is successfully added to the SVC Master
Console.

Figure 4-52 Cluster managed


In Figure 4-53, select the SVC cluster you added and click the GO button next to the Launch
the SAN Volume Controller Console function.

Figure 4-53 Viewing clusters added

The SVC cluster management console appears, as shown in Figure 4-54 on page 81. It
provides you with a navigation tree. You can navigate to the functions you want and change
configurations based on your requirements.


Figure 4-54 SVC cluster management console

Figure 4-55 shows an error message we received during our installation. By default, the
installation wizard configures all the required Windows command paths.

Figure 4-55 SVC CMMUI8300E error message


SVC CIMOM is using the plink.exe program to send commands to SVC over the SSH
protocol. As plink.exe is used without full path specification in the command, it has to be
located in the system path.

You have two options:
1. Add a path where plink.exe is installed to the system PATH variable.
2. Copy plink.exe to the directory that is already included in the system PATH variable, for
example, C:WINDOWS.

For some reason in our installation, the path of PuTTY was not configured properly. If you run
into the same error message, you may need to check your Windows command path and
make sure the PuTTY directory is in your Windows command path. We copied plink.exe to
C:WINDOWS and the error was resolved.


5

Chapter 5. Managing your SSPC appliance
This chapter provides considerations on using SSPC in your environment. It includes the
following:
SSPC redundancy
Securing your SSPC
Upgrading your SSPC
Integrating your SSPC with an existing TPC environment
Backing up your SSPC


5.1 Securing your SSPC server
In a production environment, SSPC is normally the control point of the storage systems that
stores large amount of data. The security of the SSPC server is very important.

SSPC is designed to provide you with the maximum flexibility in implementing security
controls of your choice. In general, the security of SSPC should be implemented at multiple
layers. It should include but is not limited to the following components:
Application security
Operating system security
Network security

5.1.1 Application security
TPC supports application level security by using role-based authorization. TPC allows you to
assign different users with different roles. Each user can only perform the functions they are
allowed to perform based on their roles. This provides you the capability to segregate duties
between users.

TPC supports ten different roles. The details of roles and the permission associated with each
role is summarized in Table 5-1.

Table 5-1 TPC roles
Role Authorization level

Superuser This role has full access to all TPC functions.

Productivity center administrator The role has full access to operations in the administration
section of the GUI.

Tape Operator This role has access to reports only for TPC tape functions.

Tape Administrator This role has full access to TPC tape functions.

Fabric Operator This role has access to reports only for TPC fabric functions.

Fabric Administrator This role has full access to TPC fabric functions.

Disk Operator This role has access to reports only for TPC disk functions.

Disk Administrator This role has full access to TPC disk functions.

Data Operator This role has access to reports only for TPC data functions.

Data Administrator This role has full access to TPC data functions.

Log in to TPC with a user ID that belongs to the Windows Administrators group, and in the
Navigation Tree, select Administrative Services → Configuration → Role-to-Group
Mappings. You can see the roles available in Figure 5-1 on page 85.


Figure 5-1 Roles available in TPC

Operating system groups are used in role-based authorization. If you need to create a role,
you just pick an operating system group and map it to a role listed in Table 5-1 on page 84.
When a user logs into TPC, TPC verifies the group membership of the user. Based on the
operating system group membership, TPC assign the user permissions.

Figure 5-1 shows the configuration of Role-to-Group Mapping after the initial setup. The only
group assigned is the Administrators group, which is assigned to the Superuser role in TPC.
This is because we specified the Administrators group to have the Superuser role during TPC
installation (see Figure 4-22 on page 60).This configuration gives every user in the
Administrators group the Superuser role.

One of the first tasks you should perform after installing IBM TotalStorage Productivity Center
is to assign roles to individuals who will use the product. Because the Administrators group
has already mapped to the Superuser role, what you need to create a TPC superuser ID is to
create an OS user ID and add this user to the Administrators group. When the user
authenticates with TPC, the user’s membership in Administrators group gives the user the
TPC Superuser privilege.

Based on the requirement of your environment, you may also need to create users with
different permissions, such as Fabric Operator or Disk Administrator. You need to perform the
following steps to create an user ID with a specific TPC role:
1. Create an operating system user ID.
2. Create an operating system group.
3. Add the user ID to the operating system group.
4. Map the group to a TPC role.

Chapter 5. Managing your SSPC appliance 85

Create a user to manage TPC and Element Manager
To provide more details about role based authorization, we show you an example in this
section. In our example, we create a user called diskadmin and assign diskadmin the disk
administrator role.

Right-click My Computer and select Manage (Figure 5-2).

Figure 5-2 Create new user ID (step one)

In the next window, right-click Users, and select New Users (Figure 5-3).

Figure 5-3 Create new user ID (step two)

In Figure 5-4 on page 87, enter the required information (user ID, password, and description)
and click Create to create a new Windows user account called diskadmin.


Figure 5-4 Create new user ID (step three)

After you create a new user, the next step is to create a new group. In the Computer
Management window, right-click Groups and select New Group (Figure 5-5).

Figure 5-5 Create new group (step one)


In Figure 5-6, type Disk Administrators as the group name and add diskadmin to this group,
and then click Create.

Figure 5-6 New group (step two)

Assign the TPC role to a user ID
Log in to TPC using the TPC Superuser ID, go to Role-to-Group Mappings, and click Edit
next to the Disk Administrator (see Figure 5-7).

Figure 5-7 Role-to-Group Mappings

Type Disk Administrators as the group name for the Disk Administrator role and click OK to
continue (Figure 5-8 on page 89).


Figure 5-8 Group name

In the TPC Role-to-Group Mappings window, you can see the Disk Administrators group is
added to the Disk Administrator role. Click the disk icon in the menu bar to save the change
(Figure 5-9), and then close the TPC GUI.

Figure 5-9 Save the change in TPC


Log in to TPC using the newly defined user ID diskadmin. Now you see the TPC window

Compare this TPC window with the TPC window you have when you log in with the TPC
Superuser role (Figure 5-1 on page 85). You can see Fabric Manager and Tape Manager
functions are not available in the new window. This is because you are now a disk
administrator and you are not allowed to manage Fabric or Tape. Also, you have fewer
Configuration functions because you are now only a disk administrator instead of a TPC
superuser. In summary, only disk administrator related functions are available in TPC when
you log in using diskadmin.

Figure 5-10 TPC navigation tree for disk administrator


DS8000 Element Manager access
If a new user signs in for the first time with an expired password, the DS8000 Element
Manager prompts the user for a new password, as shown in Figure 5-11.

Figure 5-11 First time login prompt password change


Figure 5-12 shows the DS8000 Element Manager Welcome window.

Figure 5-12 Element Management

If you enter an incorrect password, the user ID is locked, or the password in the DS8000 has
expired, you will get the login error message HWNEM0104E, as shown in Figure 5-13 on
page 93.

You can set up the user IDs and the password in the DS8000. You can also setup the
authority of each user in the DS8000. You will need one user and password to set up the
Element Manager. The user ID and password for the Element Manager is stored in the TPC
database. Any subsequent login from the Element Manager within TPC uses that one stored
user ID and the privileges associated with it.

For the duration of a TPC session, if you log in to the DS8000 through the Element Manager,
and then close out the DS8000 GUI and log back in to the Element Manager with a different
account on the DS8000, the privileges of the first account to log in are retained. You must
close out the TPC session to disassociate the first account to log in from the DS8000 GUI.

If your entry in the Element Manager is using an ID with administrator privileges in the
DS8000, anyone logging in through the Element Manager will have administrator privileges
for the duration of the TPC session. If you do not want anyone to log in with administrator
rights, you have two options: You can remove the entry in the Element Manager, as shown in
Figure 5-15 on page 95, or you can change the entry in the Element Manager to an user ID
with only Monitor rights, as shown in Figure 5-16 on page 96.


Figure 5-13 Login error

If your user ID has only Monitor authority and you try to change the configuration, you will get
an error message, as shown in Figure 5-14 on page 94.


Figure 5-14 User with Monitor authority tried to make changes in the DS8000 Element Manager

Figure 5-15 on page 95 shows the option to Remove Element Manager through the Select
action drop-down menu.


Figure 5-15 Selection to remove the entry in Element Manager

Figure 5-16 on page 96 shows the option to Modify Element Manager through the Select
action drop-down menu.


Figure 5-16 Selection to modify the entry in the Element Manager

After selecting to Modify Element Manager, you are presented the window where you can
modify the DS8000 Element Manager specifics (see Figure 5-17 on page 97).


Figure 5-17 Pop-up window to modify the Element Manager user entry

5.1.2 Operating system security
SSPC is built on top of a standard Windows 2003 installation. There is no customization at
the operating system level. This gives you the maximum flexibility in implementing operating
system security based on the security requirements in your environment.

SSPC has the following software running on top of Windows 2003 at the time of the writing of
this book:
DB2 Enterprise Server Edition V9.1 with Fix Pack 2
PuTTY 0.58
IBM System Storage SAN Volume Controller (SVC) Console and CIMOM Agent V4.2.1.

When you design operating system security, basically you can do whatever your security
policy requires you to do as long you give adequate permission for the installed software to
run properly on your server.

If your security policy requires you to install antivirus software, you can simply consider SSPC
as a standard Windows server and deploy the antivirus solution of your choice.


5.1.3 Network security
Securing the management interface of your storage devices is very important to your overall
security. If a malicious user obtains full control of your SSPC or DS8000, you may end up with
service interruptions or loss of data.

It is a good practice to put your SSPC and the management interfaces of your storage
devices in a secured network. We also recommend having a periodical security audit of your
storage network. This can keep you informed about any potential security issues and allow
you to mitigate any security exposure before a security incident happens.

If you have a large internal network, and there are uncertainties outside of your control, you
may consider using a firewall to segregate your storage network from your internal network.
This allows you to have a smaller storage network to mange, which is easier for you to secure.

Figure 5-18 shows a high level network diagram of using a firewall to create a smaller,
secured storage network. You connect all the management interfaces of your storage devices
in the secured storage network. Because the firewall does not allow normal users or
computers in the corporate network to access the storage devices, the storage devices are
isolated from any potential security issues on the corporate network.

When administrators or servers on the corporate internal network need to connect to your
secured storage network for valid reasons, you need to configure the firewall to allow the
connections required for them to do their work. However, when you configure the firewall to
allow new communications, you need to carefully design the firewall rules. Improperly
designed firewall rules may adversely impact the firewall’s ability to secure your storage
network.

Secured Storage Management LAN
DDS8 800 00
DSS80 000 0

SSPC
C o rp o ra te
Firewall

A dd min i ss r r a oo r s
A m minn its t rta tr sr s
ta
In te rn a l A d S ei riv e r s t o
/ / S e rv e rs
/ S e rv e rs
N e tw o r k
SSVCC
SVVC

D tSe8 0 t0 0a g e
O h r S o r0
D S800
D e v ic e s

Figure 5-18 Recommended network connection

5.2 Upgrading your SSPC
TPC Basic Edition provides basic storage management functions. However, TPC Basic
Edition is not a fully functioning storage management solution. TPC Standard Edition
provides more features, including greater reporting, disk performance analysis, provisioning,
predictive analysis, and SAN planning. TPC Standard Edition is the industry leading Storage
Resource Management and SAN Management product in the industry.

As an entry point for a storage management solution, TPC Basic Edition is designed to allow
you to have an easy road map, from adding partial TPC Standard Edition functions all the way
to full TPC Standard Edition functions. Table 5-2 on page 99 provides the details on what kind
of upgrade options you can have and what is the best situation to use them.


Table 5-2 Best solution for you requirements
Best solution When you need

TPC for Disk Disk performance management

TPC for Data A way to measure and forecast storage growth
A way to rationalize/classify storage data for ILM

TPC for Fabric A tool to manage SAN configuration, availability, and
performance

TPC Standard Edition Managing provisioning, zoning, configuration,
monitoring, and problem determination
A consolidated view of storage infrastructure,
including Disk, SAN, and capacity
A way to manage IBM and heterogeneous storage
from a single tool

TPC Standard Edition or TPC with Provisioning of storage (both IBM and heterogeneous)
Advanced Provisioning

License installation
TPC Basic Edition uses the same software package as the TPC Standard Edition. Because
the software package has already installed on your system after the TPC Basic Edition is
installed, when you upgrade your TPC Basic Edition, all you need is to order and install the
required license to unlock the functions in the software.

The license is installed using the same installation program you used to install the software.
When you install TPC Basic Edition, the license for TPC Basic Edition is automatically
installed. If you decide to upgrade later, you can use the following procedure to install the
license key. The following procedure upgrades your SSPC to TPC for Disk. It is the same
procedure if you upgrade to other TPC products, except you use the CD for other TPC
products.
1. Run the installation program setup.exe using the CD of TPC for Disk.
2. When the Select a language window is displayed, select a language from the drop-down
list and click OK (see Figure 4-16 on page 56).
3. When the Software License Agreement window is displayed. Read the terms of the
license agreement. If you agree with the terms of the license agreement, select I accept
the terms of the license agreement. Click Next (Figure 4-17 on page 56).
4. In Figure 5-19 on page 100, select Installation licenses. This option will allow you to
install the license from the CD that has the TPC for Disk license. You do not have to install
the TPC for Disk software since you already have the software packages installed on the
SSPC or during the install of TPC Basic Edition.


Figure 5-19 TPC installer

5. In Figure 5-20, the message tells you that you have successfully installed the license.
Click Next to continue. When the window disappears, reboot your computer.

Figure 5-20 License installation successful

When your server comes back from reboot, you have TPC for Disk functions available on your
server. Figure 5-21 on page 101 shows the TPC Navigation Tree before TPC for Disk is
installed. Figure 5-22 on page 101 shows the TPC Navigation Tree after TPC for Disk is
installed. In Figure 5-22 on page 101, under IBM TotalStorage Productivity Center → Disk
Manager → Reporting, you can see a new function, Storage Subsystem Performance, that
has been added. TPC Basic Edition does not provide performance reporting.


Figure 5-21 Before TPC for Disk is installed

Figure 5-22 After TPC for Disk is installed


We have shown the scenario of upgrading from TPC Basic Edition to TPC for Disk. For
detailed information about the upgrade procedure, refer to 7.1, “Upgrading SSPC” on
page 188.

5.3 Integrating your SSPC with an existing TPC environment
The ability to consolidate asset and health information collected from multiple TPC instances
was introduced with TotalStorage Productivity Center V3.3. You can create a rollup report to
have a network-wide perspective of storage usage in your environment where multiple TPC
servers are deployed and collecting storage metrics.

5.3.1 Rollup reports
To integrate your SSPC into your existing TPC environment, an existing TPC server should
function as a Master TPC server. The Master TPC server collects data from subordinate TPC
servers, and from the Master Server, you can create rollup reports. Your SSPC server should
function as a subordinate TPC server, providing data to the Master TPC server.

Note: The ability to act as a Master Server and generate rollup reports is a function of TPC
Standard Edition. The Master TPC server is required to be TPC Standard Edition.

Rollup Reports are generated through the TPC Navigation Tree. You can generate four
categories of rollup reports:
Asset: To view detailed statistics about agents, computers, storage subsystems, disk and
volume groups, disks, file systems, logical volumes, LUNs, and fabrics that are monitored
by subordinate servers.
Database Asset: To view detailed statistics that have been collected by subordinate
servers about the RDBMSs in your environment, including Oracle®, SQL Server®,
Sybase, and UDB/DB2.
Capacity: To view storage metrics related to the disk capacity, file system capacity, file
system used space, and file system free space gathered by the subordinate servers in
your environment.
Database Capacity: To view storage capacity, used space, and free space at the
computer, computer group, database, instance, and TPC server level for RDBMSs that are
monitored by subordinate servers.

Note: To generate a full report of your environment, you need to deploy a Data agent and
a Fabric agent on each server (that is, fibre attached) that you want to manage. If a server
does not have agents installed, the information for that server will be omitted from the
rollup report you generate.

Asset reports
In the Asset category, the following reports can be generated:
Agents: To view information about Data agents and Device agents that are associated with
subordinate servers in your environment.
Computers: To view information about the hosts and computers that are monitored by


Storage Subsystems: To view information about the storage subsystems that are
monitored by subordinate servers in your environment.
Disk/Volume Groups: To view information about the disk and volume groups that are
Disks: To view information about the disks that are monitored by subordinate servers in
your environment.
File Systems or Logical Volumes: To view information about the file systems or logical
volumes that are monitored by subordinate servers in your environment.
LUNs: To view information about the LUNs that are monitored by subordinate servers in
your environment.
Fabrics: To view information about the fabrics that are monitored by subordinate servers in
your environment.

Database Asset reports
In the Database Asset category, the following reports can be generated:
All DBMSs: To view information about the RDBMSs that are monitored by subordinate
servers in your environment.
Oracle: To view information about Oracle instances that are monitored by subordinate
Sybase: To view information about Sybase instances that are monitored by subordinate
SQL Server: To view information about SQL Server instances that are monitored by
UDB: To view information about UDB/DB2 instances that are monitored by subordinate

Capacity reports
In the Capacity category, the following reports can be generated:
Disk Capacity: To view disk capacity information about the computers and storage
subsystems that are monitored by subordinate servers in your environment.
Filesystem Capacity: To view file system capacity information about the file systems that
are monitored by subordinate servers in your environment.
Filesystem Free Space: To view information about the available storage space on file
systems that are monitored by subordinate servers in your environment.
Filesystem Used Space: To view information about the used storage space on file systems
that are monitored by subordinate servers in your environment.

Database Capacity reports
In the Database Capacity category, the following reports can be generated:
All DBMSs: To view storage capacity information for the DBMSs that are monitored by
Oracle: To view storage capacity information for the Oracle databases that are monitored
by subordinate servers in your environment.
Sybase: To view storage capacity information for the Sybase databases that are monitored


SQL Server: To view storage capacity information for the SQL Server databases that are
UDB: To view storage capacity information for the UDB/DB2 databases that are monitored

Refer to 7.3.4, “Enterprise rollup reporting” on page 215 for detailed information about
creating rollup reports.

5.4 Backing up your SSPC
SSPC is built on a standard Windows platform. You need to consider the same backup and
recovery policy as for your other Windows servers.

Depending on how you use your SSPC, you may have two ways to recovery your SSPC
server:
1. Rebuild your SSPC based on the procedure discussed in Chapter 4, “Building an SSPC
server” on page 45.
2. Recover your SSPC from backup tape or disk.

If you use your SSPC only as a management console, all the information in the TPC database
on the SSPC can be easily recreated from your storage subsystems managed by the SSPC.

On the other hand, if you use SSPC as a storage management solution, your SSPC may hold
a considerable amount of information that is not easily recreated. For example, if you have
upgraded your SSPC to TPC Standard Edition or TPC for Replication, you may have
historical performance data and copy services policies in the database that will need to be
restored.

To recover your SSPC instance, you need to install proper backup software and regularly
back up your SSPC. Since SSPC in built on top of a standard Windows platform, you have the
flexibility to choose your preferred Windows backup solution to meet your installation
requirements.

TPC stores all information in DB2. When you design your TPC backup solution, you need to
carefully plan your database backup procedure. All general considerations about database
backup applies to TPC backup.


6

Chapter 6. TPC Basic Edition functions
In this chapter, we describe the IBM TotalStorage Productivity Center Basic Edition functions
that help you to manage and configure your IBM System Storage DS8000 systems, IBM
System Storage SAN Volume Controller clusters, selected IBM Tape Libraries, and other
storage infrastructure components.


6.1 Overview
IBM TotalStorage Productivity Center Basic Edition (TPC BE) is a new edition of the TPC
family that comes preinstalled on the System Storage Productivity Center (SSPC) server. The
TPC family consists of different infrastructure management components that helps you
manage, configure, and tune your data storage infrastructure. The new edition TPC BE
provides most of the features that are available in TPC for Disk and TPC for Fabric
components except from performance management and reporting. TPC BE provides the
following functions:
Device discovery
Disk subsystem management
– Discovery
– Monitoring
– Provisioning (for example, volume creation and configuration)
Fabric management
– Discovery
– Monitoring
– Provisioning (for example, zone control and planning)
Tape management
– Discovery
– Monitoring
Topology viewer and Storage Health Management
Reporting

TPC BE provides a basic storage resource management solution. It extends existing
management of a single storage system, providing capabilities such as storage reporting,
monitoring, policy-based management, and storage provisioning.

TPC BE centralizes management of network storage devices that implement the SNIA
Storage Management Interface Specification (SMI-S), which includes the IBM System
Storage DS family and IBM System Storage SAN Volume Controller (SVC). It is designed to
help reduce storage management complexity and cost and help improve data availability
through open standards (SMI-S).

TPC BE can be easily upgraded to TPC Standard Edition, which provides advanced features,
such as performance reporting, file-level capacity utilization, best practices-based
configuration management, and wizard driven end-to-end storage provisioning.

6.2 Architecture
The TPC BE consist of several key components. In this topic, we describe each of these
components and show how they are related.

6.2.1 Services
The Data server and Device server run as services on the server they are installed on.


Data server
The Data server component is the control point for product scheduling functions,
configuration, event information, reporting, and GUI support. It coordinates communication
with agents and data collection from different agents that scan and gather information and
populate the database with the results. The Data server is the primary contact point for GUI
user interface functions. It also includes functions that schedule data collection and discovery
for Device server. Data server has the following services:
Server: The component that directs all the operations of Data Manager
Scheduler: The process on the server that receives requests from the scheduler
GUI: The process within the GUI that enables you to generate report requests and to
create and run jobs
Agent: The process on the server that receives requests from agents

Device server
The Device server component discovers storage subsystems and SAN fabrics, and gathers
information about storage subsystems and SAN fabrics. The Device server controls the
communication with agents and the data collection from agents that scan SAN fabrics. It is
also responsible for the creation and monitoring of replication relationships between storage
devices. Device server has the following main services:
SAN planner: The component that provides SAN planning functions
Fabric manager: A service that provides fabric management functions
Disk manager: A service that provides storage subsystem management functions
Disk monitor: A service that monitors the storage subsystems
Element manager: A service that provides the ability to manage element managers
Discovery: A service that provides discovery and probe functions
Tape manager: A service that provides tape management functions

6.2.2 Data Sources
Data Sources (Data and Fabric agents) are used to gather data about the storage
subsystems, fabric, and servers that will be monitored and managed. It sends this information
to a Data server or Device server. TPC BE uses the following agents as Data Sources:
CIMOM
In-band Fabric agent (if Agent Manager is installed)
Out of Band Fabric agent

Note: Agent Manager, the central network element, together with the distributed Common
Agents, builds an infrastructure that is used by other applications to deploy and manage an
agent environment is an optional program that can be installed on the SSPC server. TPC
BE does not require Agent Manager, so Data agents and In-band Fabric agents cannot be
deployed.

Chapter 6. TPC Basic Edition functions 107

CIMOM
The Common Information Model Object Manager (CIMOM) provides a means by which a
device can be managed by common building blocks rather than proprietary software. If a
device is a CIMOM compliant, TPC can manage it, because TPC is also CIMOM compliant.
Actually, the CIMOM is an interpreter between TPC and the device. There is an SNIA SMI-S
interface using an XML transport for data and command interchange from TPC to the
CIMOM. From the CIMOM to the device layer, there are proprietary interfaces provided by
the device vendor to convert those commands and answers from the SNIA XML language to
a language that device can understand:
For storage, CIMOMs are needed for storage asset information, provisioning, alerting, and
performance monitoring.
For fabric, CIMOMs are only used for performance monitoring.
For tape libraries, CIMOMs are used for asset and inventory information.

The CIMOM can be a separate installation or can be imbedded in the device itself. After the
CIMOM is installed and configured, TPC can communicate with a device.

In-band Fabric agent
In-band Fabric agents collect information about SAN fabrics. The In-band Fabric agents must
be installed on systems with host bus adapters (HBAs) that are connected to the SAN fabrics
that you want to manage.

The In-band Fabric agents communicate in-band through the HBA and collect the following
informations from the SAN fabrics:
Attribute and topology information
Host level information (LUN mapping)
HBA information (model and driver version)
Port state information
Zoning information

In-band Fabric agents are discovered during the installation process. The in-band Fabric
agents can be installed locally or can be also installed remotely from TPC. It must be installed
on at least one system that has an HBA that is connected to SAN fabrics.

Out of band Fabric agent
Out of band Fabric agents are used by the Fabric Manager. Out of band Fabric agents issue
SNMP queries to the fabric switches and collect topology information. The Fabric agent must
point to each switch in the SAN fabrics that you want to manage.

The out of band Fabric agents collect the following information from the SAN fabrics:
Zoning information (Brocade only)
Virtual storage area network (VSAN) information (Cisco only)

6.2.3 Database
A single database instance serves as the repository for all TPC components. It is a single
DB2 database instance.


6.2.4 Graphical user interface
The graphical user interface (GUI) provides an integrated user interface for all TPC
interactions. It lets you enter or receive information for all TPC components.

TPC provides two methods for running a GUI: as a downloadable Java GUI application or as
an application. If running the downloadable Java GUI application, it is not necessary to install
the GUI component on every workstation. You can simply access it from any Web enabled
workstation and the Java GUI application is automatically downloaded on an as-needed
basis.

6.2.5 Command-line interface
The command-line interface (CLI) lets you issue commands for major TPC functions. Generic
commands are available regardless of which components have been licensed and
configured. The only requirements are an active Device server and a valid login.

6.3 Using TPC BE
This topic will cover initial configuration tasks that are needed to get started using TPC BE
functions and managing your storage infrastructure. This topic will also help you to get an
overview of the TPC BE capabilities, the structure of the user interface, and the relationship of
the product components.

TPC BE offers two user interfaces: a graphical user interface (GUI) and a command-line
interface (CLI). We only cover the use of GUI.

6.3.1 Starting the GUI
TPC BE provides you two methods to start the GUI:
Application
Java Web Start

Application
You can start the GUI:
As an application on the SSPC server
As an TPC Client on any workstation


To start the TPC BE GUI on the SSPC server, open the TPC BE GUI by selecting Start →
Programs → IBM TotalStorage Productivity Center → Productivity Center. You can also
double-click the Productivity Center icon from desktop. After you start the GUI, you must enter
the TPC user ID and password see (Figure 6-1).

To start the TPC BE GUI from any workstation in your environment, you must install the TPC
Client from TPC installation CDs, which are shipped with SSPC. To install it, run the TPC
installer and choose to install GUI.

Figure 6-1 TPC Basic Edition logon

After entering a valid TPC user ID and password, the main TPC BE window is opened, as
shown in Figure 6-2 on page 111.


Figure 6-2 TPC Basic Edition welcome window

Java Web Start
You can start the TPC BE GUI using Java Web Start from any Web-enabled workstation that
has an IP connection to the SSPC server. The benefit of running the user interface as a Java
Web Start is that you are not required to install the GUI component on every workstation. To
start and run the TPC BE GUI Java Web Start, you must do the following:
1. Start a Web browser session.
2. Point your Web browser to the following URL where you specify your SSPC server IP
address and the appropriate port:
http://<SSPC IP address>:9550/ITSRM/app/welcome.html
3. It opens a Web page where you start the TPC BE GUI using Java Web Start. If you do not
have the appropriate Java, you can install it from the Web page. Figure 6-3 shows the TPC
BE Java applet Web page.

Figure 6-3 TPC GUI Java Web Start


TPC Basic Edition has the IBM V1.4.2 JRE in the source code. Your OEM server may not
support the IBM V1.4.2 JRE. During install, you may encounter the error message shown
in Figure 6-4. To fix this Java error, you have to download and install Java Version 1.4.2
from the Sun™ Microsystems Web site.

Figure 6-4 Java error message

4. Click the link TPC GUI (Java Web Start). It starts downloading the TPC BE GUI
(Figure 6-5).

Figure 6-5 Downloading TPC BE GUI Java Web Start

5. After the TPC BE GUI is downloaded, you will be asked if you would like to have TPC GUI
integrated into your desktop environment. You can double-click the TotalStorage
Productivity Center GUI icon on your desktop and start it.
You can start Java Web Start by selecting Start → Programs → IBM Java Web Start
V1.4.2. It open Java Web Start Application Manager, where you can manage Java
applications (Figure 6-6 on page 113).


Figure 6-6 Java Web Start

6.3.2 Using the GUI
TPC BE GUI offers two perspectives that act as containers for organizing related features and
functions that are integrated within the TPC user interface. Each perspective provides a
complete set of tools for performing a specific set of enterprise management tasks.


The ability to switch between perspectives provides you with a single interface for quickly
accessing different tools to monitor and manage your storage devices. You can switch
perspectives using the Enterprise Management or Element Management button that appears
in the TPC BE toolbar (Figure 6-7).

Figure 6-7 Element Management button

The following perspectives are currently available:
Enterprise Management
Element Management

Enterprise Management
This perspective contains the TPC BE user interface and all its related functions. You can use
this perspective to perform such tasks as configuration, data collection, policy management,
alerting, and reporting.

The tree-based navigation system lets you see a hierarchical organization of the product
features in the left pane while viewing detailed reports and informations in the right pane. The
left pane is called the Navigation Tree, and the right pane is called the Content Pane.

When you start TPC BE, the Enterprise Management perspective is opened and the
Navigation Tree is expanded to show all the high level functions. You can drill down on an
element in the tree by clicking it or by clicking the expand icon. When you right-click a node, a
pop-up (context) menu displays, which lets you perform additional actions for the node. If the
Navigation Tree gets too large, or if you want to return it to its original state, right-click the
major nodes of the tree and select Collapse Branch or Expand Branch. If you right-click the
IBM TotalStorage Productivity Center node and select Collapse Branch, the entire
Navigation Tree collapses. Then, right-click the main IBM TotalStorage Productivity Center


node and select Expand Branch to return the Navigation Tree to its original state, expanded
only to show the main functions.

The Content Pane opens on the right side of the main window. When you select a node in the
Navigation Tree, the corresponding function window opens in the Content Pane. You can use
the windows that open in the Content Pane to define and run the different functions (for
example, monitoring jobs, alerts, and reports) available within TPC BE. The information
shown on the pages in the Content Pane will vary, depending on the function you are working
with.

Element Management
This perspective enables you to add, manage, and launch the Element Managers that are
visible to TPC BE. For example, use DS8000 Element Managers to access the DS8000
Storage Manager for configuring and administering the associated DS8000 storage
subsystems. Figure 6-8 shows the Element Management perspective.

Figure 6-8 Element Management perspective

6.3.3 Collecting data
There are basically two ways to collect the information from your environment:
CIMOM and SNMP traps
Data collections

TPC BE uses only CIMOM and SNMP traps to collect the data. Data collections require that
Agent Manager is installed and that Data agents are deployed.


There are different collection jobs for the type of information collected and from which types of
elements the information is retrieved. TPC BE uses the following collection jobs:
Discovery jobs locate data sources and collects basic information about these data
sources. TPC BE discovery jobs run against CIMOMs and out of band Fabric agents.
When a discovery job is run against a storage subsystem CIMOM, the job locates all
storage subsystems behind this CIMOM and retrieves all information the CIMOM holds for
these systems. The discovery job, however, does not cause the CIMOM to log in to the
storage subsystems and retrieve more detailed information. When a discovery job is run
against a fabric, the job retrieves all available information for the fabric if it is supported by
the switches.
Probe jobs collect detailed statistics on all the assets of the managed infrastructure, such
as computers, disk controllers, fabrics, storage subsystems, and LUNs. Probe jobs can
also discover information about new or removed disks. Probe jobs can be directed against
any element in the managed infrastructure.

Note: TPC BE probe jobs do not collect all the information of the managed infrastructure,
such as file systems, because TPC BE does not require Agent Manager, and therefore
Fabric agents and Data agents are not deployed.

6.3.4 Adding CIMOM
Before you start using TPC BE, you must add the related CIMOM agents, which provide a
standard interface to storage devices for storage management applications. There are two
ways of adding CIMOM agents to TPC BE:
Run automatic CIMOM discovery.
Add CIMOM agents manually.

CIMOM discovery
To run the CIMOM Discovery job, go to Navigation Tree pane and expand Administrative
Services → Discovery. Right click CIMOM and click Run now (Figure 6-9 on page 117).


Figure 6-9 Run CIMOM discovery

In the Notice window, click OK, and the CIMOM Discovery job is started (Figure 6-10).

Figure 6-10 Notice window


To monitor the CIMOM Discovery job, expand Administrative Services → Discovery →
CIMOM, right-click CIMOM, and select Refresh Job List from the drop-down menu
(Figure 6-11). Then expand the CIMOM node of the Navigation Tree.

Figure 6-11 Update CIMOM discovery job status

The entry for CIMOM discovery job is named with the time stamp of its starting time. While it
is running, it has a blue circle outline to the left of the job name (Figure 6-12). If the job has
completed successfully, a green square is shown in front of the job name.

Figure 6-12 CIMOM discovery job status


A red circle indicates that the job has competed with errors (Figure 6-13). TPC uses also a
yellow triangle to indicate that a job has completed with warnings.

Figure 6-13 Completed CIMOM discovery job

After the job completes, the discovered CIMOMs are listed in the CIMOM table in the Content
pane. You can check it if you expand Administrative Services → Data Sources and click
CIMOM Agents (Figure 6-14).

Figure 6-14 Discovered CIMOMs

The CIMOM connection status can have different values. If the status is different than
Success, you can check the CIMOM details by clicking the magnifying glass to the left of the
listing. The information is shown in the Content pane. You can enter additional CIMOM
information, such as the user name and password used for logging into the CIMOM, and you
can also test CIMOM connectivity by checking Test CIMOM connectivity before updating
(Figure 6-15 on page 120).

If you select a specific CIMOM in the table, you can perform the following administrative
actions by clicking the buttons in the toolbar above the CIMOM list:
Test CIMOM connection: Check to ensure that communication to the CIMOM is working
properly.
Remove CIMOM: Remove the CIMOM from the function tree and repository database.
The data discovered by the CIMOM will not be removed from the repository.
Show managed devices: Show devices that are managed by the CIMOM.


Figure 6-15 Adding CIMOM details

Adding CIMOM manually
You can manually add CIMOMs if they are not discovered during automatic CIMOM
discovery. To add CIMOM manually, go to the Navigation Tree pane, expand Administrative
Services → Data Sources, and click CIMOM Agents. In the Content pane, click the Add
CIMOM button and the Add CIMOM windows opens (Figure 6-16).

Figure 6-16 Adding CIMOM manually


To add the CIMOM, you must specify the CIMOM IP address and the port on which the
CIMOM is listening. It also requires a valid user name and password for authentication. The
Interoperability Namespace within the CIMOM allows you to access the CIM Interop Schema
and determines how TPC interacts with the CIMOM when retrieving information. You can also
check the box to test CIMOM connectivity before adding it and to ensure that communication
is working properly. After you click Save, the information you have input about the CIMOM is
added to TPC so that TPC can communicate with the CIMOM.

6.3.5 DS8000 CIMOM
DS8000 CIMOM is embedded on the HMC of the DS8000 storage subsystem. The CIMOM is
initially disabled on the HMC and must be enabled through the WebSM management console
before it can be used. The HMC CIMOM can only support DS8000 devices that are managed
by that HMC. This CIMOM is not able to manage any ESS 800 or DS6000 devices, or any
DS8000 devices that are managed by a different HMC.

The first step to set up the CIMOM is enabling it on the HMC. The SSR would log in to the
HMC as for a normal service action, and from the Service Focal Point dialog start CIMOM.
Figure 6-17 shows the window from the HMC that CIMOM is running.

Figure 6-17 MC CIM Agent enable

The next step is to define a user ID and password that will be used by the CIMOM for
managing the storage devices. You can use the default admin user or create a new user. This
would be done either by using the DS8000 element manager or the DSCLI mkuser command.
You need to create a user with at least operator authority, which allows the creation and
removal of arrays and ranks and, of course, includes the ability to create, delete, and manage
logical volumes.

DSCIMCLI
The last step is configure CIMOM using the DSCIMCLI utility. The DSCIMCLI utility, which
configures the CIMOM, is available from the DS CIM agent Web site as part of the DS CIM
agent installation bundle, and also as a separate installation bundle. The DSCIMCLI can be
installed on the SSPC server.

Perform these steps to install DSCIMCLI utility:
1. Download and extract the dscimcli.zip file onto your hard drive.
2. The top-level directories of the extracted contents represent the different operating
systems (AIX, LINUX_RHEL3, LINUX_SLES9, or W2003). Set your DSAGENT_HOME
environment variable to one of those directories depending on your platform.
3. Add the bin directory of the DSAGENT_HOME to your PATH environment variable.


Use the DSCIMCLI mkdev command to define an internal connection to the HMC. The key
function of this command is to feed the DS8000 user ID and password to the CIMOM Agent,
which it will need to manage the DS8000 (very similar to a DSCLI user connecting to the
HMC for DS8000 management). You can optionally specify the address of the redundant
HMC. Example 6-1 contains the command syntax.

Example 6-1 Defining HMC to CIMOM
C:Documents and SettingsAdministrator>dscimcli -s https://9.12.6.17:6989 mkdev
9.12.6.17 -type ds -user admin -password st0rage
Device succesfully added.

After you defined the internal connection to the HMC, you can check its status as well as the
CIMOM configuration and CIMOM users. Example 6-2 contains the command syntax.

Example 6-2 Checking CIMOM status
C:Documents and SettingsAdministrator>dscimcli lsdev -l -s 9.12.6.17:6989
Type IP IP2 Username Storage Image Status Code Level Min Codelevel
===== =============== =============== ========= ================ ========== ============== ==============
DS 9.12.6.17 - mary IBM.2107-75BALB1 successful 5.3.0.991 5.1.0.309

C:Documents and SettingsAdministrator>dscimcli lsuser
Username
=========
superuser

C:Documents and SettingsAdministrator>dscimcli lsconfig
Property Current Value After Restart
============== =============================== ===============================
insecureport 5988 5988
secureport 5989 5989
certificate certname certname
enablesecure true true
enableinsecure true true

Note: Use of DSCIMCLI utility is described in the book DS Open Application Programming
Interface Reference, GC35-0516

After the CIMOM is configured, you can add it manually or it will be discovered automatically
as long as it is in the same subnet as the TPC BE server. Figure 6-18 on page 123 shows the
discovered DS8000 CIMOM and managed DS8000 storage subsystem.


Figure 6-18 DS8000 CIMOM

Note: The DS8000 CIMOM default user ID is superuser and password is passw0rd.

IBM TS3500 Tape Library CIMOM
To communicate with the Tape Library, TPC uses the CIMOM agent for tape. The CIMOM
agent for tape must be installed on a separate Intel machine that runs the SUSE® Linux
Enterprise Server 9 operating system or Red Hat Enterprise Linux 3.0. The CIMOM agent for
tape communicates by using the Web-Based Enterprise Management (WBEM) protocol,
which allows TPC to communicate with the IBM TS3500 Tape Library.


To configure the IBM TS3500 Tape Library to work with the CIMOM agent for tape, you must
connect to the Tape Library Specialist Web interface, enable the CIMOM interface, and set up
SNMP traps. To start the Tape Library Web interface, open a Web browser and enter the IP
address of the Tape Library Specialist. It opens the login Web page, as shown in Figure 6-19.

Figure 6-19 Tape Library Specialist


Enter the user ID and password. Under The Work Items in the left pane, expand Access and
click SMI-S Agent (see Figure 6-20).

Figure 6-20 SMI-S Agent option


In the right pane, click the Enable SMI-S Agent button to enable it (Figure 6-21).

Figure 6-21 Enable SMI-S agent

The window in Figure 6-22 shows you successfully enabled the agent.

Figure 6-22 SMI-S agent successful enabled


To set up the IP address of CIMOM agent for Tape, expand Access and click SNMP
destination. Enter the IP address of CIMOM agent and click Apply (see Figure 6-23).

Figure 6-23 CIMOM agent IP address


To set up the SNMP traps, expand Access and click SNMP Settings. This action opens the
SNMP Settings in the right pane, where you enable and set up SNMP traps (see Figure 6-24).

Figure 6-24 SNMP settings

Note: For information about the version of SNMP traps, the Trap Community Name, and
the Request Community Name, refer to the IBM TotalStorage SMI-S Agent for Tape on
Linux Systems Installation Guide, GC35-0512. For the details how to set up IBM TS3500
Tape Library, refer to the IBM System Storage TS3500 Tape Library Operator Guide,
GA32-0560.

6.3.6 Adding in-band Fabric agents
If you are planning to install Agent Manager, which is an optional and not required application
for TPC BE, you also deploy in-band Fabric agents on servers in your SAN environment.
In-band Fabric agents will register with TPC BE by themselves and should be readily
available. Therefore, the in-band Fabric agent does not need to perform a discovery process.

6.3.7 Adding out of band Fabric agents
Out of band Fabric agents issue SNMP queries to the fabric switches and collect topology
information. You must add out of band Fabric agents in order to get this data. The steps for
adding out of band Fabric agents are very similar to adding CIMOMs. We can either run an
automatic Discovery job, or add the out of band Fabric agents manually. This must be done
for each switch in the fabric.


Out of band Fabric agent discovery
To run the out of band Discovery job, do the following steps:
1. Navigate to the tree pane, expand Administrative Services → Discovery, and click Out
of Band Fabric.
2. In the Content Pane, you can see several tabs for the definition of the job. For the
out-of-band Discovery job, enter the IP addresses of the subnets you want to scan in the
Options tab (Figure 6-25).

Figure 6-25 Out of band discovery


3. Submit the job by selecting File → Save in the menu bar. You can monitor the job by
expanding Administrative Services → Discovery → Out of Band Fabric and clicking
the job run entry (Figure 6-26).

Figure 6-26 Monitoring Discovery job status


In the Content Pane, you can examine the log by clicking the magnifying glass next to the job
status (Figure 6-27). While the job is running, you can check its status by selecting
Administrative Services → Discovery → Out of Band Fabric. Select the job run entry and
right-click Out of Band Fabric. From the menu, you can choose Refresh Job List to refresh
the status of the Discovery job, or Update Job Status to check and see if the job has
finished.

Figure 6-27 Discovery job log


4. To check discovered out of band agents, select Administrative Services → Data
Sources and click Out of Band Fabric. The Content Pane shows all discovered out of
band agents (see Figure 6-28).

Figure 6-28 Discovered out of band agents

5. By clicking the magnifying glass to the left of the listing, you see general information for the
selected switch (Figure 6-29 on page 133).


Figure 6-29 General switch information

Note: If you have a Brocade Fabric, make sure you have enabled Advanced Brocade
Discovery in the Out of Band Fabric agents definition and provide the user name and
password, so that TPC can discover zoning information from the fabric.


Adding an Out Of Band Fabric agent manually
As an alternative to an automatic Discovery job, you can manually add an Out Of Band Fabric
agent to TPC BE. To add an Out Of Band Fabric agent, follow these steps:
1. Expand Administrative Services → Data Sources and click Out of Band Fabric
agents. This brings up a context menu in the Content pane where you select Add
(Figure 6-30).

Figure 6-30 Adding out of band Fabric agent

2. Clicking the Add button opens a dialog box (Figure 6-31 on page 135) where you enter
the host name or IP address of the switch to add. If you are adding a Brocade switch, you
can enable the Advanced Brocade Discovery and enter the user name and password for
the switch so that TPC can discover zoning information from the fabric.


Figure 6-31 Adding out of band Fabric agent

3. Click OK and you see the Out Of Band Fabric agents (Figure 6-32).

Figure 6-32 Out of band Fabric agents

4. You can check the Out Of Band Fabric agent details by clicking the magnifying glass to the
left of the listing.


6.3.8 Probe
Probe jobs collect detailed information about the managed infrastructure in your environment,
such as storage subsystems, tape libraries, and fabrics. Probe jobs can be directed against
any of these components:
Storage subsystem probes collect detailed information about the configuration of storage
subsystems. It collects the data about storage pools, storage volumes, FC ports, disks,
and host to volume assignments. A probe job needs to be run before volumes can be
created on a storage subsystem.
Library probes collect detailed information about the configuration of the tape library. They
collect the data about the tape library drives, changers, cartridges slots, and I/O ports. A
probe job need to be run before a tape library can be monitored.
Fabric probe jobs collect fabric topology and zoning information and basic identification
information about the device attached to the fabric.

Creating probes
You can create any number of probes to gather information about different storage resources
at different times. To create a probe, expand IBM TotalStorage Productivity Center →
Monitoring, right-click Probes, and click Create Probe (Figure 6-33).

Figure 6-33 Creating probe job


In the right Content pane, select the What to PROBE tab (Figure 6-34).

Figure 6-34 Select elements to probe


In this tab, select an available infrastructure element against which the probe job will run and
click the >> button to add it to your selection. We define a Probe job for each of the elements
(fabric, tape libraries, and storage) in the infrastructure. It is also possible to define one Probe
job for all of the elements in your infrastructure. First, we define a Probe for Storage
Subsystems. Expand Storage Subsystems and select All Storage Subsystems, because
we want to include all Storage Subsystems in our Probe job. This also includes all Storage
Subsystems added in the future (Figure 6-35).

Figure 6-35 Adding elements to probe

In the When to Run and Alert tabs, we set the schedule and alert options (Figure 6-36 on
page 139).


Figure 6-36 Setting probe schedule

In the upper right corner of the Content pane, select Enabled. Select File → Save and in
Save as window, specify a name for the Probe job (Figure 6-37).

Figure 6-37 Specifying probe name

We named our probe job “Storage Subsystems”. Click OK and the Probe job is submitted
(Figure 6-38).

Figure 6-38 Submitting probe job


We repeat the steps for other infrastructure elements (fabrics and tape libraries). You can see
all the created Probe jobs under the IBM TotalStorage Productivity Center →
Monitoring → Probes (Figure 6-39).

Figure 6-39 Created probe jobs

Their names are built from the user ID that we used to log in to TotalStorage Productivity
Center and the name we specified when saving the job definition. By expanding the name of
the probe job, you see its status (Figure 6-40).

Figure 6-40 Probe jobs status

The blue circles next to the entries for the job runs indicate that the jobs are still running. The
red circles indicates that the job run has completed with errors and if there is a yellow triangle,
it indicates that a job run has completed with warnings. We can examine the logs in the
Content Pane to find the reasons for the errors or warnings.


6.4 Topology Viewer
The Topology Viewer is designed to provide an extended graphical topology view, that is, a
graphical representation of the physical and logical resources (for example, computers,
fabrics, and storage subsystems) that have been discovered in your storage environment. In
addition, the Topology Viewer depicts the relationships among resources (for example, the
disks comprising a particular storage subsystem). Detailed, tabular information (for example,
attributes of a disk) is also provided.

With all the information that Topology Viewer provides, you can easily and more quickly
monitor and troubleshoot your storage environment. The overall goal of the Topology Viewer
is to provide a central location to view a storage environment, quickly monitor and
troubleshoot problems, and gain access to additional tasks and functions within the TPC GUI
without users losing their orientation to the environment. This kind of flexibility through the
Topology Viewer user interface displays better cognitive mapping between the entities within
the environment, and provides data about entities and access to additional tasks and
functionality associated with the current environmental view and the user's role.

The Topology Viewer uses the TPC database as the central repository for all data it displays.
It actually reads the data in user-defined intervals from the database and updates, if
necessary, the displayed information automatically. The Topology Viewer is an easy-to-use
and powerful tool within TPC. It will make a storage manager’s life easier. But as is true for
every tool, you first have to understand the basics, the concept, and also the do’s and don’ts,
to get the most out of it.

Note: Detailed information about Topology viewer are described in IBM TotalStorage
Productivity Center User’s Guide Version 3 Release 3, GC32-1775.

6.4.1 Topology Viewer overview
The information displayed by the Topology Viewer is collected by discovery, probing,
performance data collection (TPC SE only), and alerting. The Topology Viewer consists of two
views, a graphical view and a table view, organized vertically with the graphical view on top of
the table view. The table view shows the same information as the graphical view, but in a
tabular format. The Topology Viewer supports four levels of detail, from a high-level overview
of the entire storage environment to detailed information about individual entities. This allows
you to view as much or as little detail as you need.


To start Topology Viewer, expand, in the Navigation Tree, IBM TotalStorage Productivity
Center and click Topology. It opens Overview level, which is the default view (Figure 6-41).
Overview level shows a global, highly aggregated view of the entire storage environment.

Figure 6-41 Topology Viewer overview level

Groups level L0 focuses on groups of a particular type. You can select each group by
expanding IBM TotalStorage Productivity Center → Topology. The default groups are:
Computers: All discovered computer groups in your storage environment.
Fabrics: All fabric groups in your storage environment. A fabric is a network of entities that
are attached through one or more switches. The Topology Viewer also displays Virtual
SANs (VSANs) and Logical SANs (LSANs).
Switches: All switches in your environment.
Storage: All storage subsystems and tape libraries in your environment.
Other: All entities that are discovered in your environment but that do not fit in either the
computer, fabric, or storage classes.


The groups level is the default level upon launching the Topology Viewer by clicking either
Computers, Fabrics, Switches, Storage, or Other under the Topology node. The groups
level shows one or more groups of entities that correspond to the topology class that you
selected. Figure 6-42 shows the Storage group level.

Figure 6-42 Storage group level L0


Group level L1 focuses on one selected group and its related entities (for example, a group of
storage). To open group level L1, select the group of entities that you want to open and double
click it. It opens group level L1 (Figure 6-43).

Figure 6-43 Group level L1


Individual entities can be shown by expanding the group box (Figure 6-44). It also displays
lines representing connections between entities or between entities and groups.

Figure 6-44 Group level L1 - individual entities


Detail level L2 level focuses on individual entities (for example, a single computer, switch,
subsystem, or tape library) and the paths to the associated logical and physical entities. This
level shows details all the way to the port level (Figure 6-45).

Figure 6-45 Detail level L2

The Topology Viewer depicts the relationships among resources (for example, the disks
comprising a particular storage subsystem). Detailed, tabular information (for example,
attributes of a disk) is also provided (Figure 6-46 on page 147). With all the information that
the Topology Viewer provides, you can more quickly and easily monitor and troubleshoot your
storage environment and perform critical storage-management tasks.


Figure 6-46 Topology viewer - tabular view

As more of your resources are discovered and displayed in the Topology Viewer, it is not
possible to see all the discovered resources in a single topology window. To make it easier
for you to find the resources you want to view, TPC provides a tool called the minimap. The
minimap allows you to shift the focus of the Topology Viewer to different areas within a
particular view. The minimap is a small window that is initially located in the upper-right corner
of any topology view (Figure 6-47).

Figure 6-47 Minimap

The minimap provides a miniature representation of the current topology view. Clicking the
minimap displays a multidirectional cursor that allows you to move the focus of the current
topology view in any direction. As you drag the cursor around the minimap, the topology view
will move accordingly. This makes navigating around complex topologies much easier. The
minimap uses the following colors to indicate the aggregated health status of groups:
Green (normal): All entities in the group are operating normally.
Yellow (warning): At least one entity is operating normally, and one or more entities have a
health status of warning, critical, unknown, or missing.


Red (critical): The status of all entities is either critical or warning.
Gray (unknown): None of the entities in the group has a known health status.
Black (missing): All of the entities of the group are missing.

6.4.2 Data Path Explorer
Included at the bottom of the minimap are shortcuts that you can click to launch the Data
Path Explorer or to view or change the topology settings:
To launch the Data Path Explorer, select one or more hosts, subsystems, disks, volumes,
or Mdisks and click the Data Path Explorer shortcut.
To view or change the topology settings, click the Topology Settings shortcut. The Settings
window displays, where you can specify the type of overlays to display, the type of filtering
to perform, whether connections between topology objects should display, and whether
the Zone tab should display in the table view (Figure 6-48).

Note: In order to view the Data Path Explorer for a host, you must either have an inband
Fabric agent installed or both a Data Agent and an Out of Band Fabric agent on the SAN
on which the host is connected.

Figure 6-48 Topology settings

6.4.3 Managing storage subsystems
The Topology Viewer provides a clear view of your environment where you can start to
perform storage subsystem management tasks. With TPC BE you can:
Create volumes on your storage subsystems and Virtual Disks on your SAN Volume
Controllers and assign them to host ports.
Add Managed Disk Candidates to Managed Disk Groups on your SAN Volume Controller.
Delete Volumes and Virtual Disks.


To start with volume/virtual disk creation, expand IBM TotalStorage Productivity Center →
Topology and select Storage. It opens storage groups in the Topology Viewer pane in the
right. Expand the subsystems group with the storage subsystem that you want to manage
(Figure 6-49).

Figure 6-49 Storage subsystems group


Right-clicking the selected storage subsystem opens a pop-up menu, as shown in
Figure 6-50.

Figure 6-50 Manage storage subsystems - pop-up menu


Select Manage Storage Subsystems, which opens the Storage Subsystems pane
(Figure 6-51).

Figure 6-51 Storage subsystems window


You can also open the pane by selecting the storage subsystem in the Topology Viewer table
and, from the drop-down menu, select Manage Storage Subsystems (Figure 6-52).

Figure 6-52 Manage storage subsystems - drop-down menu

From the Storage Subsystems pane, you can create volumes or virtual volumes for the
selected storage subsystem. We show you how to create a DS8000 volume. To create the
volume, select a DS8000 storage subsystem in the table and click the Create Volume button.
It opens the create volume wizard (Figure 6-53 on page 153), where you define the volume
characteristics, such as RAID level, volume size, and volume name.


Figure 6-53 Create volume wizard

Click Next to continue. The next window, shown in Figure 6-54, shows a list with all the
available ports that TPC has located. The information about the ports come from various
sources (from the switches and from the host definitions in the subsystems) and they are not
ordered by fabrics or any other criteria. Select the ports you want to assign the volumes to
and then click Next to continue.

Figure 6-54 Available host ports


Figure 6-55 shows the available DS8000 ports to assign to host ports. Select the ports you
want to assign and click Next.

Figure 6-55 Available DS8000 ports

If there is no zoning or no active zone set for the selected ports, TPC will recognize that fact
(Figure 6-56). You can perform the zoning function later.

Figure 6-56 Zoning information


The next window is a summary of the information you have entered (Figure 6-57). Click
Finish.

Figure 6-57 Summary

TPC now creates the volume creation job, as shown in Figure 6-58.

Figure 6-58 Volume creation job is finished


You can monitor the job and examine the logs by clicking the entries and drilling into the job
logs (see Figure 6-59 and Figure 6-60). To view the job, select Disk Manager →
Monitoring → Jobs in the Navigation Tree pane.

Figure 6-59 Volume creation job

Figure 6-60 Volume creation job log


The green squares and the entries in the job logs indicate that the job has completed
successfully (Figure 6-61).

Figure 6-61 Volume creation job successfully completed


6.4.4 Managing fabrics
From the Topology Viewer, you can perform zone control management tasks. Expand IBM
TotalStorage Productivity Center → Topology and select Fabrics. This task opens the
fabric groups in the Topology Viewer pane to the right (Figure 6-62).

Figure 6-62 Fabric groups in Topology Viewer


Right-click the selected fabric and, in the pop-up menu, select Manage Zone Control
(Figure 6-63).

Figure 6-63 Manage Zone Control in pop-up menu


The Fabrics pane opens, where you manage your zone configuration (Figure 6-64).

Figure 6-64 Fabrics window


You can also open the pane by selecting the fabric in the Topology Viewer table and, from the
drop-down menu, select Manage Zone Control (Figure 6-65).

Figure 6-65 Manage Zone Control in drop-down menu


In the Fabrics pane, pressing the Zone configuration button opens the zoning page where
you can change the active zone configuration or inactive zone definitions (Figure 6-66).

Figure 6-66 Zoning page

Click the Change button to open the zone definition page (Figure 6-67 on page 163).


Figure 6-67 Zone definition page

The zone definition page lists the zones and zone sets for the fabric in the tables and
provides management tasks such as add, remove, edit zones, and zone set. Make the
changes and activate the zone set by clicking the Update and Activate button. Clicking the
Update only button commits the changes to the zoning configuration definition and updates
the database.

6.5 Element Managers
With TPC BE, you can launch Element Managers, which are provided with storage devices.
Element Managers are programs that help you to maintain and configure your storage
devices. This topic describes different ways to launch the Element Managers to access
management tools.


6.5.1 Storage subsystem
By expanding Disk Manager → Storage Subsystems, all managed and discovered storage
subsystems and SVCs are listed in the Content pane to the right. If Element Managers have
been defined for the storage subsystems and SVCs, you can launch the associated Element
Manager by selecting the Storage Subsystem from the list and clicking the Launch Element
Manager button (Figure 6-68).

Figure 6-68 Launch Element Manager button

If the Element Managers have not been defined, the Launch Element Manager button is
inactive in the menu (see Figure 6-69) and you have to provide the Element Manager
information.

Figure 6-69 Inactive Launch Element Manager button

Define Element Managers
To define an Element Manager, in the Navigation Tree, expand Disk Manager and click
Storage Subsystems. In the right Content pane, select the subsystem that you want to add
the associated Element Manager to and double click it. You can also select the Storage
Subsystem and click the magnifying glass icon to the left of the subsystem. It opens the
Storage Subsystems details page. Click the Set button and in the Edit Element Manager
window enter the URL of the Element Manager or the fully qualified name of the executable
file (Figure 6-70 on page 165).


Figure 6-70 Edit element manager window

Define DS8000 Element Manager
To be able to use DS8000 Storage manager for configuring and administering DS8000
storage subsystems, you must add the DS8000 Element Manager to TPC BE. We add the
DS8000 Element Manager from the Element Management perspective. To open the Element
Management perspective, expand Element Manager and click IBM DS8000 (Figure 6-71). In
the right pane, click the Element Management button to switch to the Element Management
perspective. You can also switch to it by clicking the Element Management button that
appears in the TPC BE toolbar.

Figure 6-71 Element Management buttons


This opens the Element Management perspective (see Figure 6-72).

Figure 6-72 Element Management perspective

To add the DS8000 Element Manager, click Select action and, in the drop-down menu,
select Add Element Manager (Figure 6-73).

Figure 6-73 Adding Element Manager

This will bring up a window where you enter the user name and password for the DS8000
Element Manager that you want to manage, the IP address of the DS8000, port used for
communication and the protocol. You also enter the name you want to associated with the
DS8000 in the main DS8000 Element Manager window in the Display Name field (see
Figure 6-74 on page 167). Click OK to continue.


Figure 6-74 Configure DS8000 Element Manager

The next window contains a message that the Element Manager has been successfully
added (see Figure 6-75).

Figure 6-75 Successfully added DS8000 Element Manager

Click OK to see the DS8000 Element Manager you just defined in the table (Figure 6-76).

Figure 6-76 Defined DS8000 Element Manager


From the Select action drop-down menu, you can add another DS8000 Element Manager and
modify, remove, or test existing ones (see Figure 6-77).

Figure 6-77 Select action drop-down menu

Selecting the Modify Element Manager option opens the Configure Element Manager
window (Figure 6-74 on page 167), where you can change the user name, password, or IP
address of the DS8000 Element Manager.

The Add CIMOM Connection option allows you to manually associate a CIMOM with an
Element Manager. The CIMOM that you associate with an Element Manager manages the
same storage subsystem as that Element Manager. Use the Add CIMOM Connection window
to define information about the CIMOM (Figure 6-78).

Note: The DS8000 CIMOM can be also added manually or by a Discovery job within TPC
when the CIMOM is in the same subnet as the TPC server.

Figure 6-78 Adding DS8000 CIMOM using the Configure Agent window


Launch Element Managers
There are different ways of launching storage subsystems Element Managers in TPC BE. In
this section, we show you how to launch it from Disk Manager, the Element Manager options
in the Navigation Tree, or through the Topology Viewer.

Disk Manager option
To launch Element Managers from the Disk Manager option, expand Disk Manager in the
Navigation Tree and click Storage Subsystems. In the right pane, select the subsystem that
you want to launch Element Manager and click the Launch Element Manager button
(Figure 6-79).

Figure 6-79 Launch Element Manager

The ESS and SVC storage subsystems Element Managers open in a Web browser
(Figure 6-80 and Figure 6-81 on page 170).

Figure 6-80 ESS Element Manager


Figure 6-81 SVC Element Manager

The DS8000 storage subsystems Element Manager open in the Element Management
perspective (Figure 6-82).

Figure 6-82 DS8000 Element Manager

Navigation Tree option
The DS8000 Element Manager can also be launched from the Navigation Tree. Expand
Element Manager in the Navigation Tree, click IBM DS8000, and in the right pane, click the
Element Management button. You can also click the Element Management button in the
TPC toolbar (see Figure 6-83 on page 171).


Figure 6-83 Launch Element Management

The Element Management perspective is opened (see Figure 6-84). You can start the
DS8000 Element Manager by clicking the link in the Name column, or selecting the name of
the DS8000 Element Manager from the Select a view drop-down menu.

Figure 6-84 Launch DS8000 Element Manager


Topology Viewer option
To launch Element Managers from the Topology Viewer, expand IBM TotalStorage
Productivity Center → Topology → Storage (Figure 6-85).

Figure 6-85 Topology Viewer - Storage


In the Topology Viewer pane, expand the Subsystems group and select the storage
subsystem whose Element Manager you want to launch. Right-click it to open a pop-up menu
and select Launch Element Manager (Figure 6-86).

Figure 6-86 Launch Element Manager from Topology Viewer


Another way of launching Element Managers from the Topology Viewer is from the
Subsystem table. Expand IBM TotalStorage Productivity Center → Topology → Storage
and select the storage subsystem in the table whose Element Manager you want to launch,
and from the Action drop-down menu, select Launch Element Manager (Figure 6-87).

Figure 6-87 Launch Element Manager from Topology Viewer


6.5.2 Switch Element Manager
In this section, we describe how to define and launch the Switch Element Manager.

Define element managers
After expanding IBM TotalStorage Productivity Center → Topology → Switches, the
Topology Viewer in the right pane shows groups of discovered switches (Figure 6-88).

Figure 6-88 Topology viewer - Switches


Expand the Switches group in the Topology Viewer and select the switch (Figure 6-89).

Figure 6-89 Expanded switch group

To set the Element Manager for the switch, right-click the switch in the Topology Viewer and
click Launch Detail Panel (Figure 6-90 on page 177).


Figure 6-90 Launch Detail window in a pop-up menu

In the panel, click the Set button, and in the Edit Element Manager window, enter the URL of
the Element Manager or the fully qualified name of the executable file (see Figure 6-91).

Figure 6-91 Switch Element Manager information


Launch element managers
To launch Switch Element Managers from the Topology viewer, expand IBM TotalStorage
Productivity Center → Topology → Switches (Figure 6-88 on page 175). In the Topology
Viewer pane, expand the Switches group, select the switch whose element manager you
want to launch, right-click it, and select Launch Element Manager (Figure 6-92).

Figure 6-92 Launch Element Manager pop-up menu

Another way of launching Element Managers from the Topology Viewer is from the
Subsystem table. Select the switch in the table that you want to launch the Element Manager
from and, from the Action drop-down menu, select Launch Element Manager (Figure 6-93
on page 179).


Figure 6-93 Launch Element manager drop-down menu

6.5.3 Tape Library
Here we discuss using Element Mangers in tape libraries.

Define Element Managers
The CIMOM Discovery job discovers and identifies tape libraries in the managed environment
and collects tape library information. Element Manager information is also discovered through
the Discovery job.

Launch Element Managers
To launch the Tape Library Element Managers, expand Tape Manager in the Navigation Tree
and click Tape Libraries. In the right pane, select the tape library that you want to launch the
Element Manager for and click the Launch Element Manager button (Figure 6-94).

Figure 6-94 Launch Element Manager button


The Tape Library Element Manager opens in a Web browser (Figure 6-95).

Figure 6-95 Tape Library Element Manager


To launch Element Managers from the Topology Viewer, expand IBM TotalStorage
Productivity Center → Topology → Storage (Figure 6-96).

Figure 6-96 Topology Viewer - Tape Libraries


In the Topology Viewer pane, expand the Tape Libraries group and select the tape library
whose Element Manager you want to launch. Right-click it to open the pop-up menu and
select Launch Element Manager (Figure 6-97).

Figure 6-97 Launch Element Manager pop-up menu

6.5.4 External tools
The external tools in the TPC BE Navigation Tree provide a simple way to configure and
launch different Web GUIs or local executables and TPC for Replication GUI from within TPC
BE. TPC for Replication GUI is auto-configured during Data server startup if the TPC for
Replication is running on the SSPC with TPC SE. It can also be configured manually. Other
external tools, like URLs or scripts, must be added manually.

With external tools you can do the following, depending on your TPC authorization:
Add TPC for Replication GUI manually.
Add external tools manually.
Launch external tools.
View external tools.
Edit external tools.
Remove external tools.

All external tools have the URL/Command, Label, and Description attributes. You can change
the attributes by expanding Administrative Services → Configuration, right-clicking
Manage Element Manager, and selecting Configure (Figure 6-98 on page 183), which
opens the Configure Element Launcher window (Figure 6-99 on page 183).


Figure 6-98 Configure Element Managers

Figure 6-99 Element Manager configuration window

As the external tools make use of the Element Manager code to launch external tools, and as
they use the same configuration facility used for Element Managers, you can also add
different Element Managers to the external tools, such as storage subsystems, tape library, or
switches.

Adding external tools
External tools must be added manually to TPC BE manually, except for a TPC for Replication
GUI if it is running on the SSPC server. Possibilities for external tools include the following:
External programs
URLs (for example, search engines and Web encyclopedias)
Shell scripts or batch files (These scripts must exist on the system where the TPC GUI is
being run.)


To add an external tool manually, go to the TPC Navigation Tree and expand IBM
TotalStorage Productivity Center. Right-click External Tools and select Add Tool
(Figure 6-100).

Figure 6-100 Add External Tools

The Add External Tool window opens. Enter the external tool definitions (Figure 6-101).

Figure 6-101 Add External Tool window

You can add different Element Managers (Figure 6-102 on page 185) and start it by
expanding IBM TotalStorage Productivity Center → External Tools.


Figure 6-102 External Tools

Right click the tool you want to launch and click Launch Tool to open the tool in Web browser
(Figure 6-103).

Figure 6-103 Launch External Tools


7

Chapter 7. Upgrading SSPC and using
additional functions
In this chapter, we detail the additional features and functions when your TPC BE is upgraded
to a TPC SE, the Agent Manager is installed, and agents are deployed.


7.1 Upgrading SSPC
Upgrading SSPC and using the additional functions requires that you upgrade your TPC BE
(pre-installed on the SSPC) to TPC SE, install Agent Manager, and deploy agents. Upgrading
SSPC gives you additional storage reporting and performance management functions. The
additional functions that you get after upgrading TPC BE to TPC SE on your SSPC are:
Capacity Analysis / Predictive Growth
Customized and detailed capacity reporting, including chargeback and database reporting
Performance reporting (IBM and SMI-S storage arrays)
Threshold reporting (IBM and SMI-S storage arrays)
Fabric performance reporting and monitoring
SAN Volume Controller performance management
Full Provisioning (including Fabric zoning and Disk LUN assignment)

Note: Upgrading SSPC includes the TPC BE upgrade to TPC SE. Additionally, it can
include the SVC GUI and CIMOM upgrade if necessary.

7.1.1 TPC BE upgrade
If you want to upgrade TPC BE with new components, all you have to do is purchase the
additional licenses, and then activate the license files on your system. The additional
components in TPC SE are pre-installed and require a license key to be activated. This topic
provides information about how to upgrade TPC BE with the components and activate the
license files.

You can easily upgrade TPC BE with the following components:
IBM TotalStorage Productivity Center for Data
IBM TotalStorage Productivity Center for Disk
IBM TotalStorage Productivity Center for Fabric
IBM TotalStorage Productivity Center Standard Edition (includes Disk, Data, and Fabric)

Note: IBM TotalStorage Productivity Center for Replication is not preloaded on SSPC.
TPC for Replication is an optional application that you can install on the SSPC server.

To check the type of license you already have, look for the .sys files in the installation
directory:
TPCBE0303.SYS2 indicates you have a TPC BE license.
BTSSE03_03.SYS indicates you have a TPC SE license.

When upgrading TPC BE with TPC for Disk, TPC for Fabric, TPC for Data, TPC SE or
installing TPC for Replication on SSPC server, it is recommended to add the SSPC
Performance Upgrade Kit. This kit provides a second processor and an additional 4 GB of
RAM.

We show you how to upgrade TPC BE to TPC SE, which includes TPC for Disk, TPC for
Data, and TPC for Fabric components. The procedure is the same if you plan to upgrade TPC
BE with other components.


To upgrade the TPC BE, start the installation program from the CD/DVD that has the licence
you want to upgrade to. After accepting the license agreement, you are asked to select the
installation, as shown in Figure 7-1. Select Installation licenses and click Next to continue.

Figure 7-1 Installing licenses

Chapter 7. Upgrading SSPC and using additional functions 189

The licenses are successfully installed when the window shown in Figure 7-2 appears. Click
Next and exit the installer.

Figure 7-2 Successfully installed licenses

To activate the licenses, you must stop the TPC GUI (exit the TPC GUI application) and stop
the TPC services. Stop Device server and then Data server (refer to Figure 7-3 and
Figure 7-4 on page 191).

Figure 7-3 Stopping Device server


Figure 7-4 Stopping Data server

Start the services in reverse order, that is, first Data server and then Device server (refer to
Figure 7-5 and Figure 7-6 on page 192).

Figure 7-5 Starting Data server


Figure 7-6 Starting Device server

Start the TPC GUI and TPC BE is successfully upgraded with the new components.

7.1.2 SVC GUI and CIMOM upgrade
Updating the SVC GUI and CIMOM will require a code download to the SSPC and local
install of the updated software. Upgrading the SVC software is described in detail in IBM
System Storage SAN Volume Controller Software Installation and Configuration Guide for
Version 4.2.1, SC23-6628.

7.2 Installing Agent Manager and deploying agents
Agent Manager is an optional component in TPC V3.3.1 and is not a prerequisite for the TPC
code install. Agent Manager is not installed on SSPC; only TPC BE V3.3.1 is. If you decide to
upgrade your TPC BE to TPC SE, Agent Manager may be necessary. After you install the
Agent Manager, you must register the Device server and Data server before installing the
Data agents and Fabric agents.

These are the steps involved when installing and activating the Agent Manager and agents:
1. Agent Manager installation
2. Device server and Data server registration with the Agent Manager
3. Deploying Data agents and Fabric agents

In this section, we show you how to install Agent Manager and deploy agents.

7.2.1 Agent Manager installation
To install the Agent Manager, you must be logged on the SSPC server with administrative
authority. Start the installation wizard from the Agent Manager CD or directory where the
Agent Manager code is downloaded. The installer program is placed in the source installation
directory called EmbeddedInstaller.


The Agent Manager installer expects to use the default JVM and SSPC does not have one.
The JVM needs to be invoked from a command-line prompt and pointed to the TPC JVM. The
command is:
setupwin32 -is:javahome “cProgramFilesIBMTPCjre”

The Agent Manager installer opens the window where you choose the run time container for
Agent Manager (Figure 7-7). Select the embedded version of the IBM WebSphere Application
Server delivered with the Agent Manager. Click Next to continue.

Note: TPC only supports an Agent Manager configured to run with the embedded version
of the IBM WebSphere Application Server.

Figure 7-7 Runtime container for the Agent Manager


In the next window, specify the directory where Agent Manager will be installed (Figure 7-8).
We accepted the default. Click Next to continue.

Figure 7-8 Agent Manager installation directory

In the next window, specify the Agent Manager Registry database. Select the first option to
use DB2 on the SSPC server (Figure 7-9 on page 195). Click Next to continue.

Note: To ensure ease of installation, maintenance, and support, TPC only supports an
Agent Manager configured to run a local DB2 database server.


Figure 7-9 Agent Manager database

In the next window, select a database software directory and database name for the Agent
Manager database (Figure 7-10). Accept the defaults and click Next to continue.

Figure 7-10 Agent Manager database installation information


The Database User Information window opens (Figure 7-11). Specify the DB2 administrator’s
user name and password. The DB2 on the SSPC is installed using the defaults of db2admin
and passw0rd. Click Next to continue.

Figure 7-11 Agent Manager database user information

Figure 7-12 on page 197 shows the window where you specify the WebSphere Application
Server connection information. Enter the information and click Next to continue. If you specify
a host name, use the fully qualified host name. This value is used for the URLs for all Agent
Manager services. We recommend that you use the fully qualified host name rather than an
IP address. If you do not use the fully qualified host name, you will likely have problems with
the agents connecting to the Agent Manager.


Figure 7-12 WebSphere Application Server connection information

If you do not specify a fully qualified host name for the Agent Manager host, you will be
presented a window similar to Figure 7-13. If you have specified an IP address or a short host
name, the window contains the reasons why the fully qualified host name is preferred. Click
Next to accept the specified value or click Back to change it.

Figure 7-13 WebSphere Application Server connection information summary


The next window (Figure 7-14) shows you the WebSphere Application Server connection
information. Accept the defaults and click Next.

Figure 7-14 WebSphere Application Server information

The Security Certificates window (Figure 7-15) appears. You should choose to generate
unique certificates for a secure environment. Click Next to continue.

Figure 7-15 Agent Manager security certificates

The next window (Figure 7-16 on page 199) is the Define the Certificate Authority window.
You should specify a password for the Security Certificates and record it. Click Next to
continue.


Figure 7-16 Certificate authority details

The Set Passwords window gives you the option to specify the Agent Manager password and
Agent Registration password (Figure 7-17 on page 200). Make sure you record these
passwords. After entering the passwords, click Next to continue.

Important: Agent Manager password is the resource manager registration password. This
password is used to register the Data server or Device server with the Agent Manager. The
default user name/password is manager/password, which cannot be changed here.

Agent Registration password is the password used to register the common agents (Fabric
agent and Data agent). You must supply this password when you install the agents.


Figure 7-17 Setting the passwords

The summary window is displayed (Figure 7-18). Review the information. If you want to
change any settings, click Back and return to the window where you set the value. When you
are satisfied with the changes, click Next to continue.

Figure 7-18 Agent Manager installation summary

An installation progress window (Figure 7-19 on page 201) displays the installation progress
for IBM WebSphere Application Server. Wait for the installation to complete and click Next.


Figure 7-19 IBM WebSphere Application server installation

After IBM WebSphere Application Server has been installed and configured, you will see the
summary information window for Agent Manager. This window indicates where Agent
Manager will be installed and the size of the program. Review the information and click Next
(Figure 7-20).

Figure 7-20 Agent Manager installation summary


Several installation progress windows are displayed for the Agent Manager (Figure 7-21).

Figure 7-21 Agent Manager installation

After the installation is complete, the Start the AgentManager Application Server window is
displayed (Figure 7-22).

Figure 7-22 Starting Agent Manager

Select Yes, start AgentManager now and click Next to continue. The next window indicates
that the WebSphere Application Server is starting the Agent Manager (Figure 7-23 on
page 203).


Figure 7-23 Starting Agent Manager

When the Agent Manager is started, the Summary of Installation and Configuration Results
window is displayed (Figure 7-24). This window indicates that the Agent Manager is
successfully installed with all of its components.

Figure 7-24 Installation summary


Review the window and click Next. It opens the last installation panel with the Summary
Information (Figure 7-25), which shows that the installation is complete and the Agent
Manager application server has been started. Click Finish to exit the installation.

Figure 7-25 Finish the installation

Verify install
After the installation wizard completes, we run the healthcheck.bat command to verify that
the Agent Manager is running. This command is located in c:/Program
Files/IBM/AgentManager/toolkit/bin. You must specify the Agent Registration password that
you specified in Figure 7-17 on page 200. Example 7-1 shows the output of the command.
Note the Health Check passed information at the bottom of the output.

For more information about the healthcheck command, see the README file also located in
the toolkit directory.

Example 7-1 HealthCheck command output
C:Program FilesIBMAgentManagertoolkitbin>healthcheck -registrationPw passw0rd
1 file(s) copied.
Tool Launcher is trying to instantiate Command line tool com.tivoli.cas.manager.tools.HealthCheck ...
Command Line Tool com.tivoli.cas.manager.tools.HealthCheck succesfully instantiatied.
Nov 16, 2007 5:15:06 PM EST Arguments passed to Command Line Tool: -HOST localhost -registrationPw passw0rd
Nov 16, 2007 5:15:07 PM EST Initializing configuration with file:C:Program
FilesIBMAgentManagertoolkitbinconfigendpoint.properties
Nov 16, 2007 5:15:07 PM com.tivoli.agentmgr.credentialmgr.ARSPKIClient getProxyConfiguration
SEVERE: CTGEM0016E The ARS.port.public parameter cannot be NULL.
Nov 16, 2007 5:15:07 PM com.tivoli.agentmgr.util.security.CRLTrustManager getCRL
SEVERE: BTC1048E
Nov 16, 2007 5:15:07 PM com.tivoli.agentmgr.client.proxy.WSDLClient$AddressCacheItem tryConnect
INFO: NOTE ==>Connected to host=localhost on port=9511
Nov 16, 2007 5:15:07 PM com.tivoli.agentmgr.client.proxy.WSDLClient$AddressCacheItem directConnect
INFO: Directly connected
Nov 16, 2007 5:15:07 PM com.tivoli.agentmgr.credentialmgr.ARSPKIClient getProxyConfiguration
SEVERE: CTGEM0016E The ARS.port.public parameter cannot be NULL.
Nov 16, 2007 5:15:07 PM com.tivoli.agentmgr.util.security.CRLTrustManager getCRL
SEVERE: BTC1048E
Agent Manager Name:
ibm-cdm:///CDM-ManagementSoftwareSystem/TivoliGUID=B05F0EE180E811DC8004001641EDB5FA,InstallPath=file%3A%2F%2F%2FC%3A%
2FProgram%20F
iles%2FIBM%2FAgentManager,Feature=CTGEM
Registration.domain = DomainName
CA.keyRing.name = certs/CARootKeyRing.jks
CA.Certificate.Root.Alias = rootcert


CA.Key.Root.Alias = rootkey
CA.CRL.TimeToLive = 24
CA.CRL.filename = certs/CertificateRevocationList
Registration.Agent.Reregistration.Policy = Any
Registration.Agent.Certificate.Duration = 365
Registration.Manager.Certificate.Duration = 3600
CA.Certificate.graceTime = 1380
Config.Server.Host = SSPCPOK
Config.Server.Port = 9512
Config.URI = /AgentMgr/ConfigurationUpdate
CertManagement.Host = SSPCPOK
CertManagement.Renewal.Port = 9512
CertManagement.Renewal.URI = /AgentMgr/CertificateRenewal
CertManagement.CRL.Port = 9513
CertManagement.CRL.URI = /AgentMgr/CRLRequest
CertManagement.Revoke.Port = 9512
CertManagement.Revoke.URI = false
AgentQuery.Host = SSPCPOK
AgentQuery.Port = 9512
AgentQuery.URI = /AgentMgr/AgentQuery
CommonAgentQuery.URI = /AgentMgr/CommonAgentQuery
AgentConfiguration.Host = SSPCPOK
AgentConfiguration.Port = 9512
AgentConfiguration.URI = /AgentMgr/AgentConfiguration
AgentManagerQuery.Host = SSPCPOK
AgentManagerQuery.Port = 9511
AgentManagerQuery.URI = /AgentMgr/AgentManagerQuery
Registration.Host = SSPCPOK
Registration.Port = 9511
Registration.URI = /AgentMgr/Registration
Status.timeToLive = 0
ARS.directory = C:/Program Files/IBM/AgentManager
ARS.port.base = 9511
ARS.port.secure = 9512
ARS.port.public = 9513
ARS.URI.root = /AgentMgr
ARS.security.enabled = true
Status.Authorization.Required = true
Access.restriction.revocation = true
Access.restriction.Configuration = true
Query.Agent.Max.Return = -1
Query.Database.Type = db2
ARS.version = 1.3.2.21
Key.Algorithm.Name = RSA
Config.Listener.Manager = com.tivoli.agentmgr.spi.providers.makeAgentRegistryUpdate,
com.tivoli.agentmgr.cert.AgentStatusChangeLis
tener
Config.Listener.Agent = com.tivoli.agentmgr.spi.providers.makeAgentRegistryUpdate
Registration.Listeners.Manager.Request = com.tivoli.agentmgr.registration.AuthorizationValidator,
com.tivoli.agentmgr.registration.AuthorizationT
estOnly, com.tivoli.agentmgr.registration.AgentReregistrationTest
Registration.Listeners.Manager.Issue = com.tivoli.agentmgr.registration.StoreCertificateListener
Registration.Listeners.Agent.Request = com.tivoli.agentmgr.registration.SimplePWRequestValidator,
com.tivoli.agentmgr.registration.Authorizatio
nTestOnly, com.tivoli.agentmgr.registration.AgentReregistrationTest
Registration.Listeners.Agent.Issue = com.tivoli.agentmgr.registration.StoreCertificateListener
Nov 16, 2007 5:15:07 PM EST Health Check passed.
Nov 16, 2007 5:15:07 PM EST Command Line Tool execution successful.

7.2.2 Device server and Data server registration with the Agent Manager
The Agent Manager is the central network element that, together with the distributed Agents,
builds an infrastructure that is used by other applications to deploy and manage an agent
environment. Each application uses a Resource Manager (Data server and Device server) to
integrate into this environment.


Before activating Agent Manager and deploying agents, Device server and Data server must
register with the Agent Manager. To register the Device server and Data server with the Agent
Manager, follow these steps:

Important: Make sure that this is the Agent Manger that you want to register. Once you
register it with the Device server and Data server, you cannot unregister it. The only way to
unregister it is to uninstall TPC.

1. Expand Administrative Services → Configuration and select Agent Manager
Registration in the Navigation Tree. Agent Manager Registration opens in the right pane
(Figure 7-26).

Figure 7-26 Agent Manager registration window

2. Click the Agent Manager Registration button. The Agent Manager Registration window
opens (Figure 7-27 on page 207).


Figure 7-27 Agent Manager registration information

Enter the host name for the Agent Manager. If you specify a host name, use the fully qualified
host name. We recommend that you use the fully qualified host name rather than an IP
address. Leave the default ports. Port 9513 is the public port used for updates and port 9511
is the secured port used for registration.

Enter the user ID and password used to register the Data server and Device server with the
Agent Manager.

Note: The default user ID used to register Data server and Device server is manager with
the default password password.

Enter the common agent password, which is used to register the common agents with the
Agent Manager.

Note: The agent registration password was specified when you installed the Agent
Manager (Figure 7-17).


3. Click OK after you enter all the information. The Agent Manager Registration window
shows the registered Agent Manager and successful registration (Figure 7-28).

Figure 7-28 Registered Agent Manager

7.2.3 Deploying Data and Fabric agents
Deploying Data and Fabric agents gives you full SSPC functionality and a complete view of
your infrastructure. As shown in Figure 7-29 on page 209, the Data agents are installed on
every computer system you want TPC to manage, while Fabric agents are installed on
computer systems that have fiber connectivity (through HBAs) into the SAN fabrics you want
to manage.You only need one Fabric agent per SAN fabric, but two are recommended for
redundancy.

Data agents collect information from the server on which they are installed. Asset information,
file and file system attributes, and any other information needed from the computer system is
gathered. Data agents can also gather information about database managers installed on the
server. You can create pings, probes, and scans to run against the servers that have Data
agents installed.

Fabric agents use scanners to collect information. The scanners are written in O/S native
code, and communicate through the HBA to collect fabric topology information, port state
information, and zoning information. They also can identify other SAN attached devices (if
they are in the same zone). Using O/S system calls, they collect information about the system
on which they are installed. Fabric agents are discovered during the agent install process,
and do not need to be discovered separately; it is not possible to do so.


Figure 7-29 Deploying agents

Agent deployment types
There are two ways of deploying the Data agent and Fabric agent. You can choose between
local installation and remote installation.

Local installation means that you must be logged on to the computer on which you want to
install the agent code. You can install the Data agent and the Fabric agent in any order and
you can install them both at one time. In any case, the TPC Installer will check if there is a
Tivoli Common Agent already installed. If not, TPC installs this component.

You can perform the local installation process either interactively using a GUI or in unattended
(silent) mode. This is useful in cases where you have to script the installation or where you do
not have access to the GUI (for example, telnet access only). Local agent installation might be
practical for a limited number of computers, but becomes rather elaborate and
time-consuming as the number of managed computers grows.

Remote installation is the process of pushing the agent code from a central computer over
the network to any number of remote computers on which you would like to install the agents.
The TPC Installer pushes the agent code to the target computers concurrently, so the
software can be installed onto a large number of remote computers at one time. The
supported operating systems for the target computers are Windows, UNIX, and LINUX. In a
remote installation, the Tivoli Common Agent is only installed with the Data Agent. It has to be
already present when you attempt to do a remote installation of the Fabric agent.
Consequently, you always must install the Data Agent first when performing remote
installations. However, you can also choose to install the Data Agent and the Fabric agent
together. In this case, the TPC Installer manages the proper sequence.

The remote installation of the Data Agent and the Fabric agent has to be performed from the
server where the TPC Server is installed and running. A remote agent installation is always
interactive.

Note: Installation of Data agents and Fabric agents is described in detail in IBM
TotalStorage Productivity Center Installation and Configuration Guide Version 3 Release
3.1, GC32-1774.


7.3 Additional Standard Edition functions
TPC BE provides value in addition to the DS8000 Storage Manager or SVC Console.
However, TPC BE is not a complete Storage Management solution. Upgrading SSPC to TPC
SE gives you many more features, such as greater reporting, disk performance analysis,
provisioning, predictive analysis, and SAN planning.

Upgrading SSPC to TPC SE gives you additional functions that come, by default, with TPC
SE:
Capacity Analysis / Predictive Growth
Customized and detailed capacity reporting, including chargeback and database reporting
Performance reporting (IBM and SMI-S storage arrays)
Threshold Reporting (IBM and SMI-S storage arrays)
Full Provisioning (including Fabric zoning and Disk LUN assignment)

In this section, we describe some of the storage management functions that are available in
TPC SE. For detailed information about these functions, refer to the IBM Redbooks
publication TotalStorage Productivity Center V3.3 Update Guide, SG24-7490.

7.3.1 Collecting storage usage and trending information
To collect statistics about the usage and trending of storage consumption within your
environment, use a scan collection job. You can view the information collected by scans in
Capacity, Usage, Usage Violations, Backup, and System reports, as well as use that
information as part of quota analysis. Scans are always directed against a Data agent and
deliver very detailed information about the file systems, files, and RDBMS objects (instances,
databases, devices, table spaces, tables, indexes, data files, and containers) of computers.
Use the statistics gathered by scans to:
View information about when storage resources are created, accessed, and modified and
by what group or user.
Map the actual storage resource to the consumers of that resource.
Generate a historical view of storage consumption to help determine usage trends over
time.

You can define any number of scans to gather information about different storage resources
at different times.

7.3.2 Determining the availability of storage resources
To collect information about the availability of the storage resources in your environment, use
a ping job. You can view the information collected by pings in Availability and System reports.
Pings enable you to monitor and report on the availability of your storage from a network point
of view or from a computer uptime perspective. You can see the percentage of off-network
time due to network problems or system downtime. Define any number of pings that each
check the availability of a unique storage resource. Pings are available with TPC BE.


7.3.3 Storage provisioning using SAN Planner
The SAN Planner allows the user to perform end-to-end planning involving fabrics, hosts,
storage controllers, storage pools, volumes, paths, ports, zones, and zone sets. Once a plan
has been generated, the user can select to have the plan implemented by TPC. This function
was introduced in TPC V3.3. In this section, we provide an overview of the SAN Planner. For
detailed information, refer to the IBM Redbooks publication TotalStorage Productivity Center
V3.3 Update Guide, SG24-7490.

Volume Planner
The Volume Planner was formerly known as the Volume Performance Advisor (VPA) in
previous versions of TPC. It plans and selects appropriate storage controllers, storage pools,
and storage volumes (when using unassigned volumes) that satisfy the user’s inputs. It allows
you to select controller type preferences, whether storage requests can be satisfied by
multiple controller types, and RAID levels. The Volume Planner uses the current performance
utilization of storage resources to determine whether a new volume should be allocated on a
particular pool in a particular storage controller, so it is important to have a representative
collection of performance data in your TPC DB2 repository. If multiple storage pools from
different controllers can potentially satisfy your provisioning request, then the Volume Planner
will use the rated utilization of the pools (the sum of the previous provisioning performance
requirements, which might be greater than the current utilization) to break the ties and select
a candidate storage pool.

Note: Before using the Volume Planner to allocate storage based on performance
characteristics, a Performance Monitor job must be run on the target subsystem. The more
performance data in your TPC database, the better the recommendation by the Volume
Planner.

Figure 7-30 Volume Planner


Path Planner
The Path Planner allows the setup of multipath options. The Path Planner enables system
administrators and SAN administrators to plan and implement storage provisioning for hosts
and storage subsystems with multipath support in fabrics managed by TPC. Planning the
paths between the host(s) and storage controller requires designing paths between hosts and
storage subsystems that will be implemented through zones in the fabric.

Note: IBM Subsystem Device Driver (SDD) must be installed on a host in order to invoke
the Path Planner.

The Path Planner is used for specifying multiple paths options between selected hosts and
storage subsystems. Path Planner assists the administrator in the multipath tuning process
through the selection of these policies:
The Multipath Option specifies how the driver uses the paths between the host and the
storage subsystem. The options are:
– Load Balancing sends Input/Output on all paths.
– Round Robin sends Input/Output on one path until a time interval expires (set in an
SDD setting at the host) or stops to use another path.
– Fail-Over sends Input/Output on one path until a failure occurs and fails over (switches)
to another path.
The Specify number of paths option specifies the number of paths between each host and
the storage subsystem.
Use fully redundant paths. The Path Planner will check for redundant fabrics between
each host and storage subsystem and create paths in each fabric. This requires at least
two fabrics.

Workload profiles provide the Path Planner with estimates of the required I/O traffic. These
estimates are used to determine the number of paths required from each host to the storage
subsystem and select the multipath driver path utilization. The number of paths and the driver
multipath mode can be adjusted by the performance requirements specified through the
selection of a workload profile.

The Path Planner does not directly interact with the Zone Planner. It provides the path
information that the Zone Planner uses. Each path is represented by a host port WWPN,
target port WWPN, and a Volume ID for the volume on the target that is mapped to the host
port. These paths are created when the Zone Planner is implemented.


Figure 7-31 Path Planner

Zone Planner
The Zone Planner allows the user to implement automatic zoning between ports on the
selected hosts and subsystems in a fabric. All zoning is based on WWPNs. The Zone Planner
will plan zoning configuration for new storage that is provisioned for use by a host. For
example, it can be used when a new storage volume is created and assigned to a host. It can
also be used with a volume that has already been created and is assigned to a host needing
more storage. In these cases, the Path Planner and Volume Planner determine which host
and storage need to be zoned together, providing the Zone Planner the exact set of ports
which need to be zoned together. The Zone Planner then uses the zoning inputs for the
planning. If the Volume and Path Planners are not used, the user may select the host and
storage ports and then invoke the Zone Planner.

The Zone Planner expects a list of host port and storage port pairs as input. If the Path
Planner has been invoked prior to the Zone Planner, its output is used as input to the Zone
Planner. If the subsystem/host are within the same fabric and Zone Planner is not checked,
then existing zones or zone sets are used. If Zone Planner is checked, this creates a new
zone or zone set.

Note: For the Zone Planner to create zones, the host and subsystem must be within the
same fabric.


For the case where the host and subsystem reside in more than one of the same fabrics, you
are given two options. The first option is to create identical zones in all of the fabrics. The
second option is to select specific fabrics to create identical zones in. The guidance policies
used for zone planning are as follows:
One zone per host bus adapter (HBA)
One zone per host
One zone per host port
Auto zone: Largest zone that satisfies the validation policies

The validation policies used for zone planning are as follows:
No two controllers of different types should be in the same zone.
Maximum number of zone members in a zone = N.
Maximum number of zones in a fabric = N, where N is specified by the user.

Figure 7-32 gives an overview of the Zone Planner.

Figure 7-32 Zone Planner

Data Path Explorer
The Data Path Explorer view in the Topology Viewer allows you to view the paths between
servers and storage subsystems or between storage subsystems (for example, SVC to
back-end storage or server to storage subsystem). Performance and health overlays on this
view will provide a mechanism to assess the impact of performance or device state in the
paths on the connectivity between the systems. The view will consist of three panes (host
information, fabric information, and subsystem information) that show the path through a
fabric or set of fabrics for the endpoint devices (host to subsystem or subsystem to
subsystem). Figure 7-33 on page 215 shows the Data Path Explorer in the Topology Viewer.


Figure 7-33 Data Path explorer

A possible scenario utilizing this feature is an application on a host that is running slow. The
system administrator wants to discover what the health of the associated I/O path for that
application is. The questions that he might have are:
Are all components along that path healthy?
Are there any component level performance problems that might be causing the slow
application response?

The system administrator may also want to discover whether the I/O paths for two
applications (on separate host LUNs) are in conflict with each other. They could be sharing a
common component (like switch). After viewing the I/O paths for these two applications, he
makes the required zoning or connectivity change to alleviate the problem.

7.3.4 Enterprise rollup reporting
TotalStorage Productivity Center V3.3 introduced the ability to consolidate asset and health
information collected from multiple TPC instances, providing the ability of scalable enterprise
wide management of the storage environments.

TPC V3.3, illustrated in Figure 7-34 on page 216, provides an enterprise rollup of reporting
across multiple TPC servers in an environment. A recommended configuration is to have at
most one TPC server act as a “master” or “enterprise” server that gathers enterprise-wide
data for reports, and all other servers act as “subordinate” servers and provide data about
entities they manage. Note that “master” and “subordinate” denominations can change over
time. A master TPC server can also manage entities just like any ordinary TPC server and
report on these entities.

TPC subordinate servers should have no more than 1200 unique data sources. This number
includes Data agents, Fabric agents (inband and out of band), CIM agents, and VM agents
(VMWare). Once this threshold has been met, a new TPC subordinate server should be
deployed and all new agents should be pointed to it. If the same storage entity is managed by
multiple subordinate servers, rollup reports reflect the storage information from the
subordinate server that most recently probed that entity.


Figure 7-34 TotalStorage Productivity Center rollup overview

For the TPC Server rollup feature, all servers must be at TPC V3.3. TPC versions prior to
V3.3 (for example, TPC V2.3 or TPC V3.1) will not support the TPC Server rollup function.

Integrating SSPC
To integrate your SSPC into your existing TPC environment, an existing TPC server functions
as a Master TPC server. The Master TPC server collects data from subordinate TPC servers
and you can create rollup reports from the Master Server. Your SSPC server should function
as a subordinate TPC server, providing data to the Master TPC server.

Note: The ability to act as a Master Server and generate rollup reports is a function of TPC
Standard Edition. The Master TPC server is required to use TPC Standard Edition.

Rollup reports are generated through the TPC Navigation Tree. You can generate four
categories of rollup reports:
Asset: To view detailed statistics about agents, computers, storage subsystems, disk and
volume groups, disks, file systems, logical volumes, LUNs, and fabrics that are monitored
by subordinate servers.
Database Asset: To view detailed statistics that have been collected by subordinate
servers about the RDBMSs in your environment, including Oracle, SQL Server, Sybase,
and UDB/DB2.
Capacity: To view storage metrics related to the disk capacity, file system capacity, file
system used space, and file system free space gathered by the subordinate servers in
your environment.


Database Capacity: To view storage capacity, used space, and free space at the
computer, computer group, database, instance, and TPC server level for RDBMSs that are
monitored by subordinate servers.

Note: To generate a full report of your environment, you need to deploy a Data agent and
a Fabric agent on each server (that is fibre attached) that you want to manage. If a server
does not have agents installed, the information for that server will be omitted from the
rollup report you generate.

Asset reports
In the Asset category, the following reports can be generated:
Agents: To view information about Data agents and Device agents that are associated with
Computers: To view information about the hosts and computers that are monitored by
Storage Subsystems: To view information about the storage subsystems that are
Disk/Volume Groups: To view information about the disk and volume groups that are
Disks: To view information about the disks that are monitored by subordinate servers in
your environment.
File Systems or Logical Volumes: To view information about the file systems or logical
volumes that are monitored by subordinate servers in your environment.
LUNs: To view information about the LUNs that are monitored by subordinate servers in
your environment.
Fabrics: To view information about the fabrics that are monitored by subordinate servers in
your environment.

Database Asset reports
In the Database Asset category, the following reports can be generated:
All DBMSs: To view information about the RDBMSs that are monitored by subordinate
Oracle: To view information about Oracle instances that are monitored by subordinate
Sybase: To view information about Sybase instances that are monitored by subordinate
SQL Server: To view information about SQL Server instances that are monitored by
UDB: To view information about UDB/DB2 instances that are monitored by subordinate

Capacity reports
In the Capacity category, the following reports can be generated:
Disk Capacity: To view disk capacity information about the computers and storage
subsystems that are monitored by subordinate servers in your environment.
Filesystem Capacity: To view file system capacity information about the file systems that
are monitored by subordinate servers in your environment.


Filesystem Free Space: To view information about the available storage space on file
systems that are monitored by subordinate servers in your environment.
Filesystem Used Space: To view information about the used storage space on file systems
that are monitored by subordinate servers in your environment.

Database Capacity reports
In the Database Capacity category, the following reports can be generated:
All DBMSs: To view storage capacity information for the DBMSs that are monitored by
Oracle: To view storage capacity information for the Oracle databases that are monitored
Sybase: To view storage capacity information for the Sybase databases that are monitored
SQL Server: To view storage capacity information for the SQL Server databases that are
UDB: To view storage capacity information for the UDB/DB2 databases that are monitored

Creating a rollup report
To create a rollup report, you need to associate a subordinate TPC server with a Master TPC
server. To do this, you need to follow the following procedure:
1. In the Master TPC server, select IBM TotalStorage Productivity Center →
Administrative Services → Data Sources → TPC Servers and click Add TPC Server
(Figure 7-35).

Figure 7-35 TPC Servers window


2. In the Add TPC Server window shown in Figure 7-36, type the required information for the
subordinate TPC server. If you have installed the TPC V3.3.1 code, the Host Device
server Port is the device server port you created in Figure 4-22 on page 60. The Host
Authentication Password is the password you created in Figure 4-22 on page 60. Click
Save after you type in the required information.
If you selected the typical installation when you installed your TPC server software
package, you were only asked for the user name and password once. This password will
be both the DB2 administrator password and Host authentication password. You will use
the same password when you log in to TPC as well when you are asked for the Host
Authentication Password.

Figure 7-36 Add TPC Server window

3. Click the Save button, and the Master TPC server tests the connection with the
subordinate TPC server. If the testing is successful, the Master TPC server adds the
subordinate TPC server to its TPC server list (Figure 7-37).

Figure 7-37 Subordinate TPC server is added to the TPC server list


4. Before generating a rollup report, you need to run discoveries, probes, and scans from the
subordinate servers to gather information about their locally-monitored storage entities.
Also, you need to run probes from the master server to gather information about its
locally-monitored storage entities. Then you need to run TPC Server probes from the
master server against the subordinate servers to collect their storage information for the
rollup reports.
To run TPC Server probes, select, in the Navigation Tree, IBM TotalStorage Productivity
Center → Monitoring → TPC Server Probes and select Create TPC Server Probes
(Figure 7-38).

Figure 7-38 TPC Server Probes


5. In the Create TPC Server Probes window, select All TPC Servers and click >>
(Figure 7-39).

Figure 7-39 Create TPC Server Probes


6. After you click >>, All TPC Servers appears in the Current Selections pane. Click the
When to Run tab (Figure 7-40).

Figure 7-40 TPC Servers selection

7. To create a rollup report on a regular basis, you can schedule periodic probes in the When
to Run window. In this example, we select Run Now to show the concept of a rollup report.
After you select Run Now, click the disk icon on the menu bar to save the task
(Figure 7-41 on page 223).


Figure 7-41 When to Run window

8. After you click the disk icon, a small window pops up asking for the name of the probe.
Type the name of your choice and click OK (Figure 7-42).

Figure 7-42 Name of probe

9. The TPC Server Probe will be submitted. Click OK in the Notice window (Figure 7-43).

Figure 7-43 Notice window


10.Go back to TPC Navigation Tree, where you can see a probe is running. Wait until the
probe is finished, then you can generate a rollup report (Figure 7-44).

Figure 7-44 Probe TPC Servers

11.Figure 7-45 on page 225 shows the TPC Navigation Tree where selecting IBM
TotalStorage Productivity Center → Rollup Reports takes you to the different rollup
reports you can generate.


Figure 7-45 Rollup Report in TPC Navigation Tree


8

Chapter 8. DS8000 GUI under Element
Manager
The DS8000 GUI is now moved to the Element Manager function of SSPC. You can toggle
between the Enterprise Management, Element Management, and each DS8000 within the
Element Management. You also can launch the SVC Master Console.

This chapter describes what is new about Element Manager in the DS8000 GUI.


8.1 Launch DS8000 GUI from SSPC
You can start the SSPC by selecting Start → Programs → IBM TotalStorage Productivity
Center → Productivity Center.

Figure 8-1 is the main login window. Enter the TPC user ID and password and click OK.

Figure 8-1 SSPC login

Figure 8-2 is the main TPC BE window. You can launch Element Manager by pressing the
Element Management button or by expanding Element Manager.

Figure 8-2 Launch Element Manager from TPC main window

Figure 8-3 on page 229 shows the Element Manager window where you select the DS8000
for which you want to launch the GUI. Click the DS8000 that you want to configure.


Figure 8-3 DS8000 selection page

Figure 8-4 shows the DS8000 GUI Real-time manager window.

Figure 8-4 DS8000 GUI Real-time manager

Chapter 8. DS8000 GUI under Element Manager 229

Expand the arrow to the left of the Real-Time Manager. All the tasks are listed in Figure 8-5.

Figure 8-5 DS8000 GUI task list

8.2 What is new in the new DS8000 GUI
There are new improvements to the GUI in R3. Figure 8-6 on page 231 and Figure 8-7 on
page 231 show the new interface of the DS8000 on the Extent Pool. Figure 8-6 on page 231
shows the Capacity Summary of Extent Pool for Open Systems and System z™. It also
displays the unassigned capacity.


Figure 8-6 Extent Pool top of window

Figure 8-7 shows the bottom of the Extent Pool window. Clicking Select action selects the
Create New Extent Pools... menu item.

Figure 8-7 Extent Pool bottom of window


8.2.1 Creating Extent Pools using the Automatic function
Figure 8-8 through Figure 8-21 on page 244 show the steps required to create Extent Pools
using the Automatic function in the GUI. Using the Automatic function, DS8000 will pick the
ranks for the Extent Pool.

In Figure 8-8, under the Storage Type drop-down menu, choose the Fix Block (FB) for an
Open Systems server or Count Key Data (CKD) for a System z server.

Figure 8-8 Fix Block or Count Key Data selection


In Figure 8-9, choose, in the RAID Type drop-down menu, either a RAID 5 or RAID 10
configuration for the Extent Pool.

Figure 8-9 RAID 5 or RAID 10 selection


In Figure 8-10, select Select action → Create New Extent Pools.

Figure 8-10 Create New Extent Pools


From the Type of Configuration drop-down menu, select Automatic, which lets the system
provision ranks for the Extent Pool (see Figure 8-11).

Figure 8-11 Select Automatic Creation of Extent Pools


In the DA Pair Usage drop-down menu (see Figure 8-12), select Spread among all pairs in
the drop-down menu to allow the ranks to be spread among different Device Adapter (DA)
pairs in the DS8000.

Figure 8-12 Select Spread of storage with Device Adapter pairs in the DS8000


The Number of extent pools drop-down menu shown in Figure 8-13 allows you select the kind
of Extent Pools to create. Here we select Two extent pools (ease of management).

Figure 8-13 Select the kind of Extent Pool to create


The next step is to select the ranks for these two Extent Pools. Figure 8-14 shows the
available ranks. When you select the ranks, the bar graph to the right displays the available
and the assigned ranks.

Figure 8-14 Select the available ranks to configure


The Pool name prefix field shown in Figure 8-15 allows you to specify the name of the Extent
Pool. The system automatically appends a number sequence to the name of the Extent Pool
name starting with zero.

Figure 8-15 Fill in the prefix name of the Extent Pool


Figure 8-16 shows a final preview of the new Extent Pool to be created using the information
provided in Figure 8-7 on page 231 through Figure 8-15 on page 239. By clicking Create All,
the system will create the Extent Pools.

Figure 8-16 Preview of the new Extent Pools


Figure 8-17 shows the progress and the result of Extent Pool creation.

Figure 8-17 Successful creation of the Extent Pools


Figure 8-18 shows, in the Extent pools window, the newly created Extent Pools named
POOL_0 and POOL_1.

Figure 8-18 The new pools


We can display the ranks to see what Extent Pool the ranks belong to, as shown in
Figure 8-19.

Figure 8-19 Ranks display


You can download the rank information by clicking the Download spreadsheet button, as

Figure 8-20 Ranks display and Download spreadsheet

Figure 8-21 shows the Extent Pool and Rank relation. You will notice that by choosing
Automatic, the system chooses the rank numbers sequentially. In this example, the first
Extent Pool has ranks R9 to R12, and the second Extent Pool has ranks R13 to R16. R9 to
R12 are (6+P+S) ranks, while R13 to R16 are (7+P) ranks, which have more capacity per
rank. The two Extent Pools created have different capacities. In Figure 8-18 on page 242, you
can see that Extent Pool POOL_0 has 3492 GB and Extent Pool POOL_1 has 4072 GB.

If we want to have the same capacity in each Extent Pool, create one Extent Pool at a time
and choose a balance of (6+P+S) and (7+P) ranks. Section 8.2.3, “Make Extent Pools:
manual action” on page 250 describes the manual action that creates the Extent Pools.

Figure 8-21 Downloaded rank information


8.2.2 Delete Extent Pool
Figure 8-22 through Figure 8-26 on page 249 shows the steps to delete the Extent Pools
using the GUI.

Figure 8-22 displays the Extent Pools. Check the box on the left side of these Extent Pools to
delete them.

Figure 8-22 Check the Extent Pool to delete


From the Select Action drop-down menu, select Delete Pools, as shown in Figure 8-23.

Figure 8-23 Select Action: Delete Pools


Figure 8-24 shows the Delete Extent Pools window. The Volume IDs field shows NONE, as
there are no volumes in the Extent Pools selected.

Attention: Clicking Continue will commit the delete action, as shown in Figure 8-24.

Figure 8-24 Attention: Click Continue will commit the delete action


Figure 8-25 shows the progress of the delete action.

Figure 8-25 Delete Progress information

Figure 8-26 on page 249 shows the completion message.


Figure 8-26 Completion message


What if you try to delete an Extent Pool with volumes in it? Figure 8-27 is an example of
deleting such a pool. Carefully read the warning message. If you click Continue, the Extent
Pool and the volumes will be deleted, and the data in the volumes will be deleted.

Figure 8-27 Warning message: Delete Extent Pool with volumes in it

8.2.3 Make Extent Pools: manual action
Figure 8-28 on page 251 through Figure 8-36 on page 258 shows the steps to create Extent
Pools manually. You will create one Extent Pool at a time while picking the ranks that you want
to be included.

The first step, shown in Figure 8-28 on page 251, is to select FB or CKD as the Storage Type.
We selected CKD.


Figure 8-28 Fix Block (FB) or Count Key Data (CKD)

In Figure 8-29, choose either RAID 10 or RAID 5.

Figure 8-29 RAID 5 or RAID 10


In the Type of Configuration drop-down menu, select Manual, as shown in Figure 8-30.

Figure 8-30 Automatic or Manual method to create Extent Pools


In the Number of extent pools drop-down menu, select Single extent pool, as shown in
Figure 8-31.

Figure 8-31 The type of Extent Pools to create


In the Create New Extent Pools window shown in Figure 8-32, select the ranks for this single
Extent Pool and fill in the name of the Extent Pool prefix.

Figure 8-32 Single Pool creation


In the Server assignment drop-down menu, use the default server affinity, as shown in
Figure 8-33. After all the information is entered, click OK to continue.

Figure 8-33 Affinity to server 0 or 1


After verifying the required information, click Create All, as shown in Figure 8-34.

Figure 8-34 Verification and creation of the Extent Pool


Figure 8-35 shows the progress and then the successful completion message.

Figure 8-35 Success in creating Extent Pool


Figure 8-36 shows the list of Extent Pools. Check the new Extent Pools just created.

Figure 8-36 The Extent Pools with the same capacity

8.2.4 Add capacity to an Extent Pool
You can increase the capacity of an Extent Pool by adding one or more ranks to an Extent
Pool.


Figure 8-37 shows the window where you select the Extent Pool to increase its capacity.
Check the Extent Pool and then, under the Select Action drop-down menu, select Add
Capacity to Pool.

Figure 8-37 Add Capacity to an Extent Pool


Figure 8-38 shows the Type of Configuration menu, where you choose Automatic or Manual.
Automatic will choose the next available rank and then add it to the pool. Manual will let you
pick the rank. Here we chose Manual.

Figure 8-38 Select Automatic or Manual


Choosing Manual will list the available ranks, as shown in Figure 8-39. Select the rank to be
added to the Extent Pool.

Figure 8-39 Select Manual and the list of ranks available


Select the rank to be added to the Extent Pool, as shown in Figure 8-40. Click OK to continue.

Figure 8-40 Check the rank to be added to the Extent Pool

Figure 8-41 on page 263 shows the validation window. Click Create All to perform the action.


Figure 8-41 Validate and Create All

Figure 8-42 through Figure 8-44 on page 264 show the progress and completion information.

Figure 8-42 Progress information


Figure 8-43 Progress information

Figure 8-44 Completion message


Figure 8-45 displays the new Extent Pool capacity.

Figure 8-45 Check the capacity of the new Extent Pool

8.2.5 Remove capacity from Extent Pool
Figure 8-46 on page 266 through Figure 8-51 on page 270 show the steps to remove
capacity from an Extent Pool. You have to check Figure 8-49 on page 269 carefully before you
proceed. You have to make sure that there are no volumes or LUNs on the rank before you
proceed.

If you used Rotate Extents to create volumes or LUNs in this pool, you cannot remove
capacity from this Extent Pool. Please proceed with caution.


Select the Extent Pool and, from the Select Action drop-down menu, select Remove
Capacity from Pool, as shown in Figure 8-46.

Figure 8-46 Select Action and Remove Capacity from Pool


Figure 8-47 shows the list of ranks in the Extent Pool.

Figure 8-47 List of ranks in the Extent Pool


Next, check one or more ranks to be removed, as shown in Figure 8-48. When you have
checked the appropriate ranks, click Remove to continue.

Figure 8-48 Check the rank(s) to remove

Figure 8-49 on page 269 shows the validation window. Proceed with caution and validate that
there are no volumes in the ranks. Click Continue to commit the delete action.


Figure 8-49 Validate there are no volumes in the ranks

Figure 8-50 shows the progress information.

Figure 8-50 Progress message


Once the capacity is removed, you will see the completion message, as shown in Figure 8-51.

Figure 8-51 Completion message: capacity successfully removed

8.2.6 Make volumes
Figure 8-52 on page 271 through Figure 8-57 on page 275 show the steps to create CKD
volumes for a IBM System z server. We will create some mod 9s and create PAVs. We will
also create volumes using Storage Pool Striping.

Storage Pool Striping (rotate extents) stripes new volumes across all ranks of an extent pool,
which improves performance and reduces the administration required to balance system
loads.

The maximum volume size is limited to the currently supported maximum size for DS8000:
Open Systems (Fixed Block) volumes: 2 TB
System z (CKD) volumes: 65,520 cylinders


In Figure 8-52, select the storage Image and the LCU. Under the Select Action drop-down
menu, select Create.

Figure 8-52 Select the Storage Image and LCU


Select the Extent Pool, as shown in Figure 8-53, and click Next to continue.

Figure 8-53 Select the Storage Extent Pool

In the next window, define the base volume characteristics (see Figure 8-54 on page 273),
select the volume type of mod 9, and the extent allocation method (whether you want rank
striping or rotate extents).

Here are the differences between the Rotate Volumes and Rotate Extents options:
Rotate Logical Volumes: Each successive logical volume created is allocated on the next
available rank in the extent pool. Extents allocated for a given logical volume are located
on the selected rank. If the selected rank is full, or fills before the volume is fully
provisioned, extent allocation proceeds to the next available rank until the volume is fully
provisioned.
Rotate Extents: Extents allocated to a logical volume are successively rotated through the
ranks within an extent pool. Ranks that are full are skipped.
Rotate Logical Volumes Algorithm (earlier versions): The volume is created before the
current algorithms are implemented. These algorithms are variants of the Rotate Logical
Volumes algorithm in that they attempt to localize the extents of a logical volume on a
single rank. Logical volumes with this extent allocation method are treated as though they
were created with the rotate logical volumes algorithm with respect to any operations that
cause the allocation additional extents. This value is changed to the 1 if the volume is
relocated such that its extents are reallocated.


Figure 8-54 Select Rotate Volumes or Rotate Extents

Next, select the LCU, as shown in Figure 8-55, and click Next to continue.

Figure 8-55 Select the LCU


Next, enter the number of volumes, starting addresses, and ascending or descending order.
Click Next after entering the information to continue (see Figure 8-56).

Figure 8-56 Number of volumes to create, starting address, and Ascending or Descending order

Next, create the nicknames for the new volumes by specifying a prefix and suffix (see
Figure 8-57 on page 275). The nickname is a description within the DS8000. It is not the
VOLSER. The suffix number will be automatically incriminated. Click Next to continue.


Figure 8-57 Nickname of the volume

8.2.7 Assign Parallel Access Volumes (PAV) (alias volumes)
The IBM Parallel Access Volumes (PAV) feature of IBM DASD subsystems enable a single
System z server and applicable storage controllers to simultaneously process multiple I/O
operations to the same logical volume, which can help significantly improve I/O response
times by reducing device queuing delays.

After creating the volume nicknames, the next step is to define alias assignments. Figure 8-58
on page 276 through Figure 8-63 on page 280 show the steps to add an alias (PAV) to the
base volumes.


Check the base volumes that need an alias, as shown in Figure 8-58.

Figure 8-58 Select the base volumes


Next, enter the starting address of the PAV, as shown in Figure 8-59. PAV usually starts from
the 255 address of an LCU in descending order.

Figure 8-59 Starting address of PAV in descending order


Next, enter the number of PAVs for a base volume, as shown in Figure 8-60. Here we enter
three aliases for each base volume checked. The Add aliases button is in blue. You have to
click it to add the aliases. It will then change to black. Click Next to continue.

Figure 8-60 Add the number of alias per base volume checked


Figure 8-61 shows the verification for creating the CKD volumes. Click Finish to create the
base and alias volumes.

Figure 8-61 Click Finish to create the base and alias volumes


Figure 8-62 gives the status of the Create action.

Figure 8-62 Create action status

Figure 8-63 shows a list of base and alias volumes created.

GB( Base
VOL Base/ Volume Typ GB(2 10^ Cylinde Extent Volume
Nickname SER ID Alias Type e ^30) 9) rs Pool Number
CKD_0000 0800 Base 3390 StaZ 7.9 8.5 10,017 Pool_0_0 800
08F4 Alias 0 0 0 803
08F5 Alias 0 0 0 803
08F6 Alias 0 0 0 803
08F7 Alias 0 0 0 802
08F8 Alias 0 0 0 802
08F9 Alias 0 0 0 802
08FA Alias 0 0 0 801
08FB Alias 0 0 0 801
08FC Alias 0 0 0 801
08FD Alias 0 0 0 800
08FE Alias 0 0 0 800
08FF Alias 0 0 0 800
Figure 8-63 Base and aliases created


8.2.8 Dynamic Volume Expansion on System z
Dynamic Volume Expansion provides the ability to increase the size of a logical volume while
it is online in a host system. This option is available for Open System and IBM System z
hosts. The following scenario shows expanding a CKD volume. From the Select Action
drop-down menu, select Increase capacity.

Figure 8-64 Select the volumes to expand the capacity

Both a 3390-3 and 3390-9 can be expanded. If a 3390-3 is expanded past 3339 cylinders, the
device type will be changed to a 3390-9. A 3390-9 can be expanded up to 65,520 cylinders. A
SCSI LUN can be expanded up to the current supported size of 2,147,483,640 blocks.


The next step is to specify the new capacity, as shown in Figure 8-65. Click OK to continue.

Figure 8-65 Fill in the new capacity

You will see a window with considerations for volume expansion, as shown in Figure 8-66 on
page 283. Click OK to continue.


Figure 8-66 Validation to change volume size

After clicking OK, you will see the progress and completion message, as shown in
Figure 8-67.

Figure 8-67 Progress and completion message


Figure 8-68 shows the GUI display of the new capacity.

Figure 8-68 Volumes with the new capacity

8.2.9 Dynamic Volume Expansion on Open Systems
Figure 8-69 on page 285 through Figure 8-74 on page 288 are the steps to expand the
capacity of an open system LUN.

Figure 8-69 on page 285 shows a list of LUNs. We circled a LUN that we want to dynamically
expand the volume size of while it is still online with the operating system.


Figure 8-69 Volume list of open system LUNs

Check the volume that you want to expand, as shown in Figure 8-70. In the Select Action
drop-down menu, select Increase capacity.

Figure 8-70 LUN Increase capacity


In Figure 8-71, you enter the new capacity of the LUN. In Open System, the largest capacity
is 2 TB. You also have to make sure there is enough spare capacity in the Extent Pool for this
expansion. The GUI lists the maximum size available in the pool.

Figure 8-71 Enter the new capacity of the LUN

You will see a window with considerations for volume expansion, as shown in Figure 8-72 on
page 287. Click OK to continue.


Figure 8-72 Check to OK the capacity increase

After clicking OK, you will see the progress and completion message, as shown in
Figure 8-73.

Figure 8-73 Action Task Status display


Figure 8-74 shows the new capacity.

Figure 8-74 New capacity for Open System LUNs


Related publications

The publications listed in this section are considered particularly suitable for a more detailed
discussion of the topics covered in this book.

IBM Redbooks
For information about ordering these publications, see “How to get Redbooks” on page 289.
Note that some of the documents referenced here may be available in softcopy only.
TotalStorage Productivity Center V3.3 Update Guide, SG24-7490

Other publications
These publications are also relevant as further information sources:
DS Open Application Programming Interface Reference, GC35-0516
IBM System Storage Productivity Center Introduction and Planning Guide, SC23-8824
IBM System Storage SAN Volume Controller Software Installation and Configuration
Guide for Version 4.2.1, SC23-6628
IBM TotalStorage Productivity Center User’s Guide Version 3 Release 3, GC32-1775

Online resources
These Web sites are also relevant as further information sources:
IBM glossary
http://www.ibm.com/ibm/terminology
SSPC software updates
http://www.ibm.com/systems/support/supportsite.wss/supportresources?brandind=50
00033&familyind=5356448&taskind=1
TPC server sizing Web site
http://www-304.ibm.com/jct01004c/systems/support/storage/software/tpc/

How to get Redbooks
You can search for, view, or download Redbooks, Redpapers, Technotes, draft publications
and Additional materials, as well as order hardcopy Redbooks, at this Web site:
ibm.com/redbooks


Help from IBM
IBM Support and downloads
ibm.com/support

IBM Global Services
ibm.com/services


Index
install 47
A DB2 Host name change 40
Administrator password 32 DB2 install 47
Agent Manager 7–8, 58, 107, 128 DB2 user ID 196
Agent registration password 199 db2admin user ID 47
Data agents 208 DB2ADMNS group 47, 53
Data server registration 206 db2extsec command 41
deploying agents 208 db2start command 41
Fabric agents 208 DB2USERS group 47, 53
HealthChack.bat 204 Device server 8
install 192 discovery function 10
local agent installation 209 Discovery jobs 116
remote agent installation 209 Disk Administrator role 88, 90
WebSphere Application Server connection informa- Disk Administrators group 89
tion 198 DNS server addresses 34
Agent Manager install 192 DNS suffixes 34
Agent Manager password 199 DS8000 CIMOM
Agent Manager services 196 DSCIMCLI utility 121
Agent Registration password 199 enabling 121
AIX server 21 mkuser command 121
antivirus 15 DS8000 Element Manager 165
antivirus software 97 modify 96
assign PAV alias 275 DS8000 Element Manager access 91
DS8000 GUI 2, 21, 227
B Automatic function 232
Basic Edition create Extent Pools 240
install 55 create volume nicknames 274
Brocade Fabric 133 Delete Pools 246
build your own SSPC 19 Download spreadsheet 244
Extent Pool and Rank relation 244
Extent Pool capacity 230, 244
C Extent Pool delete 250
CIM Interop Schema 121 Extent Pool manual create 250
CIMOM 108 increase Extent Pool capacity 258
CIMOM administrative actions 119 rank selection 238
CIMOM agents 8, 116 Real-time manager 230
CIMOM connection status 119 remove Extent Pool capacity 265
CIMOM manual add 120 Rotate Extents 265
Common Information Model 9 Type of configuration menu 260
Computer name field 39 DS8000 GUI access options 6
computer name MANNODE 32 DS8000 GUI Dynamic Volume Expansion 281
create CKD volumes DS8000 management 5
DS8000 GUI DS8000 maximum volume size 270
create CKD volumes 270 DS8000 password considerations 92
create Windows user 87 DS8000 Storage Manager 115, 165
DS8000 volume creation 152
assign ports 153
D zone configuration 162
Data agents 208 zone definition page 163
data collection 116 zoning 154
Data Path Explorer 148, 214 DSCIMCLI utility 121–122
Data server 7 DVE
database instance 108 open system LUN 284
DB2 Dynamic Volume Expansion 281
administrator user ID 51


E L
Element Management,TPC BE GUI Library probes 136
Element Management 115 license
Element Manager 163 TPC capacity 18
associate CIMOM 168 license considerations 16
DS8000 launch 228 license files 188
launching 21 license upgrade 99
Navigation Tree 170 Linux server 21
Element Manager for DS8000 8
Element Managers
launching 169 M
SVC and ESS 169 machine type 2805 2
Enterprise Management 114 MANNODE host name 32
expired DS8000 password 91 messages
Extent Pool HWNEM0104E 92
Pool name 239 minimap 147
server affinity 255 mkdev command 122
External Tools 182 mkuser command 121

F N
Fabric agents 11, 128, 208 NAS device information 11
in-band 108 Navigation Tree
Fabric agents, SSPC expand nodes 115
Fabric agents 8 Topology Viewer 173
fabric management 158 network security 98
Fabric probe jobs 136 Novell NDS tree information 11
firewall considerations 98
fully qualified host name 196 O
Out of Band Fabric agents 9, 131, 134
G
generate PuTTY keys 68 P
Path Planner
H SDD 212
HealthCheck.bat 204 PAV 270, 275
heartbeat 22 performance upgrade kit 17
Host Authentication Password 219 ping job 210
Host Device server Port 219 planning for SSPC 13
host name change 37 plink.exe program 82
probe 220
probe creation 136
I probe job status 140
IBM Passport Advantage 19 Probe jobs 116, 136
IBM V1.4.2 JRE 20, 112 PuTTY 44, 62
initial setup 26 PuTTY installation 63
install DB2 47 PuTTY key generation program 68
IP address, SSPC setup PuTTY private key 68
IP address 34 PuTTY Windows command path 82

J R
Java Web based GUI 46 Redbooks Web site 289
Java Web Start 111 Contact us xi
JVM error 20, 112 redundant SSPC 22
remote agent installation 209
Remove Element Manager option 94
K role-based authorization 84
key concepts 8 rollup report
probe 220
rollup reporting 60, 215


rollup reports Licensing Modes 31
TPC SE product license key information 30
rollup reports 102, 216 Regional Options tab 28
types 102, 216 TCP/IP settings 34
Rotate Extents 265, 272 stop TPC services 41
Rotate Logical Volumes 272 Storage Pool Striping 270
Rotate Logical Volumes Algorithm 272 storage subsystem Element Managers 164
storage subsystem probes 136
Subsystem Device Driver 212
S superuser role 85
SAN Planner 211 supported platforms 19
Volume Planner 211 SVC
scan collection job 210 postinstall.txt document 72
server sizing 19 SVC clusters 44
Service Focal Point dialog 121 connect to Master console 44, 73
Service Location Protocol 10 SVC Console
SLP SA 10 installation 66
SLP UA 10 IP address 44
SMI-S 9, 106 SVC Console customization 62
Software Maintenance 18 SVC Console URL 73
solution assurance review 19 SVC port number 69
SQL1012C error message 40 SVC upgrade 192
SQL1042C error message 37 switch data 132
SSH keys 44 Switch Element Manager 175
SSPC
architecture 6
backup and recovery 104 T
build your own 45 Tape Library
building your own SSPC 19 CIMOM 123
configuration information 14 enable SMI-S Agent 126
console and keyboard 17 SNMP traps 128
deployment 4 Tape Manager 179
DS8000 management 5 Topology Viewer 141
dual configuration 22 create volumes 152
heartbeat 22 Detail level L2 146
host name change 37 DS8000 volume creation 152
initial setup 26 fabric management 158
integrate existing environment 102 Group level L1 144
overview 2 Groups level L0 142
performance upgrade kit 17 Manage Storage Subsystems 151
planning 13 tabular information 146
pre-installed software 3 zone configuration 162
redundant 22 TPC
security considerations 84 Agent Manager 57
software options 18 Asset reports 102
SVC master console 20 Capacity reports 103
TPC Basic Edition code 16 custom installation 57
upgrading 188 Data server account password 60
upgrading to SE 98 Database Asset reports 103
Windows 2003 Enterprise Edition 19 default server port 60
SSPC hardware 4 Device server port 60
SSPC host name 32 Host authentication password 60
SSPC Performance Upgrade Kit 188 password for install 57
SSPC redundancy 22 typical installation 56
SSPC server TPC Basic Edition 3, 16–17
software 6 Agent Manager 7
SSPC server name 30 components 7
SSPC setup Fabric agents 8
licensed by capacity 6
keyboard languages 29 ordering 19
host name in DB2 40 upgrade 3

Index 293

upgrade options 3
TPC BE
architecture 106
CIMOM agents 116
data collection 116
Data server 107
Data Sources 107
DB2 user ID and password 196
Device server 107
External Tools 182
GUI 113
Java Web Start 111
overview 106
upgrading 188
upgrading to SE 188
TPC BE GUI
Content Pane 114
DS8000 Element Storage Manager 115
Enterprise Management 114
Java Web Start 111
Navigation Tree 114
starting 110
TPC command-line interface 109
TPC database 7
TPC GUI 7, 46, 109
TPC license
existing TPC license 19
TPC Limited Edition 4
TPC superuser 60
TPC superuser ID role 88
TSRMsrv1 user account 60

U
upgrade options 98

V
Volume Planner 211

W
WBEM initiative 9
WebSphere
user ID 57
WebSphere Application Server connection 196
Windows Server 2003 Product Key 31
workgroup 35

Z
zone configuration 162
zone definition page 163
Zone Planner 213


IBM System Storage Productivity
Center Deployment Guide
IBM System Storage Productivity Center Deployment Guide
(0.5” spine)
0.475”<->0.873”
250 <-> 459 pages
IBM System Storage Productivity Center Deployment Guide

Back cover ®

IBM System Storage
Productivity Center
Deployment Guide ®

Understand the IBM System Storage Productivity Center (SSPC) is the next step in the
IBM storage strategy. This solution comprises hardware and software, INTERNATIONAL
function and features
combining device configuration capabilities for the IBM System TECHNICAL
of IBM SSPC
Storage DS8000 and IBM System Storage SAN Volume Controller (SVC) SUPPORT
in an easy-to-use hardware console. SSPC extends the manageability ORGANIZATION
Consolidate of these devices with the introduction and integration of IBM
management of IBM TotalStorage Productivity Center Basic Edition V3.3.1. Consolidating
subsystems several hardware and software components on a single tested system
helps support consistent interoperability.
Integrate SSPC in an This IBM Redbooks publication will provide an overview of IBM System BUILDING TECHNICAL
existing TPC Storage Productivity Center (SSPC). It contains the information required INFORMATION BASED ON
to set up your SSPC server by taking you through the initial PRACTICAL EXPERIENCE
environment
customization of the server and then defining and launching Element
Managers through IBM TotalStorage Productivity Center (TPC) Basic IBM Redbooks are developed
Edition. Details on using the functions of TPC BE are provided as well by the IBM International
as upgrading your SSPC server (and TPC BE) to a fully functional TPC
Technical Support
Organization. Experts from
Standard Edition. Managing IBM TotalStorage DS8000 using TPC IBM, Customers and Partners
V3.3.1 is also covered in this book. from around the world create
timely technical information
based on realistic scenarios.
Specific recommendations
are provided to help you
implement IT solutions more
effectively in your
environment.

For more information:
ibm.com/redbooks

SG24-7560-00 ISBN 0738431176

Ibm system storage productivity center deployment guide sg247560

More Related Content

What's hot

Similar to Ibm system storage productivity center deployment guide sg247560

More from Banking at Ho Chi Minh city

Recently uploaded

Ibm system storage productivity center deployment guide sg247560