Problems with Cluster Compliance...

[fduranti]

Hi all,

I was a bit undecided on where to post this problem because it's a bit DRS a bit HA and a bit a Host profile problem...

The principal fact is this:

I have 2 cluster, one with 5 ESXi 4.0 machine and one with 6 ESX 4.0 machine. It seems that I cannot make the Check Compliance profile to work in any way.

I've tested various thing and it seems that I get many kind of error.

The machine are all but 2 upgraded from ESX/ESXi 3.5 and all seems to work good.

One machine per Cluster was got for the profile compliance and the host profile compliance seems good (all machine are ok with compliance to the host profile).

I've problems instead with the Cluster compliance...

Case 1: Only DRS enabled on the 2 clusters.

on both Clusters i get a failure on every host about Cluster Requirements compliance related to "VMotion NIC speed is not at least 1000 Mbps" but every host on the ESXi cluster have 2 NIC on the VMkernel distributed Switch and the NICS are configured at 1000 FD while on the ESX cluster the VMKernel have one 10Gb network card and one 1Gb card (this is just for high availability).

Case 2: HA and DRS enabled

In this case, on both cluster i get the 2 "Check Compliance" process running but one of the 2 exit with the error:

"A general system error occurred: Not initialized: anyType value"

On the ESXi Cluster the Cluster requirement compliance is in a "noncompliant" status. Some times on this cluster i can also see errors in the Host Compliance failure for the cluster related to FT logging/FT CPU incompatibilities (it's possible to disable those kind of checks somewhere?).

On the ESX cluster instead the Cluster requirement compliance is in an Unknown status with a blue "?".

Checking on the vpxd.log on the vCenter Server this is the error I get (it's running on W2008 64 bit).

2009-06-01 00:54:26.898 02780 trivia 'App' Received soap response from : checkClusterCompliance

2009-06-01 00:54:26.898 02780 error 'App' Exception in DeserializeObj: Not initialized: anyType value

2009-06-01 00:54:26.898 02780 error 'App' backtrace[00] eip 0x022686bd ?AbortProcess@System@Vmacore@@YAXXZ

backtrace[01] eip 0x022690f7 ?CreateQuickBacktrace@SystemFactoryImpl@System@Vmacore@@UAEXAAV?$Ref@VBacktrace@System@Vmacore@@@3@@Z

backtrace[02] eip 0x021ab130 ??0Throwable@Vmacore@@QAE@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z

backtrace[03] eip 0x0244ee3d ?InitLocale@Vmomi@@YAXABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z

backtrace[04] eip 0x0249e4f6 ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[05] eip 0x0249e947 ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[06] eip 0x0249d80a ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[07] eip 0x0249da8f ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[08] eip 0x0249e899 ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[09] eip 0x0249e393 ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[10] eip 0x0249e947 ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[11] eip 0x0249e393 ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[12] eip 0x0249e947 ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[13] eip 0x0249d80a ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[14] eip 0x0249da8f ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[15] eip 0x0249e899 ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[16] eip 0x0249e393 ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[17] eip 0x0249e947 ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[18] eip 0x0249d80a ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[19] eip 0x0249da8f ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[20] eip 0x0249e899 ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[21] eip 0x0249e393 ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[22] eip 0x0249e947 ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[23] eip 0x0249eb1e ?DeserializeObj@Vmomi@@YAXPAVDeserializationVistor@1@AAV?$list@U?$pair@PAVDataProperty@Vmomi@@V?$Ref@VDataObject@Vmomi@@@Vmacore@@@std@@V?$allocator@U?$pair@PAVDataProperty@Vmomi@@V?$Ref@VDataObject@Vmomi@@@Vmacore@@@std@@@2@@std@@AAV?$Ref@VAny@Vmomi@@@Vmacore@@@Z

backtrace[24] eip 0x0249762a ?CreateVmodlSoapBodyHandler@Vmomi@@YAXPAVLogger@Service@Vmacore@@PAVAdapterServer@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AAV?$Ref@VBodyHandler@Soap@Vmacore@@@4@@Z

backtrace[25] eip 0x0249ac42 ?DeserializeSoapResponse@Vmomi@@YAXPAVReader@Vmacore@@PAVManagedMethod@1@PAVVersion@1@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PAVLogger@Service@3@AA_NAAV?$Ref@VAny@Vmomi@@@3@@Z

backtrace[26] eip 0x00f6650b (no symbol)

backtrace[27] eip 0x00f66611 (no symbol)

backtrace[28] eip 0x024401f4 ?_Invoke_Task@StubImpl@Vmomi@@UAEXPAVManagedMethod@2@AAV?$RefVector@VAny@Vmomi@@@Vmacore@@AAV?$Ref@VAny@Vmomi@@@5@@Z

backtrace[29] eip 0x00b8fbc2 (no symbol)

backtrace[30] eip 0x00c277d2 (no symbol)

backtrace[31] eip 0x00c227a2 (no symbol)

backtrace[32] eip 0x02e9c667 ?_IsEqual@ProfilePropertyPath@Profile@Vim@@UBE_NPAVAny@Vmomi@@_N@Z

backtrace[33] eip 0x024137ab ?AddFat@Activation@Vmomi@@QAEXPAVObject@Vmacore@@@Z

backtrace[34] eip 0x02413782 ?AddFat@Activation@Vmomi@@QAEXPAVObject@Vmacore@@@Z

backtrace[35] eip 0x0082b583 (no symbol)

backtrace[36] eip 0x0080bbd9 (no symbol)

backtrace[37] eip 0x00814777 (no symbol)

backtrace[38] eip 0x00821c31 (no symbol)

backtrace[39] eip 0x00d1f758 (no symbol)

backtrace[40] eip 0x7689e4a5 BaseThreadInitThunk

backtrace[41] eip 0x7793cfed RtlCreateUserProcess

backtrace[42] eip 0x7793d1ff RtlCreateProcessParameters

2009-06-01 00:54:26.898 02780 verbose 'PropertyProvider' RecordOp ASSIGN: info.state, task-6671

2009-06-01 00:54:26.898 02780 trivia 'PropertyCollector' TriggerProcessGUReqs: Session 880ECA99-6420-4435-9E16-3FEF0AFC66AA

2009-06-01 00:54:26.898 02780 trivia 'PropertyCollector' TriggerProcessGUReqs: Session 245F8533-0086-4656-8476-4B78066298C6

2009-06-01 00:54:26.898 02780 verbose 'PropertyProvider' RecordOp ASSIGN: info.cancelable, task-6671

2009-06-01 00:54:26.898 02780 verbose 'PropertyProvider' RecordOp ASSIGN: info.error, task-6671

2009-06-01 00:54:26.898 02780 info 'App' -- FINISH task-6671 -- -- vim.profile.ComplianceManager.checkCompliance -- 245F8533-0086-4656-8476-4B78066298C6(ED387B07-B411-4D33-A41A-8FBA0E2F0349)

2009-06-01 00:54:26.898 03376 trivia 'PropertyCollector' ProcessGUReqs Start: Session 880ECA99-6420-4435-9E16-3FEF0AFC66AA

2009-06-01 00:54:26.898 04224 trivia 'PropertyCollector' ProcessGUReqs Start: Session 245F8533-0086-4656-8476-4B78066298C6

2009-06-01 00:54:26.898 02780 info 'App' -- ERROR task-6671 -- -- vim.profile.ComplianceManager.checkCompliance: vmodl.fault.SystemError:

(vmodl.fault.SystemError) {

dynamicType = <unset>,

faultCause = (vmodl.MethodFault) null,

reason = "Not initialized: anyType value",

msg = "",

}

2009-06-01 00:54:26.898 02780 verbose 'PropertyProvider' RecordOp ASSIGN: info.completeTime, task-6671

[agoel]

Hello,

I would like to gather some information on the two cases you've described.

Case 1 - only DRS enabled on the 2 different cluster.

a) You've mentioned that for every host in the ESXi cluster, vmotion interface is enabled on vmkernel port, vmkernel port is configured on a distributed switch, and the switch is connected to 2 physical nics where the speed of both these nics is set at 1000 full-duplex.

Can you please confirm the same settings for hosts in ESX cluster? Are they also using distributed switch or legacy switch (ESX 3x style virtual switch)? Can you check the speed of physical nics on these hosts in ESX cluster?

Side note - We've been informed about the behavior you are seeing in the cluster requirement compliance i.e. - vmotion nic speed is not at least 1000 mbps. It particularly happens with distributed switch settings to which vmkernel is configured. Therefore, I would like to confirm the configuration on ESX cluster for which I asked the question above. Unfortunately, there is no workaround to overcome this compliance message.

Case 2 - DRS and HA enabled on 2 clusters.

a) The blue ? you see in cluster requirements compliance means that the compliance status of each host against cluster compliance rules is not known.

b) Would you be willing to run the use-cases again, capture logs and attach back this thread here?

c) Can you please confirm if both clusters are failing with the Not initialized error?

:smileyinfo: Please add following elements in vpxd.cfg file on temporary basis to enable additional logging that you can remove later. Location of vpxd.cfg is C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter on most Windows systems.

<log>

<maxFileNum>10</maxFileNum>

<compressOnRoll>false</compressOnRoll>

<level>trivia</level>

</log>

<trace>

<vmomi>

<calls>true</calls>

<logLevel>trivia</logLevel>

<verbosity>verbose</verbosity>

<verboseObjectSize>40</verboseObjectSize>

</vmomi>

</trace>

(ii) You have to stop vpxd, change vpxd.cfg, start vpxd again.

(iii) Please run compliance check on only 1 cluster that fails with 'not initialized error', gather the vpxd log file that contains the log matching time for this compliance check, last pyVmomiServer log, and attach it here.

(iv) Please also take a screenshot of the left hand side inventory view of that cluster, and right hand side 'Profile Compliance' tab of that cluster. If the right hand side screenshot doesn't fit in one screen, you can split them in multiple screenshots. Please also highlight the host that says 'nonCompliance' in the same tab (it's at the bottom view) to capture the failure message which appears at the bottom pane called 'host compliance failure'.

Please attach these logs, and screenshots here.

You can revert the vpxd.cfg settings after this.

thanks

[fduranti]

I cannot to the test/logging now but in the meantime I'll answer to the first part...

The 2 cluster are configured mostly in the same (probably strange) way:

We have a dvSwitch for the storage (we use NetApp on NFS) and vmotion VLANs. The configuration is a bit strange because we're going to change the ESXi cluster hosts with some new hosts that will have 10G network too.

At this moment the dvSwitch have 4 uplink configured in this way:

uplink1-2-3 are configured with load ip balancing, uplink 4 is configured as standby.

ESXi cluster hosts have 2 vnic on the uplink 1 and 2 (so they're going in load sharing) and the vnics are 1000 FD.

ESX cluster hosts have 2 vnic on the uplink 3 (10G) and 4 (1 GB used as a standby) the 10G is saw as 10000 FD and the 1GB as 1000 FD.

This is because we're getting new machine with 2 10G (to substitute the ESXi) and putting a second 10G network interface on the ESX hosts.

Regarding the Case 2 I can confirm that both cluster get the not initialized error. I've also done another test getting 2 of the ESX hosts out of one cluster, I've created a new Cluster with just 2 hosts and the problem is back there.

With this new cluster I've done a test with all cluster configuration:

1) DRS only: i get the vmotion speed problem

2) HA only: i get the "not initialized problem"

2) HA/DRS: i get the "not initialized problem"

Tomorrow I'll change the configuration, run the test and attach log/screenshot.

Thanks for the help

Francesco

[agoel]

thanks for the response. Based on the information you've provided for Case 1, ESX cluster is also using distributed virtual switch. So that confirms it to be an issue which was brought to our attention recently, as I was mentioning earlier.

As for Case 2, you can run your test with just HA set on the cluster, since it looks like that's where the error probably is, given that HA was common between your earlier runs of HA only and HA+DRS settings, and error showed up on both.

thanks

[fduranti]

Hi ... back with some logs and screenshot. It's from the Cluster 02 with all ESX machine... I've attached 2 vpx.log because the error was just near the end of the first log so I don't know if the next log could be useful too...

You can find the error at 1:29:44 in the vpxd.log

Hoping this can help...

Just another question... it's possible to disable for example FT checks for cluster if the CPU are not compatible or we will get Compliance errors also if we don't want FT on a Cluster?

Regards

Francesco

[fduranti]

Hi... do you have any news about the case 2?

Thanks

Francesco

[agoel]

Hi,

I am trying to analyze the data which was uploaded in previous logs. If you still have the exact setup, would you please tell me the ESX version number for each of the ESX hosts in that cluster? There are a total of 6 ESX hosts; please take a look at the compliance.jpg screenshot which you had uploaded for me as a reference to get the cluster name and ESX host names.

If you have a different setup now showing the same symptoms, getting the ESX version from that would be fine too. ESX version # is visible in vSphere client at the top of Getting Started page when you highlight a particular ESX host.

thanks

[fduranti]

Hi, we have changed our infrastructure a bit because we're upgrading some older server with new server with xeon 5500 cpu. I've just finished to do some tests and here the result for all of our cluster:

Cluster 1: 3 x Dell 2950 HA/DRS Enabled - ESXi4.0.0 - 164009 - Error

One of the 2 compliance check return the "A general system error occurred: Not initialized: anyType value". The compliance status get the Non compliance for the cluster and Compliant for the Hosts. I cannot see on the Compliance failure why the hosts are not compliant for the cluster.

Cluster 2: 5 x Dell R900 HA/DRS Enabled - ESX 4.0.0 - 164009 - Error

One of the 2 compliance check return the "A general system error occurred: Not initialized: anyType value". The compliance status get the "N/A" and "Unknown" status for the Cluster and Compliant for the Hosts. I cannot see on the Compliance failure why the hosts are not compliant for the cluster.

Cluster 3: 2 x Dell R700 (with xeon 5500) - ESX 4.0.0 - 164009 - No Error

Those machine was newly installed. The 2 compliance check get the Completed status. The host profile is compliant and the cluster profile is not compliant (vmotion nic and ft logging nic speed not at least 1000 Mbps - we have a 10g and a 1g network card on those network).

Cluster 4: 2 x Dell R900 HA/DRS Enabled - ESX 4.0.0 - 164009 - No Error

Those machine was in the old Cluster 2 but was removed because we needed some hosts out of the cluster. The 2 compliance check get the Completed status. The host profile is compliant and the cluster profile is not compliant (FTP not supported on this host: IncompatibleCPU, vmotion nic and ft logging nic speed not at least 1000 Mbps - we have a 10g and a 1g network card on those network).

Now it seems that there's a schema...

The Cluster 3 and cluster 4 machine are all new installed vmware while Cluster 1-2 are all upgraded machines from esxi 3.5 update 4 and esx 3.5 update 4. It seems that there's something that create problem with compliance checks on upgraded hosts. The hosts was all upgraded with the Update manager upgrade process.

[agoel]

Thanks. This should be useful information in narrowing down the problem further. Just for clarification on my theory from previous logs, would you please do the following steps? It will be helpful in eliminating some noise from the logs.

1. Lets stick to Cluster 2, since you are seeing N/A against the cluster compliance status for each host, which is similar to the previous case. On this cluster, can you please detach the Host Profile which is currently attached? You should see a 'detach' option on Profile Compliance page at the top, next to Host Profile. By doing so, only Cluster Requirements would remain to be checked on that cluster. Now when you run compliance check on this cluster, only one task would appear. Please change the vpxd.cfg log level to 'trivia' and restart VirtualCenter service prior to running this test.

When the failure happens, please get that vpxd.log file and PyVmomiServer.log file for that time-stamp and if you can mention the time stamp itself, that would be helpful. Kindly upload these.

2. If (1) above produces the failure, login to the VirtualCenter MOB viewer through this URL - https://Your-VC-IP-Address/mob

Navigate till you reach the Cluster2.

Here are the steps on how to do it - Home page -> content -> group-d1 -> datacenter### -> group-h### (hostFolder property) -> domain-c### (ClusterComputeResource Type)

If your VC inventory has >1 datacenter and >1 Cluster, then you might have to navigate back n forth from 'group-d1' to get to the right datacenter that holds Cluster2 of our interest. Each datacenter link and ClusterComputeResource link has a 'name' property that matches what you see in vSphere client for their names, so you can navigate based on that.

Once you are there at Cluster 2 page, for each of the ESX host listed in the 'host' property -

(a) make a note of that host number, like host-112.

(b) navigate that host link -> capability -> and look for replayUnsupportedReason and ftSupported properties there. Note down the value of these 2 properties next to the (a).

Please do this for all hosts in that Cluster2. If property is missing or value is missing, kindly note down whatever you see there.

Please upload this information also.

thanks

[fduranti]

I will upload the logs as soon as I can stop/restart the VC... in the meantime I've done the test (with current log level) and saw some difference in the field on the SDK browser between the host that don't work in cluster 2 (those host was upgraded from ESX3.5) and the host that work and was in Cluster 4 (now it's not in a cluster).. The 2 machine have the same hardware (Dell R900 with 4 core CPU but without support for FT) and from what I see there are many differences in the 2 host properties between a newly installed and the upgraded ones (it could also be because the freshly installed is out of cluster, I dont know)...

Those are all the properties...

Host that don't work:

backgroundSnapshotsSupported boolean false

cloneFromSnapshotSupported boolean false

cpuMemoryResourceConfigurationSupported boolean true

datastorePrincipalSupported boolean true

deltaDiskBackingsSupported boolean false

dynamicProperty DynamicProperty[] Unset

dynamicType string Unset

ftSupported boolean false

highGuestMemSupported boolean true

ipmiSupported boolean true

iscsiSupported boolean true

localSwapDatastoreSupported boolean true

loginBySSLThumbprintSupported boolean Unset

maintenanceModeSupported boolean true

maxRunningVMs int Unset

maxSupportedVMs int 1200

maxSupportedVcpus int 4

nfsSupported boolean true

nicTeamingSupported boolean true

perVMNetworkTrafficShapingSupported boolean false

perVmSwapFiles boolean true

preAssignedPCIUnitNumbersSupported boolean true

rebootSupported boolean true

recordReplaySupported boolean false

recursiveResourcePoolsSupported boolean true

replayUnsupportedReason string Unset

restrictedSnapshotRelocateSupported boolean true

sanSupported boolean true

scaledScreenshotSupported boolean true

screenshotSupported boolean true

shutdownSupported boolean true

standbySupported boolean true

storageVMotionSupported boolean true

supportedCpuFeature HostCpuIdInfo[] Unset

suspendedRelocateSupported boolean true

tpmSupported boolean false

unsharedSwapVMotionSupported boolean true

virtualExecUsageSupported boolean false

vlanTaggingSupported boolean true

vmotionSupported boolean true

vmotionWithStorageVMotionSupported boolean false

Host that work...

backgroundSnapshotsSupported boolean false

cloneFromSnapshotSupported boolean true

cpuMemoryResourceConfigurationSupported boolean true

datastorePrincipalSupported boolean true

deltaDiskBackingsSupported boolean true

dynamicProperty DynamicProperty[] Unset

dynamicType string Unset

ftSupported boolean false

highGuestMemSupported boolean true

ipmiSupported boolean true

iscsiSupported boolean true

localSwapDatastoreSupported boolean true

loginBySSLThumbprintSupported boolean true

maintenanceModeSupported boolean true

maxRunningVMs int 0

maxSupportedVMs int 1200

maxSupportedVcpus int 8

nfsSupported boolean true

nicTeamingSupported boolean true

perVMNetworkTrafficShapingSupported boolean false

perVmSwapFiles boolean true

preAssignedPCIUnitNumbersSupported boolean true

rebootSupported boolean true

recordReplaySupported boolean false

recursiveResourcePoolsSupported boolean true

replayUnsupportedReason string "incompatibleCpu"

restrictedSnapshotRelocateSupported boolean true

sanSupported boolean true

scaledScreenshotSupported boolean true

screenshotSupported boolean true

shutdownSupported boolean true

standbySupported boolean true

storageVMotionSupported boolean true

supportedCpuFeature HostCpuIdInfo[] Unset

suspendedRelocateSupported boolean true

tpmSupported boolean false

unsharedSwapVMotionSupported boolean true

virtualExecUsageSupported boolean true

vlanTaggingSupported boolean true

vmotionSupported boolean true

vmotionWithStorageVMotionSupported boolean false

[agoel]

Hi,

I don't need logs anymore, at least for now.

I have a request though - would you be willing to deploy the fix in your environment and test the use-case again since you have a consistently reproducible environment? If so, can you please file an SR (service request) with VMware and let me know the name of support engineer who is working with you on the case? Then I can follow up with support engineer to provide you exact steps on deploying the fix etc.

thanks.

[fduranti]

No problem related to opening the SR, I'll do it during the day.

Just a question... i use this account normally (for various reason) that is not linked to vmware product we have (we've another account with the product registered).. I need to open the SR with that accout ?

Regards

Francesco

[agoel]

Please use the account to which the product is registered.

thanks

[rgiglio]

Hey guys, just checking to see if there is a fix for this yet. I too am using host profiles with a dvSwitch for the Service Console and vKernel port groups. This is ESX 4.0.0 Build 175625. The following errors are reported for Cluster Comliance:

• VMotion NIC speed is not at least 1000 Mbps.

• FT logging is not enabled

FT is not being used, so it is not enabled. Both physical NIC's are 1Gbit.

Thanks.