dmorse's Posts

The problem is the same: ProvisioningSource = tile0 and ProvisioningNumTiles = 1 are incompatible (even though you commented out ProvisioningNumTiles, 1 is the default value).  You have already provisioned 1 tile. //   For provisioning Tile 1 - N, Tile0 is used as the source and this should be the keyword 'tile0' : Ex 'ProvisioningSource = tile0' ProvisioningSource = tile0 // int ProvisioningNumTiles : 1 or more tiles : Default 1 : If ProvisioningSource is a template this is automatically set to 1 tile. //  ProvisioningNumTiles = 1   You can either try a benchmark run with 1 tile, or change ProvisioningNumTiles to 2 or higher to create more tiles.  If you do decide to create/provision more tiles, be aware you will need to change these lines from Standby/Servers = Standby0 AuctionWebA/Servers = AuctionWebA0 AuctionWebB/Servers = AuctionWebB0 etc.   to (for example): Standby/Servers = Standby0,Standby1 AuctionWebA/Servers = AuctionWebA0,AuctionWebA1 AuctionWebB/Servers = AuctionWebB0,AuctionWebB1  

all the components are retails SKUs. Can i get exact recipe that you are using , i will try same from my end . HPE : SSP/SPP (Firmware ) ESXi OS : ESXi Image & source path Ajay, As @jamesz08 mentioned above, there isn't a recipe per se. HPE BIOS/System ROM: 1.20 ESXi OS: ESXi 7.0 U3 Apr 2023  Also, please try using an unmodified VMmark3 template (in other words, do not install a specific version of VMware Tools), just to remove that as a potential variable. Thanks, David

Hi Stephen, Thanks for providing your full results directory.  I was able to reproduce and resolve the issue by removing an error check in the ParsePowerData script.  Here's how: On the Prime Client VM: Make a backup copy of /root/VMmark3/tools/VMmark3-ParsePowerData.pl (i.e. /root/VMmark3/tools/VMmark3-ParsePowerData-backup.pl) Open /root/VMmark3/tools/VMmark3-ParsePowerData.pl with a text editor Comment out lines 150 through 153 by adding a # (pound sign) at the beginning of each line (as shown below):     Save and close the file Then try another run.  You should hopefully see a *-Esxtop.csv output file in your Results directory that looks like this: (PDH-CSV 4.0) (UTC)(0), \\hostname\Power\Power Usage Now Watts 12/12/2022 19:08:04, 225 12/12/2022 19:08:25, 246 12/12/2022 19:08:45, 235 12/12/2022 19:09:06, 241 12/12/2022 19:09:27, 292 12/12/2022 19:09:48, 262 12/12/2022 19:10:09, 299

Hi @jiangjing123455 , I am glad to see you were able to scale up to this level. 1 compliance issue is very low; have you tried more than one run?  It's quite possible that rerunning may produce a compliant run. You mentioned you have SAN storage for the workload VMs; is it all-flash? You may want to consider grouping the VMs onto separate LUNs, since some are more I/O intensive, and others are more latency sensitive. It sounds like the benchmark is running correctly, so now it is just a matter of performance tuning your environment.  Reviewing the published VMmark results (https://www.vmware.com/products/vmmark/results3x.0.html), specifically the "Storage Notes" section of the PDFs that use SAN and vSAN storage, should help here.

Something is definitely wrong -- there should not be any errors when creating tile1 VMs, and you should not have to do a partial creation of ElasticApp VMs.  Please do the following: Delete all tile1 VMs (including client1) from vCenter Re-run the provisioning for tile1 (make sure you follow all the steps in the User's Guide from 'Creating Additional VMmark Tiles (Tiles 1 through n)' in the User's Guide) After it finishes, please do the following: Change to the directory of the provisioning output, i.e. 'cd /root/VMmark3/provisioning-output' Create a .zip of the directory, i.e. 'zip -r vmmark3-tile1-output.zip vmmark3-tile1-output' Attach that .zip to this thread Thanks!

For some reason, all of your tile1 VMs' hosts files are wrong: they are pointing to tile0 IP addresses.  For example, AuctionLB1_hosts.txt shows me that for the AuctionLB1 VM, its /etc/hosts files are pointing to these tile0 VMs: 192.168.1.7 ElasticWebA0 ElasticWebA 192.168.1.1 Client0 Client 192.168.1.11 ElasticDB0 ElasticDB 192.168.1.2 DS3WebA0 DS3WebA 192.168.1.16 AuctionAppA0 AuctionAppA 192.168.1.14 AuctionWebA0 AuctionWebA 192.168.1.8 ElasticWebB0 ElasticWebB 192.168.1.9 ElasticAppA0 ElasticAppA 192.168.1.18 AuctionNoSQL0 AuctionNosql 192.168.1.13 AuctionMSQ0 AuctionMSQ 192.168.1.6 ElasticLB0 ElasticLB 192.168.1.3 DS3WebB0 DS3WebB 192.168.1.17 AuctionAppB0 AuctionAppB 192.168.1.5 DS3DB0 DS3DB 192.168.1.19 AuctionDB0 AuctionDB 192.168.1.15 AuctionWebB0 AuctionWebB 192.168.1.10 ElasticAppB0 ElasticAppB 192.168.1.4 DS3WebC0 DS3WebC 192.168.1.20 Standby0 Standby While there are entries for Tile1 VMs at the bottom of the file, they don't have the correct aliases.  I would have expected to see only these lines: 127.0.0.1 Client1.vmmark3.eng.vmware.com localhost localhost4 localhost4.localdomain4 Client1 192.168.1.50 PrimeClient 192.168.1.28 ElasticWebB1 ElasticWebB 192.168.1.27 ElasticWebA1 ElasticWebA 192.168.1.26 ElasticLB1 ElasticLB 192.168.1.31 ElasticDB1 ElasticDB 192.168.1.38 AuctionNoSQL1 AuctionNosql 192.168.1.33 AuctionMSQ1 AuctionMSQ 192.168.1.21 Client1 Client 192.168.1.40 Standby1 Standby 192.168.1.24 DS3WebC1 DS3WebC 192.168.1.23 DS3WebB1 DS3WebB 192.168.1.22 DS3WebA1 DS3WebA 192.168.1.32 AuctionLB1 AuctionLB 192.168.1.39 AuctionDB1 AuctionDB 192.168.1.30 ElasticAppB1 ElasticAppB 192.168.1.29 ElasticAppA1 ElasticAppA 192.168.1.37 AuctionAppB1 AuctionAppB 192.168.1.36 AuctionAppA1 AuctionAppA 192.168.1.25 DS3DB1 DS3DB 192.168.1.35 AuctionWebB1 AuctionWebB 192.168.1.34 AuctionWebA1 AuctionWebA Could you delete all the tile1 VMs (all VMs ending in 1, including Client1), and re-run the provisioning to re-create them? Hopefully then they will have valid /etc/hosts files that point to tile1 instead of tile0.

Here are commands to zip up all the hosts files, which won't be very large at all.  Please attach that to this thread. cd /root/VMmark3/results/Results_20210913185815_Test2/configfiles/ zip hostfiles.zip *hosts.txt  

Hi @CSCM , unfortunately this STAX log is not enough to troubleshoot why the run failed. Could you please zip and upload the contents of the primeclient results directory (/root/VMmark3/results/Results_20210913185815_Test2/) and post a link to it?  Thanks!