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

eSight V300R010C00 Maintenance Guide 07

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-505001001 CPU Usage Is High

ALM-505001001 CPU Usage Is High

Description

The maintenance tool continuously samples the central processing unit (CPU) usage of the server. This alarm is generated when the CPU usage sampled each time in a sampling period is greater than or equal to the alarm generation threshold (90%). This alarm is automatically cleared if the CPU usage is less than or equal to the alarm clearance threshold (70%) in a sampling period.

NOTE:
  • Sampling period = Sampling times x Sampling interval, the sampling period is 80s (80 = 8x10).
  • If a server has multiple CPUs, the maintenance tool continuously samples the usage of each CPU.
  • In a distributed system, the maintenance tool continuously samples the CPU usage of each eSight server.

Attribute

Alarm ID

Alarm Severity

Alarm Type

505001001

Major

Quality of service alarm

Parameters

Name

Meaning

Server name

Name of the server for which the alarm is generated.

Server IP address

Internet Protocol (IP) address of the server for which the alarm is generated.

Threshold

Threshold for generating an alarm.

Clearance threshold

Threshold for clearing an alarm.

Usage

CPU usage of the server.

Impact on the System

  • The eSight responds slowly, and operations time out.
  • The real-time reporting from the northbound module, performance module, and fault module times out, and the information cannot be collected in time.
  • The system processes services slowly. As a result, messages may be accumulated.

Possible Causes

  • The eSight is busy temporarily.
  • The alarm generation threshold for the CPU usage of the eSight server is set improperly.
  • The eSight server is performing an operation that occupies many system resources or takes a long time.
  • The hardware performance of the server is low. Therefore, the eSight cannot run properly.

Procedure

  1. Check whether the eSight is busy temporarily.

    1. Choose Fault > Current Alarms from the main menu.
    2. On the Current Alarms page, view First Occurrence Time of the alarm.

      Meanwhile, Check whether one of the following situations exist:

      • The alarm is not consecutively generated, and is automatically cleared in ten minutes. In addition, the alarm is seldom generated. It is generated once each day at most.
      • The alarm affects the system running (including the northbound interface operations, performance statistics collecting, alarm reporting, and user operations) slightly or for a short time. The performance delay does not exceed a period, the alarm delay does not exceed 30 seconds, and the graphical user interface (GUI) response takes less than 10 seconds. In addition, the alarm is automatically cleared in 30 minutes.
      • When the high CPU usage alarm is generated, a large number of alarms or events are reported (this is not a mandatory condition).

        Check whether one of the preceding conditions is met.

      • If yes, go to Step 1.3.
      • If no, go to Step 3.
    3. Wait five minutes. In the current alarm list, check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to Step 2.

  2. Check whether the alarm generation threshold for the CPU usage of the eSight server is set improperly.

    1. Contact the administrator to check whether the alarm generation threshold for the CPU usage of the server is set improperly.
      • If yes, contact the administrator for troubleshooting or go to Step 6.
      • If no, go to Step 3.
    2. Wait five minutes. In the current alarm list, check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to Step 3.

  3. Check whether the CPU usage of the eSight application programs is greater than 90%.

    1. On the maintenance tool client, choose System > System Monitoring from the main menu.
    2. In the System Monitoring window, choose Look > Process from the navigation tree.
    3. On the Process tab page, check whether the CPU usage of the eSight process exceeds 90%.
      • If yes, the memory is exhausted due to the eSight application. Wait until the related service is processed. Then, go to Step 3.4. If the service has not completed within a long period of time, go to Step 6.
      • If no, go to Step 4.
    4. Wait five minutes. In the current alarm list, check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to Step 4.

  4. Check whether the CPU usage of the non-eSight application programs is greater than 90%.

    1. Contact the administrator to check whether the CPU usage of the non-eSight application programs is greater than 90%.
      • On Linux, you can run the top command to check the CPU usage of a process in the CPU column.
      • On Windows, you can click the Process tab in Windows Task Manager, and check the process CPU usage in the CPU column.
      • If yes, contact the administrator for troubleshooting. After the administrator processes it, go to Step 4.2. If you cannot wait for the administrator to process it, go to Step 6.
      • If no, go to Step 5.
    2. Wait five minutes. In the current alarm list, check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to Step 5.

  5. Check whether hardware performance of the server is low and the hardware does not support the running of the eSight.

    1. Contact the administrator to check whether the hardware performance of the server is low.

      If hardware performance of the server is low:

      • The hardware requirements corresponding to the management scope of the eSightare beyond the actual hardware capability of the server.
      • The alarm is generated consecutively or frequently.

        Check whether any of the preceding two symptoms appears.

      • If yes, contact the administrator for troubleshooting. After the administrator processes it, go to Step 4.2. If you cannot wait for the administrator to process it, go to Step 6.
      • If no, go to Step 6.
    2. Wait five minutes. In the current alarm list, check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to Step 6.

  6. Collect the information about alarm handling, and contact the technical support personnel.

Clearing

When the fault is eliminated, the system will auto-clear the alarm. Manual clearing is not required.

The following situations cause failures in automatically clearing alarms. Instead, they need to be cleared manually.

  • The name and IP address of the host for which this alarm is generated are changed.
  • The server that generates the alarm is not monitored.
  • Active/standby switchover occurs in a high-availability system.

Related Information

None.

Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 24842

Downloads: 74

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