Get HPE SSD Hard Disk Information by PowerShell

HPE published an advisor for SSD issue recently. The issue impacts most popular Proliant servers in the world. The remediation is upgrading firmware. Unfortunately HPE doesn’t have a product can easy report hard disk model for Gen9 and earlier models.

Summary

HPE published an advisor for SSD issue recently. The issue impacts most popular Proliant servers in the world. The remediation is upgrading firmware. Unfortunately HPE doesn’t have a product can easy report hard disk model for Gen9 and earlier models. I have tried HPE OneView and OneView Global Dashboard. However, we can get SSD hard disk information by PowerShell through API.

Solution

Following procedure helps you get SSD hard disk information in large environment.

  1. Make sure you have same credential available on iLO of Proliant servers. It can be local or domain credentials.
  2. Prepare a Windows 2016 or Windows 10 computer with latest patch and internet.
  3. Install HPEiLOCmdlet by following PowerShell command
    Install-Module -Name HPEiLOCmdlets 
    
  4. Run following command to connect to HPE iLO
    $Conn = Connect-HPEiLO -IP xxx -User xxx -Password xxx -DisableCertificateAuthentication
  5. Run following command to retrieve HPE Smart Array Storage Controller information.
    $HardDisks = Get-HPEiLOSmartArrayStorageController -Connection $Conn
  6. Run following command to get physical disk information.
    $HardDisks.Controllers.PhysicalDrives

Conclusion

PowerShell API is much flexible to get any information of hardware. The solution above is core part. Of course you can leverage ForEach-Object to do some automation report to export to CSV file. PowerShell is not only method, you can also get SSD hard disk information by other API.

“The Update is Not Applicable to Your Computer” When Install KB3046101

  HPE 3PAR upgrading team usually sends a per-requisites before upgrading. One thing in the guide incorrect is the Windows 2012 required patch KB3046101.     You may see error below when you install the path on Windows 2012 server.    
The update is not applicable to your computer
      The reason is the version of mpio.sys and msdsm.sys on your server is higher than 6.3.9600.17809. Usually, because the server installed KB3121261 already. You can ignore KB3046101.