> 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/licensable-features/perimeter-fence-controllers/monitoring-fence-zone-status.md).

# Monitoring Fence Zone Status

### Introduction

This procedure describes how to monitor the status of a Fence Zone from Command Centre.

### Before you begin

Before you begin this procedure:

* Ensure that the Fence Zone has been assigned to a Fence Controller, and the Fence Controller is assigned to a Gallagher Controller 6000 or 7000.
* You need to be in the same or parent Division of the Division holding the Fence Zone, and have the "View Site" operator privilege to perform this procedure.

### 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 Fence Zone you want to monitor.
3. **Right click** and select **Properties**.
4. Click the **Status and Overrides** tab.

   The status will be updated as soon as it is available.

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

   If the Voltage reading changes, this could be due to some grass touching the fence, (e.g. grass).

   If the Fence Controller that this Fence Zone is assigned to is offline the message *"Controller offline"* will display.


---

# 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/licensable-features/perimeter-fence-controllers/monitoring-fence-zone-status.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.
