Recently I've worked a bit with the HPE OneView Global Dashboard. I was surprised to see that HPE hadn't created a Powershell Module for it so I decided to create one my self

HPE [launched their InfoSight for servers](https://www.hpe.com/no/en/storage/infosight.html) back in January and as we have been using InfoSight for both Nimble and lately for our 3PAR systems we wanted to bring our compute into the mix as well

HPE [recently announced](https://community.hpe.com/t5/Servers-The-Right-Compute/HPE-delivers-on-our-promise-InfoSight-is-expanding-to-servers/ba-p/7025088#.XD3nnVxKiUk) that their [HPE InfoSight](https://www.hpe.com/us/en/storage/infosight.html) service now supports servers. This is something we have been waiting for and we're eager to check out the new functionality

As a follow-up of my exploration of the [HPE PDU REST API](/2018/11/19/exploring-the-hpe-g2-pdu-rest-api/) I wanted to create a Powershell module as a wrapper for the API. I've previously written a post on how to create a Powershell module as a wrapper for an API [here](/2018/01/31/creating-a-powershell-module-as-an-api-wrapper/). The PDU module will be built in the same way where there will be a private function that handles the actual API requests

Lately I've been playing around with the Redfish based REST API in the HPE G2 Metered and Switched Power Distribution Units. Through the API you are able to pull some details about the PDU as well as different utilization data. Based on your PDUs capabilities you should also be able to control different outlets. My …

This article will describe how you can disable the IPMI over LAN access on HPE iLO. The IPMI protocol can present a security vulnerability where the authentication process for IPMI requires a server to send a hash of a user password to the client before authentication. This is not a new vulnerability and since this is …

This is a short post on how to extend the internal firmware repository in HPE OneView. The procedure is documented in the installation guide for 3.0, but if you are like me chances are that you don't have that lying around so I thought I'd write up a short post on it for future reference. The process is pretty straight …

Recently we received lots of new hardware destined for a customer that has multiple locations world-wide. They need a robust server solution for their production environments locally. The environment is small in terms of number of VMs, but there is high demands on the environment and we need local hardware at the sites …

The last months we have had several issues with ESXi hosts going in a "Not responding" status. The VMs are still active and online in this scenario, but the ESXi cannot be managed. This also affets backup as it won't be able to reach the VMs through the APIs. Previously we have normally just restarted the …