Skip to main content

Preparing the ESXi Hypervisor for multiple NIC Usage




Step 1:

  • Open the vSphere Client and proceed to Configuration, Networking and click Add Networking
ISCSI-mountVmware-01.png

Step 2:

  • Select VMKernel and click Next
ISCSI-mountVmware-02.png

Step 3:

  • Create a new network switch and select a NIC located on another subnet
ISCSI-mountVmware-03.png

Step 4:

  • Enter a new name for this new network and click next
ISCSI-mountVmware-04.png

Step 5:

  • Enter an IP Address and Subnet address for this secondary NIC and click next
ISCSI-mountVmware-05.png

Step 6:

  • Final Confirmation Settings
ISCSI-mountVmware-06.png

Step 7:

  • The second network has been added to this Hypervisor
ISCSI-mountVmware-07.png

Step 8:

  • Repeat this process for each additional network to be added to the Hypervisor

Step 9:



Mounting the iSCSI Target on the ESXi Hypervisor

Overview: This section will guide the administrator in mounting iSCSI Targets on the Synology DiskStation to the ESXi Hypervisor.

Step 1:

  • Within the Configuration tab, click on Storage Adapters, select the iSCSI Software Adapter and click Properties
ISCSI-mountVmware-08.png

Step 2:

  • In this example, the iSCSI Initiator is disabled, click Configure to configure the settings of the iSCSI Initiator
ISCSI-mountVmware-09.png

Step 3:

  • Enable the iSCSI Initiator
ISCSI-mountVmware-10.png

Step 4:

  • Once the iSCSI Initiator is enabled, click on Dynamic Discovery
ISCSI-mountVmware-11.png

Step 5:

  • Enter the primary IP Address of the Synology DiskStation
ISCSI-mountVmware-12.png

Step 6:

  • If mounting for MPIO, enter the secondary IP address of the Synology DiskStation, located within the secondary subnet of the ESXi Hypervisor
    • The preceding direction may skipped for non-MPIO Environments
ISCSI-mountVmware-13.png

Step 7:

  • Rescan the Host Bus Adapter
ISCSI-mountVmware-14.png

Step 8:

  • The iSCSI Initiator has detected the target on the Synology DiskStation.
ISCSI-mountVmware-15.png

Step 9:

  • Right Click on the Target and click Manage Paths
    • The preceding direction may skipped for non-MPIO Environments
ISCSI-mountVmware-16.png

Step 10:

  • Select Round Robin (VMWare)
    • The preceding direction may skipped for non-MPIO Environments
  • Note that within the Path Management, that the ESXi Hypervisor is using two paths (via two subnets) to mount the same iSCSI Target.
ISCSI-mountVmware-17.png

Step 11:


Formatting the iSCSI Target for usage within the ESXi Hypervisor

Overview: This section of the article will guide the administrator in formatting the iSCSI Target for usage within ESXi Hypervisor

Step 1:

  • Within the Configuration tab, click on Storage, and click Add Storage
ISCSI-mountVmware-19.png

Step 2:

  • Select Disk/LUN and click Next
ISCSI-mountVmware-20.png

Step 3:

  • Find the iSCSI Target, and click Next
ISCSI-mountVmware-21.png

Step 4:

  • Review the current disk layout and click Next
ISCSI-mountVmware-22.png

Step 5:

  • Enter a new datastore name for this new storage.
ISCSI-mountVmware-23.png

Step 6:

  • Select a block size to use for this new storage
    • Using default settings is recommended
ISCSI-mountVmware-24.png

Step 7:

  • Final Confirmation Settings
ISCSI-mountVmware-25.png

Step 8:

  • The new datastore has been added...
ISCSI-mountVmware-26.png

Step 9:

  • ...and is ready for use
ISCSI-mountVmware-27.png

Popular posts from this blog

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...

Troubleshooting vSAN Storage Policy Migration Failures in VMware Cloud Foundation 9.0

Recently I had a customer who migrated their VMware infrastructure from vSphere 7.0 to VMware Cloud Foundation 9.0. After the migration, they wanted to update their vSAN storage policies to take advantage of the new vSAN ESA (Express Storage Architecture) features. However, when they tried to change the storage policy for their production VMs, the operation kept failing with a cryptic error message. The error they were getting was: "Cannot complete operation due to insufficient resources to satisfy current storage policy." This was strange because they had plenty of disk space available. The vSAN cluster was only at 45% capacity, and all the hosts were healthy. Let me walk through how we troubleshooted and fixed this issue. Understanding the Problem First, let's understand what was happening in their environment: They had a 6-node vSAN cluster running VCF 9.0 vSAN was configured with the new ESA architecture They were trying to migrate VMs fro...

Unlocking VMware Cloud Foundation 9.0: A Strategic Blueprint for Enterprise Transformation

The evolution of VMware under Broadcom represents not disruption, but clarification—a focused vision toward unified private cloud excellence. As organizations navigate this transformation, the opportunity has never been greater to build truly modern, efficient, and powerful infrastructure with VMware Cloud Foundation. After architecting VMware solutions across diverse enterprise environments, I've observed a pattern: organizations that embrace VMware Cloud Foundation (VCF) strategically—rather than viewing the transition as a burden—emerge with significantly more capable, cost-effective, and future-ready infrastructure. This post shares a practical framework for successfully modernizing your VMware environment, maximizing your investment, and positioning your organization for the AI-driven, cloud-native future. Understanding the VMware Cloud Foundation Vision Let's start with clarity about what Broadcom and VMware are building: VMware Cloud Foundati...