SilentKnight Using Configuration Patterns to ease receiver administration - Manual (Page 2)

Since the receiver can hold an unlimited number of configuration patterns, dealer ABC
and dealer DEF can have a different pattern for their separate subscriber installations.
In this manner, an installing dealer with say configuration pattern 1500 could be moved
to another IP and port address on a different primary and backup receiver by simply
changing the configuration pattern and then clicking on the “update accounts” button in
VisorALARM Manager. This will perform a remote update of all their remote sites via
the receiver admin server. The user passwords can also be changed instantly via this
method. The remote subscriber units will instantly switch to the new IP addresses and
new UDP port as well as any password change at the new central station.
Changing the CMS location or IP Service Provider
Instead of relying on the IP Alarm Monitoring Service on an external DNS service,
IPDACTs make use of IP tracking mechanisms offered by the ARLY communication
protocol; so that they can be reprogrammed with the new CMS IP addresses (backup
and main) with very little effort from the CMS administrator and no manual
reprogramming in each Fire Panel location. Furthermore, during the CMS IP address
space modification, the Alarm Monitoring Service will not be disrupted.
During the initial Fire Panel installation and registration of the remote IPDACT with the
receiver, the VisorALARM downloads into the IPDACT the IP addresses of the Main
and Backup CMS. The VisorALARM picks the IP addresses from the appropriate
IPDACT programming pattern in its Data Base. On the other hand, the VisorALARM
keeps track of the IPDACT IP addresses and ports since it caches it during the last
polling interval. When the IP address space of the CMS is modified, the IPDACTs are
reprogrammed without disrupting the Alarm Monitoring Service, following these steps:
1. The new IP address space is activated into the Main CMS. All the IPDACTs in the
field switch to the Backup CMS, as the IPDACTs haven’t been informed yet on how to
reach the Main CMS in the new address.
2. The new IP address from the Main CMS is edited into the appropriate programming
pattern of the Backup VisorALARM Data Base. With a one-click operation into the
VisorALARM Manager Application6, the IPDACTs are batched reprogrammed.
3. Once the batch reprogramming is completed, all the IPDACTs in the field will then
reconnect to the Main CMS at the new address.