Release notes > Known issues, limitations, and workarounds

Known issues, limitations, and workarounds

Problems and limitations are identified with a change request (QCCR) number. For more information about known problems, visit, or contact your HPE Support representative directly.


Custom Images uploaded with OMi 10.60 or 10.61 must be reuploaded after an upgrade.

Upgrade / Update

When updating or upgrading your OMi servers, do not edit the KPI configuration until the upgrade has completed on all servers.


Title: OA files are still available after OMi uninstallation (QCCR1H117148)

Description: After uninstalling OMi 10.62, the Operations Agent shortcut and the file common_oa_def are still available, but the Agent is not working.

Workaround: Delete the leftover Operations Agent files.

Title: Agent is sometimes not started on DPS. (QCCR8D47298)

Description: When installing OMi, the Operations Agent is sometimes not started on the data processing server.

Workaround: Run ovc -start after the OMi installation.

Title: SiS Integration: integration of OMi with non-hardened SiS 11.33 does not work. (QCCR1I124015)

Description: When setting up a SiteScope 11.33 server (non-TLS setup) as a connected server in OMi 10.61 (TLS setup), the connected server status is failed.

Multiple errors are logged into the SiS error.log, for example:

2017-01-13 07:52:34,307 [http-bio-8080-exec-5] ( ERROR - problem while sending data to URL: https://<host>:443/topaz/topaz_api/api_invoke.asp error: URL: https://<host>:443/topaz/topaz_api/api_invoke.asp, host: <host>, port: 443, UsingProxy: false, isHTTPS(SSL): true, Remote host closed connection during handshake, currentRetry: 0

Workaround: The non-HTTPS SiteScope tries to communicate with HTTPS OMi10.62 via SSLv3, which is not allowed due to OMi10.62's TLS configuration, so the apache aborts the connection attempts.

If possible, switch Sitescope to HTTPS and try the integration again. If this is not possible, perform the following workaround to allow SSLv3 on apache:

  1. Open <OMi_install_dir>\WebServer\conf\extra\httpd-ssl.conf and alter the following configuration line:

    SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1

    Change the line as follows:

    SSLProtocol all -TLSv1 -TLSv1.1

  2. Restart the apache web server and recreate the connected server.

Title: In case of uploading multiple files if error occurs in one of the files then upload request for subsequent files should not be sent from the UI (QCCR8D95359)

Description: If an error occurs while uploading one of the JAR files in External Instructions, Custom Actions, or Event Processing Customizations, the user interface does not disable upload of the remaining JAR files.

Workaround: If the upload of a JAR file fails, the Cancel button is enabled. Click Cancel to go back to the home page of the screen from which the upload was initiated. All the JAR files that were successfully uploaded before the error occurred remain unimpacted and the script is saved. However, the remaining JAR files are not uploaded irrespective of the file type or file size.

Title: 'File already exists' warning notification is not displayed in case of adding a few the same .jar files to External Instruction (applied only on IE) (QCCR8D94279)

Description: When uploading JAR files in External Instructions, Custom Actions, or Event Processing Customizations, "File already exists" message is not displayed even if you select the same file for upload. This issue is seen only in Internet Explorer, not other browsers

Workaround: Ensure that you do not upload the same file.

OMi Performance Dashboard

Note The minimum recommended screen resolution for the OMi Performance Dashboard is 1280x1024.

Title: Import Graph-Table graph showing same metric values for all instances. (QCCR1A183471)

Description: If you are defining multiple instances that have the same metric, the charts are not updated correctly with the metric values and labels.

Workaround: By default, the label of the chart is defined as @@[METRIC]. If you are defining a chart with a metric for different instances of a class, then the chart legend is duplicated with the same metric name, and chart data is not updated correctly. If you are creating a chart for different instances of a class, it is recommended to differentiate the chart legend by specifying an instance name in the label of the chart. You can update the label of the chart as @@[METRIC] - @@INSTANCENAME

Title: CI Type tree shows different information than details and Content Packs show unresolved content. (QCCR8D43630)

Description: The content manager shows some warnings about missing content. In addition, the Performance Dashboard Mappings show no mappings for some CI types.

Workaround: To resolve this problem, perform the following steps on the OMi Gateway Server:

  1. Launch OMi in a browser.
  2. Open a new tab in the same browser and launch http://<OMi_Gateway_Server>/OVPM/rest/1.0/admin/clearcache/all
  3. Click Clear Cache.
  4. In OMi, go to Administration > Operations Console > Performance Dashboard Mappings.
  5. Check if that the Performance Dashboard Mappings screen loads without errors or warnings.

Title: PD- Conditional Dashboards - Condition dashboard assignment not working for properties like Actual Deletion Period, Deletion Candidate Period (integer data type) (QCCR8D96198)

Description: Conditional dashboard assignment fails if a static CI Property is selected while creating a conditional dashboard.

Workaround: Do not select a static CI Property (for example, "Actual Deletion Period", "Deletion Candidate Period") while creating conditional dashboards.

OMi Performance Engine

Title: Data loss in PE after adding new node to the cluster and performing rebalance operation (QCCR1A188544)

Description: If a new node is added to the OMi Performance Engine cluster, streamed data is either delayed or lost after submission.

Workaround: To solve this issue, restart the PE Listener service on all the nodes after the rebalance operation. Follow these steps:

  1. Log into the OMi Performance Engine node using ssh or telnet.

  2. Execute the following command:

    /opt/OV/bin/ovc -restart pelistener

  3. Repeat step 1 and step 2 on all the nodes in the cluster.

Title: Performance Engine fails to push data to configured Vertica once the Vertica service is restarted. (QCCR1A189833)

Description: OMi Performance Engine does not send metrics to the Vertica database when the Vertica service is restarted.

Workaround: To resolve this issue, follow these steps:

  1. Restart PE listener services.

    /opt/OV/bin/ovc -restart pelistener

    Note In Performance Engine cluster deployments, repeat this step on each node in the cluster.

  2. Invoke the Performance Engine API in OMi to update the cache configuration. Open the following URL on the OMi server:

    http://<OMi gateway host info>/PE/rest/1.0/admin/reconfigure/cache