iSCSI Datastore Expansion

Similar Questions

• iSCSI datastore - no action listed?

  Hi all

  I don't know if it's a problem or worry about.  I have 2 datastore iSCSI connected to 4 host ESX 3.5 U3. The data store original watch information when I select the store data and properties it will list the extent and the information on the measure, but the other data store which is a new data store that was created it does not show extend them or information, when I go into the properties of the data store.  But the new data store is formatted as vmfs 3.31 and I could svmotion all our VMs above it and everything seems to work.  My questions is this normal to have no information of measurement for a data store and still work?

  Hello

  I had the same GUAR.

  Please visit http://kb.vmware.com , and see 1003064 KB

  Good day.

• Cannot access the synology on nested host iscsi datastore

  I installed a Synology ds 414 version - 5-2-5592, with 2 volumes prescribed as 2 iscsi targets, I'm running 2 esxi 6 guests, a physical and a nested, phyiscal host I can access the target immediately without any problem, the host nested when I use the dynamic discovery, I can see the target via the static mapping but LUNS never appear and I can't add them as data stores.

  I put the target to allow multiple sessions on the synology, I can ping from the nested host synology vmk. I added the host nested as initiator allowed on the Synology, although I didn't need to do it on the first host as default value is set to read / write and there is no authentication set to synology.

  I have attached a few screenshots

  Any help would be greatly appreciated.

  

  You have activated on your physical host vSwitch promiscuous mode? See this thread to another: Nested ESXi 5.1 and iSCSI Shared Storage

• Resize a shared iSCSI datastore, need manual updating?

  Hi all

  Several ESXi 4.0 hosts connected to an iSCSI lun.

  I noticed that when I resize the LUN, should I do a manual rescan on the adapter of storage on each host to recognize the new format?

  Is the conduct of intention?

  Thank you.

  Yes.

  André

• Cannot add iSCSI Datastore

  The problem:

  When you add a new data store, I am able to see all the LUNS that I am about to add. When I add the storage, I receive errors that the object reference is not valid, and the operation fails

  The events that led to this problem:

  This iSCSI storage is off-production... I'm experimenting with VDR (really cool btw, I look forward future versions). As it's storage without importance, when I decided to make some radical changes to the storage, I have simply entered in the SAN and said that it is set at the factory. I made no changes to the vCenter or ESX storage configurations.

  Other information:

  -When you add the data store via the "Add Storage" of the vSphere Client Wizard, the first issue of logic unit in my new volume shows as having a label «VDR (head)» VMFS Yes, the old data store that I didn't not remove properly called VDR.

  -The LUNS in the SAN have been removed, and the new LUNS have been created.

  Anyone has any ideas on where to start? For me, the logical place to start looking is where defunct VDR data store data takes place, so that I can clean that information... I don't know where that would be.

  Your ESX4 running?

  esxcfg-scsidevs - m

  Will give you the/dev/name for VMFS Volume names

  and

  esxcfg-scsidevs - l

  Gives you the vml/dev/name you can check

  If DD \u003d/dev/zero of = / dev/account name = 2048 bs = 512

  It blows away (first backup)

  http://blog.laspina.ca/

  vExpert 2009

• Remove an iSCSI Datastore VMFS

  We are currently migrating to NFS over iSCSI and while doing some tests, I deleted a vmfs ISCSI using the VIC data store. When I went to add to the data store to the esx server, he said the volume was empty. If you do this with NFS, you can mount the volume again as it does not destroy the volume.

  My question is what happens if you want to remove the data store because you no longer want on ESX01, but you always want on ESX02. The volume will be destroyed and therfore ESX02 will not see this volume?

  Another question I have is what happens if I have an ESX machine that created the data store, then on another computer ESX try adding the same data store. The data store appears as empty when you try to create the volume on the second machine?

  Thank you

  Rombus wrote:

  So would do you by deleting the IP address of the esx of its list on the target server and then re-scan?

  Yes, but réanalysant does that with iscsi HBAs (even here the deletion of the target may be necessary); with software disable it, kill, and activation of the initiator iscsi is required (commands on the console) - or you restart your Esx host.

• How to replace ESXi properly to keep the iSCSI datastore?

  Hi guys,.

  I explore ESXi on a usbstick. It connects

  a NAS server using iSCSI. It works fine, until I screwed something on the

  Configuration of ESXi that it cannot be managed again VI client.

  Thus,.

  I have replace the usbstick by a new one. Again install ESXi and iSCSI.

  He finds the logic unit number, but it gives warning that using this LUN will destroy

  all data in this document, which destroys fortunately when I click OK.

  Thus,.

  in this case, it is good way to regain the intact data store if we

  you will need to change the ESXi? Or, there is no such scenario?

  Thank you.

  Hello

  So a VMFS store be reintroduced to ESX or ESXi the VMFS volume must be readable and correspond to the EUI header / NAA set to paths of storage host created in the esx.conf file or the VC DB vml. If this information is not present while the volume will not be presented as a usable existing VMFS store. I have a blog with some examples to reinstate VMFS stores based on OpenSolaris and ZFS iSCSI volumes.

  http://blog.laspina.ca/roller/ubiquitous/entry/provisioning_disaster_recovery_with_zfs

  You can examine the EUI or NAA on any VMFS work and ESX volume with the following command.

  esxcfg-vmhbadevs - m

  This gives command the name of dev which are associated with the volume and this info you can use hexdump similar to the following.

  hexdump - n 1100000/dev/sda1

  The hexagonal header data will present it as this example output, the value in bold is the guid of stores.

  0100000 d00d 0003 0000 0010 0000 1602 0002 c001

  0100010 0600 5553 204th 2020 2020 4f43 534 d 4154

  0100020 2052 2020 2020 2020 2020 2e31 2030 0160

  0100030 f044 0004 0000 2 a 49 142F 0400 4f43 d47e

  0100040 0000 0000 0000 0000 0000 0000 534 d 4154

  0100050 0000 0000 0000 0000 0000 0200 0000 f800

  0100060 0031 0000 0001 0000 0000 031f 031f ffd4

  0100070 0000 0321 0000 0000 0000 0000 0110 0000

  0100080 0000 3eee 492 has 7cb8 960f 2-0200-6755 16 c

  4e14 0100090 7fda dec9 5 c 68 0004 cf98 managenment 5 c 68

  01000a 0 0004 0000 0000 0000 0000 0000 0000 0000

  01000b 0 0000 0000 0000 0000 0000 0000 0000 0000

  With this information, you can recreate the vml, but it is difficult you should know the format, but for example, we can go.

  Use the following command to see what exists in a lot of work.

  cat /etc/vmware/esx.confcat /etc/vmware/esx.conf | grep vml

  /Storage/LUN/VML.0200020000600144f07ed404000000492a2e140004434f4d535441/adapteriqn.1998-01.com.VMware:vh0.1/targetiqn.1986-03.com.Sun:02:1eddb8ec-CC09-62d0-B867-8da28dee9609/

  Here we see the part that must match in blue.

  Also a little advice on usb based ESXi priming devices, you should not run this type of config at least as the creator of the image usb provided a virtual disk for the swap area.

  Flash multi layer devices will fail quickly if the swap partition area is on the flash device.

  Kind regards

  Mike

• Storage of da Migrazione VM FC ISCSI storage

  Hello to all,

  Abbiamo due separate infrastrutture:

  UNA composed da due uno condividono storage server esx 4.1 company (S1 and S2) che FiberChannell 4 GB;

  the Altra composed da due 4.1 esx Server enterprise (S3 S4 e) che condividono uno storage ISCSI 1 GB;

  Infrastrutture sono currently separate e non hanno some punto di outdo, pure resiedendo nello stesso CED due.

  Un'esigenza di dismettere storage FiberChannell, migrare e lo abbiamo tutti i vmdk (has all the VM) dallo storage FiberChannell a quello ISCSI.

  Soluzione più semplice ed economica che ipotizzo di offers:

  (1) collegare, per mezzo di hba iscsi items, ed S1 S2 agli SAN ISCSI a cui sono treatment S3, S4 switch e lo storage ISCSI;

  (2) add I have datastore dello storage ISCSI ad ed S1 S2;

  (3) do the dei dai dello CF IA dello storage ISCSI datastore datastore vmdk migrazione.

  Che doesn't think?

  Ciao,.

  Confermo gli sono quelli corretti steps.

  Verification prima di avere nic available su e S1 S2 e ovviamente door release sugli switch.

  Oltre an IOC, to Magdalene vorrai he multipathing known iSCSI, ti consiglio di leggere questo post.

  http://virtualgeek.typepad.com/virtual_geek/2009/09/a-multivendor-post-on-using-iSCSI-with-VMware-vSphere.html

  Ciao

• iSCSI issue

  Hello everyone,

  I'm experimenting with iscsi san for my storage. I use open-e as the software. So far, I guess that everything works. In Vsphere, I did new data warehouses. And in my VMs, I can connect to the correct data store and use it as a player. But there is something that does not appear clear to me. When I connect a data store to a virtual machine and start to fill with data, there is no problem.

  When I take a second vm and connect it to the same data store, I don't see what I put it through my other virtual machine data. Is this normal and can I change this so I can see the same information in both my VM?

  Thank you very much

  onkt

  If I get you right... looking for a concept of disk shared between two virtual machines with your iSCSI datastore...

  VMware only supports MCSC 2 NŒUD clustered VM to have a shared drive...

  Please follow the link for details of configuration below: http://www.vmware.com/pdf/vsphere4/r40/vsp_40_mscs.pdf

  Please consider clicking on the button 'OK' or 'Useful', if this information is useful.

• Esxi4 + iSCSI crash test trouble

  Thus,.

  I have use ESXi4 + iscsi datastore without flaw.

  But today I tried a crash test.

  In Vsphere Client, I delete (disconnect) the Datasore and then I removed the iSCSI card. Exactly what would have happened if my server crash ESXi and I need to reinstall from scratch.

  Then I re - create a my target iSCSI iSCSI adapter: ok

  I connect a new data store based on my iSCSI adapter, but the problem is: I can not just ride my 'old' iscsi volume, he always wants to create new formatted volume!

  So, how could I, only, to mount my existing iscsi volume?

  Thanks for the kind help

  Used items:

  ESXi4

  VSphere Client

  StarWind free with volume of virtual hard disk

  You will be able to add again, because you will remove the masking of the logic unit number at the end claimrule.

  You also can anyone the LUN on the storage side, but it's the way specific to the operation.

  Marcelo Soares

  VMWare Certified Professional 310/410

  Technical Support Engineer

  Globant Argentina

  Review the allocation of points for "useful" or "right" answers.

• Try to test ESX4 with test iSCSI (FreeNAS)

  Hello

  I learn about VSphere, ESX4 and iSCSI and a simple way to assess it is to use the FreeNAS with ESX4 60 day trial.  We will get a solution EMC SAN and VSphere full blown, installed in the coming months, but I would like to have a little play time of first hand.

  So I FreeNAS installed in VMWare Workstation with SCSI 4 72 GB disks.  These disks in a RAID5 configuration and iSCSI is enabled.  I can connect to iSCSI using the Microsoft iSCSI initiator.  I can format the drive and store the files that it contains.  He has even worked with ESXi 3.5, but I have since then wiped to try the latest version of VMWare VSphere4.

  For the life of me, I can't add this iscsi datastore.  In vSphere client under Configuration > storage adapters, I have the connection iSCSI vmhba33 to the FreeNAS box NetBSD iSCSI disk (iqn.1994_04.org.netbsd.iscsi_target, 0x4a71bbb1667c11de), name of runtime: vmhba33:C1:T0:L0, 216 GB of capacity.

  Now under Configuration > storage, I try to create the data store.  Add storage > disk/LUN > choose my iSCSI option only displayed, name it vmds1, 256 GB, block size: 1 MB, maximize the capacity, next, finish.  In a few minutes, I get always an error ' error in the configuration of the host: unable to create the file system, please see VMkernal log for more details.  Under FreeNAS that I tried formatting as EXT2, FAT32, NTFS or leaving no formatted.  No work.

  I remember having a heck of a lot of trouble to get this to work with ESXi 3.5, but I end up getting things backwards and 2 virtual machines running.  Although I did jump immediately to try to vSphere 4.  Now I don't remember what I did, or maybe this version does not play nice with FreeNAS iSCSI implementation.

  On the events tab, I see lots of "connectivity lost to the iqn.1994_04.org.netbsd.iscsi_target, L, 0x4a71bbb1667c11de of storage device.  Vmhba22:C1:t0:l0 path is down.  Touch of data warehouses: "VMDS1."  Recovery attempt is underway and results will be communicated shortly. »

  There is an inscription that says "restored access to the 4a4bc1e1-f4bb4a45-cc91-000c2910ccd5 (VMDS1) volume due to connectivity problems successfully.

  Even if it is followed by more 'Lost connectivity' message above.

  I'm really tired.  I really want to play with that using iSCSI to simulate our future iSCSI EMC SAN.  Any help is greatly appreciated!

  I use several laboratory purposes but for me Openfiler was easy to install and administer. A decent free ISCSI SAN network.

  http://www.Openfiler.com/

  In addition, because you are looking at EMC you might want to take a look at their Celerra VSA (virtual SAN) for laboratory use.

  Check out this post from Chad - http://virtualgeek.typepad.com/virtual_geek/2008/08/celerra-virtual.html

• Linked clone failed: the operation is not supported on the object

  Hi all - I would appreciate help on a related clone operation that is a failure.

  I use Quest vWorkspace to create linked clone VM in my environment.  It integrates with virtual Center and creates from a VM snapshot parent according to normal related clones.  It has just stopped working and I am trying to track down the cause.  The task fails with the error message in the console of VMware vCenter: the operation is not supported on the object.

  The vCentre is 5.5 and esxi.  vWorkspace is v8.0 MR1.  The parent VM is located on an iSCSI datastore.  I tried to put the clones of destination on premises and warehouses of NFS data with the same result.  Unfortunately I can't (don't want really to) move the VM parent from the data store that I have of many VM related to this virtual machine.

  The failure message is a bit generic, so I looked on through the vmkernel.log and vpxa.log and it is an excerpt from the vpxa.log whereby it shows failed task 153.  Can someone please indicate something in the newspaper that had to be examined or another newspaper to look at?

  vWorkspace attached error and below:

  Linked clone has not CreateLinkedClone_Task of CloneVmLinked failed! Task of VMware CreateLinkedClone_Task status error - the operation is not supported on the object. -Call stacks-VmLinkedClone.VmLinkedCloneService.CloneVmLinked String vmInvPath, String strSnapshotMor, String strNewVmName, String strSysprep, ManagedObjectReference morFolder, ManagedObjectReference morResPool, ManagedObjectReference morHost, String strDatastoreName, Boolean bQuickPrep, String domainNameIP, String

  See attachments

  Thank you very much
  Wikus

  Additional accessories:

  • 
    Untitled picture.png

  Hello guys,.

  For those of you already on 5.5, I did a few tests these days. I did find a magic bullet yet as a single parameter that is sure to break but I came up with a workaround.

  I found that if my ESXi server was still on the 5.1, vWorkspace could deploy clones linked via vCenter 5.5 - it's only when the ESXi is also on 5.5 that you have a problem.

  If any of you have ESXi hosts still on 5.1, you can deploy there for now.

  In ESXi 5.x, it is easy to have an ESXi virtual machine. You might want to consider creating some virtual boxes ESXi to deploy on while the vworkspace dev team look at why it does not work.

  I know that this is not the best solution in the world, but it's better than no work around

  Thank you, Andrew.

• Extremely high latency during the migration of the local data store to data store shared.

  Hi guys I hope you help me. Sorry for my English btw, I'm not native.

  Let's start!

  I have:

  1 vCenter
  1 host
  1 Distributed Switch (with a pg for managing network/IPstorage the esxi)
  1 standard switch (empty)
  1 FreeNAS to provide iSCSI LUNS
  1 Microsoft to provide iSCSI LUNS

  When I try to migrate virtual machines between the warehouses of shared data or data shared at local store, all right. The problem has become when I try to migrate virtual machines from the local to the shared data store. All data stores down (all paths down) and back up and I get this error:

  "Error caused by the /vmfs/volumes/volumenID/VMDirectory/Disk.vmdk file.

  
  When I try to migrate virtual machines from the local to the FreeNAS iSCSI data store it fails immediately.
  When I do the same local Microsoft iSCSI datastore that it takes a time loooooong to migrate the virtual computer, give it to me even all the paths downwards and uplinks down error but not lacking in migration.

  I'll give you some screenshots to see the errors.

  Thank you very much!

  EDIT: I have extremely high latency notice when I try to migrate from the premises of warehouses of shared data. average 2000ms with peaks of 50,000 (see my response below for more information)

  Finally, I found the solution! The problem is that I have been using E1000E vmnic instead of vmxnet3. I have configured an adapter vmxnet3 and boom! 20 ms in all migration!

  Thank you to all for help, especially Nick_Andreev !

• web cluster server + database con NetApp: NFS if o... so?

  Dovro'usare bring in VMWare (ESXi 4.1 Standard) quello che fu ambiente a web cluster (classico apache con MySQL db) fatto di 8 webserver substitutes + 2 db server + only netapp spinning in nfs, che e stato poi "virtualizzato" con Xen sulle stessa macchine, cluster UN producendo con circa 20 VM no rilocabili...

  Ed e venuto he momento di passare in ambiente più semplice

  He materiale nuovo knew cui dovra run it tutto sara fatta da 3 host VMWare (96 GB RAM) e a NetApp FAS2020 file server.  He continue a NetApp da fare in NFS server file by I got the VM su cui girera apache (o lighthttpd).

  He progettuale e problema: visto che he NetApp develop sleep Reed it / I datastore with VMWare vale pena di complicarsi vita collegandolo in agli FCP (o iSCSI) ESXi host? Oppure, come sto vedendo Giro per the rete, it guadagno di prestazioni sulle VM using FCP/iSCSI Datastore dedicated NAS minimo sembrerebbe che, tale da non is the major complicazione.

  The VM che make run apache mi preoccupano poco, sul disco local fanno UN I/O minimo (gli da servire are sul Server html file).

  Quelli che mi danno da Winegardner sound system I server MySQL che hanno a carico UN alto volte (especially complesse selection-join database market not su benissimo per quanto far indici etcetc).

  Note: he FAS2020 e a quindi "dog testa" in situation normal CPU servirebbe una VM che lo montano in NFS mentre l'altra servirebbe gli VMWare host. In caso di di una delle due fault tests quella che viva takes in carico remains there lavoro di quella guasta.

  Grazie in anticipated!

  Diciamo che can be bet... The funzioni che maintain a NFS (ad esempio IGCS) probabilmente saranno clogs nella versione next.

  POI ogni cosa will Reed "calzata' nel momento storico...

  This era dell Anno'iSCSI e tutti dicevano che era he meglio

  Adesso è Unified storage e dicono che molti NFS e meglio.

  Personally consider ancora valido the CF, my / certi progetti e iSCSI NFS alternative valid sound.

  Andrea

• Aprarece RAW DEVICE MAPPING

  Hola

  Quiero crear una nueva virtual infrastructure mi Máquina y estoy lanzando el Assistant "customized" para indicarle "raw device mapping" hacía una lun of the cabina ISCSI as tengo.

  Me appears "aprarece" in gray.

  ¿Esto porque?, put back esx ven el cabina física, asi como el iscsi datastore software iscsi as tengo con openfiler, y tengo MVs running en esos data warehouses.

  ?¿?¿¿?

  Gracias

  Hola,

  ESO are, primero lo tiene than ver el ESX como una LUn, luego el disco Crystal for the VM as RDM lun of the esa.

  Saludos