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”

Popular posts from this blog

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N