Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vHealth Collect #26

Open
waldirio opened this issue May 18, 2018 · 0 comments
Open

vHealth Collect #26

waldirio opened this issue May 18, 2018 · 0 comments

Comments

@waldirio
Copy link
Owner

waldirio commented May 18, 2018

The “vHealth” tab displays the health check messages.

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant