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).
Process Alarms

Process Alarms

ALM-fusionguard_alarm_0009 The GaussDB Port Is Not Listened To

Description

ICAgent collects node process port information based on the fusionguard_gaussdb_template.yaml template. When the GaussDB port of the SCC-DB node is not listened to, the system generates an alarm.

Attribute

Alarm ID

Alarm Severity

Auto Clear

fusionguard_alarm_0009

Critical

Yes

Parameters

None

Impact on the System

GaussDB is unavailable, which affects use of services.

Possible Causes

The GaussDB process stops.

Procedure

  1. 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#$

  2. Click Enter System.
  3. On the menu bar, choose Alarms > Current Alarms. In Details, locate IP Address/URL/Domain Name of the alarm.
  4. Use PuTTY to log in to the management VM by using the IP address specified by IP Address/URL/Domain Name in Details.

    Default username: sccadmin; default password: Scloud12#$

  5. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

    sudo su - root

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

    TMOUT=0

  7. Run the following command to check whether the 5432 port is listened to:

    netstat -tlnp | grep 5432

    The correct command output is as follows:

    tcp        0      0 127.0.0.1:5432          0.0.0.0:*               LISTEN      20472/gaussdb       
    tcp        0      0 x.x.x.x:5432        0.0.0.0:*               LISTEN      20472/gaussdb       
    tcp6       0      0 ::1:5432                :::*                    LISTEN      20472/gaussdb
    • If yes, go to 12.
    • If no, go to 8.

  8. On the node where the alarm is generated, run the following command to switch to the dbadmin user:

    su dbadmin

  9. Run the following command to check whether the node is the active node or the standby node:

    gs_ctl query

    • If the node is the active node, as shown in the following figure, go to 10.

    • If the node is the standby node, as shown in the following figure, go to 11.

  10. On the active node, run the following command to restart the GaussDB process:

    gs_ctl restart -M primary

  11. On the standby node, run the following command to restart the GaussDB process:

    gs_ctl restart -M standby

  12. Wait for 10 to 20 minutes and check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Related Information

None

ALM-fusionguard_alarm_0010 The GaussDB Process Is Not Running Properly

Description

ICAgent collects node process port information based on the fusionguard_gaussdb_template.yaml template. When the GaussDB process of the SCC-DB node is not running properly, the system generates an alarm.

Attribute

Alarm ID

Alarm Severity

Auto Clear

fusionguard_alarm_0010

Critical

Yes

Parameters

None

Impact on the System

GaussDB is unavailable, which affects use of services.

Possible Causes

The GaussDB process stops.

Procedure

  1. 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#$

  2. Click Enter System.
  3. On the menu bar, choose Alarms > Current Alarms. In Details, locate IP Address/URL/Domain Name of the alarm.
  4. Use PuTTY to log in to the management VM by using the IP address specified by IP Address/URL/Domain Name in Details.

    Default username: sccadmin; default password: Scloud12#$

  5. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

    sudo su - root

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

    TMOUT=0

  7. Run the following command to check whether the GaussDB process exists:

    ps -ef | grep gaussdb | grep "/opt/gaussdb/dbprogram/bin/gaussdb -M"

    The correct command output is as follows:

    root      1311 24242  0 12:42 pts/2    00:00:00 grep --color=auto /opt/gaussdb/dbprogram/bin/gaussdb -M
    dbadmin  20472     1  0 Feb27 ?        00:00:52 /opt/gaussdb/dbprogram/bin/gaussdb -M primary
    • If yes, go to 12.
    • If no, go to 8.

  8. On the node where the alarm is generated, run the following command to switch to the dbadmin user:

    su dbadmin

  9. Run the following command to check whether the node is the active node or the standby node:

    gs_ctl query

    • If the node is the active node, as shown in the following figure, go to 10.

    • If the node is the standby node, as shown in the following figure, go to 11.

  10. On the active node, run the following command to restart the GaussDB process:

    gs_ctl restart -M primary

  11. On the standby node, run the following command to restart the GaussDB process:

    gs_ctl restart -M standby

  12. Wait for 10 to 20 minutes and check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Related Information

None

ALM-fusionguard_alarm_0016 The NTP Port of SCC Is Not Listened To

Description

ICAgent collects node process port information based on the fusionguard_ntp_template.yaml template. When the NTP port of any node on the SCC platform is not listened to, the system generates an alarm.

Attribute

Alarm ID

Alarm Severity

Auto Clear

fusionguard_alarm_0016

Critical

Yes

Parameters

None

Impact on the System

Incorrect time is recorded in the log and in the database because time is not synchronized.

Possible Causes

The NTP process stops.

Procedure

  1. 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#$

  2. Click Enter System.
  3. On the menu bar, choose Alarms > Current Alarms. In Details, locate IP Address/URL/Domain Name of the alarm.
  4. Use PuTTY to log in to the management VM by using the IP address specified by IP Address/URL/Domain Name in Details.

    Default username: sccadmin; default password: Scloud12#$

  5. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

    sudo su - root

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

    TMOUT=0

  7. Run the following command to check whether the 123 port is listened to:

    netstat -lnp | grep 123

    The correct command output is as follows:

    udp        0      0 192.168.2.160:123       0.0.0.0:*                           6752/ntpd
    udp        0      0 127.0.0.1:123           0.0.0.0:*                           6752/ntpd
    udp        0      0 0.0.0.0:123             0.0.0.0:*                           6752/ntpd
    • If yes, go to 9.
    • If no, go to 8.

  8. Run the following command to restart the NTP process:

    systemctl restart ntpd.service

  9. Wait for 10 to 20 minutes and check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Related Information

None

ALM-fusionguard_alarm_0017 The NTP Process of SCC Is Not Running Properly

Description

ICAgent collects node process port information based on the fusionguard_ntp_template.yaml template. When the NTP process of any node on the SCC platform is not running properly, the system generates an alarm.

Attribute

Alarm ID

Alarm Severity

Auto Clear

fusionguard_alarm_0017

Critical

Yes

Parameters

None

Impact on the System

Incorrect time is recorded in the log and in the database because time is not synchronized.

Possible Causes

The NTP process stops.

Procedure

  1. 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#$

  2. Click Enter System.
  3. On the menu bar, choose Alarms > Current Alarms. In Details, locate IP Address/URL/Domain Name of the alarm.
  4. Use PuTTY to log in to the management VM by using the IP address specified by IP Address/URL/Domain Name in Details.

    Default username: sccadmin; default password: Scloud12#$

  5. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

    sudo su - root

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

    TMOUT=0

  7. Run the following command to check whether the NTP process exists:

    ps -ef | grep ntpd

    The correct command output is as follows:

    ntp        813     1  0 Feb22 ?        00:00:00 /usr/sbin/ntpd -u ntp:ntp -g
    root      9953  9642  0 19:41 pts/0    00:00:00 grep --color=auto ntpd
    • If yes, go to 9.
    • If no, go to 8.

  8. Run the following command to restart the NTP process:

    systemctl restart ntpd.service

  9. Wait for 10 to 20 minutes and check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Related Information

None

ALM-fusionguard_alarm_0020 The Nginx Port of SCC Is Not Listened To

Description

ICAgent collects node process port information based on the fusionguard_scc_nginx_template.yaml template. When the Nginx port of the SCC-LB node is not listened to, the system generates an alarm.

Attribute

Alarm ID

Alarm Severity

Auto Clear

fusionguard_alarm_0020

Critical

Yes

Parameters

None

Impact on the System

Nginx is unavailable, which affects use of services.

Possible Causes

The Nginx process stops.

Procedure

  1. 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#$

  2. Click Enter System.
  3. On the menu bar, choose Alarms > Current Alarms. In Details, locate IP Address/URL/Domain Name of the alarm.
  4. Use PuTTY to log in to the management VM by using the IP address specified by IP Address/URL/Domain Name in Details.

    Default username: sccadmin; default password: Scloud12#$

  5. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

    sudo su - root

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

    TMOUT=0

  7. Run the following command to check whether the 7443 port is listened to:

    netstat -tlnp | grep 7443

    The correct command output is as follows:

    tcp        0      0 0.0.0.0:7443            0.0.0.0:*               LISTEN      8804/nginx: master
    • If yes, go to 9.
    • If no, go to 8.

  8. Run the following command to restart the Nginx process:

    service nginxd restart

  9. Wait for 10 to 20 minutes and check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Related Information

None

ALM-fusionguard_alarm_0021 The Nginx Process of SCC Is Not Running Properly

Description

ICAgent collects node process port information based on the fusionguard_scc_nginx_template.yaml template. When the Nginx process of the SCC-LB node is not running properly, the system generates an alarm.

Attribute

Alarm ID

Alarm Severity

Auto Clear

fusionguard_alarm_0021

Critical

Yes

Parameters

None

Impact on the System

Nginx is unavailable, which affects use of services.

Possible Causes

The Nginx process stops.

Procedure

  1. 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#$

  2. Click Enter System.
  3. On the menu bar, choose Alarms > Current Alarms. In Details, locate IP Address/URL/Domain Name of the alarm.
  4. Use PuTTY to log in to the management VM by using the IP address specified by IP Address/URL/Domain Name in Details.

    Default username: sccadmin; default password: Scloud12#$

  5. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

    sudo su - root

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

    TMOUT=0

  7. Run the following command to check whether the Nginx process exists:

    ps -ef | grep nginx

    The correct command output is as follows:

    nginx     8804     1  0 04:09 ?        00:00:00 nginx: master process /usr/sbin/nginx
    nginx     8805  8804  0 04:09 ?        00:00:00 nginx: worker process
    nginx     8806  8804  0 04:09 ?        00:00:00 nginx: worker process
    root     23840  3425  0 06:53 pts/1    00:00:00 grep --color=auto nginx
    • If yes, go to 9.
    • If no, go to 8.

  8. Run the following command to restart the Nginx process:

    service nginxd restart

  9. Wait for 10 to 20 minutes and check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Related Information

None

ALM-fusionguard_alarm_0022 The OMMHA Process of SCC Is Not Running Properly

Description

ICAgent collects node process port information based on the fusionguard_scc_ommha_template.yaml template. When the OMMHA process of any node on the SCC platform is not running properly, the system generates an alarm.

Attribute

Alarm ID

Alarm Severity

Auto Clear

fusionguard_alarm_0022

Critical

Yes

Parameters

None

Impact on the System

OMMHA is unavailable, which affects use of services.

Possible Causes

The OMMHA process stops.

Procedure

  1. 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#$

  2. Click Enter System.
  3. On the menu bar, choose Alarms > Current Alarms. In Details, locate IP Address/URL/Domain Name of the alarm.
  4. Use PuTTY to log in to the management VM by using the IP address specified by IP Address/URL/Domain Name in Details.

    Default username: sccadmin; default password: Scloud12#$

  5. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

    sudo su - root

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

    TMOUT=0

  7. Run the following command to check whether the OMMHA process exists:

    ps -ef | grep "ha.bin"

    The correct command output is as follows:

    [root@lb_h1 ~]# ps -ef|grep "ha.bin"
    root      2898     1  0 Feb01 ?        01:16:41 /usr/ha/module/hacom/bin/ha.bin --logsyslog=0 --loglevel=INFO --logpath=/var/log/scc/ha/runlog --logarchive=3600 --bboxpath=/var/log/scc/ha/core --module=HA
    root      5814  5431  0 14:43 pts/4    00:00:00 grep --color=auto ha.bin
    • If yes, go to 9.
    • If no, go to 8.

  8. Run the following command to restart the OMMHA process:

    service ommha restart

  9. Wait for 10 to 20 minutes and check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Related Information

None

ALM-fusionguard_alarm_0023 The Tomcat Port of SCC Is Not Listened To

Description

ICAgent collects node process port information based on the fusionguard_scc_tomcat_template.yaml template. When the Tomcat port of any node on the SCC platform is not listened to, the system generates an alarm.

Attribute

Alarm ID

Alarm Severity

Auto Clear

fusionguard_alarm_0023

Critical

Yes

Parameters

None

Impact on the System

Tomcat is unavailable, which affects use of services.

Possible Causes

The Tomcat process stops.

Procedure

  1. 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#$

  2. Click Enter System.
  3. On the menu bar, choose Alarms > Current Alarms. In Details, locate IP Address/URL/Domain Name of the alarm.
  4. Use PuTTY to log in to the management VM by using the IP address specified by IP Address/URL/Domain Name in Details.

    Default username: sccadmin; default password: Scloud12#$

  5. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

    sudo su - root

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

    TMOUT=0

  7. Run the following command to check whether the 7443 port is listened to:

    netstat -tlnp | grep 7443

    The correct command output is as follows:

    tcp        0      0 192.168.2.160:7443      0.0.0.0:*               LISTEN      7434/java
    • If yes, go to 9.
    • If no, go to 8.

  8. Run the following command to restart the Tomcat process:

    systemctl restart systemd-tomcat

  9. Wait for 10 to 20 minutes and check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Related Information

None

ALM-fusionguard_alarm_0024 The Tomcat Process of SCC Is Not Running Properly

Description

ICAgent collects node process port information based on the fusionguard_scc_tomcat_template.yaml template. When the Tomcat process of any node on the SCC platform is not running properly, the system generates an alarm.

Attribute

Alarm ID

Alarm Severity

Auto Clear

fusionguard_alarm_0024

Critical

Yes

Parameters

None

Impact on the System

Tomcat is unavailable, which affects use of services.

Possible Causes

The Tomcat process stops.

Procedure

  1. 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#$

  2. Click Enter System.
  3. On the menu bar, choose Alarms > Current Alarms. In Details, locate IP Address/URL/Domain Name of the alarm.
  4. Use PuTTY to log in to the management VM by using the IP address specified by IP Address/URL/Domain Name in Details.

    Default username: sccadmin; default password: Scloud12#$

  5. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

    sudo su - root

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

    TMOUT=0

  7. Run the following command to check whether the Tomcat process exists:

    ps -ef | grep tomcat

    The correct command output is as follows:

    root     10626  9642  0 19:42 pts/0    00:00:00 grep --color=auto tomcat
    tomcat   25902     1  0 Feb27 ?        00:03:10 /usr/java/jdk-8u191/bin/java -Dnop -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048 -Djavax.net.ssl.trustStore=/opt/tomcat/certs/gaussdb/mytruststore -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -Dorg.apache.catalina.connector.RECYCLE_FACADES=true -Djava.endorsed.dirs= -classpath /opt/tomcat/bin/bootstrap.jar:/opt/tomcat/bin/tomcat-juli.jar -Dcatalina.base=/opt/tomcat -Dcatalina.home=/opt/tomcat -Djava.io.tmpdir=/opt/tomcat/temp org.apache.catalina.startup.Bootstrap start
    • If yes, go to 9.
    • If no, go to 8.

  8. Run the following command to restart the Tomcat process:

    systemctl restart systemd-tomcat

  9. Wait for 10 to 20 minutes and check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Related Information

None

ALM-fusionguard_alarm_0025 The NTP Port of SSA Is Not Listened To

Description

ICAgent collects node process port information based on the fusionguard_ssa_ntp_template.yaml template. When the NTP port of any node on the SSA platform is not listened to, the system generates an alarm.

Attribute

Alarm ID

Alarm Severity

Auto Clear

fusionguard_alarm_0025

Critical

Yes

Parameters

None

Impact on the System

Incorrect time is recorded in the log and in the database because time is not synchronized.

Possible Causes

The NTP process stops.

Procedure

  1. 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#$

  2. Click Enter System.
  3. On the menu bar, choose Alarms > Current Alarms. In Details, locate IP Address/URL/Domain Name of the alarm.
  4. Use PuTTY to log in to the management VM by using the IP address specified by IP Address/URL/Domain Name in Details.

    Default username: sccadmin; default password: Scloud12#$

  5. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

    sudo su - root

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

    TMOUT=0

  7. Run the following command to check whether the 123 port is listened to:

    netstat -lnp | grep 123

    The correct command output is as follows:

    udp        0      0 192.168.2.241:123       0.0.0.0:*                           29784/ntpd
    udp        0      0 127.0.0.1:123           0.0.0.0:*                           29784/ntpd
    • If yes, go to 9.
    • If no, go to 8.

  8. Run the following command to restart the NTP process:

    systemctl restart ntpd.service

  9. Wait for 10 to 20 minutes and check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Related Information

None

ALM-fusionguard_alarm_0026 The NTP Process of SSA Is Not Running Properly

Description

ICAgent collects node process port information based on the fusionguard_ssa_ntp_template.yaml template. When the NTP process of any node on the SSA platform is not running properly, the system generates an alarm.

Attribute

Alarm ID

Alarm Severity

Auto Clear

fusionguard_alarm_0026

Critical

Yes

Parameters

None

Impact on the System

Incorrect time is recorded in the log and in the database because time is not synchronized.

Possible Causes

The NTP process stops.

Procedure

  1. 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#$

  2. Click Enter System.
  3. On the menu bar, choose Alarms > Current Alarms. In Details, locate IP Address/URL/Domain Name of the alarm.
  4. Use PuTTY to log in to the management VM by using the IP address specified by IP Address/URL/Domain Name in Details.

    Default username: sccadmin; default password: Scloud12#$

  5. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

    sudo su - root

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

    TMOUT=0

  7. Run the following command to check whether the NTP process exists:

    ps -ef | grep ntpd

    The correct command output is as follows:

    root      9005 30503  0 19:56 pts/0    00:00:00 grep --color=auto ntpd
    ntp      29784     1  0  2018 ?        00:00:10 /usr/sbin/ntpd -u ntp:ntp -g
    • If yes, go to 9.
    • If no, go to 8.

  8. Run the following command to restart the NTP process:

    systemctl restart ntpd.service

  9. Wait for 10 to 20 minutes and check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Related Information

None

ALM-fusionguard_alarm_0027 The OMMHA Process of SSA Is Not Running Properly

Description

ICAgent collects node process port information based on the fusionguard_ssa_ommha_template.yaml template. When the OMMHA process of any node on the SSA platform is not running properly, the system generates an alarm.

Attribute

Alarm ID

Alarm Severity

Auto Clear

fusionguard_alarm_0027

Critical

Yes

Parameters

None

Impact on the System

OMMHA is unavailable, which affects use of SSA.

Possible Causes

The OMMHA process stops.

Procedure

  1. 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#$

  2. Click Enter System.
  3. On the menu bar, choose Alarms > Current Alarms. In Details, locate IP Address/URL/Domain Name of the alarm.
  4. Use PuTTY to log in to the management VM by using the IP address specified by IP Address/URL/Domain Name in Details.

    Default username: sccadmin; default password: Scloud12#$

  5. Run the following command and enter the password Cloud12#$ of user root to switch to the root user:

    sudo su - root

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

    TMOUT=0

  7. Run the following command to check whether the OMMHA process exists:

    ps -ef | grep "ha.bin"

    The correct command output is as follows:

    root     19041 30503  0 19:57 pts/0    00:00:00 grep --color=auto ha.bin
    root     27112     1  0 Jan11 ?        05:34:39 /opt/gaussdb/ha/module/hacom/bin/ha.bin --logsyslog=0 --loglevel=WARN --logpath=/var/log/ha/runlog --logarchive=86400 --bboxth=/var/log/ha/core --module=HA
    • If yes, go to 9.
    • If no, go to 8.

  8. Run the following command to restart the OMMHA process:

    service had restart

  9. Wait for 10 to 20 minutes and check whether the alarm is automatically cleared.

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 48464

Downloads: 33

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