Troubles setting up VMotion over iSCSI (HP AIO SB600c).

[om8000]

Hello Everyone!

I'm using: AIO SB600c (which has some add-on notices in http://www.vmware.com/pdf/vi35_san_guide.pdf)

I don't understand what this notice means (Single Controller only)

On iSCSI management server I'm getting message (after first VMotion attempt):

______________________________________________________________________________

iSCSI LUN contains multiple host references. Multiple hosts are not supported.

ESX2: iSCSI LUN not associated with a host.

______________________________________________________________________________

Well, anyway, I set up everythin under windows and VMware, to make available VMFS partition on

both ESX1 and ESX2 servers.

one Target on windows management (physical server):

Computer Management > Storage > Microsoft iSCSI target > iSCSI Targets > ppesx1-0be97594

> tab: iSCSI Initiators: two IQNs which I copied from each server, when iSCSI setup was done.

On both ESX servers I created VMkernel adapter with VMotion enabled

I also opened firewall on ESX1,2 so that no ports are blocked.

Yes, I have VirtualCenter and license server ;).

Till now I was only setting up VMotion on SAN storages and no problems till now...

But, but, but ...

On first setup everything went ok.

Both servers were able to see the same VMFS with one test-VM.

Now on first VMotion attempt, where also all VMware checks (before VMotion attempt)

went well, some stranege error appears. It was'nt descriptive at all.

What really happened, was: on ESX2 server VMFS was not available anymore.

Even not after rescan, or server reboot.

Am I doing something wrong here, or notice above (Single Controller only) means, that

only one ESX at the time can write or read to one iSCSI LUN?

Is this known issue?

If not, who can confirm which HP iSCSI devices are supported for VMotion?

Is there any special settings that need to be done on iSCSI mgmt server or under VMware ESX ?

Can ayone recomend who should I talk to ?

[weinstein5]

Can you post the error - because as long as both ESX hosts see the iSCSI storage vmotion should work - from the service consoles can you ping the vmkernel ports using the vmkping command -

[om8000]

If you are asking for VMware errors:

VMotion: Checking and validating: ok, but after that: I/O error, unknown

ESX2:/var/log/vmkernel: iSCSI: session 0x8e03f90 login I/O error, failed to receive a PDU

ESX2:/var/log/vmkwarning: WARNING: SCSI: 5306: vml.020000000060003ff6413375fea7936619cdfb52ad566972747561: Too many failed retries 33 (32), Returning I/O failure. 0x28 1/0x0 0x2 0x8 0x0

I would also like to know if HP AIO SB600c is supported for VMotion or not.

Cany anyone confirm that please?

[om8000]

I want to point out that:

after I try VMotion - iSCSI LUN on ESX2 DISSAPEARED.

There were no possibility to make it work again (rescan - no new devices, reboot: the same).

and iSCSI storage reported an error mentionet on the top of this issue.

Are there any known issues?

[weinstein5]

Typically as long as the SAN i seen by the ESX hosts it should not impact vmotion - are you able to vmkping the vmkernel ports? In other words can the two vmkernel ports enabled for vmotion reach each other via simple ping?

[om8000]

ok now I feel stupid

how exactly to ping, can U give me a real-life example?

and don't you think that this message below from iSCSI storage is important ...

iSCSI LUN contains multiple host references. Multiple hosts are not supported. ESX2: iSCSI LUN not associated with a host.

at that time our clock is: 21:50 so i will continue tommorow.

[weinstein5]

now do you have ESXi or the installable version - if it is the installable version you can go to the service console and run the command vmkping - which acts like a regular ping command but will use the vmkernel port - for ESXi I believe this can be done from the direct console -

[om8000]

I have full version, I'll try from console and I'll report results.

But minwhile still want to have confirmation if this exact iSCSI model HP AIO SB600c is supported for vmotion and/or simultaneous access or not

[om8000]

INTERFACES PING RESULTS

ESX1: vmkping -v ESX1-IP

# vmkping -v 192.168.1.105

PING 192.168.1.105 (192.168.1.105): 56 data bytes

64 bytes from 192.168.1.105: icmp_seq=0 ttl=64 time=0.123 ms

64 bytes from 192.168.1.105: icmp_seq=1 ttl=64 time=0.105 ms

64 bytes from 192.168.1.105: icmp_seq=2 ttl=64 time=0.086 ms

--- 192.168.1.105 ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 0.086/0.105/0.123 ms

ESX1: vmkping -v ESX1-VMOTION-IP

# vmkping -v 192.168.123.1

PING 192.168.123.1 (192.168.123.1): 56 data bytes

64 bytes from 192.168.123.1: icmp_seq=0 ttl=64 time=0.048 ms

64 bytes from 192.168.123.1: icmp_seq=1 ttl=64 time=0.018 ms

64 bytes from 192.168.123.1: icmp_seq=2 ttl=64 time=0.018 ms

--- 192.168.123.1 ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 0.018/0.028/0.048 ms

ESX1: vmkping -v ESX2-IP

# vmkping -v 192.168.1.106

PING 192.168.1.106 (192.168.1.106): 56 data bytes

64 bytes from 192.168.1.106: icmp_seq=0 ttl=64 time=0.200 ms

64 bytes from 192.168.1.106: icmp_seq=1 ttl=64 time=0.190 ms

64 bytes from 192.168.1.106: icmp_seq=2 ttl=64 time=0.158 ms

--- 192.168.1.106 ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 0.158/0.183/0.200 ms

ESX1: vmkping -v ESX2-VMOTION-IP

# vmkping -v 192.168.123.2

PING 192.168.123.2 (192.168.123.2): 56 data bytes

64 bytes from 192.168.123.2: icmp_seq=0 ttl=64 time=0.394 ms

64 bytes from 192.168.123.2: icmp_seq=1 ttl=64 time=0.140 ms

64 bytes from 192.168.123.2: icmp_seq=2 ttl=64 time=0.130 ms

--- 192.168.123.2 ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 0.130/0.221/0.394 ms

ESX2: vmkping -v ESX2-IP

# ./vmkping -v 192.168.1.106

PING 192.168.1.106 (192.168.1.106): 56 data bytes

64 bytes from 192.168.1.106: icmp_seq=0 ttl=64 time=0.233 ms

64 bytes from 192.168.1.106: icmp_seq=1 ttl=64 time=0.060 ms

64 bytes from 192.168.1.106: icmp_seq=2 ttl=64 time=0.054 ms

--- 192.168.1.106 ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 0.054/0.116/0.233 ms

ESX2: vmkping -v ESX2-VMOTION-IP

# ./vmkping -v 192.168.123.2

PING 192.168.123.2 (192.168.123.2): 56 data bytes

64 bytes from 192.168.123.2: icmp_seq=0 ttl=64 time=0.047 ms

64 bytes from 192.168.123.2: icmp_seq=1 ttl=64 time=0.016 ms

64 bytes from 192.168.123.2: icmp_seq=2 ttl=64 time=0.013 ms

--- 192.168.123.2 ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 0.013/0.025/0.047 ms

ESX2: vmkping -v ESX1-IP

# ./vmkping -v 192.168.1.105

PING 192.168.1.105 (192.168.1.105): 56 data bytes

64 bytes from 192.168.1.105: icmp_seq=0 ttl=64 time=0.461 ms

64 bytes from 192.168.1.105: icmp_seq=1 ttl=64 time=0.196 ms

64 bytes from 192.168.1.105: icmp_seq=2 ttl=64 time=0.199 ms

--- 192.168.1.105 ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 0.196/0.285/0.461 ms

ESX2: vmkping -v ESX1-VMOTION-IP

# ./vmkping -v 192.168.123.1

PING 192.168.123.1 (192.168.123.1): 56 data bytes

64 bytes from 192.168.123.1: icmp_seq=0 ttl=64 time=0.212 ms

64 bytes from 192.168.123.1: icmp_seq=1 ttl=64 time=0.120 ms

64 bytes from 192.168.123.1: icmp_seq=2 ttl=64 time=0.145 ms

--- 192.168.123.1 ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 0.120/0.159/0.212 ms

[kjb007]

It appears your iSCSI implementation does not support multiple hosts having access to the LUN at the same time. That is what the message was stating. Either it does not support multiple host access, or it has not been enabled. So, when you configure the first time, it will allow the adding, but when two hosts try to access it, it removes access from one of them. Check your iSCSI target to see if there is some setting to allow multiple host access.

-KjB

[RXWatcher]

I have a HP AIO 1200R that I was able to get to work with vmotion and 2 ESXi boxes.

1. I initially setup the iSCSI target via the HP All in One Storage Manager

2. Went into the MS iSCSI Target and found my target entry created by the HP All in One Storage Manager, right clicked, went to properties and the iSCSI Initiators tab and defined both ESXi initiators.

3. Went back to the VI console of the first ESXi host and rescanned the Storage Adapters and noticed that it found my iSCSI target and the LUN

4. Went into the Storage and added my disk/lun and it found it was blank and formatted it.

5. Went into my 2nd ESXi host and rescanned the Storage Adapters and it found the iSCSI target.

6. Went into the Storage section on the 2nd host and the LUN was already added.

7. Migrated a VM to the LUN

8. Tested vmotion and it worked.

HP Storage Manager complains that you can't have 2 initiators configured but seems to work great.

Performance isn't too bad..I can push 70-80 Mbps through a dedicated 1GB switch..thats not using NIC teaming.Well, I dont think it's too bad anyway.

[bob2257]

I am using the SB600c and tried the work around above with no luck

Has anyone had any luck getting this to work at all on the SB600c? is it at all possible?