Interview Questions.

Q1. If We Have Configured Some Rules (affinity Or Anti-affinity) In Drs The Will Those Rules Work If We Disable Drs On A Cluster?

Yes policies may be in have an effect on even if we disable DRS with out deleting the policies first.

Q2. How Many Automation Levels Are There For A Vm In Respect To Drs? Can Vm Automation Level Override Cluster Automation Level?

VM automation stage can override cluster automation stage. From a VM potential there are five automation stages.

These are:

Fully Automated: Load stability and Initial placement may be completed by means of DRS routinely

Partially Automated: Load stability of the VM can be accomplished manually however initial placement could be performed automatically

Manual: VM migration as a part of Load balancing and preliminary placement might be both manual. DRS will best generate recommendation for that VM and administrator has to manually approve this advice.

Default: VM will inherit the DRS automation degree as defined at the cluster degree.

Disabled: DRS will no longer carry out any movements on that VM.

Q3. What Are The Limitation That Are Put By Drs Mandatory Or Must Rules On A Cluster?

If a mandatory rule is configured on a cluster then it could placed following barriers:

Limit DRS to select hosts for load balancing

Limit HA to pick out host for failover

Limit DPM to choose host to power off

It can affect potential of DRS to defragment the cluster assets. At the time of failover HA can seeks assistance for DRS and might ask to defragment sources if a single host isn't able to provide good enough sources for failover.

Q4. What Impact Does Must Rule Places On Drs, Ha And Dpm Operations?

If a migration will reason violation of ought to rule then that migration might be cancelled through DRS.

IF DPM is attempting to position a host in sleep mode for strength saving but migration of VM’s walking on this host can purpose a must rule violation, it's going to prevent DPM to place that host in sleep mode.

If HA is trying to restart VM’s after a host failure but if restart of some VM’s on a specific host can cause must rule violation then HA will either restart the ones VM’s on a few different host or couldn't restart them at all if no suitable host is available for failover.

Q5. What Are The Factors That Affect Drs Recommendations?

Following are the factors which affect the DRS pointers:

1- VM length and Initial Placement: When a new VM is created or a VM is powered on, DRS selects a number where this VM need to be to start with positioned. DRS prefers the registered host as long as placement of that VM in this host will no longer motive cluster imbalance.

During placement of such VM’s DRS makes use of a worst case state of affairs because it doesn’t have historical statistics for that VM. DRS assumes both CPU and memory call for of this VM is same to its configured length.

Oversized VM’s can temporarily reason cluster imbalance and may purpose needless migrations of active VM’s.

2- PollPeriodSec (Length of DRS Invocation): The default value of PollPeriodSec is three hundred seconds. Range of PollPeriodSec is 60 sec to 3600 sec. Shortening this period will cause boom in vCenter overhead as cluster imbalance might be calculated often.

Increasing this cost decreases the frequency of cluster balance calculation and can go away your cluster imbalanced for longer duration of times but lets in for larger variety of vMotions due to long invocation interval.

3- Simultaneous vMotion: vSphere five.1 permits 8 concurrent vMotions on a unmarried host with 10GbE abilities. For 1GbE, 4 concurrent vMotion can takes location. Also multi-NIC vMotion is supported in vSphere 5.1 so multiple energetic NICs and their blended bandwidth can be used for migration of a VM. In such environment VM’s may be migrated fast and cluster can be balanced in much less time.

Four- Estimated Total Migration Time: The migration time depends on variables like supply and destination host load, active reminiscence utilization of VM, link velocity and to be had bandwidth+ latency of the bodily network utilized by vMotion Portgroup.

Q6. Will Drs Work If Vcenter Server Is Down? If No Then Explain Why Drs Is Dependent On Vcenter Server?

No DRS will not work if vCenter Server is down.

DRS relies upon upon vCenter server for data like contemporary strength state of virtual machines, exchange in electricity kingdom of any VM, quantity of datastores to which Esxi hosts are linked and the reminiscence and cpu configurations of a VM.

DRS will use a majority of these records whilst calculating the load at the cluster and featuring migration pointers when a cluster wishes to be balanced.

Q7. What Are The Use Cases For Vm-vm Affinity Rules And Vm-vm Anti Affinity Rules?

VM-VM affinity: This is beneficial whilst you require that 2 of your VM’s must constantly run collectively on an Esxi host. For E.G. Keeping front-stop and again-cease server of an utility on equal ESXi host to reduce community latency among the 2 VM’s.

Another use case may be running together same sorts of VM’s which can be having equal type of programs if you want to get max advantages of obvious page sharing (TPS)

VM-VM anti-affinity: This is beneficial whilst you don’t want that 2 of your VM need to run together. Keeping servers presenting same type of offerings on special host will offer resiliency

For Example: You will not need your DC and ADC run together on equal Esxi host because if that Esxi host is going down it can significantly impact your environment as both DC and ADC server has gone down collectively.

Another use case might be running internet-server farms or clustered DB-servers in a virtualized environment.

Also, maintaining away 2 VM’s from every other that are very aid extensive to forestall them from monopolizing resource utilization.

Q8. If On A Vm, Vm-host Affinity Should Rule Is Configured Then Can We Migrate That Vm On An Esxi Host That Is Not Part Of The Drs Cluster?

No a VM can’t be migrated to an Esxi host that isn't a part of the DRS cluster

Q9. What Are The Best Practices For Disabling Drs?

Before disabling DRS it's miles endorsed to delete all affinity and anti-affinity policies and then continue. Because if rules aren't deleted and DRS is disabled, rules could be nonetheless in affect and may have an effect on cluster operations.

Q10. What Is Drs Cost-benefit-risk Approach?

DRS uses a fee benefit risk method to load stability a cluster. Before providing the migration pointers for a VM to load stability a cluster,

DRS calculates three things:

Cost: What can be the fee of migrating a VM from source to destination host? Cost right here refers back to the CPU and memory.

When a vMotion method in invoked on a VM, it reserves 30% of the cpu center (For 1 GB NIC) of that VM and one hundred% cpu core (For 10 GB NIC). This reservation is created on each supply and destination host. This reserves sources can’t be allocated to another VM while vMotion is in development. This can positioned a few stress on an Esxi host while it's miles closely loaded.

Benefits: What could be the useful resource gain that an Esxi host will get after migrating a virtual system to different Esxi ho st. If after the migration CHLSD value of the Esxi host comes down then DRS will don't forget that migration as advantage.

Risk: Risk debts for opportunity of irregular hundreds. Suppose a VM has inconsistent and spiky demands of assets, then migrating such VM’s isn't always an excellent pass due to the fact may be at the time of migration VM useful resource call for changed into low but after crowning glory of migration, VM’s resource needs abruptly increased. In this case it can purpose the increase in vacation spot Esxi hosts CHLSD and again DRS has to perform migration of that VM to deliver down CHLSD of the Esxi host wherein that VM become migrated.

DRS recommends migrations if Benefit received because of a migration < cost related to that migration.

Q11. What Are The Use Cases Of Vm-host Affinity Rules And Vm-host Anti-affinity Rules?

VM-Host affinity: This is beneficial while you need that your VM should run on a particular Esxi host most effective.

For Example: running and oracle DB server which has socket primarily based license. If your environment is having heterogeneous hosts than migrating such VM to a number which has special CPU configuration can violates your license and may cause trouble.

VM-Host anti affinity: This is beneficial while you need that a selected VM ought to not run on a few precise Esxi hosts.

For Example: your environment has heterogeneous hosts and all the hosts don’t have Numa structure and also you need to get blessings of the vNuma inner your VM. In this situation you'll need your VM to run simplest on those servers which helps Numa.

Q12. If A New Drs Rule Is Created But That Rule Is Conflicting With Any Existing Rule Then Which Rule Drs Will Respect, Old Rule Or New Rule While Performing Drs Actions?

If a brand new rule is conflicting with an antique rule then new rule can be disabled robotically. DRS will decide on respecting the old rule.

Q13. What Is The Default Invocation Period For Drs. Can We Change This. If Yes Then How?

The default invocation period is three hundred seconds (five minutes). But this can be changed through the configuration record vpxd.Cfg.

We should trade the cost of <pollperiodsec> as proven underneath:

<config>

<drm>

<pollperiodsec>

three hundred

</pollperiodsec>

</drm>

</config>

Just alternate the fee three hundred to a custom fee described by you. The range of supported value is 60 secs to 3600 secs.

Q14. What Is The Role Of Vpxa In Drs?

VPXA is the vCenter agent that runs internal Esxi hosts and it enables a 2 way verbal exchange between Esxi hosts and vCenter Server.

VPXA is accountable for:

Keeping the repute of Esxi and VM’s in sync

It sends data to vCenter server whilst a VM’s power kingdom is modified or a VM is vMotioned from one host to other.

DRS makes use of this information that's presented through Esxi hosts to vCenter server for calculating the burden stability and proposed migrations in case of cluster imbalance.

Q15. How Drs Calculates There Are Imbalances In Cluster? What Are The Things That Drs Takes Into Account For Determining This?

 To calculate the cluster imbalance, DRS compares the Current Hosts Load Standard Deviation (CHLSD) to Target Hosts Load Standard Deviation (THLSD) and if

CHLSD < THLSD

Cluster is considered as imbalanced.

CHLSD Calculation:

DRS computes Normalized Entitlement (NE) of each Esxi hosts and the standard deviation related to it. NE is nothing but calculation of ways lots resources are presently utilized out of total sources. NE is calculated by summing up dynamic entitlements (usage) of all VM’s which might be running on an Esxi host and diving this by way of Esxi host potential.

So, NE= Dynamic Usage of all VM’s / Total host potential

THLSD Calculation:

THLSD is derived from DRS migration threshold that's defined on the time of configuring DRS. Each threshold level units one-of-a-kind imbalance tolerance margin. The competitive threshold units a good margin making an allowance for little imbalance, whilst conservative thresholds tolerates bigger imbalances.