Home
Managing the infrastructure
After you complete the initial configuration of BigFix Inventory, learn how to manage components of its infrastructure: VM managers, server, database, and data sources.
Managing VM managers
VM managers are pieces of software that create, manage, and monitor virtual machines. You configure connections to VM managers so that BigFix Inventory can gather data that is required to calculate utilization of license metrics in virtual environments.
Advanced VM management (distributed)
Use advanced VM management if the BigFix server cannot connect to some of the VM managers because they are in separated networks. This approach requires that you install an additional VM Manager Tool, and configure VM managers through the command line.
Additional configuration
Additional configuration tasks are intended to give you more control over VM Manager Tool. You can use them to customize the VM Manager Tool, or to enable filtering of virtual machines based on their UUIDs. All of these tasks are optional.
UUID-based virtual machine filtering
The purpose of filtering based on universally unique identifier (UUID) is to collect the capacity data only for chosen virtual machines. The remaining ones are omitted and not updated in BigFix Inventory.
Obtaining the list of virtual machine UUIDs
You can use the list of virtual machine UUIDs that are currently connected to the BigFix Inventory server to select those for whom the capacity data is to be collected.

Managing the infrastructure
After you complete the initial configuration of BigFix Inventory, learn how to manage components of its infrastructure: VM managers, server, database, and data sources.
- 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.
- Managing VM managers
  VM managers are pieces of software that create, manage, and monitor virtual machines. You configure connections to VM managers so that BigFix Inventory can gather data that is required to calculate utilization of license metrics in virtual environments.
  - Default PVU counting on x86 processors
    To properly calculate PVU subcapacity, BigFix Inventory requires information about the number of processor cores that are available to virtual machines and on the physical computers that host these machines. If the information is not available, license metric utilization cannot be properly calculated and reported results might be over-counted for x86 processors.
  - Supported virtualization types
    BigFix Inventory requires that connections to VM managers are defined for the following virtualization types: Kernel-based Virtual Machine, Microsoft Hyper-V, VMware vSphere, and Xen.
  - Flow of capacity data from VM managers
    To understand how capacity data is gathered in virtual environments, see what data flows between virtual machines, VM Manager Tool, and the BigFix Inventory server, and how frequently it is transferred.
  - Basic VM management (central)
    Use basic VM management if the BigFix server can connect to VM managers in your infrastructure. It is the default method of configuring connections to VM managers through the BigFix Inventory user interface.
  - Advanced VM management (distributed)
    Use advanced VM management if the BigFix server cannot connect to some of the VM managers because they are in separated networks. This approach requires that you install an additional VM Manager Tool, and configure VM managers through the command line.
    - Deployment scenarios
      Before you proceed to advanced VM management, review the available scenarios for which you can use the additional instance of VM Manager Tool. The main purpose is to transfer the capacity data from VM managers that are in separated networks, but you can also balance the network traffic, or filter your virtual machines based on their UUIDs.
    - Installing additional VM Manager Tool
      To connect to VM managers that are in separated networks, you must first install additional VM Manager Tool. You can install it on any computer that can connect to the separated networks.
    - Uploading collected data
      After you install additional VM Manager Tool, schedule the regular uploads of collected data. This action is required so that the capacity data that is collected by VM Manager Tool is uploaded to the BigFix server.
    - Adding VM managers
      In advanced VM management, you add VM managers by creating configuration files, where you specify web address, type, and credentials that are required to access a VM manager. Each VM manager uses a separate configuration file.
    - Running VM Manager Tool
      After creating configuration files for your VM managers, you must run the VM Manager Tool to load the configuration, test connections, and check the status of VM managers.
    - Additional configuration
      Additional configuration tasks are intended to give you more control over VM Manager Tool. You can use them to customize the VM Manager Tool, or to enable filtering of virtual machines based on their UUIDs. All of these tasks are optional.
      - VM manager configuration parameters
        In advanced VM management, connection to each VM manager is created based on the information provided in the configuration files. Apart from specifying mandatory parameters, such as web address, virtualization type, user name, and password, you can also use additional ones to disable VM managers, set the number of login attempts, or allow Hyper-V to share credentials with hosts in the same cluster.
      - VM Manager Tool command-line options
        Apart from basic commands that allow you to create connections to VM managers and check their status, you can use additional commands to run or remove VM Manager Tool, encrypt passwords, or collect debug information for troubleshooting purposes.
      - VM Manager Tool settings
        You can configure settings of VM Manager Tool by editing the vmmmainconf.properties file that is stored in the BES Client\LMT\VMMAN\config directory.
      - UUID-based virtual machine filtering
        The purpose of filtering based on universally unique identifier (UUID) is to collect the capacity data only for chosen virtual machines. The remaining ones are omitted and not updated in BigFix Inventory.
        Enabling UUID-based virtual machine filtering
        The uuid_filtering_enabled parameter is set by default to false. You must set it to true before you can select virtual machines to be included in a final report.
        Selecting virtual machines for UUID-based filtering
        You can select virtual machines for whom the capacity data is to be collected by putting their UUIDs in the vmmfilterconf.properties file.
        Obtaining the list of virtual machine UUIDs
        You can use the list of virtual machine UUIDs that are currently connected to the BigFix Inventory server to select those for whom the capacity data is to be collected.
  - Collecting capacity data from virtualization hosts for Xen and KVM
    For Citrix, Xen and KVM, connection to the VM manager does not have to be defined in BigFix Inventory to collect capacity data. The data can be collected directly from virtualization hosts by using the Run Capacity Scan on Virtualization Hosts task.
  - Maintenance tasks
    You can perform additional maintenance and troubleshooting tasks on VM Manager Tool. These tasks are not limited to a specific approach to VM management, but can be applied to any instance of VM Manager Tool.
  - Best practices for configuring VM managers
    Apply the best practices when configuring VM managers to ensure that your infrastructure works efficiently.
- Administering the server
  Perform administering tasks on your server to configure advanced settings, or restart its services.
- Administering the database
  Perform administering tasks on your database to keep it in good condition, protect your data, or configure additional settings.
- Removing inactive computers
  When you decommission a computer in your infrastructure, it continues to report to BigFix Inventory. The data is still collected from this computer, and displayed on the metric reports. To ensure that all infrastructure changes are reflected in BigFix Inventory, you should remove each decommissioned computer from BigFix. If you cannot remove this computer from BigFix for a valid reason, you can use an alternative solution, and decommission the computer in BigFix Inventory.
- Managing data sources
  Computers in an organization can be divided into organizational units, and can be monitored by multiple BigFix infrastructures. Each infrastructure is referred to as a data source. Data from multiple data sources can be imported to one instance of BigFix Inventory.

Obtaining the list of virtual machine UUIDs

You can use the list of virtual machine UUIDs that are currently connected to the BigFix Inventory server to select those for whom the capacity data is to be collected.

About this task

You can find all of the virtual machine UUIDs that are currently connected to the BigFix Inventory server in the ADM.VIRTUAL_VM_UUID table in the TEMADB database. You can extract the complete list of UUIDs and then remove the chosen UUIDs to omit certain virtual machines.

The following procedure explains how to retrieve the list of UUIDs from the DB2 database. If you are using MS SQL, use a method of retrieving information from database tables that is suitable for this database.

Procedure

Log in to the database server as db2inst1 or other user with DBADM rights.
To obtain the list of virtual machines UUIDs, enter the following commands in the system command-line interface:
```
db2 connect to TEMADB
db2 "select distinct uuid from ADM.VIRTUAL_VM_UUID" >uuids.txt
```
Note: TEMADB is the default database name. If you are unsure whether it applies to your database, see: Checking the database name.

Results

The list is now stored in the uuids.txt file.

What to do next

Remove the unnecessary UUIDs from the uuids.txt file and copy the remaining UUIDs to the vmmfilterconf.properties file.