> 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/configuration-client/site-installation/hardware/creating-controllers/operation-mode-setup.md).

# Operation Mode setup

### Disabled Mode

* Only the Primary Ethernet interface is active.
* The Secondary interface is not used.

### Mode 1 - Active Backup

* Combines both interfaces into a single logical link, with only one interface active at a time.
* The Primary interface is used by default.
* The Secondary interface remains on standby and takes over automatically if the Primary fails.
* The same Primary MAC and IP address are used across both interfaces (Secondary MAC remains unused).
* Provides link-level redundancy only - it does not fail over due to upstream routing issues.

### Mode 4 - 802.3ad Link Aggregation Control Protocol

* Uses Link Aggregation Control Protocol (LACP) to combine both interfaces into a single logical connection.
* Interfaces work together to increase bandwidth and provide redundancy.
* Requires LACP support from the connected network switch.
* The switch determines the failover detection capabilities, which may vary depending on its configuration and features.

### Independent Dual Ethernet

* Both Primary and Secondary interfaces are active at the same time.
* Each interface can connect to a different network.
* IPv6 configuration must be consistently enabled or disabled across both Primary and Secondary interface.
* Dual Ethernet controllers can initiate outbound and inbound communication via the Secondary interface to servers and other controllers.
* When configured for DHCP, the Secondary interface will accept leases without Gallagher-specific vendor data, which cannot be filtered like on the Primary.
* Any DNS server IPs provided via the Secondary DHCP lease must match those in the Primary lease.

### Ethernet Bridge

* The controller operates as a transparent Ethernet bridge.
* The Secondary Ethernet interface can be used to connect a Controller or external device (e.g., camera, laptop).
* All network traffic destined for the bridged network passes through the controller without modification, regardless of traffic type or content.

  **Ethernet Bridge Operating Limitations**

  * A 'Secondary Ethernet Link Failed' alarm is raised when no active device is detected on the secondary port of a controller operating in Ethernet Bridge mode.
  * Bridged controller does not display information about any devices connected to its secondary port.
  * Devices connected downstream of a bridging controller will go offline if the bridging controller:
    * Restarts due to software upgrades
    * Restarts because of reset overrides or software faults
    * Loses power
    * Experiences upstream network connectivity issues
  * Ethernet Bridge mode must not be used as a network redundancy or failover strategy.
  * We recommend connecting no more than two downstream devices in each daisy chained Ethernet bridge configuration. Exceeding this limit may result in reduced performance and an increased likelihood of nuisance alarms within the system.


---

# 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/configuration-client/site-installation/hardware/creating-controllers/operation-mode-setup.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.
