Booster Setup

Everything you need to set up your Booster Environment

Booster System Requirements

Requirements

As of May 2023 v15.0.1 the below are supported for running Boosters, but for updated information always consult the specific release on the Downloads Page. The FileWave Booster can also be installed on a Virtual Machine.

The general guidance on CPU / RAM / Network / Storage is:

Make sure you have enough space on your hard disk to store the cached Filesets for your FileWave Clients. A Booster could conceivably contain a full mirrored set of all Filesets on the main FileWave server.

Booster Installation

Description

Booster software is compatible with either macOS, Windows or Debian.  All necessary installers or appliances can be found on the current download pages: FileWave Software Downloads

Installers

Debian

Linux has two options.  FileWave provides (as with the FileWave Server) a pre-built Debian VM.  Alternatively, it is possible to self-install the software on a Debian system.

macOS & Windows

Installers are available as PKG or MSI.

As typically with MSI installers, options exist not only for install, but repair and deletion

Install Paths

Booster installs the software to one of the following locations:

Booster Configuration

Once installed, configuration is via the Booster Monitor application, available for both macOS and Windows from the same downloads page.

Note that the standalone application, Booster Monitor, will only be able to connect to a Booster for initial configuration. Once a Booster is configured you must access Booster Monitor from FileWave Central in the Boosters section. This is because authentication is protected, and the FileWave Central application provides a secure connection. Launching Booster Monitor directly would not have that same authentication, and you will see an error about the Booster not running.

Installation

Debian

If using the pre-built Debian Appliance, simply add the VM to the VM infrastructure.  Alternatively, follow the commands provided on the downloads page.

macOS & Windows

Run the relevant PKG or MSI installer, accepting any terms and agreements.

Custom Installers may be created, pre-defining details, e.g. Server Address, Port and Booster Monitor Preferences password: Custom Installers

Configuration

Network Address

Configure a static IP for the Booster and consider adding a Domain Name within the DNS for this IP.

macOS and Windows can be configured using the Settings.  However, Debian will require some command line configuration.

Debian IP Setup
Network Interface

The current IP may be determined with the 'ip addr' command:

# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:0c:29:9d:4d:7e brd ff:ff:ff:ff:ff:ff
    altname enp11s0
    inet 192.168.1.98/24 brd 192.168.1.255 scope global dynamic ens192
       valid_lft 68853sec preferred_lft 68853sec
    inet6 fe80::20c:29ff:fe9d:4d7e/64 scope link 
       valid_lft forever preferred_lft forever

The key part here is the name of the network interface.  In the above example, this is 'ens192'.

Edit Network File

Make a backup of the current file:

cp /etc/network/interfaces /etc/network/interfaces-mybackup

Edit the original file:

sudo nano /etc/network/interfaces

Add the chosen IP and other necessary details for this interface.  Given the details above, it may look something like the below once edited:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
iface ens192 inet static
address 192.168.1.22
netmask 255.255.255.0
gateway 192.168.1.255
dns-nameservers 8.8.4.4 8.8.8.8

Once complete, save and then restart the network service:

sudo systemctl restart networking

Re-running the 'ip addr' command should now show the new details.

Add a name with this IP on the DNS.

Booster Setup

Install the Booster Monitor on a chosen macOS or Windows device.  On launching the Booster Monitor, use the above created network address.  The initial view is akin to the FileWave Client Monitor, but with Booster specific details:

image.png

Select Preferences, enter the created password (or default password as provided from the downloads page)

Consider changing this password at the earliest possible moment

This password is only used to access the Preferences from the Booster Monitor.

The Booster Monitor may then be used to configure the Booster.  At a very basic level, the Server Address and port should be added.

image.png

Approving Boosters

Once a Booster is setup on the network with the relevant FileWave Server details, it should then check-in with the server and be visible in the Booster section of the FileWave Central admin application software.

As of FileWave 13.1.0, additional security and certificates were introduced, requiring the approval process.

cert_not_installed.png

The approval process generates a certificate for the Booster.  There are four ways to generate a certificate for a booster.

  1. Select booster(s) in the Booster view → right-click → Create Certificate/Enroll Booster
  2. Select booster(s) in the Booster view → Create Certificate/Enroll Booster (in the button bar)
  3. Select booster(s) in the Booster Details → right-click → Create Certificate/Enroll Booster
  4. Select booster(s) in the Booster Details → Create Certificate/Enroll Booster (in the button bar)

Server_certs.gif

Booster Deletion

If a Booster were deleted from FileWave, this will revoke the certificate.  If still running, on a subsequent check-in, the approval process should need to be re-actioned.

Booster Monitor and Configuration Settings

Booster Monitor

Booster Status Monitor.png

When you first launch Booster Monitor, it will attempt to connect to the Booster at the default address of 127.0.0.1 with the assumption that you are running the monitor on the system you installed it on. You can change that address to any valid IP address or FQDN of a Booster you have installed. If you try to connect to a Booster from FileWave Central on the list of Boosters, and it won’t connect you should check what IP it lists there for the Booster. For some network setups, the FW server may see the Booster coming from a different address than what your clients connect to it on.

Note that the standalone application, Booster Monitor, will only be able to connect to a Booster for initial configuration. Once a Booster is configured you must access Booster Monitor from FileWave Central in the Boosters section. This is because authentication is protected, and the FileWave Central application provides a secure connection. Launching Booster Monitor directly would not have that same authentication, and you will see an error about the Booster not running.

The default password will be "filewave" or if you used the https://custom.filewave.com website, it may be "f1lewav3" or whatever you set it to.

Once you have connected with your Booster, you will see its Status Monitor window. The status window lets you see the current settings and cache of the Booster.

You can set the Booster preferences to choose how the Booster can be reached, how it works with other Boosters, the main FileWave Server, and how it handles network traffic.

Booster Prefs

FileWave Booster Preferences 2023-03-27 at 3.43.59 PM-20230327-194401.jpg

Booster Server Prefs

These settings are where you build your distribution "tree" by assigning where this Booster connects. This specifies the order in which connection attempts will be made. The best way to set this up is to follow these guidelines:

Configuring Clients to use Boosters for Server Messages

To activate the server message routing functionality introduced with FileWave 11, you must enable it using either the option on the Booster page of Superprefs or Client Preferences. More detail on this feature is here: What are "Server Messages" and why do I want them?

image.png

Boosters View

Boosters View.png
On the above screenshot you can see new options in the Boosters tab in Boosters view:

"Device Name" column contains the name of the Booster. This is configured in Booster's preferences.
"Booster Status" column indicates green/orange/red icon based on last check-in time:

"Next Scan Start Time" column indicates the start time of the next scan
"Requests per Second" column indicates the number of Booster requests per second within the last 15 minutes. Additionally, Booster statistics are sent by the Booster every 15 minutes at fixed times e.g. 0:00, 0:15, 0:30, 0:45.
"Booster Overload" column indicates if there are any clients' requests that couldn't be served by Booster. This doesn't necessarily mean the Booster is failing; it simply implies that the client has been told to retry later.
"Location" column contains location configured in Booster's preferences.

View Modes

The Boosters view offers two primary view modes: the Cards view (which requires OpenGL on the administrator machine running FileWave Admin) and the Details view. These modes operate independently. Double-clicking on a Booster in either view opens the Booster Monitor for that particular Booster.
View Modes.pngBooster_Warning.png

In the Cards view, each Booster is displayed as a card, with just an overview of its status. Besides using the contextual menu, on the top-right corner of each card there are two gears that when clicked open the same menu.
When the Booster Details tab is clicked on, the Boosters tab switches to the Details view. In this mode, a list with many columns is displayed instead:

Booster Details.png

Device Details - Booster Client Preferences Reporting

What

Want to ensure that your clients are connected to your boosters? Maybe even ensure your FileWave Clients are configured with the proper FileWave tickle time interval, is the “Route server messages via boosters” checked, or the current upstream is reporting to the correct server? FileWave can report these data values with custom fields.

When/Why

After you have set up boosters, you may want to wonder if these clients are connecting to them. With custom fields, we can report and gather inventory data from the device details to confirm that clients are indeed communicating with the FileWave server and your newly configured boosters. In addition, providing other details that can be vital to ensure proper check-in times, routing messaging, upstream server, and even memory usage.

How

Below are the custom fields that may be imported into FileWave Central (native admin). Navigate to Assistants > Custom Fields > Edit Custom Fields… > Import and select the custom fields file to import.

FileWave Download.png

Once imported, you will see listed Client Config fields ready to be assigned to your devices.

ClientConfigs.png

After importing, highlight the Client Configuration field you would like to assign to your devices. Recommend assigning to all devices to confirm that clients are connecting to your Boosters and interval times are set properly. Once you have selected all the Client Configuration fields desired, click on Save.

Give the devices time to check in and acquire the new custom fields to report their data values.

As the device checks in, you may view these custom field values in FileWave Client Info > Device Details. Scroll down through the list for Client Config Booster1, Booster2, etc. to view the data values reported by the client. Below is an example inventory query to view your device booster configurations: routing messages enabled, booster 1, booster 2, and/or booster 3 upstream connections along with the Tickle Interval.

BoosterConfigQuery.png

Note that now that you have these fields you can create queries that show which devices are connected to which Boosters and if any clients are going to the Server when you thought they shouldn’t be. This should be an easy way to show your configuration.

Digging Deeper

These custom fields report the .plist data from the FileWave Client directly so the values will be accurate unless a device has not submitted inventory. Check when it last connected to see if it has and use Verify to ask a device to check in now.