| Include Page | ||||
|---|---|---|---|---|
|
InfiMONITOR NEXT includes the following features:
- Real-time monitoring of the wireless links.
- Automatic network nodes discovery.
- Event creation.
| Note | ||
|---|---|---|
| ||
The NEXT system monitoring system system is intended only for monitoring Infinet Wireless devices. Devices from other manufacturers are not supported. |
Architecture
The InfiMONITOR NEXT monitoring system consists of several subsystems, each performing a specific function:
- Polling subsystem - periodically polls the network nodes to obtain their parameters's values.
- "SNMP Trap" processing subsystem - provides "SNMP Trap" reception, preliminary processing and transmission to the polling subsystem.
- Event creation Incident management subsystem - monitors the change in the parameter values provided by the polling subsystem, and creates the events according to a certain set of rules.
- Device discovery Discovery subsystem - performs automatic detection and addition of the network nodes.
- Device management subsystem - performs automatic detection and addition of the network nodes.
- Web GUI - graphical interface that allows the NEXT operating engineer to manage the monitoring system.
- Storage subsystem - the database.
Polling subsystem
| Anchor | ||||
|---|---|---|---|---|
|
The main main InfiMONITOR NEXT subsystem periodically polling the network nodes and obtaining their parameters 's values.
The subsystem is working constantly. It distributes all the necessary polling in order to perform the entire network polling during a 5 minutes interval, so NEXT it prevents peak loads on the wireless network:
- The time required for sequential polling of all the network nodes is determined based on the number of network nodes. If there are too many devices, a situation may occur when the time available to poll each node is less than the minimum required time. In this case, the network nodes will be grouped, and the survey will be conducted in parallel for all the network nodes of each group.
- Checks if the network nodes are ready for the surveypolling. The nodes Nodes that have the polling completed in a previous cycle will be polled first. The nodes with incomplete polling in the previous cycle will be polled last.
- If there are network nodes for which the polling began in the previous cycle and did not complete during the current 5 minutes period, then these nodes will be queued for polling in the next cycle.
- All the data received from the nodes during the polling are is placed in the storage subsystem.
...
Network node parameter values can also be obtained using the SNMP Trap notification mechanism. Usually, a node using this mechanism to notify NEXT about a change in parameter values that are critical for the operability of the device and/or wireless link, for example, connectivity loss between devices, etc.
While the polling subsystem is an active part in accessing network nodes, the SNMP Trap processing subsystem is a passive. It is always ready to receive Traps from network nodes. After receiving the notification, the subsystem proceeds to their unscheduled processing, it allows timely respond to changes, without waiting for the completion of the polling cycle.
...
Determining the link between devices
| Include Page | ||||
|---|---|---|---|---|
|
Incident management subsystem
| Anchor | ||||
|---|---|---|---|---|
|
The subsystem task is designed to create an event based on and manage incidents based on the rules set by aInfiMONITOR NEXT administrator users.
The event subsystem work starts after the information about changes in the network nodes parameters obtained incident management subsystem's operation begins after the polling results received through the polling subsystem or the "SNMP Trap" processing subsystem is placed in the storage subsystem. This . This subsystem verifies matching the conditions of the event formation rule to the relevant parameters. If match between the rules set and the received values. If the condition specified in any a rule is met, an event is generated, and can be viewed in the web interface of the monitoring systemincident is created. The incident management subsystem performs maintenance of each active incident.
Discovery subsystem
| Anchor | ||||
|---|---|---|---|---|
|
The subsystem performs the automatic search and addition adding of network nodesdevices. After After a device was is added manually, the discovery subsystem performs the following functions:
- Detects a any neighboring device of the newly added device that is in the same MINT area with which connection is and has a connection already established, but has not yet been added to NEXTthe monitoring system.
- Generates a polling task for a neighboring network node using SNMP authentication data specified by the NEXT engineer for the added deviceneighboring devices.
- The polling subsystem performs an unscheduled poll polling of a device neighboring to an already added. If the neighboring device. If the specified authentication data is suitablecorrect, then the neighboring device will be added automatically. If If the data does not match, a new request will be generated to the polling subsystem with the authentication data that was specified for other devices previously added to InfiMONITOR NEXT. Requests The requests will be repeated until any authentication data matches or it runs out of available authentication data.
- After adding the detected network nodedevice, a search for neighboring nodes devices will be also carried out. This This process ends when the neighbors of all nodes the previously added to the NEXT devices have been discovered and polled. The The network nodes without authentication data matched matching will not be added , and attempts to add them will continue carried out in the future.
An important feature of the subsystem feature is that it performs the search only within one a single MINT area. If If there is are several MINT areas on in a wireless network, then at least one node device from each area must be added to detect network nodesin order to detect the other devices.
Device management subsystem
| Anchor | ||||
|---|---|---|---|---|
|
The subsystem performs the following functions:
- Provisioning - automatically enables remote access for monitoring system to devices via SSH, that is required for configuration management functions.
- Configuration update - safely applies configuration changes made by monitoring system users. This function is available only for provisioned devices.
- Firmware update - uploads and applies the specified firmware version.
Provisioning
One of the key stage in the process of preparing a device for managing its configurations from InfiMONITOR NEXT. During provisioning unique SSH requisites will be installed to each device, After that the monitoring system will be able to connect to each provisioned device to perform configuration management operations. Provisioning may be done manually or automatically at the device adding stage.
Provisioning is performed via SSH, but you can enable using of Telnet.
Configuration update
This function is available only for provisioned devices.
The monitoring system applies configuration changes made by users. The main advantage of this feature is protection against logical errors in configuration, that may cause connection loss. If applied changes lead to a loss of connection between device and InfiMONITOR NEXT, then the previous configuration version will be restored.
Changing the device configuration includes the following stages:
- The monitoring system connects to device and uploads the new configuration, but not applies it.
- The new uploaded configuration is set as prospective, the current is set as main one.
- The device is being rebooted.
- The device will be booted with the new configuration and delayed reboot is set. If delayed reboot is done then the device will be rebooted with its previous configuration.
- The monitoring system compares current device configuration with configuration that should have been applied.
- If both of configurations are equal then delayed reboot will be cancelled. New configuration is applied successfully.
- If configurations are differ or monitoring system lost connection to wireless device, the delayed reboot timer will trigger and the previous configuration will be restored.
Notification subsystem
| Anchor | ||||
|---|---|---|---|---|
|
The subsystem is designed to send notifications to the users of the monitoring system users.
Web GUI
| Anchor | ||||
|---|---|---|---|---|
|
For the NEXT monitoring system management, a A graphical web interface is used . Web for InfiMONITOR NEXT monitoring system management. The Web GUI interacts with all the subsystems.
The Web GUI works properly with the following web the latest versions of the following web browsers:
- Chrome 81 and older, and its derivatives browsers;
- Firefox 75 and older, and its derivatives browsers.
...
- Google Chrome;
- Firefox;
- Microsoft Edge;
- Safari.
The recommended minimum screen resolution is 1600×900.
Storage subsystem
| Anchor | ||||
|---|---|---|---|---|
|
The subsystem provides data storage and quick access to them by the information for the web GUI to NEXT engineersand subsequently for the engineers operating InfiMONTOR NEXT.
import asyncioimport pathlibimport sslimport websocketsHide_comments
async def hello(websocket, path): name = await websocket.recv() print(f"< {name}")
greeting = f"Hello {name}!"
await websocket.send(greeting) print(f"> {greeting}")
ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER)path_cert = pathlib.Path(__file__).with_name("cert.pem")path_key = pathlib.Path(__file__).with_name("key.key")ssl_context.load_cert_chain(path_cert, keyfile = path_key)
start_server = websockets.serve( hello, "localhost", 8765, ssl=ssl_context)
asyncio.get_event_loop().run_until_complete(start_server)asyncio.get_event_loop().run_forever()
Licensing
The license permits using InfiMONITOR NEXT. There are three license types, differ in the validity period and the maximum number of devices for which monitoring will be performed. One license may be installed to only the one monitoring system instance.
| License type | Device number | Validity period | Description |
|---|---|---|---|
| Free | 30 | unlimited | Free license for full-featured use of InfiMONITOR NEXT for small wireless networks. |
| Trial | unlimited | 1 month | A temporary license for the evaluation use of monitoring system. |
| Enterprise | defined at ordering | defined at ordering | License for full-featured use of monitoring system for wireless networks of any size. |
All added to InfiMONITOR NEXT devices are divided into the following categories:
- Licensed device - license permits are granted to such devices, so monitoring/management functions will be available. Each licensed device decrease by one the total allowed number of devices, set by the license.
- Unlicensed device - a device for which no license permits are granted. Unlicensed devices appears when the number of added devices exceed the total allowed number of devices set by the license.
| Note |
|---|
In fact InfiMONITOR NEXT performs monitoring of any devices, whether licensed or unlicensed. However, users are provided with monitoring data and management function only for licensed devices. If license limitations on device number will be extended unlicensed devices become licensed and monitoring data for the past period will be available. |
If the maximum device number permitted by license is less than number of being added devices, licenses will be assigned on each device sequentially until license limitation is reached - the rest will be added as unlicensed.
License management
The license must be installed to use InfiMONITOR NEXT, it may be done at installation stage or in the "System configuration" section. Internet access must be provided to workstation used for license installation.
License management is performing in the licensing center.