You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unexpected RAKP 2 message error seen after powering on system and checking system status using IPMI.
This problem is seen with the recent master build: 2.10.0-dev-607-g2aff2743d
Step to recreate:
Make sure the system is in the off state.
Power on the system using ipmitool command.
Check system state using ipmitool (here you will see Unexpected RAKP 2 message sometime).
Chassis Power is off
-bash-4.2$ ipmitool -I lanplus -C 17 -p 623 -U root -P 0penBmc -H <BMC_IP> chassis power on
Chassis Power Control: Up/On
-bash-4.2$ ipmitool -I lanplus -C 17 -p 623 -U root -P 0penBmc -H <BMC_IP> chassis power status
> Error: no response from RAKP 1 message
Error: Received an Unexpected RAKP 2 message
Error: Received an Unexpected Open Session Response
^[[A
> Error: no response from RAKP 1 message
Error: Received an Unexpected RAKP 2 message
Chassis Power is off
-bash-4.2$ ipmitool -I lanplus -C 17 -p 623 -U root -P 0penBmc -H <BMC_IP> chassis power status
Chassis Power is off
-bash-4.2$ ipmitool -I lanplus -C 17 -p 623 -U root -P 0penBmc -H <BMC_IP> chassis power status
Chassis Power is off
-bash-4.2$ ipmitool -I lanplus -C 17 -p 623 -U root -P 0penBmc -H <BMC_IP> chassis power status
> Error: no response from RAKP 1 message
Error: Received an Unexpected RAKP 2 message
Chassis Power is off
-bash-4.2$ ipmitool -I lanplus -C 17 -p 623 -U root -P 0penBmc -H <BMC_IP> chassis power status
Chassis Power is on
-bash-4.2$ ipmitool -I lanplus -C 17 -p 623 -U root -P 0penBmc -H wsbmc002 chassis power status
Chassis Power is on
-bash-4.2$```
The text was updated successfully, but these errors were encountered:
Unexpected RAKP 2 message error seen after powering on system and checking system status using IPMI.
This problem is seen with the recent master build: 2.10.0-dev-607-g2aff2743d
Step to recreate:
The text was updated successfully, but these errors were encountered: