> 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/command-centre-releases/release-history/unsupported-gallagher-command-centre-versions/command-centre-9.00-releases/9.00-maintenance-release-8.md).

# 9.00 Maintenance Release 8

Enhancements in this version are as follows

<table><thead><tr><th width="112">Tech Ref</th><th width="520">Description</th><th width="470">Component</th></tr></thead><tbody><tr><td>156483</td><td>C6000 Linux Kernel Upgrade</td><td>Controller</td></tr></tbody></table>

Bug fixes in this version are as follows

<table data-header-hidden><thead><tr><th width="95"></th><th width="540"></th><th></th></tr></thead><tbody><tr><td>Tech Ref</td><td>Description</td><td>Fixed In</td></tr><tr><td>142667</td><td>C7000 SD POE - PoE Failure due to LLDP Negotiation issue causing  persistent negotiation failures and log flooding</td><td>Controller</td></tr><tr><td>142983</td><td>T Series readers misreporting wallet incompatible</td><td>Server/<br>Controller</td></tr><tr><td>157443</td><td> Performance degradation addressed</td><td>Server</td></tr><tr><td>157736</td><td>Attempting to apply the site facility code to the biometric card type triggers a "conflict occurred in database" error"</td><td>Server</td></tr><tr><td>157737</td><td>Report stuck in loading when card type filter is used</td><td>Server</td></tr><tr><td>157776</td><td>Performance Degradation from action plans set to “Not an Event,” establishing a new database connection</td><td>Server</td></tr><tr><td>158369</td><td>Z10 Tenson sensor - improper locking logic during configuration updates, causing the system to hang</td><td>Server</td></tr><tr><td>158492</td><td>"lldp Negotiation in progress" never goes away</td><td>Controler</td></tr><tr><td>158772</td><td>CC Service Restart Loop Triggered by Encrypted REST Client Keys in Restored Template – Fixed in Template Utilities</td><td>Server</td></tr><tr><td>159373</td><td>Cardholder Viewer not showing all PDF fields when creating a new cardholder in a 3 Server multiserver environment</td><td>Client/<br>Multiserver</td></tr><tr><td>159947</td><td>C6000 and C7000: Kernel version and SDK versions not displaying correctly</td><td>Controller</td></tr><tr><td>160749</td><td>Issues upgrading controller software when Alcolizer customisation is installed</td><td>Controller</td></tr><tr><td>161187</td><td>Setting a PDF as required, isn't refreshing the cache for cardholders which have a null value</td><td>Server</td></tr><tr><td>163049</td><td>Operator Privilege Enforcement Update to address issues found in the previous MR</td><td>Server</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/knowledge-hub/command-centre-releases/release-history/unsupported-gallagher-command-centre-versions/command-centre-9.00-releases/9.00-maintenance-release-8.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.