Release Version 7.7.9
Release Date: 20th February’ 2024
What’s New?
Plugin Synchronization
The plugin now gets synchronized with the Slave RPE when the Master RPE switchover takes place.
NCM Backup Enhancement
The Motadata application now takes backups of Network devices, considering either startup or running backup files, whichever exists.
Global Notification for RPE Nodes
Users can now receive notifications when an RPE Node experiences downtime and also when it reconnects.
Email Alert Enhancement
When the NMS service restarts, it will no longer resend the alert email notification for a triggered action if it has already been sent.
Support for Secure LDAP Configuration
Users can now configure a secure LDAP server using port 636, in addition to the existing port 389, enhancing security options for LDAP communication.
Motadata Report DB Archival Job Enhancements
Users can now generate a comprehensive DB Archival report for all data types. Users can leave the 'System Type' field blank to include all the log or flow types.
Polling Improvements
A Global notification and E-mail are sent when the polling queue exceeds its threshold value, indicating a potential issue with the polling engine.
Limiting Interfaces Polling
As an overload preventive mechanism, users can now limit the number of interfaces being polled at any instance.
Polling Process Optimization
Adjustments have been made to fine-tune the parameters governing alert and database query workers for enhanced stability.
H2 Database Enhancements
Users can now access the H2 database through CLI to ensure smooth interaction with the H2 database in case of port unavailability.
Report Enhancements
The grid-type alert report based on alert_id and severity can now be created. It specifically applies to the monitor source_type.
A new "DD:HH:MM:SS Time Format Export" field is added to the Motadata Report section of Global Settings. When enabled, the report for Availability Grid, Availability TopN, and Alert Grid can be downloaded in the DD:HH:MM:SS format.
Zone-wise Topology Visualization
Users can now view their infrastructure through intelligent zone-wise classification of the monitors in the Topology map.
Topology Builder Enhancements
Improved the Topology Builder with parallel processing for seed IPs and added timeout (default: 120 seconds) for faster and easier topology creation, enhancing overall performance.
Database Performance Optimization
Data ingestion at a high rate can potentially overwhelm ClickHouse. To avoid this, Motadata can store such data on cache storage, which will be dynamically handled upon Motadata startup.
Support for Parsing Windows API logs
Windows API logs can now be parsed in the Motadata application.
Security Fixes
| No. | Vulnerability Name | CVE-ID |
|---|---|---|
| 1 | OpenSSH < 9.3p2 Vulnerability | - |
| 2 | OpenSSH 8.2 < 8.5 | - |
| 3 | Unencrypted communication | - |
| 4 | TLS cookie without secure flag set | - |
| 5 | Session Hijacking | - |
| 6 | HTTP OPTIONS Method Enabled | - |
| 7 | TLS/SSL Weak Message Authentication Code Cipher Suites | - |
| 8 | Improper Access Control | - |
| 9 | Using Components with Known Vulnerabilities | - |
| 10 | The application uses a weak encoding algorithm such as Base64 | - |
Bug Fixes
Device availability now utilizes go-polling-engine for improved performance and bulk ping functionality, overcoming the limitations with fping.
Even when the URL was operational, it was incorrectly displayed as down in the NMS. This variation has been addressed.
The live session now terminates upon browser or page closure, enhancing the user experience.
The network builder job has been significantly improved, and the execution has been optimized in minimum time, addressing delays previously caused by faulty devices.
A complete NCM backup of the Extreme Network Switch device can now be taken for Telnet by updating the yaml and python files.
Correct uptime metric data value is now displayed for the Linux SNMP device in the NMS application.
The interface details of the Tejas Switch device were incorrectly displayed on the Monitors page, which is now addressed by setting the "go_polling" flag to "Yes" in the plugin.yml file.
While executing the topology-builder job, a faulty entry in the yaml file caused high CPU usage and hindrance to other functionalities. To optimize, this issue is addressed by updating the YAML beans dependency.