It is possible to get Davicom remote monitoring units (DV-216, DV-208, DV-Mini and DV-Micro) to send alarms to more than one DavNet. This may be for main/back-up, disaster recovery or simply that you want DavNet in two locations.
In DavNet >Tools>Site setup (or simply click on the wrench and then to the site location on the map if you have one). Set up each site in both DavNets as normal, entering the site name, site ID, site IP address, username, password, etc. as shown in the example below. Make sure that all of the equipment is on the same network.
More information on sending alarms is in the user manuals, but it may be necessary to forward port 23 at both ends, if routers are involved.
Then set up both DavNets in each Davicom at each site as follows (Unit>Unit Configuration>Alarm Call Lists.)
Test that alarms can be sent from each site to each DavNet by trying them individually. You can do this by temporarily disabling each DavNet in turn, creating an alarm and making sure it gets through to the DavNet.
Once it is established that each Davicom can send alarms to both DavNets we need to disable the ASA (alarm-call sequence acknowledged) on the first DavNet.
When DavNet receives an alarm it normally acknowledges that alarm so that the Davicom stops sending any more alarms. The reason behind this is that the Davicom has delivered its alarm to the NOC (Network Operations Centre) and so has done its job.
However, when we have 2 NOCs the first NOC must not acknowledge the alarm so the Davicom goes on to send an alarm to the 2nd NOC.
On the first DavNet go into Setup > ASA configuration and check each checkbox as follows.
This ensures that this DavNet never acknowledges a call. The second DavNet should have all of the checkbox unticked.
Now in each Davicom go into Unit>Unit Configuration>Alarm and Communication Parameters and set the following parameters.
This now means that once an alarm happens, the Davicom waits 10 seconds, sends an alarm to the first DavNet, doesn’t receive an ASA, so it sends the same alarm to the 2nd DavNet 30 seconds later. If it fails to get through it will wait 1 minute and try again for a maximum of 5 times. This could mean that it sends the same alarm to the first DavNet more than once (if it fails to get through to the 2nd DavNet) but this is better than not sending at all. The alarms will all have the same time stamp on them.
The “Transmit Alarm to DavNet Even if Previously Acknowledged” checkbox ensures that alarms are sent through to both DavNets even if acknowledged locally, thus ensuring that they both have a complete list of alarms.
Setting Up Test Alarm Buttons
It is always useful to put Major and Minor test alarm buttons in your Davicom so that alarms can easily be generated. To set up a Major Test button set up the following relay.
And the following VLG (virtual logic gate)
Do the same using for 1R02 and 1V02 but make it a Minor Alarm. If you are short of physical relays it is possible to substitute Virtual relays (1O01, etc.) for physical relays.
Now by forcing on or pulsing each relay an alarm will be generated and sent.
DavNet Icons
Since DavNet V5.56 the icons display the current status of each site, not the historical alarms. Icon colours are as follows:
The site is normal. This is the normal state and if a site looks like this it is OK. There are no active alarms.
The site has a minor alarm which is acknowledged within DavNet. Connect to the site to see active alarms.
The site has a major alarm which is acknowledged within DavNet. Connect to the site to see active alarms.
When DavNet starts it polls all sites. Black indicates that the site has not yet been polled.
The site is normal but there are unacknowledged alarms. Click on the site to see active alarms.
The site has a minor alarm which is unacknowledged. Click on the site to see active alarms.
The site has a major alarm which is unacknowledged. Click on the site to see active alarms.
The colours indicate the status of the site when last connected, not the most recent alarm.
System and Custom Logs
System and custom logs can only be downloaded to one of the DavNets. Decide which one and enter that IP address into the System or Custom log window (Unit>Unit configuration>Status and log transfers) as follows.
More information on log transfer can be found in the Davicom manuals.
If transferring logs from more than one site, it is a good idea to stagger the times so they don’t all contact DavNet at the same time.
Task Scheduler Configuration
Each Davnet can contact each site on a regular basis to make sure that they are still on line and to check their status.
In DavNet>Setup>Task scheduler configuration set up each site as follows.
If the call succeeds an entry will be put in the log and a reading of every input and output taken. If the call fails 3 times a minor alarm will be raised.
If using IP we recommend calling once per hour. If an alarm happens in between the Davicom will contact DavNet to report it.
Licensing
Each instance of DavNet is licensed for a single computer and is priced for the number of sites it can communicate with.
If you wish to run 2 instances of DavNet you will have to buy 2 licences. For pricing options please contact your local representative.
