The goal of the BSC is to manage the gateways, supervise their status and collect statistics about them.

A fleet is a collection of gateways.

Through the Dashboard interface, a fleet can be selected via the filtering option Select your fleet:

Once a fleet is selected, the following views are prompted to the interface:

Gives a status summary of each gateway of your fleet

By clicking a particular gateway EUI, you can obtain a high level view of the gateway and its status summary:

By selecting the Statictics menu option, you can get a detailled and historical view of your gateway:

• Link Status
• RAM
• CPU
• Disk (System & User)
• RSSI
• Temperature
• Power supply
• Uplink (from 2.1 release version)
• Downlink (from 2.1 release version)

• File System explorer
• Shell
• Command

The difference between shell and command is that the former is a full interactive shell, while the latter is just a non-interactive command launch.

The interactive shell may have been disabled by your network or security configuration.

Control panel enables to configure

• CPU
• System disk
• Door

By selecting the “Versions” item of the menu options, you can obtain following information:

• information about the current version of the gateway,
• information about older versions of the gateway,
• information about the last software update,

There are 2 ways to perform a Software Update through the Dashboard interface:

1. Software Update by using Drag&Drop feature
2. Software Update by using the Workflow feature

By selecting the “Software update” option, you can execute an update of your gateway:

1. Drag and drop your .tar.gz file to the “File” area
2. Select the date of the update (now or planned for a specific date)
3. Click the “send” button to proceed to the update.

Then confirm the update :

Once the package has been received by the gateway, the following message is prompted to the user:

Then the system reboots to install the new package in the system.

If you don't wait sufficient time before proceeding to the new package update, the following message may be prompted to you:

From RAN 2.1 release version, it is possible to update a group of gateways by using the Workflow feature.

To achieve this function, you should :

1. Create and save your list of stations or load your Cart
2. Execute an updateFirmware workflow

In BSCC menu, click on “Stations” and select the stations you want to add in your cart by clicking on the “Cart button” at the left side of the station's EUI:

Click on the Cart icon located in the upper right side of your web page:

Then, select the “Save cart” icon at the bottom left of your page:

Enter the name of your Cart (mandatory) and a description (facultative):

To ckeck the save operation has been correctly done, select the manage icon in the bottom right of your page:

and check that your Cart has been successfully created:

If your list of stations has been already saved, you can load it to your Cart by 2 manners:

1. from the manage function
2. from the add saved cart function

Select the manage function:

Add the list to your Cart:

View your Cart's content:

Select the “Add saved cart” function:

Select the list to load your Cart:

View your Cart's content:

1. Select the Cart icon
2. Select the Workflow function
3. select the updateFirmware option in the ListItems menu

then select the file used to upgrade the gateway:

then select the execute date:

and select the START button. A message indicates that the workflow has started :

You can see your work in progress by selecting the Worflow feature in the main vertical menu in the left side of your page:

When the process completes, it disappears from the “Workflow processes in-progress” list and is added to the “Workflow processes Ended” list:

The operation result can be viewed by selecting the EUI of your station in the list:

This section lists all the tasks that were run on the station. When clicking on a task, you can see all its messages and SNMP logs.

This section lists all the SNMP requests that were made on the gateway.

It lists all events that were triggered on the gateway.

Events can be alarms (high CPU value for instance) or simple events (station start, door open/closed, etc.).

This section presents the alarms of the selected fleet: