Académique Documents
Professionnel Documents
Culture Documents
IBM Systems
IBM Director
Planning, Installation, and Configuration Guide
Version 5.20
GC30-4163-01
IBM Systems
IBM Director
Planning, Installation, and Configuration Guide
Version 5.20
GC30-4163-01
Note
Before using this information and the product it supports, read the information in “Notices” on
page 389.
This edition applies to version 5.20 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 AIX (program number 44E7846), IBM Director
for Linux on POWER (program number 44E7847), IBM Director for Linux on System z (program number 5648-DR1),
and IBM Director on x86 (program numbers 5765-DIR, 44E7845, 44E7841, 42D8237, and 42D8238) and to all
subsequent releases and modifications until otherwise indicated in new editions.
© Copyright International Business Machines Corporation 1999, 2007. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . vii Supported operating systems . . . . . . . 73
Support of IBM Director tasks across operating
Tables . . . . . . . . . . . . . . . ix systems . . . . . . . . . . . . . . . 84
IBM Director task support for BladeCenter
products . . . . . . . . . . . . . . 93
About this book . . . . . . . . . . xiii IBM Director task support for Storage products 94
Conventions and terminology . . . . . . . . xiii Supported database applications . . . . . . 94
Related information . . . . . . . . . . . xiii National languages supported by IBM Director 98
How to send your comments . . . . . . . . xvi Planning to install IBM Director . . . . . . . 98
Reviewing the environment . . . . . . . . 99
New in IBM Director . . . . . . . . xvii Choosing IBM Director optional components
New in version 5.20.2 . . . . . . . . . . xvii and extensions . . . . . . . . . . . . 102
New in version 5.20.1 . . . . . . . . . . xxv Licensing requirements for IBM Director
New in version 5.20 . . . . . . . . . . xxviii components and extensions. . . . . . . . 106
Choosing between standard and express
Chapter 1. Overview of IBM Director . . 1 installation of IBM Director Server . . . . . 108
Introducing IBM Director . . . . . . . . . .1 Choosing the IBM Director Server installation
IBM Director components . . . . . . . . .2 options . . . . . . . . . . . . . . 109
IBM Director Core Services . . . . . . . .3 Choosing where to install IBM Director Server 111
IBM Director Agent . . . . . . . . . . .4 Choosing the IBM Director database application 112
IBM Director Console . . . . . . . . . .4 Choosing the management level for managed
IBM Director Server . . . . . . . . . . .5 systems . . . . . . . . . . . . . . 115
Concepts . . . . . . . . . . . . . . .5 Planning for virtual environments . . . . . 117
Accessibility . . . . . . . . . . . . .5 Planning to update IBM Director . . . . . . . 118
Associations . . . . . . . . . . . . .6 Version compatibility of IBM Director version
Common Information Model . . . . . . . .9 5.20.2 components . . . . . . . . . . . 118
Discovery . . . . . . . . . . . . . . 11 Version compatibility of IBM Director version
Event management . . . . . . . . . . . 16 5.20.1 components . . . . . . . . . . . 120
External application tasks. . . . . . . . . 27 Version compatibility of IBM Director version
Managed-object groups . . . . . . . . . 30 5.20 components . . . . . . . . . . . 121
High availability . . . . . . . . . . . . 32 Planning for events . . . . . . . . . . . 122
Managed objects . . . . . . . . . . . . 32 Planning events to be monitored . . . . . . 123
Managed system . . . . . . . . . . . 34 Planning for event action plan implementations 124
Mass configuration . . . . . . . . . . . 36 Planning IBM Director users and user groups . . 127
Microsoft Cluster Management . . . . . . . 37
Naming conventions and physical platform Chapter 3. Installing . . . . . . . . 129
managed objects . . . . . . . . . . . . 37 Preparing to install IBM Director . . . . . . . 129
Network-timeout settings and command Obtaining licenses for IBM Director components
processing . . . . . . . . . . . . . . 38 and extensions . . . . . . . . . . . . 129
Scalable objects . . . . . . . . . . . . 39 Preparing the IBM Director database . . . . 131
Security . . . . . . . . . . . . . . 42 Preparing firewalls and proxies for IBM Director 141
Service processors . . . . . . . . . . . 49 Preparing to manage service processors with
SNMP devices . . . . . . . . . . . . 54 IBM Director . . . . . . . . . . . . 141
Software distribution . . . . . . . . . . 55 Preparing the management server . . . . . 146
Storage managed objects . . . . . . . . . 57 Preparing a system for IBM Director Console 158
Update Manager . . . . . . . . . . . 60 Preparing a Level-2 managed system . . . . 162
Update Manager profile . . . . . . . . . 60 Preparing a Level-1 managed system . . . . 169
UpdateXpress System Pack . . . . . . . . 61 Preparing to manage a BladeCenter . . . . . 174
Upward integration. . . . . . . . . . . 61 Preparing Windows XP managed systems . . . 177
User interfaces . . . . . . . . . . . . 65 Preparing Windows Vista managed systems . . 178
Preparing Hardware Management Console
Chapter 2. Planning . . . . . . . . . 67 devices for discovery with IBM Director . . . 181
Specified operating environments . . . . . . . 67 Installing IBM Director using the Standard
Hardware requirements for IBM Director . . . 67 installation . . . . . . . . . . . . . . 182
Network requirements . . . . . . . . . . 70
Glossary . . . . . . . . . . . . . 393
Contents v
vi IBM Director Planning, Installation, and Configuration Guide
Figures
1. Hardware in an IBM Director environment 2 12. Creating a software package: Software
2. Software in an IBM Director environment 3 Distribution Manager window (Standard
3. Managing system updates in an IBM Director Edition) . . . . . . . . . . . . . 244
environment . . . . . . . . . . . . 60 13. Creating a software package: Software
4. Example of BladeCenter deployment network Distribution Manager window (Premium
when IBM Director Server is not installed on Edition) . . . . . . . . . . . . . 244
a blade server . . . . . . . . . . . 175 14. Creating a software package: Software
5. Example of BladeCenter deployment network Distribution Manager window (Standard
when IBM Director Server is installed on a Edition) . . . . . . . . . . . . . 271
blade server . . . . . . . . . . . . 177 15. Creating a software package: Software
6. Installing IBM Director Server on Windows: Distribution Manager window (Premium
Feature and Installation Directory Selection Edition) . . . . . . . . . . . . . 272
window . . . . . . . . . . . . . 212 16. Modifying IBM Director Agent on NetWare:
7. Installing IBM Director Server on Windows: Choose Destination Location window . . . 274
Feature and Installation Directory Selection 17. Modifying IBM Director Agent on NetWare:
window . . . . . . . . . . . . . 213 Select Components window . . . . . . . 274
8. Installing IBM Director Server on Windows: 18. Program Maintenance window . . . . . . 275
IBM Director Service Account Information 19. Creating a software package: Software
window . . . . . . . . . . . . . 213 Distribution Manager window (Standard
9. Installing IBM Director Server on Windows: Edition) . . . . . . . . . . . . . 284
Encryption Settings window . . . . . . 214 20. Creating a software package: Software
10. Installing IBM Director Server on Windows: Distribution Manager window (Premium
Network Driver Configuration window . . . 215 Edition) . . . . . . . . . . . . . 285
11. Installing IBM Director Server: IBM Director 21. Program Maintenance window . . . . . . 344
Database Configuration window . . . . . 216
Tables xi
xii IBM Director Planning, Installation, and Configuration Guide
About this book
This book provides information about installing and configuring IBM Director. In
addition to presenting an overview of IBM Director and its requirements, it covers
the following topics:
v Planning an IBM Director environment
v Installing IBM Director and IBM Director extensions
v Upgrading from IBM Director 4.2 or earlier to IBM Director 5.20
v Configuring IBM Director
It also includes information about IBM Director security and solving problems you
might encounter with IBM Director.
Important: These notices provide information or advice that might help you avoid
inconvenient or difficult situations.
Related information
Besides this documentation, there is additional information related to IBM®
Director.
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
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.
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.
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.
Note: Managed objects that do not support management using IPv4 cannot
be managed by IBM Director.
Improved installation process for AIX®
Required APAR fixes are automatically installed with IBM Director.
Enhanced memory resource monitoring for AIX
New resource monitoring for paging space and networking on AIX
For complete hardware support information, see the IBM Director Hardware and
Software Support Guide.
IBM Director Version 5.20.2 supports management of the following systems and
products.
IBM systems supported for Level-2 management with IBM Director Agent
v IBM System x3350, machine type 4192
v IBM System x3455, machine types 7984
v IBM System x3500, machine type 7977
v IBM System x3850 M2, machine type 7141 (single-node only)
v IBM System x3950 M2, machine type 7141 (single-node only)
v IBM System p 550, machine type 8204-E8A
v IBM BladeCenter HC10 workstation blade, machine type 7996
v IBM BladeCenter HS21 XM blade server, machine type 7995
v IBM BladeCenter JS22 blade server, machine type 7998-61X
IBM systems with limited support for Level-0 management
v QS21 blade server, machine type 07921
Blade Expansion Units
v PCI Expansion Unit 3e
BladeCenter chassis
v BladeCenter S chassis, machine type 8886
BladeCenter Switches
v Non-RAIDed Serial Attached SCSI (SAS) switch module for IBM
BladeCenter
v BladeCenter S Disk Storage Modules
Host bus adapters
v Emulex 4 Gb Fibre Channel compact form factor vertical (CFFv) HBA for
BladeCenter, part number 43W6859
v 6Gb Serial Attached SCSI (SAS) host bus adapter
v Qlogic single port 4Gb Fibre Channel host bus adapter
v 8Gb Fibre Channel host bus adapter
Daughter cards (blades)
Resolved APARs
IBM Director version 5.20.2 fixes the following Authorized Program Analysis
Reports (APARs):
IC51628
Inventory collection for a Level-0 managed system running Linux can time
out, inventory collection to time out for other Level–0 and Level-1
managed systems.
Note: This APAR was incorrectly listed as fixed in the release notes for
version 5.20.1.
IC52526
The self-monitoring, analysis, and reporting technology (SMART) provider
can issue SCSI commands that are not valid to SCSI storage devices,
leading to errors.
IC52563
IBM Director Agent running on VMware ESX versions 2.5.3 and 2.5.4 does
not collect inventory.
IC52568
Performing inventory on a Level-2 Linux managed system with an LSI
1064 RAID controller will cause the LSI RAID array to immediately go to
the degraded state.
IC52606
When the Nmap utility is used with the TCP connect scan option (nmap
-sT), the scan causes the Secure Sockets Layer (SSL) listener to close,
resulting in a loss of SSL communications between IBM Director Server
and IBM Director Console. This occurs only for management servers
running Linux. The default SYN scan option for Nmap does not cause this
problem.
For IBM Director 5.20 and 5.20.1, restart IBM Director Server when this
problem occurs.
Note: This APAR was incorrectly listed as fixed in the release notes for
version 5.20.1.
IC52620
IBM Director Server runs out of Service Nodes. This leads to numerous
problems, including the inability to log in using IBM Director Console,
tasks that do not work, and unexpected shutdowns of IBM Director Server.
IC52660
The start time of a scheduled task can change after the management server
is shut down and restarted.
IC52704
When an event action plan starts multiple programs on a managed system
running Windows, an error (Software communication error = X’ffff1103’)
occurs.
IC52827
The Software Distribution configuration in the SwDistConfig.properties file
is not updated when upgrading from version 5.10.3 or earlier.
For complete hardware support information, see the IBM Director Hardware and
Software Support Guide.
IBM Director Agent Version 5.20.1 can be installed on the following new IBM
systems and products.
v IBM System p 570 with POWER6™ processors
v IBM BladeCenter HT Chassis
v IBM System Storage DS3400
IBM Director Version 5.20.1 provides support for the following additional switches:
v Cisco 4 Gb 10 port Fibre Channel Switch Module, Part Number 39Y9284
v Cisco 4 Gb 20 port Fibre Channel Switch Module, Part Number 39Y9280
v Nortel 10 Gb Ethernet Switch Module, Part Number 39Y9267
v QLogic 10-port 4 Gb SAN Switch Module for IBM BladeCenter, Part Number
43W6724
v QLogic 20-port 4 Gb SAN Switch Module for IBM BladeCenter, Part Number
43W6725
v QLogic 4 Gb Intelligent Pass-thru Module for IBM BladeCenter, Part Number
43W6723
IBM Director Version 5.20.1 provides inventory awareness for the following
additional devices:
v Switch Legacy Interface Module (SLIM)
v Concurrent keyboard/video/mouse (cKVM) feature card
IBM Director Server supports the following newer versions of external databases:
v Apache Derby V10.2 (embedded with IBM Director Server 5.10 Update 1)
v IBM DB2® Universal Database
– version 9.1 with Fix Pack 2
– version 8.2 with Fix Pack 7
– version 8.1 with Fix Pack 14
For complete information about database support in IBM Director 5.20 Update 1,
see the “Supported database applications” topic in the information center.
Security enhancement
IBM Director version 5.20 improves security for some managed systems through
Intelligent Platform Management (IPMI) 2.0 support. IBM Director version 5.20
includes support for IPMI 2.0 communication using Enhanced Remote
Management Control Protocol (RMCP+) on the following managed systems:
v IBM System x3455
v IBM System x3655
v IBM System x3755
v IBM System x3200
v IBM System x3250
IBM Director Agent version 5.20 can be installed on the following new IBM
systems and products.
IntelliStation
M Pro, machine type 9229
IBM System x3nnn servers
v x3105, machine types 4347 and 4348 (Environmental-sensor monitoring
and hardware events are not supported.)
v x3200, machine types 4362 and 4363
v x3250, machine types 4364 and 4365
v x3455, machine types 7984 and 7986
v x3655, machine type 7985
v x3755, machine type 8877
Two upward integration modules for Version 5.20 were released in June, 2007:
IBM Director Management Pack for Microsoft System Center Operations
Manager 2007
With the IBM Director Management Pack for Microsoft System Center
Operations Manager 2007, you can use your systems-management software
to manage systems installed with Level-1: IBM Director Core Services or
Level-2: IBM Director Agent.
IBM BladeCenter Chassis Management Pack for Microsoft System Center
Operations Manager 2007
With the IBM BladeCenter Chassis Management Pack for Microsoft System
Center Operations Manager 2007, you can use your systems-management
software to manage a BladeCenter chassis.
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 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.
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.
Chapter 1. Overview 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 provides management data to IBM Director Server. Data can
be transferred using several network protocols, including Transmission Control
Protocol/Internet Protocol (TCP/IP), Network Basic Input/Output System
(NetBIOS), and Internetwork Package Exchange (IPX). IBM Director Server can
communicate with all systems in your network that have IBM Director Agent
installed.
IBM Director Agent features vary according to the operating system on which IBM
Director Agent is installed. For example, you can install Microsoft Cluster Browser
only on Windows 32-bit operating systems.
All IBM Intel-compatible servers, IBM BladeCenter JS20 and JS21 blade servers,
NetVista desktop computers, ThinkCentre desktop computers,IBM PC desktop
computers, IBM IntelliStation workstations, IBM ThinkPad mobile computers, IBM
System Storage Network Attached Storage (NAS) products, and IBM SurePOS™
point-of-sale systems include a license for IBM Director Agent. You can purchase
additional licenses for non-IBM systems.
IBM Director Agent is supported on systems that are running the following
operating systems:
v Microsoft Windows
v Linux (System x, POWER, System z)
v IBM AIX
v IBM i5/OS
v Novell NetWare
Systems (IBM or non-IBM servers, desktop computers, workstations, and mobile
computers) that have IBM Director Agent installed on them are referred to as
Level-2 managed systems.
The function of IBM Director Agent on the managed system will vary depending
on the operating system and platform.
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 is the main component of IBM Director; it contains the
management data, the server engine, and the application logic. IBM Director Server
provides basic functions such as discovery of managed objects, persistent storage
of configuration and management data, an inventory database, event listening,
security and authentication, management console support, and administrative
tasks.
IBM Director Server stores the inventory data in a Structured Query Language
(SQL) database. You can access information that is stored in this relational database
even when the managed objects are not available.
Every IBM System x server and IBM BladeCenter unit includes an IBM Director
Server license. You can purchase additional IBM Director Server licenses for
installation on non-IBM servers.
IBM Director Server communicates with managed objects and SNMP devices to
receive information and issue commands. If IBM Director Console is used, IBM
Director Server communicates with IBM Director Console to display network status
information and receive instructions from the system administrator.
Concepts
This section discusses concepts that will help you understand how IBM Director
works. Becoming familiar with the IBM Director components and understanding
the concepts in this section enables you to use IBM Director most effectively.
Accessibility
This topic describes the accessibility features in IBM Director and the IBM Director
extensions.
IBM strives to provide products with usable access for everyone, regardless of age
or ability.
Related information
Chapter 1. Overview 5
Associations
Associations change the organization of a group of managed objects that is
displayed in the Group Contents pane.
You can apply an association type to the group that is currently displayed in the
Group Contents pane. When you apply an association, the association persists the
next time you display that group.
If the group that is currently displayed in the Group Contents pane contains
managed objects that do not apply to the selected association, those objects are
displayed in blue type under the “Not Associated” node.
You also can display additional information about the managed objects that are
displayed in the Group Contents pane by selecting one or more association options
from the bottom half of the Associations menu. For example, you can view
managed objects to which event action plans have been applied. If a managed
object has an event action plan applied to it, the managed object is displayed as a
tree structure that you can expand to view which event action plans have been
applied to the object.
Association type
Associations change the organization of a group of managed objects that is
displayed in the Group Contents pane.
Chapter 1. Overview 7
Servers with Fibre Channel Attached SMI-S Storage
Shows the servers that are connected to SMI-S storage devices through a
Fibre Channel switch.
Tips:
v This association shows only active connections through storage attached
networks (SANs). It does not shows specific connectivity through
switches and direct connections without switches.
v Switches and disk arrays must be discovered as SMI-S objects.
v Inventory must be completed on the storage devices and servers.
SMI-S Storage with Fibre Channel Attached Servers
Shows the SMI-S storage devices that are connected to servers through a
Fibre Channel switch.
Tips:
v This association shows only active connections through storage attached
networks (SANs). It does not shows specific connectivity through
switches and direct connections without switches.
v Switches and disk arrays must be discovered as SMI-S objects.
v Inventory must be completed on the storage devices and servers.
Default associations
Associations change the organization of a group of managed objects that is
displayed in the Group Contents pane. The None association is the default
association for most groups.
This table shows the groups that have default associations other than None.
Table 3. Default associations other than None
Group Default association
All Managed Objects System Membership
Chassis and Chassis Members Chassis Membership
Clusters and Cluster Members Cluster Membership
HMC and HMC Members HMC Membership
Platforms and Platform Members Platform Membership
Racks with Members Rack Membership
Scalable Partition Scalable Partitions Membership
Scalable Systems and Members Scalable Systems Membership
Association options
Select association options to display additional information about the managed
objects that are displayed in the Group Contents pane.
The CIM and Web Based Enterprise Management (WBEM) are standards that are
developed by a consortium of major hardware and software vendors (including
IBM) called the Distributed Management Task Force (DMTF). The CIM provides
the framework by which a system can be managed by using common building
blocks rather than proprietary software. If a device is CIM-compliant, software that
is also CIM-compliant, such as IBM Director, can manage that device.
The infrastructure used by IBM Director for CIM instrumentation consists of the
following components:
CIM Client
The CIM Client is a management application that uses CIM to manage
devices. A CIM Client can reside anywhere in the network, because it uses
HTTP to talk to CIM Object Managers and Agents.
CIM Managed Object
A CIM Managed Object is a hardware or software component that can be
managed by a management application by using CIM. When Level 2: IBM
Director Agent or Level 1: Core Services is installed on a system, the
applicable CIM software is installed and that system becomes a CIM
Managed Object.
CIM Object Manager
The CIM Object Manager (CIMOM), also known as a CIM server, is the
software entity that receives, validates, and authenticates the CIM requests
from the CIM Client. It then directs the requests to the appropriate
component or device provider.
IBM Director locates the CIMOM through discovery. When Level 1: Core Services
is installed on a system, the CIMOM registers itself to the SLP and supplies its
location, IP address, port number, and the type of service that it provides
(management.software.IBM:director-agent). When IBM Director performs an SLP
discovery, the IBM Director SLP service is identified and the system running that
service is displayed as a Level-1 managed system. With this information, IBM
Director can directly communicate with the CIMOM. Director discovers the
CIMOM on Level-2 managed system using a proprietary protocol.
Using CIM as the framework, IBM Director can perform tasks on the managed
system. As requests arrive, the CIMOM validates and authenticates each request. It
Chapter 1. Overview 9
then directs the requests to the appropriate functional component of the CIMOM
or to a device provider. The provider makes calls to a device-unique programming
interface on behalf of the CIMOM to satisfy the IBM Director requests.
By creating shortcuts, or subtasks, you can bypass navigating through the class tree
to reach a specific class or method. You can define two types of shortcuts:
v A user-selected class that displays the instances, properties, and methods that are
associated with a specified class on the selected managed system.
v A user-selected method that runs on the selected managed system.
IBM Director Agent and IBM Director Core Services also install an additional
Windows Service or Linux daemon, as applicable, called CIMListener. This process
listens for subscribed CIM indications and delivers them to the proper indication
handler. The installation also creates a default set of subscriptions between the
handlers and the indications.
Additional reference information is available for IBM Director Core Services default
subscriptions, for CIM indications, and for the cimsubscribe command used to
modify subscriptions.
Discovery
Discovery is the process by which IBM Director Server identifies and establishes
connections with objects, such as systems or devices, that IBM Director can
manage.
Before IBM Director can manage a system or device, that managed object must be
discovered by IBM Director Server. After a managed object has been discovered, an
icon that represents the object is displayed in the IBM Director Console window
when the applicable group is selected. The management server also stores the
addresses of discovered managed objects in the IBM Director database.
Depending on the complexity of your network and the needs of your organization,
you will need to configure the discovery process. You will need detailed
information about the layout of your network, specifically the subnet, port, and
LAN information.
Chapter 1. Overview 11
The type of discovery method that IBM Director uses to connect with managed
objects varies based on the type of device being discovered and the type of
network protocols used by that device.
Agent-initiated discovery
In IBM Director, agent-initiated discovery occurs when managed systems contact IBM
Director Server rather than IBM Director Server searching for managed systems.
Server-initiated discovery
In IBM Director, server-initiated discovery occurs when IBM Director Server searches
the network for Level-0, Level-1, and Level-2 managed systems. Server-initiated
discovery typically is referred to simply as discovery.
The advantage of this type of discovery is ease of configuration; you set the
discovery settings once at the management server.
Broadcast discovery is the default discovery method. From IBM Director Console,
you can change the discovery preferences for the management server according to
your business needs and network requirements.
Broadcast discovery:
When you use broadcast discovery, the management server attempts to discover
manageable objects on the network by transmitting a single request to the entire
subnetwork on which the management server is located.
IBM Director Server broadcasts requests using each protocol supported by IBM
Director (for example, SNMP, SSH, DCOM, SLP, and IPC). You also can use
broadcast discovery on other subnets if your network gateway is configured to
permit broadcast messages. Your network might be configured to allow broadcast
messages within a subnet, but prevent them from passing over to other subnets.
The IP addresses that successfully respond to the broadcast request are saved in
IBM Director along with the applicable protocol information. IBM Director Console
displays the objects that respond to the broadcast discovery and that support one
or more of the protocols that IBM Director uses.
Note: By default, Level-0 managed systems are not discovered using broadcast
discovery. Level-0 managed systems are discovered using unicast discovery, and an
IP address range must be specified for the unicast.
Multicast discovery:
Multicast discovery is used to identify Level-1 and Level-2 managed systems. This
discovery method is useful on networks that are configured to filter broadcast
requests but not multicast requests.
Note: You can use multicast discovery to identify systems across multiple subnets
without configuring specific network information for each subnet. However, some
networks are configured to prevent multicast requests from passing between
subnets. Contact your network administrator to determine the best discovery
method for your organization.
Chapter 1. Overview 13
This discovery method is useful when the management server and the managed
systems belong to different subnets and the network is configured to filter
broadcast requests across those subnets.
Note: Although it is not a requirement, the Level-2 managed system that performs
the general broadcast discovery is typically on a different subnet from the
management server.
When managed systems on the same subnet as the Level-2 managed system
receive the discovery request, they reply directly to the management server that
made the original request. This type of discovery generates less network traffic
than a unicast discovery and avoids many of the problems associated with
broadcast discovery when the network is configured to filter or prevent broadcasts.
You might want to consider broadcast relay discovery if you have multiple
physical locations in which managed systems reside, with lower-bandwidth
network infrastructure (such as T1 or frame relay) between these physical sites.
Unicast discovery:
You can use this discovery method if your network filters both broadcast and
multicast requests.
The disadvantage of a unicast discovery is that an IP packet must be sent for each
individual IP address, which increases network traffic.
When you install Level 1: IBM Director Core Services on a system, SLP and the
IBM Director Agent SLP service type (management.software.IBM:director-agent) are
installed on that system. Common Information Model (CIM) also is installed with
Level 1: IBM Director Core Services.
You can configure IBM Director to send an SLP discovery request as a unicast,
multicast, or broadcast message. Some older versions of service agents do not
support multicasting and might have to be discovered by using a broadcast.
Manual discovery
In IBM Director, manual discovery occurs when a user instructs IBM Director Server
to add a specific managed object. Manual discovery can be performed in IBM
Director Console or from the command line.
During manual discovery, IBM Director Server attempts to contact the managed
object using the protocol defined for the managed-object type and the information
provided by the user. If IBM Director Server successfully contacts the managed
object, the object is added for management and is displayed in IBM Director
Console.
When IBM Director Server attempts to add a managed system, it uses the
following procedure to contact the managed system and determine the type of
management that is supported:
1. Check for the Level-2 protocol (ports 14247 on Windows, 14248 on Linux).
2. If the system does not respond, check for the Level-1 protocol (SLP port 427).
3. If the system still does not respond, check for the Level-0 protocols (ssh port 22
or Windows RPC ports 137-139, 145).
After IBM Director Server determines the system type, it creates a managed object.
If none are detected, an error is reported.
Note: You can rename managed objects in IBM Director Console after they have
been added. The display name for the managed object in IBM Director Console can
be changed independently from the name which is defined on the managed object
itself.
BladeCenter chassis, physical platforms, SMI-S storage devices
When these managed objects are discovered, they are named according to
the naming-convention template specified in the Discovery Preferences
window.
Hardware management consoles, Level-0 managed systems, Level-1 managed
systems, SNMP devices, z/VM centers
IBM Director Server uses the name returned by the managed object.
Chapter 1. Overview 15
Level-2 managed systems (Linux)
IBM Director Server uses the host name as returned by the managed
system.
Level-2 managed systems (Windows)
IBM Director Server uses the name specified in the Network Driver
Configuration on the managed system. By default, this is set to the
uppercase computer name.
Event management
An event is an occurrence of significance to a task, system, or managed object, such
as the completion or failure of an operation. In a system-management
environment, IBM Director Server receives events, traps, and notifications from
many sources.
These sources include, but are not limited to, the following programs and
protocols:
v IBM Director native events generated by IBM Director Agent
v CIM indications from the CIMOM that is installed as part of IBM Director Agent
and IBM Director Core Services
v Microsoft Windows event log
v Windows Management Instrumentation (WMI)
v SNMP traps through out-of-band communication
v Platform Event Traps (PET) through out-of-band communication from Alert
Standard Format (ASF)-capable systems and Intelligent Platform Management
Interface (IPMI)- capable systems
v IBM service processors notifications through out-of-band communication
When IBM Director Server receives these events or notifications, it converts them
into IBM Director events. For example, when IBM Director Server receives a CIM
indication, it converts the CIM indication into an IBM Director event of the type
CIM. When you view the Event Filter Builder tree, the CIM events are displayed
under the CIM node in the tree.
Note: IBM Director can convert CIM indications into other event types, including
event types that are used by enterprise-level system-management programs, such
as SNMP events. Using these event types, IBM Director can provide system data to
the enterprise-level system-management programs through the IBM Director
Upward Integration Modules. For more information, see “CIM indications in IBM
Director” in the IBM Director Events Reference.
However, these SNMP events are not the same as SNMP traps that IBM Director
Server receives out-of-band (that is, not through IBM Director Agent or IBM
Director Core Services). Out-of-band SNMP traps are generated by hardware
products and other software programs. They are displayed under the SNMP node
in the Event Filter Builder tree, but beneath a different subnode.
You can use the events in the Event Filter Builder tree when working with
managed objects. To monitor one or more events, you must create an event filter
that contains an event type from one of these sources, use the event filter as part of
an event-action plan, and then apply the event-action plan to a managed object.
Events from the Windows event log are displayed in the Windows event log tree in
the Event Type Filter Builder. Events from WMI are displayed in the Common
Information Model (CIM) tree.
In IBM Director, an event can be in one of the following categories: alert and
resolution. Typically, an alert is the occurrence of a problem relating to a managed
object. A resolution is the occurrence of a correction or solution to a problem.
Note: In the IBM Director product, there are tasks and features that use the word
alert in place of the word event. Also, ServeRAID Manager uses the word
notification instead of event.
Even though these events are generated by their respective operating systems (or
an optional layer that is installed on the operating system), IBM Director does not
process these events unless you create an event-action plan to do so. When you
install IBM Director, it has one predefined active event-action plan: Log All Events.
However, this event-action plan does not log these Windows- or i5/OS-specific
events. You must create an event-action plan with a simple-event filter that
contains the event types for one or more of these events. Then, you must apply
this event-action plan to the managed object running Windows or i5/OS.
When IBM Director Agent starts on a managed object running Windows, the
twgescli.exe program starts, too. This program listens for IBM Director Server to
send a message to IBM Director Agent that an event-action plan has been applied
to that managed object. If the event-action plan includes a simple-event filter that
contains the event types for any of the Windows-specific events, IBM Director
appropriates these events for its own use. This is called event subscription. The
twgescli.exe program subscribes to the event types that are specified in the
event-action plan and translates the Windows-specific events into an IBM Director
event type. Then, the program forwards the events to the management server from
which the event-action plan was applied.
When IBM Director Agent starts on a managed object running i5/OS, the process
is the same with comparable code to twgescli.exe that is included in IBM Director
Agent for i5/OS.
Chapter 1. Overview 17
IBM Director completes the following steps to determine which event actions to
perform:
1. The managed object generates an event and forwards the event to all the
management servers that have discovered the managed object (except for some
events, such as those that are generated through meeting or exceeding a
resource-monitor threshold, which are sent only to the management server
where the thresholds are configured and applied).
2. IBM Director Server processes the event and determines which managed object
generated the event and which group or groups the managed object belongs to.
3. IBM Director Server determines whether any event-action plans are applied to
the managed object or to any of the groups of which the managed object is a
member.
4. If an event-action plan has been applied, IBM Director Server determines
whether any event filters match the event that was generated.
5. The management server performs any event actions for each matching event
filter.
Event-action plans
When you create an event-action plan, you attach one or more event actions to a
specified event filter. Then, you include one or more event filters in the
event-action plan. Finally, you apply that event-action plan to a system or group of
systems.
By creating event-action plans and applying them to specific managed objects, you
can be notified by e-mail or pager, for example, when a specified threshold is
reached or a specified event occurs. Or you can configure an event-action plan to
start a program on a managed object and change a managed-object variable when
a specific event occurs. You can use process-monitor events and resource-monitor
events to build an event-action plan.
You can modify an existing event-action plan, even one that is already applied to
managed objects or groups, using the Event Action Plan Builder.
Event filters
An event filter specifies an instance of one or more events that you want IBM
Director to process. IBM Director ignores any event instances that do not meet the
You can use an event filter to capture a single event or multiple events. The
following list includes some of the criteria that you can use to determine whether
to include an event with other events:
v All managed objects that are targeted for the filter are able to generate all events
that are included in the filter. If the managed object does not generate the event
for which the filter is defined, the filter will not be effective on that managed
object.
v The event actions that will be used to respond to the event are the same for all
targeted objects.
v The other event filter options besides the event type are common for all targeted
objects. These settings include the number of times the event filter is active, the
severity of the event, and other attributes.
Event-action plans can include event filters with event types that are not generated
by all managed objects. In such instances, you can apply the event-action plan to
those managed objects, but it will have no effect. For example, if an event filter is
based on a ServeRAID event and that event-action plan is applied to managed
objects that do not have a ServeRAID adapter installed, the event filter has no
events to filter, and therefore, no actions are performed. If you understand this
concept, you can create more complex event-action plans, and you can reduce the
number of event-action plans you have to build and maintain.
All currently available event types are displayed in the tree on the Event Type
page in the Event Filter Builder window. The currently installed tasks and
extensions publish their events in the Event Type tree when IBM Director Server or
IBM Director Agent or IBM Director Core Services starts.
Note: Whether the events are published when IBM Director Server or IBM
Director Agent or IBM Director Core Services starts depends on the tasks or
extensions and how they are implemented.
If you add an extension to your IBM Director installation, the extension might
publish its events either when it is added to the installation or when the extension
sends its first event. If the extension publishes when it sends its first event, only
that event is published.
Event-filter types:
In the Event Action Plan Builder window, the Event Filters pane provides the
following event filters.
Chapter 1. Overview 19
Event filter Description
Simple Event Simple event filters are general-purpose filters; most event filters are
this type. When you expand this tree, any customized simple event
filters that you have created are displayed. Also, the following
predefined, read-only event filters are displayed:
v All Events
v Critical Events
v Environmental Sensor Events
v Fatal Events
v Hardware Predictive Failure Events
v Harmless Events
v Minor Events
v Security Events
v Storage Events
v Unknown Events
v Warning Events
If you want to see what events are included in a predefined event filter,
double-click that predefined event filter in the Event Filters pane. The
Simple Event Filter Builder window opens, and the Event Filter Builder
notebook is displayed. Select the applicable notebook page to view the
selected event filters. For example, click the Severity tab to view the
selections for the Critical Event filter. You cannot change predefined
event filters; they are read-only. However, you can make changes and
click File → Save As to save the modified event filter with another
name.
Duplication Event Duplication event filters ignore duplicate events, in addition to the
options that are available in the simple event filters.
To use this filter, you must specify the number of times (Count) that the
same event is ignored during a specified time range (Interval). Then,
this filter processes the first event that meets the criteria that are
defined for this filter. Only the first event triggers the event actions that
are associated with this event filter. For the associated event actions to
be triggered again, one of the following conditions must be met:
v The value that is specified in the Count field must be exceeded.
v The time range that is specified in the Interval field must elapse.
v The value that is specified in the Count field must be exceeded by 1
(Count+1) within the time range that is specified in the Interval field.
For example, you can define a duplication event filter to filter on the
occurrence of an offline event and define a corresponding event action
to forward the event to IBM Director Server. Depending on the criteria
that you define, only the first event announcing that the system is
offline is processed, and all other instances in which an event meets the
filtering criteria are discarded until the Count value is exceeded during
the specified interval.
Exclusion Event Exclusion event filters exclude certain event types, in addition to the
simple event filter options. Using this filter, you define the criteria of
the events to exclude.
An event that meets the criteria that are defined in this filter triggers
associated actions only after an event has met the criteria for the
number of times that are specified in the Count field or only after the
number of times specified in the Count field within the time range
specified in the Interval field.
Event-filter criteria:
Depending on the event-filter type, you set specific values for these types of
criteria.
Criteria Description
Event Type Use the Event Type page to specify the source or sources of the events that
are to be processed. This tree is created dynamically; and entries are added by
tasks and as new alerts are received. Entries in the tree can be expanded to
display suboption events.
Most event filters are created using only this page. It specifies the source or
sources of the events that are to be processed by this filter.
By default, the Any check box is selected, meaning that none of the events
that are listed are filtered, except for Windows-specific and i5/OS-specific
events. If you want to specify certain events on which to filter, clear the Any
check box. You can highlight more than one event by pressing the Ctrl or
Shift key.
Notes:
1. When you select a root option in the Event Type tree, all suboption events
are selected as well. For example, when you select MPA in the Simple
Event Filter Builder window, all Component, Deployment, Environmental,
and Platform suboption events are selected also.
If additional event types are published after you create the event filter, the
newly available event types are included in your event filter only if the
new event types are suboption events of an event type that you selected.
However, if you want to include a newly published event type that is not
a suboption event, you must update the event filter by selecting the new
event type.
2. The event types for BladeCenter events are displayed under MPA, except
for BladeCenter Configuration Management events, which are displayed
under Configuration Management.
Chapter 1. Overview 21
Criteria Description
Severity Use the Severity page to indicate the urgency of the events that are filtered. If
an event is received whose severity level is not included in the event filter,
the filter will not process that event. By default, the Any check box is
selected, indicating that all event severities are processed by the filter.
When you select more than one severity, they are joined together using logical
OR. The source of the event determines what severity the event is. Generally,
the severity levels have the following meanings:
Fatal The event caused a failure and must be resolved before the program
or component is restarted.
Critical The event might cause a failure and must be resolved immediately.
Minor The event is not likely to cause immediate program failure but
should be resolved.
Warning
The event is not necessarily problematic but might warrant
investigation.
Harmless
The event is for information only. Most events of this severity do not
indicate potential problems. However, offline events are categorized
as harmless, and these events can indicate potential problems.
Unknown
The application that generated the event did not assign a severity
level.
Day/Time Use the Day/Time page to set the filter to accept and ignore events on certain
days and at certain times of the day. By default, the Any check box is
selected, indicating that events that occur at any time are processed by the
event filter.
The time zone that applies to the specified time is the time zone in which the
management server is located. If your management console is not in the same
time zone as the management server, the difference in time zones is displayed
above the Selections pane as an aid to determining the correct time.
By default, all events are passed through all filters. This includes events that
were queued by IBM Director Agent because the link between the managed
object and the management server was unavailable. However, you can
prevent these queued events from being processed by a filter by selecting the
Block queued events check box. This option can be useful if the timing of the
event is important or if you want to avoid filtering on multiple queued events
that are sent all at once when IBM Director Server becomes accessible.
However, you can block queued events only if you filter events at a specified
time. To block queued events, you must clear the Any check box.
Category Use the Category page to specify an event filter according to the status of an
event (alert or resolution of a problem). However, not all events have
resolutions.
Initially, only IBM Director Server is shown in the list. As other managed
objects generate events, such as when a threshold is exceeded, this list is
added to dynamically. If you anticipate that other managed objects will
generate events, you also can type managed-object names into the field and
click Add to add them.
Extended Use the Extended Attributes page to specify additional event-filter criteria
Attributes using additional keywords and keyword values that you can associate with
some categories of events, such as SNMP. This page is available only when
you clear the Any check box on the Event Type page and select certain entries
from that page.
If the Extended Attributes page is available for a specific event type but no
keywords are listed, IBM Director Server is not aware of any keywords that
can be used for filtering.
To view the extended attributes of specific event types, expand the Event Log
task in the IBM Director Console Tasks pane and select an event of that type
from the list. The extended attributes of the event, if any, are displayed at the
bottom of the Event Details pane, below the Sender Name category.
System Use the System Variables page to further qualify the filtering criteria by
Variables specifying a system variable. This page is available only if there are one or
more system variables. A system variable consists of a user-defined pairing of
a keyword and value that are known only to the local management server.
Note: These user-defined system variables are not associated with the system
variables of the Windows operating system.
Event Text Use the Event Text page to specify event message text to associate with the
event.
Event actions
The event action specifies the actions that you want IBM Director to take as a result
of the occurrence of an event.
IBM Director has several predefined event action types. With the exception of Add
to Event Log, you must customize each event action type that you want to use.
Add/Remove “event” system to Static Group
Adds a managed object to or removes a managed object from a specified
static group when the managed object logs a specific event.
Add/Remove source group members to target static group
Adds all specified managed objects in a source group to a target group or
removes all specified managed objects from the target group.
Add a Message to the Console Ticker Tape
Displays a message in red type that scrolls from right to left at the bottom
of IBM Director Console.
Chapter 1. Overview 23
Add to the Event Log
Adds a description of the event to the IBM Director event log. This action
cannot be customized.
Define a Timed Alarm to Generate an Event
Generates an event only if IBM Director does not receive an associated
event within the specified interval.
Define a Timed Alarm to Start a Program on the Server
Starts a program on the management server if IBM Director does not
receive an associated event within the specified interval.
Log to Textual Log File
Generates a text log file for the event that triggers this action.
Post a News Group (NNTP)
Sends a message to a newsgroup using the Network News Transfer
Protocol (NNTP).
Resend Modified Event
Creates or changes an event action that modifies and resends an original
event.
i5/OS, AIX, and Linux only: Send an E-mail to a Mobile Phone
Sends an e-mail message to a specified mobile phone.
Windows only: Send an Alphanumeric Page (via TAP)
Sends an alphanumeric message to a pager using TAP.
Send an Event Message to a Console User
Displays a pop-up message on the management console of one or more
specified users.
Send an Internet (SMTP) E-mail
Sends a Simple Mail Transfer Protocol (SMTP) e-mail message.
Send an SNMP Inform to an IP host
Sends an SNMP inform request to a specified IP host.
Send an SNMP Trap to a NetView Host
Generates an SNMP trap and sends it to a specified NetView host using a
TCP/IP connection to the host. If delivery of the SNMP trap fails, a
message is posted in the history log of the managed object.
Send an SNMP Trap to an IP Host
Generates an SNMP v1 or SNMP v2c trap and sends it to a specified IP
address or host name.
Windows only: Send a Numeric Page
Sends a numeric message to a pager.
Send a TEC Event to a TEC Server
Generates a Tivoli Enterprise Console event and sends it to a specified
Tivoli Enterprise Console server.
Set an Event System Variable
Sets the managed system variable to a new value or resets the value of an
existing system variable.
Start a Program on a System
Starts a program on any managed objects on which IBM Director Agent is
installed.
Event-data-substitution variables
For some event-action types, you can include event-specific information as part of
the text message. Including event information is referred to as event-data
substitution. You can use these event-data-substitution variables to customize event
actions.
&date The date the event occurred.
&time The time the event occurred.
&text The event details, if they are supplied by the event.
&type The event-type criteria that are used to trigger the event. For example, the
event that is generated when a managed object goes offline is of type
Director > Topology > Offline. This corresponds to the entry on the Event
Type page.
&severity
The severity level of the event.
&system
The name of the managed object for which the event was generated. The
system name is either the name of IBM Director Agent or, in the case of an
SNMP device, the TCP/IP address.
&sender
The name of the managed object from which the event was sent. This
variable returns null if the name is unavailable.
&group
The group to which the target object belongs and is being monitored. This
variable returns null if the group is unavailable.
&category
The category of the event, either Alert or Resolution. For example, if the
managed object goes offline, the category is Alert. If the managed object
goes online, the category is Resolution.
&pgmtype
A dotted representation of the event type using internal type strings.
×tamp
The coordinated time of the event.
Chapter 1. Overview 25
&rawsev
The nonlocalized string of event severity (Fatal, Critical, Minor, Warning,
Harmless, Unknown).
&rawcat
The nonlocalized string of event category (Alert, Resolution).
&corr The correlator string of the event. Related events, such as those from the
same monitor-threshold activation, will match this.
&snduid
The unique ID of the event sender.
&sysuid
The unique ID of the managed object that is associated with the event.
&prop:file_name#property_name
The value of the property string property_name from property file file_name
(relative to the IBM\Director\classes directory).
Message Browser
You can use the Message Browser to view events that are sent to IBM Director
Console. The Message Browser is displayed automatically whenever an alert is sent
to the management console.
You can choose to have events sent to the management console when an event
occurs by configuring an event action plan with the Send an Event Message to a
Console User event action.
The Message Browser displays all alerts, including management console ticker-tape
alerts. However, the Message Browser does not display any ticker-tape messages. A
ticker-tape message can display, for example, resource-monitor data.
26 IBM Director Planning, Installation, and Configuration Guide
Choosing between resource and process monitors
Process monitors and resource monitors are important tools for monitoring
applications. Through the implementation of these monitors, you have access to
events that can trigger an event action plan to resolve a problem quickly and
automatically. How you intend to use your event action plan can help determine
whether you should use a resource monitor or a process monitor.
If you want to monitor a dynamic or static group of managed objects, you must
use resource monitors. Process monitors cannot be applied to groups. You can only
apply a process monitor to one managed object at a time.
Events that are generated when a process is being monitored using a resource
monitor have an alert-resolution pairing for the event category. For example, if a
Windows service is stopped, the event that is generated has the category of ″Alert″.
This category causes an orange triangle to be displayed next to the affected
managed object or group in IBM Director Console. When the Windows service is
started, an event is generated with the category of ″Resolution″ and the orange
triangle is cleared from IBM Director Console.
However, events that are generated when a process is being monitored with a
process monitor do not have an alert-resolution pairing for the event category. If a
process is stopped, the event that is generated has the category of ″Alert″ and an
orange triangle is displayed next to the affected managed object in IBM Director
Console. However, when the process is started, the event that is generated also has
the category of ″Alert″ and the orange triangle continues to be displayed in IBM
Director Console even though the problem has been resolved.
See the following table for a quick comparison of resource and process monitor
features.
Table 4. Comparison of resource monitor and process monitor features
Resource monitors Process monitors
Can be applied to groups Cannot be applied to groups
Can be used only on systems running Can be used on systems running all
Windows operating systems supported by IBM
Director
Clear the orange triangle after the problem Continue to display the orange triangle in
has been resolved IBM Director Console after the problem has
been resolved
External application tasks are defined for IBM Director by a set of resources that
you can create manually or by using the External Application Launch wizard.
Chapter 1. Overview 27
These resources specify the application to be started, the task title in IBM Director
Console, the location of the task in IBM Director Console, the icons associated with
the task, and way the task is started in IBM Director Console. External application
tasks can be targeted, untargeted, or both. External Application Launch tasks have
resources for each supported language defined in the command-task file, a process
simplified by the External Application Launch wizard.
Important: You must install IBM Director in the default location to use External
Application Launch or the External Application Launch Wizard.
Command-task files
Command-task files are Java property files that are used by the IBM Director
command-task service to configure tasks to run in the IBM Director environment.
New command-task files can be constructed and existing command-task files can
be modified using the External Application Launch Wizard or manually using an
editor.
You can create and modify External Application Launch resource bundles using an
editor or the External Application Launch Wizard. It is your responsibility to
ensure the accuracy of Java resource bundles that you create manually using an
editor.
External Application Launch Wizard always creates at least two properties files for
resources (one default file and one English file). For example, if you created a
command-task file with the title keyword “apple”, the result would be resource
bundles named appleResources.properties and appleResources_en.properties. If
you provide additional non-English titles, additional resource bundles are created
for each locale that you defined. For example, if you provided French and Spanish
titles as well, appleResources_fr.properties and appleResources_es.properties files
would also be created. These resource-bundle files reside in one of the following
directories, depending on your operating system:
Table 5. Location of resource-bundle files by operating system
Windows installation \Program Files\IBM\Director\classes\
CmdTask\resources
Linux installation /opt/IBM/director/classes/CmdTask/
resources
where resources represents the directory that contains resource files for a specific
Note: Although IBM Director ensures that IBM Director data is valid, you are
responsible for ensuring that data in the resource bundles is valid for the intended
purpose.
Task icons
Command-task files can reference Graphics Interchange Format (GIF) files that are
used as task icons. These files can be existing IBM Director task icon files specified
with a path name relative to the classes directory under the IBM Director
installation, or they can be any nonanimated GIF files specified in the
command-task file with a fully qualified path and file name. Task icon files can be
specified for small (16-pixel) and large (32-pixel) icons. If IBM Director cannot find
the icon file specified in the command-task file, External Application Launch
replaces the custom icon with a question mark (?). If an icon file is not specified in
the command-task file, a default icon is used.
The customized image files reside in one of the following directories, depending
on the operating system on which IBM Director is installed:
Table 6. Location of customized image files by operating system
Windows installation \Program Files\IBM\Director\classes\
CmdTask\resources
Linux installation /opt/IBM/director/classes/CmdTask/
resources
where resources represents the directory that contains resource files for a specific
external-application task.
Tip: Icons look best on the IBM Director Console when you create them using a
transparent background.
Chapter 1. Overview 29
configured, the IP address, MAC address, and computer name are passed
to the application by way of environment variables.
Untargeted tasks
Untargeted tasks are tasks for which no managed object is specified when
the task is started. Untargeted tasks are started in one of two ways:
v By double-clicking the task in the Tasks pane
v By selecting the task from the Tasks menu
Untargeted tasks perform actions that are not specific to a targeted
managed object, perform actions that apply to all managed objects, or
provide their own interface for selecting managed objects on which to
perform actions. Examples of targeted tasks are Scheduler, Rack Manager,
and Hardware Status.
Tasks that are both targeted and untargeted
A task may be both a targeted task and an untargeted task, with behavior
reflecting the manner in which the task is started. The Inventory task is an
example of such a task: if started from a managed object’s pop-up menu or
by dragging it to a managed object, it displays information for that object
only; if started from the Tasks menu, it displays information for all
managed objects.
Managed-object groups
IBM Director allows you to organize logical sets of managed objects into groups.
There are several types of groups that you can create in IBM Director:
Static groups
Static groups contain a specified list of managed objects. IBM Director
Server does not automatically update the contents of a static group. The
members of a static group are fixed unless you change them using IBM
Director Console, the dircli chgp command, or an event action plan. You
can also copy the members of any dynamic group to a static group.
For example, a static group might contain all the managed objects that are
physically located in a particular server room.
Group categories
Group categories contain a specified list of managed-object groups. In
other words, a group category is a kind of static group which has only
other groups as members. If you perform a task on a group category, the
task is performed on all the managed objects that are members of the
groups in the group category.
For example, if static groups are defined based on the room where a
managed object is located, a group category might include all the static
groups for rooms in a particular building.
Note: You can delete some of the default dynamic groups created by IBM
Director. If you want to use these groups after you have deleted them, you
must create them again. See “Creating a criteria-based dynamic group.”
Task-based groups
Task-based groups are dynamic groups that are based on the IBM Director
tasks that can be performed on the managed objects.
For example, a task-based group might contain all the managed objects for
which both the Hardware Status and Remote Session tasks can be
performed.
When you start IBM Director Console for the first time, the default groups are
displayed. Some of these default groups are described below.
All Groups
The All Groups group contains all managed-object groups in IBM Director.
All Managed Objects
The All Managed Objects group contains all discovered managed objects
in IBM Director.
Hardware Status groups
The Hardware Status Critical, Hardware Status Information, and
Hardware Status Warning groups are dynamic groups that contain
managed objects for which there are unresolved hardware status events.
The default groups that are relevant to scalable objects are shown in table below.
Table 7. IBM Director groups that are used with scalable objects
Group name Managed objects
Logical Platforms All logical-platform objects, which includes
all scalable partitions.
Physical Platforms All physical-platform objects, which includes
all scalable nodes.
Platforms All logical platforms and physical platforms.
Chapter 1. Overview 31
Table 7. IBM Director groups that are used with scalable objects (continued)
Group name Managed objects
Platforms and Platform Members All logical and physical platforms and any
managed systems that result from these
platforms.
Scalable Partitions Only scalable partitions.
Scalable Systems Only scalable systems.
Scalable Systems and Members All scalable systems and all members of
those scalable systems. Members of a
scalable system include its scalable
partitions, its scalable nodes, and any remote
I/O enclosures attached to its scalable
nodes. This group also includes managed
systems that result from its scalable
partitions.
This table lists the groups that support storage managed objects.
High availability
In IBM Director, high availability configuration allows IBM Director Server
operations to be performed by a redundant IBM Director Server instance in the
event of a failure on a management server, when IBM Director is run in
conjunction with a high-availability system such as IBM Tivoli System Automation
for Multiplatforms or SteelEye’s LifeKeeper.
Managed objects
A managed object is a system or device that is managed by IBM Director.
Note: To delete a physical platform from IBM Director Console, you also
must delete any associated managed system or systems.
Scalable objects
Systems with multinode configurations, including scalable systems, nodes,
and partitions.
BladeCenter chassis
A BladeCenter unit that acts as an enclosure. This 7-U modular chassis can
Chapter 1. Overview 33
contain up to 14 blade servers. It enables the individual blade servers to
share resources, such as the management, switch, power, and blower
modules.
Windows cluster
A collection of Microsoft Windows systems that work together to provide a
single, unified computing capability.
Racks Racks that are created by Rack Manager.
Static partitions
A view-only scalable partition.
Managed system
A managed system is a computer, such as a server, desktop, workstation, or mobile
computer, that can be managed by IBM Director. There are three levels that are
used to categorize managed systems.
A Level-0 managed system is a managed system that does not have IBM Director
Agent or the Common Information Model (CIM) instrumentation installed, but
does have the minimum set of protocols that are required for that system to be
managed by IBM Director. To manage a system using IBM Director, that system, at
a minimum, must support the Secure Shell (SSH) or Distributed Component Object
Model (DCOM) protocol.
Level 0: Agentless Systems is supported on systems that are running the following
operating systems.
v AIX (limited set of tasks, described below)
v i5/OS (limited set of tasks, described below)
v Linux
v Windows
Locked Unlocked
v System Name All of the attributes returned by a locked
v TCP/IP Addresses system, plus the following:
v System State v Computer Name
v MAC Address v Architecture
v System Presence Check Setting v OS Major Version
v OS Minor Version
v Access Denied
v Operating System
v Unique System ID
v System UUID (System x)
v Machine Type
v Model Number
v Serial Number
After you discover and unlock a Level-0 managed system, you can perform the
following tasks on that system:
Level-0 managed systems running AIX or i5/OS
v Install Level 2: IBM Director Agent by using software distribution
v Run command-line programs (if SSH is present)
v System information
Level-0 managed systems running Linux or Windows
v Collect inventory that is available from the operating system
v Install Level 1: IBM Director Core Services or Level 2: IBM Director
Agent by using software distribution
v Restart the operating system (Linux only)
v Run command-line programs (if SSH is present)
v Power Management
v Server Configuration Manager
v MPA CLI
v MPA Web interface
v System information
A Level-1 managed system is any system that has Level 1: IBM Director Core
Services installed but does not have Level 2: IBM Director Agent installed. Level-1
managed systems can be IBM servers, desktop computers, workstations, and
mobile computers.
Chapter 1. Overview 35
v 5.20 and later:
v Power Management
v Server Configuration Manager
v MPA CLI
v MPA Web interface
v System information
Level 1: IBM Director Core Services is supported on systems that are running the
following operating systems. For a detailed list of supported operating-system
versions, refer to the IBM Director Planning, Installation and Configuration Guide.
v Linux (System x, System p, and System z)
v Windows
A Level-2 managed systems is any system that has Level 2: IBM Director Agent
installed. Level-2 managed systems can be IBM or non-IBM servers, desktop
computers, workstations, and mobile computers.
Level 2: IBM Director Agent is supported on systems that are running the
following operating systems. For a detailed list of supported operating-system
versions, refer to the IBM Director Planning, Installation and Configuration Guide.
v AIX
v i5/OS
v Linux (System x, System p, and System z)
v NetWare
v Windows
Mass configuration
Using mass-configuration profiles, you can quickly configure a group of managed
objects.
The mass-configuration profiles are saved in the Tasks menu (and in the Tasks
pane) under the task with which they are associated. After you create a
mass-configuration profile, you then can apply that profile to a managed object or
a group.
Note: To enable IBM Director to monitor the cluster, each system in the cluster
must have IBM Director Agent installed.
Using clusters, you monitor the status of a logical collection of resources (resource
groups) that can be distributed across nodes in a network or across network
boundaries. For example, a Web server resource group might consist of individual
resources, such as an IP address, a physical disk containing the server files, and an
application that defines how the server is started. One purpose of this resource
group might be to ensure and enable redundancy of the Web server such that the
resources could be transferred from one system to another if the Web server goes
down.
The following possible states of a cluster are defined and monitored through the
IBM Director agents installed on each managed system in the cluster and reported
to the IBM Director. These states apply to the cluster objects in the IBM Director
Console, not in the Microsoft Cluster Browser. The Microsoft Cluster Browser does
not display the state of a cluster as a whole; it displays the states of individual
cluster resources, such as resource groups, nodes, networks, and network
interfaces.
Normal online
One or more nodes are online and all resource groups are online and
available.
Error online
One or more nodes are online and one or more resource groups are
unavailable.
Error offline
All nodes in the cluster are online but one or more resources or resource
groups are unavailable.
Normal offline
No systems are online.
You can use the Resource Monitors task to define thresholds and use the Event
Action Plans task to create event action plans for these and other cluster states,
according to the needs of your organization.
Chapter 1. Overview 37
Such conventions provide the following advantages:
v Computer resources that you are managing with IBM Director are easy to locate
v The physical locations of computer resources that you are managing are easy to
locate, such as within a datacenter that has the aisles numbered.
v The purpose of a system is described, eliminating the need to inspect the
system.
v Systems that are owned by different organizations, but share network space or
physical space, are easily identified.
To use a different naming convention, you must change this PPMO default naming
template to match your standardized naming convention. Auto Rename is an IBM
Director function that system administrators can use to apply a desired naming
convention to PPMOs. You can use the Auto Rename function in IBM Director
Console to easily rename PPMOs.
The command sender always expects to get a command response from the receiver.
However, a response is not always received. A command might not reach its
destination because the receiver is offline or there are network problems. Because
of these concerns, commands include a timeout value. The command-timeout value
indicates the length of time that the sender is willing to wait for a response to this
command. If the command-timeout value elapses before the response is received
from the destination, the sender is notified that the command timed out.
Consider that a command that is routed within a local system is processed very
quickly, but a command that collects inventory from a remote managed system
takes longer to process. Commands might time out because the network or the
management server is slower than usual. Although increasing the
command-timeout value might eliminate timeouts, it cannot correct a slow
network or system. When a user requests access to a Level-2 managed system, the
user expects a response within a short time, probably less than 15 seconds. A
command-timeout value of five minutes might guarantee that the command does
not timeout, but it is much longer than most users are willing to wait for a
response. Carefully weigh the advantage of ignoring timeout failures when the
network is slow against the disadvantage of waiting longer for all commands to
complete.
For example, suppose that the command-timeout value for a specific command is
60 seconds. The network-timeout setting is 45 seconds. The actual timeout is
calculated as 60 seconds X (45 seconds / 15 seconds) = 180 seconds (3 minutes).
You should adjust the network-timeout setting only in the following situations:
v You are receiving messages indicating that tasks or other actions are timing out.
v Tasks or actions are taking a long time and intermittently failing. Because the
actual time for a command varies, commands sometimes time out and
sometimes complete successfully, resulting in intermittent task failure.
Note: The default network-timeout is set on the management server, but because
commands are routed from IBM Director Console through IBM Director Server to
IBM Director Agent, the setting can seem to affect management consoles and
managed objects as well.
Typically, a command timeout is a problem only for commands that are sent from
the management server to Level-2 managed systems. These commands usually
time out because of network latency or bandwidth issues. Also, high
microprocessor (CPU) use on a Level-2 managed system can slow command
processing by IBM Director Agent.
Notes:
1. The network-timeout setting does not affect discovery because discovery does
not use commands.
2. Increasing the network-timeout setting can affect the user experience. Users
might wait longer before getting a response to certain management console
actions.
Scalable objects
Scalable objects are IBM Director managed objects that are used with multinode
configurations of scalable IBM System x and xSeries® servers.
Scalable objects in IBM Director for scalable IBM System x and xSeries servers
include:
v Scalable nodes
v Scalable partitions
v Scalable systems
Chapter 1. Overview 39
nodes and the scalable partitions that were created from those scalable nodes.
These IBM Director managed objects are referred to as scalable objects throughout
this documentation.
Note: IBM Director performs only discovery and power operations for scalable
systems and scalable partitions that have been previously configured on scalable
IBM System x and xSeries servers. It does not create or configure scalable systems
or scalable partitions.
Scalable nodes
A scalable node is a server that has one or more SMP Expansion Modules. When
IBM Director discovers such a server, it creates a physical-platform managed
object. It also assigns attributes that record the number of SMP Expansion
Modules, SMP Expansion Ports, and RXE Expansion Ports on the physical chassis.
In IBM Director Console, scalable nodes are identified with the same icon that is
used for all physical platforms. To determine whether a physical platform has the
additional attributes of a scalable node, in the Group Contents pane, double-click
the icon for the physical platform. The Display System Attributes window opens
and the attributes for SMP Expansion Modules and RXE Expansion Ports are in the
list that is displayed.
Scalable partitions
A scalable partition contains one or more scalable nodes. Regardless of the number
of scalable nodes it contains, a scalable partition can run a single image of an
operating system.
You can view the state of a scalable partition from IBM Director Console. To do so,
right-click the managed object for a scalable partition; then, click Open to display
general attributes for that scalable partition. The scalable partition state is
displayed under the general attribute State.
Scalable systems
A scalable system is an IBM Director managed object that consists of scalable
nodes and the scalable partitions that were created from the scalable nodes in the
scalable system.
The default groups that are relevant to scalable objects are shown in table below.
Table 8. IBM Director groups that are used with scalable objects
Group name Managed objects
Logical Platforms All logical-platform objects, which includes
all scalable partitions.
Physical Platforms All physical-platform objects, which includes
all scalable nodes.
Platforms All logical platforms and physical platforms.
Platforms and Platform Members All logical and physical platforms and any
managed systems that result from these
platforms.
Scalable Partitions Only scalable partitions.
Scalable Systems Only scalable systems.
Scalable Systems and Members All scalable systems and all members of
those scalable systems. Members of a
scalable system include its scalable
partitions, its scalable nodes, and any remote
I/O enclosures attached to its scalable
nodes. This group also includes managed
systems that result from its scalable
partitions.
Power operations that are performed on managed objects that represent scalable
partitions use out-of-band communication. Power operations that are performed on
managed-system objects created from powered-on scalable partitions use in-band
communication to power off the scalable partition.
Restriction: The out-of-band power operations in IBM Director are only for use by
scalable System x servers.
Chapter 1. Overview 41
IBM Director Console identifies all scalable partitions with the same scalable
partition icon whether they are powered on or powered off. However, IBM
Director Console uses additional icons with the scalable-partition icon to indicate
the state of a scalable partition.
IBM Director Console uses the same icon to depict all physical platforms, including
those that are not scalable nodes and those that are not in powered-on scalable
partitions.
This discovery determines whether the NVRAM of the service processor contains a
partition descriptor. If it does, IBM Director uses the partition-descriptor
information to create scalable systems and scalable partitions. The partition
descriptor in NVRAM was stored by the Web management interface for scalable
System x and xSeries servers.
IBM Director also creates the association between scalable systems and scalable
nodes, and between scalable partitions and scalable nodes. The partition descriptor
in NVRAM indicates how many scalable nodes are in a scalable system and how
many scalable nodes are in a scalable partition.
The following conventions are used to name the new scalable objects:
v The scalable system is named “Scalable System xxxx” where xxxx is the last four
characters of the scalable system UUID that is read from NVRAM.
v The scalable partition is named “Scalable Partition xxxx yyyy” where xxxx is the
last four characters of the scalable system UUID that is read from NVRAM and
yyyy is the last four characters of the scalable partition UUID that is read from
NVRAM.
Note: When more than one scalable system UUID ends with the same last four
characters, this naming convention will result in duplicate names. For this reason,
consider renaming automatically created scalable systems to avoid confusion.
When IBM Director Server discovers that IBM Director Agent is running on the
newly started scalable partition, it creates a managed-system object to represent the
active scalable partition. You can use IBM Director to manage this managed system
as you would any other managed system. For example, by using Management
Processor Assistant (MPA), system administrators can configure, monitor, and
manage the service processors in scalable IBM System x and xSeries servers.
Further, IBM Director associates the managed-system object with its scalable
partition object. Use the Scalable Partitions Membership association in IBM
Director Console to view a tree structure of scalable partitions and their
associations with any managed systems.
Security
IBM Director offers several security features, including authentication and
user-administration options that enable system administrators to specify user
privileges, support for Secure Sockets Layer (SSL), and optional encryption of
interprocess communication.
Digital-signature certification:
For Level-1 managed systems, the digital-signature certificate expires after 365
days. You can configure notification and polling settings when the certificate is
about to expire. You can also create an event action plan to notify you of an
expiring certificate.
Chapter 1. Overview 43
The initial security state of IBM Director Agent depends on the underlying
operating system.
Table 9. Initial security state of IBM Director Agent
Operating system Security state
AIX Secured by default during installation of IBM Director Agent.
i5/OS Secured by default during installation of IBM Director Agent.
Linux Secured by default during installation of IBM Director Agent.
NetWare Unsecured by default. Must be secured manually or during
discovery. See “Securing a managed system manually” for more
information.
Windows Can be secured during installation of IBM Director Agent.
If IBM Director Agent is not secured during installation of IBM Director Agent,
you can secure the managed system manually or during discovery.
When the managed system has been secured by a management server, only that
management server, any management servers that had previously established a
trust relationship, and any future management servers that successfully request
access are able to access the managed system.
The public keys are stored in dsaxxxxx.pub files, where xxxxx is a unique identifier.
The private keys held by IBM Director Server are stored in dsaxxxxx.pvt files. For
example, the dsa23ef4.pub file contains the public key corresponding to the private
key stored in the dsa23ef4.pvt file.
On systems running Windows, the secured or unsecured state data is stored in the
secin.ini file, which is generated when you first start IBM Director Server or IBM
Director Agent. On management servers, this file is initialized as secured; on
managed systems, it is initialized as either secured or unsecured, depending on
which options were selected during the installation of IBM Director Agent.
where d is the drive letter of the hard disk on which IBM Director is installed and
IBM Director is installed in the default location.
When you first start IBM Director Server, it randomly generates a matching set of
public and private key files (dsa*.pub and dsa*.pvt files). The secin.ini file is
generated and initialized as secure.
The initial security state of a managed system depends on the following factors:
v Which operating system it is running
v Which features were selected during the installation of IBM Director Agent
Managed systems running NetWare are set to the unsecured state automatically.
For all other managed systems, the initial security state depends on which features
are selected when IBM Director Agent is installed. If either encryption or
agent/server security is selected, the managed system is set automatically to the
secured state.
While a managed system is in the unsecured state, it accepts a public key from
every management server that attempts to access it. Through this process, the
managed system establishes trust relationships with those management servers.
You can use the Request Access window to establish authorization for a
management server to access a secured managed system. In the Request Access
window you must submit the user ID and password of a user with administrator
privileges. After a successful login, the management server deposits credentials on
the managed system that facilitate future access without explicitly requesting
access.
Explicitly requesting access through the IBM Director Console might not be
feasible because, for example:
Chapter 1. Overview 45
v A newly established management server needs to access a large number of
managed systems and you want to automate the process.
v The security policy at your installation does not permit direct logins by users
with administrator privileges.
You can circumvent Request Access by copying the management server’s public
key to the Level-2 managed system.
This topic provides information about public and private keys and how to manage
them.
The public and private key files are binary files, but they contain textual data that
indicates their origin. If a dsa*.pub or dsa*.pvt file is printed using the type
command at a command prompt, the following data is displayed in the first line:
DSAKeytypeString
where:
v Keytype indicates the type of the key. “P” denotes private, and “p” denotes
public.
v String is the name of the management server that generated the key file.
It is very important to back up and protect the dsa*.pvt files. If they are lost, you
cannot regenerate these files.
Because IBM Director uses the operating-system or LDAP user accounts, when a
user logs in to IBM Director Console, he or she uses the user ID and password that
is defined on the operating system or LDAP server.
In order for a user to access IBM Director Server, one of the following conditions
must be true:
v The user is a member of a user group that is authorized for IBM Director Server.
v The user has administrator privileges on the Windows management server or
Windows domain.
v The user is a root user on the AIX, i5/OS, or Linux management server.
When IBM Director Server is installed, two user groups are created on the
operating system of the management server in order to provide default users for
IBM Director. These two groups have administrator and superuser access privileges
to IBM Director tasks and managed objects, as described below:
administrator group
By default, members of the administrator group are authorized to log on to
Note: Root users and Windows administrators have the same authority in
IBM Director as members of the administrator group, whether or not the
user actually belongs to this group.
superuser group
Members of the superuser group are authorized with all privileges and
have access to all IBM Director managed objects and all tasks, including
user and group administration. The authority available to members of the
superuser group cannot be restricted.
The name of the superuser group is different on each supported operating
system.
Additional user groups can also be authorized to access IBM Director. These user
groups can be granted different levels of authority (privileges and access to tasks
and managed objects).
With the exception of users who are members of the administrator group, each
user’s authority in IBM Director is defined by the authority granted to the user
groups to which the user belongs.
LDAP is an open protocol that uses TCP/IP to provide access to directories that
support an X.500 model. For IBM Director user authentication, LDAP has a
number of advantages:
v Many companies already have existing LDAP directories of employees which
can be used for IBM Director user authentication. This saves the time and effort
required to create user accounts on the management server.
Chapter 1. Overview 47
v User access can be immediately modified or terminated on all instances of IBM
Director Server by changing the user’s LDAP group memberships or by
removing the user’s LDAP entry.
v Users only need one ID and password, rather than different accounts for each
management server.
Note: LDAP administrators should note that IBM Director determines group
membership using only the ″members″ attribute of the group entry. IBM Director
ignores other methods of specifying group membership, including attributes (such
as ″memberOf″) on user entries.
Encryption
IBM Director contains a security feature that encrypts all data in interprocess
communications, except transport-layer datagrams used during discovery.
This encryption feature provides automatic key management and enables you to
select an encryption algorithm from the provided libraries:
v IBM Java Cryptography Extension (JCE)
v OpenSSL
JCE provides ciphers for all Java-based platforms, including i5/OS and Linux;
OpenSSL provides ciphers for 32-bit Windows operating systems.
When you install IBM Director Server, you can select one of the following
encryption algorithms:
v Advanced Encryption Standard (AES)
v Data Encryption Standard (DES)
v Triple DES
IBM Director Server automatically generates a key, based on the encryption
algorithm selected. IBM Director Server stores the key in memory and presents it
to IBM Director Server or IBM Director Agent each time IBM Director Server or
IBM Director Agent is started, using the Diffie-Hellman key exchange. This makes
it unnecessary for a key to be stored on each managed system.
The following table outlines how data is transmitted between IBM Director Server
and Level-2 managed systems, depending on whether encryption is enabled.
Table 10. Encryption state and data transmitted between IBM Director Server and IBM
Director Agent
IBM Director Agent IBM Director Agent
(encryption enabled) (encryption disabled)
IBM Director Server Encrypted Unencrypted
(encryption enabled)
IBM Director Server No data transmission Unencrypted
(encryption disabled) possible
Important: If two management servers have discovered each other (and they each
are displayed in each other’s IBM Director Console as managed nodes), and one
management server (server A) has encryption enabled, and the other management
Notes:
v Encryption is not supported on managed systems running NetWare or systems
running 64-bit versions of Windows.
v Neither out-of-band communications nor communication used by Internet tools,
such as Telnet or File Transfer Protocol (FTP), are encrypted.
v Enabling encryption imposes a performance penalty. Encrypting data packets
and exchanging encryption keys has an effect on the speed with which IBM
Director completes management operations. When either the management server
or the managed systems are restarted, keys are regenerated and exchanged.
Consequently, an unsecured managed system might seem to be unmanageable
for a period of time.
Service processors
Hardware-based service processors, also known as management processors, work
with hardware instrumentation and systems management software and are key to
problem notification and resolution and allow you to remotely manage your
system. In an IBM Director environment, service processors send alerts IBM
Director Server when error conditions occur in a specific managed system and are
key in helping you effectively managed your environment.
There are several pathways along which communication between IBM Director
Server and the service processors present in scalable System x and xSeries servers
takes place:
In-band communication
IBM Director Server communicates with IBM Director Agent; IBM Director
Agent uses a device driver to pass data to and from the service processor.
This also is called interprocess communication (IPC).
Over the local area network (LAN)
Data is transmitted between the service processor and IBM Director Server
over the LAN. This is possible if the service processor has an integrated
network interface card (NIC) or access to a NIC shared with the server.
Over the ASM interconnect
Data is passed from the service processor over an ASM interconnect
network to a second service processor. The second service processor serves
as a gateway between IBM Director Server and the first service processor.
Chapter 1. Overview 49
Both of the latter types of communication are known as out-of-band communication,
because they take place independent of an operating system.
Notes:
1. For IBM Director to communicate out-of-band, the following conditions must
be met:
v Service processors must maintain consistent IP addresses. You either must
assign static IP addresses or configure Dynamic Host Configuration Protocol
(DHCP) to maintain consistent IP addresses for the service processors.
v The service processor IP addresses cannot change after IBM Director has
discovered the server.
2. Only one of the following systems management applications can communicate
with a service processor at any given time:
v IBM Director Server
v IBM Management Processor Command-Line Interface (MPCLI)
Whether a service processor can communicate in-band with IBM Director Server
depends on both the type of service processor and the operating system running
on the managed system.
Table 11. In-band communication between service processors and IBM Director Server
Operating system
Primary service processor Linux NetWare Windows
Advanced System Management PCI Adapter Yes Yes Yes
(ASM PCI Adapter)
Advanced System Management processor (ASM Yes Yes Yes
processor)
Integrated system management processor (ISMP) Yes No Yes
IPMI baseboard management processor Yes No Yes
Remote Supervisor Adapter Yes Yes Yes
1
Remote Supervisor Adapter II Yes Yes Yes
1
Novell NetWare 6.5 only
In addition, to enable in-band alerts between IBM Director Server and a managed
system that contains a service processor, both the service-processor device driver
and MPA Agent or System Health Monitoring must be installed on the managed
system. MPA Agent is installed by default with the IBM Director Agent installation
on the Linux operating system.
The following table specifies which IBM Director Agent feature handles in-band
alerting.
Table 12. IBM Director Agent features that handle in-band alerts
Operating system running on managed system
Type of service processor Linux NetWare Windows
ASM PCI Adapter System Health Not applicable System Health
Monitoring Monitoring
ASM processor System Health Not applicable System Health
Monitoring Monitoring
ISMP None or System Not applicable System Health
Health Monitoring
Monitoring1
IPMI baseboard management System Health Not applicable System Health
controller Monitoring Monitoring
Remote Supervisor Adapter System Health Not applicable System Health
Monitoring2 Monitoring
Remote Supervisor Adapter II System Health MPA Agent System Health
Monitoring Monitoring
1
If System Health Monitoring is supported on the server.
See the IBM Director Hardware and Software Support Guide document for a list of
servers on which System Health Monitoring is supported when the server is
running Linux. This PDF file is updated every six to eight weeks. You can
download it from the IBM Director Web site at www.ibm.com/systems/
management/director/.
The following service processors all can serve as gateway service processors:
v ASM PCI Adapter
v ASM processor
v Remote Supervisor Adapter
v Remote Supervisor Adapter II
However, some of these service processors cannot communicate with certain other
service processors. In addition, an ASM processor can communicate with IBM
Director Server only through interprocess communication.
The following table details the possible gateway service processors and the types
of service processors located on an ASM interconnect network with which they can
Chapter 1. Overview 51
communicate.
Table 13. Gateway service processors and communication with service processors on an
ASM interconnect network
Service processor on an ASM interconnect
IPMI
Gateway ASM baseboard Remote Remote
service ASM PCI management Supervisor Supervisor
processor processor adapter ISMP controller Adapter Adapter II
ASM PCI Yes Yes No Not No No
adapter applicable
ASM Yes Yes No Not No No
processor applicable
Remote Yes Yes Yes Not Yes Yes
Supervisor applicable
Adapter
Remote Yes Yes Yes Not Yes Yes
Supervisor applicable
Adapter II
To maximize the possibility of IBM Director Server receiving alerts from service
processors located on an ASM interconnect network, consider using a Remote
Supervisor Adapter or a Remote Supervisor Adapter II as a gateway service
processor.
Note: Not all scalable IBM System x and xSeries systems are supported with the
RXE-100 Remote Expansion Enclosure. If you have one of the following servers
attached to an RXE-100 Remote Expansion Enclosure, you cannot use the on-board
Remote Supervisor Adapter as a gateway service processor:
v xSeries 360
v xSeries 365
v xSeries 440
v xSeries 445
v xSeries 455
The Remote Supervisor Adapter is dedicated to managing the RXE-100 Remote
Expansion Enclosure.
The following table contains information about the pathways available for
out-of-band alerting.
Table 14. Out-of-band alerting pathways
Type of service Pathways for out-of-band Possible gateway service
processor alerting processors
ASM PCI adapter v LAN v ASM PCI adapter
v Over an ASM interconnect v Remote Supervisor Adapter
v Remote Supervisor Adapter II
ASM processor v Over an ASM interconnect v ASM PCI adapter
v Remote Supervisor Adapter
v Remote Supervisor Adapter II
ISMP v Over an ASM interconnect v Remote Supervisor Adapter
v Remote Supervisor Adapter II
See the documentation that came with the server for information about how to
configure your service processor and ASM interconnect to ensure that IBM Director
Server receives alerts.
Note: For all service processors, if IBM Director cannot determine the managed
object type for a service processor notification, IBM Director instead will identify
the source of the notification by the IP address of the service processor that sent
the notification to IBM Director Server. An example of this is a managed system
that is configured to send notifications to IBM Director Server, but IBM Director
Server currently doesn’t have a managed object representing that system.
Chapter 1. Overview 53
Service processor type Target managed-object type
BladeCenter management module BladeCenter chassis
RXE-100 Remote Expansion Enclosure RIOEnclosure
System with one of the following service Physical Platform and associated IBM
processors: Director System
v ISMP
v Remote Supervisor Adapter
v Remote Supervisor Adapter II
v Advanced System Management processor
(ASM processor)
v Advanced System Management PCI
adapter (ASM PCI adapter)
System running the MPA Agent with one of Physical Platform and associated IBM
the following service processors: Director System
v ASM processor
v ASM PCI adapter
Note: IBM Director cannot map events that are generated by ASM processors and
ASM PCI adapters to a managed object unless the MPA Agent 4.22 or earlier is
installed. The MPA agent is a feature of the IBM Director Agent, version 4.22 or
earlier, installation.
SNMP devices
IBM Director discovers SNMP devices in your network according to discovery
parameters that you can specify. The process that is used to discover SNMP
devices in your network uses lists of initial IP addresses, SNMPv1 and SNMPv2c
community names, subnet masks, and SNMPv3 profiles.
IBM Director works with SNMPv1, SNMPv2c, and SNMPv3 for all
communications and recognizes Management Information Bases (MIBs) in System
Management Information (SMI) version 1 and version 2 formats.
SNMPv1 and SNMPv2c devices and agents use community names to control their
access. A community name can be any case-sensitive text string. By default, the
community name of an SNMP device is set to public. If specific SNMP devices in
your network have unique community names to restrict access, you can specify the
correct name to gain access to a device. SNMPv3 devices and agents use profiles to
control their access.
The subnet mask enables you to further refine the scope of the discovery process,
limiting the search to certain subnets in the network. The default subnet mask is
set to the subnet of each corresponding IP address.
Using your lists of IP addresses, community names, and subnet masks, a series of
SNMP GET statements are performed against port 161 of the IP address to
determine whether the address is associated with a valid SNMP device. A valid
SNMP device for IBM Director has the following accessible values: sysName,
sysObjectID, sysLocation, sysContact, sysDescr, and sysUpTime. If the object is
determined to be a valid SNMP device, another series of SNMP GET statements
are sent to obtain information in the ipNetToMediaNetAddress table, where
additional IP addresses can be used to discover even more SNMP devices. The
search continues until no new addresses are located. Newly discovered or created
All SNMP traps that are configured with IBM Director Server as the destination are
forwarded as events to the event log. Therefore, you can view an SNMP trap using
the event log on the SNMP managed device that originated the trap. If a trap is
received that corresponds to an SNMP device that has not been discovered, IBM
Director creates the device automatically, if you selected the Auto-add unknown
agents which contact server check box on the SNMP Discovery page in the
Discovery Preferences window.
The MIB file is used to translate raw SNMP dotted-decimal notation into
human-readable text. This is especially useful for SNMP devices, such as network
hubs, switches, printers, and unit power systems (UPSs). MIBs that are placed in
the data\snmp directory on the management server are compiled automatically
when the management server is started or restarted. You can also compile MIBs
manually from the SNMP Browser window.
Software distribution
This topic compares two methods for distributing software.
For Level-2 managed systems, streaming from the management server has one
advantage, however. If a network connection is broken during the transmission,
IBM Director attempts to resume the connection from the point at which the
transmission was interrupted. If the streaming operation can be resumed,
retransmission time is saved.
Because of the ability to resume distribution, you might prefer to stream a software
package from the management server if you have an unreliable or slow network
link.
When you distribute software using redirected distribution, you set up a universal
naming convention (UNC) or an FTP share on a network server. IBM Director
Server streams software packages to the network share, where they are cached.
From the share, they are either streamed to the managed systems or, in the case of
Chapter 1. Overview 55
software that uses the Microsoft Windows Installer (MSI) or InstallShield as the
installation utility, installed directly from the file-distribution server.
IBM Director communicates with the storage devices through their respective
SMI-S providers. Their Service Location Protocol (SLPv2) component enables the
devices to be discovered by IBM Director, which looks for SNIA-defined SLP
service types.
IBM Director obtains information about storage devices through the SMI-S
provider’s Common Information Model Object Manager (CIMOM) component.
Communication occurs using the Distributed Management Task Force (DMTF)
standard for Web Based Enterprise Management (WBEM) as required by SNIA.
The information is organized according to the DMTF standard for the Common
Information Model (CIM) using the profiles defined by SNIA.
SMI-S attributes
SMI-S attributes can include four sets of data values: Default, CIMOM, Base and
Extended.
Default attributes
SMI-S storage managed objects are displayed on the console immediately after
being discovered through SLPv2 as a locked object labeled by the host name (or IP
address if DNS lookup fails). When the storage managed objects object is locked,
only the public data surfaced through SLPv2 is available (such as a locked object
that represents the CIMOM required by the SMI-S standard). Default attributes that
are common to when IBM Director managed objects are displayed. These attributes
include:
System Name
Initially, the primary host name or IP address of the CIMOM. After it is
unlocked, System Name becomes the generated name for the device.
System Factory ID
The managed object factory that creates the objects for the devices.
System State
The state of the object. Initially, the system state is unknown because access
is required to determine the actual state (online, error or offline).
System Presence Check Setting
The polling interval in minutes that is used to check the status.
Chapter 1. Overview 57
Secure/Unsecure supported
A flag that specifies whether securing of the target is supported.
Access Denied
A flag that specifies whether access is denied. The value of this attribute is
true for a locked object. This attribute is no longer displayed after the
object is unlocked.
Encryption Enabled
A flag that specifies whether encryption to the target is enabled.
CIMOM attributes
Until the storage managed object is unlocked, the actual device and its associated
data are unavailable. The storage managed object is unlocked by obtaining access
to represent the CIMOM and the CIM schemas minded for data. The SLP provided
CIMOM attributes includes:
SMI-S Provider Service ID
The unique service ID of the CIMOM. As specified in SMI-S, responses
from different IP addresses with the same Service ID value are assumed to
be the same CIMOM and are collapsed together.
Interop Namespace
The entry namespace in CIM containing the Server profile that has the
CIMOM data and list of registered profiles.
Registered Profiles Supported
The list of profiles this CIMOM claims to support.
SLP Service Names
The full service names for this CIMOM
SMI-S Provider IP Addresses
The list of one or more IP addresses for the CIMOM.
SMI-S Provider IP Port Numbers
The IP ports on this CIMOM.
Base attributes
After access is granted to the storage managed object, the full CIM data can be
obtained. When the full CIM data is obtained, the device representation might
going away successfully because the entity already exists, the object access might
fail, or a security problem might occur. If access is successful, the object becomes a
representation of an actual device. The name changes based on the rules specified
in the Discovery Preferences panel for SMI-S storage devices. The following base
attributes are then displayed:
Registered Profile
The profile that this device represents along with the version (for example,
SNIA:Array 1.0.2).
Namespace
The namespace with the schema details about this particular profile.
Manufacturer ID
The manufacturer of this device.
Type and Model
The type and model string representing this device.
Extended attributes
Any extended attributes that are specified by the attribute extension files are
created. These may vary based on the storage managed object. For example, for an
IBM DS4000™ disk array, the following attributes are displayed:
Subscriptions
Indicates whether a managed object is registered to receive state or alert
indications.
Nickname
A name for the device
Controller IP Addresses
IP addresses for the controllers on the target.
Important: You must install Storage Manager Client on each management console
from which you intend to use it.
Before you can start Storage Manager Client from IBM Director Console on
systems running a Windows operating system, you must set the following
environment variable:
STORAGE_MANAGER
Defines the working directory of Storage Manager Client. The default
directory is c:\Program Files\IBM_FAStT\client.
This table lists the groups that support storage managed objects.
Chapter 1. Overview 59
Update Manager
This topic provides information about the Update Manager task in IBM Director.
Update Manager uses profiles to provide the following core capabilities for
managing System x and IBM BladeCenter firmware and driver updates:
v Acquiring updates automatically at scheduled intervals into the updates library
v Checking the health of system software and reporting system status
v Creating software-distribution packages containing updates from the updates
library
v Deploying updates in Software Distribution packages to remote System x and
IBM BladeCenter models and groups of systems
The following figure illustrates the process of acquiring updates, storing the
updates in the updates library, and deploying necessary updates to systems that
are found to be out-of-date during a system health check.
2
Checks server
1 health
Acquires
updates
Updates
library
UpdateXpress System Packs simplify the downloading and installation of all online
driver and firmware updates for a given system, ensuring that you are always
working with a complete, current set of updates that have been tested together and
bundled by IBM. A single click downloads the entire update bundle, along with a
readme file and a complete change history, if available.
UpdateXpress System Packs are created for a machine type and operating system
combination. Separate UpdateXpress System Packs are provided for Windows and
each of the Linux distributions. For example, there could be several UpdateXpress
System Packs for one particular machine type. There might be one for Windows,
and then one for each Linux distribution. UpdateXpress System Packs are generally
released on a quarterly basis, but if there are critical updates for a system, an
UpdateXpress System Pack will be released as soon as possible.
You can use the IBM Director Update Manager and Scheduler tasks to
automatically download UpdateXpress System Packs for a particular machine type
and operating system combination.
Upward integration
IBM Director Upward Integration Modules (UIMs) and Management Packs enable
third-party workgroup and enterprise systems-management products to interpret
and display data that is provided by Level-1 and Level-2 managed systems. IBM
Director UIMs and Management Packs provide enhancements to the
systems-management products that you can use to collect inventory data, view
IBM Director event notifications, and for some UIMs, distribute IBM Director
managed system software packages.
With the IBM Director UIMs and Management Packs, you can use your
systems-management software to manage systems that have IBM Director Core
Services or IBM Director Agent software installed on them.
Note: The IBM Director UIM, however, provides only Level-1 management
functionality for the managed system.
You can use IBM Director Core Services software to:
v Gather detailed inventory information about your systems, including operating
system, memory, network adapters, and hardware.
v Track your systems with features such as power management, event log, and
system monitor capabilities.
IBM Director Core Services uses some of the latest systems-management standards,
including Common Information Model (CIM), Web-Based Enterprise Management
Chapter 1. Overview 61
(WEBM) and Extensible Markup Language (XML), to provide compatibility with
your existing enterprise-management software.
IBM Director enables you to make the most of your existing enterprise
management structure by upwardly integrating with Tivoli Management
Framework, Tivoli NetView, HP OpenView, Microsoft Systems Management Server,
and Microsoft Operations Manager 2005.
Note: The IBM Director UIM, however, provides only Level-1 management
functionality for the managed system.
When you install IBM Director UIM for HP OpenView NNM, the following
functions are added to the HP OpenView NNM environment:
v Event notification: Provides notification of events that occur on managed
systems on which IBM Director Core Services is installed. These notifications are
delivered using SNMP traps.
v Inventory: Scans inventory using an inventory plug-in that starts a Java
application to collect inventory from IBM Director Core Services, including Asset
ID data, BIOS details, and lease information. Inventory data varies depending on
the type of system (IBM Director System i,System p, and System x).
v Discovery: Provides SNMP-based discovery of managed systems on which IBM
Director Core Services is installed.
Tip: You must configure the SNMP community name of the managed systems.
For System x, this is done using the snmpd.conf file. For System p, you also
need to configure the snmpdv3.conf file.
Note: These functions are supported on IBM Director System i,System p, and
System x platforms.
When you install IBM Director Management Pack for Microsoft Operations
Manager 2005, the following functions are added to the Microsoft Operations
Manager 2005 environment:
v Discovery: Provides discovery of Level-1 and Level-2 managed systems.
v Events: Captures events that occur on Level-1 and Level-2 managed systems.
v Alerts: Sends a notification when certain events occur on Level-1 and Level-2
managed systems.
v State: Changes the state of Level-1 and Level-2 managed systems based on event
criteria.
Note: These functions are supported on System x systems running Windows. They
are not supported on System i, System p, and System z systems.
When you install IBM Director Management Pack for Microsoft System Center
Operations Manager 2007, the following functions are enhanced to work with IBM
System x systems:
v Discovery: Provides discovery of Level-1 and Level-2 managed systems.
v Events: Captures events that occur on Level-1 and Level-2 managed systems.
v Alerts: Sends a notification when certain events occur on Level-1 and Level-2
managed systems.
v State: Changes the state of Level-1 and Level-2 managed systems based on event
criteria.
Note: These functions are supported on System x systems running Windows. They
are not supported on System i, System p, and System z systems.
When you install IBM BladeCenter Chassis Management Pack for Microsoft System
Center Operations Manager 2007, the following functions are added to the
Microsoft System Center Operations Manager environment:
v Discovery: Provides discovery of a BladeCenter chassis and its components.
v Events: Captures events that occur on a BladeCenter chassis and its components.
v Alerts: Sends a notification when certain events occur on a BladeCenter chassis
and its components.
v State: Changes the state of a BladeCenter chassis and its components based on
event criteria.
When you install IBM Director UIM for Microsoft Systems Management Server
2003, the following functions are added to the SMS 2003 environment:
v Event notification: Provides notification of events that occur on managed
systems on which IBM Director Core Services is installed. These notifications are
translated into SMS status messages.
v Collections: Adds an SMS Collection to easily identify all managed systems on
which IBM Director Core Services is installed.
v Inventory: Scans inventory directly from IBM Director Core Services, including
Asset ID data, BIOS details, field-replaceable unit (FRU) numbers, lease
information, and network details.
Chapter 1. Overview 63
Tip: The inventory feature is compatible with only IBM Director Agent or IBM
Director Core Services 5.10 or later.
v Queries: Adds an SMS Query to identify all managed systems on which IBM
Director Core Services is installed.
v Software distribution: Distributes an IBM Director software package and
performs an unattended installation on any system in the Microsoft SMS
environment.
v Wake on LAN®: Remotely turns on managed systems on which IBM Director
Core Services is installed, and are Wake-on-LAN-capable.
Note: These functions are supported on System x platforms that are running
Windows. They are not supported on System i, System p, and System z systems.
When you install IBM Director UIM for Tivoli Management Framework, the
following functions are added to the Tivoli Management Framework environment:
v Event notification: Provides notification of events (such as failing components)
occurring on IBM Director Agent systems and IBM Management Processors,
allowing information technology (IT) personnel to take immediate corrective
action. These notifications can be sent as native Tivoli Enterprise Console events,
SNMP traps, and Windows event-log events.
v Inventory: Collects inventory data directly from managed systems on which
IBM Director Agent is installed using custom MIF files, SQL scripts, and
inventory queries.
v Monitors: Provides hardware status monitors for managed systems on which
IBM Director Agent is installed. This function provides more comprehensive
hardware-monitoring capabilities than the Tivoli Console interface.
v Software distribution: Enables you to build and distribute update packages for
IBM Director Agent software and perform an unattended installation of these
packages on any Tivoli endpoint running Microsoft Windows or Linux.
Note: The IBM Director UIM, however, provides only Level-1 management
functionality for the managed system.
When you install IBM Director UIM for Tivoli NetView, the following functions are
added to the Tivoli NetView environment:
v Event notification: Provides notification of events (such as failing components)
occurring on IBM Director Core Services systems and IBM Management
Note: You must configure the SNMP community name of the managed system.
User interfaces
There are two methods for managing an IBM Director environment: a graphical
user interface, called the IBM Director Console, and a command-line interface
(dircli).
The IBM Director Console allows you to control and monitor managed systems
and devices from an application-based graphical user interface. You can install this
console on a desktop computer, workstation, or mobile compute that exists on the
same network as the management server.
You can use the IBM Director the command-line interfaces to manage and monitor
the managed objects and devices.
You can use the administrative command-line interface interactively using the
dircli or dircmd utilities. This administrative command-line interface is an
important primary interface into IBM Director and may be used either as an
efficient way to accomplish simple tasks directly or as an embeddable and
scriptable framework for achieving higher level goals. For security reasons,
administrative command-line interface runs only on the management server.
Note: The IBM Director dircli supports a subset of the commands that were
available previously through the deprecated dircmd utility.
Chapter 1. Overview 65
66 IBM Director Planning, Installation, and Configuration Guide
Chapter 2. Planning
Before installing or updating IBM Director, review the installation requirements
and plan your installation.
1024 MB
(recommended)
Disk space 40 MB (for Windows) 110 MB (for Windows) 170 MB 325 MB
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
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
Note: IBM Director Server is a Java application. Java applications that are run on
heavily loaded systems might require a separate storage pool. Sections 4.3.2 and
4.3.3 of the IBM Redbooks publication Java and WebSphere® Performance on IBM
iSeries Servers (SG24-6256) provide information about how to create a separate
memory pool.
On System z servers you run IBM Director components not on the entire
mainframe but in a logical partition (LPAR) or on a z/VM guest virtual machine.
Table 20 shows the resource requirements for the LPAR or z/VM guest virtual
machine.
You can find a configuration example for a z/VM guest virtual machine in
“Creating a z/VM guest virtual machine” in the IBM Systems Information Center
at publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/zvmcenter_5.20/
vsd0_t_prepare_map_guest.html. For IBM Director Server and IBM Director Agent
the z/VM guest virtual machine requires special privileges as described in
“Defining a user class for IBM Director Server or IBM Director Agent” in the IBM
Systems Information Center at publib.boulder.ibm.com/infocenter/systems/topic/
zvmcenter_5.20/vsd0_t_prepare_zvm_classdef_framework.html.
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 21. 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 23 lists the ports used by the various IBM Director processes.
v Abbreviations used in Table 23 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 23. Ports used by IBM Director
Category Connection Destination port
IBM Director IBM Director Server ←→ IBM Director Agent 4490 IPX (read)
interprocess 4491 IPX (write)
communication 14247 UDP and TCP1
14248 UDP and TCP
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
Chapter 2. Planning 71
Table 23. Ports used by IBM Director (continued)
Category Connection Destination port
CIM-XML over IBM Director Server → Level-1 or Level-2 15988 TCP (SUSE Linux
HTTP2,3 managed system, or distributions and Red
SMI-S storage Hat Linux for System z
device distributions)
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.
For the most recent list of supported operating systems, see IBM Director Hardware
and Software Support Guide. You can download it from www.ibm.com/systems/
management/director/.
Chapter 2. Planning 73
Operating systems supported by IBM Director 5.20.2
IBM Director 5.20.2 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 is available on the following CDs:
v IBM Director on x86, Version 5.20.2
v IBM Director for AIX, Version 5.20.2 (2 CDs)
v IBM Director for Linux on POWER, Version 5.20.2
v IBM Director for i5/OS, Version 5.20.2
v IBM Director for Linux on System z, Version 5.20.2
v IBM Director Agents & Consoles, Version 5.20.2 (1 of 2)
v IBM Director Agents & Consoles, Version 5.20.2 (2 of 2)
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.
Table 24. Operating systems supported by IBM Director on System x systems, IBM and third-party x86-based
systems
Versions of Linux for 32-bit System x systems, IBM and third-party x86-based systems
IBM
IBM IBM IBM Director
Director Director Director Core
Operating system Console Server Agent Services
Red Hat Enterprise Linux AS and ES, version 3.0 (supports Update 9 and X X X X
earlier)
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 9 and earlier) X X
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 5 and X X X X
earlier)
Red Hat Enterprise Linux WS, version 4.0 (supports Update 5 and earlier) X X
Red Hat Enterprise Linux, version 5.0, Red Hat Enterprise Linux with X X X X
Xen Kernel, version 5.0 (supports Update 1 and earlier)
SUSE Linux Enterprise Server 9 for x86 (supports Service Pack 3 Update X X X X
1 and earlier)
SUSE Linux Enterprise Server 10 for x86, SUSE Linux Enterprise Server X X X X
10 with Xen Kernel (supports Update 1 and earlier)
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.5, 3.0, 3.0.1, X X
and 3.0.2, Console
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.5, 3.0, 3.0.1, X X X X
and 3.0.2, guest operating systems
Note: Supported guest operating systems are those that are supported by
both IBM Director and the specified version of VMware. See the VMware
product documentation for a list of supported operating systems.
VMware GSX Server, versions 3.1 and 3.2, host operating systems X X
Note: Supported host operating systems are those that are supported by
both IBM Director and the specified version of VMware. See the VMware
product documentation for a list of supported operating systems.
Chapter 2. Planning 75
Table 24. Operating systems supported by IBM Director on System x systems, IBM and third-party x86-based
systems (continued)
Versions of Linux for 32-bit System x systems, IBM and third-party x86-based systems
IBM
IBM IBM IBM Director
Director Director Director Core
Operating system Console Server Agent Services
VMware GSX Server, versions 3.1 and 3.2, guest operating systems X X
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.
Table 24. Operating systems supported by IBM Director on System x systems, IBM and third-party x86-based
systems
Versions of Linux for 64-bit System x systems, IBM and third-party x86-based systems
IBM
IBM IBM IBM Director
Director Director Director Core
Operating system Console Server Agent Services
Red Hat Enterprise Linux AS, version 3.0, for Intel Itanium X
Red Hat Enterprise Linux AS and ES, version 3.0, for AMD64 and EM64T X X
(supports Update 9 and earlier)
Red Hat Enterprise Linux WS, version 3.0, for AMD64 and EM64T X X
(supports Update 9 and earlier)
Red Hat Enterprise Linux AS, version 4.0, for Intel Itanium (supports X
Update 5 and earlier)
Red Hat Enterprise Linux AS and ES, version 4.0, for AMD64 and EM64T X X X X
(supports Update 5 and earlier)
Red Hat Enterprise Linux WS, version 4.0, for AMD64 and EM64T X X
(supports Update 5 and earlier)
Red Hat Enterprise Linux, versions 5.0 and 5.1, for AMD64 and EM64T X X X X
SUSE Linux Enterprise Server 9 for AMD64 and EM64T (supports Service X X X X
Pack 3 Update 1 and earlier)
SUSE Linux Enterprise Server 9 for Itanium Processor Family X
SUSE Linux Enterprise Server 10 for AMD64 and EM64T (supports X X X X
Update 1 and earlier)
SUSE Linux Enterprise Server 10 with Xen Kernel (supports Update 1 X X X X
and earlier)
Table 24. Operating systems supported by IBM Director on System x systems, IBM and third-party x86-based
systems
Other operating systems supported by System x servers
IBM
IBM IBM IBM Director
Director Director Director Core
Operating system Console Server Agent Services
Microsoft Virtual Server 2005 (Release 2 required; SP1 supported) X X X X
Table 25. Operating systems supported by IBM Director on System i and System p products
IBM
IBM IBM IBM Director
Director Director Director Core
Operating system Console Server Agent Services
AIX 5L, Version 5.2 (supports TL09 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 TL05 or later) X X X
Note: Level-0 support includes only Discovery, Remote Session and a
limited subset of the Software Distribution task.
AIX 6, Version 6.1 X X X
Note: Level-0 support includes only Discovery, Remote Session and a
limited subset of the Software Distribution task.
i5/OS, Version 5 Release 3 X X
Chapter 2. Planning 77
Table 26. Operating systems supported by IBM Director on System z systems (continued)
IBM
IBM IBM IBM Director
Director Director Director Core
Operating system Console Server Agent Services
Red Hat Enterprise Linux for Mainframe Computing (supports versions X X X X
5.1 and 5.0)
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 (supports Service X X X X
Pack 1 and earlier)
This release of IBM Director Agent and IBM Director Core Services can be
downloaded from the Web or are available on the following CDs:
v IBM Director on x86, Version 5.20 Update 1
v IBM Director for AIX 5L, Version 5.20 Update 1
v IBM Director for Linux on POWER, Version 5.20 Update 1
v IBM Director for Linux on System z, V5.20.1
See the installation instructions for each operating-system environment for
information about the applicable CD or the file that can be downloaded from the
Web.
Chapter 2. Planning 79
Table 27. Operating systems supported by IBM Director on System x systems; IBM and third-party x86-based
systems (continued)
IBM
IBM IBM IBM Director
Director Director Director Core
Operating system Console Server Agent Services
VMware GSX Server, versions 3.1 and 3.2, guest operating systems X X
Note: Supported guest operating systems are those that are supported by
both IBM Director and the specified version of VMware. See the VMware
product documentation for a list of supported operating systems.
VMware GSX Server, versions 3.1 and 3.2, host operating systems X X
Note: Supported host operating systems are those that are supported by
both IBM Director and the specified version of VMware. See the VMware
product documentation for a list of supported operating systems.
Versions of Linux for 64-bit systems:
Red Hat Enterprise Linux AS, version 3.0, for Intel Itanium X
Red Hat Enterprise Linux AS and ES, version 3.0, for AMD64 and EM64T X X
(supports Update 8 and earlier)
Red Hat Enterprise Linux WS, version 3.0, for AMD64 and EM64T X X
(supports Update 8 and earlier)
Red Hat Enterprise Linux AS, version 4.0, for Intel Itanium (supports X
Update 5 and earlier)
Red Hat Enterprise Linux AS and ES, version 4.0, for AMD64 and EM64T X X X X
(supports Update 5 and earlier)
Red Hat Enterprise Linux WS, version 4.0, for AMD64 and EM64T X X
(supports Update 5 and earlier)
SUSE Linux Enterprise Server 9 for AMD64 and EM64T (supports Service X X X X
Pack 3 Update 1 and earlier)
SUSE Linux Enterprise Server 9 for Itanium Processor Family X
SUSE Linux Enterprise Server 10 for AMD64 and EM64T X X X X
SUSE Linux Enterprise Server 10 Service Pack 1 for AMD64 and EM64T X
SUSE Linux Enterprise Server 10 with Xen Kernel X X X X
Other operating systems supported by System x servers:
Microsoft Virtual Server 2005 (Release 2 required; SP1 supported) X X X X
Microsoft Virtual Server (guest operating system) (Release 2 required; SP1 X X
supported)
Note: Supported guest operating systems are those that are supported by
both IBM Director and the specified version of Microsoft. See the
Microsoft product documentation for a list of supported operating
systems.
NetWare, version 6.5 X
Note: Level-0 support is not provided.
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
Chapter 2. Planning 81
See the installation instructions for each operating-system environment for
information about the applicable CD or the file that can be downloaded from the
Web.
Chapter 2. Planning 83
Table 30. Operating systems supported by IBM Director on System x systems; IBM and third-party x86-based
systems (continued)
IBM
IBM IBM IBM Director
Director Director Director Core
Operating system Console Server Agent Services
NetWare, version 6.5 X
Note: Level-0 support is not provided.
Table 31. Operating systems supported by IBM Director on System i and System p products
IBM
IBM IBM IBM Director
Director Director Director Core
Operating system Console Server Agent Services
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
Note: Level-0 support includes only Discovery, Remote Session and a
limited subset of the Software Distribution task.
i5/OS, Version 5 Release 3 X X
i5/OS, Version 5 Release 4
Note: Level-0 support includes only Discovery, Remote Session and a
limited subset of the Software Distribution task.
Red Hat Enterprise Linux AS, versions 4.3 and 4.4, for IBM POWER 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
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
Chapter 2. Planning 85
Task is supported on the following operating systems:
All operating systems
supported by IBM Director
Task Server Linux and Windows only
System Accounts X
Update Manager X
Operating systems
Microsoft
Virtual
Task Windows Linux VMware i5/OS AIX NetWare Server
Asset ID Level 21 Level 21, 2
Level 2 Level 2 Level 2 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 Server Configuration Manager and BladeCenter Configuration
Manager Manager”
Configure Level 21 Level 21, 3
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 Level 2 Levels 1, 2 Levels 1, 2
External See “Operating systems supported by External Application Launch”
Application
Launch
File Transfer Level 2 Level 2 Level 24 Level 2 Level 2 Level 2 Level 2
Hardware See “Operating systems supported by Hardware Status”
Status
Inventory Levels 0, 1, Levels 0, 1, Levels 08, 1, Level 2 Level 27 Level 27 Levels 0, 1, 2
(hardware)5 26, 7 26, 7 2
Inventory Levels 0, 1, Levels 0, 1, Levels 0, 1, 2 Level 2 Level 2 Level 2 Levels 0, 1, 2
(software) 26 26
Microsoft Level 29 No No No No No No
Cluster
Browser
Network Level 21 Level 21, 10
Level 2 Level 2 No No Level 2
Configuration
Power See “Operating systems supported by Power Management”
Management
Process Level 2 Level 2 Level 2 Level 2 Level 2 Level 2 Level 2
Management
Rack Level 212 Level 213, 12
Level 2 No No Level 2 Level 2
Manager11
Remote Level 2 No Level 214 No No No Level 2
Control
Notes:
1. Not supported on Itanium systems.
2. Not supported on System z systems.
3. Not supported on Windows XP Professional x64 Edition.
4. File systems that are displayed for the guest operating system are limited to
file systems within its virtual disk.
5. Inventory data provided can vary among Level-0, Level-1 and Level-2
managed systems.
6. Support on Itanium systems is limited to Level 2.
7. Platform-specific data is not available for hardware inventory.
8. Not supported on VMware ESX Server versions 2.5, 2.5.1, 2.5.2, 2.5.3, or 2.5.4.
9. 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
10. Not supported for Linux on POWER.
11. Supported on System x, xSeries, and Netfinity® systems only.
12. Not supported on 64-bit versions of these operating systems.
13. Supported on System x and Intel-based systems only.
14. Supported on Windows guest operating systems only.
15. Supported for Linux on POWER only.
16. 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.
17. Not supported on guest operating systems.
18. Supported for Linux on POWER and AIX on IBM BladeCenter JS21 only.
Chapter 2. Planning 87
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.
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 33. Hardware Status support for System x servers; IBM and third-party x86-based systems
Operating system Level 1 Level 2
Editions of Windows for 32-bit systems:
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 Editions
Editions of Windows for 64-bit systems:
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
Versions of Linux for 32-bit systems:
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
v SUSE Linux Enterprise Server 10 for x86
VMware ESX Server, versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 3.0, and 3.0.1, Console Yes1,2 Yes1,2
IBM Director 5.20.1 and later: Also, versions 2.5.5 and 3.0.2
Table 34. Hardware Status support for System i platforms and System p servers
Operating system Level 1 Level 2
v AIX 5L, Version 5.2 No Yes, for
v AIX 5L, Version 5.3 5.20
Update 1
and later
Chapter 2. Planning 89
Table 35. Hardware Status support for System z servers
Operating system Level 1 Level 2
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z No No
v SUSE Linux Enterprise Server 9 for IBM System z
v SUSE Linux Enterprise Server 10 for IBM System z
v 5.20 Update 1 and later: Red Hat Enterprise Linux for Mainframe Computing, version
5.0
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.
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 36. Operating systems supported by System x servers; IBM and third-party x86-based systems
Operating system Supported
Editions of Windows for 32-bit 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
Editions of Windows for 64-bit systems:
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
Versions of Linux for 32-bit systems:
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.
Chapter 2. Planning 91
Table 38. Operating systems supported by System z servers
Operating system Supported
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z Yes, Restart
v SUSE Linux Enterprise Server 9 for IBM System z
v SUSE Linux Enterprise Server 10 for IBM System z
v 5.20 Update 1 and later: Red Hat Enterprise Linux for Mainframe Computing, version 5.0
Support for the Power Management task can be provided by System x service
processors that can communicate out of band.
The following service processors in IBM System x servers and blade servers
provide support for the Power Management task using out-of-band
communication:
v Remote Supervisor Adapter
v Remote Supervisor Adapter II
v IPMI baseboard management controller (BMC)
These service processors provide support for the Power On, Restart Now, and
Power Off Now subtasks. Out-of-band communication does not require IBM
Director Core Services or IBM Director Agent. However, you must configure the
service processor to communicate with IBM Director Server. Also, you must
associate a Physical Platform managed object (PPMO) with the service processor in
IBM Director Console.
Support for the Power Management task can be provided by System x servers that
have the Wake on LAN feature enabled. Support is provided only for Level-2
managed systems.
Wake on LAN provides the Power On subtask only. In order to use power
management provided by Wake on LAN technology, the following criteria must be
met:
v The system must include a network interface card (NIC) that can use Wake on
LAN technology.
v The Wake on LAN feature must be enabled.
v IBM Director Server can detect the MAC address of a Level-2 managed system.
v The managed system data is included in the IBM Director inventory tables.
v The managed system is running an operating system that supports the Wake on
LAN feature. See the following table for details.
Table 39. Operating systems supported by System x servers and IBM x86-based systems
Operating system Supported
Editions of Windows for 32-bit systems:
v Windows 2000, Advanced Server, Datacenter, Professional, and Server Editions Yes
v Windows XP Professional Edition
v Windows Server 2003, Datacenter, Enterprise, Standard, and Web Editions
Editions of Windows for 64-bit systems:
v Windows Server 2003, Datacenter, Enterprise, Standard, and Web x64 Editions Yes
v Windows XP Professional x64 Edition
v Windows Server 2003, Datacenter and Enterprise 64-bit Itanium Editions
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
Chapter 2. Planning 93
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 40. 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
Software Distribution Yes3 Yes No
3
Update Manager Yes Yes No
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.
3. Can distribute updates to management module and certain network devices (pass-through modules).
1. Indicates that the Storage product generates events. Events are detected for use in event action plans.
Depending on the database application selected and the operating system of the
management server, the database might be embedded, local, or remote. The three
installation types are described below.
embedded DBMS
The DBMS is installed on the management server as part of the IBM
Director Server installation, and shares the Java Virtual Machine with IBM
Director.
local DBMS
The DBMS is installed on the management server on which IBM Director
Server is installed.
remote DBMS
The DBMS is installed on a different server than the management server,
and accessed remotely by IBM Director Server.
See “Choosing the IBM Director database application” for additional information
about these installation types.
The following table lists the database applications supported by IBM Director
Server 5.20.2 on different management servers and provides information about
whether the database management system (DBMS) is embedded or can be installed
locally or remotely.
Table 42. Database applications supported by IBM Director 5.20.2
Database Supported database versions AIX i5/OS Linux Windows
Apache Derby v V10.2 (included with IBM Embedded — Embedded Embedded
Director Server on AIX,
Linux, and Windows)
IBM DB2 v version 9.1 with Fix Pack 2 Local or — Local or Local or
Universal v version 8.2 with Fix Pack 7 remote remote remote
Database™ v version 8.1 with Fix Pack 14
IBM DB2 Universal Database — Local — —
for System i (part of i5/OS)
Microsoft SQL v Microsoft SQL Server 2005 — — Remote Local or
Server with Service Pack 2 remote
v Microsoft SQL Server 2000
(see with Service Pack 4
“Limitations of
support” on v Microsoft SQL Server 2005 — — — Local
page 97) Express Edition with Service
Pack 2
v Microsoft SQL Server 2000
Desktop Engine (also called
MSDE 2000) with Service
Pack 4
Oracle v version 10g release 2 Local or — Local or Local or
v version 10g release 1 remote remote remote
(Oracle Server) v version 9.2
Chapter 2. Planning 95
Database applications supported by IBM Director Server 5.20.1
The following table lists the database applications supported by IBM Director
Server 5.20.1 on different management servers and provides information about
whether the database management system (DBMS) is embedded or can be installed
locally or remotely.
Table 43. Database applications supported by IBM Director 5.20.1
Database Supported database versions AIX i5/OS Linux Windows
Apache Derby v V10.2 (included with IBM Embedded — Embedded Embedded
Director Server on AIX,
Linux, and Windows)
IBM DB2 v version 9.1 with Fix Pack 2 Local or — Local or Local or
Universal v version 8.2 with Fix Pack 7 remote remote remote
Database v version 8.1 with Fix Pack 14
IBM DB2 Universal Database — Local — —
for System i (part of i5/OS)
Microsoft SQL v Microsoft SQL Server 2005 — — Remote Local or
Server with Service Pack 1 remote
v Microsoft SQL Server 2000
(see with Service Pack 4
“Limitations of
support” on v Microsoft SQL Server 2005 — — — Local
page 97) Express Edition with Service
Pack 1
v Microsoft SQL Server 2000
Desktop Engine (also called
MSDE 2000) with Service
Pack 4
Oracle v version 10g release 2 Local or — Local or Local or
v version 10g release 1 remote remote remote
(Oracle Server) v version 9.2
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 44. Database applications supported by IBM Director 5.20
Database Supported database versions AIX i5/OS Linux Windows
Apache Derby v V10.1 (included with IBM Embedded — Embedded Embedded
Director Server on AIX,
Linux, and Windows)
IBM DB2 v version 8.2 with Fix Pack 5 Local or — Local or Local or
Universal v version 8.1 with Fix Pack 12 remote remote remote
Database
IBM DB2 Universal Database — Local — —
for System i (part of i5/OS)
Limitations of support
Microsoft SQL Server database
Based on information from the Microsoft Web site, the Microsoft SQL
Server 2005 JDBC Driver is officially supported only on the following
operating systems:
v Linux
v Windows 2000 Service Pack 4
v Windows Server 2003 Service Pack 1
v Windows Server 2003 Release 2 (32-Bit x86) (JDBC version 1.1.1501.101
only)
v Windows Server 2003 x64 editions (JDBC version 1.1.1501.101 only)
v Windows XP Service Pack 2
However, it is likely that Microsoft SQL Server might work well on many
other operating systems supporting Java Virtual Machine. This statement is
based on internal testing of IBM Director and on the following information
from the Microsoft Web site:
SQL Server 2005 JDBC Driver 1.1 is JDBC 3.0 compliant and runs on
the Java Runtime Environment (JRE) version 1.4 and later versions. It
has been tested against all major application servers, including BEA
WebLogic, IBM WebSphere, JBoss, and Sun.
Chapter 2. Planning 97
Sun Solaris, Red Hat Linux, and Windows 2000 or later operating
systems are officially supported. http://www.microsoft.com/downloads/
details.aspx?familyid=6d483869-816a-44cb-9787-a866235efc7c#Overview
Microsoft Jet database
The Microsoft Jet database supported in versions of IBM Director prior to
version 5.10 continues to be supported only for upgrades to IBM Director
version 5.20. The Microsoft Jet database is not available as a database
option for new installations. Users with Microsoft Jet databases are
strongly encouraged to use one of the other supported databases for IBM
Director, as support for Microsoft Jet will probably not be offered in future
releases of IBM Director.
IBM Director Server, IBM Director Console, IBM Director Agent, and IBM Director
Core Services are all enabled for the following set of national languages:
v Chinese (simplified)
v Chinese (traditional)
v English
v French
v German
v Japanese
v Korean
v Spanish
Notes:
1. The graphical user interface is translated in all of the supported national
languages.
2. In some national languages, some or all of the help system might not be
translated.
3. Changes to the graphical user interface or the help system in update releases
(for example, 5.20.1 and 5.20.2) are usually available only in English.
4. The most recent information might not be available in the translated versions of
the documentation. For the latest information, see the English version of the
information center. To do so, in your Web browser set your language preference
to English. Then, open or refresh the IBM Director information center.
5. If a discrepancy exists between the translated and the English versions of the
documentation, the English-language version is assumed to have the correct
content.
When determining whether your IBM Director environment will support a national
language, consider the following criteria:
v Your selected operating system must support your selected national language.
v IBM Director must support your selected operating system.
v IBM Director must support your selected national language.
Your network must be up and running before you install IBM Director.
The type of hardware in the environment might determine how you prepare the
physical infrastructure or which features you select when you install IBM Director
Server. Your environment might include one or more of the following types of
hardware:
v Chassis, racks, and remote input/output enclosures, such as IBM BladeCenter
units
v Systems, including servers, desktop computers, workstations, and mobile
computers, such as IBM System i platforms, System p servers, System x servers,
and System z servers
v Storage devices, such as the IBM System Storage DS4000 family of disk storage
devices
v SNMP devices and printers
v ServeRAID controllers or service processors, such as the Remote Supervisor
Adapter II
Review the complete lists of supported hardware in the “Specified operating
environments ” section of the IBM Director documentation.
Identify the systems and devices you will manage with IBM Director.
1. Ensure that all systems and devices are correctly installed and cabled.
2. Record information about those systems and devices in Table 45. You can use
this information to verify that your managed systems and devices have been
discovered, to manually add systems or devices in IBM Director, or to plan
managed-object groups or user roles based on the types or locations of
managed systems and devices.
Table 45. Hardware identification worksheet for IBM Director
System or device Operating system (if
type applicable) Physical location Network address
Chapter 2. Planning 99
Table 45. Hardware identification worksheet for IBM Director (continued)
System or device Operating system (if
type applicable) Physical location Network address
Identify the local and remote subnets in which the systems that you want to
manage with IBM Director are located, and record this in Table 46
Table 46. Local and remote subnets worksheet
Information to gather for discovery Values
Unicast Addresses for Level-0 discovery ___.___.___.___ - ___.___.___.___
___.___.___.___ - ___.___.___.___
IP addresses or IP-address ranges for unicast ___.___.___.___ - ___.___.___.___
discovery of Level-0 (″Agentless″) managed ___.___.___.___ - ___.___.___.___
systems. ___.___.___.___ - ___.___.___.___
___.___.___.___ - ___.___.___.___
___.___.___.___ - ___.___.___.___
___.___.___.___ - ___.___.___.___
___.___.___.___ - ___.___.___.___
___.___.___.___ - ___.___.___.___
Directory agent server for Level-1 discovery
IBM Director must be able to access all the managed objects in the network, and if
you will be using a remote management console, the management console and
management server must have access to each other. In addition, some functions of
IBM Director might require access to the internet.
Consider each of the following issues carefully when planning to install IBM
Director:
v Ports 5988, 5989, and 6988 must be open in order to install IBM Director. Some
firewalls might attempt to block these ports. Allow these ports to be used by the
IBM Director software components.
v The Service Location Protocol (SLP) port (port 427) needs to be open if the
installation environment is behind a firewall.
v For the getfru command to run successfully, the managed system must have
firewall access through a standard FTP port.
v The Remote Control and Software Distribution tasks both use session support to
increase data transmission. Session support within TCP/IP causes data to flow
through a nonreserved port that is different from the one that IBM Director
typically uses for communication. Most firewalls do not allow the data to be
transmitted through this other port.
v Windows firewall can interfere with discovery of managed systems running
Windows XP.
v If a proxy server is required to access the internet from the management server,
ensure that the management server is configured to use the proxy.
v The Update Manager task cannot use Digest or NTLM authentication to access
update packages from IBM. If a proxy server is required, it must be configured
to use Basic authentication.
Review the information in Table 47 and choose the optional components you will
install with IBM Director.
Table 47. IBM Director optional component planning worksheet
Optional component Description Important considerations
h BladeCenter Provides the ability to configure IBM Requires Remote Deployment Manager to
Management BladeCenter chassis, management modules, deploy operating systems to blade servers.
and network devices.
Review the following licensing requirements and determine what licenses you will
need to obtain.
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
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.
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.”
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)
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
In IBM Director 5.20, you can choose to perform an express installation of IBM
Director Server, which simplifies the installation process by automatically selecting
and configuring some options and features that are typically used by small- to
medium-sized businesses.
Note: The express installation option is not available for management servers
running i5/OS.
When you install IBM Director Server, you must make various choices. Use the
“Worksheet: Installing IBM Director Server” on page 386 to record the decisions
that you make as you work through this procedure. Complete the following steps:
1. Determine the optional features that you want to install. You can choose from
the following features:
IBM Director Remote Control Agent
Select this feature if you want to use the Remote Control task to
remotely control the management server.
BladeCenter Management
Select this feature if your environment includes BladeCenter units.
Rack Manager
Select this feature if you want to use the Rack Manager task. You can
use the Rack Manager task to build a realistic, visual representation of
a rack and its components.
2. Determine the location where you want to install IBM Director Server. By
default, IBM Director Server is installed in the following locations.
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 174 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.
Note: If you install IBM Director Server using the express installation option, the
Apache Derby database is installed.
IBM Director Server uses the database to store inventory information in a central
point. This inventory information then can be used for managing your assets.
Before you install IBM Director Server, you should decide which database you
want to use. Some installations will not require a database installed.
On all operating systems except for i5/OS, the Apache Derby database is
embedded with the IBM Director Server installation. For i5/OS, IBM Director
Server can use the IBM DB2 database that is part of the i5/OS operating system.
Use the following steps to determine the appropriate database application for your
installation of IBM Director.
1. Review the advantages and disadvantages of the different database installation
types.
2. Review the supported databases for your management server and the type of
installation that you prefer. Depending on where you are installing IBM
Director Server, you have one or more possible choices for your database. See
“Supported database applications.”
3. Review the additional database selection criteria listed in Table 49 to determine
which database best meets your needs. All supported databases provide the
following functionality in IBM Director:
Using inventory functionality
If you will be performing inventory tasks in IBM Director, a database is
required to store the inventory information.
Using dynamic groups
If you will be using dynamic managed-object groups in IBM Director, a
database is required to store the information.
For the following additional criteria, not all databases provide the desired
function.
Table 49. Additional database selection criteria
Accessing data
with a
third-party tool Large managed
while IBM network (> ~500 Performing
Director is managed capacity
Database running objects) management
no database No Yes No
Depending on the type of managed object and the management tasks you need to
perform, you can choose the best management level for the managed system. IBM
Director has three management levels:
Level 0: ″Agentless″
Managed systems without any IBM Director software installed.
Level 1: IBM Director Core Services
Managed systems with IBM Director Core Services installed.
Level 2: IBM Director Agent
Managed systems with IBM Director Agent installed.
These three management levels have different requirements and provide differing
levels of management functionality in IBM Director.
For each managed object, review the Table 50 and decide what level of
management is required.
Table 50. Management-level selection worksheet1
Level 1:
IBM Level 2:
Director IBM
Level 0: Core Director
Criteria ″Agentless″ Services Agent
Managed object types
IBM systems running AIX X
IBM systems running i5/OS X
IBM systems running Linux X X
IBM systems running Linux and supporting X X X
either the SSH2 or DCOM3 protocol
IBM systems running NetWare X
IBM systems running Windows X X
IBM systems running Windows and supporting X X X
either the SSH or DCOM protocol
Non-IBM systems running Linux and supporting X X X
either the SSH or DCOM protocol
Non-IBM systems running Windows and X X X
supporting either the SSH or DCOM protocol
Other managed objects, including management X
processors supporting SSH, racks, and SNMP
devices
Notes:
1. In this table, ″systems″ include servers, desktop computers, workstations, and
mobile computers.
2. SSH = Secure Shell
3. DCOM = Distributed Component Object Model
4. Event action plans can be applied to Level-0 managed systems; however, most
of the events that can trigger an Event Action Plan are not generated for
Level-0 managed systems.
You can install IBM Director Agent or IBM Director Core Services on Microsoft
Virtual Server guest operating systems. The operating system must be supported
by both IBM Director and Microsoft Virtual Server.
For detailed information about IBM Director Agent and IBM Director Core Services
support for Microsoft Virtual Server and its guest operating systems, see
“Supported operating systems.”
When installing IBM Director Agent or IBM Director Core Services on a Microsoft
Virtual Server guest operating system, use the installation instructions for your
selected operating system.
You can install IBM Director Agent or IBM Director Core Services on:
v VMware Console.
v VMware guest operating systems. The operating system must be supported by
both IBM Director and VMware.
v (VMware GSX only) VMware host operating systems. The operating system
must be supported by both IBM Director and VMware.
For detailed information about IBM Director Agent and IBM Director Core Services
support for VMware and its guest and host operating systems, see “Operating
systems supported by IBM Director 5.20.”
When installing IBM Director Agent or IBM Director Core Services on VMware
Console, use the Linux for xSeries installation instructions. When installing IBM
Director Agent or IBM Director Core Services on a VMware guest operating system
or host operating system, use the installation instructions for your selected
operating system.
The IBM Director tasks and features that are supported on VMware Console and
its guest operating systems varies. For detailed information about which tasks and
features are supported, see “Support of IBM Director tasks across operating
systems” on page 84.
You can install IBM Director Server, IBM Director Console, IBM Director Agent, or
IBM Director Core Services on z/VM guest operating systems. The operating
system must be supported by both IBM Director and z/VM (see “Supported
operating systems”).
The IBM Director tasks and features that are supported on z/VM guest operating
systems vary. For detailed information see “Support of IBM Director tasks across
operating systems”.
You can also install and set up z/VM Center. With z/VM Center you can virtualize
your System z hardware resources into z/VM virtual servers (that is, guest virtual
machines) and to deploy Linux instances on them. You interact with z/VM
through a graphical user interface (GUI) that runs on the IBM Director Console.
For more information about the z/VM operating system, visit the z/VM library at
www.ibm.com/servers/eserver/zseries/zos/bkserv/zvmpdf/.
As with previous versions of IBM Director, the following rules apply to the version
compatibility of IBM Director version 5.20.2 components:
See Table 51 for a complete listing of compatible IBM Director component versions
for each IBM Director Version 5.20.2 component.
Table 51. Compatibility of IBM Director Version 5.20.2 components with other component
versions
Compatible Compatible
Compatible versions of IBM Compatible versions of IBM
IBM Director versions of IBM Director versions of IBM Director Core
Version 5.20.2 Director Server Console Director Agent Services
IBM Director N/A 5.20.2 5.20.2, 5.20.1, 5.20.2, 5.20.1,
Server 5.20.2 5.20, 5.10.3, 5.20, 5.10.3,
5.10.2, 5.10.1, 5.10.2, 5.10.1,
5.10, 4.22, 4.21, 5.10
4.20.2, 4.20, 4.12,
4.11, 4.10.2, 4.10
IBM Director 5.20.2 N/A 5.20.2, 5.20.1, 5.20.2, 5.20.1,
Console 5.20.2 5.20, 5.10.3, 5.20, 5.10.3,
5.10.2, 5.10.1, 5.10.2, 5.10.1,
5.10, 4.22, 4.21, 5.10
4.20.2, 4.20, 4.12,
4.11, 4.10.2, 4.10
IBM Director 5.20.2 and later 5.20.2 and later N/A N/A
Agent 5.20.2
IBM Director 5.20.2 and later 5.20.2 and later N/A N/A
Core Services
5.20.2
IBM Director version 5.20.2 is compatible with the following versions of IBM
Director extensions:
Table 52. Compatibility of IBM Director extensions with IBM Director version 5.20.2
Extension Compatible versions
Capacity Manager 5.20.2
Electronic Service Agent System x DE V5.0, System x DE Linux V5.0
External Application Launch Wizard 5.20
Hardware Management Console 5.20.2
IBM Systems Director Active Energy 3.1, 2.10, 2.00.1, 2.00
Manager
(formerly IBM PowerExecutive)
Remote Deployment Manager 4.40, 4.30.1, 4.30
As with previous versions of IBM Director, the following rules apply to the version
compatibility of IBM Director version 5.20.1 components:
v The versions of IBM Director Server and IBM Director Console must be the
same, even when they are installed on different systems.
v Versions of components that are installed on the same system, such as IBM
Director Console and IBM Director Agent, must be the same.
v The version of IBM Director Server must always be the same or later than the
version of any IBM Director Agent or IBM Director Core Services installed on
managed systems.
See Table 53 for a complete listing of compatible IBM Director component versions
for each IBM Director Version 5.20.1 component.
Table 53. Compatibility of IBM Director Version 5.20.1 components with other component
versions
Compatible Compatible
Compatible versions of IBM Compatible versions of IBM
IBM Director versions of IBM Director versions of IBM Director Core
Version 5.20.1 Director Server Console Director Agent Services
IBM Director N/A 5.20.1 5.20.1, 5.20, 5.20.1, 5.20,
Server 5.20.1 5.10.3, 5.10.2, 5.10.3, 5.10.2,
5.10.1, 5.10, 4.22, 5.10.1, 5.10
4.21, 4.20.2, 4.20,
4.12, 4.11, 4.10.2,
4.10
IBM Director version 5.20.1 is compatible with the following versions of IBM
Director extensions:
Table 54. Compatibility of IBM Director extensions with IBM Director version 5.20.1
Extension Compatible versions
Capacity Manager 5.20
Electronic Service Agent System x DE V5.0, System x DE Linux V5.0
External Application Launch Wizard 5.20
Hardware Management Console 5.20.1
PowerExecutive 2.00.1, 2.00
Remote Deployment Manager 4.30.1, 4.30
ServeRAID Manager 8.40
IBM Server Storage Provisioning Tool 5.20.1
Software Distribution Premium Edition 5.20
System Availability 5.20
IBM Virtualization Manager 1.2(Version 1.2 requires installation of IBM
Director 5.20.1 Service Update 1. For
information about obtaining and installing
IBM Director 5.20.1 Service Update 1, see the
topic “IBM Director release notes and
readme files.”), 1.1
z/VM Center 5.20.1
http://publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/
diricinfo_5.20/fqm0_r_ibm_director_extensions.html
http://publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/
diricinfo_5.20/fqm0_r_release_notes.html
See Table 55 for a complete listing of compatible IBM Director component versions
for each IBM Director Version 5.20 component.
Table 55. Compatibility of IBM Director Version 5.20 components with other component
versions
Compatible Compatible
Compatible versions of IBM Compatible versions of IBM
IBM Director versions of IBM Director versions of IBM Director Core
Version 5.20 Director Server Console Director Agent Services
IBM Director N/A 5.20 5.20, 5.10.3, 5.20, 5.10.3,
Server 5.20 5.10.2, 5.10.1, 5.10.2, 5.10.1,
5.10, 4.22, 4.21, 5.10
4.20.2, 4.20, 4.12,
4.11, 4.10.2, 4.10
IBM Director 5.20 N/A 5.20, 5.10.3, 5.20, 5.10.3,
Console 5.20 5.10.2, 5.10.1, 5.10.2, 5.10.1,
5.10, 4.22, 4.21, 5.10
4.20.2, 4.20, 4.12,
4.11, 4.10.2, 4.10
IBM Director 5.20 and later 5.20 and later N/A N/A
Agent 5.20
IBM Director 5.20 and later 5.20 and later N/A N/A
Core Services
5.20
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
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.
Notes:
– For Ethernet connections, configure either a static IP address or enable the use
of DHCP.
– BladeCenter management modules and the Remote Supervisor Adapter and
Remote Supervisor Adapter II service processors support DHCP; however, the
use of a static IP address is potentially more reliable than using DHCP. A
static address means that the failure or inaccessibility of DNS and/or DHCP
servers will not prevent access to the management module or service
processor.
– If a BladeCenter management module or Remote Supervisor Adapter II is set
to use DHCP but does not receive an address from the DHCP server within
two minutes, the management module or adapter automatically sets its
address as 192.168.70.125.
v Consider how you want event notifications to be sent to the personnel who need
to receive them.
– Using event action plans, you can configure IBM Director to send notification
of particular events or event types via e-mail or mobile phone text message,
or by starting an application on the management server or on a managed
system.
– Alternatively, you can configure management modules and some service
processors to send event notifications directly to personnel or other
management applications besides IBM Director using means such as SNMP
Notes:
– For SNMP, decide which version of SNMP to use (v1 or v3). Enable traps and
the SNMP agent, and configure the IP address. If using SNMPv1, configure
the community name. If using SNMPv3, configure the user profile.
– For e-mail notifications, configure the SMTP server.
– If you enable timeout events (alerts), you also must plan to enable those
timeouts.
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?
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.
Note: After an Express Installation, when you first start IBM Director, the Event
Action Plan wizard starts. You can use this wizard to create an event action plan.
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.
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.
User access to
multiple Suggested
Management management LDAP directory Number of authentication
servers servers exists users method
one n/a yes many LDAP
one n/a yes few user accounts on
management
server
one n/a no n/a user accounts on
management
server
multiple yes yes n/a LDAP
multiple yes no n/a LDAP
2. Decide what kind of user roles to define for IBM Director users.
The user roles you define will provide an organizational framework that will
guide you when creating user groups, delegating management authority in IBM
Director, and creating managed-object groups. User roles can be based on a job
description, on the physical or geographic area of responsibility, or on other
criteria. A user might have several different user roles simultaneously.
Consider what kinds of access users should have in IBM Director.
v Should management authority be allocated in part based on the location of
managed objects? You might want to define user roles based on particular
managed-object sites, whether the site is a room, an office building, or a
country.
v Should management authority be allocated in part based on the kind of
managed object? You might want to define user roles for particular operating
systems or for storage devices.
v Should management authority be allocated in part based on organizational
roles? You might want to define user roles that correspond to sets of
privileges and tasks that can be performed in IBM Director, like software
distribution, inventory collection, and configuring preferences for IBM
Director Server. Depending on the user’s organizational role, the user
probably needs access to only a subset of the available privileges and tasks.
Other criteria can also be used when defining user roles for IBM Director.
Whatever criteria are used to define user roles, remember that a user can have
multiple roles.
Review the “Licensing requirements for IBM Director components and extensions”
topic to determine what licenses you need to purchase.
1. Obtain licenses for IBM Director components and extensions as described in the
following table.
Products Licenses
System i platforms IBM Director Server and IBM Director Agent
licenses are included with the purchase of
System i platforms.
Note: For System x servers, you can purchase your software subscription from
the IBM Director Subscription services Web Page at www.ibm.com/systems/
management/director/subscription/.
IBM Director can be installed before preparing the database, but you will not be
able to use database-dependent features until you configure IBM Director Server to
use a database.
The database administrator should determine an appropriate size for the database
file. If IBM Director will be managing 300 - 500 systems, an initial size of 100 MB is
sufficient. A larger database might be necessary if there will be additional managed
systems or extensive inventory data.
Notes:
v The DB2 client installation is not required for IBM Director version 5.20.
v If needed, download and install the required fix packs from the IBM DB2
database for Linux, UNIX® and Windows product support Web Site at
www.ibm.com/software/data/db2/udb/support/.
v Using the DB2 Run-time or Administration Client media, install the DB2 Java
JDBC Type 4 Universal driver on the management server. Ensure that the
driver is at the correct fix pack level.
v Installation of the DB2 Run-time or Administration Client automatically
configures the CLASSPATH environment variable.
2. Create a user on the DB2 server for the IBM Director database.
3. Create the DB2 database, if it does not already exist. The DB2 database must be
created on the local or remote server before you configure IBM Director to use
it.
Note: The IBM DB2 Information Center has current information about security in
DB2. The IBM DB2 Information Center is at publib.boulder.ibm.com/infocenter/
db2help/index.jsp.
Before installing IBM Director Server, prepare the Microsoft Data Engine 2000 (also
called SQL Server 2000 Desktop Engine or MSDE 2000) database for use with IBM
Director.
Note: In this step, the variable jdbc_path is used to represent the SQL Server
JDBC driver installation path. The default SQL Server JDBC driver installation
paths are as follows:
SQL Server 2000 Driver for JDBC on Windows: C:\Program
Files\Microsoft SQL Server 2000 Driver for JDBC\lib\
SQL Server 2005 Driver for JDBC on Windows: C:\Program
Files\Microsoft SQL Server 2005 JDBC Driver\sqljdbc_1.0\enu\
In any CLASSPATH declaration, replace jdbc_path with the correct path to the
JDBC driver on your system:
a. Click Start → Control Panel → System.
b. Click the Advanced tab, and then click Environment Variables.
c. In the System variables list, select the CLASSPATH variable, and then click
Edit.
Notes:
v CLASSPATH must be defined as a system variable. Defining CLASSPATH
as a user variable will not work.
v If CLASSPATH is not already listed under System variables, click New
and type CLASSPATH in the Variable name field.
d. Add the following to the end of the Variable value field:
;jdbc_path\sqljdbc.jar
e. In the Edit User Variable window, click OK, and then click OK in the
Environment Variables and System Properties windows.
If this installation is for an update to IBM Director, remove any existing
pointers to the following jar files used by previous versions of the JDBC driver:
jdbc_path/msbase.jar
jdbc_path/msutil.jar
jdbc_path/mssqlserver.jar
Chapter 3. Installing 133
5. Create an SQL Server ID for use with IBM Director.
6. Provide the following information to the system administrator who will install
IBM Director Server:
v TCP/IP listener port ID
v Host name of the database server
v Database name
v User ID and password
Before installing IBM Director Server, prepare the Microsoft SQL Server 2005
Express Edition database for use with IBM Director.
Notes:
v The SQL Server security must be set to Mixed Mode as the JDBC Driver
requires SQL Server Authentication for the login.
v Trusted connections are not supportedat this time.
2. If Microsoft SQL Server 2005 Express Edition is already installed: Ensure that
the authentication mode is set to mixed mode. For information about changing
these parameters for an existing installation, see the following SQL Server 2005
Express Edition Books Online article: msdn2.microsoft.com/en-us/library/
ms143705.aspx.
3. Configure TCP/IP connectivity for use with IBM Director Server. By default,
SQL Server Express Edition does not have TCP/IP connectivity enabled after
installation. In addition, the TCP port must be set for use with IBM Director
Server. Complete the following steps:
a. Click Start → All Programs → Microsoft SQL Server 2005 → Configuration
Tools → SQL Server Configuration Manager.
b. In the left pane of the SQL Server Configuration Manager window, expand
SQL Server 2005 Network Configuration and then click Protocols for
SQLEXPRESS.
c. In the right pane of the SQL Server Configuration Manager window,
right-click TCP/IP and click Enable. Click OK to acknowledge the warning
message.
d. Right-click TCP/IP again and click Properties.
e. In the TCP/IP Properties window, click the IP Addresses tab, and then
expand IPALL.
f. Under IPALL, clear the TCP Dynamic Ports field and then type a port
number in the TCP Port field. Usually, the port number should be set to the
default value of 1433.
g. In the TCP/IP Properties window, click OK, and then click OK to
acknowledge the warning message.
Note: In this step, the variable jdbc_path is used to represent the SQL Server
JDBC driver installation path. The default SQL Server JDBC driver installation
paths are as follows:
SQL Server 2000 Driver for JDBC on Windows: C:\Program
Files\Microsoft SQL Server 2000 Driver for JDBC\lib\
SQL Server 2005 Driver for JDBC on Windows: C:\Program
Files\Microsoft SQL Server 2005 JDBC Driver\sqljdbc_1.0\enu\
In any CLASSPATH declaration, replace jdbc_path with the correct path to the
JDBC driver on your system:
a. Click Start → Control Panel → System.
b. Click the Advanced tab, and then click Environment Variables.
c. In the System variables list, select the CLASSPATH variable, and then click
Edit.
Notes:
v CLASSPATH must be defined as a system variable. Defining CLASSPATH
as a user variable will not work.
v If CLASSPATH is not already listed under System variables, click New
and type CLASSPATH in the Variable name field.
d. Add the following to the end of the Variable value field:
;jdbc_path\sqljdbc.jar
e. In the Edit User Variable window, click OK, and then click OK in the
Environment Variables and System Properties windows.
If this installation is for an update to IBM Director, remove any existing
pointers to the following jar files used by previous versions of the JDBC driver:
jdbc_path/msbase.jar
jdbc_path/msutil.jar
jdbc_path/mssqlserver.jar
Before installing IBM Director Server, prepare the Microsoft SQL Server 2000 or
Microsoft SQL Server 2005 database for use with IBM Director. The Microsoft SQL
Server database can be used with IBM Director Server only on management
servers running Windows or Linux.
Notes:
v The SQL Server security must be set to Mixed Mode as the JDBC Driver
requires SQL Server Authentication for the login.
v Trusted connections are not supported at this time.
2. Install the SQL Server JDBC driver on the management server where IBM
Director Server will be installed. This driver will be used for both SQL Server
2000 and SQL Server 2005.
a. 5.20 Update 1 and earlier: Download the SQL Server 2005 JDBC Driver 1.0
(version 1.0.809.102) JDBC driver from msdn2.microsoft.com/en-us/data/
aa937724.aspx.
b. 5.20.2 and later: Download the SQL Server 2005 JDBC Driver 1.1 (version
1.1.1501.101) JDBC driver from msdn2.microsoft.com/en-us/data/
aa937724.aspx.
c. Install the downloaded SQL Server JDBC driver according to the
instructions provided by Microsoft.
3. Set the system variable CLASSPATH to point to the location of the JDBC driver
files.
Note: In this step, the variable jdbc_path is used to represent the SQL Server
JDBC driver installation path. The default SQL Server JDBC driver installation
paths are as follows:
SQL Server 2000 Driver for JDBC on Linux: /opt/msSQLjdbc/lib/
SQL Server 2005 Driver for JDBC on Linux: /home/usr1/
mssqlserver2005jdbc/Driver/sqljdbc_1.0/enu/
SQL Server 2000 Driver for JDBC on Windows: C:\Program
Files\Microsoft SQL Server 2000 Driver for JDBC\lib\
SQL Server 2005 Driver for JDBC on Windows: C:\Program
Files\Microsoft SQL Server 2005 JDBC Driver\sqljdbc_1.0\enu\
In any CLASSPATH declaration, replace jdbc_path with the correct path to the
JDBC driver on your system.
Option Description
To create the Assign the SQL Server ID Create Database permission in the
database during the master database. When the database is created during the IBM
installation of IBM Director installation, the size of the database is set to the default
Director database size specified in the SQL Server configuration options.
To create the Create the SQL Server database and give the following runtime
database now permissions to the SQL Server ID that you created:
v CREATE TABLE
v ALTER TABLE
v DROP TABLE
v CREATE INDEX
v ALTER INDEX
v DROP INDEX
v CREATE VIEW
v ALTER VIEW
v DROP VIEW
6. Provide the following information to the system administrator who will install
IBM Director Server:
v TCP/IP listener port ID
v Host name of the database server
v Database name
v User ID and password
Chapter 3. Installing 137
Preparing the Oracle Server database
Before installing IBM Director Server, prepare the Oracle Server database for use
with IBM Director.
Note: Only the JDBC driver versions listed above are known to work correctly
with IBM Director Server. Use the correct JDBC driver version for the Oracle
Server version you have installed.
Navigate to www.otn.oracle.com/software/content.html and download the
ojdbc14.jar file.
3. Set the system variable CLASSPATH on the management server to point to the
location of the JDBC driver (ojdbc14.jar file).
Note: The Oracle administrator account ID and password are used to perform
the following tasks only:
v Create table spaces and a role (TWG_ROLE)
v Assign a user ID and password
IBM Director does not save the Oracle administrator account ID and password.
Setting these parameters enables the TCP/IP listener. The default value for port
is 5432; change this value if necessary. More information about these
configuration settings can be found in the PostgreSQL online documentation.
3. In order for IBM Director Server to use the PostgreSQL database, you must
enable a password-based client authentication method such as MD5. See the
PostgreSQL documentation for information about the available password-based
client authentication methods and how to make this configuration.
4. Stop and restart PostgreSQL. For the configuration changes to take effect, you
must stop and restart the database.
5. Install the PostgreSQL Java Database Connectivity (JDBC) driver on the
management server where IBM Director Server will be installed. Use the
version of the PostgreSQL JDBC driver that was included as part of the Linux
Note: The PostgreSQL JDBC driver must be compatible with JDK 1.4.
6. Set the system variable CLASSPATH to point to the location of the JDBC driver.
Perform the following steps on the management server:
a. If the PostgreSQL JDBC driver is not named postgresql.jar, create a symbolic
link for the driver. From a command prompt, type the following command
and press Enter:
ln -s driver_path sl_path/postgresql.jar
v driver_path is the fully qualified name of the PostgreSQL JDBC driver.
v sl_path is the path of the symbolic link.
For example:
ln -s /opt/postgres/lib/pg73jdbc3.jar /opt/postgres/lib/postgresql.jar
b. Create a /etc/ibm/director/setup_env file. Add the following statement to
the file:
export CLASSPATH=path/postgreslq.jar
v path is the path of the PostgreSQL JDBC driver, or of the symbolic link, if
one exists.
For example:
export CLASSPATH=/opt/postgres/lib/postgreslq.jar
c. Set the setup_env file attributes to read-execute.
7. Create a PostgreSQL server ID for use with IBM Director.
8. Complete one of the following tasks.
Option Description
To create the Assign the PostgreSQL server ID that you created in step 7 Create
database during the Database permission.
installation of IBM
Director
To create the Create the PostgreSQL database and give the following runtime
database now permissions to the PostgreSQL server ID that you created in step 7:
v CREATE TABLE
v ALTER TABLE
v DROP TABLE
v CREATE INDEX
v ALTER INDEX
v DROP INDEX
v CREATE VIEW
v ALTER VIEW
v DROP VIEW
9. Provide the system administrator who will install IBM Director Server with the
following information:
v Database name (if the PostgreSQL database was created in step 8)
v Host name of the database server
v PostgreSQL IP listener port
v User ID and password, if necessary
Related information
IBM Director must be able to access all the managed objects in the network, and if
you will be using a remote management console, the management console and
management server must have access to each other. In addition, some functions of
IBM Director require access to the internet.
To enable this access, you must configure firewalls and proxies in your network to
allow access by IBM Director components.
1. Configure the firewall on the management server to allow the following ports
to be used by the IBM Director software components:
v 22
v 427
v 5988
v 5989
v 6988
v 15988
v 15989
These ports are the minimum required to install IBM Director. See “Ports used
by IBM Director” for a complete list of the ports which IBM Director
components must be able to use.
2. If a proxy server is required to access the internet from the management
server: Configure the management server to use the proxy when accessing the
internet.
a. Configure the proxy server to use Basic authentication, if it is configured for
Digest or NTLM authentication. The Update Manager task supports only
Basic authentication with the proxy server. If Digest or NTLM
authentication are required, Update Manager will be unable to access
update packages from IBM.
b. Configure the management server to use the proxy server, if a proxy is
required to access the internet. IBM Director requires internet access for
some functions, including Update Manager.
IBM Director can manage service processors that are installed in Level-0 managed
systems, Level-1 managed systems, and Level-2 managed systems.
v For Level-0 (″agentless″) managed systems, you do not need to install drivers to
perform Level-0 management of the service processors.
v For Level-1 or Level-2 managed systems, management of the service processor
uses the Common Information Model (CIM) standard, and requires not only
installation of either IBM Director Core Services or IBM Director Agent on the
managed system, but also installation of a device driver, and possibly a shared
library to access the device driver.
LM78 driver
VMware VMware ESX OpenIPMI driver OpenIPMI driver USB drivers SMBus driver
Server, version
2.5.4, Console or LM78 driver LM78 driver
VMware ESX
Server, version 3.0,
Console
Other VMware OSA IPMI driver MSI IPMI driver Not supported SMBus driver
distributions
IBM Mapping IBM Mapping
Layer Layer
LM78 driver
Note: If required, the MSI IPMI driver and the OSA IPMI driver must be
installed before the IBM Mapping Layer.
IBM Mapping Layer
The IBM Mapping Layer is used to translate IBM Director “generic”
requests into driver-specific requests for different IPMI drivers.
Download this driver from the IBM Support Web Site at
www.ibm.com/support/us.
LM78 driver
The LM78 device driver ensures that IBM Director Server receives
memory and processor Predictive Failure Analysis (PFA) alerts.
See “Installing IBM LM78 and SMBus device drivers for Linux” for
installation instructions.
MSI IPMI driver
The MSI IPMI device driver is used to communicate with the IPMI
baseboard management controller. All other systems should use the
OSA IPMI driver. Download this driver from the IBM Support Web Site
at www.ibm.com/support/us.
OpenIPMI driver
This driver is included with the operating system. No separate
installation is required.
OSA IPMI driver
The OSA IPMI device driver is used to communicate with the IPMI
baseboard management controller. Download this driver from the IBM
Support Web Site at www.ibm.com/support/us.
RSA daemon
The RSA daemon is a Linux-only program that is used to interface with
the RSA card. Download this driver from the IBM Support Web Site at
www.ibm.com/support/us.
RSA library
The RSA library device driver is a Windows-only driver that is used to
interface with the RSA card. It also prevents driver communication
from interfering with IBM Director. Download this driver from the IBM
Support Web Site at www.ibm.com/support/us.
Complete the following preparatory steps before installing IBM Director Server on
AIX.
1. Verify that the following required APAR fixes are installed on your system.
Note: For 5.20 Update 1 and later, installation of these prerequisites is enforced
when installing the sysmgt.pegasus.cimserver fileset at the recommended level.
a. To check if an APAR fix is installed, issue the following command:
instfix -i -k "apar_number"
b. If an APAR fix is not installed, check to see if any of the filesets
incorporating the APAR fix is installed.
c. If an APAR fix is not installed and none of the filesets containing the APAR
fix is installed, use the following procedure to download and install the
required APAR fix:
1) In a web browser, navigate to the following address:
www.ibm.com/eserver/support/fixes/fixcentral
2) Select UNIX servers.
3) Select AIX operating system.
4) Select 5.2 or 5.3.
5) Select Specific fixes.
6) Click Continue, and then follow the instructions on the succeeding
pages to select and download the APARs you need.
2. Ensure that the following AIX Pegasus CIM Server and providers are installed
and functional:
Table 59. AIX Pegasus CIM Server and providers
Version Installation requirements
5.20.2 For 5.20.2, the Pegasus CIM Server, the providers, and OpenSSL are
installed automatically with IBM Director.
5.20.1 v openssl-0.9.7g-1.aix5.1.ppc.rpm or higher (must be installed before
installing the pegasus filesets)
v sysmgt.pegasus.cimserver 2.5.1.21 or higher
v sysmgt.pegasus.osbaseproviders 1.2.6.21 or higher
v sysmgt.pegasus.smisproviders 1.1.0.21 or higher
5.20 v openssl-0.9.7g-1.aix5.1.ppc.rpm or higher (must be installed before
installing the pegasus filesets)
v sysmgt.pegasus.cimserver 2.5.1.0 or higher
v sysmgt.pegasus.osbaseproviders 1.2.6.0 or higher
v sysmgt.pegasus.smisproviders 1.1.0.0 or higher
For more information about installation and requirements for OpenSSL and
Pegasus, see “Install the Pegasus CIM Server and base providers” in the IBM
Systems Information Center at publib.boulder.ibm.com/infocenter/systems/
topic/com.ibm.aix.cim/doc/cim/ciminstall.htm. This information center
contains instructions on how to use the lslpp -l command to verify that the
installed Pegasus filesets are at the required version. It also tells how to verify
what version of OpenSSL is installed. The OpenSSL provider can be obtained
from the following Web site: www14.software.ibm.com/webapp/iwm/web/
preLogin.do?source=aixtbx.
Refer to these documents if you encounter problems running the AIX Pegasus CIM
Server. Both the Guide and README contain instructions on repository recovery if
needed.
Review the following information and complete the necessary steps to prepare
your system for installation:
v Installation of IBM Director Server on i5/OS does not include the IBM Director
Console; however, you can use the command line interface (dircli) to access the
management server.
To provide a GUI to access IBM Director Server that is running on i5/OS, you
must install IBM Director Console on an operating system that supports IBM
Director Console. The IBM Director Console installation images are available on
the IBM Director for i5/OS media, or from the IBM Director support Web site at
www.ibm.com/systems/management/director/.
v If you want to use IBM Director Server on a System i platform to manage a
heterogeneous environment, you must install the applicable IBM Director Agent
or IBM Director Core Services package on each IBM platform that you want to
manage.
You can obtain these versions of IBM Director Agent and IBM Director Core
Services from the IBM Director support Web site at www.ibm.com/systems/
management/director/ or from the IBM Director Agents & Consoles (1 of 2) CD.
v Ensure that you have installed the latest cumulative PTF packages or Group
PTFs on the System i server on which you plan to install IBM Director.
Note: If you are running i5/OS V5R4, ensure that you have installed PTF
SI28290.
v Do not install IBM Director Server over IBM Director Agent. Complete the
following steps to check if IBM Director Agent is installed:
1. From a command prompt, type GO LICPGM and press Enter.
2. Select option 10, Display installed licensed programs, and review the list of
installed programs. If installed, IBM Director Agent is displayed in the list as
one of the following entries (depending on the version):
5722DA1 *BASE IBM DIRECTOR
5733VE1 39 5050 IBM Director Multiplatform Agent, 4.2.0
If IBM Director Agent is installed, you must uninstall it before installing IBM
Director Server. You can use option 12 from the LICPGM menu to uninstall the
product or option.
v If you plan to use Software Distribution to distribute IBM Director Agent to
Level-0 managed systems that are running i5/OS, ensure you have installed and
configured OpenSSH, provided in i5/OS Utilities, *BASE and Option 1 (order
number 5733-SC1) on the managed systems. For more information about
OpenSSH, 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.″
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 Systems with service processors: Install the supporting device drivers and
mapping layers, if they are not already installed. See “Preparing to manage
service processors with IBM Director” for information about these drivers and
mapping layers.
v Make sure that the instance of IBM Director Agent will be fully functional and
able to send alerts to IBM Director Server. For the IBM Director Agent to be fully
functional you might need to install service-processor device drivers or the IBM
LM78 and SMBus device drivers for Linux.
v If you want to use the Remote Session task on the managed system, make sure
that the package that contains telnetd daemon is installed and configured. This
package is usually in the telnet_server_version.i386.RPM package, where version
is the code level of your Linux distribution.
v If you want to use IBM Director Server on System x for heterogeneous server
management, you can install IBM Director Agent or IBM Director Core Services
on the platforms you want to manage. You can obtain IBM Director Agent and
IBM Director Core Services for the supported operating systems from the IBM
Director Web site at www.ibm.com/systems/management/director/ or, if it was
included with your IBM Director distribution, from the IBM Director Agents &
Consoles (1 of 2) CD.
v The IBM Director on x86, V5.20 CD does not include SUSE Linux Enterprise
Server 10 installation packages for IBM Director Server, IBM Director Console,
IBM Director Agent, or IBM Director Core Services. You can download these
installation packages for System x platforms from the IBM Director Web site at:
www.ibm.com/systems/management/director/.
The following table contains information about these device drivers, when they
need to be installed, and what they do.
Table 61. Installing IBM Director Server: IBM LM78 and SMBus device drivers for Linux
Device driver When it is needed What it does
LM78 v The server is one of the following The LM78 device driver
servers: ensures that IBM Director
– IBM eServer 325, machine type 8835 Server receives memory and
– IBM eServer 326, machine type 8848 processor Predictive Failure
– IBM eServer 326m, machine type 7969 Analysis (PFA) alerts.
– IBM eServer 326m, machine type 7992
v The server contains one of the following
service processors:
– Remote Supervisor Adapter
– Remote Supervisor Adapter II
SMBus If the server does not contain one of the The SMBus device driver
following service processors: ensures that the
v IPMI baseboard management controller Management Processor
(BMC) Assistant tasks and System
Health Monitoring function
v Remote Supervisor Adapter
correctly, and is used to
v Remote Supervisor Adapter II communicate with the
integrated systems
management processor
(ISMP) on some servers.
The LM78 and SMBus drivers might also be required in order to provide Level-1
or Level-2 management of service processors as specified in “Preparing to manage
service processors with IBM Director”
To install the LM78 and SMBus device drivers, complete the steps in the following
topics.
Related tasks
“Preparing to manage service processors with IBM Director” on page 141
You can use IBM Director to manage supported service processors that are
installed in a managed system.
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.
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
Issuing this command unloads the device driver and removes all driver-related
files from the server.
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 151.
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
Issuing this command unloads the device driver and removes all driver-related
files from the server.
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 151.
Issuing this command unloads the device driver and removes all driver-related
files from the server.
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
To build either the LM78 or SMBus device driver, complete the following steps:
1. Download the source code for the IBM LM78 and SMBus device drivers from
the IBM Director Downloads Web Page: www.ibm.com/systems/management/
director/downloads.html.
2. Copy the source file (dir5.20_lm78_linux.tar.gz for the LM78 driver or
dir5.20_smbus_linux.tar.gz for the SMBus driver) to the SOURCES directory.
3. From a command prompt, change to the SOURCES directory.
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).
Review the following information and complete the necessary steps to prepare
your system for installation:
v Depending on the component you intend to install, you can use a CD or
installation code downloaded from the Web as your installation code.
System z mainframes, typically, do not have directly attached CD-ROM drives.
If you are using a CD, you might have to mount the CD on a different platform.
Table 62 lists some methods of making the installation code available.
Table 62. 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 AS, version 4.0, for IBM System z: Ensure that the
Compatibility Arch Support package group is installed. The Compatibility Arch
Support package group includes a number of RPMs that are required by IBM
Director.
The Compatibility Arch Support package group can be installed in two ways:
– During installation of Red Hat Enterprise Linux, by selecting the
Compatibility Arch Support package group for installation.
– After installation of Red Hat Enterprise Linux, by using the
system-config-packages tool. Install the system-config-packages tool using the
system-config-packages-1.2.23-1.noarch.rpm file, and then run the
system-config-packages tool to install the Compatibility Arch Support package
group.
In either case, you must have the Red Hat Enterprise Linux installation media
(or an ISO image of the installation media) available to install the Compatibility
Arch Support package group.
For the most current information about IBM Director required and
recommended fixes, go to the IBM Director Web site at www.ibm.com/systems/
management/director/.
v If you want to install IBM Director Server in a z/VM guest virtual machine, you
must assign hardware resources as described in Hardware requirements for IBM
System z servers. For a configuration example see “Creating a z/VM guest
virtual machine” in the IBM Systems Information Center at
publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/zvmcenter_5.20/
vsd0_t_prepare_map_guest.html. Authorize the z/VM guest virtual machine as
described in “Defining a user class for IBM Director Server or IBM Director
Agent” in the IBM Systems Information Center at publib.boulder.ibm.com/
infocenter/systems/topic/zvmcenter_5.20/
vsd0_t_prepare_zvm_classdef_framework.html
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
Review the following information and complete the necessary steps to prepare
your system for installation:
v Make sure that the system meets the hardware and software requirements for
installation described in “Specified operating environments.”
v Ensure that the X Window System package group is installed. IBM Director
Console requires RPMs that are installed with the X Window System package
group.
v Ensure that the required RPM files (or later versions) are installed:
Table 64. Required RPMs for Linux on POWER
Installation scenario Required RPMs
Red Hat Enterprise Linux AS, compat-libstdc++-33-3.2.3-47.3.ppc.rpm
version 4, for IBM POWER diagela-2.1.5-0.ppc64.rpm
librtas-1.2-1.ppc64.rpm
lsvpd-0.15.1-1.ppc.rpm1
powerpc-utils-1.0.0-1.ppc64.rpm
powerpc-utils-papr-1.0.3-1.ppc64.rpm
servicelog-0.2.1-2.ppc64.rpm
Red Hat Enterprise Linux AS, compat-libstdc++-33-3.2.3-47.3.ppc.rpm
version 5.0, for IBM POWER diagela-2.2.1-0.ppc64.rpm
librtas-1.3.1-0.ppc64.rpm
libXmu-1.0.2-5.i386.rpm
libXp-1.0.0-8.i386.rpm
lsvpd-0.15.1-1.ppc.rpm
servicelog-0.2.7-0.ppc64.rpm
SUSE Linux Enterprise Server 9 diagela-2.1.5-0.ppc64.rpm
and 10 for IBM POWER librtas-1.2-1.ppc64.rpm
lsvpd-0.12.7-1.ppc.rpm1
powerpc-utils-1.0.0-1.ppc64.rpm
powerpc-utils-papr-1.0.3-1.ppc64.rpm
servicelog-0.2.1-2.ppc64.rpm
1
If the lsvpd RPM installed on the managed system is at a level higher than
lsvpd-0.15.1-1, some inventory tables might not show inventory data.
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.
Review the following information and complete the necessary steps to prepare
your system for installation:
v Make sure that the system meets the hardware and software requirements for
installation described in “Specified operating environments.”
v Systems with service processors: Install the supporting device drivers and
mapping layers, if they are not already installed. See “Preparing to manage
service processors with IBM Director” for information about these drivers and
mapping layers.
v If you want to use IBM Director Server on System x for heterogeneous server
management, you can install IBM Director Agent or IBM Director Core Services
on the platforms you want to manage. You can obtain IBM Director Agent and
IBM Director Core Services for the supported operating systems from the IBM
Director Web site at www.ibm.com/systems/management/director/ or, if it was
included with your IBM Director distribution, from the IBM Director Agents &
Consoles (1 of 2) CD.
Related tasks
“Preparing Windows XP managed systems” on page 177
Some Windows XP systems might need to be configured before you can be
discover them with IBM Director Server. Make sure each Windows XP system
that you want to manage has been appropriately configured.
“Preparing to manage service processors with IBM Director” on page 141
You can use IBM Director to manage supported service processors that are
installed in a managed system.
Review the following information and complete the necessary steps to prepare
your system for installation:
Review the following information and complete the necessary steps to prepare
your system for installation:
v Make sure that the system meets the hardware and software requirements for
installation described in “Specified operating environments.”
Review the following information and complete the necessary steps to prepare
your system for installation:
v To access IBM Director Console on Linux on System z, you need a fast network
connection to a workstation with a Virtual Network Computing (VNC) client or
an X Window System.
v Depending on the component you intend to install, you can use a CD or
installation code downloaded from the Web as your installation code.
System z mainframes, typically, do not have directly attached CD-ROM drives.
If you are using a CD, you might have to mount the CD on a different platform.
Table 66 lists some methods of making the installation code available.
Table 66. 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.
where /dev/cdrom is the device node for the CD-ROM drive and
iso_file_name is the name of the ISO image.
3. Transfer the ISO image to your Linux on System z, for example, with
FTP.
4. On the Linux on System z system, mount the ISO image through a
loopback device:
mount -o loop iso_file_name /mnt
where iso_file_name is the name of the ISO image and /mnt the mount
point of the file system.
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z: Ensure that the
Compatibility Arch Support package group is installed. The Compatibility Arch
Support package group includes a number of RPMs that are required by IBM
Director.
The Compatibility Arch Support package group can be installed in two ways:
– During installation of Red Hat Enterprise Linux, by selecting the
Compatibility Arch Support package group for installation.
– After installation of Red Hat Enterprise Linux, by using the
system-config-packages tool. Install the system-config-packages tool using the
system-config-packages-1.2.23-1.noarch.rpm file, and then run the
system-config-packages tool to install the Compatibility Arch Support package
group.
In either case, you must have the Red Hat Enterprise Linux installation media
(or an ISO image of the installation media) available to install the Compatibility
Arch Support package group.
v Ensure that the X Window System package group is installed. IBM Director
Console requires RPMs that are installed with the X Window System package
group.
v Ensure that the following RPMs are installed.
Table 67. Required RPMs
Installation scenario 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
for IBM 64-bit compat-libstdc++-295-2.95.3-81.s390.rpm
System z 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
For the most current information about IBM Director required and
recommended fixes, go to the IBM Director Web site at www.ibm.com/systems/
management/director/.
v If you want to install IBM Director Console in a z/VM guest virtual machine,
you must assign hardware resources as described in “Hardware requirements for
IBMSystem z servers” in the IBM Systems Information Center. For a
configuration example see “Creating a z/VM guest virtual machine” in the IBM
Systems Information Center at publib.boulder.ibm.com/infocenter/eserver/
v1r2/topic/zvmcenter_5.20/vsd0_t_prepare_map_guest.html.
Review the following information and complete the necessary steps to prepare
your system for installation:
v Ensure that the X Window System package group is installed. IBM Director
Console requires RPMs that are installed with the X Window System package
group.
v IBM BladeCenter JS20 and JS21 blade servers only: To access IBM Director
Console on an IBM BladeCenter JS20 or JS21 blade server, you need a fast
network connection to a workstation with a Virtual Network Computing (VNC)
client or an X Window System.
Review the following information and complete the necessary steps to prepare
your system for installation:
Make sure that the system meets the hardware and software requirements for
installation described in “Specified operating environments.”
Complete the following preparatory steps before installing IBM Director Agent on
AIX.
1. Verify that the following required APAR fixes are installed on your system.
Note: For 5.20 Update 1 and later, installation of these prerequisites is enforced
when installing the sysmgt.pegasus.cimserver fileset at the recommended level.
a. To check if an APAR fix is installed, issue the following command:
instfix -i -k "apar_number"
b. If an APAR fix is not installed, check to see if any of the filesets
incorporating the APAR fix is installed.
c. If an APAR fix is not installed and none of the filesets containing the APAR
fix is installed, use the following procedure to download and install the
required APAR fix:
1) In a web browser, navigate to the following address:
www.ibm.com/eserver/support/fixes/fixcentral
2) Select UNIX servers.
3) Select AIX operating system.
4) Select 5.2 or 5.3.
5) Select Specific fixes.
For more information about installation and requirements for OpenSSL and
Pegasus, see “Install the Pegasus CIM Server and base providers” in the IBM
Systems Information Center at publib.boulder.ibm.com/infocenter/systems/
topic/com.ibm.aix.cim/doc/cim/ciminstall.htm. This information center
contains instructions on how to use the lslpp -l command to verify that the
installed Pegasus filesets are at the required version. It also tells how to verify
what version of OpenSSL is installed. The OpenSSL provider can be obtained
from the following Web site: www14.software.ibm.com/webapp/iwm/web/
preLogin.do?source=aixtbx.
3. Recommended, not required: Back up the CIM repository. Type the following
two commands, substituting a date string for date and pressing Enter after
each command:
/opt/freeware/cimom/pegasus/bin/cimserver -s
cp -pRh /opt/freeware/cimom/pegasus/etc/repository
/opt/freeware/cimom/pegasus/etc/repository.backup.date
4. In order to discover Level-0 managed systems that are running AIX, ensure you
have installed and configured OpenSSH on the managed systems. For more
information about OpenSSH, go to www.openssh.org.
Refer to these documents if you encounter problems running the AIX Pegasus CIM
Server. Both the Guide and README contain instructions on repository recovery if
needed.
Review the following information and complete the necessary steps to prepare
your system for installation:
v If you want to use IBM Director Server on a System i platform to manage a
heterogeneous environment, you must install the applicable IBM Director Agent
or IBM Director Core Services package on each IBM platform that you want to
manage.
You can obtain these versions of IBM Director Agent and IBM Director Core
Services from the IBM Director support Web site at www.ibm.com/systems/
management/director/ or from the IBM Director Agents & Consoles (1 of 2) CD.
Note: If you are running i5/OS V5R4, ensure that you have installed PTF
SI28290.
v Do not install IBM Director Agent over IBM Director Server. Complete the
following steps to check if IBM Director Server is installed:
1. From a command prompt, type GO LICPGM and press Enter.
2. Select option 10, Display installed licensed programs, and review the list of
installed programs. If installed, IBM Director Server is displayed in the list as
one of the following entries (depending on the version):
5722DR1 *BASE IBM DIRECTOR
5733VE1 30 5050 IBM Director Multiplatform, 4.2.0
If IBM Director Server is installed, you must uninstall it before installing IBM
Director Agent. You can use option 12 from the LICPGM menu to uninstall the
product or option.
v If you plan to use Software Distribution to distribute IBM Director Agent to
Level-0 managed systems that are running i5/OS, ensure you have installed and
configured OpenSSH, provided in i5/OS Utilities, *BASE and Option 1 (order
number 5733-SC1) on the managed systems. For more information about
OpenSSH, 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.
Review the following information and complete the necessary steps to prepare
your system for installation:
1
If the lsvpd RPM installed on the managed system is at a level higher than
lsvpd-0.15.1-1, some inventory tables might not show inventory data.
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.
Review the following information and complete the necessary steps to prepare
your system for installation:
v Make sure that the system meets the hardware and software requirements for
installation described in “Specified operating environments.”
v Make sure that the instance of IBM Director Agent will be fully functional and
able to send alerts to IBM Director Server. For the IBM Director Agent to be fully
functional you might need to install service-processor device drivers or the IBM
LM78 and SMBus device drivers for Linux.
v Ensure that the required RPMs are installed:
Table 71. Required RPMs
Installation scenario Required RPM
Red Hat Enterprise Linux AS and compat-libstdc++-7.3-2.96.122.i386.rpm
ES, version 3.0
v Systems with service processors: Install the supporting device drivers and
mapping layers, if they are not already installed. See “Preparing to manage
service processors with IBM Director” for information about these drivers and
mapping layers.
v If you want to use the Remote Session task on the managed system, make sure
that the package that contains telnetd daemon is installed and configured. This
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 and
IBM Director Core Services for the supported operating systems from the IBM
Director Web site at www.ibm.com/systems/management/director/ or, if it was
included with your IBM Director distribution, from the IBM Director Agents &
Consoles (1 of 2) CD.
Review the following information and complete the necessary steps to prepare
your system for installation:
v Depending on the component you intend to install, you can use a CD or
installation code downloaded from the Web as your installation code.
System z mainframes, typically, do not have directly attached CD-ROM drives.
If you are using a CD, you might have to mount the CD on a different platform.
Table 72 lists some methods of making the installation code available.
Table 72. 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.
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 Endpoints for which you want to support z/VM specific information in the
inventory collections: Make sure that z/VM control program (CP) commands
can be issued from Linux.
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z: Ensure that the
Compatibility Arch Support package group is installed. The Compatibility Arch
Support package group includes a number of RPMs that are required by IBM
Director.
The Compatibility Arch Support package group can be installed in two ways:
– During installation of Red Hat Enterprise Linux, by selecting the
Compatibility Arch Support package group for installation.
– After installation of Red Hat Enterprise Linux, by using the
system-config-packages tool. Install the system-config-packages tool using the
system-config-packages-1.2.23-1.noarch.rpm file, and then run the
system-config-packages tool to install the Compatibility Arch Support package
group.
In either case, you must have the Red Hat Enterprise Linux installation media
(or an ISO image of the installation media) available to install the Compatibility
Arch Support package group.
v Ensure that the following RPMs are installed.
Table 73. Required RPMs
Installation scenario 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
for IBM 64-bit compat-libstdc++-295-2.95.3-81.s390.rpm
System z 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
For the most current information about IBM Director required and
recommended fixes, go to the IBM Director Web site at www.ibm.com/systems/
management/director/.
v If you want to install IBM Director Agent in a z/VM guest virtual machine, you
must assign hardware resources as described in “Hardware requirements for
IBMSystem z servers” in the IBM Systems Information Center. For a
configuration example see “Creating a z/VM guest virtual machine” in the IBM
Systems Information Center at publib.boulder.ibm.com/infocenter/eserver/
v1r2/topic/zvmcenter_5.20/vsd0_t_prepare_map_guest.html. Authorize the
z/VM guest virtual machine as described in “Defining a user class for IBM
Director Server or IBM Director Agent” in the IBM Systems Information Center
at publib.boulder.ibm.com/infocenter/systems/topic/zvmcenter_5.20/
vsd0_t_prepare_zvm_classdef_framework.html
v If you want to use IBM Director Server on System z mainframes to manage a
heterogeneous environment, you must install the applicable IBM Director Agent
or IBM Director Core Services for each IBM platform that you want to manage.
You can obtain these versions of IBM Director Agent or IBM Director Core
Services from the IBM Director Web site at www.ibm.com/systems/
management/director/ or, if it was included with your IBM Director
distribution, from the IBM Director Agents & Consoles, V5.20 (1 of 2) CD.
Review the following information and complete the necessary steps to prepare
your system for installation:
v Make sure that the system meets the hardware and software requirements for
installation described in “Specified operating environments.”
v Systems with service processors: Install the supporting device drivers and
mapping layers, if they are not already installed. See “Preparing to manage
service processors with IBM Director” for information about these drivers and
mapping layers.
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
Review the following information and complete the necessary steps to prepare
your system for installation:
v SUSE Linux Enterprise Server 9 and 10 only: Disable the Service Location
Protocol daemon (SLPD) before installing IBM Director Core Services. IBM
Director Server does not discover Level-1 managed objects that are running
SLPD.
v Ensure that the required RPM files (or later versions) are installed:
Table 74. Required RPMs for Linux on POWER
Installation scenario Required RPMs
Red Hat Enterprise Linux AS, compat-libstdc++-33-3.2.3-47.3.ppc.rpm
version 4, for IBM POWER diagela-2.1.5-0.ppc64.rpm
librtas-1.2-1.ppc64.rpm
lsvpd-0.15.1-1.ppc.rpm1
powerpc-utils-1.0.0-1.ppc64.rpm
powerpc-utils-papr-1.0.3-1.ppc64.rpm
servicelog-0.2.1-2.ppc64.rpm
Red Hat Enterprise Linux AS, compat-libstdc++-33-3.2.3-47.3.ppc.rpm
version 5.0, for IBM POWER diagela-2.2.1-0.ppc64.rpm
librtas-1.3.1-0.ppc64.rpm
libXmu-1.0.2-5.i386.rpm
libXp-1.0.0-8.i386.rpm
lsvpd-0.15.1-1.ppc.rpm
servicelog-0.2.7-0.ppc64.rpm
SUSE Linux Enterprise Server 9 diagela-2.1.5-0.ppc64.rpm
and 10 for IBM POWER librtas-1.2-1.ppc64.rpm
lsvpd-0.12.7-1.ppc.rpm1
powerpc-utils-1.0.0-1.ppc64.rpm
powerpc-utils-papr-1.0.3-1.ppc64.rpm
servicelog-0.2.1-2.ppc64.rpm
1
If the lsvpd RPM installed on the managed system is at a level higher than
lsvpd-0.15.1-1, some inventory tables might not show inventory data.
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.
v Systems with service processors: Install the supporting device drivers and
mapping layers, if they are not already installed. See “Preparing to manage
service processors with IBM Director” for information about these drivers and
mapping layers.
v If you want to use the Remote Session task on the managed system, make sure
that the package that contains telnetd daemon is installed and configured. This
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 and
IBM Director Core Services for the supported operating systems from the IBM
Director Web site at www.ibm.com/systems/management/director/ or, if it was
included with your IBM Director distribution, from the IBM Director Agents &
Consoles (1 of 2) CD.
Review the following information and complete the necessary steps to prepare
your system for installation:
v Depending on the component you intend to install, you can use a CD or
installation code downloaded from the Web as your installation code.
System z mainframes, typically, do not have directly attached CD-ROM drives.
If you are using a CD, you might have to mount the CD on a different platform.
Table 76 on page 172 lists some methods of making the installation code
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 Endpoints for which you want to support z/VM specific information in the
inventory collections: Make sure that z/VM control program (CP) commands
can be issued from Linux.
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z: Ensure that the
Compatibility Arch Support package group is installed. The Compatibility Arch
Support package group includes a number of RPMs that are required by IBM
Director.
The Compatibility Arch Support package group can be installed in two ways:
– During installation of Red Hat Enterprise Linux, by selecting the
Compatibility Arch Support package group for installation.
– After installation of Red Hat Enterprise Linux, by using the
system-config-packages tool. Install the system-config-packages tool using the
system-config-packages-1.2.23-1.noarch.rpm file, and then run the
system-config-packages tool to install the Compatibility Arch Support package
group.
In either case, you must have the Red Hat Enterprise Linux installation media
(or an ISO image of the installation media) available to install the Compatibility
Arch Support package group.
v Ensure that the following RPMs are installed.
Table 77. Required RPMs
Installation scenario Required RPMs
For the most current information about IBM Director required and
recommended fixes, go to the IBM Director Web site at www.ibm.com/systems/
management/director/.
v If you want to install IBM Director Core Services in a z/VM guest virtual
machine, you must assign hardware resources as described in “Hardware
requirements for IBMSystem z servers” in the IBM Systems Information Center.
For a configuration example see “Creating a z/VM guest virtual machine” in the
IBM Systems Information Center at publib.boulder.ibm.com/infocenter/eserver/
v1r2/topic/zvmcenter_5.20/vsd0_t_prepare_map_guest.html.
v If you want to use IBM Director Server on System z mainframes to manage a
heterogeneous environment, you must install the applicable IBM Director Agent
or IBM Director Core Services for each IBM platform that you want to manage.
You can obtain these versions of IBM Director Agent or IBM Director Core
Services from the IBM Director Web site at www.ibm.com/systems/
management/director/ or, if it was included with your IBM Director
distribution, from the IBM Director Agents & Consoles, V5.20 (1 of 2) CD.
Review the following information and complete the necessary steps to prepare
your system for installation:
v Make sure that the system meets the hardware and software requirements for
installation described in “Specified operating environments.”
Figure 4. Example of BladeCenter deployment network when IBM Director Server is not
installed on a blade server
This network configuration ensures that applications running on the blade servers
cannot modify chassis settings, because the blade servers have no connection to
either the management module or the switch module configuration ports.
Note: Only one of the following software applications can communicate with a
BladeCenter management module at any given time:
v Cluster Systems Management (CSM)
v IBM Director Server
v IBM Management Processor Command-Line Interface (MPCLI)
With this configuration, IBM Director Server can communicate through the
Campus LAN to the Management LAN and then onto the management module.
Note: Only one of the following software applications can communicate with a
BladeCenter management module at any given time:
v Cluster Systems Management (CSM)
v IBM Director Server
v IBM Management Processor Command-Line Interface (MPCLI)
Typically, managed systems are first discovered using the Discovery task in IBM
Director Console. Then, IBM Director Core Services or IBM Director Agent is
installed on the managed systems directly from IBM Director Console. The
configuration of some Windows XP managed systems, however, can prevent
discovery by IBM Director Server.
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.
At a command prompt, type net share and press Enter to list the shares
defined on the managed system.
Typically, managed systems are first discovered using the Discovery task in IBM
Director Console. Then, IBM Director Core Services or IBM Director Agent is
installed on the managed systems directly from IBM Director Console. The
configuration of some Windows Vista managed systems, however, can prevent
discovery by IBM Director Server.
To prepare the Windows Vista system for management by IBM Director, perform
the following steps.
1. Configure the user account that IBM Director will use.
To enable these changes, you will need to shut down and restart the managed
system.
2. Enable the Remote Registry service. Complete the following steps:
a. Click Start → Control Panel → System and Maintenance → Administrative
Tools.
Note: Enabling file and printer sharing allows IBM Director to use Remote
Execution and Access (RXA) ports 135, 137, 138, and 139, as well as DCOM
port 445, to communicate with the managed system.
7. Click OK.
To prepare the Windows Vista system for Level-1 management by IBM Director,
perform the following steps.
1. Configure the system for Level-0 management as described in “Preparing to
manage a Level-0 system running Windows Vista.” Configuration for Level-0
management is required in order to access the managed system.
2. Click Start → Control Panel → Network and Internet → Windows Firewall.
3. Click Allow a program through Windows Firewall.
4. Select the Remote administration check box.
5. Specify ports to allow through Windows Firewall. Perform the following steps
for each of the ports listed in Table 78.
a. Click Add port.
b. Specify the Name, Port number, and Protocol in the Add port window.
c. Click OK.
Table 78. Ports required for Level-1 management of Windows Vista systems
Name Port number Protocol
SLP 427 TCP
SLP 427 UDP
CIM 5988 TCP
CIM SSL 5989 TCP
CIM Listener 6988 TCP
To prepare the Windows Vista system for Level-2 management by IBM Director,
perform the following steps.
1. Configure the system for Level-0 management as described in “Preparing to
manage a Level-0 system running Windows Vista.” Configuration for Level-0
management is required in order to access the managed system.
2. Click Start → Control Panel → Network and Internet → Windows Firewall.
3. Click Allow a program through Windows Firewall.
4. Select the Remote administration check box.
5. Specify ports to allow through Windows Firewall. Perform the following steps
for each of the ports listed in Table 79.
a. Click Add port.
b. Specify the Name, Port number, and Protocol in the Add port window.
c. Click OK.
Table 79. Ports required for Level-2 management of Windows Vista systems
Name Port number Protocol
Director IPC 14247 TCP 14247 TCP
Director IPC 14247 UDP 14247 UDP
Director IPC 14248 TCP 14248 TCP
Director IPC 14248 UDP 14248 UDP
6. Click OK.
Complete the following steps to enable the Pegasus and SLP ports on the HMC
device:
1. In the HMC Navigation Area pane, expand the affected HMC and expand
HMC Management. Click HMC Configuration.
2. In the HMC Configuration pane, click Customize Network Settings.
3. In the Network Settings window, click the LAN Adapters tab.
4. Select the LAN Adapter that is connected to your LAN and click Details.
5. In the LAN Adapter Details window, click the Firewall tab. The top pane
displays the firewall ports that you can enable.
6. In the top pane, select Open Pegasus and click Allow Incoming. Open Pegasus
is added to the bottom pane of enabled ports.
7. In the top pane, select SLP and click Allow Incoming. SLP is added to the
bottom pane of enabled ports.
8. Click OK; then click OK again.
Important:
v IBM Director Server and IBM Director Console must be at the same release level.
For example, if you install IBM Director Server, version 5.20.1 on the
management server, you must also install IBM Director Console, version 5.20.1
on any systems that you want to access the management server.
v If IBM Director Console and IBM Director Agent are installed on the same
system, both software components must be at the same release level as IBM
Director Server.
v If you are planning to install and use a database for IBM Director other than the
default database, make sure that you have installed and configured the database
application that you will use with IBM Director before installing IBM Director
Server. On management servers running i5/OS, IBM Director Server uses the
DB2 database. On all other operating systems, the default database is Apache
Derby, but other databases can be used.
v On management servers not running i5/OS, IBM Director Server includes all the
functionality of IBM Director Agent and IBM Director Console. It is not possible
or necessary to separately install either IBM Director Agent or IBM Director
Console on the management server after installing IBM Director Server. Any
IBM Director tasks requiring IBM Director Agent or IBM Director Console will
be performed for systems with IBM Director Server installed.
v On management servers running i5/OS, IBM Director Server includes all the
functionality of IBM Director Agent. It is not possible or necessary to separately
install IBM Director Agent on the management server after installing IBM
Director Server. Any IBM Director tasks requiring IBM Director Agent will be
performed for systems with IBM Director Server installed.
v To use IBM Director Console to access IBM Director Server on a system that is
running i5/OS, IBM Director Console must be installed on a separate non-i5/OS
server.
v Before installing IBM Director Server on a system that has IBM Director Console
or IBM Director Agent installed, you must first uninstall the existing IBM
Director component.
v Before installing IBM Director Server on a system that has IBM Storage
Configuration Manager installed, you must first uninstall IBM Storage
Configuration Manager. After installing IBM Director Server, you can re-install
IBM Storage Configuration Manager.
Important:
v IBM Director Server and IBM Director Console must be at the same release level.
For example, if you install IBM Director Server, version 5.20.1 on the
management server, you must also install IBM Director Console, version 5.20.1
on any systems that you want to access the management server.
v If IBM Director Console and IBM Director Agent are installed on the same
system, both software components must be at the same release level as IBM
Director Server.
v If you are planning to install and use a database for IBM Director other than the
default database, make sure that you have installed and configured the database
application that you will use with IBM Director before installing IBM Director
Server. On management servers not running i5/OS, the default database is
Apache Derby, but other databases can be used.
v On management servers not running i5/OS, IBM Director Server includes all the
functionality of IBM Director Agent and IBM Director Console. It is not possible
or necessary to separately install either IBM Director Agent or IBM Director
Console on the management server after installing IBM Director Server. Any
IBM Director tasks requiring IBM Director Agent or IBM Director Console will
be performed for systems with IBM Director Server installed.
v Before installing IBM Director Server on a system that has IBM Director Console
or IBM Director Agent installed, you must first uninstall the existing IBM
Director component.
v Before installing IBM Director Server on a system that has IBM Storage
Configuration Manager installed, you must first uninstall IBM Storage
Configuration Manager. After installing IBM Director Server, you can re-install
IBM Storage Configuration Manager.
During the installation process, you can configure a database to use with IBM
Director and change security settings.
Optional: If you choose to use a database application other than Apache Derby
with IBM Director, be sure to perform any necessary preparation steps before
configuring IBM Director to use the database. For more information, see
“Preparing the IBM Director database” on page 131.
Depending on the version of IBM Director Server you are installing, you can install
IBM Director Server on AIX from either installation media or from a downloaded
installation package.
Table 80. Installation options for IBM Director Server on AIX
Version Installation media Downloaded installation package file
name
5.20 IBM Director for AIX 5L, V5.20 CD Dir5.20_AIX.tar.gz
5.20 Update 1 IBM Director for AIX 5L, Dir5.20.1_Server_AIX.tar.gz
Version 5.20 Update 1 CD
Dir5.20.1_AIX.iso
5.20.2 IBM Director for AIX, Version 5.20.2 (2 Dir5.20.2_Server_AIX.tar.gz
CDs) CD
Dir5.20.2_AIX.iso
where dev/cd0 is the specific device file for the block device and mnt is the
mount point of the drive.
c. To change to the directory in which IBM Director Server is located, type
the following command and press Enter:
cd /mnt/director/server/aix
9. Select the database application to use with IBM Director. You have the
following options:
Apache Derby
(Option on all platforms except i5/OS) Creates and configures an
embedded Apache Derby database. The Apache Derby application is
included in the IBM Director installation.
IBM DB2 Universal Database
Configures IBM Director to use an IBM DB2 database. IBM DB2 must
be installed and configured on a system in your network.
Oracle Configures IBM Director to use an Oracle database. Oracle Server
must be installed and configured on a system in your network.
Select later (database disabled)
IBM Director will be installed without a database. Tasks requiring a
database will be absent or not functional.
Important: You can configure IBM Director for use with your
database application at any point after the installation of IBM Director
Server, but you must not start the management server until it is
completed. Starting the management server before configuring IBM
Director to use a database application might result in a loss of
functionality.
11. Optional: Configure IBM Director for use with a database application. For
more information, see “Configuring the database on Linux or AIX” on page
344.
Depending on the version of IBM Director Server you are installing, you can install
IBM Director Server on i5/OS from either installation media or from a downloaded
installation package.
Table 82. Installation options for IBM Director Server on i5/OS
Version Installation media Downloaded installation package file
name
5.20 IBM Director for i5/OS, V5.20 not available
5.20 Update 1 not available dir5.20.1_server_i5OS.zip
5.20.2 IBM Director for i5/OS, Version 5.20.2 dir5.20.2_server_i5OS.zip
If the version of IBM Director Server you are installing is available on installation
media for i5/OS, use these instructions to install IBM Director Server on i5/OS.
Important:
v IBM Director Server and IBM Director Console must be at the same release level.
For example, if you install IBM Director Server, version 5.20.1 on the
management server, you must also install IBM Director Console, version 5.20.1
on any systems that you want to access the management server.
v On management servers running i5/OS, IBM Director Server includes all the
functionality of IBM Director Agent. It is not possible or necessary to separately
install IBM Director Agent on the management server after installing IBM
Director Server. Any IBM Director tasks requiring IBM Director Agent will be
performed for systems with IBM Director Server installed.
v To use IBM Director Console to access IBM Director Server on a system that is
running i5/OS, IBM Director Console must be installed on a separate non-i5/OS
server.
Before you install IBM Director Server, make sure that you have completed
planning and preparing for the installation, and that the server meets the hardware
requirements to install IBM Director. You also must meet the prerequisites included
in “Preparing to install IBM Director on i5/OS” on page 148.
Note: When your system is in a restricted state (endsbs *all *immed), TCP/IP
is not active. As a result, IBM Director will not start automatically after the
installation. After installing in a restricted state, run the strtcp command to start
TCP/IP, and then start IBM Director.
2. Insert the CD into the CD-ROM drive.
3. Run RSTLICPGM.
4. In the Product field, type the product number for IBM Director Server
(5722DR1).
5. In the Device field, type the optical device identifier, for example, opt01.
6. Press Enter. The installation progress for IBM Director Server is displayed.
Continue with steps to install IBM Director Agent and IBM Director Console on
the other systems in your IBM Director environment. After you have installed the
components of IBM Director, complete the required configuration steps.
Important:
v IBM Director Server and IBM Director Console must be at the same release level.
For example, if you install IBM Director Server, version 5.20.1 on the
management server, you must also install IBM Director Console, version 5.20.1
on any systems that you want to access the management server.
v On management servers running i5/OS, IBM Director Server includes all the
functionality of IBM Director Agent. It is not possible or necessary to separately
install IBM Director Agent on the management server after installing IBM
Director Server. Any IBM Director tasks requiring IBM Director Agent will be
performed for systems with IBM Director Server installed.
v To use IBM Director Console to access IBM Director Server on a system that is
running i5/OS, IBM Director Console must be installed on a separate non-i5/OS
server.
v Before installing IBM Director Server on a system that has IBM Director Agent
installed, you must first uninstall the existing IBM Director component.
Before you install IBM Director Server, make sure that you have completed
planning and preparing for the installation, and that the server meets the hardware
requirements to install IBM Director. You also must meet the prerequisites included
in “Preparing to install IBM Director on i5/OS” on page 148.
Chapter 3. Installing 189
To install IBM Director Server, complete the following steps:
1. On a system that can connect to the i5/OS system, download the installation
package from the IBM Director Web site at www.ibm.com/systems/
management/director/.
2. Extract the contents of the installation package into a local directory.
3. Log on to the System i platform by using a profile with the following
privileges: *ALLOBJ and *SECADM.
Note: When your system is in a restricted state (endsbs *all *immed), TCP/IP
is not active. As a result, IBM Director will not start automatically after the
installation. After installing in a restricted state, run the strtcp command to
start TCP/IP, and then start IBM Director.
4. On the i5/OS system, type the following command and press Enter to create a
save file for the SAVDR100MM.sav file:
CRTSAVF FILE(QGPL/SAVDR100MM)
5. From the directory into which you extracted the contents of the downloaded
installation package, start an FTP session to the i5/OS system and then type
the following commands, pressing Enter after each:
binary
put FILES/SAVDR100MM.sav /qsys.lib/qgpl.lib/SAVDR100MM.file
6. If a previous version of IBM Director Server is installed and running, stop
IBM Director Server by typing the following command from a command
prompt and pressing Enter:
QSH CMD(’/qibm/userdata/director/bin/twgend’)
7. Verify that IBM Director Server has been stopped by typing the following
command from a command prompt and pressing Enter:
QSH CMD(’/qibm/userdata/director/bin/twgstat’)
8. On the i5/OS system, type the following command and press Enter to install
the upgrade:
RSTLICPGM LICPGM(5722DR1) DEV(*SAVF) SAVF(QGPL/SAVDR100MM)
9. Installing IBM Director Server when not in restricted state should also start it.
Otherwise, start IBM Director Server by typing the following command from a
command prompt and pressing Enter:
QSH CMD(’/qibm/userdata/director/bin/twgstart’)
10. Verify that the status for IBM Director Server is Active. Type the following
command from a command prompt and press Enter:
QSH CMD(’/qibm/userdata/director/bin/twgstat’)
11. To delete the SAVDR100MM.sav file, type the following command and press
Enter:
DLTF FILE(QGPL/SAVDR100MM)
Continue with steps to install IBM Director Agent and IBM Director Console on
the other systems in your IBM Director environment. After you have installed the
components of IBM Director, complete the required configuration steps.
Important:
Optional: If you choose to use a database application other than Apache Derby
with IBM Director, be sure to perform any necessary preparation steps before
configuring IBM Director to use the database. For more information, see
“Preparing the IBM Director database” on page 131.
Depending on the version of IBM Director Server you are installing, you can install
IBM Director Server on Linux for System x from either installation media or from
a downloaded installation package.
Table 83. Installation options for IBM Director Server on Linux for System x
Version Installation media Downloaded installation package file
name
5.20 IBM Director on x86, V5.20 CD dir5.20_server_linux.tar
5.20 Update 1 IBM Director on x86, dir5.20.1_server_linux.tar
Version 5.20 Update 1 CD
5.20.2 IBM Director on x86, Version 5.20.2 CD dir5.20.2_server_linux.tar
1. To install IBM Director Server from a Web download, perform the following
steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
b. To extract the contents of the installation package, type the following
command:
tar -xvf install_package
where dev/cdrom is the specific device file for the block device and
mnt/cdrom is the mount point of the drive.
c. Change to the directory in which the installation script is located. Type the
following command and press Enter:
cd /mnt/cdrom/director/server/linux/i386/
where directory is the local directory to which you copied the response file.
5. Open an ASCII text editor and modify the installation settings in the
dirserv.rsp file. This file is fully commented.
You can specify the location of the RPM files, select the IBM Director
extensions and features that you want to install, configure a database to use
with IBM Director, and select log file options.
6. Save the modified response file with a new file name.
7. To install IBM Director Server using the response file, type one of the
following commands and press Enter:
v Installing from CD: ./dirinstall -r /directory/response.rsp
v Installing from download (version 5.20): ./dir5.20_server_linux.sh -r
/directory/response.rsp
10. Select the database application to use with IBM Director. You have the
following options:
Apache Derby
(Option on all platforms except i5/OS) Creates and configures an
embedded Apache Derby database. The Apache Derby application is
included in the IBM Director installation.
IBM DB2 Universal Database
Configures IBM Director to use an IBM DB2 database. IBM DB2 must
be installed and configured on a system in your network.
Microsoft Data Engine (MSDE) 2000 or Microsoft SQL Server 2000
Configures IBM Director to use an MSDE or Microsoft SQL Server
database. MSDE or Microsoft SQL Server must be installed and
configured on a system in your network.
Oracle Configures IBM Director to use an Oracle database. Oracle Server
must be installed and configured on a system in your network.
PostgreSQL
Configures IBM Director to use a PostgreSQL database. PostgreSQL
must be installed and configured on a system in your network
Select later (database disabled)
IBM Director will be installed without a database. Tasks requiring a
database will be absent or not functional.
Go to step 13.
12. Optional: Configure IBM Director for use with a database application. For
more information, see “Configuring the database on Linux or AIX” on page
344.
Important: You can configure IBM Director for use with your database
application at any point after the installation of IBM Director Server, but you
must not start the management server until it is completed. Starting the
management server before configuring IBM Director to use a database
application might result in a loss of function.
13. Optional: By default, encryption using the Advanced Encryption Standard
(AES) algorithm is enabled during installation. To disable encryption or
change security settings, type the following command and press Enter:
/opt/ibm/director/bin/cfgsecurity
14. To start IBM Director, type the following command and press Enter:
/opt/ibm/director/bin/twgstart
15. Unmount the CD-ROM drive. Perform the following steps to unmount the
CD-ROM drive:
a. Type cd / and press Enter.
b. Type the following command and press Enter:
umount /mnt/cdrom
Depending on your version of IBM Director, you can install from either installation
media or from a downloaded installation package. Table 85 lists the sources of
installation code.
Table 85. Installation options for IBM Director Server on Linux for System z
Version Installation media Downloaded installation package
file name
5.20 IBM Director for Linux on System z, not available
V5.20 CD
5.20 Update 1 IBM Director for Linux on System z, dir5.20.1_server-linux-s390.tar
V5.20.1 CD
5.20 Update 2 IBM Director for Linux on System z, dir5.20.2_server-linux-s390.tar
Version 5.20.2 CD
The IBM Director for Linux on System z CDs are available as ISO images from
ShopzSeries at www.ibm.com/software/ShopzSeries and from the IBM Director
download Web page at www.ibm.com/systems/management/director/
downloads.html. The installation package files are available from the IBM Director
download Web page at www.ibm.com/systems/management/director/
downloads.html.
Important:
v IBM Director Server and IBM Director Console must be at the same release level.
For example, if you install IBM Director Server, version 5.20.1 on the
management server, you must also install IBM Director Console, version 5.20.1
on any systems that you want to access the management server.
v If IBM Director Console and IBM Director Agent are installed on the same
system, both software components must be at the same release level as IBM
Director Server.
v If you are planning to install and use a database for IBM Director other than the
default database, make sure that you have installed and configured the database
application that you will use with IBM Director before installing IBM Director
Server. On management servers not running i5/OS, the default database is
Apache Derby, but other databases can be used.
Note: The default installation uses a graphical user interface for configuring the
IBM Director database. The workstation from which you perform the installation
must have an X Window System or Virtual Network Computing (VNC) client if
you want to use this graphical user interface. If your workstation does not have an
X Window System or Virtual Network Computing (VNC) client, you can use a
customized response file to perform the installation without a graphical user
interface (see step 9 on page 199).
Optional: If you choose to use a database application other than Apache Derby
with IBM Director, be sure to perform any necessary preparation steps before
configuring IBM Director to use the database. For more information, see
“Preparing the IBM Director database” on page 131.
Complete the following steps to install IBM Director Server on Linux for System z:
1. If you install from installation media, make the installation code available to
your Linux system. See “Preparing to install IBM Director Server on Linux for
System z ” on page 155 for more information.
2. If you install from a downloaded installation package, extract the installation
files to a local directory on your Linux system.
3. From a terminal session on your Linux system, change to the directory where
the installation script is located. Type the following command and press Enter:
cd /directory/director/server/linux/s390/
where /directory is the mount point of the file system on the CD or the path to
the directory to which you have extracted the IBM Director installation files.
4. If you want to customize the installation, go to step 5. If you want to accept
the default settings for the installation, type the following command and press
Enter:
./dirinstall
Refer to the response file to view the default values. The response file is
named dirserv.rsp and is located in the same directory as the installation
script. In the response file, “1” indicates that an item is to be installed and “0”
indicates that an item is not to be installed.
Go to step 10 on page 199.
5. If you want to customize the installation and you install from installation
media, copy the response file to a local directory. Type the following
command and press Enter:
cp dirserv.rsp /directory
where directory is the local directory with your copy of the response file and
response.rsp is the name of the response file saved in step 7.
9. The selections you made in the response file determine what you do next.
10. Select the database application to use with IBM Director. You have the
following options:
Apache Derby
(Option on all platforms except i5/OS) Creates and configures an
embedded Apache Derby database. The Apache Derby application is
included in the IBM Director installation.
IBM DB2 Universal Database
Configures IBM Director to use an IBM DB2 database. IBM DB2 must
be installed and configured on a system in your network.
Microsoft Data Engine (MSDE) 2000 or Microsoft SQL Server 2000
Configures IBM Director to use an MSDE or Microsoft SQL Server
database. MSDE or Microsoft SQL Server must be installed and
configured on a system in your network.
Oracle Configures IBM Director to use an Oracle database. Oracle Server
must be installed and configured on a system in your network.
PostgreSQL
Configures IBM Director to use a PostgreSQL database. PostgreSQL
must be installed and configured on a system in your network
Select later (database disabled)
IBM Director will be installed without a database. Tasks requiring a
database will be absent or not functional.
Important: You can configure IBM Director for use with your
database application at any point after the installation of IBM Director
Server, but you must not start the management server until it is
Click Next to configure the IBM Director database. Refer to Table 86 for
application-specific configuration instructions.
Table 86. Database configuration
If the database
application is Complete the applicable steps
Apache Derby The IBM Director Apache Derby Configuration window opens. The
values cannot be changed.
Go to step 12.
11. Optional: Configure IBM Director for use with a database application. For
more information, see “Configuring the database on Linux or AIX” on page
344.
Important: You can configure IBM Director for use with your database
application at any point after the installation of IBM Director Server, but you
must not start the management server until it is completed. Starting the
management server before configuring IBM Director to use a database
application might result in a loss of function.
12. Optional: By default, encryption using the Advanced Encryption Standard
(AES) algorithm is enabled during installation. To disable encryption or
change security settings, type the following command and press Enter:
/opt/ibm/director/bin/cfgsecurity
13. To start IBM Director, type the following command and press Enter:
/opt/ibm/director/bin/twgstart
To enable SNMP Access and Trap Forwarding, install and configure Net-SNMP,
version 5.2.1. See “Enabling SNMP access and trap forwarding for Linux” on page
335.
Important:
v IBM Director Server and IBM Director Console must be at the same release level.
For example, if you install IBM Director Server, version 5.20.1 on the
management server, you must also install IBM Director Console, version 5.20.1
on any systems that you want to access the management server.
v If IBM Director Console and IBM Director Agent are installed on the same
system, both software components must be at the same release level as IBM
Director Server.
v If you are planning to install and use a database for IBM Director other than the
default database, make sure that you have installed and configured the database
application that you will use with IBM Director before installing IBM Director
Server. On management servers not running i5/OS, the default database is
Apache Derby, but other databases can be used.
v On management servers not running i5/OS, IBM Director Server includes all the
functionality of IBM Director Agent and IBM Director Console. It is not possible
or necessary to separately install either IBM Director Agent or IBM Director
Console on the management server after installing IBM Director Server. Any
IBM Director tasks requiring IBM Director Agent or IBM Director Console will
be performed for systems with IBM Director Server installed.
v Before installing IBM Director Server on a system that has IBM Director Console
or IBM Director Agent installed, you must first uninstall the existing IBM
Director component.
v Before installing IBM Director Server on a system that has IBM Storage
Configuration Manager installed, you must first uninstall IBM Storage
Configuration Manager. After installing IBM Director Server, you can re-install
IBM Storage Configuration Manager.
During the installation process, you can install several IBM Director Server
features.
Optional: If you choose to use a database application other than Apache Derby
with IBM Director, be sure to perform any necessary preparation steps before
configuring IBM Director to use the database. For more information, see
“Preparing the IBM Director database” on page 131.
1. To install IBM Director Server from a Web download, perform the following
steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
b. To unzip and extract the contents of the installation package, type the
following command:
gzip -cd install_package | tar -xvf -
where directory is the local directory into which you extracted the files.
d. Go to step 3.
2. To start the installation from the CD, perform the following steps:
a. Insert the CD into the CD-ROM drive.
b. If the CD does not automount, type the following command and press
Enter:
mount /dev/cdrom /mnt/cdrom
where dev/cdrom is the specific device file for the block device and
mnt/cdrom is the mount point of the drive.
c. Change to the directory in which the installation script is located. Type the
following command and press Enter:
cd /mnt/cdrom/director/server/linux/ppc/
where directory is the local directory into which you copied the response file,
and response.rsp is the name of the response file saved in step 6.
8. The selections you made in the response file determine what you do next.
9. Select the database application to use with IBM Director. You have the
following options:
Apache Derby
(Option on all platforms except i5/OS) Creates and configures an
embedded Apache Derby database. The Apache Derby application is
included in the IBM Director installation.
IBM DB2 Universal Database
Configures IBM Director to use an IBM DB2 database. IBM DB2 must
be installed and configured on a system in your network.
Microsoft Data Engine (MSDE) 2000 or Microsoft SQL Server 2000
Configures IBM Director to use an MSDE or Microsoft SQL Server
database. MSDE or Microsoft SQL Server must be installed and
configured on a system in your network.
Chapter 3. Installing 205
Oracle Configures IBM Director to use an Oracle database. Oracle Server
must be installed and configured on a system in your network.
PostgreSQL
Configures IBM Director to use a PostgreSQL database. PostgreSQL
must be installed and configured on a system in your network
Select later (database disabled)
IBM Director will be installed without a database. Tasks requiring a
database will be absent or not functional.
Important: You can configure IBM Director for use with your
database application at any point after the installation of IBM Director
Server, but you must not start the management server until it is
completed. Starting the management server before configuring IBM
Director to use a database application might result in a loss of
functionality.
10. Click Next to configure IBM Director for use with your database application.
Refer to Table 88 for application-specific configuration instructions.
Table 88. Database configuration
If the database
application is Complete the applicable steps
Apache Derby The IBM Director Apache Derby Configuration window opens. The
values cannot be changed.
Go to step 12.
11. Optional: Configure IBM Director for use with a database application. For
more information, see “Configuring the database on Linux or AIX” on page
344.
Important: You can configure IBM Director for use with your database
application at any point after the installation of IBM Director Server, but you
must not start the management server until it is completed. Starting the
management server before configuring IBM Director to use a database
application might result in a loss of function.
12. Optional: By default, encryption using the Advanced Encryption Standard
(AES) algorithm is enabled during installation. To disable encryption or
change security settings, type the following command and press Enter:
install_root/bin/cfgsecurity
where install_root represents the root directory of your IBM Director Server
installation.
13. To start IBM Director, type the following command and press Enter:
install_root/bin/twgstart
14. If you used the CD to install IBM Director Server, unmount the drive by
completing the following steps:
a. Type cd / and press Enter.
b. Type the following command and press Enter:
umount /mnt/cdrom
To configure your database application for use with IBM Director, see “Configuring
the database on a Linux or AIX management server using the cfgdb command” on
page 344
To enable SNMP Access and Trap Forwarding, install and configure Net-SNMP,
version 5.2.1, see “Enabling SNMP access and trap forwarding for Linux” on page
335.
Important:
v IBM Director Server and IBM Director Console must be at the same release level.
For example, if you install IBM Director Server, version 5.20.1 on the
management server, you must also install IBM Director Console, version 5.20.1
on any systems that you want to access the management server.
v If IBM Director Console and IBM Director Agent are installed on the same
system, both software components must be at the same release level as IBM
Director Server.
v If you are planning to install and use a database for IBM Director other than the
default database, make sure that you have installed and configured the database
application that you will use with IBM Director before installing IBM Director
Server. On management servers not running i5/OS, the default database is
Apache Derby, but other databases can be used.
v On management servers not running i5/OS, IBM Director Server includes all the
functionality of IBM Director Agent and IBM Director Console. It is not possible
or necessary to separately install either IBM Director Agent or IBM Director
Console on the management server after installing IBM Director Server. Any
IBM Director tasks requiring IBM Director Agent or IBM Director Console will
be performed for systems with IBM Director Server installed.
v Before installing IBM Director Server on a system that has IBM Director Console
or IBM Director Agent installed, you must first uninstall the existing IBM
Director component.
v Before installing IBM Director Server on a system that has IBM Storage
Configuration Manager installed, you must first uninstall IBM Storage
Configuration Manager. After installing IBM Director Server, you can re-install
IBM Storage Configuration Manager.
When you install IBM Director Server, the InstallShield wizard automatically
installs IBM Director Console and IBM Director Agent. During the installation
process, you can install the optional IBM Director features. You also can change
security settings.
This section provides instructions for installing IBM Director Server using the
InstallShield wizard. The wizard can be used in a standard interactive mode, or
you can perform an unattended installation using a response file to provide
answers to the questions that the wizard poses.
After preparing your System x server for the installation of IBM Director, run the
IBM Director Server installation program and choose the features that you want to
install.
Depending on the version of IBM Director Server you are installing, you can install
IBM Director Server on Windows from either installation media or from a
downloaded installation package.
Table 89. Installation options for IBM Director Server on Windows
Version Installation media Downloaded installation package file
name
5.20 IBM Director on x86, V5.20 CD dir5.20_System_x.iso (CD image)
5.20 Update 1 IBM Director on x86, dir5.20.1_server_patch_windows.zip
Version 5.20 Update 1 CD (upgrade only)
Notes:
v If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on the
system, it is installed during the IBM Director Server installation. If the upgrade
is necessary, the system prompts you to restart following the installation of IBM
Director Server without specifying that MSI was installed. Unless you install
using the response file and set the RebootIfRequired parameter to N, you are
prompted to restart whether or not the IBM Director Server installation is
completed successfully.
In addition, if you attempt to perform an administrative installation and MSI has
not yet been upgraded, you must add the admin parameter when you start the
InstallShield Wizard in this procedure. For example, you would type the
following command:
\director\server\windows\i386\ibmsetup.exe admin
This parameter updates MSI and runs the installation program in administrative
mode. Restart the system if prompted to do so.
v To use the upgrade patch to upgrade IBM Director Server to version 5.20.1,
version 5.20 must already be installed.
v To upgrade a version of IBM Director Server earlier than 5.20, you must perform
a full installation of the version to which you want to upgrade. See “Upgrading
to IBM Director 5.20 or later from previous releases.”
1. Using an account with either local or domain administrative privileges, log on
to the operating system.
2. Downloaded upgrade patches (5.20.1 only): To start the installation, perform
the following steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
b. Use the unzip command to extract the contents of the installation package
to a temporary directory.
c. Click Start → Run.
d. In the Open field, type the following command and press Enter:
\install_files\FILES\dir5.20.1_server_patch_windows.exe
where e is the drive letter on your system. The installation program starts, and
the IBM Director Setup window opens.
8. 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 CD.
d. Run the ibmsetup.exe program. The InstallShield wizard starts, and the
Welcome to the InstallShield Wizard for IBM Director Server window
opens. Continue to step 9.
9. Click Next. The License Agreement window opens.
10. Click I accept the terms in the license agreement; then, click Next. The
Installation Type window opens.
11. Click Next. The Feature and Installation Directory Selection window opens.
IBM Director Server, Level 2: IBM Director Agent, Level 1: IBM Director Core
Services, IBM Director Console, and xSeries Support and tasks 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 optional
feature that is not selected by default.
12. Select the IBM Director Agent features that you want to install:
IBM Director Remote Control Agent
Enables a system administrator to perform remote desktop functions
on the management server.
BladeCenter Management Extension
Enables a system administrator to manage BladeCenter units.
Rack Manager
Enables a system administrator to use the Rack Manager task to build
a realistic, visual representation of a rack and its components.
To select a feature, click the red X to the left of the feature name. A menu
opens. To select the feature, click either This feature will be installed on local
hard drive or This feature, and all subfeatures, will be installed on local
hard drive.
13. Click Next. The IBM Director Service Account Information window opens.
Figure 8. Installing IBM Director Server on Windows: IBM Director Service Account
Information window
16. 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.
17. Click Next. The Software Distribution Settings window opens.
18. 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.
19. Click Next. The Ready to Install the Program window opens.
20. Click Install. The Installing IBM Director Server window opens. The progress
of the installation is displayed in the Status field. When the installation is
Figure 10. Installing IBM Director Server on Windows: Network Driver Configuration window
21. In the System name field, type the name that you want to be displayed in
IBM Director Console. By default, this is the NetBIOS name of the
management server.
22. Define the communication protocols to use between IBM Director Server and
IBM Director Agent.
a. In the Network drivers field, the TCPIP (all adapters) setting is enabled by
default. To enable another protocol, select the protocol and then select the
Enable driver check box.
Note: If you disable the TCPIP (all adapters) setting and enable an
individual device driver on a system with multiple network adapters, IBM
Director Server will receive only those data packets addressed to the
individual adapter.
b. In the Network timeout field, type the number of seconds that IBM
Director Server waits for a response from IBM Director Agent. By default,
this value is set to 15 seconds.
c. Select the Enable Wake on LAN check box if the network adapter
supports the Wake on LAN feature.
Figure 11. Installing IBM Director Server: IBM Director Database Configuration window
24. Click the database application that you want to use with IBM Director. You
have the following options:
Apache Derby
(Option on all platforms except i5/OS) Creates and configures an
embedded Apache Derby database. The Apache Derby application is
included in the IBM Director installation.
IBM DB2 Universal Database
Configures IBM Director to use an IBM DB2 database. IBM DB2 must
be installed and configured on a system in your network.
Microsoft Data Engine (MSDE) 2000 or Microsoft SQL Server 2000
Configures IBM Director to use an MSDE or Microsoft SQL Server
database. MSDE or Microsoft SQL Server must be installed and
configured on a system in your network.
Important: You can configure IBM Director for use with your
database application at any point after the installation of IBM Director
Server, but you must not start the management server until it is
completed. Starting the management server before configuring IBM
Director to use a database application might result in a loss of
functionality.
25. Click Next and begin configuring the IBM Director database.
If the database
application is Complete the applicable steps
Apache Derby The IBM Director Apache Derby Configuration window opens. The
values cannot be changed. Click Next and go to step 26 on page 218.
IBM DB2 The IBM Director DB2 Universal Database Configuration window
opens.
Click Next.
MSDE or Microsoft The IBM Director Microsoft SQL Server Database Configuration
SQL Server window opens.
Click Next.
Click Next.
Select later (database Go to step 26
disabled)
26. Click Finish. A window opens, asking you if you want to restart the server.
27. Remove the CD from the CD-ROM drive.
28. Click Yes to restart the server.
Related tasks
“Upgrading to IBM Director 5.20 or later from previous releases” on page 278
You can upgrade IBM Director version 4.10 or later components by running the
installation program for the component that you want to upgrade. During the
After preparing your System x server for the installation of IBM Director, you can
perform an unattended installation of IBM Director Server by using a response file.
This method creates a standard installation file that can be used on many systems.
Optional: If you choose to use a database application other than Apache Derby
with IBM Director, be sure to perform any necessary preparation steps before
configuring IBM Director to use the database. For more information, see
“Preparing the IBM Director database” on page 131.
When you perform an unattended installation of IBM Director Server, the response
file provides answers to the questions that are posed by the InstallShield wizard.
Important: The response file for IBM Director Server contains entries for a User ID
and Password to use with the IBM Director service account. The User ID and
Password must correspond to a Windows account with administrator privileges. If
you choose to include this information in the response file, be sure to delete the
file after the installation is complete to avoid security issues.
Depending on the version of IBM Director Server you are installing, you can install
IBM Director Server on Windows from either installation media or from a
downloaded installation package.
Table 90. Installation options for IBM Director Server on Windows
Version Installation media Downloaded installation package file
name
5.20 IBM Director on x86, V5.20 CD dir5.20_System_x.iso (CD image)
5.20 Update 1 IBM Director on x86, dir5.20.1_server_patch_windows.zip
Version 5.20 Update 1 CD (upgrade only)
Notes:
v If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on the
system, it is installed during the IBM Director Server installation. If the upgrade
is necessary, the system prompts you to restart following the installation of IBM
Director Server without specifying that MSI was installed. Unless you install
using the response file and set the RebootIfRequired parameter to N, you are
prompted to restart whether or not the IBM Director Server installation is
completed successfully.
In addition, if you attempt to perform an administrative installation and MSI has
not yet been upgraded, you must add the admin parameter when you start the
InstallShield Wizard in this procedure. For example, you would type the
following command:
\director\server\windows\i386\ibmsetup.exe admin
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 created in
step 4.
v option is one of the following optional parameters:
Table 91. Optional installation parameters
Parameter What it does
waitforme Ensures that ibmsetup.exe process will not end until the
installation of IBM Director Server is completed
debug Logs all messages that are sent by the Microsoft Windows
Installer log engine, including status and information
messages
log=logfilename Specifies the fully qualified name of an alternative log file
verbose Enables verbose logging
7. If you set the RebootIfRequired parameter to Y in the response file, reboot the
system if prompted to do so.
8. When the installation is completed, remove the CD from the drive.
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.
Important:
v On management servers not running i5/OS, it is not possible or necessary to
separately install either IBM Director Agent or IBM Director Console on the
management server after installing IBM Director Server. Any IBM Director tasks
requiring IBM Director Agent or IBM Director Console will be performed for
systems with IBM Director Server installed.
v IBM Director Server and IBM Director Console must be at the same release level.
For example, if you install IBM Director Server, version 5.20.1 on the
management server, you must also install IBM Director Console, version 5.20.1
on any systems that you want to access the management server.
Depending on the version of IBM Director Console you are installing, you can
install IBM Director Console on AIX from either installation media or from a
downloaded installation package.
Table 92. Installation options for IBM Director Console on AIX
Version Installation media Downloaded installation package file
name
5.20 IBM Director for AIX 5L, V5.20 CD Dir5.20_AIX.tar.gz
1. To install IBM Director Console from a Web download, perform the following
steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
b. To unzip and extract the contents of the installation package, type the
following command:
gzip -cd install_package | tar -xvf -
where dev/cd0 is the specific device file for the block device and mnt is the
mount point of the drive.
c. To change to the directory where IBM Director Console is located, type the
following command and press Enter:
cd /mnt/director/console/aix
Go to step 8.
4. To customize the installation, copy the response file (dircon.rsp) to a local
directory. Type the following command and press Enter:
cp dircon.rsp /directory/
where directory is the local directory to which you copied the response file, and
response.rsp is the name of the response file saved in step 6.
Go to step 8.
8. To start IBM Director Console, type the following command and press Enter:
/opt/ibm/director/bin/twgcon
9. If you installed IBM Director Console from the CD, unmount the drive. Type
the following command and press Enter:
umount /mnt
Important:
Depending on the version of IBM Director Console you are installing, you can
install IBM Director Console on Linux for System x from either installation media
or from a downloaded installation package.
Table 93. Installation options for IBM Director Console on Linux for System x
Version Installation media Downloaded installation package file
name
5.20 IBM Director on x86, V5.20 CD or IBM dir5.20_console_linux.tar
Director Agents & Consoles, V5.20
(2 of 2) CD dir5.20_System_x.iso
5.20 Update 1 IBM Director on x86, dir5.20.1_console_linux.tar
Version 5.20 Update 1 CD
dir5.20.1_System_x.iso
5.20.2 IBM Director on x86, Version 5.20.2 CD dir5.20.2_console_linux.tar
dir5.20.2_System_x.iso
1. To install IBM Director Console from a Web download, perform the following
steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
b. To extract the contents of the installation package, type the following
command:
tar -xvf install_package
where dev/cdrom is the specific device file for the block device and
mnt/cdrom is the mount point of the drive.
c. Change to the directory in which the installation script is located. Type the
following command and press Enter:
cd /mnt/cdrom/director/console/linux/i386
Depending on your version of IBM Director, you can install from either installation
media or from a downloaded installation package. Table 94 lists the sources of
installation code.
Table 94. Installation options for IBM Director Console on Linux for System z
Version Installation media Downloaded installation package
file name
5.20 IBM Director for Linux on System z, not available
V5.20 CD or IBM Director Agents &
Consoles, V5.20 (2 of 2) CD
5.20 Update 1 IBM Director for Linux on System z, dir5.20.1_console-linux-s390.tar
V5.20.1 CD
5.20 Update 2 IBM Director for Linux on System z, dir5.20.2_console-linux-s390.tar
Version 5.20.2 CD or IBM Director
Agents & Consoles, Version 5.20.2
(2 of 2) CD
The IBM Director for Linux on System z CDs are available as ISO images from
ShopzSeries at www.ibm.com/software/ShopzSeries and from the IBM Director
download Web page at www.ibm.com/systems/management/director/
downloads.html. The IBM Director Agents & Consoles (2 of 2) CDs are available as
ISO images from ShopzSeries at www.ibm.com/software/ShopzSeries. The
installation package files are available from the IBM Director download Web page
at www.ibm.com/systems/management/director/downloads.html.
Complete the following steps to install IBM Director Console on Linux for
System z:
1. If you install from installation media, make the installation code available to
your Linux system.
2. If you install from a downloaded installation package, extract the installation
files to a local directory on your Linux system.
3. From a terminal session on your Linux system, change to the directory in
which the installation script is located. Type the following command and press
Enter:
cd /mnt/director/console/linux/s390/
where /mnt is the mount point of the file system on the CD or the path to the
directory to which you have extracted the IBM Director installation files.
4. If you want to customize the installation, go to step 5 on page 226. If you
want to accept the default settings for the installation, type the following
command and press Enter:
./dirinstall
Refer to the response file to view the default values. The response file is
named dircon.rsp and is located in the same directory as the installation
script. In the response file, “1” indicates that an item is to be installed and “0”
indicates that an item is not to be installed.
Go to step 10 on page 226.
Depending on the version of IBM Director Console you are installing, you can
install IBM Director Console on Linux on POWER from either installation media or
from a downloaded installation package.
Table 95. Installation options for IBM Director Console on Linux on POWER
Version Installation media Downloaded installation package file name
5.20 IBM Director for Linux on Dir5.20_LinuxonPower.tar.gz
POWER, V5.20 CD
Dir5.20_LinuxonPower.iso
IBM Director Agents &
Consoles, V5.20 (2 of 2) CD
5.20 Update 1 IBM Director for Linux on Dir5.20.1_Agent_Console_LinuxonPower.tar.gz
POWER,
Version 5.20 Update 1 CD Dir5.20.1_LinuxonPower.iso
5.20.2 IBM Director for Linux on Dir5.20.2_Agent_Console_LinuxonPower.tar.gz
POWER, Version 5.20.2 CD
Dir5.20.2_LinuxonPower.iso
1. To install IBM Director Console from a Web download, perform the following
steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
b. To unzip and extract the contents of the installation package, type the
following command:
gzip -cd install_package | tar -xvf -
where directory is the local directory into which you extracted the files.
d. Go to step 3.
2. To install IBM Director Console from the CD, perform the following steps:
a. Insert the CD into the CD-ROM drive.
b. If the CD does not automount, type the following command and press
Enter:
mount /dev/cdrom /mnt/cdrom
where dev/cdrom is the specific device file for the block device and
mnt/cdrom is the mount point of the drive.
c. Change to the directory in which the installation script is located. Type the
following command and press Enter:
cd /mnt/cdrom/director/console/linux/ppc
Go to step 8.
4. To customize the installation, copy the response file (dircon.rsp) to a local
directory. Type the following command and press Enter:
cp dircon.rsp /directory
where directory is the local directory to which you copied the response file and
responsefile.rsp is the name of the modified response file saved in step 6.
8. If you installed IBM Director Console from the CD, unmount the drive by
completing the following steps:
a. Type cd / and press Enter.
b. Type the following command and press Enter:
umount /mnt/cdrom
Depending on the version of IBM Director Console you are installing, you can
install IBM Director Console on Windows from either installation media or from a
downloaded installation package.
Table 96. Installation options for IBM Director Console on Windows
Version Installation media Downloaded installation package file
name
5.20 IBM Director on x86, V5.20 CD or IBM dir5.20_console_windows.zip
Director Agents & Consoles, V5.20
(2 of 2)
5.20 Update 1 IBM Director on x86, dir5.20.1_console_windows.zip (full
Version 5.20 Update 1 CD install) or
dir5.20.1_console_patch_windows.zip
(upgrade only)
5.20.2 IBM Director on x86, Version 5.20.2 CD dir5.20.2_console_windows.zip
Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on
the system, it is installed during the IBM Director 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.
This parameter updates MSI and runs the installation program in administrative
mode. Restart the system if prompted to do so.
1. To start the installation from a Web download, perform the following steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
b. Use the unzip command to extract the contents of the installation package
to a temporary directory.
c. Click Start → Run.
d. Full installation only: In the Open field, type one of the following
commands and press Enter:
v 5.20: \install_files\dir5.20_console_windows.exe
v 5.20.1: \install_files\dir5.20.1_console_windows.exe
where e is the drive letter of the drive. The installation program starts, and
the IBM Director Setup window opens.
d. Click Install IBM Director Console. The InstallShield wizard starts, and
the Welcome to the InstallShield Wizard for IBM Director Console window
opens. Continue to step 4.
Accessibility note: Screen readers might not process the IBM Director Setup
window correctly. To start the installation wizard for IBM Director Console
using the keyboard, perform the following steps:
a. Close the IBM Director Setup window.
b. Open Windows Explorer.
c. Browse to the director/console/windows/i386 directory on the IBM
Director on x86 CD.
d. Run the ibmsetup.exe program. The InstallShield wizard starts, and the
Welcome to the InstallShield Wizard for IBM Director Console window
opens. Continue to step 4.
4. Click Next. The License Agreement window opens.
5. Click I accept the terms in the license agreement; then, click Next. The
Feature and Installation Directory Selection window opens.
IBM Director Console and the System x Management Extension are selected
automatically for installation; a hard-disk-drive icon is displayed to the
left of each component. A red X is displayed to the left of each of the
optional features, BladeCenter Management Extension and Rack Manager.
Depending on the version of IBM Director Console you are installing, you can
install IBM Director Console on Windows from either installation media or from a
downloaded installation package.
Table 97. Installation options for IBM Director Console on Windows
Version Installation media Downloaded installation package file
name
5.20 IBM Director on x86, V5.20 CD or IBM dir5.20_console_windows.zip
Director Agents & Consoles, V5.20
(2 of 2)
5.20 Update 1 IBM Director on x86, dir5.20.1_console_windows.zip (full
Version 5.20 Update 1 CD install) or
dir5.20.1_console_patch_windows.zip
(upgrade only)
5.20.2 IBM Director on x86, Version 5.20.2 CD dir5.20.2_console_windows.zip
Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on
the system, it is installed during the IBM Director 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.
where:
v installationtype is one of the following commands:
– unattended shows the progress of the installation but does not require
any user input.
– silent suppresses all output to the screen during installation.
v responsefile.rsp is the path and name of the response file that you saved in
step 7.
v option is one of the following optional parameters:
Table 98. 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
10. If you installed IBM Director Console from the CD, remove the CD from the
drive when the installation is completed.
Depending on the version of IBM Director Core Services you are installing, you
can install IBM Director Core Services on Linux for System x from either
installation media or from a downloaded installation package.
dir5.20.2_System_x.iso
1. To start the installation from a Web download, perform the following steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
b. To extract the contents of the installation package, type the following
command:
tar -xvf install_package
where dev/cdrom is the specific device file for the block device and
mnt/cdrom is the mount point of the drive.
c. Change to the directory in which the installation script is located. Type the
following command and press Enter:
cd /mnt/cdrom/coresvcs/agent/linux/i386/FILES
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.
For 5.20.2 and later, if you installed IBM Director Core Services on IBM System
x3950 M2, machine type 7141 with either VMware version 3.0.2 or SUSE Linux
Enterprise Server 10 for x86, run the following command:
/opt/ibm/icc/cimom/bin/cimprovider -d -m SCSIDev_Module
This resolves a known issue that can prevent full collection of inventory on the
managed system.
For 5.20.2 and later, if you have a Level-1 managed system that has an LSI 1078
MegaRAID controller installed, you need to install the LSI MegaRAID provider on
the managed system after installing IBM Director Core Services.
Related tasks
“Installing the LSI MegaRAID provider for Windows or Linux” on page 245
For 5.20.2 and later, if you have a Level-1 managed system that has an LSI 1078
MegaRAID controller installed, you need to install the LSI MegaRAID provider
on the managed system after installing IBM Director Core Services.
Depending on your version of IBM Director, you can install from either installation
media or from a downloaded installation package. Table 100 lists the sources of
installation code.
Table 100. Installation options for IBM Director Core Services on Linux for System z
Version Installation media Downloaded installation package
file name
5.20 IBM Director for Linux on System z, not available
V5.20 CD or IBM Director Agents &
Consoles, V5.20 (1 of 2) CD
5.20 Update 1 IBM Director for Linux on System z, dir5.20.1_coreservices-agent-linux-
V5.20.1 CD s390.tar
5.20 Update 2 IBM Director for Linux on System z, dir5.20.2_coreservices-agent-linux-
Version 5.20.2 CD or IBM Director s390.tar
Agents & Consoles, Version 5.20.2
(1 of 2) CD
The IBM Director for Linux on System z CDs are available as ISO images from
ShopzSeries at www.ibm.com/software/ShopzSeries and from the IBM Director
download Web page at www.ibm.com/systems/management/director/
downloads.html. The IBM Director Agents & Consoles (1 of 2) CDs are available as
ISO images from ShopzSeries at www.ibm.com/software/ShopzSeries. The
installation package files are available from the IBM Director download Web page
at www.ibm.com/systems/management/director/downloads.html.
To install Level 1: IBM Director Core Services on Linux for System z, complete the
following steps:
1. If you install from installation media, make the installation code available to
your Linux system.
2. If you install from a downloaded installation package, extract the installation
files to a local directory on your Linux system.
3. From a terminal session on your Linux system, change to the directory in
which the installation script is located. Type the following command and press
Enter:
cd /mnt/coresvcs/agent/linux/s390/FILES/
where /mnt is the mount point of the file system on the CD or path to the
directory to which you have extracted the IBM Director installation files.
4. If you want to customize the installation, go to step 5 on page 235. If you want
to accept the default settings for the installation, type the following command
and press Enter:
./csversion_agent_linz.sh
csversion is a prefix “cs” followed by the product version number. For version
5.20.1, the file name would be cs5.20.1_agent_linz.sh.
where directory is the local directory with your copy of the response file and
response.rsp is the name of the response file saved in step 7.
9. Optional: Keep the response file for future use and reference.
To enable SNMP Access and Trap Forwarding, you must install and configure
Net-SNMP. Use the version included in your distribution.
Depending on the version of IBM Director Core Services you are installing, you
can install IBM Director Core Services on Linux on POWER from either installation
media or from a downloaded installation package.
Table 101. Installation options for IBM Director Core Services on Linux on POWER
Version Installation media Downloaded installation package file name
5.20 IBM Director for Linux on Dir5.20_LinuxonPower.tar.gz
POWER, V5.20 CD
Dir5.20_LinuxonPower.iso
IBM Director Agents &
Consoles, V5.20 (1 of 2) CD
5.20 Update 1 IBM Director for Linux on Dir5.20.1_Agent_Console_LinuxonPower.tar.gz
POWER,
Version 5.20 Update 1 CD Dir5.20.1_LinuxonPower.iso
5.20.2 IBM Director for Linux on Dir5.20.2_Agent_Console_LinuxonPower.tar.gz
POWER, Version 5.20.2 CD
Dir5.20.2_LinuxonPower.iso
1. To install IBM Director Core Services from a Web download, perform the
following steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
where directory is the local directory into which you extracted the files.
d. Go to step 3.
2. To start the installation from the CD, perform the following steps:
a. Insert the CD into the CD-ROM drive.
b. If the CD does not automount, type the following command and press
Enter:
mount /dev/cdrom /mnt/cdrom
where dev/cdrom is the specific device file for the block device and
mnt/cdrom is the mount point of the drive.
c. Change to the directory in which the installation script is located. Type the
following command and press Enter:
cd /mnt/cdrom/coresvcs/agent/linux/ppc/FILES
To enable SNMP Access and Trap Forwarding, you must install and configure
Net-SNMP, version 5.2.1.
To use the InstallShield wizard to install IBM Director Core Services on a system
that is runningWindows, download the installation files from the IBM Director
support Web site or use the CD.
Depending on the version of IBM Director Core Services you are installing, you
can install IBM Director Core Services on Windows from either installation media
or from a downloaded installation package.
Table 102. Installation options for IBM Director Core Services on Windows
Version Installation media Downloaded installation package file
name
5.20 IBM Director on x86, V5.20 CD dir5.20_coreservices_windows.zip
dir5.20.2_System_x.iso
Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on
the system, it is installed during the IBM Director Core Services installation. If the
upgrade is necessary, the system prompts you to restart following the installation
of IBM Director Core Services without specifying that MSI was installed. Unless
you install using the response file and set the RebootIfRequired parameter to N,
you are prompted to restart whether or not the IBM Director Core Services
installation is completed successfully.
This parameter updates MSI and runs the installation program in administrative
mode. Restart the system if prompted to do so.
1. To start the installation from a Web download, perform the following steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
b. Use the unzip command to extract the contents of the installation package
to a temporary directory.
c. Click Start → Run.
d. In the Open field, type one of the following commands and press Enter:
v 5.20: \directory\FILES\dir5.20_coreservices_windows.exe
v 5.20 Update 1: \directory\FILES\dir5.20.1_coreservices_windows.exe
v 5.20.2: \directory\FILES\dir5.20.2_coreservices_windows.exe
where directory is the local directory into which you extracted the files.
The Welcome to the InstallShield Wizard for IBM Director Core Services
window opens.
e. Go to step 4 on page 239.
2. To start the installation from the IBM Director Agents & Consoles (1 of 2) CD,
perform the following steps:
a. Insert the CD into the CD-ROM drive.
b. Click Start → Run.
c. In the Open field, type one of the following commands and press Enter:
v 5.20: \coresvcs\agent\windows\i386\FILES\
dir5.20_coreservices_windows.exe
v 5.20 Update 1: \coresvcs\agent\windows\i386\FILES\
dir5.20.1_coreservices_windows.exe
v 5.20.2: \coresvcs\agent\windows\i386\FILES\
dir5.20.2_coreservices_windows.exe
The Welcome to the InstallShield Wizard for IBM Director Core Services
window opens.
d. Go to step 4 on page 239.
3. To start the installation from the IBM Director on x86 CD, perform the following
steps:
a. Insert the CD into the CD-ROM drive.
b. If the installation program starts automatically and the IBM Director Setup
window opens, go to step 3d.
Otherwise, click Start → Run.
c. In the Open field, type the following command and press Enter:
e:\setup.exe
where e is the drive letter of the drive. The installation program starts, and
the IBM Director Setup window opens.
d. Click Install IBM Director Core Services. The Welcome to the InstallShield
Wizard for IBM Director Core Services window opens.
e. Go to step 4 on page 239.
For 5.20.2 and later, if you have a Level-1 managed system that has an LSI 1078
MegaRAID controller installed, you need to install the LSI MegaRAID provider on
the managed system after installing IBM Director Core Services.
Related tasks
“Installing the LSI MegaRAID provider for Windows or Linux” on page 245
For 5.20.2 and later, if you have a Level-1 managed system that has an LSI 1078
MegaRAID controller installed, you need to install the LSI MegaRAID provider
on the managed system after installing IBM Director Core Services.
You can perform an unattended installation of IBM Director Core Services using a
response file, which provides answers to the questions that are posed by the
InstallShield wizard. You can use this method to create a standard installation file
that can be used on many systems.
Depending on the version of IBM Director Core Services you are installing, you
can install IBM Director Core Services on Windows from either installation media
or from a downloaded installation package.
dir5.20.2_System_x.iso
Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on
the system, it is installed during the IBM Director Core Services installation. If the
upgrade is necessary, the system prompts you to restart following the installation
of IBM Director Core Services without specifying that MSI was installed. Unless
you install using the response file and set the RebootIfRequired parameter to N,
you are prompted to restart whether or not the IBM Director Core Services
installation is completed successfully.
1. To start the installation from a Web download, perform the following steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
b. Use the unzip command to extract the contents of the installation package
to a temporary directory.
c. Copy the response file (\directory\FILES\coresvcs.rsp) to a new location,
where directory is the local directory into which you extracted the files.
d. Go to step 3.
2. To start the installation from a CD, perform the following steps:
a. Insert the CD into the CD-ROM drive.
b. If the installation program starts automatically and the IBM Director Setup
window opens, close it.
c. Copy the response file (\coreservices\agent\windows\i386\FILES\
coresvcs.rsp) to a local directory.
d. Go to step 3.
3. Open the copy of the coresvcs.rsp file in an ASCII text editor.
4. Modify and save the response file with a new file name. This file follows the
Windows INI file format and is fully commented.
5. Click Start → Run.
6. In the Open field, type one of the following commands (all on one line) and
press Enter:
v 5.20:
\directory\FILES\dir5.20_coreservices_windows.exe
/s /a installationtype rsp="responsefile.rsp" option
v 5.20 Update 1:
\directory\FILES\dir5.20.1_coreservices_windows.exe
/s /a installationtype rsp="responsefile.rsp" option
v 5.20.2:
\directory\FILES\dir5.20.2_coreservices_windows.exe
/s /a installationtype rsp="responsefile.rsp" option
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.
For 5.20.2 and later, if you have a Level-1 managed system that has an LSI 1078
MegaRAID controller installed, you need to install the LSI MegaRAID provider on
the managed system after installing IBM Director Core Services.
Related tasks
“Installing the LSI MegaRAID provider for Windows or Linux” on page 245
For 5.20.2 and later, if you have a Level-1 managed system that has an LSI 1078
MegaRAID controller installed, you need to install the LSI MegaRAID provider
on the managed system after installing IBM Director Core Services.
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.
Dir5.20_LinuxonPower.tar.gz
5.20.1 IBM Director for Linux on POWER, /coresvcs/agent/linux/ppc/META-INF/
Version 5.20 Update 1 cs5.20.1_agent_linppc.xml
Dir5.20.1_Agent_Console_LinuxonPower.tar.gz
IBM Director Core Services on Linux for System z
5.20 IBM Director for Linux on System z, V5.20 /coresvcs/agent/linux/s390/META-INF/
cs5.20_agent_linz.xml
IBM Director Agents & Consoles, V5.20 (1 of 2)
5.20.1 dir5.20.1_coreservices-agent-linux-s390.tar /coresvcs/agent/linux/s390/META-INF/
cs5.20.1_agent_linz.xml
IBM Director Core Services on Windows
5.20 IBM Director on x86, V5.20 \coresvcs\agent\windows\i386\META-INF\
dir5.20_coreservices_windows.xml
IBM Director Agents & Consoles, V5.20 (1 of 2)
dir5.20_coreservices_windows.zip \META-INF\dir5.20_coreservices_windows.xml
5.20.1 IBM Director on x86, Version 5.20 Update 1 \coresvcs\agent\windows\i386\META-INF\
dir5.20.1_coreservices_windows.xml
dir5.20.1_coreservices_windows.zip \META-INF\dir5.20.1_coreservices_windows.xml
IBM Director Core Services and OpenSSH on Windows for System x
Note: If a managed system does not have a Secure Shell (SSH) package installed, IBM Director Server cannot
communicate securely with the managed system. You can download OpenSSH for Windows from
www.sourceforge.net/projects/sshwindows/ and use software distribution to distribute the package to the managed
system.
5.20 IBM Director on x86, V5.20 coresvcs\dir5.20_coreservices-toc_windows.xml
5.20.1 IBM Director on x86, Version 5.20 Update 1 \coresvcs\dir5.20.1_coreservices-toc_windows.xml
LM78 and SMBus device drivers for Linux on System x
Notes:
v To install the IBM LM78 or SMBus device driver using the Software Distribution task, you first must build the
binary RPM file and copy it to the same directory as the software distribution package descriptor file.
v See “Preparing to manage service processors with IBM Director” and “Installing IBM LM78 and SMBus device
drivers for Linux” for information about these drivers.
Related tasks
“Preparing to install IBM Director Core Services on Windows” on page 173
Before installing IBM Director Core Services on a managed system running
Windows, make sure that your system meets all the applicable requirements.
“Preparing to manage service processors with IBM Director” on page 141
You can use IBM Director to manage supported service processors that are
installed in a managed system.
Related reference
“Installing IBM LM78 and SMBus device drivers for Linux” on page 150
If you plan to install IBM Director Server on a System x or xSeries server
running Linux, you might need to install either or both the LM78 and SMBus
device drivers for Linux. These device drivers ensure that certain IBM Director
tasks and functions work correctly.
You can create a software package for installing or upgrading IBM Director Agent
or installing IBM Director Core Services.
Figure 13. Creating a software package: Software Distribution Manager window (Premium
Edition)
5. If you have not installed IBM Director 5.20 Software Distribution Premium
Edition, go to step 6. Otherwise, expand the Wizards tree.
6. Double-click IBM Update Assistant. The IBM Update Assistant window
opens.
7. If you want to get files from the management server, click Get files from the
Director server. By default, Get files from the local system is selected.
8. To select a file, click Browse. The IBM Update Package/Root Directory
Location window opens.
9. Locate the appropriate XML file and click it. The name of the XML file is
displayed in the File Name field.
Note: Use the correct XML file for your language. The correct file for English
installations is the one without the language code, for example,
dir5.20_agent_windows.xml.
10. Click OK. The IBM Update Assistant window reopens.
11. Click Next. The second IBM Update Assistant window opens.
12. To specify an alternative response file, click Browse and locate the file that
you modified in step 2 on page 243.
After you create a software package, you can use the Software Distribution task to
remotely install the package on supported systems.
To use the Software Distribution task to install a software package, complete the
following steps:
1. Start IBM Director Console.
2. In the Tasks pane, expand the Software Distribution task.
3. Click the software package that you want to distribute. Then, drag it into the
Group Contents pane and drop it onto the icon that is displayed for the system
on which you want to install the software package. A window opens.
Note: To distribute software to several systems at once, you can drag the
software package into the Groups pane and drop it onto the icon for the group.
Alternatively, you can select multiple managed systems in the Group Contents
pane.
4. When prompted with Do you wish to create a scheduled job for this task
or execute immediately?, click Schedule or Execute Now. If you click Execute
Now, the software package is distributed immediately. If you click Schedule,
the New Scheduled Job window opens.
5. Schedule the job:
a. In the Scheduled Job field, type a unique name for the job. This name is
displayed in the Jobs pane of the Scheduler window.
b. In the Date field, type the day you want the software package to be
installed (in MM/DD/YYYY format).
c. In the Time field, type the time you want the software package to be
installed.
For more information about the Scheduler task, see the IBM Director Systems
Management Guide.
6. Click OK. The Save Job Confirmation window opens.
7. Click OK.
For 5.20.2, IBM Director supports the following managed system and
configurations that need to have the LSI MegaRAID provider installed:
The LSI MegaRAID provider can be installed on Level-1 managed systems running
supported versions of the following operating systems:
v Red Hat Enterprise Linux, version 4.0
v Red Hat Enterprise Linux, version 5.0
v SUSE Linux Enterprise Server 9 for x86
v SUSE Linux Enterprise Server 10 for x86
v Microsoft Windows
Note: The LSI MegaRAID provider is not supported for VMware operating
systems.
See the “Supported operating systems” topic for specific versions of these
operating systems that are supported.
IBM Director Core Services must be installed on the managed system before
installing the LSI MegaRAID provider.
The following LSI MegaRAID provider packages are available for download from
the IBM Director Downloads Web Site:
To install the LSI MegaRAID provider on a Level-1 managed system, complete the
following steps.
1. Download the installation package from the IBM Director Downloads Web Site
at www.ibm.com/systems/management/director/downloads.html.
2. Change to the directory to which you saved the installation package on the
Level-1 managed system.
3. Linux only: Type the following command:
rpm -ivh package_name
where package_name is the file name of the installation package. The status of
the installation is displayed.
4. Windows only: Complete the following steps:
a. Run the downloaded package. No user interaction is required.
b. Run the IndicationSubscription.bat batch file. This file is located in one of
the following directories:
v C:\Program Files\Common Files\IBM\ICC\cimom\bin
v C:\Program Files (x86)\Common Files\IBM\ICC\cimom\bin
246 IBM Director Planning, Installation, and Configuration Guide
c. Shut down and restart Windows.
Related reference
“Operating systems supported by IBM Director 5.20.2” on page 74
IBM Director 5.20.2 provides support for many operating systems. However,
support varies depending on the selected hardware and IBM Director
component.
Important:
v IBM Director Server includes all the functionality of IBM Director Agent. It is
not possible or necessary to separately install IBM Director Agent on the
management server after installing IBM Director Server. Any IBM Director tasks
requiring IBM Director Agent will be performed for systems with IBM Director
Server installed.
v The version of IBM Director Agent cannot be later than the version of IBM
Director Server running on the management system.
v If IBM Director Console and IBM Director Agent are installed on the same
system, both software components must be at the same release level as IBM
Director Server.
Important:
v IBM Director Server includes all the functionality of IBM Director Agent. It is
not possible or necessary to separately install IBM Director Agent on the
management server after installing IBM Director Server. Any IBM Director tasks
requiring IBM Director Agent will be performed for systems with IBM Director
Server installed.
v The version of IBM Director Agent cannot be later than the version of IBM
Director Server running on the management system.
v If IBM Director Console and IBM Director Agent are installed on the same
system, both software components must be at the same release level as IBM
Director Server.
Depending on the version of IBM Director Agent you are installing, you can install
IBM Director Agent on AIX from either installation media or from a downloaded
installation package.
Table 106. Installation options for IBM Director Agent on AIX
Version Installation media Downloaded installation package file
name
5.20 IBM Director for AIX 5L, V5.20 CD Dir5.20_AIX.tar.gz
Dir5.20_AIX.iso
5.20 Update 1 IBM Director for AIX 5L, Dir5.20.1_Agent_Console_AIX.tar.gz
Version 5.20 Update 1 CD
Dir5.20.1_AIX.iso
1. To install IBM Director Agent from a Web download, perform the following
steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
b. To unzip and extract the contents of the installation package, type the
following command:
gzip -cd install_package | tar -xvf -
where dev/cd0 is the specific device file for the block device and mnt is the
mount point of the drive.
c. Change to the directory in which the installation script is located. Type one
of the following commands and press Enter:
v IBM Director Agent 5.20.2 for AIX 5.2: cd /mnt/director/agent/aix52/
FILES
v All others: cd /mnt/director/agent/aix/FILES
where mnt is the mount point of the drive.
d. Go to step 3.
3. If you want to customize the installation, go to step 4. If you want to accept
the default settings for the installation, type one of the following commands
and press Enter:
v 5.20: ./dir5.20_agent_aix.sh
v 5.20 Update 1: dir5.20.1_agent_aix.sh
v 5.20.2 for AIX 5.2: dir5.20.2_agent_aix52.sh
v 5.20.2 for AIX 5.3 and 6.1: dir5.20.2_agent_aix.sh
Go to step 8 on page 249.
4. To customize the installation, copy the response file (diragent.rsp) to a local
directory. Type the following command and press Enter:
cp diragent.rsp /directory
where 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.
If you are upgrading from a previous version of IBM Director Agent, migration of
the product will be processed during the RSTLICPGM processing.
Depending on the version of IBM Director Agent you are installing, you can install
IBM Director Agent on i5/OS from either installation media or from a downloaded
installation package.
Table 107. Installation options for IBM Director Agent on i5/OS
Version Installation media Downloaded installation package file
name
5.20 IBM Director for i5/OS, V5.20 dir5.20_agent_i5OS.zip
5.20 Update 1 not available dir5.20.1_agent_i5OS.zip
5.20.2 IBM Director for i5/OS, Version 5.20.2 dir5.20.2_agent_i5OS.zip
If the version of IBM Director Agent you are installing is available on installation
media for i5/OS, use these instructions to install IBM Director Agent on i5/OS.
Important:
If you are upgrading from a previous version of IBM Director Agent, migration of
the product will be processed during the RSTLICPGM processing.
To install IBM Director Agent using RSTLICPGM, complete the following steps:
1. Log on to the System i platform by using a profile with the following
privileges: *ALLOBJ and *SECADM.
2. Insert the CD into the CD-ROM drive.
3. Run RSTLICPGM.
4. In the Product field, type the product number for IBM Director Agent
(5722DA1).
5. In the Device field, type the optical device identifier, for example, opt01.
6. Press Enter. The installation progress for IBM Director Agent is displayed.
Important:
v IBM Director Server includes all the functionality of IBM Director Agent. It is
not possible or necessary to separately install IBM Director Agent on the
management server after installing IBM Director Server. Any IBM Director tasks
requiring IBM Director Agent will be performed for systems with IBM Director
Server installed.
v The version of IBM Director Agent cannot be later than the version of IBM
Director Server running on the management system.
v If IBM Director Console and IBM Director Agent are installed on the same
system, both software components must be at the same release level as IBM
Director Server.
If you are upgrading from a previous version of IBM Director Agent, migration of
the product will be processed during the RSTLICPGM processing.
To install IBM Director Agent using RSTLICPGM, complete the following steps:
1. On a system that can connect to the i5/OS system, download the installation
package from the IBM Director Web site at www.ibm.com/systems/
management/director/.
2. Extract the contents of the installation package into a local directory.
3. Log on to the System i platform by using a profile with the following
privileges: *ALLOBJ and *SECADM.
250 IBM Director Planning, Installation, and Configuration Guide
4. On the i5/OS system, type the following command and press Enter to create a
save file for the SAVDA100MM.sav file:
CRTSAVF FILE(QGPL/SAVDA100MM)
5. From the directory into which you extracted the contents of the downloaded
installation package, start an FTP session to the i5/OS system and then type
the following commands, pressing Enter after each:
binary
put FILES/SAVDA100MM.sav /qsys.lib/qgpl.lib/SAVDA100MM.file
6. If a previous version of IBM Director Agent is installed and running, stop IBM
Director Agent by typing the following command from a command prompt
and pressing Enter:
QSH CMD(’/qibm/userdata/director/bin/twgend’)
7. Verify that IBM Director Agent has been stopped by typing the following
command from a command prompt and pressing Enter:
QSH CMD(’/qibm/userdata/director/bin/twgstat’)
8. On the i5/OS system, type the following command and press Enter to install
the upgrade:
RSTLICPGM LICPGM(5722DA1) DEV(*SAVF) SAVF(QGPL/SAVDA100MM)
9. Installing IBM Director Agent when not in restricted state should also start it.
Otherwise, start IBM Director Agent by typing the following command from a
command prompt and pressing Enter:
QSH CMD(’/qibm/userdata/director/bin/twgstart’)
10. Verify that the status for IBM Director Agent is Active. Type the following
command from a command prompt and press Enter:
QSH CMD(’/qibm/userdata/director/bin/twgstat’)
11. To delete the SAVDA100MM.sav file, type the following command and press
Enter:
DLTF FILE(QGPL/SAVDA100MM)
Important:
v IBM Director Server includes all the functionality of IBM Director Agent. It is
not possible or necessary to separately install IBM Director Agent on the
management server after installing IBM Director Server. Any IBM Director tasks
requiring IBM Director Agent will be performed for systems with IBM Director
Server installed.
v The version of IBM Director Agent cannot be later than the version of IBM
Director Server running on the management system.
v If IBM Director Console and IBM Director Agent are installed on the same
system, both software components must be at the same release level as IBM
Director Server.
Depending on the version of IBM Director Agent you are installing, you can install
IBM Director Agent on Linux for System x from either installation media or from a
downloaded installation package.
dir5.20.2_System_x.iso
1. To start the installation from a Web download, perform the following steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
b. To extract the contents of the installation package, type the following
command:
tar -xvf install_package
where dev/cdrom is the specific device file for the block device and
mnt/cdrom is the mount point of the drive.
c. Change to the directory in which the installation script is located. Type the
following command and press Enter:
cd /mnt/cdrom/director/agent/linux/i386/FILES
After IBM Director Agent is installed, you can enable the Wake on LAN feature.
To enable SNMP Access and Trap Forwarding, you must install and configure
Net-SNMP, version 5.2.1.
Depending on your version of IBM Director, you can install from either installation
media or from a downloaded installation package. Table 109 on page 254 lists the
sources of installation code.
The IBM Director for Linux on System z CDs are available as ISO images from
ShopzSeries at www.ibm.com/software/ShopzSeries and from the IBM Director
download Web page at www.ibm.com/systems/management/director/
downloads.html. The IBM Director Agents & Consoles (1 of 2) CDs are available as
ISO images from ShopzSeries at www.ibm.com/software/ShopzSeries. The
installation package files are available from the IBM Director download Web page
at www.ibm.com/systems/management/director/downloads.html.
Important:
v IBM Director Server includes all the functionality of IBM Director Agent. It is
not possible or necessary to separately install IBM Director Agent on the
management server after installing IBM Director Server. Any IBM Director tasks
requiring IBM Director Agent will be performed for systems with IBM Director
Server installed.
v The version of IBM Director Agent cannot be later than the version of IBM
Director Server running on the management system.
v If IBM Director Console and IBM Director Agent are installed on the same
system, both software components must be at the same release level as IBM
Director Server.
To enable SNMP Access and Trap Forwarding, you must install and configure
Net-SNMP. Use the version that is included in your distribution.
To install IBM Director Agent on Linux for System z, complete the following steps:
1. If you install from installation media, make the installation code available to
your Linux system.
2. If you install from a downloaded installation package, extract the installation
files to a local directory on your Linux system.
3. From a terminal session on your Linux system, change to the directory in
which the installation script is located. Type the following command and press
Enter:
cd /mnt/director/agent/linux/s390/FILES/
where /mnt is the mount point of the file system on the CD or the path to the
directory to which you have extracted the IBM Director installation files.
4. If you want to customize the installation, go to step 5 on page 255. If you
want to accept the default settings for the installation, type the following
command and press Enter:
./dirversion_agent_linz.sh
Important:
v IBM Director Server includes all the functionality of IBM Director Agent. It is
not possible or necessary to separately install IBM Director Agent on the
management server after installing IBM Director Server. Any IBM Director tasks
requiring IBM Director Agent will be performed for systems with IBM Director
Server installed.
v The version of IBM Director Agent cannot be later than the version of IBM
Director Server running on the management system.
v If IBM Director Console and IBM Director Agent are installed on the same
system, both software components must be at the same release level as IBM
Director Server.
Depending on the version of IBM Director Agent you are installing, you can install
IBM Director Agent on Linux on POWER from either installation media or from a
downloaded installation package.
1. To install IBM Director Agent from a Web download, perform the following
steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
b. To unzip and extract the contents of the installation package, type the
following command:
gzip -cd install_package | tar -xvf -
where directory is the local directory into which you extracted the files.
d. Go to step 3.
2. To start the installation from the CD, perform the following steps:
a. Insert the CD into the CD-ROM drive.
b. If the CD does not automount, type the following command and press
Enter:
mount /dev/cdrom /mnt/cdrom
where dev/cdrom is the specific device file for the block device and
mnt/cdrom is the mount point of the drive.
c. Change to the directory in which the installation script is located. Type the
following command and press Enter:
cd /mnt/cdrom/director/agent/linux/ppc/FILES
where mnt/cdrom is the mount point of the drive. Remove the CD from the
drive.
After IBM Director Agent is installed, you can enable the Wake on LAN feature.
IBM Director 5.20 support for systems running Linux for Intel Itanium (64 bit) is
provided by IBM Director Agent version 5.10.3. There is no IBM Director Agent
version 5.20 for Intel Itanium systems. To install Level 2: IBM Director Agent on
system running Linux for Intel Itanium (64 bit), complete the following steps:
1. Download the dir5.10.3_agent_linux64.tar package from the IBM Director Web
site at www.ibm.com/systems/management/director/.
2. Extract the dir5.10.3_agent_linux64.tar file into a local directory.
Go to step 8.
4. To customize the installation, copy the response file (diragent.rsp) to a local
directory. Type the following command and press Enter:
cp diragent.rsp /directory
where directory is the local directory to which you copied the response file, and
response.rsp is the name of the response file saved in step 6.
8. To start IBM Director Agent, type the following command and press Enter:
install_root/bin/twgstart
After IBM Director Agent is installed, you can enable the Wake on LAN feature.
To enable SNMP Access and Trap Forwarding, you must install and configure
Net-SNMP, version 5.2.1.
Notes:
1. (System x servers only) Install the MPA Agent only if the server has one of the
following service processors installed:
v Advanced System Management processor
v Advanced System Management PCI adapter
v Remote Supervisor Adapter
v Remote Supervisor Adapter II
2. To install Level 2: IBM Director Agent, you must log on to the NetWare server
from a Windows workstation running the NetWare Client for Windows. The
SYS volume must be mapped as a drive to the system running Windows. Also,
you must have administrator or supervisor access on the NetWare server.
To install Level 2: IBM Director Agent on NetWare, complete the following steps:
1. Download the dir5.20_agent_netware.zip from the IBM Director Support Web
site at www.ibm.com/systems/management/director/.
2. Extract the contents of the dir5.20_agent_netware.zip file to the Windows
workstation running NetWare Client for Windows.
Note: If you disable the TCPIP (all adapters) setting and enable an individual
device driver on a system with multiple network adapters, IBM Director
Agent will receive only those data packets that are addressed to the individual
adapter.
14. To start IBM Director Agent, type the following command and press Enter:
load twgipc
IBM Director Agent will start automatically whenever the server running NetWare
starts.
Important:
v IBM Director Server includes all the functionality of IBM Director Agent. It is
not possible or necessary to separately install IBM Director Agent on the
management server after installing IBM Director Server. Any IBM Director tasks
requiring IBM Director Agent will be performed for systems with IBM Director
Server installed.
v The version of IBM Director Agent cannot be later than the version of IBM
Director Server running on the management system.
After preparing your 32-bit Windows system, you can use the InstallShield wizard
to install IBM Director Agent.
Depending on the version of IBM Director Agent you are installing, you can install
IBM Director Agent on Windows from either installation media or from a
downloaded installation package.
Table 111. Installation options for IBM Director Agent on Windows
Version Installation media Downloaded installation package file
name
5.20 IBM Director on x86, V5.20 CD dir5.20_agent_windows.zip
dir5.20.2_System_x.iso
Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on
the system, it is installed during the IBM Director Agent installation. If the
upgrade is necessary, the system prompts you to restart following the installation
of IBM Director Agent without specifying that MSI was installed. Unless you
install using the response file and set the RebootIfRequired parameter to N, you are
prompted to restart whether or not the IBM Director Agent installation is
completed successfully.
This parameter updates MSI and runs the installation program in administrative
mode. Restart the system if prompted to do so.
To install Level 2 : IBM Director Agent on 32-bit Windows using the InstallShield
wizard, complete the following steps:
1. To start the installation from a Web download, perform the following steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
b. Use the unzip command to extract the contents of the installation package
to a temporary directory.
c. Click Start → Run.
d. In the Open field, type one of the following commands and press Enter:
v 5.20: \directory\FILES\dir5.20_agent_windows.exe
where e is the drive letter of the drive. The installation program starts, and
the IBM Director Setup window opens.
d. Click Install IBM Director Agent. The Welcome to the InstallShield
Wizard for IBM Director Agent window opens.
e. Go to step 4 on page 262.
Accessibility note: Screen readers might not process the IBM Director Setup
window correctly. To start the installation wizard for IBM Director Agent
using the keyboard, perform the following steps:
a. Close the IBM Director Setup window.
b. Open Windows Explorer.
c. Browse to the \director\agent\windows\i386\FILES directory on the IBM
Director on x86 CD.
d. Run one of the following programs:
v 5.20: dir5.20_agent_windows.exe
v 5.20 Update 1: dir5.20.1_agent_windows.exe
v 5.20.2: dir5.20.2_agent_windows.exe
The Welcome to the InstallShield Wizard for IBM Director Agent window
opens.
e. Go to step 4 on page 262.
After preparing your 32-bit Windows system, you can use a response file to
perform an unattended installation of Level 2:IBM Director Agent. The response
file that you create can be employed on supported systems in your environment to
install IBM Director Agent.
Depending on the version of IBM Director Agent you are installing, you can install
IBM Director Agent on Windows from either installation media or from a
downloaded installation package.
Table 112. Installation options for IBM Director Agent on Windows
Version Installation media Downloaded installation package file
name
5.20 IBM Director on x86, V5.20 CD dir5.20_agent_windows.zip
dir5.20.2_System_x.iso
Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on
the system, it is installed during the IBM Director Agent installation. If the
upgrade is necessary, the system prompts you to restart following the installation
of IBM Director Agent without specifying that MSI was installed. Unless you
install using the response file and set the RebootIfRequired parameter to N, you are
prompted to restart whether or not the IBM Director Agent installation is
completed successfully.
To use a response file to install Level 2: IBM Director Agent on 32-bit Windows,
complete the following steps:
1. To start the installation from a Web download, perform the following steps:
a. Download the installation package from the IBM Director Downloads Web
Site at www.ibm.com/systems/management/director/downloads.html.
b. Use the unzip command to extract the contents of the installation package
to a temporary directory.
c. Copy the response file (\directory\FILES\diragent.rsp) to a new location,
where directory is the local directory into which you extracted the files.
d. Go to step 3.
2. To start the installation from a CD, perform the following steps:
a. Insert the CD into the CD-ROM drive.
b. If the installation program starts automatically and the IBM Director Setup
window opens, close it.
c. Copy the response file (\director\agent\windows\i386\FILES\diragent.rsp)
to a local directory.
d. Go to step 3.
3. Open the copy of the diragent.rsp file in an ASCII text editor.
4. Modify and save the response file with a new file name. This file follows the
Windows INI file format and is fully commented.
5. Click Start → Run.
6. In the Open field, type one of the following commands and press Enter:
v 5.20: \directory\FILES\dir5.20_agent_windows.exe /s /
a installationtype rsp="responsefile.rsp" option
v 5.20 Update 1: \directory\FILES\dir5.20.1_agent_windows.exe /s /
a installationtype rsp="responsefile.rsp" option
v 5.20.2: \directory\FILES\dir5.20.2_agent_windows.exe /s /
a installationtype rsp="responsefile.rsp" option
where:
v directory is either the local directory into which you extracted the files from
a web download, or the following path on the CD media:
\director\agent\windows\i386\.
7. If you set the RebootIfRequired parameter to Y in the response file, reboot the
system if prompted to do so.
8. If you installed IBM Director Agent from the CD, remove the CD from the
drive.
IBM Director 5.20 support for Intel Itanium systems running 64-bit Windows is
provided by IBM Director Agent version 5.10.3. There is no IBM Director Agent
version 5.20 for Intel Itanium systems running 64-bit Windows. IBM Director Agent
for Intel Itanium systems running 64-bit Windows is available as a Web-download
only. Download the dir5.10.3_agent_windows64.zip file from the IBM Web site at
www.ibm.com/systems/management/director/.
The wizard can be used in a standard interactive mode, or you can perform an
unattended installation using a response file to provide answers to the questions
that the wizard poses.
Note: If Microsoft Windows Installer (MSI), version 3.0 or later is not installed on
the system, it is installed during the IBM Director Agent installation. If the
upgrade is necessary, the system prompts you to restart following the installation
of IBM Director Agent without specifying that Microsoft Windows Installer was
installed. Unless you install using the response file and set the RebootIfRequired
parameter to N, you are prompted to restart whether or not the IBM Director Agent
installation is completed successfully.
Installing Level 2: IBM Director Agent on 64-bit Windows (Intel Itanium only)
using the InstallShield:
After preparing your 64-bit Windows system, you can use the InstallShield wizard
to install IBM Director Agent.
IBM Director 5.20 support for Intel Itanium systems running 64-bit Windows is
provided by IBM Director Agent version 5.10.3. There is no IBM Director Agent
version 5.20 for Intel Itanium systems running 64-bit Windows. To use InstallShield
to install Level 2: IBM Director Agent on an Intel Itanium system running 64-bit
Windows, complete the following steps:
1. Download the dir5.10.3_agent_windows64.zip file from the IBM Director
Support Web site at www.ibm.com/systems/management/director/.
2. Extract the contents of the dir5.10.3_agent_windows64.zip file into a local
directory.
3. Locate the dir5.10.3_agent_windows64.exe file. This file is in the
directory\FILES directory, where directory is the local directory into which you
extracted the contents of the dir5.10.3_agent_windows64.zip file.
4. Double-click the dir5.10.3_agent_windows64.exe file. The InstallShield wizard
starts, and the Welcome to the InstallShield Wizard for IBM Director Agent
window opens.
5. Click Next. The License Agreement window opens.
6. Click I accept the terms in the license agreement and click Next. The Feature
and Installation Directory Selection window opens.
Level 2: IBM Director Agent is selected automatically for installation; a
hard-disk-drive icon is displayed to the left of the component.
7. A red X is displayed to the left of IBM Director Remote Control Agent,
which is optional. The IBM Director Remote Control Agent enables a system
administrator to perform remote desktop functions on the management server.
To install IBM Director Remote Control Agent, click the red X to the left of the
feature name. A menu opens. Click either This feature will be installed on
local hard drive or This feature, and all subfeatures, will be installed on
local hard drive.
8. Click Next. The Security Settings window opens.
9. The Secure – IBM Director Server must request access to manage this
system check box is selected by default. This setting ensures that IBM Director
Server cannot manage this system until it is granted access.
10. Optional: Add a comma-separated list of IBM Director servers that you want
IBM Director Agent to announce itself to in the Add Known Server Address
field. The format for this field is <protocol>::<address>, for example,
TCPIP::10.3.1.4, TCPIP::192.168-1.10.
11. Click Next. The Software Distribution Settings window opens.
12. To select an alternative location for the storage of software-distribution
packages before they are applied to IBM Director Agent, click Change and
select another directory.
13. Click Next. The Ready to Install the Program window opens.
14. Click Install. The Installing IBM Director Agent window opens.
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.
After preparing your 64-bit Windows system, you can use a response file to
perform an unattended installation of Level 2:IBM Director Agent. The response
file that you create can be employed on supported systems in your environment to
install IBM Director Agent.
IBM Director 5.20 support for Intel Itanium systems running 64-bit Windows is
provided by IBM Director Agent version 5.10.3. There is no IBM Director Agent
version 5.20 for Intel Itanium systems running 64-bit Windows. To use a response
where:
v /s is an optional parameter that suppresses all file extraction windows.
v installationtype is one of the following commands:
– unattended shows the progress of the installation but does not require any
user input.
– silent suppresses all output to the screen during installation.
v responsefile.rsp is the path and name of the response file that you created in
step 5.
v option is one of the following optional parameters:
Table 114. Optional installation parameters
Parameter What it does
waitforme Ensures that dir5.10.3_agent_windows64.exe process will not
end until the installation of IBM Director Agent is completed
debug Logs all messages that are sent by the Microsoft Windows
Installer log engine, including status and information
messages
log=logfilename Specifies the fully qualified name of an alternative log file
verbose Enables verbose logging
8. If you set the RebootIfRequired parameter to Y in the response file, reboot the
system if prompted to do so.
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.
Dir5.20_LinuxonPower.tar.gz
Dir5.20.1_Agent_Console_LinuxonPower.tar.gz
5.20.2 IBM Director for Linux on POWER, Version 5.20.2 /director/agent/linux/ppc/META-INF/
dir5.20.2_agent_linppc.xml
Dir5.20.2_Agent_Console_LinuxonPower.tar.gz
IBM Director Agent on Linux for System z
5.20 IBM Director for Linux on System z, V5.20 /director/agent/linux/s390/META-INF/
dir5.20_agent_linz.xml
IBM Director Agents & Consoles, V5.20 (1 of 2)
5.20.1 dir5.20.1_agent-agent-linux-s390.tar /director/agent/linux/s390/META-INF/
dir5.20.1_agent_linz.xml
5.20.2 dir5.20.2_agent-agent-linux-s390.tar /director/agent/linux/s390/META-INF/
dir5.20.2_agent_linz.xml
IBM Director Agent on Windows (32-bit)
5.20 IBM Director on x86, V5.20 \director\agent\windows\i386\META-INF\
dir5.20_agent_windows.xml
IBM Director Agents & Consoles, V5.20 (1 of 2)
dir5.20_agent_windows.zip \META-INF\dir5.20_agent_windows.xml
5.20.1 IBM Director on x86, Version 5.20 Update 1 \director\agent\windows\i386\META-INF\
dir5.20.1_agent_windows.xml
dir5.20.1_agent_windows.zip \META-INF\dir5.20.1_agent_windows.xml
5.20.2 IBM Director on x86, Version 5.20.2 \director\agent\windows\i386\META-INF\
dir5.20.2_agent_windows.xml
dir5.20.2_agent_windows.zip \META-INF\dir5.20.2_agent_windows.xml
IBM Director Agent on 64-bit Intel Itanium
Note: IBM Director 5.20 and higher support for Intel Itanium systems is provided by IBM Director Agent version
5.10.3.
Linux dir5.10.3_agent_linux64.tar /META/INF/dir5.10.3_agent_linux64.xml
Windows dir5.10.3_agent_windows64.zip \META-INF\dir5.10.3_agent_windows64.xml
LM78 and SMBus device drivers for Linux on System x
Notes:
v To install the IBM LM78 or SMBus device driver using the Software Distribution task, you first must build the
binary RPM file and copy it to the same directory as the software distribution package descriptor file.
v See “Preparing to manage service processors with IBM Director” and “Installing IBM LM78 and SMBus device
drivers for Linux” for information about these drivers.
5.20 dir5.20_lm78_linux.tar.gz lm78driver_linux.xml
dir5.20_smbus_linux.tar.gz smbdriver_linux.xml
5.20.1 dir5.20.1_lm78_linux.tar.gz lm78driver_linux.xml
dir5.20.1_smbus_linux.tar.gz smbdriver_linux.xml
5.20.2 dir5.20.2_lm78_linux.tar.gz lm78driver_linux.xml
dir5.20.2_smbus_linux.tar.gz smbdriver_linux.xml
Related tasks
You can create a software package for installing or upgrading IBM Director Agent
or installing IBM Director Core Services.
Figure 14. Creating a software package: Software Distribution Manager window (Standard
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 271.
After you create a software package, you can use the Software Distribution task to
remotely install the package on supported systems.
To use the Software Distribution task to install a software package, complete the
following steps:
1. Start IBM Director Console.
2. In the Tasks pane, expand the Software Distribution task.
3. Click the software package that you want to distribute. Then, drag it into the
Group Contents pane and drop it onto the icon that is displayed for the system
on which you want to install the software package. A window opens.
272 IBM Director Planning, Installation, and Configuration Guide
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.
Notes:
1. You cannot use this procedure to uninstall the MPA Agent. However, you can
use this procedure to add it to an existing IBM Director Agent installation.
2. To modify an IBM Director Agent installation, you must log on to the NetWare
server from a Windows workstation running the NetWare Client for Windows.
3. The SYS volume must be mapped as a drive to the system running Windows.
4. You must have administrator or supervisor access on the NetWare server.
6. Click the drive that is mapped to the SYS volume on the NetWare server;
then, click Next. The Select Components window opens.
Figure 17. Modifying IBM Director Agent on NetWare: Select Components window
You can add or remove an IBM Director feature from a system that is running
Linux.
You can remove an IBM Director feature from a system that is running Linux.
To remove a feature from IBM Director Server, IBM Director Console or IBM
Director Agent, complete the following steps:
1. Modify the diruninstall script, which is in located in the installation directory.
By default, this script removes all detected IBM Director components. To
uninstall specific components, you must set the SmartUninstall setting to 0 and
then make the other modifications.
2. Save the modified uninstallation script.
3. To stop IBM Director Agent, from a command prompt, type the following
command and press Enter:
install_root/bin/twgstop
Before beginning any upgrade, consult the release notes for version-specific
compatibility information and special upgrade instructions.
The following general rules apply to the version compatibility of IBM Director
components:
v 5.20 Update 1 and later: You cannot upgrade IBM Director components on
Linux on System z directly from a version prior to 5.20 to a version later than
Complete the following steps to back up IBM Director persistent data on the
management server before upgrading or updating IBM Director Server.
1. Shut down IBM Director Server. Type one of the following commands,
depending on the operating system of the management server:
Note: If you do not want to back up the software package information for
software distribution, issue the -s option with the twgsave command.
The IBM Director persistent data is saved to the following directory/save file:
where install_root is the root directory of your IBM Director installation. The
variable n is an integer starting at 1 that is incremented each time the twgsave
command is run.
The persistent data includes configuration and working IBM Director data. It
does not include database information.
3. If you have the Capacity Manager extension installed, back up your Capacity
Manager data. When you update IBM Director, you also need to update
Capacity Manager. See “Preparing to update Capacity Manager” in the IBM
Director Capacity Manager Installation and User’s Guide for more information.
4. Back up your security keys. See “Key information and management” in the
IBM Director Systems Management Guide for more information.
5. Back up your dynamic group definitions. See “Exporting a dynamic group” in
the IBM Director Systems Management Guide for more information.
6. Back up your BladeCenter configuration profiles. See “Exporting a profile to an
XML file” in the IBM Director Systems Management Guide for more information.
7. Back up your event action plans. See “Exporting an event action plan” in the
IBM Director Systems Management Guide for more information.
8. Optional: If you have an external database for IBM Director, back up the
database using the instructions provided for your database.
9. Optional: If you have customized any files in the IBM Director environment,
such as icons, resources, or extensions written with the IBM Director SDK, back
up the customized files.
Notes:
1. After upgrading IBM Director Server, you might be required to upgrade any
IBM Director extensions that are installed. Make sure that you read the release
notes for any extensions that are on your management server prior to
upgrading.
2. If you use Software Distribution Premium Edition and your software reverts to
Software Distribution Standard Edition after you update IBM Director, you
need to reinstall Software Distribution Premium Edition.
To upgrade IBM Director, follow the steps for a new installation, including any
planning and environment preparation that might be necessary. When you install
the latest IBM Director software, the features from your previous installation are
automatically selected.
If you are running one of the following versions of IBM Director on a supported
operating system, you can upgrade to IBM Director 5.20 or later.
Important: Some operating systems or hardware that were supported for older
versions of IBM Director are not supported in later versions. To successfully
upgrade, your existing IBM Director component must be running on an operating
system and hardware configuration that is supported by the version of IBM
Director to which you are upgrading.
Versions of IBM Director that are earlier than IBM Director 4.10 are not compatible
with IBM Director version 5.20 or later. If you are running a version of IBM
Director that is earlier than IBM Director 4.10, you can perform one of the
following operations:
v Uninstall your existing IBM Director installation and then install IBM Director
version 5.20 or later.
v Upgrade your existing IBM Director installation to version 4.10 or later. Then,
upgrade to IBM Director version 5.20 or later.
Note: Always read the release notes before beginning any installation or upgrade
procedure.
1. Linux only: On Linux management servers, you must manually stop IBM
Director Server before installing a new version of IBM Director Server. At a
command prompt, type the following command and then press Enter:
install_root/bin/twgstop
To upgrade IBM Director Console, follow the general installation instructions for
your operating system.
Important: If the system that you are upgrading has IBM Director Console and
IBM Director Agent installed, consider the following information:
v To upgrade both IBM Director Console and IBM Director Agent at the same
time, use the IBM Director Console installation software.
v (System x only) To upgrade both IBM Director Console and IBM Director Agent
at the same time, use the IBM Director Console installation software that is
provided at the IBM Director Web site: www.ibm.com/systems/management/
director/. If you use the IBM Director Console installation software that is
provided on the CD, the installation process will detect and uninstall any
previous version of IBM Director Agent, and upgrade only IBM Director
Console.
Important: If the system that you are upgrading has IBM Director Console and
IBM Director Agent installed, consider the following information:
v To upgrade both IBM Director Console and IBM Director Agent at the same
time, use the IBM Director Console installation software.
v (System x only) To upgrade both IBM Director Console and IBM Director Agent
at the same time, use the IBM Director Console installation software that is
provided at the IBM Director Web site: www.ibm.com/systems/management/
director/. If you use the IBM Director Console installation software that is
provided on the CD, the installation process will detect and uninstall any
previous version of IBM Director Agent, and upgrade only IBM Director
Console.
You can use the IBM Director Software Distribution task to upgrade IBM Director
Agent on managed systems running AIX, i5/OS, Windows (32-bit and 64-bit), or
Linux (32-bit and 64-bit).
The zip files on the IBM Director Agent CDs contain the different agent packages
that can be imported using IBM Director Software Distribution. These are based on
the operating system and hardware on which you intend on to install the
packages.
Note: The file names listed below are English XML files. Files for other supported
languages are appended with the appropriate language identifier. For example,
dir5.20_agent_aix_packagedIU_de.zip is the German file.
Dir5.20_LinuxonPower.tar.gz
5.20.1 IBM Director for Linux on POWER, /director/agent/linux/ppc/
Version 5.20 Update 1 dir5.20.1_agent_linux_ppc_packagedIU.zip
Dir5.20.1_Agent_Console_LinuxonPower.tar.gz
IBM Director Core Services on Linux on POWER
5.20 IBM Director for Linux on POWER, V5.20 CD /coresvcs/agent/linux/ppc/
cs5.20_agent_linux_ppc_packagedIU.zip
IBM Director Agents & Consoles, V5.20 (1 of 2) CD
Dir5.20_LinuxonPower.tar.gz
5.20.1 IBM Director for Linux on POWER, /coresvcs/agent/linux/ppc/
Version 5.20 Update 1 cs5.20.1_agent_linux_ppc_packagedIU.zip
Dir5.20.1_Agent_Console_LinuxonPower.tar.gz
You can create a software package for installing or upgrading IBM Director Agent
or installing IBM Director Core Services.
Figure 19. Creating a software package: Software Distribution Manager window (Standard
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 284.
After you create a software package, you can use the Software Distribution task to
remotely install the package on supported systems.
To use the Software Distribution task to install a software package, complete the
following steps:
1. Start IBM Director Console.
2. In the Tasks pane, expand the Software Distribution task.
3. Click the software package that you want to distribute. Then, drag it into the
Group Contents pane and drop it onto the icon that is displayed for the system
on which you want to install the software package. A window opens.
Chapter 3. Installing 285
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.
Much of the CIMOM data is dynamically derived from the system on which the
CIMOM runs and does not need migration. Migrate a CIMOM repository if you
want to preserve the certificate or if you are using CIM instrumentation that
maintains static data in the CIMOM repository. If you decide to perform a
migration of the CIMOM repository, perform the migration immediately after the
upgrade of your IBM Director component, to ensure that the migrated data is
current.
You can perform the migration either manually or automatically, as the final step
of installing the new release.
Note:
v Always perform the migration manually if you want to include CIM
instrumentation other than what is installed with IBM Director.
v For migrating the CIMOM repository of a z/VM manageability access point, see
the z/VM Center upgrade information in the IBM Director z/VM Center
Installation and User’s Guide.
Complete the following steps to manually migrate the CIMOM repository after you
have installed the new version of your IBM Director component and any
additional CIM instrumentation you might require:
As part of the migration the new CIMOM repository is backed up. If a problem
occurs during the migration, the new CIMOM repository is automatically restored
to its state before the migration.
IBM might offer new releases or updates to this version of IBM Director.
v If you purchased IBM Director, see the IBM Director Web site at
www.ibm.com/systems/management/director/ for information about new
releases.
v If you received IBM Director with your IBM BladeCenter product or xSeries
server, see your hardware documentation for information about updating IBM
Director. Also, the IBM eServer xSeries Subscription Services, which allows you
to receive updates automatically, is available; for more information about this
service, contact your IBM representative.
Important:
v The data that you restore must be from the same version of IBM Director Server,
running on a management server with the same operating system.
v This process is not recommended for cloning multiple copies of IBM Director
Server configuration data to management servers that will interact in the same
management environment. Using multiple instances of IBM Director Server with
cloned configuration data in the same management environment could cause
event duplication and problems with event monitoring thresholds.
As a best practice, always back up your IBM Director Server before upgrading or
making major changes to your management server. In the event that a
complication occurs during an upgrade, if you have backed up your IBM Director
data, you can revert to your previous version of IBM Director and restore your
previous data.
To restore IBM Director persistent data on the management server, complete the
following steps:
1. Shut down IBM Director Server. Type one of the following commands,
depending on the operating system of the management server:
where directory is the directory where the persistent data was backed up. The
IBM Director persistent data is restored to the original file locations.
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.
User and user group administration can only be performed by members of the
superuser group. The name of the IBM Director superuser group is different on
each supported operating system:
v AIX or Linux: dirsuper
v i5/OS: QIBM_QDIR_SUPER_ADM_PRIVILEGES (function usage group)
v Windows: DirSuper
IBM Director users are based on user accounts on the operating system of the
management server or a Lightweight Directory Access Protocol (LDAP) server.
User access to managed objects and tasks in IBM Director is based on user group
membership, but individual user access authority can be granted or revoked in
addition to the authority defined for the user group.
There are two general methodologies for changing user access to tasks and
managed objects in IBM Director:
configure user groups based on roles
Strongly recommended for organizations where more than a few users are
authorized for IBM Director, implementing a group policy means that user
authority is exclusively defined by membership in user groups. You define
user groups that correspond to roles for task and managed-object authority,
and add or remove users from the appropriate user groups. This
methodology has several advantages:
v You can apply authority changes for multiple users at once by changing
the authority for particular groups.
v You can identify lists of users with particular authority based on their
group membership.
v You can remove user access by removing the user from all authorized
user groups.
modify individual users
For organizations where only a few users are authorized for IBM Director,
it can be simpler to manage users on an individual basis than to define
authority exclusively by group membership.
The following steps outline the general procedure for managing users and user
groups in IBM Director.
1. LDAP authentication only: Enable LDAP authentication and configure the
LDAP properties in IBM Director.
2. Create user groups on the management server or LDAP server that correspond
to roles you have defined for IBM Director users, and authorize the user groups
for IBM Director.
3. Modify authority for the user groups.
4. Create user accounts on the management server or LDAP server.
5. Add the user accounts to the appropriate user groups.
6. Optional: Modify authority for individual user accounts.
To remove user access, remove the user account from all user groups which are
authorized for IBM Director.
6. Specify the LDAP authentication method being used by the LDAP server. Set
the ldap.auth.mechanism property to one of the following values:
simple
anonymous
DIGEST-MD5
7. Set the ldap.enabled property to true. You might have to add the
ldap.enabled property to the dirldap.properties file.
8. Optional: Modify other properties in the dirldap.properties file as needed.
These properties are described in Appendix C, “Lightweight Directory Access
Protocol authentication properties for IBM Director Server,” on page 379.
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.
The names of the administrator and superuser groups are different on each
supported operating system.
Using only the default administrator and superuser groups poses the following
possible security risks:
v Because root users and Windows administrators have the same authority as the
administrator group, adding authority to the administrator group could grant
authority to users who do not need this authority. To better manage user
authority in IBM Director, you should keep the default user authority for the
administrator group (no task access, no managed object access).
To manage user authority in IBM Director, therefore, you should create one or
more user groups in addition to the administrator and superuser groups. Because
individual user authority can be configured only for members of the administrator
group, the user groups you create should correspond with a set of user authorities
you wish to assign to members of the group.
1. These might be based on what kind of managed objects the user will manage,
where the objects are located, or what tasks the user will be able to perform.
2. On the management server or on a Lightweight Directory Access Protocol
(LDAP) server, create user groups that correspond to the user authority sets
you need.
Tip: Since all members of authorized user groups share authority in IBM
Director, you should create user groups which are used only for IBM Director.
One way to identify these groups is to use a common prefix in the group name.
Refer to your operating system documentation, or the documentation for your
LDAP server, for instructions on creating user groups.
3. Authorize the user groups for IBM Director. From a command line, issue the
dircli authusrgp command. The syntax depends on whether the user group
exists on the management server or on an LDAP server.
v To authorize a user group that exists on the management server: Issue the
following command from a command prompt.
dircli authusrgp name=groupname type=local
where groupname is the name of a user group on the LDAP server, and
optional_keys refers to optional LDAP keys described in the “authusrgp”
reference. These keys can specify additional LDAP properties, such as the
LDAP host name and port. These properties can also be configured in the
dirldap.properties file.
The user groups are created and are granted access to IBM Director, but initially
the user groups have no authority to access managed objects or perform tasks.
For example, you might create the following user groups to correspond with both
managed-object access authority and task authority.
v ibmdir_albany v ibmdir_edit_prefs
v ibmdir_mumbai v ibmdir_dircli
v ibmdir_timbuktu v ibmdir_remote_control
v ibmdir_storage_dev v ibmdir_hardware_status
v ibmdir_aix_sys
v ibmdir_windows_sys
With authority correctly configured for these groups, you could authorize a user to
check the hardware status of servers running AIX in Mumbai, India by adding that
user to the groups ibmdir_mumbai, ibmdir_aix_sys, and ibmdir_hardware_status.
After creating and authorizing user groups, you need to configure the authority for
each user group, and then add users.
Changing authority for a user group using the dircli chusrgp command:
You can use the dircli chusrgp command at a command prompt on all
management servers to modify the authority for authorized user groups.
Note: The results from each of these commands include both the name and the
hexadecimal identifier of the privileges, managed-object groups, or tasks. You
can use either the name or hexadecimal identifier when granting or denying
access by the user group.
2. Optional: To list the authorized user groups, issue the following command:
dircli lsusrgp
3. To edit privileges for a user group, issue the following command:
dircli chusrgp -P privilege_list -N mo_group_list -T task_list usergroup
where:
v privilege_list is a comma-delimited list of privileges which are assigned to
members of the user group.
v mo_group_list is a comma-delimited list of managed-object groups which
members of the the user group can access.
v task_list is a comma-delimited list of tasks which members of the user
group can perform.
v usergroup is the user group you are editing.
Notes:
a. If the name of a task, managed-object group, or privilege includes a space
character, you must enclose the name in quotation marks.
b. You can use the keywords all or none, in place of a list of privileges,
managed-object groups, or tasks, to specify all or none of the available
privileges, managed-object groups, or tasks.
Examples
Two examples of editing user groups using the dircli chusrgp command follow.
Changing authority for a user group using IBM Director Console on Windows:
Note: This does not prevent users from creating new tasks, if they are
otherwise authorized to do so.
7. When you have finished editing the authority, click OK in the Group Editor
window, and then close the User Administration window.
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.
Authorize each user profile to the function usage groups that correspond to the
authority needed for the user role.
v In the i5/OS user interface: Type the following command:
CHGFCNUSG FCNID(functionid) USER(name) USAGE(*ALLOWED)
where functionid is one of the function usage groups listed in Table 117 on page
299, and name is the name of the user profile to be authorized.
Note: IBM Director is shipped with the user profile QCPMGTDIR. This profile has
*ALLOBJ, *IOSYSCFG, *JOBCTL, *SAVSYS and *SECADM special authorities, is
used to start all IBM Director jobs, and is the default profile under which the jobs
run. QCPMGTDIR is the default user profile for the following function usage
groups:
v QIBM_QDIR_AGENT_DEFAULT_USER
v QIBM_QDIR_SERVER_DEFAULT_USER
v QIBM_QDIR_AGENT_RUN_AS_USER (only on Level-2 managed systems with
IBM Director Agent installed)
v QIBM_QDIR_SERVER_RUN_AS_USER
If these function usage groups are changed to a user profile other than
QCPMGTDIR, any tasks that require more authority than the user profile that is
specified will fail. Also, if you change the IBM Director Agent default user,
anonymous command execution can occur on the given i5/OS managed system.
Related information
There are two alternative procedures for changing authority for a member of the
IBM Director administrator group.
Changing authority for a member of the administrator group using the dircli
chusr command:
You can use the dircli chusr command at a command prompt on all management
servers to modify the authority for a member of the IBM Director administrator
group.
Important: This task can only be performed for user accounts that are members of
the IBM Director administrator group. The name of the administrator group is
different on each supported operating system:
v AIX or Linux: diradmin
v i5/OS: QIBM_QDIR_ADMINISTRATOR
v Windows: DirAdmin
For other users, the available privileges, tasks, and managed-object groups are
determined exclusively by the user groups of which the user is a member.
Note: The results from each of these commands include both the name and the
hexadecimal identifier of the privileges, managed-object groups, or tasks. You
can use either the name or hexadecimal identifier when granting or denying
access by the user group.
2. Optional: To list user accounts that are members of the IBM Director
administrator group, issue the following command:
dircli lsusr
3. To edit authority for a user, issue the following command:
dircli chusr -P privilege_list -N mo_group_list -T task_list user
where:
v privilege_list is a comma-delimited list of privileges which are assigned to
the user.
v mo_group_list is a comma-delimited list of managed-object groups which the
user can access.
v task_list is a comma-delimited list of tasks which the user can perform.
v user is the user you are editing.
Notes:
a. If the name of a task, managed-object group, or privilege includes a space
character, you must enclose the name in quotation marks.
b. You can use the keywords all or none, in place of a list of privileges,
managed-object groups, or tasks, to specify all or none of the available
privileges, managed-object groups, or tasks.
Examples
Changing authority for a member of the administrator group using IBM Director
Console on Windows:
For management servers running Windows, you can use IBM Director Console to
modify a user’s access to tasks and managed objects.
Important: This task can only be performed for user accounts that are members of
the IBM Director administrator group. The name of the administrator group is
different on each supported operating system:
v AIX or Linux: diradmin
v i5/OS: QIBM_QDIR_ADMINISTRATOR
v Windows: DirAdmin
For other users, the available privileges, tasks, and managed-object groups are
determined exclusively by the user groups of which the user is a member.
Note: To select or clear the Event Action Plan Wizard task, expand Event
Action Plans → Event Action Plan Builder → Event Action Plan Wizard.
To prevent the user from accessing tasks that the user has created, select the
Deny user access to new tasks created by this user check box.
Important: This task can only be performed for user accounts that are members of
the IBM Director administrator group. The name of the administrator group is
different on each supported operating system:
v AIX or Linux: diradmin
v i5/OS: QIBM_QDIR_ADMINISTRATOR
v Windows: DirAdmin
Root users and Windows administrators have the same privileges as the
administrator group, whether or not the user actually belongs to this group.
To list other authorized IBM Director users, list the user groups which are
authorized for IBM Director, and then use the commands provided by the
operating system for listing the members of those user groups.
v To list all users that are members of the administrator group with no attribute
information, issue the following command from a command prompt.
dircli lsusr
v To list details for a particular user specified by user_id, issue the following
command from a command prompt.
dircli lsusr -l user_id
The general procedure for deauthorizing users in IBM Director is the reverse of the
procedure for adding users:
1. Remove the user account from all user groups that are authorized to access
IBM Director Server. Refer to your operating system documentation, or the
documentation for your LDAP server, for instructions on deleting user groups.
Note: Root users and Windows administrators will continue to have the same
authority in IBM Director as members of the IBM Director administrators
group.
2. To deauthorize a root user or Windows administrator, you must also remove
the user account on the operating system on which the account is defined.
Optionally, you can also remove user accounts for deauthorized IBM Director
users that are not root users or Windows administrators. Refer to your
operating system documentation, or the documentation for your LDAP server,
for instructions on deleting user accounts.
You can change the default authority for IBM Director user IDs in the
administrators group. The User Defaults Editor allows you to change the user
privileges, group access limits, and task access limits for all members of the
administrators group. These defaults affect only members of the administrators
group; they do not limit the attributes of members of the super administrators
group.
Note: Authority that is set for a specific user or group overrides defaults that are
set in the User Defaults Editor.
Note: Authority that is set for a specific user or group override defaults that are
set in the User Defaults Editor.
Complete the following steps to change the defaults for IBM Director user IDs that
are members of the administrators group:
1. In IBM Director Console, click Options → User Administration.
2. In the User Administration window, click Actions → User defaults.
Note: To select or clear the Event Action Plan Wizard task, expand Event
Action Plans → Event Action Plan Builder → Event Action Plan Wizard.
To prevent the user from accessing tasks that the user has created, select the
Deny user access to new tasks created by this user check box.
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.
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.
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.
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
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.
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.
Option Description
Disabled IBM Director Server does not automatically discover managed
systems. This value is the default.
1 - 168 IBM Director Server automatically discovers managed systems
every n hours, where n is the selected number.
5. Specify how often IBM Director Server checks the online status of each
managed object. Select one of the available values for Presence Check period
(minutes).
Option Description
Disabled IBM Director Server does not check the online status of managed
objects of this type.
1 - 240 IBM Director Server attempts to contact managed objects of this
type every n minutes, where n is the selected number. The
default value is 15.
6. Click OK.
7. Optional: To start discovery of Level-0 managed systems now, click Tasks →
Discover → Level 0: Agentless Systems. Otherwise, IBM Director Server will
automatically discover Level-0 managed systems periodically as configured in
the Discovery Preferences window.
Note: Discovery is a background process; you will not see any confirmation
that discovery is occurring until managed objects are displayed in IBM Director
Console. Discovery of managed systems can take minutes or hours, depending
on a number of factors, including the number of IP addresses being queried,
the availability of the target networks, the presence check interval that is set for
managed systems, and other operations being performed on the management
server.
4. Specify how long IBM Director Server will wait for a response after sending a
discovery query before timing out. Type a value for Maximum wait time in
seconds. If no value is specified, IBM Director Server will wait 15 seconds.
5. Specify how often IBM Director Server will attempt to discover new managed
systems. Select one of the available values for Auto-discover period (hours).
Option Description
Disabled IBM Director Server does not automatically discover managed
systems. This value is the default.
1 - 168 IBM Director Server automatically discovers managed systems
every n hours, where n is the selected number.
6. Click OK.
7. Optional: To start discovery of Level-1 managed systems now, click Tasks →
Discover → Level 1: IBM Director Core Services Systems. Otherwise, IBM
Director Server will automatically discover Level-1 managed systems
periodically as configured in the Discovery Preferences window.
Note: Discovery is a background process; you will not see any confirmation
that discovery is occurring until managed objects are displayed in IBM Director
Console. Discovery of managed systems can take minutes or hours, depending
on a number of factors, including the number of IP addresses being queried,
Option Description
Disabled IBM Director Server does not automatically discover managed
systems. This value is the default.
1 - 168 IBM Director Server automatically discovers managed systems
every n hours, where n is the selected number.
5. Specify how often IBM Director Server checks the online status of each
managed object. Select one of the available values for Presence Check period
(minutes).
Option Description
Disabled IBM Director Server does not check the online status of
managed objects of this type.
1 - 240 IBM Director Server attempts to contact managed objects of this
type every n minutes, where n is the selected number. The
default value is 15.
6. Select the Automatically secure unsecured systems check box to ensure that
IBM Director Server automatically secures any unsecured managed systems
that it discovers. When this feature is enabled, IBM Director Server prevents
future management servers from managing the managed systems without first
requesting access.
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.
Chapter 3. Installing 311
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.
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:
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.
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).
5. Specify a template for naming physical platforms 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 %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.
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.
Complete the following steps to configure discovery preferences for SMI-S storage
devices:
1. In IBM Director Console, click Options → Discovery Preferences.
2. Click the SMI-S Storage Devices tab.
3. Specify how often IBM Director Server will attempt to discover new managed
systems. Select one of the available values for Auto-discover period (hours).
Option Description
Disabled IBM Director Server does not automatically discover managed
systems. This value is the default.
1 - 168 IBM Director Server automatically discovers managed systems
every n hours, where n is the selected number.
4. Specify how often IBM Director Server checks the online status of each
managed object. Select one of the available values for Presence Check period
(minutes).
Option Description
Disabled IBM Director Server does not check the online status of
managed objects of this type.
1 - 240 IBM Director Server attempts to contact managed objects of this
type every n minutes, where n is the selected number. The
default value is 15.
5. Under Service Location Protocol (SLP) Profiles, select the SLP profiles that
IBM Director Server will discover. The default values are SNIA:Array and
SNIA:Switch.
Discovery
method Steps
Use Service 1. Specify one or more SLP directory agent servers to use. The
Location selected SLP directory agents are displayed in the Predefined
Protocol (SLP) directory agent servers list box.
directory 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 network address 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 Director Server will use only the directory agents for
discovery.
2. Select the Use multicast check box.
7. Specify how long IBM Director Server will wait for a response after sending a
discovery query before timing out. Type a value for Maximum wait time in
seconds. If no value is specified, IBM Director Server will wait 15 seconds.
8. Specify how often IBM Director Server will attempt to discover new managed
systems. Select one of the available values for Auto-discover period (hours).
Option Description
Disabled IBM Director Server does not automatically discover managed
systems. This value is the default.
1 - 168 IBM Director Server automatically discovers managed systems
every n hours, where n is the selected number.
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 %MANUFACTURER_ID%
v %HARDWARE_TYPE_MODEL%
v %HARDWARE_SERIAL_NUMBER%
v %IPADDRESSES%
v %ENDPOINT%
v %NAME%
By default, this naming template is set to the following value:
%MANUFACTURER_ID% %HARDWARE_TYPE_MODEL%
%ENDPOINT%
10. Click OK.
11. Optional: To start discovery of SMI-S storage devices now, click Tasks →
Discover → SMI-S Storage Devices. Otherwise, IBM Director Server will
automatically discover SMI-S storage devices periodically as configured in the
Discovery Preferences window.
Note: Discovery is a background process; you will not see any confirmation
that discovery is occurring until managed objects are displayed in IBM
Director Console. Discovery of managed systems can take minutes or hours,
depending on a number of factors, including the number of IP addresses being
queried, the availability of the target networks, the presence check interval
that is set for managed systems, and other operations being performed on the
management server.
Complete the following steps to configure discovery preferences for SNMP devices:
1. In IBM Director Console, click Options → Discovery Preferences.
2. Click the SNMP Devices tab.
3. Configure seed addresses for SNMP discovery. You can specify multiple IP
addresses; the addresses are searched concurrently. By default, the IP address
of the management server is added to this list. This device should be an
SNMP device. If the IBM Director Server is on a system that is not running
SNMP, then the address of the device that is not running SNMP in SNMP
discovery preferences will not help for this IBM Director Server’s discovery of
SNMP. To optimize the chance of discovering all SNMP devices, be sure to
specify the IP addresses for routers and DNS servers that are SNMP devices.
During the discovery operation, IBM Director Server,
iso.org.dod.internet.mgmt.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.
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.
Option Description
Disabled IBM Director Server does not automatically discover managed
systems. This value is the default.
1 - 168 IBM Director Server automatically discovers managed systems
every n hours, where n is the selected number.
8. Specify how often IBM Director Server checks the online status of each
managed object. Select one of the available values for Presence Check period
(minutes).
Option Description
Disabled IBM Director Server does not check the online status of
managed objects of this type.
1 - 240 IBM Director Server attempts to contact managed objects of this
type every n minutes, where n is the selected number. The
default value is 15.
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.
z/VM discovery preferences can be configured only if the z/VM Center extension
for IBM Director is installed. The extension must be installed on both IBM Director
Server and any remote instances of IBM Director Console.
Discovery
method Steps
Use Service 1. Specify one or more SLP directory agent servers to use. The
Location selected SLP directory agents are displayed in the Predefined
Protocol (SLP) directory agent servers list box.
directory 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 network address 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 Director Server will use only the directory agents for
discovery.
2. Select the Use multicast check box.
4. Specify how long IBM Director Server will wait for a response after sending a
discovery query before timing out. Type a value for Maximum wait time in
seconds. If no value is specified, IBM Director Server will wait 15 seconds.
5. Specify how often IBM Director Server will attempt to discover new managed
systems. Select one of the available values for Auto-discover period (hours).
Option Description
Disabled IBM Director Server does not automatically discover managed
systems. This value is the default.
1 - 168 IBM Director Server automatically discovers managed systems
every n hours, where n is the selected number.
6. Specify how often IBM Director Server checks the online status of each
managed object. Select one of the available values for Presence Check period
(minutes).
Option Description
Disabled IBM Director Server does not check the online status of managed
objects of this type.
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.
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.
4. Specify how long IBM Director Server will wait for a response after sending a
discovery query before timing out. Type a value for Maximum wait time in
seconds. If no value is specified, IBM Director Server will wait 15 seconds.
5. Specify how often IBM Director Server will attempt to discover new managed
systems. Select one of the available values for Auto-discover period (hours).
Option Description
Disabled IBM Director Server does not automatically discover managed
systems. This value is the default.
1 - 168 IBM Director Server automatically discovers managed systems
every n hours, where n is the selected number.
6. Specify how often IBM Director Server checks the online status of each
managed object. Select one of the available values for Presence Check period
(minutes).
Option Description
Disabled IBM Director Server does not check the online status of managed
objects of this type.
1 - 240 IBM Director Server attempts to contact managed objects of this
type every n minutes, where n is the selected number. The
default value is 15.
7. Click OK.
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.
Discovery
method Steps
Use Service 1. Specify one or more SLP directory agent servers to use. The
Location selected SLP directory agents are displayed in the Predefined
Protocol (SLP) directory agent servers list box.
directory 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 network address 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.
4. Specify how long IBM Director Server will wait for a response after sending a
discovery query before timing out. Type a value for Maximum wait time in
seconds. If no value is specified, IBM Director Server will wait 15 seconds.
5. Click OK.
6. Optional: To start discovery of Flexible Service Processors now, click Tasks →
Discover → FSP. Otherwise, IBM Director Server will automatically discover
Flexible Service Processors 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.
4. Specify how long IBM Director Server will wait for a response after sending a
discovery query before timing out. Type a value for Maximum wait time in
seconds. If no value is specified, IBM Director Server will wait 15 seconds.
5. Click OK.
6. Optional: To start discovery of Integrated Virtualization Managers now, click
Tasks → Discover → IVM. Otherwise, IBM Director Server will automatically
discover Integrated Virtualization Managers 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.
Note: Customers who are not familiar with IBM Tivoli System Automation for
Multiplatforms should read the Introduction and Getting started chapters of the
IBM Tivoli System Automation for Multiplatforms Base Component Administrator’s and
User’s Guide. These chapters include a policy example which is similar to the
configuration required for IBM Director. This guide and other documentation for
IBM Tivoli System Automation for Multiplatforms can be downloaded from
publib.boulder.ibm.com/tividd/td/
IBMTivoliSystemAutomationforMultiplatforms2.2.html.
1. Configure two management servers on which to install IBM Director Server.
v Both servers should have synchronized passwords and user IDs, possibly via
an authentication service such as LDAP or Active Directory.
v Both servers should have identical NIC configurations.
2. Define a single floating IP address to use as the IP for IBM Director Server.
Method Steps
Create a network 1. Create a network share.
share to use as
2. Use IBM Tivoli System Automation to create an active/stand-by
the IBM Director
cluster for the system exporting the network share to ensure it is
Server data
not a single point of failure.
directory.
3. Make the disk highly available using RAID or another mirroring
technique, such as Peer-to-Peer Remote Copy (PPRC) or Distributed
Replicated Block Device (DRBD).
4. Copy the contents of install_root\data from one of the management
servers to the network share, where install_root is the root directory
of your IBM Director installation. Note that this path uses the
backslash (\) to delimit the directory; depending on the system that
you are using, you might be required to enter the path using the
forward slash (/).
5. Mount the network share to install_root\data on both management
servers, where install_root is the root directory of your IBM Director
installation. Note that this path uses the backslash (\) to delimit the
directory; depending on the system that you are using, you might
be required to enter the path using the forward slash (/).
Use a cluster file 1. Make a shared disk device available to both management servers.
system that is
2. Install and configure a cluster file system such as Oracle Cluster File
backed by a
System 2 (OCFS2) or Red Hat’s Global File System (GFS).
RAID and share
the file system 3. Create a cluster file system on the shared disk device.
on both 4. Copy the contents of install_root\data from one of the management
management servers to the cluster file system on the shared disk device, where
servers. install_root is the root directory of your IBM Director installation.
Note that this path uses the backslash (\) to delimit the directory;
depending on the system that you are using, you might be required
to enter the path using the forward slash (/).
5. Mount the cluster file system to install_root\data on both
management servers, where install_root is the root directory of your
IBM Director installation. Note that this path uses the backslash (\)
to delimit the directory; depending on the system that you are
using, you might be required to enter the path using the forward
slash (/).
6. Verify that the file system will mount properly if the system is
restarted.
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.
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.
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.
After installing IBM Director and first performing discovery, all managed objects of
the selected type might not be discovered without performing discovery several
times. To avoid this situation, consider limiting the quantity of managed objects
that you discover at a time.
Note: Discovery is a background process; you will not see any confirmation that
discovery is occurring until managed objects are displayed in IBM Director
Console. Discovery of managed systems can take minutes or 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.
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.
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.
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
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).
To enable SNMP access and trap forwarding on Linux, you must be running one of
the following operating systems:
v Red Hat Linux, version 3.0
v Red Hat Linux, version 4.0
v SUSE Linux Enterprise Server 9 for x86
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.
To enable SNMP access and trap forwarding on AIX, you must be running AIX
version 5.2 or later.
1. With root authority, open the /etc/snmpdv3.conf file in a text editor.
2. Create a community entry for the customized access view. You can create a
new community entry or reuse the default community entry, as in the
following example:
# communityName securityName securityLevel netAddr netMask storageType
COMMUNITY myDirector myDirector noAuthNoPriv 0.0.0.0 0.0.0.0 -
3. Define a security group that includes the community you defined. You can
create a new group entry or reuse the default group entry, as in the following
example:
# groupName securityModel securityName storageType
VACM_GROUP mygroup_v1 SNMPv1 myDirector –
VACM_GROUP mygroup_v2c SNMPv2c myDirector -
Notes:
v Before uninstalling IBM Director, uninstall IBM Director extensions using the
uninstallation instructions provided for the extensions.
v You can retain the configuration data when you uninstall IBM Director. This
enables you to reinstall or upgrade IBM Director and access the saved
configuration data. Should you reinstall, be sure to reinstall IBM Director in the
same location.
To uninstall IBM Director Server using DLTLICPGM, complete the following steps:
1. At an i5/OS command prompt on the system on which IBM Director Server is
installed, type the following command and press Enter;
DLTLICPGM LICPGM(5722DR1)
2. To remove IBM Director user data from the i5/OS management server, delete
the /qibm/userdata/director/ directory by typing the following command:
QSH CMD (’rm -rf /qibm/userdata/director/’)
To uninstall IBM Director Agent using DLTLICPGM, complete the following steps:
1. At an i5/OS command prompt on the system on which IBM Director Agent is
installed, type the following command and press Enter:
DLTLICPGM LICPGM(5722DA1)
2. To remove IBM Director user data from the i5/OS managed system, delete the
/qibm/userdata/director/ directory using the following command:
QSH CMD(’rm -rf /qibm/userdata/director/’)
Notes:
– If you are going to uninstall a specific component, you must stop the
component first.
– (Linux on POWER only) If you did not install IBM Director Core Services you
must remove IBM Director components using standard RPM commands (by
default,IBM Director Core Services is installed when IBM Director Server or
IBM Director Agent is installed).
v You also can uninstall IBM Director on Linux using standard RPM commands or
on AIX using the System Management Interface Tool (SMIT). Consider the
following information:
– Uninstall any IBM Director extensions before uninstalling IBM Director Server,
IBM Director Console, IBM Director Core Services, or IBM Director Agent
– If an IBM Director database is configured, you must delete the tables and
remove the IBM Director database configuration. Perform this task after all
other packages are removed but before uninstalling IBM Director Server. From
a command prompt, type the following command and press Enter:
install_root/bin/uncfgdb
When you uninstall packages on Linux, the following files are retained to make
it possible to restore persistent data:
– /opt/ibm/director.save.1/saveddata.tar
– /etc/ibm/director/twgagent/twgagent.uid
You must uninstall any separately installed IBM Director extensions before
uninstalling IBM Director Server, IBM Director Console, or IBM Director Agent.
The following table contains information about the possible values for option and
directorcomponent.
Table 118. dirunins parameters
Variable Parameter What it does
option debug Logs all messages that are sent by the Windows
Installer log engine, including status and information
messages
deletedata Deletes all configuration data. This parameter must be
used in conjunction with silent or unattended
parameter. For example, dirunins agent unattended
deletedata performs an unattended uninstallation of
IBM Director Agent and deletes IBM Director
configuration data.
log=logfilename Specifies the fully qualified name of an alternative
installation log file
noreboot Suppresses any required restart
silent Suppresses all output to the screen
unattended Shows the progress of the uninstallation but does not
require any user input
verbose Enables verbose logging
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.
When uninstalling IBM Director 5.20 in order to install an earlier version of IBM
Director, make sure to uninstall all instances of IBM Director Core Services. On
managed systems running Microsoft Windows, versions of IBM Director previous
to 5.20 cannot detect whether IBM Director Core Services is installed. As a result,
the pre-5.20 installation will not provide any indication that an IBM Director 5.20
component is present.
Note: Installing pre-5.20 versions of IBM Director, including IBM Director Agent,
IBM Director Console, and IBM Director Server, on a system on which IBM
Director Core Services is installed has the potential to cause problems. Before
installing any pre-5.20 component of IBM Director, use the following procedure to
uninstall IBM Director Core Services.
At a command prompt, type one of the following commands and press Enter.
Complete the following steps to enable Wake on LAN for IBM Director Agent:
1. From a command prompt, stop IBM Director Agent. Type the following
command and press Enter:
/opt/ibm/director/bin/twgstop
2. Open an ASCII text editor and edit the ServiceNodeLocal.properties file. This
file is in the /opt/ibm/director/data directory.
3. Modify the value of ipc.wakeonlan to read as follows:
ipc.wakeonlan=1
4. Save and close the ServiceNodeLocal.properties file.
5. Start IBM Director Agent by typing the following command and pressing Enter:
/opt/ibm/director/bin/twgstart
Note: To determine whether your server supports the Wake on LAN feature, see
your server documentation.
Complete the following steps to install and configure a database after you have
installed IBM Director Server:
1. To stop IBM Director Server, from a command prompt, type the following
command and press Enter:
/opt/ibm/director/bin/twgstop
Complete the following steps to install and configure a database from the
command line after you have installed IBM Director Server:
1. Open the cfgdbcmd.rsp file in an ASCII text editor and modify the settings. The
cfgdbcmd.rsp file is located in the install_root/data directory, where install_root
is the root directory of your IBM Director installation. The cfgdbcmd.rsp file is
a fully commented example file that you can modify.
2. Save the modified file with a new file name.
3. From a command prompt, stop IBM Director Server. Type the following
command and press Enter:
install_root/bin/twgstop
where install_root is the root directory of your IBM Director installation, and
response.rsp is the name of the response file you saved in step 2.
5. When the configuration is completed, restart IBM Director Server. Type
following command and press Enter:
install_root/bin/twgstart
Complete the following steps to configure a database after you have installed IBM
Director Server:
1. Stop IBM Director Server. From a command prompt, type the following
command and press Enter:
net stop twgipc
2. Type the following command and press Enter:
cfgdb
The IBM Director Database Configuration window opens.
3. Follow the instructions on the screen.
For solutions to problems that other customers have encountered, see the IBM
Director customer forum at www.ibm.com/developerworks/forums/
dw_forum.jsp?forum=759&cat=53.
Problem
After upgrading IBM Director Agent from version 5.10.2 or earlier to version 5.20
or later, IBM Director Console shows the managed system as offline.
Resolution
In IBM Director Console, delete the managed system and then rediscover it.
Problem
When installing IBM Director Console on a system running AIX 5.3, the following
superfluous warning message is displayed.
WARNING: File /opt/ibm/director/classes/com/tivioli/twg/softwaredist/TWGFtp.properties
is also owned by fileset IBM.Director.Agent.IBMDirA
Explanation
The ServeRAID Manager extension for IBM Director is always installed on the
same logical or physical drive as IBM Director. If this drive is not the same as the
drive on which the operating system is installed, the ServeRAID Manager task will
not be started.
Instead, attempting to start the ServeRAID Manager task will generate the
following error message:
Task Not Supported
Resolution
Problem
When using a screen reader that does not support Java applications during IBM
Director installation, the reader will probably not be able to read the contents of
the Database Configuration window, because it is a Java-based interface.
Explanation
The Database Configuration window requires a screen reader that supports Java
applications because it is a Java-based interface.
Resolution
Use the following procedure to finish the installation with a non-Java screen
reader:
1. Using your screen reader, find the window whose title bar reads “IBM Director
database configuration”, and press Enter.
2. The screen reader indicates that the next window is the Apache configuration
window. Press Enter again.
3. Finish the installation as directed.
4. After installation is complete and you obtain a Java screen reader, you can
access and change the database configuration settings by entering the following
command in the command prompt window:
cfgdb
When you install IBM Director by using the keyboard functions to navigate, if
High contrast color and Large or Extra Large font settings are enabled, you cannot
move the keyboard focus to the scroll bars in the installation windows.
Also, some components and text do not display in the windows that are displayed
during installation.
Resolution
To access the scroll bars using the keyboard, use the Windows MouseKeys feature.
You can use the MouseKeys feature to move the mouse pointer by using the arrow
keys on the keyboard.
Problem
Do not install Web-based Access 5.10 on a system that has IBM Director 5.20
installed. Web-based Access will install without error, but will overwrite required
5.20 installation files, which will cause errors when you run IBM Director.
Explanation
Some common files used by both Web-based Access and IBM Director are
overwritten when Web-based Access is installed.
Support for Web-based Access is not continued in version 5.20. You can continue to
use existing version 5.10 installations of IBM Director Agent if this function is
needed.
Resolution
If you install Web-based Access after installing IBM Director 5.20 or later, you will
need to uninstall IBM Director and then install IBM Director again.
Problem
DSA is not removed when uninstalling IBM Director Core Services on a managed
system running Red Hat Linux 5.
Resolution
Problem
After installing IBM Director Core Services or IBM Director Agent on a managed
system, the cimlistener service is not running. As a result, events are not sent from
the managed system to IBM Director Server.
This occurs only after installation if the managed system has not been restarted.
Explanation
This is a limitation.
Resolution
After installing IBM Director Core Services or IBM Director Agent, shut down and
restart the managed system. The cimlistener service will be started.
Problem
After upgrading IBM Director Console from version 5.10, 5.10.1, 5.10.2, or 5.10.3 to
version 5.20 or later, the toolbar in IBM Director Console has the default
configuration of buttons. Any customizations that were made using the earlier
version of IBM Director Console are lost.
Explanation
This is a limitation.
Resolution
After upgrading, click Options → Console Preferences, and then click Toolbar
Preferences to configure the toolbar for IBM Director Console.
Problem
After installing IBM Director Agent on a managed system running Windows, some
IBM Director tasks on the managed system do not work. The following tasks are
known to be affected:
v Inventory (firmware information is not collected)
350 IBM Director Planning, Installation, and Configuration Guide
v Network Configuration
v System Accounts
v Other tasks requiring use of the CIMOM on Windows
Explanation
This is a limitation.
Installation of IBM Director Agent updates the PATH environment variable, but
Windows services do not notice the change until the system is restarted.
Resolution
After installing IBM Director Agent on a managed system running Windows, shut
down and restart the managed system.
Problem
After installing IBM Director Core Services on Windows Vista, the following
warnings appear in the Windows application log:
Event ID: 1001
Source: MsiInstaller
Level: Warning
Detection of product ’{B59F55A6-598C-439D-ADB5-EFC57BADD5D9}’,
feature ’CoreServices’ failed during request for component
’{16050694-5833-4FE5-923C-3E4504C26503}’
Event ID: 1004
Source: MsiInstaller
Level: Warning
Detection of product ’{B59F55A6-598C-439D-ADB5-EFC57BADD5D9}’,
feature ’CoreServices’, component ’{63E949F6-03BC-5C40-A01F-
C8B3B9A1E18E}’ failed. The resource ’’ does not exist.
Explanation
This is a limitation. This message does not indicate an actual problem with the
installation of IBM Director Core Services.
Problem
After installing IBM Director Core Services, run the following command:
/opt/ibm/icc/cimom/bin/cimprovider -d -m SCSIDev_Module
Installation troubleshooting
This section provides information about problems and workarounds related to
installing IBM Director.
For additional troubleshooting information, see the IBM Director Release Notes.
Problem
When installing IBM Director Core Services, IBM Director Agent, or IBM Director
Server, the following error message might be generated:
Could not detect rpm supported Linux distribution
Investigation
To correct the problem, install a supported Linux distribution. See the IBM Director
Planning, Installation and Configuration Guide.
Problem
If you install the IBM SMbus or LM78 device driver, a warning message similar to
the following might be recorded in the Bootmsg.log file:
This warning message is generated if the Red Hat Linux kernel was compiled with
versioned symbols enabled. Ignore this message; the device driver loaded and will
operate properly.
Error in the event log: The open procedure for service PerfDisk
This problem affects IBM Director Server. The problem occurs only on servers
running Windows 2000 Server.
Problem
After IBM Director Server is installed, the following error is displayed in the event
log when the server is restarted:
The open procedure for service PerfDisk in the DLL C:\WINNT\System32\perfdisk.dll
has taken longer than the established wait time to be completed.
Investigation
Use the regedit command to modify the following key entry and change the
decimal value to 30000:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
\PerfDisk\Performance key "Open Timeout"
This gives the system enough time to complete the startup task before starting the
PERF counters.
Problem
Investigation
where filename is the name of the IBM Director component installation file.
Note: If the system that is running the administrative installation has a version of
MSI that is earlier than version 3.0, these commands update MSI on that system.
After MSI is updated and the administrative installation is completed, a message is
displayed that you must reboot the system. Be sure to do so.
Problem
During installation of IBM Director Agent, Windows might display the following
blue screen trap:
IRQL_NOT_LESS_OR_EQUAL
Investigation
Problem
After installing IBM Director Server on Windows, any of the following errors
appears in the Windows Event Viewer.
Event ID: 1005
Source: Microsoft-Windows-Perflib
Level: Error
Open procedure procedure_name was not found in the service_name Service
DLL dll_name. The service’s performance data is not available. The first 4
bytes (DWORD) in the data section include an error code.
Event ID: 1008
Source: Microsoft-Windows-Perflib
Level: Error
Service service_name (DLL dll_name) failed the Open procedure. The
service’s performance data is not available. The first 4 bytes (DWORD) in
the data section include an error code.
Event ID: 1010
Source: Microsoft-Windows-Perflib
Note: These errors were observed with the following values for dll_name,
procedure_name, and service_name:
dll_name
emdmgmt.dll
ipsecsvc.dll
pnrpperf.dll
procedure_name
OpenIPSecPerformanceData
service_name
ASP.NET
ASP.NET_64
ASP.NET_64_2.0.50727
Explanation
These errors are caused by Microsoft Windows and are unrelated to the IBM
Director Server installation.
Additional information
Additional information about these errors is available from the Microsoft Web site
at the following addresses:
v support.microsoft.com/kb/226494
v support.microsoft.com/kb/173060
v support.microsoft.com/kb/927229
Problem
After you have installed IBM Director 5.20 (5722-DR1 or 5722-DA1) on a System i
system, you must completely uninstall IBM Director 5.20 before installing the older
version, IBM Director Multiplatform 4.2x (5733-VE1 option 30 or 39).
If attempted, IBM Director 5.20 is disabled and IBM Director Multiplatform 4.2x
does not work (twgstart will fail).
Investigation
Problem
0503-464 installp: The installation has FAILED for the "usr" part
of the following filesets:
IBM.Director.DirectorCimCore 5.10.2.0
Investigation
Check the following possible causes to resolve this problem and complete the
installation:
v Check that all the preparation steps have been completed as described by
“Preparing to install IBM Director Server on a System p server” in the IBM
Director Planning, Installation and Configuration Guide. Complete any skipped
steps and try the installation again.
v Restore the backup of the CIM repository. Complete the following steps:
1. Identify the CIM repository backup you wish to use. List the backups by
typing the following command and pressing Enter:
ls /opt/freeware/cimom/pegasus/etc/repository.backup.*
The final portion of the file name indicates the backup date. Identify the date
of the backup you wish to use.
2. Stop the cimserver. Type the following command and press Enter:
/opt/freeware/cimom/pegasus/bin/cimserver -s
3. Restore the CIM repository using the backup you have selected. Type the
following command and press Enter:
cp -pRh /opt/freeware/cimom/pegasus/etc/repository.backup.date
/opt/freeware/cimom/pegasus/etc/repository
4. Start the installation again.
Problem
Investigation
Do not set the IBM Director Server service startup setting to Automatic. If the IBM
Director Server service is set to Automatic, change the setting to Manual and
restart the management server. To correct the startup setting for the IBM Director
Server service, complete the following steps:
1. From the Windows desktop, click Start → Control Panel.
2. Double-click Administrative Tools.
3. Double-click Services.
4. Right-click the applicable IBM Director Service and select Properties.
5. On the General page, in the Startup type list, select Manual.
Attention: Do not change the default startup settings except for troubleshooting
purposes when working with IBM Technical Support.
Problem
Investigation
Note: Occasionally this command might fail. If it does, type rpm -ef
rpm_name --noscripts where rpm_name is the dependency.
After removing all of the dependencies, run the IBM Director uninstallation
script again.
For Windows and NetWare:
Contact the IBM Technical Support Center for assistance. You must have an
IBM Support Line contract.
Notes:
1. Printable PDFs for the different versions of the IBM Director documentation are
available from the IBM Director Support Web page at www.ibm.com/systems/
management/director/.
2. IBM Director versions 3.1.1 and earlier are no longer supported.
Although participating in the customer forum does not guarantee an answer from
an IBM representative, the forum community does include IBM employees that use
IBM Director. To access the forum you must sign in to the IBM developerWorks®
Web site and create a profile; there is no fee. The IBM Director customer forum
Web page is at www.ibm.com/developerworks/forums/dw_forum.jsp?forum=759
&cat=53.
You can solve many problems without outside assistance by following the
troubleshooting procedures that IBM provides in the online help or in the
publications that are provided with your system and software. The information
that is included with your system also describes the diagnostic tests that you can
perform. Most BladeCenter, System x, and IntelliStation systems, operating
systems, and programs includes information that contains troubleshooting
procedures and explanations of error messages and error codes. If you suspect a
software problem, see the information for the operating system or program.
Use the following Web addresses for the applicable product information.
You can find service information for your IBM products, including supported
options, at www.ibm.com/support/us.
Also, you can find information about IBM Director in the IBM Systems forum at
www.ibm.com/developerworks/forums/dw_forum.jsp?forum=759&cat=53.
System i information
Before you contact IBM for assistance, or append to the customer forum, you
should gather the following information for the affected systems:
v The operating system information for management server and for the managed
objects.
v Whether the failure is intermittent or persistent.
v The last time (or release) that the feature or function worked.
v Any exceptions or error messages that occur.
v The version of IBM Director that is installed. Also note whether it is a new
installation or an upgrade installation. If it is an upgrade installation, note from
which version of IBM Director you upgraded.
v If possible, the steps required to recreate the problem.
Before you contact IBM for assistance, or append to the customer forum, you
should gather the following information for the affected systems.
Note: Frequently, IBM uses information and logs generated by the Dynamic
System Analysis (DSA) program to resolve problems. DSA is available from the
Systems Management Web page at www.ibm.com/servers/eserver/xseries/
systems_management/.
v The machine types of all the affected systems.
v The operating system.
v The BIOS and firmware version levels of the affected systems. If you do not
know this information, you can use Dynamic System Analysis (DSA) to gather
the information for you.
v Whether the failure is intermittent or persistent.
v The last time the feature or function worked.
v Any exceptions or error messages that occur.
v The version of IBM Director that is installed. Also note whether it is a new
installation or an upgrade installation. If it is an upgrade installation, note from
which version of IBM Director you upgraded.
v If possible, the steps required to recreate the problem.
System p information
Before you contact IBM for assistance, or append to the customer forum, you
should gather the applicable information for the affected systems.
For AIX:
v The files containing the redirected output from the following commands:
– oslevel -r
– lslpp -L
– lsdev
– prtconf
– errpt -a
– lsvpd
v The /var/log/dirinst.log file, if you are having an installation problem.
v Whether the failure is intermittent or persistent.
v The last time the feature or function worked.
v Any exceptions or error messages that occur.
v The version of IBM Director that is installed. Also note whether it is a
new installation or an upgrade installation. If it is an upgrade
installation, note from which version of IBM Director you upgraded.
v If possible, the steps required to recreate the problem.
For Linux on POWER
v The files containing the redirected output from the following commands:
– (For Red Hat Linux) cat /etc/redhat-release
– (For SUSE Linux) cat /etc/SuSE-release
– rpm -qa
– lsvpd
v The /var/log/dirinst.log file, if you are having an installation problem.
v Whether the failure is intermittent or persistent.
v The last time the feature or function worked.
v Any exceptions or error messages that occur.
v The version of IBM Director that is installed. Also note whether it is a
new installation or an upgrade installation. If it is an upgrade
installation, note from which version of IBM Director you upgraded.
System z information
Before you contact IBM for assistance, or append to the customer forum, you
should gather the applicable information for the affected systems.
v A detailed description of the problem.
v Any exceptions or error messages that occur.
v If possible, the steps required to recreate the problem.
v Whether the failure is intermittent or persistent.
v The operating system information for the management server and for the
managed objects.
v The version of IBM Director that is installed in each affected system. Also note
whether it is a new installation or an upgrade installation. If it is an upgrade
installation, note from which version of IBM Director you upgraded.
v The /var/log/dirinst.log file, if you are having an installation problem.
v The /var/log/localmessages or any related log file on manageability access
point (MAP) for z/VM.
v The /opt/ibm/director/log/TWGRas.log file on the management server.
Getting fixes
Occasionally, new releases and upgrades are made available from the IBM Support
Web site at www.ibm.com/systems/management/director/. These releases and
upgrades might contain fixes to problems with IBM Director.
If your IBM Director environment has a problem that is not fixed by a new release
or upgrade, contact the IBM Technical Support Center. To do so, you must have
purchased an appropriate support product from IBM.
For information about which products are supported by Support Line in your
country or region, go to www.ibm.com/services/us/its/pdf/
remotesupportxseries.pdf. For more information about Support Line and other IBM
services, go to www.ibm.com/services/us/index.wss, or go to
www.ibm.com/planetwide/ for support telephone numbers. In the U.S. and
Canada, call 1-800-IBM-SERV (1-800-426-7378).
Accessibility features
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 125 on page 367.
v Update Manager uses additional keyboard shortcuts for table navigation. For
more information, see Table 142 on page 372.
Table 119. 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
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.
374 IBM Director Planning, Installation, and Configuration Guide
Related accessibility information
You can view the publications for IBM Director in Adobe Portable Document
Format (PDF) using the Adobe Acrobat Reader. The PDFs are provided on a CD
that is packaged with the product, or you can access them through the IBM
Director Information Center.
See the IBM Accessibility Center at www.ibm.com/able for more information about
the commitment that IBM has to accessibility.
The location in which you install IBM Director is represented in the documentation
as install_root. The examples and procedures in this documentation use the
install_root variable and separate subsequent directories with forward slashes (/).
Make sure that you use the applicable forward or back slash for your operating
system.
When you initially install IBM Director, you can select an alternative directory
other than the default into which IBM Director is installed.
Note: You cannot change the default installation directory when installing on AIX
or i5/OS.
The properties defined in the dirldap.properties file are used as default values for
the dircli authusrgp command.
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 147. 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.
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.
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
Appendix C. Lightweight Directory Access Protocol authentication properties for IBM Director Server 381
382 IBM Director Planning, Installation, and Configuration Guide
Appendix D. Installing Software Distribution Premium Edition
on Linux
You can install Software Distribution Premium Edition on a Linux management
server.
For this command and others in this topic, mnt/cdrom is the mount point of the
CD-ROM drive and dev/cdrom is the specific device file for the CD-ROM block
device.
4. Change to the directory in which the installation script is located. Type one of
the following commands and press Enter.
Option Description
Linux on POWER cd /mnt/cdrom/swdist/server/linux/ppc/
Linux on System x cd /mnt/cdrom/swdist/server/linux/i386/
Linux on System z cd /mnt/cdrom/swdist/server/linux/s390/
Information Value
Selected database application
Server on which database will be installed
Server on which IBM Director Server will be
installed
This information may be used to configure the database using the wizard during
installation, or to set options in a database-configuration response file for use with
the cfgdbcmd command.
Database configuration
attribute Description Value
DbmsApplication The selected database application. One of
the listed values:
v Apache Derby
v DB2
v Microsoft SQL Server
v Oracle
v PostgreSQL
DbmsTcpIpListenerPort The TCP/IP listener port for the database.
One of the following default values, or a
custom value:
v Apache Derby: n/a
v IBM DB2 Universal Database: 5000
v Microsoft SQL Server: 1433
v Oracle: 1521
v PostgreSQL: 5432
DbmsServerName The server name on which the database is
located. Not required for Apache Derby.
DbmsDatabaseName The database name. Not required for
Apache Derby.
DbmsUserId The user ID for the database. Not required
for Apache Derby.
DbmsPassword The password for the database. Not
required for Apache Derby.
h No
Encryption algorithm: h Advanced Encryption Setting
h Triple DES
Software- Location for packages created by
distribution IBM Director Server:
packages
Location for packages received by
IBM Director Server:
Related tasks
“Using IBM Director in a high-availability environment” on page 327
If IBM Director will be used in a high-availability environment, you need to
prepare the environment for IBM Director, and you might need to configure
IBM Director properties for running in high-availability environments.
“Planning IBM Director users and user groups” on page 127
Before deploying IBM Director, you should determine what IBM Director user
roles to define for your organization. In addition, you should determine the
user authentication type that will best meet your needs.
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:
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
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.
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.
IBM Corporation
MW9A/050
5600 Cottle Road
San Jose, CA 95193
U.S.A.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
All statements regarding IBM’s future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
Trademarks
The following terms are trademarks of Netfinity
International Business Machines Corporation in NetView
the United States, other countries, or both: OS/400
IBM POWER
IBM logo Predictive Failure Analysis
AIX pSeries®
Asset ID Redbooks
BladeCenter RETAIN
DB2 S/390
DB2 Universal Database ServeRAID
DS4000 ServerProven
eServer ServicePac
i5/OS SurePOS
IntelliStation System i
iSeries System p
Multiprise System Storage
Notices 391
392 IBM Director Planning, Installation, and Configuration Guide
Glossary
This glossary includes terms and definitions for IBM Director.
To view glossaries for other IBM products, go to Ethernet gateway, while the ASM
www.ibm.com/ibm/terminology. processor retains control of the server.
When used as a gateway service
A processor, the ASM PCI adapter can
communicate with other ASM PCI
accelerator
adapters and ASM processors only.
In a user interface, a key or combination
of keys that invokes an Advanced System Management processor (ASM
application-defined function. processor)
A service processor built into the
Advanced Encryption Standard (AES)
mid-range Netfinity and early xSeries
A data encryption technique that
servers. IBM Director can connect
improved upon and officially replaced the
out-of-band to an ASM processor located
Data Encryption Standard (DES). AES is
on an ASM interconnect; an ASM PCI
sometimes referred to as Rijndael, which
adapter, a Remote Supervisor Adapter, or
is the algorithm on which the standard is
a Remote Supervisor II must serve as the
based.
gateway service processor.
Advanced System Management interconnect
AES See Advanced Encryption Standard.
(ASM interconnect)
A feature of IBM service processors that alert A message or other indication that signals
enables users to connect up to 24 servers an event or an impending event.
to one service processor, thus eliminating
alert forwarding
the need for multiple modems,
A function that ensures that alerts are
telephones, and LAN ports. It provides
sent, even if a managed system
such out-of-band management functions
experiences a catastrophic failure, such as
as system power control,
an operating-system failure.
service-processor event-log management,
firmware updates, alert notification, and alert-forwarding profile
user profile configuration. A profile that specifies where remote
alerts for the service processor should be
Advanced System Management interconnect
sent.
network (ASM interconnect network)
A network of IBM servers created by alert standard format (ASF)
using the ASM interconnect feature. The A specification created by the Distributed
servers are connected through RS-485 Management Task Force (DMTF) that
ports. When servers containing integrated defines remote-control and alerting
system management processors (ISMPs) interfaces that can best serve a client
and ASM processors are connected to an system in an environment that does not
ASM interconnect network, IBM Director have an operating system.
can manage them out-of-band.
anonymous command execution
Advanced System Management PCI adapter Execution of commands on a target
(ASM PCI adapter) system as either system account (for
An IBM service processor that is built into managed systems running Windows) or
the Netfinity 7000 M10 and 8500R servers. root (for managed systems running
It also was available as an option that Linux).
could be installed in a server that
ASF See alert standard format.
contained an ASM processor. When an
ASM PCI adapter is used with an ASM
processor, the ASM PCI adapter acts as an
Glossary 395
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.
Glossary 397
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
Glossary 399
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.
Glossary 401
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.
Index 405
IBM Web sites (continued)
xSeries Systems Management xiii
K managed systems (continued)
distribution preferences,
IBM.Director.DirectorCimCore keyboard 365 configuring 334
troubleshooting 356 keys hardware requirements 67, 68, 69
illustrations files, location of 44 license 129
IBM Director environment 1 origin of, determining 46 preparing
IBM Director software components 2 Korean 98 Windows Vista 178
in-band communication 50 Windows XP 177
definition 49 securing
enabling 50 L IBM Director Agent installation,
ISMPs, limitations 50 Level 1 managed system 3 during 260
MPA Agent, role of 50 Level-1 managed system security states 44
information to provide 361 preparing, for installation 169 management console 5
installation Level-1 managed systems 35 definition 2
default directory 377 Level-2 managed system 4 hardware requirements 67, 68
Windows 353 running Windows 353 license 129
installations Level-2 managed systems 36 management processor
troubleshooting 357 license generating events 122
installing IBM Director Agent 4, 129 Management Processor Assistant Agent
IBM Director Agent IBM Director Console 5, 129 managed system, installing on 258,
using, Software Distribution 268 IBM Director Core Services 3, 129 260
IBM Director Console IBM Director Server 5, 129 NetWare, installing on 258
AIX 221 managed systems 129 management server
Linux for POWER 226 management console 129 choosing 111
Linux for System x 222 management server 129 DB2 database
overview 221 Linux Linux installation 131
IBM Director Core Service installation 352 Windows installation 131
Linux for POWER 235 Linux for POWER definition 1
Windows 237, 239 installing hardware requirements 67, 68, 69
IBM Director Core Services IBM Director Console 226 license 129
using, Software Distribution 241 IBM Director Core Service 235 Software Distribution, installing
IBM Director Server Linux for System x Linux 383
i5/OS 188 installing mass-configuration profiles 36
troubleshooting 356 IBM Director Console 222 Message Browser
InstallShield wizard Linux installation description of 26
IBM Director Agent 260 encryption, enabling 190, 203, 251, Microsoft
IBM Director Console 228 255, 257 Knowledge Base Article
IBM Director Server 210 IBM Director Agent 234, 251, 253, 825236 354
Integrated System Management 255 Microsoft Data Engine 95
Processor 141 IBM Director Console 225 Microsoft Data Engine 2000 132
Intel Itanium IBM Director Server 190, 197, 203 Microsoft SQL Server 95, 132
IBM Director Agent Intel Itanium migration
installing 257 IBM Director Agent 257 CIMOM data 286
Intelligent Platform Management modifying minor events filter 19
Interface 141 adding a feature 276 modifying an IBM Director installation
interim fixes xiii removing a feature 276 AIX installation
interprocess communication, SNMP Access and Trap Wake on LAN, enabling 343
definition 49 Forwarding, enabling 335 Linux installation
Inventory Wake on LAN, enabling 343 adding a feature 276
operating systems, supported 86 starting 234, 251, 253, 255, 257 removing a feature 276
IP address conflicts, troubleshooting 306 uninstalling 339 SNMP Access and Trap
IPMI 141 LM78 device driver 352 Forwarding, enabling 335
IPMI baseboard management controller Wake on LAN, enabling 343
generating events 122 NetWare installation
ISMP 141
alert-forwarding strategies 53
M adding a feature 273
limitations 273
limitations on in-band managed objects Windows installation
communication 50 description of 32 adding a feature 275
event filters 21 Program Maintenance
types 53 window 275
types of 32
J managed system
removing a feature 275
MPA events
Japanese 98 authorizing service processors 53
Java resource bundles 28 request access 327 MS Jet 95
JDBC driver, Oracle Server 138 request access MSDE 95
authorizing 327 MSI
managed systems troubleshooting 353
definition 1
Index 407
security (continued) software distribution (continued) terminology (continued)
user administration (continued) methods (continued) event 122
task access, restricting 294, 300 streaming from management gateway service processor 49
user login 290 server 55 in-band communication 49
security states 44 preferences, configuring 332 interprocess communication 49
Server Configuration Manager upgrading IBM Director Agent managed system 1
operating systems, supported 88 overview 281 management console 2
ServeRAID Manager software package, installing 245, management server 1
installing 348 272, 285 notification 122
limitation 348 Software Distribution out-of-band communication 49
managed system, installing on 258, operating systems, supported 86 resolution 122
266 Software Distribution (Premium Edition) SNMP device 1
Service and Subscription (S&S) 363 installing on the management server update manager 60
service bulletin index 360 Linux 383 threshold event
Service Location Protocol 306 Software Distribution task filter 19
service packs xiii installing IBM Director Agent 268 simple event filter 19
service processor 141 installing IBM Director Core thresholds
Power Management 92 Services 241 event action plans 125
service processors 90 Software Maintenance (SWMA) 363 toolbar
alert-forwarding strategies 53 software packages User Administration 290, 297, 304
communicating with IBM Director creating 243, 271, 284 trademarks 390
Server solving problems 347, 359, 360 Triple DES 48
interprocess communication 49 Spanish 98 troubleshooting
over the ASM interconnect 49 SQL database 95 IBM Director Agent 352, 356
over the LAN 49 SQL Server 2000 Desktop Engine 132 installing 354
communication with IBM Director starting IBM Director Core Services 352
Server 49 programs with event action IBM Director Server 352
description of 49 plans 125 IBM.Director.DirectorCimCore 356
documentation xiii static groups 30 installations 357
generating events 122 Storage installing 356
in-band communication products, supported tasks 94 MSI administrative installation 353
MPA Agent, role of 50 storage devices 57 patch 357
operating system 50 storage events filter 19 steps to take 360
service processor type 50 structure uninstallation 358
managed-object types 53 event action plan 126 upgrade 357
out-of-band communication 51 event filters 126 TWGshare 56
ServicePac 363 subscription services 287
severity levels support
event filters 21
shortcut keys 365
z/VM guest operating systems 117
Support Line 363
U
unattended installations
shortcuts 9 System Accounts
IBM Director Console 230
silent parameter 219, 230, 239, 263, 267 operating systems, supported 86
IBM Director Server 219
simple event filter System Health Monitoring
unattended parameter 219, 230, 239, 263,
definition 19 support for Linux systems 50
267
predefined filters 19 System i
uninstallation
SMBIOS 67 preparing, for installation 148, 164
troubleshooting 358
SMbus device driver 352 system variables
uninstalling IBM Director
SMI-S attributes 57 event filters 21
configuration data, retaining 339
SMI-S storage devices 57
Linux 339
SNMP
NetWare 341
AIX 336
generating events 122
T Windows 340
targeted tasks 29 unknown events filter 19
SNMP Access and Trap Forwarding
tasks untargeted tasks 29
enabling on Linux 335
event action plans 125 update manager
SNMP devices
external 27 definition 60
definition 1
management server support 84 Update Manager
description of 54
Mass Configuration 36 operating systems, supported 86
operating systems, supported 86
operating systems, supported 84 updates, new 287
SNMP traps
performing on multiple groups 30 upgrade 363
event log 54
publishing events 126 migrating CIMOM repository 286
snmpconf utility 335
targeted 29 troubleshooting 357
snmpd.conf file 335
untargeted 29 upgrading
software components (illustration) 2
User Administration 290, 297, 304 IBM Director 278
software distribution
user-defined 27 IBM Director Agent 281
methods
terminology Windows 265
redirected distribution 55
alert 122 IBM Director Console
ASM interconnect network 49 Windows 280
Index 409
410 IBM Director Planning, Installation, and Configuration Guide
Readers’ Comments — We’d Like to Hear from You
IBM Systems
IBM Director
Planning, Installation, and Configuration Guide
Version 5.20
We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,
organization, subject matter, or completeness of this book. The comments you send should pertain to only the
information in this manual or product and the way in which the information is presented.
For technical questions and information about products and prices, please contact your IBM branch office, your
IBM business partner, or your authorized remarketer.
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use
the personal information that you supply to contact you about the issues that you state on this form.
Comments:
If you would like a response from IBM, please fill in the following information:
Name Address
Company or Organization
_ _ _ _ _ _ _Fold
_ _ _and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ _do
_ _not
_ _ staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
_________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape
Cut or Fold
GC30-4163-01 Along Line
Printed in USA
GC30-4163-01