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

FusionCloud 6.3.1.1 Troubleshooting Guide 03

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).
Service Node Faults

Service Node Faults

The HSS Console Does not Respond for a Long Time

Symptom

The HSS Console stays on the page indicating waiting for approval and does not respond for a long time.

Possible Causes

The HSS background process is not started properly.

Procedure
  1. Use PuTTY to log in to all the nodes where HSS is deployed.

    Default username: sccadmin; default password: Scloud12#$

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

    sudo su - root

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

    TMOUT=0

  4. Run the following command to check whether the HSS process exists:

    ps aux |grep hss

    If the following information is displayed, the process is normal.

    • If yes, contact technical support for assistance.
    • If no, go to 5.

  5. Run the following command to restart the HSS service:

    /cmp/hssctl restart

  6. Run the following command to check whether the HSS process exists:

    ps aux |grep hss

    • If yes, go to 7.
    • If no, contact technical support for assistance.

  7. Use a browser to log in to the ManageOne operation plane as a VDC administrator or VDC operator.

    Login address: https://Domain name for accessing the console home page. Example: https://console.type.com.

  8. Select a region and a project from the drop-down box in the upper left corner of the page.
  9. Check whether the HSS service can be accessed.

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

Failed to Apply for HSS

Symptom

The HSS service fails to be applied for on the Console, and a message is displayed, indicating that the request fails.

Possible Causes
  • The Trend Micro service stopped.
  • The certificate does not match.
Troubleshooting Process
  1. Use PuTTY to log in to all the nodes where HSS is deployed.

    Default username: sccadmin; default password: Scloud12#$

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

    sudo su - root

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

    TMOUT=0

  4. Run the following command to check whether an error message is displayed in the run logs of the HSS:

    vi /cmp/log/{Latest log file name}

Procedure
  1. Log in to the Trend Micro Deep Security Manager (DSM) system and check whether the Trend Micro DSM service is stopped.

    1. Remotely log in to the VM where the Trend Micro DSM is deployed, view the service process, and check whether the service status is started.
      • If yes, go to 1.b.
      • If no, manually start the DSM service and perform 1.a again.
    2. Remotely log in to the SQL Server database server connected to the Trend Micro DSM system. Check whether the disk usage exceeds 95%.
      • If yes, expand the capacity manually and restart the database service. Then, go to 1.c.
      • If no, go to 2.
    3. Use a browser to log in to the ManageOne operation plane as a VDC administrator or VDC operator.

      Login address: https://Domain name for accessing the console home page. Example: https://console.type.com.

    4. Select a region and a project from the drop-down box in the upper left corner of the page.
    5. Apply for the service again and check whether the application is successful.
      • If yes, no further action is required.
      • If no, go to 2.

  2. Replace the certificate.

    1. For details about how to generate and replace a certificate, see section "Replacing a Certificate of the Trend Protection System" in FusionCloud 6.3.1.1 Certificate Management Guide.
    2. Use a browser to log in to the ManageOne operation plane as a VDC administrator or VDC operator.

      Login address: https://Domain name for accessing the console home page. Example: https://console.type.com.

    3. Select a region and a project from the drop-down box in the upper left corner of the page.
    4. Apply for the service again and check whether the application is successful.
      • If yes, no further action is required.
      • If no, contact technical support for assistance.

Physical Machine Power Off

Symptom

The Trend Micro DSM service stopped.

Possible Causes

The physical machine is normally or unexpectedly powered off.

Procedure
  1. Restart the DSM. Remotely log in to the Trend Micro DSM system.
  2. View the service process, find the Trend Micro DSM service, and click Restart to restart the DSM service.

  3. Use PuTTY to log in to all the nodes where HSS is deployed.

    Default username: sccadmin; default password: Scloud12#$

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

    sudo su - root

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

    TMOUT=0

  6. Run the following command to go to the /cmp directory:

    cd /cmp

  7. Run the following command to restart the HSS service:

    hssctl restart

Translation
Download
Updated: 2019-08-16

Document ID: EDOC1100063248

Views: 25241

Downloads: 40

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