> For the complete documentation index, see [llms.txt](https://docs.gxc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gxc.io/hw/5g/5g-network-appliances/onyx-es7/cable-connections-example.md).
# Cable Connections Example
The diagram below illustrates the connections to the Core/gNB Appliance and FHM (if used in your deployment). Your configuration will vary depending on your deployment but the diagram below is a representation of what the connections will look like.
**Single RU:** Connect the RU directly to the Core/gNB server to s0f3-1 as shown below for a single RU per Cell. A Cell is a port of s0f3, s0f2, or s0f1.
Onboard the RU, Refer to the Onyx Portal Operations Guide *(Manage Equipment > Manage APs > Add APs > Add APs to 5G Networks)*
**Multiple RU:** Connect the RUs to the installed Onyx-FHM-001 starting with port 0. Ensure all RUs are of the same model.
To edit the FHM. Refer to the Onyx Portal Operations Guide *(Manage Equipment > Manage FHM > Edit FHM*
RU to Core/gNB or FHM
---
# 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://docs.gxc.io/hw/5g/5g-network-appliances/onyx-es7/cable-connections-example.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.