As a follow-up of my exploration of the HPE 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. 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 focus has been to pull some details about the PDUs, and to pull the load on the different segments.
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 a part of the specification of the protocol there is no fix for it besides disabling it or accepting it.
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 forward: Shut down the appliance Extend the hard disk to 275GB* Start the appliance The repository should be extended, if not do a manual restart
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 as the connections to these sites varies and they are not fast enough at all times. Lots of racks
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 management agents on the host and it has been able to connect to vCenter and after this we have managed to migrate the VMs off the host.
After the release of the new and shiny version 4.1 of HPE OneView we have tried to upgrade one of our (smaller) OneView instances. The update process is usually quite straight forward and it gets better in every release. The upgrade to 4.0 from 3.x had some issues with certificate handling post-upgrade, but it was manageable. The upgrade from 4.0 to 4.1 should not be affected by the same so I had great hopes about a smooth upgrade.
Recently HPE released version 4.1 of their management platform, OneView. We use OneView extensively in our environment and are always looking out for new functionality and features in the product. Version 4.1 comes with some new promising features. Secure remote troubleshooting with Remote Technician Reduced downtime for firmware and driver updates for HPE ProLiant servers Simplified cluster management and rolling updates Especially the ability to schedule firmware upgrades and rolling updates on a vSphere cluster sounds exiting and are very welcome.