the iSCSI LUN mapping

Similar Questions

• 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

• Impossible to check inside of the iscsi LUN using open file server

  Hi all

  I use workstation 11 on my laptop

  and I can't seem to add the iscsi drive that we installed on nas box

  kindly help

  Dear Madlabs

  Please search for dynamic discovery of your nas box assuming that you have configured a static IP for it

• 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!

• 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é

• Extend an iscsi LUN without losing VM

  I created originally for my data store a 500 GB iSCSI VMFS LUNs. I noticed that I had more available SAN storage, so I increased the size of 500 GB to 1.3 TB LUN LUN for our VMWare data store. I currently have a VM DC on this LUN I want to thank. When I go to the store and add the extension, it is said that the drive will be formatted and all data will be erased. There is a host of ESXi v3.5. What is the best way to extend this LUN without losing my VM domain controller?

  Should I try to move the virtual machine to the internal storage using the browser to store data? What do I have to use VMWare Converter to move the virtual machine off the iscsi lun until the LUN is extended, or is there another way? With your recommendations can also provide you with exact to directions?  It is a production environment, and I don't have a lot of experience, make this type of move.  Your comments are greatly appreciated.

  Hey Monty,

  One thing to remember, whenever you play no matter what sizing such thing w.r.t. the LUN always take relevant backup and can do what you want to play. The error you get is the error for the new extend this when adding, all the data on the new measure will be lost, so certainly, you can spend without any hestations.

  Concerning

  Anil

  Save the planet, go for green

  If you have found my reply to be useful, feel free to mark it as useful or Correct.

• Error creating the store of data on iSCSI LUN (EMC CX4/120)

  I run an error when you try to create a data store on a Clariion CX4/120 system.  Connectivity to the San is performed via iSCSI.  I exhibited with success the target on the storage card and it shows in Configuration > storage adapters > vmhba33 > Details.  It has a capacity of 5.37 to.

  When I go to Configuration > storage and select Add..., I can select the disk/LUN.  The LUN appears here as well.  When I click Next, it fills the device information and location and also reported "the HDD is empty."  After 10 minutes, it generates the following error...

  Call "HostDatastoreSystem.QueryVmfsDatastoreCreateOptions" of object "ha-datastoresystem" on ESXi '172.20.100.78' failed.

  I did some research on Google and looked around here on the website of VMware, and I can't find any references to this error.  Are there log files for the process that I can look into?  I must engage EMC and see if there is a problem with the SAN itself?

  It has a capacity of 5.37 to.

  VMFS data storage limit is 2 TB less than 512 bytes. Try presenting small LUN, then it should work.

  André

• helping the 'physical LUNS and data mapping file store.

  All the

  HELP REQUIRED PLEASE?

  I have a windows VM, which must be connected to a load of RAW LUN mapped. These LUNS (storage symmetrix btw) were all presented through their esx host and were confirmed by the SAN guys and myself. The question I have now is how can I confirm what the label of "vml.xxx" for each raw mapped LUNs (I can't scroll all the way to confirm what it is!). I need this information so I can marry until Dev ID is presented in which logic unit number. The virtual machine is running and needs to stay on as long as its prod. So my question is, is there a way to know what the full title of the map file is please?

  Check the attachment below which shows a "gross mapped lun" properties and its inability to scroll to the end to copy the mapping file name complete.

  Thanks in advance

  Munster

  1, vmkfstools - q, you get the vml.xxx

  2, esxcfg-mpath - b d vml.xxx you get it naa.xxx and what is the lun number

  3, esxcfg-scsidevs - l d vml.xxx you get more information about that lun

  Binoche, VMware VCP, Cisco CCNA

• Label of the ASM to name of LUN mapping; Are not even necessary device names when you use ASMLib?

  = Environment details start =.

  OS: Oracle Linux 6.4

  Version Infra grid: 11.2.0.4

  Storage: EMC VMAX

  ASM Lib version:

  # rpm - qa | grep oracleasm

  oracleasm-support - 2.1.8 - 1.el6.x86_64

  oracleasmlib - 2.0.4 - 1.el6.x86_64

  oracleasm version came not in rpm-qa output may be because it is part of the Oracle Linux kernel. But the 2 components above are not

  = Environment details end =.

  We have a 2 node RAC cluster.

  We wanted to add 2 LUNS to our data Diskgroup and asked team storage available to both nodes of the cluster.

  After that they provided, the Linux Admin scanned the LUN and powerpath device names were generated. The powerpath device names like SCSI logic unit number names are incremented sequentially. Because, two additional powerpath LUN used to Node1 to a local file system, the names of powerpath were incrementing differently in the two nodes.

  Thus, for the same LUNS emcpowerpath names differed in Node2. Linux Admin did not notice this difference. And he told us the names of newly added from Node1 LUNS powerpath that have been

  / dev/emcpowerv

  / dev/emcpowerw

  But in Node2, the same LUN were appointed

  / dev/emcpowert

  / dev/emcpoweru

  The DBA guess powerpath name these 2 LUNS will be same on Node2, label the discs to help

  oracleasm createdisk DATA17/dev/emcpowerv1

  oracleasm createdisk DATA18/dev/emcpowerw1

  After marking in node 1, the DBA ran scandisks in Node2. But while the oracleasm scandisks in Node2 is running, it does not seem to/dev/emcpowerv and/dev/emcpowerw in Node2. Instead, ASMLib is smart enough to read the LUN ID in Node1 and search devices powerpath with the same LUN ID and labels as Node1. What's it like in Node2, / dev/emcpowert is labeled DATA17 and/dev/emcpoweru is labeled DATA18 correctly, as shown below.

  Node1

  Node2

  LUN ID

  Label of the ASM

  / dev/emcpowerv

  / dev/emcpowert

  873F

  DATA17

  / dev/emcpowerw

  / dev/emcpoweru

  629:

  DATA18

  Confirmed using the oracleasm querydisk Pei/dev/emcpower < x > .

  During labelling using the oracleasm createdisk , since we use the LUN name I always thought that asmlib dealt only with the names of devices (Powerpath name in this case). I didn't know that ASMLib treats ID LUN. If ASMLIB faces in LUN ID internally, then you don't need to have the same name for a particular LUN for disks shared in different RAC nodes? Right?

  ASMLIB contains 3 packs. Oracleasmlib, which is distributed under a license of Oracle user space and is not part of the standard GPL software distribution. Oracleasm-support, which is in the standard repository and kernel driver of Oracleasm, which is included in the core Oracle UEK only or distributed by Red Hat to RHCK kernel. The subsequent RHCK driver requires a Red Hat subscription. You need all 3 installed packages.

  ASMLib doesn't care to the SCSI ID or device names. When you configure a device to ASMLIB, he writes a header special disk in the device, the command scandisk read and identify a device. ASMLIB devices are populated under the tree of device/dev/oracleasm and found by ASM using the default ORCL: device chain.

  Don't forget that ASMLIB does not work with multiple devices and if you use DB-Multipath or EMC Powerpath, you need to blacklist the physical devices so ASMLIB will use powerpath or multipath device instead. Otherwise there will be no failover devices like ASMLIB will simply use the first device found and ignore the other. Check the following:

  http://www.Oracle.com/technetwork/topics/Linux/multipath-097959.html

• not visible on the ESXi LUN iSCSI hosts

  So I have a bit of a strange and hoping the community can help me to understand. In my lab at the House, I have 3 x ESXi 5.1 Build 799733 hosts x 2 guests are the same hardware (BUD Intel) and the other host an old HP flat desk. I am running CE Nexenta 3.1.3.5 on a Microserver HP which provided the iSCSI storage to HP desktop computer. The 2 new Intel NUC VMware hosts however, I am unable to get any iSCSI storage visible to them. Software iSCSI adapter is enabled, peut vmkping storage to the host and the target will appear on the static discovery tab. The configuration appears to be identical between the 2 However, the hardware is different... I have a new analysis on the host and no devices appear. Now the obvious answer is there must be a security issue on the side of Nexenta... but the 3 hosts are all part of the same group initiator. Confirmed and copied the IQN name over and over again. I still think that this is maybe a matter of Nexenta, but maybe it's something else.

  Check the vmkernel.log file contains the following information after a new analysis...

  (2013 06-09 T 23: 49:06.160Z cpu3:2933) VC: 1547: device rescan time 17 msec (total number of 5 devices)

  (2013 06-09 T 23: 49:06.160Z cpu3:2933) VC: 1550: Filesystem probe time 85 msec (4 of 5 surveyed devices)

  (2013 06-09 T 23: 49:06.412Z cpu3:2931) Vol3: 692: could not read the header of control volume: unsupported

  (2013 06-09 T 23: 49:06.412Z cpu3:2931) Vol3: 692: could not read the header of control volume: unsupported

  (2013 06-09 T 23: 49:06.412Z cpu3:2931) SFS: 4972: pilot no. FS claimed "on the remote control": unsupported

  Anyone got any ideas?

  Problem solved.

  Appears that it was a problem of connection iSCSI ports. There is only a single teddy bear in each of these hosts and allowing the port bindings vmkernel on initiator iSCSI under 'Network Configuration' result not being iSCSI target devices is not visible. Removed the vmkernel port binding and made a new analysis. Cameras then showed upward.

• Query on LUN mapping

  Hi forum,

  We have MD3200 I array (iSCSI). We have a LUN 1 TB mapped to a host group that contains 2 servers (Linux).

  Now, we want to map this LUN on another Windows Server. (but do not want to remove the previous mapping).

  Is it possible and if possible will have no impact on performance.

  Thanking in advance

  J.P. Raynaud

  Unfortunately, if I understand you correctly you want to have the LUN to be mapped to Linux servers, and also on a Windows host, which is not a good idea. The reason is when you try to map the same LUN 2 different types of OS you will corrupt your data. What you want to do, is to have a virtual drive for Windows Welcome. This a medium VD would be for Linux and one for Windows and the performance would be great like that as well. I hope that answers your questions.

• LUN mapping - duplicate Monday in ESXi

  Hello

  We have NetApp array with iSCSI to ESXi 5.0u1 servers.

  I'm trying to see if I can identify the iSCSI devices presented to the server ESXi as LUNS created on NetApp. So far, I was under the impression that this mapping must be one for our Installer, but this doesn't seem to be a case:

  That's what I see in the list of devices on the ESXi server. As you can see, the Monday is the same, but the size is different.

  

  Table of NetApp, a single LUN with LUN ID 4 (with 64 GB size) is presented. First initiator group is not used.

  

  This means that ESXi server MONDAY mapping is out of sync with NetApp table?

  How would I be able to identify the LUNs then - I thought that Monday would be a unique identifier, but now I'm at a loss.

  We use RDM in virtual mode, if it allows to specify the configuration.

  Thank you!

  The two LUNS have IDS unique naa. This makes the host thinks that those who are in fact different SCSI devices.

  One of your LUN has a duration of vmhba40:C0 name:T0: L4 while the other has vmhba40:C0:T1: L4, they are behind different targets.

  I would first of all check the initiator groups who have included concerned host iqn and check the unit number logic on NetApp, looking for a 8 GB LUN mapped to one of these groups.

  If you have integrated with vCenter VSC, you maybe more comfortable for the task above (I wish :))

  To ensure that you are on the right at a given time (i.e. before removing the LUN mapping or the number of unit logic itself, in which case you think, it is necessary), you may need to compare the serial number LUN with NAA ID reported by ESXi.

  The only way I have found so far is NetApp CLI: lun - x series

  This returns the serial number hexagonal LUN that actually fits NAA ID seen by the host. The drawback here is that you must specify a path for each LUN to check which can be a considerable effort if you have 100 LUNS to check.

  If anyone here knows better, please share!

  WBR

  Imants

• Access via SSH o/s RN102 iSCSI LUN

  Hello

  I can access NAS via SFTP & SCP.

  Where in the structure of the file is the LUN file so that I can copy off the coast of the NAS for editing also.

  We have an iSCSI partition that is only considered as RAW by the iSCSI connector in Windows and we need to see if he really is totally damaged,

  The data\LUN file appears to be empty.

  Andy

  It's in a hidden directory .iscsi

• The ISCSI initiator problem

  Another problem of beginner.  I learned a lot about my new virtual world, and the box Logic Equal Dell.  But I still have a fundamental problem that must be an easy fix, or something I do not understand from a technical perspective.  I want to be able to connect to a snapshot and be able to recover a file if necessary.

  I brought the snapshot online and I could even get on vSphere so I could see him there.  But, for the life of me I can't all iscsi initiator to see the snapshot at all.  I have a few guesses, but I can't seem to understand my problem.

  I can't get the initiator to see all the targets... it just tells me the connection fails.  I think I know why, but my skills of network management are not real strong.  When we had an outside company come in and set up the environment, they put everything on 192.168.100.x or 192.168.101.x.  Since I arrived here (more than 15 years ago), our network has always been 129.1.x.x ip addresses.  I'm programmer for the most part and I got a guy of networking which is solid to the networking but I don't know if he can answer my question either.

  In any case, when I try to add my portal target to the initiator, what IP address or the name am I supposed to point to?  I can't ping the 192 addresses because I'm on an IP 129.1.x.x, correct?  So, this is why I have no chance to find snapshots using the initiators?  I know the vCenter server has an address 129 and the SAN itself has a 129 address and I tried to connect to who but did not work.

  I think I gave permission to the snapshot to be seen by several initiators.

  I think it's my lack of networking, but maybe not.  Any help would be greatly appreciated.

  Thank you

  Ryan Kotowski

  The snapshot will not be a set of files that you can view. This will be a copy of exactly what the LUN looked like when you took the photograph, you need to mount it in vSphere just like you would ride the regular LUN. Then you will see all the VMX and VHDX files for virtual machines that you instantly. Then you can add one in vSphere and power to recover his files. Don't forget that you'll want to disable networking all on this virtual machine so that it is not in conflict with the actual VM on the network.

• 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-