- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Remote Server Management
- >
- Re: Cannot get iLO5 data through powershell
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-02-2021 12:40 AM
02-02-2021 12:40 AM
Cannot get iLO5 data through powershell
Hello,
I am trying to get data (healthsummary, powersettings etc..) from servers with iLO4 and iLO5; for that, I am using the HPEiLOCmdlets 3.0.
With an iLO4 I can connect and get the data.
For example :
$connection = Connect-HPEiLO $myILO -Username $iLOUser -Password $iLOPassword -DisableCertificateAuthentication
(Get-HPEiLOServerInfo -Connection $connection).HealthSummaryInfo
IP : x.x.x.x
Hostname : xxxxxxxxxxxxx
Timeout : 30
DisableCertificateAuthentication : True
TargetInfo : @{ProductName=ProLiant DL360 Gen9; ServerFamily=ProLiant; ServerGeneration=Gen9; ServerModel=DL360; iLOGeneration=iLO4; iLOFirmwareVersion=2,77; SystemROM=P89 v2.74 (07/21/2019);
ProcessorName=Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz}
ExtendedInfo : @{UserSuppliedAddress=x.x.x.x; HttpConnectAddress=x.x.x.x; UserName=Wcc; Modifier1=Zri1Oi5JT3o5mED76mTkge6slyNHarLFC0GmFH5mk=; Modifier2=Bjt5Aju3D0uXdLLMxjechA==}
ConnectionInfo : @{RIBCL=; REST=}
BatteryStatus : OK
BIOSHardwareStatus : OK
FanStatus : OK
FanRedundancy : Redundant
MemoryStatus : OK
NetworkStatus : OK
PowerSuppliesStatus : OK
PowerSuppliesRedundancy : Redundant
ProcessorStatus : OK
StorageStatus : OK
TemperatureStatus : OK
Get-HPEiLOPowerReading -Connection $connection -OutputType Object
PresentPower : 126 Watts
AveragePower : 124 Watts
MaximumPower : 149 Watts
MinimumPower : 124 Watts
IP : x.x.x.x
Hostname : xxxxxxxxxxxxxxxx
Status : OK
StatusInfo :
If I try the same with an iLO5, I can connect but I can't get any data through the cmdlet :
$connection = Connect-HPEiLO $myILO -Username $iLOUser -Password $iLOPassword -DisableCertificateAuthentication
IP : x.x.x.x
Hostname :
Timeout : 30
DisableCertificateAuthentication : True
TargetInfo : @{ProductName=ProLiant DL385 Gen10 Plus; ServerFamily=ProLiant; ServerGeneration=Gen10Plus; ServerModel=DL385; iLOGeneration=iLO5; iLOFirmwareVersion=2,33; SystemROM=A42 v1.30 (07/18/2020);
ProcessorName=AMD EPYC 7502 32-Core Processor }
ExtendedInfo : @{UserSuppliedAddress=x.x.x.x; HttpConnectAddress=x.x.x.x; UserName=Wcc; Modifier1=YLyeADYoo3sS46GfmND3/H7vre60CAfE5QUSwE8z7Wc=; Modifier2=BxU9S45cz8PXB9bqLO/oWw==}
ConnectionInfo : @{Redfish=}
Get-HPEiLOServerInfo -Connection $connection -OutputType Object
FanInfo : {HPE.iLO.Response.Redfish.Fan, HPE.iLO.Response.Redfish.Fan, HPE.iLO.Response.Redfish.Fan, HPE.iLO.Response.Redfish.Fan...}
FirmwareInfo : {HPE.iLO.Response.Redfish.FirmwareInformation, HPE.iLO.Response.Redfish.FirmwareInformation, HPE.iLO.Response.Redfish.FirmwareInformation, HPE.iLO.Response.Redfish.FirmwareInformation...}
TemperatureInfo : {HPE.iLO.Response.Redfish.Temperature, HPE.iLO.Response.Redfish.Temperature, HPE.iLO.Response.Redfish.Temperature, HPE.iLO.Response.Redfish.Temperature...}
MemoryInfo : HPE.iLO.Response.Redfish.MemoryInfoDetail
NICInfo : HPE.iLO.Response.Redfish.NICInfoDetail
PowerSupplyInfo : HPE.iLO.Response.Redfish.PowerSupply
ProcessorInfo : {HPE.iLO.Response.Redfish.Processor, HPE.iLO.Response.Redfish.Processor}
HealthSummaryInfo :
ServerName :
HostOS :
IP : x.x.x.x
Hostname :
Status : OK
StatusInfo :
(Get-HPEiLOServerInfo -Connection $connection).HealthSummaryInfo
Get-HPEiLOPowerReading -Connection $connection -OutputType Object
PresentPower : Watts
AveragePower : Watts
MaximumPower : Watts
MinimumPower : Watts
IP : 10.252.14.231
Hostname :
Status : OK
StatusInfo :
As you can see healthsummary is empty as the power readings.
Many of the cmdlets return nothing for data but each time the status of the cmdlet is OK.
If I look in the Scripting Tools for Windows Powershell 3.0, the cmdlets are well compatible for iLO4 and 5.
I have tried this on multiple GEN10 servers and it is always the same, I can't get all the data I need.
An example of a cmdlet that returns data is (Get-HPEiLOPowerSupply -Connection $connection -OutputType Object).powersupplies
Id : 0
Name : HpeServerPowerSupply
Model : 865414-B21
SerialNumber : xxxxxxxxxxxxxxx
SparePartNumber : 866730-001
PartNumber :
PowerSupplyType : AC
Capacity : 800
FirmwareVersion : 1.00
AveragePower : 145
LineInputVoltage : 228
LineInputVoltageType : ACHighLine
BayNumber : 1
Mismatched : No
HotPlugCapable : Yes
MaxPowerOutputWatts : 149
Status : HPE.iLO.Response.Redfish.Status
PowerSupplyStatus : Ok
iPDUCapable : No
iPDU :
Id : 1
Name : HpeServerPowerSupply
Model : 865414-B21
SerialNumber : xxxxxxxxxxxxxxxx
SparePartNumber : 866730-001
PartNumber :
PowerSupplyType : AC
Capacity : 800
FirmwareVersion : 1.00
AveragePower : 140
LineInputVoltage : 227
LineInputVoltageType : ACHighLine
BayNumber : 2
Mismatched : No
HotPlugCapable : Yes
MaxPowerOutputWatts : 145
Status : HPE.iLO.Response.Redfish.Status
PowerSupplyStatus : Ok
iPDUCapable : No
iPDU :
Am I missing something ?
How can I get all the info from these iLO5 through powershell ?
Thanks for your help
Marc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2021 07:04 AM
02-17-2021 07:04 AM
Re: Cannot get iLO5 data through powershell
With the help of an enginner from HPE we have determined that the problem comes from the firmware version of the iLO5.
The problem doesn't occur with the version 1.46 but occurs with firmware 2.00 and up to 2.33.
It seems that the HPEilocmdlets need to be updated for these firmware.
Marc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2021 01:06 AM
02-24-2021 01:06 AM
Re: Cannot get iLO5 data through powershell
So, is the issue resolved for you now?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2021 11:17 PM
03-02-2021 11:17 PM
Re: Cannot get iLO5 data through powershell
Hello,
Yes and no, a new module is out now, v3.1.0.0 but there are still problems with some cmdlets not returning data or incomplete data depending of the version of the ILO5 firmware or depending of the iLO generation.
I am in contact with HPE about that.
Marc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2021 03:38 AM
06-01-2021 03:38 AM
Re: Cannot get iLO5 data through powershell
@Marc Vanderhaegen_1 wrote:
QUOTE
Hello,
Yes and no, a new module is out now, v3.1.0.0 but there are still problems with some cmdlets not returning data or incomplete data depending of the version of the ILO5 firmware or depending of the iLO generation.
I am in contact with HPE about that.
Marc
UNQUOTE
Very interesting information. Thanks for sharing. I might face similar issue.
Did you get more information from HPE? Will they update the PowerShell Module to support latest firmware versions in the near future?