> 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-das.md). # Manage DAS This section describes GXC's Distributed Antenna System (DAS) solution and explains how to add and manage DAS equipment. A DAS is a network of antennas connected to a common signal source that optimizes cellular coverage and signal quality within buildings or large facilities. Integrated with the GXC Onyx 4G Platform, the DAS extends cellular coverage across large indoor and outdoor environments where a single Access Point cannot provide adequate signal strength or capacity. GXC's DAS solution supports both Active DAS and Passive DAS architectures, offering flexible deployment options to address a wide range of venue and performance requirements. * **Active DAS** – In an Active DAS configuration, the signal from a GXC AP is distributed via fiber optics (RF over Fiber) to multiple Transmission Points (TPs). This architecture enables precise power management, improved signal quality, and minimal loss across long distances. Active DAS is supported in conjunction with Wilson DAS (pre-configured Wilson Electronics systems) as well as generic DAS (third-party systems requiring manual configuration). * **Passive DAS** – In a Passive DAS configuration, the AP's signal is distributed through coaxial cabling and passive components such as splitters and couplers. Passive DAS provides a cost-effective option for smaller or less complex deployments where fiber distribution is not necessary. Passive DAS is supported in conjunction with generic DAS equipment. Both architectures operate under full SAS coordination and leverage the Onyx Edge for power and grant management. By combining these architectures, GXC's DAS solution allows network planners to select the optimal design to meet specific venue size, RF conditions, and infrastructure constraints. This flexible implementation ensures consistent, high-quality coverage while maintaining full coordination with the SAS through the Onyx Edge and Domain Proxy. ## System Architecture A GXC DAS deployment consists of three primary components: * **Signal Source** – The GXC AP serves as the signal source for the DAS. It is responsible for generating the cellular signal and controlling the overall system power based on SAS grants. {% hint style="info" %} **NOTE:** The GXC AP must be a G501 unit operating in either Single Carrier mode or Carrier Aggregation mode. {% endhint %} * **DAS Equipment** – The DAS equipment distributes the signal from the GXC AP using a constant gain configured during commissioning. GXC's DAS solution supports both Active DAS and Passive DAS architectures, enabling flexible integration with different vendor systems and deployment requirements. * **Wilson DAS** – Pre-configured Wilson Electronics equipment that supports Active DAS deployments. It uses RF over Fiber for signal distribution and is optimized for high-performance, low-loss environments. * **Generic DAS** – Third-party equipment that supports either Active or Passive DAS deployments. It requires manual configuration during setup and can be adapted to suit venue-specific coverage, cabling, and power requirements. * **Transmission Points (TPs)** – Distributed antenna endpoints that transmit signals to user devices in their coverage area. Each TP is registered as an individual CBSD with the SAS and represents an individual radiating element in the DAS system with typical DAS deployments consisting of tens to hundreds of TPs. {% hint style="info" %} **NOTE:** TPs are created and registered as CBSDs only after the DAS is associated with an AP. The TP configuration automatically inherits frequency and bandwidth from the associated AP. All TPs in a DAS deployment operate using the same frequency and bandwidth as the associated AP. Any updates to AP frequency or bandwidth automatically apply to all associated TPs. {% endhint %} {% hint style="info" %} **NOTE:** In CBRS and WinnForum documentation, DAS Remote Antenna Units are referred to as "Transmission Points". This document consistently uses "Transmission Point" / "TP" to describe the individual antenna endpoints in the DAS system. {% endhint %} ### **Active DAS**

GXC DAS Architecture in Active DAS Configuration

The Active DAS configuration extends the GXC network by distributing the AP's signal via RF over Fiber to multiple TPs. In this setup, the GXC AP connects to the DAS Head End via RF coax, where the signal is actively amplified and converted for optical fiber transport. The fiber distribution minimizes signal loss and ensures high-quality transmission across long distances and multiple floors. Each TP receives a precisely controlled signal and rebroadcasts it to user devices within its coverage area. The Onyx Edge integrates with the Onyx Portal and Domain Proxy, providing centralized configuration, monitoring, and coordination with the SAS. Active DAS is typically used in large or complex venues where: * Long-distance signal distribution or multi-floor coverage is required * Fiber-based infrastructure is available * Enhanced power management and low-loss amplification are needed Supported DAS equipment: * Wilson DAS – Pre-configured Active DAS solution optimized for high-performance distribution. * Generic DAS – Manually configured third-party systems that can operate in Active DAS mode using RF over Fiber transport. This architecture enables scalable, high-performance indoor coverage with precise power control, centralized management, and full SAS compliance. ### **Passive DAS**

GXC DAS Architecture in Passive DAS Configuration

In a Passive DAS configuration, the GXC AP provides the cellular signal that is distributed through RF coaxial cabling and passive components such as splitters, couplers, and taps to multiple TPs within the building. Unlike Active DAS, this design does not rely on optical fiber or active amplification—instead, it leverages signal splitting and attenuation control for simpler and cost-effective deployment. Each TP radiates the RF signal within its coverage zone without active electronics or powered amplifiers. The Onyx Edge connects to the Onyx Portal and SAS Domain Proxy, ensuring consistent management, configuration, and SAS coordination across the system. Passive DAS is best suited for: * Small to medium-sized venues * Single-floor or compact layouts * Installations with shorter cable runs where fiber distribution is not necessary Supported DAS equipment: * Generic DAS – Third-party systems configured manually to operate in either Active or Passive mode, suitable for cost-sensitive or smaller-scale deployments. This architecture provides an efficient and economical solution for environments where basic signal distribution is sufficient to achieve reliable in-building coverage. ### DAS Deployment Considerations DAS is ideal for large, complex indoor environments where radio frequency signals face significant propagation challenges, including multi-floor buildings with concrete or steel construction, hospitals, hotels, underground facilities, and areas with substantial wall penetration and signal attenuation. DAS excels when centralized signal distribution is preferred, physical constraints require discreet antenna placement, or when remote antenna locations lack power or network connectivity. Multiple APs work best for open environments, smaller facilities, and situations where capacity is the primary driver. APs allow independent coverage with full backhaul capacity, enable effective load balancing, and provide flexibility for phased rollouts. For deployments under 50,000 square feet or when budget constraints favor lower initial capital expense, multiple APs typically provide better value than DAS infrastructure. A hybrid approach often delivers optimal results in complex environments. Large campuses might use APs for outdoor coverage while deploying DAS within large structures or use APs for open areas and DAS for challenging RF environments. The decision depends on building construction density, coverage area complexity, power and backhaul availability, RF obstacles, user capacity requirements, and aesthetic considerations. #### **Capacity Planning** The number of TPs in a deployment varies by venue size: * Small venues under 20,000 square feet may need 2-4 points. * Medium venues (20,000-100,000 sq ft) may need 4-8 points. * Large venues (100,000-500,000 sq ft) may need 8-20 points. * Very large venues may need 20 or more points. Coverage per TP ranges from 5,000-12,000 square feet for dense indoor spaces to 50,000-100,000 square feet for outdoor areas. Critical factors include building materials, floor plan complexity, target signal strength, user density, and power constraints. Capacity-wise, light usage supports 30-50 users per point, moderate usage handles 20-30 users, and heavy usage supports 10-20 users. Never deploy fewer than two TPs, plan infrastructure for 25-50% growth, and monitor for red flags like signal strength below -90 dBm, frequent drops, or more than 30-40 concurrent users per point. #### **How DAS Power Control Works** The GXC DAS system uses cascading power control architecture: > Power Flow: GXC Access Point > DAS Head End > TPs The DAS equipment operates with constant gain, meaning changes to the AP's output power results in proportional changes to all TP output powers. For example: * AP's configured output: 24 dBm * DAS constant gain: Variable per installation * Target TP output: 21 dBm **How It Works:** 1. During commissioning, the DAS vendor configures the DAS to produce the desired output power at each TP when the AP transmits at the expected level (e.g., 24 dBm). 2. Each TP requests a grant from the SAS for its desired power level. 3. The system adjusts the AP's power level based on the lowest grants received from SAS. 4. All TPs respond proportionally to the AP's power changes. The power control system operates based on the following technical principles: * **Target Power Specification** – Target power for each TP is specified as the combined TP output power and antenna gain, measured at the antenna input. Cable losses are accounted for in the target power configuration to ensure accurate power delivery. During DAS commissioning, amplifiers are configured to achieve the target power when the AP operates at maximum output. This approach ensures that each TP delivers the appropriate signal strength to its coverage area while maintaining compliance with SAS grant limits. * **Power Calculation** – The Onyx Edge monitors grant status for each TP and calculates the required AP power based on the lowest granted TP power levels. This calculation accounts for cable loss, antenna gains, and amplifier configuration to ensure accurate power distribution throughout the system. A linear relationship between AP output and TP output is maintained, allowing the Onyx Edge to dynamically adjust transmission power while preserving proportional signal strength across all TPs in the coordinated transmitter group. * **All-or-None Operation** – The GXC system operates in an "all-or-none" mode due to its shared signal architecture, where all TPs receive the same signal source from the AP without individual power control capability. This means that all TPs in the system must have valid grants before any transmission can occur; if even one TP lacks authorization, the entire system remains offline and does not radiate. To maintain compliance across all TPs, the AP adjusts its power to ensure that the most restrictive TP grant is not exceeded, effectively allowing the lowest-authorized power level to govern the entire coordinated transmitter group. #### **Grant Management Overview** Each TP must receive an individual SAS grant, and all TPs must be granted access to the same channel. If any TP fails to obtain or maintain a valid SAS grant, the entire DAS system stops transmission to ensure regulatory compliance. The entire DAS system operates at the power level determined by the lowest grant received by any TP. **Example Scenario:** * 10 TPs in the system * 9 TPs receive grants for 21 dBm * 1 TP receives a grant for 19 dBm (2 dB less than requested) **System Response:** * AP power reduced from 24 dBm to 22 dBm (2 dB reduction) * All 10 TPs now operate at 2 dB below their configured target power * 9 TPs operate at 19 dBm * 1 TP operates at 17 dBm This ensures the restricted TP does not exceed its granted power while maintaining system operation. #### **AP Grant Coordination** The GXC AP itself does not require a SAS grant as it transmits via cable to the DAS Head End rather than over-the-air. However, the AP must coordinate with all TP grants, as the Onyx Edge monitors grant status for every associated TP by serial number. The AP cannot transmit until all TPs receive authorization from the SAS, and all TPs must be granted on the same frequency channel, though they may receive different power levels within that channel. To ensure compliance, the AP adjusts its power to accommodate the lowest grant received among all TPs. #### **Coordinated Transmitter Group** All TPs associated with a single AP form a coordinated transmitter group that operates as a unified transmission unit for grant purposes. Within this group, all TPs must operate on the same channel, though individual TPs can have different power levels as granted by the SAS. This coordinated approach ensures that the DAS system functions cohesively while allowing for site-specific power adjustments based on coverage requirements and regulatory authorizations. #### **Grant Failure Behavior** If any single TP fails to receive a grant, the entire DAS system is immediately muted, the GXC AP ceases transmission, and all TPs become non-operational. The system will indicate grant failures, ensuring FCC compliance and preventing unauthorized spectrum usage. #### **Registration Process** The GXC DAS solution uses two-step registration for all TPs, consistent with the AP registration process: 1. **Registration** – The TP registers with the SAS through the Domain Proxy (DP). During this process, the system provides the CBSD identification and parameters, which the SAS then validates and acknowledges to complete the registration. The SAS registration process is Multi-Step registration, requiring user input. 2. **Grant Request** – The TP requests a spectrum grant specifying the desired power and frequency parameters. The SAS evaluates these requests based on interference and regulatory constraints, then issues a grant with approved parameters, which may differ from those originally requested. #### **Category Assignment** Each TP is registered as a CBSD with a category determined by its Effective Isotropic Radiated Power (EIRP): * **Category A** – Lower power devices, typically for indoor use * **Category B** – Higher power devices for indoor or outdoor use TPs in a DAS system can have different categories (A or B), provided each TP's maximum EIRP does not exceed its certified hardware limit. #### **Location Requirements** Each TP must be registered with coordinates corresponding to its fixed physical antenna location. Accurate location data is required for SAS interference analysis. #### **Same Channel Requirement** All TPs in a DAS system must operate on the same frequency channel. Channel consistency is enforced during grant requests. Different power levels are permitted within the same channel. ### **Bulk Provision TPs** To simplify operations, Onyx Portal supports bulk provisioning of TPs. The TP Bulk Provisioning feature uses a comma-separated values (CSV) file containing the details required to configure new TPs. You can obtain a sample CSV data file from GXC Technical Support. The CSV file can be edited in Microsoft Excel or any text editor. The CSV data file requires the following information for each TP: * Name – (Required) TP's identifier. * Serial Number – (Required) The TP equipment's vendor-assigned serial number. * Antenna Gain (dBi) – (Required) Antenna RF gain value (integer ≤ 128). * Max Power (dBm) – (Required) Maximum transmit power (integer 0-30). ## **View DAS Details** This section describes how to view summary and detailed information of existing DAS equipment: * [*View Summary Details of All DAS*](#view-summary-details-of-all-das) * [*View Details of a DAS*](#view-details-of-a-das) ### **View Summary Details of All DAS** **To view the summary details of all DAS equipment configured in the network:** {% stepper %} {% step %} In the navigation pane, click **Equipment** > **DAS** tab. The **Equipment** page > **DAS** tab displays the summary details of all DAS equipment configured in the network.
* **Name** – The DAS equipment's name. * **Venue** – The venue hosting the DAS equipment. * **Device Class** – The DAS equipment's type/model. * **Transmission Points** – The number of TPs connected to the DAS. * **Access Point** – The cellular AP that serves as the signal source (Gateway AP). * **Actions** – Shortcut menu options to view details, edit, and delete a DAS equipment. {% endstep %} {% endstepper %} ### **View Details of a DAS** **To view details of a particular DAS equipment:** {% stepper %} {% step %} In the navigation pane, click **Equipment** > **DAS** tab. The **Equipment** page > **DAS** tab displays the summary details of all DAS configured in the network. {% endstep %} {% step %} To view the details of a particular DAS, click its name. The ***\*** page displays the DAS equipment's details.
* **Overview** tab: * **DAS Details**: * **Name** – The DAS equipment's name. * **Serial** – The DAS equipment's vendor-assigned hardware serial number. * **Description** – The DAS equipment's description. * **Venue** – The venue hosting the DAS equipment. * **Device Class** – The DAS equipment's type/model. * **Access Point** – The associated AP's name. * **Transmission Points**: * **User ID** – Registration identifier in CBSD registration process. * **Registration Type** – The CBSD registration process type—**Multi-Step** (Manual registration process). * **Name** – TP's name. * **Serial Number** – TP's vendor-assigned hardware serial number. * **Antenna Gain** – RF gain in dBi. * **Max Pwr** – Maximum transmit power in dBm. * **State** – TP's SAS grant status: * **Registered** – TP has successfully registered with SAS but has not yet requested a grant. * **Granted** – SAS has approved a spectrum grant for this TP with specific power and frequency parameters. Note that Registered or Granted states are transitional; if a TP remains in Registered or Granted state for more than 5 minutes, review the Logs tab for potential issues with SAS communication. * **Authorized** – TP has an active grant and is permitted to transmit (operational state). Note that all TPs must be in Authorized state for system operation. * **Failed** – Grant request was denied or revoked; TP cannot operate. Note that if any single TP shows Failed, the entire DAS system is muted. * **Details** – To view a CBSD's details, click the corresponding ![](https://4071075005-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZc9hpHmiTCrh1sn4mWXn%2Fuploads%2FeCmJ6XO5ZMN3GPtaeixR%2Fimage.png?alt=media\&token=6e361534-69c7-4961-85b3-da8c9743880c) icon. The **CBSD Details** dialog box is displayed.
* CBSD Status – The CBSD's current SAS registration status, showing progression through Registered > Granted > Authorized stages. * **Registered** – CBSD has registered with SAS. * **Granted** – SAS has granted spectrum access. * **Authorized** – CBSD is authorized to transmit. * **SAS Configuration**: * **CBSD Category** – Classification type. * B – Indoor/enterprise category * **User ID** – Registration identifier. * **Desired State** – Target operational state. * **Antenna Gain (dBi)** – RF antenna gain in dBi. * **No. of Antennas** – Number of antenna elements. * **Preferred Min Pwr (dBm)** – Minimum operating power in dBm. * **Preferred Max Pwr (dBm)** – Maximum operating power in dBm. * **Preferred BW (MHz)** – Channel bandwidth in MHz. * **Preferred Frequencies (MHz)** – Operating frequency in MHz. * **Strict Preference** – Whether parameters specified are strict requirements. * **SAS Status**: * **FCC ID** – Federal Communications Commission identifier. Identifies the certified radio hardware used by the TP. For Wilson DAS, predefined. For Generic DAS, provided during configuration. * **No. of Grants** – Number of spectrum grants received. * **AP to DP Connection** – Whether connected to domain proxy. * **Current State** – Operational status – Registered, Granted, Authorized. {% endstep %} {% step %} Click the **Logs** tab. The **Logs** tab displays communication logs for the selected TP and between the selected entities—Domain Proxy (DP), Citizens Broadband Radio Service Devices (CBSDs/TPs), and the Spectrum Access System (SAS). Use these logs to: * Troubleshoot specific TP – Select a problematic TP to view its registration, grant, and heartbeat history. * Compare TP behavior – Switch between different TPs to compare their log patterns. * Isolate configuration changes – View logs for a newly added or recently modified TP. * Monitor Performance – Track the communication pattern for a specific TP over time.
* **DP Logs (n)** – Displays, within parenthesis, the total number of DP log entries currently shown. * **Transmission Point** – The specific TP for which log entries are displayed. The **Transmission Point** filter works in conjunction with the **From** and **To** dropdowns, allowing users to narrow down logs. For example: * Transmission Point: das\_tp1 * From: DP * To: CBSD This combination would show only messages sent from the DP to the specific TP das\_tp1. * **From** – The source entity that sent the message—DP, CBSD, SAS. * **To** – The destination entity that received the message—DP, CBSD, SAS. * DP Logs table: * **Timestamp** – Date and time when the log entry was recorded, displayed in MM/DD/YYYY, HH:MM:SS format. * **From** – The source entity that sent the message—DP, CBSD, SAS. * **To** – The destination entity that received the message—DP, CBSD, SAS. * **Type** – The type of SAS protocol message or operation. * **Message** – Detailed message content containing the complete protocol exchange data. {% endstep %} {% endstepper %} ## **Add DAS** This section describes how to add a DAS to your network. {% hint style="info" %} **NOTE:** You can add DAS only if you are a GXC Administrator, Partner Administrator, Super Administrator, or an Administrator. {% endhint %} **To add a DAS:** {% stepper %} {% step %} In the navigation pane, click **Equipment** > **DAS** tab. The **Equipment** page > **DAS** tab displays the summary details of all DAS configured in the network. {% endstep %} {% step %} In the upper-right corner of the page, click **Add Node** > **Add DAS**. The **Create DAS** page > **DAS** tab is displayed.
{% endstep %} {% step %} Enter the following details: * **Venue** – (Required) The venue hosting the DAS equipment. * **Name** – (Required) The DAS equipment's name. The name must be an alphanumeric value of maximum 32 characters. * **Serial Number** – (Required) The DAS equipment's vendor-assigned hardware serial number. * **Description** – (Required) Enter notes or details about the DAS equipment or the deployment. The description must be an alphanumeric value of maximum 128 characters. * **Device Class** – (Required) The DAS equipment's type/model: * **Wilson DAS** – Wilson Electronics-manufactured DAS equipment with pre-configured specifications. * **Generic DAS** – Third-party DAS equipment requiring manual configuration. {% endstep %} {% step %} At the lower-right corner of the page, click **Configure Transmission Points**.
{% endstep %} {% step %} Enter the following details: * **User ID** – Unique identifier for registering with the SAS. Enter an alphanumeric value of maximum 32 characters. * **Registration Type** – (Required) The CBSD registration process type. Default: **MultiStep**. * **FCC ID** – The Federal Communications Commission identifier for the equipment. * Add TPs: * **To add one TP at a time:** 1. Select the **Manual Add** radio button, then click **+ Add Transmission Point**. The **Add Transmission Point** dialog box is displayed.
2. Enter the following details: * **Name** – TP identifier. * **Serial Number** – (Required) The TP equipment's vendor assigned serial number. * **Antenna Gain (dBi)** – (Required) Antenna RF gain value in dBi. Enter an integer value less than or equal to 128. * **Max Pwr (dBm)** – (Required) Maximum transmit power in dBm. Enter an integer value in the range of 0–30. 3. To save the TP, click **Save**. 4. To add additional TPs, repeat Steps 1–3. * **To bulk provision TPs:** 1. Select the **Upload CSV** radio button, then click **Upload CSV**. 2. Select the csv file to upload and submit it. For more information, see [*Bulk Provision TPs*](#bulk-provision-tps). * TP table: Empty unless at least one TP has already been added. * **Name** – TP identifier. * **Serial Number** – The TP equipment's vendor-assigned serial number. * **Antenna Gain** – RF gain value in dBi for each antenna. * **Max Pwr** – Maximum transmit power in dBm for each TP. * **Actions** – Options to edit and delete TPs. {% endstep %} {% step %} To save the DAS, in the upper-right corner of the screen, click **Save DAS**. {% endstep %} {% endstepper %} ## Edit DAS This section describes how to edit a DAS. {% hint style="info" %} NOTE: You can edit DAS only if you are a GXC Administrator, Partner Administrator, Super Administrator, or an Administrator. {% endhint %} {% hint style="info" %} NOTE: Editing an active DAS may cause service interruption. Changes to TPs, power settings, or registration parameters will require the TPs to re-register with the SAS and obtain new grants. During this process (typically 5–10 minutes), the DAS system will not provide coverage. Schedule configuration changes during maintenance windows when possible. {% endhint %} **To edit a DAS:** {% stepper %} {% step %} In the navigation pane, click **Equipment** > **DAS** tab. The **Equipment** page > **DAS** tab displays the summary details of all DAS configured in the network. {% endstep %} {% step %} For the DAS equipment that you want to edit, in the **Actions** column, click the corresponding ⋮ (options) icon, then click **Edit**.
The **Edit DAS *****\*** page displays the DAS equipment's details.
{% endstep %} {% step %} Edit the following details as required: * **Venue** – (Required) The venue hosting the DAS equipment. * **Name** – (Required) The DAS equipment's name. * **Serial Number** – (View-only) The DAS equipment's vendor-assigned hardware serial number. * **Description** – (Required) Enter notes or details about the DAS equipment or the deployment. * **Device Class** – (Required) The DAS equipment's type/model. * **Wilson DAS** – Wilson Electronics-manufactured DAS equipment with pre-configured specifications. * **Generic DAS** – Third-party DAS equipment requiring manual configuration. {% endstep %} {% step %} At the lower-right corner of the page, click **Configure Transmission Points**. {% endstep %} {% step %} Enter the following details: * **User ID** – Unique identifier for registering with the SAS. * **Registration Type** – (Required) The CBSD registration process type. * **FCC ID** – The Federal Communications Commission identifier for the equipment. * Add TP: * **To add one TP at a time:** 1. Select the **Manual Add** radio button, then click **+ Add Transmission Point**. The **Add Transmission Point** dialog box is displayed.
2. Enter the following details: * **Name** – TP identifier. * **Serial Number** – (Required) The TP equipment's vendor assigned serial number. * **Antenna Gain (dBi)** – (Required) Antenna RF gain value in dBi. Enter an integer value less than or equal to 128. * **Max Pwr (dBm)** – (Required) Maximum transmit power in dBm. Enter an integer value in the range of 0-30. 3. To save the TP, click **Save**. 4. To add additional TPs, repeat steps 1–2. * **To bulk provision TPs:** 1. Select the **Upload CSV** radio button, then click **Upload CSV**. 2. Select the CSV file to upload and submit it. 3. For more information, see [*Bulk Provision TPs*](#bulk-provision-tps). * TP table: Empty unless at least one TP has already been added. * Edit TP: 1. Click the corresponding (edit) icon.\ The **Edit Transmission Point** dialog box is displayed.
2. Edit the TP's details and click **Save**. * **Name** – TP identifier. * **Serial Number** – (Required) The TP equipment's vendor assigned serial number. * **Antenna Gain (dBi)** – (Required) Antenna RF gain value in dBi. Enter an integer value less than or equal to 128. * **Max Pwr (dBm)** – (Required) Maximum transmit power in dBm. Enter an integer value in the range of 0–30. * Delete TP: Click the corresponding (delete) icon. {% endstep %} {% step %} To save your edits, in the upper-right corner of the screen, click **Save DAS**. {% endstep %} {% endstepper %} ## Associate/Disassociate DAS with AP This section describes how to associate or disassociate a DAS with an AP. {% hint style="info" %} **NOTE:** You can associate or disassociate DAS with AP only if you are a GXC Administrator, Partner Administrator, Super Administrator, or an Administrator. {% endhint %} {% hint style="info" %} **NOTE:** A DAS can be associated only with GXC G501 APs configured in either Single Carrier mode or Carrier Aggregation mode. All TP operations are coordinated through that AP. {% endhint %} **On associating a DAS with an AP:** 1. All TPs register with SAS as individual CBSDs. 2. Grant requests are submitted for each TP. 3. System becomes operational once all TPs are authorized. Process typically takes 5-10 minutes. **On disassociating a DAS with an AP:** 1. All SAS grants are immediately released. 2. TPs cease transmission. 3. DAS configuration is preserved but becomes inactive. 4. Re-association requires full re-registration of all TPs. **To associate/disassociate a DAS with an AP:** {% stepper %} {% step %} In the navigation pane, click **Equipment** > **Access Point** tab. The **Equipment** page > **Access Point** tab displays the summary details of all APs configured in the network. {% endstep %} {% step %} For the AP that you want to edit, in the **Actions** column, click the corresponding ⋮ (options) icon, then click **Edit**.
The **Edit Access Point** page > **Access Point** tab is displayed. {% endstep %} {% step %} Navigate to the **RAN** tab.
{% hint style="info" %} NOTE: When associating with a DAS, verify the following AP prerequisites:\ **Device Class** – Must be set to G501\ **Carrier Mode** – Must be set to Single Carrier mode or Carrier Aggregation mode {% endhint %} {% endstep %} {% step %} Associate/disassociate a DAS. * To associate a DAS: * Toggle the **DAS** switch to ON position. The **Select DAS** dropdown becomes enabled. * In the **Select DAS** dropdown, select the DAS to associate with this AP. {% hint style="info" %} NOTE: The **Select DAS** dropdown lists only DAS equipment that is not currently associated with another AP. If no DAS is available, the dropdown is disabled. {% endhint %} * To disassociate a DAS: * Toggle the **DAS** switch to the OFF position. The **Select DAS** dropdown becomes disabled. {% endstep %} {% step %} To save your changes, in the upper-right corner of the screen, click **Save Access Point**. On associating a DAS, the selected DAS receives cellular signal from this AP and distributes it to all configured TPs. On disassociating a DAS, the DAS no longer receives signal from this AP. {% endstep %} {% endstepper %} ## **Delete DAS** {% hint style="info" %} NOTE: You can delete DAS only if you are a GXC Administrator, Partner Administrator, Super Administrator, or an Administrator. {% endhint %} {% hint style="info" %} NOTE: You cannot delete a DAS while it is associated with an AP. If a DAS is associated with an AP, you must disassociate it before you can delete it. See [*Associate/Disassociate DAS with AP*](#associate-disassociate-das-with-ap). {% endhint %} **To delete a DAS:** {% stepper %} {% step %} In the navigation pane, click **Equipment** > **DAS** tab. The **Equipment** page > **DAS** tab displays the summary details of all DAS configured in the network. {% endstep %} {% step %} For the DAS that you want to delete, in the **Actions** column, click the corresponding ⋮ (options) icon, then click **Delete**.
A confirmation dialog box is displayed.
{% endstep %} {% step %} To confirm deleting the DAS, 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-das.md?ask=&goal= ``` `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.