Dir5.20 Docs Express Install
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Dir5.20 Docs Express Install as PDF for free.
More details
- Words: 68,832
- Pages: 198
IBM Systems
IBM Director Express Planning, Installation and Configuration Guide Version 5.20
IBM Systems
IBM Director Express Planning, Installation and Configuration Guide Version 5.20
Note Before using this information and the product it supports, read the information in Appendix C, "Notices."
First Edition (December 2006) This edition applies to version 5.20 of Software Distribution Premium Edition extension 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, 2006. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents About this book . . . . . . . . . . . v Conventions and terminology . . . . . . . . v Related information . . . . . . . . . . . . v How to send your comments . . . . . . . . viii
Installing IBM Director Server on Linux for System z using the Express installation option Adding Standard installation options to an IBM Director Express installation . . . . . . . .
. 63 . 65
New in version 5.20 . . . . . . . . . ix
Chapter 5. Installing IBM Director Console . . . . . . . . . . . . . . 67
Chapter 1. Getting started with IBM Director . . . . . . . . . . . . . . . 1
Installing IBM Director Console on AIX . . . . Installing IBM Director Console on Linux for System x . . . . . . . . . . . . . . Installing IBM Director Console on Linux for System z . . . . . . . . . . . . . . Installing IBM Director Console on Linux for POWER . . . . . . . . . . . . . . Installing IBM Director Console on Windows . . Installing IBM Director Console using the InstallShield wizard . . . . . . . . . Performing an unattended installation of IBM Director Console on Windows . . . . . .
Introducing IBM Director . . IBM Director components . . IBM Director Core Services IBM Director Agent . . . IBM Director Console . . IBM Director Server . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
1 2 3 4 4 5
Chapter 2. Planning . . . . . . . . . . 7 Specified operating environments . . . . . . Hardware requirements for IBM Director . . . Network requirements . . . . . . . . . Supported operating systems . . . . . . Support of IBM Director tasks across operating systems . . . . . . . . . . . . . . IBM Director task support for BladeCenter products . . . . . . . . . . . . . IBM Director task support for Storage products Supported database applications . . . . . Licensing requirements for IBM Director components and extensions . . . . . . . . Planning to install IBM Director . . . . . . Choosing where to install IBM Director Server . Planning for events . . . . . . . . . . . Planning events to be monitored . . . . . Planning for event action plan implementations
. 7 . 7 . 10 . 13 . 17 . 26 27 . 28 . . . . .
29 31 31 32 33 34
Chapter 3. Installing . . . . . . . . . 39 Preparing to install IBM Director . . . . Preparing the management server . . . Preparing a Level-1 managed system . . Preparing to manage a BladeCenter . . Preparing Windows XP managed systems
. . . . .
. . . . .
. . . . .
39 39 49 50 53
Chapter 4. Installing IBM Director using the Express installation . . . . . . . 55 Installing IBM Director Server using the Express installation . . . . . . . . . . . . . . Installing IBM Director Server on AIX using the Express installation . . . . . . . . . . . Installing IBM Director Server on Windows using the Express InstallShield wizard . . . . . . Installing IBM Director Server on Linux on POWER using the Express installation option . . Installing IBM Director Server on Linux for System x using the Express installation option . © Copyright IBM Corp. 1999, 2006
55 55 57 59
. 67 . 69 . 70 . 71 . 72 . 73 . 74
Chapter 6. Installing Level 1: IBM Director Core Services . . . . . . . . 77 Installing Level 1: IBM Director Core Services on Linux for System x . . . . . . . . . . . . Installing Level 1: IBM Director Core Services on Linux for System z . . . . . . . . . . . . Installing Level 1: IBM Director Core Services on Linux for POWER . . . . . . . . . . . . Installing Level 1: IBM Director Core Services on Windows . . . . . . . . . . . . . . . Installing Level 1: IBM Director Core Services on Windows using the InstallShield wizard . . . . Performing an unattended installation of Level 1: IBM Director Core Services on Windows . . . Installing IBM Director Core Services using the Software Distribution task . . . . . . . . . Creating a software package . . . . . . . . Installing a software package . . . . . . .
77 78 79 81 81 82 83 85 86
Chapter 7. Installing Level 2: IBM Director Agent . . . . . . . . . . . 89 Installing Level 2: IBM Director Agent on AIX . . Installing Level 2: IBM Director Agent on i5/OS . Installing IBM Director Agent using the Virtualization Engine . . . . . . . . . Installing IBM Director Agent on i5/OS using RSTLICPGM . . . . . . . . . . . . Installing Level 2: IBM Director Agent on Linux for System x . . . . . . . . . . . . . . Installing Level 2: IBM Director Agent on Linux for System z . . . . . . . . . . . . . . Installing Level 2: IBM Director Agent on Linux for POWER . . . . . . . . . . . . . .
. 89 . 91 . 91 . 92 . 92 . 94 . 95
61
iii
Installing Level 2: IBM Director Agent on Linux for Intel Itanium (64 bit) . . . . . . . . . . . 97 Installing Level 2: IBM Director Agent on NetWare 98 Installing Level 2:IBM Director Agent on 32-bit Windows . . . . . . . . . . . . . . . 99 Installing Level 2: IBM Director Agent on 32-bit Windows using the InstallShield wizard . . . . 99 Performing an unattended installation of Level 2: IBM Director Agent on 32-bit Windows . . . 102 Installing Level 2: IBM Director Agent on 64-bit Windows (Intel Itanium only) . . . . . . . . 103 Installing Level 2: IBM Director Agent on 64-bit Windows (Intel Itanium only) using the InstallShield . . . . . . . . . . . . . 104 Performing an unattended installation of Level 2: IBM Director Agent on 64-bit Windows (Intel Itanium only) . . . . . . . . . . . . 106 Installing IBM Director Agent using the Software Distribution task . . . . . . . . . . . . 107 Creating a software package . . . . . . . 108 Installing a software package . . . . . . . 109
Chapter 8. Initially configuring IBM Director . . . . . . . . . . . . . . 111 Configuring IBM Director after an Express installation . . . . . . . . . . . . . . Adding new users in IBM Director . . . . . . Authorizing Request Access on a managed system Enabling Lightweight Directory Access Protocol authentication for IBM Director users . . . . . Using IBM Director in a high-availability environment . . . . . . . . . . . . . . Preparing a high-availability environment for IBM Director and IBM Tivoli System Automation for Multiplatforms . . . . . . Preparing a high-availability environment for IBM Director and SteelEye’s LifeKeeper . . . Configuring IBM Director for a high-availability environment . . . . . . . . . . . . . Configuring discovery preferences . . . . . . Configuring discovery preferences for BladeCenter chassis . . . . . . . . . . Configuring discovery preferences for Level-0 managed systems . . . . . . . . . . . Configuring discovery preferences for Level-1 managed systems . . . . . . . . . . . Configuring discovery preferences for Level-2 managed systems . . . . . . . . . . . Configuring discovery preferences for physical platforms . . . . . . . . . . . . . .
iv
111 112 113 113
Configuring discovery preferences for SMI-S storage devices . . . . . . . . . . . . Configuring discovery preferences for SNMP devices . . . . . . . . . . . . . . Configuring discovery preferences for hardware management consoles . . . . . . . . . Configuring discovery preferences for z/VM systems . . . . . . . . . . . . . . Performing server-initiated discovery of managed objects . . . . . . . . . . . . . . . . Configuring software-distribution preferences . . Setting up file-distribution servers . . . . . Configuring IBM Director to use a file-distribution server . . . . . . . . . Configuring software-distribution preferences for managed systems . . . . . . . . . . Enabling SNMP access and trap forwarding for Linux . . . . . . . . . . . . . . . . Enabling SNMP access and trap forwarding for Linux managed systems . . . . . . . . . Enabling SNMP access and trap forwarding for Red Hat Enterprise Linux versions 3 and 4 . . Enabling SNMP access and trap forwarding for VMware . . . . . . . . . . . . . .
127 130 133 134 136 137 137 138 139 140 141 141 142
Chapter 9. Uninstalling IBM Director on Windows . . . . . . . . . . . . 145 Uninstalling IBM Director using Add/Remove Programs feature Uninstalling IBM Director using command . . . . . . .
the Windows . . . . . . the dirunins . . . . . .
. 145 . 145
114
115 116 116 118 118 120
Appendix A. Accessibility features for IBM Director . . . . . . . . . . . . 147 Appendix B. Lightweight Directory Access Protocol authentication properties for IBM Director Server . . 159 Appendix C. Notices . . . . . . . . 163 Trademarks .
.
.
.
.
.
.
.
.
.
.
.
.
. 164
Glossary . . . . . . . . . . . . . 167
122
Glossary .
123
Index . . . . . . . . . . . . . . . 177
125
IBM Director Express Planning, Installation and Configuration Guide
.
.
.
.
.
.
.
.
.
.
.
.
.
. 167
About this book This book provides information about installing and configuring IBM Director using the Express installation option. 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 © Copyright IBM Corp. 1999, 2006
v
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 – 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/
vi
IBM Director Express Planning, Installation and Configuration Guide
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. Notes:
About this book
vii
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 Implementing IBM Director 5.10 (SG24-6188) v Integrating IBM Director with Enterprise Management Solutions (SG24-5388) v Managing IBM TotalStorage® NAS with IBM Director (SG24-6830) v 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) v IBM Director on System p5 (REDP-4219)
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 User’s 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.
viii
IBM Director Express Planning, Installation and Configuration Guide
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.
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.
© Copyright IBM Corp. 1999, 2006
ix
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 management processor logs IBM Director 5.20 provides support for monitoring and viewing system event logs of Baseboard Management Controllers and Remote Supervisor Adapters on Level-1 managed systems. The log entries are viewed as Common Information Model (CIM) events, and the logs can be cleared automatically when they reach a threshold value. 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 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 SteelEye’s 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
x
IBM Director Express Planning, Installation and Configuration Guide
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. 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.
New in version 5.20
xi
xii
IBM Director Express Planning, Installation and Configuration Guide
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.
© Copyright IBM Corp. 1999, 2006
1
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.
2
IBM Director Express Planning, Installation and Configuration Guide
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: Chapter 1. Getting started with IBM Director
3
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.
4
IBM Director Express Planning, Installation and Configuration Guide
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.
Chapter 1. Getting started with IBM Director
5
6
IBM Director Express Planning, Installation and Configuration Guide
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.
© Copyright IBM Corp. 1999, 2006
7
Table 1. x86-compatible systems: Minimum hardware requirements Requirements
IBM Director Core Services
IBM Director Agent
IBM Director Console ®
IBM Director Server
Microprocessor speed
Pentium-class processor
Pentium-class or Itanium® 2 processor
Pentium 1.5 GHz
Pentium 1.5 GHz
Memory (RAM)
128 MB
128 MB
256 MB
512 MB (minimum) 1024 MB (recommended)
Disk space
Display
40 MB (for Windows)
110 MB (for Windows) 170 MB
100 MB (for Linux)
165 MB (for Linux)
Not applicable
Not applicable
325 MB
At least 256 colors
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 2. Servers running AIX: Minimum hardware requirements Requirements
IBM Director Agent
IBM Director Console
IBM Director Server
Microprocessor speed
Power4 or Power5 1.5 GHz
Power4 or Power5 1.5 GHz
Power4 or Power5 1.5 GHz
Memory (RAM)
512 MB (minimum)
512 MB (minimum)
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.)
325 MB (/opt) 8 MB (/usr)
6 MB (/usr) Display
Not applicable
At least 256 colors
At least 256 colors
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: v The disk space listed is the minimum requirement for an installation using the default selections.
8
IBM Director Express Planning, Installation and Configuration Guide
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 3. Servers running Linux on POWER: Minimum hardware requirements Requirements
IBM Director Core Services
IBM Director Agent
IBM Director Console IBM Director Server
Microprocessor speed
Power4 or Power5 1.5 GHz
Power4 or Power5 1.5 GHz
Power4 or Power5 1.5 GHz
Power4 or Power5 1.5 GHz
Memory (RAM)
128 MB (minimum)
512 MB (minimum)
512 MB (minimum)
512 MB (minimum) 1024 MB (recommended)
Disk space
100 MB
170 MB
225 MB
425 MB
Display
Not applicable
Not applicable
At least 256 colors
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 4. System i products: Minimum hardware requirements Requirements
IBM Director Agent
IBM Director Server
Relative system performance
75 CPW
150 CPW
Storage pool size
350 MB
500 MB
Disk space
300 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 Java and WebSphere® Performance on IBM iSeries Servers (SG24-6256) Redbook 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. The following System z servers are supported: Chapter 2. Planning
9
v IBM System z9™ (all models) v IBM zSeries® (all models) v IBM S/390® (Multiprise® 3, Generation 5 and Generation 6) Table 5. Minimum hardware requirements for IBM Director on System z servers
Requirement
IBM Director Server (with or without CIM instrumentation for z/VM manageability access IBM Director point) Console
Processor speed
All processor speeds provided by IBM System z servers are sufficient for IBM Director.
Memory
1 GB
256 MB
256 MB
512 MB
Disk space
316 MB
168 MB
43-109 MB
215 MB
Display
Not applicable
At least 256 colors
Not applicable
Not applicable
IBM Director Agent
IBM Director Agent with CIM instrumentation for z/VM manageability access point
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 6. Supported versions of network protocols Protocol
Supported version
IPX
IPX versions supported by NetWare and Windows
NetBIOS
Native NetBIOS versions supported by Windows
TCP/IP
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.
10
IBM Director Express Planning, Installation and Configuration Guide
Table 7. Types of data transmission and supported network protocols Type of data transmission
Operating system running on managed system
Supported network protocols
IBM Director Server ←→ IBM Director Console
Not applicable
TCP/IP
IBM Director Server ←→ SNMP devices
Not applicable
TCP/IP
IBM Director Server ←→ IBM Director Agent
AIX
TCP/IP
IBM Director Server ←→ IBM Director Agent
i5/OS
TCP/IP
IBM Director Server ←→ IBM Director Agent
Linux
TCP/IP
IBM Director Server ←→ IBM Director Agent
NetWare
IPX or TCP/IP
IBM Director Server ←→ IBM Director Agent
Windows
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 8 lists the ports used by the various IBM Director processes. v Abbreviations used in Table 8 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 8. Ports used by IBM Director Category IBM Director interprocess communication
Connection IBM Director Server
Destination port ←→
IBM Director Agent
14247 UDP and TCP1
on
page 13; 14248 TCP; 4490 IPX (read); 4491 IPX (write)
IBM Director Console
→
IBM Director Server
2033 TCP
DIRCLI client
←→
IBM Director Server
2044 TCP
DIRCMD client
←→
IBM Director Server
2034 TCP
IBM Director Console
→
IBM Director Console
Any free port (for use of BladeCenter Network Device Manager)
IBM Director Console
→
IBM Director Server over SSL
4066 TCP
DIRCLI client
←→
IBM Director Server
Chapter 2. Planning
11
Table 8. Ports used by IBM Director (continued) Category CIM-XML over HTTP2 on page 13,3
Connection
Destination port
IBM Director Server
→
on page 13
Level-1 or Level-2 managed system, or SMI-S storage device
15988 TCP (SUSE Linux distributions and Red Hat Linux for System z distributions) 5988 TCP (other operating systems)
CIM-XML over HTTPS2 on page 13,3
IBM Director Server
→
on page 13
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 on
CIMOM
→
CIM Listener
6988 TCP (HTTP)
HTTP
IBM Director Server
→
BladeCenter switch module
80 TCP
Microsoft Windows DCOM
IBM Director Server
→
Level-0 system
137 UDP; 138 UDP; 139 TCP; 445 TCP
ServeRAID CIM Provider
→
ServeRAID Manager 34572 TCP
IBM Director Server
←→
service processor
6090 TCP
Service processor
→
IBM Director Server (alerts)
13991 UDP
IBM Director Server
→
service processor (ASF, ASF 2.0, and IPMI)
623 and 664 UDP
Service processor
→
IBM Director Server (ASF, ASF 2.0, and IPMI)
Random port in the 1024-65535 range4 on page 13
SLP
IBM Director Server
←→
SLP service agents or SLP directory agents
427 TCP and UDP
SNMP
IBM Director Server
→
SNMP agent
161 TCP and UDP1 on page
page 13,3 on page 13
ServeRAID interprocess communication Service processors
13
SNMP agent
→
IBM Director Server
162 TCP and UDP1 on page 13
SSH
12
IBM Director Server
→
SNMP devices (Remote Session task)
22 TCP
IBM Director Server
→
Level-0 system
22 TCP
IBM Director Express Planning, Installation and Configuration Guide
Table 8. Ports used by IBM Director (continued) Category Telnet
Connection
Destination port
IBM Director Server
→
BladeCenter management module
23 TCP
IBM Director Server
→
BladeCenter switch module
23 TCP
IBM Director Server
→
SNMP devices (Remote Session task)
23 TCP
Abbreviations used in Table 8 on page 11 v ASF = Alert Standard Format v HTTP = Hypertext Transfer Protocol v HTTPS = Hypertext Transfer Protocol Secure 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/ .
Chapter 2. Planning
13
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. 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 IBM Director Agents & Consoles, V5.20 (2 of 2) v IBM Director for AIX 5L™, V5.20 v IBM Director for i5/OS, V5.20 v IBM Director for Linux on POWER, V5.20 v IBM Director 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 9. Operating systems supported by IBM Director on System x systems and third-party Intel-based systems
Operating system
IBM Director Console
IBM Director Server
IBM Director Agent
IBM Director Core Services
X
X
X
X
X
X
X
X
X
X
X
X
X
X
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)
X
Windows Server 2003 Datacenter Edition (supports Service Pack 1 ) Windows Server 2003, Enterprise, Standard, and Web Editions (supports Service Pack 1 and Release 2)
X
Windows XP Professional Edition (supports Service Pack 2 and earlier)
X
Editions of Windows for 64-bit systems: Windows Server 2003 Datacenter Edition for Itanium systems
14
IBM Director Express Planning, Installation and Configuration Guide
X
Table 9. Operating systems supported by IBM Director on System x systems and third-party Intel-based systems (continued)
Operating system
IBM Director Console
IBM Director Server
Windows Server 2003 Datacenter x64 Edition (supports Release 2 and earlier)
IBM Director Agent
IBM Director Core Services
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Windows Server 2003 Enterprise Edition for Itanium systems Windows Server 2003, Enterprise, Standard, and Web x64 Editions (supports Release 2 and earlier)
X
X
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 7 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.
X
Red Hat Enterprise Linux WS, version 3.0 (supports Update 7 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 3 and X earlier)
X
Red Hat Enterprise Linux WS, version 4.0 (supports Update 3 and earlier) SUSE Linux Enterprise Server 9 for x86 (supports Service Pack 3 and earlier)
X
X
X
X
SUSE Linux Enterprise Server 10 for x86
X
X
X
X
X
X
X
X
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.
X
X
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.
X
X
Red Hat Enterprise Linux AS and ES, version 3.0, for AMD64 and EM64T (supports Update 7 and earlier)
X
X
Red Hat Enterprise Linux WS, version 3.0, for AMD64 and EM64T (supports Update 7 and earlier)
X
X
X
X
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, Console VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, guest X 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.
X
Versions of Linux for 64-bit systems: Red Hat Enterprise Linux AS, version 3.0, for Intel Itanium
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 3 and earlier)
X
Chapter 2. Planning
15
Table 9. Operating systems supported by IBM Director on System x systems and third-party Intel-based systems (continued)
Operating system
IBM Director Console
IBM Director Agent
IBM Director Core Services
X
X
X
X
X
IBM Director Server
Red Hat Enterprise Linux WS, version 4.0, for AMD64 and EM64T (supports Update 3 and earlier) 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
X
X
X
X
SUSE Linux Enterprise Server 10 with Xen Kernel
X
X
X
X
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.
X
X
NetWare, version 6.5 Note: Level-0 support is not provided.
X
Other operating systems supported by System x servers:
Table 10. Operating systems supported by IBM Director on System i and System p products
Operating system
IBM Director Console
IBM Director Server
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.
IBM Director Agent
IBM Director Core Services
X
X
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.
X
X
X
X
Red Hat Enterprise Linux AS, version 4.3 and 4.4, for IBM POWER
X
X
X
X
SUSE Linux Enterprise Server 9 for IBM POWER (Service Pack 3 required)
X
X
X
X
SUSE Linux Enterprise Server 10 for IBM POWER
X
X
X
X
IBM Director Console
IBM Director Server
IBM Director Agent
IBM Director Core Services
X
X
X
X
Table 11. Operating systems supported by IBM Director on System z systems
Operating system Red Hat Enterprise Linux AS, version 4.0, for IBM System z (supports Update 4 and earlier)
16
IBM Director Express Planning, Installation and Configuration Guide
Table 11. Operating systems supported by IBM Director on System z systems (continued) IBM Director Console
IBM Director Server
IBM Director Agent
IBM Director Core Services
SUSE Linux Enterprise Server 9 for IBM System z (supports Service Pack 3 and earlier)
X
X
X
X
SUSE Linux Enterprise Server 10 for IBM System z
X
X
X
X
Operating system
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
Task Asset ID
™
Linux and Windows only
X
CIM Manager
X
Configuration Manager
X
Configure SNMP Agent
X
Event Log
X
External Application Launch
X
File Transfer
X
Hardware Control Point
X
Hardware Management Console
X
Chapter 2. Planning
17
Task is supported on the following operating systems:
Task
All operating systems supported by IBM Director Server
Hardware Status
X
Inventory (hardware)
X
Inventory (software)
X
Microsoft Cluster Browser
X
Network Configuration
X
Power Management
X
Process Management
X
Rack Manager
X
Remote Control
X
Remote Session
X
Resource Monitors
X
Server Storage Provisioning Tool
Linux and Windows only
X
SNMP Browser
X
Software Distribution
X
Storage Configuration Manager
X
System Accounts
X
Update Manager
X
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. Review the following considerations when using this table: 1. Not supported on Itanium systems. 2. Not supported on System z systems. 3. Not supported on guest operating systems. 4. Supported on System x and Intel-based systems only. 5. Not supported on Windows XP Professional x64 Edition. 6. Support on Itanium systems is limited to Level 2. 7. Platform-specific data is not available for hardware inventory. 8. 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 9. Not supported for Linux on POWER. 10. Not supported on 64-bit versions of these operating systems. 11. Supported on Windows guest operating systems only. 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.
18
IBM Director Express Planning, Installation and Configuration Guide
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. Operating systems
Task
Windows Level 2
1
CIM Manager Level 2
1
Asset ID
ESX Server GSX Server
i5/OS
AIX
NetWare
Microsoft Virtual Server
1, 2
Level 2
Level 2
No
No
Level 2
1
Level 2
Level 2
Level 2
No
Level 2
Linux Level 2
Level 2
Configuration See “Operating systems supported by the Configuration Manager task” Manager Configure SNMP Agent
Level 21
Level 21, 5
Level 2
Level 2
Level 2
No
Level 2
Event Log
Levels 1, 2
Levels 1, 2
Levels 1, 2
Levels 1, 2
Levels 1, 2
Levels 1, 2
Levels 1, 2
External Application Launch
See “Operating systems supported by External Application Launch”
File Transfer
Level 2
Level 2
Level 2
Hardware Status
See “Operating systems supported by the Hardware Status task”
Level 2
Level 2
14
Level 2
Level 2
Levels 0, 1, 26, 7
Levels 0, 1, 26, 7
Levels 0, 1, 2 Level 2
Level 27
Level 27
Levels 0, 1, 2
Inventory (software)
Levels 0, 1, 26
Levels 0, 1, 26
Levels 0, 1, 2 Level 2
No
Level 2
Levels 0, 1, 2
Microsoft Cluster Browser
Level 28
No
No
No
No
No
No
Level 21, 9
Level 2
Level 2
No
No
Level 2
Inventory (hardware)
15
Network Level 21 Configuration Power Management
See “Operating systems supported by the Power Management task”
Process Management
Level 2
Rack Manager Level 210
Level 2
Level 2
Level 2
Level 2
Level 2
Level 2
Level 24, 10
Level 2
No
No
Level 2
Level 2
No
No
No
Level 2
13 11
Remote Control
Level 2
No
Level 2
Remote Session
Level 2
Level 2
Level 2
Level 2
Level 2
Level 2
Level 2
Resource Monitors
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
Level 2
Level 2
Level 2
Level 2
Level 2
Level 2
Level 2
Chapter 2. Planning
19
Operating systems
Task
Windows
Software Distribution
ESX Server GSX Server
Linux
i5/OS
Levels 0, 1, 2 Levels 0, 1, 2 Levels 0, 1, 2 Levels 0, 2
AIX
NetWare
Microsoft Virtual Server
Levels 0, 1, 2 No
Levels 0, 1, 2
12
Storage Levels 1, 2 Configuration Manager
Levels 1, 2
2,
Levels 1, 2
No
No
No
Levels 1, 2
Level 2
Level 2
No
No
Level 2
No
No
Levels 0, 1, 2
9
System Accounts
Level 21
Level 21, 9
Update Manager
Levels 0, 1, 2 Levels 0, 1, 2 Levels 0, 1, 2 No 2, 9
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 Table 12. Hardware Status support for System x servers; IBM and third-party x86-based systems Operating system Editions of Windows for 32-bit systems:
20
IBM Director Express Planning, Installation and Configuration Guide
Level 1
Level 2
Table 12. Hardware Status support for System x servers; IBM and third-party x86-based systems (continued) Operating system
Level 1
Level 2
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
Yes
Yes
v Windows Server 2003, Datacenter, Enterprise, Standard, and Web x64 Editions v Windows XP Professional x64 Edition
Yes
Yes
Windows Server 2003, Datacenter and Enterprise 64-bit Itanium Editions
No
No
Yes
Yes1
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, Console
Yes1
Yes1
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, guest operating systems
Limited
Limited
v VMware GSX Server, versions 3.1 and 3.2, Console v VMware GSX Server, versions 3.1 and 3.2, guest operating systems
(For Console) Yes1 (For guest) Limited
(For Console) Yes1 (For guest) Limited
Yes
Yes
No
No
Editions of Windows for 64-bit systems:
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
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
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
1
Other operating systems supported by System x servers: Microsoft Virtual Server (guest operating system) NetWare, version 6.5
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 13. Hardware Status support for System i platforms and System p servers Operating system
Level 1
Level 2
v AIX 5L, Version 5.2 v AIX 5L, Version 5.3
No
No
v i5/OS, Version 5 Release 3
No
Yes1
Yes1
Yes1
v i5/OS, Version 5 Release 4 v Red Hat Enterprise Linux AS, version 4.3 and 4.4, for IBM POWER v SUSE Linux Enterprise Server 9 for IBM POWER v SUSE Linux Enterprise Server 10 for IBM POWER
1. (BladeCenter JS20 and JS21 only) Out-of-band notifications generated by a service processor only.
Chapter 2. Planning
21
Table 14. Hardware Status support for System z servers Operating system
Level 1
Level 2
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z v SUSE Linux Enterprise Server 9 for IBM System z v SUSE Linux Enterprise Server 10 for IBM System z
No
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 15. Operating systems supported by System x servers and third-party Intel-based systems Operating system
Supported
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
Yes, Restart and Shutdown
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:
22
IBM Director Express Planning, Installation and Configuration Guide
Yes, Restart and Shutdown
Table 15. Operating systems supported by System x servers and third-party Intel-based systems (continued) Operating system v v v v v v
Supported
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, and 3.0, Console VMware GSX Server, versions 3.1 and 3.2, Console
v VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, guest operating systems v VMware GSX Server, versions 3.1 and 3.2, guest operating systems
Yes, Restart
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
NetWare, version 6.5
No
Note: (For System p servers only) Power Management-support provided only for Level-2 managed systems. Table 16. Operating systems supported by System i platforms and System p servers Operating system
Supported
v i5/OS, Version 5 Release 3
No
1
v i5/OS, Version 5 Release 4 v v v v v
AIX 5L, Version 5.2 AIX 5L, Version 5.3 Red Hat Enterprise Linux AS, version 4.3 and 4.4, for IBM POWER SUSE Linux Enterprise Server 9 for IBM POWER SUSE Linux Enterprise Server 10 for IBM POWER
Yes, Restart
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 17. Operating systems supported by System z servers Operating system
Supported
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z v SUSE Linux Enterprise Server 9 for IBM System z v SUSE Linux Enterprise Server 10 for IBM System z
Yes, Restart
Chapter 2. Planning
23
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, version 5.10. 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. These servers can be Level-0, Level-1, or 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-0, Level-1, or 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 18. Operating systems supported by System x servers and third-party Intel-based systems Operating system
Supported
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
Yes
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
Yes
Versions of Linux for 32-bit systems: v v v v
24
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
IBM Director Express Planning, Installation and Configuration Guide
Yes
Table 18. Operating systems supported by System x servers and third-party Intel-based systems (continued) Operating system v v v v
VMware VMware VMware VMware
Supported
ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, Console ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, guest operating systems GSX Server, versions 3.1 and 3.2, Console GSX Server, versions 3.1 and 3.2, guest operating systems
No
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)
No
NetWare, version 6.5
Yes
Operating systems supported by IBM Server Storage Provisioning Tool The IBM Server Storage Provisioning Tool 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. Note: IBM Server Storage Provisioning Tool provides Level-0, Level-1, and Level-2 support only on 32-bit operating systems for configurations that contain a BladeCenter Qlogic 2 Port Fibre Channel Switch Module (48P7062). Table 19. IBM Server Storage Provisioning Tool support for System x servers; IBM and third-party x86-based systems Operating system
Level 0
Level 1
Level 2
Yes
Yes
Yes
v Windows Server 2003, Datacenter, Enterprise, Standard, and Web x64 Editions v Windows XP Professional x64 Edition
No
No
Yes
Windows Server 2003, Datacenter and Enterprise 64-bit Itanium Editions
No
No
No
Yes
Yes
Yes
No
No
No
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, guest operating No systems
No
Yes
v VMware GSX Server, versions 3.1 and 3.2, Console v VMware GSX Server, versions 3.1 and 3.2, guest operating systems
No
No
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:
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
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, Console
No
Chapter 2. Planning
25
Table 19. IBM Server Storage Provisioning Tool support for System x servers; IBM and third-party x86-based systems (continued) Operating system
Level 0
Level 1
Level 2
No
Yes
No
No
No
Microsoft Virtual Server (guest operating system)
No
No
No
NetWare, version 6.5
No
No
No
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 No ES, and WS, version 4.0, for AMD64 and EM64T 9 for AMD64 and EM64T 10 for AMD64 and EM64T 10 with Xen Kernel
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:
Table 20. IBM Server Storage Provisioning Tool support for System i platforms and System p servers Operating system
Level 0
Level 1
Level 2
v AIX 5L, Version 5.2 v AIX 5L, Version 5.3
No
No
No
v i5/OS, Version 5 Release 3
No
No
No
No
No
No
Operating system
Level 0
Level 1
Level 2
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z v SUSE Linux Enterprise Server 9 for IBM System z v SUSE Linux Enterprise Server 10 for IBM System z
No
No
No
v i5/OS, Version 5 Release 4 v Red Hat Enterprise Linux AS, version 4.3 and 4.4, for IBM POWER v SUSE Linux Enterprise Server 9 for IBM POWER v SUSE Linux Enterprise Server 10 for IBM POWER Table 21. IBM Server Storage Provisioning Tool support for System z servers
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.
26
IBM Director Express Planning, Installation and Configuration Guide
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 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 22. IBM Director task support for BladeCenter products Tasks and subtasks
Chassis
Network device
Blade server without IBM Director Agent or IBM Director Core Services installed
BladeCenter Configuration Manager
Yes
No
Not applicable
Event Action Plans
Yes
Yes
Yes
Hardware Status
Yes
No
Inventory
Yes
Yes
Yes
Not applicable
Yes
Not applicable
Power Management
No
No
Yes
Rack Manager
Yes
Yes
No
Remote Session
Not applicable
Yes
No
Remote Monitors
No
Yes
No
SNMP Browser
No
Yes
Yes
Network Device Manager (formerly Switch Management launch pad)
Yes
1
2
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.
Chapter 2. Planning
27
Table 23. IBM Director task support for Storage products Tasks and features
DS300 DS400 DS4000 Brocade switches
DS6000 QLogic BladeCenter switches
Event Action Plans1
Yes
No
Event Log
Yes
Yes
External Application Launch
Yes
Yes
Hardware Status
Yes
Yes
Inventory
Yes
Yes
1. Indicates that the Storage product generates events. Events are detected for use in event action plans.
Supported database applications IBM Director Server uses an SQL database to store inventory data for the systems in the environment. Depending on the database application selected and the operating system of the management server, the database might be embedded, local, or remote. 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 24. Database applications supported by IBM Director 5.20 Database
AIX
i5/OS
Linux
Windows
Apache Derby
v V10.1 (included with IBM Director Server on AIX, Linux, and Windows)
Embedded
—
Embedded
Embedded
IBM DB2 Universal Database™
v version 8.2 with Fix Pack 5 v version 8.1 with Fix Pack 12
Local or remote
—
Local or remote
Local or remote
IBM DB2 Universal Database for System i (part of i5/OS)
—
Local
—
—
v Microsoft SQL Server — 2005 with Service Pack 1 v Microsoft SQL Server 2000 with Service Pack 4
—
Remote
Local or remote
v Microsoft SQL Server — 2005 Express Edition with Service Pack 1 v Microsoft SQL Server 2000 Desktop Engine (also called MSDE 2000) with Service Pack 4
—
—
Local
Microsoft SQL Server
28
Supported database versions
IBM Director Express Planning, Installation and Configuration Guide
Table 24. Database applications supported by IBM Director 5.20 (continued) Database Oracle (Oracle Server)
Supported database versions v version 10g release 2 v version 10g release 1 v version 9.2
PostgreSQL v version 8.1 v version 7.4 v version 7.3
AIX
i5/OS
Linux
Windows
Local or remote
—
Local or remote
Local or remote
—
—
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. Note: 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.
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
Chapter 2. Planning
29
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.”
IBM Director Console 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 IBM System p servers v IBM System x servers v v v v
IBM IBM IBM IBM
System z mainframes System Storage Network Attached Storage (NAS) products SurePOS point-of-sale systems ThinkCentre, NetVista, and PC desktop computers
v IBM 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
30
IBM Director Express Planning, Installation and Configuration Guide
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) 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 v v v
Capacity Manager Remote Deployment Manager extension Software Distribution Premium Edition 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.
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.
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
Chapter 2. Planning
31
installed either on a blade in the BladeCenter, or on a separate management server. Refer to “Preparing to manage a BladeCenter” on page 50 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. – 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.
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 v Microsoft Windows event log v Windows Management Instrumentation (WMI)
32
IBM Director Express Planning, Installation and Configuration Guide
v SNMP through out-of-band communication v Intelligent Platform Management Interface (IPMI) Platform Event Traps (PET) through out-of-band communication v IBM service processors through out-of-band communication 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 The events that you can monitor are divided into three groups. You can enable the monitoring of these events using any one of the available user interfaces, including IBM Director and a Web browser. Tip: These events are not enabled by default. v Critical alerts – Temperature outside critical thresholds – Voltage outside critical thresholds – Tamper alert (server cover opened) - on some servers only – Multiple fans failure – Power supply failure – Hard disk drive failure – VRM failure v Warning alerts (non-critical) – Redundant power supply failure – Single fan failure – Temperature outside warning thresholds – Voltage outside warning thresholds v System alerts – Operating system timeout value is exceeded – Power off – Power on – – – –
Boot failure Server loader timeout value is exceeded PFA notification Partition configuration Chapter 2. Planning
33
If you enable the O/S timeout and server loader timeout alerts, then you also must plan to enable those timeouts. 1. Consider how events will be sent by the managed systems to IBM Director Server. There are generally two options: v via telephonic modem v over a LAN, using an IP address 2. On the service processors that have Ethernet connections and modems, you should configure those connections so alerts can be sent through them. For Ethernet connections, configure either a static IP address or enable the use of DHCP. Tips: v The Remote Supervisor Adapter and Remote Supervisor Adapter II support DHCP; however, the use of a static IP address is potentially more reliable than using DHCP. A static address will mean that the failure or inaccessibility of DNS and/or DHCP servers will not prevent access to the service processor. v If the Remote Supervisor Adapter II is set to use DHCP but does not receive an address from the DHCP server within two minutes, it will set its address as 192.168.70.125. v For modem use, configure the standard modem settings (baud rate, parity, and stop bits) plus any additional strings if necessary. v For SNMP, enable traps and the SNMP agent, and configure the community name and IP address. v For SMTP, configure the SMTP server.
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. 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
34
IBM Director Express Planning, Installation and Configuration Guide
– 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. Note: 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 Chapter 2. Planning
35
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. 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
36
IBM Director Express Planning, Installation and Configuration Guide
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.
Chapter 2. Planning
37
38
IBM Director Express Planning, Installation and Configuration Guide
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.
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 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 theIBM Director for i5/OS, V5.20 media. 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, V5.20 (1 of 2) CD. 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
Order number
(V5R3 only) IBM Cryptographic Access Provider 128-bit for iSeries
5722-AC3
IBM HTTP Server for iSeries
5722-DG1
Extended Base Directory Support, Option 3
5722-SS1
™
Java Developer Kit 1.4, Option 6 © Copyright IBM Corp. 1999, 2006
5722-JV1
39
Products or options ®
Order number
OS/400 - Qshell, Option 30
5722-SS1
OS/400 - Digital Certificate Manager, Option 34
5722-SS1
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 Make sure that you have applied the most recent fix packages, otherwise the server might not start after the installation is completed. 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 on POWER Before installing IBM Director Server on a Linux on POWER platform, 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 You can obtain the IBM Director software for Linux for System p from the following sources: – The IBM Director Web site at www.ibm.com/systems/management/director/ downloads.html. – If it was included with your IBM Director distribution, the IBM Director for Linux on POWER, V5.20 CD. v Red Hat Enterprise Linux AS, version 4, for IBM POWER only: Before installing IBM Director, ensure that the following RPM file (or later version) is installed: – compat-libstdc++-33-3.2.3-47.3.ppc.rpm v Red Hat Enterprise Linux AS, version 4, for IBM POWER and SUSE Linux Enterprise Server 9 and 10: Ensure that the following RPM files (or later versions) are installed: – librtas-1.2-1.ppc64.rpm – lsvpd-0.12.7-1.ppc.rpm
40
IBM Director Express Planning, Installation and Configuration Guide
– 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 When you install the powerpc-utils RPM files on a system where a version of the ppc64-utils RPM is already installed, a file conflict error message might occur. In this case, use the --force option to install the powerpc-utils RPM file: – rpm -Uvh --force powerpc-utils-1.0.0-1.ppc64.rpm – rpm -Uvh --force powerpc-utils-papr-1.0.3-1.ppc64.rpm To check for the fileset, type the following command and press Enter: rpm -qa | grep ppc64-utils
You can download these RPM files from the IBM Service and productivity tools for Linux on POWER Web site at www14.software.ibm.com/webapp/set2/sas/ f/lopdiags/home.html. Select the appropriate tab for your Linux distribution.
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 required RPMs are installed: Table 25. Required RPMs Red Hat Enterprise Linux AS and ES, version 3.0
compat-libstdc++-7.3-2.96.122.i386.rpm
Red Hat Enterprise Linux AS and ES, version 4.0
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 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 IPMI baseboard management controllers: Install the supporting IPMI device drivers and mapping layers, if they are not already installed. IBM Director cannot receive System Health Monitoring information if these drivers and mapping layers are not installed. The device drivers and mapping layers for Windows, Linux, and NetWare can be downloaded from the IBM Director support Web site at www.ibm.com/pc/support. For eServer™ 325 or eServer 326 models, download and install the following items (the exact names of the files to download are dependent upon your operating system): – MSI IPMI device drivers for Windows Chapter 3. Installing
41
– IBM IPMI Library (mapping layer) For all other System x systems, download and install the following items (the exact names of the files to download are dependent upon your operating system): – OSA IPMI device drivers – IBM Mapping layer software source for OSA IPMI
v
v
v
v
Important: You must install the device driver first and then install the mapping layer. 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. 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. 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, V5.20 (1 of 2) CD. The IBM Director on x86, V5.20 CD does not include SUSE Linux Enterprise Server (SLES) 10 installation packages for IBM Director Server, IBM Director Console, IBM Director Agent, or IBM Director Core Services. You can download these SLES 10 installation packages for System x platforms from theIBM Director Web site at: www.ibm.com/systems/management/director/ .
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. 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 managed system to enable management of the service processor, complete the following steps: 1. Refer to the documentation for your managed servers to identify what type of service processor is installed. For a list of service processors that are typically used with IBM servers, see the“Service processors in System x, xSeries, eServer, and BladeCenter blade servers” topic in the IBM Director Systems Management Guide. 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
42
IBM Director Express Planning, Installation and Configuration Guide
processor for that system, and all management occurs through the Remote Supervisor Adapter or Remote Supervisor Adapter II. 2. After identifying the service processor types that you will be managing, use the following table to determine the drivers that must be installed for in-band (Level-1 or Level-2) management of the service processors. Notes: a. For servers that will be managed as Level-0 (″agentless″) servers, you do not need to install drivers to perform Level-0 management of the service processors. b. The MSI IPMI driver and the OSA IPMI driver must be installed before the IBM Mapping Layer. Table 26. Required drivers for in-band management of service processors Integrated system management processor
IPMI baseboard management controller
Remote Supervisor Adapter II
OpenIPMI driver
OpenIPMI driver
RSA daemon, USB drivers
Other Red Hat MSI IPMI driver, Linux distributions IBM Mapping Layer
OSA IPMI driver, IBM Mapping Layer
RSA daemon, USB drivers
v SUSE Linux Enterprise Server 9 for x86
OpenIPMI driver
OpenIPMI driver
RSA daemon, USB drivers
Other SUSE Linux distributions
MSI IPMI driver, IBM Mapping Layer
OSA IPMI driver, IBM Mapping Layer
RSA daemon, USB drivers
virtual systems using Xen
OpenIPMI driver
OpenIPMI driver
RSA daemon, USB drivers
VMware
OpenIPMI driver
OpenIPMI driver
USB drivers
MSI IPMI driver, IBM Mapping Layer
OSA IPMI driver, IBM Mapping Layer
Not Supported
MSI IPMI driver, IBM Mapping Layer
OSA IPMI driver, IBM Mapping Layer
RSA library, USB drivers
Operating system of managed server Red Hat Linux
v Red Hat Enterprise Linux, version 3.0 (update 6) v Red Hat Enterprise Linux, version 4.0 (update 3)
SUSE Linux
v VMware ESX Server, version 2.5.4, Console v VMware ESX Server, version 3.0, Console Other VMware distributions
Windows
3. Make sure that you have the latest firmware installed for your service processors. IBM LM78 and SMBus device drivers for Linux:
Chapter 3. Installing
43
This topic describes when to install the LM78 and SMBus device drivers for Linux. If you plan to install IBM Director Server on an 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. Table 27. Installing IBM Director Server: IBM LM78 and SMBus device drivers for Linux Device driver
When it is needed
What it does
LM78
If either of the following conditions applies: The LM78 device driver ensures that IBM Director v The server is one of the following Server receives memory and servers: processor Predictive Failure – BladeCenter HS20, machine type 8832 Analysis® (PFA) alerts. – BladeCenter HS20, machine type 8843 – BladeCenter HS40, machine type 8839 – xSeries 225, machine type 8647 – xSeries 226, machine type 8836 – xSeries 236, machine type 8841 – xSeries 336, machine type 8837 – xSeries 346, machine type 8840 v The server contains an integrated systems management processor (ISMP).
SMBus
If the server does not contain one of the following service processors: v IPMI baseboard management controller 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.
Preparing to install the LM78 and SMBus device drivers: This topic describes how to install the IBM LM78 and SMBus device drivers. You must perform the following steps to install either the IBM LM78 or SMBus device driver: 1. Build a binary RPM file that is customized for the kernel version of the Linux operating system on your server. For instructions, see “Building the binary RPM file.” 2. Install the binary RPM file on the system on which you will install IBM Director Server. For instructions, see “Installing the IBM LM78 or SMBus device driver” on page 45. 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.
44
IBM Director Express Planning, Installation and Configuration Guide
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// ./linux
where 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. Copy the source file (ibmlm78-5.20-1.tgz for the LM78 driver or ibmsmb-5.20-1.tgz for the SMBus driver) to the SOURCES directory. 2. From a command prompt, change to the SOURCES directory. 3. Type one of the following commands and press Enter: Device driver
Command
LM78
rpmbuild -tb ibmlm78-5.20-1.tgz
SMBus
rpmbuild -tb ibmsmb-5.20-1.tgz
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).
Chapter 3. Installing
45
Note: In this procedure, driver is one of the following strings: Device driver
Command
IBM LM78
ibmlm78
IBM SMBus
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 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” and “Uninstalling the IBM SMBus device driver, version 4.20 or earlier” on page 47. 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
where driver is one of the following strings. Device driver
Command
IBM LM78
ibmlm78
IBM SMBus
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.
46
IBM Director Express Planning, Installation and Configuration Guide
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 46. 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
String
For servers running Red Hat Linux or VMware ESX Server
redhat
For servers running SUSE Linux
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 46. 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: rpm -e ibmsmb-src-distribution
where distribution is one of the following strings. Type of distribution
String
For servers running Red Hat Linux or VMware ESX Server
redhat
For servers running SUSE Linux
suse
Issuing this command unloads the device driver and removes all driver-related files from the server.
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. Chapter 3. Installing
47
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 28 lists some methods of making the installation code available. Table 28. Making the IBM Director installation code available to Linux on System z Method
How to proceed
NFS server
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: 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.
48
IBM Director Express Planning, Installation and Configuration Guide
v Ensure that the following RPMs are installed. Table 29. Required RPMs Red Hat 31-bit Enterprise Linux AS, version 4.0
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
64-bit
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
SUSE Linux Enterprise Server 9
31-bit
compat-2004.7.1-1.2.s390.rpm
64-bit
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
SUSE Linux Enterprise Server 10 for IBM System z
64-bit
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
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 User’s 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 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 Chapter 3. Installing
49
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. Related tasks “Preparing to manage service processors with IBM Director” on page 42 You can use IBM Director to manage supported service processors that are installed in a managed system.
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 3 on page 51 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.
50
IBM Director Express Planning, Installation and Configuration Guide
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/ .
Figure 3. 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: Chapter 3. Installing
51
– 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 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 3 on page 51 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 4 on page 53 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/ .
52
IBM Director Express Planning, Installation and Configuration Guide
Figure 4. 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 . 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. 2. Configure Windows Firewall (Internet Connection Firewall) to allow access by IBM Director Server. Windows XP (before Service Pack 2) includes a built-in Chapter 3. Installing
53
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.
54
IBM Director Express Planning, Installation and Configuration Guide
Chapter 4. Installing IBM Director using the Express installation After preparing your systems and environment for IBM Director, you can use the applicable Express installation procedure to install IBM Director Server. The Express installation option automatically installs the tasks and options that are typically used by Small and Medium Businesses.
Installing IBM Director Server using the Express installation After preparing your system, use the IBM Director Server Express installation procedure for the applicable operating system on which you plan to install IBM Director Server.
Installing IBM Director Server on AIX using the Express installation After preparing your server, you can use the Express installation option to install IBM Director Server on AIX. To perform an Express installation, you must run the dirinstall script against a response file in which the ExpressInstall parameter is enabled by setting it to 1. Important: v IBM Director Server and IBM Director Console must be at the same release level. If you install IBM Director Server, version 5.20 on the management server, you must also install IBM Director Console, version 5.20 on any systems that you want to access the management server. In addition, 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. Management servers running i5/OS, IBM Director Server use the DB2 database. On all other operating systems, the default database is Apache Derby, but other databases can be used. v 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. On management servers running i5/OS, however, IBM Director Server does not include IBM Director Console. 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 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. © Copyright IBM Corp. 1999, 2006
55
To use the Express installation option to install IBM Director Server on AIX, complete the following steps: 1. To install IBM Director Server from a Web download, perform the following steps: a. Download the IBM Director for AIX - Version 5.20 (Dir5.20_AIX.tar.gz) file from the IBM Director downloads page at:www.ibm.com/systems/ management/director/downloads.html. b. To unzip and extract the contents of the Dir5.20_AIX.tar.gz file, type the following command: gzip -cd Dir5.20_AIX.tar.gz | tar -xvf -
Go to step 3. 2. To install IBM Director Server from the CD, perform the following steps: a. Insert the IBM Director for AIX 5L, V5.20 CD into the drive. b. If the CD automounts, go to step 2c. 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. 3. Type the following command and press Enter to copy the response file (dirserv.rsp) to a local directory : cp dirserv.rsp /directory
where directory is the local directory. 4. Use an ASCII text editor to open the copy of the response file, and change the value of the ExpressInstall parameter to 1. In the response file, ″1″ indicates that an item is to be installed and ″0″ indicates that an item is not to be installed. 5. Save the modified response file. 6. Type the following command and press Enter: ./dirinstall -r /directory/response.rsp
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 5. 7. The License Agreement message is displayed. If you agree with the terms, proceed with the installation. Otherwise, cancel the installation. The installation progress displays. 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: install_root/bin/cfgsecurity
where install_root represents the root directory of your IBM Director installation. 9. To start IBM Director Server, type the following command and press Enter: install_root/bin/twgstart
56
IBM Director Express Planning, Installation and Configuration Guide
10. 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. 11. If you used the CD to install IBM Director Server, remove the CD from the drive. Note: (AIX and Linux only) If you log into IBM Director Console using the root account, all the IBM Director tasks for a Standard installation are displayed.
Installing IBM Director Server on Windows using the Express InstallShield wizard After preparing your System x server for the installation of IBM Director, run the IBM Director Server installation program and choose the Express installation feature. Important: v IBM Director Server and IBM Director Console must be at the same release level. If you install IBM Director Server, version 5.20 on the management server, you must also install IBM Director Console, version 5.20 on any systems that you want to access the management server. In addition, 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. Management servers running i5/OS, IBM Director Server use the DB2 database. On all other operating systems, the default database is Apache Derby, but other databases can be used. v 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. On management servers running i5/OS, however, IBM Director Server does not include IBM Director Console. 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 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. To install IBM Director Server using the Express installation, complete the following steps: 1. Using an account with either local or domain administrative privileges, log on to the operating system. 2. Insert the IBM Director on x86, V5.20 into the drive. Chapter 4. Installing IBM Director using the Express installation
57
3. If the installation program starts automatically and the IBM Director Setup window opens, go to step 5. Otherwise, click Start → Run. 4. 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. 5. 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:
6. 7. 8. 9.
a. Close the IBM Director Setup window. b. Open Windows Explorer. c. Browse to the director/server/windows/i386 directory on the IBM Director on x86, V5.20 CD. d. Run the ibmsetup.exe program. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Server window opens. Click Next. The License Agreement window opens. Click I accept the terms in the license agreement; then, click Next. The Installation Type window opens. Click Perform an Express Installation of IBM Director Server; then, click Next. The Destination Folder window opens. To select an alternative location for the IBM Director Server installation directory, click Change and select another directory.
10. Click Next. The IBM Director Service Account Information window opens. 11. 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.
12. 13.
14. 15.
58
Note: The information that you provide must correspond to a Windows account with administrator privileges on the management server. Otherwise, the installation will fail. Click Next. The Encryption Settings window opens. 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. Click Next. The Software Distribution Settings window opens. To select an alternative location for the creation of the software-distribution packages, click Change and select another directory.
IBM Director Express Planning, Installation and Configuration Guide
16. 17.
18. 19. 20.
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. Click Next. The Ready to Install the Program window opens. 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, a status window opens. Click Finish. A window opens, asking you if you want to restart the server. Remove the CD from the drive. Click Yes to restart the server.
Installing IBM Director Server on Linux on POWER using the Express installation option After preparing your server, you can use the Express installation option to install IBM Director Server on Linux on POWER. To perform an Express installation, you must run the dirinstall script against a response file in which the ExpressInstall parameter is enabled. Important: v IBM Director Server and IBM Director Console must be at the same release level. If you install IBM Director Server, version 5.20 on the management server, you must also install IBM Director Console, version 5.20 on any systems that you want to access the management server. In addition, 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. Management servers running i5/OS, IBM Director Server use the DB2 database. On all other operating systems, the default database is Apache Derby, but other databases can be used. v 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. On management servers running i5/OS, however, IBM Director Server does not include IBM Director Console. 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 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. To install IBM Director Server on Linux on POWER, complete the following steps: Chapter 4. Installing IBM Director using the Express installation
59
1. To install IBM Director Server from a Web download, perform the following steps: a. Download the IBM Director for Linux on POWER - Version 5.20 (Dir5.20_LinuxonPower.tar.gz) file from the IBM Director downloads page at: www.ibm.com/systems/management/director/downloads.html. b. Extract the contents of the Dir5.20_AIX.tar.gz file into a local directory. c. To change to the directory in which IBM Director Server is located, type the following command and press Enter: cd /directory/director/server/linux/ppc/
where directory is the local directory into which you extracted the files. Go to step 5. 2. To install IBM Director Server from a CD, insert the IBM Director for Linux on POWER, V5.20 CD into the drive. 3. If the CD automounts, go to step 4. If the CD does not automount, 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. 4. Change to the directory in which the installation script is located. Type the following command and press Enter: cd /mnt/cdrom/director/server/linux/ppc/
where mnt/cdrom is the mount point of the drive. 5. Type the following command and press Enter to copy the response file (dirserv.rsp) to a local directory : cp dirserv.rsp /directory
where directory is the local directory. 6. Use an ASCII text editor to open the copy of the response file, and change the value of the ExpressInstall parameter to 1. In the response file, ″1″ indicates that an item is to be installed and ″0″ indicates that an item is not to be installed. 7. Save the modified response file. 8. Type the following command and press Enter: ./dirinstall -r /directory/response.rsp
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 7. 9. The License Agreement message is displayed. If you agree with the terms, proceed with the installation. Otherwise, cancel the installation. The installation progress displays. 10. 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
where install_root represents the root directory of your IBM Director installation. 11. To start IBM Director, type the following command and press Enter: install_root/bin/twgstart
60
IBM Director Express Planning, Installation and Configuration Guide
12. If you used a 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. 13. If you used a CD, remove the CD from the drive. Note: (AIX and Linux only) If you log into IBM Director Console using the root account, all the IBM Director tasks for a Standard installation are displayed.
Installing IBM Director Server on Linux for System x using the Express installation option After preparing your server, you can use the Express installation option to install IBM Director Server on Linux for System x. To perform an Express installation, you must run the dirinstall script against a response file in which the ExpressInstall parameter is enabled. Important: v IBM Director Server and IBM Director Console must be at the same release level. If you install IBM Director Server, version 5.20 on the management server, you must also install IBM Director Console, version 5.20 on any systems that you want to access the management server. In addition, 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. Management servers running i5/OS, IBM Director Server use the DB2 database. On all other operating systems, the default database is Apache Derby, but other databases can be used. v 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. On management servers running i5/OS, however, IBM Director Server does not include IBM Director Console. 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 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. To use the Express installation option to install IBM Director Server on Linux for System x, complete the following steps: 1. To install IBM Director Server from a Web download, perform the following steps: Chapter 4. Installing IBM Director using the Express installation
61
a. Download the dir5.20_server_linux.tar file from the IBM Director downloads page at: www.ibm.com/systems/management/director/ downloads.html. b. Extract the contents of the dir5.20_server_linux.tar file into a local directory. c. To change to the directory in which IBM Director Server is located, type the following command and press Enter: cd /directory/director/server/linux/i386/
where directory is the local directory into which you extracted the files. Go to step 5. 2. To install IBM Director Server from a CD, insert the IBM Director on x86, V5.20 CD into the drive. 3. If the CD automounts, go to step 4. If the CD does not automount, 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. 4. 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. 5. Type the following command and press Enter to copy the response file (dirserv.rsp) to a local directory : cp dirserv.rsp /directory
where directory is the local directory. 6. Use an ASCII text editor to open the copy of the response file, and change the value of the ExpressInstall parameter to 1. In the response file, ″1″ indicates that an item is to be installed and ″0″ indicates that an item is not to be installed. 7. Save the modified response file. 8. Type the following command and press Enter: ./dirinstall -r /directory/response.rsp
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 7. 9. The License Agreement message is displayed. If you agree with the terms, proceed with the installation. Otherwise, cancel the installation. The installation progress displays. 10. 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
where install_root represents the root directory of your IBM Director installation. 11. To start IBM Director, type the following command and press Enter: install_root/bin/twgstart
12. If you used a CD, unmount the drive by completing the following steps:
62
IBM Director Express Planning, Installation and Configuration Guide
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. 13. If you used a CD, remove the CD from the drive. Note: (AIX and Linux only) If you log into IBM Director Console using the root account, all the IBM Director tasks for a Standard installation are displayed.
Installing IBM Director Server on Linux for System z using the Express installation option After preparing your server, you can use the Express installation option to install IBM Director Server on Linux for System z. To perform an Express installation, you must run the dirinstall script against a response file in which the ExpressInstall parameter is enabled. Important: v IBM Director Server and IBM Director Console must be at the same release level. If you install IBM Director Server, version 5.20 on the management server, you must also install IBM Director Console, version 5.20 on any systems that you want to access the management server. In addition, 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. Management servers running i5/OS, IBM Director Server use the DB2 database. On all other operating systems, the default database is Apache Derby, but other databases can be used. v 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. On management servers running i5/OS, however, IBM Director Server does not include IBM Director Console. 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 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. To use the Express installation option to install IBM Director Server on Linux for System z, complete the following steps: 1. Make available to your Linux system the installation code from the IBM Director for Linux on System z, V5.20 CD. You can obtain an ISO image of this
Chapter 4. Installing IBM Director using the Express installation
63
CD from ShopzSeries at www.ibm.com/software/ShopzSeries or from the IBM Director Web site at www.ibm.com/systems/management/director/ . 2. Change to the directory where the installation script is located. Type the following command and press Enter: cd /mnt/director/server/linux/s390/
where /mnt is the mount point of the file system on the CD or the location of the IBM Director installation files. 3. Type the following command and press Enter to copy the response file (dirserv.rsp) to a local directory: cp dirserv.rsp /directory
where directory is the local directory. 4. Use an ASCII text editor to open the copy of the response file, and change the value of the ExpressInstall parameter to 1. In the response file, ″1″ indicates that an item is to be installed and ″0″ indicates that an item is not to be installed. 5. Save the modified response file. 6. Type the following command and press Enter: ./dirinstall -r /directory/response.rsp
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 5. 7. Optional: Configure IBM Director for use with a database application. See “Configuring the database on Linux or AIX” in the IBM Director Systems Management Guide for more information. 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. 8. The License Agreement message is displayed. If you agree with the terms, proceed with the installation. Otherwise, cancel the installation. The installation progress displays. 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: install_root/bin/cfgsecurity
where install_root represents the root directory of your IBM Director installation. 10. To start IBM Director, type the following command and press Enter: install_root/bin/twgstart
Note: (AIX and Linux only) If you log into IBM Director Console using the root account, all the IBM Director tasks for a Standard installation are displayed.
64
IBM Director Express Planning, Installation and Configuration Guide
Adding Standard installation options to an IBM Director Express installation If you use the IBM Director Express installation option to install IBM Director Server, a subset of IBM Director tasks are enabled by default. You can configure IBM Director Server to enable all the tasks that would have been displayed with a Standard installation. 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. Note: (AIX and Linux only) If you log into IBM Director Console using the root account, all the IBM Director tasks for a Standard installation are displayed. To add the Standard installation options to an IBM Director Express installation, complete the following steps: 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. 4. 5. 6. 7.
Note: If the Groups tab does not display, you must first create and authorize a user group on the management server. Select the group for which you want to enable the IBM Director tasks. Click Actions → Group → Edit. In the Group Editor window, click the Task Access tab to modify task access for the user group. To allow full access to all tasks, clear Limit user access only to the tasks selected. In the Group Editor window, click OK and then close the User Administration window.
Chapter 4. Installing IBM Director using the Express installation
65
66
IBM Director Express Planning, Installation and Configuration Guide
Chapter 5. 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 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. On management servers running i5/OS, however, IBM Director Server does not include IBM Director Console. 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 server. v IBM Director Server and IBM Director Console must be at the same release level. If you install IBM Director Server, version 5.20 on the management server, you must also install IBM Director Console, version 5.20 on any systems that you want to access the management server. In addition, 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 install IBM Director Console on AIX, complete the following steps: 1. To install IBM Director Console from a Web download, perform the following steps: a. Download the IBM Director for AIX - Version 5.20 (Dir5.20_AIX.tar.gz) file to a local directory from the IBM Director downloads page at: www.ibm.com/systems/management/director/downloads.html. b. To unzip and extract the contents of the Dir5.20_AIX.tar.gz file, type the following command: © Copyright IBM Corp. 1999, 2006
67
gzip -cd Dir5.20_AIX.tar.gz | tar -xvf -
Go to step 3. 2. To install IBM Director Console from the CD, perform the following steps: a. Insert the IBM Director for AIX 5L, V5.20 or the IBM Director for i5/OS, V5.20 CD into the drive. b. To mount the drive, 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 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. 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. 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. 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: ./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. 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.
68
IBM Director Express Planning, Installation and Configuration Guide
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. To install IBM Director Console on Linux for System x, complete the following steps: 1. To install IBM Director Console from a Web download, perform the following steps: a. Download the dir5.20_console_linux.tar file from the IBM Director Support Web site at www.ibm.com/systems/management/director/ . b. Extract the contents of the dir5.20_console_linux.tar file into a local directory. c. Change to the directory in which the installation script is located. Type the following command and press Enter: cd /directory/
where directory is the local directory into which you extracted the files. d. If you want to customize the installation, go to step 1e. If you want to accept the default settings for the installation, type the following command and press Enter: ./dir5.20_console_linux.sh
e. 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. f. 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. g. Save the modified response file. h. To install IBM Director Console using the response file, type the following command and press Enter: ./dir5.20_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 IBM Director on x86, V5.20 or IBM Director Agents & Consoles, V5.20 (2 of 2) CD into the drive. b. If the CD automounts, go to step 2c. If the CD does not automount, 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/console/linux/i386
Chapter 5. Installing IBM Director Console
69
where mnt/cdrom is the mount point of the drive. Go to step 2d. d. If you want to customize the installation, go to step 2e. If you want to accept the default settings for the installation, type the following command and press Enter: ./dirinstall
Go to step 2i. e. 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. f. 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. g. Save the modified response file with a new file name. h. To install IBM Director Console using the modified response file, type the following command and press Enter: ./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 saved in step 2g. i. To unmount the drive, complete the following steps: 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. j. Remove the CD from the drive.
Installing IBM Director Console on Linux for System z This topic describes how to install IBM Director Console on Linux for System z. Complete the following steps to install IBM Director Console on Linux for System z: 1. Make the installation code available to your Linux system. You can obtain the installation code: v From the IBM Director for Linux on System z, V5.20 CD v From the IBM Director Agents & Consoles, V5.20 (2 of 2) CD You can obtain ISO images of these CDs from ShopzSeries at www.ibm.com/software/ShopzSeries or from the IBM Director Web site at www.ibm.com/systems/management/director/ . See “Preparing to install IBM Director Server on Linux for System z ” on page 47 for more information. 2. Change to the directory in which the installation script is located. Type the following command and press Enter: cd /mnt/director/console/linux/s390/
70
IBM Director Express Planning, Installation and Configuration Guide
where /mnt is the mount point of the file system on the CD or the location of the IBM Director installation files. 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
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 9. 4. 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. 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 and select log file options. 6. Save the modified response file with a new file name. 7. To install IBM Director Console, 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. 8. Optional: Keep the response file for future use and reference. 9. 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 for POWER To install IBM Director Console on a system that is running Linux for 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. To install IBM Director Console on Linux for POWER, complete the following steps: 1. To install IBM Director Console from a Web download, perform the following steps: a. Download the Dir5.20_LinuxonPower.tar.gz file from the IBM Director Web site at: www.ibm.com/systems/management/director/ . b. To unzip and extract the contents of the Dir5.20_LinuxonPower.tar.gz file, type the following command: gzip -cd Dir5.20_LinuxonPower.tar.gz | tar -xvf -
Go to step 3 on page 72. 2. To install IBM Director Console from the CD, perform the following steps: a. Insert the IBM Director for Linux on POWER, V5.20 or IBM Director for i5/OS, V5.20 CD into the drive. b. If the CD automounts, go to step 2c on page 72. If the CD does not automount, type the following command and press Enter: Chapter 5. Installing IBM Director Console
71
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/console/linux/ppc
where mnt/cdrom 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
Go to step 8. 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
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. 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. 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
72
IBM Director Express Planning, Installation and Configuration Guide
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 change to the directory containing the ibmsetup.exe file and run the installation program using the following command: ibmsetup.exe admin
This command updates MSI and runs the installation program in administrative mode. Restart the system if prompted to do so.
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. To install IBM Director Console on Windows, complete the following steps: 1. To start the installation from a Web download, perform the following steps: a. Download the dir5.20_console_windows.zip file from the IBM Director downloads page at:www.ibm.com/systems/management/director/ downloads.html. b. Extract the contents of the dir5.20_console_windows.zip file into a local directory. c. Locate the dir5.20_console_windows.exe file and double-click it. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Console window opens. Go to step 4 on page 74. 2. Optional: (i5/OS only) To start the installation from the IBM Director Agents & Consoles, V5.20 (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 74. 3. To start the installation from the CD, perform the following steps: a. Insert the IBM Director on x86, V5.20 CD into the 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 74. 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. Chapter 5. Installing IBM Director Console
73
c. Browse to the director/console/windows/i386 directory on the IBM Director on x86, V5.20. 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. 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 dir5.20_console_windows.zip file from the IBM Director downloads page at:www.ibm.com/systems/management/director/ downloads.html. b. Extract the contents of the dir5.20_console_windows.zip file into a local directory. c. Locate and copy the dircon.rsp file. d. Go to step 3 on page 75. 2. Insert the IBM Director on x86, V5.20 or IBM Director Agents & Consoles, V5.20 (2 of 2)CD into the drive. a. If the installation program starts automatically and the IBM Director Setup window opens, close it.
74
IBM Director Express Planning, Installation and Configuration Guide
b. Copy the dircon.rsp file to a local directory. This file is in the director\console\windows\i386 directory on the CD. c. Go to step 3. 3. Open the copy of the dircon.rsp file in an ASCII text editor. 4. 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. 5. 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. 6. 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 4. v option is one of the following optional parameters: Table 30. Optional installation parameters Parameter
What it does
waitforme
Ensures that ibmsetup.exe process will not end until the installation of IBM Director Console is completed
debug
Logs all messages that are sent by the Microsoft Windows Installer log engine, including status and information messages
log=logfilename
Specifies the fully qualified name of an alternative log file
verbose
Enables verbose logging
7. If you installed IBM Director Console from the CD, remove the CD from the drive when the installation is completed.
Chapter 5. Installing IBM Director Console
75
76
IBM Director Express Planning, Installation and Configuration Guide
Chapter 6. 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. To install Level 1: IBM Director Core Services on Linux for System x, complete the following steps: 1. To start the installation from a Web download, perform the following steps: a. Download the dir5.20_coreservices_linux.tar file from the IBM Director Web site at www.ibm.com/systems/management/director/ . b. Extract the contents of the dir5.20_coreservices_linux.tar file into a local directory. c. Change to the directory in which the installation script is located. Type the following command and press Enter: cd /directory/FILES
where directory is the local directory into which you extracted the files. Go to step 3. 2. To start the installation from the CD, perform the following steps: a. Insert the IBM Director on x86, V5.20 or IBM Director Agents & Consoles, V5.20 (1 of 2) CD into the drive. b. If the CD automounts, go to step 2c. If the CD does not automount, 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/coresvcs/agent/linux/i386/FILES
where mnt/cdrom 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: ./dir5.20_coreservices_linux.sh
If you are installing from the CD, go to step 8 on page 78. If you are installing from a Web download, the installation is completed. 4. To customize the installation, copy the response file (coresvcs.rsp) to a local directory. Type the following command and press Enter: © Copyright IBM Corp. 1999, 2006
77
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 Level 1: IBM Director Core Services using the response file, type the following command and press Enter: ./dir5.20_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 saved in step 6. 8. If you installed IBM Director Core Services from the CD, complete 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. 9. Remove the CD from the drive. 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 To install Level 1: IBM Director Core Services on a system that is running Linux for System z, download the installation files Web or use the CD. You can perform a standard installation or you can use a response file to customize the installation for your environment. To install Level 1: IBM Director Core Serviceson Linux for System z, complete the following steps: 1. Make the installation code available to your Linux system. You can obtain the installation code: v From the IBM Director for Linux on System z, V5.20 CD. v From the IBM Director Agents & Consoles, V5.20 (1 of 2) CD. You can obtain ISO images of these CDs from ShopzSeries at www.ibm.com/software/ShopzSeries or from the .IBM Director Web site at www.ibm.com/systems/management/director/ . 2. 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 the location of the IBM Director installation files.
78
IBM Director Express Planning, Installation and Configuration Guide
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: ./csversion_agent_linz.sh
csversion is a prefix “cs” followed by the product version number. For version 5.20, the file name would be cs5.20_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. Go to step 9. 4. To customize the installation, 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. 5. Open an ASCII text editor and modify the installation settings in the copy of the coresvcs.rsp file. This file is fully commented. 6. Save the modified response file with a new file name. 7. 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 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. 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: /opt/ibm/director/bin/cfgsecurity
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 for POWER To install IBM Director Core Services on a system that is running Linux for 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. To install Level 1: IBM Director Core Services on Linux for POWER, complete the following steps: 1. To install IBM Director Core Services from a Web download, perform the following steps: a. Download the IBM Director for Linux on POWER - Version 5.20 (Dir5.20_LinuxonPower.tar.gz) file to a local directory from the IBM Director Web site at: www.ibm.com/systems/management/director/ . b. To unzip and extract the contents of the Dir5.20_LinuxonPower.tar.gz file, type the following command: gzip -cd Dir5.20_LinuxonPower.tar.gz | tar -xvf Chapter 6. Installing Level 1: IBM Director Core Services
79
Go to step 3. 2. To start the installation from the CD, perform the following steps: a. Insert the IBM Director for Linux on POWER, V5.20 or IBM Director for AIX 5L, V5.20 CD into the drive. b. If the CD automounts, go to step 2c. If the CD does not automount, 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/coresvcs/agent/linux/ppc/FILES
where mnt/cdrom 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: ./cs5.20_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 the following command and press Enter: ./cs5.20_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: 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.
80
IBM Director Express Planning, Installation and Configuration Guide
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. 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 change to the directory containing the dir5.20_coreservices_windows.exe file and run the installation program using the following command: dir5.20_coreservices_windows.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 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. To use the InstallShield wizard to install Level 1: IBM Director Core Services on Windows, complete the following steps: 1. To start the installation from a Web download, perform the following steps: a. Download the dir5.20_coreservices_windows.zip file from the IBM Director Support Web site at www.ibm.com/systems/management/director/ . b. Extract the contents of the dir5.20_coreservices_windows.zip file to a local directory. c. Locate the dir5.20_coreservices_windows.exe file and double-click it. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Core Services window opens. Go to step 4 on page 82. 2. Optional: To start the installation from the CD if you are using the IBM Director Agents & Consoles, V5.20 (1 of 2) CD, insert the CD into the drive. Browse to the coresvcs\agent\windows\i386\FILES directory and double-click dir5.20_coreservices_windows.exe. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Core Services window opens. Continue to step 4 on page 82. 3. To start the installation from the CD, perform the following steps: a. Insert the IBM Director on x86, V5.20 into the drive. b. If the installation program starts automatically and the IBM Director Setup window opens, go to step 3d on page 82. Otherwise, click Start → Run. c. In the Open field, type the following command and press Enter: e:\setup.exe
Chapter 6. Installing Level 1: IBM Director Core Services
81
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 InstallShield wizard starts, and the Welcome to the InstallShield Wizard for Core Services window opens. Continue to step 4. 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, V5.20.
4. 5.
6. 7. 8. 9.
d. Run the dir5.20_coreservices_windows.exe program. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Core Services window opens. Continue to step 4. Click Next. The License Agreement window opens. 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. Click Next. The Ready to Install the Program window opens. Click Install. The status bar displays the progress of the installation. When the installation is completed, the InstallShield Wizard Completed window opens. Click Finish. 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. To use a response file to install Level 1: IBM Director Core Services on Windows, complete the following steps: 1. To start the installation from a Web download, perform the following steps: a. Download the dir5.20_coreservices_windows.zip file from the IBM Director Support Web site at www.ibm.com/systems/management/director/ . b. Extract the contents of the dir5.20_coreservices_windows.zip file into a local directory. c. Locate and copy the coresvcs.rsp file. This file is in the local\FILES directory where local is the local directory into which you extracted the contents of the dir5.20_coreservices_windows.zip file. d. Go to step 3 on page 83. 2. Insert the IBM Director on x86, V5.20 or IBM Director Agents & Consoles, V5.20 (1 of 2) CD into the drive.
82
IBM Director Express Planning, Installation and Configuration Guide
3. 4. 5. 6.
a. If the installation program starts automatically and the IBM Director Setup window opens, close it. b. Copy the response file (coresvcs.rsp) to a local directory. This file is in the coreservices\agent\windows\i386\FILES directory on the CD. c. Go to step 3. Open the copy of the coresvcs.rsp file in an ASCII text editor. Modify and save the response file with a new file name. This file follows the Windows INI file format and is fully commented. Open a command prompt and change to the directory that contains the IBM Director Core Services installation file (dir5.20_coreservices_windows.exe). From the command prompt, type the following command (all on one line) and press Enter: dir5.20_coreservices_windows.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 4. v option is one of the following optional parameters: Table 31. Optional installation parameters Optional parameter
What it does
waitforme
Ensures that dir5.20_coreservices_windows.exe process will not end until the installation of IBM Director Core Services is completed
debug
Logs all messages that are sent by the Microsoft Windows Installer log engine, including status and information messages
log=logfilename
Specifies the fully qualified name of an alternative log file
verbose
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.
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.
Chapter 6. Installing Level 1: IBM Director Core Services
83
The following files describe IBM Director Core Services: v dir5.20_coreservices_linux.xml This file is located in the coresvcs/agent/linux/i386/META-INF directory on the IBM Director on x86, V5.20 and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v cs5.20_agent_linppc.xml This file is located in the coresvcs/agent/linux/ppc/META-INF directory on the IBM Director for AIX 5L, V5.20 and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v cs5.20_agent_linz.xml This file is located in the coresvcs/agent/linux/s390/META-INF/ directory on the IBM Director for Linux on System z, V5.20 and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v dir5.20_coreservices_windows.xml This file is located in the coresvcs\agent\windows\i386\META-INF directory on the IBM Director on x86, V5.20 and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. (System x ; Windows only) The following file describes both IBM Director Core Services and OpenSSH: v dir5.20_coreservices-toc_windows.xml This file is located in the coresvcs directory on the IBM Director on x86, V5.20 CD. When the dir5.20_coreservices-toc_windows.xml file is imported by the IBM Update Assistant, a software-distribution category containing both IBM Director Core Services and OpenSSH is created, allowing them both to be installed at the same time. The OpenSSH package can be used to provide a secure remote interface between a Level-1 managed system and IBM Director Server. Use the OpenSSH interface to run the Remote Session task or the cimsubscribe utility from IBM Director Server. The cimsubscribe utility provides a command-line interface for creating event subscriptions. (System x only) The following files describe the IBM LM78 device driver and the IBM SMBus device driver: v lm78driver_linux.xml v smbdriver_linux.xml You can download these files from the IBM Director Web site at www.ibm.com/systems/management/director/ . They are included in the .gz files containing the device drivers to which they apply. When you import the XML files into IBM Director, the IBM Update Assistant creates software packages. Then, you can use the IBM Director Software Distribution task to distribute the packages to the managed systems. 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 smbdriver_linux.xml file. Note: If an earlier version of the IBM LM78 or SMBus device driver for Linux is installed on the managed system, you must uninstall the device driver before installing version 5.20 of the driver.
84
IBM Director Express Planning, Installation and Configuration Guide
Related reference “IBM LM78 and SMBus device drivers for Linux” on page 43 This topic describes when to install the LM78 and SMBus device drivers for Linux.
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.
Figure 5. Creating a software package: Software Distribution Manager window (Standard Edition)
Figure 6. Creating a software package: Software Distribution Manager window (Premium Edition)
Chapter 6. Installing Level 1: IBM Director Core Services
85
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 85. 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.
86
IBM Director Express Planning, Installation and Configuration Guide
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.
Chapter 6. Installing Level 1: IBM Director Core Services
87
88
IBM Director Express Planning, Installation and Configuration Guide
Chapter 7. 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. 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. To install Level 2: IBM Director Agent on AIX, complete the following steps: 1. To install IBM Director Agent from a Web download, perform the following steps: a. Download the IBM Director for AIX - Version 5.20 (Dir5.20_AIX.tar.gz) file to a local directory from the IBM Director downloads page at: www.ibm.com/systems/management/director/downloads.html. b. To unzip and extract the contents of the Dir5.20_AIX.tar.gz file, type the following command: gzip -cd Dir5.20_AIX.tar.gz | tar -xvf -
Go to step 3 on page 90. 2. To start the installation from the CD, perform the following steps: a. Insert the IBM Director for AIX 5L, V5.20 CD or the IBM Director for Linux on POWER, V5.20 CD into the drive. © Copyright IBM Corp. 1999, 2006
89
b. If the CD automounts, go to step 2c. If the CD does not automount, type the following command and press Enter: mount /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. 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. 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.20_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: install_root/bin/cfgsecurity
where install_root is the root directory of your IBM Director installation. 9. To startIBM Director Agent, type the following command and press Enter: install_root/bin/twgstart
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.
90
IBM Director Express Planning, Installation and Configuration Guide
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. 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 IBM Director for i5/OS, V5.20 CD into the CD or DVD device. Note: As an alternative, you can use IBM Director Software Distribution to distribute IBM Director Agent to your managed systems. 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 IBM Director Agent using the Virtualization Engine This topic describes how you can install IBM Director Agent using the Remote Package Deployer, a part of the Virtualization Engine™. Before you distribute IBM Director Agent, you must have installed IBM Director Server along with IBM Director Agent images on your management server.
Using Remote Package Deployer You can install IBM Director Agent, Directori5OSRPD_agentpackagedIU.xml, from a command line using Remote Package Deployer (RPD). The default location for this file on the management server is at /QIBM/ProdData/VE2/ManagedNodes/ Directori5OS/META-INF. With RPD you must install IBM Director Agent to one system at a time. Refer to the instructions in the Virtualization Engine topic, Distributing agent software without IBM Director.
Chapter 7. Installing Level 2: IBM Director Agent
91
Installing IBM Director Agent on i5/OS using RSTLICPGM You can install IBM Director Agent on i5/OS using the Restore Licensed Program (RSTLICPGM) command. 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 IBM Director for i5/OS, V5.20 CD into the CD or DVD device. Note: As an alternative, you can use IBM Director Software Distribution to distribute IBM Director Agent to your managed systems. 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 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. To install Level 2: IBM Director Agent on Linux for System x, complete the following steps: 1. To start the installation from a Web download, perform the following steps: a. Download the dir5.20_agent_linux.tar file from the IBM Director Support Web site at www.ibm.com/systems/management/director/ . b. Extract the contents of the dir5.20_agent_linux.tar file into a local directory. c. Change to the directory in which the installation script is located. Type the following command and press Enter: cd /directory/FILES
where directory is the local directory into which you extracted the files. Go to step 3 on page 93.
92
IBM Director Express Planning, Installation and Configuration Guide
2. To start the installation from the CD, perform the following steps: a. Insert the IBM Director on x86, V5.20 or IBM Director Agents & Consoles, V5.20 (1 of 2) CD into the drive. b. If the CD automounts, go to step 2c. If the CD does not automount, 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/agent/linux/i386/FILES
where mnt/cdrom 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: ./dir5.20_agent_linux.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. 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_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: 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
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: install_root/bin/twgstart
10. If you installed IBM Director Agent from the CD, complete 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 CD-ROM drive. Remove the CD from the drive. Chapter 7. Installing Level 2: IBM Director Agent
93
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 Level 2: IBM Director Agent on a Linux for System z platform by downloading the installation file or using the CD. 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. Make the installation code available to your Linux system. You can obtain the installation code: v From the IBM Director for Linux on System z, V5.20 CD. v From the IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v As a Web download from www.ibm.com/systems/management/director/ . 2. 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 location of the IBM Director installation files. 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: ./dirversion_agent_linz.sh
dirversion is a prefix “dir” followed by the product version number. For version 5.20, the file name would be dir5.20_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 9 on page 95. 4. To customize the installation, copy the response file to a local directory. Type the following command and press Enter: cp diragent.rsp /directory
94
IBM Director Express Planning, Installation and Configuration Guide
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: ./dirversion_agent_linz.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: install_root/bin/cfgsecurity
where install_root is the root directory of your IBM Director installation. 9. To start IBM Director Agent, begin a new terminal session, type the following command, and press Enter: install_root/bin/twgstart
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 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 install Level 2: IBM Director Agent on Linux for POWER, complete the following steps: 1. To install IBM Director Agent from a Web download, perform the following steps: a. Download the Dir5.20_LinuxonPower.tar.gz file from the IBM Director Web site at www.ibm.com/systems/management/director/ . b. To unzip and extract the contents of the Dir5.20_LinuxonPower.tar.gz file, type the following command: gzip -cd Dir5.20_LinuxonPower.tar.gz | tar -xvf -
Go to step 3 on page 96. 2. To start the installation from the CD, perform the following steps: Chapter 7. Installing Level 2: IBM Director Agent
95
a. Insert the IBM Director for AIX 5L, V5.20 or IBM Director for Linux on POWER, V5.20 CD into the drive. b. If the CD automounts, go to step 2c. If the CD does not automount, 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/agent/linux/ppc/FILES
where mnt/cdrom 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: ./dir5.20_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: 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 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.20_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: install_root/bin/cfgsecurity
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: install_root/bin/twgstart
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.
96
IBM Director Express Planning, Installation and Configuration Guide
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 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: 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 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: install_root/bin/twgstart
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.
Chapter 7. Installing Level 2: IBM Director Agent
97
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. 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
98
IBM Director Express Planning, Installation and Configuration Guide
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. 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. 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 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 change to the directory containing the dir5.20_agent_windows.exe file and run the installation program using the following command: dir5.20_agent_windows.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 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.
Chapter 7. Installing Level 2: IBM Director Agent
99
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 dir5.20_agent_windows.zip file from theIBM Director Support Web site at www.ibm.com/systems/management/director/ . b. Extract the contents of the dir5.20_agent_windows.zip file into a local directory. c. Locate the dir5.20_agent_windows.exe file and double-click it. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Agent window opens. Go to step 4. 2. Optional: To start the installation from the CD if you are using the IBM Director Agents & Consoles, V5.20 (1 of 2) CD, insert the CD into the drive. Browse to the director\agent\windows\i386\FILES directory and double-click dir5.20_agent_windows.exe. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Agent window opens. Continue to step 4. 3. To start the installation from the CD, perform the following steps: a. Insert the IBM Director on x86, V5.20 CD into the 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 InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Agent window opens. Continue 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, V5.20. d. Run the dir5.20_agent_windows.exe program. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Agent window opens. Continue 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 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
100
IBM Director Express Planning, Installation and Configuration Guide
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.
9.
10.
11.
12. 13.
14.
15.
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>::, 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. 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.
Chapter 7. Installing Level 2: IBM Director Agent
101
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.
17. 18. 19. 20.
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. Click OK. The status bar displays the progress of the installation. When the installation is completed, the InstallShield Wizard Completed window opens. Click Finish. If you installed IBM Director Agent from the CD, remove the CD from the drive. 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. 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 dir5.20_agent_windows.zip file from theIBM Director Web site at www.ibm.com/systems/management/director/ . b. Extract the contents of the dir5.20_agent_windows.zip file into a local directory. c. Locate and copy the diragent.rsp file. This file is in the local\FILES directory where local is the local directory to which you extracted the contents of the dir5.20_agent_windows.zip file. d. Go to step 3. 2. Insert the IBM Director on x86, V5.20 or IBM Director Agents & Consoles, V5.20 (1 of 2) CD into the drive. a. If the installation program starts automatically and the IBM Director Setup window opens, close it. b. Copy the diragent.rsp file to a local directory. This file is located in the director\agent\windows\i386\FILES directory on the CD. c. Go to step 3. 3. Open the copy of the diragent.rsp file in an ASCII text editor. 4. Modify and save the diragent.rsp file with a new file name. This file follows the Windows INI file format and is fully commented.
102
IBM Director Express Planning, Installation and Configuration Guide
5. Open a command prompt and change to the directory that contains the Level 2: IBM Director Agent installation file (dir5.20_agent_windows.exe). 6. From the command prompt, type the following command and press Enter: dir5.20_agent_windows.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 saved in step 4 on page 102. v option is one of the following optional parameters: Table 32. Optional installation parameters Parameter
What it does
waitforme
Ensures that dir5.20_agent_windows.exe process will not end until the installation of IBM Director Agent is completed
debug
Logs all messages that are sent by the Microsoft Windows Installer log engine, including status and information messages
log=logfilename
Specifies the fully qualified name of an alternative log file
verbose
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 Chapter 7. Installing Level 2: IBM Director Agent
103
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. 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>::, for example, TCPIP::10.3.1.4, TCPIP::192.168-1.10.
104
IBM Director Express Planning, Installation and Configuration Guide
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. 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.
Chapter 7. Installing Level 2: IBM Director Agent
105
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. 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. v option is one of the following optional parameters: Table 33. Optional installation parameters Parameter
What it does
waitforme
Ensures that dir5.10.3_agent_windows64.exe process will not end until the installation of IBM Director Agent is completed
debug
Logs all messages that are sent by the Microsoft Windows Installer log engine, including status and information messages
log=logfilename
Specifies the fully qualified name of an alternative log file
verbose
Enables verbose logging
8. If you set the RebootIfRequired parameter to Y in the response file, reboot the system if prompted to do so.
106
IBM Director Express Planning, Installation and Configuration Guide
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: v dir5.20_agent_aix.xml This file is located in the director/agent/aix/META-INF directory on the IBM Director for AIX 5L, V5.20 IBM Director for Linux on POWER, V5.20, and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v dir5.20_agent_linux.xml This file is located in the director/agent/linux/i386/META-INF directory on the IBM Director on x86, V5.20 and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v dir5.20_agent_linppc.xml This file is located in the director/agent/linux/ppc/META-INF directory on the IBM Director for AIX 5L, V5.20, IBM Director for Linux on POWER, V5.20, and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v dir5.20_agent_linz.xml This file is located in the director/agent/linux/s390/META-INF/ directory on the IBM Director for Linux on System z, V5.20 and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v dir5.20_agent_windows.xml This file is located in the director\agent\windows\i386\META-INF directory on the IBM Director on x86, V5.20 and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v Directori5OSRPD_agentpackagedIU.xml The default location for this file on an i5/OS management server, if you have selected to install the IBM Director Agent images, is at /QIBM/ProdData/VE2/ ManagedNodes/Directori5OS/META-INF. If you have not installed IBM Director Server for i5/OS, this file is included on the IBM Director Agents & Consoles, V5.20 (1 of 2)CD. You can access it from the \FILES\Director directory, in the Directori5OSAgent.zip file. IBM Director 5.20 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. The following files describe the 64-bit, Intel Itanium versions of the IBM Director Agent: v dir5.10.3_agent_linux64.xml v dir5.10.3_agent_windows64.xml (System x only) The following files describe the IBM LM78 and IBM SMBus device drivers: v lm78driver_linux.xml v smbdriver_linux.xml
Chapter 7. Installing Level 2: IBM Director Agent
107
You can download these files from the IBM Director Support Web site at www.ibm.com/systems/management/director/ . They are included in the .zip or .gz packages for the component or device driver to which they apply. When you import the XML files into IBM Director, the IBM Update Assistant creates software packages. Then, you can use the IBM Director Software Distribution task to distribute the packages to the managed systems. 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 lm78driver_linux.xml or smbdriver_linux.xml file. Note: If an earlier version of the IBM LM78 or SMBus device driver for Linux is installed on the managed system, you must uninstall the device driver before installing version 5.20 of the driver. Related reference “IBM LM78 and SMBus device drivers for Linux” on page 43 This topic describes when to install the LM78 and SMBus device drivers for Linux.
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.
Figure 7. Creating a software package: Software Distribution Manager window (Standard Edition)
108
IBM Director Express Planning, Installation and Configuration Guide
Figure 8. 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 108. 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.
Chapter 7. Installing Level 2: IBM Director Agent
109
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.
110
IBM Director Express Planning, Installation and Configuration Guide
Chapter 8. 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.
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.
3.
4. 5. 6. 7.
8. 9.
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.
© Copyright IBM Corp. 1999, 2006
111
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. 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. b. c. d.
Select the location where the program should be started. Type the Host name of the selected system. Type the working directory of the program that needs to start. Type the Program name of the application that needs to start.
13. Click Next. 14. 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. 15. Click Next. 16. On the Summary page, verify the details of the event action plan. If you need to make changes, click < Back. 17. Click Finish.
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.
112
IBM Director Express Planning, Installation and Configuration Guide
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.
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.
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 (/). 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.
Chapter 8. Initially configuring IBM Director
113
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:
Set the ldap.auth.jndi property to:
IBM Director Server on i5/OS
true
IBM Director Server on AIX, and not using Pluggable Authentication Module (PAM) authentication.
true
IBM Director Server on Linux, and not using Pluggable Authentication Module (PAM) authentication.
true
IBM Director Server on Windows, and using an LDAP server other than Active Directory.
true
All other conditions.
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.
dn
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
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
7. 8.
9. 10.
anonymous DIGEST-MD5 Set the ldap.enabled property to true. You might have to add the ldap.enabled property to the dirldap.properties file. Optional: Modify other properties in the dirldap.properties file as needed. These properties are described in Appendix B, “Lightweight Directory Access Protocol authentication properties for IBM Director Server,” on page 159. Save and close the changed dirldap.properties file. 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.”
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.
114
IBM Director Express Planning, Installation and Configuration Guide
Note: A high-availability application is required for implementation of IBM Director high-availability configuration. For management servers running Linux, you might consider using IBM Tivoli System Automation for Multiplatforms. For management servers running Windows, you might consider using SteelEye’s 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, 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/Apache Derby). This database should be configured for high availability as described in the database documentation. 4. Create a network share to use as the IBM Director Server data directory. a. Create the network share. The network share should be made highly available using RAID or another method. b. Copy the contents of install_root/data from one of the management servers to the network share. c. 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 (/). 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.
Chapter 8. Initially configuring IBM Director
115
Preparing a high-availability environment for IBM Director and SteelEye®’s LifeKeeper™ In order for IBM Director to provide high availability, 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/Apache Derby). This database should be configured for high availability as described in the database documentation. 4. Optional: Create a network share to use as the IBM Director Server data directory. a. Create the network share. The network share should be made highly available using RAID or another method. b. Copy the contents of install_root/data from one of the management servers to the network share. c. 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 (/).
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 SteelEye’s 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.
116
IBM Director Express Planning, Installation and Configuration Guide
This tradeoff is summarized in the following table. Configuration
Benefit
Cost
High-availability not enabled Improved performance. (default configuration).
Loss of data on failover.
High-availability enabled.
Decreased performance.
Minimal loss of data on failover.
Incomplete tasks restart from beginning.
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
Command
AIX, Linux, and Windows
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 (/).
i5/OS
Using an ASCII text editor, open the /QIBM/UserData/ Director/data/softwaredist/TWGServer.prop file.
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 118. 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. Chapter 8. Initially configuring IBM Director
117
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
Commands
AIX or Linux
install_root/bin/twgstop install_root/bin/twgstart
i5/OS
QSH CMD(’/QIBM/ProdData/Director/bin/twgstop’) QSH CMD(’/QIBM/ProdData/Director/bin/twgstart’)
NetWare
unload twgipc load twgipc
Windows
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.
118
IBM Director Express Planning, Installation and Configuration Guide
2. Click the BladeCenter Chassis 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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
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
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type.
1 - 240
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:
Complete these steps:
Add a predefined parameter
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% Chapter 8. Initially configuring IBM Director
119
v %MM_NAME% 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.
120
IBM Director Express Planning, Installation and Configuration Guide
To do this:
Complete these steps:
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. Select the entry to be changed in the Address Entries list. Click Edit. Change the field values for the entry. Click OK.
Change an existing address entry
1. 2. 3. 4.
Delete an existing address entry
1. Select the entry to be deleted in the Address Entries list. 2. Click Remove. 3. If prompted, click Yes.
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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
IBM Director Server automatically discovers managed systems every n hours, where n is the selected number.
5. 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
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type.
1 - 240
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.
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. Chapter 8. Initially configuring IBM Director
121
Configuring discovery preferences for Level-1 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. 3. Select a discovery method to use and complete the specified configuration steps. Discovery method
Steps
Use Service 1. Specify one or more SLP directory agent servers to use. The selected Location Protocol SLP directory agents are displayed in the Predefined directory agent (SLP) directory servers list box. agents 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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
IBM Director Server automatically discovers managed systems every n hours, where n is the selected number.
6. Click OK.
122
IBM Director Express Planning, Installation and Configuration Guide
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, 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-2 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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
IBM Director Server automatically discovers managed systems every n hours, where n is the selected number.
5. 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
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type.
1 - 240
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.
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.
Chapter 8. Initially configuring IBM Director
123
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. 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:
Complete these steps:
Add an address and mask for broadcast discovery
1. 2. 3. 4. 5.
Click Add. Click Broadcast. Click Next. Type values in the IP Address and Subnet Mask fields. Click OK.
Add an address and mask for broadcast relay discovery
1. 2. 3. 4. 5.
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
124
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.
IBM Director Express Planning, Installation and Configuration Guide
To do this:
Complete these steps:
Delete an existing address entry
1. Select the entry to be deleted in the Address Entries list. 2. Click Remove. 3. If prompted, click Yes.
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: 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. Select the entry to be changed in the Address Entries list. Click Edit. Change the field values for the entry. Click OK.
Change an existing address entry
1. 2. 3. 4.
Delete an existing address entry
1. Select the entry to be deleted in the Address Entries list. 2. Click Remove. 3. If prompted, click Yes.
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. Chapter 8. Initially configuring IBM Director
125
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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
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
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type. This is the default value for physical platforms.
1-240
IBM Director Server attempts to contact managed objects of this type every n minutes, where n is the selected number.
5. Specify a template for naming physical platforms that IBM Director Server discovers. To perform this action:
Complete these steps:
Add a predefined parameter
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 %SERVER_MACHINE_TYPE_MODEL% v %SERVER_SERIAL_NUMBER% v %SERVER_FRU% v %SP_FRU%
126
IBM Director Express Planning, Installation and Configuration Guide
v v v v v v v
%SP_SERIAL_NUMBER% %CHASSIS_SLOT% %CHASSIS_SLOT_RANGE% %CHASSIS_NAME% %SP_TEXT_ID% %SP_IP_ADDRESS% %SP_HOSTNAME%
v %SP_ASSET_TAG% v %DIR_AGENT_NAME% v %COMPUTER_NAME% 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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
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 Chapter 8. Initially configuring IBM Director
127
(minutes). Option
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type.
1 - 240
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. 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. To do this:
Complete these steps:
Add an SLP profile
1. In the Available Profiles list, click a profile to add. 2. Click Add.
Remove an SLP profile
1. In the Selected Profiles list, click a profile to remove. 2. Click Remove.
Restore the Selected Profiles list to the default values
Select the Reset to default value check box. If prompted, click Yes.
6. Select a discovery method to use and complete the specified configuration steps. Discovery method
Steps
Use Service 1. Specify one or more SLP directory agent servers to use. The selected Location Protocol SLP directory agents are displayed in the Predefined directory agent (SLP) directory servers list box. agents 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.
128
IBM Director Express Planning, Installation and Configuration Guide
7. 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. 8. 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
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
IBM Director Server automatically discovers managed systems every n hours, where n is the selected number.
9. Specify a template for naming SMI-S storage devices that IBM Director Server discovers. To perform this action:
Complete these steps:
Add a predefined parameter
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 %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.
Chapter 8. Initially configuring IBM Director
129
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. 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 Server’s 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
130
IBM Director Express Planning, Installation and Configuration Guide
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:
Complete these steps:
Add a new seed address for SNMP discovery
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.
Add a list of seed addresses from a text file
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.
Change an existing seed address
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.
Delete an existing seed address
1. Click the entry to be deleted in the IP Addresses and Subnet Masks list. 2. Click Remove. 3. If prompted, click Yes.
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.
Chapter 8. Initially configuring IBM Director
131
To do this:
Complete these steps:
Add a profile name
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.
Delete a profile name
1. Click the profile name to be deleted. 2. Click Remove. 3. If prompted, click Yes.
7. 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
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
IBM Director Server automatically discovers managed systems every n hours, where n is the selected number.
8. 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
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type.
1 - 240
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.
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.
132
IBM Director Express Planning, Installation and Configuration Guide
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. 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. Discovery method
Steps
Use Service 1. Specify one or more SLP directory agent servers to use. The selected Location Protocol SLP directory agents are displayed in the Predefined directory agent (SLP) directory servers list box. agents 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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
Chapter 8. Initially configuring IBM Director
133
Option
Description
1 - 168
IBM Director Server automatically discovers managed systems every n hours, where n is the selected number.
6. 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
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type.
1 - 240
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 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. 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.
134
IBM Director Express Planning, Installation and Configuration Guide
Discovery method
Steps
Use Service 1. Specify one or more SLP directory agent servers to use. The selected Location Protocol SLP directory agents are displayed in the Predefined directory agent (SLP) directory servers list box. agents 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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
IBM Director Server automatically discovers managed systems every n hours, where n is the selected number.
6. 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
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type.
1 - 240
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.
Chapter 8. Initially configuring IBM Director
135
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 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 Console. Discovery of managed systems can take minutes or
136
IBM Director Express Planning, Installation and Configuration Guide
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. Chapter 8. Initially configuring IBM Director
137
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:
138
IBM Director Express Planning, Installation and Configuration Guide
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. Chapter 8. Initially configuring IBM Director
139
4. To add a share, click Add. 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 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
140
VMware ESX Server, version 3.0 Console
IBM Director Express Planning, Installation and Configuration Guide
Enabling SNMP access and trap forwarding for Linux managed systems 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.
Enabling SNMP access and trap forwarding for Red Hat Enterprise Linux versions 3 and 4 The OpenIPMI driver supported on Red Hat Enterprise Linux versions 3 and 4 has a dependency on the version of Net-SNMP that is included with those Linux distributions. IBM Director Core Services requires a different Net-SNMP version, 5.2.1. Installation of Net-SNMP 5.2.1 without removing the existing Net-SNMP version is required for IBM Director SNMP access and trap forwarding without compromising OpenIPMI services. Complete the following steps to enable SNMP access and trap forwarding for managed systems running Red Hat Enterprise Linux versions 3 and 4: 1. Download the net-snmp-5.2.1.tar.gz file from the Net-SNMP Web site at www.net-snmp.org/download.html. 2. Build and install the Net-SNMP libraries using the following steps. Notes: v This procedure does not perform a full installation of Net-SNMP, but installs only the Net-SNMP libraries, which are required for IBM Director Core Services SNMP functions. v Refer to the INSTALL and README files included in the net-snmp-5.2.1.tar.gz package for additional installation information. a. Untar the source files. Type the following command and press Enter. tar -xvzf net-snmp-5.2.1.tar.gz
b. Change to the source directory. Type the following command and press Enter. cd net-snmp-5.2.1
c. Build the Net-SNMP libraries with default options. Type the following commands (press Enter after each). ./configure --with-defaults make
d. Install the Net-SNMP libraries only to /usr/local/lib. Type the following command and press Enter. make installlibs
3. To enable trap forwarding, edit the /etc/init.d/dacimlist file and uncomment the following two lines two lines in the SNMP End Consumer section.
Chapter 8. Initially configuring IBM Director
141
LD_LIBRARY_PATH=/usr/local/lib export LD_LIBRARY_PATH
Note: The configuration changes will not take effect until you restart the cimlistener daemon in step 7. 4. To enable SNMP access, edit the /etc/init.d/dasnmp file and uncomment the following two lines in the section regarding the location of the net-snmp libraries. LD_LIBRARY_PATH=/usr/local/lib export LD_LIBRARY_PATH
5. Configure the SNMP daemon that ships with Red Hat Enterprise Linux to support AgentX agents. For details, see the documentation on the Net-SNMP Web Site. 6. Create the file /usr/local/share/snmp/snmpd.conf to specify trapsink and trapcommunity settings. You might have to create the directory. This file should contain only settings for trapcommunity and trapsink. a. Specify a trap community value by adding a line containing the word trapcommunity followed by a space and the trapcommunity value, as in the following example. trapcommunity public
b. Specify a trapsink value for each destination to which IBM Director will send SNMP traps. Add a line containing the word trapsink followed by a space and the trapsink value, as in the following example. trapsink 192.168.1.1
7. Restart the cimlistener daemon by typing the following commands and pressing Enter after each: /etc/init.d/dacimlist stop /etc/init.d/dacimlist start
8. Restart the IBM Director AgentX subagent by typing the following commands and pressing Enter after each: /etc/init.d/dasnmp stop /etc/init.d/dasnmp start
Enabling SNMP access and trap forwarding for VMware IBM Director supports SNMP access and trap forwarding on VMware ESX Server, and will inter-operate with the ucd-snmp versions that ship with VMware ESX Server versions 2.5.2 and 3.0. These instructions apply only to using IBM Director SNMP support on VMware ESX Server. Complete the following steps to enable SNMP access and trap forwarding for managed systems running VMware: 1. Download the net-snmp-5.2.1.tar.gz file from the Net-SNMP Web site at www.net-snmp.org/download.html. 2. Build and install the Net-SNMP libraries using the following steps. Notes: v This procedure does not perform a full installation of Net-SNMP, but installs only the Net-SNMP libraries, which are required for IBM Director Core Services SNMP functions. v Refer to the INSTALL and README files included in the net-snmp-5.2.1.tar.gz package for additional installation information.
142
IBM Director Express Planning, Installation and Configuration Guide
a. Untar the source files. Type the following command and press Enter. tar -xvzf net-snmp-5.2.1.tar.gz
b. Change to the source directory. Type the following command and press Enter. cd net-snmp-5.2.1
c. Build the Net-SNMP libraries with default options. Type the following commands (press Enter after each). ./configure --with-defaults make
d. Install the Net-SNMP libraries only to /usr/local/lib. Type the following command and press Enter. make installlibs
3. To enable trap forwarding, edit the /etc/init.d/dacimlist file and uncomment the following two lines two lines in the SNMP End Consumer section. LD_LIBRARY_PATH=/usr/local/lib export LD_LIBRARY_PATH
Note: The configuration changes will not take effect until you restart the cimlistener daemon in step 7. 4. To enable SNMP access, edit the /etc/init.d/dasnmp file and uncomment the following two lines in the section regarding the location of the net-snmp libraries. LD_LIBRARY_PATH=/usr/local/lib export LD_LIBRARY_PATH
5. Using the VMware Management Interface, configure the SNMP daemon that ships with VMware to support AgentX agents. For details, see the VMware documentation at www.vmware.com/support/pubs/esx_pubs.html. 6. Create the file /usr/local/share/snmp/snmpd.conf to specify trapsink and trapcommunity settings. You might have to create the directory. This file should contain only settings for trapcommunity and trapsink. a. Specify a trap community value by adding a line containing the word trapcommunity followed by a space and the trapcommunity value, as in the following example. trapcommunity public
b. Specify a trapsink value for each destination to which IBM Director will send SNMP traps. Add a line containing the word trapsink followed by a space and the trapsink value, as in the following example. trapsink 192.168.1.1
7. Restart the cimlistener daemon by typing the following commands and pressing Enter after each: /etc/init.d/dacimlist stop /etc/init.d/dacimlist start
8. Restart the IBM Director AgentX subagent by typing the following commands and pressing Enter after each: /etc/init.d/dasnmp stop /etc/init.d/dasnmp start
Chapter 8. Initially configuring IBM Director
143
144
IBM Director Express Planning, Installation and Configuration Guide
Chapter 9. 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 1. 2. 3.
uninstall IBM Director, complete the following steps: Shut down all applications. Click Start → Settings → Control Panel. The Control Panel window opens. 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.
© Copyright IBM Corp. 1999, 2006
145
Table 34. dirunins parameters Variable
Parameter
What it does
option
debug
Logs all messages that are sent by the Windows Installer log engine, including status and information messages
deletedata
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.
log=logfilename Specifies the fully qualified name of an alternative installation log file
directorcomponent
noreboot
Suppresses any required restart
silent
Suppresses all output to the screen
unattended
Shows the progress of the uninstallation but does not require any user input
verbose
Enables verbose logging
server
Uninstalls IBM Director Server and any installed IBM Director extensions
console
Uninstalls IBM Director Console and any installed IBM Director extensions
agent
Uninstalls Level 2: IBM Director Agent
coresvcs
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.
146
IBM Director Express Planning, Installation and Configuration Guide
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 41 on page 149. v Update Manager uses additional keyboard shortcuts for table navigation. For more information, see Table 58 on page 154. Table 35. Keyboard shortcuts for windows Action
Keyboard shortcut
Navigate out of the window.
Alt+F6
Hide the window.
Esc
Activate the default button (if defined).
Enter
Table 36. Keyboard shortcuts for option panes Action
Keyboard shortcut
Navigate in or out of the option pane.
Alt+F6
Hide a window.
Esc
Activate the default button (if defined).
Enter
Table 37. Keyboard shortcuts for scroll panes Action
Keyboard shortcut
Navigate forward out of the scroll pane.
Tab
Navigate backward out of the scroll pane.
Shift+Tab
Move up or down.
Up arrow or down arrow
© Copyright IBM Corp. 1999, 2006
147
Table 37. Keyboard shortcuts for scroll panes (continued) Action
Keyboard shortcut
Move left or right.
Left arrow or right arrow.
Navigate to the beginning or end of data.
Ctrl+Home or Ctrl+End
Navigate up or down one block.
PgUp or PgDn
Navigate to the left or right.
Ctrl+PgUp or Ctrl+PgDn
Table 38. Keyboard shortcuts for split panes Action
Keyboard shortcut
Navigate forward out of the split pane.
Tab or Ctrl+Tab
Navigate backward out of the split pane.
Shift+Tab or Ctrl+Shift+Tab
Navigate between split panes.
Tab or F6
Navigate to the splitter bar.
F8
Toggle the focus between two split bars (for windows with three split panes).
F8
Resize the split pane vertically.
Up arrow or down arrow
Resize the split pane horizontally.
Left arrow or right arrow
Maximize the size of the split pane .
Home
Minimize the size of the split pane.
End
Table 39. Keyboard shortcuts for notebooks (tabbed panes) Action
Keyboard shortcut
Navigate into the tabbed pane.
Tab
Navigate out of the tabbed pane.
Ctrl+Tab
Navigate to the left or right tab.
Left arrow or right arrow
Navigate to the tab above or below.
Up arrow or down arrow
Navigate from the tab to the page.
Enter or Ctrl+Down
Navigate from the page to the tab.
Ctrl+Up
Navigate to the previous or next page.
Ctrl+PgUp or Ctrl+PgDn
Table 40. Keyboard shortcuts for frames
148
Action
Keyboard shortcut
Display a window menu.
Alt+Space bar
Activate the default button (if defined).
Enter
IBM Director Express Planning, Installation and Configuration Guide
Table 41. Additional keyboard shortcuts for frames in External Application Launch wizard Action
Keyboard shortcut
To move focus to the description area when focus is currently on any of the first five event filters
Esc
To move focus to the description area when focus is currently on any other event filter
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 42. Keyboard shortcuts for internal frames Action
Keyboard shortcut
Open or restore the frame.
Ctrl+F5, Alt+F5, or Enter
Close the frame.
Ctrl+F4 or Alt+F5
Move the frame.
Ctrl+F7 or Alt+F7
Resize the frame.
Ctrl+F8 or Alt+F8
Minimize the frame size.
Ctrl+F9 or Alt+F9
Display a window menu.
Alt+Space bar
Activate the default button (if defined).
Enter
Table 43. Keyboard shortcuts for menu bar Action
Keyboard shortcut
Jump to the menu bar.
Alt or F10
Navigate out of the menu bar.
Esc or Alt
Navigate within the menu bar.
Arrow keys
Select the next or previous menu item.
Right arrow or left arrow
Activate the default or selected item.
Enter
Display a menu.
Use one of these keyboard shortcuts: v Up arrow v Down arrow v Enter v Space bar v Alt+Character accelerator key (if defined)
Hide a menu.
Esc or Alt
Table 44. Keyboard shortcuts for menus Action
Keyboard shortcut
Display a menu.
Enter or F10 Appendix A. Accessibility features for IBM Director
149
Table 44. Keyboard shortcuts for menus (continued) Action
Keyboard shortcut
Display a submenu.
Right arrow
Navigate to the next item or wrap to the top.
Down arrow
Navigate to the previous item or wrap to the bottom.
Up arrow
Hide the menu.
Esc
Hide the submenu.
Left arrow
Activate the default or selected item.
Enter
Table 45. Keyboard shortcuts for menu items Action
Keyboard shortcut
Navigate in or out of a menu.
Arrow keys
Activate an item.
Enter, space bar, or Alt+Character accelerator key (if defined)
Display a submenu.
Right arrow
Hide a submenu.
Left arrow or Esc
Table 46. Keyboard shortcuts for check-box menu items Action
Keyboard shortcut
Navigate in or out of the check-box menu.
Arrow keys
Select or clear a check-box menu item.
Enter
Hide a check-box menu.
Enter
Table 47. Keyboard shortcuts for radio-button menu items Action
Keyboard shortcut
Navigate in or out of a radio-button menu.
Arrow keys
Select or clear a radio-button menu item.
Enter
Hide a radio-button menu.
Enter
Table 48. Keyboard shortcuts for pop-up menus Action
Keyboard shortcut
Display a pop-up menu.
Shift+F10
Display a pop-up submenu.
Right arrow
Hide a pop-up menu.
Esc
Hide a submenu.
Left arrow
Navigate within a pop-up menu.
Up arrow or down arrow
Activate a pop-up menu item.
Enter or space bar
Table 49. Keyboard shortcuts for toolbar
150
Action
Keyboard shortcut
Navigate forward out of the toolbar.
Tab
IBM Director Express Planning, Installation and Configuration Guide
Table 49. Keyboard shortcuts for toolbar (continued) Action
Keyboard shortcut
Navigate backward out of the toolbar.
Shift+Tab
Navigate within the toolbar.
Arrow keys
Activate a toolbar item.
Enter
Display the Customized Toolbar menu (when focus is on an icon on the main IBM Director Console window toolbar).
Shift+10
Table 50. Keyboard shortcuts for tool tips Action
Keyboard shortcut
Display a tool tip.
Ctrl+F1
Hide a tool tip.
Esc or Ctrl+F1
Table 51. Keyboard shortcuts for buttons Action
Keyboard shortcut
Navigate forward.
Tab
Navigate backward.
Shift+Tab
Activate the default button.
Enter
Activate any button
Space bar or Alt+Character accelerator key (if defined).
Activate Cancel or Close.
Esc
Table 52. Keyboard shortcuts for check boxes Action
Keyboard shortcut
Navigate forward.
Tab
Navigate backward.
Shift+Tab
Navigate within a group.
Arrow keys
Select or clear a check box.
Space bar
Table 53. Keyboard shortcuts for radio buttons Action
Keyboard shortcut
Navigate forward.
Tab
Navigate backward.
Shift+Tab
Navigate within a group.
Arrow keys Note: To select the radio button, navigate to it.
Select or clear a radio button.
Space bar
Table 54. Keyboard shortcuts for combination boxes Action
Keyboard shortcut
Navigate forward out of the combination box.
Tab
Navigate backward out of the combination box.
Shift+Tab
Appendix A. Accessibility features for IBM Director
151
Table 54. Keyboard shortcuts for combination boxes (continued) Action
Keyboard shortcut
Navigate into a combination box within a table cell (focus must be in the table cell).
F2
Display the drop-down list.
Down arrow
Hide the drop-down list.
Esc or Alt+Up arrow
Activate the selected menu item.
Enter
Navigate up or down the drop-down list.
Alt+Up arrow or Alt+Down arrow
Navigate up or down the drop-down list for a combination box in a table.
Up arrow or Down arrow
Navigate to a list item without selecting it.
Initial character of the list item
Move up or down the drop-down list.
Up arrow or down arrow
Table 55. Keyboard shortcuts for lists Action
Keyboard shortcut
Navigate forward out of the list.
Tab
Navigate backward out of the list.
Shift+Tab
Activate the selected list item.
Enter
Navigate within the list.
Up arrow or down arrow
Navigate to the beginning or end of the list.
Ctrl+Home or Ctrl+End
Select all list items.
Ctrl+A
Select a single list item
Space bar Note: Using the space bar clears the previous selection.
Select an additional list item.
Ctrl+Space bar
Select a range of list items.
Shift+Space bar
Extend the selection up or down one item.
Shift+Up arrow or Shift+Down arrow
Extend the selection to the top or bottom of the list.
Shift+Home or Shift+End
Extend the selection up or down one block.
Shift+PgUp or Shift+PgDn
Navigate up or down a block.
PgUp or PgDn
Table 56. Keyboard shortcuts for sliders
152
Action
Keyboard shortcut
Navigate forward out of the slider.
Tab
Navigate backward out of the slider.
Shift+Tab
Increase the value
Up arrow or right arrow.
IBM Director Express Planning, Installation and Configuration Guide
Table 56. Keyboard shortcuts for sliders (continued) Action
Keyboard shortcut
Decrease the value
Down arrow or left arrow.
Set the maximum value.
Home
Set the minimum value.
End
Increase the value by a set range.
PgUp
Decrease the value by a set range.
PgDn
Table 57. Keyboard shortcuts for tables Action
Keyboard shortcut
Navigate forward out of the table.
Ctrl+Tab
Navigate backward out of the table.
Ctrl+Shift+Tab
Navigate to the next cell.
Tab or right arrow
Navigate to the previous cell.
Shift+Tab or left arrow
Navigate to the next row from the last column.
Tab or right arrow
Navigate to the previous row from the first column.
Shift+Tab or left arrow
Navigate vertically to the next or previous block.
PgUp or PgDn
Navigate horizontally to the left or right one block.
Ctrl+PgUp or Ctrl+PgDn
Navigate to the first or last cell in the row.
Home or End
Navigate to the first or last cell in the table.
Ctrl+Home or Ctrl+End
Select all cells in the table.
Ctrl+A
Clear the current selection.
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
Extend the selection up or down one row.
Shift+Up arrow or Shift+Down arrow
Extend the selection to the right or left one column.
Shift+Left arrow or Shift+Right arrow
Extend the selection to the beginning or end of the row.
Shift+Home or Shift+End
Extend the selection up or down one block.
Shift+PgUp or Shift+PgDn
Extend the selection left or right one block.
Ctrl+Shift+PgUp or Ctrl+Shift+PgDn
Appendix A. Accessibility features for IBM Director
153
Table 57. Keyboard shortcuts for tables (continued) Action
Keyboard shortcut
Extend the selection to the beginning or end of the column.
Ctrl+Shift+Home or Ctrl+Shift+End
Edit the cell without overriding the existing text.
F2
Delete the cell text before editing.
Esc
Table 58. Additional keyboard shortcuts for tables in Update Manager Action
Keyboard shortcut
Edit the sort order.
Ctrl+W
Sort the table by the selected column in ascending order.
Ctrl+S
Sort the table by the selected column in descending order.
Ctrl+Shift+S
Clear the sort.
Ctrl+T
Clear all sorts.
Ctrl+Q
Show the filter row.
Ctrl+R
Hide the filter row.
Ctrl+Shift+R
Edit the filter.
Ctrl+E
Apply the filter.
Ctrl+Shift+U
Deactivate the filter.
Ctrl+U
Clear all filters.
Ctrl+K
Display the find toolbar.
Ctrl+F
Hide the find toolbar.
Ctrl+Shift+F
Display the status line.
Ctrl+L
Hide the status line.
Ctrl+Shift+L
Table 59. Keyboard shortcuts for trees
154
Action
Keyboard shortcut
Navigate forward out of the tree.
Tab
Navigate backward out of the tree.
Shift+Tab
Expand the entry
Right arrow or Enter (if collapsed).
Collapse the entry
Left arrow or Enter (if expanded).
Navigate up or down one entry.
Up arrow or down arrow
Navigate to the first entry in the tree.
Home
Navigate to the last visible entry in the tree.
End
Navigate vertically up or down one block.
PgUp or PgDn
Navigate to the left or right one block.
Ctrl+PgUp or Ctrl+PgDn
Select all entries.
Ctrl+A or Ctrl+Slash
Clear the selection.
Ctrl+\
Select a single entry.
Ctrl+Space bar
Select a range of entries.
Shift+Space bar
IBM Director Express Planning, Installation and Configuration Guide
Table 59. Keyboard shortcuts for trees (continued) Action
Keyboard shortcut
Extend the selection up or down one block.
Shift+PgUp or Shift+PgDn
Extend the selection to the top of the tree.
Shift+Home
Extend the selection to the bottom of the tree.
Shift+End
Table 60. Keyboard shortcuts for text fields Action
Keyboard shortcut
Navigate into the text field
Alt+Character accelerator key (if defined).
Navigate forward out of the text field.
Tab
Navigate backward out of the text field.
Shift+Tab
Navigate to the previous or next character.
Left arrow or right arrow
Navigate to the previous or next word.
Ctrl+Left arrow or Ctrl+Right arrow
Navigate to the beginning or end of a field.
Home or End
Submit an entry.
Enter
Select all text in the field.
Ctrl+A
Clear the selection.
Arrow keys
Extend the selection to the left or right one character.
Shift+Left arrow or Shift+Right arrow
Extend the selection to the beginning or end of the field.
Shift+Home or Shift+End
Extend the selection to the next or previous word.
Ctrl+Shift+Left arrow or Ctrl+Shift+Right arrow
Copy the selected text.
Ctrl+C
Cut the selected text.
Ctrl+X
Paste from the clipboard.
Ctrl+V
Delete the previous or next character
Backspace or Delete
Table 61. Keyboard shortcuts for text panes Action
Keyboard shortcut
Navigate into the text pane.
Tab or Alt+Character accelerator key (if defined).
Navigate forward out of the text pane.
Ctrl+Tab
Navigate backward out of the text pane.
Ctrl+Shift+Tab
Navigate vertically up or down one block.
PgUp or PgDn
Navigate up or down one line.
Up arrow or down arrow
Navigate to the left or right one component or character.
Left arrow or right arrow
Appendix A. Accessibility features for IBM Director
155
Table 61. Keyboard shortcuts for text panes (continued) Action
Keyboard shortcut
Navigate to the beginning or end of a line.
Home or End
Navigate to the previous or next word.
Ctrl+Left arrow or Ctrl+Right arrow
Navigate to the beginning or end of the text pane.
Ctrl+Home or Ctrl+End
Navigate up or down one block.
PgUp or PgDn
Navigate to the left or right one block.
Ctrl+PgUp or Ctrl+PgDn
Navigate to the next or previous HTML link or other element which can receive the focus.
Ctrl+T or Ctrl+Shift+T
Navigate out of a focusable element that accepts a tab.
Ctrl+Tab or Ctrl+Shift+Tab
Activate a hyperlink.
Ctrl+Space bar
Extend the selection up or down one block.
Shift+PgUp or Shift+PgDn
Extend the selection to the left or right one block.
Ctrl+Shift+PgUp or Ctrl+Shift+PgDn
Extend the selection up or down one line.
Shift+Up arrow or Shift+Down arrow
Extend the selection to the left or right.
Shift+Left arrow or Shift+Right arrow
Extend the selection to the beginning or end of the line.
Shift+Home or Shift+End
Extend the selection to the beginning or end of the text pane.
Ctrl+Shift+Home or Ctrl+Shift+End
Extend the selection to the previous or next word.
Ctrl+Shift+Left arrow or Ctrl+Shift+Right arrow
Extend the selection vertically up or down one block.
Shift+PgUp or Shift+PgDn
Extend the selection to the left or right one block.
Ctrl+Shift+PgUp or Ctrl+Shift+PgDn
Select all text in the text pane.
Ctrl+A
Clear the selection.
Arrow keys
Copy the selected text.
Ctrl+C
Cut the selected text.
Ctrl+X
Paste from the clipboard.
Ctrl+V
Delete the previous or next component or character.
Backspace or Delete
Insert a line break.
Enter
Insert a tab.
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.
156
IBM Director Express Planning, Installation and Configuration Guide
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.
Appendix A. Accessibility features for IBM Director
157
158
IBM Director Express Planning, Installation and Configuration Guide
Appendix B. 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 62. Default LDAP authentication properties for IBM Director Server Property name
Description
ldap.auth.jndi
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.
ldap.auth.mechanism
Specifies the LDAP authentication mechanism to use: simple anonymous DIGEST-MD5
ldap.auth.userid.attribute
Specifies the name of the attribute on the LDAP server that specifies the user ID. This attribute is often named uid.
ldap.dn
Specifies the distinguished name of the LDAP server instance.
© Copyright IBM Corp. 1999, 2006
159
Table 62. Default LDAP authentication properties for IBM Director Server (continued) Property name
Description
ldap.enabled
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
Specifies the authorization mechanism to use when accessing the group information. The default mechanism is anonymous.
ldap.group.desc.attribute
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.
ldap.group.pwd
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.
ldap.host
Specifies the LDAP server address.
ldap.port
Specifies the port number to be used for LDAP authentication requests. By default, this is set to port 389.
ldap.search.scope
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.
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
160
IBM Director Express Planning, Installation and Configuration Guide
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 B. Lightweight Directory Access Protocol authentication properties for IBM Director Server
161
162
IBM Director Express Planning, Installation and Configuration Guide
Appendix C. 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 about the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not 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.
© Copyright IBM Corp. 1999, 2006
163
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. 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 document 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. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information softcopy, the photographs and color illustrations may not appear.
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
164
IBM Director Express Planning, Installation and Configuration Guide
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 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. Appendix C. Notices
165
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.
166
IBM Director Express Planning, Installation and Configuration Guide
Glossary contained an ASM processor. When an ASM PCI adapter is used with an ASM processor, the ASM PCI adapter acts as an Ethernet gateway, while the ASM processor retains control of the server. When used as a gateway service processor, the ASM PCI adapter can communicate with other ASM PCI adapters and ASM processors only.
Glossary This glossary includes terms and definitions for IBM Director. To view glossaries for other IBM products, go to www.ibm.com/ibm/terminology .
A accelerator In a user interface, a key or combination of keys that invokes an application-defined function. Advanced Encryption Standard (AES) A data encryption technique that improved upon and officially replaced the Data Encryption Standard (DES). AES is sometimes referred to as Rijndael, which is the algorithm on which the standard is based.
Advanced System Management processor (ASM processor) A service processor built into the mid-range Netfinity and early xSeries servers. IBM Director can connect out-of-band to an ASM processor located on an ASM interconnect; an ASM PCI adapter, a Remote Supervisor Adapter, or a Remote Supervisor II must serve as the gateway service processor. AES
See Advanced Encryption Standard.
Advanced System Management interconnect (ASM interconnect) A feature of IBM service processors that enables users to connect up to 24 servers to one service processor, thus eliminating the need for multiple modems, telephones, and LAN ports. It provides such out-of-band management functions as system power control, service-processor event-log management, firmware updates, alert notification, and user profile configuration.
alert
A message or other indication that signals an event or an impending event.
Advanced System Management interconnect network (ASM interconnect network) A network of IBM servers created by using the ASM interconnect feature. The servers are connected through RS-485 ports. When servers containing integrated system management processors (ISMPs) and ASM processors are connected to an ASM interconnect network, IBM Director can manage them out-of-band.
alert standard format (ASF) A specification created by the Distributed Management Task Force (DMTF) that defines remote-control and alerting interfaces that can best serve a client system in an environment that does not have an operating system.
Advanced System Management PCI adapter (ASM PCI adapter) An IBM service processor that is built into the Netfinity 7000 M10 and 8500R servers. It also was available as an option that could be installed in a server that © Copyright IBM Corp. 1999, 2006
alert forwarding A function that ensures that alerts are sent, even if a managed system experiences a catastrophic failure, such as an operating-system failure. alert-forwarding profile A profile that specifies where remote alerts for the service processor should be sent.
anonymous command execution Execution of commands on a target system as either system account (for managed systems running Windows) or root (for managed systems running Linux). ASF
See alert standard format.
167
ASM interconnect See Advanced System Management interconnect.
bottleneck A place in the system where contention for a resource is affecting performance.
ASM interconnect gateway See gateway service processor.
C
ASM interconnect network See Advanced System Management interconnect network. ASM PCI adapter See Advanced System Management PCI adapter. ASM processor See Advanced System Management processor. association A visual representation of the members in a group that shows relationships or provides additional information about the members of a group. Auto-Logical Drive Transfer See auto volume transfer/auto disk transfer.
chassis The metal frame in which various electronic components are mounted. chassis detect-and-deploy profile A profile that IBM Director automatically applies to all new BladeCenter chassis when they are discovered. The profile settings include management module name, network protocols, and static IP addresses. If Remote Deployment Manager (RDM) is installed on the management server, the chassis detect-and-deploy profile also can include deployment policies. CIM cloning In z/VM, a copying technique that preserves the characteristics of the original but personalizes instance-specific data. The result of a cloning operation is new instance of an entity (for example, of a virtual disk, a virtual computer system, or an operating system) rather than a backup of the original.
auto volume transfer/auto disk transfer (AVT/ADT) A function that provides automatic failover in case of controller failure on a storage subsystem. AVT/ADT See auto volume transfer/auto disk transfer.
cluster A collection of complete systems that work together to provide a single, unified computing capability.
B Basic Input/Output System (BIOS) The code that controls basic hardware operations, such as interactions with diskette drives, hard disk drives, and the keyboard. BIOS
See Basic Input/Output System.
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. blade server A high-throughput, two-way, Intel Xeon-based server on a card that supports symmetric multiprocessors (SMPs).
168
See Common Information Model.
CMS
See Conversational Monitor System.
Common Information Model (CIM) An implementation-neutral, object-oriented schema for describing network management information. The Distributed Management Task Force (DMTF) develops and maintains CIM specifications. component association In the IBM Director Rack Manager task, a function that can make a managed system or device rack-mountable when the inventory collection feature of IBM Director does not recognize the managed system or device. The function associates the system or device with a predefined component.
IBM Director Express Planning, Installation and Configuration Guide
Conversational Monitor System (CMS) A virtual-machine operating system that provides general interactive time sharing, problem solving, and program development capabilities.
D
disk pool In z/VM Center, a logical grouping of contiguous disk spaces. A disk pool can include disk spaces from multiple physical disks. A disk pool corresponds to a z/VM Directory Maintenance Facility allocation group.
database server The server on which the database application and database are installed.
DMI
See Desktop Management Interface.
DSA
See digital signature algorithm.
Data Encryption Standard (DES) A cryptographic algorithm designed to encrypt and decrypt data using a private key.
E
deployment policy A policy that associates a specific bay in a BladeCenter chassis with a Remote Deployment Manager (RDM) noninteractive task. When a blade server is added to or replaced in the bay, IBM Director automatically runs the RDM task. DES
See Data Encryption Standard.
Desktop Management Interface (DMI) A protocol-independent set of application programming interfaces (APIs) that were defined by the Distributed Management Task Force (DMTF). These interfaces give management application programs standardized access to information about hardware and software in a system. Diffie-Hellman key exchange A public, key-exchange algorithm that is used for securely establishing a shared secret over an insecure channel. digital signature algorithm (DSA) A security protocol that uses a pair of keys (one public and one private) and a one-way encryption algorithm to provide a robust way of authenticating users and systems. If a public key can successfully decrypt a digital signature, a user can be sure that the signature was encrypted using the private key. directory manager A facility for maintaining the user directory of one or more z/VM systems. discovery The process of finding resources within an enterprise, including finding the new location of monitored resources that were moved.
enclosure A unit that houses the components of a storage subsystem, such as a control unit, disk drives, and power source. event
An occurrence of significance to a task or system. Events can include completion or failure of an operation, a user action, or the change in state of a process.
event action The action that IBM Director takes in response to a specific event or events. event-action plan A user-defined plan that determines how IBM Director will manage certain events. An event action plan comprises one or more event filters and one or more customized event actions. event-data substitution variable A variable that can be used to customize event-specific text messages for certain event actions. event filter A filter that specifies the event criteria for an event action plan. Events must meet the criteria specified in the event filter in order to be processed by the event action plan to which the filter is assigned.
F fabric A complex network using hubs, switches, and gateways. Fibre channel uses a fabric to connect devices. field-replaceable unit (FRU) An assembly that is replaced in its entirety when any one of its components fails. file-distribution server In the Software Distribution task, an intermediate server that is used to Glossary
169
distribute a software package when the redirected-distribution method is used. forecast A function that can provide a prediction of future performance of a managed system using past data collected on that managed system. FRU
See field-replaceable unit.
G gateway service processor A service processor that relays alerts from service processors on an Advanced System Management (ASM) interconnect network to IBM Director Server. group A logical set of managed objects. Groups can be dynamic, static, or task-based. Guest LAN A virtual local area network (LAN) segment that is emulated by the z/VM Control Program (CP). A Guest LAN can be shared by guest virtual machines on the same z/VM system. guest virtual machine In z/VM, the functional equivalent of a System z9 or zSeries system, including the virtual processors, virtual storage, virtual devices, and virtual channel subsystem allocated to a single user. Each guest virtual machine can be controlled by an operating system, such as CMS, z/VSE, z/OS, or Linux.
H host object A logical object that groups one or more worldwide port names (WWPNs) of the host bus adapters (HBAs) that the cluster has detected on the storage area network (SAN). HT
See Hyper-Threading.
Hyper-Threading (HT) A technology with which a single processor can function as two virtual processors and execute two threads simultaneously. hypervisor A program or a portion of Licensed Internal Code (LIC) that allows multiple instances of operating systems to run simultaneously on the same hardware.
170
I IBM Director Agent A component of IBM Director software. When IBM Director Agent is installed on a system, the system can be managed by IBM Director. IBM Director Agent transfers data to the management server using several network protocols, including TCP/IP, NetBIOS, and IPX. IBM Director Console A component of IBM Director software. When installed on a system, it provides a graphical user interface (GUI) for accessing IBM Director Server. IBM Director Console transfers data to and from the management server using TCP/IP. IBM Director Core Services A facility with which IBM Director communicates with and administers a level-2 managed system. IBM Director Core Services includes the service location protocol (SLP) instrumentation, the IBM Director Agent SLP service type, and Common Information Model (CIM). IBM Director database The database that contains the data stored by IBM Director Server. IBM Director environment The complex, heterogeneous environment managed by IBM Director. It includes systems, BladeCenter chassis, software, and SNMP devices. IBM Director extension A tool that extends the functionality of IBM Director. Some of the IBM Director extensions are Capacity Manager, ServeRAID Manager, Remote Deployment Manager, and Software Distribution. IBM Director Server The main component of IBM Director software. When installed on the management server, it provides basic functions such as discovery of the managed systems, persistent storage of configuration and management data, an inventory database, event listening, security and authentication, management console support, and administrative tasks. IBM Director Server service A service that runs automatically on the
IBM Director Express Planning, Installation and Configuration Guide
management server, and provides the server engine and application logic for IBM Director. IBM Director service account The Windows operating-system account associated with the IBM Director Server service. in-band communication initial program load (IPL) The process that loads the system programs from the system auxiliary storage, checks the system hardware, and prepares the system for user operations. instance An individual realization of the operating system with a particular version, configuration, physical location, and identifier. In object-oriented programming, an object of a particular class. integrated system management processor (ISMP) A service processor built into some xSeries servers. ISMP is the successor to the Advanced System Management (ASM) processor. interprocess communication (IPC) A mechanism of an operating system that allows processes to communicate with each other within the same computer or over a network. inventory-software dictionary A file that tracks the software installed on managed systems in a network. IPC
See interprocess communication.
IPL
See initial program load.
ISMP See integrated system management processor.
J job
A separately executable unit of work.
K L Level-0 managed system An IBM or non-IBM server, desktop computer, workstation, or mobile computer, that can be managed by IBM
Director but does not have any IBM Director software installed on it. Level-1 managed system An IBM or non-IBM server, desktop computer, workstation, and mobile computer that has IBM Director Core Services installed. Level-2 managed system An IBM or non-IBM server, desktop computer, workstation, or mobile computer that has IBM Director Agent installed. The function of a Level-2 managed system varies depending on the operating system and hardware. light path diagnostics A technology that provides a lighted path to failed or failing components to expedite hardware repairs. logical unit number (LUN) In the Small Computer System Interface (SCSI) standard, a unique identifier used to differentiate devices, each of which is a logical unit (LU). LUN
See logical unit number.
M MAC address See Media Access Control address. managed group A group of systems or objects managed by IBM Director. managed object A resource that is subject to management--such as a connection, a scalable system, or a line--as viewed from a systems management perspective. managed object ID A unique identifier for each managed object. managed system A system that is being controlled by a given system management application. management console A system (server, desktop computer, workstation, or mobile computer) on which IBM Director Console is installed. management module The BladeCenter component that handles system-management functions. It configures the chassis and switch Glossary
171
modules, communicates with the blade servers and all I/O modules, multiplexes the keyboard/video/mouse (KVM), and monitors critical information about the chassis and blade servers.
connection, for example, service processor alerts sent through a modem or over a LAN.
P See Peripheral Component Interconnect. See also Peripheral Component Interconnect-X.
management server The server on which IBM Director Server is installed.
PCI
master system In z/VM Center, an operating system instance that has been set up to serve Virtual Server Deployment as a model for creating operating system templates.
PCI-X See Peripheral Component Interconnect-X. See also Peripheral Component Interconnect.
Media Access Control address (MAC address) In a local area network, the protocol that determines which device has access to the transmission medium at a given time. minidisk A direct access storage device (DASD) or a logical subdivision of a DASD that has its own virtual device number.
N node port (N_port) A port that connects a node to a fabric or to another node. An N_port connects to a fabric port (F_port) or to the N_port of another node. An N_port handles creation, detection, and flow of message units to and from the connected systems. N_ports are end points in point-to-point links. nonvolatile random access memory (NVRAM) Random access memory (storage) that retains its contents after the electrical power to the machine is shut off. N_port See node port. NVRAM See nonvolatile random access memory.
Peripheral Component Interconnect (PCI) A local bus that provides a high-speed data path between the processor and attached devices. See also Peripheral Component Interconnect-X. Peripheral Component Interconnect-X (PCI-X) An enhancement to the Peripheral Component Interconnect (PCI) architecture. PCI-X enhances the Peripheral Component Interconnect (PCI) standard by doubling the throughput capability and providing additional adapter-performance options while maintaining backward compatibility with PCI adapters. See also Peripheral Component Interconnect. persistent Pertaining to data that is maintained across session boundaries, usually in nonvolatile storage such as a database system or a directory. PFA
physical platform An IBM Director managed object that represents a single physical chassis or server that has been discovered through the use of the Service Location Protocol (SLP). plug-in A software module that adds function to an existing program or application.
O operating system template A set of installation and configuration data that z/VM Center uses as a source for creating operating system instances. Operating system templates are created from master systems. out-of-band communication Communication that occurs through a modem or other asynchronous
172
See Predictive Failure Analysis.
POST See power-on self-test. power-on self-test (POST) A series of internal diagnostic tests activated each time the system power is turned on. Predictive Failure Analysis (PFA) A scheduled evaluation of system data
IBM Director Express Planning, Installation and Configuration Guide
that detects and signals parametric degradation which might lead to functional failures.
resource-monitor threshold The point at which a resource monitor generates an event.
private key In secure communication, an algorithmic pattern used to encrypt messages that only the corresponding public key can decrypt. The private key is also used to decrypt messages that were encrypted by the corresponding public key. The private key is kept on the user’s system and is protected by a password. See also public key.
RXE Expansion Port The dedicated high-speed port used to connect a remote I/O expansion unit, such as the RXE-100 Remote Expansion Enclosure, to a server.
programming interface for customers The supported method through which customer programs request software services. The programming interface consists of a set of callable services provided with a product. public key In secure communication, an algorithmic pattern used to decrypt messages that were encrypted by the corresponding private key. A public key is also used to encrypt messages that can be decrypted only by the corresponding private key. Users broadcast their public keys to everyone with whom they must exchange encrypted messages. See also private key.
Q R redirected distribution A method of software distribution that uses a file-distribution server. remote I/O enclosure An IBM Director managed object that represents an expansion enclosure of Peripheral Component Interconnect-X (PCI-X) slots, for example, an RXE-100 Remote Expansion Enclosure. The enclosure consists of one or two expansion kits. Remote Supervisor Adapter An IBM service processor. It is built into some xSeries servers and available as an optional adapter for use with others. When used as a gateway service processor, the Remote Supervisor Adapter can communicate with all service processors on the Advanced System Management (ASM) interconnect.
S scalable node A physical platform that has at least one SMP Expansion Module. Additional attributes are assigned to a physical platform when it is a scalable node. These additional attributes record the number of SMP Expansion Modules, SMP Expansion Ports, and RXE Expansion ports on the physical chassis. scalable object An IBM Director managed object that is used with Scalable Systems Manager. Scalable objects include scalable nodes, scalable systems, scalable partitions, and remote I/O enclosures that are attached to scalable nodes. scalable partition An IBM Director managed object that defines the scalable nodes that can run a single image of the operating system. A scalable partition has a single, continuous memory space and access to all associated adapters. A scalable partition is the logical equivalent of a physical platform. Scalable partitions are associated with scalable systems and comprise only the scalable nodes from their associated scalable systems. scalable system An IBM Director managed object that consists of scalable nodes and the scalable partitions that are composed of the scalable nodes in the scalable system. When a scalable system contains two or more scalable nodes, the servers that they represent must be interconnected through their SMP Expansion Modules to make a multinode configuration, for example, a 16-way xSeries 455 server made from four scalable nodes. Secure Sockets Layer (SSL) A security protocol that provides communication privacy. With SSL, Glossary
173
client/server applications can communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery. server complex In z/VM Center, a configuration profile for Linux guest systems that includes both Linux and z/VM aspects. A server complex can define network settings, Linux configuration scripts, disk access, and VM Resource Manager (VMRM) performance goals. Service Location Protocol (SLP) An Internet protocol that identifies and uses network hosts without having to designate a specific network host name. service machine In z/VM, a guest virtual machine that provides a system service such as accounting, error recording, or monitoring. A system service can be part of z/VM or a licensed program. service processor A generic term for Remote Supervisor Adapters, Advanced System Management processors, Advanced System Management PCI adapters, and integrated system management processors (ISMPs). These hardware-based management processors used in IBM Netfinity and xSeries servers work with IBM Director to provide hardware status and alert notification. SLP
See Service Location Protocol.
SMBIOS See system management BIOS. SMP Expansion Module An IBM xSeries hardware option. It is a single module that contains microprocessors, disk cache, random access memory, and three SMP Expansion Port connections. Two SMP Expansion Modules can fit in a chassis. SNMP Access and Trap Forwarding An IBM Director Agent feature that enables SNMP to access managed-system data. When installed on a managed system, this feature enables SNMP-based managers to poll the managed system and receive its alerts. If System Health Monitoring is installed on the managed
174
system also, hardware alerts can be forwarded as SNMP traps. SNMP device An embedded device that uses SNMP to monitor network-attached devices, printers, or computers for conditions that require system-management attention. SQL
See Structured Query Language.
SSL
See Secure Sockets Layer.
static partition A view-only scalable partition. sticky key An input method that enables the user to press and release a series of keys sequentially (for example, Ctrl+Alt+Del), yet have the keys behave as if they were pressed and released at the same time. This method can be used for those who require special-needs settings to make the keyboard easier to use. storage subsystem A storage control and its attached storage devices. Structured Query Language (SQL) A standardized language for defining and manipulating data in a relational database. switch module The BladeCenter component that provides network connectivity for the BladeCenter chassis and blade servers. It also provides interconnectivity between the management module and blade servers. System Health Monitoring An IBM Director Agent feature that provides active monitoring of critical system functions, including system temperatures, voltages, and fan speeds. It also handles in-band alert notification for managed systems running Windows and some managed systems running Linux. system management BIOS (SMBIOS) A specification that extends BIOS to support the retrieval of management data. system variable A user-defined keyword and value pair that can be used to test and track the status of network resources. System variables can be referred to wherever event-data substitution is allowed.
IBM Director Express Planning, Installation and Configuration Guide
T
Agent from within the higher-level systems-management console, as well as collect IBM Director inventory data and view IBM Director alerts.
target system A managed system on which an IBM Director task is performed. time to live A technique used by best-effort delivery protocols to inhibit endlessly looping packets. The packet is discarded if the TTL counter reaches 0. triple Data Encryption Standard (triple DES) 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. triple DES See triple Data Encryption Standard. truststore In security, a storage object, either a file or a hardware cryptographic card, where public keys are stored in the form of trusted certificates, for authentication purposes in Web transactions. In some applications, these trusted certificates are moved into the application keystore to reside with the private keys.
U Universally Unique Identifier The 128-bit numerical identifier that is used to ensure that two components do not have the same identifier. Universal Unique Identifier (UUID) See Universally Unique Identifier. upward integration The methods, processes and procedures that enable lower-level systems-management software, such as IBM Director Agent, to work with higher-level systems-management software, such as Tivoli Enterprise or Microsoft SMS. upward integration module Software that enables higher-level systems-management software, such as Tivoli Enterprise or Microsoft Systems Manager Server (SMS), to interpret and display data provided by IBM Director Agent. This module also can provide enhancements that start IBM Director
user class A z/VM privilege category assigned to a user of a guest virtual machine in the user’s directory entry; each class specified allows access to a logical subset of all the z/VM Control Program (CP) commands. UUID See Universal Unique Identifier.
V virtual device number In z/VM, a device number used by a guest virtual machine. Real devices can be referred to by different virtual device numbers by different guest virtual machines. virtual server template A set of definitions that provides configuration defaults for z/VM virtual servers. z/VM Center uses virtual server templates to create z/VM virtual servers. vital product data (VPD) Information that uniquely defines system, hardware, software, and microcode elements of a processing system. VPD
See vital product data.
W Wake on LAN A technology that enables a user to remotely turn on systems for off-hours maintenance. A result of the Intel-IBM Advanced Manageability Alliance and part of the Wired for Management Baseline Specification, users of this technology can remotely turn on a server and control it across the network, thus saving time on automated software installations, upgrades, disk backups, and virus scans. walk
An SNMP operation that is used to discover all object instances of management information implemented in the SNMP agent that can be accessed by the SNMP manager.
Windows Management Instrumentation (WMI) An application programming interface (API) in the Windows operating system Glossary
175
that enables devices and systems in a network to be configured and managed. WMI uses the Common Information Model (CIM) to enable network administrators to access and share management information. WMI
See Windows Management Instrumentation.
WMI Query Language (WQL) A subset of the Structured Query Language (SQL) with minor semantic changes to support Windows Management Instrumentation (WMI). WQL
See WMI Query Language.
X Y Z z/VM
A System z9 and zSeries operating system that acts as virtualization software. z/VM can virtualize all system resources, including processors, memory, storage devices, and communication devices. z/VM supports the concurrent operation of hundreds of operating system instances.
z/VM virtual server In z/VM, a guest virtual machine that a user can log on to.
Symbols and Numerics
176
IBM Director Express Planning, Installation and Configuration Guide
Index A accessibility 147 features 147 keyboard 147 shortcut keys 147 Advanced System Management 42 AIX installing IBM Director Agent 89 IBM Director Console 67 AIX installation Express IBM Director Server 55 alerts definition 32 Apache Derby 28 ASF 22 generating events 32 ASM 42 Asset ID operating systems, supported 18
B baseboard management controller 24 Baseboard Management Controller 42 blade servers total BladeCenter units 26 BladeCenter chassis assigning IP addresses manually 118 DHCP server, using 118 discovering (automatically) 118 IP address conflicts 118 deployment infrastructure DHCP server, using 118 IP address conflicts 118 documentation v network devices 26 products, supported tasks 26 BladeCenter Configuration Manager operating systems, supported 20 BladeCenter HS20, machine type 8843 44 BladeCenter(TM) HS20, machine type 8832 44 BMC 24, 42 books v Brocade switches 28
C Capacity Manager management server, installing on 57 chassis (BladeCenter) DHCP server, using 118 discovering (automatically) 118 IP address conflicts 118 manually assigning IP addresses 118 © Copyright IBM Corp. 1999, 2006
chassis managed objects displayed in IBM Director Console (screenshot) 118 CIM Browser operating systems, supported 18 compatibility documents v Compatibility Documents 13 concepts 1 Configuration Manager 26 Configure SNMP Agent operating systems, supported 18 customer support v
D dacimlist startup script 140 dasnmp startup script 140 database function of 5 databases Apache Derby 28 for management servers 28 IBM Cloudscape 28 IBM DB2 28 Microsoft Data Engine 28 Microsoft SQL Server 28 MS Jet 28 MSDE 28 Oracle Server 28 PostgreSQL 28 supported 28 deployment infrastructure (BladeCenter) DHCP server, using 118 IP address conflicts 118 design strategies, event action plan 34 DHCP server 118 diragent.rsp 89 diragent.rsp file upgrading IBM Director Agent using Software Distribution 85, 108 dircon.rsp file customizing 74 location 74 dirinstall script IBM Director Agent 78, 94 IBM Director Console 70 IBM Director Server 55 diruns utility 145 disability 147 discovery BladeCenter chassis 118 documentation v domain controller 31 downloading v compatibility documents v hardware compatibility information v IBM Director code v IBM Director publications v Net-SNMP, version 5.2.1 140 systems-management software v
DS300 28 DS400 28 DS4000 28 DS6000 28
E encryption enabling on managed system AIX 89 i5/OS 91 Linux 92, 95, 97 Windows 100 enabling on management server Windows 57 environment ports used 11 environment (illustration) 1 event availability 36 definition 32 how they work 32 management 35 overview 32 publishing 36 sources that generate 32 types alert 32 availability 36 resolution 32 event action plans 35 design strategies 34 example 36 grouping systems 35 how events work 32 naming conventions 35 overview 35 planning and designing 34 structuring 36 successful implementation 35 wizard 35 event filters structuring 36 Event Log operating systems, supported 18 examples event action plan 36 Express installation AIX IBM Director Server 55 IBM Director Server 57 Linux 61 Linux for System z 63 Linux on POWER 59 extensions publishing events 36 External Application Launch management server support 20 operating systems, supported 18, 20 External Application Launch wizard operating systems, supported 18
177
F features, accessibility 147 File Transfer operating systems, supported file-distribution server configuring 138 setting up 137 firewall access configuring 11
18
G glossary 167 grouping managed systems
35
H hardware requirements 7 hardware compatibility v hardware requirements 7, 8, 9 Hardware Status management server support 20 operating systems, supported 18, 20 help, IBM Director resources v
I i5/os installing, IBM Director Console 67 i5/OS 91 installing IBM Director Server 39 i5/OS installation encryption, enabling 91 IBM Director Agent, installing 91 starting 91 IBM Cloudscape 28 IBM DB2 28 IBM Director components of 1 concepts 1 getting started 1 IBM Director Console 1 overview 1 scenarios 1 IBM Director Agent AIX 89 AIX, installing on encryption, enabling 89 BladeCenter chassis 26 server 26 encryption, enabling AIX 89 i5/OS 91 Linux 78, 92, 95, 97 Windows 100 function 4 generating events 32 hardware requirements 7, 8, 9 IBM Director tasks 26 installing using Software Distribution 107
178
IBM Director Agent (continued) installing on AIX 89 license 4 Linux, installing on dirinstall script 78, 92, 94, 95, 97 Net-SMNP, enabling 78, 92, 94, 95, 97 Wake on LAN, enabling 92, 95, 97 NetWare, installing on features, selecting 98 network driver, configuring 98 network protocols 10 operating systems, supported 14 uninstalling Windows 145 Windows, installing on encryption, enabling 100 features, selecting 100, 104 InstallShield wizard, using 100 network driver, configuring 100, 104 securing managed system 100 security state, setting 100 software-distribution settings 100 Wake on LAN, enabling 100, 104 IBM Director Console 73 authorizing users 112 features, selecting 73 function 5 hardware requirements 7, 8 installing 67 installing on AIX 67 Linux 69 Linux for POWER 71 installing on Linux 70 installing on Windows dircon.rsp file 74 InstallShield wizard, using 73 unattended mode, using 74 license 5 network protocols 10 operating systems, supported 14 overview 1 uninstalling Windows 145 IBM Director Console installation 73 IBM Director Core Service installing on Linux for POWER 79 Windows 81 IBM Director Core Services function 3 installing 49 license 3 IBM Director Hardware and Software Compatibility document v IBM Director Server AIX, installing on 55 encryption, enabling Windows 57 function 5 hardware requirements 7, 8, 9 i5/OS installing 39
IBM Director Express Planning, Installation and Configuration Guide
IBM Director Server (continued) installing Linux for System x 41 System p 40 license 5 network protocols 10 operating systems, supported 14 preparing, for installation 40, 41 uninstalling Windows 145 where to install 31 Windows, installing on database configuration 57 encryption settings 57 features, selecting 57 network driver, configuring 57 service account 57 Software Distribution settings 57 Wake on LAN, enabling 57 IBM eServer Information Center v IBM systems-management software downloading v overview v IBM Web sites eServer Information Center v Redbooks v ServerProven v Support v Systems Management Software v xSeries Systems Management v illustrations IBM Director environment 1 IBM Director software components 2 installing IBM Director Agent using, Software Distribution 107 IBM Director Console AIX 67 Linux for POWER 71 Linux for System x 69 overview 67 IBM Director Core Service Linux for POWER 79 Windows 81 IBM Director Server Linux 61 Linux for System z 63 Linux on POWER 59 InstallShield wizard IBM Director Agent 100 IBM Director Console 73 IBM Director Server 57 Integrated System Management Processor 42 Intel Itanium IBM Director Agent installing 97 Intelligent Platform Management Interface 42 interim fixes v Inventory operating systems, supported 18 IP address conflicts, troubleshooting 118 IPMI 42 IPMI baseboard management controller generating events 32 ISMP 42
K keyboard 147
L legal notices 163 Level 1 managed system 3 Level-1 managed system preparing, for installation 49 Level-2 managed system 4 license IBM Director Agent 4 IBM Director Console 5 IBM Director Core Services 3 IBM Director Server 5 Linux for POWER installing IBM Director Console 71 IBM Director Core Service 79 Linux for System x installing IBM Director Console 69 Linux installation encryption, enabling 92, 95, 97 IBM Director Agent 78, 92, 94, 95 IBM Director Console 70 Intel Itanium IBM Director Agent 97 modifying SNMP Access and Trap Forwarding, enabling 140 starting 78, 92, 94, 95, 97 System p IBM Director Server 59 System x IBM Director Server 61 System z IBM Director Server 63
M managed system authorizing request access 113 request access authorizing 113 managed systems definition 1 distribution preferences, configuring 139 hardware requirements 7, 8, 9 preparing Windows XP 53 securing IBM Director Agent installation, during 100 management console 5 definition 2 hardware requirements 7, 8 management processor generating events 32 Management Processor Assistant Agent managed system, installing on 98, 100 NetWare, installing on 98
management server choosing 31 definition 1 hardware requirements 7, 8, 9 Microsoft Data Engine 28 Microsoft SQL Server 28 modifying an IBM Director installation Linux installation SNMP Access and Trap Forwarding, enabling 140 MS Jet 28 MSDE 28
N N3700 28 N5200 28 Net-SNMP, version 5.2.1 140 NetWare installation IBM Director Agent, installing 98 MPA Agent, when to install 98 Network Configuration operating systems, supported 18 network protocols 10 New Scheduled Job window 86, 109 notifications definition 32
O operating system compatibility v support for tasks supported 13 Oracle Server 28
17
P PET, generating events 32 planning and designing event action plans 34 ports 11 PostgreSQL 28 Power Management management server support 22 operating system support 22 operating systems 22 service processor 24 Wake on LAN 24 preparing Level-1 managed system 49 Linux for System x IBM Director Server, installation of 41 System p IBM Director Server, installation of 40 Process Management operating systems, supported 18 process monitors event 35 publications v
Q QLogic BladeCenter switches
28
R Rack Manager management console, installing on 73 management server, installing on 57 operating systems, supported 18 Red Hat Enterprise Linux AS, ES, and WS, version 3.0 49 Redbooks v related information v Remote Control operating systems, supported 18 Remote Control Agent managed system, installing on 100 management server, installing on 57 Remote Session operating systems, supported 18 Remote Supervisor Adapter 24, 42 documentation v request access authorizing, on a managed system 113 requirements 7 hardware 7 resolution definition 32 Resource Monitors events 35 operating systems, supported 18 response file dircon.rsp 67, 69, 71, 79, 81 modifying 67, 69, 71, 79, 81
S scenarios 1 Server Configuration Manager operating systems, supported 20 Server Storage Provisioning Tool operating systems, supported 25 ServeRAID Manager managed system, installing on 98, 104 Service Location Protocol 118 service packs v service processor 42 Power Management 24 service processors 22 documentation v generating events 32 shortcut keys 147 silent parameter 74, 82, 102, 106 SMBIOS 7 SNMP generating events 32 SNMP Access and Trap Forwarding enabling on Linux 140 SNMP devices definition 1 operating systems, supported 18 snmpconf utility 140 snmpd.conf file 140 Index
179
software components (illustration) 2 software distribution preferences, configuring 137 upgrading IBM Director Agent software package, installing 86, 109 Software Distribution operating systems, supported 18 Software Distribution task installing IBM Director Agent 107 software packages creating 85, 108 SQL database 28 starting programs with event action plans 35 Storage products, supported tasks 28 structure event action plan 36 event filters 36 System Accounts operating systems, supported 18 System i preparing, for installation 39
T tasks event action plans 35 management server support 17 operating systems, supported 17 publishing events 36 User Administration 112 terminology alert 32 event 32 managed system 1 management console 2 management server 1 notification 32 resolution 32 SNMP device 1 thresholds event action plans 35 toolbar User Administration 112 trademarks 164
U unattended installations IBM Director Console 74 unattended parameter 74, 82, 102, 106 uninstalling IBM Director Windows 145 Update Manager operating systems, supported 18 upgrading IBM Director Agent Windows 103 Software Distribution task, using 85, 108 user IDs operating system 112 profiles 112
180
User Administration task 112
V VMware authorizing, request access
113
W Wake on LAN 22 enabling on AIX 89 enabling on Windows IBM Director Agent, installing 100, 104 IBM Director Server, installing 57 Power Management 24 Web site IBM Director resources v IBM Redbooks v IBM ServerProven v IBM Support v IBM Systems Management Software v IBM xSeries Systems Management v Web sites Net-SNMP 140 windows IBM Director Console IBM Update Assistant 85, 108 Windows event log generating events 32 installing IBM Director Core Service 81 windows (IBM Director) IBM Director Agent installation (NetWare) Choose destination location 98 InstallShield Wizard complete 98 Select Components 98 IBM Director Agent installation (Windows) 100 Feature and destination directory selection 100 Network driver configuration 100 Security settings 100 Software Distribution settings 100 IBM Director Console Add Share Name 138, 139 IBM Update Assistant 85, 108 IBM Update Package/Root Directory 85, 108 Managed System Distribution Preferences 139 New Scheduled Job 86, 109 Server Preferences 138 Software Distribution Manager (Premium Edition) 85, 108 Software Distribution Manager (Standard Edition) 85, 108 Software Distribution Preferences 137 IBM Director Console installation Feature and destination directory selection 73
IBM Director Express Planning, Installation and Configuration Guide
windows (IBM Director) (continued) IBM Director Server installation 57 DB2 Universal Database configuration 57 Encryption settings 57 Feature and installation directory selection 57 IBM Director database configuration 57 Microsoft SQL database configuration 57 Network driver configuration 57 Oracle database configuration 57 service account information 57 Software-distribution settings 57 Windows installation encryption, enabling 57, 100 IBM Director Agent 99 IBM Director Console 72 IBM Director Server 57 uninstalling 145 Windows Management Instrumentation (WMI) generating events 32 Windows XP preparing managed system 53 Wired for Management (WfM) specifications 7 wizards Event Action Plan 35 InstallShield IBM Director Agent 100 IBM Director Console 73 IBM Director Server 57
X xSeries xSeries xSeries xSeries xSeries
225, 226, 236, 336, 346,
machine machine machine machine machine
type type type type type
8647 8836 8841 8837 8840
44 44 44 44 44
Readers’ Comments — We’d Like to Hear from You IBM Systems IBM Director Express Planning, Installation and Configuration Guide Version 5.20 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
Address
Company or Organization Phone No.
E-mail address
___________________________________________________________________________________________________
Readers’ Comments — We’d Like to Hear from You
Cut or Fold Along Line
_ _ _ _ _ _ _Fold _ _ _and _ _ _Tape _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please _ _ _ _ _do _ _not _ _ staple _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold _ _ _and _ _ Tape ______ 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 Dept. CGFA PO Box 12195 Research Triangle Park, NC 27709-9990
_________________________________________________________________________________________ Please do not staple Fold and Tape Fold and Tape
Cut or Fold Along Line
Printed in USA
IBM Director Express Planning, Installation and Configuration Guide Version 5.20
IBM Systems
IBM Director Express Planning, Installation and Configuration Guide Version 5.20
Note Before using this information and the product it supports, read the information in Appendix C, "Notices."
First Edition (December 2006) This edition applies to version 5.20 of Software Distribution Premium Edition extension 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, 2006. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents About this book . . . . . . . . . . . v Conventions and terminology . . . . . . . . v Related information . . . . . . . . . . . . v How to send your comments . . . . . . . . viii
Installing IBM Director Server on Linux for System z using the Express installation option Adding Standard installation options to an IBM Director Express installation . . . . . . . .
. 63 . 65
New in version 5.20 . . . . . . . . . ix
Chapter 5. Installing IBM Director Console . . . . . . . . . . . . . . 67
Chapter 1. Getting started with IBM Director . . . . . . . . . . . . . . . 1
Installing IBM Director Console on AIX . . . . Installing IBM Director Console on Linux for System x . . . . . . . . . . . . . . Installing IBM Director Console on Linux for System z . . . . . . . . . . . . . . Installing IBM Director Console on Linux for POWER . . . . . . . . . . . . . . Installing IBM Director Console on Windows . . Installing IBM Director Console using the InstallShield wizard . . . . . . . . . Performing an unattended installation of IBM Director Console on Windows . . . . . .
Introducing IBM Director . . IBM Director components . . IBM Director Core Services IBM Director Agent . . . IBM Director Console . . IBM Director Server . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
1 2 3 4 4 5
Chapter 2. Planning . . . . . . . . . . 7 Specified operating environments . . . . . . Hardware requirements for IBM Director . . . Network requirements . . . . . . . . . Supported operating systems . . . . . . Support of IBM Director tasks across operating systems . . . . . . . . . . . . . . IBM Director task support for BladeCenter products . . . . . . . . . . . . . IBM Director task support for Storage products Supported database applications . . . . . Licensing requirements for IBM Director components and extensions . . . . . . . . Planning to install IBM Director . . . . . . Choosing where to install IBM Director Server . Planning for events . . . . . . . . . . . Planning events to be monitored . . . . . Planning for event action plan implementations
. 7 . 7 . 10 . 13 . 17 . 26 27 . 28 . . . . .
29 31 31 32 33 34
Chapter 3. Installing . . . . . . . . . 39 Preparing to install IBM Director . . . . Preparing the management server . . . Preparing a Level-1 managed system . . Preparing to manage a BladeCenter . . Preparing Windows XP managed systems
. . . . .
. . . . .
. . . . .
39 39 49 50 53
Chapter 4. Installing IBM Director using the Express installation . . . . . . . 55 Installing IBM Director Server using the Express installation . . . . . . . . . . . . . . Installing IBM Director Server on AIX using the Express installation . . . . . . . . . . . Installing IBM Director Server on Windows using the Express InstallShield wizard . . . . . . Installing IBM Director Server on Linux on POWER using the Express installation option . . Installing IBM Director Server on Linux for System x using the Express installation option . © Copyright IBM Corp. 1999, 2006
55 55 57 59
. 67 . 69 . 70 . 71 . 72 . 73 . 74
Chapter 6. Installing Level 1: IBM Director Core Services . . . . . . . . 77 Installing Level 1: IBM Director Core Services on Linux for System x . . . . . . . . . . . . Installing Level 1: IBM Director Core Services on Linux for System z . . . . . . . . . . . . Installing Level 1: IBM Director Core Services on Linux for POWER . . . . . . . . . . . . Installing Level 1: IBM Director Core Services on Windows . . . . . . . . . . . . . . . Installing Level 1: IBM Director Core Services on Windows using the InstallShield wizard . . . . Performing an unattended installation of Level 1: IBM Director Core Services on Windows . . . Installing IBM Director Core Services using the Software Distribution task . . . . . . . . . Creating a software package . . . . . . . . Installing a software package . . . . . . .
77 78 79 81 81 82 83 85 86
Chapter 7. Installing Level 2: IBM Director Agent . . . . . . . . . . . 89 Installing Level 2: IBM Director Agent on AIX . . Installing Level 2: IBM Director Agent on i5/OS . Installing IBM Director Agent using the Virtualization Engine . . . . . . . . . Installing IBM Director Agent on i5/OS using RSTLICPGM . . . . . . . . . . . . Installing Level 2: IBM Director Agent on Linux for System x . . . . . . . . . . . . . . Installing Level 2: IBM Director Agent on Linux for System z . . . . . . . . . . . . . . Installing Level 2: IBM Director Agent on Linux for POWER . . . . . . . . . . . . . .
. 89 . 91 . 91 . 92 . 92 . 94 . 95
61
iii
Installing Level 2: IBM Director Agent on Linux for Intel Itanium (64 bit) . . . . . . . . . . . 97 Installing Level 2: IBM Director Agent on NetWare 98 Installing Level 2:IBM Director Agent on 32-bit Windows . . . . . . . . . . . . . . . 99 Installing Level 2: IBM Director Agent on 32-bit Windows using the InstallShield wizard . . . . 99 Performing an unattended installation of Level 2: IBM Director Agent on 32-bit Windows . . . 102 Installing Level 2: IBM Director Agent on 64-bit Windows (Intel Itanium only) . . . . . . . . 103 Installing Level 2: IBM Director Agent on 64-bit Windows (Intel Itanium only) using the InstallShield . . . . . . . . . . . . . 104 Performing an unattended installation of Level 2: IBM Director Agent on 64-bit Windows (Intel Itanium only) . . . . . . . . . . . . 106 Installing IBM Director Agent using the Software Distribution task . . . . . . . . . . . . 107 Creating a software package . . . . . . . 108 Installing a software package . . . . . . . 109
Chapter 8. Initially configuring IBM Director . . . . . . . . . . . . . . 111 Configuring IBM Director after an Express installation . . . . . . . . . . . . . . Adding new users in IBM Director . . . . . . Authorizing Request Access on a managed system Enabling Lightweight Directory Access Protocol authentication for IBM Director users . . . . . Using IBM Director in a high-availability environment . . . . . . . . . . . . . . Preparing a high-availability environment for IBM Director and IBM Tivoli System Automation for Multiplatforms . . . . . . Preparing a high-availability environment for IBM Director and SteelEye’s LifeKeeper . . . Configuring IBM Director for a high-availability environment . . . . . . . . . . . . . Configuring discovery preferences . . . . . . Configuring discovery preferences for BladeCenter chassis . . . . . . . . . . Configuring discovery preferences for Level-0 managed systems . . . . . . . . . . . Configuring discovery preferences for Level-1 managed systems . . . . . . . . . . . Configuring discovery preferences for Level-2 managed systems . . . . . . . . . . . Configuring discovery preferences for physical platforms . . . . . . . . . . . . . .
iv
111 112 113 113
Configuring discovery preferences for SMI-S storage devices . . . . . . . . . . . . Configuring discovery preferences for SNMP devices . . . . . . . . . . . . . . Configuring discovery preferences for hardware management consoles . . . . . . . . . Configuring discovery preferences for z/VM systems . . . . . . . . . . . . . . Performing server-initiated discovery of managed objects . . . . . . . . . . . . . . . . Configuring software-distribution preferences . . Setting up file-distribution servers . . . . . Configuring IBM Director to use a file-distribution server . . . . . . . . . Configuring software-distribution preferences for managed systems . . . . . . . . . . Enabling SNMP access and trap forwarding for Linux . . . . . . . . . . . . . . . . Enabling SNMP access and trap forwarding for Linux managed systems . . . . . . . . . Enabling SNMP access and trap forwarding for Red Hat Enterprise Linux versions 3 and 4 . . Enabling SNMP access and trap forwarding for VMware . . . . . . . . . . . . . .
127 130 133 134 136 137 137 138 139 140 141 141 142
Chapter 9. Uninstalling IBM Director on Windows . . . . . . . . . . . . 145 Uninstalling IBM Director using Add/Remove Programs feature Uninstalling IBM Director using command . . . . . . .
the Windows . . . . . . the dirunins . . . . . .
. 145 . 145
114
115 116 116 118 118 120
Appendix A. Accessibility features for IBM Director . . . . . . . . . . . . 147 Appendix B. Lightweight Directory Access Protocol authentication properties for IBM Director Server . . 159 Appendix C. Notices . . . . . . . . 163 Trademarks .
.
.
.
.
.
.
.
.
.
.
.
.
. 164
Glossary . . . . . . . . . . . . . 167
122
Glossary .
123
Index . . . . . . . . . . . . . . . 177
125
IBM Director Express Planning, Installation and Configuration Guide
.
.
.
.
.
.
.
.
.
.
.
.
.
. 167
About this book This book provides information about installing and configuring IBM Director using the Express installation option. 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 © Copyright IBM Corp. 1999, 2006
v
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 – 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/
vi
IBM Director Express Planning, Installation and Configuration Guide
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. Notes:
About this book
vii
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 Implementing IBM Director 5.10 (SG24-6188) v Integrating IBM Director with Enterprise Management Solutions (SG24-5388) v Managing IBM TotalStorage® NAS with IBM Director (SG24-6830) v 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) v IBM Director on System p5 (REDP-4219)
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 User’s 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.
viii
IBM Director Express Planning, Installation and Configuration Guide
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.
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.
© Copyright IBM Corp. 1999, 2006
ix
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 management processor logs IBM Director 5.20 provides support for monitoring and viewing system event logs of Baseboard Management Controllers and Remote Supervisor Adapters on Level-1 managed systems. The log entries are viewed as Common Information Model (CIM) events, and the logs can be cleared automatically when they reach a threshold value. 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 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 SteelEye’s 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
x
IBM Director Express Planning, Installation and Configuration Guide
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. 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.
New in version 5.20
xi
xii
IBM Director Express Planning, Installation and Configuration Guide
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.
© Copyright IBM Corp. 1999, 2006
1
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.
2
IBM Director Express Planning, Installation and Configuration Guide
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: Chapter 1. Getting started with IBM Director
3
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.
4
IBM Director Express Planning, Installation and Configuration Guide
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.
Chapter 1. Getting started with IBM Director
5
6
IBM Director Express Planning, Installation and Configuration Guide
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.
© Copyright IBM Corp. 1999, 2006
7
Table 1. x86-compatible systems: Minimum hardware requirements Requirements
IBM Director Core Services
IBM Director Agent
IBM Director Console ®
IBM Director Server
Microprocessor speed
Pentium-class processor
Pentium-class or Itanium® 2 processor
Pentium 1.5 GHz
Pentium 1.5 GHz
Memory (RAM)
128 MB
128 MB
256 MB
512 MB (minimum) 1024 MB (recommended)
Disk space
Display
40 MB (for Windows)
110 MB (for Windows) 170 MB
100 MB (for Linux)
165 MB (for Linux)
Not applicable
Not applicable
325 MB
At least 256 colors
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 2. Servers running AIX: Minimum hardware requirements Requirements
IBM Director Agent
IBM Director Console
IBM Director Server
Microprocessor speed
Power4 or Power5 1.5 GHz
Power4 or Power5 1.5 GHz
Power4 or Power5 1.5 GHz
Memory (RAM)
512 MB (minimum)
512 MB (minimum)
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.)
325 MB (/opt) 8 MB (/usr)
6 MB (/usr) Display
Not applicable
At least 256 colors
At least 256 colors
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: v The disk space listed is the minimum requirement for an installation using the default selections.
8
IBM Director Express Planning, Installation and Configuration Guide
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 3. Servers running Linux on POWER: Minimum hardware requirements Requirements
IBM Director Core Services
IBM Director Agent
IBM Director Console IBM Director Server
Microprocessor speed
Power4 or Power5 1.5 GHz
Power4 or Power5 1.5 GHz
Power4 or Power5 1.5 GHz
Power4 or Power5 1.5 GHz
Memory (RAM)
128 MB (minimum)
512 MB (minimum)
512 MB (minimum)
512 MB (minimum) 1024 MB (recommended)
Disk space
100 MB
170 MB
225 MB
425 MB
Display
Not applicable
Not applicable
At least 256 colors
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 4. System i products: Minimum hardware requirements Requirements
IBM Director Agent
IBM Director Server
Relative system performance
75 CPW
150 CPW
Storage pool size
350 MB
500 MB
Disk space
300 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 Java and WebSphere® Performance on IBM iSeries Servers (SG24-6256) Redbook 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. The following System z servers are supported: Chapter 2. Planning
9
v IBM System z9™ (all models) v IBM zSeries® (all models) v IBM S/390® (Multiprise® 3, Generation 5 and Generation 6) Table 5. Minimum hardware requirements for IBM Director on System z servers
Requirement
IBM Director Server (with or without CIM instrumentation for z/VM manageability access IBM Director point) Console
Processor speed
All processor speeds provided by IBM System z servers are sufficient for IBM Director.
Memory
1 GB
256 MB
256 MB
512 MB
Disk space
316 MB
168 MB
43-109 MB
215 MB
Display
Not applicable
At least 256 colors
Not applicable
Not applicable
IBM Director Agent
IBM Director Agent with CIM instrumentation for z/VM manageability access point
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 6. Supported versions of network protocols Protocol
Supported version
IPX
IPX versions supported by NetWare and Windows
NetBIOS
Native NetBIOS versions supported by Windows
TCP/IP
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.
10
IBM Director Express Planning, Installation and Configuration Guide
Table 7. Types of data transmission and supported network protocols Type of data transmission
Operating system running on managed system
Supported network protocols
IBM Director Server ←→ IBM Director Console
Not applicable
TCP/IP
IBM Director Server ←→ SNMP devices
Not applicable
TCP/IP
IBM Director Server ←→ IBM Director Agent
AIX
TCP/IP
IBM Director Server ←→ IBM Director Agent
i5/OS
TCP/IP
IBM Director Server ←→ IBM Director Agent
Linux
TCP/IP
IBM Director Server ←→ IBM Director Agent
NetWare
IPX or TCP/IP
IBM Director Server ←→ IBM Director Agent
Windows
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 8 lists the ports used by the various IBM Director processes. v Abbreviations used in Table 8 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 8. Ports used by IBM Director Category IBM Director interprocess communication
Connection IBM Director Server
Destination port ←→
IBM Director Agent
14247 UDP and TCP1
on
page 13; 14248 TCP; 4490 IPX (read); 4491 IPX (write)
IBM Director Console
→
IBM Director Server
2033 TCP
DIRCLI client
←→
IBM Director Server
2044 TCP
DIRCMD client
←→
IBM Director Server
2034 TCP
IBM Director Console
→
IBM Director Console
Any free port (for use of BladeCenter Network Device Manager)
IBM Director Console
→
IBM Director Server over SSL
4066 TCP
DIRCLI client
←→
IBM Director Server
Chapter 2. Planning
11
Table 8. Ports used by IBM Director (continued) Category CIM-XML over HTTP2 on page 13,3
Connection
Destination port
IBM Director Server
→
on page 13
Level-1 or Level-2 managed system, or SMI-S storage device
15988 TCP (SUSE Linux distributions and Red Hat Linux for System z distributions) 5988 TCP (other operating systems)
CIM-XML over HTTPS2 on page 13,3
IBM Director Server
→
on page 13
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 on
CIMOM
→
CIM Listener
6988 TCP (HTTP)
HTTP
IBM Director Server
→
BladeCenter switch module
80 TCP
Microsoft Windows DCOM
IBM Director Server
→
Level-0 system
137 UDP; 138 UDP; 139 TCP; 445 TCP
ServeRAID CIM Provider
→
ServeRAID Manager 34572 TCP
IBM Director Server
←→
service processor
6090 TCP
Service processor
→
IBM Director Server (alerts)
13991 UDP
IBM Director Server
→
service processor (ASF, ASF 2.0, and IPMI)
623 and 664 UDP
Service processor
→
IBM Director Server (ASF, ASF 2.0, and IPMI)
Random port in the 1024-65535 range4 on page 13
SLP
IBM Director Server
←→
SLP service agents or SLP directory agents
427 TCP and UDP
SNMP
IBM Director Server
→
SNMP agent
161 TCP and UDP1 on page
page 13,3 on page 13
ServeRAID interprocess communication Service processors
13
SNMP agent
→
IBM Director Server
162 TCP and UDP1 on page 13
SSH
12
IBM Director Server
→
SNMP devices (Remote Session task)
22 TCP
IBM Director Server
→
Level-0 system
22 TCP
IBM Director Express Planning, Installation and Configuration Guide
Table 8. Ports used by IBM Director (continued) Category Telnet
Connection
Destination port
IBM Director Server
→
BladeCenter management module
23 TCP
IBM Director Server
→
BladeCenter switch module
23 TCP
IBM Director Server
→
SNMP devices (Remote Session task)
23 TCP
Abbreviations used in Table 8 on page 11 v ASF = Alert Standard Format v HTTP = Hypertext Transfer Protocol v HTTPS = Hypertext Transfer Protocol Secure 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/ .
Chapter 2. Planning
13
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. 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 IBM Director Agents & Consoles, V5.20 (2 of 2) v IBM Director for AIX 5L™, V5.20 v IBM Director for i5/OS, V5.20 v IBM Director for Linux on POWER, V5.20 v IBM Director 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 9. Operating systems supported by IBM Director on System x systems and third-party Intel-based systems
Operating system
IBM Director Console
IBM Director Server
IBM Director Agent
IBM Director Core Services
X
X
X
X
X
X
X
X
X
X
X
X
X
X
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)
X
Windows Server 2003 Datacenter Edition (supports Service Pack 1 ) Windows Server 2003, Enterprise, Standard, and Web Editions (supports Service Pack 1 and Release 2)
X
Windows XP Professional Edition (supports Service Pack 2 and earlier)
X
Editions of Windows for 64-bit systems: Windows Server 2003 Datacenter Edition for Itanium systems
14
IBM Director Express Planning, Installation and Configuration Guide
X
Table 9. Operating systems supported by IBM Director on System x systems and third-party Intel-based systems (continued)
Operating system
IBM Director Console
IBM Director Server
Windows Server 2003 Datacenter x64 Edition (supports Release 2 and earlier)
IBM Director Agent
IBM Director Core Services
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Windows Server 2003 Enterprise Edition for Itanium systems Windows Server 2003, Enterprise, Standard, and Web x64 Editions (supports Release 2 and earlier)
X
X
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 7 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.
X
Red Hat Enterprise Linux WS, version 3.0 (supports Update 7 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 3 and X earlier)
X
Red Hat Enterprise Linux WS, version 4.0 (supports Update 3 and earlier) SUSE Linux Enterprise Server 9 for x86 (supports Service Pack 3 and earlier)
X
X
X
X
SUSE Linux Enterprise Server 10 for x86
X
X
X
X
X
X
X
X
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.
X
X
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.
X
X
Red Hat Enterprise Linux AS and ES, version 3.0, for AMD64 and EM64T (supports Update 7 and earlier)
X
X
Red Hat Enterprise Linux WS, version 3.0, for AMD64 and EM64T (supports Update 7 and earlier)
X
X
X
X
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, Console VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, guest X 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.
X
Versions of Linux for 64-bit systems: Red Hat Enterprise Linux AS, version 3.0, for Intel Itanium
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 3 and earlier)
X
Chapter 2. Planning
15
Table 9. Operating systems supported by IBM Director on System x systems and third-party Intel-based systems (continued)
Operating system
IBM Director Console
IBM Director Agent
IBM Director Core Services
X
X
X
X
X
IBM Director Server
Red Hat Enterprise Linux WS, version 4.0, for AMD64 and EM64T (supports Update 3 and earlier) 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
X
X
X
X
SUSE Linux Enterprise Server 10 with Xen Kernel
X
X
X
X
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.
X
X
NetWare, version 6.5 Note: Level-0 support is not provided.
X
Other operating systems supported by System x servers:
Table 10. Operating systems supported by IBM Director on System i and System p products
Operating system
IBM Director Console
IBM Director Server
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.
IBM Director Agent
IBM Director Core Services
X
X
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.
X
X
X
X
Red Hat Enterprise Linux AS, version 4.3 and 4.4, for IBM POWER
X
X
X
X
SUSE Linux Enterprise Server 9 for IBM POWER (Service Pack 3 required)
X
X
X
X
SUSE Linux Enterprise Server 10 for IBM POWER
X
X
X
X
IBM Director Console
IBM Director Server
IBM Director Agent
IBM Director Core Services
X
X
X
X
Table 11. Operating systems supported by IBM Director on System z systems
Operating system Red Hat Enterprise Linux AS, version 4.0, for IBM System z (supports Update 4 and earlier)
16
IBM Director Express Planning, Installation and Configuration Guide
Table 11. Operating systems supported by IBM Director on System z systems (continued) IBM Director Console
IBM Director Server
IBM Director Agent
IBM Director Core Services
SUSE Linux Enterprise Server 9 for IBM System z (supports Service Pack 3 and earlier)
X
X
X
X
SUSE Linux Enterprise Server 10 for IBM System z
X
X
X
X
Operating system
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
Task Asset ID
™
Linux and Windows only
X
CIM Manager
X
Configuration Manager
X
Configure SNMP Agent
X
Event Log
X
External Application Launch
X
File Transfer
X
Hardware Control Point
X
Hardware Management Console
X
Chapter 2. Planning
17
Task is supported on the following operating systems:
Task
All operating systems supported by IBM Director Server
Hardware Status
X
Inventory (hardware)
X
Inventory (software)
X
Microsoft Cluster Browser
X
Network Configuration
X
Power Management
X
Process Management
X
Rack Manager
X
Remote Control
X
Remote Session
X
Resource Monitors
X
Server Storage Provisioning Tool
Linux and Windows only
X
SNMP Browser
X
Software Distribution
X
Storage Configuration Manager
X
System Accounts
X
Update Manager
X
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. Review the following considerations when using this table: 1. Not supported on Itanium systems. 2. Not supported on System z systems. 3. Not supported on guest operating systems. 4. Supported on System x and Intel-based systems only. 5. Not supported on Windows XP Professional x64 Edition. 6. Support on Itanium systems is limited to Level 2. 7. Platform-specific data is not available for hardware inventory. 8. 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 9. Not supported for Linux on POWER. 10. Not supported on 64-bit versions of these operating systems. 11. Supported on Windows guest operating systems only. 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.
18
IBM Director Express Planning, Installation and Configuration Guide
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. Operating systems
Task
Windows Level 2
1
CIM Manager Level 2
1
Asset ID
ESX Server GSX Server
i5/OS
AIX
NetWare
Microsoft Virtual Server
1, 2
Level 2
Level 2
No
No
Level 2
1
Level 2
Level 2
Level 2
No
Level 2
Linux Level 2
Level 2
Configuration See “Operating systems supported by the Configuration Manager task” Manager Configure SNMP Agent
Level 21
Level 21, 5
Level 2
Level 2
Level 2
No
Level 2
Event Log
Levels 1, 2
Levels 1, 2
Levels 1, 2
Levels 1, 2
Levels 1, 2
Levels 1, 2
Levels 1, 2
External Application Launch
See “Operating systems supported by External Application Launch”
File Transfer
Level 2
Level 2
Level 2
Hardware Status
See “Operating systems supported by the Hardware Status task”
Level 2
Level 2
14
Level 2
Level 2
Levels 0, 1, 26, 7
Levels 0, 1, 26, 7
Levels 0, 1, 2 Level 2
Level 27
Level 27
Levels 0, 1, 2
Inventory (software)
Levels 0, 1, 26
Levels 0, 1, 26
Levels 0, 1, 2 Level 2
No
Level 2
Levels 0, 1, 2
Microsoft Cluster Browser
Level 28
No
No
No
No
No
No
Level 21, 9
Level 2
Level 2
No
No
Level 2
Inventory (hardware)
15
Network Level 21 Configuration Power Management
See “Operating systems supported by the Power Management task”
Process Management
Level 2
Rack Manager Level 210
Level 2
Level 2
Level 2
Level 2
Level 2
Level 2
Level 24, 10
Level 2
No
No
Level 2
Level 2
No
No
No
Level 2
13 11
Remote Control
Level 2
No
Level 2
Remote Session
Level 2
Level 2
Level 2
Level 2
Level 2
Level 2
Level 2
Resource Monitors
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
Level 2
Level 2
Level 2
Level 2
Level 2
Level 2
Level 2
Chapter 2. Planning
19
Operating systems
Task
Windows
Software Distribution
ESX Server GSX Server
Linux
i5/OS
Levels 0, 1, 2 Levels 0, 1, 2 Levels 0, 1, 2 Levels 0, 2
AIX
NetWare
Microsoft Virtual Server
Levels 0, 1, 2 No
Levels 0, 1, 2
12
Storage Levels 1, 2 Configuration Manager
Levels 1, 2
2,
Levels 1, 2
No
No
No
Levels 1, 2
Level 2
Level 2
No
No
Level 2
No
No
Levels 0, 1, 2
9
System Accounts
Level 21
Level 21, 9
Update Manager
Levels 0, 1, 2 Levels 0, 1, 2 Levels 0, 1, 2 No 2, 9
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 Table 12. Hardware Status support for System x servers; IBM and third-party x86-based systems Operating system Editions of Windows for 32-bit systems:
20
IBM Director Express Planning, Installation and Configuration Guide
Level 1
Level 2
Table 12. Hardware Status support for System x servers; IBM and third-party x86-based systems (continued) Operating system
Level 1
Level 2
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
Yes
Yes
v Windows Server 2003, Datacenter, Enterprise, Standard, and Web x64 Editions v Windows XP Professional x64 Edition
Yes
Yes
Windows Server 2003, Datacenter and Enterprise 64-bit Itanium Editions
No
No
Yes
Yes1
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, Console
Yes1
Yes1
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, guest operating systems
Limited
Limited
v VMware GSX Server, versions 3.1 and 3.2, Console v VMware GSX Server, versions 3.1 and 3.2, guest operating systems
(For Console) Yes1 (For guest) Limited
(For Console) Yes1 (For guest) Limited
Yes
Yes
No
No
Editions of Windows for 64-bit systems:
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
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
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
1
Other operating systems supported by System x servers: Microsoft Virtual Server (guest operating system) NetWare, version 6.5
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 13. Hardware Status support for System i platforms and System p servers Operating system
Level 1
Level 2
v AIX 5L, Version 5.2 v AIX 5L, Version 5.3
No
No
v i5/OS, Version 5 Release 3
No
Yes1
Yes1
Yes1
v i5/OS, Version 5 Release 4 v Red Hat Enterprise Linux AS, version 4.3 and 4.4, for IBM POWER v SUSE Linux Enterprise Server 9 for IBM POWER v SUSE Linux Enterprise Server 10 for IBM POWER
1. (BladeCenter JS20 and JS21 only) Out-of-band notifications generated by a service processor only.
Chapter 2. Planning
21
Table 14. Hardware Status support for System z servers Operating system
Level 1
Level 2
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z v SUSE Linux Enterprise Server 9 for IBM System z v SUSE Linux Enterprise Server 10 for IBM System z
No
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 15. Operating systems supported by System x servers and third-party Intel-based systems Operating system
Supported
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
Yes, Restart and Shutdown
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:
22
IBM Director Express Planning, Installation and Configuration Guide
Yes, Restart and Shutdown
Table 15. Operating systems supported by System x servers and third-party Intel-based systems (continued) Operating system v v v v v v
Supported
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, and 3.0, Console VMware GSX Server, versions 3.1 and 3.2, Console
v VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, guest operating systems v VMware GSX Server, versions 3.1 and 3.2, guest operating systems
Yes, Restart
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
NetWare, version 6.5
No
Note: (For System p servers only) Power Management-support provided only for Level-2 managed systems. Table 16. Operating systems supported by System i platforms and System p servers Operating system
Supported
v i5/OS, Version 5 Release 3
No
1
v i5/OS, Version 5 Release 4 v v v v v
AIX 5L, Version 5.2 AIX 5L, Version 5.3 Red Hat Enterprise Linux AS, version 4.3 and 4.4, for IBM POWER SUSE Linux Enterprise Server 9 for IBM POWER SUSE Linux Enterprise Server 10 for IBM POWER
Yes, Restart
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 17. Operating systems supported by System z servers Operating system
Supported
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z v SUSE Linux Enterprise Server 9 for IBM System z v SUSE Linux Enterprise Server 10 for IBM System z
Yes, Restart
Chapter 2. Planning
23
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, version 5.10. 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. These servers can be Level-0, Level-1, or 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-0, Level-1, or 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 18. Operating systems supported by System x servers and third-party Intel-based systems Operating system
Supported
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
Yes
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
Yes
Versions of Linux for 32-bit systems: v v v v
24
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
IBM Director Express Planning, Installation and Configuration Guide
Yes
Table 18. Operating systems supported by System x servers and third-party Intel-based systems (continued) Operating system v v v v
VMware VMware VMware VMware
Supported
ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, Console ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, guest operating systems GSX Server, versions 3.1 and 3.2, Console GSX Server, versions 3.1 and 3.2, guest operating systems
No
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)
No
NetWare, version 6.5
Yes
Operating systems supported by IBM Server Storage Provisioning Tool The IBM Server Storage Provisioning Tool 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. Note: IBM Server Storage Provisioning Tool provides Level-0, Level-1, and Level-2 support only on 32-bit operating systems for configurations that contain a BladeCenter Qlogic 2 Port Fibre Channel Switch Module (48P7062). Table 19. IBM Server Storage Provisioning Tool support for System x servers; IBM and third-party x86-based systems Operating system
Level 0
Level 1
Level 2
Yes
Yes
Yes
v Windows Server 2003, Datacenter, Enterprise, Standard, and Web x64 Editions v Windows XP Professional x64 Edition
No
No
Yes
Windows Server 2003, Datacenter and Enterprise 64-bit Itanium Editions
No
No
No
Yes
Yes
Yes
No
No
No
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, guest operating No systems
No
Yes
v VMware GSX Server, versions 3.1 and 3.2, Console v VMware GSX Server, versions 3.1 and 3.2, guest operating systems
No
No
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:
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
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, Console
No
Chapter 2. Planning
25
Table 19. IBM Server Storage Provisioning Tool support for System x servers; IBM and third-party x86-based systems (continued) Operating system
Level 0
Level 1
Level 2
No
Yes
No
No
No
Microsoft Virtual Server (guest operating system)
No
No
No
NetWare, version 6.5
No
No
No
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 No ES, and WS, version 4.0, for AMD64 and EM64T 9 for AMD64 and EM64T 10 for AMD64 and EM64T 10 with Xen Kernel
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:
Table 20. IBM Server Storage Provisioning Tool support for System i platforms and System p servers Operating system
Level 0
Level 1
Level 2
v AIX 5L, Version 5.2 v AIX 5L, Version 5.3
No
No
No
v i5/OS, Version 5 Release 3
No
No
No
No
No
No
Operating system
Level 0
Level 1
Level 2
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z v SUSE Linux Enterprise Server 9 for IBM System z v SUSE Linux Enterprise Server 10 for IBM System z
No
No
No
v i5/OS, Version 5 Release 4 v Red Hat Enterprise Linux AS, version 4.3 and 4.4, for IBM POWER v SUSE Linux Enterprise Server 9 for IBM POWER v SUSE Linux Enterprise Server 10 for IBM POWER Table 21. IBM Server Storage Provisioning Tool support for System z servers
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.
26
IBM Director Express Planning, Installation and Configuration Guide
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 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 22. IBM Director task support for BladeCenter products Tasks and subtasks
Chassis
Network device
Blade server without IBM Director Agent or IBM Director Core Services installed
BladeCenter Configuration Manager
Yes
No
Not applicable
Event Action Plans
Yes
Yes
Yes
Hardware Status
Yes
No
Inventory
Yes
Yes
Yes
Not applicable
Yes
Not applicable
Power Management
No
No
Yes
Rack Manager
Yes
Yes
No
Remote Session
Not applicable
Yes
No
Remote Monitors
No
Yes
No
SNMP Browser
No
Yes
Yes
Network Device Manager (formerly Switch Management launch pad)
Yes
1
2
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.
Chapter 2. Planning
27
Table 23. IBM Director task support for Storage products Tasks and features
DS300 DS400 DS4000 Brocade switches
DS6000 QLogic BladeCenter switches
Event Action Plans1
Yes
No
Event Log
Yes
Yes
External Application Launch
Yes
Yes
Hardware Status
Yes
Yes
Inventory
Yes
Yes
1. Indicates that the Storage product generates events. Events are detected for use in event action plans.
Supported database applications IBM Director Server uses an SQL database to store inventory data for the systems in the environment. Depending on the database application selected and the operating system of the management server, the database might be embedded, local, or remote. 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 24. Database applications supported by IBM Director 5.20 Database
AIX
i5/OS
Linux
Windows
Apache Derby
v V10.1 (included with IBM Director Server on AIX, Linux, and Windows)
Embedded
—
Embedded
Embedded
IBM DB2 Universal Database™
v version 8.2 with Fix Pack 5 v version 8.1 with Fix Pack 12
Local or remote
—
Local or remote
Local or remote
IBM DB2 Universal Database for System i (part of i5/OS)
—
Local
—
—
v Microsoft SQL Server — 2005 with Service Pack 1 v Microsoft SQL Server 2000 with Service Pack 4
—
Remote
Local or remote
v Microsoft SQL Server — 2005 Express Edition with Service Pack 1 v Microsoft SQL Server 2000 Desktop Engine (also called MSDE 2000) with Service Pack 4
—
—
Local
Microsoft SQL Server
28
Supported database versions
IBM Director Express Planning, Installation and Configuration Guide
Table 24. Database applications supported by IBM Director 5.20 (continued) Database Oracle (Oracle Server)
Supported database versions v version 10g release 2 v version 10g release 1 v version 9.2
PostgreSQL v version 8.1 v version 7.4 v version 7.3
AIX
i5/OS
Linux
Windows
Local or remote
—
Local or remote
Local or remote
—
—
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. Note: 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.
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
Chapter 2. Planning
29
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.”
IBM Director Console 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 IBM System p servers v IBM System x servers v v v v
IBM IBM IBM IBM
System z mainframes System Storage Network Attached Storage (NAS) products SurePOS point-of-sale systems ThinkCentre, NetVista, and PC desktop computers
v IBM 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
30
IBM Director Express Planning, Installation and Configuration Guide
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) 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 v v v
Capacity Manager Remote Deployment Manager extension Software Distribution Premium Edition 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.
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.
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
Chapter 2. Planning
31
installed either on a blade in the BladeCenter, or on a separate management server. Refer to “Preparing to manage a BladeCenter” on page 50 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. – 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.
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 v Microsoft Windows event log v Windows Management Instrumentation (WMI)
32
IBM Director Express Planning, Installation and Configuration Guide
v SNMP through out-of-band communication v Intelligent Platform Management Interface (IPMI) Platform Event Traps (PET) through out-of-band communication v IBM service processors through out-of-band communication 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 The events that you can monitor are divided into three groups. You can enable the monitoring of these events using any one of the available user interfaces, including IBM Director and a Web browser. Tip: These events are not enabled by default. v Critical alerts – Temperature outside critical thresholds – Voltage outside critical thresholds – Tamper alert (server cover opened) - on some servers only – Multiple fans failure – Power supply failure – Hard disk drive failure – VRM failure v Warning alerts (non-critical) – Redundant power supply failure – Single fan failure – Temperature outside warning thresholds – Voltage outside warning thresholds v System alerts – Operating system timeout value is exceeded – Power off – Power on – – – –
Boot failure Server loader timeout value is exceeded PFA notification Partition configuration Chapter 2. Planning
33
If you enable the O/S timeout and server loader timeout alerts, then you also must plan to enable those timeouts. 1. Consider how events will be sent by the managed systems to IBM Director Server. There are generally two options: v via telephonic modem v over a LAN, using an IP address 2. On the service processors that have Ethernet connections and modems, you should configure those connections so alerts can be sent through them. For Ethernet connections, configure either a static IP address or enable the use of DHCP. Tips: v The Remote Supervisor Adapter and Remote Supervisor Adapter II support DHCP; however, the use of a static IP address is potentially more reliable than using DHCP. A static address will mean that the failure or inaccessibility of DNS and/or DHCP servers will not prevent access to the service processor. v If the Remote Supervisor Adapter II is set to use DHCP but does not receive an address from the DHCP server within two minutes, it will set its address as 192.168.70.125. v For modem use, configure the standard modem settings (baud rate, parity, and stop bits) plus any additional strings if necessary. v For SNMP, enable traps and the SNMP agent, and configure the community name and IP address. v For SMTP, configure the SMTP server.
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. 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
34
IBM Director Express Planning, Installation and Configuration Guide
– 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. Note: 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 Chapter 2. Planning
35
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. 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
36
IBM Director Express Planning, Installation and Configuration Guide
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.
Chapter 2. Planning
37
38
IBM Director Express Planning, Installation and Configuration Guide
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.
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 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 theIBM Director for i5/OS, V5.20 media. 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, V5.20 (1 of 2) CD. 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
Order number
(V5R3 only) IBM Cryptographic Access Provider 128-bit for iSeries
5722-AC3
IBM HTTP Server for iSeries
5722-DG1
Extended Base Directory Support, Option 3
5722-SS1
™
Java Developer Kit 1.4, Option 6 © Copyright IBM Corp. 1999, 2006
5722-JV1
39
Products or options ®
Order number
OS/400 - Qshell, Option 30
5722-SS1
OS/400 - Digital Certificate Manager, Option 34
5722-SS1
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 Make sure that you have applied the most recent fix packages, otherwise the server might not start after the installation is completed. 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 on POWER Before installing IBM Director Server on a Linux on POWER platform, 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 You can obtain the IBM Director software for Linux for System p from the following sources: – The IBM Director Web site at www.ibm.com/systems/management/director/ downloads.html. – If it was included with your IBM Director distribution, the IBM Director for Linux on POWER, V5.20 CD. v Red Hat Enterprise Linux AS, version 4, for IBM POWER only: Before installing IBM Director, ensure that the following RPM file (or later version) is installed: – compat-libstdc++-33-3.2.3-47.3.ppc.rpm v Red Hat Enterprise Linux AS, version 4, for IBM POWER and SUSE Linux Enterprise Server 9 and 10: Ensure that the following RPM files (or later versions) are installed: – librtas-1.2-1.ppc64.rpm – lsvpd-0.12.7-1.ppc.rpm
40
IBM Director Express Planning, Installation and Configuration Guide
– 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 When you install the powerpc-utils RPM files on a system where a version of the ppc64-utils RPM is already installed, a file conflict error message might occur. In this case, use the --force option to install the powerpc-utils RPM file: – rpm -Uvh --force powerpc-utils-1.0.0-1.ppc64.rpm – rpm -Uvh --force powerpc-utils-papr-1.0.3-1.ppc64.rpm To check for the fileset, type the following command and press Enter: rpm -qa | grep ppc64-utils
You can download these RPM files from the IBM Service and productivity tools for Linux on POWER Web site at www14.software.ibm.com/webapp/set2/sas/ f/lopdiags/home.html. Select the appropriate tab for your Linux distribution.
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 required RPMs are installed: Table 25. Required RPMs Red Hat Enterprise Linux AS and ES, version 3.0
compat-libstdc++-7.3-2.96.122.i386.rpm
Red Hat Enterprise Linux AS and ES, version 4.0
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 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 IPMI baseboard management controllers: Install the supporting IPMI device drivers and mapping layers, if they are not already installed. IBM Director cannot receive System Health Monitoring information if these drivers and mapping layers are not installed. The device drivers and mapping layers for Windows, Linux, and NetWare can be downloaded from the IBM Director support Web site at www.ibm.com/pc/support. For eServer™ 325 or eServer 326 models, download and install the following items (the exact names of the files to download are dependent upon your operating system): – MSI IPMI device drivers for Windows Chapter 3. Installing
41
– IBM IPMI Library (mapping layer) For all other System x systems, download and install the following items (the exact names of the files to download are dependent upon your operating system): – OSA IPMI device drivers – IBM Mapping layer software source for OSA IPMI
v
v
v
v
Important: You must install the device driver first and then install the mapping layer. 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. 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. 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, V5.20 (1 of 2) CD. The IBM Director on x86, V5.20 CD does not include SUSE Linux Enterprise Server (SLES) 10 installation packages for IBM Director Server, IBM Director Console, IBM Director Agent, or IBM Director Core Services. You can download these SLES 10 installation packages for System x platforms from theIBM Director Web site at: www.ibm.com/systems/management/director/ .
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. 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 managed system to enable management of the service processor, complete the following steps: 1. Refer to the documentation for your managed servers to identify what type of service processor is installed. For a list of service processors that are typically used with IBM servers, see the“Service processors in System x, xSeries, eServer, and BladeCenter blade servers” topic in the IBM Director Systems Management Guide. 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
42
IBM Director Express Planning, Installation and Configuration Guide
processor for that system, and all management occurs through the Remote Supervisor Adapter or Remote Supervisor Adapter II. 2. After identifying the service processor types that you will be managing, use the following table to determine the drivers that must be installed for in-band (Level-1 or Level-2) management of the service processors. Notes: a. For servers that will be managed as Level-0 (″agentless″) servers, you do not need to install drivers to perform Level-0 management of the service processors. b. The MSI IPMI driver and the OSA IPMI driver must be installed before the IBM Mapping Layer. Table 26. Required drivers for in-band management of service processors Integrated system management processor
IPMI baseboard management controller
Remote Supervisor Adapter II
OpenIPMI driver
OpenIPMI driver
RSA daemon, USB drivers
Other Red Hat MSI IPMI driver, Linux distributions IBM Mapping Layer
OSA IPMI driver, IBM Mapping Layer
RSA daemon, USB drivers
v SUSE Linux Enterprise Server 9 for x86
OpenIPMI driver
OpenIPMI driver
RSA daemon, USB drivers
Other SUSE Linux distributions
MSI IPMI driver, IBM Mapping Layer
OSA IPMI driver, IBM Mapping Layer
RSA daemon, USB drivers
virtual systems using Xen
OpenIPMI driver
OpenIPMI driver
RSA daemon, USB drivers
VMware
OpenIPMI driver
OpenIPMI driver
USB drivers
MSI IPMI driver, IBM Mapping Layer
OSA IPMI driver, IBM Mapping Layer
Not Supported
MSI IPMI driver, IBM Mapping Layer
OSA IPMI driver, IBM Mapping Layer
RSA library, USB drivers
Operating system of managed server Red Hat Linux
v Red Hat Enterprise Linux, version 3.0 (update 6) v Red Hat Enterprise Linux, version 4.0 (update 3)
SUSE Linux
v VMware ESX Server, version 2.5.4, Console v VMware ESX Server, version 3.0, Console Other VMware distributions
Windows
3. Make sure that you have the latest firmware installed for your service processors. IBM LM78 and SMBus device drivers for Linux:
Chapter 3. Installing
43
This topic describes when to install the LM78 and SMBus device drivers for Linux. If you plan to install IBM Director Server on an 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. Table 27. Installing IBM Director Server: IBM LM78 and SMBus device drivers for Linux Device driver
When it is needed
What it does
LM78
If either of the following conditions applies: The LM78 device driver ensures that IBM Director v The server is one of the following Server receives memory and servers: processor Predictive Failure – BladeCenter HS20, machine type 8832 Analysis® (PFA) alerts. – BladeCenter HS20, machine type 8843 – BladeCenter HS40, machine type 8839 – xSeries 225, machine type 8647 – xSeries 226, machine type 8836 – xSeries 236, machine type 8841 – xSeries 336, machine type 8837 – xSeries 346, machine type 8840 v The server contains an integrated systems management processor (ISMP).
SMBus
If the server does not contain one of the following service processors: v IPMI baseboard management controller 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.
Preparing to install the LM78 and SMBus device drivers: This topic describes how to install the IBM LM78 and SMBus device drivers. You must perform the following steps to install either the IBM LM78 or SMBus device driver: 1. Build a binary RPM file that is customized for the kernel version of the Linux operating system on your server. For instructions, see “Building the binary RPM file.” 2. Install the binary RPM file on the system on which you will install IBM Director Server. For instructions, see “Installing the IBM LM78 or SMBus device driver” on page 45. 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.
44
IBM Director Express Planning, Installation and Configuration Guide
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/
where
Command
LM78
rpmbuild -tb ibmlm78-5.20-1.tgz
SMBus
rpmbuild -tb ibmsmb-5.20-1.tgz
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).
Chapter 3. Installing
45
Note: In this procedure, driver is one of the following strings: Device driver
Command
IBM LM78
ibmlm78
IBM SMBus
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 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” and “Uninstalling the IBM SMBus device driver, version 4.20 or earlier” on page 47. 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
where driver is one of the following strings. Device driver
Command
IBM LM78
ibmlm78
IBM SMBus
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.
46
IBM Director Express Planning, Installation and Configuration Guide
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 46. 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
String
For servers running Red Hat Linux or VMware ESX Server
redhat
For servers running SUSE Linux
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 46. 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: rpm -e ibmsmb-src-distribution
where distribution is one of the following strings. Type of distribution
String
For servers running Red Hat Linux or VMware ESX Server
redhat
For servers running SUSE Linux
suse
Issuing this command unloads the device driver and removes all driver-related files from the server.
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. Chapter 3. Installing
47
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 28 lists some methods of making the installation code available. Table 28. Making the IBM Director installation code available to Linux on System z Method
How to proceed
NFS server
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: 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.
48
IBM Director Express Planning, Installation and Configuration Guide
v Ensure that the following RPMs are installed. Table 29. Required RPMs Red Hat 31-bit Enterprise Linux AS, version 4.0
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
64-bit
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
SUSE Linux Enterprise Server 9
31-bit
compat-2004.7.1-1.2.s390.rpm
64-bit
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
SUSE Linux Enterprise Server 10 for IBM System z
64-bit
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
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 User’s 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 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 Chapter 3. Installing
49
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. Related tasks “Preparing to manage service processors with IBM Director” on page 42 You can use IBM Director to manage supported service processors that are installed in a managed system.
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 3 on page 51 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.
50
IBM Director Express Planning, Installation and Configuration Guide
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/ .
Figure 3. 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: Chapter 3. Installing
51
– 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 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 3 on page 51 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 4 on page 53 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/ .
52
IBM Director Express Planning, Installation and Configuration Guide
Figure 4. 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 . 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. 2. Configure Windows Firewall (Internet Connection Firewall) to allow access by IBM Director Server. Windows XP (before Service Pack 2) includes a built-in Chapter 3. Installing
53
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.
54
IBM Director Express Planning, Installation and Configuration Guide
Chapter 4. Installing IBM Director using the Express installation After preparing your systems and environment for IBM Director, you can use the applicable Express installation procedure to install IBM Director Server. The Express installation option automatically installs the tasks and options that are typically used by Small and Medium Businesses.
Installing IBM Director Server using the Express installation After preparing your system, use the IBM Director Server Express installation procedure for the applicable operating system on which you plan to install IBM Director Server.
Installing IBM Director Server on AIX using the Express installation After preparing your server, you can use the Express installation option to install IBM Director Server on AIX. To perform an Express installation, you must run the dirinstall script against a response file in which the ExpressInstall parameter is enabled by setting it to 1. Important: v IBM Director Server and IBM Director Console must be at the same release level. If you install IBM Director Server, version 5.20 on the management server, you must also install IBM Director Console, version 5.20 on any systems that you want to access the management server. In addition, 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. Management servers running i5/OS, IBM Director Server use the DB2 database. On all other operating systems, the default database is Apache Derby, but other databases can be used. v 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. On management servers running i5/OS, however, IBM Director Server does not include IBM Director Console. 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 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. © Copyright IBM Corp. 1999, 2006
55
To use the Express installation option to install IBM Director Server on AIX, complete the following steps: 1. To install IBM Director Server from a Web download, perform the following steps: a. Download the IBM Director for AIX - Version 5.20 (Dir5.20_AIX.tar.gz) file from the IBM Director downloads page at:www.ibm.com/systems/ management/director/downloads.html. b. To unzip and extract the contents of the Dir5.20_AIX.tar.gz file, type the following command: gzip -cd Dir5.20_AIX.tar.gz | tar -xvf -
Go to step 3. 2. To install IBM Director Server from the CD, perform the following steps: a. Insert the IBM Director for AIX 5L, V5.20 CD into the drive. b. If the CD automounts, go to step 2c. 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. 3. Type the following command and press Enter to copy the response file (dirserv.rsp) to a local directory : cp dirserv.rsp /directory
where directory is the local directory. 4. Use an ASCII text editor to open the copy of the response file, and change the value of the ExpressInstall parameter to 1. In the response file, ″1″ indicates that an item is to be installed and ″0″ indicates that an item is not to be installed. 5. Save the modified response file. 6. Type the following command and press Enter: ./dirinstall -r /directory/response.rsp
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 5. 7. The License Agreement message is displayed. If you agree with the terms, proceed with the installation. Otherwise, cancel the installation. The installation progress displays. 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: install_root/bin/cfgsecurity
where install_root represents the root directory of your IBM Director installation. 9. To start IBM Director Server, type the following command and press Enter: install_root/bin/twgstart
56
IBM Director Express Planning, Installation and Configuration Guide
10. 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. 11. If you used the CD to install IBM Director Server, remove the CD from the drive. Note: (AIX and Linux only) If you log into IBM Director Console using the root account, all the IBM Director tasks for a Standard installation are displayed.
Installing IBM Director Server on Windows using the Express InstallShield wizard After preparing your System x server for the installation of IBM Director, run the IBM Director Server installation program and choose the Express installation feature. Important: v IBM Director Server and IBM Director Console must be at the same release level. If you install IBM Director Server, version 5.20 on the management server, you must also install IBM Director Console, version 5.20 on any systems that you want to access the management server. In addition, 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. Management servers running i5/OS, IBM Director Server use the DB2 database. On all other operating systems, the default database is Apache Derby, but other databases can be used. v 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. On management servers running i5/OS, however, IBM Director Server does not include IBM Director Console. 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 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. To install IBM Director Server using the Express installation, complete the following steps: 1. Using an account with either local or domain administrative privileges, log on to the operating system. 2. Insert the IBM Director on x86, V5.20 into the drive. Chapter 4. Installing IBM Director using the Express installation
57
3. If the installation program starts automatically and the IBM Director Setup window opens, go to step 5. Otherwise, click Start → Run. 4. 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. 5. 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:
6. 7. 8. 9.
a. Close the IBM Director Setup window. b. Open Windows Explorer. c. Browse to the director/server/windows/i386 directory on the IBM Director on x86, V5.20 CD. d. Run the ibmsetup.exe program. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Server window opens. Click Next. The License Agreement window opens. Click I accept the terms in the license agreement; then, click Next. The Installation Type window opens. Click Perform an Express Installation of IBM Director Server; then, click Next. The Destination Folder window opens. To select an alternative location for the IBM Director Server installation directory, click Change and select another directory.
10. Click Next. The IBM Director Service Account Information window opens. 11. 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.
12. 13.
14. 15.
58
Note: The information that you provide must correspond to a Windows account with administrator privileges on the management server. Otherwise, the installation will fail. Click Next. The Encryption Settings window opens. 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. Click Next. The Software Distribution Settings window opens. To select an alternative location for the creation of the software-distribution packages, click Change and select another directory.
IBM Director Express Planning, Installation and Configuration Guide
16. 17.
18. 19. 20.
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. Click Next. The Ready to Install the Program window opens. 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, a status window opens. Click Finish. A window opens, asking you if you want to restart the server. Remove the CD from the drive. Click Yes to restart the server.
Installing IBM Director Server on Linux on POWER using the Express installation option After preparing your server, you can use the Express installation option to install IBM Director Server on Linux on POWER. To perform an Express installation, you must run the dirinstall script against a response file in which the ExpressInstall parameter is enabled. Important: v IBM Director Server and IBM Director Console must be at the same release level. If you install IBM Director Server, version 5.20 on the management server, you must also install IBM Director Console, version 5.20 on any systems that you want to access the management server. In addition, 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. Management servers running i5/OS, IBM Director Server use the DB2 database. On all other operating systems, the default database is Apache Derby, but other databases can be used. v 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. On management servers running i5/OS, however, IBM Director Server does not include IBM Director Console. 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 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. To install IBM Director Server on Linux on POWER, complete the following steps: Chapter 4. Installing IBM Director using the Express installation
59
1. To install IBM Director Server from a Web download, perform the following steps: a. Download the IBM Director for Linux on POWER - Version 5.20 (Dir5.20_LinuxonPower.tar.gz) file from the IBM Director downloads page at: www.ibm.com/systems/management/director/downloads.html. b. Extract the contents of the Dir5.20_AIX.tar.gz file into a local directory. c. To change to the directory in which IBM Director Server is located, type the following command and press Enter: cd /directory/director/server/linux/ppc/
where directory is the local directory into which you extracted the files. Go to step 5. 2. To install IBM Director Server from a CD, insert the IBM Director for Linux on POWER, V5.20 CD into the drive. 3. If the CD automounts, go to step 4. If the CD does not automount, 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. 4. Change to the directory in which the installation script is located. Type the following command and press Enter: cd /mnt/cdrom/director/server/linux/ppc/
where mnt/cdrom is the mount point of the drive. 5. Type the following command and press Enter to copy the response file (dirserv.rsp) to a local directory : cp dirserv.rsp /directory
where directory is the local directory. 6. Use an ASCII text editor to open the copy of the response file, and change the value of the ExpressInstall parameter to 1. In the response file, ″1″ indicates that an item is to be installed and ″0″ indicates that an item is not to be installed. 7. Save the modified response file. 8. Type the following command and press Enter: ./dirinstall -r /directory/response.rsp
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 7. 9. The License Agreement message is displayed. If you agree with the terms, proceed with the installation. Otherwise, cancel the installation. The installation progress displays. 10. 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
where install_root represents the root directory of your IBM Director installation. 11. To start IBM Director, type the following command and press Enter: install_root/bin/twgstart
60
IBM Director Express Planning, Installation and Configuration Guide
12. If you used a 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. 13. If you used a CD, remove the CD from the drive. Note: (AIX and Linux only) If you log into IBM Director Console using the root account, all the IBM Director tasks for a Standard installation are displayed.
Installing IBM Director Server on Linux for System x using the Express installation option After preparing your server, you can use the Express installation option to install IBM Director Server on Linux for System x. To perform an Express installation, you must run the dirinstall script against a response file in which the ExpressInstall parameter is enabled. Important: v IBM Director Server and IBM Director Console must be at the same release level. If you install IBM Director Server, version 5.20 on the management server, you must also install IBM Director Console, version 5.20 on any systems that you want to access the management server. In addition, 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. Management servers running i5/OS, IBM Director Server use the DB2 database. On all other operating systems, the default database is Apache Derby, but other databases can be used. v 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. On management servers running i5/OS, however, IBM Director Server does not include IBM Director Console. 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 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. To use the Express installation option to install IBM Director Server on Linux for System x, complete the following steps: 1. To install IBM Director Server from a Web download, perform the following steps: Chapter 4. Installing IBM Director using the Express installation
61
a. Download the dir5.20_server_linux.tar file from the IBM Director downloads page at: www.ibm.com/systems/management/director/ downloads.html. b. Extract the contents of the dir5.20_server_linux.tar file into a local directory. c. To change to the directory in which IBM Director Server is located, type the following command and press Enter: cd /directory/director/server/linux/i386/
where directory is the local directory into which you extracted the files. Go to step 5. 2. To install IBM Director Server from a CD, insert the IBM Director on x86, V5.20 CD into the drive. 3. If the CD automounts, go to step 4. If the CD does not automount, 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. 4. 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. 5. Type the following command and press Enter to copy the response file (dirserv.rsp) to a local directory : cp dirserv.rsp /directory
where directory is the local directory. 6. Use an ASCII text editor to open the copy of the response file, and change the value of the ExpressInstall parameter to 1. In the response file, ″1″ indicates that an item is to be installed and ″0″ indicates that an item is not to be installed. 7. Save the modified response file. 8. Type the following command and press Enter: ./dirinstall -r /directory/response.rsp
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 7. 9. The License Agreement message is displayed. If you agree with the terms, proceed with the installation. Otherwise, cancel the installation. The installation progress displays. 10. 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
where install_root represents the root directory of your IBM Director installation. 11. To start IBM Director, type the following command and press Enter: install_root/bin/twgstart
12. If you used a CD, unmount the drive by completing the following steps:
62
IBM Director Express Planning, Installation and Configuration Guide
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. 13. If you used a CD, remove the CD from the drive. Note: (AIX and Linux only) If you log into IBM Director Console using the root account, all the IBM Director tasks for a Standard installation are displayed.
Installing IBM Director Server on Linux for System z using the Express installation option After preparing your server, you can use the Express installation option to install IBM Director Server on Linux for System z. To perform an Express installation, you must run the dirinstall script against a response file in which the ExpressInstall parameter is enabled. Important: v IBM Director Server and IBM Director Console must be at the same release level. If you install IBM Director Server, version 5.20 on the management server, you must also install IBM Director Console, version 5.20 on any systems that you want to access the management server. In addition, 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. Management servers running i5/OS, IBM Director Server use the DB2 database. On all other operating systems, the default database is Apache Derby, but other databases can be used. v 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. On management servers running i5/OS, however, IBM Director Server does not include IBM Director Console. 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 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. To use the Express installation option to install IBM Director Server on Linux for System z, complete the following steps: 1. Make available to your Linux system the installation code from the IBM Director for Linux on System z, V5.20 CD. You can obtain an ISO image of this
Chapter 4. Installing IBM Director using the Express installation
63
CD from ShopzSeries at www.ibm.com/software/ShopzSeries or from the IBM Director Web site at www.ibm.com/systems/management/director/ . 2. Change to the directory where the installation script is located. Type the following command and press Enter: cd /mnt/director/server/linux/s390/
where /mnt is the mount point of the file system on the CD or the location of the IBM Director installation files. 3. Type the following command and press Enter to copy the response file (dirserv.rsp) to a local directory: cp dirserv.rsp /directory
where directory is the local directory. 4. Use an ASCII text editor to open the copy of the response file, and change the value of the ExpressInstall parameter to 1. In the response file, ″1″ indicates that an item is to be installed and ″0″ indicates that an item is not to be installed. 5. Save the modified response file. 6. Type the following command and press Enter: ./dirinstall -r /directory/response.rsp
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 5. 7. Optional: Configure IBM Director for use with a database application. See “Configuring the database on Linux or AIX” in the IBM Director Systems Management Guide for more information. 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. 8. The License Agreement message is displayed. If you agree with the terms, proceed with the installation. Otherwise, cancel the installation. The installation progress displays. 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: install_root/bin/cfgsecurity
where install_root represents the root directory of your IBM Director installation. 10. To start IBM Director, type the following command and press Enter: install_root/bin/twgstart
Note: (AIX and Linux only) If you log into IBM Director Console using the root account, all the IBM Director tasks for a Standard installation are displayed.
64
IBM Director Express Planning, Installation and Configuration Guide
Adding Standard installation options to an IBM Director Express installation If you use the IBM Director Express installation option to install IBM Director Server, a subset of IBM Director tasks are enabled by default. You can configure IBM Director Server to enable all the tasks that would have been displayed with a Standard installation. 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. Note: (AIX and Linux only) If you log into IBM Director Console using the root account, all the IBM Director tasks for a Standard installation are displayed. To add the Standard installation options to an IBM Director Express installation, complete the following steps: 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. 4. 5. 6. 7.
Note: If the Groups tab does not display, you must first create and authorize a user group on the management server. Select the group for which you want to enable the IBM Director tasks. Click Actions → Group → Edit. In the Group Editor window, click the Task Access tab to modify task access for the user group. To allow full access to all tasks, clear Limit user access only to the tasks selected. In the Group Editor window, click OK and then close the User Administration window.
Chapter 4. Installing IBM Director using the Express installation
65
66
IBM Director Express Planning, Installation and Configuration Guide
Chapter 5. 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 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. On management servers running i5/OS, however, IBM Director Server does not include IBM Director Console. 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 server. v IBM Director Server and IBM Director Console must be at the same release level. If you install IBM Director Server, version 5.20 on the management server, you must also install IBM Director Console, version 5.20 on any systems that you want to access the management server. In addition, 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 install IBM Director Console on AIX, complete the following steps: 1. To install IBM Director Console from a Web download, perform the following steps: a. Download the IBM Director for AIX - Version 5.20 (Dir5.20_AIX.tar.gz) file to a local directory from the IBM Director downloads page at: www.ibm.com/systems/management/director/downloads.html. b. To unzip and extract the contents of the Dir5.20_AIX.tar.gz file, type the following command: © Copyright IBM Corp. 1999, 2006
67
gzip -cd Dir5.20_AIX.tar.gz | tar -xvf -
Go to step 3. 2. To install IBM Director Console from the CD, perform the following steps: a. Insert the IBM Director for AIX 5L, V5.20 or the IBM Director for i5/OS, V5.20 CD into the drive. b. To mount the drive, 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 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. 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. 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. 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: ./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. 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.
68
IBM Director Express Planning, Installation and Configuration Guide
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. To install IBM Director Console on Linux for System x, complete the following steps: 1. To install IBM Director Console from a Web download, perform the following steps: a. Download the dir5.20_console_linux.tar file from the IBM Director Support Web site at www.ibm.com/systems/management/director/ . b. Extract the contents of the dir5.20_console_linux.tar file into a local directory. c. Change to the directory in which the installation script is located. Type the following command and press Enter: cd /directory/
where directory is the local directory into which you extracted the files. d. If you want to customize the installation, go to step 1e. If you want to accept the default settings for the installation, type the following command and press Enter: ./dir5.20_console_linux.sh
e. 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. f. 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. g. Save the modified response file. h. To install IBM Director Console using the response file, type the following command and press Enter: ./dir5.20_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 IBM Director on x86, V5.20 or IBM Director Agents & Consoles, V5.20 (2 of 2) CD into the drive. b. If the CD automounts, go to step 2c. If the CD does not automount, 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/console/linux/i386
Chapter 5. Installing IBM Director Console
69
where mnt/cdrom is the mount point of the drive. Go to step 2d. d. If you want to customize the installation, go to step 2e. If you want to accept the default settings for the installation, type the following command and press Enter: ./dirinstall
Go to step 2i. e. 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. f. 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. g. Save the modified response file with a new file name. h. To install IBM Director Console using the modified response file, type the following command and press Enter: ./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 saved in step 2g. i. To unmount the drive, complete the following steps: 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. j. Remove the CD from the drive.
Installing IBM Director Console on Linux for System z This topic describes how to install IBM Director Console on Linux for System z. Complete the following steps to install IBM Director Console on Linux for System z: 1. Make the installation code available to your Linux system. You can obtain the installation code: v From the IBM Director for Linux on System z, V5.20 CD v From the IBM Director Agents & Consoles, V5.20 (2 of 2) CD You can obtain ISO images of these CDs from ShopzSeries at www.ibm.com/software/ShopzSeries or from the IBM Director Web site at www.ibm.com/systems/management/director/ . See “Preparing to install IBM Director Server on Linux for System z ” on page 47 for more information. 2. Change to the directory in which the installation script is located. Type the following command and press Enter: cd /mnt/director/console/linux/s390/
70
IBM Director Express Planning, Installation and Configuration Guide
where /mnt is the mount point of the file system on the CD or the location of the IBM Director installation files. 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
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 9. 4. 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. 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 and select log file options. 6. Save the modified response file with a new file name. 7. To install IBM Director Console, 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. 8. Optional: Keep the response file for future use and reference. 9. 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 for POWER To install IBM Director Console on a system that is running Linux for 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. To install IBM Director Console on Linux for POWER, complete the following steps: 1. To install IBM Director Console from a Web download, perform the following steps: a. Download the Dir5.20_LinuxonPower.tar.gz file from the IBM Director Web site at: www.ibm.com/systems/management/director/ . b. To unzip and extract the contents of the Dir5.20_LinuxonPower.tar.gz file, type the following command: gzip -cd Dir5.20_LinuxonPower.tar.gz | tar -xvf -
Go to step 3 on page 72. 2. To install IBM Director Console from the CD, perform the following steps: a. Insert the IBM Director for Linux on POWER, V5.20 or IBM Director for i5/OS, V5.20 CD into the drive. b. If the CD automounts, go to step 2c on page 72. If the CD does not automount, type the following command and press Enter: Chapter 5. Installing IBM Director Console
71
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/console/linux/ppc
where mnt/cdrom 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
Go to step 8. 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
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. 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. 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
72
IBM Director Express Planning, Installation and Configuration Guide
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 change to the directory containing the ibmsetup.exe file and run the installation program using the following command: ibmsetup.exe admin
This command updates MSI and runs the installation program in administrative mode. Restart the system if prompted to do so.
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. To install IBM Director Console on Windows, complete the following steps: 1. To start the installation from a Web download, perform the following steps: a. Download the dir5.20_console_windows.zip file from the IBM Director downloads page at:www.ibm.com/systems/management/director/ downloads.html. b. Extract the contents of the dir5.20_console_windows.zip file into a local directory. c. Locate the dir5.20_console_windows.exe file and double-click it. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Console window opens. Go to step 4 on page 74. 2. Optional: (i5/OS only) To start the installation from the IBM Director Agents & Consoles, V5.20 (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 74. 3. To start the installation from the CD, perform the following steps: a. Insert the IBM Director on x86, V5.20 CD into the 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 74. 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. Chapter 5. Installing IBM Director Console
73
c. Browse to the director/console/windows/i386 directory on the IBM Director on x86, V5.20. 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. 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 dir5.20_console_windows.zip file from the IBM Director downloads page at:www.ibm.com/systems/management/director/ downloads.html. b. Extract the contents of the dir5.20_console_windows.zip file into a local directory. c. Locate and copy the dircon.rsp file. d. Go to step 3 on page 75. 2. Insert the IBM Director on x86, V5.20 or IBM Director Agents & Consoles, V5.20 (2 of 2)CD into the drive. a. If the installation program starts automatically and the IBM Director Setup window opens, close it.
74
IBM Director Express Planning, Installation and Configuration Guide
b. Copy the dircon.rsp file to a local directory. This file is in the director\console\windows\i386 directory on the CD. c. Go to step 3. 3. Open the copy of the dircon.rsp file in an ASCII text editor. 4. 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. 5. 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. 6. 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 4. v option is one of the following optional parameters: Table 30. Optional installation parameters Parameter
What it does
waitforme
Ensures that ibmsetup.exe process will not end until the installation of IBM Director Console is completed
debug
Logs all messages that are sent by the Microsoft Windows Installer log engine, including status and information messages
log=logfilename
Specifies the fully qualified name of an alternative log file
verbose
Enables verbose logging
7. If you installed IBM Director Console from the CD, remove the CD from the drive when the installation is completed.
Chapter 5. Installing IBM Director Console
75
76
IBM Director Express Planning, Installation and Configuration Guide
Chapter 6. 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. To install Level 1: IBM Director Core Services on Linux for System x, complete the following steps: 1. To start the installation from a Web download, perform the following steps: a. Download the dir5.20_coreservices_linux.tar file from the IBM Director Web site at www.ibm.com/systems/management/director/ . b. Extract the contents of the dir5.20_coreservices_linux.tar file into a local directory. c. Change to the directory in which the installation script is located. Type the following command and press Enter: cd /directory/FILES
where directory is the local directory into which you extracted the files. Go to step 3. 2. To start the installation from the CD, perform the following steps: a. Insert the IBM Director on x86, V5.20 or IBM Director Agents & Consoles, V5.20 (1 of 2) CD into the drive. b. If the CD automounts, go to step 2c. If the CD does not automount, 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/coresvcs/agent/linux/i386/FILES
where mnt/cdrom 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: ./dir5.20_coreservices_linux.sh
If you are installing from the CD, go to step 8 on page 78. If you are installing from a Web download, the installation is completed. 4. To customize the installation, copy the response file (coresvcs.rsp) to a local directory. Type the following command and press Enter: © Copyright IBM Corp. 1999, 2006
77
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 Level 1: IBM Director Core Services using the response file, type the following command and press Enter: ./dir5.20_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 saved in step 6. 8. If you installed IBM Director Core Services from the CD, complete 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. 9. Remove the CD from the drive. 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 To install Level 1: IBM Director Core Services on a system that is running Linux for System z, download the installation files Web or use the CD. You can perform a standard installation or you can use a response file to customize the installation for your environment. To install Level 1: IBM Director Core Serviceson Linux for System z, complete the following steps: 1. Make the installation code available to your Linux system. You can obtain the installation code: v From the IBM Director for Linux on System z, V5.20 CD. v From the IBM Director Agents & Consoles, V5.20 (1 of 2) CD. You can obtain ISO images of these CDs from ShopzSeries at www.ibm.com/software/ShopzSeries or from the .IBM Director Web site at www.ibm.com/systems/management/director/ . 2. 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 the location of the IBM Director installation files.
78
IBM Director Express Planning, Installation and Configuration Guide
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: ./csversion_agent_linz.sh
csversion is a prefix “cs” followed by the product version number. For version 5.20, the file name would be cs5.20_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. Go to step 9. 4. To customize the installation, 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. 5. Open an ASCII text editor and modify the installation settings in the copy of the coresvcs.rsp file. This file is fully commented. 6. Save the modified response file with a new file name. 7. 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 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. 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: /opt/ibm/director/bin/cfgsecurity
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 for POWER To install IBM Director Core Services on a system that is running Linux for 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. To install Level 1: IBM Director Core Services on Linux for POWER, complete the following steps: 1. To install IBM Director Core Services from a Web download, perform the following steps: a. Download the IBM Director for Linux on POWER - Version 5.20 (Dir5.20_LinuxonPower.tar.gz) file to a local directory from the IBM Director Web site at: www.ibm.com/systems/management/director/ . b. To unzip and extract the contents of the Dir5.20_LinuxonPower.tar.gz file, type the following command: gzip -cd Dir5.20_LinuxonPower.tar.gz | tar -xvf Chapter 6. Installing Level 1: IBM Director Core Services
79
Go to step 3. 2. To start the installation from the CD, perform the following steps: a. Insert the IBM Director for Linux on POWER, V5.20 or IBM Director for AIX 5L, V5.20 CD into the drive. b. If the CD automounts, go to step 2c. If the CD does not automount, 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/coresvcs/agent/linux/ppc/FILES
where mnt/cdrom 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: ./cs5.20_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 the following command and press Enter: ./cs5.20_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: 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.
80
IBM Director Express Planning, Installation and Configuration Guide
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. 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 change to the directory containing the dir5.20_coreservices_windows.exe file and run the installation program using the following command: dir5.20_coreservices_windows.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 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. To use the InstallShield wizard to install Level 1: IBM Director Core Services on Windows, complete the following steps: 1. To start the installation from a Web download, perform the following steps: a. Download the dir5.20_coreservices_windows.zip file from the IBM Director Support Web site at www.ibm.com/systems/management/director/ . b. Extract the contents of the dir5.20_coreservices_windows.zip file to a local directory. c. Locate the dir5.20_coreservices_windows.exe file and double-click it. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Core Services window opens. Go to step 4 on page 82. 2. Optional: To start the installation from the CD if you are using the IBM Director Agents & Consoles, V5.20 (1 of 2) CD, insert the CD into the drive. Browse to the coresvcs\agent\windows\i386\FILES directory and double-click dir5.20_coreservices_windows.exe. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Core Services window opens. Continue to step 4 on page 82. 3. To start the installation from the CD, perform the following steps: a. Insert the IBM Director on x86, V5.20 into the drive. b. If the installation program starts automatically and the IBM Director Setup window opens, go to step 3d on page 82. Otherwise, click Start → Run. c. In the Open field, type the following command and press Enter: e:\setup.exe
Chapter 6. Installing Level 1: IBM Director Core Services
81
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 InstallShield wizard starts, and the Welcome to the InstallShield Wizard for Core Services window opens. Continue to step 4. 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, V5.20.
4. 5.
6. 7. 8. 9.
d. Run the dir5.20_coreservices_windows.exe program. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Core Services window opens. Continue to step 4. Click Next. The License Agreement window opens. 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. Click Next. The Ready to Install the Program window opens. Click Install. The status bar displays the progress of the installation. When the installation is completed, the InstallShield Wizard Completed window opens. Click Finish. 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. To use a response file to install Level 1: IBM Director Core Services on Windows, complete the following steps: 1. To start the installation from a Web download, perform the following steps: a. Download the dir5.20_coreservices_windows.zip file from the IBM Director Support Web site at www.ibm.com/systems/management/director/ . b. Extract the contents of the dir5.20_coreservices_windows.zip file into a local directory. c. Locate and copy the coresvcs.rsp file. This file is in the local\FILES directory where local is the local directory into which you extracted the contents of the dir5.20_coreservices_windows.zip file. d. Go to step 3 on page 83. 2. Insert the IBM Director on x86, V5.20 or IBM Director Agents & Consoles, V5.20 (1 of 2) CD into the drive.
82
IBM Director Express Planning, Installation and Configuration Guide
3. 4. 5. 6.
a. If the installation program starts automatically and the IBM Director Setup window opens, close it. b. Copy the response file (coresvcs.rsp) to a local directory. This file is in the coreservices\agent\windows\i386\FILES directory on the CD. c. Go to step 3. Open the copy of the coresvcs.rsp file in an ASCII text editor. Modify and save the response file with a new file name. This file follows the Windows INI file format and is fully commented. Open a command prompt and change to the directory that contains the IBM Director Core Services installation file (dir5.20_coreservices_windows.exe). From the command prompt, type the following command (all on one line) and press Enter: dir5.20_coreservices_windows.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 4. v option is one of the following optional parameters: Table 31. Optional installation parameters Optional parameter
What it does
waitforme
Ensures that dir5.20_coreservices_windows.exe process will not end until the installation of IBM Director Core Services is completed
debug
Logs all messages that are sent by the Microsoft Windows Installer log engine, including status and information messages
log=logfilename
Specifies the fully qualified name of an alternative log file
verbose
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.
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.
Chapter 6. Installing Level 1: IBM Director Core Services
83
The following files describe IBM Director Core Services: v dir5.20_coreservices_linux.xml This file is located in the coresvcs/agent/linux/i386/META-INF directory on the IBM Director on x86, V5.20 and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v cs5.20_agent_linppc.xml This file is located in the coresvcs/agent/linux/ppc/META-INF directory on the IBM Director for AIX 5L, V5.20 and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v cs5.20_agent_linz.xml This file is located in the coresvcs/agent/linux/s390/META-INF/ directory on the IBM Director for Linux on System z, V5.20 and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v dir5.20_coreservices_windows.xml This file is located in the coresvcs\agent\windows\i386\META-INF directory on the IBM Director on x86, V5.20 and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. (System x ; Windows only) The following file describes both IBM Director Core Services and OpenSSH: v dir5.20_coreservices-toc_windows.xml This file is located in the coresvcs directory on the IBM Director on x86, V5.20 CD. When the dir5.20_coreservices-toc_windows.xml file is imported by the IBM Update Assistant, a software-distribution category containing both IBM Director Core Services and OpenSSH is created, allowing them both to be installed at the same time. The OpenSSH package can be used to provide a secure remote interface between a Level-1 managed system and IBM Director Server. Use the OpenSSH interface to run the Remote Session task or the cimsubscribe utility from IBM Director Server. The cimsubscribe utility provides a command-line interface for creating event subscriptions. (System x only) The following files describe the IBM LM78 device driver and the IBM SMBus device driver: v lm78driver_linux.xml v smbdriver_linux.xml You can download these files from the IBM Director Web site at www.ibm.com/systems/management/director/ . They are included in the .gz files containing the device drivers to which they apply. When you import the XML files into IBM Director, the IBM Update Assistant creates software packages. Then, you can use the IBM Director Software Distribution task to distribute the packages to the managed systems. 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 smbdriver_linux.xml file. Note: If an earlier version of the IBM LM78 or SMBus device driver for Linux is installed on the managed system, you must uninstall the device driver before installing version 5.20 of the driver.
84
IBM Director Express Planning, Installation and Configuration Guide
Related reference “IBM LM78 and SMBus device drivers for Linux” on page 43 This topic describes when to install the LM78 and SMBus device drivers for Linux.
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.
Figure 5. Creating a software package: Software Distribution Manager window (Standard Edition)
Figure 6. Creating a software package: Software Distribution Manager window (Premium Edition)
Chapter 6. Installing Level 1: IBM Director Core Services
85
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 85. 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.
86
IBM Director Express Planning, Installation and Configuration Guide
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.
Chapter 6. Installing Level 1: IBM Director Core Services
87
88
IBM Director Express Planning, Installation and Configuration Guide
Chapter 7. 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. 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. To install Level 2: IBM Director Agent on AIX, complete the following steps: 1. To install IBM Director Agent from a Web download, perform the following steps: a. Download the IBM Director for AIX - Version 5.20 (Dir5.20_AIX.tar.gz) file to a local directory from the IBM Director downloads page at: www.ibm.com/systems/management/director/downloads.html. b. To unzip and extract the contents of the Dir5.20_AIX.tar.gz file, type the following command: gzip -cd Dir5.20_AIX.tar.gz | tar -xvf -
Go to step 3 on page 90. 2. To start the installation from the CD, perform the following steps: a. Insert the IBM Director for AIX 5L, V5.20 CD or the IBM Director for Linux on POWER, V5.20 CD into the drive. © Copyright IBM Corp. 1999, 2006
89
b. If the CD automounts, go to step 2c. If the CD does not automount, type the following command and press Enter: mount /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. 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. 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.20_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: install_root/bin/cfgsecurity
where install_root is the root directory of your IBM Director installation. 9. To startIBM Director Agent, type the following command and press Enter: install_root/bin/twgstart
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.
90
IBM Director Express Planning, Installation and Configuration Guide
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. 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 IBM Director for i5/OS, V5.20 CD into the CD or DVD device. Note: As an alternative, you can use IBM Director Software Distribution to distribute IBM Director Agent to your managed systems. 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 IBM Director Agent using the Virtualization Engine This topic describes how you can install IBM Director Agent using the Remote Package Deployer, a part of the Virtualization Engine™. Before you distribute IBM Director Agent, you must have installed IBM Director Server along with IBM Director Agent images on your management server.
Using Remote Package Deployer You can install IBM Director Agent, Directori5OSRPD_agentpackagedIU.xml, from a command line using Remote Package Deployer (RPD). The default location for this file on the management server is at /QIBM/ProdData/VE2/ManagedNodes/ Directori5OS/META-INF. With RPD you must install IBM Director Agent to one system at a time. Refer to the instructions in the Virtualization Engine topic, Distributing agent software without IBM Director.
Chapter 7. Installing Level 2: IBM Director Agent
91
Installing IBM Director Agent on i5/OS using RSTLICPGM You can install IBM Director Agent on i5/OS using the Restore Licensed Program (RSTLICPGM) command. 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 IBM Director for i5/OS, V5.20 CD into the CD or DVD device. Note: As an alternative, you can use IBM Director Software Distribution to distribute IBM Director Agent to your managed systems. 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 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. To install Level 2: IBM Director Agent on Linux for System x, complete the following steps: 1. To start the installation from a Web download, perform the following steps: a. Download the dir5.20_agent_linux.tar file from the IBM Director Support Web site at www.ibm.com/systems/management/director/ . b. Extract the contents of the dir5.20_agent_linux.tar file into a local directory. c. Change to the directory in which the installation script is located. Type the following command and press Enter: cd /directory/FILES
where directory is the local directory into which you extracted the files. Go to step 3 on page 93.
92
IBM Director Express Planning, Installation and Configuration Guide
2. To start the installation from the CD, perform the following steps: a. Insert the IBM Director on x86, V5.20 or IBM Director Agents & Consoles, V5.20 (1 of 2) CD into the drive. b. If the CD automounts, go to step 2c. If the CD does not automount, 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/agent/linux/i386/FILES
where mnt/cdrom 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: ./dir5.20_agent_linux.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. 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_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: 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
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: install_root/bin/twgstart
10. If you installed IBM Director Agent from the CD, complete 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 CD-ROM drive. Remove the CD from the drive. Chapter 7. Installing Level 2: IBM Director Agent
93
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 Level 2: IBM Director Agent on a Linux for System z platform by downloading the installation file or using the CD. 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. Make the installation code available to your Linux system. You can obtain the installation code: v From the IBM Director for Linux on System z, V5.20 CD. v From the IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v As a Web download from www.ibm.com/systems/management/director/ . 2. 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 location of the IBM Director installation files. 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: ./dirversion_agent_linz.sh
dirversion is a prefix “dir” followed by the product version number. For version 5.20, the file name would be dir5.20_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 9 on page 95. 4. To customize the installation, copy the response file to a local directory. Type the following command and press Enter: cp diragent.rsp /directory
94
IBM Director Express Planning, Installation and Configuration Guide
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: ./dirversion_agent_linz.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: install_root/bin/cfgsecurity
where install_root is the root directory of your IBM Director installation. 9. To start IBM Director Agent, begin a new terminal session, type the following command, and press Enter: install_root/bin/twgstart
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 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 install Level 2: IBM Director Agent on Linux for POWER, complete the following steps: 1. To install IBM Director Agent from a Web download, perform the following steps: a. Download the Dir5.20_LinuxonPower.tar.gz file from the IBM Director Web site at www.ibm.com/systems/management/director/ . b. To unzip and extract the contents of the Dir5.20_LinuxonPower.tar.gz file, type the following command: gzip -cd Dir5.20_LinuxonPower.tar.gz | tar -xvf -
Go to step 3 on page 96. 2. To start the installation from the CD, perform the following steps: Chapter 7. Installing Level 2: IBM Director Agent
95
a. Insert the IBM Director for AIX 5L, V5.20 or IBM Director for Linux on POWER, V5.20 CD into the drive. b. If the CD automounts, go to step 2c. If the CD does not automount, 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/agent/linux/ppc/FILES
where mnt/cdrom 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: ./dir5.20_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: 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 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.20_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: install_root/bin/cfgsecurity
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: install_root/bin/twgstart
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.
96
IBM Director Express Planning, Installation and Configuration Guide
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 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: 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 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: install_root/bin/twgstart
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.
Chapter 7. Installing Level 2: IBM Director Agent
97
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. 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
98
IBM Director Express Planning, Installation and Configuration Guide
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. 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. 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 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 change to the directory containing the dir5.20_agent_windows.exe file and run the installation program using the following command: dir5.20_agent_windows.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 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.
Chapter 7. Installing Level 2: IBM Director Agent
99
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 dir5.20_agent_windows.zip file from theIBM Director Support Web site at www.ibm.com/systems/management/director/ . b. Extract the contents of the dir5.20_agent_windows.zip file into a local directory. c. Locate the dir5.20_agent_windows.exe file and double-click it. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Agent window opens. Go to step 4. 2. Optional: To start the installation from the CD if you are using the IBM Director Agents & Consoles, V5.20 (1 of 2) CD, insert the CD into the drive. Browse to the director\agent\windows\i386\FILES directory and double-click dir5.20_agent_windows.exe. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Agent window opens. Continue to step 4. 3. To start the installation from the CD, perform the following steps: a. Insert the IBM Director on x86, V5.20 CD into the 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 InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Agent window opens. Continue 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, V5.20. d. Run the dir5.20_agent_windows.exe program. The InstallShield wizard starts, and the Welcome to the InstallShield Wizard for IBM Director Agent window opens. Continue 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 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
100
IBM Director Express Planning, Installation and Configuration Guide
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.
9.
10.
11.
12. 13.
14.
15.
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>::, 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. 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.
Chapter 7. Installing Level 2: IBM Director Agent
101
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.
17. 18. 19. 20.
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. Click OK. The status bar displays the progress of the installation. When the installation is completed, the InstallShield Wizard Completed window opens. Click Finish. If you installed IBM Director Agent from the CD, remove the CD from the drive. 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. 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 dir5.20_agent_windows.zip file from theIBM Director Web site at www.ibm.com/systems/management/director/ . b. Extract the contents of the dir5.20_agent_windows.zip file into a local directory. c. Locate and copy the diragent.rsp file. This file is in the local\FILES directory where local is the local directory to which you extracted the contents of the dir5.20_agent_windows.zip file. d. Go to step 3. 2. Insert the IBM Director on x86, V5.20 or IBM Director Agents & Consoles, V5.20 (1 of 2) CD into the drive. a. If the installation program starts automatically and the IBM Director Setup window opens, close it. b. Copy the diragent.rsp file to a local directory. This file is located in the director\agent\windows\i386\FILES directory on the CD. c. Go to step 3. 3. Open the copy of the diragent.rsp file in an ASCII text editor. 4. Modify and save the diragent.rsp file with a new file name. This file follows the Windows INI file format and is fully commented.
102
IBM Director Express Planning, Installation and Configuration Guide
5. Open a command prompt and change to the directory that contains the Level 2: IBM Director Agent installation file (dir5.20_agent_windows.exe). 6. From the command prompt, type the following command and press Enter: dir5.20_agent_windows.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 saved in step 4 on page 102. v option is one of the following optional parameters: Table 32. Optional installation parameters Parameter
What it does
waitforme
Ensures that dir5.20_agent_windows.exe process will not end until the installation of IBM Director Agent is completed
debug
Logs all messages that are sent by the Microsoft Windows Installer log engine, including status and information messages
log=logfilename
Specifies the fully qualified name of an alternative log file
verbose
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 Chapter 7. Installing Level 2: IBM Director Agent
103
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. 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>::, for example, TCPIP::10.3.1.4, TCPIP::192.168-1.10.
104
IBM Director Express Planning, Installation and Configuration Guide
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. 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.
Chapter 7. Installing Level 2: IBM Director Agent
105
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. 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. v option is one of the following optional parameters: Table 33. Optional installation parameters Parameter
What it does
waitforme
Ensures that dir5.10.3_agent_windows64.exe process will not end until the installation of IBM Director Agent is completed
debug
Logs all messages that are sent by the Microsoft Windows Installer log engine, including status and information messages
log=logfilename
Specifies the fully qualified name of an alternative log file
verbose
Enables verbose logging
8. If you set the RebootIfRequired parameter to Y in the response file, reboot the system if prompted to do so.
106
IBM Director Express Planning, Installation and Configuration Guide
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: v dir5.20_agent_aix.xml This file is located in the director/agent/aix/META-INF directory on the IBM Director for AIX 5L, V5.20 IBM Director for Linux on POWER, V5.20, and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v dir5.20_agent_linux.xml This file is located in the director/agent/linux/i386/META-INF directory on the IBM Director on x86, V5.20 and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v dir5.20_agent_linppc.xml This file is located in the director/agent/linux/ppc/META-INF directory on the IBM Director for AIX 5L, V5.20, IBM Director for Linux on POWER, V5.20, and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v dir5.20_agent_linz.xml This file is located in the director/agent/linux/s390/META-INF/ directory on the IBM Director for Linux on System z, V5.20 and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v dir5.20_agent_windows.xml This file is located in the director\agent\windows\i386\META-INF directory on the IBM Director on x86, V5.20 and IBM Director Agents & Consoles, V5.20 (1 of 2) CD. v Directori5OSRPD_agentpackagedIU.xml The default location for this file on an i5/OS management server, if you have selected to install the IBM Director Agent images, is at /QIBM/ProdData/VE2/ ManagedNodes/Directori5OS/META-INF. If you have not installed IBM Director Server for i5/OS, this file is included on the IBM Director Agents & Consoles, V5.20 (1 of 2)CD. You can access it from the \FILES\Director directory, in the Directori5OSAgent.zip file. IBM Director 5.20 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. The following files describe the 64-bit, Intel Itanium versions of the IBM Director Agent: v dir5.10.3_agent_linux64.xml v dir5.10.3_agent_windows64.xml (System x only) The following files describe the IBM LM78 and IBM SMBus device drivers: v lm78driver_linux.xml v smbdriver_linux.xml
Chapter 7. Installing Level 2: IBM Director Agent
107
You can download these files from the IBM Director Support Web site at www.ibm.com/systems/management/director/ . They are included in the .zip or .gz packages for the component or device driver to which they apply. When you import the XML files into IBM Director, the IBM Update Assistant creates software packages. Then, you can use the IBM Director Software Distribution task to distribute the packages to the managed systems. 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 lm78driver_linux.xml or smbdriver_linux.xml file. Note: If an earlier version of the IBM LM78 or SMBus device driver for Linux is installed on the managed system, you must uninstall the device driver before installing version 5.20 of the driver. Related reference “IBM LM78 and SMBus device drivers for Linux” on page 43 This topic describes when to install the LM78 and SMBus device drivers for Linux.
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.
Figure 7. Creating a software package: Software Distribution Manager window (Standard Edition)
108
IBM Director Express Planning, Installation and Configuration Guide
Figure 8. 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 108. 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.
Chapter 7. Installing Level 2: IBM Director Agent
109
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.
110
IBM Director Express Planning, Installation and Configuration Guide
Chapter 8. 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.
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.
3.
4. 5. 6. 7.
8. 9.
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.
© Copyright IBM Corp. 1999, 2006
111
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. 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. b. c. d.
Select the location where the program should be started. Type the Host name of the selected system. Type the working directory of the program that needs to start. Type the Program name of the application that needs to start.
13. Click Next. 14. 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. 15. Click Next. 16. On the Summary page, verify the details of the event action plan. If you need to make changes, click < Back. 17. Click Finish.
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.
112
IBM Director Express Planning, Installation and Configuration Guide
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.
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.
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 (/). 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.
Chapter 8. Initially configuring IBM Director
113
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:
Set the ldap.auth.jndi property to:
IBM Director Server on i5/OS
true
IBM Director Server on AIX, and not using Pluggable Authentication Module (PAM) authentication.
true
IBM Director Server on Linux, and not using Pluggable Authentication Module (PAM) authentication.
true
IBM Director Server on Windows, and using an LDAP server other than Active Directory.
true
All other conditions.
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.
dn
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
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
7. 8.
9. 10.
anonymous DIGEST-MD5 Set the ldap.enabled property to true. You might have to add the ldap.enabled property to the dirldap.properties file. Optional: Modify other properties in the dirldap.properties file as needed. These properties are described in Appendix B, “Lightweight Directory Access Protocol authentication properties for IBM Director Server,” on page 159. Save and close the changed dirldap.properties file. 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.”
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.
114
IBM Director Express Planning, Installation and Configuration Guide
Note: A high-availability application is required for implementation of IBM Director high-availability configuration. For management servers running Linux, you might consider using IBM Tivoli System Automation for Multiplatforms. For management servers running Windows, you might consider using SteelEye’s 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, 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/Apache Derby). This database should be configured for high availability as described in the database documentation. 4. Create a network share to use as the IBM Director Server data directory. a. Create the network share. The network share should be made highly available using RAID or another method. b. Copy the contents of install_root/data from one of the management servers to the network share. c. 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 (/). 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.
Chapter 8. Initially configuring IBM Director
115
Preparing a high-availability environment for IBM Director and SteelEye®’s LifeKeeper™ In order for IBM Director to provide high availability, 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/Apache Derby). This database should be configured for high availability as described in the database documentation. 4. Optional: Create a network share to use as the IBM Director Server data directory. a. Create the network share. The network share should be made highly available using RAID or another method. b. Copy the contents of install_root/data from one of the management servers to the network share. c. 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 (/).
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 SteelEye’s 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.
116
IBM Director Express Planning, Installation and Configuration Guide
This tradeoff is summarized in the following table. Configuration
Benefit
Cost
High-availability not enabled Improved performance. (default configuration).
Loss of data on failover.
High-availability enabled.
Decreased performance.
Minimal loss of data on failover.
Incomplete tasks restart from beginning.
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
Command
AIX, Linux, and Windows
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 (/).
i5/OS
Using an ASCII text editor, open the /QIBM/UserData/ Director/data/softwaredist/TWGServer.prop file.
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 118. 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. Chapter 8. Initially configuring IBM Director
117
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
Commands
AIX or Linux
install_root/bin/twgstop install_root/bin/twgstart
i5/OS
QSH CMD(’/QIBM/ProdData/Director/bin/twgstop’) QSH CMD(’/QIBM/ProdData/Director/bin/twgstart’)
NetWare
unload twgipc load twgipc
Windows
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.
118
IBM Director Express Planning, Installation and Configuration Guide
2. Click the BladeCenter Chassis 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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
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
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type.
1 - 240
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:
Complete these steps:
Add a predefined parameter
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% Chapter 8. Initially configuring IBM Director
119
v %MM_NAME% 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.
120
IBM Director Express Planning, Installation and Configuration Guide
To do this:
Complete these steps:
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. Select the entry to be changed in the Address Entries list. Click Edit. Change the field values for the entry. Click OK.
Change an existing address entry
1. 2. 3. 4.
Delete an existing address entry
1. Select the entry to be deleted in the Address Entries list. 2. Click Remove. 3. If prompted, click Yes.
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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
IBM Director Server automatically discovers managed systems every n hours, where n is the selected number.
5. 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
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type.
1 - 240
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.
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. Chapter 8. Initially configuring IBM Director
121
Configuring discovery preferences for Level-1 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. 3. Select a discovery method to use and complete the specified configuration steps. Discovery method
Steps
Use Service 1. Specify one or more SLP directory agent servers to use. The selected Location Protocol SLP directory agents are displayed in the Predefined directory agent (SLP) directory servers list box. agents 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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
IBM Director Server automatically discovers managed systems every n hours, where n is the selected number.
6. Click OK.
122
IBM Director Express Planning, Installation and Configuration Guide
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, 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-2 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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
IBM Director Server automatically discovers managed systems every n hours, where n is the selected number.
5. 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
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type.
1 - 240
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.
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.
Chapter 8. Initially configuring IBM Director
123
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. 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:
Complete these steps:
Add an address and mask for broadcast discovery
1. 2. 3. 4. 5.
Click Add. Click Broadcast. Click Next. Type values in the IP Address and Subnet Mask fields. Click OK.
Add an address and mask for broadcast relay discovery
1. 2. 3. 4. 5.
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
124
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.
IBM Director Express Planning, Installation and Configuration Guide
To do this:
Complete these steps:
Delete an existing address entry
1. Select the entry to be deleted in the Address Entries list. 2. Click Remove. 3. If prompted, click Yes.
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: 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. Select the entry to be changed in the Address Entries list. Click Edit. Change the field values for the entry. Click OK.
Change an existing address entry
1. 2. 3. 4.
Delete an existing address entry
1. Select the entry to be deleted in the Address Entries list. 2. Click Remove. 3. If prompted, click Yes.
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. Chapter 8. Initially configuring IBM Director
125
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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
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
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type. This is the default value for physical platforms.
1-240
IBM Director Server attempts to contact managed objects of this type every n minutes, where n is the selected number.
5. Specify a template for naming physical platforms that IBM Director Server discovers. To perform this action:
Complete these steps:
Add a predefined parameter
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 %SERVER_MACHINE_TYPE_MODEL% v %SERVER_SERIAL_NUMBER% v %SERVER_FRU% v %SP_FRU%
126
IBM Director Express Planning, Installation and Configuration Guide
v v v v v v v
%SP_SERIAL_NUMBER% %CHASSIS_SLOT% %CHASSIS_SLOT_RANGE% %CHASSIS_NAME% %SP_TEXT_ID% %SP_IP_ADDRESS% %SP_HOSTNAME%
v %SP_ASSET_TAG% v %DIR_AGENT_NAME% v %COMPUTER_NAME% 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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
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 Chapter 8. Initially configuring IBM Director
127
(minutes). Option
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type.
1 - 240
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. 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. To do this:
Complete these steps:
Add an SLP profile
1. In the Available Profiles list, click a profile to add. 2. Click Add.
Remove an SLP profile
1. In the Selected Profiles list, click a profile to remove. 2. Click Remove.
Restore the Selected Profiles list to the default values
Select the Reset to default value check box. If prompted, click Yes.
6. Select a discovery method to use and complete the specified configuration steps. Discovery method
Steps
Use Service 1. Specify one or more SLP directory agent servers to use. The selected Location Protocol SLP directory agents are displayed in the Predefined directory agent (SLP) directory servers list box. agents 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.
128
IBM Director Express Planning, Installation and Configuration Guide
7. 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. 8. 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
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
IBM Director Server automatically discovers managed systems every n hours, where n is the selected number.
9. Specify a template for naming SMI-S storage devices that IBM Director Server discovers. To perform this action:
Complete these steps:
Add a predefined parameter
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 %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.
Chapter 8. Initially configuring IBM Director
129
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. 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 Server’s 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
130
IBM Director Express Planning, Installation and Configuration Guide
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:
Complete these steps:
Add a new seed address for SNMP discovery
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.
Add a list of seed addresses from a text file
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.
Change an existing seed address
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.
Delete an existing seed address
1. Click the entry to be deleted in the IP Addresses and Subnet Masks list. 2. Click Remove. 3. If prompted, click Yes.
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.
Chapter 8. Initially configuring IBM Director
131
To do this:
Complete these steps:
Add a profile name
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.
Delete a profile name
1. Click the profile name to be deleted. 2. Click Remove. 3. If prompted, click Yes.
7. 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
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
IBM Director Server automatically discovers managed systems every n hours, where n is the selected number.
8. 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
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type.
1 - 240
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.
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.
132
IBM Director Express Planning, Installation and Configuration Guide
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. 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. Discovery method
Steps
Use Service 1. Specify one or more SLP directory agent servers to use. The selected Location Protocol SLP directory agents are displayed in the Predefined directory agent (SLP) directory servers list box. agents 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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
Chapter 8. Initially configuring IBM Director
133
Option
Description
1 - 168
IBM Director Server automatically discovers managed systems every n hours, where n is the selected number.
6. 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
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type.
1 - 240
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 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. 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.
134
IBM Director Express Planning, Installation and Configuration Guide
Discovery method
Steps
Use Service 1. Specify one or more SLP directory agent servers to use. The selected Location Protocol SLP directory agents are displayed in the Predefined directory agent (SLP) directory servers list box. agents 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). Option
Description
Disabled
IBM Director Server does not automatically discover managed systems. This value is the default.
1 - 168
IBM Director Server automatically discovers managed systems every n hours, where n is the selected number.
6. 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
Description
Disabled
IBM Director Server does not check the online status of managed objects of this type.
1 - 240
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.
Chapter 8. Initially configuring IBM Director
135
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 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 Console. Discovery of managed systems can take minutes or
136
IBM Director Express Planning, Installation and Configuration Guide
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. Chapter 8. Initially configuring IBM Director
137
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:
138
IBM Director Express Planning, Installation and Configuration Guide
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. Chapter 8. Initially configuring IBM Director
139
4. To add a share, click Add. 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 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
140
VMware ESX Server, version 3.0 Console
IBM Director Express Planning, Installation and Configuration Guide
Enabling SNMP access and trap forwarding for Linux managed systems 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.
Enabling SNMP access and trap forwarding for Red Hat Enterprise Linux versions 3 and 4 The OpenIPMI driver supported on Red Hat Enterprise Linux versions 3 and 4 has a dependency on the version of Net-SNMP that is included with those Linux distributions. IBM Director Core Services requires a different Net-SNMP version, 5.2.1. Installation of Net-SNMP 5.2.1 without removing the existing Net-SNMP version is required for IBM Director SNMP access and trap forwarding without compromising OpenIPMI services. Complete the following steps to enable SNMP access and trap forwarding for managed systems running Red Hat Enterprise Linux versions 3 and 4: 1. Download the net-snmp-5.2.1.tar.gz file from the Net-SNMP Web site at www.net-snmp.org/download.html. 2. Build and install the Net-SNMP libraries using the following steps. Notes: v This procedure does not perform a full installation of Net-SNMP, but installs only the Net-SNMP libraries, which are required for IBM Director Core Services SNMP functions. v Refer to the INSTALL and README files included in the net-snmp-5.2.1.tar.gz package for additional installation information. a. Untar the source files. Type the following command and press Enter. tar -xvzf net-snmp-5.2.1.tar.gz
b. Change to the source directory. Type the following command and press Enter. cd net-snmp-5.2.1
c. Build the Net-SNMP libraries with default options. Type the following commands (press Enter after each). ./configure --with-defaults make
d. Install the Net-SNMP libraries only to /usr/local/lib. Type the following command and press Enter. make installlibs
3. To enable trap forwarding, edit the /etc/init.d/dacimlist file and uncomment the following two lines two lines in the SNMP End Consumer section.
Chapter 8. Initially configuring IBM Director
141
LD_LIBRARY_PATH=/usr/local/lib export LD_LIBRARY_PATH
Note: The configuration changes will not take effect until you restart the cimlistener daemon in step 7. 4. To enable SNMP access, edit the /etc/init.d/dasnmp file and uncomment the following two lines in the section regarding the location of the net-snmp libraries. LD_LIBRARY_PATH=/usr/local/lib export LD_LIBRARY_PATH
5. Configure the SNMP daemon that ships with Red Hat Enterprise Linux to support AgentX agents. For details, see the documentation on the Net-SNMP Web Site. 6. Create the file /usr/local/share/snmp/snmpd.conf to specify trapsink and trapcommunity settings. You might have to create the directory. This file should contain only settings for trapcommunity and trapsink. a. Specify a trap community value by adding a line containing the word trapcommunity followed by a space and the trapcommunity value, as in the following example. trapcommunity public
b. Specify a trapsink value for each destination to which IBM Director will send SNMP traps. Add a line containing the word trapsink followed by a space and the trapsink value, as in the following example. trapsink 192.168.1.1
7. Restart the cimlistener daemon by typing the following commands and pressing Enter after each: /etc/init.d/dacimlist stop /etc/init.d/dacimlist start
8. Restart the IBM Director AgentX subagent by typing the following commands and pressing Enter after each: /etc/init.d/dasnmp stop /etc/init.d/dasnmp start
Enabling SNMP access and trap forwarding for VMware IBM Director supports SNMP access and trap forwarding on VMware ESX Server, and will inter-operate with the ucd-snmp versions that ship with VMware ESX Server versions 2.5.2 and 3.0. These instructions apply only to using IBM Director SNMP support on VMware ESX Server. Complete the following steps to enable SNMP access and trap forwarding for managed systems running VMware: 1. Download the net-snmp-5.2.1.tar.gz file from the Net-SNMP Web site at www.net-snmp.org/download.html. 2. Build and install the Net-SNMP libraries using the following steps. Notes: v This procedure does not perform a full installation of Net-SNMP, but installs only the Net-SNMP libraries, which are required for IBM Director Core Services SNMP functions. v Refer to the INSTALL and README files included in the net-snmp-5.2.1.tar.gz package for additional installation information.
142
IBM Director Express Planning, Installation and Configuration Guide
a. Untar the source files. Type the following command and press Enter. tar -xvzf net-snmp-5.2.1.tar.gz
b. Change to the source directory. Type the following command and press Enter. cd net-snmp-5.2.1
c. Build the Net-SNMP libraries with default options. Type the following commands (press Enter after each). ./configure --with-defaults make
d. Install the Net-SNMP libraries only to /usr/local/lib. Type the following command and press Enter. make installlibs
3. To enable trap forwarding, edit the /etc/init.d/dacimlist file and uncomment the following two lines two lines in the SNMP End Consumer section. LD_LIBRARY_PATH=/usr/local/lib export LD_LIBRARY_PATH
Note: The configuration changes will not take effect until you restart the cimlistener daemon in step 7. 4. To enable SNMP access, edit the /etc/init.d/dasnmp file and uncomment the following two lines in the section regarding the location of the net-snmp libraries. LD_LIBRARY_PATH=/usr/local/lib export LD_LIBRARY_PATH
5. Using the VMware Management Interface, configure the SNMP daemon that ships with VMware to support AgentX agents. For details, see the VMware documentation at www.vmware.com/support/pubs/esx_pubs.html. 6. Create the file /usr/local/share/snmp/snmpd.conf to specify trapsink and trapcommunity settings. You might have to create the directory. This file should contain only settings for trapcommunity and trapsink. a. Specify a trap community value by adding a line containing the word trapcommunity followed by a space and the trapcommunity value, as in the following example. trapcommunity public
b. Specify a trapsink value for each destination to which IBM Director will send SNMP traps. Add a line containing the word trapsink followed by a space and the trapsink value, as in the following example. trapsink 192.168.1.1
7. Restart the cimlistener daemon by typing the following commands and pressing Enter after each: /etc/init.d/dacimlist stop /etc/init.d/dacimlist start
8. Restart the IBM Director AgentX subagent by typing the following commands and pressing Enter after each: /etc/init.d/dasnmp stop /etc/init.d/dasnmp start
Chapter 8. Initially configuring IBM Director
143
144
IBM Director Express Planning, Installation and Configuration Guide
Chapter 9. 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 1. 2. 3.
uninstall IBM Director, complete the following steps: Shut down all applications. Click Start → Settings → Control Panel. The Control Panel window opens. 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.
© Copyright IBM Corp. 1999, 2006
145
Table 34. dirunins parameters Variable
Parameter
What it does
option
debug
Logs all messages that are sent by the Windows Installer log engine, including status and information messages
deletedata
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.
log=logfilename Specifies the fully qualified name of an alternative installation log file
directorcomponent
noreboot
Suppresses any required restart
silent
Suppresses all output to the screen
unattended
Shows the progress of the uninstallation but does not require any user input
verbose
Enables verbose logging
server
Uninstalls IBM Director Server and any installed IBM Director extensions
console
Uninstalls IBM Director Console and any installed IBM Director extensions
agent
Uninstalls Level 2: IBM Director Agent
coresvcs
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.
146
IBM Director Express Planning, Installation and Configuration Guide
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 41 on page 149. v Update Manager uses additional keyboard shortcuts for table navigation. For more information, see Table 58 on page 154. Table 35. Keyboard shortcuts for windows Action
Keyboard shortcut
Navigate out of the window.
Alt+F6
Hide the window.
Esc
Activate the default button (if defined).
Enter
Table 36. Keyboard shortcuts for option panes Action
Keyboard shortcut
Navigate in or out of the option pane.
Alt+F6
Hide a window.
Esc
Activate the default button (if defined).
Enter
Table 37. Keyboard shortcuts for scroll panes Action
Keyboard shortcut
Navigate forward out of the scroll pane.
Tab
Navigate backward out of the scroll pane.
Shift+Tab
Move up or down.
Up arrow or down arrow
© Copyright IBM Corp. 1999, 2006
147
Table 37. Keyboard shortcuts for scroll panes (continued) Action
Keyboard shortcut
Move left or right.
Left arrow or right arrow.
Navigate to the beginning or end of data.
Ctrl+Home or Ctrl+End
Navigate up or down one block.
PgUp or PgDn
Navigate to the left or right.
Ctrl+PgUp or Ctrl+PgDn
Table 38. Keyboard shortcuts for split panes Action
Keyboard shortcut
Navigate forward out of the split pane.
Tab or Ctrl+Tab
Navigate backward out of the split pane.
Shift+Tab or Ctrl+Shift+Tab
Navigate between split panes.
Tab or F6
Navigate to the splitter bar.
F8
Toggle the focus between two split bars (for windows with three split panes).
F8
Resize the split pane vertically.
Up arrow or down arrow
Resize the split pane horizontally.
Left arrow or right arrow
Maximize the size of the split pane .
Home
Minimize the size of the split pane.
End
Table 39. Keyboard shortcuts for notebooks (tabbed panes) Action
Keyboard shortcut
Navigate into the tabbed pane.
Tab
Navigate out of the tabbed pane.
Ctrl+Tab
Navigate to the left or right tab.
Left arrow or right arrow
Navigate to the tab above or below.
Up arrow or down arrow
Navigate from the tab to the page.
Enter or Ctrl+Down
Navigate from the page to the tab.
Ctrl+Up
Navigate to the previous or next page.
Ctrl+PgUp or Ctrl+PgDn
Table 40. Keyboard shortcuts for frames
148
Action
Keyboard shortcut
Display a window menu.
Alt+Space bar
Activate the default button (if defined).
Enter
IBM Director Express Planning, Installation and Configuration Guide
Table 41. Additional keyboard shortcuts for frames in External Application Launch wizard Action
Keyboard shortcut
To move focus to the description area when focus is currently on any of the first five event filters
Esc
To move focus to the description area when focus is currently on any other event filter
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 42. Keyboard shortcuts for internal frames Action
Keyboard shortcut
Open or restore the frame.
Ctrl+F5, Alt+F5, or Enter
Close the frame.
Ctrl+F4 or Alt+F5
Move the frame.
Ctrl+F7 or Alt+F7
Resize the frame.
Ctrl+F8 or Alt+F8
Minimize the frame size.
Ctrl+F9 or Alt+F9
Display a window menu.
Alt+Space bar
Activate the default button (if defined).
Enter
Table 43. Keyboard shortcuts for menu bar Action
Keyboard shortcut
Jump to the menu bar.
Alt or F10
Navigate out of the menu bar.
Esc or Alt
Navigate within the menu bar.
Arrow keys
Select the next or previous menu item.
Right arrow or left arrow
Activate the default or selected item.
Enter
Display a menu.
Use one of these keyboard shortcuts: v Up arrow v Down arrow v Enter v Space bar v Alt+Character accelerator key (if defined)
Hide a menu.
Esc or Alt
Table 44. Keyboard shortcuts for menus Action
Keyboard shortcut
Display a menu.
Enter or F10 Appendix A. Accessibility features for IBM Director
149
Table 44. Keyboard shortcuts for menus (continued) Action
Keyboard shortcut
Display a submenu.
Right arrow
Navigate to the next item or wrap to the top.
Down arrow
Navigate to the previous item or wrap to the bottom.
Up arrow
Hide the menu.
Esc
Hide the submenu.
Left arrow
Activate the default or selected item.
Enter
Table 45. Keyboard shortcuts for menu items Action
Keyboard shortcut
Navigate in or out of a menu.
Arrow keys
Activate an item.
Enter, space bar, or Alt+Character accelerator key (if defined)
Display a submenu.
Right arrow
Hide a submenu.
Left arrow or Esc
Table 46. Keyboard shortcuts for check-box menu items Action
Keyboard shortcut
Navigate in or out of the check-box menu.
Arrow keys
Select or clear a check-box menu item.
Enter
Hide a check-box menu.
Enter
Table 47. Keyboard shortcuts for radio-button menu items Action
Keyboard shortcut
Navigate in or out of a radio-button menu.
Arrow keys
Select or clear a radio-button menu item.
Enter
Hide a radio-button menu.
Enter
Table 48. Keyboard shortcuts for pop-up menus Action
Keyboard shortcut
Display a pop-up menu.
Shift+F10
Display a pop-up submenu.
Right arrow
Hide a pop-up menu.
Esc
Hide a submenu.
Left arrow
Navigate within a pop-up menu.
Up arrow or down arrow
Activate a pop-up menu item.
Enter or space bar
Table 49. Keyboard shortcuts for toolbar
150
Action
Keyboard shortcut
Navigate forward out of the toolbar.
Tab
IBM Director Express Planning, Installation and Configuration Guide
Table 49. Keyboard shortcuts for toolbar (continued) Action
Keyboard shortcut
Navigate backward out of the toolbar.
Shift+Tab
Navigate within the toolbar.
Arrow keys
Activate a toolbar item.
Enter
Display the Customized Toolbar menu (when focus is on an icon on the main IBM Director Console window toolbar).
Shift+10
Table 50. Keyboard shortcuts for tool tips Action
Keyboard shortcut
Display a tool tip.
Ctrl+F1
Hide a tool tip.
Esc or Ctrl+F1
Table 51. Keyboard shortcuts for buttons Action
Keyboard shortcut
Navigate forward.
Tab
Navigate backward.
Shift+Tab
Activate the default button.
Enter
Activate any button
Space bar or Alt+Character accelerator key (if defined).
Activate Cancel or Close.
Esc
Table 52. Keyboard shortcuts for check boxes Action
Keyboard shortcut
Navigate forward.
Tab
Navigate backward.
Shift+Tab
Navigate within a group.
Arrow keys
Select or clear a check box.
Space bar
Table 53. Keyboard shortcuts for radio buttons Action
Keyboard shortcut
Navigate forward.
Tab
Navigate backward.
Shift+Tab
Navigate within a group.
Arrow keys Note: To select the radio button, navigate to it.
Select or clear a radio button.
Space bar
Table 54. Keyboard shortcuts for combination boxes Action
Keyboard shortcut
Navigate forward out of the combination box.
Tab
Navigate backward out of the combination box.
Shift+Tab
Appendix A. Accessibility features for IBM Director
151
Table 54. Keyboard shortcuts for combination boxes (continued) Action
Keyboard shortcut
Navigate into a combination box within a table cell (focus must be in the table cell).
F2
Display the drop-down list.
Down arrow
Hide the drop-down list.
Esc or Alt+Up arrow
Activate the selected menu item.
Enter
Navigate up or down the drop-down list.
Alt+Up arrow or Alt+Down arrow
Navigate up or down the drop-down list for a combination box in a table.
Up arrow or Down arrow
Navigate to a list item without selecting it.
Initial character of the list item
Move up or down the drop-down list.
Up arrow or down arrow
Table 55. Keyboard shortcuts for lists Action
Keyboard shortcut
Navigate forward out of the list.
Tab
Navigate backward out of the list.
Shift+Tab
Activate the selected list item.
Enter
Navigate within the list.
Up arrow or down arrow
Navigate to the beginning or end of the list.
Ctrl+Home or Ctrl+End
Select all list items.
Ctrl+A
Select a single list item
Space bar Note: Using the space bar clears the previous selection.
Select an additional list item.
Ctrl+Space bar
Select a range of list items.
Shift+Space bar
Extend the selection up or down one item.
Shift+Up arrow or Shift+Down arrow
Extend the selection to the top or bottom of the list.
Shift+Home or Shift+End
Extend the selection up or down one block.
Shift+PgUp or Shift+PgDn
Navigate up or down a block.
PgUp or PgDn
Table 56. Keyboard shortcuts for sliders
152
Action
Keyboard shortcut
Navigate forward out of the slider.
Tab
Navigate backward out of the slider.
Shift+Tab
Increase the value
Up arrow or right arrow.
IBM Director Express Planning, Installation and Configuration Guide
Table 56. Keyboard shortcuts for sliders (continued) Action
Keyboard shortcut
Decrease the value
Down arrow or left arrow.
Set the maximum value.
Home
Set the minimum value.
End
Increase the value by a set range.
PgUp
Decrease the value by a set range.
PgDn
Table 57. Keyboard shortcuts for tables Action
Keyboard shortcut
Navigate forward out of the table.
Ctrl+Tab
Navigate backward out of the table.
Ctrl+Shift+Tab
Navigate to the next cell.
Tab or right arrow
Navigate to the previous cell.
Shift+Tab or left arrow
Navigate to the next row from the last column.
Tab or right arrow
Navigate to the previous row from the first column.
Shift+Tab or left arrow
Navigate vertically to the next or previous block.
PgUp or PgDn
Navigate horizontally to the left or right one block.
Ctrl+PgUp or Ctrl+PgDn
Navigate to the first or last cell in the row.
Home or End
Navigate to the first or last cell in the table.
Ctrl+Home or Ctrl+End
Select all cells in the table.
Ctrl+A
Clear the current selection.
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
Extend the selection up or down one row.
Shift+Up arrow or Shift+Down arrow
Extend the selection to the right or left one column.
Shift+Left arrow or Shift+Right arrow
Extend the selection to the beginning or end of the row.
Shift+Home or Shift+End
Extend the selection up or down one block.
Shift+PgUp or Shift+PgDn
Extend the selection left or right one block.
Ctrl+Shift+PgUp or Ctrl+Shift+PgDn
Appendix A. Accessibility features for IBM Director
153
Table 57. Keyboard shortcuts for tables (continued) Action
Keyboard shortcut
Extend the selection to the beginning or end of the column.
Ctrl+Shift+Home or Ctrl+Shift+End
Edit the cell without overriding the existing text.
F2
Delete the cell text before editing.
Esc
Table 58. Additional keyboard shortcuts for tables in Update Manager Action
Keyboard shortcut
Edit the sort order.
Ctrl+W
Sort the table by the selected column in ascending order.
Ctrl+S
Sort the table by the selected column in descending order.
Ctrl+Shift+S
Clear the sort.
Ctrl+T
Clear all sorts.
Ctrl+Q
Show the filter row.
Ctrl+R
Hide the filter row.
Ctrl+Shift+R
Edit the filter.
Ctrl+E
Apply the filter.
Ctrl+Shift+U
Deactivate the filter.
Ctrl+U
Clear all filters.
Ctrl+K
Display the find toolbar.
Ctrl+F
Hide the find toolbar.
Ctrl+Shift+F
Display the status line.
Ctrl+L
Hide the status line.
Ctrl+Shift+L
Table 59. Keyboard shortcuts for trees
154
Action
Keyboard shortcut
Navigate forward out of the tree.
Tab
Navigate backward out of the tree.
Shift+Tab
Expand the entry
Right arrow or Enter (if collapsed).
Collapse the entry
Left arrow or Enter (if expanded).
Navigate up or down one entry.
Up arrow or down arrow
Navigate to the first entry in the tree.
Home
Navigate to the last visible entry in the tree.
End
Navigate vertically up or down one block.
PgUp or PgDn
Navigate to the left or right one block.
Ctrl+PgUp or Ctrl+PgDn
Select all entries.
Ctrl+A or Ctrl+Slash
Clear the selection.
Ctrl+\
Select a single entry.
Ctrl+Space bar
Select a range of entries.
Shift+Space bar
IBM Director Express Planning, Installation and Configuration Guide
Table 59. Keyboard shortcuts for trees (continued) Action
Keyboard shortcut
Extend the selection up or down one block.
Shift+PgUp or Shift+PgDn
Extend the selection to the top of the tree.
Shift+Home
Extend the selection to the bottom of the tree.
Shift+End
Table 60. Keyboard shortcuts for text fields Action
Keyboard shortcut
Navigate into the text field
Alt+Character accelerator key (if defined).
Navigate forward out of the text field.
Tab
Navigate backward out of the text field.
Shift+Tab
Navigate to the previous or next character.
Left arrow or right arrow
Navigate to the previous or next word.
Ctrl+Left arrow or Ctrl+Right arrow
Navigate to the beginning or end of a field.
Home or End
Submit an entry.
Enter
Select all text in the field.
Ctrl+A
Clear the selection.
Arrow keys
Extend the selection to the left or right one character.
Shift+Left arrow or Shift+Right arrow
Extend the selection to the beginning or end of the field.
Shift+Home or Shift+End
Extend the selection to the next or previous word.
Ctrl+Shift+Left arrow or Ctrl+Shift+Right arrow
Copy the selected text.
Ctrl+C
Cut the selected text.
Ctrl+X
Paste from the clipboard.
Ctrl+V
Delete the previous or next character
Backspace or Delete
Table 61. Keyboard shortcuts for text panes Action
Keyboard shortcut
Navigate into the text pane.
Tab or Alt+Character accelerator key (if defined).
Navigate forward out of the text pane.
Ctrl+Tab
Navigate backward out of the text pane.
Ctrl+Shift+Tab
Navigate vertically up or down one block.
PgUp or PgDn
Navigate up or down one line.
Up arrow or down arrow
Navigate to the left or right one component or character.
Left arrow or right arrow
Appendix A. Accessibility features for IBM Director
155
Table 61. Keyboard shortcuts for text panes (continued) Action
Keyboard shortcut
Navigate to the beginning or end of a line.
Home or End
Navigate to the previous or next word.
Ctrl+Left arrow or Ctrl+Right arrow
Navigate to the beginning or end of the text pane.
Ctrl+Home or Ctrl+End
Navigate up or down one block.
PgUp or PgDn
Navigate to the left or right one block.
Ctrl+PgUp or Ctrl+PgDn
Navigate to the next or previous HTML link or other element which can receive the focus.
Ctrl+T or Ctrl+Shift+T
Navigate out of a focusable element that accepts a tab.
Ctrl+Tab or Ctrl+Shift+Tab
Activate a hyperlink.
Ctrl+Space bar
Extend the selection up or down one block.
Shift+PgUp or Shift+PgDn
Extend the selection to the left or right one block.
Ctrl+Shift+PgUp or Ctrl+Shift+PgDn
Extend the selection up or down one line.
Shift+Up arrow or Shift+Down arrow
Extend the selection to the left or right.
Shift+Left arrow or Shift+Right arrow
Extend the selection to the beginning or end of the line.
Shift+Home or Shift+End
Extend the selection to the beginning or end of the text pane.
Ctrl+Shift+Home or Ctrl+Shift+End
Extend the selection to the previous or next word.
Ctrl+Shift+Left arrow or Ctrl+Shift+Right arrow
Extend the selection vertically up or down one block.
Shift+PgUp or Shift+PgDn
Extend the selection to the left or right one block.
Ctrl+Shift+PgUp or Ctrl+Shift+PgDn
Select all text in the text pane.
Ctrl+A
Clear the selection.
Arrow keys
Copy the selected text.
Ctrl+C
Cut the selected text.
Ctrl+X
Paste from the clipboard.
Ctrl+V
Delete the previous or next component or character.
Backspace or Delete
Insert a line break.
Enter
Insert a tab.
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.
156
IBM Director Express Planning, Installation and Configuration Guide
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.
Appendix A. Accessibility features for IBM Director
157
158
IBM Director Express Planning, Installation and Configuration Guide
Appendix B. 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 62. Default LDAP authentication properties for IBM Director Server Property name
Description
ldap.auth.jndi
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.
ldap.auth.mechanism
Specifies the LDAP authentication mechanism to use: simple anonymous DIGEST-MD5
ldap.auth.userid.attribute
Specifies the name of the attribute on the LDAP server that specifies the user ID. This attribute is often named uid.
ldap.dn
Specifies the distinguished name of the LDAP server instance.
© Copyright IBM Corp. 1999, 2006
159
Table 62. Default LDAP authentication properties for IBM Director Server (continued) Property name
Description
ldap.enabled
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
Specifies the authorization mechanism to use when accessing the group information. The default mechanism is anonymous.
ldap.group.desc.attribute
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.
ldap.group.pwd
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.
ldap.host
Specifies the LDAP server address.
ldap.port
Specifies the port number to be used for LDAP authentication requests. By default, this is set to port 389.
ldap.search.scope
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.
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
160
IBM Director Express Planning, Installation and Configuration Guide
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 B. Lightweight Directory Access Protocol authentication properties for IBM Director Server
161
162
IBM Director Express Planning, Installation and Configuration Guide
Appendix C. 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 about the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not 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.
© Copyright IBM Corp. 1999, 2006
163
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. 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 document 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. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information softcopy, the photographs and color illustrations may not appear.
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
164
IBM Director Express Planning, Installation and Configuration Guide
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 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. Appendix C. Notices
165
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.
166
IBM Director Express Planning, Installation and Configuration Guide
Glossary contained an ASM processor. When an ASM PCI adapter is used with an ASM processor, the ASM PCI adapter acts as an Ethernet gateway, while the ASM processor retains control of the server. When used as a gateway service processor, the ASM PCI adapter can communicate with other ASM PCI adapters and ASM processors only.
Glossary This glossary includes terms and definitions for IBM Director. To view glossaries for other IBM products, go to www.ibm.com/ibm/terminology .
A accelerator In a user interface, a key or combination of keys that invokes an application-defined function. Advanced Encryption Standard (AES) A data encryption technique that improved upon and officially replaced the Data Encryption Standard (DES). AES is sometimes referred to as Rijndael, which is the algorithm on which the standard is based.
Advanced System Management processor (ASM processor) A service processor built into the mid-range Netfinity and early xSeries servers. IBM Director can connect out-of-band to an ASM processor located on an ASM interconnect; an ASM PCI adapter, a Remote Supervisor Adapter, or a Remote Supervisor II must serve as the gateway service processor. AES
See Advanced Encryption Standard.
Advanced System Management interconnect (ASM interconnect) A feature of IBM service processors that enables users to connect up to 24 servers to one service processor, thus eliminating the need for multiple modems, telephones, and LAN ports. It provides such out-of-band management functions as system power control, service-processor event-log management, firmware updates, alert notification, and user profile configuration.
alert
A message or other indication that signals an event or an impending event.
Advanced System Management interconnect network (ASM interconnect network) A network of IBM servers created by using the ASM interconnect feature. The servers are connected through RS-485 ports. When servers containing integrated system management processors (ISMPs) and ASM processors are connected to an ASM interconnect network, IBM Director can manage them out-of-band.
alert standard format (ASF) A specification created by the Distributed Management Task Force (DMTF) that defines remote-control and alerting interfaces that can best serve a client system in an environment that does not have an operating system.
Advanced System Management PCI adapter (ASM PCI adapter) An IBM service processor that is built into the Netfinity 7000 M10 and 8500R servers. It also was available as an option that could be installed in a server that © Copyright IBM Corp. 1999, 2006
alert forwarding A function that ensures that alerts are sent, even if a managed system experiences a catastrophic failure, such as an operating-system failure. alert-forwarding profile A profile that specifies where remote alerts for the service processor should be sent.
anonymous command execution Execution of commands on a target system as either system account (for managed systems running Windows) or root (for managed systems running Linux). ASF
See alert standard format.
167
ASM interconnect See Advanced System Management interconnect.
bottleneck A place in the system where contention for a resource is affecting performance.
ASM interconnect gateway See gateway service processor.
C
ASM interconnect network See Advanced System Management interconnect network. ASM PCI adapter See Advanced System Management PCI adapter. ASM processor See Advanced System Management processor. association A visual representation of the members in a group that shows relationships or provides additional information about the members of a group. Auto-Logical Drive Transfer See auto volume transfer/auto disk transfer.
chassis The metal frame in which various electronic components are mounted. chassis detect-and-deploy profile A profile that IBM Director automatically applies to all new BladeCenter chassis when they are discovered. The profile settings include management module name, network protocols, and static IP addresses. If Remote Deployment Manager (RDM) is installed on the management server, the chassis detect-and-deploy profile also can include deployment policies. CIM cloning In z/VM, a copying technique that preserves the characteristics of the original but personalizes instance-specific data. The result of a cloning operation is new instance of an entity (for example, of a virtual disk, a virtual computer system, or an operating system) rather than a backup of the original.
auto volume transfer/auto disk transfer (AVT/ADT) A function that provides automatic failover in case of controller failure on a storage subsystem. AVT/ADT See auto volume transfer/auto disk transfer.
cluster A collection of complete systems that work together to provide a single, unified computing capability.
B Basic Input/Output System (BIOS) The code that controls basic hardware operations, such as interactions with diskette drives, hard disk drives, and the keyboard. BIOS
See Basic Input/Output System.
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. blade server A high-throughput, two-way, Intel Xeon-based server on a card that supports symmetric multiprocessors (SMPs).
168
See Common Information Model.
CMS
See Conversational Monitor System.
Common Information Model (CIM) An implementation-neutral, object-oriented schema for describing network management information. The Distributed Management Task Force (DMTF) develops and maintains CIM specifications. component association In the IBM Director Rack Manager task, a function that can make a managed system or device rack-mountable when the inventory collection feature of IBM Director does not recognize the managed system or device. The function associates the system or device with a predefined component.
IBM Director Express Planning, Installation and Configuration Guide
Conversational Monitor System (CMS) A virtual-machine operating system that provides general interactive time sharing, problem solving, and program development capabilities.
D
disk pool In z/VM Center, a logical grouping of contiguous disk spaces. A disk pool can include disk spaces from multiple physical disks. A disk pool corresponds to a z/VM Directory Maintenance Facility allocation group.
database server The server on which the database application and database are installed.
DMI
See Desktop Management Interface.
DSA
See digital signature algorithm.
Data Encryption Standard (DES) A cryptographic algorithm designed to encrypt and decrypt data using a private key.
E
deployment policy A policy that associates a specific bay in a BladeCenter chassis with a Remote Deployment Manager (RDM) noninteractive task. When a blade server is added to or replaced in the bay, IBM Director automatically runs the RDM task. DES
See Data Encryption Standard.
Desktop Management Interface (DMI) A protocol-independent set of application programming interfaces (APIs) that were defined by the Distributed Management Task Force (DMTF). These interfaces give management application programs standardized access to information about hardware and software in a system. Diffie-Hellman key exchange A public, key-exchange algorithm that is used for securely establishing a shared secret over an insecure channel. digital signature algorithm (DSA) A security protocol that uses a pair of keys (one public and one private) and a one-way encryption algorithm to provide a robust way of authenticating users and systems. If a public key can successfully decrypt a digital signature, a user can be sure that the signature was encrypted using the private key. directory manager A facility for maintaining the user directory of one or more z/VM systems. discovery The process of finding resources within an enterprise, including finding the new location of monitored resources that were moved.
enclosure A unit that houses the components of a storage subsystem, such as a control unit, disk drives, and power source. event
An occurrence of significance to a task or system. Events can include completion or failure of an operation, a user action, or the change in state of a process.
event action The action that IBM Director takes in response to a specific event or events. event-action plan A user-defined plan that determines how IBM Director will manage certain events. An event action plan comprises one or more event filters and one or more customized event actions. event-data substitution variable A variable that can be used to customize event-specific text messages for certain event actions. event filter A filter that specifies the event criteria for an event action plan. Events must meet the criteria specified in the event filter in order to be processed by the event action plan to which the filter is assigned.
F fabric A complex network using hubs, switches, and gateways. Fibre channel uses a fabric to connect devices. field-replaceable unit (FRU) An assembly that is replaced in its entirety when any one of its components fails. file-distribution server In the Software Distribution task, an intermediate server that is used to Glossary
169
distribute a software package when the redirected-distribution method is used. forecast A function that can provide a prediction of future performance of a managed system using past data collected on that managed system. FRU
See field-replaceable unit.
G gateway service processor A service processor that relays alerts from service processors on an Advanced System Management (ASM) interconnect network to IBM Director Server. group A logical set of managed objects. Groups can be dynamic, static, or task-based. Guest LAN A virtual local area network (LAN) segment that is emulated by the z/VM Control Program (CP). A Guest LAN can be shared by guest virtual machines on the same z/VM system. guest virtual machine In z/VM, the functional equivalent of a System z9 or zSeries system, including the virtual processors, virtual storage, virtual devices, and virtual channel subsystem allocated to a single user. Each guest virtual machine can be controlled by an operating system, such as CMS, z/VSE, z/OS, or Linux.
H host object A logical object that groups one or more worldwide port names (WWPNs) of the host bus adapters (HBAs) that the cluster has detected on the storage area network (SAN). HT
See Hyper-Threading.
Hyper-Threading (HT) A technology with which a single processor can function as two virtual processors and execute two threads simultaneously. hypervisor A program or a portion of Licensed Internal Code (LIC) that allows multiple instances of operating systems to run simultaneously on the same hardware.
170
I IBM Director Agent A component of IBM Director software. When IBM Director Agent is installed on a system, the system can be managed by IBM Director. IBM Director Agent transfers data to the management server using several network protocols, including TCP/IP, NetBIOS, and IPX. IBM Director Console A component of IBM Director software. When installed on a system, it provides a graphical user interface (GUI) for accessing IBM Director Server. IBM Director Console transfers data to and from the management server using TCP/IP. IBM Director Core Services A facility with which IBM Director communicates with and administers a level-2 managed system. IBM Director Core Services includes the service location protocol (SLP) instrumentation, the IBM Director Agent SLP service type, and Common Information Model (CIM). IBM Director database The database that contains the data stored by IBM Director Server. IBM Director environment The complex, heterogeneous environment managed by IBM Director. It includes systems, BladeCenter chassis, software, and SNMP devices. IBM Director extension A tool that extends the functionality of IBM Director. Some of the IBM Director extensions are Capacity Manager, ServeRAID Manager, Remote Deployment Manager, and Software Distribution. IBM Director Server The main component of IBM Director software. When installed on the management server, it provides basic functions such as discovery of the managed systems, persistent storage of configuration and management data, an inventory database, event listening, security and authentication, management console support, and administrative tasks. IBM Director Server service A service that runs automatically on the
IBM Director Express Planning, Installation and Configuration Guide
management server, and provides the server engine and application logic for IBM Director. IBM Director service account The Windows operating-system account associated with the IBM Director Server service. in-band communication initial program load (IPL) The process that loads the system programs from the system auxiliary storage, checks the system hardware, and prepares the system for user operations. instance An individual realization of the operating system with a particular version, configuration, physical location, and identifier. In object-oriented programming, an object of a particular class. integrated system management processor (ISMP) A service processor built into some xSeries servers. ISMP is the successor to the Advanced System Management (ASM) processor. interprocess communication (IPC) A mechanism of an operating system that allows processes to communicate with each other within the same computer or over a network. inventory-software dictionary A file that tracks the software installed on managed systems in a network. IPC
See interprocess communication.
IPL
See initial program load.
ISMP See integrated system management processor.
J job
A separately executable unit of work.
K L Level-0 managed system An IBM or non-IBM server, desktop computer, workstation, or mobile computer, that can be managed by IBM
Director but does not have any IBM Director software installed on it. Level-1 managed system An IBM or non-IBM server, desktop computer, workstation, and mobile computer that has IBM Director Core Services installed. Level-2 managed system An IBM or non-IBM server, desktop computer, workstation, or mobile computer that has IBM Director Agent installed. The function of a Level-2 managed system varies depending on the operating system and hardware. light path diagnostics A technology that provides a lighted path to failed or failing components to expedite hardware repairs. logical unit number (LUN) In the Small Computer System Interface (SCSI) standard, a unique identifier used to differentiate devices, each of which is a logical unit (LU). LUN
See logical unit number.
M MAC address See Media Access Control address. managed group A group of systems or objects managed by IBM Director. managed object A resource that is subject to management--such as a connection, a scalable system, or a line--as viewed from a systems management perspective. managed object ID A unique identifier for each managed object. managed system A system that is being controlled by a given system management application. management console A system (server, desktop computer, workstation, or mobile computer) on which IBM Director Console is installed. management module The BladeCenter component that handles system-management functions. It configures the chassis and switch Glossary
171
modules, communicates with the blade servers and all I/O modules, multiplexes the keyboard/video/mouse (KVM), and monitors critical information about the chassis and blade servers.
connection, for example, service processor alerts sent through a modem or over a LAN.
P See Peripheral Component Interconnect. See also Peripheral Component Interconnect-X.
management server The server on which IBM Director Server is installed.
PCI
master system In z/VM Center, an operating system instance that has been set up to serve Virtual Server Deployment as a model for creating operating system templates.
PCI-X See Peripheral Component Interconnect-X. See also Peripheral Component Interconnect.
Media Access Control address (MAC address) In a local area network, the protocol that determines which device has access to the transmission medium at a given time. minidisk A direct access storage device (DASD) or a logical subdivision of a DASD that has its own virtual device number.
N node port (N_port) A port that connects a node to a fabric or to another node. An N_port connects to a fabric port (F_port) or to the N_port of another node. An N_port handles creation, detection, and flow of message units to and from the connected systems. N_ports are end points in point-to-point links. nonvolatile random access memory (NVRAM) Random access memory (storage) that retains its contents after the electrical power to the machine is shut off. N_port See node port. NVRAM See nonvolatile random access memory.
Peripheral Component Interconnect (PCI) A local bus that provides a high-speed data path between the processor and attached devices. See also Peripheral Component Interconnect-X. Peripheral Component Interconnect-X (PCI-X) An enhancement to the Peripheral Component Interconnect (PCI) architecture. PCI-X enhances the Peripheral Component Interconnect (PCI) standard by doubling the throughput capability and providing additional adapter-performance options while maintaining backward compatibility with PCI adapters. See also Peripheral Component Interconnect. persistent Pertaining to data that is maintained across session boundaries, usually in nonvolatile storage such as a database system or a directory. PFA
physical platform An IBM Director managed object that represents a single physical chassis or server that has been discovered through the use of the Service Location Protocol (SLP). plug-in A software module that adds function to an existing program or application.
O operating system template A set of installation and configuration data that z/VM Center uses as a source for creating operating system instances. Operating system templates are created from master systems. out-of-band communication Communication that occurs through a modem or other asynchronous
172
See Predictive Failure Analysis.
POST See power-on self-test. power-on self-test (POST) A series of internal diagnostic tests activated each time the system power is turned on. Predictive Failure Analysis (PFA) A scheduled evaluation of system data
IBM Director Express Planning, Installation and Configuration Guide
that detects and signals parametric degradation which might lead to functional failures.
resource-monitor threshold The point at which a resource monitor generates an event.
private key In secure communication, an algorithmic pattern used to encrypt messages that only the corresponding public key can decrypt. The private key is also used to decrypt messages that were encrypted by the corresponding public key. The private key is kept on the user’s system and is protected by a password. See also public key.
RXE Expansion Port The dedicated high-speed port used to connect a remote I/O expansion unit, such as the RXE-100 Remote Expansion Enclosure, to a server.
programming interface for customers The supported method through which customer programs request software services. The programming interface consists of a set of callable services provided with a product. public key In secure communication, an algorithmic pattern used to decrypt messages that were encrypted by the corresponding private key. A public key is also used to encrypt messages that can be decrypted only by the corresponding private key. Users broadcast their public keys to everyone with whom they must exchange encrypted messages. See also private key.
Q R redirected distribution A method of software distribution that uses a file-distribution server. remote I/O enclosure An IBM Director managed object that represents an expansion enclosure of Peripheral Component Interconnect-X (PCI-X) slots, for example, an RXE-100 Remote Expansion Enclosure. The enclosure consists of one or two expansion kits. Remote Supervisor Adapter An IBM service processor. It is built into some xSeries servers and available as an optional adapter for use with others. When used as a gateway service processor, the Remote Supervisor Adapter can communicate with all service processors on the Advanced System Management (ASM) interconnect.
S scalable node A physical platform that has at least one SMP Expansion Module. Additional attributes are assigned to a physical platform when it is a scalable node. These additional attributes record the number of SMP Expansion Modules, SMP Expansion Ports, and RXE Expansion ports on the physical chassis. scalable object An IBM Director managed object that is used with Scalable Systems Manager. Scalable objects include scalable nodes, scalable systems, scalable partitions, and remote I/O enclosures that are attached to scalable nodes. scalable partition An IBM Director managed object that defines the scalable nodes that can run a single image of the operating system. A scalable partition has a single, continuous memory space and access to all associated adapters. A scalable partition is the logical equivalent of a physical platform. Scalable partitions are associated with scalable systems and comprise only the scalable nodes from their associated scalable systems. scalable system An IBM Director managed object that consists of scalable nodes and the scalable partitions that are composed of the scalable nodes in the scalable system. When a scalable system contains two or more scalable nodes, the servers that they represent must be interconnected through their SMP Expansion Modules to make a multinode configuration, for example, a 16-way xSeries 455 server made from four scalable nodes. Secure Sockets Layer (SSL) A security protocol that provides communication privacy. With SSL, Glossary
173
client/server applications can communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery. server complex In z/VM Center, a configuration profile for Linux guest systems that includes both Linux and z/VM aspects. A server complex can define network settings, Linux configuration scripts, disk access, and VM Resource Manager (VMRM) performance goals. Service Location Protocol (SLP) An Internet protocol that identifies and uses network hosts without having to designate a specific network host name. service machine In z/VM, a guest virtual machine that provides a system service such as accounting, error recording, or monitoring. A system service can be part of z/VM or a licensed program. service processor A generic term for Remote Supervisor Adapters, Advanced System Management processors, Advanced System Management PCI adapters, and integrated system management processors (ISMPs). These hardware-based management processors used in IBM Netfinity and xSeries servers work with IBM Director to provide hardware status and alert notification. SLP
See Service Location Protocol.
SMBIOS See system management BIOS. SMP Expansion Module An IBM xSeries hardware option. It is a single module that contains microprocessors, disk cache, random access memory, and three SMP Expansion Port connections. Two SMP Expansion Modules can fit in a chassis. SNMP Access and Trap Forwarding An IBM Director Agent feature that enables SNMP to access managed-system data. When installed on a managed system, this feature enables SNMP-based managers to poll the managed system and receive its alerts. If System Health Monitoring is installed on the managed
174
system also, hardware alerts can be forwarded as SNMP traps. SNMP device An embedded device that uses SNMP to monitor network-attached devices, printers, or computers for conditions that require system-management attention. SQL
See Structured Query Language.
SSL
See Secure Sockets Layer.
static partition A view-only scalable partition. sticky key An input method that enables the user to press and release a series of keys sequentially (for example, Ctrl+Alt+Del), yet have the keys behave as if they were pressed and released at the same time. This method can be used for those who require special-needs settings to make the keyboard easier to use. storage subsystem A storage control and its attached storage devices. Structured Query Language (SQL) A standardized language for defining and manipulating data in a relational database. switch module The BladeCenter component that provides network connectivity for the BladeCenter chassis and blade servers. It also provides interconnectivity between the management module and blade servers. System Health Monitoring An IBM Director Agent feature that provides active monitoring of critical system functions, including system temperatures, voltages, and fan speeds. It also handles in-band alert notification for managed systems running Windows and some managed systems running Linux. system management BIOS (SMBIOS) A specification that extends BIOS to support the retrieval of management data. system variable A user-defined keyword and value pair that can be used to test and track the status of network resources. System variables can be referred to wherever event-data substitution is allowed.
IBM Director Express Planning, Installation and Configuration Guide
T
Agent from within the higher-level systems-management console, as well as collect IBM Director inventory data and view IBM Director alerts.
target system A managed system on which an IBM Director task is performed. time to live A technique used by best-effort delivery protocols to inhibit endlessly looping packets. The packet is discarded if the TTL counter reaches 0. triple Data Encryption Standard (triple DES) 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. triple DES See triple Data Encryption Standard. truststore In security, a storage object, either a file or a hardware cryptographic card, where public keys are stored in the form of trusted certificates, for authentication purposes in Web transactions. In some applications, these trusted certificates are moved into the application keystore to reside with the private keys.
U Universally Unique Identifier The 128-bit numerical identifier that is used to ensure that two components do not have the same identifier. Universal Unique Identifier (UUID) See Universally Unique Identifier. upward integration The methods, processes and procedures that enable lower-level systems-management software, such as IBM Director Agent, to work with higher-level systems-management software, such as Tivoli Enterprise or Microsoft SMS. upward integration module Software that enables higher-level systems-management software, such as Tivoli Enterprise or Microsoft Systems Manager Server (SMS), to interpret and display data provided by IBM Director Agent. This module also can provide enhancements that start IBM Director
user class A z/VM privilege category assigned to a user of a guest virtual machine in the user’s directory entry; each class specified allows access to a logical subset of all the z/VM Control Program (CP) commands. UUID See Universal Unique Identifier.
V virtual device number In z/VM, a device number used by a guest virtual machine. Real devices can be referred to by different virtual device numbers by different guest virtual machines. virtual server template A set of definitions that provides configuration defaults for z/VM virtual servers. z/VM Center uses virtual server templates to create z/VM virtual servers. vital product data (VPD) Information that uniquely defines system, hardware, software, and microcode elements of a processing system. VPD
See vital product data.
W Wake on LAN A technology that enables a user to remotely turn on systems for off-hours maintenance. A result of the Intel-IBM Advanced Manageability Alliance and part of the Wired for Management Baseline Specification, users of this technology can remotely turn on a server and control it across the network, thus saving time on automated software installations, upgrades, disk backups, and virus scans. walk
An SNMP operation that is used to discover all object instances of management information implemented in the SNMP agent that can be accessed by the SNMP manager.
Windows Management Instrumentation (WMI) An application programming interface (API) in the Windows operating system Glossary
175
that enables devices and systems in a network to be configured and managed. WMI uses the Common Information Model (CIM) to enable network administrators to access and share management information. WMI
See Windows Management Instrumentation.
WMI Query Language (WQL) A subset of the Structured Query Language (SQL) with minor semantic changes to support Windows Management Instrumentation (WMI). WQL
See WMI Query Language.
X Y Z z/VM
A System z9 and zSeries operating system that acts as virtualization software. z/VM can virtualize all system resources, including processors, memory, storage devices, and communication devices. z/VM supports the concurrent operation of hundreds of operating system instances.
z/VM virtual server In z/VM, a guest virtual machine that a user can log on to.
Symbols and Numerics
176
IBM Director Express Planning, Installation and Configuration Guide
Index A accessibility 147 features 147 keyboard 147 shortcut keys 147 Advanced System Management 42 AIX installing IBM Director Agent 89 IBM Director Console 67 AIX installation Express IBM Director Server 55 alerts definition 32 Apache Derby 28 ASF 22 generating events 32 ASM 42 Asset ID operating systems, supported 18
B baseboard management controller 24 Baseboard Management Controller 42 blade servers total BladeCenter units 26 BladeCenter chassis assigning IP addresses manually 118 DHCP server, using 118 discovering (automatically) 118 IP address conflicts 118 deployment infrastructure DHCP server, using 118 IP address conflicts 118 documentation v network devices 26 products, supported tasks 26 BladeCenter Configuration Manager operating systems, supported 20 BladeCenter HS20, machine type 8843 44 BladeCenter(TM) HS20, machine type 8832 44 BMC 24, 42 books v Brocade switches 28
C Capacity Manager management server, installing on 57 chassis (BladeCenter) DHCP server, using 118 discovering (automatically) 118 IP address conflicts 118 manually assigning IP addresses 118 © Copyright IBM Corp. 1999, 2006
chassis managed objects displayed in IBM Director Console (screenshot) 118 CIM Browser operating systems, supported 18 compatibility documents v Compatibility Documents 13 concepts 1 Configuration Manager 26 Configure SNMP Agent operating systems, supported 18 customer support v
D dacimlist startup script 140 dasnmp startup script 140 database function of 5 databases Apache Derby 28 for management servers 28 IBM Cloudscape 28 IBM DB2 28 Microsoft Data Engine 28 Microsoft SQL Server 28 MS Jet 28 MSDE 28 Oracle Server 28 PostgreSQL 28 supported 28 deployment infrastructure (BladeCenter) DHCP server, using 118 IP address conflicts 118 design strategies, event action plan 34 DHCP server 118 diragent.rsp 89 diragent.rsp file upgrading IBM Director Agent using Software Distribution 85, 108 dircon.rsp file customizing 74 location 74 dirinstall script IBM Director Agent 78, 94 IBM Director Console 70 IBM Director Server 55 diruns utility 145 disability 147 discovery BladeCenter chassis 118 documentation v domain controller 31 downloading v compatibility documents v hardware compatibility information v IBM Director code v IBM Director publications v Net-SNMP, version 5.2.1 140 systems-management software v
DS300 28 DS400 28 DS4000 28 DS6000 28
E encryption enabling on managed system AIX 89 i5/OS 91 Linux 92, 95, 97 Windows 100 enabling on management server Windows 57 environment ports used 11 environment (illustration) 1 event availability 36 definition 32 how they work 32 management 35 overview 32 publishing 36 sources that generate 32 types alert 32 availability 36 resolution 32 event action plans 35 design strategies 34 example 36 grouping systems 35 how events work 32 naming conventions 35 overview 35 planning and designing 34 structuring 36 successful implementation 35 wizard 35 event filters structuring 36 Event Log operating systems, supported 18 examples event action plan 36 Express installation AIX IBM Director Server 55 IBM Director Server 57 Linux 61 Linux for System z 63 Linux on POWER 59 extensions publishing events 36 External Application Launch management server support 20 operating systems, supported 18, 20 External Application Launch wizard operating systems, supported 18
177
F features, accessibility 147 File Transfer operating systems, supported file-distribution server configuring 138 setting up 137 firewall access configuring 11
18
G glossary 167 grouping managed systems
35
H hardware requirements 7 hardware compatibility v hardware requirements 7, 8, 9 Hardware Status management server support 20 operating systems, supported 18, 20 help, IBM Director resources v
I i5/os installing, IBM Director Console 67 i5/OS 91 installing IBM Director Server 39 i5/OS installation encryption, enabling 91 IBM Director Agent, installing 91 starting 91 IBM Cloudscape 28 IBM DB2 28 IBM Director components of 1 concepts 1 getting started 1 IBM Director Console 1 overview 1 scenarios 1 IBM Director Agent AIX 89 AIX, installing on encryption, enabling 89 BladeCenter chassis 26 server 26 encryption, enabling AIX 89 i5/OS 91 Linux 78, 92, 95, 97 Windows 100 function 4 generating events 32 hardware requirements 7, 8, 9 IBM Director tasks 26 installing using Software Distribution 107
178
IBM Director Agent (continued) installing on AIX 89 license 4 Linux, installing on dirinstall script 78, 92, 94, 95, 97 Net-SMNP, enabling 78, 92, 94, 95, 97 Wake on LAN, enabling 92, 95, 97 NetWare, installing on features, selecting 98 network driver, configuring 98 network protocols 10 operating systems, supported 14 uninstalling Windows 145 Windows, installing on encryption, enabling 100 features, selecting 100, 104 InstallShield wizard, using 100 network driver, configuring 100, 104 securing managed system 100 security state, setting 100 software-distribution settings 100 Wake on LAN, enabling 100, 104 IBM Director Console 73 authorizing users 112 features, selecting 73 function 5 hardware requirements 7, 8 installing 67 installing on AIX 67 Linux 69 Linux for POWER 71 installing on Linux 70 installing on Windows dircon.rsp file 74 InstallShield wizard, using 73 unattended mode, using 74 license 5 network protocols 10 operating systems, supported 14 overview 1 uninstalling Windows 145 IBM Director Console installation 73 IBM Director Core Service installing on Linux for POWER 79 Windows 81 IBM Director Core Services function 3 installing 49 license 3 IBM Director Hardware and Software Compatibility document v IBM Director Server AIX, installing on 55 encryption, enabling Windows 57 function 5 hardware requirements 7, 8, 9 i5/OS installing 39
IBM Director Express Planning, Installation and Configuration Guide
IBM Director Server (continued) installing Linux for System x 41 System p 40 license 5 network protocols 10 operating systems, supported 14 preparing, for installation 40, 41 uninstalling Windows 145 where to install 31 Windows, installing on database configuration 57 encryption settings 57 features, selecting 57 network driver, configuring 57 service account 57 Software Distribution settings 57 Wake on LAN, enabling 57 IBM eServer Information Center v IBM systems-management software downloading v overview v IBM Web sites eServer Information Center v Redbooks v ServerProven v Support v Systems Management Software v xSeries Systems Management v illustrations IBM Director environment 1 IBM Director software components 2 installing IBM Director Agent using, Software Distribution 107 IBM Director Console AIX 67 Linux for POWER 71 Linux for System x 69 overview 67 IBM Director Core Service Linux for POWER 79 Windows 81 IBM Director Server Linux 61 Linux for System z 63 Linux on POWER 59 InstallShield wizard IBM Director Agent 100 IBM Director Console 73 IBM Director Server 57 Integrated System Management Processor 42 Intel Itanium IBM Director Agent installing 97 Intelligent Platform Management Interface 42 interim fixes v Inventory operating systems, supported 18 IP address conflicts, troubleshooting 118 IPMI 42 IPMI baseboard management controller generating events 32 ISMP 42
K keyboard 147
L legal notices 163 Level 1 managed system 3 Level-1 managed system preparing, for installation 49 Level-2 managed system 4 license IBM Director Agent 4 IBM Director Console 5 IBM Director Core Services 3 IBM Director Server 5 Linux for POWER installing IBM Director Console 71 IBM Director Core Service 79 Linux for System x installing IBM Director Console 69 Linux installation encryption, enabling 92, 95, 97 IBM Director Agent 78, 92, 94, 95 IBM Director Console 70 Intel Itanium IBM Director Agent 97 modifying SNMP Access and Trap Forwarding, enabling 140 starting 78, 92, 94, 95, 97 System p IBM Director Server 59 System x IBM Director Server 61 System z IBM Director Server 63
M managed system authorizing request access 113 request access authorizing 113 managed systems definition 1 distribution preferences, configuring 139 hardware requirements 7, 8, 9 preparing Windows XP 53 securing IBM Director Agent installation, during 100 management console 5 definition 2 hardware requirements 7, 8 management processor generating events 32 Management Processor Assistant Agent managed system, installing on 98, 100 NetWare, installing on 98
management server choosing 31 definition 1 hardware requirements 7, 8, 9 Microsoft Data Engine 28 Microsoft SQL Server 28 modifying an IBM Director installation Linux installation SNMP Access and Trap Forwarding, enabling 140 MS Jet 28 MSDE 28
N N3700 28 N5200 28 Net-SNMP, version 5.2.1 140 NetWare installation IBM Director Agent, installing 98 MPA Agent, when to install 98 Network Configuration operating systems, supported 18 network protocols 10 New Scheduled Job window 86, 109 notifications definition 32
O operating system compatibility v support for tasks supported 13 Oracle Server 28
17
P PET, generating events 32 planning and designing event action plans 34 ports 11 PostgreSQL 28 Power Management management server support 22 operating system support 22 operating systems 22 service processor 24 Wake on LAN 24 preparing Level-1 managed system 49 Linux for System x IBM Director Server, installation of 41 System p IBM Director Server, installation of 40 Process Management operating systems, supported 18 process monitors event 35 publications v
Q QLogic BladeCenter switches
28
R Rack Manager management console, installing on 73 management server, installing on 57 operating systems, supported 18 Red Hat Enterprise Linux AS, ES, and WS, version 3.0 49 Redbooks v related information v Remote Control operating systems, supported 18 Remote Control Agent managed system, installing on 100 management server, installing on 57 Remote Session operating systems, supported 18 Remote Supervisor Adapter 24, 42 documentation v request access authorizing, on a managed system 113 requirements 7 hardware 7 resolution definition 32 Resource Monitors events 35 operating systems, supported 18 response file dircon.rsp 67, 69, 71, 79, 81 modifying 67, 69, 71, 79, 81
S scenarios 1 Server Configuration Manager operating systems, supported 20 Server Storage Provisioning Tool operating systems, supported 25 ServeRAID Manager managed system, installing on 98, 104 Service Location Protocol 118 service packs v service processor 42 Power Management 24 service processors 22 documentation v generating events 32 shortcut keys 147 silent parameter 74, 82, 102, 106 SMBIOS 7 SNMP generating events 32 SNMP Access and Trap Forwarding enabling on Linux 140 SNMP devices definition 1 operating systems, supported 18 snmpconf utility 140 snmpd.conf file 140 Index
179
software components (illustration) 2 software distribution preferences, configuring 137 upgrading IBM Director Agent software package, installing 86, 109 Software Distribution operating systems, supported 18 Software Distribution task installing IBM Director Agent 107 software packages creating 85, 108 SQL database 28 starting programs with event action plans 35 Storage products, supported tasks 28 structure event action plan 36 event filters 36 System Accounts operating systems, supported 18 System i preparing, for installation 39
T tasks event action plans 35 management server support 17 operating systems, supported 17 publishing events 36 User Administration 112 terminology alert 32 event 32 managed system 1 management console 2 management server 1 notification 32 resolution 32 SNMP device 1 thresholds event action plans 35 toolbar User Administration 112 trademarks 164
U unattended installations IBM Director Console 74 unattended parameter 74, 82, 102, 106 uninstalling IBM Director Windows 145 Update Manager operating systems, supported 18 upgrading IBM Director Agent Windows 103 Software Distribution task, using 85, 108 user IDs operating system 112 profiles 112
180
User Administration task 112
V VMware authorizing, request access
113
W Wake on LAN 22 enabling on AIX 89 enabling on Windows IBM Director Agent, installing 100, 104 IBM Director Server, installing 57 Power Management 24 Web site IBM Director resources v IBM Redbooks v IBM ServerProven v IBM Support v IBM Systems Management Software v IBM xSeries Systems Management v Web sites Net-SNMP 140 windows IBM Director Console IBM Update Assistant 85, 108 Windows event log generating events 32 installing IBM Director Core Service 81 windows (IBM Director) IBM Director Agent installation (NetWare) Choose destination location 98 InstallShield Wizard complete 98 Select Components 98 IBM Director Agent installation (Windows) 100 Feature and destination directory selection 100 Network driver configuration 100 Security settings 100 Software Distribution settings 100 IBM Director Console Add Share Name 138, 139 IBM Update Assistant 85, 108 IBM Update Package/Root Directory 85, 108 Managed System Distribution Preferences 139 New Scheduled Job 86, 109 Server Preferences 138 Software Distribution Manager (Premium Edition) 85, 108 Software Distribution Manager (Standard Edition) 85, 108 Software Distribution Preferences 137 IBM Director Console installation Feature and destination directory selection 73
IBM Director Express Planning, Installation and Configuration Guide
windows (IBM Director) (continued) IBM Director Server installation 57 DB2 Universal Database configuration 57 Encryption settings 57 Feature and installation directory selection 57 IBM Director database configuration 57 Microsoft SQL database configuration 57 Network driver configuration 57 Oracle database configuration 57 service account information 57 Software-distribution settings 57 Windows installation encryption, enabling 57, 100 IBM Director Agent 99 IBM Director Console 72 IBM Director Server 57 uninstalling 145 Windows Management Instrumentation (WMI) generating events 32 Windows XP preparing managed system 53 Wired for Management (WfM) specifications 7 wizards Event Action Plan 35 InstallShield IBM Director Agent 100 IBM Director Console 73 IBM Director Server 57
X xSeries xSeries xSeries xSeries xSeries
225, 226, 236, 336, 346,
machine machine machine machine machine
type type type type type
8647 8836 8841 8837 8840
44 44 44 44 44
Readers’ Comments — We’d Like to Hear from You IBM Systems IBM Director Express Planning, Installation and Configuration Guide Version 5.20 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
Address
Company or Organization Phone No.
E-mail address
___________________________________________________________________________________________________
Readers’ Comments — We’d Like to Hear from You
Cut or Fold Along Line
_ _ _ _ _ _ _Fold _ _ _and _ _ _Tape _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please _ _ _ _ _do _ _not _ _ staple _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold _ _ _and _ _ Tape ______ 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 Dept. CGFA PO Box 12195 Research Triangle Park, NC 27709-9990
_________________________________________________________________________________________ Please do not staple Fold and Tape Fold and Tape
Cut or Fold Along Line
Printed in USA
Related Documents
Dir5.20 Docs Express Install
December 2019 5
Install Shield Express
May 2020 3
Vario Express Install
May 2020 5
Express
November 2019 55
Express
November 2019 59