IBM Director Install Guide

IBM Systems
IBM Systems Director for Windows

Planning, Installation, and Configuration Guide
Version 6.1
GI11-8711-01

IBM Systems

Version 6.1
GI11-8711-01
Note
Before using this information and the product it supports, read the information in Notices on
page 147.
Copyright International Business Machines Corporation 1999, 2008.

US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this publication
. . . . . . . . v
Conventions and terminology . . . . . . . . v

Publications and related information . . . . . . v
Web resources . . . . . . . . . . . . . viii
How to send your comments . . . . . . . . ix
Checklist: Installing IBM Systems

Director Server on Windows. . . . . . xi
Checklist: Installing agents on
Windows . . . . . . . . . . . . . xiii
Chapter 1. IBM Systems Director
technical overview . . . . . . . . . . 1
IBM Systems Director components . . . . .
Management server . . . . . . . . .
Common Agent . . . . . . . . . .
Platform Agent . . . . . . . . . .
Agentless-managed systems . . . . . .
Manageable resource types . . . . . . .
Manageable systems . . . . . . . . . .
User interfaces. . . . . . . . . . . .
Base function and extensible plug-ins . . . .
Discovery manager . . . . . . . . .
Status manager . . . . . . . . . .
Configuration manager . . . . . . .
Automation manager . . . . . . . .
Update manager . . . . . . . . . .
Remote access manager . . . . . . .
Virtualization manager . . . . . . .
IBM BladeCenter and System x management
IBM System z management . . . . . .
IBM Power Systems management . . . .
IBM System Storage management . . . .
Additional IBM Systems Director plug-ins .
Upward integration. . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 2
. 3
. 4
. 5
. 5
. 6
. 6
. 7
. 8
. 9
. 9
. 10
. 10
. 11
. 11
. 12
. 12
. 12
. 12
. 13
. 13
. 14
Chapter 2. Planning for IBM Systems

Director . . . . . . . . . . . . . . 17
Hardware and software requirements. . . . . .
Hardware requirements for IBM Systems Director
Supported IBM systems and products . . . .
IBM BladeCenter products . . . . . . . .
Supported storage devices . . . . . . . .
Network requirements. . . . . . . . . .
Security requirements . . . . . . . . . .
Operating system and software requirements . .
IBM Systems Director task support by operating
system and agent levels . . . . . . . . .
IBM Systems Director task support not affected
by operating systems . . . . . . . . . .
IBM Systems Director task support for
BladeCenter products . . . . . . . . . .
Copyright IBM Corp. 1999, 2008
17
17
18
19
20
22
31
31
36
39
40
IBM Systems Director task support for Storage

products . . . . . . . . . . . . . .
National languages supported by IBM Systems
Director . . . . . . . . . . . . . .
Planning to install IBM Systems Director . . . .
Service and support information . . . . . .
Reviewing the environment . . . . . . . .
Version compatibility of IBM Systems Director
version 6.1 components . . . . . . . . .
License information. . . . . . . . . . .
Obtaining licenses for Common Agent . . . .
Choosing the IBM Systems Director Server
installation options . . . . . . . . . . .
Choosing where to install IBM Systems Director
Server . . . . . . . . . . . . . . .
Choosing the IBM Systems Director database
application . . . . . . . . . . . . .
Choosing the management level for managed
systems. . . . . . . . . . . . . . .
Planning for virtual environments . . . . . .
Disaster recovery for IBM Systems Director 6.1 . .
Planning for events . . . . . . . . . . . .
Planning events to be monitored . . . . . .
Planning for event automation plan
implementations . . . . . . . . . . . .
Planning IBM Systems Director security . . . . .
Planning IBM Systems Director users and groups
Planning Secure Sockets Layer configuration on
IBM Systems Director . . . . . . . . . .
Planning password management in IBM Systems
Director . . . . . . . . . . . . . .
41
41
42
42
42
46
47
48
48
48
49
51
53
54
55
55
56
59
59
60
69
Chapter 3. Installing IBM Systems

Director on the management server . . 71
Preparing the management server . . . . . . . 71
Preparing the database application . . . . . 71
Preparing firewalls and proxies for IBM Systems
Director . . . . . . . . . . . . . . 87
Installing firmware and device drivers . . . . 88
Preparing to install IBM Systems Director Server
on Windows . . . . . . . . . . . . . 90
Installing IBM Systems Director on the management
server . . . . . . . . . . . . . . . . 91
Installing IBM Systems Director Server on
Windows . . . . . . . . . . . . . . 91
Configuring the database application after IBM
Systems Director installation . . . . . . . . 101
Configuring IBM Systems Director Server after
installation . . . . . . . . . . . . . . 102
Configuring IBM Systems Director plug-ins and
platforms . . . . . . . . . . . . . . . 103
Configuring the command line interface . . . . 103
Reviewing Microsoft Internet Explorer security
options . . . . . . . . . . . . . . . 105
iii
Logging on to IBM Systems Director Server for the

first time . . . . . . . . . . . . . . . 106
Chapter 4. Preparing agentless

managed systems . . . . . . . . . 109
Preparing to manage a IBM BladeCenter . . . .
Preparing to manage a IBM BladeCenter chassis
using IBM Systems Director Server on a
non-blade server . . . . . . . . . . .
Preparing to manage a IBM BladeCenter chassis
using IBM Systems Director Server on a blade
server . . . . . . . . . . . . . . .
Preparing Windows managed systems . . . . .
Preparing Windows Server 2003 managed
systems . . . . . . . . . . . . . .
Preparing Windows Server 2008 managed
systems . . . . . . . . . . . . . .
Preparing Windows Vista managed systems . .
Preparing Windows XP managed systems . . .
109
109
110
112
112
113
113
117
Chapter 5. Discovering systems and

collecting inventory data . . . . . . 119
Discovery protocols . . . . . . . . .
Discovering systems with system discovery .
System discovery . . . . . . . . .
Performing a system discovery . . . .
Viewing system discovery results. . . .
Accessing a secured system with request access
.
.
.
.
.
.
.
.
.
.
119
120
120
121
122
122
Chapter 6. Installing agents . . . . . 125

Preparing a Platform-Agent managed system. . . 125
Preparing to install Platform Agent on Windows 125
Preparing a Common-Agent managed system . . 126
iv
Obtaining licenses for Common Agent . .

Preparing to install Common Agent on
Windows . . . . . . . . . . . .
Installing agents using the Agent Installation
Wizard . . . . . . . . . . . . .
Installing the LSI MegaRAID provider for
Windows or Linux . . . . . . . . .
Installing the IBM ServeRAID Manager plug-in
files . . . . . . . . . . . . . .
Installing virtualization manager subagents .
Installing virtualization manager subagents
using the installation wizard . . . . .
manually . . . . . . . . . . . .
. 126
. 126
. 127
. 130
.
.
. 132
. 134
. 134
. 135
Chapter 7. Upgrading and migrating

IBM Systems Director . . . . . . . . 137
Manual migration . . . . . . . . . . . .
IBM Systems Director Migration Tool . . . . .
Considerations for the IBM Systems Director
Migration Tool . . . . . . . . . . . .
Migrated data . . . . . . . . . . . .
IBM Systems Director Active Energy Manager
migration. . . . . . . . . . . . . . .
Obtaining and installing the IBM Systems Director
Migration Tool . . . . . . . . . . . . .
Exporting data from IBM Director 5.20 . . . . .
Importing IBM Director 5.20 data into IBM Systems
Director 6.1 . . . . . . . . . . . . . .
137
138
139
140
142
142
143
144
Notices . . . . . . . . . . . . . . 147
Trademarks .
IBM Systems Director for Windows Planning, Installation, and Configuration Guide
. 148

This IBM Systems Director for Windows Planning, Installation, and Configuration
Guide provides information about installing and configuring IBM Systems
Director. In addition to presenting an overview of IBM Systems Director and its
requirements, it covers the following topics:
v
v
v
v
Planning an IBM Systems Director environment

Installing IBM Systems Director
Upgrading from IBM Director 5.20 or earlier to IBM Systems Director 6.1
Configuring IBM Systems Director
It also includes information about IBM Systems Director security and solving
problems you might encounter during installation.
Note: Sometimes, this publication describes a single procedure for accomplishing a
task and refers to the information center for documentation of alternative
procedures.
Conventions and terminology

These notices are designed to highlight key information:
Note: These notices provide important tips, guidance, or advice.
Important: These notices provide information or advice that might help you avoid
inconvenient or difficult situations.
Attention: These notices indicate possible damage to programs, devices, or data.
An attention notice appears before the instruction or situation in which damage
can occur.
Publications and related information

You can view the same content in the IBM Systems Director Information Center as
PDF documents. To view a PDF file, you need Adobe Acrobat Reader, which can
be downloaded for free from the Adobe Web site at www.adobe.com/products/
acrobat/readstep.html.
Information centers and topic collections

v IBM Systems
publib.boulder.ibm.com/infocenter/systems/index.jsp
View the IBM Systems information center which provides integrated
information for multiple IBM Systems products, including operating systems,
hardware, storage, and software. This information center also contains scenarios
to help you use multiple IBM Systems products in the same environment.
v IBM Systems Director
publib.boulder.ibm.com/infocenter/systems/topic/director_6.1/fqm0_main.html
Updated periodically, the IBM Systems Director topic collection contains the
most up-to-date documentation available for IBM Systems Director.
v IBM Systems Director plug-ins
publib.boulder.ibm.com/infocenter/systems/index.jsp
View the IBM Systems information center for information about to install and
use plug-ins that extend the functionality of IBM Systems Director.
v IBM Systems Director Upward Integration Modules (UIMs)
publib.boulder.ibm.com/infocenter/systems/topic/uims/fqs0_main.html
Read the IBM Systems Director Upward Integration Modules (UIM) topic
collection to learn about how to install and use upward integration modules and
management packs that enable non-IBM workgroup and enterprisemanagement products to interpret and display data that is provided by
Common Agent and Platform Agent.
v IBM Systems Director Software Development Kit
publib.boulder.ibm.com/infocenter/dirinfo/toolkit/index.jsp
View the IBM Systems Director Software Development Kit (SDK) information
center to learn about the APIs and CLIs that you can use to extend the
capabilities of IBM Systems Director.
Publications
Release Notes
Provides information about hardware requirements for running IBM
Systems Director components, supported IBM Systems Director hardware,
operating systems, databases, and workgroup and enterprise
systems-management software.
Hardware and Software Support Guide
Provides information about hardware requirements for running IBM
Systems Director components, supported IBM Systems Director hardware,
operating systems, databases, and workgroup and enterprise
systems-management software.
Planning, Installation, and Configuration Guide for AIX
Provides detail instructions to install and configure each component of IBM
Systems Director on system running AIX using the standard installation
option.
Planning, Installation, and Configuration Guide for IBM i
Systems Director on system running IBM i using the Standard installation
option.
Planning, Installation, and Configuration Guide for Linux on Power Systems
Systems Director on system running Linux for Power Systems using the
Standard installation option.
Planning, Installation, and Configuration Guide for Linux on x86
Systems Director on system running Linux for System x using the
Planning, Installation, and Configuration Guide for Linux on System z
Systems Director on system running Linux for System z using the
vi
Planning, Installation, and Configuration Guide for Windows

Systems Director on system running Windows using the Standard
installation option.
Systems Management Guide
Provides detailed instructions for using the Web interface and managing
systems and resources in your environment.
Troubleshooting Guide
Provides information about problems and how to solve them, and
strategies for troubleshooting common problems.
Events Reference
Provides information about IBM Systems Director events, including the
event type, description, severity, and extended attributes.
Commands Reference
Provides detailed information about the systems management
command-line interface (smcli) commands, and other commands that can
be run directly from the command line, including configuring the database,
and starting and stopping IBM Systems Director.
Hardware Command Line Users Guide
Provides information about installing and using the Hardware Command
Line (formerly known as the IBM Management Processor Command-Line
Interface). Command output in this release might vary from command
output in previous releases.
White papers and briefs

ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03006usen/
XBW03006USEN.PDF
This paper provides a detailed overview of the changes in IBM Systems Director
V6.1, including the new Web interface, security features, operating system
agents, integrated plug-ins and additional plug-ins that can be separately
installed.
v Value Proposition for IBM Systems Director
ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03007usen/
XBW03007USEN.PDF
This paper describes the challenges of operational management for enterprise
server installations and the value provided IBM Systems Director.
v Managing IBM Power Servers with IBM Systems Director 6.1
www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH
&appname=STGE_PO_PO_USEN&htmlfid=POW03011USEN
&attachment=POW03011USEN.PDF
Provides information about managing the virtualization and consolidation on
Power systems using IBM Systems Director.
v IBM Systems Director 6.1 Migration Tips
www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH
&appname=STGE_XB_XB_USEN_&htmlfid=XBW03009USEN
&attachment=XBW03009USEN.PDF
Provides information about migrating data when upgrading your environment
from IBM Director V5.20 to IBM Systems Director V6.1.
vii
IBM Redbooks publications

www.ibm.com/redbooks/
You can also search this Web page for documents that focus on IBM Systems
Director and specific IBM hardware; such documents often contain
systems-management material. The following book is available for IBM Systems
Director V6.1:
Implementing IBM Systems Director 6.1
Tip: Be sure to note the date of publication and to determine the version of IBM
Systems Director software to which the Redbooks publication refers.
Web resources
Listed here are the Web sites and information center topics that relate to IBM
Systems Director.
Web sites
www.ibm.com/systems/management/director/
View the IBM Systems Director Web site on ibm.com which provides links to
downloads and documentation for all currently supported versions of IBM
Systems Director.
v IBM Systems Director Downloads
www.ibm.com/systems/management/director/downloads/
View the IBM Systems Director Downloads Web site on ibm.com which provides
links to download code IBM Systems Director, IBM Systems Director plug-ins,
and IBM Systems Director upward integration modules.
v IBM Systems Director Documentation and Resources
www.ibm.com/systems/management/director/resources/
View the IBM Systems Director Documentation and Resources Web site on
ibm.com which provides links to product documentation, redbooks, redpapers,
white papers, and learning modules related to IBM Systems Director, IBM
Systems Director plug-ins, and IBM Systems Director upward integration
modules.
v IBM Systems Director Upward Integration
www.ibm.com/systems/management/director/upward/
View the IBM Systems Director Upward Integration Web site on ibm.com which
provides more information about IBM Systems Director upward integration
modules created by IBM and other companies. IBM Systems Director UIMs
enable third-party workgroup and enterprise systems-management products to
interpret and display data that is provided by IBM Systems Director
Platform-Agent managed system.
v IBM Servers
www.ibm.com/servers/
View the IBM Servers Web site to learn about IBM Systems server and storage
products.
v IBM ServerProven
www.ibm.com/servers/eserver/serverproven/compat/us/
viii
View the IBM ServerProven Web site to learn about hardware compatibility of
IBM System x and BladeCenter systems with IBM applications and
middleware, including IBM Systems Director.
Forums
www.ibm.com/developerworks/forums/forum.jspa?forumID=759
View the IBM Systems Director forum Web site on ibm.com to discuss
product-related issues pertaining to IBM Systems Director, IBM Systems Director
UIMs, and IBM Systems Director extensions. This Web site includes a link for
obtaining the forum using a Rich Site Summary (RSS) feed.
v IBM Systems Director SDK
www.ibm.com/developerworks/forums/dw_esforums.jspa
View the IBM Systems Director SDK forum Web site to discuss issues pertaining
to the IBM Systems Director Software Development Kit (SDK). This Web site
includes a link for obtaining the forum using a Rich Site Summary (RSS) feed.
v IBM Systems
www.ibm.com/developerworks/forums/dw_esforums.jsp
View the IBM Systems forums Web site on ibm.com to learn about various
forums that are available to discuss technology-related and product-related
issues pertaining to IBM Systems hardware and software products. This Web
site includes a link for obtaining the forum using a Rich Site Summary (RSS)
feed.
How to send your comments

Your feedback is important in helping to provide the most accurate and highest
quality information.
If you have any comments about this book or any other IBM Systems Director
publication,
v Go to the IBM Systems Director information center Web site at
publib.boulder.ibm.com/infocenter/systems/topic/director_6.1/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 Systems Director book and
return it by mail, by fax, or by giving it to an IBM representative.
ix
Checklist: Installing IBM Systems Director Server on Windows

Use this checklist to guide you through the installation process.
1 Evaluate your hardware and system configuration.
__ 1.
__ 2.
__ 3.
__ 4.
Check
Check
Check
Check
the
the
the
the
hardware requirements (17).

network requirements (22).
security requirements (31).
supported operating systems (31).
__ 5. Check the supported database applications (35).

2 Plan your installation of IBM Systems Director Server.
__ 1. Review the environment you will manage (42).
__ 2. Review the licensing requirements (47).
__ 3. Choose installation options for IBM Systems Director Server (48).
__ 4. Choose where you will install IBM Systems Director Server (48).
__ 5. Choose a database application to use with IBM Systems Director Server (49).
__ 6. Plan users, groups, and security options for IBM Systems Director Server (59).
3 Prepare the management server.
__ 1. Prepare the database application (71).
__ 2. Prepare firewalls and proxies on the management server (87).
__ 3. Prepare the management server (90).
4 Install IBM Systems Director Server.
__ 1. Install IBM Systems Director Server (91).
__ 2. Configure the database application (101).
5 Log on and configure IBM Systems Director Server.

__ 1. Log in to IBM Systems Director Server (106).
__ 2. Perform some initial configuration of IBM Systems Director Server (102).
xi
xii
Checklist: Installing agents on Windows

Use this checklist to guide you through the installation process.
1 Evaluate your hardware and system configuration.
__ 1. Check the hardware requirements (18).
__ 2. Check the network requirements (22).
__ 3. Check the supported operating systems (31).
__ 4. Check the supported virtualization software (33).
2 Determine what agents you need to install.
__ 1. Review the task support for different management levels (36).
__ 2. Determine the management level you need for your managed systems (51).
__ 3. If you have virtual systems, determine what agents are needed for the virtual
systems (53).
__ 4. Check the version compatibility of the agents you want to install (46).
3 Prepare your managed systems.
__ 1. Prepare all managed systems for discovery and management by IBM Systems
Director (109).
__ 2. Prepare systems for Platform Agent (125).
__ 3. Prepare systems for Common Agent (126).
4 Discover the managed systems.
__ 1. Discover the managed systems on which you will install agents (120).
__ 2. Request access to the managed systems (122).
5 Install the agents.

__ 1. Use the Agent Installation Wizard to deploy agent packages to your managed
systems (127).
__ 2. Install the LSI MegaRAID provider (130).
__ 3. Install virtualization manager subagents (134).
xiii
xiv
Chapter 1. IBM Systems Director technical overview

IBM Systems Director is a platform-management foundation that streamlines the
way you manage physical and virtual systems across a heterogeneous
environment. By using industry standards, IBM Systems Director supports multiple
operating systems and virtualization technologies across IBM and non-IBM x86
platforms.
Through a single user interface, IBM Systems Director provides consistent views
for viewing managed systems, determining how these systems relate to one
another, and identifying their statuses, thus helping to correlate technical resources
with business needs. A set of common tasks included with IBM Systems Director
provides many of the core capabilities required for basic management, which
means instant out-of-the-box business value. These common tasks include
discovery, inventory, configuration, system health, monitoring, updates, event
notification and automation across managed systems.
IBM Systems Directors Web and command-line interfaces provide a consistent
interface focused on driving these common tasks and capabilities:
v Discovering, navigating and visualizing systems on the network with the
detailed inventory and relationships to the other network resources
v Notifying users of problems that occur on system and ability to drill down to
the source of the problem
v Notifying users when systems need updates and distributing and installing
updates on a schedule
v Analyzing real-time data for systems and setting critical thresholds that notify
the administrator of emerging problems
v Configuring settings of a single system and creating a configuration plan that
can apply those settings to multiple systems
v Updating installed plug-ins to add new features and function to the base
capabilities
v Managing the lifecycle of virtual resources
IBM Systems Director is designed to manage simple and complex environments,
with multiple operating systems and platforms, up to 5 000 managed systems. It
supports the management of a variety of IBM and non-IBM hardware driving
common tasks through the following platform management plug-ins and virtual
resources. The systems supported include:
v IBM Power Systems management
HMC, IVM, and VIOS appliances
Power servers, Power blades, and LS41 and QS21 blade servers
AIX, IBM i, and Linux on POWER operating systems
v IBM BladeCenter and System x management
IBM BladeCenter chassis components, such as switch modules and server
blades
System x systems and blade servers
VMWare, Microsoft Virtual Server (MSVS), and Xen virtual servers
Windows and Linux operating systems on System x
v IBM System z management
z/VM hypervisor
Linux on System z operating system installed on z/VM virtual servers
Linux on System z running on a partition without z/VM

v IBM System Storage management
Integrated RIA controller (such as LSI)
Network storage, such as DS3000, DS4000, and DS6000
Storage switches, such as IBM BladeCenter SAS, Brocade, Qlogic, Nortel and
Cisco
IBM Systems Director integrates with robust workgroup and enterprise
management software from IBM (such as Tivoli software), Computer Associates,
Hewlett-Packard, Microsoft, NetIQ, and BMC Software.
IBM Systems Director components

IBM Systems Director includes IBM Systems Director Server and two
operating-system agents: Common Agent and Platform Agent.
IBM Systems Director Server provides a central point of control for aggregating
and managing discovered systems based on a service-oriented architecture. It can
be installed on one or more systems, called management servers. Systems that
connect to the IBM Systems Director Web interface on the management server
through a Web browser are called browser systems.
The operating-system agents serve as the control point for accessing operating
system and host information that might not be accessible through an out-of-band
interface (such as remote supervisor adapter (RSA), Baseboard Management
Control (BMC), and BladeCenter Management Module). These agents run on
operating-system-based and hardware-based endpoints, called systems, that can be
discovered and managed by IBM Systems Director. The level of system
management depends on the agent that is installed on the system: Common Agent
or Platform Agent. Each agent provides a different footprint size, level of
performance, and set of management functions.
IBM Systems Director can discover and manage some systems on which neither of
these operating-system agents is installed, but the level of management is limited.
This figure shows where the IBM Systems Director Server and operating-system
agents are installed in a basic IBM Systems Director environment.
Management server
IBM Systems Director Server installed

Includes:
- IBM Systems Director Server
- IBM Systems Director Web interface
- Command-line Interface
- Common Agent
HTTPS
Browser system
- no IBM Systems Director
Ccode installed
TCP/IP
Various protocols
SNMP devices
Agentless managed systems
Ccode installed
Agentless managed systems

Ccode installed
Cco
Platform managed systems

- Platform Agent installed
on each
Common managed systems

- Common Agent installed
on each
FQM0501-0
Figure 1. Software in an IBM Systems Director environment
Management server
The management server is a system that has IBM Systems Director Server installed.
It provides a central point of control for aggregating and managing discovered
systems based on a service-oriented architecture.
IBM Systems Director Server stores data about discovered systems, their attributes,
and their relationships to other resources in a relational database. You can access
information that is stored in this database even when the managed systems are not
available. IBM Systems Director Server includes a default database, Apache Derby,
although you can choose to use any supported database (including the
high-performance DB2 database).
IBM Systems Director Server includes two interfaces that the system administrator
can use to manage their environment: a Web user interface and a command-line
interface. The system that you use to interact with these interfaces is called the
browser system.
Tip: When you install IBM Systems Director Server, the Common Agent is
installed automatically on that system. The Common Agent provides a rich set of
security, deployment, and management function.
Common Agent
Common Agent provides a rich set of security, deployment, and management
function.
Common Agent is available for all IBM Power Systems, IBM System x, IBM
BladeCenter, IBM System z systems, and some non-IBM systems, when the
system is running a supported operating system.
Notes:
v Systems running AIX require the Common Agent to be installed. These systems
cannot be managed with Platform Agent.
v For a detailed list of operating systems that are supported for Common Agent,
see the Planning information.
Common Agent replaces Level 2: IBM Director Agent version 5.20. IBM Systems
Director supports systems running Level 2: Common Agent and IBM Director
Agent version 5.20.
Common Agent has a single run-time that can be shared by IBM Systems Director
and Tivoli products, such as Tivoli Provisioning Manager, to reduce the agent
footprint, support shared credentials, and drive common services. It is also
supported by other management products that use the IBM Tivoli Common Agent
Services management infrastructure version 1.4.1 or later.
The function available for Common-Agent managed systems varies based on
operating system and hardware, and includes:
v Discover systems
v Collect comprehensive platform and operating system inventory data
v Monitor health and status
v Manage alerts
v Remotely deploy and install Common Agent
v Perform remote access, including transferring files
v Perform power management function
v Additional event support
v Monitor processes and resources, and set critical thresholds send notifications
when triggered
v Manage operating system resources and processes
v Manage updates
Additionally, using Common Agent instead of Platform Agent provides enhanced
scalability through asynchronous system management, reducing the demands on
IBM Systems Director Server. Firewall management is simplified, too, because the
Common Agent requires you to keep fewer ports open.
For a detailed list of function that is supported by Common-Agent managed
systems, see the Planning information.
Note: Throughout the IBM Systems Director documentation, the term Common
Agent (with both words capitalized) refers to the IBM Systems Director Common
Agent, which includes subagents that provide specific management capabilities for
IBM Systems Director. IBM Systems Director can also discover and perform limited
management on other common agents that use the common agent services
architecture and are distributed by other management products such as Tivoli
Provisioning Manager. When referring to these common agents generically,
lowercase text is used.
Platform Agent
Platform Agent is well suited for environments that require a smaller footprint
without sacrificing a high level of manageability. It provides a subset of Common
Agent function used to communicate with and administer the managed systems,
including hardware alerts and status information.
Platform Agent is available for all IBM Power, System x and IBM BladeCenter, and
System z, IBM System Storage systems, and some non-IBM systems.
For IBM i, Platform Agent is part of the Universal Manageability Enablement
(UME) in the base operating system.
Platform Agent is equivalent to Level 1: IBM Director Core Services version 5.20.3.
IBM Systems Director supports systems running IBM Director Core Services
version 5.20.3.
Note: The versioning for Platform Agent might not match the versioning of IBM
Systems Director.
The function available for Platform-Agent managed systems is limited to the
following tasks, and varies based on operating system and hardware.
v Discover systems
v Collect limited platform inventory data
v
v
v
v
v
Monitor health and status

Manage alerts
Remotely deploy and install Common Agent
Perform limited remote access
Perform limited restart capabilities
For a detailed list of function that is supported by Platform-Agent managed

systems, see the Planning information in the information center at.
Agentless-managed systems
IBM Systems Director provides a set of manageability functions for managed
systems that do not have Common Agent or Platform Agent installed. These
Agentless-managed systems are best for environments that require very small
footprints and are used for specific tasks, such as one-time inventory collection,
firmware and driver updates and remote deployment.
Agentless-managed systems must support the Secure Shell (SSH) or Distributed
Component Object Model (DCOM) protocol, or the Simple Network Management
Protocol (SNMP) interface. IBM Systems Director discovers Agentless-managed
systems by verifying the IP addresses on your network and scanning the ports of
those addresses using the SSH or DCOM protocols. By default, IBM Systems
Director uses the range of addresses that are in the IP domain of the management
server. You can discover a specific IP address or range of IP addresses using the
IBM Systems Director Web interface.
When an Agentless-managed system is discovered, it is locked by default. You can
unlock the system by requesting access to it through IBM Systems Director.
Agentless-managed systems are well suited for one-time collection of inventory,
and can be used for updating firmware and drivers, and remotely deploying and
running it via SSH or DCOM services.
Note: No persistent data is stored on Agentless-managed system.
The function available to Agentless-managed systems is limited to the following
tasks, and varies based on operating system and hardware.
v Discover systems
v Collect limited operating-system inventory data
v Remotely deploy and install Common Agent and Platform Agent.
v Perform limited remote access
v Perform limited restart capabilities
For a detailed list of function that is supported by Agentless-managed systems, see
the Planning information in the information center at.
Manageable resource types

A resource is a generic term for anything that IBM Systems Director can manage.
For example, systems, slots, cards, groups, and updates are all resources.
From the Web interface, you can use the Find a Resource task to find resources and
use the Navigate Resources task to view and work with these resources.
Manageable systems
A system is one type of resource that IBM Systems Director manages. It is an
operating-system-based or hardware-based endpoint that has an IP address and
host name and can be discovered and managed by IBM Systems Director. From the
Navigate Resource page in Web interface, you can view the All Systems group to
work with all discovered systems.
Operating-system-based systems (referred to as operating systems) consist of the
operating system image, agent, drivers, applications, and configuration settings.
From the Navigate Resource page in Web interface, you can view the All Operating
Systems group to work with these types of systems.
Hardware-based systems are the physical and virtual systems, such as servers,
virtual servers, storage systems, and network devices. Physical systems can host
multiple operating systems and virtual servers, either by using a dual-boot feature
or by way of a hypervisor. From the Navigate Resource page in Web interface, you
can use the All Systems or Virtualization Systems groups to work with the physical
aspects of a system, determine how many virtual servers a physical system
contains, and determine how many operating systems are running on a physical
system. You can also use the topology map to view the relationship between
systems. To view the topology map view for a system, click Actions > Topology
Perspectives. A submenu of applicable perspectives is displayed.
To view resources associated with a system, click Actions > Related Resources. A
submenu of applicable related resources is displayed.
IBM Systems Director manages these types of systems:
v Blade administrative server
v Boot server
v Cluster
v Fabric
v Farm
v Hardware Management Console
v Management controller
v Operating system
v Print server
v SAN
v Server
v Storage system
v Switch
v System chassis
Virtualization allows you to hide the physical characteristics of your servers to
consolidate servers, optimize resource usage, and improve IT flexibility and
responsiveness. Using virtualization, you can create multiple discoverable virtual
servers from a single physical server or create a single discoverable virtual server
from multiple physical servers. Each virtual server has an independent operating
environment and can have functions or features that are not available in its
underlying physical resources.
Tip: Virtual servers running on IBM systems are often referred to as logical
partitions or virtual machines.
After IBM Systems Director discovers a physical server, it continues the discovery
process to find all associated virtual servers. Each IBM system offers virtualization
technologies to help you consolidate systems, optimize resource utilization, and
improve IT flexibility and responsiveness.
User interfaces
There are several methods for managing an IBM Systems Director environment: a
Web interface and a command-line interface (smcli).
Web interface
You can use the IBM Systems Director Web interface to conduct comprehensive
systems management through a graphical user interface. Data is securely
transferred between the Web browser and Web interface through HTTPS.
The system on which you logged into the IBM Systems Director Web interface is
referred to as the browser system. You log in to the IBM Systems Director through a
supported Web browser using this URL:
http://System_Name:Port_Number/ibm/console
where System_Name is the name of the system on which IBM Systems Director
Server is installed and Port_Number is the first (lower) of two consecutive port
numbers that you specified for the Web server to use. The default ports for the
Web server are 8421 and 8422. If you use port 8422, make sure that you specify
https to indicate a secure port.
IBM Systems Director provide some tasks that start outside of the IBM Systems
Director Web interface. These tasks are launched tasks and are identified on menus
by the Launched tasks icon
When you select a launched task, the task can be displayed in one of the following
ways:
v In another instance of your Web browser. The task provides its own Web
interface.
v As a separate program on your system desktop.
v The IBM Systems Director Launched Tasks program is displayed and opens the
task that you selected.
IBM Systems Director provides some tasks that still require a client-based
application. This application is called the IBM Systems Director Launched Tasks
program. The IBM Systems Director Launched Tasks program can open the
following tasks:
v Event Action Editor (used to create advanced event actions)
v Event Filter Builder (used to create advanced event filters)
v File Transfer
v Command Automation (formerly called Process Management - Tasks)
v Remote Session
v SNMP Browser
v MIB Management
Note: The IBM Systems Director Launched Tasks program is installed
automatically the first time you use a task that requires it. Because the IBM
Systems Director Launched Tasks program opens outside of the IBM Systems
Director Web interface, Java Web Start (JWS) is also provided for installation. For
more information, see Downloading Java Web Start.
Command-line interfaces
You can use the systems management command-line interface interactively using
the smcli utilities. This command-line interface (CLI) is an important primary
interface into IBM Systems Director and can be used either as an efficient way to
accomplish simple tasks directly or as a scriptable framework for automating
functions that are not easily accomplished from a graphical user interface. For
security reasons, the CLI runs only on the management server.
The command-line interface follows the GN/POSIX conventions.
Tips:
v The IBM Systems Director smcli supports most commands that were available in
previous releases through the discontinued dircli utility.
v For security, the CLI runs only on the management server. You can run the CLI
remotely using a remote-access utility, such as secure shell (SSH) or Telnet.
Base function and extensible plug-ins

Base plug-ins in IBM Systems Director provide core function to manage the full
lifecycle of IBM servers, storage, network, and virtual servers. Plug-ins that
provide advanced function or function tailored to a particular environment can be
downloaded and installed on top of IBM Systems Director.
Basic user interface, security, and agent management functions include:

v Finding and viewing resources and resource information, including relationships
and properties
v Organizing logical sets of resources into groups
v Starting, stopping, and scheduling tasks
v Integrating third-party management software and other programs into the IBM
Systems Director Web interface
v Managing auditing
v Encrypting interprocess communication
v Managing Common Agent registration and authentication
v Authenticating users through a configured user registry available from the
operating system, Lightweight Directory Access Protocol (LDAP), or domain
controller
v Creating roles and authorizing users and user groups to access certain systems,
groups, and tasks
v Managing credentials to support single sign-on authentication, even when
services span different systems
v Installing agents on new systems, upgrading from IBM Director Agent version
5.20 or IBM Director Core Services version 5.20 to a current agent on existing
systems, and promote an Agentless-managed system or Platform-Agent
managed system to a Common-Agent managed system.
Discovery manager
Discovery manager performs physical and virtual system discovery and inventory
of related resources on the network..
You can use the discovery manager plug-in to:
v Discover systems such as physical and virtual servers, storage systems, and
network devices) in a heterogeneous environment. This includes simple
discovery using a single IP address or host name or a range of IP addresses. You
can also use a discovery profile to discover one or more systems of different
types and protocols.
v Collect inventory data about hardware and software that is currently installed
on systems. Inventory data is information about physical, logical, and virtual
hardware (such as virtual systems, virtual servers, and farms), software
applications, operating systems, middleware, firmware and BIOS, diagnostics,
and network.
v Manage inventory profiles that you can use to discover a group of resources or
collect inventory data based on a set of criteria.
v View systems, inventory data, and relationships among systems in the network
using the Resource Navigator
v Pass security credentials to one or more systems to gain access to that agents
Status manager
Status manager provides an at-a-glance view of the health of your managed
resources (including systems, operating systems, applications, and security) and
processes.
The status of discovered systems is automatically retrieved and displayed, and this
display can be customized in several waysusing one of the system health and
status-related tasks, navigating to a specific resource, or using the new capabilities

integrated into the command line interface.
You can use the status manager plug-in to:
v Use the Status Manager Summary page to view the status of discovered systems
and a summary of tasks that will help you manage the status, problems and
events for systems.
v Determine the health, compliance, and performance of managed systems in your
environment using the health summary, scoreboard, and dashboard. The health
summary shows the overall health of your managed systems. The scoreboard
summarizes the hardware state, event state and compliance state for all
managed systems. The dashboard shows performance metrics for specific
managed systems.
v View the event log.
v Identify problems and find the root cause by viewing problems and the event
log.
v Subscribe to events on the ones deemed important. You can also identify events
to be cleared automatically.
v Monitor dynamic properties of resources by defining monitors and thresholds
and generating a notification when a threshold has been reached.
v Monitor processes and device services on a specific system by defining monitors
and thresholds and generating a notification when a threshold has been reached.
v Monitor system information in various formats.
v Drill down into the root cause of problems.
Configuration manager
Configuration manager is used to integrate new hardware into your environment,
configure systems after installation, or do one-off configurations for problem
resolution. Configuration manager leverages a set of well defined templates that
can be applied to servers, storage, and network resources even if the resources are
comprised of very different technologies.
You can use the configuration manager plug-in to:
v Use the Configuration Manager Summary page to view system configuration
status and a summary of tasks that will help you configure your systems.
v Initially configure one or more systems (hardware and operating systems) to a
point where they can be deployed, allocated, and powered on.
v Automatically configure newly discovered systems using the automatic-deploy
capability of a configuration plan.
v Reconfigure systems to prepare for redeployment, reallocation, or
re-provisioning (for example, as a result of an event or as part of a workflow
that the configuration needs to be support).
v Manage configuration templates and plans. A configuration template is a collection
of settings and values that define the configuration of a system. A configuration
plan is a set of templates that can be applied to one or more systems in a specific
order.
Automation manager
Automation manager provides tools to notify an administrator or run a predefined
tasks automatically when a certain event occurs.
10
You can use the automation manager plug-in to:

v Use the Automation Manager Summary page to view the status of jobs and
automation plans and a summary of tasks that will help you automate tasks.
v Create custom event-automation plans used to automate tasks and other
responses to situations that occur in your environment.
v Create and manage event filters that allow the event automation plans to target
specific events.
v Create and manage event actions that identify tasks or commands to run or
notifications to send. The types of actions include starting a noninteractive task
or program on the management server or the system on which the event was
generated or sending an email notifications over the Internet or to a mobile
phone.
Update manager
Update manager provides tools for maintaining current versions of operating
systems, device drivers, firmware and BIOS, and IBM Systems Director agent and
server code on managed systems without an upgrade or migration of the installed
product.
You can use the update manager plug-in to:
v Use the Update Manager Summary page to view update status and a summary
of tasks that will help you manage updates on your systems.
v View update history and status of targeted systems.
v Identify updates available for your systems.
v Create customized update groups for your companys certified list of updates.
v Detect and view out-of-date systems.
v Get a notification when systems are in need of updates and which updates are
needed.
v Download, distribute and install available and requisite updates tin a single
request without repackaging or performing each step in the process separately.
v Download and review update information, such as prerequisites, readmes,
Release Notes, content letters, and associated collateral.
Remote access manager

Remote access manager provides tools that support running and monitoring
applications and services running on remote systems.
You can use the remote access manager plug-in to:
v View and interact with applications on a system remotely by displaying the
screen image of the system using remote control tools, including Virtual
Network Computing (VNC), Remote Desktop (RDP), and web-based remote
control for IBM BladeCenter and RSA.
v Run command-line programs through a remote session. The remote session
creates less network traffic and uses fewer system resources than the remote
control applications and, therefore, is useful in low-bandwidth situations.
v Run hardware management commands from the hardware command line, which
connects to the service processor of the target system.
v Transfer files from one location to another and synchronizing files, directories, or
drives using a secure alternative to FTP.
11
Virtualization manager
Virtualization manager provides tools for managing the lifecycle of virtual
resources.
Virtualization manager now includes support for virtualized environments
managed by wholly different server virtualization environments. These include
Hardware Management Console (HMC), Integrated Virtualization Manager (IVM),
Microsoft Virtual Server, VMware and Xen virtualization. Some additional basic
discovery and health management is supported for z/VM virtualization. As a
result of this cross-solution management consolidation, you can visualize and
control both the physical and virtual resources from a single user interface.
You can use the virtualization manager plug-in to:
v Work with virtualized environments and tools, including Hardware
Management Console (HMC), Integrated Virtualization Manager (IVM),
Microsoft Virtual Server, VMware, and Xen virtualization
v Viewing topology that shows the connections between physical and virtual
resources, which can vary dynamically across time
v Tracking alerts and system status for virtual resources and their resources to
easily diagnose problems affecting virtual resources
v Creating automation plans based on events and actions from virtual and
physical resources, such as relocating a virtual server based on critical hardware
alerts
v Create, delete and manage virtual servers and virtual farms for several
virtualization technologies in the industry
v Relocate virtual servers to alternate physical hosts
IBM BladeCenter and System x management

IBM BladeCenter and System x management provides lifecycle management of
your modular System x and IBM BladeCenter systems and related resources,
including discovery, health and status monitoring, configuration, updates, and
virtualization. It also provides platform-specific functions.
You can use the IBM BladeCenter and System x management plug-in to:
v Change power settings
v Manage hardware logs
v Identify hardware using the locator LED
v Turn off light-path diagnostic LEDs
IBM System z management

IBM System z management provides the capability to discover System z hosted
virtual servers, and to access status information about them.
This plug-in provides functions to discover, monitor status, configure, and update
these virtual servers. It also generates information used in the Welcome panel
summary view and includes support for Linux on System z and z/VM systems
running on IBM System z mainframes.
IBM Power Systems management

IBM Power Systems management provides lifecycle management of your IBM
Power systems, and platform managers such as Hardware Management Console
(HMC) and Integrated Virtualization Manager (IVM) platform managers, including
12
discovery, health and status monitoring, configuration, updates, and virtualization.

It also provides platform-specific functions.
You can use the IBM Power Systems management plug-in to:
v Manage the following Power System environments that might include
POWER5 and POWER6 processor-based servers running AIX, IBM i, or Linux:
Power Systems managed by the Hardware Management Console
Power Systems managed by the Integrated Virtualization Manager
A Power Systems server with a single image (a nonpartitioned configuration)
A Power Architecture BladeCenter server under the control of a BladeCenter
management module
v Perform management tasks on systems that are under the control of HMC and
IVM, including managing power, creating virtual serves, editing virtual server
resources, and relocating virtual servers between host systems.
v Perform management tasks that are available from the IBM Systems Director
Web interface for AIX 6.1 and IBM i 5.4 and 6.1.
For additional information about managing the virtualization and consolidation on
Power systems using IBM Systems Director, see the Managing IBM Power Servers
with IBM Systems Director 6.1 white paper on the Web at: www.ibm.com/
common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH
&appname=STGE_PO_PO_USEN&htmlfid=POW03011USEN
&attachment=POW03011USEN.PDF
IBM System Storage management

IBM System Storage management provides lifecycle management of your physical
and virtual storage systems, including discovery, health and status monitoring,
configuration, updates, and virtualization. It also provides platform-specific
functions.
You can use the IBM System Storage management plug-in to:
v Add storage systems to IBM Systems Director using a proxy provider
v Configure storage systems
v Manage storage devices
v Update a SAN configuration profile
v Launch storage management applications
v Use integrated SCM features to manage integrated RAID Controllers,
BladeCenter SAS modules, and BC-S RAID SAS modules
v Use embedded management interfaces for DS3000, DS4000, and DS6000, and
TotalStorage Productivity Center (TPC) to manage SAN Volume Controller
(SVC), DS8000 and ESS storage devices
v Support for automation plans based on events and event actions from storage
resources
v Support for IBM System Storage Area Network products
Additional IBM Systems Director plug-ins

Additional IBM Systems Director plug-ins can be downloaded and installed on top
of IBM Systems Director to provide advanced function or function tailored to a
particular environment.
For a complete list of available plug-ins and for information about how to
download and install the plug-ins, see the IBM Systems Director Web site at
www.ibm.com/systems/management/director/plugins/.
13
Active Energy Manager plug-in

The Active Energy Manager plug-in helps you to manage, monitor and collect
energy-consumption data from IBM systems including IBM BladeCenter chassis
and rack-mounted System x servers. You can use Active Energy Manager to:
v Allocate less power and cooling infrastructure to your IBM servers.
v Lower power usage on select IBM servers.
v Plan for the future by viewing trends of power usage over time.
v Determine power usage for all components of a rack.
Active Energy Manager is a for-fee licensed plug-in that supports Windows, Linux
for x86, and Linux for Power platforms.
BladeCenter Open Fabric Manager plug-in

The BladeCenter Open Fabric Manager plug-in helps you to quickly replace and
recover blades in your environment. You can use this plug-in to:
v Pre-assign MAC and WWN addresses, as well as storage boot targets for up to
100 chassis or 1400 blade servers.
v Create addresses for blade servers, save the addresses to a configuration file, and
deploy the addresses to the blade slots in the same chassis or in up to 100
different chassis without any blade servers installed in the chassis.
v Automatically replace a failed blade from a designated pool of spare blades.
BladeCenter Open Fabric Manager is a for-fee plug-in that supports all platforms
that IBM Systems Director supports.
Service and Support Manager plug-in

The Service and Support Manager plug-in, which includes the Electronic Service
Agent tool, identifies and reports hardware problems and service information
automatically to IBM for service and support. All information sent to IBM is
stored in a secure IBM database and used for improved problem determination.
You can use the Service and Support Manager to:
v Place service calls to IBM automatically if the system is under a service
agreement or warranty.
v Collect and send scheduled system inventory and diagnostic inventory to an
IBM database. This inventory information is available to IBM support
representatives when they are solving your problem.
v Communicate with IBM using a secure Internet connection using encryption
and authentication.
Service and Support Manager is a free plug-in that supports Windows and Linux
for x86 platforms.
Upward integration
IBM Systems Director lets you to make the most of your existing enterprise
management structure by upwardly integrating with many workgroup and
enterprise-management products.
IBM Systems Director upward integration modules (UIMs) and management packs
enable non-IBM workgroup and enterprise-management products to interpret and
14
display data that is provided by Common Agent and Platform Agent. IBM Systems
Director UIMs and management packs provide enhancements to the
enterprise-management products that you can use to collect inventory data, view
IBM Systems Director event notifications, and for some UIMs, distribute IBM
Systems Director software packages.
With the IBM Systems Director UIMs and management packs, you can use your
enterprise-management software to manage systems that have Platform Agent or
Common Agent software installed on them.
You can use Platform Agent 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.
Platform Agent uses some of the latest systems-management standards, including
Common Information Model (CIM), Web-Based Enterprise Management (WEBM)
and Extensible Markup Language (XML), to provide compatibility with your
existing enterprise-management software.
For more information about upward integration modules, see IBM Systems
Director Upward Integration Modules in the IBM Systems information center on
the Web at publib.boulder.ibm.com/infocenter/systems/topic/uims/
fqs0_main.html.
You can also configure IBM Systems Director Server to forward alerts (such as
SNMP) to higher-level enterprise managers, including CA Unicenter NSM, HP
OpenView NNM, HP OpenView Operations for Windows, Tivoli Netview, Tivoli
Management Framework, Microsoft Systems Center Operations Manager, and
Microsoft Systems Management Server.
15
16
Chapter 2. Planning for IBM Systems Director

Before installing or updating IBM Systems Director, review the installation
requirements and plan your installation.
Hardware and software requirements

IBM Systems Director has specific requirements for hardware and software. These
requirements comprise the specified operating environment for IBM Systems Director.
IBM Systems Director provides support for a wide range of hardware products,
operating systems, and database applications.
Hardware requirements for IBM Systems Director

To successfully install IBM Systems Director, the system on which you install IBM
Systems Director components must meet certain hardware requirements,
depending on the components to be installed and the type of system on which
they will be installed.
Hardware requirements for running IBM Systems Director Server

IBM Systems Director Server has certain hardware requirements. These
requirements can vary depending on the size of your IBM Systems Director
systems-management environment.
Recommended hardware requirements for IBM Systems Director Server running
on Windows:
IBM Systems Director Server has certain hardware requirements to run on systems
running Windows.
The following recommendations are for three types of IBM Systems Director
systems-management environments:
Small configuration
A systems-management environment that includes less than 500
Common-Agent managed systems. The database software is Apache Derby.
Medium configuration
A systems-management environment that includes between 500 and 1000
Common-Agent managed systems. The database software is IBM DB2.
Large configuration
A systems-management environment that includes between 1000 and 5000
Common-Agent managed systems. The database software is IBM DB2.
When reviewing these recommendations, consider the following information:
v Installation and startup times improve with faster disk access times. SCSI
adapters and 10 K RPM drives provide the best performance.
v Disk sizes are arbitrary and indicative of disk requirements.
v System performance depends on the nature of your requirements and system
workload.
v The IBM DB2 database software sizing should be comparable for Oracle and
Microsoft SQL Server. The sizing presumes that DB2 is running on the same
server as IBM Systems Director Server.
17
The following recommendations are based on a 32bit version of Windows Server

2003 Enterprise Edition.
Table 1. IBM Systems Director Server recommended hardware requirements for
different-sized Windows environments
Recommended hardware requirements
Configuration
Processor
Memory
2
Disk storage
Small
1 processor, 3 GHz
Intel Xeon 1
1 GB
Medium
2 processors, 3 GHz
Intel Xeon 1
2 GB
6 GB
Large
4 processors, 3 GHz
Intel Xeon 1
4 GB
8 GB
4 GB
The processor (CPU) sizing is based on the Intel Xeon processor, but is comparable for
equivalent Intel and AMD processors.
When accessing Common Agent or Platform Agent that are running on IBM i
partitions, it might be necessary to increase the memory on the management server
from 1 GB to 1.5 GB or 2 GB to gain better performance.
Attention: If you use DVD media to install IBM Systems Director Server, ensure that you
allot an additional 1.2 GB of available space on the system to contain the agent packages
that are copied from the DVD at the end of the server installation. The packages are copied
to \installation_directory\packaging\agent on the server, where installation_directory is the
path to the extracted installation files.
Hardware requirements for systems running Common Agent or

Platform Agent
Common Agent and Platform Agent have minimum processor speed, random
access memory (RAM), and disk space requirements.
Note: The disk space listed is the minimum requirement for an installation using
the default selections.
x86-compatible systems
Notes:
v The systems on which you install Common Agent must meet the Wired for
Management (WfM), version 2.0, specifications.
v System Management BIOS (SMBIOS) 2.1 or later is required for all systems in an
IBM Systems Director environment.
Table 2. x86-compatible systems: Minimum hardware requirements
Requirements
Platform Agent
Common Agent
Processor speed
Pentium 1.5 Ghz or equivalent
Pentium 1.5 Ghz or equivalent
Memory (RAM)
512 MB
512 MB
Disk space
40 MB (for Windows)
110 MB (for Windows)
100 MB (for Linux)
170 MB (for Linux)
Supported IBM systems and products

IBM Systems Director is licensed for use and supported in a large range of IBM
systems and products.
18
These systems and products include:

v IBM BladeCenter chassis
v IBM blade servers
v IBM Power Systems (formerly System i and System p systems)
v IBM System Storage Network Attached Storage (NAS) products
v System x servers
v System z systems
To determine whether a system meets the recommended hardware requirements
for your IBM Systems Director systems-management environment, see Hardware
requirements.
Notes:
1. The degree of support that IBM Systems Director provides on these systems
and products might vary. For this information, see the IBM Systems Director
Release Notes.
2. IBM Systems Director runs on IBM Power and System z systems when the
installed operating system is also supported by IBM Systems Director.
3. The IBM System Storage NAS products include an installation of Common
Agent.
4. Some systems and products might not be available in your area.
Related reference
Hardware requirements for IBM Systems Director on page 17
Supported operating systems on page 31
IBM BladeCenter products

IBM Systems Director provides support for IBM BladeCenter chassis and blade
servers.
v
v
v
v
v
IBM
IBM
IBM
IBM
IBM
BladeCenter
BladeCenter
BladeCenter
BladeCenter
BladeCenter
E chassis, machine type 8677

H chassis, machine type 8852
HT chassis, machine type 8740
HT chassis, machine type 8750
S chassis, machine type 8886
v IBM BladeCenter T chassis, machine type 8720

v IBM BladeCenter T chassis, machine type 8730
v
v
v
v
v
v
v
HC10 blade server, machine type 7996

HC10 blade server, machine type 7997
HS12 blade server, machine type 8014
v
v
v
v
v
HS20
HS21
HS21
HS21
HS40
blade server, machine type 8843

XM blade server, machine type 7995
v JS12 blade server, machine type 7998

Chapter 2. Planning
19
v
v
v
v
v
JS20 blade server, machine type 8842

LS20 blade server, machine type 8850
v
v
v
v

QS21 blade server, machine type 0792
QS22 blade server, machine type 0793
Supported storage devices

IBM Systems Director manages a wide variety of storage devices. Supported
storage devices are: disks, switches, internal RAID controllers, and RAID
subsystems.
Supported devices and actions

Note that a storage volume is similar to a logical volume.
This is a list of supported storage devices, subsystems, storage modules, and their
access devices:
v Dedicate Local Storage, access with Integrated RAID Controllers (IRC)
Basic RAID Controller
v IBM BladeCenter integrated storage, accessed with IBM BladeCenter S SAS
RAID Controller Modules, supported only on Windows 2003 and Linux on
System x systems.
v Network Storage, which is an external SAN storage system. Network storage is
accessed with storage switches, adapters, and protocols such as Fibre Channel,
SAS, or iSCSI
IBM System Storage DS4000
IBM System Storage DS3200, DS3300, DS3400
v Storage switches
Brocade 2Gbit/sec and 4Gbit/sec Fibre Channel (chassis and external)

Qlogic 2Gbit/sec and 4Gbit/sec Fibre Channel (chassis and external)
IBM eServer BladeCenter 2-Port Fibre Channel Switch Module
IBM BladeCenter SAS Connectivity Module
IBM BladeCenter S SAS RAID Controller Module
Table 3. Storage management tasks and supported devices
LSI SAS controllers
1064
1064e
1068
Task
Discovery
20
Yes
1078
1078
Internal Mega
RAID
RAID
Yes
Yes
IBM BladeCenter SAS

Modules
RAID
Connectivity controller
module
module
Yes
Yes
Fibre
Channel
Switches (2 IBM System Storage DS
Gbit/sec and
4 Gbit/sec)
3
2
Brocade and 0
0
Qlogic
Yes
Yes
3
3
0
0
3
4
0
0
4
0
0
0
6
0
0
0
Yes
Yes
Yes
Yes
Table 3. Storage management tasks and supported devices (continued)
LSI SAS controllers
Task
1064
1064e
1068
1078
1078
Internal Mega
RAID
RAID
IBM BladeCenter SAS

Modules
RAID
Connectivity controller
module
module
Fibre
Channel
Switches (2 IBM System Storage DS
Gbit/sec and
4 Gbit/sec)
3
2
Brocade and 0
0
Qlogic
3
3
0
0
3
4
0
0
4
0
0
0
6
0
0
0
Inventory
collection
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Monitoring
(alerts and
status)
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Physical
Topology
No
No
No
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Logical
Topology
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Provisioning
No
No
No
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
SAS zoning
No
No
No
Yes
Yes
No
No
No
No
No
No
View and
manage
attached
devices
Yes
No
No
Yes
Yes
No
No
No
No
No
No
Config
uration
Yes
No
No
Yes
Yes
No
No
No
No
No
No
Update
acquisition
and
compliance
check
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
No
Update
Installation
Yes
Yes
Yes
Yes
No
No
No
No
No
No
No
Trouble
shooting
No
No
No
Yes
Yes
No
No
No
No
No
No
Storage restrictions
v You are advised to not install Storage Configuration Manager on a system that is
running IBM Systems Director.
v Storage devices such as memory, caches, and registers are not managed by
Storage Management.
v These devices are not supported:
IBM System Storage N series hardware
IBM System Storage SAN Volume Controller
ServeRAID-MR10ie (CIOv) Controller for IBM BladeCenter
Any other storage devices not listed in Table 3 on page 20.
Chapter 2. Planning
21
v When performing configuration and serviceability functions on Integrated RAID

Controller (IRC) devices with IBM Systems Director, support is limited to
Platform-Agent managed systems on the IRC host.
v The SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module is
integrated with the IBM Systems Director Server and does not need to be
separately installed on the IBM Systems Director Server. Keep in mind these
facts about this SMI-S provider:
It has one of these two names, depending on the host operating system:
- PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module
6.1.0 Linux
- PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module
6.1.0 Windows
It must be configured in order to manage storage devices.
It runs only on versions of Windows 2003 and Linux on System x systems.
It runs on those versions and releases of Windows 2003 and Linux on
System x systems that support the IBM Systems Director Server.
It can be installed on additional IBM Systems Director Platform-Agent
managed systems if it becomes necessary to have additional copies. In this
case, the provider is supported only on
- Those versions and releases of Windows 2003 that support Platform-Agent
managed systems
- The following Linux on System x levels:
v Red Hat Enterprise Linux, version 4.0
v SUSE Linux Enterprise Server 9
v SUSE Linux Enterprise Server 10
Network requirements
IBM Systems Director requires certain ports to be available and certain network
protocols to be installed in order to enable communication among IBM Systems
Director components and between the management server and managed systems.
In addition, network connectivity must exist between the management server and
managed systems, and between the management server and the IBM Systems
Director Web interface browser system.
Nameserver (DNS) requirements

Ensure that the nameserver is configured correctly. If the nameserver is not
configured correctly, you will encounter problems and potential failure during IBM
Systems Director installation.
The following conditions indicate that the nameserver is configured correctly:
v The nameserver address or addresses are correct for your network environment.
v You are able to connect to valid hosts on the network and validate that the
connection occurs within a reasonable amount of time.
All available ports

IBM Systems Director processes require access to a number of ports in the
installation and systems-management environment. If these ports are blocked by a
firewall or used by another process, some IBM Systems Director functions might
not work.
22
Related reference
VMware Documentation (http://www.vmware.com/support/pubs/)
Important port considerations:
When preparing your ports for an IBM Systems Director environment, there are
some important considerations to remember or some IBM Systems Director
functions might not work.
Review the following considerations:
v Depending on the system configuration, one of the following port pairings must
be open in order to install IBM Systems Director:
(For Microsoft Windows and Red Hat Enterprise Linux) 5988 and 5989
(For SUSE Linux Enterprise Server) 15988 and 15989
Some firewalls might attempt to block these ports. Make sure that the IBM
Systems Director software components can use these ports. If custom alternative
ports are chosen for the CIM Server, then those ports must be opened.
v (Windows only) For any CIM-related function of the Common Agent to work,
the HTTP port must be turned on for the Pegasus CIMOM, regardless of
whether HTTPS is turned on (SSL is enabled).
v If the CIMOM ports for a Platform-Agent managed system are changed after
IBM Systems Director Server discovers the system, the system will change to an
Agentless-managed system in IBM Systems Director. To correct this change, you
must complete the following steps:
1. Delete the system in IBM Systems Director.
2. Shut down and restart the system.
3. Discover the system in IBM Systems Director.
v Windows firewall can interfere with discovery of managed systems running
Windows 2003, Windows 2008, Windows XP, and Windows Vista.
v If a proxy server is required to access the Internet from the management server,
make sure that the management server is configured to use the proxy.
v Update manager 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.
v IBM Systems Director Server can access the Internet through ports 80 (HTTP)
and 443 (HTTPS). The firewall and proxy server must permit bi-directional
communication through these ports.
v By default, IBM Systems Director uses a random source port for SLP
communication through a firewall to a Remote Supervisor Adapter. The random
port causes problems when discovering the Remote Supervisor Adapter through
a firewall because the Remote Supervisor Adapter responds using that random
port. To resolve this problem, open any unused or private port. Then, edit the
slp.prop file to use your selected port. The following example uses port 49150:
# Up to 10 parallel ports can be open at a time
# when opening firewall ports, configure the source port and open
# that port and the next 9 consecutive ports
# default: 0 - random port used
source.port=49150
v Neither z/VM nor the MAP Agent add any additional ports to those already
provided by IBM Systems Director for standard communication. Instead of
TCP/IP, z/VM communication APIs are used to communicate with the servers
Chapter 2. Planning
23
that provide information to IBM Systems Director and to enact any changes to
z/VM servers. The communication is by means of sockets and the AF_IUCV
address family.
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. The listener responds
by connecting to the original random port opened by the initiator.
v For the getfru command to run successfully, the managed system must have
firewall access through a standard FTP port.
v The Remote Control, Update Install, and the Agent Installation wizard tasks 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 Systems Director typically uses for communication. Most firewalls will
not transmit the data through this other port.
Related reference
Ports for IBM Systems Director Server
Ports for managed systems on page 29
Ports for IBM Systems Director Server:
IBM Systems Director processes require access to a number of ports on the
management server. If these ports are blocked by a firewall or used by another
process, some IBM Systems Director functions might not work.
Table 4. Ports used by IBM Systems Director Server for communication
Port
TCP or
UDP
Direction
Communication description
20
TCP
Inbound
FTP data communication with BladeCenter I/O

modules (switches and bridges)
21
TCP
Inbound
FTP communication with BladeCenter I/O

22
TCP
Outbound
SSH communication with:

v Advanced management module and
management module
v BladeCenter I/O modules
v Platform Agent installed on systems running
Linux, including systems managed by HMC
and IVM
v SSH used by IBM Power systems to
communicate with HMC/IVM
v Non-Windows Agentless-managed systems
23
TCP, UDP
Outbound
Telnet communication with:

v Advanced management module, management
module, Remote Supervisor Adapter, and
Remote Supervisor Adapter II
v Updates
69
24
TCP
Inbound
TFTP communication with BladeCenter I/O

Table 4. Ports used by IBM Systems Director Server for communication (continued)
Port
TCP or
UDP
Direction
80
TCP
Outbound
HTTP communication with:

v IBM Systems Director Web interface
v IVM interface
v Update manager
81
TCP
Outbound
HTTPS communication with BladeCenter I/O

135
TCP, UDP
Outbound
(Windows only) Software installation and remote

access communication with Platform Agent
137
TCP, UDP
Outbound
(Windows only) Communication with

Agentless-managed systems using Microsoft
Windows DCOM
138
TCP, UDP
Outbound

Agentless-managed systems using Windows
DCOM
139
TCP, UDP
Outbound

Server Message Block (SMB)
161
UDP
Outbound
SNMP agent communication with:

v Platform Agent
Note: This port is used when the SNMP agent
for the operating system is configured.
v Agentless-managed systems
162
TCP, UDP
Outbound
(TCP, UDP)
Inbound
(UDP)
427
TCP, UDP
Outbound
and
Inbound
Simple Network Management Protocol (SNMP)

trap communication with SNMP devices,
including TCP for Tivoli NetView events.
Examples of SNMP devices are advanced
management module, management module,
Remote Supervisor Adapter, and Remote
Supervisor Adapter II.
SLP communication with:
v Common Agent
v Platform Agent
v IBM Director Agent 5.20
v Service Location Protocol (SLP) service agent or
SLP directory agent
Chapter 2. Planning
25
Port
TCP or
UDP
Direction
443
TCP
Outbound
HTTPS communication with:

v IBM Systems Director Web interface
management module
v HMC Web interface
v Updates
445
TCP, UDP
Outbound
(Windows only) Open on Agentless and

Platform-Agent managed systems for the
following features:
v Software installation
v Remote access communication
v (Agentless-managed systems only) Inventory
collection
446
TCP
Outbound
Non-SSL communication with the IBM i

DRDA/DDM server job
448
TCP
Outbound
SSL communication with the IBM i DRDA/DDM

server job
449
TCP
Outbound
SSL communication with the IBM i server port

mapper
623
UDP
Outbound
Remote Management and Control Protocol

(RMCP) unsecure communication with IPMI
baseboard management controller (BMC) service
processors
664
UDP
Outbound
Remote Management and Control Protocol

(RMCP) secure communication with IPMI BMC
service processors
Random
port in the
1024-65535
range
TCP
Inbound
v Random port range for communication between

IBM Systems Director Server with Intelligent
Platform Management Interface (IPMI) service
processors
Note: You can specify a fixed port by
modifying the asmDefinitions.properties file in
the data directory.
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. The
listener responds by connecting to the original
random port opened by the initiator.
26
1433
TCP
Outbound
and
Inbound
Microsoft SQL Server databases
1521
TCP
Outbound
and
Inbound
Oracle Database databases
1527
TCP
Outbound
and
Inbound
Apache Derby databases
2033
TCP
Inbound
Communication with the IBM Systems Director

Launched Tasks program using IBM Systems
Director interprocess communication (IPC)
Port
TCP or
UDP
2044
Direction
TCP
Outbound
and
Inbound
smcli command-line interface

Note: This port number can be changed. See Port
configuration for smcli.
3389
TCP
Outbound
and
Inbound
Remote Desktop Protocol, Remote Desktop

Connection, or Remote Accessor for full screen
access to systems running Windows
4066
TCP
Inbound
Communication with the IBM Systems Director

Launched Tasks program using IBM Systems
Director interprocess communication (IPC) over
SSL
5901
TCP
Outbound
and
Inbound
Virtual Network Computing (VNC), used by

Remote Access
5988
TCP
Inbound
(Windows and Red Hat Enterprise Linux) CIM

Server unsecure port
5989
TCP
Inbound
v (Windows and Red Hat Enterprise Linux) CIM

Server secure port
v HMC/IVM CIMOM
6641
TCP
Inbound
SAS switches
6988
TCP
Inbound
CIM listener
6989
TCP
Inbound
CIM listener
6090
TCP
Outbound
TCP Command Mode communication between

IBM Systems Director Server and advanced
management module, management module,
Remote Supervisor Adapter, and Remote
Supervisor Adapter II
8421
TCP
Inbound
v (All operating system platforms) HTTP

communication between IBM Systems Director
Server and the IBM Systems Director Web
interface
v HTTP used by IBM Power systems to
communicate with CIM
8422
TCP
Inbound
v (All operating system platforms) HTTPS

communication between IBM Systems Director
Server and the IBM Systems Director Web
interface
v HTTPS used by IBM Power systems to
communicate with CIM
8470
TCP
Outbound
Non-SSL communication with the IBM i central

server job
8471
TCP
Outbound
Non-SSL communication with the IBM i database

server job
8472
TCP
Outbound
Non-SSL communication with the IBM i data

queue server job
8473
TCP
Outbound
Non-SSL communication with the IBM i file server

job
8474
TCP
Outbound
Non-SSL communication with the IBM i network

print server job
Chapter 2. Planning
27
Port
TCP or
UDP
Direction
8475
TCP
Outbound
Non-SSL communication with the IBM i remote

command and distributed program call server job
8476
TCP
Outbound
Non-SSL communication with the IBM i signon

server job
90009100
TCP
9470
TCP
Outbound
SSL communication with the IBM i central server

job
9471
TCP
Outbound
SSL communication with the IBM i database

server job
9472
TCP
Outbound
SSL communication with the IBM i data queue

server job
9473
TCP
Outbound
SSL communication with the IBM i file server job
9474
TCP
Outbound
SSL communication with the IBM i network print

server job
9475
TCP
Outbound
SSL communication with the IBM i remote

command and distributed program call server job
9476
TCP
Outbound
SSL communication with the IBM i signon server

job
9510
TCP
Inbound,
Outbound
Communication with Common Agent and CAS

Web services
95119513
TCP
Inbound
Agent manager
95149515
TCP
Communication Platform-Agent managed system

running Xen
Nonstop ports that are used to make sure

Common Agent is restarted automatically if it
fails.
Note: Ports must be available, but not firewall
accessible.
10000
Events from storage devices
13991
UDP
Inbound
Receives events sent by advanced management

module, management module, Remote Supervisor
Adapter, and Remote Supervisor Adapter II
14247
UDP
Inbound
IBM Systems Director interprocess communication

(IPC) with IBM Director Agent 5.20
14248
UDP
Outbound

14251
UDP
Inbound
IBM Systems Director Server interprocess

communication (IPC) support
20000
TCP
Inbound
v CAS events
v Communication with VMware
Note: If you plan to manage systems running
VMware VirtualCenter, or VMware ESX Server,
see the VMware documentation to make sure
port requirements are met: www.vmware.com/
support/pubs/
50000
28
TCP
Both
IBM DB2 Universal Database databases
Related reference
Important port considerations on page 23
Ports for managed systems
Ports for managed systems:
IBM Systems Director processes require access to a number of ports on managed
systems. Managed systems include Common-Agent managed systems,
Platform-Agent managed systems, and Agentless-managed systems.
Table 5. Ports on managed systems
Port
TCP or
UDP
Direction
22
TCP
Inbound
SSH communication with:

management module
v Platform Agent installed on systems running
Linux, including systems managed by HMC
and IVM
v SSH used by IBM Power systems to
communicate with HMC/IVM
v Non-Windows Agentless-managed systems
135
TCP, UDP
Inbound
(Windows only) Software installation and remote

access communication with Platform Agent
137
TCP, UDP
Inbound

Agentless-managed systems using Microsoft
Windows DCOM
138
TCP, UDP
Inbound

DCOM
139
TCP, UDP
Inbound

Server Message Block (SMB)
161
UDP
Inbound
SNMP agent communication with:

v Platform Agent
v Agentless-managed systems
Chapter 2. Planning
29
Table 5. Ports on managed systems (continued)

Port
TCP or
UDP
427
TCP, UDP
Direction
Outbound
and
Inbound
SLP communication with:

v Common Agent
v Platform Agent
v IBM Director Agent 5.20
v Service Location Protocol (SLP) service agent or
SLP directory agent
445
TCP, UDP
Inbound
(UDP)
(Windows only) Open on Agentless and

Platform-Agent managed systems for the
following features:
v Software installation
v Remote access communication
v (Agentless-managed systems only) Inventory
collection
5988
TCP
Inbound
(Windows and Red Hat Enterprise Linux) CIM

Server unsecure port
5989
TCP
Inbound
v (Windows and Red Hat Enterprise Linux) CIM

Server secure port
v HMC/IVM CIMOM
6988
TCP
Inbound
CIM listener
6989
TCP
Outbound
CIM listener
9510
TCP
Inbound
Communication with Common Agent and CAS

Web services
14247
UDP
Inbound

14248
UDP
Outbound

15988
TCP
Inbound
v (For SUSE Linux Enterprise Server) CIM Server

(alternative secure port) communication with
Platform-Agent managed system
v Service processor communication with SUSE
Linux Enterprise Server 10.
v CIM Server (alternative unsecure port)
communication with Platform-Agent managed
system
15989
TCP
Inbound
(For SUSE Linux Enterprise Server) CIM Server

(alternative secure port) communication with
Platform-Agent managed system
20000
TCP
Outbound
v CAS events
v Communication with VMware
Note: If you plan to manage systems running
VMware VirtualCenter, or VMware ESX Server,
see the VMware documentation to make sure
port requirements are met: www.vmware.com/
support/pubs/
30
Related reference
Important port considerations on page 23
Ports for IBM Systems Director Server on page 24
Security requirements
IBM Systems Director Server supports several products to house the registry used
for system security.
User registry products and types

One of the following locations must contain the registry that IBM Systems Director
uses for user authentication:
Operating system
The local operating system user registry is the default registry used by IBM
Systems Director security.
LDAP IBM Systems Director includes Lightweight Directory Access Protocol
(LDAP) authentication support. LDAP support is disabled by default. The
following LDAP servers are supported:
v IBM Tivoli Directory Server
v Microsoft Active Directory
Active directory
The active directory, which is the same as the Microsoft Active Directory,
acts as an LDAP server or domain controller. It supports the following
types of users and groups:
v Global
v Domain
v Local
v Trusted
Ensure that the IBM Systems Director server is a member of the active
directory domain.
Related reference
Operating system and software requirements
Operating system and software requirements

IBM Systems Director has specific requirements for operating systems and
software. IBM Systems Director provides support for operating systems, database
applications, virtualization software, Web browsers, and screen readers.
Supported operating systems

This section lists the operating systems on which IBM Systems Director Server,
Common Agent, and Platform Agent are supported. This support can vary by
version, release, and update. Make sure you review the supported operating
systems for the version of IBM Systems Director in your environment.
Operating systems supported by IBM Systems Director 6.1.0:
IBM Systems Director 6.1.0 provides support for many operating systems.
However, support varies depending on the selected hardware and IBM Systems
Director component.
Chapter 2. Planning
31
Purpose
This little command copies things.
DITA
Starting in version 6.1, IBM Systems Director provides a Web interface for use with
IBM Systems Director Server. IBM Director Console is no longer required.
However, some tasks in the Web interface require the IBM Systems Director
Launched Tasks program. For information about the IBM Systems Director
Launched Tasks program and the tasks that require it, see Launched tasks and the
IBM Systems Director Launched Tasks program. For operating-system support,
see Operating systems supported by the IBM Systems Director Launched Tasks
program.
When preparing to install IBM Systems Director, consider the following
information:
v Platform Agent, version 6.1.0 and IBM Director Core Services version 5.20.3 are
the same agent.
v Unless stated otherwise, IBM Systems Director provides agentless support for all
operating systems listed in this topic.
Note: IBM Systems Director Server is supported on VMware ESX Server if IBM
Systems Director Server is supported on the selected guest operating system.
Supported guest operating systems are those that are supported by both IBM
Systems Director and the specified version of VMware. See the VMware product
documentation for a list of supported operating systems.
Table 6. Windows versions supported by IBM Systems Director on System x systems; IBM and third-party
x86-based systems
IBM
Systems
Director
Server
Common
Agent
Platform
Agent
Windows Server 2003 Datacenter Edition (supports Service Pack 2)
Windows Server 2003, Enterprise and Standard Editions (supports Service Pack 2) X
Windows Server 2008 Datacenter Edition (supports Service Pack 1)
Windows Server 2008, Enterprise and Standard Editions (supports Service Pack 1) X
Windows Vista, Business, Enterprise, and Ultimate Editions
Windows XP Professional Edition (supports Service Packs 1 and 2)
Operating system
Editions of Windows for 32-bit systems:
Windows Server 2003 Datacenter Edition, Release 2
Windows Server 2003, Enterprise and Standard Editions, Release 2
Editions of Windows for 64-bit systems:

Windows Server 2003 Datacenter x64 Edition, Release 2 (supports Service Pack 2)
Windows Server 2003, Enterprise and Standard x64 Editions, Release 2 (supports
Service Pack 2)
Windows Server 2003 Datacenter x64 Edition (supports Service Pack 2)

Windows Server 2003, Enterprise and Standard x64 Editions (supports Service
Pack 2)
Windows Server 2008 Datacenter x64 Edition (supports Service Pack 1)
32
Table 6. Windows versions supported by IBM Systems Director on System x systems; IBM and third-party
x86-based systems (continued)
IBM
Systems
Director
Server
Common
Agent
Platform
Agent
Windows Vista, Business, Enterprise, and Ultimate x64 Editions
Windows XP Professional x64 Edition (supports Service Packs 1 and 2)
Operating system
Windows Server 2008, Enterprise and Standard x64 Editions (supports Service
Pack 1)
Other editions of Windows operating systems:

Microsoft Virtual Server (guest operating system) (Release 2 required, supports
Service Pack 1)
Note: Supported guest operating systems are those that are supported by both
IBM Systems Director and the specified version of Microsoft. See the Microsoft
product documentation for a list of supported operating systems.
Related reference
Operating systems supported by the IBM Systems Director Launched Tasks
program
Hardware requirements for running IBM Systems Director Server on page 17
Operating systems supported by the IBM Systems Director Launched Tasks
program:
IBM Systems Director Server. IBM Director Console is no longer required.
However, some tasks in the Web interface require the IBM Systems Director
Launched Tasks program. For information about the IBM Systems Director
Launched Tasks program and the tasks that require it, see Launched tasks and the
IBM Systems Director Launched Tasks program.
Important: The launched-tasks feature in IBM Systems Director requires Java Web
Start (JWS).
The following operating systems are supported by the IBM Systems Director
Launched Tasks program on System x systems; IBM and third-party x86 and
x64-based systems:
v Microsoft Virtual Server (guest operating system)
v Windows Server 2003, Enterprise and Standard Editions
v Windows Server 2003, Enterprise and Standard x64 Editions
v Windows Server 2008, Enterprise and Standard Editions
v Windows Server 2008, Enterprise and Standard x64 Editions
v Windows Vista, Business, Enterprise, and Ultimate Editions
v Windows Vista, Business, Enterprise, and Ultimate x64 Editions
v Windows XP Professional Edition
v Windows XP Professional x64 Edition
Virtualization software supported by IBM Systems Director

This topic lists the supported virtualization software for IBM Systems Director.
Hardware Management Console (HMC)
Chapter 2. Planning
33
v Hardware Management Console Version 7.3.3 SP2, PTF MH01146; Version 7.3.4
Note: It is recommended that you always apply the latest available service pack.
The minimum service pack prerequisite is listed here.
Integrated Virtualization Manager (IVM)
v Integrated Virtualization Manager Version 1.5.2.1 and later fix packs; Version
2.1.0.10, fix pack 20.1 and later fix packs
Note: It is recommended that you always apply the latest available service pack.
The minimum service pack prerequisite is listed here.
Microsoft Virtual Server
v Microsoft Virtual Server 2005 R2 SP1
Note: Supported guest operating systems are those that are supported by both
IBM Systems Director and the specified version of Microsoft. See the Microsoft
product documentation for a list of supported operating systems.
Virtual I/O Server
v Virtual I/O Server Version 1.5.2.1 and later fix packs (for Agentless-managed
systems)
v Virtual I/O Server Version 2.1.0.10, fix pack 20.1 and later fix packs (for
Common-Agent managed system systems and Agentless-managed systems)
VMware ESX Server
v VMware ESX Server 3.0.x Service Console
v VMware ESX Server 3.5.x Service Console
VMware ESXi
v VMware ESXi 3.5 Update 2, and later updates, under the control of VMware
VirtualCenter
VMware VirtualCenter
v VMware VirtualCenter V2.0.x
v VMware VirtualCenter V2.5.x
Xen virtualization
v Red Hat Enterprise Linux 5.0,
v SUSE Linux Enterprise Server
option installed (XEN 3.0)
v SUSE Linux Enterprise Server
option installed (XEN 3.0.4)
with Xen 3.0.3

with Xen 3.1
with Xen 3.1.2
10, with the Xen Virtual Machine Host Server
10 SP1, with the Xen Virtual Machine Host Server
v SUSE Linux Enterprise Server 10 SP2, with the Xen Virtual Machine Host Server
option installed (XEN 3.2)
z/VM virtualization
v z/VM 5.4
Note: Ensure that the following PTFs for z/VM 5.4 are installed:
34
UM32505
UM32503
UM32521
UM32522
Related reference
Microsoft Virtual Server Web page
VMware ESX Server documentation
VMware VirtualCenter documentation
VMware Infrastructure documentation
z/VM PDF files
Supported Web browsers

IBM Systems Director Server. The Web interface requires that you use a supported
Web browser.
The following Web browsers are supported by IBM Systems Director for use with
the IBM Systems Director Web interface:
v Firefox, version 3.0
Note: This is the minimum required version of Firefox on SUSE Linux
Enterprise Server 10 systems.
v Firefox, version 2.0
v Microsoft Internet Explorer, version 7.0
v Microsoft Internet Explorer, version 6.0
Supported screen readers

The IBM Systems Director Web interface provides support for JAWS version 9.0.
Supported database applications

IBM Systems Director Server provides a default database, Apache Derby, that is
configured to store inventory data for the discovered systems in the environment.
You can either use Apache Derby or configure any of the other supported database
applications, which are IBM DB2 Universal Database, Microsoft SQL Server, or
Oracle Database.
Database installation types

Depending on the database application selected and the operating system of the
management server, the database management system (DBMS) 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
Systems Director Server installation, and shares the Java Virtual Machine
with IBM Systems Director.
Local DBMS
The DBMS is installed on the management server on which IBM Systems
Director Server is installed.
Chapter 2. Planning
35
Remote DBMS
The DBMS is installed on a different server than the management server,
and accessed remotely by IBM Systems Director Server.
See Choosing the IBM Systems Director database application for additional
information about these installation types.
Database versions supported by IBM Systems Director Server

The following table lists the database versions supported by IBM Systems Director
Server on different management servers and provides information about whether
the database server is embedded or can be installed locally or remotely.
Note: The database versions that are listed represent both the database server and
the database client where applicable.
Table 7. Database versions supported by IBM Systems Director
Database
Supported database versions
Apache Derby
Linux
Windows
v V10.3 (included with IBM Systems Embedded

Director Server on AIX, Linux,
and Windows)
Embedded
Embedded
IBM DB2
Universal
Database
v Express version 9
v Version 9.1 with Fix Pack 4 or
later
v Version 9.5 with Fix Pack 1 or
later
Local or remote
Local or remote
Local or remote
Microsoft SQL
Server
Microsoft SQL Server 2005 with

Service Pack 2
Local or remote
Microsoft SQL Server 2005 Express

Edition with Service Pack 2
Local
v Version 9.2
v Version 10g release 1
v Version 10g release 2
Local or remote
Local or remote
Local or remote
Oracle Database
AIX
Related tasks
Choosing the IBM Systems Director database application on page 49
IBM Systems Director task support by operating system and

agent levels
Some IBM Systems Director tasks are supported on certain operating systems or
only on Platform-Agent managed systems or Common-Agent managed systems.
For tasks whose support is not affected in this way, see IBM Systems Director task
support not affected by operating systems.
Support for IBM Systems Director tasks can vary depending on the following
items:
v The system or hardware device model (the resource)
v The operating system that is installed on a resource
v The service processor installed in the managed system
v The level of the device drivers that are installed on the managed system
Attention: The device drivers that are available for a managed system depend
on the service processor and operating system that are installed on the managed
system.
36
v The level of IBM Systems Director support installed on the system or device. In
Table 8, the following symbols are used:
IBM Systems Director Server indicates the task is supported by IBM Systems
Director Server.
Level 0 indicates the task support is provided by the operating system.
Level 1 indicates the task is supported for managed resources with Platform
Agent installed.
Level 2 indicates the task is supported for managed resources with Common
Agent installed.
Note: Typically, if a task is supported by Common Agent, it is also supported
by IBM Director Agent version 5.20. However, support can vary for tasks that
update systems or provide cross-platform support:
- IBM i support is provided by IBM Director Agent 5.20 only.
- The Agent Installation Wizard can be used to install subagents only on
Common-Agent managed system.
- (Configuration manager) Only operating system configuration plug-ins are
supported by Common Agent and IBM Director Agent version 5.20.
- (Update manager) Updates on System x and IBM BladeCenter systems and
the IBM i operating system are supported by Common Agent and IBM
Director Agent version 5.20. All other types of updates are supported by
Common Agent only.
- (Update manager) Updates on AIX, Linux on Power Systems, and Linux for
System z are available only with Common Agent. The ability to distribute
Linux updates is only available for Common Agent on Linux.
- (Virtualization manager) IBM Director Agent version 5.20 requires a
separate download and installation of the Virtualization Manager extension.
Table 8. IBM Systems Director task support across operating systems
Operating systems
Task
AIX
IBM i
Microsoft
Virtual
Server
Linux
VMware
Windows
Event Log
IBM Systems Levels 1, 2

Director
Server, Level
2

Director
Server,
Levels 1, 2
Levels 0 , 1,
2
IBM Systems
Director
Server,
Levels 1, 2
File Transfer
IBM Systems Level 2

Director
Server, Level
2
IBM Systems Level 2

Director
Server, Level
2
Level 22
IBM Systems
Director
Server, Level
2
Inventory (hardware)3

Director
Server, Level
2
IBM Systems Levels 0, 1, 2 Levels 01, 1,

Director
2
Server,
Levels 0, 1,
24
Inventory (software)
IBM Systems Levels 0, 1,

Director
25
Server,
Levels 0, 2
IBM Systems Levels 0, 1, 2 Levels 0, 1, 2 IBM Systems

Director
Director
Server,
Server,
Levels 0, 1, 2
Levels 0, 1, 2
Problems (formerly
Hardware Status)6
Level 2
Level 2
Levels 1, 2
8, 7
Levels 1, 2
Levels 1, 2
10
IBM Systems
Director
Server,
Levels 0, 1,
24
Levels 1, 2
Chapter 2. Planning
37
Table 8. IBM Systems Director task support across operating systems (continued)
Operating systems
Task
AIX
IBM i
Linux
Microsoft
Virtual
Server
VMware
11
Level 2
11
Windows
IBM Systems
Director
Server, Level
2
Process Management
IBM Systems Level 2

Director
Server, Level
2
IBM Systems Level 2

Director
Server, Level
2
Remote Control
IBM Systems
Director
Server,
Levels 0, 2
IBM Systems Level 2

Director
Server,
Levels 0, 1, 2
Remote Command Line
IBM Systems Levels 0, 1, 2 IBM Systems Level 2

Director
Director
Server,
Server,
Levels 0, 2
Levels 013,
113, 2
Resource Monitors

Director
Server, Level
2
IBM Systems Console only Console only IBM Systems

14
14
Director
Director
Server,
Server,
Levels 1, 2
Levels 1, 2
Storage Configuration
Manager
IBM Systems
Director
Server

Director
Server,
Levels 1,
28, 15
Update Manager

Director
Server,
Levels 217

Director
Server,
Levels 0, 1,
217
Levels 0, 1,
212
IBM Systems
Director
Server,
Levels 0, 1, 2
Levels 0, 1, 2 IBM Systems

Director
Server, Level
2
19
Levels 1, 2
IBM Systems
Director
Server,
Levels 1, 2 16
Levels 1, 219
IBM Systems
Director
Server,
Levels 0, 1, 2
17
Notes:
1. Agentless-managed system support is available for VMware ESX Server 3i
only.
2. File systems that are displayed for the guest operating system are limited to
file systems within its virtual disk.
3. Inventory data provided can vary among Agentless, Platform-Agent, and
Common-Agent managed systems.
4. Hardware-platform-specific data is not available for hardware inventory.
5. Software Catalog Signatures not supported
6. Unless otherwise indicated, this task is supported (although the support might
be limited) by:
v Out-of-band notifications generated by the service processor
v CIM indications generated by Platform Agent or Common Agent
7. IBM BladeCenter JS21 and JS22 only: Out-of-band notifications generated by a
service processor only.
8. Not supported on System z systems.
9. Limited support only.
10. VMware support for the Problems task has the following limitations:
38
v No support for Platform Agent or Common Agent on VMware ESX Server

3i (Embedded and Installable Editions) although enhanced Agentless
support includes Problems support.
v Support is limited for guest operating systems.
v Support for console is limited to out-of-band notifications generated by a
service processor or in-band events generated by CIM (CIM support is
system specific).
11. Supported on guest operating systems only.
12. Supported on Windows guest operating systems only.
13.
14.
15.
16.
Supported for Linux on Power Systems only.

Limited support provided by virtualization manager.
Not supported for Linux on Power Systems.
The IBM BladeCenter SAS RAID Controller Module function is not supported
on Windows Server 2008.
17. For detailed information about hardware and operating system support
provided by update manager, see Supported updates.
18. On IBM i 5.4 or later, update manager support is provided for IBM Director
Agent 5.20.
19. On guest operating systems, support is provided for Linux updates and IBM
Systems Director agent updates only.
Related reference
IBM Systems Director task support not affected by operating systems
Related information
Supported updates
IBM Systems Director task support not affected by operating

systems
Support for the tasks listed in this section does not depend on the operating system
running on the system. Event Automation Plans, Discovery, Security, Scheduler,
and Navigate Resources are features of IBM Systems Director and their support
does not depend on any resource other than the management server. For
information about tasks whose support is affected by the operating system, the
degree of agent support, or both, see IBM Systems Director support by operating
systems and agents.
The following tasks have specific support statements:
Configuration Manager
This task does not require Common Agent or Platform Agent to function.
These tasks are a function of IBM Systems Director Server.
You can use this task on IBM BladeCenter, System x, and IBM Power
systems. The operating system running on the system does not affect the
support of this task. Configuration Manager performs IP configuration
using out-of-band communication.
External Application Launch
This task is supported by IBM Systems Director Server when installed on
x86-based management servers running Windows or Linux. Using External
Application Launch, you can configure applications to start on any type of
system that has been discovered by your installation of IBM Systems
Director Server. Before you use External Application Launch to configure
Chapter 2. Planning
39
an application to start on a system, you must make sure that the

application runs on the selected system.
Power On/Off
Support for this task can be provided by the service processor installed in
the system, the Wake on LAN feature, or the operating system. The
support varies by hardware platform. For detailed support information, see
the following topics:
v Managing power state settings on IBM BladeCenter and System x
servers
SNMP Management (formerly, SNMP Browser)
This task is supported on any system or device that runs SNMP.
Related reference
IBM Systems Director task support by operating system and agent levels on
page 36
IBM Systems Director task support for BladeCenter products

IBM Systems Director tasks provide support for BladeCenter products. The support
can vary depending on whether it is for the BladeCenter chassis, network devices,
and blade servers.
A BladeCenter unit consists of a chassis, one or two management modules, one or
more network devices (previously called switches, up to a total of four), and one
or more blade servers (up to a total of 14, depending on the model).
The chassis is the physical enclosure that contains the blade servers. The chassis
has one or two management modules that contain a service processor. IBM
Systems Director discovers the chassis and gathers information from the chassis by
way of the management module. You cannot install Common Agent or Platform
Agent on the chassis.
The network device is an SNMP device, and IBM Systems Director considers the
network device to be a managed device.
IBM Systems Director can gather some information from a blade server before
Common Agent or Platform Agent is installed on the blade server. The information
is gathered from the blade server by way of the chassis management module. In
the IBM Systems Director Web interface, the blade server is represented by a
physical platform managed object. However, after you install Common Agent or
Platform Agent on the blade server, it is a managed system, and the features and
functions that you can use on the blade server are comparable to those that you
can use on any managed system.
IBM Systems 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 Systems Director tasks and information about whether you
can use a task on the chassis, network device, or a blade server without Common
Agent or Platform Agent installed. Unless otherwise noted in this documentation, a
task behaves the same for blade servers as for any managed system.
Note: When Common Agent or Platform Agent is installed on a blade server, the
supported tasks depend on the operating system that is installed on the blade
server.
40
Table 9. IBM Systems Director task support for BladeCenter products

Tasks and subtasks
Chassis
Network
device
Blade server without Common Agent or

Platform Agent installed
Yes
No
Not applicable
Event Automation Plans
Yes
Yes
Yes
Problems
Yes
No
Inventory
Yes
Yes
Yes
Power On/Off
No
No
Yes
Not applicable
Yes
No
Remote Monitors
No
Yes
No
SNMP Browser
No
Yes
Yes
Remote Command Line
Yes
1. Inventory of the chassis, network device, and blade servers can be obtained through the management module.
Blade server inventory that is collected through the management module is a subset of the total inventory that is
available if Common Agent or Platform Agent is installed on the blade server.
2. To use the SNMP Browser task, the operating-system SNMP agent must be installed on the blade server.
IBM Systems Director task support for Storage products

IBM Systems Director provides limited task support for Storage products.
Table 10. IBM Systems Director task support for Storage products
DS300
DS400
DS4000
Brocade switches
DS6000
QLogic BladeCenter switches
Event Automation Plans1
Yes
No
Event Log
Yes
Yes
External Application Launch
Yes
Yes
Problems
Yes
Yes
Inventory
Yes
Yes
Tasks and features
1. Indicates that the Storage product generates events. Events are detected for use in event automation plans.
National languages supported by IBM Systems Director

IBM Systems Director provides support for many national languages.
IBM Systems Director Server, IBM Systems Director Web interface, Common Agent,
and Platform Agent are all enabled for the following set of national languages:
v Brazilian Portuguese
v Chinese (simplified)
v Chinese (traditional)
v English
v French
v German
v Italian
v Japanese
v Korean
v Spanish
Notes:
Chapter 2. Planning
41
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. 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 Systems Director information center.
4. 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 Systems Director environment will support a
national language, consider the following criteria:
v Your selected operating system must support your selected national language.
v IBM Systems Director must support your selected operating system.
v IBM Systems Director must support your selected national language.
Planning to install IBM Systems Director

Any time that you upgrade or install IBM Systems Director, complete the planning
steps before starting the actual installation to ensure that your installation is
successful and meets your needs.
Service and support information

Service and support offerings for IBM Systems Director are based on the platform
on which you choose to run IBM Systems Director Server.
For IBM Systems Director Server running on IBM BladeCenter or System x
systems, subscription services are available for a fee entitling you to notification of
new upgrades, patches and support information, and free updates during that
period. For more information about subscription services or to renew your
subscription service contract, see the Ready to Buy Web Page at
www.ibm.com/systems/management/director/subscription/.
For more information about service and support offerings available for all IBM
systems, see Support Offerings Web site at www.ibm.com/systems/support/
supportsite.wss/docdisplay?lndocid=MIGR-5076601&brandind=5000016 or contact
your IBM representative or IBM Business Partner.
Related reference
IBM Subscription Services
IBM Director support offerings
Reviewing the environment

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

Begin the planning process by identifying the systems and devices that you want
to manage with IBM Systems 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 Systems
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 Power systems, 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 hardware requirements section in the Hardware and software
requirements section of the IBM Systems Director documentation.
Identify the systems and devices that you will manage with IBM Systems Director.
1. Ensure that all systems and devices are correctly installed and cabled.
2. Record information about those systems and devices in Table 11. You can use
this information to verify that your managed systems and devices have been
discovered, to manually add systems or devices in IBM Systems Director, or to
plan managed-resource groups or user roles based on the types or locations of
managed systems and devices.
Table 11. Hardware identification worksheet for IBM Systems Director
System or device
type
Operating system (if

applicable)
Physical location
Network address
Chapter 2. Planning
43
Table 11. Hardware identification worksheet for IBM Systems Director (continued)
System or device
type
Operating system (if

applicable)
Physical location
Network address
Related reference
Hardware and software requirements on page 17
Identifying local and remote subnets

You need to provide local and remote subnet information in order for IBM Systems
Director to discover resources.
Identify the local and remote subnets in which the systems that you want to
manage with IBM Systems Director are located, and record this in Table 12
Table 12. Local and remote subnets worksheet
Information to gather for discovery
Values
___.___.___.___
___.___.___.___
___.___.___.___
IP addresses or IP-address ranges for unicast ___.___.___.___
discovery of Agentless managed systems.
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
Unicast Addresses for Agentless managed
system discovery
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
Directory agent server for Platform Agent

discovery
Service Location Protocol (SLP) directory
agent server for discovery of Platform Agent
managed systems.
SLP scope for Platform Agent discovery
Service Location Protocol (SLP) scope for
discovery of Platform Agent managed
systems.
___.___.___.___
___.___.___.___
___.___.___.___
IP addresses or IP-address ranges for unicast ___.___.___.___
discovery of Common Agent managed
___.___.___.___
systems.
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
Unicast Addresses for Common Agent
discovery
44
Table 12. Local and remote subnets worksheet (continued)

Information to gather for discovery
Values
Subnets for Common Agent discovery
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
TCP/IP addresses and subnet masks for

broadcast and relay discovery of Common
Agent managed systems.
Multicast group for Common Agent

discovery
/
/
/
/
/
/
/
/
/
/
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
multicast group: ___.___.___.___

time to live: _______
Multicast group TCP/IP address and

time-to-live value for multicast discovery of
Common Agent managed systems.
Subnets for discovery of SNMP devices
TCP/IP addresses and subnet masks for
discovery of simple network management
protocol (SNMP) devices.
Community names for discovery of SNMP

devices
Community names for discovery of simple
network management protocol (SNMP)
devices.
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
/
/
/
/
/
/
/
/
/
/
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
___.___.___.___
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
_________________________________
SLP profiles for discovery of SMI-S storage _________________________________

devices
_________________________________
_________________________________
Service Location Protocol (SLP) profiles for
_________________________________
discovery of SMI-S devices.
_________________________________
_________________________________
_________________________________
_________________________________
Identifying firewalls and blocked ports

Review the firewalls and blocked ports in your installation environment in order to
identify potential barriers to IBM Systems Director access, and to plan how to
implement IBM Systems Director management without creating security gaps.
IBM Systems Director must be able to access all the managed resources 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 Systems Director might require access to the Internet.
Chapter 2. Planning
45
Tip: If you have a wide area network (WAN) link, use a T1 line that transmits at a
speed of at least 1.5 megabytes per second (MBps) to ensure reliable network
performance.
Related reference
All available ports on page 22
Version compatibility of IBM Systems Director version 6.1

components
Some IBM Systems Director 6.1 components can work with IBM Systems Director
components from previous versions of the software.
Important: The version of IBM Systems Director Server must always be the same
or later than the version of any Common Agent or Platform Agent installed on
managed systems.
See the following table for a complete listing of compatible IBM Systems Director
component versions for each IBM Systems Director Version 6.1 component.
Table 13. Compatibility of IBM Systems Director Version 6.1 components with other
component versions
IBM Systems
Director Version 6.1
Compatible versions
of IBM Systems
Compatible versions Compatible versions
Director Server
of Common Agent
of Platform Agent
IBM Systems Director N/A

Server 6.1
6.1; IBM Director

For Power Systems
Agent versions 5.20.3, servers:
5.20.2, 5.20.1, 5.20
v Platform Agent
5.20.3 for Linux on
Power Systems
v IBM i Platform
Agent (available
with 5722-UME)
For System x servers:
v Platform Agent
5.20.31 for
Windows
v Platform Agent
5.20.31 for Linux
on System x
For System z servers:
v Platform Agent
5.20.3 for Linux on
System z
For Cell Broadband
Engine:
v Platform Agent
5.20.3 for Cell
Broadband Engine
IBM Director Core
Services versions
5.20.3, 5.20.2, 5.20.1,
5.20
Common Agent 6.1
46
6.1 and later
N/A
N/A
Table 13. Compatibility of IBM Systems Director Version 6.1 components with other
component versions (continued)
IBM Systems
Director Version 6.1
Compatible versions
of IBM Systems
Compatible versions Compatible versions
Director Server
of Common Agent
of Platform Agent
Platform Agent 5.20.3 6.1 and later

for:
N/A
N/A
N/A
N/A
N/A
N/A
v Linux on Power
Systems
v Linux on System z
v Cell Broadband
Engine
Platform Agent
5.20.31 for:
5.20.3, 6.1 and later
v Windows
v Linux on x86
IBM i Platform Agent 6.1 and later
Important: IBM Systems Director version 6.1 is not compatible with any versions
of IBM Director extensions that are supported by IBM Director version 5.20 or
earlier. For detailed information, see Whats new in version 6.1.
License information
Before deploying this product, ensure that you have the necessary licenses.
IBM Systems Director

IBM Systems Director contains management server and agent components, and
you are authorized to use the components on IBM systems. You are not
authorized to run IBM Systems Director Server on non-IBM systems.
You are authorized to manage non-IBM systems that run Platform Agent and
non-IBM systems without an agent. See the hardware and software requirements
for more information about supported systems.
You are authorized to use management server and agent components only on
IBM systems. Notwithstanding the foregoing, the IBM Systems Director includes a
license for up to 20 installations of the agent component on non-IBM x86 systems.
These 20 licenses for non-IBM x86 systems are not transferable and cannot be
combined or aggregated. For example, if you buy two IBM systems and install
IBM Systems Director on only one of them, you are entitled to install the agent
component on only 20 non-IBM x86 systems. If you install IBM Systems Director
on both IBM systems, your entitlement is limited to managing 20 non-IBM x86
systems. To install additional agent components on non-IBM x86 systems, you
must obtain additional agent component licenses from IBM. You can purchase
licenses from the Ready to Buy Web Page at www.ibm.com/systems/
management/director/buy/
IBM may audit your compliance with these terms upon reasonable advance notice
to you.
Chapter 2. Planning
47
Database
IBM Systems Director Server uses a database to store data. You can use the Apache
Derby database that is included with IBM Systems Director without obtaining
additional licenses. If you choose to install and use a different supported database,
ensure that you have obtained any required license for the installation.
Obtaining licenses for Common Agent

IBM Systems Director includes licenses for up to 20 installations of Common Agent
on non-IBM x86 systems. To install Common Agent on additional non-IBM x86
systems, you must obtain a license from IBM.
1. Determine which non-IBM x86 systems require Common Agent licenses.
2. Obtain licenses for each installation of Common Agent on non-IBM x86 systems
from the Ready to Buy Web Page at www.ibm.com/systems/management/
director/buy.html.
Related concepts
License information on page 47
Choosing the IBM Systems Director Server installation

options
When you install IBM Systems Director Server using a standard installation, you
must specify various options for your installation.
Complete the following steps to choose your installation options:
1. Determine the location where you want to install IBM Systems Director Server.
By default, IBM Systems Director Server is installed in the following locations.
Table 14. Default locations in which IBM Systems Director Server is installed
Operating System
Location
Linux or AIX
/opt/ibm/director
Windows
d:\Program Files\IBM\Director
where d is the drive letter of the hard disk drive.
2. Determine the IBM Systems Director service account information. You need to
provide the following information when you install IBM Systems Director
Server:
v Computer name
v User name
v Password
Choosing where to install IBM Systems Director Server

Before installing IBM Systems Director, you must choose one or more management
servers on which you will install IBM Systems Director Server.
A number of factors should influence your choice of management servers,
including the kind, number, and distribution of the systems and objects you will be
managing, the tasks you will be performing with IBM Systems Director, and the
database you will use. In some cases, you might want to install more than one
instance of IBM Systems Director Server.
48
When deciding where to install IBM Systems Director Server, evaluate the
following considerations:
v Consider installing IBM Systems Director Server on a blade to manage a IBM
BladeCenter chassis. IBM IBM BladeCenter chassis can be managed using IBM
Systems Director Server installed either on a blade in the IBM BladeCenter, or on
a separate management server. Refer to Preparing to manage a IBM
BladeCenter on page 109 for detailed information.
v Do not install IBM Systems Director Server on a system that is running only
IPv6, which is not supported.
v For Windows installations, do not install IBM Systems 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 Systems Director Server on a domain controller and then
demote the domain controller, you no longer can access IBM Systems Director
Web interface.
Unless the IBM Systems Director service account has domain administrator
privileges, you cannot restart IBM Systems Director Server.
v Consider installing multiple instances of IBM Systems Director Server. Installing
IBM Systems Director Server on multiple management servers can be helpful in
the following situations:
You want to manage more than 5000 Common-Agent managed systems. With
the IBM Systems Director Server license, you can manage only up to 5000
Common-Agent managed systems, if you have licenses for Common Agent
on those managed systems. The number of Agentless-managed systems and
Agentless-managed systems that you can manage is limited only by the
available resources of the management server and the network.
The systems that you want to manage are in several geographic locations or
are owned by multiple system administrators.
You want to manage each IBM BladeCenter with an installation of IBM
Systems Director Server on a blade in the chassis.
v Consider the kind of database you want to use. You might want to use a
particular database for IBM Systems Director data, to facilitate data-mining
activity or for other reasons. Not all databases are supported for all IBM Systems
Director Server installation locations. See Choosing the IBM Systems Director
database application for detailed information.
v Consider the extensions you want to install, and their requirements.
Some extensions can require large amounts of storage. Select a management
server (or multiple management servers) on which you can install extensions
and expect it to continue functioning even if the network grows.
The External Application Launch Wizard requires that IBM Systems Director
Server be installed in the default installation path.
Choosing the IBM Systems Director database application

Some IBM Systems Director functions require use of an external database, but not
all databases support the same functionality with IBM Systems Director. Choose a
supported database that meets the needs of your installation.
Note: If you install IBM Systems Director Server using the basic installation
option, the Apache Derby database is installed.
Chapter 2. Planning
49
IBM Systems Director Server uses a database to store inventory information in a

central location. You can then use this inventory information to manage your
assets.
Before you install IBM Systems Director Server, decide the database that you want
to use.
On all operating systems except IBM i, the Apache Derby database is embedded
with the IBM Systems Director Server installation. For IBM i, IBM Systems Director
Server can use the IBM DB2 Universal Database that is part of the IBM i operating
system.
Complete the following steps to determine the appropriate database application for
your installation of IBM Systems Director.
1. Review the advantages and disadvantages of the different database installation
types.
Table 15. Advantages and disadvantages of different DBMS installation types
DBMS installation type
Advantages
Disadvantages
Embedded DBMS
The DBMS is
installed on the
management server
as part of the IBM
Systems Director
Server installation,
and shares the Java
Virtual Machine
with IBM Systems
Director.
v Configuration is easy.
v Apache Derby database

limitation: The number of
managed objects is limited.
v No additional license is
required.
v Resource usage is lower
than that of a local DBMS
installation.
v A separate server for the
DBMS is not required.
v Apache Derby database

limitation: You cannot
query databases with an
application acquired from
another vendor while IBM
Systems Director Server is
running.
v Not available on IBM i.
Local DBMS
The DBMS is
installed on the
management server
on which IBM
Systems Director
Server is installed.

DBMS is not required.
v Resource usage on the

management server is the
highest of the DBMS types.
Remote DBMS
The DBMS is
installed on a
different server than
the management
server, and accessed
remotely by IBM
Systems Director
Server.
v Resource usage on the

management server is the
lowest of the DBMS types.

DBMS is required.
v You can use an existing

DBMS and avoid
purchasing an additional
DBMS license.
v Connectivity problems
with the database server
will affect IBM Systems
Director.
2. Review the supported databases for your management server and the type of
installation that you prefer. Depending on where you are installing IBM
Systems Director Server, you have one or more possible choices for your
database. See Supported database applications. for further information.
3. Review the information in Table 16 on page 51 to determine the database that
best meets your needs. For the following additional criteria, not all databases
provide the desired function.
50
Table 16. Additional database selection criteria
Database
Can access data with

a tool acquired from
another vendor while
IBM Systems
Director is running
Can handle a large

managed network (>
~500 managed
objects)
Apache Derby
No
No
IBM DB2 Universal Database
Yes
Yes
Microsoft SQL Server 2005
Yes
Yes
Microsoft SQL Server 2005 Express Edition
Yes
No
Yes
Yes
Oracle Database
These criteria are described more fully, including database recommendations,

below:
Can access data with a tool acquired from another vendor while IBM
Systems Director is running
Applications cannot use Apache Derby while IBM Systems Director is
using the database instance. Instead, IBM DB2 Universal Database,
Microsoft SQL Server, or Oracle Database are good choices if you have
this requirement.
Can handle a large managed network (> ~500 managed objects)
If you will be managing a large network (approximately 500 or more
managed objects), Apache Derby is probably not sufficient to meet your
database needs.
Related reference
Supported database applications on page 35
Choosing the management level for managed systems

IBM Systems Director provides three different levels of management for managed
systems and managed objects. For each managed system, you need to choose the
management level that provides the management functionality you need for that
managed system.
Depending on the type of managed system and the management tasks you need to
perform, you can choose the best management level for the managed system. IBM
Systems Director has three management levels:
Agentless
Managed systems without any IBM Systems Director software installed.
Platform Agent
Managed systems with Platform Agent installed.
Common Agent
Managed systems with Common Agent installed.
These three management levels have different requirements and provide differing
levels of management functionality in IBM Systems Director.
For each managed system, review Table 17 on page 52 and decide what level of
management is required.
Chapter 2. Planning
51
Table 17. Management-level selection worksheet4

Criteria
Agentless
Platform
Agent
Common
Agent
Managed system types

IBM systems running AIX
X1
IBM systems running IBM i
IBM systems running Linux
IBM systems running Linux and supporting

either the SSH 5 or DCOM 6 protocol
IBM systems running Windows
X2
X
IBM systems running Windows and supporting

either the SSH or DCOM protocol
Non-IBM systems running Linux and supporting

either the SSH or DCOM protocol
Non-IBM systems running Windows and

supporting either the SSH or DCOM protocol
Other managed resources, including management

processors supporting SSH, racks, and SNMP
devices
Managed system attributes

Managed system has a supported
workgroup/enterprise management agent
installed
Minimal additional memory constraint on

managed system
No additional memory constraint on managed

system
No Common Agent license required
No software required on managed system
Needed functionality
Asset ID
Event automation plans
X
7
Event log
File Transfer
Active Status
Service and Support Manager (Linux and

Windows)
virtualization manager (Linux & Windows)
Remote control (Windows only)
Remote session to all supported managed

systems and devices
52
Remote session to SNMP devices and systems

supporting SSH
Restart the managed system
Upgrade to Platform Agent
Upgrade to Common Agent
Notes:
1. Agentless management is supported only with SSH, and it is limited agentless
support.
2. Common Agent is supported with and without SSH.
3. Platform-Agent managed system support is not provided by the Platform Agent
but by the 5722UME product.
4. In this table, systems include servers, desktop computers, workstations, and
mobile computers.
5. SSH = Secure Shell
6. DCOM = Distributed Component Object Model
7. Event-automation plans can be applied to Agentless managed systems;
however, most of the events that can trigger an event-automation plan are not
generated for Agentless managed systems.
8. Not supported in version 5.20.2 on Windows Vista.
Planning for virtual environments

To fully enable the management capabilities of IBM Systems Director for your
virtual resources, ensure your environment is set up correctly. In most cases, you
need to install the required software on the host systems in your environment. The
required software varies, depending on the type of resources in your environment.
Install the following software on the host systems according to your virtual
environment:
v Hardware Management Console environment:
No agent or subagent software is needed.
v Integrated Virtualization Manager environment:
v Microsoft Virtual Server environment:
Common Agent
Virtualization manager subagent
v VMware ESX Server environment:
Common Agent
Note: If the VMware ESX host is being managed by VMware VirtualCenter
running on Windows, it is recommended that you do not install the
virtualization manager subagent for VMware ESX Server.
v VMware ESXi managed by VMware VirtualCenter environment:
v VMware VirtualCenter environment:
Common Agent
v Xen environment:
Platform Agent
v IBM z/VM environment:
Platform Agent
IBM z/VM Manageability Access Point Agent
Chapter 2. Planning
53
Note: The IBM z/VM Manageability Access Point Agent is installed on a

supported version of Linux that is running as a guest on the z/VM 5.4 operating
system.
Related reference
IBM Systems Director task support by operating system and agent levels on
page 36
Disaster recovery for IBM Systems Director 6.1

To protect your IBM Systems Director 6.1 data from a disaster, backup your data
using commands provided by IBM Systems Director. In addition to disaster
situations, it is possible that a situation can occur that might cause IBM Systems
Director to enter an undesired state, for example, IBM Systems Director Server no
longer starts. You can use data-set restoration to return IBM Systems Director to its
last known good state. Before you backup your data, you must determine the
circumstances in which you intend to restore your data.
Choosing between backup and migration

When you backup your IBM Systems Director 6.1 data, you must restore the
backup to a server that meets the following criteria:
v The same type of server hardware as the previous installation. For example, you
cannot backup data on a System x server and restore the data to an IBM Power
server.
v The same version of operating system. For example, you cannot backup data
from a server running Red Hat Enterprise Linux 4.0 to a server running Red Hat
Enterprise Linux 5.0. However, the service pack or update can vary, for example,
you can backup data from a server running Red Hat Enterprise Linux 4.0
(Update 6) to a server running Red Hat Enterprise Linux 4.0 (Update 7).
v The same version of the database application.
v The same version of IBM Systems Director. For example, you cannot backup data
from an IBM Systems Director 6.1 management server and restore the data to an
IBM Director Server 5.20 management server.
Important: If your intention is to migrate your IBM Systems Director 6.1
installation to a configuration with a different server platform, operating system, or
database application, you cannot use the commands provided for simple backup
and disaster recovery. Migrating an IBM Systems Director 6.1 installation is not
supported at this time. For information about migrating an IBM Director, version
5.20, installation to IBM Systems Director 6.1, see Upgrading and migrating IBM
Systems Director.
For detailed information about the smsave and smrestore commands, see smsave
commands and smrestore commands.
Backing up data for disaster recovery

The smsave command backs up all data associated with IBM Systems Director,
including any file-system data and database data. Save and keep the backup
output in a remote location from the management server location. You must
determine the backup frequency based on your business need. In some situations,
even a days worth of lost data is too much loss.
54
Important: If you have a remote database, the smsave command produces two
data-sets: one at the location of the remote database server and the other on the
IBM Systems Director management server system. The data-sets are mated sets.
You must maintain and restore these data-sets together.
In a disaster situation, before you restore your IBM Systems Director data, you
must first install IBM Systems Director on a new server. Make sure the server
meets the criteria described in Choosing between backup and migration. Then,
restore the most recent backup data set using the smrestore command.
Note: The IP address of the management server and the database server can
change from the original installation without any affect.
Planning for events

An event is an occurrence of a predefined condition relating to a specific system.
There are two types of events: alert and resolution. An alert is the occurrence of a
problem relating to a system. A resolution is the occurrence of a correction or
solution to a problem relating to a system.
Note: In the IBM Systems 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 Common Agent
v Platform Agent
v Microsoft Windows event log
v Windows Management Instrumentation (WMI)
v SNMP through out-of-band communication
v Intelligent Platform Management Interface (IPMI) Platform Event Traps (PET)
through out-of-band communication
v IBM service processors through out-of-band communication
Successful use of event notification depends on careful planning. Consider the
following questions:
1. Which events can be monitored on the system?
a. Which of these events are useful to my management strategy?
b. What configuration is required for the system to send event notifications?
2. How should event notifications be sent to IBM Systems Director?
See the IBM Systems Director Events Reference for additional information.
Planning events to be monitored

Before configuring IBM Systems Director and your managed systems, you should
plan how events will be sent to IBM Systems Director and how event notifications
will be sent to the personnel who need to receive them.
v Consider how events will be sent by the managed systems to IBM Systems
Director Server. When IBM Systems Director discovers IBM service processors
or BladeCenter management modules, it automatically configures them to send
events using in-band communication with IBM Systems Director Server. For
Chapter 2. Planning
55
detailed information about communication with management modules and

service processors, see Service processor communication.
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 automation plan, you can configure IBM Systems Director to
send notification of particular events or event types using 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 Systems Director using means such as
SNMP traps or e-mail. This kind of event notification is not enabled by
default, but can be configured using the BladeCenter Configuration Manager
task in IBM Systems Director or through a direct connection to the service
processor or management module. These events are broken down into the
following three categories:
- Critical events, such as Temperature outside critical thresholds or Power
supply failure.
- Warning events (non-critical), such as Redundant power supply failure or
Voltage outside warning thresholds.
- System events, such as Power off, Server loader timeout value is exceeded,
or Predictive Failure Analysis (PFA) notification.
Notes:
For SNMP, decide which version of SNMP to use (v1 or v3). Enable traps and
the SNMP agent, and configure the IP address. If using SNMPv1, configure
the community name. If using SNMPv3, configure the user profile.
For e-mail notifications, configure the SMTP server.
If you enable timeout events (alerts), you also must plan to enable those
timeouts.
Planning for event automation plan implementations

To plan and design an event automation plan, you must determine what the goal
of the event automation plan is.
Consider which systems you intend to target with the event automation plan. You
can target all systems, a subgroup of systems, or a specific system.
56
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 automation plans might include each of the elements of each of the
structures that are presented.
When designing your event automation plan structure, consider all the systems in
groups. Start by designing an event automation plan that contains events that
apply to the largest number of objects. Then, create event automation plans that
cover the next largest group of systems, and continue to group them until you
reach the individual managed-object level. When doing this, remember that each
system can be a member of multiple groups.
When planning an event automation plan structure, consider the following issues:
v What do you want to monitor on most or all of the systems of the same type as
a whole? This answer determines the grouping and event filters for your event
automation plans.
v How will you group your systems 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 system, for services and resources specific to that function
v What type of systems are you monitoring?
v What is the function of the system?
v What are the key monitors for the system?
v Are there other systems for which you want to use the same monitors?
Managing and monitoring systems with event automation plans

You can use event automation plans to specify actions that occur as a result of
events that are generated by a system.
An event automation plan is composed of two types of components:
v One event filter, which specifies event types and any related parameters.
Note: The Event Automation Plan wizard creates an event filter for you when
you select common event types.
v One or more event actions, which occur in response to filtered events
You can apply an event automation plan to an individual system, several systems,
or a group of systems.
By creating event automation plans and applying them to specific systems, 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 automation plan to
start a program on a system and change a system variable when a specific event
occurs. You can use process-monitor events and resource-monitor events to build
an event automation plan.
Successful implementation of event automation plans requires planning and
consideration of how you will implement them.
Planning system grouping

Event automation plans are best implemented by grouping all of your systems into
both larger and smaller groups.
The following criteria are examples of groupings:
Chapter 2. Planning
57
Type of system or resource (servers, desktop computers, workstations, mobile

computers, and network equipment)
Each type of system or resource has its own event automation plans.
By manufacturer
Each system manufacturer has its own event automation plans. Many
organizations have systems from multiple manufacturers. In this case, if
manufacturer-specific event monitors are required, you might want to have
manufacturer-specific event automation plans for each type of system.
By function
Each function of the system has its own event automation plans. Each
group of systems performing specific roles has different events to monitor.
For example, on all of your print servers, you might want to monitor the
print spoolers and printers.
By resources
Event automation plans are based on specific resources. Typically, these
event automation plans monitor a specific resource outside of those in the
managed-object type of event automation plan. These resource event
automation plans might apply to systems with more than one system
function but not to all systems of the same type.
By management technology
If you have many devices that send SNMP traps, you can design event
automation plans to act on those events.
Structuring event automation plans

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

You can use an event filter to capture a single event or multiple events.
58
The following list includes some of the criteria that you can use to determine
whether to include an event with other events:
v All systems that are targeted for the filter are able to generate all events that are
included in the filter. If the system does not generate the event for which the
filter is defined, the filter will not be effective on that system.
v The event actions that will be used to respond to the event are the same for all
targeted systems.
v The other event filter options besides the event type are common for all targeted
systems. These settings include the times the event filter is active, the severity of
the event, and other attributes.
Event automation plans can include event filters with event types that are not
generated by all systems. In such instances, you can apply the event automation
plan to those systems, but it will have no effect. For example, if an event filter is
based on a RAID event and that event automation plan is applied to systems that
do not have a RAID controller 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 automation plans, and you can reduce the number of event
automation plans you have to build and maintain.
Using the Event Automation Plan wizard, you can select common event types to
create an event automation plan quickly and easily. After you become familiar with
the common event type selections, you can decide whether you want to further
refine your event filters using the advanced event filter path in the Event
Automation Plan wizard.
The advanced event filter path provides a tree that displays all currently available
event types. The currently installed plug-ins publish their events in the Event Type
tree when IBM Systems Director Server or Common Agent starts.
Note:
v Whether the events are published when IBM Systems Director Server or
Common Agent starts depends on the plug-ins and how they are implemented.
If you add a plug-in to your IBM Systems Director installation, the plug-in
might publish its events either when it is added to the installation or when the
plug-in sends its first event. If the plug-in publishes when it sends its first event,
only that event is published.
v IBM i message queue events are not displayed in the Event Type tree. Instead,
you can specify message queue events in the IBM i message queue event pane
that is below the Event Type tree.
Planning IBM Systems Director security

Before deploying IBM Systems Director, determine what steps you need to take to
secure your environment.
Planning IBM Systems Director users and groups

Before deploying IBM Systems Director, define user roles for your organization and
determine the user authentication type that will best meet your needs.
1. Decide what kind of user authentication to use for IBM Systems Director.
The user authentication type that you choose (a common Lightweight Directory
Access Protocol (LDAP) server, or accounts on the operating system of the
management server) affects both the availability and security of IBM Systems
Chapter 2. Planning
59
Director Server. IBM Systems Director is shipped with LDAP authentication

support, but it is not enabled by default. LDAP support includes support for
the following LDAP servers:
v IBM Tivoli Directory Server
v Microsoft Active Directory
With LDAP authentication, it is easy to implement common roles and access for
users across multiple instances of IBM Systems Director Server. However, the
LDAP server must be secure in order to avoid unauthorized access to
management tasks and managed objects in IBM Systems Director.
To help you make a decision, consider how IBM Systems Director will be used
to manage systems and objects in various locations. You can start by answering
the following questions:
v Will a single management server be used for the entire organization, or will
multiple management servers be used?
v If multiple management servers will be used, will the same user accounts be
needed on more than one of the management servers, or should user
accounts be unique for each management server?
v Is there an existing LDAP directory, such as IBM Tivoli Directory Server or
Microsoft Active Directory, for your organization?
v How many users will be authorized to access IBM Systems Director?
Note: If you choose to use LDAP, ensure that you create smadmin, smmgr,
smmon, and smuser groups on the LDAP servers.
2. Decide what kind of user roles to define for IBM Systems 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
Systems 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 the types of access that users must have in IBM Systems Director.
Note: The types of access that you grant to users depend on the types of roles
that exist within your environment.
v If management authority is allocated partially based on the kind of managed
object, consider defining user roles for particular operating systems or for
storage devices.
v If management authority is allocated partially based on organizational roles,
consider defining user roles that correspond to sets of privileges and tasks
that can be performed in IBM Systems Director, like software distribution,
inventory collection, and configuring preferences for IBM Systems Director
Server. Depending on the users organizational role, the user probably needs
access to only a subset of the available privileges and tasks.
Other criteria can also be used when defining user roles for IBM Systems
Director. Whatever criteria are used to define user roles, remember that a user
can have multiple roles.
Planning Secure Sockets Layer configuration on IBM Systems

Director
IBM Systems Director Server provides, by default, a Secure Sockets Layer (SSL)
certificate that supports HTTPS connections between IBM Systems Director Server
and targets such as storage devices, agents, and Web browsers. However, to ensure
60
server authentication, data privacy, and data integrity, you must replace the default
certificate with either a self-signed certificate or a certificate that is signed by a
certificate authority (CA), and you must change the keystore password.
It is not required that you use SSL to secure the network traffic between your
management server and targets. However, configuring SSL ensures data integrity
and data confidentiality between the management server and its targets. This
protection is especially important if you access IBM Systems Director from outside
your network.
Note: Make sure that the host name you specify in the Common Name field of the
SSL certificate matches the host name that you specify in the URL that you use to
access the targets. For example, if you specify a long name for the host name in the
Common Name field of the certificate, you must specify a long name in the URL.
If these host names do not match, you might receive errors when you try to access
the targets. Complete the steps in the following procedure to make sure that you
specify the correct host name in the Common Name field of the certificate.
To replace the default certificate with a new certificate and to change the keystore
password for SSL, complete the following steps:
1. Delete the default certificate. For information, see Deleting the default
certificate.
2. Create a new certificate. You can create either a self-signed certificate or request
and receive a CA signed certificate.
v To create a self-signed certificate, see Creating a self-signed certificate.
v To request and receive a CA signed certificate, see Requesting a CA signed
certificate and Receiving a CA signed certificate.
3. Update the Web container properties. For information, see Updating the Web
container properties.
4. Update the targets with the new certificate. For information, see Updating the
targets with the new certificate.
Deleting the default certificate

IBM Systems Director Server provides, by default, a Secure Sockets Layer (SSL)
certificate that supports HTTPS connections between IBM Systems Director Server
and targets such as storage devices, agents, and Web browsers. You must delete
this default certificate before you can replace it with either a self-signed certificate
or a CA signed certificate. Also, you must change the keystore password.
Back up any files before you edit them.
To delete the default certificate, complete the following steps:
1. Stop IBM Systems Director Server by completing the applicable steps:
Option
Description
For Linux
Type the following command: smstop
Chapter 2. Planning
61
Option
Description
For Windows
1. Right-click My Computer and select

Manage.
2. In the Computer Management window,
expand Services and Applications
Services.
3. In the Services pane, right-click IBM
Director Server and select Stop.
4. Exit from the Computer Management
window.
2. Start the IBM Key Management program by typing the applicable command.
Option
Description
For Linux
install_root/jre/bin/ikeyman
For Windows
install_root\jre\bin\ikeyman.exe
where install_root is the root directory of your IBM Systems 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 (/).
3. To open the default keystore file, click Key Database File Open.
4. In the Key database type list, select JKS.
5. Click Browse and navigate to the applicable default keystore file:
Option
Description
For Linux
install_root/lwi/security/keystore/
ibmjsse2.jks
For Windows
install_root\lwi\security\keystore\
ibmjsse2.jks

6. Select the default keystore file and click Open; then, click OK.
7. In the Password Prompt window, specify the default password for the default
keystore file and click OK. The default keystore file password for IBM Systems
Director is ibmpassw0rd.
8. In the Key database content pane, select the default personal certificate named
lwiks and click Delete.
Next, you must create a new certificate.
v If you want to create a self-signed certificate, go to Creating a self-signed
certificate.
v If you want to request a CA signed certificate, see Requesting a CA signed
certificate.
Creating a self-signed certificate

Self-signed certificates are certificates that you create yourself for private use. After
you create a self-signed certificate, you can use it immediately. Because anyone can
create self-signed certificates, they are not considered publicly trusted certificates.
62
Therefore, use self-signed certificates only on a temporary basis while you test
your environment. You can replace the default certificate with a self-signed
certificate.
Before you complete this procedure, you must delete the default certificate. For
information see Deleting the default certificate. Also ensure that you back up any
files before you edit them.
Note: Messages and settings might differ depending on what type of target to
which you are connecting and the version of Java Web Start that you are running.
Important: If you want to request a CA signed certificate, do not perform this
procedure. Instead, see Requesting a CA signed certificate.
To create a self-signed certificate, complete the following steps:
1. In the IBM Key Management program, click Create > New Self-Signed
Certificate.
2. In the Create New Self-Signed Certificate window, in the Key Label field,
specify a label for the new certificate, for example, DirServer.
3. In the Version list, select X509 V3.
4. In the Key Size field, accept the default value.
5. In the Common Name field, specify the fully-qualified host name of the
server for which you are creating the certificate.
6.
7.
8.
9.
10.
11.
12.
Note: This host name must match the host name that appears in the URL you
specify in your Web browser to reach IBM Systems Director Server. In most
cases, you must specify the fully-qualified host name. However, if you use a
short name in your URL, you must specify a short name for the Common
Name.
In the Organization field, type the name of your organization.
In the Country or region list, accept the default value.
In the Validity Period field, specify the lifetime of the certificate in days or
accept the default value.
Click OK.
To change the default keystore file password, click Key Database File
Change Password.
In the Change Password window, specify and confirm a new password and
click OK.
To exit the IBM Key Management program, click Key Database File Exit.
Next, you must update the Web container properties. Go to Updating the Web
Requesting a CA signed certificate

You can request a digital certificate from a certificate authority (CA). Because
certificate authorities are public entities that issue certificates to identify other
entities, CA signed certificates provide a level of public trust. Therefore, this type
of certificate is better suited for your production environment.
Before you complete this procedure, you must delete the default certificate. For
information, see Deleting the default certificate.
Chapter 2. Planning
63
Important: If you are creating a self-signed certificate, do not perform this

procedure.
You must create a certificate-signing request (CSR) to request a digital certificate
from a CA. To create a certificate-signing request, complete the following steps:
1. In the IBM Key Management program, click Create New Certificate
Request.
2. In the Create New Key and Certificate Request window, in the Key Label field,
type a label for the new certificate, for example, DirServer.
3. In the Key Size field, accept the default value.
4. In the Common Name field, specify the fully-qualified host name of the server
for which you are creating the certificate.
Note: This host name must match the host name that appears in the URL you
specify in your Web browser to reach IBM Systems Director Server. In most
cases, you must specify the fully-qualified host name. However, if you use a
short name in your URL, you must specify a short name for the Common
Name.
5. In the Organization field, type the name of your organization.
6. In the Country or region list, accept the default value.
7. In the Enter the name of a file in which to store the certificate request field,
type a file name or click Browse to select a file in which to store the certificate
request, for example, DirServerSecPubCertreq.arm.
8. Click OK.
9. Send the certificate-signing request file to the CA. See the CA Web site for
specific instructions about requesting a new certificate. You can request either a
test certificate or a production certificate from the CA. However, in a
production environment, you must request a production certificate.
Next, you must receive the CA signed certificate. Go to Receiving a CA signed
certificate.
Receiving a CA signed certificate

After the certificate authority (CA) accepts the certificate-signing request, the CA
processes the request and verifies your identity. The CA sends the signed certificate
back to you by way of e-mail. You must receive and save the new certificate in the
default keystore file.
Before you complete this procedure, you must create and submit a
certificate-signing request. For information see Requesting a CA signed
certificate. Also ensure you back up any files before you edit them.
Notes:
1. Messages and settings might differ depending on what type of target to which
you are connecting and the version of Java Web Start that you are running.
2. This procedure documents how to receive a signed certificate with a file
extension of .arm from a CA into the IBM Key Management program. If your
certificate has a different file extension, see the IKeyMan Users Guide. Go to the
IBM Support and Download Web site at www.ibm.com/support/us and
search using the document number SC23-6510-00.
If you are importing a certificate with a file extension of .pfx and errors
indicate that the certificate store is corrupt, see Resolving the iKeyman Corrupted
Database Message. Go to the IBM Support and Download Web site at
www.ibm.com/support/us and search using the reference number PRS2855.
64
Important: If you are creating a self-signed certificate, do not perform this

procedure.
To receive a CA signed certificate, complete the following steps:
1. If the CA sends the new certificate to you as part of an e-mail message, you
must cut and paste the certificate from the e-mail message and save it in a
certificate file, for example, DirServerSecPubCert.arm.
Note: The e-mail message from the CA might include supplemental text in
front of the certificate and after the certificate. For example, you might see the
text BEGIN CERTIFICATE in front of the certificate and END CERTIFICATE after
the certificate. In this case, make sure that you cut and paste the supplemental
text along with the certificate text.
2. Save the certificate file in the applicable directory:
Option
Description
For Linux
install_root/lwi/security/keystore
For Windows
install_root\lwi\security\keystore

3. Start the IBM Key Management program by typing the applicable command.
Option
Description
For Linux
install_root/jre/bin/ikeyman
For Windows
install_root\jre\bin\ikeyman.exe

4. To open the default keystore file, click Key Database File Open.
5. In the Key database type list, select JKS.
6. Click Browse and navigate to the applicable default keystore file:
Option
Description
For Linux
install_root/lwi/security/keystore/
ibmjsse2.jks
For Windows
install_root\lwi\security\keystore\
ibmjsse2.jks

7. Select the default keystore file and click Open; then, click OK.
8. In the Password Prompt window, specify the default password for the default
keystore file and click OK. The default keystore file password for IBM
Systems Director is ibmpassw0rd.
9. In the Key database content pane, select Personal Certificates from the list.
10. Click Receive.
Chapter 2. Planning
65
11. In the Receive Certificate from a File window, in the Data type list, select
Base64-encoded ASCII data.
12. In the Certificate file name field, specify the name of the certificate file that
you created when you received the certificate from the CA, for example,
DirServerSecPubCert.arm.
13. In the Location field, specify the applicable directory path:
Option
Description
For Linux
install_root/lwi/security/keystore
For Windows
install_root\lwi\security\keystore
14.
15.
16.
17.

Click OK.
In the Enter a Label window, specify a label for the certificate, for example,
DirServerSec.
Click OK.
Optional: Add the public version of the CA signed certificate to the truststore
file of targets.
The public version of the certificate contains all identifying information as
well as the public key associated with the certificate. This optional step can
provide additional security within your SSL configuration. Each target can
determine whether the server presents a certificate that is signed by a trusted
signer. If the target determines that the certificate is not signed by a trusted
signer, it displays a warning which alerts you to a possible security breach.
Configuring SSL for targets is specific to each target. See the documentation
for the chosen target for instructions.
18. To change the default keystore file password, click Key Database File
Change Password.
19. In the Change Password window, specify and confirm a new password and
click OK.
20. To exit the IBM Key Management program, click Key Database File Exit.
Next, you must update the Web container properties. Go to Updating the Web
Updating the Web container properties

Because you changed the keystore password, you must update the Web container
properties with the new keystore password.
Before you perform this procedure, you must create a new certificate. You can
create either a self-signed certificate or request and receive a CA-signed certificate:
v To create a self-signed certificate, see Creating a self-signed certificate.
v To request and receive a CA signed certificate, see Requesting a CA signed
certificate and Receiving a CA signed certificate.
Ensure that you back up any files before you edit them.
To update the Web container properties, you do not edit properties directly within
the webcontainer.properties file. Instead, you must create a file named sslconfig in
the same directory, edit the properties in the sslconfig file, and restart IBM Systems
66
Director Server. The process of restarting IBM Systems Director Server encrypts the
new password in the Web container properties.
Note: Messages and settings might differ depending on what type of target to
which you are connecting and the version of Java Web Start that you are running.
To update the Web container properties, complete the following steps:
1. Change to the applicable directory:
Option
Description
For Linux
install_root/lwi/conf
For Windows
install_root\lwi\conf

2. Change the name of the webcontainer.properties file to
webcontainer.properties.bak.
3. In the same directory, create a file named sslconfig and copy the contents of
webcontainer.properties.bak to the sslconfig file.
4. Using a text editor, edit the sslconfig file.
Notes:
a. Specify only plain text values for the passwords in the sslconfig file.
b.
5. Specify com.ibm.ssl.keyStorePassword.secure_port=new_password Where
v secure_port is the secure port that IBM Systems Director Server uses. Use the
secure port value indicated in your properties file.
v new_password is the password that you set in one of the following steps:
Step 11 on page 63 in Creating a self-signed certificate
Step 19 on page 66 in Receiving a CA-signed certificate
6. Specify the default password ibmpassw0rd for the truststore file, in plain text:
com.ibm.ssl.trustStorePassword.secure_port=ibmpassw0rd
where secure_port is the secure port that IBM Systems Director Server uses.
Use the secure port value indicated in your properties file.
7. Delete the line sslEnabled=true from the sslconfig file.
8. Save the sslconfig file.
9. Restart IBM Systems Director Server by completing the applicable steps.
Option
Description
For Linux
Type the following command: smstart
For Windows
1. Right-click My Computer and select

Manage.
2. In the Computer Management window,
expand Services and Applications
Services.
3. In the Services pane, right-click IBM
Director Server and select Start.
4. Exit from the Computer Management
window.
Chapter 2. Planning
67
When you restart IBM Systems Director Server, the sslconfig file is used to
automatically create a new webcontainer.properties file and encrypt the new
password in this file. After the new webcontainer.properties file has been
created, IBM Systems Director Server deletes the sslconfig file because it is no
longer needed.
10. After you start and connect to IBM Systems Director Server, you can delete
the webcontainer.properties.bak file manually.
Next, you must update the target with the new certificate. Go to Updating the
target with the new certificate.
Updating the target with the new certificate

You must update the target with the new certificate.
Before you perform this procedure, you must update the Web container properties.
For information see Updating the Web container properties.
To update the target with the new certificate, complete the following steps.
Note: If you performed step 17 on page 66 in Receiving a CA signed certificate
or if the public version of the CA signed certificate is already stored in the browser
truststore file, go to step 11. Some targets contain the public version of well known
CA signed certificates.
1. In a Web browser, type the following URL to point to IBM Systems Director
Server: http://server_name:port_number/ibm/console, where server_name is
the host name of IBM Systems Director Server and port_number is the port for
IBM Systems Director Server. The default port is 8421.
Option
Description
For Microsoft Internet Explorer
A Security Alert window is displayed, for

example, you might see the following
message: The security certificate was
issued by a company you have not chosen
to trust. View the certificate to
determine whether you want to trust the
certifying authority. Continue to step 2.
For Firefox
A Website Certified by an Unknown

Authority window is displayed. Click
Accept this certificate permanently and
then click OK. You Web browser is updated
with the new certificate.
2.
3.
4.
5.
6.
7.
8.
9.
10.
In the Security Alert window, click View Certificate.

In the Certificate window, click Install Certificate.
In the Certificate Import Wizard, on the Welcome page, click Next.
On the Certificate Store page, select the way that you want to store the
certificate and click Next.
On the Summary page, click Finish. A Security Warning window is displayed.
In the Security Warning window, click Yes.
In the Certificate Import Wizard window, click OK.
In the Certificate window, click OK.
In the Security Alert window, click Yes.
11. When you use a launched task in the IBM Systems Director Web interface, the
following message is displayed: The applications digital signature has
68
been verified. Do you want to run the application? Be sure to select

Always trust content from this publisher and click Yes.
Planning password management in IBM Systems Director

Before deploying IBM Systems Director, plan how you will manage passwords in
your environment.
You are required to supply many different credentials when installing and
configuring IBM Systems Director. If you ever modify the user ID or password of a
credential after specifying it during IBM Systems Director installation and
configuration, you must ensure that any related tasks or other credentials are
properly updated to accommodate the change. For example, if you update the
administrator password in IBM DB2 Universal Database, you must ensure that you
also update references to that password in IBM Systems Director so that you can
still use the application.
The following table lists the primary credentials that are required for IBM Systems
Director installation and configuration along with the tasks that require each
credential. The last column contains information about changing each password in
IBM Systems Director after it is initially set. Use the table to determine links
between the credentials and tasks that might warrant further updates if you
change any one credential to help prevent any problems that you might encounter
while running IBM Systems Director.
Note: This topic does not apply to credentials that you set up and use for
discovery, such as for requesting access, because you use the IBM Systems Director
Web interface to manage those.
Table 18. Installation and configuration user IDs and passwords
Credential type
administrator using the
local operating system
registry
Tasks that require the

Your values credential
Procedure to change the password in IBM

Systems Director
User ID:
Password:
Use the appropriate tools supplied by the local

operating system.
v Determining IBM
Systems Director
service account
information
v Installing IBM
Systems Director
Server
v Logging on to IBM
Systems Director
Server

administrator using an
LDAP registry
User ID:
Password:
v Determining IBM
Systems Director
service account
information
Use the appropriate tools supplied by LDAP.
v Installing IBM
Systems Director
Server
v Logging on to IBM
Systems Director
Server
Database system
administrator
User ID:
Password:
v Preparing the
database for use with
Use the appropriate tools supplied by the

database application.
Chapter 2. Planning
69
Table 18. Installation and configuration user IDs and passwords (continued)
Tasks that require the
Your values credential
Procedure to change the password in IBM

Systems Director
User ID:
Password:
v Preparing the
database for use with
Use a tool that can handle the password

encryption to change the value in the dcm.xml
properties file and also update the
database.properties value used by LWI.
Agent manager resource User ID:

manager
Password:
v Starting IBM Systems

Director Server
(configAgtMgr.sh
script)
Use the cimsubscribe command.
LDAP administrator
v Setting up IBM
Systems Director to
use LDAP for user
authentication
Use the procedure in Authenticating IBM

Systems Director users stored in LDAP to
modify the com.ibm.lwi.LDAPAdminPassword
password value in the security.properties file.
Credential type
Database runtime
database connection
administrator
(DbmsUserId,
DbmsPassword)
70
User ID:
Password:
Chapter 3. Installing IBM Systems Director on the

management server
Prepare your systems and install IBM Systems Director Server on the management
server.
Related concepts
System discovery on page 120
Related tasks
Logging on to IBM Systems Director Server for the first time on page 106
Preparing the management server

Before installing IBM Systems Director Server, make sure that the requirements that
are applicable to your system have been met.
Related tasks
Installing IBM Systems Director on the management server on page 91
Related reference
Preparing the database application

Unless you want to use the default embedded database for your system, you must
prepare the database application for use with IBM Systems Director and configure
them to work together.
Ensure that you have chosen the supported database application that you will use
with IBM Systems Director. See Choosing the IBM Systems Director database
application for information that will help you decide the database application to
use.
The effort required to prepare the database depends on the database application
that you choose. Preparation might include one or more of the following tasks:
v Downloading and installing the applicable database administrator client
v Downloading and installing the applicable Java Database Connectivity (JDBC)
drivers
v Creating a database or server ID
v Configuring and starting a TCP/IP listener
v Setting the authentication mode.
To use a database other than your systems default database with IBM Systems
Director, follow the steps in the appropriate topic to prepare your database
application.
Note: You can install IBM Systems Director before preparing the database, but you
will only be able to use the default Apache Derby database until you configure
IBM Systems Director Server to use a different database.
After the database application is prepared, you can install IBM Systems Director
Server and configure it to connect to the database.
71
Related tasks
Configuring the database application after IBM Systems Director installation on
page 101
Installing IBM Systems Director Server on Windows using the InstallShield
wizard on page 92
Performing an unattended installation of IBM Systems Director Server on
Windows on page 98
Related reference
IBM Systems Director Downloads
IBM Systems Director Best Practices Redwiki
Preparing the IBM DB2 Universal Database

If you choose to use IBM DB2 Universal Database as the database application for
IBM Systems Director, there are some tasks that you need to complete to prepare
your system before you install IBM Systems Director Server.
To prepare the IBM DB2 Universal Database for use with IBM Systems Director,
complete the following tasks before you install IBM Systems Director Server:
1. Install the database server or client. See the Supported database applications
topic for supported versions and installation options.
Important: If you want to run the database on a remote server, you must
install the full administration client with IBM Systems Director Server. The
administration client automatically installs the needed IBM DB2 Universal
Database tools and JDBC drivers.
2. If the IBM DB2 Universal Database server and IBM Systems Director Server
are both installed on a machine running AIX, set the EXTSHM environment
variable to ON to increase the number of shared memory segments to which a
single IBM DB2 Universal Database server process can be attached. EXTSHM
must be exported both in the shell where the IBM Systems Director Server
client application is started and also in the shell where db2start is run. To
configure the EXTSHM environment variable for multiple JDBC connections,
complete the following steps:
a. Before starting the IBM DB2 Universal Database server, run the following
commands:
export EXTSHM=ON
db2set DB2ENVLIST=EXTSHM
db2set -all
b. Open db2profile in an editor and add the following lines:

EXTSHM=ON
export EXTSHM
c. Before starting IBM Systems Director Server, run the following command
in the client session:
export EXTSHM=ON
Note: Always confirm the EXTSHM setting before starting IBM Systems
Director Server or running any command line tools such as cfgdbcmd,
smreset, smsave, or smrestore. If EXTSHM is not set to ON, run the export
EXTSHM=ON command again.
3. Start the database server or client.
4. Create your IBM DB2 Universal Database.
72
5. Create a unique user ID and password on the database server for the runtime
database connection. Ensure that this user ID is not the instance owner of the
database server. The IBM Systems Director cfgdbcmd database configuration
tool will grant the user the correct privileges to manage the database.
Note: If you plan to use smsave or smrestore with IBM Systems Director
Server and the database, you must:
a. Enable password file authentication for the database system administrator
user ID that is used for backup/restore.
b. Ensure that the database system administrator user ID that is used for
backup/restore has write permission to the backup directory so that the
database server can write the database backup image to the backup
directory.
IBM Systems Director does not save the IBM DB2 Universal Database
administrator account user ID and password.
6. Ensure that the following environment variables are correctly set and also set
to be persistent after logoff or reboot:
PATH Add the bin directory under the IBM DB2 Universal Database
installation root directory to the system variable PATH so that IBM
Systems Director tools can access db2cmd.
LD_LIBRARY_PATH (Linux) or LIBPATH (AIX)
For 32-bit machine types, set this variable to <db2_install_root>/lib
or <db2_install_root>/lib32.
Restriction: If your machine type is 64-bit, the IBM DB2 Universal
Database installation will link <db2_install_root>/lib to a 64-bit
driver, which is incorrect. You must use <db2_install_root>/lib32 for
64-bit machine types.
Note: On AIX, if you want IBM Systems Director Server to
automatically start at boot time, you must also set LIBPATH in
/etc/environment.
DB2_HOME (AIX)
Set this variable to <db2_install_root>.
Note: You can automate the task of setting the environment variables on
UNIX. Depending on which UNIX platform you are on, values for the
environment variables are set in either db2profile (for bash or korn shell) or
db2cshrc (for C shell). You can place a call to these files in you .profile (bash
or korn shell) or .login (C shell) file so that, every time you log in, those
variable are set.
7. Complete the following steps to set DB2_WORKLOAD to TPM on the IBM
DB2 Universal Database Server. TPM is a predefined setting that turns on
DB2_SKIPINSERTED, DB2_SKIPDELETED, and DB2_EVALUNCOMMITTED.
Setting DB2_WORKLOAD to TPM improves concurrency through instance
level configuration settings.
Note: You must run the following commands in CLI command mode, not
interactive mode.
a. Ensure that the CLI environment is initialized by running the following
command:
Chapter 3. Installing IBM Systems Director on the management server
73
On Linux or AIX:
db2profile
On Windows:
db2cmd
Note: Registry keys and values are not case-sensitive.
b. Enter the following command to set DB2_WORKLOAD to TPM:
db2set DB2_WORKLOAD=TPM
c. Enter the following command to stop the database instance:

db2stop force
d. Enter the following command to restart the database instance:

db2start
8. Ensure that the IBM DB2 Universal Database administration server is

initialized by running the following command:
DB2ADMIN START
9. Complete the following steps to enable automatic reorg in IBM DB2 Universal
Database.
a. In the IBM DB2 Universal Database Control Center, right-click the
database instance that you want to configure for automatic reorganization
and select Configure Automatic Maintenance. The Configure Automatic
Maintenance wizard is displayed.
b. Click Next.
c. Select Change automation settings.
d. Click Next. The Specify when automatic maintenance activities can run
page is displayed.
e.
f.
g.
h.
i.
j.
Next to the On-line maintenance window, click Change.

Specify a start time of 00:00 and duration of 24.
Click OK.
Click Next.
Click Next. The Select maintenance activity to configure page is displayed.
In the Automate column, select Reorg and RUNSTATS.
k. Click Finish.
10. Provide the following information to the system administrator who will install
IBM Systems Director Server and configure it to use the database or set
options in a database-configuration response file for use with the cfgdbcmd
command:
74
Table 19. Database configuration information and values

Description
Selected database application
Database configuration
attribute
DbmsApplication
Note: If you want to install
Server and configure it by
setting options in a
database-configuration
response file, then the
value for DbmsApplication
must match the Apache
Derby, IBM DB2 Universal
Database, Microsoft SQL
Server, or Oracle Database
value you select.
Value (select or input)

__ v
__ v
__ v
__ v
Apache Derby (Apache Derby)

DB2 (IBM DB2 Universal Database)
SQLServer (Microsoft SQL Server)
Oracle (Oracle Database)
Note: You must enter into the

cfgdbcmd.rsp response file the exact value
for each database as it appears above.
Host name of the server on which the

DbmsServerName
database is installed (not required for
Apache Derby)
Note: For Microsoft SQL Server, if you use
the default instance, then the host name is
just the server name; if you create your
own instance (recommended), then the
host name is servername\instancename.
Custom value:
Database name
DbmsDatabaseName
Custom value:
Note: This value must match the name of
the database that is created in the chosen
database application. For Apache Derby,
the DbmsDatabaseName is always
hatterastc.
Database system identifier (SID) (Oracle

Database only)
SID
Custom value:
Whether the database is local or remote
__ v Local
__ v Remote
DbmsDatabaseAppHome
Fully qualified local installation folder of
the database server instance or admin
client instance on the IBM Systems Director
Server system
Note: This is the location of the SQLLIB
directory. For example, a typical Windows
installation will specify this as C:\Program
Files\IBM\SQLLIB. You can determine the
DbmsDatabaseAppHome value by opening
a IBM DB2 Universal Database command
window and specifying DB2SET DB2PATH.
Custom value:
75
Table 19. Database configuration information and values (continued)

attribute
Description
DbmsTcpIpListenerPort
TCP/IP listener port ID for the database
Note: You can determine the
DbmsTcpIpListenerPort value by opening a
IBM DB2 Universal Database command
window and specifying db2 get dbm
config . Look for the value associated with
SVCENAME. If SVCENAME is a number,
that is the port number. If it is a name
(such as db2c_DB2) you must find the
name in the services file, which is typically
located at C:\WINDOWS\system32\
drivers\etc\ on Windows and at /etc on
Unix. Inside that services file, find the
SVCENAME value that matches the one
returned from the db2 get dbm config
command. It will include a port number.
For example, it may look like db2c_DB2
50000/tcp, which indicates a port number
of 50000.
User ID of the database user account (not
required for Apache Derby)
Note: If you will not use the database
administrator user ID for the runtime
connection, provide a second user with
access to the information collection panel.
DbmsUserId
Password of the database user account (not DbmsPassword


Default or custom value:
Custom value:
Custom value:
After you have prepared the database for use with IBM Systems Director, you can
connect the IBM Systems Director Server to the database either after or during
installation:
Connect the database after installation
You can connect the database after installation regardless of your system
configuration. See Configuring the database application after IBM Systems
Director installation for the procedure.
Connect the database during installation (Windows only)
If you are running on Windows, you also have the option of connecting
the database during installation. See Installing IBM Systems Director
Server on Windows using the InstallShield wizard for the procedure.
Note: The IBM DB2 Universal Database Information Center has current
information about security in IBM DB2 Universal Database. The IBM DB2
Universal Database Information Center is at publib.boulder.ibm.com/infocenter/
db2help/index.jsp.
76
Related tasks
page 101
wizard on page 92
Related reference
DB2 information center
Preparing Microsoft SQL Server

If you want to use Microsoft SQL Server 2005 or Microsoft SQL Server 2005
Express Edition, you must prepare the database for use with IBM Systems Director
before installing IBM Systems Director Server.
Related tasks
page 101
Related reference
Preparing the Microsoft SQL Server 2005 database:
Before installing IBM Systems Director Server, prepare the Microsoft SQL Server
2005 database for use with IBM Systems Director. The Microsoft SQL Server 2005
database can be used with IBM Systems Director Server only on management
servers running Windows.
Complete the following tasks to prepare the Microsoft SQL Server 2005 database
before installing IBM Systems Director Server:
1. Install and start Microsoft SQL Server 2005. See the Supported database
applications topic for supported versions and installation options.
a. Download Microsoft SQL Server 2005 from the Microsoft SQL downloads
Web site.
b. Install Microsoft SQL Server 2005 according to the instructions provided by
Microsoft. Also adhere to the following requirements:
v Because the JDBC driver requires Microsoft SQL Server authentication for
the login, select Mixed mode and specify a password when you are
prompted for the authentication type.
v Instead of using the default instance of Microsoft SQL Server 2005, create
a customized instance by using the following server name in the install
wizard or response file: dbhostname\instancename.
Notes:
v Configure the server to allow remote network connections. See How to
configure SQL Server 2005 to allow remote connections on the Microsoft
Help and Support Web site for instructions.
v Trusted connections are not supported at this time.
v If you want to run the database on a remote server, you must download and
install the following items:
Microsoft SQL Server Native Client
77
Microsoft SQL Server 2005 Command Line Query Utility

The JDBC drivers needed for the database
2. Create a unique user ID and password on the database server for the runtime
database connection. Ensure that this user ID is not the instance owner of the
database server. The IBM Systems Director cfgdbcmd database configuration
tool will grant the user the correct privileges to manage the database.
directory.
IBM Systems Director does not save the Microsoft SQL Server 2005
administrator account user ID and password.
3. Enter your chosen database name into the cfgdbcmd.rsp file so that the
cfgdbcmd tool will create the database within the Microsoft SQL Server for you.
4. Install the Microsoft SQL Server JDBC driver on the management server where
IBM Systems Director Server will be installed.
a. Download the Microsoft SQL Server 2005 JDBC Driver 1.2 JDBC driver from
Microsoft SQL Server 2005 JDBC Driver 1.2 on the Microsoft Web site.
b. Install the downloaded Microsoft SQL Server JDBC driver according to the
instructions provided by Microsoft.
c. Enter the directory where the driver is located into the correct field of the
cfgdbcmd.rsp file.
IBM Systems Director Server and configure it to use the database or set options
in a database-configuration response file for use with the cfgdbcmd command:
Description
78
attribute
DbmsApplication
value you select.

__ v
__ v
__ v
__ v



Description
attribute

DbmsServerName
Apache Derby)
Custom value:
Database name
DbmsDatabaseName
Custom value:
hatterastc.

Database only)
SID
Custom value:
__ v Local
__ v Remote
DbmsDatabaseAppHome
Server system
Custom value:
of 50000.

DbmsUserId
Custom value:
79

Description
attribute


Custom value:
installation:
Related tasks
page 101
wizard on page 92
Related reference
Microsoft SQL Server 2005 JDBC Driver 1.2 JDBC driver
How to configure SQL Server 2005 to allow remote connections
Preparing the Microsoft SQL Server 2005 Express Edition database:
Before installing IBM Systems Director Server, prepare the Microsoft SQL Server
2005 Express Edition database for use with IBM Systems Director. The database can
be used with IBM Systems Director Server only on management servers running
Windows.
Check if Microsoft SQL Server 2005 Express Edition is already installed. If it is,
ensure that the authentication mode is set to mixed mode. For information about
changing these parameters for an existing installation, see the following Microsoft
SQL Server 2005 Express Edition Books Online article: msdn2.microsoft.com/enus/library/ms143705.aspx.
Complete the following tasks to prepare the Microsoft SQL Server 2005 Express
Edition database before installing IBM Systems Director Server:
1. Install and start Microsoft SQL Server 2005 Express Edition. See the Supported
database applications topic for supported versions and installation options.
a. Download Microsoft SQL Server 2005 Express Edition from the Microsoft
SQL Server downloads Web site.
80
b. Install Microsoft SQL Server 2005 Express Edition according to the

instructions provided by Microsoft. When prompted for the authentication
type, select Mixed mode and specify a password.
Notes:
v Configure the server to allow remote network connections. See How to
configure SQL Server 2005 to allow remote connections on the Microsoft
Help and Support Web site for instructions.
v Trusted connections are not supported at this time.
v If you want to run the database on a remote server, you must download and
install the following items:
Microsoft SQL Server Native Client
Microsoft SQL Server 2005 Command Line Query Utility
The JDBC drivers needed for the database
2. Configure TCP/IP connectivity for use with IBM Systems Director Server. By
default, Microsoft SQL Server 2005 Express Edition does not have TCP/IP
connectivity enabled after installation. In addition, the TCP port must be set for
use with IBM Systems Director Server. Complete the following steps:
a. Click Start All Programs Microsoft SQL Server 2005 Configuration
Tools Microsoft SQL Server Configuration Manager.
b. In the left pane of the Microsoft SQL Server Configuration Manager
window, expand Microsoft SQL Server 2005 Network Configuration and
then click Protocols for SQLEXPRESS.
c. In the right pane of the Microsoft 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 is set to the default
value of 1433.
g. In the TCP/IP Properties window, click OK, and then click OK to
acknowledge the warning message.
h. In the left pane of the Microsoft SQL Serve Configuration Manager window,
click Microsoft SQL Server 2005 Services.
i. In the right pane of the Microsoft SQL Serve Configuration Manager
window, right-click Microsoft SQL Server (SQLEXPRESS) and click Restart.
Note: If you have multiple instances of Microsoft SQL Server installed on the
management server, configure the instance you will be using with IBM Systems
Director Server, and substitute the correct instance name for SQLEXPRESS in
the preceding steps.
3. Install the Microsoft SQL Server JDBC driver on the management server where
IBM Systems Director Server will be installed.
a. Download the Microsoft SQL Server 2005 JDBC Driver 1.2 JDBC driver from
Microsoft SQL Server 2005 JDBC Driver 1.2 on the Microsoft Web site.
b. Install the downloaded Microsoft SQL Server JDBC driver according to the
instructions provided by Microsoft.
c. Enter the directory where the driver is located into the correct field of the
cfgdbcmd.rsp file.
81
Description
attribute
DbmsApplication
value you select.

__ v
__ v
__ v
__ v



DbmsServerName
Apache Derby)
Custom value:
Database name
DbmsDatabaseName
Custom value:
hatterastc.

Database only)
SID
Custom value:
__ v Local
__ v Remote
DbmsDatabaseAppHome
Server system
Custom value:
82

attribute
Description
of 50000.
DbmsUserId


Custom value:
Custom value:
installation:
83
Related tasks
page 101
wizard on page 92
Related reference
Authentication Mode (SQL Server Express)
Preparing the Oracle Database

If you choose to use Oracle Database as the database for IBM Systems Director,
there are some tasks that you need to complete to prepare your system before you
install IBM Systems Director Server.
Complete the following tasks before installing IBM Systems Director Server:
1. Install the database server or client. See the Supported database applications
topic for supported versions and installation options.
Important: If you want to run the database on a remote server, you must
install the full administration client with IBM Systems Director Server. The
administration client automatically installs the needed IBM DB2 Universal
Database tools and JDBC drivers.
2. Start the database server or client.
3. Create your Oracle Database. Ensure that the character set of your new
database is UTF-8.
4. Use the IBM Systems Director cfgdbcmd database configuration tool to create a
unique user ID and password on your system for the runtime database
connection and grant that user the correct privileges to manage the database.
The Oracle Database administrator account user 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.
directory.
IBM Systems Director does not save the Oracle Database administrator account
user ID and password.
5. Ensure that the following environment variables are correctly set and also set to
be persistent after logoff or reboot:
84
ORACLE_HOME
Ensure that this variable is set to the installation directory of the
Oracle Database server or client.
PATH Add the bin directory under the ORACLE installation root directory to
the system variable PATH.
LD_LIBRARY_PATH (Linux) or LIBPATH (AIX)
For 32-bit machine types, set this variable to <oracle_install_root>/
lib or <oracle_install_root>/lib32.
Restriction: If your machine type is 64-bit, the Oracle Database
installation will link <oracle_install_root>/lib to a 64-bit driver,
which is incorrect. You must use <oracle_install_root>/lib32 for
64-bit machine types.
6. Configure and start the Oracle Database TCP/IP listener.
Description
attribute
DbmsApplication
value you select.

__ v
__ v
__ v
__ v


DbmsServerName
Apache Derby)
Custom value:
Database name
DbmsDatabaseName
Custom value:
hatterastc.

Database only)
SID
Custom value:
__ v Local
__ v Remote
85

attribute
Description
DbmsDatabaseAppHome
Server system
Custom value:
of 50000.

DbmsUserId

Custom value:
Custom value:
installation:
86
Related tasks
page 101
wizard on page 92
Related reference
Preparing firewalls and proxies for IBM Systems Director

If you have firewalls in your network, or if the management server must use a
proxy server to access the internet, you must configure the firewalls and proxy
server to enable installation and operation of IBM Systems Director.
IBM Systems 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 Systems Director require access to the internet.
To enable this access, you must configure firewalls and proxies in your network to
allow access by IBM Systems Director components.
Complete the following steps to configure firewalls and proxies in your network:
1. Identify the ports that you will use in your systems-management environment
and ensure that those ports are open before you start installation. For example,
you must ensure that the listener ports for IBM Systems Director Server and
Common Agent are open. See All available ports for a complete list of the
ports that IBM Systems Director components can use.
2. If a proxy server is required to access the Internet from the management server,
complete the following steps to 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 Systems Director requires Internet
access for some functions, including update manager.
If you will be using the Service and Support Manager extension for IBM Systems
Director, you will need to allow this extension to send information to the IBM
Support Center at 207.25.252.200 using HTTPS (port 443). Additional information is
available from the Service and Support Manager Web Site at www.ibm.com/
support/electronic/. In particular, you might want to review the Service and
Support Manager Security Reference Doc.
87
Related reference
Electronic Service Agent Web site
Installing firmware and device drivers

Before installing IBM Systems Director on Red Hat Enterprise Linux, SUSE Linux,
VMware ESX Server, Windows Server 2003, or Windows Server 2008, you need to
install the latest firmware and device drivers for IBM service processors and
ServeRAID controllers. To accomplish this, you can either use the IBM
UpdateXpress System Pack Installer (UXSPi) or you can install the files manually.
Decide the level of agent management that is required for your system. See
Choosing the management level for managed systems for information.
RSA II notes for installing on Linux:
v The RSA II daemon requires the libusb and libusb-devel packages, which are
typically installed by default. If your distribution or installation does not include
or install these packages, you must install them prior to installing the RSA II
daemon.
v If you are running Linux, the RSA II daemon requires that you configure RSA II
for Linux OS prior to installation. Change this setting through the RSA II Web
management interface or through a setting found in the system BIOS setup
utility.
To install the latest firmware and device drivers for IBM service processors and
ServeRAID controllers and ServeRAID Manager plug-ins, it is recommended to use
the IBM UpdateXpress System Pack Installer (UXSPi). The UXSPi will
automatically install the latest BIOS, IPMI baseboard management controller
(BMC), Remote Supervisor Adapter II (RSA II), ServeRAID, and other firmware as
required for your server. It will also automatically install the required IPMI device
drivers for the BMC and the RSA Server Software for the RSA II. See the IBM
Systems support Web site at http://www.ibm.com/systems/support/ and select
the appropriate UpdateXpress System Pack Library to download the recommended
firmware and drivers for your system.
If you choose to not use the UpdateXpress System Pack Installer, perform the
following steps to download and install the latest firmware and device driver files
for your Red Hat Enterprise Linux, SUSE Linux, or VMware ESX Server system.
Notes:
v These steps apply to only Red Hat Enterprise Linux, SUSE Linux, or VMware
ESX Server systems, though the steps that are required for Windows systems are
similar.
v See Preparing to manage service processors with IBM Director for more
information about service processors.
v If your system contains an Integrated systems management processor (ISMP),
you need to instead install LM78 and SMBus drivers. See Installing the IBM
LM78 or SMBus device driver for information.
1. Install the latest firmware for BMC service processors.
a. Download into a temporary directory the
ibm_fw_bmc_XXXXXXX_linux_i386.sh BMC firmware file from
http://www.ibm.com/systems/support/. This file is available for all
88
supported Red Hat Enterprise Linux, SUSE Linux, and VMware ESX
operating systems, so download the version that applies to your system.
b. Navigate to the temporary directory into which you downloaded the file.
c. Use a console prompt from the temporary directory to run the following
command:
./ibm_fw_bmc_XXXXXXX_linux_i386.sh -s -a -s
2. Install the latest daemon for the RSA II service processors.

ibm_svc_rsa2_XXXXXXX_linux_32-64.tgz RSA II daemon file from
commands:
tar xzf ibm_svc_rsa2_XXXXXXX_linux_32-64.tgz
export PATH=$PATH:/usr/local/bin;./install.sh --update
3. Install the latest firmware for the RSA II service processors.

ibm_fw_rsa2_XXXXXXX_linux_i386.sh RSA II firmware file from
commands:
tar xzf ibm_fw_rsa2_XXXXXXX_linux_i386.sh
export PATH=$PATH:/usr/local/bin;./install.sh --update -force-if-overridden
4. Install the latest firmware and device drivers for ServeRAID controllers.
a. Download into a temporary directory the following individual files that are
required for your servers from http://www.ibm.com/systems/support/.
Note: The firmware packages apply to all Linux and VMware ESX
distributions, but you must download the appropriate device driver for
your particular distribution.
Table 23. Required ServeRAID controller firmware and device driver files
Files
(See
Key 1)
RHEL
AS 4
U6
32-bit
RHEL
AS 4
U6
64-bit
RHEL
AS 5
U1
32-bit
RHEL
AS 5
U1
64-bit
SLES
SLES 9 SLES 9 10
32-bit
64-bit
32-bit
7
8
9
VMware
ESX
4
5
SLES
10
64-bit
89
Table 23. Required ServeRAID controller firmware and device driver files (continued)
Files
(See
Key 1)
RHEL
AS 4
U6
32-bit
RHEL
AS 4
U6
64-bit
RHEL
AS 5
U1
32-bit
RHEL
AS 5
U1
64-bit
SLES
SLES 9 SLES 9 10
32-bit
64-bit
32-bit
SLES
10
64-bit
VMware
ESX
10
Key 1:
v 1: ServeRAID MR 10 Device driver (systems with ServeRAID
hardware): ibm_dd_sraidmr_XXXXXXXX_rhel4_32-64.tgz
hardware): ibm_dd_sraidmr_XXXXXXXX_rhel5_32-64.tgz
hardware): ibm_dd_sraidmr_XXXXXXXX_sles9_32-64.tgz
hardware): ibm_dd_sraidmr_XXXXXXXX_sles10_32-64.tgz
10
10
10
10
v 5: ServeRAID MR 10 Firmware (systems with ServeRAID 10 hardware):

ibm_fw_sraidmr_XXXXXXXXXXX_linux_32-64.bin
v 6: ServeRAID 8 Device driver (systems with ServeRAID 8 hardware):
ibm_dd_aacraid_XXXXXXXXXXX_rhel4_32-64.tgz
ibm_dd_aacraid_XXXXXXXXXXX_rhel5_32-64.tgz
ibm_dd_aacraid_XXXXXXXXXXX_sles9_32-64.tgz
ibm_dd_aacraid_XXXXXXXXXXX_sles10_32-64.tgz
v 10: ServeRAID 8 Firmware (systems with ServeRAID 8 hardware):
ibm_fw_aacraid_8k-8kl-X.X.X-XXXXX_linux_32-64.bin
b. Navigate to the temporary directory into which you downloaded the files.
c. Use a console prompt from the temporary directory to run the installation
command for each of the downloaded files. Use the following installation
command examples as guides:
Example: ServeRAID8 on RHEL5
tar xzf ibm_dd_aacraid_1.1.5.2434_sles10_32-64.tgz
export PATH=/usr/local/bin:$PATH ; ./install.sh --update
./ibm_XX_aacraid_XXXXXXXXXXX_XXXX_XXX.bin -s
Example: ServeRAID10 on RHEL5

tar xzf ibm_dd_sraidmr_XXXXXXXX_rhel5_32-64.tgz
export PATH=/usr/local/bin:$PATH ; ./install.sh --update
./ibm_fw_sraidmr_XXXXXXXXXXX_linux_32-64.bin -s
Preparing to install IBM Systems Director Server on Windows

Before installing IBM Systems Director on a management server running Windows,
make sure that your server meets all the applicable requirements.
Note: Because installing IBM Systems Director Server on Windows also installs
Common Agent and IBM Systems Director Web interface, the preparation steps for
IBM Systems Director Server also include preparation steps for Common Agent
and IBM Systems Director Web interface.
90
Review the following information and complete the necessary steps to prepare
your system for installation:
v Ensure that your system meets the hardware and software requirements
(including those for databases, security, and networking) for installation, as
described in Hardware and software requirements.
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 Systems Director for information about these
drivers and mapping layers.
v If you want to use IBM Systems Director Server on System x for heterogeneous
server management, you can install Common Agent or Platform Agent on the
platforms you want to manage. You can obtain Common Agent and Platform
Agent for the supported operating systems from the IBM Systems Director Web
site at www.ibm.com/systems/management/director/.
Related tasks
wizard on page 92
Windows on page 98
Related reference
Hardware and software requirements on page 17
Installing IBM Systems Director on the management server

After preparing your system, use the IBM Systems Director Server installation
procedure for the operating system on which you plan install IBM Systems
Director Server.
Note: You are advised to not install IBM Systems Director on the same system as
IBM Storage Configuration Manager (SCM).
Related tasks
Preparing the management server on page 71
page 101
Related reference
Installing IBM Systems Director Server on Windows

After preparing your system, you can install IBM Systems Director Server on a
Windows system by downloading the installation files from the IBM Systems
Director support Web site or by using the CD. You can then perform a standard
installation by using the wizard in a standard interactive mode, or you can
perform an unattended installation (either with or without status feedback) by
using a response file that automatically provides answers to the questions that the
wizard poses.
Important:
v Installation of IBM Systems Director installs IBM Systems Director Server,
Common Agent (when applicable), and Platform Agent all together. Therefore, it
91
is not necessary to separately install Common Agent or Platform Agent on the

management server after installing IBM Systems Director Server. In most cases,
any IBM Systems Director tasks requiring Common Agent or Platform Agent
will be performed for systems with IBM Systems Director Server installed.
v Systems running AIX require Common Agent to be installed. These systems
cannot be managed with Platform Agent.
v Ensure that the system clocks on the systems that contain IBM Systems Director
Server and Common Agent remain synchronized.
Installing IBM Systems Director Server on Windows using the

InstallShield wizard
Use the IBM Systems Director Server installation wizard to install IBM Systems
Director Server on a system that is running Windows.
Important:
v If you are planning to install and use a database for IBM Systems Director other
than the default database, make sure that you have installed and configured the
database application that you will use with IBM Systems Director before
installing IBM Systems Director Server. For more information, see Preparing the
database application on page 71.
v Before installing IBM Systems Director Server on a system that has IBM Storage
Configuration Manager installed, you must first uninstall IBM Storage
Configuration Manager. After installing IBM Systems Director Server, you can
re-install IBM Storage Configuration Manager.
When you install IBM Systems Director Server, the InstallShield wizard
automatically installs the necessary components and databases that you choose.
Depending on the version of IBM Systems Director Server you are installing, you
can install IBM Systems Director Server on Windows from either installation media
or from a downloaded installation package.
Table 24. Installation options for IBM Systems Director Server on Windows
Installation method
Title or file name
DVD media
IBM Systems Director on x86, V6.1.0 DVD

Note: To obtain an image of the IBM
Systems Director on x86, V6.1.0 DVD,
download the SysDir6_1_DVD_x86.iso file.
Attention: If you use DVD media to install
IBM Systems Director Server, ensure that
you allot an additional 1.2 GB of available
space on the system to contain the agent
packages that are copied from the DVD at
the end of the server installation. The
packages are copied to
\installation_directory\packaging\agent on
the server, where installation_directory is the
92
Table 24. Installation options for IBM Systems Director Server on Windows (continued)
Installation method
Title or file name
Downloaded installation package
SysDir6_1_Server_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 Systems Director Server installation. If
the upgrade is necessary, the system prompts you to restart following the
installation of IBM Systems 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 Systems
Director Server installation is completed successfully.
At the end of the installation process, you can configure a database to use with
IBM Systems Director and change security settings.
Note: If you plan to use the default Apache Derby database, you can choose either
the basic installation path, which configures Apache Derby by default, or the
custom installation path.
To install IBM Systems Director Server, log in as the root user and complete the
following steps:
1. Start the installation from the installation source:
Downloaded installation files: To start the installation from a Web download,
a. Download the installation package from the IBM Systems Director
Downloads Web Site at www.ibm.com/systems/management/director/
downloads/.
Note: When you download the IBM Systems Director Server installation
package from the Web, the agent packages are not included. You need to
download and install them separately as described in Installing agents.
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:
\installation_directory\IBMSystemsDirectorServerSetup.exe
where installation_directory is the path to the extracted installation

files.
e. Go to step 2 on page 94.
DVD media: To start the installation from the IBM Systems Director on x86
DVD, complete the following steps:
downloads/.
b. Create an installation DVD from the downloaded iso image file.
c. Insert the DVD into the DVD-ROM drive.
d. If the installation program starts automatically and the IBM Systems
Director Setup window opens, go to the next step.
Otherwise, click Start Run and then go to the next step.
e. In the Open field, type the following command and press Enter:
93
e:\installation_directory\IBMSystemsDirectorServerSetup.exe
where e is the DVD-ROM drive letter on your system and

installation_directory is the directory where the installation files are
located. The InstallShield wizard starts and the Welcome page is displayed.
Accessibility note: Screen readers might not process the IBM Systems
Director Setup window correctly. To start the installation wizard for IBM
Systems Director Server using the keyboard, complete the following steps:
1) Close the IBM Systems Director Setup window.
2.
3.
4.
5.
6.
2) Open Windows Explorer.

3) Browse to the \server\windows\i386\ directory on the IBM Systems
Director on x86 DVD.
4) Run the IBMSystemsDirectorServerSetup.exe program. The
InstallShield wizard starts, and the IBM Systems Director Setup
window opens.
5) Continue to step 2.
Click Next. The License Agreement page is displayed
Select I accept the terms in the license agreement and click Next. The Feature
and installation directory selection page is displayed.
To select an alternative location for the creation of the installation, click
Change and select another directory.
Click Next. The Setup Type page is displayed.
Choose one of the following setup types:
Basic
With basic installation, you are presented with the minimum number
of setup screens and IBM Systems Director default settings are
installed.
Custom
With custom installation, you are presented with all the setup screens
and can change the IBM Systems Director default values, such as
which database application to use, as necessary.
Note: If you are connecting to the default Apache Derby database, you can
choose either the basic installation path, which connects to Apache Derby by
default, or the custom installation path.
7. Click Next. The User credentials page is displayed.
8. Enter your computer information and user credentials in the fields provided.
9. Click Next. (Custom setup only.) The Agent Manager Configuration page is
displayed.
10. Select to create a new agent manager or reuse an existing agent manager.
11. Click Next. (Custom setup only.) Depending on whether you are creating a
new agent manager or reusing an existing one, enter in the information for the
new or existing agent manager.
Note: IPv6-only agent managers are not supported.
12. Click Next. (Custom setup only.) The Database configuration page is
displayed.
13. Select the database application to use with IBM Systems Director. You have
the following options:
94
Apache Derby
Creates and configures an embedded Apache Derby database. The
Apache Derby application is included in the IBM Systems Director
installation and is, unless you specify otherwise during installation,
configured by default.
IBM DB2 Universal Database
Configures IBM Systems Director to use an IBM DB2 Universal
Database. IBM DB2 Universal Database must be installed and
configured on a system in your network.
Microsoft SQL Server 2005 or Microsoft SQL Server 2005 Express Edition
Configures IBM Systems Director to use a Microsoft SQL Server
database. Microsoft SQL Server must be installed and configured on a
system in your network.
Oracle Database
Configures IBM Systems Director to use an Oracle Database. Oracle
Database must be installed and configured on a system in your
network.
Note: Only the database type, not the version, matters at this stage.
14. Click Next to configure IBM Systems Director for use with your database
application. Refer to the following table for application-specific configuration
instructions.
Table 25. Database configuration
If the database
application is
Apache Derby
Complete the applicable steps

In some cases, no window will be displayed and installation will
continue. If a IBM Systems Director Apache Derby Configuration
window is displayed, the values cannot be changed.
Click Next and continue with the next step of these instructions.
95
Table 25. Database configuration (continued)

If the database
application is
IBM DB2 Universal

Database
The IBM Systems Director DB2 Universal Database Configuration

window is displayed.
Complete the following fields, which might be spread out among
more than one screen:
1. In the User name field, type a valid IBM DB2 Universal Database
user ID.
2. In the Password field, type the password for the IBM DB2
Universal Database user ID.
3. Choose Local or Remote based on how you want to administer
the database.
4. In the Administrator name field, type a valid user ID for the IBM
DB2 Universal Database administrator account.
5. In the Password field, type the password for the IBM DB2
Universal Database administrator account.
6. In the Server hostname field, type the hostname of the server on
which IBM DB2 Universal Database is installed.
7. In the Port number field, type the number of the port that is
used by the IBM DB2 Universal Database TCP/IP listener.
8. In the Database name field, type the name of the database. If it
does not exist, it will be created.
9. In the Enter full path for your database apps field, type the path
of the directory in which your IBM DB2 Universal Database
applications are located.
Microsoft SQL Server

2005 or Microsoft
SQL Server 2005
Express Edition (does
not apply to AIX)
The IBM Systems Director Microsoft SQL Server Database

Configuration window opens.
1. In the User name field, type a valid Microsoft SQL Server user
ID.
2. In the Password field, type the password for the Microsoft SQL
Server user ID.
the database.
4. In the Administrator name field, type a valid user ID for the
Microsoft SQL Server administrator account.
5. In the Password field, type the password for the Microsoft SQL
Server administrator account.
which Microsoft SQL Server is installed.
7. In the Port number field, type the number of the port that is
used by the Microsoft SQL Server TCP/IP listener.
8. In the Database name field, type the name of the database. If it
does not exist, it will be created.
of the directory in which your Microsoft SQL Server applications
are located.
96
Table 25. Database configuration (continued)

If the database
application is
Oracle Database

The IBM Systems Director Oracle Database Configuration window
opens.
1. In the User name field, type a valid Oracle Database user ID. If
it does not exist, it is created. By default, this user ID is assigned
to the IBM Systems Director table space.
2. In the Password field, type the password for the Oracle
Database user ID.
the database.
4. In the Administrator name field, type a valid user ID for the
Oracle Database administrator account.
5. In the Password field, type the password for the Oracle
Database administrator account.
which Oracle Database is installed.
7. In the Oracle Net Service Port field, type the number of the port
that is used by the Oracle Database Net Service.
8. In the System Identifier (SID) field, type the Oracle Database
system identifier (SID).
of the directory in which your Oracle Database applications are
located.
15. Click Next. (Custom setup only.) The WebServer information page is
displayed.
16. Enter in the HTTP port and secure port that you want enabled for the
WebServer.
17. Click Next. (Custom setup only.) The Server startup option page is displayed.
18. Choose the startup options for IBM Systems Director:
v Select Automatically start server service after installation if you want IBM
Systems Director Server to start automatically after installation instead of
starting it manually.
v Select Install Non-Stop Service if you want to also install Non-Stop Service,
which is a watchdog service for the server that automatically attempts to
restart the server if it stops.
19. Click Next. The Ready to Install the Program window is displayed.
20. Click Install. Various windows that display the status of the installation are
displayed. When the installation is complete, the Installation complete
window is displayed.
21. Click Finish.
22. If you used the DVD for installation, remove the DVD from the drive.
23. If you are prompted to restart your system, click Yes.
97
Related tasks
Preparing the IBM DB2 Universal Database on page 72
Preparing the Microsoft SQL Server 2005 database on page 77
Preparing the Microsoft SQL Server 2005 Express Edition database on page 80
Preparing the Oracle Database on page 84
Preparing to install IBM Systems Director Server on Windows on page 90
Preparing the database application on page 71
Related reference
Performing an unattended installation of IBM Systems Director

Server on Windows
After preparing your System x server for the installation of IBM Systems Director,
you can perform an unattended installation of IBM Systems Director Server by
using a response file. This method creates a standard installation file that can be
used on many systems.
Important:
v If you are planning to install and use a database for IBM Systems Director other
than the default database, make sure that you have installed and configured the
database application that you will use with IBM Systems Director before
installing IBM Systems Director Server. For more information, see Preparing the
database application on page 71.
v Before installing IBM Systems Director Server on a system that has IBM Storage
Configuration Manager installed, you must first uninstall IBM Storage
Configuration Manager. After installing IBM Systems Director Server, you can
re-install IBM Storage Configuration Manager.
When you perform an unattended installation of IBM Systems Director Server, the
response file provides answers to the questions that are posed by the InstallShield
wizard.
Important: You can set up the IBM Systems Director Server response file to
contain entries for a user ID and password to use with the IBM Systems Director
service account. The user ID and password must correspond to a Windows account
98
with administrator privileges. If you choose to include this information in the

response file, ensure that you delete the file after the installation is complete to
avoid security issues.
Depending on the version of IBM Systems Director Server you are installing, you
can install IBM Systems Director Server on Windows from either installation media
or from a downloaded installation package.
Table 26. Installation options for IBM Systems Director Server on Windows
Installation method
Title or file name
DVD media
IBM Systems Director on x86, V6.1.0 DVD

Note: To obtain an image of the IBM
Systems Director on x86, V6.1.0 DVD,
download the SysDir6_1_DVD_x86.iso file.
Attention: If you use DVD media to install
IBM Systems Director Server, ensure that
you allot an additional 1.2 GB of available
space on the system to contain the agent
packages that are copied from the DVD at
the end of the server installation. The
packages are copied to
\installation_directory\packaging\agent on
the server, where installation_directory is the
Downloaded installation package
SysDir6_1_Server_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 Systems Director Server installation. If
the upgrade is necessary, the system prompts you to restart following the
installation of IBM Systems 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 Systems
Director Server installation is completed successfully.
At the end of the installation process, you can configure a database to use with
IBM Systems Director and change security settings.
Note: If you plan to use the default Apache Derby database, you can choose either
the basic installation path, which configures Apache Derby by default, or the
custom installation path.
To use a response file to install IBM Systems Director Server on Windows, log in as
the root user and complete the following steps:
1. Start the installation from the installation source:
Downloaded installation files: To start the installation from a Web download,
downloads/.
b. Use the unzip command to extract the contents of the installation package
to a temporary directory.
99
c. Copy the dirserver.rsp response file to a new location. This file is in the
\directory\FILES directory, where directory is the local directory into which
you extracted the files.
DVD media: To start the installation from the IBM Systems Director on x86,
V6.1.0 DVD, complete the following steps:
a. Insert the DVD into the DVD-ROM drive.
b. If the installation program starts automatically and the IBM Systems
Director Setup window opens, close it.
c. Copy the dirserver.rsp response file to a local directory. This file is in the
\server\windows\i386 directory on the IBM Systems Director on x86, V6.1.0
DVD.
2. Open the copy of the dirserver.rsp file, which follows the Windows INI file
format, in an ASCII text editor.
3. Modify and save the response file with a new file name. This file is fully
commented.
4. Open a command prompt and change to the directory that contains the IBM
Systems Director Server installation file (IBMSystemsDirectorServerSetup.exe).
This file is in the \server\windows\i386 directory on the IBM Systems Director
on x86, V6.1.0 DVD.
5. From the command prompt, type the following command and press Enter:
IBMSystemsDirectorServerSetup.exe installationtype rsp="responsefile" option
where the variables are defined as follows:

installationtype
One of the following commands:
v unattended shows the progress of the installation but does not
require any user input.
v silent suppresses all output to the screen during installation.
responsefile
The path and name of the response file that you created previously.
option One of the following optional parameters:
Table 27. Optional installation parameters
Optional parameter
What it does
waitforme
Ensures that installation processing will not end until this

installation 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.
6. If you set the RebootIfRequired parameter to Y in the response file, reboot the
system if prompted to do so.
7. If you used the DVD for installation, remove the DVD from the drive.
8. Run the following command in \director\bin:
cfgserver.bat -all
9. Provide the information requested by the command, clicking Enter after every
answer.
100
10. Run the cfgdbcmd tool in \director\bin. See cfgdbcmd for information. The
cfgdbcmd tool will use the response file that you previously filled in to
properly connect your IBM Systems Director Server to the chosen database.
Related tasks
Preparing to install IBM Systems Director Server on Windows on page 90
Configuring the database application after IBM Systems Director installation
Related reference
Configuring the database application after IBM Systems Director

installation
After IBM Systems Director installation, use the cfgdbcmd.rsp file to configure IBM
Systems Director to use a nondefault database application. This task actually
switches the configured database from one to another.
Ensure that IBM Systems Director Server is stopped before starting this task. See
smstop command for information.
Complete the following steps to use the cfgdbcmd.rsp file to configure your
database:
1. Open the cfgdbcmd.rsp file with any text editor. The cfgdbcmd.rsp file resides
in the install_root\proddata directory, where install_root is the root directory of
your IBM Systems Director installation.
2. In the cfgdbcmd.rsp file, ensure that the configuration information for your
chosen database is not commented out (remove the ; at the beginning of all
fields for that database) and make sure that the other possible database
configuration options are commented out so that they remain ignored. By
default, all database configuration information is commented out using the ;
character before the line and is therefore ignored by the IBM Systems Director
Server.
3. Use information from your local database administrator to fill in all of the
fields needed for your chosen database, including for Apache Derby if
applicable. See Preparing the database application for information about
what you need to gather from each applicable database server.
Attention: Ensure that you do not use any quotes in the response file as they
will cause errors during database configuration.
4. Save and close the cfgdbcmd.rsp file.
5. Run the script that encrypts passwords for your database configuration. The
script that you use varies depending on which operating system you are using.
See Encrypting passwords for database configuration for details.
6. After the encryption script is complete, run the cfgdbcmd tool. Depending on
your operating system, the filename of the tool is either cfgdbcmd.cmd or
cfgdbcmd.sh. See cfgdbcmd command for information. The cfgdbcmd tool
will use the response file that you previously filled in to properly connect your
IBM Systems Director Server to the chosen database.
7. After the database configuration tool has completed, you must run the smreset
command located in the install_root\bin folder. See smreset command for
information.
101
8. Start IBM Systems Director Server. See smstart command for information.
After the configuration is complete, IBM Systems Director Server is properly
connected to your chosen database.
Related tasks
Preparing the IBM DB2 Universal Database on page 72
Preparing Microsoft SQL Server on page 77
Preparing the Microsoft SQL Server 2005 database on page 77
Preparing the Microsoft SQL Server 2005 Express Edition database on page 80
Preparing the Oracle Database on page 84
Windows on page 98
Installing IBM Systems Director on the management server on page 91
Related reference
IBM Systems Director Best Practices Redwiki
Configuring IBM Systems Director Server after installation

Before you start using IBM Systems Director, review these recommendations for
configuring systems and setting up your environment.
Configure IBM Systems Director Server after a successful installation, so that you
can get the most benefit from the product, and be able to work efficiently. Do not
confuse this task with Configuring Systems, which is a separate topic for
configuring those resources that are controlled by IBM Systems Director.
The Welcome page of IBM Systems Director provides a quick overview, as well as
links to all necessary configuration tasks.
To configure IBM Systems Director, perform these steps:
1. Click System Discovery on the Start tab to discovery recently-installed agents.
2. Click Collect and View Inventory on the Start tab to collect inventory data on
all the recently-installed agents.
3. In the Next Steps section, click Register IBM Systems Director and complete
the product registration.
4. Run these options in the Next Steps list.
v Create event thresholds and automation plans
v Check for updates on discovered systems.
102
v Set up additional user security

v Start configuring your systems
Configuring IBM Systems Director plug-ins and platforms

These plug-ins and platforms are used to manage the various features of IBM
Systems Director. Check this list, and run the configuration tasks for those plug-ins
and platforms that you intend to use. Some of these do not require configuration,
but it is optional. Others do not have configuration tasks.
If you do not intend to use a particular plug-in or platform, there is no need to
configure it.
1. Configure console settings, including encryption, console navigation, and event
log settings.
2. Configure users and roles. Click Security Users and Security Roles.
3. Examine this list and configure all IBM Systems Director plug-ins that you
intend to use.
IBM Systems Director Server
Although the installation process has performed some of the
configuration tasks for the IBM Systems Director Server, review the
status page and make any necessary changes.
Update Manager
There are no mandatory configuration tasks, but you are advised to
click on the Update Manager link to go to the summary page, and run
the Getting Started and Settings tasks.
Virtualization Manager
Create a master image for Xen virtual servers.
Remote Access
Configure Virtual Network Computing (VNC) and Remote Desktop, if
you intend to use these Remote control features.
Storage Management
Configure SMI-S providers and external storage applications.
These plug-ins have no configuration tasks:
v
v
v
v
v
Discovery Manager
Status Manager
Automation Manager
BladeCenter and System x Management
v Power Systems Management

v System z Management
Configuring the command line interface

Before running the smcli commands or displaying help for them, ensure that
required software is installed and the locale is correctly installed and configured on
the system.
You can run smcli commands locally on the management server or remotely by
accessing the management server using a remote-access utility, such as secure shell
103
(SSH) or Telnet. Perform these steps on the management server and on all other
systems that you might use to access the management server to run commands.
Note: (AIX only) Japanese, Korean, and Chinese fonts display correctly only when
displaying man pages for smcli commands locally on the management server.
1. (Windows only) Management servers running Windows XP, Windows 2000, or
Windows 2003 require msvcr80.dll to run smcli. You can obtain the dynamic
link library (DLL) by installing vcredist_x86.exe. For information about
downloading and installing this file, see https://www.microsoft.com/
downloads.
2. (AIX) If you choose to use a single byte or double-byte language with UTF-8
encoding, the CLI displays output, messages, helps, and man pages correctly
only when run locally on an AIX management server or remotely on an AIX
display exported from the AIX management server. When run remotely on a
non-AIX display exported from the AIX management server, the characters will
appear garbled.
3. Ensure that the desired locale is supported by IBM Systems Director and is
installed correctly on the client system, from where smcli is run.
Tips:
v To verify languages supported by smcli, see .
v (AIX and Linux only) To check the current locale, use the locale -a command.
v (AIX only) To install another locale, use the smit command.
v (Linux for x86 only) To install another locale, use the yast command. Use
UTF-8 locales (for example, ja_JP.UTF-8).
v If your system does not support double-byte character sets, you will see
garbage characters or small block-like characters when you display
operating-system specific man pages.
4. (AIX and Linux only) Set the environment variables LC_ALL and LANG to the
desired locale in which you want to run the commands using the export
command (for example, export LC_ALL=en and export LANG=en).
Tip: To verify that the system locale has changed, run some AIX or Linux
specific commands and ensure that the operating-system-specific messages are
displayed in the language you set.
5. (AIX and Linux only) The smcli man page are available only in English and
Japanese. To view the view man pages in English, set the MANPATH
environment variable to /opt/ibm/director/man. To view the man pages in
Japanese on an AIX system, set the MANPATH environment variable to
opt/ibm/director/man/ja.
Tips:
v To verify that the MANPATH environment variable was changed correctly,
display man pages for some operating-system specific commands to ensure
the Japanese locale is set correctly.
v (SUSE Linux only) Man pages are available only in English. They are not
available in Japanese.
v v On AIX, man pages in Japanese display correctly only if you run the
commands locally on the management server with LANG=JA_JP (which is a
UTF-8 locale).
104
v v For SUSE Linux Enterprise Server 9.x,, the man command only understands
EUC_JP encoding. You must convert the man page encoding from UTF-8 to
EUC_JP to view the man pages, for example:
mkdir -p /tmp/man/man1
iconv -futf8 -teucjp /opt/ibm/director/man/ja/man1/command_name.1
/tmp/man/man1/command_name.1
man -M
>
/tmp/man/ command_name
Reviewing Microsoft Internet Explorer security options

Review these instructions if you are using Microsoft Internet Explorer Web
browsers that have Enhanced Security Configuration enabled, and are running on
Windows Server 2003 or Windows Server 2008.
When using a Web browser with Enhanced Security Configuration enabled, some
properties of the IBM Systems Director Web interface might not display as
expected.
Internet Explorer Enhanced Security Configuration establishes a configuration for
your server and for Internet Explorer that decreases the exposure of your server to
potential attacks that can occur through Web content and application scripts. As a
result, some Web sites might not display or perform as expected.
Using a server for Internet browsing is not a good security practice because
Internet browsing increases the exposure of your server to potential security
attacks. It is a best practice recommendation that you run your Web browser on a
system that is not a server. However, if you must use a server running Windows
Server, you must turn off Internet Explorer Enhanced Security Configuration.
Complete the following applicable steps to disable Internet Explorer Enhanced
Security:
1. On Windows Server 2003 systems:
a. Click Start Control Panel.
b. In the Control Panel window, click Add or Remove Programs.
c. Click Add/Remove Windows Components.
d. Clear the Select Internet Explorer Enhanced Security Configuration check
box.
e. Click Next; then, click Finish.
2. On Windows Server 2008 systems:
a. Close any instances of the Internet Explorer Web browser.
b. Start Server Manager.
c. In the Details pane, locate the Security Information area that is displayed
under the Server Summary area.
d. In the Security Information area, click Configure IE ESC.
e. In the Internet Explorer Enhanced Security Configuration window, click the
applicable option:
v If your user account is a member of the Administrators group, click Off
under Administrators.
v If your user account is a member of a standard users group, click Off
under Users.
f. Click OK.
105
Logging on to IBM Systems Director Server for the first time

After installing IBM Systems Director Server, log on using a Web browser, discover
managed systems, and request access to them.
You must already have installed and started IBM Systems Director Server before
beginning this task.
1. Log on to IBM Systems Director using a Web browser.
a. Point your browser to the following URL:
http://System_Name:Port_Number/ibm/console
where System_Name is the name of the system on which IBM Systems

Director Server is installed and Port_Number is the first (lower) of two
consecutive port numbers that you specified for the Web server to use. The
default ports for the Web server are 8421 and 8422. If you use port 8422,
make sure that you specify https to indicate a secure port.
b. Type the user ID and password that correspond to an authorized IBM
Systems Director administrator user ID and password.
c. Click Log in.
Note: A security alert window might be displayed before logging in. This is
due to incorrect configuration of the Secure Sockets Layer (SSL) certificate.
For information see Configuring Secure Sockets Layer (SSL) between IBM
Systems Director and the Web browser client.
2. Discover your managed systems. The first time you log on to IBM Systems
Director Server, a Discover button is displayed. Click it to start discovering
your managed systems.
3. Request access to your managed systems.
Secured systems are displayed in IBM Systems Director Web interface with a
padlock icon beside them in the Secured column of the systems details. After a
system is accessed, the padlock disappears and additional tasks and status
information are available.
The Access attribute for each resource shows the current access status. You
cannot request access to resources that have an access status of Offline, for
which you need to instead use verify access, or OK, because you already have
access to those resources and no further action is required.
To request access to secured managed systems, complete the following steps.
Note: You can select more than one system at a time as long as each requires
the same user ID and password.
a. In IBM Systems Director Web interface, click Navigate Resources.
b. Navigate to the system that you want to access.
c. Right-click the system for which you want to request access and select
Security Request Access.
d. On the Request Access page, type the user ID and password of a user with
administrator privileges on the managed system.
e. Click Request Access.
You can now begin managing the systems you have discovered, or install agents
on managed systems to enable additional management capabilities.
106
Related concepts
System discovery on page 120
Related tasks
Chapter 3, Installing IBM Systems Director on the management server, on page
71
107
108
Chapter 4. Preparing agentless managed systems

Prepare the agentless managed systems in your environment before you discover
or manage them with IBM Systems Director.
Related reference
Related information
AIX Pegasus CIM server and providers
Preparing to manage a IBM BladeCenter

IBM Systems Director can be deployed to manage the blade servers in a IBM
BladeCenter chassis.
Related reference
Preparing to manage a IBM BladeCenter chassis using IBM

Systems Director Server on a non-blade server
You can install IBM Systems Director Server on a non-blade server. With this
management server you can manage one or more IBM BladeCenter units and the
blade servers installed in them. You must configure the network so that this
installation is possible.
Complete the following steps to prepare to manage an IBM IBM BladeCenter
chassis using IBM Systems Director Server installed on a non-blade server:
1. Consider using a Dynamic Host Configuration Protocol (DHCP) server to
assign an address to the external port of the management module. When a IBM
BladeCenter management module is first started, it searches for a DHCP server.
If a DHCP server is not found, the IBM BladeCenter management module
assigns IP address 192.168.70.125 to the external management port. Because this
static IP address is the same for all management modules, IP address conflicts
can occur if you do not use a DHCP server and introduce multiple IBM
BladeCenter chassis onto a network simultaneously. When you configure the
IBM BladeCenter chassis, you assign static IP addresses to the switch module
and the external and internal ports of the management module.
2. Set up a separate management network to configure and manage your IBM
BladeCenter chassis and blade servers. By separating the LAN segment used
for production from the LAN segment to which the IBM BladeCenter
management module is connected, you can ensure that only authorized system
administrators can connect to the IBM BladeCenter chassis and switch modules.
Figure 2 on page 110 shows such a network configuration.
3. If you intend to use Remote Deployment Manager (RDM), install RDM on the
management server.
4. If you plan to use a database application other than Apache Derby, consider
installing the database server on the management LAN.
5. Make sure that you have installed the latest version of the management module
firmware. To download the firmware, go to the IBM Servers Web site at
www.ibm.com/servers/.
109
Figure 2. Example of IBM BladeCenter deployment network when IBM Systems 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
IBM BladeCenter management module at any given time:
v Cluster Systems Management (CSM)
v IBM Systems Director Server
v IBM Management Processor Command-Line Interface (MPCLI)
Preparing to manage a IBM BladeCenter chassis using IBM

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

Changing the boot options on that blade server
v Create a network setup that enables the IBM BladeCenter Management Module
to communicate with the management server. Otherwise IBM Systems Director
will be unable to discover the IBM BladeCenter chassis that contains the
management server.
By default, the blade servers installed in a IBM BladeCenter chassis cannot
communicate automatically with the IBM BladeCenter Management Module. This
architecture is designed to prevent the blade servers from modifying the IBM
BladeCenter chassis settings. If you install IBM Systems Director Server on a blade
server and want to use the instance of IBM Systems Director to manage the IBM
BladeCenter unit in which the management server is installed, you must enable
communication between the management server and the management module.
1. Consider using a Dynamic Host Configuration Protocol (DHCP) server to
assign an address to the external port of the management module. When a IBM
BladeCenter management module is first started, it searches for a DHCP server.
If a DHCP server is not found, the IBM BladeCenter management module
assigns IP address 192.168.70.125 to the external management port. Because this
static IP address is the same for all management modules, IP address conflicts
can occur if you do not use a DHCP server and introduce multiple IBM
BladeCenter chassis onto a network simultaneously. When you configure the
IBM BladeCenter chassis, you assign static IP addresses to the switch module
and the external and internal ports of the management module.
2. Set up a separate management network to configure and manage your IBM
BladeCenter chassis and blade servers. By separating the LAN segment used
for production from the LAN segment to which the IBM BladeCenter
management module is connected, you can ensure that only authorized system
administrators can connect to the IBM BladeCenter chassis and switch modules.
Figure 2 on page 110 shows such a network configuration.
3. To use an installation of IBM Systems Director Server on a blade to manage the
IBM BladeCenter unit in which the management server is installed, enable
communication between the Campus LAN and the Management LAN. Figure 3
on page 112 shows such a network configuration.
4. If you intend to use Remote Deployment Manager (RDM), install RDM on the
management server.
5. If you plan to use a database application other than Apache Derby, consider
installing the database server on the management LAN.
6. Make sure that you have installed the latest version of the management module
firmware. To download the firmware, go to the IBM Servers Web site at
www.ibm.com/servers/.
111
Figure 3. Example of IBM BladeCenter deployment network when IBM Systems Director
Server is installed on a blade server
With this configuration, IBM Systems 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
IBM BladeCenter management module at any given time:
v Cluster Systems Management (CSM)
v IBM Systems Director Server
v IBM Management Processor Command-Line Interface (MPCLI)
Related reference
IBM Servers
Preparing Windows managed systems

You might need to configure certain Windows systems before you can discover
them with IBM Systems Director Server. Ensure that each Windows system that
you want to manage has been appropriately configured.
Preparing Windows Server 2003 managed systems

You might need to configure certain Windows Server 2003 systems before you can
discover them with IBM Systems Director Server. Ensure that each Windows Server
2003 system that you want to manage has been appropriately configured.
Typically, managed systems are first discovered using the discovery task in IBM
Systems Director Web interface. Then, Platform Agent or Common Agent is
installed on the managed systems directly from IBM Systems Director Web
interface. The configuration of some Windows Server 2003 managed systems,
however, can prevent discovery by IBM Systems Director Server.
Complete the following steps on each Windows Server 2003 system to enable
discovery by IBM Systems Director Server:
112
Verify that remote registry administration is enabled. Remote registry

administration must be enabled in order for Agentless-managed system discovery
to run commands and run scripts on the managed system. The default setting for
remote registry administration on Windows systems is enabled. Complete the
following steps to verify or change the remote registry administration setting:
1. Click Start Control Panel System and Maintenance Administrative
Tools.
2. In the Administrative Tools window, double-click Services.
3. In the list of services in the Services window, right-click the Remote Registry
service and select Properties from the menu.
4. On the General page, set the Startup type to Automatic.
5. If the Service status is not Started, click Start to start the service.
6. Click OK to apply the new settings and close the window.
Preparing Windows Server 2008 managed systems

You might need to configure certain Windows Server 2008 systems before you can
discover them with IBM Systems Director Server. Ensure that each Windows Server
2008 system that you want to manage has been appropriately configured.
interface. The configuration of some Windows Server 2008 managed systems,
however, can prevent discovery by IBM Systems Director Server.
Complete the following steps on each Windows Server 2008 system to enable
discovery by IBM Systems Director Server:
Verify that remote registry administration is enabled. Remote registry
administration must be enabled in order for Agentless-managed system discovery
to run commands and run scripts on the managed system. The default setting for
remote registry administration on Windows systems is enabled. Complete the
following steps to verify or change the remote registry administration setting:
1. Click Start Control Panel System and Maintenance Administrative
Tools.
2. In the Administrative Tools window, double-click Services.
3. In the list of services in the Services window, right-click the Remote Registry
service and select Properties from the menu.
4. On the General page, set the Startup type to Automatic.
5. If the Service status is not Started, click Start to start the service.
6. Click OK to apply the new settings and close the window.
Preparing Windows Vista managed systems

Some Windows Vista systems might need to be configured before you can be
discover or manage them with IBM Systems Director Server. Make sure each
Windows Vista system that you want to manage has been appropriately
configured.
Typically, managed systems are first discovered using the Discovery task in IBM
113
interface. The configuration of some Windows Vista managed systems, however,

can prevent discovery by IBM Systems Director Server.
Complete the following steps on each Windows Vista system to enable
management by IBM Systems Director Server:
Related reference
Preparing to manage an agentless managed system running

Windows Vista
Before IBM Systems Director can manage a system running Windows Vista, you
must configure a password-protected administrator account on the managed
system and enable sharing and the remote registry service.
To prepare the Windows Vista system for management by IBM Systems Director,
1. Configure the user account that IBM Systems Director will use.
Type of account
Configuration steps
Built-in
Administrator
account on the
managed system
Enable the Administrator account and set a password for the

account.
1. Click Start Control Panel System and Maintenance
Administrative Tools.
2. In the Administrative Tools window, double-click Local
Security Policy.
3. Click Security Settings Local Policies Security Options.
4. Double-click Accounts: Administrator account status.
5. Click Enabled, and then click OK.
6. Log in to Windows Vista using the Administrator account, and
then set a password for the account.
Local user account

other than
Administrator
Disable User Account Control, create the user account, and set a
password for the account.
Security Policy.
4. Double-click User Account Control: Run all administrators in
Admin Approval Mode.
5. Click Disabled, and then click OK.
6. Create the user account you will use for IBM Systems Director,
if it does not already exist.
7. Set the user account type to administrator.
8. Set a password for the account.
114
Type of account
Configuration steps
Domain account
Disable User Account Control.

Security Policy.
4. Double-click User Account Control: Run all administrators in
Admin Approval Mode.
5. Click Disabled, and then click OK.
To enable these changes, you will need to shut down and restart the managed
system.
2. Verify that remote registry administration is enabled. Remote registry
administration must be enabled in order for Agentless-managed system
discovery to run commands and run scripts on the managed system. The
default setting for remote registry administration on Windows systems is
enabled. Complete the following steps to verify or change the remote registry
administration setting:
a. Click Start Control Panel System and Maintenance Administrative
Tools.
b. In the Administrative Tools window, double-click Services.
c. In the list of services in the Services window, right-click the Remote
Registry service and select Properties from the menu.
d. On the General page, set the Startup type to Automatic.
e. If the Service status is not Started, click Start to start the service.
f. Click OK to apply the new settings and close the window.
3. Configure Sharing and Discovery preferences. Complete the following steps:
a. Click Start Control Panel Network and Internet Network and
Sharing Center.
b. Under Sharing and Discovery, turn on each of the following items:
v Network discovery
v File sharing
v Password protected sharing
4. Click Start Control Panel Network and Internet Windows Firewall.
5. Click Allow a program through a Windows Firewall. The Windows Firewall
Settings window opens and displays the Exceptions page.
6. In the list of exceptions, select the File and Printer Sharing check box.
Note: Enabling file and printer sharing allows IBM Systems 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.
Preparing to manage a Platform-Agent managed system running

Windows Vista
Before IBM Systems Director can manage Platform Agent on a system running
Windows Vista, you must configure the firewall to allow communication on the
SLP, CIM, and CIM SSL ports.
115
To prepare the Windows Vista system for Platform-Agent managed system

management by IBM Systems Director, complete the following steps:
1. Configure the system for Agentless-managed system management as described
in Preparing to manage a Agentless-managed system running Windows
Vista. Configuration for Agentless-managed system 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. Complete the following steps
for each of the ports listed in Table 28.
a. Click Add port.
b. Specify the Name, Port number, and Protocol in the Add port window.
c. Click OK.
Table 28. Ports required for Platform-Agent managed system 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
6. Click OK.
Preparing to manage a Common-Agent managed system running

Windows Vista
Before IBM Systems Director can manage Platform Agent on a system running
Windows Vista, you must configure the firewall to allow communication with
Common Agent on ports 14247 and 14248.
To prepare the Windows Vista system for Common-Agent managed system
management by IBM Systems Director, complete the following steps:
1. Configure the system for Agentless-managed system management as described
in Preparing to manage a Agentless-managed system running Windows
Vista. Configuration for Agentless-managed system management is required in
order to access the managed system.
2.
3.
4.
5.
116
Click Start Control Panel Network and Internet Windows Firewall.

Click Allow a program through Windows Firewall.
Select the Remote administration check box.
Specify ports to allow through Windows Firewall. Complete the following steps
for each of the ports listed in Table 29 on page 117.
a. Click Add port.
b. Specify the Name, Port number, and Protocol in the Add port window.
c. Click OK.
Table 29. Ports required for Common-Agent managed system 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.
Preparing Windows XP managed systems

You might need to configure certain Windows XP systems before you can discover
them with IBM Systems Director Server. Ensure that each Windows XP system that
you want to manage has been appropriately configured.
interface. The configuration of some Windows XP managed systems, however, can
prevent discovery by IBM Systems Director Server.
Complete the following steps on each Windows XP system to enable discovery by
IBM Systems Director Server:
1. Disable Simple File Sharing. Windows XP targets must have Simple File
Sharing disabled for Agentless-managed system discovery to work. Complete
the following steps to disable simple file sharing on the Windows XP system to
be managed:
a. Select Start Control Panel Folder Options.
b. In the Folder Options window, click the View tab.
c. In the View panel, scroll to the bottom of the Advanced settings list; then,
clear the Use simple file sharing (Recommended) check box.
d. Click OK.
2. Configure Windows Firewall (Internet Connection Firewall) to allow access by
IBM Systems Director Server. Windows XP (before Service Pack 2) includes a
built-in firewall called Internet Connection Firewall (ICF), which is disabled by
default. Windows XP Service Pack 2 includes Windows Firewall, which is
enabled by default. Either firewall will block attempted accesses by
Agentless-managed system discovery unless the firewall is disabled or an
exception is defined for the management server on which IBM Systems Director
Server is installed.
Complete the following steps to enable IBM Systems Director Server to access
the managed system:
a. Select Start Control Panel Network Connections connection. The
connection is the network connection that will be used for discovery.
Typically, this is Local Area Connection.
b. In the General tab of the Connection Status window, click Properties.
c. In the Connection Properties window, click the Advanced tab.
d. In the Advanced panel, click the firewall Settings button.
e. If the firewall is turned off, no further configuration is required. Continue to
step 3 on page 118.
117
f. If the firewall is enabled, click the Exceptions tab.

g. In the Exceptions panel, select the File and Printer Sharing check box.
h. Click OK.
Note: The network administrator can define a group policy for this
configuration.
3. Verify that remote registry administration is enabled. Remote registry
administration must be enabled in order for Agentless-managed system
discovery to run commands and run scripts on the managed system. The
default setting for remote registry administration on Windows systems is
enabled. Complete the following steps to verify or change the remote registry
administration setting:
a. Click Start Control Panel System and Maintenance Administrative
Tools.
b. In the Administrative Tools window, double-click Services.
c. In the list of services in the Services window, right-click the Remote
Registry service and select Properties from the menu.
d. On the General page, set the Startup type to Automatic.
e. If the Service status is not Started, click Start to start the service.
f. Click OK to apply the new settings and close the window.
4. Verify the hidden administrative disk shares such as C$, D$, and so on. The
default hidden administrative disk shares are required for correct operation of
Agentless-managed system discovery.
At a command prompt, type net share and press Enter to list the shares
defined on the managed system.
Related reference
118
Chapter 5. Discovering systems and collecting inventory data

To manage a resource within an environment or view inventory data about it, that
resource must first be discovered and, after access is granted, an inventory must be
collected. The resource is recognized and added to the comprehensive list of native
resources and native attributes for the system. Discovery and inventory collection
are the two primary tasks that are used to connect to supported network resources
and collect information about them.
Discovery protocols
During system discovery, IBM Systems Director Server attempts to communicate
with target resources by using a predetermined list of protocols. When using
advanced system discovery, IBM Systems Director Server attempts to communicate
with target resources by using only the protocols that you have configured.
IBM Systems Director Server can be used to discover network-level resources that
use a communication protocol that is supported by the IBM Systems Director
discovery process. The protocol that is used to discover a specific type of resource
depends on the communication protocol used by that resource.
A discovery protocol is any network communication protocol that is used by IBM
Systems Director during the discovery process to discover a system. By default,
IBM Systems Director supports the following discovery protocols:
Agent manager discovery
Agent manager discovery specifically targets the discovery of Tivoli
common agents. In the Tivoli paradigm, Service Location Protocol (SLP) is
not supported and management servers contact an agent manager that
knows about the agents in their environment. You can select the agent
managers that you want to use in discovery.
Common Agent Services (CAS) discovery
CAS discovery utilizes Service Location Protocol (SLP) discovery, with
which clients can locate servers and other services on the network.
Common Information Model (CIM) discovery
CIM discovery utilizes the Service Location Protocol (SLP) for discovery.
With CIM discovery, clients can locate servers and other services on the
network.
Interprocess communication (IPC) discovery
IPC is the process by which programs send messages to each other.
Sockets, semaphores, signals, and internal message queues are common
methods of interprocess communication. IPC is also a mechanism of an
operating system that enables processes to communicate with each other
within the same computer or over a network. IPC leverages services that
IBM Systems Director provides that components use to communicate with
each other. By using these services, a server task can communicate with an
agent task running on a target.
Secure shell (ssh) discovery
Secure shell is a Unix-based command interface and protocol for securely
accessing a remote computer. With ssh discovery, you can specify either a
single IP address or a range of IP addresses upon which to run discovery
119
Service Location Protocol (SLP) discovery

SLP is a protocol for service discovery. With SLP discovery, clients can
locate servers and other services on the network.
Simple Network Management Protocol (SNMP) discovery
SNMP is a network management standard widely used in TCP/IP
networks. SNMP performs management services by using a distributed
architecture of management systems and agents. SNMP provides a method
of managing network hosts such as workstation or server computers,
routers, bridges, and hubs from a centrally-located computer running
network-management software.
Storage Management Initiative Specification (SMI-S) discovery
With SMI-S discovery, clients can locate servers and other services on the
network. It is a design specification developed by the Storage Networking
Industry Association (SNIA) that specifies a secure and reliable interface
with which storage management systems (SMSs) can identify, classify,
monitor, and control physical and logical resources in a storage area
network (SAN). The interface integrates the various devices to be managed
in a storage area network (SAN) and the tools used to manage them.
Windows Distributed component object model (DCOM) discovery
Use Windows DCOM (an extension of the Microsoft Component Object
Model (COM) to support objects distributed across a network)
configuration to specify either a single IP address or a range of IP
addresses upon which to run discovery.
Note: Additional discovery protocols are routinely created by vendors. For more
information about communicating with a device that uses a protocol that is not
listed here, contact the manufacturer or software provider for that device.
Discovering systems with system discovery

Use the System Discovery task to identify systems at a specific network address or
range of addresses.
System discovery
To discover systems at a specific network address or range of addresses, use
system discovery. This method is useful in networks in which both broadcast and
multicast messages are filtered.
System discovery discovers Agentless-managed systems, Platform-Agent managed
systems, and Common-Agent managed systems by sending a unicast request to
one or more addresses. IBM Systems Director Server sends one request to each
system at a time.
System discovery provides the following functions:
v Discovery based on a single IP address
v Discovery based on a range of IP addresses
v Discovery based on a host name
After systems are discovered, they are displayed in a table for viewing.
During system discovery, IBM Systems Director Server attempts to communicate
with target resources by using a predetermined list of protocols.
120
Performing a system discovery

Use the System Discovery task to identify systems at a specific network address or
range of addresses.
To perform a system discovery, complete the following steps:
1. Open the System Discovery page using either of these two methods:
v On the Welcome page, click System discovery under Optional tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click System Discovery.
The System Discovery page is displayed.
2. Select one of the following discovery methods:
Table 30. System discovery methods
To do this task:
Complete these steps:
Add a single IP address
1. Click Single system (IP address).

2. In the IP address field, type the IP
address of the system that you want to
discover.
3. If you want to discover only a specific
resource type, select it from the Select
resource type list.
Add a range of IP addresses
1. Click Multiple systems (Range of IP

addresses).
2. For the IP address range that contains
the systems that you want to discover,
type the low-end IP address value in the
Starting IP address field and the
high-end IP address value in the Ending
IP address field.
resource type list.
Add a host name of a system
1. Click Single system (Hostname).

2. In the Hostname field, type the host
name of the system that you want to
discover.
resource type list.
3. Click Discover. The Processing discovery protocols message is displayed and

the progress of the discovery process is displayed as a spinning graphic.
Note: The time it takes for discovery to finish processing varies depending on
such factors as network performance and the number of systems that are
discovered.
4. Optional: If you want to stop the discovery process, click Stop during
discovery.
As systems are discovered, they are displayed in the Discovered Systems table.
Note: After a resource is discovered, the virtual systems that are associated with
that resource are also discovered.
121
Viewing system discovery results

Use the System Discovery task to view a table that contains the results of all
system discovery tasks as you run them.
To view the system discovery results as you discover systems, complete the
following steps:
1. Open the System Discovery page using either of these two methods:
v On the Welcome page, click System discovery under Optional tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click System Discovery.
The System Discovery page is displayed.
2. Discover systems using one of the three available methods.
3. View systems as they are discovered in the Discovered Systems table.
Note: IBM Systems Director Server displays the discovery results for all
discovery requests that occur on the server during your discovery request,
including the results from other IBM Systems Director users who are accessing
the same management server. As a result, the systems that are displayed might
include additional systems that are not located at the target IP addresses or
host names that you enter.
When discovery is completed, all the discovered systems are displayed in the
Discovered Systems table. The table will maintain the information until you exit
the Systems Discovery task, at which point it is cleared.
Accessing a secured system with request access

Use the Request Access page to request access to a secured system if the
management server to which you are connected has not yet authenticated to the
system. You must be able to access the system before you can perform tasks or
remotely access the system.
Ensure that you have the correct authorization to access the secured system.
Note: If any CAS or IPC access points exist on the resource, you must use this
process to configure credentials for all of the agent access points, which are all
access points that have an access type other than console. When the agent access
points include CAS or IPC access points, using the request access task to
successfully request access to the resource is all that is required to obtain access to
all the agent access points. Credentials and mappings are created for the agent
access points, but you cannot view or manage them. If no CAS or IPC access
points exist on the resource, you have the option of using the configure access task
to request access to the secured resource.
Secured systems are displayed in IBM Systems Director Web interface with a
padlock icon beside them in the Secured column of the systems details. After a
system is accessed, the padlock disappears and additional tasks and status
information are available.
The Access attribute for each resource shows the current access status. You cannot
request access to resources that have an access status of Offline, for which you need
to instead use verify access, or OK, because you already have access to those
resources and no further action is required.
122
To request access to secured managed systems, complete the following steps.

Note: You can select more than one system at a time as long as each requires the
same user ID and password.
1. In IBM Systems Director Web interface, click Navigate Resources.
2. Navigate to the system that you want to access.
3. Right-click the system for which you want to request access and select Security
Request Access.
Note: Alternatively, you can select Security Configure Access and then click
Request Access on the Configure Access page.
4. On the Request Access page, type the user ID and password of a user with
administrator privileges on the managed system.
5. Click Request Access. Credentials are created and authenticated to the
managed system in an attempt to access it.
If the access request is successful, the access status for the managed system will
change to OK.
123
124
Chapter 6. Installing agents

Prepare your managed systems and environment for agent and subagent
installation and then install Common Agent, Platform Agent, virtualization
manager subagent, or IBM Systems Director z/VM manageability access point
agent.
Preparing a Platform-Agent managed system

Before installing Platform Agent on a managed system make sure that the
requirements that are applicable to your system have been met.
Complete the following steps on each system to be managed with Platform Agent:
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. On all managed systems that use the ssh protocol to communicate with IBM
Systems Director Server, ensure that the PasswordAuthentication value in
/etc/ssh/sshd_config is set to yes. So, the corresponding line in the
sshd_config file will appear as follows:
PasswordAuthentication yes
Note: You must restart the ssh server for any changes made to sshd_config to
take effect.
Related reference
RedHat chkconfig bug fix
Preparing to install Platform Agent on Windows

Before installing Platform Agent on a managed system running Windows, make
sure that your system meets all the applicable requirements.
v Ensure that your system meets the hardware and software requirements for
installation, as described in Hardware and software requirements.
v The IBM Systems Director on x86 DVD no longer includes OpenSSH for
Windows. If a Platform-Agent managed system or Common-Agent managed
125
system does not have a Secure Shell (SSH) package installed, IBM Systems
Director Server cannot communicate securely with the managed system. To
secure communication, install OpenSSH on the managed system. Download
OpenSSH for Windows from www.sourceforge.net/projects/sshwindows/ and
update the managed system with SSH.
Related tasks
Installing agents using the Agent Installation Wizard on page 127
Related reference
IBM Systems Director Web page
OpenSSH for Windows
Preparing a Common-Agent managed system

Before installing Common Agent on a managed system, ensure that the
requirements applicable to your system have been met.
Complete the following steps on each system to be managed with Common Agent:
On all managed systems that use the ssh protocol to communicate with IBM
Systems Director Server, ensure that the PasswordAuthentication value in
/etc/ssh/sshd_config is set to yes. So, the corresponding line in the sshd_config
file will appear as follows:
PasswordAuthentication yes
Note: You must restart the ssh server for any changes made to sshd_config to take
effect.
Obtaining licenses for Common Agent

IBM Systems Director includes licenses for up to 20 installations of Common Agent
on non-IBM x86 systems. To install Common Agent on additional non-IBM x86
systems, you must obtain a license from IBM.
1. Determine which non-IBM x86 systems require Common Agent licenses.
2. Obtain licenses for each installation of Common Agent on non-IBM x86 systems
from the Ready to Buy Web Page at www.ibm.com/systems/management/
director/buy.html.
Related concepts
License information on page 47
Preparing to install Common Agent on Windows

Before installing Common Agent on a managed system running Windows, make
sure that your system meets all the applicable requirements.
v Ensure that your system meets the hardware and software requirements for
installation, as described in Hardware and software requirements.
126
v The IBM Systems Director on x86 DVD no longer includes OpenSSH for
Windows. If a Platform-Agent managed system or Common-Agent managed
system does not have a Secure Shell (SSH) package installed, IBM Systems
Director Server cannot communicate securely with the managed system. To
secure communication, install OpenSSH on the managed system. Download
OpenSSH for Windows from www.sourceforge.net/projects/sshwindows/ and
update the managed system with SSH.
Related tasks
Installing agents using the Agent Installation Wizard
Related reference
OpenSSH for Windows
Installing agents using the Agent Installation Wizard

You can use the Agent Installation Wizard to install agent packages on managed
systems.
IBM Systems Director Server requires a number of agent packages that can be
deployed to managed systems using the Agent Installation Wizard.
Note: If you install IBM Systems Director Server from the DVD media, it is
installed with the agent packages. If you install IBM Systems Director Server from
the Web download file, however, you need to download the agent tcdriver
packages separately from the IBM Systems Director 6.1 Agents for Remote
Deployment with Agent Installation wizard section of the Web download site.
Copy the packages to a location of your choice on the IBM Systems Director Server
system and then import them with the Agent Installation Wizard.
These packages are located in the dynamic group Agent Package Groups and
can be accessed by clicking Release Management Agents in the navigation area.
You use the Agent Installation Wizard to select one of these agent packages to
install and one or more systems on which to install the agent package. Then, the
wizard creates an agent installation job that can run immediately or at a scheduled
time.
Note: You can also download the manual agent installation packages from the
IBM Systems Director 6.1 Agents for Manual Deployment section of the Web
download site, then copy the self-extracting script and the response file from the
package to a local directory and deploy using the Agent Installation Wizard. The
local directory into which you copy the script and response file depends on which
operating system and version of IBM Systems Director you are running:
127
v On AIX or Linux: <install_root>/packaging/agent/common/<platform>/6.1 or

<install_root>/packaging/agent/platform/<platform>/5.20.3.
v On Windows: <install_root>\packaging\agent\common\<platform>\6.1 or
<install_root>\packaging\agent\platform\<platform>\5.20.3.
1. Start the Agent Installation Wizard. You can start the wizard in multiple ways:
v From the Welcome page, click Start. Then, click Install agents on systems.
v Right-click an agent package or a managed system and select Release
Management Install Agent.
2. If the Agent Installation Wizard Welcome page appears, click Next.
3. In the Agent Installation Wizard Agents page, complete the following steps:
a. Select the agent package that you want to install in the Available list.
b. Click Add. The selected agent package is displayed in the Selected list.
Notes:
v Depending on how you started the Agent Installation Wizard, one or
more agent packages might already be displayed in the Selected list.
c.
4. In
a.
b.
v The Agent Installation Wizard can install only one agent package at a
time. If more than one agent package is displayed in the Selected list,
you will not be able to advance to the Systems page.
Click Next.
the Agent Installation Wizard Systems page, complete the following steps:
Select the managed systems on which you want to install the agent package
in the Available list.
Click Add. The selected systems are displayed in the Selected list.
Notes:
v Depending on how you started the Agent Installation Wizard, one or
more systems might already be displayed in the Selected list.
v Depending on the agent package being installed, some selected systems
might not be valid targets for installation. The wizard checks the selected
systems for some or all of the following criteria to ensure that the
systems are valid targets for installing the selected agent package before
allowing you to continue:
operating system family
operating system version
operating system distribution

operating system name
server architecture
c. Click Next.
5. In the Agent Installation Wizard Summary page, review the Selected Agents
and Selected Systems lists to ensure that they are correct.
v If the selections are not correct, click Back and make the necessary changes.
v If the selections are correct, click Finish.
After you click Finish, the Run - Install Agent window opens.
6. In the Run - Install Agent window, click the Schedule tab. On this page, you
can choose to run the job immediately or schedule the job to run at a later time.
a. A job name is required and the Name field provides a unique default name.
To change the default name, type a job name in the field.
128
b. To run the job immediately, click Run Now and go to step 7. Otherwise,
click Schedule.
c. In the Schedule list, select how frequently you want the job to run. The
default setting is Once. Other values are Hourly, Daily, Weekly, Monthly,
Yearly, or Custom. Also, you can specify whether to run the job on the
weekend.
d. Select the date and time to run the job for the first time.
e. Select the time range for the job to repeat.
7. Click the Notification tab. On this page you can customize a notification that is
sent by e-mail.
a. Select from the available criteria to customize when the e-mail notification is
sent. You can specify that the e-mail be sent when one of the following
criteria is met:
v When the job begins
v When the job competes successfully
v When the job fails. You can further customize this criterion by setting
either the percentage of target systems on which the job had errors or the
number of systems on which the job had errors. Therefore, if the job runs
on five systems, the job has errors on two systems, and you set the
criterion threshold to 50%, the notification is not sent.
v When the job receives any error.
b. Type your e-mail address, e-mail server, and e-mail server port.
Tip: You can provide only one e-mail address.
8. Click the Options tab. On this page you can select additional options for the
job behavior.
a. Select whether you want the job to run according to your management
servers time or the target systems time.
Tip: Make sure that you know the time and time zone to which the
respective systems clocks are set.
b. Select whether you want the job to fail if a system is offline or if you want
the job to run when the system is online again.
9. Click OK to save the job.
Click Cancel to exit from the Run window without saving the job.
If the job is created successfully, a message is displayed on the page from
which you started the Scheduler. If the job creation fails, a message is displayed
in the Run window so that you can correct the job.
The job created by the Agent Installation Wizard will transfer the agent
self-extracting script and the agent response file into the /tmp directory on the
target system. After the files are copied, the installation file sets are extracted
into the /tmp/extract_XXXXXX directory and installed. The files are then
removed after a successful installation. You need to ensure that there is
sufficient space on the target system to copy the self-extracting script and
extract the file sets. Refer to the space requirements as specified in Hardware
requirements for systems running Common Agent or Platform Agent.
Notes for AIX:
v Refer to Installing Common Agent on AIX for more detail on the
self-extracting script and the response file options.
v For AIX server and agents, it is less space consuming to remotely install
agents using NIM as explained in the IBM Systems Director Best Practices
129
Redwiki at http://www-01.ibm.com/redbooks/community/display/
director/IBM+Systems+Director+6.1+for+Power+Systems. Installing with
NIM does not allow the use of a response file.
You can view the status of the agent installation job by clicking Task Management
Active and Scheduled Jobs.
Related tasks
Preparing to install Common Agent on Windows on page 126
Preparing to install Platform Agent on Windows on page 125
Related reference
SourceForge.net Open IPMI project
IBM Director Fails to Start
Service and productivity tools
SourceForge.net
OpenSSH for Windows
Installing the LSI MegaRAID provider for Windows or Linux

If you have a managed system that has an LSI 1078 MegaRAID controller installed,
you need to install the LSI MegaRAID provider on the managed system after
installing Common Agent, Platform Agent, IBM Director Agent version 5.20, or
IBM Director Core Services version 5.20.
For 5.20.2 and later, IBM Systems Director supports the following managed system
and configurations that need to have the LSI MegaRAID provider installed:
Server
RAID Controller
IBM System x3950 M2,

machine type 7141
ServeRAID-MR10k SAS/SATA Controller,

part number 43W4280
IBM System x3950 M2,

machine type 7141
ServeRAID-MR10M SAS/SATA Controller,

part number 43W4339
IBM System x3350,

machine type 4192
ServeRAID-MR10i SAS/SATA Controller,

part number 43W4296
The LSI MegaRAID provider can be installed on managed systems running

supported versions of the following operating systems:
v 5.20.3 and later: VMware ESX Server, version 3.0
v 5.20.3 and later: Red Hat Enterprise Linux, version 3.0
v SUSE Linux Enterprise Server 9 for x86
v SUSE Linux Enterprise Server 10 for x86
v Microsoft Windows
See the Supported operating systems topic for specific versions of these
operating systems that are supported.
130
Notes:
v For 5.20.2, the LSI MegaRAID provider is not supported for VMware operating
systems. To use the LSI MegaRAID provider, upgrade the managed system to
5.20.3 or later.
v The LSI MegaRAID provider is not supported for systems with Xen enabled.
Common Agent, Platform Agent, IBM Director Agent version 5.20, or IBM Director
Core Services version 5.20 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 Systems Director Downloads Web Site:
Agent version
Operating system
Package file name
5.20.3 or higher
Red Hat Enterprise Linux, version

3.0
lsi_mr_hhr-00.02.G5.041.rhel3.i386.rpm
5.20.3 or higher

4.0
5.20.3 or higher

5.0
5.20.3 or higher
SUSE Linux Enterprise Server 9 for lsi_mr_hhr-00.02.G5.04x86

1.sles9.i586.rpm
5.20.3 or higher
SUSE Linux Enterprise Server 10

for x86
lsi_mr_hhr-00.02.G5.041.sles10.i386.rpm
5.20.3 or higher
Microsoft Windows
LSI_MR_HHR-WS3200.02.G5.04.exe
5.20.2

4.0
lsi_mr_hhr-90.00.05.381.rhel4.i386.rpm
5.20.2

5.0
lsi_mr_hhr-90.00.05.381.rhel5.i386.rpm
5.20.2
SUSE Linux Enterprise Server 9 for lsi_mr_hhr-90.00.05.38x86

1.sles9.i586.rpm
5.20.2
SUSE Linux Enterprise Server 10

for x86
lsi_mr_hhr-90.00.05.381.sles10.i386.rpm
5.20.2
Microsoft Windows
lsi_mr_hhr-WS32-90.00.05.38.exe
To install the LSI MegaRAID provider, complete the following steps.

1. Download the installation package from the IBM Systems Director Downloads
Web Site at www.ibm.com/systems/management/director/downloads/.
2. Change to the directory to which you saved the installation package on the
Platform-Agent 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, agent version 5.20.3 or later: Complete the following steps:
a. Run the downloaded package.
b. Click Next.
c. Click Install.
131
5. Windows only, agent version 5.20.2: 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
c. Shut down and restart Windows.
Related reference
Installing the IBM ServeRAID Manager plug-in files

Various ServeRAID Manager plug-in files are required on Red Hat Enterprise
Linux, SUSE Linux, VMware ESX Server, Windows Server 2003, and Windows
Server 2008 systems. To acquire the plug-in files, you can either use the IBM
UpdateXpress System Pack Installer (UXSPi) or you can install the files manually.
Ensure that Platform Agent is installed on your system.
Ensure that the IBM Systems Director services are stopped by issuing the following
commands:
cd /etc/rc.d/init.d
./twgagent stop
./tier1slpinst stop
./snmpd stop
./cimserver stop
./cimlistener stop
./ibmsa stop
To install the latest firmware and device drivers for IBM service processors and
ServeRAID controllers and ServeRAID Manager plug-ins, it is recommended to use
the IBM UpdateXpress System Pack Installer (UXSPi). The UXSPi will
automatically install the latest BIOS, IPMI baseboard management controller
(BMC), Remote Supervisor Adapter II (RSA II), ServeRAID, and other firmware as
required for your server. It will also automatically install the required IPMI device
drivers for the BMC and the RSA Server Software for the RSA II. See the IBM
Systems support Web site at http://www.ibm.com/systems/support/ and select
the appropriate UpdateXpress System Pack Library to download the recommended
firmware and drivers for your system.
If you choose to not use the UpdateXpress System Pack Installer, perform the
following steps to download and install the latest ServeRAID Manager plug-in files
for your Red Hat Enterprise Linux, SUSE Linux, or VMware ESX Server system.
1. Go to http://www.ibm.com/systems/management/director/about/director52/
about52/downloads/ and navigate to the IBM Director Plug-ins & Extensions
for Windows and Linux on x86 section.
2. Download into a temporary directory the following files that are required for
your Platform-Agent managed system.
132
Table 31. IBM ServeRAID Manager 9.x plug-in (ServeRAID8 support)

Files
(See
Key 1)
RHEL
AS 4
U1
32-bit
RHEL
AS 4
U1
64-bit
RHEL
AS 5
U1
32-bit
RHEL
AS 5
U1
64-bit
SLES
SLES 9 SLES 9 10
32-bit
64-bit
32-bit
SLES
10
64-bit
VMware
ESX
X
X
Key 1:
v 1: RAIDLxLevel1-9.00-1.rhel4.i386.rpm (4MB)
v
v
v
v
v
2:
3:
4:
5:
6:
RAIDLxLevel1-9.00-1.rhel4.x86_64.rpm (4MB)
RAIDLxLevel1-9.00-1.rhel5.i386.rpm (4MB)
RAIDLxLevel1-9.00-1.rhel5.x86_64.rpm (4MB)
RAIDLxLevel1-9.00-1.i386.rpm (4MB)
RAIDLxLevel1-9.00-1.x86_64.rpm (4MB)
v 7: RAIDLxLevel1-9.00-1.sles10.i586.rpm (4.2MB)
v 8: RAIDLxLevel1-9.00-1.sles10.x86_64.rpm (4.2MB)
3. Navigate to the temporary directory into which you downloaded the files.
4. Use a console prompt from the temporary directory to run the following
commands for each of the downloaded files:
rpm -ivh RAIDLxLevel1-9.00-1.XXXXX.XXXXX.rpm
5. To install the Mega RAID Provider for systems with MR10K, 10M, and 10i
controllers installed, download into a temporary directory the following
individual files that are required for your servers from https://
www14.software.ibm.com/webapp/iwm/web/reg/download.do?source=dmp
&S_PKG=director_x_ext&lang=en_US.
Table 32. LSI Mega RAID Provider plug-in files
Files
(See
Key 3)
RHEL
AS 4
U6
32-bit
RHEL
AS 4
U6
64-bit
2
3
RHEL
AS 5
U1
32-bit
RHEL
AS 5
U1
64-bit
SLES
SLES 9 SLES 9 10
32-bit
64-bit
32-bit
SLES
10
64-bit
VMware
ESX
X
X
X
X
Key 3:
v 1: lsi_mr_hhr-00.02.G5.04-1.rhel4.i386.rpm (3.2MB)
133
v 3: lsi_mr_hhr-00.02.G5.04-1.sles9.i586.rpm (3.2MB)
v 4: lsi_mr_hhr-00.02.G5.04-1.sles10.i386.rpm (3.2MB)
6. Navigate to the temporary directory into which you downloaded the files.
7. Use a console prompt to run the following commands from the temporary
directory for each of the downloaded files:
rpm -ivh lsi_mr_hhr-00.02.G5.04-1.xxxxxx.ix86.rpm

Use these instructions to install the IBM Systems Director virtualization manager
subagent on the required host systems in your environment.
Common Agent must be installed on the system where you plan to install IBM
Systems Director virtualization manager subagent.
Installing virtualization manager subagents using the

installation wizard
You can access and install virtualization manager subagents from the Release
Management section of the IBM Systems Director Web interface.
Common Agent must be installed on the system where you plan to install IBM
Systems Director virtualization manager subagent.
To install IBM Systems Director virtualization manager subagent on the host
system using the installation wizard, complete the following steps:
1. In the IBM Systems Director navigation pane, expand Release management.
2. Click Agents.
3. On the Agents page, click Common Agent Subagent Packages.
4. From the Common Agent Subagent Packages view, select the subagent that you
want to install. You can choose from the following list of subagent packages:
Common Agent subagent package
Subagent for VMware ESX Server 3.x and

3.5.x
CommonAgentSubagent_VSM_ESX3x-6.1.0
Subagent for Microsoft Virtual Server
CommonAgentSubagent_VSM_MSVS-6.1.0
Subagent for VMware VirtualCenter 2.x and

2.5.x
CommonAgentSubagent_VSM_VC2x-6.1.0
Note: Xen hosts do not require a virtualization manager subagent to be

installed. All Xen virtual server management capabilities are provided through
the Platform Agent.
5. When you have selected the subagent you want to install, click Actions from
the menu bar, and select Release Management Install Agent.
6. Complete the instructions in the installation wizard to install the appropriate
virtualization manager subagent on your host system.
7. When the installation is complete, right-click on the host system in Navigate
Resources, and select Security Verify Connection. When this task is complete,
you can access virtualization manager tasks.
134
Installing virtualization manager subagents manually

You can locate virtualization manager subagents on IBM Systems Director Server
and install them manually on host systems in your environment.
To install IBM Systems Director virtualization manager subagent on the host
system, complete the following steps:
1. Copy the IBM Systems Director virtualization manager subagent to the host
system by completing the following steps:
a. Locate the subagent in the following directory path on the IBM Systems
Director Server: Director/tpm/repository/ where Director is the path where
IBM Systems Director is installed. The default location is:
v Linux: /opt/ibm/director/tpm/repository
v Windows: C:\Program Files\IBM\Director\tpm\repository
Each subagent has a directory that begins with CommonAgentSubagent_VSM_.
For example, the ESX3 subagent is in directory
CommonAgentSubagent_VSM_ESX3x_6.1.0. Each directory has one ZIP file that
contains the feature for that subagent. See the following example:
repository\
CommonAgentSubagent_VSM_ESX3x_6.1.0\
vsmesx3x_subagent.zip
CommonAgentSubagent_VSM_MSVS_6.1.0\
vsmmsvs_subagent.zip
CommonAgentSubagent_VSM_VC14x_6.1.0\
vsmvc14x_subagent.zip
CommonAgentSubagent_VSM_VC2x_6.1.0\
vsmvc2x_subagent.zip
b. Copy the appropriate ZIP file to a temporary directory on the host system,
such as c:\temp\site or /tmp/site. For example,
c:\temp\site\vsmesx3x_subagent.zip
2. Install the IBM Systems Director virtualization manager subagent on the host
system, by completing the following steps:
a. Change directory to the host system bin directory for your operating
system:
v Windows: c:\program files\ibm\director\agent\bin
v xLinux (VMware ESX Server): /opt/ibm/director/agent/bin
b. Run the install tool, as follows:
Note: Line indents indicate a continuation of the preceding line. Both lines
are intended to go all on one line.
VMware ESX Server 3.0
./lwiupdatemgr.sh -installFeatures -featureId com.ibm.director.
vsm.esx3x.agent
-fromSite jar:file:/tmp/site/vsmesx3x_subagent.zip\!/site.xml
-toSite "file:/opt/ibm/director/agent/runtime/agent/subagents/
eclipse/"
VMware VirtualCenter 1.4

lwiupdatemgr -installFeatures -featureId com.ibm.director.vsm.
vc14x.agent
-fromSite jar:file:/c:/temp/site/vsmvc14x_subagent.zip!/site.xml
-toSite "file:/c:/program files/ibm/director/agent/runtime/agent/
subagents/eclipse/"
135
VMware VirtualCenter 2.0

vc2x.agent
-fromSite jar:file:/c:/temp/site/vsmvc2x_subagent.zip!/site.xml
subagents/eclipse/"
Microsoft Virtual Server

msvs.agent
-fromSite jar:file:/c:/temp/site/vsmmsvs_subagent.zip!/site.xml
subagents/eclipse/"
where tmp/site or temp/site is the name of the temporary directory you

have created.
3. Verify that the IBM Systems Director virtualization manager subagent was
installed successfully. Refer to the following error logs:
v Windows: Director\agent\logs\*.log
v Linux: Director/agent/logs/*.log
where Director is the path where IBM Systems Director is installed.
4. Stop and restart the Common Agent to activate the IBM Systems Director
virtualization manager subagent by running the following script files:
v Windows:
Director\agent\runtime\agent\bin\endpoint.bat stop
Director\agent\runtime\agent\bin\endpoint.bat start
v Linux:
Director/agent/runtime/agent/bin/endpoint.sh stop
Director/agent/runtime/agent/bin/endpoint.sh start
where Director is the path where IBM Systems Director is installed.
136
Chapter 7. Upgrading and migrating IBM Systems Director

This is information about upgrading and migrating from IBM Director to IBM
Systems Director 6.1.
Migration from IBM Director 5.10 to IBM Systems Director 6.1 is not supported.
If you currently have an IBM Director 5.20 system, the following information
applies:
v You are advised not to install IBM Systems Director 6.1 on the same system that
currently has IBM Director 5.20 installed. Instead, choose a different system for
IBM Systems Director 6.1.
v You have the option to perform migration to IBM Systems Director 6.1 manually.
See Manual migration.
v You have the option to use the IBM Systems Director Migration Tool, which
automates most migration tasks.
v Some operating systems or hardware that were supported for older versions of
IBM Director are not supported in later versions. Check the Planning section for
a list of supported operating systems and hardware.
Related reference
Chapter 2, Planning for IBM Systems Director, on page 17
Manual migration
This is information about manually upgrading and migrating from IBM Director to
IBM Systems Director 6.1.
If you currently have an IBM Director 5.20 system, you are advised not to install
IBM Systems Director 6.1 on the same system that currently has IBM Director.
Instead, choose a different system for IBM Systems Director 6.1.
Note:
1. The information in this topic is not a comprehensive view of the steps you
need to follow to perform a manual migration of your data. For additional
information and instructions for manually migrating your IBM Director 5.20
data to an IBM Systems Director 6.1 environment, see the IBM Systems Director
6.1 Migration from IBM Director 5.20 Tips and Information white paper on the
Web at: www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=SA
&subtype=WH&appname=STGE_XB_XB_USEN_&htmlfid=XBW03009USEN
&attachment=XBW03009USEN.PDF
2. There is no manual migration for Virtualization manager. Virtualization
manager systems must be rediscovered.
IBM Systems Director 6.1 can manage systems running IBM Director Core Services
version 5.20 and IBM Director Agent version 5.20.
To manually upgrade from IBM Director Server 5.20 to IBM Systems Director
Server 6.1 and migrate the IBM Director 5.20 data to IBM Systems Director 6.1,
137
1. Install IBM Systems Director Server 6.1 on a different management server than
the one on which you have installed IBM Director Server 5.20.
Tip: There is no need to upgrade IBM Director Console 5.20. In IBM Systems
Director 6.1 the IBM Systems Director Web interface uses a Web browser and
does not require a separate installation.
2. Manually add all of the items from the IBM Director 5.20 server to IBM
Systems Director Server 6.1.
3. System x only: If you have made modifications to the storage provisioning
settings from IBM Server Storage Provisioning Tool, use the following
procedure to migrate the SSPTSettings.xml file:
a. Locate this file on the IBM Director 5.20 system:
install_root/data/SSPTSetting.xml
where install_root is the directory where IBM Director 5.20 is installed.
b. Copy the SSPTSettings.xml file to this location on the IBM Systems Director
6.1 system:
install_root\data
4.
5.
6.
7.
where install_root is the directory where IBM Systems Director 6.1 is

installed.
Threshold Plans are not available in IBM Systems Director 6.1 and therefore
will not be migrated from IBM Director 5.20. If you need to migrate the
functionality of a Threshold plan to 6.1, follow these steps from the 6.1 IBM
Systems Director Web interface.
a. From the Health Summary Page, create a Static Group that contains all of
the endpoints specified in the threshold plan.
b. From the Monitors View, select the Browse button. Under Groups, Personal
Groups, select the group created for the threshold plan.
c. Select and Show the Monitors that you want.
d. Activate the thresholds specified in the threshold plan for the group.
Start IBM Systems Director Server 6.1.
Optional: Depending on what data has been manually migrated, you might
have to run discovery for the IBM Director 5.20 system.
To upgrade systems running IBM Director Core Services version 5.20 and IBM
Director Agent version 5.20, use the Agent Installation Wizard to deploy either
Platform Agent or Common Agent on these systems.
Related tasks
Backing up IBM Systems Director data before upgrading or updating
IBM Systems Director Migration Tool

The IBM Systems Director Migration Tool is used to migrate data from IBM
Director 5.20 to a new installation of IBM Systems Director 6.1. Both the IBM
Director 5.20 system, and the IBM Systems Director 6.1 system must be running
the same operating system. The only supported operating systems are Linux,
Windows, and AIX.
The IBM Systems Director 6.1 system must be a new installation or a clean
installation that has been updated to version 6.10.02. This update is performed from
138
within IBM Systems Director 6.1 and requires that the system running IBM
Systems Director 6.1 be discovered. After IBM Systems Director 6.1 has been
upgraded, the data must be reset. This can be accomplished by running the
smreset command from the command line. If smreset is not run, the IBM Systems
Director Migration Tool will still run, but results might be unpredictable. IBM will
not support running the IBM Systems Director Migration Tool to import data to a
system that has not first been updated to version 6.10.02 and has not run smreset
prior to importing the data.
The IBM Systems Director Migration Tool does not perform these tasks:
v Migrate data from one IBM Systems Director 6.1 system to another IBM Systems
Director 6.1 system.
v Migrate data from one IBM Director 5.20 system to another IBM Director 5.20
system.
v Migrate data from an IBM Director 5.10 system.
v Migrate data from versions of the IBM Systems Director plug-in Active Energy
Manager, formerly called PowerExecutive, older than version 3.1.
v Migrate data from an IBM Director 5.20 system that is running any operating
system other than Windows, Linux, or AIX.
v Migrate data to an IBM Systems Director 6.1 system that is running any
operating system other than Windows, Linux, or AIX.
v Migrate data from a IBM Director 5.20 system to a IBM Systems Director 6.1
system, when the two systems have different operating systems. However, the
IBM Director 5.20 and IBM Systems Director 6.1 systems can have different
versions and releases of the same operating system.
v Migrate data to an IBM Systems Director 6.1 system that is not a new
installation.
v Migrate data to an IBM Systems Director system that has not been updated to
version 6.10.02 or later.
v Migrate data to an IBM Systems Director system where the smreset command
has not been run prior to the import task.
v Allow the user to select which pieces of data or types of data are to be migrated.
The IBM Systems Director Migration Tool migrates all data that it has been
programmed to migrate, except for the situation where a failure has occurred.
v Migrate data from versions of the IBM Systems Director Virtualization manager
plug-in older than version 1.2.2.
The IBM Systems Director Migration Tool is a command-line utility. There are two
parts to the utility: smexport and smimport. Both smexport and smimport are
invoked from the command-line. Refer to the smexport and smimport commands
for more detail.
Related tasks
Obtaining and installing the IBM Systems Director Migration Tool on page 142
Exporting data from IBM Director 5.20 on page 143
Importing IBM Director 5.20 data into IBM Systems Director 6.1 on page 144
Considerations for the IBM Systems Director Migration Tool

Review these considerations about system security, performance, disk space, and
updates before running the IBM Systems Director Migration Tool.
139
Security considerations
Your IBM Director 5.20 system has files with passwords and other sensitive data.
The IBM Systems Director Migration Tool has features to ensure that this data is
safe during all phases of migration.
The -e (encrypt) and -p (password) command flags are used to encrypt the
exported data and retrieve it upon import. If you choose to not use these flags and
the IBM Systems Director Migration Tool detects a password or other credential
data, this data will not be saved to the exported directory, and appropriate error
messages will be issued. No passwords or credential data will be stored in
plaintext. The AES (Advanced Encryption Standard) is used to perform encryption.
Disk space and performance considerations

Active Energy Manager
IBM Systems Director Active Energy Manager migration requires disk
space to migrate its data, but also additional disk space to process the data
during both export and import. The additional disk space required can be
quite large. For information about disk space requirements related to
migration of data for Active Energy Manager, see Migrating Active Energy
Manager in the Active Energy Manager 4.1 documentation.
Update manager
The update manager migration exports all IBM System x updates that are
stored in IBM Director 5.20. Before migrating, check the size of the update
library located at Director 5.20/data/updatelib/ (where Director 5.20 is the
directory where IBM Director 5.20 is installed), and ensure that you have
adequate disk space available in your IBM Systems Director 6.1 installation
location.
Update manager considerations

Update manager has a requirement that you discover and unlock the local server
resource before or (automatically) during the server startup process. Because of this
requirement, before running the IBM Systems Director Migration Tool, it might be
necessary to first unlock the server and then shut it down.
Migrated data
A list of data this is migrated by the IBM Systems Director Migration Tool, and a
list of data that is not migrated, are both presented here.
Data that is migrated

This is a brief list of each type of IBM Director 5.20 data to be migrated to IBM
Systems Director 6.1 by the IBM Systems Director Migration Tool.
Active Energy Manager data
For information about the migration of data for Active Energy Manager, an
IBM Systems Director plug-in, see Migrating Active Energy Manager in the
Active Energy Manager 4.1 documentation.
Configuration profiles
Existing IBM Director 5.20 configuration profiles are converted to IBM
Systems Director 6.1 configuration plans. Each IBM Director 5.20
configuration plugin within a configuration profile is converted to an IBM
140
Systems Director 6.1 configuration template. You can then edit or deploy
these configuration plans and templates through configuration manager.
Events
Events and event action plans that have been created in IBM Director 5.20
are migrated. This does not include event logs or event subscriptions,
which are not migrated.
Groups
All static groups and some dynamic groups are migrated. Other dynamic
groups are not migrated by the IBM Systems Director Migration Tool and
must be migrated manually. Task groups are not migrated by the IBM
Systems Director Migration Tool.
Level 0 Agents
Any agentless systems that were previously discovered in IBM Director
5.20 are migrated.
Level 1 Agents
Any systems with a core service agent (CIM agent) that has been installed
and discovered are migrated.
Level 2 Agents
Any systems with a level 2 IBM Director 5.20 agent installed and
discovered are migrated.
Platform Objects
Any systems management devices such as: Remote Supervisor Adapters,
Baseboard Management Controllers, IBM BladeCenter Advanced
Management Modules, IBM BladeCenter Management Modules, Integrated
Virtualization Managers, or Hardware Management Consoles, that have
previously been discovered in IBM Director 5.20 are migrated.
Relocation Manager
Any relocation manager plans that were created in IBM Director 5.20 are
migrated. The relocation Manager was part of the Virtualization Manager
extension in IBM Director 5.20.
Virtualization manager
As part of the IBM Systems Director Migration Tool processing, the data
specific to Virtualization manager (roles, relationships, and so forth) is
regenerated, with the discovery process, after the platform objects are
migrated.
Security
User and group access to specific tasks and data that was set up in IBM
Director 5.20 is migrated. This does not include automatically recreating
local users on the new IBM Systems Director 6.1 management server.
SNMP devices
Any SNMP devices such as printers and active power distribution units
(PDUs) that were discovered on IBM Director 5.20 are migrated.
Storage
Storage systems, such as the IBM System Storage DS3000 and DS4000
families of storage systems, are migrated.
System status and health
Any monitors that were created for systems are migrated. This does not
include threshold plans and group thresholds. See the topic Manual
migration for steps to manually migrate some of this data.
141
Updates
All IBM System x updates that are stored in IBM Director 5.20 are
migrated.
Data that is not migrated

This is a brief list of each type of IBM Director 5.20 data that is not migrated to
IBM Systems Director 6.1 by the IBM Systems Director Migration Tool.
v Event Logs
v Event Subscriptions
v Inventory
v Process Monitors that are targeted to specific resources
v Resource Monitors and Resource Monitor tasks
v Group Thresholds
Some of this information can be manually migrated. See the topic Manual
migration.
v Update profiles used by update manager
v The updatePlatforms.txt file
IBM Systems Director Active Energy Manager migration

If the IBM Systems Director Active Energy Manager server plug-in version 3.1 or
later is installed on the IBM Director 5.20 system, and the Active Energy Manager
plug-in version 4.1 is installed on the IBM Systems Director 6.1 system, its data
will be migrated as well.
Throughout this document, whenever IBM Director data is mentioned, it includes
data from Active Energy Manager, if installed. Whenever IBM Systems Director 6.1
install is mentioned, it includes, if required, installing the Active Energy Manager
plug-in version 4.1. The IBM Systems Director Migration Tool includes support for
migrating Active Energy Manager data.
Note: If the stand-alone version of Active Energy Manager version 3.1 or later is
installed, IBM supports the migration only of data and objects related to Active
Energy Manager use and function.
Obtaining and installing the IBM Systems Director Migration Tool

The IBM Systems Director Migration Tool is delivered as a Web download.
Specifically the IBM Systems Director Migration Tool is a set of files containing a
batch file or shell script named smexport or smimport. There are no requirements
on the location for placing the IBM Systems Director Migration Tool files.
There are two compressed files, one for the export task on the IBM Director 5.20
system, and another for the import task on the IBM Systems Director 6.1 system.
To obtain and install the IBM Systems Director Migration Tool, complete the
following steps:
1. Point your Web browser to this location: https://www.ibm.com/services/
forms/preLogin.do?source=dmp&lang=en_US&S_PKG=SysDir6_1_mkt.
2. Obtain the files used for export:
a. Copy the migration-5.20.zip file to the IBM Director 5.20 management
server.
142
b. Extract this file to a directory. The name tool-installation-path\migration-5.20

is used in this scenario.
3. Obtain the files used for import:
a. Connect to the IBM Systems Director 6.1 management server and copy the
migration-6.1.zip file to this server.
b. Extract this file to a directory. The name tool-installation-path\migration-6.1
is used in this scenario.
The next step is to export IBM Director 5.20 data to a directory.
Related concepts
IBM Systems Director Migration Tool on page 138
Exporting data from IBM Director 5.20

Use the smexport command to export IBM Director 5.20 data to a directory, so that
it can be loaded onto a new IBM Systems Director 6.1 system.
Before you start to export IBM Director 5.20 data:
v Make sure that you have a clear understanding of what types of data are going
to be exported.
v Minimize the workload of the IBM Director 5.20 management server.
v This procedure assumes that you have installed the export portion of IBM
Systems Director Migration Tool in the directory named tool-installation-path\
migration--5.20, which this procedure calls tool-installation-location. If you have
used another directory, substitute that directory name in these steps.
To export IBM Director 5.20 data, complete the following steps:
1. From the command prompt:
v On Windows systems, run the smexport batch file.
v On Linux or AIX systems, run the smexport script.
2. While the command is running, check for error messages. A large amount of
related information will scroll by on the command-prompt window. If an error
is encountered, IBM Systems Director Migration Tool can stop unexpectedly
and an error message will be displayed.
3. When the command completes, the exported data will be in the
tool-installation-location\migration\DMIG0000 directory on Windows systems
or tool-installation-location/migration/DMIG0000 directory on Linux and AIX
systems.
Note: The number, DMIG0000, is incremented for each smexport command
invocation on the same system.
4. When the command completes, review the log file for errors. The name of the
log file is migration.log, and it is located in same directory as the exported
data.
v If the smexport command did not complete to your satisfaction, do not copy
the exported data to the new IBM Systems Director 6.1 system and do not
try to import this data. Try to determine what went wrong and rerun the
smexport command.
v If the smexport completed to your satisfaction, copy the exported data to the
new IBM Systems Director 6.1 management server, using any standard copy
program such as FTP.
143
The next step is to import the migrated data.

Related concepts
Importing IBM Director 5.20 data into IBM Systems Director 6.1
Use the smimport command to import data from IBM Director 5.20 that has been
stored in a directory to a new IBM Systems Director 6.1 system.
Before you start to import IBM Director 5.20 data to your IBM Systems Director 6.1
management server, consider these points:
v IBM Systems Director Migration Tool will bring down the IBM Systems Director
6.1 management server.
v This procedure assumes that you have installed the import portion of IBM
Systems Director Migration Tool in the directory named tool-installation-path\
migration-6.1, which this procedure calls tool-installation-location. If you have
used another directory, substitute that directory name in these steps.
To import IBM Director 5.20 data to your IBM Systems Director 6.1 management
server, complete the following steps:
1. Make sure that you have a clean installation of IBM Systems Director Server
6.1.
2. If necessary, start the IBM Systems Director Server.
3. Using the IBM Systems Director Web interface, log in to the IBM Systems
Director 6.1 management server.
4. If necessary, discover and unlock the Operating System endpoint for the
system that IBM Systems Director 6.1 is running on.
5. Perform an update of the IBM Systems Director Server 6.1 to include patch
6.1.0.2.
6. Log out from the IBM Systems Director 6.1 management server.
7. Open a command prompt window and stop the IBM Systems Director Server.
v On Windows systems, run the command: net stop dirserver.
v On Linux or AIX systems, run the command: smstop.
In both cases, wait for the IBM Systems Director Server to shut down
completely.
8. At the command prompt, run the command: smreset. This command may take
a long time to complete.
9. Copy the contents of the export directory created in the export task to the IBM
Systems Director 6.1 management server in the following location:
tool-installation-location\migration.
10. Issue the smimport -a command to import the data.
11. While the command is running, check for error messages.
12. Make sure that the tool completes successfully and prints the following
message: Migration tool processing completed. If you run into any errors or
issues and do not see this message, you will need to restart the import
process.
13. Review the log file for error messages.
v If the smimport command did not complete to your satisfaction:
a. Review all your steps carefully.
b. Review the log file for error messages.
144
c. To obtain more detailed error messages, run the smimport command

with the -v option and review the log that is produced.
d. To recover, you will most likely have to rerun the smexport command
on the IBM Director 5.20 system.
v If the smimport command completed to your satisfaction perform a few
small IBM Systems Director 6.1 tasks to verify that the data has been
imported. This will vary depending on what type of data was imported.
14. Optional: When you are satisfied with the imported data, consider deleting
the files or directories used to perform the migration. This will prevent
unintended use of the IBM Systems Director Migration Tool. Remember that
the IBM Systems Director Migration Tool is available on the Web if you
should need it again.
v On both IBM Director 5.20 and IBM Systems Director 6.1 systems, delete the
compressed file that contains the IBM Systems Director Migration Tool, and
the files that you retrieved from it.
v On both IBM Director 5.20 and IBM Systems Director 6.1 systems, delete the
directory of data produced by the smexport command.
Related concepts
145
146
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document
in other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the users responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
147
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
MW9A/050
5600 Cottle Road
San Jose, CA 95193
U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer
Agreement, IBM International Program License Agreement, or any equivalent
agreement between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBMs future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corporation in the United States, other countries,
or both. If these and other IBM trademarked terms are marked on their first
occurrence in this information with a trademark symbol ( or ), these symbols
indicate U.S. registered or common law trademarks owned by IBM at the time
this information was published. Such trademarks may also be registered or
148
common law trademarks in other countries. A current list of IBM trademarks is

available on the Web at Copyright and trademark information at
www.ibm.com/legal/copytrade.shtml.
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered
trademarks or trademarks of Adobe Systems Incorporated in the United States,
and/or other countries.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,
Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or
registered trademarks of Intel Corporation or its subsidiaries in the United States
and other countries.
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States, other
countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United
States, other countries, or both.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other
names may be trademarks of their respective owners.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Other company, product, or service names may be trademarks or service marks of
others.
Notices
149
150
Readers Comments Wed Like to Hear from You

IBM Systems
Version 6.1
Publication No. GI11-8711-01
We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,
organization, subject matter, or completeness of this book. The comments you send should pertain to only the
information in this manual or product and the way in which the information is presented.
For technical questions and information about products and prices, please contact your IBM branch office, your
IBM business partner, or your authorized remarketer.
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use
the personal information that you supply to contact you about the issues that you state on this form.
Comments:
Thank you for your support.

Send your comments to the address on the reverse side of this form.
If you would like a response from IBM, please fill in the following information:
Name
Address
Company or Organization
Phone No.
E-mail address
GI11-8711-01

___________________________________________________________________________________________________
Readers Comments Wed Like to Hear from You
Cut or Fold
Along Line
_ _ _ _ _ _ _Fold
_ _ _and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ _do
_ _not
_ _ staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
BUSINESS REPLY MAIL

FIRST-CLASS MAIL
PERMIT NO. 40
ARMONK, NEW YORK
POSTAGE WILL BE PAID BY ADDRESSEE
International Business Machines Corporation

ATTN: Dept D06A
PO Box 12195
Research Triangle Park, NC
USA 27709-9990
_________________________________________________________________________________________
Fold and Tape
Please do not staple
Fold and Tape
GI11-8711-01
Cut or Fold
Along Line

Printed in USA
GI11-8711-01

IBM Director Install Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IBM Director Install Guide

Uploaded by

Copyright:

Available Formats

IBM Systems Director for Windows

IBM Systems Director for Windows

Copyright International Business Machines Corporation 1999, 2008.

Conventions and terminology . . . . . . . . v

Checklist: Installing IBM Systems

Chapter 2. Planning for IBM Systems

Copyright IBM Corp. 1999, 2008

IBM Systems Director task support for Storage

Chapter 3. Installing IBM Systems

Logging on to IBM Systems Director Server for the

Chapter 4. Preparing agentless

Chapter 5. Discovering systems and

Chapter 6. Installing agents . . . . . 125

Obtaining licenses for Common Agent . .

Chapter 7. Upgrading and migrating

About this publication

Planning an IBM Systems Director environment

Conventions and terminology

Publications and related information

Information centers and topic collections

Planning, Installation, and Configuration Guide for Windows

White papers and briefs

About this publication

IBM Redbooks publications

How to send your comments

About this publication

Checklist: Installing IBM Systems Director Server on Windows

hardware requirements (17).

__ 5. Check the supported database applications (35).

5 Log on and configure IBM Systems Director Server.

Copyright IBM Corp. 1999, 2008

Checklist: Installing agents on Windows

5 Install the agents.

Copyright IBM Corp. 1999, 2008

Chapter 1. IBM Systems Director technical overview

Linux on System z running on a partition without z/VM

IBM Systems Director components

IBM Systems Director Server installed

Agentless managed systems

Platform managed systems

Common managed systems

Figure 1. Software in an IBM Systems Director environment

Monitor health and status

For a detailed list of function that is supported by Platform-Agent managed

Chapter 1. IBM Systems Director technical overview

Manageable resource types

Base function and extensible plug-ins

Basic user interface, security, and agent management functions include:

Chapter 1. IBM Systems Director technical overview

status-related tasks, navigating to a specific resource, or using the new capabilities

You can use the automation manager plug-in to:

Remote access manager

Chapter 1. IBM Systems Director technical overview

IBM BladeCenter and System x management

IBM System z management

IBM Power Systems management

discovery, health and status monitoring, configuration, updates, and virtualization.

IBM System Storage management

Additional IBM Systems Director plug-ins

Chapter 1. IBM Systems Director technical overview

Active Energy Manager plug-in

BladeCenter Open Fabric Manager plug-in

Service and Support Manager plug-in

Chapter 1. IBM Systems Director technical overview