> 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/gm02/gm02-mesh-node-installation-guide/view-mesh-node-status-and-logs.md).

# View Mesh Node Status and Logs

The **Status** page allows you to view the status and logs for the Mesh Node’s Wi-Fi network, Backhaul Link, and Mesh Tunnel. When you login to the Mesh Node, the **Status** page is the first page that you will see displayed.

## View Status

The center column of the Status display provides a status indicator for each of the Mesh Node’s systems with green indicating “Normal” or “Active” operation and red indicating that there is an issue with that particular system.

{% hint style="info" %}
**NOTE:** It may take a significant amount of time for the Onyx Portal to set up the Mesh Node and add it to the network.
{% endhint %}

* The Wi-Fi status will always be Active (green) if you are connected to the GM02 via Wi-Fi, which is the standard way to connect to the unit. If the Wi-Fi is not working and you have to connect using an Ethernet cable, the status will be Inactive (red).
* The Backhaul Link status will change to Normal (green) once the backhaul antenna is properly pointed and the connection to the Onyx Portal is established.
* The Mesh Tunnel status will be Active (green) once the Mesh Tunnel is established with the Onyx Portal.

## View Logs and Status Details

{% stepper %}
{% step %}
Click the **Log** button on the Wi-Fi row to view the log file for the Wi-Fi service.
{% endstep %}

{% step %}
Click the **Log** button on the **Backhaul Link** row to view the log file for the Backhaul Link.
{% endstep %}

{% step %}
Click the **Status** button on the Mesh Tunnel row to view the status details such as service (running or not), wwan-ip address, wwan0-ping status, eth1-ip address and tunnel ping status.
{% endstep %}
{% endstepper %}

## View or Download System Logs

The System logs can be viewed or downloaded from the **System** page.

{% stepper %}
{% step %}
Click the **System** link at the top right side of any of the Mesh Node’s webpages. The logs can be viewed or downloaded in the **System Logs** section of the page.
{% endstep %}

{% step %}
To view the “syslog”, and the “mesh\_manager.log” without downloading the log file, click the **view log** link adjacent to the file that you wish to view.

{% hint style="info" %}
**NOTE:** View log is limited to the most recent entries in the log file. The current limit is set to 10,000 lines. To view the entire log, use the **Download logs** feature.
{% endhint %}
{% endstep %}

{% step %}
To download the logs, click the **Download logs** button and follow the prompts to save the tar.gz file to your local laptop or desktop computer.
{% 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/gm02/gm02-mesh-node-installation-guide/view-mesh-node-status-and-logs.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.