SilentKnight VisorAlarm Plus 2U - Manual (Page 58)

VISOR ALARM – Configuration
III - 56
Doc.DM374-I
Ver.1.0
previously mentioned, the polling-sync-time parameter determines how often these updates are
carried out.
The device provides some events which display the different phases of the synchronization protocol.
One example of synchronization is when an mIP/IPDACT registration is produced. In this case the
VisorALARM PLUS 2U dynamic configuration is modified.
The traces for the main VisorALARM PLUS 2U when the synchronization timer has completed are as
follows:
03/04/05 17:44:10 ARLY.032 MAIN sync: Update commited.
03/04/05 17:44:11 ARLY.032 MAIN sync: Start sync.
03/04/05 17:44:13 ARLY.032 MAIN sync: Rcv HELLO.
03/04/05 17:44:13 ARLY.032 MAIN sync: Snd LIST.
03/04/05 17:44:13 ARLY.032 MAIN sync: Snd CFG_BCK
03/04/05 17:44:13 ARLY.032 MAIN sync: Rcv req MIP_CFG accn: 1234.
03/04/05 17:44:13 ARLY.032 MAIN sync: Snd MIP_CONFIG MIP 1234.
03/04/05 17:44:13 ARLY.032 MAIN sync: Rcv END_2.
03/04/05 17:44:13 ARLY.032 MAIN sync: Snd FIN.
The first trace indicates that the main device needs the backup device to update due to an mIP/IPDACT
register being received. The following event indicates that the TCP connection has established between
both devices and therefore the updates are exchanged. The next phase of the protocol consists of both
parts exchanging a list of updates, each of these made up of an mIP/IPDACT account number and a time
mark which indicates if this is a final modification to take into account or not. Once each device has
detected which account has been changed, the configuration for this is requested from the other device.
If the modification implies deleting an account, the device directly deletes the affected mIP/IPDACT
from its configuration.
The traces corresponding to the backup device are as follows:
03/04/05 17:44:11 ARLY.033 BCK sync: Update required from MAIN.
03/04/05 17:44:11 ARLY.033 BCK sync: Open
03/04/05 17:44:11 ARLY.033 BCK sync: Snd HELLO.
03/04/05 17:44:14 ARLY.033 BCK sync: Rcv LIST.
03/04/05 17:44:14 ARLY.033 BCK sync: Snd END_1.
03/04/05 17:44:14 ARLY.033 BCK sync: Rcv CFG_BCK.
03/04/05 17:44:14 ARLY.033 BCK sync: Snd MIP_CFG MIP 1234
03/04/05 17:44:14 ARLY.033 BCK sync: Rcv MIP_CFG _RCV accn: 1234.
03/04/05 17:44:14 ARLY.033 BCK sync: Snd END_2.
03/04/05 17:44:14 ARLY.033 BCK sync: Saving changes.
03/04/05 17:44:14 ARLY.033 BCK sync: Rcv FIN
03/04/05 17:44:17 ARLY.033 BCK sync: Changes saved.
In the above case it is the main device which requests the updating. The backup device can also
initiate this.