> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/configuring-offline-monitoring.md).

# Configuring Offline Monitoring

### Introduction

This procedure describes how to configure Server to controller offline monitoring, and Inter-controller offline monitoring by assigning several Controllers to a monitoring (or ‘parent’) Controller. The monitoring Controller will detect when any of the monitored Controllers are not communicating, indicating possible hardware failure.

**Note:** The number of monitored Controllers that can be assigned to one monitoring Controller is limited to 60. This is to minimise network traffic which could impact on the performance of your Command Centre system.

The main scenarios that require Inter-controller offline monitoring are:

* **Contact ID**

  Where a Controller hosting an Alarm Dialler must detect when other Controllers that can generate alarms that are logged using the same Alarm Dialler, are unable to communicate with it.

  (See [External Alarm Monitoring](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring.md) for further detail.)
* **Interlocking Doors**

  Inter-controller monitoring can be used to maintain the integrity of Interlock groups in which doors that are interlocked with doors on other monitored Controllers that are out of communication should not be permitted to open.

  (See [Interlocking Doors](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/interlocking-doors.md) for further detail.)

### Before you begin

Before you begin this procedure:

* Ensure that the Controllers you want to configure inter-controller monitoring for have already been created in Command Centre (see [Creating Controllers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers.md) for the procedure).
* You need to have the “Edit Site” operator privilege for the monitoring Controller and the “View Site” operator privilege for the monitored Controllers.

### Procedure

1. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. Highlight the required ‘parent’ Controller, (i.e. the one that you want to configure offline monitoring for).
3. **Right click** and select **Properties**.

   By default the **General** tab displays.
4. Click the **Offline Monitoring** tab.

   **Note:** All fields on this screen will be read-only if you do not have appropriate privileges to edit Controllers.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e977b2c4247e05967d4fea33674bcb0cf4ff393d%2Fftc_offlinemonitoringtab.png?alt=media)
5. Do you want to configure Server to controller offline monitoring?

   If **yes**, go to Step 6.

   If **no**, go to Step 7.
6. Click the appropriate radio button for the **Server to controller offline time**.

   <table><thead><tr><th width="210">Radio button</th><th>Description</th></tr></thead><tbody><tr><td>Use the Command Centre default</td><td>This option is set to 90 seconds and cannot be changed.</td></tr><tr><td>Use an offline time of</td><td><p>This option allows you to set the offline time.<br>Default = 90 seconds. Valid range = 20 - 360 seconds (6 minutes)<br><br><strong>Notes:</strong></p><ul><li>The controller heartbeat interval is inherently set at approximately one third of this time. If three heartbeats fail to detect the controller is online then a Controller Offline alarm will be raised.</li><li>If Controller offline time is set to less than 20 seconds the following warning message will display:<br><em>"Setting the server to controller offline time too low may compromise performance and risk false offline alarms."</em></li></ul></td></tr></tbody></table>
7. Do you want to configure Inter-controller offline monitoring?

   If **yes**, go to Step 8.

   If **no**, go to Step 10.
8. Enter the appropriate Inter-controller offline timeout value in the **Report offline within** field.

   **Note:** The minimum value for this field is 60 seconds and the maximum is 3600 seconds (1 hour). If an out of range value is entered an error message displays. (Default = 100 seconds)
9. From the **Hardware** List Window, select the Controller(s) that you want to be monitored by this Controller.

   Drag and drop them into the **Monitored Controllers** grid.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d85cf8f7791b6d873329000a97741c0bf3fa1963%2Fftc_offlinemonitoring_ftctoftc.png?alt=media)

   **Note:**

   The monitoring Controller cannot be assigned to itself, (i.e. if you attempt to drag it into the Monitored Controllers grid an error message will display and the assignment will be ignored).
10. Click **OK** to exit and save your changes.

    Click **Cancel** to exit without saving your changes.

    Click **Apply** to save your changes and stay in this window.

### Result

A Controller has been configured to monitor other Controller(s) for offline, and the monitored Controller(s) have been configured to send regular heartbeats to the monitoring Controller.

If the monitoring Controller fails to receive a heartbeat from one of the monitored Controllers within the configured timeout period, it creates a “Monitored Controller Offline” alarm in the Alarm Viewer.

**Note:**

It is likely there will be several “Monitored Controller Offline” alarms within a few minutes after applying the initial configuration, or applying any subsequent configuration changes.

### Hint

{% hint style="info" %}
We do not recommend that a group of Controllers be configured to all monitor one another, due to large increases in network traffic. However, if a site does configure Controllers to all monitor each other, the maximum number of Controllers configured this way should probably not exceed 12, but this is dependent on the network quality.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/configuring-offline-monitoring.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
