Tile0 deployment failed VMmark 3.1.1

[Avaakaford]

Hi Team,

Trying 1st-time VMmark, please help me to find out the issue. I'm trying to deploy Tile0 , following is the error/warnings i'm observing.

022-07-25T20:31:34.671 [pool-3-thread-12] INFO ST222 : Thread Shutting Down Normally
2022-07-25T20:31:34.673 [pool-3-thread-12] INFO ST222 : Thread Exiting Normally
2022-07-25T20:31:45.799 [pool-3-thread-9] INFO ST222 : AuctionDB0 Creation Successful
2022-07-25T20:31:45.811 [pool-3-thread-9] INFO COMM : AuctionDB0 : Scanning for IP
2022-07-25T20:32:41.084 [pool-3-thread-2] WARN COMM : AuctionAppB0 : All pings failed at 192.168.1.17 : Remediating
2022-07-25T20:32:41.086 [pool-3-thread-2] INFO vCSc : RemediateVM: AuctionAppB0
2022-07-25T20:32:41.098 [pool-3-thread-20] WARN COMM : AuctionAppA0 : All pings failed at 192.168.1.16 : Remediating
2022-07-25T20:32:41.100 [pool-3-thread-20] INFO vCSc : RemediateVM: AuctionAppA0
2022-07-25T20:32:41.100 [pool-3-thread-2] INFO vCSc : DVS Disabled: NetworkLabel VM Network
2022-07-25T20:32:43.116 [pool-3-thread-2] INFO vCSc : Updated AuctionAppB0 to use NetworkLabel VM Network and verified connected state
2022-07-25T20:32:43.119 [pool-3-thread-2] INFO COMM : RemediatedPing AuctionAppB0 : Scanning for IP
2022-07-25T20:32:43.131 [pool-3-thread-2] INFO COMM : RemediatedPing AuctionAppB0 Attempting to Ping at 192.168.1.17
2022-07-25T20:33:07.169 [pool-3-thread-2] ERROR COMM : RemediatedPing AuctionAppB0 : All pings failed at 192.168.1.17
2022-07-25T20:33:07.180 [pool-3-thread-2] INFO vCSc : RemediateVM : Reboot Guest AuctionAppB0
2022-07-25T20:33:07.265 [pool-3-thread-2] INFO COMM : AuctionAppB0 : Scanning for IP
2022-07-25T20:33:07.293 [pool-3-thread-2] INFO COMM : AuctionAppB0 Attempting to Ping at 192.168.1.17
2022-07-25T20:34:09.723 [pool-3-thread-7] INFO COMM : AuctionLB0 Attempting to Ping at 192.168.1.12
2022-07-25T20:34:19.304 [pool-3-thread-9] INFO COMM : AuctionDB0 Attempting to Ping at 192.168.1.19
2022-07-25T20:34:19.756 [pool-3-thread-14] INFO COMM : DS3WebA0 Attempting to Ping at 192.168.1.2
2022-07-25T20:34:19.756 [pool-3-thread-4] INFO COMM : ElasticWebA0 Attempting to Ping at 192.168.1.7
2022-07-25T20:34:34.314 [pool-3-thread-16] INFO COMM : Client0 Attempting to Ping at 192.168.1.1
2022-07-25T20:34:34.323 [pool-3-thread-16] INFO COMM : Pinging Client0 at 192.168.1.1 successful
2022-07-25T20:34:34.323 [pool-3-thread-16] ERROR ST222 : Terminating Early Due to Provision Thread Errors (1)
2022-07-25T20:34:34.330 [pool-3-thread-16] ERROR MAIN : Exception Caught: Terminating Early Due to Provision ThreadErrorsErrorsFound: 1 : exitSetting true
2022-07-25T20:34:34.330 [pool-3-thread-16] INFO MAIN : Email Disabled
2022-07-25T20:34:34.330 [pool-3-thread-16] INFO MAIN : Ending Early
[root@vmmark3 VMmark3]# client_loop: send disconnect: Broken pipe

VMmark: 3.1.1

ESXi : 7.0 u3d 

cloning process is still in progress during this time

Thanks & Regards

Ajay 

[dmorse · Accepted solution]

Hi Ajay,

In your properties file, try uncommenting these lines and setting them higher than the default values:

// int ProvisionPingMaxTries : Default 24 : Specifies the number of ping attempts before failing. Each ping attempt waits 30 seconds.
// ProvisionPingMaxTries = 24
// int ProvisionPingIpSeconds : Default 600 : Specified the number of seconds to wait for a VM to get an IP address.
// ProvisionPingIpSeconds = 600
// int ProvisioningMaxSimultaneousOperations : Default is the number of workload VMs being operated on. This can be used to slow down the deployment requests.
// ProvisioningMaxSimultaneousOperations =

For example:

ProvisionPingMaxTries = 50
ProvisionPingIpSeconds = 1200
ProvisioningMaxSimultaneousOperations = 3

Also, I noticed a couple of other things:

- You are using the same cluster (custom_cluster) as your System Under Test (workload) cluster and client cluster:

// String vCServerVMmark3Cluster : Default empty : Ex vCServerVMmark3Cluster = Cluster1
vCServerVMmark3Cluster = custom_cluster
// String vCServerClientCluster : Default empty : Ex vCServerClientCluster = ClientCluster1 : This is the cluster of hosts running your
// Client VMs and is where provisioning will place new client VMs.
vCServerClientCluster = custom_cluster

This is not supported, please split them out to separate clusters.

All of your VM types (clients and workloads) are being stored on one datastore named "datastore".  This could be overwhelming your storage, especially if it's not all flash.  Can you describe if you have a SAN, how many disks you have, what type they are, confirm it's shared storage, etc.?

Thanks,
David

[Avaakaford]

@dmorse 

Appreciate your response. I'm using different names than i mentioned here .The underlying datastore is NFS( all flash) 

I will do updated to 

ProvisionPingMaxTries = 50
ProvisionPingIpSeconds = 1200
ProvisioningMaxSimultaneousOperations = 3

vCServerVMmark3Cluster = cluster1

vCServerClientCluster = cluster2

Thanks & Regards

Ajay