Shared the Datastore (iSCSI / LUN)

Hello

Here is my configuration:

3 x HP DL380p

2 x Netgear ReadyData without (21 to each)

I installed on each server ESXi and vCenter running and working.

What I want to do is to create a data store on each of the San via iSCSI so that all 3 hosts can access them, so that if a virtual computer fails it is lit by the next available host.

So far I figured out how to add a NFS share to each of the hosts with the same data store but can't seem to do it with iSCSI.

Can someone give me a break down of what I have to do?

See Chapter 11 of the http://pubs.vmware.com/vsphere-51/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-511-storage-guide.pdf

Tags: VMware

Similar Questions

  • Two displayed like device the same ISCSI LUN? I'm very confused...

    Hello

    I have a little problem that I can't get my head around. I have two ISCSI Thecus SAN devices on two separate subnets.

    Thecus1 is on 192.168.17.155 and Thecus2 on 192.168.18.156

    I added both in the SW initiator but one show in the storage view.

    When I look in the devices it shows a single disc, but when I look in the paths - it shows two.

    It seems that vmware is the same device two separate paths for a reason any. Where it should show two separate devices and a path to each! Does anyone have anyone pointers or advice to help? I just can't get my head around it all. Ive restarted it this way. I think that the thecus runs some open

    source ISCSI stuff under the hood, but that really shouldn't affect what I do not. These boxes are marked 'VMWare ready' show should be compatible. I contacted Thecus support but they isn't much use. When I look on the thecus iscsi targets I see the attached both esx host. I would add also, I have two hosts, both with the same problem. Each thecus has received a different logical unit number ID, we have 1 and 4.

    Gahh... I hope it's something obvious I've missed.

    vm1.png

    vm2.pngvm3.png

    Your table exports the two volumes with the same UUID (WWN) so ESX think it's the same volume via different paths.

    Your provider of storage have you will tell how to fix this.

  • How to use a larger than 2 TB iSCSI LUN?

    I have a server ESXi (4.1 U1) connected to an iSCSI NAS network, where 4 LUNS have been defined and presented to this host. all LUNS are 3 TB in size. ESXi correctly sees the LUNS and recognizes their size 3 to.

    I know that the maximum size for a VMFS data store is 2 TB, so creating a single data store for each logic unit number would be a waste of space. I know also that the creation of multiple data on a single LUN warehouses is not recommended, and it does not seem work either: If there is already a data store on a LUN, the just vSphere Client won't let me create something else here, it is not even list it in the list of available devices for the creation of data warehouses.

    I know that I can use extensions to create a store of data from more than 2 TB, but it seems to work across multiple LUNS: when I try to increase the size of a data store using the same logic unit number where he resides, ESXi is trying to increase it in fact, it won't go above 2 TB in size.

    My question is: is it possible to combine two extensions in the same logical unit number, so actually creating a composed of 2 extensions 1.5 TB 3 TB data store?

    If this is not possible, is it possible to create two data warehouses in the same iSCSI LUN? I know that this is not recommended, but it should at least be possilbe... but looks like it's not.

    If this is not possible, then... How to make use of these 3 to LUN?

    You can carve up the LUN and then it recombine.

    How to use these LUNS 3 TB is to get rid of them and the re - present as< 2tb="">

  • ISCSI LUN appears not

    I'm having some trouble to make the new iSCSI LUN to appear, I created. I've included some screenshots of my set up.

    Thanks in advance!

    Paul

    OK, but vol1Share is limited a.58. Did you mean a shorter mask as 255.255.255.0? the 255.255.255.255 signifie.58 et.58 only. Your ESXi is sur.60. Another poster has noticed the spec VLAN that has to go. You did not show pages discovered properties of the iSCSI initiator, but maybe you got that too. I have all this software run here and screenshot can't do anything that you can't go, but for now, you have not shown all the pieces and parts that show you matched lot of information.

  • a new datastore iSCSI (disk/lun) appears in the inventory. Warehouses of data, but not availble for quick vMotioning...

    Hello

    We have added the new datastore iSCSI (disk/lun)

    This new data store appears in the inventory. Warehouses of data, but not availble for quick vMotioning or the creation of a new virtual machine.

    did we miss a step?

    Ty

    r

    The reason is that the data store is not presented to all hosts in a cluster. When you create the VM in vCenter Server, only warehouses of data visible to the host on which the virtual machine is created are displayed.

    Make sure the presentation on your storage system is correct and rescan your hosts.

    To check the above, take a look at the Configuration-> Storage for guests.

    André

  • Stream access to the ISCSI LUNs on esxi v4

    Greetings,

    Wonder just anyone could throw me some lights on it?

    Esxi v4 does support stream access to a single lun? The reason behind this is I want to consolidate LUN based on roles (exch, file, etc.), that is to say, a lun (datastore) will host all the servers exch only running on different hosts.

    Thanks in advane.

    Felix

    Hello

    Yes No... multi host access to iscsi LUNs is possible... that's what san / storage isa he's shared on the subject. Just make sure that Suur iscsi luun u plan on using is in the list compatibilityy supported so that u get the support of vmware in the future if you need. ESX / ESXi have a clustered file system.

    TM

  • How to get the runtimename of the Monday using iscsi LUNs

    Hello

    IIS there a way to get the name of length of scsi LUNS being given the lun id?

    For example, please take a look at the attached capture where I want to get the identifier (identifier of naa) in view of the number of LUNs, say 11 (the first line of the snapshot)

    Thank you!

    That you will get the link between the identifier and the Monday

    Get-VMHost MyEsx |
    Get-ScsiLun |
    Select CanonicalName,
        @{N="LunID";E={[int](Select-String ":L(?\d+)$" -InputObject $_.RuntimeName).Matches[0].Groups['LunID'].Value}}
    
  • You see only not iscsi LUN, attaching to add storage

    I'm newish to the whole thing vmware/iscsi, but got it to work once.

    Environment:

    HB BL460c (32 GB of ram, 2 x local 146 GB SAS HD, nc382m HBA)

    vSphere ESXi 5.1

    MSA2012i (12 x 1 TB HD)

    I created a vswitch (VMkernel Port) to port1 of the nc382m (vmnic2) and then added the virtual iscsi adapter to connect to them.  A re-scan one I could add the LUNs available on the MSA as storage on the esxi host.  Everything was fine.

    But, I created a second logical unit on the MSA number (it is shared to all hosts) and I re-scanned on the esxi, but when I try to add storage no LUNS are listed.  I followed the same procedure as the initial installation, which worked fine and now no joy.  I searched the forums for ideas but not so far seems applicable, since I was able to do this for a single logical unit number but can now add a second logical unit number.

    Kind regards

    Marshall.

    The issue has proved to be a bug/flaw in the MSA.  The MSA I use has only a single controller/processor storage and apparently regardless of whether it has one or two SPs it assigns new vDisks of alternately between both SPS 'potential '.  So in my case the first vDisk was entrusted to SP - A and worked beautifully.  The second vDisk was assigned to the same SP - B hard did not exist.  Therefore, it was not visible for ESXi hosts.  Change of 'ownership' of the second vDisk lun was visible on the ESXi host.

    Here is a link to HP Customer Support Advisory about this behavior:

    http://h20000.www2.HP.com/bizsupport/TechSupport/document.jsp?lang=en&cc=us&TaskID=110&prodSeriesId=3687128&prodTypeId=12169&ObjectID=c01470001

  • How to clean and do a fresh install with attached iscsi LUN?

    I intend to migrate both esx 4.1 with esxi5.1 hosts before you wipe and do a clean install.  Each host is connected to two iscis without, with 4 LUNS of each SAN attached to each host.  Each lun
    spread over 3 degrees is. I plan on vmotion (not storage vmotion) guests from one host to another to make the upgrade.  I'm stuck on the determination of what will happen to the iSCSI LUNS after I
    upgrade to esxi5.1 guests.  It seems that I should just be able to reattach, but I'm not sure.  Can I just attach the LUNS to the new installation 5.1 hosts and see all the
    VMDK intact, or is there something that I am on?

    And should the migrated to another host virtual machine continues to run on the iscsi san, while I upgrade of the host, they were released since then?  It seems that storage must be removed from the process as the LUNS
    should not remain attached to the host after it is cleared and the iqn name no longer exists.


    Am that I on the right track here?  What Miss me?

    jackjack2, understand you this? I went ahead and moved to esxi 5.0 U2 of ESX 3.5 u5. Had to perform clean install and I have an iSCSI SAN. That's what I did:

    1 a taken a screenshot from all my ESX host configurations. Go to configuration-> software adapter-> click on the iSCSI--> properties--> iqn copy map and alias-> click the dynamic discovery tab and note any IP address. You may need these IPs with the discovery of data warehouses later.

    2. after having documented the configs, put the host in maintenance mode.

    3. after maintenance, remove the host from the vcenter server. Connect directly to the host and close.

    4. remove all the network cables. Cable marking help before you detach the cables.

    5. clean install esxi 5.0.

    6. after installation, before rebooting, set the network cables.

    7. configure and test the management network. If your network management test fails, see if you have anything that is entered in the id vlan. Chances are that your port is not shared resources in the physical switch. In this case, remove the id vlan (during the configuration management network) work.

    8 bring the vcenter server host.

    9 configure the network, dns, time, etc.

    10 Add a software iSCSI adapter. This card will have a new iqn. Either you provide this iqn to your SAN administrator so that it can update side SAN, or you can use the old iqn name.

    11. in my case, I made a copy of the new iqn and then deleted. Entered the old iqn name obtained in step 1. Additionally, entered the alias (since one was present before). After that, a new analysis and update still does not fill in data warehouses. So, I went to the properties of the iSCSI adapter and then discovered added tab dynamic addresses IP that did not exist before (otherwise, you will need to enter the virtual IP address of the cluster that you data store (s) belong to). Once the IP addresses have been added to the dynamic discovery tab, he asked if I wanted to rescan the HBAs. I said yes and viola! my data stores have been populated.

    12 Add the host to the cluster.

    Note that you can add iSCSI adapter when you affiliate you the host to the cluster. However, in this case HA will not be happy because no heartbeat of data storages will be detected. In addition, when data warehouses are discovered it may appear initially as not mounted. Don't panic. After a minute or two it will be mounted.

    I hope this helps!

  • Attach an iSCSI lun to 5.1 and 5.5 to move virtual machines

    I have 1 Server esxi 5.1 I've built a bunch of VM now connected to a 4 TB iSCSI LUN.

    I gave recently 2 new 5.5 servers.

    Ideally, I would like to connect these 2 servers to the same lun iSCSI is used by the Server 5.1. Then, stop/forget each VM on 5.1, browse the data store on 5.5, add to the inventory and it start up. After all the machines are moved, I can do some changes on the material on the Server 5.1, it blow and install 5.5.

    I plead for the trouble, or is a reasonable way to do?

    Welcome to the community - Yes that works-

  • ISCSI Lun gone after restart ESXI-home

    Hello

    I have 2 hosts 5.1 ESXI and QNAP 1 for iscsi storage.

    When I restart a host, a logical unit number is gone (other Lun 4 is available).

    I have the following procedure to resolve this problem:

    # esxcfg - volume - m "vmfs_label_name".

    and then refresh data warehouses in my configuration.

    What happens after each reboot the ESXI host.

    As I say... the other 4 LUNs with the same configuration do not have this problem.

    How can I fix?

    THX.

    esxcfg-volume - m "vmfs_label_name".

    Using esxcfg-volume-M

    M must be capital because it would be persistenet to reboot

  • ISCSi LUN Vmware question

    I have two luins iscsi for vmware build hook etc. up to an emc celerra server.

    question-

    If I extend the iscsi on celerra lun in vmware puts it auto-mattically updated space iscsi LUN or is there more steps involved.

    Hello.

    There are more steps involved, after performing the operations on the Celerra.

    Use http://kb.vmware.com/kb/1752 as your starting point.

    Good luck!

  • ISCSI LUN

    Hi all

    It is possible to have a present LUN iscsi to a vSwitch with pool.

    I read the manual & quot; Configuration of the initiators iSCSI and storage & quot; but we know only this issue.

    My setup is therefore 1 vSwitch with two nick teamwork for all the computer's network traffic iSCSI and virtual.

    Thanks in advance.

    Kind regards.

    Yes, grouping of NETWORK cards is OK for iscsi, but it is recommended that no more than two cards network is used. See below for more information on:

    http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1001251

  • iSCSI LUN maximum

    So I'm looking at the documentation for maximum rates of configuration and it is said that the maximum LUN of Fiber Channel is 2 TB. This also applies to the iSCSI LUNS?  For example, I have an iSCSI LUN 5 TB ESX 'sees', but when I try to establish VMFS on it and add it to the usable storage, it allows me to choose the whole 5 TB, but only write 930GB and says "complete".

    I have to chunck this 5 to in max 2 TB LUNs, and then write my 5 to VMFS on multiple LUNS instead of one?

    Thank you!

    Yes, the limitation applies to iSCSI too. As you said already correctly, you must present the LUNS with Max 2 TB less than 512 bytes.

    The reason for this limitation, see http://kb.vmware.com/kb/3371739

    André

  • Retrieve iscsi LUNs

    Hello

    I have an iSCSI LUNS presented via OpenFiler to host ESXi 4 (standalone).  For some reason, the host has lost connectivity to the LUN and, of course, the virtual machines that were running.

    I reboot the host which did not help.  I can see the device THAT LUN is presented with success under the section of storage card from the vSphere client.  When I run through the Add Wizard storage, in the storage section, the disk is visible.  However in the next step of the wizard it ends by crashes with an error message "unable to get disk partition information.

    I don't want to just reset the partition table, and re-create the file system I want to retrieve the LUN and virtual computers that it contains.

    Any ideas?

    Thanks in advance,

    Richard

    Did you find anything in the newspapers of the OpenFiler? You have more than three LUNS on the OpenFiler? If so, this logic unit number could be a different LUN then what you think it is? Is there a chance that there is a windows or Linux machine that could have this locked LUN? Or you configured permissions so that those LUNS is available for this single ESXi host? The ESXi host for some reason any seems to think that this LUN does not contain a VMFS partition. The OpenFiler there snapshots of this LUN?

    If the ESXi host can see the LUN, I'd start looking for storage and see if you can find configuration problems there.

Maybe you are looking for