Use this Knowledge Script to monitor hosts and virtual machines that are added, removed, renamed, moved, migrated, or edited in vCenter. This script raises an event when any of the listed actions occurs. In addition, this script can perform a rediscovery when these events occur, which allows the AppManager console to display the most current inventory of hosts and virtual machines in vCenter.
NetIQ Corporation recommends you use the Inventory Knowledge Script instead of this script for inventory monitoring.
NOTE:In rare situations, queries to the ESX or ESXi host might fail with timeouts because the ESX or ESXi host stops responding. You can work around this issue by restarting the management service on the ESX or ESXi host.
vCenter server
By default, this script runs every hour.
Set the following parameters as needed:
|
Parameter |
How to Set It |
|---|---|
|
Event Notification |
Important If you are using this module with AppManager 8.0, the following Raise event... parameters should be unselected. Use the Inventory Knowledge Script if you want to raise events related to inventory changes with AppManager 8.0. |
|
Raise event when virtual machines added? |
Select Yes to raise an event when a virtual machine is added to vCenter. The default is Yes. |
|
Event severity when virtual machines added |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a virtual machine is added to vCenter. The default is 15. |
|
Raise event when virtual machines removed? |
Select Yes to raise an event when a virtual machine is removed from vCenter. The default is Yes. |
|
Event severity when virtual machines removed |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a virtual machine is removed from vCenter. The default is 15. |
|
Raise event when virtual machines renamed? |
Select Yes to raise an event when a virtual machine is renamed. The default is Yes. |
|
Event severity when virtual machines renamed |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a virtual machine is renamed. The default is 15. |
|
Raise event when virtual machines moved? |
Select Yes to raise an event when a virtual machine is moved within vCenter. The default is unselected. |
|
Event severity when virtual machines moved |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a virtual machines is moved within vCenter. The default is 15. |
|
Raise event when virtual machines migrated? |
Select Yes to raise an event when a virtual machine is migrated within vCenter. The default is Yes. |
|
Event severity when virtual machines migrated |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which virtual machines are migrated within vCenter. The default is 15. |
|
Raise event when rediscovery failed? |
Select Yes to raise an event when rediscovery fails. The default is unselected. |
|
Event severity when rediscovery fails |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which rediscovery fails. The default is 5. |
|
Event severity when AppManager failed to get metrics |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which AppManager failed to retrieve metrics from vCenter. The default is 15. |
|
Event severity when AppManager failed to log in |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which AppManager failed to log in to vCenter. The default is 5. |
|
Event severity when VirtualMachineInventory job fails unexpectedly |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the VirtualMachineInventory job fails unexpectedly. The default is 5. |
|
Event severity when writing XML to file successful |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which writing the XML code to a file succeeds. The default is 25. |
|
Data Collection |
|
|
Collect data when virtual machines are added? |
Select Yes to collect data about virtual machines that are added to vCenter. The default is unselected. |
|
Collect data when virtual machines are removed? |
Select Yes to collect data about virtual machines that are removed from vCenter. The default is unselected. |
|
Collect data when virtual machines are renamed? |
Select Yes to collect data about virtual machines that are renamed within vCenter. The default is unselected. |
|
Collect data when virtual machines are moved? |
Select Yes to collect data about virtual machines that are moved within vCenter. The default is unselected. |
|
Collect data when virtual machines are migrated? |
Select Yes to collect data about virtual machines that are migrated in vCenter. The default is unselected. |
|
Rediscovery Options |
Important If you are using this module with AppManager 8.0, select Yes for the following Rediscover parameters. Do not use the discovery parameters in the Inventory Knowledge Script. |
|
Rediscover if virtual machines are added? |
Select Yes to perform rediscovery when a virtual machine is added to vCenter. The default is unselected. |
|
Rediscover if virtual machines are removed? |
Select Yes to perform rediscovery when a virtual machine is removed from vCenter. The default is unselected. |
|
Rediscover if virtual machines are renamed? |
Select Yes to perform rediscovery when a virtual machine is renamed within vCenter. The default is unselected. |
|
Rediscover if virtual machines are moved? |
Select Yes to perform rediscovery when a virtual machine is moved within vCenter. The default is unselected. |
|
Rediscover if virtual machines are migrated? |
Select Yes to perform rediscovery when a virtual machine is migrated in vCenter. The default is unselected. |