Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

Version 6.3

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems
Version 6.3

Note Before using this information and the product it supports, read the information in Notices on page 27.

Copyright IBM Corporation 1999, 2012. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents
About this publication . . . . . . . . v
Conventions and terminology . . . . . . . . v Publications and related information . . . . . . v Web resources . . . . . . . . . . . . . viii How to send your comments . . . . . . . . ix Installing Platform Agent on IBM i . . Verifying the successful installation of an IBM Systems Director agent . . . . . . . . . . . 17 . 17

Chapter 2. Preparing agentless managed systems . . . . . . . . . . 19

Preparing to manage an IBM BladeCenter chassis using IBM Systems Director Server on a non-blade server . . . . . . . . . . . . . . . Preparing to manage an IBM BladeCenter chassis using IBM Systems Director Server on a blade server . . . . . . . . . . . . . . . Preparing Hardware Management Console devices for discovery with IBM Systems Director . . . Preparing IBM i managed systems. . . . . . . 19

Checklist: Installing agents . . . . . . xi Chapter 1. Installing agents . . . . . . 1

Installing Common Agent . . . . . . . . . . 2 Preparing for a Common Agent managed system 2 Preparing to install Common Agent on IBM i . 2 Installing agents using the Agent Installation Wizard . . . . . . . . . . . . . . . 5 Installing Common Agent manually . . . . . 8 Installing Common Agent on IBM i. . . . . 8 Installing Platform Agent . . . . . . . . . . 11 Preparing for a Platform Agent managed system 12 Preparing to install Platform Agent on IBM i 12 Installing agents using the Agent Installation Wizard . . . . . . . . . . . . . . . 13 Installing Platform Agent manually . . . . . 16

. 21 . 22 . 23

Chapter 3. Uninstalling . . . . . . . . 25
Uninstalling Common Agent 6.x on IBM i . . . . 25

Notices . . . . . . . . . . . . . . 27
Trademarks . . . . . . . . . . . . . . 29

Copyright IBM Corp. 1999, 2012

iii

iv

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

About this publication

This publication provides information about installing IBM Systems Director agents for the first time. It also covers the following topics: v Preparing the managed system for an agent v Preparing agentless managed systems v Uninstalling If you are using a printed version of this PDF, you might consider printing the following related PDFs, as relevant to your tasks: v Planning for IBM Systems Director Server in your environment v Upgrading and migrating IBM Systems Director agents v Systems management guide You can access additional information and PDFs from the IBM Systems Director information center Web site at publib.boulder.ibm.com/infocenter/director/pubs/ 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 publib.boulder.ibm.com/infocenter/director/pubs/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 http://publib.boulder.ibm.com/infocenter/director/pubs/topic/extensions/ extensionparent.html
Copyright IBM Corp. 1999, 2012

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://publib.boulder.ibm.com/infocenter/director/devsdk/index.jsp 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
Release Notes 6.3.2 Provides an easy reference to planning, install and troubleshooting information for IBM Systems Director IBM Systems Director Planning Guide Provides planning information, including hardware requirements for running IBM Systems Director components, supported IBM Systems Director hardware, operating systems, databases, and workgroup and enterprise systems-management software. PDF files for installing IBM Systems Director Server Provides detailed instructions to prepare for, install, and configure the IBM Systems Director Server. PDF files for installing IBM Systems Director agents Provides detailed instructions to prepare for and install IBM Systems Director agents on your managed systems, as well as, prepare for agentless managed systems. PDF files for upgrading and migrating IBM Systems Director Server Provides detailed instructions to upgrade and migrate the IBM Systems Director Server. PDF files for upgrading and migrating IBM Systems Director agents Provides detailed instructions to upgrade and migrate IBM Systems Director agents. IBM Systems Director Systems Management Guide Provides detailed instructions for using the Web interface and managing systems and resources in your environment. IBM Systems Director Troubleshooting Guide Provides information about problems and how to solve them, and strategies for troubleshooting common problems. IBM Systems Director Events Reference Provides information about IBM Systems Director events, including the event type, description, severity, and extended details. IBM Systems Director Commands Reference Provides detailed information about the systems management

vi

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

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. 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 Performance Tuning and Scaling Guide for IBM Systems Director 6.3 Hardware requirements for running IBM Systems Director Server 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

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
See Searching knowledge bases for more resources for further information about IBM Systems Director.

About this publication

vii

Web resources
Listed here are the websites and information center topics that relate to IBM Systems Director.

Websites
v IBM Systems Director www.ibm.com/systems/management/director/ View the IBM Systems Director website 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 website 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 website on ibm.com which provides links to product documentation, Redbooks, redpapers, white papers, and learning modules that are 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 website on ibm.com which provides more information about IBM Systems Director upward integration modules that are 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 website to learn about IBM Systems server and storage products. v IBM ServerProven www.ibm.com/servers/eserver/serverproven/compat/us/ View the IBM ServerProven website 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 Forum (System x, System z, Power Systems) www.ibm.com/developerworks/forums/forum.jspa?forumID=759

viii

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

View the IBM Systems Director Forum website on ibm.com to discuss product-related issues that pertain to IBM Systems Director, IBM Systems Director UIMs, and IBM Systems Director extensions. This website includes a link for obtaining the forum by using a Rich Site Summary (RSS) feed. v IBM Systems Director 6.x SDK Forum www.ibm.com/developerworks/forums/forum.jspa?forumID=1852&start=0 View the IBM Systems Director 6.x SDK Forum website to discuss issues that pertain to the IBM Systems Director Software Development Kit (SDK). This website includes a link for obtaining the forum by using a Rich Site Summary (RSS) feed. v IBM Systems Forums www.ibm.com/developerworks/forums/dw_esforums.jsp View the IBM Systems Forums website on ibm.com to learn about various forums that are available to discuss technology-related and product-related issues that pertain to IBM Systems hardware and software products. This website includes a link for obtaining the forum by 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 publib.boulder.ibm.com/infocenter/director/pubs/index.jsp. There you will find the feedback page where you can enter and submit comments.

About this publication

ix

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

Checklist: Installing agents

Use this checklist to guide you through the installation process. 1 Prepare your managed systems. __ 1. Prepare systems for Platform Agent (12). __ 2. Prepare systems for Common Agent (2). __ 3. If relevant, prepare any agentless managed systems for discovery and management by IBM Systems Director (19). Install the agents. __ 1. Use the Agent Installation Wizard to deploy agent packages to your managed systems (5).

Copyright IBM Corp. 1999, 2012

xi

xii

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

Chapter 1. Installing agents

Prepare your managed systems and environment for agent and subagent installation and then install Common Agent, Platform Agent, or IBM z/VM Manageability Access Point Agent. IBM Systems Director Server must be updated to 6.3.2 before, or at the same time as, the agents that are installed on the management server are updated to 6.3.2. If you attempt to update a local agent to 6.3.2 before updating IBM Systems Director Server, then the IBM Systems Director Server update to 6.3.2 fails. Use the following flowchart as a guide through the installation process for agents.

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.

Copyright IBM Corp. 1999, 2012

Note: For more information about using the Web interface, see Publications and related information to access the Systems Management guide. Related tasks: Choosing the level of agent capabilities to deploy on managed systems Updating Systems Director Excluding IP addresses Installing VMControl agents and subagents Related reference: Systems Director Agent Deployment Cookbook

Installing Common Agent

Prepare your systems and environment for installing Common Agent. Then, use the Agent Installation wizard, or alternatively, use the manual instructions, to install Common Agent. Important: v Installation of IBM Systems Director installs IBM Systems Director Server, Common Agent, and Platform Agent all together as a bundle. Therefore, it is not necessary to separately install Common Agent or Platform Agent on the management server after installing IBM Systems Director Server. v Ensure that the system clocks on the systems that contain IBM Systems Director Server and Common Agent remain synchronized. Related tasks: Running the Pre-Installation Utility

Preparing for 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. Related reference: Hardware requirements for systems running Common Agent or Platform Agent

Preparing to install Common Agent on IBM i

Before installing Common Agent on IBM i (formerly i5/OS), there are several items to consider, such as the type of media on which the installation files are saved, the user profile that is used to install IBM Systems Director, and the additional software that might be required.

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

For more information about IBM i, see the IBM i Information Center at http://publib.boulder.ibm.com/eserver/ibmi.html. Review the following information and complete the necessary steps to prepare your system for installation: v Ensure that your system meets the hardware and software requirements for installation, as described in Hardware and software requirements. v Ensure that any agentless managed systems are prepared for discovery, as described in Preparing agentless managed systems. v If you want to use IBM Systems Director Server on an IBM Power system to manage a heterogeneous environment, you must install the applicable IBM Systems Director Common Agent or Platform Agent package on each IBM platform that you want to manage. You can obtain these versions of Common Agent and Platform Agent from the IBM Systems Director support Web site at www.ibm.com/systems/ management/director/. Note: IBM i Platform Agent support is provided with IBM i Licensed Program Product 5770UME V1R3 (IBM i 7.1 and 6.1) or with 5722UME V1R2M0 (IBM i 6.1 and 5.4). v Ensure that your user profile has *ALLOBJ and *SECADM special authorities. Note: Common Agent will use ports 29510 and 29511. v Ensure that the following products and options are installed on the IBM i server on which you plan to install IBM Systems Director. These products and options are required to successfully install and securely run IBM Systems Director.
Table 1. IBM i products and options required for IBM Systems Director Products, options, or fix IDs IBM i 7.1 product number Latest group PTF for IBM HTTP Server for IBM i group PTF SF99368 IBM i 6.1 product number group PTF SF99115 5770UME V1R3M0 Note: PTFs SI41685 and SI41540 are required. 5761DG1 5761SS1 option 1 5761SS1 option 3 5761SS1 option 21 5761TC1

IBM Universal Manageability 5770UME V1R3M0 Enablement for IBM i Note: PTFs SI41685 and SI41540 are required. IBM HTTP Server for IBM i OS/400 - Extended Base Support Extended Base Directory Support Extended NLS Support

5770DG1 5770SS1 option 1 5770SS1 option 3 5770SS1 option 21

TCP/IP Connectivity Utilities 5770TC1 for Power Systems Note: TCP must be configured correctly or IBM Systems Director might not start. See IBM Systems Director Fails to Start on the IBM i Support Web site for a short description of common configuration problems. Java SE 6 32-bit Qshell 5761JV1 option 11 5770SS1 option 30

5761JV1 option 11 5761SS1 option 30

Chapter 1. Installing agents

Table 1. IBM i products and options required for IBM Systems Director (continued) Products, options, or fix IDs IBM i 7.1 product number Digital Certificate Manager OpenSSH 5770SS1 option 34 IBM i 6.1 product number 5761SS1 option 34

5733SC1 V7R1M0 *BASE and 5733SC1 V6R1M0 *BASE and option 1 Option 1

v Ensure that the Integrated File System (IFS) directory /InstallShield is accessible on the IBM i server on which you plan to install IBM Systems Director. Also, if the /InstallShield directory is linked to a directory in an Independent Auxiliary Storage Pool (IASP), ensure that that IASP is active during the installation. v Ensure that you have installed the latest cumulative PTF packages or Group PTFs on the Power Systems on which you plan to install IBM Systems Director. v If IBM Systems Director Server 5.20.x is installed on IBM i 6.1, you must uninstall it before you install the Common Agent. Complete the following steps to check if IBM Systems Director Server is installed: 1. From a command prompt, type GO LICPGM and press Enter. 2. Select option 10, Display installed licensed programs, and review the list of installed programs. If installed, IBM Systems Director Server is displayed in the list as one of the following entries (depending on the version):
5722DR1 *BASE IBM DIRECTOR 5733VE1 30 5050 IBM Director Multiplatform, 4.2.0

If IBM Systems Director Server 5.20.x is installed: Uninstall the existing IBM Systems Director Server If you choose this option, complete the following steps before uninstalling IBM Systems Director Server 5.20.x: Run the twgsave command to save the IBM Systems Director persistent data. Ensure that IBM Systems Director Server 5.20.x is not providing the support required for IBM i iSCSI attached devices. Otherwise, when IBM Systems Director Server 5.20.x is removed, the support provided by IBM Systems Director Server for iSCSI devices will go away and those devices will become unusable. Remove IBM Systems Director Server 5.20.x only when you are sure that another solution is in place. Plan an alternate method for collecting performance data across partitions if you are currently using IBM Performance Management to do so. IBM Systems Director Server 6.x offers different methods for collecting information, so be aware that what and how data is collected will change when IBM Systems Director Server 5.20.x is uninstalled, and plan which method you will use in place of the function provided by IBM Systems Director Server 5.20.x. Use option 12 from the LICPGM menu to uninstall IBM Systems Director Server 5.20.x on IBM i. v If you plan to use IBM Systems Director to monitor SNMP devices in your IBM Power environment, ensure you have completed the necessary configuration tasks for IBM Power and SNMP devices. See the "Networking" topic in the IBM Power Systems and IBM i Information Center for more information.

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

Related tasks: Installing agents using the Agent Installation Wizard Related reference: Hardware and software requirements Supported operating systems IBM Systems Director Web page IBM Director Fails to Start

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.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. Important: Ensure that the following requirements are met to enable use of the Agent Installation Wizard to install and update agents: v The root user account was used to initially request access to the managed system. v IBM Systems Director Server on non-Windows systems has SSH, and a successful SSH connection exists in both directions between the server and the agent. v IBM Systems Director Server on Windows systems has DCOM, and a successful DCOM connection exists in both directions between the server and the agent. Complete the following steps to import the agent packages: 1. Download the remote agent packages from http://www.ibm.com/systems/ software/director/downloads/agents.html. Ensure that you choose packages from the Remote Deployment using Agent Installation wizard section. 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. 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 Home page, click Additional Setup. Then, click Install agents on systems > Deploy Agents. v Right-click an agent package or a managed system and select Release Management > Install Agent.
Chapter 1. Installing agents

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, the Selected list might already contain one or more agent packages. v The Agent Installation Wizard can install only one agent package at a time. If more than one agent package is displayed in the Selected list, you will not be able to advance to the Systems page. c. Click Next. 4. In the Agent Installation Wizard Systems page, complete the following steps: a. Select the managed systems on which you want to install the agent package in the Available list. b. Click Add. The selected systems are displayed in the Selected list. Notes: v Depending on how you started the Agent Installation Wizard, the Selected list might already contain one or more systems. v Depending on the agent package that you are installing, some selected systems are potentially not valid targets for installation. The wizard checks the selected systems for some or all of the following criteria to ensure that the systems are valid targets 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 on page 7. Otherwise, click Schedule.

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

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 mail notification is sent. You can specify that the 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 mail address, mail server, and mail server port. Tip: You can provide only one mail address. 8. Click the Options tab. On this page you can select additional options for the job behavior. a. Select whether you want the job to run according to your management server's time or the target system's time. Tip: Make sure that you know the time and time zone to which the respective systems' clocks are set. b. Select whether you want the job to fail if a system is offline or if you want the job to run when the system is online again. 9. Click OK to save the job. Click Cancel to exit from the Launch Job 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 Launch Job 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

Chapter 1. Installing agents

space requirements as specified in Hardware requirements for systems running Common Agent or Platform Agent. You can view the status of the agent installation job by clicking Task Management > Active and Scheduled Jobs. If you installed Platform Agent on Linux, enable SNMP Access and Trap Forwarding by installing and configuring Net-SNMP. For instructions and information, see http://www.net-snmp.org/.

Installing Common Agent manually

You can use these manual instructions to install Common Agent on a managed system. These manual instructions provide an alternative method of installation to using the Agent Installation Wizard. Important: v Installation of IBM Systems Director installs IBM Systems Director Server, Common Agent, and Platform Agent all together as a bundle. Therefore, it is not necessary to separately install Common Agent or Platform Agent on the management server after installing IBM Systems Director Server. v Ensure that the system clocks on the systems that contain IBM Systems Director Server and Common Agent remain synchronized. Related tasks: Preparing a Common Agent managed system

Installing Common Agent on IBM i

After preparing your system, you can install Common Agent on a system that is running IBM i (formerly i5/OS) (V6R1 or later) by using a downloaded Agent Installation Wizard package or by manually installing a downloaded agent installation package. Important: v Ensure that the system clocks on the systems that contain IBM Systems Director Server and Common Agent remain synchronized. When installing IBM Systems Director Server from a Web download, no agents are imported and the agent packages are not included. So, you must use an Agent Installation Wizard package or a manual agent installation package, either one downloaded from the IBM Systems Director Web site, to install Common Agent on IBM i.
Table 2. Installation options for Common Agent on IBM i Installation method Downloaded installation package Title or file name SysDir6_3_2_Common_Agent_IBM_i.zip (agent package for manual installation) SysDir6_3_2_Common_Agent_IBM_i.jar (agent package for Agent Installation Wizard installation)

If you are upgrading from a previous version of Common Agent, migration of the product is processed automatically during installation of the new Common Agent version.

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

Note: Common Agent is installed by default in unmanaged mode. When IBM Systems Director Server discovers an unmanaged agent, the agent becomes managed after requesting access. However, if you want the agent to start out in managed mode, for example because IBM Systems Director Server is configured with more than one agent manager and you want to choose the agent manager with which the agent associates, you can do so using one of the following two methods: Install the agent in managed mode To install the agent in managed mode, complete the following steps to modify the i5OSCASInstall.rsp file that is contained in the installation package and customize the installation: 1. Open an ASCII text editor and modify the installation settings in the i5OSCASInstall.rsp file. The following lines are used in the file to register common agent services with an agent manager: v -W CASInstall.UnmanagedAgent="false" Default value is true. Change to false when making the resource managed. Note: When set to false, you must also set both CASInstall.AgentManagerHostname and CASInstallRegistrationPassword. v # -W CASInstall.AgentManagerHostname="1.23.456.789" Remove the comment indicator (the # at the beginning of the line) and replace 1.23.456.789 with the host name or IP address of the agent manager.If the agent is installed in a network address translation environment, set this parameter to ensure that the agent has the correct IP address to contact the agent manager. v # -W CASInstall.RegistrationPassword="dummypwd" Remove the comment indicator (the # at the beginning of the line) and replace dummypwd with the password used for registering with the agent manager. 2. Save the modified response file. Configure the agent for managed mode after installation To configure the agent for managed mode after installation, run the following configure.sh command that is installed in /www/cas/lwi/ runtime/agent/toolkit/bin:
/www/cas/lwi/runtime/agent/toolkit/bin/configure.sh -amhost active_am_IP_address -passwd active_agent_registration_pw -force

Tip: You can complete the following steps to edit the /www/cas/lwi/ runtime/agent/config/endpoint.properties file to return the agent to unmanaged mode: 1. Stop the agent. 2. Edit the endpoint.properties file and set the following values:
unmanagedAgent=true CatalogueService.Host=localhost

3. Start the agent. Log in as the root user and complete the following steps to install Common Agent on IBM i: 1. Use one of the following two methods to install Common Agent on IBM i:

Chapter 1. Installing agents

Install using an Agent Installation Wizard package To start the installation using an Agent Installation Wizard package, complete the following steps: a. On a system that can connect to the IBM i system, go to the IBM Systems Director Web site at www.ibm.com/systems/management/director/ and download the Agent Installation Wizard package for all operating systems other than the server operating system. b. Import the Agent Installation Wizard package into IBM Systems Director. This enables IBM Systems Director to deploy the agent. Install manually using an agent installation package To start the manual installation, complete the following steps: a. Download the agent installation package from the IBM Systems Director Web site. b. Extract the agent package into a directory, for example /iCAS, in the Integrated File System on the IBM i system. For example, issue the following command within the directory that contains the installation package:
jar -xvf SysDir6_3_2_Common_Agent_IBM_i.zip

c. Start the QSHELL environment and navigate to the directory into which you extracted the agent package. For example:
cd /iCAS

d. Issue the following command to run installAgent.sh:

./installAgent.sh

e. If prompted, provide any information requested by the command, clicking Enter after every answer, until you have completed the installation. Note: You might not receive any prompts. In either case, the installation will proceed without any status indicators. f. Wait until the task completes and the QSHELL prompt (>) is shown, then issue F3 to exit QSHELL. 2. Issue the following commands to restart the IBM i Common Agent to make available all the functions that were installed:
ENDTCPSVR SERVER(*HTTP) HTTPSVR(CAS) STRTCPSVR SERVER(*HTTP) HTTPSVR(CAS)

To ensure full functionality of your new Common Agent instance, discover it with IBM Systems Director Server. Use the following commands to manage the IBM i Common Agent, which is an IBM i TCP server. v To manually start Common Agent, type the following command on an IBM i command line and press Enter:
STRTCPSVR SERVER(*HTTP) HTTPSVR(CAS)

To manually stop Common Agent, type the following command on an IBM i command line and press Enter:
ENDTCPSVR SERVER(*HTTP) HTTPSVR(CAS)

10

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

Related tasks: Preparing to install Common Agent on i Importing agent packages Upgrading and migrating agents Restarting Common Agent Related reference: Systems Director Web page Related information: Exchanging information with IBM

Installing Platform Agent

Prepare your systems and environment for installing Platform Agent. Then, use the Agent Installation wizard, or alternatively, use the manual instructions, to install Platform Agent. Important: v Installation of IBM Systems Director installs IBM Systems Director Server, Common Agent (when applicable), and Platform Agent all together. Therefore, it is not necessary to separately install Common Agent or Platform Agent on the management server after installing IBM Systems Director Server. In most cases, any IBM Systems Director tasks requiring Common Agent or Platform Agent will be performed for systems with IBM Systems Director Server installed. v The IBM i Platform Agent is provided with the IBM i Licensed Program Product IBM Universal Manageability Enablement for IBM i (5722-UME). Refer to the IBM i documentation for details. v Ensure that the system clocks on systems that contain IBM Systems Director Server and Platform Agent remain synchronized. v If you have BMC, IMM, or IMM2 service processors, use Platform Agent 6.1.1 or later to help ensure full functionality and support. v If you have RSA service processors, use IBM Director Core Services 5.20.x to help ensure full functionality and support. If you do decide to use Platform Agent 6.3.2, you must first uninstall IBM Director Core Services 5.20.x before installing Platform Agent 6.3.2. Restriction: Platform Agent 6.3.2 will block updates on IBM Director Core Services 5.20.x systems and RSA service processors. 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. v Platform Agent 6.1.1 and later uses 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 Platform Agent systems. v See Installing and uninstalling KVM Platform Agent for considerations regarding the use of Red Hat Enterprise Linux with Linux Kernel-based Virtual Machine (KVM).

Chapter 1. Installing agents

11

Note: If you are upgrading agents manually on a previously discovered endpoint, you must discover the endpoint again after the upgrade. Discovering the endpoint again allows the correct functionality to be reflected in IBM Systems Director. For example if you are upgrading an endpoint from Agentless managed system to Platform Agent through the manual agent installation script, you must then discover the endpoint again with IBM Systems Director. Related tasks: Running the Pre-Installation Utility Binding Platform Agent to specific IP addresses Installing and uninstalling KVM Platform Agent

Preparing for a Platform Agent managed system

Before installing Platform Agent on a managed system make sure that the requirements that are applicable to your system have been met. Complete the following steps on each system to be managed with Platform Agent: Set the clock on the managed system to match the time of the management server. If the managed system time is earlier than that of the management server, the management server will be unable to unlock the managed system. To avoid the problem of system-time mismatch, you can configure managed systems and the management server to synchronize their clocks using a common network time protocol (NTP) server. Related reference: RedHat chkconfig bug fix

Preparing to install Platform Agent on IBM i

Before installing Platform Agent on IBM i (formerly i5/OS), ensure that your platform meets the applicable requirements. Platform Agent support for IBM i (formerly i5/OS) is provided with the IBM Universal Manageability Enablement for IBM i Licensed Program Product that ships with the base operating system. For more information about IBM i, see the IBM i Information Center at http://publib.boulder.ibm.com/eserver/ibmi.html. Review the following information and complete the necessary steps to prepare your system for installation: v Ensure that your system meets the hardware and software requirements for installation, as described in Hardware and software requirements. v Ensure that any agentless managed systems are prepared for discovery, as described in Preparing agentless managed systems. v Ensure that the SLP service, which is provided with IBM i, is installed on the system. v Because the IBM i Platform Agent is provided by an IBM i Licensed Program Product (LPP), ensure that the correct version of the IBM Universal Manageability Enablement for IBM i (5770-UME) LPP is installed: IBM i 7.1 and IBM i 6.1 (formerly i5/OS, Version 6 Release 1) V1R3 of the IBM Universal Manageability Enablement for IBM i (5770-UME) LPP

12

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

IBM i 5.4 (formerly i5/OS, Version 5 Release 4) V1R2 of the IBM Universal Manageability Enablement for IBM i (5770-UME) LPP Related tasks: Installing the SLP Service Related reference: Hardware and software requirements Supported operating systems Service and productivity tools

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.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. Important: Ensure that the following requirements are met to enable use of the Agent Installation Wizard to install and update agents: v The root user account was used to initially request access to the managed system. v IBM Systems Director Server on non-Windows systems has SSH, and a successful SSH connection exists in both directions between the server and the agent. v IBM Systems Director Server on Windows systems has DCOM, and a successful DCOM connection exists in both directions between the server and the agent. Complete the following steps to import the agent packages: 1. Download the remote agent packages from http://www.ibm.com/systems/ software/director/downloads/agents.html. Ensure that you choose packages from the Remote Deployment using Agent Installation wizard section. 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. 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 Home page, click Additional Setup. Then, click Install agents on systems > Deploy Agents.

Chapter 1. Installing agents

13

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, the Selected list might already contain one or more agent packages. 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.

c. 4. In a. b.

Notes: v Depending on how you started the Agent Installation Wizard, the Selected list might already contain one or more systems. v Depending on the agent package that you are installing, some selected systems are potentially not valid targets for installation. The wizard checks the selected systems for some or all of the following criteria to ensure that the systems are valid targets 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 on page 7. Otherwise, click Schedule.

14

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

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 mail notification is sent. You can specify that the 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 mail address, mail server, and mail server port. Tip: You can provide only one mail address. 8. Click the Options tab. On this page you can select additional options for the job behavior. a. Select whether you want the job to run according to your management server's time or the target system's time. Tip: Make sure that you know the time and time zone to which the respective systems' clocks are set. b. Select whether you want the job to fail if a system is offline or if you want the job to run when the system is online again. 9. Click OK to save the job. Click Cancel to exit from the Launch Job 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 Launch Job 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

Chapter 1. Installing agents

15

space requirements as specified in Hardware requirements for systems running Common Agent or Platform Agent. You can view the status of the agent installation job by clicking Task Management > Active and Scheduled Jobs. If you installed Platform Agent on Linux, enable SNMP Access and Trap Forwarding by installing and configuring Net-SNMP. For instructions and information, see http://www.net-snmp.org/.

Installing Platform Agent manually

You can use these manual instructions to install Platform Agent on a managed system. These manual instructions provide an alternative method of installation to using the Agent Installation Wizard. Important: v Installation of IBM Systems Director installs IBM Systems Director Server, Common Agent (when applicable), and Platform Agent all together. Therefore, it is not necessary to separately install Common Agent or Platform Agent on the management server after installing IBM Systems Director Server. In most cases, any IBM Systems Director tasks requiring Common Agent or Platform Agent will be performed for systems with IBM Systems Director Server installed. v The IBM i Platform Agent is provided with the IBM i Licensed Program Product IBM Universal Manageability Enablement for IBM i (5722-UME). Refer to the IBM i documentation for details. v Ensure that the system clocks on systems that contain IBM Systems Director Server and Platform Agent remain synchronized. v If you have BMC, IMM, or IMM2 service processors, use Platform Agent 6.1.1 or later to help ensure full functionality and support. v If you have RSA service processors, use IBM Director Core Services 5.20.x to help ensure full functionality and support. If you do decide to use Platform Agent 6.3.2, you must first uninstall IBM Director Core Services 5.20.x before installing Platform Agent 6.3.2. Restriction: Platform Agent 6.3.2 will block updates on IBM Director Core Services 5.20.x systems and RSA service processors. 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. v Platform Agent 6.1.1 and later uses 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 Platform Agent systems. v See Installing and uninstalling KVM Platform Agent for considerations regarding the use of Red Hat Enterprise Linux with Linux Kernel-based Virtual Machine (KVM).

16

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

Related tasks: Preparing a Platform Agent managed system

Installing Platform Agent on IBM i

Platform Agent support for IBM i (formerly i5/OS) is provided with the IBM Universal Manageability Enablement for IBM i Licensed Program Product that ships with the base operating system. Use UME to configure Platform Agent on a system that is running IBM i. Platform Agent on IBM i provides agentless function, Common Information Model (CIM) events and monitoring, inventory, and IBM Systems Director support for IBM i groups and cumulative PTFs. Complete the following steps to configure Platform Agent on IBM i: 1. Ensure that the agentless managed server (SSH) is started. If it is not started, run the following command to start the SSH service:
strtcpsvr *sshd

2. Run the following command to start the SLP service:

strtcpsvr *slp

3. Run the following command to start the CIM server:

strtcpsvr *cimom

4. Ensure that collection services is running so that you can monitor resources. To start collection services, run a set of commands that is similar to the following example commands, substituting in your own values if necessary:
CFGPFRCOL INTERVAL(5.0) CYCITV(01) ENDPFRCOL STRPFRCOL CYCCOL(*YES)

With SSH, SLP, and CIM running, your IBM i system is ready to provide Platform Agent functionality. Use IBM Systems Director Server to discover, access, and manage the IBM i system. Related tasks: Preparing to install Platform Agent on i Installing the SLP Service Restarting Platform Agent Related reference: Systems Director Downloads Related information: Exchanging information with IBM

Verifying the successful installation of an IBM Systems Director agent

You can verify a successful installation by starting IBM Systems Director Server, logging into the Web interface, and discovering the new managed system. To verify that the agent installation was successful and ensure your managed systems can be discovered, complete the following steps:
Chapter 1. Installing agents

17

1. If IBM Systems Director Server is running on AIX or Linux, 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

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. 2. Log in to the Web interface for IBM Systems Director Server. For instructions, see Logging into IBM Systems Director Server. 3. The IBM Systems Director Home page provides a quick overview, as well as links to all necessary configuration tasks. To configure IBM Systems Director, perform these steps: a. Click System Discovery on the Initial Setup tab to discovery recently-installed agents. b. Click Collect Inventory on the Initial Setup tab to collect inventory data on all the recently-installed agents. c. Run these options from the Additional Setup tab. 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 After you have verified that the agent installation was successful, complete the following tasks: 1. (Optional) Configure and activate any plug-ins you want to use. For instructions, see Activating or upgrading the advanced plug-ins of IBM Systems Director. Related tasks: Logging in Discovering systems with system discovery Collecting and viewing inventory data Importing agent packages

18

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

Chapter 2. 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. Complete the following steps on each system to be managed. 1. 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

2. On all agentless managed systems that use the root user for request access for the ssh protocol, ensure that the PermitRootLogin value in /etc/ssh/sshd_config is set to yes. Notes: 1. You must restart the ssh server for any changes made to sshd_config to take effect. 2. IBM Systems Director does not support the ssh protocol on VMware ESXi hosts. If ssh is discovered on a VMware ESXi managed system, it might cause problems when attempting to collect inventory. Related tasks: Excluding IP addresses Related reference: Hardware and software requirements Supported operating systems AIX Pegasus CIM server and providers

Preparing to manage an 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 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 an
Copyright IBM Corp. 1999, 2012

19

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 1 shows such a network configuration. 3. If you intend to use Remote Deployment Manager (RDM), install RDM on the management server. 4. 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 1. 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)

20

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

Preparing to manage an IBM BladeCenter chassis using IBM Systems Director Server on a blade server
You can install IBM Systems Director Server on a blade server. With this management server you can manage the IBM BladeCenter unit, including the server on which IBM Systems Director Server is installed, and other IBM BladeCenter units. You must configure the network so that this installation is possible. Consider the following issues when managing the IBM BladeCenter unit that contains the management server: v Enable access for authorized administrators as determined by the security policy established for the user environment. v Be careful when making changes to the configuration of the IBM BladeCenter chassis from IBM Systems Director itself. Such changes could effectively remove the instance of IBM Systems Director Server from the network and halt the entire IBM Systems Director environment. Specifically, do not perform these tasks on the blade server where IBM Systems Director Server is installed without careful consideration: 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 an 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 1 on page 20 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 2 on page 22 shows such a network configuration.
Chapter 2. Preparing agentless managed systems

21

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

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.

22

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

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. 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: Hardware and software requirements Supported operating systems AIX Pegasus CIM server and providers

Preparing IBM i managed systems

Before you can discover IBM i managed systems as agentless, you must ensure that SSH is running. SSH configuration varies depending on the version of the operating system. See http://www.ibm.com/servers/enable/site/porting/tools/ openssh.html for complete documentation.

Chapter 2. Preparing agentless managed systems

23

24

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

Chapter 3. Uninstalling
Uninstall IBM Systems Director and its components (including the default database) from your system. Notes: v Ensure that you uninstall any IBM Systems Director plug-ins before using these methods to uninstall IBM Systems Director Server, Common Agent, or Platform Agent. For information, see the uninstallation instructions provided with each plug-in. v Consider retaining the configuration data when you uninstall IBM Systems Director. This enables you to reinstall or upgrade IBM Systems Director and access the saved configuration data. Should you reinstall, be sure to reinstall IBM Systems Director in the same location. v If you want to change your installation of IBM Systems Director 6.x to a previous IBM Director 5.20.x version, you need to first uninstall all instances of Common Agent 6.x and Platform Agent 6.x. This is necessary because IBM Director Server 5.20.x cannot discover Common Agent 6.x nor Platform Agent 6.x. As a result, the pre-6.x installation will not provide any indication that an IBM Systems Director 6.x component is present. Attempting to install an earlier version of Common Agent or Platform Agent than that which already exists on the system has the potential to cause problems. Therefore, first uninstall the existing, later version of Common Agent or Platform Agent before installing the earlier version. v If you are uninstalling agents on a previously discovered endpoint, you must discover the endpoint again after you uninstall the agent. Discovering the endpoint again allows the correct functionality to be reflected in IBM Systems Director. Related tasks: Installing the management server Preparing agentless managed systems Installing Common Agent Installing Platform Agent Related information: Installation or uninstallation fails and requires cleanup

Uninstalling Common Agent 6.x on IBM i

Use uninstallDirAgent.sh to uninstall Common Agent 6.x on IBM i. To uninstall Common Agent, complete the following steps: 1. At an IBM i command prompt on the system on which Common Agent is installed, enter the following command to initialize QSH:
QSH

2. Change to the /QIBM/ProdData/Director/ directory and enter the following command to uninstall Common Agent:
uninstallDirAgent.sh

Copyright IBM Corp. 1999, 2012

25

Note: Depending on your operating system version and the components that you are removing, the uninstallation task might take a long time (up to an hour) to complete. 3. To remove IBM Director user data from the IBM i management server, delete the /qibm/userdata/director/ directory by typing the following command:
QSH CMD (rm -rf /qibm/userdata/director/)

Related tasks: Installing the management server Preparing agentless managed systems Installing Common Agent Installing Platform Agent Related information: Installation or uninstallation fails and requires cleanup

26

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

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 character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd. 1623-14, Shimotsuruma, Yamato-shi Kanagawa 242-8502 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 websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.
Copyright IBM Corp. 1999, 2012

27

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Dept. LRAS/Bldg. 903 11501 Burnet Road Austin, TX 78758-3400 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. All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information is for planning purposes only. The information herein is subject to change before the products described become available. 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. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy,

28

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. Copyright IBM Corp. _enter the year or years_. If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/ copytrade.shtml. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others.
Notices

29

30

Installing IBM Systems Director agents on IBM i and preparing agentless managed systems

Printed in USA