vThinkBeyondVM's Posts

Free version of ESXi comes with evaluation 60 days license, after that it will stop working. Hence you need to have ESXi license as well. Min. 2 ESXi hosts, 1 Virtual Center, 1 Virtual SAN. ... See more...
Free version of ESXi comes with evaluation 60 days license, after that it will stop working. Hence you need to have ESXi license as well. Min. 2 ESXi hosts, 1 Virtual Center, 1 Virtual SAN. Once you create HA cluster, you no need to use vCenter as HA is dependent on ESXi not on vCenter, vCenter is only used for management purpose but again vSAN should have its own licenses. Better to have all 3 paid with basic licenses. Ref-https://www.vmware.com/files/pdf/vCloud-Suite-Pricing-Packaging-Whitepaper.pdf
If you want to locate logs from ESX from storage perspective : Location is : 1. SSH to Host 2. Goto /var/log directory 3. You will find vmkernel.log file, which will have all storage rela... See more...
If you want to locate logs from ESX from storage perspective : Location is : 1. SSH to Host 2. Goto /var/log directory 3. You will find vmkernel.log file, which will have all storage related logs . Along with that you can find SIOC(Storage IO control ) i.e storagerm.log, FDM related fdm.log (fault domain manager) + several other components log under the same directory. Hope this helps
Mr Vmware,   If you are talking about storage related component such as SPS,SMS,SPBM (features from VMware vCenter server). Log location can be found in below directories.    From VCVA (lin... See more...
Mr Vmware,   If you are talking about storage related component such as SPS,SMS,SPBM (features from VMware vCenter server). Log location can be found in below directories.    From VCVA (linux VC): /var/log/vmware/vpx/ SPS i.e storage profiles: /var/log/vmware/vpx/sps .
Hi Friends,   I have this doubt, Which Qdepth is throttled by SIOC ? As we know there are queue depth maintained at each level i.e. GOS queue depth, HBA queue, Storage processor port q depth... See more...
Hi Friends,   I have this doubt, Which Qdepth is throttled by SIOC ? As we know there are queue depth maintained at each level i.e. GOS queue depth, HBA queue, Storage processor port q depth etc.
How exactly SIOC is leveraged by SDRS from core technical perspective?
Hi Escapem2,    Yes it should be possible. There will not be any issue if you use two vendors for a datacenter or 1 VC from replication perspective. You will have make sure all the configurati... See more...
Hi Escapem2,    Yes it should be possible. There will not be any issue if you use two vendors for a datacenter or 1 VC from replication perspective. You will have make sure all the configuration requirements are satisfied. In VMware replication, you will have to install vSphre replication appliance, same is manged by using web client. On the other hand Veem replication has their on console where you would add your ESXi or VC. Both these replication technologies are at VM level, it should not have any issue until you choose different set of VMs for setting replication job. (There will not be any conflict) From management perspective VMware replication helps as it is managed by same web client which manages entire VMware infrastructure. But there will be some difference from feature set perspective. I suggest you to first drill down why customer would like to go for VMware replication and take proper decision. But you can use both together. Plz refer: http://www.yellow-bricks.com/2012/09/17/back-to-basics-install-configure-and-use-vsphere-replication/ http://www.vmwarearena.com/2013/07/adding-esxesxi-host-or-vcenter-server.html KB1522: P.S.: Award points if it is useful/correct.
Yes, I agree with Sajal. I have done this myself several times. -Vikas
It is easy to know all cluster configuration by using VC SDK API as Duncan said. API details as follows : API to call: ReconfigureComputeResource_Task Above API takes one parameter i.e. ... See more...
It is easy to know all cluster configuration by using VC SDK API as Duncan said. API details as follows : API to call: ReconfigureComputeResource_Task Above API takes one parameter i.e. ClusterConfigSpecEx Once you retrieve above parameter, it gives you all the details about cluster. You can know whether HA/DRS/vSAN/DPM is enabled or not/ Ref-:VMware vSphere API Reference
The slot size is only relevant for the "Host Failures Cluster Tolerates" setting.
As per vSphere 5.5 Fault Tolerance maximums Virtual disks 16 Virtual CPUs per virtual machine 1 RAM per FT VM 64GB Virtual machines per host 4
Even I am really late to answer but some how I come across this query and thought to answer.: You can place the original (or Primary virtual machine). You have full control with DRS or vMoti... See more...
Even I am really late to answer but some how I come across this query and thought to answer.: You can place the original (or Primary virtual machine). You have full control with DRS or vMotion to assign it to any node. The placement of the Secondary, when created, is automatic based on the available hosts. But when the Secondary is created and placed, you can vMotion it to the preferred host. Regards Vikas
Yes, Nagarajan, You can enable FT without DRS. However, you could leverage DRS for FT as "vTagion" has specified. -FT can be enabled on the VM which is in compute cluster and HA should be e... See more...
Yes, Nagarajan, You can enable FT without DRS. However, you could leverage DRS for FT as "vTagion" has specified. -FT can be enabled on the VM which is in compute cluster and HA should be enabled on that cluster. -DRS is not mandatory. For more details on FT requirements : Ref- http://pubs.vmware.com/vsphere-51/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-51-availability-guide.pdf Section: Fault Tolerance Checklist. P.S.: Plz award points if it is useful.
              I agree with Weinstein5, there is NO any tool which captures all these parameters. However, we need to explore VC SDK APIs to know these details. Probably we may get it. I will try ... See more...
              I agree with Weinstein5, there is NO any tool which captures all these parameters. However, we need to explore VC SDK APIs to know these details. Probably we may get it. I will try in my spare time and get back to you. At the moment, you would be only dependent on event/task that are being displayed when vMotion is going on. -Vikas Message was edited by: vickyvision2020
I am too late to share my insight but some how I come across this post. If anybody want to show DRS demo in your existing setup, please follow below suggestions DRS offers you below features ... See more...
I am too late to share my insight but some how I come across this post. If anybody want to show DRS demo in your existing setup, please follow below suggestions DRS offers you below features : -Set the DRS in fully automatic mode with aggressive threshold. -Initial placement: when you add new VM to cluster it automatically place on the appropriate host. You need not to select particular host to place the same. This you could show. - You have DRS affinity and anti-affinity rules : Set DRS VM-VM affinity rule on the VMs in a cluster, it is mean that all VMs should be on one host. DRS would automatically vMotion all the VMs to either host. In this way use all types of rules and show how DRS behaves. -Remove this rule, DRS would automatically balance the load. - You can enable DPM and show how underutilized host would be placed in stand by mode (for this you need to enable IPMI/WoL) Hope this helps.
Yes, absolutely you can do these operations without any outage. If you are doing this by using UI (VI client or Web client)   1. First vMotion all the VMs from other 4 old host to a old host ... See more...
Yes, absolutely you can do these operations without any outage. If you are doing this by using UI (VI client or Web client)   1. First vMotion all the VMs from other 4 old host to a old host where compellent storage array access available.         -Make sure old host with compellent access has enough CPU/Memory so that all ON VMs can be placed.         - Also make sure all old host have shared storage array except compellent (that is available on one old host), I think it is there already.   2. Now storage vMotion all the VMs to old host compeleent storage array.        -This can be done using script or manually   3. Remove old host (with compellent ) from older vCenter server.   4. Create one cluster on new 5.5 vCenter and add all host (1 old + 2 new ) to cluster.   5. Enable DRS in fully automated mode with aggressive threshold. and make sure vMotion network is configured properly. 6. Put old host into maintenance mode. DRS will automatically vacate the old host and balance the load on other new hosts as well. 7. Wait for all the vMotion operation to complete, old host wud be now in Maintenace mode. 8. Remove old host from cluster and exit from MM and remove from new vCenter.   Note: -You can configure VMware HA/FT on the cluster to avoid any possible failure (Make sure you satisfy HA/FT requirement) -If possible explore XVMotion, which helps to relocate VM even there is no shared datastore. -If you want to use script to do vMotion/SVMOtion, get back to me. -Let me know if you have any doubt Plz award points if this is useful.
As per the current design for 5.1 & 5.5, even though you disable DRS, DRS rules are still available but would be disabled too. Once you enable DRS on the same cluster, these rules would be enable... See more...
As per the current design for 5.1 & 5.5, even though you disable DRS, DRS rules are still available but would be disabled too. Once you enable DRS on the same cluster, these rules would be enabled as well. Also, if you create VM-Host affinity/anti-affinity hard (must) rule, even though DRS is disabled, this rule will be remain enabled as HA would honor this rule. There is no way you can disable that rule once the DRS is disabled. Better way is to remove or disable such rule before DRS is getting disabled.
Most probably, there are rules those are conflicting with each other. Check if you have multiple VMs those are part of more than 1 rules or hosts are part of more than 2 rules. If there is rule... See more...
Most probably, there are rules those are conflicting with each other. Check if you have multiple VMs those are part of more than 1 rules or hosts are part of more than 2 rules. If there is rule conflict DRS generates this fault: "No Compatible Hard Affinity Host"
Yes as DRS is not available. VMs would not be migrated automatically. You will have to manually evacuate hosts to get ready for maintenance mode.
It requires : . You need 'System.Read' privileges to complete the requested operation.