> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/smb/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/smb/installing-gallagher-smb/controller-configuration.md).

# Controller Configuration

### Configuring Controller settings in a web browser

The Controller’s cloud configuration web pages allow configuration of specific Controller settings, including the Controller’s date/time and NTP server if needed.

To connect to the Controller’s cloud configuration web pages, there are two methods:

<table><thead><tr><th width="174">Method</th><th>Procedure</th></tr></thead><tbody><tr><td><strong>Navigate to the Controller's IP address</strong></td><td><ol><li>Find the IP address that has been assigned to the Controller by the local DHCP server.</li><li>Set DIP switch 1 to ON.</li><li>Connect a laptop/PC to the same network as the Controller.</li><li><p>Using a web browser, go to the Controller’s cloud configuration web page, replacing <em>&#x3C;ip_address></em> with the assigned IP address for the Controller:</p><p><em>http://&#x3C;ip_address>/cloud/</em></p><p>The Sign In dialog displays.</p></li><li><p>Enter <strong>cloud</strong> for the username, then <strong>GGLcloud</strong> for the password and press <strong>Enter</strong>.</p><p>The Gallagher Cloud Controller Configuration web page displays.</p></li><li>Select the required link to configure the Controller as needed. </li><li>When finished, set DIP switch 1 to OFF.</li></ol></td></tr><tr><td><strong>Reset the Controller's IP address, then navigate to it</strong> </td><td><p>If you cannot find the Controller's DHCP IP address, the Controller can use the default IP address by powering it on with DIP switches 1, 2, and 3 ON. The Controller then uses the following default addresses:</p><ul><li><strong>Controller IP:</strong>  192.168.1.199</li><li><strong>Gateway:</strong>         192.168.1.198</li><li><strong>Subnet:</strong>            255.255.255.0</li></ul><ol><li>Connect the Controller to your PC via the Controller's Ethernet port.</li><li>Set DIP switches 1, 2 and 3 to ON.</li><li>Power cycle the Controller.</li><li><p>Using a web browser from a PC on the same subnet as the Controller, enter the default IP address of the Controller as follows:</p><p><em>http://192.168.1.199/cloud/</em></p><p>The Sign In dialog displays.</p></li><li><p>Enter <strong>cloud</strong> for the username, then <strong>GGLcloud</strong> for the password and press <strong>Enter</strong>.</p><p>The Gallagher Cloud Controller Configuration web page displays.</p></li><li>Select the required link to configure the Controller as needed.</li><li>When finished, set DIP switches 1, 2 and 3 to OFF.</li></ol></td></tr></tbody></table>


---

# 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/smb/installing-gallagher-smb/controller-configuration.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.
