This article applies to CA Unified Infrastructure Management v8.2.
We’ve been making changes to the probe GUI displayed in Admin Console. Much of what you see in the probe’s GUI is dependent on the version of ppm running on the hub that hosts a probe. For a list of probes that can be configured with Probe Provisioning, see the ppm Release Notes.
Starting with CA UIM v8.2, ppm v3.11, baseline_engine v2.5 and prediction_engine v1.2 are bundled together. When you deploy ppm v3.11 to a hub, baseline_engine v2.5 and prediction_engine v1.2 are also installed. The reason…ppm displays the user interface (UI) but baseline_engine and prediction_engine are required if you want to configure dynamic, static (if applicable), and Time To Threshold alarm and threshold settings for monitoring probes. In addition, if you want to configure Time Over Threshold alarm and threshold settings, you’ll need to deploy the nas package comprised of the alarm_enrichment v4.67 and the nas v4.67 probe. The alarm_enrichment and nas probes are also required for alarm processing.
For fresh installs of CA UIM v8.2, ppm and the nas package are automatically deployed to the primary hub when you run the CA UIM Server Installer.
Upgrading
If you upgrade from CA UIM v8.0 or CA UIM v8.1 to CA UIM v8.2, you’ll need to deploy ppm v3.11 on the primary and all applicable secondary hubs and the nas package to at least the primary hub. You cannot upgrade to ppm v3.11 from an earlier version of ppm.
Matching Versions
Whether you’re installing CA UIM v8.2 or upgrading to CA UIM v8.2, it’s important that you have the same probe versions running on all hubs. This means with CA UIM v8.2, the following versions of the probes are deployed (or at the very least are in the Local Archive in Admin Console) and activated on hubs:
- ppm 3.11
- baseline_engine v2.5
- prediction_engine v1.2
- alarm_enrichment v4.6
- nas v4.6
And as always, we want to know what you think of this and other cookbook articles. Let us know by taking the survey on Survey Monkey.