Loading...

 

OOPS

Your browser doesn't support required HTML5 capabilities.

This demo works best with the latest version of Firefox, Chrome, or Safari.

OOPS

This demo is incomplete or damaged. Please reload the page, or download again:

For VMware partners:
www.vmware.com/go/partnerdemos

For VMware employees:
www.vmware.com/go/demos

OOPS

Something broke.

Visit the VMware Demo Library
to get more demos!

For VMware partners:
www.vmware.com/go/partnerdemos

For VMware employees:
www.vmware.com/go/demos

This is an interactive demo

Drive it with your mouse... or your finger

Use Learn mode to learn the demo

The orange boxes show you where to click

Use Present mode to hide all that when presenting

Hit the F4 key to show notes in a separate window

 

Left Arrow KeyRight Arrow KeyYou can also use the arrow keys to step forward or backward

Shortcuts jump to different parts of the demo

OK, got it!

Demo

VMware Demo Library

Demos can have multiple paths, so the sequence of clicks may differ from this list.

Please wait...
Unsaved changes! You may continue editing other frames before saving.
Save Changes
11.
This demo will walk through the configuration and an example of the new Predictive DRS feature of vSphere 6.5 and vRealize Operations 6.4.

[Click the Configure tab]
164.
Note that pDRS is not currently enabled on this cluster.
[Click the Monitor tab]
375.
Verify that DRS has no recommendations based on the current workloads.
[Click Run DRS Now]
654.
DRS has no recommendations. Now let's go and configure pDRS to see if there are any future contention problems that it can help avoid.
[Click the vRealize Operations Manager browser tab]
812.
There is a workload (ex-vm1) on this cluster that has a fairly common periodic workload pattern. Right now the memory that it is using is low, but we can see in the near future it will spike. Let's go through the steps to enable pDRS and see how it would avoid any future contention caused by this memory increase.
Hover on the graph to see the prediction.

[Click the Collection Notifications to view the vCenter adapters available for configuration]
1535.
[Click to expand the list]
1635.
This is the one vCenter connected to this vR Ops. Let's use this to shortcut to the adapter configurations on the Solutions page.
[Click Santa Clara Datacenter]
1747.
[Click the configure (gear) icon]
1922.
[Click Advanced Settings]
2080.
All you need to do to have vR Ops start predictive data to vSphere DRS is to enable the adapter to send it.
[Click the false value by 'Provide data to vSphere Predictive DRS' and select true]
2217.
[Click Save Settings]
2275.
Verify the certificate for the vR Ops to vSphere connection.
[Click OK]
2474.
[Click OK]
2516.
[Click Close]
2646.
[Click the Collection Notifications]
2856.
[Click to expand the list]
2889.
The adapter is not sending predictive data to vCenter.
[Click OK]
3020.
[Click the vSphere Web Client browser tab]
3269.
Now we need to configure pDRS on the cluster.
[Click the Configure tab]
3315.
[Click Edit...]
3433.
[Click to expand DRS Automation]
3768.
[Click Enable Predictive DRS]
3881.
[Click OK]
3958.
[Click the Monitor tab]
4158.
When we last looked at this cluster there were NO recommendations. However, we know there is a large memory increase that is going to occur in the near future. Let's run DRS again and see how the predictive data will affect DRS.
[Click Run DRS Now]
4526.
The predictive data has given DRS a view into the future and based on that knowledge DRS has determined that a VM needs to be moved to ensure proper performance for all workloads.
(End of demo)