I have VM network within workstatin 7. i installed openfiler as VM on VM workstation 7 when go to properties of iSCSIhba33 adapter and chose Dynamic Discovery it did detect iSCSI target but once i select ok and scan for LUN it did not find LUN. all VM's and ESX are same subnet each one can resolve each other by IP as well hostname.. also on ESX host iSCSI client port is open.
Is any one tell me what to check next. is very annoying that my ESX host can't see iSCSI LUN
Thanl
Thread moved to Workstation Forum -
If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
I checked every thing ok at OPENFILER but would you please tell me what exactly i should check in open filer specifically so esx can see LUN.
Thank
From what I understand I guess you missed one of the steps, Franck pointed to in link 2.
Please double check that you followed the documentation step-by-step.
André
I don't use Openfiler, so I'm not quite sure, however I think in "Network Access Configuration" the configuration for your "Allowall" should be either 10.0.0.0/255.0.0.0 or 10.0.1.0/255.255.255.0.
André
André is correct you should change the Allowall network setting to 10.0.0.0 / 255.0.0.0 it should then work ok.
If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Thank for reply. my whole network within VMware Workstation 7 include Win 2008 (DC), XP pro, and 4 ESX hosts are in same host and network ID range and same sub net mask.
Win 2008 10.0.1.2 255.0.0.0
XP 10.0.1.3 255.0.0.0 vCenter server
ESX4 10.0.1.244 255.0.0.0
Openfiler 10.0.1.80 255.0.0.0
and i all can ping each other by IP and host name, iSCSI initiator client port is open 3260 even i opened all ports on esx hosts but still have same issue.
wondering what to check.
Did you change the allowall rule in openfiler to the 10.0.0.0 / 255.0.0.0.
This is seperate to the actual ip address you gave openfiler, this is the rule that says what hosts are allowed to connect to the iSCSI service.
If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
yes i did
Does it work if you add the openfiler in the dynamic discovery tab by IP address rather than name?
ziarzi, have you solve the issue? i'm facing exact the same problem. MS initiator detects openfiler LUN esxi doesn't... looking forward for your replay
@Mixant21 & Ziarzi
I came across the same issue as yourselves and think I may know what the problem is. Openfiler for some reason has a max connection per iSCSI target of 1 (and can't see an easy way of changing it), therefore the way round to multiple connections to the same LUN for vMotion is to create the same no. of iSCSI targets as ESX hosts in your cluster and for each iSCSI target created you map the same LUN's, also don't forget to modify the ACL to Allow as it's set to Deny as default.
Proceed with the same you have done before:
1. Storage adapters>iSCSI initiator> properties on one of your ESX hosts
2. Dynamic Discovery and add the openfiler server (If you did this previously then I would remove it, rescan and re-added the openfiler server)
3. rescan the HBA's as requested and you should see appear below the Openfiler LUN's
4. You still need to go to Storage>add Storage>DIsk/LUN> and you should see the Openfiler LUN's ready to be added
If you have vCenter setup properly and your hosts are in a cluster you only need to repeat steps 1-3 for your other ESX hosts
I hope this helps.