6.2.1.installation Aix

IBM Systems Director
IBM Systems Director for AIX Planning, Installation, and Configuration Guide
Version 6.2.1
GI11-8709-06
Version 6.2.1
GI11-8709-06
Note Before using this information and the product it supports, read the information in Notices on page 173.
Copyright IBM Corporation 1999, 2010. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
About this publication . . . . . . . . v
Conventions and terminology . . . . . . . . v Publications and related information . . . . . . v Web resources . . . . . . . . . . . . . viii How to send your comments . . . . . . . . . x IBM Systems Director task support for BladeCenter products . . . . . . . . . . 60 IBM Systems Director task support for Storage products . . . . . . . . . . . . . . 61 Supported tasks and features for third-party x86-based systems . . . . . . . . . . . 61 Translations provided by IBM Systems Director 62 IBM Systems Director Pre-Installation Utility . . 63 IPv6 compliance . . . . . . . . . . . . . 64 Applicability of Platform Agent. . . . . . . . 67 Determining IBM Systems Director task support . . 69 Questions to answer about IBM hardware . . . 69 Questions to answer about third-party hardware 70 Planning to install IBM Systems Director . . . . 71 Service and support information . . . . . . 71 Reviewing the environment . . . . . . . . 72 Version compatibility of IBM Systems Director components across releases . . . . . . . . 75 License information. . . . . . . . . . . 77 Obtaining licenses for Common Agent . . . . 79 Choosing how to install IBM Systems Director. . 79 Choosing the IBM Systems Director Server installation options . . . . . . . . . . . 81 Choosing where to install IBM Systems Director Server . . . . . . . . . . . . . . . 81 Choosing the IBM Systems Director database application . . . . . . . . . . . . . 82 Choosing the management level for managed systems. . . . . . . . . . . . . . . 84 Planning for virtual environments . . . . . . 85 Planning to upgrade or update IBM Systems Director . . . . . . . . . . . . . . . 86 Disaster recovery for IBM Systems Director 6.2.x . . 89 Planning for events . . . . . . . . . . . . 90 Planning events to be monitored . . . . . . 90 Planning for event automation plan implementations . . . . . . . . . . . . 91 Planning IBM Systems Director security . . . . . 94 Planning IBM Systems Director users and groups 94 Planning Secure Sockets Layer configuration on IBM Systems Director . . . . . . . . . . 95 Planning password management in IBM Systems Director . . . . . . . . . . . 104
Checklist: Installing IBM Systems Director Server on AIX . . . . . . . . xi Checklist: Installing agents on AIX . . xiii Chapter 1. IBM Systems Director technical overview . . . . . . . . . . 1
IBM Systems Director components . . . . . Management server . . . . . . . . . Common Agent . . . . . . . . . . Platform Agent . . . . . . . . . . Agentless managed systems . . . . . . Manageable resource types . . . . . . . Manageable systems and system types. . . . User interfaces. . . . . . . . . . . . Base function and extensible plug-ins . . . . Discovery manager . . . . . . . . . Status manager . . . . . . . . . . Configuration manager . . . . . . . Automation manager . . . . . . . . Update manager. . . . . . . . . . Remote access manager . . . . . . . Virtualization manager . . . . . . . Network Management . . . . . . . . IBM BladeCenter and System x management IBM System z management . . . . . . IBM Power Systems management . . . . IBM System Storage management . . . . Additional IBM Systems Director plug-ins . Upward integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 . 3 . 4 . 5 . 5 . 6 . 6 . 8 . 8 . 9 . 9 . 10 . 10 . 10 . 11 . 11 . 12 . 12 . 12 . 12 . 13 . 13 . 16
Chapter 2. Planning for IBM Systems Director . . . . . . . . . . . . . . 17

Hardware and software requirements. . . . . . Hardware requirements for IBM Systems Director Supported IBM systems and products . . . . IBM BladeCenter products . . . . . . . . Supported network devices . . . . . . . . Supported storage devices . . . . . . . . Network requirements. . . . . . . . . . Security requirements . . . . . . . . . . Firmware and device drivers requirements . . . Operating system and software requirements . . IBM Systems Director task support by operating system and agent levels . . . . . . . . . IBM Systems Director task support not affected by operating systems . . . . . . . . . . 17 17 21 21 22 28 38 46 47 47 56 60
Chapter 3. Installing IBM Systems Director on the management server. . 107

Preparing the management server . . . . . . Preparing the database application . . . . . Preparing firewalls and proxies for IBM Systems Director . . . . . . . . . . . . . . Preparing to install IBM Systems Director Server on AIX . . . . . . . . . . . . . . Installing IBM Systems Director on the management server . . . . . . . . . . . Installing IBM Systems Director Server on AIX 107 107 117 118 121 121
Copyright IBM Corp. 1999, 2010
iii
Configuring the database connection after IBM Systems Director installation . . . . . . . . Configuring IBM Systems Director Server after installation . . . . . . . . . . . . . . Configuring IBM Systems Director plug-ins and platforms . . . . . . . . . . . . . . Configuring the command line interface . . . Reviewing Microsoft Internet Explorer security options . . . . . . . . . . . . . . Configuring IP address properties . . . . . Logging on to IBM Systems Director Server for the first time . . . . . . . . . . . . . . . Restarting IBM Systems Director Server . . . . Enabling Dynamic IP support . . . . . . . .
126 127 128 129 130 131 132 133 134
Using system discovery to view current results Accessing a secured system with request access
149 150
Chapter 6. Installing agents . . . . . 153

Preparing a Common Agent managed system Obtaining licenses for Common Agent . . Preparing to install Common Agent on AIX Installing agents using the Agent Installation Wizard . . . . . . . . . . . . . . . . . . 153 . 153 . 153 . 155
Chapter 7. Updating IBM Systems Director . . . . . . . . . . . . . . 159 Chapter 8. Upgrading and migrating IBM Systems Director . . . . . . . . 161
Database preparation considerations for upgrading and migrating to IBM Systems Director 6.2.x . . . Upgrading and migrating to IBM Systems Director 6.2.1 from 6.1.x . . . . . . . . . . . . . Upgrading and migrating to IBM Systems Director 6.2.1 from 6.2 . . . . . . . . . . . . . Upgrading and migrating to IBM Systems Director from IBM Director 5.x . . . . . . . . . . Upgrading and migrating IBM Systems Director plug-ins . . . . . . . . . . . . . . . Upgrading and migrating IBM Systems Director on the management server . . . . . . . . . . Upgrading and migrating IBM Systems Director Server on AIX . . . . . . . . . . . . Upgrading or updating the IBM Systems Director agents . . . . . . . . . . . . . . . . 161 163 164 164 165 165 166 170
Chapter 4. Preparing agentless managed systems . . . . . . . . . 137

Configuring access to agentless managed systems Sample sudo configuration file . . . . . . Preparing AIX managed systems . . . . . . . Preparing to manage a IBM BladeCenter . . . . Preparing to manage a IBM BladeCenter chassis using IBM Systems Director Server on a non-blade server . . . . . . . . . . . Preparing to manage a IBM BladeCenter chassis using IBM Systems Director Server on a blade server . . . . . . . . . . . . . . . Preparing Hardware Management Console devices for discovery with IBM Systems Director . . . . 137 138 139 139
139
140 142
Chapter 5. Discovering systems and collecting inventory data . . . . . . 145

Discovery protocols . . . . . . . . Discovering systems with system discovery System discovery . . . . . . . . Performing a system discovery . . . . . . . . . . . . . . . 145 146 146 147
Notices . . . . . . . . . . . . . . 173
Trademarks . . . . . . . . . . . . . . 174
iv
About this publication

This IBM Systems Director for AIX Planning, Installation, and Configuration Guide provides information about installing and configuring IBM Systems Director. In addition to presenting an overview of IBM Systems Director and its requirements, it covers the following topics: v Planning an IBM Systems Director environment v Installing IBM Systems Director v Upgrading from IBM Director 5.20 to IBM Systems Director 6.x v Configuring IBM Systems Director It also includes information about IBM Systems Director security and solving problems you might encounter during installation. Note: Oftentimes, this publication describes a single procedure for accomplishing a task. For documentation about alternative procedures, see the IBM Systems Director 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 avoid inconvenient or difficult situations. Attention: These notices indicate possible damage to programs, devices, or data. An attention notice appears before the instruction or situation in which damage can occur.
Publications and related information

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

v IBM Systems http://publib.boulder.ibm.com/eserver/ View the IBM Systems information center landing page, which provides integrated information for multiple IBM Systems products. v IBM Systems Director http://publib.boulder.ibm.com/infocenter/director/v6r2x/index.jsp Updated periodically, the IBM Systems Director topic collection contains the most up-to-date documentation available for IBM Systems Director. v IBM Systems Director plug-ins publib.boulder.ibm.com/infocenter/systems/index.jsp
View the IBM Systems information center for information about how to install and use plug-ins that extend the functionality of IBM Systems Director. v IBM Systems Director Upward Integration Modules (UIMs) publib.boulder.ibm.com/infocenter/systems/topic/uims/fqs0_main.html Read the IBM Systems Director Upward Integration Modules (UIM) topic collection to learn about how to install and use upward integration modules and management packs that enable non-IBM workgroup and enterprise-management products to interpret and display data that is provided by Common Agent and Platform Agent. v IBM Systems Director API Licensing http://www.ibm.com/vrm/4api1 View the license information regarding use of IBM Systems Director APIs and their associated documentation. Fill out the form to request API access. After your information is reviewed, you will be contacted with additional information regarding access to and use of the APIs.
Publications
APAR Readme 6.2.0 Provides information about APARs fixed in IBM Systems Director version 6.2.0. Release Notes 6.2.0 and Release Notes 6.2.1 Provides information about hardware requirements for running IBM Systems Director components, supported IBM Systems Director hardware, operating systems, databases, and workgroup and enterprise systems-management software. Hardware and Software Support Guide Provides information about hardware requirements for running IBM Systems Director components, supported IBM Systems Director hardware, operating systems, databases, and workgroup and enterprise systems-management software. Planning, Installation, and Configuration Guide for AIX Provides detailed instructions to install and configure each component of IBM Systems Director on system running AIX using the standard installation option. Planning, Installation, and Configuration Guide for IBM i Provides detailed instructions to install and configure each component of IBM Systems Director on system running IBM i using the Standard installation option. Planning, Installation, and Configuration Guide for Linux on Power Systems Provides detailed instructions to install and configure each component of IBM Systems Director on system running Linux for Power Systems using the Standard installation option. Planning, Installation, and Configuration Guide for Linux on x86 Provides detailed instructions to install and configure each component of IBM Systems Director on system running Linux for System x using the Standard installation option. Planning, Installation, and Configuration Guide for Linux on System z Provides detailed instructions to install and configure each component of IBM Systems Director on system running Linux for System z using the Standard installation option.
vi
Planning, Installation, and Configuration Guide for Windows Provides detailed instructions to install and configure each component of IBM Systems Director on system running Windows using the Standard installation option. Systems Management Guide Provides detailed instructions for using the Web interface and managing systems and resources in your environment. Troubleshooting Guide Provides information about problems and how to solve them, and strategies for troubleshooting common problems. Events Reference Provides information about IBM Systems Director events, including the event type, description, severity, and extended details. Commands Reference Provides detailed information about the systems management command-line interface (smcli) commands, and other commands that can be run directly from the command line, including configuring the database, and starting and stopping IBM Systems Director. Hardware Command Line User's Guide Provides information about installing and using the Hardware Command Line (formerly known as the IBM Management Processor Command-Line Interface). Command output in this release might vary from command output in previous releases.
White papers and briefs

v IBM Systems Director ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03006usen/ XBW03006USEN.PDF This paper provides a detailed overview of the changes in IBM Systems Director V6.1, including the new Web interface, security features, operating system agents, integrated plug-ins and additional plug-ins that can be separately installed. v Value Proposition for IBM Systems Director ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/xbw03007usen/ XBW03007USEN.PDF This paper describes the challenges of operational management for enterprise server installations and the value provided IBM Systems Director. v Managing IBM Power Servers with IBM Systems Director 6.1 www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH &appname=STGE_PO_PO_USEN&htmlfid=POW03011USEN &attachment=POW03011USEN.PDF Provides information about managing the virtualization and consolidation on Power systems using IBM Systems Director. v IBM Systems Director 6.1 Migration Tips www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH &appname=STGE_XB_XB_USEN_&htmlfid=XBW03009USEN &attachment=XBW03009USEN.PDF Provides information about migrating data when upgrading your environment from IBM Director V5.20 to IBM Systems Director V6.1. v Performance Tuning and Scaling Guide for IBM Systems Director 6.2
vii
http://www-01.ibm.com/support/ docview.wss?uid=nas7cd6a96f49d05f608862577420075ca9a&aid=1 Provides information about how to plan, implement, configure, and use an IBM Systems Director Server to manage a large configuration with optimal performance. The Performance Tuning and Scaling Guide also contains information 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 Systems Director and specific IBM hardware; such documents often contain systems-management material. The following book is available for IBM Systems Director V6.1: Implementing IBM Systems Director 6.1 Tip: Be sure to note the date of publication and to determine the version of IBM Systems Director software to which the Redbooks publication refers.
Further information
Also see the following resources for further information about IBM Systems Director: 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 the Search field and click Search. You can then narrow your results by document type or product category, or use additional search terms. v For white papers, technotes, tips, and other documents related to IBM Systems Director, 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 you want to search or select UNMARKED to search all categories. Then enter Systems 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 resources
Listed here are the Web sites and information center topics that relate to IBM Systems Director.
viii
Web sites
v IBM Systems Director www.ibm.com/systems/management/director/ View the IBM Systems Director Web site on ibm.com which provides links to downloads and documentation for all currently supported versions of IBM Systems Director. v IBM Systems Director Downloads www.ibm.com/systems/management/director/downloads/ View the IBM Systems Director Downloads Web site on ibm.com which provides links to download code IBM Systems Director, IBM Systems Director plug-ins, and IBM Systems Director upward integration modules. v IBM Systems Director Documentation and Resources www.ibm.com/systems/management/director/resources/ View the IBM Systems Director Documentation and Resources Web site on ibm.com which provides links to product documentation, redbooks, redpapers, white papers, and learning modules related to IBM Systems Director, IBM Systems Director plug-ins, and IBM Systems Director upward integration modules. v IBM Systems Director Upward Integration www.ibm.com/systems/software/director/downloads/integration.html View the IBM Systems Director Upward Integration Web site on ibm.com which provides more information about IBM Systems Director upward integration modules created by IBM and other companies. IBM Systems Director UIMs enable third-party workgroup and enterprise systems-management products to interpret and display data that is provided by IBM Systems Director Platform Agent managed system. v IBM Systems Director Best Practices Wiki www.ibm.com/developerworks/wikis/display/WikiPtype/ IBM+Systems+Director+Best+Practices+Wiki View updated documentation and best practices for IBM Systems Director on various systems. v IBM Servers www.ibm.com/servers/ View the IBM Servers Web site to learn about IBM Systems server and storage products. v IBM ServerProven www.ibm.com/servers/eserver/serverproven/compat/us/ View the IBM ServerProven Web site to learn about hardware compatibility of IBM System x and BladeCenter systems with IBM applications and middleware, including IBM Systems Director.
Forums
v IBM Systems Director www.ibm.com/developerworks/forums/forum.jspa?forumID=759 View the IBM Systems Director forum Web site on ibm.com to discuss product-related issues pertaining to IBM Systems Director, IBM Systems Director UIMs, and IBM Systems Director extensions. This Web site includes a link for obtaining the forum using a Rich Site Summary (RSS) feed. v IBM Systems Director SDK
ix
www.ibm.com/developerworks/forums/forum.jspa?forumID=1852&start=0 View the IBM Systems Director SDK forum Web site to discuss issues pertaining to the IBM Systems Director Software Development Kit (SDK). This Web site includes a link for obtaining the forum using a Rich Site Summary (RSS) feed. v IBM Systems www.ibm.com/developerworks/forums/dw_esforums.jsp View the IBM Systems forums Web site on ibm.com to learn about various forums that are available to discuss technology-related and product-related issues pertaining to IBM Systems hardware and software products. This Web site includes a link for obtaining the forum using a Rich Site Summary (RSS) feed.
How to send your comments

Your feedback is important in helping to provide the most accurate and highest quality information. If you have any comments about this book or any other IBM Systems Director publication, go to the IBM Systems Director information center Web site at http://publib.boulder.ibm.com/infocenter/director/v6r2x/index.jsp. There you will find the feedback page where you can enter and submit comments.
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. __ 2. __ 3. __ 4. 2 Check Check Check Check the the the the hardware requirements (17). network requirements (38). security requirements (46). supported operating systems (47).
__ 5. Check the supported database applications (55). 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). 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).
Install IBM Systems Director Server. __ 1. Install IBM Systems Director Server (121). __ 2. Configure the database application (126).
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).
Update IBM Systems Director Server. __ 1. Update IBM Systems Director Server (159).
xi
xii
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). 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). Prepare your managed systems. __ 1. Prepare all managed systems for discovery and management by IBM Systems Director (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).
Install the agents. __ 1. Use the Agent Installation Wizard to deploy agent packages to your managed systems (155).
Update the agents. __ 1. Update the agents (159).
xiii
xiv
Chapter 1. IBM Systems Director technical overview

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

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

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

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

A resource is a generic term for anything that IBM Systems Director can manage. For example, systems, slots, cards, groups, and updates are all resources. From the Web interface, you can use the Find a Resource task to find resources and use the Resource Explorer task to view and work with these resources.
Manageable systems and system types

A system is one type of resource that IBM Systems Director manages. It is an operating-system-based or hardware-based resource that has an IP address and host name and can be discovered and managed by IBM Systems Director. From the Navigate Resource page in the IBM Systems Director Web interface, you can view the All Systems group to work with all discovered systems. Operating-system-based systems Operating-system-based systems (referred to as operating systems) consist of the operating system image, agent, drivers, applications, and configuration settings. From the Navigate Resource page in the IBM Systems Director Web interface, you can view the All Operating Systems group to work with these types of systems. Hardware-based systems Hardware-based systems are the physical and virtual systems, such as servers, virtual servers, storage systems, and network devices. Physical systems can host multiple operating systems and virtual servers, either by using a dual-boot feature or by way of a hypervisor. From the Navigate Resource page in the IBM Systems Director Web interface, you can use the All Network Systems, All Storage Systems, or All Systems groups to work with the physical aspects of a system, determine how many virtual servers a physical system contains, and determine how many operating systems are running on a physical system. To view the relationships between systems, view the topology map view for a system 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 click Actions > Related Resources. A submenu of applicable related resources is displayed. IBM Systems Director manages the following types of systems:
Chassis A physical resource that encloses other resources and provides definable functions. Example types include a desktop, processing node, uninterruptible power supply, disk or tape storage, or a combination of these types. Cluster A computer system that is composed of two or more computer systems that operate together to increase performance, reliability, availability, and serviceability. ComputerSystem A single component that runs one operating system, or multiple components that are controlled by one or more operating systems. GenericNetworkDevice A computer system that has an unknown device type. HardwareManagementConsole A computer system that controls managed systems. This includes the management of logical partitions and the use of Capacity on Demand. OperatingSystem Software that is responsible for the formation of an execution environment and allocations of resources for software programs on a computer. PassThroughModule A Pass-Thru module. Server A single node computer system such as a desktop, mobile device, or NetPC. The Server class type is derived from the ComputerSystem class type. StorageSubsystem A computer system that is dedicated to acting as a storage server. Switch A computer system that is dedicated to acting as a switch for network traffic. SystemChassis A computer system that represents a modular enclosure that contains one or more blades. You can use the lssys -I command to obtain a list of valid system types for commands such as discover. Virtualization allows you to hide the physical characteristics of your servers to consolidate servers, optimize resource usage, and improve IT flexibility and responsiveness. Using virtualization, you can create multiple discoverable virtual servers from a single physical server or create a single discoverable virtual server from multiple physical servers. Each virtual server has an independent operating environment and can have functions or features that are not available in its underlying physical resources. Tip: Virtual servers running on IBM systems are often referred to as logical partitions or virtual machines. After IBM Systems Director discovers a physical server, it continues the discovery process to find all associated virtual servers. Each IBM system offers virtualization technologies to help you consolidate systems, optimize resource utilization, and improve IT flexibility and responsiveness.
User interfaces
There are several methods for managing an IBM Systems Director environment: a Web interface and a command-line interface (smcli).
Web interface
You can use the IBM Systems Director Web interface to conduct comprehensive systems management through a graphical user interface. Data is securely transferred between the Web browser and Web interface through HTTPS. The system on which you logged in to the IBM Systems Director Web interface is referred to as the browser system. You log in to the IBM Systems Director through a supported Web browser using this URL:
http://System_Name:Port_Number/ibm/console
where System_Name is the name of the system on which IBM Systems Director Server is installed and Port_Number is the first (lower) of two consecutive port numbers that you specified for the Web server to use. The default ports for the Web server are 8421 and 8422. If you use port 8422, make sure that you specify https to indicate a secure port.
Command-line interfaces
You can use the systems management command-line interface interactively using the smcli utilities. This command-line interface (CLI) is an important primary interface into IBM Systems Director and can be used either as an efficient way to accomplish simple tasks directly or as a scriptable framework for automating functions that are not easily accomplished from a graphical user interface. For security reasons, the CLI runs only on the management server. The command-line interface follows the GN/POSIX conventions. Tips: v The IBM Systems Director smcli supports most commands that were available in previous releases through the discontinued dircli utility. v For security, the CLI runs only on the management server. You can run the CLI remotely using a remote-access utility, such as Secure Shell (SSH) or Telnet.
Base function and extensible plug-ins

Base plug-ins in IBM Systems Director provide core function to manage the full lifecycle of IBM servers, storage, network, and virtual servers. Plug-ins that provide advanced function or function tailored to a particular environment can be downloaded and installed on top of IBM Systems Director. Basic user interface, security, and agent management functions include: v Finding and viewing resources and resource information, including relationships and properties v Organizing logical sets of resources into groups v Starting, stopping, and scheduling tasks in IBM Systems Director v Integrating third-party management software and other programs into the IBM Systems Director Web interface v Managing auditing
v Encrypting interprocess communication v Managing Common Agent registration and authentication v Authenticating users through a configured user registry available from the operating system, Lightweight Directory Access Protocol (LDAP), or domain controller v Creating roles and authorizing users and user groups to access certain systems, groups, and tasks v Managing credentials to support single sign-on authentication, even when services span different systems v Installing, upgrading, and promoting agents
Discovery manager
Discovery manager performs physical and virtual system discovery and inventory of related resources on the network. You can use the discovery manager plug-in to: v Discover systems and other resources (such as physical and virtual servers, storage systems, and network devices) in a heterogeneous environment. Discover resources by using a single IPv4 or IPv6 address, a single host name, a range of IP addresses, or use a discovery profile to discover systems of different types across multiple subnets. v Collect inventory data about hardware and software that is currently installed on systems. Inventory data is information about physical, logical, and virtual hardware (such as virtual systems, virtual servers, and farms), software applications, operating systems, middleware, firmware and BIOS, diagnostic information, and network. v Manage inventory profiles that you can use to discover a group of resources or collect inventory data based on a set of criteria. v View systems, inventory data, and relationships among systems in the network using Navigate Resources. v Request access to manage security credentials for discovered systems.
Status manager
Status manager provides an at-a-glance view of the health of your managed resources (including systems, operating systems, applications, processes, and security). The status of discovered systems is automatically retrieved and displayed, and this display can be customized in several waysusing one of the system status and health 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 and events for systems. v Determine the health, compliance, and performance of managed systems in your environment using the health summary, scoreboard, and dashboard. The health summary shows the overall health of your managed systems. The scoreboard summarizes the hardware state, event state and compliance state for all managed systems. The dashboard shows performance information for specific managed systems. v View the event log.
v Identify problems and find the root cause by viewing detailed information about the 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 manager
Configuration manager is used to integrate new hardware into your environment, configure systems after installation, or do one-off configurations for problem resolution. Configuration manager leverages a set of well defined templates that can be applied to servers, storage, and network resources even if the resources are comprised of very different technologies. You can use the configuration manager plug-in to: v Use the Configuration Manager Summary page to view system configuration status and a summary of tasks that will help you configure your systems. v Initially configure one or more systems (hardware and operating systems) to a point where they can be deployed, allocated, and powered on. v Automatically configure newly discovered systems using the automatic-deploy capability of a configuration plan. v Reconfigure systems to prepare for redeployment, reallocation, or re-provisioning (for example, as a result of an event or as part of a workflow that the configuration needs to be support). v Manage configuration templates and plans. A configuration template is a collection of settings and values that define the configuration of a system. A configuration plan is a set of templates that can be applied to one or more systems in a specific order.
Automation manager
Automation manager provides tools to notify an administrator or run a predefined tasks automatically when a certain event occurs. You can use the automation manager plug-in to: v Use the Automation Manager Summary page to view the status of jobs and automation plans and a summary of tasks that will help you automate tasks. v Create custom event-automation plans used to automate tasks and other responses to situations that occur in your environment. v Create and manage event filters that allow the event automation plans to target specific events. v Create and manage event actions that identify tasks or commands to run or notifications to send. The types of actions include starting a noninteractive task or program on the management server or the system on which the event was generated or sending an email notifications over the Internet or to a mobile phone.
Update manager
Update manager provides tools for maintaining current versions of operating systems, device drivers, firmware and BIOS, and IBM Systems Director agent and server code on managed systems without an upgrade or migration of the installed product.
10
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 manager

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

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

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

IBM Power Systems management provides lifecycle management of your IBM Power systems, and platform managers such as Hardware Management Console (HMC) and Integrated Virtualization Manager (IVM) platform managers, including discovery, health and status monitoring, configuration, updates, and virtualization. It also provides platform-specific functions. You can use the IBM Power Systems management plug-in to:
12
v Manage the following Power Systems environments that might include servers with 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 module v Perform management tasks on systems that are under the control of HMC and IVM, including managing power, creating virtual serves, editing virtual server resources, and relocating virtual servers between host systems. v Perform management tasks that are available from the IBM Systems Director Web interface for supported versions of AIX and IBM i. For additional information about managing the virtualization and consolidation on Power systems using IBM Systems Director, see the Managing IBM Power Servers with IBM Systems Director 6.1 white paper on the Web at: www.ibm.com/ common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH &appname=STGE_PO_PO_USEN&htmlfid=POW03011USEN &attachment=POW03011USEN.PDF
IBM System Storage management

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

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

The Active Energy Manager plug-in helps you to monitor and manage the power and cooling needs of IBM servers and IBM BladeCenter systems. Non-IBM systems
13
can also be monitored using metering products, such as power distribution units (PDU), sensors, and integration with facility software. You can use Active Energy Manager to: v v v v Allocate less power and cooling infrastructure to your IBM servers. Reduce power usage on select IBM servers. Plan for the future by viewing trends of power usage over time. Determine power usage for all components of a rack.
Active Energy Manager is a licensed plug-in that supports Windows, Linux on Power 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 and recover blades in your environment. You can use this plug-in to: v Pre-assign MAC and WWN addresses, as well as storage boot targets for up to 100 chassis or 1400 blade servers. v Create addresses for blade servers, save the addresses to a configuration file, and deploy the addresses to the blade slots in the same chassis or in up to 100 different chassis without any blade servers installed in the chassis. v Automatically replace a failed blade from a designated pool of spare blades. BladeCenter Open Fabric Manager is a for-fee plug-in that supports all platforms that IBM Systems Director supports.
Service and Support Manager plug-in

The Service and Support Manager plug-in, which includes the Electronic Service Agent tool, identifies and reports hardware problems and service information automatically to IBM for service and support. All information sent to IBM is stored in a secure IBM database and used for improved problem determination. You can use Service and Support Manager to: v Place service calls to IBM automatically if the system is under a service agreement or warranty. v Collect and send scheduled system inventory and diagnostic inventory to an IBM database. This inventory information is available to IBM support representatives when they are solving your problem. v Communicate with IBM using a secure Internet connection using encryption and authentication. Service and Support Manager is a free plug-in that is supported on the following operating systems when installed on the IBM Systems Director management server: v Windows for 32bit and 64bit systems v Linux on System x for 32bit and 64bit systems v Linux on Power Systems v Linux on System z v AIX
14
IBM Systems Director Network Control plug-in

The Network Control plug-in provides facilities to discover, inventory, and monitor network 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 IBM Systems Director. When you install or upgrade to IBM Systems Director V6.2, the Manage page displays Network Management in place of IBM Systems Director Network Control.
IBM Systems Director Storage Control 4.2.1

The Storage Control plugin lets you manage an expanded set of storage subsystems and Fibre Channel switches. You can use Storage Control to discover and collect inventory, and monitor device health. These subsystems include the IBM DS8000 family (DS8100, DS8300, DS8700, DS8800), the SAN Volume Controller, and the IBM Storwize V7000, as well as the Brocade Fibre Channel switches. Important: You must use IBM DB2 Enterprise Edition v. 9.7 (GA version only; fix packs are not supported) as the local database application for Systems Director to use Storage Control. That is, the correct version of IBM DB2 must be installed on the same system as Systems Director. Migration from other databases within Systems Director to IBM DB2 is not supported. For more information about Storage Control, see this topic: IBM Systems Director Storage Control 4.2.1.
IBM Systems Director Transition Manager for HP Systems Insight Manager plug-in
The Transition Manager for HP Systems Insight Manager plug-in enables you to discover systems that are being managed by HP Systems Insight Manager and smoothly make the transition to managing the systems in IBM Systems Director. Transitioned systems can be either IBM and non-IBM hardware. After the transition is complete, you can manage the systems using IBM Systems Director which can provide 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 in your IT environment. Use IBM Systems Director VMControl Express Edition, IBM Systems Director VMControl Standard Edition, and IBM Systems Director VMControl Enterprise Edition to manage virtual servers, virtual appliances, workloads, and system pools across multiple hardware platforms and virtualization 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-in for IBM Systems Director that provides a centralized point of control for managing workload partitions (WPARs) across a collection of managed systems running AIX . Workload Partition Manager can manage heterogeneous environments of
15
managed systems at different AIX technology levels. However, to exploit full management capabilities, the Workload Partition Manager agent should be updated to the latest version. The following features are supported on all AIX technology levels: Cross-system management of WPARs, including lifecycle management Global load balancing with application mobility Web-based administration of basic WPAR operations and advanced management tasks Monitoring and reporting of WPAR performance metrics.
Upward integration
IBM Systems Director lets you to make the most of your existing enterprise management structure by upwardly integrating with many workgroup and enterprise-management products. IBM Systems Director upward integration modules (UIMs) and management packs enable non-IBM workgroup and enterprise-management products to interpret and display data that is provided by Common Agent and Platform Agent. IBM Systems Director UIMs and management packs provide enhancements to the enterprise-management products that you can use to collect inventory data, view IBM Systems Director event notifications, and for some UIMs, distribute IBM Systems Director software packages. With the IBM Systems Director UIMs and management packs, you can use your enterprise-management software to manage systems that have Platform Agent or Common Agent software installed on them. You can use Platform Agent software to: v Gather detailed inventory information about your systems, including operating system, memory, network adapters, and hardware. v Track your systems with features such as power management, event log, and system monitor capabilities. Platform Agent uses some of the latest systems-management standards, including Common Information Model (CIM), Web-Based Enterprise Management (WEBM) and Extensible Markup Language (XML), to provide compatibility with your existing enterprise-management software. For more information about upward integration modules, see IBM Systems Director Upward Integration Modules in the IBM Systems information center on the Web at publib.boulder.ibm.com/infocenter/director/v6r2x/topic/ com.ibm.director.uims.helps.doc/fqs0_main.html. You can also configure IBM Systems Director Server to forward alerts (such as SNMP) to higher-level enterprise managers, including CA Unicenter NSM, HP OpenView NNM, HP OpenView Operations for Windows, Tivoli Netview, Tivoli Management Framework, Microsoft Systems Center Operations Manager, and Microsoft Systems Management Server.
16
Chapter 2. Planning for IBM Systems Director

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

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

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

IBM Systems Director Server has certain hardware requirements. These requirements can vary depending on the workload. If you are interested in information about how to plan, implement, configure, and use an IBM Systems Director Server to manage a large configuration with optimal performance, see the Performance Tuning and Scaling Guide for IBM Systems Director 6.2. The Performance Tuning and Scaling Guide also contains information about the following topics: v Running IBM Systems Director plug-ins, such as IBM Systems Director Active Energy Manager and IBM Scalable Systems Manager v Integration with Tivoli products v Implementing High Availability (HA) Additionally, the IBM Systems Workload Estimator for IBM Systems Director 6.2.1is a web-based tool to provide hardware sizing recommendations for systems running the IBM Systems Director server. Recommended hardware requirements for IBM Systems Director Server running on AIX : IBM Systems Director Server has certain hardware requirements to run on supported IBM Power systems running AIX , including IBM Power JS21 and later blade servers. Hardware requirements for running IBM Systems Director for AIX systems can be obtained by using the IBM Systems Workload Estimator. The IBM Systems Workload Estimator is a web tool for estimating hardware requirements for various workloads. You can access the IBM Systems Workload Estimator workload for IBM Systems Director at www-01.ibm.com/support/ docview.wss?uid=nas7cd6a96f49d05f608862577420075ca9a&myns=x016 &mynp=OCSGZ2Z3&mync=E.
17
The IBM Systems Workload Estimator asks several questions about your intended usage, such as the number of systems you are managing and whether you are using a local or remote database. After the questions are answered, IBM Systems Workload Estimator will generate a drop-down list of system model and features that meet the resource requirements of Systems Director including an estimate of the number of cores, memory, disk capacity, and number of disk drives required. It also shows a Growth Solution which can handle further growth for managing larger 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 IBM Systems 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 the non-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 IBM Systems Director to take advantage of additional memory. On AIX, the Java heap size setting is the following path: /opt/ibm/director/lwi/conf/overrides/ director.javaopt. On 64-bit operating systems, the optimal heap size value is typically in the range of 2 GB (-Xmx2g) to 8 GB (-Xmx8g), depending on the systems being managed and the amount of physical memory available on the IBM Systems Director Server. The following table provides information about disk storage requirements for installing IBM Systems Director Server. These requirements include Common Agent and Platform Agent, which are installed with IBM Systems Director Server. These requirements do not include disk storage requirements for running IBM Systems Director Server and the database, updating IBM Systems Director Server or for downloading and staging updates (such as AIX, HMC, or system firmware updates) with Update manager. Note: The disk storage requirements in the table below are for a merge installation of a 6.2 server and 6.2.1 updates. If you are performing an update installation from 6.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 / /usr /var Disk space required 50 MB 256 MB 512 MB
18
Table 1. Disk storage requirements for installing IBM Systems Director Server (continued) File system /tmp Disk space required 2 GB Note: This space is only required during the installation and is freed after the installation is complete. 5 GB Size specified on downloads website
/opt Web download file (SysDir6_2_1_DVD_AIX.iso)
(*) 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 IBM Systems Director version IBM Systems Director Best Practices Wiki
Hardware requirements for systems running Common Agent or Platform Agent

Common Agent and Platform Agent have minimum processor speed, random access memory (RAM), and disk space requirements. Note: The disk space listed is the minimum requirement for an installation using the default selections.
IBM Power systems running AIX

Note: On systems that do not provide display capability, such as IBM Power blade servers, you must export IBM Systems Director Web interface using either the xhost command or SSH tunneling. The IBM Systems Director Web interface requirements apply to the receiving system.
Table 2. Servers running AIX : Minimum hardware requirements Requirements Processor speed Memory (RAM) Common Agent POWER5, POWER6 or POWER7 512 MB (minimum)
Tables 8 and 9 provide information about disk storage requirements for installing Common Agent. Table 8 covers the space requirements for the actual installation. Table 9 covers additional space requirements based on the installation method. The total disk storage requirement must be calculated by combining Table 8 and Table 9. Note: If you are performing an update installation from 6.2.0.x to 6.2.1, see Determining 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 / /usr Disk space required <5 MB 250 MB
Chapter 2. Planning
19
Table 3. Disk storage requirements for installing Common Agent (includes Platform Agent) (continued) File system /var /tmp /opt Disk space required 300 MB 200 MB 140 MB
Note: The /tmp space is only required during the installation and is freed after the installation 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) Space needed to extract web downloaded file: SysDir6_2_1_Common_Agent_Installp_AIX_VIOS.tar.gz (Location of your choice) Manual installation using SysDir6_2_1_Common_Agent_AIX.tar.gz Web download file SysDir6_2_1_Common_Agent_AIX.tar.gz (Location of your choice) Space needed to extract web downloaded file SysDir6_2_1_Common_Agent_AIX.tar.gz (Location of your choice) Space needed to extract dir6.2.1_commonagent_aix into /tmp/ DirectorAgentselfextract.<identifier> Size specified on downloads website Size specified on downloads website
290 MB
290 MB
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) Server system: Space needed to extract web downloaded file (SysDir6_2_1_Common_Agent_AIX.tar.gz) Target system: Deploy dir6.2.1_commonagent_aix file Target system: Space needed to extract dir6.2.1_commonagent_aix into /tmp/DirectorAgentselfextract.<identifier> Size specified on downloads website 290 MB 290 MB 290 MB
Determining disk space requirements for applying updates

Before 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 the update. 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 GB v /tmp: 1.5 GB v /opt: 1.6 GB v /var: 100 M
20
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 Resource Explorer. 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 the update. 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% of the size of the disk location.
Supported IBM systems and products

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

IBM Systems Director provides support for IBM BladeCenter chassis and blade servers.
Chapter 2. Planning
21
IBM BladeCenter chassis

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

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

IBM Systems Director supports discovery and monitoring of these network devices.
22
Task support for network management

Find out which tasks are supported by Network Management for your network devices. The tables provide lists of network devices, separated by type, and notes which tasks are only supported by IBM Systems Director Network Control. The following tasks are included in the support tables: Discovery, Request Access, Inventory, Monitoring, and Alerts Use these basic network management functions to discover network devices, request access, gather information, and monitor status and device health. Network adapters do not require discovery. Note: To associate physical server subnets and VLANs in the Systems by VLAN and Subnet view, the switch inventory must be collected after network topology is collected. Correct VLAN information in views like Systems by VLAN and Subnet or the VLAN ID column in some groups require that the switch vendor support the standard SNMP Q-Bridge MIB (1.3.6.1.2.1.17.7). Packet Internet Groper (ping) and Traceroute These network diagnostic tools help you test connections between network devices and troubleshoot network systems connectivity. Network diagnostic support is listed in the table, however, they cannot be used on switches configured with a second privileged mode password or on IPv6 targets. Stacked Switch support Switch stacking allows you to combine several physical switches into one logical entity. The stacked switch functions as a single network device, with one IP address for the stack. IBM Systems Director Network Control provides full support for some switch modules. Other switch modules are supported only in their individual (non-stacked) configurations. Configuration Management You can work with the VLAN configuration and Protocol configuration of some devices using IBM Systems Director Configuration Manager. The following tables indicate which devices support these configuration management tasks. Context launch to vendor management You can use launch-in-context to access vendor configuration software for some devices directly from the IBM Systems Director interface. This is a task-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 devices v BladeCenter Ethernet switch devices v Non-BladeCenter Ethernet switch devices v Other network devices, including Fibre Channel over Converged Enhanced Ethernet (FCoCEE) switches, Fast Connection Failover (FCF) bridges, Security appliances, and virtual network devices.
Chapter 2. Planning
23
Note: v The following tables identify supported network devices which have been tested for interoperability with IBM Systems Director. Other network devices with limited interoperability might be recognized during discovery and inventory.
Table 5. Adapter devices and supported network management tasks Tasks Supported Device 2 Port Ethernet Expansion Card (1xE) for IBM BladeCenter Brocade 2-port 10Gb CNA adapter (CFFh) for IBM BladeCenter Brocade 10Gb CNA for IBM System x CIOv 2-port 4Gb FC HBA CIOv 2-port 8Gb FC HBA Emulex Virtual Fabric Adapter (CFFh) for IBM BladeCenter Ethernet Expansion Card (CIOv) for IBM BladeCenter Foxconn CFFv Gb Ethernet Expansion Card Intel 2-port 10Gb Ethernet Expansion Card (CFFh) for IBM BladeCenter Intel PRO/1000 PF 1P, PCIe x4, IOAT NetXtreme II 10 GigE Express Fiber SR Adapter QLogic 2-Port 10Gb CFFh Converged Network Adapter for IBM BladeCenter QLogic Dual-port 10Gb CNA for IBM System x Inventory Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Monitoring Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Table 6. BladeCenter Ethernet switch devices and supported network management tasks Tasks Supported Discovery, Inventory, Request Access, Monitoring, and Alerts Ping Yes1 Yes
Device Blade Network Technologies 1/10Gb Uplink Ethernet Switch Module for IBM BladeCenter (44W4404) Blade Network Technologies 10 Gb Uplink Ethernet Switch Module for IBM BladeCenter (32R1783) Blade Network Technologies 6-port 10 Gb Ethernet Switch Module for IBM BladeCenter (39Y9267) Blade Network Technologies Layer 2/3 Fiber Gb Ethernet Switch Module for IBM BladeCenter (32R1861) Blade Network Technologies Layer 2/3 Copper Gb Ethernet Switch Module for IBM BladeCenter (32R1860)
Configuration Traceroute Stacked Switch Management Yes No Yes
Yes1
Yes
Yes
No
Yes
Yes1
Yes
Yes
No
Yes
Yes1
Yes
Yes
No
Yes
Yes1
Yes
Yes
No
Yes
24
Table 6. BladeCenter Ethernet switch devices and supported network management tasks (continued) Tasks Supported Discovery, Inventory, Request Access, Monitoring, and Alerts Ping Yes1 Yes
Device Blade Network Technologies Layer 2-7 Gb Ethernet Switch Module for BladeCenter (32R1859) Blade Network Technologies Virtual Fabric 10Gb Switch Module for IBM BladeCenter (46C7191) Cisco Catalyst Switch Module 3012 for IBM BladeCenter (43W4395) Cisco Catalyst Switch Module 3110G for IBM BladeCenter (41Y8523) Cisco Catalyst Switch Module 3110X for IBM BladeCenter (41Y8522) Cisco Catalyst 3750 Cisco Nexus 4001I Switch Module for IBM BladeCenter (46M6071)2 Cisco Systems Intelligent Gb Fiber Ethernet Switch module for IBM BladeCenter (32R1888) IBM BladeCenter 4-port Gb Ethernet switch module IBM Server Connectivity Module for IBM BladeCenter (39Y9324) Intel Gigabit Ethernet Switch Module for IBM BladeCenter T Note:
Configuration Traceroute Stacked Switch Management Yes No Yes
Yes1
Yes
Yes
No
Yes
Yes Yes Yes Yes Yes Yes
Yes Yes Yes No Yes Yes
Yes Yes Yes No Yes Yes
No Yes Yes Yes No No
No No No No Yes No
Yes Yes1 Yes
No No Yes
No No No
No No No
Yes Yes Yes
1. Many hardware devices require you to install a vendor plug-in before you can request full access. For information 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 Discovery, Inventory, Request Access, Monitoring, and Alerts Yes Context launch to vendor management No
Device Blade Network Technologies RackSwitch G8000 Blade Network Technologies RackSwitch G8052
Ping Yes
Traceroute Yes
Configuration Management Yes
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 Discovery, Inventory, Request Access, Monitoring, and Alerts Yes Context launch to vendor management No
Device Blade Network Technologies RackSwitch G8124 Blade Network Technologies RackSwitch G8264 Cisco Catalyst 3750-48 Cisco Catalyst 4948 IBM Ethernet Router B04M IBM Ethernet Router B08M IBM Ethernet Router B16M IBM Ethernet Router B32M IBM Ethernet Router J02M IBM Ethernet Router J06M IBM Ethernet Router J11M IBM Ethernet Switch B08R IBM Ethernet Switch B08S IBM Ethernet Switch B16R IBM Ethernet Switch B16S IBM Ethernet Switch B24C (Copper) IBM Ethernet Switch B24C (Fiber) IBM Ethernet Switch B24X IBM Ethernet Switch B24Y IBM Ethernet Switch B04R IBM Ethernet Switch B48C (Copper) IBM Ethernet Switch B48C (Fiber) IBM Ethernet Switch B48G IBM Ethernet Switch B48Y IBM Ethernet Switch B50C (Copper) IBM Ethernet Switch B50C (Fiber) IBM Ethernet Switch B50G IBM Ethernet Switch J08E IBM Ethernet Switch J48E
Ping No
Traceroute No
Configuration Management Yes
Yes
No
No
No
No
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
No No Yes Yes Yes No Yes Yes Yes Yes Yes No Yes No No Yes No No Yes Yes Yes No Yes Yes Yes Yes Yes
No No Yes Yes Yes No Yes Yes Yes Yes Yes No Yes No No Yes No No Yes Yes Yes No Yes Yes Yes Yes Yes
No No No No No No No No No No No No No No No No No No No No No No No No No No No
No No No No No No No No No No No No No No No No No No No No No No No No No No No
26
Table 7. Ethernet switch devices, including Internet routers, and supported network management tasks (continued) Tasks Supported Discovery, Inventory, Request Access, Monitoring, and Alerts Yes Yes Yes Yes Yes Yes Yes Yes Context launch to vendor management Yes2 Yes2 No No No No No No
Device IBM System Storage SAN384B IBM System Storage SAN768B IBM Ethernet Switch J02M IBM Ethernet Switch J16E Juniper EX2200 IBM Ethernet Switch J45E (Tsunami) SMC Networks 8848M TigerStack II 10/100/1000 SMC Networks 8126L2 TigerSwitch 10/100/1000 Note:
Ping No No Yes Yes No No No Yes
Traceroute No No Yes Yes No No No Yes
Configuration Management Yes1 Yes1 No No No No No No
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 Discovery, Inventory, Request Access, Monitoring, and Alerts Ping Yes1 Yes Yes Yes Yes N/A No Yes Yes Yes
Device 10Gb Ethernet Pass-Thru Module for IBM BladeCenter Brocade FCoE Switch Module for IBM BladeCenter IBM Converged Switch B32 Cisco Nexus 5010 Switch for IBM System Storage Cisco Nexus 5020 Switch for IBM System Storage
Device Type Pass-Thru device FCoCEE Switch FCoCEE Switch Standalone FCoCEE switch Standalone FCoCEE switch
Context launch Configuration to vendor Traceroute Management management N/A No No Yes Yes No Yes Yes2 No No No Yes Yes3 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 Discovery, Inventory, Request Access, Monitoring, and Alerts Ping Yes No
Device FastIron WS 624G or FastIron WS 624G-POE
Device Type Switch Base Layer 3 Router POE Switch POE Base Layer 3 Router
Context launch Configuration to vendor Traceroute Management management No No No
FastIron WS 648G or FastIron WS 648G-POE
Switch Base Layer 3 Router POE Switch POE Base Layer 3 Router
Yes
No
No
No
No
IBM Ethernet Appliance J34S IBM Ethernet Appliance J36S IBM Ethernet Appliance J56S IBM Ethernet Appliance J58S QLogic Virtual Fabric Extension Module for IBM BladeCenter (46M6172) Notes:
Security Appliance Security Appliance Security Appliance Security Appliance FCF bridge module
Yes Yes Yes Yes Yes
No No No No Yes
No No No No No
No No No No No
No No No No No
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 devices

Systems Director manages a wide variety of storage devices. Supported storage devices are: disks, switches, internal RAID controllers, and RAID subsystems. See the appropriate table to find the information you need. Supported devices on page 29: This section lists the supported storage devices, subsystems, and storage modules.
28
Supported devices, based on operating system and Systems Director version on page 31: This section lists the supported storage devices, subsystems, and storage modules, depending on the version of Systems Director that you are running. Supported devices and actions on page 36: These tables list the storage devices and the actions you can perform on each with Systems Director. RAID controller support on page 37: This table describes Storage Manager support of RAID controllers managed with various versions of Platform Agents in IBM Systems Director. Storage devices and IPv6 support on page 37: This section lists the storage devices 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 their access 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 SAS RAID Controller Modules, supported only on Windows (2003 and 2008) and Linux on System x systems. v Network Storage, which is an external SAN storage system. Network storage is accessed with storage switches, adapters, and protocols such as Fibre Channel, SAS, or iSCSI IBM IBM IBM IBM IBM System System System System System Storage Storage Storage Storage Storage DS4100, DS4300, DS4500, DS4700, DS4800 DS5020, DS5100, DS5300 DS6000 DS3200, DS3300, DS3400, DS3500 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
Supported devices, based on operating system and Systems Director version

Table 9. Supported devices, based on operating system and Systems Director version Hardware type Model Systems Director version supported Provider Name Version /SMI-S Level /CIMOM Operating system supported Red Hat Enterprise Linux (RHEL) 4 Windows 2003 SLES 9 6.1.1 Cardinal Platform Agent CIMOM VMWare ESX, 3.5 or 4.0 00.07.05.xx / SMI-S 1.1 IBM Systems Director Platform Agent 6.1.x or 6.2.x RHEL 4 or 5 Windows 2003 (32- or 64-bit) Windows 2008 (32- or 64-bit) SLES 9, 10, or 11 VMWare ESX, 3.5 or 4.0 00.17.05.xx / SMI-S 1.1 IBM Systems Director Platform Agent 6.2.1 RHEL 4 or 5 Windows 2003 (32- or 64-bit) Windows 2008 (32- or 64-bit) SLES 9, 10, or 11 VMWare ESX, 3.5 or 4.0 LSI IRC M5014 / M5014 / M5025 6.2.1 10M09 00.17.05.xx / SMI-S 1.1 IBM Systems Director Platform Agent 6.2.1 RHEL 4 or 5 Windows 2003 (32- or 64-bit) Windows 2008 (32- or 64-bit) SLES 9, 10, or 11 Windows 2003 8.4 or 9.0 6.1.0 Adaptec ICC 5.20.31 L1CIMOM RHEL 4 or 5 VMWare ESX3.5 SLES 9 or 10 Adaptec ServeRAID 4/5/6/7 6.2.0 ServeRAID Plug-in 9.10.x Windows 2003 R2 SP3
Chapter 2. Planning R2 Windows 2008 31
LSI IRC 1064/1064e/1068
6.1.0
Patni
IBM Systems Director Platform Agent 5.20.31
6.1.2 Flamingo 6.2.0 LSI IRC 1064/1064e/1068/ 1078
6.2.1
10M09
Integrated RAID Controller (IRC) attached to a System x
9.2.0 IBM Systems Director Platform
RHEL 4.8 or 5.4
Table 9. Supported devices, based on operating system and Systems Director version (continued) Hardware type Model Systems Director version supported 6.1.x NSSM 3GB (System x) 6.2.0 6.2.1 2.99 RSSM R1 IBM BladeCenter S SAS RAID Controller 6.1.x Adaptec RSSM R1 SMI-S 1.1IBM Systems Director Platform Agent 5.20.31 Windows 2003 (32- or 64-bit) Windows XP RHEL 4 and 5 SLES 9 or 10 Windows 2003 (32- or 64-bit) 4.29, SMI-S 1.1 IBM Systems Director Platform Agent 6.2.1x Windows 2008 (32- or 64-bit) Windows XP RHEL 4 and 5 SLES 9, 10, and 11 (32- or 64-bit) none Provider Name Version /SMI-S Level /CIMOM Operating system supported
RSSM R2.1 (System x and System p)
6.2.0 6.2.1
Adaptec RSSM R2.1
32
Table 9. Supported devices, based on operating system and Systems Director version (continued) Hardware type Model Systems Director version supported 6.1.0 QLogic 6.1.1 6.1.x Qlogic 2GB, 4GB, or 8GB 6.2.0 6.2.1 Windows 2003 (32-bit) Brocade 2GB or 4GB (Chassis-mounted or standalone) 6.1.x 6.2.0 6.2.1 Brocade 120.9.0 (SMI-S 1.2) Windows 2008 (32-bit) RHEL 4 AIX 5.3, SLES 10 Windows 2003 (32- or 64-bit) 4.1, 4.1.1 Windows 2008 (32- or 64-bit) RHEL 4 and 5 SLES 9, 10 and 11 Brocade 8GB (standalone) Windows 2003 (32- or 64-bit) Windows 2008 (32- or 64-bit) 6.2.1 Storage Control 4.2.1 Windows 2008 R2 (64-bit) AIX 5.3 or 6.1 RHEL 5.x McDATA Sphereon or Intrepid Windows 2003 Server 6.2.1 Storage Control 4.2.1 Windows 2008 RHEL 4 QLogic SIM-S 1.1 Embedded SMI-S 1.0.x Embedded Provider Name Version /SMI-S Level /CIMOM Operating system supported
QLogic 2GB or 4GB
6.1.x with Storage System Pools FC Switch 6.2.0 with Storage System Pools
Storage Control or IBM Tivoli Storage Productivity Center
Chapter 2. Planning
33
Table 9. Supported devices, based on operating system and Systems Director version (continued) Hardware type LSI Storage DS3400/FC, DS4100, DS4200, DS4300, DS4400, DS4500, DS4700, and DS4800 Model Systems Director version supported Provider Name Version /SMI-S Level /CIMOM Operating system supported Windows 2003 (32- or 64-bit) 6.1.x Engenio 6.2.0 Windows 2008 (32- or 64-bit) RHEL 4 and 5 AIX 5.3 and 6.1 SLES 9 or 10 Windows 2003 (32- or 64-bit) DS3400/FC, DS4100, DS4200, DS4300, DS4400, DS4500, DS4700, DS4800 DS5020, DS5100, and DS5300 Windows 2008 (32- or 64-bit) RHEL 4 and 5 AIX 5.3 and 6.1 SLES 9, 10, and 11
10.50.G0.04 (SMI-S 1.1 )
6.2.0 Eagle 6.2.1
10.10.G5.xx, SMI-S 1.3
34
Table 9. Supported devices, based on operating system and Systems Director version (continued) Hardware type IBM storage 6.1.x DS6800 6.2.0 IBM DS6000 5.2.1.139 SMI-S 1.1 Model Systems Director version supported Provider Name Version /SMI-S Level /CIMOM Operating system supported Windows 2003 (32- or 64-bit) AIX 5.3 SP 3 RHEL 3 SLES 9 Windows 2003 (32- or 64-bit) 6.1.x with Storage DS8300, SAN Control Volume Controller 6.2.0 with Storage 4.3 and 5.1 Control Storage Control or IBM Tivoli Storage Productivity Center Windows 2008 (32- or 64-bit) 4.1, 4.11 RHEL 4 and 5 AIX 5.3 and 6.1 SLES 9, 10, and 11 Windows 2003 (32- or 64-bit) DS8300, SAN Volume Controller 6.1, IBM Storwize V7000 Storage Control or IBM Tivoli Storage Productivity Center Windows 2008 (32- or 64-bit) 4.2.1 Windows 2008 R2 (64-bit) AIX 5.3 and 6.1 RHEL 5.x Windows 2003 (32- or 64-bit) Storage Control or IBM Tivoli Storage Productivity Center Windows 2008 (32- or 64-bit) 4.2.1 Windows 2008 R2 (64-bit) AIX 5.3 and 6.1 RHEL 5.x NAS storage N-series (N3600 or N3700) - NFS only 6.1.2 6.2.0 6.2.1 NetApp 3.0.2 SMI-S 1.2 RHEL 3 and 4 (on ES and AS) Windows 2003 (32-bit) SLES10 (32-bit)
6.2.1
IBM XIV 2810-A14, 2812-A14
6.2.0 6.2.1
Chapter 2. Planning
35
Supported devices and actions

These tables list the storage devices and the actions you can perform on each with Systems Director.
Table 10. Storage management tasks and supported devices
LSI SAS controllers IBM BladeCenter SAS Modules Fibre Channel Switches (2/4/8 GB) IBM System Storage DS and N series D S 3 5 0 0 Yes Yes Yes Legacy Raid Controllers
Task Discovery Inventory collection Monitoring (alerts and status) Physical Topology Logical Topology Provisioning SAS zoning View and manage attached devices Config uration Update Installation Trouble shooting
1064 1064e 1068 Yes Yes Yes
1078 Internal RAID (IR) Yes Yes Yes
1078 Mega RAID (MR) Yes Yes Yes
Connectivity module Yes Yes No
Brocade (2/4/8) and RAID controller Qlogic (2/4/8) module Yes Yes Yes Yes Yes Yes
3K 4K 5K Systems Yes Yes Yes
6 0 0 0 Yes Yes Yes
N 3 6 0 0 Yes Yes Yes
ServeRaid 6/7/8/9 and LSI 1030 Yes Yes Yes
No Yes No No Yes
No Yes No No Yes
No Yes No No Yes
Yes Yes No Yes Yes
Yes Yes Yes Yes Yes
Yes Yes Yes No No
Yes Yes Yes No No
Yes Yes Yes No No
Yes No No No No
Yes Yes No No No
No No No No Yes
Yes Yes No
Yes Yes No
Yes Yes No
Yes Yes Yes
Yes No Yes
No No No
Yes No No
Yes No No
Yes No No
Yes No No
Yes Yes No
Table 11. Storage management tasks and supported devices (continued)

IBM Storwize V7000 Task Discovery Inventory collection Monitoring (alerts and status) Physical Topology Logical Topology Provisioning SAS zoning View and manage attached devices Config uration Yes Yes Yes No No No No No Yes Yes Yes Yes No No No No No Yes Yes Yes Yes No No No No No No Yes Yes Yes No No No No No No IBM System Storage DS8000 IBM XIV 2810, 2812 IBM SAN Volume Controller
36
Table 11. Storage management tasks and supported devices (continued) (continued)
IBM Storwize V7000 Update Installation Trouble shooting No No IBM System Storage DS8000 No No IBM XIV 2810, 2812 No No IBM SAN Volume Controller No No
RAID controller support

This table describes Storage Manager support of RAID controllers managed with various versions of Platform Agents in IBM Systems Director. The values in this table assume you have performed a basic install, without manually adding additional software to the agent. In the table, a value of Yes means that Discovery, Inventory, Configuration, and Alerts are supported, unless otherwise noted.
Table 12. RAID controller support
IBM Systems Director Platform agent version 5.20.31 or 5.20.32 IBM Systems Director version 6.1 Yes - Configuration is not supported on the Advanced RAID Controller (also called MegaRAID Controller) only. Not available Not available 6.1.1 and 6.1.2 Yes - Configuration is not supported. 6.2 and 6.2.1 Yes - Configuration is not supported.
6.1.1 or 6.1.2 6.2
Yes Not available
Yes 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 Legacy RAID Controllers Internal RAID Controllers IBM BladeCenter SAS Modules Device type ServeRAID versions 4/5/6/7/8/9 1064, 1064e, 1068, 1078 IR/MR SAS Connectivity Module (NSSM) RAIDed SAS Switch Module (RSSM) Fibre Channel Switches (2GB/4GB) QLogic 2GB/4GB IPv6 support Full compliance Full compliance Non-compliant (NSSM switches do not support IPv6) Not compliant (RSSM switches do not support IPv6) Partial compliance (QLogic Firmware version 7.4/7.8 or later supports IPv6) Full compliance Full compliance Note: Compliance statement does not include Engenio SMI Provider, which was not tested on the IBM Systems Director version 6.2 product. Full compliance Not compliant Not compliant
Chapter 2. Planning
Brocade 2GB/4GB IBM System Storage DS series DS3100, DS3200, DS3300 DS3400, DS3500 DS4100, DS4300, DS4300 (DS4K)
DS5020 DS6K DS8K
37
Table 13. Storage devices and IPv6 support (continued) Storage device IBM XIV IBM System Storage N series IBM Storwize IBM SAN Volume Controller Device type 2810-A14, 2812-A14 NS3600, N3700 v7000 IPv6 support Not compliant Not compliant Not compliant Not compliant
Storage restrictions
v You are advised to not install Storage Configuration Manager on a system that is running IBM Systems Director. v Storage devices such as memory, caches, and registers are not managed by Storage Management. v 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 IBM Systems Director 6.2. If you want to perform a separate installation of the IBM BladeCenter S SAS RAID Controller Module provider, you must ensure that the compatible 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 Level 1 Platform Agent PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.2.0 is compatible with IBM Systems Director 6.2 Platform Agent v IBM System Storage DS8000 requires IBM Systems Director Storage Control 4.2.1 or IBM TotalStorage Productivity Center 4.2.1 or higher. v IBM XIV requires IBM Systems Director Storage Control 4.2.1 or IBM TotalStorage Productivity Center 4.2.1 or higher. v 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. v IBM Storwize V7000 requires IBM Systems Director Storage Control 4.2.1 or IBM TotalStorage Productivity Center 4.2.1 (or higher).
Planning for IBM Systems Director Storage Control 4.2.1

Use the information in this section to plan for using Storage Control.
Network requirements
IBM Systems Director requires certain ports to be available and certain network protocols to be installed in order to enable communication among IBM Systems Director components and between the management server and managed systems. In addition, network connectivity must exist between the management server and managed systems, and between the management server and the IBM Systems Director Web interface browser system.
Nameserver (DNS) requirements

Ensure that the nameserver is configured correctly. If the nameserver is not configured correctly, you will encounter problems and potential failure during IBM Systems Director installation. The following conditions indicate that the nameserver is configured correctly:
38
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 a DNS server correctly configured for the network environment.
All available ports

IBM Systems Director processes require access to a number of ports in the installation and systems-management environment. If these ports are blocked by a firewall or used by another process, some IBM Systems Director functions might not work. Related reference VMware Documentation (http://www.vmware.com/support/pubs/) Important port considerations: When preparing your ports for an IBM Systems Director environment, there are some important considerations to remember or some IBM Systems Director functions might not work. Review the following considerations: v Depending on the system configuration, one of the following port pairings must be open in order to install IBM Systems Director: (For Microsoft Windows) 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 IBM Systems Director software components can use these ports. If custom alternative ports are chosen for the CIM Server, then those ports must be opened. v (Windows only) For any CIM-related function of the Common Agent to work, the HTTP port must be turned on for the Pegasus CIMOM, regardless of whether HTTPS is turned on (SSL is enabled). v If the CIMOM ports for a Platform Agent managed system are changed after IBM Systems Director Server discovers the system, the system will change to an Agentless managed system in IBM Systems Director. To correct this change, you must complete the following steps: 1. Delete the system in IBM Systems Director. 2. Shut down and restart the system. 3. Discover the system in IBM Systems Director. v Generic CIM clients should always check the IBM standard (primary) ports (for example, 15988/15989) and the back-up generic ports (for example, 5988/5989). v Windows firewall can interfere with discovery of managed systems running Windows 2003, Windows 2008, Windows XP, and Windows Vista. v If a proxy server is required to access the Internet from the management server, make sure that the management server is configured to use the proxy. v Update manager cannot use Digest or NTLM authentication to access update packages from IBM. If a proxy server is required, it must be configured to use Basic authentication. v IBM Systems Director Server can access the Internet through ports 80 (HTTP) and 443 (HTTPS). The firewall and proxy server must permit bi-directional communication through these ports.
Chapter 2. Planning
39
v By default, IBM Systems Director uses a random source port for SLP communication through a firewall to a Remote Supervisor Adapter. The random port causes problems when discovering the Remote Supervisor Adapter through a firewall because the Remote Supervisor Adapter responds using that random port. To resolve this problem, open any unused or private port. Then, edit the slp.prop file to use your selected port. The following example uses port 49150:
# Up to 10 parallel ports can be open at a time # when opening firewall ports, configure the source port and open # that port and the next 9 consecutive ports # default: 0 - random port used source.port=49150
v Neither z/VM nor the MAP Agent add any additional ports to those already provided by IBM Systems Director for standard communication. Instead of TCP/IP, z/VM communication APIs are used to communicate with the servers that provide information to IBM Systems Director and to enact any changes to z/VM servers. The communication is by means of sockets and the AF_IUCV address family. v For the TCP ports listed, the initiator opens a random port in the 1024-65535 range and then connects to the listener on the port listed. The listener responds by connecting to the original random port opened by the initiator. v The Remote Control, Update Install, and the Agent Installation wizard tasks use session support to increase data transmission. Session support within TCP/IP causes data to flow through a nonreserved port that is different from the one that IBM Systems Director typically uses for communication. Most firewalls will not transmit the data through this other port. v There are undocumented ports used by IBM Systems Director Server 6.2 and Common Agent. Prior to the 6.2 release, random source ports were used by default. Starting with IBM Systems Director Server 6.2, the default source port is now 14252 for both the server and agent. When firewalls are used to block traffic on unused ports, you must open additional source ports in order for Service Locator Protocol (SLP) discovery to work. On both the server and the agent, the configured or default source port plus the next sequential 25 ports must be opened. You may need to open more or fewer source ports, depending on the number of systems being discovered concurrently. Generally, if the discovery of many systems at a time is attempted and fails, more source ports need be opened, up to a maximum of 75. If discovery is done for only a small number of systems at a time, fewer ports need to be opened. The source port can be overridden on both the server and agent by configuring the port in the slp.prop file. Ports for IBM Systems Director Server: IBM Systems Director processes require access to a number of ports on the management server. If these ports are blocked by a firewall or used by another process, some IBM Systems Director functions might not work.
Table 14. Ports used by IBM Systems Director Server for communication Port 20 21 TCP or UDP Direction TCP TCP Inbound Inbound Communication description FTP data communication with BladeCenter I/O modules (switches and bridges) FTP communication with BladeCenter I/O modules (switches and bridges)
40
Table 14. Ports used by IBM Systems Director Server for communication (continued) Port 22 TCP or UDP Direction TCP Outbound Communication description SSH communication with: v Advanced management module and management module v BladeCenter I/O modules v Platform Agent installed on systems running Linux, including systems managed by HMC and IVM v SSH used by IBM Power systems to communicate with HMC/IVM v Non-Windows Agentless managed systems 23 TCP, UDP Outbound Telnet communication with: v Advanced management module, management module, Remote Supervisor Adapter, and Remote Supervisor Adapter II v BladeCenter I/O modules v Updates 69 80 UDP TCP Inbound Outbound TFTP communication with BladeCenter I/O modules (switches and bridges) HTTP communication with: v IBM Systems Director Web interface v Advanced management module, management module, Remote Supervisor Adapter, and Remote Supervisor Adapter II v BladeCenter I/O modules v IVM interface v Update manager 81 135 137 138 139 161 TCP TCP, UDP TCP, UDP TCP, UDP TCP, UDP UDP Outbound Outbound Outbound Outbound Outbound Outbound HTTPS communication with BladeCenter I/O modules (switches and bridges) (Windows only) Software installation and remote access communication with Platform Agent (Windows only) Communication with Agentless managed systems using Microsoft Windows DCOM (Windows only) Communication with Agentless managed systems using Windows DCOM (Windows only) Communication with Agentless managed systems using Windows Server Message Block (SMB) SNMP agent communication with: v Advanced management module, management module, Remote Supervisor Adapter, and Remote Supervisor Adapter II v BladeCenter I/O modules v Platform Agent Note: This port is used when the SNMP agent for the operating system is configured. v Agentless managed systems Note: This port is used when the SNMP agent for the operating system is configured. 162 TCP, UDP Outbound (TCP, UDP) Inbound (UDP) Simple Network Management Protocol (SNMP) trap communication with SNMP devices, including TCP for Tivoli NetView events. Examples of SNMP devices are advanced management module, management module, Remote Supervisor Adapter, and Remote Supervisor Adapter II.
Chapter 2. Planning
41
Table 14. Ports used by IBM Systems Director Server for communication (continued) Port 427 TCP or UDP Direction TCP, UDP Outbound and Inbound Communication description SLP communication with: v Advanced management module, management module, Remote Supervisor 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 directory agent 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 managed systems for the following features: v Software installation v Remote access communication v (Agentless-managed systems only) Inventory collection Non-SSL communication with the IBM i DRDA/DDM server job SSL communication with the IBM i DRDA/DDM server job SSL communication with the IBM i server port mapper Remote Management and Control Protocol (RMCP) unsecure communication with IPMI baseboard management controller (BMC) service processors Remote Management and Control Protocol (RMCP) secure communication with IPMI BMC service processors v Random port range for communication between IBM Systems Director Server with Intelligent Platform Management Interface (IPMI) service processors Note: You can specify a fixed port by modifying the asmDefinitions.properties file in the data directory. v For the TCP ports listed, the initiator opens a random port in the 1024-65535 range and then connects to the listener on the port listed. The listener responds by connecting to the original random port opened by the initiator. 1433 1521 1527 2033 TCP TCP TCP TCP Outbound and Inbound Outbound and Inbound Outbound and Inbound Inbound Microsoft SQL Server databases Oracle Database databases Apache Derby databases Communication with the IBM Systems Director Launched Tasks program using IBM Systems Director interprocess communication (IPC) smcli command-line interface Note: This port number can be changed. See Port configuration for smcli.
446 448 449 623
TCP TCP TCP UDP
Outbound Outbound Outbound Outbound
664 Random port in the 1024-65535 range
UDP TCP
Outbound Inbound
2044
TCP
Outbound and Inbound
42
Table 14. Ports used by IBM Systems Director Server for communication (continued) Port 3389 4066 TCP or UDP Direction TCP TCP Outbound and Inbound Inbound Communication description Remote Desktop Protocol, Remote Desktop Connection, or Remote Accessor for full screen access to systems running Windows Communication with the IBM Systems Director Launched Tasks program using IBM Systems Director interprocess communication (IPC) over SSL Virtual Network Computing (VNC), used by Remote Access (Windows and Red Hat Enterprise Linux) CIM Server unsecure port v (Windows and Red Hat Enterprise Linux) CIM Server secure port v HMC/IVM CIMOM 6641 6988 6989 6090 TCP TCP TCP TCP Inbound Inbound Inbound Outbound SAS switches CIM listener CIM listener TCP Command Mode communication between IBM Systems Director Server and advanced management module, management module, Remote Supervisor Adapter, and Remote Supervisor Adapter II v (All operating system platforms) HTTP communication between IBM Systems Director Server and the IBM Systems Director Web interface v HTTP used by IBM Power systems to communicate with CIM 8422 TCP Inbound v (All operating system platforms) HTTPS communication between IBM Systems Director Server and the IBM Systems Director Web interface v HTTPS used by IBM Power systems to communicate with CIM 8470 8471 8472 8473 8474 8475 8476 90009100 9470 9471 9472 9473 9474 9475 9476 TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP TCP Outbound Outbound Outbound Outbound Outbound Outbound Outbound Outbound Outbound Outbound Outbound Outbound Outbound Outbound Non-SSL communication with the IBM i central server job Non-SSL communication with the IBM i database server job Non-SSL communication with the IBM i data queue server job Non-SSL communication with the IBM i file server job Non-SSL communication with the IBM i network print server job Non-SSL communication with the IBM i remote command and distributed program call server job Non-SSL communication with the IBM i signon server job Communication Platform Agent managed system running Xen SSL communication with the IBM i central server job SSL communication with the IBM i database server job SSL communication with the IBM i data queue server job SSL communication with the IBM i file server job SSL communication with the IBM i network print server job SSL communication with the IBM i remote command and distributed program call server job SSL communication with the IBM i signon server job
5901 5988 5989
TCP TCP TCP
Outbound and Inbound Inbound Inbound
8421
TCP
Inbound
Chapter 2. Planning
43
Table 14. Ports used by IBM Systems Director Server for communication (continued) Port 9510 95119513 95149515 TCP or UDP Direction TCP TCP TCP Inbound, Outbound Inbound Communication description Communication with Common Agent and CAS Web services Agent manager Nonstop ports that are used to make sure Common Agent is restarted automatically if it fails. Note: Ports must be available, but not firewall accessible. Events from storage devices UDP Inbound Receives events sent by advanced management module, management module, Remote Supervisor Adapter, and Remote Supervisor Adapter II IBM Systems Director interprocess communication (IPC) with IBM Director Agent 5.20 IBM Systems Director interprocess communication (IPC) with IBM Director Agent 5.20 IBM Systems Director Server interprocess communication (IPC) support Source port for SLP communication There are undocumented ports used by IBM Systems Director Server 6.2 and Common Agent. Starting with IBM Systems Director Server 6.2, the default source port is now 14252 for both the server and agent. When firewalls are used to block traffic on unused ports, you must open additional source ports in order for Service Locator Protocol (SLP) discovery to work. On both the server and the agent, the configured or default source port plus the next sequential 25 ports must be opened. You may need to open more or fewer source ports, depending on the number of systems being discovered concurrently. Generally, if the discovery of many systems at a time is attempted and fails, more source ports need be opened, up to a maximum of 75. If discovery is done for only a small number of systems at a time, fewer ports need to be opened. The source port can be overridden on both the server and agent by configuring the port in the slp.prop file. 15988 15989 20000 TCP TCP TCP Inbound Inbound Inbound (Red Hat Enterprise Linux, SUSE Linux) CIM Server unsecure port (Red Hat Enterprise Linux, SUSE Linux) CIM Server secure port v CAS events v Communication with VMware Note: If you plan to manage systems running VMware VirtualCenter, or VMware ESX Server, see the VMware documentation to make sure port requirements are met: www.vmware.com/support/pubs/ 50000 61616 61617 TCP TCP TCP Inbound, Outbound Inbound, Outbound Inbound, Outbound IBM DB2 databases JMS communication with IBM Systems Director Server unsecure port JMS communication with IBM Systems Director Server secure port
10000 13991
14247 14248 14251 14252
UDP UDP UDP TCP, UDP
Inbound Outbound Inbound Inbound, Outbound
44
Ports for managed systems: IBM Systems Director processes require access to a number of ports on managed systems. Managed systems include Common Agent managed systems, Platform Agent managed systems, and Agentless managed systems.
Table 15. Ports on managed systems Port 22 TCP or UDP TCP Direction Inbound Communication description SSH communication with: v Advanced management module and management module v BladeCenter I/O modules v Platform Agent installed on systems running Linux, including systems managed by HMC and IVM v SSH used by IBM Power systems to communicate with HMC/IVM v Non-Windows Agentless managed systems 135 137 138 139 161 TCP, UDP TCP, UDP TCP, UDP TCP, UDP UDP Inbound Inbound Inbound Inbound Inbound (Windows only) Software installation and remote access communication with Platform Agent (Windows only) Communication with Agentless managed systems using Microsoft Windows DCOM (Windows only) Communication with Agentless managed systems using Windows DCOM (Windows only) Communication with Agentless managed systems using Windows Server Message Block (SMB) SNMP agent communication with: v Advanced management module, management module, Remote Supervisor Adapter, and Remote Supervisor Adapter II v BladeCenter I/O modules v Platform Agent Note: This port is used when the SNMP agent for the operating system is configured. v Agentless managed systems Note: This port is used when the SNMP agent for the operating system is configured. 389 427 TCP TCP, UDP Outbound Outbound and Inbound Used for LDAP SLP communication with: v Advanced management module, management module, Remote Supervisor 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 directory agent 445 TCP, UDP Inbound (UDP) (Windows only) Open on Agentless and Platform Agent managed systems for the following features: v Software installation v Remote access communication v (Agentless-managed systems only) Inventory collection
Chapter 2. Planning
45
Table 15. Ports on managed systems (continued) Port 5988 5989 TCP or UDP TCP TCP Direction Inbound Inbound Communication description (Windows and Red Hat Enterprise Linux) CIM Server unsecure port v (Windows and Red Hat Enterprise Linux) CIM Server secure port v HMC/IVM CIMOM 6988 6989 9510 9550 14247 14248 15988 TCP TCP TCP TCP UDP UDP TCP Inbound Outbound Inbound Both Inbound Outbound Inbound CIM listener CIM listener Communication with Common Agent and CAS Web services Used by IBM Systems Director Storage Control 4.2.1 as a server port IBM Systems Director interprocess communication (IPC) with IBM Director Agent 5.20 IBM Systems Director interprocess communication (IPC) with IBM Director Agent 5.20 v (For SUSE Linux Enterprise Server) CIM Server (alternative unsecure port) communication with Platform Agent managed system v Service processor communication with SUSE Linux Enterprise Server 10. v CIM Server (alternative unsecure port) communication with Platform Agent managed system 15989 TCP Inbound (For SUSE Linux Enterprise Server) CIM Server (alternative secure port) communication with Platform Agent managed system v CAS events v Communication with VMware Note: If you plan to manage systems running VMware VirtualCenter, or VMware ESX Server, see the VMware documentation to make sure port requirements are met: www.vmware.com/support/pubs/ 49153 TCP Inbound Used for SNMP alert
20000
TCP
Outbound
Security requirements
IBM Systems Director Server supports several products to house the registry used for system security.
User registry products and types

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

Before you install IBM Systems Director, make sure the firmware and device drivers are up-to-date. For more information, see and .
Operating system and software requirements

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

This section lists the operating systems on which IBM Systems Director Server, Common Agent, and Platform Agent are supported. This support can vary by version, release, and update. Make sure you review the supported operating systems for the version of IBM Systems Director in your environment. Operating system support for Systems Director 6.1.x is listed in the Supported operating 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 Systems Director component. IBM Systems Director supports only products that are currently supported by the owners or manufacturers of that product. If a product is no longer supported by its owner or manufacturer, it is implicit that IBM Systems Director also no longer supports that product. Starting in version 6.1, IBM Systems Director provides a Web interface for use with IBM Systems Director Server. IBM Director Console is no longer required. However, some tasks in the Web interface require the IBM Systems Director Launched Tasks program. For information about the IBM Systems Director Launched Tasks program and the tasks that require it, see Launched tasks and the IBM Systems Director Launched Tasks program. For operating-system support, see Operating systems supported by the IBM Systems Director Launched Tasks program.
Chapter 2. Planning
47
Unless stated otherwise, IBM Systems Director provides agentless support for all operating systems listed in this topic. Important: Installation of IBM Systems Director Server on third-party hardware is not 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 and third-party x86-based systems IBM Systems Director Server
Operating system VMware ESX Server, versions 3.5, 3.5.1, 3.5.2, 3.5.3, 3.5.4, and 3.5.5 Console Notes: 1. IBM Systems Director 6.1 Common Agent and IBM Director Core Services 5.20.3, Service Update 1 or Service Update 2, support VMware ESX Server versions 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.1 Platform 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 RSA in-band. You can manage it out-of-band by connecting it to the network and discovering it with IBM Systems Director. VMware ESX Server, versions 4.0, 4.0.1, 4.0.2, 4.1, 4.1.1 Console Notes: 1. IBM Systems Director 6.2.1 Common Agent with IBM Systems Director 6.2.1 Platform 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 and discovering it with IBM Systems Director. 2. You must turn off VMware ESX Server, version 4.0.x SLP, before installing IBM 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-bit compatibility mode only. Table 17. Support for guest operating systems
Common Agent X
Platform Agent X
Operating system Supported guest operating systems are those that are supported by both IBM Systems Director and the hypervisor. In other words, if the following conditions are 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 a guest OS on that hypervisor. See also the hypervisor product documentation for a list of supported operating systems.
IBM Systems Director Server X
Common Agent X
Platform Agent X
48
Table 18. AIX versions supported by IBM Systems Director on IBM Power systems IBM Systems Director Server X
Operating system 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 limited subset of the Agent Installation Wizard task, and the ability to launch the AIX Management Console for IBM AIX Version 5.3 agents. 2. For IBM Systems Director Server or Common Agent support provided by IBM AIX Version 5.3, newer TLs and Service Packs will be supported on the day of their general availability (GA). 3. Common Agent is installed with AIX ; it is started by default. 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 limited subset of the Agent Installation Wizard task, and the ability to launch the AIX Management Console for IBM AIX Version 6.1 agents. 2. For IBM Systems Director Server or Common Agent support provided by IBM AIX Version 6.1, newer TLs and Service Packs will be supported on the day of their general availability (GA). 3. Common Agent is installed with AIX ; it is started by default. IBM AIX Version 7.1 Note: 1. Agentless support includes only discovery, limited remote access, a limited subset of the Agent Installation Wizard task, and the ability to launch the AIX Management Console for AIX Version 7.1 agents. 2. For IBM Systems Director Server or Common Agent support provided by AIX Version 7.1, newer TLs and Service Packs will be supported on the day of their general availability (GA). 3. Common agent is installed with AIX operating system; it is started by default.
Common Agent X
Platform Agent
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 Systems Director component. Starting in version 6.1, IBM Systems Director provides a Web interface for use with IBM Systems Director Server. IBM Director Console is no longer required. However, some tasks in the Web interface require the IBM Systems Director Launched Tasks program. For information about the IBM Systems Director Launched Tasks program and the tasks that require it, see Launched tasks and the
Chapter 2. Planning
49
IBM Systems Director Launched Tasks program. For operating-system support, see Operating systems supported by the IBM Systems Director Launched Tasks program. Unless stated otherwise, IBM Systems Director provides agentless support for all operating systems listed in this topic. Important: Installation of IBM Systems Director Server on third-party hardware is not supported. Licensing requires that it be installed on IBM hardware only.
Table 19. Support for guest operating systems IBM Systems Director Server X
Operating system Supported guest operating systems are those that are supported by both IBM Systems Director and the hypervisor. See the hypervisor product documentation for a list of supported operating systems. Table 20. AIX versions supported by IBM Systems Director on IBM Power systems
Common Agent X
Platform Agent X
Operating system 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 limited subset of the Agent Installation Wizard task, and the ability to launch the AIX Management Console for IBM AIX Version 5.3 agents. 2. For IBM Systems Director Server or Common Agent support provided by IBM AIX Version 5.3, newer TLs and Service Packs will be supported on the day of their general availability (GA). 3. Common Agent is installed with AIX ; it is started by default. 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 limited subset of the Agent Installation Wizard task, and the ability to launch the AIX Management Console for IBM AIX Version 6.1 agents. 2. For IBM Systems Director Server or Common Agent support provided by IBM AIX Version 6.1, newer TLs and Service Packs will be supported on the day of their general availability (GA). 3. Common agent is installed with AIX operating system; it is started by default.
IBM Systems Director Server X
Common Agent X
Platform Agent
50
Table 20. AIX versions supported by IBM Systems Director on IBM Power systems (continued) IBM Systems Director Server X
Operating system IBM AIX Version 7.1: Note: 1. Agentless support includes only discovery, limited remote access, a limited subset of the Agent Installation Wizard task, and the ability to launch the AIX Management Console for IBM AIX Version 7.1 agents. 2. For IBM Systems Director Server or Common Agent support provided by AIX Version 7.1, newer TLs and Service Packs will be supported on the day of their general availability (GA). 3. Common agent is installed with AIX operating system; it is started by default.
Common Agent X
Platform Agent
Operating systems supported by the IBM Systems Director Launched Tasks program: Starting in version 6.1, IBM Systems Director provides a Web interface for use with IBM Systems Director Server. IBM Director Console is no longer required. However, some tasks in the Web interface require the IBM Systems Director Launched Tasks program. For information about the IBM Systems Director Launched Tasks program and the tasks that require it, see Launched tasks and the IBM Systems Director Launched Tasks program. Important: The launched-tasks feature in IBM Systems Director requires Java Web Start (JWS). The following operating systems are supported by the IBM Systems Director Launched Tasks program on IBM Power systems: v IBM AIX Version 5.3 v IBM AIX Version 6.1
Virtualization software supported by IBM Systems Director

This topic lists the supported virtualization software for IBM Systems Director. Hardware Management Console (HMC) v Hardware Management Console Version 7 R3.3.0 SP2, PTF MH01146; Version 7 R3.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 Management Console 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 Systems firmware Update manager extension, can only be installed for SF240_338 or later.
Chapter 2. Planning
51
It is recommended that you always apply the latest firmware level. The minimum firmware level is listed here. Integrated Virtualization Manager (IVM) v Integrated Virtualization Manager Version 1.5.2.1 and later fix packs; Version 2.1.0.10, fix pack 20.1 and later fix packs; Version 2.1.1 and later Notes: IBM Systems Director VMControl requires that Integrated Virtualization Manager 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.1 and later, and Version 2.2 Notes: The Common Agent is installed with Virtual I/O Server 2.1.1 and later; it is not started per default. For more information, see the IBM Systems Director Best Practices wiki - "IVM and VIOS topics". IBM Systems Director version 6.2.x provides IPv6 support for Virtual I/O Server 2.1.3 and later. Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled v Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled, Release 2 v Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled (supports Service Packs 1 and 2) Notes: 1. Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled, Release 2, Service Pack 1, is also supported by IBM Systems 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.x Platform Agent support Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled, Release 2. 3. Support for Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions 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 v v v VMware VMware VMware VMware ESX ESX ESX ESX Server Server Server Server 3.5.x Service Console 4.0.x Service Console 4.1 Service Console 4.1.1 Service Console
Note: VMware ESX Server 4.x is 64-bit, and is supported by way of 32-bit compatibility mode only. VMware ESXi
52
v VMware ESXi versions 3.5 Update 2, 3, 4, and 5, under the control of VMware VirtualCenter v VMware ESXi versions 4.0 Update 1 and 2, under the control of VMware vCenter 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 are not 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.1 v Red Hat Enterprise Linux 5.2, with Xen 3.1.2 v SUSE Linux Enterprise Server 10, with the Xen Virtual Machine Host Server option installed (XEN 3.0) 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 VM64514 VM64515 VM64516 VM64517 VM64596 VM64677 VM64595 VM64762 VM64813 Component name CMS CMS CMS CMS CMS CMS DIRM DIRM CMS PTF number for z/VM 5.4 UM32505 UM32503 UM32521 UM32522 UM32693 UM32765 UV61088 UV61099 Not required PTF number for z/VM 6.1 Not required Not required Not required Not required Not required UM32766 Not required UV61100 Required. See the APAR for the PTF number.
Note: z/VM 6.1 supports host and virtual server performance related monitors with APAR VM64813. However, host and virtual server performance related monitor 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 managed systems

IBM Systems Director provides support for the following virtualization software products on Agentless managed systems.
Table 22. Integrated Virtualization Manager versions supported by IBM Systems Director on Agentless 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 Agentless managed 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 browsers

Starting in version 6.1, IBM Systems Director provides a Web interface for use with IBM Systems Director Server. The Web interface requires that you use a supported Web browser. The following Web browsers are supported by IBM Systems Director for use with the IBM Systems Director Web interface: v Firefox, version 3.6 v Firefox, version 3.5 v Firefox, version 3.0 v Microsoft Internet Explorer, version 8.0 v Microsoft Internet Explorer, version 7.0 Tip: If Firefox rejects a self-signed certificate and does not give you and option to add an exception directly in the alert box, you can add the exception by selecting Tools > Options > Advanced > Encryption > View Certificates. After you click View Certificates, the Certificate Manager window opens. In the Certificate Manager window, select the Servers tab and highlight the Certificate Name for
54
your IBM Systems Director Server. Click Add Exception.... The Add Security Exception window opens. Verify the information in the Location field and click Confirm Security Exception.
Supported screen readers

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

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

Depending on the database application selected and the operating system of the management server, the database management system (DBMS) might be embedded, local, or remote. The three installation types are described below. Embedded DBMS The DBMS is installed on the management server as part of the IBM Systems Director Server installation, and shares the Java Virtual Machine with IBM Systems Director. Local DBMS The DBMS is installed on the management server on which IBM Systems Director Server is installed. Remote DBMS The DBMS is installed on a different server than the management server, and accessed remotely by IBM Systems Director Server. See Choosing the IBM Systems Director database application for additional information about these installation types.
Database versions supported by IBM Systems Director Server

The following table lists the database versions supported by IBM Systems Director Server on different management servers and provides information about whether the database server is embedded or can be installed locally or remotely. Note: The database versions that are listed represent both the database server and the database client where applicable.
Table 24. Database versions supported by IBM Systems Director Database Apache Derby Supported database versions v V10.5.3.1 (included with IBM Systems Director Server on AIX , Linux, and Windows) AIX Embedded Linux Embedded Windows Embedded
Chapter 2. Planning
55
Table 24. Database versions supported by IBM Systems Director (continued) Database IBM DB2 Supported database versions v Express version 9 v Version 9.1 with Fix Pack 4 or later v Version 9.5 with Fix Pack 1 or later v Version 9.7 with Fix Pack 1 or later Notes: 1. An IBM DB2 Version 9.5 or later client is required. 2. A 64-bit client is required to access an IBM DB2 database from 64-bit IBM Systems Director Server. Microsoft SQL Server v Microsoft SQL Server 2005 with Service Pack 3 v Microsoft SQL Server 2008 with Service Pack 1 Note: Requires Microsoft SQL Server JDBC Driver 2.0 or later. v Microsoft SQL Server 2005 Express Edition with Service Pack 2 v Microsoft SQL Server 2008 Express Note: Requires Microsoft SQL Server JDBC Driver 2.0 or later. Oracle Database v Version 9.2 v Version 10g release 1 (10.1.0.3 or later) v Version 10g release 2 v Version 11g release 2 Notes: 1. Oracle Cluster configuration is not currently supported. 2. A 64-bit client is required to access an Oracle Database database from 64-bit IBM Systems Director Server. Local or remote Local or remote Local or remote Local Local or remote AIX Local or remote Linux Local or remote Windows Local or remote
IBM Systems Director task support by operating system and agent levels
Some IBM Systems Director tasks are supported on certain operating systems or only on Platform Agent managed systems or Common Agent managed systems. For tasks whose support is not affected in this way, see IBM Systems Director task support not affected by operating systems. Support for IBM Systems Director tasks can vary depending on the following items:
56
The system or hardware device model (the resource) The operating system that is installed on a resource The service processor installed in the managed system The level of the device drivers that are installed on the managed system Attention: The device drivers that are available for a managed system depend on the service processor and operating system that are installed on the managed system. v The level of IBM Systems Director support installed on the system or device. In Table 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. v v v v Note: Typically, if a task is supported by Common Agent, it is also supported by IBM Director Agent version 5.20. However, support can vary for tasks that update systems or provide cross-platform support: - The Agent Installation Wizard can be used to install subagents only on Common Agent managed system. - (Configuration manager) Only operating system configuration plug-ins are supported by Common Agent and IBM Director Agent version 5.20. - (Update manager) Updates on System x and IBM BladeCenter systems and the IBM i operating system are supported by Common Agent and IBM Director Agent version 5.20. All other types of updates are supported by Common Agent only. - (Update manager) Updates on AIX , Linux on Power Systems, and Linux for System z are available only with Common Agent. The ability to distribute Linux updates is only available for Common Agent on Linux. - (Virtualization manager) IBM Director Agent version 5.20 requires a separate download and installation of the Virtualization Manager extension.
Table 25. IBM Systems Director task support across operating systems Operating systems Microsoft Virtual Server
Task Command Automation
AIX
IBM i
Linux IBM Systems Director Server, Level 2
VMware
Windows IBM Systems Director Server, Level 2
IBM Systems Level 2 Director Server, Level 2 IBM Systems Levels 1, 2 Director Server, Level 2 IBM Systems Level 2 Director Server, Level 2
Event Log
IBM Systems Levels 1, 2 Director Server, Levels 1, 2 IBM Systems Level 2 Director Server, Level 2
Levels 01, 1, 2
IBM Systems Director Server, Levels 1, 2 IBM Systems Director Server, Level 2
File Transfer
Level 22
Chapter 2. Planning
57
Table 25. IBM Systems Director task support across operating systems (continued) Operating systems Microsoft Virtual Server
Task Inventory (hardware)

3
AIX
IBM i
Linux
VMware
1
Windows IBM Systems Director Server, Levels 0, 1, 24
IBM Systems Levels 1, 2 Director Server, Level 2 IBM Systems Levels 0, 1, Director 25 Server, Levels 0, 2 Level 2 Level 2
7
IBM Systems Levels 0, 1, 2 Levels 0 , 1, Director 2 Server, Levels 0, 1, 24
Inventory (software)
IBM Systems Levels 0, 1, 2 Levels 0, 1, 2 IBM Systems Director Director Server, Server, Levels 0, 1, 2 Levels 0, 1, 2 Levels 1, 2
8, 7
Problems (formerly Hardware Status)6, 20 Process Management
Levels 1, 2
11
Levels 1, 2 Level 2
11
10
Levels 1, 2 IBM Systems Director Server, Level 2 IBM Systems Director Server, Levels 0, 1, 2
IBM Systems Level 2 Director Server, Level 2 IBM Systems Director Server, Levels 0, 2
IBM Systems Level 2 Director Server, Level 2 IBM Systems Level 2 Director Server, Levels 0, 1, 2
Remote Control
Levels 0, 1, 212
Remote Command Line
IBM Systems Levels 0, 1, 2 IBM Systems Level 2 Director Director Server, Server, Levels 0, 2 Levels 013, 113, 2 IBM Systems Levels 1, 2 Director Server, Level 2 IBM Systems Director Server
Levels 0, 1, 2 IBM Systems Director Server, Level 2
Resource Monitors
IBM Systems Console only Console only IBM Systems 14 14 Director Director Server, Server, Levels 1, 2 Levels 1, 2 IBM Systems Levels 1, 2 Director Server, Levels 1, 28, 15 IBM Systems Levels 1, 2 Director Server, Levels 0, 1, 217
19
Storage Manager
Levels 1, 2
IBM Systems Director Server, Levels 1, 2 16 IBM Systems Director Server, Levels 0, 1, 2
17
Update Manager
IBM Systems Levels 1, 218 Director Server, Levels 217
Levels 1, 219
Notes: 1. Agentless-managed system support is available for VMware ESX Server 3i only. 2. File systems that are displayed for the guest operating system are limited to file systems within its virtual disk. 3. Inventory data provided can vary among Agentless, Platform-Agent, and Common-Agent managed systems. 4. Hardware-platform-specific data is unavailable for hardware inventory. 5. Software Catalog Signatures not supported
58
6. Unless otherwise indicated, this task is supported (although the support might be limited) by: v Out-of-band notifications generated by the service processor v CIM indications generated by Platform Agent or Common Agent 7. IBM BladeCenter JS21 and JS22 only: Out-of-band notifications generated by a service processor only. 8. Not supported on System z systems. 9. Limited 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 Server 3i (Embedded and Installable Editions) although enhanced Agentless support includes Problems support. v Support is limited for guest operating systems. v Support for console is limited to out-of-band notifications generated by a service processor or in-band events generated by CIM (CIM support is system-specific). 11. 12. 13. 14. 15. Supported on guest operating systems only. Supported on Windows guest operating systems only. Supported for Linux on Power Systems only. Limited support provided by virtualization manager. 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, if you want to install the 6.1.x Platform Agent, you must first uninstall 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 RSA in-band. You can manage it out-of-band by connecting it to the network and discovering it with IBM Systems Director.
Chapter 2. Planning
59
Related concepts Supported updates
IBM Systems Director task support not affected by operating systems

Support for the tasks listed in this section does not depend on the operating system running on the system. Event Automation Plans, Discovery, Security, Scheduler, and Resource Explorer are features of IBM Systems Director and their support does not depend on any resource other than the management server. For information about tasks whose support is affected by the operating system, the degree of agent support, or both, see IBM Systems Director support by operating systems and agents. The following tasks have specific support statements: Configuration Manager This task does not require Common Agent or Platform Agent to function. These tasks are a function of IBM Systems Director Server. You can use this task on IBM BladeCenter, System x, and IBM Power systems. The operating system running on the system does not affect the support of this task. Configuration Manager performs IP configuration using out-of-band communication. Power On/Off Support for this task can be provided by the service processor installed in the system, the Wake on LAN feature, or the operating system. The support varies by hardware platform. For detailed support information, see the following topics: v Managing power state settings on IBM Power systems SNMP Browser This task is supported on any system or device that runs SNMP.
IBM Systems Director task support for BladeCenter products

IBM Systems Director tasks provide support for BladeCenter products. The support can vary depending on whether it is for the BladeCenter chassis, network devices, and blade servers. A BladeCenter unit consists of a chassis, one or two management modules, one or more network devices (previously called switches, up to a total of four), and one or more blade servers (up to a total of 14, depending on the model). The chassis is the physical enclosure that contains the blade servers. The chassis has one or two management modules that contain a service processor. IBM Systems Director discovers the chassis and gathers information from the chassis by way of the management module. You cannot install Common Agent or Platform Agent on the chassis. The network device is an SNMP device, and IBM Systems Director considers the network device to be a managed device. IBM Systems Director can gather some information from a blade server before Common Agent or Platform Agent is installed on the blade server. The information is gathered from the blade server by way of the chassis management module. In the IBM Systems Director Web interface, the blade server is represented by a
60
physical platform managed object. However, after you install Common Agent or Platform Agent on the blade server, it is a managed system, and the features and functions that you can use on the blade server are comparable to those that you can use on any managed system. IBM Systems Director tasks that you can use on your BladeCenter unit can vary, depending on the features and options that you have installed. See the following table for a list of IBM Systems Director tasks and information about whether you can use a task on the chassis, network device, or a blade server without Common Agent or Platform Agent installed. Unless otherwise noted in this documentation, a task behaves the same for blade servers as for any managed system. Note: When Common Agent or Platform Agent is installed on a blade server, the supported tasks depend on the operating system that is installed on the blade server.
Table 26. IBM Systems Director task support for BladeCenter products Tasks and subtasks Configuration Manager Event Automation Plans Problems Inventory Power On/Off Remote Command Line Remote Monitors SNMP Browser Chassis Yes Yes Yes Yes No Not applicable No Yes Network device Yes Yes No Yes No Yes Yes Yes Blade server without Common Agent or Platform Agent installed Not applicable Yes Yes Yes Yes No No Yes
2 1
1. Inventory of the chassis, network device, and blade servers can be obtained through the management module. Blade server inventory that is collected through the management module is a subset of the total inventory that is available if Common Agent or Platform Agent is installed on the blade server. 2. To use the SNMP Browser task, the operating-system SNMP agent must be installed on the blade server.
IBM Systems Director task support for Storage products

IBM Systems Director provides limited task support for Storage products.
Supported tasks and features for third-party x86-based systems

This section lists the IBM Systems Director tasks and features that are supported on x86 systems other than IBM hardware. Support can vary depending on whether the system uses Common Agent or no agent. Notes: 1. IBM Systems Director Platform Agent is not supported on third-party x86-based systems. 2. If a task or feature appears to work on some third-party x86-based systems, but the task or feature is not listed as supported, do not assume that the task or feature is supported. 3. All of these tasks and features are supported on IBM x86-based systems that are Common Agent managed systems.
Chapter 2. Planning
61
Table 27. Supported tasks and features for third-party x86-based systems Third-party x86-based systems Task or feature Discovery (basic) Discovery (advanced) Request access Collect and view inventory View system properties Dynamic groups View problems and events Event Automation Plans Event filters Generate events indicating online and offline state Health summary Common monitors (a subset of monitors) Thresholds Common Agent installation (manual) Common Agent installation (remote) Agentless support Yes Yes Yes Yes Yes Yes Yes No Yes No No No No Yes No
2 1
Common Agent support Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Not applicable Not applicable Not applicable
3 2 2 1
RPM installation (remote) for No Linux on x86 systems only 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 Director

IBM 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 Portuguese v Chinese (simplified) v Chinese (traditional) v English v French v German v Italian v Japanese v Korean v Spanish Notes: 1. The graphical user interface is translated in all of the listed languages. 2. Some or all of the help system might not be translated in some languages.
62
3. The most recent information might not be available in the translated versions of the documentation. For the latest information, see the English version of the information center. To do so, in your Web browser set your language preference to English. Then, open or refresh the IBM Systems Director information center. 4. If a discrepancy exists between the translated and the English versions of the documentation, the English-language version is assumed to have the correct content. 5. If you are viewing IBM Systems Director in a language other than those listed here, you may see a combination of that language and English.
IBM Systems Director Pre-Installation Utility

The IBM Systems Director Pre-Installation Utility scans the local system to identify potential problems that could prevent IBM Systems Director from installing successfully. The utility does not scan for device driver or firmware requirements. The IBM Systems Director Pre-Installation Utility is available on the IBM Systems Director installation media. Some of the checks performed by the IBM Systems Director Pre-Installation Utility include: v v v v Runtime authentication OS compatibility Host architecture Processors
v Disk space available v Memory available v v v v v v v v v v v v Software required Port availability Promotion validity Migration information Performance information Username check RSA check Paging size check File limit check (AIX only) SELinux check (Linux only) Intelligent Platform Management Interface (IPMI) Check (Linux only) Locale check (Linux only)
v Short name (8.3 names) check (Windows only) The IBM Systems Director Pre-Installation Utility generates reports and displays the results in the command window or the default browser. Refer to the readme.txt file on the installation media for more information about runtime options, the reports that are generated, and return codes.
Running the IBM Systems Director Pre-Installation Utility on AIX and Linux
Use these instructions to run the IBM Systems Director Pre-Installation Utility on AIX or Linux.
Chapter 2. Planning
63
To start the IBM Systems Director Pre-Installation Utility from the installation media, 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 mount point of the drive. 3. To change to the directory in which the installation script is located, type the following 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 information about checkds.sh options, the reports that are generated, and return codes.
IPv6 compliance
IBM Systems Director version 6.2 is IPv6 compliant. Starting with version 6.2, IBM Systems Director is compliant with Internet Protocol version 6 (IPv6). As an IPv6-compliant application, IBM Systems Director supports the ability to discover and manage resources using both IPv4- and IPv6-address formats. IBM Systems Director is a software application, so it does not implement any portion of the IP stack. In a situation where an IP address selection or specification is required, it is handled in a protocol-neutral way if possible. IBM Systems Director utilizes the underlying operating system on which it runs or the host 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. The following matrix shows interoperability between IBM Systems Director Server and managed resources. It shows that a host configured for IPv4 only cannot communicate with a host configured for IPv6 only, and a host configured for IPv6 cannot communicate with a host configured for IPv4 only.
Table 28. Interoperability between IBM Systems Director Server and managed resources IBM Systems Director Server IPv4 only IPv6 only IPv4 and IPv6 (dual stack) Resource configured for IPv4 Yes No Yes Resource configured for IPv6 No Yes Yes Resource configured for IPv4 and IPv6 (dual stack) Yes Yes Yes
Interoperability with hosts that are outside of the local subnet requires either an IPv6-enabled router to pass IPv6 packets, or the use of Simple Internet Transition (SIT) technology. Available transition technologies include:
64
v Dual-stack IP implementations for hosts and routers that must interoperate between IPv4 and IPv6. v Imbedded IPv4 addresses in IPv6 addresses. IPv6 hosts will be assigned addresses that are interoperable with IPv4, and IPv4 host addresses will be mapped to IPv6. v IPv6-over-IPv4 tunneling mechanisms for carrying IPv6 packets across IPv4 router networks. The following IPv6 restrictions and prerequisites must be taken into consideration for the listed IBM Systems Director functional areas:
Table 29. IPv6 restrictions and prerequisites for specific IBM Systems Director functional areas Function Discovery manager Restriction or Prerequisite Discovery supports using IPv6 to discover resources. For specific IPv6 restrictions, see IPv6 restrictions for discovery. For general information about using IP addresses with discovery, see IP addresses. For update manager to check for updates, the IBM Systems Director Server must have IPv4 Internet access. This access can be obtained through a direct connection or an HTTP proxy. If an IPv4 connection is unavailable, update manager cannot automatically download updates. However, you can still manually download and import updates using www.ibm.com/support/fixcentral/. For more information, see Downloading IBM Systems Director updates without an Internet connection. Integrated Management Module (IMM) 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 IPv6 support for managing System xservers out-of-band using IMM is not available. IBM Systems Director version 6.2 provides IPv6 support for Hardware Management Console Version V7 R7.1.0 SP2 or later. To properly configure your HMC system for IPv6 to ensure that it can be discovered, see http://www.ibm.com/developerworks/ wikis/display/WikiPtype/IPv6+ %28Power+Systems%29.
Update manager
Integrated Virtualization Manager (IVM) and IBM Systems Director version 6.2 provides Virtual I/O Server (VIOS) IPv6 support for Virtual I/O Server 2.1.3.0-FP23 and later. To properly configure your IVM or VIOS system for IPv6 to ensure that it can be discovered, 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 functional areas (continued) Function AIX Restriction or Prerequisite Managing AIX with IPv6 requires AIX 6.1 TL05 SP01 or later. To properly configure your AIX system for IPv6 to ensure that it can be discovered, see http://www.ibm.com/developerworks/ wikis/display/WikiPtype/IPv6+ %28Power+Systems%29. BladeCenter and System x Management IPv6 support for managing servers using BladeCenter requires Advance Management Module (AMM) Firmware v3.54 (BPET54B). In an IPv6 environment, Storage manager supports discovery, inventory, health status, alerts, configuration, topology, and element manager launch on storage devices. However, some storage devices are not supported in an IPV6 environment due to limitations. For more information, see Supported storage devices on page 28. v Changing the host name, or the IPv4 or IPv6 address, on Windows 2003 or Windows 2008 automatically reboots the host agent so that all services are updated with the new IP address. You must remove the discovered agent and rediscover the agent with the new IP address. v You cannot retrieve the IPv6 gateway nor the IPv6 prefix length on Windows Server 2003. v DHCPv6 is not supported on Windows Server 2003. Common Agent or Platform Agent v Host operating system management with IPv6 using Common Agent or Platform Agent requires IBM Systems Director version 6.2 or later of the agent. v Changing the IPv4 and IPv6 addresses through IBM Systems Director Server automatically reboots the host agent so that all the services are updated with the new IP address. You must remove the discovered agent and rediscover the agent with the new IP address. Ensure that the host machine is rebooted if the IP address changes. v Platform Agent 6.1.x on Linux on System x and Windows does not support deletion of the configured interface. You can only add or modify an IPv6 address.
Storage Management
Windows
66
Table 29. IPv6 restrictions and prerequisites for specific IBM Systems Director functional areas (continued) Function Network Management Restriction or Prerequisite For IBM System Director to work properly, an IPv6 Domain Name System (DNS) must be configured. Network management functions support IPv6 when the network devices are fully IPv6-compliant. Some network devices might not be fully compliant. Refer to the Supported network devices on page 22 topic for details. Ping and traceroute diagnostic functions do not support IPv6. SNMP SNMP supports the use of IPv6 starting with Windows Vista. However, SNMP supports IPv6 only for networks running Windows Server 2008 and Windows Vista. This is because SNMP requires the updated protocol stack available in these operating systems for its IPv6 support. Unless your network is solely a Windows Server 2008 network, IPv6 communications will fail, even if an IPv6 protocol stack is separately installed on those computers that run earlier versions of Windows. For example, SNMP agents that run on Windows Server 2003, or Windows XP, or Windows 2000, respond only to queries that are made to their IPv4 addresses. MAP agent The MAP agent can use IPv6 to communicate with the IBM Systems Director Server. However, the MAP agent must also have an IPv4 interface to communicate with the z/VM System Management API (SMAPI) and the directory manager that runs on z/VM. The IPv4 interface must be accessible to the z/VM SMAPI and directory manager.
Applicability of Platform Agent

When determining Platform Agent applicability, there are several consideration of which 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 (formerly i5/OS, Version 6 Release 1), install V1R3 of the IBM Universal Manageability Enablement for IBM i (5770-UME) LPP. On IBM i 5.4 (formerly i5/OS, Version 5 Release 4), install V1R2 of the IBM Universal Manageability Enablement for IBM i (5770-UME) LPP. v Linux on System z has two Platform Agents. The Platform Agent 5.20.32 is intended for systems that are running Red Hat Enterprise Linux AS, versions 4.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 Linux Advanced Platform, versions 5.1, 5.2, 5.3, 5.4, and 5.5, on SUSE Linux Enterprise Server for IBM System z, versions 10 and 11. v In general, customers with BMC and IMM service processors should update to Platform Agent 6.1.1 or later. v In general, customers with RSA service processors should continue to use IBM Director Core Services version 5.20 (or any update release version of 5.20, such as 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 any update release version of 5.20, such as 5.20.3). 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 and discovering it with IBM Systems Director. Platform Agent versions 6.1.1 and 6.1.2 will block updates on IBM Director Core Services version 5.20 with ServeRAID extensions. Therefore, if you want to install Platform Agent version 6.1.1 or 6.1.2, you must first uninstall 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 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 Core Services version 5.20 nor have the restriction described above. Platform Agent 6.1.1 will block updates on IBM Director Core Services version 5.20 systems with Adaptec (Aristos) extensions if the Adaptec hardware has been configured. Platform Agent 6.1.2 will do the same if the Adaptec hardware has been configured. If the Adaptec hardware has not been configured, Platform Agent 6.1.2 will uninstall the Adaptec (Aristos) extension and the Platform Agent install-upgrade will continue (assuming that there is no other restricted hardware on the system). If the update was blocked and you still want to install Platform Agent 6.1.1 or 6.1.2, you must first uninstall the 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 different server. Note: Platform Agent 6.2 will neither block updates on IBM Director Core Services version 5.20 systems with Adaptec (Aristos) extensions nor have the restriction described above. Platform Agent 6.2 will install-upgrade the Adaptec (Aristos) extension if the extension is currently on the machine or if Platform 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 newer version of the LSI MR provider. This provider will not function properly with older versions of the LSI device drivers. In order to ensure that CIM data and alerts function properly with LSI devices, it is important that the device drivers are at the latest levels for all IBM Systems Director, versions 6.1.1 or later, Platform Agents.
68
v When Platform Agent versions earlier than 6.1.2, with one NIC, are installed and discovered in CA using the IBM Systems Director Upward Integration Module for CA Unicenter, the CA agentview GUI will display erroneous information in the Network interfaces section. The only NIC that is shown will have its name specified as Name Undefined and its status specified as a yellow ! icon instead of a green OK icon. This is a known problem in Platform Agent since prior 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 ServeRAID Manager (SRM) are installed, rebooted, and discovered in CA, using the IBM Systems Director Upward Integration Module for CA Unicenter, not all sensor icons will display in the CA 2D MAP GUI. Only sensor icons for Storage Subsystem, Network Adapter, and Smart Disk will display. The other sensor icons for processor and memory do not display. This is a known problem in IBM Director Core Services 5.20.3, Service Update 1, and has been fixed in later releases.
Determining IBM Systems Director task support

Task support can vary depending on the hardware model, the operating system, and the agent installed on the hardware. To determine whether the hardware in your environment is supported by an IBM Systems Director task, you must review information 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 hardware

To determine task support on IBM hardware you must answer a few questions and review the applicable information.
Table 30. IBM hardware questions Question Is the IBM hardware is supported by IBM Systems Director? Action 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 IBM Systems Director Server on the system? Yes. v Make sure the system meets the requirements to run IBM Systems Director Server. See Hardware requirements for running IBM Systems Director Server. v Make sure IBM Systems Director Server supports the operating system installed on the system. See Operating systems supported by IBM Systems Director. No. Go to the next question.
Chapter 2. Planning
69
Table 30. IBM hardware questions (continued) Question Action
Do you want to install Common Yes. Agent or Platform Agent on the v Make sure the system meets the requirements to run system? Common Agent or Platform Agent. See Hardware requirements for systems running Common Agent or Platform Agent v Make sure the agent supports the operating system installed on the system. See Operating systems supported by IBM Systems Director. No. If you choose to install neither of these agents, IBM Systems Director provides limited management capability for Agentless-managed systems. For more information, see IBM Systems Director task support by operating system and agent levels. Does the operating system and agent (or no agent) installed on the system support the task you want to use? To determine whether the operating system and agent installed on the system permit support for a task, see IBM Systems Director task support by operating system and agent levels and IBM Systems Director task support not affected by operating systems. Notes: 1. Limited task support is provided on Agentless-managed systems. 2. Some tasks are supported only on specific hardware. For example, Storage Manager tasks are supported only on storage devices. For detailed information about task support on specific types of hardware, review the following information: v IBM Systems Director task support for BladeCenter products v IBM Systems Director task support for Storage products
Questions to answer about third-party hardware

To determine task support on third-party (non-IBM) hardware you must answer a few questions and review the applicable information.
Table 31. Third-party hardware questions Question Is the third-party hardware is supported by IBM Systems Director? Action IBM Systems Director provides support for: v Third-party x86-based systems that meet hardware requirements. See Hardware requirements for systems running Common Agent or Platform Agent. Note: You can install only Common Agent on third-party x86-based systems. Platform Agent is not supported. v Third-party storage products. See Supported storage devices.
70
Table 31. Third-party hardware questions (continued) Question Do you want to install IBM Systems Director Server on the system? Action Yes. Stop. IBM Systems Director Server is not licensed for use on third-party hardware. No. Go to the next question. Do you want to install Common Yes. Agent or Platform Agent on the Note: You can install only Common Agent on system? third-party x86-based systems. Platform Agent is not supported.Make sure Common Agent supports the operating system installed on the system. See Operating systems supported by IBM Systems Director. No. If you choose not to install Common Agent, IBM Systems Director provides limited management capability for Agentless-managed systems. Does the operating system and agent (or no agent) installed on the system support the task that you want to use? To determine whether the operating system and agent installed on the system permit support for a task, review the following information: v IBM Systems Director task support by operating system and agent levels v IBM Systems Director task support not affected by operating systems v Supported tasks and features for third-party x86-based systems Note: 1. Limited task support is provided on Agentless-managed systems. 2. Some tasks are supported only on specific hardware. For example, Storage Manager tasks are supported only on storage devices. For detailed information about task support on specific types of hardware, review the following information: v IBM Systems Director task support for BladeCenter products v IBM Systems Director task support for Storage products
Planning to install IBM Systems Director

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

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

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

Begin the planning process by identifying the systems and devices that you want to manage with IBM Systems Director. The type of hardware in the environment might determine how you prepare the physical infrastructure or which features you select when you install IBM Systems Director Server. Your environment might include one or more of the following types of hardware: v Chassis, racks, and remote input/output enclosures, such as IBM BladeCenter units v Systems, including servers, desktop computers, workstations, and mobile computers, such as IBM Power systems, System x servers, and System z servers v Storage devices, such as the IBM System Storage DS4000 family of disk storage devices v SNMP devices and printers v ServeRAID controllers or service processors, such as the Remote Supervisor Adapter II Review the hardware requirements section in the Hardware and software requirements section of the IBM Systems Director documentation. Identify the systems and devices that you will manage with IBM Systems Director. 1. Ensure that all systems and devices are correctly installed and cabled. 2. Record information about those systems and devices in Table 32 on page 73. You can use this information to verify that your managed systems and devices have been discovered, to manually add systems or devices in IBM Systems Director, or to plan managed-resource groups or user roles based on the types or locations of managed systems and devices.
72
Table 32. Hardware identification worksheet for IBM Systems Director System or device type Operating system (if applicable) Physical location Network address
Identifying local and remote subnets

You need to provide local and remote subnet information in order for IBM Systems Director to discover resources. Identify the local and remote subnets in which the systems that you want to manage with IBM Systems Director are located, and record this in Table 33
Table 33. Local and remote subnets worksheet Information to gather for discovery Unicast Addresses for Agentless managed system discovery Values ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___ ___.___.___.___ IP addresses or IP-address ranges for unicast ___.___.___.___ discovery of Agentless managed systems. ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ Directory agent server for Platform Agent discovery Service Location Protocol (SLP) directory agent server for discovery of Platform Agent managed systems.
Chapter 2. Planning
73
Table 33. Local and remote subnets worksheet (continued) Information to gather for discovery SLP scope for Platform Agent discovery Service Location Protocol (SLP) scope for discovery of Platform Agent managed systems. ___.___.___.___ ___.___.___.___ ___.___.___.___ IP addresses or IP-address ranges for unicast ___.___.___.___ discovery of Common Agent managed ___.___.___.___ systems. ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ Unicast Addresses for Common Agent discovery Subnets for Common Agent discovery TCP/IP addresses and subnet masks for broadcast and relay discovery of Common Agent managed systems. ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ / / / / / / / / / / ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ Values
Multicast group for Common Agent discovery Multicast group TCP/IP address and time-to-live value for multicast discovery of Common Agent managed systems. Subnets for discovery of SNMP devices TCP/IP addresses and subnet masks for discovery of simple network management protocol (SNMP) devices.
multicast group: ___.___.___.___ time to live: _______
___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___
/ / / / / / / / / /
___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___ ___.___.___.___
Community names for discovery of SNMP devices Community names for discovery of simple network management protocol (SNMP) devices.
_________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________ _________________________________
74
Table 33. Local and remote subnets worksheet (continued) Information to gather for discovery Values
SLP profiles for discovery of SMI-S storage _________________________________ devices _________________________________ _________________________________ Service Location Protocol (SLP) profiles for _________________________________ discovery of SMI-S devices. _________________________________ _________________________________ _________________________________ _________________________________
Identifying firewalls and blocked ports

Review the firewalls and blocked ports in your installation environment in order to identify potential barriers to IBM Systems Director access, and to plan how to implement IBM Systems Director management without creating security gaps. IBM Systems Director must be able to access all the managed resources in the network, and if you will be using a remote management console, the management console and management server must have access to each other. In addition, some functions of IBM Systems Director might require access to the Internet. Tip: If you have a wide area network (WAN) link, use a T1 line that transmits at a speed of at least 1.5 megabytes per second (MBps) to ensure reliable network performance.
Version compatibility of IBM Systems Director components across releases

IBM Systems Director Server 6.2.x can work with previous 5.20.x or 6.1.x versions of Common Agent or Platform Agent. Important: v The version of IBM Systems Director Server must always be the same as or later than the version of any Common Agent or Platform Agent that is installed on the managed systems. For example, you must install and use IBM Systems Director Server 6.2.1 to manage Common Agent 6.2.1 that is installed on managed systems, or you must install and use IBM Systems Director Server 6.2.1 to 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 of IBM Director Server extensions, IBM Director Console extensions, or IBM Director Agent extensions that are supported by IBM Director version 5.20.x or earlier. Therefore, you must first uninstall those extensions before you install or upgrade an IBM Systems Director component from version 5.20.x to version 6.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 older than the version that is currently installed, you cannot update or migrate to it. You must instead uninstall your current version and then install the older version. See the following table for a complete listing of previous agent versions that are compatible 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: Compatible IBM Systems Director Agent-managed systems Server version 6.2.x Common Agent for AIX 5.20.2 6.1 - 6.1.2 6.2 (includes Platform Agent 6.2, Pegasus CIMserver, and CIM providers) - 6.2.1 6.1.0.3 - 6.1.2 6.2 - 6.2.1 n/a IBM Systems Director Server version 6.1.2.x 5.20.2 6.1 - 6.1.2 IBM Systems Director Server version 6.1.1.x 5.20.2 6.1.0.3 - 6.1.1.x IBM Systems Director Server version 6.1 5.20.2 6.1
Common Agent for VIOS Platform Agent for AIX
6.1.0.3 - 6.1.2 n/a 5.20.3 6.1 - 6.1.2 5.20.3 6.1 - 6.1.2 6.1.2 (5722-UME V1R2)
6.1.0.3 - 6.1.1.x n/a 5.20.3 6.1 - 6.1.1.x 5.20.3 6.1 - 6.1.1.x n/a
6.1.0.3 n/a 5.20.3 6.1 5.20.3 6.1 n/a
Common Agent for 5.20.3 Linux on Power Systems 6.1 - 6.1.2 6.2 - 6.2.1 Platform Agent for 5.20.3 Linux on Power Systems 6.1 - 6.1.2 6.2 - 6.2.1 Common Agent for IBM i IBM Director [Level 2] Agent for IBM i IBM i Platform Agent For System x servers: Compatible IBM Systems Director Agent-managed systems Server version 6.2.x Common Agent for Windows Platform Agent for Windows Common Agent for Linux on System x Platform Agent for Linux on System x For System z servers: Compatible IBM Systems Director Agent-managed systems Server version 6.2.x Common Agent for Linux on System z Platform Agent for Linux on System z IBM z/VM Manageability Access Point Agent for System z 5.20 - 5.20.31 6.1 - 6.1.2 6.2 - 6.2.1 5.20.3 - 5.20.32 6.2.1 6.2.1 5.20 - 5.20.3 6.1 - 6.1.2 6.2 - 6.2.1 5.20 - 5.20.31 6.1 - 6.1.2 6.2 - 6.2.1 5.20 - 5.20.3 6.1 - 6.1.2 6.2 - 6.2.1 5.20 - 5.20.31 6.1 - 6.1.2 6.2 - 6.2.1 6.1.2 (5722-UME V1R2) 6.2 (5770-UME V1R3) 6.2.1 5.20.2 (5722UME V1R2) (5770-UME V1R3)
5.20.2 (5722UME V1R2) (5770-UME V1R3)
5.20.2 (5722UME V1R2)
5.20.2 (5722UME V1R2)
IBM Systems Director Server version 6.1.2.x 5.20 - 5.20.3 6.1 - 6.1.2 5.20 - 5.20.31 6.1.1 - 6.1.2 5.20 - 5.20.3 6.1.1 - 6.1.2 5.20 - 5.20.31 6.1.1 - 6.1.2
IBM Systems Director Server version 6.1.1.x 5.20 - 5.20.3 6.1 - 6.1.1.x 5.20 - 5.20.31 6.1.1 - 6.1.1.x 5.20 - 5.20.3 6.1 - 6.1.1.x 5.20 - 5.20.31 6.1.1 - 6.1.1.x
IBM Systems Director Server version 6.1 5.20 - 5.20.3 6.1 5.20 - 5.20.31
5.20 - 5.20.3 6.1 5.20 - 5.20.31
IBM Systems Director Server version 6.1.2.x 6.1
IBM Systems Director Server version 6.1.1.x 6.1
IBM Systems Director Server version 6.1 6.1
6.1.1 5.20.3
6.1.1 5.20.3
n/a 5.20.3
76
License information
Before deploying this product, ensure that you have the necessary licenses.

The IBM Systems Director program contains Management Server (Manager) components, Agent components, and application programming interfaces (APIs), as further described in the documentation. You are authorized to use Management Server and Agent components only on IBM machines. Notwithstanding the foregoing, the IBM Systems Director program includes a license for up to 20 installations of the Agent component on non-IBM x86 systems. These 20 licenses for non-IBM x86 systems are not transferable and cannot be combined or aggregated. For example, if you buy two IBM machines and install the IBM Systems Director program on only one of them, you are entitled to install the Agent component on only 20 non-IBM x86 systems. If you install the IBM Systems Director program on both IBM machines, your entitlement is limited to managing 20 non-IBM x86 systems. To install additional Agent components on non-IBM x86 systems, you must obtain additional Agent component licenses from IBM.
Authorization for IBM Systems Director for IBM Power Systems

Processor is a unit of measure by which the IBM Systems Director for IBM Power Systems program can be licensed. Processor (commonly called a processor core or CPU) is a functional unit within a computing device that interprets and executes instructions. A processor consists of at least an instruction control unit and one or more arithmetic or logic unit. With multi-core technology, each core is considered a processor. Authorization for the IBM Systems Director for IBM Power Systems program is based on the total number of activated processors (including any temporary processors) on the machines running the IBM Systems Director for IBM Power Systems program and the total number of activated processors (including any temporary processors) on the machines being managed by the IBM Systems Director 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 servers program can be licensed. A Server is a physical computer that is comprised of processing units, memory, and input/output capabilities and that executes requested procedures, commands, or applications for one or more users or client devices. Where racks, blade enclosures, or other similar equipment is being employed, 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 charging metric. An authorization is required for each server running the IBM Systems Director for IBM x86 servers program and for each server being managed by the IBM 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 on System z program can be licensed. Processor (commonly called a processor core, CPU, or engine) is a functional unit within a computing device that interprets and executes instructions. A processor consists of at least an instruction control unit and one or more arithmetic or logic unit. With multicore technology each core is considered a processor. Authorizations for the IBM Systems Director for Linux on System z program must be acquired for all activated processors available for use for the server. In addition to the authorization required for the IBM Systems Director for Linux on System z program directly, you must obtain authorizations for this program sufficient to cover the processor cores managed by the program. For IBM System z machines, the authorization required for the IBM Systems Director for Linux on System 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, you must acquire an authorization for each activated engine with the IFL feature on that machine. 2. When the IBM Systems Director for Linux on System z program is installed on or managing general purpose engines, you must acquire an authorization for each activated general purpose engine on that machine.
Terms applicable to API use

The IBM Systems Director program includes APIs called Representational State Transfer (REST) APIs and Advanced External Application Launch (AEAL) function. The IBM Systems Director REST APIs and AEAL function are described in the documentation, available through the IBM Systems Director Information Center. You may develop applications using the Program's REST APIs and/or AEAL function solely for testing and deployment within your Enterprise and only in connection 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. You may not rent, lease, loan, sell or otherwise distribute applications or derivative works created using the IBM Systems Director REST APIs and/or AEAL function to third party end users external to your Enterprise unless you have entered into a written contract with IBM for this purpose.
Warranty
The Specified Operating Environment for the IBM Systems Director program may be located in the Planning section of the IBM Systems Director Information Center. The IBM Systems Director program contains Upward Integration Modules (as described in the documentation) for third party system management products to manage IBM hardware platforms with IBM Director Agent components. There is no warranty or support service available for the Upward Integration Modules when 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 Director program to request software updates, the Management Server component collects information about the release level of certain software products installed on your machine ("Software Information") and electronically sends that Software
78
Information to IBM. Software Information does not include business data such as your financial, statistical and personnel data regarding your business. You agree that IBM (including subcontractors and consultants under contract to IBM) may store and use Software Information for purposes of software maintenance and support, and that such Software Information (including any contact information provided by you) may be transferred to such entities in any country whether or not a member of the European Union. Software Updates Licensee receives are covered by this Agreement. If any additional or different terms apply to any such Software Update, such terms will be 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 to directly use or access the services of IBM DB2 Enterprise Server Edition V 9.7 in any way. The IBM DB2 Enterprise Server Edition V 9.7 program is provided exclusively for use by the Principal Program. You may access IBM DB2 Enterprise Server Edition V 9.7 only to perform administrative functions, such as backup, recovery, and authorized configuration but may not directly use the IBM DB2 Enterprise Server Edition V 9.7 program for any productive use. IBM provides the IBM DB2 Enterprise Server Edition V 9.7 program without obligation of support and "AS IS," WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THE WARRANTY OF TITLE, NON-INFRINGEMENT OR NON-INTERFERENCE AND ANY IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Notwithstanding the foregoing, if you purchase an authorization to the IBM Systems Director Storage Control 4.2.1 (5765-ASM) product, the terms of the "IBM International Program License Agreement", including this License Information, will then apply to your use of the IBM DB2 Enterprise Server Edition V 9.7 program.
Obtaining licenses for Common Agent

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

The 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 already installed on your system. There are various methods that you can employ to install IBM Systems Director 6.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 you were starting from scratch than if you wanted to reuse data from an existing IBM Director 5.20.x or IBM Systems Director 6.1.x installation. Note: The IBM Systems Director installation media for 6.2 is refreshed to include the updates for 6.2.1. When running the installation from the refreshed installation media, you can choose to include the 6.2.1 updates as part of the installation. The updates for 6.2.1 are included in the \update directory on the refreshed installation media. If IBM Systems Director 6.2 is already installed on your system, then you would use update manager, but could import the 6.2.1 updates from the \update directory on the refreshed media. Complete the following steps to determine which method to use to install IBM Systems 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 your environment:
Table 35. IBM Systems Director 6.2 installation methods If your system has... No version of IBM Systems Director or IBM Director (starting from scratch) Follow this method to install IBM Systems Director 6.2.1 Install IBM Systems Director 6.2.1 using standard installation and follow the standard installation path. See Installing IBM Systems Director on the management server for instructions. Install IBM Systems Director 6.2.1 using update manager. See Updating IBM Systems Director for instructions.
IBM Systems Director 6.2, and you want to reuse your data
IBM Systems Director 6.1.x, and you want to Upgrade using standard installation and reuse your data follow the migration path. See Upgrading and migrating to IBM Systems Director 6.2.1 from 6.1.x for the two-step process. IBM Director 5.20.x, and you want to reuse your data Upgrade to IBM Systems Director 6.1.x, then install IBM Systems Director 6.2 using standard installation and follow the migration path. See Upgrading and migrating to IBM Systems Director from IBM Director 5.x for instructions.
Any version of IBM Systems Director or IBM Uninstall the previous version, then install Director, but you do not want to reuse your IBM Systems Director 6.2.1 using standard data installation and follow the standard installation path. See Uninstalling IBM Systems Director and Installing IBM Systems Director on the management server for instructions.
80
Choosing the IBM Systems Director Server installation options

When you install IBM Systems Director Server using a standard installation, you must specify various options for your installation. Determine the IBM Systems Director service account information. You need to provide the following information when you install IBM Systems Director Server: v Computer name v User name v Password
Choosing where to install IBM Systems Director Server

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

Some IBM Systems Director functions require use of an external database, but not all databases support the same functionality with IBM Systems Director. Choose a supported database that meets the needs of your installation. Note: If you install IBM Systems Director Server using the basic installation option, the Apache Derby database is installed. Attention: The Apache Derby database that is installed using the basic installation option is not able to handle a large network of 500 managed objects or more. If you plan to manage a large network from a single IBM Systems Director Server server, either initially or in the future, take this limitation into account in your planning. No option is provided for migrating data to another database management system (DBMS) type. Therefore, if you switch from Apache Derby to another DBMS type in the future, managed data will be lost and will need to be recreated or rediscovered. Tip: If you choose to use a custom remote database, it is important to understand that data is stored and migrated differently on a remote database, and if you plan to use the smsave and smrestore commands to migrate your remote database environment to a new release, you must use additional parameters to ensure that all discovery and inventory data is restored correctly on the remote database. The -dbTargetDir directory option is required when migrating a remote database. You must ensure that the user ID performing the migration has database backup and restore privileges. For more information, see the smsave and smrestore topics. IBM Systems Director Server uses a database to store inventory information in a central location. You can then use this inventory information to manage your assets. Before you install IBM Systems Director Server, decide the database that you want to use. Complete the following steps to determine the appropriate database application for your installation of IBM Systems Director. 1. Review the advantages and disadvantages of the different database installation types.
82
Table 36. Advantages and disadvantages of different DBMS installation types DBMS installation type Embedded DBMS The DBMS is installed on the management server as part of the IBM Systems Director Server installation, and shares the Java Virtual Machine with IBM Systems Director. Local DBMS The DBMS is installed on the management server on which IBM Systems Director Server is installed. Remote DBMS The DBMS is installed on a different server than the management server, and accessed remotely by IBM Systems Director Server. Advantages v Configuration is easy. v No additional license is required. v Resource usage is lower than that of a local DBMS installation. v A separate server for the DBMS is not required. Disadvantages v Apache Derby database limitation: The number of managed objects is limited.
v A separate server for the DBMS is not required.
v Resource usage on the management server is the highest of the DBMS types.
v Resource usage on the management server is the lowest of the DBMS types. v You can use an existing DBMS and avoid purchasing an additional DBMS license.
v A separate server for the DBMS is required. v Connectivity problems with the database server will affect IBM Systems Director. For example, if the database server goes offline or becomes unreachable, IBM Systems Director Server will stop responding and hang.
2. Review the supported databases for your management server and the type of installation that you prefer. Depending on where you are installing IBM Systems Director Server, you have one or more possible choices for your database. See Supported database applications. for further information. 3. Review the information in Table 37 to determine the database that best meets your needs. Some databases (including Apache Derby) cannot handle a large network of 500 managed objects or more.
Table 37. Large network management Database Apache Derby IBM DB2 Microsoft SQL Server Microsoft SQL Server Express Oracle Database
Can handle a large network of managed objects No Yes Yes No Yes
Chapter 2. Planning
83
Choosing the management level for managed systems

IBM Systems Director provides three different levels of management for managed systems and managed objects. For each managed system, you need to choose the management level that provides the management functionality you need for that managed system. Depending on the type of managed system and the management tasks you need to perform, you can choose the best management level for the managed system. IBM Systems Director has three management levels: Agentless Managed systems without any IBM Systems Director software installed. Platform Agent Managed systems with Platform Agent installed. Common Agent Managed systems with Common Agent installed. These three management levels have different requirements and provide differing levels of management functionality in IBM Systems Director. For each managed system, review Table 38 and decide what level of management is required.
Table 38. Management-level selection worksheet4 Criteria Managed system types IBM systems running AIX IBM systems running IBM i IBM systems running Linux IBM systems running Linux and supporting either the SSH 5 or DCOM 6 protocol IBM systems running Windows IBM systems running Windows and supporting either the SSH or DCOM protocol Non-IBM systems running Linux and supporting either the SSH or DCOM protocol Non-IBM systems running Windows and supporting either the SSH or DCOM protocol Other managed resources, including management processors supporting SSH, racks, and SNMP devices Managed system attributes Managed system has a supported workgroup/enterprise management agent installed Minimal additional memory constraint on managed system No additional memory constraint on managed system No Common Agent license required X X X X X X X X X X1 X X X X X X X X
3
Agentless
Platform Agent
Common Agent X2 X X X X X X X
84
Table 38. Management-level selection worksheet4 (continued) Criteria No software required on managed system Needed functionality Asset ID Event automation plans Event log File Transfer Active Status Service and Support Manager (Linux and Windows) virtualization manager (Linux & Windows) Remote control (Windows only)
8 7
Agentless X
Platform Agent
Common Agent
X X X X X X X X X X X X X X X X X X X X X X X
Remote session to all supported managed systems and devices Remote session to SNMP devices and systems supporting SSH Restart the managed system Upgrade to Platform Agent Upgrade to Common Agent
Notes: 1. Agentless management is supported only with SSH, and it is limited agentless support. 2. Common Agent is supported with and without SSH. 3. Platform Agent managed system support is not provided by the Platform Agent but by either the 5722UME or 5770UME product. 4. In this table, "systems" include servers, desktop computers, workstations, and mobile computers. 5. SSH = Secure Shell 6. DCOM = Distributed Component Object Model 7. Event-automation plans can be applied to Agentless managed systems; however, most of the events that can trigger an event-automation plan are not generated for Agentless managed systems. 8. Not supported in version 5.20.2 on Windows Vista.
Planning for virtual environments

To fully enable the management capabilities of IBM Systems Director for your virtual resources, ensure your environment is set up correctly. In most cases, you need to install the required software on the host systems in your environment. The required software varies, depending on the type of resources in your environment. Install the following software on the host systems according to your virtual environment: v Hardware Management Console environment: No agent or subagent software is needed. v Integrated Virtualization Manager environment:
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 with Hyper-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 VirtualCenter running on Windows, it is recommended that you do not install the virtualization manager subagent for VMware ESX Server. v VMware ESXi managed by VMware VirtualCenter environment: 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 a supported version of Linux that is running as a guest on the z/VM 5.4 or 6.1 operating system.
Planning to upgrade or update IBM Systems Director

If you already have IBM Systems Director installed and you want to move to a later version, it is helpful to first understand the various processes that are available. You will either upgrade or update depending on the versions from and to which you are moving. This topic helps you understand the differences between upgrading 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 Systems Director are upgrading and updating. Upgrade You 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 task and data migration is necessary if you want to preserve data from your previous version of IBM Systems Director. You are replacing, as opposed to updating, your current installation.
86
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 information about upgrading agents, see Upgrading or updating the IBM Systems Director agents. Update You 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. Update manager is used for the update task and all data is preserved from your previous version of IBM Systems Director. Note: IBM provides cumulative updates and cumulative defect-only patches 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 install a patch for an update version that is later than the currently installed update version, you also get that new update as a prerequisite for the new patch. For example, if you have version 6.2.0.1 installed and you move to install the version 6.2.1.1 patch, you automatically receive the 6.2.1 update as a prerequisite. Use update manager to install updates and patches on IBM Systems Director. 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 for IBM Systems Director and the process that you use to move to each package.
Table 39. Upgrade and update packages Package Release (for example, IBM Systems Director version 6.2) Characteristics of the package v Includes significant new function. v Requires a separate full product installation. v Is available from the DVD or www.ibm.com/ systems/management/ director/downloads/. v Is reflected in the operating system registry. Note: To determine the version of IBM Systems Director that is currently installed, use the lslpp command (on AIX ) or the rpm command (on Linux), or check the Windows registry. Process used to move to the package Upgrade
Chapter 2. Planning
87
Table 39. Upgrade and update packages (continued) Package Update (for example, IBM Systems Director version 6.2.1) Characteristics of the package v Includes minor updates, new features (such as new hardware support), and fixes. v Is not reflected in the operating system registry. Note: See Determining the installed IBM Systems Director versions for details about how to determine the version of IBM Systems Director that is currently installed. v Is cumulative. For example, if a version 6.2.2 update is made available, it would include features and fixes contained in version 6.2.1, as well as patches published for version 6.2.1. Patch (for example, IBM Systems Director version 6.2.1.1) v Includes fixes for defects at the associated update level only and is installed for a specific update, such as version 6.2.1. v Installed by update manager. v Is not reflected in the operating system registry. Note: See Determining the installed IBM Systems Director versions for details about how to determine the version of IBM Systems Director that is currently installed. v Is cumulative. For example, if a version 6.2.1.2 patch is made available, it would include features and fixes contained in version 6.2.1.1. Update Process used to move to the package Update
Notes: v You can update installed plug-ins such as Active Energy Manager independently in 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 Director Server and agents on AIX , see IBM Systems Director Best Practices Wiki.
88
Related reference IBM Systems Director Best Practices Wiki
Disaster recovery for IBM Systems Director 6.2.x

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

When you backup your IBM Systems Director 6.2.x data, you must restore the backup 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 Power server. v The same version of operating system. For example, you cannot backup data from a server running Red Hat Enterprise Linux 4.0 to a server running Red Hat Enterprise Linux 5.0. However, the service pack or update can vary, for example, you can backup data from a server running Red Hat Enterprise Linux 4.0 (Update 6) to a server running Red Hat Enterprise Linux 4.0 (Update 7). v The same version of the database application. v The same version of IBM Systems Director. For example, you cannot backup data from an IBM Systems Director 6.2.x management server and restore the data to an IBM Director 5.20 management server. Important: If your intention is to migrate your IBM Systems Director 6.2.x installation to a configuration with a different server platform, operating system, or database application, you cannot use the commands provided for simple backup and disaster recovery. For information about migrating an IBM Director 5.20 installation to IBM Systems Director 6.2.x, see Upgrading and migrating IBM Systems Director. For detailed information about the smsave and smrestore commands, see smsave command 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 backup output in a remote location from the management server location. You must determine the backup frequency based on your business need. In some situations, even a day's worth of lost data is too much loss. Important: If you have a remote database, the smsave command produces two data-sets: one at the location of the remote database server and the other on the IBM Systems Director management server system. The data sets are mated sets. You must maintain and restore these data sets together. In a disaster situation, before you restore your IBM Systems Director data, you must first install IBM Systems Director on a new server. Make sure the server
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 can change from the original installation without any effect.
Planning for events

An event is an occurrence of a predefined condition relating to a specific system. There are two types of events: alert and resolution. An alert is the occurrence of a problem relating to a system. A resolution is the occurrence of a correction to a problem relating to a system. Note: In the IBM Systems Director product, there are tasks and features that use the word alert in place of the word event. Also, some tasks use the word notification instead of event. Sources that can generate events include, but are not limited to, the following programs and protocols: v Common Agent v Platform Agent v Microsoft Windows event log v Windows Management Instrumentation (WMI) v SNMP through out-of-band communication v Intelligent Platform Management Interface (IPMI) Platform Event Traps (PET) through out-of-band communication v IBM service processors through out-of-band communication Successful use of event notification depends on careful planning. Consider the following questions: 1. Which events can be monitored on the system? a. Which of these events are useful to my management strategy? b. What configuration is required for the system to send event notifications? 2. How should event notifications be sent to IBM Systems Director? See the IBM Systems Director Events Reference for additional information.
Planning events to be monitored

Before configuring IBM Systems Director and your managed systems, you should plan how events will be sent to IBM Systems Director and how event notifications will be sent to the personnel who need to receive them. v Consider how events will be sent by the managed systems to IBM Systems Director Server. When IBM Systems Director discovers IBM service processors or BladeCenter management modules, it automatically configures them to send events using in-band communication with IBM Systems Director Server. For detailed information about communication with management modules and service processors, see Service processor communication. Notes: For Ethernet connections, configure either a static IP address or enable the use of DHCP.
90
BladeCenter management modules and the Remote Supervisor Adapter and Remote Supervisor Adapter II service processors support DHCP; however, the use of a static IP address is potentially more reliable than using DHCP. A static address means that the failure or inaccessibility of DNS and/or DHCP servers will not prevent access to the management module or service processor. If a BladeCenter management module or Remote Supervisor Adapter II is set to use DHCP but does not receive an address from the DHCP server within two minutes, the management module or adapter automatically sets its address as 192.168.70.125. v Consider how you want event notifications to be sent to the personnel who need to receive them. Using event automation plan, you can configure IBM Systems Director to send notification of particular events or event types using e-mail or mobile phone text message, or by starting an application on the management server or on a managed system. Alternatively, you can configure management modules and some service processors to send event notifications directly to personnel or other management applications besides IBM Systems Director using means such as SNMP traps or e-mail. This kind of event notification is not enabled by default, but can be configured using the BladeCenter Configuration Manager task in IBM Systems Director or through a direct connection to the service processor or management module. These events are broken down into the following three categories: - Critical events, such as Temperature outside critical thresholds or Power supply failure. - Warning events (non-critical), such as Redundant power supply failure or Voltage outside warning thresholds. - System events, such as Power off, Server loader timeout value is exceeded, or Predictive Failure Analysis (PFA) notification. Notes: For SNMP, decide which version of SNMP to use (v1 or v3). Enable traps and the SNMP agent, and configure the IP address. If using SNMPv1, configure the community name. If using SNMPv3, configure the user profile. For e-mail notifications, configure the SMTP server. If you enable timeout events (alerts), you also must plan to enable those timeouts.
Planning for event automation plan implementations

To plan and design an event automation plan, you must determine what the goal of the event automation plan is. Consider which systems you intend to target with the event automation plan. You can target all systems, a subgroup of systems, or a specific system. You can structure event filters and event actions in different ways. This section presents some of the possible structures that you can use. Remember that many event automation plans might include each of the elements of each of the structures that are presented. When designing your event automation plan structure, consider all the systems in groups. Start by designing an event automation plan that contains events that
Chapter 2. Planning
91
apply to the largest number of objects. Then, create event automation plans that cover the next largest group of systems, and continue to group them until you reach the individual managed-object level. When doing this, remember that each system can be a member of multiple groups. When planning an event automation plan structure, consider the following issues: v What do you want to monitor on most or all of the systems of the same type as a whole? This answer determines the grouping and event filters for your event automation plan. v How will you group your systems as smaller groups, according to the additional events you want to monitor? The smaller groups are usually based on the following criteria: Managed-object manufacturer, for vendor-specific events Function of the system, for services and resources specific to that function v What type of systems are you monitoring? v What is the function of the system? v What are the key monitors for the system? v Are there other systems for which you want to use the same monitors?
Managing and monitoring systems with event automation plans

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

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

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

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

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

Before deploying IBM Systems Director, define user roles for your organization and determine the user authentication type that will best meet your needs. 1. Decide what kind of user authentication to use for IBM Systems Director. The user authentication type that you choose (a common Lightweight Directory Access Protocol (LDAP) server, or accounts on the operating system of the management server) affects both the availability and security of IBM Systems Director Server. IBM Systems Director is shipped with LDAP authentication support, but it is not enabled by default. LDAP support includes support for the following LDAP servers: v IBM Tivoli Directory Server v Microsoft Active Directory v OpenLDAP With LDAP authentication, it is easy to implement common roles and access for users across multiple instances of IBM Systems Director Server. However, the
94
LDAP server must be secure in order to avoid unauthorized access to management tasks and managed objects in IBM Systems Director. To help you make a decision, consider how IBM Systems Director will be used to manage systems and objects in various locations. You can start by answering the following questions: v Will a single management server be used for the entire organization, or will multiple management servers be used? v If multiple management servers will be used, will the same user accounts be needed on more than one of the management servers, or should user accounts be unique for each management server? v Is there an existing LDAP directory, such as IBM Tivoli Directory Server or Microsoft Active Directory, for your organization? v How many users will be authorized to access IBM Systems Director? Note: If you choose to use LDAP, ensure that you create smadmin, smmgr, smmon, and smuser groups on the LDAP servers. 2. Decide what kind of user roles to define for IBM Systems Director users. The user roles you define will provide an organizational framework that will guide you when creating user groups, delegating management authority in IBM Systems Director, and creating managed-object groups. User roles can be based on a job description, on the physical or geographic area of responsibility, or on other criteria. A user might have several different user roles simultaneously. Consider the types of access that users must have in IBM Systems Director. Note: The types of access that you grant to users depend on the types of roles that exist within your environment. v If management authority is allocated partially based on the kind of managed object, consider defining user roles for particular operating systems or for storage devices. v If management authority is allocated partially based on organizational roles, consider defining user roles that correspond to sets of privileges and tasks that can be performed in IBM Systems Director, like software distribution, inventory collection, and configuring preferences for IBM Systems Director Server. Depending on the user's organizational role, the user probably needs access to only a subset of the available privileges and tasks. Other criteria can also be used when defining user roles for IBM Systems Director. Whatever criteria are used to define user roles, remember that a user can have multiple roles. Important: Before assigning users an administrator role (such as SMAdministrator) or adding them to an administrator group (such as smadmin), carefully consider whether the user requires this level of authority. Users with this type access can modify or delete all system-level resources and resources for all other users, including operating-system and user files and processes.
Planning Secure Sockets Layer configuration on IBM Systems Director

IBM Systems Director Server provides, by default, a Secure Sockets Layer (SSL) certificate that supports HTTPS connections between IBM Systems Director Server and targets such as storage devices, agents, and Web browsers. However, to ensure server authentication, data privacy, and data integrity, you must replace the default
Chapter 2. Planning
95
certificate with either a self-signed certificate or a certificate that is signed by a certificate authority (CA), and you must change the keystore password. It is not required that you use SSL to secure the network traffic between your management server and targets. However, configuring SSL ensures data integrity and data confidentiality between the management server and its targets. This protection is especially important if you access IBM Systems Director from outside your network. Note: Make sure that the host name you specify in the Common Name field of the SSL certificate matches the host name that you specify in the URL that you use to access the targets. For example, if you specify a long name for the host name in the Common Name field of the certificate, you must specify a long name in the URL. If these host names do not match, you might receive errors when you try to access the targets. Complete the steps in the following procedure to make sure that you specify the correct host name in the Common Name field of the certificate. To replace the default certificate with a new certificate and to change the keystore password for SSL, complete the following steps: 1. If you are replacing the default certificate with a new CA signed certificate: a. Request a CA signed certificate. For information, see Requesting a CA signed certificate. Important: Do not continue with the remaining steps until you are ready to receive the new CA signed certificate. Requests for new CA signed certificates may take several days to process. b. When you are ready to receive the new CA signed certificate, delete the default certificate. For information, see Deleting the default certificate. c. Receive the CA signed certificate. For information, see Receiving a CA signed certificate. d. Update the Web container properties. For information, see Updating the Web container properties. e. Update the targets with the new certificate. For information, see Updating the 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 certificate

You can request a digital certificate from a certificate authority (CA). Because certificate authorities are public entities that issue certificates to identify other entities, CA signed certificates provide a level of public trust. Therefore, this type of certificate is better suited for your production environment. Important: If you are creating a self-signed certificate, do not perform this procedure.
96
You must create a certificate-signing request (CSR) to request a digital certificate from a CA. To create a certificate-signing request, complete the following steps: 1. In the IBM Key Management program, click Create > New Certificate Request. 2. In the Create New Key and Certificate Request window, in the Key Label field, type a label for the new certificate, for example, DirServer. 3. In the Key Size field, accept the default value. 4. In the Common Name field, specify the fully-qualified host name of the server for which you are creating the certificate. Note: This host name must match the host name that appears in the URL you specify in your Web browser to reach IBM Systems Director Server. In most cases, you must specify the fully-qualified host name. However, if you use a short name in your URL, you must specify a short name for the Common Name. 5. In the Organization field, type the name of your organization. 6. In the Country or region list, accept the default value. 7. In the Enter the name of a file in which to store the certificate request field, type a file name or click Browse to select a file in which to store the certificate request, for example, DirServerSecPubCertreq.arm. 8. Click OK. 9. Send the certificate-signing request file to the CA. See the CA Web site for specific instructions about requesting a new certificate. You can request either a test certificate or a production certificate from the CA. However, in a production environment, you must request a production certificate. Next, you must delete the default certificate once you are ready to receive the CA signed certificate. For information, see Deleting the default certificate. and Receiving a CA signed certificate.
Deleting the default certificate

IBM Systems Director Server provides, by default, a Secure Sockets Layer (SSL) certificate that supports HTTPS connections between IBM Systems Director Server and targets such as storage devices, agents, and Web browsers. You must delete this default certificate before you can replace it with either a self-signed certificate or a CA signed certificate. Also, you must change the keystore password. If you requested a CA signed certificate, ensure you the CA signed certificate is ready to be received before deleting the default certificate. Back up any files before you edit them. To delete the default certificate, complete the following steps: 1. Stop IBM Systems Director Server by completing the applicable steps:
Option For Linux Description Type the following command: smstop
Chapter 2. Planning
97
Option For Windows
Description 1. Right-click My Computer and select Manage. 2. In the Computer Management window, expand Services and Applications > Services. 3. In the Services pane, right-click IBM Director Server and select Stop. 4. Exit from the Computer Management window.
2. Start the IBM Key Management program by typing the applicable command.
Option For Linux For Windows Description install_root/jre/bin/ikeyman install_root\jre\bin\ikeyman.exe
where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). 3. To open the default keystore file, click Key Database File > Open. 4. In the Key database type list, select JKS. 5. Click Browse and navigate to the applicable default keystore file:
Option For Linux For Windows Description install_root/lwi/security/keystore/ ibmjsse2.jks install_root\lwi\security\keystore\ ibmjsse2.jks
where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). 6. Select the default keystore file and click Open; then, click OK. 7. In the Password Prompt window, specify the default password for the default keystore file and click OK. The default keystore file password for IBM Systems Director is ibmpassw0rd. 8. In the Key database content pane, select the default personal certificate named lwiks and click Delete. If you want to create a self-signed certificate, go to Creating a self-signed certificate. If you requested a CA signed certificate, see Receiving a CA signed certificate.
Receiving a CA signed certificate

After the certificate authority (CA) accepts the certificate-signing request, the CA processes the request and verifies your identity. The CA sends the signed certificate back to you by way of e-mail. You must receive and save the new certificate in the default keystore file. Before you complete this procedure, you must perform the following:
98
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 default certificate. 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 your certificate has a different file extension, see the IKeyMan User's Guide. Go to the IBM Support and Download Web site at www.ibm.com/support/us and search using the document number SC23-6510-00. If you are importing a certificate with a file extension of .pfx and errors indicate that the certificate store is corrupt, see Resolving the iKeyman Corrupted Database Message. Go to the IBM Support and Download Web site at www.ibm.com/support/us and search using the reference number PRS2855. Important: If you are creating a self-signed certificate, do not perform this procedure. To receive a CA signed certificate, complete the following steps: 1. If the CA sends the new certificate to you as part of an e-mail message, you must cut and paste the certificate from the e-mail message and save it in a certificate file, for example, DirServerSecPubCert.arm. Note: The e-mail message from the CA might include supplemental text in front of the certificate and after the certificate. For example, you might see the text BEGIN CERTIFICATE in front of the certificate and END CERTIFICATE after the certificate. In this case, make sure that you cut and paste the supplemental text along with the certificate text. 2. Save the certificate file in the applicable directory:
Option For Linux For Windows Description install_root/lwi/security/keystore install_root\lwi\security\keystore
where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). 3. Start the IBM Key Management program by typing the applicable command.
Option For Linux For Windows Description install_root/jre/bin/ikeyman install_root\jre\bin\ikeyman.exe
where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). 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 For Linux For Windows Description install_root/lwi/security/keystore/ ibmjsse2.jks install_root\lwi\security\keystore\ ibmjsse2.jks
7. 8.
9. 10. 11. 12.
13.
where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). Select the default keystore file and click Open; then, click OK. In the Password Prompt window, specify the default password for the default keystore file and click OK. The default keystore file password for IBM Systems Director is ibmpassw0rd. In the Key database content pane, select Personal Certificates from the list. Click Receive. In the Receive Certificate from a File window, in the Data type list, select Base64-encoded ASCII data. 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. In the Location field, specify the applicable directory path:
Description install_root/lwi/security/keystore install_root\lwi\security\keystore
Option For Linux For Windows
14. 15. 16. 17.
18.
where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). Click OK. In the Enter a Label window, specify a label for the certificate, for example, DirServerSec. Click OK. Optional: Add the public version of the CA signed certificate to the truststore file of targets. The public version of the certificate contains all identifying information as well as the public key associated with the certificate. This optional step can provide additional security within your SSL configuration. Each target can determine whether the server presents a certificate that is signed by a trusted signer. If the target determines that the certificate is not signed by a trusted signer, it displays a warning which alerts you to a possible security breach. Configuring SSL for targets is specific to each target. See the documentation for the chosen target for instructions. To change the default keystore file password, click Key Database File > Change Password.
19. In the Change Password window, specify and confirm a new password and click OK. 20. To exit the IBM Key Management program, click Key Database File > Exit.
100
Next, you must update the Web container properties. Go to Updating the Web container properties.
Creating a self-signed certificate

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

Because you changed the keystore password, you must update the Web container properties with the new keystore password.
Chapter 2. Planning
101
Before you perform this procedure, you must create a new certificate. You can create either a self-signed certificate or request and receive a CA-signed certificate: v To create a self-signed certificate, see Creating a self-signed certificate. v To request and receive a CA signed certificate, see Requesting a CA signed certificate and Receiving a CA signed certificate. Ensure that you back up any files before you edit them. To update the Web container properties, you do not edit properties directly within the webcontainer.properties file. Instead, you must create a file named sslconfig in the same directory, edit the properties in the sslconfig file, and restart IBM Systems Director Server. The process of restarting IBM Systems Director Server encrypts the new password in the Web container properties. Note: Messages and settings might differ depending on what type of target to which you are connecting and the version of Java Web Start that you are running. To update the Web container properties, complete the following steps: 1. Change to the applicable directory:
Option For Linux For Windows Description install_root/lwi/conf install_root\lwi\conf
where install_root is the root directory of your IBM Systems Director installation. Note that this path uses the backslash (\) to delimit the directory; depending on the system that you are using, you might be required to enter the path using the forward slash (/). 2. Change the name of the webcontainer.properties file to webcontainer.properties.bak. 3. In the same directory, create a file named sslconfig and copy the contents of webcontainer.properties.bak to the sslconfig file. 4. Using a text editor, edit the sslconfig file. Notes: a. Specify only plain text values for the passwords in the sslconfig file. b. 5. Specify com.ibm.ssl.keyStorePassword.secure_port=new_password Where v secure_port is the secure port that IBM Systems Director Server uses. Use the secure port value indicated in your properties file. v new_password is the password that you set in one of the following steps: Step 11 on page 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
Option For Linux For Windows
Description Type the following command: smstart 1. Right-click My Computer and select Manage. 2. In the Computer Management window, expand Services and Applications > Services. 3. In the Services pane, right-click IBM Director Server and select Start. 4. Exit from the Computer Management window.
When you restart IBM Systems Director Server, the sslconfig file is used to automatically create a new webcontainer.properties file and encrypt the new password in this file. After the new webcontainer.properties file has been created, IBM Systems Director Server deletes the sslconfig file because it is no longer needed. 10. After you start and connect to IBM Systems Director Server, you can delete the webcontainer.properties.bak file manually. Next, you must update the target with the new certificate. Go to Updating the target with the new certificate.
Updating the target with the new certificate

You must update the target with the new certificate. Before you perform this procedure, you must update the Web container properties. For information see Updating the Web container properties. To update the target with the new certificate, complete the following steps. Note: If you performed step 17 on page 100 in Receiving a CA signed certificate or if the public version of the CA signed certificate is already stored in the browser truststore file, go to step 11 on page 104. Some targets contain the public version of well known CA signed certificates. 1. In a Web browser, type the following URL to point to IBM Systems Director Server: http://server_name:port_number/ibm/console, where server_name is the host name of IBM Systems Director Server and port_number is the port for IBM Systems Director Server. The default port is 8421.
Option For Microsoft Internet Explorer Description A Security Alert window is displayed, for example, you might see the following message: The security certificate was issued by a company you have not chosen to trust. View the certificate to determine whether you want to trust the certifying authority. Continue to step 2 on page 104. A Website Certified by an Unknown Authority window is displayed. Click Accept this certificate permanently and then click OK. You Web browser is updated with the new certificate.
For Firefox
Chapter 2. Planning
103
In the Security Alert window, click View Certificate. In the Certificate window, click Install Certificate. In the Certificate Import Wizard, on the Welcome page, click Next. On the Certificate Store page, select the way that you want to store the certificate and click Next. 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. 2. 3. 4. 5. 9. In the Certificate window, click OK. 10. In the Security Alert window, click Yes. 11. When you use a launched task in the IBM Systems Director Web interface, the following message is displayed: The application's digital signature has been verified. Do you want to run the application? Be sure to select Always trust content from this publisher and click Yes.
Planning password management in IBM Systems Director

Before deploying IBM Systems Director, plan how you will manage passwords in your environment. You are required to supply many different credentials when installing and configuring IBM Systems Director. If you ever modify the user ID or password of a credential after specifying it during IBM Systems Director installation and configuration, you must ensure that any related tasks or other credentials are properly updated to accommodate the change. For example, if you update the administrator password in IBM DB2, you must ensure that you also update references to that password in IBM Systems Director so that you can still use the application. The following table lists the primary credentials that are required for IBM Systems Director installation and configuration along with the tasks that require each credential. The last column contains information about changing each password in IBM Systems Director after it is initially set. Use the table to determine links between the credentials and tasks that might warrant further updates if you change any one credential to help prevent any problems that you might encounter while running IBM Systems Director. Note: This topic does not apply to credentials that you set up and use for discovery, such as for requesting access, because you use the IBM Systems Director Web interface to manage those.
Table 40. Installation and configuration user IDs and passwords Credential type IBM Systems Director administrator using the local operating system registry Tasks that require the Your values credential User ID: Password: v Determining IBM Systems Director service account information v Installing IBM Systems Director Server v Logging on to IBM Systems Director Server Procedure to change the password in IBM Systems Director Use the appropriate tools supplied by the local operating system.
104
Table 40. Installation and configuration user IDs and passwords (continued) Credential type IBM Systems Director administrator using an LDAP registry Tasks that require the Your values credential User ID: Password: v Determining IBM Systems Director service account information v Installing IBM Systems Director Server v Logging on to IBM Systems Director Server Database system administrator Database runtime database connection administrator (DbmsUserId, DbmsPassword) User ID: Password: User ID: Password: Preparing the database for use with IBM Systems Director Preparing the database for use with IBM Systems Director Use the appropriate tools supplied by the database application. Use a tool that can handle the password encryption to change the value in the dcm.xml properties file and also update the database.properties value used by LWI. Procedure to change the password in IBM Systems Director Use the appropriate tools supplied by LDAP.
Agent manager resource User ID: manager Password: LDAP administrator User ID: Password:
Use the cimsubscribe command. Starting IBM Systems Director Server (configAgtMgr.sh script) Setting up IBM Systems Director to use LDAP for user authentication Use the procedure in Authenticating IBM Systems Director users stored in LDAP to modify the com.ibm.lwi.LDAPAdminPassword password value in the security.properties file.
Chapter 2. Planning
105
106
Chapter 3. Installing IBM Systems Director on the management server

Prepare your systems and install IBM Systems Director Server on the management server. Note: After you install IBM Systems Director, update it to the latest version to ensure 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 the 6.2.1 agents. Obtain the 6.2.1 agents from the IBM Systems Director Downloads website. Related reference IBM Systems Director Downloads
Preparing the management server

Before installing IBM Systems Director Server, make sure that the requirements that are applicable to your system have been met. Run the IBM Systems Director Pre-Installation Environment Checker to help validate that the requirements that are applicable to your system have been met. See IBM Systems Director Pre-Installation Environment Checker .
Preparing the database application

Unless you want to use the default embedded database for your system, you must prepare the database application for use with IBM Systems Director and configure them to work together. Ensure that you have chosen the supported database application that you will use with IBM Systems Director. See Choosing the IBM Systems Director database application for information that will help you decide the database application to use. The effort required to prepare the database depends on the database application that you choose. Preparation might include one or more of the following tasks: v Downloading and installing the applicable database administrator client v Downloading and installing the applicable Java Database Connectivity (JDBC) drivers v Creating a database or server ID v Configuring and starting a TCP/IP listener v Setting the authentication mode. To use a database other than your system's default database with IBM Systems Director, follow the steps in the appropriate topic to prepare your database application. If you are upgrading and migrating to IBM Systems Director 6.2, also ensure that you follow the preparation instructions in Preparation considerations for upgrading and migrating to IBM Systems Director.
107
Note: You can install IBM Systems Director before preparing the database, but you will only be able to use the default Apache Derby database until you configure IBM Systems Director Server to use a different database. Tip: If you choose to use a custom remote database, it is important to understand that data is stored and migrated differently on a remote database, and if you plan to use the smsave and smrestore commands to migrate your remote database environment to a new release, you must use additional parameters to ensure that all 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 correct authority. For more information, see the smsave and smrestore topics listed below. After the database application is prepared, you can install IBM Systems Director Server and configure it to connect to the database.
Preparing IBM DB2

If you choose to use IBM DB2 as the database application for IBM Systems Director, there are some tasks that you need to complete to prepare your system before you install IBM Systems Director Server. Follow the steps for your operating system to prepare IBM DB2 for use with IBM Systems Director. Preparing IBM DB2 on AIX or Linux: If you choose to use IBM DB2 as the database application for IBM Systems Director, there are some tasks that you need to complete to prepare your AIX or Linux system before you install IBM Systems Director Server. The tasks that you need to complete are grouped into two categories: tasks for the IBM DB2 server, and tasks for the IBM Systems Director server. The IBM Systems Director server and IBM DB2 server can reside on two different systems or on the same system. The tasks are the same and applicable to both scenarios. When only one system is used, you must run all the tasks on that system. From the perspective of the IBM Systems Director server, the database connection is always remote 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 on AIX, 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 install IBM 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 topic for supported versions and installation options. 2. Create an IBM DB2 server instance with TCP/IP support.
108
Note: Use the graphical installer (db2setup) to install IBM DB2. This method provides an easy way to create the first server instance, the IBM DB2 administrative instance, and all the required users and groups. If you use the text 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 and administrative instance. 3. (Optional) Complete the following steps to set DB2_WORKLOAD to TPM on the newly-created IBM DB2 server instance. TPM is a predefined setting that turns on DB2_SKIPINSERTED, DB2_SKIPDELETED, and DB2_EVALUNCOMMITTED. Setting DB2_WORKLOAD to TPM improves concurrency through instance level configuration settings. 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 command to 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 unique system user ID and password that IBM Systems Director Server will use to connect to this instance. Remember these values as you will need to enter them on an installation panel or in the cfgdbcmd.rsp configuration file after the IBM Systems Director installation. Do not use the database administrator ID or any default database user ID or password. Notes: v Do not specify the same user ID in the cfgdbcmd.rsp configuration file as is specified in the -dbAdmin parameter to cfgdbcmd. Doing so might result in an error or in having the user's administrator authority revoked. If you mistakenly used this configuration in the past, you might need to grant administrator authority again to this user ID after the cfgdbcmd command runs. v If you plan to use smsave or smrestore with IBM Systems Director Server and the database, you must: a. Enable password file authentication for the database system administrator user ID that is used for backup/restore. b. Ensure that the database instance owner is in the same primary group as the IBM Systems Director user who will perform the backup and restore operations. This will enable the database server to read and write the database backup image to the backup directory. c. If you chose to create the IBM DB2 database yourself, verify how you configured the rollforward option. If this option is set to require user approval, running smrestore will cause errors. Correct this issue now to avoid potential problems later with restoring data. See smrestore fails when IBM DB2 is configured to require approval of restore operation for more information. v When you create the runtime user account on the database server, the user must change password at next logon option is selected by default. Ensure
109
that you either deselect this option or change the password before configuring IBM Systems Director. You must do this because the user is actually not given the opportunity to change the password and, when they run the cfgdbcmd command, the database configuration will fail. IBM Systems Director does not save the database server administrator account user ID and password. Tasks for the IBM Systems Director server: To prepare the IBM Systems Director server, complete the following tasks before you 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 the same system, it is possible to use the same IBM DB2 installation for the IBM DB2 server instance and the IBM DB2 client instance, in which case it is not necessary to install the IBM DB2 Data Server Client separately. However, installing a separate IBM DB2 Data Server Client ensures that you can move the IBM DB2 server instance to a remote system without affecting the current IBM Systems Director setup, and that you can apply IBM DB2 patches to the server or client instance independently. 2. (Optional) Create an IBM DB2 client instance. If not done, IBM Systems Director does this for you as part of the database configuration. Note: Use the graphical installer (db2setup) to install IBM DB2. This method provides an easy way to create the first client instance and the required users and groups. If you use the text 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 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 must first set several environment variables. You can choose from a few different options for setting the environment variables.
110
Option Manually create a dbvariables.properties file
Description 1. Create a /lwi/conf/overrides/ dbvariables.properties file to set the environment variables. After you complete this option, you do not need to do it again. This file must set the environment variables for AIX or Linux as follows: DBPATH Set the DBPATH environment variable to the IBM DB2 instance's /bin directory. DBLIBPATH Set the DBLIBPATH environment variable to the IBM DB2 instance's /lib directory. If you are using a 64-bit version of IBM Systems Director, you can set the directory to the /lib or /lib64 directory. If you are using a 32-bit version of IBM Systems Director, you can set the directory to the /lib or /lib32 directory. The following example shows what the file might look like: DBLIBPATH=/home/db2inst1/sqllib/lib32 DBPATH=/home/db2inst1/sqllib/bin 2. After you create the file, run the chmod command to ensure that users that are not root users do not have problems accessing the file. Run the command as follows: 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 initialize the connection from the IBM Systems Director server to your IBM DB2 database. Doing so creates a /lwi/conf/overrides/dbvariables.properties file with the environment variables necessary for IBM Systems Director to work properly with your IBM DB2 database. Note: Do not run the smreset command after running the cfgdbcmd command. If you do, all database data will be lost.After you complete this option, you do not need to do it again.
111
Option Manually set the environment variables
Description You can manually set the environment variables using the export command. Note: If you choose this option, each time you run the smstart, smsave, and smrestore commands you must also set the environment variables again. Otherwise, errors will result. For AIX , set the following environment variables using the export command: PATH Set the PATH environment variable to the IBM DB2 instance's /bin directory.
LIBPATH Set the LIBPATH environment variable to the IBM DB2 instance's /lib directory. If you are using a 64-bit version of IBM Systems Director, you can set the directory to the /lib or /lib64 directory. If you are using a 32-bit version of IBM Systems Director, you can set the directory to the /lib or /lib32 directory. The following example shows how to use the export command to set the environment variables for AIX : export PATH=$PATH:/home/db2inst1/sqllib/bin export LIBPATH=/home/db2inst1/sqllib/lib64 For Linux, set the following environment variables using the export command: PATH Set the PATH environment variable to the IBM DB2 instance's /bin directory.
LD_LIBRARY_PATH Set the LD_LIBRARY_PATH environment variable to the IBM DB2 instance's /lib directory. If you are using a 64-bit version of IBM Systems Director, set the directory to the /lib or /lib64 directory. The following example shows how to use the export command to set the environment variables for Linux: export PATH=$PATH:/home/db2inst1/sqllib/bin export LD_LIBRARY_PATH=/home/db2inst1/sqllib/lib32
4. Provide the database information to the system administrator who will install IBM Systems Director and configure it to use the database. The information will be needed later to enter on an installation panel or in the cfgdbcmd.rsp response file. The default response file is cfgdbcmd.rsp, which will reside in the <install_root>\proddata directory, where <install_root> is the root directory of your IBM Systems Director installation.
112
Table 41. Database configuration information and values Description Selected database application Notes: v If you want to install IBM Systems Director Server and configure it by setting options in a databaseconfiguration response file, then the value for DbmsApplication must match the database value that you select. v You must enter into the cfgdbcmd.rsp response file the exact value for the database as it appears here. Host name or IP address of the IBM DB2 DbmsServerName server instance Note: A IBM DB2 database must always be considered remote, even if IBM Systems Director Server and IBM DB2 server instances reside on the same system. Therefore, a host name or IP address is required here. DbmsDatabaseName Database name Note: If the database does not exist, then it is created later on by the cfgdbcmd task. If the database does exist, then it is used. Local installation folder in which the IBM DB2 client instance resides TCP/IP service port number for the IBM DB2 server instance User ID of the database user account that will be used to connect to the database Notes: v Database tables are created under the schema for this user ID. v If you will not use the database administrator user ID for the runtime connection, provide a second user with access to the information collection panel. Password of the database user account DbmsPassword Custom value: DbmsDatabaseAppHome DbmsTcpIpListenerPort DbmsUserId Custom value: Examples: v host1.domain.com v 127.0.0.1 Database configuration attribute DbmsApplication Value (select or input) DB2
Custom value: Example: DIRDB01
Custom value: Example: /home/db2clnt1/sqllib Custom value: Example: 50000 Custom value: Example: dirusr1
After you have prepared the IBM DB2 server and client instances for use with IBM Systems Director, you can connect IBM Systems Director Server to the database after installation regardless of your system configuration. See the Configuring the database connection after IBM Systems Director installation topic for the procedure. Note: The IBM DB2 Database for Linux, UNIX, and Windows Information Center at publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp has current information about security in IBM DB2.
113
Preparing the Oracle Database

If 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 you install IBM Systems Director Server. Complete the following tasks to prepare Oracle Database before installing IBM Systems Director Server: Tasks for the Oracle server: 1. Install Oracle Database. See the Supported database applications topic for supported 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 on an installation panel or in the cfgdbcmd.rsp configuration file after the IBM Systems Director installation. Do not use the database administrator ID or any default database user ID or password. Notes: v Do not specify the same user ID in the cfgdbcmd.rsp configuration file as is specified in the -dbAdmin parameter to cfgdbcmd. Doing so might result in an error or in having the user's administrator authority revoked. If you mistakenly used this configuration in the past, you might need to grant administrator authority again to this user ID after the cfgdbcmd command runs. v If you plan to use smsave or smrestore with IBM Systems Director Server and the database, you must: a. Enable password file authentication for the database system administrator user ID that is used for backup/restore. b. Ensure that the database instance owner is in the same primary group as the IBM Systems Director user who will perform the backup and restore operations. This will enable the database server to read and write the database backup image to the backup directory. v When you create the runtime user account on the database server, the user must change password at next logon option is selected by default. Ensure that you either deselect this option or change the password before configuring IBM Systems Director. You must do this because the user is actually not given the opportunity to change the password and, when they run the cfgdbcmd command, the database configuration will fail. IBM Systems Director does not save the database server administrator account user ID and password. Note: The user ID that is created must use the temporary tablespace temp. If you receive errors while running the smreset command to create tables, you might 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 install the Oracle Database administrator client on the same system on which IBM Systems Director Server is installed.
114
2. Ensure that the following environment variables are correctly set prior to IBM Systems Director startup. Note: For Linux on Power Systems and Linux on System z , you must be logged in as root user. ORACLE_HOME Ensure that this variable is set to the installation directory of the Oracle Database server or client. PATH Add the bin directory under the ORACLE installation root directory to the front of the system variable PATH. Note: If you already have the bin directory in your PATH, but it is not the first directory listed, consider moving it to the front of the PATH now. The smsave command might fail to create a backup if the bin directory 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 server host to include the information for your newly created database. If the Oracle Database server is remote, ensure that the information for your newly created database 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 that your 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 database v sqlplus sys/Netf1n1ty as sysdba b. In sqlplus, enter the following command to change the permissions of the remote login password file (REMOTE_LOGIN_PASSWORDFILE) to shared:
SQL SQL SQL SQL > > > > alter system set remote_login_passwordfile=SHARED scope=spfile; shutdown immediate; startup quit
c. Ensure that your listener.ora file resembles the following example for each database 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)
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 IBM Systems Director installed is consistent with your listener entries, like in the following 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 will be needed later to enter on an installation panel or in the cfgdbcmd.rsp response file. The default response file is cfgdbcmd.rsp, which will reside in the <install_root>\proddata directory, where <install_root> is the root directory of your IBM Systems Director installation.
Table 42. Database configuration information and values Description Selected database application Database configuration attribute DbmsApplication Value (select or input) Oracle Notes: v If you want to install IBM Systems Director Server and configure it by setting options in a databaseconfiguration response file, then the value for DbmsApplication must match the database value that you select. v You must enter into the cfgdbcmd.rsp response file the exact value for the database as it appears here. Host name of the server on which the database is installed Database name DbmsServerName DbmsDatabaseName Custom value: Custom value: Note: This value must match the name of the database that is created in the chosen database application. Custom value:
Database system identifier (SID) (Oracle Database only)
SID
116
Table 42. Database configuration information and values (continued) Description Database configuration attribute Value (select or input) Custom value:
Fully qualified local installation folder of DbmsDatabaseAppHome the database server instance or admin client instance on the IBM Systems Director Server system Note: This is the location of the SQLLIB directory. For example, a typical Windows installation will specify this as C:\Program Files\IBM\SQLLIB. TCP/IP listener port ID for the database User ID of the database user account Note: If you will not use the database administrator user ID for the runtime connection, provide a second user with access to the information collection panel. Password of the database user account DbmsTcpIpListenerPort DbmsUserId
Default or custom value: Custom value:
DbmsPassword
Custom value:
After you have prepared the database for use with IBM Systems Director, you can connect the IBM Systems Director Server to the database either after or during installation: Connect the database after installation You can connect the database after installation regardless of your system configuration. See Configuring the database application after IBM Systems Director installation for the procedure. Connect the database during installation (Windows only) If you are running on Windows, you also have the option of connecting the database during installation. See Installing IBM Systems Director Server on Windows using the InstallShield wizard for the procedure.
Preparing firewalls and proxies for IBM Systems Director

If you have firewalls in your network, or if the management server must use a proxy server to access the internet, you must configure the firewalls and proxy server to enable installation and operation of IBM Systems Director. IBM Systems Director must be able to access all the managed objects in the network, and if you will use a remote Web browser to access the management server, the remote systems running the Web browser and the management server must have access to each other. In addition, some functions of IBM Systems Director, including update manager, require access to the Internet. To enable this access, you must configure firewalls and proxies in your network to allow access by IBM Systems Director components. Complete the following steps to configure firewalls and proxies in your network: 1. Identify the ports that you will use in your systems-management environment and ensure that those ports are open before you start installation. For example, you must ensure that the listener ports for IBM Systems Director Server and Common Agent are open. See All available ports for a complete list of the ports that IBM Systems Director components can use.
117
2. Ensure that internet connections exist to the following internet addresses as they are required by IBM Systems Director and various plug-ins. Note: IP addresses are subject to change, so ensure that you use DNS names whenever possible.
Table 43. Required internet connections DNS name Update manager www.ibm.com 129.42.56.216, 129.42.58.216, 129.42.60.216 204.146.30.17 170.225.15.76 129.35.224.114 170.225.15.107 129.35.224.107 170.225.15.104, 129.35.224.104 129.35.224.115, 170.225.15.115 129.35.224.105, 170.225.15.105 443 or 80 https or http IP address Port(s) Protocol(s)
www-03.ibm.com download3.boulder.ibm.com download3.mul.ie.ibm.com download4.boulder.ibm.com download4.mul.ie.ibm.com delivery04-bld.dhe.ibm.com delivery04-mul.dhe.ibm.com delivery04.dhe.ibm.com Service and Support Manager eccgw01.boulder.ibm.com eccgw02.rochester.ibm.com www-945.ibm.com
443 or 80 443 or 80 443 or 80 443 or 80 443 or 80 443 or 80 443 or 80 443 or 80
https or http https or http https or http https or http https or http https or http https or http https or http
207.25.252.197 129.42.160.51 129.42.26.224, 129.42.34.224, 129.42.42.224 170.225.15.41 192.109.81.20 170.225.15.31
443 443 443
https https https
www6.software.ibm.com www.ecurep.ibm.com testcase.boulder.ibm.com
443 443 21
https https ftps
3. If the management server requires access to the Internet but does not have direct access, complete the following steps to configure the management server to 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 authentication with 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 server to use the proxy server. See Changing update settings for more information. Related reference Electronic Service Agent Web site
Preparing to install IBM Systems Director Server on AIX

Before installing IBM Systems Director Server on AIX , make sure that your management server meets the applicable requirements.
118
Run the IBM Systems Director Pre-Installation Environment Checker to help validate that the requirements that are applicable to your system have been met. See Running the IBM Systems Director Pre-Installation Environment Checker on AIX and Linux for instructions on how to run the IBM Systems Director environment analysis tool. Complete the following preparatory steps before installing IBM Systems Director Server on AIX : 1. Ensure that your system meets the hardware and software requirements (including those for databases, security, and networking) for installation, as described in Hardware and software requirements. To verify the AIX operating system level, run the following command:
oslevel -s
The command should return a value such as 5300-09-00-nnn, where nnn is irrelevant. 2. Optional: Download updates for your system, if necessary. Download AIX operating system updates from the IBM Fix Central Web site. Note: Select Power or System p for the Product family and AIX for the Product. 3. Ensure that the following required openssl and openssh versions are installed: v openssl.base 0.9.8.4 or higher v if installed, openssh.base.server 4.5.0.5301 or higher There is a dependency between openssl and openssh versions. If openssl is not 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 openssh installation. 4. Note the following list of required file sets that are installed as part of the IBM Systems Director Server installation: v expect.base 5.42.1.0 v tcl.base 8.4.7.0 v tk.base 8.4.7.0 Note: Obtain any missing RPMs from the operating system distribution media or use a package manager to find and install a missing library or RPM. For information on using a package manager to find and install a missing library or 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 your system, you can now safely uninstall the bash rpm if it is not used for any other application. Previous versions of IBM Systems Director Server on AIX required that bash be installed. This dependency was removed in IBM Systems Director 6.2. Enter the following commands to uninstall bash:
rpm -qa | grep bash rpm -e bash_rpm_name # To determine the exact rpm name
119
6. Ensure that the following file sets that are required for and installed with Common Agent on AIX will not conflict with any other applications that are installed on your system: v sysmgt.cim.providers 1.2.9.0 v sysmgt.cim.smisproviders 1.2.2.0 v sysmgt.cimserver.pegasus 2.9.1 v 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 Web interface, ensure that the dsm.core file set installed. The server installation does not check if dsm.core is installed, but these functions will work only if it is. 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 IP address lookups for loopback. For more information, see Agent install timeout due 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. By default, Common Agent requires ports 9510, 9514, and 9515 during installation and 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 is if you have a different version of the CAS agent installed, for example as part of 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 by running the following command:
/var/opt/tivoli/ep/runtime/agent/toolkit/bin/configure.sh -unmanaged -port not_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 and users have the permissions required to complete IBM Systems Director tasks. 11. Optional: If you want to use the FSP Proxy extension, which is necessary for the Power Management tasks for standalone and IVM-managed hosts, ensure that the following necessary file sets are installed. Note: IBM Systems Director Server no longer automatically installs these file sets to prevent possible installation inconsistencies with CSM. csm.hc_utils 1.7.0.0 or higher along with its CSM install requisites The CSM file sets are included on the AIX operating system media or can be downloaded from the IBM Cluster Systems Management Web site at http://www14.software.ibm.com/webapp/set2/sas/f/csm/ download/home.html. Install each file set with SMIT or the following command:
installp -acgXYd fileset_location fileset_name
where fileset_location is the location of the downloaded file sets and fileset_name is the name of the file set that you are installing.
120
Director.Server.ext.FSPProxy.rte Obtain this file set from the IBM Systems Director for AIX, V6.2.1 DVD or the SysDir6_2_Server_AIX.tar.gz file. Install the file set with SMIT or 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 server

After preparing your system, use the IBM Systems Director Server installation procedure for the operating system on which you plan install IBM Systems Director Server. Note: You are advised to not install IBM Systems Director on the same system as IBM Storage Configuration Manager (SCM).
Installing IBM Systems Director Server on AIX

After preparing your system, you can install IBM Systems Director Server on AIX by 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 the updates for 6.2.1. When running the installation from the refreshed installation media, 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 installation media. If you use a response file, you can edit the dirserv.rsp response file to specify 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 necessary to separately install Common Agent or Platform Agent on the management server after installing IBM Systems Director Server. v Common Agent and Platform Agent are now shipped as part of the AIX operating 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 an overwrite 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 and Platform Agent are installed when upgrading from a previous version of AIX if a previous version of the agent is already installed. Both are also installed when you perform an overwrite 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). The following agent version 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.
121
- 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. - AIX Version 6.1 TL06 and AIX Version 7.1 include Common Agent 6.2.0 and Platform Agent 6.2.0. v Installing IBM Systems Director Server 6.2.1 on an AIX system on which the agent is already installed will update the agent to the 6.2.1 level if it is not already at this level. v By default, Common Agent is started when your system is rebooted. You can disable this function with the steps in the Disabling IBM Systems Director agents topic. v IBM Systems Director Server is not supported to run on a system with workload partitions (WPARs) enabled. You can install IBM Systems Director Server on AIX from either installation media or from a downloaded installation package. Important: The IBM Systems Director Server and Common Agent installation packages for AIX are provided in English only.
Table 44. Installation options for IBM Systems Director Server on AIX Installation method DVD media Title or file name IBM Systems Director for AIX, V6.2.1 DVD Note: To obtain an image of the IBM Systems Director for AIX, V6.2.1 DVD, download the SysDir6_2_1_DVD_AIX.iso file. Attention: If you use DVD media to install IBM Systems Director Server, ensure that you allot an additional 1.5 GB of available space in the /opt file system to contain the agent packages that are copied from the DVD at the end of the server installation. The packages are copied to /opt/ibm/director/packaging/agent on the server. Installing IBM Systems Director Server from AIX 6.2.1 DVD media does not install the agents. This is an exception for 6.2.1. The SysDir6_2_1_Common_Agent_platform.jar files are provided in the agent subdirectory of the DVD media. Downloaded installation package SysDir6_2_Server_AIX.tar.gz (1.36GB) Attention: When downloading the installation package file to your AIX server, you must first run the following command to increase the default file size limit: ulimit -f 4194302
After the installation process, you can configure a database to use with IBM Systems Director and change security settings.
122
Note: If you plan to use the default Apache Derby database, you can choose either the basic installation path, which configures Apache Derby by default, or the custom installation path. Installing IBM Systems Director Server 6.2.1 using the dirinstall.server script is the only supported method. Network Installation Manager (NIM) is not supported for installing IBM Systems Director Server. To install IBM Systems Director Server, log in as the root user and complete the following steps: Tip: You can find the installation logs for this process in /var/log/dirinst.log and /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 Director Downloads Web Site at www.ibm.com/systems/management/director/ downloads/. c. To unzip and extract the contents of the installation package, type the following 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 the following command and press Enter:
cd /install_files/
where install_files is the path to the extracted installation files. DVD media: To start the installation from the 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:
where dev is the specific device file for the block device and mnt is the mount point of the drive. c. To change to the directory in which the installation script is located, type the 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 modify the installation settings in your local copy. a. Type the following command and press Enter:
cp dirserv.rsp /directory/
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 options v Specify the Web console port numbers v Specify the Tivoli Provisioning Manager host name and IP address v Specify migration options v Enable or disable the nonstop service, which keeps the server continuously running v Specify a different database v 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, comment out that value with a # symbol at the beginning of the line instead of leaving the value blank. v If you need to enter any Windows-based locations, ensure that you include the back slash after drive_letter:. For example, use C:\foldername instead 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 press Enter: 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 application other than that which is supplied by default. For more information, see Configuring the database application after IBM Systems Director installation. Important: You can configure IBM Systems Director for use with your database application at any point after the installation of IBM Systems Director Server, but you must not start the management server until it is completed. Starting the management server before configuring IBM Systems Director to use a database application might result in a loss of function. 5. Complete the following steps to start IBM Systems Director Server: a. 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 to the configAgtMgr.sh script prompts. After you have provided all the requested information, the configuration of the embedded agent manager (if
124
chosen) and registration of IBM Systems Director Server as the resource manager with the embedded or existing agent manager begins. The agent manager configuration script runs and displays a series of status messages. c. If it is not already started, start IBM Systems Director processes on the management 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+C causes 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 you upgraded from IBM Systems Director Server 6.1.x, the only agent deployment packages that are available by default are all applicable 6.2 agent packages (if you upgraded using the DVD media) or only the 6.2 subagent packages (if you upgraded using a downloaded installation package). Any agent deployment packages that were installed by default in 6.1.x or that you imported through the Agent Import task are no longer available. Therefore, complete the following 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 download them 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 to import and click OK. After a successful import, the 6.1.x packages will appear in the IBM Systems Director Web interface and will be ready for distribution. 7. If you used the DVD for installation, complete the following steps to unmount the drive and remove the DVD: a. Type cd / and press Enter. b. Type the following command and press Enter:
umount /mnt
where mnt is the mount point of the drive. c. Remove the DVD from the drive. 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 affect cimserver. v /tmp/cimlistener_start.conf Note: This file is deleted when cimlistener shuts down. This does not affect cimlistener. v /tmp/elasocket_cimv2 v /tmp/dpi_socket
125
If you have not already merged and installed the updates as part of the installation, then you can use update manager to update to the latest version of IBM Systems Director. See Updating IBM Systems Director for instructions. Note: Before performing an update, you will need to understand disk space requirements. For information on disk space requirements for updates, see Determining disk space requirements for applying updates or the IBM Systems Director Best Practices Wiki. Related reference IBM Systems Director Downloads IBM Systems Director Best Practices Wiki
Configuring the database connection after IBM Systems Director installation

After IBM Systems Director installation, you can configure IBM Systems Director to use a different database application. During this process, any previous data that was 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 for information. 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 they are not, use cfgserver.bat or configDB.sh, as described in Encrypting passwords for database configuration, to encrypt them. Complete the following steps to use the cfgdbcmd.rsp file to configure your database: 1. Open the cfgdbcmd.rsp file with any text editor. The cfgdbcmd.rsp file resides in the install_root\proddata directory, where install_root is the root directory of your IBM Systems Director installation. 2. In the cfgdbcmd.rsp file, ensure that the configuration information for your chosen database is not commented out and that the configuration information for 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 Director Server. So, to ensure that your chosen database is not commented out, remove the ; character at the beginning of each applicable line for your database. 3. Use information from your local database administrator to fill in all of the fields needed for your chosen database application. See Preparing the database application for information about what you need to gather from each applicable database server. Attention: Ensure that you do not use any quotes in the response file as they will cause errors during database configuration. 4. Save and close the cfgdbcmd.rsp file. 5. Run the script that encrypts passwords for your database configuration. The script that you use varies depending on which operating system you are using. See Encrypting passwords for database configuration for details.
126
6. After the encryption script is complete, run the cfgdbcmd tool. Depending on your operating system, the file name of the tool is either cfgdbcmd.cmd or cfgdbcmd.sh. The cfgdbcmd tool will use the response file that you previously filled in to properly connect IBM Systems Director Server to the chosen database. See cfgdbcmd command for information. Note: The -dbAdmin and -dbAdminPW parameters for the cfgdbcmd tool serve different purposes than the DbmsUserId and DbmsPassword database configuration attributes in the cfgdbcmd.rsp file. The -dbAdmin and -dbAdminPW parameters for the cfgdbcmd tool must specify the user ID and password for the database administrator or, in the case of IBM DB2, the instance owner ID so that the tool has the authorization to create a database. Tip: When running cfgdbcmd on a Linux or AIX operating system, it is recommended that you omit the -dbAdmin and -dbAdminPW parameters for security reasons. The tool will prompt for the administrator user ID and password 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 the install_root\bin folder to reinitialize the databases and clear all persistent data. See smreset command for information. Attention: IBM Systems Director Server will not start correctly if you do not complete 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 the documentation for the specific database application for information about how to do that. After the configuration is complete, IBM Systems Director Server is properly connected to your chosen database. Attention: Connectivity problems with the database server will affect IBM Systems Director. For example, if the database server goes offline or becomes unreachable, 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 installation

Before you start using IBM Systems Director, review these recommendations for configuring systems and setting up your environment. Configure IBM Systems Director Server after a successful installation, so that you can get the most benefit from the product, and be able to work efficiently. Do not confuse this task with Configuring Systems, which is a separate topic for configuring those resources that are controlled by IBM Systems Director. Note: Before proceeding with the following instructions, you might need to specify a preferred IP address for the IBM Systems Director Server or exclude certain IP addresses that you do not want Systems Director to manage. For example, if the server on which you installed Systems Director has more than one network
127
interface card, specify one IP address for Systems Director to use to communicate with managed resources. For more information, see Configuring IP address properties. The Welcome page of IBM Systems Director provides a quick overview, as well as links to all necessary configuration tasks. To configure IBM Systems Director, perform these steps: 1. Click System Discovery on the Start tab to discovery recently-installed agents. 2. Click Collect and View Inventory on the Start tab to collect inventory data on all the recently-installed agents. 3. In the Next Steps section, click Register IBM Systems Director and complete the product registration. 4. Run these options in the Next Steps list. v Create event thresholds and automation plans v Check for updates on discovered systems. v Set up additional user security v Start configuring your systems
Configuring IBM Systems Director plug-ins and platforms

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

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

Review these instructions if you are using Microsoft Internet Explorer Web browsers that have Enhanced Security Configuration enabled, and are running on Windows Server 2003 or Windows Server 2008. When using a Web browser with Enhanced Security Configuration enabled, some properties of the IBM Systems Director Web interface might not display as expected. Internet Explorer Enhanced Security Configuration establishes a configuration for your server and for Internet Explorer that decreases the exposure of your server to potential attacks that can occur through Web content and application scripts. As a result, some Web sites might not display or perform as expected. Using a server for Internet browsing is not a good security practice because Internet browsing increases the exposure of your server to potential security attacks. It is a best practice recommendation that you run your Web browser on a system that is not a server. However, if you must use a server running Windows Server, you must turn off Internet Explorer Enhanced Security Configuration. Complete the following applicable steps to disable Internet Explorer Enhanced Security: 1. On Windows Server 2003 systems: a. Click Start > Control Panel. b. In the Control Panel window, click Add or Remove Programs. c. Click Add/Remove Windows Components. d. Clear the Select Internet Explorer Enhanced Security Configuration check box. e. Click Next; then, click Finish. 2. On Windows Server 2008 systems:
130
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 properties

Configure IP address properties when your management server has more than one IP address, when your network uses one or more subnets that IBM Systems Director does not manage, and when resources that you want to manage have more than one IP address. Configure IP address properties by creating or updating the IPPreference.properties file.
Specifying the preferred IP address for the management server

When your management server has more than one IP address, specify the IP address that you want the server to use. For example, a server that has more than one network interface card has more than one IP address. Specify the preferred IP address for the management server by creating or updating the IPPreference.properties file. To specify the preferred IP address for the management server, 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.properties where install_path is the path where you installed IBM Systems Director. Note: If the /data/IPPreference.properties file exists, open the file with a text editor, 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 the change correctly supercedes the current entry. 3. Save and close the file. For Systems Director to recognize the preferred IP address, you must restart the management server.
131
Excluding IP addresses
Exclude IP addresses for resources that you do not want IBM Systems Director to manage or that have multiple IP addresses, or for subnets that you do not want Systems Director to manage. To exclude IP addresses, create or update the IPPreference.properties file. You can exclude one or more individual IP addresses, an IP address range, or an entire 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.properties where install_path is the path where you installed IBM Systems Director. Note: If the /data/IPPreference.properties file exists, open the file with a text editor, 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 that you 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 the management server.
Logging on to IBM Systems Director Server for the first time

After installing IBM Systems Director Server, you need to log on using a Web browser, discover managed systems, and request access to those managed systems. You must already have installed and started IBM Systems Director Server before beginning this task. 1. Log on to IBM Systems Director using a Web browser. a. Point your browser to the following URL:
132
http://System_Name:Port_Number/ibm/console
where System_Name is the name of the system on which IBM Systems Director Server is installed and Port_Number is the first (lower) of two consecutive port numbers that you specified for the Web server to use. The default ports for the Web server are 8421 and 8422. If you use port 8422, make sure that you specify https to indicate a secure port. b. Type the user ID and password that correspond to an authorized IBM Systems Director administrator user ID and password. Authorized administrator credentials include those for the root user or any user that is a member of the smadmin group. c. Click Log in. Note: A security alert window might be displayed before logging in. This is due to incorrect configuration of the Secure Sockets Layer (SSL) certificate. For information see Configuring Secure Sockets Layer (SSL) between IBM Systems Director and the Web browser client. 2. Discover your managed systems. The first time you log on to IBM Systems Director Server, a Discover button is displayed. Click it to start discovering your managed systems. 3. Request access to your managed systems. Secured systems are displayed in IBM Systems Director Web interface with a padlock icon beside them in the Access field or column of the systems details. After a system is accessed, the padlock disappears and additional tasks and status information are available. The Access attribute for each resource shows the current access status. You cannot request access to 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 the same user ID and password. a. In IBM Systems Director Web interface, click Navigate Resources. b. Navigate to the system that you want to access. c. Right-click the system for which you want to request access and select Security > Request Access. d. On the Request Access page, type the user ID and password of a user that belongs to the System group. e. Click Request Access. You can now begin managing the systems you have discovered, or install agents on managed systems to enable additional management capabilities.
Restarting IBM Systems Director Server

Restarting the IBM Systems Director Server requires that you run one command to stop the management server processes and then run another command to start them again. Before you stop the IBM Systems Director Server, warn users to finish their work or stop the processes they are running.
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 IBM Systems 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 started successfully when this command returns a value of Active. Note: You can use Ctrl+C to exit from smstatus -r if necessary. Ctrl+C causes the smstatus command to end. v If you are running Windows, check the status of the server by checking the system tray.
Enabling Dynamic IP support

If the IP address of the system running IBM Systems Director Server changes, enabling the Dynamic IP support feature automatically re-configures IBM Systems Director 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 the management server had to remain static. This meant that the IP address of the management server was not supposed to change after IBM Systems Director Server was installed on the system. In IBM Systems Director 6.2, changing the IP address of IBM Systems Director Server is supported. If the IP address of the IBM Systems Director Server system changes, the embedded Dynamic IP feature automatically detects the changed IP address when the IBM Systems Director Server stops and starts 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 be updated to use the server's new IP address. This ensures that the resources that are managed by IBM Systems Director Server maintain communication with the server after its IP address has changed. Restriction: This feature is not supported if you are managing 6.1.x common agents. 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 Systems Director Server IP address when it changes: v Operating system v BCChassis
134
v v v v v
Server (RSA, IMM, BMC) HMC IVM StorageSubSystem Switch Attention: If you configure the switch to send SNMP traps to IBM Systems Director Server, the switch will not automatically update if the IP address changes. Because it requires a manual action from the user to set the SNMP trap destination, it will also require a manual action to change it. Most switches support setting multiple SNMP trap destinations, so configure the switch to send SNMP traps to both the primary IBM Systems Director Server IP address and any backup IP addresses to which IBM Systems Director Server could potentially move. However, this is only possible if it is known ahead of time that there is a small set of IP addresses to which IBM Systems Director Server could potentially move.
Notes: v Frequent IP address changes can drive network traffic in association with updating the managed resources with the new IBM Systems Director Server IP address. IP address changes can also cause the IBM Systems Director Server CPU utilization to increase and slow down overall performance for the time period 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 not work unless IBM Systems Director Server is restarted. v IBM Systems Director Server should be started for the first time on the same IP address on which it was installed. Changing the IP address any time after the first startup is supported. v Processing for an IP address change is not supported for the scenario where the configuration for one IBM Systems Director Server and data is captured with the smsave command and restored to another IBM Systems Director Server with the smrestore command and both of these IBM Systems Director Server instances have different IP addresses. To enable the Dynamic IP function, complete the following steps when the IP address 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, IBM Systems 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 (become active) when it is restarted for the first time with a new or modified IP address because 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 the following command in a command prompt or shell on the management system:
smcli querysystem OID_of_local_OS_MEP 1
135
After you complete the above steps, the processes of reconfiguring and notifying the managed resources about the IP change will commence. Note: It will take typically eight to ten minutes after IBM Systems Director Server becomes active for the IP address change notifications to be sent to the managed resources. By default, IP address related processing is enabled (turned on) on IBM Systems Director Server. To turn the processing for an IP address change on or off, set the com.ibm.usmi.kernel.localsystem.USMSLocalSystemService .enableIPChangeProcessing property in the install_root\lwi\conf\overrides\ USMIKernel.properties file: Turn IP address change processing on To 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 processing will be enabled by default. Turn IP address change processing off To turn off IP address change processing, add or edit the property to set it to false:
com.ibm.usmi.kernel.localsystem.USMSLocalSystemService. enableIPChangeProcessing=false
136
Chapter 4. Preparing agentless managed systems

Prepare the agentless managed systems in your environment before you discover or 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 a managed resource has multiple IP addresses, specify which IP address Systems Director uses to manage the resource. To specify the IP address to use, you specify that the management server ignore (or exclude) the other IP addresses associated with the resource. For more information, see Excluding IP addresses. Related reference AIX Pegasus CIM server and providers
Configuring access to agentless managed systems

Using an account other than root to access an agentless management system enforces the appropriate security for the system while enabling more detailed audit records for access to the system. To configure access to an agentless managed system 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 agentless capabilities of a system, even though there might be a platform agent installed on the 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 for agentless capabilities. The sudo utility is provided with Linux operating systems. To use the sudo utility with AIX systems, you will need to download and install the utility from the IBM AIX Toolbox Download Web site. Perform these steps to configure access to agentless management systems for user accounts 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 be located in the /etc/sudoers directory. 2. Ensure that each user account to be used for access to the agentless managed system has authorization to run sudo commands. 3. In install_root/lwi/conf/overrides/USMi.properties file, set the following system 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 to the system through either the IBM Systems Director Request Access page, the Configure Access page, or the Configure Systems Credentials page.
137
Sample sudo configuration file

Use the sample sudo configuration file as a basis for setting up configuration to agentless 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_home Defaults 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_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_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_TELEPHONE LC_TIME LC_ALL LANGUAGE LINGUAS XDG_SESSION_COOKIE XMODIFIERS GTK_IM_MODULE QT_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. root ALL ALL=(ALL) ALL # WARNING! Only use this together with Defaults targetpw! # Runas alias specification # User privilege specification root 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
Preparing AIX managed systems

You might need to configure certain AIX systems before you can discover them with IBM Systems Director Server. Ensure that each AIX system that you want to manage has been appropriately configured. Typically, managed systems are first discovered using the discovery task in IBM Systems Director Web interface. Then, Platform Agent or Common Agent is installed on the managed systems directly from IBM Systems Director Web interface. The configuration of some AIX managed systems, however, can prevent discovery by IBM Systems Director Server. Note: If an agentless system is running openssh 4.7.0.530, you cannot use the Agent Installation Wizard to remotely install the agent on AIX . Complete the following steps on each AIX system to enable discovery by IBM Systems 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 BladeCenter

IBM Systems Director can be deployed to manage the blade servers in a IBM BladeCenter chassis.
Preparing to manage a IBM BladeCenter chassis using IBM Systems Director Server on a non-blade server
You can install IBM Systems Director Server on a non-blade server. With this management server you can manage one or more IBM BladeCenter units and the blade servers installed in them. You must configure the network so that this installation is possible. Complete the following steps to prepare to manage an IBM IBM BladeCenter chassis using IBM Systems Director Server installed on a non-blade server: 1. Consider using a Dynamic Host Configuration Protocol (DHCP) server to assign an address to the external port of the management module. When a IBM BladeCenter management module is first started, it searches for a DHCP server. If a DHCP server is not found, the IBM BladeCenter management module assigns IP address 192.168.70.125 to the external management port. Because this static IP address is the same for all management modules, IP address conflicts can occur if you do not use a DHCP server and introduce multiple IBM BladeCenter chassis onto a network simultaneously. When you configure the IBM BladeCenter chassis, you assign static IP addresses to the switch module and the external and internal ports of the management module. 2. Set up a separate management network to configure and manage your IBM BladeCenter chassis and blade servers. By separating the LAN segment used for production from the LAN segment to which the IBM BladeCenter management module is connected, you can ensure that only authorized system administrators can connect to the IBM BladeCenter chassis and switch modules. Figure 2 on page 140 shows such a network configuration.
139
3. If you intend to use Remote Deployment Manager (RDM), install RDM on the management server. 4. If you plan to use a database application other than Apache Derby, consider installing the database server on the management LAN. 5. Make sure that you have installed the latest version of the management module firmware. To download the firmware, go to the IBM Servers Web site at www.ibm.com/servers/.
Figure 2. Example of IBM BladeCenter deployment network when IBM Systems Director Server is not installed on a blade server
This network configuration ensures that applications running on the blade servers cannot modify chassis settings, because the blade servers have no connection to either the management module or the switch module configuration ports. Note: If you are using an IBM BladeCenter management module instead of an advanced management module, only one of the following software applications can communicate with it at any given time: v Cluster Systems Management (CSM) v IBM Systems Director Server v IBM Management Processor Command-Line Interface (MPCLI)
Preparing to manage a IBM BladeCenter chassis using IBM Systems Director Server on a blade server
You can install IBM Systems Director Server on a blade server. With this management server you can manage the IBM BladeCenter unit, including the server on which IBM Systems Director Server is installed, and other IBM BladeCenter units. You must configure the network so that this installation is possible. Consider the following issues when managing the IBM BladeCenter unit that contains the management server: v Enable access for authorized administrators as determined by the security policy established for the user environment.
140
v Be careful when making changes to the configuration of the IBM BladeCenter chassis from IBM Systems Director itself. Such changes could effectively remove the instance of IBM Systems Director Server from the network and halt the entire IBM Systems Director environment. Specifically, do not perform these tasks on the blade server where IBM Systems Director Server is installed without careful consideration: Powering off that blade server Changing the boot options on that blade server v Create a network setup that enables the IBM BladeCenter Management Module to communicate with the management server. Otherwise IBM Systems Director will be unable to discover the IBM BladeCenter chassis that contains the management server. By default, the blade servers installed in a IBM BladeCenter chassis cannot communicate automatically with the IBM BladeCenter Management Module. This architecture is designed to prevent the blade servers from modifying the IBM BladeCenter chassis settings. If you install IBM Systems Director Server on a blade server and want to use the instance of IBM Systems Director to manage the IBM BladeCenter unit in which the management server is installed, you must enable communication between the management server and the management module. 1. Consider using a Dynamic Host Configuration Protocol (DHCP) server to assign an address to the external port of the management module. When a IBM BladeCenter management module is first started, it searches for a DHCP server. If a DHCP server is not found, the IBM BladeCenter management module assigns IP address 192.168.70.125 to the external management port. Because this static IP address is the same for all management modules, IP address conflicts can occur if you do not use a DHCP server and introduce multiple IBM BladeCenter chassis onto a network simultaneously. When you configure the IBM BladeCenter chassis, you assign static IP addresses to the switch module and the external and internal ports of the management module. 2. Set up a separate management network to configure and manage your IBM BladeCenter chassis and blade servers. By separating the LAN segment used for production from the LAN segment to which the IBM BladeCenter management module is connected, you can ensure that only authorized system administrators can connect to the IBM BladeCenter chassis and switch modules. Figure 2 on page 140 shows such a network configuration. 3. To use an installation of IBM Systems Director Server on a blade to manage the IBM BladeCenter unit in which the management server is installed, enable communication between the Campus LAN and the Management LAN. Figure 3 on page 142 shows such a network configuration. 4. If you plan to use a database application other than Apache Derby, consider installing the database server on the management LAN. 5. Make sure that you have installed the latest version of the management module firmware. To download the firmware, go to the IBM Servers Web site at www.ibm.com/servers/.
141
Figure 3. Example of IBM BladeCenter deployment network when IBM Systems Director Server is installed on a blade server
With this configuration, IBM Systems Director Server can communicate through the Campus LAN to the Management LAN and then onto the management module. Note: If you are using an IBM BladeCenter management module instead of an advanced management module, only one of the following software applications can communicate with it at any given time: v Cluster Systems Management (CSM) v IBM Systems Director Server v IBM Management Processor Command-Line Interface (MPCLI) Related reference IBM Servers
Preparing Hardware Management Console devices for discovery with IBM Systems Director
Before discovering Hardware Management Console (HMC) devices, and after upgrading HMC hardware, you might need to open the Pegasus and SLP ports to enable IBM Systems Director to discover and manage the HMC. Complete the following steps to enable the Pegasus and SLP ports on the HMC device: 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 their associated port numbers, that are recognized by the HMC. The Allowed Hosts table displays a list of only those applications for which the HMC firewall is configured to allow access to the HMC.
142
Note: If a scroll bar appears on the table, use it to view all the applications in the table. 6. In the Available Applications table, select Open Pegasus and click Allow Incoming. Open Pegasus is added to the Allowed hosts table of enabled ports. 7. In the Available Applications table, select SLP and click Allow Incoming. SLP is 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 Server can discover the HMC. Related reference AIX Pegasus CIM server and providers
143
144
Chapter 5. Discovering systems and collecting inventory data

To manage a resource within an environment or view inventory data about it, that resource must first be discovered and, after access is granted, an inventory must be collected. The resource is recognized and added to the comprehensive list of native resources and native attributes for the system. Discovery and inventory collection are the two primary tasks that are used to connect to supported network resources and collect information about them.
Discovery protocols
A discovery protocol is any network communication protocol that IBM Systems Director Server uses during the discovery process to discover a resource.Getting started discovery uses a predetermined list of protocols. When you specify a single IP address, a single host name, or a single range of IP addresses, system discovery uses one or more protocols based on the selected target resource type. Using a discovery profile enables you to refine the target resource type and configure specific protocols that you want to use. The communication protocols that IBM Systems Director Server uses during discovery depend on the protocols used by the target resource type. You need to decide about the different protocols only when you create or edit a discovery profile. The Discovery Profile wizard helps you select and configure the correct protocol for the type of resource that you want to discover. When discovering a large number of resources, network traffic associated with the discovery process might cause timeouts that result in some discoverable resources remaining undiscovered. To help prevent this problem, use one or more discovery profiles. Using a discovery profile enables you to target specific resources and limit the number of communication protocols used during discovery. Limiting the number of communication protocols used when discovering a large number of resources helps avoid problems caused by network traffic collisions and timeouts. By default, IBM Systems Director supports the following discovery protocols: Agent manager discovery Agent manager discovery specifically targets the discovery of Tivoli common agents. In the Tivoli paradigm, Service Location Protocol (SLP) is not supported and management servers contact an agent manager that knows about the agents in their environment. You can select the agent managers that you want to use in discovery. Common Agent Services (CAS) discovery CAS discovery utilizes Service Location Protocol (SLP) discovery, with which clients can locate servers and other services on the network. Common Information Model (CIM) discovery CIM discovery utilizes the Service Location Protocol (SLP) for discovery. With CIM discovery, clients can locate servers and other services on the network. Interprocess communication (IPC) discovery IPC is the process by which programs send messages to each other. Sockets, semaphores, signals, and internal message queues are common methods of interprocess communication. IPC is also a mechanism of an
145
operating system that enables processes to communicate with each other within the same computer or over a network. IPC leverages services that IBM Systems Director provides that components use to communicate with each other. By using these services, a server task can communicate with an agent task running on a target. Secure shell (ssh) discovery Secure shell is a Unix-based command interface and protocol for securely accessing a remote computer. With ssh discovery, you can specify either a single IP address or a range of IP addresses upon which to run discovery Simple Network Management Protocol (SNMP) discovery SNMP is a network management standard widely used in TCP/IP networks. SNMP performs management services by using a distributed architecture of management systems and agents. SNMP provides a method of managing network hosts such as workstation or server computers, routers, bridges, and hubs from a centrally-located computer running network-management software. Storage Management Initiative Specification (SMI-S) discovery With SMI-S discovery, clients can locate servers and other services on the network. It is a design specification developed by the Storage Networking Industry Association (SNIA) that specifies a secure and reliable interface with which storage management systems (SMSs) can identify, classify, monitor, and control physical and logical resources in a storage area network (SAN). The interface integrates the various devices to be managed in a storage area network (SAN) and the tools used to manage them. Windows Distributed component object model (DCOM) discovery Use Windows DCOM (an extension of the Microsoft Component Object Model (COM) to support objects distributed across a network) configuration to specify either a single IP address or a range of IP addresses upon which to run discovery. Note: Additional discovery protocols are routinely created by vendors. For more information about communicating with a device that uses a protocol that is not listed here, contact the manufacturer or software provider for that device.
Discovering systems with system discovery

Use the system discovery task to discover one or more resources based on a specific IP address, host name, or range of IP addresses or by using a discovery profile. You can also use system discovery to discover properly configured systems that use mirrored images. View the results of the current system discovery or a system discovery that ran previously.
System discovery
To discover systems at a specific network address or range of addresses, use system discovery. This method is useful in networks in which both broadcast and multicast messages are filtered. System discovery discovers Agentless managed systems, Platform Agent managed systems, and Common Agent managed systems by sending a unicast request to one or more addresses. IBM Systems Director Server sends one request to each system at a time. You can also use system discovery to discover systems that use a mirrored image (cloned systems).
146
System discovery provides the following functions: v Discovery based on a single IP address v Discovery based on a range of IP addresses v Discovery based on a host name After systems are discovered, they are displayed in a table for viewing. During system discovery, IBM Systems Director Server attempts to communicate with target resources by using a predetermined list of protocols.
Performing a system discovery

Use the System Discovery task to discover one or more resources by specifying a single IP address, single host name, or a single range of IP addresses, or by using a discovery profile. To perform a system discovery, complete the following steps: Note: v Discover only those resources that you intend to manage with IBM Systems Director. For example, if the management interfaces of your networking equipment are on a single subnet, yet you do not intend to manage your networking equipment with IBM Systems Director, do not discover devices on that subnet. v When discovering a large number of resources, network traffic associated with the discovery process might cause timeouts that result in some discoverable resources remaining undiscovered. To help prevent this problem, use one or more discovery profiles. Using a discovery profile enables you to target specific resources and limit the number of communication protocols used during discovery. Limiting the number of communication protocols used when discovering a large number of resources helps avoid problems caused by network 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: Use a single IPv4 or IPv6 address Complete these steps: 1. Select Single IPv4 address or Single IPv6 address from the Select a discovery option field. 2. In the IP address field, type the IP address of the system that you want to discover. 3. If you want to discover only a specific resource type, select it from the Select the resource type to discover list.
147
Table 45. System discovery methods (continued) To do this task: Use a range of IPv4 or IPv6 addresses Complete these steps: 1. Select Range of IPv4 addresses or Range of IPv6 addresses from the Select a discovery option field. 2. For the IP address range that contains the systems that you want to discover, type the complete low-end IP address in the Starting IP address fields and the last piece of the high-end IP address in the Ending IP address field. 3. If you want to discover only a specific resource type, select it from the Select the resource type to discover list. 1. Select Single host name from the Select a discovery option field. 2. In the Host name field, type the host name of the system that you want to discover. 3. If you want to discover only a specific resource type, select it from the Select the resource type to discover list. 1. Select Select a discovery profile to run from the Select a discovery option field. 2. Select the profile that you want to use from the Discovery profile to run field. 1. Click Create new profile under Advanced Tasks. 2. Use the Discovery Profile wizard to create a discovery profile. After saving the profile, the System Discovery page display automatically, and the profile you created is already selected.
Use the host name of a system
Use an existing discovery profile
Create and use a discovery profile
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 to configure the Schedule, Notification, and Options settings for the discovery task. 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 table displays the resources that are discovered during the current discovery and those resources that were discovered previously. v The Discover Now and Schedule buttons are deactivated and the Stop and New Discovery buttons appear. 4. Optional: If you want to stop the discovery process, click Stop. If you want to run a new discovery while the current discovery continues to run, click New Discovery. When you choose to run a new discovery, the Discovered
148
Manageable Systems table displays results for the new discovery only. To view the results of the current discovery, use the Discovery jobs task. As the process discovers manageable resources, the Discovered Manageable Systems table displays them, including those resources that were discovered previously. Note: After a resource is discovered, the virtual systems that are associated with that 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 on such factors as network performance and the number of systems that are discovered. Avoid managing newly discovered resources for a time after the discovery task finishes, because associated processing continues to run. When the discovery process completes, the status icon and text message disappear and the Discover Now and Schedule buttons become active again.
Using system discovery to view current results

Use the System Discovery task to view a table that contains the results of your current system discovery task. To use the System Discovery task to view the system discovery results as you discover systems, complete the following steps: 1. Open the System Discovery page using either of these two methods: v On the 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. 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 the following items: v Displayed results include resources discovered by other IBM Systems Director users who are accessing the same management server to perform discoveries. So the Discovered Manageable Systems table displays results that might include additional resources that are not located at the target IP addresses or host names that you expect. v When you click New Discovery to run a new discovery while a previous discovery is still running, the Discovered Manageable Systems table does not include results for the previous discovery. To view results for the previous discovery, you must use the Discovery Jobs task or the Active and Scheduled Jobs task. After the discovery process completes, all the discovered manageable systems are displayed in the Discovered Manageable Systems table. The table maintains the information until you close the Systems Discovery page, at which time it is cleared.
149
Note: Any discovered manageable system also is listed in one or more groups on the Resource Explorer page.
Accessing a secured system with request access

Use the Request Access page to request access to a secured system if the management server to which you are connected has not yet authenticated to the system. You must be able to access the system before you can perform tasks or remotely access the system. Ensure that you have the correct authorization to access the secured system. Note: Agent access points are all access points that have an access type other than console. If certain types of agent access points (for example, CAS or IPC) exist on a resource, 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 be viewed or managed. For other types of agent access points on the secured resource, you have the option of using the Configure Access task to request access. Secured systems are displayed in IBM Systems Director Web interface with a padlock 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 status information are available. The Access attribute for each resource shows the current access status. You cannot request 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 the same user ID and password. 1. In IBM Systems Director Web interface, click Navigate Resources. 2. Navigate to the system that you want to access. 3. Right-click the system for which you want to request access and select Security > Request Access. Note: Alternatively, you can select Security > Configure Access and then click Request Access on the Configure Access page. 4. On the Request Access page, type the user ID and password of a user that belongs to the System group. Note: You can use the sudo utility to configure agentless managed systems running AIX or Linux so that they are accessible by a user without administrator privileges. 5. Click Request Access. Credentials are created and authenticated to the managed system in an attempt to access it. If the access request is successful, the access status for the managed system changes to OK. If the access status changes to Partial Access, then the access request was unsuccessful for at least one access point. Click Configure Access to see the list of
150
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 this procedure.
151
152
Chapter 6. Installing agents

Prepare your managed systems and environment for agent and subagent installation and then install Common Agent, Platform Agent, virtualization manager subagent, or IBM Systems Director z/VM manageability access point agent. When IBM Systems Director Server is updated to 6.2.1, the common agent that is installed on the same system with IBM Systems Director Server is updated to 6.2.1 as well. If the local common agent has been updated to 6.2.1 before IBM Systems Director 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 a managed resource has multiple IP addresses, specify which IP address Systems Director uses to manage the resource. To specify the IP address to use, you specify that the management server ignore (or exclude) the other IP addresses associated with the resource. For more information, see Excluding IP addresses. Related reference IBM Systems Director Agent Deployment Cookbook
Preparing a Common Agent managed system

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

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

Before installing Common Agent on AIX , make sure that your platform meets the applicable requirements.
153
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 an overwrite 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 and Platform Agent are installed when upgrading from a previous version of AIX if a previous version of the agent is already installed. Both are also installed when you perform an overwrite 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). 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 Agent on AIX that you can use for a fresh installation or to update an existing 6.1.x or 6.2.0 agent. You can use update manager to update an existing Common Agent installation to 6.2.1. You cannot use update manager to update an existing Platform Agent 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, as described in Hardware and software requirements. To verify the AIX operating system level, run the following command:
oslevel -s
The command should return a value such as 5300-09-00-nnn, where nnn is irrelevant. 2. Optional: Download updates for your system, if necessary. Download AIX operating system updates from the IBM Fix Central Web site. Note: Select Power or System p for the Product family and AIX for the Product. 3. Ensure that the following required openssl and openssh versions are installed: v openssl.base 0.9.8.4 or higher v if installed, openssh.base.server 4.5.0.5301 or higher There is a dependency between openssl and openssh versions. If openssl is not 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 deploy the agent to an agentless system from a server using the Agent Installation Wizard, openssh is required on the agentless system. However, the server installation does not enforce openssh installation.
154
4. Ensure that the following file sets that are required for and installed with Common Agent on AIX will not conflict with any other applications that are installed on your system: v sysmgt.cim.providers 1.2.9.0 v sysmgt.cim.smisproviders 1.2.2.0 v sysmgt.cimserver.pegasus 2.9.1 v 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 IP address lookups for loopback. For more information, see Agent install timeout due 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. By default, Common Agent requires ports 9510, 9514, and 9515 during installation and 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 is if you have a different version of the CAS agent installed, for example as part of 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 by running the following command:
/var/opt/tivoli/ep/runtime/agent/toolkit/bin/configure.sh -unmanaged -port not_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 Wizard

You can use the Agent Installation Wizard to install agent packages on managed systems. IBM Systems Director Server requires a number of agent packages that can be deployed to managed systems using the Agent Installation Wizard. Note: If you install IBM Systems Director Server 6.2.1 from the DVD media, the 6.2 agent packages are imported, unless you are installing from the AIX DVD media, in which case no agent packages are imported. If you install IBM Systems Director Server from the Web download file, no agent packages are imported for any operating system. So, regardless of the installation method that you use, you need to download the 6.2.1 agent packages separately. The imported agent packages are located in the dynamic group Agent Package Groups and can be accessed by clicking Release Management > Agents in the navigation area. You use the Agent Installation Wizard to select one of these agent packages to install and one or more systems on which to install the agent package. Then, the wizard creates an agent installation job that can run immediately or at a scheduled time. Complete the following steps to import the agent packages:
155
1. Download the remote agent packages from the IBM Systems Director Agents for Remote Deployment with Agent Installation wizard section of the IBM Systems 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 Director Server 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 Agent manually or Installing Platform Agent manually for instructions about how to 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 for remote deployment are provided on the media so that you can easily import them manually. 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 the Available list. Note: A subagent plugs-in to a base agent and provides additional capabilities to support IBM Systems Director plug-ins such as IBM Systems Director 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 or more agent packages might already be displayed in the Selected list. v The Agent Installation Wizard can install only one agent package at a time. If more than one agent package is displayed in the Selected list, you will not be able to advance to the Systems page. Click Next. the Agent Installation Wizard Systems page, complete the following steps: Select the managed systems on which you want to install the agent package in the Available list. Click Add. The selected systems are displayed in the Selected list. Notes: v Depending on how you started the Agent Installation Wizard, one or more systems might already be displayed in the Selected list. v Depending on the agent package being installed, some selected systems might not be valid targets for installation. The wizard checks the selected
c. 4. In a. b.
156
systems for some or all of the following criteria to ensure that the systems are valid targets for installing the selected agent package before allowing you to continue: operating system family operating system version operating system distribution operating system name server architecture c. Click Next. 5. In the Agent Installation Wizard Summary page, review the Selected Agents and Selected Systems lists to ensure that they are correct. v If the selections are not correct, click Back and make the necessary changes. v If the selections are correct, click Finish. After you click Finish, the Run - Install Agent window opens. 6. In the Run - Install Agent window, click the Schedule tab. On this page, you can choose to run the job immediately or schedule the job to run at a later time. a. A job name is required and the Name field provides a unique default name. To change the default name, type a job name in the field. b. To run the job immediately, click Run Now and go to step 7. Otherwise, click Schedule. c. In the Schedule list, select how frequently you want the job to run. The default setting is Once. Other values are Hourly, Daily, Weekly, Monthly, Yearly, or Custom. Also, you can specify whether to run the job on the weekend. d. Select the date and time to run the job for the first time. e. Select the time range for the job to repeat. 7. Click the Notification tab. On this page you can customize a notification that is sent by e-mail. a. Select from the available criteria to customize when the e-mail notification is sent. You can specify that the e-mail be sent when one of the following criteria is met: v When the job begins. v When the job 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 the number of systems on which the job had errors. Therefore, if the job runs on five systems, the job has errors on two systems, and you set the criterion threshold to 50%, the notification is not sent. v When the job receives any error. b. Type your e-mail address, e-mail server, and e-mail server port. Tip: You can provide only one e-mail address. 8. Click the Options tab. On this page you can select additional options for the job behavior. a. Select whether you want the job to run according to your management server's time or the target system's time. Tip: Make sure that you know the time and time zone to which the respective systems' clocks are set.
157
b. Select whether you want the job to fail if a system is offline or if you want the job to run when the system is online again. 9. Click OK to save the job. Click Cancel to exit from the Run window without saving the job. If the job is created successfully, a message is displayed on the page from which you started the Scheduler. If the job creation fails, a message is displayed in the Run window so that you can correct the job. The job created by the Agent Installation Wizard will transfer the agent self-extracting script and the agent response file into the 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 Agent install_root/SwDistPk After the files are copied, the installation file sets are extracted into the /tmp directory and installed. The files are then removed after a successful installation. You need to ensure that there is sufficient space on the target system to copy the self-extracting script and extract the file sets. Refer to the space requirements as specified in Hardware requirements for systems running Common Agent or Platform Agent. If the agent deployment completes with errors, check the log file for your target operating 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 provide to 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 the self-extracting script and the response file options. v For AIX server and agents, it is less space consuming to remotely install agents using NIM as explained in the IBM Systems Director Best Practices wiki page Installing IBM Systems Director Common Agent for AIX using NIM 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
Chapter 7. Updating IBM Systems Director

Use Update IBM Systems Director in the IBM Systems Director Web interface to automatically 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 Systems Director 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 updates needed by the IBM Systems Director Server are displayed in the table. 2. Optional: If your management server does not have an IPv4 connection to the Internet, you can download IBM Systems Director updates from www.ibm.com/support/fixcentral/ and then use update manager to import and install the updates. See Downloading IBM Systems Director updates without 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.
159
160
Chapter 8. Upgrading and migrating IBM Systems Director

You can upgrade and migrate information from earlier versions of IBM Systems Director and IBM Director. The method of migration that you use depends on the product versions from and to which you are migrating.
Database preparation considerations for upgrading and migrating to IBM Systems Director 6.2.x
Before upgrading and migrating any version of IBM Director or IBM Systems Director to IBM Systems Director 6.2.x, ensure that you properly prepare your system.
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 on many, 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 the management server and the database server. Database storage will consume the majority of the smsave data, so most of the disk space needs will fall on the database server and you will not need as much space on the management server. v If you are migrating any plug-ins, such as Active Energy Manager, along with IBM Systems Director. The presence of plug-in data will most likely greatly increase your storage needs. As a general rule, you can take the size of your current database, add 1 GB to it, and use that as your storage space requirement for the smsave data. See the documentation for your database server for instructions for determining its actual 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 IBM Systems Director 6.2, so ensure that you take the appropriate precautions for your 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 but not 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.
161
Note: Installing the newer client displaces the older client, which is needed to save the IBM Systems Director 6.1.x data. v If you are using an IBM DB2 9.1 database client, complete the following step for your 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. 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 server libraries even on 64-bit systems. IBM Systems Director 6.2 is 64-bit and 64-bit database libraries are used. Prior to migration on a 64-bit system, verify that your 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, the environment 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 Systems Director 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 after migration. Ensure that you know the database name, the administrator user ID and password, and the database server machine name that you used before and that they are still accessible. The IBM Systems Director 6.2 installer will use the same information to reconnect. If your database is on a remote server, ensure that you create a folder on that database server with permissions such that the IBM Systems Director smsave process has write access. See Migration to DB2 Version 9.5 in the IBM DB2 9.5 information center for further IBM DB2 migration considerations. If your database was configured to require approval of restore operations, you should disable that option. If you do not disable the approval requirement, the smrestore 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 the name of your IBM Systems Director database:
db2 get db cfg for db_name
v v
The output of this command includes lines for the following parameters: LOGRETAIN, LOGARCHMETH1, and LOGARCHMETH2. If any of these parameters are set to RECOVER or a state other than OFF, you must set the parameter to OFF to avoid 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, and log_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 SQL Server Express
If you are using Microsoft SQL Server or Microsoft SQL Server Express, ensure that you 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 installed Microsoft SQL Server or downloaded the jar file.
162
v You might need to log off of the operating system and log back on after extracting the JDBC 2.0 driver to make sure that all environment variables are set correctly. v The 32-bit and 64-bit database clients are both compatible with Microsoft SQL Server. 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 that they are still accessible. The IBM Systems Director 6.2 installer will use the same information to reconnect. v If your database is on a remote server, ensure that you create a folder on that database server with permissions such that the IBM Systems Director smsave process 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 server libraries even on 64-bit systems. IBM Systems Director 6.2 is 64-bit and 64-bit database libraries are used. Prior to migration on a 64-bit system, verify that your 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 environment variable 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.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 after migration. 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 that they are still accessible. The IBM Systems Director 6.2 installer will use the same information to reconnect. v If your database is on a remote server, ensure that you create a folder on that database server with permissions such that the IBM Systems Director smsave process has write access. On AIX and Linux, run chmod 777 on this directory so that 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.x

Use 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 prior versions of IBM Systems Director are installed. If a 6.1.x version is detected, user data for IBM Systems Director and plug-ins, such as Active Energy Manager and VMControl, can be automatically migrated. Attention: If your existing plug-in is not compatible with IBM Systems Director 6.2.1, you will be unable to migrate it with this process. You will need to instead install IBM Systems Director 6.2.1, obtain and install a compatible version of your plug-in, and then migrate your plug-in data. See Upgrading and migrating IBM Systems 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 extra steps. See Upgrading and migrating IBM Systems Director on the management server for further information. To upgrade and migrate to IBM Systems Director 6.2.1 from 6.1.x, complete the following 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 on the management server for full instructions for upgrading and migrating to IBM Systems Director 6.2 on each operating system. Then perform the next step. 2. Update to IBM Systems Director 6.2.1 using update manager. See "Updating IBM Systems Director" for instructions. Note: Dependent on how you updated to IBM Systems Director 6.2.1, the local platform 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 Platform Agent, refer to Upgrading the IBM Systems Director agents.
Upgrading and migrating to IBM Systems Director 6.2.1 from 6.2

Use this process to upgrade and migrate from IBM Systems Director 6.2 to IBM Systems Director 6.2.1. To upgrade and migrate to IBM Systems Director 6.2.1 from 6.2, complete the following 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 "Updating IBM Systems Director" for instructions.
Upgrading and migrating to IBM Systems Director from IBM Director 5.x
To migrate user information from IBM Director to IBM Systems Director 6.2, first upgrade and migrate to IBM Systems Director 6.1.x. You cannot directly migrate user information from IBM Director to IBM Systems Director 6.2. To migrate the information, first upgrade and migrate to IBM Systems Director 6.1.x. For more information, see Upgrading and migrating IBM Systems Director (http://publib.boulder.ibm.com/infocenter/director/v6r1x/topic/ director.upgrade_6.1/fqm0_t_upgrading_and_migrating.html) in the IBM Systems Director 6.1.x information center. To complete the upgrade and migration from IBM Director to IBM Systems Director 6.2, migrate the 6.1.x user information during the IBM Systems Director 6.2 installation process. For more information, see Upgrading and migrating to IBM Systems Director 6.2 from 6.1.x,
164
Upgrading and migrating IBM Systems Director plug-ins

When upgrading and migrating to IBM Systems Director 6.2, you need to keep in mind certain requirements for your specific plug-ins. You might need to implement various extra steps during the process depending on the version compatibility of your plug-in with IBM Systems Director 6.2. Use the information in this topic and in the documentation for your specific plug-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 the documentation for each plug-in, see the IBM Systems Director Web site at www.ibm.com/systems/management/director/plugins/. Keep in mind the following items when you upgrade and migrate to IBM Systems Director 6.2:
Service and Support Manager

If you attempt to upgrade and migrate using the smsave and smrestore migration scripts, you will lose all existing Service and Support Manager data, including saved problem and support file data. Therefore, instead upgrade and migrate through the IBM Systems Director installation path to ensure that this data carries over.
IBM Systems Director Network Control

IBM Systems Director Network Control V1.1 is not compatible with IBM Systems Director 6.2, but you can migrate an existing IBM Systems Director Network Control V1.1 configuration to V1.2.x. See the topic Migrating to IBM Systems Director Network Control V1.2.2. IBM Systems Director Network Control V1.2 can be used with IBM Systems Director 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 IBM Systems Director 6.2, but you can migrate existing IBM Systems Director VMControl resources to VMControl version 2.3. For information, see Migrating to VMControl 2.3. If you are currently managing Windows Server 2008, Enterprise, Standard, and Datacenter x64 Editions with Hyper-V role enabled, Release 2 environments with IBM Systems Director 6.2.0 and VMControl 2.3.0 and update to IBM Systems Director 6.2.1, you must update to VMControl 2.3.1. For information, see Updating IBM Systems Director VMControl.
Upgrading and migrating IBM Systems Director on the management server

After preparing your system, use the IBM Systems Director Server upgrade and migration procedure that is applicable for your operating system.
165
Upgrading and migrating IBM Systems Director Server on AIX

After preparing your system, you can upgrade and migrate IBM Systems Director Server on AIX by following the normal IBM Systems Director installation path and taking 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 two steps: 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 to IBM Systems Director Server 6.2. For more information, see smsave command and smrestore command. v Review the database preparation considerations. See Database preparation considerations 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 Director plug-ins and strictly adhere to any requirements that it lists in general or for your specific plug-in. You can upgrade and migrate IBM Systems Director Server on AIX from either installation media or from a downloaded installation package. Important: The IBM Systems Director Server and Common Agent installation packages for AIX are provided in English only.
Table 46. Installation options for IBM Systems Director Server on AIX Installation method DVD media Title or file name IBM Systems Director for AIX, V6.2.1 DVD Note: To obtain an image of the IBM Systems Director for AIX, V6.2.1 DVD, download the SysDir6_2_1_DVD_AIX.iso file. Attention: If you use DVD media to install IBM Systems Director Server, ensure that you allot an additional 1.5 GB of available space in the /opt file system to contain the agent packages that are copied from the DVD at the end of the server installation. The packages are copied to /opt/ibm/director/packaging/agent on the server. Installing IBM Systems Director Server from AIX 6.2.1 DVD media does not install the agents. This is an exception for 6.2.1. The SysDir6_2_1_Common_Agent_platform.jar files are provided in the agent subdirectory of the DVD media.
166
Table 46. Installation options for IBM Systems Director Server on AIX (continued) Installation method Downloaded installation package Title or file name SysDir6_2_Server_AIX.tar.gz (1.36GB) Attention: When downloading the installation package file to your AIX server, you must first run the following command to increase the default file size limit: ulimit -f 4194302
Upgrading and migrating IBM Systems Director Server 6.2.1 using the dirinstall.server script is the only supported method. To upgrade IBM Systems Director Server, log in as the root user and complete the following steps: Tip: You can find the installation logs for this process in /var/log/dirinst.log and /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 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 Director Downloads Web Site at www.ibm.com/systems/management/director/ downloads/. c. To unzip and extract the contents of the installation package, type the following 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 the following command and press Enter:
cd /install_files/
where install_files is the path to the extracted installation files. DVD media: To start the upgrade and migration 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:
where dev is the specific device file for the block device and mnt is the mount point of the drive.
167
c. To change to the directory in which the installation script is located, type the 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 your installation method: v Web download: install_root/InstallMigrationTools/dbconfig.sh, where install_root represents the root directory of your IBM Systems Director installation. v DVD: /dvd_mnt/server/InstallMigrationTools/dbconfig.sh, where dvd_mnt represents the directory to which you mounted the IBM Systems Director DVD. You are prompted to enter the database administrator userid and password. Tip: The database user ID and password are not the same as the database Admin user name and password. The database Admin user name and password are collected from dbconfig.sh before you run the installer. If you forget and run the installer without dbconfig.sh, you will get a message telling you to run dbconfig.sh. 3. To upgrade IBM Systems Director Server, from within the directory in which the installation script is located, type one of the following commands and press Enter: 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 the database client to be used by the upgraded IBM Systems Director. This option is usually needed when migrating to a 64-bit installation or when moving to a newer version of the database client. where saved_database_path specifies the path to the directory where database data is saved during an IBM Systems Director migration. This option is required if the database is remote (on a system other than the system where IBM Systems Director is being installed). This option is ignored if the -g option is specified. If a remote Windows database server is used, do not set this path with a space in it. where saved_data_path specifies the path to the directory where data is saved during an IBM Systems Director migration. This option is ignored if the -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
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 the response file or see the IBM Systems Director Best Practices Wiki. A sample response file named dirserv.rsp resides in the same directory as the dirinstall.server installer. If you wish to use the default for any value in the response file, comment out that value with a # symbol at the beginning of the line instead of leaving 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 specifying the remote Windows directory name. For example, use C:\\foldername instead of C:\foldername. For more options, run ./dirinstall.server -?, see dirinstall.server, or see 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 the management 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 you upgraded from IBM Systems Director Server 6.1.x, the only agent deployment packages that are available by default are all applicable 6.2 agent packages (if you upgraded using the DVD media) or only the 6.2 subagent packages (if you upgraded using a downloaded installation package). Any agent deployment packages that were installed by default in 6.1.x or that you imported through the Agent Import task are no longer available. Therefore, complete the following 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 download them 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 to import and click OK. After a successful import, the 6.1.x packages will appear in the IBM Systems Director Web interface and will be ready for distribution.
169
6. Verify that your library path environment variables are still set correctly, and fix any that are not correct. The LIBPATH environment variable must point to the 64-bit library folder, for example database_client_root\lib or database_client_root\lib64. 7. If you used the DVD for installation, complete the following steps to unmount the drive and remove the DVD: a. Type cd / and press Enter. b. Type the following command and press Enter:
umount /mnt
where mnt is the mount point of the drive. c. Remove the DVD from the drive. 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 affect cimserver. v /tmp/cimlistener_start.conf Note: This file is deleted when cimlistener shuts down. This does not affect cimlistener. v /tmp/elasocket_cimv2 v /tmp/dpi_socket After you have upgraded the agent and server packages, you can use update manager to update to the latest version of IBM Systems Director, if updates are available. See Updating IBM Systems Director for instructions. Note: Before performing an update, you will need to understand disk space requirements. For information on disk space requirements for updates, see Determining disk space requirements for applying updates or the IBM Systems Director Best Practices Wiki. Related reference IBM Systems Director Downloads IBM Systems Director Best Practices Wiki
Upgrading or updating the IBM Systems Director agents

After upgrading IBM Systems Director Server, you can upgrade or update the IBM Systems Director agents. When IBM Systems Director Server is updated to 6.2.1, the common agent that is installed on the same system with IBM Systems Director Server is updated to 6.2.1 as well. If the local common agent has been updated to 6.2.1 before IBM Systems Director 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
v A Platform Agent update is not part of the IBM Systems Director 6.2.1 update package for which you use update manager. v Before using update manager to update Platform Agent to 6.2.1 from 5.20.x or 6.1.x, see Applicability of Platform Agent for information about conditions that might cause the installation of the update to fail. You can also see IBM Systems Director Pre-Install Utility for information about running the IBM Systems Director Pre-Install Utility on the agent to obtain a compatibility report before attempting the installation of the update. If you still use update manager to update Common Agent or Platform Agent and the update process fails or logs an error message, review the installation and uninstallation logs for each of the affected agents and then instead use the manual installation process for those agents. v When you update Common Agent or Platform Agent from 5.20.x to 6.2.1 on a Red Hat Enterprise Linux system, the ports that are used on the Platform Agent are changed. You must rediscover and obtain access to the agent again before using it. Choose the appropriate method to upgrade or update your agent based on your agent type and operating system: v Use the following methods to upgrade or update Common Agent.
Operating system AIX Linux on Power Systems Method to use to update or upgrade Common Agent Install Common Agent 6.2.1. See Installing Common Agent for more information. Update Common Agent using update manager. See Updating systems for more information. Update Common Agent using update manager. See Updating systems for more information. Update Common Agent using update manager. See Updating systems for more information. Update Common Agent using update manager. See Updating systems for more information.
Linux for System x and x86-based systems
Linux for System z
Windows
v Use the following methods to upgrade or update Platform Agent.

Operating system AIX Method to use to update or upgrade Platform Agent Install Common Agent 6.2.1. (Platform Agent is updated as part of the Common Agent update.) See Installing Common Agent for more information. Install Platform Agent 6.2.1. See Installing Platform Agent for more information. Update Platform Agent using update manager. See Updating systems for more information. Install Platform Agent 6.2.1. See Installing Platform Agent for more information.
Linux on Power Systems Linux for System x and x86-based systems
Linux for System z
171
Operating system Windows
Method to use to update or upgrade Platform Agent Update Platform Agent using update manager. See Updating systems for more information.
172
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
173
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation MW9A/050 5600 Cottle Road San Jose, CA 95193 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common
174
law trademarks in other countries. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/ copytrade.shtml. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others.
Notices
175
176
Printed in USA
GI11-8709-06

6.2.1.installation Aix

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

6.2.1.installation Aix

Uploaded by

Copyright:

Available Formats

IBM Systems Director

IBM Systems Director

Chapter 2. Planning for IBM Systems Director . . . . . . . . . . . . . . 17

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

Copyright IBM Corp. 1999, 2010

126 127 128 129 130 131 132 133 134

Chapter 6. Installing agents . . . . . 153

Chapter 4. Preparing agentless managed systems . . . . . . . . . 137

Chapter 5. Discovering systems and collecting inventory data . . . . . . 145

About this publication

Conventions and terminology

Publications and related information

Information centers and topic collections

White papers and briefs

IBM Redbooks publications

How to send your comments

Checklist: Installing IBM Systems Director Server on AIX

Copyright IBM Corp. 1999, 2010

Checklist: Installing agents on AIX

Update the agents. __ 1. Update the agents (159).

Copyright IBM Corp. 1999, 2010

Chapter 1. IBM Systems Director technical overview

IBM Systems Director components

Browser system - no IBM Systems Director Ccode installed

Platform managed systems - Platform Agent installed on each

Common managed systems - Common Agent installed on each

Figure 1. Software in an IBM Systems Director environment

Agentless managed systems

Chapter 1. IBM Systems Director technical overview

Manageable resource types

Manageable systems and system types

Base function and extensible plug-ins

Remote access manager

Chapter 1. IBM Systems Director technical overview

IBM BladeCenter and System x management

IBM System z management

IBM Power Systems management

IBM System Storage management

Additional IBM Systems Director plug-ins

Active Energy Manager plug-in

Chapter 1. IBM Systems Director technical overview

BladeCenter Open Fabric Manager plug-in

Service and Support Manager plug-in

IBM Systems Director Network Control plug-in

IBM Systems Director Storage Control 4.2.1

IBM Systems Director VMControl plug-in

IBM PowerVM Workload Partition Manager for AIX plug-in

Chapter 2. Planning for IBM Systems Director

Hardware and software requirements

Hardware requirements for IBM Systems Director

Hardware requirements for running IBM Systems Director Server

Copyright IBM Corp. 1999, 2010

/opt Web download file (SysDir6_2_1_DVD_AIX.iso)

Hardware requirements for systems running Common Agent or Platform Agent

IBM Power systems running AIX

Determining disk space requirements for applying updates

Supported IBM systems and products

IBM BladeCenter products

IBM BladeCenter chassis

IBM BladeCenter blade servers

Supported network devices

Task support for network management