Dir5.20 Docs Install

IBM Systems
IBM Director Planning, Installation, and Configuration Guide Version 5.20 Update 1
GC30-4163-00
IBM Systems
IBM Director Planning, Installation, and Configuration Guide Version 5.20 Update 1
GC30-4163-00
Note Before using this information and the product it supports, read the information in Notices on page 365.
This edition applies to version 5.20 update 1 of IBM Director for i5/OS (program number 5722-DR1), IBM Director for AIX and Linux on POWER (program number 5765-DR1), IBM Director for Linux on System z (program number 5648-DR1), and IBM Director on x86 (program number 5765-DIR) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation 1999, 2007. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . v Tables . . . . . . . . . . . . . . . vii About this book . . . . . . . . . . . ix
Conventions and terminology . . . . . . . . ix Related information . . . . . . . . . . . . ix How to send your comments . . . . . . . . xii Supported operating systems . . . . . . . 73 Support of IBM Director tasks across operating systems . . . . . . . . . . . . . . . 80 IBM Director task support for BladeCenter products . . . . . . . . . . . . . . 88 IBM Director task support for Storage products 89 Supported database applications . . . . . . 90 Planning to install IBM Director . . . . . . . 92 Reviewing the environment . . . . . . . . 92 Choosing IBM Director optional components and extensions . . . . . . . . . . . . . . 96 Licensing requirements for IBM Director components and extensions. . . . . . . . 101 Choosing between standard and express installation of IBM Director Server . . . . . 103 Choosing the IBM Director Server installation options . . . . . . . . . . . . . . 104 Choosing where to install IBM Director Server 106 Choosing the IBM Director database application 107 Choosing the management level for managed systems . . . . . . . . . . . . . . 110 Planning for virtual environments . . . . . 112 Planning to update IBM Director . . . . . . . 113 Version compatibility of IBM Director version 5.20 components . . . . . . . . . . . 114 Version compatibility of IBM Director version 5.20.1 components . . . . . . . . . . . 114 Planning for events . . . . . . . . . . . 116 Planning events to be monitored . . . . . . 116 Planning for event action plan implementations 117 Planning IBM Director users and user groups . . 120
New in IBM Director . . . . . . . . . xiii

New in version 5.20.1 . . . . . . . . . . . xiii New in version 5.20 . . . . . . . . . . . xv
Chapter 1. Getting started with IBM Director . . . . . . . . . . . . . . . 1

Introducing IBM Director . . . . . . . . IBM Director components . . . . . . . . IBM Director Core Services . . . . . . IBM Director Agent . . . . . . . . . IBM Director Console . . . . . . . . IBM Director Server . . . . . . . . . Concepts . . . . . . . . . . . . . Accessibility . . . . . . . . . . . Associations . . . . . . . . . . . Common Information Model . . . . . . Discovery . . . . . . . . . . . . Event management . . . . . . . . . External application tasks. . . . . . . Managed-object groups . . . . . . . High availability . . . . . . . . . . Managed objects . . . . . . . . . . Managed system . . . . . . . . . Mass configuration . . . . . . . . . Microsoft Cluster Management . . . . . Naming conventions and physical platform managed objects . . . . . . . . . . Network-timeout settings and command processing . . . . . . . . . . . . Scalable objects . . . . . . . . . . Security . . . . . . . . . . . . Service processors . . . . . . . . . SNMP devices . . . . . . . . . . Software distribution . . . . . . . . Storage managed objects . . . . . . . Update Manager . . . . . . . . . Update Manager profile . . . . . . . UpdateXpress System Pack . . . . . . Upward integration. . . . . . . . . User interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2 3 4 4 5 5 5 5 9 11 16 27 30 32 32 34 36 36
Chapter 3. Installing . . . . . . . . 123

Preparing to install IBM Director . . . . . . . Obtaining licenses for IBM Director components and extensions . . . . . . . . . . . . Preparing the IBM Director database . . . . Preparing firewalls and proxies for IBM Director Preparing to manage service processors with IBM Director . . . . . . . . . . . . Preparing the management server . . . . . Preparing a system for IBM Director Console Preparing a Level-2 managed system . . . . Preparing a Level-1 managed system . . . . Preparing to manage a BladeCenter . . . . . Preparing Windows XP managed systems . . . Preparing Hardware Management Console devices for discovery with IBM Director . . . Installing IBM Director using the Standard installation . . . . . . . . . . . . . . Installing IBM Director Server using the Standard installation . . . . . . . . . . Installing IBM Director Console . . . . . . Installing Level 1: IBM Director Core Services Installing Level 2: IBM Director Agent . . . . 123 123 125 134 135 140 152 155 162 167 170 171 172 172 210 221 233
. 37 . . . . . . . . . . . . 38 39 42 49 54 55 57 60 60 61 61 64
Chapter 2. Planning . . . . . . . . . 67
Specified operating environments . . . . Hardware requirements for IBM Director Network requirements . . . . . . .
Copyright IBM Corp. 1999, 2007
. . .
. . .
. 67 . 67 . 70
iii
Changing IBM Director installation options . . Upgrading and updating IBM Director . . . . . Backing up IBM Director data before upgrading or updating . . . . . . . . . . . . . Upgrading to IBM Director 5.20 or later from previous releases . . . . . . . . . . . Updating IBM Director . . . . . . . . . Restoring IBM Director data . . . . . . . Initially configuring IBM Director . . . . . . Configuring IBM Director after an Express installation . . . . . . . . . . . . . Managing users and user groups for IBM Director . . . . . . . . . . . . . . Authorizing Request Access on a managed system . . . . . . . . . . . . . . Using IBM Director in a high-availability environment . . . . . . . . . . . . . Configuring discovery preferences . . . . . Performing server-initiated discovery of managed objects . . . . . . . . . . . Configuring software-distribution preferences Enabling SNMP access and trap forwarding for Linux . . . . . . . . . . . . . . .
258 262 263 264 272 273 273 274 275 291 291 296 314 315 318
Configuring the database on Linux or AIX . Configuring the database on a Windows management server . . . . . . . . . Enabling SNMP access and trap forwarding for Linux . . . . . . . . . . . . . . .
. 326 . 327 . 328
Chapter 6. Troubleshooting . . . . . 329

Installation troubleshooting . . . . . . . . . Linux installation troubleshooting . . . . . Windows installation troubleshooting . . . . Other operating-system installations troubleshooting . . . . . . . . . . . . Upgrade and patch installations fail . . . . . IBM Director uninstallation fails . . . . . . Getting help and support . . . . . . . . . Finding information about IBM Director problems . . . . . . . . . . . . . . Information to provide to the IBM Technical Support Center or IBM Director customer forum Getting fixes . . . . . . . . . . . . . Software service and support . . . . . . . 329 329 330 331 333 333 334 334 337 338 339
Chapter 4. Uninstalling IBM Director

Uninstalling IBM Director on i5/OS . . . . . Uninstalling IBM Director Server using DLTLICPGM . . . . . . . . . . . Uninstalling IBM Director Agent on i5/OS . Uninstalling IBM Director on Linux or AIX . . Uninstalling IBM Director on Windows . . . . Uninstalling IBM Director using the Windows Add/Remove Programs feature . . . . . Uninstalling IBM Director using the dirunins command . . . . . . . . . . . . Uninstalling IBM Director Agent on NetWare. . Uninstalling IBM Director Core Services before migrating to an earlier version of IBM Director .
321
. 321 . . . . 321 321 321 322
Appendix A. Accessibility features for IBM Director . . . . . . . . . . . . 341 Appendix B. Default installation directories for IBM Director . . . . . 353 Appendix C. Lightweight Directory Access Protocol authentication properties for IBM Director Server . . 355 Appendix D. Installing Software Distribution Premium Edition on Linux 359 Appendix E. Worksheets . . . . . . 361
. . . . . 361 . 362
. 322 . 323 . 323 . 324
Chapter 5. Modifying an IBM Director installation . . . . . . . . . . . . 325

Enabling the Wake on LAN feature . . . . . . Enabling the Wake on LAN feature for Linux or AIX . . . . . . . . . . . . . . . Enabling the Wake on LAN feature on Windows Configuring the database on the management server . . . . . . . . . . . . . . . . 325 325 325 326
Worksheet: Database planning . . . . . Worksheet: Installing IBM Director Server .
Notices . . . . . . . . . . . . . . 365 Trademarks . . . . . . . . . . . . 367 Index . . . . . . . . . . . . . . . 369
iv
IBM Director Planning, Installation, and Configuration Guide
Figures
1. 2. 3. 4. Hardware in an IBM Director environment 2 Software in an IBM Director environment 3 Managing system updates in an IBM Director environment . . . . . . . . . . . . 60 Example of BladeCenter deployment network when IBM Director Server is not installed on a blade server . . . . . . . . . . . 168 Example of BladeCenter deployment network when IBM Director Server is installed on a blade server . . . . . . . . . . . . 170 Installing IBM Director Server on Windows: Feature and Installation Directory Selection window . . . . . . . . . . . . . 201 Installing IBM Director Server on Windows: Feature and Installation Directory Selection window . . . . . . . . . . . . . 202 Installing IBM Director Server on Windows: IBM Director Service Account Information window . . . . . . . . . . . . . 203 Installing IBM Director Server on Windows: Encryption Settings window . . . . . . 204 Installing IBM Director Server on Windows: Network Driver Configuration window . . . 205 Installing IBM Director Server: IBM Director Database Configuration window . . . . . 206 12. Creating a software package: Software Distribution Manager window (Standard Edition) . . . . . . . . . . . . Creating a software package: Software Distribution Manager window (Premium Edition) . . . . . . . . . . . . Creating a software package: Software Distribution Manager window (Standard Edition) . . . . . . . . . . . . Creating a software package: Software Distribution Manager window (Premium Edition) . . . . . . . . . . . . Modifying IBM Director Agent on NetWare: Choose Destination Location window . . Modifying IBM Director Agent on NetWare: Select Components window . . . . . . Program Maintenance window . . . . . Creating a software package: Software Distribution Manager window (Standard Edition) . . . . . . . . . . . . Creating a software package: Software Distribution Manager window (Premium Edition) . . . . . . . . . . . . Program Maintenance window . . . . . . 232
13.
. 232
14.
5.
. 257
15.
6.
. 257 . 259 . 260 . 261
16. 17. 18. 19.
7.
8.
9. 10. 11.
. 270
20.
21.
. 270 . 326
vi
Tables
1. New operating systems supported by IBM Director Version 5.20 Update 1 . . . . . . xiv 2. Default associations other than None . . . . 8 3. Comparison of resource monitor and process monitor features . . . . . . . . . . . 27 4. Location of resource-bundle files by operating system . . . . . . . . . . . . . . 28 5. Location of customized image files by operating system . . . . . . . . . . . 29 6. IBM Director groups that are used with scalable objects . . . . . . . . . . . 31 7. IBM Director groups that are used with scalable objects . . . . . . . . . . . 41 8. Initial security state of IBM Director Agent 43 9. Encryption state and data transmitted between IBM Director Server and IBM Director Agent . 48 10. In-band communication between service processors and IBM Director Server . . . . 50 11. IBM Director Agent features that handle in-band alerts . . . . . . . . . . . . 51 12. Gateway service processors and communication with service processors on an ASM interconnect network . . . . . . . 52 13. Out-of-band alerting pathways . . . . . . 52 14. Out-of-band alert-forwarding strategies 53 15. x86-compatible systems: Minimum hardware requirements . . . . . . . . . . . . 68 16. Servers running AIX: Minimum hardware requirements . . . . . . . . . . . . 68 17. Servers running Linux on POWER: Minimum hardware requirements. . . . . . . . . 69 18. System i products: Minimum hardware requirements . . . . . . . . . . . . 69 19. Minimum hardware requirements for IBM Director on System z servers . . . . . . . 70 20. Supported versions of network protocols 70 21. Types of data transmission and supported network protocols . . . . . . . . . . 71 22. Ports used by IBM Director . . . . . . . 71 23. Operating systems supported by IBM Director on System x systems; IBM and third-party x86-based systems . . . . . . . . . . 74 24. Operating systems supported by IBM Director on System i and System p products . . . . 76 25. Operating systems supported by IBM Director on System z systems . . . . . . . . . 76 26. Operating systems supported by IBM Director on System x systems; IBM and third-party x86-based systems . . . . . . . . . . 77 27. Operating systems supported by IBM Director on System i and System p products . . . . 79 28. Operating systems supported by IBM Director on System z systems . . . . . . . . . 79 29. Hardware Status support for System x servers; IBM and third-party x86-based systems . . . 84 30. Hardware Status support for System i platforms and System p servers . . . . . . 84 31. Hardware Status support for System z servers 85 32. Operating systems supported by System x servers; IBM and third-party x86-based systems . . . . . . . . . . . . . . 85 33. Operating systems supported by System i platforms and System p servers . . . . . . 86 34. Operating systems supported by System z servers . . . . . . . . . . . . . . 87 35. Operating systems supported by System x servers and IBM x86-based systems . . . . 87 36. IBM Director task support for BladeCenter products . . . . . . . . . . . . . 89 37. IBM Director task support for Storage products 89 38. Database applications supported by IBM Director 5.20.1. . . . . . . . . . . . 90 39. Database applications supported by IBM Director 5.20 . . . . . . . . . . . . 91 40. Hardware identification worksheet for IBM Director . . . . . . . . . . . . . . 93 41. Local and remote subnets worksheet . . . . 94 42. IBM Director optional component planning worksheet . . . . . . . . . . . . . 96 43. . . . . . . . . . . . . . . . . 107 44. Database applications supported by IBM Director 5.20.1 . . . . . . . . . . . 108 45. Additional database selection criteria 109 46. Management-level selection worksheet1 110 47. Compatibility of IBM Director Version 5.20 components with other component versions . 114 48. Compatibility of IBM Director Version 5.20.1 components with other component versions . 115 49. Compatibility of IBM Director extensions with IBM Director version 5.20.1 . . . . . . . 115 50. Servers with service processors that are supported for Level-1 or Level-2 management by IBM Director. . . . . . . . . . . 136 51. Required drivers for in-band management of service processors . . . . . . . . . . 138 52. AIX Pegasus CIM Server and providers 141 53. Required RPMs . . . . . . . . . . . 143 54. Installing IBM Director Server: IBM LM78 and SMBus device drivers for Linux . . . . 145 55. Making the IBM Director installation code available to Linux on System z . . . . . 149 56. Required RPMs . . . . . . . . . . . 150 57. Required RPMs . . . . . . . . . . . 151 58. Required RPMs . . . . . . . . . . . 152 59. Making the IBM Director installation code available to Linux on System z . . . . . 153 60. Required RPMs . . . . . . . . . . . 154 61. AIX Pegasus CIM Server and providers 156 62. Required RPMs . . . . . . . . . . . 158 63. Required RPMs . . . . . . . . . . . 158
vii
64. Making the IBM Director installation code available to Linux on System z . . . . . 65. Required RPMs . . . . . . . . . . . 66. Required RPMs . . . . . . . . . . . 67. Required RPMs . . . . . . . . . . . 68. Making the IBM Director installation code available to Linux on System z . . . . . 69. Required RPMs . . . . . . . . . . . 70. Installation options for IBM Director Server on AIX . . . . . . . . . . . . . . 71. Database configuration . . . . . . . . 72. Installation options for IBM Director Server on i5/OS . . . . . . . . . . . . . 73. Installation options for IBM Director Server on Linux for System x . . . . . . . . 74. Database configuration . . . . . . . . 75. Installation options for IBM Director Server on Linux for System z . . . . . . . . 76. Database configuration . . . . . . . . 77. Installation options for IBM Director Server on Linux on POWER . . . . . . . . . 78. Database configuration . . . . . . . . 79. Installation options for IBM Director Server on Windows . . . . . . . . . . . . 80. Installation options for IBM Director Server on Windows . . . . . . . . . . . . 81. Optional installation parameters . . . . . 82. Installation options for IBM Director Console on AIX . . . . . . . . . . . . . . 83. Installation options for IBM Director Console on Linux for System x . . . . . . . . 84. Installation options for IBM Director Console on Linux for System z . . . . . . . . 85. Installation options for IBM Director Console on Linux on POWER . . . . . . . . . 86. Installation options for IBM Director Console on Windows . . . . . . . . . . . . 87. Installation options for IBM Director Console on Windows . . . . . . . . . . . . 88. Optional installation parameters . . . . . 89. Installation options for IBM Director Core Services on Linux for System x . . . . . 90. Installation options for IBM Director Core Services on Linux for System z . . . . . 91. Installation options for IBM Director Core Services on Linux on POWER . . . . . . 92. Installation options for IBM Director Core Services on Windows . . . . . . . . . 93. Installation options for IBM Director Core Services on Windows . . . . . . . . . 94. Optional installation parameters . . . . . 95. Source and file names of descriptor files used to install IBM Director Core Services using Software Distribution . . . . . . . . . 96. Installation options for IBM Director Agent on AIX . . . . . . . . . . . . . . 97. Installation options for IBM Director Agent on i5/OS . . . . . . . . . . . . .
159 160 163 163 164 165 173 175 178 181 184 187 190 194 196 200 209 210 211 212 214 215 217 219 221 221 223 224 226 228 229
230 234 236
98. Installation options for IBM Director Agent on Linux for System x . . . . . . . . 99. Installation options for IBM Director Agent on Linux for System z . . . . . . . . 100. Installation options for IBM Director Agent on Linux on POWER . . . . . . . . . 101. Installation options for IBM Director Agent on Windows . . . . . . . . . . . . 102. Installation options for IBM Director Agent on Windows . . . . . . . . . . . . 103. Optional installation parameters . . . . . 104. Optional installation parameters . . . . . 105. Source and file names of descriptor files used to install IBM Director Agent using Software Distribution . . . . . . . . . . . . 106. Source and file names of files used to upgrade IBM Director Agent using Software Distribution . . . . . . . . . . . . 107. Default IBM Director function usage groups for i5/OS . . . . . . . . . . . . . 108. dirunins parameters . . . . . . . . . 109. Keyboard shortcuts for windows . . . . . 110. Keyboard shortcuts for option panes 111. Keyboard shortcuts for scroll panes . . . . 112. Keyboard shortcuts for split panes . . . . 113. Keyboard shortcuts for notebooks (tabbed panes) . . . . . . . . . . . . . . 114. Keyboard shortcuts for frames . . . . . . 115. Additional keyboard shortcuts for frames in External Application Launch wizard . . . . 116. Keyboard shortcuts for internal frames 117. Keyboard shortcuts for menu bar . . . . . 118. Keyboard shortcuts for menus . . . . . . 119. Keyboard shortcuts for menu items . . . . 120. Keyboard shortcuts for check-box menu items 121. Keyboard shortcuts for radio-button menu items . . . . . . . . . . . . . . 122. Keyboard shortcuts for pop-up menus 123. Keyboard shortcuts for toolbar . . . . . . 124. Keyboard shortcuts for tool tips . . . . . 125. Keyboard shortcuts for buttons . . . . . 126. Keyboard shortcuts for check boxes . . . . 127. Keyboard shortcuts for radio buttons 128. Keyboard shortcuts for combination boxes 129. Keyboard shortcuts for lists . . . . . . . 130. Keyboard shortcuts for sliders . . . . . . 131. Keyboard shortcuts for tables . . . . . . 132. Additional keyboard shortcuts for tables in Update Manager . . . . . . . . . . 133. Keyboard shortcuts for trees . . . . . . 134. Keyboard shortcuts for text fields . . . . . 135. Keyboard shortcuts for text panes . . . . . 136. Default installation directories . . . . . . 137. Default LDAP authentication properties for IBM Director Server . . . . . . . . .
238 240 242 246 249 251 254
254
267 284 323 341 341 341 342 342 342 343 343 343 343 344 344 344 344 344 345 345 345 345 345 346 346 347 348 348 349 349 353 355
viii
About this book

This book provides information about installing and configuring IBM Director. In addition to presenting an overview of IBM Director and its requirements, it covers the following topics: v Planning an IBM Director environment v Installing IBM Director and IBM Director extensions v Upgrading from IBM Director 4.2 or earlier to IBM Director 5.20 v Configuring IBM Director It also includes information about IBM Director security and solving problems you might encounter with IBM Director.
Conventions and terminology

These notices are designed to highlight key information: Note: These notices provide important tips, guidance, or advice. Important: These notices provide information or advice that might help you avoid inconvenient or difficult situations. Attention: These notices indicate possible damage to programs, devices, or data. An attention notice appears before the instruction or situation in which damage can occur.
Related information
Besides this documentation, there is additional information related to IBM Director.
IBM Director resources on the World Wide Web

The following Web pages provide resources for understanding, using, and troubleshooting IBM Director and other system-management tools. IBM Director information center publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/diricinfo_5.20/ fqm0_main.html This information center is updated periodically. It contains the most current documentation on a wide range of topics. IBM Director extension information centers These information centers are updated periodically. They contain the most current documentation on a wide range of topics. v Capacity Manager: publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/capman_5.20/ fqn0_main.html v External Application Launch Wizard: publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/ealwiz_5.20/ frj0_main.html
ix
v Hardware Management Console (HMC): publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/hmc_5.20/ frk0_main.html v ServeRAID Manager: publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/serveraid_5.20/ fqy0_main.html v Software Distribution Premium Edition: publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/swdistpe_5.20/ frl0_main.html v System Availability: publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/sysavail_5.20/ fqq0_main.html v z/VM Center: publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/zvmcenter_5.20/ zvm0_main.html IBM Director Web site on ibm.com www.ibm.com/systems/management/director/ The IBM Director Web site on ibm.com has links to downloads and documentation for all currently supported versions of IBM Director. Information on this site includes: v Downloads and documentation for the following IBM Director releases: IBM Director 5.20 Update 1 (5.20.1) IBM Director 5.20 IBM Director 5.10 Update 3 (5.10.3) IBM Director 5.10 Update 2 (5.10.2) IBM Director 5.10 Update 1 (5.10.1) IBM Director 5.10 IBM Director 4.22 IBM Director 4.22 Upward Integration Modules (UIMs) IBM Director 4.21 IBM Director 4.20 v IBM Director Hardware and Software Support Guide document, which lists supported IBM systems and all supported operating systems. It is updated every 6 to 8 weeks. v Printable documentation for IBM Director is available in Portable Document Format (PDF) in several languages. IBM Director Software Developers Kit information center publib.boulder.ibm.com/infocenter/dirinfo/toolkit/index.jsp The IBM Director Software Developers Kit (SDK) information center provides information about the IBM Director SDK, which is a set of tools and documentation to help extend the capabilities of IBM Director by using the APIs and CLIs, creating tasks, and launching tools from the IBM Director user interface. IBM Systems Software information center www.ibm.com/servers/library/infocenter/ This Web page provides information about IBM Director, External Application Launch Wizard, IBM Virtualization Manager, and other topics.
IBM ServerProven page www.ibm.com/servers/eserver/serverproven/compat/us/ This Web page provides information about the hardware compatibility of IBM System x, BladeCenter, and IntelliStation with IBM Director. IBM Servers www.ibm.com/servers/ This Web page on ibm.com links to information, downloads, and IBM Director extensions, such as Remote Deployment Manager, Capacity Manager, Systems Availability and Software Distribution (Premium Edition), for the following IBM products: v IBM BladeCenter v IBM System i v IBM System p v IBM System x v IBM System z IBM forums www.ibm.com/developerworks/forums/dw_esforums.jsp This Web page on ibm.com links to several forums, available as Web pages or using Rich Site Summary (RSS) feeds, in which users can discuss technology issues relating to IBM servers. Three of these forums are of particular interest to IBM Director users: System x IBM Director forum www.ibm.com/developerworks/forums/dw_forum.jsp?forum=759 &cat=53 A forum for discussing any IBM Director topics. This Web page includes a link for obtaining the forum using a Rich Site Summary (RSS) feed. System x Server forum www.ibm.com/developerworks/forums/dw_forum.jsp?forum=740 &cat=53 A forum for discussing System x server topics, including questions related to drivers, firmware, operating systems, clustering, and storage. This Web page includes a link for obtaining the forum using a Rich Site Summary (RSS) feed. IBM Director SDK forum www.ibm.com/developerworks/forums/dw_forum.jsp?forum=849 &cat=53 A forum for discussing the use of the IBM Director Software Developers Kit (SDK) to extend the functionality of IBM Director to meet your specific needs. This Web page includes a link for obtaining the forum using a Rich Site Summary (RSS) feed.
IBM Redbooks publications

www.ibm.com/redbooks/ You can download the following documents from the IBM Redbooks Web page. You can also search this Web page for documents that focus on specific IBM hardware; such documents often contain systems-management material.
About this book
xi
Notes: 1. Be sure to note the date of publication and to determine the level of IBM Director software to which the Redbooks publication refers. 2. You need Adobe Acrobat Reader to view or print these PDF files. You can download a copy from the Adobe Web site at www.adobe.com/products/ acrobat/readstep.html. v Creating a Report of the Tables in the IBM Director 4.1 Database (TIPS0185) v v v v v Implementing IBM Director 5.20 (SG24-6188) Integrating IBM Director with Enterprise Management Solutions (SG24-5388) Managing IBM TotalStorage NAS with IBM Director (SG24-6830) Managing Linux Guests Using IBM Director and z/VM Center (SG24-6830) Monitoring Redundant Uninterruptible Power Supplies Using IBM Director (REDP-3827)
v Using the IBM Director cimsubscribe Utility (REDP-4123-00) v Virtualization on the IBM System x3950 Server (SG24-7190-00) v iSeries Systems Management Handbook (REDP-4070)
Remote Supervisor Adapter

The following Web pages provide resources for understanding and using Remote Supervisor Adapters with IBM Director: Remote Supervisor Adapter overview www.ibm.com/support/docview.wss?uid=psg1MIGR-4UKSML This Web page contains links to the Remote Supervisor Adapter Users Guide and the Remote Supervisor Adapter Installation Guide. Remote Supervisor Adapter II overview www.ibm.com/support/docview.wss?uid=psg1MIGR-50116 This Web page contains information about the Remote Supervisor Adapter II.
Other documents
For planning purposes, the Planning and Installation Guide - IBM BladeCenter (Type 8677) might be of interest.
How to send your comments

Your feedback is important in helping to provide the most accurate and highest quality information. If you have any comments about this book or any other IBM Director publication, v Go to the IBM Director information center Web site at publib.boulder.ibm.com/ infocenter/eserver/v1r2/topic/diricinfo_5.20/fqm0_main.html. There you will find the feedback page where you can enter and submit comments. v Complete one of the forms at the back of any IBM Director book and return it by mail, by fax, or by giving it to an IBM representative.
xii
New in IBM Director

IBM Director provides a number of new features and enhancements since versions 5.10 through 5.10.3. Related information IBM Director 5.10 information IBM Director is an integrated suite of tools that provide you with comprehensive system-management capabilities to maximize system availability and lower IT costs. Its open, industry-standard design supports the management of a variety of hardware and operating systems, including most Intel microprocessor-based systems and certain IBM System i, System p, System x, and System z servers.
New in version 5.20.1

IBM Director 5.20.1 provides a number of new features and enhancements. There are additional supported systems for installation and management. In addition, some functions have changed in this version and some features have been discontinued.
Support for new hardware

For complete hardware support information, see the IBM Director Hardware and Software Support Guide. IBM Director Agent Version 5.20.1 can be installed on the following new IBM systems and products. v IBM System p 570 with POWER6 processors v IBM BladeCenter HT Chassis v IBM System Storage DS3400 IBM Director Version 5.20.1 provides support for the following additional switches: v Cisco 4 Gb 10 port Fibre Channel Switch Module, Part Number 39Y9284 v Cisco 4 Gb 20 port Fibre Channel Switch Module, Part Number 39Y9280 v Nortel 10 Gb Ethernet Switch Module, Part Number 39Y9267 v QLogic 10-port 4 Gb SAN Switch Module for IBM BladeCenter, Part Number 43W6724 v QLogic 20-port 4 Gb SAN Switch Module for IBM BladeCenter, Part Number 43W6725 v QLogic 4 Gb Intelligent Pass-thru Module for IBM BladeCenter, Part Number 43W6723 v QLogic InfiniBand Ethernet Bridge Module, Part Number 39Y9207 v QLogic InfiniBand Fibre Channel Bridge Module, Part Number 39Y9211 IBM Director Version 5.20.1 provides inventory awareness for the following additional devices: v Switch Legacy Interface Module (SLIM) v Concurrent keyboard/video/mouse (cKVM) feature card
xiii
IBM Director support for new operating systems

IBM Director version 5.20.1 can be installed on additional operating system versions as indicated in the following table. For complete operating system support information, see the IBM Director Hardware and Software Support Guide.
Table 1. New operating systems supported by IBM Director Version 5.20 Update 1 IBM Director Console IBM Director Server IBM Director Agent IBM Director Core Services
Operating system
New operating systems supported on System x systems and IBM and third-party x86-based systems: Red Hat Enterprise Linux AS, ES, and WS, version 5.0 SUSE Linux Enterprise Server 9 for x86 (supports Service Pack 3, Update 1 and earlier) Red Hat Enterprise Linux AS, version 4.0, for Intel Itanium (supports Update 5 and earlier) Red Hat Enterprise Linux AS and ES, version 4.0, for AMD64 and EM64T X (supports Update 5 and earlier) Red Hat Enterprise Linux WS, version 4.0, for AMD64 and EM64T (supports Update 5 and earlier) SUSE Linux Enterprise Server 9 for AMD64 and EM64T (supports Service X Pack 3 Update 1 and earlier) Microsoft Virtual Server 2005 (Release 2 required; SP1 supported) New operating systems supported on System i and System p products: AIX 5L, Version 5.2 (supports TL06 or later) Note: Level-0 support includes only Discovery, Remote Session and a limited subset of the Software Distribution task. AIX 5L, Version 5.3 (supports TL03 or later) Note: Level-0 support includes only Discovery, Remote Session and a limited subset of the Software Distribution task. X X X X X X X X X X X X X X X X X X X X X
Red Hat Enterprise Linux AS, versions 4.3, 4.4, and 4.5, for IBM POWER X Red Hat Enterprise Linux AS, version 5.0, for IBM POWER SUSE Linux Enterprise Server 9 for IBM POWER (Service Pack 3 required) New operating systems supported on System z systems: Red Hat Enterprise Linux AS, version 4.0, for IBM System z (supports Update 5 and earlier) Red Hat Enterprise Linux AS, version 5.0, for IBM System z SUSE Linux Enterprise Server 9 for IBM System z (supports Service Pack 3 and earlier) X X X
X X
X X
Updated database support

IBM Director Server supports the following newer versions of external databases: v Apache Derby V10.2 (embedded with IBM Director Server 5.10 Update 1) v IBM DB2 Universal Database version 9.1 with Fix Pack 2 version 8.2 with Fix Pack 7 version 8.1 with Fix Pack 14
xiv
For complete information about database support in IBM Director 5.20 Update 1, see the Supported database applications topic in the information center. In addition, new versions of the Oracle Java Database Connectivity (JDBC) drivers are supported. For additional information, see the Preparing the Oracle Server database topic in the information center.
Additional changes in version 5.20.1

Added Rack Manager support for BladeCenter T chassis, machine type 8730 Added support for the Asset ID task on Level-2 managed systems running AIX Additional operating system supported for IBM Director UIM for HP OpenView IBM Director UIM for HP OpenView now supports Level-2 managed systems running AIX. IBM Director-based events and information can be received by a management server running HP OpenView. Improvements to the Hardware Management Console extension for IBM Director Version 5.20.1 of Hardware Management Console extension for IBM Director is updated to start the web based HMC version 7 console alternatively to the earlier version of the HMC console. Depending on the version of the Hardware Management Console managed object, the Hardware Management Console task in IBM Director will start either the web based HMC version 7 console or the earlier version of the HMC console. Documentation updates The online help files for IBM Director Version 5.20 Update 1 are not changed from Version 5.20. For IBM Director Version 5.20 Update 1, documentation updates are available in the IBM Director Information Center at publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/ diricinfo_5.20/fqm0_main.html. The IBM Director Information Center includes updates to both the printed and online documentation.
New in version 5.20

IBM Director 5.20 provides a number of new features and enhancements. There are additional supported systems for installation and management. In addition, some functions have changed in this version and some features have been discontinued.
Improvements to the installation procedure for IBM Director

Express installation IBM Director Express is a simplified installation that installs IBM Director using default values for a number of installation options, and filtering the task list to start with a core set of essential tasks. Users also can add other tasks after installation. Installation checking for required drivers On System x servers, the installation program for IBM Director Agent automatically checks for required drivers needed for system management and informs the user if drivers are missing. i5/OS On systems running i5/OS, IBM Director components can be installed separately from Virtualization Engine products by using the RSTLICPGM.
New in IBM Director
xv
Collection Services installed on AIX, Linux on POWER, and i5/OS Collection Services is an i5/OS application that collects interval data at the system and job levels of systems in your environment. The framework that is used to collect this data is automatically installed when you install IBM Director on AIX, Linux on POWER, or i5/OS. When installed with IBM Director, Collection Services provides a cross-partition view of processor user. For information about using Collection Services, go to http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzahx/ rzahxcollectdatapart.htm.
Improvements to the way you work in IBM Director

Update management The Update Manager task provides integrated management of updates for managed systems, including new tasks for creating profiles, downloading updates, comparing updates defined in profiles against systems, and generating reports. Enhancements to the upward integration module for Tivoli Management Framework In IBM Director version 5.20, the Software Distribution feature can be used to distribute software and perform an unattended installation of these packages on any Tivoli endpoint that is running Linux or Microsoft Windows. User administration improvements IBM Director 5.20 includes the following changes affecting user administration: v User accounts can be defined on an Lightweight Directory Access Protocol (LDAP) server, which you can use to centralize user administration for multiple management servers. v Global or domain-local user groups can be hierarchical, with user groups including other user groups. v User authorization for tasks is more precise, with separate authorization for parent and child tasks. v Several new dircli commands support command-line implementation of user and group authorization tasks. Inventory improvements IBM Director 5.20 adds a new dircli command to list inventory, and expands the capabilities of the dircli mkgp command, which you can use to create dynamic groups from the command line. In addition, inventory collection now collects firmware information for more devices, including hard disk drives, Small Computer System Interface (SCSI) tape drives, network interface controller (NIC) adapters, and Remote Supervisor Adapter (RSA) video BIOS for many Level-0, Level-1, and Level-2 managed systems. For AIX systems, IBM Director 5.20 provides added inventory support for adapters (FC and RAID), devices (IDE, PCI and SCSI), memory modules, and disk storage (ISCSI, RAID, SSA, FC, virtual disks). Monitoring of i5/OS message queues IBM Director 5.20 provides support for monitoring i5/OS message queues for specific message IDs without requiring that the message first be displayed on the IBM Director Console. With IBM Director version 5.20, a
xvi
message ID can be monitored by entering the message ID into the Event Text field of a Simple Event Filter for the applicable message queue. Support for high availability environments When IBM Director 5.20 is run in conjunction with a high-availability system, such as IBM Tivoli System Automation for Multiplatforms or SteelEyes LifeKeeper, it can be run in a high availability configuration with which IBM Director Server operations can be performed by a redundant IBM Director Server instance in the event of a failure on a management server. IBM Virtualization Manager extension With the IBM Virtualization Manager extension, IBM Director 5.20 provides a single point of management for both physical and virtual systems in a consistent way across different virtualization technologies. This support includes a Web-based user interface; a dashboard health summary; and a graphical topology with which you can visualize and navigate relationships between virtual and physical resources, and perform simplified virtualization tasks such as creating, deleting, modifying, and relocating virtual servers.
Security enhancement
IBM Director version 5.20 improves security for some managed systems through Intelligent Platform Management (IPMI) 2.0 support. IBM Director version 5.20 includes support for IPMI 2.0 communication using Enhanced Remote Management Control Protocol (RMCP+) on the following managed systems: v IBM System x3455 v v v v IBM IBM IBM IBM System System System System x3655 x3755 x3200 x3250
IBM Director Agent support for new hardware

IBM Director Agent version 5.20 can be installed on the following new IBM systems and products. IntelliStation M Pro, machine type 9229 IBM System x3nnn servers v x3105, machine types 4347 and 4348 (Environmental-sensor monitoring and hardware events are not supported.) v x3200, machine types 4362 and 4363 v x3250, machine types 4364 and 4365 v x3455, machine types 7984 and 7986 v x3655, machine type 7985 v x3755, machine type 8877
Discontinued features in version 5.20

Alert Standard Format Support for Alert Standard Format is not continued in version 5.20. When IBM Director Agent is updated to version 5.20, this function will be removed. You can continue to use existing version 5.10 installations of IBM Director Agent if this function is needed.
New in IBM Director
xvii
Web-based Access Support for Web-based Access is not continued in version 5.20. When IBM Director Agent is updated to version 5.20, this function will be removed. You can continue to use existing version 5.10 installations of IBM Director Agent if this function is needed.
xviii
Chapter 1. Getting started with IBM Director

This topic contains general and conceptual information about IBM Director.
Introducing IBM Director

This topic provides an overview of IBM Director. IBM Director is an integrated suite of tools that provide you with comprehensive system-management capabilities to maximize system availability and lower IT costs. Its open, industry-standard design supports the management of a variety of hardware and operating systems, including most Intel microprocessor-based systems and certain IBM System i, System p, System x, and System z servers. IBM Director automates many of the processes that are required to manage systems proactively, including capacity planning, asset tracking, preventive maintenance, diagnostic monitoring, troubleshooting, and more. It has a graphical user interface that provides easy access to both local and remote systems. IBM Director can be used in environments with multiple operating systems and integrated with robust workgroup and enterprise management software from IBM (such as Tivoli software), Computer Associates, Hewlett-Packard, Microsoft, NetIQ, and BMC Software.
IBM Director environment

IBM Director is designed to manage a complex environment that contains numerous servers, desktop computers, workstations, mobile computers (notebook computers), and assorted devices. IBM Director can manage up to 5000 Level-2 systems. An IBM Director environment contains the following groups of hardware: v One or more servers on which IBM Director Server is installed. Such servers are called management servers. v Servers, workstations, desktop computers, and mobile computers that are managed by IBM Director. Such systems are called managed systems. v Network devices, printers, or computers that have Simple Network Management Protocol (SNMP) agents installed or embedded. Such devices are called SNMP devices. v Additional managed objects such as platforms and chassis. Collectively, all managed systems, devices, and objects are referred to as managed objects. Figure 1 on page 2 shows the hardware in an IBM Director environment.
Figure 1. Hardware in an IBM Director environment
IBM Director components

This topic provides information about the IBM Director components. The IBM Director software has four components: v IBM Director Core Services v IBM Director Agent v IBM Director Console v IBM Director Server IBM Director may also manage some systems on which no component of IBM Director is installed. Such managed systems are referred to as Level-0 managed systems. These systems must at a minimum support either the Secure Shell (SSH) or Distributed Component Object Model (DCOM) protocol. Note: When you install IBM Director Server on Microsoft Windows or Linux, IBM Director Agent and IBM Director Console are installed automatically also. When you install IBM Director Server on IBM i5/OS, IBM Director Agent is installed automatically also. Figure 2 on page 3 shows where the IBM Director software components are installed in a basic IBM Director environment.
Figure 2. Software in an IBM Director environment
IBM Director Core Services

IBM Director Core Services is installed on a managed system to provide hardware-specific (Level-1) functionality for IBM Director to communicate with and administer the managed system. IBM Director Core Services provides a subset of IBM Director Agent functionality that is used to communicate with and administer the managed system. Systems (IBM servers, desktop computers, workstations, and mobile computers) that have IBM Director Core Services (but not IBM Director Agent) installed on them are referred to as Level-1 managed systems. IBM Director Core Services provides management entirely through standard protocols. This includes discovery, authentication, and management. The IBM Director Core Services package installs an SLP service agent, an SSL-enabled CIMOM (on Linux) or CIM mapping libraries to WMI (on Windows), an optional ssh server, and platform-specific instrumentation. You can perform the following tasks on a Level-1 managed system:
v Collect inventory. v Promote to Level-2 management by distributing the IBM Director Agent package. v Manage events using event action plans, event subscription, and the event log. v v v v v Monitor hardware status. Reboot or shut down the managed system. Run command-line programs. Distribute system update packages through Software Distribution Remote Session (requires ssh)
IBM Director Agent

IBM Director Agent is installed on a managed system to provide enhanced (Level 2) functionality with which IBM Director can communicate with and administer the managed system. IBM Director Agent provides management data to IBM Director Server. Data can be transferred using several network protocols, including Transmission Control Protocol/Internet Protocol (TCP/IP), Network Basic Input/Output System (NetBIOS), and Internetwork Package Exchange (IPX). IBM Director Server can communicate with all systems in your network that have IBM Director Agent installed. IBM Director Agent features vary according to the operating system on which IBM Director Agent is installed. For example, you can install Microsoft Cluster Browser only on Windows 32-bit operating systems. All IBM Intel-compatible servers, IBM BladeCenter JS20 and JS21 blade servers, NetVista desktop computers, ThinkCentre desktop computers,IBM PC desktop computers, IBM IntelliStation workstations, IBM ThinkPad mobile computers, IBM System Storage Network Attached Storage (NAS) products, and IBM SurePOS point-of-sale systems include a license for IBM Director Agent. You can purchase additional licenses for non-IBM systems. IBM Director Agent is supported on systems that are running the following operating systems: v Microsoft Windows v Linux (System x, POWER, System z) v IBM AIX v IBM i5/OS v Novell NetWare Systems (IBM or non-IBM servers, desktop computers, workstations, and mobile computers) that have IBM Director Agent installed on them are referred to as Level-2 managed systems. The function of IBM Director Agent on the managed system will vary depending on the operating system and platform.
IBM Director Console

IBM Director Console is installed on a desktop computer, workstation, or mobile computer to provide a GUI in which the system administrator can perform tasks in IBM Director.
IBM Director Console is the GUI for IBM Director Server. Data is transferred between IBM Director Console and IBM Director Server through TCP/IP. Using IBM Director Console, you can conduct comprehensive systems management using either a drop-and-drag action or a single click. You may install IBM Director Console on as many systems as needed. IBM Director includes an unlimited-use license for IBM Director Console. The system on which IBM Director Console is installed is referred to as a management console. Note: When you install IBM Director Console on a system, IBM Director Agent is not installed automatically. To provide full management of the management console through IBM Director, IBM Director Agent should also be installed.
IBM Director Server

IBM Director Server must be installed on the management server, and provides all the management function of IBM Director. IBM Director Server is the main component of IBM Director; it contains the management data, the server engine, and the application logic. IBM Director Server provides basic functions such as discovery of managed objects, persistent storage of configuration and management data, an inventory database, event listening, security and authentication, management console support, and administrative tasks. IBM Director Server stores the inventory data in a Structured Query Language (SQL) database. You can access information that is stored in this relational database even when the managed objects are not available. Every IBM System x server and IBM BladeCenter unit includes an IBM Director Server license. You can purchase additional IBM Director Server licenses for installation on non-IBM servers. IBM Director Server communicates with managed objects and SNMP devices to receive information and issue commands. If IBM Director Console is used, IBM Director Server communicates with IBM Director Console to display network status information and receive instructions from the system administrator.
Concepts
This section discusses concepts that will help you understand how IBM Director works. Becoming familiar with the IBM Director components and understanding the concepts in this section enables you to use IBM Director most effectively.
Accessibility
This topic describes the accessibility features in IBM Director and the IBM Director extensions. IBM strives to provide products with usable access for everyone, regardless of age or ability.
Associations
Associations change the organization of a group of managed objects that is displayed in the Group Contents pane.
You can apply an association type to the group that is currently displayed in the Group Contents pane. When you apply an association, the association persists the next time you display that group. If the group that is currently displayed in the Group Contents pane contains managed objects that do not apply to the selected association, those objects are displayed in blue type under the Not Associated node. You also can display additional information about the managed objects that are displayed in the Group Contents pane by selecting one or more association options from the bottom half of the Associations menu. For example, you can view managed objects to which event action plans have been applied. If a managed object has an event action plan applied to it, the managed object is displayed as a tree structure that you can expand to view which event action plans have been applied to the object.
Association type
Associations change the organization of a group of managed objects that is displayed in the Group Contents pane. The following associations are available: None System Membership Shows the relationship between Level-0, Level-1, and Level-2 managed systems and logical and physical platforms, with systems the top level and the associated platforms as child nodes. This is the default association for the All Managed Objects group. Object Type Shows the managed objects based on object type (such as managed systems, SNMP devices, and chassis). TCP/IP Addresses Shows the managed objects based on TCP/IP address. TCP/IP Host Names Shows the managed objects based on TCP/IP host names. IPX Network IDs Shows the managed objects based on network IDs. Domains/Workgroups Shows the managed objects based on domains and workgroups. Chassis Membership Shows all the blade servers in a BladeCenter chassis. This is the default association for the Chassis and Chassis Members group. Cluster Membership This is the default association for the Clusters and Cluster Members group. Physical PlatformRemote I/O Enclosures Shows the managed objects based on remote input/output (I/O) enclosures. Platform Membership Shows the relationship between managed systems and platforms, with platforms the top level and the associated systems as child nodes. This association is useful if you have a single system that represents multiple managed objects. Depending on the IBM Director task you want to
perform, the managed object that you target might differ. This is the default association for the Platforms and Platform Members group. Rack Membership Shows all the managed objects in a rack. This is the default association for the Racks with Members group. Scalable Partitions Membership This is the default association for the Scalable Partitions group. Scalable Systems Membership This is the default association for the Scalable Systems and Members group. TCP/IP Routers/DNS Shows the managed objects based on TCP/IP routers or domain name space (DNS). Status Shows the managed objects based on status. SNMP System Object ID Shows the managed objects based on SNMP system object ID. HMC Membership This is the default association for the HMC and HMC Members group. z/VM Server Complexes Membership Shows all z/VM systems with their server complexes, with included Linux guest systems. At the top level, the association shows the z/VM systems. Under each z/VM system, it shows the server complexes. Under each server complex, the association shows the tiers in that server complex. Under each tier, the association shows the Linux guest systems in that tier. The association also includes a Free systems node (at the second level) for Linux guest systems in the z/VM system that are not in any server complex. Linux on System z Platform Membership Shows all discovered Level-0, Level-1, and Level-2 managed Linux systems that run on a System z9 or zSeries mainframe. The association tree shows which Linux systems run natively in a logical partition (LPAR) and which of the other Linux systems run under which z/VM system. Linux systems that run under z/VM but cannot be associated with a z/VM system are grouped accordingly. The association also shows z/VM manageability access points. A z/VM manageability access point is a Linux system that has been set up to enable the z/VM Center task for a particular z/VM system. In the association tree, z/VM manageability access points are displayed twice, as a Linux system under a z/VM system and as the z/VM manageability access point for that z/VM system. Systems that are not below the LPAR or z/VM subtrees cannot be associated with an LPAR or a z/VM system, possibly because they are not Linux on System z9 and zSeries systems or because they are locked. Servers with Fibre Channel Attached SMI-S Storage Shows the servers that are connected to SMI-S storage devices through a Fibre Channel switch. Tips:
v This association shows only active connections through storage attached networks (SANs). It does not shows specific connectivity through switches and direct connections without switches. v Switches and disk arrays must be discovered as SMI-S objects. v Inventory must be completed on the storage devices and servers. SMI-S Storage with Fibre Channel Attached Servers Shows the SMI-S storage devices that are connected to servers through a Fibre Channel switch. Tips: v This association shows only active connections through storage attached networks (SANs). It does not shows specific connectivity through switches and direct connections without switches. v Switches and disk arrays must be discovered as SMI-S objects. v Inventory must be completed on the storage devices and servers.
Default associations
Associations change the organization of a group of managed objects that is displayed in the Group Contents pane. The None association is the default association for most groups. This table shows the groups that have default associations other than None.
Table 2. Default associations other than None Group All Managed Objects Chassis and Chassis Members Clusters and Cluster Members HMC and HMC Members Platforms and Platform Members Racks with Members Scalable Partition Scalable Systems and Members Default association System Membership Chassis Membership Cluster Membership HMC Membership Platform Membership Rack Membership Scalable Partitions Membership Scalable Systems Membership
Association options
Select association options to display additional information about the managed objects that are displayed in the Group Contents pane. The following association options are available: Software Packages Shows which software packages, if any, have been delivered to the managed objects in the group using the Software Distribution task. Jobs Shows all tasks, if any, that are scheduled to be run against the managed objects in the group.
Activations Shows all tasks, if any, that have already been run against each managed object in the group. Resource Monitors Shows the resource monitors, if any, that have been applied to the managed objects in the group.
Event Action Plans Shows the event action plans, if any, that have been applied to the managed objects in the group.
Common Information Model

The Common Information Model (CIM) is a language-independent programming model that defines the properties, operations, and relationships of objects in enterprise and Internet environments. Using the CIM, IBM Director has a single model for communicating with these different resources. IBM Director uses the CIM to access data on Level-1 and Level-2 managed systems. The CIM and Web Based Enterprise Management (WBEM) are standards that are developed by a consortium of major hardware and software vendors (including IBM) called the Distributed Management Task Force (DMTF). The CIM provides the framework by which a system can be managed by using common building blocks rather than proprietary software. If a device is CIM-compliant, software that is also CIM-compliant, such as IBM Director, can manage that device. The infrastructure used by IBM Director for CIM instrumentation consists of the following components: 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 to talk to CIM Object Managers and Agents. CIM Managed Object A CIM Managed Object is a hardware or software component that can be managed by a management application by using CIM. When Level 2: IBM Director Agent or Level 1: Core Services is installed on a system, the applicable CIM software is installed and that system becomes a CIM Managed Object. CIM Object Manager The CIM Object Manager (CIMOM), also known as a CIM server, is the software entity that receives, validates, and authenticates the CIM requests from the CIM Client. It then directs the requests to the appropriate component or device provider. IBM Director locates the CIMOM through discovery. When Level 1: Core Services is installed on a system, the CIMOM registers itself to the SLP and supplies its location, IP address, port number, and the type of service that it provides (management.software.IBM:director-agent). When IBM Director performs an SLP discovery, the IBM Director SLP service is identified and the system running that service is displayed as a Level-1 managed system. With this information, IBM Director can directly communicate with the CIMOM. Director discovers the CIMOM on Level-2 managed system using a proprietary protocol. Using CIM as the framework, IBM Director can perform tasks on the managed system. As requests arrive, the CIMOM validates and authenticates each request. It then directs the requests to the appropriate functional component of the CIMOM or to a device provider. The provider makes calls to a device-unique programming interface on behalf of the CIMOM to satisfy the IBM Director requests.
Shortcuts to CIM classes and methods

By creating shortcuts, or subtasks, you can bypass navigating through the class tree to reach a specific class or method. You can define two types of shortcuts: v A user-selected class that displays the instances, properties, and methods that are associated with a specified class on the selected managed system. v A user-selected method that runs on the selected managed system.
Default CIM subscriptions for IBM Director Agent and IBM Director Core Services
The Level-1 and Level-2 managed system event architecture is governed by the WBEM suite of standards as implemented by the Pegasus CIM Object Manager version 2.5.1. This event architecture includes indication providers, indication handlers, and a set of CIM indication subscriptions that binds the two together. Indication providers Software modules managed by the CIMOM that monitor a resource in a computer system and send CIM indications when some threshold has been exceeded for that resource. Indication handlers Software modules that listen for CIM indications and then export these indications to logs or other event formats. Indication subscriptions These are instances of three CIM classes: CIM_IndicationFilter, CIM_IndicationHandlerCIMXML, and CIM_IndicationSubscription. These classes create a binding between a CIM indication and an indication handler. No indications are forwarded by the CIMOM unless there is an interested handler as denoted by the set of indication subscriptions managed by the CIMOM. IBM Director Agent and IBM Director Core Services also install an additional Windows Service or Linux daemon, as applicable, called CIMListener. This process listens for subscribed CIM indications and delivers them to the proper indication handler. The installation also creates a default set of subscriptions between the handlers and the indications.
CIM indication handler IBM Director events (CIM > System events) Default subscriptions All indications of all severities after the managed system is discovered and unlocked by a management server. All indications of all severities. Exceptions are no subscription for Lease Expiration, Warranty Expiration, Service Processor Events, Automatic Server Restart Events, and IPMI Log Events. All indications of all severities. Exceptions are Network Adapter Offline and Network Adapter Online. All indications of all severities. Exceptions are Network Adapter Offline and Network Adapter Online. None
Hardware Status task (also the IBM Director Console Group Contents pane)
Linux syslog events
Microsoft Windows Event Log (event log event ID) Local message window
10
CIM indication handler
Default subscriptions
Microsoft System Management Server (SMS) All indications of all severities. Exceptions are Network Adapter Offline and Network Adapter Online. SNMP (Tivoli NetView, HP OpenView, CA Unicenter, Tivoli Enterprise Console) Microsoft Operations Manager 2005 (alerts) Tivoli Enterprise Console (native events) All indications of all severities. Exceptions are Network Adapter Offline and Network Adapter Online. All indications of all severities. All indications of all severities. Exceptions are Network Adapter Offline and Network Adapter Online.
Additional reference information is available for IBM Director Core Services default subscriptions, for CIM indications, and for the cimsubscribe command used to modify subscriptions.
Discovery
Discovery is the process by which IBM Director Server identifies and establishes connections with objects, such as systems or devices, that IBM Director can manage. Before IBM Director can manage a system or device, that managed object must be discovered by IBM Director Server. After a managed object has been discovered, an icon that represents the object is displayed in the IBM Director Console window when the applicable group is selected. The management server also stores the addresses of discovered managed objects in the IBM Director database. Depending on the complexity of your network and the needs of your organization, you will need to configure the discovery process. You will need detailed information about the layout of your network, specifically the subnet, port, and LAN information. The base-management server includes support for the following manageable entities or managed objects: v System endpoint v Storage devices that are optimized to support the SMI-S CIM standard for storage devices v Physical or logical platforms (for example a physical machine or hypervisor) that can host an operating system v SNMP (or generic) devices v Base clusters v Hypervisor services objects, such as the IBM System z z/VM managed object that can provision Linux systems in form of z/VM virtual servers. v Hardware Control Points, such as the IBM BladeCenter chassis or the Power HMC, which are the management gateway to other physical platform objects v 5.20 and later: Integrated Virtualization Manager (IVM) The type of discovery method that IBM Director uses to connect with managed objects varies based on the type of device being discovered and the type of network protocols used by that device.
11
Agent-initiated discovery
In IBM Director, agent-initiated discovery occurs when managed systems contact IBM Director Server rather than IBM Director Server searching for managed systems. When IBM Director Server is configured to permit agent-initiated discovery, this implementation has two advantages: v An agent-initiated discovery will always succeed as long as there is a TCP/IP connection from the management server to the managed systems. v The network traffic resulting from discovery requests will be negligible compared to a server-initiated discovery. Agent-initiated discovery can be performed only by Level-2 managed systems or SNMP devices. IBM Director Server must be configured to permit agent-initiated discovery for these managed-object types. The three typical agent-initiated discovery procedures are: v Performing an installation of IBM Director Agent on a Level-2 managed system and specifying the address for IBM Director Server in the Add known server field or response-file parameter. After IBM Director Agent is installed, it attempts to contact IBM Director Server. v Using the genevent command from the command line or a batch file to send an event to the management server with the managed systems name and IP address. v Sending an SNMP trap from the SNMP device to IBM Director Server.
Server-initiated discovery
In IBM Director, server-initiated discovery occurs when IBM Director Server searches the network for Level-0, Level-1, and Level-2 managed systems. Server-initiated discovery typically is referred to simply as discovery. The advantage of this type of discovery is ease of configuration; you set the discovery settings once at the management server. IBM Director offers several ways to perform server-initiated discovery: v Broadcast discovery v Multicast discovery v Broadcast relay discovery v Unicast discovery v Service Location Protocol (SLP) discovery Broadcast discovery is the default discovery method. From IBM Director Console, you can change the discovery preferences for the management server according to your business needs and network requirements. Broadcast discovery: When you use broadcast discovery, the management server attempts to discover manageable objects on the network by transmitting a single request to the entire subnetwork on which the management server is located. During a broadcast discovery, IBM Director Server sends out a broadcast request to all the IP addresses that are in a specified subnet. Typically, the subnet is one where the management server is installed. By default, most gateways do not permit broadcasts to pass over subnets, but you can also send a broadcast to other subnets if broadcasts are not filtered by your network infrastructure.
12
IBM Director Server broadcasts requests using each protocol supported by IBM Director (for example, SNMP, SSH, DCOM, SLP, and IPC). You also can use broadcast discovery on other subnets if your network gateway is configured to permit broadcast messages. Your network might be configured to allow broadcast messages within a subnet, but prevent them from passing over to other subnets. The IP addresses that successfully respond to the broadcast request are saved in IBM Director along with the applicable protocol information. IBM Director Console displays the objects that respond to the broadcast discovery and that support one or more of the protocols that IBM Director uses. Note: By default, Level-0 managed systems are not discovered using broadcast discovery. Level-0 managed systems are discovered using unicast discovery, and an IP address range must be specified for the unicast. Attention: Broadcast discovery consumes network resources. If IBM Director is configured to perform broadcast discoveries frequently, your network resources might be inefficiently used. Contact your network administrator to determine the best discovery method for your organization. Multicast discovery: In multicast discovery, the management server sends a request to a specified IP address, which is called the multicast group. The multicast group that is used by IBM Director Server by default is 224.0.1.118. Multicast discovery is used to identify Level-1 and Level-2 managed systems. This discovery method is useful on networks that are configured to filter broadcast requests but not multicast requests. One of the attributes of a multicast request is the maximum time-to-live (TTL), which is the number of times a request is passed between subnets. After the TTL expires, the packet is discarded. Note: You can use multicast discovery to identify systems across multiple subnets without configuring specific network information for each subnet. However, some networks are configured to prevent multicast requests from passing between subnets. Contact your network administrator to determine the best discovery method for your organization. Broadcast relay discovery: In broadcast relay discovery, the management server sends a discovery request message to a specific Level-2 managed system, instructing the managed system to perform a discovery on the local subnet using a general broadcast. To perform the broadcast relay discovery, the system that performs the general broadcast must have already been discovered by IBM Director. Broadcast relay discovery is used to identify Level-2 managed systems. This discovery method is useful when the management server and the managed systems belong to different subnets and the network is configured to filter broadcast requests across those subnets. Note: Although it is not a requirement, the Level-2 managed system that performs the general broadcast discovery is typically on a different subnet from the management server.
13
When managed systems on the same subnet as the Level-2 managed system receive the discovery request, they reply directly to the management server that made the original request. This type of discovery generates less network traffic than a unicast discovery and avoids many of the problems associated with broadcast discovery when the network is configured to filter or prevent broadcasts. You might want to consider broadcast relay discovery if you have multiple physical locations in which managed systems reside, with lower-bandwidth network infrastructure (such as T1 or frame relay) between these physical sites. Unicast discovery: In unicast discovery, the management server sends requests directly to an exact IP address or a range of IP addresses. Each address that you specify is contacted individually. Unicast discovery is used to discover Level-0, Level-1, and Level-2 managed systems. You can use this discovery method if your network filters both broadcast and multicast requests. The disadvantage of a unicast discovery is that an IP packet must be sent for each individual IP address, which increases network traffic. Service Location Protocol discovery: Service Location Protocol (SLP) is an open-source Internet-standards track protocol that allows network applications, such as IBM Director, to discover the location and configuration of network services in a network. In SLP discovery, the management server sends a request message for the IBM Director Agent SLP service type. An SLP Service Agent that replies to the request is identified in IBM Director Console as a Level-1 managed system. In an SLP implementation, an agent is a software entity that processes SLP protocol messages. There are three types of SLP agents: User Agent (UA) The SLP User Agent is a software entity that is looking for the location of one or more services. In an IBM Director environment, IBM Director Server acts as the user agent when it performs an SLP discovery. Service Agent (SA) The SLP Service Agent is a software entity that advertises the location of one or more services. In an IBM Director environment, Level 1: Core Services acts as the service agent. These Level-1 managed systems can advertise through the use of multicast messages and unicast responses to queries. Directory Agent (DA) The SLP Directory Agent is a software entity that acts as a centralized repository for service location information. If your network administrator has configured a directory agent, you can configure IBM Director to use the directory agent to discover service agents. When you install Level 1: IBM Director Core Services on a system, SLP and the IBM Director Agent SLP service type (management.software.IBM:director-agent) are installed on that system. Common Information Model (CIM) also is installed with Level 1: IBM Director Core Services.
14
SLP discovery is used to identify only Level-1 managed systems. You can configure IBM Director to send an SLP discovery request as a unicast, multicast, or broadcast message. Some older versions of service agents do not support multicasting and might have to be discovered by using a broadcast.
Manual discovery
In IBM Director, manual discovery occurs when a user instructs IBM Director Server to add a specific managed object. Manual discovery can be performed in IBM Director Console or from the command line. During manual discovery, IBM Director Server attempts to contact the managed object using the protocol defined for the managed-object type and the information provided by the user. If IBM Director Server successfully contacts the managed object, the object is added for management and is displayed in IBM Director Console. When IBM Director Server attempts to add a managed system, it uses the following procedure to contact the managed system and determine the type of management that is supported: 1. Check for the Level-2 protocol (ports 14247 on Windows, 14248 on Linux). 2. If the system does not respond, check for the Level-1 protocol (SLP port 427). 3. If the system still does not respond, check for the Level-0 protocols (ssh port 22 or Windows RPC ports 137-139, 145). After IBM Director Server determines the system type, it creates a managed object. If none are detected, an error is reported.
Names of discovered managed objects in IBM Director

When IBM Director Server adds a new managed object, it assigns the managed object a name based on information received from the managed object, IBM Director Server configuration settings, user input, or a combination of these three sources of information. How the managed object is named depends on the type of managed object. Note: You can rename managed objects in IBM Director Console after they have been added. The display name for the managed object in IBM Director Console can be changed independently from the name which is defined on the managed object itself. BladeCenter chassis, physical platforms, SMI-S storage devices When these managed objects are discovered, they are named according to the naming-convention template specified in the Discovery Preferences window. Hardware management consoles, Level-0 managed systems, Level-1 managed systems, SNMP devices, z/VM centers IBM Director Server uses the name returned by the managed object. Level-2 managed systems (Linux) IBM Director Server uses the host name as returned by the managed system. Level-2 managed systems (Windows) IBM Director Server uses the name specified in the Network Driver Configuration on the managed system. By default, this is set to the uppercase computer name.
15
Event management
An event is an occurrence of significance to a task, system, or managed object, such as the completion or failure of an operation. In a system-management environment, IBM Director Server receives events, traps, and notifications from many sources. These sources include, but are not limited to, the following programs and protocols: v IBM Director native events generated by IBM Director Agent v CIM indications from the CIMOM that is installed as part of IBM Director Agent and IBM Director Core Services v Microsoft Windows event log v Windows Management Instrumentation (WMI) v SNMP traps through out-of-band communication v Platform Event Traps (PET) through out-of-band communication from Alert Standard Format (ASF)-capable systems and Intelligent Platform Management Interface (IPMI)- capable systems v IBM service processors notifications through out-of-band communication When IBM Director Server receives these events or notifications, it converts them into IBM Director events. For example, when IBM Director Server receives a CIM indication, it converts the CIM indication into an IBM Director event of the type CIM. When you view the Event Filter Builder tree, the CIM events are displayed under the CIM node in the tree. Note: IBM Director can convert CIM indications into other event types, including event types that are used by enterprise-level system-management programs, such as SNMP events. Using these event types, IBM Director can provide system data to the enterprise-level system-management programs through the IBM Director Upward Integration Modules. For more information, see CIM indications in IBM Director in the IBM Director Events Reference. However, these SNMP events are not the same as SNMP traps that IBM Director Server receives out-of-band (that is, not through IBM Director Agent or IBM Director Core Services). Out-of-band SNMP traps are generated by hardware products and other software programs. They are displayed under the SNMP node in the Event Filter Builder tree, but beneath a different subnode. You can use the events in the Event Filter Builder tree when working with managed objects. To monitor one or more events, you must create an event filter that contains an event type from one of these sources, use the event filter as part of an event-action plan, and then apply the event-action plan to a managed object. Events from the Windows event log are displayed in the Windows event log tree in the Event Type Filter Builder. Events from WMI are displayed in the Common Information Model (CIM) tree.
Alerts and resolutions

In IBM Director, an event can be in one of the following categories: alert and resolution. Typically, an alert is the occurrence of a problem relating to a managed object. A resolution is the occurrence of a correction or solution to a problem.
16
Note: In the IBM Director product, there are tasks and features that use the word alert in place of the word event. Also, ServeRAID Manager uses the word notification instead of event.
Monitoring operating-system specific events

If you want to monitor Windows- or i5/OS-specific events in the IBM Director environment, you must create an event-action plan in order for IBM Director to process these events. The predefined active event-action plan in IBM Director, Log All Events, does not monitor these operating-system specific events. Managed objects running Windows or i5/OS can generate the following operating-specific events.
Window-specific event types v Windows event log v Optional: A subset of the following CIM events: Windows event log Windows services Windows registry i5/OS specific event types v Msgq
Even though these events are generated by their respective operating systems (or an optional layer that is installed on the operating system), IBM Director does not process these events unless you create an event-action plan to do so. When you install IBM Director, it has one predefined active event-action plan: Log All Events. However, this event-action plan does not log these Windows- or i5/OS-specific events. You must create an event-action plan with a simple-event filter that contains the event types for one or more of these events. Then, you must apply this event-action plan to the managed object running Windows or i5/OS. When IBM Director Agent starts on a managed object running Windows, the twgescli.exe program starts, too. This program listens for IBM Director Server to send a message to IBM Director Agent that an event-action plan has been applied to that managed object. If the event-action plan includes a simple-event filter that contains the event types for any of the Windows-specific events, IBM Director appropriates these events for its own use. This is called event subscription. The twgescli.exe program subscribes to the event types that are specified in the event-action plan and translates the Windows-specific events into an IBM Director event type. Then, the program forwards the events to the management server from which the event-action plan was applied. When IBM Director Agent starts on a managed object running i5/OS, the process is the same with comparable code to twgescli.exe that is included in IBM Director Agent for i5/OS.
Processing an event in IBM Director

Understanding how IBM Director processes an event can help you build and troubleshoot event-action plans. IBM Director completes the following steps to determine which event actions to perform: 1. The managed object generates an event and forwards the event to all the management servers that have discovered the managed object (except for some events, such as those that are generated through meeting or exceeding a resource-monitor threshold, which are sent only to the management server where the thresholds are configured and applied).
17
2. IBM Director Server processes the event and determines which managed object generated the event and which group or groups the managed object belongs to. 3. IBM Director Server determines whether any event-action plans are applied to the managed object or to any of the groups of which the managed object is a member. 4. If an event-action plan has been applied, IBM Director Server determines whether any event filters match the event that was generated. 5. The management server performs any event actions for each matching event filter.
Event-action plans
When you create an event-action plan, you attach one or more event actions to a specified event filter. Then, you include one or more event filters in the event-action plan. Finally, you apply that event-action plan to a system or group of systems. An event-action plan is composed of two types of components: v Event filters, which specify event types and any related parameters v Event actions, which occur in response to filtered events You can apply an event-action plan to an individual managed object, several managed objects, or a group of managed objects. By creating event-action plans and applying them to specific managed objects, you can be notified by e-mail or pager, for example, when a specified threshold is reached or a specified event occurs. Or you can configure an event-action plan to start a program on a managed object and change a managed-object variable when a specific event occurs. You can use process-monitor events and resource-monitor events to build an event-action plan. Successful implementation of event-action plans requires planning and consideration of how you will implement them. In particular, developing and following strict naming conventions is important, so that you can easily identify what a specific plan does.
Modifying an existing event-action plan

You can modify an existing event-action plan, even one that is already applied to managed objects or groups, using the Event Action Plan Builder. If you modify an event filter or an event action that is used in an existing event-action plan, the changes are applied automatically to any event-action plans that use those filters or actions. If you add or delete a filter or an action that is used in an existing event-action plan, a warning is displayed.
Event filters
An event filter specifies an instance of one or more events that you want IBM Director to process. IBM Director ignores any event instances that do not meet the specifications of the event filter. Because the event filter can specify possible values for the extended attributes that are included in an event types definition, an event instance can be customized for very specific problems and occurrences. To permit users to create event filters quickly, the extended attributes include default values; however, users can customize the extended attribute settings.
18
You can use an event filter to capture a single event or multiple events. The following list includes some of the criteria that you can use to determine whether to include an event with other events: v All managed objects that are targeted for the filter are able to generate all events that are included in the filter. If the managed object does not generate the event for which the filter is defined, the filter will not be effective on that managed object. v The event actions that will be used to respond to the event are the same for all targeted objects. v The other event filter options besides the event type are common for all targeted objects. These settings include the number of times the event filter is active, the severity of the event, and other attributes. Event-action plans can include event filters with event types that are not generated by all managed objects. In such instances, you can apply the event-action plan to those managed objects, but it will have no effect. For example, if an event filter is based on a ServeRAID event and that event-action plan is applied to managed objects that do not have a ServeRAID adapter installed, the event filter has no events to filter, and therefore, no actions are performed. If you understand this concept, you can create more complex event-action plans, and you can reduce the number of event-action plans you have to build and maintain. All currently available event types are displayed in the tree on the Event Type page in the Event Filter Builder window. The currently installed tasks and extensions publish their events in the Event Type tree when IBM Director Server or IBM Director Agent or IBM Director Core Services starts. Note: Whether the events are published when IBM Director Server or IBM Director Agent or IBM Director Core Services starts depends on the tasks or extensions and how they are implemented. If you add an extension to your IBM Director installation, the extension might publish its events either when it is added to the installation or when the extension sends its first event. If the extension publishes when it sends its first event, only that event is published. Event-filter types: IBM Director provides four types of event filters. In the Event Action Plan Builder window, the Event Filters pane provides the following event filters.
19
Event filter Simple Event
Description Simple event filters are general-purpose filters; most event filters are this type. When you expand this tree, any customized simple event filters that you have created are displayed. Also, the following predefined, read-only event filters are displayed: v All Events v Critical Events v Environmental Sensor Events v Fatal Events v Hardware Predictive Failure Events v Harmless Events v Minor Events v Security Events v Storage Events v Unknown Events v Warning Events Some of these predefined filters use the severity of events to determine which events they will allow to pass through; other filters target a specific type of event. For example, the Critical Events filter processes only those events that have a Critical severity. The All Events filter processes any events that occur on any managed object, except for Windows-specific and i5/OS-specific events. Using one of these preconfigured event filters ensures that the correct event type or event severity is preselected. If you want to see what events are included in a predefined event filter, double-click that predefined event filter in the Event Filters pane. The Simple Event Filter Builder window opens, and the Event Filter Builder notebook is displayed. Select the applicable notebook page to view the selected event filters. For example, click the Severity tab to view the selections for the Critical Event filter. You cannot change predefined event filters; they are read-only. However, you can make changes and click File Save As to save the modified event filter with another name.
Duplication Event Duplication event filters ignore duplicate events, in addition to the options that are available in the simple event filters. To use this filter, you must specify the number of times (Count) that the same event is ignored during a specified time range (Interval). Then, this filter processes the first event that meets the criteria that are defined for this filter. Only the first event triggers the event actions that are associated with this event filter. For the associated event actions to be triggered again, one of the following conditions must be met: v The value that is specified in the Count field must be exceeded. v The time range that is specified in the Interval field must elapse. v The value that is specified in the Count field must be exceeded by 1 (Count+1) within the time range that is specified in the Interval field. For example, you can define a duplication event filter to filter on the occurrence of an offline event and define a corresponding event action to forward the event to IBM Director Server. Depending on the criteria that you define, only the first event announcing that the system is offline is processed, and all other instances in which an event meets the filtering criteria are discarded until the Count value is exceeded during the specified interval. Exclusion Event Exclusion event filters exclude certain event types, in addition to the simple event filter options. Using this filter, you define the criteria of the events to exclude.
20
Event filter Threshold Event
Description A threshold event filter processes an event after it has occurred a specified number of times within a specified interval, in addition to the simple event filter options. An event that meets the criteria that are defined in this filter triggers associated actions only after an event has met the criteria for the number of times that are specified in the Count field or only after the number of times specified in the Count field within the time range specified in the Interval field. For example, you can define a threshold event filter to monitor frequently occurring heartbeat events and forward the event to IBM Director Server only when the heartbeat event is received for the 100th time during a specified amount of time.
Event-filter criteria: Depending on the event-filter type, you set specific values for these types of criteria.
Criteria Description
Event Type Use the Event Type page to specify the source or sources of the events that are to be processed. This tree is created dynamically; and entries are added by tasks and as new alerts are received. Entries in the tree can be expanded to display suboption events. Most event filters are created using only this page. It specifies the source or sources of the events that are to be processed by this filter. By default, the Any check box is selected, meaning that none of the events that are listed are filtered, except for Windows-specific and i5/OS-specific events. If you want to specify certain events on which to filter, clear the Any check box. You can highlight more than one event by pressing the Ctrl or Shift key. Notes: 1. When you select a root option in the Event Type tree, all suboption events are selected as well. For example, when you select MPA in the Simple Event Filter Builder window, all Component, Deployment, Environmental, and Platform suboption events are selected also. If additional event types are published after you create the event filter, the newly available event types are included in your event filter only if the new event types are suboption events of an event type that you selected. However, if you want to include a newly published event type that is not a suboption event, you must update the event filter by selecting the new event type. 2. The event types for BladeCenter events are displayed under MPA, except for BladeCenter Configuration Management events, which are displayed under Configuration Management.
21
Criteria Severity
Description Use the Severity page to indicate the urgency of the events that are filtered. If an event is received whose severity level is not included in the event filter, the filter will not process that event. By default, the Any check box is selected, indicating that all event severities are processed by the filter. When you select more than one severity, they are joined together using logical OR. The source of the event determines what severity the event is. Generally, the severity levels have the following meanings: Fatal The event caused a failure and must be resolved before the program or component is restarted.
Critical The event might cause a failure and must be resolved immediately. Minor Warning The event is not necessarily problematic but might warrant investigation. Harmless The event is for information only. Most events of this severity do not indicate potential problems. However, offline events are categorized as harmless, and these events can indicate potential problems. Unknown The application that generated the event did not assign a severity level. Day/Time Use the Day/Time page to set the filter to accept and ignore events on certain days and at certain times of the day. By default, the Any check box is selected, indicating that events that occur at any time are processed by the event filter. The time zone that applies to the specified time is the time zone in which the management server is located. If your management console is not in the same time zone as the management server, the difference in time zones is displayed above the Selections pane as an aid to determining the correct time. By default, all events are passed through all filters. This includes events that were queued by IBM Director Agent because the link between the managed object and the management server was unavailable. However, you can prevent these queued events from being processed by a filter by selecting the Block queued events check box. This option can be useful if the timing of the event is important or if you want to avoid filtering on multiple queued events that are sent all at once when IBM Director Server becomes accessible. However, you can block queued events only if you filter events at a specified time. To block queued events, you must clear the Any check box. Category Use the Category page to specify an event filter according to the status of an event (alert or resolution of a problem). However, not all events have resolutions. The event is not likely to cause immediate program failure but should be resolved.
22
Criteria Sender Name
Description Use the Sender Name page to specify the managed object to which the event filter will apply. Events that are generated by all other managed objects will be ignored. By default, the Any check box is selected, indicating that events from all managed objects (including IBM Director Server) are processed by the event filter. Initially, only IBM Director Server is shown in the list. As other managed objects generate events, such as when a threshold is exceeded, this list is added to dynamically. If you anticipate that other managed objects will generate events, you also can type managed-object names into the field and click Add to add them.
Extended Attributes
Use the Extended Attributes page to specify additional event-filter criteria using additional keywords and keyword values that you can associate with some categories of events, such as SNMP. This page is available only when you clear the Any check box on the Event Type page and select certain entries from that page. If the Extended Attributes page is available for a specific event type but no keywords are listed, IBM Director Server is not aware of any keywords that can be used for filtering. To view the extended attributes of specific event types, expand the Event Log task in the IBM Director Console Tasks pane and select an event of that type from the list. The extended attributes of the event, if any, are displayed at the bottom of the Event Details pane, below the Sender Name category.
System Variables
Use the System Variables page to further qualify the filtering criteria by specifying a system variable. This page is available only if there are one or more system variables. A system variable consists of a user-defined pairing of a keyword and value that are known only to the local management server. Note: These user-defined system variables are not associated with the system variables of the Windows operating system. Use the Event Text page to specify event message text to associate with the event.
Event Text
Event actions
The event action specifies the actions that you want IBM Director to take as a result of the occurrence of an event.
Event action types

IBM Director has several predefined event action types. With the exception of Add to Event Log, you must customize each event action type that you want to use. Add/Remove event system to Static Group Adds a managed object to or removes a managed object from a specified static group when the managed object logs a specific event. Add/Remove source group members to target static group Adds all specified managed objects in a source group to a target group or removes all specified managed objects from the target group. Add a Message to the Console Ticker Tape Displays a message in red type that scrolls from right to left at the bottom of IBM Director Console. Add to the Event Log Adds a description of the event to the IBM Director event log.
23
Define a Timed Alarm to Generate an Event Generates an event only if IBM Director does not receive an associated event within the specified interval. Define a Timed Alarm to Start a Program on the Server Starts a program on the management server if IBM Director does not receive an associated event within the specified interval. Log to Textual Log File Generates a text log file for the event that triggers this action. Post a News Group (NNTP) Sends a message to a newsgroup using the Network News Transfer Protocol (NNTP). Resend Modified Event Creates or changes an event action that modifies and resends an original event. Send an Alphanumeric Page (via TAP) Windows only) Sends a message to a pager using the Telocator Alphanumeric Protocol (TAP). Send an Event Message to a Console User Displays a popup message on the management console of one or more specified users. Send an Internet (SMTP) E-mail Sends a Simple Mail Transfer Protocol (SMTP) e-mail message. Send an SNMP Inform to an IP host Sends an SNMP inform request to a specified IP host. Send an SNMP Trap to a NetView Host Generates an SNMP trap and sends it to a specified NetView host using a TCP/IP connection to the host. If delivery of the SNMP trap fails, a message is posted in the history log of the managed object. Send an SNMP Trap to an IP Host Generates an SNMPv1 or SNMPv2c trap and sends it to a specified IP address or host name. Send a Numeric Page (Windows only) Sends a numeric-only message to the specified pager. Send a TEC Event to a TEC Server Generates a Tivoli Enterprise Console event and sends it to a specified Tivoli Enterprise Console server. Set an Event System Variable Sets the managed system variable to a new value or resets the value of an existing system variable. Start a Program on a System Starts a program on any managed objects on which IBM Director Agent is installed. Start a Program on the event System Starts a program on the managed object that generated the event. Start a Program on the Server In response to an event, starts a program on the management server that received the event.
24
Start a Task on the event System In response to an event, starts a noninteractive task on the managed object that generated the event. Update the Status of the event System When the selected resource status generates an event, causes a status indicator beside the icon of the managed object that is associated with the resource to be set or cleared according to your specification.
Event-data-substitution variables
For some event-action types, you can include event-specific information as part of the text message. Including event information is referred to as event-data substitution. You can use these event-data-substitution variables to customize event actions. &date The date the event occurred. &time The time the event occurred. &text The event details, if they are supplied by the event.
&type The event-type criteria that are used to trigger the event. For example, the event that is generated when a managed object goes offline is of type Director > Topology > Offline. This corresponds to the entry on the Event Type page. &severity The severity level of the event. &system The name of the managed object for which the event was generated. The system name is either the name of IBM Director Agent or, in the case of an SNMP device, the TCP/IP address. &sender The name of the managed object from which the event was sent. This variable returns null if the name is unavailable. &group The group to which the target object belongs and is being monitored. This variable returns null if the group is unavailable. &category The category of the event, either Alert or Resolution. For example, if the managed object goes offline, the category is Alert. If the managed object goes online, the category is Resolution. &pgmtype A dotted representation of the event type using internal type strings. &timestamp The coordinated time of the event. &rawsev The nonlocalized string of event severity (Fatal, Critical, Minor, Warning, Harmless, Unknown). &rawcat The nonlocalized string of event category (Alert, Resolution). &corr The correlator string of the event. Related events, such as those from the same monitor-threshold activation, will match this.
25
&snduid The unique ID of the event sender. &sysuid The unique ID of the managed object that is associated with the event. &prop:file_name#property_name The value of the property string property_name from property file file_name (relative to the IBM\Director\classes directory). Note: For i5/OS, the absolute directory path must be used. &sysvar:variable_name The event system variable variable_name. This variable returns null if a value is unavailable. &slotid:slot_id The value of the event detail slot with the nonlocalized ID slot_id. &md5hash The MD5 (message digest 5) hash code, or cyclic redundancy check (CRC), of the event data (an event-specific unique ID). &hashtxt Provides a full replacement for the field with an MD5 hash code (32-character hex code) of the event text. &hashtxt16 Provides a full replacement for the field with a short MD5 hash code (16-character hex code) of the event text. &otherstring The value of the detail slot that has a localized label that matches otherstring. A detail slot is a record in an event detail. For example, an event has one event detail that has an ID of key1 and a value of value1. You can use the substitution variable &soltid:key1 to obtain the value value1. You also can use &key1 to obtain the value value1. In the description above, otherstring is a placeholder for the user-defined event detail ID. However, if the passed ID is not found, Not applicable is returned.
Message Browser
You can use the Message Browser to view events that are sent to IBM Director Console. The Message Browser is displayed automatically whenever an alert is sent to the management console. You can choose to have events sent to the management console when an event occurs by configuring an event action plan with the Send an Event Message to a Console User event action. The Message Browser displays all alerts, including management console ticker-tape alerts. However, the Message Browser does not display any ticker-tape messages. A ticker-tape message can display, for example, resource-monitor data.
Choosing between resource and process monitors

Process monitors and resource monitors are important tools for monitoring applications. Through the implementation of these monitors, you have access to events that can trigger an event action plan to resolve a problem quickly and automatically. How you intend to use your event action plan can help determine whether you should use a resource monitor or a process monitor.
26
If you want to monitor a dynamic or static group of managed objects, you must use resource monitors. Process monitors cannot be applied to groups. You can only apply a process monitor to one managed object at a time. If you want to monitor processes, applications, or Windows services on managed objects that are running Windows, you can use either resource monitors or process monitors. To monitor processes or applications on managed objects that are running operating systems supported by IBM Director except Windows, you must use process monitors. Events that are generated when a process is being monitored using a resource monitor have an alert-resolution pairing for the event category. For example, if a Windows service is stopped, the event that is generated has the category of Alert. This category causes an orange triangle to be displayed next to the affected managed object or group in IBM Director Console. When the Windows service is started, an event is generated with the category of Resolution and the orange triangle is cleared from IBM Director Console. However, events that are generated when a process is being monitored with a process monitor do not have an alert-resolution pairing for the event category. If a process is stopped, the event that is generated has the category of Alert and an orange triangle is displayed next to the affected managed object in IBM Director Console. However, when the process is started, the event that is generated also has the category of Alert and the orange triangle continues to be displayed in IBM Director Console even though the problem has been resolved. See the following table for a quick comparison of resource and process monitor features.
Table 3. Comparison of resource monitor and process monitor features Resource monitors Can be applied to groups Can be used only on systems running Windows Clear the orange triangle after the problem has been resolved Process monitors Cannot be applied to groups Can be used on systems running all operating systems supported by IBM Director Continue to display the orange triangle in IBM Director Console after the problem has been resolved
External application tasks

External application tasks are user-defined tasks that are displayed in IBM Director Console. They can be a parent without a command or can start a command, process, or application that is external to IBM Director and runs on the management console or server. External application tasks are defined for IBM Director by a set of resources that you can create manually or by using the External Application Launch wizard. These resources specify the application to be started, the task title in IBM Director Console, the location of the task in IBM Director Console, the icons associated with the task, and way the task is started in IBM Director Console. External application tasks can be targeted, untargeted, or both. External Application Launch tasks have resources for each supported language defined in the command-task file, a process simplified by the External Application Launch wizard.
27
External-application task resources

External-application tasks are defined in IBM Director using a combination of Java resources including command-task files, Java resource bundles, and task icons. Important: You must install IBM Director in the default location to use External Application Launch or the External Application Launch Wizard.
Command-task files
Command-task files are Java property files that are used by the IBM Director command-task service to configure tasks to run in the IBM Director environment. New command-task files can be constructed and existing command-task files can be modified using the External Application Launch Wizard or manually using an editor.
Java resource bundles

Command-task files can reference Java resource bundles to apply national-language titles to the external application task. Use the External Application Launch Wizard to create Java resource bundles and or to specify an existing Java resource bundle and title property key. Java resource bundles created using the External Application Launch Wizard can be modified using the wizard. External Application Launch Wizard cannot modify Java resource bundles that were created manually. You can create and modify External Application Launch resource bundles using an editor or the External Application Launch Wizard. It is your responsibility to ensure the accuracy of Java resource bundles that you create manually using an editor. External Application Launch Wizard always creates at least two properties files for resources (one default file and one English file). For example, if you created a command-task file with the title keyword apple, the result would be resource bundles named appleResources.properties and appleResources_en.properties. If you provide additional non-English titles, additional resource bundles are created for each locale that you defined. For example, if you provided French and Spanish titles as well, appleResources_fr.properties and appleResources_es.properties files would also be created. These resource-bundle files reside in one of the following directories, depending on your operating system:
Table 4. Location of resource-bundle files by operating system Windows installation Linux installation \Program Files\IBM\Director\classes\ CmdTask\resources /opt/IBM/director/classes/CmdTask/ resources
where resources represents the directory that contains resource files for a specific external-application task. If you used the External Application Launch Wizard to create the resource files, resources would be the same as the name of the command-task file. Note: Although IBM Director ensures that IBM Director data is valid, you are responsible for ensuring that data in the resource bundles is valid for the intended purpose.
28
Task icons
Command-task files can reference Graphics Interchange Format (GIF) files that are used as task icons. These files can be existing IBM Director task icon files specified with a path name relative to the classes directory under the IBM Director installation, or they can be any nonanimated GIF files specified in the command-task file with a fully qualified path and file name. Task icon files can be specified for small (16-pixel) and large (32-pixel) icons. If IBM Director cannot find the icon file specified in the command-task file, External Application Launch replaces the custom icon with a question mark (?). If an icon file is not specified in the command-task file, a default icon is used. The customized image files reside in one of the following directories, depending on the operating system on which IBM Director is installed:
Table 5. Location of customized image files by operating system Windows installation Linux installation \Program Files\IBM\Director\classes\ CmdTask\resources /opt/IBM/director/classes/CmdTask/ resources
where resources represents the directory that contains resource files for a specific external-application task. Tip: Icons look best on the IBM Director Console when you create them using a transparent background.
Targeted and untargeted tasks

All IBM Director tasks (including native IBM Director tasks, tasks added by installing extensions, and external application tasks) are either targeted, untargeted, or both, depending on how the task can be started. Targeted tasks Targeted tasks are tasks for which a managed object is specified when the task is started. Targeted tasks are started in one of three ways: v By right-clicking a managed object and selecting the task v By dragging the managed object to the task in the Tasks pane v By dragging the task to the managed object in the Managed Objects pane Typically, a targeted task performs an action on the managed object specified as the target. Examples of targeted tasks are Remote Control, Remote Session, and SNMP Browser. When an external application is started as a targeted task, information about the specified target is provided. If one or more system attribute names are configured, the available values for each target are passed to the application using environment variables. If no system attributes are configured, the IP address, MAC address, and computer name are passed to the application by way of environment variables. Untargeted tasks Untargeted tasks are tasks for which no managed object is specified when the task is started. Untargeted tasks are started in one of two ways: v By double-clicking the task in the Tasks pane v By selecting the task from the Tasks menu
29
Untargeted tasks perform actions that are not specific to a targeted managed object, perform actions that apply to all managed objects, or provide their own interface for selecting managed objects on which to perform actions. Examples of targeted tasks are Scheduler, Rack Manager, and Hardware Status. Tasks that are both targeted and untargeted A task may be both a targeted task and an untargeted task, with behavior reflecting the manner in which the task is started. The Inventory task is an example of such a task: if started from a managed objects pop-up menu or by dragging it to a managed object, it displays information for that object only; if started from the Tasks menu, it displays information for all managed objects.
Managed-object groups
IBM Director allows you to organize logical sets of managed objects into groups. Managed-object groups have the following general characteristics: v Groups can include managed objects. v Groups can include other managed-object groups. v Managed objects can belong to multiple groups. v You can perform tasks on groups in order to perform the task on every group member. v When you select a group, the managed objects that are members of that group are displayed in the Group Contents pane. There are several types of groups that you can create in IBM Director: Static groups Static groups contain a specified list of managed objects. IBM Director Server does not automatically update the contents of a static group. The members of a static group are fixed unless you change them using IBM Director Console, the dircli chgp command, or an event action plan. You can also copy the members of any dynamic group to a static group. For example, a static group might contain all the managed objects that are physically located in a particular server room. Group categories Group categories contain a specified list of managed-object groups. In other words, a group category is a kind of static group which has only other groups as members. If you perform a task on a group category, the task is performed on all the managed objects that are members of the groups in the group category. For example, if static groups are defined based on the room where a managed object is located, a group category might include all the static groups for rooms in a particular building. Tip: It might be useful to consolidate all groups for which you have administrative authority into a single group category. This enables you to focus on those managed systems that are your responsibility while removing other managed systems and devices from your immediate attention. Dynamic groups Dynamic groups are based on specified managed-object attribute or
30
inventory criteria. You can create a dynamic group by specifying criteria that the attributes and properties of the managed systems must match. IBM Director automatically adds or removes managed systems to or from the group when their attributes and properties change, affecting their match to the group criteria. For example, a dynamic group might contain all managed systems that have Linux installed. Note: You can delete some of the default dynamic groups created by IBM Director. If you want to use these groups after you have deleted them, you must create them again. See Creating a criteria-based dynamic group. Task-based groups Task-based groups are dynamic groups that are based on the IBM Director tasks that can be performed on the managed objects. For example, a task-based group might contain all the managed objects for which both the Hardware Status and Remote Session tasks can be performed. When you start IBM Director Console for the first time, the default groups are displayed. Some of these default groups are described below. All Groups The All Groups group contains all managed-object groups in IBM Director. All Managed Objects The All Managed Objects group contains all discovered managed objects in IBM Director. Hardware Status groups The Hardware Status Critical, Hardware Status Information, and Hardware Status Warning groups are dynamic groups that contain managed objects for which there are unresolved hardware status events.
Groups that are used with scalable objects

IBM Director provides several default groups of scalable objects in the Groups pane for easier management of these objects. The default groups that are relevant to scalable objects are shown in table below.
Table 6. IBM Director groups that are used with scalable objects Group name Logical Platforms Physical Platforms Platforms Platforms and Platform Members Managed objects All logical-platform objects, which includes all scalable partitions. All physical-platform objects, which includes all scalable nodes. All logical platforms and physical platforms. All logical and physical platforms and any managed systems that result from these platforms. Only scalable partitions. Only scalable systems.
Scalable Partitions Scalable Systems
31
Table 6. IBM Director groups that are used with scalable objects (continued) Group name Scalable Systems and Members Managed objects All scalable systems and all members of those scalable systems. Members of a scalable system include its scalable partitions, its scalable nodes, and any remote I/O enclosures attached to its scalable nodes. This group also includes managed systems that result from its scalable partitions.
Groups used with storage managed objects

IBM Director provides several default groups of storage managed objects in the Groups pane for easier management of these objects. This table lists the groups that support storage managed objects.
Group name SMIS-Storage Devices Storage Devices Systems with Fibre Channel Ports Storage managed objects Only storage managed objects that comply with the SMI-S standard. All storage managed objects, regardless of compliance with SMI-S standards. All disk arrays, switches and servers that have Fibre Channel connectivity.
High availability
In IBM Director, high availability configuration allows IBM Director Server operations to be performed by a redundant IBM Director Server instance in the event of a failure on a management server, when IBM Director is run in conjunction with a high-availability system such as IBM Tivoli System Automation for Multiplatforms or SteelEyes LifeKeeper. Depending on the IBM Director configuration, high availability in IBM Director might have some or all of the following characteristics: v IBM Director events are sent, and event action plans are performed, even in the event of an unexpected failover of the management server. v Data loss is minimized in the event of an unexpected failover of the management server. v Non-interactive tasks, including scheduled jobs, save runtime checkpoints, and restart automatically from the last saved checkpoint in the event of an unexpected failover of the management server.
Managed objects
A managed object is a system or device that is managed by IBM Director. IBM Director manages these types of objects: managed system Any computer, such as a server, desktop, workstation, or mobile computer, that can be managed by IBM Director. In this release, managed systems are subcategorized as follows:
32
Level-0 (agentless) managed systems Systems that are managed through the network services that are native to the operating system: Secure Shell (SSH) or Windows Management Instrumentation (WMI). No IBM Director software is installed. Level-1 managed systems Systems that are managed through installation of IBM Director Core Services, which provides a subset of IBM Director Agent functionality, including Remote Session, Power Control, Hardware Status, Event Log, hardware-only inventory data, and distribution of system level updates. Level-2 managed systems Systems that are managed through installation of IBM Director Agent, which provides added functionality for administering the system. The functionality of IBM Director Agent on the managed system will vary depending on the operating system and platform. managed device An SNMP device (such as a network device, printer, desktop computer, or server) that has an SNMP agent installed or embedded. physical platform A single physical chassis or server that has been discovered through the use of the Service Location Protocol (SLP). A physical platform also can be created when: v A deployable system is discovered through an RDM scan. v You right-click any blank space in the Group Contents pane to create the physical platform manually. v IBM Director Server determines that a physical platform does not exist already for a blade server in a BladeCenter unit. v IBM Director Server first discovers and gains access to a Level-1 or Level-2 managed system. v IBM Director Server gains Internet Protocol (IP) access to a Remote Supervisor Adapter service processor. It will query the Remote Supervisor Adapter or Remote Supervisor Adapter II service processor for the topology of its associated ASM interconnect network, and for each ISMP system found, a physical platform is created. A physical platform can identify some managed systems before an operating system or IBM Director Agent is installed. Note: To delete a physical platform from IBM Director Console, you also must delete any associated managed system or systems. Scalable objects Systems with multinode configurations, including scalable systems, nodes, and partitions. BladeCenter chassis A BladeCenter unit that acts as an enclosure. This 7-U modular chassis can contain up to 14 blade servers. It enables the individual blade servers to share resources, such as the management, switch, power, and blower modules. Windows cluster A collection of Microsoft Windows systems that work together to provide a single, unified computing capability.
33
Racks Racks that are created by Rack Manager. Static partitions A view-only scalable partition.
Managed system
A managed system is a computer, such as a server, desktop, workstation, or mobile computer, that can be managed by IBM Director. There are three levels that are used to categorize managed systems.
Level 0: Agentless Systems

Level 0: Agentless Systems do not have any IBM Director software installed on them; however, although they can still be managed by using IBM Director. Level-0 managed systems can be IBM or non-IBM servers, desktop computers, workstations, and mobile computers. A Level-0 managed system is a managed system that does not have IBM Director Agent or the Common Information Model (CIM) instrumentation installed, but does have the minimum set of protocols that are required for that system to be managed by IBM Director. To manage a system using IBM Director, that system, at a minimum, must support the Secure Shell (SSH) or Distributed Component Object Model (DCOM) protocol. Level 0: Agentless Systems is supported on systems that are running the following operating systems. For a detailed list of supported operating-system versions, see IBM Director Planning, Installation and Configuration Guide. v Linux v Windows IBM Director discovers Level-0 managed systems by verifying the IP addresses on your network and scanning the ports of those addresses using the SSH or DCOM protocols. The range of IP addresses that are verified is governed by the IBM Director discovery preferences that you configure in IBM Director Console. By default, IBM Director uses the range of addresses that are in the IP domain of the management server. When a Level-0 managed system is discovered, it is locked by default. You can unlock the system by requesting access to it through IBM Director Console. Every task that was previously available only on physical platforms is now available on Level 0 systems as well, including Power Management, Server Configuration Manager, MPA CLI, MPA Web interface, and System Information. The attributes that are returned for a Level-0 managed system include: v Locked System Name TCP/IP Addresses System State MAC Address System Presence Check Setting v Unlocked Computer Name Architecture OS Major Version OS Minor Version Access Denied
34
Operating System Unique System ID System UUID (xSeries) Machine Type Model Number Serial Number
After you discover and unlock a Level-0 managed system, you can perform the following tasks on that system: v 5.10 Update 3 and earlier: v Collect inventory that is available from the operating system v Install Level 1: Core Services or Level 2: IBM Director Agent by using software distribution v Restart the operating system (Linux only) v v v v v v v Run command-line programs (if SSH is present) 5.20 and later: Power Management Server Configuration Manager MPA CLI MPA Web interface System information
Level 1: IBM Director Core Services systems

Level 1: IBM Director Core Services provides managed systems with a subset of the Level 2: IBM Director Agent functionality that is used to communicate with and administer that system. Specifically, it provides hardware alerts and status information that can flow to Director or third-party management servers. A Level-1 managed system is any system that has Level 1: IBM Director Core Services installed but does not have Level 2: IBM Director Agent installed. Level-1 managed systems can be IBM servers, desktop computers, workstations, and mobile computers. You can perform these tasks on a Level-1 managed system: v Collect inventory. v Install Level 2: IBM Director Agent using software distribution. v Manage events using event action plans, event subscription, and the event log. v Monitor hardware status. v v v v v v v v Restart or shut down the managed system. Run command-line programs. 5.20 and later: Power Management Server Configuration Manager MPA CLI MPA Web interface System information
Level 1: IBM Director Core Services is supported on systems that are running the following operating systems. For a detailed list of supported operating-system versions, refer to the IBM Director Planning, Installation and Configuration Guide.
35
v Linux (System x, System p, and System z) v Windows
Level 2: IBM Director Agent systems

Level 2: IBM Director Agent provides managed systems with the full complement of IBM Director Agent functionality that is used to communicate with and administer that system. The functionality of Level-2: IBM Director Agent on a managed system varies, depending on the operating system and platform. A Level-2 managed systems is any system that has Level 2: IBM Director Agent installed. Level-2 managed systems can be IBM or non-IBM servers, desktop computers, workstations, and mobile computers. Level 2: IBM Director Agent is supported on systems that are running the following operating systems. For a detailed list of supported operating-system versions, refer to the IBM Director Planning, Installation and Configuration Guide. v AIX v i5/OS v Linux (System x, System p, and System z) v NetWare v Windows
Mass configuration
Using mass-configuration profiles, you can quickly configure a group of managed objects. A mass-configuration profile identifies the configuration information that you want to distribute to a managed object or group. Even in a dynamic host control protocol (DHCP) environment, many critical servers tend to use static addresses. Using mass-configuration profiles, you can, for example, change the IP address that these managed systems use to locate their primary DNS server, without having to physically visit each system. You can create a profile for these IBM Director tasks: v Asset ID v Configure Alert Standard Format v Configure SNMP Agent v Network Configuration The mass-configuration profiles are saved in the Tasks menu (and in the Tasks pane) under the task with which they are associated. After you create a mass-configuration profile, you then can apply that profile to a managed object or a group.
Microsoft Cluster Management

You can monitor the status of clusters in your network using the Microsoft Cluster Browser. In IBM Director, a cluster is a representation of a collection of network resources. Note: To enable IBM Director to monitor the cluster, each system in the cluster must have IBM Director Agent installed. Using clusters, you monitor the status of a logical collection of resources (resource groups) that can be distributed across nodes in a network or across network boundaries. For example, a Web server resource group might consist of individual
36
resources, such as an IP address, a physical disk containing the server files, and an application that defines how the server is started. One purpose of this resource group might be to ensure and enable redundancy of the Web server such that the resources could be transferred from one system to another if the Web server goes down. IBM Director supports only the clustering implementation of Microsoft Clustering Service (MSCS). For Windows systems configured with MSCS, a managed system interfaces with this service to obtain and present basic cluster data, including the name of the cluster, individual member nodes of the cluster, resource groups, and the resources defined for each group. The following possible states of a cluster are defined and monitored through the IBM Director agents installed on each managed system in the cluster and reported to the IBM Director. These states apply to the cluster objects in the IBM Director Console, not in the Microsoft Cluster Browser. The Microsoft Cluster Browser does not display the state of a cluster as a whole; it displays the states of individual cluster resources, such as resource groups, nodes, networks, and network interfaces. Normal online One or more nodes are online and all resource groups are online and available. Error online One or more nodes are online and one or more resource groups are unavailable. Error offline All nodes in the cluster are online but one or more resources or resource groups are unavailable. Normal offline No systems are online. You can use the Resource Monitors task to define thresholds and use the Event Action Plans task to create event action plans for these and other cluster states, according to the needs of your organization.
Naming conventions and physical platform managed objects

When physical platform managed objects (PPMOs) are discovered, they are displayed in IBM Director Console according to the default naming template: IBM %SERVER_MACHINE_TYPE_MODEL% %SERVER_SERIAL_NUMBER%. However, system administrators typically name their systems according to a predefined, standard naming convention. Such conventions provide the following advantages: v Computer resources that you are managing with IBM Director are easy to locate v The physical locations of computer resources that you are managing are easy to locate, such as within a datacenter that has the aisles numbered. v The purpose of a system is described, eliminating the need to inspect the system. v Systems that are owned by different organizations, but share network space or physical space, are easily identified.
37
To use a different naming convention, you must change this PPMO default naming template to match your standardized naming convention. Auto Rename is an IBM Director function that system administrators can use to apply a desired naming convention to PPMOs. You can use the Auto Rename function in IBM Director Console to easily rename PPMOs.
Network-timeout settings and command processing

IBM Director tasks communicate using commands. Commands are similar to e-mail messages. They have a destination address, a return address, and a message. Typically, a message is one of the following situations: v A request for some information or to perform an action v A response to or result of a request However, unlike e-mail, all commands make a round trip to the destination and back to the sender. The receiver is able to return results and the sender receives confirmation that the message was received. The command sender always expects to get a command response from the receiver. However, a response is not always received. A command might not reach its destination because the receiver is offline or there are network problems. Because of these concerns, commands include a timeout value. The command-timeout value indicates the length of time that the sender is willing to wait for a response to this command. If the command-timeout value elapses before the response is received from the destination, the sender is notified that the command timed out. The command-timeout value attempts to strike a balance between reliably receiving a command response and the delay a user experiences before receiving a response to an action. However, it is impossible to anticipate every situation. All commands do not travel across the network at the same rate, customer environments vary, and it is difficult to find a solution that is suitable for every situation. Consider that a command that is routed within a local system is processed very quickly, but a command that collects inventory from a remote managed system takes longer to process. Commands might time out because the network or the management server is slower than usual. Although increasing the command-timeout value might eliminate timeouts, it cannot correct a slow network or system. When a user requests access to a Level-2 managed system, the user expects a response within a short time, probably less than 15 seconds. A command-timeout value of five minutes might guarantee that the command does not timeout, but it is much longer than most users are willing to wait for a response. Carefully weigh the advantage of ignoring timeout failures when the network is slow against the disadvantage of waiting longer for all commands to complete. You can use the network-timeout setting to tune the command-timeout value in your environment. The network-timeout setting is actually a scaling factor. It allows you to increase or decrease the command-timeout value on all commands through a single setting. The default network-timeout setting is 15 seconds. With the default setting, all of the command-timeout values are left unchanged. If the network-timeout setting is increased, all of the command-timeout values are increased proportionally according to the following formula: (command-timeout value in the task code) X (network-timeout setting / 15) = actual timeout.
38
For example, suppose that the command-timeout value for a specific command is 60 seconds. The network-timeout setting is 45 seconds. The actual timeout is calculated as 60 seconds X (45 seconds / 15 seconds) = 180 seconds (3 minutes). You should adjust the network-timeout setting only in the following situations: v You are receiving messages indicating that tasks or other actions are timing out. v Tasks or actions are taking a long time and intermittently failing. Because the actual time for a command varies, commands sometimes time out and sometimes complete successfully, resulting in intermittent task failure. Note: The default network-timeout is set on the management server, but because commands are routed from IBM Director Console through IBM Director Server to IBM Director Agent, the setting can seem to affect management consoles and managed objects as well. Typically, a command timeout is a problem only for commands that are sent from the management server to Level-2 managed systems. These commands usually time out because of network latency or bandwidth issues. Also, high microprocessor (CPU) use on a Level-2 managed system can slow command processing by IBM Director Agent. Notes: 1. The network-timeout setting does not affect discovery because discovery does not use commands. 2. Increasing the network-timeout setting can affect the user experience. Users might wait longer before getting a response to certain management console actions.
Scalable objects
Scalable objects are IBM Director managed objects that are used with multinode configurations of scalable IBM System x and xSeries servers. Scalable objects in IBM Director for scalable IBM System x and xSeries servers include: v Scalable nodes v Scalable partitions v Scalable systems IBM Director communicates out-of-band with service processors in scalable IBM System x and xSeries servers to manage hardware partitions. Each hardware partition can run a single image of the operating system and is defined as a scalable partition that consists of one or two scalable IBM System x and xSeries servers. The servers that are defined in a scalable partition have at least one SMP Expansion Module and are referred to as scalable nodes. A scalable system consists of scalable nodes and the scalable partitions that were created from those scalable nodes. These IBM Director managed objects are referred to as scalable objects throughout this documentation. Note: IBM Director performs only discovery and power operations for scalable systems and scalable partitions that have been previously configured on scalable IBM System x and xSeries servers. It does not create or configure scalable systems or scalable partitions.
39
Scalable nodes
A scalable node is a server that has one or more SMP Expansion Modules. When IBM Director discovers such a server, it creates a physical-platform managed object. It also assigns attributes that record the number of SMP Expansion Modules, SMP Expansion Ports, and RXE Expansion Ports on the physical chassis. In IBM Director Console, scalable nodes are identified with the same icon that is used for all physical platforms. To determine whether a physical platform has the additional attributes of a scalable node, in the Group Contents pane, double-click the icon for the physical platform. The Display System Attributes window opens and the attributes for SMP Expansion Modules and RXE Expansion Ports are in the list that is displayed. The following requirements apply to multinode configurations: v All servers in one scalable system must be of the same machine type and model, and must have the same number of SMP Expansion Modules. v All servers in one scalable system must have the same type of service processor and the same firmware code level. v The service processor of each server must be connected to an active network. This connection is necessary so that the service processors can communicate and perform the necessary functions for the multiple servers to merge as one combined server or unmerge as separate servers. This connection also is required for out-of-band communication with IBM Director. v All servers in one scalable system must be at the same basic input/output system (BIOS) code level.
Scalable partitions
A scalable partition contains one or more scalable nodes. Regardless of the number of scalable nodes it contains, a scalable partition can run a single image of an operating system. Scalable partitions can: v Be powered on and powered off v Support an operating system v Have a single, contiguous memory space and access to all associated adapters v Identify the scalable nodes that are used by the scalable partition v Be represented as managed systems after IBM Director Agent is installed on the scalable partition and the scalable partition is powered on. You can view the state of a scalable partition from IBM Director Console. To do so, right-click the managed object for a scalable partition; then, click Open to display general attributes for that scalable partition. The scalable partition state is displayed under the general attribute State. Furthermore, when you use the Status association in IBM Director Console, the Scalable Partition Power Status folder in the Group Contents pane includes several subcategories for scalable partition states.
Scalable systems
A scalable system is an IBM Director managed object that consists of scalable nodes and the scalable partitions that were created from the scalable nodes in the scalable system.
40
Attention: If you recable a multinode server into a different physical configuration after it has been used with IBM Director, you must notify IBM Director of the recabling changes by reestablishing out-of-band communication.
Groups that are used with scalable objects

IBM Director provides several default groups of scalable objects in the Groups pane for easier management of these objects. The default groups that are relevant to scalable objects are shown in table below.
Table 7. IBM Director groups that are used with scalable objects Group name Logical Platforms Physical Platforms Platforms Platforms and Platform Members Managed objects All logical-platform objects, which includes all scalable partitions. All physical-platform objects, which includes all scalable nodes. All logical platforms and physical platforms. All logical and physical platforms and any managed systems that result from these platforms. Only scalable partitions. Only scalable systems. All scalable systems and all members of those scalable systems. Members of a scalable system include its scalable partitions, its scalable nodes, and any remote I/O enclosures attached to its scalable nodes. This group also includes managed systems that result from its scalable partitions.
Scalable Partitions Scalable Systems Scalable Systems and Members
Power operations for scalable partitions

You can use IBM Director Console to power on and power off scalable partitions on scalable IBM System x servers. Power operations that are performed on managed objects that represent scalable partitions use out-of-band communication. Power operations that are performed on managed-system objects created from powered-on scalable partitions use in-band communication to power off the scalable partition. Restriction: The out-of-band power operations in IBM Director are only for use by scalable System x servers. IBM Director Console identifies all scalable partitions with the same scalable partition icon whether they are powered on or powered off. However, IBM Director Console uses additional icons with the scalable-partition icon to indicate the state of a scalable partition. IBM Director Console uses the same icon to depict all physical platforms, including those that are not scalable nodes and those that are not in powered-on scalable partitions.
41
Discovering scalable objects

When a scalable node is unlocked, IBM Director performs additional discovery for scalable IBM System x and xSeries servers. This discovery determines whether the NVRAM of the service processor contains a partition descriptor. If it does, IBM Director uses the partition-descriptor information to create scalable systems and scalable partitions. The partition descriptor in NVRAM was stored by the Web management interface for scalable System x and xSeries servers. IBM Director also creates the association between scalable systems and scalable nodes, and between scalable partitions and scalable nodes. The partition descriptor in NVRAM indicates how many scalable nodes are in a scalable system and how many scalable nodes are in a scalable partition. The interrogation of NVRAM to locate a partition descriptor is performed in the background, in a manner similar to the discovery of physical platforms. The following conventions are used to name the new scalable objects: v The scalable system is named Scalable System xxxx where xxxx is the last four characters of the scalable system UUID that is read from NVRAM. v The scalable partition is named Scalable Partition xxxx yyyy where xxxx is the last four characters of the scalable system UUID that is read from NVRAM and yyyy is the last four characters of the scalable partition UUID that is read from NVRAM. Note: When more than one scalable system UUID ends with the same last four characters, this naming convention will result in duplicate names. For this reason, consider renaming automatically created scalable systems to avoid confusion. When IBM Director Server discovers that IBM Director Agent is running on the newly started scalable partition, it creates a managed-system object to represent the active scalable partition. You can use IBM Director to manage this managed system as you would any other managed system. For example, by using Management Processor Assistant (MPA), system administrators can configure, monitor, and manage the service processors in scalable IBM System x and xSeries servers. Further, IBM Director associates the managed-system object with its scalable partition object. Use the Scalable Partitions Membership association in IBM Director Console to view a tree structure of scalable partitions and their associations with any managed systems.
Security
IBM Director offers several security features, including authentication and user-administration options that enable system administrators to specify user privileges, support for Secure Sockets Layer (SSL), and optional encryption of interprocess communication.
Server authentication
A security mechanism by which a managed system can authenticate any management server attempting to access it is integrated into IBM Director. Authentication enables Level-1 and Level-2 managed system to accept commands from only an IBM Director Server that is trusted (that is, authorized to manage it). Authentication protects Level-1 and Level-2 managed system from access by unauthorized management servers or rogue managed-system applications.
42
The IBM Director authentication process is based on two interlocking concepts: v Digital-signature certification v Security state of the managed system Digital-signature certification: IBM Director authentication is based on the Digital Signature Algorithm (DSA). DSA is the public-key algorithm specified by the Digital Signature Standard of the National Institute of Standards and Technology. It enables the holder of a public key to verify the signature for a digital document that has been signed by a holder of the corresponding private key. In an IBM Director environment, digital-signature certification works in the following way: 1. IBM Director Server attempts to access IBM Director Agent. IBM Director Server bids the public keys that correspond to the private keys it holds. 2. IBM Director Agent checks these keys. If it considers the keys to be trusted, IBM Director Agent replies with a challenge that consists of one of the trusted public keys and a random data block. 3. IBM Director Server generates a digital signature of the random data block using the private key that corresponds to the public key included in the challenge. IBM Director Server sends the signature back to IBM Director Agent. 4. IBM Director Agent uses the public key to verify that the signature is a valid signature for the random data block. If the signature is valid, IBM Director Agent grants access to IBM Director Server. This digital-signature scheme has the following benefits: v The public keys stored on the managed systems can be used only for verifying access. v Using a random data block for signing makes replay attacks unusable. v Generating a private key corresponding to a given public key is cryptographically improbable, requiring 2128 or more operations to accomplish. For Level-1 managed systems, the digital-signature certificate expires after 365 days. You can configure notification and polling settings when the certificate is about to expire. You can also create an event action plan to notify you of an expiring certificate. Security states of managed systems: A managed system is in either an unsecured or secured state. A managed system is unsecured when any management server can access it and perform functions on it. A managed system is secured when only an authorized (trusted) management server can access it. The initial security state of IBM Director Agent depends on the underlying operating system.
Table 8. Initial security state of IBM Director Agent Operating system AIX i5/OS Linux Security state Secured by default during installation of IBM Director Agent. Secured by default during installation of IBM Director Agent. Secured by default during installation of IBM Director Agent.
43
Table 8. Initial security state of IBM Director Agent (continued) Operating system NetWare Security state Unsecured by default. Must be secured manually or during discovery. See Securing a managed system manually for more information. Can be secured during installation of IBM Director Agent.
Windows
If IBM Director Agent is not secured during installation of IBM Director Agent, you can secure the managed system manually or during discovery. Note: The IBM Director Agent running on a management server is secured automatically. It has a trust relationship with only the IBM Director Server installed on the same server. On managed systems running Windows, the security state is determined by the secin.ini file. If the secin.ini file is initialized as unsecured, any management server can access the managed system and establish a trust relationship with IBM Director Agent. IBM Director Server establishes a trust relationship by giving IBM Director Agent a copy of its public key. When the managed system has been secured by a management server, only that management server, any management servers that had previously established a trust relationship, and any future management servers that successfully request access are able to access the managed system. Where the security information is stored: The information needed for authentication is stored in files on both the management server and the managed systems. The public keys are stored in dsaxxxxx.pub files, where xxxxx is a unique identifier. The private keys held by IBM Director Server are stored in dsaxxxxx.pvt files. For example, the dsa23ef4.pub file contains the public key corresponding to the private key stored in the dsa23ef4.pvt file. On systems running Windows, the secured or unsecured state data is stored in the secin.ini file, which is generated when you first start IBM Director Server or IBM Director Agent. On management servers, this file is initialized as secured; on managed systems, it is initialized as either secured or unsecured, depending on which options were selected during the installation of IBM Director Agent. By default, the files are located in the following directories.
Operating system AIX i5/OS Directory /opt/ibm/director/data /QIBM/UserData/Director/data
Linux operating systems for AMD64 and 32-bit /opt/ibm/director/data systems Linux operating systems for Intel Itanium and IBM System i, System p, and System z platforms NetWare /opt/ibm/director/data
d:\IBM\Director
44
Operating system Windows
Directory d:\Program Files\IBM\Director\Data
where d is the drive letter of the hard disk on which IBM Director is installed and IBM Director is installed in the default location. How the keys and secin.ini files work together: When you first start IBM Director Server, it randomly generates a matching set of public and private key files (dsa*.pub and dsa*.pvt files). The secin.ini file is generated and initialized as secure. The initial security state of a managed system depends on the following factors: v Which operating system it is running v Which features were selected during the installation of IBM Director Agent Managed systems running NetWare are set to the unsecured state automatically. For all other managed systems, the initial security state depends on which features are selected when IBM Director Agent is installed. If either encryption or agent/server security is selected, the managed system is set automatically to the secured state. While a managed system is in the unsecured state, it accepts a public key from every management server that attempts to access it. Through this process, the managed system establishes trust relationships with those management servers. If a management server secures that unsecured managed system, it gives that managed system a copy of its public key and its secin.ini file, which is initialized as secure. After this has occurred, the managed system no longer accepts any new public keys from management servers. However, the managed system continues to grant access to any management server whose public key is stored on the managed system. How to avoid Request Access: Secured Level-1 and Level-2 managed systems can be pre-configured for granting access to a specific management server. You can use the Request Access window to establish authorization for a management server to access a secured managed system. In the Request Access window you must submit the user ID and password of a user with administrator privileges. After a successful login, the management server deposits credentials on the managed system that facilitate future access without explicitly requesting access. Explicitly requesting access through the IBM Director Console might not be feasible because, for example: v A newly established management server needs to access a large number of managed systems and you want to automate the process. v The security policy at your installation does not permit direct logins by users with administrator privileges. You can circumvent Request Access by setting up the managed system with the appropriate credentials
45
For Level-2 managed systems, copy the management servers public key to the managed system. For Level-1 managed systems, copy a server certificate to the Pegasus truststore directory and import the certificate into the truststore. Key information and management: This topic provides information about public and private keys and how to manage them. The public and private key files are binary files, but they contain textual data that indicates their origin. If a dsa*.pub or dsa*.pvt file is printed using the type command at a command prompt, the following data is displayed in the first line:
DSAKeytypeString
where: v Keytype indicates the type of the key. P denotes private, and p denotes public. v String is the name of the management server that generated the key file. For example, DSAPtest1 indicates a private key file generated by a management server named test1, and DSAptest1 indicates the public key file generated by the same management server. It is very important to back up and protect the dsa*.pvt files. If they are lost, you cannot regenerate these files.
Users and user groups in IBM Director

In IBM Director, users and user groups are based on users and groups defined either for the operating system of the management server or on a Lightweight Directory Access Protocol (LDAP) server. Access to particular managed objects or tasks can be restricted based on the user ID or user group membership. Because IBM Director uses the operating-system or LDAP user accounts, when a user logs in to IBM Director Console, he or she uses the user ID and password that is defined on the operating system or LDAP server. In order for a user to access IBM Director Server, one of the following conditions must be true: v The user is a member of a user group that is authorized for IBM Director Server. v The user has administrator privileges on the Windows management server or Windows domain. v The user is a root user on the AIX, i5/OS, or Linux management server. When IBM Director Server is installed, two user groups are created on the operating system of the management server in order to provide default users for IBM Director. These two groups have administrator and superuser access privileges to IBM Director tasks and managed objects, as described below: administrator group By default, members of the administrator group are authorized to log on to IBM Director, but do not have any authority (privileges and access to tasks and managed objects) in IBM Director. The authority for this group can be modified by a superuser.
46
In addition, authority can be configured individually for members of the administrator group. Members of this group are the only IBM Director users for which authority can be individually configured. The name of the administrator group is different on each supported operating system.
Operating system Name of superuser group AIX or Linux i5/OS Windows diradmin QIBM_QDIR_ADMINISTRATOR DirAdmin Default users None. None. The user account specified during installation.
Note: Root users and Windows administrators have the same authority in IBM Director as members of the administrator group, whether or not the user actually belongs to this group. superuser group Members of the superuser group are authorized with all privileges and have access to all IBM Director managed objects and all tasks, including user and group administration. The authority available to members of the superuser group cannot be restricted. The name of the superuser group is different on each supported operating system.
Operating system Name of superuser group AIX or Linux i5/OS Windows dirsuper QIBM_QDIR_SUPER_ADM_PRIVILEGES DirSuper Default users None. None. The user account specified during installation.
Additional user groups can also be authorized to access IBM Director. These user groups can be granted different levels of authority (privileges and access to tasks and managed objects). With the exception of users who are members of the administrator group, each users authority in IBM Director is defined by the authority granted to the user groups to which the user belongs.
Lightweight Directory Access Protocol authentication in IBM Director

Starting with version 5.20, IBM Director can authenticate user login requests against a Lightweight Directory Access Protocol (LDAP) server. LDAP is an open protocol that uses TCP/IP to provide access to directories that support an X.500 model. For IBM Director user authentication, LDAP has a number of advantages: v Many companies already have existing LDAP directories of employees which can be used for IBM Director user authentication. This saves the time and effort required to create user accounts on the management server. v User access can be immediately modified or terminated on all instances of IBM Director Server by changing the users LDAP group memberships or by removing the users LDAP entry.
47
v Users only need one ID and password, rather than different accounts for each management server. Note: LDAP administrators should note that IBM Director determines group membership using only the members attribute of the group entry. IBM Director ignores other methods of specifying group membership, including attributes (such as memberOf) on user entries.
Encryption
IBM Director contains a security feature that encrypts all data in interprocess communications, except transport-layer datagrams used during discovery. This encryption feature provides automatic key management and enables you to select an encryption algorithm from the provided libraries: v IBM Java Cryptography Extension (JCE) v OpenSSL JCE provides ciphers for all Java-based platforms, including i5/OS and Linux; OpenSSL provides ciphers for 32-bit Windows operating systems. Encryption is disabled by default. To encrypt data transmitted between Level-2 managed systems and IBM Director Server, you must enable encryption on both IBM Director Server and Level-2 managed systems. When you install IBM Director Server, you can select one of the following encryption algorithms: v Advanced Encryption Standard (AES) v Data Encryption Standard (DES) v Triple DES IBM Director Server automatically generates a key, based on the encryption algorithm selected. IBM Director Server stores the key in memory and presents it to IBM Director Server or IBM Director Agent each time IBM Director Server or IBM Director Agent is started, using the Diffie-Hellman key exchange. This makes it unnecessary for a key to be stored on each managed system. The following table outlines how data is transmitted between IBM Director Server and Level-2 managed systems, depending on whether encryption is enabled.
Table 9. Encryption state and data transmitted between IBM Director Server and IBM Director Agent IBM Director Agent (encryption enabled) IBM Director Server (encryption enabled) IBM Director Server (encryption disabled) Encrypted No data transmission possible IBM Director Agent (encryption disabled) Unencrypted Unencrypted
Important: If two management servers have discovered each other (and they each are displayed in each others IBM Director Console as managed nodes), and one management server (server A) has encryption enabled, and the other management server (server B) either has encryption disabled or has encryption enabled now but had it disabled when it was discovered and the communication has not ended since the discovery, then unencrypted transmissions sent by server B to server A
48
will continue until the previous communication is ended. This occurs because server A (in its role as a management server) is already communicating with server B (in its role as managed system) in plain text. You can delete these managed objects from each others console to end the unencrypted communication, and if you run multiple management servers that can discover each other, you can enable encryption on both management servers before they are started or before they can discover each other. You can also use the dircli lsmo command to check for previous communication. Notes: v Encryption is not supported on managed systems running NetWare or systems running 64-bit versions of Windows. v Neither out-of-band communications nor communication used by Internet tools, such as Telnet or File Transfer Protocol (FTP), are encrypted. v Enabling encryption imposes a performance penalty. Encrypting data packets and exchanging encryption keys has an effect on the speed with which IBM Director completes management operations. When either the management server or the managed systems are restarted, keys are regenerated and exchanged. Consequently, an unsecured managed system might seem to be unmanageable for a period of time.
Service processors
Hardware-based service processors, also known as management processors, work with hardware instrumentation and systems management software and are key to problem notification and resolution and allow you to remotely manage your system. In an IBM Director environment, service processors send alerts IBM Director Server when error conditions occur in a specific managed system and are key in helping you effectively managed your environment.
Communication with IBM Director Server

This topic provides information about the pathways on which data is transmitted between service processors and IBM Director Server. There are several pathways along which communication between IBM Director Server and the service processors present in scalable System x and xSeries servers takes place: In-band communication IBM Director Server communicates with IBM Director Agent; IBM Director Agent uses a device driver to pass data to and from the service processor. This also is called interprocess communication (IPC). Over the local area network (LAN) Data is transmitted between the service processor and IBM Director Server over the LAN. This is possible if the service processor has an integrated network interface card (NIC) or access to a NIC shared with the server. Over the ASM interconnect Data is passed from the service processor over an ASM interconnect network to a second service processor. The second service processor serves as a gateway between IBM Director Server and the first service processor. Both of the latter types of communication are known as out-of-band communication, because they take place independent of an operating system.
49
An ASM interconnect network is a group of service processors that are networked together using the ASM interconnect feature. Connected through the RS-485 ports, the service processors can communicate with and send alerts out-of-band to IBM Director Server through a gateway service processor (sometimes called an ASM interconnect gateway). An ASM interconnect network eliminates the need for multiple modems, telephones, and LAN ports; it also permits service processors without network interface cards to communicate out-of-band with IBM Director Server. Notes: 1. For IBM Director to communicate out-of-band, the following conditions must be met: v Service processors must maintain consistent IP addresses. You either must assign static IP addresses or configure Dynamic Host Configuration Protocol (DHCP) to maintain consistent IP addresses for the service processors. v The service processor IP addresses cannot change after IBM Director has discovered the server. 2. Only one of the following systems management applications can communicate with a service processor at any given time: v IBM Director Server v IBM Management Processor Command-Line Interface (MPCLI)
In-band communication and alerts

This topic provides information about in-band communication and the sending of alerts to IBM Director Server by service processors. Whether a service processor can communicate in-band with IBM Director Server depends on both the type of service processor and the operating system running on the managed system.
Table 10. In-band communication between service processors and IBM Director Server Operating system Primary service processor Advanced System Management PCI Adapter (ASM PCI Adapter) Advanced System Management processor (ASM processor) Integrated system management processor (ISMP) IPMI baseboard management processor Remote Supervisor Adapter Remote Supervisor Adapter II
1
Linux Yes Yes Yes Yes Yes Yes
NetWare Yes Yes No No Yes Yes

1
Windows Yes Yes Yes Yes Yes Yes
Novell NetWare 6.5 only
In addition, to enable in-band alerts between IBM Director Server and a managed system that contains a service processor, both the service-processor device driver and MPA Agent or System Health Monitoring must be installed on the managed system. MPA Agent is installed by default with the IBM Director Agent installation on the Linux operating system.
50
When in-band alerts are possible, alerts are handled either by MPA Agent or System Health Monitoring. Unless the server supports System Health Monitoring, ISMPs in servers running Linux cannot send in-band alerts. The following table specifies which IBM Director Agent feature handles in-band alerting.
Table 11. IBM Director Agent features that handle in-band alerts Operating system running on managed system Type of service processor ASM PCI Adapter ASM processor ISMP Linux System Health Monitoring System Health Monitoring None or System Health Monitoring1 System Health Monitoring System Health Monitoring2 NetWare Not applicable Not applicable Not applicable Windows System Health Monitoring System Health Monitoring System Health Monitoring System Health Monitoring System Health Monitoring System Health Monitoring
IPMI baseboard management controller Remote Supervisor Adapter
Not applicable Not applicable MPA Agent
Remote Supervisor Adapter II System Health Monitoring

1
If System Health Monitoring is supported on the server.
See the IBM Director Hardware and Software Support Guide document for a list of servers on which System Health Monitoring is supported when the server is running Linux. This PDF file is updated every six to eight weeks. You can download it from the IBM Director Web site at www.ibm.com/systems/ management/director/.
Out-of-band communication and alerts

This topic provides information about when service processors can communicate out-of-band with IBM Director Server. It also contains information about the pathways on which service processors can provide out-of-band alerts to IBM Director Server. The type of service processor present in a server determines which paths out-of-band communication can take. Servers that contain ISMPs can communicate out-of-band with IBM Director Server only through a gateway service processor. The following service processors all can serve as gateway service processors: v ASM PCI Adapter v ASM processor v Remote Supervisor Adapter v Remote Supervisor Adapter II However, some of these service processors cannot communicate with certain other service processors. In addition, an ASM processor can communicate with IBM Director Server only through interprocess communication. The following table details the possible gateway service processors and the types of service processors located on an ASM interconnect network with which they can
51
communicate.
Table 12. Gateway service processors and communication with service processors on an ASM interconnect network Service processor on an ASM interconnect Gateway service processor ASM PCI adapter ASM processor Remote Supervisor Adapter Remote Supervisor Adapter II ASM PCI adapter Yes Yes Yes IPMI baseboard management controller Not applicable Not applicable Not applicable Not applicable Remote Supervisor Adapter No No Yes Remote Supervisor Adapter II No No Yes
ASM processor Yes Yes Yes
ISMP No No Yes
Yes
Yes
Yes
Yes
Yes
To maximize the possibility of IBM Director Server receiving alerts from service processors located on an ASM interconnect network, consider using a Remote Supervisor Adapter or a Remote Supervisor Adapter II as a gateway service processor. Note: Not all scalable IBM System x and xSeries systems are supported with the RXE-100 Remote Expansion Enclosure. If you have one of the following servers attached to an RXE-100 Remote Expansion Enclosure, you cannot use the on-board Remote Supervisor Adapter as a gateway service processor: v xSeries 360 v xSeries 365 v xSeries 440 v xSeries 445 v xSeries 455 The Remote Supervisor Adapter is dedicated to managing the RXE-100 Remote Expansion Enclosure. The following table contains information about the pathways available for out-of-band alerting.
Table 13. Out-of-band alerting pathways Type of service processor ASM PCI adapter Pathways for out-of-band alerting v LAN v Over an ASM interconnect v Over an ASM interconnect Possible gateway service processors v ASM PCI adapter v Remote Supervisor Adapter v Remote Supervisor Adapter II v ASM PCI adapter v Remote Supervisor Adapter v Remote Supervisor Adapter II v Remote Supervisor Adapter v Remote Supervisor Adapter II
ASM processor
ISMP
v Over an ASM interconnect
52
Table 13. Out-of-band alerting pathways (continued) Type of service processor IPMI baseboard management processor Pathways for out-of-band alerting v LAN Possible gateway service processors v Not applicable
Remote Supervisor v LAN Adapter v Over an ASM interconnect Remote Supervisor v LAN Adapter II v Over an ASM interconnect
v Remote Supervisor Adapter v Remote Supervisor Adapter II v Remote Supervisor Adapter v Remote Supervisor Adapter II
See the documentation that came with the server for information about how to configure your service processor and ASM interconnect to ensure that IBM Director Server receives alerts.
Out-of-band alert-forwarding strategies

This topic provides information about the out-of-band alert-forwarding strategies that are supported by System x and xSeries service processors. The type of service processor also determines what type of alert-forwarding strategy is possible. The following table contains information about possible alert-forwarding strategies.
Table 14. Out-of-band alert-forwarding strategies Type of service processor ASM PCI adapter ASM processor ISMP IPMI baseboard management controller Remote Supervisor Adapter Remote Supervisor Adapter II Possible alert-forwarding strategies IBM Director over LAN IBM Director over LAN Not applicable IBM Director comprehensive IBM Director and IBM Director comprehensive IBM Director comprehensive
Some service processors also support SNMP as an alert-forwarding strategy.
Service processors and managed-object types

Any System x server and BladeCenter unit that has a supported service processor or management module can forward events to IBM Director Server. When IBM Director Server generates event types in response to an event, the target managed object of the specific event type can vary. The following table lists the service processor type and it associated target managed-object type. Note: For all service processors, if IBM Director cannot determine the managed object type for a service processor notification, IBM Director instead will identify the source of the notification by the IP address of the service processor that sent the notification to IBM Director Server. An example of this is a managed system that is configured to send notifications to IBM Director Server, but IBM Director Server currently doesnt have a managed object representing that system.
53
Service processor type BladeCenter management module RXE-100 Remote Expansion Enclosure
Target managed-object type BladeCenter chassis RIOEnclosure
System with one of the following service Physical Platform and associated IBM processors: Director System v ISMP v Remote Supervisor Adapter v Remote Supervisor Adapter II v Advanced System Management processor (ASM processor) v Advanced System Management PCI adapter (ASM PCI adapter) System running the MPA Agent with one of Physical Platform and associated IBM the following service processors: Director System v ASM processor v ASM PCI adapter
Note: IBM Director cannot map events that are generated by ASM processors and ASM PCI adapters to a managed object unless the MPA Agent 4.22 or earlier is installed. The MPA agent is a feature of the IBM Director Agent, version 4.22 or earlier, installation.
SNMP devices
IBM Director discovers SNMP devices in your network according to discovery parameters that you can specify. The process that is used to discover SNMP devices in your network uses lists of initial IP addresses, SNMPv1 and SNMPv2c community names, subnet masks, and SNMPv3 profiles. IBM Director works with SNMPv1, SNMPv2c, and SNMPv3 for all communications and recognizes Management Information Bases (MIBs) in System Management Information (SMI) version 1 and version 2 formats. SNMPv1 and SNMPv2c devices and agents use community names to control their access. A community name can be any case-sensitive text string. By default, the community name of an SNMP device is set to public. If specific SNMP devices in your network have unique community names to restrict access, you can specify the correct name to gain access to a device. SNMPv3 devices and agents use profiles to control their access. The subnet mask enables you to further refine the scope of the discovery process, limiting the search to certain subnets in the network. The default subnet mask is set to the subnet of each corresponding IP address. Using your lists of IP addresses, community names, and subnet masks, a series of SNMP GET statements are performed against port 161 of the IP address to determine whether the address is associated with a valid SNMP device. A valid SNMP device for IBM Director has the following accessible values: sysName, sysObjectID, sysLocation, sysContact, sysDescr, and sysUpTime. If the object is determined to be a valid SNMP device, another series of SNMP GET statements are sent to obtain information in the ipNetToMediaNetAddress table, where additional IP addresses can be used to discover even more SNMP devices. The search continues until no new addresses are located. Newly discovered or created
54
SNMP-device managed-object names default to the value of sysName. If sysName has no value, the host name of the device is used. If no host name is assigned, the IP address is used. All SNMP traps that are configured with IBM Director Server as the destination are forwarded as events to the event log. Therefore, you can view an SNMP trap using the event log on the SNMP managed device that originated the trap. If a trap is received that corresponds to an SNMP device that has not been discovered, IBM Director creates the device automatically, if you selected the Auto-add unknown agents which contact server check box on the SNMP Discovery page in the Discovery Preferences window. The MIB file is used to translate raw SNMP dotted-decimal notation into human-readable text. This is especially useful for SNMP devices, such as network hubs, switches, printers, and unit power systems (UPSs). MIBs that are placed in the data\snmp directory on the management server are compiled automatically when the management server is started or restarted. You can also compile MIBs manually from the SNMP Browser window.
Software distribution
This topic compares two methods for distributing software. IBM Director supports the following methods of software distribution: v Streaming from the management server v Using redirected distribution
Streaming from the management server

This topic describes advantages and disadvantages of distributing software by streaming from the management server. When you distribute software by streaming, software-distribution packages are copied directly from the management server to the managed system. This method of software distribution is resource-intensive. It can have a negative effect on the management server performance. In addition, a package distributed by this method requires that the target managed system have empty disk space twice the size of the package. For Level-2 managed systems, streaming from the management server has one advantage, however. If a network connection is broken during the transmission, IBM Director attempts to resume the connection from the point at which the transmission was interrupted. If the streaming operation can be resumed, retransmission time is saved. Because of the ability to resume distribution, you might prefer to stream a software package from the management server if you have an unreliable or slow network link.
Using redirected distribution

This topic describes advantages and disadvantages of using redirected distribution to distribute software. When you distribute software using redirected distribution, you set up a universal naming convention (UNC) or an FTP share on a network server. IBM Director Server streams software packages to the network share, where they are cached. From the share, they are either streamed to the managed systems or, in the case of
55
software that uses the Microsoft Windows Installer (MSI) or InstallShield as the installation utility, installed directly from the file-distribution server. Because many software packages are hundreds of megabytes in size, distributing software across a large network can cause bottlenecks in network data transmission. Redirected distribution greatly reduces the software-distribution traffic in your network. It uses fewer system resources on the management-server. In addition, if you install InstallShield or MSI packages directly from the file-distribution server, redirected distribution requires less disk space on the managed systems. Redirected distribution has one limitation: if a redirected distribution of a software package is interrupted (for example, if the network connection is lost), the installation must begin again.
File-distribution server considerations

Consider the following issues when setting up file-distribution shares: v In a Windows environment, the file-distribution server must either be a member of the same domain as the management server or have a trust relationship with that domain. v The management server must have full read/write access to the share. The user ID and password that were used to install IBM Director Server must also be present on the file-distribution server. Otherwise, software distribution uses streaming from the management server. v The share must allow read access to all managed systems that you want to access the share. v If the file-distribution server is configured as an FTP server, you can choose to use FTP when transferring packages from the management server to the share. For managed systems running Windows, the home directory for the FTP login must be the same directory as the file-distribution server. For example, if c:\stuff\swd_share is mapped to \\server\swd_share, then c:\stuff\swd_share must be the home directory for the FTP user ID login used on the FTP file-distribution server configuration panel. v You can enable null credentials to access the share so that you do not have to specify a user ID and password for each managed system or group that needs to access the share. To enable null credentials, you must issue the twgshare command. This command alters a registry setting on the file-distribution server, which enables managed systems to use null credentials to access the share. To issue the twgshare command, complete the following steps: 1. Copy the twgshare.exe file to the file-distribution server. This file is in the \IBM\director\bin\ directory. 2. From a command prompt, type the following command:
twgshare -a sharename
where sharename is the name of the share on the file-distribution server. v If you do not want to use null credentials (which are a security risk), you must set up an operating-system account on the file-distribution server. This account must have read access to the share. Enter the user ID and password for this account when you configure distribution preferences for managed systems. In addition, the account must exist on each managed system so that IBM Director Agent can specify this user to mount the share.
56
Storage managed objects

IBM Director recognizes certain storage devices that comply with the Storage Management Initiative Specification (SMI-S). This is an industry standard developed by the Storage Networking Industry Association (SNIA). IBM Director supports SMI-S versions 1.1 and 1.0.2. IBM Director communicates with the storage devices through their respective SMI-S providers. Their Service Location Protocol (SLPv2) component enables the devices to be discovered by IBM Director, which looks for SNIA-defined SLP service types. IBM Director obtains information about storage devices through the SMI-S providers Common Information Model Object Manager (CIMOM) component. Communication occurs using the Distributed Management Task Force (DMTF) standard for Web Based Enterprise Management (WBEM) as required by SNIA. The information is organized according to the DMTF standard for the Common Information Model (CIM) using the profiles defined by SNIA. For information about standards, see these Web sites: SMI-S www.snia.org/smi/about SNIA www.snia.org DMTF www.dmtf.org WBEM www.dmtf.org/standards/wbem CIM www.dmtf.org/standards/cim
SMI-S attributes
SMI-S attributes can include four sets of data values: Default, CIMOM, Base and Extended.
Default attributes
SMI-S storage managed objects are displayed on the console immediately after being discovered through SLPv2 as a locked object labeled by the host name (or IP address if DNS lookup fails). When the storage managed objects object is locked, only the public data surfaced through SLPv2 is available (such as a locked object that represents the CIMOM required by the SMI-S standard). Default attributes that are common to when IBM Director managed objects are displayed. These attributes include: System Name Initially, the primary host name or IP address of the CIMOM. After it is unlocked, System Name becomes the generated name for the device. System Factory ID The managed object factory that creates the objects for the devices. System State The state of the object. Initially, the system state is unknown because access is required to determine the actual state (online, error or offline). System Presence Check Setting The polling interval in minutes that is used to check the status.
57
Secure/Unsecure supported A flag that specifies whether securing of the target is supported. Access Denied A flag that specifies whether access is denied. The value of this attribute is true for a locked object. This attribute is no longer displayed after the object is unlocked. Encryption Enabled A flag that specifies whether encryption to the target is enabled.
CIMOM attributes
Until the storage managed object is unlocked, the actual device and its associated data are unavailable. The storage managed object is unlocked by obtaining access to represent the CIMOM and the CIM schemas minded for data. The SLP provided CIMOM attributes includes: SMI-S Provider Service ID The unique service ID of the CIMOM. As specified in SMI-S, responses from different IP addresses with the same Service ID value are assumed to be the same CIMOM and are collapsed together. Interop Namespace The entry namespace in CIM containing the Server profile that has the CIMOM data and list of registered profiles. Registered Profiles Supported The list of profiles this CIMOM claims to support. SLP Service Names The full service names for this CIMOM SMI-S Provider IP Addresses The list of one or more IP addresses for the CIMOM. SMI-S Provider IP Port Numbers The IP ports on this CIMOM.
Base attributes
After access is granted to the storage managed object, the full CIM data can be obtained. When the full CIM data is obtained, the device representation might going away successfully because the entity already exists, the object access might fail, or a security problem might occur. If access is successful, the object becomes a representation of an actual device. The name changes based on the rules specified in the Discovery Preferences panel for SMI-S storage devices. The following base attributes are then displayed: Registered Profile The profile that this device represents along with the version (for example, SNIA:Array 1.0.2). Namespace The namespace with the schema details about this particular profile. Manufacturer ID The manufacturer of this device. Type and Model The type and model string representing this device.
58
Serial Number The serial number for the device. Endpoint Unique Name The unique name that identifies the primary fibre channel port in fibre channel for the device. Storage Attached Protocol The protocol of the device, either fibre channel or iSCSI device.
Extended attributes
Any extended attributes that are specified by the attribute extension files are created. These may vary based on the storage managed object. For example, for an IBM DS4000 disk array, the following attributes are displayed: Subscriptions Indicates whether a managed object is registered to receive state or alert indications. Nickname A name for the device Controller IP Addresses IP addresses for the controllers on the target.
External applications for storage managed objects

You can use IBM Director to start external applications for targeted storage managed objects, including Storage Manager Client for IBM System Storage DS4000 storage systems series. Important: You must install Storage Manager Client on each management console from which you intend to use it. Before you can start Storage Manager Client from IBM Director Console on systems running a Windows operating system, you must set the following environment variable: STORAGE_MANAGER Defines the working directory of Storage Manager Client. The default directory is c:\Program Files\IBM_FAStT\client.
Groups used with storage managed objects

IBM Director provides several default groups of storage managed objects in the Groups pane for easier management of these objects. This table lists the groups that support storage managed objects.
Group name SMIS-Storage Devices Storage Devices Systems with Fibre Channel Ports Storage managed objects Only storage managed objects that comply with the SMI-S standard. All storage managed objects, regardless of compliance with SMI-S standards. All disk arrays, switches and servers that have Fibre Channel connectivity.
59
Update Manager
This topic provides information about the Update Manager task in IBM Director. Update Manager uses profiles to provide the following core capabilities for managing System x and IBM BladeCenter firmware and driver updates: v Acquiring updates automatically at scheduled intervals into the updates library v Checking the health of system software and reporting system status v Creating software-distribution packages containing updates from the updates library v Deploying updates in Software Distribution packages to remote System x and IBM BladeCenter models and groups of systems Some BladeCenter updates can be distributed over an out-of-band path through the chassis management module without requiring that the blade is even powered on. This distribution method has no requirements on the operating system or installed applications on the BladeCenter component. The following figure illustrates the process of acquiring updates, storing the updates in the updates library, and deploying necessary updates to systems that are found to be out-of-date during a system health check.
IBM support and third-party service providers
1 Acquires updates
2 Checks server health
Updates library
IBM Director Server
3 Deploys updates if needed
IBM Director Console: Update Manager task

Figure 3. Managing system updates in an IBM Director environment
Update Manager profile

Update Manager uses profiles to manage system updates. Profiles can be created for individual updates, or for update bundles. You use profiles to specify criteria that determine which updates are downloaded to your updates library. Using profiles, you can also determine which systems in your IBM Director environment are out-of-date and require updated system software.
60
Criteria for both types of update profiles include machine type and operating system combination. Individual update profile criteria can be further narrowed by selecting severity levels or update categories (for example, BIOS firmware updates) to include. If you want to receive individual updates, you can select multiple machine type and operating system combinations in one profile, or use a unique profile for each combination. Profiles for update bundles will search for UpdateXpress System Packs that match a single machine type and operating system pair. Only one update bundle can be included in an update bundle profile.
UpdateXpress System Pack

An UpdateXpress System Pack is an integration-tested bundle of online firmware and driver updates for IBM System x and IBM BladeCenter servers. UpdateXpress System Packs simplify the downloading and installation of all online driver and firmware updates for a given system, ensuring that you are always working with a complete, current set of updates that have been tested together and bundled by IBM. A single click downloads the entire update bundle, along with a readme file and a complete change history, if available. UpdateXpress System Packs are created for a machine type and operating system combination. Separate UpdateXpress System Packs are provided for Windows and each of the Linux distributions. For example, there could be several UpdateXpress System Packs for one particular machine type. There might be one for Windows, and then one for each Linux distribution. UpdateXpress System Packs are generally released on a quarterly basis, but if there are critical updates for a system, an UpdateXpress System Pack will be released as soon as possible. You can use the IBM Director Update Manager and Scheduler tasks to automatically download UpdateXpress System Packs for a particular machine type and operating system combination.
Upward integration
IBM Director Upward Integration Modules (UIMs) and Management Packs enable third-party workgroup and enterprise systems-management products to interpret and display data that is provided by Level-1 and Level-2 managed systems. IBM Director UIMs and Management Packs provide enhancements to the systems-management products that you can use to collect inventory data, view IBM Director event notifications, and for some UIMs, distribute IBM Director managed system software packages. With the IBM Director UIMs and Management Packs, you can use your systems-management software to manage systems that have IBM Director Core Services or IBM Director Agent software installed on them. Note: The IBM Director UIM, however, provides only Level-1 management functionality for the managed system. You can use IBM Director Core Services software to: v Gather detailed inventory information about your systems, including operating system, memory, network adapters, and hardware. v Track your systems with features such as power management, event log, and system monitor capabilities. IBM Director Core Services uses some of the latest systems-management standards, including Common Information Model (CIM), Web-Based Enterprise Management
61
(WEBM) and Extensible Markup Language (XML), to provide compatibility with your existing enterprise-management software. IBM Director enables you to make the most of your existing enterprise management structure by upwardly integrating with Tivoli Management Framework, Tivoli NetView, HP OpenView, Microsoft Systems Management Server, and Microsoft Operations Manager 2005.
IBM Director UIM for HP OpenView NNM

With the IBM Director UIM for HP OpenView NNM (Network Node Manager), you can use your systems-management software to manage systems that have IBM Director Core Services or IBM Director Agent installed on them. Note: The IBM Director UIM, however, provides only Level-1 management functionality for the managed system. When you install IBM Director UIM for HP OpenView NNM, the following functions are added to the HP OpenView NNM environment: v Event notification: Provides notification of events that occur on managed systems on which IBM Director Core Services is installed. These notifications are delivered using SNMP traps. v Inventory: Scans inventory using an inventory plug-in that starts a Java application to collect inventory from IBM Director Core Services, including Asset ID data, BIOS details, and lease information. Inventory data varies depending on the type of system (IBM Director System i,System p, and System x). v Discovery: Provides SNMP-based discovery of managed systems on which IBM Director Core Services is installed. Tip: You must configure the SNMP community name of the managed systems. For System x, this is done using the snmpd.conf file. For System p, you also need to configure the snmpdv3.conf file. Note: These functions are supported on IBM Director System i,System p, and System x platforms.
IBM Director Management Pack for Microsoft Operations Manager 2005

With the IBM Director Management Pack for Microsoft Operations Manager 2005, you can use your systems-management software to manage systems installed with Level-1: IBM Director Core Services or Level-2: IBM Director Agent. When you install IBM Director Management Pack for Microsoft Operations Manager 2005, the following functions are added to the Microsoft Operations Manager 2005 environment: v Discovery: Provides discovery of Level-1 and Level-2 managed systems. v Events: Captures events that occur on Level-1 and Level-2 managed systems. v Alerts: Sends a notification when certain events occur on Level-1 and Level-2 managed systems. v State: Changes the state of Level-1 and Level-2 managed systems based on event criteria. Note: These functions are supported on System x systems running Windows. They are not supported on System i, System p, and System z systems.
62
IBM Director UIM for Microsoft Systems Management Server 2003

With the IBM Director UIM for Microsoft Systems Management Server 2003, you can use your systems-management software to manage systems installed with IBM Director Core Services or IBM Director Agent software. When you install IBM Director UIM for Microsoft Systems Management Server 2003, the following functions are added to the SMS 2003 environment: v Event notification: Provides notification of events that occur on managed systems on which IBM Director Core Services is installed. These notifications are translated into SMS status messages. v Collections: Adds an SMS Collection to easily identify all managed systems on which IBM Director Core Services is installed. v Inventory: Scans inventory directly from IBM Director Core Services, including Asset ID data, BIOS details, field-replaceable unit (FRU) numbers, lease information, and network details. Tip: The inventory feature is compatible with only IBM Director Agent or IBM Director Core Services 5.10 or later. v Queries: Adds an SMS Query to identify all managed systems on which IBM Director Core Services is installed. v Software distribution: Distributes an IBM Director software package and performs an unattended installation on any system in the Microsoft SMS environment. v Wake on LAN: Remotely turns on managed systems on which IBM Director Core Services is installed, and are Wake-on-LAN-capable. Note: These functions are supported on System x platforms that are running Windows. They are not supported on System i, System p, and System z systems.
IBM Director UIM for Tivoli Management Framework

With the IBM Director UIM for Tivoli Management Framework, you can use your system-management software to manage systems installed with IBM Director Core Services or IBM Director Agent software. When you install IBM Director UIM for Tivoli Management Framework, the following functions are added to the Tivoli Management Framework environment: v Event notification: Provides notification of events (such as failing components) occurring on IBM Director Agent systems and IBM Management Processors, allowing information technology (IT) personnel to take immediate corrective action. These notifications can be sent as native Tivoli Enterprise Console events, SNMP traps, and Windows event-log events. v Inventory: Collects inventory data directly from managed systems on which IBM Director Agent is installed using custom MIF files, SQL scripts, and inventory queries. v Monitors: Provides hardware status monitors for managed systems on which IBM Director Agent is installed. This function provides more comprehensive hardware-monitoring capabilities than the Tivoli Console interface. v Software distribution: Enables you to build and distribute update packages for IBM Director Agent software and perform an unattended installation of these packages on any Tivoli endpoint running Microsoft Windows or Linux. Note: Software distribution is not supported for System p managed systems.
63
v Tasks: Allows you to view additional information and restart or shut down managed systems on which IBM Director Agent is installed. Note: These functions are supported on System x, System p systems. Only inventory and event notification are supported on System i platforms. Only event notification is supported on System z systems.
IBM Director UIM for Tivoli NetView

With the IBM Director UIM for Tivoli NetView, you can use your systems-management software to manage systems that have IBM Director Core Services or IBM Director Agent software installed on them. Note: The IBM Director UIM, however, provides only Level-1 management functionality for the managed system. When you install IBM Director UIM for Tivoli NetView, the following functions are added to the Tivoli NetView environment: v Event notification: Provides notification of events (such as failing components) occurring on IBM Director Core Services systems and IBM Management Processors, allowing IT personnel to take immediate corrective action. Notifications are delivered through SNMP traps. v Inventory: Collects the inventory data from IBM Director Core Services, including Asset ID data, BIOS details, FRU service numbers, lease information, and network details. v Web browser launch: Provides Web-browser capability from within the NetView environment that allows you to view and manage real-time asset and health information about managed systems on which IBM Director Core Services is installed. v Discovery: Automatically finds systems with IBM Director Core Services installed, using SNMP. From NetView, you can identify IBM Director managed systems at a glance. Note: You must configure the SNMP community name of the managed system. Note: These functions are supported on System x platforms. Only event notification is supported on System i platforms. These functions are not supported on System p and System z systems.
User interfaces
There are two methods for managing an IBM Director environment: a graphical user interface, called the IBM Director Console, and a command-line interface (dircli).

The IBM Director Console allows you to control and monitor managed systems and devices from an application-based graphical user interface. You can install this console on a desktop computer, workstation, or mobile compute that exists on the same network as the management server.
IBM Director command-line interfaces

You can use the IBM Director the command-line interfaces to manage and monitor the managed objects and devices.
64
You can use the administrative command-line interface interactively using the dircli or dircmd utilities. This administrative command-line interface is an important primary interface into IBM Director and may be used either as an efficient way to accomplish simple tasks directly or as an embeddable and scriptable framework for achieving higher level goals. For security reasons, administrative command-line interface runs only on the management server. Note: The IBM Director dircli supports a subset of the commands that were available previously through the deprecated dircmd utility. To access dircli or dircmd you must log in to an management server as an IBM Director superuser. Access to dircli and interfaces is limited to IBM Director superusers (members of the DirSuper group). By default, the connection between the CLI client and the management server is a nonsecure TCP/IP data link. You can use Secure Sockets Layer (SSL) to secure the data transmission.
65
66
Chapter 2. Planning
Before installing or updating IBM Director, review the installation requirements and plan your installation.
Specified operating environments

IBM Director has specific requirements for hardware and networks. IBM Director provides support for a wide range of hardware products, operating systems, and database applications.
Hardware requirements for IBM Director

To successfully install IBM Director, the system on which you install IBM Director components must meet certain minimum hardware requirements, depending on the components to be installed and the type of system on which they will be installed. Because a system configured with the minimum requirements might perform poorly in a production environment, consider the following suggestions: v Be sure that your system can accommodate the hardware requirements, keeping in mind that the microprocessor speed, memory, and disk-space minimum requirements are additional to the resources are necessary for the software already installed on the system. v Conduct a performance analysis to ensure that the system has sufficient capacity to handle the additional requirements of functioning as a management server or a management console.
Hardware requirements for x86-compatible systems

IBM Director components have minimum microprocessor speed, random access memory (RAM), and disk space requirements on x86-compatible systems, including System i platforms, IntelliStation workstations, NetVista desktop computers, IBM ThinkCentre desktop computers, ThinkPad mobile computers, IBM System Storage Network Attached Storage (NAS) products, and IBM SurePOS point-of-sale systems. When reviewing the hardware requirements, consider the following information: v The disk space listed is the minimum requirement for an installation using the default selections. v Requirements listed for IBM Director Server do not include the database program hardware requirements or the increased persistent storage for managed objects. v The systems on which you install IBM Director Agent or IBM Director Server must meet the Wired for Management (WfM), version 2.0, specifications. v System Management BIOS (SMBIOS) 2.1 or later is required for all systems in an IBM Director environment.
67
Table 15. x86-compatible systems: Minimum hardware requirements Requirements Microprocessor speed Memory (RAM) IBM Director Core Services Pentium-class processor 128 MB IBM Director Agent Pentium-class or Itanium 2 processor 128 MB IBM Director Console Pentium 1.5 GHz 256 MB
IBM Director Server Pentium 1.5 GHz 512 MB (minimum) 1024 MB (recommended)
Disk space
40 MB (for Windows) 100 MB (for Linux)
110 MB (for Windows) 170 MB 165 MB (for Linux) Not applicable At least 256 colors
325 MB
Display
Not applicable
At least 256 colors
Hardware requirements for servers running AIX

IBM Director components have minimum microprocessor speed, random access memory (RAM), and disk space requirements on servers running AIX, including System i and System p servers, and JS20 and JS21 blade servers. When reviewing the hardware requirements, consider the following information: v The disk space listed is the minimum requirement for an installation using the default selections. v Requirements listed for IBM Director Server do not include the database program hardware requirements or the increased persistent storage for managed objects. v On systems that do not provide display capability, such as JS20 and JS21 blade servers, you must export IBM Director Console using either the xhost command or SSH tunneling. The IBM Director Console requirements apply to the receiving system.
Table 16. Servers running AIX: Minimum hardware requirements Requirements Microprocessor speed Memory (RAM) IBM Director Agent Power4, Power5, or Power6 1.5 GHz 512 MB (minimum) IBM Director Console Power4, Power5, or or Power6 1.5 GHz 512 MB (minimum) IBM Director Server Power4, Power5, or Power6 1.5 GHz 512 MB (minimum) 1024 MB (recommended) Disk space 90 MB (/opt) 3 MB (/usr) 185 MB (/opt) (Includes the disk space required for IBM Director Agent.) 6 MB (/usr) Display Not applicable At least 256 colors At least 256 colors 325 MB (/opt) 8 MB (/usr)
Hardware requirements for servers running Linux on POWER

IBM Director components have minimum microprocessor speed, random access memory (RAM), and disk space requirements on servers running Linux on POWER, including System i and System p servers, and JS20 and JS21 blade servers. When reviewing the hardware requirements, consider the following information:
68
v The disk space listed is the minimum requirement for an installation using the default selections. v Requirements listed for IBM Director Server do not include the database program hardware requirements or the increased persistent storage for managed objects. v On systems that do not provide display capability, such as JS20 and JS21 blade servers, you must export IBM Director Console using either the xhost command or SSH. The IBM Director Console requirements apply to the receiving system.
Table 17. Servers running Linux on POWER: Minimum hardware requirements Requirements Microprocessor speed Memory (RAM) IBM Director Core Services Power4, Power5, or Power6 1.5 GHz 128 MB (minimum) IBM Director Agent Power4, Power5, or Power6 1.5 GHz 512 MB (minimum) IBM Director Console IBM Director Server Power4 or Power5 1.5 GHz 512 MB (minimum) Power4 or Power5 1.5 GHz 512 MB (minimum) 1024 MB (recommended) Disk space Display 100 MB Not applicable 170 MB Not applicable 225 MB At least 256 colors 425 MB At least 256 colors
Hardware requirements for System i products

IBM Director components have minimum commercial processing workload (CPW), storage pool size, and disk space requirements when installed on System i products. When reviewing the hardware requirements, consider the following information: v The disk space listed is the minimum requirement for an installation using the default selections. v Requirements listed for IBM Director Server do not include the database program hardware requirements or the increased persistent storage for managed objects. As the number of managed objects in your IBM Director environment increases, make sure you increase disk space and storage pool size on the system running IBM Director Server. v Resource Monitors, tasks, event action plans, and managed endpoints increase the resources required by IBM Director Server.
Table 18. System i products: Minimum hardware requirements Requirements Relative system performance Storage pool size Disk space IBM Director Agent 75 CPW 350 MB 300 MB IBM Director Server 150 CPW 500 MB 500 MB
Note: IBM Director Server is a Java application. Java applications that are run on heavily loaded systems might require a separate storage pool. Sections 4.3.2 and 4.3.3 of the IBM Redbooks publication Java and WebSphere Performance on IBM iSeries Servers (SG24-6256) provide information about how to create a separate memory pool.
Hardware requirements for IBM System z servers

IBM Director components have minimum microprocessor speed, random access memory (RAM), and disk space requirements.
Chapter 2. Planning
69
The following System z servers are supported: v IBM System z9 (all models) v IBM zSeries (all models) v IBM S/390 (Multiprise 3, Generation 5 and Generation 6)
Table 19. Minimum hardware requirements for IBM Director on System z servers IBM Director Server (with or without CIM instrumentation for z/VM manageability access IBM Director point) Console IBM Director Agent with CIM instrumentation for z/VM manageability access point
Requirement Processor speed Memory Disk space Display
IBM Director Agent
All processor speeds provided by IBM System z servers are sufficient for IBM Director. 1 GB 316 MB Not applicable 512 MB 168 MB At least 256 colors 512 MB 139 MB Not applicable 512 MB 215 MB Not applicable
The additional resources you require for the systems you want to provision with z/VM Center depend on the number and nature of the provisioned systems. The requirements of the provisioned systems, including networking requirements, are the same as if you were to set them up without z/VM Center. Refer to the z/VM Planning information for further details.
Network requirements
IBM Director requires certain ports to be available and certain network protocols to be installed in order to enable communication among IBM Director components and between the management server and managed objects. In addition, network connectivity must exist between the management server and managed objects, and between the management server and the management console.
Network protocols
This topic lists the network protocols that can be used in an IBM Director environment. The following table lists the versions of network protocols that can be used in an IBM Director environment.
Table 20. Supported versions of network protocols Protocol IPX NetBIOS TCP/IP Supported version IPX versions supported by NetWare and Windows Native NetBIOS versions supported by Windows All WinSock-compatible versions of TCP/IP version 4.0 supported by AIX, i5/OS, Linux, NetWare, and Windows
Some network protocols are supported only for certain types of data transmissions or on certain operating systems. The following table contains additional information.
70
Table 21. Types of data transmission and supported network protocols Type of data transmission IBM Director Server IBM Director Console IBM Director Server SNMP devices IBM Director Server IBM Director Agent IBM Director Server IBM Director Agent IBM Director Server IBM Director Agent IBM Director Server IBM Director Agent IBM Director Server IBM Director Agent Operating system running on managed system Not applicable Not applicable AIX i5/OS Linux NetWare Windows Supported network protocols TCP/IP TCP/IP TCP/IP TCP/IP TCP/IP IPX or TCP/IP IPX, NetBIOS, or TCP/IP
Ports used by IBM Director

IBM Director processes require access to a number of ports in the installation environment. If these ports are blocked by a firewall or used by another process, some IBM Director functions might not work. Table 22 lists the ports used by the various IBM Director processes. v Abbreviations used in Table 22 are spelled out below the table. v In the Connection column, the symbols and are used. Where is used, the component to the left of the arrow is the initiator of the communication and the component to the right of the arrow is the listener or receiver of the communication. For example, if the entry in the Connection column is IBM Director Console IBM Director Server, then IBM Director Console is the initiator and IBM Director Server is the listener. Where is used, either component can function as the initiator or the listener. v For the TCP ports listed, the initiator opens a random port in the 1024-65535 range and then connects to the listener on the port listed in the Destination port column. The listener responds by connecting to the original random port opened by the initiator.
Table 22. Ports used by IBM Director Category IBM Director interprocess communication Connection IBM Director Server IBM Director Agent Destination port 14247 UDP and TCP1; 14248 TCP; 4490 IPX (read); 4491 IPX (write) 2033 TCP 2044 TCP 2034 TCP Any free port (for use of BladeCenter Network Device Manager) 4066 TCP
IBM Director Console DIRCLI client DIRCMD client IBM Director Console IBM Director Console DIRCLI client
IBM Director Server IBM Director Server IBM Director Server IBM Director Console IBM Director Server over SSL IBM Director Server
Chapter 2. Planning
71
Table 22. Ports used by IBM Director (continued) Category CIM-XML over HTTP2,3 Connection IBM Director Server Level-1 or Level-2 managed system, or SMI-S storage device Destination port 15988 TCP (SUSE Linux distributions and Red Hat Linux for System z distributions) 5988 TCP (other operating systems) CIM-XML over HTTPS2,3 IBM Director Server Level-1 or Level-2 managed system, or SMI-S storage device 15989 TCP (SUSE Linux distributions and Red Hat Linux for System z distributions) 5989 TCP (other operating systems) CIM Listener2,3 HTTP Microsoft Windows DCOM ServeRAID interprocess communication Service processors CIMOM IBM Director Server IBM Director Server CIM Listener BladeCenter switch module Level-0 system 6988 TCP (HTTP) 80 TCP 137 UDP; 138 UDP; 139 TCP; 445 TCP
ServeRAID CIM Provider IBM Director Server Service processor IBM Director Server
ServeRAID Manager 34572 TCP
service processor IBM Director Server (alerts) service processor (ASF, ASF 2.0, and IPMI) IBM Director Server (ASF, ASF 2.0, and IPMI) SLP service agents or SLP directory agents SNMP agent IBM Director Server SNMP devices (Remote Session task) Level-0 system BladeCenter management module BladeCenter switch module SNMP devices (Remote Session task)
6090 TCP 13991 UDP 623 and 664 UDP
Service processor
Random port in the 1024-65535 range4 427 TCP and UDP
SLP
IBM Director Server
SNMP
IBM Director Server SNMP agent
161 TCP and UDP1 162 TCP and UDP1 22 TCP
SSH
IBM Director Server
IBM Director Server Telnet IBM Director Server
22 TCP 23 TCP
IBM Director Server IBM Director Server
23 TCP 23 TCP
72
Abbreviations used in Table 22 on page 71 v ASF = Alert Standard Format v HTTP = Hypertext Transfer Protocol v HTTPS = Hypertext Transfer Protocol over Secure Sockets Layer (SSL) v IPMI= Intelligent Platform Management Interface v SLP = Service Location Protocol v SNMP = Simple Network Management Protocol v SSH = Secure Shell v SSL = Secure Sockets Layer v TCP = Transmission Control Protocol v UDP = User Datagram Protocol Notes: 1. (Windows XP Professional Edition with Service Pack 2 only) You must enable these ports for IBM Director to function correctly. 2. Ports 5988, 15988, 5989, 15989, and 6988 must be open in order to install IBM Director. In addition, the HTTP port must be turned on for the Pegasus CIMOM, regardless of whether or not HTTPS is turned on (SSL is enabled) for any CIM-related function of the Level-2 agent to work. 3. If the CIMOM ports for a Level-1 managed system are changed after IBM Director Server discovers the system, the system will change to a Level-0 managed system in IBM Director. To correct this, you must complete the following steps: a. Delete the managed system in IBM Director. b. Shut down and restart the managed system. c. Discover or add the managed system in IBM Director. 4. You can specify a fixed port by modifying the asmDefinitions.properties file, which is in the data directory.
Supported operating systems

This section lists the operating systems on which IBM Director Server, IBM Director Console, IBM Director Agent, and IBM Director Core Services are supported. This support can vary by version, release, and update. Make sure you review the supported operating systems for the version of IBM Director in your environment. For the most recent list of supported operating systems, see IBM Director Hardware and Software Support Guide. You can download it from www.ibm.com/systems/ management/director/.
Operating systems supported by IBM Director 5.20.1

IBM Director 5.20.1 provides support for many operating systems. However, support varies depending on the selected hardware and IBM Director component. This release of IBM Director Agent and IBM Director Core Services can be downloaded from the Web or are available on the following CDs: v IBM Director on x86, Version 5.20 Update 1 v IBM Director for AIX 5L, Version 5.20 Update 1 v IBM Director for Linux on POWER, Version 5.20 Update 1 See the installation instructions for each operating-system environment for information about the applicable CD or the file that can be downloaded from the Web.
Chapter 2. Planning
73
When preparing to install IBM Director, consider the following information: v Unless stated otherwise, IBM Director provides Level-0 support for all operating systems. v If you are installing IBM Director Console on the same system as IBM Director Server, see the operating systems supported by IBM Director Server. v IBM Director Server and IBM Director Console can be installed on non-IBM hardware as long as the system meets the hardware requirements for running that component. v IBM Director support for Intel Itanium systems is provided by IBM Director Agent version 5.10.3. There is no IBM Director Agent version 5.20.1 for Intel Itanium systems. IBM Director Agent for Intel Itanium systems is available as a Web-download only. Download the dir5.10.3_agent_windows64.zip or dir5.10.3_agent_linux64.zip file, as needed, from the IBM Director Web site at www.ibm.com/systems/management/director/downloads.html.
Table 23. Operating systems supported by IBM Director on System x systems; IBM and third-party x86-based systems IBM Director Console IBM Director Server IBM Director Agent IBM Director Core Services
Operating system Editions of Windows for 32-bit systems: Windows 2000, Advanced Server and Server Editions (Service Pack 3 required) Windows 2000 Datacenter Edition Windows 2000 Professional Edition (Service Pack 3 required) Windows Server 2003 Datacenter Edition (supports Service Pack 1 ) Windows Server 2003, Enterprise, Standard, and Web Editions (supports Service Pack 1 and Release 2) (supports Service Pack 2 and earlier) Windows Vista (Business, Business N, Enterprise, and Ultimate editions) Note: In version 5.20 Update 1, Windows Vista managed systems can be discovered, but can not be managed. Editions of Windows for 64-bit systems: Windows Server 2003 Datacenter Edition for Itanium systems Windows Server 2003 Datacenter x64 Edition (supports Release 2 and earlier) Windows Server 2003 Enterprise Edition for Itanium systems Windows Server 2003, Enterprise, Standard, and Web x64 Editions (supports Release 2 and earlier) Windows XP Professional x64 Edition (supports Release 2 and earlier) Versions of Linux for 32-bit systems:
X X
X X X X X X X
X X
X X
X X
X X X X X X X X
X X X X X
Red Hat Enterprise Linux AS and ES, version 3.0 (supports Update 8 and X earlier) Note: (Level-2 and Level-1 support only) For systems that contain an AMD Opteron or Athlon64 processor, Update 5 or later is required. Red Hat Enterprise Linux WS, version 3.0 (supports Update 8 and earlier) Note: (Level-2 and Level-1 support only) For systems that contain an AMD Opteron or Athlon64 processor, Update 5 or later is required.
74
Table 23. Operating systems supported by IBM Director on System x systems; IBM and third-party x86-based systems (continued) IBM Director Console IBM Director Server X IBM Director Agent X X IBM Director Core Services X X X X X X X X X X X X X X X X
Operating system
Red Hat Enterprise Linux AS and ES, version 4.0 (supports Update 4 and X earlier) Red Hat Enterprise Linux WS, version 4.0 (supports Update 4 and earlier) Red Hat Enterprise Linux AS, ES, and WS, version 5.0 SUSE Linux Enterprise Server 9 for x86 (supports Service Pack 3, Update 1 and earlier) SUSE Linux Enterprise Server 10 for x86 VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 3.0, and 3.0.1, Console VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 3.0, and 3.0.1, X guest operating systems Note: Supported guest operating systems are those that are supported by both IBM Director and the specified version of VMware. See the VMware product documentation for a list of supported operating systems. VMware GSX Server, versions 3.1 and 3.2, guest operating systems Note: Supported guest operating systems are those that are supported by both IBM Director and the specified version of VMware. See the VMware product documentation for a list of supported operating systems. VMware GSX Server, versions 3.1 and 3.2, host operating systems Note: Supported host operating systems are those that are supported by both IBM Director and the specified version of VMware. See the VMware product documentation for a list of supported operating systems. Versions of Linux for 64-bit systems: Red Hat Enterprise Linux AS, version 3.0, for Intel Itanium Red Hat Enterprise Linux AS and ES, version 3.0, for AMD64 and EM64T (supports Update 8 and earlier) Red Hat Enterprise Linux WS, version 3.0, for AMD64 and EM64T (supports Update 8 and earlier) Red Hat Enterprise Linux AS, version 4.0, for Intel Itanium (supports Update 5 and earlier) Red Hat Enterprise Linux AS and ES, version 4.0, for AMD64 and EM64T X (supports Update 5 and earlier) Red Hat Enterprise Linux WS, version 4.0, for AMD64 and EM64T (supports Update 5 and earlier) SUSE Linux Enterprise Server 9 for AMD64 and EM64T (supports Service X Pack 3 Update 1 and earlier) SUSE Linux Enterprise Server 9 for Itanium Processor Family SUSE Linux Enterprise Server 10 for AMD64 and EM64T SUSE Linux Enterprise Server 10 with Xen Kernel Other operating systems supported by System x servers: Microsoft Virtual Server 2005 (Release 2 required; SP1 supported) X X X
X X X X X X X X X X X X X X
X X X
X X X X X X
Chapter 2. Planning
75
Table 23. Operating systems supported by IBM Director on System x systems; IBM and third-party x86-based systems (continued) IBM Director Console IBM Director Server IBM Director Agent X IBM Director Core Services X
Operating system Microsoft Virtual Server (guest operating system) (Release 2 required; SP1 supported) Note: Supported guest operating systems are those that are supported by both IBM Director and the specified version of Microsoft. See the Microsoft product documentation for a list of supported operating systems. NetWare, version 6.5 Note: Level-0 support is not provided.
Table 24. Operating systems supported by IBM Director on System i and System p products IBM Director Console IBM Director Server IBM Director Agent X IBM Director Core Services
Operating system AIX 5L, Version 5.2 (supports TL06 or later) Note: Level-0 support includes only Discovery, Remote Session and a limited subset of the Software Distribution task. AIX 5L, Version 5.3 (supports TL03 or later) Note: Level-0 support includes only Discovery, Remote Session and a limited subset of the Software Distribution task. i5/OS, Version 5 Release 3 i5/OS, Version 5 Release 4 Note: Level-0 support includes only Discovery, Remote Session and a limited subset of the Software Distribution task. Red Hat Enterprise Linux AS, versions 4.3, 4.4, and 4.5, for IBM POWER Red Hat Enterprise Linux AS, version 5.0, for IBM POWER SUSE Linux Enterprise Server 9 for IBM POWER (Service Pack 3 required) SUSE Linux Enterprise Server 10 for IBM POWER
X X
X X
X X
X X
X X
Table 25. Operating systems supported by IBM Director on System z systems IBM Director Console X IBM Director Server X IBM Director Agent X IBM Director Core Services X X X X X X X X X X
Operating system Red Hat Enterprise Linux AS, version 4.0, for IBM System z (supports Update 5 and earlier) Red Hat Enterprise Linux AS, version 5.0, for IBM System z SUSE Linux Enterprise Server 9 for IBM System z (supports Service Pack 3 and earlier) SUSE Linux Enterprise Server 10 for IBM System z
Operating systems supported by IBM Director 5.20

IBM Director 5.20 provides support for many operating systems. However, support varies depending on the selected hardware and IBM Director component.
76
This release of IBM Director Agent and IBM Director Core Services can be downloaded from the Web or are available on the following CDs: v IBM Director on x86, V5.20 v IBM Director Agents & Consoles, V5.20 (1 of 2) v v v v v IBM IBM IBM IBM IBM Director Director Director Director Director Agents & Consoles, V5.20 (2 of 2) for AIX 5L, V5.20 for i5/OS, V5.20 for Linux on POWER, V5.20 for Linux on System z, V5.20
See the installation instructions for each operating-system environment for information about the applicable CD or the file that can be downloaded from the Web. When preparing to install IBM Director, consider the following information: v Unless stated otherwise, IBM Director provides Level-0 support for all operating systems. v If you are installing IBM Director Console on the same system as IBM Director Server, see the operating systems supported by IBM Director Server. v IBM Director Server and IBM Director Console can be installed on non-IBM hardware as long as the system meets the hardware requirements for running that component. v IBM Director support for Intel Itanium systems is provided by IBM Director Agent version 5.10.3. There is no IBM Director Agent version 5.20 for Intel Itanium systems. IBM Director Agent for Intel Itanium systems is available as a Web-download only. Download the dir5.10.3_agent_windows64.zip or dir5.10.3_agent_linux64.zip file, as needed, from the IBM Director Web site at www.ibm.com/systems/management/director/downloads.html.
Table 26. Operating systems supported by IBM Director on System x systems; IBM and third-party x86-based systems IBM Director Console IBM Director Server IBM Director Agent IBM Director Core Services
Operating system Editions of Windows for 32-bit systems: Windows 2000, Advanced Server and Server Editions (Service Pack 3 required) Windows 2000 Datacenter Edition Windows 2000 Professional Edition (Service Pack 3 required) Windows Server 2003 Datacenter Edition (supports Service Pack 1 ) Windows Server 2003, Enterprise, Standard, and Web Editions (supports Service Pack 1 and Release 2) Windows XP Professional Edition (supports Service Pack 2 and earlier) Editions of Windows for 64-bit systems: Windows Server 2003 Datacenter Edition for Itanium systems Windows Server 2003 Datacenter x64 Edition (supports Release 2 and earlier) Windows Server 2003 Enterprise Edition for Itanium systems
X X
X X X X X X
X X
X X
X X
X X X
X X X
Chapter 2. Planning
77
Table 26. Operating systems supported by IBM Director on System x systems; IBM and third-party x86-based systems (continued) IBM Director Console X X IBM Director Server X IBM Director Agent X X IBM Director Core Services X X
Operating system Windows Server 2003, Enterprise, Standard, and Web x64 Editions (supports Release 2 and earlier) Windows XP Professional x64 Edition (supports Release 2 and earlier) Versions of Linux for 32-bit systems:
Red Hat Enterprise Linux AS and ES, version 3.0 (supports Update 8 and X earlier) Note: (Level-2 and Level-1 support only) For systems that contain an AMD Opteron or Athlon64 processor, Update 5 or later is required. Red Hat Enterprise Linux WS, version 3.0 (supports Update 8 and earlier) Note: (Level-2 and Level-1 support only) For systems that contain an AMD Opteron or Athlon64 processor, Update 5 or later is required. Red Hat Enterprise Linux AS and ES, version 4.0 (supports Update 4 and X earlier) Red Hat Enterprise Linux WS, version 4.0 (supports Update 4 and earlier) SUSE Linux Enterprise Server 9 for x86 (supports Service Pack 3 and earlier) SUSE Linux Enterprise Server 10 for x86 VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 3.0, and 3.0.1, Console VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 3.0, and 3.0.1, X guest operating systems Note: Supported guest operating systems are those that are supported by both IBM Director and the specified version of VMware. See the VMware product documentation for a list of supported operating systems. VMware GSX Server, versions 3.1 and 3.2, guest operating systems Note: Supported guest operating systems are those that are supported by both IBM Director and the specified version of VMware. See the VMware product documentation for a list of supported operating systems. VMware GSX Server, versions 3.1 and 3.2, host operating systems Note: Supported host operating systems are those that are supported by both IBM Director and the specified version of VMware. See the VMware product documentation for a list of supported operating systems. Versions of Linux for 64-bit systems: Red Hat Enterprise Linux AS, version 3.0, for Intel Itanium Red Hat Enterprise Linux AS and ES, version 3.0, for AMD64 and EM64T (supports Update 8 and earlier) Red Hat Enterprise Linux WS, version 3.0, for AMD64 and EM64T (supports Update 8 and earlier) Red Hat Enterprise Linux AS, version 4.0, for Intel Itanium Red Hat Enterprise Linux AS and ES, version 4.0, for AMD64 and EM64T X (supports Update 4 and earlier) Red Hat Enterprise Linux WS, version 4.0, for AMD64 and EM64T (supports Update 4 and earlier) X X
X X
X X X X X X
X X
X X X
X X X X X X X
X X X X X X
78
Table 26. Operating systems supported by IBM Director on System x systems; IBM and third-party x86-based systems (continued) IBM Director Console IBM Director Server X IBM Director Agent X X X X X X X X IBM Director Core Services X X X X
Operating system
SUSE Linux Enterprise Server 9 for AMD64 and EM64T (supports Service X Pack 3 and earlier) SUSE Linux Enterprise Server 9 for Itanium Processor Family SUSE Linux Enterprise Server 10 for AMD64 and EM64T SUSE Linux Enterprise Server 10 with Xen Kernel Other operating systems supported by System x servers: Microsoft Virtual Server (guest operating system) (Release 2 required) Note: Supported guest operating systems are those that are supported by both IBM Director and the specified version of Microsoft. See the Microsoft product documentation for a list of supported operating systems. NetWare, version 6.5 Note: Level-0 support is not provided.
Table 27. Operating systems supported by IBM Director on System i and System p products IBM Director Console IBM Director Server IBM Director Agent X IBM Director Core Services
Operating system AIX 5L, Version 5.2 (supports ML05 or later) Note: Level-0 support includes only Discovery, Remote Session and a limited subset of the Software Distribution task. AIX 5L, Version 5.3 (supports ML03 or later) Note: Level-0 support includes only Discovery, Remote Session and a limited subset of the Software Distribution task. i5/OS, Version 5 Release 3 i5/OS, Version 5 Release 4 Note: Level-0 support includes only Discovery, Remote Session and a limited subset of the Software Distribution task. Red Hat Enterprise Linux AS, versions 4.3 and 4.4, for IBM POWER SUSE Linux Enterprise Server 9 for IBM POWER (Service Pack 3 required) SUSE Linux Enterprise Server 10 for IBM POWER
X X X
X X X
X X X
X X X
Table 28. Operating systems supported by IBM Director on System z systems IBM Director Console X X X IBM Director Server X X X IBM Director Agent X X X IBM Director Core Services X X X
Operating system Red Hat Enterprise Linux AS, version 4.0, for IBM System z (supports Update 4 and earlier) SUSE Linux Enterprise Server 9 for IBM System z (supports Service Pack 3 and earlier) SUSE Linux Enterprise Server 10 for IBM System z
Chapter 2. Planning
79
Support of IBM Director tasks across operating systems

This section lists the IBM Director tasks and the operating systems upon which they are supported. Support for IBM Director tasks can vary depending on the following items: v The system or hardware device model (the managed object) v The level of IBM Director support installed on the system or device (IBM Director Agent for a Level-2 managed object, IBM Director Core Services for a Level-1 managed object, or no IBM Director support which is Level-0 managed object). v The operating system that is installed on a managed object v The service processor installed in the managed object v The level of the device drivers that are installed on the managed object Attention: The device drivers that are available for a managed object depend on the service processor and operating system that are installed on the managed object. For information about what hardware features are supported on IBM System x, BladeCenter, or IntelliStation hardware or what operating systems are supported on IBM System x, BladeCenter, or IntelliStation hardware, go to the IBM ServerProven Web site at www.ibm.com/servers/eserver/serverproven/compat/ us/.
Management-server support of IBM Director tasks across operating systems

For some IBM Director tasks to work, IBM Director Server must be installed on a system running certain operating systems.
Task is supported on the following operating systems: All operating systems supported by IBM Director Server X X X X X X X X X X X X X X X X X
Task Asset ID CIM Manager Configuration Manager Configure SNMP Agent Event Log External Application Launch File Transfer Hardware Control Point Hardware Management Console Hardware Status Inventory (hardware) Inventory (software) Microsoft Cluster Browser Network Configuration Power Management Process Management Rack Manager
Linux and Windows only
80
Task is supported on the following operating systems: All operating systems supported by IBM Director Server X X X X X X X X X
Task Remote Control Remote Session Resource Monitors Server Storage Provisioning Tool SNMP Browser Software Distribution Storage Configuration Manager System Accounts Update Manager
Linux and Windows only
Managed-object support for IBM Director tasks across operating systems

IBM Director task support for a managed object varies depending on the operating system and the level of IBM Director support installed on the system or device. IBM Director Agent provides Level-2 managed object support. IBM Director Core Services provides Level-1 managed object support. Level-0 support is provided for systems via their operating system.
Operating systems ESX Server GSX Server
1, 2 1
Task Asset ID
Windows Level 2
1 1
Linux Level 2 Level 2
i5/OS Level 2 Level 2
AIX Level 2 Level 2
NetWare No No
Microsoft Virtual Server Level 2 Level 2
Level 2 Level 2
CIM Manager Level 2
Configuration See Operating systems supported by the Configuration Manager task Manager Configure SNMP Agent Event Log External Application Launch File Transfer Hardware Status Inventory (hardware)15 Inventory (software) Microsoft Cluster Browser Level 21 Levels 1, 2 Level 21,
5
Level 2 Levels 1, 2
Level 2 Levels 1, 2
Level 2 Level 2
No Levels 1, 2
Level 2 Levels 1, 2
Levels 1, 2
See Operating systems supported by External Application Launch
Level 2
Level 2
Level 214
Level 2
Level 2
Level 2
Level 2
See Operating systems supported by the Hardware Status task Levels 0, 1, 26, 7 Levels 0, 1, 26 Level 28 Levels 0, 1, 26, 7 Levels 0, 1, 26 No Levels 0, 1, 2 Level 2 Levels 0, 1, 2 Level 2 No No Level 27 Level 2 No Level 27 Level 2 No Levels 0, 1, 2 Levels 0, 1, 2 No
Chapter 2. Planning
81
Operating systems ESX Server GSX Server

1, 9
Task
Windows
1
Linux Level 2
i5/OS Level 2
AIX No
NetWare No
Microsoft Virtual Server Level 2
Network Level 2 Configuration Power Management Process Management Rack Manager13 Remote Control Remote Session Resource Monitors
Level 2
See Operating systems supported by the Power Management task Level 2 Level 210 Level 2 Level 2 Level 2 Level 2 Level 24, No Levels 016, 116, 2 Level 2
10
Level 2 Level 2 Level 211 Level 2 Level 2
Level 2 No No Level 2 Level 2
Level 2 No No Levels 0, 2 Level 2
Level 2 Level 2 No Level 2 Level 2
Level 2 Level 2 Level 2 Level 2 Level 2
Server Storage See Operating systems supported by IBM Server Storage Provisioning Tool Provisioning Tool SNMP Browser Software Distribution12 Level 2 Level 2 Level 2 Level 2 Level 2 Levels 0, 2 No Level 2 No No Level 2 Levels 0, 1, 2 Levels 1, 2
Levels 0, 1, 2 Levels 0, 1, 2 Levels 0, 1, 2 Levels 0, 2 Levels 1, 22,

9
Storage Levels 1, 2 Configuration Manager System Accounts Update Manager Level 21
Levels 1, 2
No
Level 21,
Level 2
Level 2
No Levels 0, 217
No No
Level 2 Levels 0, 1, 2
Levels 0, 1, 2 Levels 0, 1, 22, 17
Levels 0, 1, 2 No
Notes:
1
Not supported on Itanium systems. Not supported on System z systems. Not supported on guest operating systems. Supported on System x and Intel-based systems only. Not supported on Windows XP Professional x64 Edition. Support on Itanium systems is limited to Level 2. Platform-specific data is not available for hardware inventory.
Supported only on the following 32-bit editions of Windows: v Windows 2000, Advanced Server, Datacenter, and Server Editions v Windows Server 2003, Datacenter, Enterprise, Standard, and Web Editions
82
Not supported for Linux on POWER. Not supported on 64-bit versions of these operating systems. Supported on Windows guest operating systems only.
10
11
12
Only packages in the Solution Install format can be distributed to Level-0 and Level-1 managed systems. UpdateXpress packages can be distributed to Level-2 managed systems only.
13
Supported on System x, xSeries, and Netfinity systems only.
14
File systems that are displayed for the guest operating system are limited to file systems within its virtual disk.
15
Inventory data provided can vary among Level-0, Level-1 and Level-2 managed systems.
16
Supported for Linux on POWER only. Supported for Linux on POWER and AIX on IBM BladeCenter JS21 only.
17
Operating systems supported by Server Configuration Manager and BladeCenter Configuration Manager
The Server Configuration Manager and BladeCenter Configuration Manager tasks do not require IBM Director Agent or IBM Director Core Services to function. These tasks are a function of IBM Director Server. You can use the Server Configuration Manager task on IBM System x and System i hardware managed objects. The operating system running on the managed object does not affect the support of this task. The Server Configuration Manager performs IP configuration using out-of-band communication. You can use the BladeCenter Configuration Manager task on IBM BladeCenter hardware managed objects. The operating system running on the managed object does not affect the support of this task.
Operating systems supported by External Application Launch

The External Application Launch task is supported by IBM Director Server when installed on x86-based management servers running Windows or Linux. Using External Application Launch, you can configure applications to start on any type of managed object that has been discovered by your installation of IBM Director Server. Before you use External Application Launch to configure an application to start on a managed object, you must make sure that the application runs on the selected managed object.
Operating systems supported by Hardware Status

The Hardware Status task provides support for Level-2 and Level-1 managed objects. Operating-system support varies depending on whether IBM Director Agent or IBM Director Core Services is installed. Unless otherwise indicated, this task is supported (although the support might be limited) by: v Out-of-band notifications generated by a service processor v CIM indications generated by IBM Director Core Services or IBM Director Agent, Version 5.10 or later
Chapter 2. Planning
83
Table 29. Hardware Status support for System x servers; IBM and third-party x86-based systems Operating system Editions of Windows for 32-bit systems: v Windows 2000, Advanced Server, Datacenter, Professional, and Server Editions v Windows XP Professional Edition v Windows Server 2003, Datacenter, Enterprise, Standard, and Web Editions Editions of Windows for 64-bit systems: v Windows Server 2003, Datacenter, Enterprise, Standard, and Web x64 Editions v Windows XP Professional x64 Edition Windows Server 2003, Datacenter and Enterprise 64-bit Itanium Editions Versions of Linux for 32-bit systems: v v v v Red Hat Enterprise Linux AS, Red Hat Enterprise Linux AS, SUSE Linux Enterprise Server SUSE Linux Enterprise Server ES, and WS, version 3.0 ES, and WS, version 4.0 9 for x86 10 for x86 Yes Yes1 Yes No Yes No Yes Yes Level 1 Level 2
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 3.0, and 3.0.1, Console VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 3.0, and 3.0.1, guest operating systems v VMware GSX Server, versions 3.1 and 3.2, Console v VMware GSX Server, versions 3.1 and 3.2, guest operating systems
Yes1 Limited (For Console) Yes1 (For guest) Limited
Yes1 Limited (For Console) Yes1 (For guest) Limited

1
Versions of Linux for 64-bit systems: v v v v v Red Hat Enterprise Linux AS, Red Hat Enterprise Linux AS, SUSE Linux Enterprise Server SUSE Linux Enterprise Server SUSE Linux Enterprise Server ES, and WS, version 3.0, for AMD64 and EM64T ES, and WS, version 4.0, for AMD64 and EM64T 9 for AMD64 and EM64T 10 for AMD64 and EM64T 10 with Xen Kernel Yes Yes
v Red Hat Enterprise Linux AS, version 3.0, for Intel Itanium v Red Hat Enterprise Linux AS, version 4.0, for Intel Itanium v SUSE Linux Enterprise Server 9 for Itanium Processor Family Other operating systems supported by System x servers: Microsoft Virtual Server (guest operating system) NetWare, version 6.5
No
No
Limited Yes
2
Limited Yes
3
1. Out-of-band notifications generated by a service processor or in-band events generated by CIM (CIM support is system specific). 2. Out-of-band notifications generated by a service processor only. 3. In-band events generated by IBM Director Agent for NetWare, Version 5.1 or earlier, or out-of-band notifications generated by a service processor. Table 30. Hardware Status support for System i platforms and System p servers Operating system v AIX 5L, Version 5.2 v AIX 5L, Version 5.3 Level 1 No Level 2 Yes, for 5.20 Update 1 and later Yes1
v i5/OS, Version 5 Release 3 v i5/OS, Version 5 Release 4
No
84
Table 30. Hardware Status support for System i platforms and System p servers (continued) Operating system v 5.20 only: Red Hat Enterprise Linux AS, versions 4.3 and 4.4, for IBM POWER / 5.20 Update 1 and later: Red Hat Enterprise Linux AS, versions 4.3, 4.4, and 4.5, for IBM POWER v SUSE Linux Enterprise Server 9 for IBM POWER v SUSE Linux Enterprise Server 10 for IBM POWER v 5.20 Update 1 and later: Red Hat Enterprise Linux AS, version 5.0, for IBM POWER Level 1 Yes
1
Level 2 Yes1
Yes
No
1. (BladeCenter JS20 and JS21 only) Out-of-band notifications generated by a service processor only. Table 31. Hardware Status support for System z servers Operating system v v v v Red Hat Enterprise Linux AS, version 4.0, for IBM System z SUSE Linux Enterprise Server 9 for IBM System z SUSE Linux Enterprise Server 10 for IBM System z 5.20 Update 1 and later: Red Hat Enterprise Linux AS, version 5.0, for IBM System z Level 1 No Level 2 No
Operating systems supported by Power Management

Managed systems must meet certain criteria for the Power Management task to work. The Power Management task is provided using the right-click feature on managed objects in IBM Director Console. Power Management support is provided through one or more of the hardware or software: v A service processor configured for out-of-band communication v Operating system v Wake on LAN network interface card (NIC) Note: IBM Director Server also provides Power Management support for the following versions of IBM Director Agent with the MPA Agent feature installed: v 4.22 v 4.21 v 4.20.2 v 4.20 v 4.12 v 4.11 v 4.10.2 v 4.10 For information about this support, see the IBM Director 4.20 Systems Management Guide. Power Management-support provided by operating systems: Support for the Power Management task can be provided by the operating system running on Level-0, Level-1, and Level-2 managed systems.
Table 32. Operating systems supported by System x servers; IBM and third-party x86-based systems Operating system Editions of Windows for 32-bit systems: Supported
Chapter 2. Planning
85
Table 32. Operating systems supported by System x servers; IBM and third-party x86-based systems (continued) Operating system v Windows 2000, Advanced Server, Datacenter, Professional, and Server Editions v Windows XP Professional Edition v Windows Server 2003, Datacenter, Enterprise, Standard, and Web Editions Editions of Windows for 64-bit systems: v Windows Server 2003, Datacenter, Enterprise, Standard, and Web x64 Editions v Windows XP Professional x64 Edition v Windows Server 2003, Datacenter and Enterprise 64-bit Itanium Editions Versions of Linux for 32-bit systems: v v v v v v Red Hat Enterprise Linux AS, ES, and WS, version 3.0 Red Hat Enterprise Linux AS, ES, and WS, version 4.0 SUSE Linux Enterprise Server 9 for x86 SUSE Linux Enterprise Server 10 for x86 VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 3.0, and 3.0.1, Console VMware GSX Server, versions 3.1 and 3.2, Console Yes, Restart Yes, Restart and Shutdown Supported Yes, Restart and Shutdown
v VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 3.0, and 3.0.1, guest operating systems v VMware GSX Server, versions 3.1 and 3.2, guest operating systems
Yes, Restart (for Linux) and Restart and Shutdown (for Windows)
Versions of Linux for 64-bit systems: v v v v v v v v Red Hat Enterprise Linux AS, Red Hat Enterprise Linux AS, Red Hat Enterprise Linux AS, Red Hat Enterprise Linux AS, SUSE Linux Enterprise Server SUSE Linux Enterprise Server SUSE Linux Enterprise Server SUSE Linux Enterprise Server ES, and WS, version 3.0, for AMD64 and EM64T ES, and WS, version 4.0, for AMD64 and EM64T version 3.0, for Intel Itanium version 4.0, for Intel Itanium 9 for AMD64 and EM64T 9 for Itanium Processor Family 10 for AMD64 and EM64T 10 with Xen Kernel Yes, Restart
Other operating systems supported by System x servers: Microsoft Virtual Server (guest operating system) Yes, Restart and Shutdown No
NetWare, version 6.5
Note: (For System p servers only) Power Management-support provided for Level-0, Level-1, and Level-2 managed systems.
Table 33. Operating systems supported by System i platforms and System p servers Operating system v i5/OS, Version 5 Release 3 v i5/OS, Version 5 Release 4 v Red Hat Enterprise Linux AS, version 5.0, for IBM POWER v AIX 5L, Version 5.2 Yes, Restart v AIX 5L, Version 5.3 v 5.20 only: Red Hat Enterprise Linux AS, versions 4.3 and 4.4, for IBM POWER / 5.20 Update 1 and later: Red Hat Enterprise Linux AS, versions 4.3, 4.4, and 4.5, for IBM POWER v SUSE Linux Enterprise Server 9 for IBM POWER v SUSE Linux Enterprise Server 10 for IBM POWER Supported No
1
86
Table 33. Operating systems supported by System i platforms and System p servers (continued) Operating system Supported
1. Power-management support is available to Level-2 managed systems running i5/OS and SSH. To acquire this support, discover the managed system, log in to the system, and promote the system to a Level-2 managed system. Table 34. Operating systems supported by System z servers Operating system v v v v Red Hat Enterprise Linux AS, version 4.0, for IBM System z SUSE Linux Enterprise Server 9 for IBM System z SUSE Linux Enterprise Server 10 for IBM System z 5.20 Update 1 and later: Red Hat Enterprise Linux AS, version 5.0, for IBM System z Supported Yes, Restart
Power Management-support provided by service processors: Support for the Power Management task can be provided by System x service processors that can communicate out of band. The following service processors in IBM System x servers and blade servers provide support for the Power Management task using out-of-band communication: v Remote Supervisor Adapter v Remote Supervisor Adapter II v IPMI baseboard management controller (BMC) These service processors provide support for the Power On, Restart Now, and Power Off Now subtasks. Out-of-band communication does not require IBM Director Core Services or IBM Director Agent. However, you must configure the service processor to communicate with IBM Director Server. Also, you must associate a Physical Platform managed object (PPMO) with the service processor in IBM Director Console. Power Management-support provided by the Wake on LAN feature: Support for the Power Management task can be provided by System x servers that have the Wake on LAN feature enabled. Support is provided only for Level-2 managed systems. Wake on LAN provides the Power On subtask only. In order to use power management provided by Wake on LAN technology, the following criteria must be met: v The system must include a network interface card (NIC) that can use Wake on LAN technology. v The Wake on LAN feature must be enabled. v IBM Director Server can detect the MAC address of a Level-2 managed system. v The managed system data is included in the IBM Director inventory tables. v The managed system is running an operating system that supports the Wake on LAN feature. See the following table for details.
Table 35. Operating systems supported by System x servers and IBM x86-based systems Operating system Editions of Windows for 32-bit systems: Supported
Chapter 2. Planning
87
Table 35. Operating systems supported by System x servers and IBM x86-based systems (continued) Operating system v Windows 2000, Advanced Server, Datacenter, Professional, and Server Editions v Windows XP Professional Edition v Windows Server 2003, Datacenter, Enterprise, Standard, and Web Editions Editions of Windows for 64-bit systems: v Windows Server 2003, Datacenter, Enterprise, Standard, and Web x64 Editions v Windows XP Professional x64 Edition v Windows Server 2003, Datacenter and Enterprise 64-bit Itanium Editions Versions of Linux for 32-bit systems: v v v v Red Hat Enterprise Linux AS, Red Hat Enterprise Linux AS, SUSE Linux Enterprise Server SUSE Linux Enterprise Server ES, and WS, version 3.0 ES, and WS, version 4.0 9 for x86 10 for x86 Yes Yes Supported Yes
Versions of Linux for 64-bit systems: v v v v v v v v Red Hat Enterprise Linux AS, Red Hat Enterprise Linux AS, Red Hat Enterprise Linux AS, Red Hat Enterprise Linux AS, SUSE Linux Enterprise Server SUSE Linux Enterprise Server SUSE Linux Enterprise Server SUSE Linux Enterprise Server ES, and WS, version 3.0, for AMD64 and EM64T ES, and WS, version 4.0, for AMD64 and EM64T version 3.0, for Intel Itanium version 4.0, for Intel Itanium 9 for AMD64 and EM64T 9 for Itanium Processor Family 10 for AMD64 and EM64T 10 with Xen Kernel Yes
Other operating systems supported by System x servers: Microsoft Virtual Server (guest operating system) NetWare, version 6.5 No Yes
IBM Director task support for BladeCenter products

IBM Director tasks provide support for BladeCenter products. The support can vary depending on whether it is for the BladeCenter chassis, network devices, and blade servers. A BladeCenter unit consists of a chassis, one or two management modules, one or more network devices (previously called switches, up to a total of four), and one or more blade servers (up to a total of 14, depending on the model). The chassis is the physical enclosure that contains the blade servers. The chassis has one or two management modules that contain a service processor. IBM Director discovers the chassis and gathers information from the chassis by way of the management module. You cannot install IBM Director Agent or IBM Director Core Services on the chassis. The network device is an SNMP device, and IBM Director considers the network device to be a managed device. When you view the network device in IBM Director, it might be displayed in the RMON devices group, which is a subgroup of the SNMP devices group. IBM Director can gather some information from a blade server before IBM Director Agent or IBM Director Core Services is installed on the blade server. The information is gathered from the blade server by way of the chassis management module. In IBM Director Console, the blade server is represented by a physical platform managed object. However, after you install IBM Director Agent or IBM
88
Director Core Services on the blade server, it is a managed object, and the features and functions that you can use on the blade server are comparable to those that you can use on any managed object. IBM Director tasks that you can use on your BladeCenter unit can vary, depending on the features and options that you have installed. See the following table for a list of IBM Director tasks and information about whether you can use a task on the chassis, network device, or a blade server without IBM Director Agent or IBM Director Core Services installed. Unless otherwise noted in this documentation, a task behaves the same for blade servers as for any managed system. Note: When IBM Director Agent or IBM Director Core Services is installed on a blade server, the supported tasks depend on the operating system that is installed on the blade server.
Table 36. IBM Director task support for BladeCenter products Tasks and subtasks BladeCenter Configuration Manager Event Action Plans Hardware Status Inventory Network Device Manager (formerly Switch Management launch pad) Power Management Rack Manager Remote Session Remote Monitors SNMP Browser Chassis Yes Yes Yes Yes Not applicable No Yes Not applicable No No Network device No Yes No Yes Yes No Yes Yes Yes Yes Blade server without IBM Director Agent or IBM Director Core Services installed Not applicable Yes Yes Yes Not applicable Yes No No No Yes
2 1
1. Inventory of the chassis, network device, and blade servers can be obtained through the management module. Blade server inventory that is collected through the management module is a subset of the total inventory that is available if IBM Director Agent or IBM Director Core Services is installed on the blade server. 2. To use the SNMP Browser task, the operating-system SNMP agent must be installed on the blade server.
IBM Director task support for Storage products

IBM Director provides limited task support for Storage products.
Table 37. IBM Director task support for Storage products Tasks and features DS300 DS400 DS4000 Brocade switches Yes Yes Yes Yes Yes DS6000 QLogic BladeCenter switches
Event Action Plans1 Event Log External Application Launch Hardware Status Inventory
No Yes Yes Yes Yes
1. Indicates that the Storage product generates events. Events are detected for use in event action plans.
Chapter 2. Planning
89
Supported database applications

IBM Director Server uses an SQL database to store inventory data for the systems in the environment.
Database installation types

Depending on the database application selected and the operating system of the management server, the database might be embedded, local, or remote. The three installation types are described below. embedded DBMS The DBMS is installed on the management server as part of the IBM Director Server installation, and shares the Java Virtual Machine with IBM Director. local DBMS The DBMS is installed on the management server on which IBM Director Server is installed. remote DBMS The DBMS is installed on a different server than the management server, and accessed remotely by IBM Director Server. See Choosing the IBM Director database application for additional information about these installation types.
Database applications supported by IBM Director Server 5.20.1

The following table lists the database applications supported by IBM Director Server 5.20.1 on different management servers and provides information about whether the database management system (DBMS) is embedded or can be installed locally or remotely.
Table 38. Database applications supported by IBM Director 5.20.1 Database Apache Derby Supported database versions v V10.2 (included with IBM Director Server on AIX, Linux, and Windows) v version 9.1 with Fix Pack 2 v version 8.2 with Fix Pack 7 v version 8.1 with Fix Pack 14 IBM DB2 Universal Database for System i (part of i5/OS) Microsoft SQL Server v Microsoft SQL Server 2005 with Service Pack 1 v Microsoft SQL Server 2000 with Service Pack 4 AIX Embedded i5/OS Linux Embedded Windows Embedded
IBM DB2 Universal Database
Local or remote
Local or remote Remote
Local or remote Local or remote
Local
(see Limitations of v Microsoft SQL Server 2005 support on Express Edition with Service page 91) Pack 1 v Microsoft SQL Server 2000 Desktop Engine (also called MSDE 2000) with Service Pack 4
Local
90
Table 38. Database applications supported by IBM Director 5.20.1 (continued) Database Oracle Supported database versions AIX Local or remote i5/OS Linux Local or remote Local or remote Windows Local or remote
v version 10g release 2 v version 10g release 1 (Oracle Server) v version 9.2 PostgreSQL v version 8.1 v version 7.4 v version 7.3
Database applications supported by IBM Director Server 5.20

The following table lists the database applications supported by IBM Director Server 5.20 on different management servers and provides information about whether the database management system (DBMS) is embedded or can be installed locally or remotely.
Table 39. Database applications supported by IBM Director 5.20 Database Apache Derby Supported database versions v V10.1 (included with IBM Director Server on AIX, Linux, and Windows) v version 8.2 with Fix Pack 5 v version 8.1 with Fix Pack 12 IBM DB2 Universal Database for System i (part of i5/OS) v Microsoft SQL Server 2005 with Service Pack 1 v Microsoft SQL Server 2000 with Service Pack 4 AIX Embedded i5/OS Linux Embedded Windows Embedded
Local or remote
Local
Microsoft SQL Server
(see Limitations of v Microsoft SQL Server 2005 support) Express Edition with Service Pack 1 v Microsoft SQL Server 2000 Desktop Engine (also called MSDE 2000) with Service Pack 4 Oracle v version 10g release 2 v version 10g release 1 (Oracle Server) v version 9.2 PostgreSQL v version 8.1 v version 7.4 v version 7.3 Local or remote
Local
Local or remote
Limitations of support
Microsoft SQL Server database Based on information from the Microsoft Web site, the Microsoft SQL Server 2005 JDBC Driver is officially supported only on the following operating systems: v Linux v Windows 2000 Service Pack 4 v Windows Server 2003 Service Pack 1 v Windows XP Service Pack 2
Chapter 2. Planning
91
However, it is likely that Microsoft SQL Server might work well on many other operating systems supporting Java Virtual Machine. This statement is based on internal testing of IBM Director and on the following information from the Microsoft Web site: In its continued commitment to interoperability, Microsoft provides a Java Database Connectivity (JDBC) driver for use with SQL Server 2005. The SQL Server 2005 JDBC Driver is available to all SQL Server users at no additional charge, and provides access to SQL Server 2000 and SQL Server 2005 from any Java application, application server, or Java-enabled applet. This driver is a Type 4 JDBC driver that provides database connectivity through the standard JDBC application program interfaces (APIs) available in J2EE (Java2 Enterprise Edition). The SQL Server 2005 JDBC Driver 1.0 is JDBC 3.0 compliant and runs on the Java Runtime Environment (JRE) version 1.4 and later versions. It has been tested against all major application servers, including BEA WebLogic, IBM WebSphere, JBoss, and Sun. Note The JDBC driver is designed to work on any operating system that supports the use of a Java Virtual Machine (JVM). However, only Sun Solaris, Red Hat Linux, and Windows 2000 or later operating systems are officially supported. http://www.microsoft.com/downloads/ details.aspx?familyid=E22BC83B-32FF-4474-A44A22B6AE2C4E17#Overview Microsoft Jet database The Microsoft Jet database supported in versions of IBM Director prior to version 5.10 continues to be supported only for upgrades to IBM Director version 5.20. The Microsoft Jet database is not available as a database option for new installations. Users with Microsoft Jet databases are strongly encouraged to use one of the other supported databases for IBM Director, as support for Microsoft Jet will probably not be offered in future releases of IBM Director.
Planning to install IBM Director

Any time you upgrade or install IBM Director, you should complete the planning steps before starting the actual installation, in order to ensure that your installation is successful and meets your needs.
Reviewing the environment

Before installing IBM Director, review the network of systems and devices you will manage with IBM Director to identify what kinds of objects you will manage, where they are located, and how IBM Director will connect with them. Your network must be up and running before you install IBM Director.
Identifying the hardware

Begin the planning process by identifying the systems and devices that you want to manage with IBM Director. The type of hardware in the environment might determine how you prepare the physical infrastructure or which features you select when you install IBM Director Server. Your environment might include one or more of the following types of hardware:
92
v Chassis, racks, and remote input/output enclosures, such as IBM BladeCenter units v Systems, including servers, desktop computers, workstations, and mobile computers, such as IBM System i platforms, System p servers, System x servers, and System z servers v Storage devices, such as the IBM System Storage DS4000 family of disk storage devices v SNMP devices and printers v ServeRAID controllers or service processors, such as the Remote Supervisor Adapter II Review the complete lists of supported hardware in the Specified operating environments section of the IBM Director documentation. Identify the systems and devices you will manage with IBM Director. 1. Ensure that all systems and devices are correctly installed and cabled. 2. Record information about those systems and devices in Table 40. You can use this information to verify that your managed systems and devices have been discovered, to manually add systems or devices in IBM Director, or to plan managed-object groups or user roles based on the types or locations of managed systems and devices.
Table 40. Hardware identification worksheet for IBM Director System or device type Operating system (if applicable) Physical location Network address
Identifying local and remote subnets

You need to provide local and remote subnet information in order for IBM Director to discover managed objects.
Chapter 2. Planning
93
Identify the local and remote subnets in which the systems that you want to manage with IBM Director are located, and record this in Table 41
Table 41. Local and remote subnets worksheet Information to gather for discovery Unicast Addresses for Level-0 discovery Values ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___ IP addresses or IP-address ranges for unicast ___.___.___.___ discovery of Level-0 (Agentless) managed ___.___.___.___ systems. ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ Directory agent server for Level-1 discovery Service Location Protocol (SLP) directory agent server for discovery of Level-1 managed systems. SLP scope for Level-1 discovery Service Location Protocol (SLP) scope for discovery of Level-1 managed systems. ___.___.___.___ ___.___.___.___ IP addresses or IP-address ranges for unicast ___.___.___.___ discovery of Level-2 managed systems. ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ Unicast Addresses for Level-2 discovery Subnets for Level-2 discovery TCP/IP addresses and subnet masks for broadcast and relay discovery of Level-2 managed systems. ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___
/ / / / / / / / / /
___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___
Multicast group for Level-2 discovery Multicast group TCP/IP address and time-to-live value for multicast discovery of Level-2 managed systems.
multicast group: ___.___.___.___ time to live: _______
94
Table 41. Local and remote subnets worksheet (continued) Information to gather for discovery Subnets for discovery of SNMP devices TCP/IP addresses and subnet masks for discovery of simple network management protocol (SNMP) devices. Values ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ / / / / / / / / / / ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___
Community names for discovery of SNMP devices Community names for discovery of simple network management protocol (SNMP) devices.
_________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________
SLP profiles for discovery of SMI-S storage _________________________________ devices _________________________________ _________________________________ Service Location Protocol (SLP) profiles for _________________________________ discovery of SMI-S devices. _________________________________ _________________________________ _________________________________ _________________________________
Identifying firewalls and blocked ports

Review the firewalls and blocked ports in your installation environment in order to identify potential barriers to IBM Director access, and to plan how to implement IBM Director management without creating security gaps. IBM Director must be able to access all the managed objects in the network, and if you will be using a remote management console, the management console and management server must have access to each other. In addition, some functions of IBM Director might require access to the internet. Tip: If you have a wide area network (WAN) link, use a T1 line that transmits at a speed of at least 1.5 megabytes per second (MBps) to ensure reliable network performance. Consider each of the following issues carefully when planning to install IBM Director: v Ports 5988, 5989, and 6988 must be open in order to install IBM Director. Some firewalls might attempt to block these ports. Allow these ports to be used by the IBM Director software components. v The Service Location Protocol (SLP) port (port 427) needs to be open if the installation environment is behind a firewall. v For the getfru command to run successfully, the managed system must have firewall access through a standard FTP port. v The Remote Control and Software Distribution tasks both use session support to increase data transmission. Session support within TCP/IP causes data to flow
Chapter 2. Planning
95
through a nonreserved port that is different from the one that IBM Director typically uses for communication. Most firewalls do not allow the data to be transmitted through this other port. v Windows firewall can interfere with discovery of managed systems running Windows XP. v If a proxy server is required to access the internet from the management server, ensure that the management server is configured to use the proxy. v The Update Manager task cannot use Digest or NTLM authentication to access update packages from IBM. If a proxy server is required, it must be configured to use Basic authentication.
Choosing IBM Director optional components and extensions

Before installing IBM Director, you should choose which optional components you will install with IBM Director. These optional components include both installation options and separately installed extensions for IBM Director, and influence how and where you will install IBM Director. Review the information in Table 42 and choose the optional components you will install with IBM Director.
Table 42. IBM Director optional component planning worksheet Optional component h BladeCenter Management Description Provides the ability to configure IBM BladeCenter chassis, management modules, and network devices. BladeCenter Management Extension is an optional feature of IBM Director Server and IBM Director Console on Linux on System x, Linux on System z, and Windows. On i5/OS, Linux on System p, and AIX, the BladeCenter Management Extension is automatically installed. h Capacity Manager extension Provides resource-management planning tools to monitor resource usage, identify bottlenecks, and generate performance-analysis reports and recommendations. Capacity Manager is a separately purchased extension for IBM Director. See publib.boulder.ibm.com/ infocenter/eserver/v1r2/topic/ capman_5.20/fqn0_main.html. v Requires installation of an external database. v Increases the space needed for the database; some databases are not recommended. See Choosing the IBM Director database application on page 107. v IBM Director Server must be installed on Linux on System x or on Windows. v IBM Director Agent must be installed on systems to be monitored with Capacity Manager. Important considerations Requires Remote Deployment Manager to deploy operating systems to blade servers.
96
Table 42. IBM Director optional component planning worksheet (continued) Optional component h Electronic Service Agent extension Description Initiates automated service requests to IBM when managed system hardware errors occur that meet certain criteria for criticality. Electronic Service Agent is a free, downloadable extension for IBM Director Server and IBM Director Console. See www.ibm.com/ support/electronic/. h External Application Launch Wizard Provides wizard-based creation of IBM Director tasks to integrate third-party management software and other programs into the IBM Director Console user interface. External Application Launch Wizard is a free, downloadable extension for IBM Director Server. See publib.boulder.ibm.com/ infocenter/eserver/v1r2/topic/ ealwiz_5.20/frj0_main.html. h Hardware Management Console extension Enables starting the Hardware Management Console Web server directly from a managed object in IBM Director Console. Hardware Management Console is a free, downloadable extension for IBM Director Server and IBM Director Console. It is automatically installed with IBM Director Server and IBM Director Console on the following management servers and management consoles: v AIX v i5/OS v Linux on POWER See publib.boulder.ibm.com/ infocenter/eserver/v1r2/topic/ hmc_5.20/frk0_main.html. v IBM Director Server must be installed on Linux on System x or on Windows. v IBM Director Server must be installed in the default installation path. Important considerations IBM Director Server must be installed on Linux on System x or on Windows.
None.
Chapter 2. Planning
97
Table 42. IBM Director optional component planning worksheet (continued) Optional component Description Important considerations
h IBM Provides actual power v Requires BladeCenter PowerExecutive consumption and thermal load Management. extension information for some System x and v IBM Director Server and IBM BladeCenter servers. Director Console must be installed on one of the following PowerExecutive is a free, operating systems: downloadable extension for IBM Red Hat Enterprise Linux WS, Director Server and IBM Director version 4.0, for Intel x86 Console. See www.ibm.com/ SUSE Linux Enterprise Server servers/eserver/xseries/ 9 for x86 systems_management/ Windows Server 2003, ibm_director/extensions/ Enterprise, Standard, and powerexec.html . Web Editions h IBM Server Provides the ability to allocate or Storage deallocate volumes on a remote Provisioning Tool storage network and to save and restore network-storage configurations. IBM Server Storage Provisioning Tool is a free, downloadable extension for IBM Director Server, IBM Director Console, and IBM Director Agent. v Requires BladeCenter Management v Requires Remote Deployment Manager to perform some operations for Level-0 and Level-1 managed objects. v Ensure that the following hardware is present in your environment: BladeCenter Chassis Management Module Fibre Switch Module (IBM-supported devices such as QLogic or Brocade Switch Module) Ethernet Switch Module Blade server containing a hard drive and IBM-supported Host Bus Adapter (HBA) Remote Fibre Storage Device Fibre small form factor pluggable (SFP) modules required for specific devices, including Fibre cabling None.
h Rack Manager Provides the ability to group managed systems and devices, networking devices, power devices, and monitors with a rack in order to visually represent an existing rack in your environment. Rack Manager is an optional feature of IBM Director Server.
98
Table 42. IBM Director optional component planning worksheet (continued) Optional component h IBM Director Remote Control Agent Description Provides the ability to manage a remote system running Windows by displaying the screen image of the managed system on a management console running Windows. IBM Director Remote Control Agent is an optional feature of IBM Director Server. h IBM Remote Deployment Manager extension Enables you to remotely perform configuration, deployment, and retirement operations on both IBM and non-IBM systems, including updating system firmware, changing configuration settings, installing operating systems and applications, backing up and recovering primary partitions, and erasing data from disks. IBM Remote Deployment Manager is a separately purchased extension for IBM Director Server. See www.ibm.com/servers/eserver/ xseries/systems_management/ sys_migration/rdm.html. h Software Distribution Premium Edition extension Provides additional capabilities to the Software Distribution task, including: v Import software and build software packages that use the InstallShield, Windows Installer, RPM Package, or AIX InstallP wizards v Export a software package for use on another management server or as a backup v Restore i5/OS libraries, objects and installed programs Software Distribution Premium Edition is a separately purchased extension for IBM Director Server. See publib.boulder.ibm.com/ infocenter/eserver/v1r2/topic/ swdistpe_5.20/frl0_main.html. Software Distribution Premium Edition must be purchased in addition to IBM Director. IBM Remote Deployment Manager must be purchased in addition to IBM Director. Important considerations None.
Chapter 2. Planning
99
Table 42. IBM Director optional component planning worksheet (continued) Optional component h System Availability Description Important considerations
Allows you to analyze the None. availability of a managed system or group by viewing statistics about managed-system uptime and downtime through reports and graphical representations. System Availability is a free, downloadable extension for IBM Director Server, IBM Director Console, and IBM Director Agent. See publib.boulder.ibm.com/ infocenter/eserver/v1r2/topic/ sysavail_5.20/fqq0_main.html.
h IBM Virtualization Manager extension
Allows you to view resource health and relationships between your physical and virtual resources, and create, modify, and migrate virtual servers using IBM Director. IBM Virtualization Manager is a free, downloadable extension for IBM Director Server, IBM Director Console, and IBM Director Agent. See www.ibm.com/servers/ eserver/xseries/ systems_management/ ibm_director/extensions/ vmm.html.
IBM Director Server and IBM Director Console must be installed on Windows.
h System x Management Extension
Enables System x-specific functionality, including: v Server Configuration Manager task v Management Processor Command-Line Interface v System x power management functions xSeries Support is an optional feature of IBM Director Server and IBM Director Console.
None.
100
Table 42. IBM Director optional component planning worksheet (continued) Optional component h z/VM Center extension Description Important considerations
Allows you to provision Linux v To be able to use the z/VM systems on virtual hardware that is Center subtasks Virtual Server based on real IBM System z Deployment or Server hardware and the z/VM Complexes, you must purchase hypervisor, using a graphical user the IBM Director z/VM Center interface that runs on IBM Director extension of IBM Director for Console. Linux on System z, V5.20. z/VM Center is an extension for IBM Director Server and IBM Director Console on AIX, Linux, and Windows. On i5/OS, the z/VM Center extension is automatically installed. See publib.boulder.ibm.com/ infocenter/eserver/v1r2/topic/ zvmcenter_5.20/zvm0_main.html. v Requires a System z server running one of the following guest operating systems: SUSE Linux Enterprise Server 10 for IBM System z SUSE Linux Enterprise Server 9 for IBM System z Red Hat Enterprise Linux AS, version 4.0, for IBM System z on z/VM 5.2 or z/VM 5.3
Licensing requirements for IBM Director components and extensions

Licensing requirements for the management server and managed systems are an important consideration when planning to deploy IBM Director. Review the following licensing requirements and determine what licenses you will need to obtain.
IBM Director Server

A license for IBM Director Server is included with the purchase of each of the following IBM products: v IBM BladeCenter servers v IBM System i platforms v IBM System p servers v IBM System x servers v IBM System z mainframes This license includes authorization for one installation of IBM Director Server on the purchased server, and updates to IBM Director Server at no charge. Each licensed installation of IBM Director Server can manage up to 5000 Level-2 systems (with IBM Director Agent installed) if licenses for each IBM Director Agent installation are obtained. This constraint does not apply to Level-1 or Level-0 managed systems. To manage more than 5000 Level-2 managed systems, you must use multiple licensed instances of IBM Director Server. To install IBM Director Server on a non-IBM management server, you must obtain a license from IBM. See Obtaining licenses for IBM Director components and extensions.
Chapter 2. Planning
101

A separate license is not required for IBM Director Console. You can install as many instances of IBM Director Console as you need.
IBM Director Agent

A license for IBM Director Agent is included with the purchase of most IBM Intel-compatible systems and BladeCenter servers, including the following products: v IBM BladeCenter and BladeCenter T chassis v IBM blade servers v IBM IntelliStation workstations v IBM System i platforms v v v v v v v IBM IBM IBM IBM IBM IBM IBM System p servers System x servers System z mainframes System Storage Network Attached Storage (NAS) products SurePOS point-of-sale systems ThinkCentre, NetVista, and PC desktop computers ThinkPad mobile computers
For a complete list of IBM products that are entitled to an IBM Director Agent license, see the IBM Director Hardware and Software Support Guide document. To see the latest version of this document, go to the IBM Director Support Web Page at www.ibm.com/systems/management/director/ and click the Documentation and resources link. Note: Many Lenovo desktop and notebook systems also include a license for IBM Director Agent. In addition, each licensed installation of IBM Director Server includes a license for 20 installations of IBM Director Agent on non-IBM systems managed by that installation of IBM Director Server. Important: These 20 IBM Director Agent licenses for non-IBM systems are not transferable and cannot be combined. That is, they are valid only for an IBM Director Server installed on the particular server purchased. For example, if you buy two System x servers and install IBM Director Server on only one of them, you are entitled to install IBM Director Agent on only 20 non-IBM systems. If you install IBM Director Server on both servers, each management server is licensed to manage only 20 non-IBM systems unless you purchase additional IBM Director Agent licenses. To install IBM Director Agent on additional non-IBM systems, you must obtain a license from IBM. See Obtaining licenses for IBM Director components and extensions.
IBM Director Core Services and agentless managed systems

A separate license is not required for managed systems that do not have IBM Director Agent installed. This includes: v Level-1 managed systems (IBM Director Core Services installed)
102
v Level-0 managed systems (no management agent software installed)
IBM Director extensions

A separate license is required for each of the following IBM Director extensions: v Capacity Manager v Remote Deployment Manager extension v Software Distribution Premium Edition v z/VM Center
External database
Installation of an external database is required for many IBM Director functions. The Apache Derby database that is included with IBM Director (except on i5/OS), and the IBM DB2 database that is part of the i5/OS operating system, are databases you can use without obtaining additional licenses. If you use another database, ensure that you have obtained any required license for the installation.
Choosing between standard and express installation of IBM Director Server

Before installing IBM Director Server, you must decide whether you will use the express installation option, or perform a standard installation. In IBM Director 5.20, you can choose to perform an express installation of IBM Director Server, which simplifies the installation process by automatically selecting and configuring some options and features that are typically used by small- to medium-sized businesses. Note: The express installation option is not available for management servers running i5/OS. Consider the following differences between performing an express installation and performing a standard installation.
Standard installation Database You select the database you will use, and provide configuration information during installation. Express installation Windows only: Apache Derby database is automatically installed and configured for IBM Director. For express installations on other operating systems, database selection is the same as for a standard installation. Event action plans No event action plans are created by default. An event action plan is created on installation which automatically creates Update Manager profiles when inventory is collected for new types of managed objects. Additionally, when you first start IBM Director Server, the Event Action Plan Wizard is started so you can create event action plans.
Chapter 2. Planning
103
Standard installation Event Action Plan Wizard The standard Event Action Plan Wizard is available.
Express installation The Event Action Plan Wizard does not include the Security events or IBM Director Agent offline event filters. In addition, you cannot specify a time range for event action plans. The time range is always 24 hours.
Extensions to IBM Director
Extensions can be installed, Extensions can be installed, providing the specific requirements providing the specific requirements for the extension are met. for the extension are met. Before installing the extensions, add the Standard installation options to the IBM Director Express installation. You must manually configure discovery preferences and start discovery. When you start IBM Director the first time, you are prompted to enter Level-0 discovery options in a wizard, and then discovery is performed. Ticker-tape display of security events is automatically configured. The following subset of tasks is available to users after installation: v Inventory v Event Action Plans v Event Log v File Transfer v Hardware Status v Resource Monitors v Scheduler v Software Distribution v Update Manager After installation, you can make other tasks available to users if you need them.
Initial discovery of managed systems
Security Tasks
You must manually configure security event notifications. All tasks are available to users after installation.
Choosing the IBM Director Server installation options

When you install IBM Director Server using a standard installation, you must choose the features, encryption settings, network settings, and file locations for your installation. Note: If you are using the express installation option, none of these options are available. IBM Director Server is installed in the default location, and Advanced Encryption Setting (AES) encryption is enabled. When you install IBM Director Server, you must make various choices. Use the Worksheet: Installing IBM Director Server on page 362 to record the decisions that you make as you work through this procedure. Complete the following steps: 1. Determine the optional features that you want to install. You can choose from the following features: IBM Director Remote Control Agent Select this feature if you want to use the Remote Control task to remotely control the management server.
104
BladeCenter Management Select this feature if your environment includes BladeCenter units. Rack Manager Select this feature if you want to use the Rack Manager task. You can use the Rack Manager task to build a realistic, visual representation of a rack and its components. 2. Determine the location where you want to install IBM Director Server. By default, IBM Director Server is installed in the following locations.
Operating System i5/OS Linux or AIX Windows Location /QIBM/ProdData/Director/ /opt/ibm/director d:\Program Files\IBM\Director
d is the drive letter of the hard disk drive. 3. Determine the IBM Director service account information. You need to provide the following information when you install IBM Director Server: v Computer name v User name v Password 4. Determine whether you want to encrypt the data that is transmitted between IBM Director Server and IBM Director Agent. If you want to encrypt the data transmissions, you can select from the following encryption settings. Advanced Encryption Setting (AES) A block cipher algorithm, also known as Rijndael, used to encrypt data transmitted between managed systems and the management server, which employs a key of 128, 192, or 256 bits. AES was developed as a replacement for DES. Data Encryption Standard (DES) A cryptographic algorithm designed to encrypt and decrypt data using a private key. Triple Data Encryption Standard A block cipher algorithm that can be used to encrypt data transmitted between managed systems and the management server. Triple DES is a security enhancement of DES that employs three successive DES block operations. 5. Determine where software-distribution packages are located. By default, software-distribution packages are located in the following directories:
Operating System i5/OS Linux or AIX Windows Location /QIBM/UserData/Director/directory /opt/ibm/director/directory d:\Program Files\IBM\Director\directory
directory is one of the following strings: v SwDistPk v SwPkInst
Chapter 2. Planning
105
IBM Director Server creates software-distribution packages in the SwDistPk directory; when software packages are distributed to the instance of IBM Director Agent running on the management server, these packages are placed in the SwPkInst directory. 6. Determine the network settings: a. Will you enable all or only certain network interface cards (NICs)? If you enable an individual NIC, IBM Director Server will receive only those data packets that are addressed to the individual adapter. b. Determine the network timeout setting, which is the number of seconds that IBM Director Server waits for a response from IBM Director Agent. By default, the network timeout setting is 15 seconds. c. Determine whether you want to enable Wake on LAN. 7. (If IBM Director Remote Control Agent is installed) Determine which remote control options you want to enable: v Require user authorization for system access v Disable screen saver v Disable background wallpaper
Choosing where to install IBM Director Server

Before installing IBM Director, you must choose one or more management servers on which you will install IBM Director Server. A number of factors should influence your choice of management servers, including the kind, number, and distribution of the systems and objects you will be managing, the tasks you will be performing with IBM Director, and the database you will use. In some cases, you might want to install more than one instance of IBM Director Server. When deciding where to install IBM Director Server, evaluate the following considerations: v Consider installing IBM Director Server on a blade to manage a BladeCenter chassis. IBM BladeCenter chassis may be managed using IBM Director Server installed either on a blade in the BladeCenter, or on a separate management server. Refer to Preparing to manage a BladeCenter on page 167 for detailed information. v For Windows installations, do not install IBM Director Server on a domain controller, due to the following possible consequences: Its high resource usage might degrade domain controller performance. If you install IBM Director Server on a domain controller and then demote the domain controller, you no longer can access IBM Director Console. Unless the IBM Director service account has domain administrator privileges, you cannot restart IBM Director Server. v Consider installing multiple instances of IBM Director Server. Installing IBM Director Server on multiple management servers may be helpful in the following situations: You want to manage more than 5000 Level-2 systems. The IBM Director Server license allows you to manage only up to 5000 Level-2 systems, if you have licenses for IBM Director Agent on those managed systems. The number of Level-0 and Level-1 systems you can manage is limited only by the available resources of the management server and the network.
106
The systems that you want to manage are in several geographic locations or are owned by multiple system administrators. You want to manage each BladeCenter with an installation of IBM Director Server on a blade in the chassis. v Consider the kind of database you wish to use. You may wish to use a particular database for IBM Director data, to facilitate data-mining activity or for other reasons. Not all databases are supported for all IBM Director Server installation locations. Refer to Choosing the IBM Director database application for detailed information. v Consider the extensions you wish to install, and their requirements. Some extensions, such as Capacity Manager, can require large amounts of storage. Select a management server (or multiple management servers) which will allow extensions to be installed and continue functioning even if the network grows. The External Application Launch Wizard requires that IBM Director Server be installed in the default installation path.
Choosing the IBM Director database application

Some IBM Director functions require use of an external database, but not all databases support the same functionality with IBM Director. You should choose a supported database that meets the needs of your installation. Note: If you install IBM Director Server using the express installation option, the Apache Derby database is installed. IBM Director Server uses the database to store inventory information in a central point. This inventory information then can be used for managing your assets. Before you install IBM Director Server, you should decide which database you want to use. Some installations will not require a database installed. On all operating systems except for i5/OS, the Apache Derby database is embedded with the IBM Director Server installation. For i5/OS, IBM Director Server can use the IBM DB2 database that is part of the i5/OS operating system. Use the following steps to determine the appropriate database application for your installation of IBM Director. 1. Review the advantages and disadvantages of the different database installation types.
Table 43. DBMS installation type embedded DBMS The DBMS is installed on the management server as part of the IBM Director Server installation, and shares the Java Virtual Machine with IBM Director. Advantages v easy configuration Disadvantages
v limitations of Apache Derby database: a limited number of managed objects and inability to v lower resource usage than query database with a local DBMS installation third-party application v does not require a separate while IBM Director Server server for the DBMS is running v no additional license required v not available on i5/OS
Chapter 2. Planning
107
Table 43. (continued) DBMS installation type local DBMS The DBMS is installed on the management server on which IBM Director Server is installed. remote DBMS The DBMS is installed on a different server than the management server, and accessed remotely by IBM Director Server. Advantages Disadvantages
v does not require a separate v highest resource usage on server for the DBMS management server
v lowest resource usage on management server
v requires a separate server for the DBMS
v potential to use an existing v connectivity problems with DBMS and avoid database server will affect purchasing an additional IBM Director DBMS license
2. Review the supported databases for your management server and the type of installation that you prefer. Depending on where you are installing IBM Director Server, you have one or more possible choices for your database.
Table 44. Database applications supported by IBM Director 5.20.1 Database Apache Derby Supported database versions v V10.2 (included with IBM Director Server on AIX, Linux, and Windows) v version 9.1 with Fix Pack 2 v version 8.2 with Fix Pack 7 v version 8.1 with Fix Pack 14 IBM DB2 Universal Database for System i (part of i5/OS) Microsoft SQL Server v Microsoft SQL Server 2005 with Service Pack 1 v Microsoft SQL Server 2000 with Service Pack 4 AIX Embedded i5/OS Linux Embedded Windows Embedded
Local or remote
Local
(see Limitations of v Microsoft SQL Server 2005 support on Express Edition with Service page 91) Pack 1 v Microsoft SQL Server 2000 Desktop Engine (also called MSDE 2000) with Service Pack 4 Oracle v version 10g release 2 v version 10g release 1 (Oracle Server) v version 9.2 PostgreSQL v version 8.1 v version 7.4 v version 7.3 Local or remote
Local
Local or remote
3. Review the additional database selection criteria listed in Table 45 on page 109 to determine which database best meets your needs. All supported databases provide the following functionality in IBM Director:
108
Using inventory functionality If you will be performing inventory tasks in IBM Director, a database is required to store the inventory information. Using dynamic groups If you will be using dynamic managed-object groups in IBM Director, a database is required to store the information. For the following additional criteria, not all databases provide the desired function.
Table 45. Additional database selection criteria Accessing data with a third-party tool while IBM Director is running No No
Database no database Apache Derby
Large managed network (> ~500 managed objects) Yes No
Performing capacity management No Yes, but support might be limited for larger networks. See Planning for Capacity Manager in the Capacity Manager Information Center. Yes Yes Yes, but support might be limited for larger networks. See Planning for Capacity Manager in the Capacity Manager Information Center. Yes Yes
IBM DB2 Universal Database Microsoft SQL Server 2005 or Microsoft SQL Server 2000
Yes Yes
Yes Yes No
Microsoft SQL Server 2005 Express Yes Edition or Microsoft SQL Server 2000 Desktop Engine (also called MSDE 2000)
Oracle PostgreSQL
Yes Yes
Yes Yes
These criteria are described more fully below: Accessing data with a third-party tool while IBM Director is running Database mining by other applications might be useful in your environment. If you will need to access IBM Director data such as inventory or group information while IBM Director is running, you cannot use Apache Derby. Instead, DB2, Oracle, or SQL Server are good choices.
Chapter 2. Planning
109
Large managed network (> ~500 managed objects) If you will be managing a large network (approximately 500 managed objects or more), Apache Derby is probably not sufficient to meet your database needs. Performing capacity management Capacity management is performed with the optional Capacity Manager extension for IBM Director. For larger networks, both Apache Derby, MSDE 2000, and SQL Server Express Edition databases might not be sufficient to perform capacity management tasks. The ability to generate a report in SQL format is available on a Windows platform only. Only Microsoft SQL Server 2000 and Microsoft SQL Server Desktop Engine 2000 (MSDE 2000) are supported. The database to which Capacity Manager exports information is independent of the database used by IBM Director. As a result, information is not shared between the two. Make sure the ODBC default database uses the Capacity Manager database, which is named cmdb.
Choosing the management level for managed systems

IBM Director provides three different levels of management for managed systems and managed objects. For each managed system, you need to choose the management level that provides the management functionality you need for that managed system. Depending on the type of managed object and the management tasks you need to perform, you can choose the best management level for the managed system. IBM Director has three management levels: Level 0: Agentless Managed systems without any IBM Director software installed. Level 1: IBM Director Core Services Managed systems with IBM Director Core Services installed. Level 2: IBM Director Agent Managed systems with IBM Director Agent installed. These three management levels have different requirements and provide differing levels of management functionality in IBM Director. For each managed object, review the Table 46 and decide what level of management is required.
Table 46. Management-level selection worksheet1 Level 1: IBM Director Core Services Level 2: IBM Director Agent
Criteria Managed object types IBM systems running AIX IBM systems running i5/OS IBM systems running Linux
Level 0: Agentless
X X X X
110
Table 46. Management-level selection worksheet1 (continued) Level 1: IBM Director Core Services X Level 2: IBM Director Agent X X X X X X X X X X X X X X
Criteria IBM systems running Linux and supporting either the SSH2 or DCOM3 protocol IBM systems running NetWare IBM systems running Windows IBM systems running Windows and supporting either the SSH or DCOM protocol Non-IBM systems running Linux and supporting either the SSH or DCOM protocol Non-IBM systems running Windows and supporting either the SSH or DCOM protocol Other managed objects, including management processors supporting SSH, racks, and SNMP devices Managed object attributes Managed system does not use TCP/IP Managed system has a supported workgroup/enterprise management agent installed Minimal additional memory constraint on managed system No additional memory constraint on managed system No IBM Director Agent license required No software required on managed system Needed functionality Asset ID Capacity Manager CIM Browser Event action plans Event log File Transfer Hardware status Electronic Service Agent (Linux & Windows) IBM Virtualization Manager (Linux & Windows) Remote control (Windows only) Remote session to all supported managed systems and devices Remote session to SNMP devices and systems supporting SSH Restart the managed system ServeRAID Manager
4
Level 0: Agentless X
X X
X X X X X
X X X X X X X X X X X X X X X X X X X X X X X
Chapter 2. Planning
111
Table 46. Management-level selection worksheet1 (continued) Level 1: IBM Director Core Services Level 2: IBM Director Agent X X X X
Criteria System Availability Upgrade to Level-1 Agent Upgrade to Level-2 Agent
Level 0: Agentless
Notes: 1. In this table, systems include servers, desktop computers, workstations, and mobile computers. 2. SSH = Secure Shell 3. DCOM = Distributed Component Object Model 4. Event action plans can be applied to Level-0 managed systems; however, most of the events that can trigger an Event Action Plan are not generated for Level-0 managed systems.
Planning for virtual environments

This topic provides planning information for the installation of IBM Director in a virtual environment.
IBM Director support for Microsoft Virtual Server operating-system environments

IBM Director provides managed-system support for servers running Microsoft Virtual Server. You can install IBM Director Agent or IBM Director Core Services on Microsoft Virtual Server guest operating systems. The operating system must be supported by both IBM Director and Microsoft Virtual Server. For detailed information about IBM Director Agent and IBM Director Core Services support for Microsoft Virtual Server and its guest operating systems, see Supported operating systems. When installing IBM Director Agent or IBM Director Core Services on a Microsoft Virtual Server guest operating system, use the installation instructions for your selected operating system.
IBM Director support for VMware operating-system environments

IBM Director provides managed-system support for servers running VMware. You can install IBM Director Agent or IBM Director Core Services on: v VMware Console. v VMware guest operating systems. The operating system must be supported by both IBM Director and VMware. v (VMware GSX only) VMware host operating systems. The operating system must be supported by both IBM Director and VMware.
112
For detailed information about IBM Director Agent and IBM Director Core Services support for VMware and its guest and host operating systems, see Operating systems supported by IBM Director 5.20. When installing IBM Director Agent or IBM Director Core Services on VMware Console, use the Linux for xSeries installation instructions. When installing IBM Director Agent or IBM Director Core Services on a VMware guest operating system or host operating system, use the installation instructions for your selected operating system. The IBM Director tasks and features that are supported on VMware Console and its guest operating systems varies. For detailed information about which tasks and features are supported, see Support of IBM Director tasks across operating systems on page 80.
IBM Director support for z/VM operating-system environments

You can run IBM Director components and z/VM Center on supported z/VM guest operating systems. You can install IBM Director Server, IBM Director Console, IBM Director Agent, or IBM Director Core Services on z/VM guest operating systems. The operating system must be supported by both IBM Director and z/VM (see Supported operating systems). The IBM Director tasks and features that are supported on z/VM guest operating systems vary. For detailed information see Support of IBM Director tasks across operating systems. You can also install and set up z/VM Center. With z/VM Center you can virtualize your System z hardware resources into z/VM virtual servers (that is, guest virtual machines) and to deploy Linux instances on them. You interact with z/VM through a graphical user interface (GUI) that runs on the IBM Director Console.
Planning to update IBM Director

Before updating an installation of IBM Director, you need to consider compatibility issues relating to the versions you already have installed and the version to which you wish to update, and plan to back up user-configuration data which could be lost during an update. 1. Always read the Release Notes for any update to IBM Director that you are considering installing. 2. Consider the following general compatibility rules which apply to most versions of IBM Director: v The versions of IBM Director Server and IBM Director Console must be the same, even when they are installed on different systems. v Versions of components that are installed on the same system, such as IBM Director Console and IBM Director Agent, must be the same. v The version of IBM Director Server must always be the same or later than the version of any IBM Director Agent or IBM Director Core Services installed on managed systems. 3. Consider what user-configuration data might need to be backed up. Updating IBM Director Server usually occurs without incident; however, with proper
Chapter 2. Planning
113
planning, you can ensure that no user-configuration data could be lost. The following data types are potentially susceptible to being overwritten when updating IBM Director Server: v dynamic-group configuration data v BladeCenter configuration profiles v event action plans v Private security key (dsa*.pvt) files See the related topics for information about backing up user-configuration data.
Version compatibility of IBM Director version 5.20 components

Some IBM Director 5.20 components can work with IBM Director components from previous versions of the software. As with previous versions of IBM Director, the following rules apply to the version compatibility of IBM Director version 5.20 components: v The versions of IBM Director Server and IBM Director Console must be the same, even when they are installed on different systems. v Versions of components that are installed on the same system, such as IBM Director Console and IBM Director Agent, must be the same. v The version of IBM Director Server must always be the same or later than the version of any IBM Director Agent or IBM Director Core Services installed on managed systems. See Table 47 for a complete listing of compatible IBM Director component versions for each IBM Director Version 5.20 component.
Table 47. Compatibility of IBM Director Version 5.20 components with other component versions Compatible Compatible Compatible versions of IBM Compatible versions of IBM versions of IBM Director versions of IBM Director Core Director Server Console Director Agent Services N/A 5.20 5.20, 5.10.3, 5.10.2, 5.10.1, 5.10, 4.22, 4.21, 4.20.2, 4.20, 4.12, 4.11, 4.10.2, 4.10 5.20, 5.10.3, 5.10.2, 5.10.1, 5.10, 4.22, 4.21, 4.20.2, 4.20, 4.12, 4.11, 4.10.2, 4.10 N/A N/A 5.20, 5.10.3, 5.10.2, 5.10.1, 5.10
IBM Director Version 5.20 IBM Director Server 5.20
IBM Director Console 5.20
5.20
N/A
5.20, 5.10.3, 5.10.2, 5.10.1, 5.10
IBM Director Agent 5.20 IBM Director Core Services 5.20
5.20 and later 5.20 and later
5.20 and later 5.20 and later
N/A N/A
Version compatibility of IBM Director version 5.20.1 components

Some IBM Director 5.20.1 components can work with IBM Director components from previous versions of the software.
114
As with previous versions of IBM Director, the following rules apply to the version compatibility of IBM Director version 5.20.1 components: v The versions of IBM Director Server and IBM Director Console must be the same, even when they are installed on different systems. v Versions of components that are installed on the same system, such as IBM Director Console and IBM Director Agent, must be the same. v The version of IBM Director Server must always be the same or later than the version of any IBM Director Agent or IBM Director Core Services installed on managed systems. See Table 48 for a complete listing of compatible IBM Director component versions for each IBM Director Version 5.20.1 component.
Table 48. Compatibility of IBM Director Version 5.20.1 components with other component versions Compatible Compatible Compatible versions of IBM Compatible versions of IBM versions of IBM Director versions of IBM Director Core Director Server Console Director Agent Services N/A 5.20.1 5.20.1, 5.20, 5.10.3, 5.10.2, 5.10.1, 5.10, 4.22, 4.21, 4.20.2, 4.20, 4.12, 4.11, 4.10.2, 4.10 5.20.1, 5.20, 5.10.3, 5.10.2, 5.10.1, 5.10, 4.22, 4.21, 4.20.2, 4.20, 4.12, 4.11, 4.10.2, 4.10 N/A N/A 5.20.1, 5.20, 5.10.3, 5.10.2, 5.10.1, 5.10
IBM Director Version 5.20.1 IBM Director Server 5.20.1
IBM Director Console 5.20.1
5.20.1
N/A
5.20.1, 5.20, 5.10.3, 5.10.2, 5.10.1, 5.10
IBM Director Agent 5.20.1 IBM Director Core Services 5.20.1
5.20.1 and later 5.20.1 and later
5.20.1 and later 5.20.1 and later
N/A N/A
IBM Director version 5.20.1 is compatible with the following versions of IBM Director extensions:
Table 49. Compatibility of IBM Director extensions with IBM Director version 5.20.1 Extension Capacity Manager Electronic Service Agent External Application Launch Wizard Hardware Management Console PowerExecutive Remote Deployment Manager ServeRAID Manager IBM Server Storage Provisioning Tool Software Distribution Premium Edition Compatible versions 5.20 System x DE V5.0, System x DE Linux V5.0 5.20 5.20.1 2.00.1, 2.00 4.30.1, 4.30 5.20 5.20.1 5.20
Chapter 2. Planning
115
Table 49. Compatibility of IBM Director extensions with IBM Director version 5.20.1 (continued) Extension System Availability IBM Virtualization Manager z/VM Center Compatible versions 5.20 1.1 5.20.1
Planning for events

An event is an occurrence of a predefined condition relating to a specific managed object. There are two types of events: alert and resolution. An alert is the occurrence of a problem relating to a managed object. A resolution is the occurrence of a correction or solution to a problem relating to a managed object. Note: In the IBM Director product, there are tasks and features that use the word alert in place of the word event. Also, some tasks use the word notification instead of event. Sources that can generate events include, but are not limited to, the following programs and protocols: v IBM Director Agent v IBM Director Core Services Microsoft Windows event log Windows Management Instrumentation (WMI) SNMP through out-of-band communication Intelligent Platform Management Interface (IPMI) Platform Event Traps (PET) through out-of-band communication v IBM service processors through out-of-band communication v v v v To monitor one or more events, you must create an event filter that contains an event type from one of these sources, use the event filter as part of an event action plan, and then apply the event action plan to a managed object. Events from the Windows event log are displayed in the Windows event log tree in the Event Type Filter Builder. Events from WMI are displayed in the Common Information Model (CIM) tree. Successful use of event notification depends on careful planning. Consider the following questions: 1. Which events can be monitored on the managed object? a. Which of these events are useful to my management strategy? b. What configuration is required for the managed object to send event notifications? 2. How should event notifications be sent to IBM Director? See the IBM Director Events Reference for additional information.
Planning events to be monitored

Before configuring IBM Director and your managed systems, you should plan how events will be sent to IBM Director and how event notifications will be sent to the personnel who need to receive them.
116
v Consider how events will be sent by the managed systems to IBM Director Server. When IBM Director discovers IBM service processors or BladeCenter management modules, it automatically configures them to send events using the network interface with IBM Director Server. Notes: For Ethernet connections, configure either a static IP address or enable the use of DHCP. BladeCenter management modules and the Remote Supervisor Adapter and Remote Supervisor Adapter II service processors support DHCP; however, the use of a static IP address is potentially more reliable than using DHCP. A static address means that the failure or inaccessibility of DNS and/or DHCP servers will not prevent access to the management module or service processor. If a BladeCenter management module or Remote Supervisor Adapter II is set to use DHCP but does not receive an address from the DHCP server within two minutes, the management module or adapter automatically sets its address as 192.168.70.125. v Consider how you want event notifications to be sent to the personnel who need to receive them. Using event action plans, you can configure IBM Director to send notification of particular events or event types via e-mail or mobile phone text message, or by starting an application on the management server or on a managed system. Alternatively, you can configure management modules and some service processors to send event notifications directly to personnel or other management applications besides IBM Director using means such as SNMP traps or e-mail. This kind of event notification is not enabled by default, but can be configured using the BladeCenter Configuration Manager task in IBM Director or through a direct connection to the service processor or management module. These events are broken down into the following three categories: - Critical events, such as Temperature outside critical thresholds or Power supply failure. - Warning events (non-critical), such as Redundant power supply failure or Voltage outside warning thresholds. - System events, such as Power off, Server loader timeout value is exceeded, or Predictive Failure Analysis (PFA) notification. Notes: For SNMP, decide which version of SNMP to use (v1 or v3). Enable traps and the SNMP agent, and configure the IP address. If using SNMPv1, configure the community name. If using SNMPv3, configure the user profile. For e-mail notifications, configure the SMTP server. If you enable timeout events (alerts), you also must plan to enable those timeouts.
Planning for event action plan implementations

To plan and design an event action plan, you must determine what the goal of the event action plan is. Consider which managed objects you intend to target with the event action plan. You can target all managed objects, a subgroup of managed objects, or a specific managed object.
Chapter 2. Planning
117
You can structure event filters and event actions in different ways. This section presents some of the possible structures that you can use. Remember that many event action plans might include each of the elements of each of the structures that are presented. When designing your event action plan structure, consider all the managed objects in groups. Start by designing an event action plan that contains events that apply to the largest number of objects. Then, create event action plans that cover the next largest group of managed objects, and continue to group them until you reach the individual managed-object level. When doing this, remember that each managed object can be a member of multiple groups. When planning an event action plan structure, consider the following issues: v What do you want to monitor on most or all of the managed objects of the same type as a whole? This answer determines the grouping and event filters for your event action plans. v How will you group your managed objects as smaller groups, according to the additional events you want to monitor? The smaller groups are usually based on the following criteria: Managed-object manufacturer, for vendor-specific events Function of the managed object, for services and resources specific to that function v What type of managed objects are you monitoring? v What is the function of the managed object? v What are the key monitors for the managed object? v Are there other managed objects for which you want to use the same monitors?
Managing and monitoring systems with event action plans

This topic provides information about events and event action plans; how to plan, design, and build event action plan implementations; and how to work with existing event action plans. You can use event action plans to specify actions that occur as a result of events that are generated by a managed object. An event action plan is composed of two types of components: v One or more event filters, which specify event types and any related parameters v One or more event actions, which occur in response to filtered events You can apply an event action plan to an individual managed object, several managed objects, or a group of managed objects. By creating event action plans and applying them to specific managed objects, you can be notified by e-mail or pager, for example, when a specified threshold is reached or a specified event occurs. You also can configure an event action plan to start a program on a managed object and change a managed-object variable when a specific event occurs. You can use process-monitor events and resource-monitor events to build an event action plan. Successful implementation of event action plans requires planning and consideration of how you will implement them. In particular, developing and following strict naming conventions is important, so that you can easily identify what a specific plan does.
118
Note: After an Express Installation, when you first start IBM Director, the Event Action Plan wizard starts. You can use this wizard to create an event action plan.
Planning managed object grouping

Event action plans are best implemented by grouping all of your managed objects into both larger and smaller groups. The following criteria are examples of groupings: Type of managed object (servers, desktop computers, workstations, mobile computers, and network equipment) Each type of managed object has its own event action plans. By manufacturer Each managed-object manufacturer has its own event action plans. Many organizations have managed objects from multiple manufacturers. In this case, if manufacturer-specific event monitors are required, you might want to have manufacturer-specific event action plans for each type of managed object. By function Each function of the managed object has its own event action plans. Each group of managed objects performing specific roles has different events to monitor. For example, on all of your print servers, you might want to monitor the print spoolers and printers. By resources Event action plans are based on specific resources. Typically, these event action plans monitor a specific resource outside of those in the managed-object type of event action plan. These resource event action plans might apply to managed objects with more than one system function but not to all managed objects of the same type. By management technology If you have many devices that send SNMP traps, you can design event action plans to act on those events.
Structuring event action plans

Determine the overall structure of your event action plans before you create them. A little planning in advance can prevent wasted time and duplication of effort. Consider the following examples of event action plan structures: A structure based on the areas of responsibility of each administrator Servers are maintained and managed by one group of personnel, and desktop computers and mobile computers are maintained by another group of personnel. A structure based on administrator expertise Some organizations have personnel that specialize in particular types of technology. These individuals might be responsible for complete managed objects or only certain software running on these managed objects. A structure based on managed-object function Servers performing different functions are managed differently. A structure based on the type of event Examples of some structures based on the type of event are monitoring a specific process and monitoring for hardware events.
Chapter 2. Planning
119
A structure based on workday shifts Because you can set up the event filters to be active during certain parts of certain days, you can structure your event action plans and event filters according to the shift that will be affected by the events that are occurring.
Structuring event filters

You can use an event filter to capture a single event or multiple events. The following list includes some of the criteria that you can use to determine whether to include an event with other events: v All managed objects that are targeted for the filter are able to generate all events that are included in the filter. If the managed object does not generate the event for which the filter is defined, the filter will not be effective on that managed object. v The event actions that will be used to respond to the event are the same for all targeted objects. v The other event filter options besides the event type are common for all targeted objects. These settings include the times the event filter is active, the severity of the event, and other attributes. Event action plans can include event filters with event types that are not generated by all managed objects. In such instances, you can apply the event action plan to those managed objects, but it will have no effect. For example, if an event filter is based on a ServeRAID event and that event action plan is applied to managed objects that do not have a ServeRAID adapter installed, the event filter has no events to filter, and therefore, no actions are performed. If you understand this concept, you can create more complex event action plans, and you can reduce the number of event action plans you have to build and maintain. All currently available event types are displayed in the tree on the Event Type page in the Event Filter Builder window. The currently installed tasks and extensions publish their events in the Event Type tree when IBM Director Server or IBM Director Agent starts. Note: Whether the events are published when IBM Director Server or IBM Director Agent starts depends on the tasks or extensions and how they are implemented. If you add an extension to your IBM Director installation, the extension might publish its events either when it is added to the installation or when the extension sends its first event. If the extension publishes when it sends its first event, only that event is published.
Planning IBM Director users and user groups

Before deploying IBM Director, you should determine what IBM Director user roles to define for your organization. In addition, you should determine the user authentication type that will best meet your needs. 1. Decide what kind of user authentication to use for IBM Director. The user authentication type (using a common Lightweight Directory Access Protocol (LDAP) server, or using accounts on the operating system of the management server) affects both the availability and security of IBM Director Server. With LDAP authentication, it is easy to implement common roles and access for users across multiple instances of IBM Director Server. However, the
120
LDAP server must be secure in order to avoid unauthorized access to management tasks and managed objects in IBM Director. Consider how IBM Director will be used to manage systems and objects in various locations. v Will a single management server be used for the entire organization, or will multiple management servers be used? v If multiple management servers will be used, will the same user accounts be needed on more than one of the management servers, or should user accounts be unique for each management server? v Is there an existing LDAP directory, such as IBM Directory Server or Microsoft Active Directory, for your organization? v How many users will be authorized to access IBM Director? Refer to the following table as a guide when deciding what kind of user authentication method to use for IBM Director.
User access to multiple management servers n/a n/a Suggested authentication method LDAP user accounts on management server user accounts on management server LDAP LDAP LDAP user accounts on management server user accounts on management server
Management servers one one
LDAP directory exists yes yes
Number of users many few
one
n/a
no
n/a
multiple multiple multiple multiple
yes yes no no
yes no yes yes
n/a n/a many few
multiple
no
no
n/a
2. Decide what kind of user roles to define for IBM Director users. The user roles you define will provide an organizational framework that will guide you when creating user groups, delegating management authority in IBM Director, and creating managed-object groups. User roles can be based on a job description, on the physical or geographic area of responsibility, or on other criteria. A user might have several different user roles simultaneously. Consider what kinds of access users should have in IBM Director. v Should management authority be allocated in part based on the location of managed objects? You might want to define user roles based on particular managed-object sites, whether the site is a room, an office building, or a country. v Should management authority be allocated in part based on the kind of managed object? You might want to define user roles for particular operating systems or for storage devices. v Should management authority be allocated in part based on organizational roles? You might want to define user roles that correspond to sets of
Chapter 2. Planning
121
privileges and tasks that can be performed in IBM Director, like software distribution, inventory collection, and configuring preferences for IBM Director Server. Depending on the users organizational role, the user probably needs access to only a subset of the available privileges and tasks. Other criteria can also be used when defining user roles for IBM Director. Whatever criteria are used to define user roles, remember that a user can have multiple roles.
122
Chapter 3. Installing
Before you install IBM Director Server, IBM Director Console, IBM Director Agent, IBM Director Core Services, or an IBM Director extension, make sure to review the information about how to prepare your environment for the installation, instructions for upgrading from previous releases, and recommendations for the initial configuration.
Preparing to install IBM Director

Before installing IBM Director make sure that systems and environments that you use are configured to work with IBM Director and that the prerequisite software and communication protocols have been installed.
Obtaining licenses for IBM Director components and extensions

Licenses are needed for IBM Director Server, IBM Director Agent, and some IBM Director extensions. Review the Licensing requirements for IBM Director components and extensions topic to determine what licenses you need to purchase. 1. Obtain licenses for IBM Director components and extensions as described in the following table.
Products System i platforms Licenses IBM Director Server and IBM Director Agent licenses are included with the purchase of System i platforms. To purchase licenses for Software Distribution Premium Edition (5722-DR1), contact your sales representative. System p platforms IBM Director Server and IBM Director Agent are not shipped with System p platforms. You can order IBM Director for no additional charge by contacting your sales representative. To purchase licenses for Software Distribution Premium Edition (5765-DR1), contact your sales representative.
123
Products System x servers
Licenses IBM Director Server and IBM Director Agent are included with the purchase of IBM System x server and IBM BladeCenter. This license includes authorizations for one installation of IBM Director Server, up to 20 installations of IBM Director Agent on non-IBM systems, and unlimited installations of IBM Director Console. To purchase licenses for IBM Director Server, IBM Director Agent, Capacity Manager extension, Remote Deployment Manager extension, Software Distribution Premium Edition extension, complete the following steps: 1. Navigate to the IBM Director Ready to buy Web Page at http://www03.ibm.com/systems/management/ director/buy.html 2. Click on the product you need and follow the instructions provided. Note: These licenses include a one year subscription services contract entitling you to free updates during that period.
System z platforms
IBM Director Server and IBM Director Agent are not shipped with System z platforms. You can order IBM Director for Linux on System z (5648-DR1) for no additional charge. Licenses must be purchased for the z/VM Center and Software Distribution Premium Edition. To order media or purchase licenses, contact your sales representative or complete the following steps: 1. Navigate to the IBM ShopzSeries Web Page at www.ibm.com/software/ ShopzSeries. 2. When ordering, specify the Package type as z/VM - VM SDO version 5.2 and the Group as VM - System Support. 3. Purchase the z/VM Center extension or Software Distribution Premium Edition. 4. To receive Internet delivery, select Internet for preferred media.
non-IBM hardware
Licenses must be purchased for IBM Director Server, IBM Director Agent, Capacity Manager extension, Remote Deployment Manager extension, and Software Distribution Premium Edition extension. To purchase licenses, follow the steps that are provided for System x servers.
2. Optional: To purchase software subscription services for IBM Director Server, IBM Director Agent, Remote Deployment Manager, or Software Distribution Premium Edition, contact your sales representative. A software subscription
124
contract entitles you to receive future updates that become available during your subscription period at no additional charge. With software subscription services, you will receive proactive notification of new upgrades, patches and support information. Note: For System x servers, you can purchase your software subscription from the IBM Director Subscription services Web Page at: http://www-03.ibm.com/ systems/management/director/subscription/.
Preparing the IBM Director database

Unless you plan to use IBM DB2 for System i or Apache Derby, you must prepare the database application before configuring IBM Director Server to use it. IBM Director can be installed before preparing the database, but you will not be able to use database-dependent features until you configure IBM Director Server to use a database. The preparation required depends on the database application; it might include one or more of the following tasks: v Downloading and installing the applicable Java Database Connectivity (JDBC) drivers v Creating a database or server ID v Configuring and starting a TCP/IP listener v Setting the authentication mode The database administrator should determine an appropriate size for the database file. If IBM Director will be managing 300 - 500 systems, an initial size of 100 MB is sufficient. A larger database might be necessary if there will be additional managed systems or extensive inventory data.
Preparing the IBM DB2 database

Before installing IBM Director Server, prepare the IBM DB2 database for use with IBM Director. The IBM DB2 database can be installed locally on the management server, or (except when IBM Director Server is installed on i5/OS), the IBM DB2 database can optionally be installed on a remote server. Complete the following tasks before installing IBM Director Server: 1. Install IBM DB2 database, if you have not done so already. See the Supported database applications topic for supported versions and installation options. Notes: v The DB2 client installation is not required for IBM Director version 5.20. v If needed, download and install the required fix packs from the IBM DB2 database for Linux, UNIX and Windows product support Web Site at www.ibm.com/software/data/db2/udb/support/index.html. v Using the DB2 Run-time or Administration Client media, install the DB2 Java JDBC Type 4 Universal driver on the management server. Ensure that the driver is at the correct fix pack level. v Installation of the DB2 Run-time or Administration Client automatically configures the CLASSPATH environment variable. 2. Create a user on the DB2 server for the IBM Director database.
125
3. Create the DB2 database, if it does not already exist. The DB2 database must be created on the local or remote server before you configure IBM Director to use it. 4. Grant the following runtime permissions for the user you created on the DB2 server: v CREATE TABLE v ALTER TABLE v DROP TABLE v CREATE INDEX v ALTER INDEX v DROP INDEX v CREATE VIEW v ALTER VIEW v DROP VIEW 5. Linux only: If IBM Director Server will be installed on a Linux platform, perform the following steps on the Linux management server on which IBM Director Server will be installed: a. Create a /etc/ibm/director/setup_env file. Add the following statement to the file:
. /home/db2inst1/sqllib/db2profile
home/db2inst1 is the directory in which DB2 is installed. This statement sets up the DB2 environment. b. Set the setup_env file attributes to read-execute. 6. Provide the following information to the system administrator who will install IBM Director Server: v TCP/IP listener port ID v Host name of the database server v Database name v User ID and password Note: The IBM DB2 Information Center has current information about security in DB2. The IBM DB2 Information Center is at publib.boulder.ibm.com/infocenter/ db2help/index.jsp.
Preparing Microsoft Data Engine and Microsoft SQL Server

Before installing IBM Director Server, you must prepare the database for use with IBM Director. Preparing the Microsoft Data Engine 2000 database: Before installing IBM Director Server, prepare the Microsoft Data Engine 2000 (also called SQL Server 2000 Desktop Engine or MSDE 2000) database for use with IBM Director. Complete the following tasks before installing IBM Director Server: 1. Install Microsoft Data Engine (MSDE) 2000. See the Supported database applications topic for supported versions and installation options. Use the following command-line parameters when installing to override the default settings:
DISABLE NETWORKPROTOCOLS=0 SECURITYMODE=SQL
126
Note: The Java Database Connectivity (JDBC) driver provided by Microsoft does not support trusted connections at this time; these settings enable the database to work with the SQL Server 2000 Driver for JDBC required by IBM Director. You will install a new driver later in this procedure. 2. If MSDE 2000 is already installed: Ensure that network connections are enabled and that the authentication mode is set to mixed mode. By default, MSDE is installed with network connections disabled and security set to Windows authentication. For information about changing these parameters for an existing installation, see the following Microsoft Knowledge Base articles: v 285097 How to Change the Default Login Authentication Mode to SQL v 319930 How to Connect to Microsoft Desktop Engine 3. Install the SQL Server JDBC driver on the management server where IBM Director Server will be installed. This driver will be used for both SQL Server 2000 and SQL Server 2005. a. Download the SQL Server 2005 V1.0.809.102 JDBC driver from www.microsoft.com/sql/downloads/2005/default.mspx. b. Install the downloaded SQL Server JDBC driver according to the instructions provided by Microsoft. 4. Set the system variable CLASSPATH to point to the location of the JDBC driver files. Note: In this step, the variable jdbc_path is used to represent the SQL Server JDBC driver installation path. The default SQL Server JDBC driver installation paths are as follows: SQL Server 2000 Driver for JDBC on Windows: C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\ SQL Server 2005 Driver for JDBC on Windows: C:\Program Files\Microsoft SQL Server 2005 JDBC Driver\sqljdbc_1.0\enu\ In any CLASSPATH declaration, replace jdbc_path with the correct path to the JDBC driver on your system: a. Click Start Control Panel System. b. Click the Advanced tab, and then click Environment Variables. c. In the System variables list, select the CLASSPATH variable, and then click Edit. Notes: v CLASSPATH must be defined as a system variable. Defining CLASSPATH as a user variable will not work. v If CLASSPATH is not already listed under System variables, click New and type CLASSPATH in the Variable name field. d. Add the following to the end of the Variable value field:
;jdbc_path\sqljdbc.jar
e. In the Edit User Variable window, click OK, and then click OK in the Environment Variables and System Properties windows. If this installation is for an update to IBM Director, remove any existing pointers to the following jar files used by previous versions of the JDBC driver: jdbc_path/msbase.jar jdbc_path/msutil.jar jdbc_path/mssqlserver.jar 5. Create an SQL Server ID for use with IBM Director.
127
6. Provide the following information to the system administrator who will install IBM Director Server: v TCP/IP listener port ID v Host name of the database server v Database name v User ID and password Preparing the Microsoft SQL Server 2005 Express Edition database: Before installing IBM Director Server, prepare the Microsoft SQL Server 2005 Express Edition database for use with IBM Director. Complete the following tasks before installing IBM Director Server: 1. Install Microsoft SQL Server 2005 Express Edition. See the Supported database applications topic for supported versions and installation options. a. Download Microsoft SQL Server 2005 Express Edition from www.microsoft.com/sql/downloads/2005/default.mspx. b. Install Microsoft SQL Server 2005 Express Edition according to the instructions provided by Microsoft. When prompted for the authentication type, select Mixed mode and specify a password. Notes: v The SQL Server security must be set to Mixed Mode as the JDBC Driver requires SQL Server Authentication for the login. v Trusted connections are not supportedat this time. 2. If Microsoft SQL Server 2005 Express Edition is already installed: Ensure that the authentication mode is set to mixed mode. For information about changing these parameters for an existing installation, see the following SQL Server 2005 Express Edition Books Online article: msdn2.microsoft.com/en-us/library/ ms143705.aspx. 3. Configure TCP/IP connectivity for use with IBM Director Server. By default, SQL Server Express Edition does not have TCP/IP connectivity enabled after installation. In addition, the TCP port must be set for use with IBM Director Server. Complete the following steps: a. Click Start All Programs Microsoft SQL Server 2005 Configuration Tools SQL Server Configuration Manager. b. In the left pane of the SQL Server Configuration Manager window, expand SQL Server 2005 Network Configuration and then click Protocols for SQLEXPRESS. c. In the right pane of the SQL Server Configuration Manager window, right-click TCP/IP and click Enable. Click OK to acknowledge the warning message. d. Right-click TCP/IP again and click Properties. e. In the TCP/IP Properties window, click the IP Addresses tab, and then expand IPALL. f. Under IPALL, clear the TCP Dynamic Ports field and then type a port number in the TCP Port field. Usually, the port number should be set to the default value of 1433. g. In the TCP/IP Properties window, click OK, and then click OK to acknowledge the warning message. h. In the left pane of the SQL Server Configuration Manager window, click SQL Server 2005 Services.
128
i. In the right pane of the SQL Server Configuration Manager window, right-click SQL Server (SQLEXPRESS) and click Restart. Note: If you have multiple instances of SQL Server installed on the management server, configure the instance you will be using with IBM Director Server, and substitute the correct instance name for SQLEXPRESS in the preceding steps. 4. Install the SQL Server JDBC driver on the management server where IBM Director Server will be installed. This driver will be used for both SQL Server 2000 and SQL Server 2005. a. Download the SQL Server 2005 V1.0.809.102 JDBC driver from www.microsoft.com/sql/downloads/2005/default.mspx. b. Install the downloaded SQL Server JDBC driver according to the instructions provided by Microsoft. 5. Set the system variable CLASSPATH to point to the location of the JDBC driver files. Note: In this step, the variable jdbc_path is used to represent the SQL Server JDBC driver installation path. The default SQL Server JDBC driver installation paths are as follows: SQL Server 2000 Driver for JDBC on Windows: C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\ SQL Server 2005 Driver for JDBC on Windows: C:\Program Files\Microsoft SQL Server 2005 JDBC Driver\sqljdbc_1.0\enu\ In any CLASSPATH declaration, replace jdbc_path with the correct path to the JDBC driver on your system: a. Click Start Control Panel System. b. Click the Advanced tab, and then click Environment Variables. c. In the System variables list, select the CLASSPATH variable, and then click Edit. Notes: v CLASSPATH must be defined as a system variable. Defining CLASSPATH as a user variable will not work. v If CLASSPATH is not already listed under System variables, click New and type CLASSPATH in the Variable name field. d. Add the following to the end of the Variable value field:
;jdbc_path\sqljdbc.jar
e. In the Edit User Variable window, click OK, and then click OK in the Environment Variables and System Properties windows. If this installation is for an update to IBM Director, remove any existing pointers to the following jar files used by previous versions of the JDBC driver: jdbc_path/msbase.jar jdbc_path/msutil.jar jdbc_path/mssqlserver.jar 6. Create an SQL Server ID for use with IBM Director. 7. Provide the following information to the system administrator who will install IBM Director Server: v TCP/IP listener port ID v Host name of the database server
129
v Database name v User ID and password Preparing the Microsoft SQL Server database: Before installing IBM Director Server, prepare the Microsoft SQL Server 2000 or Microsoft SQL Server 2005 database for use with IBM Director. The Microsoft SQL Server database can be used with IBM Director Server only on management servers running Windows or Linux. Complete the following tasks before installing IBM Director Server: 1. Install Microsoft SQL Server, enabling network connections and setting the security to mixed mode. See the Supported database applications topic for supported versions and installation options. Notes: v The SQL Server security must be set to Mixed Mode as the JDBC Driver requires SQL Server Authentication for the login. v Trusted connections are not supported at this time. 2. Install the SQL Server JDBC driver on the management server where IBM Director Server will be installed. This driver will be used for both SQL Server 2000 and SQL Server 2005. a. Download the SQL Server 2005 V1.0.809.102 JDBC driver from www.microsoft.com/sql/downloads/2005/default.mspx. b. Install the downloaded SQL Server JDBC driver according to the instructions provided by Microsoft. 3. Set the system variable CLASSPATH to point to the location of the JDBC driver files. Note: In this step, the variable jdbc_path is used to represent the SQL Server JDBC driver installation path. The default SQL Server JDBC driver installation paths are as follows: SQL Server 2000 Driver for JDBC on Linux: /opt/msSQLjdbc/lib/ SQL Server 2005 Driver for JDBC on Linux: /home/usr1/ mssqlserver2005jdbc/Driver/sqljdbc_1.0/enu/ SQL Server 2000 Driver for JDBC on Windows: C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\ SQL Server 2005 Driver for JDBC on Windows: C:\Program Files\Microsoft SQL Server 2005 JDBC Driver\sqljdbc_1.0\enu\ In any CLASSPATH declaration, replace jdbc_path with the correct path to the JDBC driver on your system.
Operating system Linux Instructions Modify or add a CLASSPATH declaration in the /etc/ibm/director/setup_env file to point to the location of the JDBC driver files. Add the following statement to the /etc/ibm/director/setup_env file: CLASSPATH =.;jdbc_path/sqljdbc.jar Note: You might have to create the /etc/ibm/director/setup_env file. Set the attributes of this file to read-execute.
130
Operating system Windows
Instructions 1. Click Start Control Panel System. 2. Click the Advanced tab, and then click Environment Variables. 3. In the System variables list, select the CLASSPATH variable, and then click Edit. Notes: v CLASSPATH must be defined as a system variable. Defining CLASSPATH as a user variable will not work. v If CLASSPATH is not already listed under System variables, click New and type CLASSPATH in the Variable name field. 4. Add the following to the end of the Variable value field: ;jdbc_path\sqljdbc.jar 5. In the Edit User Variable window, click OK, and then click OK in the Environment Variables and System Properties windows.
If this installation is for an update to IBM Director, remove any existing pointers to the following jar files used by previous versions of the JDBC driver: jdbc_path/msbase.jar jdbc_path/msutil.jar jdbc_path/mssqlserver.jar 4. Create an SQL Server ID for use with IBM Director. 5. Complete one of the following tasks.
Option To create the database during the installation of IBM Director To create the database now Description Assign the SQL Server ID Create Database permission in the master database. When the database is created during the IBM Director installation, the size of the database is set to the default database size specified in the SQL Server configuration options. Create the SQL Server database and give the following runtime permissions to the SQL Server ID that you created: v CREATE TABLE v ALTER TABLE v DROP TABLE v CREATE INDEX v ALTER INDEX v DROP INDEX v CREATE VIEW v ALTER VIEW v DROP VIEW
6. Provide the following information to the system administrator who will install IBM Director Server: v TCP/IP listener port ID v Host name of the database server v Database name v User ID and password
Preparing the Oracle Server database

Before installing IBM Director Server, prepare the Oracle Server database for use with IBM Director. Complete the following tasks before installing IBM Director Server:
131
1. Install the Oracle Server database. See the Supported database applications topic for supported versions and installation options. 2. On the management server where IBM Director Server will be installed, download the correct version of the Oracle Java Database Connectivity (JDBC) thin driver for use with Java Development Kit (JDK) 1.4. IBM Director is certified to run with the Oracle Java Database Connectivity (JDBC) thin driver for use with Java Development Kit (JDK) 1.4 only. One of the following Oracle Java Database Connectivity (JDBC) thin drivers must be present.
Oracle Server version Oracle Database V9.2 Oracle Database 10g Release 1 Oracle Database 10g Release 2 JDBC driver version Oracle JDBC driver V9.2.0.8 Oracle JDBC driver V10.1.0.5 Oracle JDBC driver V10.2.0.2
Note: Only the JDBC driver versions listed above are known to work correctly with IBM Director Server. Use the correct JDBC driver version for the Oracle Server version you have installed. Navigate to www.otn.oracle.com/software/content.html and download the ojdbc14.jar file. 3. Set the system variable CLASSPATH on the management server to point to the location of the JDBC driver (ojdbc14.jar file).
Operating system AIX or Linux Instructions Modify or add a CLASSPATH declaration in the /etc/ibm/director/setup_env file to point to the location of ojdbc14.jar. Add the following statements (substituting the actual path for ojdbc_path): export CLASSPATH=$CLASSPATH:/ojdbc_path/ojdbc14.jar Note: You might have to create the /etc/ibm/director/setup_env file. Set the attributes of this file to read-execute. Windows 1. Click Start Control Panel System. 2. Click the Advanced tab, and then click Environment Variables. 3. Select the CLASSPATH variable, and then click Edit. 4. Add the following to the end of the Variable value field (substituting the actual path for ojdbc_path): ;ojdbc_path/ojdbc14.jar 5. In the Edit User Variable window, click OK, and then click OK in the Environment Variables and System Properties windows.
4. Create the Oracle Server database. 5. Configure and start the Oracle TCP/IP listener. 6. Provide the following information to the system administrator who will install IBM Director Server: v Oracle administrator account ID and password v Oracle system identifier (SID) v Oracle TCP/IP listener port ID v TCP/IP host name of the database server Note: The Oracle administrator account ID and password are used to perform the following tasks only:
132
v Create table spaces and a role (TWG_ROLE) v Assign a user ID and password IBM Director does not save the Oracle administrator account ID and password.
Preparing the PostgreSQL database

This topic describes how to prepare a PostgreSQL database for use with IBM Director. Complete the following tasks before installing IBM Director Server: 1. Install PostgreSQL, if it is not already installed. Use the PostgreSQL installation that was included as part of the Linux operating system on the management server. IBM Director is only tested for the versions of PostgreSQL that are distributed with supported Linux operating systems. 2. Configure PostgreSQL to use TCP/IP connections, and specify the TCP/IP port. Although both of these options can be specified on the command line when the PostgreSQL postmaster is started, modify the data/postgresql.conf file in the directory in which PostgreSQL is installed in order to specify configuration settings that will be applied every time the postmaster is started. Edit the data/postgresql.conf file and add or modify the following configuration parameters.
PostgreSQL versions PostgreSQL V7.3 and V7.4 PostgreSQL V8.1 Configuration parameters port=5432 tcpip_socket=true port=5432 listen_addresses=ipaddresses where ipaddresses is either a comma-delimited list of one or more IP addresses or host names (including localhost) for the TCP/IP listener to use, or an asterisk character (*), which indicates that the listener should use all available IP interfaces.
Setting these parameters enables the TCP/IP listener. The default value for port is 5432; change this value if necessary. More information about these configuration settings can be found in the PostgreSQL online documentation. 3. In order for IBM Director Server to use the PostgreSQL database, you must enable a password-based client authentication method such as MD5. See the PostgreSQL documentation for information about the available password-based client authentication methods and how to make this configuration. 4. Stop and restart PostgreSQL. For the configuration changes to take effect, you must stop and restart the database. 5. Install the PostgreSQL Java Database Connectivity (JDBC) driver on the management server where IBM Director Server will be installed. Use the version of the PostgreSQL JDBC driver that was included as part of the Linux operating system on the management server. IBM Director is only tested for the versions of the PostgreSQL JDBC driver that are distributed with supported Linux operating systems. Note: The PostgreSQL JDBC driver must be compatible with JDK 1.4. 6. Set the system variable CLASSPATH to point to the location of the JDBC driver. Perform the following steps on the management server:
133
a. If the PostgreSQL JDBC driver is not named postgresql.jar, create a symbolic link for the driver. From a command prompt, type the following command and press Enter:
ln -s driver_path sl_path/postgresql.jar
v driver_path is the fully qualified name of the PostgreSQL JDBC driver. v sl_path is the path of the symbolic link. For example:
ln -s /opt/postgres/lib/pg73jdbc3.jar /opt/postgres/lib/postgresql.jar
b. Create a /etc/ibm/director/setup_env file. Add the following statement to the file:

export CLASSPATH=path/postgreslq.jar
v path is the path of the PostgreSQL JDBC driver, or of the symbolic link, if one exists. For example:
export CLASSPATH=/opt/postgres/lib/postgreslq.jar
c. Set the setup_env file attributes to read-execute. 7. Create a PostgreSQL server ID for use with IBM Director. 8. Complete one of the following tasks.
Option To create the database during the installation of IBM Director To create the database now Description Assign the PostgreSQL server ID that you created in step 7 Create Database permission.
Create the PostgreSQL database and give the following runtime permissions to the PostgreSQL server ID that you created in step 7: v CREATE TABLE v ALTER TABLE v DROP TABLE v CREATE INDEX v ALTER INDEX v DROP INDEX v CREATE VIEW v ALTER VIEW v DROP VIEW
9. Provide the system administrator who will install IBM Director Server with the following information: v Database name (if the PostgreSQL database was created in step 8) v Host name of the database server v PostgreSQL IP listener port v User ID and password, if necessary Related information PostgreSQL online documentation at www.postgresql.org/docs/
Preparing firewalls and proxies for IBM Director

If you have firewalls in your network, or if the management server must use a proxy server to access the internet, you must configure the firewalls and proxy server to enable installation and operation of IBM Director.
134
IBM Director must be able to access all the managed objects in the network, and if you will be using a remote management console, the management console and management server must have access to each other. In addition, some functions of IBM Director require access to the internet. To enable this access, you must configure firewalls and proxies in your network to allow access by IBM Director components. 1. Configure the firewall on the management server to allow the following ports to be used by the IBM Director software components: v 22 v 427 v 5988 v 5989 v 6988 v 15988 v 15989 These ports are the minimum required to install IBM Director. See Ports used by IBM Director for a complete list of the ports which IBM Director components must be able to use. 2. If a proxy server is required to access the internet from the management server: Configure the management server to use the proxy when accessing the internet. a. Configure the proxy server to use Basic authentication, if it is configured for Digest or NTLM authentication. The Update Manager task supports only Basic authentication with the proxy server. If Digest or NTLM authentication are required, Update Manager will be unable to access update packages from IBM. b. Configure the management server to use the proxy server, if a proxy is required to access the internet. IBM Director requires internet access for some functions, including Update Manager.
Preparing to manage service processors with IBM Director

You can use IBM Director to manage supported service processors that are installed in a managed system. IBM Director can manage service processors that are installed in Level-0 managed systems, Level-1 managed systems, and Level-2 managed systems. v For Level-0 (agentless) managed systems, you do not need to install drivers to perform Level-0 management of the service processors. v For Level-1 or Level-2 managed systems, management of the service processor uses the Common Information Model (CIM) standard, and requires not only installation of either IBM Director Core Services or IBM Director Agent on the managed system, but also installation of a device driver, and possibly a shared library to access the device driver. To install the required drivers on a Level-1 or Level-2 managed system to enable management of the service processor, complete the following steps: 1. Refer to the documentation for your managed server to identify what type of service processor is installed. 2. Identify your server type in Table 50 on page 136.
135
Table 50. Servers with service processors that are supported for Level-1 or Level-2 management by IBM Director Server type BladeCenter blade servers with an IPMI baseboard management controller (BMC) See the BladeCenter, System x, and xSeries servers with an IPMI baseboard management controller (BMC) column in Table 51 on page 138. BladeCenter blade servers with an Integrated systems management processor (ISMP) See the BladeCenter and xSeries servers with an integrated systems management processor (ISMP) column in Table 51 on page 138. eServer servers See the eServer servers column in Table 51 on page 138. System x and xSeries servers with an IPMI baseboard management controller (BMC) See the BladeCenter, System x, and xSeries servers with an IPMI baseboard management controller (BMC) column in Table 51 on page 138. Note: Some systems support installation of an optional Remote Supervisor Adapter or Remote Supervisor Adapter II service processor. If this optional service processor is installed, it supersedes the standard service processor for that system, and all management occurs through the Remote Supervisor Adapter or Remote Supervisor Adapter II. v v v v v v v v v v v v v v v IBM IBM IBM IBM eServer eServer eServer eServer 325, machine type 8835 326, machine type 8848 326m, machine type 7969 326m, machine type 7992 v v v v v v v v xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries 206m 236 260 306m 336 346 347 366 Supported models v v v v v v v BladeCenter BladeCenter BladeCenter BladeCenter BladeCenter BladeCenter BladeCenter HS20, machine types 1883, 1884, 7981, 8843 HS21 HS40 JS21 LS20 LS21 LS41
BladeCenter HS20, machine types 8678, 8832, 8833
System System System System System System System System System System System
x3200 x3250 x3400 x3455 x3500 x3550 x3650 x3650 T x3755 x3800 x3850
136
Table 50. Servers with service processors that are supported for Level-1 or Level-2 management by IBM Director (continued) Server type Supported models v v v v v v v v v v v v v v v v v v v v v v xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries xSeries 206 206m 225 226 232 236 255 260 305 306 306m 335 336 342 345 346 347 360 366 445 460 MXE 460
System x and xSeries servers with a v System x3105 Remote Supervisor Adapter II or v System x3200 Remote Supervisor Adapter II v System x3250 SlimLine v System x3400 v System x3455 See the System x and xSeries v System x3500 servers with a Remote Supervisor v System x3550 Adapter II or Remote Supervisor v System x3650 Adapter II SlimLine column in v System x3650 T Table 51 on page 138. v System x3755 Note: On some of these systems, v System x3800 installation of the Remote Supervisor v System x3850 Adapter or Remote Supervisor v System x3950 Adapter II service processor is optional. If this optional service processor is not installed, all management occurs through either an IPMI baseboard management controller (BMC) or an integrated systems management processor (ISMP). xSeries servers with an integrated systems management processor (ISMP) See the BladeCenter and xSeries servers with an integrated systems management processor (ISMP) column in Table 51 on page 138. v v v v v v v xSeries xSeries xSeries xSeries xSeries xSeries xSeries 232 235 255 335 342 343 345
3. Identify the required drivers for in-band (Level-1 or Level-2) management of the service processors for your server type and operating system in Table 51 on page 138.
137
Table 51. Required drivers for in-band management of service processors BladeCenter, System x, and xSeries servers with an IPMI baseboard Operating system of managed management server controller (BMC) Red Hat Linux OpenIPMI driver v Red Hat Enterprise Linux, version 3.0 (update 6) v Red Hat Enterprise Linux, version 4.0 (update 3) v Red Hat Enterprise Linux, version 5 Other Red Hat Linux distributions OSA IPMI driver IBM Mapping Layer MSI IPMI driver IBM Mapping Layer LM78 driver SUSE Linux OpenIPMI driver v SUSE Linux Enterprise Server 9 for x86 v SUSE Linux Enterprise Server 10 for x86 Other SUSE Linux distributions OSA IPMI driver IBM Mapping Layer MSI IPMI driver IBM Mapping Layer LM78 driver virtual systems using Xen OpenIPMI driver OpenIPMI driver LM78 driver RSA daemon USB drivers LM78 driver VMware VMware ESX Server, version 2.5.4, Console or VMware ESX Server, version 3.0, Console Other VMware distributions OpenIPMI driver OpenIPMI driver LM78 driver USB drivers LM78 driver SMBus driver SMBus driver OpenIPMI driver LM78 driver RSA daemon USB drivers LM78 driver SMBus driver RSA daemon USB drivers LM78 driver SMBus driver System x and xSeries servers with a Remote Supervisor Adapter II or Remote Supervisor Adapter II SlimLine RSA daemon USB drivers LM78 driver
eServer servers OpenIPMI driver LM78 driver
BladeCenter and xSeries servers with an integrated systems management processor (ISMP) SMBus driver
RSA daemon USB drivers LM78 driver
SMBus driver
OSA IPMI driver IBM Mapping Layer
MSI IPMI driver IBM Mapping Layer LM78 driver
Not supported
SMBus driver
138
Table 51. Required drivers for in-band management of service processors (continued) BladeCenter, System x, and xSeries servers with an IPMI baseboard Operating system of managed management server controller (BMC) Windows OSA IPMI driver IBM Mapping Layer System x and xSeries servers with a Remote Supervisor Adapter II or Remote Supervisor Adapter II SlimLine RSA library USB drivers
eServer servers MSI IPMI driver IBM Mapping Layer
BladeCenter and xSeries servers with an integrated systems management processor (ISMP) The necessary drivers are installed with IBM Director Agent or IBM Director Core Services.
4. Install the required drivers. Note: If required, the MSI IPMI driver and the OSA IPMI driver must be installed before the IBM Mapping Layer. IBM Mapping Layer The IBM Mapping Layer is used to translate IBM Director generic requests into driver-specific requests for different IPMI drivers. Download this driver from the IBM Support Web Site at www.ibm.com/support/us. LM78 driver The LM78 device driver ensures that IBM Director Server receives memory and processor Predictive Failure Analysis (PFA) alerts. See Installing IBM LM78 and SMBus device drivers for Linux for installation instructions. MSI IPMI driver The MSI IPMI device driver is used to communicate with the IPMI baseboard management controller. All other systems should use the OSA IPMI driver. Download this driver from the IBM Support Web Site at www.ibm.com/support/us. OpenIPMI driver This driver is included with the operating system. No separate installation is required. OSA IPMI driver The OSA IPMI device driver is used to communicate with the IPMI baseboard management controller. Download this driver from the IBM Support Web Site at www.ibm.com/support/us. RSA daemon The RSA daemon is a Linux-only program that is used to interface with the RSA card. Download this driver from the IBM Support Web Site at www.ibm.com/support/us. RSA library The RSA library device driver is a Windows-only driver that is used to interface with the RSA card. It also prevents driver communication from interfering with IBM Director. Download this driver from the IBM Support Web Site at www.ibm.com/support/us.
139
SMBus driver The SMBus device driver ensures that the Management Processor Assistant tasks and System Health Monitoring function correctly, and is used to communicate with the integrated systems management processor (ISMP) on some servers. See Installing IBM LM78 and SMBus device drivers for Linux for installation instructions. USB drivers The RSA daemon and RSA library use this driver to communicate with the RSA II card. This driver is included with the operating system. No separate installation is required. 5. Make sure that you have the latest firmware installed for your service processors. Related reference Installing IBM LM78 and SMBus device drivers for Linux on page 144 If you plan to install IBM Director Server on a System x or xSeries server running Linux, you might need to install either or both the LM78 and SMBus device drivers for Linux. These device drivers ensure that certain IBM Director tasks and functions work correctly.
Preparing the management server

Before installing IBM Director Server make sure that the requirements that are applicable to your system have been met.
Preparing to install IBM Director Server on AIX

Before installing IBM Director Server on AIX, make sure that your platform meets the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation: AIX only: Before installing IBM Director Server or IBM Director Agent on AIX, complete the following preparatory steps: 1. Verify that required APAR fixes are installed on your system. 5.20.1 only: When installing the sysmgt.pegasus.cimserver fileset at the recommended level, the installation of these prerequisites are enforced, but you will need to download the APAR installation images as described below if they are not already installed. v IY78923 is required for all supported versions of AIX v IY76140 is required for AIX 5.3 running a 64-bit kernel v IY76141 is required for AIX 5.2 running a 64-bit kernel v IY86709 is required for AIX 5.2 at TL09. The Technology Level can be verified with the oslevel -r command. Complete the following steps to verify that you have the required fixes installed. a. Type one of the following commands and press Enter: AIX 5.3: instfix -i -k " IY76140 IY78923" AIX 5.2: instfix -i -k "IY76141 IY78923 IY86709" (IY86709 is only necessary if the system is at AIX 5.2 TL09) If the required APARs are installed, continue to step 2 on page 141. b. Check to see if filesets incorporating these APAR fixes are installed.
140
v IY78923 is included in the following filesets: xlC.aix50.rte (version 8.0.0.2 or higher), xlC.rte (version 8.0.0.0 or higher), xlsmp.aix50.rte (version 1.6.0.0 or higher) and xlsmp.rte (version 1.6.0.0 or higher). v IY76140 is included in the following filesets: bos.mp and bos.mp64 at version 5.3.0.32 or higher. v IY76141 is included in the following filesets: bos.mp and bos.mp64 at version 5.2.0.89 or higher. v IY86709 is included in the following fileset: bos.rte.shell 5.2.0.95 or higher If the required APARs are included in your installed filesets, continue to step 3. c. Download and install the required APARs from the following address: http://www.ibm.com/eserver/support/fixes/fixcentral. 1) Select UNIX servers. 2) Select AIX operating system. 3) Select 5.2 or 5.3. 4) Select Specific fixes. 5) Click Continue, and then follow the instructions on the succeeding pages to select and download the APARs you need. 2. Ensure that the following AIX Pegasus CIM Server and providers are installed and functional:
Table 52. AIX Pegasus CIM Server and providers Version 5.20 Installation requirements v openssl-0.9.7g-1.aix5.1.ppc.rpm or higher (must be installed before installing the pegasus filesets) v sysmgt.pegasus.cimserver 2.5.1.0 or higher v sysmgt.pegasus.osbaseproviders 1.2.6.0 or higher v sysmgt.pegasus.smisproviders 1.1.0.0 or higher v openssl-0.9.7g-1.aix5.1.ppc.rpm or higher (must be installed before installing the pegasus filesets) v sysmgt.pegasus.cimserver 2.5.1.21 or higher v sysmgt.pegasus.osbaseproviders 1.2.6.21 or higher v sysmgt.pegasus.smisproviders 1.1.0.21 or higher
5.20.1
For more information about installation and requirements for OpenSSL and Pegasus, see the System p and AIX information center at publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cim/doc/ cim/ciminstall.htm#ciminstall. This information center contains instructions on how to use the lslpp -l command to verify that the installed Pegasus filesets are at the required version. It also tells how to verify what version of OpenSSL is installed. The OpenSSL provider can be obtained from the following Web site: www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=aixtbx &S_PKG=dlaixww. 3. Recommended, not required: Back up the CIM repository. Type the following two commands, substituting a date string for date and pressing Enter after each command:
/opt/freeware/cimom/pegasus/bin/cimserver -s cp -pRh /opt/freeware/cimom/pegasus/etc/repository /opt/freeware/cimom/pegasus/etc/repository.backup.date
Additional configuration and troubleshooting information about the AIX Pegasus CIM Server is available in the following two documents: v The Common Information Model Guide for AIX, which is available at publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cim/doc/ cim/cim.pdf
141
v The README file that is installed with the sysmgt.pegasus.cimserver fileset in /opt/freeware/cimom/pegasus/ Refer to these documents if you encounter problems running the AIX Pegasus CIM Server. Both the Guide and README contain instructions on repository recovery if needed.
Preparing to install IBM Director on i5/OS

Before installing IBM Director on a system running i5/OS, there are several items to consider, such as the type of media on which the installation files are saved, the user profile that is used to install IBM Director, and the additional software that might be required. Review the following information and complete the necessary steps to prepare your system for installation: v Installation of IBM Director Server on i5/OS does not include the IBM Director Console; however, you can use the command line interface (dircli) to access the management server. To provide a GUI to access IBM Director Server that is running on i5/OS, you must install IBM Director Console on an operating system that supports IBM Director Console. The IBM Director Console installation images are available on the IBM Director for i5/OS media, or from the IBM Director support Web site at www.ibm.com/systems/management/director/. v If you want to use IBM Director Server on a System i platform to manage a heterogeneous environment, you must install the applicable IBM Director Agent or IBM Director Core Services package on each IBM platform that you want to manage. You can obtain these versions of IBM Director Agent and IBM Director Core Services from the IBM Director support Web site at www.ibm.com/systems/ management/director/ or from the IBM Director Agents & Consoles (1 of 2) CD. Note: IBM Director Core Services is not supported on i5/OS. v Your user profile should have *ALLOBJ and *SECADM special authorities. v Ensure that the following products and options are installed on the System i (i5/OS V5R3 or later) server on which you plan to install IBM Director, along with the latest cumulative PTF packages or Group PTFs. These products and options are required to successfully install and securely run IBM Director.
Products or options (V5R3 only) IBM Cryptographic Access Provider 128-bit for System i IBM HTTP Server for System i OS/400 - Extended Base Directory Support, Option 1 OS/400 - Extended Base Directory Support, Option 3
Order number 5722-AC3 5722-DG1 5722-SS1 5722-SS1
TCP/IP Connectivity Utilities for iSeries 5722-TC1 Note: TCP must be configured correctly or IBM Director might not start. See IBM Director Fails to Start for a short description of common configuration problems. Java Developer Kit 1.4, Option 6 OS/400 - Qshell, Option 30 OS/400 - Digital Certificate Manager, Option 34 5722-JV1 5722-SS1 5722-SS1
142
v Do not install IBM Director Server over IBM Director Agent. Complete the following steps to check if IBM Director Agent is installed: 1. From a command prompt, type GO LICPGM and press Enter. 2. Select option 10, Display installed licensed programs, and review the list of installed programs. If installed, IBM Director Agent is displayed in the list as one of the following entries (depending on the version):
5722DA1 *BASE IBM DIRECTOR 5733VE1 39 5050 IBM Director Multiplatform Agent, 4.2.0
If IBM Director Agent is installed, you must uninstall it before installing IBM Director Server. You can use option 12 from the LICPGM menu to uninstall the product or option. v If you plan to use Software Distribution to distribute IBM Director Agent to Level-0 managed systems that are running i5/OS, ensure you have installed and configured Open SSH, provided in i5/OS Utilities, *BASE and Option 1 (order number 5733-SC1) on the managed systems. For more information about Open SSH, go to www.openssh.org. v If you plan to use IBM Director to monitor SNMP devices in your System i environment, ensure you have completed the necessary configuration tasks for System i and SNMP devices. See the Networking topic in the System i Information Center for more information. v If you want to install IBM Director Server on a System i logical partition that is running AIX or Linux on POWER, see Preparing to install IBM Director Server on Linux on POWER.
Preparing to install IBM Director Server on Linux for System x

Before installing IBM Director on a management server running Linux for System x, make sure that your server meets all the applicable requirements. Note: Because installing IBM Director Server on Linux for System x also installs IBM Director Agent and IBM Director Console, the preparation steps for IBM Director Server also include preparation steps for IBM Director Agent and IBM Director Console. Review the following information and complete the necessary steps to prepare your system for installation: v Make sure that the system meets the hardware and software requirements for installation described in Specified operating environments. v Ensure that the X Window System package group is installed. IBM Director Console requires RPMs that are installed with the X Window System package group. v Ensure that the required RPMs are installed:
Table 53. Required RPMs Installation scenario Red Hat Enterprise Linux AS and ES, version 3.0 Red Hat Enterprise Linux AS and ES, version 4.0 Required RPM compat-libstdc++-7.3-2.96.122.i386.rpm compat-libstdc++-296-2.96-132.7.2.i386.rpm compat-libstdc++-33-3.2.3-47.3.i386.rpm 64-bit Intel Itanium system running compat-libstdc++-33-3.2.3-47.3.ia64.rpm Red Hat Enterprise Linux AS, version 4.0, for Intel Itanium
143
Table 53. Required RPMs (continued) Installation scenario Required RPM
Upgrading from IBM Director, rpm-4.1.1-177.9.i586.rpm version 4.20 or later on SUSE Linux Enterprise Server 9 for x86
v Systems with service processors: Install the supporting device drivers and mapping layers, if they are not already installed. See Preparing to manage service processors with IBM Director for information about these drivers and mapping layers. v Make sure that the instance of IBM Director Agent will be fully functional and able to send alerts to IBM Director Server. For the IBM Director Agent to be fully functional you might need to install service-processor device drivers or the IBM LM78 and SMBus device drivers for Linux. v If you want to use the Remote Session task on the managed system, make sure that the package that contains telnetd daemon is installed and configured. This package is usually in the telnet_server_version.i386.RPM package, where version is the code level of your Linux distribution. v If you want to use IBM Director Server on System x for heterogeneous server management, you can install IBM Director Agent or IBM Director Core Services on the platforms you want to manage. You can obtain IBM Director Agent andIBM Director Core Services for the supported operating systems from the IBM Director Web site at www.ibm.com/systems/management/director/ or, if it was included with your IBM Director distribution, from the IBM Director Agents & Consoles (1 of 2) CD. v The IBM Director on x86, V5.20 CD does not include SUSE Linux Enterprise Server 10 installation packages for IBM Director Server, IBM Director Console, IBM Director Agent, or IBM Director Core Services. You can download these installation packages for System x platforms from theIBM Director Web site at: www.ibm.com/systems/management/director/. Related tasks Preparing to manage service processors with IBM Director on page 135 You can use IBM Director to manage supported service processors that are installed in a managed system. Installing IBM LM78 and SMBus device drivers for Linux: If you plan to install IBM Director Server on a System x or xSeries server running Linux, you might need to install either or both the LM78 and SMBus device drivers for Linux. These device drivers ensure that certain IBM Director tasks and functions work correctly. The following table contains information about these device drivers, when they need to be installed, and what they do.
144
Table 54. Installing IBM Director Server: IBM LM78 and SMBus device drivers for Linux Device driver LM78 When it is needed v The server is one of the following servers: IBM eServer 325, machine type 8835 IBM eServer 326, machine type 8848 IBM eServer 326m, machine type 7969 IBM eServer 326m, machine type 7992 v The server contains one of the following service processors: Remote Supervisor Adapter Remote Supervisor Adapter II SMBus If the server does not contain one of the following service processors: v IPMI baseboard management controller (BMC) v Remote Supervisor Adapter v Remote Supervisor Adapter II The SMBus device driver ensures that the Management Processor Assistant tasks and System Health Monitoring function correctly, and is used to communicate with the integrated systems management processor (ISMP) on some servers. What it does The LM78 device driver ensures that IBM Director Server receives memory and processor Predictive Failure Analysis (PFA) alerts.
The LM78 and SMBus drivers might also be required in order to provide Level-1 or Level-2 management of service processors as specified in Preparing to manage service processors with IBM Director To install the LM78 and SMBus device drivers, complete the steps in the following topics. Related tasks Preparing to manage service processors with IBM Director on page 135 You can use IBM Director to manage supported service processors that are installed in a managed system. Uninstalling the IBM LM78 or SMBus device driver: Before you install a new IBM LM78 or SMBus device driver, you must uninstall any previous versions of the drivers from the server. Uninstalling the IBM LM78 or SMBus device driver, version 4.21 or later: This topic describes how to uninstall the IBM LM78 or SMBus device driver, version 4.21 or later. Note: For instructions about how to uninstall the IBM LM78 or SMBUS device driver, version 4.20 or earlier, see Uninstalling the IBM LM78 driver, version 4.20 or earlier on page 146 and Uninstalling the IBM SMBus device driver, version 4.20 or earlier on page 146. To uninstall the IBM LM78 or SMBus device driver, version 4.21 or later, open a command prompt, type the following command, and press Enter:
rpm -e driver
145
where driver is one of the following strings.

Device driver IBM LM78 IBM SMBus Command ibmlm78 ibmsmb
Issuing this command unloads the device driver and removes all driver-related files from the server. Uninstalling the IBM LM78 driver, version 4.20 or earlier: Before you install IBM LM78 device driver, version 4.21 or later, you must first uninstall the earlier version of the driver that is already installed. Note: For instructions about how to uninstall the IBM LM78 driver, version 4.21 or later, see Uninstalling the IBM LM78 or SMBus device driver, version 4.21 or later on page 145. To uninstall the IBM LM78 device driver, version 4.20 or earlier, complete the following steps: 1. To uninstall the binary RPM file, from a command prompt, type the following command and press Enter:
rpm -e ibmlm78
2. To uninstall the source RPM file, open a command prompt, type the following command, and press Enter:
rpm -e ibmlm78-src-distribution
where distribution is one of the following strings.

Type of distribution For servers running Red Hat Linux or VMware ESX Server For servers running SUSE Linux String redhat suse
Issuing this command unloads the device driver and removes all driver-related files from the server. Uninstalling the IBM SMBus device driver, version 4.20 or earlier: Before you install IBM SMBus device driver, version 4.21 or later, you must first uninstall the earlier version of the driver that is already installed. Note: For instructions about how to uninstall the SMBus device driver, version 4.21 or later, see Uninstalling the IBM LM78 or SMBus device driver, version 4.21 or later on page 145. To uninstall the IBM SMBus device driver, version 4.20 or earlier, complete the following steps: 1. To uninstall the binary RPM file, from a command prompt, type the following command and press Enter:
rpm -e ibmsmb
2. To uninstall the source RPM file, open a command prompt, type the following command, and press Enter:
146
rpm -e ibmsmb-src-distribution
where distribution is one of the following strings.

Type of distribution For servers running Red Hat Linux or VMware ESX Server For servers running SUSE Linux String redhat suse
Issuing this command unloads the device driver and removes all driver-related files from the server. Building the binary RPM file: If applicable, you can build the binary RPM files for the IBM LM78 or SMBus device drivers. Ensure that the following conditions are met before building the binary RPM file: v The system has Linux development and build capability. v The Linux kernel source is installed and correctly configured. v Any earlier versions of the LM78 or SMBus device drivers are uninstalled. You must build the binary RPM file on a system with the same kernel version and hardware configuration as the system on which you will install IBM Director Server. Make sure that the hardware configuration is similar in regard to the number of processors and that any previous versions of the drivers have been uninstalled. Note: If you are building on Red Hat Enterprise Linux ES, version 4.0 and the /usr/src/linux does not exist, perform the following steps: 1. From a command prompt, change to the /usr/src directory. 2. Type the following command and press Enter:
ln -s ./kernels/version/ ./linux
where version is the appropriate kernel subdirectory under /usr/src/kernels (for example, 2.6.9-5.EL-smp-i686), which matches the kernel the system is currently running. To build either the LM78 or SMBus device driver, complete the following steps: 1. Download the source code for the IBM LM78 and SMBus device drivers from the IBM Director Downloads Web Page: www.ibm.com/systems/management/ director/downloads.html. 2. Copy the source file (dir5.20_lm78_linux.tar.gz for the LM78 driver or dir5.20_smbus_linux.tar.gz for the SMBus driver) to the SOURCES directory. 3. From a command prompt, change to the SOURCES directory. 4. Type one of the following commands and press Enter:
Device driver LM78 SMBus Command rpmbuild -tb dir5.20_lm78_linux.tar.gz rpmbuild -tb dir5.20_smbus_linux.tar.gz
147
Running this command creates a binary RPM file in the RPMS/architecture directory, where architecture is one of the following strings: v i586 (SUSE Linux Enterprise Server 9 for x86 v i386 (all other 32-bit operating systems) v X86_64 (64-bit operating systems) Installing the IBM LM78 or SMBus device driver: After building the binary RPM file for the kernel version of the Linux operating system on your server, you can install the IBM LM78 or SMBus drivers. You can install the binary RPM file either on the server on which it was built or on another server that has the same Linux kernel and hardware configuration. Complete the following steps to install either the IBM LM78 or SMBus device driver: 1. If you built the binary RPM file on another server, complete the following steps: a. Make sure that any earlier versions of the device drivers have been uninstalled from the server where you will install version 5.20 of the device driver and IBM Director. b. Copy the binary RPM file to an RPMS/architecture directory, where architecture is either i386 (for a 32-bit operating system) or X86_64 (for a 64-bit operating system). Note: In this procedure, driver is one of the following strings:
Device driver IBM LM78 IBM SMBus Command ibmlm78 ibmsmb
2. Change to the RPMS/architecture directory. 3. From a command prompt, type the following command and press Enter:
rpm -ivh driver-5.20-1.architecture.rpm
where architecture is one of the following values: v i386 (32-bit operating systems) v X86_64 (64-bit operating systems) Issuing this command performs the following tasks: v Decompresses and untars the archive into the /usr/local/driver directory v Copies the device driver, shared library, and all the configuration files to the appropriate locations v Loads and starts the device driver
Preparing to install IBM Director Server on Linux for System z

Before installing IBM Director Server on Linux for System z, make sure that your platform meets the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation:
148
v Depending on the component you intend to install, you can use a CD or installation code downloaded from the Web as your installation code. System z mainframes, typically, do not have directly attached CD-ROM drives. If you are using a CD, you might have to mount the CD on a different platform. Table 55 lists some methods of making the installation code available.
Table 55. Making the IBM Director installation code available to Linux on System z Method NFS server How to proceed 1. Mount the CD on an NFS server. You might already have set up an NFS server for installing Linux. The steps for mounting the CD depend on the platform on which the NFS server runs. Refer to the installation information for that platform for details. 2. Access the NFS server from your Linux on System z system. ISO image 1. Mount the CD on the platform of your choice. The steps for mounting the CD depend on the platform. Refer to the installation information for that platform for details. 2. Create an ISO image. For example, if you are accessing the CD from Linux, you can issue a command of this form: dd if=/dev/cdrom of=./iso_file_name where /dev/cdrom is the device node for the CD-ROM drive and iso_file_name is the name of the ISO image. 3. Transfer the ISO image to your Linux on System z, for example, with FTP. 4. On the Linux on System z system, mount the ISO image through a loopback device: mount -o loop iso_file_name /mnt where iso_file_name is the name of the ISO image and /mnt the mount point of the file system.
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z: Ensure that the Compatibility Arch Support package group is installed. The Compatibility Arch Support package group includes a number of RPMs that are required by IBM Director. The Compatibility Arch Support package group can be installed in two ways: During installation of Red Hat Enterprise Linux, by selecting the Compatibility Arch Support package group for installation. After installation of Red Hat Enterprise Linux, by using the system-config-packages tool. Install the system-config-packages tool using the system-config-packages-1.2.23-1.noarch.rpm file, and then run the system-config-packages tool to install the Compatibility Arch Support package group. In either case, you must have the Red Hat Enterprise Linux installation media (or an ISO image of the installation media) available to install the Compatibility Arch Support package group. v Ensure that the X Window System package group is installed. IBM Director Console requires RPMs that are installed with the X Window System package group.
149
v Ensure that the following RPMs are installed.

Table 56. Required RPMs Installation scenario Red Hat 31-bit Enterprise Linux AS, version 4.0, for IBM 64-bit System z Required RPMs compat-libstdc++-295-2.95.3-81.s390.rpm compat-libstdc++-33-3.2.3-47.3.s390.rpm xorg-x11-deprecated-libs-6.8.2-1.EL.13.36.s390.rpm compat-libstdc++-295-2.95.3-81.s390.rpm compat-libstdc++-33-3.2.3-47.3.s390.rpm pam-0.77-66.14.s390.rpm xorg-x11-deprecated-libs-6.8.2-1.EL.13.36.s390.rpm libstdc++-3.4.6-3.s390.rpm compat-2004.7.1-1.2.s390.rpm compat-2004.7.1-1.2.s390x.rpm compat-32bit-9-200407011411.s390x.rpm pam-32bit-0.99.3.0-29.4.s390x.rpm pam-modules-32bit-10-2.2.s390x.rpm XFree86-libs-32bit-9-200512021711.s390x.rpm compat-32bit-2006.1.25-11.2.s390x.rpm pam-32bit-0.99.3.0-29.4.s390x.rpm pam-modules-32bit-10-2.2.s390x.rpm xorg-x11-libs-32bit-6.9.0-50.14.s390x.rpm
SUSE Linux 31-bit Enterprise 64-bit Server 9 for IBM System z
SUSE Linux Enterprise Server 10 for IBM System z
64-bit
For the most current information about IBM Director required and recommended fixes, go to the IBM Director Web site at www.ibm.com/systems/ management/director/. v Endpoints for which you want to support z/VM specific information in the inventory collections: Make sure that z/VM control program (CP) commands can be issued from Linux. See IBM Director z/VM Center Installation and Users Guide. v If you want to activate a firewall on the Linux system, ensure that the ports required by IBM Director are open. v If you want to use IBM Director Server on System z servers to manage a heterogeneous environment, you must install the applicable IBM Director Agent or IBM Director Core Services for each IBM platform that you want to manage. You can obtain these versions of IBM Director Agent or IBM Director Core Services from the IBM Director Support Web site at www.ibm.com/systems/ management/director/ or, if it was included with your IBM Director distribution, from the IBM Director Agents & Consoles, V5.20 (1 of 2) CD.
Preparing to install IBM Director Server on Linux on POWER

Before installing IBM Director Server on Linux on POWER, make sure that your platform meets the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation: v Make sure that the system meets the hardware and software requirements for installation described in Specified operating environments. v Ensure that the X Window System package group is installed. IBM Director Console requires RPMs that are installed with the X Window System package group.
150
v Ensure that the required RPM files (or later versions) are installed:
Table 57. Required RPMs Installation scenario Red Hat Enterprise Linux AS, version 4, for IBM POWER Required RPMs compat-libstdc++-33-3.2.3-47.3.ppc.rpm librtas-1.2-1.ppc64.rpm lsvpd-0.12.7-1.ppc.rpm diagela-2.1.5-0.ppc64.rpm servicelog-0.2.1-2.ppc64.rpm powerpc-utils-1.0.0-1.ppc64.rpm powerpc-utils-papr-1.0.3-1.ppc64.rpm compat-libstdc++-33-3.2.3-47.3.ppc.rpm librtas-1.2-1.ppc64.rpm lsvpd-0.12.7-1.ppc.rpm diagela-2.1.5-0.ppc64.rpm servicelog-0.2.1-2.ppc64.rpm powerpc-utils-1.0.0-1.ppc64.rpm powerpc-utils-papr-1.0.3-1.ppc64.rpm
Red Hat Enterprise Linux AS, version 5.0, for IBM POWER SUSE Linux Enterprise Server 9 and 10 for IBM POWER
Preparing to install IBM Director Server on Windows

Before installing IBM Director on a management server running Windows, make sure that your server meets all the applicable requirements. Note: Because installing IBM Director Server on Windows also installs IBM Director Agent and IBM Director Console, the preparation steps for IBM Director Server also include preparation steps for IBM Director Agent and IBM Director Console. Review the following information and complete the necessary steps to prepare your system for installation: v Make sure that the system meets the hardware and software requirements for installation described in Specified operating environments. v Systems with service processors: Install the supporting device drivers and mapping layers, if they are not already installed. See Preparing to manage service processors with IBM Director for information about these drivers and mapping layers. v If you want to use IBM Director Server on System x for heterogeneous server management, you can install IBM Director Agent or IBM Director Core Services on the platforms you want to manage. You can obtain IBM Director Agent andIBM Director Core Services for the supported operating systems from the IBM Director Web site at www.ibm.com/systems/management/director/ or, if it was included with your IBM Director distribution, from the IBM Director Agents & Consoles (1 of 2) CD. Related tasks Preparing Windows XP managed systems on page 170 Some Windows XP systems might need to be configured before you can be discover them with IBM Director Server. Make sure each Windows XP system that you want to manage has been appropriately configured. Preparing to manage service processors with IBM Director on page 135 You can use IBM Director to manage supported service processors that are installed in a managed system. Related reference
151
Hardware requirements for IBM Director on page 67 To successfully install IBM Director, the system on which you install IBM Director components must meet certain minimum hardware requirements, depending on the components to be installed and the type of system on which they will be installed. Network requirements on page 70 IBM Director requires certain ports to be available and certain network protocols to be installed in order to enable communication among IBM Director components and between the management server and managed objects. In addition, network connectivity must exist between the management server and managed objects, and between the management server and the management console.
Preparing a system for IBM Director Console

Before installing IBM Director Console make sure that the requirements that are applicable to your system have been met.
Preparing to install IBM Director Console on AIX

Before installing IBM Director Console on AIX, make sure that your platform meets the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation: Ensure that the following packages are installed: v sysmgt.sguide v sysmgt.websm
Preparing to install IBM Director Console on Linux for System x

Before installing IBM Director Console on a management console running Linux for System x, make sure that your platform meets the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation: v Make sure that the system meets the hardware and software requirements for installation described in Specified operating environments. v Ensure that the X Window System package group is installed. IBM Director Console requires RPMs that are installed with the X Window System package group. v Ensure that the required RPMs are installed:
Table 58. Required RPMs Installation scenario Red Hat Enterprise Linux AS and ES, version 3.0 Red Hat Enterprise Linux AS and ES, version 4.0 Required RPM compat-libstdc++-7.3-2.96.122.i386.rpm compat-libstdc++-296-2.96-132.7.2.i386.rpm
64-bit Intel Itanium system running compat-libstdc++-33-3.2.3-47.3.ia64.rpm Red Hat Enterprise Linux AS, version 4.0, for Intel Itanium Upgrading from IBM Director, rpm-4.1.1-177.9.i586.rpm version 4.20 or later on SUSE Linux Enterprise Server 9 for x86
152
Preparing to install IBM Director Console on Linux for System z

Before installing IBM Director Console on Linux for System z, make sure that your platform meets the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation: v To access IBM Director Console on Linux on System z, you need a fast network connection to a workstation with a Virtual Network Computing (VNC) client or an X Window System. v Depending on the component you intend to install, you can use a CD or installation code downloaded from the Web as your installation code. System z mainframes, typically, do not have directly attached CD-ROM drives. If you are using a CD, you might have to mount the CD on a different platform. Table 59 lists some methods of making the installation code available.
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z: Ensure that the Compatibility Arch Support package group is installed. The Compatibility Arch Support package group includes a number of RPMs that are required by IBM Director. The Compatibility Arch Support package group can be installed in two ways: During installation of Red Hat Enterprise Linux, by selecting the Compatibility Arch Support package group for installation. After installation of Red Hat Enterprise Linux, by using the system-config-packages tool. Install the system-config-packages tool using the system-config-packages-1.2.23-1.noarch.rpm file, and then run the system-config-packages tool to install the Compatibility Arch Support package group.
153
In either case, you must have the Red Hat Enterprise Linux installation media (or an ISO image of the installation media) available to install the Compatibility Arch Support package group. v Ensure that the X Window System package group is installed. IBM Director Console requires RPMs that are installed with the X Window System package group. v Ensure that the following RPMs are installed.
64-bit
For the most current information about IBM Director required and recommended fixes, go to the IBM Director Web site at www.ibm.com/systems/ management/director/.
Preparing to install IBM Director Console on Linux on POWER

Before installing IBM Director Console on Linux on POWER, make sure that your platform meets the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation: v Ensure that the X Window System package group is installed. IBM Director Console requires RPMs that are installed with the X Window System package group. v IBM BladeCenter JS20 and JS21 blade servers only: To access IBM Director Console on an IBM BladeCenter JS20 or JS21 blade server, you need a fast network connection to a workstation with a Virtual Network Computing (VNC) client or an X Window System.
Preparing to install IBM Director Console on Windows

Before installing IBM Director Console on a management console running Windows, make sure that your system meets the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation:
154
Make sure that the system meets the hardware and software requirements for installation described in Specified operating environments. Related tasks Installing IBM Director Console on Windows on page 217 You can use the InstallShield wizard to install IBM Director Console on any Windows system from which you want to remotely access IBM Director Server. The wizard can be used in a standard interactive mode, or you can perform an unattended installation using a response file to provide answers to the questions that the wizard poses. Related reference Hardware requirements for IBM Director on page 67 To successfully install IBM Director, the system on which you install IBM Director components must meet certain minimum hardware requirements, depending on the components to be installed and the type of system on which they will be installed. Network requirements on page 70 IBM Director requires certain ports to be available and certain network protocols to be installed in order to enable communication among IBM Director components and between the management server and managed objects. In addition, network connectivity must exist between the management server and managed objects, and between the management server and the management console.
Preparing a Level-2 managed system

Before installing Level 2: IBM Director Agent on a managed system make sure that the requirements that are applicable to your system have been met.
Preparing to install IBM Director Agent on AIX

Before installing IBM Director Agent on AIX, make sure that your platform meets the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation: AIX only: Before installing IBM Director Server or IBM Director Agent on AIX, complete the following preparatory steps: 1. Verify that required APAR fixes are installed on your system. 5.20.1 only: When installing the sysmgt.pegasus.cimserver fileset at the recommended level, the installation of these prerequisites are enforced, but you will need to download the APAR installation images as described below if they are not already installed. v IY78923 is required for all supported versions of AIX v IY76140 is required for AIX 5.3 running a 64-bit kernel v IY76141 is required for AIX 5.2 running a 64-bit kernel v IY86709 is required for AIX 5.2 at TL09. The Technology Level can be verified with the oslevel -r command. Complete the following steps to verify that you have the required fixes installed. a. Type one of the following commands and press Enter: AIX 5.3: instfix -i -k " IY76140 IY78923" AIX 5.2: instfix -i -k "IY76141 IY78923 IY86709" (IY86709 is only necessary if the system is at AIX 5.2 TL09)
155
If the required APARs are installed, continue to step 2. b. Check to see if filesets incorporating these APAR fixes are installed. v IY78923 is included in the following filesets: xlC.aix50.rte (version 8.0.0.2 or higher), xlC.rte (version 8.0.0.0 or higher), xlsmp.aix50.rte (version 1.6.0.0 or higher) and xlsmp.rte (version 1.6.0.0 or higher). v IY76140 is included in the following filesets: bos.mp and bos.mp64 at version 5.3.0.32 or higher. v IY76141 is included in the following filesets: bos.mp and bos.mp64 at version 5.2.0.89 or higher. v IY86709 is included in the following fileset: bos.rte.shell 5.2.0.95 or higher If the required APARs are included in your installed filesets, continue to step 3. c. Download and install the required APARs from the following address: http://www.ibm.com/eserver/support/fixes/fixcentral. 1) Select UNIX servers. 2) Select AIX operating system. 3) Select 5.2 or 5.3. 4) Select Specific fixes. 5) Click Continue, and then follow the instructions on the succeeding pages to select and download the APARs you need. 2. Ensure that the following AIX Pegasus CIM Server and providers are installed and functional:
Table 61. AIX Pegasus CIM Server and providers Version 5.20 Installation requirements v openssl-0.9.7g-1.aix5.1.ppc.rpm or higher (must be installed before installing the pegasus filesets) v sysmgt.pegasus.cimserver 2.5.1.0 or higher v sysmgt.pegasus.osbaseproviders 1.2.6.0 or higher v sysmgt.pegasus.smisproviders 1.1.0.0 or higher v openssl-0.9.7g-1.aix5.1.ppc.rpm or higher (must be installed before installing the pegasus filesets) v sysmgt.pegasus.cimserver 2.5.1.21 or higher v sysmgt.pegasus.osbaseproviders 1.2.6.21 or higher v sysmgt.pegasus.smisproviders 1.1.0.21 or higher
5.20.1
For more information about installation and requirements for OpenSSL and Pegasus, see the System p and AIX information center at publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cim/doc/ cim/ciminstall.htm#ciminstall. This information center contains instructions on how to use the lslpp -l command to verify that the installed Pegasus filesets are at the required version. It also tells how to verify what version of OpenSSL is installed. The OpenSSL provider can be obtained from the following Web site: www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=aixtbx &S_PKG=dlaixww. 3. Recommended, not required: Back up the CIM repository. Type the following two commands, substituting a date string for date and pressing Enter after each command:
/opt/freeware/cimom/pegasus/bin/cimserver -s cp -pRh /opt/freeware/cimom/pegasus/etc/repository /opt/freeware/cimom/pegasus/etc/repository.backup.date
Additional configuration and troubleshooting information about the AIX Pegasus CIM Server is available in the following two documents:
156
v The Common Information Model Guide for AIX, which is available at publib.boulder.ibm.com/infocenter/pseries/v5r3/topic/com.ibm.aix.cim/doc/ cim/cim.pdf v The README file that is installed with the sysmgt.pegasus.cimserver fileset in /opt/freeware/cimom/pegasus/ Refer to these documents if you encounter problems running the AIX Pegasus CIM Server. Both the Guide and README contain instructions on repository recovery if needed.
Preparing to install Level 2: IBM Director Agent on i5/OS

Before installing IBM Director Agent on i5/OS, there are several items to consider, such as the type of media on which the installation files are saved, the user profile that is used to install IBM Director, and the additional software that might be required. Review the following information and complete the necessary steps to prepare your system for installation: v If you want to use IBM Director Server on a System i platform to manage a heterogeneous environment, you must install the applicable IBM Director Agent or IBM Director Core Services package on each IBM platform that you want to manage. You can obtain these versions of IBM Director Agent and IBM Director Core Services from the IBM Director support Web site at www.ibm.com/systems/ management/director/ or from the IBM Director Agents & Consoles (1 of 2) CD. Note: IBM Director Core Services is not supported on i5/OS. v Your user profile should have *ALLOBJ and *SECADM special authorities. v Do not install IBM Director Agent over IBM Director Server. Complete the following steps to check if IBM Director Server is installed: 1. From a command prompt, type GO LICPGM and press Enter. 2. Select option 10, Display installed licensed programs, and review the list of installed programs. If installed, IBM Director Server is displayed in the list as one of the following entries (depending on the version):
5722DR1 *BASE IBM DIRECTOR 5733VE1 30 5050 IBM Director Multiplatform, 4.2.0
If IBM Director Server is installed, you must uninstall it before installing IBM Director Agent. You can use option 12 from the LICPGM menu to uninstall the product or option. v If you plan to use Software Distribution to distribute IBM Director Agent to Level-0 managed systems that are running i5/OS, ensure you have installed and configured Open SSH, provided in i5/OS Utilities, *BASE and Option 1 (order number 5733-SC1) on the managed systems. For more information about Open SSH, go to www.openssh.org. v If you plan to use IBM Director to monitor SNMP devices in your System i environment, ensure you have completed the necessary configuration tasks for System i and SNMP devices. See the Networking topic in the System i Information Center for more information.
Preparing to install IBM Director Agent on Linux on POWER

Before installing IBM Director Agent on Linux on POWER, make sure that your platform meets the applicable requirements.
157
Review the following information and complete the necessary steps to prepare your system for installation: Ensure that the required RPM files (or later versions) are installed:
Preparing to install IBM Director Agent on Linux for System x

Before installing IBM Director Agent on a managed system running Linux for System x, make sure that your system meets all the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation: v Make sure that the system meets the hardware and software requirements for installation described in Specified operating environments. v Make sure that the instance of IBM Director Agent will be fully functional and able to send alerts to IBM Director Server. For the IBM Director Agent to be fully functional you might need to install service-processor device drivers or the IBM LM78 and SMBus device drivers for Linux. v Ensure that the required RPMs are installed:
v Systems with service processors: Install the supporting device drivers and mapping layers, if they are not already installed. See Preparing to manage service processors with IBM Director for information about these drivers and mapping layers.
158
v If you want to use the Remote Session task on the managed system, make sure that the package that contains telnetd daemon is installed and configured. This package is usually in the telnet_server_version.i386.RPM package, where version is the code level of your Linux distribution. v If you want to use IBM Director Server on System x for heterogeneous server management, you can install IBM Director Agent or IBM Director Core Services on the platforms you want to manage. You can obtain IBM Director Agent andIBM Director Core Services for the supported operating systems from the IBM Director Web site at www.ibm.com/systems/management/director/ or, if it was included with your IBM Director distribution, from the IBM Director Agents & Consoles (1 of 2) CD. Related tasks Preparing to manage service processors with IBM Director on page 135 You can use IBM Director to manage supported service processors that are installed in a managed system.
Preparing to install IBM Director Agent on Linux for System z

Before installing IBM Director Agent on Linux for System z, make sure that your platform meets the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation: v Depending on the component you intend to install, you can use a CD or installation code downloaded from the Web as your installation code. System z mainframes, typically, do not have directly attached CD-ROM drives. If you are using a CD, you might have to mount the CD on a different platform. Table 64 lists some methods of making the installation code available.
159
v Endpoints for which you want to support z/VM specific information in the inventory collections: Make sure that z/VM control program (CP) commands can be issued from Linux. v Red Hat Enterprise Linux AS, version 4.0, for IBM System z: Ensure that the Compatibility Arch Support package group is installed. The Compatibility Arch Support package group includes a number of RPMs that are required by IBM Director. The Compatibility Arch Support package group can be installed in two ways: During installation of Red Hat Enterprise Linux, by selecting the Compatibility Arch Support package group for installation. After installation of Red Hat Enterprise Linux, by using the system-config-packages tool. Install the system-config-packages tool using the system-config-packages-1.2.23-1.noarch.rpm file, and then run the system-config-packages tool to install the Compatibility Arch Support package group. In either case, you must have the Red Hat Enterprise Linux installation media (or an ISO image of the installation media) available to install the Compatibility Arch Support package group. v Ensure that the following RPMs are installed.
64-bit
For the most current information about IBM Director required and recommended fixes, go to the IBM Director Web site at www.ibm.com/systems/ management/director/. v If you want to use IBM Director Server on System z mainframes to manage a heterogeneous environment, you must install the applicable IBM Director Agent or IBM Director Core Services for each IBM platform that you want to manage. You can obtain these versions of IBM Director Agent or IBM Director Core Services from the IBM Director Web site at www.ibm.com/systems/ management/director/ or, if it was included with your IBM Director distribution, from the IBM Director Agents & Consoles, V5.20 (1 of 2) CD.
160
Preparing to install IBM Director Agent on Windows

Before installing IBM Director Agent on a managed system running Windows, make sure that your system meets all the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation: v Make sure that the system meets the hardware and software requirements for installation described in Specified operating environments. v Systems with service processors: Install the supporting device drivers and mapping layers, if they are not already installed. See Preparing to manage service processors with IBM Director for information about these drivers and mapping layers. v If you want to use IBM Director Server on System x for heterogeneous server management, you can install IBM Director Agent or IBM Director Core Services on the platforms you want to manage. You can obtain IBM Director Agent andIBM Director Core Services for the supported operating systems from the IBM Director Web site at www.ibm.com/systems/management/director/ or, if it was included with your IBM Director distribution, from the IBM Director Agents & Consoles (1 of 2) CD. v The IBM Director on x86 CD no longer includes OpenSSH for Windows. If a Level-1 or Level-2 managed system does not have a Secure Shell (SSH) package installed, IBM Director Server cannot communicate securely with the managed system. To secure communication, you can install Open SSH on the managed system. You can download OpenSSH for Windows from www.sourceforge.net/ projects/sshwindows/. To update a managed system with SSH, start IBM Update Assistant and create a software package using the dirversion_coreservices-toc-windows.xml file that is located on the IBM Director on x86 CD or downloaded installation package, where version is the version number of IBM Director. When prompted, import the OpenSSH download into the IBM Update Assistant package. Use Software Distribution to distribute the package to the managed system. Related tasks Preparing Windows XP managed systems on page 170 Some Windows XP systems might need to be configured before you can be discover them with IBM Director Server. Make sure each Windows XP system that you want to manage has been appropriately configured. Installing Level 2:IBM Director Agent on 32-bit Windows on page 245 After preparing your system, you can install Level 2:IBM Director Agent on a 32-bit Windows system by downloading the installation file or using the CD. The wizard can be used in a standard interactive mode, or you can perform an unattended installation using a response file to provide answers to the questions that the wizard poses. Installing Level 2: IBM Director Agent on 64-bit Windows (Intel Itanium only) on page 251 After preparing your system, you can install Level 2: IBM Director Agent on a 64-bit Windows Intel Itanium. Preparing to manage service processors with IBM Director on page 135 You can use IBM Director to manage supported service processors that are installed in a managed system. Related reference Hardware requirements for IBM Director on page 67 To successfully install IBM Director, the system on which you install IBM
161
Director components must meet certain minimum hardware requirements, depending on the components to be installed and the type of system on which they will be installed. Network requirements on page 70 IBM Director requires certain ports to be available and certain network protocols to be installed in order to enable communication among IBM Director components and between the management server and managed objects. In addition, network connectivity must exist between the management server and managed objects, and between the management server and the management console.
Preparing a Level-1 managed system

Before installing Level 1: IBM Director Core Services on a managed system make sure that the requirements that are applicable to your system have been met. Perform the following steps on each system to be managed with IBM Director Core Services: 1. Set the clock on the managed system to match the time of the management server. If the managed system time is earlier than that of the management server, the management server will be unable to unlock the managed system. To avoid the problem of system-time mismatch, you can configure managed systems and the management server to synchronize their clocks using a common network time protocol (NTP) server. 2. (Level-1 managed systems with ServeRAID controllers only) In order for the management server to receive inventory data and events information from the system, you must install the ServeRAID Manager program (Standalone Edition), version 8.20 or later. You can download this program from the IBM ServeRAID Software Matrix site at www-306.ibm.com/pc/support/site.wss/ MIGR-495PES.html. 3. The chkconfig bug fix for Red Hat Enterprise Linux AS, ES, and WS, version 3.0 must be installed on Level-1 managed systems running the following operating systems: v Red Hat Enterprise Linux AS, version 3.0 v Red Hat Enterprise Linux ES, version 3.0 v Red Hat Enterprise Linux WS, version 3.0 IBM Director Server might not discover these systems if the chkconfig bug fix is not installed. For more information about the chkconfig bug fix and how to download it, go to rhn.redhat.com/errata/RHBA-2005-116.html.
Preparing to install IBM Director Core Services on Linux on POWER

Before installing IBM Director Core Services on Linux on POWER, make sure that your platform meets the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation: v SUSE Linux Enterprise Server 9 and 10 only: Disable the Service Location Protocol daemon (SLPD) before installing IBM Director Core Services. IBM Director Server does not discover Level-1 managed objects that are running SLPD.
162
v Ensure that the required RPM files (or later versions) are installed:
Preparing to install IBM Director Core Services on Linux for System x

Before installing IBM Director Core Services on a managed system running Linux for System x, make sure that your system meets all the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation: v Make sure that the system meets the hardware and software requirements for installation described in Specified operating environments. v Make sure that the instance of IBM Director Agent will be fully functional and able to send alerts to IBM Director Server. For the IBM Director Agent to be fully functional you might need to install service-processor device drivers or the IBM LM78 and SMBus device drivers for Linux. v Ensure that the required RPMs are installed:
v Systems with service processors: Install the supporting device drivers and mapping layers, if they are not already installed. See Preparing to manage service processors with IBM Director for information about these drivers and mapping layers. v If you want to use the Remote Session task on the managed system, make sure that the package that contains telnetd daemon is installed and configured. This
163
package is usually in the telnet_server_version.i386.RPM package, where version is the code level of your Linux distribution. v If you want to use IBM Director Server on System x for heterogeneous server management, you can install IBM Director Agent or IBM Director Core Services on the platforms you want to manage. You can obtain IBM Director Agent andIBM Director Core Services for the supported operating systems from the IBM Director Web site at www.ibm.com/systems/management/director/ or, if it was included with your IBM Director distribution, from the IBM Director Agents & Consoles (1 of 2) CD. Related tasks Preparing to manage service processors with IBM Director on page 135 You can use IBM Director to manage supported service processors that are installed in a managed system.
Preparing to install IBM Director Core Services on Linux for System z

Before installing IBM Director Core Services on Linux for System z, make sure that your platform meets the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation: v Depending on the component you intend to install, you can use a CD or installation code downloaded from the Web as your installation code. System z mainframes, typically, do not have directly attached CD-ROM drives. If you are using a CD, you might have to mount the CD on a different platform. Table 68 lists some methods of making the installation code available.
164
v Endpoints for which you want to support z/VM specific information in the inventory collections: Make sure that z/VM control program (CP) commands can be issued from Linux. v Red Hat Enterprise Linux AS, version 4.0, for IBM System z: Ensure that the Compatibility Arch Support package group is installed. The Compatibility Arch Support package group includes a number of RPMs that are required by IBM Director. The Compatibility Arch Support package group can be installed in two ways: During installation of Red Hat Enterprise Linux, by selecting the Compatibility Arch Support package group for installation. After installation of Red Hat Enterprise Linux, by using the system-config-packages tool. Install the system-config-packages tool using the system-config-packages-1.2.23-1.noarch.rpm file, and then run the system-config-packages tool to install the Compatibility Arch Support package group. In either case, you must have the Red Hat Enterprise Linux installation media (or an ISO image of the installation media) available to install the Compatibility Arch Support package group. v Ensure that the following RPMs are installed.
Table 69. Required RPMs Installation scenario Red Hat 31-bit Enterprise Linux AS, version 4.0, for IBM 64-bit System z Required RPMs compat-libstdc++-295-2.95.3-81.s390.rpm compat-libstdc++-33-3.2.3-47.3.s390.rpm xorg-x11-deprecated-libs-6.8.2-1.EL.13.36.s390.rpm compat-libstdc++-295-2.95.3-81.s390.rpm compat-libstdc++-33-3.2.3-47.3.s390.rpm pam-0.77-66.14.s390.rpm xorg-x11-deprecated-libs-6.8.2-1.EL.13.36.s390.rpm libstdc++-3.4.6-3.s390.rpm compat-libstdc++-295-2.95.3-85.s390.rpm compat-libstdc++-33-3.2.3-61.s390.rpm libstdc++-4.1.1-52.el5.s390.rpm pam-0.99.6.2-3.14.el5.s390.rpm compat-2004.7.1-1.2.s390.rpm compat-2004.7.1-1.2.s390x.rpm compat-32bit-9-200407011411.s390x.rpm pam-32bit-0.99.3.0-29.4.s390x.rpm pam-modules-32bit-10-2.2.s390x.rpm XFree86-libs-32bit-9-200512021711.s390x.rpm compat-32bit-2006.1.25-11.2.s390x.rpm pam-32bit-0.99.3.0-29.4.s390x.rpm pam-modules-32bit-10-2.2.s390x.rpm xorg-x11-libs-32bit-6.9.0-50.14.s390x.rpm
Red Hat 64-bit Enterprise Linux AS, version 5.0, for IBM System z SUSE Linux 31-bit Enterprise 64-bit Server 9 for IBM System z
64-bit
For the most current information about IBM Director required and recommended fixes, go to the IBM Director Web site at www.ibm.com/systems/ management/director/. v If you want to use IBM Director Server on System z mainframes to manage a heterogeneous environment, you must install the applicable IBM Director Agent or IBM Director Core Services for each IBM platform that you want to manage. You can obtain these versions of IBM Director Agent or IBM Director Core Services from the IBM Director Web site at www.ibm.com/systems/
165
management/director/ or, if it was included with your IBM Director distribution, from the IBM Director Agents & Consoles, V5.20 (1 of 2) CD.
Preparing to install IBM Director Core Services on Windows

Before installing IBM Director Core Services on a managed system running Windows, make sure that your system meets all the applicable requirements. Review the following information and complete the necessary steps to prepare your system for installation: v Make sure that the system meets the hardware and software requirements for installation described in Specified operating environments. v Systems with service processors: Install the supporting device drivers and mapping layers, if they are not already installed. See Preparing to manage service processors with IBM Director for information about these drivers and mapping layers. v If you want to use IBM Director Server on System x for heterogeneous server management, you can install IBM Director Agent or IBM Director Core Services on the platforms you want to manage. You can obtain IBM Director Agent andIBM Director Core Services for the supported operating systems from the IBM Director Web site at www.ibm.com/systems/management/director/ or, if it was included with your IBM Director distribution, from the IBM Director Agents & Consoles (1 of 2) CD. v The IBM Director on x86 CD no longer includes OpenSSH for Windows. If a Level-1 or Level-2 managed system does not have a Secure Shell (SSH) package installed, IBM Director Server cannot communicate securely with the managed system. To secure communication, you can install Open SSH on the managed system. You can download OpenSSH for Windows from www.sourceforge.net/ projects/sshwindows/. To update a managed system with SSH, start IBM Update Assistant and create a software package using the dirversion_coreservices-toc-windows.xml file that is located on the IBM Director on x86 CD or downloaded installation package, where version is the version number of IBM Director. When prompted, import the OpenSSH download into the IBM Update Assistant package. Use Software Distribution to distribute the package to the managed system. Related tasks Preparing Windows XP managed systems on page 170 Some Windows XP systems might need to be configured before you can be discover them with IBM Director Server. Make sure each Windows XP system that you want to manage has been appropriately configured. Installing Level 1: IBM Director Core Services on Windows on page 226 To install Level 1: IBM Director Core Services on a system that is running Windows, download the installation files from the IBM Director support Web site or use the CD. You can perform a standard installation or you can use a response file to customize the installation for your environment. Preparing to manage service processors with IBM Director on page 135 You can use IBM Director to manage supported service processors that are installed in a managed system. Related reference Hardware requirements for IBM Director on page 67 To successfully install IBM Director, the system on which you install IBM Director components must meet certain minimum hardware requirements, depending on the components to be installed and the type of system on which they will be installed.
166
Network requirements on page 70 IBM Director requires certain ports to be available and certain network protocols to be installed in order to enable communication among IBM Director components and between the management server and managed objects. In addition, network connectivity must exist between the management server and managed objects, and between the management server and the management console.
Preparing to manage a BladeCenter

IBM Director can be deployed to manage the blade servers in a BladeCenter chassis.
Preparing to manage a BladeCenter chassis using IBM Director Server on a non-blade server
You can install IBM Director Server on a non-blade server. With this management server you can manage one or more BladeCenter units and the blade servers installed in them. You must configure the network to allow this installation. Perform the following steps to prepare to manage an IBM BladeCenter chassis using IBM Director Server installed on a non-blade server. 1. Consider using a Dynamic Host Configuration Protocol (DHCP) server to assign an address to the external port of the management module. When a BladeCenter management module is first started, it searches for a DHCP server. If a DHCP server is not found, the BladeCenter management module assigns IP address 192.168.70.125 to the external management port. Because this static IP address is the same for all management modules, IP address conflicts can occur if you do not use a DHCP server and introduce multiple BladeCenter chassis onto a network simultaneously. When you configure the BladeCenter chassis, you assign static IP addresses to the switch module and the external and internal ports of the management module. 2. Set up a separate management network to configure and manage your BladeCenter chassis and blade servers. By separating the LAN segment used for production from the LAN segment to which the BladeCenter management module is connected, you can ensure that only authorized system administrators can connect to the BladeCenter chassis and switch modules. Figure 4 on page 168 shows such a network configuration. 3. If you intend to use Remote Deployment Manager (RDM), install RDM on the management server. 4. If you plan to use a database application other than Apache Derby, consider installing the database server on the management LAN. 5. Make sure that you have installed the latest version of the management module firmware. To download the firmware, go to the IBM Servers Web site at www.ibm.com/servers/.
167
Figure 4. Example of BladeCenter deployment network when IBM Director Server is not installed on a blade server
This network configuration ensures that applications running on the blade servers cannot modify chassis settings, because the blade servers have no connection to either the management module or the switch module configuration ports. Note: Only one of the following software applications can communicate with a BladeCenter management module at any given time: v Cluster Systems Management (CSM) v IBM Director Server v IBM Management Processor Command-Line Interface (MPCLI)
Preparing to manage a BladeCenter chassis using IBM Director Server on a blade server
You can install IBM Director Server on a blade server. With this management server you can manage the BladeCenter unit, including the server on which IBM Director Server is installed, and other BladeCenter units. You must configure the network to allow this installation. Consider the following issues when managing the BladeCenter unit that contains the management server: v Enable access for authorized administrators as determined by the security policy established for the user environment. v Be careful when making changes to the configuration of the BladeCenter chassis from IBM Director itself. Such changes could effectively remove the instance of IBM Director Server from the network and halt the entire IBM Director environment. Specifically, do not perform these tasks on the blade server where IBM Director Server is installed without careful consideration: Using Remote Deployment Manager (RDM) to deploy software to that blade server Powering off that blade server Changing the boot options on that blade server
168
v Create a network setup that enables the BladeCenter Management Module to communicate with the management server. Otherwise IBM Director will be unable to discover the BladeCenter chassis that contains the management server. By default, the blade servers installed in a BladeCenter chassis cannot communicate automatically with the BladeCenter Management Module. This architecture is designed to prevent the blade servers from modifying the BladeCenter chassis settings. If you install IBM Director Server on a blade server and want to use the instance of IBM Director to manage the BladeCenter unit in which the management server is installed, you must enable communication between the management server and the management module. 1. Consider using a Dynamic Host Configuration Protocol (DHCP) server to assign an address to the external port of the management module. When a BladeCenter management module is first started, it searches for a DHCP server. If a DHCP server is not found, the BladeCenter management module assigns IP address 192.168.70.125 to the external management port. Because this static IP address is the same for all management modules, IP address conflicts can occur if you do not use a DHCP server and introduce multiple BladeCenter chassis onto a network simultaneously. When you configure the BladeCenter chassis, you assign static IP addresses to the switch module and the external and internal ports of the management module. 2. Set up a separate management network to configure and manage your BladeCenter chassis and blade servers. By separating the LAN segment used for production from the LAN segment to which the BladeCenter management module is connected, you can ensure that only authorized system administrators can connect to the BladeCenter chassis and switch modules. Figure 4 on page 168 shows such a network configuration. 3. To use an installation of IBM Director Server on a blade to manage the BladeCenter unit in which the management server is installed, enable communication between the Campus LAN and the Management LAN. Figure 5 on page 170 shows such a network configuration. 4. If you intend to use Remote Deployment Manager (RDM), install RDM on the management server. 5. If you plan to use a database application other than Apache Derby, consider installing the database server on the management LAN. 6. Make sure that you have installed the latest version of the management module firmware. To download the firmware, go to the IBM Servers Web site at www.ibm.com/servers/.
169
Figure 5. Example of BladeCenter deployment network when IBM Director Server is installed on a blade server
With this configuration, IBM Director Server can communicate through the Campus LAN to the Management LAN and then onto the management module. Note: Only one of the following software applications can communicate with a BladeCenter management module at any given time: v Cluster Systems Management (CSM) v IBM Director Server v IBM Management Processor Command-Line Interface (MPCLI)
Preparing Windows XP managed systems

Some Windows XP systems might need to be configured before you can be discover them with IBM Director Server. Make sure each Windows XP system that you want to manage has been appropriately configured. Typically, managed systems are first discovered using the Discovery task in IBM Director Console. Then, IBM Director Core Services or IBM Director Agent is installed on the managed systems directly from IBM Director Console. The configuration of some Windows XP managed systems, however, can prevent discovery by IBM Director Server. Perform the following steps on each Windows XP system to enable discovery by IBM Director Server: 1. Disable Simple File Sharing. Windows XP targets must have Simple File Sharing disabled for Level 0 discovery to work. Use the following steps to disable Simple File Sharing on the Windows XP system to be managed: a. Select Start Control Panel Folder Options. b. In the Folder Options window, click the View tab. c. In the View panel, scroll to the bottom of the Advanced settings list and clear the Use simple file sharing (Recommended) check box. d. Click OK.
170
2. Configure Windows Firewall (Internet Connection Firewall) to allow access by IBM Director Server. Windows XP (before Service Pack 2) includes a built-in firewall called Internet Connection Firewall (ICF), which is disabled by default. Windows XP Service Pack 2 includes Windows Firewall, which is enabled by default. Either firewall will block attempted accesses by Level 0 discovery unless the firewall is disabled or an exception is defined for the management server on which IBM Director Server is installed. Use the following steps to enable IBM Director Server to access the managed system: a. Select Start Control Panel Network Connections connection. The connection is the network connection that will be used for discovery. Typically, this is Local Area Connection. b. In the General tab of the Connection Status window, click Properties. c. In the Connection Properties window, click the Advanced tab. d. In the Advanced panel, click the firewall Settings button. e. If the firewall is turned off, no further configuration is required. Continue to step 3. f. If the firewall is enabled, click the Exceptions tab. g. In the Exceptions panel, select the File and Printer Sharing check box. h. Click OK. Note: The network administrator can define a group policy for this configuration. 3. Verify that remote registry administration is enabled. Remote registry administration must be enabled in order for Level 0 discovery to run commands and run scripts on the managed system. The default setting for remote registry administration on Windows XP systems is enabled. Use the following steps to verify or change the remote registry administration setting: a. At a command prompt, type %SystemRoot%\system32\services.msc /s and press Enter. b. In the list of services in the Services window, right-click the Remote Registry service and select Properties from the menu. c. On the General page, set the Startup type to Automatic. d. If the Service status is not Started, click Start. e. Click OK to apply the new settings and close the window. 4. Verify the hidden administrative disk shares (such as C$, D$, etc). The default hidden administrative disk shares (such as C$, D$, and so on) are required for correct operation of Level 0 discovery.
Preparing Hardware Management Console devices for discovery with IBM Director
Before discovering Hardware Management Console (HMC) devices, and after upgrading HMC hardware, you might need to open the Pegasus and SLP ports to enable IBM Director to discover and manage the HMC. Complete the following steps to enable the Pegasus and SLP ports on the HMC device: 1. In the HMC Navigation Area pane, expand the affected HMC and expand HMC Management. Click HMC Configuration. 2. In the HMC Configuration pane, click Customize Network Settings.
171
3. In the Network Settings window, click the LAN Adapters tab. 4. Select the LAN Adapter that is connected to your LAN and click Details. 5. In the LAN Adapter Details window, click the Firewall tab. The top pane displays the firewall ports that you can enable. 6. In the top pane, select Open Pegasus and click Allow Incoming. Open Pegasus is added to the bottom pane of enabled ports. 7. In the top pane, select SLP and click Allow Incoming. SLP is added to the bottom pane of enabled ports. 8. Click OK; then click OK again. 9. If a message window about restarting the HMC is displayed, click OK. After the HMC is restarted, the ports are enabled and IBM Director Server can discover the HMC.
Installing IBM Director using the Standard installation

After preparing your systems and environment for IBM Director, use the applicable standard installation procedures to install IBM Director Server, IBM Director Console, Level 1: IBM Director Core Services, Level 2: IBM Director Agent, and IBM Director extensions.
Installing IBM Director Server using the Standard installation

After preparing your system, use the IBM Director Server Standard installation procedure for the applicable operating system on which plan to install IBM Director Server. Important: v IBM Director Server and IBM Director Console must be at the same release level. For example, if you install IBM Director Server, version 5.20.1 on the management server, you must also install IBM Director Console, version 5.20.1 on any systems that you want to access the management server. v If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server. v If you are planning to install and use a database for IBM Director other than the default database, make sure that you have installed and configured the database application that you will use with IBM Director before installing IBM Director Server. On management servers running i5/OS, IBM Director Server uses the DB2 database. On all other operating systems, the default database is Apache Derby, but other databases can be used. v On management servers not running i5/OS, IBM Director Server includes all the functionality of IBM Director Agent and IBM Director Console. It is not possible or necessary to separately install either IBM Director Agent or IBM Director Console on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent or IBM Director Console will be performed for systems with IBM Director Server installed. v On management servers running i5/OS, IBM Director Server includes all the functionality of IBM Director Agent. It is not possible or necessary to separately install IBM Director Agent on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent will be performed for systems with IBM Director Server installed.
172
v To use IBM Director Console to access IBM Director Server on a system that is running i5/OS, IBM Director Console must be installed on a separate non-i5/OS server. v Before installing IBM Director Server on a system that has IBM Director Console or IBM Director Agent installed, you must first uninstall the existing IBM Director component.
Installing IBM Director Server on AIX

After preparing your system, you can install IBM Director Server on AIX by downloading the AIX installation file or using the IBM Director for AIX 5L, V5.20 CD. You can perform a standard installation or you can use a response file to customize the features that are installed. Important: v IBM Director Server and IBM Director Console must be at the same release level. For example, if you install IBM Director Server, version 5.20.1 on the management server, you must also install IBM Director Console, version 5.20.1 on any systems that you want to access the management server. v If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server. v If you are planning to install and use a database for IBM Director other than the default database, make sure that you have installed and configured the database application that you will use with IBM Director before installing IBM Director Server. On management servers not running i5/OS, the default database is Apache Derby, but other databases can be used. v On management servers not running i5/OS, IBM Director Server includes all the functionality of IBM Director Agent and IBM Director Console. It is not possible or necessary to separately install either IBM Director Agent or IBM Director Console on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent or IBM Director Console will be performed for systems with IBM Director Server installed. v Before installing IBM Director Server on a system that has IBM Director Console or IBM Director Agent installed, you must first uninstall the existing IBM Director component. During the installation process, you can configure a database to use with IBM Director and change security settings. Optional: If you choose to use a database application other than Apache Derby with IBM Director, be sure to perform any necessary preparation steps before configuring IBM Director to use the database. For more information, see Preparing the IBM Director database on page 125. Depending on the version of IBM Director Server you are installing, you can install IBM Director Server on AIX from either installation media or from a downloaded installation package.
Table 70. Installation options for IBM Director Server on AIX
Version 5.20 5.20 Update 1 Installation media IBM Director for AIX 5L, V5.20 CD IBM Director for AIX 5L, Version 5.20 Update 1 CD Downloaded installation package file name Dir5.20_AIX.tar.gz Dir5.20.1_Server_AIX.tar.gz Dir5.20.1_AIX.iso Chapter 3. Installing
173
1. To install IBM Director Server from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. To unzip and extract the contents of the installation package, type the following command:
gzip -cd install_package | tar -xvf -
where install_package is the file name of the downloaded installation package. c. Go to step 3. 2. To install IBM Director Server from the CD, perform the following steps: a. Insert the CD into the CD-ROM drive. b. If the CD does not automount, type the following command and press Enter:
mount -v cdrfs -o ro /dev/cd0 /mnt
where dev/cd0 is the specific device file for the block device and mnt is the mount point of the drive. c. To change to the directory in which IBM Director Server is located, type the following command and press Enter:
cd /mnt/director/server/aix
where mnt is the mount point of the drive. Go to step 3. 3. If you want to customize the installation, go to step 4. If you want to accept the default settings for the installation, type the following command and press Enter:
./dirinstall
By default, the Apache Derby database application is installed and configured to work with IBM Director. Go to step 12 on page 178. 4. To customize the installation, copy the response file (dirserv.rsp) to a local directory. Type the following command and press Enter:
cp dirserv.rsp /directory
where directory is the local directory. 5. Open an ASCII text editor and modify the installation settings in the dirserv.rsp file. This file is fully commented. You can specify the location of the .bff files, select the IBM Director extensions and features that you want to install, configure a database to use with IBM Director, and select log file options. 6. Save the modified response file with a new file name. 7. To install IBM Director Server using the response file, type the following command and press Enter:
./dirinstall -r /directory/response.rsp
where directory is the local directory to which you copied the response file, and response.rsp is the name of the response file saved in step 6.
174
8. The selections you made in the response file determine what you do next.
Settings DbmsConfigMethod parameter set to GUI; running AIX in a graphical environment. Result and next steps The IBM Director Database Configuration window opens. Go to step 9. Note: If you set the DbmsConfigMethod parameter to GUI but are not running AIX in a graphical environment, you must perform the database configuration after the installation of IBM Director Server is complete. See Configuring the database on Linux or AIX on page 326. The database is configured silently during the installation. Go to step 12 on page 178.
DbmsConfigMethod parameter set to Rspfile; database configuration information provided.
DbmsConfigMethod parameter set to No database configuration is performed Rspfile; DbmsApplication parameter set to during the installation. Go to step 11 on noDatabase. page 177. DbmsConfigMethod parameter set to None. No database configuration is performed during the installation. Go to step 11 on page 177.
9. Select the database application to use with IBM Director. You have the following options: Apache Derby (Option on all platforms except i5/OS) Creates and configures an embedded Apache Derby database. The Apache Derby application is included in the IBM Director installation. IBM DB2 Universal Database Configures IBM Director to use an IBM DB2 database. IBM DB2 must be installed and configured on a system in your network. Oracle Configures IBM Director to use an Oracle database. Oracle Server must be installed and configured on a system in your network. Select later (database disabled) IBM Director will be installed without a database. Tasks requiring a database will be absent or not functional. Important: You can configure IBM Director for use with your database application at any point after the installation of IBM Director Server, but you must not start the management server until it is completed. Starting the management server before configuring IBM Director to use a database application might result in a loss of functionality. 10. Click Next to configure IBM Director for use with your database application.
Table 71. Database configuration If the database application is Apache Derby Complete the applicable steps The IBM Director Apache Derby Configuration window opens. The values cannot be changed. Click Next and go to step 12 on page 178.
175
Table 71. Database configuration (continued) If the database application is IBM DB2 Complete the applicable steps The IBM Director DB2 Universal Database Configuration window opens. Complete the following fields: 1. In the DB2 TCP/IP listener port field, type the number of the port that is used by the DB2 TCP/IP listener. 2. In the Server name field, type the name of the server where DB2 is installed. 3. In the Database name field, type the name of the database. 4. In the User ID field, type a valid DB2 user ID. 5. In the Password field, type the password for the DB2 user ID. Click Next and go to step 12 on page 178.
176
Table 71. Database configuration (continued) If the database application is Oracle Server Complete the applicable steps The IBM Director Oracle Database Configuration window opens. Complete the following fields: 1. In the Oracle TCP/IP listener port field, type the number of the port that is used by the Oracle TCP/IP listener. 2. In the Oracle host name field, type the TCP/IP host name of the database server. 3. In the Oracle System Identifier (SID) field, type the Oracle system identifier (SID). 4. In the User ID field, type a valid Oracle user ID. If it does not exist, it is created. By default, this user ID is assigned to the IBM Director table space. 5. In the Password and Confirm password fields, type the password that is associated with the user ID that you typed in step 4. 6. In the Oracle administrator account field, type a valid user ID for the Oracle administrator account. 7. In the Oracle administrator password field, type the password that is associated with the user ID that you typed in step 6. Click Next. A second IBM Director Oracle Database Configuration window opens. Complete the following fields: 1. In the Default tablespace name field, type a table space name. 2. In the Default tablespace data file field, type the name of the table space data file. If you do not specify the directory path, the table space data file will be created in the Oracle Server default directory. If you specify a directory path that is not valid, the database configuration will fail. 3. In the Default tablespace size (MB) field, type the size of the table space in MB. 4. In the Temporary tablespace name field, type a name for the temporary table space. 5. In the Temporary tablespace data file field, type the name of the temporary table-space data file. If you do not specify the directory path, the table-space data file will be created in the Oracle Server default directory. If you specify a directory path that is not valid, the database configuration will fail. 6. In the Temporary tablespace size (MB) field, type the size of the temporary table space in MB. Click Next and go to step 12 on page 178. Select later (database disabled) IBM Director is installed without a database configured. To configure a database after the installation of IBM Director Server, see Configuring the database on Linux or AIX on page 326. Go to step 12 on page 178.
11. Optional: Configure IBM Director for use with a database application. For more information, see Configuring the database on Linux or AIX on page 326.
177
Important: You can configure IBM Director for use with your database application at any point after the installation of IBM Director Server, but you must not start the management server until it is completed. Starting the management server before configuring IBM Director to use a database application might result in a loss of function. 12. Optional: By default, encryption using the Advanced Encryption Standard (AES) algorithm is enabled during installation. To disable encryption or change security settings, type the following command and press Enter:
install_root/bin/cfgsecurity
13. To start IBM Director Server, type the following command and press Enter:
/opt/ibm/director/bin/twgstart
14. If you used the CD to install IBM Director Server, unmount the drive by typing the following command and press Enter:
umount /mnt
where mnt is the mount point of the drive. 15. If you use the CD to install IBM Director Server, remove the CD from the drive.
Installing IBM Director Server on i5/OS

After you prepare an i5/OS system for an IBM Director Server installation, use the RSTLICPGM command to install IBM Director Server. Depending on the version of IBM Director Server you are installing, you can install IBM Director Server on i5/OS from either installation media or from a downloaded installation package.
Table 72. Installation options for IBM Director Server on i5/OS
Version 5.20 5.20 Update 1 Installation media IBM Director for i5/OS, V5.20 not available Downloaded installation package file name not available dir5.20.1_server_i5OS.zip
Installing IBM Director Server on i5/OS using installation media: If the version of IBM Director Server you are installing is available on installation media for i5/OS, use these instructions to install IBM Director Server on i5/OS. Important: v IBM Director Server and IBM Director Console must be at the same release level. For example, if you install IBM Director Server, version 5.20.1 on the management server, you must also install IBM Director Console, version 5.20.1 on any systems that you want to access the management server. v On management servers running i5/OS, IBM Director Server includes all the functionality of IBM Director Agent. It is not possible or necessary to separately install IBM Director Agent on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent will be performed for systems with IBM Director Server installed. v To use IBM Director Console to access IBM Director Server on a system that is running i5/OS, IBM Director Console must be installed on a separate non-i5/OS server. v Before installing IBM Director Server on a system that has IBM Director Agent installed, you must first uninstall the existing IBM Director component.
178
Before you install IBM Director Server, make sure that you have completed planning and preparing for the installation, and that the server meets the hardware requirements to install IBM Director. You also must meet the prerequisites included in Preparing to install IBM Director on i5/OS on page 142. To install IBM Director Server, complete the following steps: 1. Log on to the System i platform by using a profile with the following privileges: *ALLOBJ and *SECADM. Note: When your system is in a restricted state (endsbs *all *immed), TCP/IP is not active. As a result, IBM Director will not start automatically after the installation. After installing in a restricted state, run the strtcp command to start TCP/IP, and then start IBM Director. 2. Insert the CD into the CD-ROM drive. 3. Run RSTLICPGM. 4. In the Product field, type the product number for IBM Director Server (5722DR1). 5. In the Device field, type the optical device identifier, for example, opt01. 6. Press Enter. The installation progress for IBM Director Server is displayed. Continue with steps to install IBM Director Agent and IBM Director Console on the other systems in your IBM Director environment. After you have installed the components of IBM Director, complete the required configuration steps. Installing IBM Director Server on i5/OS using a downloaded installation package: If the version of IBM Director Server you are installing is available to be downloaded for i5/OS, use these instructions to install IBM Director Server on i5/OS. Important: v IBM Director Server and IBM Director Console must be at the same release level. For example, if you install IBM Director Server, version 5.20.1 on the management server, you must also install IBM Director Console, version 5.20.1 on any systems that you want to access the management server. v On management servers running i5/OS, IBM Director Server includes all the functionality of IBM Director Agent. It is not possible or necessary to separately install IBM Director Agent on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent will be performed for systems with IBM Director Server installed. v To use IBM Director Console to access IBM Director Server on a system that is running i5/OS, IBM Director Console must be installed on a separate non-i5/OS server. v Before installing IBM Director Server on a system that has IBM Director Agent installed, you must first uninstall the existing IBM Director component. Before you install IBM Director Server, make sure that you have completed planning and preparing for the installation, and that the server meets the hardware requirements to install IBM Director. You also must meet the prerequisites included in Preparing to install IBM Director on i5/OS on page 142. To install IBM Director Server, complete the following steps:
179
1. On a system that can connect to the i5/OS system, download the installation package from the IBM Director Web site at www.ibm.com/systems/ management/director/. 2. Extract the contents of the installation package into a local directory. 3. Log on to the System i platform by using a profile with the following privileges: *ALLOBJ and *SECADM. Note: When your system is in a restricted state (endsbs *all *immed), TCP/IP is not active. As a result, IBM Director will not start automatically after the installation. After installing in a restricted state, run the strtcp command to start TCP/IP, and then start IBM Director. 4. On the i5/OS system, type the following command and press Enter to create a save file for the SAVDR100MM.sav file:
CRTSAVF FILE(QGPL/SAVDR100MM)
5. From the directory into which you extracted the contents of the downloaded installation package, start an FTP session to the i5/OS system and then type the following commands, pressing Enter after each:
binary put FILES/SAVDR100MM.sav /qsys.lib/qgpl.lib/SAVDR100MM.file
6. Stop IBM Director Server by typing the following command from a command prompt and pressing Enter:
QSH CMD(/qibm/userdata/director/bin/twgend)
7. Verify that IBM Director Server has been stopped by typing the following command from a command prompt and pressing Enter:
QSH CMD(/qibm/userdata/director/bin/twgstat)
8. On the i5/OS system, type the following command and press Enter to install the upgrade:
RSTLICPGM LICPGM(5722DR1) DEV(*SAVF) SAVF(QGPL/SAVDR100MM)
9. Restart IBM Director Server by typing the following command from a command prompt and pressing Enter:
QSH CMD(/qibm/userdata/director/bin/twgstart)
10. Verify that IBM Director Server has been restarted by typing the following command from a command prompt and pressing Enter:
11. To delete the SAVDR100MM.sav file, type the following command and press Enter:
DLTF FILE(QGPL/SAVDR100MM)
Continue with steps to install IBM Director Agent and IBM Director Console on the other systems in your IBM Director environment. After you have installed the components of IBM Director, complete the required configuration steps.
Installing IBM Director Server on Linux for System x

When you install IBM Director Server, IBM Director Console and IBM Director Agent are installed automatically. During the installation process, you can install several IBM Director Agent features. You also can configure a database to use with IBM Director and change security settings. Important: v IBM Director Server and IBM Director Console must be at the same release level. For example, if you install IBM Director Server, version 5.20.1 on the
180
management server, you must also install IBM Director Console, version 5.20.1 on any systems that you want to access the management server. If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server. If you are planning to install and use a database for IBM Director other than the default database, make sure that you have installed and configured the database application that you will use with IBM Director before installing IBM Director Server. On management servers not running i5/OS, the default database is Apache Derby, but other databases can be used. On management servers not running i5/OS, IBM Director Server includes all the functionality of IBM Director Agent and IBM Director Console. It is not possible or necessary to separately install either IBM Director Agent or IBM Director Console on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent or IBM Director Console will be performed for systems with IBM Director Server installed. Before installing IBM Director Server on a system that has IBM Director Console or IBM Director Agent installed, you must first uninstall the existing IBM Director component.
Optional: If you choose to use a database application other than Apache Derby with IBM Director, be sure to perform any necessary preparation steps before configuring IBM Director to use the database. For more information, see Preparing the IBM Director database on page 125. Depending on the version of IBM Director Server you are installing, you can install IBM Director Server on Linux for System x from either installation media or from a downloaded installation package.
Table 73. Installation options for IBM Director Server on Linux for System x
Version 5.20 5.20 Update 1 Installation media IBM Director on x86, V5.20 CD IBM Director on x86, Version 5.20 Update 1 CD Downloaded installation package file name dir5.20_server_linux.tar dir5.20.1_server_linux.tar
1. To install IBM Director Server from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. To extract the contents of the installation package, type the following command:
tar -xvf install_package
where install_package is the file name of the downloaded installation package. c. Change to the directory in which the installation script is located. Type the following command and press Enter:
cd /install_files/
where install_files is the path to the extracted installation files. d. Go to step 3 on page 182. 2. To install IBM Director Server from the CD, perform the following steps:
181
a. Insert the CD into the CD-ROM drive. b. If the CD does not automount, mount the CD-ROM drive. Type the following command and press Enter:
mount /dev/cdrom /mnt/cdrom
where dev/cdrom is the specific device file for the block device and mnt/cdrom is the mount point of the drive. c. Change to the directory in which the installation script is located. Type the following command and press Enter:
cd /mnt/cdrom/director/server/linux/i386/
where mnt/cdrom is the mount point of the drive. 3. If you want to customize the installation, go to step 4. If you want to accept the default settings for the installation, type one of the following commands and press Enter: v Installing from CD: ./dirinstall v Installing from download (version 5.20): ./dir5.20_server_linux.sh v Installing from download (version 5.20.1): ./dir5.20.1_server_linux.sh Refer to the response file to find out what the defaults are. The response file is called dirserv.rsp and is located in the same directory as the installation script. In the response file, 1 indicates that an item is to be installed and 0 indicates that an item is not to be installed. v If you are running Linux in a graphical environment, go to step 10 on page 183. v If you are not running Linux in a graphical environment, go to step 12 on page 186. 4. To customize the installation, copy the response file (dirserv.rsp) to a local directory. Type the following command and press Enter:
where directory is the local directory to which you copied the response file. 5. Open an ASCII text editor and modify the installation settings in the dirserv.rsp file. This file is fully commented. You can specify the location of the RPM files, select the IBM Director extensions and features that you want to install, configure a database to use with IBM Director, and select log file options. 6. Save the modified response file with a new file name. 7. To install IBM Director Server using the response file, type one of the following commands and press Enter: v Installing from CD: ./dirinstall -r /directory/response.rsp v Installing from download (version 5.20): ./dir5.20_server_linux.sh -r /directory/response.rsp v Installing from download (version 5.20.1): ./dir5.20.1_server_linux.sh -r /directory/response.rsp where directory is the local directory to which you copied the response file and response.rsp is the name of the response file saved in step 6. 8. Optional: Keep the response file for future use and reference.
182
9. The selections you made in the response file determine what you do next.
Settings DbmsConfigMethod parameter set to GUI; running Linux in a graphical environment. Result and next steps The IBM Director Database Configuration window opens. Go to step 10. Note: If you set the DbmsConfigMethod parameter to GUI but are not running Linux in a graphical environment, you must perform the database configuration after the installation of IBM Director Server is complete. See Configuring the database on Linux or AIX on page 326. The database is configured silently during the installation. Go to step 13 on page 186.
10. Select the database application to use with IBM Director. You have the following options: Apache Derby (Option on all platforms except i5/OS) Creates and configures an embedded Apache Derby database. The Apache Derby application is included in the IBM Director installation. IBM DB2 Universal Database Configures IBM Director to use an IBM DB2 database. IBM DB2 must be installed and configured on a system in your network. Microsoft Data Engine (MSDE) 2000 or Microsoft SQL Server 2000 Configures IBM Director to use an MSDE or Microsoft SQL Server database. MSDE or Microsoft SQL Server must be installed and configured on a system in your network. Oracle Configures IBM Director to use an Oracle database. Oracle Server must be installed and configured on a system in your network. PostgreSQL Configures IBM Director to use a PostgreSQL database. PostgreSQL must be installed and configured on a system in your network Select later (database disabled) IBM Director will be installed without a database. Tasks requiring a database will be absent or not functional. Important: You can configure IBM Director for use with your database application at any point after the installation of IBM Director Server, but you must not start the management server until it is completed. Starting the management server before configuring IBM Director to use a database application might result in a loss of functionality. 11. Click Next to configure IBM Director for use with your database application. Refer to Table 74 on page 184 for application-specific configuration instructions.
183
Table 74. Database configuration If the database application is Apache Derby Complete the applicable steps The IBM Director Apache Derby Configuration window opens. The values cannot be changed. Click Next and go to step 13 on page 186. IBM DB2 The IBM Director DB2 Universal Database Configuration window opens. Complete the following fields: 1. In the DB2 TCP/IP listener port field, type the number of the port that is used by the DB2 TCP/IP listener. 2. In the Server name field, type the name of the server on which DB2 is installed. 3. In the Database name field, type the name of the database. 4. In the User ID field, type a valid DB2 user ID. 5. In the Password field, type the password for the DB2 user ID. Click Next and go to step 13 on page 186. MSDE or Microsoft SQL Server The IBM Director Microsoft SQL Server Database Configuration window opens. Complete the following fields: 1. In the SQL Server TCP/IP listener port field, type the number of the port that is used by the SQL Server TCP/IP listener. 2. In the Server name field, type the name of the server on which SQL Server is installed. 3. In the Database name field, type the name of the database. If it does not exist, it will be created. 4. In the User ID field, type a valid user ID for the SQL Server. 5. In the Password field, type the password for the SQL Server user ID. Click Next and go to step 13 on page 186.
184
Table 74. Database configuration (continued) If the database application is Oracle Server Complete the applicable steps The IBM Director Oracle Database Configuration window opens. Complete the following fields: 1. In the Oracle TCP/IP listener port field, type the number of the port that is used by the Oracle TCP/IP listener. 2. In the Oracle host name field, type the TCP/IP host name of the database server. 3. In the Oracle System Identifier (SID) field, type the Oracle system identifier (SID). 4. In the User ID field, type a valid Oracle user ID. If it does not exist, it is created. By default, this user ID is assigned to the IBM Director table space. 5. In the Password and Confirm password fields, type the password that is associated with the user ID that you typed in step 4. 6. In the Oracle administrator account field, type a valid user ID for the Oracle administrator account. 7. In the Oracle administrator password field, type the password that is associated with the user ID that you typed in step 6. Click Next. A second IBM Director Oracle Database Configuration window opens. Complete the following fields: 1. In the Default tablespace name field, type a table space name. 2. In the Default tablespace data file field, type the name of the table-space data file. If you do not specify the directory path, the table-space data file will be created in the Oracle Server default directory. If you specify a directory path that is not valid, the database configuration will fail. 3. In the Default tablespace size (MB) field, type the size of the table space in MB. 4. In the Temporary tablespace name field, type a name for the temporary table space. 5. In the Temporary tablespace data file field, type the name of the temporary table-space data file. If you do not specify the directory path, the table-space data file will be created in the Oracle Server default directory. If you specify a directory path that is not valid, the database configuration will fail. 6. In the Temporary tablespace size (MB) field, type the size of the temporary table space in MB. Click Next and go to step 13 on page 186.
185
Table 74. Database configuration (continued) If the database application is PostgreSQL Complete the applicable steps The IBM Director PostgreSQL database configuration window opens. Complete the following fields: 1. In the PostgreSQL TCP/IP listener port field, type the number of the port that is used by the PostgreSQL TCP/IP listener. 2. In the Server name field, type the name of the server on which PostgreSQL is installed. 3. In the Database name field, type the name of the database. 4. In the User ID field, type a valid PostgreSQL user ID. 5. In the Password field, type the password for the PostgreSQL user ID. Click Next and go to step 13. Select later (database disabled) IBM Director is installed without a database configured. To configure a database after the installation of IBM Director Server, see Configuring the database on Linux or AIX on page 326. Go to step 13.
12. Optional: Configure IBM Director for use with a database application. For more information, see Configuring the database on Linux or AIX on page 326. Important: You can configure IBM Director for use with your database application at any point after the installation of IBM Director Server, but you must not start the management server until it is completed. Starting the management server before configuring IBM Director to use a database application might result in a loss of function. 13. Optional: By default, encryption using the Advanced Encryption Standard (AES) algorithm is enabled during installation. To disable encryption or change security settings, type the following command and press Enter:
/opt/ibm/director/bin/cfgsecurity
14. To start IBM Director, type the following command and press Enter:
15. Unmount the CD-ROM drive. Perform the following steps to unmount the CD-ROM drive: a. Type cd / and press Enter. b. Type the following command and press Enter:
umount /mnt/cdrom
where mnt/cdrom is the mount point of the drive. 16. Remove the CD from the CD-ROM drive. Related tasks Choosing the IBM Director database application on page 107 Some IBM Director functions require use of an external database, but not all databases support the same functionality with IBM Director. You should choose a supported database that meets the needs of your installation.
186
Preparing the IBM Director database on page 125 Unless you plan to use IBM DB2 for System i or Apache Derby, you must prepare the database application before configuring IBM Director Server to use it. Configuring the database on a Linux or AIX management server using the cfgdb command on page 326 Use the cfgdb command to configure the database after IBM Director Server is installed. Configuring the database on a Linux or AIX management server using the cfgdbcmd command on page 327 Use the cfgdbcmd command to configure the database from a command line after IBM Director Server is installed.
Installing IBM Director Server on Linux for System z

After preparing your system, you can perform a standard installation or you can use a response file to customize the features that are installed. When you install IBM Director Server, IBM Director Console and IBM Director Agent are installed automatically. Depending on your version of IBM Director, you can install from either installation media or from a downloaded installation package. Table 75 lists the sources of installation code.
Table 75. Installation options for IBM Director Server on Linux for System z Version 5.20 5.20 Update 1 Installation media IBM Director for Linux on System z, V5.20 not available Downloaded installation package file name not available dir5.20.1_server-linux-s390.tar
IBM Director for Linux on System z, V5.20 is available as an ISO image from ShopzSeries at www.ibm.com/software/ShopzSeries and from the IBM Director download Web page at www.ibm.com/systems/management/director/ downloads.html. The installation package files are available from the IBM Director download Web page at www.ibm.com/systems/management/director/ downloads.html. Important: v IBM Director Server and IBM Director Console must be at the same release level. For example, if you install IBM Director Server, version 5.20.1 on the management server, you must also install IBM Director Console, version 5.20.1 on any systems that you want to access the management server. v If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server. v If you are planning to install and use a database for IBM Director other than the default database, make sure that you have installed and configured the database application that you will use with IBM Director before installing IBM Director Server. On management servers not running i5/OS, the default database is Apache Derby, but other databases can be used. v On management servers not running i5/OS, IBM Director Server includes all the functionality of IBM Director Agent and IBM Director Console. It is not possible or necessary to separately install either IBM Director Agent or IBM Director
187
Console on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent or IBM Director Console will be performed for systems with IBM Director Server installed. v Before installing IBM Director Server on a system that has IBM Director Console or IBM Director Agent installed, you must first uninstall the existing IBM Director component. Note: The default installation uses a graphical user interface for configuring the IBM Director database. The workstation from which you perform the installation must have an X Window System or Virtual Network Computing (VNC) client if you want to use this graphical user interface. If your workstation does not have an X Window System or Virtual Network Computing (VNC) client, you can use a customized response file to perform the installation without a graphical user interface (see step 9 on page 189). Optional: If you choose to use a database application other than Apache Derby with IBM Director, be sure to perform any necessary preparation steps before configuring IBM Director to use the database. For more information, see Preparing the IBM Director database on page 125. Complete the following steps to install IBM Director Server on Linux for System z: 1. If you install from installation media, make the installation code available to your Linux system. See Preparing to install IBM Director Server on Linux for System z on page 148 for more information. 2. If you install from a downloaded installation package, extract the installation files to a local directory on your Linux system. 3. From a terminal session on your Linux system, change to the directory where the installation script is located. Type the following command and press Enter:
cd /directory/director/server/linux/s390/
where /directory is the mount point of the file system on the CD or the path to the directory to which you have extracted the IBM Director installation files. 4. If you want to customize the installation, go to step 5. If you want to accept the default settings for the installation, type the following command and press Enter:
./dirinstall
Refer to the response file to view the default values. The response file is named dirserv.rsp and is located in the same directory as the installation script. In the response file, 1 indicates that an item is to be installed and 0 indicates that an item is not to be installed. Go to step 10 on page 189. 5. If you want to customize the installation and you install from installation media, copy the response file to a local directory. Type the following command and press Enter:
where directory is the local directory. 6. Open an ASCII text editor and modify the installation settings in the copy of the dirserv.rsp file. This file is fully commented. You can specify the location of the RPM files and select log file options. 7. Save the modified response file with a new file name.
188
8. To install IBM Director Server using the response file, type the following command and press Enter:
where directory is the local directory with your copy of the response file and response.rsp is the name of the response file saved in step 7 on page 188. 9. The selections you made in the response file determine what you do next.
Settings DbmsConfigMethod parameter set to GUI. DbmsConfigMethod parameter set to Rspfile; database configuration information provided. Result and next steps The IBM Director Database Configuration window opens. Go to step 10. The database is configured silently during the installation. Go to step 12 on page 192.
10. Select the database application to use with IBM Director. You have the following options: Apache Derby (Option on all platforms except i5/OS) Creates and configures an embedded Apache Derby database. The Apache Derby application is included in the IBM Director installation. IBM DB2 Universal Database Configures IBM Director to use an IBM DB2 database. IBM DB2 must be installed and configured on a system in your network. Microsoft Data Engine (MSDE) 2000 or Microsoft SQL Server 2000 Configures IBM Director to use an MSDE or Microsoft SQL Server database. MSDE or Microsoft SQL Server must be installed and configured on a system in your network. Oracle Configures IBM Director to use an Oracle database. Oracle Server must be installed and configured on a system in your network. PostgreSQL Configures IBM Director to use a PostgreSQL database. PostgreSQL must be installed and configured on a system in your network Select later (database disabled) IBM Director will be installed without a database. Tasks requiring a database will be absent or not functional. Important: You can configure IBM Director for use with your database application at any point after the installation of IBM Director Server, but you must not start the management server until it is completed. Starting the management server before configuring IBM Director to use a database application might result in a loss of functionality. Click Next to configure the IBM Director database. Refer to Table 76 on page 190 for application-specific configuration instructions.
189
Table 76. Database configuration If the database application is Apache Derby Complete the applicable steps The IBM Director Apache Derby Configuration window opens. The values cannot be changed. Click Next and go to step 12 on page 192. IBM DB2 The IBM Director DB2 Universal Database Configuration window opens. Type information in the following entry fields: 1. In the DB2 TCP/IP listener port field, type the number of the port that is used by the DB2 TCP/IP listener. 2. In the Server name field, type the name of the server on which DB2 is installed. 3. In the Database name field, type the name of the database. 4. In the User ID field, type a valid DB2 user ID. 5. In the Password field, type the password for the DB2 user ID. Click Next and go to step 12 on page 192. MSDE or Microsoft SQL Server The IBM Director Microsoft SQL Server Database Configuration window opens. Type information in the following entry fields: 1. In the SQL Server TCP/IP listener port field, type the number of the port that is used by the SQL Server TCP/IP listener. 2. In the Server name field, type the name of the server on which SQL Server is installed. 3. In the Database name field, type name of the database. If it does not exist, it will be created. 4. In the User ID field, type a valid SQL Server user ID. 5. In the Password field, type the password for the SQL Server user ID. Click Next and go to step 12 on page 192.
190
Table 76. Database configuration (continued) If the database application is Oracle Server Complete the applicable steps The IBM Director Oracle Database Configuration window opens. Type information in the following entry fields: 1. In the Oracle TCP/IP listener port field, type the number of the port that is used by the Oracle TCP/IP listener. 2. In the Oracle host name field, type the TCP/IP host name of the database server. 3. In the Oracle System Identifier (SID) field, type the Oracle system identifier (SID). 4. In the User ID field, type a valid Oracle user ID. If it does not exist, it is created. By default, this user ID is assigned to the IBM Director table space. 5. In the Password and Confirm password fields, type the password that is associated with the user ID that you typed in step 4. 6. In the Oracle administrator account field, type a valid Oracle administrator account user ID. 7. In the Oracle administrator password field, type the password that is associated with the user ID that you typed in step 6. Click Next. A second IBM Director Oracle Database Configuration window opens. Type information in the following entry fields: 1. In the Default tablespace name field, type a table space name. 2. In the Default tablespace data file field, type the name of the table-space data file. If you do not specify the directory path, the table-space data file will be created in the Oracle Server default directory. If you specify a directory path that is not valid, the database configuration will fail. 3. In the Default tablespace size (MB) field, type the size of the table space in MB. 4. In the Temporary tablespace name field, type a name for the temporary table space. 5. In the Temporary tablespace data file field, type the name of the temporary table-space data file. If you do not specify the directory path, the table-space data file will be created in the Oracle Server default directory. If you specify a directory path that is not valid, the database configuration will fail. 6. In the Temporary tablespace size (MB) field, type the size of the temporary table space in MB. Click Next and go to step 12 on page 192.
191
/opt/ibm/director/bin/cfgsecurity
13. To start IBM Director, type the following command and press Enter:
To enable SNMP Access and Trap Forwarding, install and configure Net-SNMP, version 5.2.1. See Enabling SNMP access and trap forwarding for Linux on page 318. For instructions for installing IBM Director Software Distribution (Premium Edition) see Appendix D, Installing Software Distribution Premium Edition on Linux, on page 359. Related tasks Preparing to install IBM Director Server on Linux for System z on page 148 Before installing IBM Director Server on Linux for System z, make sure that your platform meets the applicable requirements. Choosing the IBM Director database application on page 107 Some IBM Director functions require use of an external database, but not all databases support the same functionality with IBM Director. You should choose a supported database that meets the needs of your installation.
192
Preparing the IBM Director database on page 125 Unless you plan to use IBM DB2 for System i or Apache Derby, you must prepare the database application before configuring IBM Director Server to use it. Configuring the database on a Linux or AIX management server using the cfgdb command on page 326 Use the cfgdb command to configure the database after IBM Director Server is installed. Configuring the database on a Linux or AIX management server using the cfgdbcmd command on page 327 Use the cfgdbcmd command to configure the database from a command line after IBM Director Server is installed.
Installing IBM Director Server on Linux on POWER

Install IBM Director Server on Linux by downloading the installation file or using the IBM Director for Linux on POWER CD. You can perform a standard installation or you can use a response file to customize the features that are installed. Important: v IBM Director Server and IBM Director Console must be at the same release level. For example, if you install IBM Director Server, version 5.20.1 on the management server, you must also install IBM Director Console, version 5.20.1 on any systems that you want to access the management server. v If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server. v If you are planning to install and use a database for IBM Director other than the default database, make sure that you have installed and configured the database application that you will use with IBM Director before installing IBM Director Server. On management servers not running i5/OS, the default database is Apache Derby, but other databases can be used. v On management servers not running i5/OS, IBM Director Server includes all the functionality of IBM Director Agent and IBM Director Console. It is not possible or necessary to separately install either IBM Director Agent or IBM Director Console on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent or IBM Director Console will be performed for systems with IBM Director Server installed. v Before installing IBM Director Server on a system that has IBM Director Console or IBM Director Agent installed, you must first uninstall the existing IBM Director component. During the installation process, you can install several IBM Director Server features. Optional: If you choose to use a database application other than Apache Derby with IBM Director, be sure to perform any necessary preparation steps before configuring IBM Director to use the database. For more information, see Preparing the IBM Director database on page 125. Depending on the version of IBM Director Server you are installing, you can install IBM Director Server on Linux on POWER from either installation media or from a downloaded installation package.
193
Table 77. Installation options for IBM Director Server on Linux on POWER
Version 5.20 Installation media IBM Director for Linux on POWER, V5.20 CD IBM Director for Linux on POWER, Version 5.20 Update 1 CD Downloaded installation package file name Dir5.20_LinuxonPower.tar.gz Dir5.20_LinuxonPower.iso 5.20 Update 1 Dir5.20.1_Server_LinuxonPower.tar.gz
1. To install IBM Director Server from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. To unzip and extract the contents of the installation package, type the following command:
cd /directory/director/server/linux/ppc/
d. 2. To a. b.
where directory is the local directory into which you extracted the files. Go to step 3. start the installation from the CD, perform the following steps: Insert the CD into the CD-ROM drive. If the CD does not automount, type the following command and press Enter:
cd /mnt/cdrom/director/server/linux/ppc/
where mnt/cdrom is the mount point of the drive. d. Go to step 3. 3. If you want to customize the installation, go to step 4. If you want to accept the default settings for the installation, type the following command and press Enter:
./dirinstall
By default, the Apache Derby database application is installed and configured to work with IBM Director. Go to step 12 on page 198. 4. To customize the installation, copy the response file (dirserv.rsp) to a local directory. Type the following command and press Enter:
where directory is the local directory.
194
5. Open an ASCII text editor and modify the installation settings in the dirserv.rsp file. This file is fully commented. You can specify the location of the RPM files, select the IBM Director extensions and features that you want to install, configure a database to use with IBM Director, and select log file options. 6. Save the modified response file with a new file name. 7. To install IBM Director Server using the response file, type the following command and press Enter:
where directory is the local directory into which you copied the response file, and response.rsp is the name of the response file saved in step 6. 8. The selections you made in the response file determine what you do next.
Settings DbmsConfigMethod parameter set to GUI; running Linux in a graphical environment. Result and next steps The IBM Director Database Configuration window opens. Go to step 9. Note: If you set the DbmsConfigMethod parameter to GUI but are not running Linux in a graphical environment, you must perform the database configuration after the installation of IBM Director Server is complete. See Configuring the database on Linux or AIX on page 326. The database is configured silently during the installation. Go to step 12 on page 198.
9. Select the database application to use with IBM Director. You have the following options: Apache Derby (Option on all platforms except i5/OS) Creates and configures an embedded Apache Derby database. The Apache Derby application is included in the IBM Director installation. IBM DB2 Universal Database Configures IBM Director to use an IBM DB2 database. IBM DB2 must be installed and configured on a system in your network. Microsoft Data Engine (MSDE) 2000 or Microsoft SQL Server 2000 Configures IBM Director to use an MSDE or Microsoft SQL Server database. MSDE or Microsoft SQL Server must be installed and configured on a system in your network. Oracle Configures IBM Director to use an Oracle database. Oracle Server must be installed and configured on a system in your network. PostgreSQL Configures IBM Director to use a PostgreSQL database. PostgreSQL must be installed and configured on a system in your network
195
Select later (database disabled) IBM Director will be installed without a database. Tasks requiring a database will be absent or not functional. Important: You can configure IBM Director for use with your database application at any point after the installation of IBM Director Server, but you must not start the management server until it is completed. Starting the management server before configuring IBM Director to use a database application might result in a loss of functionality. 10. Click Next to configure IBM Director for use with your database application. Refer to Table 78 for application-specific configuration instructions.
Table 78. Database configuration If the database application is Apache Derby Complete the applicable steps The IBM Director Apache Derby Configuration window opens. The values cannot be changed. Click Next and go to step 12 on page 198. IBM DB2 The IBM Director DB2 Universal Database Configuration window opens. Complete the following fields: 1. In the DB2 TCP/IP listener port field, type the number of the port that is used by the DB2 TCP/IP listener. 2. In the Server name field, type the name of the server on which DB2 is installed. 3. In the Database name field, type the name of the database. 4. In the User ID field, type a valid DB2 user ID. 5. In the Password field, type the password for the DB2 user ID. Click Next and go to step 12 on page 198. MSDE or Microsoft SQL Server The IBM Director Microsoft SQL Server Database Configuration window opens. Complete the following fields: 1. In the SQL Server TCP/IP listener port field, type the number of the port that is used by the SQL Server TCP/IP listener. 2. In the Server name field, type the name of the server on which SQL Server is installed. 3. In the Database name field, type the name of the database. If it does not exist, it will be created. 4. In the User ID field, type a valid user ID for the SQL Server. 5. In the Password field, type the password for the SQL Server user ID. Click Next and go to step 12 on page 198.
196
Table 78. Database configuration (continued) If the database application is Oracle Server Complete the applicable steps The IBM Director Oracle Database Configuration window opens. Complete the following fields: 1. In the Oracle TCP/IP listener port field, type the number of the port that is used by the Oracle TCP/IP listener. 2. In the Oracle host name field, type the TCP/IP host name of the database server. 3. In the Oracle System Identifier (SID) field, type the Oracle system identifier (SID). 4. In the User ID field, type a valid Oracle user ID. If it does not exist, it is created. By default, this user ID is assigned to the IBM Director table space. 5. In the Password and Confirm password fields, type the password that is associated with the user ID that you typed in step 4. 6. In the Oracle administrator account field, type a valid user ID for the Oracle administrator account. 7. In the Oracle administrator password field, type the password that is associated with the user ID that you typed in step 6. Click Next. A second IBM Director Oracle Database Configuration window opens. Complete the following fields: 1. In the Default tablespace name field, type a table space name. 2. In the Default tablespace data file field, type the name of the table-space data file. If you do not specify the directory path, the table-space data file will be created in the Oracle Server default directory. If you specify a directory path that is not valid, the database configuration will fail. 3. In the Default tablespace size (MB) field, type the size of the table space in MB. 4. In the Temporary tablespace name field, type a name for the temporary table space. 5. In the Temporary tablespace data file field, type the name of the temporary table-space data file. If you do not specify the directory path, the table-space data file will be created in the Oracle Server default directory. If you specify a directory path that is not valid, the database configuration will fail. 6. In the Temporary tablespace size (MB) field, type the size of the temporary table space in MB. Click Next and go to step 12 on page 198.
197
where install_root represents the root directory of your IBM Director Server installation. 13. To start IBM Director, type the following command and press Enter:
install_root/bin/twgstart
14. If you used the CD to install IBM Director Server, unmount the drive by completing the following steps: a. Type cd / and press Enter. b. Type the following command and press Enter:
umount /mnt/cdrom
where mnt/cdrom is the mount point of the drive. 15. If you use the CD to install IBM Director Server, remove the IBM Director for Linux on POWER, V5.20 CD from the drive. To configure your database application for use with IBM Director, see Configuring the database on a Linux or AIX management server using the cfgdb command on page 326
198
page 326 or Configuring the database on a Linux or AIX management server using the cfgdbcmd command on page 327. To enable SNMP Access and Trap Forwarding, install and configure Net-SNMP, version 5.2.1, see Enabling SNMP access and trap forwarding for Linux on page 318.
Installing IBM Director Server on Windows

Install IBM Director Server on a system that is running Windows by downloading the installation file or using the IBM Director on x86 CD. You can perform a standard installation by using the InstallShield wizard or you can use a response file to perform a unattended installation. Important: v IBM Director Server and IBM Director Console must be at the same release level. For example, if you install IBM Director Server, version 5.20.1 on the management server, you must also install IBM Director Console, version 5.20.1 on any systems that you want to access the management server. v If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server. v If you are planning to install and use a database for IBM Director other than the default database, make sure that you have installed and configured the database application that you will use with IBM Director before installing IBM Director Server. On management servers not running i5/OS, the default database is Apache Derby, but other databases can be used. v On management servers not running i5/OS, IBM Director Server includes all the functionality of IBM Director Agent and IBM Director Console. It is not possible or necessary to separately install either IBM Director Agent or IBM Director Console on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent or IBM Director Console will be performed for systems with IBM Director Server installed. v Before installing IBM Director Server on a system that has IBM Director Console or IBM Director Agent installed, you must first uninstall the existing IBM Director component. When you install IBM Director Server, the InstallShield wizard automatically installs IBM Director Console and IBM Director Agent. During the installation process, you can install the optional IBM Director features. You also can change security settings. This section provides instructions for installing IBM Director Server using the InstallShield wizard. The wizard can be used in a standard interactive mode, or you can perform an unattended installation using a response file to provide answers to the questions that the wizard poses. Installing IBM Director Server on Windows using the InstallShield wizard: After preparing your System x server for the installation of IBM Director, run the IBM Director Server installation program and choose the features that you want to install. Optional: If you choose to use a database application other than Apache Derby with IBM Director, be sure to perform any necessary preparation steps before
199
configuring IBM Director to use the database. For more information, see Preparing the IBM Director database on page 125. Depending on the version of IBM Director Server you are installing, you can install IBM Director Server on Windows from either installation media or from a downloaded installation package.
Table 79. Installation options for IBM Director Server on Windows
Version 5.20 5.20 Update 1 Installation media IBM Director on x86, V5.20 CD IBM Director on x86, Version 5.20 Update 1 CD Downloaded installation package file name dir5.20_System_x.iso dir5.20.1_server_patch_windows.zip (upgrade only)
Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on the system, it is installed during the IBM Director Server installation. If the upgrade is necessary, the system prompts you to restart following the installation of IBM Director Server without specifying that MSI was installed. Unless you install using the response file and set the RebootIfRequired parameter to N, you are prompted to restart whether or not the IBM Director Server installation is completed successfully. In addition, if you attempt to perform an administrative installation and MSI has not yet been upgraded, you must add the admin parameter when you start the InstallShield Wizard in this procedure. For example, you would type the following command:
\director\server\windows\i386\ibmsetup.exe admin
This parameter updates MSI and runs the installation program in administrative mode. Restart the system if prompted to do so. 1. Using an account with either local or domain administrative privileges, log on to the operating system. 2. 5.20 Update 1 only: To start the installation from a Web download, perform the following steps: Note: IBM Director Server version 5.20 must already be installed. The 5.20.1 package is an upgrade package only. a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. Use the unzip command to extract the contents of the installation package to a temporary directory. c. Click Start Run. d. In the Open field, type the following command and press Enter:
\install_files\FILES\dir5.20.1_server_patch_windows.exe
e. Go to step 8 on page 201. 3. 5.20 only: To start the installation from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. Create an installation CD from the downloaded iso image file. Then, install IBM Director Server from the CD you created, starting at step 4. 4. Insert the CD into the CD-ROM drive.
200
5. If the installation program starts automatically and the IBM Director Setup window opens, go to step 7. Otherwise, click Start Run. 6. In the Open field, type the following command and press Enter:
e:\setup.exe
where e is the drive letter on your system. The installation program starts, and the IBM Director Setup window opens. 7. Click Install IBM Director Server. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard window opens. Accessibility note: Screen readers might not process the IBM Director Setup window correctly. To start the installation wizard for IBM Director Server using the keyboard, perform the following steps: Close the IBM Director Setup window. Open Windows Explorer. Browse to the \director\server\windows\i386 directory on the CD. Run the ibmsetup.exe program. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Server window opens. Continue to step 8. 8. Click Next. The License Agreement window opens. 9. Click I accept the terms in the license agreement; then, click Next. The Installation Type window opens. 10. Click Next. The Feature and Installation Directory Selection window opens. IBM Director Server, Level 2: IBM Director Agent, Level 1: IBM Director Core a. b. c. d.
Figure 6. Installing IBM Director Server on Windows: Feature and Installation Directory Selection window
Services, IBM Director Console, and xSeries Support and tasks are selected
201
automatically for installation; a hard-disk-drive icon
is displayed to the
left of each component. A red X is displayed to the left of each optional feature that is not selected by default. 11. Select the IBM Director Agent features that you want to install: IBM Director Remote Control Agent Enables a system administrator to perform remote desktop functions on the management server. BladeCenter Management Extension Enables a system administrator to manage BladeCenter units. Rack Manager Enables a system administrator to use the Rack Manager task to build a realistic, visual representation of a rack and its components. To select a feature, click the red X to the left of the feature name. A menu opens. To select the feature, click either This feature will be installed on local hard drive or This feature, and all subfeatures, will be installed on local hard drive.
Figure 7. Installing IBM Director Server on Windows: Feature and Installation Directory Selection window
12. Click Next. The IBM Director Service Account Information window opens.
202
Figure 8. Installing IBM Director Server on Windows: IBM Director Service Account Information window
13. Provide information about the IBM Director service account: a. In the Local computer name or domain field, type the computer name of the IBM Director service account. If the service account is a domain account, type the domain. b. In the User name field, type the user ID for the IBM Director service account. c. In the Password and Confirm password fields, type the password for the IBM Director service account. Note: The information must correspond to a Windows account with administrator privileges on the management server. Otherwise, the installation will fail. 14. Click Next. The Encryption Settings window opens.
203
Figure 9. Installing IBM Director Server on Windows: Encryption Settings window
15. By default, the Encrypt data transmissions between IBM Director Server and IBM Director Agent check box is selected and the Advanced Encryption Standard (AES) encryption algorithm is enabled. You can clear the check box to disable encryption or select a different encryption algorithm. 16. Click Next. The Software Distribution Settings window opens. 17. To select an alternative location for the creation of the software-distribution packages, click Change and select another directory. To select an alternative location for software-distribution packages that are received from IBM Director Server are placed, click Change and select another directory. To select an alternative location for saved update packages, click Change and select another directory. 18. Click Next. The Ready to Install the Program window opens. 19. Click Install. The Installing IBM Director Server window opens. The progress of the installation is displayed in the Status field. When the installation is completed, the Network Driver Configuration window opens.
204
Figure 10. Installing IBM Director Server on Windows: Network Driver Configuration window
20. In the System name field, type the name that you want to be displayed in IBM Director Console. By default, this is the NetBIOS name of the management server. 21. Define the communication protocols to use between IBM Director Server and IBM Director Agent. a. In the Network drivers field, the TCPIP (all adapters) setting is enabled by default. To enable another protocol, select the protocol and then select the Enable driver check box. Note: If you disable the TCPIP (all adapters) setting and enable an individual device driver on a system with multiple network adapters, IBM Director Server will receive only those data packets addressed to the individual adapter. b. In the Network timeout field, type the number of seconds that IBM Director Server waits for a response from IBM Director Agent. By default, this value is set to 15 seconds. c. Select the Enable Wake on LAN check box if the network adapter supports the Wake on LAN feature. Note: To determine whether your server supports the Wake on LAN feature, see your server documentation. d. If you chose to install the IBM Director Remote Control Agent, the following options are available:
205
Require user authorization for system access Select this check box to request authorization from the local user before controlling the management server remotely. Disable screen saver Select this check box to disable the screen saver on the management server when it is controlled remotely. Disable background wallpaper Select this check box to disable desktop wallpaper on the management server when it is controlled remotely. You might want to disable the wallpaper because complicated backgrounds slow down remote control and increase network traffic. 22. Click OK. The IBM Director Database Configuration window opens.
Figure 11. Installing IBM Director Server: IBM Director Database Configuration window
23. Click the database application that you want to use with IBM Director. You have the following options: Apache Derby (Option on all platforms except i5/OS) Creates and configures an embedded Apache Derby database. The Apache Derby application is included in the IBM Director installation. IBM DB2 Universal Database Configures IBM Director to use an IBM DB2 database. IBM DB2 must be installed and configured on a system in your network. Microsoft Data Engine (MSDE) 2000 or Microsoft SQL Server 2000 Configures IBM Director to use an MSDE or Microsoft SQL Server database. MSDE or Microsoft SQL Server must be installed and configured on a system in your network.
206
Oracle Configures IBM Director to use an Oracle database. Oracle Server must be installed and configured on a system in your network. Select later (database disabled) IBM Director will be installed without a database. Tasks requiring a database will be absent or not functional. Important: You can configure IBM Director for use with your database application at any point after the installation of IBM Director Server, but you must not start the management server until it is completed. Starting the management server before configuring IBM Director to use a database application might result in a loss of functionality. 24. Click Next and begin configuring the IBM Director database.
If the database application is Apache Derby IBM DB2 Complete the applicable steps The IBM Director Apache Derby Configuration window opens. The values cannot be changed. Click Next and go to step 25 on page 208. The IBM Director DB2 Universal Database Configuration window opens. Complete the following entry fields: 1. In the DB2 TCP/IP listener port field, type the number of the port that is used by the DB2 TCP/IP listener. 2. In the Server name field, type the name of the server on which DB2 is installed. 3. In the Database name field, type the name of the database. 4. In the User ID field, type a valid DB2 user ID. 5. In the Password field, type the password for the DB2 user ID. Click Next. MSDE or Microsoft SQL Server The IBM Director Microsoft SQL Server Database Configuration window opens. Complete the following entry fields: 1. In the SQL Server TCP/IP listener port field, type the number of the port that is used by the SQL Server TCP/IP listener. 2. In the Server name field, type the name of the server on which SQL Server is installed. 3. In the Database name field, type the name of the database. If it does not exist, it will be created. 4. In the User ID field, type a valid SQL Server user ID. 5. In the Password field, type the password for the SQL Server user ID. Click Next.
207
If the database application is Oracle Server
Complete the applicable steps The IBM Director Oracle Database Configuration window opens. Complete the following entry fields: 1. In the Oracle TCP/IP listener port field, type the number of the port that is used by the Oracle TCP/IP listener. 2. In the Oracle host name field, type the TCP/IP host name of the database server. 3. In the Oracle System Identifier (SID) field, type the Oracle system identifier (SID). 4. In the User ID field, type a valid Oracle user ID. If it does not exist, it is created. By default, this user ID is assigned to the IBM Director table space. 5. In the Password and Confirm password fields, type the password that is associated with the user ID that you entered in step 4. 6. In the Oracle administrator account field, type a valid user ID for the Oracle administrator account. 7. In the Oracle administrator password field, type the password that is associated with the user ID that you entered in step 6. Click Next. A second IBM Director Oracle Database Configuration window opens. Complete the following entry fields: 1. In the Default tablespace name field, type a table space name. 2. In the Default tablespace data file field, type the name of the table space data file. If you do not specify the directory path, the table space data file will be created in the Oracle Server default directory. If you specify a directory path that is not valid, the database configuration will fail. 3. In the Default tablespace size (MB) field, type the size of the table space in MB. 4. In the Temporary tablespace name field, type a name for the temporary table space. 5. In the Temporary tablespace data file field, type the name of the temporary table space data file. If you do not specify the directory path, the table space data file will be created in the Oracle Server default directory. If you specify a directory path that is not valid, the database configuration will fail. 6. In the Temporary tablespace size (MB) field, type the size of the temporary table space in MB. Click Next.
Select later (database Go to step 25 disabled)
25. Click Finish. A window opens, asking you if you want to restart the server. 26. Remove the CD from the CD-ROM drive. 27. Click Yes to restart the server. Performing an unattended installation of IBM Director Server on Windows:
208
After preparing your System x server for the installation of IBM Director, you can perform an unattended installation of IBM Director Server by using a response file. This method creates a standard installation file that can be used on many systems. Optional: If you choose to use a database application other than Apache Derby with IBM Director, be sure to perform any necessary preparation steps before configuring IBM Director to use the database. For more information, see Preparing the IBM Director database on page 125. When you perform an unattended installation of IBM Director Server, the response file provides answers to the questions that are posed by the InstallShield wizard. Important: The response file for IBM Director Server contains entries for a User ID and Password to use with the IBM Director service account. The User ID and Password must correspond to a Windows account with administrator privileges. If you choose to include this information in the response file, be sure to delete the file after the installation is complete to avoid security issues. Depending on the version of IBM Director Server you are installing, you can install IBM Director Server on Windows from either installation media or from a downloaded installation package.
Table 80. Installation options for IBM Director Server on Windows
Version 5.20 5.20 Update 1 Installation media IBM Director on x86, V5.20 CD IBM Director on x86, Version 5.20 Update 1 CD Downloaded installation package file name dir5.20_System_x.iso dir5.20.1_server_patch_windows.zip (upgrade only)
Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on the system, it is installed during the IBM Director Server installation. If the upgrade is necessary, the system prompts you to restart following the installation of IBM Director Server without specifying that MSI was installed. Unless you install using the response file and set the RebootIfRequired parameter to N, you are prompted to restart whether or not the IBM Director Server installation is completed successfully. Note: You cannot perform an unattended upgrade to version 5.20 Update 1. Complete the following steps to install IBM Director Server: 1. Insert the IBM Director on x86, V5.20 CD into the drive. 2. Copy the dirserv.rsp file to a local directory. This file is in the director\server\windows\i386 directory on the IBM Director on x86, V5.20 CD. 3. Open the copy of the dirserv.rsp file in an ASCII text editor. 4. Modify and save the response file with a new file name. This file follows the Windows initialization (INI) file format and is fully commented. 5. Open a command prompt and change to the directory that contains the IBM Director Server installation file (ibmsetup.exe). This file is in the director\server\windows\i386 directory on the IBM Director on x86, V5.20 CD. 6. From the command prompt, type the following command and press Enter:
ibmsetup.exe installationtype rsp="responsefile.rsp" option
where:
209
v installationtype is one of the following commands: unattended shows the progress of the installation but does not require any user input. silent suppresses all output to the screen during installation. v responsefile.rsp is the path and name of the response file that you created in step 4 on page 209. v option is one of the following optional parameters:
Table 81. Optional installation parameters Parameter waitforme debug What it does Ensures that ibmsetup.exe process will not end until the installation of IBM Director Server is completed Logs all messages that are sent by the Microsoft Windows Installer log engine, including status and information messages Specifies the fully qualified name of an alternative log file Enables verbose logging
log=logfilename verbose
7. If you set the RebootIfRequired parameter to Y in the response file, reboot the system if prompted to do so. 8. When the installation is completed, remove the CD from the drive.
Installing IBM Director Console

IBM Director Console can be installed only on supported systems that are running supported operating systems. Use these procedures to install IBM Director Console . IBM Director Console cannot be installed on a system that is running i5/OS. To access an IBM Director Server that is installed on an i5/OS server, you must use an IBM Director Console that is installed on another operating system. Note: IBM Director Server and IBM Director Console must be at the same release level. Also, if IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server.
Installing IBM Director Console on AIX

To install IBM Director Console on a system that is running AIX, download the installation files from theIBM Director Web site or use the CD. You can perform a standard installation or you can use a response file to customize the installation for your environment. Important: v On management servers not running i5/OS, it is not possible or necessary to separately install either IBM Director Agent or IBM Director Console on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent or IBM Director Console will be performed for systems with IBM Director Server installed. v IBM Director Server and IBM Director Console must be at the same release level. For example, if you install IBM Director Server, version 5.20.1 on the management server, you must also install IBM Director Console, version 5.20.1 on any systems that you want to access the management server.
210
Depending on the version of IBM Director Console you are installing, you can install IBM Director Console on AIX from either installation media or from a downloaded installation package.
Table 82. Installation options for IBM Director Console on AIX
Version 5.20 Installation media IBM Director for AIX 5L, V5.20 CD IBM Director Agents & Consoles, V5.20 (2 of 2) 5.20 Update 1 IBM Director for AIX 5L, Version 5.20 Update 1 CD Dir5.20.1_Agent_Console_AIX.tar.gz Downloaded installation package file name Dir5.20_AIX.tar.gz
1. To install IBM Director Console from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. To unzip and extract the contents of the installation package, type the following command:
where install_package is the file name of the downloaded installation package. c. Go to step 3. 2. To install IBM Director Console from the CD, perform the following steps: a. Insert the CD into the CD-ROM drive. b. If the CD does not automount, type the following command and press Enter:
where dev/cd0 is the specific device file for the block device and mnt is the mount point of the drive. c. To change to the directory where IBM Director Console is located, type the following command and press Enter:
cd /mnt/director/console/aix
where mnt is the mount point of the drive. d. Go to step 3. 3. If you want to customize the installation, go to step 4. If you want to accept the default settings for the installation, type the following command and press Enter:
./dirinstall
Go to step 8 on page 212. 4. To customize the installation, copy the response file (dircon.rsp) to a local directory. Type the following command and press Enter:
cp dircon.rsp /directory/
where directory is the local directory. 5. Open an ASCII text editor and modify the installation settings in the copy of the dircon.rsp file. This file is fully commented. You can specify the location of the .bff files and select log file options.
211
6. Save the modified response file with a new file name. 7. To install IBM Director Console using the response file, type the following command and press Enter:
where directory is the local directory to which you copied the response file, and response.rsp is the name of the response file saved in step 6. Go to step 8. 8. To start IBM Director Console, type the following command and press Enter:
/opt/ibm/director/bin/twgcon
9. If you installed IBM Director Console from the CD, unmount the drive. Type the following command and press Enter:
umount /mnt
where mnt is the mount point of the drive. Remove the CD from the drive.
Installing IBM Director Console on Linux for System x

To install IBM Director Console on a system that is running Linux for System x, download the installation files from theIBM Director support Web site or use the CD. You can perform a standard installation or you can use a response file to customize the installation for your environment. Important: v On management servers not running i5/OS, it is not possible or necessary to separately install either IBM Director Agent or IBM Director Console on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent or IBM Director Console will be performed for systems with IBM Director Server installed. v IBM Director Server and IBM Director Console must be at the same release level. For example, if you install IBM Director Server, version 5.20.1 on the management server, you must also install IBM Director Console, version 5.20.1 on any systems that you want to access the management server. Depending on the version of IBM Director Console you are installing, you can install IBM Director Console on Linux for System x from either installation media or from a downloaded installation package.
Table 83. Installation options for IBM Director Console on Linux for System x
Version 5.20 Installation media IBM Director on x86, V5.20 CD or IBM Director Agents & Consoles, V5.20 (2 of 2) CD IBM Director on x86, Version 5.20 Update 1 CD Downloaded installation package file name dir5.20_console_linux.tar
5.20 Update 1
dir5.20.1_console_linux.tar
1. To install IBM Director Console from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. To extract the contents of the installation package, type the following command:
212
cd /install_files/
where install_files is the path to the extracted installation files. d. Optional: To customize the installation, copy the response file (dircon.rsp) to a local directory and modify the installation settings in your local copy. Type the following command and press Enter:
where directory is a local directory. Then, open an ASCII text editor and modify the installation settings in the dircon.rsp file. This file is fully commented. You can specify the location of the RPM files and select log file options. Then, save the modified response file. e. To install IBM Director Console, type one of the following commands and press Enter: v To accept the default settings (version 5.20): ./dir5.20_console_linux.sh v To accept the default settings (version 5.20.1): ./dir5.20.1_console_linux.sh v To use the response file (version 5.20): ./dir5.20_console_linux.sh -r /directory/response.rsp v To use the response file (version 5.20.1): ./dir5.20.1_console_linux.sh -r /directory/response.rsp where directory is the local directory to which you copied the response file, and response.rsp is the name of the response file. 2. To install IBM Director Console from the CD, perform the following steps: a. Insert the CD into the CD-ROM drive. b. If the CD does not automount, mount the CD-ROM drive. Type the following command and press Enter:
cd /mnt/cdrom/director/console/linux/i386
where mnt/cdrom is the mount point of the drive. d. Optional: To customize the installation, copy the response file (dircon.rsp) to a local directory and modify the installation settings in your local copy. Type the following command and press Enter:
where directory is a local directory.
213
Then, open an ASCII text editor and modify the installation settings in the dircon.rsp file. This file is fully commented. You can specify the location of the RPM files and select log file options. Then, save the modified response file. e. To install IBM Director Console, type one of the following commands and press Enter: v To accept the default settings: ./dirinstall v To use the response file: ./dirinstall -r /directory/responsefile.rsp where directory is the local directory to which you copied the response file and responsefile.rsp is the name of the modified response file. f. Unmount the CD-ROM drive. Perform the following steps to unmount the CD-ROM drive: 1) Type cd / and press Enter. 2) Type the following command and press Enter:
umount /mnt/cdrom
where mnt/cdrom is the mount point of the drive. g. Remove the CD from the CD-ROM drive.
Installing IBM Director Console on Linux for System z

After preparing your system, you can perform a standard installation or you can use a response file to customize the installation for your environment. Depending on your version of IBM Director, you can install from either installation media or from a downloaded installation package. Table 84 lists the sources of installation code.
Table 84. Installation options for IBM Director Console on Linux for System z Version 5.20 Installation media IBM Director for Linux on System z, V5.20 IBM Director Agents & Consoles, V5.20 (2 of 2) not available Downloaded installation package file name not available
5.20 Update 1
dir5.20.1_console-linux-s390.tar
IBM Director for Linux on System z, V5.20 is available as an ISO image from ShopzSeries at www.ibm.com/software/ShopzSeries and from the IBM Director download Web page at www.ibm.com/systems/management/director/ downloads.html. IBM Director Agents & Consoles, V5.20 (2 of 2) is available as an ISO image from ShopzSeries at www.ibm.com/software/ShopzSeries. The installation package files are available from the IBM Director download Web page at www.ibm.com/systems/management/director/downloads.html. Complete the following steps to install IBM Director Console on Linux for System z: 1. If you install from installation media, make the installation code available to your Linux system. 2. If you install from a downloaded installation package, extract the installation files to a local directory on your Linux system.
214
3. From a terminal session on your Linux system, change to the directory in which the installation script is located. Type the following command and press Enter:
cd /mnt/director/console/linux/s390/
where /mnt is the mount point of the file system on the CD or the path to the directory to which you have extracted the IBM Director installation files. 4. If you want to customize the installation, go to step 5. If you want to accept the default settings for the installation, type the following command and press Enter:
./dirinstall
Refer to the response file to view the default values. The response file is named dircon.rsp and is located in the same directory as the installation script. In the response file, 1 indicates that an item is to be installed and 0 indicates that an item is not to be installed. Go to step 10. 5. If you want to customize the installation and you install from installation media, copy the response file to a local directory. Type the following command and press Enter:
cp dircon.rsp /directory
where directory is the local directory. 6. Open an ASCII text editor and modify the installation settings in the copy of the dircon.rsp file. This file is fully commented. You can specify the location of the RPM files and select log file options. 7. Save the modified response file with a new file name. 8. To install IBM Director Console, type the following command and press Enter:
where directory is the local directory with your copy of the response file and response.rsp is the name of the response file saved in step 7. 9. Optional: Keep the response file for future use and reference. 10. To start IBM Director Console start a new terminal session, type the following command and press Enter:
/opt/ibm/director/bin/twgcon
Installing IBM Director Console on Linux on POWER

To install IBM Director Console on a system that is running Linux on POWER, download the installation files from the IBM Director support Web site or use the CD. You can perform a standard installation or you can use a response file to customize the installation for your environment. Depending on the version of IBM Director Console you are installing, you can install IBM Director Console on Linux on POWER from either installation media or from a downloaded installation package.
Table 85. Installation options for IBM Director Console on Linux on POWER
Version 5.20 Installation media IBM Director for Linux on POWER, V5.20 CD IBM Director Agents & Consoles, V5.20 (2 of 2) CD 5.20 Update 1 IBM Director for Linux on POWER, Version 5.20 Update 1 CD Dir5.20.1_Agent_Console_LinuxonPower.tar.gz Downloaded installation package file name Dir5.20_LinuxonPower.tar.gz Dir5.20_LinuxonPower.iso
215
1. To install IBM Director Console from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. To unzip and extract the contents of the installation package, type the following command:
cd /directory/director/console/linux/ppc
d. 2. To a. b.
where directory is the local directory into which you extracted the files. Go to step 3. install IBM Director Console from the CD, perform the following steps: Insert the CD into the CD-ROM drive. If the CD does not automount, type the following command and press Enter:
cd /mnt/cdrom/director/console/linux/ppc
where mnt/cdrom is the mount point of the drive. d. Go to step 3. 3. If you want to customize the installation, go to step 4. If you want to accept the default settings for the installation, type the following command and press Enter:
./dirinstall
Go to step 8 on page 217. 4. To customize the installation, copy the response file (dircon.rsp) to a local directory. Type the following command and press Enter:
cp dircon.rsp /directory
where directory is the local directory. 5. Open an ASCII text editor and modify the installation settings in the copy of the dircon.rsp file. This file is fully commented. You can specify the location of the RPM files, optional items that you want to install, and select log file options. 6. Save the modified response file with a new name. 7. To install IBM Director Console using the modified response file, type the following command and press Enter:
./dirinstall -r /directory/responsefile.rsp
216
where directory is the local directory to which you copied the response file and responsefile.rsp is the name of the modified response file saved in step 6 on page 216. 8. If you installed IBM Director Console from the CD, unmount the drive by completing the following steps: a. Type cd / and press Enter. b. Type the following command and press Enter:
umount /mnt/cdrom
where mnt/cdrom is the mount point of the drive. 9. Remove the CD from the drive.
Installing IBM Director Console on Windows

You can use the InstallShield wizard to install IBM Director Console on any Windows system from which you want to remotely access IBM Director Server. The wizard can be used in a standard interactive mode, or you can perform an unattended installation using a response file to provide answers to the questions that the wizard poses. Installing IBM Director Console using the InstallShield wizard: To install IBM Director Console on a system that is running Windows, download the installation files from theIBM Director support Web site or use the CD. Depending on the version of IBM Director Console you are installing, you can install IBM Director Console on Windows from either installation media or from a downloaded installation package.
Table 86. Installation options for IBM Director Console on Windows
Version 5.20 Installation media IBM Director on x86, V5.20 CD or IBM Director Agents & Consoles, V5.20 (2 of 2) IBM Director on x86, Version 5.20 Update 1 CD Downloaded installation package file name dir5.20_console_windows.zip
5.20 Update 1
dir5.20.1_console_windows.zip (full install) or dir5.20.1_console_patch_windows.zip (upgrade only)
Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on the system, it is installed during the IBM Director Console installation. If the upgrade is necessary, the system prompts you to restart following the installation of IBM Director Console without specifying that MSI was installed. Unless you install using the response file and set the RebootIfRequired parameter to N, you are prompted to restart regardless of whether the IBM Director Console installation is completed successfully. In addition, if you attempt to perform an administrative installation and MSI has not yet been upgraded, you must add the admin parameter when you start the InstallShield Wizard in this procedure. For example, you would type the following command:
\director\console\windows\i386\ibmsetup.exe admin
This parameter updates MSI and runs the installation program in administrative mode. Restart the system if prompted to do so.
217
1. To start the installation from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. Use the unzip command to extract the contents of the installation package to a temporary directory. c. Click Start Run. d. 5.20 only: 1) In the Open field, type the following command and press Enter:
\install_files\dir5.20_console_windows.exe
where install_files is the path to the extracted installation files. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Console window opens. 2) Go to step 4 on page 219. e. 5.20.1 only (full install): 1) In the Open field, type the following command and press Enter:
\install_files\dir5.20.1_console_windows.exe
where install_files is the path to the extracted installation files. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Console window opens. 2) Go to step 4 on page 219. f. 5.20.1 only (upgrade): 1) In the Open field, type the following command and press Enter:
\install_files\FILES\dir5.20.1_console_patch_windows.exe
where install_files is the path to the extracted installation files. The InstallShield wizard starts, and the IBM Director Console Patch InstallShield Wizard window opens. 2) Click Update. The installation progress is displayed. 3) Go to step 10 on page 219. 2. Optional: (i5/OS only) To start the installation from the IBM Director Agents & Consoles (2 of 2)CD, insert the CD into the drive. Browse to the director\console\windows\i386 directory and double-click ibmsetup.exe. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Console window opens. Continue to step 4 on page 219. 3. To start the installation from the CD, perform the following steps: a. Insert the CD into the CD-ROM drive. b. If the installation program starts automatically and the IBM Director Setup window opens, go to step 3d. Otherwise, click Start Run. c. In the Open field, type the following command and press Enter:
e:\setup.exe
where e is the drive letter of the drive. The installation program starts, and the IBM Director Setup window opens. d. Click Install IBM Director Console. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Console window opens. Continue to step 4 on page 219.
218
Accessibility note: Screen readers might not process the IBM Director Setup window correctly. To start the installation wizard for IBM Director Console using the keyboard, perform the following steps: a. Close the IBM Director Setup window. b. Open Windows Explorer. c. Browse to the director/console/windows/i386 directory on the IBM Director on x86 CD. d. Run the ibmsetup.exe program. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Console window opens. Continue to step 4. 4. Click Next. The License Agreement window opens. 5. Click I accept the terms in the license agreement; then, click Next. The Feature and Installation Directory Selection window opens. IBM Director Console and the System x Management Extension are selected automatically for installation; a hard-disk-drive icon is displayed to the left of each component. A red X is displayed to the left of each of the optional features, BladeCenter Management Extension and Rack Manager. 6. To select BladeCenter Management Extension, a feature that manages and monitors BladeCenter systems, click the red X to the left of the feature name. A menu opens. Click either This feature will be installed on local hard drive or This feature, and all subfeatures, will be installed on local hard drive. 7. To select Rack Manager, which you can use to build a realistic, visual representation of a rack and its components, click the red X to the left of the feature name. A menu opens. Click either This feature will be installed on local hard drive or This feature, and all subfeatures, will be installed on local hard drive. 8. Click Next. The Ready to Install the Program window opens. 9. Click Install. The Installing IBM Director Console window opens. The status bar displays the progress of the installation. When the installation is completed, the InstallShield Wizard Completed window opens. 10. Click Finish. Performing an unattended installation of IBM Director Console on Windows: You can perform an unattended installation of IBM Director Console on a Windows system by using a response file, which provides answers to the questions that are posed by the InstallShield wizard. You can use this method to create a standard installation file that can be employed on many systems. Depending on the version of IBM Director Console you are installing, you can install IBM Director Console on Windows from either installation media or from a downloaded installation package.
Table 87. Installation options for IBM Director Console on Windows
Version 5.20 Installation media IBM Director on x86, V5.20 CD or IBM Director Agents & Consoles, V5.20 (2 of 2) Downloaded installation package file name dir5.20_console_windows.zip
219
Table 87. Installation options for IBM Director Console on Windows (continued)
Version 5.20 Update 1 Installation media IBM Director on x86, Version 5.20 Update 1 CD Downloaded installation package file name dir5.20.1_console_windows.zip (full install) or dir5.20.1_console_patch_windows.zip (upgrade only)
Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on the system, it is installed during the IBM Director Console installation. If the upgrade is necessary, the system prompts you to restart following the installation of IBM Director Console without specifying that MSI was installed. Unless you install using the response file and set the RebootIfRequired parameter to N, you are prompted to restart regardless of whether the IBM Director Console installation is completed successfully. To install IBM Director Console, complete the following steps: 1. To start the installation from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. Use the unzip command to extract the contents of the installation package to a temporary directory. c. Locate and copy the dircon.rsp file. d. Go to step 6. 2. Insert the CD into the CD-ROM drive. 3. If the installation program starts automatically and the IBM Director Setup window opens, close it. 4. Copy the \director\console\windows\i386\dircon.rsp file to a local directory. 5. Go to step 6. 6. Open the copy of the dircon.rsp file in an ASCII text editor. 7. Modify and save the dircon.rsp file with a new file name. This file follows the Windows initialization (INI) file format and is fully commented. 8. Open a command prompt and change to the directory that contains the IBM Director Console installation file (ibmsetup.exe). This file is in the \director\console\windows\i386 directory on the CD. 9. From the command prompt, type the following command and press Enter:
ibmsetup.exe installationtype rsp="responsefile.rsp" option
where: v installationtype is one of the following commands: unattended shows the progress of the installation but does not require any user input. silent suppresses all output to the screen during installation. v responsefile.rsp is the path and name of the response file that you saved in step 7.
220
v option is one of the following optional parameters:

Table 88. Optional installation parameters Parameter waitforme debug What it does Ensures that ibmsetup.exe process will not end until the installation of IBM Director Console is completed Logs all messages that are sent by the Microsoft Windows Installer log engine, including status and information messages Specifies the fully qualified name of an alternative log file Enables verbose logging
10. If you installed IBM Director Console from the CD, remove the CD from the drive when the installation is completed.
Installing Level 1: IBM Director Core Services

Install Level 1: IBM Director Core Services on a managed system for IBM Director to communicate with and administer the managed system.
Installing Level 1: IBM Director Core Services on Linux for System x

To install IBM Director Core Services on a system that is running Linux for System x, download the installation files from the IBM Director support Web site or use the CD. You can perform a standard installation or you can use a response file to customize the installation for your environment. Depending on the version of IBM Director Core Services you are installing, you can install IBM Director Core Services on Linux for System x from either installation media or from a downloaded installation package.
Table 89. Installation options for IBM Director Core Services on Linux for System x
Version 5.20 Installation media IBM Director on x86, V5.20 CD or IBM Director Agents & Consoles, V5.20 (2 of 2) CD IBM Director on x86, Version 5.20 Update 1 CD Downloaded installation package file name dir5.20_coreservices_linux.tar
5.20 Update 1
dir5.20.1_coreservices_linux.tar
1. To start the installation from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. To extract the contents of the installation package, type the following command:
cd /install_files/FILES
where install_files is the path to the extracted installation files. d. If you want to customize the installation, go to step 3 on page 222.
221
If you want to accept the default settings for the installation, go to step 4. 2. To start the installation from the CD, perform the following steps: a. Insert the CD into the CD-ROM drive. b. If the CD does not automount, mount the CD-ROM drive. Type the following command and press Enter:
cd /mnt/cdrom/coresvcs/agent/linux/i386/FILES
where mnt/cdrom is the mount point of the drive. d. If you want to customize the installation, go to step 3. If you want to accept the default settings for the installation, go to step 4. 3. Optional: To customize the installation, copy the response file (coresvcs.rsp) to a local directory and modify the installation settings in your local copy. a. Type the following command and press Enter:
cp coresvcs.rsp /directory/
where directory is a local directory. b. Open an ASCII text editor and modify the installation settings in the copy of the coresvcs.rsp file. This file is fully commented. You can specify the location of the RPM files and select log file options. c. Save the modified response file. 4. To install IBM Director Core Services, type one of the following commands and press Enter: v To accept the default settings (version 5.20): ./dir5.20_coreservices_linux.sh v To accept the default settings (version 5.20.1): ./dir5.20.1_coreservices_linux.sh v To use the response file (version 5.20): ./dir5.20_coreservices_linux.sh -r /directory/response.rsp v To use the response file (version 5.20.1): ./dir5.20.1_coreservices_linux.sh -r /directory/response.rsp where directory is the local directory to which you copied the response file, and response.rsp is the name of the response file. If you are installing from the CD, go to step 5. If you are installing from a Web download, the installation is completed. 5. Unmount the CD-ROM drive. Perform the following steps to unmount the CD-ROM drive: a. Type cd / and press Enter. b. Type the following command and press Enter:
umount /mnt/cdrom
where mnt/cdrom is the mount point of the drive. 6. Remove the CD from the CD-ROM drive.
222
After IBM Director Core Services is installed, you can enable the Wake on LAN feature. To enable SNMP Access and Trap Forwarding, you must install and configure Net-SNMP, version 5.2.1. See Enabling SNMP access and trap forwarding for Linux in the IBM Director Systems Management Guide for more information.
Installing Level 1: IBM Director Core Services on Linux for System z

After preparing your system, you can install Level 1: IBM Director Core Services on a Linux for System z platform. You can perform a standard installation or you can use a response file to customize the features that are installed. Depending on your version of IBM Director, you can install from either installation media or from a downloaded installation package. Table 90 lists the sources of installation code.
Table 90. Installation options for IBM Director Core Services on Linux for System z Version 5.20 Installation media IBM Director for Linux on System z, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) not available Downloaded installation package file name not available
5.20 Update 1
dir5.20.1_coreservices-agent-linuxs390.tar
IBM Director for Linux on System z, V5.20 is available as an ISO image from ShopzSeries at www.ibm.com/software/ShopzSeries and from the IBM Director download Web page at www.ibm.com/systems/management/director/ downloads.html. IBM Director Agents & Consoles, V5.20 (1 of 2) is available as an ISO image from ShopzSeries at www.ibm.com/software/ShopzSeries. The installation package files are available from the IBM Director download Web page at www.ibm.com/systems/management/director/downloads.html. To install Level 1: IBM Director Core Services on Linux for System z, complete the following steps: 1. If you install from installation media, make the installation code available to your Linux system. 2. If you install from a downloaded installation package, extract the installation files to a local directory on your Linux system. 3. From a terminal session on your Linux system, change to the directory in which the installation script is located. Type the following command and press Enter:
cd /mnt/coresvcs/agent/linux/s390/FILES/
where /mnt is the mount point of the file system on the CD or path to the directory to which you have extracted the IBM Director installation files. 4. If you want to customize the installation, go to step 5 on page 224. If you want to accept the default settings for the installation, type the following command and press Enter:
./csversion_agent_linz.sh
223
csversion is a prefix cs followed by the product version number. For version 5.20.1, the file name would be cs5.20.1_agent_linz.sh. Refer to the response file to view the default values. The response file is named coresvcs.rsp and is located in the same directory as the installation script. In the response file, 1 indicates that an item is to be installed and 0 indicates that an item is not to be installed. This step completes the default installation. 5. If you want to customize the installation and you install from installation media, copy the response file to a local directory. Type the following command and press Enter:
cp coresvcs.rsp /directory
where directory is the local directory. 6. Open an ASCII text editor and modify the installation settings in the copy of the coresvcs.rsp file. This file is fully commented. 7. Save the modified response file with a new file name. 8. To install IBM Director Core Services using the response file, type the following command and press Enter:
./csversion_agent_linz.sh -r /directory/response.rsp
where directory is the local directory with your copy of the response file and response.rsp is the name of the response file saved in step 7. 9. Optional: Keep the response file for future use and reference. To enable SNMP Access and Trap Forwarding, you must install and configure Net-SNMP. Use the version included in your distribution.
Installing Level 1: IBM Director Core Services on Linux on POWER

To install IBM Director Core Services on a system that is running Linux on POWER, download the installation files from the IBM Director support Web site or use the CD. You can perform a standard installation or you can use a response file to customize the installation for your environment. Depending on the version of IBM Director Core Services you are installing, you can install IBM Director Core Services on Linux on POWER from either installation media or from a downloaded installation package.
Table 91. Installation options for IBM Director Core Services on Linux on POWER
1. To install IBM Director Core Services from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/.
224
b. To unzip and extract the contents of the installation package, type the following command:
cd /directory/coresvcs/agent/linux/ppc/FILES
d. 2. To a. b.
where directory is the local directory into which you extracted the files. Go to step 3. start the installation from the CD, perform the following steps: Insert the CD into the CD-ROM drive. If the CD does not automount, type the following command and press Enter:
cd /mnt/cdrom/coresvcs/agent/linux/ppc/FILES
where mnt/cdrom is the mount point of the drive. d. Go to step 3. 3. If you want to customize the installation, go to step 4. If you want to accept the default settings for the installation, type one of the following commands and press Enter: v 5.20 only: ./cs5.20_agent_linppc.sh v 5.20 Update 1 only: ./cs5.20.1_agent_linppc.sh Go to step 8. 4. To customize the installation, copy the response file (coresvcs.rsp) to a local directory. Type the following command and press Enter:
cp coresvcs.rsp /directory/
where directory is the local directory. 5. Open an ASCII text editor and modify the installation settings in the copy of the coresvcs.rsp file. This file is fully commented. You can specify the location of the RPM files and select log file options. 6. Save the modified response file with a new file name. 7. To install IBM Director Core Services using the response file, type one of the following commands and press Enter: v 5.20 only: ./cs5.20_agent_linppc.sh -r /directory/response.rsp v 5.20 Update 1 only: ./cs5.20.1_agent_linppc.sh -r /directory/ response.rsp where directory is the local directory to which you copied the response file, and response.rsp is the name of the response file saved in step 6. 8. If you used a CD to install IBM Director Core Services, unmount the media drive by completing the following steps:
225
a. Type cd / and press Enter. b. Type the following command and press Enter:
umount /mnt/cdrom
where mnt/cdrom is the mount point of the media drive. 9. If you used a CD to install IBM Director Core Services, remove the CD from the drive. To enable SNMP Access and Trap Forwarding, you must install and configure Net-SNMP, version 5.2.1.
Installing Level 1: IBM Director Core Services on Windows

To install Level 1: IBM Director Core Services on a system that is running Windows, download the installation files from the IBM Director support Web site or use the CD. You can perform a standard installation or you can use a response file to customize the installation for your environment. Installing Level 1: IBM Director Core Services on Windows using the InstallShield wizard: To use the InstallShield wizard to install IBM Director Core Services on a system that is runningWindows, download the installation files from theIBM Director support Web site or use the CD. Depending on the version of IBM Director Core Services you are installing, you can install IBM Director Core Services on Windows from either installation media or from a downloaded installation package.
Table 92. Installation options for IBM Director Core Services on Windows
Version 5.20 Installation media IBM Director on x86, V5.20 CD IBM Director Agents & Consoles, V5.20 (1 of 2) CD 5.20 Update 1 IBM Director on x86, Version 5.20 Update 1 CD Downloaded installation package file name dir5.20_coreservices_windows.zip dir5.20_System_x.iso dir5.20.1_coreservices_windows.zip
Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on the system, it is installed during the IBM Director Core Services installation. If the upgrade is necessary, the system prompts you to restart following the installation of IBM Director Core Services without specifying that MSI was installed. Unless you install using the response file and set the RebootIfRequired parameter to N, you are prompted to restart whether or not the IBM Director Core Services installation is completed successfully. In addition, if you attempt to perform an administrative installation and MSI has not yet been upgraded, you must add the -a admin parameter when you start the InstallShield Wizard in this procedure. For example, to start the InstallShield Wizard for version 5.20, you would type the following command:
dir5.20_coreservices_windows.exe -a admin
This parameter updates MSI and runs the installation program in administrative mode. Restart the system if prompted to do so. 1. To start the installation from a Web download, perform the following steps:
226
a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. Use the unzip command to extract the contents of the installation package to a temporary directory. c. Click Start Run. d. In the Open field, type one of the following commands and press Enter: v 5.20 only: \directory\FILES\dir5.20_coreservices_windows.exe v 5.20 Update 1 only: \directory\FILES\ dir5.20.1_coreservices_windows.exe where directory is the local directory into which you extracted the files. The Welcome to the InstallShield Wizard for IBM Director Core Services window opens. e. Go to step 4 on page 228. 2. To start the installation from the IBM Director Agents & Consoles (1 of 2) CD, perform the following steps: a. Insert the CD into the CD-ROM drive. b. Click Start Run. c. In the Open field, type one of the following commands and press Enter: v 5.20 only: \coresvcs\agent\windows\i386\FILES\ dir5.20_coreservices_windows.exe v 5.20 Update 1 only: \coresvcs\agent\windows\i386\FILES\ dir5.20.1_coreservices_windows.exe The Welcome to the InstallShield Wizard for IBM Director Core Services window opens. d. Go to step 4 on page 228. 3. To start the installation from the IBM Director on x86 CD, perform the following steps: a. Insert the CD into the CD-ROM drive. b. If the installation program starts automatically and the IBM Director Setup window opens, go to step 3d. Otherwise, click Start Run. c. In the Open field, type the following command and press Enter:
e:\setup.exe
where e is the drive letter of the drive. The installation program starts, and the IBM Director Setup window opens. d. Click Install IBM Director Core Services. The Welcome to the InstallShield Wizard for IBM Director Core Services window opens. e. Go to step 4 on page 228. Accessibility note: Screen readers might not process the IBM Director Setup window correctly. To start the installation wizard for IBM Director Core Services using the keyboard, perform the following steps: a. Close the IBM Director Setup window. b. Open Windows Explorer. c. Browse to the \coresvcs\agent\windows\i386\FILES directory on the IBM Director on x86 CD. d. Run one of the following programs: v 5.20 only: dir5.20_coreservices_windows.exe
227
v 5.20 Update 1 only: dir5.20.1_coreservices_windows.exe The Welcome to the InstallShield Wizard for IBM Director Core Services window opens. e. Go to step 4. 4. Click Next. The License Agreement window opens. 5. Click I accept the terms in the license agreement and click Next. The Destination Folder window opens. To select an alternative location for the installation of IBM Director Core Services, click Change and select another directory. 6. Click Next. The Ready to Install the Program window opens. 7. Click Install. The status bar displays the progress of the installation. When the installation is completed, the InstallShield Wizard Completed window opens. 8. Click Finish. 9. If you installed IBM Director Core Services from the CD, remove the CD from the drive. Performing an unattended installation of Level 1: IBM Director Core Services on Windows: You can perform an unattended installation of IBM Director Core Services using a response file, which provides answers to the questions that are posed by the InstallShield wizard. You can use this method to create a standard installation file that can be used on many systems. Depending on the version of IBM Director Core Services you are installing, you can install IBM Director Core Services on Windows from either installation media or from a downloaded installation package.
Table 93. Installation options for IBM Director Core Services on Windows
Version 5.20 Installation media IBM Director on x86, V5.20 CD IBM Director Agents & Consoles, V5.20 (1 of 2) CD 5.20 Update 1 IBM Director on x86, Version 5.20 Update 1 CD Downloaded installation package file name dir5.20_coreservices_windows.zip dir5.20_System_x.iso dir5.20.1_coreservices_windows.zip
Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on the system, it is installed during the IBM Director Core Services installation. If the upgrade is necessary, the system prompts you to restart following the installation of IBM Director Core Services without specifying that MSI was installed. Unless you install using the response file and set the RebootIfRequired parameter to N, you are prompted to restart whether or not the IBM Director Core Services installation is completed successfully. 1. To start the installation from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. Use the unzip command to extract the contents of the installation package to a temporary directory. c. Copy the response file (\directory\FILES\coresvcs.rsp) to a new location, where directory is the local directory into which you extracted the files.
228
d. 2. To a. b.
Go to step 3. start the installation from a CD, perform the following steps: Insert the CD into the CD-ROM drive. If the installation program starts automatically and the IBM Director Setup window opens, close it. c. Copy the response file (\coreservices\agent\windows\i386\FILES\ coresvcs.rsp) to a local directory. d. Go to step 3.
3. Open the copy of the coresvcs.rsp file in an ASCII text editor. 4. Modify and save the response file with a new file name. This file follows the Windows INI file format and is fully commented. 5. Click Start Run. 6. In the Open field, type one of the following commands (all on one line) and press Enter: v 5.20 only:
\directory\FILES\dir5.20_coreservices_windows.exe /s /a installationtype rsp="responsefile.rsp" option
v 5.20 Update 1 only:

\directory\FILES\dir5.20.1_coreservices_windows.exe /s /a installationtype rsp="responsefile.rsp" option
where: v directory is either the local directory into which you extracted the files from a web download, or the following path on the CD media: \coresvcs\agent\windows\i386\. v /s is an optional parameter that suppresses all file extraction windows. v installationtype is one of the following commands: unattended shows the progress of the installation but does not require any user input. silent suppresses all output to the screen during installation. v responsefile.rsp is the path and name of the response file that you created in step 4. v option is one of the following optional parameters:
Table 94. Optional installation parameters Optional parameter waitforme debug What it does Ensures that installation process will not end until the installation of IBM Director Core Services is completed. Logs all messages that are sent by the Microsoft Windows Installer log engine, including status and information messages. Specifies the fully qualified name of an alternative log file. Enables verbose logging.
7. If you set the RebootIfRequired parameter to Y in the response file, reboot the system if prompted to do so. 8. If you installed IBM Director Core Services from the CD, remove the CD from the drive.
229
Installing IBM Director Core Services using the Software Distribution task
You can use the IBM Director Software Distribution task to install IBM Director Core Services on managed systems running Windows or Linux. Note: The file names listed below are English XML files. Files for other supported languages are appended with the appropriate language identifier. For example, dir5.20_coreservices_linux_de.xml is the German XML file. The following files describe IBM Director Core Services:
Table 95. Source and file names of descriptor files used to install IBM Director Core Services using Software Distribution Version CD or downloaded installation package Path and file name of the software distribution package descriptor
IBM Director Core Services on Linux for System x 5.20 IBM Director on x86, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) dir5.20_coreservices_linux.tar 5.20.1 IBM Director on x86, Version 5.20 Update 1 dir5.20.1_coreservices_linux.tar IBM Director Core Services on Linux on POWER 5.20 IBM Director for Linux on POWER, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) Dir5.20_LinuxonPower.tar.gz 5.20.1 IBM Director for Linux on POWER, Version 5.20 Update 1 Dir5.20.1_Agent_Console_LinuxonPower.tar.gz IBM Director Core Services on Linux for System z 5.20 IBM Director for Linux on System z, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) 5.20.1 dir5.20.1_coreservices-agent-linux-s390.tar /coresvcs/agent/linux/s390/META-INF/ cs5.20_agent_linz.xml /coresvcs/agent/linux/s390/META-INF/ cs5.20.1_agent_linz.xml /coresvcs/agent/linux/ppc/META-INF/ cs5.20.1_agent_linppc.xml /coresvcs/agent/linux/ppc/META-INF/ cs5.20_agent_linppc.xml coresvcs/agent/linux/i386/META-INF/ dir5.20_coreservices_linux.xml /META-INF/dir5.20_coreservices_linux.xml /coresvcs/agent/linux/i386/META-INF/ dir5.20.1_coreservices_linux.xml /META-INF/dir5.20.1_coreservices_linux.xml
IBM Director Core Services on Windows 5.20 IBM Director on x86, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) dir5.20_coreservices_windows.zip 5.20.1 IBM Director on x86, Version 5.20 Update 1 dir5.20.1_coreservices_windows.zip \coresvcs\agent\windows\i386\META-INF\ dir5.20_coreservices_windows.xml \META-INF\dir5.20_coreservices_windows.xml \coresvcs\agent\windows\i386\META-INF\ dir5.20.1_coreservices_windows.xml \META-INF\dir5.20.1_coreservices_windows.xml
IBM Director Core Services and OpenSSH on Windows for System x Note: If a managed system does not have a Secure Shell (SSH) package installed, IBM Director Server cannot communicate securely with the managed system. You can download OpenSSH for Windows from www.sourceforge.net/projects/sshwindows/ and use software distribution to distribute the package to the managed system.
230
Table 95. Source and file names of descriptor files used to install IBM Director Core Services using Software Distribution (continued) Version 5.20 5.20.1 CD or downloaded installation package IBM Director on x86, V5.20 IBM Director on x86, Version 5.20 Update 1 Path and file name of the software distribution package descriptor coresvcs\dir5.20_coreservices-toc_windows.xml \coresvcs\dir5.20.1_coreservices-toc_windows.xml
LM78 and SMBus device drivers for Linux on System x Notes: v To install the IBM LM78 or SMBus device driver using the Software Distribution task, you first must build the binary RPM file and copy it to the same directory as the software distribution package descriptor file. v See Preparing to manage service processors with IBM Director and Installing IBM LM78 and SMBus device drivers for Linux for information about these drivers. 5.20 dir5.20_lm78_linux.tar.gz dir5.20_smbus_linux.tar.gz 5.20.1 dir5.20.1_lm78_linux.tar.gz dir5.20.1_smbus_linux.tar.gz lm78driver_linux.xml smbdriver_linux.xml lm78driver_linux.xml smbdriver_linux.xml
Related tasks Preparing to install IBM Director Core Services on Windows on page 166 Before installing IBM Director Core Services on a managed system running Windows, make sure that your system meets all the applicable requirements. Preparing to manage service processors with IBM Director on page 135 You can use IBM Director to manage supported service processors that are installed in a managed system. Related reference Installing IBM LM78 and SMBus device drivers for Linux on page 144 If you plan to install IBM Director Server on a System x or xSeries server running Linux, you might need to install either or both the LM78 and SMBus device drivers for Linux. These device drivers ensure that certain IBM Director tasks and functions work correctly. Creating a software package: You can create a software package for installing or upgrading IBM Director Agent or installing IBM Director Core Services. To create a software package, complete the following steps: 1. Locate the installation or upgrade packages for IBM Director. See the IBM Director Planning, Installation and Configuration Guide for more information. 2. If you want to accept the default settings for the installation, go to step 3. Otherwise, copy the response file: use diragent.rsp for IBM Director Agent, or use coresvcs.rsp for IBM Director Core Services. Open the copy in an ASCII text editor and modify the response file as needed. Save the modified file with a new file name. 3. Start IBM Director Console. 4. In the Tasks pane, double-click Software Distribution. The Software Distribution Manager window opens.
231
Figure 12. Creating a software package: Software Distribution Manager window (Standard Edition)
Figure 13. Creating a software package: Software Distribution Manager window (Premium Edition)
5. If you have not installed IBM Director 5.20 Software Distribution Premium Edition, go to step 6. Otherwise, expand the Wizards tree. 6. Double-click IBM Update Assistant. The IBM Update Assistant window opens. 7. If you want to get files from the management server, click Get files from the Director server. By default, Get files from the local system is selected. 8. To select a file, click Browse. The IBM Update Package/Root Directory Location window opens. 9. Locate the appropriate XML file and click it. The name of the XML file is displayed in the File Name field. Note: Use the correct XML file for your language. The correct file for English installations is the one without the language code, for example, dir5.20_agent_windows.xml. 10. Click OK. The IBM Update Assistant window reopens. 11. Click Next. The second IBM Update Assistant window opens. 12. To specify an alternative response file, click Browse and locate the file that you modified in step 2 on page 231.
232
Note: If you do not specify an alternative response file, the package is installed with the default settings that are specified in the installation script. 13. Click Finish. As the package is processed, a status message is displayed at the bottom of the window. When the processing is completed, the software-distribution package is displayed in the Tasks pane of IBM Director Console. Installing a software package: After you create a software package, you can use the Software Distribution task to remotely install the package on supported systems. To use the Software Distribution task to install a software package, complete the following steps: 1. Start IBM Director Console. 2. In the Tasks pane, expand the Software Distribution task. 3. Click the software package that you want to distribute. Then, drag it into the Group Contents pane and drop it onto the icon that is displayed for the system on which you want to install the software package. A window opens. Note: To distribute software to several systems at once, you can drag the software package into the Groups pane and drop it onto the icon for the group. Alternatively, you can select multiple managed systems in the Group Contents pane. 4. When prompted with Do you wish to create a scheduled job for this task or execute immediately?, click Schedule or Execute Now. If you click Execute Now, the software package is distributed immediately. If you click Schedule, the New Scheduled Job window opens. 5. Schedule the job: a. In the Scheduled Job field, type a unique name for the job. This name is displayed in the Jobs pane of the Scheduler window. b. In the Date field, type the day you want the software package to be installed (in MM/DD/YYYY format). c. In the Time field, type the time you want the software package to be installed. For more information about the Scheduler task, see the IBM Director Systems Management Guide. 6. Click OK. The Save Job Confirmation window opens. 7. Click OK.
Installing Level 2: IBM Director Agent

After preparing your managed system, you can install IBM Director Agent. Important: v IBM Director Server includes all the functionality of IBM Director Agent. It is not possible or necessary to separately install IBM Director Agent on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent will be performed for systems with IBM Director Server installed. v The version of IBM Director Agent cannot be later than the version of IBM Director Server running on the management system.
233
v If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server.
Installing Level 2: IBM Director Agent on AIX

To install IBM Director Agent on a system that is running AIX, download the installation files from the IBM Director support Web site or use the CD. You can perform a standard installation or you can use a response file to customize the installation for your organization. Important: v IBM Director Server includes all the functionality of IBM Director Agent. It is not possible or necessary to separately install IBM Director Agent on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent will be performed for systems with IBM Director Server installed. v The version of IBM Director Agent cannot be later than the version of IBM Director Server running on the management system. v If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server. Depending on the version of IBM Director Agent you are installing, you can install IBM Director Agent on AIX from either installation media or from a downloaded installation package.
Table 96. Installation options for IBM Director Agent on AIX
Version 5.20 5.20 Update 1 Installation media IBM Director for AIX 5L, V5.20 CD IBM Director for AIX 5L, Version 5.20 Update 1 CD Downloaded installation package file name Dir5.20_AIX.tar.gz Dir5.20.1_Agent_Console_AIX.tar.gz Dir5.20.1_AIX.iso
1. To install IBM Director Agent from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. To unzip and extract the contents of the installation package, type the following command:
c. 2. To a. b.
where install_package is the file name of the downloaded installation package. Go to step 3 on page 235. start the installation from the CD, perform the following steps: Insert the CD into the CD-ROM drive. If the CD does not automount, type the following command and press Enter:
where dev/cd0 is the specific device file for the block device and mnt is the mount point of the drive.
234
c. Change to the directory in which the installation script is located. Type the following command and press Enter:
cd /mnt/director/agent/aix/FILES
where mnt is the mount point of the drive. d. Go to step 3. 3. If you want to customize the installation, go to step 4. If you want to accept the default settings for the installation, type one of the following commands and press Enter: v 5.20 only: ./dir5.20_agent_aix.sh v 5.20 Update 1 only: dir5.20.1_agent_aix.sh Go to step 8. 4. To customize the installation, copy the response file (diragent.rsp) to a local directory. Type the following command and press Enter:
cp diragent.rsp /directory
where directory is the local directory. 5. Open an ASCII text editor and modify the installation settings in the copy of the diragent.rsp file. This file is fully commented. You can specify the location of the .bff files and select log file options. 6. Save the modified response file with a new file name. 7. To install IBM Director Agent using the response file, type the following command and press Enter:
./dir5.20_agent_aix.sh -r /directory/response.rsp
where directory is the local directory to which you copied the response file, and response.rsp is the name of the response file saved in step 6. 8. Optional: By default, encryption using the Advanced Encryption Standard (AES) algorithm is enabled during installation. To disable encryption or change security settings, type the following command and press Enter:
where install_root is the root directory of your IBM Director installation. 9. To startIBM Director Agent, type the following command and press Enter:
10. If you installed IBM Director Agent from the CD, type the following command and press Enter to unmount the drive:
umount /mnt
where mnt is the mount point of the drive. Remove the CD from the drive. After IBM Director Agent is installed, you can enable the Wake on LAN feature. To determine if your server supports this feature, review the server documentation.
Installing Level 2: IBM Director Agent on i5/OS

After preparing your system, you can install Level 2: IBM Director Agent on a system that is running i5/OS (V5R3 or later) by downloading the installation files from the IBM Director Web site or using the CD. You can use the Restore Licensed Program (RSTLICPGM) command to perform the installation. If you are upgrading from a previous version of IBM Director Agent, migration of the product will be processed during the RSTLICPGM processing.
235
Depending on the version of IBM Director Agent you are installing, you can install IBM Director Agent on i5/OS from either installation media or from a downloaded installation package.
Table 97. Installation options for IBM Director Agent on i5/OS
Version 5.20 5.20 Update 1 Installation media IBM Director for i5/OS, V5.20 not available Downloaded installation package file name dir5.20_agent_i5OS.zip dir5.20.1_agent_i5OS.zip
Installing Level 2: IBM Director Agent on i5/OS using installation media: If the version of IBM Director Agent you are installing is available on installation media for i5/OS, use these instructions to install IBM Director Agent on i5/OS. Important: v IBM Director Server includes all the functionality of IBM Director Agent. It is not possible or necessary to separately install IBM Director Agent on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent will be performed for systems with IBM Director Server installed. v The version of IBM Director Agent cannot be later than the version of IBM Director Server running on the management system. v If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server. If you are upgrading from a previous version of IBM Director Agent, migration of the product will be processed during the RSTLICPGM processing. To install IBM Director Agent using RSTLICPGM, complete the following steps: 1. Log on to the System i platform by using a profile with the following privileges: *ALLOBJ and *SECADM. 2. Insert the CD into the CD-ROM drive. 3. Run RSTLICPGM. 4. In the Product field, type the product number for IBM Director Agent (5722DA1). 5. In the Device field, type the optical device identifier, for example, opt01. 6. Press Enter. The installation progress for IBM Director Agent is displayed. Installing Level 2: IBM Director Agent on i5/OS using a downloaded installation package: If the version of IBM Director Agent you are installing is available to be downloaded for i5/OS, use these instructions to install IBM Director Agent on i5/OS. Important: v IBM Director Server includes all the functionality of IBM Director Agent. It is not possible or necessary to separately install IBM Director Agent on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent will be performed for systems with IBM Director Server installed.
236
v The version of IBM Director Agent cannot be later than the version of IBM Director Server running on the management system. v If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server. If you are upgrading from a previous version of IBM Director Agent, migration of the product will be processed during the RSTLICPGM processing. To install IBM Director Agent using RSTLICPGM, complete the following steps: 1. On a system that can connect to the i5/OS system, download the installation package from the IBM Director Web site at www.ibm.com/systems/ management/director/. 2. Extract the contents of the installation package into a local directory. 3. 4. Log on to the System i platform by using a profile with the following privileges: *ALLOBJ and *SECADM. 5. On the i5/OS system, type the following command and press Enter to create a save file for the SAVDR100MM.sav file:
CRTSAVF FILE(QGPL/SAVDR100MM)
6. From the directory into which you extracted the contents of the downloaded installation package, start an FTP session to the i5/OS system and then type the following commands, pressing Enter after each:
binary put FILES/SAVDR100MM.sav /qsys.lib/qgpl.lib/SAVDR100MM.file
7. Stop IBM Director Agent by typing the following command from a command prompt and pressing Enter:
QSH CMD(/qibm/userdata/director/bin/twgend)
8. Verify that IBM Director Agent has been stopped by typing the following command from a command prompt and pressing Enter:
9. On the i5/OS system, type the following command and press Enter to install the upgrade:
RSTLICPGM LICPGM(5722DR1) DEV(*SAVF) SAVF(QGPL/SAVDR100MM)
10. Restart IBM Director Agent by typing the following command from a command prompt and pressing Enter:
QSH CMD(/qibm/userdata/director/bin/twgstart)
11. Verify that IBM Director Agent has been restarted by typing the following command from a command prompt and pressing Enter:
12. To delete the SAVDR100MM.sav file, type the following command and press Enter:
DLTF FILE(QGPL/SAVDR100MM)
13. Log on to the System i platform by using a profile with the following privileges: *ALLOBJ and *SECADM. 14. Insert the CD into the CD-ROM drive. 15. Run RSTLICPGM. 16. In the Product field, type the product number for IBM Director Agent (5722DA1). 17. In the Device field, type the optical device identifier, for example, opt01.
237
18. Press Enter. The installation progress for IBM Director Agent is displayed.
Installing Level 2: IBM Director Agent on Linux for System x

After preparing your system, you can install Level 2:IBM Director Agent on a Linux for System x platform by downloading the installation file or using the CD. You can perform a standard installation or you can use a response file to customize the features that are installed. Important: v IBM Director Server includes all the functionality of IBM Director Agent. It is not possible or necessary to separately install IBM Director Agent on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent will be performed for systems with IBM Director Server installed. v The version of IBM Director Agent cannot be later than the version of IBM Director Server running on the management system. v If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server. Depending on the version of IBM Director Agent you are installing, you can install IBM Director Agent on Linux for System x from either installation media or from a downloaded installation package.
Table 98. Installation options for IBM Director Agent on Linux for System x
Version 5.20 Installation media IBM Director on x86, V5.20 CD or IBM Director Agents & Consoles, V5.20 (1 of 2) CD IBM Director on x86, Version 5.20 Update 1 CD Downloaded installation package file name dir5.20_agent_linux.tar
5.20 Update 1
dir5.20.1_agent_linux.tar
1. To start the installation from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. To extract the contents of the installation package, type the following command:
cd /install_files/FILES
d.
2. To a. b.
where install_files is the path to the extracted installation files. If you want to customize the installation, go to step 3 on page 239. If you want to accept the default settings for the installation, go to step 4 on page 239. start the installation from the CD, perform the following steps: Insert the CD into the CD-ROM drive. If the CD does not automount, mount the CD-ROM drive. Type the following command and press Enter:
238
cd /mnt/cdrom/director/agent/linux/i386/FILES
where mnt/cdrom is the mount point of the drive. d. If you want to customize the installation, go to step 3. If you want to accept the default settings for the installation, go to step 4. 3. Optional: To customize the installation, copy the response file (diragent.rsp) to a local directory and modify the installation settings in your local copy. a. Type the following command and press Enter:
cp cdiragent.rsp /directory/
where directory is a local directory. b. Open an ASCII text editor and modify the installation settings in the copy of the diragent.rsp file. This file is fully commented. You can specify the location of the RPM files and select log file options. c. Save the modified response file. 4. To install IBM Director Agent, type one of the following commands and press Enter: v To accept the default settings (version 5.20): ./dir5.20_agent_linux.sh v To accept the default settings (version 5.20.1): ./dir5.20.1_agent_linux.sh v To use the response file (version 5.20): ./dir5.20_agent_linux.sh -r /directory/response.rsp v To use the response file (version 5.20.1): ./dir5.20.1_agent_linux.sh -r /directory/response.rsp where directory is the local directory to which you copied the response file, and response.rsp is the name of the response file. If you are installing from the CD, go to step 5. If you are installing from a Web download, go to step 7. 5. Unmount the CD-ROM drive. Perform the following steps to unmount the CD-ROM drive: a. Type cd / and press Enter. b. Type the following command and press Enter:
umount /mnt/cdrom
where mnt/cdrom is the mount point of the drive. 6. Remove the CD from the CD-ROM drive. 7. Optional: By default, encryption using the Advanced Encryption Standard (AES) algorithm is enabled during installation. To disable encryption or change security settings, type the following command and press Enter:
where install_root is the root directory of your IBM Director installation. 8. To start IBM Director Agent, type the following command and press Enter:
239
After IBM Director Agent is installed, you can enable the Wake on LAN feature. To enable SNMP Access and Trap Forwarding, you must install and configure Net-SNMP, version 5.2.1.
Installing Level 2: IBM Director Agent on Linux for System z

After preparing your system, you can install Level 2: IBM Director Agent on a Linux for System z platform. You can perform a standard installation or you can use a response file to customize the features that are installed. Depending on your version of IBM Director, you can install from either installation media or from a downloaded installation package. Table 99 lists the sources of installation code.
Table 99. Installation options for IBM Director Agent on Linux for System z Version 5.20 Installation media IBM Director for Linux on System z, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) not available Downloaded installation package file name not available
5.20 Update 1
dir5.20.1_agent-linux-s390.tar
IBM Director for Linux on System z, V5.20 is available as an ISO image from ShopzSeries at www.ibm.com/software/ShopzSeries and from the IBM Director download Web page at www.ibm.com/systems/management/director/ downloads.html. IBM Director Agents & Consoles, V5.20 (1 of 2) is available as an ISO image from ShopzSeries at www.ibm.com/software/ShopzSeries. The installation package files are available from the IBM Director download Web page at www.ibm.com/systems/management/director/downloads.html. Important: v IBM Director Server includes all the functionality of IBM Director Agent. It is not possible or necessary to separately install IBM Director Agent on the management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent will be performed for systems with IBM Director Server installed. v The version of IBM Director Agent cannot be later than the version of IBM Director Server running on the management system. v If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server. To enable SNMP Access and Trap Forwarding, you must install and configure Net-SNMP. Use the version that is included in your distribution. To install IBM Director Agent on Linux for System z, complete the following steps: 1. If you install from installation media, make the installation code available to your Linux system. 2. If you install from a downloaded installation package, extract the installation files to a local directory on your Linux system.
240
3. From a terminal session on your Linux system, change to the directory in which the installation script is located. Type the following command and press Enter:
cd /mnt/director/agent/linux/s390/FILES/
where /mnt is the mount point of the file system on the CD or the path to the directory to which you have extracted the IBM Director installation files. 4. If you want to customize the installation, go to step 5. If you want to accept the default settings for the installation, type the following command and press Enter:
./dirversion_agent_linz.sh
dirversion is a prefix dir followed by the product version number. For version 5.20.1, the file name would be dir5.20.1_agent_linz.sh. Refer to the response file to view the default values. The response file is named diragent.rsp and is located in the same directory as the installation script. In the response file, 1 indicates that an item is to be installed and 0 indicates that an item is not to be installed. Go to step 10. 5. If you want to customize the installation and you install from installation media, copy the response file to a local directory. Type the following command and press Enter:
where directory is the local directory. 6. Open an ASCII text editor and modify the installation settings in the copy of the diragent.rsp file. This file is fully commented. You can specify the location of the RPM files and select log file options. 7. Save the modified response file with a new file name. 8. To install IBM Director Agent using the response file, type the following command and press Enter:
./dirversion_agent_linz.sh -r /directory/response.rsp
where directory is the local directory with your copy of the response file and response.rsp is the name of the response file saved in step 7. 9. Optional: By default, encryption using the Advanced Encryption Standard (AES) algorithm is enabled during installation. To disable encryption or change security settings, type the following command and press Enter:
where install_root is the root directory of your IBM Director installation. 10. To start IBM Director Agent, begin a new terminal session, type the following command, and press Enter:
Installing Level 2: IBM Director Agent on Linux for POWER

After preparing your system, you can install Level 2:IBM Director Agent on Linux on POWER by downloading the installation file or using the CD. You can perform a standard installation or you can use a response file to customize the features that are installed. Important: v IBM Director Server includes all the functionality of IBM Director Agent. It is not possible or necessary to separately install IBM Director Agent on the
241
management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent will be performed for systems with IBM Director Server installed. v The version of IBM Director Agent cannot be later than the version of IBM Director Server running on the management system. v If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server. Depending on the version of IBM Director Agent you are installing, you can install IBM Director Agent on Linux on POWER from either installation media or from a downloaded installation package.
Table 100. Installation options for IBM Director Agent on Linux on POWER
1. To install IBM Director Agent from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. To unzip and extract the contents of the installation package, type the following command:
cd /directory/director/agent/linux/ppc/FILES
d. 2. To a. b.
where directory is the local directory into which you extracted the files. Go to step 3 on page 243. start the installation from the CD, perform the following steps: Insert the CD into the CD-ROM drive. If the CD does not automount, type the following command and press Enter:
cd /mnt/cdrom/director/agent/linux/ppc/FILES
where mnt/cdrom is the mount point of the drive. d. Go to step 3 on page 243.
242
3. If you want to customize the installation, go to step 4. If you want to accept the default settings for the installation, type one of the following commands and press Enter: v 5.20 only: ./dir5.20_agent_linppc.sh v 5.20 Update 1 only: ./dir5.20.1_agent_linppc.sh Go to step 8. 4. To customize the installation, copy the response file (diragent.rsp) to a local directory. Type the following command and press Enter:
where directory is the local directory. 5. Open an ASCII text editor and modify the installation settings in the copy of the diragent.rsp file. This file is fully commented. You can specify the location of the RPM files and select log file options. 6. Save the modified response file with a new file name. 7. To install IBM Director Agent using the response file, type one of the following commands and press Enter: v 5.20 only: ./dir5.20_agent_linppc.sh -r /directory/response.rsp v 5.20 Update 1 only: ./dir5.20.1_agent_linppc.sh -r /directory/ response.rsp where directory is the local directory to which you copied the response file, and response.rsp is the name of the response file saved in step 6. 8. Optional: By default, encryption using the Advanced Encryption Standard (AES) algorithm is enabled during installation. To disable encryption or change security settings, type the following command and press Enter:
where install_root is the root directory of your IBM Director installation. 9. To start IBM Director Agent, type the following command and press Enter:
10. If you installed IBM Director Agent from the CD, perform the following steps to unmount the drive: a. Type cd / and press Enter. b. Type the following command and press Enter:
umount /mnt/cdrom
where mnt/cdrom is the mount point of the drive. Remove the CD from the drive. After IBM Director Agent is installed, you can enable the Wake on LAN feature.
Installing Level 2: IBM Director Agent on Linux for Intel Itanium (64 bit)
After preparing your system, you can install Level 2:IBM Director Agent on a Linux for Intel Itanium (64 bit) platform by downloading the installation file or using the CD. You can perform a standard installation or you can use a response file to customize the features that are installed. IBM Director 5.20 support for systems running Linux for Intel Itanium (64 bit) is provided by IBM Director Agent version 5.10.3. There is no IBM Director Agent
243
version 5.20 for Intel Itanium systems. To install Level 2: IBM Director Agent on system running Linux for Intel Itanium (64 bit), complete the following steps: 1. Download the dir5.10.3_agent_linux64.tar package from the IBM Director Web site at www.ibm.com/systems/management/director/. 2. Extract the dir5.10.3_agent_linux64.tar file into a local directory. 3. If you want to customize the installation, go to step 4. If you want to accept the default settings for the installation, type the following command and press Enter:
./dir5.10.3_agent_linux64.sh
Go to step 8. 4. To customize the installation, copy the response file (diragent.rsp) to a local directory. Type the following command and press Enter:
where directory is the local directory. 5. Open an ASCII text editor and modify the installation settings in the copy of the diragent.rsp file. This file is fully commented. You can specify the location of the RPM files and select log file options. 6. Save the modified response file with a new file name. 7. To install IBM Director Agent using the response file, type the following command and press Enter:
./dir5.10.3_agent_linux64.sh -r /directory/response.rsp
where directory is the local directory to which you copied the response file, and response.rsp is the name of the response file saved in step 6. 8. To start IBM Director Agent, type the following command and press Enter:
where install_root is the root directory of your IBM Director installation. After IBM Director Agent is installed, you can enable the Wake on LAN feature. To enable SNMP Access and Trap Forwarding, you must install and configure Net-SNMP, version 5.2.1.
Installing Level 2: IBM Director Agent on NetWare

After preparing your system, you can install Level 2:IBM Director Agent on a NetWare system by downloading the installation file from a Windows workstation running the NetWare Client for Windows. Notes: 1. (System x servers only) Install the MPA Agent only if the server has one of the following service processors installed: v Advanced System Management processor v Advanced System Management PCI adapter v Remote Supervisor Adapter v Remote Supervisor Adapter II 2. To install Level 2: IBM Director Agent, you must log on to the NetWare server from a Windows workstation running the NetWare Client for Windows. The SYS volume must be mapped as a drive to the system running Windows. Also, you must have administrator or supervisor access on the NetWare server.
244
To install Level 2: IBM Director Agent on NetWare, complete the following steps: 1. Download the dir5.20_agent_netware.zip from the IBM Director Support Web site at www.ibm.com/systems/management/director/. 2. Extract the contents of the dir5.20_agent_netware.zip file to the Windows workstation running NetWare Client for Windows. 3. Start Windows Explorer and open the \directory\FILES directory, where directory is the location into which you extracted the contents of the dir5.20_agent_netware.zip file. 4. Double-click the dir5.20_agent_netware.exe file. The InstallShield wizard starts. 5. Click Next. The Installing IBM Director Agent window opens. 6. Click Next to accept the license agreement. The Choose Destination Location window opens. 7. Click the drive that is mapped to the SYS volume on the server running NetWare; then, click Next. The Select Components window opens. IBM Director Agent is selected automatically for installation. 8. Optional: The Management Processor Assistant Agent enables communication with service processors in IBM System x servers. To enable the Management Processor Assistant Agent feature, select the check box. 9. Click Next. The Setup Status window opens, and Level 2: IBM Director Agent installation begins. When the installation is completed, the InstallShield Wizard Complete window opens. 10. Click Finish. 11. On the server running NetWare, change to the console screen. 12. From the console, type the following command and press Enter:
Search add sys:IBM\Director
13. To define the protocols to use for communication between IBM Director Server and IBM Director Agent, type the following command and press Enter:
twgipccf
Note: If you disable the TCPIP (all adapters) setting and enable an individual device driver on a system with multiple network adapters, IBM Director Agent will receive only those data packets that are addressed to the individual adapter. 14. To start IBM Director Agent, type the following command and press Enter:
load twgipc
IBM Director Agent will start automatically whenever the server running NetWare starts.
Installing Level 2:IBM Director Agent on 32-bit Windows

After preparing your system, you can install Level 2:IBM Director Agent on a 32-bit Windows system by downloading the installation file or using the CD. The wizard can be used in a standard interactive mode, or you can perform an unattended installation using a response file to provide answers to the questions that the wizard poses. Important: v IBM Director Server includes all the functionality of IBM Director Agent. It is not possible or necessary to separately install IBM Director Agent on the
245
management server after installing IBM Director Server. Any IBM Director tasks requiring IBM Director Agent will be performed for systems with IBM Director Server installed. v The version of IBM Director Agent cannot be later than the version of IBM Director Server running on the management system. v If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server. Installing Level 2: IBM Director Agent on 32-bit Windows using the InstallShield wizard: After preparing your 32-bit Windows system, you can use the InstallShield wizard to install IBM Director Agent. Depending on the version of IBM Director Agent you are installing, you can install IBM Director Agent on Windows from either installation media or from a downloaded installation package.
Table 101. Installation options for IBM Director Agent on Windows
Version 5.20 Installation media IBM Director on x86, V5.20 CD IBM Director Agents & Consoles, V5.20 (1 of 2) CD 5.20 Update 1 IBM Director on x86, Version 5.20 Update 1 CD Downloaded installation package file name dir5.20_agent_windows.zip dir5.20_System_x.iso dir5.20.1_agent_windows.zip
Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on the system, it is installed during the IBM Director Agent installation. If the upgrade is necessary, the system prompts you to restart following the installation of IBM Director Agent without specifying that MSI was installed. Unless you install using the response file and set the RebootIfRequired parameter to N, you are prompted to restart whether or not the IBM Director Agent installation is completed successfully. In addition, if you attempt to perform an administrative installation and MSI has not yet been upgraded, you must add the -a admin parameter when you start the InstallShield Wizard in this procedure. For example, to start the InstallShield Wizard for version 5.20, you would type the following command:
dir5.20_agent_windows.exe -a admin
This parameter updates MSI and runs the installation program in administrative mode. Restart the system if prompted to do so. To install Level 2 : IBM Director Agent on 32-bit Windows using the InstallShield wizard, complete the following steps: 1. To start the installation from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. Use the unzip command to extract the contents of the installation package to a temporary directory. c. Click Start Run.
246
d. In the Open field, type one of the following commands and press Enter: v 5.20 only: \directory\FILES\dir5.20_agent_windows.exe v 5.20 Update 1 only: \directory\FILES\dir5.20.1_agent_windows.exe where directory is the local directory into which you extracted the files. The Welcome to the InstallShield Wizard for IBM Director Agent window opens. e. Go to step 4. 2. To start the installation from the IBM Director Agents & Consoles (1 of 2) CD, perform the following steps: a. Insert the CD into the CD-ROM drive. b. Click Start Run. c. In the Open field, type one of the following commands and press Enter: v 5.20 only: \director\agent\windows\i386\FILES\ dir5.20_agent_windows.exe v 5.20 Update 1 only: \director\agent\windows\i386\FILES\ dir5.20.1_agent_windows.exe The Welcome to the InstallShield Wizard for IBM Director Agent window opens. d. Go to step 4. 3. To start the installation from the IBM Director on x86 CD, perform the following steps: a. Insert the CD into the CD-ROM drive. b. If the installation program starts automatically and the IBM Director Setup window opens, go to step 3d. Otherwise, click Start Run. c. In the Open field, type the following command and press Enter:
e:\setup.exe
where e is the drive letter of the drive. The installation program starts, and the IBM Director Setup window opens. d. Click Install IBM Director Agent. The Welcome to the InstallShield Wizard for IBM Director Agent window opens. e. Go to step 4. Accessibility note: Screen readers might not process the IBM Director Setup window correctly. To start the installation wizard for IBM Director Agent using the keyboard, perform the following steps: a. Close the IBM Director Setup window. b. Open Windows Explorer. c. Browse to the \director\agent\windows\i386\FILES directory on the IBM Director on x86 CD. d. Run one of the following programs: v 5.20 only: dir5.20_agent_windows.exe v 5.20 Update 1 only: dir5.20.1_agent_windows.exe The Welcome to the InstallShield Wizard for IBM Director Agent window opens. e. Go to step 4. 4. Click Next. The License Agreement window opens.
247
5. Click I accept the terms in the license agreement and click Next. The Feature and Installation Directory Selection window opens. Level 2: IBM Director Agent and Level 1: Core Services are selected automatically for installation; a hard-disk-drive icon left of each component. is displayed to the
6. A red X is displayed to the left of IBM Director Remote Control Agent, which is optional. The IBM Director Remote Control Agent enables a system administrator to perform remote desktop functions on the management server. To install IBM Director Remote Control Agent, click the red X to the left of the feature name. A menu opens. Click either This feature will be installed on local hard drive or This feature, and all subfeatures, will be installed on local hard drive. 7. Click Next. 8. Encrypt data transmissions between IBM Director Server and IBM Director Agent is selected by default. Note: If encryption is enabled, the following conditions apply: v The managed system is automatically secured, and the Secure IBM Director Server must request access to manage this system check box is unavailable. v Only management servers with encryption enabled are able to communicate with the managed system. To accept this setting, go to step 10. If you do not want to encrypt transmissions between IBM Director Server and IBM Director Agent, clear the check box and go to step 9. Select the Secure IBM Director Server must request access to manage this system check box. This selection ensures that only authorized instances of IBM Director Server can manage this system. Optional: In the Add Known Server Address field, enter a comma-separated list of IBM Director Server addresses to which IBM Director Agent should announce itself. The format for this field is <protocol>::<address>, for example, TCPIP::10.3.1.4, TCPIP::192.168-1.10. Click Next. The Software Distribution Settings window opens. To select an alternative location for the storage of software-distribution packages before they are applied to IBM Director Agent, click Change and select another directory. Click Next. The Ready to Install the Program window opens. Click Install. The Installing IBM Director Agent window opens. The status bar indicates the progress of the installation. When the installation is completed, the Network Driver Configuration window opens. In the System Name field, type the name that you want to be displayed in IBM Director Console. By default, this value is the NetBIOS name of the managed system. Define the communication protocols to use between IBM Director Server and IBM Director Agent. a. In the Network drivers field, the TCPIP (all adapters) setting is enabled by default. To enable another protocol, select the protocol and then select the Enable driver check box.
9.
10.
11.
12. 13.
14.
15.
248
Note: If you disable the TCPIP (all adapters) setting and enable an individual device driver on a system with multiple network adapters,IBM Director Agent will receive only those data packets that are addressed to the individual adapter. b. In the Network timeout field, type the number of seconds that IBM Director Serverwaits for a response from IBM Director Agent. By default, this value is set to 15 seconds. c. Click Enable Wake on LAN if the network adapter supports the Wake on LAN feature. Note: To determine whether your server supports the Wake on LAN feature, see your server documentation. 16. If you chose to install the IBM Director Remote Control Agent, the following options are available: Require User Authorization for System Access Select this check box to request authorization from the local user before accessing the managed system remotely. Disable Screen Saver Select this check box to disable the screen saver when the managed system is controlled remotely. Disable Background Wallpaper Select this check box to disable desktop wallpaper when the managed system is controlled remotely. You might want to disable the wallpaper because complicated backgrounds can affect the performance of remote control and increase network traffic. 17. Click OK. The status bar displays the progress of the installation. When the installation is completed, the InstallShield Wizard Completed window opens. 18. Click Finish. 19. If you installed IBM Director Agent from the CD, remove the CD from the drive. 20. If you are prompted to restart your system, click Yes. Performing an unattended installation of Level 2: IBM Director Agent on 32-bit Windows: After preparing your 32-bit Windows system, you can use a response file to perform an unattended installation of Level 2:IBM Director Agent. The response file that you create can be employed on supported systems in your environment to install IBM Director Agent. Depending on the version of IBM Director Agent you are installing, you can install IBM Director Agent on Windows from either installation media or from a downloaded installation package.
Table 102. Installation options for IBM Director Agent on Windows
Version 5.20 Installation media IBM Director on x86, V5.20 CD IBM Director Agents & Consoles, V5.20 (1 of 2) CD 5.20 Update 1 IBM Director on x86, Version 5.20 Update 1 CD Downloaded installation package file name dir5.20_agent_windows.zip dir5.20_System_x.iso dir5.20.1_agent_windows.zip
249
Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on the system, it is installed during the IBM Director Agent installation. If the upgrade is necessary, the system prompts you to restart following the installation of IBM Director Agent without specifying that MSI was installed. Unless you install using the response file and set the RebootIfRequired parameter to N, you are prompted to restart whether or not the IBM Director Agent installation is completed successfully. To use a response file to install Level 2: IBM Director Agent on 32-bit Windows, complete the following steps: 1. To start the installation from a Web download, perform the following steps: a. Download the installation package from the IBM Director Web site at www.ibm.com/systems/management/director/. b. Use the unzip command to extract the contents of the installation package to a temporary directory. c. Copy the response file (\directory\FILES\diragent.rsp) to a new location, where directory is the local directory into which you extracted the files. d. Go to step 3. 2. To start the installation from a CD, perform the following steps: a. Insert the CD into the CD-ROM drive. b. If the installation program starts automatically and the IBM Director Setup window opens, close it. c. Copy the response file (\director\agent\windows\i386\FILES\diragent.rsp) to a local directory. d. Go to step 3. 3. Open the copy of the diragent.rsp file in an ASCII text editor. 4. Modify and save the response file with a new file name. This file follows the Windows INI file format and is fully commented. 5. Click Start Run. 6. In the Open field, type one of the following commands (all on one line) and press Enter: v 5.20 only:
\directory\FILES\dir5.20_agent_windows.exe /s /a installationtype rsp="responsefile.rsp" option
v 5.20 Update 1 only:

\directory\FILES\dir5.20.1_agent_windows.exe /s /a installationtype rsp="responsefile.rsp" option
where: v directory is either the local directory into which you extracted the files from a web download, or the following path on the CD media: \director\agent\windows\i386\. v /s is an optional parameter that suppresses all file extraction windows. v installationtype is one of the following commands: unattended shows the progress of the installation but does not require any user input. silent suppresses all output to the screen during installation. v responsefile.rsp is the path and name of the response file that you created in step 4.
250
v option is one of the following optional parameters:

Table 103. Optional installation parameters Optional parameter waitforme debug What it does Ensures that installation process will not end until the installation of IBM Director Agent is completed. Logs all messages that are sent by the Microsoft Windows Installer log engine, including status and information messages. Specifies the fully qualified name of an alternative log file. Enables verbose logging.
7. If you set the RebootIfRequired parameter to Y in the response file, reboot the system if prompted to do so. 8. If you installed IBM Director Agent from the CD, remove the CD from the drive.
Installing Level 2: IBM Director Agent on 64-bit Windows (Intel Itanium only)
After preparing your system, you can install Level 2: IBM Director Agent on a 64-bit Windows Intel Itanium. IBM Director 5.20 support for Intel Itanium systems running 64-bit Windows is provided by IBM Director Agent version 5.10.3. There is no IBM Director Agent version 5.20 for Intel Itanium systems running 64-bit Windows. IBM Director Agent for Intel Itanium systems running 64-bit Windows is available as a Web-download only. Download the dir5.10.3_agent_windows64.zip file from the IBM Web site at www.ibm.com/systems/management/director/. The wizard can be used in a standard interactive mode, or you can perform an unattended installation using a response file to provide answers to the questions that the wizard poses. Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on the system, it is installed during the IBM Director Agent installation. If the upgrade is necessary, the system prompts you to restart following the installation of IBM Director Agent without specifying that Microsoft Windows Installer was installed. Unless you install using the response file and set the RebootIfRequired parameter to N, you are prompted to restart whether or not the IBM Director Agent installation is completed successfully. In addition, if you attempt to perform an administrative installation and MSI has not yet been upgraded, you must change to the directory containing the dir5.10.3_agent_windows64.exe file and run the installation program using the following command:
dir5.10.3_agent_windows64.exe -a admin
This command updates MSI and runs the installation program in administrative mode. Restart the system if prompted to do so. Installing Level 2: IBM Director Agent on 64-bit Windows (Intel Itanium only) using the InstallShield: After preparing your 64-bit Windows system, you can use the InstallShield wizard to install IBM Director Agent.
251
IBM Director 5.20 support for Intel Itanium systems running 64-bit Windows is provided by IBM Director Agent version 5.10.3. There is no IBM Director Agent version 5.20 for Intel Itanium systems running 64-bit Windows. To use InstallShield to install Level 2: IBM Director Agent on an Intel Itanium system running 64-bit Windows, complete the following steps: 1. Download the dir5.10.3_agent_windows64.zip file from the IBM Director Support Web site at www.ibm.com/systems/management/director/. 2. Extract the contents of the dir5.10.3_agent_windows64.zip file into a local directory. 3. Locate the dir5.10.3_agent_windows64.exe file. This file is in the directory\FILES directory, where directory is the local directory into which you extracted the contents of the dir5.10.3_agent_windows64.zip file. 4. Double-click the dir5.10.3_agent_windows64.exe file. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Agent window opens. 5. Click Next. The License Agreement window opens. 6. Click I accept the terms in the license agreement and click Next. The Feature and Installation Directory Selection window opens. Level 2: IBM Director Agent is selected automatically for installation; a hard-disk-drive icon is displayed to the left of the component. 7. A red X is displayed to the left of IBM Director Remote Control Agent, which is optional. The IBM Director Remote Control Agent enables a system administrator to perform remote desktop functions on the management server. To install IBM Director Remote Control Agent, click the red X to the left of the feature name. A menu opens. Click either This feature will be installed on local hard drive or This feature, and all subfeatures, will be installed on local hard drive. 8. Click Next. The Security Settings window opens. 9. The Secure IBM Director Server must request access to manage this system check box is selected by default. This setting ensures that IBM Director Server cannot manage this system until it is granted access. 10. Optional: Add a comma-separated list of IBM Director servers that you want IBM Director Agent to announce itself to in the Add Known Server Address field. The format for this field is <protocol>::<address>, for example, TCPIP::10.3.1.4, TCPIP::192.168-1.10. 11. Click Next. The Software Distribution Settings window opens. 12. To select an alternative location for the storage of software-distribution packages before they are applied to IBM Director Agent, click Change and select another directory. 13. Click Next. The Ready to Install the Program window opens. 14. Click Install. The Installing IBM Director Agent window opens. The status bar indicates the progress of the installation. When the installation is completed, the Network Driver Configuration window opens. 15. In the System Name field, type the name that you want to be displayed in IBM Director Console. By default, this name is the NetBIOS name of the managed system. 16. Define the communication protocols to use between IBM Director Server and IBM Director Agent. a. In the Network drivers field, the TCPIP (all adapters) setting is enabled by default. To enable another protocol, select the protocol and then select the Enable driver check box.
252
Note: If you disable the TCPIP (all adapters) setting and enable an individual device driver on a system with multiple network adapters, IBM Director Agent will receive only those data packets that are addressed to the individual adapter. b. In the Network timeout field, type the number of seconds that IBM Director Server waits for a response from IBM Director Agent. By default, this value is set to 15 seconds. c. Click Enable Wake on LAN if the network adapter supports the Wake on LAN feature. Note: To determine whether your server supports the Wake on LAN feature, see your server documentation. 17. If you chose to install the IBM Director Remote Control Agent, the following options are available: Require User Authorization for System Access Select this check box to request authorization from the local user before accessing the managed system remotely. Disable Screen Saver Select this check box to disable the screen saver when the managed system is controlled remotely. Disable Background Wallpaper Select this check box to disable desktop wallpaper when the managed system is controlled remotely. You might want to disable the wallpaper because complicated backgrounds can affect the performance of remote control and increase network traffic. 18. Click OK. The status bar displays the progress of the installation. When the installation is completed, the InstallShield Wizard Completed window opens. 19. Click Finish. 20. If you are prompted to restart your system, click Yes. Performing an unattended installation of Level 2: IBM Director Agent on 64-bit Windows (Intel Itanium only): After preparing your 64-bit Windows system, you can use a response file to perform an unattended installation of Level 2:IBM Director Agent. The response file that you create can be employed on supported systems in your environment to install IBM Director Agent. IBM Director 5.20 support for Intel Itanium systems running 64-bit Windows is provided by IBM Director Agent version 5.10.3. There is no IBM Director Agent version 5.20 for Intel Itanium systems running 64-bit Windows. To use a response file to install Level 2: IBM Director Agent on an Intel Itanium system running 64-bit Windows, complete the following steps: 1. Download the dir5.10.3_agent_windows64.zip file from the IBM Director Web site at www.ibm.com/systems/management/director/. 2. Extract the contents of the dir5.10.3_agent_windows64.zip file into a local directory. 3. Copy the diragent.rsp file. 4. Open the copy of the diragent.rsp file in an ASCII text editor and modify the installation settings. This file follows the Windows INI file format and is fully commented. 5. Save the copy of the diragent.rsp file with a new file name.
253
6. Open a command prompt and change to the directory that contains the Level 2: IBM Director Agent installation file (dirdir5.10.3_agent_windows64.exe). 7. From the command prompt, type the following command and press Enter:
dirdir5.10.3_agent_windows64.exe /s /a installationtype rsp="responsefile.rsp" option
where: v /s is an optional parameter that suppresses all file extraction windows. v installationtype is one of the following commands: unattended shows the progress of the installation but does not require any user input. silent suppresses all output to the screen during installation. v responsefile.rsp is the path and name of the response file that you created in step 5 on page 253. v option is one of the following optional parameters:
Table 104. Optional installation parameters Parameter waitforme debug What it does Ensures that dir5.10.3_agent_windows64.exe process will not end until the installation of IBM Director Agent is completed Logs all messages that are sent by the Microsoft Windows Installer log engine, including status and information messages Specifies the fully qualified name of an alternative log file Enables verbose logging
8. If you set the RebootIfRequired parameter to Y in the response file, reboot the system if prompted to do so.
Installing IBM Director Agent using the Software Distribution task

You can use the IBM Director Software Distribution task to install IBM Director Agent on managed systems running AIX, i5/OS, Linux for System x, Linux on POWER, Linux for System z, or Windows. Note: The file names listed below are English XML files. Files for other supported languages are appended with the appropriate language identifier. For example, dir5.20_agent_linux_de.xml is the German XML file. The following files describe IBM Director Agent:
Table 105. Source and file names of descriptor files used to install IBM Director Agent using Software Distribution Version CD or downloaded installation package Path and file name of the software distribution package descriptor
IBM Director Agent on AIX 5.20 IBM Director for AIX 5L, V5.20 IBM Director for Linux on POWER, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) Dir5.20_AIX.tar.gz /director/agent/aix/META-INF/ dir5.20_agent_aix.xml /director/agent/aix/META-INF/ dir5.20_agent_aix.xml
254
Table 105. Source and file names of descriptor files used to install IBM Director Agent using Software Distribution (continued) Version 5.20.1 CD or downloaded installation package IBM Director for AIX 5L, Version 5.20 Update 1 Dir5.20.1_Agent_Console_AIX.tar.gz IBM Director Agent on i5/OS 5.20 If you have selected to install the IBM Director Agent images on the i5/OS management server: IBM Director Agents & Consoles, V5.20 (1 of 2) dir5.20_agent_i5OS.zip 5.20.1 dir5.20.1_agent_i5OS.zip /QIBM/ProdData/VE2/ManagedNodes/ Directori5OS/META-INF/ Directori5OSRPD_agentpackagedIU.xml Directori5OSRPD_agentpackagedIU.xml in the /FILES/Director/Directori5OSAgent.zip file META-INF/ Directori5OSRPD_agentpackagedIU.xml META-INF/ Directori5OSRPD_agentpackagedIU.xml Path and file name of the software distribution package descriptor /director/agent/aix/META-INF/ dir5.20.1_agent_aix.xml /META-INF/dir5.20.1_agent_aix.xml
IBM Director Agent on Linux for System x 5.20 IBM Director on x86, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) dir5.20_agent_linux.tar 5.20.1 IBM Director on x86, Version 5.20 Update 1 dir5.20.1_agent_linux.tar IBM Director Agent on Linux on POWER 5.20 IBM Director for AIX 5L, V5.20 IBM Director for Linux on POWER, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) CD Dir5.20_LinuxonPower.tar.gz 5.20.1 IBM Director for Linux on POWER, Version 5.20 Update 1 Dir5.20.1_Agent_Console_LinuxonPower.tar.gz IBM Director Agent on Linux for System z 5.20 IBM Director for Linux on System z, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) 5.20.1 dir5.20.1_agent-agent-linux-s390.tar /director/agent/linux/s390/META-INF/ dir5.20_agent_linz.xml /director/agent/linux/s390/META-INF/ dir5.20.1_agent_linz.xml /director/agent/linux/ppc/META-INF/ dir5.20.1_agent_linppc.xml /director/agent/linux/ppc/META-INF/ dir5.20_agent_linppc.xml director/agent/linux/i386/META-INF/ dir5.20_agent_linux.xml /META-INF/dir5.20_agent_linux.xml /director/agent/linux/i386/META-INF/ dir5.20.1_agent_linux.xml /META-INF/dir5.20.1_agent_linux.xml
IBM Director Agent on Windows (32-bit) 5.20 IBM Director on x86, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) dir5.20_agent_windows.zip 5.20.1 IBM Director on x86, Version 5.20 Update 1 dir5.20.1_agent_windows.zip \director\agent\windows\i386\META-INF\ dir5.20_agent_windows.xml \META-INF\dir5.20_agent_windows.xml \director\agent\windows\i386\META-INF\ dir5.20.1_agent_windows.xml \META-INF\dir5.20.1_agent_windows.xml
255
Table 105. Source and file names of descriptor files used to install IBM Director Agent using Software Distribution (continued) Version CD or downloaded installation package Path and file name of the software distribution package descriptor
IBM Director Agent on 64-bit Intel Itanium Note: IBM Director 5.20 and higher support for Intel Itanium systems is provided by IBM Director Agent version 5.10.3. Linux Windows dir5.10.3_agent_linux64.tar dir5.10.3_agent_windows64.zip /META/INF/dir5.10.3_agent_linux64.xml \META-INF\dir5.10.3_agent_windows64.xml
Related tasks Preparing to install IBM Director Agent on Windows on page 161 Before installing IBM Director Agent on a managed system running Windows, make sure that your system meets all the applicable requirements. Preparing to manage service processors with IBM Director on page 135 You can use IBM Director to manage supported service processors that are installed in a managed system. Related reference Installing IBM LM78 and SMBus device drivers for Linux on page 144 If you plan to install IBM Director Server on a System x or xSeries server running Linux, you might need to install either or both the LM78 and SMBus device drivers for Linux. These device drivers ensure that certain IBM Director tasks and functions work correctly. Creating a software package: You can create a software package for installing or upgrading IBM Director Agent or installing IBM Director Core Services. To create a software package, complete the following steps: 1. Locate the installation or upgrade packages for IBM Director. See the IBM Director Planning, Installation and Configuration Guide for more information. 2. If you want to accept the default settings for the installation, go to step 3. Otherwise, copy the response file: use diragent.rsp for IBM Director Agent, or use coresvcs.rsp for IBM Director Core Services. Open the copy in an ASCII text editor and modify the response file as needed. Save the modified file with a new file name. 3. Start IBM Director Console. 4. In the Tasks pane, double-click Software Distribution. The Software Distribution Manager window opens.
256
5. If you have not installed IBM Director 5.20 Software Distribution Premium Edition, go to step 6. Otherwise, expand the Wizards tree. 6. Double-click IBM Update Assistant. The IBM Update Assistant window opens. 7. If you want to get files from the management server, click Get files from the Director server. By default, Get files from the local system is selected. 8. To select a file, click Browse. The IBM Update Package/Root Directory Location window opens. 9. Locate the appropriate XML file and click it. The name of the XML file is displayed in the File Name field. Note: Use the correct XML file for your language. The correct file for English installations is the one without the language code, for example, dir5.20_agent_windows.xml. 10. Click OK. The IBM Update Assistant window reopens. 11. Click Next. The second IBM Update Assistant window opens. 12. To specify an alternative response file, click Browse and locate the file that you modified in step 2 on page 256.
257
Note: If you do not specify an alternative response file, the package is installed with the default settings that are specified in the installation script. 13. Click Finish. As the package is processed, a status message is displayed at the bottom of the window. When the processing is completed, the software-distribution package is displayed in the Tasks pane of IBM Director Console. Installing a software package: After you create a software package, you can use the Software Distribution task to remotely install the package on supported systems. To use the Software Distribution task to install a software package, complete the following steps: 1. Start IBM Director Console. 2. In the Tasks pane, expand the Software Distribution task. 3. Click the software package that you want to distribute. Then, drag it into the Group Contents pane and drop it onto the icon that is displayed for the system on which you want to install the software package. A window opens. Note: To distribute software to several systems at once, you can drag the software package into the Groups pane and drop it onto the icon for the group. Alternatively, you can select multiple managed systems in the Group Contents pane. 4. When prompted with Do you wish to create a scheduled job for this task or execute immediately?, click Schedule or Execute Now. If you click Execute Now, the software package is distributed immediately. If you click Schedule, the New Scheduled Job window opens. 5. Schedule the job: a. In the Scheduled Job field, type a unique name for the job. This name is displayed in the Jobs pane of the Scheduler window. b. In the Date field, type the day you want the software package to be installed (in MM/DD/YYYY format). c. In the Time field, type the time you want the software package to be installed. For more information about the Scheduler task, see the IBM Director Systems Management Guide. 6. Click OK. The Save Job Confirmation window opens. 7. Click OK.
Changing IBM Director installation options

After installing IBM Director, you can use the installation process to add or remove IBM Director options.
Changing installation options on NetWare

You can add Management Processor Assistant Agent to an existing IBM Director Agent installation is running on NetWare. Notes: 1. You cannot use this procedure to uninstall the MPA Agent. However, you can use this procedure to add it to an existing IBM Director Agent installation.
258
2. To modify an IBM Director Agent installation, you must log on to the NetWare server from a Windows workstation running the NetWare Client for Windows. 3. The SYS volume must be mapped as a drive to the system running Windows. 4. You must have administrator or supervisor access on the NetWare server. To add Management Processor Assistant Agent to an existing IBM Director Agent installation that is running on NetWare, complete the following steps: 1. Stop IBM Director Agent. From the server running NetWare, change to the console screen. Type the following command and press Enter:
unload twgipc
2. Start Windows Explorer and open the \directory\FILES directory, where directory is the location to which you saved the dir5.20_agent_netware.exe file. 3. Double-click the dir5.20_agent_netware.exe file. The InstallShield wizard starts. 4. Click Next. The Installing IBM Director Agent window opens. 5. Click Next to accept the license agreement. The Choose Destination Location window opens.
Figure 16. Modifying IBM Director Agent on NetWare: Choose Destination Location window
6. Click the drive that is mapped to the SYS volume on the NetWare server; then, click Next. The Select Components window opens.
259
Figure 17. Modifying IBM Director Agent on NetWare: Select Components window
7. Select the Management Processor Assistant Agent check box. 8. Click Next. The Setup Status window opens, and the IBM Director Agent installation begins. When the installation is completed, the InstallShield Wizard Completed window opens. 9. Click Finish. 10. On the NetWare server, change to the console screen. 11. Type the following command and press Enter:
load twgipc
Changing IBM Director installation options on a Windows system

You can add or remove an IBM Director feature from a system that is running Windows. To add a previously uninstalled feature to or remove a feature from IBM Director Server, IBM Director Console, or IBM Director Agent, complete the following steps: 1. Click Start Settings > Control Panel. The Control Panel window opens. 2. Double-click Add/Remove Programs. The Add/Remove Programs window opens. 3. Click the IBM Director software component that you want to modify; then, click Change. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard window opens. 4. Click Next. The Program Maintenance window opens.
260
Figure 18. Program Maintenance window
5. Click Modify; then, click Next. 6. Continue through the wizard, making changes as necessary.
Changing IBM Director installation options on a Linux system

You can add or remove an IBM Director feature from a system that is running Linux. Installing an IBM Director feature on a Linux system: You can add or remove an IBM Director feature from a system that is running Linux. To add a previously uninstalled feature to or to remove a feature from IBM Director Server, IBM Director Console, IBM Director Agent, complete the following steps: 1. Copy the applicable response file (*.rsp) to a local directory. 2. Open an ASCII text editor and modify the response file. 3. Save the modified response file. 4. Run the installation script for the component you want to change using the response file. Uninstalling an IBM Director feature on a Linux system: You can remove an IBM Director feature from a system that is running Linux. To remove a feature from IBM Director Server, IBM Director Console or IBM Director Agent, complete the following steps:
261
1. Modify the diruninstall script, which is in located in the installation directory. By default, this script removes all detected IBM Director components. To uninstall specific components, you must set the SmartUninstall setting to 0 and then make the other modifications. 2. Save the modified uninstallation script. 3. To stop IBM Director Agent, from a command prompt, type the following command and press Enter:
install_root/bin/twgstop
where install_root is the root directory of your IBM Director installation. 4. Run the diruninstall script. Type the following command and press Enter:
/SourceDirectory/diruninstall
where SourceDirectory is the directory to which you copied the modified uninstallation script. 5. To start IBM Director Agent, type the following command and press Enter:
You also can use the standard RPM commands.
Upgrading and updating IBM Director

IBM Director components can be upgraded to take advantage of new features, managed-object support, and bug fixes in subsequent versions of the software. Before beginning any upgrade, consult the release notes for version-specific compatibility information and special upgrade instructions. The following general rules apply to the version compatibility of IBM Director components: v You cannot upgrade IBM Director components on Linux on System z directly from a version prior to 5.20 to version 5.20.1. You can either uninstall your current version and then install 5.20.1, or you can first upgrade to version 5.20 and then update to version 5.20.1. v IBM Director Server and IBM Director Console must be at the same version level, even when installed on different systems. v Components that are installed on the same system, such as IBM Director Console and IBM Director Agent, must be at the same version level. v The version of IBM Director Server must always be greater than or equal to the version of any IBM Director Agent or IBM Director Core Services installed on managed systems. v If you upgrade to a new version of IBM Director Server, you must also upgrade all instances of IBM Director Console to the same version. v If you upgrade to a new version of IBM Director Agent or IBM Director Core Services on any managed system, you must upgrade both IBM Director Server and all instances of IBM Director Console to a version that is the same or later than the agent version. v You can upgrade to a new version of IBM Director Server without necessarily upgrading all instances of IBM Director Agent or IBM Director Core Services.
262
Backing up IBM Director data before upgrading or updating

Before upgrading or updating IBM Director, you should back up the IBM Director persistent data. Complete the following steps to back up IBM Director persistent data on the management server before upgrading or updating IBM Director Server. 1. Shut down IBM Director Server. Type one of the following commands, depending on the operating system of the management server:
Operating system AIX or Linux i5/OS Command install_root/bin/twgstop QSH CMD(/QIBM/ProdData/Director/bin/ twgstop) or ENDTCPSVR *DIRECTOR unload twgipc net stop twgipc
NetWare Windows
where install_root is the root directory of your IBM Director installation. 2. Use the twgsave command to save the IBM Director persistent data. Type one of the following commands, depending on the operating system of the management server.
Operating system AIX or Linux i5/OS NetWare and Windows Command install_root/bin/twgsave QSH CMD(/QIBM/ProdData/Director/bin/ twgsave) install_root\bin\twgsave
where install_root is the root directory of your IBM Director installation. Note: If you do not want to back up the software package information for software distribution, issue the -s option with the twgsave command. The IBM Director persistent data is saved to the following directory/save file:
Operating system AIX, Linux, NetWare or Windows i5/OS Command install_root.save.n /QIBM/UserData/Director/save.n
where install_root is the root directory of your IBM Director installation. The variable n is an integer starting at 1 that is incremented each time the twgsave command is run. The persistent data includes configuration and working IBM Director data. It does not include database information. 3. If you have the Capacity Manager extension installed, back up your Capacity Manager data. When you update IBM Director, you also need to update Capacity Manager. See Preparing to update Capacity Manager in the IBM Director Capacity Manager Installation and Users Guide for more information. 4. Back up your security keys. See Key information and management in the IBM Director Systems Management Guide for more information. 5. Back up your dynamic group definitions. See Exporting a dynamic group in the IBM Director Systems Management Guide for more information.
263
6. Back up your BladeCenter configuration profiles. See Exporting a profile to an XML file in the IBM Director Systems Management Guide for more information. 7. Back up your event action plans. See Exporting an event action plan in the IBM Director Systems Management Guide for more information. 8. Optional: If you have an external database for IBM Director, back up the database using the instructions provided for your database. 9. Optional: If you have customized any files in the IBM Director environment, such as icons, resources, or extensions written with the IBM Director SDK, back up the customized files.
Upgrading to IBM Director 5.20 or later from previous releases

You can upgrade IBM Director version 4.10 or later components by running the installation program for the component that you want to upgrade. During the upgrade process, you can choose to install previously uninstalled features and extensions. The database configuration used in the previous version is maintained. Notes: 1. After upgrading IBM Director Server, you might be required to upgrade any IBM Director extensions that are installed. Make sure that you read the release notes for any extensions that are on your management server prior to upgrading. 2. If you use Software Distribution Premium Edition and your software reverts to Software Distribution Standard Edition after you update IBM Director, you need to reinstall Software Distribution Premium Edition. To upgrade IBM Director, follow the steps for a new installation, including any planning and environment preparation that might be necessary. When you install the latest IBM Director software, the features from your previous installation are automatically selected. If you are running one of the following versions of IBM Director on a supported operating system, you can upgrade to IBM Director 5.20 or later: v IBM Director 4.10 v IBM Director 4.10.2 v IBM Director 4.11 v IBM Director 4.12 v IBM Director 4.20 v IBM Director 4.20.2 v IBM Director 4.21 v IBM Director 4.22 v IBM Director 5.10 v IBM Director 5.10.1 v IBM Director 5.10.2 v IBM Director 5.10.3 Important: Some operating systems or hardware that were supported for older versions of IBM Director are not supported in later versions. To successfully upgrade, your existing IBM Director component must be running on an operating system and hardware configuration that is supported by the version of IBM Director to which you are upgrading.
264
Versions of IBM Director that are earlier than IBM Director 4.10 are not compatible with IBM Director version 5.20 or later. If you are running a version of IBM Director that is earlier than IBM Director 4.10, you can perform one of the following operations: v Uninstall your existing IBM Director installation and then install IBM Director version 5.20 or later. v Upgrade your existing IBM Director installation to version 4.10 or later. Then, upgrade to IBM Director version 5.20 or later. Before upgrading IBM Director, consider the following information: v (System x Linux only) When upgrading from an installation to which a product-engineering fix has been applied, you must return IBM Director to the base installation state before upgrading to version 5.20 or later. To do this, perform one of the following tasks: Uninstall the fix using the following command:
rpm -e fixname
v v
where fixname is the name of the fix to be removed. The version of IBM Director Agent cannot be later than the version of IBM Director Server running on the management server. IBM Director Server and IBM Director Console must have the same release level. If you upgrade IBM Director Server, you must upgrade IBM Director Console also. If IBM Director Console is installed on the same system as IBM Director Agent or IBM Director Core Services, both software components must have the same release level as IBM Director Server. If version 4.22 or earlier of the IBM LM78 or SMBus device driver for Linux is installed on a managed system, you must uninstall it and then install version 5.20 or later of the device driver. If you have the Hardware Management Console extension installed for 5.10 Update 3 and earlier, you must uninstall the Hardware Management Console extension before updating IBM Director to version 5.20 or later. (Software Distribution Premium Edition only) When upgrading Software Distribution Premium Edition, make sure that IBM Director Server is the same version as Software Distribution Premium Edition to which you are upgrading. When upgrading Software Distribution Premium Edition, the upgrade process will migrate data, such as existing packages; it does not uninstall any information. If Software Distribution Premium Edition reverts back to Software Distribution Standard Edition after an update to IBM Director Server, reinstall Software Distribution Premium Edition.
Upgrading IBM Director Server

You can upgrade to IBM Director Server 5.20 or later from IBM Director Server, version 4.10 or later. To successfully upgrade, your existing IBM Director Server must be running on an operating system that is supported by the version of IBM Director Server to which you are upgrading. Otherwise, you cannot upgrade to IBM Director Server 5.20 or later.
265
Note: Always read the release notes before beginning any installation or upgrade procedure. 1. Linux only: On Linux management servers, you must manually stop IBM Director Server before installing a new version of IBM Director Server. At a command prompt, type the following command and then press Enter:
where install_root is the root directory of your IBM Director installation. . 2. To upgrade IBM Director Server, follow the general installation instructions for your operating system.
Upgrading IBM Director Console

You can upgrade toIBM Director Console 5.20 or later from IBM Director Console, version 4.1 or later. To successfully upgrade, your existing IBM Director management console must be running on an operating system that is supported by the version ofIBM Director Console to which you will be upgrading. Otherwise, you cannot upgrade to IBM Director Console 5.20 or later. To upgrade IBM Director Console, follow the general installation instructions for your operating system. Important: If the system that you are upgrading has IBM Director Console and IBM Director Agent installed, consider the following information: v To upgrade both IBM Director Console and IBM Director Agent at the same time, use the IBM Director Console installation software. v (System x only) To upgrade both IBM Director Console and IBM Director Agent at the same time, use the IBM Director Console installation software that is provided at the IBM Director Web site: www.ibm.com/systems/management/ director/. If you use the IBM Director Console installation software that is provided on the CD, the installation process will detect and uninstall any previous version of IBM Director Agent, and upgrade only IBM Director Console.
Upgrading IBM Director Agent

You can upgrade to IBM Director Agent 5.20 or later from IBM Director Agent, version 4.10 or later. You can use either standard installation procedures or the IBM Director Software Distribution task. Notes: v If IBM Director Console and IBM Director Agent are installed on the same system, both software components must be at the same release level as IBM Director Server. v The version of IBM Director Agent cannot be later than the version of IBM Director Server running on the management system. v If you want to use IBM Director to manage a system running an operating system that IBM Director 5.20 does not support, do not upgrade IBM Director Agent. IBM Director 5.20 can manage systems running IBM Director Agent, versions 4.10 and later. Important: If the system that you are upgrading has IBM Director Console and IBM Director Agent installed, consider the following information:
266
v To upgrade both IBM Director Console and IBM Director Agent at the same time, use the IBM Director Console installation software. v (System x only) To upgrade both IBM Director Console and IBM Director Agent at the same time, use the IBM Director Console installation software that is provided at the IBM Director Web site: www.ibm.com/systems/management/ director/. If you use the IBM Director Console installation software that is provided on the CD, the installation process will detect and uninstall any previous version of IBM Director Agent, and upgrade only IBM Director Console. To successfully upgrade, your existing IBM Director Agent must be running on an operating system that is supported by the version of IBM Director Agent to which you will be upgrading. Otherwise, you cannot upgrade to IBM Director Agent 5.20 or later. To upgrade IBM Director Agent, complete the following steps: 1. Linux only: On Linux systems, you must manually stop IBM Director Agent before installing a new version. At a command prompt, type the following command and then press Enter:
where install_root is the root directory of your IBM Director installation. 2. To upgrade IBM Director Agent using standard installation procedures, follow the general installation instructions for IBM Director Agent for your operating system. Upgrading IBM Director Agent using the Software Distribution task: You can use the IBM Director Software Distribution task to upgrade IBM Director Agent on managed systems running AIX, i5/OS, Windows (32-bit and 64-bit), or Linux (32-bit and 64-bit). The zip files on the IBM Director Agent CDs contain the different agent packages that can be imported using IBM Director Software Distribution. These are based on the operating system and hardware on which you intend on to install the packages. Note: The file names listed below are English XML files. Files for other supported languages are appended with the appropriate language identifier. For example, dir5.20_agent_aix_packagedIU_de.zip is the German file. The following files can be used to import IBM Director Agent for the applicable platforms:
Table 106. Source and file names of files used to upgrade IBM Director Agent using Software Distribution Version CD or downloaded installation package Path and file name of the software distribution package
IBM Director Agent on AIX 5.20 IBM Director for AIX 5L, V5.20 IBM Director for Linux on POWER, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) 5.20.1 IBM Director for AIX 5L, Version 5.20 Update 1 /director/agent/aix/ dir5.20.1_agent_aix_packagedIU.zip
/director/agent/aix/ dir5.20_agent_aix_packagedIU.zip
267
Table 106. Source and file names of files used to upgrade IBM Director Agent using Software Distribution (continued) Version CD or downloaded installation package Path and file name of the software distribution package
IBM Director Agent on i5/OS 5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) dir5.20_agent_i5OS.zip 5.20.1 dir5.20.1_agent_i5OS.zip /director/agent/i5os/ dir5.20_agent_i5os_packagedIU.zip dir5.20_agent_i5os_packagedIU.zip dir5.20.1_agent_i5os_packagedIU.zip
IBM Director Agent on Linux for System x 5.20 IBM Director on x86, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) 5.20.1 IBM Director on x86, Version 5.20 Update 1 director/agent/linux/i386/ dir5.20_agent_linux_i386_packagedIU.zip /director/agent/linux/i386/ dir5.20.1_agent_linux_i386_packagedIU.zip
IBM Director Core Services on Linux for System x 5.20 IBM Director on x86, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) 5.20.1 IBM Director on x86, Version 5.20 Update 1 coresvcs/linux/i386/ cs5.20_agent_linux_i386_packagedIU.zip coresvcs/linux/i386/ cs5.20.1_agent_linux_i386_packagedIU.zip
IBM Director Agent on Linux on POWER 5.20 IBM Director for AIX 5L, V5.20 IBM Director for Linux on POWER, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) CD Dir5.20_LinuxonPower.tar.gz 5.20.1 IBM Director for Linux on POWER, Version 5.20 Update 1 Dir5.20.1_Agent_Console_LinuxonPower.tar.gz IBM Director Core Services on Linux on POWER 5.20 IBM Director for Linux on POWER, V5.20 CD IBM Director Agents & Consoles, V5.20 (1 of 2) CD Dir5.20_LinuxonPower.tar.gz 5.20.1 IBM Director for Linux on POWER, Version 5.20 Update 1 Dir5.20.1_Agent_Console_LinuxonPower.tar.gz IBM Director Agent on Linux for System z 5.20 IBM Director for Linux on System z, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) 5.20.1 dir5.20.1_agent-agent-linux-s390.tar /director/agent/linux/s390/ dir5.20_agent_linux_s390_packagedIU.zip /director/agent/linux/s390/ dir5.20.1_agent_linux_s390_packagedIU.zip /coresvcs/agent/linux/ppc/ cs5.20.1_agent_linux_ppc_packagedIU.zip /coresvcs/agent/linux/ppc/ cs5.20_agent_linux_ppc_packagedIU.zip /director/agent/linux/ppc/ dir5.20.1_agent_linux_ppc_packagedIU.zip /director/agent/linux/ppc/ dir5.20_agent_linux_ppc_packagedIU.zip
IBM Director Core Services on Linux for System z 5.20 IBM Director for Linux on System z, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) /coresvcs/agent/linux/s390/ cs5.20_agent_linux_s390_packagedIU.zip
268
Table 106. Source and file names of files used to upgrade IBM Director Agent using Software Distribution (continued) Version 5.20.1 CD or downloaded installation package dir5.20.1_coreservices-agent-linux-s390.tar Path and file name of the software distribution package /coresvcs/agent/linux/s390/ cs5.20.1_agent_linux_s390_packagedIU.zip
z/VM CIM instrumentation 5.20 IBM Director for Linux on System z, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) 5.20.1 dir5.20.1_zvmmap-agent-linux-s390.tar director/zvmmapagent/s390/ dir5.20_zvmmapagent_linux_s390_packagedIU.zip director/zvmmapagent/s390/ dir5.20.1_zvmmapagent_linux_s390_packagedIU.zip
IBM Director Agent on Windows (32-bit) 5.20 IBM Director on x86, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) dir5.20_agent_windows.zip 5.20.1 IBM Director on x86, Version 5.20 Update 1 dir5.20.1_agent_windows.zip IBM Director Core Services on Windows 5.20 IBM Director on x86, V5.20 IBM Director Agents & Consoles, V5.20 (1 of 2) dir5.20_coreservices_windows.zip 5.20.1 IBM Director on x86, Version 5.20 Update 1 dir5.20.1_coreservices_windows.zip IBM Director Agent on 64-bit Intel Itanium Note: IBM Director 5.20 and higher support for Intel Itanium systems is provided by IBM Director Agent version 5.10.3. Linux Windows dir5.10.3_agent_linux64.tar dir5.10.3_agent_windows64.zip /META/INF/dir5.10.3_agent_linux64.xml \META-INF\dir5.10.3_agent_windows64.xml \coresvcs\agent\windows\i386\ cs5.20_agent_windows_i386_packagedIU.zip cs5.20_agent_windows_i386_packagedIU.zip \coresvcs\agent\windows\i386\ cs5.20.1_agent_windows_i386_packagedIU.zip cs5.20.1_agent_windows_i386_packagedIU.zip \director\agent\windows\i386\ dir5.20_agent_windows_packagedIU.zip dir5.20_agent_windows_packagedIU.zip \director\agent\windows\i386\ dir5.20.1_agent_windows_packagedIU.zip dir5.20.1_agent_windows_packagedIU.zip
Creating a software package: You can create a software package for installing or upgrading IBM Director Agent or installing IBM Director Core Services. To create a software package, complete the following steps:
269
1. Locate the installation or upgrade packages for IBM Director. See the IBM Director Planning, Installation and Configuration Guide for more information. 2. If you want to accept the default settings for the installation, go to step 3. Otherwise, copy the response file: use diragent.rsp for IBM Director Agent, or use coresvcs.rsp for IBM Director Core Services. Open the copy in an ASCII text editor and modify the response file as needed. Save the modified file with a new file name. 3. Start IBM Director Console. 4. In the Tasks pane, double-click Software Distribution. The Software Distribution Manager window opens.
5. If you have not installed IBM Director 5.20 Software Distribution Premium Edition, go to step 6. Otherwise, expand the Wizards tree. 6. Double-click IBM Update Assistant. The IBM Update Assistant window opens. 7. If you want to get files from the management server, click Get files from the Director server. By default, Get files from the local system is selected. 8. To select a file, click Browse. The IBM Update Package/Root Directory Location window opens. 9. Locate the appropriate XML file and click it. The name of the XML file is displayed in the File Name field.
270
Note: Use the correct XML file for your language. The correct file for English installations is the one without the language code, for example, dir5.20_agent_windows.xml. 10. Click OK. The IBM Update Assistant window reopens. 11. Click Next. The second IBM Update Assistant window opens. 12. To specify an alternative response file, click Browse and locate the file that you modified in step 2 on page 270. Note: If you do not specify an alternative response file, the package is installed with the default settings that are specified in the installation script. 13. Click Finish. As the package is processed, a status message is displayed at the bottom of the window. When the processing is completed, the software-distribution package is displayed in the Tasks pane of IBM Director Console. Installing a software package: After you create a software package, you can use the Software Distribution task to remotely install the package on supported systems. To use the Software Distribution task to install a software package, complete the following steps: 1. Start IBM Director Console. 2. In the Tasks pane, expand the Software Distribution task. 3. Click the software package that you want to distribute. Then, drag it into the Group Contents pane and drop it onto the icon that is displayed for the system on which you want to install the software package. A window opens. Note: To distribute software to several systems at once, you can drag the software package into the Groups pane and drop it onto the icon for the group. Alternatively, you can select multiple managed systems in the Group Contents pane. 4. When prompted with Do you wish to create a scheduled job for this task or execute immediately?, click Schedule or Execute Now. If you click Execute Now, the software package is distributed immediately. If you click Schedule, the New Scheduled Job window opens. 5. Schedule the job: a. In the Scheduled Job field, type a unique name for the job. This name is displayed in the Jobs pane of the Scheduler window. b. In the Date field, type the day you want the software package to be installed (in MM/DD/YYYY format). c. In the Time field, type the time you want the software package to be installed. For more information about the Scheduler task, see the IBM Director Systems Management Guide. 6. Click OK. The Save Job Confirmation window opens. 7. Click OK.
Migrating the CIMOM repository

When upgrading IBM Director Server, IBM Director Agent, or IBM Director Core Services on Linux on System z or Linux on POWER from release 5.10.1 or later to release 5.20 or later, you can migrate your the existing CIMOM repository.
271
Much of the CIMOM data is dynamically derived from the system on which the CIMOM runs and does not need migration. Migrate a CIMOM repository if you want to preserve the certificate or if you are using CIM instrumentation that maintains static data in the CIMOM repository. If you decide to perform a migration of the CIMOM repository, perform the migration immediately after the upgrade of your IBM Director component, to ensure that the migrated data is current. You can perform the migration either manually or automatically, as the final step of installing the new release. Note: v Always perform the migration manually if you want to include CIM instrumentation other than what is installed with IBM Director. v For migrating the CIMOM repository of a z/VM manageability access point, see the z/VM Center upgrade information in the IBM Director z/VM Center Installation and Users Guide. Complete the following step to automatically migrate the CIMOM repository during the installation of the new version of your IBM Director component: Perform a customized installation of IBM Director Server, IBM Director Agent, or IBM Director Core Services, with option CIMRepositoryUpgrade set to 1 in the response file. Complete the following steps to manually migrate the CIMOM repository after you have installed the new version of your IBM Director component and any additional CIM instrumentation you might require: 1. Ensure that CIMOM is shut down by entering the following command from a Linux terminal session:
/etc/initd./cimserverd stop
2. Change the directory to /opt/ibm/icc/cimom/bin 3. Start the migration process by entering the following command:
./repmigrate /opt/ibm/repository_old_backup.tar.gz
If the repmigrate script fails an automatic rollback is performed and the newly installed repository is restored. 4. Start CIMOM by entering the following command:
/etc/initd./cimserverd start
As part of the migration the new CIMOM repository is backed up. If a problem occurs during the migration, the new CIMOM repository is automatically restored to its state before the migration.
Updating IBM Director

Updates to IBM Director are issued periodically to resolve problems and limitations with the software, or to provide support for additional management servers or managed objects. IBM might offer new releases or updates to this version of IBM Director. v If you purchased IBM Director, see the IBM Director Web site at www.ibm.com/systems/management/director/ for information about new releases.
272
v If you received IBM Director with your IBM BladeCenter product or xSeries server, see your hardware documentation for information about updating IBM Director. Also, the IBM eServer xSeries Subscription Services, which allows you to receive updates automatically, is available; for more information about this service, contact your IBM representative.
Restoring IBM Director data

You can use the twgrestore command to restore saved data to IBM Director Server. You also can restore configuration data from one management server to another in order to replicate a management server. Important: The data that you restore must be from the same version of IBM Director Server, running on a management server with the same operating system. As a best practice, always back up your IBM Director Server before upgrading or making major changes to your management server. In the event that a complication occurs during an upgrade, if you have backed up your IBM Director data, you can revert to your previous version of IBM Director and restore your previous data. Important: If you use the twgrestore command to copy data to another management server, make sure that you select the switch to prevent the Server ID from being restored. Having duplicate Server IDs will cause problems. To restore IBM Director persistent data on the management server, complete the following steps: 1. Shut down IBM Director Server. Type one of the following commands, depending on the operating system of the management server:
Operating system AIX or Linux i5/OS Command install_root/bin/twgstop QSH CMD(/QIBM/ProdData/Director/bin/ twgstop) or ENDTCPSVR *DIRECTOR unload twgipc net stop twgipc
NetWare Windows
where install_root is the root directory of your IBM Director installation. 2. Optional: If you have an external database for IBM Director, restore the database using the instructions provided for your database. 3. Type the following command to restore the IBM Director persistent data.
twgrestore directory
where directory is the directory where the persistent data was backed up. The IBM Director persistent data is restored to the original file locations.
Initially configuring IBM Director

After completing the installation of IBM Director, make sure that you review and apply the configuration procedures that are applicable to your environment.
273
Configuring IBM Director after an Express installation

After completing an Express installation of IBM Director, you can use the Express Start wizard to configure the settings that are applicable to your environment. When you first start IBM Director Console after an Express installation on the management server, the Express Start wizard is started. You can use the Express Start wizard to set up your discovery preferences and to configure event action plans. To configure IBM Director Server using the Express Start wizard, complete the following steps: 1. After installing IBM Director Server using the Express installation option, open IBM Director Console on the management server. The Express Start wizard starts and the Discover window opens. Note: An IBM Director Server that is installed using the Express installation option, performs a broadcast discovery to discover Level-0, Level-1, and Level-2. 2. Optional: To prevent Level-0 managed systems from being discovered, clear the Discover Level 0: Agentless Systems check box. Note: If the Discover Level 0: Agentless Systems check box is not selected, Level-0 managed systems will not be discovered. IBM Director Server performs a Discover All and adds all managed objects other than those that are Level 0 only. Some Level 0 managed systems might display briefly in IBM Director Console during discovery. When the discovery process finishes discovering the IBM Director Agent and IBM Director Core Services software on these systems, the Level-0 managed systems disappear. Optional: To configure Level-0 discovery, complete the following steps: a. Make sure the Discover Level 0: Agentless Systems check box is selected. b. In the Starting IP Address and Ending IP Address fields, type the IP address range to use for the Level-0 discovery. Click OK. The initial discovery is performed and the Event Action Plan Wizard is displayed. On the Name page, type a descriptive name for the event action plan you are creating. Click Next. On the Systems page, choose the systems to which you want to apply the event-action plan. Select the managed objects in the left pane, and click Add to move them to the Selected pane. Click Next. On the Event Filters page, select the check boxes adjacent to the types of events you want to monitor.
3.
4. 5. 6. 7.
8. 9.
10. Click Next. 11. In the Event Action Plan Wizard, on the Actions page, choose the event actions that you want performed when an event occurs. If you want to be notified by e-mail when an event occurs, select the E-mail check box. Then, configure the e-mail notification: a. In the E-mail address field, type the e-mail address to which the notification will be sent. b. In the Reply-to address field, type the e-mail address that will be displayed in the reply-to field of the e-mail.
274
c. In the SMTP server field, type the host name or IP address of the Simple Mail Transfer Protocol (SMTP) server. d. In the SMTP port field, type the port number of the SMTP server. By default, the SMTP port is set to 25. e. In the Subject field, type the message that will be displayed in the subject-line of the e-mail. You can use variables such as &type and &system. For example, you might want to type the following string: IBM Director alert: &system &type. When the e-mail is generated, the name of the managed system is substituted for &system, and the type of event that occurred is substituted for &type. f. In the Body field, type the message that will be displayed in the body of the e-mail. You can use variables such as &text. For example, you might want to type the following string: &time &date &text. When the e-mail is generated, the body will contain the time and date the event occurred, as well as details about the event. The e-mail notification is configured. Note that &type, &system, &time, &date, and &text are event-data substitution variables. 12. If you want to start a program as a result of the event, select the Start program check box. Then configure the start program instructions. a. Select the location where the program should be started. b. Type the Host name of the selected system. c. Type the working directory of the program that needs to start. d. Type the Program name of the application that needs to start. Click Next. On the Time Range page, choose the period of time over which you want to collect the events. You can select All day to enable the plan to be active all the time. Or you can select Custom to choose the time range for the plan to be active during specific days of the week. Click Next. On the Summary page, verify the details of the event action plan. If you need to make changes, click < Back. Click Finish.
13. 14.
15. 16. 17.
Managing users and user groups for IBM Director

Superusers can perform user-administration tasks in IBM Director, including authorizing and deauthorizing user groups, and modifying access to tasks and managed objects for users and user groups. User and user group administration can only be performed by members of the superuser group. The name of the IBM Director superuser group is different on each supported operating system: v AIX or Linux: dirsuper v i5/OS: QIBM_QDIR_SUPER_ADM_PRIVILEGES (function usage group) v Windows: DirSuper IBM Director users are based on user accounts on the operating system of the management server or a Lightweight Directory Access Protocol (LDAP) server. User access to managed objects and tasks in IBM Director is based on user group membership, but individual user access authority can be granted or revoked in addition to the authority defined for the user group.
275
There are two general methodologies for changing user access to tasks and managed objects in IBM Director: configure user groups based on roles Strongly recommended for organizations where more than a few users are authorized for IBM Director, implementing a group policy means that user authority is exclusively defined by membership in user groups. You define user groups that correspond to roles for task and managed-object authority, and add or remove users from the appropriate user groups. This methodology has several advantages: v You can apply authority changes for multiple users at once by changing the authority for particular groups. v You can identify lists of users with particular authority based on their group membership. v You can remove user access by removing the user from all authorized user groups. modify individual users For organizations where only a few users are authorized for IBM Director, it can be simpler to manage users on an individual basis than to define authority exclusively by group membership. In practice, many organizations will probably employ a combination of these two methodologies. The following steps outline the general procedure for managing users and user groups in IBM Director. 1. LDAP authentication only: Enable LDAP authentication and configure the LDAP properties in IBM Director. 2. Create user groups on the management server or LDAP server that correspond to roles you have defined for IBM Director users, and authorize the user groups for IBM Director. 3. Modify authority for the user groups. 4. Create user accounts on the management server or LDAP server. 5. Add the user accounts to the appropriate user groups. 6. Optional: Modify authority for individual user accounts. To remove user access, remove the user account from all user groups which are authorized for IBM Director.
Enabling Lightweight Directory Access Protocol authentication for IBM Director users
IBM Director can authenticate user login requests against a Lightweight Directory Access Protocol (LDAP) server. 1. On the management server, open the dirldap.properties file for editing. The dirldap.properties file is in the following location: AIX, Linux, and Windows: install_root\data\dirldap.properties i5/OS: /QIBM/UserData/Director/data/dirldap.properties file, where install_root is the root directory of your IBM Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/).
276
2. Modify the ldap.host property to specify the LDAP server address. If the LDAP server is located on the management server itself, you can set this to localhost. Otherwise, this should specify the fully qualified name of the LDAP server. 3. Modify the ldap.port property to specify the port number to be used for LDAP authentication requests. By default, this is set to port 389. 4. Specify whether or not to use the Java Naming and Directory Interface (JNDI) provider. Modify the ldap.auth.jndi property according to the following table.
If this is true: IBM Director Server on i5/OS IBM Director Server on AIX, and not using Pluggable Authentication Module (PAM) authentication. IBM Director Server on Linux, and not using Pluggable Authentication Module (PAM) authentication. IBM Director Server on Windows, and using an LDAP server other than Active Directory. All other conditions. Set the ldap.auth.jndi property to: true true true true false
5. Specify the user attribute (dn or uid) that the LDAP server will use for user authentication according to the following table.
User attribute to be used uid The user ID specified when the LDAP user was created. The fully qualified distinguished name of the user. Properties to be set ldap.auth.userid.attribute=uid ldap.auth.userid.lookupUserDN=true ldap.auth.userid.attribute=dn
dn
6. Specify the LDAP authentication method being used by the LDAP server. Set the ldap.auth.mechanism property to one of the following values: simple anonymous DIGEST-MD5 7. Set the ldap.enabled property to true. You might have to add the ldap.enabled property to the dirldap.properties file. 8. Optional: Modify other properties in the dirldap.properties file as needed. These properties are described in Appendix C, Lightweight Directory Access Protocol authentication properties for IBM Director Server, on page 355. 9. Save and close the changed dirldap.properties file. 10. Stop and restart IBM Director Server. For IBM Director Server to use the new values, you must stop and restart IBM Director Server. Additional information about the dirldap.properties file, including example configurations for various authentication scenarios, are included in Lightweight Directory Access Protocol authentication properties for IBM Director Server.
Creating and authorizing user groups for IBM Director

When IBM Director Server is installed, two user groups are created on the operating system of the management server: an administrator group, and a
277
superuser group. If multiple people will be authorized to access IBM Director, you should create additional user groups in order to manage user authority in IBM Director. The names of the administrator and superuser groups are different on each supported operating system.
Operating system AIX or Linux i5/OS Windows Name of administrator group diradmin QIBM_QDIR_ADMINISTRATOR DirAdmin Name of superuser group dirsuper QIBM_QDIR_SUPER_ADM_PRIVILEGES DirSuper
Using only the default administrator and superuser groups poses the following possible security risks: v Because root users and Windows administrators have the same authority as the administrator group, adding authority to the administrator group could grant authority to users who do not need this authority. To better manage user authority in IBM Director, you should keep the default user authority for the administrator group (no task access, no managed object access). v Because members of the superuser group have unrestricted access to all tasks and managed objects in IBM Director, you should not add users to this group whose access should be restricted in some way. To manage user authority in IBM Director, therefore, you should create one or more user groups in addition to the administrator and superuser groups. Because individual user authority can be configured only for members of the administrator group, the user groups you create should correspond with a set of user authorities you wish to assign to members of the group. 1. These might be based on what kind of managed objects the user will manage, where the objects are located, or what tasks the user will be able to perform. 2. On the management server or on a Lightweight Directory Access Protocol (LDAP) server, create user groups that correspond to the user authority sets you need. Tip: Since all members of authorized user groups share authority in IBM Director, you should create user groups which are used only for IBM Director. One way to identify these groups is to use a common prefix in the group name. Refer to your operating system documentation, or the documentation for your LDAP server, for instructions on creating user groups. 3. Authorize the user groups for IBM Director. From a command line, issue the dircli authusrgp command. The syntax depends on whether the user group exists on the management server or on an LDAP server. v To authorize a user group that exists on the management server: Issue the following command from a command prompt.
dircli authusrgp name=groupname type=local
where groupname is the name of a user group on the management server. v To authorize a user group that exists on a Windows domain: Issue the following command from a command prompt.
dircli authusrgp name=groupname type=domain
where groupname is the name of a user group on the Windows domain.
278
v To authorize a user group that exists on an LDAP server: Issue the following command from a command prompt
dircli authusrgp name=groupname type=ldap optional_keys
where groupname is the name of a user group on the LDAP server, and optional_keys refers to optional LDAP keys described in the authusrgp reference. These keys can specify additional LDAP properties, such as the LDAP host name and port. These properties can also be configured in the dirldap.properties file. The user groups are created and are granted access to IBM Director, but initially the user groups have no authority to access managed objects or perform tasks. For example, you might create the following user groups to correspond with both managed-object access authority and task authority.
Groups corresponding to managed-object authority v ibmdir_albany v ibmdir_mumbai v ibmdir_timbuktu v ibmdir_storage_dev v ibmdir_aix_sys v ibmdir_windows_sys Groups corresponding to task authority v ibmdir_edit_prefs v ibmdir_dircli v ibmdir_remote_control v ibmdir_hardware_status
With authority correctly configured for these groups, you could authorize a user to check the hardware status of servers running AIX in Mumbai, India by adding that user to the groups ibmdir_mumbai, ibmdir_aix_sys, and ibmdir_hardware_status. After creating and authorizing user groups, you need to configure the authority for each user group, and then add users.
Changing authority for an IBM Director user group

After creating and authorizing a user group for IBM Director, you can modify the user groups access to tasks and managed objects with the dircli chusrgp command. There are two alternative procedures for changing user-group authority. Changing authority for a user group using the dircli chusrgp command: You can use the dircli chusrgp command at a command prompt on all management servers to modify the authority for authorized user groups. The following prerequisites apply to this task: v Only superusers or users granted user administration authority can perform this task. v The user group must exist on the management server or LDAP server, and must be authorized for IBM Director. v Because managed-object access authority is based on the managed-object groups you have defined in IBM Director, you might need to create additional managed-object groups that correspond to areas of responsibility for which you intend to assign authority.
279
v For user accounts on an LDAP server, you must have enabled LDAP authentication for IBM Director. Complete the following steps to edit authority for a group. 1. Optional: List the available privileges, managed-object groups, and tasks. To add or deny privileges or access to managed-object groups or tasks, you need to know the correct name or identifier for the privilege, managed-object group, or task. a. To list the privileges which can be assigned to a user group, issue the following command:
dircli lspriv -l -o
b. To list all IBM Director managed-object groups, issue the following command:
dircli lsgp -o
c. To list all IBM Director tasks, issue the following command:

dircli lstask -o
Note: The results from each of these commands include both the name and the hexadecimal identifier of the privileges, managed-object groups, or tasks. You can use either the name or hexadecimal identifier when granting or denying access by the user group. 2. Optional: To list the authorized user groups, issue the following command:
dircli lsusrgp
3. To edit privileges for a user group, issue the following command:

dircli chusrgp -P privilege_list -N mo_group_list -T task_list usergroup
where: v privilege_list is a comma-delimited list of privileges which are assigned to members of the user group. v mo_group_list is a comma-delimited list of managed-object groups which members of the the user group can access. v task_list is a comma-delimited list of tasks which members of the user group can perform. v usergroup is the user group you are editing. Notes: a. If the name of a task, managed-object group, or privilege includes a space character, you must enclose the name in quotation marks. b. You can use the keywords all or none, in place of a list of privileges, managed-object groups, or tasks, to specify all or none of the available privileges, managed-object groups, or tasks. Examples Two examples of editing user groups using the dircli chusrgp command follow. The following command modifies the user group named hr_users to v grant user administration privileges; v deny managed-object access; and v grant access to the Launch Command Line Interface and User Administration tasks.
280
dircli chusrgp -P engine.useradmin -N none -T "Launch Command Line Interface","User Administration" hr_users
The following command modifies the user group named ibmdir_tokyo_admins to v grant all privileges; v grant access to managed objects in the Tokyo devices managed-objects group; and v grant access to all tasks.
dircli chusrgp -P all -N "Tokyo devices" -T all ibmdir_tokyo_admins
Changing authority for a user group using IBM Director Console on Windows: For management servers running Windows, you can use IBM Director Console to modify a user groups access to tasks and managed objects. The following prerequisites apply to this task: v Only superusers or users granted user administration authority can perform this task. v The user group must exist on the management server or LDAP server, and must be authorized for IBM Director. v Because managed-object access authority is based on the managed-object groups you have defined in IBM Director, you might need to create additional managed-object groups that correspond to areas of responsibility for which you intend to assign authority. v For user accounts on an LDAP server, you must have enabled LDAP authentication for IBM Director. 1. In IBM Director Console, click Options User Administration. The User Administration window lists all users and groups that are authorized to access IBM Director. 2. In the User Administration window, click the Groups tab. 3. Select the group whose access authority you want to modify. Click Actions Group Edit. 4. In the Group Editor window, click the Privileges tab to modify privileges for the user group. a. To add a privilege, click the privilege in the Unassigned Privileges pane and then click Add. b. To remove a privilege, click the privilege in the privileges Granted to User pane and then click Remove. 5. In the Group Editor window, click the Group Access tab to modify managed-object access for the user group. a. To allow full access to all managed objects, clear the Limit user access only to the groups listed check box and the Limit user to read-only access of groups check box. b. To allow access to all managed objects and prevent users in the user group from adding or changing managed-object groups, clear the Limit user access only to the groups listed check box, and select the Limit user to read-only access of groups check box.
281
c. To allow access only to specified managed-object groups and prevent users in the user group from adding or changing managed-object groups, select the Limit user access only to the groups listed check box. To add access to a managed-object group, click the group in the Available Groups pane and click Add. To remove access to a managed-object group, click the group in the Groups User Can Access pane and click Remove. 6. In the Group Editor window, click the Task Access tab to modify task access for the user group. a. To allow full access to all tasks, clear the Limit user access only to the tasks selected check box. b. To allow access only to specified tasks, select the Limit user access only to the tasks selected check box. To allow access to a task, select its check box in the Tasks User Can Access list. To remove access to a task, clear its check box in the Tasks User Can Access list. To prevent users in the user group from accessing tasks which they create, select the Deny user access to new tasks created by this user check box. Note: This does not prevent users from creating new tasks, if they are otherwise authorized to do so. 7. When you have finished editing the authority, click OK in the Group Editor window, and then close the User Administration window.
Adding new users in IBM Director

You can create new users for IBM Director Server by adding user accounts on the operating system of the management server, or by adding users to a Lightweight Directory Access Protocol (LDAP) server. The following prerequisites apply to this task: v Only superusers or users granted user administration authority can perform this task. v One or more user groups must exist on the management server or LDAP server, and must be authorized for IBM Director. v For user accounts on an LDAP server, you must have enabled LDAP authentication for IBM Director. The general procedure for adding new users in IBM Director is the same for all operating systems and for authentication using an LDAP server: 1. Create the user account on the operating system or on an LDAP server. 2. Add the user account to a user group that is authorized to access IBM Director Server. Because user authority in IBM Director is determined by user group membership, the user should be made a member of user groups for which the needed authority is configured. Refer to your operating system documentation, or the documentation for your LDAP server, for instructions on creating user accounts and adding them to user groups.
282
Authorizing IBM Director users on a management server running i5/OS

To sign on to an i5/OS management server from IBM Director Console, the user must be authorized. Two methods of user authentication are supported for IBM Director: LDAP and local authentication on the management server. To use local authentication, a user must have a user profile on that i5/OS management server. In addition, the user must be registered in either the QIBM_QDIR_ADMINISTRATOR function usage group or the QIBM_QDIR_SUPER_ADM_PRIVILEGES function usage group. To authorize users, you must have the following authority: v Security administrator (*SECADM) special authority. v Use (*USE) authority to the initial program, initial menu, job description, message queue, output queue, and attention-key-handling program (if specified). v Change (*CHANGE) and object management (*OBJMGT) authorities to the group profile and supplemental group profiles (if specified). v If you are using iSeries Navigator, you must have Application Administration and Management Central installed. This procedure can be performed in the i5/OS character-based user interface, or using iSeries Navigator on a system that has connectivity to the i5/OS management server. Authorize each user profile to the function usage groups that correspond to the authority needed for the user role. v In the i5/OS user interface: Type the following command:
CHGFCNUSG FCNID(functionid) USER(name) USAGE(*ALLOWED)
where functionid is one of the function usage groups listed in Table 107 on page 284, and name is the name of the user profile to be authorized. Note: Typically, user profiles are authorized to either the QIBM_QDIR_ADMINISTRATOR or the QIBM_QDIR_SUPER_ADM_PRIVILEGES function usage groups. You can repeat this command to authorize the user profile for additional function usage groups. v In iSeries Navigator: Complete the following steps: 1. In iSeries Navigator, right-click the management server and click Application Administration. 2. On the Application Administration window, click the Host Applications tab. 3. Expand IBM Director for iSeries. 4. Select one of the function usage groups listed in Table 107 on page 284, and click Customize. Note: Typically, user profiles are authorized to either the QIBM_QDIR_ADMINISTRATOR or the QIBM_QDIR_SUPER_ADM_PRIVILEGES function usage groups. You can authorize the user profile for additional function usage groups. 5. In the Customize Access window, select the user profile and then click Add to add the group to the Access Allowed list. 6. Click OK to close the Customize Access window. 7. Click OK to close the Application Administration window.
283
Note: IBM Director is shipped with the user profile QCPMGTDIR. This profile has *ALLOBJ, *IOSYSCFG, *JOBCTL, *SAVSYS and *SECADM special authorities, is used to start all IBM Director jobs, and is the default profile under which the jobs run. QCPMGTDIR is the default user profile for the following function usage groups: v QIBM_QDIR_AGENT_DEFAULT_USER v QIBM_QDIR_SERVER_DEFAULT_USER v QIBM_QDIR_AGENT_RUN_AS_USER (only on Level-2 managed systems with IBM Director Agent installed) v QIBM_QDIR_SERVER_RUN_AS_USER If these function usage groups are changed to a user profile other than QCPMGTDIR, any tasks that require more authority than the user profile that is specified will fail. Also, if you change the IBM Director Agent default user, anonymous command execution can occur on the given i5/OS managed system.
Table 107. Default IBM Director function usage groups for i5/OS Installed IBM Director component IBM Director Server, IBM Director Agent Function ID (function name) QIBM_QDIR_AGENT_ACCESS (IBM Director Agent access) Purpose Users in this group can request access from IBM Director Server to a managed system that is running IBM Director Agent. Note: By default, any user with *ALLOBJ authority has access to this function. QCPMGTDIR is the default user profile for this function ID. By specifying a user profile other than the default profile, the user can issue remote commands on a managed system using the specified user profile. No user ID and password are required when requesting the command. QCPMGTDIR is the default user profile for this function ID. By specifying a user profile other than the default profile, the user performs jobs on the managed system under this profile. To complete all IBM Director tasks successfully, the user profile must have *ALLOBJ authority. QCPMGTDIR is the default user profile for this function ID. By specifying a user profile other than the default profile, the user runs tasks such as file transfer, software distribution, and event actions under the profile you specify. To complete all IBM Director tasks successfully, the user profile must have *ALLOBJ authority. QCPMGTDIR is the default user profile for this function ID. By specifying a user profile other than the default profile, the user performs jobs on the management server under this profile. To complete all IBM Director tasks successfully, the user profile must have *ALLOBJ and *SECADM authority.
IBM Director Server, IBM Director Agent
QIBM_QDIR_AGENT_DEFAULT_USER (IBM Director Agent default user)
IBM Director Agent
QIBM_QDIR_AGENT_RUN_AS_USER (IBM Director Agent run as user )
IBM Director Server
QIBM_QDIR_SERVER_DEFAULT_USER (IBM Director Server default user )
IBM Director Server
QIBM_QDIR_SERVER_RUN_AS_USER (IBM Director Server run as user )
284
Table 107. Default IBM Director function usage groups for i5/OS (continued) Installed IBM Director component IBM Director Server Function ID (function name) QIBM_QDIR_ADMINISTRATOR (IBM Director Administrators) Purpose By default, members of this group have authority to sign on to IBM Director Server using IBM Director Console, but have access to no IBM Director managed objects and no tasks except for Message Browser. This authority can be modified by a member of the QIBM_QDIR_SUPER_ADM_PRIVILEGES group using the User Administration task in IBM Director Console. Members of this group have access to all IBM Director managed objects and all tasks, including user and group administration. The authority available to members of the QIBM_QDIR_SUPER_ADM_PRIVILEGES group cannot be restricted.
IBM Director Server
QIBM_QDIR_SUPER_ADM_PRIVILEGES (IBM Director Super Administrators)
Related information Accessing a secured managed system in the IBM Director Information Center Create a group profile in the iSeries Information Center Create User Profile (CRTUSRPRF) in the iSeries Information Center iSeries Navigator in the iSeries Information Center
Changing authority for an IBM Director user

Usually, you will grant authority to IBM Director users by configuring the authority of user groups and adding the user to the appropriate user groups. However, for members of the IBM Director administrator group, you can also configure an individual users access authority to IBM Director functions, managed-object groups, and tasks. There are two alternative procedures for changing authority for a member of the IBM Director administrator group. Changing authority for a member of the administrator group using the dircli chusr command: You can use the dircli chusr command at a command prompt on all management servers to modify the authority for a member of the IBM Director administrator group. Important: This task can only be performed for user accounts that are members of the IBM Director administrator group. The name of the administrator group is different on each supported operating system: v AIX or Linux: diradmin v i5/OS: QIBM_QDIR_ADMINISTRATOR v Windows: DirAdmin For other users, the available privileges, tasks, and managed-object groups are determined exclusively by the user groups of which the user is a member.
285
The following prerequisites apply to this task: v Only superusers or users granted user administration authority can perform this task. v The user account must exist on the management server or LDAP server, and must be a member of a user group authorized for IBM Director. v Because managed-object access authority is based on the managed-object groups you have defined in IBM Director, you might need to create additional managed-object groups that correspond to areas of responsibility for which you intend to assign authority. v For user accounts on an LDAP server, you must have enabled LDAP authentication for IBM Director. Complete the following steps to edit authority for an individual user. 1. Optional: List the available privileges, managed-object groups, and tasks. To add or deny privileges or access to managed-object groups or tasks, you need to know the correct name or identifier for the privilege, managed-object group, or task. a. To list the privileges which can be assigned to a user group, issue the following command:
dircli lspriv -l -o
b. To list all IBM Director managed-object groups, issue the following command:
dircli lsgp -o
c. To list all IBM Director tasks, issue the following command:

dircli lstask -o
Note: The results from each of these commands include both the name and the hexadecimal identifier of the privileges, managed-object groups, or tasks. You can use either the name or hexadecimal identifier when granting or denying access by the user group. 2. Optional: To list user accounts that are members of the IBM Director administrator group, issue the following command:
dircli lsusr
3. To edit authority for a user, issue the following command:

dircli chusr -P privilege_list -N mo_group_list -T task_list user
where: v privilege_list is a comma-delimited list of privileges which are assigned to the user. v mo_group_list is a comma-delimited list of managed-object groups which the user can access. v task_list is a comma-delimited list of tasks which the user can perform. v user is the user you are editing. Notes: a. If the name of a task, managed-object group, or privilege includes a space character, you must enclose the name in quotation marks. b. You can use the keywords all or none, in place of a list of privileges, managed-object groups, or tasks, to specify all or none of the available privileges, managed-object groups, or tasks. Examples
286
Changing authority for a member of the administrator group using IBM Director Console on Windows: For management servers running Windows, you can use IBM Director Console to modify a users access to tasks and managed objects. Important: This task can only be performed for user accounts that are members of the IBM Director administrator group. The name of the administrator group is different on each supported operating system: v AIX or Linux: diradmin v i5/OS: QIBM_QDIR_ADMINISTRATOR v Windows: DirAdmin For other users, the available privileges, tasks, and managed-object groups are determined exclusively by the user groups of which the user is a member. The following prerequisites apply to this task: v Only superusers or users granted user administration authority can perform this task. v The user account must exist on the management server or LDAP server, and must be a member of a user group authorized for IBM Director. v Because managed-object access authority is based on the managed-object groups you have defined in IBM Director, you might need to create additional managed-object groups that correspond to areas of responsibility for which you intend to assign authority. v For user accounts on an LDAP server, you must have enabled LDAP authentication for IBM Director. 1. In IBM Director Console, click Options User Administration. The User Administration window lists all users and groups for which authority can be changed. 2. In the User Administration window, click the Users tab. 3. Select the user whose access authority you want to modify. Click Actions User Edit. 4. Optional: In the User Editor window, click the User Properties tab to change the e-mail address and pager number for the user. In the EMail Address and Pager Information fields, add the users e-mail address and pager number. 5. Click the Privileges tab to modify privileges for the user. a. To add a privilege, click the privilege in the Unassigned Privileges pane and then click Add. b. To remove a privilege, click the privilege in the privileges Granted to User pane and then click Remove. 6. Click the Group Access tab to modify managed-object access for the user. a. To allow full access to all managed objects, clear the Limit user access only to the groups listed check box and the Limit user to read-only access of groups check box. b. To allow access to all managed objects and prevent the user from adding or changing managed-object groups, clear the Limit user access only to the groups listed check box, and select the Limit user to read-only access of groups check box. c. To allow access only to specified managed-object groups and prevent the user from adding or changing managed-object groups, select the Limit user access only to the groups listed check box.
287
To add access to a managed-object group, click the group in the Unassigned Groups pane and click Add. To remove access to a managed-object group, click the group in the Groups User Can Access pane and click Remove. 7. Click the Task Access tab to modify task access for the user. a. To allow full access to all tasks, clear the Limit user access only to the tasks selected check box. b. To allow access only to specified tasks, select the Limit user access only to the tasks selected check box. To allow access to a task, select its check box in the Tasks User Can Access tree. You can expand the tree to select available subtasks. To remove access to a task, clear its check box in the Tasks User Can Access tree. You can expand the tree to clear available subtasks. Note: To select or clear the Event Action Plan Wizard task, expand Event Action Plans Event Action Plan Builder Event Action Plan Wizard. To prevent the user from accessing tasks that the user has created, select the Deny user access to new tasks created by this user check box. Note: This does not prevent users from creating new tasks, if they are otherwise authorized to do so. 8. When you have finished editing the authority, click OK in the User Editor window, and then close the User Administration window.
Listing authorized IBM Director user groups

You can list the identifiers and attributes of user groups authorized for a particular instance of IBM Director Server. v To list all user groups with no attribute information, issue the following command from a command prompt.
dircli lsusrgp
v To list details for a particular user group specified by user_group, issue the following command from a command prompt.
dircli lsusrgp -l user_group
Listing members of the IBM Director administrator group

You can list the identifiers and attributes of users that are members of the administrator group for a particular instance of IBM Director Server. Important: This task can only be performed for user accounts that are members of the IBM Director administrator group. The name of the administrator group is different on each supported operating system: v AIX or Linux: diradmin v i5/OS: QIBM_QDIR_ADMINISTRATOR v Windows: DirAdmin Root users and Windows administrators have the same privileges as the administrator group, whether or not the user actually belongs to this group. To list other authorized IBM Director users, list the user groups which are authorized for IBM Director, and then use the commands provided by the operating system for listing the members of those user groups. v To list all users that are members of the administrator group with no attribute information, issue the following command from a command prompt.
288
dircli lsusr
v To list details for a particular user specified by user_id, issue the following command from a command prompt.
dircli lsusr -l user_id
Listing available privileges for IBM Director users and user groups
To list the available privileges in IBM Director, issue the following command from a command prompt.
dircli lspriv -l -o
The privileges are listed with descriptions and hexadecimal IDs.
Deauthorizing IBM Director users

You can remove a users authority to access IBM Director by removing the user account from all managed-object groups that are authorized to access IBM Director. The following prerequisites apply to this task: v Only superusers or users granted user administration authority can perform this task. v One or more user groups must exist on the management server or LDAP server, and must be authorized for IBM Director. v For user accounts on an LDAP server, you must have enabled LDAP authentication for IBM Director. The general procedure for deauthorizing users in IBM Director is the reverse of the procedure for adding users: 1. Remove the user account from all user groups that are authorized to access IBM Director Server. Refer to your operating system documentation, or the documentation for your LDAP server, for instructions on deleting user groups. Note: Root users and Windows administrators will continue to have the same authority in IBM Director as members of the IBM Director administrators group. 2. To deauthorize a root user or Windows administrator, you must also remove the user account on the operating system on which the account is defined. Optionally, you can also remove user accounts for deauthorized IBM Director users that are not root users or Windows administrators. Refer to your operating system documentation, or the documentation for your LDAP server, for instructions on deleting user accounts.
Deauthorizing IBM Director user groups

You can deauthorize an IBM Director user group to remove the authority granted to users in that user group. If users are members of other user groups that are authorized to access IBM Director, the users will retain the authority granted them by the other user groups. 1. From a command line, issue the following command.
dircli rmusrgp group_name
where group_name is the name or hexadecimal identifier of a user group authorized to access IBM Director. The syntax is the same regardless of whether the user group exists on the management server, a Windows domain, or an LDAP server.
289
2. Optional: Delete the user group on the management server or LDAP server where it is defined. Refer to your operating system documentation, or the documentation for your LDAP server, for instructions on deleting user groups.
Changing the default authority for users in the IBM Director administrators group
For user accounts that are members of the IBM Director administrators group, individual authority for IBM Director privileges, tasks, and managed objects can be configured. Use this procedure to set the default authority for members of this group. You can change the default authority for IBM Director user IDs in the administrators group. The User Defaults Editor allows you to change the user privileges, group access limits, and task access limits for all members of the administrators group. These defaults affect only members of the administrators group; they do not limit the attributes of members of the super administrators group. Note: Authority that is set for a specific user or group overrides defaults that are set in the User Defaults Editor. A superuser can use the User Defaults Editor to set the default access to privileges, groups, and tasks for members of the administrators group. Until a superuser grants the administrators authority, they have no authority. If a superuser sets user defaults, all of the users in the administrator group, as well as any users that are added to the administrator group in the future, are automatically granted the default authority that has been assigned by the superuser. Note: Authority that is set for a specific user or group override defaults that are set in the User Defaults Editor. Complete the following steps to change the defaults for IBM Director user IDs that are members of the administrators group: 1. In IBM Director Console, click Options User Administration. 2. In the User Administration window, click Actions User defaults. Note: For increased security, consider providing no default access authority. You will have to set access levels for each user, but you can be sure that a user will not accidentally be able to access restricted groups or tasks. 3. Click the Privileges tab to modify privileges for the user. a. To add a privilege, click the privilege in the Unassigned Privileges pane and then click Add. b. To remove a privilege, click the privilege in the privileges Granted to User pane and then click Remove. 4. Click the Group Access tab to modify managed-object access for the user. a. To allow full access to all managed objects, clear the Limit user access only to the groups listed check box and the Limit user to read-only access of groups check box. b. To allow access to all managed objects and prevent the user from adding or changing managed-object groups, clear the Limit user access only to the groups listed check box, and select the Limit user to read-only access of groups check box.
290
c. To allow access only to specified managed-object groups and prevent the user from adding or changing managed-object groups, select the Limit user access only to the groups listed check box. To add access to a managed-object group, click the group in the Unassigned Groups pane and click Add. To remove access to a managed-object group, click the group in the Groups User Can Access pane and click Remove. 5. Click the Task Access tab to modify task access for the user. a. To allow full access to all tasks, clear the Limit user access only to the tasks selected check box. b. To allow access only to specified tasks, select the Limit user access only to the tasks selected check box. To allow access to a task, select its check box in the Tasks User Can Access tree. You can expand the tree to select available subtasks. To remove access to a task, clear its check box in the Tasks User Can Access tree. You can expand the tree to clear available subtasks. Note: To select or clear the Event Action Plan Wizard task, expand Event Action Plans Event Action Plan Builder Event Action Plan Wizard. To prevent the user from accessing tasks that the user has created, select the Deny user access to new tasks created by this user check box. Note: This does not prevent users from creating new tasks, if they are otherwise authorized to do so. 6. When you have finished editing the authority, click OK in the User Defaults Editor window, and then close the User Administration window.
Authorizing Request Access on a managed system

When you use root to request access to a managed system that is running VMware 3.0 or later, OpenSSH on the managed system must be configured to permit remote users to log in as root. To configure a managed system to enable remote users to log in as root, complete the following steps: 1. On the managed system, change to the directory in which the OpenSSH configuration file (sshd_config) is located. Type the following command and press Enter:
cd /etc/ssh/
2. Use an ASCII text editor to open the sshd_config file and change the PermitRootLogin parameter to yes . 3. Save the modified sshd_config file. 4. Restart the managed system.
Using IBM Director in a high-availability environment

If IBM Director will be used in a high-availability environment, you need to prepare the environment for IBM Director, and you might need to configure IBM Director properties for running in high-availability environments. Note: A high-availability application is required for implementation of IBM Director high-availability configuration.
291
For management servers running Linux, you might consider using IBM Tivoli System Automation for Multiplatforms. For management servers running Windows, you might consider using SteelEyes LifeKeeper.
Preparing a high-availability environment for IBM Director and IBM Tivoli System Automation for Multiplatforms
In order for IBM Director to provide high availability with IBM Tivoli System Automation for Multiplatforms, you must configure the IBM Director Server installation environment. Note: Customers who are not familiar with IBM Tivoli System Automation for Multiplatforms should read the Introduction and Getting started chapters of the IBM Tivoli System Automation for Multiplatforms Base Component Administrators and Users Guide. These chapters include a policy example which is similar to the configuration required for IBM Director. This guide and other documentation for IBM Tivoli System Automation for Multiplatforms can be downloaded from http://publib.boulder.ibm.com/tividd/td/ IBMTivoliSystemAutomationforMultiplatforms2.2.html. 1. Configure two management servers on which to install IBM Director Server. v Both servers should have synchronized passwords and user IDs, possibly via an authentication service such as LDAP or Active Directory. v Both servers should have identical NIC configurations. 2. Define a single floating IP address to use as the IP for IBM Director Server. 3. Install IBM Director Server on both management servers. When installing IBM Director Server, specify the following configuration: v IBM Director Server must use the same floating IP address on both management servers. v IBM Director Server should use a remote database (not Apache Derby). This database should be configured for high availability as described in the database documentation. 4. Make the IBM Director Server data directory highly available. There are numerous ways to do this, and you should use the method that is best for your installation. The following methods are suggested:
292
Method
Steps
Create a network 1. Create a network share. share to use as 2. Use IBM Tivoli System Automation to create an active/stand-by the IBM Director cluster for the system exporting the network share to ensure it is Server data not a single point of failure. directory. 3. Make the disk highly available using RAID or another mirroring technique, such as Peer-to-Peer Remote Copy (PPRC) or Distributed Replicated Block Device (DRBD). 4. Copy the contents of install_root\data from one of the management servers to the network share, where install_root is the root directory of your IBM Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). 5. Mount the network share to install_root\data on both management servers, where install_root is the root directory of your IBM Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). Use a cluster file system that is backed by a RAID and share the file system on both management servers. 1. Make a shared disk device available to both management servers. 2. Install and configure a cluster file system such as Oracle Cluster File System 2 (OCFS2) or Red Hats Global File System (GFS). 3. Create a cluster file system on the shared disk device. 4. Copy the contents of install_root\data from one of the management servers to the cluster file system on the shared disk device, where install_root is the root directory of your IBM Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). 5. Mount the cluster file system to install_root\data on both management servers, where install_root is the root directory of your IBM Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). 6. Verify that the file system will mount properly if the system is restarted.
5. Copy the \highavail\sa\directorsa script from the IBM Director installation media to the location for control scripts on your cluster. Alternatively, copy the \highavail\sa\directorsa script from the IBM Director installation media to install_root\bin on all systems in the cluster, where install_root is the root directory of your IBM Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). 6. Copy the \highavail\sa\dir_sa_setup script from the IBM Director installation media to a directory on the management server. Open the script in a text editor, modify the values specified in the script commands to work with your configuration, and then save the modified dir_sa_setup script. 7. Run the dir_sa_setup script to begin controlling IBM Director with IBMTivoli System Automation for Multiplatforms. Related information
293
Documentation for IBM Tivoli System Automation for Multiplatforms at publib.boulder.ibm.com/tividd/td/ IBMTivoliSystemAutomationforMultiplatforms2.2.html
Preparing a high-availability environment for IBM Director and SteelEyes LifeKeeper

In order for IBM Director to provide high availability with SteelEyes LifeKeeper, you must configure the IBM Director Server installation environment. 1. Configure two management servers on which to install IBM Director Server. v Both servers should have synchronized passwords and user IDs, possibly via an authentication service such as LDAP or Active Directory. v Both servers should have identical NIC configurations. 2. Define a single floating IP address to use as the IP for IBM Director Server. 3. Install IBM Director Server on both management servers. When installing IBM Director Server, specify the following configuration: v IBM Director Server must use the same floating IP address on both management servers. v IBM Director Server should use a remote database (not Apache Derby). This database should be configured for high availability as described in the database documentation. It should not be necessary to manually configure a network share, because LifeKeeper configures its own mirrored share between the management servers. If needed, see step 4 on page 292 in Preparing a high-availability environment for IBM Director and IBM Tivoli System Automation for Multiplatforms on page 292.
Configuring IBM Director for a high-availability environment

If IBM Director will be installed with a high-availability system (such as IBM Tivoli System Automation for Multiplatforms or SteelEyes LifeKeeper), you can configure high-availability properties for IBM Director. Normally, the default IBM Director configuration provides an acceptable balance between reliability and performance. In some situations, some intermediate data might be lost, but performance is not adversely affected by near-constant logging of events to disk. However, you can choose to improve reliability in high-availability environments, at the cost of decreased performance, particularly with regard to event processing. With IBM Director configured for high-availability environments, very little data is likely to be lost because of unexpected failovers, but performance might be negatively impacted by logging events to disk and increased redundancy in disk write operations. Enabling the high-availability configuration also enables some tasks, such as Inventory, to save checkpoints while they are running; if a failover occurs, the task continues from the last saved checkpoint rather than starting from the beginning.
294
This tradeoff is summarized in the following table.

Configuration Benefit Cost Loss of data on failover. Incomplete tasks restart from beginning. Decreased performance.
High-availability not enabled Improved performance. (default configuration).
High-availability enabled.
Minimal loss of data on failover. Incomplete tasks continue from last saved checkpoint.
To configure IBM Director Server for a high-availability environment, complete the following steps: 1. On the management server, open the TWGServer.prop file in a text editor.
Operating system AIX, Linux, and Windows Command Using an ASCII text editor, open the install_root\data\ softwaredist\TWGServer.prop file, where install_root is the root directory of your IBM Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). Using an ASCII text editor, open the /QIBM/UserData/ Director/data/softwaredist/TWGServer.prop file.
i5/OS
2. To enable high-availability configuration for IBM Director, add the following line to the TWGServer.prop file:
HA.enabled = true
If this line is not present, the default value is false. For most environments, you can skip to step 6 on page 296. 3. Optional: To change the event server shutdown delay time, add the following line to the TWGServer.prop file:
HA.events.shutdowndelay = seconds
where seconds is the number of seconds that the event server will delay server shutdown to make sure all events are flushed. If no value is specified, the event server delays 10 seconds. Note: Do not change this value unless the default value does not work correctly in your environment. 4. Optional: To prevent the persistent store from using dual datastores, add the following line to the TWGServer.prop file:
HA.store.backup = false
When HA.enabled is true, the persistent store will alternate writes between two datastores to keep the data current. To force the persistent store to use a single datastore only, specify HA.store.backup = false. When HA.enabled is false, the default value of HA.store.backup is false. Note: Do not change this value unless the default value does not work correctly in your environment.
295
5. Save and close the TWGServer.prop file. 6. Stop and restart IBM Director Server. Type the commands to stop and restart IBM Director Server for your operating system.
Operating system AIX or Linux i5/OS NetWare Windows Commands install_root/bin/twgstop install_root/bin/twgstart QSH CMD(/QIBM/ProdData/Director/bin/twgstop) QSH CMD(/QIBM/ProdData/Director/bin/twgstart) unload twgipc load twgipc net stop twgipc net start twgipc
where install_root is the root directory of your IBM Director installation.
Configuring discovery preferences

This topic describes how to configure discovery preferences. By default, IBM Director Server automatically discovers all managed systems that are on the same subnet as the management server. If you want to manage systems that are on a different subnet, you must configure discovery preferences.
Configuring discovery preferences for BladeCenter chassis

To discover BladeCenter chassis, you must configure IBM Director Server. The management server and the BladeCenter chassis must be connected to the network and on the same subnet. One of the following conditions must also be true: v The network contains a Dynamic Host Configuration Protocol (DHCP) server that has assigned an IP address to the management module. v The default IP address of the management module has been changed to a valid IP address on the same subnet as the management server. If these conditions are not met, you must discover the BladeCenter chassis manually. IBM Director Server uses Service Location Protocol (SLP) to communicate out-of-band with the BladeCenter chassis. This communication occurs through the external Ethernet port on the BladeCenter management module. When the BladeCenter management module first is started, the management module attempts to acquire an IP address for the external management port using DHCP. If this attempt fails, the BladeCenter management module assigns an IP address (192.168.70.125) to the external management port. Note: If you do not use a DHCP server to assign a temporary IP address to the BladeCenter chassis, introduce only one BladeCenter chassis onto the network at a time. IBM Director must discover and configure the chassis before another chassis is added to the LAN. Otherwise, an IP address conflict will occur. Complete the following steps to configure discovery preferences for BladeCenter chassis: 1. In IBM Director Console, click Options Discovery Preferences. 2. Click the BladeCenter Chassis tab.
296
3. Specify how often IBM Director Server will attempt to discover new managed systems. Select one of the available values for Auto-discover period (hours).
Option Disabled 1 - 168 Description IBM Director Server does not automatically discover managed systems. This value is the default. IBM Director Server automatically discovers managed systems every n hours, where n is the selected number.
4. Specify how often IBM Director Server checks the online status of each managed object. Select one of the available values for Presence Check period (minutes).
Option Disabled 1 - 240 Description IBM Director Server does not check the online status of managed objects of this type. IBM Director Server attempts to contact managed objects of this type every n minutes, where n is the selected number. The default value is 15.
5. Specify a template for naming BladeCenter chassis that IBM Director Server discovers.
To perform this action: Add a predefined parameter Complete these steps: 1. In the Selected Parameters list, click the parameter after which you would like to add a new parameter. 2. In the Available Parameters list, click the parameter you want to add. 3. Click Add. Add space between parameters 1. In the Selected Parameters list, click the parameter after which you would like to add a space. 2. In the Available Parameters list, click Insert a space. 3. Click Add. Add custom text 1. In the Selected Parameters list, click the parameter after which you would like to add your text. 2. In the Available Parameters list, click Insert additional text. 3. Click Add. 4. Type the text you want to add. 5. Click OK. Delete a parameter 1. In the Selected Parameters list, click the parameter you want to delete. 2. Click Remove. Restore parameters to Select the Reset to default value check box. If prompted, click Yes. the default values
The following parameters are available, as well as custom text and spaces: v %CHASSIS_MACHINE_TYPE_MODEL% v %CHASSIS_SERIAL_NUMBER% v %CHASSIS_FRU% v %MM_NAME%
297
v %MM_SERIAL_NUMBER% v %MM_IP_ADDRESS% By default, this naming template is set to the following value: IBM %CHASSIS_MACHINE_TYPE_MODEL% %CHASSIS_SERIAL_NUMBER% 6. To use the naming template during discovery, select Use during discovery. 7. Click OK. 8. Optional: To start discovery of BladeCenter chassis now, click Tasks Discover BladeCenter Chassis. Otherwise, IBM Director Server will automatically discover the BladeCenter chassis periodically as configured in the Discovery Preferences window. Note: Discovery is a background process; you will not see any confirmation that discovery is occurring until managed objects are displayed in IBM Director Console. Discovery of managed systems can take minutes or hours, depending on a number of factors, including the number of IP addresses being queried, the availability of the target networks, the presence check interval that is set for managed systems, and other operations being performed on the management server. To increase the speed of discovery operations, try reducing the number of IP addresses being queried in multicast discovery or decreasing the frequency of presence checks on managed systems.
Configuring discovery preferences for Level-0 managed systems

To discover Level-0 managed systems, you must configure IBM Director Server. Complete the following steps to configure discovery preferences for Level-0 managed systems: 1. In IBM Director Console, click Options Discovery Preferences. 2. Click the Level 0: Agentless Systems tab. 3. To configure unicast discovery of Level-0 managed systems on remote subnets, complete one or more of the following steps.
To do this: Complete these steps:
Add a single IP 1. Click Add. address for 2. Click Unicast Address. unicast discovery 3. Click Next. 4. Type a value in the IP Address field. 5. Click OK. Add a range of 1. Click Add. IP addresses for 2. Click Unicast Range. unicast discovery 3. Click Next. 4. Type values in the Start Address and End Address fields. 5. Click OK. Add a list of IP 1. Click Import. addresses for 2. Select the text file containing the IP addresses. unicast discovery Note: The file must be a text file, with each line containing either a from a text file single IP addresses or an IP address range specified by a start address and an end address separated by a space. You can select a file on the Local system (on which IBM Director Console is running) or on the Server (on which IBM Director Server is running). 3. Click OK.
298
To do this: Change an existing address entry Delete an existing address entry
Complete these steps: 1. 2. 3. 4. Select the entry to be changed in the Address Entries list. Click Edit. Change the field values for the entry. Click OK.
1. Select the entry to be deleted in the Address Entries list. 2. Click Remove. 3. If prompted, click Yes.
6. Click OK. 7. Optional: To start discovery of Level-0 managed systems now, click Tasks Discover Level 0: Agentless Systems. Otherwise, IBM Director Server will automatically discover Level-0 managed systems periodically as configured in the Discovery Preferences window. Note: Discovery is a background process; you will not see any confirmation that discovery is occurring until managed objects are displayed in IBM Director Console. Discovery of managed systems can take minutes or hours, depending on a number of factors, including the number of IP addresses being queried, the availability of the target networks, the presence check interval that is set for managed systems, and other operations being performed on the management server. To increase the speed of discovery operations, try reducing the number of IP addresses being queried in multicast discovery or decreasing the frequency of presence checks on managed systems.

To discover Level-1 managed systems, you must configure IBM Director Server. Complete the following steps to configure discovery preferences for Level-1 managed systems: 1. In IBM Director Console, click Options Discovery Preferences. 2. Click the Level 1: IBM Director Core Services Systems tab.
299
3. Select a discovery method to use and complete the specified configuration steps.
Discovery method Use Service Location Protocol (SLP) directory agents Steps 1. Specify one or more SLP directory agent servers to use. The selected SLP directory agents are displayed in the Predefined directory agent servers list box. v To add an SLP directory agent server, click Add under the Predefined directory agent servers list. In the Add directory agent window, type the of the SLP directory agent to be added, and then click OK. v To remove an SLP directory agent, click the SLP directory agent to be removed, and then click Remove under the Predefined directory agent servers list. 2. Specify one or more SLP scopes to use. The selected SLP scopes are displayed in the SLP Scope list box. v To add an SLP scope, click Add under the SLP Scope list. In the Add scope window, type the scope to be added, and then click OK. v To remove an SLP scope, click the SLP scope to be removed, and then click Remove under the SLP Scope list. Issue a general IP broadcast 1. Ensure that no SLP directory agents are listed in the Predefined directory agent servers list box. If a directory agent is provided, IBM Director Server will use only the directory agents for discovery. 2. Select the Use broadcast check box. Issue an IP multicast 1. Ensure that no SLP directory agents are listed in the Predefined directory agent servers list box. If a directory agent is provided, IBM Director Server will use only the directory agents for discovery. 2. Select the Use multicast check box.
4. Specify how long IBM Director Server will wait for a response after sending a discovery query before timing out. Type a value for Maximum wait time in seconds. If no value is specified, IBM Director Server will wait 15 seconds. 5. Specify how often IBM Director Server will attempt to discover new managed systems. Select one of the available values for Auto-discover period (hours).
6. Click OK. 7. Optional: To start discovery of Level-1 managed systems now, click Tasks Discover Level 1: IBM Director Core Services Systems. Otherwise, IBM Director Server will automatically discover Level-1 managed systems periodically as configured in the Discovery Preferences window. Note: Discovery is a background process; you will not see any confirmation that discovery is occurring until managed objects are displayed in IBM Director Console. Discovery of managed systems can take minutes or hours, depending on a number of factors, including the number of IP addresses being queried,
300
the availability of the target networks, the presence check interval that is set for managed systems, and other operations being performed on the management server. To increase the speed of discovery operations, try reducing the number of IP addresses being queried in multicast discovery or decreasing the frequency of presence checks on managed systems.

To discover Level-2 managed systems, you must configure IBM Director Server. Complete the following steps to configure discovery preferences for Level-2 managed systems: 1. In IBM Director Console, click Options Discovery Preferences. 2. Click the Level 2: IBM Director Agents tab. 3. At the top of the page, click General to display the general discovery preferences for Level-2 managed systems. 4. Specify how often IBM Director Server will attempt to discover new managed systems. Select one of the available values for Auto-discover period (hours).
6. Select the Automatically secure unsecured systems check box to ensure that IBM Director Server automatically secures any unsecured managed systems that it discovers. When this feature is enabled, IBM Director Server prevents future management servers from managing the managed systems without first requesting access. 7. To enable agent-initiated discovery of this managed-object type, select the Auto-add unknown agents which contact server check box. Agent-initiated discovery can be enabled or disabled separately for Level-2 managed systems and SNMP devices. This option might be useful if you are reinstalling IBM Director Server in an existing IBM Director environment, or if you have configured instances of IBM Director Agent to contact IBM Director Server directly. 8. At the top of the page, click System Discovery (IP) to display IP-specific discovery preferences for Level-2 managed systems. 9. To specify that IBM Director Server issues an IP broadcast to discover managed systems on the local subnet, select the Use TCP/IP general broadcasts check box. By default, this feature is enabled.
301
10. To specify that IBM Director Server issues an IP multicast, complete the following steps: a. Select the Use TCP/IP multicasts check box. b. In the Multicast Group field, type the address of the multicast group address. By default, the multicast group address is set to 224.0.1.118. Note: If you modify the multicast group address, you also must modify the multicast group address on each managed system. c. Select a time-to-live value for the multicast discovery packet in the Multicast TTL field. The time to live is the number of times (1-255) that a packet is forwarded between subnets. By default, this is set to 32. 11. To configure IBM Director Server to use IP broadcast, broadcast relay, or unicast discovery methods to discover managed systems on remote subnets, complete one or more of the following steps.
To do this: Add an address and mask for broadcast discovery Add an address and mask for broadcast relay discovery Complete these steps: 1. 2. 3. 4. 5. 1. 2. 3. 4. 5. Click Add. Click Broadcast. Click Next. Type values in the IP Address and Subnet Mask fields. Click OK. Click Add. Click Relay. Click Next. Type values in the IP Address and Subnet Mask fields. Click OK.
Add a single IP 1. Click Add. address for 2. Click Unicast Address. unicast discovery 3. Click Next. 4. Type a value in the IP Address field. 5. Click OK. Add a range of 1. Click Add. IP addresses for 2. Click Unicast Range. unicast discovery 3. Click Next. 4. Type values in the Start Address and End Address fields. 5. Click OK. Change an existing address entry Delete an existing address entry 1. 2. 3. 4. Select the entry to be changed in the Address Entries list. Click Edit. Change the field values for the entry. Click OK.
12. IPX-enabled management servers only: At the top of the page, click System Discovery (IPX) to display IPX-specific discovery preferences for Level-2 managed systems. Then, complete the following steps: a. To specify that IBM Director Server issues an IPX broadcast to discover managed systems on the local subnet, on the System Discovery (IPX) page, select the Use IPX general broadcasts check box. By default, this feature is enabled. b. To configure IBM Director Server to use IPX broadcasts to discover managed systems on remote subnets, complete one or more of the following steps:
302
To do this:
Complete these steps:
Add an address 1. Click Add. for IPX broadcast 2. Type the IPX address to be added. or broadcast 3. If you want to enable a broadcast relay, select the Enable broadcast relay discovery relay check box. 4. Click OK. Change an existing address entry Delete an existing address entry 1. 2. 3. 4. Select the entry to be changed in the Address Entries list. Click Edit. Change the field values for the entry. Click OK.
13. Click OK. 14. Optional: To start discovery of Level-2 managed systems now, click Tasks Discover Level 2: IBM Director Agents. Otherwise, IBM Director Server will automatically discover Level-2 managed systems periodically as configured in the Discovery Preferences window. Note: Discovery is a background process; you will not see any confirmation that discovery is occurring until managed objects are displayed in IBM Director Console. Discovery of managed systems can take minutes or hours, depending on a number of factors, including the number of IP addresses being queried, the availability of the target networks, the presence check interval that is set for managed systems, and other operations being performed on the management server. To increase the speed of discovery operations, try reducing the number of IP addresses being queried in multicast discovery or decreasing the frequency of presence checks on managed systems.
Configuring discovery preferences for physical platforms

To discover physical platforms, you must configure IBM Director Server. Complete the following steps to configure discovery preferences for physical platforms: 1. In IBM Director Console, click Options Discovery Preferences. 2. Click the Physical Platforms tab. 3. Specify how often IBM Director Server will attempt to discover new managed systems. Select one of the available values for Auto-discover period (hours).
303
Option Disabled
Description IBM Director Server does not check the online status of managed objects of this type. This is the default value for physical platforms. IBM Director Server attempts to contact managed objects of this type every n minutes, where n is the selected number.
1-240
5. Specify a template for naming physical platforms that IBM Director Server discovers.
The following parameters are available, as well as custom text and spaces: v %SERVER_MACHINE_TYPE_MODEL% v %SERVER_SERIAL_NUMBER% v %SERVER_FRU% v %SP_FRU% v %SP_SERIAL_NUMBER% v %CHASSIS_SLOT% v v v v v v v v %CHASSIS_SLOT_RANGE% %CHASSIS_NAME% %SP_TEXT_ID% %SP_IP_ADDRESS% %SP_HOSTNAME% %SP_ASSET_TAG% %DIR_AGENT_NAME% %COMPUTER_NAME%
304
By default, this naming template is set to the following value: IBM %SERVER_MACHINE_TYPE_MODEL% %SERVER_SERIAL_NUMBER% 6. To use the naming template during discovery, select Use during discovery. 7. Click OK. 8. Optional: To start discovery of physical platforms now, click Tasks Discover Physical Platforms. Otherwise, IBM Director Server will automatically discover physical platforms periodically as configured in the Discovery Preferences window. Note: Discovery is a background process; you will not see any confirmation that discovery is occurring until managed objects are displayed in IBM Director Console. Discovery of managed systems can take minutes or hours, depending on a number of factors, including the number of IP addresses being queried, the availability of the target networks, the presence check interval that is set for managed systems, and other operations being performed on the management server. To increase the speed of discovery operations, try reducing the number of IP addresses being queried in multicast discovery or decreasing the frequency of presence checks on managed systems.
Configuring discovery preferences for SMI-S storage devices

To discover SMI-S Storage devices, you must configure IBM Director Server. Complete the following steps to configure discovery preferences for SMI-S storage devices: 1. In IBM Director Console, click Options Discovery Preferences. 2. Click the SMI-S Storage Devices tab. 3. Specify how often IBM Director Server will attempt to discover new managed systems. Select one of the available values for Auto-discover period (hours).
5. Under Service Location Protocol (SLP) Profiles, select the SLP profiles that IBM Director Server will discover. The default values are SNIA:Array and SNIA:Switch.
305
To do this: Add an SLP profile
Complete these steps: 1. In the Available Profiles list, click a profile to add. 2. Click Add. 1. In the Selected Profiles list, click a profile to remove. 2. Click Remove. Select the Reset to default value check box. If prompted, click Yes.
Remove an SLP profile
Restore the Selected Profiles list to the default values
6. Select a discovery method to use and complete the specified configuration steps.
306
9. Specify a template for naming SMI-S storage devices that IBM Director Server discovers.
The following parameters are available, as well as custom text and spaces: v %MANUFACTURER_ID% v %HARDWARE_TYPE_MODEL% v %HARDWARE_SERIAL_NUMBER% v %IPADDRESSES% v %ENDPOINT% v %NAME% By default, this naming template is set to the following value: %MANUFACTURER_ID% %HARDWARE_TYPE_MODEL% %ENDPOINT% 10. Click OK. 11. Optional: To start discovery of SMI-S storage devices now, click Tasks Discover SMI-S Storage Devices. Otherwise, IBM Director Server will automatically discover SMI-S storage devices periodically as configured in the Discovery Preferences window. Note: Discovery is a background process; you will not see any confirmation that discovery is occurring until managed objects are displayed in IBM Director Console. Discovery of managed systems can take minutes or hours, depending on a number of factors, including the number of IP addresses being queried, the availability of the target networks, the presence check interval that is set for managed systems, and other operations being performed on the management server.
307
To increase the speed of discovery operations, try reducing the number of IP addresses being queried in multicast discovery or decreasing the frequency of presence checks on managed systems.
Configuring discovery preferences for SNMP devices

To discover SNMP devices, you must configure IBM Director Server. Complete the following steps to configure discovery preferences for SNMP devices: 1. In IBM Director Console, click Options Discovery Preferences. 2. Click the SNMP Devices tab. 3. Configure seed addresses for SNMP discovery. You can specify multiple IP addresses; the addresses are searched concurrently. By default, the IP address of the management server is added to this list. This device should be an SNMP device. If the IBM Director Server is on a system that is not running SNMP, then the address of the device that is not running SNMP in SNMP discovery preferences will not help for this IBM Director Servers discovery of SNMP. To optimize the chance of discovering all SNMP devices, be sure to specify the IP addresses for routers and DNS servers that are SNMP devices. During the discovery operation, IBM Director Server, iso.org.dod.internet.mgmt.mib2.ip.ipNetToMediaTable.ipNetToMediaEntry.ipNetToMediaNetAddress, locates the address tables that are found on the specified devices and adds those addresses to the list of addresses to search. You can use the SNMP browser on the SNMP device that is listed in your preferences to view the table. Addresses in the table are used for Discovery. An address will not be found in the table if SNMP is not currently active on that device. The process is repeated for every new SNMP device that is discovered from the new addresses. The discovery operation continues until no more addresses are found. A newly installed IBM Director Server is not likely to find many addresses in the address table. Some IBM Director Servers without any additions in SNMP Discovery Preferences might find few or no SNMP devices while others might find many SNMP devices. Adding to the address table can be accomplished by doing Discovery. However, the implementation of the SNMP device is completely separate from IBM Director and addresses that are in the same subnet or subnets as the SNMP device might be the only ones that are added to the address table. The manual add SNMP device panel has a checkbox for Use as a discovery seed. Selecting this checkbox adds the address to SNMP Discovery preferences to allow the new device to be a seed in all subsequent discovery operations. If you are using a community name other than the public community name, you can manually add the community name to SNMP Discovery preferences. SNMP Discovery preferences also has an option to Auto-add unknown agents which contact server.
To do this: Add a new seed address for SNMP discovery Complete these steps: 1. Type an IP address and subnet mask value in the text boxes at the top of the IP Addresses and Subnet Masks list. 2. Click Add.
308
To do this: Add a list of seed addresses from a text file
Complete these steps: 1. Click Import. 2. Select the text file containing the IP addresses. Note: The file must be a text file, with each line containing a single IP address. You can select a file on the Local system (on which IBM Director Console is running) or on the Server (on which IBM Director Server is running). 3. Click OK. 1. Click the entry to be changed in the IP Addresses and Subnet Masks list. 2. Change the IP address and subnet mask value in the text boxes at the top of the IP Addresses and Subnet Masks list. 3. Click Replace. 1. Click the entry to be deleted in the IP Addresses and Subnet Masks list. 2. Click Remove. 3. If prompted, click Yes.
Change an existing seed address
Delete an existing seed address
4. Select the version of SNMP being used. Select a value from the SNMP Version control. Possible values are SNMPv1, SNMPv2c, or SNMPv3. 5. SNMPv1 and SNMPv2c only: Specify the community names for SNMP discovery.
To do this: Complete these steps:
Add a new 1. Type the community name in the text box at the top of the community name Community Names list. to the end of the 2. Click Add. Community Names list Change an 1. Click the community name to be changed. existing 2. Change the community name in the text box at the top of the community name Community Names list. 3. Click Replace. Delete an 1. Click the community name to be deleted. existing 2. Click Remove. community name 3. If prompted, click Yes.
Note: The community names should be ordered from top to bottom in increasing level of access restriction. 6. SNMPv3 only: Specify profile names for SNMP discovery of systems that have restricted SNMP access. Restricted SNMP devices are not discovered without correct specification of a profile name.
To do this: Add a profile name Complete these steps: 1. Select a profile name using the control at the top of the Profile Names list. Note: Profile names which are displayed in this control are configured in the Server Preferences window. 2. Click Add. 1. Click the profile name to be deleted. 2. Click Remove. 3. If prompted, click Yes.
Delete a profile name
309
9. To enable agent-initiated discovery of this managed-object type, select the Auto-add unknown agents which contact server check box. Agent-initiated discovery can be enabled or disabled separately for Level-2 managed systems and SNMP devices. This option might be useful if you are reinstalling IBM Director Server in an existing IBM Director environment, or if you have configured instances of IBM Director Agent to contact IBM Director Server directly. 10. Click OK. 11. Optional: To start discovery of SNMP devices now, click Tasks Discover SNMP Devices. Otherwise, IBM Director Server will automatically discover SNMP devices periodically as configured in the Discovery Preferences window. Note: Discovery is a background process; you will not see any confirmation that discovery is occurring until managed objects are displayed in IBM Director Console. Discovery of managed systems can take minutes or hours, depending on a number of factors, including the number of IP addresses being queried, the availability of the target networks, the presence check interval that is set for managed systems, and other operations being performed on the management server. To increase the speed of discovery operations, try reducing the number of IP addresses being queried in multicast discovery or decreasing the frequency of presence checks on managed systems.
Configuring discovery preferences for hardware management consoles

To discover hardware management consoles (HMC), you must configure IBM Director Server. HMC discovery preferences can only be configured if the Hardware Management Console extension for IBM Director is installed. The extension must be installed on both IBM Director Server and any remote instances of IBM Director Console.
310
Complete the following steps to configure discovery preferences for hardware management consoles: 1. In IBM Director Console, click Options Discovery Preferences. 2. Click the HMC tab. 3. Select a discovery method to use and complete the specified configuration steps.
311
Option Disabled 1 - 240
Description IBM Director Server does not check the online status of managed objects of this type. IBM Director Server attempts to contact managed objects of this type every n minutes, where n is the selected number. The default value is 15.
7. Click OK. 8. Optional: To start discovery of hardware management consoles now, click Tasks Discover HMC. Otherwise, IBM Director Server will automatically discover hardware management consoles periodically as configured in the Discovery Preferences window. Note: Discovery is a background process; you will not see any confirmation that discovery is occurring until managed objects are displayed in IBM Director Console. Discovery of managed systems can take minutes or hours, depending on a number of factors, including the number of IP addresses being queried, the availability of the target networks, the presence check interval that is set for managed systems, and other operations being performed on the management server. To increase the speed of discovery operations, try reducing the number of IP addresses being queried in multicast discovery or decreasing the frequency of presence checks on managed systems.
Configuring discovery preferences for z/VM systems

To discover z/VM systems, you must configure IBM Director Server. z/VM discovery preferences can be configured only if the z/VM Center extension for IBM Director is installed. The extension must be installed on both IBM Director Server and any remote instances of IBM Director Console. Complete the following steps to configure discovery preferences for z/VM systems: 1. In IBM Director Console, click Options Discovery Preferences. 2. Click the z/VM Systems tab. 3. Select a discovery method to use and complete the specified configuration steps.
312
Discovery method Use Service Location Protocol (SLP) directory agents
Steps 1. Specify one or more SLP directory agent servers to use. The selected SLP directory agents are displayed in the Predefined directory agent servers list box. v To add an SLP directory agent server, click Add under the Predefined directory agent servers list. In the Add directory agent window, type the of the SLP directory agent to be added, and then click OK. v To remove an SLP directory agent, click the SLP directory agent to be removed, and then click Remove under the Predefined directory agent servers list. 2. Specify one or more SLP scopes to use. The selected SLP scopes are displayed in the SLP Scope list box. v To add an SLP scope, click Add under the SLP Scope list. In the Add scope window, type the scope to be added, and then click OK. v To remove an SLP scope, click the SLP scope to be removed, and then click Remove under the SLP Scope list.
Issue a general IP broadcast
1. Ensure that no SLP directory agents are listed in the Predefined directory agent servers list box. If a directory agent is provided, IBM Director Server will use only the directory agents for discovery. 2. Select the Use broadcast check box.
Issue an IP multicast
1. Ensure that no SLP directory agents are listed in the Predefined directory agent servers list box. If a directory agent is provided, IBM Director Server will use only the directory agents for discovery. 2. Select the Use multicast check box.
7. Click OK.
313
8. Optional: To start discovery of z/VM systems now, click Tasks Discover z/VM Systems. Otherwise, IBM Director Server will automatically discover z/VM systems periodically as configured in the Discovery Preferences window. Note: Discovery is a background process; you will not see any confirmation that discovery is occurring until managed objects are displayed in IBM Director Console. Discovery of managed systems can take minutes or hours, depending on a number of factors, including the number of IP addresses being queried, the availability of the target networks, the presence check interval that is set for managed systems, and other operations being performed on the management server. To increase the speed of discovery operations, try reducing the number of IP addresses being queried in multicast discovery or decreasing the frequency of presence checks on managed systems.
Performing server-initiated discovery of managed objects

Use server-initiated discovery procedures to configure IBM Director Server to find managed objects in your network. By default, IBM Director Server automatically discovers all managed systems that are on the same subnet as the management server. To discover systems that are on a different subnet, you must configure discovery preferences. Discovery preferences are persistent in IBM Director and might not need to be changed each time you discover new managed objects. However, reviewing the discovery preferences when discovering managed objects is a good practice and offers an opportunity to verify that the discovery preferences will support discovery of new components in your network. The general procedure for performing server-initiated discovery of managed objects is the same for all managed-object types: 1. Configure discovery preferences: a. In IBM Director Console, click Options Discovery Preferences. b. Configure preferences in the Discovery Preferences window and click OK. 2. Click Tasks Discover Managed-object type. Managed-object type is one of the following managed-object types: v All Managed Objects v BladeCenter Chassis v HMC (only if the optional Hardware Management Console extension is installed) v Level 0: Agentless Systems v Level 1: IBM Director Core Services Systems v Level 2: IBM Director Agents v Physical Platforms v SMI-S Storage Devices v SNMP Devices After installing IBM Director and first performing discovery, all managed objects of the selected type might not be discovered without performing discovery several times. To avoid this situation, consider limiting the quantity of managed objects that you discover at a time. Note: Discovery is a background process; you will not see any confirmation that discovery is occurring until managed objects are displayed in IBM Director
314
Console. Discovery of managed systems can take minutes or hours, depending on a number of factors, including the number of IP addresses being queried, the availability of the target networks, the presence check interval that is set for managed systems, and other operations being performed on the management server. To increase the speed of discovery operations, try reducing the number of IP addresses being queried in multicast discovery or decreasing the frequency of presence checks on managed systems.
Configuring software-distribution preferences

Use the Server Preferences window: Software Distribution page to configure software-distribution preferences such as the maximum number of managed systems to which you want to stream software packages concurrently and the bandwidth that you want to assign to streaming software packages. You can also specify not to stream a package if a redirected distribution fails, as well as restrict the server access check. Complete the following steps to configure software-distribution preferences: 1. If necessary, start IBM Director Console. 2. Click Options Server Preferences. 3. In the Server Preferences window, click the Software Distribution tab. 4. On the Software Distribution page, locate the Maximum Managed Systems field and type the maximum number of managed systems to which IBM Director Server can concurrently stream software packages. The default value is three. 5. To limit the bandwidth used to stream packages, select the Enter streaming bandwidth (kbps) for managed systems check box. In the entry field, type the bandwidth, in kilobytes per second (kbps), that you want to use to stream packages from either IBM Director Server or a file-distribution server to the managed system. To specify values less than 1 kbps, type a decimal fraction. The minimum acceptable value is 0.25 (256 bytes per second). 6. To avoid streaming a package in the event that a redirected distribution fails, select the Do not stream distribution if redirected distribution fails check box. However, if no shares are defined on the file-distribution server and this check box is selected, the package is streamed. 7. To prevent IBM Director Server from performing an access check of all of the file-distribution-server shares, select the Restrict server access check check box. This selection restricts the access check to only the file-distribution-server shares that you configure for a specific managed system or group. 8. Click OK.
Setting up file-distribution servers

This topic describes how to set up file-distribution servers. IBM Director supports UNC-based and FTP-based file distribution. See your server documentation for information about setting up a shared subdirectory. Note: You do not need to install IBM Director on the file-distribution server. Complete the following steps to configure software-distribution preferences: 1. If necessary, start IBM Director Console. 2. Click Options -> Server Preferences.
315
3. In the Server Preferences window, click the Software Distribution tab. 4. On the Software Distribution page, locate the Maximum Managed Systems field and type the maximum number of managed systems to which IBM Director Server can concurrently stream software packages. The default value is three. 5. To limit the bandwidth used to stream packages, select the Enter streaming bandwidth (kbps) for managed systems check box. In the entry field, type the bandwidth, in kilobytes per second (kbps), that you want to use to stream packages from either IBM Director Server or a file-distribution server to the managed system. To specify values less than 1 kbps, type a decimal. The minimum acceptable value is 0.25 (256 bytes per second). 6. To avoid streaming a package in the event that a redirected distribution fails, select the Do not stream distribution if redirected distribution fails check box. However, if no shares are defined on the file-distribution server and this check box is selected, the package is streamed. 7. To prevent IBM Director Server from performing an access check of all of the file-distribution-server shares, select Restrict server access check. This selection restricts the access check to only the file-distribution-server shares that you configure for a specific managed system or group. 8. Click OK.
Configuring IBM Director to use a file-distribution server

You can configure IBM Director to use a file-distribution server to distribute software to Level-2 managed systems. Complete the following steps to configure IBM Director Server to use a file-distribution server: 1. Start IBM Director Console. 2. Click Options Server Preferences. 3. In the Server Preferences window, click the File Distribution Server tab. A list is displayed of all configured file-distribution servers. 4. Click Add. 5. In the Add Share Name window, type the name of the file-distribution server (using UNC notation) in the Share Name field. To specify FTP as the transport protocol, begin the share-name entry with ftp:, for example ftp:\\server_name. 6. In the Maximum Disk Space field, type the maximum amount of disk space (in MB) that can be allocated on the file-distribution server for software distribution. 7. In the Maximum Managed Systems field, type the maximum number of managed systems that can receive a software package at the same time. 8. To limit the bandwidth that can be used to send packages between IBM Director Server and the file-distribution server, select Limit bandwidth between server and share (kbps). In the entry field, type the maximum bandwidth, in kilobytes per second (kbps), that can be used to send packages between IBM Director and the file-distribution server. You might want to limit the bandwidth when a dedicated connection, such as integrated services digital network (ISDN), is used for copying the files from IBM Director Server to the share. 9. If you specified an FTP-based server in step 5, you must provide information about the FTP server:
316
a. In the User ID on FTP server field, type a user ID authorized to access the FTP server installed on the share. b. In the Password field, type the password associated with the user ID. c. In the Confirm password field, retype the password associated with the user ID. d. In the Home Directory field, you can specify the directory in which you want to cache software packages. If you do not specify a directory, the packages will be cached in the default home directory defined for the FTP user. Note: For i5/OS, you must specify a directory, or configure the FTP server to operate in regular mode. By specifying a directory, IBM Director automatically changes the FTP server to operate in regular mode. 10. Click OK. If you have multiple file-distribution servers, repeat this procedure for each server.
Configuring software-distribution preferences for managed systems

This topic describes how to configure software-distribution preferences for Level-2 managed systems. After you configure IBM Director to use a file-distribution server, you can assign policies to a managed system and groups. By default, a managed system attempts to access shared directories on the file-distribution server that have been defined to the management server. You can configure the following software-distribution preferences for a managed system or group: v Specify whether software distribution occurs through streaming or redirected distribution v Restrict access to an explicit list of shares that reside on the file-distribution server v Limit the bandwidth used for software distribution to the managed system or group Complete the following steps to define distribution preferences: 1. If necessary, start IBM Director Console. 2. In the Group Contents pane, right-click the managed system or group to which you want to distribute software and click Distribution Preferences. 3. In the Distribution Preferences window, select the method of software distribution: v If you want to copy packages directly from IBM Director Server to the managed system or group, click Always stream to the Managed System(s). v If you want to copy packages from a share on a file-distribution server to the managed system or group, click Use File Distribution Server Shares. Note: When you have selected Use File Distribution Server Shares and a file-distribution-server share cannot be located during a software distribution, the default action is to stream the package from IBM Director Server. You can prevent streaming from IBM Director Server by selecting the Do not stream if redirection fails check box in the Server Preferences for Software Distribution window. However, if no file-distribution-server shares are defined and this check box is selected, the package is streamed. 4. To add a share, click Add.
317
5. In the Add Share Name window, select the share on the file-distribution server in the Share Name field. If necessary, specify a user ID and password for an account that can access the share. 6. Click OK. 7. Repeat steps 4 on page 317 through 6 until you have added all of the file-distribution-server shares that you want the managed system or group to access. 8. If you want to limit the file-distribution-server shares that the managed system or group can access to only those displayed, select the Restrict share selection to list check box. Note: Windows only: If you select to use a file-distribution server share and specify a user ID and password with which to distribute the package, rather than using null credentials, the Stream from File Distribution Server check box must be selected for a distribution to complete successfully. This applies to packages created with the IBM Update Assistant, InstallShield Package, or Microsoft Windows Installer Package wizards. 9. To limit the bandwidth that is used when copying packages, select the Limit streaming bandwidth for system check box. If you have selected Always stream to system(s), type a bandwidth value, in kilobytes per second (kbps), to define the bandwidth for copying packages from IBM Director Server to the managed system or group. If a bandwidth limitation is also set in Server Preferences for streaming from the IBM Director Server, the lower value of the two settings is used. If you have selected Use File Distribution Server Shares, type a bandwidth value to define the bandwidth for copying packages from the file-distribution-server share to the managed system or group. If a file-distribution-server share is unavailable at the time of distribution and if the software distribution preferences on the management server allow streaming, IBM Director Server streams the package to the managed system. In this case, the bandwidth limitation works in the same way as if you had selected Always stream to system(s).
Enabling SNMP access and trap forwarding for Linux

SNMP access and trap forwarding enable SNMP-based managers to poll the managed system and receive its alerts. If System Health Monitoring is installed on the managed system also, hardware alerts can be forwarded as SNMP traps. To enable SNMP access and trap forwarding on Linux, you must be running one of the following operating systems: v Red Hat Linux, version 3.0 v Red Hat Linux, version 4.0 v SUSE Linux Enterprise Server 9 for x86 v SUSE Linux Enterprise Server 10 for x86 v SUSE Linux Enterprise Server 9 for IBM System z v VMware ESX Server, version 2.5.x Console v VMware ESX Server, version 3.0 Console IBM Director supports SNMP access and trap forwarding using NetSNMP. To enable SNMP access and trap forwarding, complete the following steps: 1. Install the Net-SNMP agent.
318
Note: You can use the Net-SNMP agent that is provided with your Linux distribution. 2. Configure the Net-SNMP agent as the master agent and configure the access permissions and trap destination. For information about how to configure Net-SNMP, go to the Net-SNMP Web site at www.net-snmp.org/ download.html. 3. Start the Net-SNMP agent on the managed system.
319
320

You can use the following procedures to uninstall IBM Director. Notes: v Before uninstalling IBM Director, uninstall IBM Director extensions using the uninstallation instructions provided for the extensions. v You can retain the configuration data when you uninstall IBM Director. This enables you to reinstall or upgrade IBM Director and access the saved configuration data. Should you reinstall, be sure to reinstall IBM Director in the same location.
Uninstalling IBM Director on i5/OS

Use this information to uninstall the IBM Director components that are installed on your i5/OS systems.
Uninstalling IBM Director Server using DLTLICPGM

You can uninstall IBM Director Server from an i5/OS system by using DLTLICPGM. To uninstall IBM Director Server using DLTLICPGM, complete the following steps: 1. At an i5/OS command prompt on the system on which IBM Director Server is installed, type the following command and press Enter;
DLTLICPGM LICPGM(5722DR1)
2. To remove IBM Director user data from the i5/OS management server, delete the /qibm/userdata/director/ directory by typing the following command:
QSH CMD (rm -rf /qibm/userdata/director/)
Uninstalling IBM Director Agent on i5/OS

You can uninstall IBM Director Agent on i5/OS using DLTLICPGM. To uninstall IBM Director Agent using DLTLICPGM, complete the following steps: 1. At an i5/OS command prompt on the system on which IBM Director Agent is installed, type the following command and press Enter:
DLTLICPGM LICPGM(5722DA1)
2. To remove IBM Director user data from the i5/OS managed system, delete the /qibm/userdata/director/ directory using the following command:
QSH CMD(rm -rf /qibm/userdata/director/)
Uninstalling IBM Director on Linux or AIX

You can use the diruninstall script to uninstall IBM Director on Linux on System p, Linux for System x, Linux for System z, or AIX. The diruninstall script is located in the install_root/bin directory, where install_root represents the root directory of your IBM Director installation. By default, this script removes all IBM Director components. You can modify the script to remove specific components.
321
v To uninstall IBM Director and all components, type the following command and press Enter:
install_root/bin/diruninstall
v To uninstall specific components, complete the following steps: 1. Open the diruninstall script in an ASCII text editor and set the SmartUninstall setting to 0. 2. Make additional modifications to the script. 3. Save the modified diruninstall script. 4. Type the following command and press Enter:
install_root/bin/diruninstallbin/diruninstall
Notes: If you are going to uninstall a specific component, you must stop the component first. (Linux on POWER only) If you did not install IBM Director Core Services you must remove IBM Director components using standard RPM commands (by default,IBM Director Core Services is installed when IBM Director Server or IBM Director Agent is installed). v You also can uninstall IBM Director on Linux using standard RPM commands or on AIX using the System Management Interface Tool (SMIT). Consider the following information: Uninstall any IBM Director extensions before uninstalling IBM Director Server, IBM Director Console, IBM Director Core Services, or IBM Director Agent If anIBM Director database is configured, you must delete the tables and remove theIBM Director database configuration. Perform this task after all other packages are removed but before uninstalling IBM Director Server. From a command prompt, type the following command and press Enter:
install_root/bin/uncfgdb
When you uninstall packages on Linux, the following files are retained to make it possible to restore persistent data: /opt/ibm/director.save.1/saveddata.tar /etc/ibm/director/twgagent/twgagent.uid
Uninstalling IBM Director on Windows

You can uninstall IBM Director either by using the Windows Add/Remove Programs feature or from a command-line prompt. You can use both of these methods to uninstall IBM Director Server, IBM Director Console, IBM Director Agent, or IBM Director Core Services. You must uninstall any separately installed IBM Director extensions before uninstalling IBM Director Server, IBM Director Console, or IBM Director Agent.
Uninstalling IBM Director using the Windows Add/Remove Programs feature

You can uninstall IBM Director from Windows by using the Windows Add/Remove Programs feature. To uninstall IBM Director, complete the following steps: 1. Shut down all applications. 2. Click Start Settings Control Panel. The Control Panel window opens.
322
3. Double-click Add/Remove Programs. The Add/Remove Programs window opens. 4. Click the IBM Director software component that you want to remove; then, click Remove. 5. Follow the instructions on the screen.
Uninstalling IBM Director using the dirunins command

You can uninstall IBM Director from Windows by using the dirunins command. To uninstall an IBM Director component that is running on a Windows system, from a command-line prompt, type the following command and press Enter:
dirunins directorcomponent option
The following table contains information about the possible values for option and directorcomponent.
Table 108. dirunins parameters Variable option Parameter debug What it does Logs all messages that are sent by the Windows Installer log engine, including status and information messages Deletes all configuration data. This parameter must be used in conjunction with silent or unattended parameter. For example, dirunins agent unattended deletedata performs an unattended uninstallation of IBM Director Agent and deletes IBM Director configuration data.
deletedata
log=logfilename Specifies the fully qualified name of an alternative installation log file noreboot silent unattended verbose directorcomponent server console agent coresvcs Suppresses any required restart Suppresses all output to the screen Shows the progress of the uninstallation but does not require any user input Enables verbose logging Uninstalls IBM Director Server and any installed IBM Director extensions Uninstalls IBM Director Console and any installed IBM Director extensions Uninstalls Level 2: IBM Director Agent Uninstalls Level 1: IBM Director Core Services
Note: If you are uninstalling IBM Director Agent or IBM Director Core Services, you must uninstall any installed IBM Director extensions first.
Uninstalling IBM Director Agent on NetWare

You can use the following procedure to uninstall IBM Director Agent on NetWare. Complete the following steps to uninstall IBM Director Agent on NetWare: 1. From the server running NetWare, change to the console screen. 2. Type the following command and press Enter:
323
unload twgipc
3. Type the following command and press Enter:

nwconfig
The Configuration Options screen opens. 4. Select NCF Files Options. 5. Select Edit AUTOEXEC.NCF file. 6. Remove the following lines from the autoexec.ncf file:
:********IBM Director Agent******** Search add sys:IBM\Director load twgipc :********IBM Director agent********
7. Save the modified autoexec.ncf file. 8. Shut down and restart the server running NetWare. 9. From a Windows workstation running the NetWare Client for Windows, map a drive to the SYS volume and delete the IBM\Director directory.
Uninstalling IBM Director Core Services before migrating to an earlier version of IBM Director
If you want to change your installation of IBM Director Core Services to a to a pre-5.20 version make sure that you understand potential issues that might affect the installation. When uninstalling IBM Director 5.20 in order to install an earlier version of IBM Director, make sure to uninstall all instances of IBM Director Core Services. On managed systems running Microsoft Windows, versions of IBM Director previous to 5.20 cannot detect whether IBM Director Core Services is installed. As a result, the pre-5.20 installation will not provide any indication that an IBM Director 5.20 component is present. Note: Installing pre-5.20 versions of IBM Director, including IBM Director Agent, IBM Director Console, and IBM Director Server, on a system on which IBM Director Core Services is installed has the potential to cause problems. Before installing any pre-5.20 component of IBM Director, use the following procedure to uninstall IBM Director Core Services. At a command prompt, type one of the following commands and press Enter.
Operating System Linux Command install_root/bin/diruninstall where install_root represents the directory in which IBM Director was installed. Microsoft Windows dirunins coresvcs unattended deletedata
IBM Director Core Services is uninstalled.
324
Chapter 5. Modifying an IBM Director installation

Enabling the Wake on LAN feature
If your server supports the Wake on LAN feature, you can enable it after IBM Director is installed. See your server documentation to determine whether or not your server supports this feature.
Enabling the Wake on LAN feature for Linux or AIX

This topic describes how to enable the Wake on LAN feature for IBM Director Agent. Complete the following steps to enable Wake on LAN for IBM Director Agent: 1. From a command prompt, stop IBM Director Agent. Type the following command and press Enter:
/opt/ibm/director/bin/twgstop
2. Open an ASCII text editor and edit the ServiceNodeLocal.properties file. This file is in the /opt/ibm/director/data directory. 3. Modify the value of ipc.wakeonlan to read as follows:
ipc.wakeonlan=1
4. Save and close the ServiceNodeLocal.properties file. 5. Start IBM Director Agent by typing the following command and pressing Enter:
Enabling the Wake on LAN feature on Windows

Use the Control Panel to enable Wake on LAN on a managed system running Windows. Note: To determine whether your server supports the Wake on LAN feature, see your server documentation. Complete the following steps to enable Wake on LAN: 1. Click Start Settings Control Panel. The Control Panel window opens. 2. Double-click Add/Remove Programs. The Add/Remove Programs window opens. 3. Click the IBM Director software component that you want to modify; then, click Change. The InstallShield wizard starts, and the Welcome to the InstallShield window opens. 4. Click Next. The Program Maintenance window opens.
325
Figure 21. Program Maintenance window
5. Click Modify; then, click Next. 6. Continue through the wizard until you reach the Network Driver Configuration window. 7. Select the Enable Wake on LAN check box. 8. Complete the wizard.
Configuring the database on the management server

Use the instructions appropriate for your platform to configure the database after IBM Director Server is installed.
Configuring the database on Linux or AIX

This section describes how to configure your database application for use with IBM Director after IBM Director Server is installed. These instructions are applicable for all Linux platforms and AIX.
Configuring the database on a Linux or AIX management server using the cfgdb command
Use the cfgdb command to configure the database after IBM Director Server is installed. Note: The cfgdb command must be used in a graphical environment. To configure the database from a command line, see Configuring the database on a Linux or AIX management server using the cfgdbcmd command. Complete the following steps to install and configure a database after you have installed IBM Director Server: 1. To stop IBM Director Server, from a command prompt, type the following command and press Enter:
/opt/ibm/director/bin/twgstop
326

/opt/ibm/director/bin/cfgdb
3. Follow the instructions on the screen. 4. Restart IBM Director Server by typing the following command and pressing Enter:
Configuring the database on a Linux or AIX management server using the cfgdbcmd command
Use the cfgdbcmd command to configure the database from a command line after IBM Director Server is installed. Complete the following steps to install and configure a database from the command line after you have installed IBM Director Server: 1. Open the cfgdbcmd.rsp file in an ASCII text editor and modify the settings. The cfgdbcmd.rsp file is located in the install_root/data directory, where install_root is the root directory of your IBM Director installation. The cfgdbcmd.rsp file is a fully commented example file that you can modify. 2. Save the modified file with a new file name. 3. From a command prompt, stop IBM Director Server. Type the following command and press Enter:
where install_root is the root directory of your IBM Director installation. 4. Type the following command and press Enter:
install_root/bin/cfgdbcmd -rspfile response.rsp
where install_root is the root directory of your IBM Director installation, and response.rsp is the name of the response file you saved in step 2. 5. When the configuration is completed, restart IBM Director Server. Type following command and press Enter:
where install_root is the root directory of your IBM Director installation.
Configuring the database on a Windows management server

Use the cfgdb command to configure the database on a Windows management server after IBM Director Server is installed. Complete the following steps to configure a database after you have installed IBM Director Server: 1. Stop IBM Director Server. From a command prompt, type the following command and press Enter:
net stop twgipc

cfgdb
The IBM Director Database Configuration window opens. 3. Follow the instructions on the screen.
Chapter 5. Modifying an IBM Director installation
327
Note: If you want the IBM Director Database Configuration window to accept Windows color settings after installation, you must first go to the Accessibility Preferences tab in the Console Preferences window, and select the Windows option in the Colors field.
Enabling SNMP access and trap forwarding for Linux

SNMP access and trap forwarding enable SNMP-based managers to poll the managed system and receive its alerts. If System Health Monitoring is installed on the managed system also, hardware alerts can be forwarded as SNMP traps. To enable SNMP access and trap forwarding on Linux, you must be running one of the following operating systems: v Red Hat Linux, version 3.0 v Red Hat Linux, version 4.0 v SUSE Linux Enterprise Server 9 for x86 v SUSE Linux Enterprise Server 10 for x86 v SUSE Linux Enterprise Server 9 for IBM System z v VMware ESX Server, version 2.5.x Console v VMware ESX Server, version 3.0 Console IBM Director supports SNMP access and trap forwarding using NetSNMP. To enable SNMP access and trap forwarding, complete the following steps: 1. Install the Net-SNMP agent. Note: You can use the Net-SNMP agent that is provided with your Linux distribution. 2. Configure the Net-SNMP agent as the master agent and configure the access permissions and trap destination. For information about how to configure Net-SNMP, go to the Net-SNMP Web site at www.net-snmp.org/ download.html. 3. Start the Net-SNMP agent on the managed system.
328
Chapter 6. Troubleshooting
Use this section to troubleshoot and resolve problems with IBM Director 5.20 or later. To troubleshoot problems that are specific to earlier versions of IBM Director, see the documentation for that version. For solutions to problems that other customers have encountered, see the IBM Director customer forum at www.ibm.com/developerworks/forums/ dw_forum.jsp?forum=759&cat=53.
Installation troubleshooting
This section provides information about problems and workarounds related to installing IBM Director. For additional troubleshooting information, see the IBM Director Release Notes.
Linux installation troubleshooting

This section provides information for specific problems and workarounds associated with Linux installation. Review all troubleshooting topics for possible solutions. For additional troubleshooting information, see the IBM Director Release Notes.
Could not detect rpm supported Linux distribution

This problem affects only systems running Linux.
Problem
When installing IBM Director Core Services, IBM Director Agent, or IBM Director Server, the following error message might be generated:
Could not detect rpm supported Linux distribution
where rpm is one of the following RPMs: v DirectorCimCore v xSeriesCoreServices-level1 v pSeriesCoreServices-level1
Investigation
This message occurs if you install IBM Director components on a Linux distribution that is not supported by the DirectorCimCore, xSeriesCoreServiceslevel1, and pSeriesCoreServices-level1 RPMs. To correct the problem, install a supported Linux distribution. See the IBM Director Planning, Installation and Configuration Guide.
depmod: *** Unresolved symbols in /lib/modules/2.4.7-10smp/ kernel/drivers/char/

This problem only affects systems running Red Hat Linux.
329
Problem
If you install the IBM SMbus or LM78 device driver, a warning message similar to the following might be recorded in the Bootmsg.log file: depmod: *** Unresolved symbols in /lib/modules/2.4.7-10smp/kernel/drivers/ char/driver.o where driver is either ibmsmb or ibmlm78.
Investigation
This warning message is generated if the Red Hat Linux kernel was compiled with versioned symbols enabled. Ignore this message; the device driver loaded and will operate properly.
Windows installation troubleshooting

This section provides information for specific problems and workarounds associated with Windows installation. Review all troubleshooting topics for possible solutions. For additional troubleshooting information, see the IBM Director Release Notes.
Error in the event log: The open procedure for service PerfDisk
This problem affects IBM Director Server. The problem occurs only on servers running Windows 2000 Server.
Problem
After IBM Director Server is installed, the following error is displayed in the event log when the server is restarted:
The open procedure for service PerfDisk in the DLL C:\WINNT\System32\perfdisk.dll has taken longer than the established wait time to be completed.
Investigation
Use the regedit command to modify the following key entry and change the decimal value to 30000:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services \PerfDisk\Performance key "Open Timeout"
This gives the system enough time to complete the startup task before starting the PERF counters.
Installation package cannot be installed by Windows Installer service

This problem affects systems with a version of Windows Installer (MSI) that is earlier than version 3.0. This problem occurs only on systems running Windows 2000, Windows XP with no service packs, or Windows XP with Service Pack 1.
Problem
During a Windows Installer administrative installation, the following message is displayed:
330
This installation Windows Installer service pack that Windows Installer
package cannot be installed by service. You must install a Windows contains a newer version of the service.
Investigation
To correct this problem and perform Windows Installer administrative installation, complete the applicable procedure. v If you are installing a Web-downloadable extension, type the following command:
filename.exe -a admin
where filename is the name of the Web-downloadable extension installation file. v If you are installing IBM Director Server, IBM Director Console, IBM Director Agent, or IBM Director Core Services from the IBM Director CD, complete the following steps: 1. On the IBM Director CD, change to the directory for the IBM Director component that you want to install. 2. Type one of the following commands:
filename.exe -a admin
where filename is the name of the IBM Director component installation file. Note: If the system that is running the administrative installation has a version of MSI that is earlier than version 3.0, these commands update MSI on that system. After MSI is updated and the administrative installation is completed, a message is displayed that you must reboot the system. Be sure to do so.
Windows blue screen IRQL_NOT_LESS_OR_EQUAL

This problem affects IBM Director Agent. It occurs only on systems running Windows Server 2003.
Problem
During installation of IBM Director Agent, Windows might display the following blue screen trap:
IRQL_NOT_LESS_OR_EQUAL
Investigation
This problem is solved by a Microsoft update. See Microsoft Knowledge Base Article 825236 for more information.
Other operating-system installations troubleshooting

This section provides information for specific problems and workarounds associated with operating-system installations other than Linux and Windows. Review all troubleshooting topics for possible solutions. For additional troubleshooting information, see the IBM Director Release Notes.
Installing an earlier version of IBM Director after installing IBM Director 5.20
This problem affects IBM Director for System i installations.
331
Problem
After you have installed IBM Director 5.20 (5722-DR1 or 5722-DA1) on a System i system, you must completely uninstall IBM Director 5.20 before installing the older version, IBM Director Multiplatform 4.2x (5733-VE1 option 30 or 39). If attempted, IBM Director 5.20 is disabled and IBM Director Multiplatform 4.2x does not work (twgstart will fail).
Investigation
To correct this problem, complete the following steps: 1. Uninstall IBM Director Multiplatform 4.2x (5733-VE1 option 30 or 39). 2. Complete the manual cleanup described in the IBM Systems Software Information Center: IBM Systems Software Information Center 3. Install only one of the following releases: v IBM Director 5.20 (5722-DR1 or 5722-DA1) v IBM Director Multiplatform 4.2x (5733-VE1 option 30 or 39)
The IBM.Director.DirectorCimCore installation fails

This problem affects IBM Director Agent.
Problem
During installation of IBM Director Agent, the following error occurs:
loading default handlers and subscriptions... failed to load default handlers and subscriptions. instal: Failed while executing the ./IBM.Director.DirectorCimCore.post_i script. 0503-464 installp: The installation has FAILED for the "usr" part of the following filesets: IBM.Director.DirectorCimCore 5.10.2.0 installp: Cleaning up software for: IBM.Director.DirectorCimCore 5.10.2.0
Investigation
Check the following possible causes to resolve this problem and complete the installation: v Check that all the preparation steps have been completed as described by Preparing to install IBM Director Server on a System p server in the IBM Director Planning, Installation and Configuration Guide. Complete any skipped steps and try the installation again. v Restore the backup of the CIM repository. Complete the following steps: 1. Identify the CIM repository backup you wish to use. List the backups by typing the following command and pressing Enter:
ls /opt/freeware/cimom/pegasus/etc/repository.backup.*
The final portion of the file name indicates the backup date. Identify the date of the backup you wish to use. 2. Stop the cimserver. Type the following command and press Enter:
/opt/freeware/cimom/pegasus/bin/cimserver -s
332
3. Restore the CIM repository using the backup you have selected. Type the following command and press Enter:
cp -pRh /opt/freeware/cimom/pegasus/etc/repository.backup.date /opt/freeware/cimom/pegasus/etc/repository
4. Start the installation again.
Upgrade and patch installations fail

This problem affects upgrade and patch installations on systems running Windows.
Problem
Upgrade installations and patch installation fail.
Investigation
Do not set the IBM Director Server service startup setting to Automatic. If the IBM Director Server service is set to Automatic, change the setting to Manual and restart the management server. To correct the startup setting for the IBM Director Server service, complete the following steps: 1. From the Windows desktop, click Start Control Panel. 2. Double-click Administrative Tools. 3. Double-click Services. 4. Right-click the applicable IBM Director Service and select Properties. 5. On the General page, in the Startup type list, select Manual. 6. Click OK. The services listed in the following table are installed on the management server (the server running IBM Director Server), the managed system (the system running IBM Director Agent), or both. Attention: Do not change the default startup settings except for troubleshooting purposes when working with IBM Technical Support.
IBM Director Service IBM Director Agent SLP Attributes IBM Director Agent WMI CIM Server IBM Director CIM Listener IBM Director Server IBM Director Support Program IBM SLP SA Default startup setting Automatic Automatic Automatic Manual Automatic Automatic
IBM Director uninstallation fails

This problem affects systems on which the removal of an installation failed for an IBM Director component.
Problem
A failed uninstallation of an IBM Director component can leave files, data, or registry settings that might cause problems for later installations.
333
Investigation
Use the following information to clean up after a failed uninstallation: For AIX: If the uninstallation of one of the IBM Director filesets fails, run the following command:
installp -C
For more information about cleaning up a failed installation, see the pSeries and AIX information center. For i5/OS: If IBM Director uninstallation fails on i5/OS because an object is locked, see the job log for details about the object that caused the failure. Commands such as WRKOBJLCK and DLCOBJ can be used to work with object locks. If a different server has a lock on an IBM Director object, the uninstallation might be completed successfully but the locked IBM Director object might still exist after the uninstallation. If you want to clean up the locked objects, you first might need to end that server to release the locks. Use the normal documented method of ending that server, for example, use ENDTCPSVR instead of ENDJOB. For Linux and VMware: The IBM Director uninstallation script checks for any RPM dependencies. If dependencies are detected, the script lists the dependencies found and then exits. To remove the dependencies, type the following command for each dependency listed:
rpm -ef rpm_name
where rpm_name is the dependency. Note: Occasionally this command might fail. If it does, type rpm -ef rpm_name --noscripts where rpm_name is the dependency. After removing all of the dependencies, run the IBM Director uninstallation script again. For Windows and NetWare: Contact the IBM Technical Support Center for assistance. You must have an IBM Support Line contract.
Getting help and support

If you need help, service, or technical assistance or just want more information about IBM products, you will find a wide variety of sources available from IBM to assist you. This section contains information about where to go for additional information about IBM and IBM products, and whom to call for service, if it is necessary.
Finding information about IBM Director problems

In addition to the IBM Director information center, you can find information about problems and solutions in earlier editions of IBM Director documentation, the IBM Director forum, and the IBM Service Bulletin (RETAIN tip) index.
334
Available troubleshooting documentation for earlier versions of IBM Director

To troubleshoot problems that are specific to earlier versions of IBM Director, see the documentation for that version. Notes: 1. Printable PDFs for the different versions of the IBM Director documentation are available from the IBM Director Support Web page at www.ibm.com/systems/ management/director/. 2. IBM Director versions 3.1.1 and earlier are no longer supported.
IBM Director version Available troubleshooting documentation 5.20 v IBM Director version 5.20 Information Center v Release Notes v Service Bulletin (RETAIN tips) index v IBM Director version 5.10 information center at http://publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/ diricinfo/fqm0_main.html v Release Notes for each version v Service Bulletin (RETAIN tips) index v IBM Director Systems Management Guide, version 4.20 v Release Notes or readme.txt file for each version v Service Bulletin (RETAIN tips) index v IBM Director Systems Management Guide, version 4.11 v readme.txt file for each version v Service Bulletin (RETAIN tips) index v IBM Director Systems Management Guide, version 4.1 v readme.txt file for each version v Service Bulletin (RETAIN tips) index
5.10, 5.10.1, 5.10.2, and 5.10.3
4.20, 4.20.2, 4.21, and 4.22 4.11 and 4.12
4.10 and 4.10.2
Accessing the IBM Director customer forum

The IBM Director customer forum provides a place for customers to share ideas and solutions for IBM Director implementations. Even though this forum is called the xSeries (System x) IBM Director forum, it serves as the forum for IBM Director installations on all supported operating systems and hardware. Although participating in the customer forum does not guarantee an answer from an IBM representative, the forum community does include IBM employees that use IBM Director. To access the forum you must sign in to the IBM developerWorks Web site and create a profile; there is no fee. The IBM Director customer forum Web page is at www.ibm.com/developerworks/forums/dw_forum.jsp?forum=759 &cat=53.
Accessing the IBM Service Bulletin (RETAIN tips) index

You an access the IBM Service Bulletin (RETAIN tips) index to view known problems and workarounds for IBM Director at the following Web address: www.ibm.com/servers/eserver/xseries/systems_management/ibm_director/. On this page, click the applicable version of IBM Director. A list of service bulletins is displayed.
Before you call

Before you call, make sure that you have taken these steps to try to solve the problem yourself: v Check all cables to make sure that they are connected.
335
v Check the power switches to make sure that the system is turned on. v Use the troubleshooting information in your system documentation and the diagnostic tools that are included with your system. You can find information about diagnostic tools for BladeCenter and System x systems in the Problem Determination Service Guide on the IBM System x Documentation CD. You can find information about diagnostic tools for IntelliStation in the IntelliStation Hardware Maintenance Manual at the IBM Support Web site. v Go to the IBM Support Web site at www.ibm.com/support/us to check for technical information, hints, tips, and new device drivers or to submit a request for information. You can solve many problems without outside assistance by following the troubleshooting procedures that IBM provides in the online help or in the publications that are provided with your system and software. The information that is included with your system also describes the diagnostic tests that you can perform. Most BladeCenter, System x, and IntelliStation systems, operating systems, and programs includes information that contains troubleshooting procedures and explanations of error messages and error codes. If you suspect a software problem, see the information for the operating system or program.
Using the hardware documentation

Information about your IBM BladeCenter, System x, or IntelliStation system and any preinstalled software is available in the documentation that is included with your system. That documentation includes printed books, online books, readme files, and help files. See the troubleshooting information in your system documentation for instructions for using the diagnostic programs. The troubleshooting information or the diagnostic programs might tell you that you need additional or updated device drivers or other software. IBM maintains pages on the World Wide Web where you can get the latest technical information and download device drivers and updates. To access these pages, go to www.ibm.com/support/us and follow the instructions. Also, you can order publications through the IBM Publications Ordering System at www.ibm.com/planetwide/.
Getting information from the World Wide Web

On the World Wide Web, the IBM Web site has up-to-date information about IBM BladeCenter, System i, System p, System x, System z, and IntelliStation products, services, and support. Use the following Web addresses for the applicable product information.
IBM product BladeCenter products IntelliStation workstations System i systems System p servers System x servers System z mainframes Web address www.ibm.com/servers/eserver/support/bladecenter/ www.ibm.com/servers/intellistation/pro/already.html www.ibm.com/servers/eserver/support/iseries/ www.ibm.com/servers/eserver/support/unixservers/ www.ibm.com/servers/eserver/support/xseries/index.html www.ibm.com/servers/eserver/support/zseries/
You can find service information for your IBM products, including supported options, at www.ibm.com/support/us.
336
Also, you can find information about IBM Director in the IBM Systems forum at www.ibm.com/developerworks/forums/dw_forum.jsp?forum=759&cat=53.
Information to provide to the IBM Technical Support Center or IBM Director customer forum
When looking for assistance, either from IBM Technical Support Center or in the IBM Director customer forum, there is some basic information that you should provide.
System i information
Before you contact IBM for assistance, or append to the customer forum, you should gather the following information for the affected systems: v The operating system information for management server and for the managed objects. v Whether the failure is intermittent or persistent. v The last time (or release) that the feature or function worked. v Any exceptions or error messages that occur. v The version of IBM Director that is installed. Also note whether it is a new installation or an upgrade installation. If it is an upgrade installation, note from which version of IBM Director you upgraded. v If possible, the steps required to recreate the problem.
System x, BladeCenter, and x86-based system information

Before you contact IBM for assistance, or append to the customer forum, you should gather the following information for the affected systems. Note: Frequently, IBM uses information and logs generated by the Dynamic System Analysis (DSA) program to resolve problems. DSA is available from the Systems Management Web page at www.ibm.com/servers/eserver/xseries/ systems_management/. v The machine types of all the affected systems. v The operating system. v The BIOS and firmware version levels of the affected systems. If you do not know this information, you can use Dynamic System Analysis (DSA) to gather the information for you. v Whether the failure is intermittent or persistent. v The last time the feature or function worked. v Any exceptions or error messages that occur. v The version of IBM Director that is installed. Also note whether it is a new installation or an upgrade installation. If it is an upgrade installation, note from which version of IBM Director you upgraded. v If possible, the steps required to recreate the problem.
System p information
Before you contact IBM for assistance, or append to the customer forum, you should gather the applicable information for the affected systems. For AIX: v The files containing the redirected output from the following commands: oslevel -r lslpp -L lsdev prtconf
337
v v v v v
errpt -a lsvpd The /var/log/dirinst.log file, if you are having an installation problem. Whether the failure is intermittent or persistent. The last time the feature or function worked. Any exceptions or error messages that occur. The version of IBM Director that is installed. Also note whether it is a new installation or an upgrade installation. If it is an upgrade installation, note from which version of IBM Director you upgraded. If possible, the steps required to recreate the problem.
For Linux on POWER v The files containing the redirected output from the following commands: (For Red Hat Linux) cat /etc/redhat-release (For SUSE Linux) cat /etc/SuSE-release rpm -qa lsvpd v The /var/log/dirinst.log file, if you are having an installation problem. v Whether the failure is intermittent or persistent. v The last time the feature or function worked. v Any exceptions or error messages that occur. v The version of IBM Director that is installed. Also note whether it is a new installation or an upgrade installation. If it is an upgrade installation, note from which version of IBM Director you upgraded. v If possible, the steps required to recreate the problem.
System z information
Before you contact IBM for assistance, or append to the customer forum, you should gather the applicable information for the affected systems. v A detailed description of the problem. v Any exceptions or error messages that occur. v If possible, the steps required to recreate the problem. v Whether the failure is intermittent or persistent. v The operating system information for the management server and for the managed objects. v The version of IBM Director that is installed in each affected system. Also note whether it is a new installation or an upgrade installation. If it is an upgrade installation, note from which version of IBM Director you upgraded. v The /var/log/dirinst.log file, if you are having an installation problem. v The /var/log/localmessages or any related log file on manageability access point (MAP) for z/VM. v The /opt/ibm/director/log/TWGRas.log file on the management server.
Getting fixes
Occasionally, new releases and upgrades are made available from the IBM Support Web site at www.ibm.com/systems/management/director/. These releases and upgrades might contain fixes to problems with IBM Director. If your IBM Director environment has a problem that is not fixed by a new release or upgrade, contact the IBM Technical Support Center. To do so, you must have purchased an appropriate support product from IBM.
338
Software service and support

IBM provides a wide range of support products for IBM Director software. For installations on IBM BladeCenter products If you install and use IBM Director Server on BladeCenter products, you can purchase the Implementation Services ServicePac for BladeCenter and xSeries for service and support of IBM Director Server. For installations on System i technology Through IBM Software Maintenance (SWMA), you can get assistance with usage, configuration, and software problems with System i technology. Fixes and updates are part of the warranty of the SWMA product and are included in your license for this product. For installations on System p servers Through IBM Software Maintenance (SWMA), for a fee, you can get telephone or electronic assistance with usage, configuration, and software problems with System p servers. Fixes and updates are part of the warranty of the SWMA product and are included in your license for this product. Note: When ordering or downloading only IBM Director Server, SWMA is optional and must be ordered specifically. For installations on System x servers and IntelliStation workstations Through IBM Support Line, for a fee, you can get telephone assistance with usage, configuration, and software problems. You also can purchase Enhanced Technical Support (ETS), which is a proactive support option to Support Line for System x servers. Through IBM Software Maintenance (SWMA), for a fee, you can get telephone or electronic assistance with usage, configuration, and software problems with System x servers. Fixes and updates are part of the warranty of the SWMA product and are included in your license for this product. If you install and use IBM Director Server on System x servers, you can purchase the Implementation Services ServicePac for BladeCenter and xSeries for service and support of IBM Director Server. For installations on System z mainframes Through IBM Service and Subscription (S&S), for a fee, you can get telephone or electronic assistance for software problems with System z mainframes. Fixes and updates are part of the warranty of this product and are included in your license for this product. For installations on non-IBM hardware If you want to install and run IBM Director Server on non-IBM hardware, you must purchase a license for IBM Director Server. However, this license does not entitle you to service and support of IBM Director Server. You can purchase service and support separately from Support Line. You also can purchase Enhanced Technical Support (ETS), which is a proactive support option to Support Line for non-IBM x86 systems. For information about which products are supported by Support Line in your country or region, go to www.ibm.com/services/us/its/pdf/ remotesupportxseries.pdf. For more information about Support Line and other IBM
339
services, go to www.ibm.com/services/us/index.wss, or go to www.ibm.com/planetwide/ for support telephone numbers. In the U.S. and Canada, call 1-800-IBM-SERV (1-800-426-7378).
340
Appendix A. Accessibility features for IBM Director

Accessibility features help users who have a physical disability, such as restricted mobility or limited vision, to use information technology products successfully.
Accessibility features
The major accessibility features in IBM Director support: v Keyboard-only operation v Interfaces that are commonly used by screen readers v The attachment of alternative input and output devices Tip: The IBM Director Information Center and its related publications are accessibility-enabled for the IBM Home Page Reader. You can operate all features using the keyboard instead of the mouse.
Keyboard navigation
This product uses standard Microsoft Windows navigation keys. In addition, the following tables provide information that addresses the IBM Director Console. Note: v External Application Launch Wizard uses additional keyboard shortcuts for navigating between frames. For more information, see Table 115 on page 343. v Update Manager uses additional keyboard shortcuts for table navigation. For more information, see Table 132 on page 348.
Table 109. Keyboard shortcuts for windows Action Navigate out of the window. Hide the window. Activate the default button (if defined). Table 110. Keyboard shortcuts for option panes Action Navigate in or out of the option pane. Hide a window. Activate the default button (if defined). Table 111. Keyboard shortcuts for scroll panes Action Navigate forward out of the scroll pane. Navigate backward out of the scroll pane. Move up or down. Keyboard shortcut Tab Shift+Tab Up arrow or down arrow Keyboard shortcut Alt+F6 Esc Enter Keyboard shortcut Alt+F6 Esc Enter
341
Table 111. Keyboard shortcuts for scroll panes (continued) Action Move left or right. Navigate to the beginning or end of data. Navigate up or down one block. Navigate to the left or right. Keyboard shortcut Left arrow or right arrow. Ctrl+Home or Ctrl+End PgUp or PgDn Ctrl+PgUp or Ctrl+PgDn
Table 112. Keyboard shortcuts for split panes Action Navigate forward out of the split pane. Navigate backward out of the split pane. Navigate between split panes. Navigate to the splitter bar. Toggle the focus between two split bars (for windows with three split panes). Resize the split pane vertically. Resize the split pane horizontally. Maximize the size of the split pane . Minimize the size of the split pane. Table 113. Keyboard shortcuts for notebooks (tabbed panes) Action Navigate into the tabbed pane. Navigate out of the tabbed pane. Navigate to the left or right tab. Navigate to the tab above or below. Navigate from the tab to the page. Navigate from the page to the tab. Navigate to the previous or next page. Keyboard shortcut Tab Ctrl+Tab Left arrow or right arrow Up arrow or down arrow Enter or Ctrl+Down Ctrl+Up Ctrl+PgUp or Ctrl+PgDn Keyboard shortcut Tab or Ctrl+Tab Shift+Tab or Ctrl+Shift+Tab Tab or F6 F8 F8 Up arrow or down arrow Left arrow or right arrow Home End
Table 114. Keyboard shortcuts for frames Action Display a window menu. Activate the default button (if defined). Keyboard shortcut Alt+Space bar Enter
342
Table 115. Additional keyboard shortcuts for frames in External Application Launch wizard Action To move focus to the description area when focus is currently on any of the first five event filters To move focus to the description area when focus is currently on any other event filter Keyboard shortcut Esc Space bar, then Shift+Tab Note: When you press the space bar, the Event Filter check box that has focus is selected and then focus moves to the first entry field or check box below the description area.
Table 116. Keyboard shortcuts for internal frames Action Open or restore the frame. Close the frame. Move the frame. Resize the frame. Minimize the frame size. Display a window menu. Activate the default button (if defined). Table 117. Keyboard shortcuts for menu bar Action Jump to the menu bar. Navigate out of the menu bar. Navigate within the menu bar. Select the next or previous menu item. Activate the default or selected item. Display a menu. Keyboard shortcut Alt or F10 Esc or Alt Arrow keys Right arrow or left arrow Enter Use one of these keyboard shortcuts: v Up arrow v Down arrow v Enter v Space bar v Alt+Character accelerator key (if defined) Esc or Alt Keyboard shortcut Ctrl+F5, Alt+F5, or Enter Ctrl+F4 or Alt+F5 Ctrl+F7 or Alt+F7 Ctrl+F8 or Alt+F8 Ctrl+F9 or Alt+F9 Alt+Space bar Enter
Hide a menu. Table 118. Keyboard shortcuts for menus Action Display a menu.
Keyboard shortcut Enter or F10

343
Table 118. Keyboard shortcuts for menus (continued) Action Display a submenu. Navigate to the next item or wrap to the top. Navigate to the previous item or wrap to the bottom. Hide the menu. Hide the submenu. Activate the default or selected item. Table 119. Keyboard shortcuts for menu items Action Navigate in or out of a menu. Activate an item. Keyboard shortcut Arrow keys Enter, space bar, or Alt+Character accelerator key (if defined) Right arrow Left arrow or Esc Keyboard shortcut Right arrow Down arrow Up arrow Esc Left arrow Enter
Display a submenu. Hide a submenu. Table 120. Keyboard shortcuts for check-box menu items Action Navigate in or out of the check-box menu. Select or clear a check-box menu item. Hide a check-box menu. Table 121. Keyboard shortcuts for radio-button menu items Action Navigate in or out of a radio-button menu. Select or clear a radio-button menu item. Hide a radio-button menu. Table 122. Keyboard shortcuts for pop-up menus Action Display a pop-up menu. Display a pop-up submenu. Hide a pop-up menu. Hide a submenu. Navigate within a pop-up menu. Activate a pop-up menu item. Table 123. Keyboard shortcuts for toolbar Action Navigate forward out of the toolbar.
Keyboard shortcut Arrow keys Enter Enter
Keyboard shortcut Arrow keys Enter Enter
Keyboard shortcut Shift+F10 Right arrow Esc Left arrow Up arrow or down arrow Enter or space bar
Keyboard shortcut Tab
344
Table 123. Keyboard shortcuts for toolbar (continued) Action Navigate backward out of the toolbar. Navigate within the toolbar. Activate a toolbar item. Display the Customized Toolbar menu (when focus is on an icon on the main IBM Director Console window toolbar). Table 124. Keyboard shortcuts for tool tips Action Display a tool tip. Hide a tool tip. Table 125. Keyboard shortcuts for buttons Action Navigate forward. Navigate backward. Activate the default button. Activate any button Keyboard shortcut Tab Shift+Tab Enter Space bar or Alt+Character accelerator key (if defined). Esc Keyboard shortcut Ctrl+F1 Esc or Ctrl+F1 Keyboard shortcut Shift+Tab Arrow keys Enter Shift+10
Activate Cancel or Close. Table 126. Keyboard shortcuts for check boxes Action Navigate forward. Navigate backward. Navigate within a group. Select or clear a check box. Table 127. Keyboard shortcuts for radio buttons Action Navigate forward. Navigate backward. Navigate within a group.
Keyboard shortcut Tab Shift+Tab Arrow keys Space bar
Keyboard shortcut Tab Shift+Tab Arrow keys Note: To select the radio button, navigate to it. Space bar
Select or clear a radio button. Table 128. Keyboard shortcuts for combination boxes Action Navigate forward out of the combination box. Navigate backward out of the combination box.
Keyboard shortcut Tab Shift+Tab
345
Table 128. Keyboard shortcuts for combination boxes (continued) Action Navigate into a combination box within a table cell (focus must be in the table cell). Display the drop-down list. Hide the drop-down list. Activate the selected menu item. Navigate up or down the drop-down list. Navigate up or down the drop-down list for a combination box in a table. Navigate to a list item without selecting it. Move up or down the drop-down list. Keyboard shortcut F2 Down arrow Esc or Alt+Up arrow Enter Alt+Up arrow or Alt+Down arrow Up arrow or Down arrow Initial character of the list item Up arrow or down arrow
Table 129. Keyboard shortcuts for lists Action Navigate forward out of the list. Navigate backward out of the list. Activate the selected list item. Navigate within the list. Navigate to the beginning or end of the list. Select all list items. Select a single list item Keyboard shortcut Tab Shift+Tab Enter Up arrow or down arrow Ctrl+Home or Ctrl+End Ctrl+A Space bar Note: Using the space bar clears the previous selection. Ctrl+Space bar Shift+Space bar Shift+Up arrow or Shift+Down arrow Shift+Home or Shift+End Shift+PgUp or Shift+PgDn PgUp or PgDn
Select an additional list item. Select a range of list items. Extend the selection up or down one item. Extend the selection to the top or bottom of the list. Extend the selection up or down one block. Navigate up or down a block. Table 130. Keyboard shortcuts for sliders Action Navigate forward out of the slider. Navigate backward out of the slider. Increase the value
Keyboard shortcut Tab Shift+Tab Up arrow or right arrow.
346
Table 130. Keyboard shortcuts for sliders (continued) Action Decrease the value Set the maximum value. Set the minimum value. Increase the value by a set range. Decrease the value by a set range. Table 131. Keyboard shortcuts for tables Action Navigate forward out of the table. Navigate backward out of the table. Navigate to the next cell. Navigate to the previous cell. Navigate to the next row from the last column. Navigate to the previous row from the first column. Navigate vertically to the next or previous block. Navigate horizontally to the left or right one block. Navigate to the first or last cell in the row. Navigate to the first or last cell in the table. Select all cells in the table. Clear the current selection. Keyboard shortcut Ctrl+Tab Ctrl+Shift+Tab Tab or right arrow Shift+Tab or left arrow Tab or right arrow Shift+Tab or left arrow PgUp or PgDn Ctrl+PgUp or Ctrl+PgDn Home or End Ctrl+Home or Ctrl+End Ctrl+A Use one of these keyboard shortcuts: v Up arrow or down arrow v Ctrl+Up arrow or Ctrl+Down arrow v PgUp or PgDn v Ctrl+PgUp or Ctrl+PgUp v Home or End v Ctrl+Home or Ctrl+End Shift+Up arrow or Shift+Down arrow Shift+Left arrow or Shift+Right arrow Shift+Home or Shift+End Shift+PgUp or Shift+PgDn Ctrl+Shift+PgUp or Ctrl+Shift+PgDn Keyboard shortcut Down arrow or left arrow. Home End PgUp PgDn
Extend the selection up or down one row. Extend the selection to the right or left one column. Extend the selection to the beginning or end of the row. Extend the selection up or down one block. Extend the selection left or right one block.
347
Table 131. Keyboard shortcuts for tables (continued) Action Extend the selection to the beginning or end of the column. Edit the cell without overriding the existing text. Delete the cell text before editing. Keyboard shortcut Ctrl+Shift+Home or Ctrl+Shift+End F2 Esc
Table 132. Additional keyboard shortcuts for tables in Update Manager Action Edit the sort order. Sort the table by the selected column in ascending order. Sort the table by the selected column in descending order. Clear the sort. Clear all sorts. Show the filter row. Hide the filter row. Edit the filter. Apply the filter. Deactivate the filter. Clear all filters. Display the find toolbar. Hide the find toolbar. Display the status line. Hide the status line. Table 133. Keyboard shortcuts for trees Action Navigate forward out of the tree. Navigate backward out of the tree. Expand the entry Collapse the entry Navigate up or down one entry. Navigate to the first entry in the tree. Navigate to the last visible entry in the tree. Navigate vertically up or down one block. Navigate to the left or right one block. Select all entries. Clear the selection. Select a single entry. Select a range of entries. Keyboard shortcut Tab Shift+Tab Right arrow or Enter (if collapsed). Left arrow or Enter (if expanded). Up arrow or down arrow Home End PgUp or PgDn Ctrl+PgUp or Ctrl+PgDn Ctrl+A or Ctrl+Slash Ctrl+\ Ctrl+Space bar Shift+Space bar Keyboard shortcut Ctrl+W Ctrl+S Ctrl+Shift+S Ctrl+T Ctrl+Q Ctrl+R Ctrl+Shift+R Ctrl+E Ctrl+Shift+U Ctrl+U Ctrl+K Ctrl+F Ctrl+Shift+F Ctrl+L Ctrl+Shift+L
348
Table 133. Keyboard shortcuts for trees (continued) Action Extend the selection up or down one block. Extend the selection to the top of the tree. Extend the selection to the bottom of the tree. Table 134. Keyboard shortcuts for text fields Action Navigate into the text field Keyboard shortcut Alt+Character accelerator key (if defined). Tab Shift+Tab Left arrow or right arrow Ctrl+Left arrow or Ctrl+Right arrow Home or End Enter Ctrl+A Arrow keys Shift+Left arrow or Shift+Right arrow Shift+Home or Shift+End Ctrl+Shift+Left arrow or Ctrl+Shift+Right arrow Ctrl+C Ctrl+X Ctrl+V Backspace or Delete Keyboard shortcut Shift+PgUp or Shift+PgDn Shift+Home Shift+End
Navigate forward out of the text field. Navigate backward out of the text field. Navigate to the previous or next character. Navigate to the previous or next word. Navigate to the beginning or end of a field. Submit an entry. Select all text in the field. Clear the selection. Extend the selection to the left or right one character. Extend the selection to the beginning or end of the field. Extend the selection to the next or previous word.
Copy the selected text. Cut the selected text. Paste from the clipboard. Delete the previous or next character Table 135. Keyboard shortcuts for text panes Action Navigate into the text pane.
Keyboard shortcut Tab or Alt+Character accelerator key (if defined). Ctrl+Tab Ctrl+Shift+Tab PgUp or PgDn Up arrow or down arrow Left arrow or right arrow
Navigate forward out of the text pane. Navigate backward out of the text pane. Navigate vertically up or down one block. Navigate up or down one line. Navigate to the left or right one component or character.
349
Table 135. Keyboard shortcuts for text panes (continued) Action Navigate to the beginning or end of a line. Navigate to the previous or next word. Navigate to the beginning or end of the text pane. Navigate up or down one block. Navigate to the left or right one block. Navigate to the next or previous HTML link or other element which can receive the focus. Navigate out of a focusable element that accepts a tab. Activate a hyperlink. Extend the selection up or down one block. Extend the selection to the left or right one block. Extend the selection up or down one line. Extend the selection to the left or right. Extend the selection to the beginning or end of the line. Extend the selection to the beginning or end of the text pane. Extend the selection to the previous or next word. Keyboard shortcut Home or End Ctrl+Left arrow or Ctrl+Right arrow Ctrl+Home or Ctrl+End PgUp or PgDn Ctrl+PgUp or Ctrl+PgDn Ctrl+T or Ctrl+Shift+T Ctrl+Tab or Ctrl+Shift+Tab Ctrl+Space bar Shift+PgUp or Shift+PgDn Ctrl+Shift+PgUp or Ctrl+Shift+PgDn Shift+Up arrow or Shift+Down arrow Shift+Left arrow or Shift+Right arrow Shift+Home or Shift+End Ctrl+Shift+Home or Ctrl+Shift+End Ctrl+Shift+Left arrow or Ctrl+Shift+Right arrow Shift+PgUp or Shift+PgDn Ctrl+Shift+PgUp or Ctrl+Shift+PgDn Ctrl+A Arrow keys Ctrl+C Ctrl+X Ctrl+V Backspace or Delete Enter Tab
Extend the selection vertically up or down one block. Extend the selection to the left or right one block. Select all text in the text pane. Clear the selection. Copy the selected text. Cut the selected text. Paste from the clipboard. Delete the previous or next component or character. Insert a line break. Insert a tab.
Interface information
You can choose from a variety of high-contrast color schemes and large font sizes in the IBM Director Console. See the IBM Director Systems Management Guide for more information about configuring IBM Director Console settings.
350
Related accessibility information

You can view the publications for IBM Director in Adobe Portable Document Format (PDF) using the Adobe Acrobat Reader. The PDFs are provided on a CD that is packaged with the product, or you can access them through the IBM Director Information Center.
IBM and accessibility

See the IBM Accessibility Center for more information about the commitment that IBM has to accessibility.
351
352
Appendix B. Default installation directories for IBM Director

The default installation directory in which IBM Director is installed is different for each type of installation.
Table 136. Default installation directories Type of installation AIX i5/OS Linux Windows Directory /opt/ibm/director/ /QIBM/ProdData/Director/ /opt/IBM/director/ \Program Files\IBM\Director\
The location in which you install IBM Director is represented in the documentation as install_root. The examples and procedures in this documentation use the install_root variable and separate subsequent directories with forward slashes (/). Make sure that you use the applicable forward or back slash for your operating system. When you initially install IBM Director, you can select an alternative directory other than the default into which IBM Director is installed. Note: You cannot change the default installation directory when installing on AIX or i5/OS.
353
354
Appendix C. Lightweight Directory Access Protocol authentication properties for IBM Director Server
Default Lightweight Directory Access Protocol (LDAP) authentication properties for IBM Director Server are configured in the dirldap.properties file. The properties defined in the dirldap.properties file are used as default values for the dircli authusrgp command. The dirldap.properties file is in the following location: AIX, Linux, and Windows: install_root\data\dirldap.properties i5/OS: /QIBM/UserData/Director/data/dirldap.properties file, where install_root is the root directory of your IBM Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). Notes: v When editing this file, be aware that the hash character (#) at the beginning of a line causes the contents of the line to be treated as a comment instead of a valid property definition. v After making changes to this file, you must stop and restart IBM Director Server for the changes to take effect. The properties which can be specified in this file are described in the following table.
Table 137. Default LDAP authentication properties for IBM Director Server Property name ldap.auth.jndi Description Specifies whether or not to use the Java Naming and Directory Interface (JNDI) provider. This property should only be set to true if one of the following conditions exists: v IBM Director Server is installed on i5/OS v IBM Director Server is installed on AIX, and not using Pluggable Authentication Module (PAM) authentication. v IBM Director Server is installed on Linux, and not using Pluggable Authentication Module (PAM) authentication. v IBM Director Server is installed on Windows, and using an LDAP server other than Active Directory. Specifies the LDAP authentication mechanism to use: simple anonymous DIGEST-MD5 Specifies the name of the attribute on the LDAP server that specifies the user ID. This attribute is often named uid. Specifies the distinguished name of the LDAP server instance.
ldap.auth.mechanism
ldap.auth.userid.attribute ldap.dn
355
Table 137. Default LDAP authentication properties for IBM Director Server (continued) Property name ldap.enabled Description Specifies whether or not IBM Director Server attempts to authenticate users against an LDAP server. If set to true, IBM Director Server first tries to authenticate using an LDAP server; if the LDAP authentication fails, IBM Director Server tries local authentication. If set to false, IBM Director Server tries local authentication only. ldap.group.auth.mechanism ldap.group.desc.attribute Specifies the authorization mechanism to use when accessing the group information. The default mechanism is anonymous. Specifies the name of the attribute on the LDAP server which contains a text description of the group.
ldap.group.member.attribute Specifies the name of the attribute on the LDAP server that specifies the names of group members for a group entry. This attribute is often named member. ldap.group.name.attribute Specifies the name of the attribute on the LDAP server that specifies the group name for a group entry. This attribute is often named cn. Note: This attribute belongs to the group entry; it is not the attribute of a user entry specifying a group name; IBM Director ignores group specification in the user entry. Specifies the password of the user who is authorized to access the group information. CAUTION: This file is not encrypted. Specifying a password using the dirldap.properties file could pose a security risk. Instead, use the dircli authusrgp command to specify the password. When the dircli authusrgp command is used, password transmission is secure, and the password is encrypted for storage. ldap.group.userid Specifies the user ID of a user who is authorized to access the group information. Leave this blank to use anonymous authentication or to specify with the dircli authusrgp command. Specifies the LDAP server address. Specifies the port number to be used for LDAP authentication requests. By default, this is set to port 389. Specifies a search scope use when finding LDAP entries. This will reduce the portion of the directory which is searched, resulting in increased performance. However, entries that are not in the specified scope will not be found.
ldap.group.pwd
ldap.host ldap.port ldap.search.scope
Examples
The following examples illustrate common configurations of the dirldap.properties file. Configured to use Directory Server for System i on the i5/OS management server as the LDAP server
ldap.enabled=true ldap.host=localhost ldap.port=389 ldap.dn="cn=groups,dc=IBMDirSrv,dc=IBM,dc=COM" ldap.auth.jndi=true ldap.auth.mechanism=anonymous ldap.group.name.attribute=cn ldap.group.member.attribute=member ldap.group.auth.mechanism=anonymous
356
Configured to use Active Directory on a remote server as the LDAP server

ldap.enabled=true ldap.host=myldap.mycompany.com ldap.port=389 ldap.dn="ou=mydepartment,c=US" ldap.auth.jndi=false ldap.auth.userid.attribute=uid ldap.auth.mechanism=DIGEST-MD5 ldap.group.name.attribute=cn ldap.group.member.attribute=member ldap.group.auth.mechanism=anonymous ldap.group.desc.attribute=description
Configured to authenticate only on the operating system of the management server

ldap.enabled=false
Appendix C. Lightweight Directory Access Protocol authentication properties for IBM Director Server
357
358
Appendix D. Installing Software Distribution Premium Edition on Linux

You can install Software Distribution Premium Edition on a Linux management server. To install Software Distribution Premium Edition on the management server, complete the following steps: 1. Stop IBM Director Server by going to a command prompt, typing the following command, and pressing Enter:
where install_root is the root directory of your IBM Director installation. 2. Insert the IBM Director 5.20 Software Distribution Premium Edition CD into the CD-ROM drive. 3. If the CD does not automount, mount the CD-ROM drive. Type the following command and press Enter:
For this command and others in this topic, mnt/cdrom is the mount point of the CD-ROM drive and dev/cdrom is the specific device file for the CD-ROM block device. 4. Change to the directory in which the installation script is located. Type one of the following commands and press Enter.
Option Linux on POWER Linux on System x Linux on System z Description cd /mnt/cdrom/swdist/server/linux/ppc/ cd /mnt/cdrom/swdist/server/linux/i386/ cd /mnt/cdrom/swdist/server/linux/s390/

./install
6. Remove the CD from the CD-ROM drive. 7. Restart IBM Director Server by going to a command prompt, typing the following command, and pressing Enter:
where install_root is the root directory of your IBM Director installation. No further installation is required on managed systems or management consoles.
359
360
Appendix E. Worksheets
This topic contains worksheets you can use to plan your IBM Director environment.
Worksheet: Database planning

After determining what database you will use with IBM Director, use this worksheet to record information you will need when installing IBM Director Server or configuring IBM Director Server to use the database.
Information Selected database application Server on which database will be installed Server on which IBM Director Server will be installed Value
Database configuration information

This information may be used to configure the database using the wizard during installation, or to set options in a database-configuration response file for use with the cfgdbcmd command.
Database configuration attribute DbmsApplication Description The selected database application. One of the listed values: v Apache Derby v DB2 v Microsoft SQL Server v Oracle v PostgreSQL The TCP/IP listener port for the database. One of the following default values, or a custom value: v Apache Derby: n/a v IBM DB2 Universal Database: 5000 v Microsoft SQL Server: 1433 v Oracle: 1521 v PostgreSQL: 5432 The server name on which the database is located. Not required for Apache Derby. The database name. Not required for Apache Derby. The user ID for the database. Not required for Apache Derby. The password for the database. Not required for Apache Derby. Value
DbmsTcpIpListenerPort
DbmsServerName DbmsDatabaseName DbmsUserId DbmsPassword
361
Additional configuration information for Oracle databases

Database configuration attribute DbmsAdminId DbmsAdminPassword DbmsTableName DbmsTableFile DbmsTableFileSize DbmsTempTableName DbmsTempTableFile DbmsTempTableFileSize Description The administrator user ID for the database. The administrator password for the database. The table space name for the database. The table space datafile for the database. The table space size. The temporary table space name for the database. The temporary table space datafile for the database. The temporary table space size. IBM_DIRECTOR_DATA_TS IBM_DIRECTOR_DATA_DF 500 IBM_DIRECTOR_TEMP_TS IBM_DIRECTOR_TEMP_DF 50 Value
Worksheet: Installing IBM Director Server

Use this worksheet when planning your installation to record information you will need when you install IBM Director Server.
Complete this section for all IBM Director Server installations Installation type h Standard installation h Express installation Installation path Service account information Computer name: User name: Password: Encryption Enable encryption h Yes h No Encryption algorithm: h Advanced Encryption Setting h Data Encryption Setting h Triple DES Softwaredistribution packages Location for packages created by IBM Director Server: Location for packages received by IBM Director Server: See Choosing between standard and express installation of IBM Director Server.
362
Complete this section for standard IBM Director Server installations only (not required for express installation) Optional features h BladeCenter Management h External Application Launch Wizard h IBM Server Storage Provisioning Tool h IBM Remote Deployment Manager extension h IBM Virtualization Manager extension h Capacity Manager extension h Hardware Management Console extension h Rack Manager h Electronic Service Agent extension h IBM PowerExecutive extension h IBM Director Remote Control Agent
h Software Distribution h System Availability Premium Edition h z/VM Center extension extension h System x Management Extension
See Choosing IBM Director optional components and extensions. Network settings Enable all NICs Network timeout: Enable Wake on LAN Remote control options Require user authorization for system access Disable screen saver Disable background wallpaper Yes h Yes h No h No h Yes h No h
Yes h Yes h
No h No h
Related tasks Using IBM Director in a high-availability environment on page 291 If IBM Director will be used in a high-availability environment, you need to prepare the environment for IBM Director, and you might need to configure IBM Director properties for running in high-availability environments. Planning IBM Director users and user groups on page 120 Before deploying IBM Director, you should determine what IBM Director user roles to define for your organization. In addition, you should determine the user authentication type that will best meet your needs.
Appendix E. Worksheets
363
364
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
365
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation MW9A/050 5600 Cottle Road San Jose, CA 95193 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBMs future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
366
Trademarks
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: AIX Asset ID BladeCenter DB2 DB2 Universal Database developerWorks DirMaint DS4000 DS6000 FlashCopy Electronic Service Agent Enterprise Storage Server eServer i5/OS IBM IBM logo IntelliStation Informix iSeries Lotus Notes Multiprise Netfinity NetServer NetView OS/400 PC 300 POWER Predictive Failure Analysis pSeries Redbooks RETAIN S/390 ServeRAID ServerProven ServicePac SP SurePOS System i System p System Storage System x System z System z9 Tivoli Tivoli Enterprise Tivoli Enterprise Console Tivoli Management Environment
Virtualization Engine Wake on LAN xSeries z/OS z/VSE z/VM zSeries Adobe, Acrobat, and Portable Document Format (PDF) are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both. Intel, Itanium, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. Java and all Java-based trademarks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. Red Hat and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc., in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others.
367
368
Index A
accessibility 5, 341 features 341 keyboard 341 shortcut keys 341 Advanced System Management 135 AIX installing IBM Director Agent 234 IBM Director Console 210 AIX installation IBM Director Server 173 modifying Wake on LAN, enabling 325 alert-forwarding strategy, service processors 53 alerts definition 116 ISMP and limitations 50 MPA Agent, role of 50 out-of-band 51 System Health Monitoring, role of 50 all events filter 19 Apache Derby 90 applications, running external 27 ASF 85 generating events 116 ASM 135 ASM interconnect gateway gateway service processors 49 ISMPs, enabling communication with 49 ASM interconnect network definition 49 gateway service processor, role of 49 ASM PCI adapter alert-forwarding strategies 53 use as a gateway service processor 49 ASM processor alert-forwarding strategies 53 Asset ID operating systems, supported 81 associations default 8 description of 6 options 8 types of 6 attributes, SMI-S 57 Auto Rename 37 BladeCenter chassis assigning IP addresses manually 296 DHCP server, using 296 discovering (automatically) 296 IP address conflicts 296 deployment infrastructure DHCP server, using 296 IP address conflicts 296 documentation ix network devices 88 products, supported tasks 88 BladeCenter Configuration Manager operating systems, supported 83 BMC 87, 135 books ix Brocade switches 89
D
dacimlist startup script 318, 328 dasnmp startup script 318, 328 Data Encryption Standard 48 database configuring 125 DB2 database Linux installation 125 Windows installation 125 function of 5 Microsoft Data Engine 2000 126 Microsoft SQL Server 126 Oracle Server JDBC driver 131 overview 131 planning 107 PostgreSQL 133 preparing 125 selecting 107 SQL Server 2000 Desktop Engine 126 databases Apache Derby 90 for management servers 90 IBM Cloudscape 90 IBM DB2 90 Microsoft Data Engine 90 Microsoft SQL Server 90 MS Jet 90 MSDE 90 Oracle Server 90 PostgreSQL 90 supported 90 date and time event filters 21 DB2 database Linux installation 125 Windows installation 125 default associations 8 default directory 353 definitions ASM interconnect network 49 gateway service processor 49 in-band communication 49 interprocess communication 49 out-of-band communication 49 deployment infrastructure (BladeCenter) DHCP server, using 296 IP address conflicts 296 DES 48 design strategies, event action plan 117 device driver LM78 330 SMbus 330 DHCP server 296 Diffie-Hellman key exchange 48 Digital Signature Algorithm 43 DirAdmin 46, 275 diragent.rsp 234 diragent.rsp file upgrading IBM Director Agent using Software Distribution 231, 256, 269
C
Capacity Manager management server, installing on 199 category event filters 21 chassis (BladeCenter) DHCP server, using 296 discovering (automatically) 296 IP address conflicts 296 manually assigning IP addresses 296 chassis managed objects displayed in IBM Director Console (screenshot) 296 CIM Browser 9 operating systems, supported 81 CIM class shortcut, description of 9 CIM-class method shortcut, description of 9 CIMOM migrating data 272 command processing 38 command-line interface 64 command-task files definition of 28 Common Information Model (CIM) 9 communication out-of-band, service processor 51 compatibility documents ix Compatibility Documents 73 concepts 1 discovery 11 Configuration Manager 88 Configure SNMP Agent operating systems, supported 81 critical events 19 events filter 19 customer service 339 customer support ix
B
bandwidth issues 38 baseboard management controller 87 Baseboard Management Controller 135 blade servers total BladeCenter units 88
369
dircon.rsp file customizing 219 location 219 dirinstall script IBM Director Agent 223, 240 IBM Director Console 214 IBM Director Server 173, 180, 187, 193 dirserv.rsp file customizing 209 location 209 DirSuper 46, 275 diruninstall script 321 diruns utility 323 disability 5, 341 discovery BladeCenter chassis 296 concept 11 scalable objects 42 documentation ix, 335 domain controller 106 downloading ix compatibility documents ix hardware compatibility information ix IBM Director code ix IBM Director publications ix Net-SNMP, version 5.2.1 318, 328 systems-management software ix DS300 89 DS400 89 DS4000 89 DS6000 89 duplication event filter 19 dynamic groups 30
E
encryption algorithms 48 enabling on managed system AIX 234 i5/OS 235, 236 Linux 238, 241, 243 Windows 246 enabling on management server Linux 180, 193 Windows 199 overview 48 performance penalty 48 Enhanced Technical Support 339 environment planning 92 ports used 71 reviewing 92 environment (illustration) 1 environmental sensor events filter 19 error message Could not detect rpm 329 depmod: *** Unresolved symbols 330 installation package cannot be installed by Windows Installer service 330 IRQL_NOT_LESS_OR_EQUAL 331 loading default handlers and subscriptions 332
error message (continued) The open procedure for service PerfDisk 330 event availability 120 definition 116 how they work 116 i5/OS-specific 19 log error after restarting 330 management 118 overview 116 processing 17 publishing 120 sources that generate 116 types alert 116 availability 120 resolution 116 Windows-specific 19 Event Action Plan wizard access to, restricting 279, 285, 290 event action plans 118 design strategies 117 example 119 filtering 21 grouping systems 119 how events work 116 naming conventions 118 overview 118 planning and designing 117 process monitors 27 resource monitors 27 structuring 119 successful implementation 118 wizard 118 event filters category 21 date and time 21 duplication event filter 19 event text 21 event type 21 exclusion event filter 19 extended attributes 21 Hardware Predictive Failure events 19 managed objects 21 severity levels 21 simple event filter 19 structuring 120 system variables 21 threshold event 19 event filter 19 Event Log operating systems, supported 81 event text event filters 21 event type event filters 21 examples event action plan 119 exclusion event filter 19 Express installation planning 103 extended attributes event filters 21
extensions publishing events 120 External Application Launch management server support 83 operating systems, supported 81, 83 External Application Launch wizard operating systems, supported 81 external application tasks command-task files 28 definition of 27 icons for 28 Java resource bundles 28 resources for 28 targeted 29 untargeted 29 external applications, starting with IBM Director 27
F
fatal events filter 19 features, accessibility 341 File Transfer operating systems, supported file-distribution server configuring 316 considerations 56 setting up 315 firewall access configuring 71 firewalls 95, 135 fixes 338 forum 335 81
G
gateway service processor, definition getting fixes 338 group profile 283 grouping managed systems 119 groups description of 30 scalable object 31, 41 types of 30 49
H
hardware predictive failure events 19 predictive failure events filter 19 requirements 67 hardware compatibility ix hardware requirements 67, 68, 69 Hardware Status management server support 83 operating systems, supported 81, 83 harmless events filter 19 help, IBM Director resources ix HelpCenter 337
I
i5/os installing, IBM Director Console 210
370
i5/OS 235, 236 adding users for IBM Director Server 283 events 19 group profiles 283 installing IBM Director Agent 157 IBM Director Server 142, 178 user profiles 283 i5/OS installation encryption, enabling 235, 236 IBM Director Agent, installing 235, 236 starting 235, 236 IBM Cloudscape 90 IBM DB2 90 IBM Director components of 1 concepts 1 getting started 1 IBM Director Console 1 overview 1 scenarios 1 updating 272 upgrading 264 user IDs 290 IBM Director Agent AIX 234 AIX, installing on encryption, enabling 234 BladeCenter chassis 88 server 88 description of 36 encryption, enabling AIX 234 i5/OS 235, 236 Linux 223, 238, 241, 243 Windows 246 function 4 generating events 116 hardware requirements 67, 68, 69 i5/OS installing 157 IBM Director tasks 88 installing AIX 155 Linux for System x 158 System p 158 using Software Distribution 254 Windows 161 installing on AIX 234 license 4, 123 Linux, installing on dirinstall script 223, 238, 240, 241, 243 Net-SMNP, enabling 223, 238, 240, 241, 243 Wake on LAN, enabling 238, 241, 243 modifying an installation NetWare 258 NetWare, installing on features, selecting 244 network driver, configuring 244 network protocols 70
IBM Director Agent (continued) operating systems, supported 73, 77 preparing, for installation 155, 158, 161 troubleshooting 329, 332 installing 331 uninstalling Linux 321 NetWare 323 Windows 322 upgrading 266 Software Distribution task, using 267 Windows, installing on encryption, enabling 246 features, selecting 246, 252 InstallShield wizard, using 246 network driver, configuring 246, 252 securing managed system 246 security state, setting 246 software-distribution settings 246 Wake on LAN, enabling 246, 252 IBM Director Console 64, 217 authorizing users 275, 282 features, selecting 217 function 5 hardware requirements 67, 68 installing 210 AIX 152 Linux for System x 152 System p 154 System z 153 Windows 154 installing on AIX 210 Linux 212 Linux for POWER 215 installing on Linux 214 installing on Windows dircon.rsp file 219 InstallShield wizard, using 217 unattended mode, using 219 license 5, 123 network protocols 70 operating systems, supported 73, 77 overview 1 preparing, for installation 152, 153, 154 uninstalling Linux 321 Windows 322 IBM Director Console installation 217 IBM Director Core Service installing Linux for System x 163 Windows 166 installing on Linux for POWER 224 Windows 226, 228 preparing, for installation 163, 166 IBM Director Core Services description of 35 function 3 installing 162 System p 162 using Software Distribution 230
IBM Director Core Services (continued) license 3 preparing, for installation 162 troubleshooting 329 IBM Director Hardware and Software Compatibility document ix IBM Director Server AIX, installing on 173 configuration data 321 encryption, enabling Linux 180, 193 Windows 199 function 5 hardware requirements 67, 68, 69 i5/OS installing 142, 178 installing Linux for System x 143 System p 140, 150 Windows 151 installing on Windows dirserv.rsp file 209 unattended mode, using 209 license 5, 123 Linux, installing on database, configuring 180, 187, 193 network protocols 70 operating systems, supported 73, 77 preparing, for installation 140, 143, 150, 151 service processors, communication with 49 troubleshooting 329 uninstalling Linux 321 Windows 322 upgrading 265 where to install 106 Windows, installing on database configuration 199 encryption settings 199 features, selecting 199 network driver, configuring 199 service account 199 Software Distribution settings 199 Wake on LAN, enabling 199 IBM eServer Information Center ix IBM systems-management software downloading ix overview ix IBM Technical Support Center 337 IBM Web sites eServer Information Center ix Redbooks ix ServerProven ix Support ix Systems Management Software ix xSeries Systems Management ix IBM.Director.DirectorCimCore troubleshooting 332 illustrations IBM Director environment 1 IBM Director software components 2 in-band communication 50 definition 49 enabling 50 Index
371
in-band communication (continued) ISMPs, limitations 50 MPA Agent, role of 50 information to provide 337 installation default directory 353 Windows 330 installations troubleshooting 333 installing IBM Director Agent using, Software Distribution 254 IBM Director Console AIX 210 Linux for POWER 215 Linux for System x 212 overview 210 IBM Director Core Service Linux for POWER 224 Windows 226, 228 IBM Director Core Services using, Software Distribution 230 IBM Director Server i5/OS 178 troubleshooting 332 InstallShield wizard IBM Director Agent 246 IBM Director Console 217 IBM Director Server 199 Integrated System Management Processor 135 Intel Itanium IBM Director Agent installing 243 Intelligent Platform Management Interface 135 interim fixes ix interprocess communication, definition 49 Inventory operating systems, supported 81 IP address conflicts, troubleshooting 296 IPMI 135 IPMI baseboard management controller generating events 116 ISMP 135 alert-forwarding strategies 53 limitations on in-band communication 50
Level-1 managed system preparing, for installation 162 Level-1 managed systems 35 Level-2 managed system 4 running Windows 330 Level-2 managed systems 36 license IBM Director Agent 4, 123 IBM Director Console 5, 123 IBM Director Core Services 3, 123 IBM Director Server 5, 123 managed systems 123 management console 123 management server 123 Linux installation 329 Linux for POWER installing IBM Director Console 215 IBM Director Core Service 224 Linux for System x installing IBM Director Console 212 Linux installation encryption, enabling 180, 193, 238, 241, 243 IBM Director Agent 223, 238, 240, 241 IBM Director Console 214 IBM Director Server 180, 187, 193 Intel Itanium IBM Director Agent 243 modifying adding a feature 261 removing a feature 261 SNMP Access and Trap Forwarding, enabling 318, 328 Wake on LAN, enabling 325 starting 223, 238, 240, 241, 243 uninstalling 321 LM78 device driver 330
M
managed objects description of 32 event filters 21 types 53 types of 32 managed system authorizing request access 291 request access authorizing 291 managed systems definition 1 distribution preferences, configuring 317 hardware requirements 67, 68, 69 license 123 preparing Windows XP 170 securing IBM Director Agent installation, during 246 security states 43 management console 5
J
Java resource bundles 28 JDBC driver, Oracle Server 131
management console (continued) definition 2 hardware requirements 67, 68 license 123 management processor generating events 116 Management Processor Assistant Agent managed system, installing on 244, 246 NetWare, installing on 244 management server choosing 106 DB2 database Linux installation 125 Windows installation 125 definition 1 hardware requirements 67, 68, 69 license 123 Software Distribution, installing Linux 359 mass-configuration profiles 36 Message Browser description of 26 Microsoft Knowledge Base Article 825236 331 Microsoft Data Engine 90 Microsoft Data Engine 2000 126 Microsoft SQL Server 90, 126 migration CIMOM data 272 minor events filter 19 modifying an IBM Director installation AIX installation Wake on LAN, enabling 325 Linux installation adding a feature 261 removing a feature 261 SNMP Access and Trap Forwarding, enabling 318, 328 Wake on LAN, enabling 325 NetWare installation adding a feature 258 limitations 258 Windows installation adding a feature 260 Program Maintenance window 260 removing a feature 260 MPA events service processors 53 MS Jet 90 MSDE 90 MSI troubleshooting 330
K
keyboard 341 keys files, location of 44 origin of, determining 46
N
N3700 89 N5200 89 naming conventions 37 Net-SNMP, version 5.2.1 318, 328 NetWare installation IBM Director Agent, installing 244 modifying adding a feature 258 limitations 258
L
Level 1 managed system 3
372
NetWare installation (continued) MPA Agent, when to install 244 uninstalling 323 Network Configuration operating systems, supported 81 network latency 38 network protocols 70 network-timeout setting 38 new release 338 New Scheduled Job window 233, 258, 271 newsgroup 335 notifications definition 116
O
operating system compatibility ix support for tasks 80 supported 73 Oracle Server 90 JDBC driver 131 overview 131 out-of-band communication definition 49 service processor 51
P
patch troubleshooting 333 PET, generating events 116 phone number 339 physical platform managed objects Auto Rename 37 planning database 107 Express installation 103 firewalls 95 ports 95 proxy servers 95 planning and designing event action plans 117 ports 71, 95, 135 PostgreSQL 90 JDBC driver 133 overview 133 Power Management management server support 85 operating system support 85 operating systems 85 service processor 87 Wake on LAN 87 preparing AIX IBM Director Agent, installation of 155 IBM Director Console, installation of 152 firewalls 135 Level-1 managed system 162 Linux for System x IBM Director Agent, installation of 158
preparing (continued) Linux for System x (continued) IBM Director Console, installation of 152 IBM Director Core Service, installation of 163 IBM Director Server, installation of 143 ports 135 proxy servers 135 System p IBM Director Agent, installation of 158 IBM Director Console, installation of 154 IBM Director Core Services, installation of 162 IBM Director Server, installation of 140, 150 System z IBM Director Console, installation of 153 Windows IBM Director Agent, installation of 161 IBM Director Console, installation of 154 IBM Director Core Service, installation of 166 IBM Director Server, installation of 151 problem solving 329, 335 Process Management operating systems, supported 81 process monitors 27 event 118 profiles mass-configuration 36 proxy servers 95, 135 publications ix
Remote Supervisor Adapter (continued) documentation ix use as an ASM interconnect gateway 49 request access authorizing, on a managed system 291 avoiding 45 requirements 67 hardware 67 resolution definition 116 resource bundles, Java 28 resource monitors 27 Resource Monitors events 118 operating systems, supported 81 response file dircon.rsp 210, 212, 215, 224, 226, 228 modifying 210, 212, 215, 224, 226, 228 RETAIN tips 335 RS-485 ports 49
S
scalable nodes, description of 40 scalable objects description of 39 discovering 42 groups used with 31, 41 scalable partitions power operations 41 scalable partitions, description of 40 scalable systems 41 scenarios 1 secured system avoiding request access 45 secured systems avoiding request access 45 security 279 Digital Signature Algorithm 43 encryption algorithms 48 performance penalty 48 events filter 19 IBM Director Agent-Server authentication 42 key management location of files 44 origin of a key, determining 46 public and private keys 44 user administration default profile, creating 290 editing groupr privileges 279 editing user privileges 285 Event Action Plan wizard, restricting access to 285, 290 group access, restricting 279, 285 task access, restricting 279, 285 user login 275 security states 43 Server Configuration Manager operating systems, supported 83 ServeRAID Manager managed system, installing on 244, 252 Index
Q
QLogic BladeCenter switches 89
R
Rack Manager management console, installing on 217 management server, installing on 199 operating systems, supported 81 Red Hat Enterprise Linux AS, ES, and WS, version 3.0 162 Redbooks ix related information ix releases, new 272 Remote Control operating systems, supported 81 Remote Control Agent managed system, installing on 246 management server, installing on 199 Remote Session operating systems, supported 81 Remote Supervisor Adapter 87, 135 alert-forwarding strategies 53
373
Service and Subscription (S&S) 339 service bulletin index 335 Service Location Protocol 296 service packs ix service processor 135 Power Management 87 service processors 85 alert-forwarding strategies 53 communicating with IBM Director Server interprocess communication 49 over the ASM interconnect 49 over the LAN 49 communication with IBM Director Server 49 description of 49 documentation ix generating events 116 in-band communication MPA Agent, role of 50 operating system 50 service processor type 50 managed-object types 53 out-of-band communication 51 ServicePac 339 severity levels event filters 21 shortcut keys 341 shortcuts 9 silent parameter 209, 219, 228, 249, 253 simple event filter definition 19 predefined filters 19 SMBIOS 67 SMbus device driver 330 SMI-S attributes 57 SMI-S storage devices 57 SNMP generating events 116 SNMP Access and Trap Forwarding enabling on Linux 318, 328 SNMP devices definition 1 description of 54 operating systems, supported 81 SNMP traps event log 54 snmpconf utility 318, 328 snmpd.conf file 318, 328 software components (illustration) 2 software distribution methods redirected distribution 55 streaming from management server 55 preferences, configuring 315 upgrading IBM Director Agent overview 267 software package, installing 233, 258, 271 Software Distribution operating systems, supported 81 Software Distribution (Premium Edition) installing on the management server Linux 359 Software Distribution task installing IBM Director Agent 254
Software Distribution task (continued) installing IBM Director Core Services 230 Software Maintenance (SWMA) 339 software packages creating 231, 256, 269 solving problems 329, 335 SQL database 90 SQL Server 2000 Desktop Engine 126 starting programs with event action plans 118 static groups 30 Storage products, supported tasks 89 storage devices 57 storage events filter 19 structure event action plan 119 event filters 120 subscription services 272 support z/VM guest operating systems 113 Support Line 339 System Accounts operating systems, supported 81 System Health Monitoring support for Linux systems 50 System i preparing, for installation 142, 157 system variables event filters 21
thresholds event action plans 118 toolbar User Administration 275, 282, 290 trademarks 367 Triple DES 48 troubleshooting IBM Director Agent 329, 332 installing 331 IBM Director Core Services 329 IBM Director Server 329 IBM.Director.DirectorCimCore 332 installations 333 installing 332 MSI administrative installation 330 patch 333 steps to take 335 uninstallation 333 upgrade 333 TWGshare 56
U
unattended installations IBM Director Console 219 IBM Director Server 209 unattended parameter 209, 219, 228, 249, 253 uninstallation troubleshooting 333 uninstalling IBM Director configuration data, retaining 321 Linux 321 NetWare 323 Windows 322 unknown events filter 19 untargeted tasks 29 update manager definition 60 Update Manager operating systems, supported 81 updates, new 272 upgrade 338 migrating CIMOM repository 272 troubleshooting 333 upgrading IBM Director 264 IBM Director Agent 266 Windows 251 IBM Director Console Windows 266 IBM Director Server 265 Software Distribution task, using 231, 256, 269 user IDs Director 290 operating system 275, 282 profiles 275, 282, 290 user accounts DirAdmin and DirSuper 46 management server running Linux 46 management server running Windows 46 service account 46 user administration 275
T
targeted tasks 29 tasks event action plans 118 external 27 management server support 80 Mass Configuration 36 operating systems, supported 80 performing on multiple groups 30 publishing events 120 targeted 29 untargeted 29 User Administration 275, 282, 290 user-defined 27 terminology alert 116 ASM interconnect network 49 event 116 gateway service processor 49 in-band communication 49 interprocess communication 49 managed system 1 management console 2 management server 1 notification 116 out-of-band communication 49 resolution 116 SNMP device 1 update manager 60 threshold event filter 19 simple event filter 19
374
user administration (continued) default profile, creating 290 DirAdmin group 275 DirSuper group 275 editing group privileges 279 editing user privileges 285 Event Action Plan wizard, restricting access to 279, 285, 290 group access, restricting 279, 285 task access, restricting 279, 285 User Administration task 275, 282, 290 User Administration window 290 User Defaults Editor 290 user interfaces, types of 64 user profile 283 user-defined tasks 27
V
virtualization z/VM 113 Virtualization Engine 332 VMware authorizing, request access
291
W
Wake on LAN 85 enabling on AIX 234 enabling on Linux and AIX 325 enabling on Windows IBM Director Agent, installing 246, 252 IBM Director Server, installing 199 Power Management 87 WAN link 92 warning events filter 19 Web site IBM Director resources ix IBM Redbooks ix IBM ServerProven ix IBM Support ix IBM Systems Management Software ix IBM xSeries Systems Management ix Web sites Net-SNMP 318, 328 Oracle Technology Network 131 windows IBM Director Console IBM Update Assistant 231, 256, 269 Program Maintenance 260 Windows event log generating events 116 events 19 installation event log error 330 installing IBM Director Core Service 226, 228
windows (IBM Director) IBM Director Agent installation (NetWare) Choose destination location 244 InstallShield Wizard complete 244 Select Components 244 IBM Director Agent installation (Windows) 246 Feature and destination directory selection 246 Network driver configuration 246 Security settings 246 Software Distribution settings 246 IBM Director Console Add Share Name 316, 317 IBM Update Assistant 231, 256, 269 IBM Update Package/Root Directory 231, 256, 269 Managed System Distribution Preferences 317 New Scheduled Job 233, 258, 271 Server Preferences 316 Software Distribution Manager (Premium Edition) 231, 256, 269 Software Distribution Manager (Standard Edition) 231, 256, 269 Software Distribution Preferences 315 User Administration 290 User Defaults Editor 290 IBM Director Console installation Feature and destination directory selection 217 IBM Director Server installation 199 DB2 Universal Database configuration 199 Encryption settings 199 Feature and installation directory selection 199 IBM Director database configuration 199 Microsoft SQL database configuration 199 Network driver configuration 199 Oracle database configuration 199 service account information 199 Software-distribution settings 199 Windows installation encryption, enabling 199, 246 IBM Director Agent 245 IBM Director Console 217 IBM Director Server 199 modifying adding a feature 260 removing a feature 260 uninstalling 322 Windows Installer 330 Windows Management Instrumentation (WMI) generating events 116 Windows Server 2003, troubleshooting 331 Windows XP preparing managed system 170
Wired for Management (WfM) specifications 67 wizards Event Action Plan 118 InstallShield IBM Director Agent 246 IBM Director Console 217 IBM Director Server 199
Index
375
376
Readers Comments Wed Like to Hear from You

IBM Systems IBM Director Planning, Installation, and Configuration Guide Version 5.20 Update 1 Publication No. GC30-4163-00 We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy, organization, subject matter, or completeness of this book. The comments you send should pertain to only the information in this manual or product and the way in which the information is presented. For technical questions and information about products and prices, please contact your IBM branch office, your IBM business partner, or your authorized remarketer. When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use the personal information that you supply to contact you about the issues that you state on this form. Comments:
Thank you for your support. Submit your comments using one of these channels: v Send your comments to the address on the reverse side of this form. If you would like a response from IBM, please fill in the following information:
Name Company or Organization Phone No.
Address
E-mail address
___________________________________________________________________________________________________
Readers Comments Wed Like to Hear from You

GC30-4163-00
Cut or Fold Along Line
Fold and _ _ _ _ _ _ _ _ _ _Fold and_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please _ _ _ _ _ staple _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Tape _ _ _ _ _ _ _ _ Tape _ _ _ _ do not _ _ _ _ NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES
BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK POSTAGE WILL BE PAID BY ADDRESSEE
International Business Machines Corporation PO Box 12195 Research Triangle Park NC U.S.A. 27709-9990
_________________________________________________________________________________________ Please do not staple Fold and Tape Fold and Tape
GC30-4163-00
Cut or Fold Along Line
Printed in USA
GC30-4163-00

Dir5.20 Docs Install

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Dir5.20 Docs Install

Загружено:

Авторское право:

Доступные форматы

IBM Systems

New in IBM Director . . . . . . . . . xiii

Chapter 1. Getting started with IBM Director . . . . . . . . . . . . . . . 1

Chapter 3. Installing . . . . . . . . 123

. 326 . 327 . 328

Chapter 6. Troubleshooting . . . . . 329

Chapter 4. Uninstalling IBM Director

. 322 . 323 . 323 . 324

Chapter 5. Modifying an IBM Director installation . . . . . . . . . . . . 325

Worksheet: Database planning . . . . . Worksheet: Installing IBM Director Server .

Notices . . . . . . . . . . . . . . 365 Trademarks . . . . . . . . . . . . 367 Index . . . . . . . . . . . . . . . 369

IBM Director Planning, Installation, and Configuration Guide

. 257 . 259 . 260 . 261

16. 17. 18. 19.

Copyright IBM Corp. 1999, 2007

IBM Director Planning, Installation, and Configuration Guide

Copyright IBM Corp. 1999, 2007

230 234 236

238 240 242 246 249 251 254

IBM Director Planning, Installation, and Configuration Guide

About this book

Conventions and terminology

IBM Director resources on the World Wide Web

IBM Director Planning, Installation, and Configuration Guide

IBM Redbooks publications

About this book

Remote Supervisor Adapter

How to send your comments

IBM Director Planning, Installation, and Configuration Guide

New in IBM Director

New in version 5.20.1

Support for new hardware

IBM Director support for new operating systems

Updated database support

IBM Director Planning, Installation, and Configuration Guide

Additional changes in version 5.20.1

New in version 5.20

Improvements to the installation procedure for IBM Director

Improvements to the way you work in IBM Director

IBM Director Planning, Installation, and Configuration Guide

IBM Director Agent support for new hardware

Discontinued features in version 5.20

IBM Director Planning, Installation, and Configuration Guide

Chapter 1. Getting started with IBM Director

Introducing IBM Director

IBM Director environment

Copyright IBM Corp. 1999, 2007

Figure 1. Hardware in an IBM Director environment

IBM Director components

IBM Director Planning, Installation, and Configuration Guide

Figure 2. Software in an IBM Director environment

IBM Director Core Services

IBM Director Agent

IBM Director Console

IBM Director Planning, Installation, and Configuration Guide

IBM Director Server

Chapter 1. Getting started with IBM Director

IBM Director Planning, Installation, and Configuration Guide

Chapter 1. Getting started with IBM Director

IBM Director Planning, Installation, and Configuration Guide

Common Information Model

Chapter 1. Getting started with IBM Director

Shortcuts to CIM classes and methods