No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Administrator Guide

OceanStor 2800 V5 V500R007

This document is applicable to OceanStor 2800 V5. Routine maintenance activities are the most common activities for the storage device, including powering on or off the storage device, managing users, modifying basic parameters of the storage device, and managing hardware components. This document is intended for the system administrators who are responsible for carrying out routine maintenance activities, monitoring the storage device, and rectifying common device faults.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Setting VM Failover

Setting VM Failover

Storage systems support VM failover. If a controller fails, VMs can be automatically switched to another functional controller to resume the services.

Prerequisites

Failover takes effect on a VM. When failover is enabled, the peer controller must meet the following requirements:

  • The remaining memory resources meet VM requirements after the failover. To view the remaining memory resources, run show vm_container general. To view the memory resource of the VM to be migrated, run show virtual_machine general vm_id=?.
  • If vCPU isolation is enabled, check whether the remaining number of CPUs in the container meets VM requirements after the failover. You can run show vm_container general to view the remaining number of CPUs in the container and run show virtual_machine general vm_id=? to view the number of vCPUs of the VMs to be migrated.
  • Free network ports exist on the secondary controller and have been added to the VM to be migrated as secondary network ports. To add secondary network ports to the VM, run add virtual_machine secondary_port. Then configure parameters vm_id, port_type, port_id, and primary_port_id to set the VM ID, secondary port type, secondary port ID, and primary port ID.

Context

VM failover uses the cold backup mode. In this mode, services are not used when VMs are started on the peer controller. The following figure shows the process for setting VM failover.

Figure 5-29 Process for setting VM failover

Procedure

  1. Go to the CLI.
  2. Check whether remaining memory resources of the secondary controller meet the migration requirements.

    1. On the CLI, run show vm_container general to view the remaining memory resources.

      NOTE:

      Free memory of VM containers = Total memory of VM containers - VM memory of the active container - Memory of VMs (in the standby container) whose failover function is enabled.

    2. Run the show virtual_machine general vm_id=? command to view the memory resource of the VM to be migrated.

  3. If vCPU isolation is enabled, check whether the remaining number of CPUs in the container meets migration requirements.

    1. Run show virtual_machine vcpu_isolate_switch to check whether vCPU isolation is enabled.

    2. Run show vm_container general to check the number of available CPUs.

    3. Run show virtual_machine general vm_id=? to view the number of vCPUs of the VMs to be migrated.

    The value of CPU Counts must be less than or equal to that of Available CPU Counts.

  4. Add free network ports on the secondary controller to the VM to be migrated as secondary network ports.

    1. Run the show virtual_machine port vm_id=? command to view the used ports.

    2. Run the add virtual_machine secondary_port command to add secondary ports, use parameters vm_id, port_type, port_id, and primary_port_id to specify the VM ID, secondary port type, secondary port ID, and primary port ID.

      When running this command, you can use Ctrl+A to view the available ports.

  5. Run the change virtual_machine general vm_id=? failover_switch=? command. Table 5-45 describes the related parameters.

    Table 5-45 VM failover parameters

    Parameter

    Description

    Value

    vm_id=?

    VM ID

    To obtain the value, run show virtual_machine general without parameters.

    failover_switch=?

    Failover switch

    Possible values are:

    • on: The failover switch is enabled.
    • off: The failover switch is disabled.

  6. Confirm the parameter settings.

    After executing the command, run the show virtual_machine general vm_id=? command to view the status of VM failover.

Example

Enable the failover switch.

admin:/>change virtual_machine general vm_id=1 failover_switch=on  
Command executed successfully.

Follow-up Procedure

After failover is enabled, if the working controller is faulty, VMs fail over to another functional controller. After the faulty controller recovers, the VMs fail back to the controller by default. If failback is disabled, the VMs cannot fail back. You can view and set the switchback mode for VMs as follows:

  1. Run the show virtual_machine failback_switch command to view the switchback mode of VMs.
  2. Run the change virtual_machine failback_switch status=on command to enable failover for VMs.
Translation
Download
Updated: 2019-07-11

Document ID: EDOC1000181576

Views: 19373

Downloads: 31

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next