Search the VMware Knowledge Base (KB)
View by Article ID

vSAN objects are not discovered or collected in vRealize Operations Manager 6.6.0 (2150746)

  • 1 Ratings
Language Editions

Symptoms

  • vSAN Objects are not discovered in vRealize Operations Manager 6.6.0.
  • Existing vSAN objects collected with vSAN Management Pack in vRealize Operations Manager 6.5 shows the status:
     
    Not Existing

  • In the  /storage/log/vcops/log/adapters/VsanStorageAdapter/VsanStorageAdapter_XXX.log file, you see entries similar to:

    com.vmware.adapter3.vsan.DiscoveryEngine.discover - Error during VC Inventory discovery task.
    (vmodl.fault.InvalidArgument) {
    faultCause = null,
    faultMessage = null,
    invalidProperty = token
    }
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
        at java.lang.Class.newInstance(Class.java:442)
        at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:174)
        at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:25)
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:30)
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.parse    
             (UnmarshallerImpl.java:150)
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.unmarshall    
             (UnmarshallerImpl.java:101)
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:88)
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:83)
        at com.vmware.vim.vmomi.client.common.impl.SoapFaultStackContext.setValue(SoapFaultStackContext.java:40)
        at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.processNextElement(ResponseUnmarshaller.java:127)
        at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.unmarshal(ResponseUnmarshaller.java:70)
        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.unmarshalResponse(ResponseImpl.java:272)
        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:229)
        at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:150)
        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:48)
        at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:226)
        at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:110)
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall    
            (MethodInvocationHandlerImpl.java:581)
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall    
            (MethodInvocationHandlerImpl.java:562)
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall    
            (MethodInvocationHandlerImpl.java:344)
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation

    Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment. 

Cause

This issue occurs due to Incorrect pagination handling when obtaining resources from vCenter Server running vSAN when the total number of objects for Clusters, Hosts and Datastores is either equal to 100 or greater than 200.

Resolution

This issue is resolved in VMware vRealize Operations Manager 6.6.1, available at VMware Downloads.
 
To work around this issue if you do not want to upgrade, you can apply a hotfix. To request for this hotfix, contact VMware Support and note this Knowledge Base article ID (2150746) in the problem description. For more information, see Filing a Support Request in My VMware (2006985).
 
Note: This hot fix is only applicable for vRealize Operations Manager 6.6.0.

See Also

Update History

Version updated - Aug 8 2017

Language Editions

zh_cn,2151355

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 1 Ratings
Actions
KB: