Released with DX UIM 23.4 CU4.

Fixed Defects:

• Resolved an issue where the cdm probe remains deactivated when pushing configuration in some Windows servers.

Released with DX UIM 23.4 CU3.

Fixed Defects:

• Resolved an issue where the Robot seems to deactivate the logmon/ntevl probe after multiple redeployments.
• Resolved an issue where upgrading the AIX robot to v23.4 is not working.
  • For AIX robots installed using 20.4.x rpm and trying to upgrade to 23.4.x, deploy niminit_AIX package on the AIX robot.
  • (For nimldr installation of AIX robot) Download and extract the aix_dependency_libs-1.0.0.zip file available in Nimsoft Support to aix-ppc64 folder.

Released with DX UIM 23.4 CU2.

What's New:

• Auto-Clearing of alerts generated through alarm policies with Nimsoft service restart.

Fixed Defects:

• Resolved an issue where the CDM Alarm Policies with TOT are generating alarms for poll cycles below the Threshold. (Support case: 35463899)

Released as part of 23.4 CU1.1

Fixed Defects:

• Resolved an issue where probe configuration changes were deployed by both the controller and Configuration Reader Service. Such duplicate action corrupted the deployment. Now, all configuration passes through the controller.

Released with DX UIM 23.4 CU1.

What's New:

• Upgraded OpenSSL from v3.0.11 to v3.0.13

Fixed Defects:

• Resolved an issue where the configuration in the Package Editor in Infrastructure Manager does not match the configuration in the probe definition when the probe definition is of type daemon.

Released with DX UIM 20.4 CU10

Released with DX UIM 23.4

Released with DX UIM 20.4 CU9.

Released with DX UIM 20.4 CU8.

• Released with DX UIM 20.4 CU7.

(Released with DX UIM 20.4 CU6)

Fixed Defects:

• SSL vulnerability with robot 9.33HF5. (Support Case: 33255031)

(Released with DX UIM 20.4 CU4)

What's New:

• OpenSSL upgraded to v1.1.1q for BCI-Nimbus components.
• Remove Glibc check dependency for robots.

What's New:

• OpenSSL upgrade from version 1.1.1k to 1.1.1l
• Race condition issue resolution while package distribution.

Fixed Defects:

• Controller binding to 169.x address should be prevented. (Support Case: 32870028)

For the robot_update 9.34 Release Notes, see http://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/controller/controller-release-notes.html

Fixed Defects:

• DE505161: 32725529 - Robot restart when editing distsrv config

Reason: Issue is coming as size of key/value is more that 2KB.
Resolution: CFG_MAX_LINE size changed from 2K to 8K.

This is Control Release (robot_update_9.33_TF2).

(Released as part of UIM 20.3.3)

• (9.32 HF1) Resolved an issue where robots were not falling back to their primary hub and were staying connected to their secondary hub, until the secondary hub was powered off. This behavior was being observed in those scenarios where both the proxy_mode and strict_ip_binding were enabled for the robot. With 9.32 HF1, this issue has been resolved. (Support Case: 32302280)
• Fixed an issue where Windows blue screen (BSOD) was coming up during the reboot caused by controller.exe. Upon rebooting a system, during or immediately after the reboot process, users were observing a Windows crash event. (Support Case: 32467624)
• Fixed an issue where the UIM Server installing was failing while upgrading from 20.1.0 to 20.3.0. The installation was unable to communicate with the controller probe in the allotted time. (Support Case: 32446423)
• Fixed an issue where duplicate robots were getting reported in the OC UI, but the Admin Console was showing only one robot. (Support Case: 32450799)

• Released as part of the UIM 20.3.1 patch. UIM 20.3.1 is a patch release that contains separate standalone artifacts that let you upgrade to 20.3.1.

• Released with UIM 20.3.

(Included in UIM 20.1)

For the robot_update 9.30 Release Notes, see http://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/controller/controller-release-notes.html

For the robot_update 9.20 Release Notes, see https://docops.ca.com/rest/ca/product/latest/topic?hid=controller_RN&space=UIMPGA&language=&format=rendered

Note: 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.

• Updated to support the Microsoft Visual C++ Redistributable for Visual Studio 2017 package version 1.01 (vs2017_vcredist_x86 1.01 and vs2017_vcredist_x64 1.01). This support helps ensure that the minimum version of the VS 2017 package is equal to or greater than 1.01. With this dependency on the version 1.01, the computer is no longer getting restarted automatically when installing the VS 2017 package. That is, with v1.01, no auto-restart of the computer happens.
• Better handling of the controller plug-in. For example, when controller 7.96 (compiled with vs2017_vcredist_x86 1.0 or vs2017_vcredist_x64 1.0) tries to load attr_publisher (compiled with Microsoft Visual C++ Redistributable for Visual Studio 2008), the controller stops responding. This happens because of the compiler incompatibility. Now, with this release of the probe, which is dependent on vs2017_vcredist_x86 1.01 or vs2017_vcredist_x64 1.01, controller no longer loads the plugin (attr_publisher) if it is not compatible.
• Updated to provide support for Amazon Linux 2.

What's New:

• (7.92HF5) If you create a new Solaris zone, a robot installed in the global zone is not automatically deployed to the new zone. To install a robot in a new, non-global zone, install the robot into the non-global zone using the same steps that you use to install the robot in the global zone. (Support Case 746015)
• (7.92) In addition to the operating systems listed below, support for Suse 11 or later secondary hubs and robots is added:
• If you are installing your hub or robot on one of the following operating systems:
• CentOS 7 or later
• Red Hat 7 or later
• Suse 11 or later
• openSUSE 13 or later
• Debian 8 or later
• You must enable the nimbus service after your nimldr installation is complete. To enable the nimbus service, execute:
• systemctl enable nimbus.service
• (7.92HF3) Fixed a problem where VMware templates were not properly created in Windows when audit=on was set. (Support Case 00425378)
• (7.92HF3) Fixed a problem where sections of a probe configuration file could be lost during editing when AUDIT_DETAIL is enabled, causing the probe to crash.
• (7.92HF3) Fixed a problem where timed probes showed as inactive when they are active. (Support Case 00633989)
• (7.92HF3) Fixed a problem where multi-threaded probes could lock the config file on Windows unnecessarily.
• (7.92HF10) Controller performance improvements.
• (7.92HF11) The snmpcollector probe can now be successfully deployed through Infrastructure Manager. The controller now distributes the snmpcollector probe vendor certification files.(Support Case 00819546, 00824491, 00683844, 00825054, 00835227, 00818146, 00821694)

• Ubuntu 16 x64 robot is now supported.
  • Perform a native installation as described in Deploy Robots in Bulk with a Third Party Tool and Native Installers. Note: Deployment with automated_deployment_engine is not supported for Ubuntu 16.
    • When installation completes, execute /opt/nimsoft/install/service-ctrl.sh enable to enable the robot services on Ubuntu 16. This step is not required for Ubuntu 14.
    • Start the robot with /opt/nimsoft/bin/niminit start
  • To completely uninstall the robot on Ubuntu 16, uninstall the service by executing the command systemctl disable nimbus.service, and delete the file /lib/systemd/system/nimbus.service.
• Microsoft Cluster is now supported.
• Windows Server 2016 robot is now supported.
• Support for Debian 6 robot is discontinued.
• The probe utility (pu) is distributed as a separate package. Use the pu package to upgrade the probe utility to v7.90.
• Robot automatic IPv4 address determination is improved. Robotip does not have to be manually set in robot.cfg in order for a robot to start.
• Robot failover detection prevents unnecessary robot failovers when the hub misses a single response to a robot request (_status, alive, robotup, or probelist). The robot is more tolerant of incomplete _status requests. Two new properties can be specified in robot.cfg.
  • robot_status_check_interval controls how frequently the robot polls the hub with a _status request. Previously, this was not configurable, and the polling occurred at a medium timeout, approximately every 11 seconds. Use this property to approximately specify the new polling interval. The interval is approximate because the status check occurs in the medium timeout that exceeds the requested interval. For example, if the robot_status_check_interval is set to 30 seconds, polling will occur every 33 seconds (3 x 11 second medium timeout). The default value is 60 seconds, which equates to a status check every 66 seconds.
  • robot_failover_count improves the resiliency of the robot. In the past, the robot failover mechanism was invoked when one _status request to the hub failed. Use this property to specify the number of consecutive _status failures that must occur before initiating robot failover to a secondary hub. Default, 2.

• Install the v7.90 robot_update package before upgrading the hub probe to v7.90. When the hub package is installed first, the hub appears to go offline in Admin Console and Infrastructure Manager. A communication error is reported, but the hub upgrade is successful even when the error occurs.
• Update robotip manually on Debian platform
  By default, Debian uses 127.0.1.1 as the name resolution address. When a robot is deployed to a Debian system with automated_deployment_engine and the system is restarted, the robot attempts to bind to 127.0.1.1. To avoid contention for 127.0.1.1 on Debian systems, take the following actions:
  • After installing the robot manually or with automated_deployment_engine, add or update the following key in the robot.cfg file to ensure that the robot binds to the correct IP address:
    • robotip = debian_ip_address
  • When preparing an XML file for bulk deployment to Debian systems, explicitly set the robotip in the XML file as follows:
    • <robotip>debian_ip_address</robotip> where debian_ip_address is the IP address that the robot should bind to on the target system

• Proxy mode for robot will now allow the robot spooler to start. In hub-7.7x, the spooler will not start on a controller restart when the controller is configured in proxy mode, due to a port assignment conflict. In hub-7.80, this issue was resolved.

• In SSL mode 0, the robot spooler will not attempt to communicate using SSL.

• AIX java probes will now start up. Previously, on AIX, the controller did not start java probes correctly, so that the java probes process failed to launch. The fix changes the way the system calls to start java probes allowing them to start.

• Controller pre-install exit codes are now correctly interpreted. Previously, POSIX systems were incorrectly utilizing the exit code which would cause improper behavior.

• Added longer output from the command line probe utility. The individual item character line limit is now 300 characters.

-get_info now includes MAC address information for AIX, Solaris and HP-UX as well as the previously provided support for Linux and Windows. -Resolved core dump issue on controller shutdown. -Fixes a bug that caused the robot to always de-register from the hub on shutdown. -A socket leak in the get_info callback on Linux has been resolved.

md5sum: f2745f0b39e1f76c1dd9844fdd69183b
sha1sum: 1ffb6e08ea3980a6d79b8f531e3d229318580646

Fixes issue for non root robots where robot would not start properly.

md5sum: 57dc307a1fb68d746492e15b83cc55f9
sha1sum: 466de82b08d29cd6bbb71f6752a8dff255289b69

Package that is included in the NMS 7.60 distribution.

md5sum: f450137a2c08a2b2c713c3259fe99e0a
sha1sum: 0885c91d220af1aac00df107e63d791bc81c3e01

Package that is included in the NMS 7.50 distribution. Note that this is a package version. The actual robot version is 7.05.

You are advised to carefully read the document "Upgrading the NimBUS Robot" before installation.