VMware Performance Community
schris14
Contributor
Contributor

VMmark 3.1.1 failed deployment Tile0

I have two unsuccessful attempts at the deployment of Tile0.  Both attempts fail due to an issue with the PrimeClient being able to ping the private network of the deployed VMs.  The log file for the first attempt is in VMmark3-ProvisioningService1.log and config file is VMmark2.properities.txt.  I then updated the VMmark3.properties file and made the following updates and ran the deployment again...which also failed.

ProvisionPingMaxTries = 50

ProvisionPingIPSeconds = 1200

ProvisioningMaxSimultaneousOperations = 5

The log file for that failed attempt is in VMmark3-ProvisioningService2.log and the config file is VMmark3-2.properties.txt.

 

Any help would be appreciated.

0 Kudos
3 Replies
gregwk
VMware Employee
VMware Employee

Can you manually ping the same IP addresses from the prime client?

0 Kudos
schris14
Contributor
Contributor

I can ping the first three addresses ...192.168.50.1-3...which are reserved on the switch, but none of the IP addresses that were assigned to the VMs.

 

I get a "Destination Host Unreachable" error for all of those.

0 Kudos
schris14
Contributor
Contributor

I figured it out...I needed to update the ProvisioningNetworkLabel to point to the Private Network I created for the VM deployment...by default it was set to VM Network.

 

ProvisioningNetworkLabel = Private Network

Tags (1)
0 Kudos