Accessibility of the data store

Similar Questions

• Lost access to local data store

  Hi people:

  I have ESXi 6.0 running on an Intel S2600CWTS motherboard using the LSI SAS controller onboard and six readers Samsung 850 Pro SSD in a RAID 5 configuration.  This server is about a month and a half, and it worked fine for the first month, but in the last few weeks I started to do in the case where journal messages saying that ESXi has lost access to the data store, then, most of the time, about 15 seconds later access is restored.   Several times it took more time, which one crashed the server.  On these long, the motherboard Intel event log showed that a player had failed and began a regeneration and once the motherboard has shown that two different drives had failed, and it took both offline originally ESXi crashing.  On it that I was able to bring the two records back online via the RAID bios and everything worked fine again.  I suspect that I have hard disk problems because these discs are new and because different readers have been reported as failed, and also because no data has been lost even if 2 drives went offline at the same time.   I guess I could have a bad controller LSI, or a cable has come loose somewhere, but I expect to happen if it is really the case of data loss.

  I also noticed that lost access messages tend to appear in the log at the moment I start a virtual machine.  At first I thought that it would be one thing to flow, thinking a VM departure did a lot of IO, but this happens immediately, before even the bios of the virtual screen machine disappears, so I don't think that the virtual machine is actually reading the disc again.  In addition, as a precaution, I started the migration of some virtual machines on the server to the old server I still had available, and there is no lost access messages in the event log while that was happening, while about 50 megabytes per second of i/o has reached the disk during transfers.  I put the last patch on ESXi in mid-May, about two weeks before this started, and I begin to suspect that the patch may have something to do with it, because it seems to me that if something is happening between ESXi and the disk controller making hang up or lose interruptions during a short period of time , and I wonder if it goes pretty long if material in the motherboard sensors interpret this as some sort of hardware and simply brand failure according to readers I / O was hooked as bad then.

  Unfortunately I'm out of town now so I wanted more I had to the remote server, lest I do not not get back to the top.  I moved a couple of the most critical virtual machines from the old server which I was remotely start and transfer to virtual machines.  I also noticed that this issue tended to occur more frequently when I got to the top of the VCenter Server apparatus that any other (sometimes to others, but has happened every time I tried to start the device VCenter).  So who was the first that I moved to the old server, but strangely enough there is no error logged when I transferred the files, so the issue is not that ESXi had trouble reading the VMs vmdk file when I started it.

  I also wanted to ask you if there are any vibs for the LSI Megaraid controller on motherboard S2600CWTS I could install that would allow me to access the RAID controller without having to pick up the server and do it from the BIOS configuration screens, similar to how you can access the controller RAID from Dell while ESXi is running via a vib add-on.  So far I have not found one.

  My intention when I go to the server is to run an integrity check against the RAID 5 array via the controller and then use the AIMÉ ESXi utility on the data store to see if something is wrong here.  If not, then I guess I'll rewritten can patch.

  Ideas or suggestions welcome.

  Success!  I finally understood what the problem was corrected.  The problem is the fact that although the last vib driver LSI has been installed, for some reason any it would not automatically replace the default ESXi pilot lsi_mr3.  I did not notice that even though the latest driver package vib properly installed LSI controller was still using the original driver.  This could be considered by a 'esxcfg-scsidev - a' command showed that even "vmhba1 lsi_mr3 link-n/a sas.5001e67ca647e000 (0000:0: 00.0) controller LSI MegaRAID SAS Fury."  The second field after the controller (vmhba1) is the current manager used.  The pilot, which was to be used was: "vmhba1 megaraid_sas link-n/a unknown.vmhba (0000:03:00.0) Avago (LSI / Symbios Logic) Invader MegaRAID SAS controller.

  To fix this I had to disable the lsi_mr3 driver so that ESXi is forced to use it.  The procedure to do is the following:

  (1) make sure you have the new EXSi driver you want to use already installed.  I assume that bad things would happen if you have disabled the only driver who could run your disk controller.  Use this command to view the drivers installed: "esxcli software vib list" and you should get something similar to the following:

  [root@intelserver:~] esxcli list of software of vib

  Name Version Date seller installation acceptance level

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

  MegaRAID SCSI-sas 6.608.11.00 - 1OEM.600.0.0.2494585 Avago VMwareCertified 2015-07-19

  LSI - mr3 6.606.10.00 - 1OEM.550.0.0.1391871 LSI VMwareCertified 2015-06-19

  mtip32xx-native 3.8.5 - 1vmw.600.0.0.2494585 VMWARE VMwareCertified 2015-04-28

  ATA-pata-amd 0.3.10 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-atiixp 0.4.6 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-cmd64x 0.2.5 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-hpt3x2n 0.3.4 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-pdc2027x 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-serverworks 0.4.3 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-sil680 0.4.8 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-via 0.3.3 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  block-cciss 3.6.14 - 10vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  CPU-microcode 6.0.0 - 0.0.2494585 VMware VMwareCertified-2015-04-28

  EHCI-ehci-hcd 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  elxnet 10.2.309.6v - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  Emulex-10.2.309.6v - 0.0.2494585 VMwareCertified-2015-04-28 VMware esx-elxnetcli

  ESX-based 6.0.0 - 0.11.2809209 VMware VMwareCertified 2015-07-21

  ESX-dvfilter-credits-fastpath 6.0.0 - 0.0.2494585 VMware VMwareCertified-2015-04-28

  ESX-tboot 6.0.0 - 0.0.2494585 VMware VMwareCertified-2015-04-28

  6.0.0 - 0.0.2494585 of xserver-ESX VMware VMwareCertified 2015 - 04 - 28

  IMA-qla4xxx 2.02.18 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  IPMI-ipmi-devintf 39, 1 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  IPMI-ipmi-paremeter 39, 1 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  IPMI-ipmi-TR-drv 39, 1 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LPFC 10.2.309.8 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSI-msgpt3 06.255.12.00 - 7vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU-hp-hpsa-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU-lsi-lsi-mr3-plugin 1.0.0 - 2vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  LSU-lsi-lsi-msgpt3-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU lsi megaraid sas plugin 1.0.0 - 2vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  LSU-lsi-mpt2sas-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU-lsi-mptsas-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  Misc-cnic-register 1.78.75.v60.7 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  Misc-pilots 6.0.0 - 0.11.2809209 VMware VMwareCertified 2015-07-21

  NET-bnx2 2.2.4f.v60.10 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-bnx2x 1.78.80.v60.12 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-cnic 1.78.76.v60.13 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-e1000 8.0.3.1 - 5vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-e1000e 2.5.4 - 6vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-enic 2.1.2.38 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-forcedeth 0, 61 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-igb 5.0.5.1.1 - 5vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  NET-IGB 3.7.13.7.14iov - 20vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-mlx4-core 1.9.7.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-mlx4-en 1.9.7.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-nx-nic 5.0.621 - 5vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-tg3 3.131d.v60.4 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-vmxnet3 1.1.3.0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  nmlx4-core 3.0.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  nmlx4-en 3.0.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  nmlx4-rdma 3.0.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  nVMe 1.0e.0.35 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  OHCI-usb-ohci 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  qlnativefc 2.0.12.0 - 5vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  REST 2.0.2.0088 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  Ahci SATA 3, 0 - 21vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  ATA-SATA-piix 2: 12 - 10vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  NV-sata-SATA 3, 5 - 4vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  SATA-sata-promise 2: 12 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SATA-sata-sil24 1, 1 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SATA-sata-sil 2, 3 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SATA-sata-svw 2, 3 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-aacraid 1.1.5.1 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-adp94xx 1.0.8.12 - 6vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-3, 1 - aic79xx 5vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-bnx2fc 1.78.78.v60.8 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-bnx2i 2.78.76.v60.8 - 1vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  SCSI-DNI 1.5.0.45 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-hpsa 6.0.0.44 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-ips 7.12.05 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-megaraid-mbox 2.20.5.1 - 6vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-megaraid2 2.00.4 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-mpt2sas 19.00.00.00 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-mptsas 4.23.01.00 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-mptspi 4.23.01.00 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-qla4xxx 5.01.03.2 - 7vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  UHCI-usb-uhci 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  VMware-esx-dvfilter-maclearn-1, 00 1.00 VMware VMwareCertified 2015-05-12

  xHCI-xhci 1, 0 - 2vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  Tools-light 6.0.0 - 0.11.2809209 VMware VMwareCertified 2015-07-21

  [root@intelserver:~

  Verify that the scsi-megaraid-sas driver is installed before proceeding.

  (2) to disable the lsi_mr3 driver do the following: "esxcli set of module system - enabled = false - module = lsi_mr3 '

  (3) reboot

  After restarting, do: "esxcfg-scsidev - a" to check megaraid_sas driver is assigned to your disk controller.

  I don't know how ESXi decided to prioritize if two or more drivers are applicable to a single hardware device, or if the installation of the new driver LSI process is supposed to disable or remove default lsi_mr3 driver and simply failed to do so.  Also, I don't know what's going to happen when I put on the next patch of ESXi, specially if the lsi_mr3 driver will be once more the priority.  If anyone knows how the driver installation process is supposed to work in this situation, please let me know.  I am so happy that I finally got this problem because the server has been seriously covered with the data store become unaccessable for 5 to 10 seconds every time a VM started or stopped, and the former driver at least once done something bad enough to deceive the controller into thinking that one of the disks has went wrong and began a RAID Resync.

• VDP: Cannot access the data store

  Hello!

  I have a problem.

  Every day I see error for one of my servers in "reports":

  2016-07 - 05T 06: 00:47.971 + error 06:00-[7F2F3FA5E700] [Originator@6876 = transport sub]

  Cannot use hotadd mode to access the FileSrv1/FileSrv1_1.vmdk [Cisco2-datastore]: can't get using this method.

  (Mounting VM using vm-3198 transport hotadd failed: cannot access the data store for one of the drives of the Machine virtual FileSrv1..)

  At the same time, I havn't this error for the other servers.

  "FileSrv1" has not has installed "VMWare tools". After the instalation "VMWare tools" on this server, the problem is resolved.

• Can't do multiple hosts access to the data of the other local host store

  Hello!

  I'm faced with a problem I have no idea how I can solve it. I have a cluster of ESXi 5.1.0 799733 with 3 guests and a shared iSCSI storage. I do vMotion well, as my VM files are stored in the storage. These 3 hosts are managed my vCenter 5.1.0.5300 build 947940.

  Now, I would have a few virtual machines on the local storage of the host cause some performance issues, and so I would like to make Storage vMotion. In addition, Storage vMotion is allowed to my cluster.

  I know that each host needs to access the storage time origin and target to make Storage vMotion. I also know that 5 VMFS is a cluster file system.  Search this documentation [1], it says that I must use in the web client of vSphere (I prefer to use vSphere client), the data store and click the "mount a store of data to some hosts. But there is no icon!

  I also tried clicking 'Add storage' on vSphere Client GUI, by selecting "VMFS", without success.

  Attached to this post is my cluster infrastructure. The DS_LOCAL_ * are storehouses of data space and DS_SAN_ * are SAN datastore.

  Where mess me things up? Help, tip or documentation pointing will be nice.

  Many thanks for any help

  Lucas

  [1] VMware vSphere 5.1

  You can not access local data warehouses of other armies. However, with vSphere VMware 5.1 introduced a new VMotion feature, which allows you to migrate virtual machines without shared storage "(hôte de changement et magasin de données»)." However, this feature is available on the Web Client.

  André

• Machine virtual IOPS / s report, how to display the name of the data store?

  Hi guys

  I am new to the Foglight community, this is a great tool, and I learn a lot.

  Currently I am trying to create a simple table that will show me metric of my VMware environment: Virtual Machine name, Datastore IOPS and data store.

  However I can't find how to include data store name in the table, because it is not a measure of the Virtual Machine. I think I need to expand the scope of my table to include VMware Datastore, but I don't know how to do this.

  -Mark

  

  Check the options available it seems that it can be done with WCF (the frame behind the Foglight dashboards).  We recommend generally customers who plan to build views WCF take adequate training or our PSO people engaged in it.

  In any case I can help show a quick example of how it's done.

  Please try this on a local/test server.

  Go to Configuration > definition >

  

  Make sure that you are in my definition, and click the icon to add a view. then choose from the tables and trees - oriented line table

  

  Give a name to the view, go public and make a portlet/reportlet and apply

  

  Switch to the configuration tab and click the change for the lines and choose a query

  Under query, expand the VMware and scroll down

  

  Until you can select the query for virtual machines

  

  And press the set button.

  Your view should look like this

  

  Now you must select the columns.

  Each column has a value you can edit and there is a button + to add additional columns.

  Lets start with the name of the virtual machine - click on the button to change to your default column and choose the context.

  

  Click on the drop down menu to enter key and choose the current line (virtual vmware machine)

  

  Click on the drop down menu to access path and scroll down until you can select the name and then click on set.

  

  You have created a table that lists the names of all virtual machines.

  You can click on save. and then click test, choose a time and click the result. A new window will open a show the list you of virtual machines.
  From here you can continue to add additional columns, each time choosing the key entry in the current line and the path to the metric/string to display.

  For example, the name of the data store.
  I change the module

  

  Click the configuration tab and click the icon to add a column

  

  For the column value, that I chose defined context once again, the key input is the current row and for the path, I expand the node for the data store

  

  And scroll until I see the Proprietename

  

  If you save and test you will see the result

  

  Keep adding columns and the data you want, notice that you have arrows that allow you to control the order of the columns.

  Note that you can click Show advanced configuration properties

  

  This will give you the opportunity to see the properties of the extra table, such as header - giving you the opportunity to give a more meaningful name (name of the data store, the name of the virtual machine, etc.) to the column header.

  

  You can now go you drag and drop the table edge/report and under my eyes, you will see your new view

  

  Drop it in the main view

  

  I hope this has given you the starting point to build this table.

  As I said, I strongly recommend going through our WCF training if you plan build more custom views or hire software Dell PSO Organisation to help build you views that correspond to your need.

  Best regards

  Golan

• alleged connection to the data store local preventing vmotion

  I have a VM that signals a connection to the local data store on its host, and therefore can't do vMotion elsewhere.  The virtual machine has two virtual drives, which are both on a SAN storage.  The virtual machine has been previously connected to an ISO on the local data store, but it has since been replaced by client device.  He always insists that he's using something on this data store, however.  I've looked through the vmx file and don't see any reference to it.  I also tried to remove the data store, but he claims that the file system is in use.  The hosts have been recently updated to esxi 6.0 U2, and it's the only VM that now seems this behavior.  Any suggestions on what could be the cause?  It is a server important enough in this environment, and be locked into a single host makes me a little anxious.

  Turns out it was because of an old cliché.  If you get an ISO from a data store and take a snapshot, the virtual machine will keep a link to that store of data even after changing the client machine.  As soon as you delete the snapshot, this relationship goes, and access to this database is therefore more a review when searching valid hosts.

• ESXi 5.5 only 4 TB usable for the data store

  Hi all

  Although in vSphere Client 5,46 TB of capacity is visible, I can only use 3.64 TB to a data store.

  Configuration:

  -HP Proliant Microserver N40L

  -HP Smart Array P410/512 MB BBWC, FW 3.66 Controller

  -4 x 2 TB as a Raid5

  HP-ESXi - 5.5.0 - iso - 5.72 A

  I read a lot of articles on > limits of 2 TB of older versions of ESXi or controllers, limitation of 4 TB of c# vSphere Client, old firmware and esxi driver problems, etc.

  But I could not understand the problem.

  The P410 controller shows 5.5 TB:

  ~ # esxcli hpssacli cmd - q "controller connector = 1 see the config.

  Smart Array P410 in slot 1 (sn: PACCRID110510NR)

  Array A (SATA, used space: 0 MB)

  logicaldrive 1 (5.5 TB, RAID 5, OK)

  then 2I:0:5 (port 2I:box 0:bay 5, SATA, 2 TB, OK)

  then 2I:0:6 (port 2I:box 0:bay 6, SATA, 2 TB, OK)

  then 2I:0:7 (port 2I:box 0:bay 7, SATA, 2 TB, OK)

  then 2I:0:8 (port 2I:box 0:bay 8, SATA, 2 TB, OK)

  MS (Vendor ID PMCSIERA, model SRC 8x6G) 250 (WWID: 5001438013D9F37F)

  ESXi obviously knows the same size:

  ~ # Esxcli storage core devices list

  NAA.600508b1001ca5e68adc0bc4bc508d6e

  Full name: Serial Attached SCSI disk HP (naa.600508b1001ca5e68adc0bc4bc508d6e)

  Definable display name: true

     Size: 5723091

  Device type: Direct access

  Multichannel plugin: NMP

  Devfs Path: /vmfs/devices/disks/naa.600508b1001ca5e68adc0bc4bc508d6e

  Vendor: HP

  Model: VOLUME LOGIC

  Review: 3.66

  SCSI level: 5

  (etc.)

  But does that 4 TB:

  ~ # df h

  Size of filesystem used available use % mounted on

  VMFS-5 T 3.6 2.1 T 1. 5 t 58% / vmfs/volumes/mainstorage

  vfat 249.7 M 177.2 M 72.6 M 71% / vmfs/volumes/aeda2aeb-c934ad60-46ce-cb77abdfabaa

  vfat 249.7 M 175.9 M 73.9 M 70% / vmfs/volumes/c8ace7e9-a96a5914-16 d 4-a697ad4634d9

  vfat 285.8 M 191.4 M 94.4 M 67% / vmfs/volumes/55d7af6e-a25f7c97-c3ec-6805ca0de93c

  I tried to increase the size of the data store, last used area was 11720890367 and last sector was 11720890510 which doesn't really seem to translate into an increase of 1.8 to.

  Thanks for your help.

  DC

  Your output, it shows that there are two partitions vmfs

  3 10229760 3907029134 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

  4 3907031040 11720890367 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

  A partition with 1.8 to and another with 3.8 to.   That's the reason why you see only 3.8 to

  I don't know why the 1.8 to vmfs volume is not list anywhere (which does not appear in the list of file system of storage of esxcli also). Do you have any before partition created manually. If you think that if there is no data in this 1.8 to vmfs partition you can remove it by using the partedutil command and then use this free space to extend the existing 3.8 to. But do not forget before you delete the partitiaon

• local storage in the data store

  I have 4 ESXi 5.5 cluster nodes (host1, 2... 5) + 3par storage, I noticed that the local drive of host2 is detected as a data store.

  When I create a VM and I choose the data store, I can see all data related to my on3par LUN stores but it seems this drive local host2 too!

  I would like to remove it! Can you offer me please?

  You must hide hide this data store using permissions, you must run the following procedure: Open-> inventory-> warehouses vSphere-> select the select data-> permissions VMFS store-> click the user or group in the list and set them to 'No access' - are not propagated.

  Once achieve you its judgment showing everywhere.

• Script in time of latency list vm e/s and the data store the virtual machine is on

  Hello.  We have a vsphere 5.0 environment and we live a latency of IO heavy.  I'm looking for powercli script will get the latency of i/o for each virtual machine and get the data store name, to what it is now.  We will access our storage on optical fiber.  I'm trying to get a good overview of the latency of IO in a nice view in a csv file.  I found what could be a good basis to https://communities.vmware.com/thread/304827?start=0 & tstart = 0 , but I'm not sure how to get the name of the data store in the table and I think that it is written to the nfs in any case storage.  Thanks in advance for any info\advice!

  Try the next version, it includes the average latency time read/write for the virtual machine and PAHO are / s average for the virtual machine.

  Since the CSV has a row for each data store, the values for the virtual machine are repeated.

  I also added the host name

  $vmName = "VM*"
  
  $stat = "datastore.totalReadLatency.average","datastore.totalWriteLatency.average",  "datastore.numberReadAveraged.average","datastore.numberWriteAveraged.average"$entity = Get-VM -Name $vmName$start = (Get-Date).AddHours(-1)
  
  $dsTab = @{}Get-Datastore | Where {$_.Type -eq "VMFS"} | %{  $key = $_.ExtensionData.Info.Vmfs.Uuid  if(!$dsTab.ContainsKey($key)){    $dsTab.Add($key,$_.Name)  }  else{    "Datastore $($_.Name) with UUID $key already in hash table"  }}
  
  Get-Stat -Entity $entity -Stat $stat -Start $start |Group-Object -Property {$_.Entity.Name} | %{  $vmName = $_.Values[0]  $VMReadLatency = $_.Group |    where {$_.MetricId -eq "datastore.totalReadLatency.average"} |    Measure-Object -Property Value -Average |    Select -ExpandProperty Average  $VMWriteLatency = $_.Group |    where {$_.MetricId -eq "datastore.totalWriteLatency.average"} |    Measure-Object -Property Value -Average |    Select -ExpandProperty Average  $VMReadIOPSAverage = $_.Group |    where {$_.MetricId -eq "datastore.numberReadAveraged.average"} |    Measure-Object -Property Value -Average |    Select -ExpandProperty Average  $VMWriteIOPSAverage = $_.Group |    where {$_.MetricId -eq "datastore.numberWriteAveraged.average"} |    Measure-Object -Property Value -Average |    Select -ExpandProperty Average  $_.Group | Group-Object -Property Instance | %{    New-Object PSObject -Property @{      VM = $vmName      Host = $_.Group[0].Entity.Host.Name      Datastore = $dsTab[$($_.Values[0])]      Start = $start      DSReadLatencyAvg = [math]::Round(($_.Group |           where {$_.MetricId -eq "datastore.totalReadLatency.average"} |          Measure-Object -Property Value -Average |          Select -ExpandProperty Average),2)      DSWriteLatencyAvg = [math]::Round(($_.Group |           where {$_.MetricId -eq "datastore.totalWriteLatency.average"} |          Measure-Object -Property Value -Average |          Select -ExpandProperty Average),2)      VMReadLatencyAvg = [math]::Round($VMReadLatency,2)      VMWriteLatencyAvg = [math]::Round($VMWriteLatency,2)      VMReadIOPSAvg = [math]::Round($VMReadIOPSAverage,2)      VMWriteIOPSAvg = [math]::Round($VMWriteIOPSAverage,2)    }  }} | Export-Csv c:\report.csv -NoTypeInformation -UseCulture
  

• How can I add an ISO to the data store?

  How can I add an ISO to the data store?  It doesn't let me access the ISO.

  of the error, it seems that your iso is bad.

  hitting a md5 checksum or re-download the iso

• Add the new hard drive into the data store in ESXi 4.1

  Hi all

  I got ESX 4.1 installed on the Dell server, and I have 3 virtual machines on a data store.

  I added a new 500 GB scsi hard drive to the server,

  and I need to add it to the datasore or create a new...

  How can I see this new hard drive? and add it to the data store?

  Waiting for your help.

  concerning

  Abrams

  Oracle system engineer

  Abrams,

  That's all I can help you.  These instructions are based on the Perc 5 / i controller, which I think you have on our system.  You have not specified the server so I just assumed that this is so.

  1. unscrew the hot spare that you just made.  Follow this link from Dell.
  http://support.Dell.com/support/eDOCS/storage/RAID/PERC5/en/UG/HTML/chapterh.htm#wp1061343

  2 follow the link for the installation of virtual disks - http://support.dell.com/support/edocs/storage/RAID/PERC5/en/UG/HTML/chapterh.htm#wp1069357

  This link has three steps to void, skip the step on "spare parts of designate hot."
  a. create the virtual disks and select virtual disk options.   -Online steps to create another disk group and add the new disk to the disk group.
  (b) designate the drives hot spares (optional). =>, YOU CAN SKIP THIS STEP
  c. initialize virtual disks. -online must do.  just do not initialize the incorrect disk.

  After the step #2 c, you should be able to access the drive in ESXi or command-line (list of nmp esxcli devices).

  And no, you cannot add this manaully until do you step #2 above which is to define the disk group, creating virtual disks and initialize the virtual disk.

  Good luck.

• Recommended minimum on the data store when free disk space you use connection vRanger 5

  I was wondering if anyone can tell me what the recommendation is on the left of free space on a data store. I use 5 vRanger connection to back up my VM to another physical server. As such, I will not take snapshots 'manual '. I'm not sure if vRanger connection, running on a separate server, creates additional files on the data store.

  I've read a few threads on this site and some are advocating to let free, 20 to 25%, while that of others, offer 10% left free may be sufficient. Is there an official number for this or if anyone can share valuable experince?

  Welcome to the community,

  I generally recommend to have about 20% of free space on each data store. However, this depends on the activity/writes to disk during backup. vRanger connection - as well as any other backup software - create a snapshot, back up the virtual machine and then remove / commit the snapshot again. This is necessary in order to access the virtual disk files. Usually the backups are made during hours, so snapshots should not grow too much. However, you must also take into account the fact that in the case of a mistake - if the snapshot cannot be deleted - it will grow until it is deleted manually.

  André

• Combining the VM with files in the data store

  I apologize for the very basic question.

  I have a few ESXi servers and I need to associate each VM with the related directory inside the data store and each direxctory within the data with the associated directory store.

  With the command:

  SE connect-VIServer-Server 192.168.1.1 - user root - < password >

  I connect with the server.

  With the command

  Get - vm

  I get a list of all VM with the State and the amount of memory, the number of vCPU

  • How can I get path for each computer listed virtual, to the related .vmx file?
    
  • How to browse the data store, the list of the .vmx file and for each .vmx file, get the name of the associated virtual machine?
    
  • What manual download to find the emanations of the arguments of the command get-vm and qualifying?
    

  Concerning

  Marius

  The Get - VM by default displays a selection of properties.

  You can ask all the properties

  Get - VM | Select *.

  or some specific

  Get - VM | Select name, Description

  You can even access the real object of the SDK VirtualMachine

  Get - VM | Select Name,@{N="VMX; E={$_. Extensiondata.Config.Files.VmPathName}}

  PowerCLI comes with a data store provider.

  It is documented in the vSphere PowerCLI Admin Guide, which is installed with PowerCLI.

  With the provider, you can list the files .vmx on data warehouses.

  To find the name of the corresponding client, you will need to retrieve the DisplayName of the .vmx file field.

• Problems with the data store when installting ESXi USB

  I had problems getting free ESXi reliable running.  I am able to install a flash drive fine and initially everything works and I am able to create virtual machines.  Upon the first connection to vSphere, told me that there is no data store, so I create one on my controller LSI 400 GB RAID1 8308elp without problem.  However, once I reboot the server ESXi I lose the data store.  When I check my warehouses under Configuration it is listed.  At this point, if I try to create the data store, yet once I get "Error during the configuration of the host".  I read about using fdisk from the console when people have had this problem but there is no access console in the free version.  Is that what I can do to work around this problem?

  Right in the HCL... SAS/SATA-RAID of the lists for older versions, SCSI for the current version... Search within i/o devices for "LSI 8308elp '...

  VMware VCP4

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

• Not be able to reverse engineer the data store by using technology such as postgres

  Hello
  
  When I am creating a data store for postgres using reverse engineering process he gives error jdbc.
  
  Then we created the data store manually by using the same schema logic and used in the interface and it was working fine.
  It is not possible to manually create all the data store for postgres we need in my project.
  
  Error details:
  ODI-20131: unable to retrieve a list of tables
  oracle.odi.core.exception.OdiRuntimeException: java.lang.IllegalArgumentException: could not load driver JDBC [org.postgresql.Driver] class
  at oracle.odi.core.datasource.provider.AbstractDataSourceProvider.configure(AbstractDataSourceProvider.java:107)
  to oracle.odi.core.DataSourceManager$ LoginTimeoutDataSourceProviderProxy.configure (DataSourceManager.java:303)
  at oracle.odi.core.DataSourceManager.createAndConfigureDataSourceProvider(DataSourceManager.java:226)
  to oracle.odi.core.DataSourceManager.access$ 0 (DataSourceManager.java:206)
  to oracle.odi.core.DataSourceManager$ 1.create(DataSourceManager.java:76)
  at org.springframework.util.CachingMapDecorator.get(CachingMapDecorator.java:152)

  Your postgresqldriver is missing (in the folder userlib/agent)-able to load JDBC driver class.

  Similar problem for SQL Server - unable to connect to SQL Server 2005 using ODI 11 g