BN - Device Setup

After logging in to the BN web UI, the device setup is displayed. This provides a summary of the current configuration. Changes may also be made here. 

The Hostname of the device is listed at the top. The Hostname being in green text indicates the device is connected to TCS. An alarm icon in the top right corner will change to red to indicate active alarms that may require attention. 

Configuration information is displayed and updated in the main screen. The following configuration options are available:

  • System: Required device information

    • Hostname: The configurable name of the device.

    • Operator ID: The operator ID. BNs and RNs must share the same Operator ID in order to connect.

    • Carrier 0 Frequency: Frequency for the carrier 0 radio in MHz.

    • Carrier 1 Frequency: Frequency for the carrier 1 radio in MHz.

    • Country: The regulatory domain in which the radios operate. The regulatory domain determines available channels and transmit power.

  • Data: Specifies the data port

    • Interface: Use the drop-down menu to select which physical port (Data1, Data2, Data3) will be used for data transmission.

    • Data VLAN: All data on the data interface is tagged with the specified VLAN. The default data VLAN is 2000 with allowed values being 2-4091.


      The following VLANs are reserved and not available for use: 4092, 4093, 4094

  • In-Band Management: Specifies configuration for the in-band management port

    • IP/Prefix: The IP address and subnet mask. The subnet mask must be in CIDR notation, e.g., /24. An IP address may only be manually entered if Enable DHCP is set to Disabled.

    • Management VLAN: If used, all traffic on the in-band management port is tagged with the specified VLAN. A management VLAN may only be entered manually if Tagged Management is set to Enabled.

    • Note: The in-band management VLAN must be different from the data VLAN.

    • Enable DHCP: Use the toggle to enable or disable DHCP.

    • Tagged Mgmt: Use the toggle to enable the manual assignment of a management VLAN.

  • Out-of-Band Management: Optionally used to configure the out-of-band management port

    • IP/Prefix: This sets the IP address and subnet mask. The subnet mask must be in CIDR notation, e.g., /24. An IP address may only be manually entered if Enable DHCP is set to Disabled.

    • Enable DHCP: Use the toggle to enable or disable DHCP.


      DHCP should not be enabled for both in-band and out-of-band management and VLAN tagging is not available for out-of-band management.

  • Network/Services: Other network services

    • Mgmt Default Gateway: This sets the default gateway for the device.

    • NTP Server(s): By default, the NTP Server is blank and not used because the BN uses GPS for synchronization. However, if needed for lab testing (when the BN does not have a view of the sky for GPS synchronization, configure an NTP server using an IP address or FQDN.

    • DNS Server IP(s): This specifies the Domain Name Servers (DNS) used to resolve the TCS URL. Servers must be entered as IP addresses.


  1. The following information is reserved on the BN and may not be used as part of the configuration:

    1. Reserved VLANs: 4092, 4093, and 4094

    2. Reserved IP subnets:,

  2. The Data VLAN (required) and the Management VLAN (optional) are on the data port and must be separate VLANs.

  3. On the switch north of the BN, the IP subnet associated to the Data VLAN ingressing to the BN’s data port must be different from the In-band Management IP subnet.  For more information about VLANs in a G1 network, see the VLAN appendix in the G1 Admin Guide.

  4. Out-of-band management is optional.  If used, it must use a different IP subnet as In-band management.

  5. DHCP cannot be used for both In-band and Out-of-band management IP addresses.

  6. The following IP ports must be open in order to allow the BN to reach TCS:

    1. 443 (TCP for HTTPS)

    2. 53 (UDP for DNS)

    3. 123 (UDP for network time)

  7. The web UI should not be used for configuration changes once the initial deployment has been completed.  Configuration settings in TCS will overwrite web UI settings.  To avoid confusion or incorrect settings being applied, use TCS for configuration once the device is registered and connected to TCS.

If any changes have been made, click Save Config. New configuration settings are not used until Apply is clicked or the system is rebooted.


For CBRS installations, the Cloud URL should be changed to:


Figure 126: BN Configuration Setup

Click Installation Parameters to verify those values and enter your CPI ID. Until this happens, the BN will not be able to access the spectrum.


Figure 127: CBRS BN Configuration

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.