> 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-unable-to-bring-6000-hs-online.md).

# Unable to Bring a 6000 HS Online

Resolve High Sec Controller 6000 connection failures and configuration issues.

> ⚠️ **Scope:** This only relates to a **WinCE version of the 6000 Enhanced (C300101)** released **prior to July 2022** (Enhanced controllers with serial number **2225xxxxxx and below**).

> ⚠️ **Naming note:** The "High Spec (HS)" has been renamed to the **Enhanced Controller (C300101)**. Do not confuse it with the **PIV Controller**, which has been renamed to the **High Sec controller (C305101)**. See [High Sec Specific Information](/knowledge-hub/products/cc-hardware/controllers/controller-6000/reference/controller-6000-high-sec-specific-info.md).

***

## Symptom

If you have been upgrading a 6000 Enhanced controller (C300101) and had issues with bringing it online or upgraded, and have performed a **DIP Switch 8 procedure** on the controller, you may be running into a known issue.

If the controller has been **upgraded directly from v7.50 or earlier** to **v8.10**, and then had a DIP Switch 8 procedure performed, the controller becomes **unusable** and will have to be returned to Gallagher for servicing before it will be usable again.

***

## Diagnostic indicators

* The C6000 Enhanced will take an IP address.
* The controller shows an **inbound** connection on the TCP Sender page (web-browse, see [Testing Controller Connections](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-testing-controller-connections.md)).
* On TCP Exchange there is **no** outbound connection.

Command Centre log error:

```
CCNTBertServ[1dec:0694], GENERAL, [insert IP here] CM(logSSLError) -- [reason: 1051]
error:1409441B:SSL routines:ssl3_read_bytes:tlsv1 alert decrypt error(s3_pkt.c:1498)
SSL alert number 51
```

> ⚠️ **Unrecoverable in the field. Must be sent back to Gallagher for repair.**

***

## Prevention - recommended upgrade procedure

The Controller Enhanced (C300101) with **v7.50 and below** should be upgraded **first** to **any version within v7.60 to v8.00**.

This ensures the controllers will not brick once upgraded to v8.10 and the DIP Switch 8 procedure is performed.

For the broader upgrade, downgrade and defaulting matrix, see [Upgrading, Downgrading, Defaulting and Compatibility](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-upgrading-downgrading-defaulting-compatibility.md).

***

🔗 **Related**

* [High Sec Specific Information](/knowledge-hub/products/cc-hardware/controllers/controller-6000/reference/controller-6000-high-sec-specific-info.md). The full Enhanced and High Sec reference.
* [DIP Switch 8 Recovery](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-dip-switch-8-recovery.md). The recovery procedure and its brick warning.
* [Upgrading, Downgrading, Defaulting and Compatibility](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-upgrading-downgrading-defaulting-compatibility.md). The firmware matrix.


---

# 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-unable-to-bring-6000-hs-online.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.