Skip to main content

VMware Fixed and Round Robin are two types of path selection policies used in VMware ESXi for multipathing.


Fixed Path Policy:


1. Definition: The Fixed path policy is a path selection policy that always uses the same preferred path for I/O operations.

2. How it works: The ESXi host selects a preferred path for I/O operations and sticks to it unless the path becomes unavailable.

3. Advantages: Provides predictable performance and is suitable for environments where the storage array is configured for active-passive mode.

4. Disadvantages: May not provide optimal performance if the preferred path becomes congested.


Round Robin Path Policy:


1. Definition: The Round Robin path policy is a path selection policy that distributes I/O operations across all available paths in a cyclical manner.

2. How it works: The ESXi host selects a path for I/O operations and then switches to the next available path for the next I/O operation.

3. Advantages: Provides load balancing across all available paths, which can improve performance and reduce the risk of path congestion.

4. Disadvantages: May not provide predictable performance and can be affected by differences in path latency.


When to use each:


1. Fixed Path Policy: Use in environments where predictability and consistency are more important than load balancing, such as in active-passive storage array configurations.

2. Round Robin Path Policy: Use in environments where load balancing and performance are critical, such as in active-active storage array configurations.


Configuration:


To configure the path selection policy in ESXi:


1. Log in to the vSphere Client.

2. Select the ESXi host.

3. Click on "Configuration" and then "Storage".

4. Select the storage device.

5. Click on "Properties" and then "Path Selection Policy".

6. Select the desired path selection policy (Fixed or Round Robin). 


Comments

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...