OC 20.3.2 Patch

This document provides information about the Operator Console (OC) 20.3.2 patch. OC 20.3.2 is a cumulative patch on top of OC 20.3.0 and OC 20.3.1 with upgrade supported from both the versions.
3
2
Enhanced Features
This patch includes the following enhancements:
Enhanced Group Management
The group management functionality in OC has been further enhanced to ease the group creation, edit, and management process in UIM:
  • You can now define filters while creating static groups.
    • This ability lets you fetch a list of devices at the time of creating a static group. You can then browse the list to identify and add the required devices to the static group. Previously, the ability to define filters was available only for the dynamic groups.
  • Complete end-to-end group creation and edit functionality is now available through the single UI dialog.
    • You no longer need to move across different screens to perform create or edit operations. For example, previously, the process of creating static groups was spread across multiple UI screens. Now, you can achieve the same functionality using the single screen.
    • Similarly, when you try to edit a group, you can find all the options to edit a group at the same place (Actions menu (three dots), Edit group). For example, the following options are now consolidated and are available as part of the edit group dialog:
      • Modify the filter criteria.
      • Add devices to a static group.
      • Remove devices from a static group.
      • Update the group name or description.
      • Change the account information.
      Previously, these options were scattered across different locations in the UI.
For more information, see the Manage Groups article.
Enhanced Monitoring Configuration Service (MCS) UI
The following enhancements have been made to the MCS UI in OC:
  • The Actions column on the Profiles page now logically organizes different actions that you can perform on the created profiles. The available actions are copy a profile, delete a profile, and view the profile details:
    • The copy profile icon is now logically grouped under the Actions column along with the new icons (delete profile and profile details).
    • The delete profile icon lets you delete a created profile directly from the Profiles page. You no longer need to navigate to the specific profile page to delete it.
    • The details icon lets you view the profile details information. The detailed information helps you determine if a configuration profile was successfully applied to target devices.
  • At the time of creating a profile, you can now view the template version. The version of the template is displayed as a separate column (Template Version).
  • In addition to the existing Profiles tab and the Alarm Policies tab, a new tab (MCS Deployment Overview) is now added to the UI. This tab provides an in-context linking of the profiles to MCS Deployment Dashboard. You can access this tab through the same Monitoring Config icon (gear icon) that you use to access the Profiles and Alarm Policies tabs.
  • The Profiles page now contains additional columns, Profile Id and Derived from Group, to provide the relevant information.
For more information, see the Manage Monitoring Using MCS Profile Types article.
Enhanced Session Management
UIM now provides the following token parameters in the wasp.cfg file that help administrators efficiently manage the user sessions:
  • oc.jwt.expiryInSecs
    Allows administrators to specify the appropriate interval (in seconds) after which the session of the inactive users is expired. After the expiry of the session, when the users try to perform any action in the OC UI, they receive a session timeout expiry message along with the login link.
  • oc.jwt.refreshInterval
    Allows administrators to configure the refresh interval (in seconds). Based on the specified interval, the session is appropriately refreshed if the user is active in the UI. Ensure that the value of the refresh interval is lower than the session expiry (oc.jwt.expiryInSecs) value.
    OC users can add the
    keep-alive=true
    parameter to the OC URL to continue working in the UI without any interruption. For example,
    http://<OC_server>/operatorconsole_portlet/standalone_login.jsp?keep-alive=true
    .
View List of Maintenance Schedules for Devices
You can now access the list of maintenance schedules from the device view. When you select a device through the Inventory view, you can see all the maintenance schedules that include the selected device. To access the list, click the Information icon (Name column) for the selected device, and select the Maintenance tab. You can then access the following information:
  • Name of the maintenance schedule that contains the device.
  • Status (Active or Inactive) of the maintenance schedule that contains the device.
  • An option to remove the device from the maintenance schedule. When you click the minus icon (Disassociate column), the device is removed from the maintenance schedule. The corresponding row is also removed from the table.
For more information, see the "View Maintenance Schedule for Devices" section in the View Your Inventory article.
Prerequisites
Verify that your existing environment is using 20.3.0 or 20.3.1.
Deployment
You can upgrade from:
  • OC 20.3.0 to OC 20.3.2
  • OC 20.3.1 to OC 20.3.2
Follow these steps:
  1. Download the OC 20.3.2 patch installer from UIM Hotfix Index.
  2. Run the OC 20.3.2 patch installer on the primary hub and specify the OC server during the upgrade.
  3. Download the MCS 20.31 HF1 (or higher) package bundle and deploy the MCS 20.31 HF1 (or higher) packages as follows:
    If you are upgrading from 20.3.0 to 20.3.2, you need to first upgrade the MCS 20.30 packages to MCS 20.31 and then apply the MCS 20.31 HF1 (or higher) packages. For 20.3.1 to 20.3.2, directly apply the MCS 20.31 HF1 (or higher) packages.
    1. Deactivate the existing mon_config_service probe on the primary hub, deploy the mon_config_service 20.31 HF1 (or higher) package to the primary hub, and activate mon_config_service.
    2. Deactivate the wasp probe on the OC robot, deploy the mon_config_service_ws 20.31 HF1 (or higher) package to the OC robot, and activate wasp. This step is required if you are using the MCS web services.
    3. Deploy the mon_config_service_recon 20.31 HF1 (or higher) package to the primary hub and activate the probe after it gets created. This step is required if you want to use the MCS reconciliation functionality.
    4. Deploy the mon_config_service_cli 20.31 HF1 (or higher) package to the primary hub. This step is required if you are using the MCS CLI functionality.
  4. If your environment contains multiple OC instances, perform the following additional steps on your secondary OC servers:
    • Upgrade the packages listed in Step 2 of the Configure a Secondary OC Server section to the latest version that the OC 20.3.2 patch provides. You can find the latest packages in the local archive.
    • Execute Step 3b on the secondary OC robots.
    • Deploy the ump_slm 20.32 package to the secondary OC robots. The ump_slm 20.32 package is available in the local archive.
Resolved Issues
The following issues have been resolved in this patch release:
  • Resolved an issue where users were facing problems while creating OC groups with the SQL type filter criteria. (Support Case: 32368990)
  • Resolved an issue where users were not able to apply a duration of more than 12 hours while creating a maintenance schedule. (Support Cases: 32391126 and 32418953)
  • Resolved an issue where when users were adding the maintenance schedule through the Swagger UI, the schedules added through the OC UI were disappearing. Additionally, even the Swagger-created schedule was not becoming visible in the UI.
    However, if the Swagger-created schedule was deleted from the database, the schedules created through the UI were appearing again. (Support Cases: 32285971, 32329398, and 32391160)
  • Resolved an issue where in the Alarm properties (expanded item on the tab overview), the policy name was displaying the ID instead of the name. (Support Case: 32387893)
  • Resolved an issue where the time for the maintenance schedule was getting changed to the 24-hour format with AM (for example, 17:00 AM). (Support Case: 32407130)
  • Resolved an issue related to the maintenance mode view. Now, with this patch, when a computer system is in the maintenance mode, the Inventory view does not show an alarm icon; instead, it displays the maintenance mode icon. Also, in the Groups tree view, the system in a group displays the maintenance mode icon instead of an alarm icon. (Support Cases: 32345467 and 32301665)
  • Resolved an issue where OC session was not timing out. The session was remaining active even after being idle for 72 hours.
  • Resolved an issue where the Bus users were observing occasional interchanging of the groups in the tree view. This was occurring when two different account users were creating the groups with the same name.
  • Resolved an issue where an incorrect label “Interface Filters” was getting displayed in the UI when users were trying to edit a dynamic group. The dynamic group was created with the OR conditions in the group filter criteria.
  • Resolved an issue where when the alarms were getting created as a result of an alarm policy in the alarms page of OC, the link to the alarm policy was not enabling for the newly created alarm policies.
  • Resolved an issue where users were unable to view the summary of the maintenance schedule group at the device level. (Support Case: 32419077)
  • Resolved an issue where the MCS Deployment Dashboard was not working; it was displaying the following error:
    Data access error The data required for this page is not currently available
    (Support Cases: 32398161 and 32396442)
  • Resolved an issue where the Dashboard was not filtering the data correctly; it was not considering the time-related filters. (Support Case: 32271065)
  • Resolved an issue where the account contact users were not able to see the metrics in the created Dashboard. (Support Case: 32263741)
Known Issues
The following are the newly added known issues that are applicable for this patch release:
  • [OC 20.3.2] SAML SSO Not Forwarding Additional URL Request Parameters
    With SAML SSO, the session timeout configuration is considered, and every user request adheres to the centralized session time out configured in the wasp.cfg file. It does not allow the users to create the sessions that will never expire with the
    keep-alive
    flag set to
    true
    in the URL request parameter.
  • [OC 20.3.2] Duplicate Devices Are Displaying While Editing a Static Group
    While editing static groups, users can see duplicate devices in the device selection area of the edit group dialog. Out of the two entries, one entry is selected and the other is unselected. If users select an unselected device, they receive an exception in that case.
    This issue has been fixed in UIM 20.3.3.