> KB 1752

Release notes for Veeam MP Integration Management Pack update

KB ID: 1752
Products: Veeam Management Pack for System Center
Version: 6.0.0.1421
Published:
Created: 2013-04-29
Last Modified: 2013-07-30

Challenge:

Maintenance mode synchronization in System Center 2012 Operations Manager SP1
 
Importing the updated Veeam Integration MP will resolve the known issue related to maintenance mode synchronization in System Center 2012 Operations Manager SP1.
When a vSphere host enters the maintenance mode in vCenter, the Veeam VMware: vSphere Host Maintenance Mode Tracker monitor should automatically respond by placing the host and its components into the OpsMgr Maintenance Mode. By design, the maintenance mode for the VM-Container object on this host — including all contained VMs, and Ops Mgr Agents (if any) — is not set.
 
However, in Ops Mgr 2012 SP1, VMs and any Ops Mgr agents that are contained within VMs will also enter maintenance mode when the host does. Furthermore, maintenance mode for such agents will not be stopped when the Veeam MP monitor stops maintenance mode for the host. Such Ops Mgr agents will only exit maintenance mode when the duration expires (by default, 24 hours).
 
Applying the Integration MP patch will resolve this issue.
 
VMGUEST to OpsMgr Agent relationship discovery

The script response VmToAgent.ps1 in the discovery VMGUEST to Ops Mgr Agent Relationship Discovery which creates relationships between VM objects and Ops Mgr Agent objects may time out in large environments. 
 
Applying the Integration MP patch will resolve this issue. The updated MP script has been optimized for better performance.

HostNetStats metrics not collected for hosts with only virtual distributed switches
 
Veeam MP fails to collect HostNetStats metrics for vSphere hosts that have only distributed virtual switches configured, and no standard virtual switches. Additional information can be found here.

Applying the Collector patch will resolve this issue. 
 
Incorrect scope passed to Alert History report
 
When you drill down from the Alert Statistics report (run in the Troublemakers mode) to the Alert History report, incorrect scope is passed to the Alert History report. 
Applying the Report Library MP patch will resolve this issue.
 
Frequently changing properties of resource pools/vApps can cause discovery thrashing
 
In Veeam MP 6.0, resource pool and vApp properties are collected with the frequency that is defined in the TopologyUpdateBuffer Collector setting (once per 4 collection intervals by default). In certain vSphere environments, it was found that resource pool/vApp property values (e.g., resource allocation setting) are unstable and changing (by a minimum value) very frequently. This will cause constant topology rediscovery and can result in discovery thrashing.
 
Applying the Discovery MP patch will resolve this issue. With the patch applied, the Veeam MP will update resource pool/vApp properties as prescribed by the PropertyUpdateBuffer setting (once per day by default). This will reduce any topology rediscoveries for these properties to once per day.
 
VM Disk Space Analysis monitor not working properly with non-English locale
 
If the System Locale on a Collector server does not use dot (.) as a decimal separator, the Veeam VMware: Virtual Machine Disk Space Analysis monitor may fail. The problem occurs because the monitor diagnostic script does not correctly process VMGuest-disk\ freeMB values which have a non-dot decimal separator.
 
Applying the Monitoring MP patch will resolve this issue. After you apply the patch, VMGuest-disk\ freeMB metrics will be converted to properly formatted numeric values even when the Collector system uses a decimal separator other than dot (.).
 
Failure to collect hardware data due to null LUN or LUN path
 
In some situations, the Collector fails to gather hardware data from a vSphere host if the host's LUNs become inaccessible. The problem manifests itself if the LUN or LUN path property is not present. The following error can be seen in SCOM:

VP510 No metrics obtained for ESX hosts , failed to process performance or configuration data for host
 
Applying the Collector patch will resolve this issue. The patch adds checking for invalid LUN and LUN path values, which eliminates the problem.
 
Different decimal separators for OpsMgr and HealthService system accounts
 
If different decimal separators are used for system accounts of OpsMgr Management Server and Ops Mgr Agent (where Collector runs), the Datastore Cluster Free Space Analysis monitor does not process collected metrics properly. The problem occurs due an Ops Mgr issue with converting the values to the requested type.
 
Applying the Monitoring MP patch eliminates the locale-specific formatting problem for the affected monitor.
 
Scan Datastore task fails with timeout expired error
 
If the ‘Scan Datastore for Unknown Files’ task takes longer than 5 minutes to complete, it fails with an error: ‘Timeout expired Error Code: -2130771868 (Unknown error (0x80ff0064))’. The problem remains even if the task timeout is increased manually with an override. 
 
Applying the Monitoring MP patch will resolve this issue: the patch removes the hardcoded timeout of 300 seconds.  If the timeout error occurs when running the task, you can override the default timeout with a value greater than 300 seconds.

Datastore Free Space Analysis Monitor triggers false alerts with zero metric values

The Veeam VMware: Datastore Free Space Analysis monitor provides incorrect information on datastore space usage. The monitor triggers an alert stating that a datastore “has breached the free space threshold. Datastore is currently 0% used, with 0 GB space remaining.”
 
If different decimal separators are used for system accounts of OpsMgr Management Server and OpsMgr Agent (where Collector runs), the Datastore Cluster Free Space Analysis monitor does not process collected metrics properly. The problem occurs due an Ops Mgr issue with converting the values to the requested type.
 
Applying the Monitoring MP patch eliminates the locale-specific formatting problem for the affected monitor.
 
 

Cause:

This is a list of issues resolved in the Veeam MP for VMware patch 1


Solution:

The issues are resolved by importing the updated Veeam MP Patch 1.

More Information:

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support.html

How helpful is this article:
Rating: 4 / 5 (2 votes cast)
‹‹ Back to knowledge base search

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!