virtualg_uk's Accepted Solutions

Enterprise does include custom dashboard creation. Please see the link provided above which shows the difference between Standard, Advanced and Enterprise. Review the entry for "Customizable Dashboards, Reports and Views" in the table to see that Enterprise does include this feature.

Hi Dana, Welcome to the vRealize Operations Manager forum! Can I ask which license you have for vROps? Report creation is only available in Advanced and Enterprise versions: https://blogs.vmware.com/management/2016/12/vrops-editions-series-overview.html vROps Editions: Series Overview - VMware Cloud Management Kind regards, Graham

Standard licensing limits you to 75 protected VMs per site. See > Site Recovery Manager | Disaster Recovery Software | VMware Enterprise has no license limit however there are technical limits as described here (depends on protection type, etc) > https://configmax.vmware.com/guest  (Select SRM on left)

Hello and welcome! Can you navigate to Administration > Certificates Then delete the old certificate Once the certificate is gone, go back to the vCenter solution/adapter in vROps and test connection and save. If this isn't possible in the UI (Sorry I forget if you can do this in 6.2) Then try this KB: VMware Knowledge Base Ensure you have a good rollback point before carrying this out. A side note is that 6.2 is no longer supported by VMware so you may wish to upgrade so they can help you with future issues https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/support/product-lifecycle-matrix.pdf

I can do one better! - Here is the official documentation, it's one or two versions behind vRealize Operations Manager 6.0.1 Documentation Center Wait and Cancel Cycle The wait cycle setting helps you adjust for sensitivity in your environment. The wait cycle for the alert definition goes into effect after the wait cycle for the symptom definition results in a triggered symptom. In most alert definitions you configure the sensitivity at the symptom level and configure the wait cycle of alert definition to 1. This configuration ensures that the alert is immediately generated after all of the symptoms are triggered at the desired symptom sensitivity level. The cancel cycle setting helps you adjust for sensitivity in your environment. The cancel cycle for the alert definition goes into affect after the cancel cycle for the symptom definition results in a cancelled symptom. In most definitions you configure the sensitivity at the symptom level and configure the cancel cycle of alert definition to 1. This configuration ensures that the alert is immediately cancelled after all of the symptoms conditions disappear after the desired symptom cancel cycle.

Hello and welcome! If you want to change the VM state back to what it was when you created the snapshot, you need to select that snapshot in the UI and select "Revert to" This will obviously delete data because all changes made since this snapshot will be deleted. You can then choose to delete the snapshot or leave the existing one in place. I've attached a screenshot to show this in the HTML5 vSphere Client accessible via https://vcenter-server-fqdn/ui Hope this helps!

Take for example a VMDK that has a storage policy of FTT=1 This means that there will be 2x copies of the VMDK and a witness component VMDK 1 VMDK 2 WITNESS Total = 3 "components" If you lose one of these components (disk failure, disk group failure, host failure etc), then there are over 50% of the components available so the VMDK remains accessible. Example: You lose VMDK copy 2. This means that 2 out of 3 components are still available  = 66% = More than 50% If you lose any two components, for example VMDK1 and WITNESS then the VMDK object will no longer be accessible since <50% of components are available (33%) The witness components are automatically created, you do not need to worry too much about them.

Sounds like this check is just looking at the Distributed Switch and alarming because there are mixed speed NICs. As long as the vSAN port is using those 10G NICs (even for failover) then you should be in a supported configuration. Feel free to upload a screenshot(s) of your Distributed Switch configuration.

Ideally you would want to use NIOC when teaming traffic like you suggest. Do you have a license to use the distributed switch to take advantage of that feature? (Enterprise Plus / vSAN) Also, when you mention FT, are you referring to the Fault Tolerance vSphere feature or simply (N+1) for up-link availability?

You can restart VCSA services via shell: Stopping, starting, or restarting VMware vCenter Server Appliance 6.x services (2109887) | VMware KB See the last section on that KB article. Also, you could try to reboot the VCSA to clear out anything that might be causing this?

You could try the XtremIO management back from Blue Medora https://solutionexchange.vmware.com/store/products/blue-medora-mp-for-dell-emc-xtremio There is also a management pack from Dell EMC which works with most Dell EMC storage solutions such as Avamar, Isilon, EMC RecoverPoint for Virtual Machines, ScaleIO, Unity, Unity/VSA, VNX, VNXe, VMAX, VMAX All Flash, VPLEX and XtremIO Cloud Management Marketplace | Solution Exchange All Hitachi ones are listed here: Hitachi Data Systems | Solution Exchange

This post from depping‌ should help work out the different between %VMWAIT and %WAIT: http://www.yellow-bricks.com/2012/07/17/why-is-wait-so-high/ %VMWAIT is a derivative of %WAIT, however it does not include %IDLE time but does include %SWPWT and the time the VM is blocked for when a device is unavailable. That kind of reveals immediately why  %WAIT seems extremely high, it includes %IDLE! Another thing to note is the %WAIT for a VM is multiple worlds collided in to a single metric. Let me show you what I mean: The blog post above should go a long way to help explain.

The vSAN licenses you get with VMUG Advantage are 6 x 1 CPU licenses so you would be limited to 3 x 2CPU hosts. I've just checked my portal to clarify and this is still the case for vSAN and vSphere Hope this helps

It's definitely not supported: https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=vsanio&productid=39500&vcl=true I don't see any of the 6.5 Dell Ready Nodes using this controller either yet. You would need to contact the Vendor (Dell) to see when it might be on the HCL

To be perfectly honest, it depends how active the CPUs are within those guest VMs. You are right to over-commit CPU cores though. ESXi handles this very well. What I would do for a BASIC answer is add up all the "GHz" for the VMs you want to run, so: 16 VMs x 2 cores at 2.4GHz each = 76.8GHz Then Add up the GHz available on the ESXi server(s) 2x 4x 2.4GHz = 19.2GHz So you would have 19.2GHz available on the ESXi host but you would want to run 76.8GHz on that ESXi hosts. A rough calculation means that on average, VMs would need to be running at less than 25% CPU for this to work without contention 76.8GHz / (100/25) = 19.2 GHz This is VERY approximate but should give you an idea of what's possible. Hope this help.

Yes many high end servers will utilise a single internal SD or USB for the ESXI installation, this is the norm now unless you can boot from SAN etc. The advantage is that there are no spinning disks to fail and SD/USB is far cheaper. When ESXi loads, it loads into memory so having a disk there is just a waste of space and money. Some systems (Dell) support redundancy on the SD cards, so you can put in 2 SD cards for the ESXi install and it will mirror one to the other. If one fails it will use the other. If you dont have this and SD fails, ESXi will still continue running until the next reboot. ESXi is very quick to install again if needed anyway. For SQL server performance, depending on how many IOPS you require / how busy the server is, NAS can be a good option, it generally depends on how many IOPS the NAS can deliver to the application (This is determined by how many disks you have in the NAS and their type etc) See here for a calculator: Disk RAID and IOPS | The Cloud Calculator I would vary rarely recommend standard local disk configurations for anything as you lose HA and vMotion abilities between hosts in a cluster. SAN can have better performance but it all depends on the bandwidth available to it and the IOPS you require, for small DBs NAS can work well.