XenServer in High Availability Enabled Pool is Unresponsive and Does not Self-Fence

XenServer in High Availability Enabled Pool is Unresponsive and Does not Self-Fence

book

Article ID: CTX129815

calendar_today

Updated On:

Description

A XenServer in a High Availability enabled pool is unresponsive. The Virtual Machines on that host might not work, or are unable to stop, or unable to migrate any Virtual Machines.

Resolution

To resolve this issue, complete the following procedure:

  1. If the server is a member server, run the following commands:
    # xe host-emergency-ha-disable
    #xe-toolstack-restart

  2. Shut down or migrate the virtual machines.

  3. If the master is still in an unresponsive state on a member server, run the following commands:
    xe pool-emergency-transition-to-master
    xe pool-recover-slaves

  4. Run the following command from the old master server:
    pool-emergency-reset-master master-address=<IP ADDRESS of the new master>

  5. If the computer is still in an unresponsive state, restart the computer.
    The pool starts without any issues.

  6. Re-enable High Availability through XenCenter.
    Refer to CTX121708 – How to Configure High Availability in XenServer for more information.


Problem Cause

Sometimes the management interface of the computer functions, but the other NICs or resources stop working. This issue occurs because of the enabling of the C-states. Refer to CTX127395 – Hosts Become Unresponsive with XenServer 5.6 and above on Nehalem and Westmere CPUs for more information. The server does not self-fence and remains in an unresponsive state.

Issue/Introduction

This article contains resolution for XenServer in High Availability Enabled Pool is Unresponsive and Does not Self-Fence.