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-1200074 VPC Database Access Failed

ALM-1200074 VPC Database Access Failed

Description

The system checks the connection status between VPC service nodes and VPC database nodes every 60 seconds. This alarm is generated if the connection is interrupted.

Attribute

Alarm ID

Alarm Severity

Auto Clear

1200074

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

VPC service nodes cannot access VPC database nodes. As a result, the VPC service becomes unavailable.

Possible Causes

  • The network for VPC service nodes is interrupted.
  • The VPC database service is abnormal.

Procedure

  1. Log in to the ManageOne OM plane using a browser.

    • URL: https://Address for the homepage of the ManageOne OM plane:31943. For example: https://oc.type.com:31943.
    • Default username: admin, default password: Huawei12#$.

  2. Click Login.
  3. On the menu bar in the upper part of the page, choose Alarms.
  4. 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.
  5. 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.
  6. Use PuTTY to log in to the node for which the alarm is generated.

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

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

    TMOUT=0

  8. Run the following command to obtain the database address:

    cat /home/vpc/network/WEB-INF/classes/config/extension.properties |grep network.db.url

    Information similar to the following is displayed. Record the database address 192.168.109.50:5432.

    network.db.url=jdbc\:postgresql\://192.168.109.50:5432/vpc?use_boolean\=true

  9. Use PuTTY to log in to the PUB-DB-01 or PUB-DB-02 node (VPC DB node).

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

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

    TMOUT=0

  11. Run the ifconfig command to check whether the floating IP address is consistent with the obtained address.

    Information similar to the following is displayed.

    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
            inet 192.168.109.123  netmask 255.255.255.0  broadcast 192.168.109.255
            inet6 fe80::f816:3eff:feab:d1b9  prefixlen 64  scopeid 0x20<link>
            ether fa:16:3e:ab:d1:b9  txqueuelen 1000  (Ethernet)
            RX packets 61250645  bytes 20429432458 (19.0 GiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 53692510  bytes 27388569156 (25.5 GiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    
    eth0:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
            inet 192.168.109.50  netmask 255.255.255.0  broadcast 192.168.109.255
            ether fa:16:3e:ab:d1:b9  txqueuelen 1000  (Ethernet)
    
    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
            inet 127.0.0.1  netmask 255.0.0.0
            inet6 ::1  prefixlen 128  scopeid 0x10<host>
            loop  txqueuelen 1000  (Local Loopback)
            RX packets 8209772  bytes 4629798489 (4.3 GiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 8209772  bytes 4629798489 (4.3 GiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    
    lo:1: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
            inet 192.168.109.50  netmask 0.0.0.0
            loop  txqueuelen 1000  (Local Loopback)
    • If the IP addresses are consistent, go to 12 to check the VPC database status:
    • If the IP addresses are inconsistent, contact technical support for assistance.

  12. Run the following command to check the VPC database status:

    sudo service had query

    Enter the password of the root user as prompted. The following command output is displayed.

    • If the value in the RESS column is normal, the VPC database is running properly.
    • If the value in the RESS column is not normal, the VPC database is abnormal. In this case, contact technical support for assistance.

  13. After 2 minutes, check whether the alarm is automatically cleared.

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: 37458

Downloads: 31

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