Released with DX UIM 23.4 CU1.

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.

• Released with DX UIM 20.4 CU4.

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)

(Released as part of DX UIM 20.4.0.)

For the robot_hpux 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

(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 with UIM 20.3.

(Included in UIM 20.1)

For the robot_hpux 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_hpux 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.

• 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.