Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

163975

March 17th, 2015 15:00

No VM Network traffic being pulled, and no Datastore Info

I am running a trial of Foglight Visualization Enterprise, and have things up and running, and an agent installed for my VMWare infrustructure vCenter server.  it is pulling a lot of info, but none of the basic datastore info is being pulled (not the stuff that requires the Foglight for Storage integration) and none of the network information is being pulled for the individual VM's.  The hosts and parents have netowrk traffic showing, but nothing on the VM side.  The environment is configured with dvswitches for data, iscsi, vmotion, etc.  Any idea what might be going on, or what I can look at?

I see some errors in the agent log if I pull it down about datastores... here is a sample:

ERROR [Quartz[0]-6] com.quest.agent.esx.task.HardwareTask - DatastoreInfo is missing for Datastore:datastore-162
2015-03-17 13:57:16.165 ECHO ERROR [Quartz[0]-6] com.quest.agent.esx.task.HardwareTask - DatastoreInfo is missing for Datastore:datastore-131
2015-03-17 13:57:16.165 ECHO ERROR [Quartz[0]-6] com.quest.agent.esx.task.HardwareTask - DatastoreInfo is missing for Datastore:datastore-10985

But other than that, I don't see a whole lot... I do see what appears to be some Java warnings, such as this: 

2015-03-17 13:57:17.291 ECHO WARN [Quartz[0]-6] com.quest.agent.esx.task.ESXAgentTask - Inventory and Relations - Error during FGLAM submission: null
java.lang.NullPointerException
at com.quest.vmware.agent.history.samples.VMWHostVirtualSwitch__IMPL.__addPropertiesToNodeTree(VMWHostVirtualSwitch__IMPL.java:2418)
at com.quest.vmware.agent.history.samples.VMWHostVirtualSwitch__IMPL.__addToNodeTree(VMWHostVirtualSwitch__IMPL.java:2348)
at com.quest.vmware.agent.history.samples.VMWESXServerNetwork__IMPL.__addPropertiesToNodeTree(VMWESXServerNetwork__IMPL.java:1339)
at com.quest.vmware.agent.history.samples.VMWESXServerNetwork__IMPL.__addToNodeTree(VMWESXServerNetwork__IMPL.java:1078)
at com.quest.vmware.agent.history.samples.VMWESXServer__IMPL.__addPropertiesToNodeTree(VMWESXServer__IMPL.java:5015)
at com.quest.vmware.agent.history.samples.VMWESXServer__IMPL.__addToNodeTree(VMWESXServer__IMPL.java:4213)
at com.quest.vmware.agent.history.samples.VMWCluster__IMPL.__addPropertiesToNodeTree(VMWCluster__IMPL.java:10666)
at com.quest.vmware.agent.history.samples.VMWCluster__IMPL.__addToNodeTree(VMWCluster__IMPL.java:10010)
at com.quest.vmware.agent.history.samples.VMWClusterCollection__IMPL.__addPropertiesToNodeTree(VMWClusterCollection__IMPL.java:780)
at com.quest.vmware.agent.history.samples.VMWClusterCollection__IMPL.__addToNodeTree(VMWClusterCollection__IMPL.java:702)
at com.quest.vmware.agent.history.samples.VMWVirtualCenter__IMPL.__addPropertiesToNodeTree(VMWVirtualCenter__IMPL.java:9298)
at com.quest.vmware.agent.history.samples.VMWVirtualCenter__IMPL.__addToNodeTree(VMWVirtualCenter__IMPL.java:8979)
at com.quest.vmware.agent.history.samples.VMWModel__IMPL.__addPropertiesToNodeTree(VMWModel__IMPL.java:1304)
at com.quest.vmware.agent.history.samples.VMWModel__IMPL.__addToNodeTree(VMWModel__IMPL.java:974)
at com.quest.vmware.agent.history.samples.VMWModel__IMPL.buildSubmission(VMWModel__IMPL.java:919)
at com.quest.vmware.agent.history.samples.VMWModel__IMPL.submit(VMWModel__IMPL.java:810)
at com.quest.agent.esx.task.HardwareTask.submitData(HardwareTask.java:813)
at com.quest.agent.esx.task.ESXAgentTask.submit(ESXAgentTask.java:208)
at com.quest.agent.esx.task.ESXAgentTask.run(ESXAgentTask.java:201)
at com.quest.agent.esx.ESXAgent.runTask(ESXAgent.java:518)
at com.quest.agent.esx.ESXAgent.esxHardwareCollection(ESXAgent.java:718)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.quest.glue.core.services.EquivalenceInvocationHandler.invoke(EquivalenceInvocationHandler.java:76)
at com.quest.glue.core.agent.AgentInteractionHandler.invoke(AgentInteractionHandler.java:177)
at com.sun.proxy.$Proxy65.esxHardwareCollection(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.quest.glue.core.agent.scheduler.CollectorCallback.invokeCollector(CollectorCallback.java:246)
at com.quest.glue.core.agent.scheduler.CollectorCallback.execute(CollectorCallback.java:146)
at com.quest.glue.common.util.scheduler.quartz.QuartzScheduler$ScheduledTaskSequentialJob.execute(QuartzScheduler.java:738)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

Thanks in advance!!

-Jake

March 18th, 2015 09:00

Hi Jake,

I am not sure what could be causing this issue, it does look you have added the Datastore Browse role to the Foglight service account in vCenter. Could you please create a Service Request with Support?
https://support.software.dell.com/

Could you also attach a FglAM Support Bundle to the case? please post the case number here, or send it to me via private message.

Thanks.

Gaston.

March 18th, 2015 09:00

I did enable it, but haven't added any agents for storage, and should just go in and disable the agent packages for it that I installed, I thought that might be why I was getting those errors... but couldn't be sure.  I'll open a support case will Dell and see what they have to say, I'll send something your way as well when I have it open so your aware :)  Thanks a bunch!

March 18th, 2015 10:00

Jake,

By the way, here is the link to the document explaining all the required roles you need to assign to the service account used by the VMware agent to access the vCenter. Please check you have added all required roles.

http://edocs.quest.com/vfoglight/800/doc/Cartridge/vFoglightCartridge-install/CartridgeForVMwareInstall_Installation.12.php

March 18th, 2015 11:00

The support number is SR:2772054

Thanks!

March 18th, 2015 11:00

Thanks Gaston,

For the sake of ease, during the trial period I used my vCenter Admin account when creating the monitoring agent for vCenter, which is a full administrator in vCenter... so I don't believe it would be related to that.

No Events found!

Top