> 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/4g-onyx-portal-4.x-operations/manage-equipment/manage-access-points.md).

# Manage Access Points

The AP, in 4G networks the eNodeB and in 5G networks the gNodeB function, handles the air interface for UE. For core services, each AP connects to an Onyx Edge. For getting grants from SAS, a different kind of resource called a CBSD must be created. Each CBSD is associated with a single AP. CBSDs do not directly contact the SAS; Domain Proxy is used to communicate with SAS, it sends requests to SAS on behalf of CBSDs.

## Carrier Modes

The 4G Onyx solution supports the Single Carrier (SC), Dual Carrier (DC), and Carrier Aggregation (CA) carrier modes.

{% hint style="info" %}
**NOTE:** The DC and CA modes are not supported on Mesh APs. This is because the CA and DC modes require four antenna ports (filters), while the Mesh Node only supports two.
{% endhint %}

* Single Carrier (SC) Mode – In SC mode, APs use a single carrier frequency, making it suitable for smaller networks or areas with lower traffic where bandwidth needs can be met with one frequency. SC mode is often used for basic services with lower data rates. While it performs well in environments with limited spectrum, it may become less effective as data demands grow. APs in SC mode use a single antenna and support up to 96 active UE per AP.

* Dual Carrier (DC) Mode – In DC mode, APs use two carrier frequencies simultaneously, effectively doubling the available bandwidth. Compared to the SC mode, DC mode provides the same data rates but allows for increased network capacity by effectively doubling the number of connected UE. DC mode is particularly advantageous for covering two distinct areas from a single AP, especially when the required throughput is less than that of a single channel. APs in DC mode use two antennas and support up to 96 + 96 active UE per carrier sector, with a total aggregate UE capacity of 192 UE per AP.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> DC handovers are not supported in this release.</p></div>

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> For DC mode, the APs must be updated with the "FAP010 Dual Carrier Function" license.</p></div>

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> The DC mode is not supported with Mesh APs.</p></div>

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> If APs running software version BaiBLQ_3.1.14 are configured for DC mode, to ensure seamless handovers between an AP's cells, GXC Technical Support must remotely log on to DC APs and run an internal command. Please contact GXC Technical Support to fulfill this requirement.</p></div>

* Carrier Aggregation (CA) Mode – In CA mode, APs can combine up to two component carriers (frequencies from the same or different bands) to increase throughput capacity and peak data rates. This mode enhances spectrum efficiency and significantly improves network performance, supporting high-speed data for bandwidth-intensive applications. CA mode is ideal for scenarios requiring peak data rates that exceed the capacity of a single carrier. It is better suited for use cases with lower device density but higher data throughput requirements, effectively doubling the data capacity. APs in CA mode use a single antenna and can support up to 96 active UE per AP.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> For CA mode, the APs must be updated with the "FAP009 Carrier Aggregation Function" license.</p></div>

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> For CA mode, the UE must also support CA.</p></div>

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> The CA mode is not supported with Mesh APs.</p></div>

### AP LCI

The carrier mode configurations required in the AP equipment are managed by GXC. For queries, please contact GXC Technical Support.

## Managed Neighbor Relations

Handovers enable uninterrupted service continuity as active UE move between cells. GXC's Onyx solution supports both intra-AP and inter-AP handovers using a "make-before-break" approach, ensuring seamless mobility for mission-critical applications.

Neighbor cell relationships are configured in the Onyx Portal, providing administrators with complete control over handover topology. The system automatically generates an initial all-to-all neighbor configuration that can be customized with prioritized neighbor lists for each cell.

For comprehensive information configuring and managing neighbor relations, see the *4G Onyx Handovers Application Note*.

## Suspended Grant Handling

When a grant is suspended, spectrum inquiry is initiated to seek a new grant. If a new grant is chosen, the suspended grant is relinquished immediately, and a grant request is sent for the chosen new grant.

* In single grant scenarios:
  * If a new grant is available, it is chosen, and the suspended grant is relinquished.
  * If no new grant is available, the suspended grant is maintained.
* In dual grant scenarios:
  * If both grants are suspended:
    * If two new grants are available, they are both chosen, and the suspended grants are relinquished.
    * If only one new grant is available, the new grant is chosen. Depending on the best compatibility with this new grant:
      * The better of the two suspended grants is retained, and the other relinquished. Here, better is the one that is first larger in bandwidth size and then contiguous. Preference order or power of grants is not used here to keep the implementation simple. If both grants are equal with respect to both bandwidth size and contiguity, then the lower frequency is chosen first.
      * If none of the suspended grants is compatible with the new grant, both the suspended grants are relinquished. If no new grants are available, both suspended grants are retained.
  * If only one grant is suspended:

    * If at least two new grants are available:
      * Of the possible choice of grants, the best compatible two are chosen (new grant + the existing authorized grant).
      * The suspended grant is relinquished.
      * If it is not part of the chosen two, the existing authorized grant is also relinquished.
    * If only one new grant is available and it is compatible with the existing authorized grant, it is chosen, and the suspended grant is relinquished.
    * If no such new grant is available, the suspended grant is maintained.

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> The suspended grant is relinquished immediately, and a grant request is sent for the chosen new grant. However, the SAS may reject the grant request, leaving the CBSD bereft of grants.</p></div>

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> It is expected that the SAS does not include currently issued grants (be it granted, authorized, or suspended) as part of available channels, especially when it is suspended. If the suspended grant is part of the available channel, then the same suspended channel/grant may be chosen. It is also possible that some other channel will be chosen. There is no guarantee that another channel will be tried instead of the suspended grant.</p></div>

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> Since Spectrum Inquiry is now initiated as long as there are suspended grants, to avoid continuous Spectrum Inquiry, a Spectrum Inquiry is sent only five minutes after the previous Spectrum Inquiry.</p></div>

## View AP Details

This section describes how to:

* [*View Summary Details of All APs*](#view-summary-details-of-all-aps)
* [*View an AP's Details*](#view-an-aps-details)

### **View Summary Details of All APs**

**To view the summary details of all APs in a 4G network:**

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

The **Equipment** page > **Access Points** tab displays the summary details of all APs configured in the network.

<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%2FV0v4Gcph1cSbOzSus5EJ%2Fap-view-summary.png?alt=media&amp;token=8ce5a037-8690-4646-a655-81cb4f29da4f" alt=""><figcaption></figcaption></figure></div>

* AP Service Status — Indicates the AP's service status based on the RF transmission state of its cell(s).

  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FZywebLtTLxXc2MKnAYIb%2Ficon-service-status-green.png?alt=media\&token=d5eb44a4-9aa3-4bcd-a4ce-bdd3dcd2a563) (green) – Indicates the AP's service state is healthy and the neighbor configuration is in sync.
  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2Fvu42mnExMXEjCu3VGyhX%2Fimage.png?alt=media\&token=ce6e31d1-542c-4fdc-9839-11ec8f94582e) (amber) — Indicates the AP's service state is Partial or Unwarranted, or the neighbor configuration is not in sync.
  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FiHEQhrrr113aWHfk3SdF%2Ficon-service-status-red.png?alt=media\&token=4eb60ea7-7e37-498f-ab3f-d76fab2eaa56) (red) – Indicates the AP's service state is Service Down.
  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FxE2wEaJsMMBETSGqFjCo%2Ficon-service-status-grey.png?alt=media\&token=bce212be-77a4-4d85-8cff-baf4c5a8b451) (grey) – Indicates the AP is offline, the associated Onyx Edge is offline, or the service state is Shutdown.

  Hovering over the Service Status icon displays the following details:

  * **Cell 1 Rf Tx** – Indicates whether RF transmission for Cell 1 is On or Off.
  * **Cell 1 Desired State** – Indicates whether RF transmission for Cell 1 is in the desired state — Yes or No.
  * **Cell 2 Rf Tx** – (Displayed only for dual-cell APs) Indicates whether RF transmission for Cell 2 is On or Off.
  * **Cell 2 Desired State** – (Displayed only for dual-cell APs) Indicates whether RF transmission for Cell 2 is in the desired state — Yes or No.
  * **Neighbor Update Status** – Indicates whether the AP's neighbor configuration is in sync — IN\_SYNC or NOT\_IN\_SYNC.
* **Name** – The AP's name.

  To view the AP equipment's vendor-assigned serial number, hover your cursor over the AP's name.
* **Venue** – The name of the venue hosting the AP.
* **B/W 1 (MHz)** – The bandwidth for cell 1 in MHz.
* **B/W 2 (MHz)** – (Displayed only if DC mode is configured) The bandwidth for cell 2 in MHz.
* **Freq 1 (MHz)** – The frequency for cell 1 in MHz.
* **Freq 2 (MHz)** – (Displayed only if DC mode is configured) The frequency for cell 2 in MHz.
* **Cell ID 1** – The Cell ID for Cell 1.
* **Cell ID 2** – (Displayed only if DC mode is configured) The Cell ID for Cell 2.
* **PCI 1** – The Physical Cell ID (PCI) for cell 1. The PCI is used for cell identity during cell selection procedure, and is used by UE to decode physical layer data being transmitted by the AP.
* **PCI 2** – (Displayed only if DC mode is configured) The PCI for cell 2.
* **Pwr 1 (dBm)** – The power in dBm for cell 1.
* **Pwr 2 (dBm)** – (Displayed only if DC mode is configured) The power for cell 2.
* **Online** – Indicates the AP's online status, which is determined by its reachability from the Onyx Portal.

  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FweFEJNnJsmVdvFDHmRsm%2Ficon-online-status-green.png?alt=media\&token=17b6e737-de82-473d-aad7-2f802028a13f) (green) – Indicates the AP has checked-in with the Onyx Portal in the last five minutes.
  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FZohzOGtzTsuXHQaFWIBM%2Ficon-online-status-red.png?alt=media\&token=5e81ae71-e1ed-48cb-8380-b83880e79d70) (red) – Indicates the AP has not checked-in with the Onyx Portal in the last five minutes. Or, the time reported is older than five minutes.
  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FIxHbkQtQQUDqyHP6MdwF%2Ficon-online-status-grey.png?alt=media\&token=591f8d34-d3f3-4023-bf25-7966fd116774) (grey) – Indicates the associated Onyx Edge is offline.

  Hovering your cursor over the "Online Status" icon displays the last check-in timestamp.
* **Interface Status** – Indicates the AP's interface status.

  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F4CBj8TZIUDPsdxCuGkEN%2Ficon-interface-status-green.png?alt=media\&token=1e98e305-88b5-442e-99e6-02ac1745e033) (green) – Indicates the AP is MME-connected.
  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2Fu1MOfffYGH62lqdVYQcP%2Ficon-interface-status-red.png?alt=media\&token=798bed1a-7986-4140-8086-8c5ea4d5894a) (red) – Indicates the AP is MME-disconnected.
  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FfkRNbsj0pI0iT0nB2gsD%2Ficon-interface-status-grey.png?alt=media\&token=bf9874b0-79fb-4371-9065-b742c5079932) (grey) – Indicates the AP is offline.

  Hovering your cursor over the "Interface Status" icon displays the MME status and last synchronized at timestamp.
* **IPSec Status** – Indicates status of IPSec tunnel between the AP and the Onyx Edge and the IPSec certificate’s validity. Note that the certificate status is that of the generated certificate, and not of the one uploaded to the AP.

  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2Fl3c9H7KZwAPC28d5wdDn%2Ficon-ipsec-status-green.png?alt=media\&token=02c5b8c5-c038-48c9-b9b4-fca11cc145bf) (green) – The AP is IPSec-enabled and the desired number of active IPSec tunnels with the Onyx Edge are up, and the certificate is valid for more than seven days.
  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FeAbCntt9UDX8T2ZgKrqk%2Ficon-ipsec-status-amber.png?alt=media\&token=de4fcf71-5817-44e8-9f90-4942222778a4) (amber) – The AP is IPSec-enabled and less than the desired number of active IPSec tunnels with the Onyx Edge are up, and/or the certificate is valid for less than seven days.
  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FIUrYSsOnZzJKMvo31kDV%2Ficon-ipsec-status-red.png?alt=media\&token=689c0bd6-93b3-448d-aa58-a57bf1a56e72) (red) – All the IPSec tunnels with the Onyx Edge are down, and the certificate’s validity has expired.
  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FxeP3iNaxrysNZQLwhxH6%2Ficon-ipsec-status-grey.png?alt=media\&token=b6ac67c0-6dee-4acb-ba78-441b01f59c8a) (grey) – Any of the following:
    * The AP is offline.
    * The associated Onyx Edge is offline.
    * The AP is IPSec-disabled.
    * IPSec tunnel information is not available.

  Hovering your cursor over the “IPSec Status” icon displays additional details.
* **Sync Status** – Indicates status of the AP's time reference synchronization with the primary clock source.
  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2Fl3c9H7KZwAPC28d5wdDn%2Ficon-ipsec-status-green.png?alt=media\&token=02c5b8c5-c038-48c9-b9b4-fca11cc145bf) (green) – AP is in sync with the clock source.
  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FIUrYSsOnZzJKMvo31kDV%2Ficon-ipsec-status-red.png?alt=media\&token=689c0bd6-93b3-448d-aa58-a57bf1a56e72) (red) – AP is not in sync with the clock source.
  * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FxeP3iNaxrysNZQLwhxH6%2Ficon-ipsec-status-grey.png?alt=media\&token=b6ac67c0-6dee-4acb-ba78-441b01f59c8a) (grey) – Any of the following:
    * The AP is offline.
    * The Onyx Edge associated with the AP is offline.
    * The AP's Sync Mode is set to “Free Running”.
    * The AP’s sync status is not available.
* **Actions** – Options to view details, edit, and delete APs.

To include or exclude additional details from the list, click <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F1t6W43smlaKTcL93oWyL%2Fimage.png?alt=media&amp;token=5ec847a7-8812-4a19-ab97-c86655e36118" alt="" data-size="line"> (additional details) and select or clear from the following additional parameters:

* **IP Address** – The AP's IP address.
* **Model** – The AP equipment's model.
* **Software Version** – The AP's software version.
* **Up Time** – The duration for which the AP has been continuously operational without any downtime or interruptions.
* **FSM State** – The AP's Finite State Machine (FSM) state indicating the AP's operational state.
* **GPS Latitude** – The AP equipment's GPS latitude coordinate.
* **GPS Longitude** – The AP equipment's GPS longitude coordinate.
* **Access Mode** – The UE access mode. By default, Open Access—authorized UE will have access to any cell in the network.
  {% endstep %}
  {% endstepper %}

### **View an AP's Details**

**To view an AP's details in a 4G network:**

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

The **Equipment** page > **Access Points** tab displays the summary details of all APs configured in the network.
{% endstep %}

{% step %}
To view the details of a particular AP, click its name.

The ***\<AP name>*** page > **Overview** tab displays the AP's details.

* **Access Point Details**:
  * **Name** – The AP's name.
  * **Serial Number** – The AP equipment's vendor-assigned serial number.
  * **Description** – The AP's description.
  * **Venue** – The name of the venue hosting the AP.
  * **Upgrade Status** – Status of the previous AP 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 details, click the status.

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

    * **Description** – Description of the last upgrade's status.
    * **Old Version** – The AP software version before the upgrade.
    * **New Version** – The new AP software version.
    * **Updated At** – Timestamp at which the last upgrade completed.
    * **Start Time** – Timestamp at which the last upgrade started.
  * **Online** – Indicates the AP's online status, which is determined by its reachability from the Onyx Portal.

    * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F5Fb0HOqHNq9pf5SsFcQN%2Ficon-online-status-green.png?alt=media\&token=a6282035-609d-4036-bdf5-37cf39d00619) (green) – Indicates the AP has checked-in with the Onyx Portal in the last five minutes.
    * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FCMzIjwf3zchkkOMZeohs%2Ficon-online-status-red.png?alt=media\&token=ce1f4660-a0df-487e-bfeb-c33c9d2e52c9) (red) – Indicates the AP has not checked-in with the Onyx Portal in the last five minutes. Or, the time reported is older than five minutes.
    * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FuAjf57FGGngRwtUiOxZE%2Ficon-online-status-grey.png?alt=media\&token=8516b150-50c2-4fd4-8e8c-0e335f1d6374) (grey) – Indicates the associated Onyx Edge is offline.

    Hovering your cursor over the "Online Status" icon displays the last check-in timestamp.
  * **Interface Status** – Indicates the AP's interface status.

    * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FJMYN4gczD8ad8s5Uexta%2Ficon-interface-status-green.png?alt=media\&token=b0e36f00-9d80-4b9f-a08c-28422e6a6c17) (green) – Indicates the AP is MME-connected.
    * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2F9nBHXH5Th3tJ8OnoHiTO%2Ficon-interface-status-red.png?alt=media\&token=cf3cb05a-8139-4a6c-b250-a962d90a0f8c) (red) – Indicates the AP is MME-disconnected.
    * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FzGZiZFjRbilVB4Mch0nV%2Ficon-interface-status-grey.png?alt=media\&token=ea3dc764-ce77-4867-920a-91dbb036dc9f) (grey) – Indicates the AP is offline.

    Hovering your cursor over the "Interface Status" icon displays the MME status and last synchronized at timestamp.
  * **Service Status** – Indicates the AP's service status.

    An AP can have one or two cells depending on the AP's carrier mode.

    Cell states per cell:

    <table><thead><tr><th width="120">RF Tx Desired</th><th width="119.6666259765625">Rf Tx Actual</th><th width="157.6666259765625">“Service Status” Icon</th><th>Cell State</th></tr></thead><tbody><tr><td>On</td><td>On</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FWfs3as0Kjkley3LYIfdF%2Ficon-service-status-green.png?alt=media&amp;token=fedb174a-97bf-4976-af92-00004f9b0837" alt=""> (green)</td><td>Healthy</td></tr><tr><td>Off</td><td>Off</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FKVUfPfGWjuvw5EiXsIlq%2Ficon-service-status-grey.png?alt=media&amp;token=4f682728-404f-4233-bb4c-409b9c5b4b04" alt=""> (grey)</td><td>Shutdown, the AP is offline, or the associated Onyx Edge is offline.</td></tr><tr><td>On</td><td>Off</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FO3j3tMTfAKPO4Kf1B7P3%2Ficon-service-status-red.png?alt=media&amp;token=2477b5c9-4201-4d98-aaa1-83f9f028f4c0" alt=""> (red)</td><td>Service Down</td></tr><tr><td>Off</td><td>On</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FwRbhytNFPgCZiKgSHsP7%2Ficon-service-status-amber.png?alt=media&amp;token=e2fda2a7-3eac-49f0-bfb5-67e39be7f15f" alt=""> (amber)</td><td>Unwarranted Transmission</td></tr></tbody></table>

    \
    Cell states for two cells:

    <table><thead><tr><th width="128.6666259765625">Cell 1 State</th><th width="127.6666259765625">Cell 2 State</th><th width="157.6666259765625">“Service Status” Icon</th><th>Notes</th></tr></thead><tbody><tr><td>Healthy</td><td>Healthy</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FWfs3as0Kjkley3LYIfdF%2Ficon-service-status-green.png?alt=media&amp;token=fedb174a-97bf-4976-af92-00004f9b0837" alt=""> (green)</td><td>Perfectly okay transmission.</td></tr><tr><td>Healthy</td><td>Shutdown</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FWfs3as0Kjkley3LYIfdF%2Ficon-service-status-green.png?alt=media&amp;token=fedb174a-97bf-4976-af92-00004f9b0837" alt=""> (green)</td><td>As desired, the service is up.</td></tr><tr><td>Healthy</td><td>Service Down</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FwRbhytNFPgCZiKgSHsP7%2Ficon-service-status-amber.png?alt=media&amp;token=e2fda2a7-3eac-49f0-bfb5-67e39be7f15f" alt=""> (amber)</td><td>One cell is down.</td></tr><tr><td>Healthy</td><td>Unwarranted</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FwRbhytNFPgCZiKgSHsP7%2Ficon-service-status-amber.png?alt=media&amp;token=e2fda2a7-3eac-49f0-bfb5-67e39be7f15f" alt=""> (amber)</td><td>One cell is not behaving as expected.</td></tr><tr><td>Shutdown</td><td>Healthy</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FWfs3as0Kjkley3LYIfdF%2Ficon-service-status-green.png?alt=media&amp;token=fedb174a-97bf-4976-af92-00004f9b0837" alt=""> (green)</td><td>As desired, the service is up.</td></tr><tr><td>Shutdown</td><td>Shutdown</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FKVUfPfGWjuvw5EiXsIlq%2Ficon-service-status-grey.png?alt=media&amp;token=4f682728-404f-4233-bb4c-409b9c5b4b04" alt=""> (grey)</td><td>User shuts down full service.</td></tr><tr><td>Shutdown</td><td>Service Down</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FO3j3tMTfAKPO4Kf1B7P3%2Ficon-service-status-red.png?alt=media&amp;token=2477b5c9-4201-4d98-aaa1-83f9f028f4c0" alt=""> (red)</td><td>User's desire is one cell and that cell’s service is down.</td></tr><tr><td>Shutdown</td><td>Unwarranted</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FwRbhytNFPgCZiKgSHsP7%2Ficon-service-status-amber.png?alt=media&amp;token=e2fda2a7-3eac-49f0-bfb5-67e39be7f15f" alt=""> (amber)</td><td>Unwarranted.</td></tr><tr><td>Service Down</td><td>Healthy</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FwRbhytNFPgCZiKgSHsP7%2Ficon-service-status-amber.png?alt=media&amp;token=e2fda2a7-3eac-49f0-bfb5-67e39be7f15f" alt=""> (amber)</td><td>One cell is down.</td></tr><tr><td>Service Down</td><td>Shutdown</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FO3j3tMTfAKPO4Kf1B7P3%2Ficon-service-status-red.png?alt=media&amp;token=2477b5c9-4201-4d98-aaa1-83f9f028f4c0" alt=""> (red)</td><td>User's desire is one cell and that cell’s service is down.</td></tr><tr><td>Service Down</td><td>Service Down</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FO3j3tMTfAKPO4Kf1B7P3%2Ficon-service-status-red.png?alt=media&amp;token=2477b5c9-4201-4d98-aaa1-83f9f028f4c0" alt=""> (red)</td><td>Both cells are out of service.</td></tr><tr><td>Service Down</td><td>Unwarranted</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FO3j3tMTfAKPO4Kf1B7P3%2Ficon-service-status-red.png?alt=media&amp;token=2477b5c9-4201-4d98-aaa1-83f9f028f4c0" alt=""> (red)</td><td>User's desire is one cell and that cell’s service is down.</td></tr><tr><td>Unwarranted</td><td>Healthy</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FwRbhytNFPgCZiKgSHsP7%2Ficon-service-status-amber.png?alt=media&amp;token=e2fda2a7-3eac-49f0-bfb5-67e39be7f15f" alt=""> (amber)</td><td>One cell is not behaving as expected.</td></tr><tr><td>Unwarranted</td><td>Shutdown</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FwRbhytNFPgCZiKgSHsP7%2Ficon-service-status-amber.png?alt=media&amp;token=e2fda2a7-3eac-49f0-bfb5-67e39be7f15f" alt=""> (amber)</td><td>Unwarranted.</td></tr><tr><td>Unwarranted</td><td>Service Down</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FO3j3tMTfAKPO4Kf1B7P3%2Ficon-service-status-red.png?alt=media&amp;token=2477b5c9-4201-4d98-aaa1-83f9f028f4c0" alt=""> (red)</td><td>User's desire is one cell and that cell’s service is down.</td></tr><tr><td>Unwarranted</td><td>Unwarranted</td><td><img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FwRbhytNFPgCZiKgSHsP7%2Ficon-service-status-amber.png?alt=media&amp;token=e2fda2a7-3eac-49f0-bfb5-67e39be7f15f" alt=""> (amber)</td><td>Unwarranted.</td></tr></tbody></table>

    Hover your cursor over the "Service Status" icon to view the cell's RF Tx status and cell's desired status. In DC mode, info is displayed for Cell 1 and Cell 2, and in CA mode for Primary and Secondary cells.
  * **IPSec Status** – (Displayed only if IPSec is enabled.) Indicates status of the IPSec tunnels with the Onyx Edge and the IPSec certificate's validity. Note that the certificate status is that of the generated certificate, and not of the one uploaded to the AP.

    * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2Fzv59kRKuJvxG2kPSnHa4%2Ficon-ipsec-status-green.png?alt=media\&token=0ab72ea6-698f-4f83-bc4b-a9476962a3da) (green) – The AP is IPSec-enabled and the desired number of active IPSec tunnels with the Onyx Edge are up, and the certificate is valid for more than seven days.
    * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FqtIl80fafg2AITzFgrbi%2Ficon-ipsec-status-amber.png?alt=media\&token=58afc7df-709c-4722-942c-a15bd588ca1b) (amber) – The AP is IPSec-enabled and less than the desired number of active IPSec tunnels with the Onyx Edge are up, and/or the certificate is valid for less than seven days.
    * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FGzWlFxxdWGakQszbzTS8%2Ficon-ipsec-status-red.png?alt=media\&token=a3e75cfa-af46-441f-a318-ce7f3d66b381) (red) – All the IPSec tunnels with the Onyx Edge are down, and the certificate's validity has expired.
    * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FzUU60lu6hxvs5CVjdCpR%2Ficon-ipsec-status-grey.png?alt=media\&token=48f51d0f-021a-4eea-89b6-1334092169cb) (grey) – Any of the following:
      * The AP is offline.
      * The associated Onyx Edge is offline.
      * The AP is IPSec-disabled.
      * IPSec tunnel information is not available.

    Hovering your cursor over the "IPSec Status" icon displays additional details.
  * **Sync Status** – Indicates the AP's time reference synchronization status with the primary clock source.
    * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2Fzv59kRKuJvxG2kPSnHa4%2Ficon-ipsec-status-green.png?alt=media\&token=0ab72ea6-698f-4f83-bc4b-a9476962a3da) (green) – AP is in sync with the clock source.
    * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FGzWlFxxdWGakQszbzTS8%2Ficon-ipsec-status-red.png?alt=media\&token=a3e75cfa-af46-441f-a318-ce7f3d66b381) (red) – AP is not in sync with the clock source.
    * ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FzUU60lu6hxvs5CVjdCpR%2Ficon-ipsec-status-grey.png?alt=media\&token=48f51d0f-021a-4eea-89b6-1334092169cb) (grey) – Any of the following:
      * The AP is offline.
      * The Onyx Edge associated with the AP is offline.
      * The AP's Sync Mode is set to "Free Running".
      * The AP's sync status is not available.
  * **Onyx Edge** – The associated Onyx Edge.
  * **MME Status** – The AP's MME connection status—Connected or Disconnected.
  * **IP Address** – The AP's IP address.
  * **VIP Address** – (Displayed only for IPSec-enabled APs) The Virtual IP address (inner IP address) used for MME connection.
  * **Mesh Node** – (Displayed only for Mesh APs) The associated Mesh Node.
* **AP Properties**:
  * **View License** — Click to view the AP's license 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%2FLHjJ2WG9O7b8t4W5sypx%2F4g-ap-view-details-license-db.png?alt=media&amp;token=69f99aac-6529-4b86-9749-36c5110ba0c9" alt="" width="432"><figcaption></figcaption></figure></div>
  * **Certificate Status** – (Displayed only when IPSec is enabled.) The IPSec certificate expiry status.
  * **Model** – The AP equipment's model—G100, G101, G501.
  * **Software Version** – The AP's software version.
  * **Up Time** – The duration for which the AP has been continuously operational without any downtime or interruptions.
  * **Reported Time** – The timestamp at which the AP's data was last reported.
  * **Config/FSM State** – The current configuration synchronization status between the Onyx Portal and the AP. The **Config/FSM State** parameter displays one of the following status values:

    * **Updating Configuration** – Configuration changes made in the Onyx Portal have not yet been applied to the AP.
    * **In Sync** – Configuration between Onyx Portal and the AP is in sync.
    * **Disconnected** – The AP is offline and not connected to the Onyx Portal.
    * **Rebooting** – The AP is currently rebooting.
    * **Stuck** – Configuration update has not completed within 10 minutes of being pushed from the Onyx Portal as the AP is rejecting the configuration.
    * **Pending Reboot with Schedule** – A reboot is pending to apply neighbor configuration updates and is scheduled for a specified time. The scheduled time is shown in the **Reboot Schedule for Neighbor Update** parameter.
    * **Pending Reboot Without Schedule** – A reboot is pending to apply neighbor configuration updates but has not yet been scheduled. User action is required to schedule the reboot before neighbor changes will take effect.

    Hovering over the Config/FSM State value displays additional details in an info tooltip.

    <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%2FSKHyq6cSffMM1gmfU5bm%2Fimage.png?alt=media&amp;token=357e9818-79c4-4551-8688-7716ecaa2447" alt="" width="428"><figcaption></figcaption></figure></div>

    This information is intended for troubleshooting and includes:

    * **Last Session Start Time** – Start timestamp of the most recent TR069 session (displayed in local time).
    * **Last Session End Time** – End timestamp of the most recent TR069 session (displayed in local time).
    * **Portal Config Time** – Timestamp when the configuration was last updated in the Onyx Portal (displayed in local time).
    * **AP Config Receive Time** – Timestamp when the AP last received and acknowledged a configuration update from the Onyx Portal (displayed in local time).
    * **Last Neighbor Update Time** — Timestamp of the last neighbor configuration update pushed to the AP. Displays **Already in Sync** if no update is pending.
    * **Last Reboot Sent Time** — Timestamp of the last reboot command sent to the AP from the Onyx Portal. Displays **Already in Sync** if no reboot has been triggered for a pending update.
    * **Last Boot Time** — Timestamp of the AP's last boot. Displays **--** (double dashes) if unavailable.
    * **FSM State** – The internal Finite State Machine (FSM) state of the AP, reflecting its current operational phase (e.g., *Waiting for an Inform with eNB post error state*). Intended for advanced troubleshooting.
    * **CBSD Details** – (CBSD-AP Only) For each Citizens Broadband Radio Service Device (CBSD) associated with the AP:
      * **Last Session End Time** – End timestamp of the most recent TR069 session (displayed in local time).
      * **Portal Config Time** – Timestamp when the CBSD configuration was last updated in the Onyx Portal.
      * **AP Config Rcv Time** – Timestamp when the AP last received the CBSD configuration update (displayed in local time).

        If any debug information is unavailable, the system displays -- (double dashes) in place of value.
      * **CBSD Serial Number** — The serial number identifying this specific CBSD.
  * **Reboot Schedule for Neighbor Update** – Indicates the AP's current reboot scheduling status for applying neighbor configuration updates. This parameter provides operators with clear visibility into which APs are waiting on a reboot to apply neighbor changes. Displays one of the following values:
    * **Neighbor Config in Sync** – No reboot is pending; the AP's neighbor configuration is already up to date.
    * **Auto Reboot Set** – The network is configured to automatically reboot APs when neighbor updates are pending.
    * **No Scheduled Time** – A reboot is required to apply neighbor changes, but no reboot time has been scheduled. User action is required to schedule the reboot.
    * A specific timestamp indicating when the reboot is scheduled to occur.
    * **Stuck** — The AP's configuration update is stuck and the reboot schedule status cannot be determined.
  * **GPS Latitude** – The AP equipment's GPS latitude coordinate.
  * **GPS Longitude** – The AP equipment's GPS longitude coordinate.
* SAS Status – (Displayed only if SAS is enabled.) Indicates the AP's Spectrum Access System (SAS) status—Registered, Granted, or Authorized.

  To view the grant state, hover your cursor over the "SAS Status" icon.

  * SC mode – Displays grant state of the only cell.
  * CA mode – Displays grant states of the Primary and Secondary Cells.
  * DC mode – Displays grant states of Cell 1 and Cell 2.

  Color coding for "SAS Status" icons:

  * Registered icon:
    * Green – All CBSDs are registered.
    * Amber – Some CBSDs are registered, and some are not registered.
    * Red – No CBSDs are registered.
  * Granted icon:
    * Green – Required number of grants are available.
    * Amber – Some grants are available but not the required number.
    * Red – No grants are available.
    * Grey – No CBSDs are registered.
  * Authorized icon:
    * Green – Required number of grants are authorized.
    * Amber – Some grants are authorized but not the required number.
    * Red – No grants are authorized.
    * Grey – No grants are available.
* **RAN**:

  <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%2Fk2CJSKZymsYbdxCk3zKT%2Fimage.png?alt=media&amp;token=3465acf2-30ad-45bc-b53d-8187935356b3" alt=""><figcaption></figcaption></figure></div>

  * **SAS** – Indicates whether SAS is used for frequency allocation—Enabled or Disabled.
  * **TAC** – The Tracking Area Code (TAC). The TAC is a unique code assigned to a geographical area to track mobile devices within the network.
  * **DAS** – Indicates whether the AP is associated with a DAS.
  * **Carrier Mode** – The AP's carrier mode—Single Carrier, Dual Carrier, or Carrier Aggregation.
  * **Sync Mode** — The AP's time reference synchronization mode — Free Running, GPS, or PTP. Synchronization helps adjacent APs avoid interfering with each other, optimizes bandwidth usage, and enhances network capacity.

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> In this release, the PTP sync mode is qualified only for PTP over Ethernet in Single Carrier mode. The PTP over UDP, and DC and CA modes will be qualified in a later release.</p></div>
  * **PCI** – The Physical Cell ID (PCI) used for cell identity during the cell selection procedure. The PCI is used by UE to decode physical layer data transmitted by the AP.\
    In CA mode, it is displayed for Primary and Secondary Cells.\
    In DC mode, it is displayed for Cell 1 and Cell 2.
  * **Cell ID** – The cell's unique ID.\
    In CA mode, it is displayed for Primary and Secondary Cells.\
    In DC mode, it is displayed for Cell 1 and Cell 2.
  * **Radio Range (SSF)** – (Displayed only if configured at the venue level or inherited from the network level.) The Radio Range parameter, also referred to as Signal Strength Floor (SSF). SSF determines the signal strength thresholds for different coverage areas within a network, ensuring optimal connectivity and handover performance across varying distances and terrain conditions.
    * **Normal (SSF7)** – This SSF category represents the typical signal strength threshold for cell selection and handover within a network. It is used for areas where the network coverage is considered standard, and the signal strength is within the normal operating range.
    * **> 6miles (SSF5)** – This SSF category represents an extended coverage area where the signal strength may be weaker compared to the normal operating range. It is used for areas where the distance between the cell site and the UE exceeds six miles, requiring a lower signal strength threshold for cell selection and handover.
  * **DL/UL Distribution (SA)** – (Displayed only if configured at the venue level or inherited from the network level.) The DL/UL Subframe Assignment (SA). SA determines the percentage of transmission resources in downlink and uplink.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> In CA mode, the Cell ID, PCI, Bandwidth, Frequency, Max Tx Power, and Transmit parameters are displayed for the Primary and Secondary cells. In DC mode, it is displayed for Cell 1 and Cell 2. </p></div>

  * **SAS Configuration** – (Displayed only if SAS is enabled.)

    <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%2FDBbnrv23A2TFXCvF2H7S%2Fimage.png?alt=media&amp;token=a6884814-79aa-4aa8-99ed-2437f8e9369a" alt=""><figcaption></figcaption></figure></div>

    * **CBSD Category** – (Displayed only if SAS is enabled.) The CBSD's power class under CBRS regulations—Category A (devices that operate at maximum 30 dBm EIRP), Category B (devices that operate at maximum 47 dBm EIRP).
    * **User ID** – (Displayed only if SAS is enabled.) The SAS account's user ID for SAS registration and authentication.
    * **Desired State** – (Displayed only if SAS is enabled.) The desired state—Registered, Unregistered. If SAS is enabled, the CBSD's desired state is Registered, it will search for grants, and if available, acquire them. If SAS is disabled, the state is Unregistered.
    * **Antenna Gain (dBi)** – The amount of signal boost provided by the CBSD's antenna, measured in "decibels relative to an isotropic antenna" (dBi), measured in dBi. A higher gain focuses energy more effectively but may have stricter deployment requirements.
    * **No. of Antenna** – The number of physical antennas associated with the CBSD.
    * **Preferred Min Pwr (dBm)** – The minimum transmit power level that the CBSD prefers to use.
    * **Preferred Max Pwr (dBm)** – The maximum transmit power level that the CBSD prefers to use.
    * **Preferred BW (MHz)** – The channel width that the CBSD requests.
    * **Preferred Frequencies (MHz)** – The frequencies that the device prefers to operate on in the CBRS band in MHz.\
      In CA mode, it is displayed for Primary and Secondary Cells.\
      In DC mode, it is displayed for Cell 1 and Cell 2.
    * **Strict Freq Preference** – If set to true, the CBSD strongly prefers the listed frequency and may reject alternate frequencies offered by the SAS.
    * **Transmit** – The CBSD's transmission status—Enabled or Disabled.\
      In CA mode, it is displayed for Primary and Secondary Cells.\
      In DC mode, it is displayed for Cell 1 and Cell 2.
  * **SAS Status**

    <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%2FjkLxLaHpSUU5DL3DIywH%2Fimage.png?alt=media&amp;token=49f38fea-5dda-468e-8357-587edc7fd25a" alt=""><figcaption></figcaption></figure></div>

    * **BW (MHz)** – The actual bandwidth the SAS has granted or is in the process of granting to the CBSD.
    * **Freq (MHz)** – The specific frequency center or range that the SAS has granted to the CBSD or is considering.
    * **Max Tx Pwr (dBm)** – The maximum transmit power level that the SAS allows the CBSD to use on the granted frequency.
    * **AP to DP Connection** – Indicates whether the CBSD is connected to the Domain Proxy (DP), which acts as an intermediary between multiple CBSDs and SAS.
    * **FCC ID** – (Displayed only if SAS is enabled.) The AP's Federal Communications Commission (FCC) ID, which indicates the CBSD complies with FCC regulations for operation in the CBRS spectrum.
    * **Heartbeat Interval** — The interval, in seconds, at which the CBSD sends heartbeat messages to the SAS to maintain its grant.
    * **Grant Expire Time** — The timestamp at which the current SAS grant expires. After this time, the CBSD must re-request a grant from the SAS to continue transmitting.
    * **Transmit Expire Time** — The timestamp by which the CBSD must send a heartbeat to the SAS to maintain authorization to transmit. If the heartbeat is not sent before this time, the CBSD must stop transmitting.
    * **View Available Spectrum** — Click to view display of the available frequency ranges between 3550 MHz and 3700 MHz, as reported by the SAS following Spectrum Inquiry. This information is available only after the CBSD is registered.

      <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%2FhM3xYuK1204tZfQcC3xe%2Fimage.png?alt=media&amp;token=0b11dab7-248b-4a62-9372-68a617d5cb15" alt=""><figcaption></figcaption></figure></div>
* **Subscribers (n)** – The count and list of subscribers attached to the AP.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> For non-GXC Administrator users this list excludes MeshBackhaul subscriber data.</p></div>

  For APs in DC mode, you can choose to view all subscribers or only subscribers attached to a particular cell—select "**Cell&#x20;*****\<cell\_id>*****&#x20;Subscribers**" from the dropdown.<br>

  <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%2FmVw0Echo21vu6PNo0Uzn%2Fimage.png?alt=media&amp;token=633cb1e5-fef3-4716-b48f-75c68518323a" alt=""><figcaption></figcaption></figure></div>

  \
  Also, in the Onyx Edge's details, you can view the specific cells that individual subscribers are attached to (Onyx Portal > **Subscribers** > list of subscribers > **Access Point Cell ID** column).

  * **Status** – The subscriber's service state—Active or Inactive.
  * **Name** – The subscriber account's name.
  * **IMSI** – The subscriber's IMSI number.
  * **Subscriber Group Name** – The subscriber group to which the subscriber belongs.
    {% endstep %}

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

<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%2F3sqAkrSwOlrD9okCSlzC%2Fimage.png?alt=media&amp;token=4963ef38-d9c4-41d9-9d6a-fd620012f433" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
**NOTE:** For detailed information on 4G Handovers and configuring and managing neighbor relations for handovers refer to the *4G Onyx Handovers Application Note*.
{% endhint %}

* **Handover**
  * **Neighbor Management —** Indicates whether the Onyx Edge automatically manages neighbor relationships for this AP—**Enabled** or **Disabled**. When enabled, the Onyx Edge automatically populates and maintains this AP's "Neighbor Frequency Table" and "Neighbor Cell Table" based on the other cells associated with it.
  * **Hysteresis —** A buffer value (in dB) that prevents handover flapping due to small signal fluctuations. The neighbor cell's signal must exceed the serving cell's signal by this margin for the handover to be triggered. This prevents oscillating handovers caused by minor signal variations.
  * **Time To Trigger —** The time duration (in milliseconds) that a qualifying signal condition must persist before a handover is initiated. This prevents unnecessary handovers due to temporary signal variations or momentary interference.
  * Measurement Event Thresholds:
    * **A1 RSRP —** The RSRP threshold above which the serving cell's signal is considered acceptable. When this threshold is met, the UE is instructed to stop measuring neighbor cells. This optimizes battery life by stopping unnecessary measurements when signal is strong.\
      Conversion: Portal value 60 = -80 dBm (Portal value = dBm + 140)
    * **A2 RSRP —** The RSRP threshold below which the serving cell's signal quality is considered poor. When this threshold is met, the UE is instructed to start measuring neighbor cells in preparation for a potential handover.\
      Conversio&#x6E;**:** Portal value 55 = -85 dBm
    * **A5 RSRP Serving Cell —** The serving cell's signal strength must fall below this threshold to qualify for handover evaluation. Ensures handovers only occur when serving cell signal is genuinely weak. Part of the dual-condition A5 event logic.\
      Conversion: Portal value 50 = -90 dBm
    * **A5 RSRP Neighbor Cell —** The neighboring cell's signal strength must exceed this threshold to be considered a valid handover target. This prevents handovers to cells with insufficient signal quality. Part of the dual-condition A5 event logic.\
      Conversion: Portal value 52 = -88 dBm
    * **A3 Offset —** The signal strength margin (in dB) by which the neighbor cell's RSRP must exceed the serving cell's RSRP to trigger a handover. This offset helps prevent unnecessary handovers due to minor signal fluctuations. Unlike A1, A2, and A5 thresholds, this is a relative value (dB offset), not an absolute power level (dBm).
* **Neighbors —** Displays the list of configured neighbor cells for this AP:
  * **Serial No** - Sequential number of the neighbor in the list.
  * **Freq (MHz)** - The neighbor cell's frequency in MHz (e.g., 3660, 3600).
  * **EARFCN** - E-UTRA Absolute Radio Frequency Channel Number - the channel number used in LTE to identify the carrier frequency (e.g., 56340, 55740).
  * **PCI** - Physical Cell ID - used for cell identity during cell selection procedure (e.g., 4, 6).
  * **Cell ID** - The neighbor cell's unique identifier (e.g., 769, 1025).
  * **PLMN-TAC** - Public Land Mobile Network - Tracking Area Code (e.g., 315010-1).
  * **Q Offset Cell** - Cell-specific offset used in handover and reselection decisions (e.g., 24).
  * **CIO** - Cell Individual Offset - Additional offset applied to this specific neighbor cell relationship (e.g., 24).
    {% endstep %}

{% step %}
Click the **Events & Alerts** tab.

<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%2Fk9vGVxL34RmQsEuqWNKc%2Fimage.png?alt=media&amp;token=3e4fa1b0-6ea0-4d48-bf2e-7db4b7db96f9" alt=""><figcaption></figcaption></figure></div>

* **Alerts** – Details of AP and SAS-related alerts based on the selected severity level. You can select the alert severity level from **All**, **Major**, **Minor**, **Critical**, or **Others**.<br>

  <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%2FaKSNdLYEoTj8n9NKEeKX%2Fimage.png?alt=media&amp;token=751266a2-4fdf-4e38-9431-c85d5b227739" alt="" width="375"><figcaption></figcaption></figure></div>

  * **Date** – The alert's creation timestamp.
  * **Status** – The alert's status.
  * **Alert Name** – The alert's name.
  * **Severity** – The alert's severity level.
* **Events** – Details of AP and SAS related events for the selected duration:
  * **Timestamp** – The timestamp at which the event occurred.
  * **Module** – The specific module or source from which the event originated. To filter events based on module, click the **Module** column header and select one or more modules.
  * **Event Type** – The event's type. To filter the events based on the event type, click the **Event Type** header and select one or more event types.
  * **Event Description** – The event's description.
  * To view the details of a particular event, click the corresponding <img src="https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FK3DABEHTuVJgUAmTFKIs%2Fimage.png?alt=media&amp;token=0d5004f8-49c0-42ff-b5b5-3b94a7787bc7" alt="" data-size="original"> (view details) icon.
    {% endstep %}

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

<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%2FJeN6kZc3JlHGZOLhBE3U%2Fimage.png?alt=media&amp;token=7b8f6f46-3e93-478e-839f-7005d87e4b4c" alt="" width="563"><figcaption></figcaption></figure></div>

* **Logs** – The total number and list of log events for the AP in the selected duration.
  * **Timestamp** – The timestamp at which the log was generated.
  * **Severity** – The severity of the log message.
  * **Message** – The actual information logged by the system.\
    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%2FdAELcnvPLE5CgdTQNqLS%2Fimage.png?alt=media&amp;token=d1e74d1f-51e1-438c-84b8-dfc30feed2b8" 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%2Fr9FpIy194lB6iHZgKceH%2Fimage.png?alt=media&amp;token=4d92cb24-408d-4ddd-97c1-b8848e1d6f94" 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%2F8P0Pdmczs72k5siljbSJ%2Fimage.png?alt=media&amp;token=3c6bcf82-ddde-4bc9-ae99-eef2e269204c" 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>
* **DP Logs (n)** – The total number and list of Domain Proxy (DP) log events between the selected entities—**DP**, **ACS**, **CBSD**, and **SAS**.

  To change the selected entities, click the corresponding dropdown.<br>

  <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%2FCXzMAW6O6Fg5ygxj6y6C%2Fimage.png?alt=media&amp;token=f40ac959-e6a6-4406-8613-ec51a3d3d5bd" alt="" width="282"><figcaption></figcaption></figure></div>

  For 4G APs operating in SAS Dual Carrier Mode, the DP Logs section includes cell-specific filtering, enabling you to isolate and analyze First Cell or Second Cell traffic for targeted troubleshooting and improved dual carrier network visibility.

  <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%2FdXZXM3OMvKbEbBnVrca8%2Fimage.png?alt=media&amp;token=02d726af-935a-43e4-a4de-86143a0be6a4" alt="" width="563"><figcaption></figcaption></figure></div>

  First Cell: Filter using the AP's serial number (e.g., ABX123).

  Second Cell: Filter using the AP's serial number with "-2" suffix (e.g., ABX123-2).

  The list of DP log events between the selected entities.

  * **Timestamp** – The timestamp at which the log was generated.
  * **From** – The source or origin of the data.
  * **To** – The destination or target of the data.
  * **Type** – The type of the log entry.
  * **Message** – The actual information logged by the system.
  * **Download** – (Available only if IPSec is enabled for the AP.) To download the AP Certificate and AP Private Key, in the upper-right corner of the page, click **Download**.

    On enabling IPSec for an AP, these AP Certificate and AP Private Key files, and the network's Root CA Certificate file must be uploaded to the AP equipment's configuration interface. For more information see [*Enable and Configure IPSec on AP Equipment*](#enable-and-configure-ipsec-on-ap-equipment).
  * **Actions** (**Actions** button in the upper-right corner of the page):
    * **Delete** – (Super Administrator and Administrators only.) To delete the AP. For more information, see *Delete APs*.
    * **Reboot** – (Super Administrator and Administrators only.) To reboot the AP. For more information, see *Reboot APs*.
    * **Upgrade** – (Super Administrator and Administrators only.) To upgrade the AP software running on the APs. For more information, see [*Manage AP Software Upgrades*](#manage-ap-software-upgrades).
      {% endstep %}
      {% endstepper %}

## Add APs

This section describes how to add APs.

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

**To add an AP to a 4G network:**

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

The **Equipment** page > **Access Points** tab displays the summary details of all APs configured in the network.
{% endstep %}

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

The **Create Access Point** page > **Access Point** 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%2FbBn1k2gwKe7ailIs51Ts%2Fimage.png?alt=media&amp;token=5268f047-fcf5-439a-b61b-b2a3f4685d2c" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Enter the following details:

* **Venue** – (Required) Select the venue hosting the AP.
* **Name** – (Required) The AP's name.
* **Serial Number** – (Required) The AP equipment's vendor-assigned serial number.
* **Description** – (Required) The AP's description.
  {% endstep %}

{% step %}
In the lower-right corner of the page, click **Configure RAN**.

The **RAN** 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%2F2PwkBjAV91bOeCpe0AZn%2Fimage.png?alt=media&amp;token=ab3b96d0-cc6f-49fd-8875-c9a01d710700" alt=""><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Enter the following details:

* **Device Class** – (Required) Select the AP equipment's model from the following:

  * **G100** – Indoor Low Power AP
  * **G101** – Outdoor Low Power AP
  * **G501** – Outdoor High Power AP

  For detailed information on these 4G APs, refer to the corresponding Specification Sheets and Hardware Installation Guides.
* **TAC** – (Optional) The Tracking Area Code used for UE mobility handling within this AP's service area. Default value: 55.
* **Carrier Mode** – (Required) Select the carrier mode from **Single Carrier**, **Dual Carrier**, **Carrier Aggregation**. Default value: Single Carrier.

  If you select **Carrier Aggregation**, you must configure the Bandwidth, Frequency, Max Tx Power, and Transmit parameters for the Primary and Secondary Cells.

  If you select **Dual Carrier**, you must configure the Bandwidth, Frequency, Max Tx Power, and Transmit parameters for Cell 1 and Cell 2.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> For CA mode, the APs must be updated with the "FAP009 Carrier Aggregation Function" license.</p></div>

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> For CA mode, the UE must also support CA.</p></div>

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> DC handovers are not supported in this release.</p></div>

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> For DC mode, the APs must be updated with the "FAP010 Dual Carrier Function" license.</p></div>

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> The CA and DC modes are not supported with Mesh APs. This is because the CA and DC modes require four antenna ports (4 filters), while the GM01 Mesh Node supports two. However, the Gateway AP serving a Mesh Node can be operated in CA or DC modes.</p></div>
* **Sync Mode** – (Required) Select the AP's time reference synchronization mode. Synchronization helps adjacent APs avoid interfering with each other, optimizes bandwidth usage, and enhances network capacity. Default value: Free Running.
  * **Free Running** – The AP synchronizes to its own internal clock set by an NTP server.
  * **GPS** – The AP synchronizes time using a directly-connected GPS antenna.
  * **PTP** – The AP synchronizes time with a local PTP server.
    * **PTP Transport** – (Displayed only when the PTP sync mode is selected. Required.) Select the Precision Time Protocol (PTP) transport protocol—**Ethernet**, **UDP**. Default value: Ethernet.

      <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> In this release, the PTP sync mode is qualified only for PTP over Ethernet in Single Carrier mode. The PTP over UDP, and DC and CA modes will be qualified in a later release.</p></div>
* **Operation Mode** – (Required) Select the AP's operation mode:
  * **Manual** – Select to disable SAS. The AP uses user-defined radio parameters such as frequency, bandwidth, and power without relying on SAS automation.
  * **SAS** – Select to enable SAS. The AP operates under the SAS, automatically receiving CBRS channel assignments and power limits based on SAS grants.
  * **DAS** – The AP operates as part of a DAS where RF parameters are centrally controlled, and the AP functions as a remote radio head rather than an independently managed radio node.
* **IPSec** – Enable or disable IPSec. Default setting: disabled.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> IPSec must be enabled only on APs that are directly connected to IPSec-enabled Onyx Edge. IPSec must not be enabled for APs behind Mesh Nodes.</p></div>

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> If enabled here, IPSec must also be enabled and configured on the AP equipment. For more information, see <a href="#enable-and-configure-ipsec-on-ap-equipment"><em>Enable and Configure IPSec on AP Equipment</em></a>.</p></div>

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> IPSec is not supported in conjunction with HA/Onyx Edge pools. IPSec-enabled APs must not be associated with an Onyx Edge pool. IPSec must not be enabled on APs already associated with a pool. For more information, see <em>Manage Onyx Edge High Availability</em>.</p></div>

In SC mode with SAS enabled.

<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%2FHZIUMBioXaew4mimN8uZ%2Fimage.png?alt=media&amp;token=446c1907-6a3d-4d4d-9e90-3fc3bd615695" alt=""><figcaption></figcaption></figure></div>

In DC mode with SAS enabled.

<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%2FDG0gwzpiVTr9rHzAm1OY%2Fimage.png?alt=media&amp;token=5d658d90-d44a-4328-8480-43e83569e1c5" alt=""><figcaption></figcaption></figure></div>

In CA mode with SAS enabled.

<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%2FKWYHGzudhTORxZTUJ9aO%2Fimage.png?alt=media&amp;token=d3ed960d-72b4-4faa-8fc1-9439b986441f" alt=""><figcaption></figcaption></figure></div>

* **CBSD Category** – (Displayed only if SAS is enabled. Required.) The Citizens Broadband Radio Service Device (CBSD) category. Select either **A** or **B**. Category A devices operate at a maximum of 30 dBm EIRP, while Category B devices operate at a maximum of 47 dBm EIRP.
  * G100 – (Cannot be changed.) A.
  * G101 – A or B. Default value: B.
  * G501 – A or B. Default value: B.
* **User ID** – (Displayed only if SAS is enabled. Required.) The SAS account's user ID.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> To obtain the SAS user ID, contact GXC Technical Support.</p></div>
* **Antenna Gain (dBi)** – (Displayed only if SAS is enabled. Required.) The antenna's gain in dBi.
  * G100 – (Cannot be changed.) Default value: 4.
  * G101 – Must be in the range of -5–30. Default value: 13.
  * G501 – Must be in the range of -5–30. Default value: 0.

    In DC mode, configure this parameter for Cell 1 and Cell 2.
* **Preferred Max Pwr (dBm)** – (Displayed only if SAS is enabled. Required.) The preferred maximum power in dBm.
  * G100 – Must be in the range of 0–24. Default value: 24.
  * G101 – Must be in the range of 0–24. Default value: 24.
  * G501 – Must be in the range of 0–30. Default value: 30.

    In DC mode, configure this parameter for Cell 1 and Cell 2.
* **Preferred BW (MHz)** – (Displayed only if SAS is enabled. Required.) Select the preferred bandwidth value in MHz.
  * G100 – Must be 10 or 20. Default value: 10.
  * G101 – Must be 10 or 20. Default value: 10.
  * G501 – Must be 10 or 20. Default value: 10.

    In DC mode, configure this parameter for Cell 1 and Cell 2.
* **Preferred Frequencies (MHz) in Priority Order** – (Displayed only if SAS is enabled. Required.) Select the preferred frequency values (multiple) in priority order, that is, highest priority first, followed by the second priority, and so on. Available values depend on **Preferred BW (MHz)** and are in increments of five.
  * G100 – For 10MHz Preferred Bandwidth = 3555–3695. For 20MHz Preferred Bandwidth = 3560–3690. Default setting: 3680.
  * G101 – For 10MHz Preferred Bandwidth = 3555–3695. For 20MHz Preferred Bandwidth = 3560–3690. Default setting: 3680.
  * G501 – For 10MHz Preferred Bandwidth = 3555–3695. For 20MHz Preferred Bandwidth = 3560–3690. Default setting: 3680.

    In DC mode, configure this parameter for Cell 1 and Cell 2.

{% hint style="info" %}
**NOTE:** For a Mesh Node, you must enter a preferred frequency. Do not use the default **Auto** value. If the Gateway AP is assigned a channel in the high frequency portion of the CBRS band, then the Mesh AP must be configured for a channel in the low frequency portion of the CBRS band and vice versa. For more information, see *GM01 Mesh Node Installation and Configuration Guide > Mesh Filters and Channel Frequency Assignments*.
{% endhint %}

* **Strict Preference** – (Displayed only if SAS is enabled. Optional.) Select **True** to enable and **False** to disable the Strict Frequency Control feature, wherein grant selection is restricted only to the preferred frequencies. Default value: True.

  When enabled, if none of the preferred frequencies are available, the DP will retry with a Spectrum Inquiry Request until one of the preferred frequencies becomes available. Until then, the CBSD will not be able to transmit. When disabled, the next best frequency will be requested for the grant.

  In DC mode, configure this parameter for Cell 1 and Cell 2.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> Strict Preference must be set to True for both the Gateway AP and Mesh AP.</p></div>
* **Transmit** – (Optional) Select to enable or disable transmission. Default setting: disabled.

  In CA mode, configure this parameter for Primary Cell and Secondary Cell.

  In DC mode, configure this parameter for Cell 1 and Cell 2.

Manual in SC mode.

<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%2FKhL7SzoaMtaESYqnSjWB%2Fimage.png?alt=media&amp;token=e672aafd-7137-4497-84a1-43f8f9834331" alt=""><figcaption></figcaption></figure></div>

Manual in DC mode.

<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%2FN3MDUsJCpuEmW3vl7ama%2Fimage.png?alt=media&amp;token=aedaec4d-7560-4258-8ec5-929d9bdb5bfd" alt=""><figcaption></figcaption></figure></div>

Manual in CA mode.

<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%2FS3NzpPKw1aoFXxB5MNkx%2Fimage.png?alt=media&amp;token=adceae3b-433b-464f-84b9-75ae4d5e394b" alt=""><figcaption></figcaption></figure></div>

* **BW (MHz)** – (Required) Select the bandwidth value in MHz. Default value: 10.

  In CA mode, configure this parameter for the primary and secondary cells.

  In DC mode, configure this parameter for Cell 1 and Cell 2.
* **Freq (MHz)** – (Required) Select the frequency value in MHz. Default value: 3555.

  In CA mode, configure this parameter for the primary and secondary cells.

  In DC mode, configure this parameter for Cell 1 and Cell 2.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>NOTE:</strong> Ensure that the Mesh AP and the Gateway AP are not assigned the same frequency. If the Gateway AP is assigned a channel in the high-frequency portion of the CBRS band, the Mesh AP must be assigned a channel in the low-frequency portion, and vice versa. For more information, see <em>GM01 Mesh Node Installation and Configuration Guide > Mesh Filters and Channel Frequency Assignments</em>.</p></div>
* **Max Tx Pwr (dBm)** – (Required) The maximum transmission power in dBm.

  * G100: Must be in the range of 17–24. Default value: 24.
  * G101: Must be in the range of 17–24. Default value: 24.
  * G501: Must be in the range of 24–30. Default value: 30.

  In CA mode, configure this parameter for the primary and secondary cells.

  In DC mode, configure this parameter for Cell 1 and Cell 2.
* **Transmit** – (Required) Select to enable or disable transmission. Default setting: disabled.

  In DC mode, configure this parameter for Cell 1 and Cell 2.
  {% endstep %}

{% step %}
In the lower-right corner of the page, click **Configure Handover**.

The **Handover** 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%2FnT6Ladz4TduBf9osRXlV%2Fimage.png?alt=media&amp;token=7091b85a-0fea-4f59-8726-84aa0afd78df" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
**NOTE:** For detailed information on configuring and managing neighbor relations for handovers refer to the *4G Onyx Handovers Application Note*.
{% endhint %}
{% endstep %}

{% step %}
To save the AP, in the upper-right corner of the page, click **Save Access Point**.

{% hint style="info" %}
**NOTE:** In non-HA mode, after adding the AP, to activate it, you must associate it with an Onyx Edge. To associate an AP with an Onyx Edge, click **Equipment** > **Onyx Edge** tab > edit Onyx Edge > **RAN** tab > **Associated Access Point** parameter.

To check the APs associated with an Onyx Edge, click **Equipment** > **Onyx Edge** tab > view Onyx Edge details > **Connected Access Point** section.
{% endhint %}

{% hint style="info" %}
**NOTE:** For information on associating an AP with an Onyx Edge in HA/Onyx Edge Pool mode, see *Manage Onyx Edge High Availability*.
{% endhint %}

These steps must be repeated for each AP that you add to the system. Depending on your network traffic and internet connection, it may take up to 10 minutes or more for an AP to check-in with the Onyx Portal.
{% endstep %}
{% endstepper %}

### Enable and Configure IPSec on AP Equipment

{% hint style="info" %}
**NOTE:** In this release, IPSec is supported only in 4G networks.
{% endhint %}

{% hint style="info" %}
**NOTE:** This section is applicable only if you are enabling IPSec between an AP and the associated Onyx Edge. For more information, see *IPSec Support*.
{% endhint %}

{% hint style="info" %}
**NOTE:** IPSec is not supported in conjunction with HA/Onyx Edge pools. IPSec-enabled APs must not be associated with an Onyx Edge pool. IPSec must not be enabled on APs already associated with a pool. For more information, see *Manage Onyx Edge High Availability*.
{% endhint %}

After you enable IPSec support for an AP in the Onyx Portal, you must download the Root CA Certificate, AP Certificate, and AP Private Key files from the Onyx Portal and upload them to the AP's configuration interface. You must then enable and configure IPSec in the AP's configuration interface.

{% hint style="info" %}
**NOTE:** The "IPSec Equipment" and "IPSec Private" certificates have one-year validity periods. Upon expiration, they must be downloaded again and uploaded to the AP LCI interface.
{% endhint %}

#### Download Certificate Files from the Onyx Portal

**To download the certificate files from the Onyx Portal:**

{% stepper %}
{% step %}
Download the network's Root CA Certificate file:

1. In the navigation pane, click **Network**.

   The ***\<network name>*** page is displayed.
2. In the upper-right corner of the page, click **Download Root CA Certificate**.

   The .pem file is downloaded.
   {% endstep %}

{% step %}
Download the AP Certificate and AP Private Key files:

1. In the navigation pane, click **Equipment** > **Access Points** tab.

   The list of available APs is displayed.
2. Click the name of the AP for which you want to download the certificate files.

   The ***\<AP name>*** page is displayed.
3. In the upper-right corner of the page, click **Download** > **Download AP Certificate**.

   The .pem file is downloaded.
4. In the upper-right corner of the page, click **Download** > **Download AP Private Key**.

   The .key file is downloaded.
   {% endstep %}
   {% endstepper %}

#### **Upload Certificate Files to the AP**

**To upload the certificate files to the AP:**

{% stepper %}
{% step %}
Log on to the AP equipment's LCI.
{% endstep %}

{% step %}
In the AP's LCI navigation menu, click **Network** > **IPSec**.

The **Network/IPSec** page is displayed.
{% endstep %}

{% step %}
In the **IPSec Tunnel List** section, edit the first index and enable IPSec.
{% endstep %}

{% step %}
In the **IPSec Certs** section, in the **Type** drop-down, select each of the certificate types **IPSec CA Certs**, **IPSec Equipment Certs**, and **IPSec Private Certs**, and upload the corresponding files.

The updates are listed in the **Certificate List** section.

<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%2Fy02xeytalobrbqvqkJTP%2Fimage.png?alt=media&amp;token=1791ebd2-97fb-4258-b34f-fe9de37bd912" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Click **Save** to exit.
{% endstep %}
{% endstepper %}

### Enable and Configure IPSec in the AP's LCI

**To enable and configure IPSec in the AP's configuration interface:**

{% stepper %}
{% step %}
Log on to the AP equipment's LCI.
{% endstep %}

{% step %}
In the AP's LCI navigation pane, click **Network** > **IPSec**.

The **Network/IPSec** page is displayed.
{% endstep %}

{% step %}
In the **IPSec-Tunnel-List** section, edit the first index.

Click the corresponding edit icon, and then enter the following values:

* **Left-Auth** – (Optional) PUBKEY.
* **Right-Auth** – (Optional) PUBKEY.
* **Gateway** – (Required) The outer IP address of the MME.

  For Onyx Edge On-Premises deployments, this is typically 10.0.2.1.
* **Right Subnet** – (Required) This must match the MME Local IP address configured on the Onyx Edge (Onyx Portal > **Equipment** > **Onyx Edge** tab > view Onyx Edge's details > **RAN** tab > **AGW IPSec Configuration** > **MME Local IP** parameter).
* **Right Id** – (Optional) “CN=*\<onyx-edge-uuid>*”.

  For example, "CN=ad72fe38-062c-4c51-ae20-4c59c9cc4a0f".
* **Secret key** – (Optional) Name of the AP key file.

  For example, "*enb\_key.pem*".
  {% endstep %}

{% step %}
In the **Advanced Setting** section, enter the following values:

* **Left Id** – The AP's serial. You can obtain this from the *enb\_cert.pem* file by running the following command:

{% code overflow="wrap" %}

```
$ openssl x509 -in enb_cert.pem -noout -text | grep 'Subject:'
        Subject: C = US, O = Gxc, OU = GxcEnodeb, CN = 1202000468222AB0008
```

{% endcode %}

* **Left Cert** – Name of the enb-cert file.

  For example, "*enb\_cert.pem*".
* Keep the second index switched off.
  {% endstep %}

{% step %}
In the AP’s LCI navigation pane, click **Network** > **Core Network**.
{% endstep %}

{% step %}
In the **MME Pool Config** section, add the MME IP address.
{% endstep %}

{% step %}
On saving your edits, you will be required to reboot the AP.   &#x20;

After rebooting, IPSec will be enabled.
{% endstep %}
{% endstepper %}

## Edit APs

This section describes how to edit APs in 4G networks.

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

{% hint style="info" %}
**NOTE:** The carrier mode of an AP cannot be changed as long as any of its cells are part of the "Allowed Cell" configuration for any subscriber. The subscriber's configuration must first be cleared of the allowed cell configuration, after which the AP's carrier mode can be changed.
{% endhint %}

**To edit an AP's details:**

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

The **Equipment** page > **Access Points** tab displays the summary details of all APs configured in the network.
{% endstep %}

{% step %}
For the 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%2FGqTV5ejeLgHB4lfMCb4y%2Fimage.png?alt=media&amp;token=0efa7453-fb32-42f6-bd0c-b4acc8dd850c" alt="" width="110"><figcaption></figcaption></figure></div>

The **Edit Access Point** page displays the equipment's details.
{% endstep %}

{% step %}
Edit the AP's details as required.

For parameter descriptions, see [*Add APs*](#add-aps).
{% endstep %}

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

## Reboot APs

{% hint style="info" %}
**NOTE:** You can reboot APs only if you are a Super Administrator or an Administrator.
{% endhint %}

{% hint style="info" %}
**NOTE:** When you reboot an AP, it will temporarily deactivate any active networks and disconnect any UE that are connected to those networks.
{% endhint %}

To reboot an AP:

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

The **Equipment** page > **Access Points** tab displays the summary details of all APs configured in the network.
{% endstep %}

{% step %}
Click the name of the AP that you want to reboot.

The ***\<AP name>*** page displays the AP's details.
{% endstep %}

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

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%2Foz8y9F7VbX8d6LEJCqmx%2Fap-reboot.png?alt=media&amp;token=54049913-0fc7-4c5f-97e9-f916c7e4ce62" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

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

## Delete APs

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

{% hint style="info" %}
**NOTE:** An AP cannot be deleted as long as any of its cells are part of the "Allowed Cell" configuration for any subscriber. The subscriber's configuration must first be cleared of the allowed cell configuration, after which the AP can be deleted. For more information, see *Mesh Node-AP Affinity Feature*.
{% endhint %}

**To delete an AP:**

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

The **Equipment** page > **Access Points** tab displays the summary details of all APs configured in the network.
{% endstep %}

{% step %}
For the equipment 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%2FSYICYJbhYP9sziLyaBPW%2Fimage.png?alt=media&amp;token=1d690894-96fa-4f23-bff6-a7b52f6036bf" 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%2F3cin62OGZik4LmkTkHAx%2Fimage.png?alt=media&amp;token=457b12d1-ee99-48df-a098-603d8fd70e37" alt="" width="398"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
To confirm deleting the AP, 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/4g-onyx-portal-4.x-operations/manage-equipment/manage-access-points.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.
