I tested this script on several HP models and several iLO versions. PS C:\> Get-HPServerStatistics -ComputerName 10.0.7.156 -Credential $CredentialĬomputerName ProductName CurrentPower CurrentTempġ0.0.7.156 ProLiant D元60p Gen8 85 Watts 73.4F / 23C
Not specifying the -Summary parameter will result in a different output. PS C:\> Get-HPServerStatistics -IPAddress 10.0.7.156 -Credential $Credential -Summary The -Summary parameter gives you just that, a summary of your server and iLO settings. For those of you who don’t care and use it strictly for your homelab, I provided the option to hardcode your creds into the script. The -Credential parameter was implemented so you can enter in your credentials for that added security. Again, this is the ComputerName or IPAddress of the iLO IP. IPAddress was added as an alias to specify which servers you would like to query. The best part is that you can query multiple servers at once. This script uses Invoke-WebRequest to initially login and parse the data needed, then it converts from JSON to output the data into a nice and neat table format. Hence the title, Get HP Server Status Using Powershell (iLO Query). Luckily for myself, I am pretty well versed in Powershell and created a script to check those settings for me. The problem is, I had to keep logging into the iLO (Integrated Lights Out) to check the settings and after a while I started wondering why I was manually logging every so often to check the same thing. Since I run my homelab in a small, non-ventilated area I’ve found myself doing this on a regular basis.
#Hp ilo 4 cli commands pdf#
I’ll have to give it a go this week…and see what other nuggets are in that CLI guide.įYI, the link to HP’s PDF is bad…looks like you have your article’s URL prepended to HP’s URL.If you have a homelab (or work environment) filled with HP ProLiant equipment as I do, you might have found yourself checking your power consumption and temperatures on a regular basis to ensure they’re not overheating and/or drawing too much power. Think it might an ILO1 issue, nice to see this has been resolved with ILO2… I tried this via the GUI on the old ILO1 (Ive got G1s) and found powermanagement rights weren’t enough to make DPM work. You can configure all iLO settings on an entire enclosure with 1 command. RIBCL + HPONCFG using the OA CLI (or external scripts) is even simpler. Woops – thx for pointing out the broken link fellas, I left the off the front of the URL so WordPress thought it was a local link! You can leave a response, or trackback from your own site.Ħ Responses to “Create Users with the HP iLO CLI” You can follow any responses to this entry through the RSS 2.0 feed. This entry was posted on Augat 9:13 pm and is filed under Uncategorized. Will post up some more examples as I come across them! Doing this via the CLI on 16 blades sure was a lot faster than pointing and clicking my way through. Do we like the principle of least privilege? Yes we do :). This will result in a user being created with only the ‘Virtual Power and Reset’ privilege, which is all that is required for DPM to work. Set /map1/accounts1/dpm_usr group=oemhp_power You can do this in 2 simple commands:Ĭreate /map1/accounts1 username=dpm_usr password=a_strong_password The task at hand was to create some users on each blade in order to play around with vSphere’s Distributed Power Management feature. So I thought what the hell, I might as well put up a few posts on the quickest way to do some common tasks. Of course the interface is fully documented here, but the commands, contexts and properties are documented in different sections so it doesn’t flow that well. But with the amount of blades coming into the lab these days, I figured it was about time I started using the CLI to do stuff rather than the web based UI. I must admit, configuring stuff on HP boxes via their Integrated Lights Out (iLO) is something you don’t have to do often… generally you do it when you set a new box up and that’s it.
0 kommentar(er)
