ESX 3.5 and iSCSI LUNS

Similar Questions

• VCB server with both FC and iSCSI connections

  Hello.

  Anyone know if a VCB implementation that has the FC and iSCSI LUN presented to the proxy server is possible/supported?  I see no technical reason that it wouldn't work, but I'm trying to understand whether or not this is a supported configuration.

  Thank you!

  I don't see why that would be a question of a standpoing of features, but if you didn't mind the performance hit you just the business day following mode of transport and not worry present LUNS.   I guess that maybe in the same way hotadd would work as well.

  If you have found this device or any other useful post please consider the use of buttons useful/correct to award points

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

• ESXi 4.0 - attached an iSCSI Lun and you want to import a VM to...

  OK, I have attached an iSCSI LUN that has a couple of VM on it from a previous generation test. Now, I want to import those virtual machines to my ESXi 4.0 host. Can someone give me step by step on this operation method?

  You'll just want to browse the data store, right-click on the VMX files and select Add to the inventory.   After you have added, you will want to check the network label to ensure that it exists on the new server.  If one of the virtual machines have been using VMdirectpath, generic SCSI devices, etc. you'll want to update those as well.

  Dave

  VMware communities user moderator

  New book in town - Start Guide quick vSphere -http://www.yellow-bricks.com/2009/08/12/new-book-in-town-vsphere-quick-start-guide/.

  You have a system or a PCI with VMDirectPath?  Submit your specifications to the unofficial VMDirectPath HCL - http://www.vm-help.com/forum/viewforum.php?f=21.

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

• ESX 4.1 and Openfiler 2.3

  Hello

  What follows refers to a test environment.  He gets blown a few times per month.

  I used ESXi 4.1 and openfiler 2.3 without any problem. (Openfiler is used to provide iscsi storage)

  Then I tried using ESX 4.1.

  So I rebuild my two ML115 of (zapping all warehouses of data, vm, batch) and created a server virtual openfiler both to serve as a shared storage.

  So far no problem, both ESX hosts saw two iscsi data warehouses.

  Now I wanted to install a new virtual machine... again no problem.  I can create the virtual machine.

  Now, I want to install Windows 2003 on this virtual machine.

  I get to a point where the Windows operating system files are copied to the C: drive and that's where the problems begin.  The progress bar (indicating what percentage of files windows 2003 have been copied) 2% (sometimes less) and then everything becomes insensitive.

  Not only 2003 does not install, but the entire army becomes insensitive... the only way to solve the problem is reboot the host.

  Is there a problem with Openfiler 2.3 and 4.1 ESX.  He charges advanced for iSCSI in ESX and openfiler attributes but I don't know what would solve the problem (I've tried a few comments on the basis that I've read ut no joy).

  As I said that esxi 4.1 worked a treat.

  Thank you very much.

  p.s. I read various assignments related to the presentation only to a host iscsi LUN.  But I still get the same problem.

  p.s. I have only a single 160 GB drive in each ESX ML115 and the data store to share this record.

  PPS each host only has a NIC... This is a test environment.

  I use Openfiler 2.3 as an ISCSI target for ESX 4.1 for Dev environments all the time. It works very well! One thing that I found will help performance to "write-back" and "fileio" when you map the lun. I don't know why, but it seems to provoke the Openfiler to use the available RAM on the server as the write cache.

  Why your fails Openfiler is problematic, I've known occational hickups when you try to use the network mask to try to limit the number of guests who can see the iSCSI target, for example establishing a network of 192.168.1.11/32 on the Openfiler to hide the lun to an ESX Server.

  Good luck!

• MS on NFS and iSCSI with cluster?

  Clustering for vSphere management guide States that only storage fibre channel is supported of the CF/MSCS clusters, so I'm sure I already know the answer to that, but...

  I have a client who wants to run a NetApp storage solution active cluster failover, configure the disks in the operating system for Windows 2008 R2 servers on an NFS volume and application driven on a DRM iSCSI data.  IOPS / s and network side, someone set up a cluster like this before, and if so what were your experiences?  I'm just trying to get an idea of what kind of potential problems to wait on the road.  I also assume that VMware is not going to support because they advise against it expressly.  Thoughts?

  
  
  -Justin

  According to me, that it will simply not work. ISCSI initiator Software in ESX/ESXi does not support persistent reservations SCSI-3, which is required by MSCS on 2008 and above. With the help of the RDM will not change it. I don't know if iSCSI HBA will work.

  The workaround for this is to use software iSCSI initiator inside 2008. Operating system can sit on NFS datastore. Quorum and the data must be on iSCSI LUNS connected via the Windows iSCSI initiator.

• How to get the host ESX DR see replicated Celerra Lun

  Hi guys, Im setting up SRM with 2 x NS20 and ive got regarding the configuration of the LUN on the production storage array, Lun on the storage LUN appropriate to prod/dr esx servers present DR Bay. Ive set up replication and added the DR lun to the esx server, ensuring not to add it as he will write a signature. I've then added the production on the production ESX Server LUNs, added storage which obviously writes a signature on the drive, and with the installation of the replication, I expected to simply issue a new analysis on the DR esx host and do see the data store.

  Am I missing something here? Any help would be appreciated.

  Thank you

  Hello

  "On DR NS ive done exactly the same thing with respect to FS, Lun, target iSCSI and presented to the host ESX DR, ive done a rescan and his picked up the lun 'Read Only', which is being replicated in but the tab of summary in VC, I see that the local VMFS file system and I was expecting to see the replicated LUN listed with the store local data or is this seen only". When SRM changes the properties of Lun during a failover? »

  You will not see the Site recovery volumes listed in data warehouses, unless you do one of two things - a failover in which case the production side will be unalterable and be removed from the list of data on the Production side store while exposing the VMFS data store now read-write on the side of the recovery.

  Or you use the test function in which case that encourage a wink of Celerra temporary writable and it will appear as a data store broken in the list on the side of the recovery VMFS data warehouses.

  However, it seems that you do not see this result, as DR table does not seem to be configured as it should.

  Can the side Production VC communicate with happiness with the Celerra recovery site - IE can launch you a session PUTTY from the Production side VC and connect to recovery side Celerra. Can the recovery side VC do the same thing for the Production side Celerra?

  I guess you get the unknown peer after that MRS. not the discovery of the table that owns about 23% forever and then ends. The only other thing I can think of and am not sure about this as a solution because it is a set of actions that I did of my side of recovery when Celerra is to create a small file system and in a small iSCSI LUN on the side of the recovery of the recovery side Celerra and put it in your recovery ESX cluster side - create a file system VMFS on it and place a Virtual computer in this VMFS file system - this is to check that there are no problems with the ESX host side recovery working with the recovery side Celerra

  My guess would be a thing of IP connectivity - if it's a little strange, if the link between the Production side VC and the recovery side VC has been established successfully

  I'll pass on to a colleague to VMware SRM and see if he has any ideas

  Concerning

  Alex Tanner

• 2 questions - group leader and iscsi

  We have a unique PS6500 of the firmware 6.0.5. From 3 days ago, Archbishop Grp freezes when I click on the member icon. I could go into all the rest of the GUI with no problems. I got the firmware installed for about a month, so I don' t think that is the problem. Has anyone else seen elsewhere?

  2nd edition - we have vmware hosts connected to QE through private switches. Vmware hosts have separate vswitches for vmotion and windows iscsi volumes. VMotion is on 10.2.0 subnet and iscsi volumes are on 10.2.1 subnet. The EQ is on 10.2.0 with a 255.255.0.0 mask. The switches are set with the VLANS separated for iscsi and vmotion.  So far in Grp Mgr, I allowed on each volume 10.2. *. *. I started to try to change it so that the vm volumes only allow connections from 10.2.0. * (vmotion subnet) and volumes windows only allow connection of the 10.2.1. *. Currently, I do not use chap or iscsi initiator to limit. Here is an example for a windows volume.

  But here is what I get in the Connections tab for this volume, even after a new analysis of storage host adapters:

  So either I completely ignore the setting of the limits of intellectual property, or my EQ has a problem. Shouldn't I have the 10.2.1 connections to this volume?

  Any ideas? Thank you.

  None of the fixes listed in the 6.0.6 release notes apply to my EQ,.

  BTW, you can add the ACL CHAP to the EQL live volume.  This will not affect existing sessions.  Just make sure that you first create the CHAP user on the table.  Then after setting the ACL volume, set the iSCSI initiator ESX to use CHAP.

  If you take a look at the RPM, you can find a few Commons left default setings.  There are some that will improve performance, other stability.

  vMotion has not EQL access at all.  It's strictly for compose the image memory of a computer virtual from one host to another ESX host.

  Storage vMotion includes EQL, but it does not use the port of vMotion to do anything.

  vMotion traffic must be completely isolated, because the content in the course of the transfer are not encrypted.   So no VM Network exchanges should be on this vSwitch and the physical switch should be isolated too.

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

• Recommend bridge SCSI and iSCSI

  Hi guys,.

  Currently I have an ADIC FastStor 2 tape auto-chargeur connected to a physical machine, Backup Exec 12.5, which backs up our running VMS with internal agents. Our ESX host running ESX 4.1, running on servers of 4 HP DL380G5.

  We are looking into converting to a more focused VM disk backup over the next 9 months, but we have a short-term obligation to upgrade our current solution quickly so that we can remove the material (it has long been out of support and our backups start to fail). To this, looking at a quick upgrade to BE2010 R2 (since we have already supported) and put us the media server on a virtual machine. Remains to be seen how to connect to the tape library. A SCSI and iSCSI Bridge seems to be the best option to do it quickly and with headache less.

  Someone at - it experience with these devices? Recommendations for an individual? The current tape drive uses a connection of Ultra2 SCSI wide 68 pins.

  Thank you

  .. .After research forums and seeing the difficulty that people have, I wasn't convinced.

  The positions of 'problem' I see the most are those who use cards non - of Adaptec SCSI and / or not parallel SCSI drives.  The most recent posts I've seen are for tape drives, SATA or SAS drives.  Basically trying to use 'new' band players, rather than reuse the 'old' band of readers.

  Quick is the main concern here. The money is available, it cannot simply be a ridiculous amount since it is monstly going to be throwing next year (otherwise I'd just go straight for an iSCSI tape library).

  Then I recommend the SCSI card because it would be cheaper than a bridge.  Or if you have an existing workstation you can re-tasks to host your tape drive for awhile so that get you the rest of your new backup equipment.  Used & refurb workstations can be made for well under $ 500 and often as low as $200 and would be more powerful enough to accommodate a tape drive.  Because you can reuse the workstation after obtaining new equipment, you could get something more than the bare minimum for this project.  Maybe it's a better use of $$$ instead of a bridge iSCSI that you go to "throw".

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

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