Great! I'll add your motherboard to the "seen on" list and I'll also
add a note about needing this workaround with the "not discovered" error.
Al
On 4/12/24 10:48, Devon Bautista wrote:
Al,
Thanks for your quick response.
Interestingly, rmcpping fails while ipmiping succeeds:
[admin@te-head ~]$ rmcpping bmc-te01
rmcpping bmc-te01 (172.16.0.101)
pong timed out: message_tag=164
^C--- rmcpping bmc-te01 statistics ---
2 pings transmitted, 0 pongs received in time, 100.0% packet loss
[admin@te-head ~]$ ipmiping bmc-te01
ipmiping bmc-te01 (172.16.0.101)
response received from 172.16.0.101: rq_seq=25
response received from 172.16.0.101: rq_seq=26
response received from 172.16.0.101: rq_seq=27
response received from 172.16.0.101: rq_seq=28
^C--- ipmiping bmc-te01 statistics ---
4 requests transmitted, 4 responses received in time, 0.0% packet loss
With that discovery, I added the 'ipmiping' workaround to the
ipmipower command, which succeeds:
[admin@te-head ~]$ sudo /usr/sbin/ipmipower -D lanplus -u admin -p
<password> -h bmc-te01 -I 17 -W ipmiping
ipmipower> stat
bmc-te01: on
Adding '-W ipmiping' to the ipmipower command line in the powerman
config causes the node to now be seen:
[admin@te-head ~]$ pm -q
on: te01
off:
unknown:
It seems that these BMCs either don't support RMCP or have it
disabled, but at least there is a workaround so thank you for helping
me discover it. 🙂
On 4/12/24 11:14 AM, Al Chu wrote:
Hi Dave,
That is quite interesting. Short description, in the background of
shell mode, ipmipower will "ping" nodes half regularly to make sure
they are there. Because it is supposed to "run forever" under
powerman, there's no point to send power control to nodes missing
from a cluster (e.g. taken out for maintenance) and thus slowing down
powerman.
"not discovered" means that it can't ping that node.
Does "rmcpping" to the node work?
if not, does "ipmiping" to the node work?
If so, perhaps the "ipmiping" workaround to ipmipower would work (see
manpage on workaround).
Al
On 4/11/24 21:21, Devon Bautista via Freeipmi-users wrote:
Hello,
Similar to my previous email regarding issues with the M50CYP Intel
board, I'm running into issues with the newer M50FCP Intel board.
I'm trying to use powerman to manage power to nodes with an Intel
M50FCP board:
[admin@te-head ~]$ pm -q
on:
off:
unknown: te01
The /etc/powerman/powerman.conf is:
include
"/etc/powerman/https://urldefense.com/v3/__http://ipmipower.dev__;!!Bt8fGhp8LhKGRg!BG2PhUDpc-5_EMUFXtI_2vLQzPsdohKTXub4ruPFSll9lzM83_0KczXA1IyNrcUnTxnXeP4SBCUvCL4$
"
device "ipmi0" "ipmipower" "/usr/sbin/ipmipower -D lanplus -u
admin -p <password> -h bmc-te01 -I 17 |&"
node "te01" "ipmi0" "bmc-te01"
Running the ipmipower command:
[admin@te-head ~]$ sudo /usr/sbin/ipmipower -D lanplus -u admin -p
<password> -h -I 17 bmc-te01
ipmipower> debug
debugging is now on
ipmipower> stat
bmc-te01: not discovered
However:
[admin@te-head ~]$ sudo /usr/sbin/ipmipower -D lanplus -u admin -p
<password> -h bmc-te01 -I 17 --stat
bmc-te01: on
I'm also able to hit the BMC with ipmitool:
[admin@te-head ~]$ ipmitool -I lanplus -H bmc-te01 -U admin -P
<password> power status
Chassis Power is on
The "not discovered" error doesn't seem to be documented in the
ipmipower manual page and I haven't been able to find out online
what it means. It is odd that entering "stat" in the ipmipower shell
errs, but using the "--stat" option works fine. This only seems to
happen with these newer Intel Fox Creek Pass boards and not other
boards I have.
For context, conman works with the following config:
SERVER keepalive=ON
SERVER logdir="/var/log/conman"
SERVER logfile="/var/log/conman.log"
SERVER loopback=ON
SERVER
pidfile="/var/run/https://urldefense.com/v3/__http://conman.pid__;!!Bt8fGhp8LhKGRg!BG2PhUDpc-5_EMUFXtI_2vLQzPsdohKTXub4ruPFSll9lzM83_0KczXA1IyNrcUnTxnXeP4SH-JmQFA$
"
SERVER resetcmd="/usr/bin/powerman -0 %N; sleep 5; /usr/bin/powerman
-1 %N"
SERVER tcpwrappers=ON
GLOBAL seropts="115200,8n1"
GLOBAL log="/var/log/conman/console.%N"
GLOBAL logopts="sanitize,timestamp"# IPMI Console\
CONSOLE name="te01" dev="ipmi:bmc-te01"
ipmiopts="U:admin,P:<password>,C:17,W:solpayloadsize"
Is there a way to fix this?
Versions:
ipmipower - 1.6.8
ipmiconsole - 1.6.8
powerman - 2.3.26
Regards,
Devon
_______________________________________________
Freeipmi-users mailing list
Freeipmi-users@gnu.org
https://urldefense.com/v3/__https://lists.gnu.org/mailman/listinfo/freeipmi-users__;!!Bt8fGhp8LhKGRg!BG2PhUDpc-5_EMUFXtI_2vLQzPsdohKTXub4ruPFSll9lzM83_0KczXA1IyNrcUnTxnXeP4SPVaT6yI$
Best,
Devon
--
Al Chu
Livermore Computing
Lawrence Livermore National Laboratory
_______________________________________________
Freeipmi-users mailing list
Freeipmi-users@gnu.org
https://lists.gnu.org/mailman/listinfo/freeipmi-users