> For the complete documentation index, see [llms.txt](https://wiki.astrawireless.net/astra-wireless-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.astrawireless.net/astra-wireless-documentation/technical-documentation/next-monitoring-system-technical-user-manual/monitoring-and-management/devices.md).

# Devices

**NEXT** allows the network engineers to monitor the status of the wireless devices and to manage their configurations.

## Devices review <a href="#id-devices-devicesreview" id="id-devices-devicesreview"></a>

The section includes two key areas:

* **Devices list** - devices and their groups that are in the user's visibility area.
* **Side area for detailed information**.

The list of devices is displayed in a table with the following columns:

* **Device** - the device name.
* **Status** - current device status.
* **Family** - family to which this device belongs.
* **Serial number** - unique serial number assigned to device at the production stage.
* **IP address** - device's IP addresses list.

### Device profile <a href="#id-devices-deviceprofile" id="id-devices-deviceprofile"></a>

Each device is presented by its profile contains the whole information about device. There are following section in profile:

* **Status** - device operation parameters.
* **Maintenance** - management tools: firmware, configurations etc.
* **CLI** - device management via command line interface.

The "Status" section consists of several parts:

* The status of device and its wireless link.
* Network interfaces statistics.
* General information.

There is special section includes both the current and remote device. This section presents characteristics of wireless link in downstream and upstream. For local and remote devices, there is the ability to switch to its web interface or to manage via the command line.

## Network infrastructure requirements <a href="#id-devices-networkinfrastructurerequirements" id="id-devices-networkinfrastructurerequirements"></a>

Management functionality requires network connectivity from wireless devices to the monitoring system port **2121/TCP**, please check your firewall rules.

## Management <a href="#id-devices-management" id="id-devices-management"></a>

Management tools are presented in the "**Maintenance**" section of device's profile.

<figure><img src="/files/0QvHQYzytCwDtKNStZLz" alt=""><figcaption></figcaption></figure>

### Configuration <a href="#id-devices-configuration" id="id-devices-configuration"></a>

The configuration is automatically loaded for each device added to **NEXT**. If the device's configuration has been changed, it will be reloaded, but the previous configuration won't be deleted. Thus, the monitoring system always stores both the current device configuration and its previous versions.

{% hint style="warning" %}
**NOTE**

Configuration and software management functions are available only for devices monitored via SNMP v3.
{% endhint %}

To view the device configurations list, click on the "**Manage**" button in the "**Configuration**" row:

The list of configurations includes the entire configuration history, displayed as a table with the following columns:

* **Status** - current configuration status, the following values are possible:
  * Draft - draft configuration stored in the monitoring system and not applied on the device.
  * Success - the configuration was successfully downloaded from the device or applied on it.
  * Error - the applying of the configuration on the device has failed.
* **Source** - configuration source, the following values are possible:
  * EMS - configuration applied using **NEXT**.
  * Device - configuration received from the device. Configuration changes were made directly on the device, the monitoring system has detected it and downloaded the updated configuration.
* **Version from** - configuration date and time:
  * The date and time of its uploading to the monitoring system.
  * For the draft, the date and time of the last change.

<figure><img src="/files/JacyIHzNR0atYYh8R6Bm" alt=""><figcaption></figcaption></figure>

Select any configuration to view it:

<figure><img src="/files/RqUva103ytbOoU2AVLbd" alt=""><figcaption></figcaption></figure>

You can compare the two configurations to see how they differ. To do this, in the "**Compare**" list, select any other configuration.

To highlight changes in the comparison mode, click on the "**Show the difference**" button.

<figure><img src="/files/JFbfumbGX5xFLj5XpOwa" alt=""><figcaption></figcaption></figure>

#### Configuration changing <a href="#id-devices-configurationchanging" id="id-devices-configurationchanging"></a>

Changing the device's configuration includes the following steps:

1. Select the configuration version.
2. Edit selected configuration.
3. Create job - set a task for applying the configuration on the device.
4. Apply the configuration — the configuration is applied on the device.

**Configuration editing**

Click "**Edit**" button in the selected configuration. A draft will be created, with the content identical to the previously selected configuration. Each device may have only one configuration draft. If you create a new draft the previous will be rewritten.

After editing, you can save a draft without applying it on the device, or create a job to apply it. You may apply any configuration version without editing by clicking "**Create job**" button.

<figure><img src="/files/rB3BjFlBS0ck4LOApyaP" alt=""><figcaption></figcaption></figure>

#### Job creation <a href="#id-devices-jobcreation" id="id-devices-jobcreation"></a>

When you are ready to apply configuration draft please click "**Create job**" button.

In the menu, you can schedule the time for applying the configuration, the following options are available:

* Create job at a required date and time.
* Create job for the current time.

{% hint style="warning" %}
**NOTE**

In order to perform the jobs execution at a required time, it is necessary to set date and time on the virtual machine where **NEXT** is installed. Time settings can not be made in the monitoring system.
{% endhint %}

<figure><img src="/files/5KQmKRCfouvNuW9AmOyC" alt=""><figcaption></figcaption></figure>

#### Applying the configuration <a href="#id-devices-applyingtheconfiguration" id="id-devices-applyingtheconfiguration"></a>

At the set time, the configuration will be downloaded to the device. After successful validation, the configuration will be applied and the device will reboot.

{% hint style="warning" %}
**NOTE**

Configuration applying procedure eliminates the risk of loss of communication with the device due to configuration errors or other failures. For details, see the "⁣⁣Description⁣ and operational principles" article.
{% endhint %}

After rebooting the device, **NEXT** will re-poll it and perform a configuration check. If it was applied correctly, then the job will be marked as completed successfully. Otherwise, the job will fail.

<figure><img src="/files/xOh2MCHhL1qe8PinjCLm" alt=""><figcaption></figcaption></figure>

## Firmware <a href="#id-devices-firmware" id="id-devices-firmware"></a>

The monitoring system provides the ability to update the software, both on one and on a group of devices.

### Upload firmware files <a href="#id-devices-uploadfirmwarefiles" id="id-devices-uploadfirmwarefiles"></a>

To update the firmware, it must be previously uploaded into a special storage of the monitoring system. In order to do this, go to the "**Management**" section and click the "**Firmware**" button.

<figure><img src="/files/g1QS7TSMI7l8uWM3Hlox" alt=""><figcaption></figcaption></figure>

Each file in the repository has the following fields:

* **Version** - the firmware version.
* **Platform** - the hardware platform for which the firmware is intended. The monitoring system will allow to create an update task using only those files that are suitable for the device selected.
* **Type** - the firmware type, MINT or TDMA.
* **Source** - firmware files can be uploaded to the repository either manually or automatically from the update center (not available at the moment). Here will be displayed the source of the file.
* **Build date** - date when the firmware file was built.
* **Comment** - the monitoring system administrators can leave comments to each file.

<figure><img src="/files/YwvzxawORgiZXeLqjsWD" alt=""><figcaption></figcaption></figure>

### Firmware update <a href="#id-devices-firmwareupdate" id="id-devices-firmwareupdate"></a>

The firmware update is performed via a special update job. In order to do this, go to the "**Maintenance**" section of the device card. In the "**Firmware**" line click the "**Manage**" button. This will open a list of firmware files suitable for this device.

<figure><img src="/files/MQOr810NylT0VrebEwJD" alt=""><figcaption></figcaption></figure>

Select the firmware version to be applied to the device, then click the "**Create job**" button. Same to the configuration update jobs, you can run the update immediately or schedule it for a later time.

### Command execution <a href="#id-devices-commandexecution" id="id-devices-commandexecution"></a>

The monitoring system allows to manage the device using the command line. The command line is available in the "**CLI**" subsection of the device status section.

<figure><img src="/files/16ELEx6qrZH0ZChnKURI" alt=""><figcaption></figcaption></figure>

To manage the device from the monitoring system, it must be provisioned, see "System configuration - Provisioning" article.

A complete list of commands is available in the technical documentation: [AstraFleX - Technical User Manual](/astra-wireless-documentation/technical-documentation/astraflex-technical-user-manual.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.astrawireless.net/astra-wireless-documentation/technical-documentation/next-monitoring-system-technical-user-manual/monitoring-and-management/devices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.