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 02

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).
Common Operations

Common Operations

System Time Faults

Scenarios

Perform operations described in this section to adjust system time in the following scenarios:

  • A precise external clock source is not configured in the system, producing a time difference after the system runs for a long period.
  • The system time of the Service OM is manually adjusted inappropriately.
  • A time difference is produced for the Service OM due to an unsuccessful system time synchronization.

The adjusted system time cannot be earlier than the time when the license file of the system is loaded.

Impact on the System
  • All system services will be temporarily interrupted during system time adjustment, but services on the in-use VMs will not be affected.
  • If you need to adjust the time to a point earlier than the current time, stop accepting new services that may be submitted from the new time point. For example, if you need to adjust the system time from 00:00 to 23:00, stop accepting new services from 23:00.
  • If you adjust the system time to a point earlier than the current time, historical backup files and log files stored in the system may be overwritten. You are advised to handle time-irrelevant service alarms before adjusting the system time.
Prerequisites
  • If a Network Time Protocol (NTP) server is configured, it communicates with the Service OM properly.
  • If an NTP server is configured, it provides time services properly.
Procedure

Check the time configuration information.

  1. Log in to Service OM. For details, see Logging In to and Logging Out of Service OM.
  2. Choose Services > Service OM > Centralized O&M > System > Time Management.

    The Time Management page is displayed.

  3. On the Clock Sync area, check whether the time server has been configured.

    • If yes, go to 4.
    • If no, go to 10.

Adjust the system time.

  1. Use PuTTY to log in to the Service OM.

    Log in to the operating system (OS) as the galaxmanager user. The default password is IaaS@OS-CLOUD9!.

    NOTE:
    For details about Management IP address of the FusionSphere Service OM node , see the LLD generated by FCD sheet of the xxx_export_all.xlsm file exported from FusionCloud Deploy during software installation, and search for the IP addresses corresponding to VMs and nodes.The parameter names in different scenarios are as follows:
    • Region Type I scenario : Cascading-OM-externalOM-Float-IP.
    • Region Type II and Type III scenarios : OM-externalAPI-Float-IP.

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

    su - root

    The default password of the root user is IaaS@OS-CLOUD8!.

  3. Run the TMOUT=0 command to disable user logout upon system timeout:
  4. Run the following command to change the time to that of the upper-layer clock source:

    setDate "new time new date"

    For example, to change the time to 2013-4-3 15:00:00, run the following command:

    setDate "15:00:00 2013-4-3"

  5. Input N to quit.
  6. Check whether the time difference before and after the adjustment is greater than 1 minute.

    • If yes, go to 10.
    • If no, no further action is required.

  7. On the Time Management page, click Synchronize Time Forcibly.

    The Service OM will restart during the time synchronization. The restart takes 10 to 15 minutes.

  8. Log in to the Service OM.
  9. On the Time Management page, check whether the time synchronization is successful.

    • If yes, go to 13.
    • If no, contact technical support for assistance.
    NOTE:

    If the system displays a message indicating that the NTP server is faulty, check the NTP server state and ensure that the NTP server communicates with the Service OM properly.

  10. Use PuTTY to log in to the standby Service OM node.

    Log in to the operating system (OS) as the galaxmanager user. The default password is IaaS@OS-CLOUD9!.

    NOTE:
    For details about Management IP address of the FusionSphere Service OM node , see the LLD generated by FCD sheet of the xxx_export_all.xlsm file exported from FusionCloud Deploy during software installation, and search for the IP addresses corresponding to VMs and nodes.The parameter names in different scenarios are as follows:
    • Region Type I scenario : Cascading-OM-externalOM-Float-IP.
    • Region Type II and Type III scenarios : OM-externalAPI-Float-IP.

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

    su - root

    The default password of the root user is IaaS@OS-CLOUD8!.

  12. Run the TMOUT=0 command to disable user logout upon system timeout:
  13. Run the following command to query the standby Service OM node time:

    date

  14. Check whether the time on the active and standby Service OM nodes are the same.

    • If yes, no further action is required.
    • If no, go to 18.

  15. Run the following command to stop the NTP service on the standby FusionSphere OpenStack OM node:

    service ntp stop

  16. Run the following command to update the standby node time to the active node time:

    ntpdate Active node IP address

  17. Run the following command to start the NTP service on the standby FusionSphere OpenStack OM node:

    service ntp start

Obtaining Service OM Root Certificate

Scenarios

When Service OM functions as a server to communicate with network elements (NEs) except FusionSphere using the Secure Shell (SSL) protocol, the NEs, as clients, need to authenticate the Service OM identity using the root certificate of Service OM. To do so, the NEs must obtain the Service OM root certificate and import the obtained certificate to their trusted certificate libraries. If the Service OM root certificate is not imported to an NE's trusted certificate library, the NE will fail to communicate with the Service OM.

Prerequisites
  • A tool that can be used for remote access on various platforms, such as PuTTY, is available.
  • You have obtained the Service OM management IP address and the password of the galaxmanager user.
  • A cross-platform file transfer tool, such as WinSCP is available.
Procedure
  1. Use PuTTY to log in to the Service OM node. If Service OM is deployed in active/standby mode, log in to the active Service OM node.

    Ensure that the Service OM management IP address and the galaxmanager user are used to establish the connection.

    The default password of the galaxmanager user is IaaS@OS-CLOUD9!.

    NOTE:
    For details about Management IP address of the FusionSphere Service OM node , see the LLD generated by FCD sheet of the xxx_export_all.xlsm file exported from FusionCloud Deploy during software installation, and search for the IP addresses corresponding to VMs and nodes.The parameter names in different scenarios are as follows:
    • Region Type I scenario : Cascading-OM-externalOM-Float-IP.
    • Region Type II and Type III scenarios : OM-externalAPI-Float-IP.

  2. Run the following command to switch to user root, and enter the password of user root as prompted:

    su - root

    The default password of user root is IaaS@OS-CLOUD8!.

  3. Run the TMOUT=0 command to disable user logout upon system timeout.
  4. Run the following command to export the Service OM root certificate:

    exportFMRootCert

    The root certificate is exported successfully if the following information is displayed:

    export Root CA successfully

  5. Use the prepared file transfer tool, such as WinSCP, to enter the /opt/goku/data/upload directory and obtain the Service OM root certificate fsRoot.crt.
Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 23238

Downloads: 37

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