Resynchronization

When the probe starts, it performs a full resynchronization with the Genband IEMS server to collect all current alarms. If the full resynchronization fails, the RedoResynch property allows you to specify whether the probe reattempts a full resynchronization. Additionally, the ResynchAttempt property allows you to specify the number of full resynchronization attempts that the probe makes.

Note: You can instruct the probe to not perform a full resynchronization on startup by setting the DisableResynch property to 1.

Following resynchronization, the probe processes each alarm as it is generated. The Genband IEMS server maintains a cache table of the most recent alarms. The number of alarms stored in the cache table is a configurable value on the Genband IEMS server. To ensure no alarms are lost during resynchronization specify the NlmConfigGlobalEntryLimit property for the Probe for Genband IEMS to the same value.

As alarms are generated, they are each allocated a sequence number. This enables the probe to recognize when an alarm has been missed. If an alarm is missed, the probe performs a resynchronization. If the number of alarms missed is less than or equal to the number of alarms stored in the cache table, the resynchronization is incremental. If the number of missed alarms exceeds the number of alarms stored in the cache table, a full resynchronization is performed.