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-73410 CPU Usages of UVP Key Processes Exceed the Thresholds

ALM-73410 CPU Usages of UVP Key Processes Exceed the Thresholds

Description

This alarm is generated when the CPU usages of key UVP processes exceed the thresholds.

Attribute

Alarm ID

Alarm Severity

Auto Clear

73410

Minor

Yes

Parameters

Name

Meaning

Name

Specifies the alarm name.

Object ID

Specifies the alarm object ID.

If an alarm is generated for a resource, such as a host or VM, the value is the resource ID, for example, the host ID. If an alarm is generated for a service module, the value is the ID of the service module, for example, FusionSphere OpenStack OM.

Object Type

Specifies the alarm object type. Example values: host and heart beat (indicating the heartbeat detection system).

Object Name

Specifies the object for which the alarm is generated.

If an alarm is generated for a resource, such as a host or VM, the value is the resource name, for example, the host name. If the alarm is generated for a service module, the value is the name of the service module, for example, FusionSphere OpenStack OM.

Component Type

Specifies the type of the component that reports the alarm, for example, FusionSphere OpenStack or FusionSphere OpenStack OM.

Component

Specifies the component that reports the alarm.

Fault Location Info

Provides detailed information about the alarm object, usually in the form of key value pairs. For example: host=*****,portName=###, indicating that the alarm is generated on port ### of host ****.

Additional Info

Provides additional information about the alarm, usually in the form of key value pairs. For example: Threshold=70,current_value=75, indicating that the alarm is generated because the threshold is 70 and the current value is 75.

Generated At

Specifies the time when the alarm is generated.

Cleared At

Specifies the time when the alarm is cleared.

Clearance Type

Specifies how the alarm is cleared (manually or automatically).

Cleared By

Specifies the name of the user who clears the alarm. This parameter is left blank if the alarm is automatically cleared.

Alarm Clearance User ID

Specifies the ID of the user who clears the alarm. This parameter is left blank if the alarm is automatically cleared.

Alarm Cleared At

Specifies the system view (tenant view or administrator view) in which the alarm is manually cleared.

SN

Specifies the sequence number of the alarm.

Impact on the System

The UVP management overheads have increased, which deteriorates management performance.

Possible Causes

UVP management processes are busy.

Procedure

  1. Check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, go to 2.

  2. Use PuTTY to log in to a FusionSphere OpenStack controller node.

    Ensure that the reverse proxy IP address and username fsp are used to establish the connection.

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

    su - root

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

    TMOUT=0

  5. Import environment variables. For details, see Importing Environment Variables.
  6. Run the cps host-list command to query the management IP address of the host in the alarm details.
  7. Run the following commands to log in to the host for which the alarm is generated:

    su - fsp

    ssh fsp@HOST_MANAGE_IP

    Enter the system private key password as prompted. The default password is Huawei@CLOUD8!. If you have successfully replaced the public and private key files, enter the new private key password. Alternatively, press Enter and enter the password of user fsp.

    Then, run the su - root command to switch to user root.

  8. Perform the required operation based on the abnormal process name obtained from the extended alarm information.

    • If the process name is libvirtd, go to 9.
    • If the process name is hirmd, vBMC_agentd, UVPHostd, virtlogd, systemd-journal, dbus-daemon, rsyslogd, sysalarm, sysmonitor, or getosstat, go to 10
    • If the process name is systemd, go to 11.
    • If the process name is ovs-vswitchd or ovsdb-server, go to 12.

      When the CPU usage of the ovs-vswitchd process exceeds the threshold, the system collects the EVS MAC entries and port-core binding information and records the information in the key process monitoring log /var/log/sysmonitor/process_monitor.log.

    • If the process name is a VM name, go to 12.

  9. Use the PuTTY to log in to the host. Then execute the virsh event --all command to receive the libvirtd service event. Wait for 1 minute. Then press Ctrl+C to stop receiving the libvirtd service event and check whether more than 15 events are received.

    • If yes, stop performing VM lifecycle management operations on the host and perform the step again.
    • If no, go to 10.

  10. Use PuTTY to log in to a host and run the following command to restart the process service. After 30 seconds, check whether the alarm is automatically cleared.

    systemctl restart ${SERVER_NAME}
    NOTE:

    ${SERVER_NAME} indicates the name of the service corresponding to the process.

    You need to re-specify ${SERVER_NAME} for the following processes:

    • systemd-journal, corresponding to the systmed-journald service
    • dbus-daemon, corresponding to the dbus service
    • rsyslogd, corresponding to the rsyslog service
    • If yes, no further action is required.
    • If no, go to 13.

  11. Use PuTTY to log in to the host. Then run the following command to re-load systemd (wait for 30s and check whether the alarm is automatically cleared):

    systemctl daemon-reload
    • If yes, no further action is required.
    • If no, go to 13.

  12. Run the uvplog -o host -t hyp command to collect logs and contact Huawei technical support.
  13. Contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 48368

Downloads: 33

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