For NFS Datastore vSphere alarms

Similar Questions

• Size max for NFS and VMFS (iscsi, FCP) datastore on vSphere 4.1 and 5.0

  Hello

  What is the maximum size for NFS and VMFS (iscsi and FCP) data created on vSphere 4.1, 5.0, and 4.0 stores?

  Thank you

  Tony

  Hi Tony,.

  You should find the answers in the various maxima of Configuration documents:

  • http://www.VMware.com/PDF/vsphere5/R50/vSphere-50-configuration-maximums.PDF
  • http://www.VMware.com/PDF/vSphere4/R41/vsp_41_config_max.PDF
  • http://www.VMware.com/PDF/vSphere4/R40/vsp_40_config_max.PDF

  Good luck.

  Concerning

  Franck

• What "unmapped user access" for NFS share in Windows Server 2008 R2?

  In the beginning, I followed this Youtube video to set up an NFS share in Windows Server 2008 R2:

  https://www.YouTube.com/watch?v=BQ8Q_vsiksg

  Please note that the default option to allow to access Unix unmapped user is not changed (to about 1 min 57 sec).

  Then I found another article at http://www.vmwarearena.com/2012/07/create-nfs-datastore-for-esx-in-windows.html

  But in this article, I like to select allow anonymous access (instead of allow access Unix unmapped user).

  So who is correct?  Or both are correct (which means that this 'unmapped user access' is not serious)?

  And why should we have to allow root access (in the NFS share permissions dialog box)?  What a security risk?

  Thanks in advance.

  Have you tried to run through the steps taken from the blog of VMware?

  How to enable NFS on Windows 2008 and currently at ESX | Insider - Articles from VMware VMware support

  Also, there are 3 KB articles to know in case of potential problems

  1. http://kb.vmware.com/kb/1004490

  2. http://kb.vmware.com/kb/1003967

  3. http://technet.microsoft.com/en-us/library/cc753302 (WS.10) .aspx

  Noting in particular this section

  Share the folder of Windows for NFS

  To share the folder of Windows for NFS:

  1. Right click on the local folder you want to share via NFS.
  2. Click NFS share.
  3. Type the name for the share. For example, NFS-VMFS01.
  4. Delete to allow anonymous access.
  5. Click on permissions.
  6. Change the type of access in reading + writing and select allow root Access.

• Network for NFS

  Hello

  I have infrastructure as follows;

  2 welcome each containing 6 1Gig speed NIC each.

  A NAS storage with 4 NIC

  Two L2 Switches (managed HP).

  Planning to run it by the best recommendations and requirements, so that there should not be a SPOF any level.

  So keeping this in mind, we have designed to use ports on each server as follows:

  2 for the NFS storage, 2 for Production management and 2 others for vMotion on each server.

  A cable from each port configured for respective roles goes uplink switch1 and switch2, so if a switch goes down we still have the other switch support.

  Separated VLAN is configured by the switch to different types of traffic.

  My question as below;

  Should I team two ports on each vSS.If so that what should be the parameters for NETWORK adapters for the production, storage, and vMotion network grouping (keeping in mind cables going to switch uplink separated).

  Should I keep adapter in active-standby or active-active mode.

  I didn't think any specific settings to link pass that one cable by a single port is to go there and I don't have the choice of the channel of the ether or LACP.

  In addition, vmware license is essential and having therefore no possibility to use dynamic switches.

  Consider using 5.5.0.

  Also do you propose to use frames as well in the present.

  Kind regards

  Sushil

  Hello

  I suggest always you put management and vMotion on the same set of natachasery management and workloads. It makes no difference where they are subnet a perspective.  I also suggest to read the following:

  • The great debate VSwitch (old writings but still VERY there, let not the age fool you on this one)
  • VMware Virtual networking concepts
  • Networking for administrators of virtualization

  Who should you get.

  natachasery have no IP address in a vSphere environment, they act as a link between a physical and virtual switch. According to the way which you the trunk your VLAN Trunk ends pSwitch (external switch tagging) or the virtual switch (switch virtual tagging). Most people master their VLAN to the virtual switch.

  You want something like the following:

  pSwitch <->pNIC0 <->[ <->Portgroup vSwitch0] <->management (subnet1)

  pSwitch <->pNIC1 <->[ <->Portgroup vSwitch0] <->vMotion (subnet2)

  When switching between pNIC0 and pNIC1 management and vMotion end up on the same bear but when normally run that they remain separated. It is the recommended method. In this case you would master the VLAN to the vSwitch. I know some people who just do not use VLANs, but who use only separate subnets and it works as well.

  pSwitch <->pNIC2/pNIC3 <-> <->Portgroup vSwitch1 (s) <->of workloads (subnet1)

  If you use VLANs (except for vMotion) you're trunking to vSwitch1 (virtual switch tagging). If subnet1 is on the same vSwitch and the trunk is correct via pSwitch ports so he can talk to management on vSwitch0 effortlessly. Switches know how to route traffic to VLAN.

  pSwitch <->pNIC4/pNIC5 <->vSwitch2 <->Portgroup <->NFS (subnet3)

  Here we link pNIC4 and pNIC5 together or use them as a pair of failover for NFS on its own subnet / VLAN itself. This VLAN can end the pSwitch if you wish or terminate once again to the vSwitch.

  In this configuration you have 3 VLAN and 3 subnets (subnets use by VLAN are also recommended)... for example:

  VLAN100-> subnet1-> workload management

  VLAN200->-> vMOtion subnet2

  VLAN300->-> NFS subnet3

  Let the pSwitches any 'movement' of traffic for each VLAN. You need only a routing device if you want TO cross borders VLAN and there is absolutely no need to do it in this configuration.

  Best regards
  Edward L. Haletky
  VMware communities user moderator, VMware vExpert 2009, 2010, 2011,2012,2013,2014

  Author of the books ' VMWare ESX and ESXi in the business: Planning Server Virtualization Deployment, Copyright 2011 Pearson Education. ' Of VMware VSphere and Virtual Infrastructure Security: securing the virtual environment ', Copyright 2009 Pearson Education.

  Virtualization and Cloud Security Analyst: The Practice of virtualization, LLC - vSphere Upgrade Saga - virtualization security Table round Podcast

• Windows do not install ISO in the NFS datastore

  Hi all

  I searched this forum for a few days and tried to suggestions from different positions without success. I recently installed ESXi 5.1 update 1. I have setup a NFS datastore on the same computer by using a USB external hard drive. I was able to install RHEL6 using an iso from the NFS data store. The problem is that I can't install Windows by using an iso of Windows 7. Whenever the virtual computer is booted, it aims to achieve crashes and boot TFTP. No iso standard is detected. I tried the following:

  1. guaranteed 'Connected' and 'Connect at Power On' options for CD/DVD are verified. However, I have noticed that when the virtual machine starts, the 'Connected' for Windows option becomes not controlled. This is not the case for the Linux VM.

  2. change the boot order in BIOS to the first boot from CD/DVD.

  3. uncontrolled ' connect at power on "for network adapters.

  Even after these changes, VM trying to do a start-up network and TFTP.

  The next thing I did:

  4 network cards removed from the BIOS (by changing configuration).

  For the moment, VM does not network boot attempt, but complains that the operating system was not detected.

  Few details on the NFS datastore:

  1. 1 TB external USB with 2 Configuration of partitions ext4 as an NFS share to the RHEL6 server on the same machine.

  2. NFS configured correctly because I can install from an iso RHEL6 very well.

  Am I missing something? Nothing wrong with iso of Windows. I used it elsewhere. Also tried a different iso Windows without success. Help, please. Thanks in advance for your time.

  Kind regards.

  As the ISO for the operating system files are big and sometimes take a considerable amount of clusters on the hard drive make a control office (or a scan of the drive) can fix corrupt ISO file. and to make sure that your ISO is not corrupted try to open it with Winrar and extract a file from it.

  Yours,
  Mar Vista

• slow writes - nfs datastore

  Greetings.

  I note that some write throughput problems I see with a based NFS datastore. Seems I'm not the only one who is seeing this, but so far have given little information in making it better.

  Try the update of ESXi V4 1 on a Poweredge T110 with 4 GB of memory, xeon X 3440 CPU and 1 250 GB sata drive.

  The NFS is based datastore served a machine of OpenSUSE 11.2 on a network of 1000Mb and speed and duplex has been verified to be correctly set on both machines.

  Initially I converted a server image OpenSUSE 11.2 VMware VMware ESXi server (12 GB) in a based NFS data store. It worked, but was incredibly slow, medium flow 2.7 MB/sec.

  Once, I found 3 MB/s writing was everything that I have the NFS datastore using jj. I tried both leave within the virtual machine and also in the ESXi console to the same store location.

  Performance of network using iperf, shows ~940mb/s between the virtual machine and the NFS server so when drives are out of the way, the net is doing well.

  I ended up changing the following advanced settings to see if it is any kind of problem memory buffer;

  NFS.maxvolumes to 32

  NET.tcpheapsize to 32

  NET.tcpheapmax to 128

  Which seem to help, access write from the virtual machine to the NFS data store went from 3 MB/s to 11 MB/s - 13 MB/s. So, there is certainly some slowdowns self-imposed via the default settings are defined.

  Tried to mount the NFS datastore even directory directly as / mnt in the virtual machine hosted and low and write to/mnt watch throughput ~ 25 Mbps. do the same exact command to another linux only box on the same network that I see about the same rate with the stand-alone server see about 2 MB/s more so no problem there.

  I suspect that there may be other elements in which the ESXi NFS based datastore is 50% less efficient than straight NFS. Have other any golden treats to try to obtain the ESXi storage NFS write speed up to something similar to what can be done with native NFS mounted in the virtual machine?

  TIA

  Check the mounting options on underlying partition, for example by the file system,

  -ext3 - rw, async, noatime

  -xfs - rw, noatime, nodiratime, logbufs = 8

  -reiserfs - rw, noatime, data = writeback

  Then export options use (rw, no_root_squash, async, no_subtree_check)

  Check that the IO Scheduler is correctly selected based on underlying hardware (use a rewrite if material noop).

  Increase the NFS threads (if 128) and Windows TCP to 256K.

  Finally ensure comments partitions are 4K aligned (this should not affect sequential performance well).

  I worked on a few notes on NFS, which cover all of this (not complete yet): http://blog.peacon.co.uk/wiki/Creating_an_NFS_Server_on_Debian

  HTH

  http://blog.peacon.co.UK

  Please give points for any helpful answer.

• Poor ESXi 4 NFS Datastore Performance with various NAS systems

  Hello!

  In testing, I found that I get between a half and a quarter of the e/s inside a guest performance when ESXi 4 systems connect to the using NFS data store if the clients connect to the exact same NFS share.  However, I don't see this effect if the data store using iSCSI or local storage.  This has been reproduced with different systems running ESXi 4 and NAS systems.

  My test is very simple.  I created naked CentOS 5.4 minimum installation (completely updated 07/04/2010) with VMware Tools loaded and the creation time of a file of 256 MB using jj.  I create the file on the root (a VMDK stored in different data warehouses) partition or a directory of the NAS mounted via NFS, directly in the comments

  My crucial test configuration consists of a single test PC (Intel 3.0 GHz Core 2 Duo E8400 CPU with a single Intel 82567LM-3 Gigabit NC and 4 GB RAM) running ESXi 4 connected to a printer HP Procurve 1810 - 24 G, which is connected to a VIA EPIA M700 NAS system running OpenFiler 2.3 with two 1.5 to 7200 tr / MIN SATA disks configured in front of software RAID 1 and dual Gigabit Ethernet NIC.  However, I have reproduced it with different ESXi PC and NAS systems.

  This is a release of one of the tests.  In this case, the VMDK is a store of data stored on the NAS via NFS:

  -

  ---

  root@iridium /sync #; Sync; Sync; time {dd if = / dev/zero of = bs = 1 M count = test.txt 256 sync; sync; sync ;}}
  2560 records in
  2560 records out
  268435456 bytes (268 MB) copied, 0,524939 seconds, 511 MB/s
  Real 0m38.660s
  user 0m0.000s
  sys 0m0.566s
  root@iridium /# mount/mnt 172.28.19.16:/mnt/InternalRAID1/shares/VirtualMachines
  root@iridium /# cd/mnt
  synchronization of the # mnt root@iridium; Sync; Sync; time {dd if = / dev/zero of = bs = 1 M count = test.txt 256 sync; sync; sync ;}}
  2560 records in
  2560 records out
  268435456 bytes (268 MB) copied, 8,69747 seconds, 30.9 MB/s
  Real 0m9.060s
  user 0m0.001s
  sys 0m0.659s
  mnt root@iridium#.

  -

  ---

  The first dd is a VMDK stored in a connected via NFS data store.  The dd ends almost immediately, but the synchronization takes nearly 40 seconds!  It's less than 7 MB per second transfer rate: very slow.  Then I get the exact same NFS share that ESXi is used to store data directly in the comments and repeat the DD.  As you can see, the SD is longer and the synchronization takes no real time (as befits a NFS share with active sync), and the whole process takes less than 10 seconds: this is four times faster!

  I don't see these results on data warehouses mounted via NFS.  For example, here is a test on the guest even running from a mounted via iSCSI data store (using the exact same SIN):

  -

  ---

  root@iridium /sync #; Sync; Sync; time {dd if = / dev/zero of = bs = 1 M count = test.txt 256 sync; sync; sync ;}}
  2560 records in
  2560 records out
  268435456 bytes (268 MB) copied, 1,6913 seconds, 159 MB/s
  Real 0m7.745s
  user 0m0.000s
  sys 0m1.043s

  
  root@iridium /# mount/mnt 172.28.19.16:/mnt/InternalRAID1/shares/VirtualMachines
  root@iridium /# cd/mnt
  synchronization of the # mnt root@iridium; Sync; Sync; time {dd if = / dev/zero of = bs = 1 M count = test.txt 256 sync; sync; sync ;}}
  2560 records in
  2560 records out
  268435456 bytes (268 MB) copied, 8,66534 seconds, 31.0 MB/s
  Real 0m9.081s
  user 0m0.001s
  sys 0m0.794s
  mnt root@iridium#.

  -

  ---

  And the same comments linking internal SATA drive of the PC ESXi:

  -

  ---

  root@iridium /sync #; Sync; Sync; time {dd if = / dev/zero of = bs = 1 M count = test.txt 256 sync; sync; sync ;}}
  2560 records in
  2560 records out
  268435456 bytes (268 MB) copied, 6,77451 seconds, 39.6 Mbps
  Real 0m7.631s
  user 0m0.002s
  sys 0m0.751s
  root@iridium /# mount/mnt 172.28.19.16:/mnt/InternalRAID1/shares/VirtualMachines
  root@iridium /# cd/mnt
  synchronization of the # mnt root@iridium; Sync; Sync; time {dd if = / dev/zero of = bs = 1 M count = test.txt 256 sync; sync; sync ;}}
  2560 records in
  2560 records out
  268435456 bytes (268 MB) copied, 8,90374 seconds, 30.1 MB/s
  Real 0m9.208s
  user 0m0.001s
  sys 0m0.329s
  mnt root@iridium#.

  -

  ---

  As you can see, the performance of NFS direct comments for each of the three are very consistent.  ISCSI and the performance of the store local data disk are both a bit better than that - as I expect.  But the mounted via NFS data store gets only a fraction of the perfomance of the any of them.  Obviously, something is wrong.

  I was able to reproduce this effect with an Iomega Ix4 - 200 d as well.  The difference is not as dramatic, butalways important and consistent.  Here is a test of a guest of CentOS using a VMDK stored in a data store provided by an Ix4 - 200 d via NFS:-.

  root@palladium /sync #; Sync; Sync; time {dd if = / dev/zero of = bs = 1 M count = test.txt 256 sync; sync; sync ;}}
  2560 records in
  2560 records out
  268435456 bytes (268 MB) copied, 11,1253 seconds, 24.1 Mbps
  Real 0m18.350s
  user 0m0.006s
  sys 0m2.687s
  root@palladium /# mount/mnt 172.20.19.1:/nfs/VirtualMachines
  root@palladium /# cd/mnt
  synchronization of the # mnt root@Palladium; Sync; Sync; time {dd if = / dev/zero of = bs = 1 M count = test.txt 256 sync; sync; sync ;}}
  2560 records in
  2560 records out
  268435456 bytes (268 MB) copied, 9,91849 seconds, 27.1 MB/s
  Real 0m10.088s
  user 0m0.002s
  sys 0m2.147s root@palladium mnt-#.

  -

  ---

  Once more, the direct NFS mount gives very consistent results.  But using the diskette provided by ESXi on a mounted NFS datastore gives still worse results.  They are not as terrible as OpenFiler test results, but they are constantly between 60% and 100% longer.

  Why is this?  What I've read, NFS performace is supposed to be within a few percent of the iSCSI performance, and yet I see between 60% and 400% worse performance.  And this isn't a case of the SIN is not able to provide correct NFS performance.  When I connect to the NAS via NFS directly inside the guest, I see much better than when ESXi connects to the same NAS (the same proportion!) via NFS.

  The configuration of ESXi (network and network cards) is 100% stock.  There is no VLAN in place, etc., and ESXi system has only one

  Single Gigabit adapter.  It is certainly not optimal, but it doesn't seem to me to be able to explain why a virtualized guest is able to get a lot better performance NFS as ESXi itself to the same NAS.  After all, they both use the same exact suboptimal network configuration...

  Thank you very much for your help.  I would be grateful any idea or advice, you might be able to give me.

  Hi all

  It is very definitely a performance O_Sync problem. It is well known that NFS VMware shops still use O_Sync for writes little matter what share put for a default value. VMware uses a custom file locking system so you really can't compare it to a normal NFS share connection to a different NFS client.

  I have validated that the performance will be good if you have an SSD cache or storage target with enough reliable battery backup.

  http://blog.laspina.ca/ubiquitous/running-ZFS-over-NFS-as-a-VMware-store

  Kind regards

  Mike

  vExpert 2009

• When I use the Client for NFS provided by Windows 7, I'm unable to connect. The "mount \\ip address\share Z:" command fails with the error code "the path not found network".

  Identification of customer's Windows 7 NFS UID GID information

  I am trying to connect to the Windows 7 Client NFS on a server running on a computer (VxWorks) NFS.  I am able to properly connect Client NFS software by a 3rd party on the NFS server.  However, when I use the Client for NFS provided by Windows 7, I am unable to connect.  The \\ip address\share Z: mount"command fails with the error code"the path not found network ".  I can't do a ping of the computer running the NFS server.

  The NFS Client operating system: Windows 7 Ultimate, 64-bit

  Data captured by Wireshark

  MOUNT V1 EXPORT call 3rd party client
  Identification information Flavor: AUTH_UNIX (1)
  Length: 32
  Stamp: 0xc7065970

  Machine name: PC
  UID: 1000
  GID: 1000

  MOUNT V1 EXPORT appeal of the NFS client
  Identification information Flavor: AUTH_NULL (0)
  Length: 0

  It seems that the credentials of NFS Client are not correct.  How can I change the flavor of AUTH_UNIX and the UID and GID to 1000?

  Hello VDAEMP,

  As Eddie and Sudarshan has said, the Microsoft Answers community focuses on issues and problems related to the consumer environment. Please join the public IT pro TechNet forums below:
  TechNet - Windows Server
   
  Thank you

• tare on server for NFS mangles of symbolic links

  Hello

  I'm running into a problem where symbolic links are distorted when calibration files that reside on the Server 2003 and Server 2008 running server for NFS, serving to Redhat Linux 4.6, 5.3, 5.7 and machines Ubuntu 11.10. Note that the test below, region of origin of the user is mounted on a server for NFS 2008 R2 installation.  The question is not if I create a tar with files on the local computer. Absolute links are unaffected, related links.  Help solve this for links are greatly appreciated.

  [Dd ~/TEST]$ if = OneGig.txt of = / dev/zero bs = 1024 count = 1000]
  [~/TEST]$ ln-s OneGig.txt test
  [~/TEST]$ ln-s /home/USER/TEST/OneGig.txt test2

  [~/TEST]$ ls-l
  Total 1000
  -rw - r - r - 1 1024000 24 August at 14:11 OneGig.txt
  lrwxrwxrwx 1 0 24 August to 14:12 test-> OneGig.txt
  lrwxrwxrwx 1 0 24 August to 14:12 test2-> /home/USER/TEST/OneGig.txt

  [~/TEST]$ cd...
  [~] $ tar cvf TEST.tar TEST.
  TEST /.
  TEST/OneGig.txt
  TEST/test
  TEST/test2
  [~] $ tar tvf TEST.tar
  drwxr-xr-x 0 2012-08-24 14:12:55 TEST.
  -rw - r - r - 1024000 2012-08-24 14:11:29 TEST/OneGig.txt
  lrwxrwxrwx 0 2012-08-24 14:12:46 TEST / test-> O
  lrwxrwxrwx 0 2012-08-24 14:12:55 TEST / test2-> /home/USER/TEST/OneGig.txt

  This forum is for users of the home computer having problems with files in the Windows consumer editions.  Help server, check with the people in the TechNet forums, this is where the guys TI and server gurus hang out.

• Is it possible create Oracle RAC on NFS datastore?

  Hello

  Is it possible create Oracle RAC on NFS datastore?   With the VMFS data store, we use VMDK files as the Oracle RAC shared virtual disks with the Comptrollership and multi-writer SCSI Paravirtual, what about the NFS datastore? is the controller SCSI Paravirtual and writer multi function supported on the NFS datastore?

  Unless I'm missing something, this is not supported on NFS.

• NFS datastore = &gt; no host not connected, impossible to remove

  Hello

  I have a NFS datastore (it was an ISO repository), I need to delete.   So I deleted all records from this share

  My problem is I disassembled it all hosts and the data store is still visible in my inventory and I am unable to remove it.

  When I try "Datastore Mounte to... additional host", the Wizard run in an endless loop and does not load the list of hosts.

  On my hosts, the NFS share is not visible. So nothing stuck because of a file in use.

  Have you already encountered this problem?

  Sorry found the culpit... instant on the virtual machines (with mapped CD-ROM).

• Customer error supported download the files for the client vSphere 5.0

  Hi all

  
  

  I am new to VMware and learning ESXi 5.0. I built my 5.0 ESXi host and then downloaded the 5.5 vSphere client. Given that I have only one host; client vSphere 5.5 can handle that. I installed the client and enter the IP address of the host with root/configured password management. He gave the certificate WARNING said to download the files from customer support. He has always exceeded with error as you can see it.

  
  

  I'm under client on a LAN connection high speed, I even changed the connections to see if access to the internet the problem. It is more simple home, 1 host installation, a windows 7 computer (with vSphere client installed), both connected to my DSL modem/router. The client support files won't download anything. Help please!

  
  

  

  Sorry my bad vSphere Client 5.5 support ESXi 5.0 but Client vSphere 5.0 ESXi host does not support the 5.5U1 (Build 1618071)

  Check the compatibility matrix for more information vSphere Client

  

  VMware product interoperability matrices

• Cannot remove/remove NFS datastore because its use, but is not

  I am trying to remove an old NFS data store, but I get an error message saying that it is in use. I find the virtual machine that he believes is used, stepped through all the parameters of the virtual machine and there is nothing pointing to this NFS datastore. I also tried to remove the store of data from the command line using 'esxcfg-nas - d < NFS_Datastore_Name >. That returned an error saying "unknown, cannot delete file system. Even 30 minutes before I was access and moving data out of this data to another ESX host store. I don't know what else to try. Can someone please help?

  It also still shows up on top of the virtual machine as used storage an idle...

  The virtual machine has an active overview that was created while the virtual machine was on the NFS datastore?

  André

• Moving to VM - NFS Datastore - no vmotion - invalid

  Hey people,

  Having a problem here to move a virtual machine from one ESX host to another (with VC).  First of all, let me tell you that I don't have vmotion (working on fixing that), but I have no shared storage (NFS datastore).

  If the virtual machine is hosted by esx1 on this NFS data store.  I stop the virtual machine and remove it from the inventory.  Then, I go to esx2 and browse the data store.  Find the vmx file and add to the inventory.  Then, the virtual machine appears in the inventory, but is grayed out with (invalid) beside him.

  I'm sure I could add a new virtual machine and use the existing vmdk files like discs, but I would rather simply add to the inventory with the existing configuration.

  Is this possible?

  Thank you very much

  Grant

  -

  ---

  Without vmotion you should always be able to migrate cold the VM - Power Down the VM - right click on the virtual machine name, select migrates - select another ESX host - you can change the storage or leave it where it is at.

  This will allow to get cold migrate the virtual computer with the ing to remove and re add to the inventory of VC.

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Configure alarms for VMware Datastore latency in version FREE Foglight!

  Hi all

  I downloaded the version free foglight and that I imported the FVO in my test harness. I want that when a data store has over 50ms latency so I should launch an alert.

  I can't see the alarms on the console free foglight.

  Can you please how can I do to achieve the same thing.

  Thank you

  Vaibhav

  Hi vaibhav,

  The free version does not include a rule to check latency of data store. I checked with development and looks like a new rule has been added to the Foglight for virtualization Enterprise Edition 7.2 (to be released in the following months). The new rule is called: VMW Datastore total latency.

  For the moment, in my view, there is a latency of data store rule included in one of the established community of cartridges. These cartridges are not created by Dell and are not supported. Take a look at it and see if it meets your request.

  http://communities.quest.com/docs/doc-12956#comment-6001

  Note: If your Foglight does not have the ability to install cartridges, chances are that you are running the Standard Edition version. If you have problems, please indicate the full version number. You should find it in the topic of the article.

  Concerning

  Gaston.