controller Release Notes
The controller probe is a core component of the canm robot.
The controller probe is a core component of the
CA Unified Infrastructure Managementrobot.
- Controllers schedule, start, and stop the probes that the robot manages. Controllers keep configured probes running according to the probe configurations.
- Controllers maintain contact with parent hubs and handle CA UIM operations, including hub state, name-lookup services, and licenses.
- Controllers respond to directives in therobot.cfgand thecontroller.cfgfiles, and to commands issued over thecontroller_port.Default: 48000
Two types of hubs and robots are now available—secure (9.10S) and non-secure (9.10 and earlier). Hub and robot versions 9.10 and earlier use the legacy security model. Beginning with CA UIM 9 SP1, secure hub (9.10S) and robot (9.10S) are available, which further enhance the security mechanism in CA UIM.
Note:Support cases might not be visible to all customers.
(Included in UIM 20.3.3)
(Included in UIM 20.3.0)
(Included in UIM 20.1.0)
(Included in CA UIM 9.2.0)
(7.97 HF3) This hotfix resolves the following issues:
(7.97 HF1) Fixed an issue in which plugin_metric was not collecting metrics for the probes (which have new profiles that are created) unless the robot was restarted. This issue has been fixed with this hotfix.
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.
Included in CA UIM 9.0.2
Important:SSL communication mode options are more meaningful with the release of controller v7.70. The controller creates the
robot.pemcertificate file during startup. The file enables encrypted communication over the OpenSSL transport layer. The treatment of the
robot.pemcertificate file has changed. Changes in treatment impact communication for:
option, which enabled the hub to read user tags from
robot.cfg, was removed from the hub v7.70. Hubs and robots at v7.70 do not read user tags from
robot.cfg. If the hub robot had defined user tags, they will remain in
robot.cfgafter upgrade, but they are ignored. To add user tags to hub probe alarms and messages, specify the user tags in
- When a robot is upgraded, it is recommended to upgrade the controller plug-ins like attr_publisher as well. It is mandatory in the case of a robot upgrade from an older version to 7.97. Otherwise, attr_publisher does not work.
Valid Values for the audit Key in robot.cfg
When you enable the audit functionality in the controller, a configuration key called audit is added to the robot.cfg file. This key has several valid values, which are constructed by adding the "base" values together.
- "6" - Enable auditing and send the messages to the message bus with subject AUDIT
- "5" - Enable auditing but save the messages to a file called "audit.txt" in the Nimsoft\Robot directory.
- "7" - Enable auditing and send the messages to the message bus and save them to the file.
- "8" - Enable auditing only if this robot's hub has "audit=robot" in its hub.cfg.
These values (other than 8) are arrived at by adding certain "base values" together. These can be thought of as "switches" that enable certain functionality.
The base values are:
- 1 - Audit to a file only. This causes the robot to save audit activity to a file called audit.txt in the Nimsoft\Robot directory.
- 2 - Audit messages should be sent to the message bus with the subject AUDIT
- 4 - Enable auditing.
So, for example, a value of "6" therefore means "4+2" are both enabled (since 4+2=6).
Note that if you set the value of audit to 1, 2, or 4, this will have no effect. The first two values (file and message bus auditing) must be "combined" with the "enable auditing" flag.
A value of "8" is a special value that tells the robot to defer to the hub setting for audit.