Statuses on the Capacity Scan Health widget

Edit online

The Capacity Scan Health widget provides information whether capacity data is properly collected from the computers in your infrastructure. The data is needed to measure license metric utilization of the software that is installed on the monitored computers.

OK

There are no problems with the computer. No actions are required.

No Scan Data

Results of the capacity scan are missing. To solve the problem, schedule the capacity scan, and upload its results. For more information, see the following links.

For computers with the BigFix® client, see: Initiating the capacity scan on all computers (BigFix scenario).
For disconnected computers, see: Installing the disconnected scanner and gathering scan results (disconnected scenario).

If the computer that reports this status runs on IBM Cloud LinuxONE VS, mark the computer as running on the public cloud. For more information, see the following links.

For computers with the BigFix client, see: Identifying computers as running on public clouds (BigFix scenario).
For disconnected computers, see: Identifying disconnected computers as running on public clouds (disconnected scenario).
For disconnected computers managed by Ansible, see: Identifying computers as running on public clouds (Ansible scenario).

No Host Scan Data

The BigFix client or the disconnected scanner is not installed on the host operating system. Depending on the virtualization technology, perform the following actions:

For Solaris Container/Zones or Logical Domains (LDOM), install the BigFix client or the disconnected scanner in the following zones and wait until it uploads the capacity scan results or upload them manually.
- Global zone on the control domain
- Global zones of all local zones in which software is installed
For more information, see the following links.
- For computers with the BigFix client, see: Client installation on Oracle Solaris (BigFix scenario).
- For disconnected computers, see: Installation of the disconnected scanner on Oracle Solaris.
For other virtualization technologies, refer to Virtualization Capacity License Counting Rules.

Outdated VM Manager Data

Connection to the VM manager is configured, but hardware inventory data that was retrieved from the computer is older than 3 days. License metric utilization is not affected yet. If you do not resolve the issue within 30 days, the computer status changes to No VM Manager Data. As a result, default subcapacity counting is applied to the computer and license metric utilization that is reported can be higher. For more information, see: Default subcapacity counting.

Note: The period after which hardware inventory data is considered outdated is configured by the vmManagerDetachmentNotificationPeriod parameter. The period after which the computer status changes to No VM Manager Data is configured by the vmManagerDetachmentPeriod parameter. For more information, see: Advanced server settings.

To solve the problem, perform the following actions.

Ensure that the VM manager is connected.
Ensure that all parameters of the VM manager connection are correctly configured.
Important: When you troubleshoot the VM manager connection, ensure that the following conditions are fulfilled.
- You have sufficient rights to collect information about the complete virtualization topology including virtual machines, hosts, clusters, and relations among them.
- The UUIDs of virtual machines and hosts are valid and in scope of the particular virtualization technology.
- Information about the number of processors, total number of cores, and processor description is available.
If the problem persists on KVM although the VM manager connection is correctly configured, go to Reports > Hardware Inventory, and check the value in the Server ID column. If the value has the TLM_VM_UUID_of_the_VM format, check whether the UUID is correctly set on the virtual machine. If two or more virtual machines have the same UUID, manually set unique UUIDs for these machines. Note that virtual machines can operate on different hosts.
Ensure that each cluster in your infrastructure has a unique name. In the VMware environment, it is not possible to create two clusters with the same name in the same data center. However, vCenter can manage several data centers at the same time. As a result, one vCenter can control clusters that have the same name but are in different data centers. If multiple clusters share a name, rename them to keep each name unique.
Ensure that the value of the vmManagerDetachmentPeriod parameter is higher than the frequency with which data is retrieved from VM managers. The interval between consecutive retrievals of data is set by the vmm_polling_time_interval parameter and is 30 minutes by default. If the idle time after which a computer that is managed by a VM manager is considered detached is lower, change the value of the vmManagerDetachmentPeriod parameter.

If none of the actions solves the problem, see: Troubleshooting the Outdated VM Manager Data and No VM Manager Data statuses.

No VM Manager Data

Hardware inventory data that was retrieved from the computer is older than a specific period or has never been retrieved. Default subcapacity counting is applied to the computer. As a result, reported license metric utilization can be higher than actual. For more information, see: Default subcapacity counting.

Impact of the peak of metric utilization on the reports depends on why the status appeared. The status can appear in the following situations.

The VM manager is not specified for the computer and hardware inventory data has never been retrieved. If you configure the VM manager within a specific period, the peak of metric utilization is ignored and does not influence the reports. The period is:
- 1 day for version up to 9.2.9.
- 30 days for version 9.2.10 and higher. The period can be configured by the vmManagerDetachmentPeriod parameter.
The VM manager is specified for the computer but the retrieved hardware inventory data is older than a specific period. The period can be configured by the vmManagerDetachmentPeriod parameter and is by default:
- 7 days for version up to 9.2.9
- 30 days for version 9.2.10 and higher
The peak of metric utilization is not removed from the reports that are generated for the period when the computer had the No VM Manager Data status even after you resolve the issue.

To solve the problem, perform the same actions as in case of the Outdated VM Manager Data status. Additionally, if the computer runs on a public cloud, identify it as running on a public cloud. For more information, see the following links.

For computers with the BigFix client, see: Identifying computers as running on public clouds (BigFix scenario).
For disconnected computers, see: Identifying disconnected computers as running on public clouds (disconnected scenario).
For disconnected computers managed by Ansible, see: Identifying computers as running on public clouds (Ansible scenario).

If none of the actions solves the problem, see: Troubleshooting the Outdated VM Manager Data and No VM Manager Data statuses.

Outdated Scan

The last successful capacity scan was run more than 12 hours ago (by default). The problem might occur because the capacity scan is not scheduled. To solve the problem, perform the following steps.

For computers with the BigFix client, perform the following steps.
- Ensure that the Scanner Information analysis is enabled. To enable the analysis, log in to the BigFix console, and go to Sites > External Sites > IBM License Reporting v9 (ILMT) > Analyses. Right-click the Scanner Information analysis, and click Activate.
- Ensure that a regular capacity scan and upload of scan results is scheduled. For more information, see: Initiating the capacity scan on all computers (BigFix scenario).
- Wait for the scheduled import of data or run it manually.
For disconnected computers, perform the following steps.
1. Ensure that the value of the HW_SCAN_SCHEDULE_ENABLED parameter is set to TRUE. For more information, see: Configuration parameters of the disconnected scanner (disconnected scenario).
2. If you used the -noschedule parameter during the installation of the disconnected scanner, regular capacity scan was not scheduled. To schedule the scan, run the scanner installation script without the parameter. For more information, see: Installing the disconnected scanner and gathering scan results (disconnected scenario).
3. Copy results packages from the disconnected computer to the disconnected data source. For more information, see: Setting up daily transfer of scan results to the License Metric Tool server (disconnected scenario).

Information about the percentage of computers with this status is included in the data_condition.txt file in the audit snapshot to show infrastructure health during the period for which the snapshot was generated.

To change the number of hours after which the status is displayed, edit the following parameters on the Advanced Server Settings panel.

For computers with the BigFix client, change the computer_health_outdated_capacity_config parameter.
For disconnected computers, change the computer_health_outdated_capacity_config_disconnected parameter.

For more information, see: Advanced server settings.