AppManager for VMware vSphere provides a set of Knowledge Scripts designed to give you a comprehensive view of how vSphere performs in your environment. This module monitors resources through vCenter to ensure that the most basic components of your vSphere environment function correctly.
This release improves usability and resolves previous issues. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the AppManager forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.
The documentation for this product is available on the NetIQ website in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click Click to comment on this content to the right of each section of any page in the HTML version of the documentation posted at the AppManager Modules page. To download this product, see the AppManager Module Upgrades & Trials website.
This release of AppManager for VMware vSphere provides the following enhancement:
Support of monitoring of vCenter through VMware vCenter Server Appliance (vCSA): With this hotfix release, AppManager for VMware vSphere now supports monitoring of vCenter through VMware vCenter Server Appliance (vCSA).
Support for VMware vSphere version 6.7: This release supports VMware vSphere version 6.7.
To get the updates provided in this release, you must install the module to the AppManager repository (QDB) and on the agent computer, and then propagate changes to any running jobs for the Knowledge Scripts that were updated in this release. AppManager 7.x does not automatically update renamed or copied Knowledge Scripts. For more information, see the “Upgrading Knowledge Script Jobs” section in the management guide.
This release of AppManager for VMware vSphere replaces all Previous Releases.
For the latest information about supported software versions and the availability of module updates, visit the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.
AppManager for VMware vSphere has the following system requirements:
|
Software/Hardware |
Version |
|---|---|
|
NetIQ AppManager installed on the AppManager repository (QDB) computers, on the vCenter servers you want to monitor (AppManager agents), and on all console computer |
AppManager 8.0 Service Pack 2 (8.0.2), 8.0.3, 8.2, 9.1, 9.2, 9.5, or later, or AppManager 7.0.4. The following hotfixes are required for AppManager 8.0 Service Pack 2 or later:
The following hotfixes are required for AppManager 7.0.4:
The following hotfixes might be required for AppManager 7.0.4, depending on your environment:
Important You must install all hotfixes before installing this release of the module. For more information about hotfixes, see the AppManager Suite Hotfixes page, or contact NetIQ Technical Support. |
|
Microsoft Windows operating system on the agent or proxy agent computer |
One of the following:
|
|
AppManager for Microsoft Windows module installed on repository, agent, and console computers |
8.0.80.0 or later. For more information, see the AppManager Module Upgrades & Trials page. |
|
Microsoft .NET Framework on the agent or proxy agent computer |
4.5 or later |
|
VMware vSphere and vCenter |
VMware vSphere 6.7, 6.5, 6.0, 5.5, 5.1, or 5.0 |
|
vCenter Server Appliance (vCSA) |
6.7 (proxy discovery support) |
|
Microsoft SQL Server Native Client 11.0 (for TLS 1.2 support) |
11.3.6538.0 or later NOTE:The SQL Server Native client can be installed from this Microsoft download link. |
NOTE:If you want TLS 1.2 support and are running AppManager 9.1 or 9.2, then you are required to perform some additional steps. To know about the steps, see the article.
AppManager for VMware vSphere includes a managed object, qVirtualCenterMOa4.dll, and Knowledge Scripts to discover and monitor AppManager for VMware vSphere resources. The download package includes this release notes, a management guide, Help for Knowledge Scripts, and several files that are used during installation:
AM70-VMware-8.1.76.0.msi, the module installer.
AM70-VMware-8.1.76.0.ini, a configuration file used with the AppManager setup program.
AM70-VMware-8.1.76.0.xml, a configuration file used for deploying the module with Control Center. This is the file you check into the Control Center Web Depot.
AM70-VMware-8.1.76.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.
ckVC.exe, the pre-installation check used with the AppManager setup program.
DefaultRule_VMware.xml, a configuration file used for deploying the module with Control Center.
When you download the module, these files are copied by default to the local folder on the download computer. Consider copying these files to the \windows_installation\setup\Setup Files folder on the same distribution computer on which you saved your main AppManager software and documentation. By doing so, you maintain all AppManager software in one location that is easily accessible when you want to add more repositories, management servers, or agents.
IMPORTANT:If you are upgrading from the previous release, version 8.0, you need to perform additional steps to make sure the Knowledge Scripts get updated correctly for version 8.1 of the module. For more information, see the “Upgrading from Version 8.1 of the Module” section in the management guide.
Run the module installer to install the module components in the following locations:
On the AppManager agent or proxy computers you want to monitor (agents) to install the agent components
On all console computers to install the Help and console extensions
Run the module installer only once on each of these computers.
You must also install the Knowledge Scripts. You can install these components into local or remote QDBs.
Install this module to all QDBs, and for Control Center environments, but install the module to the primary QDB last. When installing to the each QDB, select the option to install Knowledge Scripts, and then specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name. Select the option to install Analysis Center reports, and then specify the SQL Server name of the server hosting the Analysis Center Configuration Database.
IMPORTANT:This release provides SQL stored procedures. To ensure module functionality, run the module installer for each QDB attached to Control Center.
Install Knowledge Scripts only once per QDB. The module installer now installs Knowledge Scripts for each module directly into the QDB instead of to the \AppManager\qdb\kp folder as in previous releases.
For more information about installing this module, see the AppManager for VMware vSphere Management Guide, included in the download package.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
With AppManager 8.2 only, Operator Console does not update the TreeView if you move or rename an object until you close and then re-open Operator Console: If you move or rename an object, the discovery process in Operator Console does not update with the change until after you close and then open AppManager again, or if you expand and collapse the Operator Console TreeView. This issue only happens with AppManager 8.2. (ENG332495)
Unable to move an object under a parent object that already has a child object with the same name as the moved object. AppManager does not support the moving of an object under a parent object if the parent object already has a child object under it with the same name as the object you are trying to move. (ENG323403)
Unable to manually check out the VirtualCenter_VmToolsStatus Knowledge Script: If you installed the AppManager repository (QDB) hotfix 7010373 after you installed the 8.0 version of this module, manual checkout of the VirtualCenter_VmToolsStatus script fails with the following message “Failed to fetch job request”. To work around this issue, reinstall the 8.0 version of the AppManager for VMware vSphere module. (ENG319344)
A deployment task is not created for uninstallation of the VMWare module using remote deployment: This issue occurs only on AppManager 8.0. To work around this issue, manually uninstall the module. (ENG315507)
Sessions that you created in vCenter before a restart of the NetIQmc service will not be terminated: After you restart the NetIQmc service, the module cannot terminate any existing sessions. As a result, the sessions will time out from vCenter using their own internal timeout settings. (DOC309707)
Some Knowledge Scripts do not raise events for virtual machines that have the same name or a comma in their names: If you have virtual machines with the same name in different data-centers, or if you have virtual machines with commas in their names, some scripts will not generate events for those objects. The events only appear in the Master view for the module, not in the Virtual Center view. (ENG296530)
Existing VirtualCenter_ResourcePool* jobs not upgraded with this release: This release does not upgrade existing VirtualCenter_ResourcePool* jobs. As a result, you will need to start new jobs for any of the three ResourcePool* Knowledge Scripts that were running before you installed this release. (ENG314728)
This module does not support Web Console or other consoles that do not use .VBS extension files: Because the AppManager Web Console does not use Visual Basic Scripting (.VBS) extension files, you cannot run Knowledge Scripts that use .VBS extension files from the Web Console. (DOC315627)
The following scripts use VBS and are not supported when you run them from the Web Console:
Discovery_VirtualCenter
VirtualCenter_Alarms
VirtualCenter_Configuration
VirtualCenter_Events
VirtualCenter_Inventory
VirtualCenter_Tasks
VirtualCenter_VirtualMachineInventory
VirtualCenter_VmDiskUsage
VMware Knowledge Scripts do not recognize resource objects that have the pipe character (“|”) in their names: This module does not support the use of a pipe character (“|”) in the name of a virtual machine, host, cluster, datastore, resource pool, or other resource object. If a pipe character is present in an object name, such as Test|machine, the VMware Knowledge Scripts will not be able to monitor that object, nor will it be able to monitor a collection of VMs containing that resource object. (ENG304467, ENG304767)
Running the Alarms Knowledge Script might cause the NetIQms.exe service to fail: The NetIQms.exe service fails when running the Alarms script if you changed the Persistent IOC key from 1 to 0, which disables the PIOC files. To address this issue, change the Persistent IOC key to 1 and restart the AppManager agent services. (ENG294399)
Tasks that do not identify the inventory entity are displayed as unassociated TreeView objects when you run the Tasks Knowledge Script: In some instances, a new vCenter task does not include data about the inventory entity associated with the task, such as the VM or the datastore. When this occurs, AppManager associates the task with the root vCenter object in the TreeView. To ensure that you receive events about vCenter tasks that do not contain inventory information, select vCenter for the Select vCenter entity type parameter in the Tasks Knowledge Script. (ENG299205)
Occasionally, some data may not be stored in the AppManager repository (QDB): For more information, see NetIQ Knowledge Base article NETIQKB72388. (ENG285900)
Character differences between TreeView Pane and VI Client: You can name specific entities in vCenter such as virtual machines, resource pools, clusters, folders, and datacenters. vCenter stores the backslash (\), forward slash (/), and percent sign (%) internally as “%2f”, “%5c”, and “%25” respectively. Discovery shows these characters as they are stored internally, so they appear differently in the AppManager TreeView and the VI Client. (ENG264668)
Incorrect data points for CPU wait time: Data points for CPU wait time may represent values close to 100%. CPU wait time values should be very low, much less than 100%. NetIQ Corporation is currently researching a solution with VMware. (ENG249422)
The VirtualCenter_ClusterCPUUsage Knowledge Script does not return valid values for VMware vSphere 4.0: When you run the VirtualCenter_ClusterCPUUsage Knowledge Script, the values returned do not match the values displayed in the Advanced Performance Charts in the vSphere client. (ENG267133)
Virtual machines may not be discovered: Virtual machines will not be discovered if the Discovery_VirtualCenter job is running while the virtual machines are being deployed from a template. (ENG261351)
This release of AppManager for VMware vSphere includes enhancements added in previous releases.
This release of AppManager for VMware vSphere provides the following enhancement:
Support for Transport Layer Security 1.2 (TLS): This release of AppManager for VMware vSphere provides support for TLS 1.2.
This release of AppManager for VMware vSphere provided the following enhancements:
Option to suppress alarms about host event from VC Alarms Knowledge Script while host being in maintenance mode: You can now decide whether or not to receive alarms about host event from VC Alarms KS while host goes into maintenance mode by selecting a checkbox added in the UI. In case you want the alarm event, select the checkbox, or else deselect it.(ENG346817)
This release of AppManager for VMware vSphere resolved the following issues:
VMware 8.0.284 discovery fails: This release resolves an issue in which the discovery job fails to authenticate vCenter server by enabling TLS 1.2. (ENG346857)
This release of AppManager for VMware vSphere provides the following enhancement:
VirtualCenter_HostDiskTotalLatency monitors Physical Device Latency, Kernel Disk Latency, and Queue Latency: You can now use the VirtualCenter_HostDiskTotalLatency Knowledge Script to monitor and collect data for Physical Device Latency, Kernel Disk Latency, and Queue Latency.
This release of AppManager for VMware vSphere resolves the following issues:
Discovery_VirtualCenter fails to access a file from a specified location if the file path contains spaces: The Discovery_VirtualCenter Knowledge Script job was throwing an error while trying to access or read the files that contained the list of hosts or virtual machines to exclude from discovering. The locations or paths of the files were specified in the Full path to file containing list of hosts to exclude parameter and the Full path to file containing list of virtual machines to exclude parameter. The error occurred when the path of the file contained spaces. In this release, the issue is resolved. (ENG338079)
VirtualCenter_DatastoreUsage does not display datastores names in events and data points: The VirtualCenter_DatastoreUsage Knowledge Script failed to display the datastores names for which the events were raised or the data points were collected. In this release, the issue is resolved and datastores names appear in the corresponding event messages and data points. (ENG341404)
VirtualCenter_ServiceHealthCheck crashes the Management Server: The AKPID string in the VirtualCenter_ServiceHealthCheck Knowledge Script was causing the Management Server to crash. In this release, the issue is resolved and the AKPID string is modified to AKP_NULL. (ENG342511)
Running Discovery_VirtualCenter stops all the existing jobs and raises a job failure event: When you ran the Discovery_VirtualCenter Knowledge Script on the virtual center objects that were already being monitored, the Knowledge Script stopped any existing jobs on the virtual center objects and deleted all the virtual center objects from TreeView. The Knowledge Script re-discovered all the virtual center objects, instead of delta discovery. In this release, the issue is resolved. (ENG336552 and ENG336929)
This release provided the following enhancement:
Support for VMware vSphere version 6.5. This release supports vSphere version 6.5.
This release provided the following enhancements:
Support for VMware vSphere version 5.5 and 6.0: This release supports vSphere version 5.5 and 6.0.
Support for Windows Server 2012: This release supports Windows Server 2012 on agent or proxy agent computers.
This release resolved the following issues:
VirtualCenter Knowledge Scripts keep trying to reconnect without stopping: This release addresses an issue in which the VirtualCenter scripts continued trying to reconnect when they encountered incorrect information in the Security Manager entry. With this release, the VirtualCenter scripts stop trying to reconnect in this situation, and will generate an error event message about the incorrect Security Manager information. For more information, see section 2.7.2 in the AppManager for VMware vSphere Management Guide. (ENG329937, ENG330961)
VirtualCenter_Alarms Knowledge Script raises an event message stating that an index was outside the bounds of the array: This release resolves an issue in which the list of display names monitored by the VirtualCenter_Alarms script was too large and was truncated, and the script could not monitor all of the entities provided. With this release, an update to the VirtualCenter_Alarms script traces if the list of display names are truncated and ensures that the script functions properly. (ENG330155)
Discovery_VirtualCenter Knowledge Script completes successfully, but some VirtualCenter scripts fail after discovery completes: This release resolves an issue in which the Discovery_VirtualCenter script completed successfully, but some VirtualCenter Knowledge Scripts failed with the following error: Cannot complete login due to an incorrect user name or password. With this release, an update to the VirtualCenter_VirtualMachineInventory ensures that the correct global variables are populated and verified when retrieving information from Security Manager. (ENG330515)
This release provided the following enhancements:
Support for discovery in a large-scale environment: With AppManager 8.x or later, the Discovery_VirtualCenter Knowledge Script uses delta discovery during the initial discovery process, which enables it to correctly discover all vSphere servers, virtual machines, and hosts, regardless of the size of your environment. For more information about using this module with large-scale environments, see the “Scalability Considerations” section of the management guide.
The VirtualCenter_Inventory Knowledge Script automatically updates the object tree hierarchy: The VirtualCenter_Inventory script now uses delta discovery functionality to automatically update the AppManager TreeView whenever you change the inventory status of your virtual machines or hosts, such as when you add or move a virtual machine or host.
The VirtualCenter_Alarms Knowledge Script includes new event parameters for cleared and acknowledged alarms: You can now use this script to raise an event when monitored vCenter alarms are acknowledged and cleared. You can also raise events when currently triggered alarms are acknowledged and cleared.
The new VirtualCenter_VmSnapshotUsage Knowledge Script monitors virtual machine snapshots: This script raises an event when the number of snapshots, the size of a snapshot, the age of a snapshot, or the age of a reverted snapshot exceeds the thresholds you set. This script generates data streams for the number of snapshots, snapshot size, snapshot age, and the age of reverted snapshot.
Support for VMware vSphere 5.1: This release now supports VMware vSphere version 5.1.
This release resolved the following issues:
Monitoring policy jobs restart whenever the object tree hierarchy updates: This release resolves an issue in which monitoring policy jobs for Knowledge Scripts that monitored virtual machine objects were deleted and then recreated with a new ID whenever you discovered new virtual machines, or when changes occurred to the AppManager TreeView. With this release, the monitoring policy jobs for monitoring virtual machines do not get deleted and recreated every time the TreeView changes.
Datastore and Host Knowledge Scripts can now monitor many more objects in monitoring policy jobs: With this release, improvements to the VirtualCenter_DatastoreUsage and VirtualCenter_Host* Knowledge Scripts enable the scripts to monitor a much larger number of objects in monitoring policy jobs. (ENG298282, ENG317050)
Analysis Center reports replace the VirtualCenter_RPT_* Knowledge Scripts: This module uses reports generated by NetIQ Analysis Center instead of the obsolete VirtualCenter_RPT_* scripts. For more information about using Analysis Center reports, see the “Reporting with Analysis Center” section of the management guide. (DOC317884)
This release resolved the following issues:
VirtualCenter_HostCPUUsage Knowledge Script gathers CPU used data that is twice the actual value: This release resolves an issue in which VMware vSphere 5 and ESXi 5 calculated the CPU used values differently than previous releases, which caused the VirtualCenter_HostCPUUsage script to gather values that were twice the value that vCenter reported for CPU used as a whole. VMware vSphere 5 and ESXi 5 now provide a summation value for the Host as a whole. With this release, updates to the VirtualCenter_HostCPUUsage script enable the module to accurately display data from VMware vSphere 5 and ESXi 5. (ENG319854)
VirtualCenter_VMToolsStatus Knowledge Script displays an incorrect VMware Tools status: This release resolves an issue in which the VirtualCenter_VMToolsStatus script incorrectly reported that the status of the VMware Tools on a virtual machine was either Not running or Not supported, when the actual status of VMware Tools was Not current and not supported. With this release, an update to the VirtualCenter_VMToolsStatus script enables it to properly report the Not running status as well as the Not current and not supported status. (ENG319857, ENG319170)
This release resolved the following issue:
VirtualCenter_VmOperations Knowledge Script reports incorrect data: This release resolves an issue in which the VirtualCenter_VmOperations script created data based on absolute counter values instead of relative values. For example, if the counter value was 1 in one iteration and 3 the next, the script reported a data value of 3 instead of 2. With this release, the VirtualCenter_VmOperations script creates data with correct values. (ENG318500)
This release resolved the following issue:
VirtualCenter Knowledge Scripts fail when the Job ID is too large: This release resolves an issue in version 7.9.253.0 of this module in which VirtualCenter Knowledge Scripts failed when the assigned value for the Job ID was 32000 or greater. This issue affected any Knowledge Script that connected to the vCenter Web service. Scripts not affected by this issue included all scripts that use SNMP (the VirtualCenter_HW* scripts), VirtualCenter_ServiceHealthCheck, VirtualCenter_VirtualCenterCPUUsage, and VirtualCenter_VirtualCenterMemoryUsage. With this release, an update to the way in which the managed object handles the Job ID values prevents VirtualCenter scripts from failing in this situation. (ENG317676)
This release provided the following enhancements:
Enhanced vCenter session management: All jobs running against vCenter 4.1 and higher share a single session per vCenter server, and the module no longer creates new sessions without terminating old sessions.
Improved vApp support for VirtualCenter_ResourcePool* Knowledge Scripts: Virtual appliances (vApps) no longer appear as resource pool objects in the AppManager TreeView, but they now have their own unique object type. You can also select vApps as resource objects with the VirtualCenter_Alarms, VirtualCenter_Events, and VirtualCenter_Tasks scripts.
Updates to the Discovery_VirtualCenter Knowledge Script: With this release, the Discovery_VirtualCenter Knowledge Script allows you to create exclusion lists for virtual machines and hosts to limit the number of virtual machines or hosts listed in the AppManager TreeView. You can also raise an event if excluded objects are not found by the discovery process. The Discovery script also now lets you discover and monitor virtual appliances, or vApps.
Support for concurrent jobs for the VirtualCenter_Alarms, VirtualCenter_Events, and VirtualCenter_Tasks Knowledge Scripts: In the previous release, you were limited to a single active instance of each job type for VirtualCenter_Alarms, VirtualCenter_Events, or VirtualCenter_Tasks. With this release, you can run multiple jobs for each script at the same time, enabling you to monitor and take different actions on groups of monitored entities. For example, you can simultaneously run two Alarms jobs, three Events jobs, and two Task jobs. (DOC310135)
The VirtualCenter_ServiceHealthCheck monitors additional vCenter Server services: The VirtualCenter_ServiceHealthCheck script can now monitor the new services available in VMware vSphere 5.0. (DOC313421)
New event options for VirtualCenter_VmToolsStatus Knowledge Script: The VirtualCenter_VmToolsStatus script can now monitor the new running states and version states now supported with VMware vSphere 4.0 and 5.0. (ENG313440)
This release included the following set of new Knowledge Scripts:
VirtualCenter_HostUptime: Monitors the time elapsed since the last system startup for a host. This script raises an event when a host is rebooted, and it collects data for host uptime.
VirtualCenter_Inventory: Monitors if hosts and VMs are added or removed from a vCenter, tracks configuration changes to hosts and VMs in a vCenter, and monitors VMs that migrate to different hosts or move to different datastores, resource pools, or vApps. If an inventory change occurs, you have the option of setting the script to run a discovery. This Knowledge Script is supported on vCenter 4.0 or later.
VirtualCenter_VmOperations: Monitors the number of virtual machine operations that are occurring across clusters and datacenters. You can also use this script to raise events when the number of Storage vMotions or vMotions exceed a specified threshold. This script generates data streams for Storage vMotion operations and vMotion operations. The VirtualCenter_VmOperations Knowledge Script is supported on vCenter 4.0 or later.
VirtualCenter_VmUptime: Monitors virtual machine uptime in days. Virtual machine uptime is the time elapsed since the last system startup. This script raises an event when a virtual machine is rebooted, and it collects data for virtual machine uptime. The VmUptime Knowledge Script is supported on vCenter 5.0 or later.
The VirtualCenter_ResourcePoolMemUsage Knowledge Script includes a new data stream: This release adds a Memory Consumed data stream to the VirtualCenter_ResourcePoolMemUsage script. (ENG248610)
This release resolved the following issues:
The VirtualCenter_DatastoreUsage Knowledge Script fails with a type mismatch error: This release resolves an issue in which the VirtualCenter_DatastoreUsage script failed with the error message VMware managed object is not installed. Error Number: 13 Description: Type mismatch. With this release, an update to the code of the VirtualCenter_DatastoreUsage script prevents the type mismatch. (ENG310727)
VirtualCenter_Tasks and VirtualCenter_Events Knowledge Scripts run briefly, then fail with invalid procedure call errors: This release resolves an issue in which jobs for the VirtualCenter_Events and VirtualCenter_Tasks scripts failed after running successfully for up to 12 hours with an Invalid procedure call or argument error message. You could not restart the jobs unless you also restarted the NetIQ AppManager Client Resource Monitor (netiqmc.exe) agent service. With this release, an update to the code for these two scripts as well as the code for the managed object prevents these scripts from failing in this situation. (ENG311111)
This release provided the following enhancement:
Support for VMware vSphere version 5.0: This release now supports vSphere version 5.
This release resolved the following issue:
Discovery_VirtualCenter failed to re-discover objects it had previously discovered: This release resolves an issue in which Discovery_VirtualCenter failed to re-discover objects that it had previously discovered. As a result the jobs for that object disappeared, because no object was associated with those jobs, but events were created for those jobs along with a Failed to fetch job request error message. With this release, an update to the Discovery_VirtualCenter script prevents the error from occurring, and running a second discovery process works as expected. (ENG293815)
This release included the following new Knowledge Scripts:
VirtualCenter_Alarms: raises AppManager events when monitored vCenter alarms get triggered. You can filter the alarms by alarm type and alarm name. You can also use this script to monitor changes in the ESX hardware.
VirtualCenter_Events: raises AppManager events when monitored vCenter events occur. You can filter the events by vCenter entity type, user name, and event description.
VirtualCenter_Tasks: raises AppManager events when monitored vCenter tasks fail. You can filter the tasks by vCenter entity type, task name, and task user name.
This release also provides the following enhancements:
Improved querying of performance counters: With this release, several improvements in the way in which performance counters are queried allow Knowledge Script jobs to run faster.
A new format for querying output allows results to be returned faster. The results, in .CSV format, do not include metadata that is not related to the results.
At each job iteration, a Knowledge Script queries only the changes (the delta) to an entity's configuration information that have occurred since the previous iteration.
These improvements affect the following VirtualCenter Knowledge Scripts:
ClusterCPUUsage
ClusterMemUsage
HostCPUUsage
HostDiskIO
HostDiskTotalLatency
HostMemoryUsage
ResourcePoolCPUUsage
ResourcePoolMemUsage
VmDiskIO
VmMemoryUsage
VmNetworkIO
Monitoring of additional vCenter Server services: The ServiceHealthCheck Knowledge Script now monitors the following vCenter Server services: (ENG293846)
VMware Capacity Planner service
VMware License Server service
VMware Mount service
Update Manager service
VMware vCenter Collector service
VMware vCenter Converter service
VMware Orchestrator Configuration service
VMware vCenter Server Heartbeat service
VMwareVCMSDS service
VMware VirtualCenter Management Webservices service
Improved event messages related to the disk latency of a virtual machine: When the HostDiskTotalLatency Knowledge Script encounters a high level of disk latency in a virtual machine (VM), it now lists all VMs running on that host as well as the VMs connected to that datastore in the event detail message. (ENG295385, DOC300371)
This release resolved the following issue:
Discovery_VirtualCenter gives incomplete results when datacenters have duplicate names: This release resolves an issue where the Discovery Knowledge Script job returns an incomplete list of virtual machines in environments with multiple datacenters in vCenter with the same name under different parent folders. With this release, the folder structures for Hosts & Clusters and Datastores are updated to account for duplicate datacenter names. (ENG293770)
As a result of the change provided in this hotfix, if your datacenters are in folders in vCenter, those folders will appear in the AppManager tree view.
This release resolved the following issues:
Discovery fails on Windows for double-byte languages: This release resolves an issue in which the Discovery_VirtualCenter Knowledge Script job fails on versions of Microsoft Windows Server 2003 for double-byte languages such as Japanese and Chinese. The Discovery XML file is encoded for UTF-8 standards, but the double-byte Windows environments require XML to be encoded for ANSI standards. With this release, a code change allows the Discovery XML file to be encoded for UTF-8 or ANSI standards, as appropriate. (ENG282225)
Configuration job fails: This release resolves an issue in which the VirtualCenter_Configuration Knowledge Script job fails and raises an event with the following message: Failed to generate Configuration files. The failure is caused by the presence of duplicate Datacenter names in the results returned by a query to the vCenter Server. The Configuration script expects all Datacenter names to be unique. When duplicate names are detected, the job throws an exception to indicate that the names already exist. With this release, a code change allows the Configuration job to create configuration files, without exception, when the query results contain duplicate Datacenter names, host names, or virtual machine names. (ENG286764)
This release provided the following enhancements:
Improved monitoring capabilities:
New CPU metrics for the following Virtual Center Knowledge Scripts:
ClusterCPUusage
HostCPUusage
VmCPUUsage
ResourcePoolCPUusage
New disk metrics for the following Virtual Center Knowledge Scripts:
VmDiskIO
HostDiskIO
New memory metrics for the following Virtual Center Knowledge Scripts:
ClusterMemoryUsage
HostMemoryUsage
ResourcePoolMemUsage
VmMemoryUsage
New Virtual Center Knowledge Scripts:
HostDiskTotalLatency
VmDiskUsage
VmToolsStatus Knowledge Script updated to collect data for Analysis Center reports
New Recommended Knowledge Script Groups:
ClusterMonitor
HostMonitor
ResourcePoolMonitor
VirtualCenterMonitor
VirtualMachineMonitor
Improved reporting capabilities:
New Analysis Center reports:
Logical Disk Space Usage by VM
Reports about Datastore usage:
Average Datastore Free Space by Datastore Over Time
Average Datastore Utilization by Datastore Over Time
Bottom N Datastores by Datastore Free Space
Bottom N Datastores by Datastore Utilization
Top N Datastores by Datastore Free Space
Top N Datastores by Datastore Utilization
Reports about tools:
Tools Status
Tools Status by Status
New metrics added and the following updates made to Analysis Center reports:
Alphanumeric ordering of Analysis Center Reports
CPU Ready and Memory Balloon metrics in Performance Overview reports
“Top N” and “Bottom N” reports allow selection of all relevant memory metrics via the context menu
Analysis Center Dashboards, which are views that show multiple reports as follows:
Datastore Top-Bottom Datastore Usage Dashboard:
Top N Datastores by Datastore Free Space
Top N Datastores by Datastore Utilization
Datastore Usage Dashboard:
Average Datastore Free Space by Datastore Over Time
Average Datastore Utilization by Datastore Over Time
Host Performance Dashboard:
Average Host CPU Utilization by Host Over Time
Average Host Disk IO by Host Over Time
Average Host Memory Utilization by Host Over Time
Average Network IO by Host Over Time
Host Total Overview Dashboard:
Host Datastore Disk Operation Performance Overview
Host Datastore Free Space Overview
Host Datastore Latency Performance Overview
Host Datastore Utilization Overview
Host Performance Overview
Host Storage Performance Dashboard:
Average Datastore Latency by Host Over Time
Average Disk Operation by Host Over Time
Average Host Disk IO by Host Over Time
VM Performance Dashboard:
Average VM CPU Utilization by VM Over Time
Average VM Disk IO by VM Over Time
Average VM Logical Disk Usage by VM Over Time
Average VM Memory Utilization by VM Over Time
Average VM Network IO by VM Over Time
More efficient use of vCenter sessions:
VMware reuses connections from the AppManager agent with vCenter for subsequent iterations of a Knowledge Script instead of creating a new session each time you run the job. Therefore, sessions remain open in the Sessions dialog box of the vSphere client and at times appear to be idle. You will see one active session for each active job instead of many sessions starting and ending with each iteration of a job.
This release resolved the following issues:
Discovery_VMware fails in Chinese environment: Before you install this release, the Discovery_VMware Knowledge Script job fails. The Discovery XML file cannot be inserted into the repository. After you install this release, a code change allows the XML file to be written in UTF-8 format, rather than ANSI format, so that Chinese characters can be translated. (ENG282225)
VirtualCenter_HostConnected job raises events for hosts in maintenance mode: Before you install this release, the VirtualCenter_HostConnected Knowledge Script jobs raises events for host computers that are in maintenance mode. After you install this release, a code change prevents the HostConnected script from raising events for hosts in maintenance mode. (ENG282626)
Discovery job times out when number of discovered objects is large: Before you install this release, the Discovery_VirtualCenter Knowledge Script job can time out while attempting to discover large virtual environments. You can filter the number of discovered objects by using the “Detailed object settings” parameters in the Discovery_VirtualCenter Knowledge Script. After you install this release, two new parameters in the Discovery_VirtualCenter Knowledge Script allow you to further filter the number of discovered objects by selectively discovering Datastores and virtual machines. For more information, see the Help for the Discovery_VirtualCenter Knowledge Script. (ENG282798)
The AppManager for VMware vSphere product and all updates and modifications thereto (“Software”) is distributed with certain third-party software and open source software (as may be defined in the license agreement provided with the Software).
The following third-party and open source software are included with the Software and are licensed for distribution according to the terms described in this document and any use thereof must be in accordance with such terms, solely in conjunction with your internal use of the Software, and - unless explicitly contradicted below - consistent with the terms and conditions set forth in the applicable license agreement for the software. No further licenses are granted.
Apache License: Distributions of log4j, log4net, log4cxx Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
Definitions: “License” shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. “Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. “Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. “You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this License. “Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. “Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. “Work” shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). “Derivative Works” shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. “Contribution” shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, “submitted” means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as “Not a Contribution” “Contributor” shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
Grant of Copyright License: Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sub license, and distribute the Work and such Derivative Works in Source or Object form.
Grant of Patent License: Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a “NOTICE” text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
VMware License: VMware(r) End User License Agreement VMware, Inc. (“VMware”) provides the vSphere Web Services Software Development Kit (vSphere WS SDK) (the “Software”) to you subject to the following terms and conditions. If you disagree with any of the following terms, then do not use the Software.
The Software contains a variety of materials, interface definitions, documentation, sample utility applications and sample code regarding programming interfaces to one or more VMware products as referenced in such materials (“VMware Products”). This Software is intended to be used to execute supplied commands and utility applications and to create scripts that interact with the VMware Products.
Use Rights: Subject to the restrictions below, you may download and make a reasonable number of copies of the Software contents for your use solely for the purpose of creating software that communicates with VMware Products (“Developer Software”). For vSphere WS SDK, some code may be designated as “distributable code” and/or “modifiable code” at http://www.vmware.com/go/vwssdk-redistribution-info. Any merged portion of any “distributable code” is subject to this Agreement. Additionally, you may modify or create derivative works of all or portions of the “modifiable code.” You are permitted to re-distribute the “distributable code” and the modified or derivative works of the “modifiable code” only as part of your Developer Software for non-commercial or commercial use. Open source software components provided with the Software are licensed to you under the terms of the applicable license agreements included with such open source software components. The open source software licenses can be found in the open_source_licenses.txt file, other materials accompanying the Software, the documentation or corresponding source files available at http://www.vmware.com/download/vi/open_source.html.
Restrictions: You agree that you will not (1) use the Software to create, design or develop anything other than Developer Software; (2) make any more copies of the Software than are reasonably necessary for the authorized use and backup and archival purposes; (3) modify, create derivative works of, reverse engineer, reverse compile, or disassemble the Software, except as expressly permitted in Section 2; (4) distribute, sell, lease, rent, lend, or sublicense any part of the Software to any third party except as expressly permitted in Section 2 or; (5) use the Software to (a) create, design or develop software or service to circumvent, enable, modify or provide access, permissions or rights which would violate the technical restrictions of VMware Products, any additional licensing terms provided by VMware via product documentation, email notification and/or policy change on VMware website, and/or the terms of the End User License Agreements of VMware products; (b) disable, remove, over-ride or modify the display of any VMware product End User License Agreements to the end customers; and (c) upload or otherwise transmit any material containing software viruses or other computer code, files or programs designed to interrupt, destroy, or limit the functionality of any software or hardware.The restrictions in this Section 3 shall not apply if and to the extent they contradict mandatory local law (including, but not limited to, law implementing the EC Software Directive) provided that, before you exercise any rights that you believe to be entitled to based on mandatory law, you provide VMware with 30 days prior written notice at SDK_Legal@vmware.com and provide all reasonably requested information to allow VMware to assess your claim and, at VMware's sole discretion, to provide alternatives that reduce any adverse impact on VMware's intellectual property or other rights.
VMware retains ownership of the Software, including without limitation all copyrights and other intellectual property rights therein. You may not remove, delete or modify any of VMware copyright statements in the Software.
You may not use VMware's name, trademarks or service marks in your Developer Software's names or in a way that suggests your Developer Software is certified or endorsed by VMware. Your use of VMware product names and trademarks shall comply with the Branding Guidelines posted at www.vmware.com.
You will not receive any VMware support or subscription services for the vSphere WS SDK or any other services from VMware in connection with the vSphere WS SDK. If you have purchased support and/or subscription services for a VMware product, such support and/or subscription services shall not apply to the vSphere WS SDK or your use of the vSphere WS SDK.
Term, Termination and Changes: This Agreement shall continue as long as you are in compliance with the terms specified herein or until otherwise terminated. You or VMware each may terminate this Agreement for any reason at any time. You agree, upon termination, to destroy all copies of the Software within your possession or control. The Limitations of Warranties, Liability and Indemnification sections set out in this Agreement shall survive any termination or expiration of this Agreement.
Limitations of Warranties and Liability: THE SOFTWARE IS PROVIDED "AS IS" WITHOUT ANY WARRANTIES OF ANY KIND. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, VMWARE DISCLAIMS ANY IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL VMWARE BE LIABLE FOR ANY LOST PROFITS OR BUSINESS OPPORTUNITIES, LOSS OF USE, BUSINESS INTERRUPTION, LOSS OF DATA, OR ANY OTHER INDIRECT, SPECIAL, INCIDENTAL, OR CONSE- QUENTIAL DAMAGES ARISING OUT OF THE SOFTWARE OR YOUR USE OF THE SOFTWARE, UNDER ANY THEORY OF LIABILITY, WHETHER BASED IN CONTRACT, TORT, NEGLIGENCE, PRODUCT LIABILITY, OR OTHERWISE. BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE PRECEDING LIMITATION MAY NOT APPLY TO YOU. VMWARE'S LIABILITY ARISING OUT OF THE SOFTWARE PROVIDED HEREUNDER WILL NOT, IN ANY EVENT, EXCEED US$5.00.THE FOREGOING LIMITATIONS SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, REGARDLESS OF WHETHER VMWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AND REGARDLESS OF WHETHER ANY REMEDY FAILS OF ITS ESSENTIAL PURPOSE.
Indemnification: You agree to defend, indemnify and hold harmless VMware, and any of its directors, officers, employees, affiliates or agents, from and against any and all claims, losses, damages, liabilities and other expenses (including reasonable attorneys' fees), arising from your modification or derivative works of the “modifiable code”, distribution or use of your Developer Software or breach of this Agreement.
These terms are governed by the laws of the State of California and the United States of America without regard to conflict of laws principles. You may not assign any part of this Agreement without the prior written consent of VMware. Any attempted assignment without consent shall be void. These terms constitute the entire agreement between you and VMware with respect to the Software, and supersede all prior written or oral communications, understandings and agreements. Any waiver of these terms must be in writing to be effective. If any provision of these terms is found to be invalid or unenforceable, the remaining terms will continue to be valid and enforceable to the fullest extent permitted by law.
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information website.
For general corporate and product information, see the NetIQ Corporate website.
For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.
For information about NetIQ legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government restricted rights, patent policy, and FIPS compliance, see https://www.netiq.com/company/legal/.
Copyright (C) 2019 NetIQ Corporation. All rights reserved.