Step 2 of 4. BN - Initial Configuration

For initial configuration, use a Harting Push-Pull Ethernet cable assembly plugged into the MGMT port on the BN.


Using a standard Ethernet cable in this port will make removing the cable difficult and could damage the port.

Harting Ethernet cable assemblies for this purpose are available through Tarana.

Upon receiving power, the BN will undergo the booting and initialization process for a period of 5-7 minutes. There are a set of LEDs on the bottom edge of the BN that will cycle through patterns and colors during this time.

For more information about LED behavior in BN - LED Light Status


DATA1 and DATA2 are optical SFP+ interfaces. Devices connected to these data ports must support SFP+ (10Gbps) or the ports will not come up. Tarana offers an industrial-temperature SFP+ module for data connection at the BN on the tower. This SFP+ module is MEF certified with an extended temperature range of -40° to +85°C. DATA3 is a copper interface and only supports 1Gbps. Devices connected to DATA3 must be Gigabit Ethernet or the port will not come up.


Only one of the three data ports can be active at a time.

The BN communicates to TCS through one of the data ports. The MGMT port is for initial configuration. Optionally this port can be used for on-site management, also called Out of Band (OOB) management.


Accessing the MGMT Port

  1. Connect a laptop to the MGMT Gigabit Ethernet port of the BN.

  2. On the laptop, assign a static IP address in the same subnet as the default IP of the MGMT port. The example below uses with a subnet mask of

  3. The MGMT port has a default IP of with no VLAN. Type into a web browser to access the BN’s web interface.


    Note: Chrome is the recommended and supported browser.

  4. Enter the default login and password of “admin” and “admin123”, respectively. This will bring up the BN’s web interface.


    A management IP can also be assigned statically or by a DHCP server if there is a DHCP server on the network.

    DHCP is not enabled by default and must be enabled through the BN’s web UI. DHCP cannot be enabled for both the in-band management and out of band management interfaces.



The following is for the 5GHz BN. For CBRS BN configuration, see BN - CBRS Installations.

From the BN’s web UI the following information needs to be configured:

  1. For in-band management (on one of the data ports), enter a static IP within the subnet of the LAN gateway or enable DHCP to have a DHCP server give the BN an IP address.


    If DHCP is enabled for the in-band management IP Address, it cannot be used for the out-of-band management address.

  2. Configure a management VLAN on the data port (optional, but this is a good practice).

  3. Configure the Data VLAN on the data port (required).


    The BN’s data ports (DATA1, DATA2, DATA3) require ingressing and egressing data frames to be tagged (802.1q). By default, the BN will tag egressing data frames with VLAN 2000. Arriving frames sent from the network router to the BN’s data port must therefore also be tagged with this VLAN number. The default Data VLAN can be changed via the BN’s web UI, as seen in below. For more information about using VLANs in a G1 network, see VLANs and Quality of Service.

  4. Enter the Mgmt Default IP gateway. This is the gateway for the in-band management IP address configured in Step 1.

  5. 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.

  6. Verify the connection to TCS by confirming the Hostname appears in green text at the top of the screen.


Important Notes:

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

    • Reserved VLANs: 4092, 4093, and 4094

    • Reserved IP subnets:,

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

  • 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 VLANs and Quality of Service.

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

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

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

    • 443 (TCP for HTTPS)

    • 53 (UDP for DNS)

    • 123 (UDP for network time)

  • 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.

Unmute Radios

  1. Click "Radio Control" --> Up


    For safety, the radios are muted by default. After verifying functionality, mute the radios again until after the BN is installed on site.

  2. Click Save Config.


TCS Confirmation

To verify the BN is accessible from the Tarana Cloud Suite (TCS), use an Internet connection external to the BN.


The BN communicates to TCS across Data Port 1, 2, or 3. One of those ports must be connected to the Internet for the BN to contact TCS. Remember that Data Ports 1 and 2 are 10 Gbps only. Data Port 3 is 1 Gbps only.

  1. Login to Tarana Cloud Suite (TCS) using the URL: For the username and password, contact your TCS system administrator.

  2. From the left column, click on Devices > List.

  3. Verify that “BN” is selected from the RN/BN switch.

  4. Finally, verify the BN is online as indicated by its Serial Number being in green text.



    If the BN does not appear in the Devices > List page, it may not have been assigned to a Sector in TCS. Under Admin > Network Configuration, check if this BN is in the BN Devices: Unassigned folder. The BN must be assigned to a Sector before an RN will associate to it. A TCS user with OP Admin role rights is required for this step.

    For more information on Network Configuration, see TCS Network Configuration.

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



Article is closed for comments.