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-1200053 Failed to Make Calls to the Neutron API

ALM-1200053 Failed to Make Calls to the Neutron API

Description

The system checks the communication between VPC service nodes and FusionSphere OpenStack nodes every 30 seconds. This alarm is generated if communication failures are detected for three consecutive times.

Attribute

Alarm ID

Alarm Severity

Auto Clear

1200053

Major

Yes

Parameters

Parameter

Description

Alarm Name

Indicates the alarm name.

Source Device

Indicates the device for which the alarm is generated.

Monitoring System

Indicates the type of the interconnected system.

Source System

Indicates the name of the interconnected system.

IP Address

Indicates the IP address of the ECS instance for which the alarm is generated.

Last Occurred At

Indicates the time when the alarm was generated for the last time.

Location Information

Indicates the information required to locate the alarm.

Additional Information

Provides supplementary information about the alarm.

Impact on the System

The VPC service nodes cannot communicate with FusionSphere OpenStack nodes, leading to network configuration failures.

Possible Causes

  • The network for VPC service nodes is interrupted.
  • A FusionSphere OpenStack Neutron service exception occurred.

Procedure

  1. Check whether the alarm results from a FusionSphere OpenStack Neutron service exception by making reference to ALM-73203 Component Fault and ALM-73201 HAProxy Backend Services Fault.

    • If yes, rectify the fault as described in the corresponding section:
    • If no, the network for VPC service nodes may be interrupted. In this case, go to 2.

  2. Log in to ManageOne Maintenance Portal using a browser.

    • URL: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943
    • Default username: admin; default password: Huawei12#$

  3. Click Log In.
  4. On the menu bar in the upper part of the page, choose Alarms.
  5. In the alarm list, locate and click the target alarm name in the Name column. The alarm details and proposed processing actions dialog box is displayed.
  6. In the Basic Information list of the Alarm Details and Handling Recommendations dialog box, locate Location Info. The value of Host IP address in Location Info is the IP address of the node for which the alarm is generated.
  7. Use PuTTY to log in to the node for which the alarm is generated.

    The default username is vpc. The default password is Huawei12#$.

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

    TMOUT=0

  9. Run the following command to obtain the neutron domain name:

    cat /home/vpc/network/WEB-INF/classes/config/networkConfig.xml | grep neutron-endpoint

    The following command output is displayed.

  10. Run the following command to ping the obtained neutron domain name:

    ping network.az1.dc1.type2.uniontest.com

    The following command output is displayed.

    [vpc@PUB-SRV01 ~]$ ping network.az1.dc1.type2.uniontest.com
    PING network.az1.dc1.type2.uniontest.com (192.168.102.50) 56(84) bytes of data.
    64 bytes from 192.168.102.50 (192.168.102.50): icmp_seq=1 ttl=63 time=0.151 ms
    64 bytes from 192.168.102.50 (192.168.102.50): icmp_seq=2 ttl=63 time=0.195 ms
    64 bytes from 192.168.102.50 (192.168.102.50): icmp_seq=3 ttl=63 time=0.196 ms
    ^C
    --- network.az1.dc1.type2.uniontest.com ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2001ms
    rtt min/avg/max/mdev = 0.151/0.180/0.196/0.026 ms
    • If the neutron domain name cannot be pinged, perform the operations in 11 to check whether the DNS configuration of the current node is correct.
    • If the neutron domain name can be pinged, contact technical support for assistance.

  11. Check whether the DNS configuration of the current node is correct:

    1. Run the following command to check the DNS configuration:

      cat /etc/resolv.conf | grep nameserver

      The following command output is displayed.

      [vpc@PUB-SRV01 ~]$ cat /etc/resolv.conf | grep nameserver
      nameserver 192.168.109.124
      nameserver 192.168.109.125
    2. Compare the obtained information with the DNS-Internal node information in the LLD document.
      • If the obtained information is different from the information described in the LLD document, modify the resolv.conf file based on the information in the LLD document.
      • If the obtained information is the same as the information described in the LLD document, the DNS configuration is correct. In this case, contact technical support for assistance.
    3. Run the following command and enter the password of the root user to change the DNS configuration:

      sudo vim /etc/resolv.conf

    4. Press Insert and edit the file content as required.
    5. Press Esc, enter :wq, and press Enter to save the changes made to this file.
    6. Try to ping the neutron domain name again. If the ping operation still fails, contact technical support for assistance.

  12. Use PuTTY to log in to a FusionSphere OpenStack node.

    The default username is fsp. The default password is Huawei@CLOUD8.

  13. Import environment variables.

    For details, see section Importing Environment Variables.

  14. Replace the domain name in the following command with the neutron domain name obtained in 9 and run the command:

    curl -i --insecure -X GET 'https://network.az1.dc1.type2.uniontest.com:443/ ' -H "Accept: application/json"

    The following command output is displayed.

    If the return code is not 200, contact technical support for assistance.

  15. After 3 minutes, check whether the alarm is automatically cleared.

    • If the alarm is cleared, no further action is required.
    • If the alarm persists, contact technical support for assistance.

Alarm Clearance

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

Reference

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 34565

Downloads: 31

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