fence_cisco_ucs fails with "fenced[xxxx]: fence node1 dev 0.0 agent fence_cisco_ucs result: error from agen?

Solution Unverified - Updated -

Issue

  • Red Hat High Availability cluster failed to fence two unresponsive hosts. Two hosts in a UCS domain appeared to have gone into a non-responsive state, however they failed to be restarted. Following messages observed around the same time:
Mar 28 10:39:00 node1 fenced[6535]: fencing node node2
Mar 28 10:39:05 node1 fenced[6535]: fence node2 dev 0.0 agent fence_cisco_ucs result: error from agent
Mar 28 10:39:05 node1 fenced[6535]: fence node2 failed

Environment

  • Red Hat Enterprise Linux 6.6
  • fence_cisco_ucs agent configuration is as below:
<fencedevice agent="fence_cisco_ucs" ipaddr="x.x.x.x" login="user" name="node1_fence" passwd="password" suborg="org-RHEL"/>

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content