Connection to multiple iSCSI SAN ESXi

Similar Questions

• ISCSI SAN & ESXi

  Hello

  We are currently researching the possibility of using ESXi to build about 15 physical servers on 3 or 4 HP bl460c blades. We are at the stage where we are trying to work on the costs and potential savings, and we need to know how much to budget for a SAN. We probably need 2-3 TB to fit all our data and us do not grow by that much each year (less than 100 GB). Far factor matters most in this process will be costly, so unfortunately a FC SAN is out of the question.

  The servers are:

  1 x Exchange 2003 (used by users of ~ 100)

  1 Server x Mimesweeper (antispam)

  2 x CRM LOB systems (only one is used at a given time, the second is a spare)

  1 x file win2k3 Server

  1 x Server SQL (used only for the low use of Sharepoint 2007 accounting software & Sage 200)

  1 x Sharepoint 2007 server

  3-4 random 2 k 3, use of the very low disk servers

  3-4 2 k 8 Terminal servers

  All Windows 2003 Terminal servers with the exception

  I would rank all these while the use of low disk (although I don't know how to measure this, any suggestions?)

  I want to know what products we should watch. This is a product that I've seen, but I don't know if the 2 x 1 Gbps is sufficient to use these virtual machines. Upper cost limit is probably £5 k (~ £3 k would be nice if possible!) and we would ideally have a better performance and an acceptable performance option

  If it makes a difference, we probably look at the free version of ESX now and Dr., we have a 3rd party using the double take.

  I have also heard people using NFS, would also be an acceptable solution for us?

  Thank you very much

  Ideally, he would answer your pic, but sometimes it's not realistic as you say.   What kind of load IO get you exchange, SQL and file server?

• Connection iSCSI SAN to ESXi servers

  Hi all

  I am trying to work through the iSCSI SAN Config Guide and get our three ESXi servers connected to our iSCSI SAN, but I'm confused about a few points.

  Background - Our production network is 172.16.10.x, our management network is 172.16.64.x and the SAN is on the 10.1.1.x network.

  The Guide says that the service console and VMkernel need to access the iSCSI storage - but in ESXi, there is no service console. Our network administrator (who has used 2 ESX) said just put in place two vSwitches and configuring each of them to VMkernel access, one on network 10 and the other on the management network. Every time I try this, I lose connectivity to the management console. It seems VMkernel wants a default gateway set and when I put it for 172.16.64.1, the SAN does not connect, but when I put it to 10.1.1.1, vCenter loses the connection. Our network administrator says he won't let the 172.16.64.x network traffice to the 10.1.1.x network, but I think that we have to set up in this way.

  Is there something I'm missing. There actually seems to be three issues. (1) when the Guide says of console, VMkernel and service is possible to distinguish between the two in ESXi? (2) if we set VMkernel network 172.16.64.x, can we create a second VMkernel on the 10.1.1.x network? and (3) should just bite the bullet and set up routing between the VMkernel and the San?

  Thank you. I know it was long and complicated, but that reflects my confusion! Any help would be appreciated.

  The answer to the first question is no, there is no distinction between console and vmkernel port in ESXi, like network service management of walks on the portgroup vmkernel.

  You should be able to create a vmkernel 2nd interface, and you do not change the default gateway.  As you have noticed, you can have a default gateway, that is why the default part.  That alone, and you should have two exchanges vmkernel, one on the network management and the other on the storage network.  The vmkernel being on the same segment as the storage, traffic goes out through it and not the default gateway, so no routing must take place.

  -KjB

  VMware vExpert

• Multiple ISCSI targets and connection failed

  last week I was preparing my s/w iscsi initiator to connect to multiple iscsi targets.  I ended up not doing last week, and I thought that I removed the targets of the GUI.  looking now @ the GUI, I only show my main production target, but if I look in my Journal vmkernel, his constantly trying to connect to these targets, I had the plan on connecting the box to.  Anyone know of a way for me to look @ the console and see where they can still be defined, of cause, they are not displayed in the GUI.

  See part 3 of this post "The case of stale iSCSI LUN.

  http://apps.sourceforge.NET/MediaWiki/iscsitarget/index.php?title=The_case_of_stale_iSCSI_LUNs

• Make Accessible iSCSI SAN-VM via Windows iSCSI initiator

  I have a "total newbie" question that I hope can respond quickly enough.

  I added a new DELL MD3000i SAN to my storage network in order to use this SAN exclusively for Windows virtual machines. I have the vdisks large (2) 4 to 7 to each (Yes, I REALLY need unique and large volumes) defined on the MD3000i. (4) the MD3000i ports are connected to my iSCSI VLANS and have the id default host port 192.168.130.101/102 and 192.168.131.101/102.

  I have a MD3220i installed in the network and working with hosts ESXi 4.1 (2) (192.168.230.101/102, 192.168.231.101/102 of the subnets). I am quite familiar with how to make the storage available to the host via the initiator of the iSCCI, but I know not how to make accessible storage for virtual machines WITHOUT using the host to connect to the iSCSI SAN, create a data store, and then add a new virtual disk to the virtual machine.

  Only the vmnic dedicated to the iSCSI initiator have physical links to iSCSI VLANS (vSwitch01). The network switch has (2) network adapters connected to the network via vSwitch0 "inside".

  Any ideas on the best way to "get there from here"?

  Hello.

  You will need to create a group of ports in virtual machine on the same vSwitch created in your iSCSI ports group.  Give the virtual machine a 2nd NETWORK card and then assign it to the created virtual machine port group previously.

  Good luck!

• Should two switches for the installation of iSCSI SAN - be stacked

  I mean by "stacked" should they be hung by backplane?  Reference Dell passes, btw.

  Just two hosts connected to an iSCSI SAN.

  If the goal is to be completely redundant, your server is able to cable a physical NIC directly on each switch and your San can connect to both switches, there is no reason for the connections between these switches. Stacking of the switches can provide options for a large number of cases, but I don't think it will be here.

• Microsoft NLB on a virtual iSCSI SAN using computer

  Hello

  Is it possible to use the NLB network on a virtual computer that is connected to an iSCSI SAN?  I was under the impression that MSCS is not available, use an iSCSI device, but is NLB another form of consolidation?  I am unable to find a clear answer anywhere else.

  Any help would be appreciated.

  Yes its is possible, the storage has nothing to do with NLB, its pretty much traffic going to different hosts of network load balancing.

  useful info: http://blog.baeke.info/blog/_archives/2006/2/21/1775587.html

  If you found this information useful, please consider awarding points to 'Correct' or 'useful '. Thank you!

• ESXi 4.1 or ESXi 5.0 with iSCSI SAN

  Hello

  I'm trying to establishing an environment that is / will be an iSCSI SAN backend entirely.  I know of a lot of reading that the best practice is to config the ESXi host with:

  VMKernel > vmnic > physical network adapter > switch ports > port on SAN (config 1:1 - no grouping of vmnic)

  Environment:

  ESXi 4.1 & 5.0

  Force10 switches

  EqualLogic iSCSI SAN (PS4000 & 6000)

  Here's my real question (playing the Devil's advocate):

  Why I shouldn't team 3-4 vnmics on a vswitch with multiple vmkernel ports?

  Given my environment.  Can someone point me to a technical document that explains what will / could happen if I set up the environment ESXi in this way?

  Thank you

  BDAboy22

  So, basically, we want the SAN to take full responsibility for the failover instead of the network and/or the SAN for who should resolve the failure (which could lead to the time of restitutio in integrum longer session).   I understand that correctly?

  Yes, that's right, we want to stack storage for vSphere manage with path selection and tipping - and by connecting each vmknic directly to the physical vmnic map we sort of "simulate" how to CF cards and also ignores the network failover mechanisms. As you probably know you also need to "bind" the iSCSI Software to the two vmnic (GUI now in 5.0, esxcli in 4.x)

• iSCSI SAN Connectivity

  I'm kinda new to this Yes, you can be sweet.

  We are migrating some of our less critical servers to VSphere. Because the servers are at camp, we'll install eSXI on our server and use hosted camp via iSCSI SAN. The camp provided us with a block of IP addresses that we can use for SAN connectivity.
  SAN connectivity is on it's own dedicated NIC (1 for testing purposes) and physical switch.
  Management network
  192.168.72/24
  SAN IP blocked
  172.26.11.0/26
  172.26.11.1 - GW
  The target IPs
  172.31.3.105
  172.31.3.109
  I created a virtual switch for iSCSI and tied a physical NETWORK adapter to it. I then added the iSCSI adapter software, responsible for the target in the dynamic, linked discovery the NIC to the iSCSI Software card.
  I then added a road 172.31.3.0/24 to go to 172.26.11.1.
  When I scan for the storage of the new, I just blank. If I go back into the adapter software, targets are now listed on the static discovery tab. The camp is saying that their HDS does not all applications.
  So I built a virtual Windows machine and loaded on this host (using an Openfiler iSCSI on the management network) and installed the Microsoft iSCSI initiator. By using this software, I am able to connect to the SAN CoLo network from inside the virtual machine.
  What Miss me? Why can I not connect to the network the host SAN? Any help will be much appreciated.
  Bob

  http://pubs.VMware.com/vSphere-50/topic/com.VMware.vSphere.storage.doc_50/GUID-0D31125F-DC9D-475B-BC3D-A3E131251642.html

  (Physical network adapters must be on the same subnet as the iSCSI storage system, that they connect)

  / Rubeck

• Is it possible to use GPFS or another build is a SAN storage shared for multiple ESX and ESXi hosts?

  We have a license GPFS and SAN storage. I am trying to create a storage shared for multiple ESX and ESXi hosts share existing virtual machines. We tried once NFS, it of a little slow and consume too much bandwidth LAN.

  Anyone can help answer? Thank you very much in advance!

  It depends on your storage space.

  You must connect all hosts to the same San, then follow the configuration guide of ESXi and specific documentation for your storage space (for sharing LUNS on multiple hosts).

  André

• Live iSCSI SAN upgrade production network (Dell MD3000i and PowerConnect & ESXi 4)

  Hi all

  For the moment, I have a direct connection to my Dell MD3000i iSCSI SAN in ESXi 4 2 x host with no switch between the two, all of the virtual machine is within the SAN and running on both hosts.

  If I want to put a switch between the two and add one more iSCSI SAN so that the two SAN can be accessed / shared with the 3 ESXi 4 guests total, how should I approach the issue?

  any idea or guideline would be greatly appreciated.

  What I have to plan the time or can I change the old IP on the existing SAN iSCSI manually cable one by one without damage/alter the existing operation of the virtual machine on SAN? or I have to stop the virtual machine and then terminate the connection manually iSCSI session and then restart the host SAN?

  Thank you

  AWT

  Standard installation on the MD3000i is for a port iSCSI on each controller on a subnet and one on each controller to be on another.

  There have been people working successfully on a subnet, reported problems too.   I wish we were longer on our Vsphere upgrade, I'm not at a point but where I test things like Vmotion.

• How to reconnect safely iSCSI SAN connection after new ESXi4u1 reinstall on USB?

  Hi all

  Can anyone here guide me how to add the connection to the current host of ESXi 4 iSCSI SAN?

  I think not as export the ESXi existing profile using vMA can do much because the version number is different so ESXi profile export is useless.

  Note: during the installation of 4u1 ESXi I unplug the host LAN cable.

  Thank you.

  Kind regards

  AWT

  Access to the host on the MD3000i configured?

  Cause the host will have a different IQN, you must reconfigure the access.

  André

• ESXi 3.5 4 problem to upgrade by adding the VMFS partition existing on iSCSI SAN

  Hi all

  I've got 2 x Dell PowerEdge 2950 III linked directly with Dell MD3000i iSCSI-SAN and today I had once hard to improve my production ESXi 3.5 u 4 ESXi 4.0,.

  First is that the upgrade is failed miserably after following this thread: url = http://communities.vmware.com/thread/211413;jsessionid=47217F9BCCA2DF1325DBE7A266D48A8D?tstart=0VMware communities: error on upgrade the host: this host is not compatible with this upgrade. [url]

  with the following error message: ERROR: unsupported boot disk

  The layout of boot device on the host computer does not support the upgrade.

  That's why I did a clean reinstall of ESXi 4 on top of ESXi 3.5 u 4 and lost all unique settings on my ESXi host. I am now stuck in SAN iSCSI partition mapping after following the guide from: http://support.dell.com/support/edocs/software/eslvmwre/AdditionalDocs/cnfigrtnguide/storage_guide.pdf [/ URL]

  See the following attachment.

  I wonder how people make their upgrade in ESXi 4.0 in the production system running ESXi 3.5 u 4 filled with hundreds of VM? The reason why I use 2 x ESXi server connected to unique SAN server, is that I can just start the virtual machine on the SAN from the other ESXi - & gt; that's fine and tested, but then when I rebuild the failed server, I need to delete all the data inside the shared partition that contains my VMs.

  So in conclusion after one of the ESXi server failed, mapping of iSCSI would eventually destroy all data in the partition?

  CMIIW, any idea and suggestion would be gladly appreciated

  Kind regards

  AWT

  The configuration-> tab cards storage, you should be able to recrawl and find existing VMFS volumes.  You shouldn't need to add storage.

  Andy

• Impossible to mount simultaneously multiple targets since a single iSCSI SAN iSCSI

  Hi guys,.

  I recently deployed FreeNAS 8.0.3 as a practice laboratory iSCSI SAN on one of my HP Proliant microservers.  The first target is a measure of physical disk since it was noted that the drive is faster than file extensions.  I have install the Initiator Software for dynamic and found discovery.  I built on that vCenter.  It was pretty slow going to see that it is also on a 100 MB network.  I decided to buy a gigabit switch and a 240 GB SSD.  I added the SSD as another target.  However, I can't get two data warehouses at the same time.  Am I missing something?  The two are listed under iSCSI Software Initiator...

  Connected targets: 2

  Features: 1

  Paths: 2

  When I'm actually in the paths, I see two targets, but only one can be Active (e/s) and the other is active.  To switch between data warehouses, I had to disable the currently active (e/s) an and the reactivate to failover to the other.  I wish that both target mounted at the same time.  How can I do this?  Thanks for any help.

  Mark

  My apologies in advance if I'm wrong understand something in the description of the problem, but it seems that you have only 1 "" meaning a block at the level of the device (iscsi) LUNS presented through two separate iscsi (two separate cobinations iqn/IP) targets. You can't have a VMFS in LUN data store so I am bit confused with your statement "I can't climb the two warehouses of data at the same time"...

  Peter D

• Problem with ESXi 3.5 host or our iSCSI SAN

  Hello

  Last week, twice we came into work and notice that some virtual machines on a host somehow the bomb and break the connection or work habit and are turned off.  It happens with mutiple errors, but we are not sure if it's the host itself or iSCSI SAN is too connected a NETgear ReadyNAS.  All the vmdk and vmx VM files are on the SAN storage are loacted here for targets.  Your opinion on this if someone could help determine what may be the question, please, thank you?

  Welcome to the forums

  I edit your images and delete the business credentials. There is a security risk that you should not expose.

  Take a look at the following.

  http://communities.VMware.com/message/1333118#1333118