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).
SFS Console

SFS Console

ALM-6100011 The SFS Console tomcat process is abnormal

Description

This alarm is generated when the Tomcat process of the monitored object is interrupted.

Attribute

ID

Alarm Severity

Automatically Cleared

6100011

Critical

Yes

Parameters

Parameter

Description

Location Info

Resource name

Name of the device for which the alarm is generated

Resource type

MONITOR

Monitor type

Service monitoring

Host IP address

IP address of the host

Details

Recent %s cycle data

Threshold

Threshold for generating an alarm

Impact on the System

SFS Console cannot function properly.

Possible Causes

The Tomcat process of SFS Console fails to be started.

Procedure

  1. Use PuTTY to log in to the SFS Console node. To obtain its IP address, search for SFS_CONSOLE01 or SFS_CONSOLE02 in the 2.1 Tool-generated IP Parameters sheet of the xxx_export_all_EN.xlsm file exported after deployment using HUAWEI CLOUD Stack Deploy.

    Default account is sfs_admin, default password: Huawei12#$.

  1. Run the following command to switch to user root:

    sudo su

    Enter the password of user root next to password for root:, default password: Cloud12#$.

  2. Run the following command to check whether the SFS service has been started successfully:

    sh /etc/sfs/console/control.sh status
    • If yes, SFS is started successfully and Console is running is displayed in the command output. Go to Step 5.
      [root@host-172-17-11-45 sfs_admin]# sh /etc/sfs/console/control.sh status
      Console is running
    • If no, SFS fails to be started and Console is not running is displayed in the command output. Go to Step 4.
      [root@host-172-17-11-45 sfs_admin]# sh /etc/sfs/console/control.sh status
      Console is not running

  3. Run the following command to restart the SFS service.

    sh /etc/sfs/console/control.sh restart

    • If yes, SFS is restarted successfully and Start console successfully is displayed in the command output. Go to Step 5.
      [root@host-172-17-11-45 sfs_admin]# sh /etc/sfs/console/control.sh restart
      Stop console successfully
      Starting console component...
      Console started successfully
      Start console successfully
    • If no, contact technical support engineers for help.

  4. Please check whether the alarm is cleared within the next monitoring period (about 3 minutes).

    • If yes, the alarm is cleared and no further action is required.
    • If no, contact technical support engineers for help.

Related Information

None

ALM-6100010 The SFS Console tomcat port is not listening

Description

This alarm is generated when the Tomcat 7443 port of the monitored object fails to be bound.

Attribute

ID

Alarm Severity

Automatically Cleared

6100010

Critical

Yes

Parameters

Parameter

Description

Location Info

Resource name

Name of the device for which the alarm is generated

Resource type

MONITOR

Monitor type

Service monitoring

Host IP address

IP address of the host

Details

Recent %s cycle data

Threshold

Threshold for generating an alarm

Impact on the System

SFS Console cannot function properly.

Possible Causes

The Tomcat 7443 port of SFS Console fails to be bound.

Procedure

  1. Use PuTTY to log in to the SFS Console node. To obtain its IP address, search for SFS_CONSOLE01 or SFS_CONSOLE02 in the 2.1 Tool-generated IP Parameters sheet of the xxx_export_all_EN.xlsm file exported after deployment using HUAWEI CLOUD Stack Deploy.

    Default account is sfs_admin, default password: Huawei12#$.

  2. Run the following command to switch to user root:

    sudo su

    Enter the password of user root next to password for root:, default password: Cloud12#$.

  3. Run the following command to check whether the SFS service has been started successfully:

    sh /etc/sfs/console/control.sh status

    • If yes, SFS is started successfully and the following command output is displayed. Go to Step 4.
      [root@host-172-17-11-45 sfs_admin]# sh /etc/sfs/console/control.sh status
      Console is running
    • If no, SFS fails to be started and Console is not running is displayed in the command output. Go to Step 5.
      [root@host-172-17-11-45 sfs_admin]# sh /etc/sfs/console/control.sh status  
      Console is not running

  4. Run the following command to check whether the Tomcat port is bound properly:

    netstat -ntl

    • If yes, the SFS service port is bound successfully and the SFS Console service port (7443) is displayed in the command output. Go to Step 6.
      [root@host-172-17-11-45 sfs_admin]# netstat -ntl
      Active Internet connections (only servers)
      Proto Recv-Q Send-Q Local Address           Foreign Address         State      
      tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     
      tcp        0      0 192.168.1.3:26401        0.0.0.0:*               LISTEN     
      tcp6       0      0 192.168.1.3:7443         :::*                    LISTEN     
      tcp6       0      0 :::22                   :::*                    LISTEN  
    • If no, the SFS service port fails to be bound and the SFS Console service port (7443) is not displayed in the command output. Go to Step 5.

  5. Run the following command to restart the SFS service.

    sh /etc/sfs/console/control.sh restart

    • If yes, SFS is restarted successfully and Start console successfully is displayed in the command output. Go to Step 6.
      [root@host-172-17-11-45 sfs_admin]# sh /etc/sfs/console/control.sh restart
      Stop console successfully
      Starting console component...
      Console started successfully
      Start console successfully
    • If no, contact technical support engineers for help.

  6. Please check whether the alarm is cleared within the next monitoring period (about 3 minutes).

    • If yes, the alarm is cleared and no further action is required.
    • If no, contact technical support engineers for help.

Related Information

None

ALM-6100012 The SFS Console tomcat certificate excepting

Description

This alarm is generated when the Tomcat certificate of the monitored object is abnormal.

Attribute

ID

Alarm Severity

Automatically Cleared

6100012

Critical/Major

Yes

Parameters

Parameter

Description

Location Info

Resource name

Name of the device for which the alarm is generated

Resource type

MONITOR

Monitor type

Service monitoring

Host IP address

IP address of the host

Details

Recent %s cycle data

Threshold

Threshold for generating an alarm

Impact on the System

SFS Console cannot function properly.

Possible Causes

  1. The validity period of the SFS Console Tomcat certificate is about to expire.
  2. The validity period of the SFS Console Tomcat certificate has expired.
  3. Validity monitoring on the SFS Console Tomcat certificate is abnormal.

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. In the upper part of the page, choose System > Monitoring. The service monitoring page is displayed.
  3. In the navigation tree on the left, choose Instances. In the search box in the upper right corner, enter SFS.
  4. Click the instance name in the row where the instance that you want to view resides. The instance monitoring page is displayed.
  5. In the navigation tree on the left, choose keystore. Check the monitoring status value of the SFS Console Tomcat certificate on the current node.

    • If the value is 1, the certificate is about to expire. Go to 3.
    • If the value is 2, the certificate has expired. Go to 3
    • If the value is greater than or equal to 3, the certificate validity monitoring is abnormal. Contact technical support for assistance.

  6. Replace the Tomcat certificate. For details, see section Updating the TLS Certificate of Tomcat on the SFS Console in HUAWEI CLOUD Stack 6.5.0 Security Management Guide.
  7. After the certificate is replaced, check whether the alarm is cleared within the next monitoring period (about 3 minutes).

    • If yes, the alarm is cleared and no further action is required.
    • If no, contact technical support engineers for help.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 36705

Downloads: 31

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