how to configure grid control agents to monitor virtual hostname in ha environments

7/31/2019 How to Configure Grid Control Agents to Monitor Virtual Hostname in HA Environments

1/4

How to Configure Grid Control Agents to Monitor Virtual Hostname in HA environments

[ID 406014.1]

Modified04-SEP-2010 Type WHITE PAPER Status PUBLISHED

In this DocumentAbstractDocument HistoryHow to Configure Grid Control Agents to Monitor Virtual Hostname in HA environments

Overview and RequirementsInstallation and Configuration

SummaryReferences

Applies to:

Enterprise Manager Grid Control - Version: 10.2.0.1 to 11.1.0.1 - Release: 10.2 to 11.1Information in this document applies to any platform.

Abstract

Scope and Application:

Grid Control 10.2.0.1 +All Unix platforms; for Windows useNote 464191.1This document provides a general reference for Grid Control administrators on configuring 10g Grid Control

agents in Cold Failover Cluster (CFC) environments

Document History

Last Updated 04-SEP-2010Expire Date 03-SEP-2010

How to Configure Grid Control Agents to Monitor Virtual Hostname in HA environments

Overview and Requirements

In order for Grid Control agent to fail over to a different host, the following conditions must be met:

1. Installations must be done using a Virtual Hostname associated with a unique IP address.2. The virtual hostname used for the group, must be used for any service that runs inside this virtual group.For example: listeners, HTTP servers, iAS etc must use the virtual hostname.3. Install on a shared disk/volume, which holds the binaries, configuration and runtime data.**4. Configuration data and metadata must also failover to the surviving node5. Inventory location must failover to the surviving node6. Software owner and timezone parameters must be the same on all cluster member nodes that will hostthis agent

** Note: Any reference to shared could also be true for non-shared failover volumes, which can be mountedon active hosts after failover.

An agent must be installed on each physical node in the cluster to monitor the local services.
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#WP_ABSTRACThttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#WP_ABSTRACThttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#WP_DOCHISThttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#WP_DOCHISThttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#WP_BODYhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#WP_BODYhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#aref1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#aref1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#aref2https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#aref2https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#WP_SUMMARYhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#WP_SUMMARYhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#REFhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#REFhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=464191.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=464191.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=464191.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=464191.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#REFhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#WP_SUMMARYhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#aref2https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#aref1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#WP_BODYhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#WP_DOCHISThttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#WP_ABSTRACT


2/4

An alternate solution for CFC deployments, Grid Control 10.2.0.4 offers a "relocate_target" feature usingEMCLI, where the physical agent monitors all virtual services hosted by the physical cluster member.SeeNote 577443.1for details.

Installation and Configuration

A. Setup the Virtual Hostname/Virtual IP Address

The virtual hostname must be static and resolveable consistently on the network. All nodes participating inthe setup must resolve the virtual IP address to the same hostname. Standard TCP tools such as "nslookup"and "traceroute" can be used to verify the hostname. Validate using the commands listed below

nslookup -> returns the virtual IP address and fully qualified hostname

nslookup -> returns the virtual IP address and fully qualified hostname

Make sure to try these commands on every node of the cluster, and verify that the correct information isreturned.

B. Setup Shared Storage

This can be storage managed by the clusterware that is in use, or you can use any shared file system (FS)volume as long as it is not an unsupported type, such as OCFS V1. The most common shared FS is NFS.

You can also use non-shareable volumes that are mounted upon failover to the succeeding host. (Such isthe case in Windows environments)

C. Setup the Environment

Before you launch the installer, certain environment variables need to be verified. Each of these variablesmust be set identical for the account installing the software on ALL machines participating in the cluster:

OS variable TZ (All cluster member nodes must be time synchronized)

Timezone setting. It is recommended to unset this variable prior to installation

PERL variables

Variables like PERL5LIB should also be unset to prevent from picking up the wrong set of PERLlibraries

D. Synchronize OS User IDs

The user and group of the software owner should be defined identically on all nodes of the cluster. This can

be verified using the id command:

$ id auid=550(oracle) gid=50(oinstall) groups=501(dba)
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=577443.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=577443.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=577443.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=577443.1


3/4

The agent software owner must be a member of the targets primary group if you are using a different userfor each software home.

E. Setup Inventory

Each failover group or virtual hostname package should have its own inventory. Use the same inventorywhen you install the agent inside each virtual group. This is accomplished by pointing the installer to thegroups oraInst.loc file using -invPtrLoc parameter.

F. Install the Software:

1. Run the installer using the inventory location file oraInst.loc as well as specifying the hostname of thevirtual group. For example:

runInstaller -invPtrLoc /app/oracle/share1/oraInst.loc ORACLE_HOSTNAME=lxdb.acme.com debug

(-debug parameter is optional)(For 11g agents, you must use a response file for silent installations)

Modifiche Response fileSECURITY_UPDATES_VIA_MYORACLESUPPORT=falseDECLINE_SECURITY_UPDATES=trueINSTALL_UPDATES_SELECTION=skipORACLE_AGENT_HOME_LOCATION=/u01/oracle/b_silentInstall =trueOMS_HOST=xxxxxx.xxxxxx.com The grid control oms server. OMS_PORT=4889AGENT_REGISTRATION_PASSWORD=xxxxxxxFROM_LOCATION=/u01/oracle/stage/aix/agent/stage/products.xml

2. Continue the rest of the installation normally.

Note: Agents will be installed using the default port 3872. By default, each agent is configured to listen onall NIC's. This may cause failure for each subsequent agent startup. To avoid this problem, edit the localagent's emd.properties file and change:

AgentListenOnAllNICs=TRUE

to

AgentListenOnAllNICs=FALSE

Then bounce the local agent.

You can set this value for each additional agent to avoid startup failures.

G. Startup of Services:

Ensure that you start your services in the proper order:

Note: ORACLE_HOSTNAME must be set when running any emctl command to control the virtual agent.

- establish IP address on the active node- start all services normally except the agent- unset all environment variables such as ORACLE_HOME, *LIB*, ORACLE_SID, PERL5LIB etc.


4/4

- cd to the agent home / bin directory- start the agent

In case of failover

- Establish IP on failover node

- start all services normally except the agent- unset all environment variables such as ORACLE_HOME, *LIB*, ORACLE_SID, PERL5LIB etc.- cd to the agent home / bin directory- start the agent

Summary

If you have a large number of virtual groups to monitor on each cluster node, you may want to consider usingonly one agent on each cluster node (physical host) and use EMCLI to relocate targets as they failover toother cluster nodes.

Note 577443.1How to Setup and Configure Target Relocate using EMCLI

References

NOTE:330072.1- How To Configure Grid Control Components for High AvailabilityNOTE:405642.1- How to Configure Grid Control OMS in Active/Passive CFC Environments failover / HANOTE:405979.1- How to Configure Grid Control Repository in Active/Passive HA environmentsNOTE:464191.1- How to Configure Grid Control Agents in Windows HA - Failover Cluster EnvironmentsNOTE:549270.1- How to configure Grid Control 10.2.0.4 Management Servers behind a Server LoadBalancer (SLB)NOTE:577443.1- How to Setup and Configure Target Relocate using EMCLI

Enterprise Manager Maximum Availability Architecture (MAA) Best Practicesathttp://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_EnterpriseManagerBestPractices.pdfFor Fail Safe deployments, pleaseseehttp://download.oracle.com/docs/html/B25003_01/toc.htm#BABCHGJDAdvanced ConfigGuidehttp://download.oracle.com/docs/cd/B16240_01/doc/em.102/e10954/actpass_env.htm#CHDHAHCB

Related

Products

Enterprise Management > Enterprise Manager Consoles, Packs, and Plugins > Enterprise

Manager Grid Control > Enterprise Manager Grid Control

Keywords

FAILOVER; CLUSTERWARE; GRID CONTROL; VIRTUAL HOST

Back to top

Rate this document
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=577443.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=577443.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=330072.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=330072.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=405642.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=405642.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=405979.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=405979.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=464191.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=464191.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=549270.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=549270.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=577443.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=577443.1http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_EnterpriseManagerBestPractices.pdfhttp://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_EnterpriseManagerBestPractices.pdfhttp://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_EnterpriseManagerBestPractices.pdfhttp://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_EnterpriseManagerBestPractices.pdfhttp://download.oracle.com/docs/html/B25003_01/toc.htm#BABCHGJDhttp://download.oracle.com/docs/html/B25003_01/toc.htm#BABCHGJDhttp://download.oracle.com/docs/html/B25003_01/toc.htm#BABCHGJDhttp://download.oracle.com/docs/cd/B16240_01/doc/em.102/e10954/actpass_env.htm#CHDHAHCBhttp://download.oracle.com/docs/cd/B16240_01/doc/em.102/e10954/actpass_env.htm#CHDHAHCBhttp://download.oracle.com/docs/cd/B16240_01/doc/em.102/e10954/actpass_env.htm#CHDHAHCBhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#tophttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#tophttp://displayfeedbackbox%28%29/http://displayfeedbackbox%28%29/https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1http://displayfeedbackbox%28%29/https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1http://displayfeedbackbox%28%29/https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1http://displayfeedbackbox%28%29/https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=406014.1#tophttp://download.oracle.com/docs/cd/B16240_01/doc/em.102/e10954/actpass_env.htm#CHDHAHCBhttp://download.oracle.com/docs/html/B25003_01/toc.htm#BABCHGJDhttp://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_EnterpriseManagerBestPractices.pdfhttp://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_EnterpriseManagerBestPractices.pdfhttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=577443.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=549270.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=464191.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=405979.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=405642.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=330072.1https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=577443.1

how to configure grid control agents to monitor virtual hostname in ha environments

Documents