Administering the eG Manager to Monitor an Oracle Cluster

  1. Log into the eG administrative interface.
  2. eG Enterprise cannot automatically discover the Oracle Cluster component. You need to manually add the server using the COMPONENTS page (see Figure 1) that appears when the Infrastructure -> Components -> Add/Modify menu sequence is followed. Remember that components manually added are managed automatically.

    Figure 1 : Adding the Oracle Cluster

  3. To manage the cluster, specify the VIP or the SCAN IP address of any node in that cluster against Host IP in Figure 1. VIP or virtual IP address is the IP that the Oracle Clusterware assigns to each node in the cluster, upon cluster startup. SCAN provides a single domain name via DNS, allowing end-users to address a RAC cluster as-if it were a single IP address.
  4. Then, provide a Nick name for the cluster.
  5. eG Enterprise recommends that the Oracle cluster be monitored in an 'agentless' manner. Therefore, select the Agentless check box in Figure 1 to enable agentless monitoring of the cluster.
  6. Next, pick the OS on which the cluster node is running. Then, from the Mode drop-down, select the agentless monitoring mechanism you want the remote agent to use. If the OS you have chosen is Windows, then pick Perfmon as the Mode. If the OS you have chosen is a flavor of Unix or Solaris, then pick Rexec as the Mode.
  7. Then, select the Remote agent and External agent that will be monitoring the cluster.
  8. Finally, click the Add button to register the changes.
  9. When you attempt to sign out, a list of unconfigured tests appears (see Figure 2).

    Figure 2 : List of tests to be configured for the Oracle Cluster

  10. Click on the Oracle Active Sessions test to configure it. To know how to configure the test, refer toMonitoring the Oracle Cluster chapter.
  11. Once all the tests are configured, signout of the eG administrative interface.