Example failover hosting without NCIM topology database high availability
This is an example of failover hosting where the failover configuration does not include a copy of the NCIM topology database on the backup installation.
In any failover configuration, both the primary and backup Network Manager domains connect to the same database, but in a failover set up without NCIM topology database high availability there is no database replication on a standby server.
The following figure shows an example of hosting ObjectServer and Network Manager failover using four host machines.
For performance reasons, the NCIM topology database requires a high bandwidth connection to the Dashboard Application Services Hub server. If host machine 3 has multiple CPUs and sufficient memory, you can install NCIM on host machine 3.
Install the core components
on both host machines 1 and 2, and install the Web applications on
host machine 3. Install the NCIM topology database on host machine
4.
Note: If you implement failover, then you must ensure that both the primary and backup installations are using identical encryption keys. If the encryption keys are not identical, then the backup poller does not function correctly during failover. To ensure that both the primary and backup installations are using identical encryption keys, copy the following file from the primary server to the same location on the backup server:
$NCHOME/etc/security/keys/conf.key. If you enter all SNMP community strings on the command line and do not encrypt them, you do not need to do this task. Also, to update the NCIM and ObjectServer passwords use the Perl script ncp_password_update.pl.