iSCSI breaks when upgrading form 3.02 to 3.5 using SanMelody

[RickSz]

Hi Folks,

I've been playing with ESX 3.02 with Sanmelody's software based iSCSI solution in a lab for the past month and half without any issues.

I've tried upgrading to 3.5 and also a complete fresh install of 3.5 and can not get the iSCSI initiator to see my SanMelody volumes. I've verified it's something to do with 3.5 by reinstalling 3.02 and it sees the iSCSI volumes immediately. I've also tried using the openfiler iSCSI and same scenario happens.

Anyone else have this issue? If not, can any recommend another software based ISCSI program that has worked with 3.5?

Regards,

Rick

[virtualdud3 · Accepted solution]

Are you opening the firewall port?

To do so, run the following command from the Service Console:

#esxcfg-firewall -e swISCSIClient

###############

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

[depping]

indeed, probably firewall issue. this was a bug in 3.0.2 pre 15nov updates. besure to open it up if you run 3.5 or the updates.

Duncan

My virtualisation blog:

[RickSz]

That totally fixed my issue!

Thanks guys, I was banging my head against a wall for the past 2 days trying to get it to work.

Regards,

Rick