Ibm system storage productivity center deployment guide sg247560

6,178 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
6,178
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Ibm system storage productivity center deployment guide sg247560

  1. 1. Front coverIBM System StorageProductivity CenterDeployment GuideUnderstand the function and featuresof IBM SSPCConsolidate management of IBMsubsystemsIntegrate SSPC in an existingTPC environment Mary Lovelace Martin Jer Patrick Ji Danijel Paulinibm.com/redbooks
  2. 2. International Technical Support OrganizationIBM System Storage Productivity Center DeploymentGuideJuly 2008 SG24-7560-00
  3. 3. 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 ScheduleContract with IBM Corp.
  4. 4. 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
  5. 5. 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188iv IBM System Storage Productivity Center Deployment Guide
  6. 6. 7.1.2 SVC GUI and CIMOM upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1927.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2087.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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Chapter 8. DS8000 GUI under Element Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2278.1 Launch DS8000 GUI from SSPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2288.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 . . . . . . . . . . . . . . . . . . . . . . . . . 284Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289How to get Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 Contents v
  7. 7. vi IBM System Storage Productivity Center Deployment Guide
  8. 8. NoticesThis 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. Consultyour 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 IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service that doesnot infringe any IBM intellectual property right may be used instead. However, it is the users responsibility toevaluate 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. Thefurnishing of this document does not give you any license to these patents. You can send license inquiries, inwriting, 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 suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer ofexpress 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 madeto the information herein; these changes will be incorporated in new editions of the publication. IBM may makeimprovements and/or changes in the product(s) and/or the program(s) described in this publication at any timewithout notice.Any references in this information to non-IBM Web sites are provided for convenience only and do not in anymanner serve as an endorsement of those Web sites. The materials at those Web sites are not part of thematerials 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 withoutincurring any obligation to you.Information concerning non-IBM products was obtained from the suppliers of those products, their publishedannouncements or other publicly available sources. IBM has not tested those products and cannot confirm theaccuracy of performance, compatibility or any other claims related to non-IBM products. Questions on thecapabilities 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 themas 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 businessenterprise is entirely coincidental.COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating platform for which the sampleprograms 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
  9. 9. TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business MachinesCorporation in the United States, other countries, or both. These and other IBM trademarked terms aremarked on their first occurrence in this information with the appropriate symbol (® or ™), indicating USregistered or common law trademarks owned by IBM at the time this information was published. Suchtrademarks may also be registered or common law trademarks in other countries. A current list of IBMtrademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtmlThe 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 Statesand other countries.Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporation and/orits affiliates.Java, JRE, JVM, Sun, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the UnitedStates, other countries, or both.Microsoft, SQL Server, Windows Server, Windows, and the Windows logo are trademarks of MicrosoftCorporation in the United States, other countries, or both.Intel Xeon, Intel, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarksof 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
  10. 10. 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
  11. 11. 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 Centerx IBM System Storage Productivity Center Deployment Guide
  12. 12. 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.htmlComments 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
  13. 13. xii IBM System Storage Productivity Center Deployment Guide
  14. 14. 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
  15. 15. 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 storage2 IBM System Storage Productivity Center Deployment Guide
  16. 16. 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
  17. 17. 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.4 IBM System Storage Productivity Center Deployment Guide
  18. 18. 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 Edition1.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. Chapter 1. System Storage Productivity Center introduction 5
  19. 19. 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.11.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.6 IBM System Storage Productivity Center Deployment Guide
  20. 20. 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. Chapter 1. System Storage Productivity Center introduction 7
  21. 21. 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.8 IBM System Storage Productivity Center Deployment Guide
  22. 22. 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 StorageNetworking Industry Association (SNIA) in mid-2002 to create and develop a universal, openinterface for managing storage devices, including storage networks. In the SMI-S model, theCIM for storage management is fully adopted and enhanced to standardize the managementinterfaces so that management applications can provide cross device management.The TPC design follows the SMI-S architecture. Figure 1-3 shows how the CIMOM agentworks 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 DevicesFigure 1-3 SMI-S architecture for TPCIn the SSPC environment, the CIMOM agent or the SVC clusters is integrated into SSPC. TheCIMOM agents of DS8000 are embedded into DS8000 HMC consoles. Therefore, in theSSPC environment, there is no extra CIMOM hardware required for SVC and DS8000.Out of Band Fabric agentsThe function of Out of Band Fabric agent is to collect storage fabric information through aTCP/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 SNMPagent is a piece of software running on an SNMP-capable network component. It responds tothe SNMP requests from an SNMP manager and provides the management functionalitydefined in the subsystem. An SNMP manager manages the SNMP agents on behalf of anadministrator.In the Out of Band Fibre Agents implementation, TPC functions as an SNMP manager andmanages the SNMP agent in each Fabric device. Chapter 1. System Storage Productivity Center introduction 9
  23. 23. 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.10 IBM System Storage Productivity Center Deployment Guide
  24. 24. 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 ServerFigure 1-5 Agent Manager overviewAgent Manager is the central component managing agents deployed in the environment. Itmaintains 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 managingSubagent 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 upgradeyour 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 connectivitiesthrough HBAs into the SAN fabrics that you want to manage and monitor. The Fabric agentscollect fabric topology information, port state information, and zoning information. The Fabricagents can also identify other SAN-attached devices if they are in the same zone. Usingoperating system calls, the agents also collect information about the machine on which theyare 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 informationneeded from computer systems. Data agents can also gather information about databasemanagers installed on the servers, Novell® NDS tree information, and NAS deviceinformation. Data agents are typically installed on all servers in the SAN that you want tocollect information from. This is because each server has a unique set of files and filesystems that TPC cannot track without an agent. Chapter 1. System Storage Productivity Center introduction 11
  25. 25. 12 IBM System Storage Productivity Center Deployment Guide
  26. 26. 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.© Copyright IBM Corp. 2008. All rights reserved. 13
  27. 27. 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: ____.____.____.____14 IBM System Storage Productivity Center Deployment Guide
  28. 28. 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.com7. 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 DS8000 System Name/ Host Name IP address: SVC __________________ ____.____.____.____ Other DS8000 System Name/ Host Name IP address: SVC __________________ ____.____.____.____ Other DS8000 System Name/ Host Name IP address: SVC __________________ ___.____.____.____ Other DS8000 System Name/ Host Name IP address: SVC __________________ ____.____.____.____ Other DS8000 System Name/ Host Name IP address: SVC __________________ ____.____.____.____ Other8. 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
  29. 29. 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.16 IBM System Storage Productivity Center Deployment Guide
  30. 30. Figure 2-1 SSPC server, 2805-MC2The hardware of the SSPC server is a Machine Type 2805-MC2. It is an IBM System x x35501U high rack-mounted server. It has one Quad-Core Intel Xeon® Processor E5310 (1.60 GHz8 MB L2 1066 MHz 80 W), 4 GB of memory, two 3.5" hard disk drives of 146 GB 15K rpmSAS HDD in a RAID 1, optical drive CD-ROM, and dual integrated 10/100/1000 MbpsEthernet.This hardware configuration is sized for the TPC Basic Edition. TPC Basic Edition is TPC forDisk without the Disk performance function and TPC for Fabric. TPC Basic Edition does notinclude TPC Data and there is no Agent Manager.Performance Upgrade KitThere is a Performance Upgrade Kit (Feature Code 1800) for the 2805-MC2. ThisPerformance Upgrade Kit doubles the CPU and RAM of the server. The SSPC server withfeature code 1800 will have two Quad-Core Intel Xeon Processors and 8 GB of memory. Youneed to purchase the Performance Upgrade Feature if you plan to upgrade your SSPC toTPC Standard Edition or install TPC for Replication on the SSPC server. TPC StandardEdition consists of TPC for Disk, TPC for Fabric, TPC for Data, and Agent Manager. TPC forReplication helps you manage the advanced copy services provided by IBM ESS model 800,IBM DS8000, IBM DS6000™, and IBM SVC. The Performance Upgrade Feature providesmore system resources for the additional workload.Optional console and keyboardThere is also a Console Keyboard/Display/Drawer (feature code 9100) for the SSPC. Youneed 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 9100Figure 2-2 2805-MC2 hardware features Chapter 2. Planning for SSPC install 17
  31. 31. 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 TotalStorage Productivity Center Basic Edition V3.3.1 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 dashboard2.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.18 IBM System Storage Productivity Center Deployment Guide
  32. 32. 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 Chapter 2. Planning for SSPC install 19
  33. 33. 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 message2.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.20 IBM System Storage Productivity Center Deployment Guide
  34. 34. 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 Chapter 2. Planning for SSPC install 21
  35. 35. 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.22 IBM System Storage Productivity Center Deployment Guide
  36. 36. If one SSPC stops working, you can go to the second SSPC and manage your systems fromthere. This is equivalent to having have two remote controllers for your television. If oneremote controller stops working, you may simply use the other remote controller. SSPC SSPC LAN SVC Cluster DS8000 Internal HMCFigure 2-7 Dual SSPC configuration Chapter 2. Planning for SSPC install 23
  37. 37. 24 IBM System Storage Productivity Center Deployment Guide
  38. 38. 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.© Copyright IBM Corp. 2008. All rights reserved. 25
  39. 39. 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.26 IBM System Storage Productivity Center Deployment Guide
  40. 40. Figure 3-2 License AgreementThe next window is the Regional and Language options, as shown in Figure 3-3. CheckCustomize to update the Regional and Language Options.Figure 3-3 Regional and Language Options Chapter 3. SSPC initial setup 27
  41. 41. 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.28 IBM System Storage Productivity Center Deployment Guide
  42. 42. Figure 3-5 Language tabIn the Text Services and Input Languages window, select the language for the SSPC from thedrop-down menu. In the Installed services window, select the keyboard languages for theSSPC, as shown in Figure 3-6.Figure 3-6 Text Services and Input Languages Chapter 3. SSPC initial setup 29
  43. 43. 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.30 IBM System Storage Productivity Center Deployment Guide
  44. 44. The Windows Server 2003 Product Key is listed on a sticker labeled Windows SVR Ent 2003located on the outside of the top cover of the SSPC. It was recorded in 2.1, “Collectingconfiguration information” on page 14. Enter this value now and click Next to continue.Figure 3-9 Product License Key windowThe next window is the Licensing Modes window, as shown in Figure 3-10. We accepted thedefaults and click Next to continue. For detailed information, refer to the Microsoft Web site onLicensing Overview for Windows Server 2003:http://www.microsoft.com/windowsserver2003/howtobuy/licensing/overview.mspxFigure 3-10 Licensing Modes Chapter 3. SSPC initial setup 31
  45. 45. 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 Password32 IBM System Storage Productivity Center Deployment Guide
  46. 46. 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 SettingsThe next steps are to set up the network. You need the information in Table 2-3 on page 14 toset up the IP address, net mask, default gateway, and DNS of the SSPC server. In theNetworking Settings window shown in Figure 3-14, select the Custom settings button andclick Next to continue.Figure 3-14 Network Settings Chapter 3. SSPC initial setup 33
  47. 47. 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 DNS34 IBM System Storage Productivity Center Deployment Guide

×