Onyx Portal 5G Alerts
| Type | Module | Alert Name | Severity |
|---|---|---|---|
| Access Point | Control Plane | Neighbor Tables Incomplete | Major |
| Access Point | CU-Plane | Cell Service Down | Major |
| Access Point | CU-Plane | Insufficient SAS Power | Major |
| Access Point | CU-Plane | Multiport Cell Service Down | Major |
| Access Point | Domain Proxy | CBSD Lesser BW Granted | Major |
| Access Point | Domain Proxy | CBSD New Grant | Warning |
| Access Point | Domain Proxy | CBSD Preferred Frequency Unavailable | Warning |
| Access Point | Domain Proxy | CBSD Registration Failure | Major |
| Access Point | M-Plane | Offline | Major |
| Access Point | MCU-Plane | Cell Unwarranted Transmission | Major |
| Access Point | MCU-Plane | Mesh Filter-Frequency Mismatch | Major |
| Access Point | S-Plane | Timing Out of Sync | Major |
| FHM | C-Plane | Packet Loss Detected | Major |
| FHM | M-Plane | Offline | Major |
| Mesh Node | Domain Proxy | CPE CBSD New Grant | Warning |
| Mesh Node | Domain Proxy | CPE CBSD Preferred Frequency or Bandwidth Unavailable | Warning |
| Mesh Node | Domain Proxy | CPE CBSD Registration Failure | Major |
| Mesh Node | Management Plane | Offline | Critical |
| Mesh Node | MCU-Plane | Tunnel Down | Major |
| Mesh Node | MCU-Plane | Watchdog Powercycle | Minor |
| Mesh Node | Platform | CPU Usage | Minor |
| Mesh Node | Platform | Disk Usage | Major |
| Mesh Node | Platform | Memory Usage | Minor |
| Mesh Node | Provisioning Server | Provisioning Server Connection Failure | Warning |
| Onyx Edge (Core) | C-Plane | DHCP Server Failed | Major |
| Onyx Edge (Core) | C-Plane | NG Setup Failure | Major |
| Onyx Edge (Core) | C-Plane | SCTP Outbound Stalled | Major |
| Onyx Edge (Core) | C-Plane | UE IMSI-IMEI Validation Failure | Warning |
| Onyx Edge (Core) | C-Plane | UE Registration Failure | Warning |
| Onyx Edge (Core) | CU Plane | HA Peer Down | Major |
| Onyx Edge (Core) | M-Plane | Offline | Critical |
| Onyx Edge (Core) | MCU-Plane | Service Down | Critical |
| Onyx Edge (Core) | Platform | CPU Usage | Minor |
| Onyx Edge (Core) | Platform | Disk Usage | Major |
| Onyx Edge (Core) | Platform | Memory Usage | Minor |
| Onyx Edge (Core) | Provisioning Server | Provisioning Server Connection Failure | Warning |
| Onyx Edge (NR) | C-Plane | F1 Setup Failure | Critical |
| Onyx Edge (NR) | C-Plane | RRC Security Mode Failure | Warning |
| Onyx Edge (NR) | C-Plane | RRC Setup Failure | Warning |
| Onyx Edge (NR) | M-Plane | Offline | Critical |
| Onyx Edge (NR) | MCU-Plane | Service Down | Critical |
| Onyx Edge (NR) | Platform | CPU Usage | Minor |
| Onyx Edge (NR) | Platform | Disk Usage | Major |
| Onyx Edge (NR) | Platform | Memory Usage | Minor |
| Onyx Edge (NR) | Provisioning Server | Provisioning Server Connection Failure | Warning |
| Onyx Edge (NR) | S-Plane | GPS Signal Not Available | Major |
| Onyx Edge (NR) | S-Plane | PHC2SYS Offset Is Too High | Warning |
| Onyx Edge (NR) | S-Plane | TS2PHC Offset Is Too High | Warning |
| Onyx Edge (NR) | User Plane | Cell High DL BLER | Warning |
| Onyx Edge (NR) | User Plane | Cell High UL BLER | Warning |
| Onyx Edge (NR) | User Plane | Early eCPRI Packets | Warning |
| Onyx Edge (NR) | User Plane | Late eCPRI Packets | Warning |
| Onyx Edge (NR) | User Plane | eCPRI Rx Down | Warning |
| Orchestrator | Domain Proxy | SAS Connection Failure | Critical |
Notifications icon.)
2. Check if SAS grants are available. (Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > **Overview** tab > SAS Status.)
3. Check if PTP sync is locked in the AP status. (Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > **Overview** tab > **Access Point Details** tile > **Sync Status** icon >  green.)
4. Ensure that the ECPRI status reported by L1 (NR server) is good. (Onyx Portal > **Equipment** > **Onyx Edge (Core + NR)** tab / **Onyx Edge** tab > view Onyx Edge's details > **Overview** tab > **Onyx Edge Details** tile > **Interface Status** icon >  green.)
5. If the issue persists after completing the above steps, reboot the AP.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
#### Insufficient SAS Power
**Trigger Condition**
SAS has granted the CBSD(s) associated with this AP a maximum transmit power that is below the AP's configured hardware minimum power, and the AP has force-disabled transmission as a result.
**Probable Causes**
* SAS is unable to grant sufficient power due to spectrum congestion or interference near the deployment location.
* The AP's configured minimum power threshold does not match the actual hardware/deployment requirement.
**Clear Condition**
SAS grants a maximum transmit power at or above the AP's configured hardware minimum power.
**Severity**
Major
**System Impact**
The AP will stop transmitting.
**Indications**
See [Cell Transmission Down Indications](#cell-transmission-down-indications).
**Corrective Actions**
1. Check to see if any maintenance activity is in progress.
2. Check the SAS granted power for the CBSD(s) associated with the AP (Onyx Portal > **Equipment** > **Access Point** tab > AP details page > SAS Status Display).
3. In the AP's DP logs, check the granted power against the expected minimum (Onyx Portal > **Equipment** > **Access Point** tab > AP details page > **Logs** tab > **DP Logs** section).
4. If the granted power is consistently below the minimum, contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
**Related Alerts**
* [Access Point Cell Service Down](#cell-service-down)
* [Access Point Multiport Cell Service Down](#multiport-cell-service-down)
***
#### Multiport Cell Service Down
**Trigger Condition**
When a cell with Multiport enabled is not transmitting for at least 5 minutes.
**Probable Causes**
Grant for all Multiport antennas is unavailable or unauthorized.
**Clear Condition**
When the cell is transmitting again.
**Severity**
Major
**System Impact**
The AP will stop transmitting.
**Indications**
See [Cell Transmission Down Indications](#cell-transmission-down-indications).
**Corrective Actions**
1. Check if any scheduled maintenance activity is in progress.
2. Verify grants are available and authorized for all antennas to transmit:
* Check SAS status (Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > SAS Status display).
* Check the AP's DP logs for failures on each antenna and take required action (Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > **Logs** tab > **DP Logs** section).
* If grants are not available or not authorized, adjust the preferences to obtain grants (Onyx Portal > **Equipment** > **Access Point** tab > edit AP's details > **RAN** tab).
* If grants are still not available for the minimum acceptable preferences, transmission will not be possible until resources become available with SAS again.
3. Verify synchronization and connectivity:
* Check if PTP sync is locked in the AP's details page.
* Check if the eCPRI status reported by L1 (NR server) shows as connected.
4. If the issue persists after completing the above steps, reboot the AP.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
### Access Point Domain Proxy Alerts
#### CBSD Lesser BW Granted
**Trigger Condition**
When a CBSD has been granted less bandwidth than desired, and it continues to be in this state for at least five minutes.
**Clear Condition**
When either of the following conditions occur:
* CBSD gets the desired bandwidth in a grant.
* CBSD loses the grant.
**Severity**
Major
**System Impact**
The network capacity is reduced from what was planned.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Downlink/Uplink Traffic** tile: Traffic will reduce as bandwidth is reduced.
* Onyx Portal > **Dashboard** > **Data Usage** tile: Usage will not increase at the expected rate due to reduced bandwidth.
**Corrective Actions**
1. Check if any maintenance activity is currently in progress.
2. In the AP's DP logs, check Spectrum Inquiry Response to determine available frequencies (Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > **Logs** tab > **DP Logs** section).
3. If Strict Preference is enabled, disable it, if possible (Onyx Portal > **Equipment** > **Access Point** tab > edit AP's details > **RAN** tab > **Strict Preference** parameter), or change the frequency preference to obtain frequency with higher bandwidth (Onyx Portal > **Equipment** > **Access Point** tab > edit AP's details > **RAN** tab).
4. Contact GXC Technical Support.
**Resolution Verification**
1. All tiles have returned to their pre-incident conditions.
2. In the AP's details, verify the granted bandwidth (Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > **Overview** tab > **RAN** tile > **Bandwidth (MHz)** parameter).
**Related Alerts**
Access Point Domain Proxy [CBSD New Grant](#cbsd-new-grant) Alert — Triggered in conjunction with the Access Point Domain Proxy "CBSD Lesser BW Granted" alert.
***
#### CBSD New Grant
**Trigger Condition**
When new grants have been received within the last one hour.
**Clear Condition**
When no new grants have been received for at least one hour.
**Severity**
Warning
**System Impact**
This alert indicates a new grant has been received from SAS. For an AP that is already transmitting, it could change the transmission frequency, bandwidth, power, etc. The operator should verify the new grant will not affect the required KPIs.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Access Point** tile > **Service Status** icon — Depending on grant authorization state and previous transmission state of the AP,  green or  amber.
* Onyx Portal > **Dashboard** > **Subscribers** tile:
* If the new grant comes with a lower power level, subscribers at the edge may lose connection.
* If the AP was not previously transmitting, and the grant got authorized as well, previously unconnected subscribers in the coverage area can get connected.
* Onyx Portal > **Dashboard** > **Downlink/Uplink Traffic** tile: The traffic may change depending on AP's previous transmission state, grant authorization, and UE behavior. For example, a reduced bandwidth will not transmit as much data as before.
* Onyx Portal > **Dashboard** > **Data Usage** tile: The usage may change depending on the AP's previous transmission state, grant authorization, and UE behavior.
* Onyx Portal > **Dashboard** > **Access Point SAS Status** tile: Granted/Authorized CBSDs count may change depending on the CBSD's previous state.
* Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > **Overview** tab > **RAN** tile: SAS Status will move to Granted and generally to Authorized if no previous grants were available.
* Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > **Overview** tab > **Access Point Details** tile > **Service Status** icon: If the AP was not transmitting previously, the icon can be  green.
**Corrective Actions**
None.
**Resolution Verification**
None required for initial alert for an AP.
**Related Alerts**
Access Point Domain Proxy [CBSD Lesser BW Granted](#cbsd-lesser-bw-granted) Alert — Triggered if the new grant does not have the desired bandwidth.
**Additional Information**
* This alert simply indicates that a new grant has been received from SAS.
* As each grant change is a separate grant success, this alert can also be used to track grant changes. However, note that the very first grant is also tracked.
***
#### CBSD Preferred Frequency Unavailable
**Trigger Condition**
* In SC/DC mode, none of the frequencies in the preferred list are available with SAS.
* In CA mode, no non-overlapping frequency pair from the preferred list is available with SAS.
**Clear Condition** When any of the following conditions occur:
* Preferred frequencies become available again.
* CBSD is deregistered.
**Severity**
Warning
**System Impact**
* Network radio transmissions may not occur as planned, potentially causing interference from neighboring cells.
* This alert indicates that transmission on preferred frequencies is not fully possible. If Strict Preference is enabled, the AP will stop transmitting.
* In other cases, the AP will continue transmitting on whatever frequency is received via SAS grant.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* In case Strict Preference is disabled (Onyx Portal > **Equipment** > **Access Point** tab > view AP's details), the granted frequency would not be part of the preferred list.
* In case Strict Preference is enabled, see [Cell Transmission Down Indications](#cell-transmission-down-indications).
**Corrective Actions**
1. Change the preference list (Onyx Portal > **Equipment** > **Access Point** tab > edit AP's details > **RAN** tab).
2. The available frequency can be found in the "Spectrum Inquiry Response" log type (Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > **Logs** tab > **DP Logs** section > "Spectrum Inquiry Response" log type). Filter for "From SAS To DP logs".
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
#### CBSD Registration Failure
**Trigger Condition**
When one or more CBSD registration attempts have failed within the last one hour.
**Clear Condition**
When no CBSD registration failures occur for at least one hour.
**Severity**
Major
**System Impact**
The AP becomes non-functional, as it cannot obtain any grants to transmit.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > SAS Status: Will show Registered in red .
* See [Cell Transmission Down Indications](#cell-transmission-down-indications).
**Corrective Actions**
1. Check the AP's DP logs for the failure reason and take necessary action (Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > **Logs** tab > **DP Logs** section).
2. The most probable cause is a parameter mismatch between the Onyx Portal and the SAS Portal. Verify the CBSD registration on the Federated Wireless Portal has the correct information. Verify the FCC ID, Serial Number, CBSD Type and Category, Location, and Antenna parameters.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
### Access Point M-Plane Alerts
#### Offline
**Trigger Condition**
When no M-Plane messages have been received for the past 10 minutes (five minutes in alert condition + five minutes for changing the metric). This may occur, for example, if the AP is powered off.
**Clear Condition**
When M-Plane connection is re-established with the AP.
**Severity**
Major
**System Impact**
* Management access to the AP will be down. Configurations, alerts, events, metrics, etc. between the Onyx Portal and the AP will not be in sync.
* User traffic may be unavailable depending on the mode of failure.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Access Point** tile > **Online** icon: This AP is offline. Depending on other APs in the network,  red or  amber. Hover information shows the offline APs.
* Onyx Portal > **Dashboard** > **Access Point** tile > **Service Status** icon: Depending on other APs in the network,  grey or  amber.
* Onyx Portal > **Dashboard** > **Subscribers** tile: If the AP results in loss of online subscribers, the connected subscribers count will change.
* Onyx Portal > **Dashboard** > **Downlink/Uplink Traffic** tile: If S1 is down, the traffic will commensurately reduce.
* Onyx Portal > **Dashboard** > **Data Usage** tile: If S1 is down, the usage will commensurately reduce.
* Onyx Portal > **Dashboard** > **Access Point SAS Status** tile: For SAS-enabled APs that are not online for the last four hours:
* If unregistered, it will not get registered until it is online.
* Any grants will be relinquished, and the AP will move to Registered state.
* Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > **Overview** tab > **Access Point Details** tile > **Online** icon:  red. All other statuses will turn grey.
**Corrective Actions**
1. Check if any maintenance activity is currently in progress.
2. Check for any power outages at the equipment's location.
3. Verify the AP is associated with the correct Onyx Edge.
4. Verify network connectivity between the AP and Onyx Edge.
5. Contact a local technician for physical AP inspection.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
**Related Alerts**
Onyx Edge (Core) MCU-Plane [Service Down](#onyx-edge-core-service-down) Alert — Triggered if all APs connected to the Onyx Edge are offline.
***
### Access Point MCU-Plane Alerts
#### Cell Unwarranted Transmission
**Trigger Condition**
When even though transmission is disabled, an AP's cell transmits for at least 15 minutes.
**Clear Condition**
When the cell stops transmission.
**Severity**
Major
**System Impact**
* The AP cell may transmit when not expected, potentially causing interference to neighboring radio equipment.
* This may result in a violation of federal spectrum regulations.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Access Point** tile > **Service Status** icon:  amber.
**Corrective Actions**
1. Check if any maintenance activity is currently in progress.
2. Check the AP's events and alerts and resolve any faults (Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > **Events & Alerts** tab). Any faults will be represented as "unexpected\_fault\_received" event, and new alerts as "enb\_alarm\_raised" event.
3. Check the AP's logs and resolve any errors (Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > **Logs** tab).
4. If the issue persists after completing the above steps, reboot the AP.
5. If the condition does not clear, contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
#### Mesh Filter-Frequency Mismatch
**Trigger Condition**
The Mesh Node's filter configuration and the attached AP's frequency are mismatched, and this condition persists for at least five minutes.
**Clear Condition**
The Mesh Node's filter configuration and the AP's frequency are aligned again.
**Severity**
Major
***
### Access Point S-Plane Alerts
#### Timing Out of Sync
**Trigger Condition**
When a 5G AP fails to obtain a PTP lock.
**Clear Condition**
When the AP successfully receives the PTP signal and synchronizes with it.
**Severity**
Major
**System Impact**
The AP will stop transmitting.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > **Overview** tab > **Access Point Details** section > **Sync Status** icon: If PTP is not locked,  red.
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert count has returned to its pre-incident state.
* Onyx Portal > **Dashboard**: All dashboard tiles have returned to their pre-incident state.
***
## FHM Alerts
### FHM C-Plane Alerts
#### Packet Loss Detected
**Trigger Condition**
When "Radio Unit Loss of Signal Detection" (RU-los-detect) is triggered on FHM RU ports due to early/late packets at least three times in five minutes.
**Clear Condition**
When RU-los-detect is not triggered more than two times in the last five minutes, and no early/late packets are detected between the FHM and RU.
**Severity**
Major
**System Impact**
* The network is affected due to the RU not being able to function correctly.
* User traffic may be unavailable depending on the mode of failure.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* An alert is raised for the specific FHM port number and the serial number of the RU attached to this port.
**Corrective Actions**
1. Check if any maintenance activity is in progress.
2. Verify network connectivity between the FHM, RU, and Onyx Edge.
3. Verify timing/sync status on all NR components.
4. Contact a local technician for physical FHM inspection.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Returns to pre-incident alert counts.
* Confirm that packet loss is no longer occurring between the FHM and RU. (Onyx Portal > **Equipment** > **FHM** tab > check port status.)
***
### FHM M-Plane Alerts
#### Offline
**Trigger Condition**
When no M-plane messages have been received for the past 15 minutes. This can happen, for example, due to the FHM being powered off.
**Clear Condition**
When the M-plane connection is established again with the AP.
**Severity**
Major
**System Impact**
Management access to the FHM will be unavailable. Configurations, alerts, events, and metrics between the Onyx Portal and the FHM will not be in sync. User traffic may be unavailable depending on the mode of failure.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **FHM** tile > **Online** icon: The online status icon will display in  red indicating the FHM is offline. Hover tooltip displays the offline FHMs.
* Onyx Portal > **Equipment** > **FHM** tab > view FHM's details > **Overview** tab > **Online** icon: The **Online** icon will display in  red, and all other statuses will display in grey.
**Corrective Actions**
1. Check if any maintenance activity is in progress.
2. Check for power outages at the device location.
3. Verify the FHM is associated with the correct Onyx Edge (Onyx Portal > **Equipment** > **FHM** tab > view FHM's details > **FHM Details** section > **Onyx Edge** parameter).
4. Verify network connectivity between the FHM and Onyx Edge. Ping the FHM from Onyx Edge.
5. Contact a local technician for physical FHM inspection.
**Resolution Verification**
* Verify that the alert has cleared.
* Verify that all Dashboard tiles have returned to pre-incident conditions.
* Check FHM details (Onyx Portal > **Equipment** > **FHM** tab > view FHM details > **Overview** tab > **Online** icon). The **Online** icon should display in green.
***
## Mesh Node Alerts
### Mesh Node Domain Proxy Alerts
#### CPE CBSD New Grant
**Trigger Condition**
When using the GM03 Mesh Node, one or more new grants have been received within the last hour.
**Clear Condition**
When no new grants are received within the last one hour.
**Severity**
Warning
**System Impact**
* This alert is triggered upon receiving a new grant from SAS. For a Mesh Node that is already in transmission, it may result in a change in transmission power.
* Operators should verify that the new grant will not affect the required KPIs.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Access Point** tile > **Service Status** icon: Based on grant authorization state and previous transmission state of the Mesh Node,  green or  amber.
* Onyx Portal > **Dashboard** > **Access Point SAS Status** tile: Granted/Authorized CBSDs count may change depending on the CBSD's previous state.
* Onyx Portal > **Equipment** > **Mesh Node** tab > view Mesh Node's details > **Overview** tab: If no previous grants were available, SAS Status will move to Granted state and generally to Authorized state.
* Onyx Portal > **Equipment** > **Mesh Node** tab > view Mesh Node's details > **Overview** tab > **Mesh Node Details** tile > **Service Status** icon: If the Mesh Node was not transmitting previously, it can change to  green.
**Corrective Actions**
None.
**Resolution Verification**
None required for initial alert.
***
#### CPE CBSD Preferred Frequency or Bandwidth Unavailable
**Trigger Condition**
When using the GM03 Mesh Node, if the configured backhaul frequency or bandwidth to which the Mesh Node is connected becomes unavailable.
**Clear Condition**
When the preferred frequencies or bandwidth become available again.
**Severity**
Warning
**System Impact**
The Mesh Node is transmitting at reduced capacity and power and will not support any data traffic.
**Indications**
The GM03 Mesh Node will be online but does not have a grant.
**Corrective Actions**
1. Change the Mesh Node's backhaul frequency or bandwidth and reconnect.
2. The available frequency can be found in the "Spectrum Inquiry Response" log type (Onyx Portal > **Equipment** > **Mesh Node** tab > view Mesh Node's details > **Logs** tab > **DP Logs** section > "Spectrum Inquiry Response" log type). Filter for "From SAS To DP logs".
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to their pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
#### CPE CBSD Registration Failure
**Trigger Condition**
When using the GM03 Mesh Node, if one or more CPE CBSD registration attempts have failed within the last one hour.
**Clear Condition**
When no CPE CBSD registration failures occur for at least one hour.
**Severity**
Major
**System Impact**
The Mesh Node will become non-functional, as it cannot obtain any grants to transmit.
**Indications**
* Onyx Portal > **Equipment** > **Mesh Node** tab > view Mesh Node's details > **Overview** tab > SAS Status will show **Registered** in red .
* The Mesh Node will be reported offline. See the Mesh Node M-Plane [Offline](#mesh-node-offline) alert.
**Corrective Actions**
1. Check the Mesh Node's DP logs for the failure reason and take necessary action (Onyx Portal > **Equipment** > **Mesh Node** tab > view Mesh Node's details > **Logs** tab > **DP Logs** section).
2. The most probable cause is a parameter mismatch between the Onyx Portal and the SAS Portal. Verify the CPE CBSD registration on the Federated Wireless Portal has the correct information. Verify the FCC ID, Serial Number, CBSD Type and Category, Location, and Antenna parameters.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to their pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
### Mesh Node M-Plane Alerts
#### Offline
**Trigger Condition**
When a Mesh Node has remained offline for at least 10 minutes.
**Clear Condition**
When the Mesh Node comes back online.
**Severity**
Critical
**System Impact**
Configurations, alerts, events, metrics, etc. between the Onyx Portal and Mesh Node will not be in sync.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Mesh Node** tile > **Online** icon: Depending on whether other Mesh Nodes are offline,  amber or  red.
* Onyx Portal > **Dashboard** > **Mesh Node** tile > **Service Status** icon: Depending on whether other Mesh Nodes are offline,  amber or  grey.
* Onyx Portal > **Equipment** > **Mesh Node** tab > Mesh Nodes list > **Compute Resource** icon:  red.
* Onyx Portal > **Equipment** > **Mesh Node** tab > view Mesh Node's details > **Overview** tab > **Mesh Node Details** tile > **Compute Resource** icon:  red.
**Corrective Actions**
1. Check the Mesh Node's Internet connectivity.
2. Verify that the subscriber associated with the Mesh Node is connected and active.
3. If Internet connectivity is confirmed, ensure the Mesh Node is properly provisioned. Log on to the Mesh Node and run the `checkin_cli.py` command. Investigate and resolve any errors in the output.
4. Verify power supply to the Mesh Node equipment.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Returns to pre-incident alert counts.
* Onyx Portal > **Dashboard**: All tiles return to their pre-incident states.
***
### Mesh Node MCU-Plane Alerts
#### Tunnel Down
**Trigger Condition**
When the Mesh Tunnel between the Mesh Node and the Onyx Edge remains down for at least five minutes.
**Clear Condition**
When the Mesh Tunnel between the Mesh Node and the Onyx Edge is restored.
**Severity**
Major
**System Impact**
The Mesh AP behind the Mesh Node will not be configured, preventing UE from attaching to it.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Equipment** > **Mesh Node** tab > Mesh Nodes list > **Compute Resource** icon:  red.
* Onyx Portal > **Equipment** > **Mesh Node** tab > view Mesh Node's details > **Overview** tab > **Mesh Node Details** tile > **Compute Resource** icon:  red.
**Corrective Actions**
1. Check the Mesh Node's Internet connectivity.
2. Check if the subscriber associated with the Mesh Node is connected and active.
3. Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Returns to pre-incident alert counts.
* Onyx Portal > **Dashboard**: All tiles return to their pre-incident states.
***
#### Watchdog Powercycle
**Trigger Condition**
When the Mesh Node is power cycled by the Watchdog service within the last 10 minutes.
**Clear Condition**
When the Mesh Node Watchdog service has not triggered a power cycle on the Mesh Node for at least 10 minutes.
**Severity**
Minor
**System Impact**
* The mesh network will be affected until the Mesh Node reconnects and comes back online.
* UE will be unable to attach to the Mesh AP.
**Indications**
Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
**Corrective Actions**
* Watchdog is triggered due to issues with the "cpe\_controller" service or modem identification. If the alert persists, contact GXC Technical Support.
* Check the alert's details for the cause.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to their pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
### Mesh Node Platform Alerts
#### CPU Usage
**Trigger Condition**
When a Mesh Node's CPU usage exceeds 70% of capacity in the last five minutes.
**Clear Condition**
When the Mesh Node's CPU usage drops below 70% of capacity.
**Severity**
Minor
**System Impact**
* Delays may occur in signaling and data processing at the Mesh Node.
* If CPU usage continues to rise, unexpected system behavior may occur.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Equipment** > **Mesh Node** tab > Mesh Nodes list > **Compute Resource** icon:  red.
* Onyx Portal > **Equipment** > **Mesh Node** tab > view Mesh Node's details > **Overview** tab > **Mesh Node Details** tile > **Compute Resource** icon:  red.
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Returns to pre-incident alert counts.
* Onyx Portal > **Dashboard**: All tiles return to their pre-incident states.
* Onyx Portal > **Equipment** > **Mesh Node** tab > view Mesh Node's details > **Overview** tab > **Mesh Node Details** tile > **Compute Resource** icon:  green.
***
#### Disk Usage
**Trigger Condition**
When a Mesh Node's disk usage exceeds 70% of capacity.
**Clear Condition**
When the Mesh Node's disk usage drops below 70% of capacity.
**Severity**
Major
**System Impact**
Delays in signaling and data processing at the Mesh Node.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Equipment** > **Mesh Node** tab > **Mesh Node** list > **Compute Resource** icon:  red.
* Onyx Portal > **Equipment** > **Mesh Node** tab > view Mesh Node's details > **Overview** tab > **Mesh Node Details** tile > **Compute Resource** icon:  red.
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Returns to pre-incident alert counts.
* Onyx Portal > **Dashboard**: All tiles return to their pre-incident states.
* Onyx Portal > **Equipment** > **Mesh Node** tab > view Mesh Node's details > **Overview** tab > **Mesh Node Details** tile > **Compute Resource** icon:  green.
***
#### Memory Usage
**Trigger Condition**
When a Mesh Node's memory usage exceeds 70% of capacity.
**Clear Condition**
When the Mesh Node's memory usage drops below 70% of capacity.
**Severity**
Minor
**System Impact**
Delays in signaling and data processing at the Mesh Node.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Equipment** > **Mesh Node** tab > Mesh Nodes list > **Compute Resource** icon:  red.
* Onyx Portal > **Equipment** > **Mesh Node** tab > view Mesh Node's details > **Overview** tab > **Mesh Node Details** tile > **Compute Resource** icon:  red.
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to their pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles return to their pre-incident states.
* Onyx Portal > **Equipment** > **Mesh Node** tab > view Mesh Node's details > **Overview** tab > **Mesh Node Details** tile > **Compute Resource** icon:  green.
***
### Mesh Node Provisioning Server Alerts
#### Provisioning Server Connection Failure
**Trigger Condition**
When a Mesh Node has not successfully checked in with the Provisioning Server within the past 35 minutes.
**Clear Condition**
When the Mesh Node successfully checks in with the Provisioning Server.
**Severity**
Warning
**System Impact**
* A new Mesh Node will be unable to connect to the Onyx Portal or begin operations.
* For an existing Mesh Node:
* If the keys have changed, it will be unable to get the updated keys from the Provisioning Server and will be unable to connect to the Onyx Portal.
* If the keys have not changed, there will be no impact.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Mesh Node** tile > **Online** icon:
* If the Mesh Node's unique keys have changed,  red.
* If the Mesh Node's unique keys have not changed,  green.
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to their pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
## Onyx Edge (Core) Alerts
### Onyx Edge (Core) C-Plane Alerts
#### DHCP Server Failed
**Trigger Condition**
When the DHCP server, responsible for assigning IP addresses to UE, has been unavailable for five minutes.
**Clear Condition**
When the DHCP server becomes available.
**Severity**
Major
**System Impact**
* UE may not be able to obtain IP addresses for data connectivity.
* New data sessions will be impacted while existing sessions may continue to function.
**Indication**
Onyx Portal > **Dashboard** > common counter indications.
**Corrective Actions**
Check the DHCP server health in the network.
**Resolution Verification**
Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
***
#### NG Setup Failure
**Trigger Condition**
When an NG Setup Request failure is detected within the last five minutes.
**Clear Condition**
When no NG Setup Request failures occur within the last five minutes.
**Severity**
Major
**System Impact**
All APs connected to the Onyx Edge (Core) will stop transmission if setup fails.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Onyx Edge** tile > **Service Status** icon: If failures are persistent,  red.
* Onyx Portal > **Dashboard** > **Access Point** tile > **Service Status** icon: If failures are persistent,  red.
* Onyx Portal > **Dashboard** > **Subscribers** tile: Subscribers impacted by the Onyx Edge will move to **Unknown** state.
* Onyx Portal > **Dashboard** > **Downlink/Uplink Traffic** tile: Traffic will reduce to the extent of the traffic handled by the Onyx Edge.
* Onyx Portal > **Dashboard** > **Data Usage** tile: Data Usage will reduce to the extent of the traffic handled by the Onyx Edge.
* Onyx Portal > **Dashboard** > **Backhaul (SGi) Health** tile: May reduce to the extent of traffic handled by the Onyx Edge.
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
#### SCTP Outbound Stalled
**Trigger Condition**
SCTP inbound ordered chunks have been increasing over the last 15 minutes while SCTP outbound ordered chunks have remained flat.
**Clear Condition**
Outbound SCTP chunks resume normal flow, indicating the core is processing and responding to signaling messages again.
**Severity**
Major
**System Impact**
* The NGAP/NAS signaling layer on the Onyx Edge core is stalled — SCTP packets are arriving from the access network but the core is not sending any responses back.
* New UE procedures (attach, registration, handover, PDU session establishment) will fail because signaling responses are not being sent.
* Existing sessions may continue to pass user-plane traffic for a time, but any control-plane operation (e.g., service request, paging response, session modification) will time out.
* If the condition persists, APs may tear down their SCTP associations and trigger S1/NG Setup failures, leading to a broader service outage.
**Indications**
* Onyx Portal > **Dashboard** > common counter indications
* Onyx Portal > **Dashboard** > **Onyx Edge** tile > **Service Status** — May change to Red if the stall persists and signaling associations are lost
* Onyx Portal > **Dashboard** > **Subscribers** — Active subscriber count may begin to decline as UE procedures fail
* Onyx Portal > **Dashboard** > **Downlink/Uplink Traffic** — Control-plane stall may eventually impact data traffic as sessions cannot be established or modified
**Corrective Actions**
Contact GXC Support. There is no automatic recovery action for this condition.
**Resolution Verification**
From the Dashboard:
* The alerts count has returned to the condition prior to the incident.
* SCTP outbound chunk counters are incrementing normally.
* UE attach/registration procedures are succeeding again.
***
#### UE IMSI-IMEI Validation Failure
**Trigger Condition**
When attach requests for a UE have been rejected in the last 15 minutes because the UE IMEI does not match the configured IMSI-IMEI mapping.
**Clear Condition**
When no attach requests for the UE have failed in the last 15 minutes due to IMSI-IMEI validation.
**Severity**
Warning
**System Impact**
Any of the following:
* Legitimate UE cannot attach to the network due to incorrect configuration.
* Illegal attempt to use the network.
**Indications**
* Onyx Portal > **Dashboard** > common counter indications.
* Onyx Edge Control Plane Transaction Status shows attach failures.
* Onyx Edge events list displays IMEI mismatch failures (Onyx Portal > **Equipment** > **Onyx Edge (Core)** tab > view Onyx Edge's details > **Events & Alerts** tab).
**Corrective Actions**
1. Identify the offending IMSI and IMEI: In the Onyx Edge events view, filter with stream "mme" and look for Attach Reject events to identify the offending IMSI and IMEI. (Onyx Portal > **Equipment** > **Onyx Edge (Core)** tab > view Onyx Edge's details > **Events & Alerts** tab.)
2. Determine the appropriate action:
* If the IMEI is not authorized for the IMSI, no further action is required in Onyx Portal. The operator can investigate who is attempting to attach with the unauthorized UE.
* If the IMEI mapping is incorrectly configured, correct it in the subscriber configuration (Onyx Portal > **Subscribers**).
**Resolution Verification**
* Verify that the alert has cleared.
* Confirm that the UE can successfully attach to the network.
***
#### UE Registration Failure
**Trigger Condition**
When registration requests for a UE have failed for reasons other than unknown user or IMEI validation failures in the past 15 minutes.
**Clear Condition**
When no registration requests for a UE have failed for reasons other than unknown user or IMEI validation failures for at least 15 minutes.
**Severity**
Warning
**System Impact**
UE cannot attach to the network.
**Indications**
* Onyx Portal > **Dashboard** > common counter indications.
* Onyx Portal > **Equipment** > **Onyx Edge (Core)** tab > view Onyx Edge's details: Control Plane Transaction Status shows registration failures.
**Corrective Actions**
1. Ensure the subscriber/IMSI is configured in the Onyx Portal (Onyx Portal > **Subscribers** > **Subscriber** tab).
2. Ensure the subscriber's service status is set to Active (Onyx Portal > **Subscribers** > **Subscriber** tab > view subscriber's details > **Subscriber Details** section > **Service** parameter).
3. Contact GXC Technical Support.
**Resolution Verification**
* Verify that the alert has cleared.
* Confirm that the affected UE can attach successfully and pass data traffic.
***
### Onyx Edge (Core) CU-Plane Alerts
#### HA Peer Down
**Trigger Condition**
When, in an Onyx Edge pool, the Primary Onyx Edge detects a peer Onyx Edge is down. A peer Onyx Edge can be marked as "down" for the following reasons:
* NG interface is down
* N6 interface is down
* Both NG and N6 interfaces are down
* The peer Onyx Edge is powered down
The Primary Onyx Edge detects a peer is down within 10 minutes of it going down.
**Clear Condition**
When the Primary Onyx Edge detects that the peer Onyx Edge is operational.
**Severity**
Major
**System Impact**
When a peer Onyx Edge is reported as down, if the NG/N6 interface is also down, it will not be able to handle any UE traffic and is flagged as non-operational. A complete blackout will occur if all the Onyx Edge in a pool become non-operational.
**Indications**
Common Dashboard indications.
**Corrective Actions**
1. Check the Onyx Edge pool's status (Onyx Portal > **Equipment** > **Onyx Edge** tab > **Onyx Edge Pool** tile > view pool's details > **HA Connectivity Status** icon):
*  green — One Onyx Edge is functioning as the Primary, and the others as Standby.
*  amber — One Onyx Edge is functioning as the Primary, but one or more of the other Onyx Edge are non-functional.
*  red — All Onyx Edge are non-functional, or their status is not available.
*  grey — All Onyx Edge are offline.
2. Check if all the Onyx Edge in the pool are online (Onyx Portal > **Equipment** > **Onyx Edge** tab > **Onyx Edge Pool** tile > view pool's details > **Associated Onyx Edge** tile > **Online** column > **Online** icon):
*  green — The Onyx Edge has checked in with the Onyx Portal in the last five minutes.
*  red — The Onyx Edge has not checked in with the Onyx Portal in the last five minutes.
3. If the NG interface is down, check the NG connection between the peer Onyx Edge and APs. In a healthy NG interface, the Onyx Edge should be able to ping each AP (Onyx Portal > **Equipment** > **Onyx Edge** tab > view Onyx Edge's details > **Actions** > **Ping**). Verify physical connections, switch configuration, and VLAN assignments for both the Onyx Edge and APs.
4. If the N6 interface is down, check Internet connectivity. In a healthy N6 interface, the Onyx Edge should be able to ping the Internet (8.8.8.8) (Onyx Portal > **Equipment** > **Onyx Edge** tab > view Onyx Edge's details > **Actions** > **Ping**). Verify physical connections, switch configuration, and VLAN assignments.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Returns to pre-incident alert counts.
* Onyx Portal > **Dashboard**: All tiles return to their pre-incident states.
***
### Onyx Edge (Core) M-Plane Alerts
#### Offline
**Trigger Condition**
When an Onyx Edge (Core) remains offline for at least 10 minutes.
**Clear Condition**
When the Onyx Edge (Core) comes back online.
**Severity**
Critical
**System Impact**
Configurations, alerts, events, metrics, etc. between the Onyx Portal and the Onyx Edge (Core) will be out of sync.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Onyx Edge** tile > **Online** icon: Depending on whether other Onyx Edge are offline,  amber or  red.
* Onyx Portal > **Dashboard** > **Onyx Edge** tile > **Service Status** icon: Depending on whether other Onyx Edge are offline,  amber or  grey.
* Onyx Portal > **Dashboard** > **Access Point** tile > **Online** icon: Depending on whether other Onyx Edge are offline,  amber or  grey.
* Onyx Portal > **Dashboard** > **Access Point** tile > **Service Status** icon: Depending on whether other Onyx Edge are offline,  amber or  grey.
* Onyx Portal > **Dashboard** > **Subscribers** tile: Total subscribers impacted by this Onyx Edge will change to Unknown.
* Onyx Portal > **Dashboard** > **Downlink/Uplink Traffic** tile: Reduces by the extent of traffic handled by the Onyx Edge.
* Onyx Portal > **Dashboard** > **Data Usage** tile: Reduces by the extent of traffic handled by the Onyx Edge.
* Onyx Portal > **Dashboard** > **Backhaul (SGi) Health** tile: Reduces by the extent of traffic handled by the Onyx Edge.
**Corrective Actions**
1. Check the Onyx Edge (Core)'s Internet connectivity on the N6 interface. This cannot be done from the Onyx Portal when the Onyx Edge (Core) is offline. If some other system, such as a remote laptop in the local network is accessible, ping the Onyx Edge (Core) to check if there is a local network issue, and then log on to the Onyx Edge (Core) to verify Internet connectivity.
2. At the Onyx Edge (Core)'s location, verify power and connectivity to the equipment.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
### Onyx Edge (Core) MCU-Plane Alerts
#### Service Down
**Trigger Condition**
When any of the following conditions occur:
* All APs remain offline for five minutes.
* All APs are S1-disconnected for five minutes.
* Any critical service has restarted more than three times in the last five minutes.
* Any critical service remains down for five minutes.
**Clear Condition**
When the trigger condition is resolved.
**Severity**
Critical
**System Impact**
The Onyx Edge may be offline or may not function as expected, potentially causing UE to lose service.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Onyx Edge** tile > **Service Status** icon: Depending on how other APs are connected to this and other Onyx Edge, and how they are affected, the icon will change to  amber or  red.
* Onyx Portal > **Dashboard** > **Access Point** tile > **Online** icon: Depending on if the APs are affected, the icon may change to  amber.
* Onyx Portal > **Dashboard** > **Access Point** tile > **Service Status** icon: Depending on if the APs are affected, the icon will change to  amber or  red.
* Onyx Portal > **Dashboard** > **Subscribers** tile: Subscribers impacted by the Onyx Edge may move to **Unregistered** state.
* Onyx Portal > **Dashboard** > **Downlink/Uplink Traffic** tile: Traffic will decrease proportionately to the volume previously handled by the Onyx Edge.
* Onyx Portal > **Dashboard** > **Data Usage** tile: May decrease proportionately to the traffic previously handled by the Onyx Edge.
* Onyx Portal > **Dashboard** > **Backhaul (SGi) Health** tile: May reduce to the extent of traffic handled by the Onyx Edge.
**Corrective Actions**
1. Check if the Onyx Edge is properly provisioned.
2. If an AP is offline and the [Access Point M-Plane Offline](#access-point-offline) alert has triggered:
* Check for network connectivity issues between the AP and the Onyx Edge.
* Check if the AP is associated with the correct Onyx Edge.
3. If an AP is S1-disconnected, and the "CBRS AP S1 Disconnected" alert has triggered:
* Check the AP's IPSec status.
* Check for any CBRS AP faults and alarm events (**Events and Alerts** tab).
4. If neither of the above alerts has triggered, restart Onyx Edge services (Onyx Portal > **Equipment** > **Onyx Edge** tab > view Onyx Edge (Core)'s details > **Actions** > **Restart Services**).
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Returns to pre-incident alert counts.
* Onyx Portal > **Dashboard**: All tiles return to their pre-incident states.
**Related Alerts**
* Access Point Management Plane [Offline](#access-point-offline) Alert
* Onyx Edge (Core) Management Plane [Offline](#onyx-edge-core-offline) Alert
***
### Onyx Edge (Core) Platform Alerts
#### CPU Usage
**Trigger Condition**
When an Onyx Edge (Core)'s CPU usage exceeds 70% of capacity in the last five minutes.
**Clear Condition**
When the Onyx Edge (Core)'s CPU usage drops below 70% of capacity in the last five minutes.
**Severity**
Minor
**System Impact**
* Possible delays in signaling and data processing at the Onyx Edge (Core).
* If CPU usage continues to rise, unexpected behaviors may be seen.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Equipment** > **Onyx Edge** tab > **Onyx Edge** list > **Compute Resource** icon:  red.
* Onyx Portal > **Equipment** > **Onyx Edge** tab > view Onyx Edge's details > **Overview** tab > **Onyx Edge Details** tile > **Compute Resource** icon:  red.
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Equipment** > **Onyx Edge** tab > **Onyx Edge** list > **Compute Resource** icon: Depending on the usage,  amber or  green.
* Onyx Portal > **Equipment** > **Onyx Edge** tab > view Onyx Edge (Core)'s details > **Overview** tab > **Onyx Edge Details** tile > **Compute Resource** icon: Depending on the usage,  amber or  green.
***
#### Disk Usage
**Trigger Condition**
When an Onyx Edge (Core)'s disk usage exceeds 70% of capacity in the last five minutes.
**Clear Condition**
When the Onyx Edge (Core)'s disk usage drops below 70% of capacity in the last five minutes.
**Severity**
Major
**System Impact**
* If the disk usage continues to rise, it may eventually cause downtime on the Onyx Edge (Core).
* The Onyx Edge (Core) may stop collecting critical logs required for debugging issues.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Equipment** > **Onyx Edge** tab > **Onyx Edge** list > **Compute Resource** icon:  red.
* Onyx Portal > **Equipment** > **Onyx Edge** tab > view Onyx Edge (Core)'s details > **Overview** tab > **Onyx Edge Details** tile > **Compute Resource** icon:  red.
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Equipment** > **Onyx Edge** tab > **Onyx Edge** list > **Compute Resource** icon: Depending on the usage,  amber or  green.
* Onyx Portal > **Equipment** > **Onyx Edge** tab > view Onyx Edge (Core)'s details > **Overview** tab > **Onyx Edge Details** tile > **Compute Resource** icon: Depending on the usage,  amber or  green.
***
#### Memory Usage
**Trigger Condition**
When an Onyx Edge (Core)'s memory usage exceeds 70% of capacity.
**Clear Condition**
When the Onyx Edge (Core)'s memory usage drops below 70% of capacity.
**Severity**
Minor
**Indications**
Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Equipment** > **Onyx Edge** tab > **Onyx Edge** list > **Compute Resource** icon: Depending on the usage,  amber or  green.
* Onyx Portal > **Equipment** > **Onyx Edge** tab > view Onyx Edge (Core)'s details > **Overview** tab > **Onyx Edge Details** tile > **Compute Resource** icon: Depending on the usage,  amber or  green.
***
### Onyx Edge (Core) Provisioning Server Alerts
#### Provisioning Server Connection Failure
**Trigger Condition**
When an Onyx Edge (Core) has not successfully checked in with the Provisioning Server within the past 35 minutes.
**Clear Condition**
When the Onyx Edge (Core) successfully checks in with the Provisioning Server.
**Severity**
Warning
**System Impact**
* A new Onyx Edge (Core) will be unable to connect to the Onyx Portal or begin operations.
* For an existing Onyx Edge (Core):
* If the keys have changed, it will be unable to get the updated keys from the Provisioning Server and will be unable to connect to the Onyx Portal.
* If the keys have not changed, there will be no impact.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Onyx Edge** tile > **Online** icon:
* If the Onyx Edge (Core)'s unique keys have changed:  red.
* If the Onyx Edge (Core)'s unique keys have not changed:  green.
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
## Onyx Edge (NR) Alerts
### Onyx Edge (NR) C-Plane Alerts
#### F1 Setup Failure
**Trigger Condition**
When an F1 Setup Request failure occurs within the last five minutes.
**Clear Condition**
When no F1 Setup Request failures occur within the last five minutes.
**Severity**
Critical
**System Impact**
All APs connected to the Onyx Edge may stop transmission if the setup fails.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Onyx Edge** tile > **Service Status** icon: If failures are persistent,  red.
* Onyx Portal > **Dashboard** > **Access Point** tile > **Service Status** icon: If failures are persistent,  red.
* Onyx Portal > **Dashboard** > **Subscribers** tile: Subscribers impacted by the Onyx Edge will move to **Unknown** state.
* Onyx Portal > **Dashboard** > **Downlink/Uplink Traffic** tile: Traffic will reduce to the extent of the traffic handled by the Onyx Edge.
* Onyx Portal > **Dashboard** > **Data Usage** tile: Data Usage will reduce to the extent of the traffic handled by the Onyx Edge.
**Corrective Actions**
1. Check if any maintenance activity is currently in progress.
2. Check if any recent configuration changes have been made.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
#### RRC Security Mode Failure
**Trigger Condition**
When at least one RRC Security Mode failure occurs within the last five minutes.
**Clear Condition**
When no RRC Security Mode failures occur within the last five minutes.
**Severity**
Warning
**System Impact**
Affected UE may experience issues connecting to the system.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Subscribers** tile: Subscribers impacted by this issue will move to **Unknown** state.
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
#### RRC Setup Failure
**Trigger Condition**
When more than 25% of RRC Connection Setup attempts in the last 15 minutes have failed, and this condition has persisted for at least the last three minutes.
**Clear Condition**
When more than 75% of RRC Connection Setup attempts in the last 15 minutes completed successfully.
**Severity**
Warning
**System Impact**
Failures may result from UE being in poor coverage areas or a larger underlying system issue preventing UE from establishing an RRC connection.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Subscribers** tile: Subscribers impacted by this issue will move to **Unknown** state.
**Corrective Actions**
1. Check if any maintenance activity is currently in progress.
2. Check if any recent configuration changes have been made.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
### Onyx Edge (NR) M-Plane Alerts
#### Offline
**Trigger Condition**
When an Onyx Edge (NR) remains offline for at least 10 minutes.
**Clear Condition**
When the Onyx Edge (NR) comes back online.
**Severity**
Critical
**System Impact**
Configurations, alerts, events, metrics, etc. between the Onyx Portal and the Onyx Edge (NR) will not be in sync.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Onyx Edge** tile > **Online** icon: Depending on whether other Onyx Edge are offline,  amber or  red.
* Onyx Portal > **Dashboard** > **Onyx Edge** tile > **Service Status** icon: Depending on whether other Onyx Edge are offline,  amber or  grey.
* Onyx Portal > **Dashboard** > **Access Point** tile > **Online** icon: Depending on whether other Onyx Edge are offline,  amber or  grey.
* Onyx Portal > **Dashboard** > **Access Point** tile > **Service Status** icon: Depending on whether other Onyx Edge are offline,  amber or  grey.
* Onyx Portal > **Dashboard** > **Subscribers** tile: Subscribers impacted by the Onyx Edge will move to **Unknown** state.
* Onyx Portal > **Dashboard** > **Downlink/Uplink Traffic** tile: Traffic will reduce to the extent of traffic handled by the Onyx Edge.
* Onyx Portal > **Dashboard** > **Data Usage** tile: Data Usage will reduce to the extent of traffic handled by the Onyx Edge.
* Onyx Portal > **Dashboard** > **Backhaul (SGi) Health** tile: Will reduce to the extent of traffic handled by the Onyx Edge.
**Corrective Actions**
1. Check the Onyx Edge's Internet connectivity on the SGi/N6 interface.
* This cannot be done from the Onyx Portal when the Onyx Edge is offline.
* If another system, such as a remote laptop in the local network is accessible, try pinging the Onyx Edge to check if there is a local network issue.
* If the Onyx Edge is reachable, log in to verify Internet connectivity.
2. At the Edge location, verify power and connectivity to the equipment.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
### Onyx Edge (NR) MCU-Plane Alerts
#### Service Down
**Trigger Condition**
When any of the following conditions occur:
* F1c connection is down for five minutes.
* NGc connection is down for five minutes.
* Any critical Edge services have unexpectedly restarted more than three times within the last five minutes.
* Any critical Edge services remain down for five minutes.
* gNB services have restarted due to failures in the last five minutes.
**Clear Condition**
When the trigger condition is resolved.
**Severity**
Critical
**System Impact**
The Onyx Edge may be offline or not functioning as expected, potentially preventing UE from receiving service.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Onyx Edge** tile > **Service Status** icon: Depending on whether other Onyx Edge are also experiencing failures,  amber or  red.
* Onyx Portal > **Dashboard** > **Access Point** tile > **Online** icon: Depending on whether the APs are affected,  amber or  red.
* Onyx Portal > **Dashboard** > **Access Point** tile > **Service Status** icon: Depending on whether the APs are affected,  amber or  red.
* Onyx Portal > **Dashboard** > **Subscribers** tile: Subscribers impacted by the Onyx Edge may move to **Unregistered** state.
* Onyx Portal > **Dashboard** > **Downlink/Uplink Traffic** tile: Traffic will reduce to the extent of the traffic handled by the Onyx Edge.
* Onyx Portal > **Dashboard** > **Data Usage** tile: Data Usage will reduce to the extent of the traffic handled by the Onyx Edge.
* Onyx Portal > **Dashboard** > **Backhaul (SGi) Health** tile: May reduce to the extent of traffic handled by the Onyx Edge.
**Corrective Actions**
1. Check if the Onyx Edge (NR) is provisioned properly.
2. Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
**Related Alerts**
* Onyx Edge (NR) Control Plane [F1 Setup Failure](#f1-setup-failure) Alert — Can trigger the Onyx Edge (NR) MCU-Plane "Service Down" alert.
* Onyx Edge (Core) Control Plane [NG Setup Failure](#ng-setup-failure) Alert — Can trigger the Onyx Edge (NR) MCU-Plane "Service Down" alert.
***
### Onyx Edge (NR) Platform Alerts
#### CPU Usage
**Trigger Condition**
When an Onyx Edge (NR)'s CPU usage exceeds 80% of capacity in the last five minutes.
**Clear Condition**
When the Onyx Edge (NR)'s CPU usage drops below 80% of capacity in the last five minutes.
**Severity**
Minor
**System Impact**
* Potential delays in signaling and data processing at the Onyx Edge (NR).
* If CPU usage continues to rise, unexpected behaviors may be seen.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Equipment** > **Onyx Edge** tab > **Onyx Edge (n)** tile > **Compute Resource** column, and Onyx Portal > **Equipment** > **Onyx Edge** tab > view Onyx Edge's details > **Overview** tab > **Onyx Edge Details** tile: The Compute Resource icon will change to  red.
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Equipment** > **Onyx Edge** tab > **Onyx Edge (n)** tile > **Compute Resource** column, and Onyx Portal > **Equipment** > **Onyx Edge** tab > view Onyx Edge's details > **Overview** tab > **Onyx Edge Details** tile: Depending on the usage level, the Compute Resource icon will change to  amber or  green.
***
#### Disk Usage
**Trigger Condition**
When an Onyx Edge (NR)'s disk usage exceeds 70% of capacity in the last five minutes.
**Clear Condition**
When the Onyx Edge (NR)'s disk usage drops below 70% of capacity in the last five minutes.
**Severity**
Major
**System Impact**
* If disk usage continues to rise, it may eventually cause downtime on the Onyx Edge.
* The Onyx Edge (NR) may stop collecting critical logs needed for debugging issues.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Equipment** > **Onyx Edge** tab > **Onyx Edge (n)** tile > **Compute Resource** column, and Onyx Portal > **Equipment** > **Onyx Edge** tab > view Onyx Edge's details > **Overview** tab > **Onyx Edge Details** tile: The Compute Resource icon will change to  red.
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Equipment** > **Onyx Edge** tab > **Onyx Edge (n)** tile > **Compute Resource** column, and Onyx Portal > **Equipment** > **Onyx Edge** tab > view Onyx Edge's details > **Overview** tab > **Onyx Edge Details** tile: Depending on the usage level, the Compute Resource icon will change to  amber or  green.
***
#### Memory Usage
**Trigger Condition**
When an Onyx Edge (NR)'s memory usage exceeds 80% of capacity.
**Clear Condition**
When the Onyx Edge (NR)'s memory usage drops below 80% of capacity.
**Severity**
Minor
**System Impact**
If memory usage continues to rise, it could lead to downtime on the Onyx Edge.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Equipment** > **Onyx Edge** tab > **Onyx Edge (n)** tile > **Compute Resource** column, and Onyx Portal > **Equipment** > **Onyx Edge** tab > view Onyx Edge's details > **Overview** tab > **Onyx Edge Details** tile: The Compute Resource icon changes to  red.
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Equipment** > **Onyx Edge** tab > **Onyx Edge (n)** tile > **Compute Resource** column, and Onyx Portal > **Equipment** > **Onyx Edge** tab > view Onyx Edge's details > **Overview** tab > **Onyx Edge Details** tile: Depending on the usage level, the Compute Resource icon changes to  amber or  green.
***
### Onyx Edge (NR) Provisioning Server Alerts
#### Provisioning Server Connection Failure
**Trigger Condition**
When an Onyx Edge (NR) has not successfully checked in with the Provisioning Server within the past 35 minutes.
**Clear Condition**
When the Onyx Edge (NR) successfully checks in with the Provisioning Server.
**Severity**
Warning
**System Impact**
* A new Onyx Edge (NR) will be unable to connect to the Onyx Portal or begin operations.
* For an existing Onyx Edge (NR):
* If the keys have changed, it will be unable to get the updated keys from the Provisioning Server and will be unable to connect to the Onyx Portal.
* If the keys have not changed, there will be no impact.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* Onyx Portal > **Dashboard** > **Onyx Edge** tile > **Online** icon:
* If the Onyx Edge (NR)'s unique keys have changed:  red.
* If the Onyx Edge (NR)'s unique keys have not changed:  green.
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
***
### Onyx Edge (NR) S-Plane Alerts
#### GPS Signal Not Available
**Trigger Condition**
When the Onyx Edge timing service has a high time difference between external timestamp signals (GPS) and the PTP hardware clock, and is unable to sync the hardware clock to GPS timing.
**Clear Condition**
When the Onyx Edge timing service successfully syncs the hardware clock to GPS timing.
**Severity**
Major
**System Impact**
The Onyx Edge Cell service may not function as expected. UE may be unable to obtain service.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* **Dashboard** > **Onyx Edge** tile > **Sync Status** icon: Will display as  red; hover tooltip shows error details.
* **Dashboard** > **Onyx Edge** tile > **Service Status** icon: Will display as amber or red depending on whether other Onyx Edge are also failing.
* **Dashboard** > **Access Point** tile > **Service Status** icon: Will display as  amber or  red depending on whether they are affected.
* **Dashboard** > **Subscribers** tile: Total subscribers impacted by this Onyx Edge may become unregistered.
**Corrective Actions**
1. Check if the Onyx Edge (NR) is provisioned properly.
2. Check the physical connections and if GPS mode is selected, verify GPS signal.
3. After the GPS signal is restored, restart all NR services to return to GPS mode.
4. Contact GXC Technical Support.
**Resolution Verification**
* Verify that all Dashboard tiles have returned to pre-incident states.
* Verify that the alert has cleared.
***
#### PHC2SYS Offset Is Too High
**Trigger Condition**
When the Onyx Edge timing service has a high time difference between the system clock and PTP hardware clock, and is unable to sync the system clock to the hardware clock.
**Clear Condition**
When the Onyx Edge timing service successfully syncs the system clock to the hardware clock.
**Severity**
Warning
**System Impact**
The Onyx Edge cell service may not function as expected. UE may be unable to obtain service.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* **Dashboard** > **Onyx Edge** tile > **Sync Status** icon: Will display as  red; hover tooltip shows error details.
* **Dashboard** > **Onyx Edge** tile > **Service Status** icon: Will display as  amber or  red depending on whether other Onyx Edges are also failing.
* **Dashboard** > **Access Point** tile > **Service Status** icon: Will display as  amber or  red depending on whether they are affected.
* **Dashboard** > **Subscribers**: Total subscribers impacted by this Onyx Edge may become unregistered.
**Corrective Actions**
1. Check if the Onyx Edge (NR) is provisioned properly.
2. Check the physical connections and verify GPS signal if GPS mode is selected.
3. Contact GXC Technical Support.
**Resolution Verification**
* Verify that the alert has cleared.
* Verify all Dashboard tiles have returned to pre-incident states.
***
#### TS2PHC Offset Is Too High
**Trigger Condition**
When the Onyx Edge timing service has a high time difference between external timestamp signals (GPS) and the PTP hardware clock and is unable to sync the hardware clock to GPS timing.
**Clear Condition**
When the Onyx Edge timing service successfully syncs the hardware clock to GPS timing.
**Severity**
Warning
**System Impact**
The Onyx Edge cell service may not function as expected. UE may be unable to obtain service.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* **Dashboard** > **Onyx Edge** tile > **Sync Status** icon: Will display as  red; hover tooltip shows error details.
* **Dashboard** > **Onyx Edge** tile > **Service Status** icon: Will display as  amber or  red depending on whether other Onyx Edges are also failing.
* **Dashboard** > **Access Point** tile > **Service Status** icon: Will display as  amber or  red depending on whether they are affected.
* **Dashboard** > **Subscribers**: Total subscribers impacted by this Onyx Edge may become unregistered.
**Corrective Actions**
1. Check if the Onyx Edge (NR) is provisioned properly.
2. Check the physical connections and verify GPS signal if GPS mode is selected.
3. Contact GXC Technical Support.
**Resolution Verification**
* Verify that the alert has cleared.
* Confirm that all Dashboard tiles have returned to their pre-incident states.
***
### Onyx Edge (NR) User Plane Alerts
#### Cell High DL BLER
**Trigger Condition**
Downlink BLER (Block Error Rate) for the cell exceeds 50% for at least 15 minutes.
**Clear Condition**
Downlink BLER for the cell falls to or below 50%.
**Severity**
Warning
***
#### Cell High UL BLER
**Trigger Condition**
Uplink BLER for the cell exceeds 50% for at least 15 minutes.
**Clear Condition**
Uplink BLER for the cell falls to or below 50%.
**Severity**
Warning
***
#### Early eCPRI Packets
**Trigger Condition**
More than 50% of eCPRI packets received for the cell in the last 15 minutes are classified as early.
**Clear Condition**
The proportion of early eCPRI packets falls to or below 50%.
**Severity**
Warning
***
#### Late eCPRI Packets
**Trigger Condition**
More than 50% of eCPRI packets received for the cell in the last 15 minutes are classified as late.
**Clear Condition**
The proportion of late eCPRI packets falls to or below 50%.
**Severity**
Warning
***
#### eCPRI Rx Down
**Trigger Condition**
No eCPRI Rx packets are received for the cell for at least 10 minutes, even though the RU's RF Tx is enabled/desired.
**Clear Condition**
eCPRI Rx packets resume being received while Tx remains enabled.
**Severity**
Warning
***
## Orchestrator Alerts
### Orchestrator Domain Proxy Alerts
#### SAS Connection Failure
**Trigger Condition**
When any of the following conditions occur:
* Could not connect to SAS at least three times in the last 15 minutes.
* At least one HTTP error from SAS in the last 15 minutes.
**Clear Condition**
When there are no SAS connection errors and no HTTP errors for at least 15 minutes.
**Severity**
Critical
**System Impact**
This could potentially mean the entire network is down, at least those APs that are dependent on SAS for their grants.
**Indications**
* Onyx Portal > [Alerts Counter Panel Indication](#alerts-counter-panel-indication).
* In case of constant connection errors, the transmit timer could expire and result in the cells going down. See [Cell Transmission Down Indications](#cell-transmission-down-indications).
* Onyx Portal > **Equipment** > **Access Point** tab > view AP's details > SAS status: The SAS state may not progress if not authorized, and the Authorized state may eventually revert to Granted on timer expiry.
**Corrective Actions**
Contact GXC Technical Support.
**Resolution Verification**
* Onyx Portal > Alerts Counter Panel: Alert counts revert to pre-incident levels.
* Onyx Portal > **Dashboard**: All tiles revert to their pre-incident states.
**Additional Information**
* There are two kinds of errors:
* **HTTP errors** — Should not occur under normal conditions; typically indicate an SAS-side issue or fundamental breakage in Domain Proxy.
* **Transport-level errors** — May occur due to connectivity issues (unable to reach SAS) or security issues (server-side or client-side authentication failures).
The error type can be determined from the alert labels.
* SAS Connection Failure alerting generates a single consolidated alert at the network level instead of individual alerts per AP.
## Related Documentation
* *5G Onyx Portal Operations Guide*
* *GXC Glossary*
## Contact GXC
To get in touch with GXC, please visit