13.3.3. Manually Fencing or Isolating a Host

If a host unpredictably goes into a non-responsive state, for example, due to a hardware failure; it can significantly affect the performance of the system. You can reboot the host server manually, in order to isolate storage and networking issues.


At least one host must be up and running in the data center to test fencing. Do not attempt to test the first host that is added to a data center, until at least one other host is up and running.

To manually fence a non-responsive host:

  1. On the Hosts tab, select the host. The status must display as Not Responding.
  2. Manually reboot the host. This could mean physically entering the lab and rebooting the host.
  3. On the Administration Portal, right click the host entry and select the Confirm Host has been rebooted button.
    The Host Right-click menu

    Figure 13.3. The Host Right-click menu

  4. 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.
  5. The host to be fenced is isolated from the virtualized system, enabling any of its functions to be automatically transferred to an active host.
  6. After the non-responsive host is rectified, and is reinstalled or rebooted, click the Activate button to restore the host status to Up.