Users Guide

Preparation for Clustering | Clustering
OMNM 6.5.3 Installation Guide 117
For high availability (HA) installations, systems typically use pairs of load balancers. OpenManage
Network Manager needs at least one load balancer pair to distribute loads among webservers. The
load balancer IP is what clients connect to. If webserver and appserver are on same machines, all
web servers can point to 127.0.0.1 to use their own local appserver. If webserver and appserver are
on different machines, they must have another load balancer pair to distribute loads among
appservers. All web servers then point to the appserver load balancer IP.
Load Balancer recommended hardware (or equivalent)
Configure your minimum hardware based on the expected number of connection per second:
• Less than 10000 connection/ sec 1 GB RAM, 2GB HD, Atom processor
• Up to 20000 connections/sec 4 GB ram, 10GB HD, Core DUO processor.
Deployments vary based on application usage, system availability and redundancy needs.
Deployment recommendations depend on system sizing factors discussed in the Sizing section.
Refer to
Single-Server Hardware Requirements on page 30 for hardware recommendations.
Preparation for Clustering
The following prepares for clustering.
• See
Distributed/HA Hardware Requirements on page 58 for hardware recommendations.
• Cluster licenses.
• As in any distributed system, you must ensure all servers’ system time is synchronized.
Application server cluster and mediation server cluster have significant problems operating
until time is in sync with NTP.
An example of such problems: the job status messages does not appear when backing up
devices. The start time is later than the finish time.
NTP is unnecessary with a standalone server. Otherwise, you must use it when you distribute
computing in clusters or when you just distribute Meditation.
Here is a sample ntp client configuration file:
# @(#)ntp.client 1.2 96/11/06 SMI
#
# /etc/inet/ntp.client
#
# An example file that could be copied over to /etc/inet/ntp.conf; it
# provides a configuration for a host that passively waits for a server
# to provide NTP packets on the ntp multicast net.
#
#multicastclient 224.0.1.1
driftfile /var/ntp/driftfile
server apollo