VMWare probe - Knowledge Base Index
Document ID :
Last Modified Date :
Show Technical Document Details
CA Unified Infrastructure Management
CA Unified Infrastructure Management:Release:8.51
CA Unified Infrastructure Management:Release:8.47.1
UNIFIED INFRASTRUCTURE MGMT:CAUIM
UIM - VMWARE:UIMVMW
Index of vmware probe knowledge base articles written by Technical Support
KB000033993 | VMWARE PROBE ERROR: UNEXPECTED APPLICATION ERROR OCCURRED. KEY HOST NOT FOUND
I can't configure the vmware probe. When I try I get a popup error: "Unexpected application error occurred. Key host not found"
KB000036532 | VMWARE PROBE FAILS TO COLLECT DATA FOR SOME MONITORS AND GENERATES AN ERROR WITH 'FAILED TO CONFIGURE MONITOR'
The vmware probe fails to collect data only for certain monitors and vmware.log has errors with 'message==Failed to configure monitor'.
KB000007314 | UNABLE TO COLLECT ALL METRICS FROM GUEST VMS USING VMWARE PROBE - UNABLE TO ALARM ON THOSE SAME METRICS
I have Guest disk capacity/free/free capacity included in my template with data turned on and alarms set. I am not able to see any of this data in USM.
KB000004655 | ALERTS FROM THE VMWARE PROBE COME FROM THE VCENTER AND NOT THE HOST
as of version 6.72 the vmware probe aggregates self-monitoring alarms based on monitor type. This can be overridden with the enable_self_monitoring_alarm_aggregation key.
KB000033588 | VMWARE PROBE - BEST PRACTICES FOR BETTER PERFORMANCE
List of vmware best practices for better overall performance. Symptoms of bad performance could be slow load times for the GUI/checkpoints or data values, empty GUI window showing no checkpoints/data, etc.
KB000007686 | VMWARE PROBE USING A LOT OF HARD DISK SPACE
More specifically the vmware/discovery folder is backing up
KB000014896 | UNABLE TO CHANGE QOS NAME FOR VMWARE PROBE IN ADMIN CONSOLE
QoS Name can be edited in Infrastructure Manager, but can't be edited in Admin Console
KB000038045 | VMWARE VIRTUAL CENTER/ESX SERVER MAPPING TO DUAL ORIGINS
CA UIM discovery server is discovered with dual origin?
KB000004742 | AUTO MONITORS ARE NOT SHOWING IN VMWARE PROBE, ON EXPANDING A V-CENTER
On expanding a resource in vmware probe, its auto monitors are not visible.
KB000005057 | VMWARE PROBE DATA COLLECTION ERROR AFTER STARTUP
The vmware probe connects to vCenter but then throws a data collection error after starting up
KB000006440 | NEW TEMPLATE DISAPPEARS IN VMWARE PROBE
Because of a bug in controller (still present as of robot 7.90) a newly created template for vmware probe may disappear after the template is modified and probe restarted
KB000007702 | VMWARE PROBE DOES NOT DISPLAY VCENTER IN UMP
Devices discovered by vmware probe attached to secondary hub are not displayed in UMP
KB000004946 | DEVICES CREATED BY THE VMWARE PROBE ARE NOT REMOVED BY RUNNING THE REMOVE_MASTER_DEVICES_BY_CSKEYS PROBE CALLBACK.
How to remove vmware devices that are unable to be removed by the remove_master_devices_by_cskeys probe callback.
KB000007403 | VMWARE PROBE STOPS MONITORING INTERMITTENTLY
Intermittent issues in monitoring vcenter using VMware probe. Probe might stop monitoring and it works after restarting the probe.
KB000004795 | VMWARE PROBE TEMPLATES NOT APPLYING
Running UIM 8.47, VMware probe on similar, dedicated server (2012 R2 Datacenter) and can not longer save a custom template, and no templates appear to be applied when viewing hosts from the AC configure GUI.
KB000010375 | PARTIAL GRAPH PUBLISHING FOR VMWARE PROBE
This TEC provides information on the partial graph publishing feature for vmware probe
KB000013678 | DOES VMWARE PROBE SUPPORT VMWARE VSAN STORAGE MONITORING?
This document includes the qos metrics for VSAN monitoring.
KB000034038 | VMWARE PROBE FAILING (POPUP ERROR: CONF_VMWARE HAS STOPPED WORKING)
We are getting this error message when trying to view VMWare probe from Infrastructure Manager on one of our vCenter servers. Description: Stopped working Problem signature: Problem Event Name:u0009APPCRASH Application Name:u0009conf_vmware_6.41.exe Application Version:u00091.0.0.0 Application Timestamp:u00095519cef7 Fault Module Name:u0009KERNELBASE.dll Fault Module Version:u00096.1.7601.23072 Fault Module Timestamp:u0009556367b6 Exception Code:u0009e053534f Exception Offset:u0009000000000000adcd OS Version:u00096.1.7601.2.1.0.16.7 Locale ID:u00091033 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:Windowssystem32en-USerofflps.txt
KB000006097 | VMWARE PROBE DATA COLLECTION ERROR
The vmware probe connects via the API but throws an error shortly after being activated. hostname is not responding (reason: Unexpected fatal error in data collection.
KB000007255 | THE CHANGE ON ACTIVE MONITORS IN VMWARE PROBE DOES NOT GET REFLECTED.
When making change on active monitors through Admin Console, it does not get reflected after the probe is restarted.
KB000074019 | VMWARE PROBE EXPORT LIST OF DATASTORES AND MONITOR SETTINGS
Is it possible to export a list of the datastores discovered by the vmware probe and their monitor settings?
KB000074904 | VMWARE PROBE - TIPS FOR TROUBLESHOOTING SOME COMMON VMWARE PROBLEMS / ALARMS
vmware probe - tips for troubleshooting some common vmware problems / alarms
KB000057252 | DUPLICATE DEVICES IN USM WHEN USING DISCOVERY WIZARD AND VMWARE
Duplicate Devices in USM when using Discovery Wizard and vmware
KB000093067 | VMWARE PROBE DISCOVERS VM'S THAT THE USER HAS NO ACCESS TO
The VMWare probe is configured with a user that does not have access to all VM's in VCenter, however all the VM's are discovered in USM
KB000092775 | UNABLE TO CONFIGURE VMWARE PROBE
We were unable to configure the VMWARE probe. u000aThe probe failed to query the host.
KB000007419 | HEAP MEMORY OF VMWARE PROBE SUDDENLY RISES
When polling cycle is not enough, vwware probe needs to poll next cycle before garbage collection. This makes increase of vmware probe heap memory.
KB000010640 | THE MESSAGES FOR ALARMS FORWARDED FROM VCENTER DO NOT CONTAIN ENOUGH INFORMATION
The vmware probe can generate alarms for events and alarms generated in vcenter. The messages for these alarms do not contain enough information to be useful
KB000035058 | HOW TO ENABLE NUMERICSERVERINFO ON THE VMWARE PROBE
There is a set of information made available by vCenter through the WebServices API that the vmware probe does not present by default. The collection of information is known as HostNumericServerInfo, or sometimes NumericServerInfo in the literature. This includes information about server fans, running temperatures, power supplies, etc. Nimsoft does not present this for monitoring by default. There is a configuration hand-edit that can enable the data for monitoring.
KB000007763 | VMWARE PROBE KEY HOST NOT FOUND
When configuring a new vmware template it appears to be corrupted as soon as we save the configuration. We have audit enabled
KB000034064 | VMWARE FAILED TO COLLECT DATA - ALARMS NOT AVAIABLE
Vmware alarms appear and disappear very quickly from the Infrastructure Management console. There are several. Follow the logs and print attached.
KB000035071 | VMWARE PROBE ERROR: (12) LOGIN FAILED,VMWARE API IS UNAVAILABLE. VI SDK INVOKE
When a customer tries to add a virtual center, the customer get's the following message (12) login failed,VMWare API is unavailable. VI SDK invoke exception:java.net.ConnectException: Connection refused: connect: VI SDK invoke exception:java.net.ConnectException: Connection refused : connect.
KB000010189 | ADDING THE INFRASTRUCTURE GROUPS INTO UIM
There is a feature that enables you to find probes quickly known as Infrastructure Groups. This article shows how to enable this feature.
KB000044160 | RESOURCE NOT RESPONDING AFTER UPGRADING THE VMWARE PROBE TO 6.72 FROM 6.60
vmware resource connection error: login failed, VMWare API is unavailable Exception caught trying to invoke method RetrieveServiceContent; nested exception is: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
KB000047918 | VMWARE : WHAT DO RED, GREEN, YELLOW, UNKNOWN STATUS INDICATE?
vmware : what do red, green, yellow, unknown status indicate?
KB000034272 | VMWARE PERFORMANCE, STABILITY AND RESPONSE
What to look for when troubleshooting the vmware probe performance, stability, and response.
KB000008487 | QOS DATA FOR MONITOR FREE SPACE ON DATASTORE FROM VMWARE PROBE FAILS TO BE SUBMITTED TO SLM DATABASE
This technical document provides information how to resolve the issue related to data from QOS_DS_DISK_FREE monitor not getting recorded in the UIM database
KB000033612 | VCSA SUPPORT ON VMWARE PROBE
Does the UIM vmware probe support VCSA environment ?
KB000007924 | VMWARE PROBE TEMPLATES ARE NOT APPLYING TO ALL SYSTEMS.
When trying to apply different probe configurations via templates, only some of the systems are getting the templates applied. Guest A and Guest B have different names but after trying regex, even explicitly stating the machine name is failing as well.
KB000009745 | [CHECK INTERVAL] RECOMMENDATION.
VMware ESXi/vCenter server does not collect performance data in real time. Therefore, it is meaningless to set [Check Interval] shorter than the VMware ESXi/vCenter server performance interval.
KB000041027 | THE VMWARE PROBE OUTPUT ERROR WITH "INVALID PROPERTY: QUERYSPEC.INTERVAL DETAILS: NULL"
vmware probe keep output the "Invalid property: querySpec.interval Details: null" error for a vCenter Server.
KB000008366 | VMWARE PROBE REPORTS SELF-MONITORING FAILURES FOR PROVISIONED SPACE IN SOME DATA STORES.
Self-monitoring alarms are generated because the probe is unable to collect Provisioned Space information from VMware vCenter.
KB000033926 | VMWARE PROBE POWERSTATE DOES NOT GENERATE AN ALARM
The VMware probe Power State does NOT Alert when it is !=1 and when you turn off the Virtual Machine, the Monitor are all greyed out. How can I make Nimsoft trigger an alert when a Virtual Machine is Powered Off?
KB000015535 | WHAT VARIABLES CAN BE USED IN VMWARE PROBE MESSAGES?
The vmware probe documentation details the variables but does not provide full description
KB000010294 | VMWARE PROBE ERROR FAILED TO EXECUTE - MAX QUERY SIZE
Keep getting: Failed to execute single perf query for entity resgroup-1040. Max query size exceeded. Request processing is restricted by administrator (vpxd.stats.maxQueryMetrics). Follow VMware KB 2107096 to resolve.
KB000071382 | VMWARE HOSTMEMORYUSAGE METRIC
vmware probe monitoring vcenter and esx servers and estsummary unified dashboard, HostMemoryUsage metric shows above 100%u000au000awhy it can go above 100% and whats the calculation formula used for this.
KB000071599 | DUPLICATE DEVICE ENTRIES EXIST FOR THE SAME DEVICE IN THE UMP USM PORTLET.
After a full discovery reset, we are still finding that there are 2 entries for some virtual host devices.
KB000074043 | VMWARE MONITORING IS NOT WORKING FOR A TRIAL
We just installed a relay and new robot to monitor VMware but we are getting a error.u000au000aMar 16 10:31:19:496 [Data Collector - test123, vmware] DataCollector for test123 collecting datau000aMar 16 10:31:19:496 [Data Collector - test123, vmware] PERF: START: ----- Pass-001 --- Data Collector Check Interval for: test123u000aMar 16 10:31:19:496 [Data Collector - test123, vmware] PERF: Memory Status: Max=1820 CurrentAllocated=156 Free=136 Used=20 MBu000aMar 16 10:31:19:496 [Data Collector - test123, vmware] https://18.104.22.168:443/sdk: login as firstname.lastname@example.orgMar 16 10:31:19:496 [Data Collector - test123, vmware] First try to login to https://22.214.171.124:443/sdk failed - SSLHandshakeException. Trying again.
KB000093245 | HOW DO YOU ADD A NEW ALARM MESSAGE FOR THE VMWARE PROBE WHEN BULK DEPLOYMENT IS IN USE?
If you are using Bulk Deployment in the vmware probe then adding a new alarm message in the cfg or via raw configure does not show up when you select alarm messages in the probe configuration.
KB000095683 | CA UIM - NOT RECEIVING CLEAR ALARMS FOR THE VMWARE PROBE
No Clear Alarms received from the vmware probe?u000au000aThe probe has been configured using the bulk configuration method / UMP Metrics template, we are monitoring QOS_VMWARE_DATASTORE_ACCESSIBLE. We've configured a High Operator and Low Operator, when the Datastore is down (not accessible) we do receive the Major Alarm as expected however, we do not receive a Clear Alarm when the Datastore is accessible again. u000au000aCurrently settings is: u000au000aLOW OPERATOR = 1(Powered ON) u000aLow threshold = True u000aLow Message name = MonitorInfo
KB000096824 | CA UIM - DUPLICATE DEVICE ENTRIES IN USM AND METRICS DISPLAYED UNDER THE WRONG DEVICE (CDM AND VMWARE PROBE DATA)
We have deployed a robot to a server and configured the cdm probe, the same server is also being monitored by the vmware probe which is running on a separate robot. u000au000aIn this scenario two device entries are displayed in the USM, one vmware entry containing the vmware data. The other is the robot entry containing the cdm data. u000au000aAfter several weeks, a new file system was added to the server. All other file systems display under the robot however, the newly added file system is displayed under the vmware probe entry.
KB000012278 | HOW TO DISABLE DISCOVERY OF ALL VM?S WHEN USING VMWARE PROBE?
This article shows how to disable discovery of all VM?s when using vmware probe.
KB000007766 | PROBEDISCOVERY QUEUE NOT PROCESSING ANY MESSAGES
The discovery_server probe shows high CPU consumptions but fails to clear messages from the probeDiscovery queue, eventually causing the hub to disconnect the queue.
KB000045476 | HOW DO I TROUBLESHOOTING MISSING DATA
Walks a user through the steps to find why data might not be showing up in USM.
KB000009879 | SNMPCOLLECTOR PROBE - PERFORMANCE TUNING AND OPTIMIZATION GUIDELINES
snmpcollector probe tuning and optimization guidelines and recommendations
KB000034300 | SLOW PERFORMANCE AND RESPONSE ISSUES
What can I look at besides probe scalability and performance parameters when troubleshooting slow performance and response in NMS, SLM, or UMP?
KB000005772 | INVALID ALARMS FROM SNMPCOLLECTOR
False alarms for probe snmpcollector; VMware; cdm and others
KB000010355 | WHAT IS DIFFERENCE IN BETWEEN 'STATIC MONITOR' AND 'AUTO MONITOR' AND HOW IM GUI 'TEMPLATE' INTERACTS WITH PROBE.
There are 2 similar operation in IM GUI which results completely different intreaction with the probe, when you are using template.
KB000034371 | DE: QOSINSERT::CHECKDATAINTEGRITY - MESSAGE DROPPED; SAMPLEMAX IS MISSING. QOS=QOS_MEMORY_USAGE
Error was showing in the data_engine v7/89 log: u0009 QoSInsert::CheckDataIntegrity - message dropped; samplemax is missing
KB000033598 | VMWARE AUTO MONITORS ARE SUPERIOR TO STATIC MONITORS
Static monitors can overload the vmware probe and cause unexpected null values. Auto monitors should always be deployed by default.
KB000010578 | ADMIN CONSOLE - CHANGE VMWARE UMP METRICS TEMPLATE
This document explains why the "UMP Metrics" template is applied by default to the vmware probe and how you can override it if required.
KB000038163 | SPECTRUM - UIM INTEGRATION FAQ
Spectrum to UIM integration
KB000034939 | COMMUNICATION ERROR OCCURS WHEN OPENING VMWARE PROBE GUI OR STORAGE PROBES
Storage probes that contain large numbers of static monitors will cause a "communication error" to pop up in IM when the configuration GUI is opened. Using Auto monitors will cut down on the size of the config file and allow the GUI to open.
KB000035422 | VMWARE: ALARM MESSAGE FOR DISABLED STATIC MONITORS
After disabling static monitors for a specific vmware on the vcenter you still get alarms that the now inactive monitors cannot be configured.
KB000034923 | VMWARE PROBE: DUPLICATE UUID ENCOUNTERED
vmware probe generating duplicate UUID alarm messages. A duplicate Virtual Machine UUID was encountered. Please consider enabling use_instance_uuid to properly track VM instances.
KB000033921 | DATA_ENGINE QUEUE IS HUGE AND ADO_BULKINSERT::COMMIT - FAILED SEEN IN THE LOG
May 21 10:54:07:405  de: ADO_BulkInsert::Commit - failed for RN_QOS_DATA_0049 May 21 10:54:07:405  de: Commit - ERROR: Code=0x80004005 Source=Microsoft OLE DB Provider for SQL Server Description=The statement has been terminated. May 21 10:54:07:405  de: Commit - ERROR: Code=0x80004005 Source=Microsoft OLE DB Provider for SQL Server Description=Cannot insert the value NULL into column 'tz_offset', table 'nod113.dbo.RN_QOS_DATA_0049'; column does not allow nulls. INSERT fails.
KB000034665 | TUNING VMWARE PROBE PERFORMANCE
The following config variables can be adjusted to optimize the vmware probe in circumstances of poor performance.
KB000057229 | HOW DOES DISCOVERY CORRELATION WORK?
How Does Discovery Correlation Work?
KB000034026 | VCENTER SERVER ONLY SHOWS AS A HOST - NOT VCENTER
The discovery_server was reporting a server (hosting vCenter) as only a 'host' and not 'vCenter'
KB000072455 | UIM VIRTUAL MACHINE WITH MORE THAN ONE IP ADDRESS WHICH IP ADDRESS THE UIM GET TO TRIGGER ALARM
When the virtual machine has more than one IP address which IP address the UIM will choose and send the alarms and QoS
KB000034421 | PROBEDISCOVERY QUEUE NOT DRAINING IN CA UIM 8.1
How to workaround or resolve the problem.u000aThe probe discovery queue is not draining/falling behind.
KB000034726 | HOW DO I FIND THE SOURCE OF A USM ENTRY?
In some cases, hubs, robots or devices may still appear in USM despite being previously removed from the infrastructure/monitoring environment. This Article describes an approach to find any underlying data which may cause this to happen.
KB000007627 | TIME OVER THRESHOLD SETTING IS NOT UPDATING IN ADMIN CONSOLE
A reset of baseline_engine and alarm_enrichment should clear up most TOT setting problems.
KB000015227 | HOW TIME OVER THRESHOLD WORKS
A brief summary of how the time over threshold works.
KB000091942 | BEST PRACTICES FOR UIM, HUBS, ROBOTS, AND SELECT PROBES
This article contains a list of helpful links related to general UIM best practices, along with Hub, Robots, and some Probes
Was this information helpful?