IBM Systems Director
Installing IBM Systems Director agents on Linux for
System x and preparing agentless managed systems
Version 6.3
IBM Systems Director
Installing IBM Systems Director agents on Linux for
System x 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 43.
© Copyright IBM Corporation 1999, 2013.
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 . . . . . . . . . . . . . vii
How to send your comments . . . . . . . . ix
Installing Platform Agent manually . . .
Installing Platform Agent on Linux for
System x and x86-based systems . . .
Verifying the successful installation of an IBM
Systems Director agent . . . . . . . .
.
. 20
.
. 21
.
. 23
Checklist: Installing agents . . . . . . xi
Chapter 2. Preparing agentless
managed systems . . . . . . . . . . 25
Chapter 1. Installing agents . . . . . . 1
Preparing to manage service processors with IBM
Systems Director. . . . . . . . . . . .
Configuring access to agentless managed systems
Sample sudo configuration file . . . . . .
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 VMware managed systems. . . . .
Running the Pre-Installation Utility on an agent (AIX
and Linux) . . . . . . . . . . . . . . . 2
Installing Common Agent . . . . . . . . . . 3
Preparing for a Common Agent managed system 3
Obtaining licenses for Common Agent . . . . 3
Preparing to install Common Agent on Linux
for System x and x86-based systems . . . . 4
Using a Linux package manager to find
libraries or RPMs . . . . . . . . . . . 6
Installing agents using the Agent Installation
Wizard . . . . . . . . . . . . . . . 7
Installing Common Agent manually . . . . . 10
Installing Common Agent on Linux for
System x and x86-based systems . . . . . 11
Installing Platform Agent . . . . . . . . . . 14
Preparing for a Platform Agent managed system 15
Preparing to install Platform Agent on Linux
for System x and x86-based systems . . . . 15
Installing agents using the Agent Installation
Wizard . . . . . . . . . . . . . . . 17
© Copyright IBM Corp. 1999, 2013
. 25
32
. 33
. 34
. 35
. 37
Chapter 3. Uninstalling . . . . . . . . 39
Uninstalling IBM Systems Director on Linux .
.
. 39
Notices . . . . . . . . . . . . . . 43
Trademarks .
.
.
.
.
.
.
.
.
.
.
.
.
. 45
iii
iv
Installing agents on Linux for System x 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, 2013
v
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.3
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 agents on Linux for System x 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.
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.
Web resources
Listed here are the websites and information center topics that relate to IBM
Systems Director.
About this publication
vii
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
https://www.ibm.com/developerworks/mydeveloperworks/wikis/
home?lang=en#/wiki/W3e8d1c956c32_416f_a604_4633cd375569/page/Best
%20Practices
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
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
viii
Installing agents on Linux for System x and preparing agentless managed systems
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
x
Installing agents on Linux for System x and preparing agentless managed systems
Checklist: Installing agents
Use this checklist to guide you through the installation process.
1 Prepare your managed systems.
__ 1.
__ 2.
__ 3.
__ 4.
Run the Pre-Installation Utility (2.
Prepare systems for Platform Agent (15).
Prepare systems for Common Agent (3).
If relevant, prepare any agentless managed systems for discovery and
management by IBM Systems Director (25).
2 Install the agents.
__ 1. Use the Agent Installation Wizard to deploy agent packages to your
managed systems (7).
© Copyright IBM Corp. 1999, 2013
xi
xii
Installing agents on Linux for System x 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.3 before, or at the same time
as, the agents that are installed on the management server are updated to 6.3.3. If
you attempt to update a local agent to 6.3.3 before updating IBM Systems Director
Server, then the IBM Systems Director Server update to 6.3.3 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, 2013
1
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
Running the Pre-Installation Utility on an agent (AIX and Linux)
Use these instructions to run the IBM Systems Director Pre-Installation Utility
(PIU) on an agent on AIX® or Linux.
v You can obtain or run the Pre-Installation Utility from the following locations.
Table 1. Obtaining the Pre-Installation Utility
Location
Action
SysDir_PreInstUtil_6_3_3_platform.tar.gz
Download the Pre-Installation Utility from
the IBM Systems Director Downloads
website.
Note: The downloads website always
contains the most recent version.
1. To run the Pre-Installation Utility, complete the following steps:
v Pre-Installation Utility download
a. To extract the contents of the Pre-Installation Utility package, type the
following command depending on your operating system:
– Linux:
tar -zxvf package_name
where package_name is the file name of the download package.
b. To change to the directory in which the Pre-Installation Utility script is
located, type the following command and press Enter:
cd server/checkds
c. Type the following command, depending on your operating system, and
press Enter:
AIX
./checkds.sh -p commonagent
Linux
./checkds.sh -p [platformagent|commonagent]
For example:
./checkds.sh -p platformagent
Note: If you do not specify the -p attribute, the tool is run for the server.
So, you must specify -p and designate whether you are running the tool
to prepare for Common Agent or, if applicable, Platform Agent
installation.
2
Installing agents on Linux for System x and preparing agentless managed systems
The IBM Systems Director Pre-Installation Utility starts.
2. 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. The
./checkds.sh -? command also displays supported syntax.
Related tasks:
Preparing to upgrade and migrate
Related reference:
Systems Director Downloads
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
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.
Chapter 1. Installing agents
3
2. Obtain licenses for each installation of Common Agent on non-IBM x86 systems
from the software ordering web page: From the ibm.com web page
(http://www.ibm.com/us/en/), complete the following steps:
a.
b.
c.
d.
Click Products.
Under Systems and servers, select System x (xSeries).
Under Options and upgrades, select All options and upgrades.
Under More options and upgrades, select Software.
Note: Standard subscription and support contracts for IBM Systems Director
components are not available for any of the non-IBM servers.
Related concepts:
|
|
License information
Preparing to install Common Agent on Linux for System x and
x86-based systems
Before installing Common Agent on a managed system running Linux for
System x and x86-based systems, make sure that your system meets all the
applicable requirements.
Review the following information and complete the necessary steps to prepare
your system for installation:
v Run the Pre-Installation Utility and fix any errors that it identifies. For
instructions, see “Running the Pre-Installation Utility on an agent (AIX and
Linux)” on page 2.
v Ensure that your system meets the hardware and software requirements for
installation, as described in “Hardware and software requirements”.
v Ensure that the instance of Common Agent will be fully functional and able to
send alerts to IBM Systems Director Server. For the Common Agent to be fully
functional you might need to install service-processor device drivers or the IBM
LM78 and SMBus device drivers for Linux.
v Ensure that the required RPMs are installed.
Table 2. Required libraries for Linux on System x
Installation scenario
Management server
Common agent
Platform agent
Red Hat Enterprise Linux
openssh
libstdc++.so.5
libm.so.6
libgcc_s.so.1
libc.so.6
libdl.so.2
libpthread.so.0
unzip
libaio
libcrypt.so.1
libnsl.so.1
libpam.so.0
librt.so.1
bind-utils
net-tools
libstdc++.so.6
libuuid.so.1
libexpat.so.0
libcrypt.so.1
libc.so.6
libdl.so.2
libstdc++.so.5
libgcc_s.so.1
libm.so.6
libnsl.so.1
libpam.so.0
libpthread.so.0
librt.so.1
unzip
bind-utils
net-tools
libstdc++.so.6
libuuid.so.1
libexpat.so.0
libstdc++.so.5
bind-utils
net-tools
libpam.so.0
libstdc++.so.6
libuuid.so.1
libcrypt.so.1
unzip
libexpat.so.0
4
Installing agents on Linux for System x and preparing agentless managed systems
Table 2. Required libraries for Linux on System x (continued)
Installation scenario
Management server
Common agent
Platform agent
SUSE Linux Enterprise
Server 10
openssh
libstdc++.so.5
libm.so.6
libgcc_s.so.1
libc.so.6
libdl.so.2
libpthread.so.0
unzip
libaio
libcrypt.so.1
libnsl.so.1
libpam.so.0
librt.so.1
bind-utils
net-tools
libstdc++.so.6
libuuid.so.1
libexpat.so.1
libcrypt.so.1
libc.so.6
libdl.so.2
libstdc++.so.5
libgcc_s.so.1
libm.so.6
libnsl.so.1
libpam.so.0
libpthread.so.0
librt.so.1
unzip
bind-utils
net-tools
libstdc++.so.6
libuuid.so.1
libexpat.so.1
libstdc++.so.5
bind-utils
net-tools
libpam.so.0
libstdc++.so.6
libuuid.so.1
libcrypt.so.1
unzip
libexpat.so.1
SUSE Linux Enterprise
Server 11
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 about using a package manager to find and install a missing library
or RPM, see “Using a Linux package manager to find libraries or RPMs” on
page 6.
v (Red Hat Enterprise Linux only): Before you install IBM Systems Director Server,
you must ensure the SELinux policy is not being enforced.
SELinux runs in any of the following states:
Disabled
SELinux is disabled. You can tell that SELinux is in the disabled state by
determining if any of the following conditions are true:
– No files exist in the /selinux/ directory.
Permissive (enabled)
SELinux is enabled but not enforcing any security policies. You can tell
that SELinux is in the permissive state by determining if any of the
following conditions are true:
– The SELINUX variable in /etc/sysconfig/selinux/enforce is set to
permissive or a value not equal to "1".
– When you run the getenforce command, it outputs “Permissive”.
Enforcing (enabled)
SELinux is enabled and enforcing security policies. You can tell that
SELinux is in the enforcing state by determining if any of the following
conditions are true:
– The SELINUX variable in /etc/sysconfig/selinux/enforce is set to
enforcing or "1".
– When you run the getenforce command, it outputs “Enforcing”.
To set SELinux to permissive, run the following command before you install
IBM Systems Director Server:
/usr/sbin/setenforce Permissive
Chapter 1. Installing agents
5
v Systems with service processors: Install the supporting device drivers and
mapping layers, if they are not already installed. See “Preparing to manage
service processors with IBM Systems Director” for information about these
drivers and mapping layers.
v If you want to use the Remote Session task on the managed system, make sure
that the package that contains telnetd daemon is installed and configured.
v If you want to use IBM Systems Director Server on System x for heterogeneous
server management, you can install Common Agent or Platform Agent on the
platforms you want to manage. You can obtain Common Agent and Platform
Agent for the supported operating systems from the IBM Systems Director Web
site at www.ibm.com/systems/software/director/downloads/agents.html.
v Ensure the validity of any stored public key data for the target system in
root_SSH_data_directory/known_hosts on IBM Systems Director Server. See
“Common Agent cannot be installed on an AIX or Linux system” for more
information.
Related tasks:
Installing agents using the Agent Installation Wizard
Installing Common Agent on Linux for System z
Related reference:
Hardware and software requirements
Supported operating systems
IBM Systems Director Web page
Related information:
Linux installation troubleshooting
Common Agent cannot be installed on an AIX or Linux system
Using a Linux package manager to find libraries or RPMs
If you are missing a library or RPM that is required for installation, use the
following information to find and install the missing library or RPM.
Before using a Linux package manager, review the following requirements:
v Ensure that your system is registered with an RHN satellite or a YaST online
repository.
v Run these commands against the full library names, as they appear in the
Pre-Installation Utility report.
For Red Hat Enterprise Linux:
1. Enter yum whatprovides library_dependency_name to determine what operating
system package provides the library or RPM. For example:
[root@rhel5-host ~]# yum whatprovides libstdc++.so.5
Loaded plugins: rhnplugin, security
compat-libstdc++-33-3.2.3-61.i386 : Compatibility standard C++ libraries
Repo
: rhel-x86_64-server-5
Matched from:
Other
: libstdc++.so.5
compat-libstdc++-33-3.2.3-61.i386 : Compatibility standard C++ libraries
6
Installing agents on Linux for System x and preparing agentless managed systems
Repo
: installed
Matched from:
Other
: Provides-match: libstdc++.so.5
2. Enter yum install package_name to install the package.
[root@rhel5-host ~]# yum install compat-libstdc++-33
For SUSE Linux 11:
1. Enter zypper what-provides library_dependency_name to determine what
operating system package in the repository provides the library or RPM. For
example:
sles11-host:~ # zypper what-provides libstdc++.so.5
Retrieving repository ’sle-11-i586-extras’ metadata [done]
Building repository ’sle-11-i586-extras’ cache [done]
Loading repository data...
Reading installed packages...
S | Name
| Type
| Version
| Arch | Repository
--+-------------+---------+------------+------+----------------i | libstdc++33 | package | 3.3.3-11.9 | i586 | sle-11-i586-pool
2. Enter zypper install package_name to install the package. For example:
sles11-host:~ # zypper install libstdc++33
For SUSE Linux 10:
1. Enter rug what-provides library_dependency_name to determine what
operating system package in the repository provides the library or RPM. For
example:
sles10-host:~ # rug what-provides libstdc++.so.5
S | Catalog | Package
| Version
| libstdc++.so.5 Version
--+---------+------------------+------------+----------------------i | system | compat-libstdc++ | 5.0.7-22.2 | any
2. Enter zypper install package_name to install the package. For example:
sles10-host:~ # rug install compat-libstdc++
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.
Chapter 1. Installing agents
7
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.
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
8
Installing agents on Linux for System x and preparing agentless managed systems
– 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 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.
Chapter 1. Installing agents
9
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
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:
– Common Agent: /var/log/dirinst.log
– Platform Agent: /opt/ibm/platform/log/install.log
Note: For more information about error log files, see “Information to provide
to the IBM Technical Support Center”.
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.
10
Installing agents on Linux for System x and preparing agentless managed systems
Related tasks:
Preparing a Common Agent managed system
Installing Common Agent on Linux for System x and x86-based
systems
After preparing your system, you can install Common Agent on a Linux for
System x platform, including a VMware ESX server, by downloading the
installation file or, if available for this release, using the DVD. You can perform a
standard installation or you can use a response file to customize the features that
are installed.
Important:
v Ensure that the system clocks on the systems that contain IBM Systems Director
Server and Common Agent remain synchronized.
v Use the Pre-Installation Utility to check your system for required RPM packages
and libraries. If any packages or libraries are missing, you receive an alert and
information about how to obtain them.
|
Common Agent 6.3.3 and Platform Agent 6.3.3 are primarily intended to support
new hardware and operating systems. You can install them for the first time on
any system that has the supported operating system and hardware, or you can
install them as updates to 6.3 upgrades to most 5.x and 6.x agents. One exception
is that the Platform Agent 6.3 installation does not upgrade agents that have the
IBM Systems Director 5.20.x on systems with an RSA service processor. In this
situation, you have the following option:
v To maintain full support of agents on these systems, continue to use Common
Agent 6.1 for Windows, Common Agent 6.1.2.3 for Linux for System x, or IBM
Director Core Services 5.20.31 or 5.20.32.
|
Depending on the version of Common Agent that you are installing, you can
install Common Agent on Linux for System x from either installation media or
from a downloaded installation package.
Important: The IBM Systems Director Server, Common Agent, and Platform Agent
installation packages for Linux are provided in English only.
Table 3. Installation options for Common Agent on Linux for System x
Installation method
Downloaded installation
package
Title or file name
6.3.3 agents
Install the 6.3.3 agents unless you need full
support for downlevel agents that have the
previously specified hardware and software
configurations.
v SysDir6_3_3_Common_Agent_Linux_x86.tar.gz
(agent package for manual installation)
v SysDir6_3_3_Common_Agent_Linux_x86.jar
(agent package for Agent Installation Wizard
installation)
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
Chapter 1. Installing agents
11
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, use the optional diragent.rsp file
as described in the following steps.
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 /opt/ibm/director/
agent/runtime/agent/toolkit/bin:
/opt/ibm/director/agent/runtime/agent/toolkit/bin/configure.sh -amhost
agentmanager_ip -passwd agentregistration_password -force
Tip:
v You can use the configure.sh -unmanaged -force command to return
the agent to unmanaged mode.
v The agent will also change to managed mode automatically after you
discover it, and request access to it through the IBM Systems Director
Server.
Log in as the root user and complete the following steps to install Common Agent
on Linux for System x:
1. Start the installation from the installation source:
Downloaded installation files: To start the installation from a Web download,
complete the following steps:
a. Download the installation package from the IBM Systems Director
Downloads Web Site at http://www-03.ibm.com/systems/software/
director/downloads/agents.html.
b. To extract the contents of the installation package to a local directory, type
one the following commands:
tar -zxvf SysDir6_3_3_Common_Agent_Linux_x86.tar.gz
or
jar -xvf SysDir6_3_3_Common_Agent_Linux_x86.jar
c. Change to the directory in which the installation script is located. Type the
following command and press Enter:
cd /install_files/repository
where install_files is the path to the extracted installation files.
d. If you used the jar command, change the permission setting of the
installation script to make it accessible. Type the following command and
press Enter:
chmod +x dir6.3.3_commonagent_linux_x86
2. Optional: To customize the installation, copy the response file (diragent.rsp) to
a local directory and modify the installation settings in your local copy.
a. Type the following command and press Enter:
cp diragent.rsp /directory/
where directory is a local directory.
12
Installing agents on Linux for System x and preparing agentless managed systems
b. Open an ASCII text editor and modify the installation settings in the copy
of the diragent.rsp file. This file is fully commented.
The following parameters are used in the diragent.rsp file to register the
Common Agent services with an agent manager. These parameters are
optional, but, if one is specified, then both must be specified.
AGENT_MANAGER_HOSTNAME
The host name or IP address for 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.
AGENT_MANAGER_PASSWORD
The password for registering with the agent manager.
The following parameters are used to set the ports that the common agent
services will use. A valid number for each port is a number that is greater
than 1024 and lesser than 65535. The values listed are the default values for
each parameter.
v AGENT_PORT=9510
v AGENT_NONSTOP_PORT_1=9514
v AGENT_NONSTOP_PORT_2=9515
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 Common Agent, from within the directory in which the installation
script is located and type one of the following commands, then press Enter:
v To accept the default settings:
./dir6.3.3_commonagent_linux_x86
v To use the response file:
./dir6.3.3_commonagent_linux_x86 -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.
Note: To extract the file sets but not install Common Agent, enter the following
command:
./dir6.3.3_commonagent_linux_x86 -x all -p extract_directory
where extract_directory is the local directory into which you want to extract
the installation files.
Common Agent is started automatically when installation completes.
To ensure full functionality of your new Common Agent instance, discover it with
IBM Systems Director Server.
See “Restarting Common Agent” for information about how to stop, start, and
obtain the status of Common Agent.
Chapter 1. Installing agents
13
Related tasks:
Linux for System x
Importing agent packages
Upgrading and migrating agents
Restarting Common Agent
Discovering systems and collecting inventory data
Related reference:
Systems Director Downloads
Related information:
You cannot promote Platform Agent to Common Agent on Linux with Xen
Linux installation troubleshooting
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 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 or later, you must first uninstall IBM Director Core Services 5.20.x
before installing Platform Agent.
Restriction: Platform Agent 6.3.2 and later 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.
14
Installing agents on Linux for System x and preparing agentless managed 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).
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 Linux for System x and
x86-based systems
Before installing Platform Agent on a managed system running Linux for
System x, make sure that your system meets all the applicable requirements.
Review the following information and complete the necessary steps to prepare
your system for installation:
v Run the Pre-Installation Utility and fix any errors that it identifies. For
instructions, see “Running the Pre-Installation Utility on an agent (AIX and
Linux)” on page 2.
v Ensure that your system meets the hardware and software requirements for
installation, as described in “Hardware and software requirements”.
v Ensure that the instance of Common Agent will be fully functional and able to
send alerts to IBM Systems Director Server. For the Common Agent to be fully
functional you might need to install service-processor device drivers or the IBM
LM78 and SMBus device drivers for Linux.
v Ensure that the required RPMs are installed.
Note: The Platform Agent installer checks for all of the RPMs and will notify
you if any are missing.
Chapter 1. Installing agents
15
Table 4. Required libraries for Linux on System x
Installation scenario
Management server
Common agent
Platform agent
Red Hat Enterprise Linux
openssh
libstdc++.so.5
libm.so.6
libgcc_s.so.1
libc.so.6
libdl.so.2
libpthread.so.0
unzip
libaio
libcrypt.so.1
libnsl.so.1
libpam.so.0
librt.so.1
bind-utils
net-tools
libstdc++.so.6
libuuid.so.1
libexpat.so.0
libcrypt.so.1
libc.so.6
libdl.so.2
libstdc++.so.5
libgcc_s.so.1
libm.so.6
libnsl.so.1
libpam.so.0
libpthread.so.0
librt.so.1
unzip
bind-utils
net-tools
libstdc++.so.6
libuuid.so.1
libexpat.so.0
libstdc++.so.5
bind-utils
net-tools
libpam.so.0
libstdc++.so.6
libuuid.so.1
libcrypt.so.1
unzip
libexpat.so.0
SUSE Linux Enterprise
Server 10
openssh
libstdc++.so.5
libm.so.6
libgcc_s.so.1
libc.so.6
libdl.so.2
libpthread.so.0
unzip
libaio
libcrypt.so.1
libnsl.so.1
libpam.so.0
librt.so.1
bind-utils
net-tools
libstdc++.so.6
libuuid.so.1
libexpat.so.1
libcrypt.so.1
libc.so.6
libdl.so.2
libstdc++.so.5
libgcc_s.so.1
libm.so.6
libnsl.so.1
libpam.so.0
libpthread.so.0
librt.so.1
unzip
bind-utils
net-tools
libstdc++.so.6
libuuid.so.1
libexpat.so.1
libstdc++.so.5
bind-utils
net-tools
libpam.so.0
libstdc++.so.6
libuuid.so.1
libcrypt.so.1
unzip
libexpat.so.1
SUSE Linux Enterprise
Server 11
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 about using a package manager to find and install a missing library
or RPM, see “Using a Linux package manager to find libraries or RPMs” on
page 6.
v If you are running Red Hat Enterprise Linux 6.x, ensure that the following
RPMs are not installed because they impact network configuration support for
Platform Agent:
– NetworkManager-glib, and the following RPMs that depend on it:
- geoclue
- gimp-help-browser
- pywebkitgtk
- rhythmbox
- webkitgtk
– NetworkManager, and the following RPMs that depend on it:
- NetworkManager-openswan
- NetworkManager-gnome
- anaconda
16
Installing agents on Linux for System x and preparing agentless managed systems
v Systems with service processors: Install the supporting device drivers and
mapping layers, if they are not already installed. See “Preparing to manage
service processors with IBM Systems Director” for information about these
drivers and mapping layers.
v Verify that the LD_LIBRARY_PATH environment variable is not exported
globally.
v Verify that no applications force the SSL libraries to be exported to the
/etc/ld.so.conf.d/ directory or the /root/.bash-profile directory.
v If you want to use the Remote Session task on the managed system, make sure
that the package that contains telnetd daemon is installed and configured.
v If you want to use IBM Systems Director Server on System x for heterogeneous
server management, you can install Common Agent or Platform Agent on the
platforms you want to manage. You can obtain Common Agent and Platform
Agent for the supported operating systems from the IBM Systems Director Web
site at www.ibm.com/systems/software/director/downloads/agents.html.
Related tasks:
Installing agents using the Agent Installation Wizard
Using a Linux package manager to find libraries or RPMs
Related reference:
Hardware and software requirements
Supported operating systems
IBM Systems Director Web page
Related information:
Linux installation troubleshooting
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:
Chapter 1. Installing agents
17
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.
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.
c.
4. In
a.
b.
v The Agent Installation Wizard can install only one agent package at a
time. If more than one agent package is displayed in the Selected list,
you will not be able to advance to the Systems page.
Click Next.
the Agent Installation Wizard Systems page, complete the following steps:
Select the managed systems on which you want to install the agent package
in the Available list.
Click Add. The selected systems are displayed in the Selected list.
Notes:
v Depending on how you started the Agent Installation Wizard, 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
18
Installing agents on Linux for System x and preparing agentless managed systems
– 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 9.
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 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.
Chapter 1. Installing agents
19
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:
– Common Agent: /var/log/dirinst.log
– Platform Agent: /opt/ibm/platform/log/install.log
Note: For more information about error log files, see “Information to provide
to the IBM Technical Support Center”.
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 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 or later, you must first uninstall IBM Director Core Services 5.20.x
before installing Platform Agent.
20
Installing agents on Linux for System x and preparing agentless managed systems
Restriction: Platform Agent 6.3.2 and later 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).
Related tasks:
Preparing a Platform Agent managed system
Installing Platform Agent on Linux for System x and x86-based
systems
To install Platform Agent on a system that is running Linux for System x and
x86-based systems, download the installation files from the IBM Systems Director
support Web site or, if available for this release, use the DVD. You can perform a
standard installation or you can use a response file to customize the installation for
your environment.
Important:
v Ensure that the system clocks on systems that contain IBM Systems Director
Server and Platform Agent remain synchronized.
v Use the Pre-Installation Utility to check your system for required RPM packages
and libraries. If any packages or libraries are missing, you receive an alert and
information about how to obtain them.
|
|
Common Agent 6.3.3 and Platform Agent 6.3.3 are primarily intended to support
new hardware and operating systems. You can install them for the first time on
any system that has the supported operating system and hardware, or you can
install them as updates to 6.3 upgrades to most 5.x and 6.x agents. One exception
is that the Platform Agent 6.3 installation does not upgrade agents that have the
IBM Systems Director 5.20.x on systems with an RSA service processor. In this
situation, you have the following option:
v To maintain full support of agents on these systems, continue to use Common
Agent 6.1 for Windows, Common Agent 6.1.2.3 for Linux for System x, or IBM
Director Core Services 5.20.31 or 5.20.32.
You can install Platform Agent on Linux for System x and x86-based systems from
either installation media or from a downloaded installation package.
Important: The IBM Systems Director Server, Common Agent, and Platform Agent
installation packages for Linux are provided in English only.
Chapter 1. Installing agents
21
Table 5. Installation options for Platform Agent on Linux for System x and x86-based
systems
Installation method
Downloaded installation
package
Title or file name
6.3.3 agents
Install the 6.3.3 agents unless you need full
support for downlevel agents that have the
previously specified hardware and software
configurations.
v SysDir6_3_3_Platform_Agent_Linux_x86.tar.gz
(agent package for manual installation)
v SysDir6_3_3_Platform_Agent_Linux_x86.jar
(agent package for Agent Installation Wizard
installation)
Complete the following steps to install Platform Agent on Linux for System x:
1. Start the installation from the installation source:
Downloaded installation files: To start the installation from a Web download,
complete the following steps:
a. Download the installation package from the IBM Systems Director
Downloads Web Site at http://www-03.ibm.com/systems/software/
director/downloads/agents.html.
b. To extract the contents of the installation package to a local directory, type
one the following commands:
tar -zxvf SysDir6_3_3_Platform_Agent_Linux_x86.tar.gz
or
jar -xvf SysDir6_3_3_Platform_Agent_Linux_x86.jar
c. Change to the directory in which the installation script is located. Type the
following command and press Enter:
cd /install_files/repository
where install_files is the path to the extracted installation files.
d. If you used the jar command, change the permission setting of the
installation script to make it accessible. Type the following command and
press Enter:
chmod +x dir6.3.3_platform_agent_linux_x86
2. Optional: To customize the installation, copy the response file to a local
directory and modify the installation settings in your local copy.
a. Type the following command and press Enter:
cp platform.rsp /directory/
where directory is a local directory.
b. Save the modified response file.
Tip: After installation, keep the response file for future use and reference.
Enable SNMP Access and Trap Forwarding by installing and configuring
Net-SNMP. For instructions and information, see http://www.net-snmp.org/.
3. To install Platform Agent, from within the directory in which the installation
script is located, type one of the following commands and press Enter:
22
Installing agents on Linux for System x and preparing agentless managed systems
v To accept the default settings:
./dir6.3.3_platform_agent_linux_x86
v To output a usage statement that documents the command line options:
./dir6.3.3_platform_agent_linux_x86 -h
v To use the response file:
./dir6.3.3_platform_agent_linux_x86 -r /directory/response.rsp
v To start an unattended installation:
./dir6.3.3_platform_agent_linux_x86 -i
where directory is the local directory to which you copied the response file,
and response.rsp is the name of the response file. Platform Agent is started
automatically when installation completes.
After Platform Agent is installed, you can enable the Wake on LAN feature. To
determine if your server supports this feature, review the server documentation.
If you installed Platform Agent on IBM System x3950 M2, machine type 7141 with
either VMware version 3.0.2 or SUSE Linux Enterprise Server 10 for x86, run the
following command:
/opt/ibm/icc/cimom/bin/cimprovider -d -m SCSIDev_Module
This resolves a known issue that can prevent full collection of inventory on the
managed system.
Note: On Windows and Linux RSA II systems, Platform Agent 6.3.3 will install the
LSI MegaRAID provider along with the RSA II service. Platform Agent 6.3.3 will
also install the OSA IPMI driver on Windows 2003 systems that need it. Use the
Verify Connection page to query vital properties after you upgrade to Platform
Agent 6.3.3. This will immediately renew alert subscriptions for the LSI MegaRAID
provider and Basic RAID hardware. If you do not verify the connection, the alert
subscriptions might take as long as an hour to update.
See “Restarting Platform Agent” for information about how to stop, start, and
obtain the status of Platform Agent.
Related tasks:
Preparing to install Platform Agent on Linux for System x
Importing agent packages
Restarting Platform Agent
Related reference:
Systems Director Downloads
Related information:
Linux installation troubleshooting
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.
Chapter 1. Installing agents
23
To verify that the agent installation was successful and ensure your managed
systems can be discovered, complete the following steps:
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
24
Installing agents on Linux for System x 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.”
|
|
Note: You must enable secure copy protocol (SCP) when you set up a Linux
resource for agentless or Platform Agent managed systems.
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 service processors with IBM Systems Director
You can use IBM Systems Director to manage supported service processors that are
installed in a managed system.
IBM Systems Director can manage service processors that are installed in Agentless
managed systems, Platform Agent managed systems, and Common Agent
managed systems.
v For Agentless managed systems, you do not need to install drivers to perform
Agentless management of the service processors.
© Copyright IBM Corp. 1999, 2013
25
v For Platform Agent managed systems and Common Agent managed systems,
management of the service processor uses the Common Information Model
(CIM) standard, and requires not only installation of either Platform Agent or
Common Agent on the managed system, but also installation of a device driver,
and possibly a shared library to access the device driver.
To install the required drivers on a Platform Agent managed system or Common
Agent managed system to enable management of the service processor, complete
the following steps:
1. See the documentation for your managed server to identify the type of service
processor that is installed.
2. Identify your server type in Table 6.
Note: For information about specific IBM Systems Director functions that
support or do not support these systems, see IBM ServerProven at
www.ibm.com/servers/eserver/serverproven/compat/us/.
Table 6. Servers with service processors that are supported for Platform Agent or Common Agent management by
IBM Systems Director
Server type
Supported models
IBM BladeCenter blade servers with v IBM BladeCenter
an IPMI baseboard management
v IBM BladeCenter
controller (BMC)
v IBM BladeCenter
v IBM BladeCenter
See the “IBM BladeCenter, System x, v IBM BladeCenter
and System x servers with an IPMI
v IBM BladeCenter
baseboard management controller
v IBM BladeCenter
(BMC) or with an integrated systems v IBM BladeCenter
management module (IMM)” column v IBM BladeCenter
in Table 7 on page 29.
v IBM BladeCenter
v IBM BladeCenter
v IBM BladeCenter
v IBM BladeCenter
v IBM BladeCenter
v IBM BladeCenter
v IBM BladeCenter
HC10
HS20, machine types 1883, 1884, 7981, 8843
HS12, machine types 8014, 8028
HS21
HS21 XM
HS40
JS12 Express®
JS20
JS21
JS22
LS20
LS21
LS22
LS41
LS42
QS21
IBM BladeCenter blade servers with v IBM BladeCenter HS22 machine type 7870
an integrated systems management
v IBM BladeCenter HS22V machine type 7871
module (IMM)
v IBM BladeCenter HX5 machine type 7872
Note: The IMM internally contains a
BMC.
See the “IBM BladeCenter, System x,
and System x servers with an IPMI
baseboard management controller
(BMC) or with an integrated systems
management module (IMM)” column
in Table 7 on page 29.
IBM BladeCenter blade servers with IBM BladeCenter HS20, machine types 8678, 8832, 8833
an Integrated systems management
processor (ISMP)
See the “IBM BladeCenter and
System x servers with an integrated
systems management processor
(ISMP)” column in Table 7 on page
29.
26
Installing agents on Linux for System x and preparing agentless managed systems
Table 6. Servers with service processors that are supported for Platform Agent or Common Agent management by
IBM Systems Director (continued)
Server type
™
eServer servers with an IPMI
baseboard management controller
(BMC)
See the “eServer servers with an
IPMI baseboard management
controller (BMC)” column in Table 7
on page 29.
Note: Some systems support
installation of an optional Remote
Supervisor Adapter or Remote
Supervisor Adapter II service
processor. If this optional service
processor is installed, it supersedes
the standard service processor for
that system, and all management
occurs through the Remote
Supervisor Adapter or Remote
Supervisor Adapter II.
Supported models
v
v
v
v
IBM
IBM
IBM
IBM
eServer
eServer
eServer
eServer
325, machine type 8835
326, machine type 8848
326m, machine type 7969
326m, machine type 7992
v System x3200
v System x 206m
v System x3200 M2
v System x 236
v System x3250
v System x 260
v System x3250 M2
v System x 306m
See the “IBM BladeCenter, System x, v System x3250 M3
v System x 336
and System x servers with an IPMI
v System x3350
v System x 346
baseboard management controller
v System x3400
v System x 347
(BMC) or with an integrated systems v System x3450
v System x 366
management module (IMM)” column v System x3455
in Table 7 on page 29.
v System x3500
Note: Some systems support
v System x3550
installation of an optional Remote
v System x3610
Supervisor Adapter or Remote
v System x3650
Supervisor Adapter II service
v System x3650 T
processor. If this optional service
v System x3655
processor is installed, it supersedes
v System x3755
the standard service processor for
v System x3755 M31
that system, and all management
v System x3800
occurs through the Remote
v System x3850
Supervisor Adapter or Remote
1
The BMC in this system provides a subset of the function found in the
Supervisor Adapter II.
other system BMCs.
System x and System x servers with
an IPMI baseboard management
controller (BMC)
Chapter 2. Preparing agentless managed systems
27
Table 6. Servers with service processors that are supported for Platform Agent or Common Agent management by
IBM Systems Director (continued)
Server type
Supported models
v
v
v
v
v
v
See the “IBM BladeCenter, System x, v
and System x servers with an IPMI
v
baseboard management controller
v
(BMC) or with an integrated systems v
management module (IMM)” column v
in Table 7 on page 29.
v
v
v
v
v
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
x3200
x3250
x3400
x3400
x3500
x3500
x3550
x3550
x3620
x3650
x3650
x3690
x3850
x3850
x3950
x3950
System x and System x servers with
a Remote Supervisor Adapter II or
Remote Supervisor Adapter II
SlimLine
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
x3105
x3200
x3200
x3250
x3250
x3350
x3400
x3455
x3500
x3550
x3650
x3650
x3655
x3755
x3800
x3850
x3850
x3950
x3950
x3950
System x and System x servers with
an integrated systems management
module (IMM)
Note: The IMM internally contains a
BMC.
See the “System x and System x
servers with a Remote Supervisor
Adapter II or Remote Supervisor
Adapter II SlimLine” column in
Table 7 on page 29.
Note: On some of these systems,
installation of the Remote Supervisor
Adapter or Remote Supervisor
Adapter II service processor is
optional. If this optional service
processor is not installed, all
management occurs through either
an IPMI baseboard management
controller (BMC) or an integrated
systems management processor
(ISMP).
Restriction: When IBM Director
Agent 5.20.x or IBM Director Core
Services 5.20.x is installed, you can
manage Remote Supervisor Adapter
II or Remote Supervisor Adapter II
SlimLine in-band. When Common
Agent 6.1.x or 6.2.x, or Platform
Agent 6.1.x or 6.2.x are installed, you
are no longer 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.
28
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
M3 machine types 7327 and 7328
M2 machine types 4190, 4191, and 4194
M2 machine types 7836 and 7837
M3 machine types 7378 and 7379
M2 machine type 7839
M3 machine type 7380
M2 machine type 7946
M3 machine type 7944
M3 machine type 7376
M2 machine type 7947
M3 machine type 7945
X5 machine type 7148
M2 machine type 7233
X5 machine type 7145
M2 machine types 7141 and 7233
X5 machine type 7145
M2
M2
T
M2
E
M2
Installing agents on Linux for System x and preparing agentless managed systems
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
v
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
System
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
206
206m
225
226
232
236
255
260
305
306
306m
335
336
342
345
346
347
360
366
445
460
MXE 460
Table 6. Servers with service processors that are supported for Platform Agent or Common Agent management by
IBM Systems Director (continued)
Server type
Supported models
System x servers with an integrated
systems management processor
(ISMP)
v
v
v
v
v
v
v
See the “IBM BladeCenter and
System x servers with an integrated
systems management processor
(ISMP)” column in Table 7.
IBM Flex System compute nodes
with the integrated management
module II (IMM2)
System
System
System
System
System
System
System
x
x
x
x
x
x
x
232
235
255
335
342
343
345
v IBM Flex System x220 Compute
Node, Types 2585 and 7906
v
IBM Flex System x240 Compute
Node, Types 7863, 8737, and 8738
3. Identify the required drivers for in-band (Platform Agent or Common Agent)
management of the service processors for your server type and operating
system in Table 7.
RSA restriction: When IBM Director Agent 5.20.x or IBM Director Core
Services 5.20.x is installed, you can manage Remote Supervisor Adapter II or
Remote Supervisor Adapter II SlimLine in-band. When Common Agent 6.1.x or
6.2.x, or Platform Agent 6.1.x or 6.2.x are installed, you are no longer 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.
Table 7. Required drivers for in-band management of service processors
Operating system of
managed server
v Red Hat Enterprise
Linux, version 4
IBM BladeCenter,
System x, and System x
servers with an IPMI
baseboard management
controller (BMC) or
with an integrated
systems management
module (IMM)
eServer servers with an
IPMI baseboard
management controller
(BMC)
System x and System x
servers with a Remote
Supervisor Adapter II
or Remote Supervisor
Adapter II SlimLine
IBM BladeCenter and
System x servers with
an integrated systems
management processor
(ISMP)
OpenIPMI driver
OpenIPMI driver
RSA daemon
SMBus driver
LM78 driver
USB drivers
v Red Hat Enterprise
Linux, version 5.0
Other Red Hat
Enterprise Linux
distributions
LM78 driver
OSA IPMI driver
MSI IPMI driver
RSA daemon
IBM Mapping Layer
IBM Mapping Layer
USB drivers
LM78 driver
LM78 driver
OpenIPMI driver
RSA daemon
LM78 driver
USB drivers
OpenIPMI driver
v SUSE Linux
Enterprise Server 9 for
x86
v SUSE Linux
Enterprise Server 10
for x86
Other SUSE Linux
distributions
SMBus driver
SMBus driver
LM78 driver
OSA IPMI driver
MSI IPMI driver
RSA daemon
IBM Mapping Layer
IBM Mapping Layer
USB drivers
LM78 driver
LM78 driver
SMBus driver
Chapter 2. Preparing agentless managed systems
29
Table 7. Required drivers for in-band management of service processors (continued)
Operating system of
managed server
Virtual systems using
Xen
IBM BladeCenter,
System x, and System x
servers with an IPMI
baseboard management
controller (BMC) or
with an integrated
systems management
module (IMM)
eServer servers with an
IPMI baseboard
management controller
(BMC)
System x and System x
servers with a Remote
Supervisor Adapter II
or Remote Supervisor
Adapter II SlimLine
IBM BladeCenter and
System x servers with
an integrated systems
management processor
(ISMP)
OpenIPMI driver
OpenIPMI driver
RSA daemon
SMBus driver
LM78 driver
USB drivers
LM78 driver
VMware ESX Server,
versions 4.0, 4.0.1, and
4.1.
OpenIPMI driver
OpenIPMI driver
USB drivers
Other VMware
distributions
SMBus driver
LM78 driver
LM78 driver
OSA IPMI driver
MSI IPMI driver
Not supported
SMBus driver
IBM Mapping Layer
IBM Mapping Layer
LM78 driver
Windows Server 2008
MS IPMI driver
MS IPMI driver
RSA Library
The necessary drivers
are installed with
Common Agent or
Platform Agent.
Windows Server 2003 R2 MS IPMI driver
MS IPMI driver
RSA Library
The necessary drivers
are installed with
Common Agent or
Platform Agent.
USB drivers
Other Windows
operating systems
OSA IPMI driver
MSI IPMI driver
RSA Library
IBM Mapping Layer
IBM Mapping Layer
USB drivers
The necessary drivers
are installed with
Common Agent or
Platform Agent.
LM78 driver
4. Install the required drivers.
Note: If required, the MSI IPMI driver and the OSA IPMI driver must be
installed before the IBM Mapping Layer.
IBM Mapping Layer
The IBM Mapping Layer is used to translate IBM Systems Director
"generic" requests into driver-specific requests for different IPMI
drivers. Download this driver from the IBM Support Web Site at
www.ibm.com/support/us.
LM78 driver
The LM78 device driver ensures that IBM Systems Director Server
receives memory and processor Predictive Failure Analysis (PFA) alerts.
See “Installing IBM LM78 and SMBus device drivers” for installation
instructions.
MS IPMI driver
IBM Systems Director agent can use the Intelligent Platform
Management Interface (IPMI) driver included with Windows 2003 R2
and Windows 2008. In order for IBM Systems Director Server to
provide in-band alerting from the Baseboard Management Controller
(BMC) or Integrated Management Module (IMM), the MS IPMI driver
is required. By default, the MS IMPI driver is not installed with
Windows 2003 R2. To install the Microsoft IPMI device driver on
30
Installing agents on Linux for System x and preparing agentless managed systems
Windows 2003 R2, see “Managing IPMI Devices in Windows 2003 R2
and Windows 2008” in the IBM Systems Director Best Practices Wiki.
The MS IPMI driver is included with the Windows 2008 operating
system. No separate installation is required.
MSI IPMI driver
The MSI IPMI device driver is used to communicate with the IPMI
baseboard management controller. All other systems should use the
OSA IPMI driver. Download this driver from the IBM Support Web Site
at www.ibm.com/support/us.
OpenIPMI driver
This driver is included with the operating system. No separate
installation is required.
OSA IPMI driver
The OSA IPMI device driver is used to communicate with the IPMI
baseboard management controller. Download this driver from the IBM
Support Web Site at www.ibm.com/support/us.
RSA daemon
The RSA daemon is a Linux-only program that is used to interface with
the Remote Supervisor Adapter. Download this driver from the IBM
Support Web Site at www.ibm.com/support/us.
RSA library
The RSA library device driver is a Windows-only driver that is used to
interface with the Remote Supervisor Adapter. It also prevents driver
communication from interfering with IBM Systems Director. Download
this driver from the IBM Support Web Site at www.ibm.com/support/
us.
SMBus driver
The SMBus device driver ensures that configuration manager and
status manager tasks function correctly, and is used to communicate
with the integrated systems management processor (ISMP) on some
servers.
See “Installing IBM LM78 and SMBus device drivers for Linux” for
installation instructions.
USB drivers
The RSA daemon and RSA library use this driver to communicate with
the Remote Supervisor Adapter II. This driver is included with the
operating system. No separate installation is required.
5. Make sure that you have the latest firmware installed for your service
processors.
Chapter 2. Preparing agentless managed systems
31
Related concepts:
Platform agent
Common agent
Related tasks:
Installing the LM78 or SMBus device driver
Related reference:
Hardware and software requirements
Supported operating systems
Support Web site
Related information:
Unresponsive service processor
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.
The sudo utility is provided with Linux operating systems.
Before configuring access to agentless management systems for user accounts other
than root, read the following information:
v You must create and manage the sudo configuration file on each agentless
managed system that requires non-root based access.
v You must create a sudo configuration file that meets the requirements of your
security policies.
v You must create multiple credential mappings between IBM Systems Director
users and all of the agentless managed systems that IBM Systems Director is
managing using SSH.
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 an 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.
32
Installing agents on Linux for System x and preparing agentless managed systems
Note: To enable use of the Agent Installation Wizard to install and update agents,
ensure that the root user account was used to initially request access to the
managed system.
Related tasks:
Restarting Systems Director
Installing agents using the Agent Installation Wizard
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.
Note: This sample sudo configuration file is for example purposes only. Ensure
that you customize this sample file to meet the guidelines of your security policies.
Run visudo to edit the sudoers file.
#
#
#
#
#
#
#
#
#
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
# Disable "ssh hostname sudo <cmd>", because it will show the password in clear.
#
You have to run "ssh -t hostname sudo <cmd>".
#
Defaults
requiretty
Defaults:dirtest !requiretty
# 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
Chapter 2. Preparing agentless managed systems
33
# %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
dirtest ALL=(ALL)
NOPASSWD: ALL
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
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 35 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/.
34
Installing agents on Linux for System x and preparing agentless managed systems
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
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
Chapter 2. Preparing agentless managed systems
35
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 35 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 37 shows such a network configuration.
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/.
36
Installing agents on Linux for System x and preparing agentless managed systems
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
Related reference:
Systems
Preparing VMware managed systems
You might need to configure certain VMware systems before you can install agents
on them using the Agent Installation Wizard.
Managed systems running VMware ESX require the following configuration to
ensure that agents can be installed using the Agent Installation Wizard:
1. On the VMware managed system, open the /etc/ssh/sshd_config file in a text
editor.
2. Locate the following line:
Ciphers aes256-cbc,aes128-cbc
3. Change the line to:
Ciphers aes256-cbc,aes128-cbc,3des-cbc
4. Save and close the /etc/ssh/sshd_config file.
5. Stop and restart the ssh daemon. Type the following command:
service sshd restart
6. Use VMware vSphere Client Security Profile Properties to enable ibmsa and
ibmcim.
a. Using VMware vSphere Client, connect to a VMware ESX 4.x system.
Chapter 2. Preparing agentless managed systems
37
b. Click the Configuration tab.
c. Under Software, click Security Profile.
d. Select Properties and enable ibmsa and ibmcim.
7. Ensure the validity of any stored public key data for the target system in
root_SSH_data_directory/known_hosts on IBM Systems Director Server. See
“Common Agent cannot be installed on an AIX or Linux system” for more
information.
Related information:
Common Agent cannot be installed on an AIX or Linux system
38
Installing agents on Linux for System x 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 IBM Systems Director on Linux
Use the diruninstall and uninstall commands to uninstall IBM Systems Director
and its components (including the default database) on Linux for System p, Linux
for System x, or Linux for System z.
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.
On Linux, the diruninstall.server command and diruninstall.agent command
uninstall IBM Systems Director Server and Common Agent, respectively, and the
© Copyright IBM Corp. 1999, 2013
39
uninstall command uninstalls Platform Agent. The commands are located in
install_root/bin, where install_root represents the root directory of your IBM
Systems Director component installation:
IBM Systems Director Server
For diruninstall, the default value of install_root is /opt/ibm/director,
which creates the following command:
/opt/ibm/director/bin/diruninstall.server
Common Agent
For diruninstall.agent, the default value of install_root is
/opt/ibm/director/agent, which creates the following command:
/opt/ibm/director/agent/bin/diruninstall.agent
Platform Agent
For uninstall, the default value of install_root is /opt/ibm/platform, which
creates the following command:
/opt/ibm/platform/bin/uninstall
By default, this command removes all IBM Systems Director components, but you
can modify the script to remove specific components. The following files are not
removed in case other applications need them:
v TIVguid-1.3.0-0
Complete the following steps to uninstall IBM Systems Director and all of its
components on Linux.
1. From a command-line prompt, run the command that applies to your system:
v To uninstall IBM Systems Director Server on Linux systems, type the
following command and press Enter:
install_root/bin/diruninstall.server
v To uninstall Common Agent on Linux systems, type the following command
and press Enter:
install_root/bin/diruninstall.agent
v To uninstall Platform Agent and all of its components, type the following
command and press Enter:
install_root/bin/uninstall
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.
2. Ensure that the installed RPM packages were removed by executing the
following command:
rpm -qa --last | less
3. Remove the TIVguid package (and related folders) if it is not in use by another
product. The TIVguid package is not automatically removed in case it is
needed by another product.
Note: An example of a scenario in which you would leave the TIVguid
package installed is where you already manage a resource with IBM Systems
Director Server and plan to reinstall and continue to manage that resource. IBM
Systems Director Server will use TIVguid to identify the resource instance. If
TIVguid is removed and then the agent is reinstalled, IBM Systems Director
Server will treat the resource as a different system with the same IP address,
which can lead to confusion. Therefore, if you are going through this process of
uninstalling and reinstalling an agent, you should remove the agent from any
40
Installing agents on Linux for System x and preparing agentless managed systems
management servers that are managing it before performing the uninstallation.
Then perform a rediscovery after the agent has been reinstalled.
Attention: If you plan to uninstall IBM Systems Director and then install an
earlier release of IBM Systems Director, you must remove TIVguid. If you leave
the newer TIVguid on the system, the installation of common agent services
will fail.
If you determine that TIVguid is not needed elsewhere, use the following
command to remove it manually:
rpm -ev TIVguid
After the TIVguid package is removed, you can remove other related folders as
well.
Important: Ensure that the folders are empty before you remove them. Other
IBM or Tivoli software that is installed at these locations could be damaged if
you remove the folders.
Issue the following commands to remove the leftover folders:
rm
rm
rm
rm
rm
rm
rm
rm
rm
rm
rm
rm
rm
rm
rm
-rf /opt/ibm/icc
-rf /opt/ibm/director
-rf /opt/ibm/platform
-rf /opt/lsi
-rf /opt/adaptec
-rf /etc/ibm/icc
-rf /etc/ibm/director
-rf /etc/ibm/tivoli
-rf /etc/TWGagent
-rf /etc/tivguid
-rf /usr/ibm/tivoli
-f /var/log/dirinst.log
-rf /var/opt/ibm/platform
-rf /var/opt/ibm/icc
-rf /var/opt/lsi
4. If you uninstalled Platform Agent, you can remove the following folders and
files that were potentially left behind after the installation.
Important: Ensure that the folders are empty before you remove them.
/opt/adaptec
/opt/adaptec/serveraid
/opt/adaptec/serveraid/bin
/opt/adaptec/serveraid/lib
/opt/adaptec/serveraid/lib/NRMFSAConfig.xml
/opt/adaptec/serveraid/lib/NRMIROCConfig.xml
/opt/adaptec/serveraid/lib/NRMSRConfig.xml
/opt/adaptec/serveraid/logs
/opt/adaptec/serveraid/logs/adptlogs
/opt/adaptec/serveraid/logs/adptlogs/ADPTIndication.log
/opt/adaptec/serveraid/logs/adptlogs/adptprov.log
/opt/adaptec/serveraid/logs/adptlogs/NRMFSADebug.log
/opt/adaptec/serveraid/logs/adptlogs/NRMFSAEvents.log
/opt/adaptec/serveraid/logs/adptlogs/NRMIROCDebug.log
/opt/adaptec/serveraid/logs/adptlogs/NRMIROCEvents.log
/opt/adaptec/serveraid/logs/adptlogs/NRMSRDebug.log
/opt/adaptec/serveraid/logs/adptlogs/NRMSREvents.log
/opt/adaptec/serveraid/mof
/opt/ibm
/opt/ibm/icc
/opt/ibm/icc/cimom
/opt/ibm/icc/cimom/logs
/opt/ibm/icc/cimom/logs/raidController.txt
/opt/ibm/icc/cimom/logs/rpmLog
/opt/lsi
/opt/lsi/MR_Provider
Chapter 3. Uninstalling
41
/opt/lsi/MR_Provider/bin
/opt/lsi/MR_Provider/data
/opt/lsi/MR_Provider/lib
/opt/lsi/MR_Provider/mof
/opt/lsi/MR_Provider/sbma
/opt/lsi/MR_Provider/sbma/logs
/opt/lsi/MR_Provider/sbma/logs/SbmaTraceLog.txt
/opt/tivoli
5. If you uninstalled Common Agent, you can remove the following files and
folders that were potentially left behind after the installation.
/opt/tivoli/ep.reg
/opt/tivoli/ep.bak
/opt/ibm/director/agent
When you uninstall packages on Linux, the /etc/ibm/director/twgagent/
twgagent.uid file is retained to make it possible to restore persistent data.
When you uninstall IBM Systems Director Server, Common Agent, and Platform
Agent, the uninstallation does not remove any hardware drivers or daemons that
were installed with the product:
v The ibmusbasm or ibmusbasm64 RPM packages might remain after uninstallation.
These RPM packages are uninstalled only if an RSA II card is installed on the
system.
v The init service of the IPMI driver remains enabled after uninstallation. You can
disable the init service after uninstallation if no other services or applications
rely on this service.
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
42
Installing agents on Linux for System x 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 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.
© Copyright IBM Corp. 1999, 2013
43
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,
44
Installing agents on Linux for System x 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.
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
45
46
Installing agents on Linux for System x and preparing agentless managed systems
Printed in USA