Setting Up Multiple Always-On Monitoring Instances

You can set up multiple Always-On Monitoring (AOM) instances to ensure Always-On Monitoring is available in the event of outages.

  1. Uninstall any 13.1 Always-On Monitoring instances, if any.

    Except for the last running AOM instance (in this example, there are three AOM instances AOM1, AOM2 and AOM3) you must perform the following for AOM1 and AOM2):

    • Shut down the instances (AOM1 and AOM2) by running $AOM_HOME/scripts/emsctl stop

    • Remove all the files and sub-directories under $AOM_HOME

    And on the last AOM instance (AOM3):

    • Shut down the instance (AOM3) by running $AOM_HOME/scripts/emsctl stop

    • Uninstall AOM by running $AOM_HOME/scripts/emsca uninstall

    • Remove all files and sub-directories under $AOM_HOME

    • To remove any trace of the previous AOM installation, you can drop the AOM repository user in the repository by executing drop user ems cascade.

  2. Obtain the latest Always-On Monitoring release. The ZIP file can be found on the OMS' /sysman/ems directory. Copy the ems_13.5.x.x.x.zip file to a location where you want AOM to be installed and unzip the file.
    unzip ems.zip

    Note:

    For AOM 13.5 to run, both the Management Agent and Enterprise Manager installation MUST be upgraded to 13.5 as well.

  3. Install AOM.

    For setting up the very first AOM instance, the user must run $AOM_HOME/scripts/emsca

    For installing subsequent AOM instances the user must run $AOM_HOME/scripts/emsca add_ems

  4. Finally, you must run the following steps on all instances before starting AOM.

    • To generate the certificate and the wallet for the SLB host, run $AOM_HOME/scripts/emsctl secure

    • Configure the downtime contacts. For more information, see Configuring Downtime Contacts in Enterprise Manager.

    • To sync the AOM repository schema with the Enterprise Manager repository schema, execute $AOM_HOME/scripts/emsctl sync

    • Set the upload URL, by running emctl config emkey -copy_to_repos on the Enterprise Manager host.

    • Start the AOM instances by running, $AOM_HOME/scripts/emsctl start