Page History

...

...

The parameters of the network nodes can also be obtained using the SNMP Trap notification mechanism. Usually, a node using this mechanism will notify NEXT about a change in the parameters's values that are critical for the operation of the device and/or of the wireless link, for example, when the connectivity is lost between the devices etc.

While the polling subsystem is an active component, the SNMP Trap processing subsystem is passive. It is always ready to receive Traps from network nodes. After receiving the notifications, the subsystem proceeds with their unscheduled processing, allowing for a timely response to changes, without waiting for the completion of the polling cycle.

...

Incident management subsystem

Anchor
Подсистема формирования событий Подсистема формирования событий

The subsystem 's task is designed to create an event based and manage incidents based on the rules set by the NEXT InfiMONITOR NEXT administrator.

The event subsystemincident management subsystem's operation begins after the information received about the changes in the network nodes's parameters obtained polling results received through the polling subsystem or through the "SNMP Trap" processing subsystem is placed in the storage subsystem. This . This subsystem verifies the match between the rules set for the event and the received parametersvalues.  If If the condition specified in any a rule is met, an event is generated, and it 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 the network nodesdevices.  After After a device was is added manually, the discovery subsystem performs the following functions:

• Detects any neighboring device of the newly added node device that is in the same MINT area and has a connection already established, but has not yet been added to NEXTthe monitoring system.
• Generates a polling task for the neighboring network nodes using the SNMP authentication data specified by the NEXT engineer for this deviceneighboring devices.
• The polling subsystem performs an unscheduled polling of the neighboring device.  If If the specified authentication data is correct, 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. 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 the previously added nodes have devices have been discovered and polled.  The The network nodes without authentication data matching will not be added and attempts to add them will carried out in the future.

An important feature of the subsystem is that it performs the search only within a single MINT area.  If If there are several MINT areas in a wireless network, then at least one node device from each area must be added in order to detect the other network nodesdevices.

Device management subsystem

Anchor
Device management Device management

The subsystem performs the following functions:

1. Provisioning - automatically enables remote access from monitoring system to devices via SSH, that is required for configuration management functions.
2. Configuration update - safely applies configuration changes made by monitoring system users. This function is available only for provisioned devices.
3. 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:

1. The monitoring system connects to device and uploads the new configuration, but not applies it.
2. The new uploaded configuration is set as prospective, the current is set as main one.
3. The device is being rebooted.
4. The device will be booted with the new configuration and delayed reboot is armed. If delayed reboot is done then the device will be rebooted with its previous configuration.
5. The monitoring system compares active device configuration with configuration that should have been applied.
   1. If both of configurations are equal then delayed reboot will be cancelled. New configuration is applied successfully.
   2. If configurations are differ or monitoring system lost connection to wireless device, then the delayed reboot timer will trigger and the previous configuration will be restored.

Notification subsystem

Anchor
Подсистема уведомлений Подсистема уведомлений

...