Oracle VM Device and Infrastructure Inventory
With FlexNet Manager Suite for Oracle product, FlexNet Manager Suite can generate a license compliance position for the applications installed on virtual machines that are created and managed by Oracle VM products. To generate a complete and accurate license compliance position for some publishers, FlexNet Manager Suite should also collect Oracle VM infrastructure inventory (clusters, pools, hosts, and virtual machines), in addition to the normal hardware and software inventory of virtual machines. To collect Oracle VM inventory, FNMS uses the following different components and processes:
Inventory type | Component used | Process used | Need |
---|---|---|---|
Device inventory |
ndtrack , either installed locally or run remotely from the appropriate
inventory beacon. |
The inventory collection component (
ndtrack ) collects the software and
hardware inventory of all Oracle VM virtual machines within the targeted subnet. For
this, you need to create a discovery and inventory rule with the following settings:
For more information, see the topics under Creating an Action. The inventory device records are visible on the Virtual Devices and Clusters (you can filter by VM type= Oracle VM), and other management views under Inventory. |
The hardware and software inventory used for normal license compliance calculations. |
Oracle VM infrastructure inventory |
inventory beacon | The inventory beacon connects to the Oracle VM Manager to gather VM
hierarchy, and to each Oracle VM Server to gather processor-specific information (such as
CPU affinity). The complete hierarchy is displayed on the Virtual Devices and Clusters page. You need the following settings:
|
The cluster hierarchy information is useful in calculating the license position for applications from some specific software vendors. For example, a publisher may require you to buy an application license for the whole cluster if the application is installed on a virtual machine that is dynamically moved between the hosts of an Oracle VM cluster. Also, the processor-specific properties (such as CPU affinity) are required for calculating the compliance position for Oracle processor licenses. |