Resynchronization
If the probe loses the connection to a SpectroSERVER, there are three methods for resynchronizing cleared alarms in the SpectroSERVER with the ObjectServer. Resynchronization can be performed using the command line interface (CLI), the SpectroSERVER resynchronization interval, and during the SpectroSERVER failover process.
Resynchronization
to the ObjectServer is performed
using an SQL statement specified by the ResyncSQLCmd
property
in the host configuration file. You can configure the Value
attribute
of the ResyncSQLCmd
property using the tokens listed
in the following table.
Token |
Description |
---|---|
|
The list of active alarm identifiers collected during resynchronization. |
|
The same value as the generic Netcool/OMNIbus Manager property. |
|
The same value as the MinSpectrumSeverity property. |
|
The same value as the MaxSpectrumSeverity property. |
|
The same value as the generic Netcool/OMNIbus Name property. |
|
The same value as the OSHost property. |
|
The same value as the OSPort property. |
|
The time at which the probe receives the requested active alarm list. |
|
The same value as the generic Netcool/OMNIbus Server property. |
|
The same value as the generic Netcool/OMNIbus ServerBackup property. |
|
The name of the SpectroSERVER host as specified
by the |
|
The domain of the SpectroSERVER host as specified
by the |
|
The IP address of the SpectroSERVER host as
specified by the |
Resynchronization using the CLI
You can perform a manual resynchronization using the resync
spectrumName
command, where spectrumName is the name
of the SpectroSERVER host as specified by the Name
attribute of the
SpectroServer
property in the host configuration file. For more information about
using the CLI, see Command line interface.
Using a resynchronization interval
You can
use the ResyncInterval
property in the host configuration
file to set an automatic resynchronization at specified intervals.
The default is 86400 seconds (24 hours). You can specify different
resynchronization intervals for each monitored SpectroSERVER.
Using a SpectroSERVER failover configuration
If you are running two SpectroSERVERs in a failover configuration, you can use the ResyncOnFailover property to trigger a resynchronization operation when the probe fails over to the secondary SpectroSERVER. There is a possibility that the secondary SpectroSERVER might not contain all available alarms while the primary SpectroSERVER is down. To avoid data loss, you can use the ResyncPrimaryOnly property to specify that the probe resynchronizes with the primary SpectroSERVER only.
You can use the ResyncThreadMax property to specify the maximum number of threads that the probe spawns to perform the resynchronization operation. Specify a value of 0 to allow the probe to use an unlimited number of threads. The default is 5.