Skip to main content

VMware: Creating iSCSI network in vSphere ESXi 5.0







Storage Adapter:





Nope.. by default it’s not installed, you must manual add the adapter by clicking Configuration > Storage Adapter > Add Storage Adapter





- Select: Add Software iSCSI Adapter





A new software iSCSI adapter will be added to the Storage Adapters list. After it has been added, select the software iSCSI adapter in the list and click on Properties to complete the configuration








Event: Change Software Internet SCSI Status = Completed


Create new vSwitch (in my case two VMkernel ports):





- Network label: iSCSI01





- Configure IP Address and Subnet Mask


..


- Finish the configuration, repeat this step to configure the 2nd iSCSI02 port


vSwitch2 result:





VMkernel – Override switch failover order:


Now we need to change the failover order for each VMkernel:





iSCSI01: Active Adapter VMNIC4 – Unused Adapter: VMNIC5

iSCSI02: Active Adapter VMNIC5 – Unused Adapter: VMNIC4


Configure Software iSCSI Initiator:


Go to the properties of the iSCSI initiator: Configuration > Storage Adapters > iSCSI Storage Adapter: vmhba** > Properties


And setup Dynamic Discovery – Sent Target location (in my case the StarWind VSA)





- Add target: 192.168.70.2:3260


Next we need to bind a pNIC to the iSCSI VMkernel.. looong loooong time ago (vSphere 4) ..we need to configure this by CLI (esxcli swiscsi nic add -n vmk1 -d vmhba33) but now it’s possible to do this via the GUI.


When you go to tab: Network Configuration > Add..





- Click: Add..





- Now you can select a Physical NIC to bind the VMkernel for your iSCSI targets





Overview:




VMkernel Port Bindings

iSCSI01


VMkernel Adapter

vmk1


Port Group Policy

Compliant


Path Status

Not Used


Physical Network Adapter

VMNIC4


Switch

vSwitch2


IP Address

192.168.70.10


Subnet Mask

255.255.255.0


Configured Speed

1000 Mbps (Full Duplex)





VMkernel Port Bindings

iSCSI02


VMkernel Adapter

vmk2


Port Group Policy

Compliant


Path Status

Not Used


Physical Network Adapter

VMNIC5


Switch

vSwitch2


IP Address

192.168.70.11


Subnet Mask

255.255.255.0



Now you can add the storage by clicking the “Add storage wizard”
Labels:

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...
Read more

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...
Read more

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...
Read more