vmware
VMware monitoring probe

The Nimsoft VMware monitoring probe has the capability of handling all the common monitoring and data collection tasks on VMware VC/ESX Servers. The probe collects and stores data and information from the monitored system at customizable intervals.

You can easily define alarms to be raised and propagated to the Nimsoft Enterprise Console when the specified thresholds are breached.

Installation notes

  1. Install the package into your local archive.
  2. To ensure a successful installation of the probe package (drag-and-drop), it is required that a java.exe (version not critical) exists in the PATH. If no java runtime is present, install java version 1.4.2, which is required by the probe.
  3. Drop the package from your local archive onto the targeted robot.
  4. Double-click the probe for initial configuration. On first-time probe configuration, initiated by double-clicking the probe in Nimsoft Infrastructure Manager, the installation wizard automatically will be launched. The wizard will prompt you for the path to the java.exe of the version required by the probe.
  5. The first time a configuration is applied with a new Virtual Center, the startup of the probe may take several minutes (depending on number of VMs in the Virtual Center).

    Upgrade Considerations

    Unified Dashboards or Summary Views in UMP VMware probe version 5.01 and above requires you to update to the default out of box VMware List Views provided under Unified Dashboards or Summary Views in UMP. Any existing VMware list views may show blank data in some list views. See the following steps to resolve the VMware dashboard or VMware List Views issues: Apply the UMP Template provided with the VMware probe (or manually update your monitors to reflect the content in the UMP Template), and Use the List Views provided with the latest version of UMP. Alternatively, you can go to the Nimsoft support site and obtain the updated List Views that are compatible with version 3.53 of the probe. Please refer to the forums for information on obtaining this content.

    Migration

    Migration from 4.2x versions of the VMware probe is supported, but with important caveats. Please read carefully if you intend to perform migration.
  6. CPU Extra (% of available) and CPU Guaranteed (% of available) were both removed from the VMware API after ESX 3.5. They have been removed from the probe.
  7. VMwareApiAvailable has been removed as a monitorable metric. A self-monitoring alarm has replaced it.
  8. Reservation (vm) was a duplicate of the monitor CPUReservation. To avoid confusion, reservation has been removed.
  9. Host metrics VMNonTemplateCount, VMNamesActive, and VMNames were all intended for an abandoned feature. They have been removed.
  10. ToolsStatus (deprecated) was deprecated for a release and is now removed.
  11. TemplateState has been removed in favor of having fully distinct type for VMs and templates. Static monitors that were created against entities reclassified from VM to template will need to be recreated.

  12. Attempting to migrate any of these monitors will result in alarms for each during every polling cycle. The original configuration file is automatically backed up in the probe installation directory. Any of CpuStatusInfo, MemoryStatusInfo, or NumericSensorInfo that were manually enabled the old probe will need to be enabled in the new probe by editing the The new probe uses more memory. If you were close to the memory limit on the previous version of the probe, it is very likely you will need to increase the available memory.

    Known issues

    Out of Memory Errors UI Fails to Load Auto/All Monitors Nodes UI Slowly Loads Nodes Within the Inventory Tree VMWARE--Collection Times are Extremely Slow Probe Values Don't Match the vSphere Client For Event Monitors, All Events are Coming Across as Part of a Single Alarm Limited Multibyte Character Support
Revision history
Date Description State Version
12.10.2023

What's New:

  • Certified the vmware probe on the vSphere 8 and vCentre Server 8.
SHA-256 Checksum: 66919002a6f889e60a490d87813626c1ac4539f20aa87da2221a4907c4d090a1
GA 7.22
28.07.2023

What's New:

Added support to clear the acknowledged alarms in the DX UIM environment for vsphere-triggered alarms.

Fixed Defects:

Fixed an issue where the vmware probe was unable to clear the vsphere acknowledged alarms (support case 33356180)

SHA-256 Checksum: c1f12489001bd9f9b2bae145fe727573fbd755ad701a3b4b09ea8af1bd3c0fcd
7.21
15.05.2023

What's New:

Updated the probe as part of addressing known vulnerabilities in DX UIM by upgrading Jettison - Json Stax implementation from 1.5.1 to 1.5.4.

Fixed Defects:

  • The metrics gathered through the QOS Metrics type "QOS_VMWARE_VM_CPU_READY_MS" (CPU Ready (milliseconds) wrongly gather aggregate values (summation of last polling) instead of single real measures.
  • Some vmware probe alarms which are missing the dev_id and are not being replicated to OI via the oi_connector.
  • Not reporting Correct snapshot size on VMFS6.
SHA-256 Checksum: 80c0c96e152c63307316c2b75626e055d24b23008827ac92d385e742a1912807
7.20
06.05.2022

What's New:

  • Addressed Security Vulnerabilities and Third-party product fixes.
SHA-256 Checksum: 53f334f52b4238d342e759911c7a87ffedb061b2971c100af3d44700c88e0bf6
7.18
17.01.2022

What's New:

  • Updated log4j library to 2.17.1 to remediate the vulnerabilities - CVE-2021-44228, CVE-2021-45046, CVE-2021-45105.
SHA-256 Checksum: b2d76d34d8574401642df1621985ce6c86094f3d52cf4e136f4eab00e764034c
7.17
28.06.2021

What's New:

  • Added the ability to filter out Datastores from inventory.
MD5 Checksum: 38d01375a9d3d773cbecc54fb4f04c2d
SHA-1 Checksum: 807b97d0cbe6915d3124cc35adf40ed5e64736db
7.16
09.11.2020

What's New:

  • Certified the probe to monitor VMware vSphere 7.0 environment.
MD5 Checksum: 6cadcec6f38e7e5514c0c05f3abf8268
SHA-1 Checksum: c90d7f0896f7401062388db0004cad3477a5bba3
7.15
18.03.2019

What's New:

  • Added custom properties to the VMware probe inventory elements to support publishing of Inventory Topology and relationships between VMware objects: Resource Pools to Datacenters
  • Added a key in Raw Configuration to define the DNS Name or short name as the device name.
  • Introduced the Auto Filter section for the datastore component in the VMware POBC mode in the new and default factory templates.

Fixed Defects:

  • Fixed an issue where after upgrading to vmware 7.11 the discovery queue was growing continuously. (Support Case 01188309)
  • Fixed an issue where after upgrading to vmware 7.11 the Monitors Included in Templatesection is blank and a large number of failed to collect data for... errors were generated. (Support Case 01184595)
  • Fixed an issue where the vmware probe was unable to monitor a vCenter version 6.7.0. (Support Cases: 01204155, 01239412, 01193497, 01254703)
  • Fixed an issue where the probe was sendingAttempt to add vertex that already exist (Support Cases: 01229015, 01244295, 01292418)

For more information, refer https://docops.ca.com/rest/ca/product/latest/topic?hid=vmware_RN&space=UIMPGA&language=&format=rendered

MD5 Checksum: 7225d5a816a7b59b2b13c2ce31816095
SHA-1 Checksum: c10b9a795d39dc04f1bab4efc4dc177b485f1b62
7.14
25.01.2019

What's New:

Added custom properties to the VMware probe inventory elements to support publishing of Inventory Topology and relationships between VMware objects:

  • Resource Pools to Clusters
  • Resource Pools to Hosts
MD5 Checksum: 6df8f608c91f322b667505b14c6cbcd8
SHA-1 Checksum: 3d9291fc15c69e8e2c1fb9d52c09712e34cc3a73
7.13
21.08.2018

What's New:

  • Added support for vSphere 6.7 suite.
  • Probe supports TLS 1.2/1.1/1.0 for communicating with vCenter. By default, the probe will start communicating with TLS 1.2 and try to connect with the vCenter, stepping down with each test until it finds a connection path it can use. For more information see Installation Considerations.
  • Supports suppression of alarms and QOS metrics publishing for hosts that are on maintenance mode. For more information, see Disable alarms and QoS from Host machines in maintenance mode.
  • The following enhancements are available with vmware v7.11 MCS template package. The template package is compatible only with UIM 9.01 release and above.

For compatibility with CA UIM 8.51, where vmware probe is configured using MCS, we recommend that you upgrade only the vmware probe v7.11, and continue to use the vmware v6.82 MCS templates. For more information see known issue.

      • Enhanced profiles that enable you to configure metrics, baselines, alarm thresholds, alarms - including Time Over Threshold alarms - and custom alarm and close alarm messages, all within a single MCS profile. For more information, see Configuring Alarm Thresholds in MCS.
      • Ability to create group and device override profile with automatic profile filtering. For more information, see vmware MCS Profile Type Configuration.
      • Additional inventory parameters have been added to enhance and improve dynamic and static group creation in USM. For more information see list of additional attributes added.
      • Ability to monitor a VCenter but exclude certain VMs to be discovered by vmware Probe. For more information, see Filter VMs from discovery.

 

  • The following metrics have been deprecated from their applicable monitors in 7.11.1 (Legacy) and 7.11.2 (Enhanced) MCS templates.

    Network Packets Received
    Network Packets Transmitted
    You can view the following metrics instead:

    Network Packet Receive Rate
    Network Packet Transmit Rate

Fixed Defect:

  • Fixed an issue in the UIM-Spectrum integration, where devices were not modeled in the correct hierarchical containers and the resource pools were empty. (Support Case 01104617)
  • Fixed an issue where a new alarm message added to vmware probe but is not available in Template Editor. (Support Case: 00962935) A new callback was added. For more information see workaround.
  • Fixed an issue where vmware probe configuration having issues pulling data from Virtual Center. (Support Case: 01005286) For more information see known issue.
  • Fixed an issue where QOS metrics was missing for VMware Probe (Support Case 00767838). For more information see known issue.
  • Fixed an issue where vmware probe randomly stops collecting QoS (Support Case 00855918).
MD5 Checksum: 2be9f945c9c164db82e30c8bcef4f8d9
SHA-1 Checksum: 22d3b2a4be03e6e597a76dd7bc6972d50cac43a6
7.11
19.07.2018

What's New:

  • Added support for vSphere 6.7 (vmware probe communicates with vcenter using TLS)

Fixed Defects:

  • Fixed an issue in the UIM-Spectrum integration, where devices were not modeled in the correct hierarchical containers and the resource pools were empty. (Support Case 01104617)
  • Fixed an issue where after adding VCenter to the VMware probe some VM's don't get the IP Adress in UIM (Support Case 01098469)
  • Fixed an issue where vmware models in CA Spectrum OneClick hierarchy was not updating. (Support Case 00946887 

Important!
The MCS packages shipped with the vmware 7.11 package are not compatible with CA UIM 8.51, we recommend that you upgrade only the probe and not the MCS templates that are shipped with the 7.11 beta package, unless you have registered for the CA UIM 9.01 EA program.

For Detailed Release Notes-Please refer

https://docops.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=vmware_RN

7.11
14.09.2017

What's New:

  • A DataGridView Default Error Dialog appeared after navigating to a VM host within a cluster and selecting Memory. Support case number 00754934, 00786235, 00789071
  • A problem where queue files could back up and not process caused users to have to manually delete the queue files. Support case number 00738661
  • The probe published partial graphs when monitors or events changed on a monitored system resulted in excessive graph publishing. Support case number 00799774
  • Alarm-only monitors failed to report QoS definitions.
md5sum: 784da1f9f5eb4a595664dc510ba59486
sha1sum: 9118f816546b181b92a1553e12bb2cbc19c6ceeb
6.87
11.07.2017

Fixed Defects:

  • Fixed an issue where the vmware probe would not respond to the Infrastructure Management thick client when certain probe configurations were enabled.
  • Fixed an issue where the vmware probe did not publish QoS for some metrics when configured using MCS (Support Case 00783809).
  • Fixed an issue where the vmware probe sometimes crashed when configured using MCS.
  • Fixed an issue where probe data collection is interrupted when VCenter presents an IPv6 address with a scope ID.
md5sum: ffce2d4f6e36204e47a0a1bcfa809d25
sha1sum: 680770c321003d5e2972d2f28ecf058a9c423a79
6.83
16.02.2017 md5: dd8e37a7722a9e6350132f75c21613ee

Fixed Defect:


  • Fixed an issue in which the probe generated false alarms related to disk latency. Support case number 00645192
6.82
18.05.2016 What's New:
- Added reporting of all secondary MAC and IP addresses for a VM that has VMware Tools installed.
- Added documentation describing a work-around for a known issue. When you reconfigure a static monitor, the static monitor cache does not clear unless you deactivate and activate the probe. Support case 00157751
- Added documentation describing a work-around for a VMware known issue that causes the probe log file to display a performance metric collection error message.
- Added support for vCenter 6.0u2.

Fixed Defects:
- Fixed a document defect in the Software Requirements section, which stated incorrectly that Microsoft .NET framework must be installed on the same system as the probe. Install Microsoft .NET only if you are using Infrastructure Manager. Install Microsoft .NET only on the system that runs the Infrastructure Manager GUI.
- Fixed a defect in which the probe self-monitoring alarms did not clear when the cause of the alarm was resolved or when the probe was restarted.
- Fixed a defect in which template configuration changes made by the user in the Admin Console UI were not persisted by the probe. (DE55070) Support case 00355985
- Fixed a defect in which the probe returned null data for a VM hostname and host CPU usage.
6.72
08.10.2015 ? Fixed an issue in which, if a message pool identification name included an underscore, the high and low threshold status display order was reversed.
? Fixed an issue in which, if a metric was disabled in Infrastructure Manager, it was not disabled in Admin Console.
? Fixed an issue in which the probe was inconsistent in which name it used to identify the source for a QoS message.
? Fixed an issue in which, for certain alarms, the device ID incorrectly displayed as the default connector.
? Fixed an issue in which, for users with CA UIM v8.0-8.1, the Unified Dashboards for VMware were missing QoS that were collected by the probe.
? Fixed an issue in which the probe required a cold restart in order to configure static monitors correctly.
? Fixed an issue in which the probe did not send device ID in alerts through the CA UIM Connector for CA SOI.
? Fixed an issue in which the template editor in Admin Console offered a superfluous option to apply a log level filter.
? Fixed an issue in which the probe stopped generating QoS messages after running continuously for one day.
? Fixed an issue in which a MissingTargetException occurred.
? Fixed an issue in which, when running on a Windows 2008 server with a socket leak, the probe displayed the following error message: "Java.net.SocketException: No buffer space available."
? Fixed an issue in which, when the user was using Japanese characters, the QoS source and target were garbled when they were stored in the database.

md5sum: 8e546aa76ea529464c37d9a83f4f9517
shar1sum: 575c8d1e2fbe04004174c7337094a96c7545cd3b
6.60
12.08.2015 Bulk Configuration is now supported

md5sum: b17f564eaeb927e5fa3ff5ca48f2bc8c
sha1sum: 806783da51478a555c7385fdeadfb9bab5057544
6.53
02.07.2015

- Added support to configure and apply all monitoring, manually or with templates, in Admin Console.
- Added new monitors to the datastore resource
- Added the ability to monitor a datastore disk
- Added the ability to monitor a datastore under a host
- Added the ability to monitor a datastore under a vm

6.51
31.03.2015 Added Admin Console GUI element: the Detached Configuration folder in the left-hand navigation tree for the probe displays resources that have been deleted in the VMware vSphere and which still have configuration in the probe.

Added monitoring of Distributed Virtual Port Groups and Switch.
Added support for monitoring the same VCenter with multiple credentials.
Added support for using non-English characters in the following fields:
template name, template description, message name, message error text, message OK text, and alarm thresholds.

Enabled the probe to indicate to baseline_engine (or other probes performing a similar computational function) to compute baselines, publish QoS data to the message bus, and publish alarms when configured alarm threshold criteria is met.
Improved discovery time and HEAP memory usage.

Fixed Defects:
Fixed an issue in which, when using two user profiles with different permissions on the same ESXi host, incorrect credentials were set on both resources and both resources monitored the same set of objects from the vCenter. Salesforce Case 00152061
Fixed an issue in which, when monitoring numeric sensors on ESXi hosts, the profile did not work and the tooltip displayed an "unable to connect" error message.
Fixed an issue in which, when monitoring QoS metric for host service availability, the service description was missing from the CI naming.
Fixed an issue in which internationlization (translation from English) caused the QoS source/target text to be garbled when it was stored in the database.


md5sum: f54275bfb3de5260566273406b865e0a
sha1sum: b29a4cfccd9482ea78f85530c5c71f70886d4e5c
6.41
23.12.2014 Corrected an issue with value updates for HOST_SERVICE metrics.
Improved the loading time of All Monitors and Auto Monitors content in GUI..
Improved monitor processing logic to reduce polling intervals..
Performance metrics are now visible in the GUI whether or not monitoring is enabled..
Reduced memory footprint by modifying internal representation of objects..
Reduced polling interval time by creating thread calls to collect vCenter performance metrics.
.
For Detailed Release Notes-Please refer
https://wiki.ca.com/display/UIMPGA/VMware+Monitoring+%28vmware%29+Release+Notes
6.30
01.10.2014

-Fixed: QoS Messages for Datastores now show correct target
Md5sum: d8f6b37ed5b3a76cb3ef1f6d0b1d4280
sha1sum: 72f8ad8249aee83c5c6135491b2675538d69aaf9

6.21
30.09.2014 Fixed:
USM VMware Appviews now show data under correct system.
Event forwarding metrics now forward all events..
CI Names and targets are now correct for any data center affiliated entities..
Monitors that failed to collect data will now show the correct warning icon in Infrastructure Manager GUI..
Added support for integration with CA Capacity Management; VMWare probe now collects and publishes attributes that Capacity Management uses to perform correlation tracking and analysis:.
Added metrics:.

Datastore Node - Usage Cluster.
Computer Resource Node - CPUusage.
Computer Resource Node - Memoryusage.
Host Node - distributedCpuFairness.
Host Node - distributedMemoryFairness.
VM Node - GuestMemoryUsage.
VM Node - HostCPUUsage.
VM Node - Physical Cores Used.
VM Node - StorageProvisioned.
VM Node - StorageUsage.
Deprecated metrics:.
Host Cluster Services Node - distributedCpuFairness.
Host Cluster Services Node - distributedMemoryFairness.
Removed deprecated metrics (for 6.1 and 6.2 releases) from documentation metrics tables..
For Detailed Release Notes-Please refer
http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/vmware/ReleaseNotes/index.htm
6.20
30.03.2014 Added requirements for VMware VirtualCenter 5.5 and VMware ESX/ESXi 5.5
Described appearance of VMs in USM.
Support for IPv6 environments.
Restored VMwareApiAvailable metric
For Detailed Release Notes-Please refer
http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/vmware/ReleaseNotes/index.htm
6.11
19.12.2013 Fixed: Monitoring alarms on multiple vCenters could cause a collection failure 6.01
13.12.2013 Added Support for VMware 5.5 and made performance enhancements 6.00
23.10.2013 Probe fails to detect new VMs on 5.1 update 1 Provisioning VMs trigger false duplicate UUID alarms Monitors of 'average of last n' do not display values in 'All Monitors' 5.06
27.06.2013 Reintroduce source_is_ip support Use a new method of event collection that works for all ESXi hosts. Fix API response time calculation Improve displayed error message when communication with the controller fails. 5.03
02.05.2013 Mouse-over tool-tips on resource nodes to provide additional context Fixed creation of devices visible to USM 5.02
29.03.2013 Rewritten backend and GUI Alarm forwarding support Storage Pod and Virtual App monitoring Cluster VMotion monitoring 5.01
01.10.2012 What's New:
Added support for the following authentication types in Windows platform:
1. NTLM
2. DIGEST
3. GSSNEGOTIATE
4. ANYSAFE

Fixed Defects:
1. Defaults were overwritten in message section in the cfx file. Salesforce Case: 00164613
2. Variables specified in the Source Override field in the Advanced tab did not expand to their actual values. Salesforce Case: 00165815

For Detailed Release Notes-Please refer
http://wiki.ca.com/rest/ca/product/latest/topic?hid=url_response_RN&space=UIMPGA&language=&format=rendered

Note: Salesforce case(s) may not be viewable to all

md5sum: 1527b3b3a2576c19afa21ad2e0eca497
sha1sum: 164785880c3eaa5540c9519e63c503180cdf5d54
4.22
29.06.2012 Probe Help now accesses online Help Resource Site
Performance metric auto-monitors are no longer created for entities missing the performance metric
Memory and CPU performance metrics added to Resource Pools
Corrections around the creation of Remote Device details for SOC niscache content
Host Virtual Switch ports and available ports metrics added to Hosts entity
Added (optional) support for including DataStore containing folders in the QoS Target
Active Template highlighting during drag-n-drop fixed
Template copy operation is now supported
4.20
28.03.2012 Corrected Resource Pool QoS target strings for uniqueness Corrected Auto-Monitor wildcard instance QoS target strings Corrected QoS target string for Auto to Static Monitor conversions 4.11
14.03.2012 Polling interval alarms are now cleared when the collection cycle take less time than the configured interval.
Target string corrected for DS, Cluster, and Network auto-monitors created from static monitors.
Target string corrected to contain topology path for Resource Pools and Networks.
Corrected the robot dependencies setting in the VMware probe package
Restored missing VM Memory usage metric in the inventory tree.
Corrected reported VM Snapshot size.
Added support for tracking VMs by instanceUUIDs for env. with duplicate UUIDs (e.g., Lab Manager & vCloud)
Updated the UMP Metrics template to match with the latest Dashboard content
4.10
01.12.2011 Augment QoS source to optionally include origin for multi-tenant setups. Fixed missing scenarios around converting auto monitor to static monitors. Any static monitor now takes precedence over auto monitors. 4.01
18.10.2011 Added support for SOC management of Hosts, and VMs with VMTools installed.
Corrected target naming for Datastores contained within Folders.
Fixed enabling of static monitors for the Top Level API monitors.
VMCount and VMCountActive monitors now report zero for vSphere targets with zero VMs.
Resource Level Monitors properly tag auto-configured monitors as auto-monitors.
4.00
30.06.2011 Fixing failures around calculation process for missing Network Metrics.
Adjusting QOS entries in support OOB Dashboards.
3.53
22.06.2011 Fixed millisecond to percentage calculations for CPU perf metrics.
3.51
27.05.2011
  • Status monitor supported for Network Switches.<\li>
  • Summary level monitors are supported for Clusters.<\li>
  • Top level disk latency is now reported as an average.<\li>
  • Booleans are converted to integers to enable QOS submittal.<\li>
  • Correcting CPU Performance metrics to report in terms of per CPU Average.<\li>
  • Fixed auto-monitor behavior around wildcarded monitors (e.g., Services, CPUs, CpuStatusInfo, Disks, etc).<\li>
  • StorageStatusInfo, CpuStatusInfo, MemoryStatusInfo and NumericSensorInfo monitors now support wildcarding in auto-monitors and templates.<\li>
  • Probe allows for ESX Hosts vnic property to not be set<\li>
  • Rolled revision for GA Release.<\li>
  • 3.50
    29.03.2011 Revision roll as part of maintenance release.
    Additional Message types and QOS entries added.
    3.40
    31.12.2010 Fixed the enabling of Datastore Monitors from Config UI's List View.
    Enabled the use of Templates with Datastores with both Auto-Monitors and Monitors.
    Enabled the drag-and-drop of Templates to Datastores directly.
    Implemented the functioning of VMware API Auto-Monitors at the Resouce level.
    Corrected error recovery / handling around VMware session timeouts
    Fixed the Config UI's browse hierarchy to properly reflect the state of performance based Auto-Monitors.
    Disabled the NumericSensorInfo reporting by default.
    Fixed the bugs related to Memory percent based metrics.
    Added metrics for reporting VM Template state and tallying the count of Non-Template VMs.
    3.27
    18.12.2010 Corrected behavior around disabled monitors.
    3.26
    03.11.2010 Corrected behavior around sending clear alarms for monitors.
    Fixed target for datastore auto monitors.
    Fixed checkbox for host monitors.
    3.25
    29.10.2010 Fixed the handle error when some hosts have a null datastore
    3.24
    01.10.2010 Fixed metrics that did not properly display in the GUI when a host name is not resolvable.
    3.23
    26.09.2010 Fixed the auto-configuration matching defect that caused auto monitors to match non-running VMs
    Fixed the session timeout defect that caused null data when long intervals were used
    Note: It is recommneded to retry the queryAvailablePerfMetrics, since it sometimes fails.
    3.22
    13.09.2010 Allowed IP address as source for the auto monitors.
    Fixed the defect in string threshold editing.
    3.21
    17.08.2010 Added VMware API availability and response time metrics
    Added SnapshotCount and SnapshotSize metrics for VMs
    Added default auto configurations for new resources
    Improved Performance
    3.20
    01.04.2010 Added Scale improvements.
    Probe is now NIS2-enabled.
    3.10
    21.01.2010 Removed limitation on the number of resources.
    Added login-only check for resources without monitors.
    Use of language-independent exception handling.
    Fixed NullPointerException when the array of objects returned by the server (by one of the getArrayOf methods) is null.
    3.02
    30.09.2009 Fix problems with VMWARE subject detection and reconnection after connection to server is lost. 3.01
    14.07.2009 Fixed CPU key in default template. 2.73
    23.06.2009 Added support for additional measurement points for vSphere 4.
    Added support $ip tag in messages.
    Added support for automatic upgrade to vSphere 4 (if possible) using Ctrl-U.
    Fixed CPU key in default template.
    3.00
    29.04.2009 Fixed internal database truncation error.
    Verifed support for VI4.
    Note:Nimsoft has tested and verified intial support for VI4, but more comprehnsive testing will be performed during the relase provess to verify that all features of VI4 are supported.
    2.72
    19.03.2009 Corrected error when connecting to VC / ESX.
    Added support for CPU, Disk and Network instance performance monitoring.
    Added the possibility to average a monitor point over the 2-5 last measurements.
    Optimized start-up time for configurations with many active resources.
    Added sortable column of alarm severities.
    Fixed deployment of templates in clustered environments.
    Fixed potential GUI issues when probe is about to restart.
    2.71
    05.12.2008 Added support for resource alarms to queue.
    Fixed connect timeout.
    2.55
    23.10.2008 Removed possible performance collection error after a monitored VM is removed. 2.53
    21.10.2008 Fixed situation were alarms were being sent, when only QoS was active.
    Fixed hang situation in GUI, when a resource was unavailable.
    2.52
    02.10.2008 Added support for two alarm levels.
    Added support for auto configuration.
    2.50
    31.07.2008 Added the possibility to route alarms to logmon queue.
    Added the possibility to add the DNS name (if available) to an alarm ($dns tag).
    Added possibility to define Datastore, GuestDisk and Service checkpoints in Templates.
    Added possibility to delete all existing checkpoints when a template is deployed.
    Added "Add to template..." menu option.
    Added "Deploying templates" status window.
    Java 1.6 is supported.
    2.20
    05.06.2008 A number of new measurement points are added.
    Improved GUI performance.
    Automatic refresh of GUI may be turned off (use F5 for manual refresh).
    A number of icons are changed.
    The VM icons reflect the run-state and configuration-state of the VM.
    A template may be dropped at any level (supports VM, Host and Resource Pool checkpoints).
    Removed "Create Template" / "Apply Template" menu options on VM's.
    Added support for Events in templates.
    Removed list of checkpoints in template creation process (only drag'n'drop is supported).
    Java 1.5 is supported.
    Technical upgrade.
    2.10
    26.10.2007 Upgrade libraries. 2.08
    28.09.2007 Fixed login
    Changed handling of monitor id's
    2.07
    28.08.2007 Fixed templates 2.05
    04.06.2007 Added support for Infrastructure 3 (VirtualCenter 2.x and ESX 3.x).
    Added template support.
    Changed GUI icons.
    2.00
    30.11.2006 Improved certificate handling. 1.15
    27.10.2006 Initial version 1.14
    Requirements
    Platform: Please refer to the Platform Support Matrix located in the Download section of http://support.nimsoft.com
    Software: Java version 1.6.x.
    VMware VirtualCenter 4.1 update 1 or newer, 5.0 ,5.1&5.5br>VMware ESX/ESXi 4.1 update 1 or newer, 5.0,5.1&5.5
    Nimsoft Monitor Server5.1.1orlater
    Microsoft .NET Framework 3.5 on the hardware running the Infrastructure Manager
    Hardware: None