© 2017 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public.
Page 20 of 146
3. Test the function.
mgmtsrv01:/tftpboot # ipmitool -I lanplus -U admin -P admin -H 172.23.1.101
power status
Chassis Power is off
mgmtsrv01:/tftpboot # ipmitool -I lanplus -U admin -P admin -H 172.23.1.101
power on
Chassis Power Control: Up/On
mgmtsrv01:/tftpboot # ipmitool -I lanplus -U admin -P admin -H 172.23.1.101
power status
Chassis Power is on
mgmtsrv01:/tftpboot #
Configure Clustering with IPMI as Fencing Device
If you don’t have a STONITH Block Devices (SBD) option to configure because of legging on shares Fibre Channel
disks of a RHEL 6 installation, IPMI is also an valid option which can be configured.
The STONITH configuration with IPMI for SLES is shown here.
Note:
The
server01-ipmi
and
server02-ipmi
parameters refer to the BMC IP address. Add those entries in the
/etc/hosts file of both nodes.
server01:~ # crm configure
crm(live)configure#
primitive STONITH-Server01 stonith:external/ipmi op monitor
interval="0" timeout="60s" op monitor interval="300s" timeout="60s" on-
fail="restart" op start interval="0" timeout="60s" on-fail="restart" params
hostname="server01" ipaddr="server01-ipmi" userid="admin" passwd="admin"
interface="lanplus"
crm(live)configure#
primitive STONITH-Server02 stonith:external/ipmi op monitor
interval="0" timeout="60s" op monitor interval="300s" timeout="60s" on-
fail="restart" op start interval="0" timeout="60s" on-fail="restart" params
hostname="server11" ipaddr="server02-ipmi" userid="admin" passwd="admin"
interface="lanplus"
crm(live)configure#
location LOC_STONITH_Server01 STONITH-Server01 -inf:
server01
crm(live)configure#
location LOC_STONITH_Server02 STONITH-Server02 -inf:
server02
