About iscsi share storage connect same target and volume

[BanchaTH]

Hi Alls,

I have openfiler and make 1 volume for share iscsi to ESX two Hosts with same iscsi target iqn.

So one (first)  ESX have config dynamic  discover iscsi target and format block size finish, So ESX have new datastore come from iscsi.

So another ESX need to connect with same ip of iscsi target and same iqn target. then discover iscsi and  rescan datastore have show datastore name of  same name that found on first ESX.

( note for second ESX is not format block size but rescan HBA/VMSF have found same name of datastore  like  first ESX)

Question.

1. for iscsi target  that have one target and map to one volume on openfiler  can run with 2 ESXs same time with same target ?

2 .If not How i setup share storage with openfiler  that can used data same volume on openfiler?

Regards,

Bancha

[JPM300]

Hey BanchaTh,

When you setup an iSCSI target AKA your SAN/OpenFiler the IP address for that will always be your dynamic discovery for every ESXi host.  You will want every LUN/Datastore you share out to your ESXi host to all of your ESXi hosts so you can use vMotion/DRS, ect.

When you say how do you setup an open filer that can be used data same volume on openfiler? I'm not sure as to what you mean, can you clarify for me?

[BanchaTH]

Dear Sir ,

I mean. I'd like to share same datastore that create with iscsi tagget on openfiler and already format block size 1MB  from first  ESX.

So that mean i want to add this datastore on other ESX host.

On other ESX i discover iscsi target with same ip address of openfiler iscsi target and rescan VMFS/HBA and it can see same datastore name like map on first ESX server.

But i worry if same name that access same volume on iscsi target.Have any effect ? and This is can said "complete share storage with iscsi and  same LUN right?

Regards,

[a_p_]

Using the same LUNs/datastores is actually the concept of shared storage. ESXi uses it's own VMFS file system, which is build for shared access from multiple initiators (ESXi hosts).

André

[BanchaTH]

Sir,

So Is it right that i do this my config ?

and if i plan maintenance  my ESX. So i'm must disconnect static iscsi initiators on all ESX hosts. and It will take remove my LUN (iscsi openfiler) on datastore of ESX right ?

and if after finish. i add auto discover initiators and rescan HBA/VMFS it will auto remount LUN on my datastore ?

Regards,

Bancha

[a_p_]

There's absolutely no need to disconnect the storage for maintenance. However, if you are going to access the datastore from two stand-alone hosts - i.e. not managed by vCenter Server - it's your responsibility to ensure that the VM's on the datastore are NOT accessed simultaneously by multiple hosts!

André

[BanchaTH]

Dear Sir,

If i plan reinstall ESX and preserve data vmfs on local disk and data vmfs on  iscsi server.

So i must power off all VMs and disconnect static iscsi  session right ?

After i reinstall and i need to reconfig vmknel network and enter ip for discover iscsi target. So Question !

Can i used old data on iscsi server with recreate new VM and choose exciting file vmdk and power on VMs ?

(Some case i see when ESX fond iscsi target server it will force format old partition vmfs on my iscsi server )

Bancha

[a_p_]

If you want, you can certainly detach the "iSCSI" network cables from the host while re-installing it. However, the last time I disconnected the storage system (fiber channel) from the hosts for installation was in the ESX 3.x times. With iSCSI you should not need to be concerned anyway. Once you re-install the ESXi host, it will receive a new IQN, and without the iSCSI settings being configured properly on the host as well as on the storage system, the host woun't be able to access the storage anyway.

Once you configure the iSCSI settings, the host will detect the existing VMFS volumes, and you will be able to access the VM's again. If needed, open the Datastore Browser and right-click the VM's configuration (.vmx) file to add it to the host's inventory.

André

[BanchaTH]

Dear André,

Please see my config. My solution do any step like http://fojta.wordpress.com/2010/04/13/iscsi-and-esxi-multipathing-and-jumbo-frames/

but i can't enable vmotion on portgroup.

i mean when i enable vmotion on portgroup 1 as name  'iscsi_1' and try ebable vmotion on portgroup2 name 'iscsi_2'

when i habe done. it will have one portgroup show enable vmotion. what i wrong ?

(please see  that picture )

I think i apply with VMware KB:    Multiple-NIC vMotion in vSphere 5  but not  work How i can do this ?

Bancha

[a_p_]

Although it may be possible to run all traffic on only a few port groups with only two shared uplinks, I'd wouldn't recommend it. Firstly you should separate storage traffic from the production LAN, and secondly vMotion can easily saturate an uplink which will most likely cause issues with the other traffic on that uplink.

Btw. Multi-NIC vMotion has been introduced with vSphere 5. However, according to the screenshots, you are using the classic ESX version which doen't exist in vSphere 5 anymore!? Which version do you use?

André

[BanchaTH]

No Sir,

On vSwitch is only iscsi traffic but for portgroup 'service console' i make for test but no traffic in/out.

and concept for this vswitch1 is handle iscsi traffic to storage.

I test remove service console portgroup still same result.

This is ESX4.1 version.

any idea?

Bancha

[a_p_]

As mentioned before, Multi-NIC vMotion is not available with ESX/ESXi versions prior to v5. I guest that VMware prevents you from selecting two port groups for vMotion in this case.

André

[BanchaTH]

Dear Sir,

Ok maybe it not support on my version ESX.

So If now it can bring vmotion as one interface on portgroup. Is it ok ?

And Vmotion is only transfer config/index of config but real data file as stay on share storage  right ?

Bancha

[a_p_]

Like I said before, vMotion can saturate an uplink, so you will need to keep an eye on this. If you want to run vMotion on the same vSwitch anyway, I'd suggest you create a separate port group with private IP addresses (e.g. 192.168.x.y) for it, and leave both vmnics active for this port group to allow failover in case an uplink fails.

André

[Matt Brown]

I haven't used Openfiler myself but a quick Google search suggests it will support simultaneous connections for iSCSI VMFS volumes. As long as you have simultaneous connections enabled, both hosts should be able to see the iSCSI volume.

You may find this guide helpful (references ESXi 3.5 but the steps are the same for 4.x and 5.x) : http://techhead.co/how-to-configure-openfiler-v23-iscsi-storage-for-use-with-vmware-esx/