> 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/lte/4g-mesh-nodes/gm01/gm01-mesh-node-installation-guide/view-antenna-information.md).

# View Antenna Information

**To view antenna information:**

{% stepper %}
{% step %}
Click the **Antenna** link at the top right side of any of the Mesh Node’s webpages to open the Antenna page to display the following parameters.

* **Connection State** – State of the Mesh Node’s connection to the Onyx Portal via the Gateway AP.
* **Connection Status** – Possible status values are:
  * **Normal Service** – The CPE is connecting properly, and the APN and attenuation is set correctly.
  * **Limited Service** – Possible causes include:
    * APN is not set correctly – the CPE found the right network but can’t attach.
    * The attenuation is too high – the CPE can’t attach to the network.
    * The network settings have been changed so the SIM is no longer provisioned for that network.
  * **No Cell** – This means the CPE can’t see the signal at all. Possible causes are:
    * The Gateway AP is down, so the CPE has no network to connect to.
    * The backhaul filter is not in the correct state causing it to attenuate the signal so the CPE can’t see it.
  * **Attaching/Waiting for NW** – The CPE is trying to attach to the network, it started the process.
  * **Attempt Update** – The CPE can’t attach to the network. The TAU attach is not working.
* **Backhaul Filter** – Filter in use for the backhaul connection.
* **Access Filter** – Filter in use for the Access (CBRS sector coverage) antenna.
* **RSRQ (dB)** – Reference Signal Received Quality. This indicates the quality of the signal from the Gateway AP.
* **SINR (dB)** – Signal to Interference & Noise Ratio of the backhaul signal.

{% hint style="info" %}
**NOTE:** The following parameters are displayed separately for the Primary and Secondary carriers when the Gateway AP is operating in Carrier Aggregation Mode.
{% endhint %}

* **Frequency** – Operating frequency of the Gateway Node (backhaul link).
* **EARFCN** – E-UTRA Absolute Radio Frequency Channel Number of the Gateway Node (backhaul link).
* **RSRP (dBm)** – Reference Signal Received Power for the backhaul link. RSRP is displayed for Antenna 0 port (main) and Antenna 1 port (diversity).
* **RSSI (dB)** – Received Signal Strength Indicator for the backhaul link. RSSI is displayed for Antenna 0 port (main) and Antenna 1 port (diversity).
  {% endstep %}

{% step %}
Use the Antenna page to aim the CPE (backhaul) antenna to achieve the best possible RSRQ, SINR, RSRP, and RSSI readings between the Gateway AP and the Mesh Node.
{% endstep %}
{% endstepper %}


---

# 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/lte/4g-mesh-nodes/gm01/gm01-mesh-node-installation-guide/view-antenna-information.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.