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 Enterprise Virtualization (RHEV) 3.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.