UIM 20.3.3

uim2033
2033_release_notes
As part of the regular release cycle for updating Unified Infrastructure Management (UIM), we are pleased to announce the UIM 20.3.3 patch release. This patch release includes new and enhanced features, resolved issues, and so on.
The following features and enhancements are included in 20.3.3:
3
2
Metrics Palette Enhancements
The following enhancements have been made to the Metrics palette. These enhancements further improve the usability of the palette:
  • Define and save the metrics view.
    This eases the process of accessing the views. Otherwise, you would be required to select the metrics every time you want to access the specific metrics view for a device/group.
  • Rename, copy, or delete the metrics view.
    This helps you make the necessary updates to the views based on the changes in your scenarios.
  • Export the metrics view.
    This helps you save or share the views in the supported formats.
  • Publish the metrics view at the private, account, or public level.
    This ensures that only authorized users can access the required views.
  • Set a specific metrics view as a default view.
    This ensures that the same view is displayed in the UI whenever you navigate to the Metrics palette for that entity.
  • Configure the custom time period.
    This allows you to view the historical metrics data based on your defined custom duration.
For more information, see the Working with the Metrics Palette article.
Removing CABI Dependency (Native Operator Console)
This release of UIM removes dependency on CA Business Intelligence (CABI) for rendering the following OC web pages. These pages are now rendered by using HTML5:
  • Home page
    The Home page lets you:
    • View the open alarms, monitored devices, segregation of devices by role, and top ten entities for monitoring technologies, groups, and devices in your environment.
    • Customize the Home page view (using the three-dot menu) to show or hide specific tiles.
    • Click the respective View All link or the specific entity to navigate to the detailed view.
    • Remove a tile from the view by clicking X on the respective tile.
  • Group view page
    The Group view page lets you:
    • View the open alarms, segregation of devices by roles, and top entities for sub-groups/monitoring technologies, and devices related to your group.
    • Use the properly created URL to directly access the specific group dashboard view:
      http://<OC_Server>/operatorconsole_portlet/groups/0/<Group_ID>/dashboard
    • Customize the view (using the three-dot menu) to show or hide specific tiles.
    • Click the respective View All link or the specific entity to navigate to the detailed view.
    • Remove a tile from the view by clicking X on the respective tile.
  • Device view page
    The Device view page lets you:
    • View the details about the device, groups related to the device, count of open alarms, and metrics monitoring charts (metric views) related to the selected device.
    • Put the device in the maintenance schedule by using the in-context Maintenance link on the Device Details tile.
    • Edit the device alias by using the edit icon (pencil) next to the alias name on the Device Details tile.
    • Use the properly created URL to directly access the specific device dashboard view:
      http://<OC_Server>/operatorconsole_portlet/computer_systems/<CI_ID>/dashboard
    • Click the specific group entity link to navigate to the detailed view.
    • Click the open alarms count to access the associated list of alarms.
  • Monitored Technologies (probes) view page
    The Monitoring Technologies view lets you:
    • Access the dashboard views rendered by using HTML5 for the monitoring technologies like cdm, processes, rsp, and so on.
    • View the information like open alarms, devices by roles, and top devices.
    • Click the respective View All link or the specific entity to navigate to the detailed view.
    The following example screenshot shows the dashboard view (for cdm) that is rendered by using HTML5 in UIM 20.3.3.
Custom and Out-of-the-Box dashboards and reports are still rendered using CABI; that is, they have a dependency on CABI. However, the native OC screens are no longer dependent on CABI (Jaspersoft) and are rendered using HTML5. This gives improved performance and actionable views for users to navigate and triage.
For more information, see the Configuring and Viewing Monitoring Data article.
If you change the Zoom level in your browser, then you must reload the OC so that all the widgets in these native OC screens can be loaded properly. This behavior is applicable only for the above-mentioned OC screens.
Availability of Report Scheduler
This release of UIM provides the Report Scheduler functionality that helps you schedule Metric views (Performance metrics) or Service Level Agreement (SLA) reports to run at specified times. With the availability of this functionality, you can now share the reports for viewing and comparing the performance metrics for the various monitored devices, SLAs in terms of the alarms, metrics, and QoS with your stakeholders for the compliance purpose on the predefined schedules. The reports can be delivered as a PDF through email or FTP, or can be stored on a server. Furthermore, you can create, edit, delete, copy, and run jobs for the reports.
For more information, see the Working with Report Scheduler article.
Packages Signed with GPG-Enabled Keys
This release of UIM provides the .rpm and .deb packages that are signed with the GNU Privacy Guard (GPG)-enabled keys. With this enhanced security mechanism, the integrity and authenticity of the packages are maintained. This helps you verify that the packages that you are using for installation are the same that you have downloaded from the Support site. You can, therefore, be assured that no modifications have occurred in the packages after they were signed, thereby providing the quality and security assurance of the delivered packages.
The following packages have been signed with the GPG-enabled keys:
  • nimsoft-robot.i386.rpm
  • nimsoft-robot.x86_64.rpm
  • nimsoft-robot+debian_amd64.deb
  • nimsoft-robot+ubuntu_amd64.deb
For more information, see the Packages Signed with GPG-Enabled Keys article.
Secure Transmission of Certificates
With newer security issues coming up every single day, organizations understand the importance of products having robust security mechanism. This release of UIM has further enhanced its security by enabling the seamless transfer of the certificates
from a hub to a robot
over a secure channel.
Now, you no longer need to manually drag-and-drop the certificates from a hub to a robot when using the secure bus. The complete process is automatically done without any intervention, which ensures that the communication is secure and the data is not tampered with.
For more information, see the Secure Transmission of Certificates article.
Ability to Change the Password
As an account contact user, you can now change your own password. If the "Change Password" ACL is enabled for an account, then the associated account contact users can change their own password. This reduces the chances of your password getting compromised.
The option (Change Password) to change the password is available in the top-right area of the OC UI (under the logged-in user name). After you click the Change Password option, you can enter and save your new password.
For more information, see the Change Your Password article.
Alarm Console Enhancements
The following enhancements have been made to the Alarm console:
  • Provides the arrival date information for an alarm. The Arrival Date column is now available in the Alarm console. With this, you can sort the information based on the arrival date of the alarm, allowing you to always view the latest updates.
  • Displays the date format based on the browser locale.
  • Updates the Alarms UI to show the configured annotations in the Alarm Details section in OC.
  • Provides the ability to access a specific alarm by using the alarm ID as a filter. For example,
    http://<OC_server>/operatorconsole_portlet/uim-alarms?alarmId=MA123456-76568
  • Provides the ability to access the alarms for a specific host by using the host name as a filter. For example,
    http://<OC_server>/operatorconsole_portlet/uim-alarms?hostname=am102345
  • Provides the Hide Invisible and Include Invisible options for alarms in the Alarm console. The Hide Invisible option hides the alarms that are marked as invisible from the list. The Include Invisible option shows all the alarms: alarms marked as invisible and also the alarms
    not
    marked as invisible.
  • Added the ability to display alarms in the Alarm console based on the alarm filter conditions in the Dashboard Designer view. You can create the alarm filter in the Dashboard Designer view. When you access that alarm filter in the created dashboard, you are then redirected to the Alarm console. The Alarm console displays the appropriate alarms based on the defined filter conditions; it does not display other alarms.
For more information, see the Manage Alarms article.
Asynchronous Distribution of Probes
UIM 20.3.3 now introduces the asynchronous behavior for probe distribution mechanism, which ensures more robust and resilient deployments. This ability also helps you avoid intermittent time-out or communication issues with the deployment of the larger probes. Previously, while deploying the larger packages, distsrv and ADE were facing time-out issues, which was causing unsuccessful deployment of such packages.
This functionality supports backward compatibility. For example, if you have an older robot, then the deployment happens based on the earlier (synchronous) behavior.
Creating New Custom Dashboard Views
You can now create new custom dashboard views using CA Business Intelligence (CABI) and add them to the OC Dashboards page. This ability helps you address situations where you want to create customized views of your dashboards depending on your needs. Therefore, in UIM 20.3.3, you can create these views in two ways: by using CABI or by using the already existing Dashboard Designer functionality.
For more information, see the Create a New Custom Dashboard View article.
Data Maintenance Stored Procedures Enhancement
For Microsoft SQL Server 2016 (or higher), the existing data maintenance stored procedures have been enhanced to enable the truncation of partitions directly from the table. This enhancement eases the data maintenance process. For example, it eliminates the need of creating temporary tables, creating indexes, switching the partition data to the temporary tables, and then truncating the data.
For Microsoft SQL Server 2012 or 2014, the existing stored procedures would continue to work as they were working earlier. That is, the new behavior is not applicable for these versions.
For more information, see the data_engine probe documentation.
discovery_server Enhancement
The discovery_server probe has been enhanced in this release. 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 = true, which means enabling udm_manager.
If you are integrating with DX NetOps Spectrum or Network Flow Analysis (NFA), then we recommend that you allow discovery_server to continue using the udm_manager probe.
For more information, see the discovery_server probe documentation.
Group Management Enhancements
The following enhancements have been made to the groups:
  • Added the ability to move groups along with devices from one container group to another. This helps you logically organize your groups.
  • Added the new group ACL permissions (OC Group Add, OC Group Edit, OC Group Delete) to provide the create, edit, and delete group permissions to the appropriate users. This ensures that only required users are allowed to perform the relevant operations.
For more information, see the Manage Groups article.
Group View and Alarm View Optimization
The response time in the Alarm view and the Group view in the OC UI has been further optimized for better user experience and ease of working. For example, with the implementation of the lazy loading in the Group tree view, you no longer experience any lag while accessing the information.
Improved Implementation of the Alarm Policy and MCS ACL Permissions
With this release, the implementation of the ACL permissions for the alarm policy and MCS has been improved. Now, when you disable the Policy Management ACL permission for the alarm policy, the associated users no longer see the option to add, update, or delete an alarm policy. Similarly, when the OC Monitoring Configuration Service and OC Edit Monitoring Templates ACL permissions are disabled for MCS, the Monitoring Config gear icon is not enabled for the related users.
Monitoring Configuration Service (MCS) Enhancements
The following new parameters are now available in the MCS configuration:
  • txn_timeout: This parameter lets you configure the transaction time-out. This configuration, therefore, helps you roll back the transaction if any exception occurs during the transaction process. The transaction time-out is configured so that if any exception occurs, the transaction is rolled back. It is available in the setup section of the MCS configuration. The default value is 1020. For example, txn_timeout = 1020.
  • audit_enabled: This parameter lets you enable or disable the auditing in MCS. For example, if you want to stop the auditing only in MCS, you can disable this parameter. It is available in the timed section of the MCS configuration. By default, the value is set to true. For example, audit_enabled = true.
  • number_of_processing_devices: This parameter lets you specify the number of devices (which are in the modified or new state) to be processed for the monitoring purpose. It is available in the timed section of the MCS configuration. The default value is 1000. For example, number_of_processing_devices = 1000.
For more information, see the mon_config_service probe documentation.
Persist Maintenance Schedules in the nas Probe
The nas probe now lets you persist the maintenance schedules even when the maintenance_mode probe is not reachable from nas. Also, while trying to reconnect, the previous schedules are not deleted and the alarms can be filtered even if the maintenance_mode probe is unavailable.
A new parameter
maint_sched_discard
is available that lets you decide whether you want to discard the maintenance schedule. You can specify the value as
yes
or
no
. The value
no
implies that the maintenance schedule is retained.
For more information, see the nas probe documentation.
Deprecating the ace Probe
The ace (Automatic Configuration Engine) probe has been deprecated in UIM 20.3.3. When you upgrade from a previous version of UIM to UIM 20.3.3, the already existing ace probe is removed from the probes and the installed packages lists after the upgrade. The probe package, however, remains in the local archive.
Platform Support
  • UIM now supports Microsoft SQL Server 2019.
  • Robot 9.33/9.33S supports Ubuntu 20.01 LTS (Intel 64-bit).
Resolved Issues
The following are the resolved issues in UIM 20.3.3:
  • Operator Console
    • Fixed an issue where duplicate devices were displaying when users were editing a static group in OC 20.3.2. While editing static groups, users could see the duplicate devices in the device selection area of the edit group dialog. Out of the two entries, one entry was selected and the other was unselected. If users were selecting an unselected device, they were receiving an exception in that case.
    • Fixed an issue where exporting SLA to PDF was truncating the QoS constraint list of SLOs in UIM 20.3.1. In SLA Reports, when users were exporting the SLA to the PDF format, the SLA and SLO information was exporting to the PDF. However, the list of QoS constraints configured in the SLO was not exporting completely.
    • Fixed an issue where the change password option for the account users added manually to the Account Admin was not available in UIM 20.3.0. Users were not able to change the password using OC.
    • Fixed in an issue where the percentage (%) was not getting displayed in the Dashboard Designer when users were clicking the show units. (Support Case: 32416005)
    • Fixed an issue where the customized dashboard layout was not working after upgrading to 20.3.2. (Support Case: 32442952)
    • Fixed an issue where the PDF export was not working in Dashboard Designer. (Support Case: 32420957)
    • Fixed an issue where the images were not loading in the dashboard in 20.3.2. When users were creating a dashboard, uploading an image to it, and publishing the dashboard, they were not able to view the images. An empty box was displaying in place of the image. (Support Case: 32438021)
    • Fixed an issue where the published custom dashboards were not opening. When users were accessing the custom dashboard through OC, the custom dashboard was not redirecting to the HTTPS link. Therefore, the dashboards were not opening. (Support Case: 32455058)
    • Fixed an issue where users were getting 401 and 500 data access errors in 20.3.2 while using OC. If an LDAP user was mapped to multiple accounts and logged into OC 20.3.2, the user was unable to access the web pages and was receiving the data access errors. (Support Case: 32439786)
    • Fixed an issue where resetting of the maintenance schedule for the create/edit process was happening when multiple users were accessing the maintenance schedules. (Support Case: 32452624)
    • Fixed an issue where the information in the Member Group table was not rendering properly in the Group Details view in OC. (Support Cases: 32452448 and 32450811)
    • Fixed an issue where while generating the SLA report from the SLM view, the PDF was generating only the first page of the report. It was not generating the remaining pages. (Support Case: 32513503)
    • Fixed an issue where the new dialog was flashing (appearing/disappearing) while creating a new maintenance schedule or editing an existing schedule. (Support Case: 32452613)
    • Fixed an issue where while performing an update to the member hosts in a maintenance item, the update host choice was resetting to the original value. (Support Case: 32387923)
    • Fixed an issue where the Admin Console link from the Settings page in OC was not working. (Support Case: 32443932)
    • Fixed an issue where LDAP users were not able to view the dashboards published to No account. They could view only those dashboards that were published to Public. (Support Case: 32440968)
    • Fixed an issue where users were unable to download, edit, or copy the SLA report. When users were navigating to SLA in OC to download the report, the OC UI was not responding. (Support Case: 32456125)
    • Fixed an issue where the last modified date for the alarms was not available in the Alarm view. (Support Case: 32466952)
    • Fixed an issue where the single source selection in Metric Viewer was not working in those scenarios where the multi-source was available. This issue was being observed with all the probes QoS that had the multi-source available. For example, when they were selecting "disk usage - Percentage", they were seeing all the file systems. When they were trying to select the "disk usage" metric, select the three dots next to that metric, and then select the specific file system, they were still getting a graph with all the file systems. (Support Case: 32543888)
    • Fixed an issue where the metrics view graph was showing a continuous line even when the system status was down. (Support Case: 32540906)
    • Fixed an issue where users were unable to change the parent group of static or dynamic groups. (Support Case: 32534974)
    • Fixed an issue where users were receiving the invalid dashboard report PDF through the email. When users were configuring a schedule on the dashboard to send the report through email, they were receiving the email with an invalid PDF. (Support Case: 32535203)
    • Fixed an issue where the scheduled dashboard and generate dashboard were showing the logon screen. (Support Case: 32502458)
    • Fixed an issue where users were not able to set the compliance value in decimals while creating a monthly SLA report in OC. (Support Cases: 32432656 and 32442628)
    • Fixed an issue where some of the URL actions in the Alarms page stopped working after upgrading to 20.3.1. Users were getting the error as
      <Error><Message>The requested resource does not support http method 'GET'.</Message></Error>
      . And, those URLs were doing the GET operation instead of the POST operation. (Support Case: 32415022)
    • Fixed an issue where users were getting errors when they were trying to export SLA reports to PDF. (Support Case: 32432717)
    • Fixed an issue where users were unable to accept or assign alarms. When users were trying to assign alarms to some other users with email addresses, OC was displaying the
      Request failed with a status code 406
      message. (Support Case: 32388293)
    • Fixed an issue where the delete option for some of the SLOs was not working. This issue was occurring in those scenarios where SLOs were having exclusion period with the notes. If users were trying to delete such SLOs, they were not able to do that. (Support Case: 32411716)
    • Fixed an issue where while creating the dashboard using the Dashboard Designer, the circle widget was not showing up properly in the canvas. (Support Case: 32452612)
    • Fixed an issue where the selected device under a group was not getting highlighted. When users were navigating to the Groups view and selecting a device under a specific group, the UI was not highlighting the selected device. (Support Case: 32511189)
    • Fixed an issue where sorting of the accounts list was not working when users were trying to create groups and maintenance schedules in OC. (Support Case: 32529776)
    • Fixed an issue where the maximum aggregation was not working in the list widget in Dashboard Designer. (Support Case: 32460053)
    • Fixed an issue where users were unable to view the general alarm policies with the Policy Basic ACL. Users with the "MCS Read-Only Access" ACL and the "Policy Basic" ACL could view the MCS profiles and a specific alarm policy, but they could not view the list of all the alarm policies. (Support Case: 32412802)
    • Fixed an issue where users were unable to update a parent of a static or a dynamic group. This issue was occurring after users upgraded to 20.3.2. (Support Case: 32511259)
    • Fixed an issue where when users were creating the Application Discovery Script MCS profile, the profile was not appearing in the list of the profiles for the group. When users were trying to create the profile again, they were receiving the error that the profile was already available. (Support Case: 32450249)
    • Fixed an issue where users were facing issues with the sort order in SLM while configuring QoS constraints. When users were adding the new QoS in an SLO, the source list was not sorting alphabetically. (Support Case: 32502206)
    • Fixed an issue where one account user could see the other origin names of a robot. (Support Case: 32504369)
    • Fixed an issue where users were facing issues while editing a weekly maintenance schedule that had multiple days selected in the Starting field. After creating a weekly schedule with multiple starting days, when users were trying to edit this schedule, the starting days were not getting selected. (Support Case: 32461052)
    • Fixed an issue where no targets were appearing when users were looking for targets using the QOS_e2e_Execution on a VM in the SLM. (Support Case: 32385684)
    • Fixed an issue where users were unable to create SLA for the server CDM data. (Support Case: 32485423)
    • Fixed an issue where the alarm policy deleted by the admin user was still visible in the OC UI. (Support Case: 32498397)
    • Fixed an issue where the Operator Console /main.js and accountadmin/ were displaying the dummy values. In UIM 20.3.3, these dummy values have been removed. (Support Case: 32521709)
    • Fixed an issue where the Enable Callback Proxy for MCS in the configuration service options was not working. (Support Case: 32398528)
    • Fixed an issue where the alarms generated from an MCS profile were displaying the host name and the alarms generated from an alarm policy were displaying the IP address in the Alarm view (Device Name column). (Support Case: 32382212)
    • Fixed an issue where the status was not getting updated in the Group tree view (left pane) when alarms were raised or acknowledged. The status was getting updated only after refreshing the browser. (Support Case: 32528576)
    • Fixed an issue where users were not able to drill down the Citrix Xendesktop dashlets in the OC UI. (Support Case: 32374724)
    • Fixed an issue where users were able to dissociate a device from the Inventory view and also select the maintenance button even when they did not have the Edit Maintenance ACL permission. Now, after fixing this issue, they cannot dissociate a device from the Inventory view and the maintenance button is also disabled for such users. (Support Case: 32438209)
    • Fixed an issue where the policy_management queue was not getting processed and the queue color was yellow. (Support Case: 32463333)
    • Fixed an issue where the sorting of the Group members in the Name column was not happening properly. When users were trying to sort the data in the Name column, the sorting was not happening alphabetically. The sorting was case-sensitive and the uppercase names were getting listed before the lowercase names. (Support Case: 32529786)
    • Fixed an issue where some of the hubs in the Admin Console were not displaying properly. Also, users were not able to retrieve the robot information for such hubs. (Support Case: 32445829)
    • Fixed an issue where no option in OC was working when users were trying to access the SLM functionality. (Support Case: 32463430)
    • Fixed an issue where the time for the maintenance schedule was getting changed to the 24-hour format with AM (for example, 17:00 AM). Also, the starting data was resetting to the default value (for example, dd-mm-yyyy). This was happening when users were saving the maintenance schedule. (Support Case: 32407130)
    • Fixed an issue where the Interface groups were not displaying the utilization data after upgrading to 20.3. (Support Case: 32445423)
    • Fixed an issue where users were getting the Data Access Error in the OC reports after they upgraded to 20.3.2. (Support Case: 32455050)
    • Fixed an issue where the OC installer was selecting the main hub as the server for installation. This issues was occurring when users were trying to upgrade to 20.3.0. (Support Case: 32501074)
    • Fixed an issue where users were receiving the "no metrics found" error when they were trying to create an alarm policy on an existing group. The metrics was available, but users were getting the no metrics error message. (Support Case: 32517066)
    • Fixed an issue where alarm policies were not working. They were in the ERROR_RECOVERY or PENDING_RECOVERY state. (Support Case: 32488591)
    • Fixed an issue where users were facing the problems while creating an alarm policy using the long RegEx string that had more than 256 characters. (Support Case: 32492535)
    • Fixed an issue where users were getting the "Error Adding Scopes | Invalid Discovery Agent" error when they were trying to add the scope in the Discovery wizard. (Support Cases: 32513593, 32533191, 32426281, and 32506530)
    • Fixed an issue where users were not able to set the alarms coming from the spectrumgtw probe to the invisible state in the Alarm console. When they were trying to do so, the visibility state of such alarms was not changing. The Alarm console was still showing the state as true and the alarm was not getting removed from the list of the displayed alarms. (Support Case: 32497750)
  • CABI
    • Fixed an issue where users were unable to download or export the reports. For example, when they created customized CPU reports in the CABI dashboard, they could not perform the export or download. (Support Case: 32478274)
    • Fixed an issue where users were unable to deploy the cabi 4.30 probe in UIM 20.3.0 environment. The CABI log was showing the
      usersync errors
      . (Support Case: 32518022)
    • Fixed an issue where users were facing Data Access Error in the OC reports after upgrading to 20.3.2. (Support Case: 32455050)
    • Fixed an issue where CABI 4.30 was not working after disabling TLS v1.0 and TLS v1.1 on the Microsoft SQL Server. (Support Case: 32485217)
    • Fixed an issue where scheduled reports were timing-out or failing to complete. Users started observing this behavior after they upgraded to CABI 4.30. (Support Case: 32469192)
    • Fixed an issue where users were observing performance issues with CABI when they were generating the reports. (Support Case: 32505644)
    • Fixed an issue where Operator Console in the HTTPS mode was not loading. (Support Case: 32365132)
    • Fixed an issue where users were facing CABI issues and they were unable to connect to JasperServer. (Support Case: 32446652)
    • Fixed an issue where users were unable to install CABI in a newly upgraded 20.3 environment. When they were trying to install the bundled CABI on a standalone robot reporting to the primary hub, they were receiving the error. (Support Case: 32446543)
    • Fixed an issue where the Device/Group Trend/At A Glance reports in the /public/ca/uim/reports/library/health location were not aware of the origin. (Support Case: 32439177)
    • Fixed an issue where users were getting the Data Access Error in the dashboard home page after upgrading to 20.3.0. (Support Case: 32511235)
    • Fixed an issue where users were unable to see the data in the CABI report (UIM Single QOS Topic). (Support Case: 32453770)
    • Fixed an issue where values in reports were not showing in percentage. For example, when users configured the adhoc reports for Disk Utilization in percentage (%), the value in reports was not showing up in percentage. (Support Case: 32468506)
    • Fixed an issue where the CABI bundled installation was completing successfully, but the cabi probe was failing to start. (Support Case: 32437153)
    • Fixed an issue where users were unable to fetch the data for more than three months in CABI. (Support Case: 32450088)
    • Fixed an issue where only limited time range options were available in the CABI reports. For example, there was no option to run a report for the previous month or to select a custom time range when running a report. (Support Case: 32510132)
    • Fixed an issue where users were unable to view the CABI page in the OC UI. (Support Case: 32473595)
    • Fixed an issue where the CABI Home Dashboard was not displaying the dashboards correctly. (Support Case: 32456241)
    • Fixed an issue where the Schedule menu within
      OC, Reports
      was not displaying the Edit option correctly. (Support Case: 32447941)
    • Fixed an issue where the dashboards were not loading when the users were accessing them directly from the CABI server. The users were getting the waiting (hourglass) symbol. (Support Case: 32485752)
    • Fixed an issue where users were not able to open the reports page from the OC UI. The users were receiving the 500 error. (Support Case: 32497978)
    • Fixed an issue where the Availability reports were not showing any groups or devices in CABI. (Support Case: 32512294)
    • Fixed an issue where the users were receiving the JKS key error when they were trying to import the reports. This issue was occurring in the case of the bundled CABI. (Support Case: 32455022)
    • Fixed an issue where users were facing issues while installing the cabi 4.30 version in their UIM environment. (Support Case: 32424521)
    • Fixed an issue where users were receiving Data Access Error when they were trying to access the Reports page in OC. (Support Case: 32458239)
    • Fixed an issue where CABI was not working with TLS v1.2 when UIM was using Microsoft SQL Server as the database. (Support Case: 32442685)
    • Fixed an issue where users were getting Data Access Error when they were opening the OC Home page. (Support Case: 32470294)
    • Fixed an issue where users were not able to download the robot_update_9.32.zip package. They needed this package to fix the
      System component missing CA Business Intelligence system component is needed
      error. Users were receiving this error when they were launching the OC UI. (Support Case: 32491879)
  • data_engine
    • (9.20 HF5) Fixed an issue where data_engine was not processing all the qos_processor-enriched metrics after the restart.
    • (9.20 HF5) Fixed an issue where after updating the origin through qos_processor, data_engine was unable to store the related metrics.
    • Fixed an issue where users were unable to upgrade to 20.3.0. The upgrade was getting stuck at 40%. (Support Case: 32473364)
  • discovery_server
    • 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)
  • ems
    • Fixed an issue where the ems probe was always in the process of getting restarted. (Support Case: 32464287)
  • hub
    • (9.32 HF2 and 9.32 SHF2) Fixed an issue where users were able to see the cleartext passwords in the hub.log file when they were logging in using the Admin Console. (Support Case: 32475607)
    • Fixed an issue where the primary hub was restarting after every few minutes. The logs from controller and hub were not showing any relevant information about the issue. (Support Case: 32498752)
    • Fixed an issue where users were getting errors when they were trying to create tunnels on a hub. (Support Case: 32488645)
    • Fixed an issue where the enhanced security.cfg configurations were not propagating to one of the hubs in the environment. (Support Case: 32509796)
    • Fixed an issue where the AD/LDAP login through IM was failing. The hub was able to connect to the AD/LDAP server and fetch the group/user list, but the login was still failing. (Support Case: 32424406)
  • maintenance_mode
    • Fixed an issue where the maintenance schedules were not starting at the correct time. These schedules were starting after 1-2 hours of the correct start time. (Support Case: 32493641)
    • (20.30 HF1) Fixed an issue where the maintenance schedule for the Nth day of a month was not working. The schedule was not starting on the scheduled date and time and was remaining inactive. This was happening when the user time zone or the target schedule time zone and the server time zone were different.
    • (20.10 HF1) Fixed an issue where the alarms were getting generated during the maintenance schedule.
    • (9.20 HF5) Fixed an issue where the maintenance schedules were not working. (Support Case: 32160419)
  • mon_config_service
    • (20.31 HF1) Fixed an issue where updates on the UIM profiles were not always triggering the probe restart. (Support Case: 32283937)
    • (20.31 HF1) Fixed an issue where monitoring profiles were not always getting assigned to the server. (Support Case: 32327952)
      The 20.31 HF1 hotfix introduces a new key (number_of_processing_devices) in the mon_config_service.cfg file (under the timed section). The default value is 1000. This value is configurable. You can change the value based on the number of devices in the inventory that you are monitoring.
    • (20.31 HF2) Fixed an issue where the MCS profiles were getting created too slowly. (Support Case: 32440705)
    • Fixed an issue where the UIM provisioning information and the profile name were not matching with the profile variable field. This issue was being observed for the Network Connectivity (Enhanced) profile. (Support Case: 32443342)
    • Fixed an issue where the MCS query was making the SQL transaction log full after every 2-3 days. (Support Case: 32462061)
    • Fixed an issue where for several "disabled" profiles, the expected template or probe versions within the MCS backend tables were actually missing within the UIM probe/package archive. This was resulting in the profiles being disabled as MCS/ADE was unable to locate the required versions for the monitoring configuration deployment. Also, the MCS profiles were not deploying and the MCS logs were showing
      maximum number of profiles
      . (Support Cases: 32481934 and 32469928)
    • Fixed an issue where the default alarm policies were not getting created after upgrading from UIM 9.2.0 to UIM 20.3.1. For example, when users were creating a new profile using MCS and the processes (enhanced) template on a device, the default alarm policy "CA default policy" was not getting created. (Support Cases: 32425602 and 32475405)
    • Fixed an issue where MCS was creating the profiles at an extremely slow pace. (Support Case: 32440705)
    • Fixed an issue where the MCS template deployment for nic_monitor was failing. The MCS log was not showing up any entries of uploading the new template. It was still referring to the older version. (Support Case: 32445566)
    • Fixed an issue where users were unable to use OC after they upgraded to 20.3.2. They were observing that the performance was too slow. (Support Case: 32467330)
    • Fixed an issue where the probe deployment was getting referred for most of the robots. The MCS deployment dashboard was also showing that the profiles were still in the pending state. (Support Case: 32470045)
  • mon_config_service_cli
    • (20.31 HF1) Fixed an issue where updates on the UIM profiles were not always triggering the probe restart. (Support Case: 32283937)
    • (20.31 HF1) Fixed an issue where the monitoring profiles were not always getting assigned to the server. (Support Case: 32327952)
    • (20.31 HF2) Fixed an issue where the MCS profiles were getting created too slowly. (Support Case: 32440705)
  • mon_config_service_ws
    • (20.31 HF1) Fixed an issue where updates on the UIM profiles were not always triggering the probe restart. (Support Case: 32283937)
    • (20.31 HF1) Fixed an issue where the monitoring profiles were not always getting assigned to the server. (Support Case: 32327952)
    • (20.31 HF2) Fixed an issue where the MCS profiles were getting created too slowly. (Support Case: 32440705)
  • mon_config_service_recon
    • (20.31 HF1) Fixed an issue where updates on the UIM profiles were not always triggering the probe restart. (Support Case: 32283937)
    • (20.31 HF1) Fixed an issue where the monitoring profiles were not always getting assigned to the server. (Support Case: 32327952)
    • (20.31 HF2) Fixed an issue where the MCS profiles were getting created too slowly. (Support Case: 32440705)
  • nas
    • Fixed an issue where, in UIM 20.3.0 (nas 9.31), when the parenthesis "(" or ")" was used in the Auto-Operator (AO) message matching criteria (RegEx), all alarms were matching. However, only alarms matching the alarm text should had been identified. This issue was occurring because starting from nas 9.31 RegEx is being used instead of the pattern matching to match the alarms. This represents a change regarding the previous pattern matching behavior. Also, ensure that the RegEx defined in nas for any AO rule or pre-processing rule must be validated and must not include any RegEx complication error. For more information, see the KB Article. (Support Case: 32302660)
    • Fixed an issue where pre-processing rules were not working as expected in nas. (Support Case: 32476942)
  • prediction_engine
    • Fixed an issue where the prediction_engine probe was not starting. Users were receiving the "max restart reached" error. (Support Case: 32475437)
    • Fixed an issue related to the vulnerability in the probe. (Support Case: 32501164)
  • robot
    • (9.32 HF1 and 9.32 SHF1) Fixed 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 switched off. This behavior was being observed in those scenarios where both the proxy_mode and strict_ip_binding were enabled for the robot. (Support Case: 32302280)
    • Fixed an issue where the Windows blue screen (BSOD) was coming up during the reboot that was 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)
  • uimapi
    • Fixed an issue where the /uimapi/hubs/{domain}/{hub}/robots endpoint was not returning the probes information in the return statement. This issue was occurring in the uimapi 20.30 version. (Support Case: 32490205)
    • Fixed an issue where the GET /hubs/{domain}/{hub}/robots endpoint was returning the error
      No element found for key pkg_version
      . (Support Cases: 32191365 and 32193303)
    • (20.32 HF2) Fixed an issue where the alarm acknowledgement was taking very long time when using uimapi. This was happening because the PUT /alarms/{alarmid}/ack API of uimapi was taking too long to complete. (Support Case: 32543378)
    • (20.32 HF1) Provided the uimapi endpoint that helps encrypt the password while updating the probe configuration for the XenDesktop probe.
Download Artifacts
The UIM 20.3.3 artifacts (OC installer, UIM Server installer, and GPG Key File) are available at UIM Hotfix Index.
High-Level Deployment Process
This section provides a high-level deployment process that helps you quickly get started with this patch release.
  1. Review the upgrade path.
  2. Run the 20.3.3 server installer.
  3. Upgrade the robots on the OC and the CABI computers to the latest version released with 20.3.3.
  4. Run the OC 20.3.3 installer.
  5. Upgrade the other hubs to the latest version released with 20.3.3. For more information, see the Upgrade the Hubs article.
  6. Upgrade the other robots to the latest version released with 20.3.3. For more information, see the Upgrade the Robots article.
Probes and Packages
This section lists the probes and packages that are updated in UIM 20.3.3.
Component
Version
automated_deployment_engine
20.31
cdm
6.60
cm_data_import
20.33
data_engine
20.31
discovery_agent
20.33
discovery_server
20.33
distsrv
9.33
ems
10.25
hdb
9.33S
hub
9.33
hub_secure
9.33S
hub_adapter
9.33S
maintenance_mode
20.31
mon_config_service
20.33
nas
9.32
rsp
5.50
spooler
9.33/9.33S
sla_engine
20.11
udm_manager
20.33
usage_metering
9.28
wasp
20.33
attr_publisher
9.33
java_jre
2.06
mcsuiapp_portlet
1.39
nisapi_wasp
20.33
policy_management_ws
0.27
robot_aix
9.33
robot_deb
9.33
robot_exe
9.33
robot_hpux
9.33
robot_update
9.33
robot_update_secure
9.33S
robot_rpm
9.33
robot_sol
9.33
uimhome
20.33
uimapi
20.33
ump_accountadmin
20.33
uim_reportscheduler
20.33
ump_cabi
4.23
ump_dashboard
20.33
ump_operatorconsole
2.10
ump_slm
20.33
vs2017_vcredist_x64
1.02
vs2017_vcredist_x86
1.02
wasp_alarmviewer_api
2.17
wasp_service_wrapper
20.33
Known Issues
The following are the newly found known issues in UIM 20.3.3:
  • [UIM 20.3.3] Interface Groups Not Displaying in the Dashboard Overview Page
    The Interface groups are not showing up in the dashboard overview page. For example, the Top 10 Entities (Sub Groups) view does not display in the Interface groups.
  • [UIM 20.3.3] Creation Time and Date Alarm Filter Not Working Correctly
    In the Alarm console, when users are trying to use the "Creation time & date" alarm filter with the current date, the filter is not working properly. Additionally, the column name and its date value is not displaying correctly in the Advanced Filters area.
  • [UIM 20.3.3] Session Time-out Not Working in Groups View
    While working in the Groups view in OC, the session time-out does not happen even if the time-out value is configured properly. The session continues to work irrespective of the fact that the user is idle in the Groups view. 
Third-Party Software Agreements
For a list of third-party software agreements that are added in UIM 20.3.3, download the attached file "tpsrs_uim_2033.zip".