> 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/docs/network-configuration-and-operations-guides/5g-onyx-portal-4.x-operations/manage-equipment/manage-mesh-nodes.md).

# Manage Mesh Nodes

The 5G Mesh Node is a wireless backhaul-capable radio access node for 5G networks. Like an AP, a Mesh Node serves subscribers over the radio access network; unlike a wired AP, it can also relay traffic to another AP or Mesh Node over the air, which lets you extend 5G coverage into areas without a wired backhaul connection.

## View 5G Mesh Node Details

This section describes how to view Mesh Node details.

* [*View Mesh Node Summary Details*](#view-mesh-node-summary-details)
* [*View a Mesh Node's Details*](#view-a-mesh-nodes-details)

### View Mesh Node Summary Details

To view the summary details of all Mesh Node configured in the network:

{% stepper %}
{% step %}
In the navigation pane, click **Equipment > Mesh Node** tab.

The **Equipment** page > **Mesh Node** tab displays the summary details of all Mesh Nodes configured in the network.

* **Mesh Node (n)** — The number of Mesh Nodes configured in the network.
* The list of Mesh Nodes.
  * Mesh Node Service Status.

    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FN7iOkBO5oSE7SrNUBjst%2Fimage.png?alt=media&amp;token=8597395a-0446-4cbc-b8ba-730e9519fe18" alt="" data-size="line"> Green — Mesh AP cell is in a healthy state.
    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FIOaQpWLQY1jOmau1DMyM%2Fimage.png?alt=media&amp;token=e5c3d89c-9e1a-4e0a-999d-d26fce22baf5" alt="" data-size="line"> Red — Mesh AP cell is in service down state.
    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FQQ2gYV3bAHI5TrFu9rT7%2Fimage.png?alt=media&amp;token=f34e8ed3-0e0c-4cc6-9293-576e8928b2df" alt="" data-size="line"> Amber — Mesh AP cell is in unwarranted transmission state.
    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FsXE6duDt2IO6ToFzIL4F%2Fimage.png?alt=media&amp;token=53ec8bbb-ea0a-400a-9aca-312393369840" alt="" data-size="line"> Grey — Mesh AP cell state is shutdown, AP is offline, or Mesh Node is offline.

    To view the Mesh AP Rf Tx status and Mesh AP Last Sync timestamp, hover your cursor over the "Service Status" icon.
* **Name** — The Mesh Node's name.
* **Description** — The Mesh Node's description.
* **Venue** — The name of the venue hosting the Mesh Node.
* **Online** — Indicates the Mesh Node's online status, which is determined by its reachability from the Onyx Portal.

  * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F99qGDJljczjeJBLyd4za%2Fimage.png?alt=media&amp;token=acdef267-a172-4c22-8f3e-876d827000e2" alt="" data-size="line"> Green — Indicates the Mesh Node is connected to the Onyx Portal, and it last checked-in with the Onyx Portal within the last two minutes.
  * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F5mvjhEfhhozDJgNCDJZU%2Fimage.png?alt=media&amp;token=3c90d639-81df-4dbc-802e-9ccec84da5bb" alt="" data-size="line"> Red — Indicates the Mesh Node is not connected to the Onyx Portal, and it last checked-in with the Onyx Portal more than two minutes ago.

  To view the last synchronized at timestamp, hover your cursor over the "Online Status" icon.
* **Interface Status** — Indicates the Mesh Node's interface status.

  * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FXIigi4HXPPW1ugkcd5dE%2Fimage.png?alt=media&amp;token=9a3f8927-233b-4637-848f-cd9b833dd113" alt="" data-size="line"> Green — Indicates GRE tunnel status is okay, and Mesh AP is online.
  * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FnEqfpOgCgGMrJGTGBDW3%2Fimage.png?alt=media&amp;token=b151935f-dfe9-4aee-b91f-eb377de4662d" alt="" data-size="line"> Amber — Indicates Mesh Node is online, but Mesh AP is offline, and GRE tunnel Status is okay.
  * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FAWvDOu50JriOUkZlMKMW%2Fimage.png?alt=media&amp;token=0fc36839-8d13-4a62-9d92-69179278a01b" alt="" data-size="line"> Red — Indicates the GRE tunnel status is not okay.
  * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F1EG7Cqeb9WRcbNinCvsd%2Fimage.png?alt=media&amp;token=e786e5f3-39af-4e20-a87a-f082868f9de9" alt="" data-size="line"> Grey — Indicates the Mesh Node is offline.

  To view the Tunnel status and Mesh AP Power Up status, hover your cursor over the "Interface Status" icon.
* **Compute Resource** — Indicates utilization status of the Mesh Node's computing resources—CPU percentage, Memory percentage, and Disk Utilization percentage.

  * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2Fl2axRRXn664zxHDphsg0%2Fimage.png?alt=media&amp;token=9242e8eb-5a34-4f45-ad3c-6595c127f94c" alt="" data-size="line"> Green — Indicates all parameters are less than or equal to 50%.
  * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FXbHFYEOW5YQsqBGeDKYq%2Fimage.png?alt=media&amp;token=ae32a73a-007c-46d8-be61-57820fab0841" alt="" data-size="line"> Amber — Indicates all parameters are less than or equal to 70%, and at least one parameter is above 50%.
  * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FSKllqNhHbQp4FC7Gtwt8%2Fimage.png?alt=media&amp;token=26406e9d-0933-4a87-b6e3-82b3f8ed38aa" alt="" data-size="line"> Red — Indicates at least one parameter is above 70%.
  * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F7vwZ95O8s520FWCrLpba%2Fimage.png?alt=media&amp;token=b1ff7e80-2ca5-4a22-b9e8-3b86fe724591" alt="" data-size="line"> Grey — Indicates the Mesh Node is offline.

  To view the Disk Utilization, CPU Utilization, and Memory Utilization percentages, hover your cursor over the "Compute Resource Status" icon.
* **Actions** — Options to view details, edit, and delete a Mesh Node.
  {% endstep %}
  {% endstepper %}

### **View a Mesh Node's Details**

**To view a GM03 Mesh Node's details:**

{% stepper %}
{% step %}
In the navigation pane, click **Equipment > Mesh Node** tab.

The **Equipment** page > **Mesh Node** tab displays the summary details of all Mesh Nodes configured in the network.
{% endstep %}

{% step %}
To view a Mesh Node's details, in the list, click its name.

The ***\<Mesh Node name>*** page is displayed.

* **Overview** tab:
  * **Mesh Node Details**:

    * **Name** — The Mesh Node's name.
    * **Serial No.** — The Mesh Node equipment's vendor-assigned serial number.
    * **Venue Name** — The name of the venue hosting the Mesh Node.
    * **Version** — The Mesh Node's software version.
    * **Up Time** — The duration for which the Mesh Node has been continuously operational without any downtime or interruptions.
    * **Mesh AP** — The Mesh AP equipment's vendor-assigned serial number.
    * **Donor AP** — The Mesh Node's donor AP's name.
    * **UUID/Challenge Key** — To view the Mesh Node's Hardware UUID and Challenge Key, click <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F3FMBfOKtw2zjI4ONERQM%2Fimage.png?alt=media&amp;token=01ddb5e4-04e0-409d-8170-7e4492b0c479" alt="" data-size="line"> (view details).
    * **Hostname** — The Mesh Node's hostname.
    * **Description** — The Mesh Node's description.
    * **Device Class** — The Mesh Node's device class—GM03.
    * **Upgrade Status** — Status of the previous Mesh Node software upgrade.

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> The <strong>Upgrade Status</strong> parameter is displayed only during an upgrade and for one hour after the upgrade. </p></div>

    * To view the previous upgrade's details, click the status.

      The **Upgrade Status** dialog box displays the following details:

      * **Description** — Description of the last upgrade's status.
      * **Old Version** — The software version before the upgrade.
      * **New Version** — The new software version.
      * **Updated At** — The timestamp at which the last upgrade completed.
      * **Start Time** — The timestamp at which the last upgrade started.
* **SIM Related Info**:
  * **Active SIM** — The active SIM's status—**Disabled**, **Enabled**.
  * **IMSI** — The IMSI number that identifies the SIM within the network.
  * **IMEI** — The IMEI number that uniquely identifies the equipment.
* Status:
  * **Online** — The Mesh Node's online status.

    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FggNTxqK9UfbLaOFCRhWB%2Fimage.png?alt=media&amp;token=ebd0d85b-f7de-4461-acae-96ffff317171" alt="" data-size="line"> Green — Indicates the Mesh Node is connected to the Onyx Portal, and it last checked-in with the Onyx Portal within the last two minutes.
    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FADWXl52OhsogM26d7377%2Fimage.png?alt=media&amp;token=52d41512-e74a-447a-919a-d5b3f1ca8e53" alt="" data-size="line"> Red — Indicates the Mesh Node is not connected to the Onyx Portal, and it last checked-in with the Onyx Portal more than two minutes ago.

    To view the last synchronized at timestamp, hover your cursor over the "Online Status" icon.
  * **Interface Status** — The Mesh Node's interface status.

    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FsqJBRBRO0RZEMu46Ubdp%2Fimage.png?alt=media&amp;token=bbf96426-72e8-4cc5-bd67-4ef4c77b10dd" alt="" data-size="line"> Green — Indicates GRE tunnel status is okay, and Mesh AP is online.
    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F9AUaDfOXt939KOdtOtwL%2Fimage.png?alt=media&amp;token=f291442d-8817-4d1a-a181-1f72e385e3fa" alt="" data-size="line"> Amber — Indicates the Mesh Node is online, but Mesh AP is offline, and GRE tunnel Status is okay.
    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2Fr9oEeikPcpxtSp6zoqzy%2Fimage.png?alt=media&amp;token=366515c0-15f6-41b7-9b91-bf76578fd8cd" alt="" data-size="line"> Red — Indicates the GRE tunnel status is not okay.
    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FxD9pWBNAyoalqOWWdgKR%2Fimage.png?alt=media&amp;token=58d43ad3-693d-4270-9e96-086aad498e2f" alt="" data-size="line"> Grey — Indicates the Mesh Node is offline.

    To view the Tunnel status and the Mesh AP Power Up status, hover your cursor over the "Interface Status" icon.
  * **Compute Resource** — The Mesh Node's compute resource status.

    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FZ2Tn8QwFm01QyKobkKAJ%2Fimage.png?alt=media&amp;token=be85be73-0790-4332-9883-32d15840883c" alt="" data-size="line"> Green — Indicates all parameters are below 50%.
    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FoQbb3wdoXXRWySMC4fEy%2Fimage.png?alt=media&amp;token=fe60ab4e-c24d-4dda-9829-98b1ff3e97ad" alt="" data-size="line"> Amber — Indicates at least one parameter is above 50% and below 75%.
    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FnHIj0bMckMneLgHMfjHC%2Fimage.png?alt=media&amp;token=a3341da9-683b-4d1b-abdc-0240d6b6048e" alt="" data-size="line"> Red — Indicates at least one parameter is above 75%.
    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FsVBbumUodxvI2F3hIvVl%2Fimage.png?alt=media&amp;token=8b57e62b-d048-44b8-b812-0c9a6afe8893" alt="" data-size="line"> Grey — Indicates the Mesh Node is offline.

    To view the Disk Utilization, CPU Utilization, and Memory Utilization percentages, hover your cursor over the "Compute Resource Status" icon.
  * **Service Status** — The Mesh Node's service status.

    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FdNE7uBfyY2dumEbCYGdh%2Fimage.png?alt=media&amp;token=9019d893-ca21-4fa6-af16-952b1fcf7db7" alt="" data-size="line"> Green — Mesh AP cell is in a healthy state.
    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FDgovl2shO8ocZcX0ImkA%2Fimage.png?alt=media&amp;token=b3ff1951-d470-49fb-aca8-24758fbef3f1" alt="" data-size="line"> Red — Mesh AP cell is in service down state.
    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FdOOzsKzdILWRMfO9CrJ5%2Fimage.png?alt=media&amp;token=6d11225c-d655-4850-a2f9-d3144191072c" alt="" data-size="line"> Amber — Mesh AP cell is in unwarranted transmission state.
    * <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FmUHTZ1aMG7XzkdtQAtcE%2Fimage.png?alt=media&amp;token=a6e379ed-e7f7-4edb-852d-80fc08620f1e" alt="" data-size="line"> Grey — Mesh AP is offline, or Mesh Node is offline.

    To view the Mesh AP Rf Tx status and the Mesh AP last synchronized at timestamp, hover your cursor over the "Service Status" icon.
* **Backhaul Status Details** — Indicates how consistent and stable the network connection is.

  * **Backhaul IP** — The backhaul IP address.
  * **Backhaul Filter State** — The backhaul filter state—Low Pass, High Pass.
  * **Mesh AP Filter State** — The Mesh AP filter state—Low Pass, High Pass.

  The following details are displayed in the case of SC mode for Primary cell, and in the case of CA mode for the Primary and Secondary Cells.

  * **Freq** — The cell's frequency in MHz.
  * **BW** — The cell's bandwidth in dBm.
  * **RSRQ** — The cell's RSRQ in dB.
  * **RSRP (dBm)** – The antenna's RSRP in dBm. Displayed for Antenna 0 and Antenna 1.
  * **RSSI (dBm)** — The antenna's RSSI in dBm. Displayed for Antenna 0 and Antenna 1.
* **Alert Thresholds** — Pre-defined limits set in the system to monitor radio signal quality and generate alerts when certain metrics drop below acceptable levels. These thresholds help proactively identify and address connectivity or performance issues with the mesh node.
  * **RSRP Limit** — Reference Signal Received Power (RSRP) indicates the power level of the LTE reference signals received by the antenna. It is a critical measurement for determining coverage quality and cell selection. If the RSRP drops below -90 dB, it implies weak received signal power, which may lead to coverage holes or poor connectivity for the UE.
  * **RSRQ Limit** — Reference Signal Received Quality (RSRQ) is a measure of signal quality, factoring in interference and noise, and is derived from RSRP and Received Signal Strength Indicator (RSSI). When RSRQ falls below -15 dB, it indicates a high level of interference or poor quality of the received signal. This can result in degraded throughput and unreliable connections.
  * **SINR Limit** — Signal-to-Interference-plus-Noise Ratio (SINR) measures the quality of the wireless link by comparing the strength of the desired signal to the level of background interference and noise. SINR below -13 dB suggests severe interference or noise, potentially leading to significant performance degradation, reduced data rates, or dropped connections.
    {% endstep %}

{% step %}
Click the **Analytics** tab.

The Analytics tab displays time-based visualizations of critical radio signal metrics collected from the Mesh Node. It helps monitor signal stability and quality in real time, identify degradations, and take corrective actions.

* **Selected Range** — The time period from which signal metrics are displayed on the analytics plots. Select the time period in the dropdown to the far right.
* **Performance Analytics**
  * **RSRP Signal** — Measures the average power of reference signals received by the Mesh Node from the donor cell. It serves as a primary indicator of coverage strength. Higher RSRP indicates a stronger and more reliable signal. If RSRP falls below certain thresholds, it may signal weak coverage or physical obstructions. This plot displays frequency-based color coding.
    * **Primary/Secondary** — Select the cell's role.
      * **ant0/ant1** — Select the antenna.
  * **RSRQ Signal** — Indicates the quality of the received signal (interference and noise in the signal) by combining information on interference and overall signal strength. It is derived using RSRP and RSSI (total received power). Lower (more negative) RSRQ values signify higher interference or noise in the environment, which can degrade throughput and reliability. This plot displays frequency-based color coding.
    * **Primary/Secondary** — Select the cell's role.
  * **SINR Signal** — Signal-to-Interference-pus Noise ratio. Measures the ratio of the desired signal strength to the sum of interference and noise. It is a key indicator of overall link quality and expected data rates. Higher SINR values correspond to better radio conditions and higher possible throughput. When SINR drops, it can indicate interference from nearby cells, environmental noise, or hardware faults. This plot displays frequency-based color coding.
  * **Check-In Count** — The number of check-in events from the Mesh Node over time, used to monitor node connectivity responsiveness and health.
    {% endstep %}

{% step %}
Click the **Logs** tab.

* **Logs (n)** — The number of logs for the Mesh Node in the selected date and time range.
* To change the date and time range, select the required timestamps in the <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FQz7fOlIyfrOBx5u8WpeR%2Fimage.png?alt=media&amp;token=9b2b6ecb-e79a-4f01-913f-f111fb34538e" alt="" data-size="line"> fields. The logs list automatically updates to display the corresponding logs.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> Your selections must fall within a seven-day range.</p></div>
* To download the logs in .csv format, in the <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FQcorBYTM4BFSJEsukhXE%2Fimage.png?alt=media&amp;token=31029dba-9ad0-4579-bca2-79a385b11d42" alt="" data-size="line"> field, enter the number of logs to be included in the .csv file, then click <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FA9d0Aek1jV2iPxXuMOWG%2Fimage.png?alt=media&amp;token=edd7a6f0-7ada-421a-857e-c76ec352928d" alt="" data-size="line">. Default value: 5000. The downloaded .csv file includes details such as the timestamp, service, tag, type, and log text.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> You can download a maximum 5000 logs.</p></div>
* To search for a log, in the <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FAMro7PwVe8p4zdXFzvqB%2Fimage.png?alt=media&amp;token=e5107389-4ddf-4e70-b698-553e8879afe7" alt="" data-size="line"> field, enter your search term. The logs list automatically updates to display logs containing the term.
* **Timestamp** — The date and time when each log entry was recorded.
* **Service** — The specific service associated with the log.
* **Type** — The log’s type.
* **Output** — The log’s message.&#x20;
  {% endstep %}
  {% endstepper %}

## Add 5G Mesh Node Equipment

{% hint style="info" %}
**NOTE:** You can add a Mesh Node only if you are a GXC Administrator, Partner Administrator, Super Administrator, or an Administrator.
{% endhint %}

{% hint style="info" %}
**NOTE:** The Mesh Node must check in with the Onyx Portal before it can be registered on the network. It must make an attempt to connect first before you can add its serial number. Once it attempts to connect, you can configure the Mesh Node in the system.
{% endhint %}

**To add a 5G Mesh Node:**

{% stepper %}
{% step %}
In the navigation pane, click **Equipment** > **Mesh Node** tab.

The **Equipment** page > **Mesh Node** tab displays the summary details of all Mesh Nodes configured in the network.
{% endstep %}

{% step %}
In the upper-right corner of the page, click **Add Node** > **Add Mesh Node**.

The **Create Mesh Node** page > **Mesh Node** tab is displayed.

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FQUd2yCOyvcF2Mu3jrSfZ%2Fimage.png?alt=media&amp;token=238d5d7c-c4df-49ae-904f-077ce9da6e1e" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Enter the following details:

* **Venue** — (Required) Select the venue hosting the Mesh Node.
* **Mesh Node Name** — (Required) The Mesh Node's name.
* **Serial No.** — (Required) The Mesh Node equipment's vendor-assigned serial number. The Provisioning Server uses this serial number to generate and provision the keys required for the Mesh Node to operate with the Onyx Portal.
* **Host Name** — (Optional) The Mesh Node's host name.
* **Device Class** — (Required) The Mesh Node's device class—**GM03**. Default value: **GM03**.
* **Description** — (Required) A brief description that will help discern the Mesh Node's role.
  {% endstep %}

{% step %}
Click the **Alert Threshold** tab and enter the following details.

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FSDMpmdZOKIzEYaivgjnb%2Fimage.png?alt=media&amp;token=44f8b0a9-25e0-430d-bd78-19c061bcd8ca" alt=""><figcaption></figcaption></figure></div>

You can configure alert thresholds for the following Mesh Node radio signal quality metrics. When real-time metrics fall below the configured thresholds, alerts trigger automatically enabling timely diagnostics and corrective action.

For information on the corresponding alert rules, see *Semi-Custom Alert Rules*.

* **RSRP Limit** — (Required) Enter the minimum acceptable RSRP limit in the range of -140—44. RSRP measures the average received signal power. A value below this limit indicates weak coverage or possible connection issues. When this limit is breached, an alert is triggered. Default value: -100.
* **RSRQ Limit** — (Required) Enter the minimum acceptable RSRQ limit in the range of -20—3. RSRQ reflects signal quality, considering strength and interference. A value below this limit indicates poor quality or high interference, which may affect performance. When this limit is breached, an alert is triggered. Default value: -15.
* **SINR Limit** — (Required) Enter the minimum acceptable SINR limit in the range of -20–30. SINR measures signal quality against interference and noise. A value below this limit can cause slow data rates or dropped connections. When this limit is breached, an alert is triggered. Default value: 13.
  {% endstep %}

{% step %}
To save the Mesh Node, in the upper-right corner of the page, click **Save Mesh Node**.
{% endstep %}
{% endstepper %}

## Mesh Node-AP Affinity Feature

The Mesh Node-AP Affinity feature manages the association between a Mesh Node and a specific cell. By restricting a Mesh Node to attach to a specific cell, this feature optimizes network resource management and enhances the Mesh Node's performance.

In the Onyx Portal subscriber configuration, administrators can designate a specific cell ID as the "Allowed Cell" for a Mesh Node subscriber. The cell IDs are in the format "<*AP name*>-cell-<*cell id*>". For APs with dual cells, two separate entries, one for each cell, are available for association. For more information, see *Manage Subscriber Accounts*.

{% hint style="info" %}
**NOTE:** For this feature to operate effectively, the desired cell should have a signal strength of around -90 RSRP dBm, while undesired cells should have signal strengths of -110 RSRP dBm or lower.
{% endhint %}

{% hint style="info" %}
**NOTE:** You cannot delete an AP or change its carrier mode while its cell ID is configured as a Mesh Node subscriber's "Allowed Cell". The subscriber configuration must first be cleared of the cell ID, after which the AP can be deleted, or its carrier mode can be changed.
{% endhint %}

{% hint style="info" %}
**NOTE:** Users are responsible for associating valid AP cells. Configuring a non-associated AP cell as an "Allowed Cell" for a Mesh Node, or removing the association of an AP whose cell is configured as an "Allowed Cell", will result in a loss of connectivity for that subscriber.
{% endhint %}

{% hint style="info" %}
**NOTE:** The Mesh Node-AP Affinity feature will not work during handovers between two Gateway APs.
{% endhint %}

## Register Mesh Node SIM Card

GXC ships Mesh Nodes with one SIM card preinstalled. The Mesh Node's SIM card/IMSI must be activated in the Onyx Portal before the Mesh Node can join the network. The Mesh Node's SIM card/IMSI can be added in the Onyx Portal even before the Mesh Node equipment is powered up.

{% hint style="info" %}
**NOTE:** The IMSI of the SIM Card and the Serial Number of the Mesh Node can be found on the Mesh Node's LCI > **System** page.
{% endhint %}

**To register a Mesh Node in the Onyx Portal:**

{% stepper %}
{% step %}
In the navigation pane, click **Subscribers**.

The **Subscribers** page > **Subscriber** tab displays the list of subscribers and any Mesh Nodes in the network.
{% endstep %}

{% step %}
In the upper-right corner of the page, click **Add Subscriber**.

The **Add Subscriber** page is displayed.
{% endstep %}

{% step %}
Enter the following details:

* **Subscriber Name** — (Required) The Mesh Node's name.
* **IMSI** — (Required) The Mesh Node SIM's IMSI number.
* **Auth Key** — (Required) The authentication key.
* **Auth OPC** — (Required) The authentication OPc. Operator Code used to validate the network.
* **Service** — (Required) Select the SIM card's service state—Active or Inactive.
* **Subscriber Groups** — (Required) Select the "Mesh Nodes" subscriber group. For more information on subscriber groups, see *Manage Subscribers > Manage Subscriber Groups*.
* **Add More Subscriber** — Shortcut option to add additional SIM cards/IMSI.
  {% endstep %}

{% step %}
To save the Mesh Node subscriber account, in the upper-right corner of the page, click **Save Subscriber**.

{% hint style="info" %}
**NOTE:** In the subscriber list and subscriber details, the Mesh Node IMSI's Status will be "Unregistered" until the Mesh Node is powered up and its CPE antenna is pointed correctly to the gateway node.
{% endhint %}
{% endstep %}
{% endstepper %}

## Edit Mesh Nodes

{% hint style="info" %}
**NOTE:** You can edit Mesh Node details only if you are a GXC Administrator, Partner Administrator, Super Administrator, or an Administrator.
{% endhint %}

{% hint style="info" %}
**NOTE:** When editing a Mesh Node's details, you can either edit its serial number or edit the rest of its editable parameters. If you edit the serial number, the other parameters will be read-only.
{% endhint %}

**To edit a Mesh Node's details:**

{% stepper %}
{% step %}
In the navigation pane, click **Equipment** > **Mesh Node** tab.

The **Equipment** page > **Mesh Node** tab displays the summary details of all Mesh Nodes configured in the network.
{% endstep %}

{% step %}
For the Mesh Node that you want to edit, in the **Actions** column, click the corresponding ⋮ (options) icon, then click **Edit**.

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F2B1Kb2otIgLfYffZVAaT%2Fimage.png?alt=media&amp;token=415d6979-3b1a-4e80-adf8-60c0569ad005" alt="" width="110"><figcaption></figcaption></figure></div>

The **Edit Mesh Node** page displays the node's details.

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F873O8rtulzMFTxWVVQ0q%2Fimage.png?alt=media&amp;token=7d82cce2-c70b-475c-a073-8449b5568800" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Edit the following details as required:

* **Venue** — (Read only) The name of the venue hosting the Mesh Node.
* **Mesh Node Name** — (Required) The Mesh Node's name.
* **Serial No.** — (Required) The Mesh Node equipment's vendor-assigned serial number. To edit the serial number, click <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2Fk3qQE9wLufBN9iqCJhhX%2Fimage.png?alt=media&amp;token=1e47f66b-4eed-4065-b52e-13b4bcc5dc0f" alt="" data-size="line"> then edit the serial number and save the Mesh Node.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> When editing a Mesh Node's details, you can either edit its serial number or rest of its editable parameters. If you edit the serial number, the other parameters will be view only.</p></div>
* **Host Name** — (Optional) The Mesh Node's host name.
* **Device Class** — (Read only) The Mesh Node's device class.
* **Description** — (Required) The Mesh Node's description.
  {% endstep %}

{% step %}
Click the **Alert Threshold** tab and edit the following details as required.

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FrW5PtAjcukFLnweQo7Vc%2Fimage.png?alt=media&amp;token=cd1cd918-09cf-4001-a63f-d1b2301fc9c1" alt=""><figcaption></figcaption></figure></div>

You can configure alert thresholds for the following Mesh Node radio signal quality metrics. When real-time metrics fall below the configured thresholds, alerts trigger automatically enabling timely diagnostics and corrective action.

For information on the corresponding alert rules, see *Semi-Custom Alert Rules*.

* **RSRP Limit** — (Required) Enter the minimum acceptable RSRP limit. RSRP measures the average received signal power. A value below this limit indicates weak coverage or possible connection issues. When this limit is breached, an alert is triggered. Default value: -100.
* **RSRQ Limit** — (Required) Enter the minimum acceptable RSRQ limit. RSRQ reflects signal quality, considering strength and interference. A value below this limit indicates poor quality or high interference, which may affect performance. When this limit is breached, an alert is triggered. Default value: -15.
* **SINR Limit** — (Required) Enter the minimum acceptable SINR limit. SINR measures signal quality against interference and noise. A value below this limit can cause slow data rates or dropped connections. When this limit is breached, an alert is triggered. Default value: 13.
  {% endstep %}

{% step %}
To save your edits, in the upper-right corner of the page, click **Save Mesh Node**.
{% endstep %}
{% endstepper %}

## Reboot Mesh Nodes

**To reboot a Mesh Node:**

{% stepper %}
{% step %}
In the navigation pane, click **Equipment** > **Mesh Node** tab.

The **Equipment** page > **Mesh Node** tab displays the summary details of all Mesh Nodes configured in the network.
{% endstep %}

{% step %}
For the Mesh Node that you want to reboot, in the **Actions** column, click the corresponding ⋮ (options) icon, then click **View**.

The ***\<Mesh Node name>*** page is displayed.
{% endstep %}

{% step %}
In the upper-right corner of the page, click **Actions > Reboot**.

A confirmation dialog box is displayed.
{% endstep %}

{% step %}
To confirm rebooting the Mesh Node, click **Yes**.
{% endstep %}
{% endstepper %}

## Delete Mesh Nodes

{% hint style="info" %}
**NOTE:** You can delete a Mesh Node only if you are a GXC Administrator, Partner Administrator, Super Administrator, or an Administrator.
{% endhint %}

{% hint style="info" %}
**NOTE:** Before you delete a Mesh Node, confirm that no active subscribers depend on it for backhaul, since deleting it will disconnect any traffic relayed through it.
{% endhint %}

**To delete a Mesh Node:**

{% stepper %}
{% step %}
In the navigation pane, click **Equipment** > **Mesh Node** tab.

The **Equipment** page > **Mesh Node** tab displays the summary details of all Mesh Nodes configured in the network.
{% endstep %}

{% step %}
For the Mesh Node that you want to delete, in the **Actions** column, click the corresponding ⋮ (options) icon, then click **Delete**.

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F8a5RvLCx9bqGqQsS1I9I%2Fimage.png?alt=media&amp;token=825b1a9c-967c-4393-a2cd-c361f1ec71e5" alt="" width="110"><figcaption></figcaption></figure></div>

A confirmation dialog box is displayed.

<div data-with-frame="true"><figure><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FEpxJRz3w9l84drVjfS1O%2Fimage.png?alt=media&amp;token=8c2a7363-5601-4c4a-a35c-5a6927819d42" alt="" width="410"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
To confirm deleting the Mesh Node, click **Yes.**
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.gxc.io/docs/network-configuration-and-operations-guides/5g-onyx-portal-4.x-operations/manage-equipment/manage-mesh-nodes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
