Dir5.20 Docs Express Install

IBM Systems
IBM Director Express
Planning, Installation and Configuration Guide
Version 5.20

IBM Systems
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 Installing IBM Director Server on Linux for
Conventions and terminology . . . . . . . . v System z using the Express installation option . 63
Related information . . . . . . . . . . . . v Adding Standard installation options to an IBM
How to send your comments . . . . . . . . viii Director Express installation . . . . . . . . . 65
New in version 5.20 . . . . . . . . . ix Chapter 5. Installing IBM Director

Console . . . . . . . . . . . . . . 67
Chapter 1. Getting started with IBM Installing IBM Director Console on AIX . . . . . 67
Director . . . . . . . . . . . . . . . 1 Installing IBM Director Console on Linux for
System x . . . . . . . . . . . . . . . 69
Introducing IBM Director . . . . . . . . . . 1
Installing IBM Director Console on Linux for
IBM Director components . . . . . . . . . . 2
System z . . . . . . . . . . . . . . . 70
IBM Director Core Services . . . . . . . . 3
Installing IBM Director Console on Linux for
IBM Director Agent . . . . . . . . . . . 4
POWER . . . . . . . . . . . . . . . 71
IBM Director Console . . . . . . . . . . 4
Installing IBM Director Console on Windows . . . 72
IBM Director Server . . . . . . . . . . . 5
Installing IBM Director Console using the
InstallShield wizard . . . . . . . . . . 73
Chapter 2. Planning . . . . . . . . . . 7 Performing an unattended installation of IBM
Specified operating environments . . . . . . . 7 Director Console on Windows . . . . . . . 74
Hardware requirements for IBM Director . . . . 7
Network requirements . . . . . . . . . . 10
Chapter 6. Installing Level 1: IBM
Supported operating systems . . . . . . . 13
Support of IBM Director tasks across operating Director Core Services . . . . . . . . 77
systems . . . . . . . . . . . . . . . 17 Installing Level 1: IBM Director Core Services on
IBM Director task support for BladeCenter Linux for System x . . . . . . . . . . . . 77
products . . . . . . . . . . . . . . 26 Installing Level 1: IBM Director Core Services on
IBM Director task support for Storage products 27 Linux for System z . . . . . . . . . . . . 78
Supported database applications . . . . . . 28 Installing Level 1: IBM Director Core Services on
Licensing requirements for IBM Director Linux for POWER . . . . . . . . . . . . 79
components and extensions . . . . . . . . . 29 Installing Level 1: IBM Director Core Services on
Planning to install IBM Director . . . . . . . 31 Windows . . . . . . . . . . . . . . . 81
Choosing where to install IBM Director Server . . 31 Installing Level 1: IBM Director Core Services on
Planning for events . . . . . . . . . . . . 32 Windows using the InstallShield wizard . . . . 81
Planning events to be monitored . . . . . . 33 Performing an unattended installation of Level 1:
Planning for event action plan implementations 34 IBM Director Core Services on Windows . . . 82
Installing IBM Director Core Services using the
Software Distribution task . . . . . . . . . 83
Chapter 3. Installing . . . . . . . . . 39
Creating a software package . . . . . . . . 85
Preparing to install IBM Director . . . . . . . 39
Installing a software package . . . . . . . 86
Preparing the management server . . . . . . 39
Preparing a Level-1 managed system . . . . . 49
Preparing to manage a BladeCenter . . . . . 50 Chapter 7. Installing Level 2: IBM
Preparing Windows XP managed systems . . . 53 Director Agent . . . . . . . . . . . 89
Installing Level 2: IBM Director Agent on AIX . . . 89
Chapter 4. Installing IBM Director using Installing Level 2: IBM Director Agent on i5/OS . . 91
Installing IBM Director Agent using the
the Express installation . . . . . . . 55
Virtualization Engine . . . . . . . . . . 91
Installing IBM Director Server using the Express
Installing IBM Director Agent on i5/OS using
installation . . . . . . . . . . . . . . 55
RSTLICPGM . . . . . . . . . . . . . 92
Installing IBM Director Server on AIX using the
Installing Level 2: IBM Director Agent on Linux for
Express installation . . . . . . . . . . . 55
System x . . . . . . . . . . . . . . . 92
Installing IBM Director Server on Windows using
the Express InstallShield wizard . . . . . . 57
System z . . . . . . . . . . . . . . . 94
Installing IBM Director Server on Linux on
POWER using the Express installation option . . 59
POWER . . . . . . . . . . . . . . . 95
Installing IBM Director Server on Linux for
System x using the Express installation option . 61
© Copyright IBM Corp. 1999, 2006 iii

Installing Level 2: IBM Director Agent on Linux for Configuring discovery preferences for SMI-S
Intel Itanium (64 bit) . . . . . . . . . . . 97 storage devices . . . . . . . . . . . . 127
Installing Level 2: IBM Director Agent on NetWare 98 Configuring discovery preferences for SNMP
Installing Level 2:IBM Director Agent on 32-bit devices . . . . . . . . . . . . . . 130
Windows . . . . . . . . . . . . . . . 99 Configuring discovery preferences for hardware
Installing Level 2: IBM Director Agent on 32-bit management consoles . . . . . . . . . 133
Windows using the InstallShield wizard . . . . 99 Configuring discovery preferences for z/VM
Performing an unattended installation of Level systems . . . . . . . . . . . . . . 134
2: IBM Director Agent on 32-bit Windows . . . 102 Performing server-initiated discovery of managed
Installing Level 2: IBM Director Agent on 64-bit objects . . . . . . . . . . . . . . . . 136
Windows (Intel Itanium only) . . . . . . . . 103 Configuring software-distribution preferences . . 137
Installing Level 2: IBM Director Agent on 64-bit Setting up file-distribution servers . . . . . 137
Windows (Intel Itanium only) using the Configuring IBM Director to use a
InstallShield . . . . . . . . . . . . . 104 file-distribution server . . . . . . . . . 138
Performing an unattended installation of Level Configuring software-distribution preferences
2: IBM Director Agent on 64-bit Windows (Intel for managed systems . . . . . . . . . . 139
Itanium only) . . . . . . . . . . . . 106 Enabling SNMP access and trap forwarding for
Installing IBM Director Agent using the Software Linux . . . . . . . . . . . . . . . . 140
Distribution task . . . . . . . . . . . . 107 Enabling SNMP access and trap forwarding for
Creating a software package . . . . . . . 108 Linux managed systems . . . . . . . . . 141
Installing a software package . . . . . . . 109 Enabling SNMP access and trap forwarding for
Red Hat Enterprise Linux versions 3 and 4 . . 141
Chapter 8. Initially configuring IBM Enabling SNMP access and trap forwarding for
Director . . . . . . . . . . . . . . 111 VMware . . . . . . . . . . . . . . 142
Configuring IBM Director after an Express
installation . . . . . . . . . . . . . . 111 Chapter 9. Uninstalling IBM Director
Adding new users in IBM Director . . . . . . 112 on Windows . . . . . . . . . . . . 145
Authorizing Request Access on a managed system 113 Uninstalling IBM Director using the Windows
Enabling Lightweight Directory Access Protocol Add/Remove Programs feature . . . . . . . 145
authentication for IBM Director users . . . . . 113 Uninstalling IBM Director using the dirunins
Using IBM Director in a high-availability command . . . . . . . . . . . . . . 145
environment . . . . . . . . . . . . . . 114
Preparing a high-availability environment for Appendix A. Accessibility features for
IBM Director and IBM Tivoli System IBM Director . . . . . . . . . . . . 147
Automation for Multiplatforms . . . . . . 115
Preparing a high-availability environment for
IBM Director and SteelEye’s LifeKeeper . . . 116 Appendix B. Lightweight Directory
Configuring IBM Director for a high-availability Access Protocol authentication
environment . . . . . . . . . . . . . 116 properties for IBM Director Server . . 159
Configuring discovery preferences . . . . . . 118
Configuring discovery preferences for Appendix C. Notices . . . . . . . . 163
BladeCenter chassis . . . . . . . . . . 118 Trademarks . . . . . . . . . . . . . . 164
Configuring discovery preferences for Level-0
managed systems . . . . . . . . . . . 120
Glossary . . . . . . . . . . . . . 167
managed systems . . . . . . . . . . . 122 Glossary . . . . . . . . . . . . . . . 167
managed systems . . . . . . . . . . . 123 Index . . . . . . . . . . . . . . . 177
Configuring discovery preferences for physical
platforms . . . . . . . . . . . . . . 125
iv IBM Director Express Planning, Installation and Configuration Guide

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 4.22 Upward Integration Modules (UIMs)
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
&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
&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 IBM System x3655
v IBM System x3755
v IBM System x3200
v IBM System 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 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 Monitor hardware status.
v Reboot or shut down the managed system.
v Run command-line programs.
v Distribute system update packages through Software Distribution
v 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
The function of IBM Director Agent on the managed system will vary depending
on the operating system and platform.
IBM Director Console

IBM Director Console is installed on a desktop computer, workstation, or mobile
computer to provide a GUI in which the system administrator can perform tasks in
IBM Director.

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

IBM Director Server must be installed on the management server, and provides all
the management function of IBM Director.
IBM Director Server is the main component of IBM Director; it contains the
management data, the server engine, and the application logic. IBM Director Server
provides basic functions such as discovery of managed objects, persistent storage
of configuration and management data, an inventory database, event listening,
security and authentication, management console support, and administrative
tasks.
IBM Director Server stores the inventory data in a Structured Query Language
(SQL) database. You can access information that is stored in this relational database
even when the managed objects are not available.
Every IBM System x server and IBM BladeCenter unit includes an IBM Director
Server license. You can purchase additional IBM Director Server licenses for
installation on non-IBM servers.
IBM Director Server communicates with managed objects and SNMP devices to
receive information and issue commands. If IBM Director Console is used, IBM
Director Server communicates with IBM Director Console to display network status
information and receive instructions from the system administrator.
Chapter 1. Getting started with IBM Director 5

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.

Table 1. x86-compatible systems: Minimum hardware requirements
IBM Director Core
Requirements Services IBM Director Agent IBM Director Console IBM Director Server
®
Microprocessor Pentium-class Pentium-class or Pentium 1.5 GHz Pentium 1.5 GHz
speed processor Itanium® 2 processor
Memory (RAM) 128 MB 128 MB 256 MB 512 MB (minimum)
1024 MB
(recommended)
Disk space 40 MB (for Windows) 110 MB (for Windows) 170 MB 325 MB
100 MB (for Linux) 165 MB (for Linux)

Display Not applicable Not applicable At least 256 colors At least 256 colors
Hardware requirements for servers running AIX

memory (RAM), and disk space requirements on servers running AIX, including
System i and System p servers, and JS20 and JS21 blade servers.

default selections.
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) 185 MB (/opt) (Includes the 325 MB (/opt)
disk space required for IBM
3 MB (/usr) Director Agent.) 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

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.

default selections.

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
IBM Director Core
Requirements Services IBM Director Agent IBM Director Console IBM Director Server
Microprocessor Power4 or Power5 1.5 Power4 or Power5 1.5 Power4 or Power5 1.5 Power4 or Power5 1.5
speed GHz GHz GHz 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.

default selections.
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

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
IBM Director Server
(with or without IBM Director Agent
CIM instrumentation with CIM
for z/VM instrumentation for
manageability access IBM Director z/VM manageability
Requirement point) Console IBM Director Agent access point
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
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.

Table 7. Types of data transmission and supported network protocols
Operating system Supported
Type of data transmission running on managed network
system 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 Connection Destination port
IBM Director IBM Director Server ←→ IBM Director Agent 14247 UDP and TCP1 on
interprocess page 13; 14248 TCP; 4490 IPX (read);

communication 4491 IPX (write)
IBM Director → IBM Director Server 2033 TCP

Console
DIRCLI client ←→ IBM Director Server 2044 TCP
DIRCMD client ←→ IBM Director Server 2034 TCP
IBM Director → IBM Director Any free port (for use of
Console Console BladeCenter Network
Device Manager)
IBM Director → IBM Director Server 4066 TCP
Console over SSL
DIRCLI client ←→ IBM Director Server
Table 8. Ports used by IBM Director (continued)
CIM-XML over IBM Director Server → Level-1 or Level-2 15988 TCP (SUSE Linux
HTTP2 on page 13,3 managed system, or distributions and Red
on page 13 SMI-S storage Hat Linux for System z
device distributions)
5988 TCP (other

operating systems)
CIM-XML over IBM Director Server → Level-1 or Level-2 15989 TCP (SUSE Linux
HTTPS2 on page 13,3 managed system, or distributions and Red
on page 13 SMI-S storage Hat Linux for System z
device distributions)
5989 TCP (other

operating systems)
CIM Listener2 on CIMOM → CIM Listener 6988 TCP (HTTP)
page 13,3 on page 13
HTTP IBM Director Server → BladeCenter switch 80 TCP

module
Microsoft IBM Director Server → Level-0 system 137 UDP; 138 UDP; 139
Windows TCP; 445 TCP
DCOM
ServeRAID ServeRAID CIM → ServeRAID Manager 34572 TCP
interprocess Provider
communication
Service IBM Director Server ←→ service processor 6090 TCP
processors
Service processor → IBM Director Server 13991 UDP
(alerts)
IBM Director Server → service processor 623 and 664 UDP
(ASF, ASF 2.0, and
IPMI)
Service processor → IBM Director Server Random port in the
(ASF, ASF 2.0, and 1024-65535 range4 on page 13
IPMI)
SLP IBM Director Server ←→ SLP service agents 427 TCP and UDP
or SLP directory
agents
SNMP IBM Director Server → SNMP agent 161 TCP and UDP1 on page
13
SNMP agent → IBM Director Server 162 TCP and UDP1 on page
13
SSH IBM Director Server → SNMP devices 22 TCP

(Remote Session
task)
IBM Director Server → Level-0 system 22 TCP

Table 8. Ports used by IBM Director (continued)
Telnet IBM Director Server → BladeCenter 23 TCP
management
module
IBM Director Server → BladeCenter switch 23 TCP
module
IBM Director Server → SNMP devices 23 TCP
(Remote Session
task)
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/ .
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
IBM
IBM IBM IBM Director
Director Director Director Core
Operating system Console Server Agent Services
Editions of Windows for 32-bit systems:
Windows 2000, Advanced Server and Server Editions (Service Pack 3 X X X X
required)
Windows 2000 Datacenter Edition X X
Windows 2000 Professional Edition (Service Pack 3 required) X X X
Windows Server 2003 Datacenter Edition (supports Service Pack 1 ) X X
Windows Server 2003, Enterprise, Standard, and Web Editions (supports X X X X
Service Pack 1 and Release 2)
Windows XP Professional Edition (supports Service Pack 2 and earlier) X X X
Windows Server 2003 Datacenter Edition for Itanium systems

Table 9. Operating systems supported by IBM Director on System x systems and third-party Intel-based
systems (continued)
IBM
Windows Server 2003 Datacenter x64 Edition (supports Release 2 and X X
earlier)
Windows Server 2003 Enterprise Edition for Itanium systems
Windows Server 2003, Enterprise, Standard, and Web x64 Editions X X X X
(supports Release 2 and earlier)
Windows XP Professional x64 Edition (supports Release 2 and earlier) X X
Versions of Linux for 32-bit systems:
Red Hat Enterprise Linux AS and ES, version 3.0 (supports Update 7 and X X X X
earlier)
Note: (Level-2 and Level-1 support only) For systems that contain an
AMD Opteron or Athlon64 processor, Update 5 or later is required.
Red Hat Enterprise Linux WS, version 3.0 (supports Update 7 and earlier) X X
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 X X X
earlier)
Red Hat Enterprise Linux WS, version 4.0 (supports Update 3 and earlier) X X
SUSE Linux Enterprise Server 9 for x86 (supports Service Pack 3 and X X X X
earlier)
SUSE Linux Enterprise Server 10 for x86 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 X X
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, guest X X X 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.
VMware GSX Server, versions 3.1 and 3.2, guest operating systems X X
VMware GSX Server, versions 3.1 and 3.2, host operating systems X X
Note: Supported host operating systems are those that are supported by
Red Hat Enterprise Linux AS, version 3.0, for Intel Itanium
Red Hat Enterprise Linux AS and ES, version 3.0, for AMD64 and EM64T X X
(supports Update 7 and earlier)
Red Hat Enterprise Linux WS, version 3.0, for AMD64 and EM64T X X
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 X X X
Table 9. Operating systems supported by IBM Director on System x systems and third-party Intel-based
systems (continued)
IBM
Red Hat Enterprise Linux WS, version 4.0, for AMD64 and EM64T X X
SUSE Linux Enterprise Server 9 for AMD64 and EM64T (supports Service X X X 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
Other operating systems supported by System x servers:
Microsoft Virtual Server (guest operating system) (Release 2 required) X X
both IBM Director and the specified version of Microsoft. See the
Microsoft product documentation for a list of supported operating
systems.
NetWare, version 6.5 X
Note: Level-0 support is not provided.
Table 10. Operating systems supported by IBM Director on System i and System p products
IBM
AIX 5L, Version 5.2 (supports ML05 or later) X
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) X X X
i5/OS, Version 5 Release 3 X X
i5/OS, Version 5 Release 4
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 X X X X
required)
SUSE Linux Enterprise Server 10 for IBM POWER X X X X
Table 11. Operating systems supported by IBM Director on System z systems

IBM
Red Hat Enterprise Linux AS, version 4.0, for IBM System z (supports X X X X
Update 4 and earlier)

Table 11. Operating systems supported by IBM Director on System z systems (continued)
IBM
SUSE Linux Enterprise Server 9 for IBM System z (supports Service Pack X X X X
3 and earlier)
SUSE Linux Enterprise Server 10 for IBM System z X X X X
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
Task Server Linux and Windows only
™
Asset ID 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 X
Console
Task is supported on the following operating systems:
All operating systems
supported by IBM Director
Task Server Linux and Windows only
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 X
Tool
SNMP Browser X
Software Distribution X
Storage Configuration X
Manager
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.

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
Microsoft
ESX Server Virtual
Task Windows Linux GSX Server i5/OS AIX NetWare Server
1 1, 2
Asset ID Level 2 Level 2 Level 2 Level 2 No No Level 2
1 1
CIM Manager Level 2 Level 2 Level 2 Level 2 Level 2 No Level 2
Configuration See “Operating systems supported by the Configuration Manager task”
Manager
Configure Level 21 Level 21, 5 Level 2 Level 2 Level 2 No Level 2
SNMP Agent
Event Log Levels 1, 2 Levels 1, 2 Levels 1, 2 Levels 1, 2 Levels 1, 2 Levels 1, 2 Levels 1, 2
External See “Operating systems supported by External Application Launch”
Application
Launch
14
File Transfer Level 2 Level 2 Level 2 Level 2 Level 2 Level 2 Level 2
Hardware See “Operating systems supported by the Hardware Status task”
Status
Inventory Levels 0, 1, Levels 0, 1, Levels 0, 1, 2 Level 2 Level 27 Level 27 Levels 0, 1, 2
15
(hardware) 26, 7 26, 7
Inventory Levels 0, 1, Levels 0, 1, Levels 0, 1, 2 Level 2 No Level 2 Levels 0, 1, 2
(software) 26 26
Microsoft Level 28 No No No No No No
Cluster
Browser
Network Level 21 Level 21, 9 Level 2 Level 2 No No Level 2
Configuration
Power See “Operating systems supported by the Power Management task”
Management
Process Level 2 Level 2 Level 2 Level 2 Level 2 Level 2 Level 2
Management
Rack Manager Level 210 Level 24, 10 Level 2 No No Level 2 Level 2
13
11
Remote Level 2 No Level 2 No No No Level 2
Control
Remote Level 2 Level 2 Level 2 Level 2 Level 2 Level 2 Level 2
Session
Resource Level 2 Level 2 Level 2 Level 2 Level 2 Level 2 Level 2
Monitors
Server Storage See “Operating systems supported by IBM Server Storage Provisioning Tool”
Provisioning
Tool
SNMP Level 2 Level 2 Level 2 Level 2 Level 2 Level 2 Level 2
Browser
Operating systems
Microsoft
ESX Server Virtual
Task Windows Linux GSX Server i5/OS AIX NetWare Server
Software Levels 0, 1, 2 Levels 0, 1, 2 Levels 0, 1, 2 Levels 0, 2 Levels 0, 1, 2 No Levels 0, 1, 2
12
Distribution
2,
Storage Levels 1, 2 Levels 1, 2 Levels 1, 2 No No No Levels 1, 2
Configuration 9
Manager
System Level 21 Level 21, 9 Level 2 Level 2 No No Level 2
Accounts
Update Levels 0, 1, 2 Levels 0, 1, 2 Levels 0, 1, 2 No No No Levels 0, 1, 2
2, 9
Manager
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 Level 1 Level 2

Table 12. Hardware Status support for System x servers; IBM and third-party x86-based systems (continued)
v Windows 2000, Advanced Server, Datacenter, Professional, and Server Editions Yes Yes
v Windows XP Professional Edition
v Windows Server 2003, Datacenter, Enterprise, Standard, and Web x64 Editions Yes Yes
v Windows XP Professional x64 Edition
Windows Server 2003, Datacenter and Enterprise 64-bit Itanium Editions No No
v Red Hat Enterprise Linux AS, ES, and WS, version 3.0 Yes Yes1
v Red Hat Enterprise Linux AS, ES, and WS, version 4.0
v SUSE Linux Enterprise Server 9 for x86
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 (For (For
v VMware GSX Server, versions 3.1 and 3.2, guest operating systems Console) Console)
Yes1 (For Yes1 (For
guest) guest)
Limited Limited
1
v Red Hat Enterprise Linux AS, ES, and WS, version 3.0, for AMD64 and EM64T Yes Yes
v Red Hat Enterprise Linux AS, ES, and WS, version 4.0, for AMD64 and EM64T
v SUSE Linux Enterprise Server 9 for AMD64 and EM64T
v SUSE Linux Enterprise Server 10 with Xen Kernel
v Red Hat Enterprise Linux AS, version 3.0, for Intel Itanium No No
v Red Hat Enterprise Linux AS, version 4.0, for Intel Itanium
v SUSE Linux Enterprise Server 9 for Itanium Processor Family
Microsoft Virtual Server (guest operating system) Limited Limited
2 3
NetWare, version 6.5 Yes Yes
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
v AIX 5L, Version 5.2 No No
v AIX 5L, Version 5.3
v i5/OS, Version 5 Release 3 No Yes1

v i5/OS, Version 5 Release 4
v Red Hat Enterprise Linux AS, version 4.3 and 4.4, for IBM POWER Yes1 Yes1
v SUSE Linux Enterprise Server 9 for IBM POWER
1. (BladeCenter JS20 and JS21 only) Out-of-band notifications generated by a service processor only.
Table 14. Hardware Status support for System z servers
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z No No
v SUSE Linux Enterprise Server 9 for IBM System z
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
v Windows 2000, Advanced Server, Datacenter, Professional, and Server Editions Yes, Restart
v Windows XP Professional Edition and
v Windows Server 2003, Datacenter, Enterprise, Standard, and Web Editions Shutdown
v Windows Server 2003, Datacenter, Enterprise, Standard, and Web x64 Editions Yes, Restart
v Windows XP Professional x64 Edition and
v Windows Server 2003, Datacenter and Enterprise 64-bit Itanium Editions Shutdown

Table 15. Operating systems supported by System x servers and third-party Intel-based systems (continued)
v Red Hat Enterprise Linux AS, ES, and WS, version 3.0 Yes, Restart
v VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, Console
v 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 Yes, Restart
v VMware GSX Server, versions 3.1 and 3.2, guest operating systems (for Linux)
and Restart
and
Shutdown
(for
Windows)
v Red Hat Enterprise Linux AS, ES, and WS, version 3.0, for AMD64 and EM64T Yes, Restart
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
Table 16. Operating systems supported by System i platforms and System p servers
1
v i5/OS, Version 5 Release 3 No
v AIX 5L, Version 5.2 Yes, Restart
v Red Hat Enterprise Linux AS, version 4.3 and 4.4, for IBM POWER
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

v Red Hat Enterprise Linux AS, version 4.0, for IBM System z Yes, Restart
Power Management-support provided by service processors:
Support for the Power Management task can be provided by System x service
processors that can communicate out of band.
The following service processors in IBM System x servers and blade servers
provide support for the Power Management task using out-of-band
communication:
v Remote Supervisor Adapter
v Remote Supervisor Adapter II
v IPMI baseboard management controller (BMC)
These service processors provide support for the Power On, Restart Now, and
Power Off Now subtasks. Out-of-band communication does not require IBM
Director Core Services or IBM Director Agent, 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
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
v Windows 2000, Advanced Server, Datacenter, Professional, and Server Editions Yes
v Windows Server 2003, Datacenter, Enterprise, Standard, and Web x64 Editions Yes
v Windows Server 2003, Datacenter and Enterprise 64-bit Itanium Editions
v Red Hat Enterprise Linux AS, ES, and WS, version 3.0 Yes

Table 18. Operating systems supported by System x servers and third-party Intel-based systems (continued)
v VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, Console No
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, Console
v VMware GSX Server, versions 3.1 and 3.2, guest operating systems
v Red Hat Enterprise Linux AS, ES, and WS, version 3.0, for AMD64 and EM64T Yes
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
v Windows 2000, Advanced Server, Datacenter, Professional, and Server Editions Yes Yes Yes
v Windows Server 2003, Datacenter, Enterprise, Standard, and Web x64 Editions No No Yes
Windows Server 2003, Datacenter and Enterprise 64-bit Itanium Editions No No No
v Red Hat Enterprise Linux AS, ES, and WS, version 3.0 Yes Yes Yes
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, and 3.0, Console 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 No Yes
systems
v VMware GSX Server, versions 3.1 and 3.2, Console No No No
v VMware GSX Server, versions 3.1 and 3.2, guest operating systems
Table 19. IBM Server Storage Provisioning Tool support for System x servers; IBM and third-party x86-based
systems (continued)
v Red Hat Enterprise Linux AS, ES, and WS, version 3.0, for AMD64 and EM64T No No Yes
v Red Hat Enterprise Linux AS, version 3.0, for Intel Itanium No No No
Microsoft Virtual Server (guest operating system) No No No
NetWare, version 6.5 No No No
Table 20. IBM Server Storage Provisioning Tool support for System i platforms and System p servers
v AIX 5L, Version 5.2 No No No
v i5/OS, Version 5 Release 3 No No No

v Red Hat Enterprise Linux AS, version 4.3 and 4.4, for IBM POWER No No No
Table 21. IBM Server Storage Provisioning Tool support for System z servers
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z No No No
IBM Director task support for BladeCenter products

IBM Director tasks provide support for BladeCenter products. The support can
vary depending on whether it is for the BladeCenter chassis, network devices, and
blade servers.
A BladeCenter unit consists of a chassis, one or two management modules, one or

more network devices (previously called switches, up to a total of four), and one
or more blade servers (up to a total of 14, depending on the model).
The chassis is the physical enclosure that contains the blade servers. The chassis
has one or two management modules that contain a service processor. IBM
Director discovers the chassis and gathers information from the chassis by way of
the management module. You cannot install IBM Director Agent or IBM Director
Core Services on the chassis.

The network device is an SNMP device, and IBM Director considers the network
device to be a managed device. When you view the network device in IBM
Director, it might be displayed in the RMON devices group, which is a subgroup
of the SNMP devices group.
IBM Director can gather some information from a blade server before IBM Director
Agent or IBM Director Core Services is installed on the blade server. The
information is gathered from the blade server by way of the chassis management
module. In IBM Director Console, the blade server is represented by a physical
platform managed object. However, after you install IBM Director Agent or IBM
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 Blade server without IBM Director Agent
device or IBM Director Core Services installed
BladeCenter Configuration Manager Yes No Not applicable
Event Action Plans Yes Yes Yes
1
Hardware Status Yes No Yes
Inventory Yes Yes Yes
Network Device Manager (formerly Not applicable Yes Not applicable
Switch Management launch pad)
Power Management No No Yes
Rack Manager Yes Yes No
Remote Session Not applicable Yes No
Remote Monitors No Yes No
2
SNMP Browser No Yes Yes
1. Inventory of the chassis, network device, and blade servers can be obtained through the management module.
Blade server inventory that is collected through the management module is a subset of the total inventory that is
available if IBM Director Agent or IBM Director Core Services is installed on the blade server.
2. To use the SNMP Browser task, the operating-system SNMP agent must be installed on the blade server.
IBM Director task support for Storage products

IBM Director provides limited task support for Storage products.
Table 23. IBM Director task support for Storage products
Tasks and features DS300 DS6000
DS400 QLogic BladeCenter switches
DS4000
Brocade 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
Supported database
Database versions AIX i5/OS Linux Windows
Apache v V10.1 (included with Embedded — Embedded Embedded
Derby IBM Director Server
on AIX, Linux, and
Windows)
IBM DB2 v version 8.2 with Fix Local or — Local or Local or
Universal Pack 5 remote remote remote
Database™ v version 8.1 with Fix
Pack 12
IBM DB2 Universal — Local — —
Database for System i
(part of i5/OS)
Microsoft v Microsoft SQL Server — — Remote Local or
SQL Server 2005 with Service remote
Pack 1
v Microsoft SQL Server
2000 with Service
Pack 4
v Microsoft SQL Server — — — Local
2005 Express Edition
with Service Pack 1
v Microsoft SQL Server
2000 Desktop Engine
(also called MSDE
2000) with Service
Pack 4

Table 24. Database applications supported by IBM Director 5.20 (continued)
Supported database
Database versions AIX i5/OS Linux Windows
Oracle v version 10g release 2 Local or — Local or Local or
v version 10g release 1 remote remote remote
(Oracle v version 9.2
Server)
PostgreSQL v version 8.1 — — Local or —
v version 7.4 remote
v version 7.3
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
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.”
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 IBM System z mainframes
v IBM System Storage Network Attached Storage (NAS) products
v IBM SurePOS point-of-sale systems
v IBM 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

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 Capacity Manager
v Remote Deployment Manager extension
v Software Distribution Premium Edition
v z/VM Center
External database
Installation of an external database is required for many IBM Director functions.

The Apache Derby database that is included with IBM Director (except on i5/OS),
and the IBM DB2® database that is part of the i5/OS operating system, are
databases you can use without obtaining additional licenses. If you use another
database, ensure that you have obtained any required license for the installation.
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
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)

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
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

– 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
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

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 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 5722-JV1

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.
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

– 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.
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 compat-libstdc++-7.3-2.96.122.i386.rpm
ES, version 3.0
Red Hat Enterprise Linux AS and compat-libstdc++-296-2.96-132.7.2.i386.rpm
ES, version 4.0
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
Important: You must install the device driver first and then install the mapping
layer.
v Make sure that the instance of IBM Director Agent will be fully functional and
able to send alerts to IBM Director Server. For the IBM Director Agent to be fully
functional you might need to install service-processor device drivers or the IBM
LM78 and SMBus device drivers for Linux.
v If you want to use the Remote Session task on the managed system, make sure
that the package that contains telnetd daemon is installed and configured. This
package is usually in the telnet_server_version.i386.RPM package, where version
is the code level of your Linux distribution.
v If you want to use IBM Director Server on System x for heterogeneous server
management, you can install IBM Director Agent or IBM Director Core Services
on the platforms you want to manage. You can obtain IBM Director Agent
andIBM Director Core Services for the supported operating systems from the
IBM Director Web site at www.ibm.com/systems/management/director/ or, if it
was included with your IBM Director distribution, from the IBM Director Agents
& Consoles, V5.20 (1 of 2) CD.
v 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

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 IPMI baseboard Remote
Operating system of management management Supervisor
managed server processor controller Adapter II
Red Hat v Red Hat OpenIPMI driver OpenIPMI driver RSA daemon, USB
Linux Enterprise drivers
Linux, version
3.0 (update 6)
v Red Hat
Enterprise
Linux, version
4.0 (update 3)
Other Red Hat MSI IPMI driver, OSA IPMI driver, RSA daemon, USB
Linux distributions IBM Mapping IBM Mapping drivers
Layer Layer
SUSE v SUSE Linux OpenIPMI driver OpenIPMI driver RSA daemon, USB
Linux Enterprise drivers
Server 9 for x86
Other SUSE Linux MSI IPMI driver, OSA IPMI driver, RSA daemon, USB
distributions IBM Mapping IBM Mapping drivers
Layer Layer
virtual systems using Xen OpenIPMI driver OpenIPMI driver RSA daemon, USB
drivers
VMware v VMware ESX OpenIPMI driver OpenIPMI driver USB drivers
Server, version
2.5.4, Console
v VMware ESX
Server, version
3.0, Console
Other VMware MSI IPMI driver, OSA IPMI driver, Not Supported
distributions IBM Mapping IBM Mapping
Layer Layer
Windows MSI IPMI driver, OSA IPMI driver, RSA library, USB
IBM Mapping IBM Mapping drivers
Layer Layer
3. Make sure that you have the latest firmware installed for your service
processors.
IBM LM78 and SMBus device drivers for Linux:
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
v The server is one of the following ensures that IBM Director
servers: Server receives memory and
processor Predictive Failure
– BladeCenter HS20, machine type 8832
Analysis® (PFA) alerts.
– xSeries 225, machine type 8647
v The server contains an integrated systems
management processor (ISMP).
SMBus If the server does not contain one of the The SMBus device driver
following service processors: ensures that the
v IPMI baseboard management controller Management Processor
Assistant tasks and System
Health Monitoring function
v Remote Supervisor Adapter II 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.

You must build the binary RPM file on a system with the same kernel version and
hardware configuration as the system on which you will install IBM Director
Server. Make sure that the hardware configuration is similar in regard to the
number of processors and that any previous versions of the drivers have been
uninstalled.
Note: If you are building on Red Hat Enterprise Linux ES, version 4.0 and the
/usr/src/linux does not exist, perform the following steps:
1. From a command prompt, change to the /usr/src directory.
2. Type the following command and press Enter:
ln -s ./kernels/<version>/ ./linux
where <version> is the appropriate kernel subdirectory under

/usr/src/kernels (for example, 2.6.9-5.EL-smp-i686), which matches the
kernel the system is currently running.
To build either the LM78 or SMBus device driver, complete the following steps:
1. 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).
Note: In this procedure, driver is one of the following strings:

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.

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.

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
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
rpm -e ibmsmb
2. To uninstall the source RPM file, open a command prompt, type the following
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
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.
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.

v Ensure that the following RPMs are installed.
Table 29. Required RPMs
Red Hat 31-bit compat-libstdc++-295-2.95.3-81.s390.rpm
Enterprise Linux compat-libstdc++-33-3.2.3-47.3.s390.rpm
AS, version 4.0 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 31-bit compat-2004.7.1-1.2.s390.rpm
Enterprise
64-bit compat-2004.7.1-1.2.s390x.rpm
Server 9 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 64-bit compat-32bit-2006.1.25-11.2.s390x.rpm
Enterprise pam-32bit-0.99.3.0-29.4.s390x.rpm
Server 10 for pam-modules-32bit-10-2.2.s390x.rpm
IBM System z 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
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.

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 Management Processor Command-Line Interface (MPCLI)
Preparing to manage a BladeCenter chassis using IBM Director

Server on a blade server
You can install IBM Director Server on a blade server. With this management
server you can manage the BladeCenter unit, including the server on which IBM
Director Server is installed, and other BladeCenter units. You must configure the
network to allow this installation.
Consider the following issues when managing the BladeCenter unit that contains
the management server:
v Enable access for authorized administrators as determined by the security policy
established for the user environment.
v Be careful when making changes to the configuration of the BladeCenter chassis
from IBM Director itself. Such changes could effectively remove the instance of
IBM Director Server from the network and halt the entire IBM Director
environment.
Specifically, do not perform these tasks on the blade server where IBM Director
Server is installed without careful consideration:
– Using Remote Deployment Manager (RDM) to deploy software to that blade
server
– Powering off that blade server
– Changing the boot options on that blade server
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/ .

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 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
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.

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.
To use the Express installation option to install IBM Director Server on AIX,
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
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.
./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

10. If you used the CD to install IBM Director Server, unmount the drive by
typing the following command and press Enter:
umount /mnt

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:
Server.
separate server.
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:
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.
6. Click Next. The License Agreement window opens.
7. Click I accept the terms in the license agreement; then, click Next. The
Installation Type window opens.
8. Click Perform an Express Installation of IBM Director Server; then, click
Next. The Destination Folder window opens.
9. 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.
Note: The information that you provide must correspond to a Windows

account with administrator privileges on the management server.
Otherwise, the installation will fail.
12. Click Next. The Encryption Settings window opens.
13. 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.
14. Click Next. The Software Distribution Settings window opens.
15. To select an alternative location for the creation of the software-distribution
packages, click Change and select another directory.

To select an alternative location for software-distribution packages that are
received from IBM Director Server are placed, click Change and select another
directory.
To select an alternative location for saved update packages, click Change and
select another directory.
16. Click Next. The Ready to Install the Program window opens.
17. 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.
18. Click Finish. A window opens, asking you if you want to restart the server.
19. Remove the CD from the drive.
20. Click Yes to restart the server.
Installing IBM Director Server on Linux on POWER using the

Express installation option
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:
Server.
separate server.
To install IBM Director Server on Linux on POWER, complete the following steps:

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.
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
cd /mnt/cdrom/director/server/linux/ppc/
where mnt/cdrom is the mount point of the drive.


installed.

installation.
11. To start IBM Director, type the following command and press Enter:

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

13. If you used a CD, remove the CD from the drive.
Installing IBM Director Server on Linux for System x using

the Express installation option
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:
Server.
separate server.
To use the Express installation option to install IBM Director Server on Linux for
System x, complete the following steps:
steps:

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.
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
where dev/cdrom is the specific device file for the block device and mnt/cdrom
is the mount point of the drive.
cd /mnt/cdrom/director/server/linux/i386/


installed.

installation.
12. If you used a CD, unmount the drive by completing the following steps:
umount /mnt/cdrom

13. If you used a CD, remove the CD from the drive.
Installing IBM Director Server on Linux for System z using the

Express installation option
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:
Server.
separate server.
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

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
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.
(dirserv.rsp) to a local directory:

installed.
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.

installation.

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.
To add the Standard installation options to an IBM Director Express installation,

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.
Note: If the Groups tab does not display, you must first create and authorize a
user group on the management server.
3. Select the group for which you want to enable the IBM Director tasks.
4. Click Actions → Group → Edit.
5. In the Group Editor window, click the Task Access tab to modify task access
for the user group.
6. To allow full access to all tasks, clear Limit user access only to the tasks
selected.
7. In the Group Editor window, click OK and then close the User Administration
window.

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:
separate server.
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:
to a local directory from the IBM Director downloads page at:
following command:

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
c. To change to the directory where IBM Director Console is located, type the
cd /mnt/director/console/aix

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/

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
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
umount /mnt

Remove the CD from the drive.

Installing IBM Director Console on Linux for System x
To install IBM Director Console on a system that is running Linux for System x,
download the installation files from theIBM Director support Web site or use the
CD. You can perform a standard installation or you can use a response file to
customize the installation for your environment.
To install IBM Director Console on Linux for System x, complete the following
steps:
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
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
cp dircon.rsp /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
./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.
a. Insert the IBM Director on x86, V5.20 or IBM Director Agents & Consoles,
V5.20 (2 of 2) CD into the drive.
where dev/cdrom is the specific device file for the block device and
mnt/cdrom is the mount point of the drive.
cd /mnt/cdrom/director/console/linux/i386
Chapter 5. Installing IBM Director Console 69

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
cp dircon.rsp /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
./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

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.
cd /mnt/director/console/linux/s390/

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:
the dircon.rsp file. This file is fully commented.
You can specify the location of the RPM files and select log file options.
7. To install IBM Director Console, type the following command and press Enter:
where directory is the local directory to which you copied the response file and
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
/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:
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.
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:

cd /mnt/cdrom/director/console/linux/ppc

Go to step 3.
Enter:
./dirinstall
Go to step 8.
4. To customize the installation, copy the response file (dircon.rsp) to a local

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
./dirinstall -r /directory/responsefile.rsp
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:
umount /mnt/cdrom

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

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
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
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.
Director Console using the keyboard, perform the
following steps:

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.
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.
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:

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.

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 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:
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.
cd /directory/FILES
Go to step 3.
cd /mnt/cdrom/coresvcs/agent/linux/i386/FILES

Go to step 3.
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

cp coresvcs.rsp /directory/

the coresvcs.rsp file. This file is fully commented.
7. To install Level 1: IBM Director Core Services using the response file, type the
./dir5.20_coreservices_linux.sh -r /directory/response.rsp
8. If you installed IBM Director Core Services from the CD, complete the
following steps to unmount the drive:
umount /mnt/cdrom

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:
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
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/

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.
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
cp coresvcs.rsp /directory

7. To install IBM Director Core Services using the response file, type the following
./csversion_agent_linz.sh -r /directory/response.rsp
8. Optional: Keep the response file for future use and reference.
(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
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/ .
Chapter 6. Installing Level 1: IBM Director Core Services 79

Go to step 3.
a. Insert the IBM Director for Linux on POWER, V5.20 or IBM Director for
AIX 5L, V5.20 CD into the drive.
cd /mnt/cdrom/coresvcs/agent/linux/ppc/FILES

Go to step 3.
Enter:
./cs5.20_agent_linppc.sh
Go to step 8.
4. To customize the installation, copy the response file (coresvcs.rsp) to a local
cp coresvcs.rsp /directory/

7. To install IBM Director Core Services using the response file, type the following
./cs5.20_agent_linppc.sh -r /directory/response.rsp
8. If you used a CD to install IBM Director Core Services, unmount the media
drive by completing the following steps:
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.
Net-SNMP, version 5.2.1.

Installing Level 1: IBM Director Core Services on Windows
To install Level 1: IBM Director Core Services on a system that is running
Windows, download the installation files from the IBM Director support Web site
or use the CD. You can perform a standard installation or you can use a response
file to customize the installation for your environment.
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,

containing the dir5.20_coreservices_windows.exe file and run the installation
program using the following command:
dir5.20_coreservices_windows.exe -a admin

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:
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
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.
a. Insert the IBM Director on x86, V5.20 into the drive.
window opens, go to step 3d on page 82. Otherwise, click Start → Run.
e:\setup.exe

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.
Director Core Services using the keyboard, perform the
following steps:
c. Browse to the coresvcs/agent/windows/i386/FILES
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.
5. Click I accept the terms in the license agreement and click Next. The
Destination Folder window opens.
To select an alternative location for the installation of IBM Director Core
Services, click Change and select another directory.
7. Click Install. The status bar displays the progress of the installation. When the
installation is completed, the InstallShield Wizard Completed window opens.
8. Click Finish.
9. If you installed IBM Director Core Services from the CD, remove the CD from
the drive.
Performing an unattended installation of Level 1: IBM Director

Core Services on Windows
You can perform an unattended installation of IBM Director Core Services using a
response file, which provides answers to the questions that are posed by the
InstallShield wizard. You can use this method to create a standard installation file
that can be used on many systems.
To use a response file to install Level 1: IBM Director Core Services on Windows,
a. Download the dir5.20_coreservices_windows.zip file from the IBM 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.
(1 of 2) CD into the drive.

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.
3. Open the copy of the coresvcs.rsp file in an ASCII text editor.
4. Modify and save the response file with a new file name. This file follows the
Windows INI file format and is fully commented.
5. Open a command prompt and change to the directory that contains the IBM
Director Core Services installation file (dir5.20_coreservices_windows.exe).
6. 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.
user input.
v responsefile.rsp is the path and name of the response file that you created in
step 4.
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
messages
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.

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.

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)

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:
2. In the Tasks pane, expand the Software Distribution task.
3. Click the software package that you want to distribute. Then, drag it into the
Group Contents pane and drop it onto the icon that is displayed for the system
on which you want to install the software package. A window opens.
Note: To distribute software to several systems at once, you can drag the
software package into the Groups pane and drop it onto the icon for the
group. Alternatively, you can select multiple managed systems in the
Group Contents pane.
4. When prompted with Do you wish to create a scheduled job for this task
or execute immediately?, click Schedule or Execute Now. If you click Execute
Now, the software package is distributed immediately. If you click Schedule,
the New Scheduled Job window opens.
5. Schedule the job:
a. In the Scheduled Job field, type a unique name for the job. This name is
displayed in the Jobs pane of the Scheduler window.

b. In the Date field, type the day you want the software package to be
installed (in MM/DD/YYYY format).
c. In the Time field, type the time you want the software package to be
installed.
For more information about the Scheduler task, see the IBM Director Systems
Management Guide.
6. Click OK. The Save Job Confirmation window opens.
7. Click OK.

Chapter 7. Installing Level 2: IBM Director Agent
After preparing your managed system, you can install IBM Director Agent.
Important:
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
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:
installed.
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:
to a local directory from the IBM Director downloads page at:
following command:
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.
mount /dev/cd0 /mnt
where dev/cd0 is the specific device file for the block device and mnt is the
cd /mnt/director/agent/aix/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:
./dir5.20_agent_aix.sh
Go to step 8.
4. To customize the installation, copy the response file (diragent.rsp) to a local
cp diragent.rsp /directory

the diragent.rsp file. This file is fully commented. You can specify the location
of the .bff files and select log file options.
7. To install IBM Director Agent using the response file, type the following
./dir5.20_agent_aix.sh -r /directory/response.rsp
where install_root is the root directory of your IBM Director installation.

9. To startIBM Director Agent, type the following command and press Enter:
10. If you installed IBM Director Agent from the CD, type the following
command and press Enter to unmount the drive:
umount /mnt
where mnt is the mount point of the drive. Remove the CD from the drive.
After IBM Director Agent is installed, you can enable the Wake on LAN feature. To
determine if your server supports this feature, review the server documentation.

Installing Level 2: IBM Director Agent on i5/OS
After preparing your system, you can install Level 2: IBM Director Agent on a
system that is running i5/OS (V5R3 or later) by downloading the installation files
from the IBM Director Web site or using the CD. You can use the Restore Licensed
Program (RSTLICPGM) command to perform the installation.
Important:
installed.
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:
installed.
To install Level 2: IBM Director Agent on Linux for System x, complete 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.
cd /directory/FILES

cd /mnt/cdrom/director/agent/linux/i386/FILES

Go to step 3.
Enter:
./dir5.20_agent_linux.sh
Go to step 8.

the diragent.rsp file. This file is fully commented.
./dir5.20_agent_linux.sh -r /directory/response.rsp

9. To start IBM Director Agent, type the following command and press Enter:
10. If you installed IBM Director Agent from the CD, complete the following steps
to unmount the drive:
umount /mnt/cdrom
where mnt/cdrom is the mount point of the CD-ROM drive. Remove the
CD from the drive.

After IBM Director Agent is installed, you can enable the Wake on LAN feature.
Installing Level 2: IBM Director Agent on Linux for 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:
installed.
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:
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/
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.
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.
4. To customize the installation, copy the response file to a local directory. Type

./dirversion_agent_linz.sh -r /directory/response.rsp
(AES) algorithm is enabled during installation. To disable encryption or change
security settings, type the following command and press Enter:

9. To start IBM Director Agent, begin a new terminal session, type the following
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:
installed.
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

a. Insert the IBM Director for AIX 5L, V5.20 or IBM Director for Linux on
POWER, V5.20 CD into the drive.
cd /mnt/cdrom/director/agent/linux/ppc/FILES

Go to step 3.
Enter:
./dir5.20_agent_linppc.sh
Go to step 8.

the diragent.rsp file. This file is fully commented. You can specify the location
of the RPM files and select log file options.
./dir5.20_agent_linppc.sh -r /directory/response.rsp

10. If you installed IBM Director Agent from the CD, perform the following steps
to unmount the drive:
umount /mnt/cdrom
where mnt/cdrom is the mount point of the drive. Remove the CD from the
drive.

Installing Level 2: IBM Director Agent on Linux for Intel Itanium

(64 bit)
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
2. Extract the dir5.10.3_agent_linux64.tar file into a local directory.
Enter:
./dir5.10.3_agent_linux64.sh
Go to step 8.

./dir5.10.3_agent_linux64.sh -r /directory/response.rsp

Installing Level 2: IBM Director Agent on NetWare
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 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
2. Extract the contents of the dir5.20_agent_netware.zip file to the Windows
workstation running NetWare Client for Windows.
3. Start Windows Explorer and open the \directory\FILES directory, where
directory is the location into which you extracted the contents of the
dir5.20_agent_netware.zip file.
4. Double-click the dir5.20_agent_netware.exe file. The InstallShield wizard
starts.
5. Click Next. The Installing IBM Director Agent window opens.
6. Click Next to accept the license agreement. The Choose Destination Location
window opens.
7. Click the drive that is mapped to the SYS volume on the server running
NetWare; then, click Next. The Select Components window opens.
IBM Director Agent is selected automatically for installation.
8. Optional: The Management Processor Assistant Agent enables communication
with service processors in IBM System x servers. To enable the Management
Processor Assistant Agent feature, select the check box.
9. Click Next. The Setup Status window opens, and Level 2: IBM Director Agent
installation begins. When the installation is completed, the InstallShield
Wizard Complete window opens.
10. Click Finish.
11. On the server running NetWare, change to the console screen.
12. From the console, type the following command and press Enter:
Search add sys:IBM\Director
13. To define the protocols to use for communication between IBM Director Server
and IBM Director Agent, type the following command and press Enter:
twgipccf

Note: If you disable the TCPIP (all adapters) setting and enable an individual
device driver on a system with multiple network adapters, IBM
Director Agent will receive only those data packets that are addressed to
the individual adapter.
load twgipc
IBM Director Agent will start automatically whenever the server running NetWare
starts.
Installing Level 2:IBM Director Agent on 32-bit Windows

32-bit Windows system by downloading the installation file or using the CD.
Important:
installed.
the system, it is installed during the IBM Director Agent installation. If 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.

containing the dir5.20_agent_windows.exe file and run the installation
dir5.20_agent_windows.exe -a admin

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.

To install Level 2 : IBM Director Agent on 32-bit Windows using the InstallShield
wizard, complete the following steps:
a. Download the dir5.20_agent_windows.zip file from theIBM 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
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.
a. Insert the IBM Director on x86, V5.20 CD into the drive.
window opens, go to step 3d. Otherwise, click Start → Run.
e:\setup.exe
d. Click Install IBM Director Agent. The InstallShield wizard starts, and the
Welcome to the InstallShield Wizard for IBM Director Agent window
Director Agent using the keyboard, perform the following
steps:
c. Browse to the director/agent/windows/i386/FILES
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
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 is displayed to the
left of each component.
6. A red X is displayed to the left of IBM Director Remote Control Agent,
which is optional. The IBM Director Remote Control Agent enables a system
administrator to perform remote desktop functions on the management server.
To install IBM Director Remote Control Agent, click the red X to the left of the

feature name. A menu opens. Click either This feature will be installed on
local hard drive or This feature, and all subfeatures, will be installed on
local hard drive.
7. Click Next.
8. Encrypt data transmissions between IBM Director Server and IBM Director
Agent is selected by default.
Note: If encryption is enabled, the following conditions apply:

v The managed system is automatically secured, and the Secure – IBM
Director Server must request access to manage this system check
box is unavailable.
v Only management servers with encryption enabled are able to
communicate with the managed system.
To accept this setting, go to step 10. If you do not want to encrypt
transmissions between IBM Director Server and IBM Director Agent, clear the
check box and go to step 9.
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.
10. Optional: In the Add Known Server Address field, enter a comma-separated
list of IBM Director Server addresses to which IBM Director Agent should
announce itself. The format for this field is <protocol>::<address>, for example,
TCPIP::10.3.1.4, TCPIP::192.168-1.10.
To select an alternative location for the storage of software-distribution
packages before they are applied to IBM Director Agent, click Change and
13. 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.
14. 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.
15. 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.

Note: To determine whether your server supports the Wake on LAN
feature, see your server documentation.
16. If you chose to install the IBM Director Remote Control Agent, the following
options are available:
Require User Authorization for System Access
Select this check box to request authorization from the local user
before accessing the managed system remotely.
Disable Screen Saver
Select this check box to disable the screen saver when the managed
system is controlled remotely.
Disable Background Wallpaper
Select this check box to disable desktop wallpaper when the managed
system is controlled remotely. You might want to disable the
wallpaper because complicated backgrounds can affect the
performance of remote control and increase network traffic.
17. Click OK. The status bar displays the progress of the installation. When the
18. Click Finish.
19. If you installed IBM Director Agent from the CD, remove the CD from the
drive.
20. If you are prompted to restart your system, click Yes.

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,
a. Download the dir5.20_agent_windows.zip file from theIBM Director Web
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.
(1 of 2) CD into the drive.
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.

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).
dir5.20_agent_windows.exe /s /a installationtype rsp="responsefile.rsp" option
where:
user input.
v responsefile.rsp is the path and name of the response file that you saved in
step 4 on page 102.
waitforme Ensures that dir5.20_agent_windows.exe process will not end
until the installation of IBM Director Agent is completed
messages
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
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
the system, it is installed during the IBM Director Agent installation. If the
installation of IBM Director Agent without specifying that Microsoft
Windows Installer was installed. Unless you install using the response file

and set the RebootIfRequired parameter to N, you are prompted to restart
whether or not the IBM Director Agent installation is completed successfully.

containing the dir5.10.3_agent_windows64.exe file and run the installation
dir5.10.3_agent_windows64.exe -a admin

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.
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
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.
6. Click I accept the terms in the license agreement and click Next. The Feature
and Installation Directory Selection window opens.
Level 2: IBM Director Agent is selected automatically for installation; a
hard-disk-drive icon is displayed to the left of the component.
7. A red X is displayed to the left of IBM Director Remote Control Agent,
which is optional. The IBM Director Remote Control Agent enables a system
administrator to perform remote desktop functions on the management server.
To install IBM Director Remote Control Agent, click the red X to the left of the
feature name. A menu opens. Click either This feature will be installed on
local hard drive or This feature, and all subfeatures, will be installed on
local hard drive.
8. Click Next. The Security Settings window opens.
9. The Secure – IBM Director Server must request access to manage this
system check box is selected by default. This setting ensures that IBM Director
Server cannot manage this system until it is granted access.
10. Optional: Add a comma-separated list of IBM Director servers that you want
IBM Director Agent to announce itself to in the Add Known Server Address
field. The format for this field is <protocol>::<address>, for example,
TCPIP::10.3.1.4, TCPIP::192.168-1.10.
12. To select an alternative location for the storage of software-distribution
packages before they are applied to IBM Director Agent, click Change and
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
19. Click Finish.
20. If you are prompted to restart your system, click Yes.

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.
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
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).
dirdir5.10.3_agent_windows64.exe /s /a installationtype rsp="responsefile.rsp"
option
where:
user input.
v responsefile.rsp is the path and name of the response file that you created in
step 5.
waitforme Ensures that dir5.10.3_agent_windows64.exe process will not
end until the installation of IBM Director Agent is completed
messages

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

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.
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)

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:
2. In the Tasks pane, expand the Software Distribution task.

3. Click the software package that you want to distribute. Then, drag it into the
Group Contents pane and drop it onto the icon that is displayed for the system
on which you want to install the software package. A window opens.
Note: To distribute software to several systems at once, you can drag the
software package into the Groups pane and drop it onto the icon for the
group. Alternatively, you can select multiple managed systems in the
Group Contents pane.
4. When prompted with Do you wish to create a scheduled job for this task
or execute immediately?, click Schedule or Execute Now. If you click Execute
Now, the software package is distributed immediately. If you click Schedule,
the New Scheduled Job window opens.
5. Schedule the job:
a. In the Scheduled Job field, type a unique name for the job. This name is
displayed in the Jobs pane of the Scheduler window.
b. In the Date field, type the day you want the software package to be
installed (in MM/DD/YYYY format).
c. In the Time field, type the time you want the software package to be
installed.
For more information about the Scheduler task, see the IBM Director Systems
Management Guide.
6. Click OK. The Save Job Confirmation window opens.
7. Click OK.

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.
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.
3. 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.
4. Click OK. The initial discovery is performed and the Event Action Plan
Wizard is displayed.
5. On the Name page, type a descriptive name for the event action plan you are
creating.
6. Click Next.
7. 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.
8. Click Next.
9. On the Event Filters page, select the check boxes adjacent to the types of
events you want to monitor.

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. Select the location where the program should be started.
b. Type the Host name of the selected system.
c. Type the working directory of the program that needs to start.
d. Type the Program name of the application that needs to start.
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.

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.
Set the ldap.auth.jndi

If this is true: property to:
IBM Director Server on i5/OS true
IBM Director Server on AIX, and not using Pluggable true
Authentication Module (PAM) authentication.
IBM Director Server on Linux, and not using Pluggable true
Authentication Module (PAM) authentication.
IBM Director Server on Windows, and using an LDAP true
server other than Active Directory.
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 Properties to be set

ldap.auth.userid.attribute=uid
uid The user ID specified when the ldap.auth.userid.lookupUserDN=true
LDAP user was created.
ldap.auth.userid.attribute=dn
dn The fully qualified distinguished
name of the user.
6. Specify the LDAP authentication method being used by the LDAP server. Set
the ldap.auth.mechanism property to one of the following values:
simple
anonymous
DIGEST-MD5
7. Set the ldap.enabled property to true. You might have to add the
ldap.enabled property to the dirldap.properties file.
8. Optional: Modify other properties in the dirldap.properties file as needed.
These properties are described in Appendix B, “Lightweight Directory Access
Protocol authentication properties for IBM Director Server,” on page 159.
9. Save and close the changed dirldap.properties file.
10. Stop and restart IBM Director Server. For IBM Director Server to use the new
values, you must stop and restart IBM Director Server.
Additional information about the dirldap.properties file, including example

configurations for various authentication scenarios, are included in “Lightweight
Directory Access Protocol authentication properties for IBM Director Server.”
Using IBM Director in a high-availability environment

If IBM Director will be used in a high-availability environment, you need to
prepare the environment for IBM Director, and you might need to configure IBM
Director properties for running in high-availability environments.

Note: A high-availability application is required for implementation of IBM
Director high-availability configuration.
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.

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
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.

This tradeoff is summarized in the following table.
Configuration Benefit Cost

High-availability not enabled Improved performance. Loss of data on failover.
(default configuration).
Incomplete tasks restart from
beginning.
High-availability enabled. Minimal loss of data on Decreased performance.
failover.
Incomplete tasks continue

from last saved checkpoint.
To configure IBM Director Server for a high-availability environment, complete the

following steps:
1. On the management server, open the TWGServer.prop file in a text editor.
Operating system 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.

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
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
Configuring discovery preferences

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

To discover BladeCenter chassis, you must configure IBM Director Server.
The management server and the BladeCenter chassis must be connected to the
network and on the same subnet. One of the following conditions must also be
true:
v The network contains a Dynamic Host Configuration Protocol (DHCP) server
that has assigned an IP address to the management module.
v The default IP address of the management module has been changed to a valid
IP address on the same subnet as the management server.
If these conditions are not met, you must discover the BladeCenter chassis
manually.
IBM Director Server uses Service Location Protocol (SLP) to communicate

out-of-band with the BladeCenter chassis. This communication occurs through the
external Ethernet port on the BladeCenter management module. When the
BladeCenter management module first is started, the management module
attempts to acquire an IP address for the external management port using DHCP. If
this attempt fails, the BladeCenter management module assigns an IP address
(192.168.70.125) to the external management port.
Note: If you do not use a DHCP server to assign a temporary IP address to the
BladeCenter chassis, introduce only one BladeCenter chassis onto the
network at a time. IBM Director must discover and configure the chassis
before another chassis is added to the LAN. Otherwise, an IP address
conflict will occur.
Complete the following steps to configure discovery preferences for BladeCenter

chassis:
1. In IBM Director Console, click Options → Discovery Preferences.

2. Click the BladeCenter Chassis tab.
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 1. In the Selected Parameters list, click the parameter after which
parameter 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 1. In the Selected Parameters list, click the parameter after which
parameters you would like to add a space.
2. In the Available Parameters list, click Insert a space.
3. Click Add.
Add custom text 1. In the Selected Parameters list, click the parameter after which
you would like to add your text.
2. In the Available Parameters list, click Insert additional text.
3. Click Add.
4. Type the text you want to add.
5. Click OK.
Delete a parameter 1. In the Selected Parameters list, click the parameter you want to
delete.
2. Click Remove.
Restore parameters to Select the Reset to default value check box. If prompted, click Yes.
the default values
The following parameters are available, as well as custom text and spaces:
v %CHASSIS_MACHINE_TYPE_MODEL%
v %CHASSIS_SERIAL_NUMBER%
v %CHASSIS_FRU%

v %MM_NAME%
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:
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.
4. Type values in the Start Address and End Address fields.
5. Click OK.

Add a list of IP 1. Click Import.
addresses for 2. Select the text file containing the IP addresses.
unicast discovery Note: The file must be a text file, with each line containing either a
from a text file single IP addresses or an IP address range specified by a start
address and an end address separated by a space. You can select a
file on the Local system (on which IBM Director Console is running)
or on the Server (on which IBM Director Server is running).
3. Click OK.
Change an 1. Select the entry to be changed in the Address Entries list.
existing address 2. Click Edit.
entry 3. Change the field values for the entry.
4. Click OK.
Delete an 1. Select the entry to be deleted in the Address Entries list.
existing address 2. Click Remove.
entry 3. If prompted, click Yes.
Option Description
(minutes).
Option Description
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.


systems

managed systems:
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 1. Ensure that no SLP directory agents are listed in the Predefined
IP broadcast 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 1. Ensure that no SLP directory agents are listed in the Predefined
multicast directory agent servers list box. If a directory agent is provided, IBM
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.
Option Description
6. Click OK.

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.


systems

managed systems:
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.
Option Description
(minutes).
Option Description
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.

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.

Add an address 1. Click Add.
and mask for 2. Click Broadcast.
broadcast 3. Click Next.
discovery 4. Type values in the IP Address and Subnet Mask fields.
5. Click OK.
and mask for 2. Click Relay.
broadcast relay 3. Click Next.
discovery 4. Type values in the IP Address and Subnet Mask fields.
5. Click OK.
Add a single IP 1. Click Add.
address for 2. Click Unicast Address.
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.
4. Type values in the Start Address and End Address fields.
5. Click OK.
4. Click OK.

12. IPX-enabled management servers only: At the top of the page, click System
Discovery (IPX) to display IPX-specific discovery preferences for Level-2
managed systems. Then, complete the following steps:
a. To specify that IBM Director Server issues an IPX broadcast to discover
managed systems on the local subnet, on the System Discovery (IPX) page,
select the Use IPX general broadcasts check box. By default, this feature is
enabled.
b. To configure IBM Director Server to use IPX broadcasts to discover
managed systems on remote subnets, complete one or more of the
following steps:

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.
4. Click OK.
13. Click OK.

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.

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:

2. Click the Physical Platforms tab.
Option Description
(minutes).
Option Description
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
to add.
3. Click Add.
3. Click Add.
3. Click Add.
5. Click OK.
delete.
2. Click Remove.
the default values
v %SERVER_MACHINE_TYPE_MODEL%
v %SERVER_SERIAL_NUMBER%
v %SERVER_FRU%
v %SP_FRU%

v %SP_SERIAL_NUMBER%
v %CHASSIS_SLOT%
v %CHASSIS_SLOT_RANGE%
v %CHASSIS_NAME%
v %SP_TEXT_ID%
v %SP_IP_ADDRESS%
v %SP_HOSTNAME%
v %SP_ASSET_TAG%
v %DIR_AGENT_NAME%
v %COMPUTER_NAME%
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.

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:
2. Click the SMI-S Storage Devices tab.
Option Description

(minutes).
Option Description
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.

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 Select the Reset to default value check box.
default values If prompted, click Yes.

steps.
Discovery
method Steps
click OK.
OK.

Option Description
9. Specify a template for naming SMI-S storage devices that IBM Director Server
discovers.
To perform this
to add.
3. Click Add.
3. Click Add.
3. Click Add.
5. Click OK.
delete.
2. Click Remove.
the default values
v %MANUFACTURER_ID%
v %HARDWARE_TYPE_MODEL%
v %HARDWARE_SERIAL_NUMBER%
v %IPADDRESSES%
v %ENDPOINT%
v %NAME%
%MANUFACTURER_ID% %HARDWARE_TYPE_MODEL%
%ENDPOINT%
10. Click OK.

11. Optional: To start discovery of SMI-S storage devices now, click Tasks →
Discover → SMI-S Storage Devices. Otherwise, IBM Director Server will
automatically discover SMI-S storage devices periodically as configured in the
Discovery Preferences window.

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:
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.mib-
2.ip.ipNetToMediaTable.ipNetToMediaEntry.ipNetToMediaNetAddress, locates
the address tables that are found on the specified devices and adds those
addresses to the list of addresses to search. You can use the SNMP browser on
the SNMP device that is listed in your preferences to view the table.
Addresses in the table are used for Discovery. An address will not be found in
the table if SNMP is not currently active on that device. The process is
repeated for every new SNMP device that is discovered from the new
addresses. The discovery operation continues until no more addresses are
found.
A newly installed IBM Director Server is not likely to find many addresses in
the address table. Some IBM Director Servers without any additions in SNMP
Discovery Preferences might find few or no SNMP devices while others might
find many SNMP devices. Adding to the address table can be accomplished
by doing Discovery. However, the implementation of the SNMP device is
completely separate from IBM Director and addresses that are in the same
subnet or subnets as the SNMP device might be the only ones that are added
to the address table. The manual add SNMP device panel has a checkbox for
Use as a discovery seed. Selecting this checkbox adds the address to SNMP
Discovery preferences to allow the new device to be a seed in all subsequent

discovery operations. If you are using a community name other than the
public community name, you can manually add the community name to
SNMP Discovery preferences.
SNMP Discovery preferences also has an option to Auto-add unknown agents
which contact server.

Add a new seed 1. Type an IP address and subnet mask value in the text boxes at the
address for top of the IP Addresses and Subnet Masks list.
SNMP discovery 2. Click Add.
Add a list of 1. Click Import.
seed addresses 2. Select the text file containing the IP addresses.
from a text file 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 1. Click the entry to be changed in the IP Addresses and Subnet
existing seed Masks list.
address 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 1. Click the entry to be deleted in the IP Addresses and Subnet Masks
existing seed list.
address 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.

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.

Add a profile 1. Select a profile name using the control at the top of the Profile
name Names list.
Note: Profile names which are displayed in this control are
configured in the Server Preferences window.
2. Click Add.
Delete a profile 1. Click the profile name to be deleted.
name 2. Click Remove.
3. If prompted, click Yes.
Option Description
(minutes).
Option Description
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.


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:
2. Click the HMC tab.
steps.
Discovery
method Steps
click OK.
OK.
Option Description

Option Description
(minutes).
Option Description
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.

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:
2. Click the z/VM Systems tab.
steps.

Discovery
method Steps
click OK.
OK.
Option Description
(minutes).
Option Description
value is 15.
7. Click OK.

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.

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.


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:

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. 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:
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:

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:

2. In the Group Contents pane, right-click the managed system or group to which
you want to distribute software and click Distribution Preferences.
3. In the Distribution Preferences window, select the method of software
distribution:
v If you want to copy packages directly from IBM Director Server to the
managed system or group, click Always stream to the Managed System(s).
v If you want to copy packages from a share on a file-distribution server to the
managed system or group, click Use File Distribution Server Shares.
Note: When you have selected Use File Distribution Server Shares and a
file-distribution-server share cannot be located during a software
distribution, the default action is to stream the package from IBM
Director Server. You can prevent streaming from IBM Director Server by
selecting the Do not stream if redirection fails check box in the Server
Preferences for Software Distribution window. However, if no
file-distribution-server shares are defined and this check box is selected,
the package is streamed.

4. To add a share, click Add.
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 VMware ESX Server, version 2.5.x Console
v VMware ESX Server, version 3.0 Console

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.

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.
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.

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.
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.
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 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 uninstall IBM Director, complete the following steps:

1. Shut down all applications.
2. Click Start → Settings → Control Panel. The Control Panel window opens.
3. Double-click Add/Remove Programs. The Add/Remove Programs window
opens.
4. Click the IBM Director software component that you want to remove; then,
click Remove.
5. Follow the instructions on the screen.
Uninstalling IBM Director using the dirunins command

You can uninstall IBM Director from Windows by using the dirunins command.
To uninstall an IBM Director component that is running on a Windows system,

from a command-line prompt, type the following command and press Enter:
dirunins directorcomponent option
The following table contains information about the possible values for option and
directorcomponent.

Table 34. dirunins parameters
Variable Parameter What it does
option debug Logs all messages that are sent by the Windows
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
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
directorcomponent 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.

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

Navigate in or out of the option pane. Alt+F6
Hide a window. Esc
Table 37. Keyboard shortcuts for scroll panes

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

Table 37. Keyboard shortcuts for scroll panes (continued)
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

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 F8
split panes).
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)

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

Display a window menu. Alt+Space bar

Table 41. Additional keyboard shortcuts for frames in External Application Launch wizard
To move focus to the description area when focus is currently on Esc
any of the first five event filters
To move focus to the description area when focus is currently on Space bar, then
any other event filter 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

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
Table 43. Keyboard shortcuts for menu bar

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

Display a menu. Enter or F10
Appendix A. Accessibility features for IBM Director 149

Table 44. Keyboard shortcuts for menus (continued)
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

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

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

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

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

Navigate forward out of the toolbar. Tab

Table 49. Keyboard shortcuts for toolbar (continued)
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 Shift+10
on the main IBM Director Console window toolbar).
Table 50. Keyboard shortcuts for tool tips

Display a tool tip. Ctrl+F1
Hide a tool tip. Esc or Ctrl+F1
Table 51. Keyboard shortcuts for buttons

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

Navigate within a group. Arrow keys
Select or clear a check box. Space bar
Table 53. Keyboard shortcuts for radio buttons

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

Navigate forward out of the combination box. Tab
Navigate backward out of the combination box. Shift+Tab

Table 54. Keyboard shortcuts for combination boxes (continued)
Navigate into a combination box within a table cell (focus must be F2
in the table cell).
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 Up arrow or Down
a table. 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

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

Navigate forward out of the slider. Tab
Navigate backward out of the slider. Shift+Tab
Increase the value Up arrow or right
arrow.

Table 56. Keyboard shortcuts for sliders (continued)
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

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
Shift+PgDn
Extend the selection left or right one block. Ctrl+Shift+PgUp or
Ctrl+Shift+PgDn

Table 57. Keyboard shortcuts for tables (continued)
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

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

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

Table 59. Keyboard shortcuts for trees (continued)
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

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

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

Table 61. Keyboard shortcuts for text panes (continued)
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 Ctrl+T or Ctrl+Shift+T
which can receive the focus.
Navigate out of a focusable element that accepts a tab. Ctrl+Tab or
Ctrl+Shift+Tab
Activate a hyperlink. Ctrl+Space bar
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.
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 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
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.

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

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
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.

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

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.

Glossary
contained an ASM processor. When an
Glossary ASM PCI adapter is used with an ASM
This glossary includes terms and definitions for processor, the ASM PCI adapter acts as an
IBM Director. Ethernet gateway, while the ASM
processor retains control of the server.
To view glossaries for other IBM products, go to When used as a gateway service
www.ibm.com/ibm/terminology . processor, the ASM PCI adapter can
communicate with other ASM PCI
A adapters and ASM processors only.
accelerator Advanced System Management processor (ASM
In a user interface, a key or combination processor)
of keys that invokes an A service processor built into the
application-defined function. mid-range Netfinity and early xSeries
servers. IBM Director can connect
Advanced Encryption Standard (AES)
out-of-band to an ASM processor located
A data encryption technique that
on an ASM interconnect; an ASM PCI
improved upon and officially replaced the
adapter, a Remote Supervisor Adapter, or
Data Encryption Standard (DES). AES is a Remote Supervisor II must serve as the
sometimes referred to as Rijndael, which gateway service processor.
is the algorithm on which the standard is
based. AES See Advanced Encryption Standard.
Advanced System Management interconnect alert A message or other indication that signals
(ASM interconnect) an event or an impending event.
A feature of IBM service processors that alert forwarding
enables users to connect up to 24 servers
A function that ensures that alerts are
to one service processor, thus eliminating sent, even if a managed system
the need for multiple modems, experiences a catastrophic failure, such as
telephones, and LAN ports. It provides an operating-system failure.
such out-of-band management functions
as system power control, alert-forwarding profile
service-processor event-log management, A profile that specifies where remote
firmware updates, alert notification, and alerts for the service processor should be
user profile configuration. sent.
Advanced System Management interconnect alert standard format (ASF)
network (ASM interconnect network) A specification created by the Distributed
A network of IBM servers created by Management Task Force (DMTF) that
using the ASM interconnect feature. The defines remote-control and alerting
servers are connected through RS-485 interfaces that can best serve a client
ports. When servers containing integrated system in an environment that does not
system management processors (ISMPs) have an operating system.
and ASM processors are connected to an anonymous command execution
ASM interconnect network, IBM Director Execution of commands on a target
can manage them out-of-band.
system as either system account (for
Advanced System Management PCI adapter managed systems running Windows) or
(ASM PCI adapter) root (for managed systems running
An IBM service processor that is built into Linux).
the Netfinity 7000 M10 and 8500R servers. ASF See alert standard format.
It also was available as an option that
could be installed in a server that

ASM interconnect bottleneck
See Advanced System Management A place in the system where contention
interconnect. for a resource is affecting performance.
ASM interconnect gateway
C
See gateway service processor.
chassis
ASM interconnect network
The metal frame in which various
See Advanced System Management
electronic components are mounted.
interconnect network.
chassis detect-and-deploy profile
ASM PCI adapter
A profile that IBM Director automatically
See Advanced System Management PCI
applies to all new BladeCenter chassis
adapter.
when they are discovered. The profile
ASM processor settings include management module
See Advanced System Management name, network protocols, and static IP
processor. addresses. If Remote Deployment
Manager (RDM) is installed on the
association
management server, the chassis
A visual representation of the members in
detect-and-deploy profile also can include
a group that shows relationships or
deployment policies.
provides additional information about the
members of a group. CIM See Common Information Model.
Auto-Logical Drive Transfer cloning
See auto volume transfer/auto disk In z/VM, a copying technique that
transfer. preserves the characteristics of the
original but personalizes instance-specific
auto volume transfer/auto disk transfer
data. The result of a cloning operation is
(AVT/ADT)
new instance of an entity (for example, of
A function that provides automatic
a virtual disk, a virtual computer system,
failover in case of controller failure on a
or an operating system) rather than a
storage subsystem.
backup of the original.
AVT/ADT
cluster
See auto volume transfer/auto disk
A collection of complete systems that
transfer.
work together to provide a single, unified
computing capability.
B
CMS See Conversational Monitor System.
Basic Input/Output System (BIOS)
The code that controls basic hardware Common Information Model (CIM)
operations, such as interactions with An implementation-neutral,
diskette drives, hard disk drives, and the object-oriented schema for describing
keyboard. network management information. The
Distributed Management Task Force
BIOS See Basic Input/Output System.
(DMTF) develops and maintains CIM
BladeCenter chassis specifications.
A BladeCenter unit that acts as an
component association
enclosure. This 7-U modular chassis can
In the IBM Director Rack Manager task, a
contain up to 14 blade servers. It enables
function that can make a managed system
the individual blade servers to share
or device rack-mountable when the
resources, such as the management,
inventory collection feature of IBM
switch, power, and blower modules.
Director does not recognize the managed
blade server system or device. The function associates
A high-throughput, two-way, Intel the system or device with a predefined
Xeon-based server on a card that supports component.
symmetric multiprocessors (SMPs).

Conversational Monitor System (CMS) disk pool
A virtual-machine operating system that In z/VM Center, a logical grouping of
provides general interactive time sharing, contiguous disk spaces. A disk pool can
problem solving, and program include disk spaces from multiple
development capabilities. physical disks. A disk pool corresponds to
a z/VM Directory Maintenance Facility
D allocation group.
database server DMI See Desktop Management Interface.
The server on which the database
DSA See digital signature algorithm.
application and database are installed.
Data Encryption Standard (DES) E
A cryptographic algorithm designed to
enclosure
encrypt and decrypt data using a private
A unit that houses the components of a
key.
storage subsystem, such as a control unit,
deployment policy disk drives, and power source.
A policy that associates a specific bay in a
event An occurrence of significance to a task or
BladeCenter chassis with a Remote
system. Events can include completion or
Deployment Manager (RDM)
failure of an operation, a user action, or
noninteractive task. When a blade server
the change in state of a process.
is added to or replaced in the bay, IBM
Director automatically runs the RDM task. event action
The action that IBM Director takes in
DES See Data Encryption Standard.
response to a specific event or events.
Desktop Management Interface (DMI)
event-action plan
A protocol-independent set of application
A user-defined plan that determines how
programming interfaces (APIs) that were
IBM Director will manage certain events.
defined by the Distributed Management
An event action plan comprises one or
Task Force (DMTF). These interfaces give
more event filters and one or more
management application programs
customized event actions.
standardized access to information about
hardware and software in a system. event-data substitution variable
A variable that can be used to customize
Diffie-Hellman key exchange
event-specific text messages for certain
A public, key-exchange algorithm that is
event actions.
used for securely establishing a shared
secret over an insecure channel. event filter
A filter that specifies the event criteria for
digital signature algorithm (DSA)
an event action plan. Events must meet
A security protocol that uses a pair of
the criteria specified in the event filter in
keys (one public and one private) and a
order to be processed by the event action
one-way encryption algorithm to provide
plan to which the filter is assigned.
a robust way of authenticating users and
systems. If a public key can successfully
decrypt a digital signature, a user can be
F
sure that the signature was encrypted fabric A complex network using hubs, switches,
using the private key. and gateways. Fibre channel uses a fabric
to connect devices.
directory manager
A facility for maintaining the user field-replaceable unit (FRU)
directory of one or more z/VM systems. An assembly that is replaced in its
entirety when any one of its components
discovery
fails.
The process of finding resources within
an enterprise, including finding the new file-distribution server
location of monitored resources that were In the Software Distribution task, an
moved. intermediate server that is used to
Glossary 169
distribute a software package when the I
redirected-distribution method is used.
IBM Director Agent
forecast A component of IBM Director software.
A function that can provide a prediction When IBM Director Agent is installed on
of future performance of a managed a system, the system can be managed by
system using past data collected on that IBM Director. IBM Director Agent
managed system. transfers data to the management server
using several network protocols,
FRU See field-replaceable unit.
including TCP/IP, NetBIOS, and IPX.
G IBM Director Console
A component of IBM Director software.
gateway service processor
When installed on a system, it provides a
A service processor that relays alerts from
graphical user interface (GUI) for
service processors on an Advanced
accessing IBM Director Server. IBM
System Management (ASM) interconnect
Director Console transfers data to and
network to IBM Director Server.
from the management server using
group A logical set of managed objects. Groups TCP/IP.
can be dynamic, static, or task-based.
IBM Director Core Services
Guest LAN A facility with which IBM Director
A virtual local area network (LAN) communicates with and administers a
segment that is emulated by the z/VM level-2 managed system. IBM Director
Control Program (CP). A Guest LAN can Core Services includes the service location
be shared by guest virtual machines on protocol (SLP) instrumentation, the IBM
the same z/VM system. Director Agent SLP service type, and
Common Information Model (CIM).
guest virtual machine
In z/VM, the functional equivalent of a IBM Director database
System z9 or zSeries system, including The database that contains the data stored
the virtual processors, virtual storage, by IBM Director Server.
virtual devices, and virtual channel
IBM Director environment
subsystem allocated to a single user. Each
The complex, heterogeneous environment
guest virtual machine can be controlled
managed by IBM Director. It includes
by an operating system, such as CMS,
systems, BladeCenter chassis, software,
z/VSE, z/OS, or Linux.
and SNMP devices.
H IBM Director extension
A tool that extends the functionality of
host object
IBM Director. Some of the IBM Director
A logical object that groups one or more
extensions are Capacity Manager,
worldwide port names (WWPNs) of the
ServeRAID Manager, Remote Deployment
host bus adapters (HBAs) that the cluster
Manager, and Software Distribution.
has detected on the storage area network
(SAN). IBM Director Server
The main component of IBM Director
HT See Hyper-Threading.
software. When installed on the
Hyper-Threading (HT) management server, it provides basic
A technology with which a single functions such as discovery of the
processor can function as two virtual managed systems, persistent storage of
processors and execute two threads configuration and management data, an
simultaneously. inventory database, event listening,
security and authentication, management
hypervisor
console support, and administrative tasks.
A program or a portion of Licensed
Internal Code (LIC) that allows multiple IBM Director Server service
instances of operating systems to run A service that runs automatically on the
simultaneously on the same hardware.

management server, and provides the Director but does not have any IBM
server engine and application logic for Director software installed on it.
IBM Director.
Level-1 managed system
IBM Director service account An IBM or non-IBM server, desktop
The Windows operating-system account computer, workstation, and mobile
associated with the IBM Director Server computer that has IBM Director Core
service. Services installed.
in-band communication Level-2 managed system
An IBM or non-IBM server, desktop
initial program load (IPL)
computer, workstation, or mobile
The process that loads the system
computer that has IBM Director Agent
programs from the system auxiliary
installed. The function of a Level-2
storage, checks the system hardware, and
managed system varies depending on the
prepares the system for user operations.
operating system and hardware.
instance
light path diagnostics
An individual realization of the operating
A technology that provides a lighted path
system with a particular version,
to failed or failing components to
configuration, physical location, and
expedite hardware repairs.
identifier.
logical unit number (LUN)
In object-oriented programming, an object
In the Small Computer System Interface
of a particular class.
(SCSI) standard, a unique identifier used
integrated system management processor to differentiate devices, each of which is a
(ISMP) logical unit (LU).
A service processor built into some
LUN See logical unit number.
xSeries servers. ISMP is the successor to
the Advanced System Management (ASM)
processor.
M
MAC address
interprocess communication (IPC)
See Media Access Control address.
A mechanism of an operating system that
allows processes to communicate with managed group
each other within the same computer or A group of systems or objects managed
over a network. by IBM Director.
inventory-software dictionary managed object
A file that tracks the software installed on A resource that is subject to
managed systems in a network. management--such as a connection, a
scalable system, or a line--as viewed from
IPC See interprocess communication.
a systems management perspective.
IPL See initial program load.
managed object ID
ISMP See integrated system management A unique identifier for each managed
processor. object.
managed system
J A system that is being controlled by a
job A separately executable unit of work. given system management application.
management console
K
A system (server, desktop computer,
workstation, or mobile computer) on
L
which IBM Director Console is installed.
Level-0 managed system
management module
An IBM or non-IBM server, desktop
The BladeCenter component that handles
computer, workstation, or mobile
system-management functions. It
computer, that can be managed by IBM
configures the chassis and switch
Glossary 171
modules, communicates with the blade connection, for example, service processor
servers and all I/O modules, multiplexes alerts sent through a modem or over a
the keyboard/video/mouse (KVM), and LAN.
monitors critical information about the
chassis and blade servers. P
management server PCI See Peripheral Component Interconnect.
The server on which IBM Director Server See also Peripheral Component
is installed. Interconnect-X.
master system PCI-X See Peripheral Component Interconnect-X.
In z/VM Center, an operating system See also Peripheral Component
instance that has been set up to serve Interconnect.
Virtual Server Deployment as a model for
Peripheral Component Interconnect (PCI)
creating operating system templates.
A local bus that provides a high-speed
Media Access Control address (MAC address) data path between the processor and
In a local area network, the protocol that attached devices. See also Peripheral
determines which device has access to the Component Interconnect-X.
transmission medium at a given time.
Peripheral Component Interconnect-X (PCI-X)
minidisk An enhancement to the Peripheral
A direct access storage device (DASD) or Component Interconnect (PCI)
a logical subdivision of a DASD that has architecture. PCI-X enhances the
its own virtual device number. Peripheral Component Interconnect (PCI)
standard by doubling the throughput
N capability and providing additional
adapter-performance options while
node port (N_port)
maintaining backward compatibility with
A port that connects a node to a fabric or
PCI adapters. See also Peripheral
to another node. An N_port connects to a
Component Interconnect.
fabric port (F_port) or to the N_port of
another node. An N_port handles persistent
creation, detection, and flow of message Pertaining to data that is maintained
units to and from the connected systems. across session boundaries, usually in
N_ports are end points in point-to-point nonvolatile storage such as a database
links. system or a directory.
nonvolatile random access memory (NVRAM) PFA See Predictive Failure Analysis.
Random access memory (storage) that
physical platform
retains its contents after the electrical
An IBM Director managed object that
power to the machine is shut off.
represents a single physical chassis or
N_port server that has been discovered through
See node port. the use of the Service Location Protocol
(SLP).
NVRAM
See nonvolatile random access memory. plug-in
A software module that adds function to
O an existing program or application.
operating system template POST See power-on self-test.
A set of installation and configuration
power-on self-test (POST)
data that z/VM Center uses as a source
A series of internal diagnostic tests
for creating operating system instances.
activated each time the system power is
Operating system templates are created
turned on.
from master systems.
Predictive Failure Analysis (PFA)
out-of-band communication
A scheduled evaluation of system data
Communication that occurs through a
modem or other asynchronous

that detects and signals parametric resource-monitor threshold
degradation which might lead to The point at which a resource monitor
functional failures. generates an event.
private key RXE Expansion Port
In secure communication, an algorithmic The dedicated high-speed port used to
pattern used to encrypt messages that connect a remote I/O expansion unit,
only the corresponding public key can such as the RXE-100 Remote Expansion
decrypt. The private key is also used to Enclosure, to a server.
decrypt messages that were encrypted by
the corresponding public key. The private S
key is kept on the user’s system and is
scalable node
protected by a password. See also public
A physical platform that has at least one
key.
SMP Expansion Module. Additional
programming interface for customers attributes are assigned to a physical
The supported method through which platform when it is a scalable node. These
customer programs request software additional attributes record the number of
services. The programming interface SMP Expansion Modules, SMP Expansion
consists of a set of callable services Ports, and RXE Expansion ports on the
provided with a product. physical chassis.
public key scalable object
In secure communication, an algorithmic An IBM Director managed object that is
pattern used to decrypt messages that used with Scalable Systems Manager.
were encrypted by the corresponding Scalable objects include scalable nodes,
private key. A public key is also used to scalable systems, scalable partitions, and
encrypt messages that can be decrypted remote I/O enclosures that are attached to
only by the corresponding private key. scalable nodes.
Users broadcast their public keys to
scalable partition
everyone with whom they must exchange
encrypted messages. See also private key.
defines the scalable nodes that can run a
single image of the operating system. A
Q
scalable partition has a single, continuous
memory space and access to all associated
R
adapters. A scalable partition is the logical
redirected distribution equivalent of a physical platform. Scalable
A method of software distribution that partitions are associated with scalable
uses a file-distribution server. systems and comprise only the scalable
nodes from their associated scalable
remote I/O enclosure
systems.
represents an expansion enclosure of scalable system
Peripheral Component Interconnect-X An IBM Director managed object that
(PCI-X) slots, for example, an RXE-100 consists of scalable nodes and the scalable
Remote Expansion Enclosure. The partitions that are composed of the
enclosure consists of one or two scalable nodes in the scalable system.
expansion kits. When a scalable system contains two or
more scalable nodes, the servers that they
Remote Supervisor Adapter
represent must be interconnected through
An IBM service processor. It is built into
their SMP Expansion Modules to make a
some xSeries servers and available as an
multinode configuration, for example, a
optional adapter for use with others.
16-way xSeries 455 server made from four
When used as a gateway service
scalable nodes.
processor, the Remote Supervisor Adapter
can communicate with all service Secure Sockets Layer (SSL)
processors on the Advanced System A security protocol that provides
Management (ASM) interconnect. communication privacy. With SSL,
Glossary 173
client/server applications can system also, hardware alerts can be
communicate in a way that is designed to forwarded as SNMP traps.
prevent eavesdropping, tampering, and
SNMP device
message forgery.
An embedded device that uses SNMP to
server complex monitor network-attached devices,
In z/VM Center, a configuration profile printers, or computers for conditions that
for Linux guest systems that includes require system-management attention.
both Linux and z/VM aspects. A server
SQL See Structured Query Language.
complex can define network settings,
Linux configuration scripts, disk access, SSL See Secure Sockets Layer.
and VM Resource Manager (VMRM)
static partition
performance goals.
A view-only scalable partition.
Service Location Protocol (SLP)
sticky key
An Internet protocol that identifies and
An input method that enables the user to
uses network hosts without having to
press and release a series of keys
designate a specific network host name.
sequentially (for example, Ctrl+Alt+Del),
service machine yet have the keys behave as if they were
In z/VM, a guest virtual machine that pressed and released at the same time.
provides a system service such as This method can be used for those who
accounting, error recording, or require special-needs settings to make the
monitoring. A system service can be part keyboard easier to use.
of z/VM or a licensed program.
storage subsystem
service processor A storage control and its attached storage
A generic term for Remote Supervisor devices.
Adapters, Advanced System Management
Structured Query Language (SQL)
processors, Advanced System
A standardized language for defining and
Management PCI adapters, and integrated
manipulating data in a relational
system management processors (ISMPs).
database.
These hardware-based management
processors used in IBM Netfinity and switch module
xSeries servers work with IBM Director to The BladeCenter component that provides
provide hardware status and alert network connectivity for the BladeCenter
notification. chassis and blade servers. It also provides
interconnectivity between the
SLP See Service Location Protocol.
management module and blade servers.
SMBIOS
System Health Monitoring
See system management BIOS.
An IBM Director Agent feature that
SMP Expansion Module provides active monitoring of critical
An IBM xSeries hardware option. It is a system functions, including system
single module that contains temperatures, voltages, and fan speeds. It
microprocessors, disk cache, random also handles in-band alert notification for
access memory, and three SMP Expansion managed systems running Windows and
Port connections. Two SMP Expansion some managed systems running Linux.
Modules can fit in a chassis.
system management BIOS (SMBIOS)
SNMP Access and Trap Forwarding A specification that extends BIOS to
An IBM Director Agent feature that support the retrieval of management data.
enables SNMP to access managed-system
system variable
data. When installed on a managed
A user-defined keyword and value pair
system, this feature enables SNMP-based
that can be used to test and track the
managers to poll the managed system and
status of network resources. System
receive its alerts. If System Health
variables can be referred to wherever
Monitoring is installed on the managed
event-data substitution is allowed.

T Agent from within the higher-level
systems-management console, as well as
target system
collect IBM Director inventory data and
A managed system on which an IBM
view IBM Director alerts.
Director task is performed.
user class
time to live
A z/VM privilege category assigned to a
A technique used by best-effort delivery
user of a guest virtual machine in the
protocols to inhibit endlessly looping
user’s directory entry; each class specified
packets. The packet is discarded if the
allows access to a logical subset of all the
TTL counter reaches 0.
z/VM Control Program (CP) commands.
triple Data Encryption Standard (triple DES)
UUID See Universal Unique Identifier.
A block cipher algorithm that can be used
to encrypt data transmitted between
V
managed systems and the management
server. Triple DES is a security virtual device number
enhancement of DES that employs three In z/VM, a device number used by a
successive DES block operations. guest virtual machine. Real devices can be
referred to by different virtual device
triple DES
numbers by different guest virtual
See triple Data Encryption Standard.
machines.
truststore
virtual server template
In security, a storage object, either a file or
A set of definitions that provides
a hardware cryptographic card, where
configuration defaults for z/VM virtual
public keys are stored in the form of
servers. z/VM Center uses virtual server
trusted certificates, for authentication
templates to create z/VM virtual servers.
purposes in Web transactions. In some
applications, these trusted certificates are vital product data (VPD)
moved into the application keystore to Information that uniquely defines system,
reside with the private keys. hardware, software, and microcode
elements of a processing system.
U VPD See vital product data.
Universally Unique Identifier
The 128-bit numerical identifier that is W
used to ensure that two components do
Wake on LAN
not have the same identifier.
A technology that enables a user to
Universal Unique Identifier (UUID) remotely turn on systems for off-hours
See Universally Unique Identifier. maintenance. A result of the Intel-IBM
Advanced Manageability Alliance and
upward integration
part of the Wired for Management
The methods, processes and procedures
Baseline Specification, users of this
that enable lower-level
technology can remotely turn on a server
systems-management software, such as
and control it across the network, thus
IBM Director Agent, to work with
saving time on automated software
higher-level systems-management
installations, upgrades, disk backups, and
software, such as Tivoli Enterprise or
virus scans.
Microsoft SMS.
walk An SNMP operation that is used to
upward integration module
discover all object instances of
Software that enables higher-level
management information implemented in
systems-management software, such as
the SNMP agent that can be accessed by
Tivoli Enterprise or Microsoft Systems
the SNMP manager.
Manager Server (SMS), to interpret and
display data provided by IBM Director Windows Management Instrumentation (WMI)
Agent. This module also can provide An application programming interface
enhancements that start IBM Director (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.
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

Index
A chassis managed objects
displayed in IBM Director Console
DS300 28
DS400 28
accessibility 147 (screenshot) 118 DS4000 28
features 147 CIM Browser DS6000 28
keyboard 147 operating systems, supported 18
shortcut keys 147 compatibility documents v
Advanced System Management 42
AIX
Compatibility Documents 13
concepts 1
E
installing encryption
Configuration Manager 26
IBM Director Agent 89 enabling on managed system
Configure SNMP Agent
IBM Director Console 67 AIX 89
operating systems, supported 18
AIX installation i5/OS 91
customer support v
Express Linux 92, 95, 97
IBM Director Server 55 Windows 100
alerts enabling on management server
definition 32 D Windows 57
Apache Derby 28 dacimlist startup script 140 environment
ASF 22 dasnmp startup script 140 ports used 11
generating events 32 database environment (illustration) 1
ASM 42 function of 5 event
Asset ID databases availability 36
operating systems, supported 18 Apache Derby 28 definition 32
for management servers 28 how they work 32
IBM Cloudscape 28 management 35
B IBM DB2 28
Microsoft Data Engine 28
overview 32
publishing 36
baseboard management controller 24 Microsoft SQL Server 28 sources that generate 32
Baseboard Management Controller 42 MS Jet 28 types
blade servers MSDE 28 alert 32
total BladeCenter units 26 Oracle Server 28 availability 36
BladeCenter PostgreSQL 28 resolution 32
chassis supported 28 event action plans 35
assigning IP addresses deployment infrastructure (BladeCenter) design strategies 34
manually 118 DHCP server, using 118 example 36
DHCP server, using 118 IP address conflicts 118 grouping systems 35
discovering (automatically) 118 design strategies, event action plan 34 how events work 32
IP address conflicts 118 DHCP server 118 naming conventions 35
deployment infrastructure diragent.rsp 89 overview 35
DHCP server, using 118 diragent.rsp file planning and designing 34
IP address conflicts 118 upgrading IBM Director Agent using structuring 36
documentation v Software Distribution 85, 108 successful implementation 35
network devices 26 dircon.rsp file wizard 35
products, supported tasks 26 customizing 74 event filters
BladeCenter Configuration Manager location 74 structuring 36
operating systems, supported 20 dirinstall script Event Log
BladeCenter HS20, machine type IBM Director Agent 78, 94 operating systems, supported 18
8843 44 IBM Director Console 70 examples
BladeCenter(TM) HS20, machine type IBM Director Server 55 event action plan 36
8832 44 diruns utility 145 Express installation
BMC 24, 42 disability 147 AIX
books v discovery IBM Director Server 55
Brocade switches 28 BladeCenter chassis 118 IBM Director Server 57
documentation v Linux 61
domain controller 31 Linux for System z 63
C downloading v Linux on POWER 59
Capacity Manager compatibility documents v extensions
management server, installing on 57 hardware compatibility publishing events 36
chassis (BladeCenter) information v External Application Launch
DHCP server, using 118 IBM Director code v management server support 20
discovering (automatically) 118 IBM Director publications v operating systems, supported 18, 20
IP address conflicts 118 Net-SNMP, version 5.2.1 140 External Application Launch wizard
manually assigning IP addresses 118 systems-management software v operating systems, supported 18

F IBM Director Agent (continued)
installing on
IBM Director Server (continued)
installing
features, accessibility 147 AIX 89 Linux for System x 41
File Transfer license 4 System p 40
operating systems, supported 18 Linux, installing on license 5
file-distribution server dirinstall script 78, 92, 94, 95, 97 network protocols 10
configuring 138 Net-SMNP, enabling 78, 92, 94, operating systems, supported 14
setting up 137 95, 97 preparing, for installation 40, 41
firewall access Wake on LAN, enabling 92, 95, uninstalling
configuring 11 97 Windows 145
NetWare, installing on where to install 31
features, selecting 98 Windows, installing on
G network driver, configuring 98 database configuration 57
glossary 167 network protocols 10 encryption settings 57
grouping operating systems, supported 14 features, selecting 57
managed systems 35 uninstalling network driver, configuring 57
Windows 145 service account 57
Windows, installing on Software Distribution settings 57
H encryption, enabling 100
features, selecting 100, 104
Wake on LAN, enabling 57
IBM eServer Information Center v
hardware InstallShield wizard, using 100 IBM systems-management software
requirements 7 network driver, configuring 100, downloading v
hardware compatibility v 104 overview v
hardware requirements 7, 8, 9 securing managed system 100 IBM Web sites
Hardware Status security state, setting 100 eServer Information Center v
management server support 20 software-distribution settings 100 Redbooks v
operating systems, supported 18, 20 Wake on LAN, enabling 100, 104 ServerProven v
help, IBM Director resources v IBM Director Console 73 Support v
authorizing users 112 Systems Management Software v
features, selecting 73 xSeries Systems Management v
I function 5 illustrations
i5/os hardware requirements 7, 8 IBM Director environment 1
installing, IBM Director Console 67 installing 67 IBM Director software components 2
i5/OS 91 installing on installing
installing AIX 67 IBM Director Agent
IBM Director Server 39 Linux 69 using, Software Distribution 107
i5/OS installation Linux for POWER 71 IBM Director Console
encryption, enabling 91 installing on Linux 70 AIX 67
IBM Director Agent, installing 91 installing on Windows Linux for POWER 71
starting 91 dircon.rsp file 74 Linux for System x 69
IBM Cloudscape 28 InstallShield wizard, using 73 overview 67
IBM DB2 28 unattended mode, using 74 IBM Director Core Service
IBM Director license 5 Linux for POWER 79
components of 1 network protocols 10 Windows 81
concepts 1 operating systems, supported 14 IBM Director Server
getting started 1 overview 1 Linux 61
IBM Director Console 1 uninstalling Linux for System z 63
overview 1 Windows 145 Linux on POWER 59
scenarios 1 IBM Director Console installation 73 InstallShield wizard
IBM Director Agent IBM Director Core Service IBM Director Agent 100
AIX 89 installing on IBM Director Console 73
AIX, installing on Linux for POWER 79 IBM Director Server 57
encryption, enabling 89 Windows 81 Integrated System Management
BladeCenter IBM Director Core Services Processor 42
chassis 26 function 3 Intel Itanium
server 26 installing 49 IBM Director Agent
encryption, enabling license 3 installing 97
AIX 89 IBM Director Hardware and Software Intelligent Platform Management
i5/OS 91 Compatibility document v Interface 42
Linux 78, 92, 95, 97 IBM Director Server interim fixes v
Windows 100 AIX, installing on 55 Inventory
function 4 encryption, enabling operating systems, supported 18
generating events 32 Windows 57 IP address conflicts, troubleshooting 118
hardware requirements 7, 8, 9 function 5 IPMI 42
IBM Director tasks 26 hardware requirements 7, 8, 9 IPMI baseboard management controller
installing i5/OS generating events 32
using Software Distribution 107 installing 39 ISMP 42

K management server
choosing 31
Q
keyboard 147 definition 1 QLogic BladeCenter switches 28
hardware requirements 7, 8, 9
Microsoft Data Engine 28
L Microsoft SQL Server 28 R
legal notices 163 modifying an IBM Director installation Rack Manager
Level 1 managed system 3 Linux installation management console, installing
Level-1 managed system SNMP Access and Trap on 73
preparing, for installation 49 Forwarding, enabling 140 management server, installing on 57
Level-2 managed system 4 MS Jet 28 operating systems, supported 18
license MSDE 28 Red Hat Enterprise Linux
IBM Director Agent 4 AS, ES, and WS, version 3.0 49
IBM Director Console 5 Redbooks v
IBM Director Core Services 3 N related information v
IBM Director Server 5 N3700 28 Remote Control
Linux for POWER N5200 28 operating systems, supported 18
installing Net-SNMP, version 5.2.1 140 Remote Control Agent
IBM Director Console 71 NetWare installation managed system, installing on 100
IBM Director Core Service 79 IBM Director Agent, installing 98 management server, installing on 57
Linux for System x MPA Agent, when to install 98 Remote Session
installing Network Configuration operating systems, supported 18
IBM Director Console 69 operating systems, supported 18 Remote Supervisor Adapter 24, 42
Linux installation network protocols 10 documentation v
encryption, enabling 92, 95, 97 New Scheduled Job window 86, 109 request access
IBM Director Agent 78, 92, 94, 95 notifications authorizing, on a managed
IBM Director Console 70 definition 32 system 113
Intel Itanium requirements 7
IBM Director Agent 97 hardware 7
modifying resolution
SNMP Access and Trap O definition 32
Forwarding, enabling 140 operating system Resource Monitors
starting 78, 92, 94, 95, 97 compatibility v events 35
System p support for tasks 17 operating systems, supported 18
IBM Director Server 59 supported 13 response file
System x Oracle Server 28 dircon.rsp 67, 69, 71, 79, 81
IBM Director Server 61 modifying 67, 69, 71, 79, 81
System z
IBM Director Server 63 P
PET, generating events 32 S
planning and designing event action scenarios 1
M plans 34 Server Configuration Manager
managed system ports 11 operating systems, supported 20
authorizing PostgreSQL 28 Server Storage Provisioning Tool
request access 113 Power Management operating systems, supported 25
request access management server support 22 ServeRAID Manager
authorizing 113 operating system support 22 managed system, installing on 98,
managed systems operating systems 22 104
definition 1 service processor 24 Service Location Protocol 118
distribution preferences, Wake on LAN 24 service packs v
configuring 139 preparing service processor 42
hardware requirements 7, 8, 9 Level-1 managed system 49 Power Management 24
preparing Linux for System x service processors 22
Windows XP 53 IBM Director Server, installation documentation v
securing of 41 generating events 32
IBM Director Agent installation, System p shortcut keys 147
during 100 IBM Director Server, installation silent parameter 74, 82, 102, 106
management console 5 of 40 SMBIOS 7
definition 2 Process Management SNMP
hardware requirements 7, 8 operating systems, supported 18 generating events 32
management processor process monitors SNMP Access and Trap Forwarding
generating events 32 event 35 enabling on Linux 140
Management Processor Assistant Agent publications v SNMP devices
managed system, installing on 98, definition 1
100 operating systems, supported 18
NetWare, installing on 98 snmpconf utility 140
snmpd.conf file 140
Index 179
software components (illustration) 2 User Administration windows (IBM Director) (continued)
software distribution task 112 IBM Director Server installation 57
preferences, configuring 137 DB2 Universal Database
upgrading IBM Director Agent configuration 57
software package, installing 86,
109
V Encryption settings 57
Feature and installation directory
VMware
Software Distribution selection 57
authorizing, request access 113
operating systems, supported 18 IBM Director database
Software Distribution task configuration 57
installing IBM Director Agent 107 Microsoft SQL database
software packages W configuration 57
creating 85, 108 Wake on LAN 22 Network driver configuration 57
SQL database 28 enabling on AIX 89 Oracle database configuration 57
starting enabling on Windows service account information 57
programs with event action plans 35 IBM Director Agent, Software-distribution settings 57
Storage installing 100, 104 Windows installation
products, supported tasks 28 IBM Director Server, installing 57 encryption, enabling 57, 100
structure Power Management 24 IBM Director Agent 99
event action plan 36 Web site IBM Director Console 72
event filters 36 IBM Director resources v IBM Director Server 57
System Accounts IBM Redbooks v uninstalling 145
operating systems, supported 18 IBM ServerProven v Windows Management Instrumentation
System i IBM Support v (WMI)
preparing, for installation 39 IBM Systems Management generating events 32
Software v Windows XP
IBM xSeries Systems Management v preparing
T Web sites
Net-SNMP 140
managed system 53
Wired for Management (WfM)
tasks
windows specifications 7
event action plans 35
IBM Director Console wizards
management server support 17
IBM Update Assistant 85, 108 Event Action Plan 35
operating systems, supported 17
Windows InstallShield
publishing events 36
event log IBM Director Agent 100
User Administration 112
generating events 32 IBM Director Console 73
terminology
installing IBM Director Server 57
alert 32
IBM Director Core Service 81
event 32
windows (IBM Director)
managed system 1
management console 2
IBM Director Agent installation
(NetWare)
X
management server 1 xSeries 225, machine type 8647 44
Choose destination location 98
notification 32 xSeries 226, machine type 8836 44
InstallShield Wizard complete 98
resolution 32 xSeries 236, machine type 8841 44
Select Components 98
SNMP device 1 xSeries 336, machine type 8837 44
IBM Director Agent installation
thresholds xSeries 346, machine type 8840 44
(Windows) 100
event action plans 35
Feature and destination directory
toolbar
selection 100
User Administration 112
Network driver configuration 100
trademarks 164
Security settings 100
Software Distribution settings 100
U Add Share Name 138, 139
unattended installations IBM Update Assistant 85, 108
IBM Director Console 74 IBM Update Package/Root
unattended parameter 74, 82, 102, 106 Directory 85, 108
uninstalling IBM Director Managed System Distribution
Windows 145 Preferences 139
Update Manager New Scheduled Job 86, 109
operating systems, supported 18 Server Preferences 138
upgrading Software Distribution Manager
IBM Director Agent (Premium Edition) 85, 108
Windows 103 Software Distribution Manager
Software Distribution task, using 85, (Standard Edition) 85, 108
108 Software Distribution
user Preferences 137
IDs IBM Director Console installation
operating system 112 Feature and destination directory
profiles 112 selection 73

Readers’ Comments — We’d Like to Hear from You
IBM Systems
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
_________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape
Cut or Fold
Along Line

Printed in USA

Dir5.20 Docs Express Install

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Dir5.20 Docs Express Install

Hochgeladen von

Copyright:

Verfügbare Formate

First Edition (December 2006)

New in version 5.20 . . . . . . . . . ix Chapter 5. Installing IBM Director

© Copyright IBM Corp. 1999, 2006 iii

iv IBM Director Express Planning, Installation and Configuration Guide

Conventions and terminology

Note: These notices provide important tips, guidance, or advice.

Attention: These notices indicate possible damage to programs, devices, or data.

IBM Director resources on the World Wide Web

© Copyright IBM Corp. 1999, 2006 v

vi IBM Director Express Planning, Installation and Configuration Guide

IBM Redbooks™ publications

About this book vii

Remote Supervisor Adapter

How to send your comments

viii IBM Director Express Planning, Installation and Configuration Guide

Improvements to the installation procedure for IBM Director

Improvements to the way you work in IBM Director

© Copyright IBM Corp. 1999, 2006 ix

x IBM Director Express Planning, Installation and Configuration Guide

IBM Director Agent support for new hardware

Discontinued features in version 5.20

New in version 5.20 xi

Introducing IBM Director

IBM Director environment

IBM Director is designed to manage a complex environment that contains

An IBM Director environment contains the following groups of hardware:

Figure 1 on page 2 shows the hardware in an IBM Director environment.

© Copyright IBM Corp. 1999, 2006 1

IBM Director components

The IBM Director software has four components:

2 IBM Director Express Planning, Installation and Configuration Guide

IBM Director Core Services

IBM Director Core Services provides management entirely through standard

You can perform the following tasks on a Level-1 managed system:

Chapter 1. Getting started with IBM Director 3

IBM Director Agent

IBM Director Console

4 IBM Director Express Planning, Installation and Configuration Guide

IBM Director Server

Chapter 1. Getting started with IBM Director 5

Specified operating environments

Hardware requirements for IBM Director

Because a system configured with the minimum requirements might perform

Hardware requirements for x86-compatible systems

When reviewing the hardware requirements, consider the following information:

© Copyright IBM Corp. 1999, 2006 7

100 MB (for Linux) 165 MB (for Linux)

Hardware requirements for servers running AIX

When reviewing the hardware requirements, consider the following information:

Hardware requirements for servers running Linux on POWER

When reviewing the hardware requirements, consider the following information:

8 IBM Director Express Planning, Installation and Configuration Guide

Hardware requirements for System i products

When reviewing the hardware requirements, consider the following information:

Hardware requirements for IBM System z servers

The following System z servers are supported:

10 IBM Director Express Planning, Installation and Configuration Guide

Ports used by IBM Director

interprocess page 13; 14248 TCP; 4490 IPX (read);

IBM Director → IBM Director Server 2033 TCP

5988 TCP (other

5989 TCP (other

HTTP IBM Director Server → BladeCenter switch 80 TCP