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-38017 PSM Unavailable

ALM-38017 PSM Unavailable

Description

This alarm is reported when access to PSM is abnormal.

Attribute

Alarm ID

Alarm Severity

Alarm Type

38017

Major

Communications alarm

Parameters

Parameter Name

Parameter Description

ServiceName

Indicates the name of the service that reports the alarm.

NameSpace

Indicates the namespace of the service that reports the alarm.

InstanceName

Indicates the name of the service instance for which the alarm is reported.

SrvAddr

Indicates the access address of the service that reports the alarm.

Impact on the System

The PSM functions are unavailable.

System Actions

None

Possible Causes

  • PSM is abnormal.
  • The network connection between the application and PSM is abnormal.

Procedure

  1. Query the location and additional information of the alarm.
  2. Check the pod status of PSM.

    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 Kubernetes command to check whether the pod status of PSM is normal.

      kubectl get pod -owide -n fst-manage | grep psm

      The parameter following -n indicates the value of namespace in the location information in 1.

    4. Check whether the pod status of PSM is normal.

      If the pod status of PSM is Running, the pod status of PSM is normal.

      • If yes, go to 3.
      • If no, go to 2.g.
    5. If the pod status of PSM is abnormal, perform either of the following operations:
      • Wait for the healthcheck service to restart. This process takes approximately 10 minutes.
      • Run the following command to manually restart the pod on which abnormal PSM service runs:

        kubectl deletepod podname -n fst-manage

        The parameter following -n indicates the value of namespace in the location information in 1.

        For details about podname, see 2.c.

    6. Check whether the pod status of PSM is normal again.
      • If yes, go to 2.g.
      • If no, go to 4.
    7. Check whether this alarm has been cleared.
      • If yes, no further action is required.
      • If no, go to 3.

  3. Check whether the network status is normal.

    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 Kubernetes command to view the PSM container IP address.

      kubectl get pod -owide -n fst-manage | grep psm

      The parameter following -n indicates the value of namespace in the location information in 1.

    4. Run the following command to check whether the network connection between PSM and the application is normal:

      curl -k https://${IP address of Cluster Manager queried in 3.c}:9445

      If the command output is displayed, the network connection is normal.

      • If yes, go to 4.
      • If no, contact the network administrator to rectify the fault.
    5. After the fault is rectified, check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to 4.

  4. Contact technical support.

Alarm Clearing

This alarm will be automatically cleared after the fault is rectified.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 47699

Downloads: 33

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