A Host was fenced due to Network Problems

Solution Verified - Updated -

Issue

  • Fence issue
  • A host was fenced from the RHEV cluster by another host
  • The host returned to an available state
  • Server failed to respond
  • Host from CLUSTER was choosen as a proxy to execute Restart command
  • Host was stopped by Engine
  • Host was started by Engine
  • Host goes in Non-Responsive state with message in the Event logs
Host <host-name> is non-responsive.
  • Messages in engine.log
No route to host

Environment

  • Red Hat Virtualization 4.x

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