Users Guide

Understanding Installation Types | Preparing for Installation
24 OMNM 6.5.3 Installation Guide
Application Server Installation
To install only the Application server, select that option in the Choose Install Set screen that
appears in the installer. As in most installations, and as is essential for distributed installations, you
must select a partition name, whether the server starts automatically on host startup, the heap size,
database type and location (host and port).
Mediation Server Subnets
For other Mediation server-initiated OpenManage Network Manager functions like provisioning,
configuration, backup, restoration, compliance monitoring, and so on, you can optionally assign
Mediation servers to a management subnet on an installation screen.
When OpenManage Network Manager initiates communication to a Network Element in the
assigned subnet, the Application server attempts to use the Mediation server for that subnet.
Application servers update their list of active Mediation servers every 15 seconds. When
OpenManage Network Manager needs to communicate to a device that is on a subnet without an
assigned Mediation server, it uses the first Mediation server on the Active Mediation server list. If
for some reason a device does not respond to a Mediation server, the Application server try the next
Mediation server on the Active list. During installation Accept or alter the subnet mask for this
agent. By default the subnet mask is 255.255.255.0. This mask represents the portion of the
network serviced by this agent.
If you want to change this subnet later, the
installed.properties file (in
owareapps\installprops\lib\ ) has a oware.mediation.subnet.mask property that
you can re-make. You must then restart the Mediation server.
Mediation request routing supports explicit configuration of device scope managed per Mediation
server partition.
Routing Behavior
Each mediation request made by the application is routed to a server for execution. The routing is
based on the IP address of the device to be communicated with. The logic of this routing is as
follows:
—Is the target IP already in a Mediation server's device list?
yes - Is the same Mediation server still available?
yes - Use the same agent
—If no agent yet determined
For each available Mediation server...
For each
ip;mask pair (default and additional config),
calculate network address from IP and mask
calculate network address from device IP and mask
Do they match?
yes - add Mediation server to preferred agent list
Were any preferred agents found?
yes - use the least loaded agent from preferred list
add device IP to the agent's device list (use same server next time)
replicate agent device list within Application server cluster