Redundant network configurations

Overview

The NFM-P supports database and main server redundancy, which provides network visibility in the event of a failure on one or more components. If a primary component fails, the standby component automatically takes control. You can also perform a manual switch to test redundancy or to prepare for a network upgrade.

The NFM-P supports collocated and distributed redundant deployment. In a collocated system, an NFM-P main server and database are on the same station. In a distributed deployment, the NFM-P server and the database are on separate stations. The servers and databases are separate entities, regardless of the physical or geographical deployment.

You require the following information to configure redundant OSS connections:

• the IP addresses of the primary and standby main servers

• which main server is currently primary

You can use any of the following methods to monitor the connection status between an OSS client and a main server:

• JMS exceptions, to monitor client connections to the JMS server

• monitoring near-real-time events using a JMS client connection

• XML API ping to monitor the HTTP connection to the NFM-P web server

See OSS client interfaces for more information about monitoring the connection status between the OSS client and a main server.

See Chapter 4, Event monitoring using JMS for more information about JMS and redundancy.