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-15032 Failed in Link Check

ALM-15032 Failed in Link Check

Alarm Description

This alarm is reported when the current system contains invalid links. You are advised to check the status of related links and nodes to rectify potential faults.

Attribute

Alarm ID

Alarm Severity

Alarm Type

15032

Warning

Communications alarm

Alarm Parameters

Parameter

Description

additional

Specifies the head node and tail node of an abnormal link.

locationinfo

Specifies the location information, including the IP address and service type of the end node of the abnormal link.

Impact on the System

The APIServer, LB server, Rest, and Manager nodes of the current system are configured in active/standby mode. In the location information, you can identify the IP address and service type of the end node of the abnormal link. When the link of a single node of the same type is abnormal, the system can still work properly, but you are advised to rectify the fault in time.

Possible Causes

The related services of the end node of the link are faulty or are stopped manually.

Procedure

  1. Log in to the node where the link is abnormal.

    • Region Type III scenario
      1. Use PuTTY to log in to the manage_lb1_ip node.

        The default username is paas, and the default password is QAZ2wsx@123!.

      2. Run the following command to log in to the abnormal node:

        ssh x.x.x.x

        NOTE:

        In the proceeding command, the x.x.x.x indicates the IP address of the node where the link exception alarm is generated.

    • Region Type I and Region Type II scenarios
      1. Use PuTTY to log in to the manage_lb1_ip node.

        The default username is paas, and the default password is QAZ2wsx@123!.

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

        su - root

        Default password: QAZ2wsx@123!

      3. Run the following command to obtain the project ID:

        kubectl get node | grep dms

        2a10ea7fa79949e79f59d7385268cd3a   dms-np-lvs-33bd8778-cshnf                    Ready     <none>    5d        v2.3.27-FusionStage6y

        In the preceding information, the content in bold is the obtained project ID.

      4. Run the following command to obtain the node name of the manage-lb node:

        kubectl get po -n 2a10ea7fa79949e79f59d7385268cd3a -owide | grep x.x.x.x

        NOTE:

        In the proceeding command, the x.x.x.x indicates the IP address of the node where the link exception alarm is generated.

        dms-kafka-33bd8778-d4fc89c44-ncdgc                1/1       Running   0          5d        192.168.254.114   dms-np-kafka-zk-mgr-33bd8778-w5j7s
        dms-manager-33bd8778-967476ffb-dsfkq              1/1       Running   0          5d        192.168.254.114   dms-np-kafka-zk-mgr-33bd8778-w5j7s
        dms-zookeeper-33bd8778-64b85b4c8d-8hmbt           1/1       Running   0          5d        192.168.254.114   dms-np-kafka-zk-mgr-33bd8778-w5j7s

        In the proceeding information, the content in bold indicates the node name.

      5. Run the following command to obtain the IP address of the abnormal node:

        kubectl get node -owide | grep dms-np-kafka-zk-mgr-33bd8778-w5j7

        In the preceding command, dms-np-kafka-zk-mgr-33bd8778-w5j7 is the node name obtained in 1.d.

        2a10ea7fa79949e79f59d7385268cd3a   dms-np-kafka-zk-mgr-33bd8778-w5j7s           Ready     <none>    5d        v2.3.27-FusionStage6.5.RP3-B100-dirty   10.64.0.80    EulerOS 2.0 (SP5)   3.10.0-862.14.0.1.h85.eulerosv2r7.x86_64   docker://1.11.2

        In the proceeding information, the part in bold indicates the IP address of the public network where the link is abnormal.

      6. Run the following command to log in to the node where the link is abnormal:

        ssh 10.64.0.80

        In the preceding command, 10.64.0.80 indicates the public network IP address of abnormal link obtained in 1.e.

  2. View the logs of the abnormal service in the /opt/paas/middleware/log/dms/ directory and analyze the causes of the service exception:
  3. If you cannot get the causes of service exception based on log analysis, contact technical support.

Alarm Clearing

After the fault is rectified, the system automatically clears the alarm.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 46452

Downloads: 33

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