Navigation:  Remote Monitoring and Management > Proactive Monitoring > Windows Server and Workstation Monitoring > 24x7 Checks > Script Check > Default Script Checks > Virtualisation >

VMware ESXi Health – Storage

Previous pageReturn to chapter overviewNext page

 

Script Type: PowerShell

 

The VMWare ESXi Health – Storage Script can be used to monitor multiple elements of the storage sub-system (RAID controller, physical disks etc) with the PowerShell Script retrieves the health status from the storageinfo and numeric sensors where they contain the string disk.

 

Information on each of the monitored sensors is available from the Dashboard in the clickable Extra column against the relevant Check.The subsequent More Information dialog contains the sensor’s Name, a Summary of its current condition - for example Sensor is Operating under normal conditions or Physical element is functioning as expected - along with its Health indicator (pass or fail).

 

Storage

Name

Summary

Health

 

The Script will pass where the Health status is reported as okay or unknown, with any problem conditions generating a failure. The Health state indicators are: pass (green tick), unknown (grey tick) or fail (red cross

 

 

clip1042

clip1041

 

 

Please note, the level of information returned by the script may vary depending upon the queried hardware and version of ESXi installed.

 

Our VMware ESXi scripts are supported on ESXi 6.5 or earlier.

 

Requirements

The script uses the VMware CIM / SMASH API including the WSMAN library which is not supported on XP, 2003 or earlier Operating systems.

 

In addition to this, Microsoft .Net 3.5 (or higher), PowerCLI and PowerShell 2.0 (or later) must be installed on the device the scripts will be executed from.

 

Additionally for PowerShell scripts Microsoft .Net 3.5 (or higher), PowerCLI and PowerShell 2.0 (or later) must be installed on the device the scripts will be executed from.

Please note: PowerCLI is supported up to version 6.0. Later versions of PowerCLI (from 6.3) are currently unsupported and may results in unexpected results when running Checks.

 

We suggest running this script from machines running Agent 8.16.1RC or later.

 

PowerShell: the use of $ and other special characters in the password

Consideration must be given when passing passwords that contain special characters through PowerShell to ensure they are handled as literal strings.

 

For example if the password contains a dollar sign ($) it must either be preceded by a grave accent ` (also known as a backtick: ASCII code 96 - Alt+96) or the password encapsulated in single ' ' to pass the password to PowerShell exactly as entered.

 

Password Example

String

Result

pas$word

pas

pas`word

pas$word

'pas$word'

pas$word

 

Where the password contains a special character (in this example dollar sign) but no preceding grave accent, or is not encapsulated in single quotes, the message Failed to connect – Credentials invalid is returned.

 

Note: some PowerShell special characters are themselves constructed using a grave accent so should be encapsulated in single quotes when passed via the Script and these are covered in the Microsoft Technet article: about_Special_Characters

 

Further information on Escape_Characters and Quoting_Rules is available from Microsoft's Technet

 

Please be aware that we are not responsible for the content of external sites.