ISCSI Volume resizing

Similar Questions

• NAS to Nas backup for iSCSI volumes

  Hello

  I have a NAS PX12-400r, with some volumes are configured as iSCSI volumes, connected to different servers.

  I would like to find a nas to nas backup solution, in order to back up or synchronize the entire volume to an another NAS PX12-400r.

  I want to do it using only the SAR in a transparent way for servers connected to iSCSI volumes, or one-third of the machine.

  Concerning

  Gabriele

  Hello ecohmedia,

  For NAS to NAS (data) transfers, your only option is running from part to part.

• Configure the iSCSI Volumes

  Hi all!

  Its the first time install Ubuntu Server on a Power Edge 2950 to me and
  The question is when it comes to partitioning, it said that it has detected that active SATA disks--"one or more drives containing Serial ATA RAID configurations have been found. You want to activate these RAID devices? Turn on Serial ATA RAID devices. They gave me two options 'Yes' or «» I clicked 'Yes' because I thought that this would allow Ubuntu server configure RAID1 during installation. However, I was led to the disks Partition that says "this is an overview of your currently configured partitions and mount points. Select a partition to modify its settings..., and there are three options to choose from, namely:
  Configure the iSCSI volumes
  Undo changes to partitions
  Finish partitioning and write changes to disk

  So I don't know if I'm doing the thing to write here. When I chose 'To configure iSCSI Volumes', I was prompted to choose either log on to the target iSCSI or finishing. I don't know what to do from here.

  Any help would be greatly appreciated.

  Thank you

  I found the solution, the problem was that the hard drive Master Boot Record was not present.

  I run a Ubuntu Live CD and install it. The hard drive is already detected and the installation was successful.

  Thank you very much!

• Adding additional iSCSI Volumes?

  I have a cluster of 2 esx 4.0 host connected to an equallogic SAN.  Currently, the ESX hosts are connected to 1 volume on the equallogic and he VM 10-15 running using equallogic volume.  I created a new volume on the equallogic and configured to allow access of the two hosts.

  My question is the following: to add the new volume for ESX hosts, should I simply go to each iSCSI host initiator and do a rescan "volumes"?  Is there any problem that would affect the other connected volume or the virtual machine; s that are on it?

  Thank you

  My question is the following: to add the new volume for ESX hosts, should I simply go to each iSCSI host initiator and do a rescan "volumes"?

  That should do it.

  Is there any problem that would affect the other connected volume or the virtual machine; s that are on it?

  I've never had one with EQ and renumerisations - you should be fine here.

• Impossible to create great on ESX iscsi volumes

  Hi all

  I have 2 servers to ESX 4.1 new installation u1 nine directly connected to the new HP P2000 iscsi storage facility.
  HP Storage has 4 1 GB iscsi ports.
  They are:
  PortA1: 10.0.0.1
  PortA2: 10.0.0.2
  PortA3: 10.0.0.3
  PortA4: 10.0.0.4

  
  As you can see from the photos storage1 and storage2, I assigned Port A1, A2 to ESX1
  Other PortA3 and A4 to ESX2.
  I have on two servers, 10.0.0.5 and 0.6 vmkernel

  As you can see from picture1 iscsi connections seems to be OK. What I normally do after that is to go to Storage - storage to add.
  Image2 is what I see of the storage option that you want to add. And I got error on photo3

  Don't you think that it is bound to no limitation of capacity because I created a LUN with less than 2 TB and it worked very well.
  So should I split 6 to a 3 to make it less than 2 TB? should be a silly thing to divide it. There should be another options I guess?

  Thank you.

  This limit if for VMFS.

  NFS is not at the level of the blocks and he doesn't use VMFS, so you can have a great store of data.

  But vmdk are still limited to 2 TB max.

  André

• Reattach the EqualLogic iSCSI for 2012 Windows volumes

  Hello

  We use EqualLogic, Windows 2008R2, HIT and initiator iSCSI access volumes. Now I'm re - install OS to Windows 2012. All materials, IP addresses, volumes, host name will be the same on the new operating system. BONES of some changes. Will it be the right way to remap the iSCSI volumes to the new operating system:

  1. on windows 2008 R2 take the volume offline in the disk management console.
  2. disconnect "Discovered targets" in the Windows iSCSI initiator.
  3 collect volumes offline in Manager Dell EqualLogic Group (to restore the connections).
  4. the new 2012 Windows Installer 4.5 HIT and set (is this version of the correct software for Windows 2012?)
  5 activate the volumes in the Dell EqualLogic Group Manager.
  6. Discovery target and connect to targets.
  7 collect volumes online in the OS disk management console.

  These steps are correct?
  Are they all necessary?
  Is a correct software 4.5 for windows 2012 HIT?

  Thank you

  Re: connections.  Are you referring to the iSCSI to table sessions?   If so, those are dynamic.  When you stop they will disappear.

  If everything is the same, so technically Yes.  Shutdown, you can reload and bring it to the top.

• 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 - can not share a lun/volume between 2 hosts?

  I've just set up ISCSI SAN with 2 empty volumes.

  I added one of the volumes to server1. It says space free 418G.

  I then tried to add the same amount to server2 and he says there is no available capacity, and that the current structure of the disk will be destroyed if I continue.

  ISCSI volumes cannot be shared between hosts?

  I was going to move a virtual machine server1 on the volume, then browse the data store and add the virtual machine via a right-click the vmx file

  Yes you can. But you don't need to create a new VMFS volume. Rescan just your HBA on the second server that's all there is to him.

  Duncan

  VMware communities user moderator | VCP | VCDX

  -

• ASM Volumes ISCSI thin-set in service in volumes of dirty

  Hi, we have some EBS test case is going and that you are testing auto-prolonger (into reasonable pieces) on an ISCSI volume thin-set in service to the layer of database 11g. Something does not seem right however: in general I see about 55 GB used by data files, but about 95 percent of the thin-set volume in service is marked modified.
  
  Obviously, this sort of deny the utility of thin provisioning at all, but I can't help thinking that there is something else at work here. Does anyone have any experience with this situation and if so what settings can be defined to do what we try to do a work really right?

  ASM is designed to put a wrapper around raw devices leaving (Oracle DBWR, process server) software to read/write directly from a crude into pieces drive "to THE" (AUs being 1 MB by default), rather than "block pieces. For me, the best way to understand it is: the process that wants to work with the disk request ASM where au.

  To do this, ASM itself will have to 'index', the location of each AU and blocking is involved. Which, in turn, would require ASM analyze the whole score to determine locations, which might as well mark the blocks as 'reserved '.

  If my conjecture is true (and seems to be based on "Oracle automatic storage management: under the hood & practice Deployment Guide" (http://www.amazon.ca/Oracle-Automatic-Storage-Management-Under/dp/0071496076) as well as another reading and supported by your conclusion), then it is not a surprise that the entire volume is assigned and be considered dirty.

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

• ESXi 6.0 U1 U2 upgrade, iSCSI questions

  Hello

  First post, so I'll try and summarize my thoughts and what I did with troubleshooting.  Please let me know if I left anything out or more information is required.

  I use the free ESXi 6.0 on a Board with a CPU Intel Xeon E3-1231v3 and 32 GB of DDR3 ECC UDIMM mATX to Supermicro X10SLL-F.  I use a 4G USB FlashDrive for start-up, 75 GB 2.5 "SATA to local storage (i.e. /scratch) and part of a 120 GB SSD for the cache of the host, as well as local storage.  The main data store for virtual machines are located on a target (current running FreeNAS 9.3.x). iSCSI  This Setup worked great since installing ESXi 6.0 (June 2015), then 6.0 U1 (September 2015) and I recently made the leap to 6.0 U2.  I thought everything should be business as usual for the upgrade...

  However, after upgrading to 6.0 U2 none of the iSCSI volumes are "seen" by ESXi- vmhba38:C0:T0 & vmhba38:C0:T1, although I can confirm that I can ping the iSCSI target and the NIC (vmnic1) vSwitch and VMware iSCSI Software adapter are loaded - I did not bring any changes to ESXi and iSCSI host before the upgrade to 6.0 U2.  It was all work beforehand.

  I went then to dig in the newspapers; VMkernel.log and vobd.log all report that there is not able to contact the storage through a network issue.  I also made a few standard network troubleshooting (see VMware KB 1008083); everything going on, with the exception of jumbo frame test.

  [root@vmware6:~] tail - f /var/log/vmkernel.log | grep iscsi

  [ ... ]

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T: 0 CN:0: iSCSI connection is being marked "OFFLINE" (event: 5)

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: TPGT (null): TSIH 0: 0]

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 10.xxx.yyy.195:41620 r L: 0: 10.xxx.yyy.109:3260]

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T:1 CN:0: connection iSCSI is being marked "OFFLINE" (event: 5)

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: TPGT (null): TSIH 0: 0]

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 10.xxx.yyy.195:32715 r L: 0: 10.xxx.yyy.109:3260]

  [root@vmware6:~] tail - f /var/log/vobd.log

  [ ... ]

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622023006us: [vob.iscsi.connection.stopped] iScsi connection 0 arrested for vmhba38:C0:T0

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622023183us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 could not connect to iqn.2005 - 10.org.freenas.ctl:vmware - iscsi because of a network connection failure.

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622002451us: [esx.problem.storage.iscsi.target.connect.error] connection iSCSI target iqn.2005 - 10.org.freenas.ctl:vmware - iscsi on vmhba38 @ vmk1 failed. The iSCSI Initiator failed to establish a network connection to the target.

  2016 03-31 T 05: 05:48.218Z: [iscsiCorrelator] 1622023640us: [vob.iscsi.connection.stopped] iScsi connection 0 arrested for vmhba38:C0:T1

  2016 03-31 T 05: 05:48.218Z: [iscsiCorrelator] 1622023703us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 could not connect to

  [root@vmware6:~] ping 10.xxx.yyy.109

  PING 10.xxx.yyy.109 (10.xxx.yyy.109): 56 bytes

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 0 ttl = 64 time = 0,174 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 1 ttl = 64 time = 0,238 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 2 ttl = 64 time = 0,309 ms

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 3 packets received, 0% packet loss

  round-trip min/avg/max = 0.174/0.240/0.309 ms

  vmkping [root@vmware6:~] 10. xxx.yyy.109

  PING 10.xxx.yyy.109 (10. xxx.yyy. 109): 56 bytes

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 0 ttl = 64 time = 0,179 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 1 ttl = 64 time = 0,337 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 2 ttl = 64 time = 0.382 ms

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 3 packets received, 0% packet loss

  round-trip min/avg/max = 0.179/0.299/0.382 ms

  [root@vmware6:~] NF - z 10. xxx.yyy3260.109

  Connection to 10. xxx.yyy3260.109 port [tcp / *] succeeded!

  [root@vmware6:~] vmkping 8972 10 s. xxx.yyy.109 - d

  PING 10.xxx.yyy.109 (10. xxx.yyy. 109): 8972 data bytes

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 0 packets received, 100% packet loss

  I began to watch the drivers NIC thinking maybe something got screwed up during the upgrade; not the first time I saw problems with the out-of-box drivers supplied by VMware.  I checked VMware HCL for IO devices; the physical NIC used on that host are Intel I217-LM (nic e1000e), Intel I210 (nic - igb) and Intel® 82574 L (nic-e1000e).  Lists HCL from VMware that the driver for the I217-LM & 82574L should be version 2.5.4 - I210 and 6vmw should be 5.0.5.1.1 - 5vmw.  When I went to check, I noticed that he was using a different version of the e1000e driver (I210 driver version was correct).

  [root@vmware6:~] esxcli list vib software | e1000e grep

  Name Version Date seller installation acceptance level

  -----------------------------  ------------------------------------  ------  ----------------  ------------

  NET-e1000e 3.2.2.1 - 1vmw.600.1.26.3380124 VMware VMwareCertified 2016-03-31

  esxupgrade.log seems to indicate that e1000e 2.5.4 - VMware 6vmw should have been loaded...

  [root@esxi6-lab: ~] grep e1000e /var/log/esxupdate.log

  [ ... ]

  # ESXi 6.0 U1 upgrade

  2015-09 - 29 T 22: 20:29Z esxupdate: BootBankInstaller.pyc: DEBUG: about to write payload "net-e100" of VIB VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585 to "/ tmp/stagebootbank".

  [ … ]

  # ESXi 6.0 U2 upgrade

  2016-03 - 31 T 03: 47:24Z esxupdate: BootBankInstaller.pyc: DEBUG: about to write to payload "net-e100" of VIB VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585 to ' / tmp/stagebootbank '

  3.2.2.1 - 1vmw e1000e is recommended for 5.5 U3 and not 6.0 U2 ESXi ESXi driver!  As these drivers are listed as "Inbox", I don't know if there is an easy way to download the drivers supplied by seller (vib) for him, or even if they exist.  I found an article online to manually update drivers on an ESXi host using esxcli; I tried check and install the new e1000e drivers.

  [root@vmware6:~] esxcli software update net-e1000e-n-d vib https://hostupdate.VMware.com/software/VUM/production/main/VMW-Depot-index.XML

  Result of the installation

  Message: The update completed successfully, but the system must be restarted for the changes to be effective.

  Restart required: true

  VIBs installed: VMware_bootbank_net - e1000e_3.2.2.1 - 2vmw.550.3.78.3248547

  VIBs removed: VMware_bootbank_net - e1000e_3.2.2.1 - 1vmw.600.1.26.3380124

  VIBs ignored:

  As you can see there is a newer version and installed it.  However after restarting it still did not fix the issue.  I even went so far as to force the CHAP password used to authenticate to reset and update on both sides (iSCSI initiator and target).  At this point, I wonder if I should somehow downgrade and use the driver of 2.5.4 - 6vmw (how?) or if there is another issue at play here.  I'm going down a rabbit hole with my idea that it is a NETWORK card driver problem?

  Thanks in advance.

  --G

  

  I found [a | the?] solution: downgrade for 2.5.4 drivers - Intel e1000e 6.0 U1 6vmw.  For the file name, see VMware KB 2124715 .

  Steps to follow:

  1. Sign in to https://my.vmware.com/group/vmware/patch#search
  2. Select ' ESXi (Embedded and Installable) ' and '6.0.0 '.  Click on the Search button.
  3. Look for the update of the release name - of - esxi6.0 - 6.0_update01 (released 10/09/2015). Place a check next to it and then download the button to the right.
     
  4. Save the file somewhere locally. Open archive ZIP once downloaded.
  5. Navigate to the directory "vib20". Extract from the record of the net-e1000e.  In East drivers Intel e1000e ESXi 6.0 U1: VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585.vib
     
  6. This transfer to your ESXi Server (be it via SCP or even the file within the vSphere Client browser). Save it somewhere you will remember (c.-a-d./tmp).
  7. Connect via SSH on the ESXi 6.0 host.
  8. Issue the command to install it: software esxcli vib install v - /tmp/VMware_bootbank_net-e1000e_2.5.4-6vmw.600.0.0.2494585.vib
     
  9. Restart the ESXi host.  Once it comes back online your datastore (s) iSCSI / volumes should return.  You can check by issuing h df or the list of devices storage core esxcli at the CLI prompt.  vSphere Client also works
  
  

  It took some time to find the correct file (s), the steps and commands to use.  I hope someone else can benefit from this.  I love that VMware can provide for virtualization, but lately, it seems that their QA department was out to lunch.

  Do not always have a definitive explanation as to why Intel e1000e ESXi 5.5 U3 drivers were used when ESXi 6.0 U1 U2.  Maybe someone with more insight or VMware Support person can.

  & out

  --G

• iSCSI storage problem ESXi 5 u1

  Hello

  We have six ESXi 5 u1 servers connected to the storage unit Dell EqualLogic 65xx series. On ESXi systems we use the iSCSI Software and PSP is set to RoundRobin. We investigated a question where randomly throughout the day that we receive the following warning:

  VCenter:

  Failed to write command to write-suspended partition naa.6090a08890b27eeab8cee499fb01a0f6:1

  VMKernel:

  WARNING: ScsiDeviceIO: 3075: order of writing-suspended bulkhead 6090a08890b27eeab8cee499fb01a0f6:1 write failure

  Capability3: 13359: Max (10) attempts exceeded for appellant Fil3_FileIO (status "IO has been abandoned by VMFS via virt-reset of the unit")

  BC: 1858: cannot write (couriers) object '. iormstats.SF': level core exceeded Maximum attempts

  Also, we see a lot of messages indicating a loss of connectivity, iSCSI volumes:

  Lost access to the volume (LUN_NAME) 4f58ac5f-ef525322-XXXXXXXXXXXXXXX because of connectivity issues. Recovery attempt is underway and the result will be
  reported in no time.

  This event is generated by all six guests at random time intervals and LUN iSCSI target different. At the same time, we notice a very high spike in CPU usage of 100% on the host that generates the message

  One thing we found through tests of vmkping is that ESXi hosts are configured for extended frames (9000 MTU vmk, vswitch and adapters), but the storage network, does not allow frames.

  This could be an indication of serious IP fragmentation on iSCSI? How we measure this?

  conraddel wrote:

  One thing we found through tests of vmkping is that ESXi hosts are configured for extended frames (9000 MTU vmk, vswitch and adapters), but the storage network, does not allow frames.

  This could be an indication of serious IP fragmentation on iSCSI? How we measure this?

  Do you know if the side SAN is configured for frames? If not, then it should probably not be a problem, given that the TCP connection will take care of the other so-called MSS sizes and your guests should get off by default the images of sizes.

  The worst situation would be if both the ESXi and the SAN supports jumbo frames, but not the switches between the two. Because the switches are 'invisible' problems don't happen, until you actually start sending larger images and those will arrive in silence by switches, i.e. no IP fragmentation.

  Have you also checked with vmkping what kind of end-to-end connectivity, you have? Options-d and s are very important get right: http://rickardnobel.se/archives/992

• LUN visible in tabs of discovery, and not in the devices in iSCSI storage adapters

  So, the gist of the problem is in the title. The question is finally: which would cause the iSCSI targets to appear in the static discovery tab of my iSCSI initiator properties, but do NOT appear in the list of devices in the details section of my properties of the storage card? I added the new IP address of my server iSCSI in the dynamic discovery tab and all appropriate records is immediately apparent in the static discovery tab, but I can't actually join one of them or add them to storage.

  Since his arrival in vSphere 5, I have more problems than in the past with iSCSI LUNS.  We recently had to do physical and IP changes, and I'm fighting to get my iSCSI volumes reconnected. Although I write about a specific instance (something I need to get up in production as soon as POSSIBLE), I experienced the same thing on a different cluster with a completely separate SAN.

  Anyone run into something similar? Basically, I know that guests can see the iSCSI volumes, but they are not available for me to add that the cluster storage.

  NOTE: This same storage was attached to the same group last week. The only thing that has changed is IPS adapters and the SAN. In addition, the Network Configuration of the iSCSI Software initiator tab shows all three links in linked vmk "compliant".

  Thank you

  Post edited by: inspiration (added a NOTE at the bottom)

  Hello

  Thanks for the update.

  VMware announced specifically that routed iSCSI is not possible unfortunately. So yes, the issue is software ESXi SCSI adapter. The problem is that it is often a good thing - many problems of performance on other platforms relate to routers on iSCSI.

• Initiators of software iSCSI Microsoft Cluster in guest

  Hi guys

  I have a client who have iSCSI Storage... now they want to create a cluster, but I read that only FC SAN is supported for RDM...

  but it seems that iscsi is supported as iscsi in guest...

  If someone knows the configuration for this?

  or is it as simple as:

  1. create iscsi volume of Quorum

  2. create iscsi for data volumes

  3 activate the iscsi initiator in Windows 2008 guest VM

  4 map these to W2008 VM iscsi volume

  5. create an another PortGroup-VLAN for the private heartbeat (is it necessary or the private sector can take thje same segment as the notrmal network)?

  Thank you very much

  Oh, sorry I didn't answer your original question.

  You are right, you must configure the virtual computer with 3 vNIC on 3 different subnets, then make sure that the public network is on top, when configuring the network order in the BONE (don't know where it was in 2008 for Windows, in Windows 2003 is configurable in the advanced network settings) Guest.

  André

• Static configuration of iSCSI targets

  I was playing with New-IScsiHbaTarget, but has problems.  Each of my iSCSI Target names has the same IP address for the iSCSI server, and he didn't like that.  I tried something like:

  New-HBA target HBA - vmhba33-address 10.0.0.10 - static Type - nomiscsi iqn.2003 - 10.com.lefthandnetworks:blah:blah - 001

  and that seems to work, but when I tried:

  New-HBA target HBA - vmhba33-address 10.0.0.10 - static Type - nomiscsi iqn.2003 - 10.com.lefthandnetworks:blah:blah - 002

  He would say that "the specified target '10.0.0.10:3260' already exists... but I can't add these volumes manually using the client vSphere...

  We have a bunch of iSCSI volumes, and we are forced to use static targets for each.  For each vmhba on each host (vmhba33, vmhba35), without a script, we have to manually add each iSCSI target name.  So for 5 guests with 2 adapters for iscsi and 10 Mon, it's 100 steps.  Or someone at - it a script that can add several static targets?-preferably something that can extend over several hosts.

  Thank you very much!

  You're right, this looks like a bug.

  Until the problem is resolved, you can use the AddInternetScsiStaticTargets method directly.

  Something like that

  $iScsiHba = "vmhba33"
  $esx = Get-VMHost MyEsx
  $hStorSys = Get-View $esx.ExtensionData.ConfigManager.StorageSystem
  
  $tgt1 = New-Object VMware.Vim.HostInternetScsiHbaStaticTarget $tgt1.address = "10.0.0.10" $tgt1.iScsiName = "iqn.2003-10.com.test.iscsiA"
  $tgt2 = New-Object VMware.Vim.HostInternetScsiHbaStaticTarget $tgt2.address = "10.0.0.10" $tgt2.iScsiName = "iqn.2003-10.com.test.iscsiB"
  $targets = @()
  $targets += $tgt1$targets += $tgt2
  $hStorSys.AddInternetScsiStaticTargets($iScsiHba,$targets)