IBM Systems Director

IBM Systems Director for AIXPlanning, Installation, and Configuration GuideVersion 6.2.1

GI11-8709-06

���

IBM Systems Director

IBM Systems Director for AIXPlanning, Installation, and Configuration GuideVersion 6.2.1

GI11-8709-06

���

NoteBefore using this information and the product it supports, read the information in “Notices” onpage 173.

© Copyright IBM Corporation 1999, 2010.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this publication . . . . . . . . vConventions and terminology . . . . . . . . vPublications and related information . . . . . . vWeb resources . . . . . . . . . . . . . viiiHow to send your comments . . . . . . . . . x

Checklist: Installing IBM SystemsDirector Server on AIX . . . . . . . . xi

Checklist: Installing agents on AIX . . xiii

Chapter 1. IBM Systems Directortechnical overview . . . . . . . . . . 1IBM Systems Director components . . . . . . . 2

Management server . . . . . . . . . . . 3Common Agent . . . . . . . . . . . . 4Platform Agent . . . . . . . . . . . . 5Agentless managed systems . . . . . . . . 5

Manageable resource types . . . . . . . . . 6Manageable systems and system types. . . . . . 6User interfaces. . . . . . . . . . . . . . 8Base function and extensible plug-ins . . . . . . 8

Discovery manager . . . . . . . . . . . 9Status manager . . . . . . . . . . . . 9Configuration manager . . . . . . . . . 10Automation manager . . . . . . . . . . 10Update manager. . . . . . . . . . . . 10Remote access manager . . . . . . . . . 11Virtualization manager . . . . . . . . . 11Network Management . . . . . . . . . . 12IBM BladeCenter and System x management . . 12IBM System z management . . . . . . . . 12IBM Power Systems management . . . . . . 12IBM System Storage management . . . . . . 13Additional IBM Systems Director plug-ins . . . 13

Upward integration. . . . . . . . . . . . 16

Chapter 2. Planning for IBM SystemsDirector . . . . . . . . . . . . . . 17Hardware and software requirements. . . . . . 17

Hardware requirements for IBM Systems Director 17Supported IBM systems and products . . . . 21IBM BladeCenter products . . . . . . . . 21Supported network devices . . . . . . . . 22Supported storage devices . . . . . . . . 28Network requirements. . . . . . . . . . 38Security requirements . . . . . . . . . . 46Firmware and device drivers requirements . . . 47Operating system and software requirements . . 47IBM Systems Director task support by operatingsystem and agent levels . . . . . . . . . 56IBM Systems Director task support not affectedby operating systems . . . . . . . . . . 60

IBM Systems Director task support forBladeCenter products . . . . . . . . . . 60IBM Systems Director task support for Storageproducts . . . . . . . . . . . . . . 61Supported tasks and features for third-partyx86-based systems . . . . . . . . . . . 61Translations provided by IBM Systems Director 62IBM Systems Director Pre-Installation Utility . . 63

IPv6 compliance . . . . . . . . . . . . . 64Applicability of Platform Agent. . . . . . . . 67Determining IBM Systems Director task support . . 69

Questions to answer about IBM hardware . . . 69Questions to answer about third-party hardware 70

Planning to install IBM Systems Director . . . . 71Service and support information . . . . . . 71Reviewing the environment . . . . . . . . 72Version compatibility of IBM Systems Directorcomponents across releases . . . . . . . . 75License information. . . . . . . . . . . 77Obtaining licenses for Common Agent . . . . 79Choosing how to install IBM Systems Director. . 79Choosing the IBM Systems Director Serverinstallation options . . . . . . . . . . . 81Choosing where to install IBM Systems DirectorServer . . . . . . . . . . . . . . . 81Choosing the IBM Systems Director databaseapplication . . . . . . . . . . . . . 82Choosing the management level for managedsystems. . . . . . . . . . . . . . . 84Planning for virtual environments . . . . . . 85

Planning to upgrade or update IBM SystemsDirector . . . . . . . . . . . . . . . 86Disaster recovery for IBM Systems Director 6.2.x . . 89Planning for events . . . . . . . . . . . . 90

Planning events to be monitored . . . . . . 90Planning for event automation planimplementations. . . . . . . . . . . . 91

Planning IBM Systems Director security . . . . . 94Planning IBM Systems Director users and groups 94Planning Secure Sockets Layer configuration onIBM Systems Director . . . . . . . . . . 95Planning password management in IBMSystems Director . . . . . . . . . . . 104

Chapter 3. Installing IBM SystemsDirector on the management server. . 107Preparing the management server . . . . . . 107

Preparing the database application . . . . . 107Preparing firewalls and proxies for IBM SystemsDirector . . . . . . . . . . . . . . 117Preparing to install IBM Systems Director Serveron AIX . . . . . . . . . . . . . . 118

Installing IBM Systems Director on themanagement server . . . . . . . . . . . 121

Installing IBM Systems Director Server on AIX 121

© Copyright IBM Corp. 1999, 2010 iii

Configuring the database connection after IBMSystems Director installation . . . . . . . . 126Configuring IBM Systems Director Server afterinstallation . . . . . . . . . . . . . . 127

Configuring IBM Systems Director plug-ins andplatforms . . . . . . . . . . . . . . 128Configuring the command line interface . . . 129Reviewing Microsoft Internet Explorer securityoptions . . . . . . . . . . . . . . 130Configuring IP address properties . . . . . 131

Logging on to IBM Systems Director Server for thefirst time . . . . . . . . . . . . . . . 132Restarting IBM Systems Director Server . . . . 133Enabling Dynamic IP support . . . . . . . . 134

Chapter 4. Preparing agentlessmanaged systems . . . . . . . . . 137Configuring access to agentless managed systems 137

Sample sudo configuration file . . . . . . 138Preparing AIX managed systems . . . . . . . 139Preparing to manage a IBM BladeCenter . . . . 139

Preparing to manage a IBM BladeCenter chassisusing IBM Systems Director Server on anon-blade server . . . . . . . . . . . 139Preparing to manage a IBM BladeCenter chassisusing IBM Systems Director Server on a bladeserver . . . . . . . . . . . . . . . 140

Preparing Hardware Management Console devicesfor discovery with IBM Systems Director . . . . 142

Chapter 5. Discovering systems andcollecting inventory data . . . . . . 145Discovery protocols . . . . . . . . . . . 145Discovering systems with system discovery . . . 146

System discovery . . . . . . . . . . . 146Performing a system discovery . . . . . . 147

Using system discovery to view current results 149Accessing a secured system with request access 150

Chapter 6. Installing agents . . . . . 153Preparing a Common Agent managed system . . 153

Obtaining licenses for Common Agent . . . . 153Preparing to install Common Agent on AIX . . 153

Installing agents using the Agent InstallationWizard . . . . . . . . . . . . . . . 155

Chapter 7. Updating IBM SystemsDirector . . . . . . . . . . . . . . 159

Chapter 8. Upgrading and migratingIBM Systems Director . . . . . . . . 161Database preparation considerations for upgradingand migrating to IBM Systems Director 6.2.x . . . 161Upgrading and migrating to IBM Systems Director6.2.1 from 6.1.x . . . . . . . . . . . . . 163Upgrading and migrating to IBM Systems Director6.2.1 from 6.2 . . . . . . . . . . . . . 164Upgrading and migrating to IBM Systems Directorfrom IBM Director 5.x . . . . . . . . . . 164Upgrading and migrating IBM Systems Directorplug-ins . . . . . . . . . . . . . . . 165Upgrading and migrating IBM Systems Director onthe management server . . . . . . . . . . 165

Upgrading and migrating IBM Systems DirectorServer on AIX . . . . . . . . . . . . 166

Upgrading or updating the IBM Systems Directoragents . . . . . . . . . . . . . . . . 170

Notices . . . . . . . . . . . . . . 173Trademarks . . . . . . . . . . . . . . 174

iv IBM Systems Director for AIX Planning, Installation, and Configuration Guide

About this publication

This IBM® Systems Director for AIX® Planning, Installation, and Configuration Guideprovides information about installing and configuring IBM Systems Director. Inaddition to presenting an overview of IBM Systems Director and its requirements,it covers the following topics:v Planning an IBM Systems Director environmentv Installing IBM Systems Directorv Upgrading from IBM Director 5.20 to IBM Systems Director 6.xv Configuring IBM Systems Director

It also includes information about IBM Systems Director security and solvingproblems you might encounter during installation.

Note: Oftentimes, this publication describes a single procedure for accomplishing atask. For documentation about alternative procedures, see the IBM SystemsDirector information center Web site at http://publib.boulder.ibm.com/infocenter/director/v6r2x/index.jsp.

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 avoidinconvenient 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 damagecan occur.

Publications and related informationYou can view the same content in the IBM Systems Director Information Center asPDF documents. To view a PDF file, you need Adobe Acrobat Reader, which canbe downloaded for free from the Adobe Web site at http://get.adobe.com/reader/.

Information centers and topic collectionsv IBM Systems

http://publib.boulder.ibm.com/eserver/View the IBM Systems information center landing page, which providesintegrated information for multiple IBM Systems products.

v IBM Systems Directorhttp://publib.boulder.ibm.com/infocenter/director/v6r2x/index.jspUpdated periodically, the IBM Systems Director topic collection contains themost up-to-date documentation available for IBM Systems Director.

v IBM Systems Director plug-inspublib.boulder.ibm.com/infocenter/systems/index.jsp

© Copyright IBM Corp. 1999, 2010 v

View the IBM Systems information center for information about how to installand use plug-ins that extend the functionality of IBM Systems Director.

v IBM Systems Director Upward Integration Modules (UIMs)publib.boulder.ibm.com/infocenter/systems/topic/uims/fqs0_main.htmlRead the IBM Systems Director Upward Integration Modules (UIM) topiccollection to learn about how to install and use upward integration modules andmanagement packs that enable non-IBM workgroup and enterprise-managementproducts to interpret and display data that is provided by Common Agent andPlatform Agent.

v IBM Systems Director API Licensinghttp://www.ibm.com/vrm/4api1View the license information regarding use of IBM Systems Director APIs andtheir associated documentation. Fill out the form to request API access. Afteryour information is reviewed, you will be contacted with additional informationregarding access to and use of the APIs.

Publications

APAR Readme 6.2.0Provides information about APARs fixed in IBM Systems Director version6.2.0.

Release Notes® 6.2.0 and Release Notes 6.2.1Provides information about hardware requirements for running IBMSystems Director components, supported IBM Systems Director hardware,operating systems, databases, and workgroup and enterprisesystems-management software.

Hardware and Software Support GuideProvides information about hardware requirements for running IBMSystems Director components, supported IBM Systems Director hardware,operating systems, databases, and workgroup and enterprisesystems-management software.

Planning, Installation, and Configuration Guide for AIXProvides detailed instructions to install and configure each component ofIBM Systems Director on system running AIX using the standardinstallation option.

Planning, Installation, and Configuration Guide for IBM iProvides detailed instructions to install and configure each component ofIBM Systems Director on system running IBM i using the Standardinstallation option.

Planning, Installation, and Configuration Guide for Linux on Power Systems™

Provides detailed instructions to install and configure each component ofIBM Systems Director on system running Linux for Power Systems usingthe Standard installation option.

Planning, Installation, and Configuration Guide for Linux on x86Provides detailed instructions to install and configure each component ofIBM Systems Director on system running Linux for System x® using theStandard installation option.

Planning, Installation, and Configuration Guide for Linux on System z®

Provides detailed instructions to install and configure each component ofIBM Systems Director on system running Linux for System z using theStandard installation option.

vi IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Planning, Installation, and Configuration Guide for WindowsProvides detailed instructions to install and configure each component ofIBM Systems Director on system running Windows using the Standardinstallation option.

Systems Management GuideProvides detailed instructions for using the Web interface and managingsystems and resources in your environment.

Troubleshooting GuideProvides information about problems and how to solve them, andstrategies for troubleshooting common problems.

Events ReferenceProvides information about IBM Systems Director events, including theevent type, description, severity, and extended details.

Commands ReferenceProvides detailed information about the systems managementcommand-line interface (smcli) commands, and other commands that canbe run directly from the command line, including configuring the database,and starting and stopping IBM Systems Director.

Hardware Command Line User's GuideProvides information about installing and using the Hardware CommandLine (formerly known as the IBM Management Processor Command-LineInterface). Command output in this release might vary from commandoutput in previous releases.

White papers and briefsv IBM Systems Director

ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03006usen/XBW03006USEN.PDFThis paper provides a detailed overview of the changes in IBM Systems DirectorV6.1, including the new Web interface, security features, operating systemagents, integrated plug-ins and additional plug-ins that can be separatelyinstalled.

v Value Proposition for IBM Systems Director

ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03007usen/XBW03007USEN.PDFThis paper describes the challenges of operational management for enterpriseserver 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.PDFProvides information about managing the virtualization and consolidation onPower 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.PDFProvides information about migrating data when upgrading your environmentfrom IBM Director V5.20 to IBM Systems Director V6.1.

v Performance Tuning and Scaling Guide for IBM Systems Director 6.2

About this publication vii

http://www-01.ibm.com/support/docview.wss?uid=nas7cd6a96f49d05f608862577420075ca9a&aid=1Provides information about how to plan, implement, configure, and use an IBMSystems Director Server to manage a large configuration with optimalperformance. The Performance Tuning and Scaling Guide also containsinformation about the following topics:– Running IBM Systems Director plug-ins, such as IBM Systems Director Active

Energy Manager® and IBM Scalable Systems Manager– Integration with Tivoli® products– Implementing High Availability (HA)

IBM Redbooks® publications

www.ibm.com/redbooks/

You can also search this Web page for documents that focus on IBM SystemsDirector and specific IBM hardware; such documents often containsystems-management material. The following book is available for IBM SystemsDirector V6.1:

Implementing IBM Systems Director 6.1

Tip: Be sure to note the date of publication and to determine the version of IBMSystems Director software to which the Redbooks publication refers.

Further information

Also see the following resources for further information about IBM SystemsDirector:v For alerts, discussions, news, parts and product information, and specific

troubleshooting workarounds for IBM Systems Director, see the Support &downloads Web site at http://www.ibm.com/support/us/en/.

Tip: To locate the information that you need, enter Systems Director in theSearch field and click Search. You can then narrow your results by documenttype or product category, or use additional search terms.

v For white papers, technotes, tips, and other documents related to IBM SystemsDirector, see the Techdocs Web site at http://w3.ibm.com/support/techdocs/atsmastr.nsf/Web/Techdocs.

Tip: To locate the information that you need, either select the categories that youwant to search or select UNMARKED to search all categories. Then enterSystems Director in the for: field and click Search.

v For solutions to all types of situations that other customers have encountered,see the IBM Systems Director customer forum at www.ibm.com/developerworks/forums/forum.jspa?forumID=759.

Web resourcesListed here are the Web sites and information center topics that relate to IBMSystems Director.

viii IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Web sitesv IBM Systems Director

www.ibm.com/systems/management/director/View the IBM Systems Director Web site on ibm.com® which provides links todownloads and documentation for all currently supported versions of IBMSystems Director.

v IBM Systems Director Downloadswww.ibm.com/systems/management/director/downloads/View the IBM Systems Director Downloads Web site on ibm.com which provideslinks to download code IBM Systems Director, IBM Systems Director plug-ins,and IBM Systems Director upward integration modules.

v IBM Systems Director Documentation and Resourceswww.ibm.com/systems/management/director/resources/View the IBM Systems Director Documentation and Resources Web site onibm.com which provides links to product documentation, redbooks, redpapers,white papers, and learning modules related to IBM Systems Director, IBMSystems Director plug-ins, and IBM Systems Director upward integrationmodules.

v IBM Systems Director Upward Integrationwww.ibm.com/systems/software/director/downloads/integration.htmlView the IBM Systems Director Upward Integration Web site on ibm.com whichprovides more information about IBM Systems Director upward integrationmodules created by IBM and other companies. IBM Systems Director UIMsenable third-party workgroup and enterprise systems-management products tointerpret and display data that is provided by IBM Systems Director PlatformAgent managed system.

v IBM Systems Director Best Practices Wikiwww.ibm.com/developerworks/wikis/display/WikiPtype/IBM+Systems+Director+Best+Practices+WikiView updated documentation and best practices for IBM Systems Director onvarious systems.

v IBM Serverswww.ibm.com/servers/View the IBM Servers Web site to learn about IBM Systems server and storageproducts.

v IBM ServerProven®

www.ibm.com/servers/eserver/serverproven/compat/us/View the IBM ServerProven Web site to learn about hardware compatibility ofIBM System x and BladeCenter® systems with IBM applications and middleware,including IBM Systems Director.

Forumsv IBM Systems Director

www.ibm.com/developerworks/forums/forum.jspa?forumID=759View the IBM Systems Director forum Web site on ibm.com to discussproduct-related issues pertaining to IBM Systems Director, IBM Systems DirectorUIMs, and IBM Systems Director extensions. This Web site includes a link forobtaining the forum using a Rich Site Summary (RSS) feed.

v IBM Systems Director SDK

About this publication ix

www.ibm.com/developerworks/forums/forum.jspa?forumID=1852&start=0View the IBM Systems Director SDK forum Web site to discuss issues pertainingto the IBM Systems Director Software Development Kit (SDK). This Web siteincludes a link for obtaining the forum using a Rich Site Summary (RSS) feed.

v IBM Systemswww.ibm.com/developerworks/forums/dw_esforums.jspView the IBM Systems forums Web site on ibm.com to learn about variousforums that are available to discuss technology-related and product-relatedissues pertaining to IBM Systems hardware and software products. This Web siteincludes a link for obtaining the forum using a Rich Site Summary (RSS) feed.

How to send your commentsYour feedback is important in helping to provide the most accurate and highestquality information.

If you have any comments about this book or any other IBM Systems Directorpublication, go to the IBM Systems Director information center Web site athttp://publib.boulder.ibm.com/infocenter/director/v6r2x/index.jsp. There youwill find the feedback page where you can enter and submit comments.

x IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Checklist: Installing IBM Systems Director Server on AIX

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 (38).__ 3. Check the security requirements (46).__ 4. Check the supported operating systems (47).__ 5. Check the supported database applications (55).

�2� Plan your installation of IBM Systems Director Server.

__ 1. Review the environment you will manage (72).__ 2. Review the licensing requirements (77).__ 3. Choose installation options for IBM Systems Director Server (81).__ 4. Choose where you will install IBM Systems Director Server (81).__ 5. Choose a database application to use with IBM Systems Director Server (82).__ 6. Plan users, groups, and security options for IBM Systems Director Server (94).

�3� Prepare the management server.

__ 1. Prepare the database application (107).__ 2. Prepare firewalls and proxies on the management server (117).__ 3. Prepare the management server (118).

�4� Install IBM Systems Director Server.

__ 1. Install IBM Systems Director Server (121).__ 2. Configure the database application (126).

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

__ 1. Log in to IBM Systems Director Server (132).__ 2. Perform some initial configuration of IBM Systems Director Server (127).

�6� Update IBM Systems Director Server.

__ 1. Update IBM Systems Director Server (159).

© Copyright IBM Corp. 1999, 2010 xi

xii IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Checklist: Installing agents on AIX

Use this checklist to guide you through the installation process.

�1� Evaluate your hardware and system configuration.

__ 1. Check the hardware requirements (19).__ 2. Check the network requirements (38).__ 3. Check the supported operating systems (47).__ 4. Check the supported virtualization software (51).

�2� Determine what agents you need to install.

__ 1. Review the task support for different management levels (56).__ 2. Determine the management level you need for your managed systems (84).__ 3. If you have virtual systems, determine what agents are needed for the virtual

systems (85).__ 4. Check the version compatibility of the agents you want to install (75).

�3� Prepare your managed systems.

__ 1. Prepare all managed systems for discovery and management by IBM SystemsDirector (137).

__ 2. Prepare systems for Common Agent (153).

�4� Discover the managed systems.

__ 1. Discover the managed systems on which you will install agents (146).__ 2. Request access to the managed systems (150).

�5� Install the agents.

__ 1. Use the Agent Installation Wizard to deploy agent packages to your managedsystems (155).

�6� Update the agents.

__ 1. Update the agents (159).

© Copyright IBM Corp. 1999, 2010 xiii

xiv IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Chapter 1. IBM Systems Director technical overview

IBM Systems Director is a platform-management foundation that streamlines theway you manage physical and virtual systems across a heterogeneousenvironment. By using industry standards, IBM Systems Director supports multipleoperating systems and virtualization technologies across IBM and non-IBM x86platforms.

Through a single user interface, IBM Systems Director provides consistent viewsfor viewing managed systems, determining how these systems relate to oneanother, and identifying their statuses, thus helping to correlate technical resourceswith business needs. A set of common tasks included with IBM Systems Directorprovides many of the core capabilities required for basic management, whichmeans instant out-of-the-box business value. These common tasks includediscovery, inventory, configuration, system health, monitoring, updates, eventnotification, and automation across managed systems.

IBM Systems Director's Web and command-line interfaces provide a consistentinterface 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 resourcesv Notifying users of problems that occur on system and ability to drill down to

the source of the problemv Notifying users when systems need updates and distributing and installing

updates on a schedulev Analyzing real-time data for systems and setting critical thresholds that notify

the administrator of emerging problemsv Configuring settings of a single system and creating a configuration plan that

can apply those settings to multiple systemsv Updating installed plug-ins to add new features and function to the base

capabilitiesv 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. Itsupports the management of a variety of IBM and non-IBM hardware drivingcommon tasks through the following platform management plug-ins and virtualresources. The systems supported include:v IBM Power Systems management

– HMC, IVM, and VIOS appliances– Power servers, Power blades, and LS41 and QS21 blade servers– AIX , IBM i, and Linux on POWER® operating systems

v IBM BladeCenter and System x management– IBM BladeCenter chassis components, such as switch modules and server

blades– System x systems and blade servers– VMWare, Microsoft Virtual Server (MSVS), and Xen virtual servers– Windows and Linux operating systems on System x

v IBM System z management– z/VM hypervisor– Linux on System z operating system installed on z/VM® virtual servers

© Copyright IBM Corp. 1999, 2010 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®, DS 5000, and DS6000™

– Storage switches, such as IBM BladeCenter SAS, Brocade, QLogic, Nortel, andCisco

v IBM System Storage management

IBM Systems Director integrates with robust workgroup and enterprisemanagement software from IBM (such as Tivoli software), Computer Associates,Hewlett-Packard, Microsoft, NetIQ, and BMC Software.

IBM Systems Director componentsIBM Systems Director includes IBM Systems Director Server and twooperating-system agents: Common Agent and Platform Agent.

IBM Systems Director Server provides a central point of control for aggregatingand managing discovered systems based on a service-oriented architecture. It canbe installed on one or more systems, called management servers. Systems thatconnect to the IBM Systems Director Web interface on the management serverthrough a Web browser are called browser systems.

The operating-system agents serve as the control point for accessing operatingsystem and host information that might not be accessible through an out-of-bandinterface (such as remote supervisor adapter (RSA), Baseboard ManagementControl (BMC), and BladeCenter Management Module). These agents run onoperating-system-based and hardware-based endpoints, called systems, that can bediscovered and managed by IBM Systems Director. The level of systemmanagement depends on the agent that is installed on the system: Common Agentor Platform Agent. Each agent provides a different footprint size, level ofperformance, and set of management functions.

IBM Systems Director can discover and manage some systems on which neither ofthese operating-system agents is installed, but the level of management is limited.

This figure shows where the IBM Systems Director Server and operating-systemagents are installed in a basic IBM Systems Director environment.

2 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Management serverThe management server is a system that has IBM Systems Director Server installed.It provides a central point of control for aggregating and managing discoveredsystems 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 accessinformation that is stored in this database even when the managed systems are notavailable. IBM Systems Director Server includes a default database, Apache Derby,although you can choose to use any supported database (including thehigh-performance DB2® database).

IBM Systems Director Server includes two interfaces that the system administratorcan use to manage their environment: a Web user interface and a command-lineinterface. The system that you use to interact with these interfaces is called thebrowser 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 isinstalled automatically on that system. The Common Agent provides a rich set ofsecurity, deployment, and management function.

Common AgentCommon Agent provides a rich set of security, deployment, and managementfunction.

Common Agent is available for all Power Systems, System x, IBM BladeCenter,System z systems, and some non-IBM systems, when the system is running asupported operating system.

Notes:v Systems running AIX require 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 SystemsDirector 6.x supports agent systems running either the new Common Agentversion 6.x or the older Level 2: IBM Director Agent version 5.20.

The functionality that is available for Common Agent managed systems variesbased on the operating system and hardware in an environment, and includes thefollowing functionality:v Discover systemsv Collect comprehensive platform and operating system inventory datav Monitor health and statusv Manage alertsv Remotely deploy and install Common Agentv Perform remote access, including transferring filesv Perform power management functionv Additional event supportv Monitor processes and resources, and set critical thresholds send notifications

when triggeredv Manage operating system resources and processesv Manage updates

Additionally, using Common Agent instead of Platform Agent provides enhancedscalability through asynchronous system management, which reduces the demandson IBM Systems Director Server. Firewall management is simplified, too, becauseCommon Agent requires that you keep fewer ports open.

For a detailed list of functionality that is supported by Common Agent managedsystems, see the Planning information.

Note: Throughout the IBM Systems Director documentation, the term CommonAgent (with both words capitalized) refers to the IBM Systems Director CommonAgent, which includes subagents that provide specific management capabilities forIBM Systems Director. IBM Systems Director can also discover and perform limitedmanagement on other common agents that use the common agent services (CAS)architecture. When referring to these common agents generically, lowercase text isused.

4 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

For information about resource managers and agent managers, see “Commonagent services”.

Platform AgentPlatform Agent is well suited for environments that require a smaller footprintwithout sacrificing a high level of manageability. It provides a subset of CommonAgent 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, andSystem z, IBM System Storage systems, and some non-IBM systems.

For IBM i, Platform Agent is part of the IBM Universal Manageability Enablementfor i Licensed Program Product that ships with the base operating system.

Platform Agent 6.1.x is the upgrade replacement to Level 1: IBM Director CoreServices version 5.20.3. IBM Systems Director Server 6.1 and 6.1.x support systemsrunning either IBM Director Core Services version 5.20.3 or Platform Agent 6.1.x.Common Agent 6.1.1 supports systems running Platform Agent 6.1.x.

Note: The version level of Platform Agent might not match the version levels ofIBM Systems Director Server or Common Agent.

The function available for Platform Agent managed systems is limited to thefollowing tasks, and varies based on operating system and hardware.v Discover systemsv Collect limited platform inventory datav Monitor health and statusv Manage alertsv Remotely deploy and install Common Agentv Perform limited remote accessv Perform limited restart capabilities

For a detailed list of function that is supported by Platform Agent managedsystems, see the Planning information in the information center at.

Agentless managed systemsIBM Systems Director provides a set of manageability functions for managedsystems that do not have Common Agent or Platform Agent installed. TheseAgentless managed systems are best for environments that require very smallfootprints 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 DistributedComponent Object Model (DCOM) protocol, or the Simple Network ManagementProtocol (SNMP) interface. IBM Systems Director discovers Agentless managedsystems by verifying the IP addresses on your network and scanning the ports ofthose addresses using the SSH or DCOM protocols. By default, IBM SystemsDirector uses the range of addresses that are in the IP domain of the managementserver. You can discover a specific IP address or range of IP addresses using theIBM Systems Director Web interface.

Chapter 1. IBM Systems Director technical overview 5

When an Agentless managed system is discovered, it is locked by default. You canunlock 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 andrunning it via SSH or DCOM services.

Note: No persistent data is stored on Agentless managed system.

For a detailed list of function that is supported by Agentless managed systems, seethe “Planning for IBM Systems Director” section in the information center atpublib.boulder.ibm.com/infocenter/director/v6r2x/topic/com.ibm.director.plan.helps.doc/fqm0_r_planning.html.

Manageable resource typesA 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 anduse the Resource Explorer task to view and work with these resources.

Manageable systems and system typesA system is one type of resource that IBM Systems Director manages. It is anoperating-system-based or hardware-based resource that has an IP address andhost name and can be discovered and managed by IBM Systems Director. From theNavigate Resource page in the IBM Systems Director Web interface, you can viewthe All Systems group to work with all discovered systems.

Operating-system-based systemsOperating-system-based systems (referred to as operating systems) consistof the operating system image, agent, drivers, applications, andconfiguration settings. From the Navigate Resource page in the IBMSystems Director Web interface, you can view the All Operating Systemsgroup to work with these types of systems.

Hardware-based systemsHardware-based systems are the physical and virtual systems, such asservers, virtual servers, storage systems, and network devices. Physicalsystems can host multiple operating systems and virtual servers, either byusing a dual-boot feature or by way of a hypervisor. From the NavigateResource page in the IBM Systems Director Web interface, you can use theAll Network Systems, All Storage Systems, or All Systems groups to workwith the physical aspects of a system, determine how many virtual serversa physical system contains, and determine how many operating systemsare running on a physical system.

To view the relationships between systems, view the topology map view for asystem by selecting the system and then clicking Actions > Topology Perspectives.A submenu of applicable perspectives is displayed.

To view resources associated with a system, select the system and then clickActions > Related Resources. A submenu of applicable related resources isdisplayed.

IBM Systems Director manages the following types of systems:

6 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

ChassisA physical resource that encloses other resources and provides definablefunctions. Example types include a desktop, processing node,uninterruptible power supply, disk or tape storage, or a combination ofthese types.

ClusterA computer system that is composed of two or more computer systemsthat operate together to increase performance, reliability, availability, andserviceability.

ComputerSystemA single component that runs one operating system, or multiplecomponents that are controlled by one or more operating systems.

GenericNetworkDeviceA computer system that has an unknown device type.

HardwareManagementConsoleA computer system that controls managed systems. This includes themanagement of logical partitions and the use of Capacity on Demand.

OperatingSystemSoftware that is responsible for the formation of an execution environmentand allocations of resources for software programs on a computer.

PassThroughModuleA Pass-Thru module.

Server A single node computer system such as a desktop, mobile device, orNetPC. The Server class type is derived from the ComputerSystem classtype.

StorageSubsystemA computer system that is dedicated to acting as a storage server.

SwitchA computer system that is dedicated to acting as a switch for networktraffic.

SystemChassisA computer system that represents a modular enclosure that contains oneor more blades.

You can use the lssys -I command to obtain a list of valid system types forcommands such as discover.

Virtualization allows you to hide the physical characteristics of your servers toconsolidate servers, optimize resource usage, and improve IT flexibility andresponsiveness. Using virtualization, you can create multiple discoverable virtualservers from a single physical server or create a single discoverable virtual serverfrom multiple physical servers. Each virtual server has an independent operatingenvironment and can have functions or features that are not available in itsunderlying physical resources.

Tip: Virtual servers running on IBM systems are often referred to as logicalpartitions or virtual machines.After IBM Systems Director discovers a physical server, it continues the discoveryprocess to find all associated virtual servers. Each IBM system offers virtualizationtechnologies to help you consolidate systems, optimize resource utilization, andimprove IT flexibility and responsiveness.

Chapter 1. IBM Systems Director technical overview 7

User interfacesThere are several methods for managing an IBM Systems Director environment: aWeb interface and a command-line interface (smcli).

Web interface

You can use the IBM Systems Director Web interface to conduct comprehensivesystems management through a graphical user interface. Data is securelytransferred between the Web browser and Web interface through HTTPS.

The system on which you logged in to the IBM Systems Director Web interface isreferred to as the browser system. You log in to the IBM Systems Director through asupported 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 DirectorServer is installed and Port_Number is the first (lower) of two consecutive portnumbers that you specified for the Web server to use. The default ports for theWeb server are 8421 and 8422. If you use port 8422, make sure that you specifyhttps to indicate a secure port.

Command-line interfaces

You can use the systems management command-line interface interactively usingthe smcli utilities. This command-line interface (CLI) is an important primaryinterface into IBM Systems Director and can be used either as an efficient way toaccomplish simple tasks directly or as a scriptable framework for automatingfunctions that are not easily accomplished from a graphical user interface. Forsecurity 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 inprevious releases through the discontinued dircli utility.

v For security, the CLI runs only on the management server. You can run the CLIremotely using a remote-access utility, such as Secure Shell (SSH) or Telnet.

Base function and extensible plug-insBase plug-ins in IBM Systems Director provide core function to manage the fulllifecycle of IBM servers, storage, network, and virtual servers. Plug-ins thatprovide advanced function or function tailored to a particular environment can bedownloaded 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 propertiesv Organizing logical sets of resources into groupsv Starting, stopping, and scheduling tasks in IBM Systems Directorv Integrating third-party management software and other programs into the IBM

Systems Director Web interfacev Managing auditing

8 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

v Encrypting interprocess communicationv Managing Common Agent registration and authenticationv Authenticating users through a configured user registry available from the

operating system, Lightweight Directory Access Protocol (LDAP), or domaincontroller

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 whenservices span different systems

v Installing, upgrading, and promoting agents

Discovery managerDiscovery manager performs physical and virtual system discovery and inventoryof related resources on the network.

You can use the discovery manager plug-in to:v Discover systems and other resources (such as physical and virtual servers,

storage systems, and network devices) in a heterogeneous environment. Discoverresources by using a single IPv4 or IPv6 address, a single host name, a range ofIP addresses, or use a discovery profile to discover systems of different typesacross multiple subnets.

v Collect inventory data about hardware and software that is currently installedon systems. Inventory data is information about physical, logical, and virtualhardware (such as virtual systems, virtual servers, and farms), softwareapplications, operating systems, middleware, firmware and BIOS, diagnosticinformation, and network.

v Manage inventory profiles that you can use to discover a group of resources orcollect inventory data based on a set of criteria.

v View systems, inventory data, and relationships among systems in the networkusing Navigate Resources.

v Request access to manage security credentials for discovered systems.

Status managerStatus manager provides an at-a-glance view of the health of your managedresources (including systems, operating systems, applications, processes, andsecurity).

The status of discovered systems is automatically retrieved and displayed, and thisdisplay can be customized in several ways—using one of the system status andhealth tasks, navigating to a specific resource, or using 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 andevents for systems.

v Determine the health, compliance, and performance of managed systems in yourenvironment using the health summary, scoreboard, and dashboard. The healthsummary shows the overall health of your managed systems. The scoreboardsummarizes the hardware state, event state and compliance state for allmanaged systems. The dashboard shows performance information for specificmanaged systems.

v View the event log.

Chapter 1. IBM Systems Director technical overview 9

v Identify problems and find the root cause by viewing detailed information aboutthe problems and inspecting the event log.

v Monitor dynamic properties of resources by defining monitors and thresholds.v Monitor applications on a specific system by defining process monitors.v Automatically send notifications when devices and services on a specific system

reach or exceed a particular setting by defining thresholds.

Configuration managerConfiguration manager is used to integrate new hardware into your environment,configure systems after installation, or do one-off configurations for problemresolution. Configuration manager leverages a set of well defined templates thatcan be applied to servers, storage, and network resources even if the resources arecomprised 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 workflowthat the configuration needs to be support).

v Manage configuration templates and plans. A configuration template is a collectionof settings and values that define the configuration of a system. A configurationplan is a set of templates that can be applied to one or more systems in a specificorder.

Automation managerAutomation manager provides tools to notify an administrator or run a predefinedtasks 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 taskor program on the management server or the system on which the event wasgenerated or sending an email notifications over the Internet or to a mobilephone.

Update managerUpdate manager provides tools for maintaining current versions of operatingsystems, device drivers, firmware and BIOS, and IBM Systems Director agent andserver code on managed systems without an upgrade or migration of the installedproduct.

10 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

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 in 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 managerRemote access manager provides tools that support running and monitoringapplications 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 VirtualNetwork Computing (VNC), Remote Desktop (RDP), and web-based remotecontrol for IBM BladeCenter and RSA.

v Run command-line programs through a remote session. The remote sessioncreates less network traffic and uses fewer system resources than the remotecontrol applications and, therefore, is useful in low-bandwidth situations.

v Run hardware management commands from the hardware command line, whichconnects to the service processor of the target system.

v Manage files on a remote system.v Open console windows to one or more POWER managed systems.v Execute a command on one or more managed systems in parallel.

Virtualization managerVirtualization manager provides tools for managing the lifecycle of virtualresources.

Virtualization manager now includes support for virtualized environmentsmanaged by wholly different server virtualization environments. These includeHardware Management Console (HMC), Integrated Virtualization Manager (IVM),Microsoft Virtual Server, VMware and Xen virtualization. Some additional basicdiscovery and health management is supported for z/VM virtualization. As aresult of this cross-solution management consolidation, you can visualize andcontrol 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 View topology that shows the connections between physical and virtualresources, which can vary dynamically across time

Chapter 1. IBM Systems Director technical overview 11

v Track alerts and system status for virtual resources and their resources to easilydiagnose problems affecting virtual resources

v Create automation plans based on events and actions from virtual and physicalresources, such as relocating a virtual server based on critical hardware alerts

v Create, delete and manage virtual servers and virtual farms for severalvirtualization technologies in the industry

v Relocate virtual servers to alternate physical hosts

Note: For the full set of virtualization support, it is recommended that you useIBM Systems Director VMControl. See the Virtualization Management summarypage for more information.

Network ManagementNetwork Management provides management functions for network devices,including discovery, inventory, health and status monitoring, and configuration.

You can use Network Management to:v Discover network devices in your environment.v Review your network device inventory.v Monitor the health and status of network devices.v View network device configuration settings, and apply templates to configure

devices.v Run network diagnostics tools like ping and traceroute.

IBM BladeCenter and System x managementIBM BladeCenter and System x management provides lifecycle management ofyour modular System x and IBM BladeCenter systems and related resources,including discovery, health and status monitoring, configuration, updates, andvirtualization. It also provides platform-specific functions.

You can use the IBM BladeCenter and System x management plug-in to:v Change power settingsv Manage hardware logsv Identify hardware using the locator LEDv Turn off light-path diagnostic LEDs

IBM System z managementIBM System z management provides the capability to discover System z hostedvirtual servers, and to access status information about them.

This plug-in provides functions to discover, monitor status, configure, and updatethese virtual servers. It also generates information used in the Welcome panelsummary view and includes support for Linux on System z and z/VM systemsrunning on IBM System z mainframes.

IBM Power Systems managementIBM Power Systems management provides lifecycle management of your IBMPower systems, and platform managers such as Hardware Management Console(HMC) and Integrated Virtualization Manager (IVM) platform managers, includingdiscovery, 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:

12 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

v Manage the following Power Systems environments that might include serverswith any supported processor versions 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 serverresources, and relocating virtual servers between host systems.

v Perform management tasks that are available from the IBM Systems DirectorWeb interface for supported versions of AIX and IBM i.

For additional information about managing the virtualization and consolidation onPower systems using IBM Systems Director, see the Managing IBM Power Serverswith 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 managementIBM System Storage management provides lifecycle management of your physicaland virtual storage systems, including discovery, health and status monitoring,configuration, updates, and virtualization. It also provides platform-specificfunctions.

You can use the IBM System Storage management plug-in to:v Add storage systems to IBM Systems Director using a proxy providerv Configure storage systemsv Manage storage devicesv Update a SAN configuration profilev Launch storage management applicationsv Use integrated SCM features to manage integrated RAID Controllers,

BladeCenter SAS modules, and BC-S RAID SAS modulesv 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 storageresources

v Support for IBM System Storage Area Network products

Additional IBM Systems Director plug-insAdditional IBM Systems Director plug-ins can be downloaded and installed on topof IBM Systems Director to provide advanced function or function tailored to aparticular environment.

For a complete list of available plug-ins and for information about how todownload and install the plug-ins, see the IBM Systems Director Web site atwww.ibm.com/systems/management/director/plugins/.

Active Energy Manager plug-in

The Active Energy Manager plug-in helps you to monitor and manage the powerand cooling needs of IBM servers and IBM BladeCenter systems. Non-IBM systems

Chapter 1. IBM Systems Director technical overview 13

can also be monitored using metering products, such as power distribution units(PDU), sensors, and integration with facility software. You can use Active EnergyManager to:v Allocate less power and cooling infrastructure to your IBM servers.v Reduce 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 licensed plug-in that supports Windows, Linux onPower Systems, and Linux on System x platforms.

BladeCenter Open Fabric Manager plug-in

The BladeCenter Open Fabric Manager plug-in helps you to quickly replace andrecover 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 100different chassis without any blade servers installed in the chassis.

v Automatically replace a failed blade from a designated pool of spare blades.

BladeCenter Open Fabric Manager is a for-fee plug-in that supports all platformsthat IBM Systems Director supports.

Service and Support Manager plug-in

The Service and Support Manager plug-in, which includes the Electronic ServiceAgent™ tool, identifies and reports hardware problems and service informationautomatically to IBM for service and support. All information sent to IBM is storedin a secure IBM database and used for improved problem determination. You canuse 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 supportrepresentatives when they are solving your problem.

v Communicate with IBM using a secure Internet connection using encryption andauthentication.

Service and Support Manager is a free plug-in that is supported on the followingoperating systems when installed on the IBM Systems Director managementserver:v Windows for 32–bit and 64–bit systemsv Linux on System x for 32–bit and 64–bit systemsv Linux on Power Systemsv Linux on System zv AIX

14 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

IBM Systems Director Network Control plug-in

The Network Control plug-in provides facilities to discover, inventory, and monitornetwork devices, launch vendor applications for configuration of network devices,and see groups of network devices.

Note: IBM Systems Director Network Control V1.1 is not supported on IBMSystems Director. When you install or upgrade to IBM Systems Director V6.2, theManage page displays Network Management in place of IBM Systems DirectorNetwork Control.

IBM Systems Director Storage Control 4.2.1

The Storage Control plugin lets you manage an expanded set of storagesubsystems and Fibre Channel switches.

You can use Storage Control to discover and collect inventory, and monitor devicehealth. These subsystems include the IBM DS8000 family (DS8100, DS8300, DS8700,DS8800), the SAN Volume Controller, and the IBM Storwize V7000, as well as theBrocade Fibre Channel switches.

Important: You must use IBM DB2 Enterprise Edition v. 9.7 (GA version only; fixpacks are not supported) as the local database application for Systems Director touse Storage Control. That is, the correct version of IBM DB2 must be installed onthe same system as Systems Director. Migration from other databases withinSystems Director to IBM DB2 is not supported.

For more information about Storage Control, see this topic: IBM Systems DirectorStorage Control 4.2.1.

IBM® Systems Director Transition Manager for HP® SystemsInsight Manager™ plug-in

The Transition Manager for HP® Systems Insight Manager™ plug-in enables you todiscover systems that are being managed by HP Systems Insight Manager andsmoothly make the transition to managing the systems in IBM Systems Director.Transitioned systems can be either IBM and non-IBM hardware. After the transitionis complete, you can manage the systems using IBM Systems Director which canprovide superior systems-management features for IBM hardware. Additionally,you can still manage the systems using HP® Systems Insight Manager™.

IBM Systems Director VMControl plug-in

The VMControl plug-in is designed to simplify the management of workloads inyour IT environment. Use IBM Systems Director VMControl Express® Edition, IBMSystems Director VMControl Standard Edition, and IBM Systems DirectorVMControl Enterprise Edition to manage virtual servers, virtual appliances,workloads, and system pools across multiple hardware platforms andvirtualization environments from one location.

IBM PowerVM™ Workload Partition Manager for AIX plug-in

IBM PowerVM Workload Partition Manager for AIX (WPAR Manager) is a plug-infor IBM Systems Director that provides a centralized point of control for managingworkload partitions (WPARs) across a collection of managed systems running AIX. Workload Partition Manager can manage heterogeneous environments of

Chapter 1. IBM Systems Director technical overview 15

managed systems at different AIX technology levels. However, to exploit fullmanagement capabilities, the Workload Partition Manager agent should beupdated to the latest version. The following features are supported on all AIXtechnology levels: Cross-system management of WPARs, including lifecyclemanagement Global load balancing with application mobility Web-basedadministration of basic WPAR operations and advanced management tasksMonitoring and reporting of WPAR performance metrics.

Upward integrationIBM Systems Director lets you to make the most of your existing enterprisemanagement structure by upwardly integrating with many workgroup andenterprise-management products.

IBM Systems Director upward integration modules (UIMs) and management packsenable non-IBM workgroup and enterprise-management products to interpret anddisplay data that is provided by Common Agent and Platform Agent. IBM SystemsDirector UIMs and management packs provide enhancements to theenterprise-management products that you can use to collect inventory data, viewIBM Systems Director event notifications, and for some UIMs, distribute IBMSystems Director software packages.

With the IBM Systems Director UIMs and management packs, you can use yourenterprise-management software to manage systems that have Platform Agent orCommon 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, includingCommon Information Model (CIM), Web-Based Enterprise Management (WEBM)and Extensible Markup Language (XML), to provide compatibility with yourexisting enterprise-management software.

For more information about upward integration modules, see IBM SystemsDirector Upward Integration Modules in the IBM Systems information center onthe Web at publib.boulder.ibm.com/infocenter/director/v6r2x/topic/com.ibm.director.uims.helps.doc/fqs0_main.html.

You can also configure IBM Systems Director Server to forward alerts (such asSNMP) to higher-level enterprise managers, including CA Unicenter NSM, HPOpenView NNM, HP OpenView Operations for Windows, Tivoli Netview, TivoliManagement Framework, Microsoft Systems Center Operations Manager, andMicrosoft Systems Management Server.

16 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Chapter 2. Planning for IBM Systems Director

Before installing or updating IBM Systems Director, review the installationrequirements and plan your installation.

Hardware and software requirementsIBM Systems Director has specific requirements for hardware and software. Theserequirements 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 DirectorTo successfully install IBM Systems Director, the system on which you install IBMSystems Director components must meet certain hardware requirements,depending on the components to be installed and the type of system on whichthey will be installed.

Hardware requirements for running IBM Systems Director ServerIBM Systems Director Server has certain hardware requirements. Theserequirements can vary depending on the workload.

If you are interested in information about how to plan, implement, configure, anduse an IBM Systems Director Server to manage a large configuration with optimalperformance, see the Performance Tuning and Scaling Guide for IBM SystemsDirector 6.2. The Performance Tuning and Scaling Guide also contains informationabout the following topics:v Running IBM Systems Director plug-ins, such as IBM Systems Director Active

Energy Manager® and IBM Scalable Systems Managerv Integration with Tivoli productsv Implementing High Availability (HA)

Additionally, the IBM Systems Workload Estimator for IBM Systems Director6.2.1is a web-based tool to provide hardware sizing recommendations for systemsrunning the IBM Systems Director server.

Recommended hardware requirements for IBM Systems Director Server runningon AIX :

IBM Systems Director Server has certain hardware requirements to run onsupported IBM Power systems running AIX , including IBM Power JS21 and laterblade servers.

Hardware requirements for running IBM Systems Director for AIX systems can beobtained by using the IBM Systems Workload Estimator. The IBM SystemsWorkload Estimator is a web tool for estimating hardware requirements for variousworkloads. You can access the IBM Systems Workload Estimator workload for IBMSystems Director at www-01.ibm.com/support/docview.wss?uid=nas7cd6a96f49d05f608862577420075ca9a&myns=x016&mynp=OCSGZ2Z3&mync=E.

© Copyright IBM Corp. 1999, 2010 17

The IBM Systems Workload Estimator asks several questions about your intendedusage, such as the number of systems you are managing and whether you areusing a local or remote database. After the questions are answered, IBM SystemsWorkload Estimator will generate a drop-down list of system model and featuresthat meet the resource requirements of Systems Director including an estimate ofthe number of cores, memory, disk capacity, and number of disk drives required. Italso shows a “Growth Solution” which can handle further growth for managinglarger environments.

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.v The Estimator only provides disk space requirements that are not on a file

system base. For AIX, please consider that space requirements to run IBMSystems Director relate to the following file systems:– /opt: for server information not kept in a database and if using the Derby

database. Refer to your database configuration for the file system hosting thenon-Derby database.

– /var: for Common Agent information-like log files.

Paging space should be at least 3 GB regardless of the memory size.

It might be necessary to change the maximum Java heap size in order for IBMSystems Director to take advantage of additional memory. On AIX, the Java heapsize setting is the following path: /opt/ibm/director/lwi/conf/overrides/director.javaopt. On 64-bit operating systems, the optimal heap size value istypically in the range of 2 GB (-Xmx2g) to 8 GB (-Xmx8g), depending on thesystems being managed and the amount of physical memory available on the IBMSystems Director Server.

The following table provides information about disk storage requirements forinstalling IBM Systems Director Server. These requirements include CommonAgent and Platform Agent, which are installed with IBM Systems Director Server.These requirements do not include disk storage requirements for running IBMSystems Director Server and the database, updating IBM Systems Director Serveror for downloading and staging updates (such as AIX, HMC, or system firmwareupdates) with Update manager.

Note: The disk storage requirements in the table below are for a merge installationof a 6.2 server and 6.2.1 updates. If you are performing an update installation from6.2.0.x to 6.2.1, see Determining disk space requirements for applying updates.

Table 1. Disk storage requirements for installing IBM Systems Director Server

File system Disk space required

/ 50 MB

/usr 256 MB

/var 512 MB

18 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 1. Disk storage requirements for installing IBM Systems Director Server (continued)

File system Disk space required

/tmp 2 GBNote: This space is only required during theinstallation and is freed after the installationis complete.

/opt 5 GB

Web download file(SysDir6_2_1_DVD_AIX.iso)

Size specified on downloads website

(*) If /tmp is a JFS2 file system, the file system can be shrunk after the installation.Related reference

IBM Systems Director Best Practices Wiki: Install or upgrade to the latest IBMSystems Director version

IBM Systems Director Best Practices Wiki

Hardware requirements for systems running Common Agent orPlatform AgentCommon Agent and Platform Agent have minimum processor speed, randomaccess memory (RAM), and disk space requirements.

Note: The disk space listed is the minimum requirement for an installation usingthe default selections.

IBM Power systems running AIX

Note: On systems that do not provide display capability, such as IBM Power bladeservers, you must export IBM Systems Director Web interface using either thexhost command or SSH tunneling. The IBM Systems Director Web interfacerequirements apply to the receiving system.

Table 2. Servers running AIX : Minimum hardware requirements

Requirements Common Agent

Processor speed POWER5, POWER6® or POWER7®

Memory (RAM) 512 MB (minimum)

Tables 8 and 9 provide information about disk storage requirements for installingCommon Agent. Table 8 covers the space requirements for the actual installation.Table 9 covers additional space requirements based on the installation method. Thetotal disk storage requirement must be calculated by combining Table 8 and Table9.

Note: If you are performing an update installation from 6.2.0.x to 6.2.1, seeDetermining disk space requirements for applying updates. Make sure that both/var and /tmp match the calculated free space specified on this page.

Table 3. Disk storage requirements for installing Common Agent (includes Platform Agent)

File system Disk space required

/ <5 MB

/usr 250 MB

Chapter 2. Planning 19

Table 3. Disk storage requirements for installing Common Agent (includes Platform Agent) (continued)

File system Disk space required

/var 300 MB

/tmp 200 MB

/opt 140 MB

Note: The /tmp space is only required during the installation and is freed after theinstallation is complete.

Table 4. Additional disk storage requirement for installing Common Agent based on installation method

File system Disk space required

Manual installation using SysDir6_2_1_Common_Agent_Installp_AIX_VIOS.tar.gz

Web download file:SysDir6_2_1_Common_Agent_Installp_AIX_VIOS.tar.gz(Location of your choice)

Size specified on downloads website

Space needed to extract web downloaded file:SysDir6_2_1_Common_Agent_Installp_AIX_VIOS.tar.gz(Location of your choice)

290 MB

Manual installation using SysDir6_2_1_Common_Agent_AIX.tar.gz

Web download fileSysDir6_2_1_Common_Agent_AIX.tar.gz(Location of your choice)

Size specified on downloads website

Space needed to extract web downloaded fileSysDir6_2_1_Common_Agent_AIX.tar.gz(Location of your choice)

290 MB

Space needed to extract dir6.2.1_commonagent_aix into /tmp/DirectorAgentselfextract.<identifier>

290 MB

Agent deployment with Agent Installation Wizard using SysDir6_2_1_Common_Agent_AIX.tar.gz

Server system: Web downloaded file(SysDir6_2_1_Common_Agent_AIX.tar.gz)

Size specified on downloads website

Server system: Space needed to extract web downloaded file(SysDir6_2_1_Common_Agent_AIX.tar.gz)

290 MB

Target system: Deploy dir6.2.1_commonagent_aix file 290 MB

Target system: Space needed to extract dir6.2.1_commonagent_aix into/tmp/DirectorAgentselfextract.<identifier>

290 MB

Determining disk space requirements for applying updatesBefore installing an update, you can determine the disk space required.

To determine disk space requirements for applying IBM Systems Director updates,follow these steps to review the disk space information before downloading theupdate.

Restriction: Note the following free space requirements for AIX:v IBM Systems Director Server update from 6.2 to 6.2.1 via Update Manager (to

extract SysDir6_2_1.zip): 1.3 GBv /tmp: 1.5 GBv /opt: 1.6 GBv /var: 100 M

20 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

v Common Agent update from 6.2 to 6.2.1– /var: 100 M– /tmp: 100 M

1. In the IBM Systems Director Web interface navigation area, click ResourceExplorer.

2. Navigate to the system that you need to update.3. Right-click the system and select Release Management > Show needed

updates.4. On the Show Needed Updates page, select the required update.5. Click Actions > Download The Download Updates window displays with the

Size of update and its Location.6. Multiply the update size value by 250%. The resulting number will be the

approximate disk space required on the system to download and install theupdate.

7. Click Cancel to close the Download Updates window.8. Optional: Alternatively, if you plan to import the update from a disk location,

you can assume that the disk space size is approximately a multiple of 250% ofthe size of the disk location.

Supported IBM systems and productsIBM Systems Director is licensed for use and supported in a large range of IBMsystems and products.

These systems and products include:v IBM BladeCenter chassisv IBM blade serversv IBM Power Systems (formerly System i® and System p® systems)v IBM System Storage Network Attached Storage (NAS) productsv System x serversv System z systems

To determine whether a system meets the recommended hardware requirementsfor your IBM Systems Director systems-management environment, see “Hardwarerequirements.”

Notes:

1. The degree of support that IBM Systems Director provides on these systemsand products might vary. For this information, see the IBM Systems DirectorRelease Notes.

2. IBM Systems Director runs on IBM Power and System z systems when theinstalled operating system is also supported by IBM Systems Director.

3. The IBM System Storage NAS products include an installation of CommonAgent.

4. Some systems and products might not be available in your area.

IBM BladeCenter productsIBM Systems Director provides support for IBM BladeCenter chassis and bladeservers.

Chapter 2. Planning 21

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

IBM BladeCenter blade serversv IBM BladeCenter HC10 blade server, machine type 7996v IBM BladeCenter HC10 blade server, machine type 7997v IBM BladeCenter HS12 blade server, machine type 8014v IBM BladeCenter HS12 blade server, machine type 8028v IBM BladeCenter HS20 blade server, machine type 7981v IBM BladeCenter HS20 blade server, machine type 8678v IBM BladeCenter HS20 blade server, machine type 8832v IBM BladeCenter HS20 blade server, machine type 8843v IBM BladeCenter HS21 blade server, machine type 8853v IBM BladeCenter HS21 XM blade server, machine type 7995v IBM BladeCenter HS22 blade server, machine type 7870v IBM BladeCenter HS22V blade server, machine type 7871v IBM BladeCenter HS40 blade server, machine type 8839v IBM BladeCenter HX5 blade server, machine type 7872v IBM BladeCenter JS12 blade server, machine type 7998v IBM BladeCenter JS20 blade server, machine type 8842v IBM BladeCenter JS21 blade server, machine type 8844v IBM BladeCenter JS22 blade server, machine type 7998v IBM BladeCenter JS23 blade server, machine type 7778v IBM BladeCenter JS43 blade server, machine type 7778v IBM BladeCenter LS20 blade server, machine type 8850v IBM BladeCenter LS21 blade server, machine type 7971v IBM BladeCenter LS22 blade server, machine type 7901v IBM BladeCenter LS41 blade server, machine type 7972v IBM BladeCenter LS42 blade server, machine type 7902v IBM BladeCenter PS700 Express blade server, machine type 8406v IBM BladeCenter PS701 Express blade server, machine type 8406v IBM BladeCenter PS702 Express blade server, machine type 8406v IBM BladeCenter QS21 blade server, machine type 0792v IBM BladeCenter QS22 blade server, machine type 0793

Supported network devicesIBM Systems Director supports discovery and monitoring of these networkdevices.

22 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Task support for network management

Find out which tasks are supported by Network Management for your networkdevices.

The tables provide lists of network devices, separated by type, and notes whichtasks are only supported by IBM Systems Director Network Control. The followingtasks are included in the support tables:

Discovery, Request Access, Inventory, Monitoring, and AlertsUse these basic network management functions to discover networkdevices, request access, gather information, and monitor status and devicehealth. Network adapters do not require discovery.

Note: To associate physical server subnets and VLANs in the Systems byVLAN and Subnet view, the switch inventory must be collected afternetwork topology is collected. Correct VLAN information in views likeSystems by VLAN and Subnet or the VLAN ID column in some groupsrequire that the switch vendor support the standard SNMP Q-Bridge MIB(1.3.6.1.2.1.17.7).

Packet Internet Groper (ping) and TracerouteThese network diagnostic tools help you test connections between networkdevices and troubleshoot network systems connectivity. Networkdiagnostic support is listed in the table, however, they cannot be used onswitches configured with a second privileged mode password or on IPv6targets.

Stacked Switch supportSwitch stacking allows you to combine several physical switches into onelogical entity. The stacked switch functions as a single network device,with one IP address for the stack. IBM Systems Director Network Controlprovides full support for some switch modules. Other switch modules aresupported only in their individual (non-stacked) configurations.

Configuration ManagementYou can work with the VLAN configuration and Protocol configuration ofsome devices using IBM Systems Director Configuration Manager. Thefollowing tables indicate which devices support these configurationmanagement tasks.

Context launch to vendor managementYou can use launch-in-context to access vendor configuration software forsome devices directly from the IBM Systems Director interface. This is atask-level launch, with device context, to the vendor management tool.Tasks can then be completed from within the vendor management tool.This IBM Systems Director Network Control task requires additional steps,see the topic Configuring launch to DCFM for more information.

The supported network devices are divided into the following tables:v Adapter devicesv BladeCenter Ethernet switch devicesv Non-BladeCenter Ethernet switch devicesv Other network devices, including Fibre Channel over Converged Enhanced

Ethernet (FCoCEE) switches, Fast Connection Failover (FCF) bridges, Securityappliances, and virtual network devices.

Chapter 2. Planning 23

Note:

v The following tables identify supported network devices which have been testedfor interoperability with IBM Systems Director. Other network devices withlimited interoperability might be recognized during discovery and inventory.

Table 5. Adapter devices and supported network management tasks

Tasks Supported

Device Inventory Monitoring

2 Port Ethernet Expansion Card (1xE) for IBM BladeCenter Yes Yes

Brocade 2-port 10Gb CNA adapter (CFFh) for IBM BladeCenter Yes Yes

Brocade 10Gb CNA for IBM System x Yes Yes

CIOv 2-port 4Gb FC HBA Yes Yes

CIOv 2-port 8Gb FC HBA Yes Yes

Emulex Virtual Fabric Adapter (CFFh) for IBM BladeCenter Yes Yes

Ethernet Expansion Card (CIOv) for IBM BladeCenter Yes Yes

Foxconn CFFv Gb Ethernet Expansion Card Yes Yes

Intel 2-port 10Gb Ethernet Expansion Card (CFFh) for IBMBladeCenter

Yes Yes

Intel PRO/1000 PF – 1P, PCIe x4, IOAT Yes Yes

NetXtreme II 10 GigE Express Fiber SR Adapter Yes Yes

QLogic 2-Port 10Gb CFFh Converged Network Adapter for IBMBladeCenter

Yes Yes

QLogic Dual-port 10Gb CNA for IBM System x Yes Yes

Table 6. BladeCenter Ethernet switch devices and supported network management tasks

Tasks Supported

Device

Discovery,Inventory,RequestAccess,Monitoring,and Alerts Ping Traceroute Stacked Switch

ConfigurationManagement

Blade Network Technologies 1/10GbUplink Ethernet Switch Module for IBMBladeCenter (44W4404)

Yes1 Yes Yes No Yes

Blade Network Technologies 10 Gb UplinkEthernet Switch Module for IBMBladeCenter (32R1783)

Yes1 Yes Yes No Yes

Blade Network Technologies 6-port 10 GbEthernet Switch Module for IBMBladeCenter (39Y9267)

Yes1 Yes Yes No Yes

Blade Network Technologies Layer 2/3Fiber Gb Ethernet Switch Module for IBMBladeCenter (32R1861)

Yes1 Yes Yes No Yes

Blade Network Technologies Layer 2/3Copper Gb Ethernet Switch Module forIBM BladeCenter (32R1860)

Yes1 Yes Yes No Yes

24 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 6. BladeCenter Ethernet switch devices and supported network management tasks (continued)

Tasks Supported

Device

Discovery,Inventory,RequestAccess,Monitoring,and Alerts Ping Traceroute Stacked Switch

ConfigurationManagement

Blade Network Technologies Layer 2-7 GbEthernet Switch Module for BladeCenter(32R1859)

Yes1 Yes Yes No Yes

Blade Network Technologies Virtual Fabric10Gb Switch Module for IBM BladeCenter(46C7191)

Yes1 Yes Yes No Yes

Cisco Catalyst Switch Module 3012 for IBMBladeCenter (43W4395)

Yes Yes Yes No No

Cisco Catalyst Switch Module 3110G forIBM BladeCenter (41Y8523)

Yes Yes Yes Yes No

Cisco Catalyst Switch Module 3110X forIBM BladeCenter (41Y8522)

Yes Yes Yes Yes No

Cisco Catalyst 3750 Yes No No Yes No

Cisco Nexus 4001I Switch Module for IBMBladeCenter (46M6071)2

Yes Yes Yes No Yes

Cisco Systems Intelligent Gb Fiber EthernetSwitch module for IBM BladeCenter(32R1888)

Yes Yes Yes No No

IBM BladeCenter 4-port Gb Ethernet switchmodule

Yes No No No Yes

IBM Server Connectivity Module for IBMBladeCenter (39Y9324)

Yes1 No No No Yes

Intel Gigabit Ethernet Switch Module forIBM BladeCenter T

Yes Yes No No Yes

Note:

1. Many hardware devices require you to install a vendor plug-in before you can request full access. Forinformation about obtaining and installing vendor plug-ins, see the related topics at the end of this page.

2. This switch does not support network topology functions of IBM Systems Director Network Control.

Table 7. Ethernet switch devices, including Internet routers, and supported network management tasks

Tasks Supported

Device

Discovery, Inventory,Request Access,Monitoring, andAlerts Ping Traceroute

ConfigurationManagement

Context launchto vendormanagement

Blade NetworkTechnologies RackSwitchG8000

Yes Yes Yes Yes No

Blade NetworkTechnologies RackSwitchG8052

Yes No No No No

Chapter 2. Planning 25

Table 7. Ethernet switch devices, including Internet routers, and supported network management tasks (continued)

Tasks Supported

Device

Discovery, Inventory,Request Access,Monitoring, andAlerts Ping Traceroute

ConfigurationManagement

Context launchto vendormanagement

Blade NetworkTechnologies RackSwitchG8124

Yes No No Yes No

Blade NetworkTechnologies RackSwitchG8264

Yes No No No No

Cisco Catalyst 3750-48 Yes No No No No

Cisco Catalyst 4948 Yes No No No No

IBM Ethernet Router B04M Yes Yes Yes No No

IBM Ethernet Router B08M Yes Yes Yes No No

IBM Ethernet Router B16M Yes Yes Yes No No

IBM Ethernet Router B32M Yes No No No No

IBM Ethernet Router J02M Yes Yes Yes No No

IBM Ethernet Router J06M Yes Yes Yes No No

IBM Ethernet Router J11M Yes Yes Yes No No

IBM Ethernet Switch B08R Yes Yes Yes No No

IBM Ethernet Switch B08S Yes Yes Yes No No

IBM Ethernet Switch B16R Yes No No No No

IBM Ethernet Switch B16S Yes Yes Yes No No

IBM Ethernet Switch B24C(Copper)

Yes No No No No

IBM Ethernet Switch B24C(Fiber)

Yes No No No No

IBM Ethernet Switch B24X Yes Yes Yes No No

IBM Ethernet Switch B24Y Yes No No No No

IBM Ethernet Switch B04R Yes No No No No

IBM Ethernet Switch B48C(Copper)

Yes Yes Yes No No

IBM Ethernet Switch B48C(Fiber)

Yes Yes Yes No No

IBM Ethernet Switch B48G Yes Yes Yes No No

IBM Ethernet Switch B48Y Yes No No No No

IBM Ethernet Switch B50C(Copper)

Yes Yes Yes No No

IBM Ethernet Switch B50C(Fiber)

Yes Yes Yes No No

IBM Ethernet Switch B50G Yes Yes Yes No No

IBM Ethernet Switch J08E Yes Yes Yes No No

IBM Ethernet Switch J48E Yes Yes Yes No No

26 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 7. Ethernet switch devices, including Internet routers, and supported network management tasks (continued)

Tasks Supported

Device

Discovery, Inventory,Request Access,Monitoring, andAlerts Ping Traceroute

ConfigurationManagement

Context launchto vendormanagement

IBM System StorageSAN384B

Yes No No Yes1 Yes2

IBM System StorageSAN768B

Yes No No Yes1 Yes2

IBM Ethernet Switch J02M Yes Yes Yes No No

IBM Ethernet Switch J16E Yes Yes Yes No No

Juniper EX2200 Yes No No No No

IBM Ethernet Switch J45E(Tsunami)

Yes No No No No

SMC Networks 8848MTigerStack II 10/100/1000

Yes No No No No

SMC Networks 8126L2TigerSwitch 10/100/1000

Yes Yes Yes No No

Note:

1. IBM Systems Director Network Control V1.2.2 and IBM System Storage Data Center Fabric Manager (DCFM)10.4.1a configured with SMI-S Agent are required to support Configuration Management of this device.

2. IBM Systems Director Network Control V1.2.2 and IBM System Storage Data Center Fabric Manager (DCFM)10.3.2 or higher are required to launch vendor configuration management of this device.

Table 8. Supported network management tasks for other network devices including Fast Connection Failover (FCF)bridge, Fibre Channel over Converged Enhanced Ethernet (FCoCEE) switches, and Security appliances

Tasks Supported

Device Device Type

Discovery,Inventory,RequestAccess,Monitoring,and Alerts Ping Traceroute

ConfigurationManagement

Context launchto vendormanagement

10Gb Ethernet Pass-ThruModule for IBM BladeCenter

Pass-Thrudevice

Yes1 N/A N/A No No

Brocade FCoE Switch Modulefor IBM BladeCenter

FCoCEE Switch Yes No No Yes Yes

IBM Converged Switch B32 FCoCEE Switch Yes Yes No Yes2 Yes3

Cisco Nexus 5010 Switch forIBM System Storage

StandaloneFCoCEE switch

Yes Yes Yes No No

Cisco Nexus 5020 Switch forIBM System Storage

StandaloneFCoCEE switch

Yes Yes Yes No No

Chapter 2. Planning 27

Table 8. Supported network management tasks for other network devices including Fast Connection Failover (FCF)bridge, Fibre Channel over Converged Enhanced Ethernet (FCoCEE) switches, and Security appliances (continued)

Tasks Supported

Device Device Type

Discovery,Inventory,RequestAccess,Monitoring,and Alerts Ping Traceroute

ConfigurationManagement

Context launchto vendormanagement

FastIron WS 624G or FastIronWS 624G-POE

Switch

Base Layer 3Router

POE Switch

POE Base Layer3 Router

Yes No No No No

FastIron WS 648G or FastIronWS 648G-POE

Switch

Base Layer 3Router

POE Switch

POE Base Layer3 Router

Yes No No No No

IBM Ethernet Appliance J34S SecurityAppliance

Yes No No No No

IBM Ethernet Appliance J36S SecurityAppliance

Yes No No No No

IBM Ethernet Appliance J56S SecurityAppliance

Yes No No No No

IBM Ethernet Appliance J58S SecurityAppliance

Yes No No No No

QLogic Virtual FabricExtension Module for IBMBladeCenter (46M6172)

FCF bridgemodule

Yes Yes No No No

Notes:

1. Pass-Thru devices display as in chassis inventory.

2. IBM Systems Director Network Control V1.2.2 and IBM System Storage Data Center Fabric Manager (DCFM)10.4.1a configured with SMI-S Agent are required to support Configuration Management of this device.

3. IBM Systems Director Network Control V1.2.2 and IBM System Storage Data Center Fabric Manager (DCFM)10.3.2 or higher are required to launch vendor configuration management of this device.

Supported storage devicesSystems Director manages a wide variety of storage devices. Supported storagedevices are: disks, switches, internal RAID controllers, and RAID subsystems. Seethe appropriate table to find the information you need.

“Supported devices” on page 29: This section lists the supported storagedevices, subsystems, and storage modules.

28 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

“Supported devices, based on operating system and Systems Director version”on page 31: This section lists the supported storage devices, subsystems, andstorage modules, depending on the version of Systems Director that you arerunning.“Supported devices and actions ” on page 36: These tables list the storagedevices and the actions you can perform on each with Systems Director.“RAID controller support” on page 37: This table describes Storage Managersupport of RAID controllers managed with various versions of Platform Agentsin IBM Systems Director.“Storage devices and IPv6 support” on page 37: This section lists the storagedevices and whether they support IPV6.

Supported devices

Note that a storage volume is similar to a logical volume.

This is a list of supported storage devices, subsystems, storage modules, and theiraccess devices:v Dedicate Local Storage, access with Integrated RAID Controllers (IRC)

– Legacy RAID Controller– Basic RAID Controller– Advanced RAID Controller

v IBM BladeCenter integrated storage, accessed with IBM BladeCenter S SASRAID Controller Modules, supported only on Windows (2003 and 2008) andLinux on System x systems.

v Network Storage, which is an external SAN storage system. Network storage isaccessed with storage switches, adapters, and protocols such as Fibre Channel,SAS, or iSCSI– IBM System Storage DS4100, DS4300, DS4500, DS4700, DS4800– IBM System Storage DS5020, DS5100, DS5300– IBM System Storage DS6000– IBM System Storage DS3200, DS3300, DS3400, DS3500– IBM System Storage N series: N3600 and N3700– IBM System Storage DS8000 (requires IBM Systems Director Storage Control

4.2.1 or IBM TotalStorage Productivity Center 4.2.1 or higher.)– IBM XIV 2810, 2812– IBM System Storage SAN Volume Controller (requires IBM Systems Director

Storage Control 4.2.1 or IBM TotalStorage Productivity Center 4.2.1 or higher.)– IBM Storwize V7000 (requires IBM Systems Director Storage Control 4.2.1 or

IBM TotalStorage Productivity Center 4.2.1 or higher.)v Storage switches

– BladeCenter - Switch Module - 2GB McData Fibre Channel Expansion Switch– BladeCenter - Switch Module - 4GB McData Fibre Channel Expansion Switch– BladeCenter - Switch Module - 4GB Qlogic Fibre Channel Expansion Switch– BladeCenter - Switch Module - Qlogic 8GB Switch Module– BladeCenter - Switch Module - Qlogic Transparent Switch Module for IBM

BladeCenter– Brocade 2Gbit/sec and 4Gbit/sec Fibre Channel (chassis and external)– Brocade 300 IBM System Storage SAN24B-4 Express fabric switch

Chapter 2. Planning 29

– Brocade 4GB SAN Switch Module for IBM eServer™ BladeCenter– Brocade 8GB SAN Switch Module for IBM eServer BladeCenter– Brocade SAN Switch Module for IBM BladeCenter– Cisco 4GB Fibre Channel Switch Module for IBM BladeCenter– Cisco Systems 4X InfiniBand Switch Module for IBM BladeCenter– IBM BladeCenter S SAS RAID Controller Module– IBM BladeCenter SAS Connectivity Module– IBM eServer BladeCenter 6-port Enterprise Fibre Channel Switch Module– IBM System Storage SAN40B-4 Qlogic 2Gbit/sec, 4Gbit/sec, and 8Gbit/sec

Fibre Channel (chassis and external)– IBM BladeCenter SAS Controller Module– McDATA Intrepid 6064, 6140, and 1000 Switches– McDATA Sphereon 3216, 3232, 4300, 4400, 4500, 4700, Fibre Channel Switches– SAS Connectivity Module for IBM BladeCenter

30 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Supported devices, based on operating system and SystemsDirector version

Table 9. Supported devices, based on operating system and Systems Director version

Hardware type ModelSystems Director

versionsupported

Provider

NameVersion /SMI-SLevel /CIMOM

Operating systemsupported

Integrated RAIDController (IRC)attached to aSystem x

LSI IRC1064/1064e/1068

6.1.0 PatniIBM Systems

Director PlatformAgent 5.20.31

Red HatEnterprise Linux

(RHEL) 4

Windows 2003

SLES 9

LSI IRC1064/1064e/1068/

1078

6.1.1 CardinalPlatform Agent

CIMOM

6.1.2

6.2.0Flamingo

00.07.05.xx /SMI-S 1.1 IBM

Systems DirectorPlatform Agent

6.1.x or 6.2.x

VMWare ESX, 3.5or 4.0

RHEL 4 or 5

Windows 2003(32- or 64-bit)

Windows 2008(32- or 64-bit)

SLES 9, 10, or 11

6.2.1 10M09

00.17.05.xx /SMI-S 1.1 IBM

Systems DirectorPlatform Agent

6.2.1

VMWare ESX, 3.5or 4.0

RHEL 4 or 5

Windows 2003(32- or 64-bit)

Windows 2008(32- or 64-bit)

SLES 9, 10, or 11

LSI IRC

M5014 / M5014 /M5025

6.2.1 10M09

00.17.05.xx /SMI-S 1.1 IBM

Systems DirectorPlatform Agent

6.2.1

VMWare ESX, 3.5or 4.0

RHEL 4 or 5

Windows 2003(32- or 64-bit)

Windows 2008(32- or 64-bit)

SLES 9, 10, or 11

AdaptecServeRAID

4/5/6/7

6.1.0 Adaptec

8.4 or 9.0

ICC 5.20.31L1CIMOM

Windows 2003

RHEL 4 or 5

VMWare ESX3.5

SLES 9 or 10

6.2.0

6 2 1

ServeRAIDPlug-in 9.10.x

9.2.0 IBM SystemsDirector Platform

Agent 6 2 x

Windows 2003 R2SP3

Windows 2008 R2

RHEL 4.8 or 5.4

Chapter 2. Planning 31

Table 9. Supported devices, based on operating system and Systems Director version (continued)

Hardware type ModelSystems Director

versionsupported

Provider

NameVersion /SMI-SLevel /CIMOM

Operating systemsupported

IBM BladeCenterS SAS RAIDController

NSSM 3GB(System x)

6.1.x

6.2.0

6.2.1

none

RSSM R1 6.1.xAdaptec RSSM

R1

2.99

SMI-S 1.1IBMSystems DirectorPlatform Agent

5.20.31

Windows 2003(32- or 64-bit)

Windows XP

RHEL 4 and 5

SLES 9 or 10

RSSM R2.1(System x and

System p)

6.2.0

6.2.1

Adaptec RSSMR2.1

4.29, SMI-S 1.1IBM Systems

Director PlatformAgent 6.2.1x

Windows 2003(32- or 64-bit)

Windows 2008(32- or 64-bit)

Windows XP

RHEL 4 and 5

SLES 9, 10, and11 (32- or 64-bit)

32 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 9. Supported devices, based on operating system and Systems Director version (continued)

Hardware type ModelSystems Director

versionsupported

Provider

NameVersion /SMI-SLevel /CIMOM

Operating systemsupported

FC Switch

QLogic 2GB or4GB

6.1.0

6.1.1QLogic SMI-S 1.0.x Embedded

Qlogic 2GB, 4GB,or 8GB

6.1.x

6.2.0

6.2.1

QLogic SIM-S 1.1 Embedded

Brocade 2GB or4GB

(Chassis-mountedor standalone)

6.1.x

6.2.0

6.2.1

Brocade120.9.0 (SMI-S

1.2)

Windows 2003(32-bit)

Windows 2008(32-bit)

RHEL 4

AIX 5.3, SLES 10

Brocade 8GB(standalone)

6.1.x with StorageSystem Pools

6.2.0 with StorageSystem Pools

Storage Controlor IBM Tivoli

StorageProductivity

Center

4.1, 4.1.1

Windows 2003(32- or 64-bit)

Windows 2008(32- or 64-bit)

RHEL 4 and 5

SLES 9, 10 and 11

6.2.1 Storage Control 4.2.1

Windows 2003(32- or 64-bit)

Windows 2008(32- or 64-bit)

Windows 2008 R2(64-bit)

AIX 5.3 or 6.1

RHEL 5.x

McDATASphereon or

Intrepid6.2.1 Storage Control 4.2.1

Windows 2003Server

Windows 2008

RHEL 4

Chapter 2. Planning 33

Table 9. Supported devices, based on operating system and Systems Director version (continued)

Hardware type ModelSystems Director

versionsupported

Provider

NameVersion /SMI-SLevel /CIMOM

Operating systemsupported

LSI Storage

DS3400/FC,DS4100, DS4200,DS4300, DS4400,DS4500, DS4700,

and DS4800

6.1.x

6.2.0Engenio

10.50.G0.04(SMI-S 1.1 )

Windows 2003(32- or 64-bit)

Windows 2008(32- or 64-bit)

RHEL 4 and 5

AIX 5.3 and 6.1

SLES 9 or 10

DS3400/FC,DS4100, DS4200,DS4300, DS4400,DS4500, DS4700,DS4800 DS5020,

DS5100, andDS5300

6.2.0

6.2.1Eagle

10.10.G5.xx,SMI-S 1.3

Windows 2003(32- or 64-bit)

Windows 2008(32- or 64-bit)

RHEL 4 and 5

AIX 5.3 and 6.1

SLES 9, 10, and11

34 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 9. Supported devices, based on operating system and Systems Director version (continued)

Hardware type ModelSystems Director

versionsupported

Provider

NameVersion /SMI-SLevel /CIMOM

Operating systemsupported

IBM storage

DS68006.1.x

6.2.0IBM DS6000

5.2.1.139 SMI-S1.1

Windows 2003(32- or 64-bit)

AIX 5.3 SP 3

RHEL 3

SLES 9

DS8300, SANVolume Controller

4.3 and 5.1

6.1.x with StorageControl

6.2.0 with StorageControl

Storage Controlor IBM Tivoli

StorageProductivity

Center

4.1, 4.11

Windows 2003(32- or 64-bit)

Windows 2008(32- or 64-bit)

RHEL 4 and 5

AIX 5.3 and 6.1

SLES 9, 10, and11

DS8300, SANVolume Controller6.1, IBM Storwize

V7000

6.2.1

Storage Controlor IBM Tivoli

StorageProductivity

Center

4.2.1

Windows 2003(32- or 64-bit)

Windows 2008(32- or 64-bit)

Windows 2008 R2(64-bit)

AIX 5.3 and 6.1

RHEL 5.x

IBM XIV2810-A14,2812-A14

6.2.0

6.2.1

Storage Controlor IBM Tivoli

StorageProductivity

Center

4.2.1

Windows 2003(32- or 64-bit)

Windows 2008(32- or 64-bit)

Windows 2008 R2(64-bit)

AIX 5.3 and 6.1

RHEL 5.x

NAS storage

N-series (N3600or N3700) - NFS

only

6.1.2

6.2.0

6.2.1

NetApp 3.0.2 SMI-S 1.2

RHEL 3 and 4 (onES and AS)

Windows 2003(32-bit)

SLES10 (32-bit)

Chapter 2. Planning 35

Supported devices and actions

These tables list the storage devices and the actions you can perform on each withSystems Director.

Table 10. Storage management tasks and supported devices

LSI SAS controllersIBM BladeCenter SAS

Modules

FibreChannelSwitches(2/4/8 GB)

IBM System Storage DS® andN series

LegacyRaid

Controllers

Task

10641064e1068

1078InternalRAID(IR)

1078MegaRAID(MR)

Connectivitymodule

RAIDcontrollermodule

Brocade(2/4/8) andQlogic(2/4/8)

3K4K5KSystems

6000

N3600

DS3500

ServeRaid6/7/8/9andLSI 1030

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

Inventorycollection

Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes

Monitoring(alerts andstatus)

Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes

PhysicalTopology

No No No Yes Yes Yes Yes Yes Yes Yes No

LogicalTopology

Yes Yes Yes Yes Yes Yes Yes Yes No Yes No

Provisioning No No No No Yes Yes Yes Yes No No No

SAS zoning No No No Yes Yes No No No No No No

View andmanageattacheddevices

Yes Yes Yes Yes Yes No No No No No Yes

Configuration

Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes

UpdateInstallation

Yes Yes Yes Yes No No No No No No Yes

Troubleshooting

No No No Yes Yes No No No No No No

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

IBM StorwizeV7000

IBM SystemStorage DS8000 IBM XIV 2810, 2812 IBM SAN Volume Controller

Task

Discovery Yes Yes Yes Yes

Inventorycollection

Yes Yes Yes Yes

Monitoring (alertsand status)

Yes Yes Yes Yes

Physical Topology No No No No

Logical Topology No No No No

Provisioning No No No No

SAS zoning No No No No

View and manageattached devices

No No No No

Config uration Yes Yes No No

36 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

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

IBM StorwizeV7000

IBM SystemStorage DS8000 IBM XIV 2810, 2812 IBM SAN Volume Controller

UpdateInstallation

No No No No

Trouble shooting No No No No

RAID controller support

This table describes Storage Manager support of RAID controllers managed withvarious versions of Platform Agents in IBM Systems Director. The values in thistable assume you have performed a basic install, without manually addingadditional software to the agent.

In the table, a value of Yes means that Discovery, Inventory, Configuration, andAlerts are supported, unless otherwise noted.

Table 12. RAID controller support

IBM SystemsDirector Platform

agent version

IBM Systems Director version

6.1 6.1.1 and 6.1.2 6.2 and 6.2.1

5.20.31 or 5.20.32 Yes - Configuration is notsupported on the AdvancedRAID Controller (also calledMegaRAID Controller) only.

Yes - Configuration is not supported. Yes - Configuration is not supported.

6.1.1 or 6.1.2 Not available Yes Yes

6.2 Not available Not available Yes

Storage devices and IPv6 support

Storage device support in an IPv6 environment is described in the following table.

Table 13. Storage devices and IPv6 support

Storage device Device type IPv6 support

Legacy RAID Controllers ServeRAID versions 4/5/6/7/8/9 Full compliance

Internal RAID Controllers 1064, 1064e, 1068, 1078 IR/MR Full compliance

IBM BladeCenter SAS Modules SAS Connectivity Module (NSSM) Non-compliant (NSSM switches donot support IPv6)

RAIDed SAS Switch Module (RSSM) Not compliant (RSSM switches donot support IPv6)

Fibre Channel Switches (2GB/4GB) QLogic 2GB/4GB Partial compliance (QLogic Firmwareversion 7.4/7.8 or later supportsIPv6)

Brocade 2GB/4GB Full compliance

IBM System Storage DS series DS3100, DS3200, DS3300DS3400, DS3500DS4100, DS4300, DS4300 (DS4K)

Full complianceNote: Compliance statement does notinclude Engenio SMI Provider, whichwas not tested on the IBM SystemsDirector version 6.2 product.

DS5020 Full compliance

DS6K Not compliant

DS8K Not compliant

Chapter 2. Planning 37

Table 13. Storage devices and IPv6 support (continued)

Storage device Device type IPv6 support

IBM XIV 2810-A14, 2812-A14 Not compliant

IBM System Storage N series NS3600, N3700 Not compliant

IBM Storwize v7000 Not compliant

IBM SAN Volume Controller Not compliant

Storage restrictionsv 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 Any storage devices not listed in Table 10 on page 36 are not supported.v IBM BladeCenter S SAS RAID Controller Module provider is integrated with

IBM Systems Director 6.2 Platform Agent and is installed as a default with IBMSystems Director 6.2. If you want to perform a separate installation of the IBMBladeCenter S SAS RAID Controller Module provider, you must ensure that thecompatible IBM Systems Director Platform Agent is installed:– PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0

is compatible with the IBM Systems Director Core Component Services Level1 Platform Agent

– PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.2.0is compatible with IBM Systems Director 6.2 Platform Agent

v IBM System Storage DS8000 requires IBM Systems Director Storage Control 4.2.1or IBM TotalStorage Productivity Center 4.2.1 or higher.

v IBM XIV requires IBM Systems Director Storage Control 4.2.1 or IBMTotalStorage Productivity Center 4.2.1 or higher.

v IBM System Storage SAN Volume Controller requires IBM Systems DirectorStorage Control 4.2.1 or IBM TotalStorage Productivity Center 4.2.1 or higher.

v IBM Storwize V7000 requires IBM Systems Director Storage Control 4.2.1 or IBMTotalStorage Productivity Center 4.2.1 (or higher).

Planning for IBM Systems Director Storage Control 4.2.1Use the information in this section to plan for using Storage Control.

Network requirementsIBM Systems Director requires certain ports to be available and certain networkprotocols to be installed in order to enable communication among IBM SystemsDirector components and between the management server and managed systems.In addition, network connectivity must exist between the management server andmanaged systems, and between the management server and the IBM SystemsDirector Web interface browser system.

Nameserver (DNS) requirements

Ensure that the nameserver is configured correctly. If the nameserver is notconfigured correctly, you will encounter problems and potential failure during IBMSystems Director installation.

The following conditions indicate that the nameserver is configured correctly:

38 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

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.

Note: Before you install IBM Systems Director Server, your system must have aDNS server correctly configured for the network environment.

All available portsIBM Systems Director processes require access to a number of ports in theinstallation and systems-management environment. If these ports are blocked by afirewall or used by another process, some IBM Systems Director functions mightnot 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 aresome important considerations to remember or some IBM Systems Directorfunctions 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) 5988 and 5989– (For SUSE Linux Enterprise Server and Red Hat Enterprise Linux) 15988 and

15989

Some firewalls might attempt to block these ports. Make sure that the IBMSystems Director software components can use these ports. If custom alternativeports 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 ofwhether HTTPS is turned on (SSL is enabled).

v If the CIMOM ports for a Platform Agent managed system are changed afterIBM Systems Director Server discovers the system, the system will change to anAgentless managed system in IBM Systems Director. To correct this change, youmust 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 Generic CIM clients should always check the IBM standard (primary) ports (forexample, 15988/15989) and the back-up generic ports (for example, 5988/5989).

v Windows firewall can interfere with discovery of managed systems runningWindows 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 updatepackages from IBM. If a proxy server is required, it must be configured to useBasic 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-directionalcommunication through these ports.

Chapter 2. Planning 39

v By default, IBM Systems Director uses a random source port for SLPcommunication through a firewall to a Remote Supervisor Adapter. The randomport causes problems when discovering the Remote Supervisor Adapter througha firewall because the Remote Supervisor Adapter responds using that randomport. To resolve this problem, open any unused or private port. Then, edit theslp.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 usedsource.port=49150

v Neither z/VM nor the MAP Agent add any additional ports to those alreadyprovided by IBM Systems Director for standard communication. Instead ofTCP/IP, z/VM communication APIs are used to communicate with the serversthat provide information to IBM Systems Director and to enact any changes toz/VM servers. The communication is by means of sockets and the AF_IUCVaddress family.

v For the TCP ports listed, the initiator opens a random port in the 1024-65535range and then connects to the listener on the port listed. The listener respondsby connecting to the original random port opened by the initiator.

v The Remote Control, Update Install, and the Agent Installation wizard tasks usesession support to increase data transmission. Session support within TCP/IPcauses data to flow through a nonreserved port that is different from the onethat IBM Systems Director typically uses for communication. Most firewalls willnot transmit the data through this other port.

v There are undocumented ports used by IBM Systems Director Server 6.2 andCommon Agent. Prior to the 6.2 release, random source ports were used bydefault. Starting with IBM Systems Director Server 6.2, the default source port isnow 14252 for both the server and agent.When firewalls are used to block traffic on unused ports, you must openadditional source ports in order for Service Locator Protocol (SLP) discovery towork. On both the server and the agent, the configured or default source portplus the next sequential 25 ports must be opened. You may need to open moreor fewer source ports, depending on the number of systems being discoveredconcurrently. Generally, if the discovery of many systems at a time is attemptedand fails, more source ports need be opened, up to a maximum of 75. Ifdiscovery is done for only a small number of systems at a time, fewer portsneed to be opened.The source port can be overridden on both the server and agent by configuringthe port in the slp.prop file.

Ports for IBM Systems Director Server:

IBM Systems Director processes require access to a number of ports on themanagement server. If these ports are blocked by a firewall or used by anotherprocess, some IBM Systems Director functions might not work.

Table 14. 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 (switchesand bridges)

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

40 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

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

Port TCP or UDP Direction Communication description

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, includingsystems managed by HMC and IVM

v SSH used by IBM Power systems to communicate withHMC/IVM

v Non-Windows Agentless managed systems

23 TCP, UDP Outbound Telnet communication with:

v Advanced management module, management module, RemoteSupervisor Adapter, and Remote Supervisor Adapter II

v BladeCenter I/O modules

v Updates

69 UDP Inbound TFTP communication with BladeCenter I/O modules (switchesand bridges)

80 TCP Outbound HTTP communication with:

v IBM Systems Director Web interface

v Advanced management module, management module, RemoteSupervisor Adapter, and Remote Supervisor Adapter II

v BladeCenter I/O modules

v IVM interface

v Update manager

81 TCP Outbound HTTPS communication with BladeCenter I/O modules (switchesand bridges)

135 TCP, UDP Outbound (Windows only) Software installation and remote accesscommunication with Platform Agent

137 TCP, UDP Outbound (Windows only) Communication with Agentless managed systemsusing Microsoft Windows DCOM

138 TCP, UDP Outbound (Windows only) Communication with Agentless managed systemsusing Windows DCOM

139 TCP, UDP Outbound (Windows only) Communication with Agentless managed systemsusing Windows Server Message Block (SMB)

161 UDP Outbound SNMP agent communication with:

v Advanced management module, management module, RemoteSupervisor Adapter, and Remote Supervisor Adapter II

v BladeCenter I/O modules

v Platform AgentNote: This port is used when the SNMP agent for the operatingsystem is configured.

v Agentless managed systemsNote: This port is used when the SNMP agent for the operatingsystem is configured.

162 TCP, UDP Outbound (TCP,UDP)

Inbound (UDP)

Simple Network Management Protocol (SNMP) trapcommunication with SNMP devices, including TCP for TivoliNetView® events. Examples of SNMP devices are advancedmanagement module, management module, Remote SupervisorAdapter, and Remote Supervisor Adapter II.

Chapter 2. Planning 41

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

Port TCP or UDP Direction Communication description

427 TCP, UDP Outbound andInbound

SLP communication with:

v Advanced management module, management module, RemoteSupervisor Adapter, and Remote Supervisor Adapter II

v Common Agent

v Platform Agent

v IBM Director Agent version 5.20

v Service Location Protocol (SLP) service agent or SLP directoryagent

443 TCP Outbound HTTPS communication with:

v IBM Systems Director Web interface

v Advanced management module and management module

v HMC Web interface

v Updates

445 TCP, UDP Outbound (Windows only) Open on Agentless and Platform Agent managedsystems for the following features:v Software installationv Remote access communicationv (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) unsecurecommunication with IPMI baseboard management controller(BMC) service processors

664 UDP Outbound Remote Management and Control Protocol (RMCP) securecommunication with IPMI BMC service processors

Random portin the1024-65535range

TCP Inbound v Random port range for communication between IBM SystemsDirector Server with Intelligent Platform Management Interface(IPMI) service processorsNote: You can specify a fixed port by modifying theasmDefinitions.properties file in the data directory.

v For the TCP ports listed, the initiator opens a random port inthe 1024-65535 range and then connects to the listener on theport listed. The listener responds by connecting to the originalrandom port opened by the initiator.

1433 TCP Outbound andInbound

Microsoft SQL Server databases

1521 TCP Outbound andInbound

Oracle® Database databases

1527 TCP Outbound andInbound

Apache Derby databases

2033 TCP Inbound Communication with the IBM Systems Director Launched Tasksprogram using IBM Systems Director interprocess communication(IPC)

2044 TCP Outbound andInbound

smcli command-line interfaceNote: This port number can be changed. See “Port configurationfor smcli.”

42 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

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

Port TCP or UDP Direction Communication description

3389 TCP Outbound andInbound

Remote Desktop Protocol, Remote Desktop Connection, or RemoteAccessor for full screen access to systems running Windows

4066 TCP Inbound Communication with the IBM Systems Director Launched Tasksprogram using IBM Systems Director interprocess communication(IPC) over SSL

5901 TCP Outbound andInbound

Virtual Network Computing (VNC), used by Remote Access

5988 TCP Inbound (Windows and Red Hat Enterprise Linux) CIM Server unsecureport

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

v HMC/IVM CIMOM

6641 TCP Inbound SAS switches

6988 TCP Inbound CIM listener

6989 TCP Inbound CIM listener

6090 TCP Outbound TCP Command Mode communication between IBM SystemsDirector Server and advanced management module, managementmodule, Remote Supervisor Adapter, and Remote SupervisorAdapter II

8421 TCP Inbound v (All operating system platforms) HTTP communication betweenIBM Systems Director Server and the IBM Systems Director Webinterface

v HTTP used by IBM Power systems to communicate with CIM

8422 TCP Inbound v (All operating system platforms) HTTPS communicationbetween IBM Systems Director Server and the IBM SystemsDirector 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

8475 TCP Outbound Non-SSL communication with the IBM i remote command anddistributed 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 anddistributed program call server job

9476 TCP Outbound SSL communication with the IBM i signon server job

Chapter 2. Planning 43

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

Port TCP or UDP Direction Communication description

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 isrestarted 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 RemoteSupervisor Adapter II

14247 UDP Inbound IBM Systems Director interprocess communication (IPC) with IBMDirector Agent 5.20

14248 UDP Outbound IBM Systems Director interprocess communication (IPC) with IBMDirector Agent 5.20

14251 UDP Inbound IBM Systems Director Server interprocess communication (IPC)support

14252 TCP, UDP Inbound,Outbound

Source port for SLP communication

There are undocumented ports used by IBM Systems DirectorServer 6.2 and Common Agent. Starting with IBM SystemsDirector Server 6.2, the default source port is now 14252 for boththe server and agent.

When firewalls are used to block traffic on unused ports, you mustopen additional source ports in order for Service Locator Protocol(SLP) discovery to work. On both the server and the agent, theconfigured or default source port plus the next sequential 25 portsmust be opened. You may need to open more or fewer sourceports, depending on the number of systems being discoveredconcurrently. Generally, if the discovery of many systems at a timeis attempted and fails, more source ports need be opened, up to amaximum of 75. If discovery is done for only a small number ofsystems at a time, fewer ports need to be opened.

The source port can be overridden on both the server and agent byconfiguring the port in the slp.prop file.

15988 TCP Inbound (Red Hat Enterprise Linux, SUSE Linux) CIM Server unsecure port

15989 TCP Inbound (Red Hat Enterprise Linux, SUSE Linux) CIM Server secure port

20000 TCP Inbound v CAS events

v Communication with VMwareNote: If you plan to manage systems running VMwareVirtualCenter, or VMware ESX Server, see the VMwaredocumentation to make sure port requirements are met:www.vmware.com/support/pubs/

50000 TCP Inbound,Outbound

IBM DB2 databases

61616 TCP Inbound,Outbound

JMS communication with IBM Systems Director Server unsecureport

61617 TCP Inbound,Outbound

JMS communication with IBM Systems Director Server secure port

44 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Ports for managed systems:

IBM Systems Director processes require access to a number of ports on managedsystems. Managed systems include Common Agent managed systems, PlatformAgent managed systems, and Agentless managed systems.

Table 15. Ports on managed systems

PortTCP orUDP Direction Communication description

22 TCP Inbound 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 withHMC/IVM

v Non-Windows Agentless managed systems

135 TCP, UDP Inbound (Windows only) Software installation and remote accesscommunication with Platform Agent

137 TCP, UDP Inbound (Windows only) Communication with Agentless managedsystems using Microsoft Windows DCOM

138 TCP, UDP Inbound (Windows only) Communication with Agentless managedsystems using Windows DCOM

139 TCP, UDP Inbound (Windows only) Communication with Agentless managedsystems using Windows Server Message Block (SMB)

161 UDP Inbound SNMP agent communication with:

v Advanced management module, management module,Remote Supervisor Adapter, and Remote Supervisor AdapterII

v BladeCenter I/O modules

v Platform AgentNote: This port is used when the SNMP agent for theoperating system is configured.

v Agentless managed systemsNote: This port is used when the SNMP agent for theoperating system is configured.

389 TCP Outbound Used for LDAP

427 TCP, UDP Outbound and Inbound SLP communication with:

v Advanced management module, management module,Remote Supervisor Adapter, and Remote Supervisor AdapterII

v Common Agent

v Platform Agent

v IBM Director Agent version 5.20

v Service Location Protocol (SLP) service agent or SLPdirectory agent

445 TCP, UDP Inbound (UDP) (Windows only) Open on Agentless and Platform Agentmanaged systems for the following features:v Software installationv Remote access communicationv (Agentless-managed systems only) Inventory collection

Chapter 2. Planning 45

Table 15. Ports on managed systems (continued)

PortTCP orUDP Direction Communication description

5988 TCP Inbound (Windows and Red Hat Enterprise Linux) CIM Server unsecureport

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

v HMC/IVM CIMOM

6988 TCP Inbound CIM listener

6989 TCP Outbound CIM listener

9510 TCP Inbound Communication with Common Agent and CAS Web services

9550 TCP Both Used by IBM Systems Director Storage Control 4.2.1 as a serverport

14247 UDP Inbound IBM Systems Director interprocess communication (IPC) withIBM Director Agent 5.20

14248 UDP Outbound IBM Systems Director interprocess communication (IPC) withIBM Director Agent 5.20

15988 TCP Inbound v (For SUSE Linux Enterprise Server) CIM Server (alternativeunsecure port) communication with Platform Agentmanaged system

v Service processor communication with SUSE LinuxEnterprise Server 10.

v CIM Server (alternative unsecure port) communication withPlatform Agent managed system

15989 TCP Inbound (For SUSE Linux Enterprise Server) CIM Server (alternativesecure port) communication with Platform Agent managedsystem

20000 TCP Outbound v CAS events

v Communication with VMwareNote: If you plan to manage systems running VMwareVirtualCenter, or VMware ESX Server, see the VMwaredocumentation to make sure port requirements are met:www.vmware.com/support/pubs/

49153 TCP Inbound Used for SNMP alert

Security requirementsIBM Systems Director Server supports several products to house the registry usedfor system security.

User registry products and types

One of the following locations must contain the registry that IBM Systems Directoruses for user authentication:

Operating systemThe local operating system user registry is the default registry used by IBMSystems Director security.

LDAP IBM Systems Director includes Lightweight Directory Access Protocol(LDAP) authentication support. LDAP support is disabled by default. Thefollowing LDAP servers are supported:

46 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

v IBM Tivoli Directory Serverv Microsoft Active Directoryv OpenLDAP

Active directoryThe active directory, which is the same as the Microsoft Active Directory,acts as an LDAP server or domain controller. It supports the followingtypes of users and groups:v Globalv Domainv Localv Trusted

Ensure that the IBM Systems Director server is a member of the activedirectory domain.

Firmware and device drivers requirementsBefore you install IBM Systems Director, make sure the firmware and devicedrivers are up-to-date.

For more information, see and .

Operating system and software requirementsIBM Systems Director has specific requirements for operating systems andsoftware. IBM Systems Director provides support for operating systems, databaseapplications, virtualization software, Web browsers, and screen readers.

Supported operating systemsThis section lists the operating systems on which IBM Systems Director Server,Common Agent, and Platform Agent are supported. This support can vary byversion, release, and update. Make sure you review the supported operatingsystems for the version of IBM Systems Director in your environment.

Operating system support for Systems Director 6.1.x is listed in the Supportedoperating systems topic in the IBM Systems Director 6.1.x information center.

Operating systems supported by IBM Systems Director 6.2.1:

IBM Systems Director 6.2.1 provides support for many operating systems.However, support varies depending on the selected hardware and IBM SystemsDirector component.

IBM Systems Director supports only products that are currently supported by theowners or manufacturers of that product. If a product is no longer supported by itsowner or manufacturer, it is implicit that IBM Systems Director also no longersupports that product.

Starting in version 6.1, IBM Systems Director provides a Web interface for use withIBM Systems Director Server. IBM Director Console is no longer required.However, some tasks in the Web interface require the IBM Systems DirectorLaunched Tasks program. For information about the IBM Systems DirectorLaunched Tasks program and the tasks that require it, see “Launched tasks and theIBM Systems Director Launched Tasks program.” For operating-system support,see “Operating systems supported by the IBM Systems Director Launched Tasksprogram.”

Chapter 2. Planning 47

Unless stated otherwise, IBM Systems Director provides agentless support for alloperating systems listed in this topic.

Important: Installation of IBM Systems Director Server on third-party hardware isnot supported. Licensing requires that it be installed on IBM hardware only.

Table 16. VMware ESX Server versions supported by IBM Systems Director on System x systems; IBM andthird-party x86-based systems

Operating system

IBMSystemsDirectorServer

CommonAgent

PlatformAgent

VMware ESX Server, versions 3.5, 3.5.1, 3.5.2, 3.5.3, 3.5.4, and 3.5.5 ConsoleNotes:

1. IBM Systems Director 6.1 Common Agent and IBM Director Core Services5.20.3, Service Update 1 or Service Update 2, support VMware ESX Serverversions 3.5, 3.5.1, 3.5.2, 3.5.3, and 3.5.4.

2. IBM Systems Director 6.2.1 Common Agent with IBM Systems Director 6.2.1Platform Agent supports VMware ESX Server versions 3.5, 3.5.1, 3.5.2, 3.5.3,3.5.4, 3.5.5. Restriction: You will no longer be able to manage the RSAin-band. You can manage it out-of-band by connecting it to the network anddiscovering it with IBM Systems Director.

X X

VMware ESX Server, versions 4.0, 4.0.1, 4.0.2, 4.1, 4.1.1 ConsoleNotes:

1. IBM Systems Director 6.2.1 Common Agent with IBM Systems Director 6.2.1Platform Agent supports VMware ESX Server versions 4.0, 4.0.1, 4.0.2, 4.1,and 4.1.1. Restriction: You will no longer be able to manage the RSA in-band.You can manage it out-of-band by connecting it to the network anddiscovering it with IBM Systems Director.

2. You must turn off VMware ESX Server, version 4.0.x SLP, before installingIBM Systems Director 6.1.1 or later Common Agent.

3. VMware ESX Server 4.x is 64-bit, and is supported by way of 32-bitcompatibility mode only.

X X

Table 17. Support for guest operating systems

Operating system

IBMSystemsDirectorServer

CommonAgent

PlatformAgent

Supported guest operating systems are those that are supported by both IBMSystems Director and the hypervisor. In other words, if the following conditionsare true:

1. the given OS platform supported is documented in this topic

2. the given OS platform is supported as a guest OS by a hypervisor

3. the hypervisor is supported by IBM Systems Director

then IBM Systems Director support of that OS platform extends to running it as aguest OS on that hypervisor.

See also the hypervisor product documentation for a list of supported operatingsystems.

X X X

48 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 18. AIX versions supported by IBM Systems Director on IBM Power systems

Operating system

IBMSystemsDirectorServer

CommonAgent

PlatformAgent

IBM AIX Version 5.3:

v AIX 53 TL06 SP09 or later SP levels

v AIX 53 TL07 SP06 or later SP levels

v AIX 53 TL08 SP04 or later SP levels

v AIX 53 TL09 or later TL levels

Note:

1. Agentless support includes only discovery, limited remote access, a limitedsubset of the Agent Installation Wizard task, and the ability to launch the AIXManagement Console for IBM AIX Version 5.3 agents.

2. For IBM Systems Director Server or Common Agent support provided byIBM AIX Version 5.3, newer TLs and Service Packs will be supported on theday of their general availability (GA).

3. Common Agent is installed with AIX ; it is started by default.

X X

IBM AIX Version 6.1:

v AIX 61 TL00 SP07 or later SP levels

v AIX 61 TL01 SP03 or later SP levels

v AIX 61 TL02 or later TL levels

Note:

1. Agentless support includes only discovery, limited remote access, a limitedsubset of the Agent Installation Wizard task, and the ability to launch the AIXManagement Console for IBM AIX Version 6.1 agents.

2. For IBM Systems Director Server or Common Agent support provided byIBM AIX Version 6.1, newer TLs and Service Packs will be supported on theday of their general availability (GA).

3. Common Agent is installed with AIX ; it is started by default.

X X

IBM AIX Version 7.1Note:

1. Agentless support includes only discovery, limited remote access, a limitedsubset of the Agent Installation Wizard task, and the ability to launch the AIXManagement Console for AIX Version 7.1 agents.

2. For IBM Systems Director Server or Common Agent support provided by AIXVersion 7.1, newer TLs and Service Packs will be supported on the day oftheir general availability (GA).

3. Common agent is installed with AIX operating system; it is started by default.

X X

Operating systems supported by IBM Systems Director 6.2.0:

IBM Systems Director 6.2.0 provides support for many operating systems.However, support varies depending on the selected hardware and IBM SystemsDirector component.

Starting in version 6.1, IBM Systems Director provides a Web interface for use withIBM Systems Director Server. IBM Director Console is no longer required.However, some tasks in the Web interface require the IBM Systems DirectorLaunched Tasks program. For information about the IBM Systems DirectorLaunched Tasks program and the tasks that require it, see “Launched tasks and the

Chapter 2. Planning 49

IBM Systems Director Launched Tasks program.” For operating-system support,see “Operating systems supported by the IBM Systems Director Launched Tasksprogram.”

Unless stated otherwise, IBM Systems Director provides agentless support for alloperating systems listed in this topic.

Important: Installation of IBM Systems Director Server on third-party hardware isnot supported. Licensing requires that it be installed on IBM hardware only.

Table 19. Support for guest operating systems

Operating system

IBMSystemsDirectorServer

CommonAgent

PlatformAgent

Supported guest operating systems are those that are supported by both IBMSystems Director and the hypervisor. See the hypervisor product documentationfor a list of supported operating systems.

X X X

Table 20. AIX versions supported by IBM Systems Director on IBM Power systems

Operating system

IBMSystemsDirectorServer

CommonAgent

PlatformAgent

IBM AIX Version 5.3:

v AIX 53 TL06 SP09 or later SP levels

v AIX 53 TL07 SP06 or later SP levels

v AIX 53 TL08 SP04 or later SP levels

v AIX 53 TL09 or later TL levels

Note:

1. Agentless support includes only discovery, limited remote access, a limitedsubset of the Agent Installation Wizard task, and the ability to launch the AIXManagement Console for IBM AIX Version 5.3 agents.

2. For IBM Systems Director Server or Common Agent support provided byIBM AIX Version 5.3, newer TLs and Service Packs will be supported on theday of their general availability (GA).

3. Common Agent is installed with AIX ; it is started by default.

X X

IBM AIX Version 6.1:

v AIX 61 TL00 SP07 or later SP levels

v AIX 61 TL01 SP03 or later SP levels

v AIX 61 TL02 or later TL levels

Note:

1. Agentless support includes only discovery, limited remote access, a limitedsubset of the Agent Installation Wizard task, and the ability to launch the AIXManagement Console for IBM AIX Version 6.1 agents.

2. For IBM Systems Director Server or Common Agent support provided byIBM AIX Version 6.1, newer TLs and Service Packs will be supported on theday of their general availability (GA).

3. Common agent is installed with AIX operating system; it is started by default.

X X

50 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 20. AIX versions supported by IBM Systems Director on IBM Power systems (continued)

Operating system

IBMSystemsDirectorServer

CommonAgent

PlatformAgent

IBM AIX Version 7.1:Note:

1. Agentless support includes only discovery, limited remote access, a limitedsubset of the Agent Installation Wizard task, and the ability to launch the AIXManagement Console for IBM AIX Version 7.1 agents.

2. For IBM Systems Director Server or Common Agent support provided by AIXVersion 7.1, newer TLs and Service Packs will be supported on the day oftheir general availability (GA).

3. Common agent is installed with AIX operating system; it is started by default.

X X

Operating systems supported by the IBM Systems Director Launched Tasksprogram:

Starting in version 6.1, IBM Systems Director provides a Web interface for use withIBM Systems Director Server. IBM Director Console is no longer required.However, some tasks in the Web interface require the IBM Systems DirectorLaunched Tasks program. For information about the IBM Systems DirectorLaunched Tasks program and the tasks that require it, see “Launched tasks and theIBM Systems Director Launched Tasks program.”

Important: The launched-tasks feature in IBM Systems Director requires Java WebStart (JWS).

The following operating systems are supported by the IBM Systems DirectorLaunched Tasks program on IBM Power systems:v IBM AIX Version 5.3v IBM AIX Version 6.1

Virtualization software supported by IBM Systems DirectorThis topic lists the supported virtualization software for IBM Systems Director.

Hardware Management Console (HMC)

v Hardware Management Console Version 7 R3.3.0 SP2, PTF MH01146; Version 7R3.4.0 and SPs; Version 7 R3.5.0 SP1; Version 7 R7.1.0, R7.1.1, R7.2.0

Notes:

– It is recommended that you always apply the latest available service pack.The minimum service pack prerequisite is listed here

– IBM Systems Director 6.2.x provides IPv6 support for Hardware ManagementConsole V7 R7.1.0 SP2 and later.

Power Systems Firmware

v Power Systems Firmware: POWER51, POWER6, and POWER7

Notes:

– 1Power Systems firmware updates for POWER5, via the Power Systemsfirmware Update manager extension, can only be installed for SF240_338 orlater.

Chapter 2. Planning 51

– It is recommended that you always apply the latest firmware level. Theminimum firmware level is listed here.

Integrated Virtualization Manager (IVM)

v Integrated Virtualization Manager Version 1.5.2.1 and later fix packs; Version2.1.0.10, fix pack 20.1 and later fix packs; Version 2.1.1 and later

Notes:

– IBM Systems Director VMControl requires that Integrated VirtualizationManager be at a minimum version of 2.1.0.10.

– It is recommended that you always apply the latest available service pack.The minimum service pack prerequisite is listed here.

Virtual I/O Server

v Virtual I/O Server Version 2.1.0.10, fix pack 20.1 and later fix packs, Version 2.1.1and later, and Version 2.2

Notes:

– The Common Agent is installed with Virtual I/O Server 2.1.1 and later; it isnot started per default. For more information, see the IBM Systems DirectorBest Practices wiki - "IVM and VIOS topics".

– IBM Systems Director version 6.2.x provides IPv6 support for Virtual I/OServer 2.1.3 and later.

Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions withHyper-V role enabled

v Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions withHyper-V role enabled, Release 2

v Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions withHyper-V role enabled (supports Service Packs 1 and 2)

Notes:

1. Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions withHyper-V role enabled, Release 2, Service Pack 1, is also supported by IBMSystems Director 6.2.1.2.

2. Only IBM Systems Director 6.1.2 or 6.2.x Common Agent and 6.1.2 or 6.2.xPlatform Agent support Windows Server 2008, Enterprise, Standard, andDatacenter x64 Editions with Hyper-V role enabled, Release 2.

3. Support for Windows Server 2008, Enterprise, Standard, and Datacenter x64Editions with Hyper-V role enabled is based on coexistence testing only.

4. All Windows Server 2008 support is for Full install only.

VMware ESX Server

v VMware ESX Server 3.5.x Service Consolev VMware ESX Server 4.0.x Service Consolev VMware ESX Server 4.1 Service Consolev VMware ESX Server 4.1.1 Service Console

Note: VMware ESX Server 4.x is 64-bit, and is supported by way of 32-bitcompatibility mode only.

VMware ESXi

52 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

v VMware ESXi versions 3.5 Update 2, 3, 4, and 5, under the control of VMwareVirtualCenter

v VMware ESXi versions 4.0 Update 1 and 2, under the control of VMwarevCenter

v VMware ESXi versions 4.1 Update 1, under the control of VMware vCenter

Note: Firmware update types other than direct IMM, UEFI, PBDSA, and FPGA arenot supported on systems running VMware ESXi.

VMware VirtualCenter

v VMware VirtualCenter V2.5.x

VMware vCenter

v VMware vCenter 4.x

Xen virtualization

v Red Hat Enterprise Linux 5.1, with Xen 3.1v Red Hat Enterprise Linux 5.2, with Xen 3.1.2v SUSE Linux Enterprise Server 10, with the Xen Virtual Machine Host Server

option installed (XEN 3.0)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

Ensure that the following PTFs for z/VM are installed:

Table 21. z/VM 5.4 and 6.1 PTFs

APAR number Component namePTF number forz/VM 5.4

PTF number forz/VM 6.1

VM64514 CMS UM32505 Not required

VM64515 CMS UM32503 Not required

VM64516 CMS UM32521 Not required

VM64517 CMS UM32522 Not required

VM64596 CMS UM32693 Not required

VM64677 CMS UM32765 UM32766

VM64595 DIRM UV61088 Not required

VM64762 DIRM UV61099 UV61100

VM64813 CMS Not required Required. See theAPAR for the PTFnumber.

Note: z/VM 6.1 supports host and virtual server performance related monitorswith APAR VM64813. However, host and virtual server performance relatedmonitor support is not available for systems running z/VM 5.4.

Chapter 2. Planning 53

Related reference

Microsoft Virtual Server Web page

VMware ESX Server documentation

VMware VirtualCenter documentation

VMware Infrastructure documentation

z/VM PDF files

IBM Systems Director Best Practices Wiki - IVM/VIOS

Virtualization software supported on Agentless managedsystemsIBM Systems Director provides support for the following virtualization softwareproducts on Agentless managed systems.

Table 22. Integrated Virtualization Manager versions supported by IBM Systems Director onAgentless managed systems

Operating system

Integrated Virtualization Manager Version 1.5.2.1 and later fix packs

Integrated Virtualization Manager Version 2.1.0.10, fix pack 20.1 and later fix packs

Integrated Virtualization Manager Version 2.1.1 and later

Table 23. VMware ESXi versions supported by IBM Systems Director on Agentlessmanaged systems

Operating system

VMware ESXi versions 3.5, 3.5.2, 3.5.3, 3.5.4, and 3.5.5

VMware ESXi versions 4.0, 4.0.1, 4.0.2, 4.1, and 4.1.1

Supported Web browsersStarting in version 6.1, IBM Systems Director provides a Web interface for use withIBM Systems Director Server. The Web interface requires that you use a supportedWeb browser.

The following Web browsers are supported by IBM Systems Director for use withthe IBM Systems Director Web interface:v Firefox, version 3.6v Firefox, version 3.5v Firefox, version 3.0v Microsoft Internet Explorer, version 8.0v Microsoft Internet Explorer, version 7.0

Tip: If Firefox rejects a self-signed certificate and does not give you and option toadd an exception directly in the alert box, you can add the exception by selectingTools > Options > Advanced > Encryption > View Certificates. After you clickView Certificates, the Certificate Manager window opens. In the CertificateManager window, select the Servers tab and highlight the Certificate Name for

54 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

your IBM Systems Director Server. Click Add Exception.... The Add SecurityException window opens. Verify the information in the Location field and clickConfirm Security Exception.

Supported screen readersThe IBM Systems Director Web interface provides support for JAWS version 9.0.

Supported database applicationsIBM Systems Director Server provides a default database, Apache Derby, that isconfigured to store inventory data for the discovered systems in the environment.You can either use Apache Derby or configure any of the other supported databaseapplications, which are IBM DB2, Microsoft SQL Server, or Oracle® Database.

Database installation types

Depending on the database application selected and the operating system of themanagement server, the database management system (DBMS) might beembedded, local, or remote. The three installation types are described below.

Embedded DBMSThe DBMS is installed on the management server as part of the IBMSystems Director Server installation, and shares the Java Virtual Machinewith IBM Systems Director.

Local DBMSThe DBMS is installed on the management server on which IBM SystemsDirector Server is installed.

Remote DBMSThe 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 additionalinformation about these installation types.

Database versions supported by IBM Systems Director Server

The following table lists the database versions supported by IBM Systems DirectorServer on different management servers and provides information about whetherthe database server is embedded or can be installed locally or remotely.

Note: The database versions that are listed represent both the database server andthe database client where applicable.

Table 24. Database versions supported by IBM Systems Director

Database Supported database versions AIX Linux Windows

Apache Derby v V10.5.3.1 (included with IBMSystems Director Server on AIX ,Linux, and Windows)

Embedded Embedded Embedded

Chapter 2. Planning 55

Table 24. Database versions supported by IBM Systems Director (continued)

Database Supported database versions AIX Linux Windows

IBM DB2 v Express version 9v Version 9.1 with Fix Pack 4 or

laterv Version 9.5 with Fix Pack 1 or

laterv Version 9.7 with Fix Pack 1 or

later

Notes:

1. An IBM DB2 Version 9.5 or laterclient is required.

2. A 64-bit client is required toaccess an IBM DB2 databasefrom 64-bit IBM Systems DirectorServer.

Local or remote Local or remote Local or remote

Microsoft SQLServer

v Microsoft SQL Server 2005 withService Pack 3

v Microsoft SQL Server 2008 withService Pack 1

Note: Requires Microsoft SQLServer JDBC Driver 2.0 or later.

— — Local or remote

v Microsoft SQL Server 2005Express Edition with Service Pack2

v Microsoft SQL Server 2008Express

Note: Requires Microsoft SQLServer JDBC Driver 2.0 or later.

— — Local

Oracle® Database v Version 9.2v Version 10g release 1 (10.1.0.3 or

later)v Version 10g release 2v Version 11g release 2

Notes:

1. Oracle Cluster configuration isnot currently supported.

2. A 64-bit client is required toaccess an Oracle® Databasedatabase from 64-bit IBMSystems Director Server.

Local or remote Local or remote Local or remote

IBM Systems Director task support by operating system andagent levels

Some IBM Systems Director tasks are supported on certain operating systems oronly on Platform Agent managed systems or Common Agent managed systems.For tasks whose support is not affected in this way, see “IBM Systems Director tasksupport not affected by operating systems.”

Support for IBM Systems Director tasks can vary depending on the followingitems:

56 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

v The system or hardware device model (the resource)v The operating system that is installed on a resourcev The service processor installed in the managed systemv The level of the device drivers that are installed on the managed system

Attention: The device drivers that are available for a managed system dependon the service processor and operating system that are installed on the managedsystem.

v The level of IBM Systems Director support installed on the system or device. InTable 25, 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 supportedby IBM Director Agent version 5.20. However, support can vary for tasks thatupdate systems or provide cross-platform support:- 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 IBMDirector Agent version 5.20. All other types of updates are supported byCommon Agent only.

- (Update manager) Updates on AIX , Linux on Power Systems, and Linuxfor System z are available only with Common Agent. The ability todistribute Linux updates is only available for Common Agent on Linux.

- (Virtualization manager) IBM Director Agent version 5.20 requires aseparate download and installation of the Virtualization Manager extension.

Table 25. IBM Systems Director task support across operating systems

Task

Operating systems

AIX IBM i Linux

MicrosoftVirtualServer VMware Windows

Command Automation IBM SystemsDirectorServer, Level2

Level 2 IBM SystemsDirectorServer, Level2

IBM SystemsDirectorServer, Level2

Event Log IBM SystemsDirectorServer, Level2

Levels 1, 2 IBM SystemsDirectorServer,Levels 1, 2

Levels 1, 2 Levels 01, 1,2

IBM SystemsDirectorServer,Levels 1, 2

File Transfer IBM SystemsDirectorServer, Level2

Level 2 IBM SystemsDirectorServer, Level2

Level 2 Level 22 IBM SystemsDirectorServer, Level2

Chapter 2. Planning 57

Table 25. IBM Systems Director task support across operating systems (continued)

Task

Operating systems

AIX IBM i Linux

MicrosoftVirtualServer VMware Windows

Inventory (hardware)3 IBM SystemsDirectorServer, Level2

Levels 1, 2 IBM SystemsDirectorServer,Levels 0, 1,24

Levels 0, 1, 2 Levels 01, 1,2

IBM SystemsDirectorServer,Levels 0, 1,24

Inventory (software) IBM SystemsDirectorServer,Levels 0, 2

Levels 0, 1,25

IBM SystemsDirectorServer,Levels 0, 1, 2

Levels 0, 1, 2 Levels 0, 1, 2 IBM SystemsDirectorServer,Levels 0, 1, 2

Problems (formerlyHardware Status)6, 20

Level 2 Level 2 7 Levels 1, 2 8, 7 Levels 1, 2 9 Levels 1, 2 10 Levels 1, 2

Process Management IBM SystemsDirectorServer, Level2

Level 2 IBM SystemsDirectorServer, Level2

Level 2 11 Level 2 11 IBM SystemsDirectorServer, Level2

Remote Control IBM SystemsDirectorServer,Levels 0, 2

IBM SystemsDirectorServer,Levels 0, 1, 2

Level 2 Levels 0, 1,212

IBM SystemsDirectorServer,Levels 0, 1, 2

Remote Command Line IBM SystemsDirectorServer,Levels 0, 2

Levels 0, 1, 2 IBM SystemsDirectorServer,Levels 013,113, 2

Level 2 Levels 0, 1, 2 IBM SystemsDirectorServer, Level2

Resource Monitors IBM SystemsDirectorServer, Level2

Levels 1, 2 IBM SystemsDirectorServer,Levels 1, 2

Console only14

Console only14

IBM SystemsDirectorServer,Levels 1, 2

Storage Manager IBM SystemsDirectorServer

IBM SystemsDirectorServer,Levels 1,28, 15

Levels 1, 2 Levels 1, 2 IBM SystemsDirectorServer,Levels 1, 2 16

Update Manager IBM SystemsDirectorServer,Levels 217

Levels 1, 218 IBM SystemsDirectorServer,Levels 0, 1,217

Levels 1, 2 19 Levels 1, 219 IBM SystemsDirectorServer,Levels 0, 1, 217

Notes:

1. Agentless-managed system support is available for VMware ESX Server 3ionly.

2. File systems that are displayed for the guest operating system are limited tofile systems within its virtual disk.

3. Inventory data provided can vary among Agentless, Platform-Agent, andCommon-Agent managed systems.

4. Hardware-platform-specific data is unavailable for hardware inventory.5. Software Catalog Signatures not supported

58 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

6. Unless otherwise indicated, this task is supported (although the support mightbe limited) by:v Out-of-band notifications generated by the service processorv CIM indications generated by Platform Agent or Common Agent

7. IBM BladeCenter JS21 and JS22 only: Out-of-band notifications generated by aservice processor only.

8. Not supported on System z systems.9. Limited supported for Problems (formerly hardware status) in levels 1 and 2

of Microsoft Virtual Server.10. VMware support for the Problems task has the following limitations:

v No support for Platform Agent or Common Agent on VMware ESX Server3i (Embedded and Installable Editions) although enhanced Agentlesssupport 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 issystem-specific).

11. Supported on guest operating systems only.12. Supported on Windows guest operating systems only.13. Supported for Linux on Power Systems only.14. Limited support provided by virtualization manager.15. Not supported for Linux on Power Systems.16. The IBM BladeCenter SAS RAID Controller Module function is not supported

on Windows Server 2008.17. For detailed information about hardware and operating system support

provided by update manager, see “Supported updates.”18. On IBM i 5.4 or later, update manager support is provided for IBM Director

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

Systems Director agent updates only.20. Some important considerations for IBM Systems Director, versions 6.1.1 or

later, Platform Agents:v Customers with BMC and IMM service processors should update to the

6.1.xPlatform Agent.v Customers with RSA service processors should continue to use the IBM

Director Core Services version 5.20 (or any update release version of 5.20,such as 5.20.3).– The 6.1.x Platform Agent will block updates on IBM Director Core

Services version 5.20 systems and RSA service processors. Therefore, ifyou want to install the 6.1.x Platform Agent, you must first uninstall IBMDirector Core Services version 5.20 (or any update release version of 5.20,such as 5.20.3). Restriction: You will no longer be able to manage theRSA in-band. You can manage it out-of-band by connecting it to thenetwork and discovering it with IBM Systems Director.

Chapter 2. Planning 59

Related concepts

Supported updates

IBM Systems Director task support not affected by operatingsystems

Support for the tasks listed in this section does not depend on the operating systemrunning on the system. Event Automation Plans, Discovery, Security, Scheduler,and Resource Explorer are features of IBM Systems Director and their support doesnot depend on any resource other than the management server. For informationabout tasks whose support is affected by the operating system, the degree of agentsupport, or both, see “IBM Systems Director support by operating systems andagents.”

The following tasks have specific support statements:

Configuration ManagerThis 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 Powersystems. The operating system running on the system does not affect thesupport of this task. Configuration Manager performs IP configurationusing out-of-band communication.

Power On/OffSupport for this task can be provided by the service processor installed inthe system, the Wake on LAN feature, or the operating system. Thesupport varies by hardware platform. For detailed support information, seethe following topics:v “Managing power state settings on IBM Power systems”

SNMP BrowserThis task is supported on any system or device that runs SNMP.

IBM Systems Director task support for BladeCenter productsIBM Systems Director tasks provide support for BladeCenter products. The supportcan 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 ormore network devices (previously called switches, up to a total of four), and oneor 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 chassishas one or two management modules that contain a service processor. IBMSystems Director discovers the chassis and gathers information from the chassis byway of the management module. You cannot install Common Agent or PlatformAgent on the chassis.

The network device is an SNMP device, and IBM Systems Director considers thenetwork device to be a managed device.

IBM Systems Director can gather some information from a blade server beforeCommon Agent or Platform Agent is installed on the blade server. The informationis gathered from the blade server by way of the chassis management module. Inthe IBM Systems Director Web interface, the blade server is represented by a

60 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

physical platform managed object. However, after you install Common Agent orPlatform Agent on the blade server, it is a managed system, and the features andfunctions that you can use on the blade server are comparable to those that youcan 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 followingtable for a list of IBM Systems Director tasks and information about whether youcan use a task on the chassis, network device, or a blade server without CommonAgent or Platform Agent installed. Unless otherwise noted in this documentation, atask behaves the same for blade servers as for any managed system.

Note: When Common Agent or Platform Agent is installed on a blade server, thesupported tasks depend on the operating system that is installed on the bladeserver.

Table 26. IBM Systems Director task support for BladeCenter products

Tasks and subtasks Chassis Networkdevice

Blade server without Common Agent orPlatform Agent installed

Configuration Manager Yes Yes 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 Yes 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 isavailable 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 productsIBM Systems Director provides limited task support for Storage products.

Supported tasks and features for third-party x86-basedsystems

This section lists the IBM Systems Director tasks and features that are supportedon x86 systems other than IBM hardware. Support can vary depending on whetherthe system uses Common Agent or no agent.

Notes:

1. IBM Systems Director Platform Agent is not supported on third-party x86-basedsystems.

2. If a task or feature appears to work on some third-party x86-based systems, butthe task or feature is not listed as supported, do not assume that the task orfeature is supported.

3. All of these tasks and features are supported on IBM x86-based systems thatare Common Agent managed systems.

Chapter 2. Planning 61

Table 27. Supported tasks and features for third-party x86-based systems

Task or feature

Third-party x86-based systems

Agentless support Common Agent support

Discovery (basic) Yes Yes

Discovery (advanced) Yes Yes

Request access Yes Yes

Collect and view inventory Yes 1 Yes 1

View system properties Yes Yes

Dynamic groups Yes Yes

View problems and events Yes 2 Yes 2

Event Automation Plans No Yes 2

Event filters Yes Yes

Generate events indicatingonline and offline state

No No

Health summary No Yes 3

Common monitors (a subsetof monitors)

No Yes

Thresholds No Yes

Common Agent installation(manual)

Yes Not applicable

Common Agent installation(remote)

No Not applicable

RPM installation (remote) forLinux on x86 systems only

No Not applicable

1. Some hardware-based inventory might be missing.

2. Only events provided by way of the operating system, thresholds, and SNMP.

3. Only information provided by way of the operating system and thresholds.

Translations provided by IBM Systems DirectorIBM Systems Director is translated into many languages.

IBM Systems Director Server, IBM Systems Director Web interface, Common Agent,and Platform Agent are all translated into the following set of languages:v Brazilian Portuguesev Chinese (simplified)v Chinese (traditional)v Englishv Frenchv Germanv Italianv Japanesev Koreanv Spanish

Notes:1. The graphical user interface is translated in all of the listed languages.2. Some or all of the help system might not be translated in some languages.

62 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

3. The most recent information might not be available in the translated versions ofthe documentation. For the latest information, see the English version of theinformation center. To do so, in your Web browser set your language preferenceto English. Then, open or refresh the IBM Systems Director information center.

4. If a discrepancy exists between the translated and the English versions of thedocumentation, the English-language version is assumed to have the correctcontent.

5. If you are viewing IBM Systems Director in a language other than those listedhere, you may see a combination of that language and English.

IBM Systems Director Pre-Installation UtilityThe IBM Systems Director Pre-Installation Utility scans the local system to identifypotential problems that could prevent IBM Systems Director from installingsuccessfully. The utility does not scan for device driver or firmware requirements.

The IBM Systems Director Pre-Installation Utility is available on the IBM SystemsDirector installation media.

Some of the checks performed by the IBM Systems Director Pre-Installation Utilityinclude:v Runtime authenticationv OS compatibilityv Host architecturev Processorsv Disk space availablev Memory availablev Software requiredv Port availabilityv Promotion validityv Migration informationv Performance informationv Username checkv RSA checkv Paging size checkv File limit check (AIX only)v SELinux check (Linux only)v Intelligent Platform Management Interface (IPMI) Check (Linux only)v Locale check (Linux only)v Short name (8.3 names) check (Windows only)

The IBM Systems Director Pre-Installation Utility generates reports and displaysthe results in the command window or the default browser. Refer to thereadme.txt file on the installation media for more information about runtimeoptions, the reports that are generated, and return codes.

Running the IBM Systems Director Pre-Installation Utility on AIXand LinuxUse these instructions to run the IBM Systems Director Pre-Installation Utility onAIX or Linux.

Chapter 2. Planning 63

To start the IBM Systems Director Pre-Installation Utility from the installationmedia, complete the following steps:1. Insert the DVD into the DVD-ROM drive.2. If the DVD does not automount, type the following command and press Enter:

mount -v cdrfs -o ro /dev /mnt

where dev is the specific device file for the block device and mnt is the mountpoint of the drive.

3. To change to the directory in which the installation script is located, type thefollowing command and press Enter:cd /dvd_mnt/checkds/

where dvd_mnt is the mount point of the DVD media.4. Type following command and press Enter:

./checkds.sh

The IBM Systems Director Pre-Installation Utility starts.5. Reports are generated and results are displayed in the command window or

the default browser. Refer to the /checkds/readme.txt file for more informationabout checkds.sh options, the reports that are generated, and return codes.

IPv6 complianceIBM Systems Director version 6.2 is IPv6 compliant.

Starting with version 6.2, IBM Systems Director is compliant with Internet Protocolversion 6 (IPv6). As an IPv6-compliant application, IBM Systems Director supportsthe ability to discover and manage resources using both IPv4- and IPv6-addressformats. IBM Systems Director is a software application, so it does not implementany portion of the IP stack. In a situation where an IP address selection orspecification is required, it is handled in a protocol-neutral way if possible. IBMSystems Director utilizes the underlying operating system on which it runs or thehost that it manages to provide an IP implementation.

In a network configured to connect with either or both IPv4 or IPv6 hosts,interoperability between hosts is based on the available IP-protocol stacks. Thefollowing matrix shows interoperability between IBM Systems Director Server andmanaged resources. It shows that a host configured for IPv4 only cannotcommunicate with a host configured for IPv6 only, and a host configured for IPv6cannot communicate with a host configured for IPv4 only.

Table 28. Interoperability between IBM Systems Director Server and managed resources

IBM SystemsDirector Server

Resource configuredfor IPv4

Resource configuredfor IPv6

Resource configuredfor IPv4 and IPv6(dual stack)

IPv4 only Yes No Yes

IPv6 only No Yes Yes

IPv4 and IPv6 (dualstack)

Yes Yes Yes

Interoperability with hosts that are outside of the local subnet requires either anIPv6-enabled router to pass IPv6 packets, or the use of Simple Internet Transition(SIT) technology. Available transition technologies include:

64 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

v Dual-stack IP implementations for hosts and routers that must interoperatebetween IPv4 and IPv6.

v Imbedded IPv4 addresses in IPv6 addresses. IPv6 hosts will be assignedaddresses that are interoperable with IPv4, and IPv4 host addresses will bemapped to IPv6.

v IPv6-over-IPv4 tunneling mechanisms for carrying IPv6 packets across IPv4router networks.

The following IPv6 restrictions and prerequisites must be taken into considerationfor the listed IBM Systems Director functional areas:

Table 29. IPv6 restrictions and prerequisites for specific IBM Systems Director functionalareas

Function Restriction or Prerequisite

Discovery manager Discovery supports using IPv6 to discoverresources. For specific IPv6 restrictions, seeIPv6 restrictions for discovery. For generalinformation about using IP addresses withdiscovery, see IP addresses.

Update manager For update manager to check for updates,the IBM Systems Director Server must haveIPv4 Internet access. This access can beobtained through a direct connection or anHTTP proxy.

If an IPv4 connection is unavailable, updatemanager cannot automatically downloadupdates. However, you can still manuallydownload and import updates usingwww.ibm.com/support/fixcentral/. Formore information, see Downloading IBMSystems Director updates without anInternet connection.

Integrated Management Module (IMM) IPv6 support for managing System xserversout-of-band using IMM is not available.

Hardware Management Console(HMC)http://www.ibm.com/developerworks/wikis/display/WikiPtype/IPv6+%28Power+Systems%29http://www.ibm.com/developerworks/wikis/display/WikiPtype/IPv6+%28Power+Systems%29

IBM Systems Director version 6.2 providesIPv6 support for Hardware ManagementConsole Version V7 R7.1.0 SP2 or later.

To properly configure your HMC system forIPv6 to ensure that it can be discovered, seehttp://www.ibm.com/developerworks/wikis/display/WikiPtype/IPv6+%28Power+Systems%29.

Integrated Virtualization Manager (IVM) andVirtual I/O Server (VIOS)

IBM Systems Director version 6.2 providesIPv6 support for Virtual I/O Server2.1.3.0-FP23 and later.

To properly configure your IVM or VIOSsystem for IPv6 to ensure that it can bediscovered, see http://www.ibm.com/developerworks/wikis/display/WikiPtype/IPv6+%28Power+Systems%29.

Chapter 2. Planning 65

Table 29. IPv6 restrictions and prerequisites for specific IBM Systems Director functionalareas (continued)

Function Restriction or Prerequisite

AIX Managing AIX with IPv6 requires AIX 6.1TL05 SP01 or later.

To properly configure your AIX system forIPv6 to ensure that it can be discovered, seehttp://www.ibm.com/developerworks/wikis/display/WikiPtype/IPv6+%28Power+Systems%29.

BladeCenter and System x Management IPv6 support for managing servers usingBladeCenter requires Advance ManagementModule (AMM) Firmware v3.54 (BPET54B).

Storage Management In an IPv6 environment, Storage managersupports discovery, inventory, health status,alerts, configuration, topology, and elementmanager launch on storage devices.However, some storage devices are notsupported in an IPV6 environment due tolimitations. For more information, see“Supported storage devices” on page 28.

Windows v Changing the host name, or the IPv4 orIPv6 address, on Windows 2003 orWindows 2008 automatically reboots thehost agent so that all services are updatedwith the new IP address. You mustremove the discovered agent andrediscover the agent with the new IPaddress.

v You cannot retrieve the IPv6 gateway northe IPv6 prefix length on Windows Server2003.

v DHCPv6 is not supported on WindowsServer 2003.

Common Agent or Platform Agent v Host operating system management withIPv6 using Common Agent or PlatformAgent requires IBM Systems Directorversion 6.2 or later of the agent.

v Changing the IPv4 and IPv6 addressesthrough IBM Systems Director Serverautomatically reboots the host agent sothat all the services are updated with thenew IP address. You must remove thediscovered agent and rediscover the agentwith the new IP address. Ensure that thehost machine is rebooted if the IP addresschanges.

v Platform Agent 6.1.x on Linux onSystem x and Windows does not supportdeletion of the configured interface. Youcan only add or modify an IPv6 address.

66 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 29. IPv6 restrictions and prerequisites for specific IBM Systems Director functionalareas (continued)

Function Restriction or Prerequisite

Network Management For IBM System Director to work properly,an IPv6 Domain Name System (DNS) mustbe configured.

Network management functions supportIPv6 when the network devices are fullyIPv6-compliant. Some network devicesmight not be fully compliant. Refer to the“Supported network devices” on page 22topic for details. Ping and traceroutediagnostic functions do not support IPv6.

SNMP SNMP supports the use of IPv6 startingwith Windows Vista. However, SNMPsupports IPv6 only for networks runningWindows Server 2008 and Windows Vista.This is because SNMP requires the updatedprotocol stack available in these operatingsystems for its IPv6 support.

Unless your network is solely a WindowsServer 2008 network, IPv6 communicationswill fail, even if an IPv6 protocol stack isseparately installed on those computers thatrun earlier versions of Windows. Forexample, SNMP agents that run onWindows Server 2003, or Windows XP, orWindows 2000, respond only to queries thatare made to their IPv4 addresses.

MAP agent The MAP agent can use IPv6 tocommunicate with the IBM SystemsDirector Server. However, the MAP agentmust also have an IPv4 interface tocommunicate with the z/VM SystemManagement API (SMAPI) and the directorymanager that runs on z/VM. The IPv4interface must be accessible to the z/VMSMAPI and directory manager.

Applicability of Platform AgentWhen determining Platform Agent applicability, there are several consideration ofwhich you should be aware before installing each agent.

The following list contains some important considerations for Platform Agent:v The IBM i (formerly i5/OS®) Platform Agent is provided by an IBM i (formerly

i5/OS) Licensed Program Product (LPP). On IBM i 7.1 and IBM i 6.1 (formerlyi5/OS, Version 6 Release 1), install V1R3 of the IBM Universal ManageabilityEnablement for IBM i (5770-UME) LPP. On IBM i 5.4 (formerly i5/OS, Version 5Release 4), install V1R2 of the IBM Universal Manageability Enablement for IBMi (5770-UME) LPP.

v Linux on System z has two Platform Agents. The Platform Agent 5.20.32 isintended for systems that are running Red Hat Enterprise Linux AS, versions4.6, 4.7, and 4.8 on SUSE Linux Enterprise Server 9 for IBM System z. Platform

Chapter 2. Planning 67

Agent 6.2.1 is intended for systems that are running Red Hat Enterprise LinuxAdvanced Platform, versions 5.1, 5.2, 5.3, 5.4, and 5.5, on SUSE Linux EnterpriseServer for IBM System z, versions 10 and 11.

v In general, customers with BMC and IMM service processors should update toPlatform Agent 6.1.1 or later.

v In general, customers with RSA service processors should continue to use IBMDirector Core Services version 5.20 (or any update release version of 5.20, suchas 5.20.3).– Platform Agent versions 6.1.1, 6.1.2, and 6.2 will block updates on IBM

Director Core Services version 5.20 systems and RSA service processors.Therefore, if you want to install Platform Agent version 6.1.1, 6.1.2, or 6.2,you must first uninstall IBM Director Core Services version 5.20 (or anyupdate release version of 5.20, such as 5.20.3).

Restriction: You will no longer be able to manage the RSA in-band. You canmanage it out-of-band by connecting it to the network and discovering it withIBM Systems Director.

– Platform Agent versions 6.1.1 and 6.1.2 will block updates on IBM DirectorCore Services version 5.20 with ServeRAID extensions. Therefore, if you wantto install Platform Agent version 6.1.1 or 6.1.2, you must first uninstall IBMDirector Core Services version 5.20 (or any update release version of 5.20,such as 5.20.3).

Restriction: You will no longer be able to manage the ServeRAID extensions.You can manage the extension if installed on a different server.

Note: Platform Agent 6.2 will neither block updates on IBM Director CoreServices version 5.20 nor have the restriction described above.

– Platform Agent 6.1.1 will block updates on IBM Director Core Servicesversion 5.20 systems with Adaptec (Aristos) extensions if the Adaptechardware has been configured. Platform Agent 6.1.2 will do the same if theAdaptec hardware has been configured. If the Adaptec hardware has not beenconfigured, Platform Agent 6.1.2 will uninstall the Adaptec (Aristos) extensionand the Platform Agent install-upgrade will continue (assuming that there isno other restricted hardware on the system). If the update was blocked andyou still want to install Platform Agent 6.1.1 or 6.1.2, you must first uninstallthe Adaptec (Aristos) extension and IBM Director Core Services version 5.20(or any update release version of 5.20, such as 5.20.3).

Restriction: You will no longer be able to manage the Adaptec (Aristos)extensions. You can manage the extension if it is installed on a differentserver.

Note: Platform Agent 6.2 will neither block updates on IBM Director CoreServices version 5.20 systems with Adaptec (Aristos) extensions nor have therestriction described above. Platform Agent 6.2 will install-upgrade theAdaptec (Aristos) extension if the extension is currently on the machine or ifPlatform Agent is being installed with IBM Systems Director Server 6.2.

v IBM Systems Director, versions 6.1.1 or later, Platform Agents use a newerversion of the LSI MR provider. This provider will not function properly witholder versions of the LSI device drivers. In order to ensure that CIM data andalerts function properly with LSI devices, it is important that the device driversare at the latest levels for all IBM Systems Director, versions 6.1.1 or later,Platform Agents.

68 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

v When Platform Agent versions earlier than 6.1.2, with one NIC, are installed anddiscovered in CA using the IBM Systems Director Upward Integration Modulefor CA Unicenter, the CA agentview GUI will display erroneous information inthe Network interfaces section. The only NIC that is shown will have its namespecified as Name Undefined and its status specified as a yellow “!” iconinstead of a green “OK” icon. This is a known problem in Platform Agent sinceprior to 6.1.2 and has been fixed in 6.1.2 and later releases.

v When IBM Director Core Services 5.20.3, Service Update 1, and ServeRAIDManager (SRM) are installed, rebooted, and discovered in CA, using the IBMSystems Director Upward Integration Module for CA Unicenter, not all sensoricons will display in the CA 2D MAP GUI. Only sensor icons for StorageSubsystem, Network Adapter, and Smart Disk will display. The other sensoricons for processor and memory do not display. This is a known problem in IBMDirector Core Services 5.20.3, Service Update 1, and has been fixed in laterreleases.

Determining IBM Systems Director task supportTask support can vary depending on the hardware model, the operating system,and the agent installed on the hardware. To determine whether the hardware inyour environment is supported by an IBM Systems Director task, you must reviewinformation based on the answers to a few questions.

Is the hardware made by IBM?v Yes, go to “Questions to answer about IBM hardware.”v No, go to “Questions to answer about third-party (non-IBM) hardware.”

Questions to answer about IBM hardwareTo determine task support on IBM hardware you must answer a few questions andreview the applicable information.

Table 30. IBM hardware questions

Question Action

Is the IBM hardware issupported by IBM SystemsDirector?

See the following applicable information:

v Supported IBM® systems and products

v Supported IBM BladeCenter products

v Supported storage devices

Do you want to install IBMSystems Director Server on thesystem?

Yes.

v Make sure the system meets the requirements to runIBM Systems Director Server. See Hardwarerequirements for running IBM Systems DirectorServer.

v Make sure IBM Systems Director Server supports theoperating system installed on the system. SeeOperating systems supported by IBM SystemsDirector.

No. Go to the next question.

Chapter 2. Planning 69

Table 30. IBM hardware questions (continued)

Question Action

Do you want to install CommonAgent or Platform Agent on thesystem?

Yes.

v Make sure the system meets the requirements to runCommon Agent or Platform Agent. See Hardwarerequirements for systems running Common Agent orPlatform Agent

v Make sure the agent supports the operating systeminstalled on the system. See Operating systemssupported by IBM Systems Director.

No. If you choose to install neither of these agents, IBMSystems Director provides limited managementcapability for Agentless-managed systems. For moreinformation, see IBM Systems Director task support byoperating system and agent levels.

Does the operating system andagent (or no agent) installed onthe system support the task youwant to use?

To determine whether the operating system and agentinstalled on the system permit support for a task, seeIBM Systems Director task support by operating systemand agent levels and IBM Systems Director task supportnot affected by operating systems.Notes:

1. Limited task support is provided onAgentless-managed systems.

2. Some tasks are supported only on specific hardware.For example, Storage Manager tasks are supportedonly on storage devices.

For detailed information about task support on specifictypes of hardware, review the following information:

v IBM Systems Director task support for BladeCenterproducts

v IBM Systems Director task support for Storageproducts

Questions to answer about third-party hardwareTo determine task support on third-party (non-IBM) hardware you must answer afew questions and review the applicable information.

Table 31. Third-party hardware questions

Question Action

Is the third-party hardware issupported by IBM SystemsDirector?

IBM Systems Director provides support for:

v Third-party x86-based systems that meet hardwarerequirements. See Hardware requirements for systemsrunning Common Agent or Platform Agent.Note: You can install only Common Agent onthird-party x86-based systems. Platform Agent is notsupported.

v Third-party storage products. See Supported storagedevices.

70 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 31. Third-party hardware questions (continued)

Question Action

Do you want to install IBMSystems Director Server on thesystem?

Yes.

Stop. IBM Systems Director Server is not licensed for useon third-party hardware.

No. Go to the next question.

Do you want to install CommonAgent or Platform Agent on thesystem?

Yes.Note: You can install only Common Agent onthird-party x86-based systems. Platform Agent is notsupported.Make sure Common Agent supports theoperating system installed on the system. See Operatingsystems supported by IBM Systems Director.

No. If you choose not to install Common Agent, IBMSystems Director provides limited managementcapability for Agentless-managed systems.

Does the operating system andagent (or no agent) installed onthe system support the task thatyou want to use?

To determine whether the operating system and agentinstalled on the system permit support for a task, reviewthe following information:

v IBM Systems Director task support by operatingsystem and agent levels

v IBM Systems Director task support not affected byoperating systems

v Supported tasks and features for third-party x86-basedsystems

Note:

1. Limited task support is provided onAgentless-managed systems.

2. Some tasks are supported only on specific hardware.For example, Storage Manager tasks are supportedonly on storage devices.

For detailed information about task support on specifictypes of hardware, review the following information:

v IBM Systems Director task support for BladeCenterproducts

v IBM Systems Director task support for Storageproducts

Planning to install IBM Systems DirectorAny time that you install IBM Systems Director, complete the planning steps beforestarting the actual installation to ensure that your installation is successful andmeets your needs.

Service and support informationService and support offerings for IBM Systems Director are based on the platformon which you choose to run IBM Systems Director Server.

For IBM Systems Director Server running on IBM BladeCenter or System xsystems, subscription services are available for a fee entitling you to notification ofnew upgrades, patches and support information, and free updates during that

Chapter 2. Planning 71

period. For more information about subscription services or to renew yoursubscription service contract, see the Ready to Buy Web Page atwww.ibm.com/systems/management/director/subscription/.

For more information about service and support offerings available for all IBMsystems, see Support Offerings Web site at www.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5076601&brandind=5000016 or contactyour IBM representative or IBM Business Partner.Related reference

IBM Subscription Services

IBM Director support offerings

Reviewing the environmentBefore installing IBM Systems Director, review the network of systems and devicesyou will manage with IBM Systems Director to identify what kinds of resourcesthat you will manage, where they are located, and how IBM Systems Director willconnect with them.

Your network must be up and running before you install IBM Systems Director.

Identifying the hardwareBegin the planning process by identifying the systems and devices that you wantto manage with IBM Systems Director.

The type of hardware in the environment might determine how you prepare thephysical infrastructure or which features you select when you install IBM SystemsDirector Server. Your environment might include one or more of the followingtypes of hardware:v Chassis, racks, and remote input/output enclosures, such as IBM BladeCenter

unitsv Systems, including servers, desktop computers, workstations, and mobile

computers, such as IBM Power systems, System x servers, and System z serversv Storage devices, such as the IBM System Storage DS4000 family of disk storage

devicesv SNMP devices and printersv ServeRAID controllers or service processors, such as the Remote Supervisor

Adapter II

Review the hardware requirements section in the “Hardware and softwarerequirements” 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 32 on page 73.

You can use this information to verify that your managed systems and deviceshave been discovered, to manually add systems or devices in IBM SystemsDirector, or to plan managed-resource groups or user roles based on the typesor locations of managed systems and devices.

72 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 32. Hardware identification worksheet for IBM Systems Director

System or devicetype

Operating system (ifapplicable) Physical location Network address

Identifying local and remote subnetsYou need to provide local and remote subnet information in order for IBM SystemsDirector to discover resources.

Identify the local and remote subnets in which the systems that you want tomanage with IBM Systems Director are located, and record this in Table 33

Table 33. Local and remote subnets worksheet

Information to gather for discovery Values

Unicast Addresses for Agentless managedsystem discovery

IP addresses or IP-address ranges for unicastdiscovery of Agentless managed systems.

___.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.___

Directory agent server for Platform Agentdiscovery

Service Location Protocol (SLP) directoryagent server for discovery of Platform Agentmanaged systems.

Chapter 2. Planning 73

Table 33. Local and remote subnets worksheet (continued)

Information to gather for discovery Values

SLP scope for Platform Agent discovery

Service Location Protocol (SLP) scope fordiscovery of Platform Agent managedsystems.

Unicast Addresses for Common Agentdiscovery

IP addresses or IP-address ranges for unicastdiscovery of Common Agent managedsystems.

___.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.______.___.___.___ - ___.___.___.___

Subnets for Common Agent discovery

TCP/IP addresses and subnet masks forbroadcast and relay discovery of CommonAgent managed systems.

___.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.___

Multicast group for Common Agentdiscovery

Multicast group TCP/IP address andtime-to-live value for multicast discovery ofCommon Agent managed systems.

multicast group: ___.___.___.___time to live: _______

Subnets for discovery of SNMP devices

TCP/IP addresses and subnet masks fordiscovery of simple network managementprotocol (SNMP) devices.

___.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.______.___.___.___ / ___.___.___.___

Community names for discovery of SNMPdevices

Community names for discovery of simplenetwork management protocol (SNMP)devices.

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

74 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 33. Local and remote subnets worksheet (continued)

Information to gather for discovery Values

SLP profiles for discovery of SMI-S storagedevices

Service Location Protocol (SLP) profiles fordiscovery of SMI-S devices.

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Identifying firewalls and blocked portsReview the firewalls and blocked ports in your installation environment in order toidentify potential barriers to IBM Systems Director access, and to plan how toimplement IBM Systems Director management without creating security gaps.

IBM Systems Director must be able to access all the managed resources in thenetwork, and if you will be using a remote management console, the managementconsole and management server must have access to each other. In addition, somefunctions 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 aspeed of at least 1.5 megabytes per second (MBps) to ensure reliable networkperformance.

Version compatibility of IBM Systems Director componentsacross releases

IBM Systems Director Server 6.2.x can work with previous 5.20.x or 6.1.x versionsof Common Agent or Platform Agent.

Important:

v The version of IBM Systems Director Server must always be the same as or laterthan the version of any Common Agent or Platform Agent that is installed onthe managed systems. For example, you must install and use IBM SystemsDirector Server 6.2.1 to manage Common Agent 6.2.1 that is installed onmanaged systems, or you must install and use IBM Systems Director Server 6.2.1to manage Platform Agent 6.2.1 that is installed on managed systems.

v IBM Systems Director version 6.1 or later is not compatible with any versions ofIBM Director Server extensions, IBM Director Console extensions, or IBMDirector Agent extensions that are supported by IBM Director version 5.20.x orearlier. Therefore, you must first uninstall those extensions before you install orupgrade an IBM Systems Director component from version 5.20.x to version6.1.x or 6.2.x. For detailed information, see What's new in version 6.2.0.

v If you must run a version of IBM Director or IBM Systems Director that is olderthan the version that is currently installed, you cannot update or migrate to it.You must instead uninstall your current version and then install the olderversion.

See the following table for a complete listing of previous agent versions that arecompatible with and can be managed by IBM Systems Director Server or 6.2.x.

Chapter 2. Planning 75

Table 34. Compatibility of IBM Systems Director Server with previous agent versions

Compatibility of IBM Systems Director Server with previous agent versions

For Power Systems servers:

CompatibleAgent-managed systems

IBM Systems DirectorServer version 6.2.x

IBM Systems DirectorServer version 6.1.2.x

IBM Systems DirectorServer version 6.1.1.x

IBM Systems DirectorServer version 6.1

Common Agent for AIX 5.20.26.1 - 6.1.26.2 (includesPlatform Agent 6.2,Pegasus CIMserver,and CIM providers)- 6.2.1

5.20.26.1 - 6.1.2

5.20.26.1.0.3 - 6.1.1.x

5.20.26.1

Common Agent forVIOS

6.1.0.3 - 6.1.26.2 - 6.2.1

6.1.0.3 - 6.1.2 6.1.0.3 - 6.1.1.x 6.1.0.3

Platform Agent for AIX n/a n/a n/a n/a

Common Agent forLinux on Power Systems

5.20.36.1 - 6.1.26.2 - 6.2.1

5.20.36.1 - 6.1.2

5.20.36.1 - 6.1.1.x

5.20.36.1

Platform Agent forLinux on Power Systems

5.20.36.1 - 6.1.26.2 - 6.2.1

5.20.36.1 - 6.1.2

5.20.36.1 - 6.1.1.x

5.20.36.1

Common Agent for IBMi

6.1.2 (5722-UME V1R2)6.2 (5770-UME V1R3)6.2.1

6.1.2 (5722-UME V1R2) n/a n/a

IBM Director [Level 2]Agent for IBM i

5.20.2 5.20.2 5.20.2 5.20.2

IBM i Platform Agent (5722–UME V1R2)(5770-UME V1R3)

(5722–UME V1R2)(5770-UME V1R3)

(5722–UME V1R2) (5722–UME V1R2)

For System x servers:

CompatibleAgent-managed systems

IBM Systems DirectorServer version 6.2.x

IBM Systems DirectorServer version 6.1.2.x

IBM Systems DirectorServer version 6.1.1.x

IBM Systems DirectorServer version 6.1

Common Agent forWindows

5.20 - 5.20.36.1 - 6.1.26.2 - 6.2.1

5.20 - 5.20.36.1 - 6.1.2

5.20 - 5.20.36.1 - 6.1.1.x

5.20 - 5.20.36.1

Platform Agent forWindows

5.20 - 5.20.316.1 - 6.1.26.2 - 6.2.1

5.20 - 5.20.316.1.1 - 6.1.2

5.20 - 5.20.316.1.1 - 6.1.1.x

5.20 - 5.20.31

Common Agent forLinux on System x

5.20 - 5.20.36.1 - 6.1.26.2 - 6.2.1

5.20 - 5.20.36.1.1 - 6.1.2

5.20 - 5.20.36.1 - 6.1.1.x

5.20 - 5.20.36.1

Platform Agent forLinux on System x

5.20 - 5.20.316.1 - 6.1.26.2 - 6.2.1

5.20 - 5.20.316.1.1 - 6.1.2

5.20 - 5.20.316.1.1 - 6.1.1.x

5.20 - 5.20.31

For System z servers:

CompatibleAgent-managed systems

IBM Systems DirectorServer version 6.2.x

IBM Systems DirectorServer version 6.1.2.x

IBM Systems DirectorServer version 6.1.1.x

IBM Systems DirectorServer version 6.1

Common Agent forLinux on System z

5.20 - 5.20.316.1 - 6.1.26.2 - 6.2.1

6.1 6.1 6.1

Platform Agent forLinux on System z

5.20.3 - 5.20.326.2.1

6.1.1 6.1.1 n/a

IBM z/VMManageability AccessPoint Agent for Systemz

6.2.1 5.20.3 5.20.3 5.20.3

76 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

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

IBM Systems Director

The IBM Systems Director program contains Management Server (Manager)components, Agent components, and application programming interfaces (APIs), asfurther described in the documentation.

You are authorized to use Management Server and Agent components only on IBMmachines.

Notwithstanding the foregoing, the IBM Systems Director program includes alicense 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 becombined or aggregated. For example, if you buy two IBM machines and installthe IBM Systems Director program on only one of them, you are entitled to installthe Agent component on only 20 non-IBM x86 systems. If you install the IBMSystems Director program on both IBM machines, your entitlement is limited tomanaging 20 non-IBM x86 systems. To install additional Agent components onnon-IBM x86 systems, you must obtain additional Agent component licenses fromIBM.

Authorization for IBM Systems Director for IBM Power Systems

Processor is a unit of measure by which the IBM Systems Director for IBM PowerSystems program can be licensed. Processor (commonly called a processor core orCPU) is a functional unit within a computing device that interprets and executesinstructions. A processor consists of at least an instruction control unit and one ormore arithmetic or logic unit. With multi-core technology, each core is considered aprocessor. Authorization for the IBM Systems Director for IBM Power Systemsprogram is based on the total number of activated processors (including anytemporary processors) on the machines running the IBM Systems Director for IBMPower Systems program and the total number of activated processors (includingany temporary processors) on the machines being managed by the IBM SystemsDirector for IBM Power Systems program.

Authorization for IBM Systems Director for IBM x86 servers

Server is a unit of measure by which the IBM Systems Director for IBM x86 serversprogram can be licensed. A Server is a physical computer that is comprised ofprocessing units, memory, and input/output capabilities and that executesrequested procedures, commands, or applications for one or more users or clientdevices. Where racks, blade enclosures, or other similar equipment is beingemployed, each separable physical device (e.g., a blade or a rack-mounted device)that has the required components is considered itself a separate Server.

The IBM Systems Director for IBM x86 servers program uses a per Server chargingmetric. An authorization is required for each server running the IBM SystemsDirector for IBM x86 servers program and for each server being managed by theIBM Systems Director for IBM x86 servers program.

Chapter 2. Planning 77

Authorization for IBM Systems Director for Linux on System z

Processor is a unit of measure by which the IBM Systems Director for Linux onSystem z program can be licensed. Processor (commonly called a processor core,CPU, or engine) is a functional unit within a computing device that interprets andexecutes instructions. A processor consists of at least an instruction control unitand one or more arithmetic or logic unit. With multicore technology each core isconsidered a processor. Authorizations for the IBM Systems Director for Linux onSystem z program must be acquired for all activated processors available for usefor the server.

In addition to the authorization required for the IBM Systems Director for Linuxon System z program directly, you must obtain authorizations for this programsufficient to cover the processor cores managed by the program. For IBM System zmachines, the authorization required for the IBM Systems Director for Linux onSystem z program is based on the following:1. When the IBM Systems Director for Linux on System z program is installed on

or managing engines with the Integrated Facility for Linux (IFL) feature, youmust acquire an authorization for each activated engine with the IFL feature onthat machine.

2. When the IBM Systems Director for Linux on System z program is installed onor managing general purpose engines, you must acquire an authorization foreach activated general purpose engine on that machine.

Terms applicable to API use

The IBM Systems Director program includes APIs called Representational StateTransfer (REST) APIs and Advanced External Application Launch (AEAL) function.The IBM Systems Director REST APIs and AEAL function are described in thedocumentation, available through the IBM Systems Director Information Center.You may develop applications using the Program's REST APIs and/or AEALfunction solely for testing and deployment within your Enterprise and only inconnection with your internal business purposes. An Enterprise is any legal entity(such as a corporation) and the subsidiaries it owns by more than 50 percent. Youmay not rent, lease, loan, sell or otherwise distribute applications or derivativeworks created using the IBM Systems Director REST APIs and/or AEAL functionto third party end users external to your Enterprise unless you have entered into awritten contract with IBM for this purpose.

Warranty

The Specified Operating Environment for the IBM Systems Director program maybe located in the Planning section of the IBM Systems Director Information Center.The IBM Systems Director program contains Upward Integration Modules (asdescribed in the documentation) for third party system management products tomanage IBM hardware platforms with IBM Director Agent components. There isno warranty or support service available for the Upward Integration Moduleswhen you use a third party system management product.

Special terms for the Software Update component

When you use the Software Updates navigation link of the IBM Systems Directorprogram to request software updates, the Management Server component collectsinformation about the release level of certain software products installed on yourmachine ("Software Information") and electronically sends that Software

78 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Information to IBM. Software Information does not include business data such asyour financial, statistical and personnel data regarding your business. You agreethat IBM (including subcontractors and consultants under contract to IBM) maystore and use Software Information for purposes of software maintenance andsupport, and that such Software Information (including any contact informationprovided by you) may be transferred to such entities in any country whether ornot a member of the European Union.

Software Updates Licensee receives are covered by this Agreement. If anyadditional or different terms apply to any such Software Update, such terms willbe included with the Software Update.

Supporting program details - IBM DB2

The following applies to use of IBM DB2 Enterprise Server Edition V 9.7.

Use Limitations: Use by Principal Program"Use by Principal Program" means that neither you nor any application,program, or device external to the Principal Program is authorized todirectly use or access the services of IBM DB2 Enterprise Server Edition V9.7 in any way. The IBM DB2 Enterprise Server Edition V 9.7 program isprovided exclusively for use by the Principal Program. You may accessIBM DB2 Enterprise Server Edition V 9.7 only to perform administrativefunctions, such as backup, recovery, and authorized configuration but maynot directly use the IBM DB2 Enterprise Server Edition V 9.7 program forany productive use.

IBM provides the IBM DB2 Enterprise Server Edition V 9.7 program withoutobligation of support and "AS IS," WITHOUT WARRANTY OF ANY KIND,EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THEWARRANTY OF TITLE, NON-INFRINGEMENT OR NON-INTERFERENCE ANDANY IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITYAND FITNESS FOR A PARTICULAR PURPOSE.

Notwithstanding the foregoing, if you purchase an authorization to the IBMSystems Director Storage Control 4.2.1 (5765-ASM) product, the terms of the "IBMInternational Program License Agreement", including this License Information, willthen apply to your use of the IBM DB2 Enterprise Server Edition V 9.7 program.

Obtaining licenses for Common AgentIBM Systems Director includes licenses for up to 20 installations of Common Agenton non-IBM x86 systems. To install Common Agent on additional non-IBM x86systems, 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/about/director52/about52/buy/.

Choosing how to install IBM Systems DirectorThe method that you use to install IBM Systems Director 6.2.1 depends on which,or if any, previous versions of IBM Systems Director or IBM Director are alreadyinstalled on your system.

There are various methods that you can employ to install IBM Systems Director6.2.1 on your system. Each method is tailored to the state of a system before

Chapter 2. Planning 79

installation. For example, you would use a different installation method if youwere starting from scratch than if you wanted to reuse data from an existing IBMDirector 5.20.x or IBM Systems Director 6.1.x installation.

Note: The IBM Systems Director installation media for 6.2 is refreshed to includethe updates for 6.2.1. When running the installation from the refreshed installationmedia, you can choose to include the 6.2.1 updates as part of the installation. Theupdates for 6.2.1 are included in the \update directory on the refreshed installationmedia. If IBM Systems Director 6.2 is already installed on your system, then youwould use update manager, but could import the 6.2.1 updates from the \updatedirectory on the refreshed media.

Complete the following steps to determine which method to use to install IBMSystems Director 6.2.1 on your system:1. Determine which, if any, previous versions of IBM Systems Director or IBM

Director are already installed on your system.2. If a previous version is installed, determine whether you want to migrate the

data to IBM Systems Director 6.2.1.3. Based on your results from the previous steps, obtain and install IBM Systems

Director 6.2.1 using the installation method that is most appropriate for yourenvironment:

Table 35. IBM Systems Director 6.2 installation methods

If your system has...Follow this method to install IBM SystemsDirector 6.2.1

No version of IBM Systems Director or IBMDirector (starting from scratch)

Install IBM Systems Director 6.2.1 usingstandard installation and follow thestandard installation path. See “InstallingIBM Systems Director on the managementserver” for instructions.

IBM Systems Director 6.2, and you want toreuse your data

Install IBM Systems Director 6.2.1 usingupdate manager. See “Updating IBMSystems Director” for instructions.

IBM Systems Director 6.1.x, and you want toreuse your data

Upgrade using standard installation andfollow the migration path. See “Upgradingand migrating to IBM Systems Director 6.2.1from 6.1.x” for the two-step process.

IBM Director 5.20.x, and you want to reuseyour data

Upgrade to IBM Systems Director 6.1.x, theninstall IBM Systems Director 6.2 usingstandard installation and follow themigration path. See “Upgrading andmigrating to IBM Systems Director fromIBM Director 5.x” for instructions.

Any version of IBM Systems Director or IBMDirector, but you do not want to reuse yourdata

Uninstall the previous version, then installIBM Systems Director 6.2.1 using standardinstallation and follow the standardinstallation path. See “Uninstalling IBMSystems Director” and “Installing IBMSystems Director on the managementserver” for instructions.

80 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Choosing the IBM Systems Director Server installationoptions

When you install IBM Systems Director Server using a standard installation, youmust specify various options for your installation.

Determine the IBM Systems Director service account information. You need toprovide the following information when you install IBM Systems Director Server:v Computer namev User namev Password

Choosing where to install IBM Systems Director ServerBefore installing IBM Systems Director, you must choose one or more managementservers 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 bemanaging, the tasks you will be performing with IBM Systems Director, and thedatabase you will use. In some cases, you might want to install more than oneinstance of IBM Systems Director Server.

When deciding where to install IBM Systems Director Server, evaluate thefollowing 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 IBMSystems Director Server installed either on a blade in the IBM BladeCenter, or ona separate management server. Refer to “Preparing to manage a IBMBladeCenter” on page 139 for detailed information.

v For Windows installations, do not install IBM Systems Director Server on adomain 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 DirectorWeb interface.

– Unless the IBM Systems Director service account has domain administratorprivileges, you cannot restart IBM Systems Director Server.

v Consider installing multiple instances of IBM Systems Director Server. Installingmultiple instances of IBM Systems Director Server means that all of the instancesneed to register with the same agent manager. See “Agent manager”, to learnabout the agent manager. Installing IBM Systems Director Server on multiplemanagement 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 5000Common Agent managed systems, if you have licenses for Common Agenton those managed systems. The number of Agentless managed systems andAgentless managed systems that you can manage is limited only by theavailable resources of the management server and the network.

– The systems that you want to manage are in several geographic locations orare owned by multiple system administrators.

– You want to manage each IBM BladeCenter with an installation of IBMSystems Director Server on a blade in the chassis.

Chapter 2. Planning 81

v Consider the kind of database you want to use. You might want to use aparticular database for IBM Systems Director data, to facilitate data-miningactivity or for other reasons. Not all databases are supported for all IBM SystemsDirector Server installation locations. See “Choosing the IBM Systems Directordatabase 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 extensionsand expect it to continue functioning even if the network grows.

– The External Application Launch Wizard requires that IBM Systems DirectorServer be installed in the default installation path.

Choosing the IBM Systems Director database applicationSome IBM Systems Director functions require use of an external database, but notall databases support the same functionality with IBM Systems Director. Choose asupported database that meets the needs of your installation.

Note: If you install IBM Systems Director Server using the basic installationoption, the Apache Derby database is installed.

Attention: The Apache Derby database that is installed using the basicinstallation option is not able to handle a large network of 500 managed objects ormore. If you plan to manage a large network from a single IBM Systems DirectorServer server, either initially or in the future, take this limitation into account inyour planning. No option is provided for migrating data to another databasemanagement system (DBMS) type. Therefore, if you switch from Apache Derby toanother DBMS type in the future, managed data will be lost and will need to berecreated or rediscovered.

Tip: If you choose to use a custom remote database, it is important to understandthat data is stored and migrated differently on a remote database, and if you planto use the smsave and smrestore commands to migrate your remote databaseenvironment to a new release, you must use additional parameters to ensure thatall discovery and inventory data is restored correctly on the remote database. The-dbTargetDir directory option is required when migrating a remote database. Youmust ensure that the user ID performing the migration has database backup andrestore privileges. For more information, see the “smsave” and “smrestore” topics.

IBM Systems Director Server uses a database to store inventory information in acentral location. You can then use this inventory information to manage yourassets.

Before you install IBM Systems Director Server, decide the database that you wantto use.

Complete the following steps to determine the appropriate database application foryour installation of IBM Systems Director.1. Review the advantages and disadvantages of the different database installation

types.

82 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 36. Advantages and disadvantages of different DBMS installation types

DBMS installation type Advantages Disadvantages

Embedded DBMSThe DBMS isinstalled on themanagement serveras part of the IBMSystems DirectorServer installation,and shares the JavaVirtual Machinewith IBM SystemsDirector.

v Configuration is easy.

v No additional license isrequired.

v Resource usage is lowerthan that of a local DBMSinstallation.

v A separate server for theDBMS is not required.

v Apache Derby databaselimitation: The number ofmanaged objects is limited.

Local DBMSThe DBMS isinstalled on themanagement serveron which IBMSystems DirectorServer is installed.

v A separate server for theDBMS is not required.

v Resource usage on themanagement server is thehighest of the DBMS types.

Remote DBMSThe DBMS isinstalled on adifferent server thanthe managementserver, and accessedremotely by IBMSystems DirectorServer.

v Resource usage on themanagement server is thelowest of the DBMS types.

v You can use an existingDBMS and avoidpurchasing an additionalDBMS license.

v A separate server for theDBMS is required.

v Connectivity problemswith the database serverwill affect IBM SystemsDirector. For example, ifthe database server goesoffline or becomesunreachable, IBM SystemsDirector Server will stopresponding and hang.

2. Review the supported databases for your management server and the type ofinstallation that you prefer. Depending on where you are installing IBMSystems Director Server, you have one or more possible choices for yourdatabase. See “Supported database applications.” for further information.

3. Review the information in Table 37 to determine the database that best meetsyour needs. Some databases (including Apache Derby) cannot handle a largenetwork of 500 managed objects or more.

Table 37. Large network management

DatabaseCan handle a large networkof managed objects

Apache Derby No

IBM DB2 Yes

Microsoft SQL Server Yes

Microsoft SQL Server Express No

Oracle® Database Yes

Chapter 2. Planning 83

Choosing the management level for managed systemsIBM Systems Director provides three different levels of management for managedsystems and managed objects. For each managed system, you need to choose themanagement level that provides the management functionality you need for thatmanaged system.

Depending on the type of managed system and the management tasks you need toperform, you can choose the best management level for the managed system. IBMSystems Director has three management levels:

AgentlessManaged systems without any IBM Systems Director software installed.

Platform AgentManaged systems with Platform Agent installed.

Common AgentManaged systems with Common Agent installed.

These three management levels have different requirements and provide differinglevels of management functionality in IBM Systems Director.

For each managed system, review Table 38 and decide what level of managementis required.

Table 38. Management-level selection worksheet4

Criteria AgentlessPlatform

AgentCommon

Agent

Managed system types

IBM systems running AIX X1 X2

IBM systems running IBM i X X 3 X

IBM systems running Linux X X

IBM systems running Linux and supportingeither the SSH 5 or DCOM 6 protocol

X X X

IBM systems running Windows X X

IBM systems running Windows and supportingeither the SSH or DCOM protocol

X X X

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

X X X

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

X X X

Other managed resources, including managementprocessors supporting SSH, racks, and SNMPdevices

X

Managed system attributes

Managed system has a supportedworkgroup/enterprise management agentinstalled

X

Minimal additional memory constraint onmanaged system

X

No additional memory constraint on managedsystem

X

No Common Agent license required X X

84 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 38. Management-level selection worksheet4 (continued)

Criteria AgentlessPlatform

AgentCommon

Agent

No software required on managed system X

Needed functionality

Asset ID X

Event automation plans 7 X X X

Event log X X X

File Transfer X

Active Status X X

Service and Support Manager (Linux andWindows)

X

virtualization manager (Linux & Windows) X

Remote control (Windows only) 8 X

Remote session to all supported managedsystems and devices

X

Remote session to SNMP devices and systemssupporting SSH

X X X

Restart the managed system X X X

Upgrade to Platform Agent X

Upgrade to Common Agent X X

Notes:1. Agentless management is supported only with SSH, and it is limited agentless

support.2. Common Agent is supported with and without SSH.3. Platform Agent managed system support is not provided by the Platform Agent

but by either the 5722UME or 5770UME product.4. In this table, "systems" include servers, desktop computers, workstations, and

mobile computers.5. SSH = Secure Shell6. DCOM = Distributed Component Object Model7. Event-automation plans can be applied to Agentless managed systems;

however, most of the events that can trigger an event-automation plan are notgenerated for Agentless managed systems.

8. Not supported in version 5.20.2 on Windows Vista.

Planning for virtual environmentsTo fully enable the management capabilities of IBM Systems Director for yourvirtual resources, ensure your environment is set up correctly. In most cases, youneed to install the required software on the host systems in your environment. Therequired software varies, depending on the type of resources in your environment.

Install the following software on the host systems according to your virtualenvironment:v Hardware Management Console environment:

– No agent or subagent software is needed.v Integrated Virtualization Manager environment:

Chapter 2. Planning 85

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

– Common Agent– Virtualization manager subagent

v Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions withHyper-V role enabled, Release 2 environment:– Common Agent– Virtualization manager subagent

v VMware ESX Server environment:– Common Agent– Virtualization manager subagent

Note: If the VMware ESX host is being managed by VMware VirtualCenterrunning on Windows, it is recommended that you do not install thevirtualization manager subagent for VMware ESX Server.

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

v VMware VirtualCenter environment:– Common Agent– Virtualization manager subagent

v VMware vCenter environment:– Common Agent– Virtualization manager subagent

v Xen environment:– Platform Agent

v IBM z/VM environment:– Platform Agent– IBM z/VM Manageability Access Point Agent

Note: The IBM z/VM Manageability Access Point Agent is installed on asupported version of Linux that is running as a guest on the z/VM 5.4 or 6.1operating system.

Planning to upgrade or update IBM Systems DirectorIf you already have IBM Systems Director installed and you want to move to alater version, it is helpful to first understand the various processes that areavailable. You will either upgrade or update depending on the versions from andto which you are moving. This topic helps you understand the differences betweenupgrading and updating and the circumstances in which you use each process.

The two processes that are available to move to a later version of IBM SystemsDirector are upgrading and updating.

UpgradeYou upgrade IBM Systems Director when moving to a major or minor(two-digit) release such as 6.2. A full installer is used for the upgrade taskand data migration is necessary if you want to preserve data from yourprevious version of IBM Systems Director. You are replacing, as opposed toupdating, your current installation.

86 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Use the upgrade and migration process to upgrade IBM Systems Director.For more information about upgrading IBM Systems Director, see“Upgrading and migrating IBM Systems Director”. For more informationabout upgrading agents, see “Upgrading or updating the IBM SystemsDirector agents”.

UpdateYou update IBM Systems Director when moving to an update (three-digit)release such as 6.2.1 or a patch (four-digit) release such as 6.2.0.1. Updatemanager is used for the update task and all data is preserved from yourprevious version of IBM Systems Director.

Note: IBM provides cumulative updates and cumulative defect-onlypatches for IBM Systems Director versions 6.1 and 6.2. From any release,update, or patch, you can update to a newer update or patch. If you installa patch for an update version that is later than the currently installedupdate version, you also get that new update as a prerequisite for the newpatch. For example, if you have version 6.2.0.1 installed and you move toinstall the version 6.2.1.1 patch, you automatically receive the 6.2.1 updateas a prerequisite.

Use update manager to install updates and patches on IBM SystemsDirector. For more information about updating IBM Systems Director, see“Updating systems”. For more information about updating agents, see“Upgrading or updating the IBM Systems Director agents”.

The following table details the upgrade and update packages that are provided forIBM Systems Director and the process that you use to move to each package.

Table 39. Upgrade and update packages

PackageCharacteristics of thepackage

Process used to move to thepackage

Release

(for example, IBM SystemsDirector version 6.2)

v Includes significant newfunction.

v Requires a separate fullproduct installation.

v Is available from the DVDor www.ibm.com/systems/management/director/downloads/.

v Is reflected in theoperating system registry.Note: To determine theversion of IBM SystemsDirector that is currentlyinstalled, use the lslppcommand (on AIX ) or therpm command (on Linux),or check the Windowsregistry.

Upgrade

Chapter 2. Planning 87

Table 39. Upgrade and update packages (continued)

PackageCharacteristics of thepackage

Process used to move to thepackage

Update

(for example, IBM SystemsDirector version 6.2.1)

v Includes minor updates,new features (such as newhardware support), andfixes.

v Is not reflected in theoperating system registry.Note: See Determining theinstalled IBM SystemsDirector versions fordetails about how todetermine the version ofIBM Systems Director thatis currently installed.

v Is cumulative. Forexample, if a version 6.2.2update is made available,it would include featuresand fixes contained inversion 6.2.1, as well aspatches published forversion 6.2.1.

Update

Patch

(for example, IBM SystemsDirector version 6.2.1.1)

v Includes fixes for defectsat the associated updatelevel only and is installedfor a specific update, suchas version 6.2.1.

v Installed by updatemanager.

v Is not reflected in theoperating system registry.Note: See Determining theinstalled IBM SystemsDirector versions fordetails about how todetermine the version ofIBM Systems Director thatis currently installed.

v Is cumulative. Forexample, if a version6.2.1.2 patch is madeavailable, it would includefeatures and fixescontained in version6.2.1.1.

Update

Notes:

v You can update installed plug-ins such as Active Energy Manager independentlyin update manager. For an overview of available IBM Systems Director plug-ins,see Additional IBM Systems Director plug-ins.

v For platform specific information about how to update IBM Systems DirectorServer and agents on AIX , see “IBM Systems Director Best Practices Wiki.”

88 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Related reference

IBM Systems Director Best Practices Wiki

Disaster recovery for IBM Systems Director 6.2.xTo protect your IBM Systems Director 6.2.x data from a disaster, backup your datausing commands provided by IBM Systems Director. In addition to disastersituations, it is possible that a situation can occur that might cause IBM SystemsDirector to enter an undesired state, for example, IBM Systems Director Server nolonger starts. You can use data set restoration to return IBM Systems Director to itslast known good state. Before you backup your data, you must determine thecircumstances in which you intend to restore your data.

Choosing between backup and migration

When you backup your IBM Systems Director 6.2.x data, you must restore thebackup data 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 Powerserver.

v The same version of operating system. For example, you cannot backup datafrom a server running Red Hat Enterprise Linux 4.0 to a server running Red HatEnterprise 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.2.x management server and restore the data toan IBM Director 5.20 management server.

Important: If your intention is to migrate your IBM Systems Director 6.2.xinstallation to a configuration with a different server platform, operating system, ordatabase application, you cannot use the commands provided for simple backupand disaster recovery. For information about migrating an IBM Director 5.20installation to IBM Systems Director 6.2.x, see “Upgrading and migrating IBMSystems Director.”

For detailed information about the smsave and smrestore commands, see “smsavecommand” and “smrestore command.”

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 backupoutput in a remote location from the management server location. You mustdetermine 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 twodata-sets: one at the location of the remote database server and the other on theIBM 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, youmust first install IBM Systems Director on a new server. Make sure the server

Chapter 2. Planning 89

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 canchange from the original installation without any effect.

Planning for eventsAn 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 aproblem relating to a system. A resolution is the occurrence of a correction to aproblem relating to a system.

Note: In the IBM Systems Director product, there are tasks and features that usethe word alert in place of the word event. Also, some tasks use the word notificationinstead of event.

Sources that can generate events include, but are not limited to, the followingprograms and protocols:v Common Agentv Platform Agentv Microsoft Windows event logv Windows Management Instrumentation (WMI)v SNMP through out-of-band communicationv Intelligent Platform Management Interface (IPMI) Platform Event Traps (PET)

through out-of-band communicationv IBM service processors through out-of-band communication

Successful use of event notification depends on careful planning. Consider thefollowing 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 monitoredBefore configuring IBM Systems Director and your managed systems, you shouldplan how events will be sent to IBM Systems Director and how event notificationswill 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 orBladeCenter management modules, it automatically configures them to sendevents using in-band communication with IBM Systems Director Server. Fordetailed information about communication with management modules andservice processors, see “Service processor communication.”

Notes:

– For Ethernet connections, configure either a static IP address or enable the useof DHCP.

90 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

– BladeCenter management modules and the Remote Supervisor Adapter andRemote Supervisor Adapter II service processors support DHCP; however, theuse of a static IP address is potentially more reliable than using DHCP. Astatic address means that the failure or inaccessibility of DNS and/or DHCPservers will not prevent access to the management module or serviceprocessor.

– If a BladeCenter management module or Remote Supervisor Adapter II is setto use DHCP but does not receive an address from the DHCP server withintwo minutes, the management module or adapter automatically sets itsaddress as 192.168.70.125.

v Consider how you want event notifications to be sent to the personnel who needto receive them.– Using event automation plan, you can configure IBM Systems Director to

send notification of particular events or event types using e-mail or mobilephone text message, or by starting an application on the management serveror on a managed system.

– Alternatively, you can configure management modules and some serviceprocessors to send event notifications directly to personnel or othermanagement applications besides IBM Systems Director using means such asSNMP traps or e-mail. This kind of event notification is not enabled bydefault, but can be configured using the BladeCenter Configuration Managertask in IBM Systems Director or through a direct connection to the serviceprocessor or management module. These events are broken down into thefollowing 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 andthe SNMP agent, and configure the IP address. If using SNMPv1, configurethe 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 implementationsTo plan and design an event automation plan, you must determine what the goalof the event automation plan is.

Consider which systems you intend to target with the event automation plan. Youcan target all systems, a subgroup of systems, or a specific system.

You can structure event filters and event actions in different ways. This sectionpresents some of the possible structures that you can use. Remember that manyevent automation plans might include each of the elements of each of thestructures that are presented.

When designing your event automation plan structure, consider all the systems ingroups. Start by designing an event automation plan that contains events that

Chapter 2. Planning 91

apply to the largest number of objects. Then, create event automation plans thatcover the next largest group of systems, and continue to group them until youreach the individual managed-object level. When doing this, remember that eachsystem 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 eventautomation plan.

v How will you group your systems as smaller groups, according to the additionalevents you want to monitor? The smaller groups are usually based on thefollowing criteria:– Managed-object manufacturer, for vendor-specific events– Function of the system, for services and resources specific to that function

v What type of systems are you monitoring?v What is the function of the system?v What are the key monitors for the system?v Are there other systems for which you want to use the same monitors?

Managing and monitoring systems with event automation plansYou can use event automation plans to specify actions that occur as a result ofevents 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 whenyou 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 canbe notified by e-mail or pager, for example, when a specified threshold is reachedor a specified event occurs. You also can configure an event automation plan tostart a program on a system and change a system variable when a specific eventoccurs. You can use process-monitor events and resource-monitor events to buildan event automation plan.

Successful implementation of event automation plans requires planning andconsideration of how you will implement them.

Planning system groupingEvent automation plans are best implemented by grouping all of your systems intoboth larger and smaller groups.

The following criteria are examples of groupings:

Type of system or resource (servers, desktop computers, workstations, mobilecomputers, and network equipment)

Each type of system or resource has its own event automation plans.

By manufacturerEach system manufacturer has its own event automation plans. Manyorganizations have systems from multiple manufacturers. In this case, if

92 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

manufacturer-specific event monitors are required, you might want to havemanufacturer-specific event automation plans for each type of system.

By functionEach function of the system has its own event automation plans. Eachgroup of systems performing specific roles has different events to monitor.For example, on all of your print servers, you might want to monitor theprint spoolers and printers.

By resourcesEvent automation plans are based on specific resources. Typically, theseevent automation plans monitor a specific resource outside of those in themanaged-object type of event automation plan. These resource eventautomation plans might apply to systems with more than one systemfunction but not to all systems of the same type.

By management technologyIf you have many devices that send SNMP traps, you can design eventautomation plans to act on those events.

Structuring event automation plansDetermine the overall structure of your event automation plans before you createthem. A little planning in advance can prevent wasted time and duplication ofeffort.

Consider the following examples of event automation plan structures:

A structure based on the areas of responsibility of each administratorServers are maintained and managed by one group of personnel, anddesktop computers and mobile computers are maintained by anothergroup of personnel.

A structure based on administrator expertiseSome organizations have personnel that specialize in particular types oftechnology. These individuals might be responsible for complete systems oronly certain software running on these systems.

A structure based on system functionServers performing different functions are managed differently.

A structure based on the type of eventExamples of some structures based on the type of event are monitoring aspecific process and monitoring for hardware events.

A structure based on workday shiftsBecause you can set up the event filters to be active during certain parts ofcertain days, you can structure your event automation plans and eventfilters according to the shift that will be affected by the events that areoccurring.

Structuring event filtersYou 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 determinewhether 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 thefilter 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 alltargeted systems.

Chapter 2. Planning 93

v The other event filter options besides the event type are common for all targetedsystems. These settings include the times the event filter is active, the severity ofthe event, and other attributes.

Event automation plans can include event filters with event types that are notgenerated by all systems. In such instances, you can apply the event automationplan to those systems, but it will have no effect. For example, if an event filter isbased on a RAID event and that event automation plan is applied to systems thatdo not have a RAID controller installed, the event filter has no events to filter, andtherefore, no actions are performed. If you understand this concept, you can createmore complex event automation plans, and you can reduce the number of eventautomation plans you have to build and maintain.

Using the Event Automation Plan wizard, you can select common event types tocreate an event automation plan quickly and easily. After you become familiar withthe common event type selections, you can decide whether you want to furtherrefine your event filters using the advanced event filter path in the EventAutomation Plan wizard.

The advanced event filter path provides a tree that displays all currently availableevent types. The currently installed plug-ins publish their events in the Event Typetree when IBM Systems Director Server or Common Agent starts.

Note:

v Whether the events are published when IBM Systems Director Server orCommon 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-inmight publish its events either when it is added to the installation or when theplug-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 panethat is below the Event Type tree.

Planning IBM Systems Director securityBefore deploying IBM Systems Director, determine what steps you need to take tosecure your environment.

Planning IBM Systems Director users and groupsBefore deploying IBM Systems Director, define user roles for your organization anddetermine 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 DirectoryAccess Protocol (LDAP) server, or accounts on the operating system of themanagement server) affects both the availability and security of IBM SystemsDirector Server. IBM Systems Director is shipped with LDAP authenticationsupport, but it is not enabled by default. LDAP support includes support forthe following LDAP servers:v IBM Tivoli Directory Serverv Microsoft Active Directoryv OpenLDAPWith LDAP authentication, it is easy to implement common roles and access forusers across multiple instances of IBM Systems Director Server. However, the

94 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

LDAP server must be secure in order to avoid unauthorized access tomanagement tasks and managed objects in IBM Systems Director.To help you make a decision, consider how IBM Systems Director will be usedto manage systems and objects in various locations. You can start by answeringthe 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 useraccounts be unique for each management server?

v Is there an existing LDAP directory, such as IBM Tivoli Directory Server orMicrosoft 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 willguide you when creating user groups, delegating management authority in IBMSystems Director, and creating managed-object groups. User roles can be basedon a job description, on the physical or geographic area of responsibility, or onother 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 rolesthat 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 forstorage devices.

v If management authority is allocated partially based on organizational roles,consider defining user roles that correspond to sets of privileges and tasksthat can be performed in IBM Systems Director, like software distribution,inventory collection, and configuring preferences for IBM Systems DirectorServer. Depending on the user's organizational role, the user probably needsaccess to only a subset of the available privileges and tasks.

Other criteria can also be used when defining user roles for IBM SystemsDirector. Whatever criteria are used to define user roles, remember that a usercan have multiple roles.

Important: Before assigning users an administrator role (such asSMAdministrator) or adding them to an administrator group (such assmadmin), carefully consider whether the user requires this level of authority.Users with this type access can modify or delete all system-level resources andresources for all other users, including operating-system and user files andprocesses.

Planning Secure Sockets Layer configuration on IBM SystemsDirector

IBM Systems Director Server provides, by default, a Secure Sockets Layer (SSL)certificate that supports HTTPS connections between IBM Systems Director Serverand targets such as storage devices, agents, and Web browsers. However, to ensureserver authentication, data privacy, and data integrity, you must replace the default

Chapter 2. Planning 95

certificate with either a self-signed certificate or a certificate that is signed by acertificate authority (CA), and you must change the keystore password.

It is not required that you use SSL to secure the network traffic between yourmanagement server and targets. However, configuring SSL ensures data integrityand data confidentiality between the management server and its targets. Thisprotection is especially important if you access IBM Systems Director from outsideyour network.

Note: Make sure that the host name you specify in the Common Name field of theSSL certificate matches the host name that you specify in the URL that you use toaccess the targets. For example, if you specify a long name for the host name in theCommon 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 accessthe targets. Complete the steps in the following procedure to make sure that youspecify 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 keystorepassword for SSL, complete the following steps:1. If you are replacing the default certificate with a new CA signed certificate:

a. Request a CA signed certificate. For information, see “Requesting a CAsigned certificate.”

Important: Do not continue with the remaining steps until you are ready toreceive the new CA signed certificate. Requests for new CA signedcertificates may take several days to process.

b. When you are ready to receive the new CA signed certificate, delete thedefault certificate. For information, see “Deleting the default certificate.”

c. Receive the CA signed certificate. For information, see “Receiving a CAsigned certificate.”

d. Update the Web container properties. For information, see “Updating theWeb container properties.”

e. Update the targets with the new certificate. For information, see “Updatingthe targets with the new certificate.”

2. If you are replacing the default certificate with a new self-signed certificate:a. Delete the default certificate. For information, see “Deleting the default

certificate.”b. Create a new self-signed certificate. For information, see “Creating a

self-signed certificate.”c. Update the Web container properties. For information, see “Updating the

Web container properties.”d. Update the targets with the new certificate. For information, see “Updating

the targets with the new certificate.”

Requesting a CA signed certificateYou can request a digital certificate from a certificate authority (CA). Becausecertificate authorities are public entities that issue certificates to identify otherentities, CA signed certificates provide a level of public trust. Therefore, this typeof certificate is better suited for your production environment.

Important: If you are creating a self-signed certificate, do not perform thisprocedure.

96 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

You must create a certificate-signing request (CSR) to request a digital certificatefrom 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 youspecify in your Web browser to reach IBM Systems Director Server. In mostcases, you must specify the fully-qualified host name. However, if you use ashort name in your URL, you must specify a short name for the CommonName.

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 certificaterequest, 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 atest certificate or a production certificate from the CA. However, in aproduction environment, you must request a production certificate.

Next, you must delete the default certificate once you are ready to receive the CAsigned certificate. For information, see “Deleting the default certificate.” and“Receiving a CA signed certificate.”

Deleting the default certificateIBM Systems Director Server provides, by default, a Secure Sockets Layer (SSL)certificate that supports HTTPS connections between IBM Systems Director Serverand targets such as storage devices, agents, and Web browsers. You must deletethis default certificate before you can replace it with either a self-signed certificateor a CA signed certificate. Also, you must change the keystore password.

If you requested a CA signed certificate, ensure you the CA signed certificate isready to be received before deleting the default certificate. Back up any files beforeyou edit them.

To delete the default certificate, complete the following steps:1. Stop IBM Systems Director Server by completing the applicable steps:

Option Description

For Linux Type the following command: smstop

Chapter 2. Planning 97

Option Description

For Windows 1. Right-click My Computer and selectManage.

2. In the Computer Management window,expand Services and Applications >Services.

3. In the Services pane, right-click IBMDirector Server and select Stop.

4. Exit from the Computer Managementwindow.

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 Directorinstallation. Note that this path uses the backslash (\) to delimit the directory;depending on the system that you are using, you might be required to enterthe path using the forward slash (/).

3. To open the default keystore file, click Key Database File > Open.4. In the Key database type list, select JKS.5. Click Browse and navigate to the applicable default keystore file:

Option Description

For Linux install_root/lwi/security/keystore/ibmjsse2.jks

For Windows install_root\lwi\security\keystore\ibmjsse2.jks

where install_root is the root directory of your IBM Systems Directorinstallation. Note that this path uses the backslash (\) to delimit the directory;depending on the system that you are using, you might be required to enterthe path using the forward slash (/).

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 SystemsDirector is ibmpassw0rd.

8. In the Key database content pane, select the default personal certificate namedlwiks and click Delete.

If you want to create a self-signed certificate, go to “Creating a self-signedcertificate”. If you requested a CA signed certificate, see “Receiving a CA signedcertificate.”

Receiving a CA signed certificateAfter the certificate authority (CA) accepts the certificate-signing request, the CAprocesses the request and verifies your identity. The CA sends the signed certificateback to you by way of e-mail. You must receive and save the new certificate in thedefault keystore file.

Before you complete this procedure, you must perform the following:

98 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

1. Create and submit a certificate-signing request. For information, see“Requesting a CA signed certificate.”

2. Delete the default certificate. For information, see “Deleting the defaultcertificate.”

3. 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 yourcertificate has a different file extension, see the IKeyMan User's Guide. Go to theIBM Support and Download Web site at www.ibm.com/support/us and searchusing the document number SC23-6510-00.If you are importing a certificate with a file extension of .pfx and errorsindicate that the certificate store is corrupt, see Resolving the iKeyman CorruptedDatabase Message. Go to the IBM Support and Download Web site atwww.ibm.com/support/us and search using the reference number PRS2855.

Important: If you are creating a self-signed certificate, do not perform thisprocedure.

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 acertificate file, for example, DirServerSecPubCert.arm.

Note: The e-mail message from the CA might include supplemental text infront of the certificate and after the certificate. For example, you might see thetext BEGIN CERTIFICATE in front of the certificate and END CERTIFICATE afterthe certificate. In this case, make sure that you cut and paste the supplementaltext 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

where install_root is the root directory of your IBM Systems Directorinstallation. Note that this path uses the backslash (\) to delimit the directory;depending on the system that you are using, you might be required to enterthe path using the forward slash (/).

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

where install_root is the root directory of your IBM Systems Directorinstallation. Note that this path uses the backslash (\) to delimit the directory;depending on the system that you are using, you might be required to enterthe path using the forward slash (/).

4. To open the default keystore file, click Key Database File > Open.5. In the Key database type list, select JKS.

Chapter 2. Planning 99

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

where install_root is the root directory of your IBM Systems Directorinstallation. Note that this path uses the backslash (\) to delimit the directory;depending on the system that you are using, you might be required to enterthe path using the forward slash (/).

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

where install_root is the root directory of your IBM Systems Directorinstallation. Note that this path uses the backslash (\) to delimit the directory;depending on the system that you are using, you might be required to enterthe path using the forward slash (/).

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 aswell as the public key associated with the certificate. This optional step canprovide additional security within your SSL configuration. Each target candetermine whether the server presents a certificate that is signed by a trustedsigner. If the target determines that the certificate is not signed by a trustedsigner, it displays a warning which alerts you to a possible security breach.Configuring SSL for targets is specific to each target. See the documentationfor 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 andclick OK.

20. To exit the IBM Key Management program, click Key Database File > Exit.

100 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Next, you must update the Web container properties. Go to “Updating the Webcontainer properties.”

Creating a self-signed certificateSelf-signed certificates are certificates that you create yourself for private use. Afteryou create a self-signed certificate, you can use it immediately. Because anyone cancreate self-signed certificates, they are not considered publicly trusted certificates.Therefore, use self-signed certificates only on a temporary basis while you testyour environment. You can replace the default certificate with a self-signedcertificate.

Before you complete this procedure, you must delete the default certificate. Forinformation see “Deleting the default certificate.” Also ensure that you back up anyfiles before you edit them.

Note: Messages and settings might differ depending on what type of target towhich 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 thisprocedure. 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 youspecify in your Web browser to reach IBM Systems Director Server. In mostcases, you must specify the fully-qualified host name. However, if you use ashort name in your URL, you must specify a short name for the CommonName.

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 andclick 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 Webcontainer properties.”

Updating the Web container propertiesBecause you changed the keystore password, you must update the Web containerproperties with the new keystore password.

Chapter 2. Planning 101

Before you perform this procedure, you must create a new certificate. You cancreate 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 withinthe webcontainer.properties file. Instead, you must create a file named sslconfig inthe same directory, edit the properties in the sslconfig file, and restart IBM SystemsDirector Server. The process of restarting IBM Systems Director Server encrypts thenew password in the Web container properties.

Note: Messages and settings might differ depending on what type of target towhich 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

where install_root is the root directory of your IBM Systems Directorinstallation. Note that this path uses the backslash (\) to delimit the directory;depending on the system that you are using, you might be required to enterthe path using the forward slash (/).

2. Change the name of the webcontainer.properties file towebcontainer.properties.bak.

3. In the same directory, create a file named sslconfig and copy the contents ofwebcontainer.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 Wherev 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 101 in “Creating a self-signed certificate”– Step 19 on page 100 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.

102 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Option Description

For Linux Type the following command: smstart

For Windows 1. Right-click My Computer and selectManage.

2. In the Computer Management window,expand Services and Applications >Services.

3. In the Services pane, right-click IBMDirector Server and select Start.

4. Exit from the Computer Managementwindow.

When you restart IBM Systems Director Server, the sslconfig file is used toautomatically create a new webcontainer.properties file and encrypt the newpassword in this file. After the new webcontainer.properties file has beencreated, IBM Systems Director Server deletes the sslconfig file because it is nolonger needed.

10. After you start and connect to IBM Systems Director Server, you can deletethe webcontainer.properties.bak file manually.

Next, you must update the target with the new certificate. Go to “Updating thetarget with the new certificate.”

Updating the target with the new certificateYou 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 100 in “Receiving a CA signed certificate”or if the public version of the CA signed certificate is already stored in the browsertruststore file, go to step 11 on page 104. Some targets contain the public version ofwell 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 isthe host name of IBM Systems Director Server and port_number is the port forIBM Systems Director Server. The default port is 8421.

Option Description

For Microsoft Internet Explorer A Security Alert window is displayed, forexample, you might see the followingmessage: The security certificate wasissued by a company you have not chosento trust. View the certificate todetermine whether you want to trust thecertifying authority. Continue to step 2on page 104.

For Firefox A Website Certified by an UnknownAuthority window is displayed. ClickAccept this certificate permanently andthen click OK. You Web browser is updatedwith the new certificate.

Chapter 2. Planning 103

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 hasbeen verified. Do you want to run the application? Be sure to selectAlways trust content from this publisher and click Yes.

Planning password management in IBM Systems DirectorBefore deploying IBM Systems Director, plan how you will manage passwords inyour environment.

You are required to supply many different credentials when installing andconfiguring IBM Systems Director. If you ever modify the user ID or password of acredential after specifying it during IBM Systems Director installation andconfiguration, you must ensure that any related tasks or other credentials areproperly updated to accommodate the change. For example, if you update theadministrator password in IBM DB2, you must ensure that you also updatereferences to that password in IBM Systems Director so that you can still use theapplication.

The following table lists the primary credentials that are required for IBM SystemsDirector installation and configuration along with the tasks that require eachcredential. The last column contains information about changing each password inIBM Systems Director after it is initially set. Use the table to determine linksbetween the credentials and tasks that might warrant further updates if youchange any one credential to help prevent any problems that you might encounterwhile running IBM Systems Director.

Note: This topic does not apply to credentials that you set up and use fordiscovery, such as for requesting access, because you use the IBM Systems DirectorWeb interface to manage those.

Table 40. Installation and configuration user IDs and passwords

Credential type Your valuesTasks that require thecredential

Procedure to change the password in IBMSystems Director

IBM Systems Directoradministrator using thelocal operating systemregistry

User ID:Password:

v Determining IBMSystems Directorservice accountinformation

v Installing IBMSystems DirectorServer

v Logging on to IBMSystems DirectorServer

Use the appropriate tools supplied by the localoperating system.

104 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 40. Installation and configuration user IDs and passwords (continued)

Credential type Your valuesTasks that require thecredential

Procedure to change the password in IBMSystems Director

IBM Systems Directoradministrator using anLDAP registry

User ID:Password:

v Determining IBMSystems Directorservice accountinformation

v Installing IBMSystems DirectorServer

v Logging on to IBMSystems DirectorServer

Use the appropriate tools supplied by LDAP.

Database systemadministrator

User ID:Password:

Preparing the databasefor use with IBMSystems Director

Use the appropriate tools supplied by thedatabase application.

Database runtimedatabase connectionadministrator(DbmsUserId,DbmsPassword)

User ID:Password:

Preparing the databasefor use with IBMSystems Director

Use a tool that can handle the passwordencryption to change the value in the dcm.xmlproperties file and also update thedatabase.properties value used by LWI.

Agent manager resourcemanager

User ID:Password:

Starting IBM SystemsDirector Server(configAgtMgr.sh script)

Use the cimsubscribe command.

LDAP administrator User ID:Password:

Setting up IBM SystemsDirector to use LDAPfor user authentication

Use the procedure in “Authenticating IBMSystems Director users stored in LDAP” tomodify the com.ibm.lwi.LDAPAdminPasswordpassword value in the security.properties file.

Chapter 2. Planning 105

106 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Chapter 3. Installing IBM Systems Director on themanagement server

Prepare your systems and install IBM Systems Director Server on the managementserver.

Note: After you install IBM Systems Director, update it to the latest version toensure that you have the most recent important fixes and enhancements. See“Updating IBM Systems Director” for instructions.

The DVD ISO image that contains IBM Systems Director 6.2.1 does not contain the6.2.1 agents. Obtain the 6.2.1 agents from the IBM Systems Director Downloadswebsite.Related reference

IBM Systems Director Downloads

Preparing the management serverBefore installing IBM Systems Director Server, make sure that the requirements thatare applicable to your system have been met.

Run the IBM Systems Director Pre-Installation Environment Checker to helpvalidate that the requirements that are applicable to your system have been met.See “IBM Systems Director Pre-Installation Environment Checker ”.

Preparing the database applicationUnless you want to use the default embedded database for your system, you mustprepare the database application for use with IBM Systems Director and configurethem to work together.

Ensure that you have chosen the supported database application that you will usewith IBM Systems Director. See “Choosing the IBM Systems Director databaseapplication” for information that will help you decide the database application touse.

The effort required to prepare the database depends on the database applicationthat you choose. Preparation might include one or more of the following tasks:v Downloading and installing the applicable database administrator clientv Downloading and installing the applicable Java Database Connectivity (JDBC)

driversv Creating a database or server IDv Configuring and starting a TCP/IP listenerv Setting the authentication mode.

To use a database other than your system's default database with IBM SystemsDirector, follow the steps in the appropriate topic to prepare your databaseapplication. If you are upgrading and migrating to IBM Systems Director 6.2, alsoensure that you follow the preparation instructions in “Preparation considerationsfor upgrading and migrating to IBM Systems Director”.

© Copyright IBM Corp. 1999, 2010 107

Note: You can install IBM Systems Director before preparing the database, but youwill only be able to use the default Apache Derby database until you configureIBM Systems Director Server to use a different database.

Tip: If you choose to use a custom remote database, it is important to understandthat data is stored and migrated differently on a remote database, and if you planto use the smsave and smrestore commands to migrate your remote databaseenvironment to a new release, you must use additional parameters to ensure thatall discovery and inventory data is restored correctly on the remote database. The-dbTargetDir directory command is required when migrating a remote database,and you must ensure that the user ID performing the migration has the correctauthority. For more information, see the smsave and smrestore topics listed below.

After the database application is prepared, you can install IBM Systems DirectorServer and configure it to connect to the database.

Preparing IBM DB2If you choose to use IBM DB2 as the database application for IBM SystemsDirector, there are some tasks that you need to complete to prepare your systembefore you install IBM Systems Director Server.

Follow the steps for your operating system to prepare IBM DB2 for use with IBMSystems Director.

Preparing IBM DB2 on AIX or Linux:

If you choose to use IBM DB2 as the database application for IBM SystemsDirector, there are some tasks that you need to complete to prepare your AIX orLinux system before you install IBM Systems Director Server.

The tasks that you need to complete are grouped into two categories: tasks for theIBM DB2 server, and tasks for the IBM Systems Director server. The IBM SystemsDirector server and IBM DB2 server can reside on two different systems or on thesame system. The tasks are the same and applicable to both scenarios. When onlyone system is used, you must run all the tasks on that system. From theperspective of the IBM Systems Director server, the database connection is alwaysremote and uses the TCP/IP protocol, even if both servers are on the same system.

Note: Do not use IPC to connect to the local IBM DB2 server instance.Related reference

DB2 information center

Technote: When Using DB2 as the Database for Systems Director Server onAIX, Database Connection May Fail after Rebooting the Director Server

Tasks for the IBM DB2 server:

To prepare the IBM DB2 server, complete the following tasks before you installIBM Systems Director Server:1. Install the IBM DB2 server. See the IBM DB2 Database for Linux, UNIX, and

Windows Information Center at publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp for instructions. See the “Supported database applications” topicfor supported versions and installation options.

2. Create an IBM DB2 server instance with TCP/IP support.

108 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Note: Use the graphical installer (db2setup) to install IBM DB2. This methodprovides an easy way to create the first server instance, the IBM DB2administrative instance, and all the required users and groups. If you use thetext based installer (db2install), then refer to the IBM DB2 Database for Linux,UNIX, and Windows Information Center at publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp for information about how to create a server instance andadministrative instance.

3. (Optional) Complete the following steps to set DB2_WORKLOAD to TPM onthe newly-created IBM DB2 server instance. TPM is a predefined setting thatturns on DB2_SKIPINSERTED, DB2_SKIPDELETED, andDB2_EVALUNCOMMITTED. Setting DB2_WORKLOAD to TPM improvesconcurrency through instance level configuration settings.a. Enter the following command to log in as or switch to the server instance

owner ID:su - owner_ID

b. Enter the following command to set the DB2_WORKLOAD flag to “TPM”:db2set DB2_WORKLOAD=TPM

c. If you are using IBM DB2 version 9.7 or later, enter the following commandto set the CUR_COMMIT flag to “on”:db2set CUR_COMMIT=ON

d. Enter the following command to start the instance:db2start

4. Create, in the same primary group as the IBM DB2 server instance ID, a uniquesystem user ID and password that IBM Systems Director Server will use toconnect to this instance. Remember these values as you will need to enter themon an installation panel or in the cfgdbcmd.rsp configuration file after the IBMSystems Director installation. Do not use the database administrator ID or anydefault database user ID or password.

Notes:

v Do not specify the same user ID in the cfgdbcmd.rsp configuration file as isspecified in the -dbAdmin parameter to cfgdbcmd. Doing so might result inan error or in having the user's administrator authority revoked. If youmistakenly used this configuration in the past, you might need to grantadministrator authority again to this user ID after the cfgdbcmd commandruns.

v If you plan to use smsave or smrestore with IBM Systems Director Serverand 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 instance owner is in the same primary group as

the IBM Systems Director user who will perform the backup and restoreoperations. This will enable the database server to read and write thedatabase backup image to the backup directory.

c. If you chose to create the IBM DB2 database yourself, verify how youconfigured the rollforward option. If this option is set to require userapproval, running smrestore will cause errors. Correct this issue now toavoid potential problems later with restoring data. See “smrestore failswhen IBM DB2 is configured to require approval of restore operation” formore information.

v When you create the runtime user account on the database server, the “usermust change password at next logon” option is selected by default. Ensure

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

that you either deselect this option or change the password beforeconfiguring IBM Systems Director. You must do this because the user isactually not given the opportunity to change the password and, when theyrun the cfgdbcmd command, the database configuration will fail. IBMSystems Director does not save the database server administrator account userID and password.

Tasks for the IBM Systems Director server:

To prepare the IBM Systems Director server, complete the following tasks beforeyou install IBM Systems Director Server:1. Install the IBM DB2 client. See the “Supported database applications” topic for

supported versions and installation options.

Note: If the IBM Systems Director server and the IBM DB2 server reside on thesame system, it is possible to use the same IBM DB2 installation for the IBMDB2 server instance and the IBM DB2 client instance, in which case it is notnecessary to install the IBM DB2 Data Server Client separately. However,installing a separate IBM DB2 Data Server Client ensures that you can movethe IBM DB2 server instance to a remote system without affecting the currentIBM Systems Director setup, and that you can apply IBM DB2 patches to theserver or client instance independently.

2. (Optional) Create an IBM DB2 client instance. If not done, IBM SystemsDirector does this for you as part of the database configuration.

Note: Use the graphical installer (db2setup) to install IBM DB2. This methodprovides an easy way to create the first client instance and the required usersand groups. If you use the text based installer (db2install), then refer to theIBM DB2 Database for Linux, UNIX, and Windows Information Center atpublib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp for information abouthow to create a client instance.

3. If you are moving an existing IBM DB2 database to IBM Systems Director 6.2.1,and you are using an IBM Systems Director server on AIX or Linux, you mustfirst set several environment variables. You can choose from a few differentoptions for setting the environment variables.

110 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Option Description

Manually create a dbvariables.properties file 1. Create a /lwi/conf/overrides/dbvariables.properties file to set the environmentvariables. After you complete this option, you do notneed to do it again. This file must set theenvironment variables for AIX or Linux as follows:

DBPATHSet the DBPATH environment variable to theIBM DB2 instance's /bin directory.

DBLIBPATHSet the DBLIBPATH environment variable tothe IBM DB2 instance's /lib directory. If youare using a 64-bit version of IBM SystemsDirector, you can set the directory to the/lib or /lib64 directory. If you are using a32-bit version of IBM Systems Director, youcan set the directory to the /lib or /lib32directory.

The following example shows what the file mightlook like:

DBLIBPATH=/home/db2inst1/sqllib/lib32DBPATH=/home/db2inst1/sqllib/bin

2. After you create the file, run the chmod command toensure that users that are not root users do not haveproblems accessing the file. Run the command asfollows: chmod 444 dbvariables.properties.

Run the cfgdbcmd command After you have upgraded to IBM Systems Director 6.2.1,run the cfgdbcmd command to configure and initializethe connection from the IBM Systems Director server toyour IBM DB2 database. Doing so creates a/lwi/conf/overrides/dbvariables.properties file withthe environment variables necessary for IBM SystemsDirector to work properly with your IBM DB2 database.Note: Do not run the smreset command after runningthe cfgdbcmd command. If you do, all database data willbe lost.After you complete this option, you do not needto do it again.

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

Option Description

Manually set the environment variables You can manually set the environment variables usingthe export command.Note: If you choose this option, each time you run thesmstart, smsave, and smrestore commands you mustalso set the environment variables again. Otherwise,errors will result.

For AIX , set the following environment variables usingthe export command:

PATH Set the PATH environment variable to the IBMDB2 instance's /bin directory.

LIBPATHSet the LIBPATH environment variable to theIBM DB2 instance's /lib directory. If you areusing a 64-bit version of IBM Systems Director,you can set the directory to the /lib or /lib64directory. If you are using a 32-bit version ofIBM Systems Director, you can set the directoryto the /lib or /lib32 directory.

The following example shows how to use the exportcommand to set the environment variables for AIX :

export PATH=$PATH:/home/db2inst1/sqllib/binexport LIBPATH=/home/db2inst1/sqllib/lib64

For Linux, set the following environment variables usingthe export command:

PATH Set the PATH environment variable to the IBMDB2 instance's /bin directory.

LD_LIBRARY_PATHSet the LD_LIBRARY_PATH environmentvariable to the IBM DB2 instance's /libdirectory. If you are using a 64-bit version ofIBM Systems Director, set the directory to the/lib or /lib64 directory.

The following example shows how to use the exportcommand to set the environment variables for Linux:

export PATH=$PATH:/home/db2inst1/sqllib/binexport LD_LIBRARY_PATH=/home/db2inst1/sqllib/lib32

4. Provide the database information to the system administrator who will installIBM Systems Director and configure it to use the database. The information willbe needed later to enter on an installation panel or in the cfgdbcmd.rspresponse file. The default response file is cfgdbcmd.rsp, which will reside in the<install_root>\proddata directory, where <install_root> is the root directoryof your IBM Systems Director installation.

112 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 41. Database configuration information and values

DescriptionDatabase configurationattribute Value (select or input)

Selected database applicationNotes:

v If you want to install IBM SystemsDirector Server and configure it bysetting options in a database-configuration response file, then thevalue for DbmsApplication must matchthe database value that you select.

v You must enter into the cfgdbcmd.rspresponse file the exact value for thedatabase as it appears here.

DbmsApplication DB2

Host name or IP address of the IBM DB2server instanceNote: A IBM DB2 database must always beconsidered remote, even if IBM SystemsDirector Server and IBM DB2 serverinstances reside on the same system.Therefore, a host name or IP address isrequired here.

DbmsServerName Custom value:Examples:

v host1.domain.com

v 127.0.0.1

Database nameNote: If the database does not exist, then itis created later on by the cfgdbcmd task. Ifthe database does exist, then it is used.

DbmsDatabaseName Custom value:Example: DIRDB01

Local installation folder in which the IBMDB2 client instance resides

DbmsDatabaseAppHome Custom value:Example: /home/db2clnt1/sqllib

TCP/IP service port number for the IBMDB2 server instance

DbmsTcpIpListenerPort Custom value:Example: 50000

User ID of the database user account thatwill be used to connect to the databaseNotes:

v Database tables are created under theschema for this user ID.

v If you will not use the databaseadministrator user ID for the runtimeconnection, provide a second user withaccess to the information collectionpanel.

DbmsUserId Custom value:Example: dirusr1

Password of the database user account DbmsPassword Custom value:

After you have prepared the IBM DB2 server and client instances for use with IBMSystems Director, you can connect IBM Systems Director Server to the databaseafter installation regardless of your system configuration. See the “Configuring thedatabase connection after IBM Systems Director installation” topic for theprocedure.

Note: The IBM DB2 Database for Linux, UNIX, and Windows Information Centerat publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp has currentinformation about security in IBM DB2.

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

Preparing the Oracle® DatabaseIf you choose to use Oracle® Database as the database for IBM Systems Director,there are some tasks that you must complete to prepare your system before youinstall IBM Systems Director Server.

Complete the following tasks to prepare Oracle® Database before installing IBMSystems Director Server:

Tasks for the Oracle server:

1. Install Oracle® Database. See the “Supported database applications” topic forsupported versions and installation options.

2. Start the database server.3. Create your Oracle® Database within the Oracle® Database Server.

Note: Ensure that the character set of your new database is UTF-8.4. Create a unique user ID and password on the database server for the runtime

database connection. Remember these values as you will need to enter them onan installation panel or in the cfgdbcmd.rsp configuration file after the IBMSystems Director installation. Do not use the database administrator ID or anydefault database user ID or password.

Notes:

v Do not specify the same user ID in the cfgdbcmd.rsp configuration file as isspecified in the -dbAdmin parameter to cfgdbcmd. Doing so might result inan error or in having the user's administrator authority revoked. If youmistakenly used this configuration in the past, you might need to grantadministrator authority again to this user ID after the cfgdbcmd commandruns.

v If you plan to use smsave or smrestore with IBM Systems Director Serverand 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 instance owner is in the same primary group as

the IBM Systems Director user who will perform the backup and restoreoperations. This will enable the database server to read and write thedatabase backup image to the backup directory.

v When you create the runtime user account on the database server, the “usermust change password at next logon” option is selected by default. Ensurethat you either deselect this option or change the password beforeconfiguring IBM Systems Director. You must do this because the user isactually not given the opportunity to change the password and, when theyrun the cfgdbcmd command, the database configuration will fail. IBMSystems Director does not save the database server administrator account userID and password.

Note: The user ID that is created must use the temporary tablespace “temp”. Ifyou receive errors while running the smreset command to create tables, youmight need to increase the size of the temporary tablespace.

Tasks for the IBM Systems Director Server server:

1. If you chose to install the Oracle® Database on a remote server, you must installthe Oracle® Database administrator client on the same system on which IBMSystems Director Server is installed.

114 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

2. Ensure that the following environment variables are correctly set prior to IBMSystems Director startup.

Note: For Linux on Power Systems and Linux on System z , you must belogged in as root user.

ORACLE_HOMEEnsure that this variable is set to the installation directory of theOracle® Database server or client.

PATH Add the bin directory under the ORACLE installation root directory tothe front of the system variable PATH.

Note: If you already have the bin directory in your PATH, but it is notthe first directory listed, consider moving it to the front of the PATHnow. The smsave command might fail to create a backup if the bindirectory is not at the front of the PATH.

LD_LIBRARY_PATH (Linux) or LIBPATH (AIX )

a. For 32-bit machine types, set this variable to<oracle_install_root>/lib/ or <oracle_install_root>/lib32/.

b. For 64-bit machine types, set this variable to<oracle_install_root>/lib/ .

Final tasks:

1. Update the tnsnames.ora and listener.ora files on the Oracle® Database serverhost to include the information for your newly created database. If the Oracle®

Database server is remote, ensure that the information for your newly createddatabase is also added to the tnsnames.ora file on your Oracle® Database client.See the Oracle® Database documentation for details.

2. If you will have multiple database instances in the listener.ora file, ensure thatyour Oracle® Database server is properly set up to support this situation.a. On the Oracle® Database server, enter either one of the following commands

to launch sqlplus:v sqlplus sys/Netf1n1ty@db_name as sysdba where db_name is the name of

the databasev sqlplus sys/Netf1n1ty as sysdba

b. In sqlplus, enter the following command to change the permissions of theremote login password file (REMOTE_LOGIN_PASSWORDFILE) to shared:SQL > alter system set remote_login_passwordfile=SHARED scope=spfile;SQL > shutdown immediate;SQL > startupSQL > quit

c. Ensure that your listener.ora file resembles the following example for eachdatabase instance (SID_DESC):SID_LIST_LISTENER =(SID_LIST =(SID_DESC =(SID_NAME = PLSExtProc)(ORACLE_HOME = C:\oracle\product\10.2.0\db_1)(PROGRAM = extproc)

)(SID_DESC =

(GLOBAL_DBNAME = db_name_2.oracle-10g2.netfinity.com)(SID_NAME = db_name_2)(ORACLE_HOME = C:\oracle\product\10.2.0\db_1)

)(SID_DESC =

(GLOBAL_DBNAME = db_name_1.oracle-10g2.netfinity.com)

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

(SID_NAME = db_name_1)(ORACLE_HOME = C:\oracle\product\10.2.0\db_1)

))

LISTENER =(DESCRIPTION_LIST =(DESCRIPTION =(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))(ADDRESS = (PROTOCOL = TCP)(HOST = oracle-10g2.netfinity.com)(PORT = 1521))

))

d. Ensure that the content in the tnsnames.ora file on your server with IBMSystems Director installed is consistent with your listener entries, like in thefollowing example:db_name_2 =

(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP) (HOST = oracle-10g2.netfinity.com) (PORT = 1521))(CONNECT_DATA =

(SERVER = DEDICATED)(SERVICE_NAME = db_name_2.oracle-10g2.netfinity.com)

))

db_name_1 =(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = oracle-10g2.netfinity.com) (PORT = 1521))(CONNECT_DATA =

(SERVER = DEDICATED)(SERVICE_NAME = db_name_1.oracle-10g2.netfinity.com)

))

3. Configure and restart the Oracle® Database TCP/IP listener.4. Provide the database information to the system administrator who will install

IBM Systems Director and configure it to use the database. The information willbe needed later to enter on an installation panel or in the cfgdbcmd.rspresponse file. The default response file is cfgdbcmd.rsp, which will reside in the<install_root>\proddata directory, where <install_root> is the root directoryof your IBM Systems Director installation.

Table 42. Database configuration information and values

DescriptionDatabase configurationattribute Value (select or input)

Selected database application DbmsApplication OracleNotes:

v If you want to install IBM SystemsDirector Server and configure it bysetting options in a database-configuration response file, then thevalue for DbmsApplication must matchthe database value that you select.

v You must enter into the cfgdbcmd.rspresponse file the exact value for thedatabase as it appears here.

Host name of the server on which thedatabase is installed

DbmsServerName Custom value:

Database name DbmsDatabaseName Custom value:Note: This value must match the name ofthe database that is created in the chosendatabase application.

Database system identifier (SID) (Oracle®

Database only)SID Custom value:

116 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 42. Database configuration information and values (continued)

DescriptionDatabase configurationattribute Value (select or input)

Fully qualified local installation folder ofthe database server instance or adminclient instance on the IBM Systems DirectorServer systemNote: This is the location of the SQLLIBdirectory. For example, a typical Windowsinstallation will specify this as C:\ProgramFiles\IBM\SQLLIB.

DbmsDatabaseAppHome Custom value:

TCP/IP listener port ID for the database DbmsTcpIpListenerPort Default or custom value:

User ID of the database user accountNote: If you will not use the databaseadministrator user ID for the runtimeconnection, provide a second user withaccess to the information collection panel.

DbmsUserId Custom value:

Password of the database user account DbmsPassword Custom value:

After you have prepared the database for use with IBM Systems Director, you canconnect the IBM Systems Director Server to the database either after or duringinstallation:

Connect the database after installationYou can connect the database after installation regardless of your systemconfiguration. See “Configuring the database application after IBM SystemsDirector installation” for the procedure.

Connect the database during installation (Windows only)If you are running on Windows, you also have the option of connectingthe database during installation. See “Installing IBM Systems DirectorServer on Windows using the InstallShield wizard” for the procedure.

Preparing firewalls and proxies for IBM Systems DirectorIf you have firewalls in your network, or if the management server must use aproxy server to access the internet, you must configure the firewalls and proxyserver to enable installation and operation of IBM Systems Director.

IBM Systems Director must be able to access all the managed objects in thenetwork, and if you will use a remote Web browser to access the managementserver, the remote systems running the Web browser and the management servermust have access to each other. In addition, some functions of IBM SystemsDirector, including update manager, require access to the Internet.

To enable this access, you must configure firewalls and proxies in your network toallow 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 andCommon Agent are open. See “All available ports” for a complete list of theports that IBM Systems Director components can use.

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

2. Ensure that internet connections exist to the following internet addresses asthey are required by IBM Systems Director and various plug-ins.

Note: IP addresses are subject to change, so ensure that you use DNS nameswhenever possible.

Table 43. Required internet connections

DNS name IP address Port(s) Protocol(s)

Update manager

www.ibm.com 129.42.56.216,129.42.58.216,129.42.60.216

443 or 80 https or http

www-03.ibm.com 204.146.30.17 443 or 80 https or http

download3.boulder.ibm.com 170.225.15.76 443 or 80 https or http

download3.mul.ie.ibm.com 129.35.224.114 443 or 80 https or http

download4.boulder.ibm.com 170.225.15.107 443 or 80 https or http

download4.mul.ie.ibm.com 129.35.224.107 443 or 80 https or http

delivery04-bld.dhe.ibm.com 170.225.15.104,129.35.224.104

443 or 80 https or http

delivery04-mul.dhe.ibm.com 129.35.224.115,170.225.15.115

443 or 80 https or http

delivery04.dhe.ibm.com 129.35.224.105,170.225.15.105

443 or 80 https or http

Service and Support Manager

eccgw01.boulder.ibm.com 207.25.252.197 443 https

eccgw02.rochester.ibm.com 129.42.160.51 443 https

www-945.ibm.com 129.42.26.224,129.42.34.224,129.42.42.224

443 https

www6.software.ibm.com 170.225.15.41 443 https

www.ecurep.ibm.com 192.109.81.20 443 https

testcase.boulder.ibm.com 170.225.15.31 21 ftps

3. If the management server requires access to the Internet but does not havedirect access, complete the following steps to configure the management serverto use the proxy when accessing the Internet.a. Ensure that the selected proxy server is configured to use basic

authentication. The update manager task supports only basic authenticationwith the proxy server. If digest or NTLM authentication are required,update manager will be unable to access update packages from IBM.

b. Use the update manager Settings page to configure the management serverto use the proxy server. See “Changing update settings” for moreinformation.

Related reference

Electronic Service Agent Web site

Preparing to install IBM Systems Director Server on AIXBefore installing IBM Systems Director Server on AIX , make sure that yourmanagement server meets the applicable requirements.

118 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Run the IBM Systems Director Pre-Installation Environment Checker to helpvalidate that the requirements that are applicable to your system have been met.See “Running the IBM Systems Director Pre-Installation Environment Checker onAIX and Linux” for instructions on how to run the IBM Systems Directorenvironment analysis tool.

Complete the following preparatory steps before installing IBM Systems DirectorServer on AIX :1. Ensure that your system meets the hardware and software requirements

(including those for databases, security, and networking) for installation, asdescribed in “Hardware and software requirements.” To verify the AIXoperating system level, run the following command:oslevel -s

The command should return a value such as 5300-09-00-nnn, where nnn isirrelevant.

2. Optional: Download updates for your system, if necessary. Download AIXoperating system updates from the “IBM Fix Central” Web site.

Note: Select “Power” or “System p” for the Product family and “AIX ” forthe Product.

3. Ensure that the following required openssl and openssh versions are installed:v openssl.base 0.9.8.4 or higherv if installed, openssh.base.server 4.5.0.5301 or higher

There is a dependency between openssl and openssh versions. If openssl isnot installed, it is installed as part of the server or agent installation. However,if this would create an inconsistency with the openssh version on the system,openssl is not installed and the installation fails.

Note: If you want to run the Agent Installation Wizard from the server,openssh is required. However, the server installation does not enforce opensshinstallation.

4. Note the following list of required file sets that are installed as part of the IBMSystems Director Server installation:v expect.base 5.42.1.0v tcl.base 8.4.7.0v tk.base 8.4.7.0

Note: Obtain any missing RPMs from the operating system distribution mediaor use a package manager to find and install a missing library or RPM. Forinformation on using a package manager to find and install a missing libraryor RPM, see “Using a Linux package manager to find libraries or RPMs”.

5. If a previous version of IBM Systems Director Server was installed on yoursystem, you can now safely uninstall the bash rpm if it is not used for anyother application. Previous versions of IBM Systems Director Server on AIXrequired that bash be installed. This dependency was removed in IBMSystems Director 6.2.Enter the following commands to uninstall bash:rpm -qa | grep bash # To determine the exact rpm namerpm -e bash_rpm_name

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

6. Ensure that the following file sets that are required for and installed withCommon Agent on AIX will not conflict with any other applications that areinstalled on your system:v sysmgt.cim.providers 1.2.9.0v sysmgt.cim.smisproviders 1.2.2.0v sysmgt.cimserver.pegasus 2.9.1v ICU4C.rte 5.3.9.0 (only AIX 5.3 systems)v xlC.aix50 10.1.0.2 (only AIX 5.3 systems)v xlC.rte 10.1.0.2 (only AIX 5.3 systems)

7. If you run the dconsole command using the IBM Systems Director Webinterface, ensure that the dsm.core file set installed. The server installationdoes not check if dsm.core is installed, but these functions will work only if itis. dsm.core is available on the product media for AIX 6.1 TL03 or later.

8. Verify /etc/hosts and /etc/netsvc.conf settings to ensure the success of IPaddress lookups for loopback. For more information, see Agent install timeoutdue to localhost lookup in the IBM Systems Director Best Practices Wiki.

9. Ensure that the installation is set to use ports that are not already in use. Bydefault, Common Agent requires ports 9510, 9514, and 9515 during installationand at runtime. If these ports are already in use when you install the agent,the installation will fail. A situation where these ports will be already in use isif you have a different version of the CAS agent installed, for example as partof the Tivoli Provisioning Manager agent.Complete the following steps to check for port use and, if any are in use,modify the Common Agent configuration to use different ports:a. Check if the ports are in use by running the following command:

netstat -an | grep LISTEN | egrep "951(0|4|5)"

b. On the agent system, modify the configuration to use different ports byrunning the following command:/var/opt/tivoli/ep/runtime/agent/toolkit/bin/configure.sh -unmanaged -portnot_9510 -jport not_9514 -nport not_9515 -force

where not_951x is any open port other than 951x.a. Rerun the installation script or install the Common Agent file set manually.

10. Ensure that the umask value on your system is set to 022 so that groups andusers have the permissions required to complete IBM Systems Director tasks.

11. Optional: If you want to use the FSP Proxy extension, which is necessary forthe Power Management tasks for standalone and IVM-managed hosts, ensurethat the following necessary file sets are installed.

Note: IBM Systems Director Server no longer automatically installs these filesets to prevent possible installation inconsistencies with CSM.

csm.hc_utils 1.7.0.0 or higher along with its CSM install requisitesThe CSM file sets are included on the AIX operating system media orcan be downloaded from the IBM Cluster Systems Management Website at http://www14.software.ibm.com/webapp/set2/sas/f/csm/download/home.html. Install each file set with SMIT or the followingcommand:installp -acgXYd fileset_location fileset_name

where fileset_location is the location of the downloaded file setsand fileset_name is the name of the file set that you are installing.

120 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Director.Server.ext.FSPProxy.rteObtain this file set from the IBM Systems Director for AIX, V6.2.1 DVDor the SysDir6_2_Server_AIX.tar.gz file. Install the file set with SMITor the following command:installp -acgXYd fileset_location Director.Server.ext.FSPProxy.rte

where fileset_location is the location of the downloaded file set.Related reference

AIX Toolbox for Linux Applications

IBM Fix Central

Installing IBM Systems Director on the management serverAfter preparing your system, use the IBM Systems Director Server installationprocedure for the operating system on which you plan install IBM SystemsDirector Server.

Note: You are advised to not install IBM Systems Director on the same system asIBM Storage Configuration Manager (SCM).

Installing IBM Systems Director Server on AIXAfter preparing your system, you can install IBM Systems Director Server on AIXby downloading the AIX installation file or using the IBM Systems Director for AIX,V6.2.1 DVD.

Important:

v The IBM Systems Director installation media for 6.2 is refreshed to include theupdates for 6.2.1. When running the installation from the refreshed installationmedia, the 6.2.1 updates are automatically included as part of the installation.The updates for 6.2.1 are found in the \update directory on the installationmedia. If you use a response file, you can edit the dirserv.rsp response file tospecify that the 6.2.1 updates should not be included as part of the installation.

v Installation of IBM Systems Director installs IBM Systems Director Server,Common Agent, and Platform Agent all together. Therefore, it is not necessaryto separately install Common Agent or Platform Agent on the managementserver after installing IBM Systems Director Server.

v Common Agent and Platform Agent are now shipped as part of the AIXoperating system:– Starting with AIX Version 5.3 TL10 and AIX Version 6.1 TL03, Common Agent

Version 6.1.0.3 and Platform Agent 5.20.3 are installed when you perform anoverwrite or a preservation operating system installation with the defaultoptions, which include the SystemMgmtClient bundle (AIX 6.1) or theGraphics bundle (AIX 5.3).

– Starting with AIX Version 5.3 TL11 and AIX Version 6.1 TL04, Common Agentand Platform Agent are installed when upgrading from a previous version ofAIX if a previous version of the agent is already installed. Both are alsoinstalled when you perform an overwrite or a preservation operating systeminstallation with the default options, which include the SystemMgmtClientbundle (AIX 6.1) or the Graphics bundle (AIX 5.3). The following agentversion are included:- AIX Version 5.3 TL11 and AIX Version 6.1 TL04 include Common Agent

6.1.0.4 and Platform Agent 6.1.2.0.

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

- AIX Version 5.3 TL12 and AIX Version 6.1 TL05 include Common Agent6.1.2.0 and Platform Agent 6.1.2.0.

- AIX Version 6.1 TL06 and AIX Version 7.1 include Common Agent 6.2.0and Platform Agent 6.2.0.

v Installing IBM Systems Director Server 6.2.1 on an AIX system on which theagent is already installed will update the agent to the 6.2.1 level if it is notalready at this level.

v By default, Common Agent is started when your system is rebooted. You candisable this function with the steps in the “Disabling IBM Systems Directoragents” topic.

v IBM Systems Director Server is not supported to run on a system with workloadpartitions (WPARs) enabled.

You can install IBM Systems Director Server on AIX from either installation mediaor from a downloaded installation package.

Important: The IBM Systems Director Server and Common Agent installationpackages for AIX are provided in English only.

Table 44. Installation options for IBM Systems Director Server on AIX

Installation method Title or file name

DVD media IBM Systems Director for AIX, V6.2.1 DVDNote: To obtain an image of the IBMSystems Director for AIX, V6.2.1 DVD,download the SysDir6_2_1_DVD_AIX.isofile.

Attention: If you use DVD media to installIBM Systems Director Server, ensure thatyou allot an additional 1.5 GB of availablespace in the /opt file system to contain theagent packages that are copied from theDVD at the end of the server installation.The packages are copied to/opt/ibm/director/packaging/agent on theserver. Installing IBM Systems DirectorServer from AIX 6.2.1 DVD media does notinstall the agents. This is an exception for6.2.1. TheSysDir6_2_1_Common_Agent_platform.jarfiles are provided in the agent subdirectoryof the DVD media.

Downloaded installation package SysDir6_2_Server_AIX.tar.gz (1.36GB)

Attention: When downloading theinstallation package file to your AIX server,you must first run the following commandto increase the default file size limit:

ulimit -f 4194302

After the installation process, you can configure a database to use with IBMSystems Director and change security settings.

122 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Note: If you plan to use the default Apache Derby database, you can choose eitherthe basic installation path, which configures Apache Derby by default, or thecustom installation path.

Installing IBM Systems Director Server 6.2.1 using the dirinstall.server script is theonly supported method. Network Installation Manager (NIM) is not supported forinstalling IBM Systems Director Server.

To install IBM Systems Director Server, log in as the root user and complete thefollowing steps:

Tip: You can find the installation logs for this process in /var/log/dirinst.logand /opt/ibm/director/log/installFeatures_date.log.1. Start the IBM Systems Director Server installation from the installation source:

Downloaded installation files: To start the installation from a Web download,complete the following steps:a. Run the following command to increase the default file size limit:

ulimit -f 4194302

b. Download the installation package from the IBM Systems DirectorDownloads Web Site at www.ibm.com/systems/management/director/downloads/.

c. To unzip and extract the contents of the installation package, type thefollowing command:gzip -cd <package_name> | tar -xvf -

where <package_name> is the file name of the download package.d. Run the following command to reset the default file size limit:

ulimit -f 2097151

e. Change to the directory in which the installation script is located. Type thefollowing 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 IBM Systems Director for AIX,V6.2.1 DVD, complete the following steps:a. Insert the DVD into the DVD-ROM drive.b. If the DVD does not automount, type the following command and press

Enter:mount -v cdrfs -o ro /dev /mnt

where dev is the specific device file for the block device and mnt is themount point of the drive.

c. To change to the directory in which the installation script is located, typethe following command and press Enter:cd /dvd_mnt/server/

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

database, copy the response file (dirserv.rsp) to a local directory and modifythe installation settings in your local copy.a. Type the following command and press Enter:

cp dirserv.rsp /directory/

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

where directory is a local directory.b. Open an ASCII text editor and modify the installation settings in the copy

of the dirserv.rsp file. This file is fully commented.You can specify the following items in the server response file:v Specify the log file optionsv Specify the Web console port numbersv Specify the Tivoli Provisioning Manager host name and IP addressv Specify migration optionsv Enable or disable the nonstop service, which keeps the server

continuously runningv Specify a different databasev Specify an different location from where to install updates.

Notes:

v In the response file, “1” indicates that an item is to be installed and “0”indicates that an item is not to be installed.

v If you wish to use the default for any value in the response file, commentout that value with a “#” symbol at the beginning of the line instead ofleaving the value blank.

v If you need to enter any Windows-based locations, ensure that youinclude the back slash after drive_letter:. For example, use C:\foldernameinstead of C:foldername.

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

Tip: After installation, keep the response file for future use and reference.3. To install IBM Systems Director Server, from within the directory in which the

installation script is located, type one of the following commands and pressEnter:

v To accept the default settings:./dirinstall.server

v To use the response file:./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 applicationother 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 databaseapplication at any point after the installation of IBM Systems Director Server,but you must not start the management server until it is completed. Startingthe management server before configuring IBM Systems Director to use adatabase application might result in a loss of function.

5. Complete the following steps to start IBM Systems Director Server:a. To configure the agent manager that the server will use to manage Common

Agent resources, type the following command and press Enter:install_root/bin/configAgtMgr.sh

b. Use the information in the “configAgtMgr command” topic to respond tothe configAgtMgr.sh script prompts. After you have provided all therequested information, the configuration of the embedded agent manager (if

124 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

chosen) and registration of IBM Systems Director Server as the resourcemanager with the embedded or existing agent manager begins. The agentmanager configuration script runs and displays a series of status messages.

c. If it is not already started, start IBM Systems Director processes on themanagement servers by running the smstart command:install_root/bin/smstart

See the “smstart command” topic for instructions.d. To view the IBM Systems Director Server status, type the following

command and press Enter:install_root/bin/smstatus -r

Note: You can use Ctrl+C to exit from smstatus -r if necessary. Ctrl+Ccauses the smstatus command to end.When this command returns a value of Active, the server is started.

6. Optional: Obtain and distribute any needed 6.1.x agent packages. If youupgraded from IBM Systems Director Server 6.1.x, the only agent deploymentpackages that are available by default are all applicable 6.2 agent packages (ifyou upgraded using the DVD media) or only the 6.2 subagent packages (if youupgraded using a downloaded installation package). Any agent deploymentpackages that were installed by default in 6.1.x or that you imported throughthe Agent Import task are no longer available. Therefore, complete thefollowing steps if you need to distribute the 6.1.x agent packages:a. If the 6.1.x agent packages do not still reside on the server system, find

them on the IBM Systems Director Downloads Web Site and downloadthem to any location on the server system.

b. In the IBM Systems Director Web interface, go to Release Management >Agents and click Import Agent.

c. Enter the directory path that contains the agent package that you want toimport and click OK. After a successful import, the 6.1.x packages willappear in the IBM Systems Director Web interface and will be ready fordistribution.

7. If you used the DVD for installation, complete the following steps to unmountthe 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.

The following CAS agent runtime files are created by cimserver during runtime:v /tmp/cimserver_start.conf

Note: This file is deleted when cimserver shuts down. This does not affectcimserver.

v /tmp/cimlistener_start.conf

Note: This file is deleted when cimlistener shuts down. This does not affectcimlistener.

v /tmp/elasocket_cimv2v /tmp/dpi_socket

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

If you have not already merged and installed the updates as part of theinstallation, then you can use update manager to update to the latest version ofIBM Systems Director. See “Updating IBM Systems Director” for instructions.

Note: Before performing an update, you will need to understand disk spacerequirements. For information on disk space requirements for updates, see“Determining disk space requirements for applying updates” or the IBM SystemsDirector Best Practices Wiki.Related reference

IBM Systems Director Downloads

IBM Systems Director Best Practices Wiki

Configuring the database connection after IBM Systems Directorinstallation

After IBM Systems Director installation, you can configure IBM Systems Director touse a different database application. During this process, any previous data thatwas collected will be lost.v Ensure that the database instance to which you are switching is already created

and accessible.v Ensure that all prerequisites for connecting to the database application are

installed and configured. See “Preparing the database application” forinformation.

v Ensure that IBM Systems Director Server is stopped before starting this task. See“smstop command” for information.

v Ensure that all passwords for your database configuration are encrypted. If theyare not, use cfgserver.bat or configDB.sh, as described in “Encryptingpasswords for database configuration”, to encrypt them.

Complete the following steps to use the cfgdbcmd.rsp file to configure yourdatabase: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 directoryof your IBM Systems Director installation.

2. In the cfgdbcmd.rsp file, ensure that the configuration information for yourchosen database is not commented out and that the configuration informationfor the other possible databases is 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 IBM Systems DirectorServer. So, to ensure that your chosen database is not commented out, removethe “;” character at the beginning of each applicable line for your database.

3. Use information from your local database administrator to fill in all of thefields needed for your chosen database application. See “Preparing the databaseapplication” for information about what you need to gather from eachapplicable database server.Attention: Ensure that you do not use any quotes in the response file as theywill 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.

126 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

6. After the encryption script is complete, run the cfgdbcmd tool. Depending onyour operating system, the file name of the tool is either cfgdbcmd.cmd orcfgdbcmd.sh. The cfgdbcmd tool will use the response file that you previouslyfilled in to properly connect IBM Systems Director Server to the chosendatabase. See “cfgdbcmd command” for information.

Note: The -dbAdmin and -dbAdminPW parameters for the cfgdbcmd tool servedifferent purposes than the DbmsUserId and DbmsPassword databaseconfiguration attributes in the cfgdbcmd.rsp file. The -dbAdmin and -dbAdminPWparameters for the cfgdbcmd tool must specify the user ID and password forthe database administrator or, in the case of IBM DB2, the instance owner ID sothat the tool has the authorization to create a database.

Tip: When running cfgdbcmd on a Linux or AIX operating system, it isrecommended that you omit the -dbAdmin and -dbAdminPW parameters forsecurity reasons. The tool will prompt for the administrator user ID andpassword if they are not provided. For example:cd /opt/ibm/director/bin./cfgdbcmd.sh -dbLocal false

7. After the cfgdbcmd tool completes, run the smreset command located in theinstall_root\bin folder to reinitialize the databases and clear all persistentdata. See “smreset command” for information.Attention: IBM Systems Director Server will not start correctly if you do notcomplete this step.

8. Start IBM Systems Director Server. See “smstart command” for information.9. After you have confirmed that the server is working well, you should consider

removing the old database that was configured. You can refer to thedocumentation for the specific database application for information about howto do that.

After the configuration is complete, IBM Systems Director Server is properlyconnected to your chosen database.

Attention: Connectivity problems with the database server will affect IBMSystems Director. For example, if the database server goes offline or becomesunreachable, IBM Systems Director Server will stop responding and hang.Related reference

Technote: IBM Systems Director Functions Fail Without Database Connectivity

Configuring IBM Systems Director Server after installationBefore you start using IBM Systems Director, review these recommendations forconfiguring systems and setting up your environment.

Configure IBM Systems Director Server after a successful installation, so that youcan get the most benefit from the product, and be able to work efficiently. Do notconfuse this task with Configuring Systems, which is a separate topic forconfiguring those resources that are controlled by IBM Systems Director.

Note: Before proceeding with the following instructions, you might need to specifya preferred IP address for the IBM Systems Director Server or exclude certain IPaddresses that you do not want Systems Director to manage. For example, if theserver on which you installed Systems Director has more than one network

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

interface card, specify one IP address for Systems Director to use to communicatewith managed resources. For more information, see “Configuring IP addressproperties.”

The Welcome page of IBM Systems Director provides a quick overview, as well aslinks 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 plansv Check for updates on discovered systems.v Set up additional user securityv Start configuring your systems

Configuring IBM Systems Director plug-ins and platformsThese plug-ins and platforms are used to manage the various features of IBMSystems Director. Check this list, and run the configuration tasks for those plug-insand 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 toconfigure 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 ServerAlthough the installation process has performed some of theconfiguration tasks for the IBM Systems Director Server, review thestatus page and make any necessary changes.

Update ManagerThere are no mandatory configuration tasks, but you are advised toclick on the Update Manager link to go to the summary page, and runthe Getting Started and Settings tasks.

Virtualization ManagerCreate a master image for Xen virtual servers.

Remote AccessConfigure Virtual Network Computing (VNC) and Remote Desktop, ifyou intend to use these Remote control features.

Storage ManagementConfigure SMI-S providers and external storage applications.

These plug-ins have no configuration tasks:v Discovery Manager

128 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

v Status Managerv Automation Managerv Configuration Managerv BladeCenter and System x Managementv Power Systems Managementv System z Management

Configuring the command line interfaceBefore running the smcli commands or displaying help for them, ensure thatrequired software is installed and the locale is correctly installed and configured onthe system.

You can run smcli commands locally on the management server or remotely byaccessing 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 othersystems that you might use to access the management server to run commands.

Note: (AIX only) Japanese, Korean, and Chinese fonts display correctly only whendisplaying man pages for smcli commands locally on the management server.1. (Windows only) Management servers running 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 andinstalling this file, see https://www.microsoft.com/downloads.

2. (AIX) If you choose to use a single byte or double-byte language with UTF-8encoding, the CLI displays output, messages, helps, and man pages correctlyonly when run locally on an AIX management server or remotely on an AIXdisplay exported from the AIX management server. When run remotely on anon-AIX display exported from the AIX management server, the characters willappear garbled.

3. Ensure that the desired locale is supported by IBM Systems Director and isinstalled correctly on the client system, from where smcli is run.

Tips:

v To verify languages supported by smcli, see Language specifications for smclicommands.

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 displayoperating-system specific man pages.

4. (AIX and Linux only) Set the environment variables LC_ALL and LANG to thedesired locale in which you want to run the commands using the exportcommand (for example, export LC_ALL=en and export LANG=en).

Tip: To verify that the system locale has changed, run some AIX or Linuxspecific commands and ensure that the operating-system-specific messages aredisplayed in the language you set.

5. (AIX and Linux only) The smcli man page are available only in English andJapanese. To view the view man pages in English, set the MANPATH

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

environment variable to /opt/ibm/director/man. To view the man pages inJapanese on an AIX system, set the MANPATH environment variable toopt/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 ensurethe Japanese locale is set correctly.

v (SUSE Linux only) Man pages are available only in English. They are notavailable in Japanese.

v v On AIX, man pages in Japanese display correctly only if you run thecommands locally on the management server with LANG=JA_JP (which is aUTF-8 locale).

v v For SUSE Linux Enterprise Server 9.x,, the man command only understandsEUC_JP encoding. You must convert the man page encoding from UTF-8 toEUC_JP to view the man pages, for example:

mkdir -p /tmp/man/man1

iconv -futf8 -teucjp /opt/ibm/director/man/ja/man1/command_name.1 >/tmp/man/man1/command_name.1

man -M /tmp/man/ command_name

Reviewing Microsoft Internet Explorer security optionsReview these instructions if you are using Microsoft Internet Explorer Webbrowsers that have Enhanced Security Configuration enabled, and are running onWindows Server 2003 or Windows Server 2008.

When using a Web browser with Enhanced Security Configuration enabled, someproperties of the IBM Systems Director Web interface might not display asexpected.

Internet Explorer Enhanced Security Configuration establishes a configuration foryour server and for Internet Explorer that decreases the exposure of your server topotential attacks that can occur through Web content and application scripts. As aresult, some Web sites might not display or perform as expected.

Using a server for Internet browsing is not a good security practice becauseInternet browsing increases the exposure of your server to potential securityattacks. It is a best practice recommendation that you run your Web browser on asystem that is not a server. However, if you must use a server running WindowsServer, you must turn off Internet Explorer Enhanced Security Configuration.

Complete the following applicable steps to disable Internet Explorer EnhancedSecurity: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:

130 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

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.

Configuring IP address propertiesConfigure IP address properties when your management server has more than oneIP address, when your network uses one or more subnets that IBM SystemsDirector does not manage, and when resources that you want to manage havemore than one IP address. Configure IP address properties by creating or updatingthe IPPreference.properties file.

Specifying the preferred IP address for the management serverWhen your management server has more than one IP address, specify the IPaddress that you want the server to use. For example, a server that has more thanone network interface card has more than one IP address. Specify the preferred IPaddress for the management server by creating or updating theIPPreference.properties file.

To specify the preferred IP address for the management server, perform thefollowing steps:1. Use a text editor to open an empty file named IPPreference.properties in the

following location: install_path/data/IPPreference.propertieswhereinstall_path is the path where you installed IBM Systems Director.

Note: If the /data/IPPreference.properties file exists, open the file with a texteditor, then go to the next step.

2. On a single line, type the following entry:com.ibm.director.server.preferred.ip=<IP_address>

whereIP_address is the IPv4 or IPv6 address for the management server.v Each entry in the IPPreference.properties file must be on a separate line.v To insert a comment, begin the line with a number (#) character.

Note: If a com.ibm.director.server.preferred.ip entry exists, confirm that thechange correctly supercedes the current entry.

3. Save and close the file.

For Systems Director to recognize the preferred IP address, you must restart themanagement server.

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

Excluding IP addressesExclude IP addresses for resources that you do not want IBM Systems Director tomanage or that have multiple IP addresses, or for subnets that you do not wantSystems Director to manage. To exclude IP addresses, create or update theIPPreference.properties file.

You can exclude one or more individual IP addresses, an IP address range, or anentire subnet. Consider the following examples:v When a managed resource has multiple network interface cards, exclude all but

the IP address that Systems Director uses to communicate with the resource.v When managed resources are on more than one subnet, exclude the subnet that

Systems Director does not use to manage resources.

To exclude IP addresses, perform the following steps:1. Use a text editor to open an empty file named IPPreference.properties in the

following location: install_path/data/IPPreference.propertieswhereinstall_path is the path where you installed IBM Systems Director.

Note: If the /data/IPPreference.properties file exists, open the file with a texteditor, then go to the next step.

2. Type the IP addresses that you want to exclude:com.ibm.director.agent.excluded.ip.prefix=<IP_addresses>

where IP_address is one or more IPv4 or IPv6 addresses or address ranges thatyou want to exclude.v To exclude one or more individual IP addresses, use a comma character (,) to

separate the IP addresses:com.ibm.director.endpoint.excluded.ip.prefix=192.168.53.1,192.168.53.22

To exclude an IP address range:com.ibm.director.endpoint.excluded.ip.prefix=192.168.53.1-192.168.53.150

To exclude a subnet, use the asterisk character (*) as a wildcard:com.ibm.director.endpoint.excluded.ip.prefix=192.168.*

Note:

v Each entry in the IPPreference.properties file must be on a separate line.v To insert a comment, begin the line with a number (#) character.

3. Save and close the file.

For Systems Director to ignore the excluded IP addresses, you must restart themanagement server.

Logging on to IBM Systems Director Server for the first timeAfter installing IBM Systems Director Server, you need to log on using a Webbrowser, discover managed systems, and request access to those managed systems.

You must already have installed and started IBM Systems Director Server beforebeginning this task.1. Log on to IBM Systems Director using a Web browser.

a. Point your browser to the following URL:

132 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

http://System_Name:Port_Number/ibm/console

where System_Name is the name of the system on which IBM SystemsDirector Server is installed and Port_Number is the first (lower) of twoconsecutive port numbers that you specified for the Web server to use. Thedefault 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 IBMSystems Director administrator user ID and password. Authorizedadministrator credentials include those for the root user or any user that isa member of the smadmin group.

c. Click Log in.

Note: A security alert window might be displayed before logging in. This isdue to incorrect configuration of the Secure Sockets Layer (SSL) certificate.For information see “Configuring Secure Sockets Layer (SSL) between IBMSystems Director and the Web browser client.”

2. Discover your managed systems. The first time you log on to IBM SystemsDirector Server, a Discover button is displayed. Click it to start discoveringyour managed systems.

3. Request access to your managed systems.Secured systems are displayed in IBM Systems Director Web interface with apadlock icon beside them in the Access field or column of the systems details.After a system is accessed, the padlock disappears and additional tasks andstatus information are available.The Access attribute for each resource shows the current access status. Youcannot request access to the resources that have the following types of accessstatus:v Offline: Use verify access instead.v OK: No further action is required. You already have access to these resources.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 requiresthe 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 that

belongs to the System group.e. Click Request Access.

You can now begin managing the systems you have discovered, or install agentson managed systems to enable additional management capabilities.

Restarting IBM Systems Director ServerRestarting the IBM Systems Director Server requires that you run one command tostop the management server processes and then run another command to startthem again.

Before you stop the IBM Systems Director Server, warn users to finish their workor stop the processes they are running.

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

To restart the IBM Systems Director Server, complete the following steps:

Note: You must run all the commands in the following procedure on the IBMSystems Director management server.1. Stop the IBM Systems Director processes that are running on the management

server.v If you are running AIX or Linux, run the following command: smstop.v If you are running Windows, run the following command: net stop

dirserver.2. Restart the IBM Systems Director processes that run on the management server.

v If you are running AIX or Linux, run the following command: smstart.v If you are running Windows, run the following command: net start

dirserver.3. Check to ensure that the IBM Systems Director Server started successfully.

v If you are running AIX or Linux, run the following command: smstatus[-r]. Without the -r option, the current server status is displayed. With the-r option, the command monitors the server status. The server startedsuccessfully when this command returns a value of Active.

Note: You can use Ctrl+C to exit from smstatus -r if necessary. Ctrl+Ccauses the smstatus command to end.

v If you are running Windows, check the status of the server by checking thesystem tray.

Enabling Dynamic IP supportIf the IP address of the system running IBM Systems Director Server changes,enabling the Dynamic IP support feature automatically re-configures IBM SystemsDirector Server and notifies the managed resources of the IP address change.

In IBM Systems Director 6.1.x and earlier releases, the IP address of themanagement server had to remain static. This meant that the IP address of themanagement server was not supposed to change after IBM Systems Director Serverwas installed on the system. In IBM Systems Director 6.2, changing the IP addressof IBM Systems Director Server is supported. If the IP address of the IBM SystemsDirector Server system changes, the embedded Dynamic IP feature automaticallydetects the changed IP address when the IBM Systems Director Server stops andstarts and initiates the following actions:v It re-configures IBM Systems Director Server for the new IP address.v It notifies the resources that are managed by IBM Systems Director Server that

the management server's IP has changed and the managed resources will beupdated to use the server's new IP address. This ensures that the resources thatare managed by IBM Systems Director Server maintain communication with theserver after its IP address has changed.

Restriction: This feature is not supported if you are managing 6.1.x commonagents. To use this feature, you must first upgrade 6.1.x common agents to 6.2.

The following manageable resource types support updating the IBM SystemsDirector Server IP address when it changes:v Operating systemv BCChassis

134 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

v Server (RSA, IMM, BMC)v HMCv IVMv StorageSubSystemv Switch

Attention: If you configure the switch to send SNMP traps to IBM SystemsDirector Server, the switch will not automatically update if the IP addresschanges. Because it requires a manual action from the user to set the SNMP trapdestination, it will also require a manual action to change it. Most switchessupport setting multiple SNMP trap destinations, so configure the switch to sendSNMP traps to both the primary IBM Systems Director Server IP address andany backup IP addresses to which IBM Systems Director Server could potentiallymove. However, this is only possible if it is known ahead of time that there is asmall set of IP addresses to which IBM Systems Director Server could potentiallymove.

Notes:

v Frequent IP address changes can drive network traffic in association withupdating the managed resources with the new IBM Systems Director Server IPaddress. IP address changes can also cause the IBM Systems Director ServerCPU utilization to increase and slow down overall performance for the timeperiod during which the IP address updates are sent to the managed resources.

v Dynamic IP does not support on-the-fly processing, meaning that it does notwork unless IBM Systems Director Server is restarted.

v IBM Systems Director Server should be started for the first time on the same IPaddress on which it was installed. Changing the IP address any time after thefirst startup is supported.

v Processing for an IP address change is not supported for the scenario where theconfiguration for one IBM Systems Director Server and data is captured with thesmsave command and restored to another IBM Systems Director Server with thesmrestore command and both of these IBM Systems Director Server instanceshave different IP addresses.

To enable the Dynamic IP function, complete the following steps when the IPaddress of the IBM Systems Director Server system changes:1. Stop IBM Systems Director Server.2. Change the IP address of the system on which IBM Systems Director Server is

installed.3. (AIX and Linux) Ensure that the new IBM Systems Director Server system IP

address is reflected in the /etc/hosts system configuration file. If it is not, IBMSystems Director Server might not be able to detect the IP address change.

4. Start IBM Systems Director Server.

Note: IBM Systems Director Server will take more time to start up (becomeactive) when it is restarted for the first time with a new or modified IP addressbecause it needs to configure itself to the new IP address.IBM Systems Director Server is active.

5. Perform Lite Query on the local operating-system agent by issuing thefollowing command in a command prompt or shell on the management system:smcli querysystem OID_of_local_OS_MEP 1

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

After you complete the above steps, the processes of reconfiguring and notifyingthe managed resources about the IP change will commence.

Note: It will take typically eight to ten minutes after IBM Systems Director Serverbecomes active for the IP address change notifications to be sent to the managedresources.

By default, IP address related processing is enabled (turned on) on IBM SystemsDirector Server. To turn the processing for an IP address change on or off, set thecom.ibm.usmi.kernel.localsystem.USMSLocalSystemService.enableIPChangeProcessing property in the install_root\lwi\conf\overrides\USMIKernel.properties file:

Turn IP address change processing onTo turn on IP address change processing, delete the property or set it to“true”:com.ibm.usmi.kernel.localsystem.USMSLocalSystemService.enableIPChangeProcessing=true

If this property is not set or present, the Dynamic IP change processingwill be enabled by default.

Turn IP address change processing offTo turn off IP address change processing, add or edit the property to set itto “false”:com.ibm.usmi.kernel.localsystem.USMSLocalSystemService.enableIPChangeProcessing=false

136 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Chapter 4. Preparing agentless managed systems

Prepare the agentless managed systems in your environment before you discoveror manage them with IBM Systems Director.

Note: A managed system might have more than one IP address (for example,when the system contains more than one network interface card). When amanaged resource has multiple IP addresses, specify which IP address SystemsDirector uses to manage the resource. To specify the IP address to use, you specifythat the management server ignore (or exclude) the other IP addresses associatedwith the resource. For more information, see “Excluding IP addresses.”Related reference

AIX Pegasus CIM server and providers

Configuring access to agentless managed systemsUsing an account other than root to access an agentless management systemenforces the appropriate security for the system while enabling more detailed auditrecords for access to the system. To configure access to an agentless managedsystem for a user account other than root, use the sudo utility.

Note: It is also valid to use the sudo utility to make a connection to the agentlesscapabilities of a system, even though there might be a platform agent installed onthe system. The platform agent has its own authentication for its CIM connection,but the sudo utility connection can be used along side the CIM connection foragentless capabilities.

The sudo utility is provided with Linux operating systems. To use the sudo utilitywith AIX systems, you will need to download and install the utility from the IBMAIX Toolbox Download Web site.

Perform these steps to configure access to agentless management systems for useraccounts other than root:1. On each agentless managed system, create the sudo configuration file (called

sudoers) if it does not already exist.On a Linux-based or AIX-based agentless managed system, the file should belocated in the /etc/sudoers directory.

2. Ensure that each user account to be used for access to the agentless managedsystem has authorization to run sudo commands.

3. In install_root/lwi/conf/overrides/USMi.properties file, set the followingsystem variable:com.ibm.usmi.server.security.cts.util.escalateUser=true

4. Restart the IBM Systems Director Server.

After configuring the agentless managed system, you can then request access tothe system through either the IBM Systems Director Request Access page, theConfigure Access page, or the Configure Systems Credentials page.

© Copyright IBM Corp. 1999, 2010 137

Sample sudo configuration fileUse the sample sudo configuration file as a basis for setting up configuration toagentless managed systems for a user account other than root.# sudoers file.## This file MUST be edited with the ’visudo’ command as root.# Failure to use ’visudo’ may result in syntax or file permission errors# that prevent sudo from running.## See the sudoers man page for the details on how to write a sudoers file.#

# Host alias specification

# User alias specification

# Cmnd alias specification

# Defaults specification

# Prevent environment variables from influencing programs in an# unexpected or harmful way (CVE-2005-2959, CVE-2005-4158, CVE-2006-0151)Defaults always_set_homeDefaults env_reset# Change env_reset to !env_reset in previous line to keep all environment variables# Following list will no longer be necessary after this change

Defaults env_keep = "LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATIONLC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONELC_TIME LC_ALL LANGUAGE LINGUAS XDG_SESSION_COOKIE"

# Comment out the preceding line and uncomment the following one if you need# to use special input methods. This may allow users to compromise the root# account if they are allowed to run commands without authentication.#Defaults env_keep = "LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATION

LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONELC_TIME LC_ALL LANGUAGE LINGUAS XDG_SESSION_COOKIE XMODIFIERS GTK_IM_MODULEQT_IM_MODULE QT_IM_SWITCHER"

# In the default (unconfigured) configuration, sudo asks for the root password.# This allows use of an ordinary user account for administration of a freshly# installed system. When configuring sudo, delete the two# following lines:Defaults targetpw # ask for the password of the target user i.e. rootALL ALL=(ALL) ALL # WARNING! Only use this together with ’Defaults targetpw’!

# Runas alias specification

# User privilege specificationroot ALL=(ALL) ALL

# Uncomment to allow people in group wheel to run all commands# %wheel ALL=(ALL) ALL

# Same thing without a password# %wheel ALL=(ALL) NOPASSWD: ALL

# IBM Systems Director provides the credentials required to establish connections# with each system. Therefore, be sure to specify “NOPASSWD” for each user/group.

# Samples# %users ALL=/sbin/mount /cdrom,/sbin/umount /cdrom# %users localhost=/sbin/shutdown -h now

diruser ALL=(ALL) NOPASSWD: ALL

138 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Preparing AIX managed systemsYou might need to configure certain AIX systems before you can discover themwith IBM Systems Director Server. Ensure that each AIX system that you want tomanage has been appropriately configured.

Typically, managed systems are first discovered using the discovery task in IBMSystems Director Web interface. Then, Platform Agent or Common Agent isinstalled on the managed systems directly from IBM Systems Director Webinterface. The configuration of some AIX managed systems, however, can preventdiscovery by IBM Systems Director Server.

Note: If an agentless system is running openssh 4.7.0.530, you cannot use theAgent Installation Wizard to remotely install the agent on AIX .

Complete the following steps on each AIX system to enable discovery by IBMSystems Director Server:1. Check if sshd is running by running the following command:

lssrc -s sshd

2. If sshd is not running, run the following command to start it:startsrc -s sshd

Preparing to manage a IBM BladeCenterIBM Systems Director can be deployed to manage the blade servers in a IBMBladeCenter chassis.

Preparing to manage a IBM BladeCenter chassis using IBMSystems Director Server on a non-blade server

You can install IBM Systems Director Server on a non-blade server. With thismanagement server you can manage one or more IBM BladeCenter units and theblade servers installed in them. You must configure the network so that thisinstallation is possible.

Complete the following steps to prepare to manage an IBM IBM BladeCenterchassis 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 IBMBladeCenter management module is first started, it searches for a DHCP server.If a DHCP server is not found, the IBM BladeCenter management moduleassigns IP address 192.168.70.125 to the external management port. Because thisstatic IP address is the same for all management modules, IP address conflictscan occur if you do not use a DHCP server and introduce multiple IBMBladeCenter chassis onto a network simultaneously. When you configure theIBM BladeCenter chassis, you assign static IP addresses to the switch moduleand the external and internal ports of the management module.

2. Set up a separate management network to configure and manage your IBMBladeCenter chassis and blade servers. By separating the LAN segment usedfor production from the LAN segment to which the IBM BladeCentermanagement module is connected, you can ensure that only authorized systemadministrators can connect to the IBM BladeCenter chassis and switch modules.Figure 2 on page 140 shows such a network configuration.

Chapter 4. Preparing agentless managed systems 139

3. If you intend to use Remote Deployment Manager (RDM), install RDM on themanagement server.

4. If you plan to use a database application other than Apache Derby, considerinstalling the database server on the management LAN.

5. Make sure that you have installed the latest version of the management modulefirmware. To download the firmware, go to the IBM Servers Web site atwww.ibm.com/servers/.

This network configuration ensures that applications running on the blade serverscannot modify chassis settings, because the blade servers have no connection toeither the management module or the switch module configuration ports.

Note: If you are using an IBM BladeCenter management module instead of anadvanced management module, only one of the following software applicationscan communicate with it at any given time:v Cluster Systems Management (CSM)v IBM Systems Director Serverv IBM Management Processor Command-Line Interface (MPCLI)

Preparing to manage a IBM BladeCenter chassis using IBMSystems Director Server on a blade server

You can install IBM Systems Director Server on a blade server. With thismanagement server you can manage the IBM BladeCenter unit, including theserver on which IBM Systems Director Server is installed, and other IBMBladeCenter units. You must configure the network so that this installation ispossible.

Consider the following issues when managing the IBM BladeCenter unit thatcontains the management server:v Enable access for authorized administrators as determined by the security policy

established for the user environment.

Figure 2. Example of IBM BladeCenter deployment network when IBM Systems DirectorServer is not installed on a blade server

140 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

v Be careful when making changes to the configuration of the IBM BladeCenterchassis from IBM Systems Director itself. Such changes could effectively removethe instance of IBM Systems Director Server from the network and halt theentire IBM Systems Director environment.Specifically, do not perform these tasks on the blade server where IBM SystemsDirector Server is installed without careful consideration:– Powering off that blade server– Changing the boot options on that blade server

v Create a network setup that enables the IBM BladeCenter Management Moduleto communicate with the management server. Otherwise IBM Systems Directorwill be unable to discover the IBM BladeCenter chassis that contains themanagement server.

By default, the blade servers installed in a IBM BladeCenter chassis cannotcommunicate automatically with the IBM BladeCenter Management Module. Thisarchitecture is designed to prevent the blade servers from modifying the IBMBladeCenter chassis settings. If you install IBM Systems Director Server on a bladeserver and want to use the instance of IBM Systems Director to manage the IBMBladeCenter unit in which the management server is installed, you must enablecommunication 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 IBMBladeCenter management module is first started, it searches for a DHCP server.If a DHCP server is not found, the IBM BladeCenter management moduleassigns IP address 192.168.70.125 to the external management port. Because thisstatic IP address is the same for all management modules, IP address conflictscan occur if you do not use a DHCP server and introduce multiple IBMBladeCenter chassis onto a network simultaneously. When you configure theIBM BladeCenter chassis, you assign static IP addresses to the switch moduleand the external and internal ports of the management module.

2. Set up a separate management network to configure and manage your IBMBladeCenter chassis and blade servers. By separating the LAN segment usedfor production from the LAN segment to which the IBM BladeCentermanagement module is connected, you can ensure that only authorized systemadministrators can connect to the IBM BladeCenter chassis and switch modules.Figure 2 on page 140 shows such a network configuration.

3. To use an installation of IBM Systems Director Server on a blade to manage theIBM BladeCenter unit in which the management server is installed, enablecommunication between the Campus LAN and the Management LAN. Figure 3on page 142 shows such a network configuration.

4. If you plan to use a database application other than Apache Derby, considerinstalling the database server on the management LAN.

5. Make sure that you have installed the latest version of the management modulefirmware. To download the firmware, go to the IBM Servers Web site atwww.ibm.com/servers/.

Chapter 4. Preparing agentless managed systems 141

With this configuration, IBM Systems Director Server can communicate through theCampus LAN to the Management LAN and then onto the management module.

Note: If you are using an IBM BladeCenter management module instead of anadvanced management module, only one of the following software applicationscan communicate with it at any given time:v Cluster Systems Management (CSM)v IBM Systems Director Serverv IBM Management Processor Command-Line Interface (MPCLI)Related reference

IBM Servers

Preparing Hardware Management Console devices for discovery withIBM Systems Director

Before discovering Hardware Management Console (HMC) devices, and afterupgrading HMC hardware, you might need to open the Pegasus and SLP ports toenable IBM Systems Director to discover and manage the HMC.

Complete the following steps to enable the Pegasus and SLP ports on the HMCdevice:1. In the HMC Navigation Area pane, click HMC Management.2. In the HMC Management pane, click Change Network Settings.3. In the Customize Network Settings window, click the LAN Adapters tab.4. Select the LAN Adapter that is connected to your LAN and click Details.5. In the LAN Adapter Details window, click the Firewall Settings tab. The

Available Applications table displays a list of applications, with theirassociated port numbers, that are recognized by the HMC. The Allowed Hoststable displays a list of only those applications for which the HMC firewall isconfigured to allow access to the HMC.

Figure 3. Example of IBM BladeCenter deployment network when IBM Systems DirectorServer is installed on a blade server

142 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Note: If a scroll bar appears on the table, use it to view all the applications inthe table.

6. In the Available Applications table, select Open Pegasus and click AllowIncoming. Open Pegasus is added to the Allowed hosts table of enabled ports.

7. In the Available Applications table, select SLP and click Allow Incoming. SLPis added to the Allowed hosts table of enabled ports.

8. Click OK; then click OK again.9. If a message window about restarting the HMC is displayed, click OK. After

the HMC is restarted, the ports are enabled and IBM Systems Director Servercan discover the HMC.

Related reference

AIX Pegasus CIM server and providers

Chapter 4. Preparing agentless managed systems 143

144 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Chapter 5. Discovering systems and collecting inventory data

To manage a resource within an environment or view inventory data about it, thatresource must first be discovered and, after access is granted, an inventory must becollected. The resource is recognized and added to the comprehensive list of nativeresources and native attributes for the system. Discovery and inventory collectionare the two primary tasks that are used to connect to supported network resourcesand collect information about them.

Discovery protocolsA discovery protocol is any network communication protocol that IBM SystemsDirector Server uses during the discovery process to discover a resource.Gettingstarted discovery uses a predetermined list of protocols. When you specify a singleIP address, a single host name, or a single range of IP addresses, system discoveryuses one or more protocols based on the selected target resource type. Using adiscovery profile enables you to refine the target resource type and configurespecific protocols that you want to use.

The communication protocols that IBM Systems Director Server uses duringdiscovery depend on the protocols used by the target resource type. You need todecide about the different protocols only when you create or edit a discoveryprofile. The Discovery Profile wizard helps you select and configure the correctprotocol for the type of resource that you want to discover.

When discovering a large number of resources, network traffic associated with thediscovery process might cause timeouts that result in some discoverable resourcesremaining undiscovered. To help prevent this problem, use one or more discoveryprofiles. Using a discovery profile enables you to target specific resources and limitthe number of communication protocols used during discovery. Limiting thenumber of communication protocols used when discovering a large number ofresources helps avoid problems caused by network traffic collisions and timeouts.

By default, IBM Systems Director supports the following discovery protocols:

Agent manager discoveryAgent manager discovery specifically targets the discovery of Tivolicommon agents. In the Tivoli paradigm, Service Location Protocol (SLP) isnot supported and management servers contact an agent manager thatknows about the agents in their environment. You can select the agentmanagers that you want to use in discovery.

Common Agent Services (CAS) discoveryCAS discovery utilizes Service Location Protocol (SLP) discovery, withwhich clients can locate servers and other services on the network.

Common Information Model (CIM) discoveryCIM discovery utilizes the Service Location Protocol (SLP) for discovery.With CIM discovery, clients can locate servers and other services on thenetwork.

Interprocess communication (IPC) discoveryIPC is the process by which programs send messages to each other.Sockets, semaphores, signals, and internal message queues are commonmethods of interprocess communication. IPC is also a mechanism of an

© Copyright IBM Corp. 1999, 2010 145

operating system that enables processes to communicate with each otherwithin the same computer or over a network. IPC leverages services thatIBM Systems Director provides that components use to communicate witheach other. By using these services, a server task can communicate with anagent task running on a target.

Secure shell (ssh) discoverySecure shell is a Unix-based command interface and protocol for securelyaccessing a remote computer. With ssh discovery, you can specify either asingle IP address or a range of IP addresses upon which to run discovery

Simple Network Management Protocol (SNMP) discoverySNMP is a network management standard widely used in TCP/IPnetworks. SNMP performs management services by using a distributedarchitecture of management systems and agents. SNMP provides a methodof managing network hosts such as workstation or server computers,routers, bridges, and hubs from a centrally-located computer runningnetwork-management software.

Storage Management Initiative Specification (SMI-S) discoveryWith SMI-S discovery, clients can locate servers and other services on thenetwork. It is a design specification developed by the Storage NetworkingIndustry Association (SNIA) that specifies a secure and reliable interfacewith which storage management systems (SMSs) can identify, classify,monitor, and control physical and logical resources in a storage areanetwork (SAN). The interface integrates the various devices to be managedin a storage area network (SAN) and the tools used to manage them.

Windows Distributed component object model (DCOM) discoveryUse Windows DCOM (an extension of the Microsoft Component ObjectModel (COM) to support objects distributed across a network)configuration to specify either a single IP address or a range of IPaddresses upon which to run discovery.

Note: Additional discovery protocols are routinely created by vendors. For moreinformation about communicating with a device that uses a protocol that is notlisted here, contact the manufacturer or software provider for that device.

Discovering systems with system discoveryUse the system discovery task to discover one or more resources based on aspecific IP address, host name, or range of IP addresses or by using a discoveryprofile. You can also use system discovery to discover properly configured systemsthat use mirrored images. View the results of the current system discovery or asystem discovery that ran previously.

System discoveryTo discover systems at a specific network address or range of addresses, usesystem discovery. This method is useful in networks in which both broadcast andmulticast messages are filtered.

System discovery discovers Agentless managed systems, Platform Agent managedsystems, and Common Agent managed systems by sending a unicast request toone or more addresses. IBM Systems Director Server sends one request to eachsystem at a time. You can also use system discovery to discover systems that use amirrored image (cloned systems).

146 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

System discovery provides the following functions:v Discovery based on a single IP addressv Discovery based on a range of IP addressesv 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 communicatewith target resources by using a predetermined list of protocols.

Performing a system discoveryUse the System Discovery task to discover one or more resources by specifying asingle IP address, single host name, or a single range of IP addresses, or by using adiscovery profile.

To perform a system discovery, complete the following steps:

Note:

v Discover only those resources that you intend to manage with IBM SystemsDirector. For example, if the management interfaces of your networkingequipment are on a single subnet, yet you do not intend to manage yournetworking equipment with IBM Systems Director, do not discover devices onthat subnet.

v When discovering a large number of resources, network traffic associated withthe discovery process might cause timeouts that result in some discoverableresources remaining undiscovered. To help prevent this problem, use one ormore discovery profiles. Using a discovery profile enables you to target specificresources and limit the number of communication protocols used duringdiscovery. Limiting the number of communication protocols used whendiscovering a large number of resources helps avoid problems caused bynetwork traffic collisions and timeouts.

1. Open the System Discovery page using either of these two methods:v On the Start page 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 45. System discovery methods

To do this task: Complete these steps:

Use a single IPv4 or IPv6 address 1. Select Single IPv4 address or SingleIPv6 address from the Select a discoveryoption field.

2. In the IP address field, type the IPaddress of the system that you want todiscover.

3. If you want to discover only a specificresource type, select it from the Selectthe resource type to discover list.

Chapter 5. Discovering systems and collecting inventory data 147

Table 45. System discovery methods (continued)

To do this task: Complete these steps:

Use a range of IPv4 or IPv6 addresses 1. Select Range of IPv4 addresses or Rangeof IPv6 addresses from the Select adiscovery option field.

2. For the IP address range that containsthe systems that you want to discover,type the complete low-end IP address inthe Starting IP address fields and thelast piece of the high-end IP address inthe Ending IP address field.

3. If you want to discover only a specificresource type, select it from the Selectthe resource type to discover list.

Use the host name of a system 1. Select Single host name from the Selecta discovery option field.

2. In the Host name field, type the hostname of the system that you want todiscover.

3. If you want to discover only a specificresource type, select it from the Selectthe resource type to discover list.

Use an existing discovery profile 1. Select Select a discovery profile to runfrom the Select a discovery option field.

2. Select the profile that you want to usefrom the Discovery profile to run field.

Create and use a discovery profile 1. Click Create new profile underAdvanced Tasks.

2. Use the Discovery Profile wizard tocreate a discovery profile. After savingthe profile, the System Discovery pagedisplay automatically, and the profileyou created is already selected.

3. Run the discovery.v Click Discover Now if you want to run the discovery immediately.v Click Schedule if you want to schedule the discovery to run at a specific

time. The Job Launcher page is displayed. Use the Job Launcher page toconfigure the Schedule, Notification, and Options settings for the discoverytask.

The System discovery page updates in the following ways:v A message displays information about the job under which the discovery

task runs.v When the discovery task runs immediately, a status icon and text message

indicate the status of the discovery process.v As the process discovers manageable resources, the Discovered Manageable

Systems table displays them. The Discovered Manageable Systems tabledisplays the resources that are discovered during the current discovery andthose resources that were discovered previously.

v The Discover Now and Schedule buttons are deactivated and the Stop andNew Discovery buttons appear.

4. Optional: If you want to stop the discovery process, click Stop. If you want torun a new discovery while the current discovery continues to run, click NewDiscovery. When you choose to run a new discovery, the Discovered

148 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Manageable Systems table displays results for the new discovery only. To viewthe results of the current discovery, use the Discovery jobs task.

As the process discovers manageable resources, the Discovered ManageableSystems table displays them, including those resources that were discoveredpreviously.

Note: After a resource is discovered, the virtual systems that are associated withthat resource are also discovered.v To view the results of a specific discovery that ran at a previous time or a

discovery that is scheduled to run at a later time, use the Discovery jobs task.v To view all discovered resources, use the Resource Explorer task.

Note: The time it takes for discovery to finish processing varies depending onsuch factors as network performance and the number of systems that arediscovered. Avoid managing newly discovered resources for a time after thediscovery task finishes, because associated processing continues to run.

When the discovery process completes, the status icon and text message disappearand the Discover Now and Schedule buttons become active again.

Using system discovery to view current resultsUse the System Discovery task to view a table that contains the results of yourcurrent system discovery task.

To use the System Discovery task to view the system discovery results as youdiscover systems, complete the following steps:1. Open the System Discovery page using either of these two methods:

v On the Start page on the Welcome page, click System discovery underOptional tasks.

v In the IBM Systems Director Web interface navigation area, expandInventory and then click System Discovery.

The System Discovery page is displayed.2. Discover systems by using one of the available methods.3. View systems as they are discovered in the Discovered Manageable Systems

table.

Note: When you are viewing results of a system discovery, consider thefollowing items:v Displayed results include resources discovered by other IBM Systems

Director users who are accessing the same management server to performdiscoveries. So the Discovered Manageable Systems table displays resultsthat might include additional resources that are not located at the target IPaddresses or host names that you expect.

v When you click New Discovery to run a new discovery while a previousdiscovery is still running, the Discovered Manageable Systems table doesnot include results for the previous discovery. To view results for theprevious discovery, you must use the Discovery Jobs task or the Active andScheduled Jobs task.

After the discovery process completes, all the discovered manageable systems aredisplayed in the Discovered Manageable Systems table. The table maintains theinformation until you close the Systems Discovery page, at which time it is cleared.

Chapter 5. Discovering systems and collecting inventory data 149

Note: Any discovered manageable system also is listed in one or more groups onthe Resource Explorer page.

Accessing a secured system with request accessUse the Request Access page to request access to a secured system if themanagement server to which you are connected has not yet authenticated to thesystem. You must be able to access the system before you can perform tasks orremotely access the system.

Ensure that you have the correct authorization to access the secured system.

Note: Agent access points are all access points that have an access type other thanconsole. If certain types of agent access points (for example, CAS or IPC) exist on aresource, you must use this process to access all agent access points on the system.This process creates the necessary credentials and mappings, but they cannot beviewed or managed. For other types of agent access points on the securedresource, you have the option of using the Configure Access task to request access.

Secured systems are displayed in IBM Systems Director Web interface with apadlock icon beside them in the Access field or column of the systems details.After a system is accessed, the padlock disappears and additional tasks and statusinformation are available.

The Access attribute for each resource shows the current access status. You cannotrequest access to the resources that have the following types of access status:v Offline: Use verify access instead.v OK: No further action is required. You already have access to these resources.

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 thesame 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 clickRequest Access on the Configure Access page.

4. On the Request Access page, type the user ID and password of a user thatbelongs to the System group.

Note: You can use the sudo utility to configure agentless managed systemsrunning AIX or Linux so that they are accessible by a user withoutadministrator privileges.

5. Click Request Access. Credentials are created and authenticated to themanaged system in an attempt to access it.

If the access request is successful, the access status for the managed systemchanges to OK.

If the access status changes to Partial Access, then the access request wasunsuccessful for at least one access point. Click Configure Access to see the list of

150 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

access points and their access states. If necessary, to create additional credentials,click an access point that does not have an access state of OK and repeat thisprocedure.

Chapter 5. Discovering systems and collecting inventory data 151

152 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Chapter 6. Installing agents

Prepare your managed systems and environment for agent and subagentinstallation and then install Common Agent, Platform Agent, virtualizationmanager subagent, or IBM Systems Director z/VM manageability access pointagent.

When IBM Systems Director Server is updated to 6.2.1, the common agent that isinstalled on the same system with IBM Systems Director Server is updated to 6.2.1as well. If the local common agent has been updated to 6.2.1 before IBM SystemsDirector Server, then the IBM Systems Director Server update to 6.2.1 will fail.

Note: A managed system might have more than one IP address (for example,when the system contains more than one network interface card). When amanaged resource has multiple IP addresses, specify which IP address SystemsDirector uses to manage the resource. To specify the IP address to use, you specifythat the management server ignore (or exclude) the other IP addresses associatedwith the resource. For more information, see “Excluding IP addresses.”Related reference

IBM Systems Director Agent Deployment Cookbook

Preparing a Common Agent managed systemBefore installing Common Agent on a managed system, ensure that therequirements 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 IBMSystems Director Server, ensure that the PasswordAuthentication value in/etc/ssh/sshd_config is set to yes. So, the corresponding line in the sshd_configfile will appear as follows:PasswordAuthentication yes

Note: You must restart the ssh server for any changes made to sshd_config to takeeffect.

Obtaining licenses for Common AgentIBM Systems Director includes licenses for up to 20 installations of Common Agenton non-IBM x86 systems. To install Common Agent on additional non-IBM x86systems, 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/about/director52/about52/buy/.

Preparing to install Common Agent on AIXBefore installing Common Agent on AIX , make sure that your platform meets theapplicable requirements.

© Copyright IBM Corp. 1999, 2010 153

Starting with AIX Version 5.3 TL10 and AIX Version 6.1 TL03, Common AgentVersion 6.1.0.3 and Platform Agent 5.20.3 are installed when you perform anoverwrite or a preservation operating system installation with the default options,which include the SystemMgmtClient bundle (AIX 6.1) or the Graphics bundle(AIX 5.3).

Starting with AIX Version 5.3 TL11 and AIX Version 6.1 TL04, Common Agent andPlatform Agent are installed when upgrading from a previous version of AIX if aprevious version of the agent is already installed. Both are also installed when youperform an overwrite or a preservation operating system installation with thedefault options, which include the SystemMgmtClient bundle (AIX 6.1) or theGraphics bundle (AIX 5.3). The following agent version are included:v AIX Version 5.3 TL11 and AIX Version 6.1 TL04 include Common Agent 6.1.0.4

and Platform Agent 6.1.2.0.v AIX Version 5.3 TL12 and AIX Version 6.1 TL05 include Common Agent 6.1.2.0

and Platform Agent 6.1.2.0.v AIX Version 6.1 TL06 and AIX Version 7.1 include Common Agent 6.2.0 and

Platform Agent 6.2.0.

IBM Systems Director 6.2.1 provides fresh installation images for Common Agenton AIX that you can use for a fresh installation or to update an existing 6.1.x or6.2.0 agent. You can use update manager to update an existing Common Agentinstallation to 6.2.1. You cannot use update manager to update an existing PlatformAgent installation to 6.2.1.

Complete the following preparatory steps before installing Common Agent on AIX:1. Ensure that your system meets the hardware and software requirements

(including those for databases, security, and networking) for installation, asdescribed in “Hardware and software requirements.” To verify the AIXoperating system level, run the following command:oslevel -s

The command should return a value such as 5300-09-00-nnn, where nnn isirrelevant.

2. Optional: Download updates for your system, if necessary. Download AIXoperating system updates from the “IBM Fix Central” Web site.

Note: Select “Power” or “System p” for the Product family and “AIX ” for theProduct.

3. Ensure that the following required openssl and openssh versions are installed:v openssl.base 0.9.8.4 or higherv if installed, openssh.base.server 4.5.0.5301 or higher

There is a dependency between openssl and openssh versions. If openssl is notinstalled, it is installed as part of the server or agent installation. However, ifthis would create an inconsistency with the openssh version on the system,openssl is not installed and the installation fails.

Note: If you want to deploy the agent to an agentless system from a serverusing the Agent Installation Wizard, openssh is required on the agentlesssystem. However, the server installation does not enforce openssh installation.

154 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

4. Ensure that the following file sets that are required for and installed withCommon Agent on AIX will not conflict with any other applications that areinstalled on your system:v sysmgt.cim.providers 1.2.9.0v sysmgt.cim.smisproviders 1.2.2.0v sysmgt.cimserver.pegasus 2.9.1v ICU4C.rte 5.3.9.0 (only AIX 5.3 systems)v xlC.aix50 10.1.0.2 (only AIX 5.3 systems)v xlC.rte 10.1.0.2 (only AIX 5.3 systems)

5. Verify /etc/hosts and /etc/netsvc.conf settings to ensure the success of IPaddress lookups for loopback. For more information, see Agent install timeoutdue to localhost lookup in the IBM Systems Director Best Practices Wiki.

6. Ensure that the installation is set to use ports that are not already in use. Bydefault, Common Agent requires ports 9510, 9514, and 9515 during installationand at runtime. If these ports are already in use when you install the agent, theinstallation will fail. A situation where these ports will be already in use is ifyou have a different version of the CAS agent installed, for example as part ofthe Tivoli Provisioning Manager agent.Complete the following steps to check for port use and, if any are in use,modify the Common Agent configuration to use different ports:a. Check if the ports are in use by running the following command:

netstat -an | grep LISTEN | egrep "951(0|4|5)"

b. On the agent system, modify the configuration to use different ports byrunning the following command:/var/opt/tivoli/ep/runtime/agent/toolkit/bin/configure.sh -unmanaged -portnot_9510 -jport not_9514 -nport not_9515 -force

where not_951x is any open port other than 951x.a. Rerun the installation script or install the Common Agent file set manually.

Installing agents using the Agent Installation WizardYou can use the Agent Installation Wizard to install agent packages on managedsystems.

IBM Systems Director Server requires a number of agent packages that can bedeployed to managed systems using the Agent Installation Wizard.

Note: If you install IBM Systems Director Server 6.2.1 from the DVD media, the6.2 agent packages are imported, unless you are installing from the AIX DVDmedia, in which case no agent packages are imported. If you install IBM SystemsDirector Server from the Web download file, no agent packages are imported forany operating system. So, regardless of the installation method that you use, youneed to download the 6.2.1 agent packages separately.

The imported agent packages are located in the dynamic group “Agent PackageGroups” and can be accessed by clicking Release Management > Agents in thenavigation area. You use the Agent Installation Wizard to select one of these agentpackages to install and one or more systems on which to install the agent package.Then, the wizard creates an agent installation job that can run immediately or at ascheduled time.

Complete the following steps to import the agent packages:

Chapter 6. Installing agents 155

1. Download the remote agent packages from the “IBM Systems Director Agentsfor Remote Deployment with Agent Installation wizard” section of the IBMSystems Director Downloads Web Site at www.ibm.com/systems/management/director/downloads/.

2. Copy the packages to a location of your choice on the IBM Systems DirectorServer system.

3. Import the packages with the Agent Installation Wizard.4. Make any required changes to the diragent.rsp and or platform.rsp response

files. See the topic for your operating system under “Installing Common Agentmanually” or “Installing Platform Agent manually” for instructions about howto change the response files.

Note: If you install IBM Systems Director Server 6.2.1 from the AIX DVD media,no agents are automatically imported. However, the 6.2.1 agent packages forremote deployment are provided on the media so that you can easily import themmanually.

Complete the following steps to install agents using the Agent Installation Wizard: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 or subagent package that you want to install in theAvailable list.

Note: A subagent plugs-in to a base agent and provides additionalcapabilities to support IBM Systems Director plug-ins such as IBM SystemsDirector VMControl. This documentation uses the collective term “agents”to refer to both agents and subagents.

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 ormore agent packages might already be displayed in the Selected list.

v The Agent Installation Wizard can install only one agent package at atime. 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 packagein 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 ormore systems might already be displayed in the Selected list.

v Depending on the agent package being installed, some selected systemsmight not be valid targets for installation. The wizard checks the selected

156 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

systems for some or all of the following criteria to ensure that thesystems are valid targets for installing the selected agent package beforeallowing you to continue:– operating system family– operating system version– operating system distribution– operating system name– server architecture

c. Click Next.5. In the Agent Installation Wizard Summary page, review the Selected Agents

and Selected Systems lists to ensure that they are correct.v If the selections are not correct, click Back and make the necessary changes.v If the selections are correct, click Finish.

After you click Finish, the Run - Install Agent window opens.6. In the Run - Install Agent window, click the Schedule tab. On this page, you

can choose to run the job immediately or schedule the job to run at a later time.a. A job name is required and the Name field provides a unique default name.

To change the default name, type a job name in the field.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 theweekend.

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 issent 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 followingcriteria is met:v When the job begins.v When the job completes 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 thenumber of systems on which the job had errors. Therefore, if the job runson five systems, the job has errors on two systems, and you set thecriterion 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 therespective systems' clocks are set.

Chapter 6. Installing agents 157

b. Select whether you want the job to fail if a system is offline or if you wantthe 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 fromwhich you started the Scheduler. If the job creation fails, a message is displayedin the Run window so that you can correct the job.The job created by the Agent Installation Wizard will transfer the agentself-extracting script and the agent response file into the following directory,which depends on your version and agent level, on the target system:

6.x Common Agent/tmp/commonagent_tmp

6.x Platform Agent/tmp/platformagent_temp

5.x Common Agentinstall_root/SwDistPk

After the files are copied, the installation file sets are extracted into the /tmpdirectory and installed. The files are then removed after a successfulinstallation. You need to ensure that there is sufficient space on the targetsystem to copy the self-extracting script and extract the file sets. Refer to thespace requirements as specified in “Hardware requirements for systemsrunning Common Agent or Platform Agent”.If the agent deployment completes with errors, check the log file for your targetoperating system for a possible root cause:v AIX and Linux: /var/log/dirinst.log

Note: For more information about error log files, see “Information to provideto the IBM Technical Support Center or IBM Systems Director customer forum”.

Notes for AIX:

v Refer to “Installing Common Agent on AIX ” for more detail on theself-extracting script and the response file options.

v For AIX server and agents, it is less space consuming to remotely installagents using NIM as explained in the IBM Systems Director Best Practiceswiki page “Installing IBM Systems Director Common Agent for AIX usingNIM” at http://www.ibm.com/developerworks/wikis/display/WikiPtype/Installing+IBM+Systems+Director+Common+Agent+for+AIX+using+NIM.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.

158 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Chapter 7. Updating IBM Systems Director

Use “Update IBM Systems Director” in the IBM Systems Director Web interface toautomatically obtain and install all types of updates for IBM Systems Director.

Consider these points when updating IBM Systems Director:v Most update manager methods cannot determine the applicability of updates to

a system unless inventory was previously collected on the system.v You must restart IBM Systems Director to activate installed updates.

To instruct update manager to take most defaults and update IBM SystemsDirector almost automatically, complete the following steps:1. From the IBM Systems Director Web interface Welcome page, click Update IBM

Systems Director. When the check for updates task completes, the updatesneeded by the IBM Systems Director Server are displayed in the table.

2. Optional: If your management server does not have an IPv4 connection to theInternet, you can download IBM Systems Director updates fromwww.ibm.com/support/fixcentral/ and then use update manager to importand install the updates. See “Downloading IBM Systems Director updateswithout an Internet connection” for more information.

3. Click Download and Install to run or schedule the update.4. After the installation is complete, restart IBM Systems Director to activate the

updates.

© Copyright IBM Corp. 1999, 2010 159

160 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Chapter 8. Upgrading and migrating IBM Systems Director

You can upgrade and migrate information from earlier versions of IBM SystemsDirector and IBM Director. The method of migration that you use depends on theproduct versions from and to which you are migrating.

Database preparation considerations for upgrading and migrating toIBM Systems Director 6.2.x

Before upgrading and migrating any version of IBM Director or IBM SystemsDirector to IBM Systems Director 6.2.x, ensure that you properly prepare yoursystem.

General considerations

Ensure that you adhere to the following items for all systems:1. Ensure that you have enough free storage space to save your data with the

smsave command. Each system has its own set of storage needs that depend onmany, including the following, factors:v The type of database that you are using with IBM Systems Director. Some

database types require more storage space than others.v If the database server is local or remote to the management server. If the

database server is remote, the disk space needs are split across themanagement server and the database server. Database storage will consumethe majority of the smsave data, so most of the disk space needs will fall onthe database server and you will not need as much space on themanagement server.

v If you are migrating any plug-ins, such as Active Energy Manager, alongwith IBM Systems Director. The presence of plug-in data will most likelygreatly increase your storage needs.

As a general rule, you can take the size of your current database, add 1 GB toit, and use that as your storage space requirement for the smsave data. See thedocumentation for your database server for instructions for determining itsactual size.

Note: If you are not sure which database type IBM Systems Director is using,the install_root\lwi\conf\overrides\database.properties file will list it.

2. Certain versions of IBM Systems Director plug-ins are not compatible with IBMSystems Director 6.2, so ensure that you take the appropriate precautions foryour plug-in. See “Upgrading and migrating IBM Systems Director plug-ins”for more information.

Considerations for IBM DB2

If you are using IBM DB2, ensure that you adhere to the following items:v If IBM Systems Director Server is on a Windows machine and you are using an

IBM DB2 9.1 database, ensure that the IBM DB2 9.5 database client is ready butnot yet installed. If you are already using an IBM DB2 9.5 (or later) database,you do not need to install a new IBM DB2 database client.

© Copyright IBM Corp. 1999, 2010 161

Note: Installing the newer client displaces the older client, which is needed tosave the IBM Systems Director 6.1.x data.

v If you are using an IBM DB2 9.1 database client, complete the following step foryour operating system.

Note: The IBM DB2 9.5 database client is recommended.– AIX and Linux: Install the IBM DB2 9.5 administration client and create a

database instance before migrating to IBM Systems Director 6.2.v For AIX and Linux there are special database considerations. IBM Systems

Director 6.1.x is 32-bit and uses 32-bit versions of the database client or serverlibraries even on 64-bit systems. IBM Systems Director 6.2 is 64-bit and 64-bitdatabase libraries are used. Prior to migration on a 64-bit system, verify thatyour environment variable (LD_LIBRARY_PATH for Linux or LIBPATH for AIX) is set to point to the 32-bit database library versions. For example,LD_LIBRARY_PATH=/home/db2inst1/sqllib/lib32. After migration, theenvironment variable will need to be updated to point to the 64-bit locations.For example, LD_LIBRARY_PATH=/home/db2inst1/sqllib/lib. If your IBM SystemsDirector 6.1.x server and local database server or client run on a 32-bit system,you will not need to make any changes to your environment variable aftermigration.

v Ensure that you know the database name, the administrator user ID andpassword, and the database server machine name that you used before and thatthey are still accessible. The IBM Systems Director 6.2 installer will use the sameinformation to reconnect.

v If your database is on a remote server, ensure that you create a folder on thatdatabase server with permissions such that the IBM Systems Director smsaveprocess has write access.

v See “Migration to DB2 Version 9.5” in the IBM DB2 9.5 information center forfurther IBM DB2 migration considerations.

v If your database was configured to require approval of restore operations, youshould disable that option. If you do not disable the approval requirement, thesmrestore command will fail during upgrade to IBM Systems Director 6.2.To determine if your database is set to require approval of restore operations,run the following command on your IBM DB2 server, where db_name is thename of your IBM Systems Director database:db2 get db cfg for db_name

The output of this command includes lines for the following parameters:LOGRETAIN, LOGARCHMETH1, and LOGARCHMETH2. If any of these parameters are set toRECOVER or a state other than OFF, you must set the parameter to OFF toavoid problems restoring the database.To set a parameter to OFF, run the following command on your IBM DB2 server,where db_name is the name of your IBM Systems Director database, andlog_parameter is the parameter that must be set to OFF:db2 update db cfg for db_name using log_parameter no

Considerations for Microsoft SQL Server and Microsoft SQLServer Express

If you are using Microsoft SQL Server or Microsoft SQL Server Express, ensure thatyou adhere to the following items:v Before initiating the IBM Systems Director 6.2 installation, copy the Microsoft

SQL Server JDBC 2.0 driver on your local machine from where you installedMicrosoft SQL Server or downloaded the jar file.

162 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

v You might need to log off of the operating system and log back on afterextracting the JDBC 2.0 driver to make sure that all environment variables areset correctly.

v The 32-bit and 64-bit database clients are both compatible with Microsoft SQLServer.

v Keep the Command Line tool installed and unchanged.v Ensure that you know the database name, the administrator user ID and

password, and the database server machine name that you used before and thatthey are still accessible. The IBM Systems Director 6.2 installer will use the sameinformation to reconnect.

v If your database is on a remote server, ensure that you create a folder on thatdatabase server with permissions such that the IBM Systems Director smsaveprocess has write access.

Considerations for Oracle® Database

If you are using Oracle® Database, ensure that you adhere to the following items:v For AIX and Linux there are special database considerations. IBM Systems

Director 6.1.x is 32-bit and uses 32-bit versions of the database client or serverlibraries even on 64-bit systems. IBM Systems Director 6.2 is 64-bit and 64-bitdatabase libraries are used. Prior to migration on a 64-bit system, verify thatyour environment variable (LD_LIBRARY_PATH for Linux or LIBPATH for AIX) is set to point to the 32-bit database library versions. For example,LD_LIBRARY_PATH=oracle_install_root/lib32. After migration, the environmentvariable will need to be updated to point to the 64-bit locations. For example,LD_LIBRARY_PATH=oracle_install_root/lib64. If your IBM Systems Director 6.1.xserver and local database server or client run on a 32-bit system, you will notneed to make any changes to your environment variable after migration.

v Ensure that you know the database name, the administrator user ID andpassword, and the database server machine name that you used before and thatthey are still accessible. The IBM Systems Director 6.2 installer will use the sameinformation to reconnect.

v If your database is on a remote server, ensure that you create a folder on thatdatabase server with permissions such that the IBM Systems Director smsaveprocess has write access. On AIX and Linux, run chmod 777 on this directory sothat the Oracle® Database user ID can write to it.

Related reference

Migration to DB2 Version 9.5

Upgrading and migrating to IBM Systems Director 6.2.1 from 6.1.xUse this process to upgrade and migrate to IBM Systems Director 6.2.1.

The IBM Systems Director 6.2.1 installation process checks whether any priorversions of IBM Systems Director are installed. If a 6.1.x version is detected, userdata for IBM Systems Director and plug-ins, such as Active Energy Manager andVMControl, can be automatically migrated.

Attention: If your existing plug-in is not compatible with IBM Systems Director6.2.1, you will be unable to migrate it with this process. You will need to insteadinstall IBM Systems Director 6.2.1, obtain and install a compatible version of yourplug-in, and then migrate your plug-in data. See “Upgrading and migrating IBMSystems Director plug-ins” for information about migrating specific plug-ins.

Chapter 8. Upgrading and migrating 163

Note: If you do not want to migrate existing data, you might need to take extrasteps. See “Upgrading and migrating IBM Systems Director on the managementserver” for further information.

To upgrade and migrate to IBM Systems Director 6.2.1 from 6.1.x, complete thefollowing steps.1. Upgrade to IBM Systems Director 6.2 using the standard installation and follow

the migration path. See “Upgrading and migrating IBM Systems Director onthe management server” for full instructions for upgrading and migrating toIBM Systems Director 6.2 on each operating system. Then perform the nextstep.

2. Update to IBM Systems Director 6.2.1 using update manager. See "UpdatingIBM Systems Director" for instructions.

Note: Dependent on how you updated to IBM Systems Director 6.2.1, the localplatform agent might still be at the 6.2 level. To determine this, check the/opt/ibm/director/version.lv1 file on AIX and Linux. To update the PlatformAgent, refer to “Upgrading the IBM Systems Director agents”.

Upgrading and migrating to IBM Systems Director 6.2.1 from 6.2Use this process to upgrade and migrate from IBM Systems Director 6.2 to IBMSystems Director 6.2.1.

To upgrade and migrate to IBM Systems Director 6.2.1 from 6.2, complete thefollowing steps.1. Determine the disk space requirements. See “Determining disk space

requirements for applying updates”.

Note: The /tmp filesystem requires approximately 2 GB of free space and the/var filesystem requires approximately 100 MB of free space.

2. Update to IBM Systems Director 6.2.1 using update manager. See "UpdatingIBM Systems Director" for instructions.

Upgrading and migrating to IBM Systems Director from IBM Director5.x

To migrate user information from IBM Director to IBM Systems Director 6.2, firstupgrade and migrate to IBM Systems Director 6.1.x.

You cannot directly migrate user information from IBM Director to IBM SystemsDirector 6.2. To migrate the information, first upgrade and migrate to IBM SystemsDirector 6.1.x. For more information, see “Upgrading and migrating IBM SystemsDirector” (http://publib.boulder.ibm.com/infocenter/director/v6r1x/topic/director.upgrade_6.1/fqm0_t_upgrading_and_migrating.html) in the IBM SystemsDirector 6.1.x information center.

To complete the upgrade and migration from IBM Director to IBM SystemsDirector 6.2, migrate the 6.1.x user information during the IBM Systems Director6.2 installation process. For more information, see “Upgrading and migrating toIBM Systems Director 6.2 from 6.1.x,”

164 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Upgrading and migrating IBM Systems Director plug-insWhen upgrading and migrating to IBM Systems Director 6.2, you need to keep inmind certain requirements for your specific plug-ins. You might need to implementvarious extra steps during the process depending on the version compatibility ofyour plug-in with IBM Systems Director 6.2.

Use the information in this topic and in the documentation for your specificplug-in when upgrading and migrating to IBM Systems Director 6.2.

For a complete list of available IBM Systems Director plug-ins and for links to thedocumentation for each plug-in, see the IBM Systems Director Web site atwww.ibm.com/systems/management/director/plugins/.

Keep in mind the following items when you upgrade and migrate to IBM SystemsDirector 6.2:

Service and Support Manager

If you attempt to upgrade and migrate using the smsave and smrestore migrationscripts, you will lose all existing Service and Support Manager data, includingsaved problem and support file data. Therefore, instead upgrade and migratethrough the IBM Systems Director installation path to ensure that this data carriesover.

IBM Systems Director Network Control

IBM Systems Director Network Control V1.1 is not compatible with IBM SystemsDirector 6.2, but you can migrate an existing IBM Systems Director NetworkControl V1.1 configuration to V1.2.x. See the topic Migrating to IBM SystemsDirector Network Control V1.2.2.

IBM Systems Director Network Control V1.2 can be used with IBM SystemsDirector 6.2 and 6.2.1.

IBM Systems Director Network Control V1.2.1 requires IBM Systems Director 6.2.1.

IBM Systems Director VMControl

IBM Systems Director VMControl versions 2.1 and 2.2 are not compatible with IBMSystems Director 6.2, but you can migrate existing IBM Systems DirectorVMControl resources to VMControl version 2.3. For information, see Migrating toVMControl 2.3.

If you are currently managing Windows Server 2008, Enterprise, Standard, andDatacenter x64 Editions with Hyper-V role enabled, Release 2 environments withIBM Systems Director 6.2.0 and VMControl 2.3.0 and update to IBM SystemsDirector 6.2.1, you must update to VMControl 2.3.1. For information, see UpdatingIBM Systems Director VMControl.

Upgrading and migrating IBM Systems Director on the managementserver

After preparing your system, use the IBM Systems Director Server upgrade andmigration procedure that is applicable for your operating system.

Chapter 8. Upgrading and migrating 165

Upgrading and migrating IBM Systems Director Server on AIXAfter preparing your system, you can upgrade and migrate IBM Systems DirectorServer on AIX by following the normal IBM Systems Director installation path andtaking the options (or making the response file selections) for migration.

Important:

v The migration from IBM Systems Director 6.1.x to 6.2.1 must be done in twosteps:1. Migrate from IBM Systems Director 6.1.x to 6.2 by following this procedure.2. Use update manager to apply the 6.2.1 updates. See “Updating IBM Systems

Director” for instructions.v Before performing an upgrade, you will need to understand disk space

requirements. For information on disk space requirements for upgrades, see“Hardware requirements” or the IBM Systems Director Best Practices Wiki.

v It is recommended to make a system backup before upgrading and migrating toIBM Systems Director Server 6.2. For more information, see “smsave command”and “smrestore command”.

v Review the database preparation considerations. See “Database preparationconsiderations for upgrading and migrating”.

v If you are upgrading and migrating plug-ins along with IBM Systems Director,ensure that you first reference “Upgrading and migrating IBM Systems Directorplug-ins” and strictly adhere to any requirements that it lists in general or foryour specific plug-in.

You can upgrade and migrate IBM Systems Director Server on AIX from eitherinstallation media or from a downloaded installation package.

Important: The IBM Systems Director Server and Common Agent installationpackages for AIX are provided in English only.

Table 46. Installation options for IBM Systems Director Server on AIX

Installation method Title or file name

DVD media IBM Systems Director for AIX, V6.2.1 DVDNote: To obtain an image of the IBMSystems Director for AIX, V6.2.1 DVD,download the SysDir6_2_1_DVD_AIX.isofile.

Attention: If you use DVD media to installIBM Systems Director Server, ensure thatyou allot an additional 1.5 GB of availablespace in the /opt file system to contain theagent packages that are copied from theDVD at the end of the server installation.The packages are copied to/opt/ibm/director/packaging/agent on theserver. Installing IBM Systems DirectorServer from AIX 6.2.1 DVD media does notinstall the agents. This is an exception for6.2.1. TheSysDir6_2_1_Common_Agent_platform.jarfiles are provided in the agent subdirectoryof the DVD media.

166 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

Table 46. Installation options for IBM Systems Director Server on AIX (continued)

Installation method Title or file name

Downloaded installation package SysDir6_2_Server_AIX.tar.gz (1.36GB)

Attention: When downloading theinstallation package file to your AIX server,you must first run the following commandto increase the default file size limit:

ulimit -f 4194302

Upgrading and migrating IBM Systems Director Server 6.2.1 using thedirinstall.server script is the only supported method.

To upgrade IBM Systems Director Server, log in as the root user and complete thefollowing steps:

Tip: You can find the installation logs for this process in /var/log/dirinst.logand /opt/ibm/director/log/installFeatures_date.log. The migration log is in/var/log/director_migration_date.log.1. Start the IBM Systems Director Server upgrade and migration from the

installation source:Downloaded installation files: To start the upgrade and migration from a Webdownload, complete the following steps:a. Run the following command to increase the default file size limit:

ulimit -f 4194302

b. Download the installation package from the IBM Systems DirectorDownloads Web Site at www.ibm.com/systems/management/director/downloads/.

c. To unzip and extract the contents of the installation package, type thefollowing command:gzip -cd <package_name> | tar -xvf -

where <package_name> is the file name of the download package.d. Run the following command to reset the default file size limit:

ulimit -f 2097151

e. Change to the directory in which the installation script is located. Type thefollowing command and press Enter:cd /install_files/

where install_files is the path to the extracted installation files.DVD media: To start the upgrade and migration from the IBM Systems Directorfor AIX, V6.2.1 DVD, complete the following steps:a. Insert the DVD into the DVD-ROM drive.b. If the DVD does not automount, type the following command and press

Enter:mount -v cdrfs -o ro /dev /mnt

where dev is the specific device file for the block device and mnt is themount point of the drive.

Chapter 8. Upgrading and migrating 167

c. To change to the directory in which the installation script is located, typethe following command and press Enter:cd /dvd_mnt/server/

where dvd_mnt is the mount point of the DVD media.2. If you are using Apache Derby or you are not using a response file, then go to

the next step. Otherwise, enter the following command to run dbconfig:dbconfig.sh

Note: The dbconfig script is in the following location depending on yourinstallation method:v Web download: install_root/InstallMigrationTools/dbconfig.sh, where

install_root represents the root directory of your IBM Systems Directorinstallation.

v DVD: /dvd_mnt/server/InstallMigrationTools/dbconfig.sh, where dvd_mntrepresents the directory to which you mounted the IBM Systems DirectorDVD.

You are prompted to enter the database administrator userid and password.

Tip: The database user ID and password are not the same as the databaseAdmin user name and password. The database Admin user name andpassword are collected from dbconfig.sh before you run the installer. If youforget and run the installer without dbconfig.sh, you will get a message tellingyou to run dbconfig.sh.

3. To upgrade IBM Systems Director Server, from within the directory in whichthe installation script is located, type one of the following commands and pressEnter:v To accept the default settings (Apache Derby):

./dirinstall.server

v To specify options (IBM DB2 or Oracle® Database):./dirinstall.server -a dms_database_app_home -b saved_database_path -d saved_data_path

– where dms_database_app_home specifies the path to the directory of thedatabase client to be used by the upgraded IBM Systems Director. Thisoption is usually needed when migrating to a 64-bit installation or whenmoving to a newer version of the database client.

– where saved_database_path specifies the path to the directory wheredatabase data is saved during an IBM Systems Director migration. Thisoption is required if the database is remote (on a system other than thesystem where IBM Systems Director is being installed). This option isignored if the -g option is specified. If a remote Windows database serveris used, do not set this path with a space in it.

– where saved_data_path specifies the path to the directory where data issaved during an IBM Systems Director migration. This option is ignored ifthe -g option is specified.

This example illustrates migrating from a 32 bit to a 64 bit operating system,using a remote database.dirinstall.server -a /home/db2inst2/sqllib -b /remotedbdir -d /isdbackup

Note: For more options, run ./dirinstall.server -?, see “dirinstall.server”,or see the IBM Systems Director Best Practices Wiki.

v To use the response file (IBM DB2 or Oracle® Database):./dirinstall.server -r /directory/response.rsp

168 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

where directory is the local directory to which you copied the response file,and response.rsp is the name of the response file.

Notes:

– For more information about the response file, see the comments in theresponse file or see the IBM Systems Director Best Practices Wiki.

– A sample response file named dirserv.rsp resides in the same directoryas the dirinstall.server installer.

– If you wish to use the default for any value in the response file, commentout that value with a “#” symbol at the beginning of the line instead ofleaving the value blank.

– If you need to enter any Windows-based locations, ensure that you use“\\” (two back slashes) for every “\” (one back slash) when specifyingthe remote Windows directory name. For example, use C:\\foldernameinstead of C:\foldername.

– For more options, run ./dirinstall.server -?, see “dirinstall.server”, orsee the IBM Systems Director Best Practices Wiki.

Tip: After installation, keep the response file for future use and reference.v To force a clean installation regardless of existing data:

./dirinstall.server -g

or change MIGRATE_DATA=1 to MIGRATE_DATA=0 in the response file.4. Complete the following steps to start IBM Systems Director Server:

a. If it is not already started, start IBM Systems Director processes on themanagement servers by running the smstart command:install_root/bin/smstart

See the “smstart command” topic for instructions.b. To view the IBM Systems Director Server status, type the following

command and press Enter:install_root/bin/smstatus -r

Note: You can use Ctrl+C to exit from smstatus -r if necessary.When this command returns a value of Active, the server is started.

5. Optional: Obtain and distribute any needed 6.1.x agent packages. If youupgraded from IBM Systems Director Server 6.1.x, the only agent deploymentpackages that are available by default are all applicable 6.2 agent packages (ifyou upgraded using the DVD media) or only the 6.2 subagent packages (if youupgraded using a downloaded installation package). Any agent deploymentpackages that were installed by default in 6.1.x or that you imported throughthe Agent Import task are no longer available. Therefore, complete thefollowing steps if you need to distribute the 6.1.x agent packages:a. If the 6.1.x agent packages do not still reside on the server system, find

them on the IBM Systems Director Downloads Web Site and downloadthem to any location on the server system.

b. In the IBM Systems Director Web interface, go to Release Management >Agents and click Import Agent.

c. Enter the directory path that contains the agent package that you want toimport and click OK. After a successful import, the 6.1.x packages willappear in the IBM Systems Director Web interface and will be ready fordistribution.

Chapter 8. Upgrading and migrating 169

6. Verify that your library path environment variables are still set correctly, and fixany that are not correct. The LIBPATH environment variable must point to the64-bit library folder, for example database_client_root\lib ordatabase_client_root\lib64.

7. If you used the DVD for installation, complete the following steps to unmountthe 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.

The following CAS agent runtime files are created by cimserver during runtime:v /tmp/cimserver_start.conf

Note: This file is deleted when cimserver shuts down. This does not affectcimserver.

v /tmp/cimlistener_start.conf

Note: This file is deleted when cimlistener shuts down. This does not affectcimlistener.

v /tmp/elasocket_cimv2v /tmp/dpi_socket

After you have upgraded the agent and server packages, you can use updatemanager to update to the latest version of IBM Systems Director, if updates areavailable. See “Updating IBM Systems Director” for instructions.

Note: Before performing an update, you will need to understand disk spacerequirements. For information on disk space requirements for updates, see“Determining disk space requirements for applying updates” or the IBM SystemsDirector Best Practices Wiki.Related reference

IBM Systems Director Downloads

IBM Systems Director Best Practices Wiki

Upgrading or updating the IBM Systems Director agentsAfter upgrading IBM Systems Director Server, you can upgrade or update the IBMSystems Director agents.

When IBM Systems Director Server is updated to 6.2.1, the common agent that isinstalled on the same system with IBM Systems Director Server is updated to 6.2.1as well. If the local common agent has been updated to 6.2.1 before IBM SystemsDirector Server, then the IBM Systems Director Server update to 6.2.1 will fail.

Notes:

v This task applies to both local and remote agents.v A Common Agent update is part of the IBM Systems Director 6.2.1 update

package for which you use update manager.

170 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

v A Platform Agent update is not part of the IBM Systems Director 6.2.1 updatepackage for which you use update manager.

v Before using update manager to update Platform Agent to 6.2.1 from 5.20.x or6.1.x, see “Applicability of Platform Agent” for information about conditions thatmight cause the installation of the update to fail. You can also see “IBM SystemsDirector Pre-Install Utility” for information about running the IBM SystemsDirector Pre-Install Utility on the agent to obtain a compatibility report beforeattempting the installation of the update. If you still use update manager toupdate Common Agent or Platform Agent and the update process fails or logsan error message, review the installation and uninstallation logs for each of theaffected agents and then instead use the manual installation process for thoseagents.

v When you update Common Agent or Platform Agent from 5.20.x to 6.2.1 on aRed Hat Enterprise Linux system, the ports that are used on the Platform Agentare changed. You must rediscover and obtain access to the agent again beforeusing it.

Choose the appropriate method to upgrade or update your agent based on youragent type and operating system:v Use the following methods to upgrade or update Common Agent.

Operating systemMethod to use to update or upgradeCommon Agent

AIX Install Common Agent 6.2.1. See “InstallingCommon Agent” for more information.

Linux on Power Systems Update Common Agent using updatemanager. See “Updating systems” for moreinformation.

Linux for System x and x86-based systems Update Common Agent using updatemanager. See “Updating systems” for moreinformation.

Linux for System z Update Common Agent using updatemanager. See “Updating systems” for moreinformation.

Windows Update Common Agent using updatemanager. See “Updating systems” for moreinformation.

v Use the following methods to upgrade or update Platform Agent.

Operating systemMethod to use to update or upgradePlatform Agent

AIX Install Common Agent 6.2.1. (Platform Agentis updated as part of the Common Agentupdate.) See “Installing Common Agent” formore information.

Linux on Power Systems Install Platform Agent 6.2.1. See “InstallingPlatform Agent” for more information.

Linux for System x and x86-based systems Update Platform Agent using updatemanager. See “Updating systems” for moreinformation.

Linux for System z Install Platform Agent 6.2.1. See “InstallingPlatform Agent” for more information.

Chapter 8. Upgrading and migrating 171

Operating systemMethod to use to update or upgradePlatform Agent

Windows Update Platform Agent using updatemanager. See “Updating systems” for moreinformation.

172 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

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 inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing 2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct 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 itbelieves appropriate without incurring any obligation to you.

© Copyright IBM Corp. 1999, 2010 173

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationMW9A/0505600 Cottle RoadSan Jose, CA 95193U.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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both. If these and other IBM trademarked terms are marked on their firstoccurrence in this information with a trademark symbol (® or ™), these symbolsindicate U.S. registered or common law trademarks owned by IBM at the time thisinformation was published. Such trademarks may also be registered or common

174 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

law trademarks in other countries. A current list of IBM trademarks is available onthe Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registeredtrademarks 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 orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand 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, othercountries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Othernames may be trademarks of their respective owners.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other company, product, or service names may be trademarks or service marks ofothers.

Notices 175

176 IBM Systems Director for AIX Planning, Installation, and Configuration Guide

����

Printed in USA

GI11-8709-06