Early Release Collector 21.019 includes all of the functionality you’ll need to take advantage of our new Netscan, and will be available April 7, 2016. While the basic Netscan features will still work with previous collector versions, most of the new improvements rely on what’s included in this collector version. Along with what is included in optional GD 21, we expect this collector version to wrap up the bulk of what will be included in our required GD version coming later this year.
- RC4 related ciphers are disabled in this collector version, which may cause data collection issues for servers which utilize RC4 connections.
- This collector version may cause SNMPv3 data collection task timeouts in some cases, due to engine time and engine boots not being synchronized correctly.
We will be releasing a new collector version with RC4 ciphers re-enabled & a fix for the SNMPv3 timeouts.
Here is a summary of what’s included in EA Collector 21.019:
- This collector version includes support for LogicMonitor’s new Netscan improvements. See our release notes and detailed documentation for more information on these improvements.
- Our AutoProperties subsystem previously relied on detecting system OID, system info and system IP properties successfully with one version of SNMP before these device properties were set for the device. That was causing issues in some cases where not all properties were detected. In these cases, we now use the SNMP version that provided the most properties and set those properties for the device.
- We’ve changed the way we calculate Netflow and sFlow in/out bytes to make Top Flow data more accurate in certain cases.
- Windows Netscan policies sometimes failed to discover multiple active devices. This was due to the way we interpreted multi-ping responses. We’ve changed how we handle these responses to correct this issue.
- Active Discovery was not assigning instances to the correct instance group if the group name ended with a space. We now trim instance group names that end in spaces.
- Eventsources configured to monitor SNMP v3 Traps weren’t working correctly. This has been fixed.
- Ping packet send intervals have been increased from 250ms to 500ms to fix issues reporting invalid ping loss.
In this Article: