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-127 Alarm of the Failure to Connect the Master and Standby Syslog Servers

ALM-127 Alarm of the Failure to Connect the Master and Standby Syslog Servers

Alarm Description

This alarm is generated when ManageOne fails to connect to the active and standby Syslog servers. This alarm is cleared after ManageOne successfully connects to the active or standby Syslog server.

Alarm Attribute

Alarm ID

Alarm Severity

Alarm Type

127

Major

Environment alarm

Alarm Parameters

Name

Description

Master server IP address

IP address of the active Syslog server.

Master server port

Port number of the active Syslog server.

Standby server IP address

IP address of the standby Syslog server.

Standby server port

Port number of the standby Syslog server.

Impact on the System

If the connection fails, logs cannot be forwarded to the active and standby Syslog servers. After the connection recovers, logs that meet log forwarding requirements but failed to be forwarded are forwarded to the active or standby Syslog servers.

System Actions

None

Possible Causes

  • The active and standby Syslog servers are not running.
  • ManageOne is disconnected from the active and standby Syslog servers.

Handling Procedure

  1. Check whether the active and standby Syslog servers are running properly.

    • If yes, go to 2.
    • If no, restart the active and standby Syslog servers and go to 3.
      NOTE:

      Syslog servers are third-party servers. For details about how to check whether they are running or started, see the relevant description for third-party Syslog servers.

  2. Check the network connection between ManageOne and the active and standby Syslog servers.

    1. Use PuTTY to log in to the MOC-ManageOne-Deploy01 node where the SMLogLic service is deployed as the ossadm user in SSH mode.
    2. Run the following command to check the network connection between ManageOne and the active Syslog server:

      ping IP address of the active Syslog server

      • If information similar to the following is displayed, the network connection is normal:
        64 bytes from IP address of the active Syslog server: icmp_seq=1 ttl=62 time=2.20 ms
      • If the information is not returned within 1 minute, the network is faulty. Rectify the network fault.
    3. Run the following command to check the network connection between ManageOne and the standby Syslog server:

      ping IP address of the standby Syslog server

      • If information similar to the following is displayed, the network connection is normal:
        64 bytes from IP address of the standby Syslog server: icmp_seq=1 ttl=62 time=2.20 ms
      • If the information is not returned within 1 minute, the network is faulty. Rectify the network fault.
    4. Use PuTTY to log in to the MOC-ManageOne-Deploy02 node where the SMLogLic service is deployed as the ossadm user in SSH mode and perform 2.b to 2.c.

  3. Wait for 30 seconds and check whether this alarm is cleared.

    • If yes, no further action is required.
    • If no, collect the information about alarm handling and contact Huawei technical support.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 44979

Downloads: 33

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