A failure in the fence_cisco_ucs agent opens too many sessions with Cisco UCSM in RHEL 5, 6, or 7 High Availability cluster

Solution Unverified - Updated -


  • The cluster nodes are using fence_cisco_ucs as a fence agent, there was some issue with permissions assigned to fence device user id, due to which the fence operation on cluster node was failing. The repeated failure in fence actions had created too many open sessions on Cisco UCSM due to which it exhausted the maximum number of open sessions allowed by Cisco UCS manager.
May  2 17:13:59 node1 fenced[8321]: fence slot1 dev 0.0 agent fence_cisco_ucs result: error from agent
  • Is there any issue present in fence_cisco_ucs agent due to which it leaves the session open even when the fence operation is failed?


  • Red Hat Enterprise Linux (RHEL) 5, 6, and 7 with the High Availability Add On
  • fence-agents-cisco-ucs releases prior to 4.0.11-10.el7 in RHEL 7
  • All fence-agents releases in RHEL 6
  • All cman releases in RHEL 5
  • fence_cisco_ucs as fence agent

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