> 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/configure/controller-6000-bringing-online-and-ne.md). # Bring a controller online and configure networking Bring a Controller 6000 online and configure its server connection, networking, and diagnostics. Getting a Controller 6000 onto the network and talking to the Command Centre server. This page pulls the workflow together. The dedicated topic pages are the canonical references for each step. ## IP address assignment For the full procedure (Methods 1 to 3: BootP, Default IP, ccftBootp.exe), see [Assigning a Controller an IP address](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-assigning-a-controller.md). > ⚠️ From Command Centre v8.50 onwards there is only an **outbound** TCP connection from the Controller to the Server. Controller to Port 1072 to Server. *** ## Trouble bringing a controller online 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. ### 6000 Linux-specific points * When the controller first comes online, ensure the software selected is left as **None Selected** until the controller has connected. * The controller will restart a number of times. **Don't change the software settings while it's upgrading.** * The upgrade process involves Command Centre upgrading the controller to **8.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. * 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**. * Upgrading via USB is an alternative upgrade option (see the release notes for your version of Command Centre for the correct procedure). For controller-drops-offline behaviour after first connection, see [Controller Drops Offline Immediately After Coming Online](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-controller-drops-offli.md). For server-side multi-NIC behaviour, see [Command Centre Server has Multiple Network Adaptors](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-command-centre-server.md). *** ## Testing controller network connections > The majority of testing is best done from the Controller network connection point using a laptop, back to the server. > ⚠️ From CC v8.50 onwards the controller is the device that makes the initial TCP connection to the server. The server does not send any TCP connection request to the controller. For the full testing toolset (Network Connectivity Tools, Ping, Listen Port, Telnet, TNC, ARP, netstat, Web Browsing, Node Number), see [Testing Controller Connections](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-testing-controller-connections.md). Key testing tools (summary): | Tool | Use | | ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | Network Connectivity Tools (firmware 9.30+) | Web-browse to controller at `{IP}/debug.`, use credentials provided by Tech Support. Tests outbound connectivity from the controller. | | `ping ` / `ping ` | Confirms basic network connection. Use `-4` switch to force IPv4. | | `telnet 1072` | Tests TCP Port 1072 (controller-server communication). Run in both directions. Indication of blocked port means check firewall, switch/router, anti-virus. | | `tnc -p ` (PowerShell) | Modern alternative to telnet. Confirms outbound port and server IP. | | `arp -a` | Physical Address starting with `00-90-1d` is a Gallagher controller. | | `netstat -an` / `-ano` | CC v8.40 and below: two established connections (inbound and outbound on 1072). CC v8.50 and above: one outbound connection. | > ⚠️ **PID mismatch on port 1072:** If the PID using port 1072 does not match the PID of 'FT Controller Service' in Task Manager, another application is locking port 1072. Two options: (1) get the third-party app to change port, (2) change Command Centre's listen port. Web Browsing (`{controller IP}/debug.`): | Condition | Logon | Password | | --------------------------- | ------------ | ------------------------------------------------------------------------------------- | | Controller in 2-flash state | `diagnostic` | `[REDACTED]` (default - contact Tech Support) | | Controller in 1-flash state | `diagnostic` | `[REDACTED]` (site-specific value based on Site Serial number - contact Tech Support) | | CC v8.40+ | `diagnostic` | May be a configured password, check with Tech Support | Key pages on the controller's debug web interface: * **TCPSender.** Confirm TCP IP settings. Check Server IP matches the actual Server IP. * **TCPExchange.** Confirm keys and certificates are OK and the correct Master certificate is selected. * **Errorlog.** Shows recurring errors or restarts. Check as a last resort. * **Node Number.** Must match the node number in Command Centre. To view the CC node number: open Controller Properties > Setup tab, then Ctrl + double-click in a clear area of the Setup tab. A popup window shows the node number. *** ## Firewall configuration For the full firewall configuration procedure, see [Firewall Issues](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-firewall-issues.md). *** ## DNS - Dynamic DNS For DNS failover behaviour and configuration, see [Dynamic DNS](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-dynamic-dns.md). *** 🔗 **Related** * [Assigning a Controller an IP address](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-assigning-a-controller.md). The IP assignment methods in full. * [Testing Controller Connections](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-testing-controller-connections.md). The full diagnostic toolset. * [Firewall Issues](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-firewall-issues.md). Opening the ports the controller needs. --- # 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/configure/controller-6000-bringing-online-and-ne.md?ask=&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.