dir6.1_install_gde_xlinux

IBM Systems

IBM Systems Director for Linux on x86

Planning, Installation, and Configuration Guide

Version 6.1

GI11-8712-00

��

Note

Before using this information and the product it supports, read the information in “Notices” on

page 119.

© 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 Linux on x86 . . . . xi

Checklist: Installing agents on Linux

on x86 . . . . . . . . . . . . . . . xiii

Chapter 1. IBM Systems Director

technical overview . . . . . . . . . . 1

IBM Systems Director components . . . . . . . 2

Management server . . . . . . . . . . . 3

Common Agent . . . . . . . . . . . . 4

Platform Agent . . . . . . . . . . . . 5

Agentless-managed systems . . . . . . . . 5

Manageable resource types . . . . . . . . . 6

Manageable systems . . . . . . . . . . . . 6

User interfaces . . . . . . . . . . . . . . 7

Base function and extensible plug-ins . . . . . . 8

Discovery manager . . . . . . . . . . . 9

Status manager . . . . . . . . . . . . 9

Configuration manager . . . . . . . . . 10

Automation manager . . . . . . . . . . 10

Update manager . . . . . . . . . . . . 11

Remote access manager . . . . . . . . . 11

Virtualization manager . . . . . . . . . 12

IBM BladeCenter and System x management . . 12

IBM System z management . . . . . . . . 12

IBM Power systems management . . . . . . 12

IBM System Storage management . . . . . . 13

Additional IBM Systems Director plug-ins . . . 13

Upward integration . . . . . . . . . . . . 14

Chapter 2. Planning for IBM Systems

Director . . . . . . . . . . . . . . 17

Hardware and software requirements . . . . . . 17

Hardware requirements for IBM Systems Director 17

Supported IBM systems and products . . . . 18

IBM BladeCenter products . . . . . . . . 19

Supported storage devices . . . . . . . . 20

Network requirements . . . . . . . . . . 22

Security requirements . . . . . . . . . . 31

Operating system and software requirements . . 31

IBM Systems Director task support by operating

system and agent levels . . . . . . . . . 37

IBM Systems Director task support not affected

by operating systems . . . . . . . . . . 39

IBM Systems Director task support for

BladeCenter products . . . . . . . . . . 40

IBM Systems Director task support for Storage

products . . . . . . . . . . . . . . 41

National languages supported by IBM Systems

Director . . . . . . . . . . . . . . 42

Planning to install IBM Systems Director . . . . 42

Service and support information . . . . . . 42

Reviewing the environment . . . . . . . . 43

Version compatibility of IBM Systems Director

version 6.1 components . . . . . . . . . 46

License information . . . . . . . . . . . 47

Obtaining licenses for Common Agent . . . . 47

Choosing the IBM Systems Director Server

installation options . . . . . . . . . . . 48

Choosing where to install IBM Systems Director

Server . . . . . . . . . . . . . . . 49

Choosing the IBM Systems Director database

application . . . . . . . . . . . . . 50

Choosing the management level for managed

systems . . . . . . . . . . . . . . . 52

Planning for virtual environments . . . . . . 54

Disaster recovery for IBM Systems Director 6.1 . . 54

Planning for events . . . . . . . . . . . . 55

Planning events to be monitored . . . . . . 56

Planning for event automation plan

implementations . . . . . . . . . . . . 57

Planning IBM Systems Director security . . . . . 60

Planning IBM Systems Director users and groups 60

Planning Secure Sockets Layer configuration on

IBM Systems Director . . . . . . . . . . 61

Planning password management in IBM Systems

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

Preparing to install IBM Systems Director Server

on Linux for System x and x86-based systems . . 80

Installing IBM Systems Director on the management

server . . . . . . . . . . . . . . . . 85

Installing IBM Systems Director Server on Linux

for System x and x86-based systems . . . . . 86

Configuring the database application after IBM

Systems Director installation . . . . . . . . . 90

Configuring IBM Systems Director Server after

installation . . . . . . . . . . . . . . 91

Configuring IBM Systems Director plug-ins and

platforms . . . . . . . . . . . . . . 92

Configuring the command line interface . . . . 92

Reviewing Microsoft Internet Explorer security

options . . . . . . . . . . . . . . . 94

Logging on to IBM Systems Director Server for the

first time . . . . . . . . . . . . . . . 95

© Copyright IBM Corp. 1999, 2008 iii

Chapter 4. Preparing agentless

managed systems . . . . . . . . . . 97

Preparing to manage a IBM BladeCenter . . . . 97

Preparing to manage a IBM BladeCenter chassis

using IBM Systems Director Server on a

non-blade server . . . . . . . . . . . . 97

Preparing to manage a IBM BladeCenter chassis

using IBM Systems Director Server on a blade

server . . . . . . . . . . . . . . . 98

Preparing VMware managed systems . . . . . 100

Chapter 5. Discovering systems and

collecting inventory data . . . . . . 101

Discovery protocols . . . . . . . . . . . 101

Discovering systems with system discovery . . . 102

System discovery . . . . . . . . . . . 102

Performing a system discovery . . . . . . 103

Viewing system discovery results . . . . . . 104

Accessing a secured system with request access 104

Chapter 6. Installing agents . . . . . 107

Preparing a Platform-Agent managed system . . . 107

Preparing to install Platform Agent on Linux for

System x and x86-based systems . . . . . . 107

Preparing VMware managed systems . . . . 108

Preparing a Common-Agent managed system . . 109

Obtaining licenses for Common Agent . . . . 109

Preparing to install Common Agent on Linux

for System x and x86-based systems . . . . 109

Preparing VMware managed systems . . . . 111

Installing agents using the Agent Installation

Wizard . . . . . . . . . . . . . . . 111

Installing the LSI MegaRAID provider for

Windows or Linux . . . . . . . . . . . . 114

Installing virtualization manager subagents . . . 116

Installing virtualization manager subagents

using the installation wizard . . . . . . . 116


manually . . . . . . . . . . . . . . 117

Notices . . . . . . . . . . . . . . 119

Trademarks . . . . . . . . . . . . . . 120

iv IBM Systems Director for Linux on x86 Planning, Installation, and Configuration Guide

About this publication

This IBM Systems Director for Linux® on x86 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 Planning an IBM Systems Director environment

v Installing IBM Systems Director

v Upgrading from IBM Director 5.20 or earlier to IBM Systems Director 6.1

v 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

© Copyright IBM Corp. 1999, 2008 v

http://www.adobe.com/products/acrobat/readstep.html

http://www.adobe.com/products/acrobat/readstep.html

http://publib.boulder.ibm.com/infocenter/systems/index.jsp

http://publib.boulder.ibm.com/infocenter/systems/topic/director_6.1/fqm0_main.html

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_6.1/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 enterprise-management 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 IBM Systems Director for Linux on x86 Planning, Installation, and Configuration Guide

http://publib.boulder.ibm.com/infocenter/systems/index.jsp

http://publib.boulder.ibm.com/infocenter/systems/topic/uims_6.1/fqs0_main.html

http://publib.boulder.ibm.com/infocenter/dirinfo/toolkit/index.jsp

http://publib.boulder.ibm.com/infocenter/systems/topic/main/dir6.1.0_relnotes.pdf

http://publib.boulder.ibm.com/infocenter/systems/topic/main/frn0_bk_compat_guide.pdf

http://publib.boulder.ibm.com/infocenter/systems/topic/main/fqp0_bk_install_gde_aix.pdf

http://publib.boulder.ibm.com/infocenter/systems/topic/main/fqp0_bk_install_gde_ibmi.pdf

http://publib.boulder.ibm.com/infocenter/systems/topic/main/fqp0_bk_install_gde_plinux.pdf

http://publib.boulder.ibm.com/infocenter/systems/topic/main/fqp0_bk_install_gde_xlinux.pdf

http://publib.boulder.ibm.com/infocenter/systems/topic/main/fqp0_bk_install_gde_zlinux.pdf

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 User’s 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


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.

About this publication vii

http://publib.boulder.ibm.com/infocenter/systems/topic/main/fqp0_bk_install_gde_windows.pdf

http://publib.boulder.ibm.com/infocenter/systems/topic/main/fqr0_bk_systm_mgmt.pdf

http://publib.boulder.ibm.com/infocenter/systems/topic/main/frq0_bk_troubleshoot.pdf

http://publib.boulder.ibm.com/infocenter/systems/topic/main/fqo0_bk_events_ref.pdf

http://publib.boulder.ibm.com/infocenter/systems/topic/main/frp0_bk_commands.pdf

http://publib.boulder.ibm.com/infocenter/systems/topic/main/mpcli_bk.pdf





http://www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH&appname=STGE_PO_PO_USEN&htmlfid=POW03011USEN&attachment=POW03011USEN.PDF



http://www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH&appname=STGE_XB_XB_USEN_&htmlfid=XBW03009USEN&attachment=XBW03009USEN.PDF



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.

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

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.

viii IBM Systems Director for Linux on x86 Planning, Installation, and Configuration Guide

http://www.ibm.com/redbooks/

http://www.ibm.com/systems/management/director/

http://www.ibm.com/systems/management/director/downloads/

http://www.ibm.com/systems/management/director/resources/

http://www.ibm.com/systems/management/director/upward/

http://www.ibm.com/servers/

http://www.ibm.com/servers/eserver/serverproven/compat/us/

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.

About this publication ix

http://www.ibm.com/developerworks/forums/forum.jspa?forumID=759

http://www.ibm.com/developerworks/forums/dw_esforums.jspa

http://www.ibm.com/developerworks/forums/dw_esforums.jsp

http://publib.boulder.ibm.com/infocenter/systems/topic/director_6.1/fqm0_main.html

x IBM Systems Director for Linux on x86 Planning, Installation, and Configuration Guide

Checklist: Installing IBM Systems Director Server on Linux on

x86

Use this checklist to guide you through the installation process.

�1� Evaluate your hardware and system configuration.

__ 1. Check the hardware requirements (17).

__ 2. Check the network requirements (22).

__ 3. Check the security requirements (31).

__ 4. Check the 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 (43).

__ 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 (49).

__ 5. Choose a database application to use with IBM Systems Director Server (50).

__ 6. Plan users, groups, and security options for IBM Systems Director Server (60).

�3� Prepare the management server.

__ 1. Prepare the database application (71).

__ 2. Prepare firewalls and proxies on the management server (79).

__ 3. Prepare the management server (80).

�4� Install IBM Systems Director Server.

__ 1. Install IBM Systems Director Server (86).

__ 2. Configure the database application (90).

�5� Log on and configure IBM Systems Director Server.

__ 1. Log in to IBM Systems Director Server (95).

__ 2. Perform some initial configuration of IBM Systems Director Server (91).

© Copyright IBM Corp. 1999, 2008 xi

xii IBM Systems Director for Linux on x86 Planning, Installation, and Configuration Guide

Checklist: Installing agents on Linux on x86

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

�2� Determine what agents you need to install.

__ 1. Review the task support for different management levels (37).

__ 2. Determine the management level you need for your managed systems (52).

__ 3. If you have virtual systems, determine what agents are needed for the virtual

systems (54).

__ 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 (97).

__ 2. Prepare systems for Platform Agent (107).

__ 3. Prepare systems for Common Agent (109).

�4� Discover the managed systems.

__ 1. Discover the managed systems on which you will install agents (102).

__ 2. Request access to the managed systems (104).

�5� Install the agents.

__ 1. Use the Agent Installation Wizard to deploy agent packages to your managed

systems (111).

__ 2. Install the LSI MegaRAID provider (114).

__ 3. Install virtualization manager subagents (116).

© Copyright IBM Corp. 1999, 2008 xiii

xiv IBM Systems Director for Linux on x86 Planning, Installation, and Configuration Guide

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 Director’s 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 systemsv 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 xv IBM System z management

– z/VM hypervisor

– Linux on System z operating system installed on z/VM® virtual servers

© Copyright IBM Corp. 1999, 2008 1

– Linux on System z running on a partition without z/VMv 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.

2 IBM Systems Director for Linux on x86 Planning, Installation, and Configuration Guide

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.

Browser system- no IBM Systems Directorcode installedC

Management server

IBM Systems Director Server installedIncludes:- IBM Systems Director Server- IBM Systems Director Web interface- Command-line Interface- Common Agent

SNMP devices

Agentless managed systems- no IBM Systems Director

de installedcoC Cco

Platform managed systems- Platform Agent installedon each

Common managed systems- Common Agent installedon each

HTTPS TCP/IP Various protocols

FQM0501-0

Agentless managed systems- no IBM Systems Directorcode installedC

Figure 1. Software in an IBM Systems Director environment

Chapter 1. IBM Systems Director technical overview 3

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 or IBM i 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 Monitor health and status

v Manage alerts

v Remotely deploy and install Common Agent

v Perform limited remote access

v 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 ways—using 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.


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 company’s 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.


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


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






http://www.ibm.com/systems/management/director/plugins/

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


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_6.10/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.




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 Linux on x86-compatible systems:

IBM Systems Director Server has certain hardware requirements to run on

x86-compatible systems running Linux.

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.


The following recommendations are based on a 32–bit version of SUSE Linux

Enterprise Server 10 for x86. The recommendations are comparable for Red Hat

Enterprise Linux on x86-compatible systems.

Table 1. IBM Systems Director Server recommended hardware requirements for

different-sized Linux environments

Configuration

Recommended hardware requirements

Processor Memory Disk storage

Small 1 processor, 3 GHz

Intel Xeon

1

1 GB 4 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

1 The processor (CPU) sizing is based on the Intel Xeon processor, but is comparable for

equivalent Intel® and AMD processors.

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 /opt/ibm/director/packaging/agent on the server.

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)

100 MB (for Linux)

110 MB (for Windows)

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.

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 IBM BladeCenter E chassis, machine type 8677

v IBM BladeCenter H chassis, machine type 8852

v IBM BladeCenter HT chassis, machine type 8740

v IBM BladeCenter HT chassis, machine type 8750

v IBM BladeCenter S chassis, machine type 8886

v IBM BladeCenter T chassis, machine type 8720

v IBM BladeCenter T chassis, machine type 8730

v HC10 blade server, machine type 7996

v HC10 blade server, machine type 7997

v HS12 blade server, machine type 8014







v HS21 XM blade server, machine type 7995



v JS12 blade server, machine type 7998



Chapter 2. Planning 19



v LS20 blade server, machine type 8850



v QS21 blade server, machine type 0792

v 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 Controllerv 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, DS3400v 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

IBM BladeCenter SAS

Modules

Fibre

Channel

Switches (2

Gbit/sec and

4 Gbit/sec)

IBM® System Storage DS™

Task

1064

1064e

1068

1078

Internal

RAID

1078

Mega

RAID

Connectivity

module

RAID

controller

module

Brocade and

Qlogic

3

2

0

0

3

3

0

0

3

4

0

0

4

0

0

0

6

0

0

0

Discovery Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

Inventory

collection

Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes


Table 3. Storage management tasks and supported devices (continued)

LSI SAS controllers

IBM BladeCenter SAS

Modules

Fibre

Channel

Switches (2

Gbit/sec and

4 Gbit/sec)

IBM® System Storage DS™

Task

1064

1064e

1068

1078

Internal

RAID

1078

Mega

RAID

Connectivity

module

RAID

controller

module

Brocade and

Qlogic

3

2

0

0

3

3

0

0

3

4

0

0

4

0

0

0

6

0

0

0

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


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


http://www.vmware.com/support/pubs/

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 TCP Inbound TFTP communication with BladeCenter I/O



Table 4. Ports used by IBM Systems Director Server for communication (continued)

Port

TCP or


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


Agentless-managed systems using Windows

DCOM



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)

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.


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



Port

TCP or


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.

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


2044 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


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



Port

TCP or


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

9000–9100 TCP Communication Platform-Agent managed system

running Xen

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

9511–9513 TCP Inbound Agent manager

9514–9515 TCP 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 IBM Systems Director interprocess communication


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


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 (Windows only) Communication with

Agentless-managed systems using Microsoft

Windows DCOM



DCOM



Server Message Block (SMB)

161 UDP Inbound SNMP agent communication with:





v Platform Agent



v Agentless-managed systems




Table 5. Ports on managed systems (continued)

Port

TCP or



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


6989 TCP Outbound CIM listener

9510 TCP Inbound Communication with Common Agent and CAS

Web services

14247 UDP Inbound IBM Systems Director interprocess communication


14248 UDP Outbound IBM Systems Director interprocess communication


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/




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.


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.

Table 6. Linux versions supported by IBM Systems Director on System x systems; IBM® and third-party x86-based

systems

Operating system

IBM

Systems

Director

Server

Common

Agent

Platform

Agent

Versions of Linux for 32-bit systems:

Red Hat Enterprise Linux AS, version 4.0 (supports Updates 5, 6, and 7) X X X

Red Hat Enterprise Linux ES and WS, version 4.0 (supports Updates 5, 6, and 7) X X

Red Hat Enterprise Linux AS, version 5.0 (supports Updates 1 and 2) X X X

Red Hat Enterprise Linux ES and WS, version 5.0 (supports Updates 1 and 2) X X

Red Hat Enterprise Linux AS, ES, and WS, version 5.0, with Xen Kernel (supports

Updates 1 and 2)

X

SUSE Linux Enterprise Server 9 for x86 (supports Service Packs 3 and 4) X X X

SUSE Linux Enterprise Server 10 for x86 (supports Service Packs 1 and 2) X X X

SUSE Linux Enterprise Server 10, with Xen Kernel (supports Service Packs 1 and

2)

X

VMware ESX Server, versions 3.0, 3.0.1, 3.0.2, 3.5, 3.5.1, and 3.5.2, Console X X

VMware ESX Server, versions 3.0, 3.0.1, 3.0.2, 3.5, 3.5.1, and 3.5.2, guest operating

systems

Notes:

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

2. IBM Systems Director Server is supported on VMware ESX Server if IBM

Systems Director Server is supported on the selected guest operating system.

X X X

Versions of Linux for 64-bit systems:

Red Hat Enterprise Linux AS, version 4.0, for AMD64 and EM64T (supports

Updates 5, 6, and 7)

X X X

Red Hat Enterprise Linux ES and WS, version 4.0, for AMD64 and EM64T

(supports Updates 5, 6, and 7)

X X

Red Hat Enterprise Linux AS, version 5.0, for AMD64 and EM64T (supports

Updates 1 and 2)

X X X

Red Hat Enterprise Linux ES and WS, version 5.0, for AMD64 and EM64T

(supports Updates 1 and 2)

X X


Table 6. Linux versions supported by IBM Systems Director on System x systems; IBM® and third-party x86-based

systems (continued)

Operating system

IBM

Systems

Director

Server

Common

Agent

Platform

Agent

Red Hat Enterprise Linux AS, ES, and WS, version 5.0, for AMD64 and EM64T,

with Xen Kernel (supports Updates 1 and 2)

X

SUSE Linux Enterprise Server 9 for AMD64 and EM64T (supports Service Packs 3

and 4)

X X X

SUSE Linux Enterprise Server 10 for AMD64 and EM64T (supports Service Packs

1 and 2)

X X X

SUSE Linux Enterprise Server 10, for AMD64 and EM64T, with Xen Kernel

(supports Service Packs 1 and 2)

X

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 Red Hat Enterprise Linux AS and ES, version 4.0

v Red Hat Enterprise Linux AS and ES, version 4.0, for AMD64 and EM64T


v Red Hat Enterprise Linux, versions 5.0 and 5.1, for AMD64 and EM64T

v Red Hat Enterprise Linux AS, ES, and WS, version 5.0, for AMD64 and EM64T,

with Xen Kernel

v SUSE Linux Enterprise Server 9 for x86

v SUSE Linux Enterprise Server 9 for AMD64 and EM64T


v SUSE Linux Enterprise Server 10 for AMD64 and EM64T

v SUSE Linux Enterprise Server 10, for AMD64 and EM64T, with Xen Kernel

v VMware ESX Server, versions 3.0, 3.0.1, 3.0.2, 3.5, 3.5.1, and 3.5.2, guest

operating systems


Virtualization software supported by IBM Systems Director

This topic lists the supported virtualization software for IBM Systems Director.

Hardware Management Console (HMC)

v Hardware Management Console Version 7.3.3 SP2, PTF MH01146

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

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)

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 V1.4.x



Note:

v VMware VirtualCenter must be installed on a physical system to operate in the

virtualization manager environment.

v If you use VMware VirtualCenter 1.4.1, ensure that you download and install the

latest patches from Download VMware VirtualCenter 1.x http://www.vmware.com/download/vc/ before you install Virtualization Manager.

Xen virtualization

v Red Hat Enterprise Linux 5.0, with Xen 3.0.3

v Red Hat Enterprise Linux 5.1, with Xen 3.1

v Red Hat Enterprise Linux 5.2, with Xen 3.1.2

v SUSE Linux Enterprise Server 10, with the Xen Virtual Machine Host Server

option installed (XEN 3.0)


http://www.vmware.com/download/vc/

http://www.vmware.com/download/vc/

v SUSE Linux Enterprise Server 10 SP1, with the Xen Virtual Machine Host Server

option installed (XEN 3.0.4)

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:

– UM32505

– UM32503

– UM32521

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


http://www.microsoft.com/windowsserversystem/virtualserver/default.aspx

http://www.vmware.com/support/pubs/esx_pubs.html

http://www.vmware.com/support/pubs/vc_pubs.html

http://www.vmware.com/support/pubs/vi_pubs.html

http://www.ibm.com/systems/z/os/zos/bkserv/zvmpdf/

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.

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 AIX Linux Windows

Apache Derby v V10.3 (included with IBM Systems

Director Server on AIX, Linux,

and Windows)

Embedded 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

Oracle® Database v Version 9.2

v Version 10g release 1

v Version 10g release 2

Local or remote Local or remote Local or remote


Related tasks

“Choosing the IBM Systems Director database application” on page 50

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.

v The level of IBM Systems Director support installed on the system or device. In

Table 8 on page 38, 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

Task

Operating systems

AIX IBM i Linux

Microsoft

Virtual

Server VMware Windows

Event Log IBM Systems

Director

Server, Level

2

Levels 1, 2 IBM Systems

Director

Server,

Levels 1, 2

Levels 1, 2 Levels 01, 1,

2

IBM Systems

Director

Server,

Levels 1, 2

File Transfer IBM Systems

Director

Server, Level

2

Level 2 IBM Systems

Director

Server, Level

2

Level 2 Level 22 IBM Systems

Director

Server, Level

2

Inventory (hardware)3 IBM Systems

Director

Server,

Levels 0, 24


Director

Server,

Levels 0, 1,

24

Levels 0, 1, 2 Levels 01, 1,

2

IBM Systems

Director

Server,

Levels 0, 1,

24

Inventory (software) IBM Systems

Director

Server,

Levels 0, 2

Levels 0, 1,

25

IBM Systems

Director

Server,

Levels 0, 1, 2

Levels 0, 1, 2 Levels 0, 1, 2 IBM Systems

Director

Server,

Levels 0, 1, 2

Problems (formerly

Hardware Status)6

Level 2 Level 2

7 Levels 1, 2

8,

7, 9

Levels 1, 2

10 Levels 1, 2

11 Levels 1, 2

Process Management IBM Systems

Director

Server, Level

2

Level 2 IBM Systems

Director

Server, Level

2

Level 2

12 Level 2

12 IBM Systems

Director

Server, Level

2

Remote Control IBM Systems

Director

Server,

Levels 0, 2

IBM Systems

Director

Server,

Levels 0, 1, 2

Level 2 Levels 0, 1,

213

IBM Systems

Director

Server,

Levels 0, 1, 2

Remote Command Line IBM Systems

Director

Server,

Levels 0, 2

Levels 0, 1, 2 IBM Systems

Director

Server,

Levels 014,

114, 2

Level 2 Levels 0, 1, 2 IBM Systems

Director

Server, Level

2

Resource Monitors IBM Systems

Director

Server, Level

2


Director

Server,

Levels 1, 2

Console only

15

Console only

15

IBM Systems

Director

Server,

Levels 1, 2

Storage Configuration

Manager

IBM Systems

Director

Server

IBM Systems

Director

Server,

Levels 1,

28, 16

Levels 1, 2 Levels 1, 2 IBM Systems

Director

Server,

Levels 1, 2

17

Update Manager IBM Systems

Director

Server,

Levels 218


Director

Server,

Levels 0, 1,

218

Levels 1, 2

20 Levels 1, 220 IBM Systems

Director

Server,

Levels 0, 1, 2

18

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 JS20 and JS21 only: Out-of-band notifications generated by a

service processor only.

8. Not supported on System z systems.

9. Platform Agent support only on Red Hat Enterprise Linux AS, version 5.0, for

IBM Power systems.

10. Limited support only.

11. VMware support for the Problems task has the following limitations:

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).12. Supported on guest operating systems only.

13. Supported on Windows guest operating systems only.

14. Supported for Linux on Power systems only.

15. Limited support provided by virtualization manager.

16. Not supported for Linux on Power systems.

17. The RSSM function is not supported on Windows Server 2008.

18. For detailed information about hardware and operating system support

provided by update manager, see “Supported updates.”

19. On IBM i 5.4 or later, update manager support is provided for IBM Director

Agent 5.20.

20. On guest operating systems, support is provided for Linux updates and IBM

Systems Director agent updates only.Related concepts

Supported updatesRelated reference

“IBM Systems Director task support not affected by operating systems”

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


http://publib.boulder.ibm.com/infocenter/systems/topic/updates_6.1/fqm0_c_um_update_types_and_applicable_resources.html

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

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 37

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.

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

Configuration Manager Yes No Not applicable

Event Automation Plans Yes Yes Yes

Problems Yes No Yes

1

Inventory Yes Yes Yes

Power On/Off No No Yes

Remote Command Line Not applicable Yes No

Remote Monitors No Yes No

SNMP Browser No Yes Yes

2

1. Inventory of the chassis, network device, and blade servers can be obtained through the management module.

Blade server inventory that is collected through the management module is a subset of the total inventory that is

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

Tasks and features 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


Table 10. IBM Systems Director task support for Storage products (continued)

Tasks and features DS300

DS400

DS4000

Brocade switches

DS6000

QLogic BladeCenter switches

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:

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.

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 on page 44.

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.


http://www.ibm.com/systems/management/director/subscription/

http://www.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5076601&brandind=5000016


http://www.ibm.com/systems/management/director/subscription/


Table 11. Hardware identification worksheet for IBM Systems Director

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

Unicast Addresses for Agentless managed

system discovery

IP addresses or IP-address ranges for unicast

discovery of Agentless managed systems.

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___


Table 12. Local and remote subnets worksheet (continued)


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.

Unicast Addresses for Common Agent

discovery

IP addresses or IP-address ranges for unicast

discovery of Common Agent managed

systems.

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

___.___.___.___ - ___.___.___.___

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 TCP/IP address and

time-to-live value for multicast discovery of

Common Agent managed systems.

multicast group: ___.___.___.___

time to live: _______

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.

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________

_________________________________


Table 12. Local and remote subnets worksheet (continued)


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.

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

Director Server

Compatible versions

of Common Agent

Compatible versions

of Platform Agent

IBM Systems Director

Server 6.1

N/A 6.1; IBM Director

Agent versions 5.20.3,

5.20.2, 5.20.1, 5.20,

6.1; IBM Director

Core Services

versions 5.20.3,

5.20.2, 5.20.1, 5.20,

Common Agent 6.1 6.1 and later N/A N/A

Platform Agent 6.1 6.1 and later N/A N/A


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 “What’s new in version 6.1.”

License information

Before deploying this product, ensure that you have the necessary licenses.


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.

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.


http://www.ibm.com/systems/management/director/buy/

http://www.ibm.com/systems/management/director/buy/

http://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 choose the features, encryption settings, network settings, and file locations

for your installation.

Complete the following steps to choose your installation options:

1. Determine the optional features that you want to install. You can choose from

the following features:

IBM Systems Director Remote Control Agent

Select this feature if you want to use the Remote Control task to

remotely control the management server.

IBM BladeCenter Management

Select this feature if your environment includes IBM BladeCenter units.2. 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.

3. 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 Password4. Determine whether you want to encrypt the data that is transmitted between

IBM Systems Director Server and Common Agent. If you want to encrypt the

data transmissions, you can select from the following encryption settings.

Advanced Encryption Setting (AES)

A block cipher algorithm, also known as Rijndael, used to encrypt data

transmitted between managed systems and the management server,

which employs a key of 128, 192, or 256 bits. AES was developed as a

replacement for DES.

Data Encryption Standard (DES)

A cryptographic algorithm designed to encrypt and decrypt data using

a private key.

Triple Data Encryption Standard

A block cipher algorithm that can be used to encrypt data transmitted

between managed systems and the management server. Triple DES is a

security enhancement of DES that employs three successive DES block

operations.


5. Determine where software-distribution packages are located. By default,

software-distribution packages are located in the following directories:

Table 15. Default locations in which software-distribution packages are installed

Operating System Location

Linux or AIX /opt/ibm/director/directory

Windows d:\Program Files\IBM\Director\directory

where directory is one of the following strings:

v SwDistPk

v SwPkInst

IBM Systems Director Server creates software-distribution packages in the

SwDistPk directory; when software packages are distributed to the instance of

Common Agent running on the management server, these packages are placed

in the SwPkInst directory.

6. Determine the network settings:

a. Will you enable all or only certain network interface cards (NICs)? If you

enable an individual NIC, IBM Systems Director Server will receive only

those data packets that are addressed to the individual adapter.

b. Determine the network timeout setting, which is the number of seconds that

IBM Systems Director Server waits for a response from Common Agent. By

default, the network timeout setting is 15 seconds.

c. Determine whether you want to enable Wake on LAN.7. (If IBM Systems Director Remote Control Agent is installed) Determine which

remote control options you want to enable:

v Require user authorization for system access

v Disable screen saver

v Disable background wallpaper

Choosing where to install IBM 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.

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

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 16. 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 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: The number of

managed objects is limited.

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.

v You can use an existing

DBMS and avoid

purchasing an additional

DBMS license.


DBMS is required.

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 17 to determine the database that best meets

your needs. For the following additional criteria, not all databases provide the

desired function.

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

Oracle® Database Yes Yes


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 18 and decide what level of management

is required.

Table 18. Management-level selection worksheet2

Criteria Agentless

Platform

Agent

Common

Agent

Managed system types

IBM® systems running AIX X X

IBM® systems running IBM i X X

1

IBM® systems running Linux X X

IBM® systems running Linux and supporting

either the SSH

3 or DCOM

4 protocol

X X X

IBM® systems running Windows X X

IBM® systems running Windows and supporting

either the SSH or DCOM protocol

X X X


Table 18. Management-level selection worksheet2 (continued)

Criteria Agentless

Platform

Agent

Common

Agent

Non-IBM systems running Linux and supporting

either the SSH or DCOM protocol

X X X

Non-IBM systems running Windows and

supporting either the SSH or DCOM protocol

X X X

Other managed resources, including management

processors supporting SSH, racks, and SNMP

devices

X

Managed system attributes

Managed system has a supported

workgroup/enterprise management agent

installed

X

Minimal additional memory constraint on

managed system

X

No additional memory constraint on managed

system

X

No Common Agent license required X X

No software required on managed system X

Needed functionality

Asset ID™ X

Event automation plans

5 X X X

Event log X X X

File Transfer X

Active Status X X

Service and Support Manager (Linux and

Windows)

X

virtualization manager (Linux & Windows) X

Remote control (Windows only)

6 X

Remote session to all supported managed

systems and devices

X

Remote session to SNMP devices and systems

supporting SSH

X X X

Restart the managed system X X X

Upgrade to Platform Agent X

Upgrade to Common Agent X X

Notes:

1. Platform-Agent managed system support is not provided by the Platform Agent

but by the 5722UME product.

2. In this table, ″systems″ include servers, desktop computers, workstations, and

mobile computers.

3. SSH = Secure Shell

4. DCOM = Distributed Component Object Model

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


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

– No agent or subagent software is needed.v Microsoft Virtual Server environment:

– Common Agent

– Virtualization manager subagentv VMware ESX Server environment:

– Common Agent

– Virtualization manager subagentv VMware ESXi managed by VMware VirtualCenter environment:

– No agent or subagent software is needed.v VMware VirtualCenter environment:

– Common Agent

– Virtualization manager subagentv Xen environment:

– Platform Agentv IBM® z/VM environment:

– Platform Agent or Common Agent

– IBM z/VM Manageability Access Point Agent

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 37

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 day’s worth of lost data is too much loss.

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

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.


http://publib.boulder.ibm.com/infocenter/systems/topic/main/fqo0_bk_events_ref.pdf

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

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

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.

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

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 user’s organizational role, the user probably needs

access to only a subset of the available privileges and tasks.

Other criteria can also be used when defining user roles for IBM 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

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

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


Option Description

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.

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.

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.


6. In the Organization field, type the name of your organization.

7. In the Country or region list, accept the default value.

8. In the Validity Period field, specify the lifetime of the certificate in days or

accept the default value.

9. Click OK.

10. To change the default keystore file password, click Key Database File →

Change Password.

11. In the Change Password window, specify and confirm a new password and

click OK.

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

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 User’s 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.

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


http://www.ibm.com/support/us

http://www.ibm.com/support/us





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.

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

15. In the Enter a Label window, specify a label for the certificate, for example,

DirServerSec.

16. Click OK.

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

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 64 in “Creating a self-signed certificate”

– Step 19 on page 67 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.

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 on page 69. 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. In the Security Alert window, click View Certificate.

3. In the Certificate window, click Install Certificate.

4. In the Certificate Import Wizard, on the Welcome page, click Next.

5. On the Certificate Store page, select the way that you want to store the

certificate and click Next.

6. On the Summary page, click Finish. A Security Warning window is displayed.

7. In the Security Warning window, click Yes.

8. In the Certificate Import Wizard window, click OK.

9. In the Certificate window, click OK.

10. 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 application’s digital signature has

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 19. Installation and configuration user IDs and passwords

Credential type Your values

Tasks that require the

credential

Procedure to change the password in IBM

Systems Director


administrator using the

local operating system

registry

User ID:

Password:

v Determining IBM

Systems Director

service account

information

v Installing IBM

Systems Director

Server

v Logging on to IBM

Systems Director

Server

Use the appropriate tools supplied by the local

operating system.


administrator using an

LDAP registry

User ID:

Password:

v Determining IBM

Systems Director

service account

information

v Installing IBM

Systems Director

Server

v Logging on to IBM

Systems Director

Server

Use the appropriate tools supplied by LDAP.

Database system

administrator

User ID:

Password:

v Preparing the

database for use with


Use the appropriate tools supplied by the

database application.

Database runtime

database connection

administrator

(DbmsUserId,

DbmsPassword)

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

manager

User ID:

Password:

v Starting IBM Systems

Director Server

(configAgtMgr.sh

script)

Use the cimsubscribe command.

LDAP administrator User ID:

Password:

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.


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 102Related tasks

“Logging on to IBM Systems Director Server for the first time” on page 95

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 85Related 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 system’s 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.


Related tasks

“Configuring the database application after IBM Systems Director installation” on

page 90

“Installing IBM Systems Director Server on Linux for System x and x86-based

systems” on page 86Related 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 process can be attached. EXTSHM must be exported both in the shell

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

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


http://www.ibm.com/systems/management/director/downloads.html

http://www.ibm.com/redbooks/community/display/director/IBM+Systems+Director+6.1+for+Power+Systems

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:

On Linux or AIX:

db2profile

Chapter 3. Installing IBM Systems Director on the management server 73

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. Next to the On-line maintenance window, click Change.

f. Specify a start time of 00:00 and duration of 24.

g. Click OK.

h. Click Next.

i. Click Next. The Select maintenance activity to configure page is displayed.

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

Table 20. Database configuration information and values

Description

Database configuration

attribute Value (select or input)

Selected database application 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.

__ v Apache Derby (Apache Derby)

__ v DB2 (IBM DB2 Universal Database)

__ v SQLServer (Microsoft SQL Server)

__ v Oracle (Oracle® Database)

Note: You must enter into the

cfgdbcmd.rsp response file the exact value

for each database as it appears above.


Table 20. Database configuration information and values (continued)

Description



Host name of the server on which the

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.

DbmsServerName 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

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.

DbmsDatabaseAppHome Custom value:

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.

DbmsTcpIpListenerPort Default or custom value:

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 Custom value:



Description



Password of the database user account (not


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

Related tasks


page 90Related reference




DB2 information center

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


http://publib.boulder.ibm.com/infocenter/db2help/index.jsp

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.

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

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.

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

Table 21. Database configuration information and values

Description



Selected database application 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.

__ v Apache Derby (Apache Derby)

__ v DB2 (IBM DB2 Universal Database)

__ v SQLServer (Microsoft SQL Server)

__ v Oracle (Oracle® Database)

Note: You must enter into the

cfgdbcmd.rsp response file the exact value

for each database as it appears above.



Description



Host name of the server on which the

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.

DbmsServerName 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

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.

DbmsDatabaseAppHome Custom value:

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.

DbmsTcpIpListenerPort Default or custom value:

User ID of the database user account (not


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 Custom value:



Description



Password of the database user account (not


DbmsPassword 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.Related tasks






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.

Related reference



Electronic Service Agent Web site

Preparing to install IBM Systems Director Server on Linux for

System x and x86-based systems

Before installing IBM Systems Director on a management server running Linux for

System x, make sure that your server meets all the applicable requirements.

Note: Because installing IBM Systems Director Server on Linux for System x also

installs Common Agent, the preparation steps for IBM Systems Director Server also

include preparation steps for Common Agent.

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 Ensure that the required RPMs are installed:

Table 22. Required RPMs for Linux for System x

Installation scenario Required RPM

Red Hat Enterprise Linux AS,

version 4.0

compat-libstdc++-296-2.96-132.7.2.i386.rpm

compat-libstdc++-33-3.2.3-47.3.i386.rpm

expect-5.42*.rpm

Red Hat Enterprise Linux AS,

version 5.0

libXp-1.0.0-8.i386.rpm

libXmu-1.0.2-5.i386.rpm

compat-libstdc++-33-3.2.3-61.i386.rpm

compat-libstdc++-296-2.96-138.i386.rpm

expect-5.42*.rpm

Upgrading from IBM Systems

Director, version 4.20 or later on

SUSE Linux Enterprise Server 9 for

x86

rpm-4.1.1-177.9.i586.rpm

expect-5.42*.rpm

v If you plan to run the Agent Installation Wizard from the server, ensure that

openssh is installed.

Note: The server installation does not enforce openssh installation.


http://www.ibm.com/support/electronic

http://www.ibm.com/support/electronic

http://www.ibm.com/support/electronic/

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 Ensure that the instance of Common Agent will be fully functional and able to

send alerts to IBM Systems Director Server. For the Common Agent to be fully

functional you might need to install service-processor device drivers or the IBM®

LM78 and SMBus device drivers for Linux.

v If you want to use the Remote Session task on the managed system, make sure

that the package that contains telnetd daemon is installed and configured. This

package is usually in the telnet_server_version.i386.RPM package, where version

is the code level of your Linux distribution.

v If you want to use IBM 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/.

v The IBM Systems Director on x86, V6.1.0 DVD does not include SUSE Linux

Enterprise Server 10 for x86 installation packages for IBM Systems Director

Server, Common Agent, or Platform Agent. You can download these installation

packages for System x platforms from the IBM Systems Director Web site at:

www.ibm.com/systems/management/director/.Related tasks



“Hardware and software requirements” on page 17


IBM Systems Director Web page

IBM® LM78 and SMBus device drivers for Linux

This topic describes when to install the LM78 and SMBus device drivers for Linux.

If you plan to install IBM Systems Director Server on a System x server running

Linux, you might need to install either or both the LM78 and SMBus device

drivers for Linux. These device drivers ensure that certain IBM Systems Director

tasks and functions work correctly. The following table contains information about

these device drivers, when they need to be installed, and what they do.





Table 23. Installing IBM Systems Director Server: IBM® LM78 and SMBus device drivers for

Linux

Device driver When it is needed What it does

LM78 If either of the following conditions applies:

v The server is one of the following

servers:

– IBM BladeCenter HS20, machine type

8832


8843


8839

– System x 225, machine type 8647



v The server contains an integrated systems

management processor (ISMP).

The LM78 device driver

ensures that IBM Systems

Director Server receives

memory and processor

Predictive Failure Analysis®

(PFA) alerts.

SMBus If the server does not contain one of the

following service processors:

v IPMI baseboard management controller

v Remote Supervisor Adapter

v Remote Supervisor Adapter II

The SMBus device driver

ensures that the

configuration manager and

status manager tasks

function correctly.

Uninstalling the IBM® LM78 or SMBus device driver

Before you install a new IBM® LM78 or SMBus device driver, you must uninstall

any previous versions of the drivers from the server.

Uninstalling the IBM® LM78 or SMBus device driver, version 4.21 or later:

This topic describes how to uninstall the IBM® LM78 or SMBus device driver,

version 4.21 or later.

Note: For instructions about how to uninstall the IBM® LM78 or SMBUS device

driver, version 4.20 or earlier, see “Uninstalling the IBM® LM78 driver, version 4.20

or earlier” and “Uninstalling the IBM® SMBus device driver, version 4.20 or

earlier” on page 83.

To uninstall the IBM® LM78 or SMBus device driver, version 4.21 or later, open a

command prompt, type the following command, and press Enter:

rpm -e driver

where driver is one of the following strings.

Device Driver Command

IBM® LM78 ibmlm78

IBM® SMBus ibmsmb

Issuing this command unloads the device driver and removes all driver-related

files from the server.

Uninstalling the IBM® LM78 driver, version 4.20 or earlier:


Before you install IBM® LM78 device driver, version 4.21 or later, you must first

uninstall the earlier version of the driver that is already installed.

Note: For instructions about how to uninstall the IBM® LM78 driver, version 4.21

or later, see “Uninstalling the IBM® LM78 or SMBus device driver, version 4.21 or

later” on page 82.

To uninstall the IBM® LM78 device driver, version 4.20 or earlier, complete the

following steps:

1. To uninstall the binary RPM file, from a command prompt, type the following

command and press Enter:

rpm -e ibmlm78

2. To uninstall the source RPM file, open a command prompt, type the following

command, and press Enter:rpm -e ibmlm78-src-distribution

where distribution is one of the following strings.

Type of distribution String

For servers running Red Hat Enterprise

Linux or VMware ESX Server

redhat

For servers running SUSE Linux suse



Uninstalling the IBM® SMBus device driver, version 4.20 or earlier:

Before you install IBM® SMBus device driver, version 4.21 or later, you must first

uninstall the earlier version of the driver that is already installed.

Note: For instructions about how to uninstall the SMBus device driver, version

4.21 or later, see “Uninstalling the IBM® LM78 or SMBus device driver, version 4.21

or later” on page 82.

To uninstall the IBM® SMBus device driver, version 4.20 or earlier, complete the

following steps:

1. To uninstall the binary RPM file, from a command prompt, type the following

command and press Enter:

rpm -e ibmsmb

2. To uninstall the source RPM file, open a command prompt, type the following

command, and press Enter:rpm -e ibmsmb-src-distribution

where distribution is one of the following strings.

Type of distribution String

For servers running Red Hat Enterprise

Linux or VMware ESX Server

redhat

For servers running SUSE Linux suse




Building the binary RPM file

If applicable, you can build the binary RPM files for the IBM® LM78 or SMBus

device drivers.

Ensure that the following conditions are met before building the binary RPM file:

v The system has Linux development and build capability.

v The Linux kernel source is installed and correctly configured.

v Any earlier versions of the LM78 or SMBus device drivers are uninstalled.

You must build the binary RPM file on a system with the same kernel version and

hardware configuration as the system on which you will install IBM Systems

Director Server. Make sure that the hardware configuration is similar in regard to

the number of processors and that any previous versions of the drivers have been

uninstalled.

Note: If you are building on Red Hat Enterprise Linux ES, version 4.0 and the

/usr/src/linux does not exist, complete the following steps:

1. From a command prompt, change to the /usr/src directory.

2. Type the following command and press Enter:

ln -s ./kernels/version/ ./linux

where version is the appropriate kernel subdirectory under /usr/src/kernels

(for example, 2.6.9-5.EL-smp-i686), which matches the kernel the system is

currently running.

To build either the LM78 or SMBus device driver, complete the following steps:

1. Download the source code for the IBM® LM78 and SMBus device drivers from

the IBM Systems Director Downloads Web Page: www.ibm.com/systems/management/director/downloads/.

2. Extract the source code archive (.tgz file) from the driver package to a

temporary directory. Follow the instructions in the readme file to configure the

kernels sources before building the driver source RPM.

3. Copy the source file (ibmlm78-5.20-3.tgz for the LM78 driver or

ibmsmb-5.20-3.tgz for the SMBus driver) to the SOURCES directory.

4. From a command prompt, change to the SOURCES directory.

5. Type one of the following commands and press Enter:


LM78 rpmbuild -tb ibmlm78-5.20-3.tgz

SMBus rpmbuild -tb ibmsmb-5.20-3.tgz

Running this command creates a binary RPM file in the RPMS/architecture

directory, where architecture is one of the following strings:

v i586 (SUSE Linux Enterprise Server 9 for x86)

v i386 (all other 32-bit operating systems)

v x86_64 (64-bit operating systems)




Related reference


Installing the IBM® LM78 or SMBus device driver

After building the binary RPM file for the kernel version of the Linux operating

system on your server, you can install the IBM® LM78 or SMBus drivers.

You can install the binary RPM file either on the server on which it was built or on

another server that has the same Linux kernel and hardware configuration.

Complete the following steps to install either the IBM® LM78 or SMBus device

driver:

1. If you built the binary RPM file on another server, complete the following

steps:

a. Make sure that any earlier versions of the device drivers have been

uninstalled from the server where you will install version 5.20 of the device

driver and IBM Systems Director.

b. Copy the binary RPM file to an RPMS/architecture directory, where

architecture is either i386 (for a 32-bit operating system) or X86_64 (for a

64-bit operating system).

Note: In this procedure, driver is one of the following strings:


IBM® LM78 ibmlm78

IBM® SMBus ibmsmb

2. Change to the RPMS/architecture directory.

3. From a command prompt, type the following command and press Enter:

rpm -ivh driver-5.20-3.architecture.rpm

where architecture is one of the following values:

v i386 (32-bit operating systems)

v X86_64 (64-bit operating systems)

Issuing this command performs the following tasks:

v Decompresses and untars the archive into the /usr/local/driver directory

v Copies the device driver, shared library, and all the configuration files to the

appropriate locations

v Loads and starts the device driver

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




Installing IBM Systems Director Server on Linux for System x

and x86-based systems

When you install IBM Systems Director Server, Common Agent is installed

automatically. During the installation process, you can install several Common

Agent features. You also can configure a database to use with IBM Systems

Director and change security settings.

Important:

v Installation of IBM Systems Director installs IBM Systems Director Server,

Common Agent (when applicable), and Platform Agent all together. Therefore, it

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

v IBM Systems Director Server is not supported to run on a system with workload

partitions (WPARs) enabled.

You can install IBM Systems Director Server on Linux for System x from either

installation media or from a downloaded installation package.

Important: The IBM Systems Director Server, Common Agent, and Platform Agent

installation packages for Linux are provided in English only.

Table 24. Installation options for IBM Systems Director Server on Linux for System x

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 /opt/ibm/director/packaging/agent on the server.

Downloaded installation package SysDir6_1_Server_Linux_x86.tar.gz

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,

complete the following steps:

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. To extract the contents of the installation package, type the following

command:

tar -xvf install_package

where install_package is the file name of the downloaded installation

package.

c. Change to the directory in which the installation script is located. Type the

following command and press Enter:

cd /install_files/

where install_files is the path to the extracted installation files.DVD media: To start the installation from the DVD, complete the following

steps:

a. Insert the DVD into the DVD-ROM drive.

b. If the DVD does not automount, mount the DVD-ROM drive. Type the


mount /dev /mnt

where dev is the specific device file for the block device and mnt is the

mount point of the drive.

c. Change to the directory in which the installation script is located. Type the


cd /mnt/server/linux/i386/

where mnt is the mount point of the drive.2. Optional: To customize the installation, for example to select a nondefault

database, copy the response file (dirserver.rsp) to a local directory and modify

the installation settings in your local copy.

a. Type the following command and press Enter:

cp dirserv.rsp /directory/

where directory is a local directory.

b. Open an ASCII text editor and modify the installation settings in the copy

of the dirserver.rsp file. This file is fully commented.

You can specify the following items in the server response file:

v Specify the log file options




v Specify the Web console port numbers

v Specify the TPM hostname and IP address

v Enable or disable the nonstop service, which keeps the server

continuously running

Note: In the response file, “1” indicates that an item is to be installed and

“0” indicates that an item is not to be installed.

c. Save the modified response file with a new name.

Note: For more information about the dirserver.rsp file, see the IBM Systems

Director Best Practices Redwiki.

Tip: After installation, keep the response file for future use and reference.

3. To install IBM Systems Director Server, type one of the following commands

and press Enter:

v To accept the default settings:

server/dirinstall.server

v To use the response file:

server/dirinstall.server -r /directory/response.rsp

where directory is the local directory to which you copied the response file,

and response.rsp is the name of the response file.

4. Optional: Configure IBM Systems Director for use with a database application

other than that which is supplied by default. For more information, see

“Configuring the database application after IBM Systems Director installation”.

Important: You can configure IBM Systems Director for use with your database

application at any point after the installation of IBM Systems Director Server,

but you must not start the management server until it is completed. Starting

the management server before configuring IBM Systems Director to use a

database application might result in a loss of function.

5. Complete the following steps to start IBM Systems Director Server:

a. Type the following command and press Enter:

/opt/ibm/director/bin/configAgtMgr.sh

b. Use the following information to respond to the configAgtMgr.sh script

prompts:

Enter the Resource Manager user ID that you would like to set for your

Agent Manager

If you want to register with an existing agent manager, enter the

same resource manager user ID as that of the agent manager. If you

want to create a new agent manager, enter in any user ID that will

then be defined as the resource manager user ID for that new agent

manager.

Note: The resource manager user ID is an identifier that is used by

IBM Systems Director or other resource managers to communicate

with the agent manager; it is not a user ID on the operating system

or an LDAP server.

Enter the Resource Manager password to set for your Agent Manager


same resource manager password as that of the agent manager. If


you want to create a new agent manager, enter in any password

that will then be defined as the resource manager password for that

new agent manager.

Verify the Resource Manager password to set for your Agent Manager

Reenter the password you entered for Enter the Resource Manager

password to set for your Agent Manager.

Enter the Agent Registration password to set for your Agent Manager


same agent registration password as that of the agent manager. If

you want to create a new agent manager, enter in any password

that will then be defined as the agent registration password for that

new agent manager.

Verify the Agent Registration password to set for your Agent Manager

Reenter the password you entered for Enter the Agent Registration

password to set for your Agent Manager.

Would you like to use an existing Agent Manager (yes or no)?

If you answer yes, ensure that the user ID and passwords that you

previously entered match the user ID and passwords of the existing

agent manager.

If you answer no, you are done and the configuration will start.

Enter the IP address for the existing Agent Manager

If you answered yes to Would you like to use an existing Agent

Manager (yes or no)?, you must provide the IP address of the

existing agent manager.

Enter the port number for the existing Agent Manager

If you answered yes to Would you like to use an existing Agent

Manager (yes or no)?, you must provide the port number of the

existing agent manager. The port number must be a valid number

between 0 and 65535.

After you have provided all the requested information, the agent manager

configuration script runs and displays a series of status messages.

c. Start IBM Systems Director processes on the management servers by

running the smstart command:

/opt/ibm/director/bin/smstart

See the “smstart command” topic for instructions.

d. Type the following command and press Enter:

install_root/bin/smstatus -r

When this command returns a value of Active, the server is started.6. If you used the DVD for installation, complete the following steps to unmount

the drive and remove the DVD:

a. Type cd / and press Enter.

b. Type the following command and press Enter:

umount /mnt

where mnt is the mount point of the drive.

c. Remove the DVD from the drive.


To enable SNMP Access and Trap Forwarding, install and configure Net-SNMP,

version 5.2.1, see .

Related tasks

“Preparing the database application” on page 71

“Configuring the database application after IBM Systems Director installation”

“Preparing to install IBM Systems Director Server on Linux for System x and

x86-based systems” on page 80

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.

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 database application” on page 71

“Preparing the IBM DB2 Universal Database” on page 72

“Preparing the Oracle® Database” on page 76


systems” on page 86

“Installing IBM Systems Director on the management server” on page 85Related reference




DB2 information center

Microsoft SQL Server 2005 JDBC Driver 1.2 JDBC driver

How to configure SQL Server 2005 to allow remote connections

Authentication Mode (SQL Server Express)


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.

v Set up additional user security

v Start configuring your systems


http://publib.boulder.ibm.com/infocenter/db2help/index.jsp

http://www.microsoft.com/downloads/details.aspx?FamilyId=C47053EB-3B64-4794-950D-81E1EC91C1BA&displaylang=en

http://support.microsoft.com/kb/914277

http://msdn2.microsoft.com/en-us/library/ms143705.aspx



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

v Status Manager

v Automation Manager

v Configuration Manager

v 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

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

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:


https://www.microsoft.com/downloads

https://www.microsoft.com/downloads

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.

For additional information, see http://technet2.microsoft.com/windowsserver/en/library/910d7a79-fd6f-447e-9bb1-bc9e57d54ec41033.mspx?mfr=true


http://technet2.microsoft.com/windowsserver/en/library/910d7a79-fd6f-447e-9bb1-bc9e57d54ec41033.mspx?mfr=true

http://technet2.microsoft.com/windowsserver/en/library/910d7a79-fd6f-447e-9bb1-bc9e57d54ec41033.mspx?mfr=true

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.


Related concepts

“System discovery” on page 102Related tasks

Chapter 3, “Installing IBM Systems Director on the management server,” on page

71


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


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


https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?lang=en_US&source=aixpegcim


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

– Powering off that blade server

Figure 2. Example of IBM BladeCenter deployment network when IBM Systems Director

Server is not installed on a blade server


– Changing the boot options on that blade serverv 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 98 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 100 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/.

Chapter 4. Preparing agentless managed systems 99


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 VMware managed systems

You might need to configure certain VMware systems before you can install agents

on them using the Agent Installation Wizard.

Managed systems running VMware ESX require the following configuration to

ensure that agents can be installed using the Agent Installation Wizard:

1. On the VMware managed system, open the /etc/ssh/sshd_config file in a text

editor.

2. Locate the following line:

Ciphers aes256-cbc,aes128-cbc

3. Change the line to:

Ciphers aes256-cbc,aes128-cbc,3des-cbc

4. Save and close the /etc/ssh/sshd_config file.

5. Stop and restart the ssh daemon. Type the following command:

service sshd restart

Figure 3. Example of IBM BladeCenter deployment network when IBM Systems Director

Server is installed on a blade server



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


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.


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

Chapter 5. Discovering systems and collecting inventory data 103

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.


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.

Chapter 5. Discovering systems and collecting inventory data 105

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 Linux for System x and

x86-based systems

Before installing Platform Agent on a managed system running Linux for

System x, 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.”






Table 26. Required RPMs


Red Hat Enterprise Linux, version

4.0



http://rhn.redhat.com/errata/RHBA-2005-116.html

Table 26. Required RPMs (continued)



5.0






x86

rpm-4.1.1-177.9.i586.rpm













site at www.ibm.com/systems/management/director/.Related tasks

“Installing agents using the Agent Installation Wizard” on page 111Related reference










editor.












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 Linux for System x

and x86-based systems

Before installing Common Agent on a managed system running Linux for

System x, 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.”






Table 27. Required RPMs



4.0



5.0






x86

rpm-4.1.1-177.9.i586.rpm

Chapter 6. Installing agents 109



v Ensure that SELinux is not set to enforce security policies prior to installing IBM

Systems Director.

If your server runs Red Hat Enterprise Linux version 4 or 5, SELinux might be

enabled and enforcing security policies on your system. IBM Systems Director

Common Agent might have trouble if SELINUX is set to enforcing. Therefore,

before you install IBM Systems Director Common Agent, you must set the

SELinux policy to permissive.

SELinux runs in any of the following states:

Disabled

SELinux is disabled. You can tell that SELinux is in the disabled state by

determining if any of the following conditions are true:

– No files exist in the /selinux/ directory.

– The SELINUX variable in /etc/selinux/config is set to disabled.

Permissive (enabled)

SELinux is enabled but not enforcing any security policies. You can tell

that SELinux is in the permissive state by determining if any of the

following conditions are true:

– The SELINUX variable in /etc/selinux/config is set to permissive.

– When you run the cat /selinux/enforce; echo command, it outputs a

0.

Note: The echo after the cat command is required so you can read

what is printed out by /selinux/enforce.

Enforcing (enabled)

SELinux is enabled and enforcing security policies. You can tell that

SELinux is in the enforcing state by determining if any of the following

conditions are true:

– The SELINUX variable in /etc/selinux/config is set to enforcing.

– When you run the cat /selinux/enforce; echo command, it outputs a

1.

Note: The echo after the cat command is required so you can read

what is printed out by /selinux/enforce.To set SELinux to permissive, run the following command before you install

IBM Systems Director Common Agent:

/usr/sbin/setenforce Permissive













site at www.ibm.com/systems/management/director/.



Related tasks

“Installing agents using the Agent Installation Wizard”Related reference










editor.








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 is installed with a number of agent packages that can

be deployed to managed systems using 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 be run now or scheduled.

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.




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.c. Click Next.

4. In the Agent Installation Wizard Systems page, complete the following steps:

a. Select the managed systems on which you want to install the agent package

in the Available list.

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

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

server’s time or the target system’s 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

Redwiki at http://www.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 Linux for System x and x86-based

systems” on page 109

“Preparing to install Platform Agent on Linux for System x and x86-based



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

See the “Supported operating systems” topic for specific versions of these

operating systems that are supported.

Notes:


http://sourceforge.net/projects/openipmi/


http://www-912.ibm.com/s_dir/slkbase.NSF/7de7b52481a6bad786256d09006d9b28/08de762e62794c89862571fe007b1b91

http://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/home.html

http://sourceforge.net/projects/linux-diag/?abmode=1

http://sourceforge.net/projects/sshwindows/

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.04-1.rhel3.i386.rpm


4.0



5.0


5.20.3 or higher SUSE Linux Enterprise Server 9 for

x86

lsi_mr_hhr-00.02.G5.04-1.sles9.i586.rpm

5.20.3 or higher SUSE Linux Enterprise Server 10

for x86

lsi_mr_hhr-00.02.G5.04-1.sles10.i386.rpm

5.20.3 or higher Microsoft Windows LSI_MR_HHR-WS32-00.02.G5.04.exe

5.20.2 Red Hat Enterprise Linux, version

4.0

lsi_mr_hhr-90.00.05.38-1.rhel4.i386.rpm

5.20.2 Red Hat Enterprise Linux, version

5.0

lsi_mr_hhr-90.00.05.38-1.rhel5.i386.rpm

5.20.2 SUSE Linux Enterprise Server 9 for

x86

lsi_mr_hhr-90.00.05.38-1.sles9.i586.rpm

5.20.2 SUSE Linux Enterprise Server 10

for x86

lsi_mr_hhr-90.00.05.38-1.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.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\binc. Shut down and restart Windows.

Related reference




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:

Virtualization manager subagent 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 1.4.x CommonAgentSubagent_VSM_VC14x-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.

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/binb. 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/"

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.


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 user’s responsibility to evaluate and verify the

operation of any non-IBM product, program, or service.

IBM® may have patents or pending patent applications covering subject matter

described in this document. The furnishing of this document does not grant you

any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785

U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM®

Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing 2-31 Roppongi 3-chome, Minato-ku

Tokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other

country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER

EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS

FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or

implied warranties in certain transactions, therefore, this statement may not apply

to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be

incorporated in new editions of the publication. IBM® may make improvements

and/or changes in the product(s) and/or the program(s) described in this

publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for

convenience only and do not in any manner serve as an endorsement of those Web

sites. The materials at those Web sites are not part of the materials for this IBM®

product and use of those Web sites is at your own risk.

IBM® may use or distribute any of the information you supply in any way it

believes appropriate without incurring any obligation to you.


Licensees of this program who wish to have information about it for the purpose

of enabling: (i) the exchange of information between independently created

programs and other programs (including this one) and (ii) the mutual use of the

information which has been exchanged, should contact:

IBM Corporation

MW9A/050

5600 Cottle Road

San Jose, CA 95193

U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

The licensed program described in this 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 IBM’s 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


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 121

http://www.ibm.com/legal/copytrade.shtml

Readers’ Comments — We’d Like to Hear from You

IBM Systems

IBM Systems Director for Linux on x86

Planning, Installation, and Configuration Guide

Version 6.1

Publication No. GI11-8712-00

We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,

organization, subject matter, or completeness of this book. The comments you send should pertain to only the

information in this manual or product and the way in which the information is presented.

For technical questions and information about products and prices, please contact your IBM branch office, your

IBM business partner, or your authorized remarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any

way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use

the personal information that you supply to contact you about the issues that you state on this form.

Comments:

Thank you for your support.

Send your comments to the address on the reverse side of this form.

If you would like a response from IBM, please fill in the following information:

Name

Address

Company or Organization

Phone No. E-mail address

Readers’ Comments — We’d Like to Hear from You GI11-8712-00

GI11-8712-00

��

Cut or FoldAlong Line

Cut or FoldAlong Line

Fold and Tape Please do not staple Fold and Tape

Fold and Tape Please do not staple Fold and Tape

NO POSTAGENECESSARYIF MAILED IN THEUNITED 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

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

_

��

Printed in USA

GI11-8712-00

dir6.1_install_gde_xlinux

Documents

program filesibmsqllib

program filesibmdirectoragentruntimeagent

appnamestgepopousenamp

infotypesaamp

subtypewh

4gbitsec fibre

htmlfidpow03011usen

remote supervisor