Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • Pacemaker cluster (stonith:fence_idrac) device is stopped whenever there is a configuration task carried out in network switch

    Posted on

    Hi,

    We have a Red hat failover cluster with pacemaker which has two nodes with iDRAC as the fencing device. However, when there is a any kind of configuration change in Network switch side fencing resources get stopped.

    +++++++++++++++++++++++++++++++++++++++++++++++++
    * node01 (stonith:fence_idrac): Stopped
    * node02 (stonith:fence_idrac): Started ime-prod-app01
    * Clone Set: ping-clone [ping]:
    * Started: [ ime-prod-app01 ime-prod-app02 ]

    Failed Resource Actions:
    * node01_start_0 on ime-prod-app02 'OCF_TIMEOUT' (198): call=594, status='Timed Out', exitreason='', last-rc-change='2021-03-20 02:35:25 +05:30', queued=0ms, exec=20137ms

    Failed Fencing Actions:
    * reboot of ime-prod-app01 failed: delegate=ime-prod-app02, client=pacemaker-controld.14605, origin=ime-prod-app02, last-failed='2021-03-20 03:51:34 +05:30'

    ++++++++++++++++++++++++++++++++++++++++++++++++++
    [root@ime-prod-app02 log]#
    [root@ime-prod-app02 log]# pcs stonith show node01
    Warning: This command is deprecated and will be removed. Please use 'pcs stonith config' instead.
    Resource: node01 (class=stonith type=fence_idrac)
    Attributes: cipher=3 ipaddr=172...20 lanplus=on login=root method=cycle passwd=XXXX pcmk_host_list=ime-prod-app01 pcmk_monitor_retries=10 pcmk_monitor_timeout=120s
    Operations: monitor interval=120s (node01-monitor-interval-120s)
    [root@ime-prod-app02 log]# pcs stonith show node02
    Warning: This command is deprecated and will be removed. Please use 'pcs stonith config' instead.
    Resource: node02 (class=stonith type=fence_idrac)
    Attributes: cipher=3 delay=20 ipaddr=172...21 lanplus=on login=root method=cycle passwd=xxxx pcmk_host_list=ime-prod-app02 pcmk_monitor_retries=10 pcmk_monitor_timeout=120s
    Operations: monitor interval=120s (node02-monitor-interval-120s)
    [root@ime-prod-app02 log]#

    +++++++++++++++++++++++++++++++++++++++++++++

    Are there some parameters that we need to adjust?
    What does it mean by "Failed Fencing Actions"?

    Thanks,
    Dinaj

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2026 Red Hat