[RHEV 2.2] Procedure for manual fencing
Environment
- Red Hat Enterprise Virtualization 2.2
Issue
Procedure for what to do for manual fencing.
Resolution
To manually fence a non-responsive host
-
Click the Hosts tab. If a host is not displayed.
-
Select the host. The status must display as Not Responding.
-
Manually reboot the host.For example, this could mean physically entering the lab and rebooting the host.
-
In the Red Hat Enterprise Virtualization Manager, right click and select the Confirm Host has been rebooted button.
-
A message displays prompting you to ensure that the host has been shut down or rebooted. Select the Approve Operation check box and click OK.
- The host to be fenced is isolated from the virtualized system, enabling any of its functions to be automatically transferred to an active host.
- After the non-responding host is rectified, and is reinstalled or rebooted, click the Activate button to restore the host status to Up.
Root Cause
If a host unpredictably goes into an unresponsive state, for example, due to a hardware failure; it can significantly affect the performance of the system. For example, if the unresponsive host is the Storage Pool Manager, Red Hat Enterprise Virtualization Manager needs to move this function to an active host. Administrators can isolate a non-reponsive host from networked storage, and other hosts by manually rebooting the host. Once the administrator has manually rebooted the host, click the Confirm Host has been Rebooted option on the right-click submenu, to indicate to the platform that the host has been manually rebooted.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.