Troubleshooting OMi Performance Dashboard

Windows: %TOPAZ_HOME%\log\pmi\pmi.log

Linux: $TOPAZ_HOME/log/pmi/pmi.log

To check the logfiles related to integration of OMi Performance Dashboard with BVD, check the following locations:

Windows: %TOPAZ_HOME%\log\pmi\bvd.log

Linux: $TOPAZ_HOME/log/pmi/bvd.log

Problem: Events do not appear in the graph charts.

Solution: To resolve this problem, you must zoom in and check the events. It could be possible that the events are overlapping.

Problem: Real Time graphing displays error message stating No data found error.... in OMi Performance Dashboard.

Solution: To resolve this problem, follow these steps:

For Operations Agent version 12 CIs:

1. Check if HPCS is running by using the URL: http://<systemname:portno>/hpcs/lwistatus For example, http://hostname1:383/hpcs/lwistatus
2. Check if data is loaded from the system by running the URL: http://<systemname:portnumber>/hpcs/v2/Metrics/all For example, http://hostname1:383/hpcs/v2/Metrics/all

3. If HPCS is not running, start the HPCS service using the following command:

   # ovc -restart hpsensor

4. Check if the HP Ops OS Inst to Realtime Inst LTU license is enabled

   oalicense -get –all

5. If the HP Ops OS Inst to Realtime Inst LTU license is not enWabled, you can enable Compute sensor license on the CI using the following command:

   # oalicense -set -type PERMANENT "HP Ops OS Inst to Realtime Inst LTU

6. Restart HPCS service using the following command:

   # ovc -restart hpsensor

For Operations Agent version 11 CIs:

1. Check if the HP Ops OS Inst to Realtime Inst LTU license is enabled by running the following command:

   oalicense -get -all

2. If HP Ops OS Inst to Realtime Inst LTU license is not enabled, enable RTM license on the CI using the following command.

   # oalicense -set -type PERMANENT "HP Ops OS Inst to Realtime Inst LTU

   The LTU is set successfully

3. Restart perfd component and rtmd component.
4. Check if the RTM component of Operations Agent is running on the node.
5. Check perfd and rtmd are running on the node.
6. If the components are not running, start the perfd component and rtmd component on the node.

Problem: Real Time graphing is not updated for every 5 seconds in OMi Performance Dashboard for Operations Agent version 12 CIs.

Solution: To resolve this problem, follow these steps:

1. Change the HPCS data collection interval by editing the HPCS configuration file.

   #vi /var/opt/perf/hpcs.conf

2. Change collection_Interval value which is in seconds and save the file.

3. Restart HPCS service using the following command:

   # ovc -restart

4. Restart OMi Performance Dashboard from Operations Agent
5. Go to OMi Performance Dashboard and in the Performance pane, click .
6. Choose the option Clear Cache to reload the OMi Performance Dashboard data collection from HPCS.

Problem: Performance Dashboard is not loading and not working as expected.

Solution: Check the network log, for any failures in URL calls.

To check the network log, follow these steps:

1. Press F12 in the browser, the debug panel appears.
2. Select Network tab in the debug panel.

Problem: Inconsistency in the data shown in the performance dashboard.

Solution: To resolve this problem, follow these steps:

1.In the Performance pane, click . The performance dashboard is updated with latest data.

2. You can use the following URL to make sure that data is coming for the required time interval.

http://<HOST_NAME>/OVPM/rest/1.0/data/graphdata?ciid=<CI_ID>&class=<CLASS>&ds=<DATASOURCE>&endtime=<END_TIME>&instances=<INSTANCE_NAME>&interval=<INTERVAL>&metrics=<METRIC_NAME>&starttime=<START_TIME>

Problem: Metrics, instances, or classes are available in a CI but are not available in OMi Performance Dashboard.

Solution: To resolve this problem, Click > Clear Cache.

Problem: In Performance Dashboard Mappings, CI Type tree does not appear in the left pane.

Solution: To resolve this problem, follow these steps:

1. Check if Adobe flash player is installed in the browser.
2. If Adobe Flash Player is installed, check if it is enabled. If it is disabled, enable it.

Problem: CI Type tree loads with error message

Solution: To resolve this problem, you must log out from OMi and log in to OMi.

Problem: In the Performance Dashboard Mappings, the Save icon is not enabled.

Solution: To resolve this problem, follow these steps:

1. If you make any changes, the Save option is enabled.
2. To enable Save option, you can edit the CI Attribute or Assigned Dashboards.

Problem: Performance Dashboard Mappings does not change locale on Internet Explorer.

Solution: To resolve this problem, follow these steps:

1. Close all the tabs of the browser.
2. Open the browser again.
3. Open the OMi console.
4. Log on with the credentials.
5. Click Administration > Operations Console > Performance Dashboard Mappings

Problem: A performance dashboard drawn with metrics obtained from the RTM data source stops receiving updates if the HPE Operations agent (or the RTM component of the agent) on the node that hosts the RTM data source stops running. The performance dashboard title bar shows no data point.

Solution: When the HPE Operations agent (or the RTM component of the agent) starts running on the node again, the performance dashboard window starts showing the updated data.

Problem: SiteScope Real Time is not working

Solution: To resolve this problem, follow these steps:

1. Check if configured SiteScope version is 11.22 or above.
2. Check connectivity with the SiteScope server from OMi server. You need to ensure that the SiteScope server is up and running.
3. Check monitored_by attribute of the Selected CI in OMi contains SiteScope. If SiteScope is not available then there could be a synchronization issue with SiteScope to OMi. Contact SiteScope or OMi team.

4. Check if the Integration XML is available at the following location:

   Windows: %ovdatadir%\shared\server\conf\perf\pmiworkdir\data\SiteScope_RTM_GC_Integration.xml

   Linux: /var/opt/OV/shared/server/conf/perf/pmiworkdir/data/SiteScope_RTM_GC_Integration.xml

5. In SiteScope, click Preferences and perform the following steps:

   Search/Filter tag

   1. Check if Filter is created
   2. Click group containing monitors or a monitor and click Properties > Search/Filter tag. Check if the filter is listed and the option is enabled.
   3. Click Properties > Monitor run settings > Frequency and check if frequency is set to 15 seconds for the monitors for which RTM data is not showing up in OMi Performance Dashboard.

   Integration Preferences

   1. Click Integration Preferences. Check if Data integration is added. If data integration is not added, see SiteScope documentation.
   2. If the data integration is available, select a data integration , click Edit and check for the following configurations
      1. Check if the Receiver URL is OMi Performance Dashboard listener URL. For example, http://<OMI_HOST_NAME>/OVPM/rest/SiteScopeDataReceiver
      2. Check if the Encoding is UTF-8.
      3. Check if the Reporting Interval is 15 seconds.
      4. Check if the Time Synchronization Interval is 10 minutes.
      5. Check if the GZIP compression only.
      6. Check the Web Server Security Settings, Specify the username and password to access the OMi Performance Dashboard if the OMi Performance Dashboard is configured to use basic authentication. Otherwise, leave blank

      7. In the Reporting Tags, check if the filter applied on monitors is selected.

   6. Check for the configured receiver URL in SiteScope, if there are any errors in the data_integration.log file of SiteScope installed machine.

   1. Check <Sitescope_Installed_Folder>\log\data_integration.log file.

      If error exists then configured receiver URL is incorrect. For more information, see SiteScope documentation.

   2. If there are no errors in the log file then enable debug mode for SiteScope data integration log file.

   3. In <Sitescope_Installed_Folder>\conf\core\Tools\log4j\PlainJava\log4j.properties file , change following text:

      log4j.category.dataIntegration=${loglevel}, data.integration.appender

      to

      log4j.category.dataIntegration=DEBUG, data.integration.appender

   4. Enable OMi Performance Dashboard log level to Trace in log4j.properties

      Windows: %TOPAZ_HOME%\log\pmi\pmi.log

      Linux: $TOPAZ_HOME/log/pmi/pmi.log ( )

6. Check if RTM data as shown in the following text is getting logged for the selected monitor.

   com.hp.pm.core.adapter.metric.SiSRTMDataReceiver:doPost() -> RTM XML Content

   <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

   <performanceMonitors collector="SiteScope" collectorHost="martellvm8">

   <group name="Demo_Monitors" desc="">

   <monitor type="Memory" target="example.example.com" targetIP="<IP>" time="1417567245958" quality="1" name="Memory monitor on system">

   <counter value="49" quality="" name="percent used"/>

   </monitor>

   </group>

   </performanceMonitors>

Problem: SiteScope historical data is not working

Solution: To resolve this problem, follow these steps:

1. Check if configured SiteScope version is 11.22 or above.
2. Check if SiteScope server is configured in OMi > Administration > Setup and Maintenance > Connected Servers
3. Check connectivity with the SiteScope server from OMi server. You need to ensure that the SiteScope server is up and running.
4. Check monitored_by attribute of the Selected CI contains SiteScope. If SiteScope is not available, then there is a synchronization issue with SiteScope to OMi.

5. Check if the Integration XML is available at the following locations:

   Windows: %ovdatadir%\shared\server\conf\perf\pmiworkdir\data\SiteScope_GC_Integration.xml

   Linux: /var/opt/OV/shared/server/conf/perf/pmiworkdir/data/SiteScope_GC_Integration.xml

6. Analyze the OMi Performance Dashboard log file for any errors or exceptions:

   Windows: %TOPAZ_HOME%\log\pmi\pmi.log

   Linux: $TOPAZ_HOME/log/pmi/pmi.log

   In the log files, check the following:

   1. Check if Connected Server API returns SiteScope server data.

      com.hp.pm.core.adapter.metric.SiSDAMetricAdapter:loadMeta() -> Sitescope Connected Server size : 1

   2. Check if RTSM API returns monitors data for the selected CI.

      com.hp.pm.core.adapter.metric.SiSDAMetricAdapter:loadMeta() -> Number of Serversthe selected CI associated with 1

      com.hp.pm.core.adapter.metric.SiSDAMetricAdapter:loadMeta() -> Selected CI's Serve Name martellvm8.ind.example.com

      com.hp.pm.core.adapter.metric.SiSDAMetricAdapter:loadMeta() -> Selected CI's Topology Monitor Map size 2

      com.hp.pm.core.adapter.metric.SiSDAMetricAdapter:loadMeta() -> Selected CI's Monitor Name Demo_Monitors/CPU Monitor on iwfvm00127

   3. Check if SiteScope DAL API returns data to OMi Performance Dashboard

      com.hp.pm.core.adapter.metric.SiSDAMetricAdapter:loadMeta() -> Querying Sitescope DAL API with query parameters

      com.hp.pm.core.adapter.metric.SiSDAMetricAdapter:getMonitorsForASiSServer() -> Full Server Name martellvm8.ind.example.com

      com.hp.pm.core.adapter.metric.SiSDAMetricAdapter:getMonitorsForASiSServer() -> Short Server Name martellvm8

      com.hp.pm.core.adapter.metric.SiSHelper:getHistoryData() -> Getting SiS History data

      com.hp.pm.core.adapter.metric.SiSHelper:getHistoryData() -> Server Name martellvm8

      com.hp.pm.core.adapter.metric.SiSDAMetricAdapter:getMonitorsForASiSServer() -> SiS histroy mapsize 1

      com.hp.pm.core.adapter.metric.SiSDAMetricAdapter:getMonitorsForASiSServer() ->Monitor List size.. 3

      com.hp.pm.core.adapter.metric.SiSDAMetricAdapter:loadMeta() -> Monitor Output sizevia DAL 3

      com.hp.pm.core.adapter.metric.SiSDAMetricAdapter:loadMeta() -> Final Output size 2

7. If SiteScope server is down then you see the following connection refused exception in the log file:

   com.hp.pm.core.adapter.metric.SiSDAMetricAdapter:loadMeta() -> Querying Sitescope DAL API with query parameters

   com.hp.pm.core.adapter.metric.SiSHelper:getDataFromDALApi() -> Error getting data from Sitescope DAL API: ; nested exceptionis: java.net.ConnectException: Connection refused: connect

   com.hp.pm.core.adapter.metric.SiSHelper:getDataFromDALApi() -> AxisFault

   faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException

   faultSubcode:

   faultString: java.net.ConnectException: Connection refused:connect

8. If there is any data request error, you see the following exception in the log file:

   com.hp.pm.core.adapter.metric.SiSHelper:getDataFromDALApi() -> Error getting data from Sitescope DAL API: com.mercury.sitescope.api.data.exception.RequestDataExceedLimitException: Error Code: 77104.

   Error Description: Request from start date Tue Sep 02 04:06:14 IST 2014 to Wed Sep 03 04:06:14 IST 2014 resources are over the configured maximum limit: 20 MB (approximate request resources size is 660MB).

   Process succeed for time range: Tue Sep 02 04:06:14 IST 2014 to Tue Sep 02 04:49:39 IST 2014.

   You need to change the resource size limitation. Go to SiteScope infrastructure preferences and change Data acquisition API single request size value.

9. Check if the data is getting logged for these monitors in SiteScope Server with status good from current time to last one day.

   <Sitescope_Installed_Folder>\logs\Sitescope.log

Problem: Favorites to compare same metrics of different CIs does not display data. This happens when the CIs for which the metrics are compared, do not have the system time set as per the time zone of the region.

Solution: For the Favorites to display data, make sure that the system time is set to the time zone of the region where the CIs are located.

Problem: When you select the MAC address of an NIC as a CI from the View Explorer, the corresponding predefined performance dashboards are not listed. This is because while creating the Performance Dashboard Mappings, the NIC name is mapped to the predefined performance dashboards and not the MAC address.

Solution: You can select the corresponding host to view the predefined performance dashboards.

Problem: Unable to integrate OMi Performance Dashboard with Cloud Optimizer.

Description: To resolve this problem, follow these steps:

1. Check if the monitored_by attribute of the Selected CI in OMi contains Cloud Optimizer. If it does not contain Cloud Optimizer then there could be a synchronization issue with Cloud Optimizer to OMi. Contact Cloud Optimizer team.

2. Check if the Integration XML is available in the following locations:

   Windows: %ovdatadir%\shared\server\conf\perf\pmiworkdir\data\vPV_GC_Integration.xml

   Linux: /var/opt/OV/shared/server/conf/perf/pmiworkdir/data/vPV_GC_Integration.xml

3. Check if the time configured in both OMi and Cloud Optimizer is same.

4. Check instance information in RTSM Response:

   <graphParameters>

   <systemNames>

   <systems>

   <systemName>16.184.47.225</systemName>

   <port>8444</port>

   </systems>

   <systems>

   <systemName>martell.ind.example.com</systemName>

   </systems>

   </systemNames>

   <instanceNames>

   <instance>

   <instanceName>martell.ind.example.com</instanceName>

   <graphParameters>

   <systemNames>

   <systems>

   <systemName>16.184.47.225</systemName>

   <port>8444</port>

   </systems>

   <systems>

   <systemName>martell.ind.example.com</systemName>

   </systems>

   </systemNames>

   <instanceNames>

   <instance>

   <instanceName>martell.ind.example.com</instanceName>

5. Check if metadata that is queried using Rest API to Cloud Optimizer server is successful

   INFO : com.hp.pm.core.adapter.metric.AbstractMetricAdapter:loadMeta() -> In loadMeta - The selected CI id c751a5dccc27daafd9922abcae1580b4

   INFO : com.hp.pm.core.adapter.metric.AbstractMetricAdapter:loadMeta() -> The selected CI type unix

   INFO : com.hp.pm.core.adapter.metric.AbstractMetricAdapter:loadMeta() -> The selected CI Name syspulsevm200.ind.example.com

   INFO : com.hp.pm.core.adapter.metric.AbstractMetricAdapter:loadMeta() -> The selected CI's Server Name 16.184.47.225

   INFO : com.hp.pm.core.adapter.metric.AbstractMetricAdapter:loadMeta() -> The selected CI's Server Port 8444

   INFO : com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getRestOutputData() -> The rest url https://16.184.47.225:8444/PV/api/v1/loadmeta?name=syspulsevm200.ind.example.com&type=unix&context=PMI

   INFO : com.hp.pm.core.adapter.metric.AbstractMetricAdapter:queryRestAPI() -> The response status code 200

   INFO : com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getRestOutputData() -> Connection to vPV Rest url is success

6. If querying via Rest API fails, then you see following error in the log file

   com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getRestOutputData() -> The rest url https://goldrch7vm8.ind.example.com:8444/PV/api/v1/loadmeta?name=goldrch7vm7.ind.example.com&type=unix&context=PMI

   com.hp.pm.core.adapter.metric.AbstractMetricAdapter:queryRestAPI() -> Error occured while connecting to vPV rest url.

   com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getRestOutputData() -> Failed to get response from the vPV rest url with status code 0

   com.hp.pm.core.adapter.metric.AbstractMetricAdapter:loadMeta() -> vPV Output for the selected CI is null or empty

7. For checking the URLs, open a new tab in the same browser where OMi is launched. Copy the URL to the new tab and launch them.

8. Valid JSON response should be retrieved

9. Check if data queried from Rest API from Cloud Optimizer is successful.

   INFO : com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getDataRows() -> In GetDataRows

   INFO : com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getDataRows() -> Instance Full Name 16.184.47.225/VCENTER_HOST__2

   INFO : com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getDataRows() -> Instance Name VCENTER_HOST__2

   INFO : com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getRestOutputData() -> The rest url https://16.184.47.225:8444/PV/api/v1/getdatarows?instanceId=VCENTER_HOST__2&className=VCENTER_HOST&metrics=CPUPhysTotalUtil&summarizeMins=5&startEpochMillis=1448321439000&endEpochMillis=1448364639000

   INFO : com.hp.pm.core.adapter.metric.AbstractMetricAdapter:queryRestAPI() -> The response status code 200

   INFO : com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getRestOutputData() -> Connection to vPV Rest url is success

   INFO : com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getDataRows() -> Get data rows row count 143

10. Open a new tab in the same browser where OMi is launched. Copy the URL to the new tab and launch them. Valid JSON response should be retrieved.

11. If initstring configured in Cloud Optimizer is not correct then you see following exception in the log file:

    com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getRestOutputData() -> The rest url https://goldrch7vm8.ind.example.com:8444/PV/api/v1/loadmeta?name=goldrch7vm7.ind.example.com&type=unix&context=PMI

    com.hp.pm.core.adapter.metric.AbstractMetricAdapter:queryRestAPI() -> Error occured while connecting to vPV rest url .

    com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getRestOutputData() -> Failed to get response from the vPV rest url with status code 401 (forbidden access)

12. Check if SSO (Single Sign-On ) is configured properly in Cloud Optimizer server similar to OMi.

13. In OMi, navigate to Administration > Users > Authentication Management. In the Single Sign-On Configuration section, click Edit to open Single Sign On Editor.

14. Check for Token Creation Key (initString). Log on to Cloud Optimizer server machine and check for initString in the following location:

    /opt/OV/www/webapps/PV/WEB-INF/classes/lwssofmconf.xml

Problem: Cloud Optimizer data source is not listed in performance dashboard while creating or editing a graph.

Solution: To resolve this problem, follow these steps:

1. Check if the monitored_by attribute of the selected CI in OMi contains the value vPV. If the attribute contains any other value, there might be a topology synchronization issue between Cloud Optimizer and OMi.

2. Check if the Integration XML file is available in the following locations:

   • Windows: %ovdatadir%\shared\server\conf\perf\pmiworkdir\data\vPV_GC_Integration.xml
   • Linux: /var/opt/OV/shared/server/conf/perf/pmiworkdir/data/vPV_GC_Integration.xml

Problem: Classes from Cloud Optimizer are not listing in performance dashboard while creating or editing a graph.

Solution: To resolve this problem, follow these steps:

1. Check if the value of the monitored_by attribute of the selected CI in OMi is vPV. If the attribute contains any other value, there might be a topology synchronization issue between Cloud Optimizer and OMi.
2. If the value of the monitored_by attribute is vPV, then check if the time configured in both OMi and Cloud Optimizer is the same.
3. Check if the instance ID definition for the selected CI type in Administration > Operations Console > Performance Dashboard Mappings is configured to the correct CI attribute.
4. Check if the vPV server host is ping-able from the OMi server.

5. Check if the selected CI has is_datacollector relationship to vPV running software and if vPV running software has the composition relationship with the vPV server host.

6. Analyze the performance dashboard trace file:

   1. Check instance information in RTSM Response:

      com.hp.pmi.graphing.RTSMQueryHandler:getGraphData() ->

      <systemNames>

      <systems>

      <systemName>vpvhost11-wed.ind.hp.com</systemName>

      <port>8444</port>

      </systems>

      <systems>

      <systemName>vpvqa14</systemName>

      </systems>

      </systemNames>

      <instanceNames>

      <instance>

      <instanceName>vpvqa14</instanceName>

      </instance>

      </instanceNames>

   2. Check if the metadata(classes/metrics) that is queried using Rest API to Cloud Optimizer server is successful. If querying Rest API fails, then you will see the following error in the log file:

      com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getRestOutputData() -> The rest url https://vpvhost11-wed.ind.hp.com:8444/PV/api/v1/loadmeta?name=vpvqa14.ind.hp.com&type=unix&context=PMI

      com.hp.pm.core.adapter.metric.AbstractMetricAdapter:queryRestAPI() -> Error occured while connecting to vPV rest url

      com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getRestOutputData() -> Failed to get response from the vPV rest url with status code 0

      com.hp.pm.core.adapter.metric.AbstractMetricAdapter:loadMeta() -> vPV Output for the selected CI is null or empty

   3. For checking the Cloud Optimizer Rest URLs, open a new tab in the same browser where OMi is launched. Copy the URL to the new tab and launch the REST URLs. You will retrieve a valid JSON response.

   4. Check if data queried from Cloud Optimizer using REST API is successful.

   5. Open a new tab in the same browser where OMi is launched. Copy the URL to the new tab and launch them. You will retrieve a valid JSON response.

   6. If initstring (LWSSO token String or Single Sign on token String) configured in Cloud Optimizer is not correct, then you will see the following exception in the log file:

      com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getRestOutputData() -> The rest url https://vpvhost11-wed.ind.hp.com:8444/PV/api/v1/loadmeta?name=vpvqa14.ind.hp.com&type=unix&context=PM

      com.hp.pm.core.adapter.metric.AbstractMetricAdapter:queryRestAPI() -> Error occured while connecting to vPV rest URL

      com.hp.pm.core.adapter.metric.AbstractMetricAdapter:getRestOutputData() -> Failed to get response from the vPV rest url with status code 401 (forbidden access)

   7. Check if Single Sign-On (SSO) is configured properly in Cloud Optimizer server similar to OMi.

   8. )In OMi, navigate to Administration > Users > Authentication Management. In the Single Sign-On Configuration section, click Edit to open Single Sign-On Editor.

      Check for Token Creation Key (initString). Log on to Cloud Optimizer server machine and check for initString in the following location:

      /opt/OV/www/webapps/PV/WEB-INF/classes/lwssofmconf.xml

Problem: When a performance dashboard containing more than 15 charts each of height 250 pixels is saved in PDF format, the PDF appears blank.

Solution: To resolve this problem, reduce the number of charts on the dashboard and generate the PDF again.

Problem: Operations Connector data source is not listed while creating or editing a chart in Performance Dashboard.

Solution: To resolve this problem, follow these steps:

1. Check if the value of the monitored_by property is BSMC:<CONNECTED_SERVER_NAME>. If it contains any other value, there might be a topology synchronization issue.

2. Check if the performance dashboard integration XML is available at the following locations:

   • %ovdatadir%\shared\server\conf\perf\pmiworkdir\data\BSM_Connector_GC_Integration.xml (Windows)
   • /var/opt/OV/shared/server/conf/perf/pmiworkdir/data/BSM_Connector_GC_Integration.xml (Linux)

Problem: Classes from Operations Connectors are not listed while creating or editing a chart in Performance Dashboard.

Solution: To resolve this problem, follow these steps:

1. Check if the value of the monitored_by property is BSMC:<CONNECTED_SERVER_NAME>. If it contains any other value, there might be a topology synchronization issue.
2. If the value of the monitored_by property is BSMC:<CONNECTED_SERVER_NAME>, do the following:
   1. Check if Operations Connector is configured as a connected server in OMi: Administration > Setup and Maintenance > Connected Servers
   2. Check the data_externalid property of the selected CI as performance dashboard uses this property to identify the right classes and metrics of the CI from the agent that stores data for Operations Connector.
3. Check if the host name configured in Connected Servers page is ping-able from the OMi server.
4. Analyze the performance dashboard trace file:

   1. Identify if connected server name is retrieved properly:

      • com.hp.pmi.graphing.GraphDataProvider.getBSMCMonitoredBy()->Connected server display name ><iwfvm07996>
      • com.hp.pmi.graphing.GraphDataProvider.getConnectedServerHostName()->Host name of the BSMC Connected Server = iwfvm07996.hpeswlab.net

   2. Check instance information in RTSM response.

   3. Check if data is logged for this instance in Operations Connector.

Problem: All metrics for a selected class from Operations Connectors are not listed in the performance dashboard.

Solution: To resolve this problem, follow these steps:

1. Check if metric names contain arithmetic operators like +, -, * and , /, as these operators are not supported in performance dashboard.
2. If the metric names do not contain any arithmetic operators but are still not listed, refer the troubleshooting tips in Operations Connector documentation.

Problem: OpsBridge Store datasource is not listed in Performance Dashboard while creating or editing a graph.

Solution: To resolve this problem, follow these steps:

1. Check if the value of the monitored_by property is BSMC:<CONNECTED_SERVER_NAME>. If it contains any other value, there might be a topology synchronization issue between OMi, and Operations Connector or Operations Agent.

2. Check if OMi Performance Engine is running properly. Type the following command in OMi Performance Engine server:

   #/opt/OV/bin/ovc -status PE

   All the PE services should be running successfully.

3. Check if the Performance Engine node is configured in Administration > Setup and Maintenance > Infrastructure Settings:
   1. Choose the Application as Performance Engine.

   2. Provide Performance Engine node details.

      Example: http://<PESERVER_HOSTNAME>:<PORT_NUMBER>

   3. Provide Performance Engine node password.

4. Check the Performance Engine endpoint status by opening a new tab in the same browser where OMi is launched. Copy the URL to the new tab and launch the REST URLs.

   http://<OMi_Gateway_server/PE/rest/1.0/admin/endpoint

   Output:

   {"Status" : "Success", "EndPoint" : "http://<PE_Server>:7387/perfengine/HPCSListener"}

5. Check if the performance dashboard integration XML is available at the following locations:

   Windows: %ovdatadir%\shared\server\conf\perf\pmiworkdir\data\PERF_STORE_GC_Integration.xml

   Linux: /var/opt/OV/shared/server/conf/perf/pmiworkdir/data/PERF_STORE_GC_Integration.xml

6. Check for errors in OMi Performance Engine server by verifying the logs in /var/opt/OV/pe/log/ folder.

7. Check for errors in OMi logs at the following location:

   Windows: %TOPAZ_HOME%\log\PE\perfengine.log

   Linux: /opt/HP/BSM/log/PE/perfengine.log

Problem: Classes from OpsBridge store are not listing in PD while creating or editing a graph.

Solution: To resolve this issue, follow these steps:

1. Check if the value of the monitored_by property is BSMC:<CONNECTED_SERVER_NAME>. If it contains any other value, there might be a topology synchronization issue between OMi, and Operations Connector or Operations Agent.

   If the monitored_by contains "OM", then for the selected CI, do the following:

   1. Find related monitored agent node in OMi: Administration > RTSM Administration > Modeling > IT Universe Manager.
   2. For the Agent node, check "composition" relationship to "HP Operations Agent" CI type.

   3. On "HP Operations Agent" CI, right click to see the properties and get the property 'Name' containing core id of the agent. This core id should be same as the output of the following command on the agent node:

      $OVINSTALLDIR/bin/ovcoreid

   If the monitored_by contains "BSMC:<Connected_server_name>", then for the selected CI, do the following:

   1. Check if the Operations Connector is configured as a connected server in OMi: Administration > Setup and Maintenance > Connected Servers.
   2. Check for data_externalid property for the selected CI as performance dashboard uses this property as the instance key to identify the right classes and metrics of the CI from the OpsBridge store.

   3. Check if the configured connected server host has "composition" relationship to ‘HP Operations Agent’ CIType in OMi: Administration > RTSM Administration > Modeling > IT Universe Manager.

      On "HP Operations Agent" CI, right click to see the properties and get the property 'Name' containing core id of the agent. This core id should be same as the output of the following command:

      $OVINSTALLDIR/bin/ovcoreid on the OpsConnector host

2. Check the metadata Rest API (classes/metrics/instances) by opening a new tab in the same browser where OMi is launched. Copy the URL to the new tab and launch the REST APIs.

   <PROTOCOL>://<OMi_GATEWAY_SERVER>/PE/rest/1.0/data/cimetadata?ciid=<COREID_OF_AGENT>

   If Rest API output is an empty list then check if PE cache server(redis) has metadata for the selected CI.

   1. Log in to the Performance Engine server.

   2. Run the redis command line tool:

      /opt/HP/BSM/HPEPerfEngine/redis/src/redis-cli -p <REDIS_PORT> -a <PE_PASSWORD>

   3. Invoke the redis command to list metadata for a selected CI.

      zrangebylex perfengine:metadata [<CORE_ID> "[<CORE_ID>\uFFFF“

      Example: zrangebylex perfengine:metadata [ab1234-38d9-758c-123d-1234 "[ab1234-38d9-758c-123d-1234 \uFFFF"

      If the above command fails to list the metadata for the selected CI, check for errors in Performance Engine server by verifying the logs at the following location:

      /var/opt/OV/pe/log/

Problem: No data found error in performance dashboard for the metrics from OpsBridge Store.

Solution: To resolve this issue, follow these steps:

1. Check the performance dashboard log files for REST APIs at the following locations:

   Windows: %TOPAZ_HOME%\log\pmi\pmi.log

   Linux: opt/HP/BSM/log/pmi/pmi.log

2. Check the performance dashboard Rest API data by opening a new tab in the same browser where OMi is launched. Copy the URL to a new tab and launch the REST APIs:

   <PROTOCOL>://<OMi_GATEWAY_SERVER>/OVPM/rest/1.0/data/graphdata?alias=.....

3. If performance dashboard data is not available, then check PE Rest API for data by opening a new tab in the same browser where OMi is launched. Copy the URL to a new tab and launch the REST APIs:

   <PROTOCOL>://<OMi_GATEWAY_SERVER>:<OMi_PORT_NUMBER>/PE/rest/1.0/data/graphdata?ciid=.......