How did you find out that error without the HP drivers? Maybe the storage was running without write-cache since months and nobody was able to understand why…Īnother alert we got, was about the missing ILO configuration (for those of you not used to HP hardware, it’s the remote console):īesides the alert, the HP drivers were also helpful to correct the error. Since this server was also hosting some VMs in its local datastores, this information was useful for replacing the battery and have again a working situation.
The two alert were related to the battery status of the embedded P400 raid controller: Once I installed the drivers on one of my customer’s HP server (a quite old D元80 G5), the server rebooted and showed us two alert and a warning that were not there before. Even if all the servers in VMware HCL are correctly recognized, not all their hardware information are correctly displayed. The plain ESXi installation does have a great amount of drivers in it, but for obvious reasons it cannot hold all the existing drivers. What I want to show you here, is why these drivers can be useful in managing your ESXi servers and how you can effectively take advantage of them.įirst of all, these drivers add further informations to the Hardware Status tab of your servers. I’m not going to copy/paste their articles.
Those two blog posts are really useful resources to understand how to configure vCenter Update Manager to update your HP servers with their specific drivers. Update your HP drivers with VMware Update Manager from Viktor van den Berg
I recently installed the HP drivers on some customers’ server following these two great guides:Īdd HP drivers to VMware Update Manager (VUM) from Ivo Beerens
0 Flares Twitter 0 Facebook 0 LinkedIn 0 Email - 0 Flares ×
0 kommentar(er)
