ProLiant MicroServer Gen8 installed ESX 6.7 and try to find correct SSA CLI download

[justinwubo]

Hi I have one Gen 8 Micro Server and get ESX 6.7 installed. I try to monitor the NVME SSD status and was told to install Smart Storage Administrator CLI.

But I cannot find where to download it. Any helps will be much appreciated!

[Suman_1978]

Hi,

I could not find server specific download, but here is OS specific download.
Smart Storage Administrator (SSA) CLI for VMware 6.7

HPE Smart Storage Administrator CLI User Guide

Thank You!
I work with HPE but opinions expressed here are mine.
HPE Tech Tips videos on How To and Troubleshooting topics

[justinwubo]

Thanks for the later reply! It did help me install the SSA, but I found it could not get the NVME device on my ESXi.

But run 'lspci' on the ESXi server, the NVME is there. So how could I get it on the ssacli?

[Vinky_99]

@justinwubo 

Good day!

If your NVMe SSD is not showing up in the SSA CLI, it's possible that the SSD is not managed by the HPE Smart Array controller, or there may be driver-related issues.

[Vinky_99 · Accepted solution]

Found this additional info see if this helps you. You may give a try to below ones:

>> Ensure that your NVMe SSD is officially supported by your HPE ProLiant MicroServer Gen8 and the Smart Array controller. You can usually find a list of compatible hardware on HPE's website or in the server's documentation.

>> Make sure that your server's firmware (BIOS/UEFI) and drivers are up to date. Sometimes, updates include better support for new hardware.

>> Check if your NVMe SSD is connected to an HPE Smart Array controller. If it's connected directly to the motherboard or a separate PCIe controller card, you may need to use a different tool or utility to manage it, as SSA is primarily designed for HPE Smart Array controllers.

>> Ensure that the necessary NVMe drivers are installed and functioning correctly in your ESXi installation. If the drivers are missing or outdated, your NVMe SSD may not be recognized by the system.

>> If your NVMe SSD is not managed by an HPE Smart Array controller, you may need to use NVMe-specific management tools. For example, you can use the "nvme-cli" utility, which is a command-line tool for managing NVMe devices in Linux-based systems like ESXi. You would typically install this tool within your ESXi environment.

To install "nvme-cli," you can use the following command on your ESXi host (ensure you have SSH access):

esxcli software vib install -v https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vib20/tools-light/VMware_locker_tools-light_6.7.0-1.48.17441118.vib

Replace the URL with the appropriate one for your ESXi version.

>> Ensure that your version of ESXi is compatible with NVMe SSDs. Some older versions may not fully support NVMe drives, so upgrading to a more recent version may help.

>> Verify that the NVMe SSD is not being used for other purposes (e.g., VMFS datastores) that might prevent it from appearing in SSA. In ESXi, you can use the "esxcli storage core device list" command to list all storage devices detected by ESXi.

>> If you've tried the above steps and are still experiencing issues, it may be a specific compatibility or configuration issue. Contacting HPE support can be helpful for diagnosing and resolving such issues.

Remember to take precautions when making changes to your server's configuration, and always back up important data before performing any potentially disruptive actions.

Let me know... 

[justinwubo]

nvmecli did work it out.

esxcli nvme device log smart get --adapter=vmhba1
SMART And Health Info:
   Available Spare Space Below Threshold: false
   Temperature Warning: false
   NVM Subsystem Reliability Degradation: false
   Read Only Mode: false
   Volatile Memory Backup Device Failure: false
   Composite Temperature: 324 K
   Available Spare: 100 %
   Available Spare Threshold: 10 %
   Percentage Used: 0 %   
   Data Units Read: 0x150d580
   Data Units Written: 0x9d9ba5
   Host Read Commands: 0x5ab259c2
   Host Write Commands: 0xf15cd5c
   Controller Busy Time: 0x34c
   Power Cycles: 0xd
   Power On Hours: 0x1f16
   Unsafe Shutdowns: 0xb
   Media Errors: 0x0
   Number of Error Info Log Entries: 0x0
   Warning Composite Temperature Time: 0 Mins
   Critical Composite Temperature Time: 0 Mins
   Temperature Sensor 1: 324 K
   Temperature Sensor 2: 341 K
   Temperature Sensor 3: 354 K
   Temperature Sensor 4: 0 K
   Temperature Sensor 5: 0 K
   Temperature Sensor 6: 0 K
   Temperature Sensor 7: 0 K
   Temperature Sensor 8: 0 K

[Sunitha_Mod]

Hello @justinwubo,

That's awesome! We are extremely glad to know you were able to find the solution and we appreciate you for keeping us updated.