several host esx on an iSCSI LUN?

Similar Questions

• Adding more than one host ESX and the upgrade at the same time.  What is the order of preference of the operations here?

  We are budgeting for more licenses and hardware for 2014 and want to do immediately in January.  I am trying to decide what is the best order of operations for adding two vmware hosts additional to our current installation of vsphere and also upgrade our vsphere / esx 4.1 u3 for the latest and best.

  We have 3 Dell PowerEdge R710 running ESX 4.1 U3.  In this vmware cluster, there is a vcenter server 4.1 U3 virtual machine handle this.  The three servers are about 90% memory used so we add 2 additional servers.  Probably the Dell PowerEdge r.620 since we get up 2 in the space of a 710.  Storage is on a san EMC NX4 NFS which will become too but not yet, let's just deal with the vmware part.

  When adding additional r.620 2, should I install ESX 4.1 on them and join them to the existing cluster and THEN pass vcenter and each one esx?  I ask precisely because 90% of use on 3 current servers, I need 2 other servers to support the update operations take place.  They would be able to repel vmotioned vm while each host receives an upgrade at the same time.

  So which is the best way to go about adding of the hosts and the upgrade?  Would I add as 4.1, then they would be available as targets vmotion and so I have room to start the hosts one upgrade at a time?

  If I update vcenter to the latest version, it is comparable backwards and can manage the 4.1 hosts, but also hosts 5.x?  I guess version 5.5 is the last one I would get from VMWare?  It is right of ESXi, then, how is this ESX ESXi 5.5 4.1 upgrade?  How much storage space do I need for ESXi 5.5, as I'm dechatoiement out of these r.620 Dell and need to know what hard drive to put in.

  The steps that you must follow

  -Updated vCenter Server

  -Upgrade of the ESX hosts (because we do a updating of the material we will install 5.5 on our new guests and add them to the cluster and then dismantle our existing)

  -Upgrade VMWare tools

  -Update data warehouses

  ESXi 5.5 has these storage requirements:

  • Installing ESXi 5.5 requires a boot device is at least 1 GB in size. When booting from a local disk or SAN/LUN iSCSI, a 5.2 GB drive is necessary to allow for the creation of the VMFS volume and a scratch 4 GB partition on the boot device. If a smaller drive or logical unit number is used, the installation program attempts to allocate a region scratching on a separate local disk. If a local drive is not found, the scratch partition (/ scratch) is located on the disk virtual ESXi host, linked to the/tmp/scratch. You can reconfigure /scratch to use another drive or logical unit number. For best performance and memory optimization, VMware recommends that you leave no /scratch on the ESXi host ramdisk.
  • To reconfigure / scratch, see Configure the Scratch Partition of vSphere Client vSphere Installation and Installation Guide.
  • Because of the sensitivity of the I/O devices, USB and SD, the installation program does not create a partition scratch on these devices. Therefore, there is no tangible benefits to the use of the great features of USB/SD that ESXi uses only the first 1 GB. When installing on USB or SD, tent Setup devices to allocate a region scratching on a local disk or the data store. If no disk is local or data store, /scratch is placed on the virtual disk. You must reconfigure /scratch to use a persistent data store after the installation.
  • In Auto deploy facilities, Setup attempts to allocate a region scratching on a local disk or the data store. If no local disk or data store is found /scratch is placed on the virtual disk. You must reconfigure /scratch to use a persistent data store after the installation.
  • For environments that start from a San or use Auto Deploy, it is not necessary to assign a separate logical unit number for each ESXi host. You can co-locate areas scrape for several hosts ESXi on a single LUN. The number of hosts assigned to a single LUN must balance the size of the LUN and behavior I/O virtual machines.

• ESX 3.5 and iSCSI LUNS

  Good so I'm setting up my servers ESX using iSCSI LUNS.  I do not have the LUN in a VM, I want the servers to use.  Is it possible to do?  And how can I do for that implemented?

  Scott

  You must enable initiator initiator or software hardware

  If you go to the inititiator of the software, you must enable on each ESX host, by going to the configuration of the VI Client storage adapter tab. (you will see something like vmhba32, activate it)

  Once it is enabled, you must add your target (as we are talking about software initiator, it supports only dinamic discovery).  Recommendation, isolate the network cards that will connect to the iSCSI network.

  concerning

  Jose

• 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

• Unable to add a lun to esxiting to host ESX 4

  I'm not able to add a unit number logic esxiting presented to the ESX host to an esx host 4. I chose gt & Add storage; disk/Lun & gt; I chose the desired lun & gt; Keep the existing Signature & gt; Next & gt; Next & gt; Finishing. I get an error message "Unable to change the configuration of the host." I was able to add to the initial ESX4 host, but not a second. This is an existing lun created in ESX 3.5 the lun in question has two extensions added, which would explain the message "Warning" status on screen edatastore th. The warning does not appear in ESX 3.5, however.

  In my view, it is a bug, and in fact we have an open PR with VMware.  If you try to add the LUN back using vCenter, when you will encounter the error.

  Have you tried of you connecting directly to the ESX host and adding back?

• Presentation of ID host ESX host LUN to the VCB Proxy Server

  I have a typical scenario where I have 3 ESX servers with 3 x 800 GB LUNS in a storage group separate on a CX 310 SAN box. The host LUN., of these 3 LUN Ids are 0, 1 and 2.

  I have a specific host that starts from SAN, from the same box of CX 310 SAN. At this point of time, I have no choice to use this server as a Server Proxy VCB. As far as my knowledge goes, LUNS of the ESX servers must be made visible to VCB Proxy Server, as they are presented to the ESX servers.

  My question here is, as the designated Proxy VCB server is booting from the SAN, he already has a host LUN 0 to Id the logic unit number this is the start of. The Id to host ONE of the first 800 GB LUN in the ESX Server storage group is also Host Id 0. Now, if I try to make the LUNS in storage group visible on the VCB Proxy Server ESX, is there not a shock of the VCB Proxy 0 host Id and Id host ESX Lun 0? I'm confused, I don't have a test envirinment where I could try this before I could actually go forward with any solution.

  My intention is to perform a backup outside LAN of the VMDK.

  Any help is that this respect is very much appreciated. Thanks in advance.

  (1) Yes, you can have different host for VCB then for your ESX host LUN ID

  (2) Yes, you can use the identifiers of naa, it will automatically use the identifiers of naa, no need to configure anything at all.

  Duncan

  VMware communities user moderator

  -

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

• 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

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

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

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

• Questions about connecting to a host ESX 3.5 to vCenter 4.1

  I need to migrate 7 hosts 3.5.x ESX ESX 4.1. I did not have a test environment and will work with live on committed production systems (not clustered). vCenter 4.1 and two new 4.1 ESX hosts have been configured to handle live Vmotion (cluster will come later). I activated the license point server towards the old VirtualCenter 2.5 in the hope of being able to disconnect a host ESX 3.5 live the old virtualcenter and reconnect to the new vCenter 4.1 without rebooting the host ESX 3.5. VUM is not an option at the present time, so I intend to do a full install base upgrade.

  (1) I know that I can disconnect the ESX 3.5 server the old virtualcenter without problem. My first question is, if I try to join the new vCenter (config pointing to the old license server) box of 3.5 will be vCenter 4.1 need to install the new management agent in the box of 3.5 and therefore require the host restarts?

  (2) if the agent of 4.1 management is not installed on the host ESX 3.5, its virtual machines can be migrated (cold) to one of the new servers?

  I should add that the licenses are not a problem, we are migrating to the latest keys but have sufficient old licenses to manage the transition. The VMs are on SAN LUNs that are visible to guests old and new.

  Especially, I want to know what to expect through are exactly what will to restart is required and have not been able to locate that particular point.

  Thanks in advance.

  hensonj7

  When we went from 3.5 to vSphere, is that big of a deal.  Just disconnected the vCenter server host and updated the vCenter keeping the existing license server, and then re-attached to the new Victoria Cross.  It will establish links with the new 4.1 software, but it shouldn't require a reboot at all.  I did mine with all virtual machines out of it, but I think you can do all this live... Since a little while I did this upgrade

  -Kyle

  «"RParker wrote: I guess I was mistaken, everything CAN be virtualized"»

• VMotion using on OpenFiler iSCSI LUNS

  Does anyone know if it is possible to 'share' a logic unit number on an OpenFiler iSCSI target so I can use VMotion? So far, I can't my second ESX server to connect to the LUN.

  Should not be a problem,

  Follow this: http://www.petri.co.il/connect-vmware-esx-server-iscsi-san-openfiler.htm

  of http://superuser.com/questions/101662/vmotion-using-iscsi-lun-on-openfiler

  StarWind software developer

  www.starwindsoftware.com

• Error in adding an iSCSI LUN - use software iSCSI initiator...

  Hi guys,.

  I can't add an iSCSI LUN to my host ESX4.0. It is the iSCSI Software initiator that is activated and I can see the LUN after I launch a new analysis.

  While adding the LUN as a data store, it throws me an error, please find the attached for the snapshot file.

  The real question is if I add a lun iSCSI and then remove it and again try to re add it whether or nor the old signature are found that do not readd it.

  Is there a command that I can use to remove all the LUNS already assigned and delete it existing signatures.

  Let me know guys if the above is not clear.

  Kind regards

  Use fdisk to create a partition and vmkfstools - C command to format the partition as VMFS. You use a supported storage array?

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