Users Guide

ManualsBrandsDell ManualsComputer equipmentOpenManage Network Manager

Installing Distributed/HA Deployments | Installing Distributed and HA Deployments

OMNM 6.5.3 Installation Guide 59

Installing Distributed/HA Deployments

The following describes an installation to a cluster. In a production environment, such installations

must take account of the network security settings and firewalls.

Here are a few things to check before your installation:

• Synchronize clocks on all hosts where you install OMNM.

• Ensure any time (NTP) server processes are running.

• Ping all hosts from each other to ensure connectivity exists. Ping with fully-qualified domain

name and with the hostname alone.

• Ensure that the installing user has admin privileges on any Oracle database. See

Oracle

Database Management

on page 165 for more about setting up Oracle.

• Refer to the ports used in the

OpenManage Network Manager

User Guide

for a list of ports

that must be open on the firewall for components to communicate with each other. Open the

appropriate ports (bidirectionally).

NOTE:

It is often easiest to disable firewalls completely while initially installing and testing distributed

installations with firewalls between components.

• Add the following line to the application user’s Linux.profile file:

. /etc/.dsienv

This means the user sources the environment on login. On Windows, running the oware

command on clients creates a bash emulation with the same environment.

This section provides some general instructions to install OMNM in a distributed and HA

environment.

Install OMNM in a distributed and HA environment as follows.

Make the appropriate Custom installations to all affected hosts (Application servers,

Mediation servers, clients). You must know the following that you configure:

• Cluster name can be any string less than 40 characters

For example:

my_omnm_cluster

is the OMNM Application server cluster.

• Database information:

@[Server_name]:[port]:[database name]

For example:

@my_server:1521:MYDB

• Config server if you are clustering servers

For example:

my_server

You may want these to autostart in a production system. If so, select that option when

installing.

Install to Oracle as the installing user.

a. Configure the $ORACLE_HOME/network/admin/tnsnames.ora file on your Application

server. This is required for loaddb to work. Here is an example configuration:

MYDB =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = [Server_name])(PORT = 1521))

)

(CONNECT_DATA =