aDeploy Upgrade Pre-Check Prompts "Failed to obt"

|
  • 929
  • 10

Issue Description

Using the aDeploy tool to perform the pre-upgrade assessment, and prompts an alert of "Failed to obtain IPMI information".

Error/Warning Information

285962046f14c04aa.png

Handling Process

1. Check and make sure the IPMI of the node is accessible.
2. Check if the ipmi modules have all loaded properly from system backend.
1424762047002c8374.png

Command: vs_cluster_cmd.sh e "lsmod | grep ipmi"
- make sure all these 3 modules are present. (ipmi_devinf, ipmi_si and ipmi_msghandler)
*If those modules aren't complete, execute command below to reload the module.
1694362047076b1246.png
- ensure the command sequence is as above image.

2. Try to grab ipmi logs from system backend.
11623620471513decd.png
- SEL value returns has no entries.
- probably due to the IPMI log is empty.

3. Try generating some logs to the IPMI.

4. Execute cluster health check again from aDeploy.
- the alert has been resolved.
8365262047306e16b2.png

Root Cause

IPMI SEL log is empty.

Solution

Refer to the handling process.

Suggestions

If the scenario varies from above or the solution doesn't work, kindly consult specialist or R&D for further verification.
Tanzeela Lv2Posted 14 Feb 2022 14:52
  
Nice Information
Tanzeela Lv2Posted 14 Feb 2022 14:55
  
Good Code
Surbakti Lv3Posted 14 Feb 2022 20:02
  
good information
Faisal Lv8Posted 07 Apr 2022 13:28
  
Raza Islam Lv3Posted 14 Jun 2022 13:34
  
Thanks for sharing.
Faisal P Lv8Posted 21 Sep 2022 08:22
  
Thank you very much for the information ...
Faisal P Lv8Posted 21 Sep 2022 08:23
  
Nice article ...
Faisal P Lv8Posted 21 Sep 2022 08:23
  
Great info ...
Faisal P Lv8Posted 21 Sep 2022 08:23
  
Very informative ...

I want to write a case
Doc ID: 5736
Author: CTI Chris
Updated: 2022-02-10 10:10
Version: