BLiNQ Networks

FW-300i Intelligent LTE Base Station

User Manual

Release 2.0
Issue 02
July 2019
BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Revision History
DATE RELEASE ISSUE REASON FOR ISSUE
November 2018 Release 1.0 Issue 01 Initial Release
June 2019 Release 2.0 Issue 01 Launching new WebUI
July 2019 Release 2.0 Issue 02 Update default frequency/EARFCN

Contact Information:
BLiNQ Networks (CCARI)
140 Renfrew Drive, Suite 205
Markham, ON L3R 6B3

Web Site:
http://www.blinqnetworks.com

Sales Inquiries:
Email: [email protected]
Telephone: 1-416-214-4204

Customer Support:
Email: [email protected]
Telephone: 1-416-214-4204

Confidential - Restricted Use and Duplication i Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Table of Contents

1 About This Manual ..................................................................................................................1

1.1 Manual Conventions...................................................................................................................... 2
2 FW-300i System Overview .......................................................................................................3
2.1 Technical Features ......................................................................................................................... 4
2.2 Network Management Features ................................................................................................... 6
2.2.1 FW-300i Security Protocols.................................................................................................... 8
2.2.1.1 Local Networking Protocols ........................................................................................... 8
3 Technical Specifications ..........................................................................................................9
3.1 System Parameters ...................................................................................................................... 10
3.2 System Enclosure......................................................................................................................... 12
3.3 Antenna Patterns......................................................................................................................... 13
4 Getting Started with the FW-300i .......................................................................................... 14
4.1 FW-300i Web User Interface (WebUI)......................................................................................... 15
4.1.1 Common Tools ..................................................................................................................... 17
4.1.1.1 Title Bar: Tool Area....................................................................................................... 17
4.1.1.2 Minimized and Maximized Menus ............................................................................... 18
4.1.1.3 System Information Bar ............................................................................................... 18
4.1.2 System Status Messages ...................................................................................................... 18
4.2 Default FW-300i Configuration.................................................................................................... 20
5 Configuration ........................................................................................................................ 21
5.1 System Configuration Process ..................................................................................................... 22
5.2 Configuration with the WebUI .................................................................................................... 23
5.2.1 System.................................................................................................................................. 23
5.2.1.1 Configuring a System Name ......................................................................................... 24
5.2.1.2 System Synchronization ............................................................................................... 24
5.2.1.3 Network Connectivity Parameters ............................................................................... 26
5.2.1.4 Advanced Options ........................................................................................................ 27
5.2.2 Carriers................................................................................................................................. 29
5.2.2.1 Setting up Carriers Baseline Parameters...................................................................... 29
5.2.2.2 Set Cells 0-2 RF Parameters ......................................................................................... 30
5.2.2.3 Advance Option............................................................................................................ 33
5.2.3 LTE Baseline ......................................................................................................................... 34
5.2.3.1 Configuring LTE Baseline Parameters .......................................................................... 35
5.2.3.2 eNB Identifiers ............................................................................................................. 39
5.2.3.3 EPC Settings.................................................................................................................. 39
5.2.3.4 Advanced Options ........................................................................................................ 40

Confidential - Restricted Use and Duplication ii Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.2.4 CBSD ..................................................................................................................................... 43

5.2.5 Management........................................................................................................................ 45
5.2.5.1 SSH/Web Users ............................................................................................................ 45
5.2.5.2 Syslog............................................................................................................................ 48
5.2.5.3 SNMP ............................................................................................................................ 49
5.2.6 Verify, Save and Activate Current Running Configuration........................................................ 54
5.2.6.1 Verify and Save Running Configuration ....................................................................... 54
5.3 Configuration with the CLI ........................................................................................................... 55
5.3.1 System.................................................................................................................................. 55
5.3.1.1 Configuring a Hostname............................................................................................... 55
5.3.1.2 Assigning IP Address..................................................................................................... 56
5.3.1.3 Setting up IPv6 Address ............................................................................................... 56
5.3.1.4 Configuring DNS Servers .............................................................................................. 56
5.3.2 Carriers................................................................................................................................. 57
5.3.2.1 Configure Channel Bandwidth and Frequency Mode .................................................. 57
5.3.2.2 Enabling Cells ............................................................................................................... 58
5.3.2.3 Set Transmit Power ...................................................................................................... 58
5.3.3 LTE Baseline ......................................................................................................................... 59
5.3.3.1 Assign the Maximum Cell Range .................................................................................. 59
5.3.3.2 Configure the Cell Identity Parameters........................................................................ 59
5.3.3.3 Assign an eNodeB ID .................................................................................................... 60
5.3.4 EPC ....................................................................................................................................... 60
5.3.4.1 Set EPC Specific Information ........................................................................................ 60
5.3.4.2 EPC Provisioning ........................................................................................................... 61
5.3.4.3 Embedded EPC ............................................................................................................. 62
5.3.4.4 External EPC ................................................................................................................. 65
5.3.5 CBSD ..................................................................................................................................... 69
5.3.6 Management via the CLI ...................................................................................................... 70
5.3.6.1 User .............................................................................................................................. 71
5.3.6.2 SNMP ............................................................................................................................ 72
5.3.6.3 Syslog Server ................................................................................................................ 73
5.3.7 Verify, Save and Activate Current Running Configuration................................................... 75
5.3.7.1 Enable Sector and Radio Transmitters ......................................................................... 75
5.3.7.2 Verify and Save Running Configuration ....................................................................... 75
5.3.8 System Synchronization ....................................................................................................... 77
6 Operation and Maintenance ................................................................................................. 79
6.1 Operation and Maintenance with the WebUI ............................................................................. 80
6.1.1 Software Upgrade ................................................................................................................ 80
6.1.1.1 System Software Upgrade............................................................................................ 80

Confidential - Restricted Use and Duplication iii Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

6.1.2 Performance ........................................................................................................................ 83

6.1.2.1 eNB Statistics Page ....................................................................................................... 83
6.1.2.2 CPE Statistics Page ....................................................................................................... 83
6.1.2.3 Trace Log Files .............................................................................................................. 84
6.1.2.4 Measurements ............................................................................................................. 86
6.1.3 Events................................................................................................................................... 88
6.1.3.1 Alarms (Logs) Page ....................................................................................................... 88
6.1.3.2 History Page ................................................................................................................. 89
6.2 Operation and Maintenance with the CLI ................................................................................... 90
6.2.1 Software Upgrade ................................................................................................................ 90
6.2.1.1 FW-300i CLI System Software Upgrade ....................................................................... 90
6.2.2 Performance ........................................................................................................................ 91
6.2.2.1 eNB Statistics................................................................................................................ 91
6.2.2.2 CPE Statistics ................................................................................................................ 92
6.2.2.3 Trace Log Files .............................................................................................................. 93
6.2.2.4 Measurements ............................................................................................................. 93
6.2.3 Events................................................................................................................................... 98
6.3 Troubleshooting ........................................................................................................................ 101
7 Customer Premise Equipment (CPE) .................................................................................... 102
Appendix A BLiNQ Wireless Devices and RF Safety/Les appareils sans fil BLiNQ et la sécurité RF .. 103
A.1 Equipment Compliance ............................................................................................................. 105
A.1.1 Federal Communications Commission (FCC) Notices ........................................................ 105
Appendix B PCI Planning Guidelines ............................................................................................ 106
Appendix C Alarms and Events (Fault Management) ................................................................... 108
Appendix D List of Acronyms ...................................................................................................... 112

List of Figures

Figure 2-1 FW-300i Mounted on a Pole ...................................................................................................... 3

Figure 2-2 FW-300i Sectors with Antenna Pattern ..................................................................................... 5
Figure 2-3 Antenna Sectors with Examples of CA Mapping ........................................................................ 5
Figure 3-1 FW-300i (back and front respectively) ..................................................................................... 12
Figure 3-2 Band 42, 43, 48 Antenna Patterns ........................................................................................... 13
Figure 3-3 Band 46 Antenna Patterns ....................................................................................................... 13
Figure 4-1 Welcome FW-300i Screen ........................................................................................................ 15
Figure 4-2 Title Bar – Tool Area Identification .......................................................................................... 17

Confidential - Restricted Use and Duplication iv Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Figure 4-3 View Maximized ....................................................................................................................... 18

Figure 4-4 FW-300i WebUI System Success Status Message .................................................................... 18
Figure 4-5 FW-300i WebUI Warning Message .......................................................................................... 19
Figure 4-6 FW-300i WebUI Error Message................................................................................................ 19
Figure 5-1 FW-300i Configuration Process................................................................................................ 22
Figure 5-2 FW-300i Sectors ....................................................................................................................... 31
Figure 5-3 EPC Topology............................................................................................................................ 61

List of Tables

Table 3-1 FW-300i System Parameters ..................................................................................................... 10

Table 4-1 FW-300i Default Configuration Values...................................................................................... 20
Table 6-1 Troubleshooting ...................................................................................................................... 101
Table C-1 List of Alarms ........................................................................................................................... 109
Table C-2 List of Events ........................................................................................................................... 111

Confidential - Restricted Use and Duplication v Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

1 About This Manual

This manual contains informational and overview chapters, and then continues as a guide to the
recommended order that you configure and then monitor your FW-300i system.
There are two methods to configure the FW-300i:
 FW-300i Web-based User Interface (WebUI) (recommended) or
 Command Line Interface (CLI)
Each chapter contains step-by-step instructions for the applicable method. Choose either the FW-300i
WebUI or the CLI method and follow the procedures under the desired chapter.
Note: If you need more information on the FW-300i WebUI or CLI, consult the separate manual:
“Complete WebUI and CLI Overview”
The WebUI menu structure is the basis for the order of the chapters and the processes contained within
those chapters:
 Initial system setup: See Chapter 4, “Getting Started with the FW-300i”
 Configuration: See Chapter 5, “Configuration” for configuring the FW-300i system using:
 WebUI; See Section 5.2, “Configuration with the WebUI” or
 Command Line Interface (CLI); See Section 5.3, “Configuration with the CLI”
 Operation and Maintenance: See Chapter 6 , “Operation and Maintenance”
 Software upgrade
 Performance containing eNB and Customer Premise Equipment (CPE) statistics plus trace log
files and measurements
 Events including alarms and past events (History)
 Troubleshooting
 Administration: See Chapter 5.2.5, “Management” (for WebUI) and Chapter 5.3.6, “Management
via the CLI”
 User operations (Local security)
 Simple Network Management Protocol (SNMP)
 Syslog server

Confidential - Restricted Use and Duplication 1 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

1.1 Manual Conventions

Bold words indicate actual page names, fields, buttons or commands within the software.
Examples:
 In the LTE Baseline Parameters section, set the Cell range to the desired kilometer range. The range
is from 1 to 100 kilometers.

 Most FW-300i WebUI pages have a Commit button in the top right hand corner.

Commit Button

 If not already there, access the device via a CLI and enter the following commands:
Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# radio rf 0
Blinq eNB(config-rf-0)# tx-power 18
Blinq eNB(config-rf-0)# top
Blinq eNB(config)# radio rf 1 tx-power 18
Blinq eNB(config)# radio rf 2 tx-power 18
Blinq eNB(config)# commit
Commit complete.
Blinq eNB(config)#

Confidential - Restricted Use and Duplication 2 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

2 FW-300i System Overview

BLiNQ Networks is a pioneer of next-generation wireless solutions that feature intelligent systems
capable of adapting to the radio frequency environment to maximize capacity and performance.

Figure 2-1 FW-300i Mounted on a Pole

The BLiNQ FW-300i system is a tri-sector and tri-carrier Long-Term Evolution (LTE) Evolved Node B (eNB)
with the capability to operate in the following bands: 42, 43, 46 and 48 (Citizens Broadband Radio
Service (CBRS)). With a distinctive feature set and integration level, the FW-300i brings an ideal solution
to an “install anywhere” micro-base transceiver station (micro-BTS) that fully serves private networks,
fixed wireless access and mobility use cases.

Confidential - Restricted Use and Duplication 3 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

2.1 Technical Features

Some of the main technical product characteristics are as follows:
 ‘All-In-One’ Fully Integrated Solution: The FW-300i solution packs a three (3) sector 180-degree
integrated antenna (60-degrees per sector) with an integrated Global Positioning System (GPS) sync
source. There is also an additional option for an integrated Evolved Packet core (EPC), making
deployment of the FW-300i as simple as deploying Wi-Fi.
 Compact All-Outdoor and Zero-Footprint Form Factor: The FW-300i packs three (3) carrier radios in
one compact form. The FW-300i meets IP67 requirements for operation in tough environments with
the capability to handle temperature variations from extreme cold to extreme heat. BLiNQ’s state-
of-the-art and unique mounting design allows an unobtrusive deployment of multiple FW-300i
systems on towers, poles, building sidewalls or rooftops with ease (See the “FW-300i Installation
Guide” for more details).
 For CBRS Band: The FW-300i implements a native Spectrum Access System client that fully enables
easy Citizens Broadband Radio Service (CBRS) deployments. With each cell designed to operate as
an independent Type B CBSD, the FW-300i can operate on a Priority Access or General Authorized
Access basis in the CBRS band consistent with Title 47 CFR Part 96.
 Industry Standard TDD LTE-A Release 13 Radio Interface: The FW-300i solution utilizes industry
standard Time Division Duplexing (TDD) LTE-A Release 13 radio capabilities. This allows for robust
wireless performance, with extremely cost-effective deployments of Customer Premise Equipment
(CPE).
 Configuration: The FW-300i supports all LTE TDD frame configurations but focuses on Category 1
and Category 2.
 Carrier Aggregation: The FW-300i supports carrier aggregation (CA) with up to three (3) Component
Carriers (3CC), allowing for increased throughput to support high bandwidth deployments in both
dense suburban and rural environments.
 Software Controlled Adaptive Carrier Steering: The FW-300i is able to steer, with variable capacity,
over different areas across 180 degrees of azimuth. The unit powers this steering ability by its
integrated antenna system of three (3) sectors of 60 degrees each. This flexibility allows the FW-300i
to support both large coverage models, as well as capacity driven models. The FW-300i supports
three modes via software (SW) configuration:
 3 Sector covering 180 degrees each of 1 x 20 MHz carrier
 2 Sector covering 120 degrees (one sector with 2 x 20 MHz carriers and one sector with 1 x
20MHz carrier)
 1 Sector covering 60 degrees: one sector with 3 x 20 MHz carriers

Confidential - Restricted Use and Duplication 4 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Figure 2-2 FW-300i Sectors with Antenna Pattern

3 Sector 2 Sector 1 Sector

Figure 2-3 Antenna Sectors with Examples of CA Mapping
 Multiple Input Multiple Output (MIMO): The FW-300i system features standard 2x2 MIMO
configurations in both downlink (DL) and uplink (UL) directions for each active sector.
 High Modulation and Coding Scheme (MCS): The FW-300i hardware supports high MCS:
 Downlink (DL): 256 Quadrature Amplitude Modulation (QAM) and
 Uplink (UL): 64 QAM
Please refer to the latest SW release notes for the availability of these features.

 Quality of Service (QoS): The FW-300i system implements advanced features such Traffic
Classification, Admission Control, Rate Shaping plus Active Scheduling and Queue Management in
order to deliver the most optimal quality of service.

Confidential - Restricted Use and Duplication 5 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

2.2 Network Management Features

The FW-300i implements complete web-based user interface (WebUI) and Command Line Interface (CLI)
functionality, plus strong Element Management System (EMS) implementation that suits any type of
customer needs.
 FW-300i Web Interface (WebUI) — Accessible via HTTP(S), the FW-300i WebUI provides an
interactive visual toolset that allows you to modify the full configuration of the FW-300i system, as
well as view state, fault and performance indicators. The FW-300i WebUI displays performance data
using visual charts and provides applications to visualize up to 24 hours of historical performance
data stored on the system.
 FW-300i Command Line Interface (CLI) — Accessible via Secure Shell protocol (SSH), the FW-300i CLI
provides a well-structured command language in an industry standard idiom. The interface allows
you (or third-party system) to manipulate the full configuration of the unit and examine state,
performance and fault indicators.
 Element Management System (EMS) — The BLiNQ EMS system, powered by the robust Web
Network Management System (WebNMS) platform, enables a state-of-the-art Operations,
Administration, Maintenance and Provisioning (OAM&P) feature set. The OAM&P possesses a
strong set of interfaces to connect to northbound provision systems.
Providing comprehensive Fault, Configuration, Accounting, Performance, and Security (FCAPS)
functionality, the FW-300i system uses standard networking protocols and tools that facilitate a full
range of element and network management operations—from local craft configuration, to complex
integration in Simple Network Management Protocol (SNMP) or script-based Element Management
System (EMS) and Operations Support System (OSS) infrastructures.
 Community-Based Simple Network Management Protocol version 2 (SNMPv2c) and SNMP version
3 (SNMPv3) — The SNMPv2c and SNMPv3 interfaces provide complete access to configuration,
state, performance and fault information in the FW-300i system. This allows for high levels of
integration in existing EMS/OSS infrastructure for monitoring, Service Level Agreement (SLA)
assurance and administrative task automation.
 Syslog — The syslog interface allows the FW-300i system to send standard syslog fault management
information (that is, syslog alarms, events and log entries) to external syslog servers.
All network management interfaces on the FW-300i system are accessible via Transmission Control
Protocol/Internet Protocol (TCP/IP) and User Datagram Protocol/IP (UDP/IP). The FW-300i system
provides the following IP addresses for management purposes:
 Local Craft IP Address — A fixed, non-routable IP address: 169.254.1.1 which is always accessible
without VLAN encapsulation. This address is always present on eNodeB modules. You use this
address in situations where the Management IP Address (see below) is not configured or is
unavailable, including initial commissioning and field troubleshooting scenarios. Typically, a
technician accesses the Local Craft IP Address by plugging directly into the RJ45 Ethernet port of the
module.
 WAN IPv4 IP Address — A user assigned, static or Dynamic Host Configuration Protocol (DHCP) IPv4
address. The device uses this IPv4 address to exchange traffic and control information with the
network. The operator will use this IPv4 address to remotely manage the system. A user-
configurable Virtual Local Area Network (VLAN) encapsulates all traffic to and from the WAN
interface.

Confidential - Restricted Use and Duplication 6 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

The FW-300i system provides the following network management functions:

 Configuration Management — The system configuration covers several functional areas:
 Radio Link Commissioning
Radio Link Commissioning parameters (for example, radio frequency, synchronization, TDD
configuration) needs to be set before system deployment and are particular to the operator RF
network.
 EPC Configuration
The Evolved Packet Core (EPC) Configuration parameters configure the EPC interface (e.g. Public
Land Mobility Network Identifier (PLMN-ID), Mobility Management Entity (MME) interface,
Serving Gateway (SGW) interface).
 Security Configuration
Security Configuration parameters allow you to secure access or disable specific management
interfaces (add local user accounts) and perform various unit administrative operations.
 EMS Interfaces Configuration
Element Management Systems (EMS) enables you to configure SNMP, Syslog, plus the
automatic upload of Performance Management (PM) files.
All parameters in these areas are accessible via all of the network management interfaces previously
described.
 Fault Management — The FW-300i system provides fault management service via a comprehensive
list of alarms and events. Some of the potential faults that the system detects and initiates alarms
on include:
 radio and Ethernet link failures
 hardware module failures
 synchronization faults
 software module faults
SNMP traps or Syslog relays all alarms and events to higher level managers. The system also allows
you to access active alarm and event history information using either the FW-300i CLI or WebUI.
 Performance Management — The FW-300i system maintains a comprehensive set of performance
counters and indicators to facilitate:
 performance monitoring
 Service Level Agreement (SLA) monitoring
 troubleshooting
The system provides a full set of Ethernet counters at the interface, module and service flow level,
as well as radio quality indicators at the module level. The system makes all the counters available
as either instantaneous values (via SNMP, CLI or WebUI) or historical performance files. The system
maintains 24 hours of performance data at a 15 minute granularity. The eNodeB only stores
performance files and can be extracted from the system on-demand.

Confidential - Restricted Use and Duplication 7 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 Administrative Operations — The FW-300i system provides tools that allow you to perform all
standard unit administration operations using the provided remote network management
interfaces. The system supports remote software upgrade operations using either a pull paradigm
(that is, the system modules retrieve the software package files from external FTP servers) or a push
scheme using the FW-300i WebUI (that is, you upload a software package file to the system modules
using the FW-300i WebUI). The FW-300i system also supports remote configuration backups and
backup restoration.

2.2.1 FW-300i Security Protocols

The FW-300i system supports local security access regarding system configuration and maintenance.
With this model, you can, through CLI or WebUI, configure the user name, password and access level for
the user. The configuration is stored on the FW-300i.

2.2.1.1 Local Networking Protocols

Local security protocol is the default protocol for the FW-300i modules. This means that you set each
username, password and access level on each module. Each module stores the configuration data in its
configuration database.
To configure the local security:
 with the WebUI see Section 5.2.5.1, “SSH/Web User” or
 with CLI, see Section 5.3.6.1, “User”.

Confidential - Restricted Use and Duplication 8 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

3 Technical Specifications
This chapter covers:
 System Parameters,
 System Enclosure and
 Antenna Patterns.

Confidential - Restricted Use and Duplication 9 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

3.1 System Parameters

Table 3-1 lists the FW-300i system parameters for the North American (NA) product line.
Table 3-1 FW-300i System Parameters

RADIO SPECIFICATIONS
Frequency Band TDD LTE Bands: 42, 43, 48, 46
Transmit Power (Bands 42, 43, 48) Maximum 33 dBm per sector of 60 degrees (deg)
17 dBi Integrated Antenna  50 dBm EIRP/Sector
Transmit Power (Band 46) Maximum 26 dBm (Typically (Typ.) 19 dBm) per each 60 deg sector
17 dBi Integrated Antenna  36 dBm EIRP/Sector
Channel Bandwidth 10, 20 MHz
MIMO 2TX x 2RX (several possible MIMO configurations)
LTE Compliance 3GPP Release 10 (SW upgrade to Release 13)
PERFORMANCE AND ATTRIBUTES
Connected/Active User Equipment (UE) Up to 96 active users per sector; 288 active users per box
Carrier Aggregation Supports contiguous and non-contiguous 1CC, 2CC, 3CC, covers full
CBRS band (150 MHz)
Throughput DL TDD 3GPP Release 10 (Software (SW) upgrade to Release 13)
Throughput UL TDD 3GPP Release 10 (SW upgrade to Release 13)
Operating Mode TD-LTE
Power Consumption (Band 46) 80 Watts (W) maximum
Power Consumption (Band 42, 43, 48) 150 W maximum
Power 48 VDC
Connectivity Default: 1 x Copper 1000BaseT; Optional: 1 x SFP
Synchronization Integral GPS antenna (GPS, GLONASS, BeiDou),
Optional: External GPS, 1588v2
Citizens Broadband Radio Service (CBRS) CBSD Type B SAS Support
Embedded Evolved Packet Core (EPC) Software Option
OPERATIONS, ADMINISTRATION AND MAINTENANCE (OAM)
Configuration WebUI/CLI, radio and Ethernet performance monitoring
EMS Integration SNMP v2c/v3
OAM Protocols NETCONF, HTTP(S), TCP/IP, UDP, (S)FTP, SSH, TR-069/TR-196
ANTENNA SPECIFICATIONS CBRS BANDS 42/43 (48)
Gain 17 dBi
Azimuth Coverage (-5 dB) 180 degrees
Azimuth Beamwidth (-3 dB) 45 degrees
Azimuth Beamwidth (-5 dB) 60 degrees
Elevation Beamwidth (-3 dB) 10 degrees
Electrical Downtilt 0 degree

Confidential - Restricted Use and Duplication 10 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

ANTENNA SPECIFICATIONS CBRS BANDS 42/43 (48) (CONT.)

Azimuth Sidelobe < -25 dB (Typ.)
Front-to-Back Ratio @180 Degrees > 30 dB (Typ.)
Co-Polar Port-to-Port Isolation 15 dB (Typ.)
Cross-Polarization Port-to-Port Isolation > 20dB (Typ.)
Max. Voltage Standing Wave Ratio (VSWR) 1.5:1
Polarization Dual Pol 45 degrees
Lightning Protection DC Ground
MECHANICAL
Dimensions (L x W x D) 13.78" x 22.4" x 8.9" (350 x 570 x 227 mm)
Survival Wind Speed > 124 mph (200 km/hour)
Weight 26.5 lbs. (12.0 Kg)
Operational Temperature -40 to 60 degrees Celsius (-40 to 140 degrees Fahrenheit)
Mechanical Uptilt/Downtilt 0 - 10 degrees

Confidential - Restricted Use and Duplication 11 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

3.2 System Enclosure

The enclosure for the FW-300i is a rugged IP67 casing, supplied with an optional mounting bracket with
both horizontal and vertical tilt capabilities to mount the unit on towers, poles and building side walls.
These cases allow for full flexibility in the range of orientation to establish best connectivity between the
FW-300i and Customer Premise Equipment (CPE).

Figure 3-1 FW-300i (back and front respectively)

The mechanical enclosure for the FW-300i has an integrated antenna. There are two ports on the
bottom of the FW-300i: a -48VDC power port and an Ethernet port for network connectivity. The
Ethernet port comes pre-populated with 1 Gbps (100 Base-T) copper Small Form-factor Pluggable (SFP).
If needed, you can replace this SFP with 1 Gbps fiber SFP.
An integrated Global Positioning System (GPS) antenna is included in the FW-300i antenna, yet if
needed, the FW-300i has a SYNC port, to use for example, as an optional external GPS Pulse per Second
(PPS) source. Therefore, there is no need for additional synchronization equipment which reduces total
cost of ownership.

Confidential - Restricted Use and Duplication 12 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

3.3 Antenna Patterns

The FW-300i covers up to 180 degree of azimuth which is powered by an integrated adaptive antenna
system of 3 x 60 degree sectors. Following are the antenna patterns for Band 42, 43, 48 and then by the
antenna patterns for Band 46.

Figure 3-2 Band 42, 43, 48 Antenna Patterns

Figure 3-3 Band 46 Antenna Patterns

Confidential - Restricted Use and Duplication 13 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

4 Getting Started with the FW-300i

To initially log in to the FW-300i:

Notes:
 If required, consult the “FW-300i Installation Guide” for instructions on powering the unit.
 Connect your computer directly to the FW-300i through an Ethernet cable, and then check your
connectivity by pinging the FW-300i using 169.254.1.1 (the Craft IP address that is always
accessible).
Note: You need to statically set the IP address on the computer to 169.254.1.x subnet before
pinging.
After successfully pinging the Craft IP address:
 Use a Secure Shell (SSH) client to log on to the FW-300i CLI using a SSH connection to the pinged
169.254.1.1 address. However, you must install SSH version 2.0 or higher client software on your
host computer (you can use SSH version 1.0, but it is not recommended), or
 Open a web browser and navigate to the pinged 169.254.1.1 to bring up the FW-300i WebUI
When prompted for login credentials, enter the default username and password: admin/admin.
To complete the initial system setup, choose either the WebUI or the CLI method and follow the
procedures under the desired chapter.

Confidential - Restricted Use and Duplication 14 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

4.1 FW-300i Web User Interface (WebUI)

On initial log in to the FW-300i Web User Interface (WebUI), you see an overview of the FW-300i details;
BLiNQ refers to these FW-300i details as the Dashboard. Figure 4-1, Welcome FW-300i Screen identifies
the various elements of the FW-300i WebUI.

Title Bar: Tool Area

Dashboard
Navigation
Bar
Increase
Width Button

System
Information Bar
Figure 4-1 Welcome FW-300i Screen
The dashboard gives you the summary of your system. This is the first page that you will land on after
you log into the WebUI.
It shows you the System Overview, which includes the System Name, Device Code, Serial Number,
Software Version, Operational Status just to name a few.

There are two tabs at the bottom: Alarms and LTE Cells Status

Confidential - Restricted Use and Duplication 15 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 Alarms: Errors on your system will appear in this section, giving you the Alarm ID, Alarm Time,
Component, Severity, Type, Probable Cause and Description of the error.

 LTE Cells Status: This is where you can monitor the LTE Cells’ operational parameters.

Confidential - Restricted Use and Duplication 16 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

4.1.1 Common Tools

Following are some common features of the FW-300i WebUI.

4.1.1.1 Title Bar: Tool Area

Most FW-300i WebUI pages have either a Commit button or a Refresh button or both in the top right
hand corner.

Copy Running Configuration to Start-Up Configuration Button Sign Out Button

User Name Identification

Reboot Button
Refresh Button
Collapse Menu
Commit Button
Button

Figure 4-2 Title Bar – Tool Area Identification

 Commit button: If you change any settings on a page, select Commit before navigating to another
page to save your changes.
 Refresh button: Updates any read-only data on a page or returns any altered settings to their
original values.
 Copy Running Configuration to Start-Up Configuration button ( ): Makes any configuration
changes persistent over system reboots.
 Reboot button ( ): Reboot the FW-300i, at any time. It is available at the top of every page.
Note: Before a reboot, the FW-300i system performs a verification check between the running
configuration and the startup configuration to determine if there are any changes. This is to prevent
the loss of any changes. If there is a change, the system prompts you to save your changes.
 Sign Out button: Ends each session.
 Collapse Menu button ( ): Minimizes the Dashboard Navigation Bar on the left side. You can still
access the menu by positioning your cursor over the thin visible portion of the Dashboard
Navigation Bar. Select the Collapse Menu button again to make the menu visible again.

Confidential - Restricted Use and Duplication 17 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

4.1.1.2 Minimized and Maximized Menus

When a plus sign (+) is present beside a menu title, this indicates that you can minimize/maximize this
area to reduce or see more options. To maximize an area, select the plus sign (+); the area expands so
that all options are visible. To minimize, select the minus sign (-); the menu closes.

Maximized

Figure 4-3 View Maximized

4.1.1.3 System Information Bar

The FW-300i system displays the model number, serial number, software version and current license (if
applicable) status/number along the bottom of each main page. For example:

4.1.2 System Status Messages

The FW-300i WebUI outputs the following types of real-time messages to report on the interaction
and/or change results between you and the FW-300i system:
Success Message (Green):
 A Success message in green advises, for example, of a successful data or configuration change.
 Success messages automatically disappear after about 4 seconds. You can dismiss them earlier by
clicking on the message.

Figure 4-4 FW-300i WebUI System Success Status Message

Confidential - Restricted Use and Duplication 18 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Warning Message (Yellow):

 A Warning message in yellow usually cautions of a validation error. For example, if there are
problems with entered data, then a Warning message in yellow appears to explain the issue.
 You must click on a Warning message to dismiss it. They do not disappear automatically.

Figure 4-5 FW-300i WebUI Warning Message

Error Message (Red):
 An Error message in red usually advises, for example, when the server is returning an error.
 Error messages signify syntactical issues (or a required field being left empty) with the settings you
are trying to commit.
 You must click on an Error messages to dismiss it. They do not disappear automatically.

Figure 4-6 FW-300i WebUI Error Message

Confidential - Restricted Use and Duplication 19 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

4.2 Default FW-300i Configuration

The following table contains the FW-300i default configuration:
Table 4-1 FW-300i Default Configuration Values

CONFIGURATION DEFAULT SETTING

DHCP ON
Fixed, Non-routable Local Craft IP 169.254.1.1
Address
Management IP Address Provided by DHCP
Gateway IP Address Provided by DHCP
WebUI Enabled (ON)
Channel Bandwidth 20 MHz
Operating Frequencies 3580MHz, 3620MHz, 3640MHz
Corresponding eARFCN:
 Band 42/43: 43390, 43790, 43990
 Band 48: 55540, 55940, 56140
TDD Frame Configuration 2 (Special Subframe: 7)
Cell 0, 1, 2 Disabled
Transmit Power per stream 23 dBm
Clock Source GPS

Confidential - Restricted Use and Duplication 20 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5 Configuration

This chapter describes the tasks associated with preparing an FW-300i system to provide network
services to its users using the FW-300i WebUI or a Command Line Interface (CLI).
The FW-300i system allows efficient installation processes by supporting full pre-configuration of
equipment in the warehouse and a field installation process that does not require other installation
tools other than the ones needed for the physical installation.
To configure your system using the FW-300i WebUI (recommended), see Section 5.2, “Configuration
with the WebUI”.
If you want to perform the configuration process using a CLI, see Section 5.3, “Configuration with the
CLI”.
The recommended FW-300i system commissioning process includes the following steps:
 Pre-Configuration in the Warehouse
 Field Installation (See the “FW-300i Installation Manual”)

Confidential - Restricted Use and Duplication 21 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.1 System Configuration Process

The FW-300i WebUI menu structure is the basis for the configuration process. This means that the
configuration steps are set up so that you logically input all of the related parameters on a page before
you move to the next page/step in the configuration process.

SYSTEM CARRIERS LTE BASELINE CBSD MANAGEMENT FINISH

 System  Baseline  LTE Baseline  Common  Verify
Settings
 SSH/Web Users
Parameters Parameters Settings  Save
 Network  Cells RF  EPC Settings  eNB Settings  Syslog Settings
 Reboot
Connectivity Parameters  Advanced  Antenna  SNMP
 Advanced  Advanced Settings

Figure 5-1 FW-300i Configuration Process

Notes:
 Choose either the WebUI or the CLI method and follow the procedures under the desired
section/chapter.
 Perform these steps in the order presented.
 Once you complete the pre-configuration, ensure that you save the current running configuration to
the start-up configuration. This ensures that any changes are persistent over reboots.
 For the WebUI, see Section 5.2.6, “Verify, Save and Activate Current Running Configuration” and
 For the CLI, see Section 5.3.7, “Verify, Save and Activate Current Running Configuration” for
more information.

Confidential - Restricted Use and Duplication 22 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.2 Configuration with the WebUI

This section describes the tasks associated with preparing an FW-300i system to provide network
services to its users using the FW-300i WebUI. If needed, see Figure 5-1, FW-300i Configuration Process
for a visual overview of the configuration process.
If you want to perform the configuration process using a CLI, see Section 5.3, “Configuration with the
CLI”.
The recommended FW-300i system commissioning process includes the following steps:
 Pre-Configuration in the Warehouse
 Field Installation (See the “FW-300i Installation Manual”)

5.2.1 System
On the WebUI (under “Setup”) System page you set a few parameters:
 System Name and Description
 System Time Zone and Clock Source
 Network Connectivity parameters
 Advanced (IPv6, DNS, NTP, MTU, VLAN)

Confidential - Restricted Use and Duplication 23 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.2.1.1 Configuring a System Name

When pre-configuring the FW-300i, it is highly recommended that you set a unique hostname to
differentiate it from other devices.
 Navigate to the Setup > System page of the FW-300i WebUI.
 Under the System Settings area, assign a descriptive name to the module in the System Name field.
If desired, assign more identifying information via the System Description field. Use System Time
Zone and System Clock Source to set your time zone and clock source.

Select Commit in the top right corner in order to save the changes or select the Refresh ( )button to
cancel and return to the previous settings.
Repeat as needed for each device in your system.
Please note that most configuration changes are only applied after system reboot. To ensure that all of
your pre-configuration changes are saved to the start-up configuration file and to activate all of your
current configuration settings, see Section 5.2.6, “Verify, Save and Activate Current Running Configuration”.

5.2.1.2 System Synchronization

The FW-300i system is a Time Division Multiplexed (TDM) radio system. Therefore, FW-300i networks
require proper synchronization of the air interface to provide optimal service. The FW-300i system
provides flexible synchronization options as well as providing a high-performance extension to existing
synchronization networks which delivers quality clock services to downstream devices such as small
cells.
The eNodeB synchronizes using the Global Positioning System (GPS).
When configured to synchronize via GPS, the FW-300i system uses its internal GPS antenna and receiver
module to synchronize to the GPS network. This allows all network deployed FW-300i eNodeBs to

Confidential - Restricted Use and Duplication 24 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

accurately synchronize their transmit and receive operations on the air interface. The GPS system also
allows the FW-300i system to determine accurate time of day and date information. This time
information, together with a user configured time zone setting, tells time across the system and is
essential in functions such as fault management (for example, event and alarm time stamping) and
historical performance (for example, performance indicator processing and performance file creation). If
needed, there is also an optional external GPS source available.
The FW-300i system includes a high performance crystal oscillator that allows it to maintain its clock
properties (Holdover) even if the primary clock reference (that is, GPS) is no longer available. The system
provides a Holdover period of 5 minutes. During this time the radio is operational and the system
attempts to recover its primary clock source. If the system does not reacquire the clock source after the
Holdover period expires, the system is deemed “Not synchronized” and therefore ceases radio
operation so as to not interfere with other deployed FW-300i systems.
On the WebUI, to set the system synchronization:
 Navigate the Setup > System page on the FW-300i WebUI.
In the System Settings area, you set the system synchronization via the System Clock Source option.
Select your system clock source to GPS.

Notes:
 Networks of FW-300i systems depend on proper synchronization through GPS clock references
to operate optimally, and may experience significant performance degradation or even outage if
not deployed accordingly.
 The system allows you to use local clock as a clock source. This parameter is meant for lab
testing only.
 A change in clock source requires a reboot!
When you change the system time, you need to commit, save the change and then perform a
FW-300i reboot in order for the change to take effect.
Before moving to a new page, select Commit in the top right corner to save your changes or select the
Refresh button to cancel and return to the previous settings.
To save your changes to the startup configuration, select the Copy Running Configuration to Start-Up
Configuration button ( ) in the title bar.

Confidential - Restricted Use and Duplication 25 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Reboot the system to activate all of your saved changes, by selecting the Reboot System button ( ) in
the top right corner.

5.2.1.3 Network Connectivity Parameters

Once logged on to the FW-300i, you can change the IP address of the WAN interface under Network
Connectivity. There are two possible methods of assigning IP address to the system. You can choose
either:
 Static: statically assign the IP address for the WAN interface. If set to Static: you must configure
the IP address, subnet mask and default gateway, or
 DHCP: use the Dynamic Host Configuration Protocol (DHCP) to configure this IP address.
Note: To have DHCP properly assign an address to your FW-300i system, the system must have
network access to a DHCP server on your local network. This DHCP server must have available
addresses in its address pool, which are in the desired subnet you wish to assign to the system.
By default, the FW-300i WAN IPv4 address is assigned via DHCP.
In order to set the IPv4 address, please follow these steps:
 Navigate to the Setup > System page of the FW-300i WebUI.
Under Network Connectivity, you find all the configurable options.

Ensure the WAN IPv4 Address option is set to Static.

Enter an IPv4 address, subnet mask and optionally an address for the default gateway (local router)
using the applicable fields:
 IPv4 Address,
 Subnet Mask,
 Default Gateway
Select Commit in the top right corner to save your changes.
Notes:
 At any time during configuration changes and before clicking the Commit button, use the
Refresh ( ) button to return to the previous settings and/or to update the information on the
screen.
 To make your changes permanent (same configuration after a reboot), select the Copy Running
Configuration to Start-Up Configuration ( )button – located on the top right corner.

Confidential - Restricted Use and Duplication 26 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 The changes do not take effect until you reboot the system. Reboot the system by selecting the
Reboot System button ( ) in the top right corner.

5.2.1.4 Advanced Options

When you click on the Show Advanced button, more configurable fields (IPv6 and Advanced Network
Connectivity) will appear. This is where you will go to configure IPv6 and your DNS, NTP, IP MTU and
VLAN.

5.2.1.4.1 Setting up IPv6

1. Ensure the WAN IPv6 Address option is set to Static.

2. Enter an IPv6 address, IPv6 Prefix Length and optionally an address for the default gateway (local
router) using the applicable fields:
 IPv6 Address,
 IPv6 Prefix Length,
 Default Gateway

Confidential - Restricted Use and Duplication 27 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

3. Select Commit in the top right corner to save your changes.

Notes:
 With the current SW release, the IPv4 address and IPv6 address are either both statically
assigned, or both obtained through DHCP. This behavior will be modified in the future software
release such that methods for obtaining IP addresses are independent of each other.
 At any time during configuration changes in advanced mode and before clicking the Commit
button, use the Reset Advanced button (at the bottom) to return to the previous/default
settings.

5.2.1.4.2 Advanced Network Connectivity

This is where you can configure your DNS1, DNS2, NTP1, NTP2, IP MTU and VLAN settings.
1. Enter your desired DNS1, DNS2, NTP1, NTP2, IP MTU and VLAN values into each of the applicable
fields.
2. Select Commit in the top right corner to save your changes.

Confidential - Restricted Use and Duplication 28 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Notes:
 At any time during configuration changes and before clicking the Commit button, use the Reset
Advance button to return to the previous settings and/or to update the information on the
screen.
 All of these advanced parameters (DNS, NTP, MTU and VLAN) are optional settings and are not
critical for the system to be working.

5.2.2 Carriers
On the WebUI Carriers page you set the following parameters:
 Carriers Baseline Parameter (such as Channel Bandwidth and Frequency Setting Mode)
 Cell 0, 1 and 2 RF Parameters

5.2.2.1 Setting up Carriers Baseline Parameters

This is where you can set the parameters that are common for all the cells:
 Set the channel size,
 Assign the operating frequency mode (EARFCN or Frequency)
 Along with the option of muting the carriers

Confidential - Restricted Use and Duplication 29 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 The system supports 10MHz and 20MHz bandwidth configuration. Select the desired bandwidth via
the Channel Size (MHz) drop-down menu: 10 MHz or 20 MHz (default).
 Set the frequency mode for your carrier from the Frequency Setting Mode drop-down list. The
options are: EARFCN (Evolved Absolute Radio Frequency Channel Number (LTE)) or Frequency. The
default is set to EARFCN.
Note: If you select EARFCN, configure each Cell x Carrier EARFCN (where x is the desired cell
number) to the EARFCN licensed for your operation.

You also have the option of muting all Carriers in this section, should you desire to. All carriers are not
muted by default.

Click Commit in the top right corner to save the changes on this page or select the Refresh ( ) button
to cancel and return to the previous settings.
Notes:
 The EARFCN or RF frequency parameter must match between an FW-300i and the CPE to create a
link.

5.2.2.2 Set Cells 0-2 RF Parameters

This is where you can set the parameters that are unique for each cell:
1. Make sure that the box under “Enable Cell” is checked for each of the cell that you are configuring.

Confidential - Restricted Use and Duplication 30 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

2. Assign Sector x (where “x” is the desired sector antenna number) to each cell using the drop-down
list.*

As a reference as to how the sectors are labelled, see Figure 5-2, “FW-300i Sectors”.

Figure 5-2 FW-300i Sectors

As seen in Figure 5-2 FW-300i Sectors”, the cells can be programmed to transmit out of different
antenna sectors. A typical use for this is carrier aggregation, where for 2CC, two cells typically
transmit out of the same sector antenna (Please refer to the latest software release notes to see if
carrier aggregation is supported).
3. Next, depending on the frequency mode (EARFN or Frequency) that you have selected previously
under “Carriers Baseline Parameters”, set up the Carrier Frequency for each cell. Here are the
default values for each cell:
 3620MHz (Cell 0)
 3640MHz (Cell 1)
 3660MHz (Cell 2)

Confidential - Restricted Use and Duplication 31 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

OR
Set up the Carrier EARFCN values for each cell. . Here are the default values for each cell:
 55940 (Cell 0)
 56140 (Cell 1)
 56340 (Cell 2)

Note: The FW-300i and CPE MUST have matching EARFCN or frequencies (that are within the range
of usable frequency for the FW-300i system) to create a link.
4. The Carrier TX Power (Carrier Transmit Power) has a 29dBm maximum. Unless otherwise required,
BLiNQ recommends that you keep the value unchanged.*
5. Lastly, the drop-down list for Carrier Aggregation gives you the option of “Disabled” or “2 CC”.
Please refer to the latest software release notes to see if carrier aggregation is supported and make
your selection.

6. Select Commit in the top right corner to save the changes on this page or select the Refresh ( )
button to cancel and return to the previous settings.

Confidential - Restricted Use and Duplication 32 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Note:
 You configure transmit power per cell
 The following maximum values are limited via software:
o Band 48
 20MHz Bandwidth: 29dBm for any operational frequency within 3565MHz to 3685MHz
 10MHz Bandwidth: 27dBm for any operational frequency within 3555MHz to 3695MHz
o Band 42
 20MHz Bandwidth: 29dBm for any operational frequency within 3410MHz to 3590MHz
 10MHz Bandwidth: 29dBm for any operational frequency within 3405MHz to 3595MHz
o Band 43
 20MHz Bandwidth: 29dBm for any operational frequency within 3610MHz to 3790MHz
 10MHz Bandwidth: 29dBm for any operational frequency within 3605MHz to 3795MHz
 *One of the unique features of the FW-300i is the ability to steer, with variable capacity, over
different areas across 180 degrees of azimuth. This flexibility allows the FW-300i to support both
large coverage models, as well as capacity driven models. As a result of this feature, you are able to
configure the FW-300i to cover 60 degrees (3 x 20MHz), 120 degrees (2 x 20MHz) or 180 degrees (1
x 20MHz). Please note that the max. Carrier Transmit Power will vary based on your configuration.
o 3 x 20MHz: 24dBm per cell
o 2 x 20MHz: 26dBm per cell for the 2 cells and 29 dBm for the single cell
o 1 x 20MHz: 29dBm per cell

5.2.2.3 Advance Option

When you click “Show Advanced” button at the bottom of the page, you will reveal another configurable
parameter – Cell Advanced Parameters, where the Multiband feature is revealed.

Confidential - Restricted Use and Duplication 33 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Band 48 overlaps with Band 42 and 43 (3550-3700MHz). The Multiband feature allows CPE that do not
support Band 48 to connect to the FW-300i operating on Band 48. (ie. Backwards compatibility) To
enable this feature, make sure that the “Enable Multiband” is turned to “YES”.
Note:
 CPE’s support for multiband feature (MFBI) is also required. Please consult your CPE manual to
verify this.
 All BLiNQ CPEs support multiband feature.
 By default, “Enable Multiband” is set to “YES”.

5.2.3 LTE Baseline

On the LTE Baseline page, you configure the following parameters for all modes of operation:
 The baseline parameters (such as eNB ID and Cell Range)
 EPC settings

Confidential - Restricted Use and Duplication 34 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.2.3.1 Configuring LTE Baseline Parameters

In this section, you can assign values to Subframe Assignment, Special Subframe, eNB ID, PCI Seed
Value, Cell Range and Tracking Area Code.
Based on Baseline eNB ID and PCI Seed Value, the system will calculate eNB Identifiers and PCIs for
each of the cells and display these values in the eNB Identifiers table.

5.2.3.1.1 Subframe Assignment and Special Subframe

The advantage of using TDD is that it is possible to change the up and downlink balance and
characteristics to meet the load conditions. Please refer to ETSI TS 136 211 Chapter 4.2 to properly
configure your subframes.
1. Navigate to the Setup > LTE Baseline page of the FW-300i WebUI
2. In the LTE Baseline Parameters section, enter a value between 0-6 for the Subframe Assignment
field. As a default, it has the value of 2.
3. Under the Special Subframe field, set a value between 0-8. It is set at 7 by default.

4. Select Commit in the top right corner to save the changes on this page or select the Refresh ( )
button to cancel and return to the previous settings.

Confidential - Restricted Use and Duplication 35 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.2.3.1.2 Assign a Baseline eNodeB ID

You use the eNodeB ID to identify each cell when establishing a connection with the Evolved Packet
Core (EPC). The system automatically generates three IDs from the baseline value of this parameter for
each cell respectively, using the following logic:
 {[eNB Id]*256},
 {[eNB Id]*256+1},
 {[eNB Id]*256+2}.
This setting must match with the configured value in the EPC.
To setup the Baseline eNodeB ID:
 Navigate to the Setup > LTE Baseline page of the FW-300i WebUI.
Under the LTE Baseline Parameters section, assign the eNodeB identification in the Baseline eNB ID
field. The default value for this parameter is 100.

 Before going to another section, select Commit in the top right corner to save your changes or select
the Refresh button to cancel and return to the previous settings.

5.2.3.1.3 Entering PCI Seed Value

The Cell ID and PCI Seed Value define each cell’s Physical Cell ID (PCI) which the system uses to decode
data transmission.
 PCI calculation: 3*[PCI Seed Value] + [Cell Id]
 Cell IDs are fixed at 0, 1 and 2 respectively.
 BLiNQ recommends to pre-draft a PCI assignment strategy carefully to avoid interference due to PCI
reuse; you can use preconfigured default values
 Refer to Appendix B, “PCI Planning Guidelines” for more information on creating a PCI assignment
strategy
To enter PCI Seed Value:
 Navigate to the Setup > LTE Baseline Parameters page of the FW-300i WebUI.

Confidential - Restricted Use and Duplication 36 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Under the LTE Baseline Parameters area, assign the PCI Seed Value in the PCI Seed Value field (You can
enter any value between 0-167). It is set to 10 by default.

 Before going to another section, select Commit in the top right corner to save your changes or select
the Refresh ( ) button to cancel and return to the previous settings.

5.2.3.1.4 Assigning Cell Range

Configuring the cell range parameter automatically sets the parameters that the CPE requires to
establish the link.
To assign the cell range:
 Navigate to the Setup > LTE Baseline page of the FW-300i WebUI.

Confidential - Restricted Use and Duplication 37 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 In the LTE Baseline Parameters section, set the Cell range to the desired kilometer range. The range
is from 1 to 100 kilometers. 2km is the default value.

 Select Commit in the top right corner to save the changes on this page or select the Refresh ( )
button to cancel and return to the previous settings.

5.2.3.1.5 Setting Tracking Area Code

The Tracking Area Code identifies the tracking area within a particular network. You need to set the
same code that matches the settings on your EPC.
 Navigate to Setup > LTE Baseline page to set the tracking area code under LTE Baseline Parameters
section.
 Set the Tracking Area code via the Tracking Area Code field. By default, the value is set at 1.

 Before going to another section on the page, select Commit in the top right corner to save your
changes or select the Refresh ( ) button to cancel and return to the previous settings.

Confidential - Restricted Use and Duplication 38 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.2.3.2 eNB Identifiers

The values in this section are read only, and will change based on the values inserted in the LTE Baseline
Parameters section.
To configure this section, manipulate the values (see Section 5.2.3.1.2 Assign a Baseline eNodeB ID and
Section 5.2.3.1.3 Entering PCI Seed Value) in LTE Baseline Parameters.

Varies with Varies with PCI

Baseline eNB ID Seed Value

5.2.3.3 EPC Settings

The Evolved Packet Core (EPC) sets up the optional integrated (embedded) Evolved Packet Core on the
FW-300i system. In the EPC Settings section, you will configure the system to use either Embedded EPC
or External EPC.
This is also the section where you configure the PLMN ID.
The Public Land Mobile Network Identifier or PLMN ID defines the network. The PLMN ID consists of a
3-digit mobile country code (MCC) and a 2 (or 3)-digit mobile network code (MNC), thus PLMN-ID = MCC
+ MNC. You must enter the value that matches the one in the EPC.
To configure the Evolved Packet Core (EPC) for the FW-300i:
1. Navigate to the Setup > LTE Baseline page of the FW-300i WebUI.
2. Under the PLMN Id area of the EPC Settings section, assign the Public Land Mobile Network
identification in the PLMN Id field. The default value is 00101 (test network)

Confidential - Restricted Use and Duplication 39 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

3. Select either “Use Embedded EPC” or “Use External EPC”.

4. If you select “Use Embedded EPC”, please refer to Section 5.3.4.3, “Embedded EPC” to configure
your EPC.
5. If you are using external EPC, use the drop down list to select either “MME IPv4 Address” or “MME
IPv6 Address” and set your IP address.

6. Select Commit in the top right corner to save your changes or select the Refresh ( ) button to
cancel and return to the previous settings
Note: EPC Provisioning - You use the CLI for setting up the optional embedded EPC on the FW-300i
system. See Section 5.3.4, “EPC”.

5.2.3.4 Advanced Options

The Show Advanced Option in the LTE Baseline page opens up three more sections where you can set
different values for each cell. The sections are LTE Advanced – General, PDSCH/PDDCH and
RACH/PRACH.

Confidential - Restricted Use and Duplication 40 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.2.3.4.1 LTE Advanced – General Settings

1. Set the max. number of UEs (between 0-96) of the respective cells.
2. Enter the P-max Value. This is the maximum power the CPE is allowed to transmit. The maximum
value for this parameter is 23dBm.
3. Lastly, configure the Q Rx Lev Min value, which is the minimum signal strength that the CPE needs
to see in order for it to connect. Care must be taken when modifying this parameter. Please note
that a value of -65 dBm configured on the FW-300i translates to a min. threshold of -130 dBm (ie.
Multiplied by 2). If the CPE measures the signal strength lower than -130 dBm, then it will not
attempt to connect. Increasing the value of this parameter will severely impact the cell range.

Confidential - Restricted Use and Duplication 41 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

4. Select Commit in the top right corner to save your changes or select the Reset Advanced button to
cancel and return to the previous advanced settings.

5.2.3.4.2 Setting Up RACH/PRACH Values

Setting up the right values for RACH is critical to achieve up link synchronization between UE and eNB.
The default parameters are carefully selected by BLiNQ. Please do not modify unless instructed by BLiNQ
Support.
1. Choose a value from the drop down list in the RACH Powerramping Step field. This is the amount of
power that will be added onto the Initial RTP (which you will be configuring next) after each
connection attempt.

2. The next column is RACH Powerramping Preamble Initial RTP. Similarly, select a value from the
drop down list to set the initial power to use for connection to the CPE.
3. Select the maximum number of connection attempts from the drop down list under RACH Preamble
Trans Max field.
4. The next two columns (PRACH Config Idx and PRACH Zero Corr Zone) are used only if you wish to
use RACH/PRACH to configure your cell range instead of setting it up in the previous section (LTE
Baseline Parameters).
a. Check off the box at the top left corner of this section.
b. Set your PRACH Config Idx and the PRACH Zero Corr Zone to establish your cell range.

Confidential - Restricted Use and Duplication 42 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5. Once you are satisfied with your values, select Commit in the top right corner to save your changes
or select the Reset Advanced button to cancel and return to the previous advanced settings.

5.2.3.4.3 PDSCH/PDCCH

This section sets up the PDCCH (Physical Downlink Control Channel) CFI (Control Format Indicator) value.
It defines the amount of symbols in each subframe allocated to PDCCH. The default is set at 1.
BLiNQ Networks recommends keeping this value at 1.

5.2.4 CBSD
On the WebUI, you use the Citizens Broadband (radio) Service Device (CBSD) page for the Spectrum
Access System (SAS) server connectivity. When using the LTE Band 48, it requires Spectrum Access
System (SAS) server connectivity for operation. You configure the operating frequency, RF transmission
and transmit power per sector based on the grants received by the SAS server.
Perform these steps in the order presented.
Notes:
 You need to select the Commit button before you move to a new page to save your configuration
changes.
 Before exiting from the SAS configuration, you must save the current configuration to the startup
configuration with the Copy Running Configuration to Start-Up Configuration button ( ) in the
title bar. This ensures that your current configuration is the configuration after a reboot of the unit.
To configure the SAS server connectivity:
 On the WebUI, navigate to Setup > CBSD.

Confidential - Restricted Use and Duplication 43 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 Under the Common Settings area, use the following options to set up your SAS server connectivity:
 User ID: Input the CBSD User identification
number
 FCC ID: Input the Federal Communications
Commission (FCC) identification (ID) number. For
FW-300i, the value is ROR00000005.
 SAS Server URL: Input the Spectrum Access
System (SAS) database server Universal Resource
Locator (URL), for example:
https://testexample.com

Under the eNB Settings area, use the following options to

connect your eNodeB:
 eNB ID: Input the eNB identification number
 Category: Select the category A or B. If you
choose A, a new option appears:
 CPI Signed: Turn this feature on (YES) or off
(NO) with the toggle button
 Multi Step Reg: Use the toggle button to turn on
(YES) or off (NO) this feature
 Latitude: Input the eNB latitude
 Longitude: Set the eNB longitude
 Height: Input the height (feet) of the eNB based
on the type of height selected
 Height Type: Set the type of height; options are:
above ground level (AGL) or altitude/elevation
above mean sea level (AMSL)

Confidential - Restricted Use and Duplication 44 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 Horizontal Accuracy: Set the horizontal accuracy

 Vertical Accuracy: Set the vertical accuracy
 Measurement Capability: Assign the measurement capability; you can leave this blank or
choose from the following options: Power Without Grant and Power With Grant
 Group Type: Set the type of group; options are: None or Interference Coordination
Under the Antenna Settings area, use the following options to set up the antennas:
 Azimuth: Set the antenna azimuth
 Downtilt: Input the antenna downtilt
 Gain: Set the antenna gain
 Beam Width: Input the antenna beamwidth

Notes:
 While Azimuth differs for each antenna by 60 degrees, all the other parameters must be set with the
same value for each of 3 antennas.
 BLiNQ Networks do not recommend changing the default values for Gain and Beam Width.
Select the Commit button at the top of the screen to save your changes.
To save your changes to the startup configuration, select the Copy Running Configuration to Start-Up
Configuration button ( ) in the title bar.

Reboot the system to activate all of your saved changes, by selecting the Reboot System button ( ) in
the top right corner.

5.2.5 Management
The following sections only deal with using the FW-300i WebUI. If you want to use the CLI, see Section
5.3.6, “Management via the CLI”.

5.2.5.1 SSH/Web Users

You configure the user name, password and access level for the local security of each unit. The
SSH/Web Users feature allows you to add, modify (update password and read/write privileges level) or
delete system users from the FW-300i WebUI. Each unit’s configuration database stores the user
configuration data on the FW-300i.

Confidential - Restricted Use and Duplication 45 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

To add users to (or modify an existing user on) the system using the FW-300i WebUI:
 Navigate to the Setup > Management > Web, CLI, Logging page of the FW-300i WebUI.

 Select the Add User button to add a user. An Add User dialog box appears.

From the Add User dialog box, you can enter a username, password and choose the access level of that
user (Group) -- either Read Only or Read Write.
Note:
 Usernames must start with a letter and may be composed of alphanumeric characters only.
 Passwords are case sensitive, may be composed of alphanumeric characters including special
characters and must contain at least one (1) letter and one (1) digit.
 At least one user with read/write privileges needs to exist in the FW-300i system.
 The system will lock out specific user after 6 unsuccessful login attempts.

Confidential - Restricted Use and Duplication 46 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

You can edit existing FW-300i users by selecting the hyperlinked name of the user you want to modify.
The Update User dialog box appears.
To reset a password, type in the new password and select the Update User button to confirm the new
password. Inform the user of the new password.
You can also adjust the user’s access level – either Read Only or Read Write.

To change a user name, you must delete this user and create the user under a new name.

To delete a user: select the check box beside the user that you want to delete. Select the Delete User
button. The selected user’s User Name disappears from the list.

Confidential - Restricted Use and Duplication 47 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Note: If you cannot login due to a forgotten username or password, contact another user with
read/write access privileges to have them reset your login credentials. If you have lost all read/write
login credentials, contact your supplier.
For any of the actions, select Commit for the changes to save your changes or Cancel to abandon this
action.
Ensure that you save your changes to the startup configuration, select the Copy Running Configuration
to Start-Up Configuration button ( ) in the title bar.

5.2.5.2 Syslog

The syslog interface allows the FW-300i system to send standard syslog fault management information
(that is, syslog alarms, events and log entries) to external syslog servers.
On the Setup > Management > Web, CLI, Logging page, you can set or change their operational status.

5.2.5.2.1 Using/Editing Syslog Server

To use/edit a syslog server:

 Navigate to the Management > Web, CLI, Logging page.
 Select the server you wish to use in the Logging section.

 Enter either an IPv4 or an IPv6 address in the IP Address field.

 Select a Severity Filter by using the drop down list to set the type of information collected.

 Select the Commit button at the top of the screen to save your changes.
 To save your changes to the startup configuration, select the Copy Running Configuration to Start-
Up Configuration button ( ) in the title bar.

5.2.5.2.2 Delete a Syslog Server

To delete a server:

Confidential - Restricted Use and Duplication 48 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 Navigate to the Management > Web, CLI, Logging page.

 From the Logging section, uncheck the box next to the syslog server that you want to delete.

 Select the Commit button at the top of the screen to save your changes.
 The syslog server would then be deleted.
 To save your changes to the startup configuration, select the Copy Running Configuration to Start-
Up Configuration button ( ) in the title bar.

5.2.5.3 SNMP

The Simple Network Management Protocol (SNMP) feature allows you to add, delete or edit SNMPv2c
or SNMPv3 users and hosts. Theses interfaces provide complete access to configuration, state,
performance and fault information in the FW 300i system.
The WebUI SNMP page allows you to set up Simple Network Management Protocol (SNMP) users and
host servers, plus add, edit and remove SNMP users and host servers.

5.2.5.3.1 Add or Remove SNMP User

To add or remove an SNMP user:

 Access the Management > SNMP page.

Confidential - Restricted Use and Duplication 49 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 To add an SNMP user: select the Add User button under the SNMP Users section. An Add User
dialog appears. Input the name of the user in the Name field. Use the Access option to designate the
user access level by selecting either the Read Only or Read Write option.

Version refers to the security protocol level for that user: v2c (default) or a higher level security
protocol of v3. If you select v3, more options appear. Within the SNMPv3 Security area, you can
choose higher levels of security depending on the needs of your user and network.
 Security Level — sets the level of security: None (no options available), Authentication,
Authentication Privacy.
 Auth Encryption — sets the type of authentication encryption protocol: md5 or sha; only visible
when Security Level set to Authentication.
 Auth Password — sets the authentication password; only visible when Security Level set to
Authentication.
 Priv Encryption — sets the privacy encryption: aes128 or des56; available only when
Authentication Privacy option selected; only visible when Security Level set to Authentication
Privacy. (aes128 - The system automatically establishes encryption keys and changes them
periodically.)
 Priv Password — sets the privacy encryption password; available only when Authentication
Privacy option selected; only visible when Security Level set to Authentication Privacy.

Confidential - Restricted Use and Duplication 50 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 Select the Add User button to add your user or the Cancel button to abandon the addition.
 If you need to edit an existing user, select the hyperlinked name of the desired user, an Update User
dialog appears. When you finish your edits, select the Update User button to save your changes or
Cancel to abandon these changes.
Note: You cannot change the name field. If you do need to change the user name, delete that user
and repeat the above steps with a new name.
 To remove an SNMP user: select the check box beside the user you want to delete. Select the Delete
User button. The user disappears from the list.
 Select the Commit button at the top of the screen to save your changes.
 To save your changes to the startup configuration, select the Copy Running Configuration to Start-
Up Configuration button ( ) in the title bar.

 If this is your last change/update, reboot the system to activate all of your saved changes, by
selecting the Reboot System button ( ) in the top right corner.

Confidential - Restricted Use and Duplication 51 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.2.5.3.2 Add or Remove SNMP Host

To add or remove an SNMP host:

 Access the Management > SNMP; SNMP Hosts area.
 To add an SNMP host: select the Add Server button. An Add Server dialog appears. You need to
know the Name, IP Address and Port for your SNMP host.

Version refers to the security protocol level for that host: v1 (default), v2 or the higher level security
protocol of v3. If you select v3, more options appear. Within the SNMPv3 Security area, you can
choose higher levels of security depending on the needs of your host.
 Security Level — sets the level of security: None (no options available), Authentication,
Authentication Privacy
 Auth Encryption — sets the type of authentication encryption protocol: md5 or sha; only visible
when Security Level set to Authentication.
 Auth Password — sets the authentication password; only visible when Security Level set to
Authentication.
 Priv Encryption — sets the privacy encryption: aes128 or des56; only visible when Security Level
set to Authentication Privacy. (aes128 - The system automatically establishes encryption keys
and changes them periodically.)

Confidential - Restricted Use and Duplication 52 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 Priv Password — sets the privacy encryption password; only visible when Security Level set to
Authentication Privacy.

 Select the Add Server button to add your server or the Cancel button to abandon this addition.
 If you need to edit an existing SNMP host, select the hyperlinked name of the desired host, an
Update Server dialog will appear. When you finish your edits, select the Update Server button to
save your changes or Cancel to abandon these changes.
Note: If you do need to change the Host name, delete that host and repeat the above steps with a
new name.

 To remove an SNMP host: select the check box beside the host you want to delete. Select the Delete
Server button. The host disappears from the list.
 Select the Commit button at the top of the screen to save your changes.
 To save your changes to the startup configuration, select the Copy Running Configuration to Start-
Up Configuration button ( ) in the title bar.

Confidential - Restricted Use and Duplication 53 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 If this is your last change/update, reboot the system to activate all of your saved changes, by
selecting the Reboot System button ( ) in the top right corner.

5.2.6 Verify, Save and Activate Current Running Configuration

Before exiting from the pre-configuration setup:
 Verify that the currently running configuration meets all of the configuration system setup
requirements. If the configuration matches the expected configuration, you must save the currently
running configuration to the start-up configuration. This ensures that any changes are saved after a
reboot. To activate and see your configuration changes, reboot the system.

5.2.6.1 Verify and Save Running Configuration

To verify and save the currently running configuration:

 Verify the currently running configuration to ensure that it matches the expected configuration. For
instance, check that the EARFCN or radio frequencies match on the FW-300i and CPE.
Select the Commit button at the top of the screen to save your changes.
To save your changes to the startup configuration, select the Copy Running Configuration to Start-Up
Configuration button ( ) in the title bar.

Reboot the system to activate all of your saved changes, by selecting the Reboot System button ( ) in
the top right corner.

Confidential - Restricted Use and Duplication 54 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.3 Configuration with the CLI

This is a brief description on commands that you need to configure the FW-300i using a Command Line
Interface (CLI).
If desired, see Figure 5-1, FW-300i Configuration Process for a visual reference of the process.
To perform the configuration process using the FW-300i WebUI, see Section 5.2, “Configuration with the
WebUI”.
Notes:
 You only need to submit the commit command after you have input all of your pre-configuration
changes, but to ensure that you do not forget to save your changes; the commit command is
included at each step.
 Before exiting from the configuration, you must save the running configuration to the start-up
configuration so that changes are saved after a reboot. If needed see Section 5.3.7, “Verify, Save and
Activate Current Running Configuration” for more information.

5.3.1 System
Through the System command you set a few parameters:
 Configure a Hostname
 Assigning IPv4, IPv6 Addresses
 Configure DNS Servers

5.3.1.1 Configuring a Hostname

When initially provisioning an FW-300i, it is highly recommended that you set a unique hostname to
differentiate it from other devices.
 CLI Command:
[system id hostname]
To configure a hostname:
 If not already there, access the device via a CLI and enter the following commands:
 Rename the device by entering the following commands:
Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# system id hostname West1
Blinq eNB(config)# commit
Commit complete.
Repeat as needed for each device in your system.
To ensure that all of your pre-configuration changes are saved to the start-up configuration file, see
Section 5.3.7, “Verify, Save and Activate Current Running Configuration”.

Confidential - Restricted Use and Duplication 55 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.3.1.2 Assigning IP Address

Once logged on to the FW-300i, you can change the IP address of the WAN interface. There are two
methods. You can choose either:
 Static: statically assign the IP address for the WAN interface. If set to static: you must configure
the IP address, netmask and default gateway (optional), or
 DHCP: use the Dynamic Host Configuration Protocol (DHCP) to configure this IP address.
Note: To have DHCP properly assign an address to your FW-300i system, the system must have
network access to a DHCP server on your local network. This DHCP server must have available
addresses in its address pool, which are in the desired subnet you wish to assign to the system.
 CLI Commands:
[mgmt ip-config-mode], [mgmt ip], [mgmt netmask], [mgmt default-gateway]
The default configuration for the FW-300i system is a DHCP IP address.
Change the IP address, as follows:
 Using the FW-300i CLI to change the IP to a user-assigned IP address (for example, IP address:
192.168.1.10 with netmask 255.255.255.0 and optional gateway 192.168.1.254), enter these
commands:
Blinq eNB#
Blinq eNB# config terminal
Entering configuration mode terminal
Blinq eNB(config)# mgmt ip-config-mode static
Blinq eNB(config)# mgmt ip 192.168.1.10
Blinq eNB(config)# mgmt netmask 255.255.255.0
Blinq eNB(config)# mgmt default-gateway 192.168.1.254
Blinq eNB(config)# commit
Commit complete.

5.3.1.3 Setting up IPv6 Address

To configure IPv6 address, enter the following commands:

Blinq eNB#
Blinq eNB# config terminal
Entering configuration mode terminal
Blinq eNB(config)# mgmt ipv6-ip 2600:6ce6:4400:35::e
Blinq eNB(config)# mgmt default-ipv6-gateway 2600:6ce6:4400:35::1
Blinq eNB(config)# commit
Commit complete

5.3.1.4 Configuring DNS Servers

You can also configure DNS servers via CLI by using the following commands:
Blinq eNB#
Blinq eNB# config terminal
Entering configuration mode terminal
Blinq eNB(config)# mgmt dns status enable
Blinq eNB(config)# mgmt dns server 0 ip 8.8.8.8
Blinq eNB(config-server-0)# exit
Blinq eNB(config)# mgmt dns server 1 ip 8.8.4.4
Blinq eNB(config-server-1)# exit

Confidential - Restricted Use and Duplication 56 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Blinq eNB(config)# commit

Commit complete

5.3.2 Carriers
In this section, you configure the following parameters:
 Channel bandwidth and frequency mode,
 Enabling the Cells
 Cell 0, 1 and 2 RF Settings

5.3.2.1 Configure Channel Bandwidth and Frequency Mode

This procedure combines two steps, since you find both of these steps on the same command:
 Setting the channel bandwidth and
 Assigning the operating frequency for each sector
Notes:
 The default bandwidth is 20 MHz.
 The EARFCN or RF frequency parameter must MATCH between an FW-300i and CPE to create a
radio link.
 CLI Commands:
[radio bandwidth], [radio freq-setting-mode],
[radio rf x earfcn] OR [radio rf x frequency] where x is the desired radio number; repeat as required
for each radio
To create a radio link between an FW-300i and CPE, you must initially configure the channel bandwidth
and frequency mode:
 Access the device via a CLI and enter the following commands:
 For EARFCN:
Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# radio bandwidth 20
Blinq eNB(config)# radio freq-setting-mode mearfcn
Blinq eNB(config)# radio rf 0 earfcn 43090
Blinq eNB(config-rf-0)# top
Blinq eNB(config)# radio rf 1 earfcn 43290
Blinq eNB(config-rf-1)# top
Blinq eNB(config)# radio rf 2 earfcn 43090
Blinq eNB(config-rf-2)# top
Blinq eNB(config)# commit
Commit complete.
Blinq eNB(config)# end
 For RF:
Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# radio bandwidth 20
BliNQ eNB(config)# radio freq-setting-mode mfreq
Blinq eNB(config)# radio rf 0 frequency 3200

Confidential - Restricted Use and Duplication 57 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Blinq eNB(config-rf-0)# top

Blinq eNB(config)# radio rf 1 frequency 5150
Blinq eNB(config-rf-1)# top
Blinq eNB(config)# radio rf 2 frequency 3550
Blinq eNB(config-rf-2)# commit
Commit complete.
Blinq eNB(config-rf-2)# end

5.3.2.2 Enabling Cells

By default, the all 3 cells are disabled. Therefore, you will need to enable the cells prior to configuring
them.
To enable and configure 1 cell:
Blinq eNB#
Blinq eNB# config terminal
Entering configuration mode terminal
Blinq eNB(config)# cell sector 0
Blinq eNB(config-sector-0)# cell-enabled true
Blinq eNB(config-sector-0)# p-max true
Blinq eNB(config-sector-0)# p-max-value 23
Blinq eNB(config-sector-0)# q-rx-rev-min -70
Blinq eNB(config-sector-0)# exit
Blinq eNB(config) # commit
Commit complete
Repeat the same steps for the other cells that you are configuring by changing the sector number from
“0” to “1” or “2”.

5.3.2.3 Set Transmit Power

Transit power is set to the maximum of 29dBm. Unless otherwise required, BLiNQ recommends that you
keep the value unchanged.
Note:
 You configure transmit power per stream
 The following maximum values are limited via software:
o Band 48
 20MHz Bandwidth: 29dBm for any operational frequency within 3565MHz to 3685MHz
 10MHz Bandwidth: 27dBm for any operational frequency within 3555MHz to 3695MHz
o Band 42
 20MHz Bandwidth: 29dBm for any operational frequency within 3410MHz to 3590MHz
 10MHz Bandwidth: 29dBm for any operational frequency within 3405MHz to 3595MHz
o Band 43
 20MHz Bandwidth: 29dBm for any operational frequency within 3610MHz to 3790MHz
 10MHz Bandwidth: 29dBm for any operational frequency within 3605MHz to 3795MHz

 CLI Commands:
[radio rf x tx-power], where x is the desired radio number; repeat as required for each radio in your
system

Confidential - Restricted Use and Duplication 58 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

If you choose to set the transmit power to another value:

 If not already there, access the device via a CLI and enter the following commands:
Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# radio rf 0
Blinq eNB(config-rf-0)# tx-power 18
Blinq eNB(config-rf-0)# top
Blinq eNB(config)# radio rf 1 tx-power 18
Blinq eNB(config-rf-1)# top
Blinq eNB(config)# radio rf 2 tx-power 18
Blinq eNB(config-rf-2)# commit
Commit complete.

5.3.3 LTE Baseline

To configure the LTE Baseline parameters, complete the following steps:
 Assign the maximum cell range
 Configure the cell identity
 Assign an eNodeB identity

5.3.3.1 Assign the Maximum Cell Range

Configuring the cell range parameter automatically sets the parameters. Set the cell range to the desired
kilometer range. The range is from 1 (default) to 100 kilometers.
 CLI Commands:
[cell use-cell-range], [cell cell-range]
To assign the cell range and set the maximum:
 Using the FW-300i CLI, enter the following commands:
Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# cell use-cell-range true
Blinq eNB(config)# cell cell-range 1
Blinq eNB(config)# commit
Commit complete.
Blinq eNB(config)#

5.3.3.2 Configure the Cell Identity Parameters

On the CLI, the cell identity parameters include the cell-id and cell-group-id.
 cell-id and cell-group-id define each cell’s Physical Cell ID (PCI) which the system uses to decode the
data transmission
 PCI calculation: 3*[cell-group-id] + [cell-id]
 BLiNQ recommends to careful pre-draft a PCI assignment strategy to avoid interference due to
PCI reuse; you can use preconfigured default values
 Refer to Appendix B, “PCI Planning Guidelines” for more information on creating a PCI assignment
strategy

Confidential - Restricted Use and Duplication 59 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 CLI Commands:
[cell sector x cell-id], [cell sector x cell-group-id], where x is the desired cell number; repeat as
required for each cell in your system, [cell tracking-area-code]
To configure the sector/cell assignments:
 If not already there, access the device via a CLI and enter the following commands:
Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# cell sector 0 cell-id 0
Blinq eNB(config-sector-0)# cell-group-id 30
Blinq eNB(config-sector-0)# top
Blinq eNB(config)# cell sector 1 cell-id 1
Blinq eNB(config-sector-1)# cell-group-id 30
Blinq eNB(config-sector-1)# top
Blinq eNB(config)# cell sector 2 cell-id 2
Blinq eNB(config-sector-2)# cell-group-id 30
Blinq eNB(config-sector-2)# top
Blinq eNB(config)# cell tracking-area-code 1
Blinq eNB(config)#commit
Commit complete.
Blinq eNB(config)#

5.3.3.3 Assign an eNodeB ID

On the CLI, you use the cell enb-id to identify each cell when establishing a connection with the Evolved
Packet Core (EPC). There are three connections per FW-300i. The system automatically generates three
IDs from the configured value of this parameter for each cell respectively using the following logic:
{[enb-id]*256}, {[enb-id]*256+1}, {[enb-id]*256+2}. This setting must match with the configured value in
the EPC.
 CLI Command:
[cell enb-id]
To setup the eNodeB ID assignments:
 If not already there, access the device via a CLI and enter the following commands:
Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# cell enb-id 120
Blinq eNB(config)#commit
Commit complete.
Blinq eNB(config)#

5.3.4 EPC
The following section provides information about configuring External EPC and Embedded EPC.

5.3.4.1 Set EPC Specific Information

The Public Land Mobile Network Identifier or PLMN ID defines the network; it consists of a 3-digit
mobile country code (MCC) and a 2 (or 3)-digit mobile network code (MNC), thus PLMN-ID = MCC +
MNC. You must enter the value that matches the one in the EPC.

Confidential - Restricted Use and Duplication 60 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

In addition, the Mobility Management Entity (MME) defines the route for the control plane traffic. By
default, both are set to the same value.
 CLI Commands:
[epc plmn-id], [epc mme mme-ip]
To configure the EPC specific information for the FW-300i:
 If not already there, access the device via a CLI and enter the following commands:
Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# epc plmn-id 00101
Blinq eNB(config)# epc mme mme-ip 192.168.26.200
Blinq eNB(config)#commit
Commit complete.
Blinq eNB(config)#

5.3.4.2 EPC Provisioning

You use the CLI for setting up the optional integrated Evolved Packet Core (EPC) on the FW-300i system.
The FW-300i handles two forms of EPC:
 Embedded – internal, most of the settings are automatic
 External – requires more manual EPC settings
Note: All of the following steps assume that BLiNQ provides the EPC. If you are using your own EPC, base
your configuration on the information in this chapter.

Figure 5-3 EPC Topology

This section covers the steps for setting up the optional Embedded EPC on the FW-300i system using a
CLI.
If your system has an:
 Embedded EPC: follow the steps in Section 5.3.4.3, “Embedded EPC”, or for an
 External EPC: follow the steps in Section 5.3.4.4, “External EPC”
Notes:

Confidential - Restricted Use and Duplication 61 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 All of the following steps assume that BLiNQ provides the EPC.
 If needed, a read or show command details the current CLI configuration setup on the EPC.
Unless explicitly stated, the following commands are executed under rancli prompt, ‘RAN>’.

5.3.4.3 Embedded EPC

This section deals with the installation and configuration of the Embedded EPC.

5.3.4.3.1 Installation

BLiNQ Embedded EPC is packaged into the following two TAR archives:
 Software application (blqeepc.ac.3.2.39.tar.bz2)
 License file (license_<FW-300i MAC Address>.tar)

Notes:
 Whereas the SW application is generic, each license file is locked to the MAC address of a specific
FW-300i and can only be used with the FW-300i it is generated for. The filename of the license file
includes the MAC address of the licensed FW-300i.
 License file should be uncompressed before uploading to the FW-300i. On a Linux device, the tar file
can be uncompressed by using the following command:
tar -xvf license_<FW-300i MAC Address>.tar
 Software application should be uploaded to the FW-300i as provided by BLiNQ; the package will be
uncompressed automatically as part of the upload process
 Both packages can only be uploaded to the FW-300i via FTP, so there is a pre-requisite to have a FTP
server (with these packages) which is accessible from the FW-300i

The FW-300i CLI commands required to install the Embedded EPC are as follows:
 embedded-epc download license ftp <username> <password> <FTP-IP-address>
<license-file-name>
 embedded-epc download application ftp <username> <password> <FTP-IP-
address> blqeepc.ac.3.2.39.tar.bz2

The BLiNQ Embedded EPC can be activated by the following FW-300i CLI commands:

Blinq eNB# config

Entering configuration mode terminal
Blinq eNB(config)# system enable-embedded-epc true
Blinq eNB(config)# embedded-epc vendor attocore
Blinq eNB(config)# commit
#commit complete
Blinq eNB(config)# exit
Blinq eNB# copy running-config startup-config
Blinq eNB# system reboot

After the reboot, the FW-300i will be configured to use the BLiNQ embedded EPC.

Confidential - Restricted Use and Duplication 62 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.3.4.3.2 Configuration

Embedded EPC can currently only be configured via the command line interface (CLI).

Notes:
 You only need to submit the commit command after you have input all of your pre-configuration
changes, however, to ensure that you do not forget to save your changes, you may enter the
commit command after each configuration step.
 Once you finish configuring the system, you must save the running configuration to the start-up
configuration so that changes are saved after a reboot.
Blinq eNB# copy running-config startup-config

Configuration of the embedded EPC involves configuring the following items:

 Access Point Name (APN)
 Subscriber Information

5.3.4.3.2.1 Access Point Name (APN)

Through the APN command you set a few parameters:
 APN index
 APN name
 IPv4 network and netmask
 First IP assignment
 Primary/Secondary DNS

CLI commands required to define an APN completely are as follows:

Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# embedded-epc apn 0
Value for 'name' (<string>): internet
Value for 'network' (<IPv4 address>): 10.0.0.0
Blinq eNB(config-apn-0)# netmask 255.255.255.0
Blinq eNB(config-apn-0)# first-ip 10.0.0.2
Blinq eNB(config-apn-0)# num-ips 16
Blinq eNB(config-apn-0)# dns-primary 8.8.8.8
Blinq eNB(config-apn-0)# dns-secondary 8.8.8.4
Blinq eNB(config-apn-0)# exit
Blinq eNB(config)# commit
#commit complete
Blinq eNB(config)# exit
Blinq eNB# copy running-config startup-config

With respect to the commands above, please note:

Confidential - Restricted Use and Duplication 63 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 Index 0 (Blinq eNB(config)# embedded-epc apn 0) identifies the APN as the first one
defined. Index value can be incremented to define additional APNs
 In the above example, the first APN is named internet
 Network and netmask signify the IP address range that will be assigned to the CPEs
 IP address assignment per CPE can either be done dynamically or statically. The parameter “first-ip”
signifies the first IP address that will be assigned dynamically. By default, 32 addresses are allocated
for dynamic assignment. This number can be modified with parameter “num-ips”. Static IP
assignment requires the configuration of the exact IP address for each subscriber (Section 2.2)
 By default, NAT is enabled per APN; you can disable NAT per APN, by setting apn parameter “nat-
enabled” to false
 With the SW release 1.3.4 only one APN is supported.

5.3.4.3.2.2 Subscriber Information

Through the UE command you set a few parameters:
 International Mobile Subscriber Identity (IMSI)
 Security keys
 Maximum UL/DL traffic rates (i.e. Rate Limiting)
 APN name
 Static IP address (optional)

CLI commands required to define a subscriber completely are as follows:

Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# embedded-epc ue 001015432100123
Value for 'k' (<string>): 00112233445566778899aabbccddeeff
Value for 'opc' (<string>): 000102030405060708090a0b0c0d0e0f
Value for 'amf' (<string>): 8234
Blinq eNB(config-ue-001015432100123)# ambr-apn-dl 150000
Blinq eNB(config-ue-001015432100123)# ambr-apn-ul 15000
Blinq eNB(config-ue-001015432100123)# ambr-dl 150000
Blinq eNB(config-ue-001015432100123)# ambr-ul 15000
Blinq eNB(config-ue-001015432100123)# apn-name internet
Blinq eNB(config-ue-001015432100123)# ip 10.0.0.23
Blinq eNB(config-ue-001015432100123)# exit
Blinq eNB(config)# commit
#commit complete
Blinq eNB(config)# exit
Blinq eNB# copy running-config startup-config

With respect to the commands above, please note:

 IMSI is used as a unique attribute to identify each SIM card within a CPE. It is also used to define the
subscriber on the embedded EPC (001015432100123 used in the commands above)
 The K, OPc and AMF parameters form the security keys which are used for authenticating the user
when the CPE attempts to connect with the FW-300i. These values may be unique for each SIM
cards. Please contact BLiNQ Networks Support to obtain this information.

Confidential - Restricted Use and Duplication 64 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 AMBR parameters (ambr-apn-dl, ambr-apn-ul, ambr-dl, ambr-ul) define the maximum

instantaneous UL and DL throughout limits for the particular subscriber
 APN name defined for a specific user should match the definition in Section 2.1 and the
configuration on the CPE. If no (or incorrect) APN name is defined, the CPE will be rejected by the
EPC during attach
 Static IP address (10.0.0.23) is defined for the subscriber

5.3.4.4 External EPC

Perform all of the steps in Section 5.3.4.3, “Embedded EPC” AND the following additional steps:

5.3.4.4.1 Access Point Name (APN)

An Access Point Name (APN) differentiates different services allowed on the network.
You can configure IP addresses associated with each APN dynamically (within the range provided) or
statically (range=0). If needed, see Section 5.3.4.4.3, “Configure User Equipment (UE)” for more
information on configuring static IP addresses.
 CLI Command:
[add apn internet network=<IP address> netmask=<netmask> first=<IP address> range=<IP address
range>]
An added APN and IP pool range example:
RAN> add apn internet network=10.0.0.0 netmask=255.255.255.0 first=10.0.0.2
range=255

5.3.4.4.2 Configure the Default APN

Once you have added an Access Point Name, you need to assign the default configuration.
 CLI Command:
[set apnrt defaultapn=]
A default APN configuration example:
RAN> set apnrt defaultapn=internet

5.3.4.4.3 Configure User Equipment (UE)

You need to add subscriber information for each CPE (or UE) to the Home Location Register (HLR). The
HLR is responsible for storing and updating the database which contains all of the user subscription
information.
Depending on your system, configuring the User Equipment (UE) could consist of three steps:
 Configure Default Bearer
 Configure Dedicated Bearer
 Configure Multiple Dedicated Bearers

Confidential - Restricted Use and Duplication 65 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.3.4.4.4 Configure Default Bearer

Configuring the HLR default bearer includes the following subscriber identity and Quality of Service
(QoS) Profiles information:
 Subscriber Identity Module (SIM) card ID (International Mobile Subscriber Identity (IMSI)),
 Phone number (Mobile Subscriber ISDN Number (MSISDN)), and
 Network authentication keys (K (Subscriber Authentication Key (128 bit)), OPc (derived Operator
Code).
The IMSI, K and OPc must be identical with the SIM card information used during provisioning of the SIM
card. These values are dependent on how the SIM card is provisioned. You can assign the static IP
address via the parameter epsinfo1, e.g. epsinfo1=1,internet,{if Static IP: 10.0.0.43},9
The QoS profile includes the maximum allowed UL and DL bitrates (ambrul, ambrdl), associated Access
Point Name (APN) and quality class identifier (QCI). Unless explicitly required, leave the default values
for the QoS configuration.
 CLI Command:
[add hlr imsi=<imsi> msisdn=<msisdn> imei=<imei> k=<K> opc=<OPc> ambrdl=<dl> ambrul=<ul>
epsinfo1=1, internet, 9]
A default bearer configuration example:
RAN> add hlr imsi=001015432100043 msisdn=0043 imei=359657072055878
k=00112233445566778899AABBCCDDEEFF opc=000102030405060708090A0B0C0D0E0F
ambrdl=60 ambrul=20 epsinfo1=1,internet,{if Static IP 10.0.0.43},9

5.3.4.4.5 Configure Dedicated Bearer

This is to configure an optional dedicated bearer or specific SIM card ID/IMSI.

 CLI Command:
[upd hlr imsi=<imsi> epsinfoded1= <QCI>, <MaxULBitrate>, <MaxDLBitrate>, <GuarULBitRate>,
<GuarDLBitRate>, createtft,n*bi,0 ,pinh,17,lpr,<port range>]
A dedicated bearer configure example:
RAN> upd hlr imsi=001015432100040 epsinfoded1=1, 15000,150000,7000,
70000,createtft, n*bi,0,pinh,17,lpr,700-800

5.3.4.4.6 Configure Multiple Dedicated Bearers

This is to configure optional multiple dedicated bearers or SIM card IDs/IMSIs.

 CLI Command:
[upd hlr imsi=<imsi> epsinfoded1= #<QCI>, <MaxULBitrate>, <MaxDLBitrate>, <GuarULBitRate>,
<GuarDLBitRate>, createtft,n*bi,0, pinh,17,lpr,<port range>, #<QCI>, <MaxULBitrate>,
<MaxDLBitrate>, <GuarULBitRate>, <GuarDLBitRate>, createtft,n*bi,0, ,pinh,17,lpr,<port range>];
the red text highlights the changes
A multiple dedicated bearer configure example:
RAN> upd hlr imsi=001015432100040 epsinfoded1=#1, 15000,150000,7000, 70000,
createtft, n*bi,0,pinh,17,lpr,700-750,#2, 15000,150000,7000, 70000,createtft,
n*bi,0, pinh,17,lpr,750-800

Confidential - Restricted Use and Duplication 66 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.3.4.4.7 Delete Default/Dedicated Bearer

Use the following command to delete a default/dedicated bearer:

 CLI Command:
[upd hlr imsi=<imsi> epsinfoded1]
An example of the bearer delete command:
RAN> upd hlr imsi=001015432100040 epsinfoded1

5.3.4.4.8 Configure Authentication Center (AuC)

The Authentication Center (AuC) is the security part of HLR and is in charge of generating security
information from user identity keys. This HLR receives the security information and further
communicates to other entities in the network.
Input the Authentication Management Field (AMF) number which sets the acceptable synchronization
window in both the User Equipment (UE) and the network.
 CLI Command:
[set auc amf=<AMF>]
An authentication center (AuC) configuration example:
RAN> set auc amf=8234

5.3.4.4.9 Configure DNS

The General Packet Radio Service (GPRS) Domain Name System (DNS) Server allows mobile networks to
transmit IP packets to external networks such as the Internet. The Gateway GPRS Support Node (GGSN)
is a main component of the GPRS network. The GGSN is responsible for the internetworking between
the GPRS network and external packet switched networks, such as the Internet.
 CLI Command:
[set ggsn dns=<DNS IP address>
A DNS server configure example:
RAN> set ggsn dns=8.8.8.8

5.3.4.4.10 Configure Internal Media Gateway

The command “set intmgw” requires you to restart the system. Please refer to the Figure 5-3, EPC
Topology for the interfaces used in the following command sample, if your setup differs, adjust the ports
accordingly.
 CLI Command:
[set intmgw]
Configuring an Internal Media Gateway example:
RAN> set intmgw mgwid=1 ransideaddr=eth2 cnsideaddr=eth0 natinterface=eth0

Changes take effect after restart

RAN> reset system

Are you sure (Y/N)? y

Confidential - Restricted Use and Duplication 67 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.3.4.4.11 Configure MME to Define PLMN

You must configure the Mobility Management Entity (MME) to define the Public Land Mobile Network
(PLMN) identifier (PLMN Id). The PLMN Id must match the configuration on the FW-300i. This command
also includes a Tracking Area Identifier List (TAI List).
 CLI Command:
[set mme plmn=<PLMN Id> tailist=<TAI List>]
An example of setting the MME PLMN:
RAN> set mme plmn=00101 tailist=00101-50-60

5.3.4.4.12 Configure numPS channels (Max Bearers)

You control the maximum number of bearers allowed by using the “numps” parameter within a ran.cfg
configuration file. By having a higher value, you make sure that you do not hit the limitation of EPC on
the maximum bearers allowed.
Note: To make the changes effective, save and exit the ran.cfg file. Then restart the EPC by the
command: “sudo service ran restart”.
Example of numPS channels configuration:
blinq@quortus2:~$ sudo vi /usr/ran/ran.cfg

---ran.cfg------------
[intmgw]
asideaddr=eth2
baseporta=4000
baseportb=6000
boauthif=
bsideaddr=eth0
cnaddr=127.0.0.1
enable=y
enforcemtu=n
ethdefif=eth0
key=
localgtpport=2152
logeventspsdatausage=n
mecaddr=
mgwid=1
natinterface=eth2
numcs=20
nummux=20
numps=1000
pgwaddr=
postroutingscript=
postroutingscriptevery=
sgwaddr=
teidend=0
teidstart=0
tunaddr=
type=3
uuid=

Confidential - Restricted Use and Duplication 68 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.3.4.4.13 Configure eNodeB Settings

The command “add enodeb” requires a parameter in the format of <PLMN>-<eNB Id>.
Note: You need to enter three (3) eNB IDs for each FW-300i and the eNB ID should equal: (value-in-
FW-300i)*256, (value-in-FW-300i)*256+1, (value-in-FW-300i)*256+2.
This setting defines the PLMN-eNodeB ID to establish the connection between FW-300i and EPC.
This setting must match the configuration on the FW-300i.
 CLI Command:
[add enodeb <eNB Id>]
Example of the eNodeB setting:
RAN> add enodeb 00101-1

5.3.4.4.14 Configure SCTP Link

The Stream Control Transmission Protocol (SCTP) server provides guaranteed message delivery between
the MME and eNodeB by providing multi-homing and redundant paths to increase resilience and
reliability.
When configuring the SCTP server, the “localip” parameter is the address of the interface connected to
the eNodeB. The local port (“localport”) must be 36412.
 CLI Command:
[add net sctp-12 server binding=mme localip=<Local IP address> localport=36412]
Following is an example of SCTP link configuration:
RAN> add net sctp-12 server binding=mme localip=10.188.6.1 localport=36412

5.3.5 CBSD
Note: This setting applies to ALL modes of operation.
The Citizens Broadband (radio) Service Device or CBSD command structure sets up the Spectrum Access
System (SAS). When using the LTE Band 48, it requires Spectrum Access System (SAS) server connectivity
for operation. You configure the operating frequency, RF transmission and transmit power per sector
based on the grants received by the SAS server.
Notes:
 You only need to submit the commit command after you have input all of your configuration
changes, but to ensure that you do not forget to save your changes; the commit command is
included at each step.
 Before exiting from the SAS configuration, you must save the running configuration to the start-up
configuration so that changes are saved after a reboot. If needed see Section 5.3.7, “Verify, Save and
Activate Current Running Configuration” for more information.
Blinq eNB# copy running-config startup-config

Confidential - Restricted Use and Duplication 69 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 CLI Commands:
[cbsd common user-id], [cbsd common fcc-id], [cbsd common radio-tech], [cbsd common sas-server-
url], [cbsd enb id], [cbsd enb category], [cbsd enb latitude], [cbsd enb longitude], [cbsd enb height],
[cbsd enb height-type], [cbsd enb h-accuracy], [cbsd enb v-accuracy], [cbsd enb indoor-deployment],
[cbsd enb antenna-azimuth], [cbsd enb antenna-downtilt], [cbsd enb antenna-gain], [cbsd enb
antenna-beamwidth], [cbsd enb group-type], [cbsd enb meas-capability-list 0 capability]
To configure the SAS server connectivity:
 Access the FW-300i CLI and input the following:
Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# cbsd common user-id test
Blinq eNB(config)# cbsd common fcc-id 012
Blinq eNB(config)# cbsd common radio-tech e_utra
Blinq eNB(config)# cbsd common sas-server-url www.test.com
Blinq eNB(config)# cbsd enb id 01234
Blinq eNB(config)# cbsd enb category b
Blinq eNB(config)# cbsd enb latitude 45.123
Blinq eNB(config)# cbsd enb longitude 25.321
Blinq eNB(config)# cbsd enb height 10
Blinq eNB(config)# cbsd enb height-type agl
Blinq eNB(config)# cbsd enb h-accuracy 1
Blinq eNB(config)# cbsd enb v-accuracy 1
Blinq eNB(config)# cbsd enb indoor-deployment false
Blinq eNB(config)# cbsd enb antenna-azimuth 5
Blinq eNB(config)# cbsd enb antenna-downtilt 10
Blinq eNB(config)# cbsd enb antenna-gain 15
Blinq eNB(config)# cbsd enb antenna-beamwidth 2
Blinq eNB(config)# cbsd enb group-type interference-coordination
Blinq eNB(config)# cbsd enb meas-capability-list 0 capability
received_power_with_grant
Blinq eNB(config-meas-capability-list-0)# commit
Commit complete.
Once your SAS server connectivity set up is completed, save your running configuration to the startup
configuration with the following command:
Blinq eNB# copy running-config startup-config
Reboot the system to see and activate all of your configuration settings.
Blinq eNB# system reboot

5.3.6 Management via the CLI

You perform the following procedures via a CLI. If you wish to use the FW-300i WebUI, see Section 5.2.5,
“Management”.

Confidential - Restricted Use and Duplication 70 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.3.6.1 User

You configure the user name, password and access level for local security of each unit. Each unit’s
configuration database stores the user configuration data on the FW-300i.
To add users to the FW-300i system using the FW-300i CLI, enter these commands (<text> denotes the
unique per user information that you must add/choose):
Blinq eNB#
Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# admin users user <user name> password <password> group
<read-only OR read-write>
Blinq eNB(config-user-<username>)# commit
Commit complete.
Blinq eNB(config)# end
Blinq eNB# copy running-config startup-config
This command string creates a user with the given username, password, and access privilege based on
the group. The supported characters for usernames are A-Z/a-z/0-9/ and for passwords A-Z/a-z/0-9/Any
special character.
Through the CLI, you can change/update a password or change the group (privileges level) of a user:
Blinq eNB#
Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# admin users user ?
Possible completions:
User name [A-Za-z_][A-Za-z0-9_-]* Test admin
Blinq eNB(config)# admin users user Test
Blinq eNB(config-user-Test)# group ?
Possible completions:
[read-only] read-only read-write
Blinq eNB(config-user-Test)# group read-write
Blinq eNB(config-user-Test)# group ?
Possible completions:
[read-write] read-only read-write
Blinq eNB(config-user-Test)# password ?
Possible completions:
<string>[Test]
Blinq eNB(config-user-Test)# password
(<string>): ********
Reconfirm (<string>): ********
Blinq eNB(config-user-Test)# password ?
Possible completions:
<string>[test123!]
Blinq eNB(config-user-Test)# commit
Commit complete.
Blinq eNB(config)# copy running-config startup-config
To change a user name, you must delete the user and add the user under a new name.
To delete a user, you use the “no” before the command:
Blinq eNB#
Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# admin users user ?
This line doesn't have a valid range expression

Confidential - Restricted Use and Duplication 71 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Possible completions:
User name [A-Za-z_][A-Za-z0-9_-]* admin range Test
Blinq eNB(config)# no admin users user Test
Blinq eNB(config)# admin users user ?
This line doesn't have a valid range expression
Possible completions:
User name [A-Za-z_][A-Za-z0-9_-]* admin range
Blinq eNB(config)# commit
Commit complete.
Blinq eNB(config)# copy running-config startup-config

5.3.6.2 SNMP

The Simple Network Management Protocol (SNMP) feature allows you to add, edit or remove SNMPv2c
or SNMPv3 users and hosts. Following are examples on how to configure an SNMP user and host server
using the CLI.

5.3.6.2.1 Add SNMP User

Each SNMP user requires the following configuration data:

 name — The name of the SNMP user. For SNMPv2c users, this value represents the SNMP
community name.
 version — The SNMP version for the user — either SNMPv2c or SNMPv3.
 access-level — The access level of the user — either read-only or read-write.
 security-level — The security level of the user — either none, authentication only or authentication
and privacy. This parameter is only visible when the version is v3.
 auth-encryption — The SNMPv3 authentication encryption algorithm — either MD5 or SHA. This
parameter is only configurable when security-level is configured to authentication only or
authentication and privacy.
 auth-password — The password for the SNMPv3 authentication algorithm. This parameter is only
configurable when security-level is configured to authentication only or authentication and privacy.
 priv-encryption — The SNMPv3 privacy encryption algorithm — either DES56 or AES128. This
parameter is only configurable when security-level is configured to authentication and privacy.
(AES128 - The system automatically establishes encryption keys and changes them periodically.)
 priv-password — The password for the SNMPv3 privacy algorithm. This parameter is only
configurable when security-level is configured to authentication and privacy.
Configuration example (SNMPv3 user with authentication and privacy):
Blinq eNB(config)# admin snmp user mgr1
Value for 'version' [v2c,v3]: v3
Value for 'access-level' [read-only,read-write]: read-write
Value for 'security-level' [auth,auth-priv,none]: auth-priv
Value for 'auth-encryption' [md5,sha]: sha
Value for 'auth-password' (<[A-Za-z0-9_\-
!@#$%\^&\*\(\)~`\+=<>,\.\?/\|\{\}]+>): *********
Reconfirm Value for 'auth-password'
(<[A-Za-z0-9_\-!@#$%\^&\*\(\)~`\+=<>,\.\?/\|\{\}]+>):*********
Value for 'priv-encryption' [aes128,des56]: aes128
Value for 'priv-password' (<[A-Za-z0-9_\-
!@#$%\^&\*\(\)~`\+=<>,\.\?/\|\{\}]+>): *********
Reconfirm Value for 'priv-password'

Confidential - Restricted Use and Duplication 72 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

(<[A-Za-z0-9_\-!@#$%\^&\*\(\)~`\+=<>,\.\?/\|\{\}]+>):*********
Blinq eNB(config-user-mgr1)# exit
Blinq eNB(config)#

5.3.6.2.2 Add SNMP Host

Each SNMP host requires the following configuration data:

 name — The name of the SNMP host. For SNMPv2c hosts, this value represents the SNMP
community name.
 hostname – IP address of the host server (IPv4 or IPv6).
 port – port for the SNMP host server (SNMP trap listener port).
 version — The SNMP version for the host — either SNMPv1, SNMPv2c or SNMPv3.
 security-level — The security level of the host — either none, authentication only or authentication
and privacy. This parameter is only visible when the version is v3.
 auth-encryption — The SNMPv3 authentication encryption algorithm — either MD5 or SHA. This
parameter is only configurable when security-level is configured to authentication only or
authentication and privacy.
 auth-password — The password for the SNMPv3 authentication algorithm. This parameter is only
configurable when security-level is configured to authentication only or authentication and privacy.
 priv-encryption — The SNMPv3 privacy encryption algorithm — either DES56 or AES128. This
parameter is only configurable when security-level is configured to authentication and privacy.
(AES128 - The system automatically establishes encryption keys and changes them periodically.)
 priv-password — The password for the SNMPv3 privacy algorithm. This parameter is only
configurable when security-level is configured to authentication and privacy.
Configuration example:
Blinq eNB(config)# admin snmp host test
Value for 'hostname' (<IP address>): 192.164.123.123
Value for 'version' [v1,v2,v3]: v2
Blinq eNB(config-host-test)# port 162
Blinq eNB(config-host-test)# commit
Commit complete.
Blinq eNB(config)#

5.3.6.2.3 Remove SNMP User or Host

To remove an SNMP User or Host, you use the “no” before the command.
Configuration example:
Blinq eNB(config)# no admin snmp user mgr1
Blinq eNB(config)# no admin snmp host test
Blinq eNB(config-host-test)# commit
Commit complete.
Blinq eNB(config)#

5.3.6.3 Syslog Server

This option is available in a future software release. This section deals with setting up syslog servers via
the CLI. The syslog interface allows the FW-300i system to send standard syslog fault management
information (that is, syslog alarms, events and log entries) to external syslog servers.

Confidential - Restricted Use and Duplication 73 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

The mgmt syslog configuration command deals with remote syslog server and module log location
configuration.

5.3.6.3.1 Add Syslog Server

The mgmt syslog server command supports configuration of remote syslog servers. You can configure
up to 5 remote syslog servers. You must configure the following data for each server:
 ip — The IPv4 or IPv6 address of the syslog server.
 status — The status of the server (enabled or disabled (default)). When enabled, all syslogs
generated on the module are delivered to the remote server as well.
 severity-filter — The severity filter for logs forwarded to the remote server. The severity filters are:
alert, critical, debug, emergency, error, info (default), notice, or warning. The system forwards only
logs of the specified (or higher) severity.
Configuration example:
Blinq eNB(config)# mgmt syslog server 192.168.168.55
Blinq eNB(config-server-192.168.168.55)# status enabled
Blinq eNB(config-server-192.168.168.55)# severity-filter warning
Blinq eNB(config-server-192.168.168.55)# exit
Blinq eNB(config)#

5.3.6.3.1.1 Log-location
The log-location parameter configures the destination of syslog files on the module. Syslogs may be
written to either flash (persistent) or RAM (volatile) storage.
Configuration example:
BLiNQ-module(config)# mgmt syslog log-location flash
BLiNQ-module(config)#

5.3.6.3.2 Edit a Syslog Server

You can edit the status and severity filter of a syslog server.
Configuration example:
Blinq eNB(config)# mgmt syslog server 192.168.168.55
Blinq eNB(config-server-192.168.168.55)# status enabled
Blinq eNB(config-server-192.168.168.55)# severity-filter notice
Blinq eNB(config-server-192.168.168.55)# exit
Blinq eNB(config)#

5.3.6.3.3 Delete a Syslog Server

You use the “no” command to delete a syslog server.

Configuration example:
Blinq eNB(config)# no mgmt syslog server 192.168.168.55
Blinq eNB(config)# commit
Commit complete.
Blinq eNB(config)#

Confidential - Restricted Use and Duplication 74 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5.3.7 Verify, Save and Activate Current Running Configuration

Before exiting from the configuration system setup:
 Enable sector and radio transmitters
 Verify that the currently running configuration meets all of the pre-configuration system setup
requirements. If the configuration matches the expected configuration, you must save the currently
running configuration to the start-up configuration. This ensures that any changes are saved after a
reboot. Reboot your system to observe and activate all configuration settings.

5.3.7.1 Enable Sector and Radio Transmitters

In this two (2) step process, you:

 Activate (true) the cell sectors, which are by default set to false (disabled) and
 ensure that the radio transmitters are set to enabled (default)
You use the following commands to enable the transmitters:
 CLI Command:
[cell sector x cell-enabled], [radio rf x enabled], where x is the desired cell or radio number; repeat
as required for each cell or radio in your system
 If not already there, access the device via a CLI and enter the following commands:
Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# cell sector 0 cell-enabled
[false,true] (false): true
Blinq eNB(config-sector-0)#top
Blinq eNB(config)# cell sector 1 cell-enabled true
Blinq eNB(config-sector-1)# top
Blinq eNB(config)# cell sector 2 cell-enabled true
Blinq eNB(config-sector-2)# top
Blinq eNB(config)# radio rf 0 admin-state enabled
Blinq eNB(config-rf-0)# top
Blinq eNB(config)# radio rf 1 admin-state enabled
Blinq eNB(config-rf-1)# top
Blinq eNB(config)# radio rf 2 admin-state enabled
Blinq eNB(config-rf-2)# top
Blinq eNB(config)# commit
Commit complete

5.3.7.2 Verify and Save Running Configuration

To verify and save the currently running configuration:

 To verify the currently running configuration to ensure that it matches the expected configuration,
use the show running-config command:
Blinq eNB# show running-config
admin users user admin
password $1$LXxjxja3$Tba4S47GfDXElWOwo/E2H/
group read-write
!
cell prach prach-zero-corr-zone-config 10
cell sib3 sib3-snonintra-search-r9 false

Confidential - Restricted Use and Duplication 75 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

cell enb-id 120

cell sector 0
rflist rf0 true
cell-id 0
cell-enabled true
cell-group-id 30
q-rx-rev-min -55
p-max-value 18
!
cell sector 1
rflist rf1 true
cell-id 1
cell-enabled true
cell-group-id 30
rnti cell-offset 1
q-rx-rev-min -55
p-max-value 18
!
cell sector 2
rflist rf2 true
cell-id 2
cell-enabled true
cell-group-id 30
rnti cell-offset 2
q-rx-rev-min -55
p-max-value 18
!
.
.
[…OUTPUT REMOVED FOR SPACE]
epc mme mme-ip 192.168.26.200
epc sgw sgw-ip 192.168.26.200
epc enb enb-ip 192.168.26.150
epc enb enb-netmask 255.255.255.0
epc enb enb-gateway 192.168.26.200
ethernet port eth0
!
mac 0
!
mgmt ip 192.168.26.150
.
.
[…OUTPUT REMOVED FOR SPACE]
radio rf 0
enabled
tx-power 18
earfcn 43090
!
radio rf 1
enabled
tx-power 18
earfcn 43290
!
radio rf 2
enabled
tx-power 18
earfcn 43090
!

Confidential - Restricted Use and Duplication 76 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

system sync freerun-mode enabled

Blinq eNB#
If the configuration is as expected and meets all requirements, save the running configuration to the
start-up configuration so that changes are saved after reboot.
Blinq eNB# copy running-config startup-config
Reboot the system to observe and activate all of your configuration settings.
Blinq eNB# system reboot

5.3.8 System Synchronization

The FW-300i system is a Time Division Multiplexed (TDM) radio system. Therefore, FW-300i networks
require proper synchronization of the air interface to provide optimal service. The FW-300i system
provides flexible synchronization options as well as providing a high-performance extension to existing
synchronization networks which delivers quality clock services to downstream devices such as small
cells.
The eNodeB synchronizes using one of two standard synchronization mechanisms:
 Global Positioning System (GPS) or
 Optional IEEE 1588v2 with Sync E.
When configured to synchronize via GPS, the FW-300i system uses its internal GPS antenna and receiver
module to synchronize to the GPS network. This allows all network deployed FW-300i eNodeBs to
accurately synchronize their transmit and receive operations on the air interface. The GPS system also
allows the FW-300i system to determine accurate time of day and date information. This time
information, together with a user configured time zone setting, tells time across the system and is
essential in functions such as fault management (for example, event and alarm time stamping) and
historical performance (for example, performance indicator processing and performance file creation). If
needed, there is also an optional external GPS source available.
When configured to synchronize on IEEE 1588v2, the FW-300i system synchronizes to IEEE 1588v2
master clocks deployed on the operator network. The eNodeB can either be configured to use a specific
master clock (by providing the master clock identity) or can perform the standard Best Master Clock
(BMC) algorithm to select the best available master clock on the network. Additionally, you can
configure the system to use Sync E to assist the 1588 clock recovery when available. Just like GPS, the
IEEE 1588v2 infrastructure allows the eNodeB to precisely synchronize its air interface. It also provides
accurate time of day information.
The FW-300i system includes a high performance crystal oscillator that allows it to maintain its clock
properties (Holdover) even if the primary clock reference (that is, GPS or IEEE 1588v2) is no longer
available. The system provides a Holdover period of 5 minutes. During this time the radio is operational
and the system attempts to recover its primary clock source. If the system does not reacquire the clock
source after the Holdover period expires, the system is deemed “Not synchronized” and therefore
ceases radio operation so as to not interfere with other deployed FW-300i systems.
Command example:
Blinq eNB# config
Entering configuration mode terminal
Blinq eNB(config)# system sync ?
Possible completions:
freerun-mode Override sync-source and use freerun mode

Confidential - Restricted Use and Duplication 77 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

sync-source System synchronization source (requires reset)

Blinq eNB(config)# system sync sync-source ?
Description: System synchronization source (requires reset)
Possible completions:
[gps] gps ptp ptp-synce
Blinq eNB(config)# system sync sync-source gps
Blinq eNB(config)# commit
Commit complete
Blinq eNB(config)# exit
Blinq eNB# copy running-config startup-config
Blinq eNB# system reboot

Confidential - Restricted Use and Duplication 78 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

6 Operation and Maintenance

This section contains the following additional FW-300i operation and maintenance features:
 Software Upgrade
 Performance monitoring statistics for:
 eNB
 CPE
 Trace Log Files
 Measurements (per Sector)
 Fault management via the Events:
 Alarms page
 Events history

Confidential - Restricted Use and Duplication 79 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

6.1 Operation and Maintenance with the WebUI

The following sections only deal with using the FW 300i WebUI. If you want to use the CLI, see Section
6.2, “Operation and Maintenance with the CLI”.

6.1.1 Software Upgrade

To perform system software upgrade activities, you must have read-write privileges to access this
functionality.
Following are the instructions for upgrading the system software via the FW-300i WebUI.

The read-only Software Details area informs you of the device’s currently running software (active), the
available standby software and the current upgrade status.

6.1.1.1 System Software Upgrade

Software upgrades occur either from an FTP server, SFTP server or from your hard disk. To upgrade the
software, do the following:
 Navigate to the Administration > Software Upgrade in the FW-300i WebUI.

Confidential - Restricted Use and Duplication 80 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 Within the Run Software Upgrade area, from the Software Upgrade Method, select either FTP
Server or SFTP Server and enter the details (Host Address (IPv4 or IPv6), Username, Password and
File Path).
OR if you have a file on your hard disk or available network drive, select the Browse button under
Upgrade File and browse for the file from the File Manager window that appears.

sFTP Software Upgrade Option Browse Button: File Manager (example)

After choosing your upgrade file, select the Upgrade button in the top right corner of the page. A
progress bar appears.

A banner at the top of the page indicates if the software download succeeds.
The Standby Software Version field then shows the new software load version.
To load the standby software, select the Software Switch Over button at the top of the page.
 A Software Switch Over query window appears. Select the Yes button at the prompt. The
system restarts using the new software image. If the banner at the top indicates that this was
successful, you have finished this software upgrade procedure. Select the No button, if you want
to abandon this update.

Confidential - Restricted Use and Duplication 81 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 If there is a difference between the currently running configuration and the saved configuration,
a query window appears. Select Yes to save your configuration changes and continue with the
switch over or No to continue with the software switch over and lose your configuration
changes. You can select Cancel to stop the switch over completely, for instance to verify the
configuration changes.

If the software upgrade fails (for example, due to a corrupt load), the banner at the top of the page
indicates the upgrade was unsuccessful. The system tries three (3) times to restart with the new
software version; if the software upgrade attempts fail, the system reverts to the previous software
version. In this case, select a different version of the new software and repeat this procedure from Step
1.
Notes:
 You can only upgrade the FW-300i system software from one active browser session. This means
you can not open another browser session and start another upgrade process in parallel with
the first. If you try this, you get a warning message and the system does not let you continue.
Further, do not close the browser once you start the upgrade; if you do or if your computer
crashes, you must reset the FW-300i system that was being upgraded and start the upgrade
process over.
 To ensure a fresh installation, after switching over to new software, please clear your browser
history cache before launching a new WebUI session!

ONLY USE the ! Reset Factory Defaults button, at the top of the page, when you want to return all of the
configuration settings to the factory defaults. You must have read-write privileges to access this button.
When you select the ! Reset Factory Defaults button, the Login screen appears.

Confidential - Restricted Use and Duplication 82 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

6.1.2 Performance
The FW-300i monitors the performance statistics for the eNB and the linked CPE(s).

6.1.2.1 eNB Statistics Page

The eNodeB Statistics or eNB stats page is a read-only page that displays accumulated eNB throughput
statistics for how the FW-300i and the associated sectors have been performing for the past 24 hours.
The FW-300i stores a maximum of 96 performance history files over 24 hours before overwriting—one
file for every 15 minutes of performance data. Each performance history file contains all of the
performance data for every active, linked CPE during the associated 15 minute period.

6.1.2.2 CPE Statistics Page

The Customer Premise Equipment Statistics or CPE stats page is a performance read-only page that
visualizes the incoming and outgoing traffic for the interface connections between the CPE and the
FW-300i. This allows you to see traffic and bandwidth usage for the interfaces in real-time and monitor
the current download/upload throughput speeds. It also lists the current throughput performance
statistics for the interfaces.
Note: The screen refresh interval is every 5 seconds.
If needed, the Refresh button allows you to refresh the data; it takes approximately 5 seconds to
refresh.

Confidential - Restricted Use and Duplication 83 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

The CPE Statistics covers:

 LTE CELL:
 IMSI:
 RNTI: denotes the Radio Network Temporary Identifier (RNTI) of a connected UE
 Carrier Frequency:
 UL-SINR:
 UL-RSSI:
 UL MCS: indicates the uplink Modulation and Coding Scheme (MCS)
 DL MCS: indicates the downlink Modulation and Coding Scheme (MCS)
 UL-BLER:
 DL-BLER:
 DL/UL Throughput: shows the downlink (DL) and uplink (UL) throughput (Tput)
 Reattach Count: designates the Physical Uplink Shared Channel (PUSCH) Signal to Interference plus
Noise Ratio (SINR)
 Trace: Starts and then stops the creation of a Trace Log file on this specific CPE

6.1.2.3 Trace Log Files

The Trace Log Files page offers access to XML trace log files which provide detailed information on one
or more UEs. You can use this information for monitoring and optimizing operations and/or to aid in
troubleshoot issues.

Confidential - Restricted Use and Duplication 84 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

To obtain a trace file:

 Navigate to the Performance > CPE Statistics > Trace column; then select the Start button under the
desired CPE, this activates the trace file. The button label changes to say Stop and the button
background changes from blue to red. Each CPE creates a separate trace file.

To stop the trace, select the Stop button under Performance > CPE Statistics > Trace, this deactivates
the trace on this CPE.
To view the file(s), go to Performance > Trace log files and select the desired XML file hyperlink. The
names are based on the CPE’s RNTI. The file opens in a separate tab in your web browser.

Confidential - Restricted Use and Duplication 85 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

6.1.2.4 Measurements

Sector x Measurements page, where x represents the sector number, covers Key Performance
Indicators (KPI) subcategories: accessibility, retainability, availability and mobility measurements for that
sector.

Part 1 of Sector 0 Measurements page

Part 2 of Sector 0 Measurements page

6.1.2.4.1 Accessibility

 RRC Establishments per Cause: details Radio Resource Control (RRC) established connections per
cause

Confidential - Restricted Use and Duplication 86 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 RRC.ConnEstabAtt.Cause: shows established RRC connections attempts per cause

 RRC.ConnEstabSucc.Cause: demonstrates successful RRC connections established per cause
 RRC Reestablishments per Cause: details Radio Resource Control (RRC) re-established connections
per cause
 RRC.ConnReEstabAtt.Cause: shows re-established RRC connections attempts per cause
 RRC.ConnReEstabSucc.Cause: demonstrates successful RRC connections re-established per
cause
 S1SIG Establishments: details established S1 signalling
 S1SIG.ConnEstabAtt: shows S1 signalling established connections attempts per cause
 S1SIG.ConnEstabSucc: demonstrates successful S1 signalling connections established per cause
 ERAB Establishments per QCI: details the number of established E-UTRAN Radio Access Bearers
(E-RAB) per Quality of Service (QoS) Class Identifier (QCI)
 ERAB.EstabInitAttNbr.QCI: shows the number of established initial attempts E-RAB per QCI
 ERAB.EstabInitSuccNbr.QCI: shows the number of successfully established initial attempts
E-RAB per QCI
 ERAB.EstabAddAttNbr.QCI: shows the number of additional established attempts E-RAB per QCI
 ERAB.EstabAddSuccNbr.QCI: shows the number of additional successfully established attempts
E-RAB per QCI

6.1.2.4.2 Retainability

 ERAB Releases per QCI: details the number of E-UTRAN Radio Access Bearer (E-RAB) releases per
Quality of Service (QoS) Class Identifier (QCI)
 ERAB.RelActNbr.QCI: shows the actual release number of E-RAB per QCI
 ERAB.RelEnbNbr.QCI: shows the eNB release number of E-RAB per QCI
 ERAB Session time: details the E-RAB active session time
 ERAB.SessionTimeUE: shows the active session time between the UE and the E-RAB

6.1.2.4.3 Availability

 RRU Unavailable time per Cause: provides percentage of time that the remote radio unit (RRU) is
unavailable per cause (0 and 1)
 RRU.CellUnavailableTime.Cause

6.1.2.4.4 Mobility

 HO Preparations per QCI: provides handover(HO) preparations per standardized Quality of Service
(QoS) Class Identifier (QCI) characteristics (release 12)
 HO.PrepAtt.QCI: specifies the attempted handover preparations per standardized QCI
 HO.PrepSucc.QCI: states the successful handover preparations per standardized QCI
 HO Executions:
 HO.ExeAtt: identifies the number of handover execution attempts
 HO.ExeSucc: details the number of handover execution successes

Confidential - Restricted Use and Duplication 87 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

6.1.3 Events
The system events are broken down into two sections:
 Alarms and
 History

6.1.3.1 Alarms (Logs) Page

This read-only page lists active alarms (set alarms). Once you clear the Alarm, it appears on the Alarm
and History pages along with its details. For a list of alarms, see Appendix C, “Alarms and Events (Fault
Management)”.

Confidential - Restricted Use and Duplication 88 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

6.1.3.2 History Page

This read-only page lists a chronological history of alarms and events along with their details. For a list of
alarms and events see Appendix C, “Alarms and Events (Fault Management)”. The most recent events
appear first, to view older events use the page buttons or to quickly access the oldest events, use the
Last button.

Note: Clicking Clear History completely clears the current alarms and events history from the FW-300i
event logging infrastructure.
Use the Refresh button to update the information on the screen.

Confidential - Restricted Use and Duplication 89 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

6.2 Operation and Maintenance with the CLI

The following sections deal with using the FW-300i CLI only. If you want to use the WebUI, see Section
6.1, “Operation and Maintenance with the WebUI”.

6.2.1 Software Upgrade

Following are the instructions for upgrading the system software via the FW-300i CLI.

6.2.1.1 FW-300i CLI System Software Upgrade

Active and standby software image versions can coexist simultaneously on the FW-300i.
Entering the show system software Privileged EXEC command displays the running-version, restart-
version, and available-version software images currently on the FW-300i. The running and restart
versions represent the currently active system software images, while the available version represents
the standby system software image. For example:
Blinq eNB# show system software
system software running-version 1.1.1
system software restart-version 1.1.1
system software available-version 1.1.2
system software upgrade-status idle
Blinq eNB#
To upgrade the software through the FW-300i CLI:
 Run the command: system software download to download a new software image onto the
FW-300i from an FTP server. You need to know the:
 ftp server name, [in the example below, blinq1]
 access password, [in the example below, blinq1]
 IP address and [in the example below, 169.254.1.27]
 the software file name you want to download [in the example below, BLiNQ_FW300i_1.1.2.bin].
If the software download is successful, the command output indicates a successful download. For
example:
Blinq eNB# system software download ftp blinq1 blinq1 169.254.1.27
BLiNQ_FW300i_1.1.2.bin
Downloading file...ok.
Verifying image integrity...ok.
Extracting image (5/5)...ok.
Download of software image ftp/BLiNQ_FW300i_1.1.2.bin succeeded.
 Run the show system software command. The available-version field (that is, the standby system
software image) should show the new software load image version:
Blinq eNB# show system software
system software running-version 1.1.1
system software restart-version 1.1.1
system software available-version 1.1.2
system software upgrade-status switchover-succeeded
Blinq eNB#

Confidential - Restricted Use and Duplication 90 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 To make the available-version software (that is, the standby software load image) the active
software on the module, run the system software switchover command:
Blinq eNB# system software switchover
Preparing for switchover.
Comparing running-config to startup-config...no differences.
Switching from version 1.1.1 to version 1.1.2. Proceed [y/n]? yes
Running configuration transformers...
Release 1.1.1 transformer...ok.
Configuration data migration succeeded.
Proceeding with switchover.
On completion, the FW-300i resets and you are forced out of the FW-300i CLI. Log in again once the
FW-300i system is back up and running.
 If the software upgrade fails (due typically to a corrupt load), the output from the systems software
download command indicates the upgrade was unsuccessful, and the system restarts again using
the old software image. In this case, select a different version of the new software and repeat this
procedure from Step 1.

6.2.2 Performance
The FW-300i monitors the performance statistics for the eNB and the linked CPE(s).
In the CLI, you use the “show” command to view performance statistics.

6.2.2.1 eNB Statistics

This read-only information displays accumulated eNB throughput statistics for the performance of the
FW-300i and the associated sectors for the past 24 hours.
The FW-300i stores a maximum of 96 performance history files over 24 hours before overwriting—one
file for every 15 minutes of performance data. Each performance history file contains all of the
performance data for every active, linked CPE during the associated 15 minute period.
The data includes the following:
 index — Identifies the sector
 dl-tput — Details the downlink (DL) throughput (Tput)
 ul-tput — Shows the uplink (UL) throughput (Tput)
If desired, you can specify the desired data required per specific sector.
Show example:
 Without a specific sector
Blinq eNB# show pm enb-stats
INDEX DL TPUT UL TPUT
-------------------------------
0 0 0
1 0 0
2 0 0

Confidential - Restricted Use and Duplication 91 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 With a specific sector

Blinq eNB# show pm enb-stats sector 2
INDEX DL TPUT UL TPUT
-------------------------------
2 0 0
 Specific data per specific sector
Blinq eNB# show pm enb-stats sector 2 dl-tput
dl-tput " 0"
Blinq eNB#

6.2.2.2 CPE Statistics

This performance read-only information visualizes the incoming and outgoing traffic for the interface
connections between the CPE and the FW-300i. This allows you to see traffic and bandwidth usage for
the interfaces in real-time and monitor the current download/upload throughput speeds. It also lists the
current throughput performance statistics for the interfaces.
Note: The refresh interval is every 5 seconds.
If desired, due to multiple CPEs, you can specify the applicable CPE.
The CPE data includes the following:
 cpe-id — Shows the CPE Identification
 dl-cqi — Shows the Downlink (DL) Channel Quality Indicator (CQI)
 dl-tput — Details the DL throughput (Tput)
 dl-ul-mcs — Demonstrates the downlink and uplink (UL) Modulation and Coding Scheme (MCS)
 pucch-sinr — Details the Physical Uplink Control Channel’s (PUCCH) Signal to Interference plus Noise
Ratio (SINR)
 pusch-sinr — Shows the Physical Uplink Shared Channel’s (PUSCH) Signal to Interference plus Noise
Ratio (SINR)
 sec — Identifies the Sector
 srs-sinr — Demonstrates the Sounding Reference Signal’s (SRS) Signal to Interference plus Noise
Ratio (SINR)
 state — Identifies the current operating state
 ul-tput — Shows the uplink (UL) throughput (Tput)
 trace — When set to true, traces the specific CPE activity for a period of time (only available via the
WebUI)
If desired, you can specify the desired data required per specific CPE.
Show example:
 Without a specific CPE
Blinq eNB# show pm cpe-stats
CPE PUSCH PUCCH SRS DL UL DL
RNTI ID SEC SINR SINR SINR MCS CQI STATE DL TPUT UL TPUT TRACE
-----------------------------------------------------------------------------------------------
285 1 2 26.0 14.0 24.0 28 23 15 IDLE_COMMON_WT 24302 2283 false
322 2 2 27.0 14.0 25.0 27 23 15 IDLE_COMMON_WT 24450 1981 false
396 4 2 27.0 14.0 23.0 27 24 15 IDLE_COMMON_WT 24276 1904 false
469 1 1 32.0 14.0 32.0 28 23 15 IDLE_COMMON_WT 24279 2288 false

Confidential - Restricted Use and Duplication 92 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 With a specific CPE

Blinq eNB# show pm cpe-stats cpe 285
CPE PUSCH PUCCH SRS DL UL DL
RNTI ID SEC SINR SINR SINR MCS CQI STATE DL TPUT UL TPUT TRACE
-----------------------------------------------------------------------------------------------
285 1 2 26.0 14.0 24.0 28 23 15 IDLE_COMMON_WT 24298 2283 false

 Specific data per specific CPE

Blinq eNB# show pm cpe-stats cpe 285 pucch-sinr
pucch-sinr 14.0
Blinq eNB#

6.2.2.3 Trace Log Files

This feature is available in the WebUI only. See Section 6.1.2.3, “Trace Log Files” for more information.

6.2.2.4 Measurements

This command covers Key Performance Indicators (KPI) accessibility, retainability, availability and
mobility measurements per specific sectors.
You can view all of the measurements or individually.
Example:
 Specific measurement
Blinq eNB# show pm measurements 0 availability
RRU CELL
UNAVAILABLE
CAUSE TIME
--------------------
0 0
1 0

Blinq eNB#
 All measurements
Blinq eNB# show pm measurements 0
accessibility s1sig-conn-estab-att 9
accessibility s1sig-conn-estab-succ 6
RRC
CONN
ESTAB
CAUSE ATT
--------------
0 0
1 0
2 0
3 6
4 3
5 0
6 0
7 0

Confidential - Restricted Use and Duplication 93 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

RRC
CONN
ESTAB
CAUSE SUCC
--------------
0 0
1 0
2 0
3 6
4 3
5 0
6 0
7 0

RRC
CONN
REESTAB
CAUSE ATT
----------------
0 0
1 0
2 0
3 0

RRC
CONN
REESTAB
CAUSE SUCC
----------------
0 0
1 0
2 0
3 0

ERAB
ESTAB
INIT
ATT
QCI NBR
------------
0 0
1 0
2 0
3 0
4 0
5 0
6 0
7 0
8 6
9 0
10 0
11 0
12 0
13 0
14 0
.
.
[...OUTPUT REMOVED FOR SPACE, otherwise 15 pages showing ALL measurements]

Confidential - Restricted Use and Duplication 94 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

6.2.2.4.1 Accessibility

 ERAB Establishments per QCI — details the number of established attempts of E-UTRAN Radio
Access Bearers (E-RAB) per Quality of Service (QoS) Class Identifier (QCI)
 erab-estab-add-att-nbr-list — shows the number of additional established attempts E-RAB per
QCI
 erab-estab-add-succ-nbr-list — shows the number of additional successfully established
attempts E-RAB per QCI
 erab-estab-init-att-nbr-list — shows the number of established initial attempts E-RAB per QCI
 erab-estab-init-succ-nbr-list — shows the number of successfully established initial attempts
E-RAB per QCI
 RRC Reestablishments per Cause — details Radio Resource Control (RRC) established and re-
established connections per cause
 rrc-conn-estab-att-list — shows established RRC connections attempts per cause
 rrc-conn-estab-succ-list — demonstrates successful RRC connections established per cause
 rrc-conn-reestab-att-list — shows re-established RRC connections attempts per cause
 rrc-conn-reestab-succ-list — demonstrates successful RRC connections re-established per cause
 S1SIG Establishments per Cause — details attempts and established S1 signalling
 s1sig-conn-estab-att — shows S1 signalling established connections attempts per cause
 s1sig-conn-estab-succ — demonstrates successful S1 signalling connections established per
cause
Example:
Blinq eNB# show pm measurements 0 accessibility ?
Description: Accessibility
Possible completions:
erab-estab-add-att-nbr-list ERAB_EstabAddAttNbr
erab-estab-add-succ-nbr-list ERAB_EstabAddSuccNbr
erab-estab-init-att-nbr-list ERAB_EstabInitAttNbr
erab-estab-init-succ-nbr-list ERAB_EstabInitSuccNbr
rrc-conn-estab-att-list RRC_ConnEstabAtt
rrc-conn-estab-succ-list RRC_ConnEstabSucc
rrc-conn-reestab-att-list RRC_ConnReEstabAtt
rrc-conn-reestab-succ-list RRC_ConnReEstabSucc
s1sig-conn-estab-att S1SIG_ConnEstabAtt
s1sig-conn-estab-succ S1SIG_ConnEstabSucc
| Output modifiers
<cr>
Blinq eNB# show pm measurements 0 accessibility erab-estab-add-att-nbr-list
ERAB
ESTAB
ADD
ATT
QCI NBR
------------
0 0
1 0
2 0
3 0
4 0

Confidential - Restricted Use and Duplication 95 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

5 0
6 0
7 0
8 0
9 0
10 0
11 0
12 0
13 0
14 0

Blinq eNB#

6.2.2.4.2 Retainability

 ERAB Releases per QCI — details the number of E-UTRAN Radio Access Bearer (E-RAB) releases per
Quality of Service (QoS) Class Identifier (QCI) plus the active session time
 erab-rel-act-nbr-list — shows the actual release number of E-RAB per QCI
 erab-rel-enb-nbr-list — shows the release number of E-RAB per QCI
 erab-session-time-ue — shows the active session time between the UE and the E-RAB
Example:
Blinq eNB# show pm measurements 0 retainability ?
Description: Retainability
Possible completions:
erab-rel-act-nbr-list ERAB_RelActNbr
erab-rel-enb-nbr-list ERAB_RelEnbNbr
erab-session-time-ue ERAB_SessionTimeUE
| Output modifiers
<cr>Blinq eNB# show pm measurements 0 retainability
retainability erab-session-time-ue 219
ERAB
REL
ACT
QCI NBR
-----------
0 0
1 0
2 0
3 0
4 0
5 0
6 0
7 0
8 10
9 0
10 0
11 0
12 0
13 0
14 0

Confidential - Restricted Use and Duplication 96 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

ERAB
REL
ENB
QCI NBR
-----------
0 0
1 0
2 0
3 0
4 0
5 0
6 0
7 0
8 10
9 0
10 0
11 0
12 0
13 0
14 0

Blinq eNB#

6.2.2.4.3 Availability

 rru-cell-unavailable-time-list — provides the percentage of time that the remote radio unit (RRU) is
unavailable per cause (0 and 1)
Example:
Blinq eNB# show pm measurements 0 availability rru-cell-unavailable-time-list
RRU CELL
UNAVAILABLE
CAUSE TIME
--------------------
0 0
1 0

Blinq eNB#

6.2.2.4.4 Mobility

 HO Executions — deals with handover (HO) executions

 ho-exe-att — identifies the number of handover execution attempts
 ho-exe-succ — details the number of successful handover executions
 HO Preparations per QCI — provides handover (HO) preparations per standardized Quality of
Service (QoS) Class Identifier (QCI) characteristics (release 12)
 ho-prep-att-list — specifies the attempted handover preparations per standardized QCI
 ho-prep-succ-list — states the successful handover preparations per standardized QCI
Example:
Blinq eNB# show pm measurements 0 mobility
mobility ho-exe-att 0
mobility ho-exe-succ 0

Confidential - Restricted Use and Duplication 97 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

HO
PREP
QCI ATT
-----------
0 0
1 0
2 0
3 0
4 0
5 0
6 0
7 0
8 0
9 0
10 0
11 0
12 0
13 0
14 0

HO
PREP
QCI SUCC
-----------
0 0
1 0
2 0
3 0
4 0
5 0
6 0
7 0
8 0
9 0
10 0
11 0
12 0
13 0
14 0

Blinq eNB#

6.2.3 Events
Via the CLI, the FW-300i presents a table of the last 1000 events generated on the node.
In the CLI, you use the “show” command to view the events.
Each event contains the following information:
 index — The event index number.
 module-id — The module identification (MAC address) of the module generating the event.
 component-name — The name of the affected component on the module.
 event-id — The numeric event identifier. This is used to map the event to documentation.
 category — The category of the event (set, clear or message).
 type — The event type.

Confidential - Restricted Use and Duplication 98 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 probable-cause — The probable cause of the event.

 severity — The severity of the event (info, warning, minor, major, critical).
 timestamp — The timestamp from when the event was generated (Date/time string: YYYY-MM-
DDThh:mm:ss[+|-]hh:mm).
 notification-id — The event notification identification (ID) number. The event notification ID is a
monotonically increasing number which supports event tracking.
 comment-data — Textual data providing additional information about the cause of the event.
Note: You can search the events by any of the above parameters, for instance, severity:
Blinq eNB# show event-history event severity ?
Description: Severity
Possible completions:
critical info major minor warning
Remember: There are 1000 stored events, so it is a long list to scan; therefore it is highly recommended
that you search by one of the criteria listed above.
Show example:
Blinq eNB# show event-history
event-history event 57427
module-id 0c:a1:38:00:04:06
component-name "RNTI 1060"
event-id 12003
category msg
type operational-status
probable-cause operating-mode
severity info
timestamp 2018-08-31T19:02:12-05:00
notification-id 49
comment-data "UE Detached"
event-history event 57428
module-id 0c:a1:38:00:04:06
component-name "RNTI 1097"
event-id 12003
category msg
type operational-status
probable-cause operating-mode
severity info
timestamp 2018-08-31T19:02:12-05:00
notification-id 50
comment-data "UE Detached"
event-history event 57429
module-id 0c:a1:38:00:04:06
component-name "RNTI 1208"
event-id 12003
category msg
type operational-status
probable-cause operating-mode
severity info
timestamp 2018-08-31T19:02:12-05:00
notification-id 51
comment-data "UE Detached"
event-history event 57430
module-id 0c:a1:38:00:04:06
component-name "RNTI 1542"

Confidential - Restricted Use and Duplication 99 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

event-id 12003
category msg
type operational-status
probable-cause operating-mode
severity info
timestamp 2018-08-31T19:02:12-05:00
notification-id 52
comment-data "UE Detached"
event-history event 57431
module-id 0c:a1:38:00:04:06
component-name "RNTI 2134"
event-id 12002
category msg
type operational-status
probable-cause operating-mode
severity info
timestamp 2018-08-31T19:02:12-05:00
notification-id 53
comment-data "UE Attached"
.
.
[…OUTPUT REMOVED FOR SPACE, otherwise it is 1000 events!]

Confidential - Restricted Use and Duplication 100 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

6.3 Troubleshooting
Following is a quick troubleshooting guide:
Table 6-1 Troubleshooting

SYMPTOM POSSIBLE CAUSE SOLUTION

STATE LED stuck Operating system (OS) or Reboot unit. If problem persists over multiple
continuously on red configuration mismatch preventing reboots, remove and return the unit to BLiNQ
or amber the unit from entering functional Networks
state Contact BLiNQ Networks to arrange for a
replacement
FW-300i unable to Incorrect/missing gateway Verify the gateway configuration for FW-300i
form SCTP link with configuration management IP address
EPC Wrong MME IP address set Verify the MME IP address and SCTP port
number settings on FW-300i
SCTP association not set in EPC Verify SCTP interface configuration on EPC
Wrong eNB ID set on EPC Verify eNB settings on EPC which may be causing
the SCTP association request to be rejected
CPE unable to form Link is down due to loss of GPS Reboot the FW-300i
link with FW-300i sync
Wrong RF channel number Verify the RF channel number configured on CPE
to confirm that it matches to FW-300i
APN misconfiguration Verify the APN configured on CPE is the same as
in the CPE profile on EPC
Incorrect cell range Increase cell range to enable CPE to successfully
perform network entry
CPE unable to pass Link is down Confirm that the RF channel number is correctly
data traffic or access configured on CPE. Restart CPE to trigger
internet network entry again
Link quality is poor Analyze the link performance metrics (RSRP,
CINR, Tx Pwr) on the CPE to determine if it’s
being served by the best available sector.
Antenna orientation optimization may be
required
Wrong mode of operation Verify that the CPE is operating in NAT mode
EPC misconfiguration Verify the RAN, CN and NAT interface definition
for the MGW on EPC
Verify the DNS server and routing table
configuration on EPC

Confidential - Restricted Use and Duplication 101 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

7 Customer Premise Equipment (CPE)

BLiNQ Networks offers a wide variety of CPEs, designed to meet your needs. Please contact BLiNQ for
more information.
You can also use a third party CPE to connect to the FW-300i. If so, please consult your third party CPE
manual for details on this equipment or the relevant CPE Configuration Manual.

Confidential - Restricted Use and Duplication 102 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Appendix A BLiNQ Wireless Devices and RF

Safety/Les appareils sans fil BLiNQ et la sécurité
RF

REMARQUE: La traduction française suit le texte anglais.

BLiNQ Networks evaluates all of its products to ensure that they conform to the Radio Frequency (RF)
energy emission safety limits adopted by the Federal Communications Commission (FCC). BLiNQ
Networks conducts these evaluations using the compliance rules and guidelines adopted by both the
FCC and Industry Canada. They are based on the results of the Maximum Permissible Exposure (MPE)
studies by the FCC for mobile or fixed devices, which dictate MPE limits for human exposure to RF
energy.
Before selling any wireless networking device to the public, BLiNQ Networks submits its devices to the
FCC and Industry Canada for MPE (that is, RF emissions) studies and evaluation. These studies must
demonstrate that the device meets the accepted regulatory limits for safe RF emissions, or it is not
approved for sale by the FCC and thus cannot be sold to the public. This means that when wireless
networking devices, purchased from BLiNQ Networks, are installed and operated as instructed, the RF
emissions from the devices is equal to or less than the levels accepted as safe by the FCC and Industry
Canada.
When used as intended, BLiNQ wireless networking devices do not pose health risks. Like other devices
that emit RF energy (such as computers and microwave ovens), the level of RF emissions from BLiNQ
devices is too low to cause harm. Further, BLiNQ wireless networking devices emit far lower levels of RF
energy than cellular and cordless telephones, and are almost always used further away from the human
body.
To prevent unnecessary exposure to RF energy:
 Always install the FW-300i system so as to provide and maintain a minimum separation distance of
at least 1.1 metre from all persons.
 When the FW-300i system is operational, avoid standing directly in front of the FW-300i antennas.
RF energy fields may be present when the transmitter is on.

Confidential - Restricted Use and Duplication 103 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

 When the FW-300i system is operational, maintain a distance of at least 1.1 metre (43.3 inches)
from the FW-300i antennas.
 Do not install the FW-300i system in a location where it is possible for people to stand or walk
inadvertently in front of an antenna.
Antenna Statement:
The antenna used for this transmitter must be installed to provide a separation distance of at least 1.1
metre (43.3 inches) from all persons and must not be co-located or operating in conjunction with any
other antenna or transmitter. Users and installers must be provided with antenna installation
instructions and transmitter operating conditions for satisfying RF exposure compliance.

BLiNQ Networks évalue l'ensemble de ses produits afin de s'assurer qu'ils sont conformes à la limite
d'émission énergétique sécuritaire de radiofréquence (RF) adoptée par la «Federal Communications
Commission» (FCC). BLiNQ Networks effectue ces évaluations en utilisant les règles et lignes directrices
adoptées à la fois par le FCC et Industrie Canada. Elles sont basées sur les résultats de l'exposition
maximale admissible, études menées par le FCC sur les appareils mobiles ou fixes, qui dictent les limites
de l'exposition maximale admissible pour l'exposition humaine aux énergies RF.
Avant de vendre tout appareil de réseau sans fil au public, BLiNQ Networks présente ses appareils au
FCC et à Industrie Canada pour l'évaluation de l'exposition maximale admissible. Ces études doivent
démontrer que l'appareil est conforme aux limites réglementaires acceptées pour les émissions RF,
sinon les appareils ne sont pas approuvés pour la vente par la FCC et ne peuvent donc pas être vendus
au public. Cela signifie que lorsque des équipements sans fil, achetés auprès de BLiNQ Networks, sont
installés et utilisés conformément aux instructions, les émissions RF provenant des dispositifs sont
inférieures ou égales aux niveaux acceptés comme étant sécuritaire par la FCC et Industrie Canada.
Lorsqu'utilisés comme prévu, les périphériques sans fil BLiNQ ne posent pas de risques pour la santé. De la
même façon que les autres appareils qui émettent de l'énergie RF (comme les ordinateurs et les fours à
micro-ondes), le niveau des émissions RF des dispositifs BLiNQ est trop faible pour causer des dommages.
En outre, les dispositifs de réseau sans fil BLiNQ émettent des niveaux beaucoup plus faibles d'énergie RF
que les téléphones cellulaires et sans fil, et sont presque toujours utilisés loin du corps humain.
Pour éviter toute exposition inutile à l'énergie RF:
 Installer toujours le système FW-300i afin de fournir et de maintenir une distance de séparation
minimale de 1.1 mètre au moins pour les personnes.
 Lorsque le système FW-300i est opérationnel, éviter de se tenir directement devant les antennes du
FW-300i et leurs antennes internes. Les champs d'énergie RF peuvent être présents lorsque
l'émetteur est en marche.
 Lorsque le système FW-300i est opérationnel, maintenir une distance d'au moins 1.1 mètre (43.3
pouces) à partir des antennes du FW-300i.
 Ne pas installer le système FW-300i dans un endroit où il est possible pour les gens de se tenir
debout ou de marcher en face d'une antenne.
Déclaration d’antenne:
L'antenne utilisée pour cet émetteur doit être installé de façon à créer une distance de séparation d'au
moins 1.1 mètre (43.3 pouces) de toute personne et ne doit pas être co-localisées ou opérant en
conjonction avec une autre antenne ou émetteur. Les utilisateurs et les installateurs doivent avoir reçus
des instructions d'installation de l'antenne et des conditions de fonctionnement de l'émetteur pour
satisfaire la conformité aux expositions RF.

Confidential - Restricted Use and Duplication 104 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

A.1 Equipment Compliance

A.1.1 Federal Communications Commission (FCC) Notices

This equipment has been tested and found to comply with the limits for a Class B digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against
harmful interference in a residential installation. This equipment generates, uses and can radiate radio
frequency energy and, if not installed and used in accordance with the instructions, may cause harmful
interference to radio communications. However, there is no guarantee that interference will not occur
in a particular installation. If this equipment does cause harmful interference to radio or television
reception, which can be determined by turning the equipment off and on, the user is encouraged to try
to correct the interference by one or more of the following measures:
 Reorient or relocate the receiving antenna.
 Increase the separation between the equipment and receiver.
 Connect the equipment into an outlet on a circuit different from that to which the receiver is
connected.
 Consult the dealer or an experienced radio/TV technician for help.
This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions:
(1) This device may not cause harmful interference, and
(2) This device must accept any interference received, including interference that may cause
undesired operation.

CAUTION: Any changes or modifications not expressly approved by BLiNQ Networks could void the
user's authority to operate this equipment.

Confidential - Restricted Use and Duplication 105 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Appendix B PCI Planning Guidelines

When setting up your system, you must abide by the rules outlined below in order to minimize Physical
Cell ID (PCI) collision and enforce an effective PCI assignment strategy:
Rule 1: Same PCI Utilization
 Multiple cells within a FW-300i on the same frequency should not have the same PCI
 Immediate neighbour cells on the same frequency should not have the same PCI
Rule 2: PCI MOD3
 Cells on the same frequency within a similar coverage area must not have the same PCI MOD3
(i.e., PCIcellA != PCIcellB)
 Occurs due to the fact that when PCI X is changed by a factor of X+3n (where n is an integer)
there is a collision on the reference signals between the two antenna ports, i.e., between the
PCI[X]-antenna port0 and PCI[X+3n]-antenna port1
 Applicable for MIMO transmission only
Rule 3: PCI MOD6
 Cells on the same frequency within a similar coverage area must not have the same PCI MOD6
 Applicable for SISO transmission only
Rule 4: PCI MOD30+
 Cells on the same frequency within a similar coverage area must not have the same PCI MOD30
 Occurs due to the collision of the uplink (UL) reference signals (RS) which leads to a higher bit
error rate (BER) in the UL
Rule 5: PCI MOD50 (20MHz Bandwidth (BW)) or PCI MOD25 (10MHz BW)
 Cells on the same frequency within a similar coverage area must not have the same PCI
MOD50/MOD25
 Occurs due to the collision on the Physical Control Format Indicator Channel (PCFICH) which
leads to failure in decoding on the Physical Downlink Control Channel (PDCCH)

Confidential - Restricted Use and Duplication 106 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Rule 6: Cell Group ID Correlation

 Cell Group ID is derived from two length-31 binary m-sequences (m0, m1)
 Each time m0/m1 repeats, the overall correlation between the two Cell Group ID values is
higher
 No impact to the performance of Key Performance Indicators (KPI) due to this type of
interference
 Only causes network entry delay (by 5-10ms)

Confidential - Restricted Use and Duplication 107 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Appendix C Alarms and Events (Fault

Management)

This appendix lists the alarms and events for the BLiNQ FW-300i system.
Note: There is no need to open the FW-300i module casing. If there is an unsolvable problem or a
module malfunction, please contact our Customer Service Department for help or a return merchandise
authorization (RMA) number/procedure.
The FW-300i system issues an alarm notification when a fault condition occurs. You view alarms through the:
 FW-300i WebUI Events > Alarms page (See Section 6.1.3.1, “Alarms (Logs) Page”) or
 on the CLI via the “show event-history” command (See Section 6.2.3, “Events”).
These alarms require operation and maintenance actions to restore functionality and/or to prevent a
more serious situation from developing.
Table C-1, List of Alarms shows each alarm (whose name also represents the particular problem), the
alarm ID, type and explanation on the likely cause of the alarm and possible solution (as applicable).
The FW-300i system issues an event notification when something of importance happens that does not
trigger an alarm, but is considered significant enough to take note. You view these events through the:
 FW-300i WebUI Events > History page (See Section 6.1.3.2, “History Page”) or
 On the CLI via the “show event-history” command (See Section 6.2.3, “Events”).
Table C-2, List of Events shows each event (whose name also represents the particular problem), the
event ID, type and explanation on the likely cause of the event.
Severity is also defined for each listed alarm and event, to indicate the relative level of urgency for
operator action:
 CRITICAL — the alarm or event requires immediate corrective action, regardless of the time
 Major — the alarm or event requires immediate corrective action, within working hours
 Minor — the alarm or event requires corrective action at a suitable time or, at least, continuous
close observation
 Warning — the alarm or event requires corrective action on a scheduled maintenance basis
 Information — the alarm or event requires no corrective action; it is for informational purposes only

Confidential - Restricted Use and Duplication 108 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Table C-1 List of Alarms

ID NAME DESCRIPTION/COMMENTS TYPE SEVERITY

1
4001 Ethernet Port Down Ethernet link is down, can be caused by Eth Comms . Major
cable unplugged or connected port
defective, administratively disabled,
equipment down, etc. System recovers
when Ethernet link is re-established.
2
5004 Radio Disabled An operator has administratively disabled Equip. Major
the radio in the unit. Identified per sector.
5006 Radio Module Down Configuration issue e.g. radio enabled but Equip. Major
not used by any sector. Identified per RF
instance.
5008 Radio Temperature The radio operating temperature has Equip. Major
Warning exceeded the normal operating range.
Identified per sector.
5009 Radio RF Calibration This alarm usually indicates a hardware Equip. CRITICAL
failure. The unit should be replaced.
Identified per RF instance.
5014 Radio DCA No Frequency The system is using all the available Comms. Minor
Available frequency channels and pauses the jump
sequence to prevent flip-flopping.
6002 GPS Antenna Failure This indicates a hardware fault with the GPS Equip. CRITICAL
antenna of the FW-300i.
6003 Hardware Temperature The alarm triggers with 2 severity levels: Equip. Major/
- Major - this warns that temperature is CRITICAL
above normal range (85C) and
- Critical - when the temperature exceeds
safety limits and the radio is stopped (90C).
6004 Phy Start Issue Failure to load or start the PHY code. Comms. CRITICAL
6005 RF Power Amp Issue 1611 could not start, power failure or other Equip. CRITICAL
issue
6006 CA Chain Issue RF card not Carrier Aggregation (CA) Comms. CRITICAL
capable. Badly configured CA chain.
7001 System GPS When operating in GPS mode, the GPS Comms. Major
Synchronization Lost receiver has lost synchronization. When
operating in 1588 mode, the 1588 client has
lost communication with the 1588 master
clock.
Upon FW-300i reset, this alarm is not raised
until 60 s after reset and if synchronization
still is not achieved. After holdover time
expires (5 minutes), system transitions to
unsynchronized state.

1
Comms = Communications
2
Equip. = Equipment

Confidential - Restricted Use and Duplication 109 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

ID NAME DESCRIPTION/COMMENTS TYPE SEVERITY

7002 System Synchronization When operating in GPS mode, the GPS Equip. CRITICAL
Failed receiver has lost synchronization. When
operating in 1588 mode, the 1588 client has
lost communication with the 1588 master
clock. This alarm is raised when the module
fails to achieve system timing
synchronization. Probably caused by a loss
of signal.
7006 Sync E Unreliable The provider of SyncE connected to the Comms. CRITICAL
FW-300i is either malfunctioning or not
configured to provide SyncE on the FW-300i
connection port.
7010 DHCP Server Unavailable The system has not been able to obtain a Comms. Major
DHCP address.
9003 PM Automatic File The unit could not perform the FTP transfer Comms. Minor
Upload Failure of the performance data. The FTP system is
inaccessible. (Module cannot upload PM
files to the specified server. Indicates a
server connectivity or access error. System
recovers when connectivity/access to the
PM server is restored.)
11001 SAS Server Registration Registration with SAS server failed. Comms. CRITICAL
Failure (CBSD)
11002 Grant Suspended or Grant was suspended or terminated by SAS Comms. CRITICAL
Terminated (CBSD) server.

Confidential - Restricted Use and Duplication 110 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Table C-2 List of Events

ID NAME DESCRIPTION/COMMENTS TYPE SEVERITY

2001 Configuration Changed A configuration change has been committed System Information
to the running configuration.
3001 Software Download Downloading software image. System Information

3002 Software Download Successful download of software image. System Information

Successful
3003 Software Download Error Software error: A software download is System Minor
already in progress.
3004 Software Boot Failure This may indicate a physical or logical Equip. CRITICAL
corruption of the system non-volatile
storage.
5004 Radio Module Disabled Radio Module is initialized and has received Equip. Information
an administrative disable configuration.
7003 System Synchronized GPS entered synchronized state. Equip. Information

7004 GPS State Change The GPS state machine gained or lost GPS Equip. Information
synchronization (specific state indicated by
the comment text).
8001 Authentication Failed Attempts to authenticate on one of the Security Warning
management interfaces of the equipment
failed.
1
10001 License successfully applied A license was successfully applied to System Major
module.
1
10002 Invalid license Invalid license: Digital signature does not System Major
match license content.
1
10003 License not applicable License not applicable to module: MAC System Major
address does not match filter or license
capabilities do not match the hardware.
12001 S1 State Enabled Event (ENB) S1 State Enabled System Information

12002 UE Attached Event (ENB) User Equipment (UE) Attached System Information

12003 UE Detached Event (ENB) UE Detached System Information

1
Future Software Release

Confidential - Restricted Use and Duplication 111 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

Appendix D List of Acronyms

ACRONYM MEANING
3CC Three Component Carriers
3GPP Third Generation Partnership Project
AAA Authentication, Authorization and Accounting (centralized networking protocol)
AAS Active Antenna System
ACK Acknowledgment
AES Advanced Encryption Standard
AF Assured Forwarding behavior, DSCP
APN Access Point Name
ANR Automatic Neighbour Relation
ARP Address Resolution Protocol
ARQ Automatic Repeat Request
ATP Automatic Transmit Power
BCCH Broadcast Channel
BER Bit Error Rate
BMC Best Master Clock
BSI Best Signal Indication
BSR Buffer Status Report
BTS Base Transceiver Station
BW Bandwidth
CAC Call Admission Control
CBRS Citizens Broadband Radio Service
CBSD Citizens Broadband Radio Service Device
CC Component Carrier
CDB Common Database
CINR Carrier to Interference plus Noise Ratio
CIO Cell Individual Offset

Confidential - Restricted Use and Duplication 112 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

ACRONYM MEANING
CIR Committed Information Rate
CLI Command Line Interface
CPE Customer Premise Equipment
CPI Certified Professional Installer
CPIR-ID Certified Professional Installer Registration Identification
CQI Channel Quality Indicator
Craft IP IP address typically used by technical personnel to test the equipment
CRC Cyclic Redundancy Check
CS Class Selector, DSCP
CTX Channel Transmit
CW Continuous Wave (carrier)
dBi Decibel isotropic
DBS Dynamic Bandwidth Sharing
DCA Dynamic Channel Assignment
DHCP Dynamic Host Configuration Protocol
DL Downlink
DRX Discontinuous Reception
DSCP Differentiated Services Code Point
DSR Diameter Signaling Router
DSN Domain Name System
EARFCN Evolved Absolute Radio Frequency Channel Number (LTE)
EF Expedited Forwarding behavior, DSCP
eICIC Enhanced Inter-Cell Interference Coordination
EIRP Equivalent/Effective Isotropic Radiated Power
EMS Element Management System
eNB See eNodeB
eNodeB E-UTRAN Node B, also identified as Evolved Node B (abbreviated as eNodeB or eNB) is an
element of an LTE Radio Access Network (RAN)
EPC Evolved Packet Core
EPRE Energy Per Resource Element
ETWS Earthquake and Tsunami Warning System
EUTRAN Evolved Universal Terrestrial Radio Access Network
FCAPS Fault, Configuration, Accounting, Performance, and Security
FCC Federal Communications Commission
FDE Frequency Domain Equalized
FTP File Transfer Protocol
FWA Fixed Wireless Access
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
GPS Global Positioning System
GTP GPRS Tunneling Protocol

Confidential - Restricted Use and Duplication 113 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

ACRONYM MEANING
HARQ Hybrid Automatic Repeat reQuest
HD High Density
HLR Home Location Register
HO Handover
HTTP Hyper Text Transfer Protocol
HTTPS Hyper Text Transfer Protocol Secure
ICIC Inter-Cell Interference Coordination
IEEE Institute of Electrical and Electronics Engineers
IMEI International Mobile Equipment Identity
IMSI International Mobile Subscriber Identity
IP Internet Protocol
ISDN Integrated Services Digital Network
Kbps Kilobits per second
KPI Key Performance Indicators
L2 Layer 2
LL Low Latency
LLDP Link Layer Discovery Protocol
LOS Line-of-Sight
LTE Long Term Evolution refers to a mobile device, high-speed, wireless communications standard.
MAC Media Access Control
Mbps Megabits per second
MCC Mobile Country Code
MCS Modulation and Coding Scheme
MHz Megahertz
MGP Measurement Gap Configuration Pattern
MIMO Multiple Input Multiple Output
MIMO-SM Multiple Output-Spatial Multiplexing
MME Mobility Management Entity; the key control-node for the LTE access-network
MNC Mobile Network Code
MPE Maximum Permissible Exposure
MPLS Multiprotocol Label Switching
ms or msec Millisecond
MSB Most Significant Bit
MSISDN Mobile Subscriber ISDN Number
MSR Multi-Standard Radio
MU-MIMO Multiple-user Multiple Input Multiple Output
NACK negative acknowledgment
NETCONF Network Configuration Protocol
nLOS near Line-of-Sight
NLOS Non Line-of-Sight
NMS Network Management System

Confidential - Restricted Use and Duplication 114 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

ACRONYM MEANING
NOM Network Operations Mode
OAM Operations, Administration and Maintenance
OLLA Outer Loop Link Adaptation
OSS Operations Support System
PBCH Physical Broadcast Channel
PCCH Paging Control Channel (PCCH)
PCFICH Physical Control Format Indicator Channel
PDCCH Physical Downlink Control Channel
PDCP Packet Data Convergence Protocol
PDN Packet Data Network
PDSCH Physical Downlink Shared Channel
PHICH Physical Hybrid-Automatic Repeat Request (ARQ) (HARQ) Indicator Channel
PHR Power Headroom Report
PHY Physical Layer
PLMN-ID Public Land Mobile Network Identifier (PLMN-ID = MCC + MNC)
PM Performance Measurement
PMI Precoding Matrix Indicator
PMP Point-to-Multipoint
PPS Pulse Per Second
PRACH Physical Random Access Channel
PSS Primary Synchronization Signal
PTP Point-to-Point
PUCCH Physical Uplink Control Channel
PUSCH Physical Uplink Shared Channel
QAM Quadrature Amplitude Modulation
QoS Quality of Service
QPSK Quadrature Phase Shift Keying
RACH Random Access Channel
RAN Radio Access Network
RARP Reverse Address Resolution Protocol
RAT Radio Access Technology
RF Radio Frequency
RI Rank Indication
RLC Radio Link Control
RNTI Radio Network Temporary Identifier
ROHC Robust Header Compression
RRC Radio Resource Control
RS Reference Signal
RSSI Received Signal Strength Indicator
RSCP Received Signal Code Power
RSRQ Reference Signal Received Quality

Confidential - Restricted Use and Duplication 115 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

ACRONYM MEANING
RSRP Reference Signal Received Power
RTP Received Target Power
RX Received
s second
S1 Interface between an eNB and the Core Network (CN)
SAS Spectrum Access System
SCH Shared Channel
SCTP Stream Control Transmission Protocol
SeGW Security Gateway
SFP Small form-factor pluggable
SFTP Secure File Transfer Protocol
SGW Serving Gateway; routes and forwards user data packets, also acts as mobility anchor
SI System Information
SIB3 System Information Block type 3
SIM Subscriber Identity Module
SINR Signal to Interference plus Noise Ratio
SISO Single Input Single Output
SLA Service Level Agreement
SMC Security Mode Command
SNMP Simple Network Management Protocol
SON Self-Organizing Network
SPS Semi-Persistent Scheduling
SR Scheduling Request
SRB Signaling Radio Bearer
SRS Sounding Reference Signal
SSH Secure Shell protocol
SSS Secondary Synchronization Signal
S-VLAN Stacked VLAN
SW Software
TAC Tracking Area Code
TAI Tracking Area Identifier
TCP Transmission Control Protocol
TCP/IP Transmission Control Protocol/Internet Protocol
TDD Time Division Duplexing
TDM Time Division Multiplexed
TM Transmission Mode
ToS Type of Service
TPC Transmit Power Control
TTI Transmission Time Interval
TTW Time To Wait
TX Transmit

Confidential - Restricted Use and Duplication 116 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

ACRONYM MEANING
UDP/IP User Datagram/Internet Protocol
UE User Equipment
uint16 Unsigned 16-bit integer with specified range, if any
Uint32 Unsigned 32-bit integer with specified range, if any
uint8 Unsigned 8-bit integer with specified range, if any
UL Uplink
UMTS Universal Mobile Telecommunications System
U-NII Unlicensed National Information Infrastructure
URL Universal Resource Locator
UTC Coordinated Universal Time
UTRAN UMTS Terrestrial Radio Access Network
VDC Volts Direct Current
VLAN Virtual Local Area Network
VSWR Voltage Standing Wave Ratio
WFP Weighted Fair Priority
X2 Interface that interconnects eNBs
XPIC Cross Polarization Interference Cancellation

Confidential - Restricted Use and Duplication 117 Issue 02

BLiNQ Networks Inc. FW-300i User Manual Release 2.0

© Copyright 2012-2019 BLiNQ Networks Inc. All rights reserved.

CONFIDENTIAL INFORMATION
RESTRICTED USE AND DUPLICATION
The information contained herein is the property of BLiNQ Networks Inc. and is strictly confidential. Except as expressly
authorized in writing by BLiNQ Networks Inc., the holder shall keep all information contained herein confidential, shall disclose
it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third
parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care.
Except as expressly authorized in writing by BLiNQ Networks Inc., the holder is granted no rights to use the information
contained herein.
BLiNQ and BLiNQ Networks Inc. corporate logo are trademarks of BLiNQ Networks Inc. All other trademarks used in this
document are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between BLiNQ and any other company.

Disclaimer
The statements, configurations, technical data, and recommendations in this document are believed to be accurate and
reliable, but are presented without express or implied warranty. Additionally, BLiNQ Networks makes no representations or
warranties, either expressed or implied, regarding the contents of this product. BLiNQ Networks shall not be liable for any
misuse regarding this product. The information in this document is subject to change without notice.

Confidential - Restricted Use and Duplication Issue 02