Author: Danilo

Configuring MPIO on Windows iSCSI Initiator is an article that explains how to configure the MultiPath Input Output in a Windows Client to provide load balancing and failover process to access an iSCSI LUN provided by the vSAN iSCSI Target Service feature. First and foremost, What is MPIO? MultiPath Input Output (MPIO) is a feature or framework that allows administrators to configure load balancing and failover processes for connections to storage devices. Most storage arrays offer this in the form of multiple controllers, but the servers still need a way to spread the I/O load and handle internal failover from…

Using the vSAN iSCSI Target Service is an article that explains how to enable and configure the vSAN iSCSI Target Service. We will show in a basic way how to enable and configure this service. Before starting, I want to share some official links about this service: About the vSAN iSCSI Target Service With this service, a remote host with an iSCSI Initiator can transport block-level data to an iSCSI Target in the vSAN cluster. In this context: In a vSAN cluster, we can enable this feature and configure one or more vSAN Targets to provide block storage to legacy…

vSAN is a software-defined storage solution used a lot in modern data centers. It’s a police-driven technology that provides us the flexibility to apply different policies for each virtual machine (VM) and different policies for each virtual disk (vmdk level). This article aims to provide a basic understanding of the vSAN Durability Components. We have written some articles about vSAN. You can access those by the following link: First and Foremost, What is a vSAN Storage Policy? As we know, vSAN is an Object-Based storage. It means that all VMs stored in the vSAN datastore are formed by the following…

This article will provide an introduction to the vSAN Trace Files and some techniques to customize the maximum size and location to place those files. So, First and Foremost, What are the vSAN Trace Files? vSAN traces are log files that are used for diagnosing and troubleshooting issues with vSAN. These files can be particularly useful for debugging critical performance issues and data-path-related problems. By default, vSAN traces are saved to /var/log/vsantraces.The default maximum file size is 180MB, and there is a rotation of 8 files. This means that when the 9th file is created, the oldest file is deleted,…

VMs Are Unable to Connect in the NSX Environment is an article that shows a simple workflow to debug a VM connection issue. In this article, for instance, we are considering both VMs placed in the same NSX segment (VM A and VM B) but running on different ESXi hosts (different Host Transport Nodes). The NSX segment name is “NSX Web Segment”. In the following picture, we have a workflow that can be used to troubleshoot a communication failure between both VMs: Step 1: Are the virtual machines configured correctly? To begin with, a good starting point is to check…

NSX Distributed Firewall Challenge Scenario shows a scenario with a connectivity issue between two VMs placed on the same segment. The challenge here is to understand the issue by using troubleshooting techniques and fix the issue. Let’s talk a little about the scenario: What is the issue? From the VM “sa-infosec-03” the curl command failed. The curl command is using the reach a web page provided by the “sa-tlsvm-01” VM. Our aim here is to troubleshoot and solve the issue! Note: There are some ways to troubleshoot this issue. So, based on this, we will show a couple of ways…