Computer statuses

Computer statuses provide information about the condition of the computers that are monitored by BigFix Inventory. To properly discover the installed software and measure its license metric utilization, ensure that computers in your environment work correctly.

OK icon OK

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

No Scan Data icon 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: Initiating the capacity scan on all computers.

No Host Scan Data icon No Host Scan Data

The BigFix client is not installed on the host operating system. Depending on the virtualization technology, perform the following actions:
  • For HP Integrity VM, install the BigFix client on the host computer and wait until it uploads the capacity scan results or upload them manually. For more information, see: Initiating the capacity scan on all computers.
  • For Solaris Container/Zones or Logical Domains (LDOM), install the BigFix client in the following zones:
    • Global zone on the control domain
    • Global zones of all local zones in which software is installed
    Wait until the client uploads the capacity scan results or upload them manually. For more information, see: Client installation on Oracle Solaris.
  • For other virtualization technologies, refer to Virtualization Capacity License Counting Rules for more information.

9.2.10 Outdated VM Manager Data icon 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 and default IBM PVU counting is applied to the computer. As a result, license metric utilization that is reported can be higher. For more information, see: Default PVU counting on x86 processors.
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. 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.

No VM Manager Data icon 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 PVU counting is applied to the computer. As a result, reported license metric utilization can be higher than actual. For more information, see: Default PVU counting on x86 processors.

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.