From f0d96b30ca6d052198d6f033a5e6147dde7cb533 Mon Sep 17 00:00:00 2001 From: Victor Hu Date: Tue, 26 Jan 2016 09:09:47 -0500 Subject: [PATCH] For IBM Power 822LC and 812LC, it seems there is something wrong with the firmware that causes the BMC to stop replying to ping a few seconds after the changes are made. To work around this issue, sleep 30 before doing the cold reset. Once the firmware is fixed, this reset is NOT needed --- xCAT-genesis-scripts/bin/bmcsetup | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/xCAT-genesis-scripts/bin/bmcsetup b/xCAT-genesis-scripts/bin/bmcsetup index f52a2f4cf..6c872ff53 100755 --- a/xCAT-genesis-scripts/bin/bmcsetup +++ b/xCAT-genesis-scripts/bin/bmcsetup @@ -399,10 +399,21 @@ if [ ! "$IPMIVER" == "1.5" ]; then #if [ $TRIES -gt $TIMEOUT ]; then echo "ERROR"; else echo "OK"; fi fi -# Reset the BMC for the x3755 M4 (8722), otherwise the BMC will not be pingable after running of bmcsetup +# +# Cold Reset the BMC for: +# Product ID: 309 - x3755 M4 (8722) +# Product ID: 43707 - IBM Power S822LC and S812LC +# Otherwise the BMC will not respond to ping after running bmcsetup +# XPROD=`ipmitool mc info|grep "^Product ID"|awk '{print $4}'` -# Product ID with 43707 is for IBM Power S822LC and S812LC machine if [ "$XPROD" = "309" -o "$XPROD" = "43707" ] ; then + if [ "$XPROD" = "43707" ]; then + # The IBM Power S822LC and S812LC should NOT need a reset to apply changes + # to the BMC. However, it seems there's a problem with the BMC where after + # 15 seconds, it stops responding. To work around until the firmware is fixed, + # have a sleep here for 30 seconds, then issue the reset of the BMC + sleep 30 + fi echo "Resetting BMC ..." ipmitool mc reset cold echo "Waiting for the BMC to appear ..."