Limitations of the Network Manager failover process

A number of limitations apply for the failover process.

The discovery process (ncp_disco) performs network discovery only in the primary domain.

The backup domain is not used for network discovery, so when the backup domain is active, do not attempt to configure a discovery. Also, when the backup domain is active, do not edit the discovered network topology to manually add or remove devices and connections.

The WebTools do not function when the backup server is in primary mode.

The Web applications do not connect to the backup server when it becomes primary during failover. Some Web applications, such as the SNMP MIB Browser and SNMP MIB Grapher, do not function when the backup server is in primary mode.

Restriction: Network Manager does not support the Dashboard Application Services Hub load balancing feature that the Tivoli Netcool/OMNIbus Web GUI does.
If you are running more than one Dashboard Application Services Hub server, they each run independently. If one of the Dashboard Application Services Hub servers fails, any remaining servers continue to run as individual entities. To minimize the effect of a server failing:
  • A user session on one Dashboard Application Services Hub server cannot be transferred, or continued, on another. If the first Dashboard Application Services Hub server fails, users must log in to another active Dashboard Application Services Hub server.
  • Ensure that each of the servers is configured with the same set of users, roles, groups, preference profiles, and resources such as pages, views, widgets, and reports.
  • Configure the servers to whatever the database high availability requires. For example, for Db2® you would configure the servers according the requirements of the Db2 HADR feature. Similarly, if you have a Oracle database, you would configure the servers according to the requirements of the Real Application Clusters (RAC) feature.
Note: Failover is not supported for the ITM monitoring agents in the Network Manager failover architecture.