BQN Documentation
BQN Documentation


How to Update the Software

The update of a bqn package (e.g.,bqn-R4.0.24.bpkg) consists of two steps: first it is installed and then it is activated. The activation involves a traffic interruption of some seconds, so it is advisable to carry it out at times of low throughput.

The installation is performed in Administration->Software, clicking on the ⁝ menu icon and selecting Install… A file selector pops up to choose the package, that it is transferred to the BQN server and installed.

The activation is done in Administration->Software clicking on the ↶ arrow icon of the package to activate (highlighted in red in the picture below).

This operation forces you to log back into the BQN after a few seconds, during which time, the traffic flow is interrupted.

How to Generate a Diagnostic

When requested by Bequant support, a diagnostic file can be generated in Administration->Diagnostic.

The file will be placed in the download folder of the browser being used.

How to Back up the Configuration

You can save the server configuration to a local file in Administration->Backup->Save.

To restore it, pick a previous backup file in option Administration->Backup->Load.

It is strongly recommended that you load the configuration always without overwriting management address and wire configuration, so the interface configuration is not lost when transferring configuration from one BQN server to another.

Monitoring with SNMP

The BQN supports the following SNMP v2c alarms (traps):

  • Cpu: excessive server CPU load.
  • Memory-dpdk: excessive memory usage in DPDK packet processing.
  • Memory-pool: excessive memory usage in BQN general memory pool.
  • Disk: file system full or almost full.
  • Process: some mandatory processes down.
  • Traffic-uplink: no traffic in the uplink direction.
  • Traffic-downlink: no traffic in the downlink direction.
  • Traffic-low: low traffic (uplink and downlink directions combined).
  • Traffic-inverted: uplink throughput higher than downlink throughput (possibly because some wires are inverted, with access port connected to the Internet and vice versa).
  • Wire: no wires configured or some wires down.
  • License-available: no license defined or license invalid.
  • License-expiration: license has expired.
  • License-usage: server throughput is above the license capacity.
  • Time: no NTP server configured or not reachable.
  • Bqnmgr: BQN remote management system not reachable.

These alarms are related to the dashboard shown in BQN homepage. See the Troubleshooting section for more information.

To configure the SNMP agent, log via SSH as an administrator:

bqnadm@bqn0# configure
bqnadm@bqn0(config)# snmp
bqnadm@bqn0(config-snmp)# community <community-string>
bqnadm@bqn0(config-snmp)# trap-v2c <nms-ip-address>
bqnadm@bqn0(config-snmp)# commit
bqnadm@bqn0(config-snmp)# end
bqnadm@bqn0# exit

Where community-string is the SNMP community to be used by the BQN and nms-ip-address the IP address of the network management system to which to send the notifications.

The BQN SNMP also exports some system statistics. To get the BQN MIB files, contact Bequant support.