Nokia NFM-P server redundancy
Two Nokia NFM-P servers can run in a redundancy pair (that is, one runs as the primary server and the other as a backup server). This affects the way that you configure the probe.
If the primary NFM-P server is down while the probe is connected, then the probe will attempt to connect to the secondary NFM-P server which will take over the primary server role. The probe cannot connect to the secondary NFM-P server if the primary server is still operational.
This feature works with the RetryCount property and the optionally with the RetryInterval property.
If RetryCount is 0 (retry is disabled), the redundancy feature is also disabled.
The RetryInterval property should be set to the appropriate amount of time needed for the NFM-P server to complete the server activity switch.
When the EnableFailover property is set to true the probe is trying to setup a connection with the new primary NFM-P server and you should see the following messages.
ProbeWatch message:
Connecting new primary Nokia NSP NFM-P server.
Debug message:
Setting up connection to primary/secondary host.
When the probe is successfully connected to the primary NFM-P server, you will see the following ProbeWatch message:
Connected to the primary Nokia NSP NFM-P server.
These are the probe properties impacted by the NFM-P server redundancy:
- Host (The primary host in redundancy).
- HTTPPort (This is the primary HTTP port in redundancy).
- EJBPort (EJBPort is the primary EJB port in redundancy).
- EnableFailover
- SecondaryHost
- SecondaryHTTPPort
- SecondaryEJBPort