Known issues, limitations and workarounds

Infra MP [Doc] WorkAround for System Infrastructure Discovery fails on Ubuntu Node needs to be captured in Release Notes.

Workaround: To resolve this problem, apply CIs related to the corresponding node and follow these steps on the BSM Server:

1. Create a folder named Linux_Deb on the BSM Server at the following locations.

   For Linux:/var/opt/OV/shared/server/tmp/deployment/instrumentation/SystemsInfrastructure/Unix

   For Windows: %OvDataDir%\shared\server\tmp\deployment\instrumentation\SystemsInfrastructure\Unix

   If the above folder is not available on the BSM Server, then first deploy System Infrastructure Discovery on any non-Debian node and proceed with the steps.

2. Copy GetLogfileName.sh and ispi-ovperl files from the /var/opt/OV/shared/server/tmp/deployment/instrumentation/SystemsInfrastructure/Unix/Linux folder into the Linux_Deb folder:

   For Linux:cp Linux/* Linux_Deb/

   For Windows:copy Linux\* Linux_Deb\

3. Deploy the System Infrastructure Discovery Aspect on the node.

4. Verify if the files are present at the following location on the node:

   /var/opt/OV/bin/instrumentation

   On successful run of System Infrastructure Discovery, all the CIs related to the corresponding node will appear in Run-time Service Model (RTSM).

Agent Self Monitoring policies facing issues under OMi MP for Infrastructure2.00.

Workaround: Missing file in the instrumentation folder and process running for older policies. Agent self monitoring is supported only on versions ealier to Operations Agent 12.00. It is recommended to use Operation Agent Health View for self monitoring of Operaitons Agent from 12.00 or higher versions.

To perform self-monitoring for Operations Agent 11.x version, perform following:

1. Instal the HOTFIX_OMI_MANAGEMENT_PACK_FOR_INFRASTRUCTURE_QCCR8D54256__2017_06_20 hotfix.
2. Deploy the Operations Agent Self Monitoring Aspect to the node.

The CIs discovered by Virtual Infrastructure Discovery are not populated by IBM HMC toposync.

Workaround: You must add the product name as ibm_power_hypervisor in the enumeration product_name_enum. To add the product name, follow these steps:

1. Click Admin > RTSM Administration > CI Type Manager > CI Types > System Type Manager. The System Type Manager dialog box appears.

2. Double-click product_name_enum and click Apply. The Update List Definition appears.

3. Add ibm_power_hypervisor to the list and click OK.

You are not able to differentiate between the FileSystem Configuration Item (CI) type when multiple, similar nodes, or FileSystems are discovered.

Workaround: To distinguish the FileSystem CIs for multiple nodes, follow these steps:

1. Click Admin > RTSM Administration > Modeling > CI Type Manager.
2. In the CI Type Manager window, from the CI Types pane, click Managed Object > Configuration Item > Infrastructure Element > Node Element > FileSystem.
3. In the right pane, click Default Label tab.

4. In the CI Type Label Definition format, add user_label to mount_point|root_class.

   For example, user_label|mount_point|root_class

5. Click Save.

End users cannot setup KVM monitoring due to missing documentation.

File System Space utilization monitors wrong devices, generating false alarms.

Performance Alert Utilization alert showing repeating alert conditions.