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

CloudEC V600R019C00 Troubleshooting (Enterprise On-premises, Convergent Conference)

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).
Anti-Affinity Rule for VMs Does Not Take Effect

Anti-Affinity Rule for VMs Does Not Take Effect

Symptom

An anti-affinity rule is set for the two virtual machines (VMs) during the installation. However, after the two VMs are started, they are running on the same host, as shown in Figure 3-1.

NOTE:
This section takes CGPOMU_90_180_omu_omu1_0 and CGPOMU_90_180_omu_omu1_1 as an example to illustrate how to identify and resolve this issue.
Figure 3-1 CGPOMU_90_180_omu_omu1_0 and CGPOMU_90_180_omu_omu1_1 running on the same host

NOTE:
You can configure either an affinity rule or an anti-affinity rule for two VMs when installing them.
  • Affinity: Two VMs are running on one host.
  • Anti-affinity: Two VMs are running on separate hosts.

To prevent service failures caused by host faults, it is recommended that you configure an anti-affinity rule for two VMs in active/standby or load-sharing mode.

Possible Causes

  • CPU and memory resources on hosts are insufficient.
  • Setting the anti-affinity rule failed.

Fault Diagnosis

  • CPU and memory resources on hosts are insufficient.
    1. Log in to the vCenter and choose Inventory > Hosts and Clusters. In the navigation tree on the left pane, select other hosts in the cluster containing the host running CGPOMU_90_180_omu_omu1_0 and CGPOMU_90_180_omu_omu1_1 in sequence. Then, on the Summary tab of the right pane, check the available CPU and memory resources on these hosts, as shown in Figure 3-2.
      Figure 3-2 Checking available CPU and memory resources on hosts

    2. In the navigation tree on the left pane, select CGPOMU_90_180_omu_omu1_0 and CGPOMU_90_180_omu_omu1_1 in sequence. Then, on the Resource Allocation tab of the right pane, check the reserved CPU and memory resources for these two VMs, as shown in Figure 3-3.
      Figure 3-3 Checking reserved CPU and memory resources for CGPOMU_90_180_omu_omu1_0 and CGPOMU_90_180_omu_omu1_1

    3. Check whether the available resources on each host are more than the reserved resources for the two VMs. If the available resources on each host are less than the reserved resources for the two VMs, the VMware will automatically deploy the two VMs on a host with sufficient resources. To resolve this issue, perform the operations in 1.
  • Setting the anti-affinity rule failed.
    1. Open the VNFD file and check whether an anti-affinity rule is set for CGPOMU_90_180_omu_omu1_0 and CGPOMU_90_180_omu_omu1_1. If the information in the VNFD file is similar to that shown in Figure 3-4, an anti-affinity rule is set for CGPOMU_90_180_omu_omu1_0 and CGPOMU_90_180_omu_omu1_1.
      Figure 3-4 Anti-affinity rule between CGPOMU_90_180_omu_omu1_0 and CGPOMU_90_180_omu_omu1_1

      NOTE:
      The value of affinity may be any of the following:
      • distinct: A single VM must be deployed on an independent host.
      • n: A configurable number of VMs can be deployed on an independent host.
      • none: There are no restrictions on the VM deployment.
    2. Choose Inventory > Hosts and Clusters. In the navigation tree on the left pane, right-click the cluster where CGPOMU_90_180_omu_omu1_0 and CGPOMU_90_180_omu_omu1_1 reside and choose Edit settings from the shortcut menu. If information similar to that shown in Figure 3-5 is displayed, setting of an-affinity rule for the two VMs failed. To resolve this issue, perform the operations in 3.
    Figure 3-5 An-affinity rule setting for CGPOMU_90_180_omu_omu1_0 and CGPOMU_90_180_omu_omu1_1

  • If this issue occurs for other reasons, perform the operations in 5.

Procedure

    Rectify CPU and memory resources on hosts.

    1. Contact infrastructure maintenance engineers to add a host with sufficient resources for CGPOMU_90_180_omu_omu1_0 and CGPOMU_90_180_omu_omu1_1 to the cluster where these two VMs reside. Migrate CGPOMU_90_180_omu_omu1_0 or CGPOMU_90_180_omu_omu1_1 to the new host.
    2. Check whether the anti-affinity rule for CGPOMU_90_180_omu_omu1_0 and CGPOMU_90_180_omu_omu1_1 takes effect.

      • Yes: No further action is required.
      • No: Go to 5.

    Setting the anti-affinity rule failed.

    1. Contact infrastructure maintenance engineers to set an anti-affinity rule for CGPOMU_90_180_omu_omu1_0 and CGPOMU_90_180_omu_omu1_1. Then, migrate CGPOMU_90_180_omu_omu1_0 or CGPOMU_90_180_omu_omu1_1 to another host.
    2. Check whether the anti-affinity rule for CGPOMU_90_180_omu_omu1_0 and CGPOMU_90_180_omu_omu1_1 takes effect.

      • Yes: No further action is required.
      • No: Go to 5.

    Contact Huawei technical support engineers.

    1. Use the Information Collection Tool to collect information about Common fault analysis scenario.
    2. Contact Huawei technical support engineers.

Related Information

None.

Translation
Download
Updated: 2019-08-07

Document ID: EDOC1100059098

Views: 26112

Downloads: 12

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next