Jump to content
RESET Forums (homeservershow.com)
acidzero

HP Microserver Gen8 + HP P410 + ESXi 6.5U1 + VCSA 6.5U1

Recommended Posts

acidzero

Hello,

 

So, after several days of testing various different configurations, creating custom ESXi install ISOs and numerous reinstalls, I've managed to get ESXi 6.5U1 installed on my Microserver Gen8 and have working HP Smart Array P410 Health Status showing. For those that are struggling to do the same, firstly here's how. I used original VMWare ESXi 6.5U1 ISO, build 5969303 then made the following modifications:

 

  • Remove driver "ntg3" - If I left this in, I had a weird network issue where Port 1 or 2 would repeatedly connect/drop every few seconds. This forces ESXi to use the working net-tg3 driver
  • Remove driver "nhpsa" - this Smart Storage Array driver is what causes array health monitoring to not work. Remove to force ESXi to use working "hpsa" driver
  • Add the Nov 2017 HPE vib bundles
  • Remove hpe-smx-provider v650.01.11.00.17 - This version seems to cause the B120i or P410 to crash when querying health status
  • Add hpe-smx-provider v600.03.11.00.9 (downloaded from HPE vibsdepot)

  • Add scsi-hpvsa v5.5.0-88 bundle (downloaded from HPE drivers page)

  • Add scsi-hpdsa v5.5.0.54 bundle (downloaded from HPE drivers page)

 

I did the above by getting a basic/working ESXi/VCSA installation and then creating a custom ISO in VCSA AutoDeploy and exporting it. But the same can be achieved by installing VMWare's original ISO and modifying via the esxcli command.

 

I have a SSD connected to the SATA port, onto which I am installing ESXi. The 4 front drive bays are connected to the P410.

 

  • Configure the Microserver Gen8 B120i to use AHCI mode - the B120i is a fake raid card so only reports physical disks to ESXi. Leaving in RAID mode works but I got a false Health Alert on Disk Bay 5
  • Install my modified ESXi ISO to the SSD

 

With these modifications I have a working ESXi 6.5U1 on my Gen8 with fully functioning HPE tools and array health monitoring:

 

FornQz5.jpg

I also tested disabling the vmw_ahci driver, which is why the AHCI controller shows it is using ahci in the above image.

klryZ4n.jpg

 

If I pull out a disk to test a raid failure, when the health status next updates I can see a raid health alert in the ESXi WebGUI:

 

yqmmt9d.jpg

 

However I'm now stuck at the next stage - getting this storage health to pass through to VCSA. VCSA can successfully see all other health monitors (under System Sensors in ESXi) just not the storage, which is the most important.

 

yqmmt9d.jpg

 

Does anyone know how I can get the storage health working in VCSA?

 

Thanks.

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites
cansher

Thanks!

 

Disabled the nhpsa driver and installed a hpsa driver separately and seems to have solved my problems with creating datastores.

Received a "cannot change the host configuration" error before, and system was more sluggish.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • npapanik
      By npapanik
      FYI, I have just installed Windows Server 2019 Standard (Desktop Experience) using the latest (WS2016) HP AMD chipset & VGA driver. Everything is recognised in Device Manager and stable.
    • TonyTheTechie
      By TonyTheTechie
      I need to update the firmware on a HP Proliant Microserver Remote Access Card installed in my N40L.
       
      Can someone please explain what I need to do to create a boot device that will update the firmware on the Remote Access Card?
       
      Thanks
       
      Tony Self
    • pksparks
      By pksparks
      Good evening,
       
      after checking my ILo4, version2.61 on my Gen8 hp microservet, i saw an exclamation mark at cpld-pal0. It is now version 0x06.
      i have read that there is an version 0x32.
       
      anybody who has this version, and can provide me with a download link?
       
      Attached my firmware configuration. Any suggestions for any updating? Think most is up to date?
       
      rgds
      patrick
      Sorry can’t upload photo, error 200.
    • Richardracer
      By Richardracer
      Good afternoon,
       
      Newbie here, so please be gentle with me!
       
      I have an 18 month old Gen8 server bought new but now out of warranty, so limited access to HPE updates.  My Gen8 has 8Gb memory, Recently added Xeon 1220v2, standard disk controller (122i ) and 4 off 3.5” drives giving 6Tb of storage under storage spaces.  OS on SATA HDD  sitting in ODD space as recommended on here.  I was running Win10 Pro, but after upgrading processor and trying to update drivers with Intelligent Provisioning, I fell foul of the expired warranty.  I also lost my printer driver for HP laser jet and my sound drivers (usb connected sound card).
       
      To cut a long and painful journey a bit shorter, I am re-installing Win10 Pro from DVD, with licence key under IP.  My question as someone without warranty, but with a copy of the SPP download (ISO?), how do I install the various drivers needed from the SPP and do I need to update the firmware for the Xeon processor, if so how?  I read on here that the original 2014 J06 firmware does not have a thermal solution for Xeon processor and ILO shows high temps for some components.
       
      I am reasonable knowledgeable in Windows of old and have Rufus to create bootable usb sticks, but unsure how to get from SPP ISO image as downloaded (871795_001_spp-2017.04.0-SPP2017040.2017_0420.14).
       
      Any help from experienced gurus much appreciated!
       
      regards
       
      Richardracer.
    • Joe_Miner
      By Joe_Miner
      I installed a BU50N Blu-ray 4K drive in my HPE ProLiant Gen8 MicroServer.  Worked out well, I'm using PowerDVD13 -- I had to restart the "Machine" several times before it saw the ODD but "Machine" finally figured it out.
       
       
       
       
       
       










×
×
  • Create New...