SilentKnight VisorAlarm ARLY Interface - Manual (Page 17)

VISOR ALARM – ARLY Configuration
II - 12
Doc.DM359-I
Rev.2.0
option MAIN, for the main receiver, SECONDARY for the backup and
MAINTENANCE for the maintenance receiver.
Example:
ARLY-1 Cfg> BACKUP-ALARM-RECEIVER TYPE MAIN
ARLY-1 Cfg>
b) BACKUP-ALARM-RECEIVER ADDRESS-MAIN
Configures the main VisorALARM address. This parameter is only logical for the backup
VisorALARM, as it needs to know the IP address of the main in order to execute two functions:
• Poll to 1 main VisorALARM with the aim of detecting if it’s down.
• Establish the connection with the main VisorALARM to synchronize configurations.
Syntax:
ARLY-1 Cfg>BACKUP-ALARM-RECEIVER ADDRESS-MAIN value
value Main VisorALARM IP address.
Example:
ARLY-1 Cfg>BACKUP-ALARM-RECEIVER ADDRESS-MAIN 80.26.96.183
ARLY-1 Cfg>
c) BACKUP-ALARM-RECEIVER MAINTENANCE-PASSWORD
This parameter only is necessary when the receiver is configured as maintenance. This parameter
configures the keyword that must be used by the receiver to decipher the sent messages from the mIP
devices.
d) BACKUP-ALARM-RECEIVER SYNC-PORT
This parameter is necessary both in the main VisorALARM and in the backup. This value is the port
which listens in the main and where TCP connections are accepted from the backup VisorALARM
through which the configurations synchronization protocol is established. To simplify this port, it can
be the same as that used for mIP/IPDACT supervision tasks. In this way, you only need to make a
single port transparent in the input router.
Syntax:
ARLY-1 Cfg>BACKUP-ALARM-RECEIVER SYNC-PORT value
value Configurations synchronization port. Admits values between 1 and
65535.
Example:
ARLY-1 Cfg>BACKUP-ALARM-RECEIVER SYNC-PORT 35536
ARLY-1 Cfg>
e) BACKUP-ALARM-RECEIVER POLL-TIME
This parameter is the time between polls carried out by the backup VisorALARM over the main. The
task of these polls is to detect when the main VisorALARM is down. If the backup device checks
that its output to Internet is correct (its Ethernet physical interface is operative and the polls carried out
over an external server are correct) but the poll fails, you need to assume that rest of the installed