Resynchronization
On startup, you can instruct the probe to connect to an HTTP port of the Nokia NFM-P server, and send a SOAP/XML request to resynchronize all active alarms.
Using the InitialResync property,
the probe can resynchronize alarms generated while the network elements
managed by the NFM-P server are either inService
(active)
or inMaintenance
(in the maintenance stage or inactive).
The Nokia NFM-P server generates inService
alarms
when the associated network elements are active, and generates inMaintenance
alarms
when they are inactive.
To resynchronize only the active network
elements and to receive only the inService
alarms,
set the XMLretrieveUseInService property to 1.
If you have specified a value for the RecoveryFile property, you must create the file manually. The server only sends alarms that have been generated since the timestamp indicated in the recovery file.
If you set the ResynchInterval property to a value greater than 1, the probe periodically resynchronizes with the Nokia NFM-P server. If you set the ResyncInterval property to a low value, you may experience performance issues if the probe has to resynchronize large amounts of active alarms each interval.
If you set the Optimize property to 1, the probe optimizes performance by not writing the resynchronized events received from the HTTP request and the JMS events to the log file.