Skip Headers
Oracle® Enterprise Manager Grid Control Installation and Configuration Guide
10g Release 5 (10.2.0.5.0)

Part Number E10953-15
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

12 Deploying Management Agent on a Cluster

This chapter explains how a Management Agent can be deployed in a cluster-based environment. One of the options of installing a Management Agent in your environment is to install it individually on each computer. This is convenient when you want to install Management Agents only on a few computers. However, if your network is large and you have multiple computers grouped as a cluster, then installing Management Agents on all the computers, without using the available cluster, can be time-consuming and tasking.

Enterprise Manager 10g Grid Control Release 2 (or higher) offers a feature that helps you install Management Agents on multiple computers associated with a cluster, in a single installation, by pointing only to that cluster. This saves time and effort, as you reference only a cluster and have the Management Agent installed on all or some of the nodes of that cluster, in one attempt.

Therefore, if you have clusters in your environment, then use this feature to install a Management Agent either on each node of a cluster, individually, or on one or more nodes of a cluster, in a single installation. The clusters supported are Release 9.2 Clusters and Oracle Clusterware.

Caution:

The agent Oracle home cannot be installed in an Oracle Cluster Shared File System (OCFS) drive, but is supported on a NAS (Network Attached Storage) drive.

The following explains how Management Agents can be installed on Release 9.2 Clusters and Oracle Clusterware.

Table 12-1 Deploying Management Agent on a Cluster

 

Installation on 9.2 Cluster

Installation on Oracle Clusterware

Method 1

Installing Management Agent on Each Node of a Cluster, Individually

Method 2

Installing Management Agent on Many Nodes of a Cluster, in One Installation

A Management Agent can be installed on 9.2 Cluster in any of the following ways:

  • Using agentDownload script

  • Using Agent Deploy application

  • Using Oracle Universal Installer (OUI)

A Management Agent can be installed on Oracle Clusterware in any of the following ways:

  • Using agentDownload script

  • Using Agent Deploy application

  • Using Oracle Universal Installer (OUI)


IMPORTANT:

You cannot use addnode.sh script to extend Management Agents in a cluster.

Installing Management Agent on Each Node of a Cluster, Individually

One of the ways to install a Management Agent in a cluster-based environment is to install it on each node of a cluster, individually. This can take more time, as it involves installation of Management Agent on each and every node of a cluster. You use the cluster only to identify the nodes associated with it, but not to perform the installation on multiple nodes at a time.

Note:

If the installation fails, review the log files described in Appendix C, "Agent Log Files".

Installing Management Agent on Release 9.2 Cluster

This section explains how a Management Agent can be installed on each node of a cluster, individually, on a Release 9.2 Cluster.

Using the agentDownload Script

A Management Agent can be installed by running the agentDownload script on one node at a time using the correct arguments.

If you want to discover the cluster targets, then you must set the CLUSTER_NAME environment variable before running the agentDownload script, or pass the cluster name to the agentDownload script as agentDownload -n <clustername>.

agentDownload -b <Oracle Base Directory location> -n <clustername>

For detailed instructions, see Installing Management Agent Using agentDownload Script.

Note:

If the CLUSTER_NAME environment variable is not set, the agent cannot discover any cluster targets.

Using the Agent Deploy Application

A Management Agent can be installed using the Agent Deploy application that is part of Enterprise Manager Grid Control (Grid Control).

While using the Agent Deploy application to install a Management Agent on a cluster node, you must select the appropriate node of that cluster. If you want to discover the cluster targets, you must specify the correct cluster name in the Cluster Name field.

For detailed instructions, see Fresh Installation of the Management Agent.

Note:

Ensure the nodes that you select for the agent installation are part of the cluster that you have specified in the Cluster Name field. Otherwise, the targets are not discovered.

Using Oracle Universal Installer

A Management Agent can be installed by invoking the installer using Oracle Universal Installer (OUI). The interactive type is typically a one-node installation.

In this case, you can set the CLUSTER_NAME environment variable to the name of the cluster that you want to use for the cluster targets, before invoking the installer, that is the runInstaller script. If this variable is not set, the agent cannot discover any cluster targets.

For detailed instructions, see Installing Management Agent Using OUI.

Installing Management Agent on Oracle Clusterware

This section explains how a Management Agent can be installed on each node of Oracle Clusterware, individually.

Using agentDownload Script

A Management Agent can be installed by running the agentDownload script on one node at a time using the correct arguments.

If you want to override the cluster name to be used in targets.xml file, you must set the CLUSTER_NAME environment variable prior to executing the agentDownload script, or pass the cluster name to the agentDownload script as agentDownload -n <clustername>.

agentDownload -b <Oracle Base Directory location> -n <clustername>

Note:

If the CLUSTER_NAME environment variable is not set or passed, the agent uses the cluster name that was specified during the Oracle Clusterware installation.

For detailed instructions, see Installing Management Agent Using agentDownload Script.

Using the Agent Deploy Application

A Management Agent can be installed using the Agent Deploy application that is part of Grid Control.

While using the Agent Deploy application to install a Management Agent on a cluster node, you must select the Cluster Install option, and specify the appropriate cluster node names. The cluster name that you specify here overrides the corresponding value in the targets.xml file.

For detailed instructions, see Fresh Installation of the Management Agent.

Using Oracle Universal Installer

The Management Agent can be installed by invoking the installer using Oracle Universal Installer (OUI).

If you want to set the cluster name that will appear in targets.xml file, then you must set the CLUSTER_NAME environment variable before invoking the runInstaller. If this variable is not set, then the agent uses the cluster name that was specified during the Oracle Clusterware installation.

For detailed instructions, see Installing Management Agent Using OUI.

Installing Management Agent on Many Nodes of a Cluster, in One Installation

The other way to install a Management Agent in a cluster-based environment is to install it on one or more nodes of a cluster, at a time, in a single installation. This can may not take time (though it depends on the size of the cluster), as it involves installation of Management Agent on multiple nodes of a cluster, at a time, in parallel, in a single installation attempt. You use the cluster not only to identify the nodes associated with it, but also to perform the installation on multiple nodes.

Caution:

While installing a Management Agent on multiple nodes of a Oracle Cluster that is running on a Microsoft Windows platform, only the host and cluster targets will be discovered during the installation.

To discover all other targets, you must run the following on each node of that cluster:

Agent Home>/bin/agentca -d -n <Cluster Name> -c <node name>

Note:

If the installation fails, review the log files described in Appendix C, "Agent Log Files".

Installing Management Agent on Release 9.2 Cluster

This section explains how a Management Agent can be installed on one or more nodes of a Release 9.2 Cluster, at a time, in a single installation.

Using the agentDownload Script

A Management Agent can be installed by running the agentDownload script with the -c option (for example, -c "node1,node2,..."). This option helps you install the Management Agent on one or more nodes that you specify.

If you want to override the cluster name that appears in targets.xml, then you must set the CLUSTER_NAME environment variable before running the agentDownload script, or pass the cluster name to the agentDownload script as agentDownload -b <Oracle Base Directory location> -n <clustername> -c "node1,node2,node3".

For detailed instructions, see Installing Management Agent Using agentDownload Script.

Using the Agent Deploy Application

A Management Agent can be installed using the Agent Deploy application that is part of Grid Control.

While using the Agent Deploy application to install a Management Agent on multiple nodes of a cluster, you must select the Cluster Install option and specify all the nodes of that cluster.

If you want to discover the cluster targets, then you must specify the correct cluster name in the Cluster Name field.

For detailed instructions, see Fresh Installation of the Management Agent.

Using Oracle Universal Installer

A Management Agent can be installed by invoking the installer using Oracle Universal Installer (OUI).

Ensure that you pass the CLUSTER_NODES variable when starting the installer, that is the runinstaller script, like this:

./runInstaller "CLUSTER_NODES={node1,node2,node3}"

If the CLUSTER_NODES variable is not passed, then the installer cannot detect the nodes and cannot perform the cluster install.

If you want to set the cluster name that appears in the targets.xml file, you must set the CLUSTER_NAME environment variable before invoking the runInstaller. If this variable is not set, the agent uses the first node as the cluster name.

For detailed instructions, see Installing Management Agent Using OUI.

Installing Management Agent on Oracle Clusterware

This section explains how a Management Agent can be installed on one or mode nodes of Oracle Clusterware, at a time, in a single installation.

Using the agentDownload Script

A Management Agent can be installed by running the agentDownload script with the -c option (for example, -c "node1,node2,..."). This option helps you install the Management Agent on one or more nodes that you specify here.

If you want to override the cluster name that appears in targets.xml file, then you must set the CLUSTER_NAME environment variable prior to executing the agentDownload script, or pass the cluster name to the agentDownload script as agentDownload -b <Oracle Base Directory location> -n <clustername> -c "node1,node2,node3".

Note:

If the CLUSTER_NAME variable is not set or passed, the agent uses the cluster name that was specified during the Oracle Clusterware installation.

For detailed instructions, see Installing Management Agent Using agentDownload Script.

Using the Agent Deploy Application

A Management Agent can be installed using the Agent Deploy application that is part of Grid Control.

While using the Agent Deploy application to install a Management Agent on multiple nodes of a cluster, you must select the Cluster Install option and specify all the nodes of that cluster.

If you want to override the cluster name that appears in targets.xml file, you must specify the appropriate cluster name in the application.

For detailed instructions, see Fresh Installation of the Management Agent.

Using Oracle Universal Installer

A Management Agent can be installed by invoking the installer using Oracle Universal Installer (OUI).

When you execute the runInstaller script, it automatically detects all the cluster nodes. You can then choose the nodes on which you want to install the Management Agent.

If you want to override the Cluster name that appears in targets.xml, you must set the CLUSTER_NAME environment variable before invoking the runInstaller. If this variable is not set, the agent uses the cluster name that was specified during the Oracle Clusterware installation.

For detailed instructions, see Installing Management Agent Using OUI.