Skip to main content

How to Setup iSCSI on Windows 2008 R2 Server

Configuration: VMware vSphere 4.0, ESX Hosts, EMC AX4-5 Celerra's, 2 HP Proliant DL380G7 Servers for Veeam 5.0.2 Backup and Replication (1 Server for Main Office and 1 for Collocation Datacenter Site), 2 Cisco Switch (Storage Switch) Main/Collocation Site configuration, Qlogic iSCSI HBA Server Card connectivity to SAN's.

Goal: Connect iSCSI HBA Cards to SAN through iSCSI Initiator on Windows 2008 R2 SP1 Servers.

1. Go to the QLogic website (HBA Drivers Website) if it is an OEM choose EMC, NetApp, etc. This tutorial is for a QLogic EMC HBA. (This is tested to work for Dell PowerEdge/HP Proliant Servers)

Driver Download Link

1a. You will also need to download the EMC PowerPath Server Utility for Windows Server x64 (2008 R2). And make sure that you download and install the Navisphere Server Utility (Windows/VMware) - [Just register your server in Navisphere if you have already configured your AX4-5]

2. Install the drivers and you should now see QLogic iSCSI Adapter under Storage Processors in Device Manager.

3. You can use SANSurfer for QLogic to configure the cards (Recommended) or you can change the configurations on the QLogic iSCSI Adapter itself. I had to many problems from the Driver configuration Window, so just download and use SANSurfer. The password is 'config'.

4. Check your settings on the SAN for iSCSI since your configurations of SANSurfer, you must make sure you can ping your SAN IP first before doing anything.


4a. Make sure you can ping your SAN from the Device Manager QLogic iSCSI Adapter. Make sure that the IP is on the same IP Subnet as the SAN. If it is 10.10.1.XX, then your iSCSI card has to be on 10.10.1.XX to communicate. Make sure that the server switch is setup right also! If you can't ping, FIX THIS FIRST!!!



5. Ok. Now you can ping the SAN's IP Port of 10.10.1.11 (or whatever) with your Server iSCSI IP of 10.10.1.50. Great. Now, let's configure Windows Server 2008 R2 SP1 iSCSI Initiator.

5a: Open iSCSI Intiator. 
5b: Click on the Discovery Tab. 
5c. Click on Discover Portal
5d. Enter the IP Address of the SAN (#4 Above) 
5e. Select the Local Adapter (your iSCSI HBA Card) and the iSCSI IP (Troubleshooting Tip: If no IP is showing or it is showing all 0000:0000:000 just pick it anyway. Make sure it is the right HBA by selecting the same from the same Adapter row. So...if it is the 2nd iSCSI Adapter HBA, pick the 2nd Initiator IP option...OK?) 
5f.  If you are using CHAP/Initiator Authentication use your iSCSI Intiator (Make the Initiator the default or be warned of plenty of SAN Configuration Headaches)


 6. Click on Volumes and Devices and click on Auto configure. It will come up with gobbledegoop. This is when you have to go to Disk Management and Configure the SAN Drives as NTFS (Troubleshooting Tip: NTFS 101: If the SAN LUN was/is used for anything else, it will not let you format the drive or Initialize  the disk, so NO you will not be sharing this LUN, it will need to be dedicated to format and use. So do not waist time trying to get it to work.)

6a. (Troubleshooting Tip: I highly recommend naming the HDD properties by the SAN LUN Name for Troubleshooting and problem resolution later.)










Popular posts from this blog

How to Fix /storage/core filesystem Out of Disk Space Error on VCSA 6.0U1

How to fix the error of "The /storage/core filesystem is out of disk space or inodes"


Step 1: Login to the new VCSA 6.0U1 HTML5 web client. https://ip address:5480



Step 2: Enable SSH and Bash Shell
Step 3: Login as root and type "shell" at Command> shell
Step 4: df -h (Check if it's out of space)
/dev/mapper/core_vg-core               50G   50G     0 100% /storage/core
Step 5: Stop the services of VCSA: 
hostname: # service vmware-vpxd stop hostname: # service vmware-vpxd status (make sure it is stopped)
Step 6:  cd /storage/core
Step 7: rm -rf *.tgz (be CAREFUL...do this in the wrong directory and you will be retrieving from a backup.)


If you need help. Go to Cybercity (http://www.cyberciti.biz/faq/delete-all-files-folder-linux/
Step 8: service vmware-vpxd restart

Step 9: history -c
Step 10: Refresh the browser (https://ip address:5480). Now it's all green


VMware KB: (

How to Configure HP ILO 4 for Active Directory Login

1. Make sure that your Windows Active Directory Domain Controller has an SSL Certificate to support port 636 (HP's authentication doesn't like 389)

2. Use Softerra LDAP Administrator (or whatever is your preferred tool to get the OU path) if you don't know how to do it by heart (which...um...sometimes its better to verify).

3. Make sure that you have a way to authenticate users by adding in the OU where your restricted accounts are located. You don't want anyone in the domain to be able to login to the server.

ILO Login > Administration > User Administration - Click New and Add the Group DN Only:



Click Add Group and then you will see your group added. (*Make sure it's a security group)


4. Add in your Windows Active Directory DC to authenticate against (Verified against 2008R2):

ILO Login > Administration > Security - Directory (*Make sure it's the OU where the security group is)


5. Sign Out (Log off) and then Log Back in (If you don't see Direct…

VCSA vmware-vpxd Service Won't Restart After Upgrading to 6.0 U2

You navigate to the VMware Web Client and you get this 503 Error:
503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x7fe4a805cc90] _serverNamespace = / _isRedirect = false _pipeName =/var/run/vmware/vpxd-webserver-pipe)
Cause:(SSL Certificates wouldn’t issue automatically after reboot for service vmware-vpxd
Compounded Problem:(Clearing logs under ~/.* **root**) – Specifically, clearing ~/.pgpass 
(Lesson Learned: NEVER EVER CLEAR FILES UNDER ~/. Except .bash_history on templates creation only!!!)
Fix: Kill all the services running vpxd
1. ps -ef | grep vpxd 2. kill ### 3. Re-add the ~/.pgpass file with the PostGreSQL password 4. vi /et c/vmware-vpx/embedded_db.cfg 5. Copy the password you see between PGUSER_PASSWORD=’password here‘ 6. Put the password back in ~/.pgpass
localhost:5432:VCDB:postgres: password here localhost:5432:postgres:postgres: password here localhost:5432:VCDB:vc: password here
7. Check /etc/hosts and make sure config is there. 10.…