ViPR SRM: Seeing severe errors in VMware collecting logs

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms



After upgrading to ViPR SRM 4.0.1, user started noticing these errors in the VMware collecting logs. The reports do not seem to be affected.

SEVERE   [2017-01-10 09:15:52 CST]   WSClient::invoke(): Exception caught while invoking method: RetrieveProperties
com.vmware.vim25.InvalidProperty
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAcce ssorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstru ctorAccessorImpl.java:45)

SEVERE   [2017-01-10 09:15:52 CST]   GroupedArrayHandler::a(): Error while polling data com.vmware.vim25.VirtualMachineUsageOnDatastore@38ef048a
com.watch4net.apg.collector.plugins.vmwarecollector.VMWareException: The property summary.url is invalid on the entity hostname.FQDN.bz. Please verify in the MOB. It's probably a MOR or an array.

Cause

Polling period needs to be increased.

Resolution

Increase the polling period to 15 minutes. Polling interval for VMware vCenter collection default value is 5 minutes. Change it to 15 minutes. Then click "Reconfigure". Monitor the VMware collecting log as the errors should clear.
Article Properties
Article Number: 000057112
Article Type: Solution
Last Modified: 30 May 2024
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.