Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Possible Bug with Vmware sync
#1
Hello ASG Support and Community,

I found that if I have a VM with 120gig RAM or more present on a vmware host either online or offline and I try to sync ASG to that vCenter, that it will fail and give up. 

Anyone else seen this?

thanx

Nid.

edit:

I have confirmed that if I edit the VM down to 80gig RAM sync is okay, so maybe the Sync operation cannot handle 3 digit spaces in the ram field    120gig vs 80gig  ?

I can also report that Servers with 32+ vCPUs cause the vcenter sync to fail also. This may be a limitation of the sync if the Cores is above 8 and or the sockets are above 4.
Reply
#2
Are you running the x86 or x64 application of ASGRD?

We will try to reproduce - do you have any error logs in ASGRD? Which version of ASGRD are you using and which version of vCenter/ESX?
Regards/Gruss
Oliver
Reply
#3
We have tried with following VM parameters - 56 CPU and 512GB RAM - without any issues...
Regards/Gruss
Oliver
Reply
#4
(11-02-2021, 10:18 AM)DevOma Wrote: Are you running the x86 or x64 application of ASGRD?

We will try to reproduce - do you have any error logs in ASGRD? Which version of ASGRD are you using and which version of vCenter/ESX?

ASG 2020 x64 Patch 6
vcenter 6.5
Reply
#5
(11-02-2021, 10:18 AM)DevOma Wrote: Are you running the x86 or x64 application of ASGRD?

We will try to reproduce - do you have any error logs in ASGRD? Which version of ASGRD are you using and which version of vCenter/ESX?

How do I pull logs to help ?
Reply
#6
Administration - Logs - Error Log
Regards/Gruss
Oliver
Reply
#7
(11-02-2021, 08:33 PM)DevOma Wrote: Administration - Logs - Error Log

The Top Log is the VM with properties that are blocking the sync. It is Online and running.
Details: ESXi 5.5 compatibility (VM version 10) on ESXi 6.5 host.
VM has 32 CPU and 32 gig RAM


The bottom Log is the VM that is offline. When the server had 120gig RAM sync failed and when I edited it to 80 gig RAM it stopped being reported as a problem.


Attached Files Thumbnail(s)
   
Reply
#8
Hi,
can you doubleclick on the log entry ? That should normally provide some more infos.
Best regards
Michael
best regards,
Michael -- michael.scholz@asg.com --
Reply
#9
Error while loading properties of virtual machine 'xxx4.xxx.com' with ID 'vm-401' from vCenter Server.

---------------------------

at visionapp.vVE.vVM.ESXEnvironment.SetVMProperties(VimServiceConnection vimConnection, String VMIdentifier, DynamicProperty[] VMProperties, ObjectTypes ChildType, EsxManagedObjectPropertyCache managedObjectCache, Boolean throwOnError)
at visionapp.vVE.vVM.ESXEnvironment.AddNestedObjects(VimServiceConnection vimConnection, VEStructureItem item, Dictionary`2 objectContentDictionary, EsxManagedObjectPropertyCache managedObjectCache)
at visionapp.vVE.vVM.ESXEnvironment.AddNestedObjects(VimServiceConnection vimConnection, VEStructureItem item, Dictionary`2 objectContentDictionary, EsxManagedObjectPropertyCache managedObjectCache)
at visionapp.vVE.vVM.ESXEnvironment.AddNestedObjects(VimServiceConnection vimConnection, VEStructureItem item, Dictionary`2 objectContentDictionary, EsxManagedObjectPropertyCache managedObjectCache)
at visionapp.vVE.vVM.ESXEnvironment.AddNestedObjects(VimServiceConnection vimConnection, VEStructureItem item, Dictionary`2 objectContentDictionary, EsxManagedObjectPropertyCache managedObjectCache)
at visionapp.vVE.vVM.ESXEnvironment.GetVmAndTemplatesView(VimServiceConnection vimConnection, VEStructureItem StartObject, String[] PathSet)
at visionapp.vVE.vVM.ESXEnvironment.GetVmAndTemplatesView(VEStructureItem StartObject, Boolean AllProperties)
at PlugInVMware.Helper.SyncHelper.SyncVMFolder(IWin32Window owner, IBaseItem folderParams, CredentialsParameter creds, Object props, ConnectionCustomFieldsSettings customFields)
Reply
#10
Error while loading properties of virtual machine 'xxxxxxx50m' with ID 'vm-399' from vCenter Server.

---------------------------

at visionapp.vVE.vVM.ESXEnvironment.SetVMProperties(VimServiceConnection vimConnection, String VMIdentifier, DynamicProperty[] VMProperties, ObjectTypes ChildType, EsxManagedObjectPropertyCache managedObjectCache, Boolean throwOnError)
at visionapp.vVE.vVM.ESXEnvironment.AddNestedObjects(VimServiceConnection vimConnection, VEStructureItem item, Dictionary`2 objectContentDictionary, EsxManagedObjectPropertyCache managedObjectCache)
at visionapp.vVE.vVM.ESXEnvironment.AddNestedObjects(VimServiceConnection vimConnection, VEStructureItem item, Dictionary`2 objectContentDictionary, EsxManagedObjectPropertyCache managedObjectCache)
at visionapp.vVE.vVM.ESXEnvironment.AddNestedObjects(VimServiceConnection vimConnection, VEStructureItem item, Dictionary`2 objectContentDictionary, EsxManagedObjectPropertyCache managedObjectCache)
at visionapp.vVE.vVM.ESXEnvironment.AddNestedObjects(VimServiceConnection vimConnection, VEStructureItem item, Dictionary`2 objectContentDictionary, EsxManagedObjectPropertyCache managedObjectCache)
at visionapp.vVE.vVM.ESXEnvironment.GetVmAndTemplatesView(VimServiceConnection vimConnection, VEStructureItem StartObject, String[] PathSet)
at visionapp.vVE.vVM.ESXEnvironment.GetVmAndTemplatesView(VEStructureItem StartObject, Boolean AllProperties)
at PlugInVMware.Helper.SyncHelper.SyncVMFolder(IWin32Window owner, IBaseItem folderParams, CredentialsParameter creds, Object props, ConnectionCustomFieldsSettings customFields)
Reply
#11
We will try to reproduce again - we just set high values for the mentioned fields and nothing happened - we will continue working on this issue...
Regards/Gruss
Oliver
Reply
#12
(22-02-2021, 02:52 PM)DevOma Wrote: We will try to reproduce again - we just set high values for the mentioned fields and nothing happened - we will continue working on this issue...

I really believe the error is on the vmware side. We have many vCenters and only one Vcenter has this issue and only a few VM servers.

if it helps for testing, try to make the VM settings for the OS mismatch. VMware tools expects the server to be 2008 but the server might have been OS upgraded to 2012 and now VMware could be confused about it

The below image is not related to the VM servers with the reported issued. 


Picture is only an example.
   
Reply




Users browsing this thread: 1 Guest(s)