• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Ibm total storage productivity center v3.1 the next generation sg247194
 

Ibm total storage productivity center v3.1 the next generation sg247194

on

  • 741 views

 

Statistics

Views

Total Views
741
Views on SlideShare
741
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Ibm total storage productivity center v3.1 the next generation sg247194 Ibm total storage productivity center v3.1 the next generation sg247194 Document Transcript

    • Front coverIBM TotalStorageProductivity Center:The Next GenerationEffectively use the IBM TotalStorageProductivity CenterEfficiently manage your storagesubsystems using one interfaceEasily customize reports foryour environment Mary Lovelace Tom Conway Werner Eggli Marta Greselin Hartmut Harder Stefan Lein Massimo Mastrorilliibm.com/redbooks
    • International Technical Support OrganizationIBM TotalStorage Productivity Center: The NextGenerationSeptember 2006 SG24-7194-00
    • Note: Before using this information and the product it supports, read the information in “Notices” on page xi.First Edition (September 2006)This edition applies to Version 3, Release 1, of IBM TotalStorage Productivity Center (product number5608-VC0).© Copyright International Business Machines Corporation 2006. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corp.
    • Contents Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii The team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi Chapter 1. Introduction to IBM TotalStorage Productivity Center . . . . . . . . . . . . . . . . . 1 1.1 What is IBM TotalStorage Productivity Center? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1.1 TotalStorage Productivity Center structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1.2 IBM TotalStorage Productivity Center components . . . . . . . . . . . . . . . . . . . . . . . . 5 1.2 What is new in IBM TotalStorage Productivity Center V3.1 . . . . . . . . . . . . . . . . . . . . . . 8 1.2.1 Changes between TPC V3.1 and V2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.3 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.3.1 IBM TotalStorage Productivity Center Limited Edition . . . . . . . . . . . . . . . . . . . . . 11 1.3.2 IBM TotalStorage Productivity Center Standard Edition . . . . . . . . . . . . . . . . . . . . 12 1.3.3 IBM TotalStorage Productivity Center for Replication. . . . . . . . . . . . . . . . . . . . . . 12 Chapter 2. Key concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.1 Standards used in IBM TotalStorage Productivity Center . . . . . . . . . . . . . . . . . . . . . . . 14 2.1.1 ANSI standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.1.2 Web-Based Enterprise Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.1.3 Storage Networking Industry Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.1.4 Simple Network Management Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.1.5 Fibre Alliance MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.2 Service Location Protocol overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.2.1 SLP architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.2.2 SLP communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 2.2.3 Configuration recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 2.3 Common Information Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 2.4 Component interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 2.4.1 CIMOM discovery with SLP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 2.4.2 How CIM Agent works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.5 Tivoli Common Agent Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 2.5.1 Tivoli Agent Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.5.2 Common Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 2.6 Communication in TotalStorage Productivity Center. . . . . . . . . . . . . . . . . . . . . . . . . . . 35 2.7 IBM TotalStorage Productivity Center basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2.7.1 Collecting data in general . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 2.7.2 Role-based Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Chapter 3. Installation planning and considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . 43 3.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 3.2 Installation prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 3.2.1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 3.2.2 Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 3.3 Preinstallation check list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 3.3.1 TCP/IP ports used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46© Copyright IBM Corp. 2006. All rights reserved. iii
    • 3.4 User IDs and security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 3.4.1 User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 3.4.2 Increasing user security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 3.4.3 Certificates and key files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 3.4.4 Services and service accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 3.5 Starting and stopping the managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 3.6 Server recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 3.7 Supported subsystems, devices, filesystems, databases . . . . . . . . . . . . . . . . . . . . . . . 53 3.7.1 Storage subsystem support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 3.7.2 Tape library support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 3.7.3 File system support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 3.7.4 Network File System support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 3.7.5 Database support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 3.8 Security considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Chapter 4. TotalStorage Productivity Center installation on Windows 2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 4.1 TotalStorage Productivity Center installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 4.1.1 Typical installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 4.1.2 Custom installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 4.1.3 CD layout and components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 4.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 4.2.1 One-server environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 4.2.2 Two-server environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 4.3 Hardware prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 4.3.1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 4.3.2 Disk space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 4.4 Software prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 4.4.1 Databases supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 4.5 Preinstallation steps for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 4.5.1 Verify primary domain name systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 4.5.2 Activate NetBIOS settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 4.5.3 Internet Information Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 4.5.4 Create Windows user ID to install Device server and Data server . . . . . . . . . . . . 65 4.5.5 User IDs and password to be used and defined . . . . . . . . . . . . . . . . . . . . . . . . . . 66 4.6 DB2 install for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 4.6.1 Agent Manager installation for Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 4.7 Install TotalStorage Productivity Center components . . . . . . . . . . . . . . . . . . . . . . . . . . 94 4.7.1 Verifying installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 4.7.2 Installing Data and Device Servers, GUI, and CLI . . . . . . . . . . . . . . . . . . . . . . . 100 4.8 Configuring the GUI for Web Access under Windows 2003 . . . . . . . . . . . . . . . . . . . . 107 4.8.1 Installing Internet Information Services (IIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 4.8.2 Configuring IIS for the TotalStorage Productivity Center GUI. . . . . . . . . . . . . . . 110 4.8.3 Launch the TotalStorage Productivity Center GUI . . . . . . . . . . . . . . . . . . . . . . . 113 Chapter 5. TotalStorage Productivity Center installation on AIX . . . . . . . . . . . . . . . . 117 5.1 TotalStorage Productivity Center installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 5.1.1 Typical installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 5.1.2 Custom installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 5.1.3 CD layout and components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 5.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 5.3 Hardware Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 5.4 Software Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 5.4.1 Databases supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122iv IBM TotalStorage Productivity Center: The Next Generation
    • 5.5 Preinstallation steps for AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 5.5.1 Verify primary domain name servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 5.5.2 User IDs, passwords, and groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 5.5.3 Create the TotalStorage Productivity Center user ID and group. . . . . . . . . . . . . 124 5.5.4 Creating and sizing file systems and logical volumes . . . . . . . . . . . . . . . . . . . . . 125 5.5.5 Verify port availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1255.6 DB2 installation for AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 5.6.1 Accessing the installation media with CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 5.6.2 Accessing the installation media with a downloaded image . . . . . . . . . . . . . . . . 127 5.6.3 Preparing the display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 5.6.4 Beginning the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 5.6.5 Verifying the DB2 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 5.6.6 Removing the CD from the server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1435.7 Installing the DB2 fix pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 5.7.1 Obtaining and installing the latest DB2 fix pack . . . . . . . . . . . . . . . . . . . . . . . . . 143 5.7.2 Add the root user to the DB2 instance group . . . . . . . . . . . . . . . . . . . . . . . . . . . 1455.8 Agent Manager installation for AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 5.8.1 Accessing the installation media using CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 5.8.2 Accessing the installation media using a downloaded image . . . . . . . . . . . . . . . 146 5.8.3 Preparing the display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 5.8.4 Beginning the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 5.8.5 Removing the CD from the server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1575.9 Installing IBM TotalStorage Productivity Center for AIX . . . . . . . . . . . . . . . . . . . . . . . 157 5.9.1 Order of component installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 5.9.2 Accessing the installation media with a CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 5.9.3 Accessing the installation media with a downloaded image . . . . . . . . . . . . . . . . 158 5.9.4 Preparing the display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 5.9.5 Sourcing the environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 5.9.6 Assigning file system ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 5.9.7 Installing the database schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 5.9.8 Installing Data server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 5.9.9 Installing Device server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 5.9.10 Installing agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 5.9.11 Installing the Java Graphical User and the Command Line Interface . . . . . . . . 1825.10 Installing the user interface for access with a Web browser . . . . . . . . . . . . . . . . . . . 186 5.10.1 Distributing the Graphical User Interface with a Web browser . . . . . . . . . . . . . 187Chapter 6. Agent deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1956.1 Functional overview: Which agents do I need?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 6.1.1 Types of agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 6.1.2 TotalStorage Productivity Center component use of agents. . . . . . . . . . . . . . . . 1976.2 Agent infrastructure overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2006.3 Agent deployment options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 6.3.1 Local installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 6.3.2 Remote installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2026.4 Local installation of Data and Fabric Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 6.4.1 Interactive installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 6.4.2 Unattended (silent) installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2106.5 Remote installation of Data and Fabric Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 6.5.1 Preparing the remote installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 6.5.2 Performing the remote installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2146.6 Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 6.6.1 Logfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Contents v
    • 6.7 Uninstalling Data and Fabric Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 6.7.1 Remote uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 6.7.2 Local uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 6.8 Upgrading the Data Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Chapter 7. CIMOM installation and customization. . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 7.2 Planning considerations for CIMOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 7.2.1 CIMOM configuration recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 7.3 SNIA certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 7.4 Installing CIM Agent for ESS 800/DS6000/DS8000 . . . . . . . . . . . . . . . . . . . . . . . . . . 242 7.4.1 CIM Agent and LIC level relationship for DS8000. . . . . . . . . . . . . . . . . . . . . . . . 243 7.4.2 CIM Agent and LIC level relationship for DS6000. . . . . . . . . . . . . . . . . . . . . . . . 244 7.4.3 ESS CLI Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 7.4.4 DS CIM Agent install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 7.4.5 Post-installation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 7.4.6 Configuring the DS CIM Agent for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 7.4.7 Restart the CIMOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 7.4.8 CIMOM user authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 7.5 Verifying connection to the storage subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 7.5.1 Adding your CIMOM to the TotalStorage Productivity Center GUI . . . . . . . . . . . 269 7.5.2 Problem determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 7.5.3 Confirming that ESS CIMOM is available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 7.5.4 Start the CIM Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 7.6 Installing CIM agent for IBM DS4000 family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 7.6.1 Registering DS4000 CIM agent if SLP-DA is in place. . . . . . . . . . . . . . . . . . . . . 281 7.6.2 Verifying and managing CIMOM availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 7.7 Configuring CIMOM for SAN Volume Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 7.7.1 Adding the SVC TotalStorage Productivity Center for Disk user account. . . . . . 286 7.7.2 Registering the SAN Volume Controller host in SLP . . . . . . . . . . . . . . . . . . . . . 292 7.8 Configuring CIMOM for McData switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 7.8.1 Planning the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 7.8.2 Supported configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 7.8.3 Installing SMI-S Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 7.8.4 Configuring the SMI-S interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 7.8.5 Verifying the connection with TPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 7.9 Configuring the CIM Agent for Brocade Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 7.9.1 Planning the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 7.9.2 Installing the CIM Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 7.9.3 SLP installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 7.9.4 Changing the ports used in the CIM Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 7.9.5 Connecting the CIM Agent with TPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 7.10 Configuring the CIM Agent for Cisco switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 7.10.1 Enabling and configuring the CIM Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 7.10.2 Connecting the CIM Agent with TPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 7.11 Configuring the CIM Agent for IBM Tape Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . 318 7.11.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 7.11.2 SMI-S Agent for Tape Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 7.11.3 Configuring the SMI-S Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 7.12 Discovering endpoint devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 7.13 Verifying and managing CIMOMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 7.14 Interoperability namespace summary table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 7.15 Planning considerations for SLP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331vi IBM TotalStorage Productivity Center: The Next Generation
    • 7.15.1 Considerations for using SLP DA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 7.15.2 SLP configuration recommendation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 7.15.3 General performance guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3327.16 CIMOM registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 7.16.1 Manual method to add a CIMOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 7.16.2 Automated method to add CIMOMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 7.16.3 Configuring TotalStorage Productivity Center for SLP discovery . . . . . . . . . . . 335 7.16.4 Registering the CIM Agent to SLP-DA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 7.16.5 Creating slp.reg file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336Chapter 8. Getting Started with TotalStorage Productivity Center. . . . . . . . . . . . . . . 3398.1 Infrastructure summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3408.2 TotalStorage Productivity Center function overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3418.3 First steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 8.3.1 Starting the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 8.3.2 Logging on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343 8.3.3 GUI basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3438.4 Initial configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 8.4.1 Configuring CIMOMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 8.4.2 Verifying Data and Fabric Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 8.4.3 Configuring out-of-band fabric connectivity (SNMP/API) . . . . . . . . . . . . . . . . . . 3588.5 Collecting data about your infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 8.5.1 Creating Probes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 8.5.2 Creating Scans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 8.5.3 Creating Pings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 8.5.4 Creating Performance Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3708.6 Retrieving and displaying data about your Infrastructure . . . . . . . . . . . . . . . . . . . . . . 376 8.6.1 Viewing data about your storage subsystems. . . . . . . . . . . . . . . . . . . . . . . . . . . 376 8.6.2 Viewing data about your fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3868.7 Viewing data about your tape libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 8.7.1 Viewing data about your computers and file systems . . . . . . . . . . . . . . . . . . . . . 3938.8 Alerting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3988.9 Configuring your storage subsystems and switches . . . . . . . . . . . . . . . . . . . . . . . . . . 409Chapter 9. Topology viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4159.1 Design principles and concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 9.1.1 Progressive information disclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 9.1.2 Semantic Zooming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 9.1.3 Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 9.1.4 Information Overlays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422 9.1.5 Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 9.1.6 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424 9.1.7 Status propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425 9.1.8 Hovering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 9.1.9 Pinning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430 9.1.10 Zone and zonesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431 9.1.11 Removing entities from the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 9.1.12 Refreshing the Topology Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4339.2 Getting started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 9.2.1 Launch the Topology Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 9.2.2 Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 9.2.3 Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 9.2.4 Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 Contents vii
    • 9.2.5 Storage Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445 9.3 Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 9.4 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 Chapter 10. Managing and monitoring your storage subsystem . . . . . . . . . . . . . . . . 453 10.1 Case study 1: adding new servers and storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 10.1.1 Server tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 10.1.2 Storage provisioning and zoning on Colorado . . . . . . . . . . . . . . . . . . . . . . . . . 459 10.1.3 Storage Provisioning and Zoning on AZOV ( 002-AZOV ) . . . . . . . . . . . . . . . . 465 10.1.4 Post activities for Colorado and AZOV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470 10.1.5 Manual zone configuration with TPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 10.2 Case Study 2: Detect and alert unwanted files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481 10.2.1 Prerequisite steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481 10.2.2 Create a Scan targeted to the specific filesystem . . . . . . . . . . . . . . . . . . . . . . . 483 10.2.3 Create a customized report for the scan-results . . . . . . . . . . . . . . . . . . . . . . . . 487 10.2.4 Set up the constraint definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 10.2.5 Rescan the filesystem to see if there is a violation . . . . . . . . . . . . . . . . . . . . . . 494 10.2.6 Activate Archive/Delete Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498 10.3 Case Study 3: Policy management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499 10.3.1 The steps to perform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500 10.3.2 Create a Scan and a Report targeted to a specific filesystem . . . . . . . . . . . . . 503 10.3.3 Define an alert for a filesystem threshold condition (optional) . . . . . . . . . . . . . 506 Chapter 11. Hints, tips and good to knows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509 11.1 Selecting an SMS or DMS tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510 11.2 DB2 installation known issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 11.3 How to get rid of Engenio provider 5989 port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 11.4 DB2 view for CIMOM discovered each subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . 511 11.5 Valid characters for user ID and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 11.5.1 Typical installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512 11.5.2 Custom installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512 11.6 How to change timeout value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 11.7 Common Agent and Agent Manager documentation . . . . . . . . . . . . . . . . . . . . . . . . 513 11.7.1 For an installed Common Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 11.7.2 For an installed Agent Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 11.7.3 Scripts to clean up TPC V3.1 component or complete install . . . . . . . . . . . . . . 513 11.8 SLP configuration recommendation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514 11.8.1 SLP registration and slptool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 11.9 Tivoli Common Agent Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 11.9.1 Locations of configured user IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 11.9.2 Tivoli Agent Manager status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 11.10 Verifying if a port is in use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518 Appendix A. Worksheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519 User IDs and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520 Server information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520 User IDs and passwords for key files and installation. . . . . . . . . . . . . . . . . . . . . . . . . . 521 Storage device information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521 IBM TotalStorage Enterprise Storage Server, DS6000, DS8000 . . . . . . . . . . . . . . . . . 522 IBM DS4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523 IBM SAN Volume Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525viii IBM TotalStorage Productivity Center: The Next Generation
    • Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527 Contents ix
    • x IBM TotalStorage Productivity Center: The Next Generation
    • 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. Anyreference 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 notinfringe 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 such provisions areinconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "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 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 without incurringany 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 illustrates 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. You may copy, modify, anddistribute these sample programs in any form without payment to IBM for the purposes of developing, using,marketing, or distributing application programs conforming to IBMs application programming interfaces.© Copyright IBM Corp. 2006. All rights reserved. xi
    • TrademarksThe following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both: AIX 5L™ FlashCopy® System Storage™ AIX® ibm.com® Tivoli Enterprise Console® Cloudscape™ IBM® Tivoli Enterprise™ DB2 Universal Database™ iSeries™ Tivoli® DB2® NetView® TotalStorage® DS4000™ Power PC® WebSphere® DS6000™ POWER4™ xSeries® DS8000™ POWER5™ z/OS® Enterprise Storage Server® pSeries® zSeries® ESCON® Redbooks (logo) ™ eServer™ Redbooks™The following terms are trademarks of other companies:Java, JDBC, JDK, JRE, JVM, Solaris, Sun, Sun Microsystems, and all Java-based trademarks are trademarks of SunMicrosystems, Inc. in the United States, other countries, or both.Active Directory, Internet Explorer, Microsoft, Windows Server, Windows, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.Intel, Pentium, Xeon, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of IntelCorporation 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.xii IBM TotalStorage Productivity Center: The Next Generation
    • Preface IBM TotalStorage® Productivity Center is a suite of infrastructure management software that can centralize, automate, and simplify the management of complex and heterogeneous storage environments. It can help reduce the effort of managing complex storage infrastructures, improve storage capacity utilization, and improve administration efficiency. IBM TotalStorage Productivity Center allows you to respond to on demand storage needs and brings together, in a single point, the management of storage devices, fabric, and data. TotalStorage Productivity Center V3.1 is a rewrite of previous versions. This IBM Redbook shows you how to access the functions as compared to the previous releases. This IBM Redbook is intended for administrators and users who are installing and using IBM TotalStorage Productivity Center. It provides an overview of the product components and functions. It describes the hardware and software environment required and provides a step- by-step installation procedure. Customization and usage hints and tips are also provided. This book is not a replacement for existing IBM Redbooks™ or product manuals that detail the implementation and configuration of individual products that make up the IBM TotalStorage Productivity Center, or the products as they may have been called in previous versions. We refer to those books as appropriate throughout this book.The team that wrote this redbook This redbook was produced by specialists from around the world working at the International Technical Support Organization (ITSO), San Jose Center. The book was completed in two phases. The team pictures are shown in on this page and on page xiv. From left to right: Massimo, Marta, Tom , and Mary© Copyright IBM Corp. 2006. All rights reserved. xiii
    • From left to right: Hartmut, Stefan, and Werner 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 many redbooks on TotalStorage Productivity Center and z/OS® storage products. Tom Conway is an Infrastructure Architect in the United States of America. He has 16 years of experience in the Open Systems Infrastructure field. He joined IBM in 2001 and became the Chief Engineer of the IBM Global Services SAN Interoperability Lab at the IBM National Test Center in Gaithersburg, Maryland. His areas of expertise include Open Systems server hardware, operating systems, networking, and storage hardware and software, including the IBM TotalStorage Productivity Center. He is an IBM Certified Professional Server Expert. Werner Eggli is a Senior IT Specialist with IBM Switzerland. He has more than 20 years experience in Software Development, Project Managment and Consulting concentrating in the Telecommunication Segment. Werner joined IBM in 2001 and works in presales as a Storage SE for Open Systems. His expertise is the design and implementation of IBM Storage Solutions (ESS/FAStT/LTO/NAS/SAN/SVC). He holds a degree in Dipl.Informatiker (FH) from Fachhochschule Konstanz, Germany. Marta Greselin is an IT specialist working for IBM Software Group in Italy. She joint IBM in 1999. Her role is Technical Sales Support in Tivoli®. She has seven years of experience in selling and implementing Proof of Concept scenarios for Storage Management software solutions both in Tivoli and TotalStorage Open Software. She holds a degree in Physics from Università Statale di Milano. Her area of expertise include IBM Tivoli Storage Manager, IBM TotalStorage Productivity Center, IBM TotalStorage SAN Volume Controller, IBM TotalStorage SAN File System. Hartmut Harder is an IT Specialist based in Karlsruhe, Germany. Before joining IBM in 1985 he ompleted his education as a certified engineer of electronics. He started with IBM ITS Delivery as a Hardware Specialist for Large System customers. In his more than 20 years of IT experience, he has been working two thirds of this time in several areas of Systems Management software products like Tivoli Framework,Tivoli Monitoring,Software Distributionxiv IBM TotalStorage Productivity Center: The Next Generation
    • with NetView® DM/2. For the last six years he has focussed on storage related products likeTivoli Storage Manager. His working knowledge is gained from supporting customers withplanning,implementing and supporting IBM Storage Management Solutions.Stefan Lein is a Consulting IT Specialist working for Field Technical Sales Support in the IBMStorage Sales Organization in Germany. He joined IBM in 1993 and has worked in severalsales and technical roles. He has five years of experience experience providing presales andpostsales support for IBM TotalStorage solutions for open systems. His areas of specialexpertise include IBM Disk Systems and the IBM Storage Software solution portfolio. Stefanis a certified IBM Certified Specialist for TotalStorage Networking and VirtualizationArchitecture and for Open Systems Storage Solutions. He holds a degree in ComputerScience of the University of Applied Science in Nürnberg Germany and a degree ineconomical engineering of the University of Applied Science in Würzburg/Schweinfurt,Germany.Massimo Mastrorilli is an Advisory IT Storage Specialist in Switzerland. He joined IBM Italyin 1989 and seven years ago he moved to IBM Switzerland, based in Lugano. He has 16years of experience in implementing, designing, and supporting Storage solutions in S390and Open Systems environment. His areas of expertise include IBM Tivoli Storage Manager,SAN Storage Area Network, and Storage solutions for Open Systems. He is an IBM CertifiedSpecialist for TSM, Storage Sales and Open System Storage™ Solutions. He is a member ofTivoli GRT Global Response Team group.Thanks to the following people for their contributions to this project:Robert HaimowitzSangam RacherlaInternational Technical Support OrganizationDiana DuanDoug DunhamPaul LeeCurtis NealJeanne OstdiekScott VenutiSan Jose, CaliforniaIBM USARuss WarrenStorage Software Project ManagementResearch Triangle Park, North CarolinaIBM USAMike GrieseTechnical Support MarketingRochester, MinnisotaIBM USADerek JacksonAdvanced Technical SupportGaithersburg, MarylandIBM USA Preface xv
    • Tina Dunton Nancy Hobbs Sudhir Koka Bryant Lee Arvind Surve Bill Tuminaro Miki Walters TotalStorage Productivity Center Development San Jose, California IBM USA Eric Butler Andreas Dieberger Roberto Pineiro Ramani Routray IBM Research San Jose, California IBM USABecome a published author Join us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. Youll team with IBM technical professionals, Business Partners and/or customers. Your efforts will help increase product acceptance and customer satisfaction. As a bonus, youll 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 Redbooks to be as helpful as possible. Send us your comments about this or other Redbooks in one of the following ways: Use the online Contact us review redbook form found at: ibm.com/redbooks Send your comments in an email to: redbook@us.ibm.com Mail your comments to: IBM® Corporation, International Technical Support Organization Dept. HYTD Mail Station P099 2455 South Road Poughkeepsie, NY 12601-5400xvi IBM TotalStorage Productivity Center: The Next Generation
    • 1 Chapter 1. Introduction to IBM TotalStorage Productivity Center IBM TotalStorage Productivity Center is a storage management solution that can help you reduce the effort required to manage complex storage infrastructures and improve storage utilization and administration efficiency. This solution allows you to respond to on demand storage needs and brings together, in a single point, the management of storage devices, fabric, and data. In this chapter, we provide an overview of IBM TotalStorage Productivity Center V3.1.© Copyright IBM Corp. 2006. All rights reserved. 1
    • 1.1 What is IBM TotalStorage Productivity Center? IBM TotalStorage Productivity Center is an integrated set of software components that provides end-to-end storage management, from the host and application to the target storage device in a heterogeneous platform environment. This software offering provides disk and tape library configuration and management, performance management, SAN fabric management and configuration, and host-centered usage reporting and monitoring from the perspective of the database application or file system. IBM TotalStorage Productivity Center: Simplifies the management of storage infrastructures. Manages, configures, and provisions SAN-attached storage. Monitors and tracks performance of SAN-attached devices. Monitors, manages, and controls (through zones) SAN fabric components. Manages the capacity utilization and availability of file systems and databases. TotalStorage Productivity Center V3.1 is an integrated storage infrastructure management solution that simplifies, automates and optimizes the management of storage devices, storage networks and capacity utilization of file systems and databases. It helps you manage the capacity utilization of file systems and databases and automate file system capacity provisioning, perform device configuration and management of multiple devices from a single user interface, tune and proactively manage the performance of storage devices on the SAN and manage, monitor and control your SAN fabric. TotalStorage Productivity Center V3.1 provides a single management platform that allows you to centralize how you manage your storage infrastructure. By providing an integrated suite with management modules focused on various aspects of the storage infrastructure, TotalStorage Productivity Center delivers the capability to do role based administration, single sign-on and a single management server and repository. The central console provides a centralized place to monitor, plan, configure, report and do problem determination on the SAN fabric, storage arrays and storage capacity.1.1.1 TotalStorage Productivity Center structure In this section, we look at the TotalStorage Productivity Center structure from the logical and physical view. Logical Structure The logical structure of TotalStorage Productivity Center V3.1 has three layers, as shown in Figure 1-1 on page 3. The infrastructure layer consists of basic function such as messaging, scheduling, logging, device discovery, and a consolidated database shared by all components of TotalStorage Productivity to ensure consistent operation and performance. The application layer consists of core TotalStorage Productivity Center management functions, based on the infrastructure implementation, that provide different disciplines of storage or data management. These application components are most often associated with the product components that make up the product suite, such as fabric management, disk management, replication management and data management. The interface layer presents integration points for the products that make up the suite. The integrated graphical user interface (GUI) brings together product and component functions into a single representation that seamlessly interacts with the components to centralize the tasks for planning, monitoring, configuring, reporting, topology viewing, and problem resolving.2 IBM TotalStorage Productivity Center: The Next Generation
    • Interfaces Automated Integrated Best User Practices Interface Provisioning / Workflow WSDL CL Management Fabric Disk Replication Performance Data Others … Applications Fabric Disk Replication Performance Data Others … Scheduling, Device Discovery Scheduling, Device Discovery Consolidated Database Messages Infrastructure And Control Consolidated Database Messages And Control Logging C Logging l C Control Monitor Discovery a l Interface Interface Interface C s a l s C s a M Control Discover API l s Proc ess Proc ess s a a M Proc ess Translator Job Engine s p Queue Queue Queue Queue s a Monitor CIMSc anner SLPSc annerSLPPars er CIMPars er M p s p Copy CIMObj ect Pars er CIMXMLParser a e Legend CIMProc ess or M p p r Infr astr ucture Services Domai n s pecific Plug-ins a DB e Profil e (eCS) Driver p p r CIM e ESSNI Agent SNMP p Client r Library Library Library e Library r …Figure 1-1 TotalStorage Productivity Center V3.1 logical structurePhysical structureIBM TotalStorage Productivity Center is comprised of the following elements: A data component IBM TotalStorage Productivity Center for Data (formerly IBM Tivoli Storage Resource Manager) A fabric component IBM TotalStorage Productivity Center for Fabric (formerly IBM Tivoli SAN Manager) A disk component IBM TotalStorage Productivity Center for Disk (formerly IBM TotalStorage Multiple Device Manager) A replication component (formerly IBM TotalStorage Multiple Device Manager Replication Manager)IBM TotalStorage Productivity Center includes a centralized suite installer and IBMTotalStorage Productivity Center for Data and IBM TotalStorage Productivity Center forFabric share a common agent to manage the fabric as well as capacity utilization of filesystems and databases. Figure 1-2 on page 4 shows the TotalStorage Productivity CenterV3.1 physical structure. Chapter 1. Introduction to IBM TotalStorage Productivity Center 3
    • T PC D atabase Figure 1-2 TotalStorage Productivity Center structure The Data server is the control point for product scheduling functions, configuration, event information, reporting, and GUI support. It coordinates communication with agents and data collection from agents that scan file systems and databases to gather storage demographics and populate the database with results. Automated actions can be defined to perform file system extension, data deletion, and Tivoli Storage Manager backup or archiving or event reporting when defined thresholds are encountered. The Data server is the primary contact point for GUI user interface functions. It also includes functions that schedule data collection and discovery for the Device server. The Device server component discovers, gathers information from, analyzes performance of, and controls storage subsystems and SAN fabrics. It coordinates communication with agents and data collection from agents that scan SAN fabrics. The single database instance serves as the repository for all TotalStorage Productivity Center components. The Data agents and Fabric agents gather host, application, and SAN fabric information and send this information to the Data server or Device server. The GUI allows you to enter information or receive information for all TotalStorage Productivity Center components. The command-line-interface (CLI) allows you to issue commands for major TotalStorage Productivity Center functions.4 IBM TotalStorage Productivity Center: The Next Generation
    • 1.1.2 IBM TotalStorage Productivity Center components In this section we provide more details onthe components that make up the TotalStorage Productivity Center. IBM TotalStorage Productivity Center for Data IBM TotalStorage Productivity Center for Data is designed to provide a comprehensive storage resource management (SRM) solution for heterogeneous storage environments across the enterprise. It includes enterprise-wide reporting and monitoring, policy-based management, and automated capacity provisioning for direct attached storage (DAS), network attached storage (NAS), and storage area network (SAN) environments. TotalStorage Productivity Center for Data enables administrators to identify, manage, control, and predict storage usage. It also provides file system and database management, reporting on storage capacity and growth. TotalStorage Productivity Center for Data provides over 300 enterprise-wide reports, monitoring and alerts, policy based action and file system capacity automation in the heterogeneous environment. TotalStorage Productivity Center for Data helps improve capacity utilization of filesystems and databases and helps add intelligent data protection and retention practices. TotalStorage Productivity Center for Data performs the following functions: Discover and monitor disks, partitions, shared directories, and servers. Monitor and report on capacity and utilization across platforms to help you to identify trends and prevent problems. Monitor storage assets associated with enterprise-wide databases and issues notifications of potential problems. Provides a wide variety of standardized reports about filesystems, databases, and storage infrastructure to track usage and availability. Provide file analysis across platforms to help you to identify and reclaim space used by non-essential files. Provide policy-based management and automated capacity provisioning for file systems when user-defined thresholds are reached. Generate invoices that charge back for storage usage on a departmental, group, or user level. These functions that are available with Data Manager are designed to help lower storage costs by: Improving storage utilization Enabling intelligent capacity planning Supporting application availability through computer uptime reporting and application database monitoring. The architecture of IBM TotalStorage Productivity Center for Data enables system administrators to see all of the storage assets including direct-attached storage and network-attached storage. This comprehensive view of the entire storage map allows the administrators to manage much larger environments, but also get the information about utilization and usage that is typically required in large environments. The information collected by TotalStorage Productivity Center for Data can help you make intelligent decisions optimizing the utilization of your open system environments. The data collected by TotalStorage Productivity Center for Data helps you understand what is really going on with the data that resides on your servers. This includes views as to when files are Chapter 1. Introduction to IBM TotalStorage Productivity Center 5
    • created, accessed and modified and by what group or user. This type of information enables system administrators to map the actual storage resource to the consumers of that resource. The ability to map storage consumption to storage hardware has become increasingly important as the size of open systems environments have increased. In addition to understanding the current consumption and usage of data within the enterprise, TotalStorage Productivity Center for Data keeps track of this information over time. Not only does this historical view of storage consumption and utilization allow you to see usage trends over time, it also enables the system administrator to see a projected use of storage into the future. This allows the system administrator to plan the purchase of additional capacity in a planned proactive manner rather than just reacting to being out of space. The major components of TotalStorage Productivity Center for Data are: Data Manager The manager controls the discovery, reporting, and alert functions. It does the following: – Receives information from the agents and stores that information in the central repository Issues commands to agents for jobs. – Receives requests from clients for information and retrieves the requested information from the central data repository. Data agents on managed systems An agent resides on each managed system. Each agent performs the following functions: – Runs probes and scans. – Collects storage-related information about the volumes or file systems that are accessible to the managed systems. – Forwards information to the manager to be stored in the database repository. Web server The optional Web server permits remote Web access to the server. Clients Clients communicate directly to Data Manager to perform administration, monitoring, and reporting. A client can be a locally installed interface to Data Manager, or it can use the Web server to access the user interface through a Web browser. IBM TotalStorage Productivity Center for Disk IBM TotalStorage Productivity Center for Disk enables device configuration and management of SAN attached devices from a single console. In addition, it also includes performance capabilities to monitor and manage the performance of the disks. TotalStorage Productivity Center for Disk simplifies the complexity of managing multiple SAN attached storage devices. It allows you to manage SANs and heterogeneous storage from a single console. TotalStorage Productivity Center for Disk allows you to manage network storage components based on SMI-S, such as: IBM TotalStorage SAN Volume Controller (SVC) IBM TotalStorage Enterprise Storage Server® (ESS) IBM TotalStorage Disk Subsystems (DS4000™, DS6000™, and DS8000™ Series) Other storage subsystems that support the SMI-S standards Device discovery is performed by the Service Location Protocol (SLP), as specified by SMI-S. Configuration of the discovered devices is possible in conjunction with CIM agents associated with those devices, using the standard mechanisms defined in SMI-S. TotalStorage Productivity Center for Disk gathers events, and can launch an element manager specific to each discovered device.6 IBM TotalStorage Productivity Center: The Next Generation
    • TotalStorage Productivity Center for Disk performance functions include: Collect and store performance data and provide alerts Provide graphical performance reports Helps optimize storage allocation Provide volume contention analysisThrough the use of data collection, setting of thresholds and use of performance reports,performance can be monitored for the ESS, DS4000, DS6000, DS8000, SVC, and any otherstorage subsystem that supports the SMI-S block server performance subprofile. Theperformance function starts with the data collection task, responsible for capturingperformance statistics for the devices and storing the data in the database.Thresholds can be set for certain performance metrics depending on the type of device.Threshold checking is performed during data collection. When performance is outside thespecified boundaries, alerts can be generated.Once performance data has been collected, you can configure TotalStorage ProductivityCenter for Disk to present graphical or text reports on the historical performance behavior ofspecified devices. The performance reports provide information about the performancemetrics and display past or current performance in graphical form.IBM TotalStorage Productivity Center for FabricTotalStorage Productivity Center for Fabric provides automated device discovery, topologyrendering, error detection fault isolation, SAN error predictor, zone control, real-timemonitoring and alerts and event management for heterogeneous enterprise SANenvironments. TotalStorage Productivity Center for Fabric simplifies the management andimproves the availability of the SAN environment.The Fabric manager can monitor and report on SAN resources and switch performance. Itprovides a single location for zone control. TotalStorage Productivity Center for Fabricdiscovers existing zones and zone members and allows you to modify or delete them. Inaddition, you can create new zones. Support for aliases is also provided. Switch performanceand capacity management reporting and monitoring can help determine if more bandwidth isneeded.TotalStorage Productivity Center for Fabric gives you the ability to view events happening inyour SAN environment and records state changes. The events are displayed in a color-codedfashion and can be further customized to reflect organizational priorities. TotalStorageProductivity Center for Fabric forwards events signaling topology changes or updates to theIBM Tivoli Enterprise™ Console, to another SNMP manager, or both.TotalStorage Productivity Center for Fabric supports host bus adapters (HBAs), disksubsystems, tape systems, SAN switches, routers and gateways. For a complete list of thesupported devices, go to the following URL and navigate to the Fabric Manager supportpages.http://www.ibm.com/servers/storage/support/software/tpcThe components of TotalStorage Productivity Center for Fabric are: Fabric Manager The manager performs the following functions: – Discovers SAN components and devices, – Gathers data from agents on managed hosts, such as descriptions of SANs, and host information. Chapter 1. Introduction to IBM TotalStorage Productivity Center 7
    • – Generates Simple Network Management Protocol (SNMP) events when a change is detected in the SAN fabric. – Forwards events to the Tivoli Enterprise Console® or an SNMP console. – Monitors switch performance by port and by constraint violations Fabric agents on managed hosts Each agent performs the following functions: – Gathers information about the SAN by querying switches and devices for attribute and topology information. – Gathers event information detected by host bus adapters (HBAs). IBM TotalStorage Productivity Center for Replication IBM TotalStorage Productivity Center for Replication simplifies copy services management for the IBM TotalStorage Enterprise Storage Server (ESS). IBM TotalStorage Productivity Center for Replication provides configuration and management of the FlashCopy® and Synchronous PPRC capabilities of the ESS.1.2 What is new in IBM TotalStorage Productivity Center V3.1 This section describes the enhancements and functions in Total Storage Productivity Center V3.1. Topology Viewer Within TotalStorage Productivity Center the Topology Viewer is designed to provide an extended graphical topology view; 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 function within the TotalStorage Productivity Center UI without users losing their orientation to the environment. This kind of flexibility through the Topology Viewer UI will afford better cognitive mapping between the entities within the environment, and provide data about entities and access to additional tasks and functionality associated with the current environmental view and the users role. The Topology Viewer uses the TotalStorage Productivity Center database as the central repository for all data that it displays. It actually reads the data in user definable intervals from the database and updates, if necessary, the displayed information automatically. Figure 1-3 on page 9 shows the Topology Viewer Overview view.8 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 1-3 Topology Viewer Overview viewTape library supportTotalStorage Productivity Center provides support for tape library management. TapeManager is present and available in the GUI whenever the Device Server is installed. UsingTape Manager, you can discover tape libraries, group libraries to monitor multiple libraries,view alerts generated by tape libraries, and launch tape library element managers. The tapelibraries supported are: – IBM 3584 – IBM 3494 - limited supportSummary of changes in TotalStorage Productivity Center V3.1TotalStorage Productivity Center V3.1 offers: A single, integrated package with a new topology viewer, providing an end-to-end view of the Storage Area Network (from hosts to physical disks). A simple, easy to install package with management server support added for IBM AIX® V5.3, and integrating IBM DB2® as the management server database. The server components of IBM TotalStorage Productivity Center can now be installed on: – Microsoft® Windows® 2003 – AIX 5.3 (p5 supported) – Linux® RedHat 3.0 on xSeries® Performance management support for the IBM TotalStorage DS4000 family and additional performance support for select IBM TotalStorage, Brocade, Cisco, and McData fabric switches and directors. Role-based task authentication which assists with implementing storage management that conforms to government initiatives. Support for managing IBM TotalStorage 3584 and limited support for IBM TotalStorage Enterprise Automated 3494 tape libraries. Support for third-party disk array systems that include Storage Management Interface Specification (SMI-S) Providers certified by the SNIA Conformance Test Program (CTP) to Chapter 1. Introduction to IBM TotalStorage Productivity Center 9
    • be SMI-S 1.02 or SMI-S 1.1 compliant. This support includes storage provisioning, as well as asset and capacity reporting. Consolidated and enhanced device discovery and control through CIMOM – All CIMOM related information gathered during CIMOM discovery are shared by all TotalStorage Productivity Center components Consistent reporting capabilities (scheduled and ad hoc) – The scheduling capabilities of TotalStorage Productivity Center for Data have been extended to all components. Consolidated message logging Data export capabilities (HTML, CSV) Single set of services for consistent administration and operations: – Policy definitions – Event handling – Resource groups New command line interface tpctool for configuration, fabric and disk management, and performance reporting. TotalStorage Productivity Center for Fabric adds support for SMI-S-based fabric, collecting performance statistics from IBM and third-party SAN fabrics. TotalStorage Productivity Center for Fabric is designed to provide an extended graphical topology view of your storage area network that displays the hosts, SAN fabric and storage, showing the SAN connectivity and its availability and also the fabric performance metrics and the status of the ports on the SAN fabric. TotalStorage Productivity Center V3.1 will provide the following support for any disk subsystems (including non IBM devices) that are SNIA SMI-S 1.0.2 or 1.1 compliant (for example, SNIA CTP provider certified). The support provided for these SMI-S compliant subystems will include those functions enabled by support for the required profiles of the SMI-S standard. Typically, that will include: – Discovery of CIMOMs and storage subsystems (through SLP) – Reporting on subsystem asset and capacity data (with details on storage subsystems, disk groups, disks, storage pools and volumes) – Monitoring – Provisioning (volume creation and volume mapping/masking to host server) – Performance metrics for storage subsystem ports, subsystem volumes, and top level storage Computer Systems (including overall performance metrics for the storage device). It should also be noted that IBM will rely on the testing and certification being performed through SNIA for SMI-S compliance. The anticipated list of non IBM disk subsystems that TotalStorage Productivity Center V3.1 will support through SMI-S compliance for the functions listed here include: • EMC Symmetrix • EMC Clariion • Engenio subsystems • HDS Thunder 9500V • HDS Lightning 9900V • HPQ XP 512, XP 1024 • HPQ Storage Works Virtual Array family10 IBM TotalStorage Productivity Center: The Next Generation
    • For a complete list of third-party device support of SMI-S, consult the SNIA Web site: http://www.snia.org/ctp1.2.1 Changes between TPC V3.1 and V2 The following is a list of TotalStorage Productivity Center items in prior releases that are not in TotalStorage Productivity Center V3.1. Workflow integration of TotalStorage Productivity Center with Tivoli Provisioning Manager is not supported. ED-FI or SAN error predictor functionality is not supported in this release. TotalStorage Productivity Center for Replication is not integrated with the V3.1 components (TotalStorage Productivity Center for Data, TotalStorage Productivity Center for Disk and TotalStorage Productivity Center for Fabric). Prerequisite Software Installer Suite Installer ICAT installation Tivoli NetView installation, uninstallation, and upgrade IBM Director base IIBM TotalStorage Productivity Center for Data supported its database repository on Oracle, SQL Server, and Cloudscape™ in Version 2.x. These databases are not supported in TotalStorage Productivity Center V3.1. Installing Simple Network Management Protocol (SNMP) service with community name of public and Management Information Base (MIB) files is no longer necessary. iSCSI support in Fabric Manager1.3 Licensing All IBM TotalStorage Productivity Center licenses offer a common set of general functionalities, like the TotalStorage Productivity Center Administrative Services, Disk Management (not including performance management), Fabric Management (not including performance management) and Tape Management (reporting). IBM TotalStorage Productivity Center licensing is based on the full usable terabyte capacity of the associated storage devices to be managed1.3.1 IBM TotalStorage Productivity Center Limited Edition IBM TotalStorage Productivity Center Limited Edition is packaged with IBM TotalStorage Family of DS Platforms, including DS8000 DS6000 DS4000 SAN Volume Controller SVC IBM 3584 tape library Productivity Center Limited Edition is designed to help you: Discover and configure IBM and heterogeneous SMI-S supported devices. Perform event gather, error logging and launch device element managers. Provide basic asset and capacity reporting. Chapter 1. Introduction to IBM TotalStorage Productivity Center 11
    • Display an end-to-end topology view of your storage infrastructure and health console. Enable a simple upgrade path to IBM TotalStorage Productivity Center Standard Edition (or single-priced modules). IBM TotalStorage Productivity Center Limited Edition is a management option offered with IBM midrange and high-end storage systems. This tool provides storage administrators with a simple way to conduct device management for multiple storage arrays and SAN fabric components from a single integrated console that also is the base of operations for the IBM TotalStorage Productivity Center suite. This offering is available with Productivity Center for Data, Fabric and Disk. Enabling additional function To enable additional function when IBM TotalStorage Productivity Center Limited Edition is installed you would add the corresponding license key. Installing the IBM TotalStorage Productivity Center for Disk license enables: Subsystem performance monitors Performance triggering in subsystem alerts Advanced performance reports Performance overlay in topology Installing the IBM TotalStorage Productivity Center for Fabric license enables: Fabric performance monitors Performance triggering in fabric alert Advanced performance report Performance overlay in topology1.3.2 IBM TotalStorage Productivity Center Standard Edition IBM TotalStorage Productivity Center Standard Edition brings together TotalStorage Productivity Center for Data, TotalStorage Productivity Center for Disk and TotalStorage Productivity Center for Fabric with the advanced performance management capabilities in one package and can provide an end-to-end view of the storage infrastructure. IBM TotalStorage Productivity Center Standard Edition provides all the management capabilities to better manage your heterogeneous storage infrastructure from application to back-end storage system disk at a single bundled price. With Productivity Center Standard Edition you can centralize the management of your storage infrastructure from a single interface using role-based administration and single sign-on. This also provides a single management application with modular integrated components that easy to install, configure and operate. Productivity Center Standard Edition additionally can manage performance and connectivity from the host file system to the physical disk, including in-depth performance monitoring and analysis on SAN fabric performance. TotalStorage Productivity Center Standard Edition provides a main storage management application to monitor, plan, configure, report and do problem determination on heterogeneous storage infrastructure.1.3.3 IBM TotalStorage Productivity Center for Replication IBM TotalStorage Productivity Center for Replication simplifies the configuration of advanced copy services for the IBM TotalStorage ESS, attached to z/OS or open systems. Productivity Center for Replication will also monitor the advanced copy services and notify the storage administrator if problems are encountered.12 IBM TotalStorage Productivity Center: The Next Generation
    • 2 Chapter 2. Key concepts There are industry standards and protocols that are the basis of the IBM TotalStorage Productivity Center. The understanding of these concepts is important for installing and customizing the IBM TotalStorage Productivity Center. This chapter describes the standards on which the IBM TotalStorage Productivity Center is built, as well as the methods of communication used to discover and manage storage devices. Communication between various components of IBM TotalStorage Productivity Center will also be discussed. Diagrams are provided to show the relationship and interaction of the various elements in the IBM TotalStorage Productivity Center environment.© Copyright IBM Corp. 2006. All rights reserved. 13
    • 2.1 Standards used in IBM TotalStorage Productivity Center This section presents an overview of the standards that are used within IBM TotalStorage Productivity Center by the different components. SLP and CIM are described in detail since they are new concepts to many people that work with TotalStorage Productivity Center and are important to understand. Vendor specific tools are available to manage devices in the SAN, but these proprietary interfaces are not used within TotalStorage Productivity Center. The only exception is the application programming interface (API) that Brocade has made available to manage their Fibre Channel switches. This API is used within TotalStorage Productivity Center.2.1.1 ANSI standards Several standards have been published for the in-band management of storage devices, for example, SCSI Enclosure Services (SES). T11 committee Since the 1970s, the objective of the ANSI T11 committee is to define interface standards for high-performance and mass storage applications. Since that time, the committee has completed work on three projects: High-Performance Parallel Interface (HIPPI) Intelligent Peripheral Interface (IPI) Single-Byte Command Code Sets Connection (SBCON) Currently the group is working on Fibre Channel (FC) and Storage Network Management (SM) standards. Fibre Channel Generic Services The Fibre Channel Generic Services (FC-GS-3) Directory Service and the Management Service are being used within IBM TotalStorage Productivity Center for the SAN management. The availability and level of function depends on the implementation by the individual vendor. TotalStorage Productivity Center uses this standard. For more information about the T11 committee, go to: http://www.t11.org/index.htm2.1.2 Web-Based Enterprise Management Web-Based Enterprise Management (WBEM) 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. See also 2.3, “Common Information Model” on page 28. xmlCIM This is a grammar to describe CIM declarations and messages used by the CIM protocol. Hypertext Transfer Protocol (HTTP)14 IBM TotalStorage Productivity Center: The Next Generation
    • Hypertext Transfer Protocol over Secure Socket Layer (HTTPS) HTTP and HTTPS are used as a way to enable communication between a management application and a device that both use CIM. For more information go to: http://www.dmtf.org/standards/wbem/ WBEM architecture The WBEM architecture defines the following elements: CIM Client The CIM Client is a management application that uses CIM to manage devices. A CIM Client can reside anywhere in the network, because it uses HTTP(S) to talk to CIM Object Managers and Agents. TotalStorage Productivity Center incorporates a CIM Client. CIM Managed Object A CIM Managed Object is a hardware or software component that can be managed by a management application using CIM. CIM Agent The CIM Agent is embedded into a device or it can be installed on the server using the CIM provider as the translator of device’s proprietary commands to CIM calls, and interfaces with the management application (the CIM Client). The CIM Agent is linked to one device. CIM Provider A CIM Provider is the element that translates CIM calls to the device-specific commands. That is the reason why a CIM-Provider is - in most of the cases - delivered from the hardware vendor. You can imagine it like a device driver. A CIM Provider is always closely linked to a CIM Object Manager or CIM Agent. CIM Object Manager A CIM Object Manager (CIMOM) is a part of the CIM Server that links the CIM Client to the CIM Provider. It enables a single CIM Agent to talk to multiple devices. CIM Server A CIM Server is the software that runs the CIMOM and the CIM provider for a set of devices. This approach is used when the devices do not have an embedded CIM Agent. This term is often not used. Instead people often use the term CIMOM when they really mean the CIM Server.2.1.3 Storage Networking Industry Association The Storage Networking Industry Association (SNIA) defines standards that are used within IBM TotalStorage Productivity Center. You can find more information at the following Web site: http://www.snia.org Fibre Channel Common HBA API The Fibre Channel Common HBA API is used as a standard for in-band storage management. It acts as a bridge between a SAN management application like Fabric Manager and the Fibre Channel Generic Services. IBM TotalStorage Productivity Center for Fabric Agent uses this standard. Chapter 2. Key concepts 15
    • Storage Management Initiative - Specification SNIA has fully adopted and enhanced the CIM for Storage Management in its SMI-S. SMI-S was launched in mid-2002 to create and develop a universal open interface for managing storage devices including storage networks. The idea behind SMI-S is to standardize the management interfaces so that management applications can use these and provide cross device management. This means that a newly introduced device can be immediately managed as it conforms to the standards. SMI-S extends CIM and WBEM with the following features: A single management transport Within the WBEM architecture, the CIM-XML over HTTP protocol was selected for this transport in SMI-S. A complete, unified, and rigidly specified object model SMI-S defines profiles and recipes within the CIM that enables a management client to reliably use a component vendor’s implementation of the standard, such as the control of LUNs and zones in the context of a SAN. Consistent use of durable names As a storage network configuration evolves and is reconfigured, key long-lived resources, such as disk volumes, must be identified uniquely and consistently over time. Rigorously documented client implementation considerations SMI-S provides client developers with vital information for traversing CIM classes within a device or subsystem and between devices and subsystems such that complex storage networking topologies can be successfully mapped and reliably controlled. An automated discovery system SMI-S compliant products, when introduced in a SAN environment, automatically announce their presence and capabilities to other constituents using SLP (see 2.2.1, “SLP architecture” on page 18). Resource locking SMI-S compliant management applications from multiple vendors can exist in the same storage device or SAN and cooperatively share resources through a lock manager. The models and protocols in the SMI-S implementation are platform-independent, enabling application development for any platform, and enabling them to run on different platforms. The SNIA also provides interoperability tests which help vendors to test their applications and devices if they conform to the standard. For information about SNIA certified devices, go to the SNIA OEM Vendor Certification site: http://www.snia.org/ctp/conformingproviders Managers or components that use this standard include: IBM TotalStorage Productivity Center for Disk IBM TotalStorage Productivity Center for Replication IBM TotalStorage Productivity Center for Data16 IBM TotalStorage Productivity Center: The Next Generation
    • 2.1.4 Simple Network Management Protocol The SNMP is an Internet Engineering Task Force (IETF) protocol for monitoring and managing systems and devices in a network. Functions supported by the SNMP protocol are the request and retrieval of data, the setting or writing of data, and traps that signal the occurrence of events. SNMP is a method that enables a management application to query information from a managed device. The managed device has software running that sends and receives the SNMP information. This software module is usually called the SNMP agent. Device management An SNMP manager can read information from an SNMP agent to monitor a device. Therefore the device needs to be polled on an interval basis. The SNMP manager can also change the configuration of a device, by setting certain values to corresponding variables. Managers or components that use these standards include the IBM TotalStorage Productivity Center for Fabric. Traps A device can also be set up to send a notification to the SNMP manager (this is called a trap) to inform this SNMP manager asynchronously of a status change. Depending on the existing environment and organization, it is likely that your environment already has an SNMP management application in place. The managers or components that use this standard are: IBM TotalStorage Productivity Center for Fabric (sending and receiving of traps) IBM TotalStorage Productivity Center for Data can be set up to send traps, but does not receive traps Management Information Base SNMP use a hierarchical structured Management Information Base (MIB) to define the meaning and the type of a particular value. An MIB defines managed objects that describe the behavior of the SNMP entity, which can be anything from a IP router to a storage subsystem. Each SNMP managed device has its own MIB. The information is organized in a tree structure. Note: For more information about SNMP, refer to TCP/IP Tutorial and Technical Overview, GG24-3376. IBM TotalStorage Productivity Center for Data MIB file For users planning to use the IBM TotalStorage Productivity Center for Data SNMP trap alert notification capabilities, an SNMP MIB is included in the server installation. You can find the SNMP MIB in the file tivoli_install_directory/snmp/tivoliSRM.MIB. The MIB is provided for use by your SNMP management console software. Most SNMP management station products provide a program called an MIB compiler that can be used to import MIBs. This allows you to better view Productivity Center for Data generated SNMP traps from within your management console software. Refer to your management console software documentation for instructions on how to compile or import a third-party MIB. Chapter 2. Key concepts 17
    • 2.1.5 Fibre Alliance MIB The Fibre Alliance has defined an MIB for the management of storage devices. The Fibre Alliance is presenting the MIB to the IETF standardization. The intention of putting together this MIB was to have one MIB that covers most (if not all) of the attributes of storage devices from multiple vendors. The idea was to have only one MIB that is loaded onto an SNMP manager, one MIB file for each component. However, this requires that all devices comply with that standard MIB, which is not always the case. Note: This MIB is not part of IBM TotalStorage Productivity Center. To learn more about Fibre Alliance and MIB, refer to the following Web sites: http://www.fibrealliance.org http://www.fibrealliance.org/fb/mib_intro.htm2.2 Service Location Protocol overview The Service Location Protocol (SLP) is an IETF standard, documented in Request for Comments (RFCs) 2165, 2608, 2609, 2610, and 2614. SLP provides a scalable framework for the discovery and selection of network services. SLP enables the discovery and selection of generic services, which can range in function from hardware services such as those for printers or fax machines, to software services such as those for file servers, e-mail servers, Web servers, databases, or any other possible services that are accessible through an IP network. Traditionally, to use a particular service, an end-user or client application needs to supply the host name or network IP address of that service. With SLP, however, the user or client no longer needs to know individual host names or IP addresses (for the most part). Instead, the user or client can search the network for the desired service type and an optional set of qualifying attributes. For example, a user can specify to search for all available printers that support PostScript, based on the given service type (printers), and the given attributes (PostScript). SLP searches the user’s network for any matching services and returns the discovered list to the user.2.2.1 SLP architecture The SLP architecture includes three major components, a Service Agent (SA), a User Agent (UA), and a Directory Agent (DA). The SA and UA are required components in an SLP environment, where the SLP DA is optional. The SMI-S specification introduces SLP as the method for the management applications (the CIM clients) to locate managed objects. In SLP, an SA is used to report to UAs that a service that has been registered with the SA is available. For more information see: http://www.caldera.com/support/docs/volution/vm/ig/appendixb.html#AEN2455 The following sections describes the components of SLP.18 IBM TotalStorage Productivity Center: The Next Generation
    • Service AgentThe SLP SA is a component of the SLP architecture that works on behalf of one or morenetwork services to broadcast the availability of those services by using broadcasts. The SAreplies to external service requests using IP unicasts to provide the requested informationabout the registered services, if it is available.The SA can run in the same process or in a different process as the service itself. In eithercase, the SA supports registration and deregistration requests for the service (as shown inthe right part of Figure 2-1). The service registers itself with the SA during startup, andremoves the registration for itself during shutdown. In addition, every service registration isassociated with a life-span value, which specifies the time that the registration will be active.In the left part of the diagram, you can see the interaction between a UA and the SA.Figure 2-1 SLP SA interactions (without SLP DA)A service is required to reregister itself periodically, before the life-span of its previousregistration expires. This ensures that expired registration entries are not kept. For instance, ifa service becomes inactive without removing the registration for itself, that old registration isremoved automatically when its life span expires. The maximum life span of a registration is65535 seconds (about 18 hours).User AgentThe SLP UA is a process working on the behalf of the user to establish contact with somenetwork service. The UA retrieves (or queries for) service information from the ServiceAgents or Directory Agents.The UA is a component of SLP that is closely associated with a client application or a userwho is searching for the location of one or more services in the network. You can use the SLPUA by defining a service type that you want the SLP UA to locate. The SLP UA then retrievesa set of discovered services, including their service Uniform Resource Locator (URL) and anyservice attributes. You can then use the service’s URL to connect to the service.The SLP UA locates the registered services, based on a general description of the servicesthat the user or client application has specified. This description usually consists of a servicetype, and any service attributes, which are matched against the service URLs registered inthe SLP Service Agents.The SLP UA usually runs in the same process as the client application, although it is notnecessary to do so. The SLP UA processes find requests by sending out multicast messagesto the network and targeting all SLP SAs within the multicast range with a single UserDatagram Protocol (UDP) message. The SLP UA can, therefore, discover these SAs with a Chapter 2. Key concepts 19
    • minimum of network overhead. When an SA receives a service request, it compares its own registered services with the requested service type and any service attributes, if specified, and returns matches to the UA using a unicast reply message. The SLP UA follows the multicast convergence algorithm 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 the client application or user. The client application or user is then responsible for contacting the individual services, as needed, using the service’s URL (see Figure 2-2). Figure 2-2 SLP UA interactions without SLP DA An SLP UA is not required to discover all matching services that exist in the network, but only enough of them to provide useful results. This restriction is mainly the result of the transmission size limits for UDP packets. They can be exceeded when there are many registered services or when the registered services have lengthy URLs or a large number of attributes. However, in most modern SLP implementations, the UAs can recognize truncated service replies and establish TCP connections to retrieve all of the information of the registered services. With this type of UA and SA implementation, the only exposure that remains is when there are too many SAs within the multicast range. This can cut short the multicast convergence mechanism. This exposure can be mitigated by the SLP administrator by setting up one or more SLP DAs. The SLP process shown in the diagram above can be described as follows. The application needs a specific service and issues an “find request” The UA starts a multicast service request One or more SAs are answering and providing service information The application gets feedback from the UA The application is able to contact and use the service by their own Note: TotalStorage Productivity Center acts as a User Agent in terms of SLP communication.20 IBM TotalStorage Productivity Center: The Next Generation
    • Directory AgentThe SLP DA is an optional component of SLP that collects and caches network servicebroadcasts. The DA is used primarily to simplify SLP administration and to improve SLPperformance.You can consider the SLP DA as an intermediate tier in the SLP architecture. It is placedbetween the UAs and the SAs so that both UAs and SAs communicate only with the DAinstead of with each other. This eliminates a large portion of the multicast request or replytraffic in the network. It also protects the SAs from being overwhelmed by too many servicerequests if there are many UAs in the environment.Figure 2-3 shows the interactions of the SLP UAs and SAs in an environment with SLP DAs.Figure 2-3 SLP User Agent interactions with User Agent and Service AgentWhen SLP DAs are present, the behavior of both SAs and UAs changes significantly. Whenan SA is first initializing, it performs a DA discovery using a multicast service request. It alsospecifies the special, reserved service type service:directory-agent. This process is alsocalled active DA discovery. It is achieved through the same mechanism as any otherdiscovery using SLP.Similarly, in most cases, an SLP UA also performs active DA discovery using multicastingwhen it first starts. However, if the SLP UA is statically configured with one or more DAaddresses, it uses those addresses instead. If it is aware of one or more DAs, either throughstatic configuration or active discovery, it sends unicast service requests to those DAs insteadof multicasting to SAs. The DA replies with unicast service replies, providing the requestedservice URLs and attributes. Figure 2-4 on page 22 shows the interactions of UAs and SAswith DAs, during active DA discovery. Chapter 2. Key concepts 21
    • Figure 2-4 SLP Directory Agent discovery interactions The SLP DA functions similarly to an SLP SA, receiving registration and deregistration requests, and responding to service requests with unicast service replies. There are a couple of differences, where DAs provide more functionality than SAs. One area, mentioned previously, is that DAs respond to service requests of the service:directory-agent service type with a DA advertisement response message, passing back a service URL containing the DA’s IP address. This allows SAs and UAs to perform active discovery on DAs. One other difference is that when a DA first initializes, it sends a multicast DA advertisement message to advertise its services to any existing SAs (and UAs) that may already be active in the network. UAs can optionally listen for, and SAs are required to listen for, such advertisement messages. This listening process is also sometimes called passive DA discovery. When the SA finds a new DA through passive DA discovery, it sends registration requests for all its currently registered services to that new DA. Figure 2-5 shows the interactions of DAs with SAs and UAs, during passive DA discovery. Figure 2-5 Service Location Protocol passive DA discovery22 IBM TotalStorage Productivity Center: The Next Generation
    • Why use an SLP DA? The primary reason to use DAs is to reduce the amount of multicast traffic involved in service discovery. In a large network with many UAs and SAs, the amount of multicast traffic involved in service discovery can become so large that network performance degrades. By deploying one or more DAs, UAs must unicast to DAs for service and SAs must register with DAs using unicast. The only SLP-registered multicast in a network with DAs is for active and passive DA discovery. SAs register automatically with any DAs they discover within a set of common scopes. Consequently, DAs within the UAs scopes reduce multicast. By eliminating multicast for normal UA request, delays and time outs are eliminated. DAs act as a focal point for SA and UA activity. Deploying one or several DAs for a collection of scopes provides a centralized point for monitoring SLP activity. You can deploy any number of DAs for a particular scope or scopes, depending on the need to balance the load. In networks without multicasting enabled, you can configure SLP to use broadcast. However, broadcast is inefficient, because it requires each host to process the message. Broadcast also does not normally propagate across routers. As a solution in a network without multicast, DAs can be deployed on multihomed hosts to bridge SLP advertisements between the subnets. When to use DAs Use DAs in your enterprise when any of the following conditions are true: Multicast SLP traffic exceeds one percent (1%) of the bandwidth on your network, as measured by using a network traffic analyzer. UA clients experience long delays or timeouts during multicast service request. You want to centralize monitoring of SLP service advertisements for particular scopes on one or several hosts. Your network does not have multicast enabled and consists of multiple subnets that must share services.2.2.2 SLP communication SLP uses three methods to send messages across an IP network, unicast, broadcast, or multicast. Data can be sent to one single destination (unicast) or to multiple destinations that are listening at the same time (multicast). The difference between a multicast and a broadcast is quite important. A broadcast addresses all stations in a network. Multicast messages are only by those stations that are member of a multicast group (that have joined a multicast group). Unicast The most common communication method, unicast, requires that a sender of a message identifies one and only one target of that message. The target IP address is encoded within the message packet, and is used by the routers along the network path to route the packet to the proper destination. If a sender wants to send the same message to multiple recipients, then multiple messages must be generated and placed in the network, one message per recipient. When there are many potential recipients for a particular message, then this places an unnecessary strain on network resources, since the same data is duplicated many times, where the only difference is the target IP address encoded within the messages. Chapter 2. Key concepts 23
    • Broadcast In cases where the same message must be sent to many targets, broadcast is a much better choice than unicast, because it puts much less strain in the network. Broadcasting uses a special IP address, 255.255.255.255, which indicates that the message packet is intended to be sent to all nodes in a network. As a result, the sender of a message needs to generate only a single copy of that message, and can still transmit it to multiple recipients, that is to all members of the network. The routers multiplex the message packet, as it is sent along all possible routes in the network to reach all possible destinations. This puts much less strain on network bandwidth, because only a single message stream enters the network, as opposed to one message stream per recipient. However, it puts much more strain on the individual nodes (and routers) in the network, since every node receives the message, even though most likely not every node is interested in the message. This means that those members of the network that were not the intended recipients, who receive the message anyway, must receive the unwanted message and discard it. Due to this inefficiency, in most network configurations, routers are configured to not forward any broadcast traffic. This means that any broadcast messages can only reach nodes on the same subnet as the sender. Multicast The ability of the SLP to discover automatically services that are available in the network, without a lot of setup or configuration, depends in a large part on the use of IP multicasting. IP multicasting is a broad subject in itself, therefore only a brief, simple overview is provided here. Multicasting can be thought of as more sophisticated broadcast, which aims to solve some of the inefficiencies inherent in the broadcasting mechanism. With multicasting, again the sender of a message has to generate only a single copy of the message, saving network bandwidth. However unlike broadcasting, with multicasting, not every member of the network receives the message. Only those members who have explicitly expressed an interest in the particular multicast stream receive the message. Multicasting introduces a concept called a multicast group, where each multicast group is associated with a specific IP address. A particular network node (host) can join one or more multicast groups, which notifies the associated router or routers that there is an interest in receiving multicast streams for those groups. When the sender, who does not necessarily have to be part of the same group, sends messages to a particular multicast group, that message is routed appropriately to only those subnets, which contain members of that multicast group. This avoids flooding the entire network with the message, as is the case for broadcast traffic. Multicast addresses The Internet Assigned Numbers Authority (IANA), which controls the assignment of IP addresses, has assigned the old Class D IP address range to be used for IP multicasting. Of this entire range, which extends from 224.0.0.0 to 239.255.255.255, the 224.0.0.* addresses are reserved for router management and communication. Some of the 224.0.1.* addresses are reserved for particular standardized multicast applications. Each of the remaining addresses corresponds to a particular general purpose multicast group. The Service Location Protocol uses address 239.255.255.253 for all its multicast traffic. The port number for SLP is 427, for both unicast and multicast.24 IBM TotalStorage Productivity Center: The Next Generation
    • SLP messages In order to be able to provide a framework for service location, SLP agents communicate with each other using eleven different types of messages. The dialog between agents is usually limited to these very simple exchanges of request and reply messages shown in Figure 2-6.Message DescriptionService Request (SrvRqst) Sent by UAs to SAs and DAs to request the location of a service.Service Reply (SrvRply) Sent by SAs and DAs containing information about a service that is no longer available.Service Registration (SrvReg) Sent by SAs to DAs containing information about a service that is available.Service Deregister (SrvDeReg) Sent by SAs to inform DAs that a service is no longer available.Service Acknowledge (SrvAck) A generic acknowledgement that is sent by DAs to SAs as a reply to SrvReg and SrvDeReg messages.Attribute Request (AttrRqst) Sent by UAs to request the attributes of a service.Attribute Reply (AttrRply) Sent by SAs and DAs in reply to a AttrRqst. The AttrRply contains the list of attributes that were requested.Service Type Request (SrvTypeRqst) Sent by UAs to SAs and DAs requesting the types of services that are available.Service Type Reply (SrvTypeReply) Sent by SAs and DAs in reply to a SrvTypeRqst. The SrvTypeRply contains a list of requested service types.DA Advertisement (DAAdvert) Sent by DAs to let SAs and UAs know where they are.SA Advertisement (SAAdvert) Sent by SAs to let UAs know where they are.Figure 2-6 Dialog syntax used in SLP communications2.2.3 Configuration recommendations Ideally, after TotalStorage Productivity Center is installed, it would discover all storage devices that it can reach physically over the IP network. However in most situations, this is not the case. This is primarily the result of the previously mentioned limitations of multicasting and the fact that the majority of routers have multicasting disabled by default. As a result, in most cases without any additional configuration, TotalStorage Productivity Center discovers only those storage devices that reside in its own subnet, but no more. The following sections provide some configuration recommendations to enable TotalStorage Productivity Center to discover a larger set of storage devices. Router configuration The majority of components which allow multicasting to work is implemented in the router operating system software. As a result, it is necessary to configure the routers properly in the network to allow multicasting to work effectively. Unfortunately, there is a dizzying array of protocols and algorithms which can be used to configure particular routers to enable multicasting. The most common ones are: Internet Group Management Protocol (IGMP) is used to register individual hosts in particular multicast groups, and to query group membership on particular subnets. Distance Vector Multicast Routing Protocol (DVMRP) is a set of routing algorithms that use a technique called Reverse Path Forwarding to decide how multicast packets are to be routed in the network. Chapter 2. Key concepts 25
    • Protocol-Independent Multicast (PIM) comes in two varieties: dense mode (PIM-DM) and sparse mode (PIM-SM). They are optimized to networks where either a large percentage of nodes require multicast traffic (dense), or a small percentage require the traffic (sparse). Multicast Open Shortest Path First (MOSPF) is an extension of OSPF, a link-state unicast routing protocol that attempts to find the shortest path between any two networks or subnets to provide the most optimal routing of packets. The routers of interest are all those which are associated with subnets that contain one or more storage devices which are to be discovered and managed by TotalStorage Productivity Center. You can configure the routers in the network to enable multicasting in general, or at least to allow multicasting for the SLP multicast address, 239.255.255.253, and port, 427. This is the most generic solution and permits discovery to work the way that it was intended by the designers of SLP. To properly configure your routers for multicasting, refer to your router manufacturer’s reference and configuration documentation. Although older hardware may not support multicasting, all modern routers do. However, in most cases, multicast support is disabled by default, which means that multicast traffic is sent only among the nodes of a subnet but is not forwarded to other subnets. For SLP, this means that service discovery is limited to only those agents which reside in the same subnet. Firewall configuration In the case where one or more firewalls are used between TotalStorage Productivity Center and the storage devices that are to be managed, the firewalls need to be configured to pass traffic in both directions as SLP communication is 2-way. This means that when TotalStorage Productivity Center, for example, queries an SLP DA which is behind a firewall for the registered services, the response will not use an already opened TCP/IP session but will establish another connection in the direction from the SLP DA to the TotalStorage Productivity Center. For this reason port 427 should be opened in both directions otherwise the response will not be received and TotalStorage Productivity Center will not recognize services offered by this SLP DA. SLP DA configuration If router configuration is not feasible, another technique is to use SLP DAs to circumvent the multicast limitations. Since with statically configured DAs all service requests are unicast instead of multicast by the UA, it is possible to simply configure one DA for each subnet that contains storage devices which are to be discovered by TotalStorage Productivity Center. One DA is sufficient for each of such subnets, although more can be configured without harm perhaps for reasons of fault tolerance. Each of these DAs can discover all services within its own subnet, but no other services outside its own subnet. To allow Productivity Center to discover all of the devices, you must statically configure it with the addresses of each of these DAs. You accomplish this using the IBM TPC panel shown here. As described previously, Productivity Center unicasts service requests to each of these statically configured DAs, but also multicasts service requests on the local subnet on which Productivity Center is installed. Figure 2-7 on page 27 displays a sample environment where DAs have been used to bridge the multicast gap between subnets in this manner.26 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 2-7 Recommended SLP configuration - redraw graphic - change MDM to TPCYou can easily configure an SLP DA by changing the configuration of the SLP SA included aspart of an existing CIM Agent installation. This causes the program that normally runs as anSLP SA to run as an SLP DA instead. The procedure to perform this configuration isexplained in “SLP directory agent configuration” on page 332. Note that the change from SAto DA does not affect the CIMOM service of the subject CIM Agent, which continues tofunction as normal, sending registration and deregistration commands to the DA directly.SLP configuration with services outside local subnetSLA DA and SA can also be configured to cache CIM services information from non localsubnets. Usually CIM Agents or CIMOMs will have local SLP SA function. When there is aneed to discover CIM services outside the local subnet and the network configuration doesnot permit the use of SLP DA in each of them (for example firewall rules do not allow 2-waycommunication on port 427) remote services can be registered on the SLP DA in the localsubnet.This configuration can be done by using slptool which is part of SLP installation packages.The registration is not persistent across system restarts. To achieve persistent registration ofservices outside of the local subnet, these services need to be defined in registration file usedby SLP DA at startup. Refer to 7.16.5, “Creating slp.reg file” on page 336 for information aboutcreating the slp.reg file. Chapter 2. Key concepts 27
    • 2.3 Common Information Model The CIM Agent provides a means by which a device can be managed by common building blocks rather than proprietary software. If a device is CIM-compliant, software that is also CIM-compliant can manage the device. Vendor applications can benefit from adopting the common information model because they can manage CIM-compliant devices in a common way, rather than using device-specific programming interfaces. Using CIM, you can perform tasks in a consistent manner across devices and vendors. CIM uses schemas as a kind of class library to define objects and methods. The schemas can be categorized into three types: Core schema define classes and relationships of objects. Common schema define common components of systems. Extension schema are the entry point for vendors to implement their own schema. The CIM/WBEM architecture defines the following elements: Agent code or CIM Agent An open-systems standard that interprets CIM requests and responses as they transfer between the client application and the device. The Agent is embedded into a device, which can be hardware or software. CIM Object Manager The common conceptual framework for data management that receives, validates, and authenticates the CIM requests from the client application. It then directs the requests to the appropriate component or a device provider such as a CIM Agent. Client application or CIM Client A storage management program, such as TotalStorage Productivity Center, that initiates CIM requests to the CIM Agent for the device. A CIM Client can reside anywhere in the network, because it uses HTTP to talk to CIM Object Managers and Agents. Device or CIM Managed Object A Managed Object is a hardware or software component that can be managed by a management application by using CIM, for example, a IBM SAN Volume Controller. Device provider A device-specific handler that serves as a plug-in for the CIMOM. That is, the CIMOM uses the handler to interface with the device. Note: The terms CIM Agent and CIMOM are often used interchangeably. At this time, few devices come with an integrated CIM Agent. Most devices need a external CIMOM for CIM to enable management applications (CIM Clients) to talk to the device. For ease of installation, IBM provides an Integrated Configuration Agent Technology (ICAT), which is a bundle that includes the CIMOM, the device provider, and an SLP SA. Integrating existing devices into the CIM model Because these standards are still evolving, we cannot expect that all devices will support the native CIM interface. As a result, the SMI-S is introducing CIM Agents and CIM Object Managers. The agents and object managers bridge proprietary device management to device management models and protocols used by SMI-S. The agent is used for one device and an object manager for a set of devices. This type of operation is also called proxy model and is shown in Figure 2-8 on page 29.28 IBM TotalStorage Productivity Center: The Next Generation
    • The CIM Agent or CIMOM translates a proprietary management interface to the CIMinterface. The CIM Agent for the IBM TotalStorage ESS includes a CIMOM inside it.In the future, more and more devices will be native CIM compliant, and will therefore have abuilt-in Agent as shown in the Embedded Model in Figure 2-8. When widely adopted, SMI-Swill streamline the way that the entire storage industry deals with management. Managementapplication developers will no longer be required to integrate incompatible feature-poorinterfaces into their products. Component developers will no longer be required to push theirunique interface functionality to application developers. Instead, both will be better able toconcentrate on developing features and functions that have value to end-users. Ultimately,faced with reduced costs for management, end-users will be able to adoptstorage-networking technology faster and build larger, more powerful networks. CIM Client Management Application 0..n CIMxml CIM operations over http [TCP/IP] Agent Object Manager 0..n Provider 0..n 1 Proprietary 1 1 n Proprietary Agent Device or Device or Subsystem Device or Subsystem 0..n Subsystem Proxy Model Embedded Model Proxy ModelFigure 2-8 CIM Agent and Object Manager overviewCIM Agent implementationWhen a CIM Agent implementation is available for a supported device, the device can beaccessed and configured by management applications using industry-standardXML-over-HTTP transactions. This interface enables IBM TotalStorage Productivity Centerfor Data, IBM TotalStorage Productivity Center for Disk, IBM TotalStorage Productivity Centerfor Replication, IBM Director and vendor tools to manage the SAN infrastructure moreeffectively.By implementing a standard interface over all devices, an open environment is created inwhich tools from a variety of vendors can work together. This reduces the cost of developingintegrated management applications, installing and configuring management applications,and managing the SAN infrastructure. Figure 2-9 on page 30 shows an overview of the CIMAgent. Chapter 2. Key concepts 29
    • Figure 2-9 CIM Agent overview The CIM Agent includes a CIMOM, which adapts various devices using a plug-in called a provider. The CIM Agent can work as a proxy or can be embedded in storage devices. When the CIM Agent is installed as a proxy, the IBM CIM Agent can be installed on the same server that supports the device user interface. CIM Object Manager The SNIA SMI-S standard designates that either a proxy or an embedded agent may be used to implement CIM. In each case, the CIM objects are supported by a CIM Object Manager. External applications communicate with CIM through HTTP to exchange XML messages that are used to configure and manage the device. In a proxy configuration, the CIMOM runs outside of the device and can manage multiple devices. In this case, a provider component is installed into the CIMOM to enable the CIMOM to manage specific devices such as the ESS or SAN Volume Controller. The providers adapt the CIMOM to work with different devices and subsystems. In this way, a single CIMOM installation can be used to access more than one device type and more than one device of each type on a subsystem. The CIMOM acts as a catcher for requests that are sent from storage management applications. The interactions between the catcher and sender use the language and models defined by the SMI-S standard. This enables storage management applications, regardless of vendor, to query status and perform command and control using XML-based CIM interactions.2.4 Component interaction This section provides an overview of the interactions between the different components by using standardized management methods and protocols.2.4.1 CIMOM discovery with SLP The SMI-S specification introduces SLP as the method for the management applications (the CIM clients) to locate managed objects. SLP is explained in more detail in 2.2, “Service Location Protocol overview” on page 18. Figure 2-10 on page 31 shows the interaction between CIMOMs and SLP components.30 IBM TotalStorage Productivity Center: The Next Generation
    • Lock CIM Client Directory Manager Management Manager Application SA SA UA 0..n DA 0..n 0..n SLP TCP/IP CIMxml CIM operations over http [TCP/IP] SA SA Agent Object Manager 0..n Provider 0..n 1 1 Proprietary SA 1 Proprietary n Agent Device or Device or Subsystem Device or Subsystem 0..n Subsystem Proxy Model Embedded Model Proxy Model Figure 2-10 SMI-S extensions to WBEM/CIM2.4.2 How CIM Agent works The CIM Agent typically works as explained in the following sequence and as shown in Figure 2-11 on page 32: 1. The client application locates the CIMOM by calling an SLP directory service. 2. The CIMOM is invoked. 3. The CIMOM registers itself to the SLP and supplies its location, IP address, port number, and the type of service it provides. 4. With this information, the client application starts to communicate directly with the CIMOM. 5. The client application sends CIM requests to the CIMOM. As requests arrive, the CIMOM validates and authenticates each request. 6. The CIMOM directs the requests to the appropriate functional component of the CIMOM or to a device provider. 7. The provider makes calls to a device-unique programming interface on behalf of the CIMOM to satisfy client application requests. 8. — 10. The client application requests are made. Chapter 2. Key concepts 31
    • Figure 2-11 CIM Agent work flow - graphic must be updated2.5 Tivoli Common Agent Services The Tivoli Common Agent Services is a new concept with the goal to provide a set of functions for the management of agents that will be common to all Tivoli products. See Figure 2-12 on page 33 for an overview of the three elements in the Tivoli Common Agent Services infrastructure. The Agent Manager is the central network element, that together with the distributed Common Agents, builds an infrastructure which is used by other applications to deploy and manage an agent environment. Each application uses a Resource Manager that is built into the application server (Productivity Center for Data or Productivity Center for Fabric) to integrate in this environment. Note: You can have multiple Resource Managers of the same type using a single Agent Manager. This might be necessary to scale the environment when, for example, one Data Manager cannot handle the load related to all the agents. But the individual agents will be managed by only one of the Data Managers.32 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 2-12 Tivoli Common Agent ServicesThe Common Agent provides the platform for the application specific agents. Depending onthe tasks for which a subagent is used, the Common Agent is installed on application servers,desktop PCs, or notebooks. Note: In different documentation, Readme files, directory and file names, you also see the terms Common Endpoint, Endpoint, or simply EP. This always refers to the Common Agent which is part of the Tivoli Common Agent Services.The Common Agent talks to the application specific subagent, with the Agent Manager andthe Resource Manager, but the actual system level functions are invoked by the subagentsee Figure 2-13 on page 34). The information that the subagent collects is sent directly to theResource Manager by using the application’s native protocol. This is enabled to havedown-level agents in the same environment, as the new agents that are shipped with theTotalStorage Productivity Center.Certificates are used to validate if a requester is allowed to establish a communication. Demokeys are supplied to set up and configure a small environment quickly. Because everyinstallation CD uses the same certificates, this is not secure. If you want to use TivoliCommon Agent Services in a production environment, we recommend that you use your ownkeys that can be created during the Tivoli Agent Manager installation.One of the most important certificates is stored in the agentTrust.jks file. The certificate canalso be created during the installation of Tivoli Agent Manager. If you do not use the democertificates, you must have this file available during the installation of the Common Agent andthe Resource Manager.This file is locked with a password (the agent registration password) to secure the access tothe certificates. You can use the ikeyman utility in the javajre subdirectory to verify yourpassword. Chapter 2. Key concepts 33
    • Data Device Server Server Resource Resource Manager Manager Agentmanager RegistrationService IBMCDB Ports: 9511 - registration RecoveryServices 9512 - authentication Holds the 9513 - updates Registration Of all Agents And Ports: Resource 80 – recovery Managers 9513 – alternate for recovery SubAgent SubAgent Data Fabric CommonAgent Application Server with Agent Figure 2-13 Schematic diagram of Agent Manager and its services In this picture you can see a simplified diagram showing the two most important services the Agent Manager provides. Also shown are the ports which are used for these services. A more detailed list of all the ports and their relationship can be found in the Installation and Configuration Guide.2.5.1 Tivoli Agent Manager :Using the Tivoli Agent Manager requires two conditions to be met before installing it: a database to store information in the registry The only options for installing the database is using a local DB2 database or a remote DB2 database. WebSphere Application Server This is installed as an integral part of the IBM TotalStorage Productivity Center installation. We recommend that you do not install WebSphere Application Server manually. Three dedicated ports are used by the Agent Manager (9511-9513). Port 9511 is the most important port because you have to enter this port during the installation of a Resource Manager or Common Agent, if you choose to change the defaults. Attention: When the Tivoli Agent Manager is being installed, make sure that the Microsoft Internet Information Server (IIS) is not running, or, even better, that it is not installed. Port 80 is used by the Tivoli Agent Manager for the recovery of agents that can no longer communicate with the manager, because of lost passwords or certificates. This Agent34 IBM TotalStorage Productivity Center: The Next Generation
    • Recovery Service is located by a DNS entry with the unqualified host name of TivoliAgentRecovery. During the installation, you also have to specify the agent registration password and the Agent Registration Context Root. The password is stored in the AgentManager.properties file on the Tivoli Agent Manager. This password is also used to lock the agentTrust.jks certificate file. Important: A detailed description about how to change the password is available in the corresponding Resource Manager Planning and Installation Guide. Because this involves redistributing the agentTrust.jks files to all Common Agents, we encourage you to use your own certificates from the beginning. To control the access from the Resource Manager to the Common Agent, certificates are used to make sure that only an authorized Resource Manager can install and run code on a computer system. This certificate is stored in the agentTrust.jks and locked with the agent registration password.2.5.2 Common Agent As mentioned earlier, the Common Agent is used as a platform for application specific agents. These agents sometimes are called subagents. The subagents can be installed using two different methods: Using an application specific installer From a central location once the Common Agent is installed When you install the software, the agent has to register with the Tivoli Agent Manager. During this procedure, you must specify the registration port on the manager (by default 9511). Additionally, you must specify an agent registration password. This registration is performed by the Common Agent, which is installed automatically if not already installed. If the subagent is deployed from a central location, the port 9510 is by default used by the installer (running on the central machine), to communicate with the Common Agent to download and install the code. When this method is used, no password or certificate is required, because these were already provided during the Common Agent installation on the server. If you choose to use your own certificate during the Tivoli Agent Manager installation, you must supply it for the Common Agent installation.2.6 Communication in TotalStorage Productivity Center This section describes the communication methods used by the TotalStorage Productivity Center components. IBM TotalStorage Productivity Center for Disk IBM TotalStorage Productivity Center for Disk uses the Storage Management Initiative - Specification (SMI-S) standard ( “Storage Management Initiative - Specification” on page 16) to collect information about subsystems. For devices that are not CIM ready, this requires the installation of a proxy application (CIM Agent or CIM Object Manager (CIMOM)). It does not use its own agent as the Data Manager and Fabric Manager do. Chapter 2. Key concepts 35
    • IBM TotalStorage Productivity Center for Fabric IBM TotalStorage Productivity Center for Fabric uses mainly two methods to collect information: Inband and Outband discovery. You can use either method or you can use both at the same time to obtain the most complete picture of your environment. Using just one of the methods will give you incomplete information, but topology information will be available in both cases. With some vendors and their specific devices, you can even have a third path of collecting data, for example the Switch API for Brocade SAN Switches. Outband discovery is the process of discovering SAN information, including topology and device data, without using the Fibre Channel data paths. Outband discovery uses SNMP queries, invoked over IP network. Outband management and discovery is used normally to manage devices such as switches and hubs which support SNMP. Inband discovery is the process of discovering information about the SAN, including topology and attribute data, through the Fibre Channel data paths. Inband discovery uses the following general process: The Agent sends commands through its Host Bus Adapters (HBA) and the Fibre Channel network to gather information about the switches. The switch returns the information through the Fibre Channel network and the HBA to the Agent. The Agent queries the endpoint devices using RNID and SCSI protocols. The Agent returns the information to the Manager over the IP network. The Manager then responds to the new information by updating the database and redrawing the topology map if necessary. IBM TotalStorage Productivity Center for Data Within the IBM TotalStorage Productivity Center, the data manager is used to collect information about logical drives, file systems, individual files, database usage and more. Agents are installed on the application servers and perform a regular scan to report back the information. To report on a subsystem level, a SMI-S interface is also built in. This information is correlated with the data that is gathered from the agents to show the LUNs that a host is using (an agent must be installed on that host). This correlation is done in the TotalStorage Productivity Center database. In contrast to Productivity Center for Disk and Productivity Center for Replication, the SMI-S interface in Productivity Center for Data is only used to retrieve information, but not to configure a device. Note: The SLP User Agent integrated into the Data Manager uses SLP Directory Agents and Service Agents to find services in a local subnet. To discover CIM Agents from remote networks, they have to be registered to either the Directory Agent or Service Agent which is located in the local subnet unless routers are configured to also route multicast packets. You must add each CIM Agent that is not discovered manually to the Data Manager. Refer to Chapter 7, “CIMOM installation and customization” on page 239.2.7 IBM TotalStorage Productivity Center basics This section reviews the basics of using the TotalStorage Productivity Center.36 IBM TotalStorage Productivity Center: The Next Generation
    • 2.7.1 Collecting data in general IBM TotalStorage Productivity Center uses multiple techniques to collect data from the various subsytems and devices in your environment. Figure 2-14 shows presents these various data paths where data is coming from and passing across TotalStorage Productivity Center. The data paths are: CIM Agents The IBM TotalStorage Productivity Center Data and Fabric Agents SNMP Traps and Events StorageManagement Interface-Specification (SMI-S) queries API calls through vendor specific product APIs CI M TPC Ag e n t f o r Di s k Storage and Tape Topology Viewer Subsystems TPC cent r al Data Agent Fabric Agent TPC f o r Da t a DB Computers Proprietary SNMP TPC API f or Fabr i c SAN Components Figure 2-14 Data paths within the TotalStorage Productivity Center environment These data paths can be used on demand to collect data. In this case the queries are triggered by manual interaction with the system. But in general you will setup your TotalStorage Productivity Center environment to perform data collection at intervals you define. Each time when these jobs are run, another record of information is stored in the associated database tables. The continuously gathered information is the basis for all reports, statistics, performance charts and other reports that can be produced with TotalStorage Productivity Center. The frequency of this data collection is a critical factor for the timeliness of the data which is displayed in other elements of the GUI. This brings up the crucial fact, that elements that are shown in the explorer - the elements you might want to perform a specific action on - might be missing until you go out for the next data collection and update the database contents. The behavior of the Topology Viewer is to look up the information in the database instead of collecting it from the managed systems. The principle with updating the database contents is that only the scheduled jobs, scans, or probes will update the information. Chapter 2. Key concepts 37
    • There are only two exceptions: A subsystem can issue an indication to its associated CIM Agent to have it update a specific information in the database (for example, the addition of a newly created LUN). A device managed through SNMP ( for example, a switch) can send a trap indicating there was a change to which TotalStorage Productivity Center should be notified. In this version of the product, the information is stored in a single database. There is a second database for Tivoli Agent Manager which is described this later in the book. Data correlation within IBM TotalStorage Productivity Center The design of the database and its tables are the basis for the information you can derive from IBM TotalStorage Productivity Center. The logical relation - in terms of how a storage infrastructure is functioning - between single entries in the database makes it possible to tell t the condition and state of the subsystems and its counterparts to the left and to the right. Startup of the main user interface After installation of the product the user will be presented with the main GUI. The GUI holds several containers which are filled up with items related to the following tasks. The next paragraph tries to explain these tasks in brief fashion. Later in this redbook more details are provided.Figure 2-15 The main GUI window38 IBM TotalStorage Productivity Center: The Next Generation
    • DiscoveryDiscovery is the first task to be performed, after the infrastructure is completely rolled out.Discovery is the process of using the established datapaths to see which devices are outthere. Discovery is about seeing if you can reach all your installed storage subsystems.The discovery should be repeated after you have installed new resources in yourenvironment. For a successful recovery there are involved several protocols and standardswhich are explained later in this chapter. To name only a few of them you have to have aproperly setup the IP, SLP, SNMP infrastructure so that protocols like SLP, WBEM andSMI-S can find your hardware devices. The following table gives an overview of the varioustypes of discovery. Type of discovery Data source Top-level entities CIMOM CIMOM Fabric ( switches ) Storage subsystems Tape subsystems Out-of-band SNMP agents on the Fabric ( switches). A fabric switches discovery gets all the fabric information. NetWare Filer NetWare agent NetWare trees Windows domain,NAS, Data agent Computers and SAN FS Files Clusters Names or agentsProbingProbing is the process of gathering more detailed information from within the subsystemswhich have been discovered before. The goal is to get statistic and asset information aboutcomponents such as disk controllers, hard disks, clusters, fabrics, storage subsystems,LUNs, and so forth. When you perform your probes on a regular basis you can becomeaware of any changes in your environment. such as the addition or deletion of LUNs on astorage subsystem.ReportingWithin IBM TotalStorage Productivity Center there are several reporting categories.Predefined are some dozens of reports in the area of Data,Disk and Fabric. A user can defineits own reports. He can export the reports to formats like CSV,HTML,PDF and others. Thescope of these reports can be like: Asset Reporting Availability Reporting Capacity Reporting Usage Reporting Usage Violation Reporting Backup ReportingIn addition to the predefined reports the user can define and customize its own reports.Important to understand is the principle, that every report - a user can define as its own report- is based on the standard definitions which are built in the predefined reports. That meansthey inherit most of their definitions, but every aspect can be changed. Each user definedreport can be scheduled to run on a regular base. Chapter 2. Key concepts 39
    • Another important concept in IBM TotalStorage Productivity Center in the context of Reporting is the Grouping-Concept. The administrator can define his reports, his monitoring jobs, his schedules scans in that way, that they are running against pre,-or self-defined groups. A group is a collection of entities of the same type. The concept of grouping can be found at several other areas within IBM TotalStorage Productivity Center. Monitoring Monitoring can be broken up into three main tasks. They are, depending on which area of TPC on which you are working: Pings They are the simplest way to test the connectivity to its devices. Scans They are used, for example, for collecting data from filesystems on a computer/ Probes They are the most intensive queries to collect data from subsystems. Profiles Profiles are a means to control what the contents of your scan should be. There are a lot of predefined profiles which can be modified, but you can create your own. Alerting Each of the functions in IBM TotalStorage Productivity Center can be described as active, meaning they are directly interacting with the storage devices, computer or the SAN devices, you as the administrator are able to define what kind of actions should be performed to raise an alarm. The possibilities vary from plain logging, SNMP, e-mail to issuing an TEC Event, and even others. Policy Management Within the widespread capabilities you can achieve with Policies are things like Quota definitions Definition of which file type, sizes and so forth are acceptable (constraint definitions) Automation of Backup/Archive operation on identified files Filesystem Extension on filesystems exceeding the specifications2.7.2 Role-based Administration The role-based Administration is implemented to have the different tasks within IBM TotalStorage Productivity Center assigned to different groups or people in your company. IBM TotalStorage Productivity Center has its own, strictly defined set of roles which you have to map with groups which are established on the operating system side of your server. Table 2-1 lists the different roles and their level of authorization.Table 2-1 Role Base Administration: Roles versus level of authorization Role Authorization level Superuser Has full access to all IBM TotalStorage Productivity Center functions Productivity Center Administrator Has full access to operations in the Administration section of the GUI. Disk Administrator Has full access to IBM TotalStorage Productivity Center disk functions Disk Operator Has access to reports only for IBM TotalStorage Productivity Center disk functions. This includes reports on tape devices. Fabric Administrator Has full access to IBM TotalStorage Productivity Center for Fabric functions40 IBM TotalStorage Productivity Center: The Next Generation
    • Role Authorization level Fabric Operator Has access to reports only for IBM TotalStorage Productivity Center for Fabric functions. Data Administrator Has full access to IBM TotalStorage Productivity Center for Data functions Data Operator Has access to reports only for Data functions. 1. The following is an example of role mappings. In the TPC GUI you must navigate to the Role-to-Group-Mappings view, as shown in Table 2-1 on page 40.Figure 2-16 Role-to-Group Mappings Dialog In this panel we see an entry for each of the roles listed in the table above. The administrator has to group the user entities into specific groups within the operating system where the TPC server is running. 2. Navigate to your Windows User Administration and create the groups and populate them with the users you want to have in these groups. Table 2-17 on page 42 gives an example of how inputting these groups looks. The other possible platforms use their own tools to administer the users and groups, but the process is the same. Chapter 2. Key concepts 41
    • Figure 2-17 Windows User and Group Administration 3. The group name you used here is to be entered in the Role-to-Group Mappings view, shown in Figure 2-18. Figure 2-18 Edit the Group name for the Data Operators sample42 IBM TotalStorage Productivity Center: The Next Generation
    • 3 Chapter 3. Installation planning and considerations IBM TotalStorage Productivity Center is made up of several products which can be installed individually, as a complete suite, or any combination in between. By installing multiple products, a synergy is created, allowing the products to interact with each other to provide a more complete solution to help you meet your business storage management objectives. This chapter contains information that you will need to gather before beginning the installation. It also discusses the supported environments and preinstallation tasks.© Copyright IBM Corp. 2006. All rights reserved. 43
    • 3.1 Configuration You can install the components of IBM TotalStorage Productivity Center on a variety of platforms. However, for the IBM TotalStorage Productivity Center suite, when all components are installed on the same system, the only common platforms for the managers are: AIX 5.3 Red Hat Enterprise Linux v3.0 (Intel® only) Windows 2003 Server Windows 2003 Enterprise Server Note: Refer to the following Web site for the updated support summaries, including specific software, hardware, and firmware levels supported: http://www.storage.ibm.com/software/index.html3.2 Installation prerequisites This section lists the minimum prerequisites for installing IBM TotalStorage Productivity Center.3.2.1 Hardware The following hardware is required: For all servers: – Network connectivity – Subsystem Device Driver (SDD), for IBM TotalStorage Productivity Center for Disk (optional) – Up to 80 GB of free space for databases For Intel servers running Microsoft Windows 2003 Server or Microsoft Windows 2003 Enterprise Server: – Dual Pentium® 4 or Intel Xeon® 2.4 GHz or faster processors – 4 GB of DRAM – 4 GB of available disk space For Intel servers running Red Hat Enterprise Linux v3.0: – Dual Pentium 4 or Intel Xeon 2.4 GHz or faster processors – 4 GB of DRAM – 4 GB of available disk space – 500 MB free space in /tmp – 1.3 GB free space in /opt For IBM pSeries® servers: – 1 GHz or faster processor – 4 GB DRAM – 500 MB free space in /tmp – 1.3 GB free space in /opt44 IBM TotalStorage Productivity Center: The Next Generation
    • 3.2.2 Database This section describes the database requirements. As we write this section, we referenced the following Web site: http://www-1.ibm.com/support/docview.wss?rs=1133&uid=ssg1S1002813 For the Agent Manager Repository: – IBM DB2 UDB v8.2 with FixPak 7a (or higher) is supported for local and remote installation For the IBM TotalStorage Productivity Center Server repository – IBM DB2 UDB v8.2 with Fixpak 7a (or higher) is supported: The Data Agent can monitor these databases: • IBM DB2 UDB v7.2, 8.1, and 8.2 • Microsoft SQL Server 7.0, 2000, and 7.0 2000 • Oracle 8i, 9i, and 10g • Sybase Note: We recommend using IBM DB2 UDB V8.2 with Fixpak 7a (or higher) as the single repository for the Agent Manager as well as the TotalStorage Productivity Center. Default databases created during the installation In TotalStorage Productivity Center V3.1, there are only two default databases created during the installation process. These databases are named IBMCDB (for the Agent Manager repository) and TPCDB (for the TotalStorage Productivity Center Server repository). It is possible to use only one database, IBMCDB, for both repositories, but this configuration is not recommended. Note: For a description of our ITSO TotalStorage Productivity Center lab environment ,refer to 8.1, “Infrastructure summary” on page 340.3.3 Preinstallation check list You must complete the following tasks before installing the TotalStorage Productivity Center. 1. Print the tables in Appendix A, “Worksheets” on page 519, to keep track of the information you will need during the installation, such as user names, ports, IP addresses, and locations of servers and managed devices. 2. Determine which elements of the TotalStorage Productivity Center you will install. 3. For installations in a Windows environment, either disable or uninstall Internet Information Services (if it is already installed) from the servers on which the Agent Manager and TotalStorage Productivity Center Server software will be installed. In our environment, we uninstalled IIS. For detailed information, refer to 4.5.3, “Internet Information Services” on page 65. 4. Grant the following privileges to the Windows user account that will be used to install the TotalStorage Productivity Center: – Act as part of the operating system – Create a token object – Adjust memory quotas for a process – Replace a process-level token – Logon as a service Chapter 3. Installation planning and considerations 45
    • 5. Identify any firewalls and obtain the required authorization to pass network traffic through them. 6. Obtain the static IP addresses that will be used for the TotalStorage Productivity Center servers.3.3.1 TCP/IP ports used Table 3-1 lists the TCP/IP ports used by the Agent Manager component. You can change any of the port numbers except for port 80, which is used by the agent recovery service. If there is a firewall between the Agent Manager and the agents and resource managers in your deployment, you must open the Agent Manager ports for inbound TCP traffic to the Agent Manager. Table 3-1 TCP/IP ports used by the Agent Manager Port Use Connection security 9511 Registering agents. Secure SSL Registering resource manager 9512 Providing configuration updates Secure SSL with client Renewing and revoking authentication certificates Querying the registry for agent information Requesting ID resets 9513 Requesting updates to the This is a public port and is certificate revocation list insecure Requesting Agent Manager information Downloading the truststore file Alternate port for the agent recovery service 80 Recovery Service (optional) Insecure Table 3-2 lists the ports for the different components of IBM TotalStorage Productivity Center.Table 3-2 TCP/IP ports used by IBM TotalStorage Productivity Center Component session initiator Inbound / Firewall Inbound / Session (server Outbound port Outbound initiator perspective) (server (agent (agent perspective) perspective) perspecti ve) Data server Both 9549 Device server Both 9550 Common Agent Yes Outbound 9510 Inbound No Agent Manager No Inbound 9511 Outbound Yes Agent Manager Yes Both 9512 Both Yes Agent Manager No Inbound 9513 Outbound Yes46 IBM TotalStorage Productivity Center: The Next Generation
    • Component session initiator Inbound / Firewall Inbound / Session (server Outbound port Outbound initiator perspective) (server (agent (agent perspective) perspective) perspecti ve)Common Agent 9514 Local to server(no accessneeded)Common Agent 9515 Local to server(no accessneeded)Agent Manager No Inbound 80 Outbound YesRecovery ServicePUSH UNIX® Yes Outbound SSH(22) Both NoPUSH Yes Outbound NetBIOSWINDOWS sessions service (139)PUSH UNIX Yes Outbound RSH (514) Both NoPUSH UNIX Yes Outbound REXEC Both No (512)PUSH UNIX Yes Inbound 601PUSH ALL Yes Inbound High ports Both No 3000+PUSH ALL Yes Inbound TPCD Server 2078SLP Both 427SNMP Listener Inbound 162Port You can find the port numbers used on your system by running the netstat -a or netstat -ano commands (to see the PID using that port, too), as shown in Figure 3-1 on page 48 and Figure 3-2 on page 49. Chapter 3. Installation planning and considerations 47
    • Figure 3-1 netstat -a sample48 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 3-2 netstat -ano sample3.4 User IDs and security This section discusses the user IDs that are used during the installation and those that are used to manage and work with TotalStorage Productivity Center. It also explains how you can increase the basic security of the different components. Chapter 3. Installation planning and considerations 49
    • 3.4.1 User IDs This section lists and explains the user IDs used in a IBM TotalStorage Productivity Center environment. Granting privileges Grant privileges to the user ID used to install the IBM TotalStorage Productivity Center for Data, IBM TotalStorage Productivity Center for Disk, and the IBM TotalStorage Productivity Center for Fabric. These user rights are governed by the local security policy and are not initially set as the defaults for administrators. They might not be in effect when you log on as the local administrator. If the TotalStorage Productivity Center installation program does not detect the required user rights for the logged on user name, the program can set them optionally. The program can set the local security policy settings to assign these user rights. Alternatively, you can set them manually prior to performing the installation. To set these privileges manually, follow these steps: 1. Click Start → Settings → Control Panel. 2. Double-click Administrative Tools. 3. Double-click Local Security Policy. 4. The Local Security Settings window opens. Expand Local Policies. Then double-click User Rights Assignments to see the policies in effect on your system. For each policy added to the user, perform the following steps: a. Highlight the policy to be selected. b. Double-click the policy and look for the user’s name in the Assigned To column of the Local Security Policy Setting window to verify the policy setting. Ensure that the Local Policy Setting and the Effective Policy Setting options are selected. c. If the user name does not appear in the list for the policy, you must add the policy to the user. Perform the following steps to add the user to the list: i. In the Local Security Policy Setting window, click Add. ii. In the Select Users or Groups window, under the Name column, highlight the user of group. iii. Click Add to place the name in the lower window. iv. Click OK to add the policy to the user or group. 5. After you set these user rights, either by using the installation program or manually, log off the system and then log on again for the user rights to take effect. 6. Restart the installation program to continue with the TotalStorage Productivity Center installation.3.4.2 Increasing user security The goal of increasing security is to have multiple roles available for the various tasks that can be performed. Each role is associated with a certain group. The users are only added to those groups that they need to be part of to fulfill their work. Not all components have the possibility to increase the security. Others methods require some degree of knowledge about the specific components to perform the configuration successfully.50 IBM TotalStorage Productivity Center: The Next Generation
    • Microsoft Windows domain If you are installing the TotalStorage Productivity Center in a Microsoft Windows environment, it does not support the following Microsoft Windows domain login formats for logging into the server component: (domain name)/(username) (username)@(domain) Because TotalStorage Productivity Center does not support these formats, you must set up users in a domain account that can log into the server. Perform the following steps before you install Productivity Center for Data in your environment: 1. Create a Local Admin Group. 2. Create a Domain Global Group. 3. Add the Domain Global Group to the Local Admin Group. Productivity Center for Data looks up the SID for the domain user when the login occurs. You only need to specify a user name and password.3.4.3 Certificates and key files A TotalStorage Productivity Center environment uses certificates to ensure a high level of security. The security certificates can be generated during the installation of the Agent Manager component. During the installation, key files can be generated as self-signed certificates, but you must enter a password for each file to lock it. Although you can leave the password for the Certificate Authority file blank, we do not recommend it. If you leave this password blank, a random password will be generated for you during the install process and you will then be unable to unlock the Certificate Authority file. We therefore recommend that you enter a password for this file, which will allow you to unlock the Certificate Authority file later, if needed. The default file names are: CARootKeyRing.jks (the Certificate Authority file) agentTrust.jks (the Common Agent registration file) The default directory for the key file on the Agent Manager in a Windows environment is C:Program FilesIBMAgentManagercerts. In a UNIX or LINUX environment, the default directory is /opt/IBM/AgentManager/certs. Agent Manager certificates The Agent Manager comes with demonstration certificates that you can use. However, you can also create new certificates during the installation of Agent Manager (see Figure 4-37 on page 88). If you choose to create new files, the password that you enter on the panel, as shown in Figure 4-38 on page 89, as the Agent registration password is used to lock the agentTrust.jks key file. The default directory for that key file on the Agent Manager is C:Program FilesIBMAgentManagercerts. There are more key files in that directory, but during the installation and first steps, the agentTrust.jks file is the most important one. This is only important if you allow the installer to create your keys, which is recommended.3.4.4 Services and service accounts The managers and components that belong to the TotalStorage Productivity Center are started as Windows Services. Table 3-3 on page 52 provides an overview of the most important services. To keep it simple, we did not include all the DB2 services in the table. Chapter 3. Installation planning and considerations 51
    • Table 3-3 Services and service accounts Element Service name Service account Comment DB2 db2admin The account needs to be part of Administrators and DB2ADMNS. Agent Manager IBM WebSphere® LocalSystem You need to set this service to start Application Server V5 — automatically, after the installation. Tivoli Agent Manager Common Agent IBM Tivoli Common Agent — itcauser C:Program Filestivoliep Productivity Center IBM TotalStorage Productivity TSRMsrv1 for Data Center for Data server Productivity Center IBM WebSphere Application LocalSystem for Fabric Server V5 — Fabric Manager3.5 Starting and stopping the managers To start, stop or restart one of the managers or components, you use the Windows control panel. Table 3-4 shows a list of the services.Table 3-4 Services used for TotalStorage Productivity Center Element Service name Service account DB2 Note that there are several services for db2 db2admin Agent Manager IBM WebSphere Application Server V5 - Tivoli Agent Manager LocalSystem Common Agent IBM Tivoli Common Agent — C:Program Filestivolica itcauser Productivity Center for Data IBM TotalStorage Productivity Center Data Server TSRMsrv1 Productivity Center for Fabric IBM WebSphere Application Server V5 - Device Server LocalSystem3.6 Server recommendations The IBM TotalStorage Productivity Center for Data server component acts as a traffic officer for directing information and handling requests from the agent and UI components installed within an environment. You need to install at least one server within your environment. We recommend that you do not manage more than 1000 agents with a single server. If you need to install more than 1000 agents, we suggest that you install an additional server for those agents to maintain optimal performance.52 IBM TotalStorage Productivity Center: The Next Generation
    • 3.7 Supported subsystems, devices, filesystems, databases This section contains the subsystems, tape libraries, file system formats, and databases that the TotalStorage Productivity Center supports.3.7.1 Storage subsystem support IBM TotalStorage Productivity Center V3.1 supports IBM and third-party disk systems that are Storage Management Interface Specification (SMI-S) 1.0.2 or SMI-S 1.1 compatible. This support includes storage provisioning, as well as asset and capacity reporting. TotalStorage Productivity Center V3.1 implements many of its disk, tape, and fabric management functions through exploitation of the SMI-S 1.0.2 and 1.1 levels of the standard. SMI-S 1.1 supports all of the functions of SMI-S 1.0.2 plus additional functionality (for example, performance management). These systems include, but are not limited to: IBM TotalStorage SAN Volume Controller (SVC) IBM TotalStorage Enterprise Storage Server (ESS) IBM TotalStorage Disk Subsystems (DS4000, DS6000, and DS8000 Series)3.7.2 Tape library support IBM TotalStorage Productivity Center 3.1 supports the following tape libraries: IBM 3494 IBM 35843.7.3 File system support Data Manager supports the monitoring and reporting of the following file systems: AIX_JFS AIX_JFS2 AIX_OLD EXT2 EXT3 FAKE FAT FAT32 HP_HFS NF NTFS4 NTFS5 NetWare FAT NetWare NSS REISERFS IBM TotalStorage SAN File System (SFS) TMPFS UFS VERITAS File System (VxFS) WAFL Chapter 3. Installation planning and considerations 53
    • 3.7.4 Network File System support Data Manager currently supports the monitoring and reporting of the following Network File Systems (NFS): IBM TotalStorage SAN File System 1.0 (Version 1 Release 1), from AIX V5.1 (32-bit) and Windows 2000 Server/Advanced Server clients IBM TotalStorage SAN File System 2.1, 2.2 from AIX V5.1 (32-bit), Windows 2000 Server/Advanced Server, Red Hat Enterprise Linux 3.0 Advanced Server, and SUN Solaris™ 9 clients IBM General Parallel File System (GPFS) v2.1, v2.23.7.5 Database support Data Manager currently supports the monitoring of the following relational database management systems (RDBMS): IBM DB2 UDB v7.2, 8.1, and 8.2 Microsoft SQL Server 7.0, 2000, and 7.0 2000 Oracle 8i, 9i, and 10g3.8 Security considerations This section describes the security issues that you must consider when installing Data Manager. Role-based levels of users There are mainly two levels of users within TotalStorage Productivity Center. They are an Operator user and an administrator for each of the specific work areas in IBM TotalStorage Productivity Center ( Data, Fabric, Disk and Tape ). Besides these two roles, there is a general TotalStorage Productivity Center administrator who can work in all four areas as an administrator. On top of that is a so called Superuser. This is the standard user you are working with right after installing the product. The level of these users determine how they can use IBM TotalStorage Productivity Center. Operator users can: – View the data collected by TotalStorage Productivity Center. – Create, generate, and save reports. Administrator users can: – Create, modify, and schedule Pings, Probes, and Scans. – Create, generate, and save reports. – Perform administrative tasks and customize the TotalStorage Productivity Center environment. – Create Groups, Profiles, Quotas, and Constraints. – Set alerts. Important: Security is set up by using the certificates. You can use the demonstration certificates or you can generate new certificates. It is recommended that you generate new certificates when you install the Agent Manager.54 IBM TotalStorage Productivity Center: The Next Generation
    • 4 Chapter 4. TotalStorage Productivity Center installation on Windows 2003 In this chapter we describe the installation of the TotalStorage Productivity Center components and the remote GUI on Microsoft Windows 2003. This includes the installation of the prerequisite components, DB2 and Agent Manager. Of the available installation paths, Typical and Custom, we used the Custom installation for our environment.© Copyright IBM Corp. 2006. All rights reserved. 55
    • 4.1 TotalStorage Productivity Center installation IBM TotalStorage Productivity Center uses an install wizard that guides you through the installation of the TotalStorage Productivity Center servers and agents. Figure 4-1 describes the install of the TotalStorage Productivity Center Standard Edition. The prerequisite components are installed prior to invoking the installation wizard. TPC Version 3 Release 1 TPC Standard A Single Application Edition with modular components Disk Data Fabric Streamlined Installation and Consistent Reporting Capabilities NEW: Storage topology viewer Packaging (Scheduled, Ad-Hoc) NEW: Role based administration Single User Interface Data Export Capabilities - File System, Database, Fabric (html, CSV) NEW: AIX support for TPC server and Storage management NEW: Fabric performance management - Asset, Capacity and Single set of services for consistent administration and NEW: Tape discovery and asset/capacity Performance Reporting operations reporting Single Database Policy Definitions, Correlated host, fabric, storage Event Handling, NEW: Performance Management for information Resource Groups DS4000 TPC Standard Edition for the full suite or orderable separately Figure 4-1 TotalStorage Productivity Center Standard Edition installation IBM TotalStorage Productivity Center provides an integrated storage infrastructure management solution that is designed to allow you to manage every point of your storage infrastructure, between the hosts through the network and fabric through to the physical disks. It can help simplify and automate the management of devices, data, and storage networks. IBM TotalStorage Productivity Center V3.1 offers a simple, easy to install package with management server support added for IBM AIX V5.3, and integrating IBM DB2 as the management server database. The default installation directory is: c:Program FilesIBM... (for Windows) /opt/IBM/...(for Unix and Linux) You can change this path during installation setup. There are two types of installation: typical and custom.4.1.1 Typical installation The Typical installation allows you to install all the components of the TotalStorage Productivity Center on the local server by selecting the options Servers, Agents and Clients. Our recommendation is not to use the Typical installation, because the control of the installation process is much better when you use the Custom installation method.56 IBM TotalStorage Productivity Center: The Next Generation
    • 4.1.2 Custom installation The Custom installation allows you to install each component of the TotalStorage Productivity Center separately and deploy remote Fabric and or Data agents on different computers. This is the installation method we recommend.4.1.3 CD layout and components In this section we describe the contents of the product CDs at the time of writing. The actual layout of your CDs might be different. The purpose of this section is to give you an idea of the CD content. You can install the following components from different CDs: CD1: – OS: Windows, AIX, and Linux RH 3 – Database Schema – Data Server – Device Server – GUI – CLI – Local Data Agent – Local Device Agent – Remote installation of Device Agent CD2: – OS: Windows, AIX, Linux RH 3, Linux Power, Linux s390 (zLinux), Solaris, HP-UX – Local Data Agent – Local Device Agent – Remote installation of Data Agent – Remote installation of Device Agent CD3: – Data upgrade for all platforms For information about the deployment of agents refer to Chapter 6, “Agent deployment” on page 195.4.2 Configuration The TotalStorage Productivity Center components are: Data server Device server Database Agents GUI CLI There are two supported environments, a one-server and a two-server environment. You must install the Data Server and Device Server on one computer. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 57
    • 4.2.1 One-server environment In this environment all the components are installed on one server. DB2 Agent Manager Data Server Device Server CLI GUI4.2.2 Two-server environment In a two server environment, you would install the components as follows. Note that you can have DB2 on a remote server. Server 1 – DB2 – Agent Manager Server 2 – DB2 – Data Server – Device Server – GUI – CLI4.3 Hardware prerequisites This section lists the minimum hardware prerequisites. In the ITSO we installed all TotalStorage Productivity Center components on a single computer. For other possible configurations, refer to 4.2, “Configuration” on page 57.4.3.1 Hardware For Windows and Linux on Intel, IBM eServer™ xSeries server or other Intel technology-compatible platforms the hardware requirements are: Dual Pentium 4 or Xeon 2.4 GHz or faster processors 4 GB of RAM Network connectivity For AIX on IBM eServer iSeries™ and IBM eServer pSeries: Machine - Minimum 1.0 GHz processor 4 GB of RAM Network connectivity4.3.2 Disk space For Windows, you need 4 GB of available disk space for the code and up to approximately 80 GB of hard disk space for databases. For Unix or Linux, you need 500 MB in /tmp and 1.3 GB in /opt and up to approximately 80 GB of hard disk space for databases.58 IBM TotalStorage Productivity Center: The Next Generation
    • 4.4 Software prerequisites Table 4-1 shows the platform supported by TotalStorage Productivity Center for server components. Table 4-1 Platform support for Data server, Device server, GUI and Agent Manager Platform Data server, Device GUI Agent Manager v1.2 server, database (install fix pack 2, schema (DB2), CLI even if you can optionally use the Agent Manager you installed with v2.3) Windows 2000 NO NO YES Advanced Server Windows 2000 NO NO NO Datacenter Windows Server® YES YES YES 2003 Standard Edition 32-bit or 64-bit Windows Server 2003 YES YES YES Enterprise Edition 32-bit or 64-bit Red Hat Enterprise YES YES YES Linux AS Version 3.0 IBM eServer xSeries Red Hat Enterprise NO NO NO Linux AS Version 3.0 IBM eServer pSeries on POWER5™ Red Hat Enterprise NO NO NO Linux AS Version 3.0 IBM eServer iSeries on POWER5 United LInux 1.0 IBM NO NO NO eServer xSeries United LInux 1.0 IBM NO NO NO eServer zSeries® SUSE LINUX NO NO NO Enterprise Server 8 IBM eServer pSeries on POWER4™ zSeries Chapter 4. TotalStorage Productivity Center installation on Windows 2003 59
    • Platform Data server, Device GUI Agent Manager v1.2 server, database (install fix pack 2, schema (DB2), CLI even if you can optionally use the Agent Manager you installed with v2.3) SUSE LINUX NO NO NO Enterprise Server 9 IBM eServer xSeries, pSeries on POWER5 iSeries on POWER5 zseries (Data agent only) IBM AIX 5.1 (32-bit) NO NO YES IBM AIX 5.1 (64-bit) NO NO YES IBM AIX 5L™ (32-bit) NO NO YES IBM AIX 5L (64-bit) NO NO YES IBM AIX 5.2 (32-bit) NO NO YES IBM AIX 5.2 (64-bit) NO NO YES IBM AIX 5.3 (32 bit) YES YES YES (32- and 64-bit) (with AIX 5300-01 (with AIX 5300-01 maintenance level and maintenance level and APAR IY70336 APAR IY70336 Solaris 8 NO NO YES Solaris 9 NO NO YES HP-UX 11 and 11i NO NO NO Table 4-2 shows the platforms supported to install and deploy Data agents and Fabric agents. Important: Data agents and Fabric agents at the 2.x version are supported by IBM TotalStorage Productivity Center V3.1 managers. Table 4-2 Platform support for Data agent and Fabric agent Platform Data agent and Fabric agent Windows 2000 Advanced Server YES Windows 2000 Datacenter YES Windows Server 2003 Standard Edition YES 32-bit or 64-bit Windows Server 2003 Enterprise Edition YES 32-bit or 64-bit Red Hat Enterprise Linux AS Version 3.0 IBM YES eServer xSeries60 IBM TotalStorage Productivity Center: The Next Generation
    • Platform Data agent and Fabric agent Red Hat Enterprise Linux AS Version 3.0 IBM Only Data agent eServer pSeries on POWER5 Red Hat Enterprise Linux AS Version 3.0 IBM Only Data agent eServer iSeries on POWER5 United LInux 1.0 IBM eServer xSeries Only Data agent United LInux 1.0 IBM eServer zSeries Only Data agent SUSE LINUX Enterprise Server 8 Only Data agent IBM eServer pSeries on POWER4 zSeries SUSE LINUX Enterprise Server 9 Only Data agent IBM eServer xSeries, pSeries on POWER5 iSeries on POWER5 zseries (Data agent only) SUSE LINUX Enterprise Server 9 Data agent (ALL) IBM eServer xSeries, pSeries on POWER5 Fabric agent (xSeries only) iSeries on POWER5 zseries (Data agent only) IBM AIX 5.1 (32-bit) YES with AIX 5100-05 maintenance level IBM AIX 5.1 (64-bit) YES in compatibility mode with AIX 5100-05 maintenance level IBM AIX 5L (32-bit) YES in compatibility mode with AIX 5100-05 maintenance level IBM AIX 5L (64-bit) YES in compatibility mode with AIX 5100-05 maintenance level IBM AIX 5.2 (32-bit) YES with AIX 5200-02 maintenance level IBM AIX 5.2 (64-bit) YES in compatibility mode with AIX 5200-02 maintenance level IBM AIX 5.3 (32 bit) YES with AIX 5300-01 maintenance level and APAR IY70336 Solaris 8 YES Solaris 9 YES HP-UX 11 and 11i Only Data agent4.4.1 Databases supported At time of writing, we used the information contained in the following Web site as a reference: http://www-1.ibm.com/support/docview.wss?rs=1133&uid=ssg1S1002813 Chapter 4. TotalStorage Productivity Center installation on Windows 2003 61
    • The Agent Manager repository is supported only on the following databases. DB2 Enterprise Server Edition version 8.2 with fix pack 7a or higher. There is only one database instance created for IBM TotalStorage Productivity Center on DB2. The default database name for the repository is TPCDB. The Agent Manager repository uses its own database. The default name of this database is IBMCDB. The Data agent can monitor these databases: DB2 7.2 - 32 bit only DB2 8.1 - 32 or 64 bit DB2 8.2 - 32 or 64 bit Microsoft SQL Server 7.0 Microsoft SQL Server 2000 Oracle 8i Oracle 9i Oracle 10g Sybase support is not included in TotalStorage Productivity Center V3.1. Note: We recommend that you install a single instance of IBM DB2 UDB Enterprise Server Edition version 8.2 with fix pack 7a or higher as your repository for both the Agent Manager and IBM TotalStorage Productivity Center.4.5 Preinstallation steps for Windows The prerequisite components for IBM TotalStorage Productivity Center V3.1 are: IBM DB2 UDB Enterprise Server Edition V8.2 fix pack 7a or higher Agent Manager 1.2, 1.2.2 or later (Agent Manager V1.1 is not supported with TotalStorage Productivity Center V3.1) Order of component installation The components are installed in the following order: 1. DB2 2. Data Manager 3. TotalStorage Productivity Center components Tip: We recommend that you install the Database Schema first. After that, install Data Server and Device Server in a separate step. If you install all the components in one step, if any part of the installation fails for any reason (for example space or passwords) the installation suspends and rolls back, uninstalling all the previously installed components.4.5.1 Verify primary domain name systems Before you start your installation, we recommend you verify if a primary domain name system (DNS) suffix is set. This can require a computer restart. To verify the primary DNS name follow these steps: 1. Right-click My Computer on your desktop.62 IBM TotalStorage Productivity Center: The Next Generation
    • 2. Click Properties. The System Properties panel is displayed as shown in Figure 4-2.3. On the Computer Name tab, click Change.Figure 4-2 system properties4. Enter the host name in the Computer name field. Click More to continue (see Figure 4-3).Figure 4-3 computer name5. In the next panel, verify that Primary DNS suffix field displays a domain name. Click OK (see Figure 4-4 on page 64). Chapter 4. TotalStorage Productivity Center installation on Windows 2003 63
    • Figure 4-4 DNS domain name 6. If you made any changes, you might need to restart your computer (see Figure 4-5). Figure 4-5 you must restart4.5.2 Activate NetBIOS settings If NetBIOS is not enabled on Microsoft Windows 2003, then GUID is not generated. You must verify and activate NetBIOS settings. On your TotalStorage Productivity Center Server, go to Start → Settings → Network and Dial-up Connections. Select your Local Area Connections. From the Local Area Connection Properties panel, double-click Internet Protocol (TCP/IP). The next panel is the Internet Protocol (TCP/IP) Properties. Click Advanced as shown in Figure 4-6. Figure 4-6 TPC/IP properties64 IBM TotalStorage Productivity Center: The Next Generation
    • On the WINS tab, select Enable NetBIOS over TCP/IP and click OK (Figure 4-7). Figure 4-7 Advanced TCP/IP properties4.5.3 Internet Information Services Port 80 is used by Internet Information Services (IIS). Port 80 is also used by the Tivoli Agent Manager for the recovery of agents that can no longer communicate with the manager, because of lost passwords or certificates. If any service is using port 80, then Agent Recovery Service installs, but it does not start. Before beginning the installation of TotalStorage Productivity Center, you must do one of the following: Change the IIS port to something other than 80, for example 8080. Uninstall IIS Disable IIS In our installation, we uninstalled IIS to avoid any port conflicts. It must be reinstalled to use the Web-based GUI (see 4.8, “Configuring the GUI for Web Access under Windows 2003” on page 107). To uninstall IIS, use the following procedure: 1. Click Start → Settings → Control Panel. 2. Click Add/Remove Programs. 3. In the Add or Remove Programs window, click Add/Remove Windows Components. 4. In the Windows Components panel, deselect IIS.4.5.4 Create Windows user ID to install Device server and Data server In order to install Device server and Data server, you must have a Windows User with all the proper required rights. We created a unique user ID, as described in Table 4-5 on page 67. It is a good practice to use the worksheets in Appendix A, “Worksheets” on page 519 to record the user IDs and passwords used during the installation of TotalStorage Productivity Center. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 65
    • 4.5.5 User IDs and password to be used and defined In this section, we describe the user IDs and passwords you need to define or set up during TotalStorage Productivity Center installation. Table 4-3 points you to the appropriate table that contains the user IDs and passwords used during the installation of TotalStorage Productivity Center. Table 4-3 Index to tables describing required user IDs and passwords item table Installing DB2 and Agent Manager Table 4-4 on page 66 Installing Device server or Data server Table 4-5 on page 67 Installing Data agent or Fabric agent Table 4-6 on page 67 DB2 administration server user Table 4-7 on page 68 Certificate authority password Table 4-8 on page 69 Common agent registration Table 4-9 on page 69 Common agent service logon user ID and Table 4-10 on page 70 password Host authentication password Table 4-11 on page 70 NAS filer login user ID and password Table 4-12 on page 70 Resource manager registration user ID and Table 4-13 on page 70 password WebSphere Application Server administrator Table 4-14 on page 71 user ID and password Important: To verify the valid characters you could use for these user IDs and passwords, refer to 11.5, “Valid characters for user ID and passwords” on page 511. Table 4-4 through Table 4-14 on page 71 contain information about the user IDs and passwords used during the installation of the TotalStorage Productivity Center prerequisites and components. Table 4-4 Installing DB2 and Agent Manager item OS description created when used when Installing DB2 All Log on Windows Used to log on and Agent as a local Windows to Manager Administrator install DB2 and Agent Manager group user ID password ITSO’s user ID and password Administr user ID used to used to log on Administrator / ators log on password66 IBM TotalStorage Productivity Center: The Next Generation
    • Table 4-5 Installing Device server or Data server item OS description created when used when Installing All Add user ID to DB2 Has to be created Used to log on Device server or Admin group or assign before starting Windows to Data server the user rights: Device server install Device and - Log on as a service and Data server Data server - Act as part of the installation. operating system - Adjust memory quotas for a process - Create a token object - Debug programs - Replace a process level token. On Linux or Unix give root authority group user ID password ITSO’s user ID and password Administr new user ID used to log new password tpcadmin / ators on Windows used to log on tpcadmin Windows (group Administrators)Table 4-6 Installing Data agent or Fabric agent item OS description created when used when Installing Data All User rights: Has to be created Used to logon agent or fabric - act as part of the before starting Windows to agent operating system Data agent or install Data agent - Log on as a service. Fabric agent or Fabric agent On Linux or Unix, give installation root authority group user ID password ITSO’s user ID and password Administr new user ID used to new password tpcadmin / ators log on Windows used to log on tpcadmin Windows (group Administrators)To install a GUI or CLI you do not need any particular authority or special user ID. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 67
    • Table 4-7 DB2 administration server item OS description created when used when DB2 All Used to run the DB2 Specified when Used by the DB2 administration administration server on DB2 is installed GUI tools to server user your system. Used by perform the DB2 GUI tools to administration perform administration tasks. tasks. See rules below. group user ID password ITSO’s user ID and password new user ID new password db2tpc / db2tpc DB2 user ID and password rules DB2 user IDs and passwords must follow these rules. User IDs cannot be any of the following: UNIX user names and passwords cannot be more than eight characters long. They cannot start with a numeric digit or end with $. Windows 32-bit user IDs and passwords can contain 1 to 20 characters. Group and instance names can contain 1 to 8 characters. User IDs cannot be any of the following: – USERS – ADMINS – GUESTS – PUBLIC – LOCAL User IDs cannot begin with: – IBM – SQL – SYS User IDs cannot include accented characters. UNIX users, groups, and instance names must be lowercase. Windows 32-bit users, groups, or instance names can be any case. DB2 creates a user group with the following administrative rights: Act as a part of an operating system Create a token object Increase quotas Replace a process-level token Log on as a service. Note: Adding the user ID used to install TotalStorage Productivity Center to the DB2 Admin group gives the user ID the necessary administrative rights.68 IBM TotalStorage Productivity Center: The Next Generation
    • Table 4-8 Certificate authority password r item OS description created when used when Certificate All This password locks Specified when authority the you install Agent password CARootKeyRing.jks Manager file. Specifying a value for this password is optional. You need to specify this password only if you want to be able to unlock the certificate authority files. We recommend you create a password. group user ID password ITSO’s user ID and password no default, if not tpctpc specified one is generated automatically Important: Do not change the Agent Registration password under any circumstances. Changing this password will render the certificates unusable.Table 4-9 Common agent registration passwords item OS description created when used when Common agent All This is the Specified when you Used during registration password required install Agent common agent, by the common Manager Data agent and agent to register Fabric agent with the Agent installation Manager group user ID password ITSO’s user ID and password changeMe changeMe (is the default) Chapter 4. TotalStorage Productivity Center installation on Windows 2003 69
    • Table 4-10 Common agent service logon user ID and password item OS description created when used when Common agent Windows This creates a new Specified when service logon service account for the you install Data user ID and common agent to run agent or Fabric password under. agent (only local). group user ID password ITSO’s user ID and password Administra If you do not specify tpcadmin / tors anything, itcauser is tpcadmin created by default Table 4-11 Host authentication password item OS description created when used when Host All Specified when Used when you authentication you install the install Fabric password Device server agent, to communicate with the Device server. group user ID password ITSO’s user ID and password must be provided tpctpc Table 4-12 NAS filer login user ID and password item OS description created when used when NAS filer login Windows Specified when user ID and you run NAS password discovery group user ID password ITSO’s user ID and password Table 4-13 Resource manager registration user ID and password r item OS description created when used when Resource ALL Specified when Used when Device manager you install Device server and Data registration user server and Data server have to ID and password server register to Agent Manager group user ID password ITSO’s user ID and password manager password manager / (by default) (by default) password70 IBM TotalStorage Productivity Center: The Next Generation
    • Table 4-14 WAS Webpshere administrator user ID and password item OS description created when used when WebSphere ALL You may use Specified when Used when Device Application tpcadmin, in order you install Device server has to Server to avoid to create a server communicate with WebSphere new one WebSphere administrator user ID and group user ID password ITSO’s user ID password and password if not provided, it if not provided, it tpcadmin / will be created. will be created. tpcadmin4.6 DB2 install for Windows In this section, we show a typical installation of DB2 8.2. Before beginning the installation, it is important that you log on to your system as a local administrator with Administrator authority for Windows or root authority for UNIX and Linux (see Table 4-4 on page 66). Attention: If you update DB2 from an older version, for example from DB2 7.2 to DB2 8.2, the TotalStorage Productivity Center installer might not recognize the DB2 version. See 11.2, “DB2 installation known issues” on page 511. To begin the installation of DB2, follow these steps: 1. Insert the IBM TotalStorage Productivity Center Prerequisite Software Installer CD into the CD-ROM drive. If Windows autorun is enabled, the installation program should start automatically. If it does not, open Windows Explorer and go to the IBM TotalStorage Productivity Center CD-ROM drive. Go to the DB2 Installation image path and double-click setup.exe. You will see the first panel, as shown in Figure 4-8 on page 72. Select Install Product to proceed with the installation. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 71
    • Figure 4-8 DB2 setup welcome 2. The next panel allows you to select the DB2 product to be installed. Click Next to proceed as shown in Figure 4-9 on page 73.72 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-9 Select product The InstallShield Wizard starts (see Figure 4-10).Figure 4-10 Preparing to install3. The DB2 Setup wizard panel is displayed, as shown in Figure 4-11 on page 74. Click Next to proceed. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 73
    • Figure 4-11 setup wizard 4. You have to read and click I accept the terms in the license agreement (Figure 4-12). Figure 4-12 license agreement 5. To select the installation type, accept the default of Typical and click NEXT to continue (see Figure 4-13 on page 75).74 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-13 Typical installation6. Accept the defaults and proceed with Install DB2 Enterprise Server Edition on this computer (see Figure 4-14). Click NEXT to continue.Figure 4-14 Installation action7. The panel shown in Figure 4-15 on page 76 shows defaults for drive and directory to be used as the installation folder. You can change these or accept the defaults, then click NEXT to continue. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 75
    • Figure 4-15 Installation folder 8. Set the user information for the DB2 Administration Server; choose the domain of this user. If it is a local user, leave the field blank. Type a user name and password of the DB2 user account that you want to create (Figure 4-16 on page 77). You can refer to Table 4-7 on page 68. DB2 creates a user with the following administrative rights: – Act as a part of an operating system. – Create a token object. – Increase quotas. – Replace a process-level token. – Log on as a service.76 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-16 User Information9. Accept the defaults in the panel shown in Figure 4-17, and click Next to continue.Figure 4-17 Administration contact list10.Click OK when the warning window shown in Figure 4-18 on page 78 opens. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 77
    • Figure 4-18 Warning 11.In the Configure DB2 instances panel, accept the default and click Next to continue (see Figure 4-19). Figure 4-19 Configure DB2 instances 12.Accept the defaults, as shown in Figure 4-20 on page 79. Verify that Do not prepare the DB2 tools catalog on this computer is selected. Click Next to continue.78 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-20 Prepare db2 tools catalog13.In the panel shown in Figure 4-21, click Defer the task until after installation is complete and then click Next to continue.Figure 4-21 Health Monitor14.The panel shown in Figure 4-22 on page 80 is presented, click Install to continue. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 79
    • Figure 4-22 Start copying files The DB2 installation proceeds and you see a progress panel similar to the one shown in Figure 4-23. Figure 4-23 installing DB2 Enterprise Server Edition installation progress 15.When the installation completes, click Finish, as shown in Figure 4-24 on page 81.80 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-24 DB2 setup wizard16.If you see the DB2 product updates panel shown in Figure 4-25, click No because you have already verified that your DB2 version is at the latest recommended and supported level for TotalStorage Productivity Center, as mentioned in “Databases supported” on page 61.Figure 4-25 DB2 product tapes17. Click Exit First Steps (Figure 4-26 on page 82) to complete the installation. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 81
    • Figure 4-26 Universal Database First Steps panel Verifying the installation To verify the DB2 installation, check if db2tpc user has been created and included in DB2ADMINS group. Open a Command Prompt window and enter the db2level command to check the version installed as shown in Figure 4-27. Figure 4-27 db2 clplevel 20 Figure 4-28 on page 83 shows the DB2 window services created at the end of the installation.82 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-28 Windows services showing DB2 services4.6.1 Agent Manager installation for Windows This is a typical installation of Agent Manager 1.2.2. When you install the Agent Manager, you will also be installing the Embedded version of IBM WebSphere Application Server - Express, V5.0 (WebSphere Express), without the Administrative console to manage WebSphere itself, that was present in TotalStorage Productivity Center V2.3. 1. To start the Agent Manager installer, run the following program from the EmbeddedInstaller directory (Table 4-15). Table 4-15 EmbeddedInstaller directory commands Operating system Command Java™ error failure alternate command Microsoft Windows setupwin32.exe setupwin32.exe -is:javahome ..jrewindows AIX setupAix.bin setupAix.bin -is:javahome ../ Linux setupLinux.bin setupAix.bin -is:javahome ../ Linux on Power PC® setupLinuxPPC.bin setupLinux.bin -is:javahome ../ Solaris setupSolaris.bin setupLinux.bin -is:javahome ../ Note: Log on with a user ID that has administrative authority on Windows and root authority on UNIX or Linux. 2. The Installation Wizard starts; you see a panel similar to the one in Figure 4-29 on page 84. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 83
    • Figure 4-29 Install wizard panel 3. Select a language and click OK (see Figure 4-30). Figure 4-30 Language selection panel 4. Read and accept the terms of license agreement, select I accept the terms of the license agreement. Click Next to continue (see Figure 4-31). Figure 4-31 License panel 5. Figure 4-32 on page 85 shows the Directory Name for the installation. Click Next to accept the default or click Browse to install to a different directory.84 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-32 Installer directory name6. The Agent Manager Registry information panel is displayed, as shown in Figure 4-33. On this panel specify the type of database, Database Name or Directory and type of Database Connection. You can accept the defaults and click Next to continue.Figure 4-33 Wizard installing Chapter 4. TotalStorage Productivity Center installation on Windows 2003 85
    • 7. In the next panel shown in Figure 4-34, enter the following database information: – Database Software Directory Enter the directory where DB2 is installed on your system. The default directory is: • C:Program FilesIBMSQLLIB (Microsoft Windows) • /opt/IBM/SQLLIB (UNIX or Linux) – Database User Name Record this name also in Table A-4 on page 521. – Database Password Record this password also in the tables in Appendix A, “Worksheets” on page 519. – Host name of the Database Server Record this host name in the tables in Appendix A, “Worksheets” on page 519. – Database Port This port number is required for a remote database. After entering the information, click Next to continue. Figure 4-34 Agent Manager database information 8. Enter the following information in the window in Figure 4-35 on page 87: – Host name Alias or Fully Qualified Host name Review the preinstallation task mentioned in 4.5.1, “Verify primary domain name systems” on page 62. If you specify an IP address, you will see the warning panel shown in Figure 4-36 on page 88. – Application Server Name for Agent Manager Accept the default name or enter a different name.86 IBM TotalStorage Productivity Center: The Next Generation
    • – Registration port The default port is 9511 for the server-side SSL. Refer to 3.3.1, “TCP/IP ports used” on page 46. – Secure port The default port is 9512 for client authentication, two-way SSL. Refer to 3.3.1, “TCP/IP ports used” on page 46. – Public Port and Secondary Port for the Agent Recovery Service The public communication port default is 9513. Refer to 3.3.1, “TCP/IP ports used” on page 46. – Do not use port 80 for the agent recovery service. – Start the Agent Manager after the installation is complete. – Autostart the Agent Manager each time the system restarts. It is recommended that you select both Start agent manger and Autostart the agent manager. To check for other applications which are using port 80, run the netstat -an command. Look for port 80 in the listening state. If there is an application using port 80, stop that application and then continue with the installation of Agent Manager. Note: If you want Agent Recovery Service to run, you must stop any service using port 80. If any service is using port 80, Agent Recovery Service installs, but does not start.Figure 4-35 Wizard host name without DO NOT USE port 80 Chapter 4. TotalStorage Productivity Center installation on Windows 2003 87
    • 9. If you specify an IP address instead of a fully qualified host name for the WebSphere Application Server, you see the panel shown in Figure 4-36. We recommend you click the Back button and specify a fully qualified host name. Figure 4-36 Warning IP specified panel 10.In the Security Certificates panel (see Figure 4-37), it is highly recommended that you accept the defaults to generate new certificates for a secure environment. Click Next to continue. Figure 4-37 Create security certificates88 IBM TotalStorage Productivity Center: The Next Generation
    • 11.In the panel shown in Figure 4-38, specify the Security Certificate settings. – To create Certificates, you must specify a Certificate Authority Password. You must specify this password to look at the certificate files after they are generated. Make sure you record this password in the worksheets in Appendix A, “Worksheets” on page 519. – The second password specified in this panel is the Agent Registration password. The default Agent Registration password is changeMe. We recommend you specify a unique password and record it in the worksheets provided in Appendix A, “Worksheets” on page 519. After entering the passwords click Next to continue.Figure 4-38 Certificate password panel12.The User Input Summary panel is displayed (see Figure 4-39 on page 90). If you want to change any settings, click Back and return to the window where you set the value. If you do not need to make any changes, click Next to continue. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 89
    • Figure 4-39 Input summary 13.Review the summary information panel (see Figure 4-40) and click Next to continue. Figure 4-40 Summary info The Agent Manager installation starts and you see several messages similar to those in Figure 4-41 on page 91 and Figure 4-42 on page 91.90 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-41 Installation progress panel Figure 4-42 is the database IBMCDB creation status panel.Figure 4-42 Registry database14.The Summary of Installation and Configuration Results panel is displayed in Figure 4-43 on page 92. Verify that the Agent Manager has successfully installed all of its components. Review the panel and click Next to continue. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 91
    • Figure 4-43 Summary of Agent Manager configuration options summary 15.The last panel (Figure 4-44) shows that the Agent Manager has been successfully installed. Click Finish to complete the Agent Manager installation. Figure 4-44 Finish the Agent Manager install Verifying the installation You can verify the installation by running the healthcheck utility from a command-prompt. From a command prompt, navigate to the directory <InstallDir>Program FilesIBMAgentManagertoolkitbin and run healthcheck.92 IBM TotalStorage Productivity Center: The Next Generation
    • Verify that the ARS.version field shows the level you have installed (in our installation it is1.2.2.2) and that at the end you see the message Health Check passed as shown inFigure 4-45.Figure 4-45 Healthcheck utilityAfter the completion of the Agent Manager installation, you can verify the connection to thedatabase (see Figure 4-46 on page 94). From a command-prompt, enter:db2cmd→ db2→ connect to IBMCDB user db2tpc using db2tpc Chapter 4. TotalStorage Productivity Center installation on Windows 2003 93
    • Figure 4-46 DB2 command line CONNECT4.7 Install TotalStorage Productivity Center components Now that the prerequisites have been installed, we install the TotalStorage Productivity Center components. Before starting the installation, verify that DB2 8.2 Enterprise Edition fix pack 7a has been installed and has been started. Important: Log on to your system as a local administrator with database authority, for Windows. The user ID must have root authority, for Unix or Linux. 1. For Windows, if Windows autorun is enabled, the installation program should start automatically. If it does not, open Windows Explorer and go to the TotalStorage Productivity Center CD–ROM drive or directory. Double-click setup.exe. 2. Chose your language and click OK (see Figure 4-47). Figure 4-47 Language selection panel 3. The License Agreement panel is displayed. Read the terms and select I accept the terms of the license agreement. Then click Next to continue (see Figure 4-48 on page 95).94 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-48 License panel4. Figure 4-49 on page 96 shows how to select typical or custom installation. You have the following options: – Typical installation allows you to install all of the components on the same computer by selecting Servers, Agents and Clients. – Custom installation allows you to install each component separately. – Installation licenses This selection installs the TotalStorage Productivity Center licenses. The TotalStorage Productivity Center license is on the CD. You only need to run this option when you add a license to a TotalStorage Productivity Center package that has already been installed on your system. For example, if you have installed TotalStorage Productivity Center for Data package, the license will be installed automatically when you install the product. If you decide to later enable TotalStorage Productivity Center for Fabric, run the installer and select Installation licenses. This option will allow you to install the license key from the CD. You do not have to install the IBM TotalStorage Productivity Center for Fabric product. In this chapter, we document Custom Installation. Click Next to continue. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 95
    • Figure 4-49 Custom installation 5. In the Custom installation, you can select all the components in the panel shown in Figure 4-50. This is the recommended installation scenario. In our scenario, we show the installation in stages. As the first step, we select the option to Create database schema. and click Next to proceed (see Figure 4-50). Figure 4-50 Custom installation component selection 6. To start the Database creation, you must specify a DB2 user ID. We suggest you use the same DB2 user ID you created before (see Table 4-7 on page 68). Click Next, as shown in Figure 4-51 on page 97.96 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-51 DB2 user and password7. Enter your DB2 user ID and password again (see Table 4-7 on page 68). Do not take the default of Use Local Database. Click Create local database. By default, a database named TPCDB is created. Click Next to continue (Figure 4-52)..Figure 4-52 DB2 user and create local database8. The next panel allows you to change the default space assigned to the database. At this time, you do not need to change these values and you can accept defaults. You have to specify the Schema name. In our installation we chose TPC. For better performance, we recommend that you: – Allocate TEMP DB on a different physical disk that the TotalStorage Productivity Center components. – Create larger Key and Big Databases.9. Select System managed (SMS) and click OK to proceed (see Figure 4-53 on page 98). To understand the advantage of an SMS database versus a DMS database, refer to 11.1, “Selecting an SMS or DMS tablespace” on page 510. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 97
    • Figure 4-53 DB schema space Figure 4-54 is the the Database schema installation progress panel. Wait for the installation to complete. Figure 4-54 installing DB 10.Upon completion, the successfully installed panel is displayed. Click Finish to continue (Figure 4-55 on page 99).98 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-55 Installation summary information4.7.1 Verifying installation To check the installation, start DB2 Control Center, verifying that you have two DB2 instances in your environment, as shown in Figure 4-56. Figure 4-56 Verifying DB2 installation Attention: Do not edit or modify anything in DB2 Control Center. This could cause serious damage to your tablespace. Simply use DB2 Control Center to browse your configuration. Log files Check for errors and java exceptions in the log files at the following locations: Install<timestamp>.log file from system temp directory or <InstallLocation>. <InstallLocation>dbschemalog Chapter 4. TotalStorage Productivity Center installation on Windows 2003 99
    • Look for dbschema.out, dbschema.err, DBSchema.log <InstallLocation>log <InstallLocation>TPC.log Check for the success message at the end of the INSTALL<timestamp>.log file for successful installation.4.7.2 Installing Data and Device Servers, GUI, and CLI In our environment, we performed a custom installation of Data Server, Device Server, GUI, and CLI. Preinstallation tasks To install Data Server and Device Server components, you must log on to Windows 2003 with a User that has the following rights: Log on as a service. Act as part of the operating system. Adjust memory quotas for a process. Create a token object. Debug programs. Replace a process-level token. Be certain the following tasks are completed: We recommend you create a user ID for installation. We created the user ID TPCADMIN (refer to Table 4-5 on page 67). The database schema must be installed successfully to start the Data server installation. An accessible Agent manager must be available to start the Device server installation. Data server must be successfully installed prior to installing GUI. Device server must be successfully installed prior to installing CLI. Custom installation To perform a custom installation, follow these steps: 1. Start the TotalStorage Productivity Center installer. 2. Select the components you want to install. In our scenario, we select the four server components, as shown in Figure 4-57 on page 101. Tip: We recommend that you install Data Agent and Device Agent in a separate step. If you install all the components at the same time, if one fails for any reason (for example, space or passwords) the installation suspends and a rollback occurs, uninstalling all the previously installed components.100 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-57 Installation selection – Specify the DB2 user ID and password defined for Table 4-7 on page 68 in the panel in Figure 4-58 and click Next.Figure 4-58 User ID and password3. Enter the DB2 user ID and password and click Use local database. Click Next to continue (Figure 4-59 on page 102). Chapter 4. TotalStorage Productivity Center installation on Windows 2003 101
    • Figure 4-59 Use local database selection 4. In the panel in Figure 4-60 on page 103, enter the following information: – Data Server Name Enter the fully qualified host name of the Data Server. – Data Server Port Enter the Data Server port. The default is 9549. See 3.3.1, “TCP/IP ports used” on page 46 for more details. – Device Server Name Enter the fully qualified host name of the Device Server. – Device Server Port Enter the Device Server port. The default is 9550. – TPC Superuser Enter the Administrators Group for the TPC Superuser. We created the user ID TPCADMIN and added this to the existing Administrators group. See 4.5.5, “User IDs and password to be used and defined” on page 66 for more details. – Host Authentication Password This is the password used for the Fabric agents to communicate with the Device Server. Remember to record this password. See Table 4-11 on page 70. – WebSphere Application Server admin ID and Password You can use the TPC Superuser here. In our case we used TPCADMIN. See Table 4-14 on page 71 for further details. Click Next to continue.102 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-60 Component information for installation5. In the panel shown in Figure 4-61 on page 104, enter the Agent Manager information. You must specify the following information: – Hostname or IP address Fully qualified name or IP address of the agent manager server. For further details about the fully qualified name, refer to 4.5.1, “Verify primary domain name systems” on page 62. – Port (Secured) Port number of the Agent Manager server. If acceptable (not in use by any other application), use the default port 9511.See 3.3.1, “TCP/IP ports used” on page 46 for further details. – Port (Public) The public communication port. If acceptable (not in use by any other application), use the default of 9513. – User ID This is the user ID used to register the Data Server or Device Server with the Agent Manager. The default is manager. You previously specified this user ID during the Agent Manager install (see Figure 4-38 on page 89). – Password This is the password used to register the Data Server or Device Server with the Agent Manager. The default is password. You previously specified this user ID during the Agent Manager install (see Figure 4-38 on page 89). – Password - common agent registration password This is the password used by the common agent to register with the agent manager. this was specified when you installed the Agent Manager. The default is changeMe. See Table 4-9 on page 69 for further details. Click Next to continue. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 103
    • Figure 4-61 Agent manager 6. The Summary information panel is displayed. Review the information, then click Install to continue (see Figure 4-62). Figure 4-62 Summary of installation The installation starts. You might see several messages related to Data Server installation similar to Figure 4-63 on page 105.104 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-63 Installing Data Server You might also see several messages about the Device Server installation, as shown in Figure 4-64.Figure 4-64 Installing Device Server7. After the GUI and CLI installation messages, you see the summary information panel (Figure 4-65 on page 106). Read and verify the information and click Finish to complete the installation. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 105
    • Figure 4-65 Component installation completion panel Verifying installation At the end of the installation, the Windows Services shows the Data Server and Device Server services (shown in Figure 4-66) have been installed. Figure 4-66 Windows service Check that the Administrators group contains the newly created TPC user ID. The user ID TSRMsrv1 is created by default by the install program. Log files for data server Check the logs for any errors/java exceptions. Install<timestamp>.log file from system temp directory or <InstallLocation> <InstallLocation>datalog Look for dataserver.out, dataserver.err, DataServer.log <InstallLocation>log106 IBM TotalStorage Productivity Center: The Next Generation
    • From <InstallLocation>datalog: – Cimom_000001.log – createdLuns.log – guidinstallog.txt – Scheduler_000001.log – Server_000001.log – TPCD_000001.log – TSRMsrv1.out INSTALL<timestamp>.log file should not have any exceptions and it should show install successful at the bottom. Server_000001.out file mentions that the server is ready to accept connections. Log files for device server The log files for the device server are: <InstallLocation>deviceappswaslogs <InstallLocation>TPC.log <InstallLocation>device.log <InstallLocation>deviceMgrlog.txt If successful, you see the Server server1 open for e-business message in <InstallationLocation>deviceappswaslogsserver1SystemOut.log. In case of failure you can find errors and exceptions here. Log files for GUI Check the log files for any errors. The log files for the GUI are: Install<timestamp>.log file from system temp directory or <InstallLocation>. <InstallLocation>guilog Look for gui.out, gui.err, GUI.log Log files for CLI Check the log files for any errors. The log files for the CLI are: <InstallLocation> <InstallLocation>clilog <InstallLocation>clilog4.8 Configuring the GUI for Web Access under Windows 2003 You can configure the TotalStorage Productivity Center V3.1 user interface to be accessible from a Web browser. After this is done, a user can access the TotalStorage Productivity Center GUI by browsing to the URL. The TotalStorage Productivity Center GUI applet is downloaded into the browser and executed. It looks and acts exactly as though you were interacting with the native server. You can install the interface on any of the TotalStorage Productivity Center servers, management consoles, or workstations. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 107
    • 4.8.1 Installing Internet Information Services (IIS) To configure the Web server on the TotalStorage Productivity Center Server, make sure that IIS is installed. It is not installed by default, but is a part of Windows Server 2003. To install it, follow these directions. 1. On the Windows Taskbar, select Start → Control Panel → Add or Remove programs 2. Select Add/Remove Windows Components from the task bar on the left (see Figure 4-67). Figure 4-67 Add/Remove Windows Components icon 3. Highlight the entry for Application Server. Click Details to continue (Figure 4-68). Figure 4-68 Windows Components panel 4. Check the Internet Information Services (IIS) box. Click OK to continue (Figure 4-69 on page 109).108 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-69 Installing IIS5. You are returned to the panel in Figure 4-68 on page 108. Click Next to install IIS. An Installation Progress window shows the installation progress. Have your Windows Server 2003 CD-ROM available or have a 2003 I386 directory installed on a hard disk (see Figure 4-70). If you have Service Pack 1 installed, you also need to have the Service Pack 1 CD_ROM or SP1 I386 directory available as well.Figure 4-70 Service Pack media request6. When the installation has completed successfully, click the Finish button to complete the Windows Component Wizard (see Figure 4-71 on page 110). Chapter 4. TotalStorage Productivity Center installation on Windows 2003 109
    • Figure 4-71 Installation complete window 7. Cancel the Add or Remove Programs dialog box. You now have IIS installed.4.8.2 Configuring IIS for the TotalStorage Productivity Center GUI You can now configure IIS to serve up the TotalStorage Productivity Center User interface. 1. Open the IIS Configuration Panel by clicking Start → All Programs → Administrative Tools → Internet Information Services (IIS) Manager (Figure 4-72). Figure 4-72 Open the IIS configuration panel 2. When the Internet Information Services (IIS) Manager opens, open the Explorer panel to display the Web Site Default Web Site. Right-click the Default Web Site name, and click the Properties entry from the context menu (see Figure 4-73 on page 111).110 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-73 IIS Default Web Site Properties3. The Default Web Site Properties panel opens. There are three tabs that you must configure: – Web Site tab On the Web Site tab (see Figure 4-74 on page 112), you can change the Description to TPC V3.1 GUI. Attention: Agent Manager is configured to use port 80 for the Agent Recovery service, you must change the default port to something other than 80. Port 8080 is a good alternative. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 111
    • Figure 4-74 Default Web Site Properties - Web Site tab – Home Directory tab On the Home Directory tab (Figure 4-75), change the Local Path to the GUI directory for TotalStorage Productivity Center. The default is C:Program FilesIBMTPCgui. Figure 4-75 Default Web Site Properties Home Directory tab112 IBM TotalStorage Productivity Center: The Next Generation
    • – Documents tab On the Documents tab (see Figure 4-76), click the Add… button, and add TPCD.html to the list. Highlight the new name in the list, and click Move Up to move TPCD.html to the top of the list. Figure 4-76 Default Web Site Properties Documents tab 4. Click OK to save these changes. Close the IIS Manager by clicking the X in the upper right corner of the panel.4.8.3 Launch the TotalStorage Productivity Center GUI To start the TotalStorage Productivity Center GUI, follow these steps: 1. Start your Web browser (Internet Explorer®), and enter the URL you have just created. If you changed the port, you must incorporate the port into the URL also. The format of the URL is: http://<hostname>:port# For example, if your hostname for the TotalStorage Productivity Center server is fred.mycompany.com, and you changed the port to 8080, the URL would be http://fred.mycompany.com:8080 If you left the port set to 80, the URL is: http://fred.mycompany.com If you start the Web browser on your TotalStorage Productivity Center server machine, you can use localhost rather than the network name: http://localhost Chapter 4. TotalStorage Productivity Center installation on Windows 2003 113
    • 2. The IBM TotalStorage Productivity Center for Data panel is displayed (see Figure 4-77). This is the anchor page for the TotalStorage Productivity Center GUI java applet, and must remain open as long as the TotalStorage Productivity Center GUI is running. Figure 4-77 TotalStorage Productivity Center for Data panel 3. A security certificate approval panel is displayed (see Figure 4-78 on page 115). Depending on network transmission rates, it could take a few minutes for the panel to open. Click Yes to accept the certificate. (If you click No, the TotalStorage Productivity Center GUI does not load, and you must relaunch the TotalStorage Productivity Center GUI URL to restart.)114 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 4-78 Security certificate At this point, the java applet for the TotalStorage Productivity Center GUI downloads. The applet jar file is 15.6 MB, and can take some time to load into your browser the first time. Be patient because there is no progress bar displayed while it downloads. When the applet jar file has been loaded into your browser, it remains in your browser cache until you dump it. Subsequent starts of the TotalStorage Productivity Center GUI will load much faster.4. After the applet has loaded, it launches the TotalStorage Productivity Center GUI. In the center of the GUI, the Sign On panel opens. It should be prefilled with the Server address and access port (9549 for TotalStorage Productivity Center V3.1). Enter your TotalStorage Productivity Center Server User ID and password, and click OK to continue (see Figure 4-79).Figure 4-79 IBM TotalStorage Productivity Center Sign on panelThe TotalStorage Productivity CenterGUI is displayed (see Figure 4-80 on page 116), andhas all the functionality of the native GUI on the TotalStorage Productivity Center Server. Chapter 4. TotalStorage Productivity Center installation on Windows 2003 115
    • Figure 4-80 TotalStorage Productivity Center V3.1 GUI116 IBM TotalStorage Productivity Center: The Next Generation
    • 5 Chapter 5. TotalStorage Productivity Center installation on AIX In this chapter we describe the installation of TotalStorage Productivity Center on AIX. This includes the installation of the prerequisite components - DB2 and Agent Manager. Of the available installation paths, Typical and Custom, we used the custom installation for our environment.© Copyright IBM Corp. 2006. All rights reserved. 117
    • 5.1 TotalStorage Productivity Center installation IBM TotalStorage Productivity Center is a unified software product which contains multiple, modular components as shown in Figure 5-1. TPC Version 3 Release 1 TPC Standard A Single Application Edition with modular components Disk Data Fabric Streamlined Installation and Consistent Reporting Capabilities NEW: Storage topology viewer Packaging (Scheduled, Ad-Hoc) NEW: Role based administration Single User Interface Data Export Capabilities - File System, Database, Fabric (html, CSV) NEW: AIX support for TPC server and Storage management NEW: Fabric performance management Single set of services for - Asset, Capacity and consistent administration and NEW: Tape discovery and asset/capacity Performance Reporting operations reporting Single Database Policy Definitions, Correlated host, fabric, storage Event Handling, NEW: Performance Management for information Resource Groups DS4000 TPC Standard Edition for the full suite or orderable separately Figure 5-1 A single application TotalStorage Productivity Center provides an integrated storage infrastructure management solution that is designed to allow you to manage every point of your storage infrastructure, including hosts, network and fabric, and physical disks. It can help simplify and automate the management of devices, data, and storage networks. TotalStorage Productivity Center V3.1 offers a simple, easy to install package with management server support added for IBM AIX V5.3, and integrating IBM DB2 as the management server database. The default installation directory is: /opt/IBM/TPC for AIX. You may change this path during installation setup. There are two types of installation, typical and custom.5.1.1 Typical installation The typical installation allows you to install all the components on the same computer, by selecting Servers, Agents and Clients. It is a local installation only.5.1.2 Custom installation The Custom installation allows you to install each component separately and deploy Remote Agents, Fabric and, Data on a different computer.118 IBM TotalStorage Productivity Center: The Next Generation
    • 5.1.3 CD layout and components You can install the components from different CDs: CD1: – OS: Windows, AIX and Linux Red Hat 3 – Database Schema – Data Server – Device Server – GUI – CLI – Local Data Agent – Local Device Agent – Remote installation of Device Agent CD2: – OS: Windows, AIX, Linux Red Hat 3, Linux Power, Linux s390 (zLinux), Solaris, HP-UX – Local Data Agent – Local Device Agent – Remote installation of Data Agent – Remote installation of Device Agent CD3: – Data Upgrade for all supported platforms. If you need to perform a remote installation of Data Agents on an Operating System other than AIX, you need to copy the contents of both CD1 and CD2 to one location.5.2 Configuration The IBM TotalStorage Productivity Center components are listed below: Data Server Device Server DB2 Agent Manager Graphical User Interface (GUI) Command Line Interface (CLI) The Data Server and Device Server must be installed on the same server. You can install all the components on one server, or you can have a two server configuration. In a two server configuration you would install the components as follows: Server 1 – DB2 – Agent Manager Server 2 – Device Server – Data Server – GUI – CLI You can install DB2 on a remote server. Chapter 5. TotalStorage Productivity Center installation on AIX 119
    • 5.3 Hardware Prerequisites The minimum hardware prerequisites are listed below. For AIX on IBM eServer iSeries and IBM eServer pSeries: Processor - Minimum 1.0 GHz 4 GB of RAM Network connectivity For AIX, you need 500 MB in /tmp and 1.3 GB in /opt and up to approximately 80 GB of hard disk space for databases.5.4 Software Prerequisites Table 5-1 shows the platforms supported by IBM TotalStorage Productivity Center for AIX server components. Table 5-1 Platform support for Data server, Device server, GUI and Agent Manager Platform Data server, Device GUI Agent Manager v1.2 server, database (install fix pack 2, schema (DB2), CLI even if you can optionally use the Agent Manager you installed with v2.3) IBM AIX 5.1 (32-bit) NO NO YES IBM AIX 5.1 (64-bit) NO NO YES IBM AIX 5L (32-bit) NO NO YES IBM AIX 5L (64-bit) NO NO YES IBM AIX 5.2 (32-bit) NO NO YES IBM AIX 5.2 (64-bit) NO NO YES IBM AIX 5.3 (32 bit) YES YES YES (32- and 64-bit) (with AIX 5300-01 (with AIX 5300-01 maintenance level and maintenance level and APAR IY70336 APAR IY70336 Table 5-2 shows the platform supported to install and deploy Data agent and Fabric agent. Important: Data agents and Fabric agents at the 2.x version are supported by IBM TotalStorage Productivity Center V3.1 managers. Table 5-2 Platform support for Data agent and Fabric agent Platform Data agent and Fabric agent Windows 2000 Advanced Server Only Data agent Windows 2000 Datacenter Only Data agent Windows Server 2003 Standard Edition YES120 IBM TotalStorage Productivity Center: The Next Generation
    • Platform Data agent and Fabric agentWindows Server 2003 Enterprise Edition YESRed Hat Enterprise Linux AS Version 3.0 IBM YESeServer xSeriesRed Hat Enterprise Linux AS Version 3.0 IBM Only Data agenteServer pSeries on POWER5Red Hat Enterprise Linux AS Version 3.0 IBM Only Data agenteServer iSeries on POWER5United LInux 1.0 IBM eServer xSeries Only Data agentUnited LInux 1.0 IBM eServer zSeries Only Data agentSUSE LINUX Enterprise Server 8 Only Data agentIBM eServer pSeries on POWER4 zSeriesSUSE LINUX Enterprise Server 9 Only Data agentIBM eServer xSeries, pSeries on POWER5iSeries on POWER5 zseries (Data agent only)SUSE LINUX Enterprise Server 9 Data agent (ALL)IBM eServer xSeries, pSeries on POWER5 Fabric agent (xSeries only)iSeries on POWER5 zseries (Data agent only)IBM AIX 5.1 (32-bit) YES with AIX 5100-05 maintenance levelIBM AIX 5.1 (64-bit) YES in compatibility mode with AIX 5100-05 maintenance levelIBM AIX 5L (32-bit) YES in compatibility mode with AIX 5100-05 maintenance levelIBM AIX 5L (64-bit) YES in compatibility mode with AIX 5100-05 maintenance levelIBM AIX 5.2 (32-bit) YES with AIX 5200-02 maintenance levelIBM AIX 5.2 (64-bit) YES in compatibility mode with AIX 5200-02 maintenance levelIBM AIX 5.3 (32 bit) YES with AIX 5300-01 maintenance level and APAR IY70336Solaris 8 YESSolaris 9 YESHP-UX 11 and 11i Only Data agent Chapter 5. TotalStorage Productivity Center installation on AIX 121
    • 5.4.1 Databases supported At time of writing, we used the information contained on the following Web site as a reference. http://www-1.ibm.com/support/docview.wss?rs=1133&uid=ssg1S1002813 The Agent Manager repository is supported only on the following databases. DB2 Enterprise Server Edition version 8.2 with fix pack 7a or higher. There is only one database instance created for IBM TotalStorage Productivity Center on DB2. The default database name for the repository is TPCDB. The Agent Manager repository uses its own database. The default name of this database is IBMCDB. Data agent monitored databases The Data agent can monitor these databases: DB2 7.2 - 32 bit only DB2 8.1 - 32 or 64 bit DB2 8.2 - 32 or 64 bit Microsoft SQL Server 7.0 Microsoft SQL Server 2000 Oracle 8i Oracle 9i Oracle 10g Sybase support is not included in TotalStorage Productivity Center V3.1. Note: We recommend that you install a single instance of IBM DB2 UDB Enterprise Server Edition version 8.2 with fix pack 7a or higher as your repository for both the Agent Manager and IBM TotalStorage Productivity Center.5.5 Preinstallation steps for AIX The prerequisite components for IBM TotalStorage Productivity Center V3.1 are: IBM DB2 UDB Enterprise Server Edition V8.2 fix pack 7a or higher Agent Manager 1.2, 1.2.2 or later (V1.1 is not supported with TotalStorage Productivity Center V3.1) In addition, you must perform the steps outlined below.5.5.1 Verify primary domain name servers Before starting your installation, we recommend that you verify that a primary domain name system (DNS) suffix is set. This may require a computer restart. Follow these steps: 1. Log on to the system as a user with root-level authority, 2. Display the contents of the file /etc/resolv.conf. Two ways to do this are shown below: cat /etc/resolv.conf or lsnamsv -C122 IBM TotalStorage Productivity Center: The Next Generation
    • 3. The file should contain a reference to one or more name servers, as well as the name of the DNS domain for the host. A sample file may look like this: nameserver 1.2.3.4 domain mycompany.com 4. If the file does not contain those two references, edit the file to insert the IP address of a DNS server, and the domain name which should be used by the host. Save the file when you have finished your edits. Alternatively, you can use SMIT to accomplish this. From the main SMIT menu, choose Communications Applications and Services → TCP/IP → Minimum Configuration & Startup. From the menu that appears, select the appropriate network interface. Then in the NAMESERVER options, edit the properties for Internet ADDRESS (dotted decimal) and DOMAIN name. Change the START Now option to Yes, and press Enter. When the changes have been committed and the OK status appears, press F10 to exit SMIT.5.5.2 User IDs, passwords, and groups We have included worksheets in Appendix A, “Worksheets” on page 519 to help you keep track of the user IDs, passwords, and groups required to install and configure TotalStorage Productivity Center. We reprint two of those sheets here to show you the user IDs, passwords, and groups we used in our environment. Note: You should create user IDs, groups, and passwords which conform to the requirements and standards of your organization whenever possible. However, we recommend that you do not use any characters other than letters and numbers in creating the user IDs and passwords used by the TotalStorage Productivity Center components. Some of the user IDs, passwords, and groups we used in creating this Redbook would not be considered secure enough for many production deployments. Table 5-3 shows the password we use when generating the security certificates in 5.8, “Agent Manager installation for AIX” on page 146. Table 5-3 Password used to lock the key file Default key file name Password agentTrust.jks tpctpc Table 5-4 shows the user IDs and passwords we use for the various components of TotalStorage Productivity Center. You may wish to refer to this table, or the worksheets in the Appendix as you read the remainder of this chapter. Table 5-4 User IDs and passwords used in our environment Element Default user ID Our user ID Our password DB2 DAS user db2admin db2tpc db2tpc DB2 instance owner db2inst1 db2inst2 passw0rd DB2 fenced user db2fenc1 db2fenc1 passw0rd Resource Manager manager1 manager1 password Agent Manager AgentMgr AgentMgr changeMe2 Common Agent itcauser1 itcauser1 changeMe2 Chapter 5. TotalStorage Productivity Center installation on AIX 123
    • Element Default user ID Our user ID Our password WebSphere (user defined) tpcadmin tpcadmin Administrator Host authentication (user defined) tpctpc tpctpc TotalStorage (user defined)3 tpcadmin3 tpcadmin Productivity Center administrator 1 - This user ID is created by the installer and cannot be changed. 2 - Despite what it says, we recommend that you do NOT change this password. 3 - This user ID is created manually. Some of these user IDs and passwords will be created by the installers, but there is one user ID that we recommend you create, the TotalStorage Productivity Center administrator. The next section discusses the creation of this user.5.5.3 Create the TotalStorage Productivity Center user ID and group Prior to installing TotalStorage Productivity Center, we recommend that you create a user ID which will be used to administer the TotalStorage Productivity Center. This user, as well as any user that will be authorized to manage your storage environment, must be made a member of the adm AIX group. All defined AIX users on the TotalStorage Productivity Center server will be automatically granted read-only privileges to use the Graphical User Interface (GUI), but only users in the adm group will be authorized to use the GUI to make changes to the environment. Follow these steps to create the administrative user and configure the adm group: 1. If you have not already done so, log on to the system as a user with root-level authority. 2. Launch the SMIT interface by typing smit at a command prompt. 3. From the main SMIT menu, choose Security & Users, → Users → Add a User. 4. Complete the Add a User form according to your organization’s standards. When you have completed the form, press Enter to create the user. When the user has been created and the OK status appears, press F3 three times to return to the Security & Users menu. Note: The user ID you create is subject to the following constraints: It must contain only lower-case alpha and numeric characters (a-z, 0-9) and be 8 characters or less It must not start with a numeric digit The password must be 8 characters or less The password may contain upper- or lower-case alpha and numeric characters 5. From the Security & Users menu, highlight Groups and press Enter. 6. From the Groups menu, highlight Change / Show Characteristics of a Group and press Enter. 7. In the Group NAME field, type adm and press Enter. The properties for the adm group will display. 8. Highlight the USER List field. You may type user IDs directly into this field, separating multiple user IDs with a comma. Alternatively, you can press F4 to display a list of users to124 IBM TotalStorage Productivity Center: The Next Generation
    • add to the group. Move the cursor to the desired user ID and press F7 to select that user ID. Multiple users can be selected by moving the cursor each desired user ID and pressing F7 while the user ID is highlighted. When you have finished selecting user IDs to add to the group, press Enter. You will be returned to the “Change Group Attributes” menu. 9. Press Enter to commit the changes you have made to the adm group. When the OK status appears, press F10 to exit SMIT (F12 if using the graphical version). 10.Set the initial password for the user ID you just created by typing passwd username at a command prompt, where username is the user ID you just created. Follow the on-screen prompts to enter the new password two times. Note: After DB2 is installed, and you have applied the latest fix pack, you must add the root user to the group db2grp1. The group will be automatically created during the installation of DB2. Adding the root user to this group allows the root user to source the instance owner’s environment prior to installing TotalStorage Productivity Center. Refer to 5.7.2, “Add the root user to the DB2 instance group” on page 145 for details.5.5.4 Creating and sizing file systems and logical volumes At a minimum, the installation of IBM TotalStorage Productivity Center V3.1 requires that you have 500 MB free space in /tmp and 1.3 GB free space in /opt. In addition, if you are installing any of the products from a downloaded image, you will need additional space to house the image plus space to house the extracted files contained within the image. For best performance, we recommend creating separate logical volumes and file systems to house the various components of TotalStorage Productivity Center. For Enterprise-class deployments, these should ideally be on separate disk devices. For example, you could create a volume for DB2 application code, another for DB2 databases, a third for DB2 temporary storage, and a fourth for DB2 log files (only if you choose Database managed storage). In addition, you could create a volume for Agent Manager application code and for TotalStorage Productivity Center server code. For all deployments, we recommend creating separate file systems to house each component of IBM DB2, Agent Manager, and TotalStorage Productivity Center whenever possible. Tip: If you performed a default installation of AIX, it is likely that you will need to extend the logical volumes and file systems that house /tmp and /opt prior to beginning the installation procedure for TotalStorage Productivity Center. For detailed instructions on creating or extending logical volumes and file systems in AIX, consult AIX 5L Version 5.3 System Management Guide: Operating Systems and Devices, SC23-4910.5.5.5 Verify port availability TotalStorage Productivity Center communicates on a variety of TCP ports. Table 5-5 on page 126 lists the ports used by the various components of TotalStorage Productivity Center and indicates the direction of communication. You will need to ensure that your servers and agents can communicate with each other on all of these ports, including traversing any intervening firewalls or routers. Chapter 5. TotalStorage Productivity Center installation on AIX 125
    • Table 5-5 TCP ports used by TotalStorage Productivity Center components Component Port Number Inbound to or Inbound to our outbound from the outbound from the server agent Remote agent 22 (SSH) Outbound Both deployment for UNIX agents Agent Manager 80 (HTTP) Inbound Outbound recovery service (optional) or Web GUI (optional) Remote agent 139 (NetBIOS) Outbound Both deployment for Windows agents Remote agent 512 (REXEC) Outbound Both deployment for UNIX agents Remote agent 514 (RSH) Outbound Both deployment for UNIX agents Remote agent 601 Inbound Outbound deployment for UNIX agents Remote agent 2078 Inbound Outbound deployment for all agents; Graphical User Interface Remote agent 3000+ (High ports) Inbound Both deployment for all agents; Common Agent 9510 Outbound Inbound Agent Manager 9511 Inbound Outbound Agent Manager 9512 Both Both Agent Manager 9513 Inbound Outbound Common Agent (no 9514 Local to server None access needed) Common Agent (no 9515 Local to server None access needed) Data Server; Web GUI 9549 Both Both Device Server 9550 Both Both126 IBM TotalStorage Productivity Center: The Next Generation
    • 5.6 DB2 installation for AIX Once you have verified that your system has met the minimum system requirements for installing TotalStorage Productivity Center, including adequate free disk space, the first component to be installed is IBM DB2 UDB Enterprise Server Edition V8.2. Once it is successfully installed, you will then install the DB2 fix pack. At a minimum, fix pack 7a is required. Follow these steps to perform the installation of IBM DB2 UDB:5.6.1 Accessing the installation media with CD If you are accessing the installation media using a downloaded image, skip to the next section. 1. If you have not already done so, log on to the system as the root user. 2. Insert the CD into the CD-ROM or DVD-ROM drive on your system. 3. Create a mount point for the media. For example, if you wish to mount the disc at /cdrom, type the following command: mkdir /cdrom 4. Next, mount the disc in read-only mode at the mount point you created in the previous step. For example: mount -o ro /dev/cd0 /cdrom 5. Change to the newly mounted fleshiest. For example: cd /cdrom 6. Proceed to the section entitled Preparing the display, below.5.6.2 Accessing the installation media with a downloaded image 1. If you have not already done so, log on to the system as the root user. 2. Create a temporary directory to contain the installation image and the compressed image files. This directory must be created on a fleshiest which has approximately 2 GB of free space. Also, the directory must NOT contain a space anywhere in its path. For example, to create a directory in /usr called tarfiles, type the following command: mkdir /usr/tarfiles 3. Download or copy the installation image to the temporary directory you created. 4. Change to the directory where you have stored the image. For example: cd /usr/tarfiles 5. Extract the image files by following the instructions supplied at the repository from which you downloaded the image. This may involve running the tar or gunzip commands, or a combination of both. For example: tar -xvf db2.tar 6. Change to the installation directory which you extracted from the image. For example: cd ese.sbcsaix15.6.3 Preparing the display This version of the DB2 installer uses a graphical, Java-based interface. If you are installing with a local graphical display, proceed to the next section entitled 5.6.4, “Beginning the Chapter 5. TotalStorage Productivity Center installation on AIX 127
    • installation” on page 128. However, if you are installing from a remote terminal session, you must setup an X-Windows display prior to beginning the installation process. First, you must start your local X-Windows server application. Examples are Hummingbird Exceed or Cygwin. After your local X-Windows server application is running, you must set the DISPLAY variable on your host. You must know the IP address of the system from which you intend to perform the installation. For example, if the IP address is 2.3.4.5, type the following command at the server’s command prompt: export DISPLAY=2.3.4.5:0.0 You can verify that the X-Windows environment is properly set up by executing the following command on the host: xclock If the environment is successfully configured, you will see a graphical clock display, similar to the one shown in Figure 5-2: Figure 5-2 Graphical clock display5.6.4 Beginning the installation Follow these steps to perform the installation of IBM DB2 UDB: 1. At the command prompt on the host, type the following command: ./db2setup The DB2 setup launchpad opens, and appears similar to the one shown in Figure 5-3.128 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-3 DB2 Launchpad2. Click Install products to begin the installation. A new window will display, similar to the one in Figure 5-4 which asks you which products you would like to install.Figure 5-4 DB2 product selection3. Select the option DB2 UDB Enterprise Server Edition and click Next. The DB2 setup wizard will now display, and will be similar to the one shown in Figure 5-5. Chapter 5. TotalStorage Productivity Center installation on AIX 129
    • Figure 5-5 Welcome to the DB2 Setup wizard 4. Click Next. The license agreement opens, and is similar to the one shown in Figure 5-6. Figure 5-6 DB2 Software License Agreement130 IBM TotalStorage Productivity Center: The Next Generation
    • 5. You must click Accept, then click Next to proceed. The Installation Type window opens and is similar to the one shown in Figure 5-7 on page 131.Figure 5-7 DB2 installation type6. Select the Typical installation option, then click Next. The installation action window opens and is similar to the one shown in Figure 5-8 on page 132. Chapter 5. TotalStorage Productivity Center installation on AIX 131
    • Figure 5-8 DB2 installation action 7. Select Install DB2 UDB Enterprise Server Edition on this computer and click Next. The DAS user window opens and is similar to the one shown in Figure 5-9 on page 133.132 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-9 DB2 Administration Server user information8. If you would like the installer to create a DB2 Administration Server (DAS) user ID, you must enter a unique username for the DAS user in the User name field. You must also enter a password in both the Password and Confirm password fields. If you leave the UID and GID fields blank, and check the Use default boxes, the system assign a UID and GID for you. Optionally, you can check the Existing user button, and enter the name of an existing user ID which will become the DAS user. When you have completed this form, click Next. The Set up a DB2 instance window opens and appears similar to the one shown in Figure 5-10 on page 134. Chapter 5. TotalStorage Productivity Center installation on AIX 133
    • Figure 5-10 Set up a DB2 instance 9. Select the option Create a DB2 Instance - 32 bit and click Next. The instance partitioning window opens and appears similar to the one shown in Figure 5-11 on page 135.134 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-11 DB2 instance partitioning10.Select Single-partition instance and click Next. The DB2 instance owner window opens and is similar to the one shown in Figure 5-12 on page 136. Chapter 5. TotalStorage Productivity Center installation on AIX 135
    • Figure 5-12 DB2 instance owner 11.If you would like the installer to create a DB2 instance owner user ID, you must enter a unique username for the instance owner in the User name field. You must also enter a password in both the Password and Confirm password fields. If you leave the UID and GID fields blank, and check the Use default boxes, the system will assign a UID and GID for you. Optionally, you can check the Existing user button, and enter the name of an existing user ID which will become the instance owner. After you have completed this form, click Next. The DB2 fenced user window opens and is similar to the one shown in Figure 5-13 on page 137.136 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-13 DB2 fenced user12.If you would like the installer to create a DB2 fenced user ID, you must enter a unique username for the fenced user in the User name field. You must also enter a password in both the Password and Confirm password fields. If you leave the UID and GID fields blank, and check the Use default boxes, the system will assign a UID and GID for you. Optionally, you can check the Existing user button, and enter the name of an existing user ID which will become the fenced user. When you have completed this form, click Next. The Prepare the DB2 tools catalog window opens and is similar to the one shown in Figure 5-14 on page 138. Chapter 5. TotalStorage Productivity Center installation on AIX 137
    • Figure 5-14 DB2 tools catalog 13.Click Do not prepare the DB2 tools catalog on this computer, then click Next. The Administration contact window opens and is similar to the one shown in Figure 5-15 on page 139.138 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-15 DB2 administration contact14.Choose the options on this screen which pertain to your specific environment. If you already have DB2 servers in your environment, it can benefit you to use a contact list on an existing DB2 server. If so, select Remote and enter the name of the remote DB2 server from which to obtain the contact list. Otherwise, choose the default options of Local and Enable notification. The local host name is displayed in the Notification SMTP server field by default. You can change this option to suit your environment. After you have completed this form, click Next. The health monitor window opens, similar to the one shown in Figure 5-16 on page 140. Chapter 5. TotalStorage Productivity Center installation on AIX 139
    • Figure 5-16 DB2 health monitor contact 15.Enter information in this screen also in accordance with your particular environment. If you do not want to specify a contact, choose Defer this task until after installation is complete, then click Next. The Start copying files window opens, similar to the one shown in Figure 5-17 on page 141.140 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-17 DB2 start copying files16.Scroll through the window to review the installation summary. When you are ready to proceed, click Finish. The DB2 installer begins the product installation. A progress screen opens and appears similar to the one shown in Figure 5-18.Figure 5-18 DB2 installation progress17.When DB2 has been installed successfully, an installation summary screen opens, similar to the one shown in Figure 5-19 on page 142. Chapter 5. TotalStorage Productivity Center installation on AIX 141
    • Figure 5-19 DB2 post installation steps 18.Review the information in the Post-install steps tab to see if there are any additional tasks you need to complete. You can also select the Status report tab. It appears similar to the one shown in Figure 5-20. Figure 5-20 DB2 installation status report 19.Each of the items in the status report should indicate Success. Click Finish to close the installer.142 IBM TotalStorage Productivity Center: The Next Generation
    • 5.6.5 Verifying the DB2 installation To verify that DB2 was successfully installed, first change to the instance owner user ID by using the su command. For example, if your instance owner user ID is db2inst1, type the following at the host command prompt: su - db2inst1 This will log you on to the system as the instance owner. Then, type the following commands db2level exit The output of the db2level command will appear similar to the text shown in Figure 5-21: DB21085I Instance "db2inst1" uses "32" bits and DB2 code release "SQL08020" with level identifier "03010106". Informational tokens are "DB2 v8.1.1.64", "s040812", "U498350", and FixPak "7". Product is installed at "/usr/opt/db2_08_01". Figure 5-21 Output of the db2level command5.6.6 Removing the CD from the server If you accessed the installation media from the CD, you should now unmount the CD and remove it from the system. To do this, complete the following steps: 1. Type the following at a host command prompt: umount /cdrom 2. Remove the CD from the drive by pressing the button on the front panel of the CD-ROM or DVD-ROM drive. This will eject the media tray. 3. Remove the CD from the media tray, and close the media tray by pressing the button again.5.7 Installing the DB2 fix pack TotalStorage Productivity Center requires you to install IBM DB2 UDB with fix pack 7a or higher. At the time of this writing, fix pack 10 was the latest available, and that is what we used during out testing. The procedure below is the one we followed for installing fix pack 10. You should always consult the README file for specific installation instructions for the version of the fix pack you are installing.5.7.1 Obtaining and installing the latest DB2 fix pack Complete the following steps to download and install the latest DB2 fix pack: 1. If you have not already done so, login to your DB2 server as the root user. 2. Create a temporary directory to contain the fix pack image and the compressed image files. This directory must be created on a fleshiest which has approximately 2 GB of free space. Also, the directory must NOT contain a space anywhere in its path. For example, to create a directory in /usr called tarfiles, type the following command: mkdir /usr/tarfiles Chapter 5. TotalStorage Productivity Center installation on AIX 143
    • 3. Download the latest IBM DB2 UDB fix pack from the IBM support FTP site. We donwnloaded fix pack 10 from the following location: ftp://ftp.software.ibm.com/ps/products/db2/fixes2/english-us/db2aix5v8/fixpak/ FP10_U803920/FP10_U803920.tar.Z 4. Change to the directory where you stored the fix pack image. For example, if you downloaded the file to /usr/tarfiles, type the following command: cd /usr/tarfiles 5. Extract the compressed image files. For version 10 of the fix pack, the command is: gunzip -c FP10_U803920.tar.Z | tar -xvf - 6. Switch to the instance authority. For example, if your DB2 instance is db2inst1, type the following command: su - db2inst1 7. Source the environment by issuing the following command: . $HOME/sqllib/db2profile 8. Type the following commands to shut down the DB2 environment: db2 force applications all db2 terminate db2stop db2licd -end $HOME/sqllib/bin/ipclean exit 9. Switch to the DAS user authority. For example, if your DB2 DAS user is db2tpc, type the following command: su - db2tpc 10.Type the following commands to source the environment and shutdown DB2 DAS: . $HOME/das/dasprofile db2admin stop exit 11.As the root user, issue the following commands to unload shared libraries and disable the DB2 fault monitor: /usr/sbin/slibclean cd /usr/opt/db2_08_01/bin Note: The above listed location is the default for DB2 installation. However, if you elected to install DB2 at another location, you should change into that directory structure instead. ./db2fmcu -d ./db2fm -i db2tpc -D Where db2tpc is the user ID of your DB2 DAS user. 12.Change to the directory which was created automatically when the fix pack files were uncompressed. For version 10 of the fix pack, the directory is named fixpak.s050811. To do this, type the following command: cd fixpak.s050811 13.Install the fix pack by issuing the following command: ./installFixPak -y144 IBM TotalStorage Productivity Center: The Next Generation
    • 14.After the fix pack has been successfully installed, you must bind the database instance to the updated code. To do this, you must issue the db2iupdt command. For example, if your instance name is db2inst1, and you installed DB2 in the default location, type the following commands: /usr/opt/db2_08_01/instance/db2iupdt db2inst1 15.Next you must update the DB2 DAS. For example, if your DB2 DAS user ID is db2tpc, type the following command: /usr/opt/db2_08_01/instance/dasupdt db2tpc 16.Next, you must update the db2 instance owner’s user profile to update the number of shared memory segments allowed for a process. To do this, edit the userprofile located in the sqllib directory under the instance owner’s home directory. For example, if your instance is db2inst1, then type the following command to change to that directory: cd /home/db2inst1/sqllib 17.Then, edit the userprofile contained in that directory. Add the following lines to the file, then save the file: EXTSHM=ON export EXTSHM db2set DB2ENVLIST=EXTSHM 18.Next, you must restart DB2. To do this, switch to the instance authority. For example, if your DB2 instance is db2inst1, type the following command: su - db2inst1 19.Source the environment by issuing the following command: . $HOME/sqllib/db2profile 20.Type the following commands to start the instance and exit from the instance authority: db2start exit 21.Finally, you must login as the DAS user and restart DB2 DAS. To do this, switch to the DAS user authority. For example, if your DB2 DAS user is db2tpc, type the following command: su - db2tpc 22.Type the following commands to source the environment and start DB2 DAS: . $HOME/das/dasprofile db2admin start exit5.7.2 Add the root user to the DB2 instance group You must add the root user to the group you created when you created the database instance. If you used the default group ID, the group name is db2grp1. This step is necessary in order to perform the TotalStorage Productivity Center installation. Follow these steps to add the root user to the instance group: 1. Type the following at a command prompt: smit group The SMIT interface will display, and will show the Groups menu. 2. Select the option Change / Show Characteristics of a Group. Chapter 5. TotalStorage Productivity Center installation on AIX 145
    • 3. In the Group NAME field, enter the name of the group to be modified. If you used the default group ID, enter the name db2grp1 and press Enter. 4. Highlight the USER list field and press F4. The USER list menu appears. 5. Highlight the root user ID and press F7 to select it. 6. Highlight the DB2 instance owner user ID and press F7 to select it. For example, select the user ID db2inst1. Then press Enter. The Change Group Attributes screen will reappear. Ensure that both the root user and the DB2 instance owner user ID appear in the USER list field, then press Enter. 7. When the OK status appears, press F10 to exit SMIT (F12 if using the graphical version).5.8 Agent Manager installation for AIX After you have completed the installation of IBM DB2 UDB, and applied the latest fix pack, then you can install Agent Manager. For small and medium-sized deployments, Agent Manager should be installed on the same server as DB2. For Enterprise deployments, Agent Manager can be installed on a separate server if desired. The only change to the install procedure will be connecting to a remote DB2 server, instead of a local one. If you are upgrading from TotalStorage Productivity Center V2.3, you do not need to reinstall Agent Manager. Agent Manager 1.2 will work and is supported with IBM TotalStorage Productivity Center V3.1. By default, the Agent Manager installer will also install IBM WebSphere Application Server - Express, V5.0 (WebSphere Express), unless it finds an existing copy of the full version of WebSphere Application Server (WAS) V5.1.1.3 or higher. If the installer does find an existing copy of WAS V5.1.1.3 or higher, the existing WAS installation will be used for Agent Manager.5.8.1 Accessing the installation media using CD If you are accessing the installation media using a downloaded image, skip to 5.8.2, “Accessing the installation media using a downloaded image” on page 146. 1. If you have not already done so, log on to the system as the root user. 2. Insert the CD into the CD-ROM or DVD-ROM drive on your system. 3. If you have not already done so, create a mount point for the media. For example, if you wish to mount the disc at /cdrom, type the mkdir /cdrom command. 4. Next, mount the disc in read-only mode at the mount point you created in the previous step, mount -o ro /dev/cd0 /cdrom, for example. 5. Change to the newly mounted file system, cd /cdrom, for example. 6. Proceed to the section entitled Preparing the display.5.8.2 Accessing the installation media using a downloaded image 1. If you have not already done so, log on to the system as the root user. 2. Create a temporary directory to contain the installation image and the compressed image files. This directory must be created on a file system which has approximately 2 GB of free space. Also, the directory must NOT contain a space anywhere in its path. For example, to create a directory in /usr called tarfiles, type the following command: mkdir /usr/tarfiles146 IBM TotalStorage Productivity Center: The Next Generation
    • 3. Download or copy the installation image to the temporary directory you created. 4. Change to the directory where you have stored the image, for example, cd /usr/tarfiles 5. Extract the image files by following the instructions supplied at the repository from which you downloaded the image. This may involve running the tar or gunzip commands, or a combination of both, for example, tar -xvf agentmanager.tar 6. Change to the installation directory that was created automatically which you extracted from the image. For example: cd EmbeddedInstaller5.8.3 Preparing the display This version of the Agent Manager installer uses a graphical, Java-based interface. If you are installing with a local graphical display, proceed to the next section entitled 5.6.4, “Beginning the installation” on page 128. However, if you are installing from a remote terminal session, you must setup an X-Windows display prior to beginning the installation process. First, you must start your local X-Windows server application. Examples are Hummingbird Exceed or Cygwin. Once your local X-Windows server application is running, you must set the DISPLAY variable on your host. You must know the IP address of the machine from which you intend to perform the installation. For example, if you IP address is 2.3.4.5, type the following command at the server’s command prompt: export DISPLAY=2.3.4.5:0.0 You can verify that the X-Windows environment is properly set up by executing the following command on the host: xclock If the environment is successfully configured, you will see a graphical clock display, similar to the one shown in Figure 5-22: Figure 5-22 Graphical clock display5.8.4 Beginning the installation Follow these steps to perform the installation of Agent Manager: 1. At the command prompt on the host, type the following command: ./setupAix.bin 2. The Agent Manager setup installer will open, and will prompt you to select an installation language. The prompt will appear similar to the one shown in Figure 5-23 on page 148. Chapter 5. TotalStorage Productivity Center installation on AIX 147
    • Figure 5-23 Agent Manager installation language selection 3. Select the language you wish to use for the installation from the drop-down box, then click OK. The Agent Manager setup wizard will then initialize. The first item to display will be the license agreement screen, and it will appear similar to the one shown in Figure 5-24. Figure 5-24 Agent Manager license agreement 4. Click the button labeled I accept the terms of the license agreement, then click Next. The installation location window displays, and appears similar to the one shown in Figure 5-25 on page 149.148 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-25 Agent Manager installation location5. The default location for installing Agent Manager is /opt/IBM/AgentManager. You may choose to change this location to suit your requirements. Once you have entered the installation location path in the Directory Name field, click Next. The installing panel displays, and appears similar to the one shown in Figure 5-26.Figure 5-26 Agent Manager installation progress Note: At this point, if you have an existing version of Agent Manager installed, it will be detected and you will be given a choice to upgrade to the latest version. If your Agent Manager version is older that 1.2, you must upgrade it. If you wish to upgrade, click Next. If not, click Cancel. Either way, the Agent Manager installer will continue. Chapter 5. TotalStorage Productivity Center installation on AIX 149
    • 6. The Agent Manager Registry Information window displays, and appears similar to the one shown in Figure 5-27. Figure 5-27 Agent Manager registry information 7. Click the option DB2 Universal Database™ at the top of the screen. The Database Name or Directory field contains the name of the database which Agent Manager will use. The default database name is IBMCDB. We recommend that you do not change this name. Then, select the Type of Database Connection used in your environment. If you are installing Agent Manager on the same server on which you installed DB2, then choose Local database. If you are installing Agent Manager on a separate server, then choose Remote database. Once you have made your selections, click Next. The Database Connection Information window displays, and appears similar to the one shown in Figure 5-28 on page 151.150 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-28 Agent Manager database connection information8. The Database Software Directory is the sqllib directory under the home directory of the instance owner. For example, if your instance name is db2inst1, then you would enter /home/db2inst1/sqllib. If you are installing Agent Manager on the same server as you installed DB2, you can also click Browse to navigate the directory structure and select the directory. Enter the user ID for the instance owner in the Database User Name field. Enter the password for the instance owner in the Database Password field. If you are installing Agent Manager on a separate machine from where you installed DB2, you must enter the host name of the DB2 server in the Host Name of the Database Server field, and the TCP port number in the Database Port field. The default port number for DB2 databases is 50000. Once you have completed this form, click Next. The WebSphere Application Server Information window displays, and appears similar to the one shown in Figure 5-29 on page 152. Chapter 5. TotalStorage Productivity Center installation on AIX 151
    • Figure 5-29 Agent Manager WebSphere Application Server information 9. Enter the fully qualified host name in the Host Name or Fully Qualified Host Name field. We recommend that you do not enter an IP address in this field. If you do, an information panel will display asking you to confirm the use of an IP address instead of a host name. The default name AgentManager is entered in the Application Server Name for Agent Manager field. We recommend that you do not change this from the default setting. The defaults of 9510, 9511, and 9512 are entered in the Registration Port, Secure Port, and Public Port and Secondary Port for the Agent Recovery Service fields, respectively. We recommend that you do not change these from their default settings. The Do not use port 80 for the agent recovery service option is unchecked by default, which means that port 80 will be used for this service. We recommend that you check this box. See the note below regarding this option. The Start the agent manager after the installation is complete and Autostart the agent manager each time this system restarts options are checked by default. We recommend that you leave these options checked. Note: By default, the Agent Manager agent recovery service will use port 80 for its communication. However, if your server functions as a Web server, or if you will install the IBM TotalStorage Productivity Center Graphical User Interface (GUI) Web access component, you should check the box labeled Do not use port 80 for the agent recovery service. This will avoid conflicts with Web services. Once you have completed this form, click Next. The Security Certificates screen displays, and appears similar to the on shown in Figure 5-30 on page 153.152 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-30 Agent Manager security certificates10.The default option is Create certificates for this installation. We recommend that you accept the default. Note: Tip: Earlier versions of TotalStorage Productivity Center encountered difficulty creating and distributing security certificates. In those versions, we recommended using the demonstration certificates. However, TotalStorage Productivity Center V3.1 has resolved these issues, and can create and distribute the certificates correctly. We have therefore updated our recommendation to create certificates during the installation process. Click Next after you have made your selection. If you chose the option to create certificates, the Security Certificate Settings window displays, and appears similar to the one shown in Figure 5-31 on page 154. Chapter 5. TotalStorage Productivity Center installation on AIX 153
    • Figure 5-31 Agent Manager security certificate settings 11.The Certificate Authority Name field contains TivoliAgentManagerCA by default. This name must be unique in your environment. We recommend you use the default setting unless it has already been used in your environment. the Security Domain field is automatically populated with your DNS information. We recommend you accept this default setting. the Certificate Authority Password field is blank by default. If you leave it blank, a random password will be generated by the system. We recommend you enter a password in this field, in case you need to unlock the certificate files in the future. The Agent Registration Password is changeMe. Despite its setting, we recommend that you do not change it. Once you have completed this form, click Next. The User Input Summary screen displays, and appears similar to the one shown in Figure 5-32 on page 155.154 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-32 Agent Manager user input summary12.Review the settings displayed on this screen. If you need to make changes, click Back. If you are ready to proceed with the installation, click Next. When you do, the Summary Information screen displays, and appears similar to the one shown in Figure 5-33.Figure 5-33 Agent Manager summary information13.When you have reviewed the summary information, click Next. The installation progress screen displays, and appears similar to the one shown in Figure 5-34 on page 156. Chapter 5. TotalStorage Productivity Center installation on AIX 155
    • Figure 5-34 Agent Manager installation progress 14.When the installation has finished, the installation results screen displays, and is similar to the one shown in Figure 5-35. Figure 5-35 Agent Manager installation results 15.When you have reviewed the results, click Next. The installation summary screen displays, and is similar to the one shown in Figure 5-36 on page 157.156 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-36 Agent Manager installation completed 16.Click Finish to close the installation wizard.5.8.5 Removing the CD from the server If you accessed the installation media using a CD, you should now unmount the CD and remove it from the system. To do this, complete the following steps: 1. Type the following at a host command prompt: umount /cdrom 2. Remove the CD from the drive by pressing the button on the front panel of the CD-ROM or DVD-ROM drive. This will eject the media tray. 3. Remove the CD from the media tray, and close the media tray by pressing the button again.5.9 Installing IBM TotalStorage Productivity Center for AIX After you have completed the installation of DB2 and Agent Manager, then you can install TotalStorage Productivity Center. In this chapter we document the Custom install. We show how you can select each component individually. While we do recommend the Custom install, you can select all components to be installed in one invocation of the installer.5.9.1 Order of component installation After installing the prerequisites, it is ideal to install the components in the following order: 1. DB Schema 2. Data Server 3. Device Server 4. GUI and CLI 5. Data agent and Device agent. Chapter 5. TotalStorage Productivity Center installation on AIX 157
    • Tip: We recommend that you install the Database Schema first. Then, install Data Server and Device Server in a separate step. If you install all the components in one step, if any part of the installation fails for any reason (for example space or passwords) the installation suspends and rolls back, uninstalling all the previous components.5.9.2 Accessing the installation media with a CD If you are accessing the installation media with a downloaded image, skip to the next section. Follow these steps to perform the installation of IBM TotalStorage Productivity Center V3.1: If you have not already done so, log on to the DB2 system as the root user. 1. Insert the CD into the CD-ROM or DVD-ROM drive on your system. 2. If you have not already done so, create a mount point for the media. For example, if you wish to mount the disc at /cdrom, type the mkdir /cdrom command. 3. Next, mount the disc in read-only mode at the mount point you created in the previous step, mount -o ro /dev/cd0 /cdrom for example, 4. Change to the newly mounted file system, cd /cdrom, for example. Proceed to the section entitled 5.8.3, “Preparing the display” on page 147, below.5.9.3 Accessing the installation media with a downloaded image Follow these steps to install the media with a downloaded image: 1. If you have not already done so, log on to the DB2 system as the root user. 2. Create a temporary directory to contain the installation image and the compressed image files. This directory must be created on a file system which has approximately 2 GB of free space. Also, the directory must not contain a space anywhere in its path. For example, to create a directory in /usr called tarfiles, type the following command: mkdir /usr/tarfiles 3. Download or copy the installation image to the temporary directory you created. 4. Change to the directory where you have stored the image, for example: cd /usr/tarfiles 5. Extract the image files by following the instructions supplied at the repository from which you downloaded the image. This might involve running the tar or gunzip commands, or a combination of both, tar -xvf TPC_3.1.0_aix_disk1.tar, for example.5.9.4 Preparing the display This version of the TotalStorage Productivity Center installer uses a graphical, Java-based interface. If you are installing with a local graphical display, please proceed to the next section entitled 5.6.4, “Beginning the installation” on page 128. However, if you are installing from a remote terminal session, you must setup an X-Windows display prior to beginning the installation process. First, you must start your local X-Windows server application. Examples are Hummingbird Exceed or Cygwin.158 IBM TotalStorage Productivity Center: The Next Generation
    • When your local X-Windows server application is running, you must set the DISPLAY variable on your host. You must know the IP address of the machine from which you intend to perform the installation. For example, if you IP address is 2.3.4.5, type the following command at the server’s command prompt: export DISPLAY=2.3.4.5:0.0 You can verify that the X-Windows environment is properly set up by executing the following command on the host: xclock If the environment is successfully configured, you will see a graphical clock display, similar to the one shown in Figure 5-37: Figure 5-37 Graphical clock display5.9.5 Sourcing the environment If you will be installing TotalStorage Productivity Center on the same server on which you installed DB2, you need to source the DB2 environment. For example, if you DB2 instance is named db2inst1, type the following command: . /home/db2inst1/sqllib/db2profile Note: You must install TotalStorage Productivity Center as the root user. However, you must still source the environment with the instance owner.5.9.6 Assigning file system ownership If you created file systems to contain DB2 tables and temporary space, you must change the owner of those file systems to the DB2 instance owner so that the appropriate database files can be created. For example, if you created the file system /dbfiles to house DB2 tables, and created the file system /dbtemp to house DB2 temporary storage, and your instance owner is db2inst1, issue the following command on your DB2 server: chown db2inst1 /dbfiles /dbtemp5.9.7 Installing the database schema Follow these steps to perform the installation of the database schema for TotalStorage Productivity Center: 1. At the command prompt on the DB2 host, type the ./setup.sh command. 2. The TotalStorage Productivity Center installer will open, and will prompt you to select an installation language. The prompt will appear similar to the one shown in Figure 5-38 on page 160. Chapter 5. TotalStorage Productivity Center installation on AIX 159
    • Figure 5-38 TotalStorage Productivity Center installation language selection 3. Select the language you wish to use for the installation from the drop-down box, then click OK. The TotalStorage Productivity Center setup wizard will then initialize. The first item to display will be the license agreement screen, and it will appear similar to the one shown in Figure 5-39. Figure 5-39 TotalStorage Productivity Center license agreement 4. Click the button labeled I accept the terms of the license agreement, then click Next. The installation types window displays, and appears similar to the one shown in Figure 5-40 on page 161.160 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-40 TotalStorage Productivity Center installation types5. Click Custom installation. In addition, you can change the TPC Installation Location from the default location of /opt/IBM/TPC to suit your requirements. Once you have filled out this form, click Next. The “Select one or more components to install” window displays, and appears similar to the one shown in Figure 5-41.Figure 5-41 TotalStorage Productivity Center component selection6. Deselect all the options except Create database schema. Then click Next. The database administrator information window displays, and appears similar to the one found in Figure 5-42 on page 162. Chapter 5. TotalStorage Productivity Center installation on AIX 161
    • Figure 5-42 TotalStorage Productivity Center database administrator 7. Enter the user ID for the DB2 instance owner in the Database administrator field, and the instance owner’s password in the Password field, then click Next. The database schema information window displays, and appear similar to the one shown in Figure 5-43. Figure 5-43 TotalStorage Productivity Center database schema information 8. You must enter the DB2 instance owner’s user ID in the DB user ID field, and the instance owner’s password in the Password field. Then you can choose which database connection type to use for TotalStorage Productivity Center: – If you are upgrading from a current version of TotalStorage Productivity Center, choose the option Use local database. Enter in the port, database name, full path, and instance name in the appropriate fields. – If this is a new installation (not an upgrade), choose the option Create local database. The default database name is TPCDB. We recommend that you do not change this name. After you have selected the database connection type which suits your requirements, click Schema creation details. The schema details window displays, and appears similar to the one shown in Figure 5-44 on page 163.162 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-44 TotalStorage Productivity Center database schema details9. The default entry in the Schema name field is TPC. We recommend that you do not change this from the default setting. You then have the option of placing the various table spaces in different directories or file systems, and for setting an initial database size. For all but the largest Enterprise deployments, database sizes of 200 MB should be sufficient for initial creation. For best performance in medium and Enterprise deployments, you should consider placing the table spaces on separate file systems and on separate disk devices. If you have already created these file systems, enter their paths in the Normal, Key, Big, and Temp fields, or click the Browse button to search for them. The Normal, Key, and Big databases can be housed in the same file system. The Temp database should be housed on a separate file system for best performance. The differences between choosing System managed (SMS) and Database managed (DMS) containers are discussed in 11.1, “Selecting an SMS or DMS tablespace” on page 510. If you select Database managed, you can enter a path in which to house log files, and an initial size. Log files should be housed on a separate fleshiest from the table spaces for best performance. For all but the largest Enterprise deployments, an initial size of 20 MB should suffice. After you have filled out the form, click OK. You will be returned to the database schema information window. In that window, click Next. The summary information window displays, and appears similar to the one shown in Figure 5-45 on page 164. Chapter 5. TotalStorage Productivity Center installation on AIX 163
    • Figure 5-45 TotalStorage Productivity Center install summary 10.Click Install to begin the database schema installation. A progress screen opens, and is similar to the one shown in Figure 5-46. Figure 5-46 TotalStorage Productivity Center installation progress 11.When the installation is complete, the installation results window displays, and appears similar to the one shown in Figure 5-47 on page 165.164 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-47 TotalStorage Productivity Center installation results 12.Click Finish to exit the installer.5.9.8 Installing Data server When you have finished creating the database schema, you are ready to install Data server. Follow these steps to complete the installation process for Data sever. 1. At the command prompt on the Data server host, in the installation media directory, type the ./setup.sh command. 2. The TotalStorage Productivity Center installer will open, and will prompt you to select an installation language. The prompt will appear similar to the one shown in Figure 5-48. Figure 5-48 TotalStorage Productivity Center installation language selection 3. Select the language you want to use for the installation from the drop-down box, then click OK. The TotalStorage Productivity Center setup wizard will then initialize. The first item to display will be the license agreement screen, and it will appear similar to the one shown in Figure 5-49 on page 166. Chapter 5. TotalStorage Productivity Center installation on AIX 165
    • Figure 5-49 TotalStorage Productivity Center license agreement 4. Click the button labeled I accept the terms of the license agreement, then click Next. The installation types window displays, and appears similar to the one shown in Figure 5-50. Figure 5-50 TotalStorage Productivity Center installation types 5. Click Custom installation. In addition, you can change the TPC Installation Location from the default location of /opt/IBM/TPC to suit your requirements. Once you have filled out this form, click Next. The Select one or more components to install window displays, and appears similar to the one shown in Figure 5-51 on page 167.166 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-51 TotalStorage Productivity Center component selection6. Deselect all the options except Data server. Then click Next. The database administrator information window displays, and appears similar to the one found in Figure 5-52.Figure 5-52 TotalStorage Productivity Center database administrator7. Enter the user ID for the DB2 instance owner in the Database administrator field, and the instance owner’s password in the Password field, then click Next. The database schema information window displays, and appears similar to the one found in Figure 5-53 on page 168. Chapter 5. TotalStorage Productivity Center installation on AIX 167
    • Figure 5-53 Data server database schema information 8. Enter the DB2 instance owner’s user ID in the DB user ID field, and the instance owner’s password in the Password field. – If you are installing Data server on the same machine on which DB2 is installed, check the option Use local database. The local database information should be populated automatically. Highlight the local database to be used. – If you are installing Data server on a separate machine, check the option Use remote database. The default database name is TPCDB, but if you created a database with a different name, enter it here. Enter the DB2 server’s host name in the Host name field. Enter the communication port number in the Port field. The default port number for DB2 is 50000. You will also need to enter the path to the JDBC™ driver. If your instance name is db2inst1, then the default path is /home/db2inst1/sqllib/java.db2jcc.jar. You can enter the path directly, or click Browse to search for it. When you have selected your database connection information and completed the form, click Next. The Data server information window displays, and appears similar to the one shown in Figure 5-54. Figure 5-54 Data server information168 IBM TotalStorage Productivity Center: The Next Generation
    • 9. If it is not already displayed, you must enter the fully qualified host name of the server on which you are installing TotalStorage Productivity Center in the Data server name field. The default port of 9549 is listed in the Data server port field. You may change this to suit your requirements, but we recommend that you do not change it. The adm group is listed by default in the TPC superuser field. We recommend that you do not change it. If you want to perform advanced security role mapping, click Security roles. If you do, the security roles mapping screen displays, and appears similar to the one shown in Figure 5-55.Figure 5-55 Data server security roles mapping You can optionally enter group names to map to each specific role in TotalStorage Productivity Center. This allows for more customized control over your management environment. When you have finished filling out the form click OK. The Data server information screen will display. If you want to discover Network Attached Storage (NAS) devices in your environment, click NAS discovery. The NAS discovery options window will display, and will appear similar to the one shown in Figure 5-56.Figure 5-56 Data server NAS discovery options Chapter 5. TotalStorage Productivity Center installation on AIX 169
    • You can add login information in the User name and Password fields in order to attach to Network Appliance storage devices. You can also add Simple Network Management Protocol (SNMP) community strings to search during the discovery process. To add an SNMP community, enter the community name in the SNMP community field and click Add. When you have finished filling out the form click OK. The Data server information screen will display. When you have finished making your selections, click Next. The Agent Manager information panel displays, and appears similar to the one shown in Figure 5-57. Figure 5-57 Agent Manager information 10.Enter the fully qualified host name of the Agent Manager server in the Hostname or IP address field. The Port (secured) and Port (Public) fields will be populated with the defaults of 9511 and 9513, respectively. We recommend that you do not change them. In the User ID field, enter manager. In the Password field for that ID, enter password. These are the defaults and cannot be changed. The default agent registration password is changeMe. Enter it, or the agent registration password you created during the Agent Manager installation, into the final Password field. When you have finished filling out the form click Next. The summary information window displays, and appears similar to the on shown in Figure 5-58. Figure 5-58 Data server installation summary170 IBM TotalStorage Productivity Center: The Next Generation
    • 11.Click Install. Data server installation begins. A progress window displays, and appears similar to the one shown in Figure 5-59. Figure 5-59 Data server installation progress 12.When the installation completes, an installation results window displays, and appears similar to the one shown in Figure 5-60. Figure 5-60 Data server installation results 13.Click Finish to close the installer.5.9.9 Installing Device server Follow these steps to complete the installation process for Device sever. 1. At the command prompt on the Device server host, in the installation media directory, type the ./setup.sh command. 2. The TotalStorage Productivity Center installer will open, and will prompt you to select an installation language. The prompt will appear similar to the one shown in Figure 5-61 on page 172. Chapter 5. TotalStorage Productivity Center installation on AIX 171
    • Figure 5-61 TotalStorage Productivity Center installation language selection 3. Select the language you want to use for the installation from the drop-down box, then click OK. The TotalStorage Productivity Center setup wizard will then initialize. The first item to display will be the license agreement screen, and it will appear similar to the one shown in Figure 5-62. Figure 5-62 TotalStorage Productivity Center license agreement 4. Click the button labeled I accept the terms of the license agreement, then click Next. The installation types window displays, and appears similar to the one shown in Figure 5-63 on page 173.172 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-63 TotalStorage Productivity Center installation types5. Click Custom installation. In addition, you can change the TPC Installation Location from the default location of /opt/IBM/TPC to suit your requirements. After you have com- pleted this form, click Next. The Select one or more components to install window displays, and appears similar to the one shown in Figure 5-64.Figure 5-64 TotalStorage Productivity Center component selection6. Deselect all the options except Device server. Then click Next. The database administrator information window displays, and appears similar to the one found in Figure 5-65 on page 174. Chapter 5. TotalStorage Productivity Center installation on AIX 173
    • Figure 5-65 TotalStorage Productivity Center database administrator 7. Enter the user ID for the DB2 instance owner in the Database administrator field, and the instance owner’s password in the Password field, then click Next. The database schema information window displays, and appears similar to the one found in Figure 5-66. Figure 5-66 Device server database schema information 8. Enter the DB2 instance owner’s user ID in the DB user ID field, and the instance owner’s password in the Password field. – If you are installing Device server on the same machine on which DB2 is installed, check the option Use local database. The local database information should be populated automatically. Highlight the local database to be used. – If you are installing Device server on a separate machine, check the option Use remote database. The default database name is TPCDB, but if you created a database with a different name, enter it here. Enter the DB2 server’s hos tname in the Host name field. Enter the communication port number in the Port field. The default port number for DB2 is 50000. You will also need to enter the path to the JDBC driver. If your instance name is db2inst1, then the default path is /home/db2inst1/sqllib/java.db2jcc.jar. You can enter the path directly, or click Browse to search for it.174 IBM TotalStorage Productivity Center: The Next Generation
    • Once you have selected your database connection information and filled out the form, click Next. The Device server information window displays, and appears similar to the one shown in Figure 5-67.Figure 5-67 Device server information9. If it is not already displayed, you must enter the fully qualified host name of the server on which you are installing TotalStorage Productivity Center in the Device server name field. The default port of 9550 is listed in the Device server port field. You may change this to suit your requirements, but we recommend that you do NOT change it. The adm group is listed by default in the TPC superuser field. We recommend that you do not change it. Enter a password in the Host authentication password field that will be used for fabric agents to communicate with the device server. The password should contain eight characters or less, and should contain only alphanumeric characters. The password is case-sensitive. Enter a user ID and password in the WAS admin ID and Password fields. This user ID and password is only used during the installation process by the Device server so that it can communicate with WebSphere. If you did not have a previous version of WebSphere installed, these entries can be anything. However, if you are installing Device server with an existing version of WebSphere, these must be the authentication credentials used by the installed version of WebSphere. If you want to perform advanced security role-mapping, click Security roles. If you do, the security roles mapping screen displays, and appears similar to the one shown in Figure 5-68 on page 176. Chapter 5. TotalStorage Productivity Center installation on AIX 175
    • Figure 5-68 Device server security roles mapping You can optionally enter group names to map to each specific role in TotalStorage Productivity Center. This allows for more customized control over your management environment. When you have finished filling out the form click OK. The Device server information screen will display. When you have finished making your selections, click Next. The summary information window displays, and appears similar to the on shown in Figure 5-69. Figure 5-69 Device server installation summary 10.Click Install. Device server installation begins. A progress window displays, and appears similar to the one shown in Figure 5-70 on page 177.176 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-70 Device server installation progress 11.When the installation completes, an installation results window displays, and appears similar to the one shown in Figure 5-71. Figure 5-71 Device server installation results 12.Click Finish to close the installer.5.9.10 Installing agents TotalStorage Productivity Center Data agents and Fabric agents use the same installation instructions. You can install either agent (or both agents together) using these directions. Follow these steps to complete the installation process for the agents. 1. At the command prompt on the agent host, in the installation media directory, type the ./setup.sh command. 2. The TotalStorage Productivity Center installer will open, and will prompt you to select an installation language. The prompt will appear similar to the one shown in Figure 5-72 on page 178. Chapter 5. TotalStorage Productivity Center installation on AIX 177
    • Figure 5-72 TotalStorage Productivity Center installation language selection 3. Select the language you wish to use for the installation from the drop-down box, then click OK. The TotalStorage Productivity Center setup wizard will then initialize. The first item to display will be the license agreement screen, and it will appear similar to the one shown in Figure 5-73. Figure 5-73 TotalStorage Productivity Center license agreement 4. Click the button labeled I accept the terms of the license agreement, then click Next. The installation types window displays, and appears similar to the one shown in Figure 5-74 on page 179.178 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-74 TotalStorage Productivity Center installation types5. Click Custom installation. In addition, you can change the TPC Installation Location from the default location of /opt/IBM/TPC to suit your requirements. After you have completed this form, click Next. The “Select one or more components to install” window displays, and appears similar to the one shown in Figure 5-75.Figure 5-75 TotalStorage Productivity Center component selection6. Deselect all the options except the agent(s) you wish to install. For example, you can leave Fabric agent checked. When you have finished selecting the agent(s) to install click Next. The Data server and Device server information window displays, and appears similar to the one shown in Figure 5-76 on page 180. Chapter 5. TotalStorage Productivity Center installation on AIX 179
    • Figure 5-76 Data server and Device server information 7. If they are not already displayed, you must enter the fully qualified host name of the Data server or the Device server in the appropriate fields, depending on which agents you are installing. The default ports of 9549 for Data server and 9550 for Device server are listed in the Data Server port and Device server port fields, respectively. You may change these to suit your requirements, but we recommend that you do not change them. The adm group is listed by default in the TPC superuser field. We recommend that you do not change it. If you are installing Fabric agent, you will need to enter the password used for authenticating with the Device server in the Host authentication password field. If you are installing Data agent, you can click Data agent options. If you do, the data agent options window displays, and is similar to the one shown in Figure 5-77. Figure 5-77 Data agent options There are two options, Agent should perform a scan when first installed, and Agent may run scripts sent by server. We recommend that you leave both options checked. However, if you are installing into a production environment and the agent host is heavily utilized, you may elect to uncheck the option Agent should perform a scan when first installed. This will use less resources on the agent host during the installation process.180 IBM TotalStorage Productivity Center: The Next Generation
    • The agent will not collect statistics about itself until a scan is scheduled by the TotalStorage Productivity Center administrator. When you have completed the options on this form click OK. The Data server and Device server information window will display. When you have finished making your selections, click Next. The common agent selection window displays, and appears similar to the one shown in Figure 5-78.Figure 5-78 Common agent selection8. If you have an existing Common agent installed, you can select the option Select an existing common agent from the list below. Highlight the common agent you want to use. If not, select the option Install the new common agent at the location listed below. You can change the installation path to suit your requirements by entering the path directly in the path field, or clicking Browse. When you have made your selection, click Next. The summary information window displays, and appears similar to the on shown in Figure 5-79.Figure 5-79 Agent installation summary9. Click Install. Agent installation begins. A progress window displays, and appears similar to the one shown in Figure 5-80 on page 182. Chapter 5. TotalStorage Productivity Center installation on AIX 181
    • Figure 5-80 Agent installation progress 10.When the installation completes, an installation results window displays, and appears similar to the one shown in Figure 5-81. Figure 5-81 Agent installation results Click Finish to close the installer.5.9.11 Installing the Java Graphical User and the Command Line Interface TotalStorage Productivity Center Data Java Graphical User Interface (GUI) and Command Line Interface (CLI) use the same installation instructions. You can install either interface (or both interfaces together) using these directions. You can install the interfaces on any of the TotalStorage Productivity Center servers, management consoles, or workstations. Follow these steps to complete the installation process for the interfaces. 1. At the command prompt on the interface host, in the installation media directory, type the following command: ./setup.sh182 IBM TotalStorage Productivity Center: The Next Generation
    • 2. The TotalStorage Productivity Center installer will open, and will prompt you to select an installation language. The prompt will appear similar to the one shown in Figure 5-82.Figure 5-82 TotalStorage Productivity Center installation language selection3. Select the language you wish to use for the installation from the drop-down box, then click OK. The TotalStorage Productivity Center setup wizard will then initialize. The first item to display will be the license agreement screen, and it will appear similar to the one shown in Figure 5-83.Figure 5-83 TotalStorage Productivity Center license agreement4. Click the button labeled I accept the terms of the license agreement, then click Next. The installation types window displays, and appears similar to the one shown in Figure 5-84 on page 184. Chapter 5. TotalStorage Productivity Center installation on AIX 183
    • Figure 5-84 TotalStorage Productivity Center installation types 5. Click Custom installation. In addition, you can change the TPC Installation Location from the default location of /opt/IBM/TPC to suit your requirements. When you have completed this form, click Next. The Select one or more components to install window displays, and appears similar to the one shown in Figure 5-85. Figure 5-85 TotalStorage Productivity Center component selection 6. Deselect all the options except the interfaces you want to install. For example, you can leave GUI checked. When you have finished selecting the interfaces to install, click Next. The Data server and Device server information window displays, and appears similar to the one shown in Figure 5-86 on page 185.184 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-86 Data server and Device server information7. If they are not already displayed, you must enter the fully qualified host name of the Data server and/or the Device server in the appropriate fields. The default ports of 9549 for Data server and 9550 for Device server are listed in the Data Server port and Device server port fields, respectively. You may change these to suit your requirements, but we recommend that you do not change them. The adm group is listed by default in the TPC superuser field. We recommend that you do not change it. You will also need to enter the password used for authenticating with the Device server in the Host authentication password field. When you have finished making your selections, click Next. The summary information window displays, and appears similar to the on shown in Figure 5-87.Figure 5-87 Interface installation summary8. Click Install. Interface installation begins. A progress window displays, and appears similar to the one shown in Figure 5-88 on page 186. Chapter 5. TotalStorage Productivity Center installation on AIX 185
    • Figure 5-88 Interface installation progress 9. When the installation completes, an installation results window displays, and appears similar to the one shown in Figure 5-89. Figure 5-89 Interface installation results Click Finish to close the installer.5.10 Installing the user interface for access with a Web browser This section details how to setup the TotalStorage Productivity Center Graphical User Interface (GUI) for use with a Web browser. To distribute the GUI with a Web browser, there are two prerequisites which must be met: 1. The Java-based GUI must be installed on the system that will act as the Web server. 2. A Web application server must be installed. Examples of this are Microsoft Internet Information Server (IIS) or IBM HTTP Server. For more information about installing IIS on Windows 2003 refer to 4.8.1, “Installing Internet Information Services (IIS)” on page 108.186 IBM TotalStorage Productivity Center: The Next Generation
    • After the prerequisite software has been installed, distributing the GUI with a Web interface is mostly a matter of configuring the Web application server.5.10.1 Distributing the Graphical User Interface with a Web browser Follow the instructions in this section to set up your environment to distribute the Graphical User Interface (GUI) with the Web when you are using AIX systems. 1. If you have not already done so, log in as the root user on the AIX system which you will use as a Web server. 2. Install the TotalStorage Productivity Center GUI if it is not already installed on this system. Refer to “Installing the Java Graphical User and the Command Line Interface” on page 182 for detailed instructions. 3. If you already have a Web application server installed, proceed to “Configuring the Web application server” on page 191. If not, you can follow the instructions in the next section to download and install IBM HTTP Server. Installing IBM HTTP Server If you do not already have a Web application server installed, you can download and install IBM HTTP Server. This package is based on the Apache Geronimo open source project. Your server must have a minimum of 512 MB of RAM, and 1 GB of free disk space in order to install IBM HTTP Server. You will also need an additional 1 GB of free space to temporarily house the software image and uncompressed installation files. Follow these steps to download an installation image of IBM HTTP Server: 1. Enter the following URL into your Web browser: http://www.ibm.com/software/webservers/httpservers 2. Click on the link on that page to download the latest version of IBM HTTP Server. As of this writing, the latest version was 6.0.2.0. 3. Follow the instructions for downloading the image to a temporary location on your system. Note: Registration at the ibm.com® Web site is required. There is no charge to download the software. 4. Change to the location where you stored the image file. For example: cd /tarfiles 5. Extract the compressed image files. For example, if you downloaded Version 6.0.2.0, you would type the following command: tar -xvf ihs.6020.aix.ppc32.tar 6. Change to the installation directory that was created automatically during the image extraction. For example: cd IHS Preparing the display This version of the IBM HTTP Server installer uses a graphical, Java-based interface. If you are installing using a local graphical display, proceed to the next section entitled “Beginning the installation” on page 188. However, if you are installing from a remote terminal session, you must set up an X-Windows display prior to beginning the installation process. Chapter 5. TotalStorage Productivity Center installation on AIX 187
    • First, you must start your local X-Windows server application. Examples are Hummingbird Exceed or Cygwin. Once your local X-Windows server application is running, you must set the DISPLAY variable on your host. You must know the IP address of the machine from which you intend to perform the installation. For example, if you IP address is 2.3.4.5, type the following command at the server’s command prompt: export DISPLAY=2.3.4.5:0.0 You can verify that the X-Windows environment is properly set up by executing the following command on the host: xclock If the environment is successfully configured, you will see a graphical clock display, similar to the one shown in Figure 5-37 on page 159: Figure 5-90 Graphical clock display Beginning the installation To start the installation, follow these steps: 1. In the installation directory, type the following command: ./install The graphical installation displays, and appears similar to the one shown in Figure 5-91. Figure 5-91 IBM HTTP Server installer welcome screen 2. Click Next. The license agreement screen displays, and appears similar to the one shown in Figure 5-92 on page 189.188 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-92 IBM HTTP Server license agreement3. Choose I accept the terms in the license agreement and click Next. The installation location screen displays, and appears similar to the one shown in Figure 5-93.Figure 5-93 IBM HTTP Server installation location4. The default installation location is /usr/IBMIHS. You may change the installation location to suit your requirements by entering a path in the Directory Name field or by clicking Browse to search for it. Once you have entered the installation location, click Next. The setup type screen displays, and appears similar to the one shown in Figure 5-94 on page 190. Chapter 5. TotalStorage Productivity Center installation on AIX 189
    • Figure 5-94 IBM HTTP Server installation type selection 5. Select Typical, then click Next. The installation summary screen displays, and appears similar to the one shown in Figure 5-95. Figure 5-95 IBM HTTP Server installation summary 6. Click Next to begin the installation. A progress screen displays, and appears similar to the one shown in Figure 5-96 on page 191.190 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 5-96 IBM HTTP Server installation progress When the installation is complete, an installation results screen displays, and appears similar to the one shown in Figure 5-97.Figure 5-97 IBM HTTP Server installation results7. Click Finish to close the installer.Configuring the Web application serverThis section assumes that you are configuring a single instance of a Web application serverand that no other Web services are configured (with the exception of the standardTotalStorage Productivity Center services). If you are installing on a shared Web applicationserver on which other Web services are configured, you must tailor the configuration shownhere to your specific environment. Chapter 5. TotalStorage Productivity Center installation on AIX 191
    • Configuring the IBM HTTP Server for AIX 1. Edit the httpd.conf file. If you installed IBM HTTP Server in the default location, you can find the file at /usr/IBMIHS/conf/httpd.conf. In Section 2 of the file, locate the following line: DocumentRoot "/usr/IBMIHS/htdocs/en_US" Change the text in quotes to point to the location where the TotalStorage Productivity Center GUI is installed. If you installed it at the default location, your edited line would look like this: DocumentRoot "/opt/IBM/TPC/gui" Note: The path is case-sensitive. 2. Farther down in the same section, locate the following line: <Directory "/usr/IBMIHS/htdocs/en_US"> Change the text in quotes to point to the location where the TotalStorage Productivity Center GUI is installed. If you installed it at the default location, your edited line would look like this: <Directory "/opt/IBM/TPC/gui"> Note: The path is case sensitive. 3. Farther down in the same section, locate the following line: DirectoryIndex index.html index.html.var At the end of the line, add a space, and then type TPCD.html. Your edited line will look like this: DirectoryIndex index.html index.html.var TPCD.html 4. Save the changes you made to the file. Important: If you installed the IBM HTTP Server on the same machine that is running Agent Manager, and Agent Manager is using TCP port 80 for the agent recovery service, you will have to configure the Web server to listen on a different port than 80, which is the default for HTTP requests. To do this, locate the line in Section 1 of the httpd.conf file that looks like this: Listen 80 Change the number 80 to an unused port. For example, you might configure the HTTP server to listen on port 8000. Then, when you attempt to access the GUI with the Web server, you must append the port number to the URL. For example: http://myserver.com:8000 5. Start your Web application server. For IBM HTTP server installed at the default location, the command is: /usr/IBMIHS/bin/apachectl start 6. If you want the Web application server to start automatically every time the server is booted, edit the /etc/inittab file and add the following line to it: ibmihs:2:once:/usr/IBMIHS/bin/apachectl start >/dev/console 2>&1192 IBM TotalStorage Productivity Center: The Next Generation
    • 7. Open a Web browser and enter your Web application server’s fully qualified name in the URL field, for example: http://myserver.com8. You should initially see the TotalStorage Productivity Center welcome screen, which appears similar to the one shown in Figure 5-98.Figure 5-98 TotalStorage Productivity Center welcome screen You must leave this window open while you are using the GUI. The GUI applet will be downloaded to your system automatically. You must answer Yes to the security questions regarding the installation of the security certificate. When the GUI finishes loading the logon box displays, and appears similar to the one shown in Figure 5-99.Figure 5-99 GUI logon9. Enter a valid user ID and password in the appropriate fields and click OK. The GUI displays, and appears similar to the one shown in Figure 5-100 on page 194. Chapter 5. TotalStorage Productivity Center installation on AIX 193
    • Figure 5-100 Web GUI194 IBM TotalStorage Productivity Center: The Next Generation
    • 6 Chapter 6. Agent deployment TotalStorage Productivity Center uses different methods to collect information from the various systems and to interact with them to give you a complete view of the environment and a single point of control for your storage infrastructure. These methods are: SMI-S through Common Information Model (CIM) agents to communicate and interact with Storage Subsystems, Tape Libraries and Switches Simple Network Management Protocol (SNMP) Software agents on the attached servers (Data Agent and Fabric Agent) Proprietary interfaces (for only a few devices) This chapter discusses the function of the Data Agent and the Fabric Agent and provides a description of the various methods and necessary steps to roll out the agent infrastructure to your managed servers and computers.© Copyright IBM Corp. 2006. All rights reserved. 195
    • 6.1 Functional overview: Which agents do I need? Although you can run TotalStorage Productivity Center without the Data Agents and the Fabric Agents being present on your servers, this gives you only limited functionality and an incomplete view of your infrastructure. As shown in Figure 6-1, the Data Agents and Fabric Agents interact with each component of the TotalStorage Productivity Center product. CIM TPC Agent for Disk Storage and Tape Topology Viewer Subsystems TPC central Data Agent Fabric Agent TPC for Data DB Computers Proprietary SNMP TPC API for Fabric SAN Components Figure 6-1 TotalStorage Productivity Center V3.1 Information Flow The TotalStorage Productivity Center components collect data about the infrastructure using the Data Agents and Fabric Agents along with other information sources (CIM agents and SNMP) and, in turn, feed the central TotalStorage Productivity Center database. The TotalStorage Productivity Center for Data and Fabric components also use the Data Agent and the Fabric Agent to initiate and perform management and configuration tasks on the servers and the fabric devices. The TotalStorage Productivity Center Topology Viewer (see Chapter 9, “Topology viewer” on page 415) as a central common interface to all TotalStorage Productivity Center components reads the data from the central database fed by the various product components, combines and correlates it. As a result, this produces a complete end-to-end view of your server and storage infrastructure.6.1.1 Types of agents TotalStorage Productivity Center uses four different types of agents to gather data about the devices and servers to be managed and monitored. Different combinations of these agents are required to effectively enable the functions of Data Manager, Fabric Manager, Disk Manager, and Tape Manager. In addition to these manager functions, the topology viewer is greatly affected by the proper discovery of all the managed entities in the management scope of TotalStorage Productivity Center. CIMOM agents These agents are provided by the vendor of the storage device, fabric switch, or tape library. For storage, they are needed for storage asset information, provisioning, alerting, and performance monitoring. For fabric switches, they are used only for performance monitoring. For tape libraries, they are used for asset and inventory information.196 IBM TotalStorage Productivity Center: The Next Generation
    • Data agents These are the traditional Tivoli Storage Resource Manager agents. They are installed on every computer system you want TotalStorage Productivity Center to manage. This is commonly referred to as an Agents Everywhere methodology. These 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, Novell NDS tree information, and NAS device information. In TotalStorage Productivity Center, you can create pings, probes, and scans to run against the servers that have Data agents installed. Data agents can be remotely installed only by running the TotalStorage Productivity Center agent installer from the TotalStorage Productivity Center server machine. This will install both the common agent and the Data agent. Fabric agents These are the traditional Tivoli SAN Manager agents. They are installed on computer systems that have fiber connectivity (through HBAs) into the SAN fabrics you want to manage and monitor. 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, nor is it possible to do so. You can only remotely deploy Fabric agents from the TotalStorage Productivity Center server. If you run the agent installer from the TotalStorage Productivity Center server to remotely deploy Fabric Agents, the common agent must already be installed, and registered to the Agent Manager with which TotalStorage Productivity Center is associated. If you install the Fabric agent locally on the server, the installer installs the common agent for you. Out of Band Fabric (OOBF) agents Out Of Band Fabric (OOBF) agents are used to collect topology information from fabric switches through the IP network using SNMP queries to the switches. These agents discover less information than fabric agents. You must have an OOBF agent pointing to each switch in each SAN fabric you are managing. If the switches are behind private IP networks, as is normally the case with McData, you will not be able to use OOBF agents. OOBF agents are also required to collect zoning information for Brocade switches (where the admin user ID and password are needed), and VSAN information for Cisco switches. TotalStorage Productivity Center only responds to SNMP V1 queries. If the switches that you register OOBF agents to use SNMP V2 or V3, the agent does not work. You must either reconfigure the switch to use SNMP V1, if possible, or rely on fabric agents to collect switch information for these switches.6.1.2 TotalStorage Productivity Center component use of agents Although all TotalStorage Productivity Center components use the server agents, the contribution of the agents to the various components differ considerably. The following considerations provide some guidelines to determine if the deployment of a server agent infrastructure should be pursued. The TotalStorage Productivity Center for Disk mainly operates on the basis of SMI-S through CIM agents. Complete subsystem and tape-information collection, device management, Chapter 6. Agent deployment 197
    • performance management, monitoring and alerting is performed through this path. There are reports within the TotalStorage Productivity Center for Disk component, correlating storage subsystem information and information about computers which would not be available without the presence of Data Agents out on the servers. So the capabilities of TotalStorage Productivity Center for Disk can be exploited almost completely without a server agent infrastructure. The TotalStorage Productivity Center for Fabric is designed to use three communication paths to gather information and interact with the fabric devices. However, at the time of writing, SMI-S can be used solely for switch-performance data collection and performance monitoring and alerting. Fabric configuration and status collection as well as fabric management (such as zone control) are either performed out-of-band or in-band through the Fabric Agents. Which one of these two ways TotalStorage Productivity Center actually employs is determined by the particular fabric components and is documented on the TotalStorage Productivity Center for Fabric Support Web site: http://www-306.ibm.com/software/sysmgmt/products/support/IBM_TSANM_Device_Compatibility.html To sum up, a decision whether or not the Fabric Agent should be deployed is largely determined by the fabric components which are to be managed. TotalStorage Productivity Center for Data receives almost all the information it provides in its reports and repositories solely through the Data Agents on the managed servers and computers. It also relies on the presence of a Data Agent infrastructure to perform policy driven management. Although TotalStorage Productivity Center for Data can also receive some information directly from the storage subsystems through CIM agents without the presence of any Data Agents, we recommend this only for very special requirements because this would limit the overall product capabilities to a large extent. The TotalStorage Productivity Center Topology Viewer is able to deliver a complete and meaningful end-to-end view of the server and storage-infrastructure only if both agents, the Data Agent and the Fabric Agents, are present on the managed computers. This end-to-end view of the infrastructure and the graphical presentation of the links and relations between the different elements of the environment is one of the big advantages of the Topology Viewer. Without the presence of the Data Agent and the Fabric Agents, most information about the attached servers and computers would be missing. If you use switches which support out-of-band discovery of the SAN infrastructure, only the SAN ports of the servers and computers would be depicted in the Topology Viewer. They would appear in the Other Group with their WWNNs as a label. In this case, you would be able to label the depicted SAN ports manually and classify them as Computers. If you use switches which support only in-band fabric discovery, the servers and computers would be missing in the Topology Viewer altogether. In both cases, the relationship between storage subsystem volumes and the managed computers would not be presented in the Topology Viewer. The following figures show two examples to give you an idea of the capabilities of the Topology Viewer with and without the server agents having been deployed. Figure 6-2 on page 199 shows an environment where several computers are present, but none of them has any agents installed. The switch is an IBM 2005-B32 and supports out-of-band infrastructure discovery. TotalStorage Productivity Center is able to discover the the HBAs of the computers. The Topology Viewer depicts them in the category Other and labels them with their WWNNs. The status is unknown.198 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 6-2 Topology viewer without agents deployed to the managed serversFigure 6-3 on page 200 shows the same environment, but this time the Data Agent and theFabric Agent have been deployed on the computers. Now TotalStorage Productivity Centerdiscovers them correctly as Computers and is able to display status information and evenmore details in the subsequent layers of the Topology Viewer. Chapter 6. Agent deployment 199
    • Figure 6-3 Topology viewer with agents deployed to the managed servers Recommendation: Except for limited, well-defined requirements, we strongly recommend the deployment of the server agents infrastructure regardless of the TotalStorage Productivity Center component being used.6.2 Agent infrastructure overview The TotalStorage Productivity Center server agent infrastructure is built on the Tivoli Common Agent Services infrastructure and is described in detail in 2.5, “Tivoli Common Agent Services” on page 32 and in the IBM TotalStorage Productivity Center Installation and Configuration Guide, GC32-1774. At the heart of the Tivoli Common Agent Services infrastructure, the Tivoli Agent Manager provides authentication and authorization services and maintains a registry of configuration information about the managed computer systems in your environment. Those computers run the Tivoli Common Agent software which acts as a container to application-specific agent code such as the TotalStorage Productivity Center Data and Fabric Agent. Those application-specific agents are called subagents. The Common Agent software provides common services, shared machine resources, and secure connectivity for the subagents. Management applications such as the TotalStorage Productivity Center use the services of the Agent Manager to communicate securely with and to obtain information about the computer systems running the Tivoli Common Agent software. They are also able to interact directly with the subagents using their native protocols. Figure 6-4 on page 201 shows an overview of the TotalStorage Productivity Center server agent infrastructure:200 IBM TotalStorage Productivity Center: The Next Generation
    • Tivoli Common Agent Port 9510 Subagents Fabric Agent Data Agent Port 9550 Ports 9511, native Protocol Tivoli 9512, 9513 Port 9549 IBM TotalStorage Agent Manager Server Authentication and Productivity Center Server Agent Registration authorization services Central TPC Database Database Figure 6-4 TotalStorage Productivity Center server agent infrastructure The Tivoli Agent Manager can be installed on the same server as the TotalStorage Productivity Center Server or can run on a different machine (for example, larger installations or in cases where an Tivoli Common Agent Services infrastructure is already in place). The Tivoli Agent Manager is installed in a separate step with its own installer. The installation is discussed in detail in 4.6.1, “Agent Manager installation for Windows” on page 83 . The Tivoli Common Agent, which has to be present on each managed computer as the container for the Data Agent and Fabric Agent, is installed during the TotalStorage Productivity Center Agent installation with the TotalStorage Productivity Center Installer, and is discussed in detail in the subsequent sections.6.3 Agent deployment options There are two ways of deploying the Tivoli Common Agent and the TotalStorage Productivity Center Data and Fabric Agent. You can choose between local installation and remote installation. If you decide for local installation, you can either install the agents interactively or perform a unattended (silent) installation. Remote installation can only be performed interactively.6.3.1 Local 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 TotalStorage Productivity Center Installer will check if there is a Tivoli Common Agent already installed. If not, TotalStorage Productivity Center 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). Chapter 6. Agent deployment 201
    • 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.6.3.2 Remote installation 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 TotalStorage Productivity Center agents. The TotalStorage Productivity Center 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. You can install all required agent components remotely, the Tivoli Common Agent as well as the Data Agent and the Fabric Agent. 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 TotalStorage Productivity Center Installer manages the proper sequence. The remote installation of the Data Agent can be performed from any computer running one of the supported operating systems and having a network connection to the remote target computers. The Fabric Agent installation has to be performed from the same system, where the TotalStorage Productivity Center Server is installed and running. A remote agent installation is always interactive. Unattended (silent) remote installation is not supported at the time of writing. In the following sections we will guide you through both agent deployment methods.6.4 Local installation of Data and Fabric Agents This section guides you through the local installation of the TotalStorage Productivity Center Data Agent and Fabric Agent. Before you can start to install the Agents, you must verify that the TotalStorage Productivity Center Server and the Tivoli Agent Manager are installed and running and can both be reached over the network. For a successful installation, you must provide the following information: The host name or the IP Address of the Data Server The port to communicate with the Data Server The host name or the IP Address of the Device Server The port to communicate with the Device Server The host authentication password The host name or the IP Address of the Tivoli Agent Manager Server The host name or the IP Address of the Tivoli Agent Manager Server The ports to communicate with the Tivoli Agent Manager Server The Common Agent registration password202 IBM TotalStorage Productivity Center: The Next Generation
    • 6.4.1 Interactive installation Start the TotalStorage Productivity Center Installer by running setup.exe on Microsoft Windows systems and setup.sh on UNIX and LINUX systems. These programs in the root directory of the installation CD. In the following screen captures, we show the dialog windows of an installation on a Windows platform. While here in this book, we install Data Agent and Fabric Agent at the same time, of course you can install the Data Agent or the Fabric Agent separately. 1. In the first panel, select the preferred language for the installer as shown in Figure 6-5. Figure 6-5 Local interactive installation, language selection Click Ok. 2. The International Program License Agreement is shown (Figure 6-6). Read the terms and select I accept the terms of the license agreement. Figure 6-6 Local interactive installation, License agreement Click Next to continue. 3. In Figure 6-7 on page 204 you can choose the type of installation. We recommend you always use Custom Installation when you install the agents. Select Custom Installation. In this same panel, you can also choose the installation path of the agents. The default is C:Program FilesIBMTPC under Windows and /opt/IBM/TPC under UNIX and LINUX. In our example we keep the defaults. Note that the installer not only installs files in the location you specify in this panel. There are also some files installed to the C:Program FilesTivoliep Directory under Windows and the /usr/Tivoli/ep Directory under LINUX and UNIX. Chapter 6. Agent deployment 203
    • Make sure, the installation location you specify in this panel is empty. Otherwise the installer fails. Figure 6-7 Local interactive installation, Type of installation, installation location Click Next to continue. 4. In the panel in Figure 6-8, select which components of TotalStorage Productivity Center you want to install. Select only Data Agent and Fabric Agent. Deselect any other options. Figure 6-8 Local interactive installation, component selection Click Next to continue. 5. In the panel shown in Figure 6-9 on page 205, enter the following information: – Data Server Name This is the fully qualified host name or the IP address of the machine on which the TotalStorage Productivity Center Data Server and Device Server are running. At the time of writing, the Data Server and the Device Server must be installed on the same machine, so the Data Server Name and the Device Server Name will always be the same. In our environment, the TotalStorage Productivity Center Server is on gallium.almaden.ibm.com.204 IBM TotalStorage Productivity Center: The Next Generation
    • – Data Server Port The Data Agent uses the Data Server Port to communicate with the Data Server. It is set when you install the Data Server. We recommend keeping the default, 9549. – Device Server Name This is is the fully qualified host name or the IP address of the Device Server. In TotalStorage Productivity Center V3.1 it has to match with the Data Server Name. In our environment the name of the Data Server and Device Server is gallium.almaden.ibm.com. – Device Server Port. The Fabric Agent uses the Device Server Port to communicate with the Device Server. It is set when installing the Device Server. We recommend keeping the default, 9550. – Host authentication password. This is the password used by the Fabric Agent to communicate with the Device Server. You specify this password when you install the Device Server.6. Select options for the Data Agent, as shown in Figure 6-9.Figure 6-9 Local interactive installation, server and agent settings Click Data Agent Options. The panel in Figure 6-10 on page 206 is displayed. Here, you have two options: – Agent should perform a scan when first installed This option is selected by default. We suggest you accept this default, so that you make sure your Data Server receives a solid information base about your computer right after installation. Deselect this option if you do not want to have the Data Agent perform an initial scan of your computer after installation. – Agent may run scripts sent by server This option is checked by default. The advantage of enabling this option is that you can store scripts in the servers scripts directory, and do not have to keep a copy of the script on every agent computer. When a script must be run on a particular agent, the server accesses the script from its local scripts directory and sends it to the appropriate agent. If you deselect Agent may run scripts sent by server, you must make sure that the script is stored in every agents scripts directory. Chapter 6. Agent deployment 205
    • Note: If a script with the same name exists on both the server and the agent, the script stored on the agent will take precedence. This is useful if you want to run a special version of a script on one of your agents, while running a different version of the same script across all the other agents in your environment. Figure 6-10 Local interactive installation, Data Agent setting Click OK to continue. This will bring you back to the panel shown in Figure 6-9 on page 205 where you will have to click Next. 7. In the next panel shown in Figure 6-11 on page 207 you must enter the fully qualified host name or IP address of the Tivoli Agent Manager. Tivoli Agent Manager must already be installed and running. The Tivoli Agent Manager may run on the same machine as your TotalStorage Productivity Center Server, or on a separate machine. In our environment, we installed the Tivoli Agent Manager on the TotalStorage Productivity Center Server. You also must specify the ports which the agents use to communicate with the Tivoli Agent Manager. They are specified during the installation of the Agent Manager. We recommend keeping the default ports, which are 9511 (secure) and 9513 (public). Finally, enter the Common Agent Registration password. This is the password required by the Common Agent to register with the Agent Manager. It is specified when you install the Agent Manager. The default password is changeMe. Note: If you do not specify the correct Agent Manager password, you are not permitted to continue the installation.206 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 6-11 Local interactive installation, Tivoli Agent Manager information Click Next to continue.8. The Common Agent selection panel is displayed (Figure 6-12). If a Tivoli Common Agent is already running (for example, when you install a Fabric Agent and a Data Agent is already installed, or vice versa), you can choose to install your agent under the control of this Common Agent by selecting it in the lower selection box. If a Common Agent is not already installed on the system, you must elect to install it and specify a location. The default location is C:Program FilesIBMTPCca under Windows and /opt/IBM/TPC/ca under UNIX and LINUX.Figure 6-12 Local interactive installation, Common Agent options9. If you click Window Service Info in Figure 6-12l, you open the Common Agent Service Information Panel (Figure 6-13 on page 208). This information is optional. You can enter a Common Agent service name, user ID, and password that the Installer will use to create a Windows service for the Common Agent. Otherwise, by default itcauser is created. Chapter 6. Agent deployment 207
    • Figure 6-13 Local interactive installation, Common Agent services name and user information 10.Enter the information and click OK. This returns you to the panel shown in Figure 6-12 on page 207, where you click Next. 11.The Summary information panel is displayed (see Figure 6-14). You can review some of the information you have entered during the installation process. Figure 6-14 Local interactive installation, summary information panel Click Install to continue. The installer begins to install the Data Agent first (Figure 6-15 on page 209) and then the Fabric Agent (Figure 6-16 on page 209).208 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 6-15 Local interactive installation, installing the Data AgentFigure 6-16 Local interactive installation, installing the Fabric Agent Important : Although you could Cancel the installation while the progress bars are displayed, we strongly recommend that you not do this. An inconsistent state of your system might be the result.Finally a panel is displayed announcing that the installation has finished successfully, asshown in Figure 6-17 on page 210. Chapter 6. Agent deployment 209
    • Figure 6-17 Local interactive installation, installation complete 12.Click Finish to exit the installer.6.4.2 Unattended (silent) installation For an unattended (silent) installation of the agents, you must set up a special response file for the TotalStorage Productivity Center Installer. TotalStorage Productivity Center provides an example response file for the agent installation which you can modify according to your environment. The name of this response file is setup_agents.iss. It is located in the root directory of Disk 1 of the installation CDs. There are variables for all the information you can supply during the interactive installation. They are summarized in Example 6-1. Example 6-1 Local unattended installation, response file variables -V LICENSE_ACCEPT_BUTTON="true" -V LICENSE_REJECT_BUTTON="false" -P installLocation="/opt/IBM/TPC" -V varCreateDBSchm="false" -V varInstallDataSrv="false" -V varInstallDevSrv="false" -V varInstallGUI="false" -V varInstallCLI="false" -V varInstallDataAgt="true" -V varInstallDevAgt="true" -V varAMHostname="gallium.almaden.ibm.com" -V varAMRegPort="9511" -V varAMPubPort="9513" -V varCAPort="9510" -V varCAPassword="changeMe" -V varCAInstallLoc="/opt/IBM/TPC/ca" #-V varCASvcName= #-V varCASvcUsrID= #-V varCASvcUsrPW= -V varInstallNewCA="true" -V varUseOldCA="false" -V varDataSrvName="gallium.almaden.ibm.com" -V varDataSrvPort="9549"210 IBM TotalStorage Productivity Center: The Next Generation
    • -V varDevSrvName="gallium.almaden.ibm.com" -V varDevSrvPort="9550" -V varHostAuthUsrPW="tpctpc" #-V varDataAgtScan="true" #-V varDataAgtScripts="true" However, as with the interactive installation, the variables most often will be used with their default values and need not to be touched when preparing the response file. Normally, you must review at least the variables in bold in Example 6-1 on page 210, on a LINUX system, for example. You should also check that the the target directory you specify is empty. Otherwise, the unattended (silent) installation fails. After having modified and reviewed the response file according to your needs, you can start the installer with the following command, executed from within the directory in which the response file is located as shown in Example 6-2. Example 6-2 Microsoft Windows and Linux and Unix local unattended installation setup.exe -options "setup_agents.iss" -silent (for Windows) ./setup.sh -options "setup_agents.iss" -silent (for LINUX and UNIX) The installer exits with a return code which can be used in your scripts. In addition, you should verify that the installation has completed successfully using the methods summarized in 6.6, “Verifying the installation” on page 223.6.5 Remote installation of Data and Fabric Agents This section guides you through the necessary steps to perform a remote installation of the TotalStorage Productivity Center Data and Fabric Agents. You can only perform a remote installation interactively. At the time of writing, an unattended (silent) remote installation is not supported. You can perform remote agent installations to machines running either Windows (same domain or different domain), LINUX or UNIX operating systems. You must install the Data Agent before installing the Fabric Agent to a remote computer. The Common Agent is only installed with the Data Agent. The remote installation of the Fabric Agent requires that the Common Agent be installed and running on the target computer. So either install the Data Agent first, and then the Fabric agent, or install both agents together. In the latter case, the TotalStorage Productivity Center Installer performs in the proper sequence. Chapter 6. Agent deployment 211
    • 6.5.1 Preparing the remote installation Before you can start to install the agents, you must verify that the TotalStorage Productivity Center Server and the Tivoli Agent Manager are installed and running. You can install the Data Agents from any workstation having a network connection to the target machine. However, you can perform a remote installation of the Fabric Agent only from the server where the Device Server is installed and running. 1. For a successful installation, you must provide the information summarized here: – The fully qualified host name or the IP address of the computers on which you want to install the agents – A user ID and password that has administrative privileges on each of the the target computers For Windows systems, the user ID must be a local administrative account on the target computer (not a domain administrative account). When installing to a foreign Windows domain, the domain from which you are installing has to trust the foreign domains, and your login must be an administrator on the local box (the computer from which you are installing) and a domain administrator on the foreign domains. – The host name or the IP Address of the Data Server – The port to communicate with the Data Server – The host name or the IP Address of the Device Server – The port to communicate with the Device Server – The host authentication password – The host name or the IP Address of the Tivoli Agent Manager Server – The host name or the IP Address of the Tivoli Agent Manager Server – The ports to communicate with the Tivoli Agent Manager Server – The Common Agent registration password Disk 1 of the TotalStorage Productivity Center installation CDs permits only a remote installation of the Fabric Agent, which requires a Common Agent already running on the target computer. Note: For a remote installation of the Data Agent and the Common Agent, you must use Disk 2 of the TotalStorage Productivity Center Installation CDs together with the CD containing the cross-platform agent files. 2. For a remote installation of the Data Agent and the Common Agent, you must copy the installation files from Disk 2 of the product installation CDs together with the cross-platform agent files to a local directory of the machine from which you initiate the remote installation. For this, copy the content of Disk 2 of the TotalStorage Productivity Center installation CD to a local directory of your hard drive <C:TPCinstall> for Microsoft Windows or </TPCinstall> for LINUX. If you have an electronic image of the product, unzip or untar the image to the respective directories. This results in a tree structure similar to the one shown in Figure 6-18 on page 213.212 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 6-18 Remote installation, Tree structure installation disk 23. Insert the cross platform agent CD. It contains a directory for each supported agent platform. In each directory, there is a file called upgrade.zip. Copy this file for each platform you on which you want to install the product remotely in the <C:TPCinstall>dataupgrade (Windows) or </TPCinstall>/data/upgrade (LINUX or UNIX) directory of your installation directory. In our example, we perform a remote installation to Windows, AIX, and LINUX Systems. Our installation directory looks similar to Figure 6-19.Figure 6-19 Remote installation, installation directory with cross-platform agent files Chapter 6. Agent deployment 213
    • 4. If you are installing the Data Agent to a LINUX system, you must perform a last check before you can start the installation. Verify, that the /etc/ssh/sshd_config file parameter PasswordAuthentication is set to yes. To set the parameter, follow these steps: a. Go to the following directory: /etc/ssh. b. Use a text editor such as vi to open and edit the /etc/ssh/sshd_config file. Change the PasswordAuthentication parameter to yes. c. Stop the daemon by running the following command: /etc/init.d/sshd stop. d. Start the daemon by running the following command: /etc/init.d/sshd start.l6.5.2 Performing the remote installation The following steps show a remote installation done from a Windows system to Windows (non domain), AIX and LINUX computers. The installation dialog will not differ if the remote installation is performed from AIX or LINUX. In our example we installed the Data Agent and the Fabric Agent together. To invoke the remote installer, go to <C:TPCinstall> on Windows and double-click setup.exe. On LINUX or AIX, go to the /TPCinstall/ directory and run setup.sh. 5. In the first panel, select the preferred language for the installer (Figure 6-20) and Click OK. Figure 6-20 Remote installation, language selection 6. The International Program License Agreement is shown (see Figure 6-21). Read and accept the terms by selecting I accept the terms of the license agreement. Figure 6-21 Remote installation, license agreement Click Next.214 IBM TotalStorage Productivity Center: The Next Generation
    • 7. In the panel shown in Figure 6-22, choose Custom Installation. Click Next to continue.Figure 6-22 Remote installation, type of installation / installation location8. In the panel in Figure 6-23, select which components you want to install. Select Remote Data Agent and Remote Fabric Agent. Deselect other options. Click Next.Figure 6-23 Remote installation, component selection9. In the next panel (Figure 6-24 on page 216), enter the Host authentication password. This is the password used by the Fabric Agent to communicate with the Device Server. You specify this password when you install the Device Server. All other information is already set correctly because we are installing from the machine which is running the Data Server and the Device Server. Click Next to continue. Chapter 6. Agent deployment 215
    • Figure 6-24 Remote installation, server and agent settings 10.Next, a panel similar to the one shown in Figure 6-25 is displayed where you enter the remote computers on which you want to install the Data Agents and the Common Agents. You must enter remote LINUX and UNIX computers manually by host name or IP address. Microsoft Windows computers can be added either manually or from Microsoft Directory if you have an Active Directory® environment. Figure 6-25 Remote installation, select remote computers 11.We enter our target computers manually, so click Manually Enter Agents. You will see the panel in Figure 6-26 on page 217.216 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 6-26 Remote installation, manually add agents12.In Figure 6-26, enter the fully qualified host name or the IP address of the computer on which you want the Data Agent and Common Agent to be installed. Note: You can add multiple computers in this panel if they share the same user ID and password. If computers do not share the same user ID and password, you must add them individually. In our example we added five remote systems, each individually, because our target machines have different user IDs and passwords as shown in Figure 6-27 on page 218. Chapter 6. Agent deployment 217
    • Figure 6-27 Remote Installation, list of remote computers to install the Data Agent Note: Right-click a column name to filter or sort the listed computers. If you filter the names in the computer list, the computers you selected for an agent installation that do not match the filter criteria will not appear in the list. Those agents will still be installed to the unlisted computers with names that do not match the filter. 13.When you are satisfied with your list of target computers click Next. 14.The panel shown in Figure 6-28 on page 219 is displayed. Here, you specify the settings for the Common Agent Service on your Windows target machines. This information is optional. You can enter a Common Agent service name, user ID and password, and a listener port that the installer will use to create a Windows service for the Common Agent. Otherwise, itcauser is created and a random listener port is used by default. We recommend that you keep those defaults. This panel corresponds to the panel shown in Figure 6-13 on page 208 for the local installation. Click Next.218 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 6-28 Remote installation, Windows Common Agent service settings15.The TotalStorage Productivity Center Installer runs a mini-probe on all the computers you selected, to verify all prerequisites. The status for each computer will change several times. Finally you will see the panel in Figure 6-29.Figure 6-29 Remote installation, ready to install In this panel, the TotalStorage Productivity Center Installer shows you the default installation directory for each target computer. Chapter 6. Agent deployment 219
    • Note: The default installation directory for the Data Agent remote installation differs from the default installation directory for the Data Agent for a local installation. The installation directory for the Data Agent remote installation defaults to: C:Program FilesTivoliep for Windows /usr/tivoli/ep for LINUX and UNIX. The defaults for a local installation are: C:Program FilesIBMTPC for Windows d /opt/IBM/TPC for LINUX and UNIX. In this panel you can also select two settings for the Data Agents: – Agent should perform a scan when first installed This option is enabled by default. We suggest you accept this default, so that your Data Server receives a solid information base about your computer right after installation. Deselect this option if you do not want to have the Data Agent perform an initial scan of your computer after installation. – Agent may run scripts sent by server This option is enabled by default. The advantage of enabling this option is that you can store scripts in the servers scripts directory, and do not have to keep a copy of the script on every agent computer. When a script must be run on a particular agent, the server accesses the script from its local scripts directory and sends it to the appropriate agent. If you deselect Agent may run scripts sent by server, you must make sure that the script is stored in every agents scripts directory. Note: If a script with the same name exists on both the server and the agent, the script stored on the agent will take precedence. This is useful if you want to run a special version of a script on one of your agents, while running a different version of the same script across all the other agents in your environment. Click Install to continue. The TotalStorage Productivity Center Installer starts to install the Data Agents and the Common Agent to the remote target computers. The installation status (see Figure 6-30 on page 221) is shown in the upper pane and you can monitor the installation log in the lower pane. When the installation is complete, you will see the window in Figure 6-31 on page 221.220 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 6-30 Remote installation, progressWhen completed, you will see the status Probed for all successfully installed Data Agents asshown in Figure 6-31.Figure 6-31 Remote installation, installation complete Note: You can review the Installation log for each computer by double-clicking the computer name or the IP address. Chapter 6. Agent deployment 221
    • 16.Click Done to continue. The remote installation of the Data Agent and the Common Agent is now finished. The remote computers are now ready for the remote installation of the Fabric Agents because they now run a Common Agent. Because we have selected to install both, the Data Agent and the Fabric Agent, the TotalStorage Productivity Center Installer opens the panel shown in Figure 6-32, where we can select on which of the remote computers we want to install the remote Fabric Agents. 17.Select the remote computers where the Fabric Agents shall be deployed. Click Next. Figure 6-32 Remote installation, select remote computers to deploy Fabric Agents 18.Review the list of the computers as shown in Figure 6-33 and click Next. Figure 6-33 Remote installation, list of selected computers for remote Fabric Agent installation You can see a panel as shown in Figure 6-34 on page 223, indicating the progress of the remote Fabric Agent deployment.222 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 6-34 Remote installation, Fabric Agent deployment progress panel 19.The TotalStorage Productivity Center Installer (see Figure 6-35) shows you a panel with a summary of the remote Fabric Agent deployment process. Click Next. Figure 6-35 Remote installation, Fabric Agent deployment complete 20.Verify that the installation has completed successfully using the methods summarized in 6.6, “Verifying the installation” on page 223.6.6 Verifying the installation After installing the server agents, you should check that the agents have registered successfully with the TotalStorage Productivity Center Server. They should do this without any further discovery. 1. To check the communication between the TotalStorage Productivity Center Server and the agents start the TotalStorage Productivity Center graphical user interface and log on. 2. In the Navigation Tree shown in Figure 6-36 on page 224 select Administrative Services → Agents and expand Data Agents and Fabric Agents. Look for an entry for each of the newly installed agents. Chapter 6. Agent deployment 223
    • 3. Right-click the entries and check if the TotalStorage Productivity Center Server can reach the agent and if the agent is up and running. In addition to that, the same context menu provides a look at the log files and the possibility to set up a trace for each agent. Figure 6-36 Verify agent installation 4. On the servers, the install process creates a directory structure, which should be similar to the one shown in Figure 6-37 on page 225 for a Windows server. For UNIX and LINUX System the tree is created under /opt/IBM/ by default and, otherwise, looks the same.224 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 6-37 Directory tree for Data and Fabric Agent installation Note: The Remote Installer however will create a different tree structure by default. It will install the Data Agent and the Common Agent to the following directory: C:ProgramTivoliep on Windows and /usr/tivoli/ep on UNIX and LINUX.5. Under Windows, look for a service called IBM Tivoli Common Agent (see Figure 6-38).Figure 6-38 Windows Services after agent installationThe Data Agent and Fabric Agent do not show up as a service. They run under the context ofthe Common Agent. Chapter 6. Agent deployment 225
    • 6. Under UNIX and LINUX, look for two processes: – One is the nonstop process, which launches the Common Agent process – The Common Agent itself Run the ps -ef command to shows results similar to Figure 6-39. Figure 6-39 UNIX and LINUX process status after agent installation6.6.1 Logfiles The agent installation process creates a number of logs, which can be checked to retrace the installation process and also to monitor the activity during normal operation. These logs provide detailed information and are especially useful in case of a failed installation to determine the reason for the failure and to troubleshoot the installation. They are spread over several locations: Note: The default <InstallLocation> will differ in local and remote administration. Data Agent logs The following installation logs are for the Data Agent when installed locally. <InstallLocation>logsubagentsTPCDatainstall for Windows <InstallLocation>/log/subagents/TPC/Data/install/ for UNIX AND LINUX The following installation logs are for the Data Agent when installed remotely for Windows. <InstallLocation>logs <InstallLocation>logsinstall <InstallLocation>subagentsTPCDatalog The following installation logs are for the Data Agent when installed remotely for UNIX and LINUX. <InstallLocation>/logs/ <InstallLocation>/subagents/TPC/Data/log/ <InstallLocation>/logs/226 IBM TotalStorage Productivity Center: The Next Generation
    • The following operational logs are for the Data Agent when installed locally for Windows. <InstallLocation>casubagentsTPCDatalog<hostname>The following operational logs are for the Data Agent when installed locally for UNIX andLINUX <InstallLocation>/ca/subagents/TPC/Data/log/<hostname>/The following operational logs are for the Data Agent when installed remotely for Windows. <InstallLocation>logs <InstallLocation>subagentsTPCDatalog<hostname>The following operational logs are for the Data Agent when installed remotely for UNIX andLINUX. <InstallLocation>/logs/ <InstallLocation>/subagents/TPC/Data/log/<hostname>Fabric Agent logsThe following installation logs are for the Fabric Agent when installed locally for Windows. <InstallLocation>logsubagentsTPCFabricinstallThe following installation logs are for the Fabric Agent when installed locally for UNIX andLINUX. <InstallLocation>/log/subagents/TPC/Fabric/install/The following installation logs are for the Fabric Agent when installed remotely for Windows. <InstallLocation>logsubagentsTPCFabricinstall <InstallLocation>subagentsTPCFabriclogThe following installation logs are for the Fabric Agent when installed remotely for UNIX andLINUX. <InstallLocation>/log/subagents/TPC/Fabric/install/ <InstallLocation>/subagents/TPC/Data/log/The following operational logs are for the Fabric Agent when installed locally for Windows <InstallLocation>casubagentsTPCFabriclog<hostname>The following operational logs are for the Fabric Agent when installed locally for UNIX andLINUX. <InstallLocation>/ca/subagents/TPC/Fabric/log/<hostname>/The following operational logs are for the Fabric Agent when installed remotely for Windows. <InstallLocation>logs <InstallLocation>subagentsTPCFabriclogThe following operational logs are for the Fabric Agent when installed remotely for UNIX andLINUX. <InstallLocation>/logs/ <InstallLocation>/subagents/TPC/Fabric/log/ Chapter 6. Agent deployment 227
    • Common Agent logs The following installation and operational logs are for the Common Agent when installed locally for Windows. <InstallLocation>calogs <InstallLocation>calogsinstall The following installation and operational logs are for the Common Agent when installed locally for UNIX and LINUX. <InstallLocation>/ca/logs/ <InstallLocation>/ca/logs/install/ The following installation and operational logs are for the Common Agent when installed remotely for Windows. <InstallLocation>logs <InstallLocation>logsinstall The following installation and operational logs are for the Common Agent when installed remotely for UNIX and LINUX. <InstallLocation>/logs/ <InstallLocation>/logs/install/6.7 Uninstalling Data and Fabric Agent For the Data Agent, TotalStorage Productivity Center V3.1 offers you two methods of uninstallation, remote and local. The remote uninstallation procedure is independent of the installation method (local or remote). The local uninstallation procedures differ slightly, depending on how the installation has been performed because TotalStorage Productivity Center V3.1 uses different installers for remote and local installation. The following sections guide you through the different uninstallation procedures.6.7.1 Remote uninstallation You can uninstall the Data Agent remotely from the TotalStorage Productivity Center Server GUI. This method is only supported for the Data Agent. The Fabric Agent cannot be uninstalled remotely. 1. To uninstall the Data Agent, start the TotalStorage Productivity Center GUI and log on. 2. In the Navigation Tree as shown in Figure 6-40 on page 229 select Administrative Services → Agents and expand Data Agents. 3. Right-click the entry and select Delete. This erases the entry for the Data Agent from the Navigation Tree and uninstalls the Data Agent on the remote computer.228 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 6-40 Remote Data Agent uninstall Although the context menu for the Fabric Agents also offer the option to delete the agent, this procedure erases the entries for the Fabric Agents from the navigation tree and the TotalStorage Productivity Center Repository as well, but does not uninstall the agent on the remote computer. Note: If you perform a remote uninstallation of the Data Agent on a remote computer where no Fabric Agent is installed, the remote uninstallation process also uninstalls the Common Agent. Otherwise, the remote uninstallation process keeps the Common Agent on the target computer.6.7.2 Local uninstallation If you have performed the installation of the Data Agent and the Fabric Agent locally, the local uninstallation of the Data Agent, the Fabric Agent and the Common Agent can be performed in a single step. In the following example, we show the uninstallation procedure for a Windows system. There are no differences on UNIX or LINUX systems in the dialog box. 1. To invoke the uninstall on a windows computer select the following: Start → Settings → Control Panel → Add/Remove Programs as shown in Figure 6-41 on page 230. Chapter 6. Agent deployment 229
    • Figure 6-41 Local agent uninstall, Add or Remove Programs 2. Select the entry TotalStorage Productivity Center and Click Change/Remove. On a UNIX or LINUX machine go to the directory /opt/IBM/TPC/_uninst/ and run the uninstall program. In the first panel shown in Figure 6-42, select the preferred language for the uninstaller. Figure 6-42 Local agent uninstall, language selection Click Ok to continue. You can see the TotalStorage Productivity Center Installer Welcome Panel shown in Figure 6-43 on page 231.230 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 6-43 Local agent uninstall, welcome panel Click Next.3. In the panel shown in Figure 6-44 you select the components you want to uninstall. The TotalStorage Productivity Center Installer offers all components which it has detected on your system. In our example the Data Agent and the Fabric Agent are installed and we want to uninstall them both in one step. Although there is a check box where you select to force the uninstallation of the Common Agent, it is not necessary to check this box, because the Common Agent will be deinstalled automatically when the last subagent is removed.Figure 6-44 Local agent uninstall, select component to uninstall Click Next to continue. You can see a summary of the components which the TotalStorage Productivity Center Installer is about to uninstall, as shown in Figure 6-45 on page 232. Chapter 6. Agent deployment 231
    • Figure 6-45 Local agent uninstall, summary panel Click Next to continue. 4. The system uninstalls the selected components. You can see the panel Figure 6-46 when the uninstallation is finished. You must reboot a Microsoft Windows machine. Click Finish. Figure 6-46 Local agent uninstall, uninstall complete If you have installed the Fabric Agent and the Data Agent remotely, you cannot uninstall both agents and the Common Agent in one step. We recommend that you uninstall the Fabric Agent first, then uninstall the Data Agent, which uninstalls the Common Agent also. 1. To invoke the uninstall on a Microsoft Windows computer, select Start → Settings → Control Panel → Add/Remove Programs. You now see a separate entry for the Data Agent. The uninstallation for the Fabric Agent is invoked by selecting TotalStorage Productivity Center → Change/Remove, as shown in Figure 6-47 on page 233.232 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 6-47 Local agent uninstall, Add or Remove Programs for remotely deployed agents2. The uninstallation dialog box is the same as described previously, with the exception that the installer only offer to uninstall the Fabric Agent. You are not able to select the Data Agent.3. When the uninstallation of the Fabric Agent is complete, you must reboot your system and again select Start → Settings → Control Panel → Add/Remove Programs.4. Now the TotalStorage Productivity Center entry is gone and you must select TotalStorage Productivity Center for Data - Agent as shown in Figure 6-48 on page 234. Click Change/Remove. Chapter 6. Agent deployment 233
    • Figure 6-48 Local agent uninstall, Add or Remove Programs for remotely deployed agents Now a different installer is presented, which is the one you have used to perform the remote installation of the Data Agent as shown in Figure 6-49. 5. Although there is a radio button, you are not be able to make any selections. Click Next. Figure 6-49 Local agent uninstall, uninstall of remotely deployed Data Agent A panel is shown (Figure 6-50 on page 235), where you are able to monitor the log of the deinstallation process in the lower pane.234 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 6-50 Local agent uninstall, uninstall of remotely deployed Data Agent When the deinstallation completes, you can see a panel announcing the successful installation of the Data Agent (see Figure 6-51). Figure 6-51 Local agent uninstall, uninstall of remotely deployed Data Agent completed 6. Click OK and restart your system.6.8 Upgrading the Data Agent The TotalStorage Productivity Center GUI allows you to upgrade your Data Agent infrastructure from a central point of management. This central upgrade is only supported for the Data Agent and the Common Agent. The Fabric Agent cannot be upgraded this way. 1. Before you can upgrade your Data Agents from your central TotalStorage Productivity Center GUI, you have to copy the upgrade.zip files of the new Data Agent Version for the operating systems, you want to perform an upgrade for to the C:Program Chapter 6. Agent deployment 235
    • FileIBMTPCdataupgrade (for Windows) and /opt/IBM/TPC/data/upgrade (for LINUX and UNIX) path of your TotalStorage Productivity Center Server installation. Note that if you do not copy the upgrade.zip file, you will break all of your agents. The tree structure should look similar to the figure in Figure 6-52. Figure 6-52 Data Agent upgrade, copy the upgrade.zip file to the server upgrade directories 2. After having copied the files you need to the respective directories, launch the TotalStorage Productivity Center GUI and log on. In the navigation tree, select Administrative Services → Configuration and right-click Data Agent Upgrade as shown in Figure 6-53 on page 237.236 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 6-53 Data Agent upgrade, create an upgrade job3. You will then see a panel similar to Figure 6-54 where you can select the computers for which you want to perform a Data Agent upgrade.Figure 6-54 Data Agent upgrade, create an upgrade job, select computers to upgrade Chapter 6. Agent deployment 237
    • You can either select Computer Groups (if you have defined them in the TotalStorage Productivity Center) or select single computers or all computers which have Data Agents installed. Verify that the Enable box in the top right corner of the panel is checked. 4. In the When to Run tab, specify if the upgrade should run immediately or should be scheduled at a later time. 5. The Options tab gives you some options for the upgrade of the Data Agents. You can specify if the Data Agent should be overwritten if the server already has the upgraded level installed, and you can select the correct language option. 6. In the Alert tab, you can chose what alerts the TotalStorage Productivity Center Server will generate for the upgrade job. 7. After having reviewed all tabs select File → Save. You must specify a name for the job. The upgrade job will be saved and run either immediately, or at the time you chose in the When to Run tab. 8. To check if the upgrades have completed successfully, right-click the Data Agent upgrade and select Refresh. You can see an entry for the upgrade job you submitted. Click the little plus sign (+) to the left of your job name and an entry with the time stamp of the submission of your job opens. Click this entry and you can see the log for the job on the right pane, as shown in Figure 6-55. Figure 6-55 Data Agent upgrade, job log of the upgrade job 9. You can click the symbol next to the job log entry and examine the log for your upgrade job.238 IBM TotalStorage Productivity Center: The Next Generation
    • 7 Chapter 7. CIMOM installation and customization This chapter provides a step-by-step guide to configure Service Location Protocol (SLP) and the Common Information Model Object Manager (CIMOM) for supported storage subsystems, tapes, and switches and that are required to use TotalStorage Productivity Center.© Copyright IBM Corp. 2006. All rights reserved. 239
    • 7.1 Introduction After you have completed the installation of TotalStorage Productivity Center, you must install and configure the Common Information Model Object Manager (CIMOM) and Service Location Protocol (SLP) agents. Note: For the remainder of this chapter, we refer to the TotalStorage Productivity Center, TotalStorage Productivity Center for Fabric and TotalStorage Productivity Center for Data simply as TotalStorage Productivity Center. The TotalStorage Productivity Center uses SLP as the method for CIM clients to locate managed objects. The CIM clients may have built in or external CIM agents. When a CIM agent implementation is available for a supported device, the device may be accessed and configured by management applications using industry-standard XML-over-HTTP transactions. In this chapter we describe the steps for: Planning considerations for CIMOM Installing and configuring CIM agent for Enterprise Storage Server and DS6000/DS8000 Installing and configuring CIM agent for DS 4000 Family Configuring CIM agent for SAN Volume Controller Planning considerations for Service Location Protocol (SLP) SLP configuration recommendation Setting up Service Location Protocol Directory Agent (SLP DA) General performance guidelines7.2 Planning considerations for CIMOM The CIM agent includes a CIM Object Manager (CIMOM) which adapts various devices using a plug-in called a provider. The CIM agent can work as a proxy or can be imbedded in storage devices. When the CIM agent is installed as a proxy, the IBM CIM agent can be installed on the same server that supports the device specific management interface. Figure 7-1 shows an overview of CIM agent. Figure 7-1 CIM Agent Overview You can plan to install CIM agent code on the same server which also has the specific management or you can install it on a separate server.240 IBM TotalStorage Productivity Center: The Next Generation
    • Attention: At this time, only a few devices come with an integrated CIM Agent, most devices need a external CIMOM for CIM-enabled management applications (CIM Clients) to be able to communicate with a device. For the ease of the installation, IBM provides an Integrated Configuration Agent Technology (ICAT) which is a bundle that includes the CIMOM, the device provider, and an SLP SA.7.2.1 CIMOM configuration recommendations The following recommendations are based on our experience in the ITSO lab environment: The CIMOM agent code that you plan to use must be supported by the installed version of TotalStorage Productivity Center. Refer to this link for latest updates: http://www-1.ibm.com/servers/storage/support/software/tpc/ You must have the CIMOM supported firmware level on the storage devices. It you have an incorrect version of the firmware, you might not be able to discover and manage the storage devices which have the incorrect level of software or firmware installed. The data traffic between CIMOM agent and device can be very high, especially during performance data collection. As a result, it is recommended that you have a dedicated server for the CIMOM agent. Although, you can configure the same CIMOM agent for multiple devices of same type. Locate the server containing the CIMOM within the same data center where the managed storage devices are located. This is in consideration of firewall port requirements. Typically, it is a best practice to minimize firewall port openings between the data center and the external network. If you consolidate the CIMOM servers within the data center, then you might be able to minimize the need to open the firewall ports only for TotalStorage Productivity Center communication with the CIMOM. It is strongly recommended that you have separate and dedicated servers for CIMOM agents and TotalStorage Productivity Center. The reason for this is resource contention, TCP/IP port requirements, and system services coexistence. It is highly recommended that you have separate systems for each CIMOM that you need to install. They do not need to be dedicated servers. It depends on the workload you expect the servers to support. This recommendation is based on the following: – CIMOMs by default should use either port 5988 (HTTP) or port 5989 (HTTPS) for communication. If you collocate two CIMOMs, you will have a port conflict. – Most CIMOMs have different interoperability namespaces. If you collocate two CIMOMs, you could have an interoperability namespace mismatch. The user ID that will be used by the CIMOM to communicate with the storage device must have superuser, administrator, or equivalent read and write authorization on the storage device. This level of authorization is required to manage, manipulate, and configure the storage device, as well as to gather performance data. Read-only authorization is insufficient for all but basic inventory collection tasks.7.3 SNIA certification Support is for third-party disks systems and switches that are Storage Management Interface Specification (SMI-S) 1.0.2 or SMIS 1.1 compatible. This support includes storage provisioning, as well as asset and capacity reporting. TotalStorage Productivity Center V3.1 Chapter 7. CIMOM installation and customization 241
    • implements many of its disk, tape, and fabric management functions through exploitation of the SMIS 1.0.2 and 1.1 levels of the standard. SMIS 1.1 supports all of the functions of SMIS 1.0.2 plus additional functionality (such as performance management). If you are interested in finding out what is new in SMI-S 1.1 compared to 1.0.2 or just generally, you can visit the following Web site (subscription needed): http://www.snia.org/smi/tech_activities/smi_spec_pr/spec You can find a list of all device vendors that are participating the SMI-S initiative and that have successfully passed the SNIA Conformance Testing Program by visiting the following Web site: http://www.snia.org/ctp/conformingproviders If you select one of the vendors you are brought to a vendor-specific page where certified devices are listed together with minimum software requirements for the SMI-S Agent. We strongly suggest you visit this Web site to find all the latest information about conforming SNIA CTP provider devices. Any new device that is SMI-S 1.0.2 or 1.1 can be monitored and managed by TotalStorage Productivity Center because of the standard approach adopted on both sides.7.4 Installing CIM Agent for ESS 800/DS6000/DS8000 Before starting TotalStorage Productivity Center Common Information Model Object Manager (CIMOM) discovery, you must first install and configure the related CIMOM. In order to manage IBM ESS 800, DS6000 and DS8000 disk subsystems using SMI-Specifications V1.1 you must be certain that your storage subsystem is listed on the following Web sites: SNIA - conforming providers IBM http://www.snia.org/ctp/conformingproviders/ibm IBM Support for IBM Common Information Model (CIM) Agent for DS Open (API) The IBM Web site for the IBM CIM Agent for DS Open API Code is located at: http://www-1.ibm.com/support/search.wss?rs=1118&tc=STC4NKB&dc=D400&dtm The software components have requirements that have to be checked in advance. Verify the minimum ESS LIC level and ESSCLI version documented on these Web pages: IBM ESS CIM Agent Compatibility Matrix http://www-1.ibm.com/support/docview.wss?rs=586&context=STHUUM&dc=DB520&dc=DA460&dc= DB540&uid=ssg1S1002397&loc=en_US&cs=utf-8&lang=en IBM CIM Agent for DS Open API Compatibility Matrix http://www-1.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=DB500&uid= ssg1S1002714&loc=en_US&cs=utf-8&lang=en Figure 7-2 on page 243 shows the interaction between the DS Open API and the storage subsystems it manages.242 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-2 DS Open API overview7.4.1 CIM Agent and LIC level relationship for DS8000 You must identify the relationship between CIM Agent Level and LIC Level or Bundle Version on a DS8000. The Web site mentions Bundle Versions. In a DS8000, you can determine the active LIC level by following these steps. 1. Log into the HMC console. 2. Navigate through this path: – Management Environment – <HMC Hostname> – Licensed Internal Code Maintenance – Licensed Internal Code Updates – Change Internal Code (In new window) – Select Storage Facility – From the menu, choose Selected. – Display Installed Code Levels. 3. In the new window CDA Install History you should be able to locate the latest entry. There you will find a relation from LIC-Level to Bundle Version. This information makes it possible to find the relationship between the CIM Agent, LIC level, and Bundle Version. Be sure that the prerequisites are met before proceeding with the software installation. Chapter 7. CIMOM installation and customization 243
    • 7.4.2 CIM Agent and LIC level relationship for DS6000 The following information will help you to determine the relationship between CIM Agent Level and LIC Level or Bundle Version on a DS6000. 1. Logon to the DS6000 StorageManager Web Interface. 2. Navigate through this sequence: – Real-time Manager – Manage Hardware – Storage Units – Your DS6000 check box – Apply Firmware Update – Go 3. This results in the panel hold the first part of the information that you need. The second part is found on the following Web site: http://www-1.ibm.com/support/dlsearch.wss?rs=1112&lang=en&loc=en_US&r=10&cs= utf-8&rankfile=0&cc=&spc=&stc=&apar=include&q1=ssg1*&q2=&dc=D420&atrn=SWPlatform&atrv= all&atrn1=SWVersion&atrv1=all&tc=HW2A2&Go.x=17&Go.y=9 4. Here you can cross-reference the internal LIC level to a Release Level. 5. Lastly, on the IBM CIM Agent for DS Open API Compatibility Matrix site you can find the CIM Agent Version requiered for your DS6000.7.4.3 ESS CLI Installation The ESS CLI is required if you monitor and manage ESS disk subsystems. If you will not monitor any ESS Model Fxx,7xx or 800 devices, then you do not need to install the CLI. You can go directly to 7.4.4, “DS CIM Agent install” on page 249. The ESS CLI installation wizard detects if you have an earlier level of the ESS CLI software installed on your system and uninstalls the earlier level. After you uninstall the previous version, you must restart the ESS CLI installation program to install the current level of the ESS CLI. You must have a minimum ESS CLI level of 2.4.0.236. You should also uninstall the ESS CIM Agent and replace it with CIM Agent for DS Open API To install the ESS CLI insert the CD for the ESS CLI in the CD-ROM drive and run the setup. Alternatively, use the Windows Explorer to select the directory where you have stored the ESS CLI Code. 1. The first panel is the InstallShield Wizard Welcome as shown in Figure 7-3 on page 245. Click Next to continue.244 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-3 ESS CLI InstallShield Wizard I1. On the license agreement panel in Figure 7-4, select I accept the terms of the license agreement and click Next to continue.Figure 7-4 ESS CLI License agreement2. Verify the target operating system as shown in Figure 7-5 on page 246 and click Next to continue. Chapter 7. CIMOM installation and customization 245
    • Figure 7-5 ESS CLI choose target system panel 3. The panel in Figure 7-6 specifies the CLI installation directory. Accept the default or enter the appropriate directory and click Next to continue. Figure 7-6 ESS CLI Setup Status panel 4. The next panel is a summary of the installation requirements as shown in Figure 7-7 on page 247. Click Next to continue.246 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-7 ESS CLI selected options summary5. You can see a panel showing the progress of the installation. When the installation is complete, you can see a panel similar to Figure 7-8. Click Next to continue.Figure 7-8 ESS CLI installation complete panel6. The next panel contains the ESS CLI readme file (see Figure 7-9 on page 248). Read the information and click Next. Chapter 7. CIMOM installation and customization 247
    • Figure 7-9 ESS CLI Readme 7. The next panel (see Figure 7-10) gives you the option to restart your system before proceeding with the ESS CIM Agent installation. You must do this because the ESS CLI is dependent on environmental variable settings which will not be in effect for the ESS CIM Agent. The reason for this is the CIM Agent runs as a service, unless you reboot your system. Figure 7-10 ESS CLI Restart panel248 IBM TotalStorage Productivity Center: The Next Generation
    • 8. After your server has restarted, you should verify that the ESS CLI is installed: a. Click Start → Settings → Control Panel. b. Double-click Add/Remove Programs. c. Verify that there is an IBM ESS CLI entry. 9. Verify that the ESS CLI is operational and can connect to the ESS. From a command prompt window, issue the following command: esscli -u userid -p password -s 9.1.11.111 list server Where: – 9.1.11.111 represents the IP address of the Enterprise Storage Server – userid represents the Enterprise Storage Server Specialist user name – password represents the Enterprise Storage Server Specialist password for the user name Figure 7-11 shows the response from the esscli command. Figure 7-11 ESS CLI verification7.4.4 DS CIM Agent install Before you install the DS CIM Agent, you must install the IBM TotalStorage Enterprise Storage System Command Line Interface (ESS CLI) if you plan to manage 2105-F20s or 2105-800s with this CIM agent. The DS CIM Agent installation program checks your system for the existence of the ESS CLI and provides the warning shown in Figure 7-15 on page 253 if no valid ESS CLI is found. As part of the CIMOM installation, there is an installation of the Service Location Protocol (SLP). If there are any previous versions of SLP on the system, you should deinstall them or stop the service prior to this installation. The latest DS Open API code can be downloaded from the following Web site: http://www-03.ibm.com/servers/storage/support/software/cimdsoapi/downloading.html At the time of writing, we used the code which is contained in the package ibm-ds-smis-agent-5.1.0.45.zip. To install the DS Open API in your Windows system, perform the following steps: 1. Log on to your system as the local administrator. 2. Insert the CIM Agent for DS Open Api Code CD into the CD-ROM drive. Alternatively, use the Windows Explorer to select the directory where you have stored the DS Open API Code. Chapter 7. CIMOM installation and customization 249
    • 3. Start the setup.exe found in ......ibm-ds-smis-agent-5.1.0.45W2K. The Install Wizard launchpad starts automatically, if you use a CD and have autorun mode set on your system,. Look for a launchpad similar to Figure 7-12. Open and review the readme file from the launchpad menu. Subsequently, you can Click Installation Wizard. The Installation Wizard starts the setup.exe program and shows the Welcome panel in Figure 7-13 on page 251. The DS CIM Agent program starts within 15 - 30 seconds, if you have autorun mode set on your system. If the installer window does not open, perform the following steps: a. Use a command prompt or Windows Explorer to change to the Windows directory on the CD. b. If you are using a Command Prompt window, run launchpad.bat. c. If you are using Windows Explorer, double-click the launchpad.bat file. Figure 7-12 DSCIM Agent launchpad 4. The Welcome window opens suggesting what documentation you should review prior to installation. Click Next to continue (see Figure 7-13 on page 251).250 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-13 DS CIM Agent welcome window5. The License Agreement window opens. Read the license agreement information. Select I accept the terms of the license agreement, then click Next to accept the license agreement (see Figure 7-14 on page 252). Chapter 7. CIMOM installation and customization 251
    • Figure 7-14 DS CIM Agent license agreement 6. The window shown in Figure 7-15 on page 253 only opens if no valid ESS CLI installed. If you do not plan to manage an ESS from this CIM agent, then click Next. Important: If you plan to manage an ESS from this CIM agent, then click Cancel. Install the ESS CLI following the instructions in 7.4.3, “ESS CLI Installation” on page 244.252 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-15 DS CIM Agent ESS CLI warning7. The Destination Directory window opens. Accept the default directory and click Next to continue (see Figure 7-16 on page 254). Chapter 7. CIMOM installation and customization 253
    • Figure 7-16 DS CIM Agent destination directory panel 8. The Updating CIMOM Port window opens (see Figure 7-17 on page 255). Click Next to accept the default port if it is available and free in your environment. For our ITSO setup, we used default port 5989. Note: As mentioned throughout this book, it is not recommended to use anything other than the default ports. Use the following commands to check which ports are in use: netstat -a netstat -an | find/f “598”254 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-17 DS CIM Agent port window9. The Installation Confirmation window opens (see Figure 7-18 on page 256). Click Install to confirm the installation location and file size. Chapter 7. CIMOM installation and customization 255
    • Figure 7-18 DS CIM Agent installation confirmation The Installation Progress window opens (see Figure 7-19 on page 257), indicating how much of the installation has completed.256 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-19 DS CIM Agent installation progress10.When the Installation Progress window closes, the Finish window opens (see Figure 7-20 on page 258). Select View post installation tasks to view the post-installation tasks Readme when the wizard closes. We recommend that you review the post-installation tasks. Click Finish to exit the installation wizard (Figure 7-20 on page 258). Note: Before proceeding, you might want to review the log file for any error messages. The log file is located in xxxlogsinstall.log, where xxx is the destination directory where the DS CIM Agent for Windows is installed. Chapter 7. CIMOM installation and customization 257
    • Figure 7-20 DS CIM Agent install successful 11.If you checked the view post installation tasks box, then the window shown in Figure 7-21 opens. Close the window when you have finished reviewing the post installation tasks. Figure 7-21 DS CIM Agent post install readme 12.The launch pad window (Figure 7-12 on page 250) opens. Click Exit.258 IBM TotalStorage Productivity Center: The Next Generation
    • 7.4.5 Post-installation tasks Figure 7-22 contains a short summary of the post-installation steps. In our lab environment, we did not perform all of them. Note that the term ESS CIM Agent and DS Open CIM Agent are used interchangeably. Summary: 1. Verifying the DS Open CIM Agent Installation a. Verify the installation of the Service Location Protocol (SLP) b. Verify the installation of the ESS CIM Agent 2. Configuring the DS Open CIM Agent a. Configure the authorized CIMOM user b. Reset the password of the provided default CIMOM username (optional, recommended) c. Configure the ESS devices 3. Configuring the DS Open CIM Agent to run in unsecure mode (optional) 4. Verifying connection to the ESS Figure 7-22 Summary of the post installation tasks Verify the SLP installation To verify the SLP installation, follow these steps: 1. Verify that the Service Location Protocol is started. Select Start → Settings → Control Panel. Double-click Administrative Tools. Double-click Services. 2. Find SLP in the Services window list. For this component, the Status column should be marked Started as shown in Figure 7-23. Figure 7-23 Verify Service Location Protocol started Chapter 7. CIMOM installation and customization 259
    • 3. If SLP is not started, right-click the SLP and select Start from the pop-up menu. Wait for the Status column to be changed to Started and make sure that the Startup-Type is Automatic. Verify the DS CIM Agent installation To verify the DSCIM Agent installation, follow these steps: 1. Verify that the CIMOM service is started. If you closed the Services window, select Start → Settings → Control Panel. Double-click Administrative Tools. Double-click Services. 2. Find the CIM Object Manager - DS Open API in the Services window list. For this component, the Status column should be marked Started and the Startup Type column should be marked Automatic, as shown in Figure 7-24. Figure 7-24 DS CIM Object Manager started confirmation 3. If the CIM Object Manager is not started, right-click the CIM Object Manager - DS Open API and select Start from the pop-up menu. Wait for the Status column to change to Started. If you are able to perform all of the verification tasks successfully, the DS CIM Agent has been installed successfully on your Windows system. Next, perform the configuration tasks. Tip: All commands used for configuration and verification of the CIM Agent are described either in the ReadMe files or in the InstallGude.pdf which are part of the package. It is not advisable to use executables found in the working directory of the CIM Agent.7.4.6 Configuring the DS CIM Agent for Windows This task configures the DS CIM Agent after it has been successfully installed. DS Open CIMOM and ESS subsystem considerations Here are some issues to consider when using DS Open CIMOM and ESS subsystems: DS CIM agent relies on ESS CLI connectivity from DS CIMOM server to ESS devices. Make sure that the ESS devices you are registering are reachable and available at this point. It is recommended that you verify their availability by launching the ESS specialist browser from the ESS CIMOM server. You should log on to both ESS clusters for each ESS and be certain e you are authenticated with correct ESS passwords and IP addresses.260 IBM TotalStorage Productivity Center: The Next Generation
    • If the ESS is on a different subnet than the DS CIMOM server and behind a firewall, then you must authenticate through the firewall first before registering the ESS with the CIMOM. You must set up the firewall between the ESS subsystem and the CIMOM to allow bidirectional traffic between them. Rules might need to be put in place to open specific ports. You must authenticate through the firewall in both directions, that is from the ESS to CIMOM server and also from the CIMOM server to ESS. You must verify the connection between the ESS devices and the CIMOM server using rsTestConnection command of ESS CLI code. When you are satisfied that you are able to authenticate and receive the ESS CLI heartbeat with all registered ESS subsystems, you may proceed with entering ESS IP addresses. If the CIMOM agent fails to authenticate with ESSs, then it will not start-up properly and may be very slow, since it retries the authentication.Figure 7-25 shows an example of the rsTestConnection.exe command to check theconnection to your ESS subsystems. C:Program FilesIBMESScli>rsTestConnection.exe /v /s 9.12.6.29 rsWebTest: Using 9.12.6.29 as server name rsWebTest: HeartBeat to the server was successful. rsWebTest: command successfulFigure 7-25 Prerequisite is to check the connection to the ESSPerform the following steps to configure the DS CIM Agent.1. Configure the ESS CIM Agent with the information for each Enterprise Storage Server the ESS CIM Agent is to access. Select Start → Programs → CIM agent for the IBM TotalStorage DS Open API → Enable DS Communications, as shown in Figure 7-26. The setdevice.bat utility starts.Figure 7-26 Configuring the ESS CIM AgentRegistering DS6000 and DS8000 subsystemsAfter you have started the interface to enable the DS Communications successfully, theCMD-Line Interface to the DS Communications opens (Figure 7-27 on page 262). Chapter 7. CIMOM installation and customization 261
    • Figure 7-27 CMD Line Interface setdevice.bat 2. Type help to see the available commands as shown in Figure 7-28. Note that the addess, lsess, rmess commands are for the ESS-family subsystems. The and others such as addessserver, lsessserver, rmessserver commands are for the DS6000, DS8000 and the copyservice-server in the ESS-family subsystems. Figure 7-28 Available commands in setdevice.bat 3. Enter the following commands for each DS6000, DS8000, or ESS copyservices server that is to be configured. Both clusters must be added to the CIM Agent. addessserver <ip> <user> <password> – <ip> represents the IP address of the storage subsystem – <user> represents the DS Storage Server HMC or SMC user name – <password> represents the DS Storage Server password for the user name Attention: If the username or password entered is incorrect or the DS CIM agent does not connect to the storage subsystem, this will cause a error and the DS CIM Agent will not start and stop correctly. Use the following command to remove the entry that is causing the problem and reboot the server. rmessserver <ip> Whenever you add or remove a storage subsystem from CIMOM registration, you must restart the CIMOM to pick up the updated device list. Figure 7-29 on page 263 shows a sample output of the systems in our lab environment.262 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-29 List some ESS subsystems versus some DS8K subsystems Note: The CIMOM collects and caches the information from the defined storage subsystems at startup time. The first time it is started might take longer than subsequent starts.Registering ESS DevicesEnter the following command for each ESS subsystem that is to be configured. Both clustersmust be added to the CIM Agent.addess <ip> <user> <password> <ip> represents the IP address of the Enterprise Storage Server <user> represents the Enterprise Storage Server Specialist user name <password> represents the Enterprise Storage Server Specialist password for the user nameAn example of the addess command is:addess <ip> <user> <password>Type this command for each ESS (as shown in Figure 7-30). Where <ip> represents the IPaddress of the cluster of Enterprise Storage Server.Figure 7-30 The addess command example Chapter 7. CIMOM installation and customization 263
    • 7.4.7 Restart the CIMOM Perform the following steps to use the Windows Start menu facility to stop and restart the CIMOM. This is required so that CIMOM can register new devices or unregister deleted devices. 1. Stop the CIMOM by selecting Start → Programs → CIM Agent for the IBM TotalStorage DS Open API → Stop CIMOM service. A Command Prompt window opens to track the stoppage of the CIMOM (as shown in Figure 7-31). If the CIMOM has stopped successfully, the following message is displayed: Figure 7-31 Stop DS Open CIM Agent 2. Restart the CIMOM by selecting Start → Programs → CIM Agent for the IBM TotalStorage DS Open API → Start CIMOM service. A Command Prompt window opens to track the progress of the starting of the CIMOM. If the CIMOM has started successfully, the message shown in Figure 7-32 displayed: Figure 7-32 Restart DS Open CIM Agent Note: The restarting of the CIMOM might take a while, because it is connecting to the defined storage subsystems and is caching that information for future use. As an alternative, you might use the Services Applet in the Windows Control Panel. 3. You should now have a look at the CIMOM.LOG File. Figure 7-33 on page 265 is a sample output from our lab. Note the bolded text where the most important events are highlighted.264 IBM TotalStorage Productivity Center: The Next Generation
    • CMMOM0200I SSG/SSD CIM Object Manager CMMOM0203I **** CIMOM Server Started **** CMMOM0204I CIMOM Version: 5.1.0.45 CMMOM0205I CIMOM Build Date: 01/05/06 Build Time: 07:26:32 PM CMMOM0206I OS Name: Windows 2000 Version: 5.0 CIMServer[initialize]: Namespace rootibm initialized CMMOM0400I Authorization module = com.ibm.provider.security.EnhancedAuthModule CMMOM0410I Authorization is active CMMOM0901I IndicationProcessor started CMMOM0902I Indication subscription created for http://9.1.38.36:1272/1303 CMMOM0902I Indication subscription created for http://9.1.38.36:1272/1303 CMMOM0902I Indication subscription created for http://9.1.38.36:1272/1303 CMMOM0902I Indication subscription created for http://9.1.38.36:1272/1303 CMMOM0905I 4 indication subscriptions re-started EssProvider[initialize]: ESS Provider is starting... EssProvider[initialize]: CLI already configured for ESS 2105.22513. Adding aditional information 9.12.6.30 EssProvider[initialize]: End initialize ESS Provider NCache EssProvider[initialize]: com.ibm.provider.common.ProviderContext@26a15b3f : finished for 2107.75BALB1 PrimeCache[run]: Alternative ip = 9.12.6.30 PrimeCache[run]: Starting Thread Creating cache for ip 9.12.6.29 EssProvider[initialize]: ESS 2105.22513 configured at 9.12.6.29 EssProvider[initialize]: ESS 2107.75BALB1 configured at Internal Service 9.12.6.17 EssProvider[initialize]: ESCON Connectivity interval set to: 60 minutes CMMOM0403I Platform is Windows CMMOM0404I Security server starting on port 5989 CMMOM0409I Server waiting for connections... CMMOM0500I Registered service service:wbem:https://9.1.38.35:5989 with SLP SA PrimeCache[run]: Ending Thread Creating cache for ip 9.12.6.29 Figure 7-33 Sample CIMOM Output after restarting the service7.4.8 CIMOM user authentication Use the setuser interactive tool to configure the CIMOM for the user who will have the authority to use the CIMOM. The user is the TotalStorage Productivity superuser. Upon installation of the CIM Agent for ESS, the provided default user name is superuser with a default password of passw0rd. The first time you use the setuser tool, you must use this user name and password combination, as shown in Figure 7-34 on page 266. After you have defined other user names, you can start the setuser command by specifying other defined CIMOM user names. Additional user IDs should be less than or equal to eight characters. You should consider deleting the default user ID of superuser after you have defined additional user IDs to the CIMOM. Chapter 7. CIMOM installation and customization 265
    • C:Program FilesIBMcimagent> setuser -u superuser -p passw0rd Application setuser started in interactive mode To terminate the application enter: exit To get a help message enter: help >>> help Available commands: ? exit rmuser adduser h[elp] setentry chuser lsuser setoutput >>> Figure 7-34 Available commands for setuser.bat The users which you configure to have authority to use the CIMOM are defined uniquely to the CIMOM software and have no required relationship to operating system user names, the ESS Specialist user names, or the ESS Copy Services user names. Note: We recommend that you change the superuser password to something other than the default or delete the superuser user ID after defining a new CIMOM user ID and password. Following are the steps to define users to the CIMOM: 1. Open a Command Prompt window and change directory to the CIM Agent directory, for example: C:Program FilesIBMcimagent 2. Type the command setuser -u superuser -p passw0rd at the command prompt to start the setuser interactive session to identify users to the CIMOM. 3. Type the command adduser cimuser cimpass in the setuser interactive session to define new users. – cimuser represents the new user name to access the CIMOM. – cimpass represents the password for the new user name to access the CIMOM. 4. Close the setuser interactive session by typing exit. 5. The users which you configure to have authority to use the CIMOM are now functional.7.5 Verifying connection to the storage subsystems During this task, the DS Open API CIM Agent software connectivity to the Enterprise Storage Server (ESS) is verified. The connection to the ESS is through the ESS CLI software. If the network connectivity fails, or if the user name and password that you set in the configuration task is incorrect, the CIM Agent cannot connect successfully to the ESS. The installation, verification, and configuration of the CIM Agent must be completed before you verify the connection to the storage subsystem defined to it. Verify that you have network connectivity to the ESS, DS8000 or DS6000 from the system where the CIM Agent is installed. Issue a ping command to the storage subsystem and check that you can see reply statistics from the storage subsystem IP address.266 IBM TotalStorage Productivity Center: The Next Generation
    • Verify that the CIMOM is active by selecting Start → Settings → Control Panel → Administrative Tools → Services. Launch the Services panel and select CIM Object Manager service. Verify the Status is shown as Started, as shown in Figure 7-35.Figure 7-35 Verify ESS CIMOM has started Verify that the SLP is active by selecting Start → Settings → Control Panel. Double-click Administrative Tools. Double-Click Services. You should see a panel similar to Figure 7-23 on page 259. Ensure that Status is Started. Verify that SLP has dependency on CIMOM. This was configured automatically when you installed the CIM agent software. Verify this by selecting Start → Settings → Control Panel. Double-click Administrative Tools. Double-Click Services. Select Properties on Service Location Protocol, as shown in Figure 7-36.Figure 7-36 SLP properties panel Chapter 7. CIMOM installation and customization 267
    • Click Properties and select the Dependencies tab, as shown in Figure 7-37. You must ensure that CIM Object Manager has a dependency on Service Location Protocol. This should be the default. Figure 7-37 SLP dependency on CIMOM Verify CIMOM registration with SLP by selecting Start → Programs → CIM Agent for the IBM TotalStorage DS Open API → Check CIMOM Registration. A window opens displaying the wbem services as shown in Figure 7-38. These services have either registered themselves with SLP, or you have registered them explicitly with SLP using slptool. If you changed the default ports for a CIMOM during installation, the port number should be correctly listed here. It might take some time for a CIM Agent to register with SLP. Figure 7-38 Verify CIM Agent registration with SLP Note: If the verification of the CIMOM registration is not successful, stop and restart the SLP and CIMOM services. Note that the CIMOM will attempt to contact each storage subsystem registered to it. Therefore, the startup may take some time, especially if it is not able to connect and authenticate to any of the registered devices. Use the verifyconfig -u superuser -p passw0rd command, where superuser is the user name and passw0rd is the password for the user name that you configured to manage the268 IBM TotalStorage Productivity Center: The Next Generation
    • CIMOM, to locate all WBEM services in the local network. You need to define the TotalStorage Productivity Center superuser name and passw0rd in order for TotalStorage Productivity Center to have the authority to manage the CIMOM. The verifyconfig command checks the registration for the ESS CIM Agent and checks that it can connect to the ESSs. At the ITSO lab, we configured two ESSs (as shown in Figure 7-39). Figure 7-39 The verifyconfig command7.5.1 Adding your CIMOM to the TotalStorage Productivity Center GUI Now that you have added devices to your CIMOM, they should be made known to TotalStorage Productivity Center. This done by adding the CIMOM to TotalStorage Productivity Center entering the information into the GUI panel similar to Figure 7-40. Figure 7-40 Adding a CIMOM to TotalStorage Productivity Center After entering the CIMOM information, test the connectivity to your CIMOM. Click the Test CIMOM connectivity before adding box. This is shown in Figure 7-41 on page 270. Chapter 7. CIMOM installation and customization 269
    • Figure 7-41 Test the connectivity - successfully done7.5.2 Problem determination In case of errors, you can start debugging by examining the cimom.log file. This file is located in the C:Program FilesIBMcimagent directory. A sample is shown in Figure 7-42. The entries of specific interest are: CMMOM050OI Registered service service:wbem:https://x.x.x.x:5989 with SLP SA CMMOM0409I Server waiting for connections This first entry indicates that the CIMOM has sucessfully registered with SLP using the port number specified at ESS CIM agent install time. The second entry indicates that it has started sucessfully and is waiting for connections. Figure 7-42 CIMOM Log file270 IBM TotalStorage Productivity Center: The Next Generation
    • If you still have problems, Refer to the DS Open Application Programming Interface Reference for an explanation and resolution of the error messages. You can find this Guide in the doc directory at the root of the CIM Agent CD.7.5.3 Confirming that ESS CIMOM is available Before you proceed, you need to be sure that the DS CIMOM is listening for incoming connections. To do this, run a telnet command from the server where TotalStorage Productivity Center resides. A successful telnet on the configured port (as indicated by a black screen with cursor on the top left) will tell you that the DS CIMOM is active. You selected this port during DS CIMOM code installation. If the telnet connection fails, you will have a panel like the one shown in Figure 7-43. In that event, you must investigate the problem until you get a blank screen for telnetting the CIMOM on its port. Figure 7-43 Example of telnet fail connection7.5.4 Start the CIM Browser Another method to verify that your DS Open CIM Agent is up and running, is to use the CIM Browser interface. The CIM-Browser is an interface to the whole tree of the WBEM language the CIMOM is using in its communication with the CIM-provider. Attention: As with most of the CIM Agents, the DS Open CIM Agent is shipped with its own workshop or browser application. CIM Browsers are not intended as an enduser tool. Instead, they are a tool for the developers of management applications. That is why they are shipped with the CIM Agent. Be careful not to delete or destroy anything while using the workshop. 1. For Microsoft Windows machines, change the working directory to: c:Program Filesibmcimagent 2. Run startcimbrowser.The WBEM browser in Figure 7-44 on page 272 opens. The default user name is superuser and the default password is passw0rd. If you have already changed it using the setuser command, the new userid and password must be provided. This should be set to the TotalStorage Productivity Center userid and password. Chapter 7. CIMOM installation and customization 271
    • Figure 7-44 CIMOM Browser Login Panel When login is successful, you should see a panel similar to the one in Figure 7-45. Figure 7-45 CIMOM Browser entry panel 3. Now that the CIM Browser has started, the following scenario will take you through the steps to find information about the installed subsystems. The scenario assumes that you have subsystems registered within your CIMOM. In the CIM Workshop, follow the path down to the element shown in Figure 7-46 on page 273.272 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-46 Select your Physical Element4. After selecting the physical element, select Instances → Show, as show in Figure 7-47.Figure 7-47 Show selected elements In Figure 7-48 on page 274, you can see elements from our subsystem and their corresponding values. Chapter 7. CIMOM installation and customization 273
    • Figure 7-48 Elements and their values This concludes the usage sample for this CIM-Workshop. Note, that other CIMOMs have their own CIMOM-Workshop. They might look and behave a little different than this one, but the principle is the same.7.6 Installing CIM agent for IBM DS4000 family To manage IBM DS4000 disk subsystems using SMI-Specifications V1.0.2, we need the software component mentioned on the sites listed in this section. The CIM Agent for DS4000 family is provided by Engenio and it is called Engenio SANtricity SMI-S Provider. For the TotalStorage Productivity Center CIMOM and code levels and the technical documentation go to the following site: http://www-03.ibm.com/servers/storage/support/software/ The following Engenio sites are useful for the most current CIMOM levels (Note: The information contained on this Web site is not for use with TotalStorage Productivity Center.): http://www.engenio.com/products/smi_provider.html Go the following Web site for information about TotalStorage Productivity Center: http://www.engenio.com/products/smi_provider_archive.html Before going any further, be sure to run one of the supported firmware levels mentioned there. Attention: Note that there are Web sites from Engenio where you can find the very latest SMI-S provider, but it must be stated that this code is inappropriate for use with TotalStorage Productivity Center. Throughout the remainder of this chapter the terms DS4000 and FaStT are used interchangeably.274 IBM TotalStorage Productivity Center: The Next Generation
    • The code level used for this redbook is V1.1.0.614. This information can be found in thedirectory of your CIMOM server.C:Program FilesEngenioProviderSMI_SProviderdocChangeLog.txt1. From the Web site mentioned previously, select the operating system used for the server on which the Engenio SMI-S Provider has to be installed. For example, with Windows you have to download a setup.exe file. Save it to a directory on the server you in which will be installing the Engenio SMI-S Provider.2. Launch the setup.exe file to begin the Engenio SMI-S Provider installation. The InstallShield Wizard for Engenio SMI-S Provider window opens (see Figure 7-49). Click Next to continue.Figure 7-49 Engenio SMI-S Provider welcome panel3. The Engenio License Agreement window opens next. If you agree with the terms of the license agreement, click Yes to accept the terms and continue the installation (see Figure 7-50).Figure 7-50 Engenio License Agreement4. The System Info window opens. The minimum requirements are listed along with the install system disk free space and memory attributes as shown in Figure 7-51 on Chapter 7. CIMOM installation and customization 275
    • page 276. If the target system fails the minimum requirements evaluation, then a notification window will appear and the installation will fail. Click Next to continue. Figure 7-51 System Info window 5. The Choose Destination Location window opens. Click Browse to choose another location or click Next to begin the installation of the DS4000/FAStT CIM agent (see Figure 7-52). Figure 7-52 Choose a destination The InstallShield Wizard prepares and copies the files into the destination directory. Figure 7-53 on page 277 shows the installation progress.276 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-53 Install progress6. In the Enter IPs and Hostnames window, enter the IP addresses and hostnames of the DS4000 devices this CIM Agent will manage as shown in Figure 7-54.Figure 7-54 DS4000 device list7. Use the Add New Entry button to add the IP addresses or host names of the DS4000 devices with which this DS4000 CIM Agent will communicate. Enter one IP address or host name at a time until all the DS4000 devices have been entered and click Next (see Figure 7-55 on page 278). Chapter 7. CIMOM installation and customization 277
    • Figure 7-55 Enter host name or IP address Important: Do not enter the IP address of a DS4000 device in multiple DS4000 CIM Agents within the same subnet. This can cause unpredictable results on the TotalStorage Productivity Center for Disk server and could cause a loss of communication with the DS4000 devices. 8. If the list of hostnames or IP addresses has been previously written to a file, use the Add File Contents button, opening Windows Explorer. Locate and select the file, then click Open to import the file contents. The file where all the IP-Addresses or hostnames are collected in is located in this Microsoft Windows directory: C:Program FilesEngenioProviderSMI_SProviderbinarrayhosts.txt When all the DS4000 device hostnames and IP addresses have been entered, your panel should list them all as shown in Figure 7-56. Figure 7-56 Device list Click Next to start the Engenio SMI-S Provider Service (see Figure 7-57 on page 279).278 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-57 Provider Service startingWhen the Service has started, the installation of the Engenio SMI-S Provider is complete(see Figure 7-58).Figure 7-58 Installation completeDuring the start of the service, the Engenio code processes all the entries in the arrayhosts.txtfile. The configuration is stored in an another file named:C:Program FilesEngenioProviderSMI_SProviderbinproviderStoreEvery time you change anything with the registered DS4000/FaStT Controllers and restartthe Engenio CIMOM, and when you make a new discovery, the providerStore andarrayhosts.txt are updated with a new time stamp.arrayhosts.txt file exampleIf you chose the default installation directory, the installer creates a file named arrayhost.txt inthe following path (see Figure Figure 7-59):C:Program FilesEngenioProviderSMI_SProviderbinarrayhost.txtIn this file, the IP addresses of installed DS 4000 units can be reviewed, added, or edited.After editing this file, you must restart the service.Figure 7-59 Arrayhost file Chapter 7. CIMOM installation and customization 279
    • Verifying Engenio SMI-S Provider Service availability You can verify that the Engenio SMI-S Provider service has started from the Windows Services window, as shown in Figure 7-60. If you change the contents of the arrayhost file for adding and deleting DS4000 devices, then you must restart the LSI Provider service using the Windows Services panel. Figure 7-60 LSI Provider Service Another method is to use the tool supplied in the installation directory of your DS4000 CIM Agent. The tool is named runservice.bat and can be found in the path: C:Program FilesEngenioProviderSMI_SProviderbin Figure 7-61 shows the runservice.bat parameters and their output. runservice.bat -s Looking in C:Program FilesEngenioProviderSMI_SProviderbinService.ini for service name Service Name: Engenio SMI-S Provider. Stopping Engenio SMI-S Provider Server. Engenio SMI-S Provider Server stopped. runservice.bat -q Looking in C:Program FilesEngenioProviderSMI_SProviderbinService.ini for service name Service Name: Engenio SMI-S Provider. Service Status: SERVICE_STOPPED runservice.bat -t Looking in C:Program FilesEngenioProviderSMI_SProviderbinService.ini for service name Service Name: Engenio SMI-S Provider. Starting Engenio SMI-S Provider Server. Engenio SMI-S Provider Server started. runservice.bat -q Looking in C:Program FilesEngenioProviderSMI_SProviderbinService.ini for service name Service Name: Engenio SMI-S Provider. Figure 7-61 Sample usage of runservice.bat280 IBM TotalStorage Productivity Center: The Next Generation
    • 7.6.1 Registering DS4000 CIM agent if SLP-DA is in place If you had to set up a SLP-DA structure, then the DS4000 CIM Agent needs to be registered with an SLP DA. This might be the case when the DS4000 CIM Agent is in a different subnet than that of IBM TotalStorage Productivity Center environment. The registration is not currently provided automatically by the CIM Agent. You register the DS4000 CIM Agent with SLP DA from a command prompt using the slptool command. An example of the slptool command follows this paragraph. You must change the IP address to reflect the IP address of the workstation or server where you installed the DS4000 family DS 4000 CIM Agent. The IP address of our DS4000 CIM Agent is 9.1.38.39 and port 5988. You need to execute this command on your SLP DA server if a SLP-DA setup was chosen before. In our ITSO lab, we did not use a SLP DA server. Go to the command line and switch to the directory listed here, then issue the following command. For example, switch to this directory: C:Program FilesIBMcimagentslp Execute slptool register service:wbem:http:9.1.38.39:5988 Important: You cannot have the DS4000 management password set if you are using IBM TotalStorage Productivity Center, because the Engenio CIMOM has no capability to keep track of the user ID and password combinations which would be necessary to get into the managed DS4000/FaStT subsystems. At this point, you can run following command on the SLP DA server, or any other system where SLP is installed, to verify that DS 4000 family DS4000 CIM agent is registered with SLP DA. slptool findsrvs wbem The response from this command will show the available services which you may verify.7.6.2 Verifying and managing CIMOM availability Verify that TotalStorage Productivity Center can authenticate and discover the CIMOM agent services which are either registered by SLP DA or manually entered into CIMOM registration. The Engenio Provider does not require any specific userid and password to authenticate, just enter any nonzero userid and password when adding the CIMOM from TPC GUI (see Figure 7-62 on page 282). Enter the following values in the IBM TotalStorage Productivity Center panel: Host: your IP address or fully qualified host name of the Engenio SMI-S Provider server Port: unsecure port 5988 (Engenio does not support secure communication as we write) Username: any username Password: any password (not null) Interoperability Namespace: /interop protocol: HTTP Display name: any name that can help you identify the CIM Agent Chapter 7. CIMOM installation and customization 281
    • Figure 7-62 Add CIMOM Starting the CIM Browser Following are screen captures showing how to log on and find information about your subsystem. Attention: As with most of the CIM Agents, the Engenio Provider is shipped with its own workshop or browser application. CIM Browsers are not intended as an enduser tool. Instead they are a tool for the developers of management applications to be used when an error is encountered. That is why they are shipped with the CIM Agent. Be careful not to delete or destroy anything while using the workshop. 1. Start the cimworkshop.bat found in the path: C:Program FilesEngenioProviderwbemservicesbin 2. Enter a value for userid and password. Because the CIMOM runs unauthenticated, you can use any values (see Figure 7-63 on page 283).282 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-63 Logon to the CIMWORKSHOP and entry screen3. After you log on, you must switch to another namespace by using the drop-down button. For the IBM DS4000 it is LSISSI as shown in Figure 7-64 on page 284. Chapter 7. CIMOM installation and customization 283
    • Figure 7-64 Change the namespace and navigate to the physical elements. 4. From the Action Menu, select Show Instances, as shown in Figure 7-65 on page 285.284 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-65 Show instances - the detailed values of the elements.7.7 Configuring CIMOM for SAN Volume Controller The CIM Agent for SAN Volume Controller is part of the SAN Volume Controller Console and provides TotalStorage Productivity Center with access to SAN Volume Controller clusters. You must customize the CIM Agents in your enterprise to accept the TotalStorage Productivity Center user name and password. Figure 7-66 on page 286 explains the communication between TotalStorage Productivity Center and SAN Volume Controller Environment. Chapter 7. CIMOM installation and customization 285
    • Figure 7-66 TotalStorage Productivity Center SVC communication For additional details on how to configure the SAN Volume Controller Console refer to the IBM Redbook IBM TotalStorage Introducing the SAN Volume Controller and SAN Integration Server, SG24-6423. To discover and manage the SAN Volume Controller, we need to ensure that our TotalStorage Productivity Center superuser name and password (the account specified in the TotalStorage Productivity Center configuration panel as shown in 7.7.1, “Adding the SVC TotalStorage Productivity Center for Disk user account” on page 286) matches an account defined on the SAN Volume Controller console. In our case we implemented username TPCSUID and password ITSOSJ. This userid and password combination has to be used later when you authenticate the CIMOM Agent in the TPC GUI. You might want to adapt a similar nomenclature and setup the username and password on each SAN Volume Controller CIMOM to be monitored with TotalStorage Productivity Center.7.7.1 Adding the SVC TotalStorage Productivity Center for Disk user account As stated previously, you should implement a unique user ID to manage the SAN Volume Controller devices in TotalStorage Productivity Center for Disk. This can be achieved at the SAN Volume Controller console using the following steps: 1. Log in to the SAN Volume Controller console with a superuser account. 2. Click Users under My Work on the left side of the panel (see Figure 7-67 on page 287).286 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-67 SAN Volume Controller console3. Select Add a user in the drop-down under Users panel and click Go (see Figure 7-68).Figure 7-68 SAN Volume Controller console Add a user Chapter 7. CIMOM installation and customization 287
    • 4. An introduction screen is opened, click Next (see Figure 7-69). Figure 7-69 SAN Volume Controller Add a user wizard 5. Enter the User Name and Password and click Next (see Figure 7-70 on page 289).288 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-70 SAN Volume Controller Console Define users panel6. Select your candidate cluster and move it to the right, under Administrator Clusters (see Figure 7-71). Click Next to continue.Figure 7-71 SAN Volume Controller console Assign administrator roles7. Click Next after you Assign service roles (see Figure 7-72 on page 290). Chapter 7. CIMOM installation and customization 289
    • Figure 7-72 SAN Volume Controller Console Assign user roles 8. Click Finish after you Verify user roles (see Figure 7-73 on page 291).290 IBM TotalStorage Productivity Center: The Next Generation
    • Figure 7-73 SAN Volume Controller Console Verify user roles9. After you click Finish, the Viewing users panel opens (see Figure 7-74).Figure 7-74 SAN Volume Controller Console Viewing Users Chapter 7. CIMOM installation and customization 291
    • Confirming SAN Volume Controller CIMOM availability Before you proceed, you need to be sure that the CIMOM on the SAN Volume Controller is listening for incoming connections. To do this, issue a telnet command from the server where TotalStorage Productivity Center resides. A successful telnet on port 5989 (as indicated by a black screen with cursor on the top left) will tell you that the CIMOM SAN Volume Controller console is active. If the telnet connection fails, you will have a panel similar to the one in Figure 7-75. Figure 7-75 Example of telnet fail connection7.7.2 Registering the SAN Volume Controller host in SLP The next step to detecting an SAN Volume Controller is to register the SAN Volume Controller console manually to the SLP DA. Attention: Starting with SVC V2.1, the default port is 5999. When upgrading SVC from a version earlier than 2.1 to a version 2.1 or later, the CIM port should be changed from 5989 to 5999. For detailed information, refer to this Web site: http://www-1.ibm.com/support/docview.wss?rs=591&context=STCAFUL&context=STCKNX4&dc=DB500 &uid=ssg1S1002559&loc=en_US&cs=utf-8&lang=en To register the SAN Volume Controller Console, perform the following command on the SLP DA server: slptool register service:wbem:https://ipaddress:5999 Where ipaddress is the SAN Volume Controller console IP address. Run a verifyconfig command to confirm that SLP is aware of the SVC console registration. Tip: If your SAN Volume Controller console resides in the same subnet as the TotalStorage Productivity Center server, SLP registration will be automatic so you do not need to perform the SLP registration.7.8 Configuring CIMOM for McData switches Before running performance monitoring jobs against switches, you must discern if the switch you want to monitor is either using an embedded CIM agent, or a proxy CIM Agent.292 IBM TotalStorage Productivity Center: The Next Generation
    • As an example of exploiting SMI-S for switch monitoring, we focus our tests on two McDATA switches available. McDATA, as Brocade, is providing an proxy CIM Agent to connect to its devices. In order to manage McDATA fabric using SMI-Specifications V1.1, we need the software component mentioned on this site: http://www.snia.org/ctp/conformingproviders/mcdata At the time of writing, this is McDATA SMI-S Interface: http://www-1.ibm.com/support/docview.wss?rs=591&context=STCAFUL&context=STCKNX4&dc=DB500&ui d=ssg1S1002559&loc=en_US&cs=utf-8&lang=en The McDATA SMI-S Interface is a software product that provides support for the SMI-S for McDATA director and switch products. McDATA SMI-S Interface provides an SMI-S interface for management of McDATA products. It exposes a WBEM (specifically, CIM XML) interface for management.7.8.1 Planning the installation These are the planning considerations we suggest you think through before installing the SMI-S Interface. Prerequisites The McDATA SMI-S Interface solution requires the hardware and software described in the following sections. Table 7-1 lists the switch hardware supported for this release of McDATA SMI-S Interface and the minimum levels of firmware required by the hardware. Table 7-1 Supported Hardware Manufacturer Product Minimum Firmware Supported McData ED-5000 Firmware version 4.1 Intrepid 6064 EOS version 7.0 Intrepid 6140 EOS version 7.0 Sphereon 3016 EOS version 7.0 Sphereon 3032 EOS version 7.0 Sphereon 3216 EOS version 7.0 Sphereon 3232 EOS version 7.0 Sphereon 4300 EOS version 7.0 Sphereon 4500 EOS version 7.0 Sphereon 4700 EOS version 7.0 Intrepid 10000 E/OSn version 6.3 The McDATA SMI-S Interface, version 1.1, implementation supports the following operating system (OS) platforms: Windows 2000, with Service Pack 2 or higher Solaris 9 Chapter 7. CIMOM installation and customization 293
    • 7.8.2 Supported configurations McDATA SMI-S Interface communicates with a device using one of two modes. If you prefer to keep the EFCM Management Software as an additional interface to your s