discovery_server Release Notes

The Discovery Server (discovery_server) is released as a part of the core Unified Infrastructure Management Server release.
uimpga-ga
discovery_server_RN
The Discovery Server (discovery_server) is released as a part of the core Unified Infrastructure Management Server release.
Revision History
This table lists the known issues, fixed defects, and revision history for the discovery_server probe.
Version
Description
State
Date
20.33
(Released with UIM 20.3.3)
  • Starting with UIM 20.3.3, a new parameter (using_datomic) has been introduced. This flag is intended to make the discovery_server probe function without having udm_manager. In this release of 20.3.3, the default value of this flag is true and users can set it to false if they want to stop using udm_manager or Datomic.  You can set this parameter by using the raw configuration or by updating the discovery_server.cfg file (under setup/udm/). The discovery_server probe then does not try to perform any Datomic transactions, and all the data is stored in the relational database.
    This flag mainly impacts the way how device interfaces are processed within discovery_server. When using udm_manager or Datomic, the device interfaces information is stored in Datomic first and then ported to the relational database. When udm_manager is disabled and discovery_server is configured with using_datomic = false, then the device interfaces information is stored only in the relational database. No data is propagated to Datomic. So, if there are any other probes that read information from Datomic, you must run discovery_server with using_datomic = false and enable udm_manager.
    If using_datomic is changed from true to false, then the Datomic is not updated further.
    If using_datomic is changed from false to true, it takes awhile to populate Datomic with all the inventory information. During the course of the inventory graph processing, Datomic is filled with the inventory information. The time to re-populate depends on the frequency at which probes publish the full graphs to discovery_server.
    If you are integrating with DX NetOps Spectrum or Network Flow Analysis (NFA), then it is recommended that you allow discovery_server to continue using the udm_manager probe.
  • Fixed an issue where the availability data was not reflecting in the UI. The data was present, but it was not showing up in the UI. (Support Case: 32450276)
  • Fixed an issue where the group_info queue was re-establishing itself (returning) after a reboot, which was causing the probe_discovery queue to back up. (Support Case: 32492426)
  • (20.30 T1) This hotfix includes code changes that let you get more information on the processing of the metrics, which in turn helps in troubleshooting the missing metrics issues.
GA
March 2021
20.30
Released with CA UIM 20.3.0.
GA
September 2020
20.10
(Included in UIM 20.1.0)
What's New:
  • (9.0.3 HF3) Fixed an issue where the vCenter is being correlated with the host instead of being decorrelated. To fix the issue, modified the nisMetaData index to include the virtual ID. (Support Case: 20031152)
  • (920 HF1) Fixed an issue in which discovery_server was not picking up changes in user tags. This issue was occurring in a scenario where robot was going down when the tag was getting changed in the controller configuration and only the robot status was getting updated. To fix the issue, changed the mechanism to update the attributes. (Support Case: 20105364)
  • Fixed an issue in which Device xmi b104vpn01 does not show interface metrics from Interfaces tab. (Support Case: 20052255)
  • Fixed an issue of duplicate entry for the Discovery_server of same origin with different case. (Support Case: 20047981)
  • Fixed an issue where vCenter is being correlated with the host instead of being decorrelated. (Support Case: 20031152)
  • Fixed an issue with the discovery_server which is not picking up changes in user tags. (Support Case: 20105364)
  • Fixed an issue where discovery_server keeps logging exceptions. (Support Case: 20033061)
GA
March 2020
9.20
(Included in CA UIM 9 SP1)
What's New:
  • Fixed an issue in which users were facing some import metric error in the discovery log. (Support Case: 01200697)
  • Fixed an issue in which users were observing device count fluctuation in automatic inventory and a few groups on UMP USM. (Support Cases: 01297434 and 00966713)
  • (9.02 HF2)
    Fixed an issue in which the spectrumgtw probe was not synchronizing device credentials. This issue was occurring when users upgraded CA Unified Infrastructure Management to 9.0.2 (new installation) and installed the spectrumgtw 8.67 probe to integrate with CA Spectrum 10.3.1. In this case, the probe was not synchronizing device credentials from CA Spectrum to CA Unified Infrastructure Management. This issue was occurring because the SNMP profiles were not getting imported into CA Unified Infrastructure Management from CA Spectrum due to an internal error in discovery_server. This hotfix has resolved the issue. (Support Case: 01312626)
  • (8.52 HF2) Fixed an issue in which discovery was not validating certain SNMPv3 devices that were using AES256 encryption. (Support Case: 01271190)
  • Fixed an issue in which devicetype was showing differently in the USM inventory view and in the details view. (Support Case: 01227594)
  • (9.02 HF1) Fixed an issue in which when users were changing the alias for an interface, USM was not reflecting the changed value. But, the change was being getting updated in the database. (Support Case: 01275050)
  • CA UIM 9.2.0 has adopted OpenJDK 8u212 instead of Oracle JDK. Because of this change, CA UIM 9 SP1 (9.1.0) that was using Oracle JDK (JRE) 8u212 is no longer available and has been removed from the Support site. All the functionality that was included in 9.1.0 is now released as part of CA UIM 9.2.0. Consequently, all references to the 9.1.0 release and the probe version 9.10 (released with it) have also been removed from this probe documentation. We recommend that you move to this version 9.20 of this probe, as the previous version 9.10 is no longer available now. For more information about the OpenJDK usage in CA UIM, see  Adopting OpenJDK.
GA
August 2019
9.02
(Included in CA UIM 9.0.2)
What's New:
  • Updated this probe as part of addressing CVE-2018-13820 and CVE-2018-13819 vulnerabilities in CA UIM 9.0.2.
  • Updated this probe as part of removing known security vulnerabilities in CA UIM 9.0.2 by using the upgraded MariaDB components.
  • Changed the default value of the java_mem_init setting in discovery_server.cfg to -Xms1024m.
  • Changed the default value of the java_mem_max setting in discovery_server.cfg to -Xmx2048m.
  • Updated this probe as part of supporting TLS v1.2 in CA UIM for establishing secure communication with the UIM databases: Microsoft SQL Server and Oracle.
Fixed Defects:
  • User properties for devices are now persisted when set for devices is not in UDM. (Support Case: 813599)
  • Discovery has improved robustness in hub/robot scanning to add inventory more quickly in large environments. (Support Case: 717825)
  • Discovery better handles niscache devices with
    localhost
    as the hostname or with a loopback IP address. (Support Case: 701740)
  • discovery_server's queue processing logic has been optimized to quickly process the probeDiscovery queue. (Support case: 00969912)
GA
October 2018
8.53
  • Optimized/improved robustness of hub/robot scanning to add inventory more quickly in large environments. (Support Case: 717825)
  • Better handles niscache devices with
    localhost
    as hostname or loopback IP address. (Support Case: 701740)
GA
August 2017
8.52
Included in CA UIM 8.51, Service Pack 1:
  • Discovery server now handles pre-5.10 robots that don’t support the niscache bulk_size parameter.
  • Discovery server is updated to minimize UDM processing in order to improve the udm_inventory queue performance.
  • A foreign key violation after deleting discovery agent from the database using P_CM_DISCOVERY_AGENT stored procedure is corrected.
GA
March 2017
8.51
Included in CA UIM 8.51:
  • Discovery_server v8.51 contains improved default device correlation logic and allows for a high degree of correlation customization.
  • Discovery_server v8.51 enhancements support new properties from AWS and azure probes.
  • Discovery_server v8.51 has been enhanced to support App Discovery.
  • Discovery_server v8.51 now supports device removal in USM.
GA
February 2017
8.50
Included in CA UIM 8.50:
  • The get_devices callback now includes the Roles parameter in order to identify SystemEDGE devices.
GA
December 2016
8.42
Included in CA UIM 8.4, Service Pack 2:
  • With discovery_server 8.42, when processing large amounts of data with logging set at level 5 or higher, asynchronous logging helps to prevent discovery server processing bottlenecks by decoupling the logging from the processing.
GA
August 2016
8.41
Included in CA UIM 8.4, Service Pack 1:
  • Discovery performance is improved at scale through a combination of discovery server and snmpcollector improvements.
GA
June 2016
8.4
Included in discovery_server 8.4:
  • Memory performance at high scales has been improved in processing inventory and interactions with the bus.
  • Enriched origins are now automatically applied to devices and configuration items from all probes. Devices with enriched origin changes are recorrelated. This applies consistent discovery behavior for all devices.ent behavior to discovery for all devices.
    Support
    cases 163363, 70006870.
GA
January 2016
8.32
Included in discovery_server 8.32:
  • Fixed memory leak when processing network interfaces.
  • Fixed issue in which the robot IP address was not associated with the correct MAC address, resulting in duplicate devices.
    Salesforce
    case 70001492.
  • Fixed issue in which the device name was not always passed to the SNMP Collector probe when it queried the discovery server for SNMP devices, resulting in a mismatch between the QOS source name and the device name displayed in USM.
GA
November 2015
8.31
Included in CA UIM 8.3:
  • Added AWS probe support for auto-scaling groups. More information about auto-scaling groups is available at
    Create and Manage Groups in USM
    and http://aws.amazon.com/autoscaling/.
  • USM has been enhanced to allow users to set an alias for devices and network interfaces. To support this, the
    set_user_properties
    probe command was updated to set the
    UserAlias
    property.
  • Improved support for nfa_inventory probe. For more information, refer to the
    nfa_inventory probe Release Notes
    on the CA UIM Probes space.
GA
August 2015
8.20
Included in CA UIM 8.2:
  • 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 statements was prohibited since 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.
  • 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.
  • Discovery supports subnets with a CIDR notation number of /16 or larger only. Entering range scopes larger than 65,536 addresses when defining a discovery range, may result in one of the two following behaviors:
    • When using the snmpcollector probe to query for a list of devices, defining a range greater than /16 will generate an exception with an error message indicating that the query is not supported.
    • When using the Discovery Wizard to define one or more subnets using the same CIDR notation, defining a range greater than /16, or entering multiple /16 ranges will generate an
      out of memory
      exception error.
  • WMI and SSH discovery provide more detailed host system information than SNMP. We recommend that you use WMI or SSH discovery in addition to SNMP.
  • A bug in MySQL 5.5 causes a slow restart of discovery_server. Upgrading MySQL to version 5.6.13 or later resolves the issue.
  • If you are unable to find a device in USM by IP address, it may be that the device has multiple IP addresses, and discovery identifies the device by a different address.
  • As part of 7.0 discovery server and discovery agent enhancements, a device with multiple IP addresses is now shown as a single device in USM, not as multiple distinct devices per IP address. If you cannot locate a device in USM by IP address, try searching for it by name.
  • The NIS Manager link in Infrastructure Manager does not work because it has been removed from the product. Use the Discovery Wizard available in the USM portlet to configure discovery components.
  • SSH password authentication is disabled with OpenSUSE 12.x.
  • Discovery Agent uses password authentication to connect to a target device over SSH. Discovery Agent cannot communicate with a device where SSH is configured for other authentication methods, such as keyboard-interactive. Discovery Agent also does not support public key authentication or challenge-response authentication.
  • Fixed
    : Multiple cases where devices are not showing up as duplicate devices in USM because they are not being correlated.
  • Fixed
    : An issue in which discovery_server is not applying enriched origins to NIS cache devices.
    Salesforce
    case 00153429.
  • Fixed
    : An issue in which discovery_server fails to re-subscribe to a hub after the hub connection is dropped. As a result of this error, changes to the hub and/or its robots are not persisted in the database.
  • Fixed
    : An issue in which SNMP devices from the discovery_agent are not fully persisted to the database if a field (e.g., system description) is greater than 255 bytes. As a result of this error, the device is not populated in the CM_SNMP_SYSTEM table. Furthermore, the device is not persisted in UDM, which prevents it from being visible in USM.
  • Fixed
    : An issue in which the Discovery Server probe does not restart. This error is experienced regularly in Infrastructure Manager, and only intermittently in Admin Console.
  • Fixed
    : An issue in which NIS cache devices with an invalid IP address are not persisted, including their associated configuration items and metrics.
  • Fixed
    : An issue in which configuration items and metrics are not persisted in the database.
  • Fixed
    : Multiple cases where elements are being persisted into the UIM database, but not to UDM.
GA
March 2015
8.12
Included in CA UIM 8.1:
  • 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.
GA
March 2015
8.10
Included in CA UIM 8.1:
  • Device correlation in Discovery Server and Discovery Agent is improved to avoid false matches and incorrectly merging non-matching devices into one device.
  • Discovery publishes details of each network interface.
  • UDM Manager is coupled with Discovery Server to integrate UDM as a key part of inventory management:
    • Discovery Server writes inventory to both UDM manager and NIS/TNT2 tables.
    • Discovery Server uses log4j logging to capture UDM log information.
    • Logsize is no longer specified in discovery_server.cfg. Logsize is set in the log4j.xml file.
    • Some data resides only in UDM (for example, USM relies on UDM as the sole source for some interface data views).
  • Improvements to the discovery of AIX and HP-UX systems make it possible to deploy robots to these systems using USM.
  • Improvements to device correlation enable Discovery Server and Discovery Agent to avoid false matches and the merging of non-matching devices into one device.
  • Enhancements to interface origins. By default, an interface inherits its origin from its associated device. If the interface origin is enriched through the QoS processor, that origin can now be associated with the interface in UDM.
  • Discovery supports subnets with a CIDR notation number of /16 or larger only. Entering range scopes larger than 65,526 addresses when defining a discovery range may create an out of memory condition.
  • WMI and SSH discovery provide more detailed host system information than SNMP. We recommend that you use WMI or SSH discovery in addition to SNMP.
  • A bug in MySQL 5.5 causes a slow restart of discovery_server. Upgrading MySQL to version 5.6.13 or later resolves the issue.
  • If you are unable to find a device in USM by IP address, it may be that the device has multiple IP addresses, and discovery identified it by a different address.
  • As part of 7.0 discovery server and discovery agent enhancements, a device with multiple IP addresses is now shown as a single device in USM, not as multiple distinct devices per IP address. If you cannot locate a device in USM by IP address, try searching for it by name.
  • The NIS Manager link in Infrastructure Manager does not work because it has been removed from the product. Use the Discovery Wizard available in the USM portlet to configure discovery components.
  • SSH password authentication is disabled with OpenSUSE 12.x.
  • Discovery Agent uses password authentication to connect to a target device over SSH. Discovery Agent cannot communicate with a device where SSH is configured for toehr authentication methods, such as keyboard-interactive. Discovery Agent also does not support public key authentication or challenge-response authentication.
  • Fixed
    : Device correlation in Discovery Server and Discovery Agent is improved to avoid false matches and incorrectly merging non-matching devices into one device.
GA
December 2014
8.00
Included in CA UIM 8.0:
  • Fixed
    : Reintroduced population of CM_SNMP_SYSTEM and CM_SNMP_INTERFACE tables with discovery agent results in order to restore pre-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 failed to get discovery information for a robot managing probes that did not have the "group" field set. This information is now obtained.
  • Fixed
    : An alarm was issued if an
    attach
    queue was not created for the probe_discovery subject, 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 has been adjusted to account for Cisco ASA routers. New exclusions were added to the MAC address correlation configuration to account for Cisco ASA internal data interfaces.
  • Fixed
    : Discovery Server failed to resubscribe to a hub due to malformed
    nametoip
    requests.
September 2014
7.60
Included in NMS 7.6:
  • 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:
    Discovery server includes a new version of the SDK to provide better performance on systems with multiple network interfaces running on different subnets.
  • Fixed:
    In some cases the IP address was used as the computer name instead of the name provided by a probe.
  • 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.
June 2014
7.50
Included in NMS 7.50:
  • 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:
    Discovery server startup error on SQL Server with Windows Authentication enabled.
March 2014
7.10
Included in NMS 7.10:
  • Added correct operating system name and version detection for Microsoft Windows Server 2012 R2.
  • Eliminated support for Microsoft Windows Server 2003 (all forms).
  • Reintroduced LUA script functionality to enable user customization of name, dedicated setting and OS info.
  • Expanded SNMP device characterization to better detect OS type, OS version and device role (the
    dedicated
    setting).
  • Fixed:
    Discovery Server failed on MySQL during startup when there were duplicate entries in DS_ROBOT_XREF.
  • Fixed:
    discovery_server 7.0 did not respond appropriately to origins with spaces/commas.
December 2013
7.00
Included in NMS 7.0
  • New probe_discovery queue for collecting a richer set of element data from probes.
  • Enhanced device correlation.
  • Probe GUI discontinued.
  • Changed handling of expired systems to only delete systems with no QOS data.
  • Fixed:
    Discovery did not identify multiple IPs of network devices (e.g. routers or switches) as one device.
  • Fixed:
    Devices displayed multiple times in USM.
  • Fixed:
    Some devices listed two origins when the names match.
  • Fixed:
    Duplicate Origins on remotely monitored systems.
  • Fixed:
    CM_Computer_System: nimbus_type changed to 0 when robot moved to another hub.
  • Fixed:
    discovery_server failed to insert records as origin field size is exceeded.
September 2013
6.60
Added functionality to support the snmp_collector probe.
June 2013
6.50
Included in NMS 6.5
  • Accepts imported device information from the cm_data_import probe and saves to the information to the NIS database.
  • Enhancements to support Discovery Wizard (in USM).
March 2013
3.50
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:
    cm_computer_system was missing trigger upon delete for cm_nimbus_robot on Oracle and MySQL.
December 2012
3.41
Included in NMS 6.1
  • To better support the Automatic Deployment Engine (ADE) and UMP, enhanced 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.
September 2012
3.40
Included in NMS 6.0
  • Enabled up to 200 discovery agents to be controlled by the discovery server without requiring an increase in the number of threads or amount of memory used.
  • Provided a default level of Service Discovery by adding pre-defined service definitions for well-known network services such as HTTP, FTP, email, etc.
  • Enabled discovery server to run on a different robot other than the primary hub.
  • Reduced memory usage to support up to 5000 robots using the default maximum Java heap size of 1GB.
  • Added further improvements to reduce the number of sockets and database connections to help overall Nimsoft Server performance.
  • Fixed database transaction deadlocks seen with Microsoft SQL Server; fixed other SQL error cases.
  • Fixed SOC defect.
June 2012
3.29
  • 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).
  • 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:
    Some customers no longer show their devices in USM/Dynamic Dashboard. Handle origin changes in discovery.
  • Fixed:
    Systems are missing from dynamic views due to many CM_DEVICE entries with null cs_id.
  • Fixed:
    discovery_server maps robots with same IPs incorrectly in data centers that have robots with different names, but the same IP address.
  • Fixed:
    Help fix discovery agent waiting forever on
    waiting for configuration from discovery_server
    .
March 2012
3.28
Included in NMS 5.61
  • Increased default maximum Java heap size to 1GB (from 256MB) to support up to 2000 robots.
December 2011
3.25
Included in NMS 5.60
  • First plugin-based version of discovery_server to support probe based discovery and better enable service oriented configuration in Unified Service Manager.
November 2011
2.79
Included in NMS 5.21
August 2011