IBM Systems Director
Installing IBM Systems Director agents on AIX and
preparing agentless managed systems
Version 6.3
IBM Systems Director
Installing IBM Systems Director agents on AIX and
preparing agentless managed systems
Version 6.3
Note
Before using this information and the product it supports, read the information in “Notices” on
page 27.
© Copyright IBM Corporation 1999, 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
Checklist: Installing agents . . . . . . xi
Chapter 1. Installing agents . . . . . . 1
Running the Pre-Installation Utility on an agent (AIX
and Linux) . . . . . . . . . . . . . . . 2
Installing Common Agent . . . . . . . . . . 3
Preparing for a Common Agent managed system 3
Preparing to install Common Agent on AIX . . 4
Installing agents using the Agent Installation
Wizard . . . . . . . . . . . . . . . 6
Installing Common Agent manually . . . . . . 9
Installing Common Agent on AIX . . . . . . 10
Installing Common Agent on Virtual I/O Server 14
Verifying the successful installation of an IBM
Systems Director agent . . . . . . . . . . 15
© Copyright IBM Corp. 1999, 2013
Chapter 2. Preparing agentless
managed systems . . . . . . . . . . 17
Configuring access to agentless managed systems
Sample sudo configuration file . . . . . .
Preparing AIX managed systems . . . . . .
Preparing to manage an IBM BladeCenter chassis
using IBM Systems Director Server on a non-blade
server . . . . . . . . . . . . . . .
Preparing to manage an IBM BladeCenter chassis
using IBM Systems Director Server on a blade
server . . . . . . . . . . . . . . .
Preparing Hardware Management Console devices
for discovery with IBM Systems Director . . .
17
. 18
. 19
. 20
. 21
. 23
Chapter 3. Uninstalling . . . . . . . . 25
Uninstalling IBM Systems Director on AIX .
.
.
. 25
Notices . . . . . . . . . . . . . . 27
Trademarks .
.
.
.
.
.
.
.
.
.
.
.
.
. 29
iii
iv
Installing agents on AIX 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 AIX 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 AIX 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 AIX and preparing agentless managed systems
Checklist: Installing agents
Use this checklist to guide you through the installation process.
1 Prepare your managed systems.
__ 1. Run the Pre-Installation Utility (2.
__ 2. Prepare systems for Common Agent (3).
__ 3. If relevant, prepare any agentless managed systems for discovery and
management by IBM Systems Director (17).
2 Install the agents.
__ 1. Use the Agent Installation Wizard to deploy agent packages to your
managed systems (6).
© Copyright IBM Corp. 1999, 2013
xi
xii
Installing agents on AIX 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:
– AIX:
gzip -cd package_name | tar -xvf -
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
Note: AIX does not support Platform Agent.
Linux
./checkds.sh -p [platformagent|commonagent]
For example:
./checkds.sh -p platformagent
2
Installing agents on AIX and preparing agentless managed systems
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.
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 Systems running AIX require Common Agent to be installed. These systems
cannot be managed with Platform Agent.
Note: The CIM Remote Service Access Point (RSAP), which is part of Common
Agent and Platform Agent, is not supported when requesting access to Common
Agent. Therefore, you will see the CIM RSAP when discovering AIX Common
Agent managed systems, but you cannot use it to request access to the AIX
system.
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
Chapter 1. Installing agents
3
Note: You must restart the ssh server for any changes made to sshd_config to take
effect.
Related reference:
Hardware requirements for systems running Common Agent or Platform
Agent
Preparing to install Common Agent on AIX
Before installing Common Agent on AIX, make sure that your platform meets the
applicable requirements.
Complete the following preparatory steps before installing Common Agent on AIX:
1. If you are running AIX server 7.1, complete the following steps to ensure that
the included version of Common Agent is completely removed before
installing the new version of Common Agent:
a. Uninstall the version of Common Agent that was included in AIX server
7.1.
b. If any of the following file sets still exist, uninstall them using the
installp -ug fileset_name command:
v DirectorCommonAgent
v cas.agent
v Director.DirectorCimCore
v
v
v
v
v
DirectorPlatformAgent
Director.CimExtension
Director.CimCore
sysmgt.cim.smisproviders.hba_hdr*
sysmgt.cim.smisproviders.hhr*
v sysmgt.cim.smisproviders.vblksrv*
v sysmgt.cim.providers.smash*
v sysmgt.cim.providers.osbase*
v sysmgt.cim.providers.metrics*
v sysmgt.cim.providers.scc*
v sysmgt.cimserver.pegasus.rte*
v tivoli.tivguid*
c. If any of the following directories still exist and are not empty, either
remove or empty them:
v /opt/ibm/director/
v /opt/ibm/icc
v
v
v
v
v
/etc/ibm/director
/etc/ibm/tivoli
/usr/tivoli/guid
/usr/pegasus
/var/opt/tivoli/ep
v /var/cim/
v /opt/freeware/cimom/pegasus
d. If the installation fails with a parsing error similar to “Could not find
declaration for Qualifier named Provider”, the CIM repository is corrupt
and the cimserver cannot start. In this case, you need to remove the
following additional directories, if they still exist:
4
Installing agents on AIX and preparing agentless managed systems
v /var/cim/rebuild_repository.lock
v /opt/freeware/cimom/pegasus/etc/repository
2. 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.
3. Ensure that your system meets the hardware and software requirements. To
verify the AIX operating system level, run the following command:
oslevel -s
The command should return a value such as 5300-09-00-nnn, where nnn is
irrelevant.
4. Optional: Download updates for your system, if necessary. Download AIX
updates from the "Fix Central" Web site.
Note: Select “IBM Power®” or “System p®” for the Product family and “AIX”
for the Product.
5. Ensure that, if they are installed, openssl and openssh are at the following
versions:
v openssl.base 0.9.8.4 or higher
v openssh.base.server 4.5.0.5301 or higher
There is a dependency between openssl and openssh versions. If openssl is
not installed, it is installed as part of the server or agent installation. However,
if this would create an inconsistency with the openssh version on the system,
openssl is not installed and the installation fails.
Note: If you want to run the Agent Installation Wizard from the server,
openssh is required. However, the server installation does not enforce openssh
installation.
6. Ensure that the following file sets that are required for and installed with
Common Agent on AIX will not conflict with any other applications that are
installed on your system:
v
v
v
v
v
sysmgt.cim.providers 1.2.9.30
sysmgt.cim.smisproviders 1.2.2.30
sysmgt.cimserver.pegasus 2.9.1.30
ICU4C.rte 5.3.9.0 (only AIX 5.3 systems)
xlC.aix50 10.1.0.2 (only AIX 5.3 systems)
v xlC.rte 10.1.0.2 (only AIX 5.3 systems)
7. Verify /etc/hosts and /etc/netsvc.conf settings to ensure the success of IP
address lookups for loopback. For more information, see Agent install timeout
due to localhost lookup in the IBM Systems Director Best Practices Wiki.
8. Ensure that nofiles is set to a value other than unlimited. To specify an
appropriate value, run the following command:
chsec -f /etc/security/limits -s root -a nofiles=value
where value is a value such as 3000.
9. Ensure that the installation is set to use ports that are not already in use. By
default, Common Agent requires ports 9510, 9514, and 9515 during installation
and at runtime. If these ports are already in use when you install the agent,
the installation will fail. A situation where these ports will be already in use is
if you have a different version of the CAS agent installed, for example as part
of the Tivoli Provisioning Manager agent.
Chapter 1. Installing agents
5
Complete the following steps to check for port use and, if any are in use,
modify the Common Agent configuration to use different ports:
a. Check if the ports are in use by running the following command:
netstat -an | grep LISTEN | egrep "951(0|4|5)"
b. On the agent system, modify the configuration to use different ports by
running the following command:
/var/opt/tivoli/ep/runtime/agent/toolkit/bin/configure.sh -unmanaged -port
not_9510 -jport not_9514 -nport not_9515 -force
where not_951x is any open port other than 951x.
c. Rerun the installation script or install the Common Agent file set manually.
10. 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
Updating Systems Director
Related reference:
Hardware and software requirements
Supported operating systems
Related information:
AIX installation troubleshooting
Common Agent cannot be installed on an AIX or Linux system
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.
6
Installing agents on AIX and preparing agentless managed systems
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
Chapter 1. Installing agents
7
– 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.
8
Installing agents on AIX and preparing agentless managed systems
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”.
Notes for AIX:
v Refer to “Installing Common Agent on AIX” for more detail on the
self-extracting script and the response file options.
v For AIX server and agents, it is less space consuming to remotely install
agents using NIM as explained in the IBM Systems Director Best Practices
wiki page “Installing IBM Systems Director Common Agent for AIX using
NIM” at http://www.ibm.com/developerworks/wikis/display/WikiPtype/
Installing+IBM+Systems+Director+Common+Agent+for+AIX+using+NIM.
Installing with NIM does not allow the use of a response file.
You can view the status of the agent installation job by clicking Task Management
> Active and Scheduled Jobs.
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:
Chapter 1. Installing agents
9
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 Systems running AIX require Common Agent to be installed. These systems
cannot be managed with Platform Agent.
Note: The CIM Remote Service Access Point (RSAP), which is part of Common
Agent and Platform Agent, is not supported when requesting access to Common
Agent. Therefore, you will see the CIM RSAP when discovering AIX Common
Agent managed systems, but you cannot use it to request access to the AIX
system.
v Ensure that the system clocks on the systems that contain IBM Systems Director
Server and Common Agent remain synchronized.
Related tasks:
Preparing a Common Agent managed system
Installing Common Agent on AIX
To install Common Agent on a system that is running AIX, download the
installation files from the IBM Systems Director support Web site or, if available for
this release, use the DVD. You can perform the installation manually or by using
the Installation wizard. Both methods allow the use of a response file to customize
the installation for your organization. You can alternatively perform the installation
by using installp or nim, neither of which methods allow the use of a response file.
Important:
v Installation of IBM Systems Director Server on AIX installs IBM Systems Director
Server and Common Agent together. (AIX systems do not support Platform
Agent as a stand-alone agent, so installing Platform Agent is not an option.)
Therefore, it is not necessary to separately install Common Agent on the
management server after installing IBM Systems Director Server. In most cases,
any IBM Systems Director tasks requiring Common Agent will be performed for
systems with IBM Systems Director Server installed.
v Ensure that the system clocks on the systems that contain IBM Systems Director
Server and Common Agent remain synchronized.
v By default, Common Agent is started when your system is rebooted. You can
disable this function with the steps in the “Disabling IBM Systems Director
agents” topic.
v Common Agent is not supported to run in an AIX workload partition (WPAR).
v Common Agent and Platform Agent are now shipped as part of the AIX
operating system. For a mapping of agent versions shipped with each AIX
version, see https://www.ibm.com/developerworks/mydeveloperworks/wikis/
home?lang=en#/wiki/W3e8d1c956c32_416f_a604_4633cd375569/page/Common
%20Agent%20versions%20shipped%20with%20AIX%20and%20VIOS.
Depending on the version of Common Agent that you are installing, you can
install Common Agent on AIX from either installation media or from a
downloaded installation package.
Important: The IBM Systems Director Server and Common Agent installation
packages for AIX are provided in English only.
10
Installing agents on AIX and preparing agentless managed systems
Table 2. Installation options for Common Agent on AIX
Installation method
Title or file name
Downloaded installation
package
v SysDir6_3_3_Common_Agent_Installp_AIX_VIOS.tar.gz
(for installp or NIM installation)
v SysDir6_3_3_Common_Agent_AIX.tar.gz (for script
installation, as described here)
v SysDir6_3_3_Common_Agent_AIX.jar (agent package for
Agent Installation Wizard installation)
Note: For more information about using installp or NIM to install Common Agent,
see the IBM Systems Director Best Practices Wiki for installing on IBM Power. Do
not use the force overwrite installp option with installp or NIM to force install an
older agent file set over a newer agent file set. When you update or force install
the agent, ensure you always install the cas.agent and DirectorCommonAgent file
sets as a pair to avoid corrupting the agent configuration.
Note: Common Agent is installed by default in unmanaged mode. When IBM
Systems Director Server discovers an unmanaged agent, the agent becomes
managed after requesting access. However, if you want the agent to start out in
managed mode, for example because IBM Systems Director Server is configured
with more than one agent manager and you want to choose the agent manager
with which the agent associates, you can do so using one of the following two
methods:
Install the agent in managed mode
To install the agent in managed mode, 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.
The following process uses a self-extracting script that requires temporary space in
the /tmp directory to extract the file sets. This is as specified in “Hardware
requirements for systems running Common Agent or Platform Agent”. If /tmp does
not have enough space to extract the files, the installation will fail. If /tmp is a JFS2
file system, you can specify in the diragent.rsp agent response file that /tmp is
temporarily extended and should shrink back to its original size after the agent
installation is complete. The default is to not extend /tmp. The files in /tmp are
deleted after a successful installation. If the extraction or installation fails, the size
of the/tmp file system might not decrease to its original size and it might retain
files. The files are extracted into /tmp/DirectorAgentselfextract.identifier.
The self-extracting script does not offer an installation preview option.
Chapter 1. Installing agents
11
Log in as the root user and complete the following steps to install Common Agent
on AIX:
Tip: You can find the installation logs for this process in /var/log/dirinst.log
and /opt/ibm/director/agent/log/installFeatures_date.log.
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 unzip and extract the contents of the installation package to a local
directory, type one of the following commands:
gzip -cd SysDir6_3_3_Common_Agent_AIX.tar.gz | tar -xvf -
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.
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.
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
The following parameter relates to the size of the /tmp file system. The
default is EXTEND_TMP = 0.
EXTEND_TMP = 0
This instructs /tmp to remain at its default size. If you choose to
keep this setting, ensure that /tmp is large enough to accommodate
the agent file sets.
12
Installing agents on AIX and preparing agentless managed systems
EXTEND_TMP = 1
If /tmp is a JFS/JFS2 file system and there is not enough space in
/tmp to extract the agent file sets, set EXTEND_TMP = 1 to extend /tmp
and then shrink it back to its original size after the agent installation
is done. However, if /tmp is a JFS file system, it is not shrunk to its
original size after the agent installation is done.
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, type one of the following commands, and press Enter:
v To accept the default settings:
./dir6.3.3_commonagent_aix
v To use the response file:
./dir6.3.3_commonagent_aix -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_aix -x extract_directory
where extract_directory is the local directory into which you want to extract
the installation files.
The option to expand the /tmp file system cannot be combined with the -x
option.
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.
If you have not already merged and installed the updates as part of the
installation, then you can use update manager to update to the latest version of
IBM Systems Director. See “Updating IBM Systems Director” for instructions.
Note: Before performing an update, you will need to understand disk space
requirements. For information on disk space requirements for updates, see
“Determining disk space requirements for applying updates” or the IBM Systems
Director Best Practices Wiki.
See “Restarting Common Agent” for information about how to stop, start, and
obtain the status of Common Agent.
AIX systems do not support Platform Agent as a standalone agent. However,
Common Agent includes Platform Agent, which means that you can still manage
it.
See “Restarting Platform Agent” for information about how to stop, start, and
obtain the status of Platform Agent.
Chapter 1. Installing agents
13
Related tasks:
Preparing to install Common Agent on AIX
Importing agent packages
Updating Systems Director
Upgrading and migrating agents
Disabling Systems Director agents
Restarting Common Agent
Restarting Platform Agent
Related reference:
Systems Director Downloads
Systems Director Best Practices Wiki - Installation (Power Systems)
Related information:
AIX installation troubleshooting
Exchanging information with IBM
Installing Common Agent on Virtual I/O Server
To install Common Agent on a system that is running Virtual I/O Server,
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,
install using installp or NIM, or you can use a response file to customize the
installation for your organization.
Important:
v Ensure that the system clocks on the systems that contain IBM Systems Director
Server and Common Agent remain synchronized.
v Common Agent and Platform Agent are now installed with Virtual I/O Server.
For a mapping of agent versions shipped with each Virtual I/O Server version,
see the IBM Systems Director Best Practices Wiki.
v You can also download Common Agent for installation on Virtual I/O Server
2.1.0.1 FP20.1 or higher using installp.
See Installing Common Agent on VIOS and IVM on the IBM Systems Director Best
Practices Wiki for instructions.
To ensure full functionality of your new Common Agent instance, discover it with
IBM Systems Director Server.
If you have not already merged and installed the updates as part of the
installation, then you can use update manager to update to the latest version of
IBM Systems Director. See “Updating IBM Systems Director” for instructions.
Note: Before performing an update, you will need to understand disk space
requirements. For information on disk space requirements for updates, see
“Determining disk space requirements for applying updates” or the IBM Systems
Director Best Practices Wiki.
14
Installing agents on AIX and preparing agentless managed systems
Related tasks:
Updating Systems Director
Related reference:
Systems Director Downloads
Systems Director Best Practices Wiki - Installation (VIOS)
Verifying the successful installation of an IBM Systems Director agent
You can verify a successful installation by starting IBM Systems Director Server,
logging into the Web interface, and discovering the new managed system.
To verify that the agent installation was successful and ensure your managed
systems can be discovered, complete the following steps:
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.
Chapter 1. Installing agents
15
Related tasks:
Logging in
Discovering systems with system discovery
Collecting and viewing inventory data
Importing agent packages
16
Installing agents on AIX 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
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.
To use the sudo utility with AIX systems, you will need to download and install
the utility from the AIX Toolbox Download Web site.
© Copyright IBM Corp. 1999, 2013
17
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.
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
18
Installing agents on AIX and preparing agentless managed systems
# 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
# %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 AIX managed systems
You might need to configure certain AIX systems before you can discover them
with IBM Systems Director Server. Ensure that each AIX system that you want to
manage has been appropriately configured.
Typically, managed systems are first discovered using the discovery task in IBM
Systems Director Web interface. Then, Platform Agent or Common Agent is
installed on the managed systems directly from IBM Systems Director Web
interface. The configuration of some AIX managed systems, however, can prevent
discovery by IBM Systems Director Server.
Chapter 2. Preparing agentless managed systems
19
Note: If an agentless system is running openssh 4.7.0.530, you cannot use the
Agent Installation Wizard to remotely install the agent on AIX.
Complete the following steps on each AIX system to enable discovery by IBM
Systems Director Server:
1. Check if sshd is running by running the following command:
lssrc -s sshd
2. If sshd is not running, run the following command to start it:
startsrc -s sshd
Related reference:
Hardware and software requirements
Supported operating systems
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 21 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/.
20
Installing agents on AIX 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
21
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 21 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 23 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/.
22
Installing agents on AIX 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 Hardware Management Console devices for discovery with
IBM Systems Director
Before discovering Hardware Management Console (HMC) devices, and after
upgrading HMC hardware, you might need to open the Pegasus and SLP ports to
enable IBM Systems Director to discover and manage the HMC.
Complete the following steps to enable the Pegasus and SLP ports on the HMC
device:
1. In the HMC Navigation Area pane, click HMC Management.
2. In the HMC Management pane, click Change Network Settings.
3. In the Customize Network Settings window, click the LAN Adapters tab.
4. Select the LAN Adapter that is connected to your LAN and click Details.
5. In the LAN Adapter Details window, click the Firewall Settings tab. The
Available Applications table displays a list of applications, with their
associated port numbers, that are recognized by the HMC. The Allowed Hosts
table displays a list of only those applications for which the HMC firewall is
configured to allow access to the HMC.
Chapter 2. Preparing agentless managed systems
23
Note: If a scroll bar appears on the table, use it to view all the applications in
the table.
6. In the Available Applications table, select Open Pegasus and click Allow
Incoming. Open Pegasus is added to the Allowed hosts table of enabled ports.
7. In the Available Applications table, select SLP and click Allow Incoming. SLP
is added to the Allowed hosts table of enabled ports.
8. Click OK; then click OK again.
9. If a message window about restarting the HMC is displayed, click OK. After
the HMC is restarted, the ports are enabled and IBM Systems Director Server
can discover the HMC.
Related tasks:
Discovering VIOS servers managed by an HMC
Related reference:
Hardware and software requirements
Supported operating systems
AIX Pegasus CIM server and providers
24
Installing agents on AIX 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 AIX
Use the diruninstall command to uninstall IBM Systems Director and its
components (including the default database) on AIX.
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.
The diruninstall command is located in the install_root/bin directory, where
install_root represents the root directory of your IBM Systems Director installation.
The default value of install_root is /opt/ibm/director. By default, this command
© Copyright IBM Corp. 1999, 2013
25
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
v
v
v
v
cas.agent
sysmgt.cimserver.pegasus
sysmgt.cim.providers
sysmgt.cim.smisproviders
tivoli.tivguid
Complete the following steps to uninstall IBM Systems Director and all of its
components on AIX.
From a command-line prompt, type the following command and press Enter:
install_root/bin/diruninstall
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.
For information about how to remove the file sets that are not removed by the
diruninstall script and how to recover from a failed installation, see Uninstall IBM
Systems Director on AIX in the IBM Systems Director Best Practices Wiki.
When you uninstall packages on AIX, the /etc/ibm/director/twgagent/
twgagent.uid file is retained to make it possible to restore persistent data.
26
Installing agents on AIX 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
27
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
Dept. LRAS/Bldg. 903
11501 Burnet Road
Austin, TX 78758-3400
U.S.A
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. You may copy,
28
Installing agents on AIX 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
29
30
Installing agents on AIX and preparing agentless managed systems
Printed in USA