Tuesday, March 21, 2017

Storage IO Control in vSphere 6.5


What is Storage IO Control?

Storage IO Control is used to control the IO usage of virtual machines and gradually enforce pre-defined shares. Shares can be high, medium or low. This feature was introduced in vSphere 4.1 and requires the Enterprise Plus License.

Step 1: Create a datastore. VMFS was used in this case and a datastore called dy (datastore y) was created.



Step 2: SIOC is now managed via IO Filters Providers. You can easily see the filters are registered automatically. You can select the vCenter server and see these filters.


Step 3: To enable SIOC on a datastore, right click on the datastore and enable SIOC.


Step 4: Next, create a virtual machine policy. Click on Home and select VM Storage Policies to create a new SIOC policy.


Step 5: Name the policy and click on Next.


Step 6: Select SIOC and select High, Medium or Low Shares.





Step 7: Now, apply the policy to the virtual machine. Right click on an existing virtual machine  and edit Storage Policies. Select the policy to use and select Apply All.


Thursday, February 9, 2017

Virtual SAN and PowerCLI

Creating a vsan cluster with manual disk claim mode:

new-cluster -name cluster_name -vsanenabled -location datacenter_name

Viewing disk groups:

get-vsandiskgroup

Creating a disk group:

new-vsandiskgroup -vmhost hostname -ssdcanonicalname disk_name -datadiskcanonicalname  disk_name,disk_name

Removing a disk group:

remove-vsandiskgroup -vsandiskgroup disk_group_name -confirm:$false

Removing a disk from a disk group:

remove-vsandisk -vsandisk disk_name -confirm:$false

Adding  a disk to a disk group:

new-vsandisk -canonicalname disk_name -vsandiskgroup disk_group_name

Viewing attributes of a vsan disk:

get-vsandisk -canonicalname disk_name -vmhost esxi_name

Viewing vsan storage policies:

get-spbmstoragepolicy -name policy_name

Creating a vsan storage policy:

new-spbmstoragepolicy -name policy_name -anyofrulesets

Removing a vsan storage policy:

remove-spbmstoragepolicy -storagepolicy policy_name

Exporting a vsan storage policy:

export-spbmstoragepolicy -storagepolicy policy_name -filepath C:\location -force

Importing a vsan storagepolicy:

import-spbmstoragepolicy -storagepolicy policy_name -filepath C:\location

Viewing fault domains:

get-vsanfaultdomain -cluster cluster_name

Creating a vsan fault domain:

new-vsanfaultdomain -name domain_name -vmhost hostname1, hostname2

Removing a vsan fault domain:

remove-vsanfaultdomain -vsanfaultdomain domain_name -confirm:$false

Viewing vsan disk space usage:

get-vsanspaceusage -cluster cluster_name




Friday, January 27, 2017

Virtual SAN 6.5 Licensing


Virtual SAN 6.5 Licensing


6.5 vs 6.2


http://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vsan/vmware-vsan-65-licensing-guide.pdf

Thursday, January 12, 2017

D.R.S. 6.5 Enhancements

D.R.S. Enhancements in vSphere 6.5

Predictive DRS

Disabled by default, predictive DRS works together with VROPS to make DRS proactive instead of
reactive.The way that it works, VROPs computes and forecasts vm utilization (both cpu and ram) based on data received from the vCenter server. In turn, DRS receives the forecasted metrics 60 minutes ahead of time in order to balance the loads prior to contention.



VM distribution, Memory Metric for Load Balancing and CPU-Overcommitment.

VM distribution is used to prevent less vms from restarting due to a failure by distributing the
number of vms more evenly. If DRS detects a severe performance inbalance, it will correct the
performance at the expense of the even distribution of vms.

Memory Metric for Load Balancing: By default, DRS uses active memory + 25% as the primary
metric. This new feature dictates that consumed memory should be used intead.

CPU over-commitment: Use this option to enforce a maximum vcpu vs lcpu ratio. Once the limit is reached, no new vms are allowed to power on on that particular host. According to the documentation, 500 is equals 5 vcpus x 1 lcpu.


Sunday, December 25, 2016

vCenter Migration from Windows to Linux

Step 1:  Download the vCenter Appliance and copy the Migration Assistant Tool folder to the windows vCenter. Inside the folder you have the executable. Double click on the VMware-Migration-Assistant script.




Step 2:  Launch the appliance installer and double click on the Migrate icon to start Stage 1. Go through the wizard.












Step 3:  Start Stage 2 of the migration and verify the new vCenter once the operation is finished.










Friday, December 23, 2016

vCenter Appliance Partitions


From:
http://www.virtuallyghetto.com/2016/11/updates-to-vmdk-partitions-disk-resizing-in-vcsa-6-5.html

Vimtop Main Options

What is vimtop?  Vimtop is a command found on the vCenter appliance that can give you lots of performance related information. Just run vimtop without any options to run it interactively. This gives you cpu, memory and process information.


Vimtop has an "h" option for help. Press Escape once you are done looking at these options.


Vimtop has a "k" option for disk related information. Look for Read and Write operations.


Vimtop has an "o" option for network related information. Look for dropped packets.


Final Note:

"P" option = pauses the screen
"S" option = sets the refresh rate in seconds
"Q" option = quit vimtop