Users Guide
Understanding Installation Types | Preparing for Installation
OMNM 6.5.3 Installation Guide 25
—If no agent yet determined
Is the local Application server configured to do mediation?
yes - use the local server (not “sticky”)
no - execution of mediation request will fail
Compatibility with Previous Versions
The impact of the above behavior on previous mediation versions occurs only where no preferred
Mediation server is available. Before such behavior was available, the application made an arbitrary
selection from any available Mediation servers, possibly using the same server every time. Now, only
the local Application server can handle the request. If you have configured the Application server to
perform mediation (true by default), then the system should continue to execute these requests as
it had in the past. If the Application server is not configured to perform mediation, then requests
may fail with
no mediation
errors instead of being routed to the wrong Mediation server
possibly resulting false
device not available
errors.
Configuration Options
By default, each Mediation server has a single network mask established during installation. Each
Mediation server in a cluster or HA Pair should yield the same network address when the default
mask is applied to the Mediation server’s IP address. Here is an example of a default mask setting
on a Mediation server:
oware.mediation.subnet.mask=255.255.255.0
In addition to the default mask, you can define additional routing configurations as Application
server properties. Each Application server in a cluster should have the same settings. You can add
more IP Addresses and/or masks to the default configuration made locally on the Mediation server
for each Mediation server partition. The property name is
com.dorado.mediation.routing
with a mediation partition name appended. Here is an example of routing requests for any device
IP address starting with 10.10 to a Mediation server named
foo-medPartition
:
com.dorado.mediation.routing.foo-medPartition=10.10.0.0;255.255.0.0
This appends
Partition
to the partition name. For example:
com.dorado.mediation.routing.rcellmedPartition=172.16.0.0;255.255.0.0
The syntax for routing configuration values is as follows:
ipAddress;mask[,ipAddress;mask]
Basically, you can add more IP and mask pairs as comma delimited values. If you omit the mask,
then the OpenManage Network Manager (OMNM) installer assumes it is 255.255.255.255. If you
omit the IP address, then the OMNM installer assumes the address is the Mediation server's IP
address. If an IP address or mask is not valid, a warning appears once in the Application server log
when the properties load. If one of several values for a single property is not valid, the OMNM
installer still applies the other setting.
The Application server itself performs mediation when no agents are available. This is required
unless your deployment includes at least one Mediation server. All Application servers in a cluster
must have the same configuration. To disable mediation services on an Application server after you
configured a distributed Mediation server elsewhere, add the following property on the Application
server (preferably in
installed.properties
):
oware.appserver.mediation.setup=false