> 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/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-trouble-bringing-online-first-time.md).

# Troubleshoot initial controller connection

Troubleshoot a Controller 6000 that cannot establish its first Command Centre connection.

## General controller points

When bringing a controller online to Command Centre:

> ⚠️ If the Server has more than one network interface, ensure that the **Use different IP for Server** field has the IP address for the network interface that is connecting to the controllers.

See [Use Cases for Using Different IP Addresses for Server](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-use-cases-different-ip-for-server.md) and [Command Centre Server has Multiple Network Adaptors](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-command-centre-server.md).

***

## 6000 Linux-specific points

If you are having trouble bringing on a new (to the site) Controller 6000, or upgrading an older 8.10 and earlier 6000 to Linux (firmware **8.20 and above**) on a site, note the following:

1. When the controller first comes online, ensure the software selected is left as **None Selected** until the controller has connected.
2. The controller will restart a number of times. **Don't change the software settings while it's upgrading.**
3. The upgrade process involves Command Centre upgrading the controller to **v8.10 WinCE first**, then upgrading to the **Linux version**.

> ⚠️ **DIP Switch 2:** During the upgrade process, DIP Switch 2 should **remain ON** if using the BootP addressing option.

4. If the site has to assign IP addresses using the **DIP Switch 1, 2, 3 procedure**, once the controller has its IP address set, turn **OFF all DIP Switches**.
5. **Upgrading via USB** is an alternative upgrade option. See the release notes for your version of Command Centre for the correct procedure.

For the full WinCE-to-Linux upgrade procedure (DHCP, Default IP, and BootP variants), see [Upgrading WinCE to Linux](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-upgrading-wince-to-linux.md).

***

🔗 **Related**

* [Bringing online and networking](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-bringing-online-and-ne.md). The wider bringing-online workflow.
* [Controller Drops Offline Immediately After Coming Online](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-controller-drops-offli.md). If the controller connects then drops.
* [Upgrading WinCE to Linux](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-upgrading-wince-to-linux.md). The full migration procedure.


---

# 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/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-trouble-bringing-online-first-time.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.