Manage hosts

Perform this task to connect to, edit, or delete hosts, enable or disable the maintenance mode, or manage host power options.

Enable the maintenance mode for a host

Before maintaining a host, for example, adding memory modules or disks, you can first enable the maintenance mode for the host to prevent server interruption caused by maintenance.

 

·          You can power off or restart a host in maintenance mode and the powered-on host will stay in maintenance mode. ·          You can configure the system to migrate running, suspended, and shutdown VMs that use shared storage to another host upon entering maintenance mode. The auto migration feature does not take effect on VMs that use local storage. ·          Enabling the maintenance mode for a host might cause some VMs to become unavailable. Make sure you are fully aware of the impacts of this operation.

 

To enable the maintenance mode for a host:

1. From the navigation pane, select Data Center > Virtualization > Cluster name > Host name.

2. Click Enter Maintenance Mode.

3. Select whether to migrate running, suspended, or shutdown VMs, and then click OK.

Disable the maintenance mode for a host

After maintenance, you must disable the maintenance mode for the host to be used.

To disable the maintenance mode for a host:

1. From the navigation pane, select Data Center > Virtualization > Cluster name > Host name.

2. Click Exit Maintenance Mode.

3. Click OK.

Add a host to an HA-enabled cluster

Perform this task to add a host recovered from exceptions to an HA-enabled cluster.

To add a host to a cluster:

1. From the navigation pane, select Data Center > Virtualization > Cluster name > Host name.

2. Click Add to HA-Enabled Cluster.

3. Click OK.

Connect to a host

Perform this task to connect a host to Space Console if the host connection terminates because of network or host errors. If the host is already connected, the operation reconnects the host to Space Console.

To connect to a host:

1. From the navigation pane, select Data Center > Virtualization > Cluster name > Host name.

2. Click More, and then click Connect Host.

3. Click OK.

Edit a host

Perform this operation to change the password used by a host to connect to Space Console. The operation also changes the root user password on the host.

 

1. From the navigation pane, select Data Center > Virtualization > Cluster name > Host name.

2. Click More, and then click Edit Host.

3. Enter the current password and the new password, confirm the new password, and then click OK.

Delete a host

·          To delete a host from an HA-enabled cluster, make sure the host is no longer in use or the host is faulty and cannot be repaired. For such a deleted host to operate correctly, you must first re-install Space Console software on the host before adding the host to a cluster. ·          If the system fails to delete a host because of connection errors, reconnect the system to the host and then try again. ·          Before deleting a host, first delete all system images and desktop images from the host. ·          Deleting a host might cause some VMs to become unavailable. Make sure you are fully aware of the impacts of this operation.

 

1. From the navigation pane, select Data Center > Virtualization > Cluster name > Host name.

2. Click More, and then click Delete Host.

3. Click OK.

Shut down a host

Only hosts in maintenance mode support this feature.

To shut down a host:

1. From the navigation pane, select Data Center > Virtualization > Cluster name > Host name.

2. Click More, and then click Shut Down Host.

3. Click OK.

Bulk shut down all hosts

This operation shuts down all hosts in the system and interrupts services. Make sure you are fully aware of the impacts of this operation.

 

1. From the navigation pane, select Data Center > Virtualization.

2. Click the Hosts tab, and then click Shut Down.

3. Select I am fully aware of the impacts of this operation, enter a password, and then click OK.

A system administrator or super administrator enters the password of its account. Any other administrator enters the password of the admin account.

 

Restart a host

Only hosts in maintenance mode support this feature.

To restart a host:

1. From the navigation pane, select Data Center > Virtualization > Cluster name > Host name.

2. Click More, and then click Reboot Host.

3. Click OK.

Wake up a host remotely

You can wake up a shutdown host remotely. Before you wake up a host, configure wakeup parameters.

To wake up a host remotely:

1. From the navigation pane, select Data Center > Virtualization > Cluster name > Host name.

2. Click More, and then click Remote Wakeup.

3. Click OK.

Configure wakeup parameters

1. From the navigation pane, select Data Center > Virtualization > Cluster name > Host name.

2. Click More, and then click Configure Wakeup Parameters.

3. Configure the following parameters, and then click OK:

• Wakeup Mode: Select a wakeup mode.

• Network—Send data packets from a running host to the host to wake up. To use this mode, make sure the target host uses ATX power supply and supports remote wakeup, and the management host has Layer 2 reachability to the target host.

• IPMI—Send a command to the baseboard management controller (BMC) of the host to wake up through Intelligent Platform Management Interface (IPMI). A BMC is an independent module installed on the baseboard of the host. The host uses a dedicated NIC to communicate with the BMC. To use the IPMI node, make sure the target host has a BMC installed and supports IPMI, and the management host has Layer 3 reachability to the BMC of the target host.

• BMC: Enter the IP address of the NIC attached to the BMC. The IP address must be a static address or DHCP-assigned address that has a permanent lease.

• Username: Enter the BMC username.

• Password: Enter the BMC password. Make sure the username and password can be used to power on the target host remotely.

Deploy OVF template

Open Virtualization Format (OVF) defines the open-source VM file format specifications. An OVF template enables VMs to be compatible with different virtualization management platforms. In the current software version, the system supports OVS templates exported from virtualization platforms such as H3C CAS CVM, VMware vSphere, Oracle VM, and ZTE iECS.

Restrictions and guidelines

• The time taken to upload an OVF template mainly depends on the disk space used by the VM image file. Before deploying an OVF template, as a best practice, navigate to the System > Advanced Settings > System Parameters > Basic Parameter Settings page, and set the idle timeout timer for the operator to be longer than the time taken to upload the OVF template. This setting ensures that the OVF template upload will not be interrupted.

• In the current software version, the system does not support deploying an OVF template saved in a disk fragment.

• In the current software version, the system does not support deploying a disk file or an OVF template that is not named correctly. An OVF file name supports only letters, digits, minus signs, underscores, and dots, cannot start with a minus sign or dot, and cannot be all-digits.

• When deploying an OVF template for a VMware vSphere VM or VirtualBox VM, if the VM runs an old operating system (for example, Windows XP), you can edit the registry to enable the operating system to support IDE (PIIX3 or PIIX4), or directly select a VM with good hardware compatibility as the template. In this way, you can avoid the blue screen issues caused by hardware compatibility issues.

• ARM hosts do not support this feature in the current software version.

Procedure

1. From the navigation pane, select Data Center > Virtualization > Cluster name > Host name.

2. Click More, and then click Deploy OVF Template.

3. Upload the OVF file. After the file is successfully uploaded, set the VM alias, CPUs, and memory, and click Next to configure the VM disks.

4. Select the target storage file and bus type for the VM, and click Next to configure the NIC.

5. After completing the configuration, click OK.

Parameters

Basic Info

• Alias: Enter the alias name of the VM.

• CPUs: Set the number of CPU cores assigned to the VM, which is the number of CPUs multiplied by cores per CPU.

• Memory: Specify the memory capacity of the VM.

• Start Now: Configure whether to start the VM immediately after deployment is finished.

Disks

• Target Storage File: Specify a target storage file for the VM.

• Target Storage Pool: Specify a target storage pool for the VM.

• Bus Type: Select a bus type. Options include IDE (the default), SCSI, USB, High-Speed, and High-Speed SCSI. When you deploy an OVF template from another platform, as a best practice, set the bus type to IDE.

NIC

• Network: Select the vSwitch for the image source VM network communication.

• Port Profile: Select a port profile for the VM.

• vFirewalls: Select the vFirewalls for the VM. The incoming and outgoing packets of the VM will be filtered by rules of the selected vFirewalls.

• Network Type: Select a NIC type for the VM. Options include Common NIC, High-Speed NIC, and Intel e1000 NIC. The default NIC type is high-speed NIC, which is CVK driven.

• Bound IPv4/IPv6 Address: Set the IP address bound to the MAC address of the VM. For the NIC to communicate correctly, make sure the IP address assigned to the NIC is the same as the bound IP address.

• Fast Forwarding: Enable the fast forwarding feature. With fast forwarding enabled, a high-speed NIC will be simulated in the CVK kernel as a separate thread to improve the network performance for the VM. This parameter is available when you select High-Speed NIC for the network type, and is enabled by default.

• Queue Count: Set the number of queues for the virtual NIC. The default is 1. Setting more queues can improve the data processing performance for the virtual NIC. The maximum number of queues is the number of vCPUs multiplied by the number of cores. You need to set this parameter after you select High-Speed NIC for the network type and enable fast forwarding.