Reading Time: 3 minutes

RVtools is a great tools to inventory a virtual infrastructure based on VMware vSphere, with or without vCenter Server (works great also on standalone ESXi hosts).

RVTools supports ESX Server 3.5, VirtualCenter 2.5, ESX Server 3i, ESX Server 4i, VirtualCenter 4.x, ESX 4.x, VirtualCenter 5.0, VirtualCenter Appliance, ESX 5.0, VirtualCenter 5.5, ESX 5.5, VirtualCenter 6.0, ESX 6.0, VirtualCenter 6.5 and ESX 6.5, so all you can have (also legacy versions) in a datacenter. And it’s totally free.

Latest version is 3.9.5 (April, 2017).

One of the most powerful feature of RVTools is the vHealth tab, that perform basics check-lists on the status of your VMs:

There are 19 possible “Health Check” messages:

  1. VM has a CDROM device connected!
  2. VM has a Floppy device connected!
  3. VM has an active snapshot!
  4. VMware tools are out of date, not running or not installed!
  5. On disk xx is yy% disk space available! The threshold value is zz%
  6. On datastore xx is yy% disk space available! The threshold value is zz%
  7. There are xx virtal CPUs active per core on this host. The threshold value is zz
  8. There are xx VMs active on this datastore. The threshold value is zz
  9. Possible a zombie vmdk file! Please check.
  10. Possible a zombie vm! Please check.
  11. Inconsistent Folder Names
  12. Multipath operational state
    Degraded = One or more paths to the LUN are down, but I/O is still possible.
    Further path failures may result in lost connectivity
    Error = The LUN is dead and/or not reachable
    LostCommunication = No more paths are available to the LUN.
    Off = The LUN is off.
  13. Virtual machine consolidation needed
  14. Search datastore errors.
  15. VM config issues
  16. Host config issues
  17. NTP issues
  18. Cluster config issues
  19. Datastore config issues

All can help you find some common mistakes at VM level, but maybe you have to tuning some parameters to adapt them at your needs.

For example, the default number of VMs per datastore is quite low and this provide false positive messages. The number could make sense on Virtual Infrastructure 3.x, maybe also for vSphere 4.x, but starting with vSphere 5.x you can have reasonably also more than 20 VMs on a datastore, with a limit that could depends on how VAAI ATS is used, the type of workloads and the type of storage… but usually less than 30-40 VMs.

Also notes that if you have same datastore shared with different clusters and hosts managed you may have still some false positive on zombie VMs and zombie VMDKs. For example if you are just inventory ESXi hosts individually. Or if you have different vCenter. Make always a double check on the dates of your VMDK files before try to delete them!

  • Comments (0)

Comments are closed.

© 2024-2011 vInfrastructure Blog | Disclaimer & Copyright