|
Date
|
Description
|
State
|
Version
|
|
|
|
|
|
16.11.2015
|
• Fixed memory leak when processing network interfaces.
• Fixed issue where the robot IP address was not associated with the correct MAC address, which resulted in duplicate devices (Salesforce 70001492). This also fixes a MAC address correlation issue seen when using snmpcollector 2.26.
• Fixed issue where the device name was not always passed to the snmpcollector probe when it queried the discovery server for SNMP devices, which resulted in a mismatch between the QOS source name and the device name displayed in USM.
md5sum: bcd2f3e3058546170d4da252d3a51642
sha1sum: e0dfe428cfaf8040a2e3c59d3ca5c1271387a282
|
|
8.32
|
|
|
|
|
|
12.08.2015
|
Released with 8.31
md5sum: a440fd549bf30b216a606128f0fefa29
sha1sum: 03076afb245281ba58a3765655d952e3add4708a
|
|
8.31
|
|
|
|
|
|
31.03.2015
|
• Discovery Server has been enhanced to include callbacks that allow you to cleanly delete devices from both the UIM and UDM tables in the UIM database. With the introduction of UDM, manual deletion of devices using SQL commands was prohibited as it can cause the UDM tables to be out of sync with the rest of the UIM database. Using the callbacks introduced in this release provides you with a mechanism to delete devices without causing syncing issues. See Remove Master Devices for information about using these callbacks.
• Discovery Server has been enhanced to work in conjunction with the vmware probe to provide partial graph publishing. To enable this feature, additional configuration in the vmware probe is necessary. See Enable Partial Graph Publishing for Discovery Server Version for more information about enabling partial graph publishing.
md5sum: b51a8ebd1acac9ebec4e3dd13fb4a79c
sha1sum: 9817c0f27b6b03b8e810d9b9ab2d2930ed625d15
|
|
8.20
|
|
|
|
|
|
06.03.2015
|
• Fixed an issue in which the remove_master_devices_by_cs_keys callback fails on computer systems from VMware probe.
• Fixed an issue in which discovered SNMP devices were not fully persisted to the database if a field (e.g. system description) was greater than 255 bytes.
• Fixed an issue in which discovery_server 8.10 was not applying enriched origins to NIS cache devices.
• Fixed an issue in which the Discovery Server probe was not restarting from Infrastructure Manager and only intermittently restarting from Admin Console.
• Fixed an issue in which NIS cache devices without a valid IP address did include their associated configuration items and metrics when imported.
• Fixed an issue in which discovery_server 8.10 was not correlating devices based on enriched origins.
md5sum: c7346a4b23ca66ab14e3b16854ece5f0
sha1sum: 9ce434de23ae7e56c3279d192782c5c9b32c2364
|
|
8.12
|
|
|
|
|
|
31.12.2014
|
– Added correlation of network interfaces
– Device correlation in the discovery server has been improved to avoid false matches
md5sum: 709dd769d9ee4bb98b95c70456e98874
sha1sum: c1cecff90905dc48d11fd391ba72d17bd12743e9
|
|
8.10
|
|
|
|
|
|
29.09.2014
|
• Fixed: Reintroduced population CM_SNMP_SYSTEM and CM_SNMP_INTERFACE tables with discovery agent results in order to restore per-7.0 Service Oriented Configuration (SOC) functionality and enable ACE to automatically configure the interface_traffic and cisco_monitor probes.
• Fixed: Discovery Server and Relationship Service do not properly handle Discovery Agent and Topology Agent moving from its primary hub to its secondary hub. Now a single Discovery Agent instance is maintained in the database with its configuration data.
• Fixed: Discovery Server fails to get discovery information for a robot that includes probes that do not have the "group" field set.
• Fixed: an alarm is issued if an attach queue is not configured for the subject probe_discovery even if a post queue was configured. Now an alarm is issued only if neither an attach queue nor a post queue is configured for probe_discovery.
• Fixed: Discovery Server correlation should be adjusted to account for Cisco ASA Routers. Added new exclusions to the MAC Address correlation configuration to account for Cisco ASA internal data interfaces.
• Fixed: Discovery Server fails to resubscribe to a hub due to malformed nametoip requests.
Md5sum: 0d040d6f51d0ad062059663ab3769673
sha1sum: e557b0de40d480f88fa6982c42412f0add1e6dd9
|
|
8.00
|
|
|
|
|
|
20.06.2014
|
Discovery Server package included with NMS 7.60 release.
- Expanded SNMP device characterization for AIX operating system information, Cisco Unified Communications devices, and HP Tipping Point devices.
- Added excluded_ip_addresses configuration parameter to IP address correlation. The parameter value supports a comma-separated list of any combination of individual IP addresses, IP address ranges, and IP subnets in CIDR notation (for example, 1.2.3.4, 10.1.2.3-99, 172.1.2/24).
- Added excluded_fqdns and excluded_domains configuration parameters to FQDN (fully qualified domain name) correlation.
- Fixed: Under some networking configurations on Unix systems (particularly Solaris), the discovery agent encountered an error expecting certain information. This caused the discovery agent to terminate before all results were published. The Agent will now gather the information as best it can and continue discovering and publishing.
- Fixed: Discovery server includes a new version of the SDK to provide better performance on systems with multiple network interfaces running on different subnets.
- Fixed: When a robot running a discovery agent moved from one hub to another, an extra discovery agent record was created. Now the same discovery agent record (including the agent’s discovery configuration) is maintained after the robot moves to another hub.
|
|
7.60
|
|
|
|
|
|
28.03.2014
|
Discovery Server package included with NMS 7.50 release.
Added functionality to support VMware App Views.
Enabled port to be specified in a SNMP authentication profile.
Expanded SNMP device characterization for Alcatel devices.
Expanded LUA script functionality to add device_label as a possible value that can used as the computer system name.
Removed the default setting for the CM_COMPUTER_SYSTEM caption field so that users can customize it.
Added a probe command to delete all devices discovered by a specified discovery agent.
Fixed a defect that sometimes resulted in a startup error on SQL Server with Windows Authentication enabled.
MD5 checksum: ae9b8af2faf13118f438b2f661a3b6d0
SHA-1 checksum: 5b9eca08d0f2552be3dbabe0fb99530c9450aa50
|
|
7.50
|
|
|
|
|
|
20.12.2013
|
Added support for target devices with IPv6 addresses
Archive package for the Nimsoft Monitor 7.10 release.
MD5 checksum: d79727850cc0b5212b3c4a8c7efc5053
SHA-1 checksum: 58df9b24e97ab8e061230c97b3a31cc213a92328
|
|
7.10
|
|
|
|
|
|
02.10.2013
|
Archive package for the Nimsoft Monitor 7.0 Release
MD5 Signature: 7b416a55e9880d99630d27d3083e3142
|
|
7.00
|
|
|
|
|
|
24.06.2013
|
Added functionality to support the snmpcollector probe. No other changes or defect fixes are included in this release.
Version 6.6 of discovery_server requires NMS 6.50 and UMP 6.50 or later. It should not be used with any version of NMS prior to 6.50.
Version 6.5 of discovery_agent is required.
MD5 sum: bfe089e83371377b02ef66f845ccc2de
|
|
6.60
|
|
|
|
|
|
01.04.2013
|
Requires NMS 6.5 release.
Requires 64-bit platform.
Accepts imported devices from the cm_data_import probe and saves to the NIS database.
Enhancements to support Discovery Wizard (in USM).
Requires NMS 6.50 and UMP 6.50 or later. It should not be used with any version of NMS prior to 6.50.
Version 6.5 of discovery_agent is required.
|
|
6.50
|
|
|
|
|
|
19.12.2012
|
Included in NMS 6.2.
Improved the collection of the Fully Qualified Domain (Host) Name (FQDN). Adjusted Lua script prioritization rules to select best FQDN data.
Removed handlers for protocols the Discovery Agent no longer supports.
Fixed defect: cm_computer_system missing trigger upon delete for cm_nimbus_robot on Oracle and MySQL.
|
|
3.50
|
|
|
|
|
|
30.09.2012
|
Included in NMS 6.1.
To better support the Automatic Deployment Engine (ADE) and UMP, enhance discovery to get and save processor architecture (32/64-bit) and Linux distribution information.
Updated to use new version of Nimsoft SDK to better handle running on a system with multiple IP addresses.
|
|
3.41
|
|
|
|
|
|
09.07.2012
|
|
|
3.40
|
|
|
|
|
|
30.03.2012
|
Add top level support for SNMP ENTITY-MIB:
Requires 3.31 or later version of discovery_agent.
Only information from the top-level entity is saved (e.g. the router or switch). Information about lower level entities is not saved (e.g. power supply).
The following attributes are saved in CM_DEVICE_ATTRIBUTE:
vendor_name
ent_phys_serialnum
ent_phys_descr
ent_phys_firmwarerev
ent_phys_hardwarerev
ent_phys_softwarerev
Improved origin handling to better support custom origins in multi-tenancy environments.
Reduced number of threads and database connections to help overall Nimsoft Server performance.
Re-established regular interval for collecting data from hubs and robots to ensure that full updated data is collected on a timely basis.
Improved accuracy and consistency of data written to the database.
Improved performance of database updates.
Fixed DE9524, SF70699, SF74814: Some customers no longer show their devices in USM/Dynamic Dashboard. Handle origin changes in discovery.
Fixed US6372, SF58307: Systems are missing from dynamic views due to many CM_DEVICE entries with null cs_id.
Fixed DE9762, SF73197: discovery_server maps robots with same IP’s incorrectly in data centers that have robots with different names, but the same IP address.
Fixed DE9666: Help fix discovery agent waiting forever on "waiting for configuration from discovery_server".
|
|
3.29
|
|
|
|
|