> 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/integrations/elevators/otis/configure-otis-compass-networking.md).

# Configure Otis Compass networking

Configure NIC addressing and routes for an Otis Compass HLI connection.

The Otis Compass HLI service requires a dedicated network interface.

### Configure the standard network

Install `FT Otis Compass HLI Service` on a server with a NIC configured as follows:

```
IP address:  192.168.50.250
Subnet mask: 255.255.255.0
```

{% hint style="warning" %}
These settings are hardcoded by Otis. Install this NIC on the Command Centre server.
{% endhint %}

Connect NIC 2 directly to the Otis Layer 3 switch. Do not use intermediary switches.

Intermediary switches can block multicast traffic. Elevator controllers may then remain offline.

### Configure an alternate subnet

Use two NICs when Command Centre and Otis use different subnets. Connect the Command Centre server directly to the Otis Layer 3 switch.

![Alternate subnet diagram - CC server with two NICs, directly connected to the Otis Layer 3 switch for the Compass HLI network](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-2c5dc0350a423095feaea539f7c1838a05a581c1%2FSECHUB-otis-integration-01-alternate-subnet-diagram.png?alt=media)

1. On the controller **Advanced Networking** tab, enter the local server IP address.

![Controller properties - Advanced Networking tab with the local server IP entered for the Controller NIC](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-4dffc561b560123424f0a4c4b980b5b0b7632a91%2FSECHUB-otis-integration-02-alternate-subnet-controller.png?alt=media)

2. On the Elevator HLI **Advanced** tab, enter that address in **Additional configuration**.

![Elevator HLI properties - Advanced tab with the local server IP entered in the Additional configuration field](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-db675c2054586cd297b1e5753eace15129234653%2FSECHUB-otis-integration-03-alternate-subnet-hli.png?alt=media)

3. Stop `FT Otis Compass HLI Service`, then configure routing.

   ```
   route -p change 0.0.0.0 mask 0.0.0.0 192.168.50.254 metric 200 if X
   ```

   This assigns the preferred interface by using the lowest metric.

   ```
   route delete 224.0.0.0
   ```

   This removes the existing multicast route.

   ```
   route -p add 224.0.0.0 mask 240.0.0.0 192.168.50.250 metric 30 if X
   ```

   This assigns the lower metric to multicast traffic.

   Replace `X` with the `192.168.50.250` NIC interface number. Use `ipconfig /all` to identify its MAC address. Match that address in `route print`.

![Routing table example - showing the 224.0.0.0 multicast route correctly assigned to the 192.168.50.250 interface with metric 55](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-701af58011ef421afa66401fa0d73ca3b7287b94%2FSECHUB-otis-integration-04-alternate-subnet-routing-table.png?alt=media)

4. Restart `FT Otis Compass HLI Service`.

### Configure the service file

The sample file is located at:

```
C:\Program Files (x86)\Gallagher\Gallagher OTIS Compass High Level Integration\Otis Compass Service\
```

Copy `OtisCompassHli.conf.sample` and rename the copy `OtisCompassHli.conf`.


---

# 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/integrations/elevators/otis/configure-otis-compass-networking.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.