sfit1
Contributor
Contributor

VMmark result marked as non compliance

Hi community,

 

Can anyone help me to see why the run marked as non compliance? Attached is the graph file. What can I do to make it compliance? I pretty sure I followed the VMmark guide correctly..

0 Kudos
8 Replies
sfit1
Contributor
Contributor

Hi, 

 

I am tracing the log files and found something that might be the cause, but not sure. See below:

(From VMmark3-STAX_Job_3_User-Parsed.log)

20210714-13:40:06 Info Service: Request Cluster Mapping Info : vCServerVMmark3Cluster (This May Take A While)
20210714-13:40:08 Info VMs In Cluster : ['DS3WebA0', 'Client0', 'AuctionLB0','ElasticLB0', 'DS3WebC0', 'AuctionAppA0', 'DS3WebB0', 'AuctionNoSQL0', 'ElasticAppA0', 'AuctionWebA0', 'ElasticAppB0', 'ElasticDB0', 'AuctionMSQ0', 'DS3DB0', 'AuctionDB0', 'ElasticWebA0', 'ElasticWebB0', 'AuctionAppB0','Standby0', 'PrimeClient', 'AuctionWebB0']
20210714-13:52:48 Info Warning: Cluster VM Mapping And Resources returned Warnings :::Only VMware pre-approved Non-VMmark VMs are compliant. :::All other VMs will cause this run to be non-compliant.:::InvalidResources 0:::PoweredOnErrors 0 :::Non-VMmark VMs Found 15:::See VC-ClusterMapping.txt
20210714-13:52:48 Info VMmark3Msg : Warning: Cluster VM Mapping And Resourcesreturned Warnings :::Only VMware pre-approved Non-VMmark VMs are compliant. :::All other VMs will cause this run to be non-compliant.:::InvalidResources 0:::PoweredOnErrors 0 :::Non-VMmark VMs Found 15:::See VC-ClusterMapping.txt

 

 

VMmark3 ClusterMapping: vCServerVMmark3Cluster

ClusterMapping Iteration 1

Host: 192.168.101.161

    VM[0] DS3WebA0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[1] Client0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[2] AuctionLB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[3] ElasticLB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[4] DS3WebC0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[5] AuctionAppA0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[6] DS3WebB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[7] AuctionNoSQL0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[8] ElasticAppA0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[9] AuctionWebA0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[10] ElasticAppB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[11] ElasticDB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[12] vCLS (3) : Tile -1 : TargetHost Unknown : Invalid VM Naming - Skipping

    VM[13] vCLS (2) : Tile -1 : TargetHost Unknown : Invalid VM Naming - Skipping

Host: 192.168.101.162

    VM[0] AuctionMSQ0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[1] DS3DB0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[2] AuctionDB0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[3] ElasticWebA0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[4] ElasticWebB0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[5] AuctionAppB0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[6] Standby0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[7] PrimeClient : Tile -1 : TargetHost Unknown : Invalid VM Naming - Skipping

    VM[8] VMware vCenter Server : Tile -1 : TargetHost Unknown : Invalid VM Naming - Skipping

    VM[10] AuctionWebB0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[11] vCLS (1) : Tile -1 : TargetHost Unknown : Invalid VM Naming - Skipping

Cluster Mapping Iteration 1 Ending Normally : TaskErrors 0 : TaskSuccess 8

ClusterMapping Iteration 2

Host: 192.168.101.161

    VM[0] DS3DB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[1] AuctionDB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[2] Client0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[3] AuctionLB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[4] ElasticLB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[5] AuctionAppA0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[6] AuctionNoSQL0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[7] AuctionAppB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[8] ElasticAppA0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[9] ElasticAppB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[10] ElasticDB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[11] vCLS (3) : Tile -1 : TargetHost Unknown : Invalid VM Naming - Skipping

    VM[12] vCLS (2) : Tile -1 : TargetHost Unknown : Invalid VM Naming - Skipping

Host: 192.168.101.162

    VM[0] AuctionMSQ0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[1] DS3WebB0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[2] DS3WebA0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[3] ElasticWebA0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[4] DS3WebC0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[5] ElasticWebB0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[6] Standby0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[7] PrimeClient : Tile -1 : TargetHost Unknown : Invalid VM Naming - Skipping

    VM[8] VMware vCenter Server : Tile -1 : TargetHost Unknown : Invalid VM Naming - Skipping

    VM[10] AuctionWebB0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[11] AuctionWebA0 : Tile 0 : TargetHost 192.168.101.161 : Requesting VMotion

    VM[12] vCLS (1) : Tile -1 : TargetHost Unknown : Invalid VM Naming - Skipping

Cluster Mapping Iteration 2 Ending Normally : TaskErrors 0 : TaskSuccess 9

ClusterMapping Iteration 3

Host: 192.168.101.161

    VM[0] AuctionMSQ0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[1] Standby0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[2] DS3WebB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[3] ElasticWebA0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[4] DS3WebA0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[5] DS3DB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[6] AuctionDB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[7] Client0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[8] AuctionLB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[9] ElasticLB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[10] DS3WebC0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[11] AuctionAppA0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[12] AuctionNoSQL0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[13] ElasticWebB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[14] AuctionAppB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[15] ElasticAppA0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[16] AuctionWebB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[17] AuctionWebA0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[18] ElasticAppB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[19] ElasticDB0 : Tile 0 : TargetHost 192.168.101.161 : CorrectHost

    VM[20] vCLS (3) : Tile -1 : TargetHost Unknown : Invalid VM Naming - Skipping

    VM[21] vCLS (2) : Tile -1 : TargetHost Unknown : Invalid VM Naming - Skipping

Host: 192.168.101.162

    VM[0] PrimeClient : Tile -1 : TargetHost Unknown : Invalid VM Naming - Skipping

    VM[1] VMware vCenter Server : Tile -1 : TargetHost Unknown : Invalid VM Naming - Skipping

    VM[3] vCLS (1) : Tile -1 : TargetHost Unknown : Invalid VM Naming - Skipping

Cluster Mapping Iteration 3 Ending Normally : TaskErrors 0 : TaskSuccess 0

Resource Review:

  VM[1] DS3WebA0 : vCPUS 1 : vMEM 4096 : Valid Resource Allocation

  VM[2] Client0 : vCPUS 12 : vMEM 20480 : Valid Resource Allocation

  VM[3] AuctionLB0 : vCPUS 2 : vMEM 4096 : Valid Resource Allocation

  VM[4] ElasticLB0 : vCPUS 1 : vMEM 4096 : Valid Resource Allocation

  VM[5] DS3WebC0 : vCPUS 1 : vMEM 4096 : Valid Resource Allocation

  VM[6] AuctionAppA0 : vCPUS 4 : vMEM 14336 : Valid Resource Allocation

  VM[7] DS3WebB0 : vCPUS 1 : vMEM 4096 : Valid Resource Allocation

  VM[8] AuctionNoSQL0 : vCPUS 2 : vMEM 16384 : Valid Resource Allocation

  VM[9] ElasticAppA0 : vCPUS 2 : vMEM 8192 : Valid Resource Allocation

  VM[10] AuctionWebA0 : vCPUS 2 : vMEM 8192 : Valid Resource Allocation

  VM[11] ElasticAppB0 : vCPUS 2 : vMEM 8192 : Valid Resource Allocation

  VM[12] ElasticDB0 : vCPUS 2 : vMEM 8192 : Valid Resource Allocation

  VM[13] AuctionMSQ0 : vCPUS 2 : vMEM 4096 : Valid Resource Allocation

  VM[14] DS3DB0 : vCPUS 8 : vMEM 32768 : Valid Resource Allocation

  VM[15] AuctionDB0 : vCPUS 2 : vMEM 8192 : Valid Resource Allocation

  VM[16] ElasticWebA0 : vCPUS 2 : vMEM 4096 : Valid Resource Allocation

  VM[17] ElasticWebB0 : vCPUS 2 : vMEM 4096 : Valid Resource Allocation

  VM[18] AuctionAppB0 : vCPUS 4 : vMEM 14336 : Valid Resource Allocation

  VM[19] Standby0 : vCPUS 1 : vMEM 2048 : Valid Resource Allocation

  VM[20] AuctionWebB0 : vCPUS 2 : vMEM 8192 : Valid Resource Allocation

Total SUTs: 2

Total_Powered_On_VMs : 35 : Warning, Non-VMmark VMs detected.  Only VMware pre-approved Non-VMmark VMs are compliant.  All other VMs will cause this run to be non-compliant.

Number_Of_VMs_With_Invalid_Resources : 0

Number_Of_NonVMmark_VMs : 15

Cluster Mapping Ending Normally

0 Kudos
RebeccaG
VMware Employee
VMware Employee

Hi sfit1,

From looking at the VMmark3-Graphs.html, all the workloads are passing except for WeathervaneAuction and WeathervaneElastic which both had QoS failures. VMmark appears to be configured correctly, so that is good.

The most common cause of QoS failure like this is resource contention in the cluster which is running VMmark. In the VMmark User's Guide, check the "VMmark Hardware Requirements" section to make sure your hardware supports the load that VMmark is creating. Storage that is too slow is a very common cause of QoS failure.

VMmark is supposed to be run on two clusters; the VMmark cluster which hosts VMmark VMs and the Client cluster which hosts Clients including the Prime Client. I see you are running both on one cluster which can increase the load. If you move the Client0, Prime Client and vCenter Server VMs to a different cluster, that would give you a better chance to pass QoS at 1 tile. 

The vCLS VMs warnings are OK and can be ignored. The presence of these non-VMmark VMs is not why your run is non-compliant. The QoS failure is what makes it non compliant.

If you would like me to take a closer look, please zip your results folder for the VMmark run and upload to the forum.

 

0 Kudos
sfit1
Contributor
Contributor

Hi Rebecca,

 

Thanks for your reply. I am pretty sure my Hardware meet the requirements. I have two host which is using a single socket processor of Intel Xeon Gold 5220R with 192 GB of RAM. I have a FC SAN of 10 TB which consist of 8 x 2 TB 10K RPM HDD, running at RAID6. Each host connected to this SAN using 16Gbps Fiber cable.

 

I am going to setup another ESXi host and build another Cluster and add it in, then migrate Client0, Prime Client and vCenter Server VM into it and rerun the test.

 

I attached the complete result file except vcsupport-20210714-173409.tgz (this file size is 167MB which exceed the limit) here.

 

Tags (1)
0 Kudos
sfit1
Contributor
Contributor

Hi,

 

So I moved client0, primeclient and vcenter server vm to another host which belongs to different cluster and rerun the test. Result still says non compliance. Any suggestion to correct this?

0 Kudos
RebeccaG
VMware Employee
VMware Employee

Hi sfit1, thank you for providing more information about your testing environment and the results .zip.

Unfortunately, I believe your storage latency and/or bandwidth is too slow to support the VMmark workloads. VMmark typically requires all-flash storage, or a hybrid (flash and HDD) vSAN setup. You can see which storage was used for published VMmark results at https://www.vmware.com/products/vmmark/results3x.html.  

You can see in VMmark3-Graphs.html that spikes in QoS latency occur at the beginning of the run. This happens for all workloads except vMotion which is not storage-dependent. This probably indicates that storage cacheing is occurring at the beginning of the run. By later in the run once most hot data is cached, the QoS is much lower. But the slow performance at the beginning still causes VMmark to fail QoS requirements.

Unfortunately you will need to use a faster storage solution to test this environment. If you can add some SSDs to your FC SAN and place the Weathervane VMs there, that would be a good place to start.

0 Kudos
sfit1
Contributor
Contributor

Hi Rebecca,

You probably right. I have 2 SSD used for caching in the FC SAN. Let me see what can I do for this environment.

 

Many thanks for the advise.

Tags (1)
anilspp
Enthusiast
Enthusiast

Thanks for all the info.

0 Kudos
mburger
Contributor
Contributor

Thanks for this information very helpful

0 Kudos