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

HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

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).
ALM-70126 Residual Orphan VMware VMs

ALM-70126 Residual Orphan VMware VMs

Description

This alarm is generated when a VM exists on vCenter but is deleted from the OpenStack database. This alarm is generated only for heterogeneous VMware VMs.

Attribute

Alarm ID

Alarm Severity

Auto Clear

70126

Major

No

Parameters

Name

Meaning

Fault Location Info

instance_id: specifies the ID of the VM for which the alarm is generated.

Additional Info

  • host_id: specifies the ID of the host accommodating the VM for which the alarm is generated.
  • hypervisor_vm_name: specifies the name of the VM for which the alarm is generated on the VMware hypervisor.

Impact on the System

Orphan VMs may affect the accuracy of the data presented to customers and data statistics.

Possible Causes

  • A backup is created for a database for future restoration. However, after the backup was created, one or more VMs were created. After the database is restored, records of these VMs are deleted from the database, but these VMs reside on vCenter and become orphan VMs.
  • VMs are directly created on vCenter.

Procedure

  1. Query alarm information to obtain the VM ID (instance_id) and VM name in the VMware hypervisor.
  2. Use PuTTY to log in to the first FusionSphere OpenStack node through the IP address of the External OM plane.

    The default user name is fsp. The default password is Huawei@CLOUD8.

    The system supports both password and public-private key pair for identity authentication. If the public-private key pair is used for login authentication, see detailed operations in Using PuTTY to Log In to a Node in Key Pair Authentication Mode.

    NOTE:
    To obtain the IP address of the External OM plane, search for the required parameter on the Tool-generated IP Parameters sheet of the xxx_export_all.xlsm file exported from HUAWEI CLOUD Stack Deploy during software installation. The parameter names in different scenarios are as follows:
    • Region Type I scenario:

      Cascading system: Cascading-ExternalOM-Reverse-Proxy

      Cascaded system: Cascaded-ExternalOM-Reverse-Proxy

    • Region Type II and Region Type III scenarios: ExternalOM-Reverse-Proxy

  3. Run the following command and enter the password of user root to switch to user root:

    su - root

    The default password of user root is Huawei@CLOUD8!.

  4. Run the following command to disable user logout upon system timeout:

    TMOUT=0

  5. Run the following command to import environment variables:

    source set_env

    Information similar to the following is displayed:

      please choose environment variable which you want to import: 
      (1) openstack environment variable (keystone v3) 
      (2) cps environment variable 
      (3) openstack environment variable legacy (keystone v2) 
      (4) openstack environment variable of cloud_admin (keystone v3) 
      please choose:[1|2|3|4] 

  6. Enter 1 to enable Keystone V3 authentication and enter the password of OS_USERNAME as prompted.

    Default account format: DCname_admin; default password: FusionSphere123.

  7. Run the nova show instance_id command to check whether the VM exists.

    • If yes, it is not an orphan VM. In such a case, manually clear the alarm.
    • If no, go to 8.

  8. Log in to vCenter and check whether the VM exists based on the VM name in the VMware hypervisor.

    • If yes, it is an orphan VM. In such a case, go to 9.
    • If no, go to 10.

  9. After confirming that the VM can be deleted, delete it and check whether it is deleted from vCenter.

    • If yes, manually clear the alarm.
    • If no, go to 10.

  10. Contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 46126

Downloads: 33

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