UCS iSCSI SAN Configuration

Similar Questions

• iSCSI network configuration

  Hello world

  I did two configured 5.1 esxi hosts with iSCSI SAN and they work very well. In fact, the configuration of the network is as below:

  MD3200i: 4 of the 8 ports configured on both controllers. two on a subnet on VLAN x and two on another subnet on VLAN y.

  ESX HOSTS: two different vSwitches with a vmnic and a vmkernel on each host.

  Everything works well, with configured multipath.

  So now: I want to improve the performance of storage using the last four ports on the md3200i and the two NICs per host.

  My question is do I have to create new vmkernel for each nic 'new' or do I just add nics on my vSwitches?

  Maybe I misunderstood the documentation I've read, but the portbinding is not improve performance but only HA feature?

  

  Thanks in advance

  Martin

  Unless there is something that has changed lately, you need a one-to-one relationship between groups of VMkernel ports and vmnic. Actually regardless if configure you this in a single vSwitch - with setting the vmnic as assets/Unused - or by using a vSwitch by group of VMkernel ports.

  André

• ProLiant BL460c G7 iSCSI SAN boot

  Hello
  I'm looking to start a single ProLiant BL460c G7 of our HDS iSCSI SAN and then install ESXi 5. The blade has no local storage. The SAN is already in use by the cluster of our production.  In the iSCSI SAN config guide it States to set up storage so your host has access LUNS. How can you do this if your host is not installed? How can I configure the LUN to only be accesed by my hosts IQN name when I don't have an IQN name yet? What I must first install ESXi? I'm obviously missing something any help would be great!

  This is true, for this, but as your correctly point out if the OS is not installed how do you have a software iSCSI initiator - boot from an iSCSI SAN is supported only if you have an initiator of independent hardware installed in your ESXi host.

• Several iSCSI SAN on different VLANS

  I have a little trouble to get this configured.

  In our environment, we have 4 guests and 2 EqualLogic iSCSI San. Each host has 3 NICs dedicated to iSCSI traffic, and they have been implemented to use the plugin for Multipathing of Dell with 3 VMKernel iSCSI ports, each bound to a NETWORK adapter physical and then linked to the iSCSI software adapter.

  We want to add a new SAN QNAP out some VMs test & dev environment of low cost data warehouses. The QNAP San not supporting Jumbo frames, we want to move them to their own VIRTUAL local area network.

  Can someone tell me how I can get this set up? I need of course a new VMKernel port running on the VLAN again, but after that I'm stuck.

  Thank you

  First: the initiator will be gracefully demote by using standard images.

  Second, there is nothing that prevents you from using the same trade for the qnap. If it does not manage the same way MPIO, you may need to add more exchanges and vmknics. If you place moderate to heavy load on the qnap it would interfere with the ability of the EMM to balance the load properly but allows to measure.

  We have a group EQL and a Celerra making MPIO in different ways. With Celerra you add several portals (ip addresses) network on different subnets so ideally you set up your trade in this way. For us, this meant adding a second portgroup and vmknic on each vmnic, resulting in a whole bunch of paths to the Celerra said. If our use of Celerra was far from being weak to non-existent I probably don't have it.

  -Anders

• Assistant can't see iSCSI SAN software

  Hello

  I test StarWind version 5 (www.starwindsoftware.com) with an ESX v3.5

  I have configured an adapter for iScsi (vmhba40) and specific vswitch (only the VMkernel port) software. There are specific NIC for iSCSI traffic and no rule of firewall between ESX and SAN.

  .

  Using the Wizard "Adding storage", I don't see the "iSCSI SAN software.

  Anyone have problems with this software SAN?

  Thank you for your reply,

  Yossi

  REM: to be sure that the Starwind is set correctly, I tried

  connect through Microsoft Initiator. And it has been directly

  Ok.

  You probably followed the white paper of http://www.starwindsoftware.com/images/content/StarWind_HA_ESX.pdf

  ?

  ---

  iSCSI SAN software

  http://www.starwindsoftware.com

• Slow performance read/write on iSCSI SAN.

  This is a new configuration of ESXi 4.0 running virtual machines off a Cybernetics miSAN D iSCSI SAN.

  Having a high data read the test on a virtual machine, it took 8 minutes vs 1.5 minutes the

  the same VM on a slower 1.0 Server of VMWare host with virtual computers on

  local disk.   I look at my reading speed of the SAN, and

  It's getting a little more than 3 MB/s max in reading, and usage of the disk on the virtual computer is slower 3MB/s...horribly.

  The SAN and the server is both connected to the same switch 1 GB.  I followed this guide

  virtualgeek.typepad.com/virtual_geek/2009/09/a-multivendor-post-on-using-iSCSI-w

  ITH-vmware - vsphere.html

  to get the configuration of multiple paths correctly, but I still do not get good

  performance with my VM.   I know that the SAN and network

  must be able to handle more than 100 MB/s, but I am not getting

  it. I have two network cards of GB on the multipath SAN to GB two network cards on the

  ESXi host.  One NETWORK card per VMkernel.  Is there anything else I can check

  or do to improve my speed?  Thanks in advance for advice.

  Another vote for IOMeter.

  Try to test 32K 100% sequential read (and write) with 64 IOs in circulation, this will give sequential performance.  Should be close to 100 Mbps per active path of GigE, depending on how much the storage system can get out.

  Then 32K 0% sequential read (and write) with 64 traffic against a LUN will IOs (say 4 GB +) good test size give a value for IOPS, which is the main factor for virtualization.  Look at the latency, must remain below approximately 50ms usually in order to be able to work if the default 32 IOs in circulation (by host) is OK (say you had six hosts, the table should be able to deliver the random i/o with a latency)<50ms with="" 192="" outstanding="" ios="" (="">

  Do not use the "test connect rate" and cela effectively tests only cached flow, which we are not so interested in any case.

  Please give points for any helpful answer.

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

• question put on the vSphere iSCSI SAN infrastructure network

  Hi all

  We are a small company with a small virtualized environment (3 ESX servers) and are about to buy an AX-5 SAN EMC (model Ethernet not CF) to implement some of the features of high availability of vSphere. My question is related to the networking of the SAN: we switch dual Cisco 2960 G Gigabit and dual Cisco ASA 5510 firewalls in a redundant configuration.

  I understand that the best practice is to implement iSCSI traffic on a separate from all other traffic LAN switch. However, I do not have the knowledge and experience to determine the real difference than a separate switch would really vs the plan to create a separate VLAN on the switches Cisco dedicated to iSCSI traffic only. I would ensure that the iSCSI traffic has been on a VLAN dedicated Physics (not just a logic) with any other VLAN logical (subinterfaces) on the same VLAN). It is difficult for me to understand how a port gigabit on a VLAN isolated on kit Cisco will perform much poorer than on a dedicated Cisco switch somehow. But then again, I don't know what I don't know...

  The thoughts and the input would be appreciated here: I'm (very) hard not to drop another $6 + in another pair of Cisco switches, at least that this decision will significantly compromised performance iSCSI SAN.

  Enjoy your time,

  Rob

  You have 2 SP each with 2 iSCSI, for example:

  SPA: 10.0.101.1 101 VLANS and VLAN 102 10.0.102.1

  SPB: 10.0.101.2 101 VLANS and VLAN 102 10.0.102.2

  On your ESX to create 2 vSwithes, each with a port vmkernel on an iSCSI network and each with a single physical NIC.

  See also:

  http://www.DG.com/microsites/CLARiiON-support/PDF/300-003-807.PDF

  André

• iSCSI SAN, ESX4 Datastore recommended sizing

  Hi all.  I am in the final stages of our construction of vSphere and I'm looking for best practices in terms of sizing of the warehouses of data/Lun on a SAN, iSCSI for several hosts of ESX4.

  What we have:

  Two HP c7000 blade enclosure with three BL460c in each enclosure.

  All servers will run ESX4 and use an iSCSI SAN (Software initiator).

  I'm not sure of the best way to configure these elements.  A large unit number logic holding a large store of data?  A few small LUN each holding a data store? A unit number logic/data store for each ESX host?  I don't want to use vMotion and who could help narrow down the answer.

  Any help that you experienced people from VMware can each give this noob is very much appreciated.

  -Dave

  Dave

  This is my golden rule.

  Virtual machines are mixed on data warehouses to optimize storage efficiency and the efficiency of the I/O - low mix I/O virtual machines with virtual machines I/O high on the same data store.

  VMs per VMFS datastore 12-16 maximum.

  16 VMDK files per VMFS datastore maximum.

  * A VMFS volume per LUN storage.

  * At least 15% to 20% of a VMFS data store should be left as open space to meet requirements such as the virtual machine swap files and snapshots.

  According to your needs - you will initially 30 virtual machines, you must look for set 2 data warehouses-, but the number of vmdk files or e/s for a virtual machine needs can change that.

• Config network initial ESX with iSCSI SAN

  Hi all

  I want to install 2 ESX 3.5 servers which will be connected to an EqualLogic iSCSI SAN.

  The SAN is on a VIRTUAL, 10.x.x.200 with a 255.255.255.224 LAN Gateway.  This VLAN is not routable, DNS servers, etc.

  What I am trying to understand, it's for the initial setup of ESX, when I set the config network (console), should I register the IP address for the VIRTUAL LAN, example was:

  IP address: 10.x.x.201

  Gateway: 255.255.255.224

  Primary DNS: white

  Secondary DNS: white

  Or, for example B, should I use our 'public' speaking:

  IP Adress:129.x.x.201

  Gateway: 255.255.255.0

  Primary DNS:129.x.x.1

  Secondary DNS: 129.x.x.2

  I know that with the VIC, I can later add vSwitches, etc., but at least for the initial installation, I want the configuration to provide smoother operation. Thanks for any idea that you can provide!

  Chad

  Hello and welcome to the forums.

  What I am trying to understand, it's for the initial setup of ESX, when I set the config network (console), should I register the IP address for the VIRTUAL LAN, example was:

  Use example B (129.x.x.x) for the Service Console (management functions), and after that the system is in place to add an another vSwitch used to connect to the SAN VLAN.

  Good luck!

• Cannot migrate VM on iSCSI SAN. Failure at the helm of the 10%. Peut vmping to all addresses

  Hello everyone

  Impossible to migrate virtual machines on iSCSI SAN. Failure at the helm of the 10%. Peut vmping to all addresses

  I recently installed a new configuration of the VM and I feel the above. My configuration is:

  2 HP DL380 with 1CPU 16 GB of ram and 500 GB shared space on iSCSI SAN.

  Installation of the network as follows:

  each host has the 6 network ports that is load balanced and fault tolrated in 3 VMSwitches. VMSwitch0 goes to 2 ports to shared resources on a 4510th cisco. On this switch, I use VLAN tagging to different servers that perform different functions. It works fine.ie. VLAN 5 is for the management vlan 31 is for secure vlan servers 37 is forinternal Web servers.

  VMSwitch1 is a vmkwenelport for the connection of iSCSI SAN. It is set on vlan 200 on the switch, so does tagging vlan put it. We have separated our san network ourusual networks.

  vmswitch2 is used for backup purposes and is used in a similar manner as vmswitch0. the ports of trunkied and backup services is vlan tag to go to the correct servers.

  I am able to ping betwneen the VLANS allowed. I can also vmkping to all the ip addresses of the two hosts san.

  What I can't do is to migrate direct customers between the hosts. He is still unable to 10% with the following error:

  Migrate the computer virtual iws3xx - pop1.mns.tlg.private a general error has occurred: the VMotion failed because the ESX hosts were not able to connect to the network for VMotion.  Please check your physical network configuration and settings network VMotion.

  I looked in the newspaper of vmkkernel and I get the following text:

  9 Oct 15:05:38 esxn1-pop1 vmkernel: & lt; 7 & gt; fn_scroll_back not implemented & lt; 7 & gt; fn_scroll_back not implemented & lt; 7 & gt; fn_scroll_back not implemented & lt; 7 & gt; fn_scroll_back no implemented7:05:04:55.236 cpu2:6534) migrate: vm 6535:2094: info setting VMOTION: ts = 1255097135856641 Source, src = ip & lt; 172.31.207.21 & gt;

  9 Oct 15:05:38 esxn1-pop1 vmkernel: ip dest = & lt; 172.31.207.22 & gt; Dest wid = 6447 using SHARED swap

  9 Oct 15:05:38 esxn1-pop1 vmkernel: 7:05:04:55.236 cpu2:6534) Tcpip_Vmk: 1107: refining worldwide 6899 172.31.207.21, success

  (9 Oct 15:05:38 esxn1-pop1 vmkernel: 7:05:04:55.236 cpu2:6534) VMotion: 1807:1255097135856641 S: Set ip address ' 172.31.207.21 ' worldlet affinity to send the world ID 6899

  9 Oct 15:06:53 esxn1-pop1 vmkernel: 7:05:06:10.234 cpu3:6899) WARNING: MigrateNet: 668: 1255097135856641 S: Connect to & lt; 172.31.207.22 & gt; : 8000 failed: timeout

  9 Oct 15:06:53 esxn1-pop1 vmkernel: 7:05:06:10.234 cpu3:6899) WARNING: migrate: 295: 1255097135856641 S: Failed: host ESX The failed to connect on the network for VMotion (0xbad010d) @0 x 0

  9 Oct 15:06:53 esxn1-pop1 vmkernel: 7:05:06:10.245 cpu1:6538) WARNING: migrate: 3267: 1255097135856641 s: Migration, considered a failure by the VMX.  It is probably a timeout, but check the VMX log for the actual error.

  The journal of vmx says:

  16:07:38.856 Oct 09: vmx | http://Msg.checkpoint.migration.nodata the VMotion failed because the destination ESX host has not received all of the data of the source on the network for VMotion ESX host.  Please check your network VMotion settings and physical network configuration and ensure that they are correct.

  Can anyone help with this please

  No iSCSI traffic will work only if vmKernal and vmConsole are on the same vswitch. Maybe on the same vLAN according to how your VLAN.

• iSCSI SAN, blocking the ability to attach a RDM to two VM?

  Hello

  We have an iSCSI SAN and I wanted to test with clusters on this stuff, but I can't get a RDM attached to more than one virtual computer at a time.

  I know that MSCS is not taken in charge by iSCSI, but is not supported or is it not possible to join a ROW over a virtual computer at a time?

  Thank you!

  Kenneth

  The solution should work... so with RDM, but also with an initiator of software inside each node of the virtual computer.

  If you use RDM, you must configure the SCSI controller in physical mode.

  On the second node does not add a new drive... but easy to use existing RDM disk (or disable ROW filtering of the customer).

  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

• 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

• How to get iSCSI SAN connected to ESX when the SAN is on a different subnet?

  Hi all

  I have two machines ESX which are directly connected to a San that are on a different subnet other network cards.  Other network cards are 10.x.x.x and the SAN is on 172.16.x.x, however whenever I try to add the iSCSI storage, the system will never find the LUN.  I put the vmkernel 172.16.x.x but it does not always find them.  I know that the LUNS are configured correctly if its ESX just having problems with the other subnet.

  You need to activate the Service Console to see the iSCSI SAN, too. This is because you use the initiator software. For example, you can add a second SC in the vSwitch that your VMKernel Port is connected and align on the same subnet.

  Kind regards

  Gerrit Lehr

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