> 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/onelink-network-setup.md).

# OneLink network setup

* OneLink utilises Gallagher Cloud Services to enable Controller 7000s to connect to the on-premises Command Centre Server over the internet.
* OneLink prerequsites:
  * An active Sales & Maintenance Agreement/Care Plan.
  * v9.30+ software.
  * Only available on Controller 7000s.
* OneLink set up:
  * *Network Preparation:*
    * The controller requires a stable internet connection and access to DHCP and DNS services. If a firewall is in place, it must allow TCP outbound traffic from the controller to:
      * **Controller Registration Service:** <https://controller-onboarding.security.gallagher.cloud:443>
      * **Controller Gateway:** wss\://controller-gateway.security.gallagher.cloud:443
      * **Trusted Issuer Service:** <http://controller-onboarding.security.gallagher.cloud:80>
  * *Cloud Configuration:*
    * Ensure Command Centre has a connection to Gallagher Cloud.
  * *Controller Configuration (Registration):*
    * Enter controller details (MAC Address and Serial Number), click **OneLink** radio button and **Apply**.
  * *Controller Activation:*
    * Turn DIP Switches 2 and 7 ON.
    * Connect the Controller to the internet.
    * Power on the Controller.
    * The Controller will automatically come online (typically this can take up to 2 minutes).
    * Turn DIP Switches OFF.


---

# 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/onelink-network-setup.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.
