storage iSCSI with UCS

Similar Questions

• 4path iSCSI with 2 switch

  I want to connect 2 ESX 4.1 with 4 storage iSCSI NETWORK card and want to use 4 network cards and spend 2. I tried several configurations, but I don't see that 2 way. I see 4 way only if I connect on a single switch. How can I do?

  
  ESX IP (iSCSI) iSCSI host IP 192.168.11.90 192.168.11.101,102,103,104
  fix the image.

  Thank you too much.

  You must create a 4 vmkernels, each with its own IP address.

  Each core linking to a single physical NIC.

  Run a command in the console service to each of the vmkernels link to the initiator iscsi (see PDF below). This is only possible via CLI.

  New analysis of your storage space.

  Go to each volume and value "round robin" multiple paths.

  To be really an easy way to do this via the GUI. That's pretty pathetic IMO it does not already exist.

  That you configured is a single path (only one source IP) with the possibility to have 3 NICs fails.

  What you will get with your current configuration is an increased bandwidth. Never will flow of traffic from a single IP address on the storage device. 3 of your network cards won't do anything unless sit and wait to die or be disconnected Active NETWORK card.

  Download the PDF here:

  http://www.EqualLogic.com/ResourceCenter/assetview.aspx?ID=8453

  In what concerns a Dell Equallogic, but the ESX part won't be different depending on your type of iSCSI storage.

  The PDF file gives clear instructions on how to do it. ESXi will probably have different commands and must be made through the line of remote control commands.

  I just did this there are 3 mights. No reboot is required, and it did not have any currently active storage offline.

  Hope that helps.

• Upgrade and migration of 3.5.0upd0 to 4.0upd1 and shared storage iSCSI

  Hi people,

  I've got 2 ESX host: Alpha and beta. Two of them are connected to a cabin of iSCSI with some created shared storage drive (all VMFS3 v3.31). And both had ESX 3.5.0 update0

  I migrated all the VMS running in the Alpha host for shared storage and made host Beta to run (clones cold or simply reassign files). Then I bâtait Alpha from scratch and I installed vSphere 4.0 in it. I also created in its local storage space bit a new virtual machine with vCenter4 inside. It has worked well.

  Then I had to migrate Beta and its virtual machines, too. I first tried to manage the host with vCenter4, but it is not backward compatible.

  So I'll use the host update utility to upgrade beta I saw in a video tutorial, but my doubts are...

  • Option 1:

  Disable all virtual machines managed in host Beta.

  Configure the iSCSI client in Alpha, add storage shared cabin and try to manage the virtual machines already extinct. This reduces the time to downgrade.

  Upgrade Vmware Tools in the virtual machines (v4 to v7 type VM). Required reboots.

  Upgrade host Beta (with no SMV in there and unplug the cable of iSCSI) vSphere4.

  Connect and configure the iSCSI version beta customer.

  Manage the host with the new vCenter4 Beta.

  Configure the vMotion, DRS etc. in both hosts.

  • Option 2:

  Disable all virtual machines managed in host Beta.

  Upgrade host Beta (with no SMV in there and unplug the cable of iSCSI) vSphere4. Downgrade time increases.

  Connect and configure the iSCSI version beta customer.

  Upgrade Vmware Tools in the virtual machines (v4 to v7 type VM). Required reboots.

  Manage the host with the new vCenter4 Beta.

  Configure the vMotion, DRS etc. in both hosts.

  Which option is the best? Maybe is it possible to apply a third? What do you think?

  Thanks in advance.

  without loss of performance?

  Yes. VM with v4 works very well.

  The only problem is that you lose some new features, like the new drivers and FT.

  Note also that Standalone VMware Converter 4.x can also convert between v4 and v7 and vice versa.

  André

• Credit card was stolen. How can I pay for storage iCloud with Tunes gift card?

  Credit card was stolen. How can I pay for storage iCloud with Tunes gift card?

  Buy the card normally and wait for it to be loaded.

  (139690)

• Associated error - "Server features are not compatible with UCS below.

  Hi all

  I am tempted to associate a SPG which the UCS field but get the following error. Under the general tab:

  There are not enough global resources.
  field of the UCS has no server corresponding to this service profile features.

  And under the status tab:

  Descriptor of the stage: analysis of changes impact(FSM-STAGE:sam:dme:LsServerConfigure:AnalyzeImpact)

  Tent: 0

  Previous state: ConfigureFail

  Remote control Err Code: 5

  Distance Err Description: Server features are not compatible with UCS below.

  Distance Inv result: resources-out of stock

  The field of the UCS that I associate this GSP which is an existing domain, I have just signed up with Central UCS. I created and associated with a GSP scheme a UCS of greenfield in another area data center.

  The two areas are running UCSM 2.2 (6 d). Central UCS is 1.4(1a).

  I found a bug that suggests this may be due to the presence of a policy to Boot, but the workaround solution (remove the startup policy) does not work in this case.

  So, anyone know what might be going on here?

  Thank you

  Richard

  Richard,

  Please check the following bug: CSCuy07572

  You can use the global default and should work completely correctly.

  You can choose the version that is required here.

  Non-policy default will be a problem.

  Thank you

  Yoga

• Change of storage iSCSI IPs

  Hello

  We will be consolidating the 2 sites in one soon, and in the context of that we'll have the blades moving and storage iSCSI from one site to the other and re - IP them in the process.

  That's what I had in mind, please let me know if Miss me something:

  -Stop everything and moving equipment

  -Fuel storage iSCSI and re - IP

  -Power of blades and change their IPs

  (at this point all data warehouses and virtual machines on show them also inaccessible)

  -Add the IPs blade storage unit to allow access

  -In storage adapters / iSCSI / dynamic discovery, remove the old storage IPs and add new IPs, rescan storage

  Here, we should have our data storages and all VMs back on their show normal, that we should be good to start turning on VMs.

  Anything I missed? I did similar work a few times, but not in the last year or so, just wanted to do a validation test. We lack ESXi 4.6 build 1050704.

  Thank you

  If it worked very well, just as described above. I have to award points to myself :-)

  Thank you

• I have a lot of storage iCloud with my Macbook air why I also have to buy adobe revel?

  Why do I need Adobe Revel when I have a lot of storage iCloud with Apple?

  Hi Doris,.

  If you use iCloud for everything, that is to say, contacts, calendar, photos, etc., then you probably need not really Revel. If you are looking for a service that allows you to store unlimited videos and pictures, edit them, synchronize them, create albums to group with your friends and your family, then Revel is an excellent choice. Revel works with Mac, Win 8.1, iPhone/iPad and Android.

  But, as I said above, if you already use iCloud for storing your photos and you are happy with it, I would say that, in truth, you do not need to Revel, too.

  Best regards

  Glenyse

• LUN iSCSI with 4096 bytes logical block cannot be formatted

  Anyone using Freenas to disseminate to ESXi 5.1 iSCSI LUNS?

  Can you use LUNS which are presented with 4 096 blocksize bytes?

  Here a Lun iSCSI with 4096 bytes logical block cannot be formatted with a VMFS volume
  Same logical unit number presented with works by 512 bytes

  I have enclosed two copies, one before that I did anything and the second after that I tried to add the data store.

  So I first created the LUN and presented to the host;

  

  You get a nice warning;

  

  I see this new LUN;

  

  Pending;

  

  If you wait long enough;

  

  In the next step, it breaks;

  

• Storage vMotion with advanced vsphere license

  I have the vSphere advanced license that doesn't include a Storage vMotion.

  This does mean that I won't be able to do manually storage vmotion with this license, or is what is not included in the new vSphere GUI?

  You will not be able to make Storage VMotion.

  But many people say Storage VMotion, even when cold migration is performed. Thus, you will not be able to move VMS on another store data seamlessly, without power off VM.

  ---

  VMware vExpert 2009

  http://blog.vadmin.ru

• The upgrade to ESXi 4.1 with storage iSCSI software to ESXi 5.5

  I intend to upgrade ESXi 4.1 with which I have attached to ESXi 5.5 iSCSI software storage

  I've updated all my guests who were on the SAN storage with no problems.

  I would like to know that if it there's nothing I should take care before I update the host connected iSCSI to ESXi 5.5, as for the hosts with SAN attached storage I made to remove the cables of SAN before upgrading the host.

  Also, if all known problems, you will be informed during the upgrade to ESXi 4.1 to ESXi 5.5 with iSCSI Software storage, please let me know?

  If there is no different process to upgrade coz in ESXi 4.1 I do not see this link ports of iSCSI vmkernel ports software iSCSI but I know in ESXi5.5 we have to or I just launch a procedure of standard upgrade via the Update Manager and everything will be taken care?

  Thanks in advance

  With ESXi prior to version 5, linking ports had to be done via command line. However, if it has been configured correctly, you should be able to upgrade to ESXi 5.5 (assuming that the host has not been previously updated since version 3). BTW. the last time that I disconnected the host of storage for an upgrade has been with ESX 3.0.

  André

• Increase throughput for iSCSI with multiple NICs

  I'm implementing a new host ESXi 6 using a Synology NAS as an iSCSI target. I have 4 nic of the Synology stuck in 1 connection, so it has 4 GB of throughput. So far, over my hosting provider, I have two nic I dedicated to iSCSI traffic. So far, I put vSwitch under 1 two NICs and I was playing with patterns. I put two 1 vmkernel network cards and set as active adapters. However when I watch the iSCSI network traffic I only see traffic on a network adapter. This of course caps my speed to 1 GB. I would like to be able to bind several network cards so I can get a flow more. I tried changing the selection of the path for the warehouses of data in Round Robin are therefore at least two active nic. But which always leaves me with two individual connections of 1 GB instead of 2 GB connection. Is it possible for me to get there or I'm better off just having several 1 GB NIC load balanced?

  I'm not familiar with the Synology. However, what is generally - in the case where the storage system supports - is to set up several uplinks on the side of the target of storage/as well as on the initiator/ESXi side, each with their own IP address. Once configured, you can use multiple paths to access the target. According to the capabilities of the target, Round-Robin (if supported) will send traffic through all the links, i.e. using the bandwidth of all the links.

  André

• iSCSI with MPIO

  I need configure the virtual switch in VMware for an iSCSI Array does not support LACP or aggregation of any kind.

  There are 4 ports on the table that can be used.

  • How many cables should I use for my 7K table?
  • Should I use MPIO for LACP is not an option?
  • How many IP addresses to configure on my table for iSCSI?
    
    

  I never used LACP for iSCSI connectivity, I don't know yet if this is supported by VMware! Anyway, basically you will configure an IP address for each target port and an IP address to each initiator VMkernel on one or more ESXi hosts. You may need to double-check with the documentation of the unit of the range, if for example a VIP (virtual IP) for the target to be used, and the question of whether IP addresses should be in the same or in different subnets. If storage systems supports the path of Round-Robin policy, then make sure that set you this for the LUN to the advantage of the bandwidth available.

  André

• How to add more target iSCSI with static discovery

  Try to add multiple entries of static discovery for a set of hosts in the cluster. I can add the first entry by running the following PowerCLI

  Get-vmhost 'vdi1.vdi.sf.local ' | Get-VMHostHba-Type iScsi. New-IScsiHbaTarget-address '172.27.32.30' nomiscsi - iqn.2010 - 01.com.solidfire:bbup.desktop01.2514 - ChapName VDI-desktop computers - ChapPassword j0iT18i17Vp4su > r ChapType - required - static type

  However, whenever I try to add the following entries to static discovery (I have 22 to add to the same discovery IP address) I get the following error message:

  New-IScsiHbaTarget: 27/10/2014-09:17:28 new-IScsiHbaTarget the specified target

  '172.27.32.30:3260' already exists.

  On line: 1 char: 62

  + get-vmhost 'vdi1.vdi.sf.local ' | Get-VMHostHba-Type iScsi. New-IScsiHbaTarget...

  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  + CategoryInfo: InvalidArgument: (:)) [new IScsiHbaTarget], VimException)

  + FullyQualifiedErrorId: Client20_StorageServiceImpl_TryValidateUniqueIScisTargetAddress_NonU

  niqueAddress, VMware.VimAutomation.ViCore.Cmdlets.Commands.Host.Storage.NewIScsiHbaTarget

  Can I add multiple static targets to a single iSCSI server IP address just right with esxcli, but I'd rather this fact directly in PowerCLI without using $esxcli if possible.

  the discovery of iscsi adapter statictarget esxcli add - a vmhba38 - a 172.27.32.30:3260 - n iqn.2010 - 01.com.solidfire:bbup.desktop01.2514

  esxcli iscsi Portal adapter defined target - a vmhba38 - 172.27.32.30 auth chap d United-a-n VDI-Desktops - required l - n iqn.2010 - 01.com.solidfire:bbup.desktop01.2514 - S j0iT18i17Vp4su > r

  the discovery of iscsi adapter statictarget esxcli add - a vmhba38 - a 172.27.32.30:3260 - n iqn.2010 - 01.com.solidfire:bbup.desktop02.2515

  esxcli iscsi Portal adapter defined target - a vmhba38 - 172.27.32.30 auth chap d United-a-n VDI-Desktops - required l - n iqn.2010 - 01.com.solidfire:bbup.desktop02.2515 - S j0iT18i17Vp4su > r

  I must be missing something simple. Any help is very appreciated.

  As far as I know, it is not possible with the current construction of PowerCLI to set several iScsiNames on the same target.

  You use the $esxcli I'm afraid.

• All share storage iscsi connect same target and volume

  Hi Alls,

  I have openfiler and do 1 iscsi volume share in two ESX hosts with even described as iscsi target.

  So a (first) ESX have dynamic config discover iscsi target and the format of finishing, so ESX block size have new data store come from iscsi.

  Another ESX must sign in with the same ip address of the iscsi target and even target iqn. then discover iscsi and rescan datastore have see the name of name identical to that found on ESX first data store.

  (Note for second ESX is not block format size but rescan HBAS/VMSF found eponymous store data like first ESX)

  Issue.

  1. for iscsi target that have one objective and correspond to a volume on openfiler can operate with 2 ESXs at the same time with the same target?

  2 if not, how to configure shared storage with openfiler that can used data volume on openfiler?

  Kind regards

  Bancha

  Like I said before, vMotion can saturate an uplink, so you will need to keep an eye on it. If you want to perform vMotion on the same vSwitch anyway, I suggest you create a group of separate ports with private IP (e.g. 192.168.x.y) addresses for her and let the two active vmnic for this group of ports allow failover in the event of an uplink failure.

  André

• iSCSI with two uplinks

  
  Can I connect more than one uplink to iSCSI storage?

  Yes you can multiple iSCSI adapters (as far as I know up to 4), each with its own group of VMkwernel iSCSI ports and IP address (assuming you are using SW iSCSI).

  André