IBM PVU Scanning

FlexNet Manager Suite 2019 R1 (On-Premises Edition)

These controls allow you to use FlexNet inventory for sub-capacity licensing calculations, potentially in place of ILMT (subject to overall IBM approval).

Note: This IBM PVU scanning section of the Inventory Settings page is available only when you have licensed the FlexNet Manager for Datacenters product.
Before adjusting settings in this section, it is important that you understand the implications included in Sub-Capacity Licensing Using IBM PVU:

To configure higher frequency processing for IBM PVU licenses:

  1. Select the Enable frequent hardware scanning for IBM PVU license calculations check box.
    A number of additional controls appear when this check box is selected (provided that the prerequisites described in Sub-Capacity Licensing Using IBM PVU have been satisfied).
    Tip: In contrast, if you clear this check box, you must either use full capacity calculations for your IBM PVU licenses, or rely on the points calculations collected from ILMT, TAD4D, SUA, or IBM Big Fix. Selecting the check box is a requirement for IBM acceptance of sub-capacity calculations based on FlexNet inventory.
    Saving this page with this check box enabled also has the following effects:
    • Modifies the appearance of the Compliance tab on all IBM PVU licenses so that they can display the peak consumption of sub-capacity points (and when this occurred) for each IBM region, together with the full consumption for any devices not eligible for sub-capacity calculations (see Compliance Tab)
    • Enables the mapping of enterprise group locations to the three mandatory IBM regions, allowing you to assign ownership of devices to appropriate locations so that their consumption points are directed to the appropriate IBM region (see Locations)
    • Causes display of an IBM region column in appropriate searches and listings, such as the Ownership tab on device properties, the Locations page, and the Consumption tab on license properties
    • Adds the All devices consuming IBM PVU points target to the list of targets available for IBM PVU-related hardware scans, visible in the Discovery & Inventory > Discovery and Inventory Rules page
    • Enables remote scans by appropriate inventory beacons of all known VMware vCenter and Oracle VM Manager servers
    • Enables frequent hardware scanning of all target inventory devices where the FlexNet inventory agent is locally installed, as required by IBM (this setting is distributed within policy to the installed FlexNet inventory agents through the inventory beacons, which in turn receive it through the BIBMPVUEnableScanning=true setting in the BeaconSettings.xml file)
    • Enables the recalculation (retrospectively covering the data retention period, including the current reporting period for reports to IBM) of the peak points consumption for each mandatory IBM region (this happens as part of each full license reconciliation process, by default scheduled overnight)
    • Prevents IBM PVU licenses incorporating any points imported from ILMT, where this remains available as an auxiliary inventory source.
      Tip: When imports are still available from ILMT, and high-frequency scanning is enabled, there is a report provided that compares the current sub-capacity results imported from ILMT with those calculated by FlexNet Manager Suite.
  2. In the Perform extra inventory scanning every time-interval drop-down list, choose one of the available intervals (between 30 minutes and 4 hours).
    The default value (30 minutes) is mandatory if you wish to use FlexNet inventory for sub-capacity license calculations in place of an IBM tool such as ILMT (which also captures snapshots for its licensing history every 30 minutes). If you choose an option other than the 30 minutes default, a warning appears, allowing you to confirm that your choice is well-informed and intentional.

    Be aware that this time interval applies not only to the inventory gathering from the host server, but also to the upload of any inventory changes, and import to the inventory database. Recalculation of peak consumption per region, which takes into account any hardware or VM changes that have been imported since the last calculation, occurs as part of the full compliance calculations, by default scheduled overnight.

  3. For the check box Perform remote scans against all known VMware vCenter and Oracle VM Manager servers, accept the default setting, or clear the check box for exceptional circumstances.
    These servers, identified automatically from the list of discovered devices, are automatically inventoried by the appropriate inventory beacon remotely accessing their management APIs to track the movement of virtual machines.
    Note: This functionality requires that the virtual host and the inventory beacon can connect across an IPv4 network. (FlexNet Manager Suite does not currently support any form of remote execution using IPv6 address families, and therefore a virtual host in an IPv6 zone remains invisible to this functionality.)
    The effects of the check box are as follows:
    • When this check box is set, an additional hidden rule is enabled to run on the same frequency that you selected for the extra inventory scanning in the previous step. The rule uses an automated target that is updated daily to contain all servers (in IPv4 networks) where either VMware vCenter or Oracle VM Manager has been discovered. While the rule is active (that is, while this check box is set), those servers are scanned for high-level hardware information, including which virtual machines are running on which host server, using direct inventory gathering by the appropriate inventory beacon.
      Note: While VMs on VMware vCenter are candidates for sub-capacity license consumption, VMs on Oracle VM Manager are always calculated at full consumption. This is because currently IBM accepts Oracle VM servers only on SPARC and UltraSPARC architectures for sub-capacity consumption (and not on x86 platforms), and FlexNet Manager Suite supports Oracle VM servers only on x86 platforms.
    • When this check box is cleared, high-frequency scans of servers running VMware vCenter or Oracle VM Manager do not occur. In general, you should not clear this check box in production, and the option is available only for exceptional circumstances (for example, while you are waiting for approval from your Oracle team to run the inventory scans). In production, you might clear the check box if your enterprise uses neither of these virtualization products; or if you know that there are no IBM PVU licenses applying on any of the virtual machines managed by these servers. Otherwise, clearing the check box risks puts you at risk of breaching IBM's conditions, which normally require tracking the movement of virtual machines where the relevant software may be operating.
  4. If this is your first time configuring these settings, click Save.
    This refreshes the content of the drop-down list you will use next, including display of the hidden target group.
    Tip: The built-in target All devices consuming IBM PVU points is suppressed until you Save this page with extra inventory scanning enabled.
  5. In the drop-down list to Enable PVU-related hardware scans by installed inventory agents within the following targets, choose the first of your existing targets for increased scanning.
    Normally this is the built-in target for All devices consuming IBM PVU points (available only after you have saved the set check box Enable frequent hardware scanning for IBM PVU license calculations). This target, automatically updated after each full inventory import (by default, daily), lists all computers with installed software linked to IBM PVU licenses. These computers must have the FlexNet inventory agent installed. Independently of this setting, you may either:
    • Manage the installation and configuration of the FlexNet inventory agent using your preferred deployment technology (this third-party deployment is mandatory in networks using the IPv6 address family); or
    • Create a separate rule for discovery and adoption, for which you define the target to match the machines where you want the FlexNet inventory agent installed (this applies only in networks using the IPv4 address family). In this case, the inventory beacon checks for a prior installation on each target machine, and if it is not present, automatically installs FlexNet inventory agent in line with your targeting.
    Tip: When the selected target is present in the closed list, it is included in data saved when you click Save.
  6. If you want to include another target that you have defined, click the + button to the right of the list.
    A new line appears below your previous choice, and you can repeat the selection process for other targets you have defined (as discussed above).
  7. When you are satisfied with your settings, click Save (in the bottom right of the page).

Your system is now configured for the more frequent inventory checks required for sub-capacity licensing calculations using the FlexNet inventory agent.

If you have multiple inventory sources, ensure that data from other sources cannot overwrite data from the high-frequency inventory you have just enabled. To do this:
  1. Navigate to the system menu ( in the top right corner) and choose Data Inputs.
  2. Select the Inventory Data tab.
  3. Check that the FlexNet Manager Suite — Flexera source currently displays Primary (on the right end), and if not, click Make primary.

You may also wish to check the configuration on your IBM PVU licenses around rights on virtual machines and hosts, set in the Use Rights & Rules tab of each license's properties (see Rights on Virtual Machines and Hosts). These are already correctly configured if you have set up these licenses using the Product Use Rights Library enabled by the FlexNet Manager for Datacenters license term.