Closed ilanni2460 closed 8 months ago
The old iLO 4 machines are also not fully compatible with the Redfish standard.
I made some changes, such that Memory partially works now, but for the network there is again not enough information available. I have not looked at the storage part yet.
The old iLO 4 machines are also not fully compatible with the Redfish standard.
I made some changes, such that Memory partially works now, but for the network there is again not enough information available. I have not looked at the storage part yet.
Already very good, I just used the latest code and can already get the latest memory information. Currently, it cannot be stored, so I don’t know if it can be obtained. It doesn't matter if the network cannot be obtained. After all, the network here only shows how many network ports are alive and the speed of the network card.
@mrlhansen There are some problems found in obtaining the memory operating frequency. In the ilo web interface, you can clearly see that the operating frequency is 2400MHz, but through idrac_exporter, the obtained operating frequency is 0. I guess this should be a bug.
At the same time, I also noticed that the value obtained by the metric idrac_power_control_capacity_watts is exactly the same as the memory operating frequency.
This is indeed a bug. I have fixed it. I need to modify line 364 of the internal/collector/client.go file and add the following content:
m.OperatingSpeedMhz = m.MaximumFrequencyMHz
I was actually looking at this. However, 2400 Mhz is the maximal possible speed of the module, while in reality the actual speed is in your case only 1333 Mhz from what I can read. The metric is supposed to report the operating speed and not the maximal possible speed and this is why I did not include it.
I was actually looking at this. However, 2400 Mhz is the maximal possible speed of the module, while in reality the actual speed is in your case only 1333 Mhz from what I can read. The metric is supposed to report the operating speed and not the maximal possible speed and this is why I did not include it.
OK, thank you very much for your reply.
@mrlhansen By the way, I have updated part of the code for ilo4 storage monitoring. In line 131 of client.go, I added the following content.
client.memoryPath = "/redfish/v1/Systems/1/Memory/"
client.storagePath = "/redfish/v1/Systems/1/SmartStorage/ArrayControllers/0/DiskDrives/"
After compilation, using the debug mode of idrac_exporter, you can see the interface for storing redfish, but I really don’t see the relevant information stored. Please help me find out where the problem is. Thank you very much🙏
I made another commit and storage should now be working. I think this is the best I can do for iLO 4
I made another commit and storage should now be working. I think this is the best I can do for iLO 4
Thank you very much. Using the latest code, you can now obtain disk related information.
HPE Server iLO 4 ProLiant DL580 Gen9 cannot obtain memory, disk, network and other information
idrac_exporter debug log:
NetworkInface:
curl -k https://10.10.190.32/redfish/v1/Systems/1/EthernetInterfaces/4/
Memory:
curl -k https://10.10.190.32/redfish/v1/Systems/1/Memory/
curl -k https://10.10.190.32/redfish/v1/Systems/1/Memory/board1dimm4/ |jq .
Disk:
curl -k https://10.10.190.32/redfish/v1/Systems/1/SmartStorage/ArrayControllers/0/ |jq .
curl -k https://10.10.190.32/redfish/v1/Systems/1/SmartStorage/ArrayControllers/0/DiskDrives/ |jq .
curl -k https://10.10.190.32/redfish/v1/Systems/1/SmartStorage/ArrayControllers/0/DiskDrives/0/ |jq .