Problem with Software iSCSI on VMWare 5.0

We have a Buffalo TeraStation NAS that we want to connect to a VMWare 5.0 infrastructure via software iSCSI. I have done the configuration by the book (create VMkernels, bind NICs, add software iSCSI storage, assign NICs, discover target) and everything seems to be fine. Alas after i rescan the iSCSI storage adapter, it doesn't see any targets. I am relatively new to all this. Any suggestions?

ps. i attach screenshots of the iSCSI adapter's Network tab, Discovery tab and Status (that shows zero targets/paths)
Who is Participating?
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
Do you see any LUNs?

How you added the IQN of the software adaptor to the LUNs on the NAS?

Have you configured LUNs on the NAS?

Please check against my document to check your configuration

Please follow my EE Step by Step Tutorial Article with screenshots, it will show you how to complete this correctly

HOW TO: Add an iSCSI Software Adaptor and Create an iSCSI Multipath Network in VMware vSphere Hypervisor ESXi 5.0
criskritAuthor Commented:
hello and thanks for your reply.
The steps in your article is exactly what i have followed (except instead of creating a new vSwitch i am using an existing one). Per your questions:
Q1: i don't see any LUNs through the iSCSI. (i don't see any devices/targets).
Q3: the NAS has LUNs, it actually works fine with a physical server that is accessing it.
Q2: this sounds interesting, i have to do something on the NAS side in order to "accept" connection from the iSCSI adapter? Could you please elaborate?

FYI (in case it helps) I can vmkping the NAS from the host and i can also reach the TCP port (nc -z ip_address 3260)
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Have you enabled LUNs for concurrent access from multiple IQN Targets?

Do you have LUN Mapping enabled, usually you would need to add the IQN of the software initiator to the LUN.

Make sure a ESXi and Windows Server DO NOT access the same LUN.
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

criskritAuthor Commented:
good progress! There were two things that I needed to do:
- disconnected the Windows machine from the iSCSI NAS
- configure a volume that can have more than one attached servers (i setup a simple non-LVM volume with max 8 concurrent connections)
once i did these i added the storage to one VMHost and showed up in all three!
many thanks for your help.  :-)

one more question: this NAS is for backups so only one VM (that runs the backups) will need tp access it. Can i have the VM access the NAS directly (as direct attached storage) as opposed to creating a Virtual Disk that will sit on the NAS? I don't want the extra layer of complexity and i'd rather have the data sit directly on the disk.
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
This could be achieved in two ways

1. Install Microsoft iSCSI Initiator in the Virtual Machine, and connect the VM directly to the NAS. This will then use the LUN and be able to format as native NTFS.

2. Use a RAW LUN and present this to the VM. (this may not be supported on your NAS)

see here
criskritAuthor Commented:
I went with the RAW LUN approach (first had to disconnect the LUN from the VMHosts) and works like a charm. Thanks for all the help, you are really great!  :-)
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Thanks for the kind words.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.