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

CloudEC V600R019C00 Troubleshooting (Enterprise On-premises, Convergent Conference)

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).
LMT Login Failure

LMT Login Failure

Symptom

  • When you start the client of HUAWEI Operation & Maintenance System, enter the correct user name and password, and then click Login. Then, the system displays any of the following messages:
    • Failed to initialize the communication environment. Check that the communication security modes are consistent and the required services are running correctly.
    • Failed to communicate with the server. Please check if the network is connected or the service is running properly.
    • Failed to authenticate the ID certificate, or no algorithm matches the peer.
  • When you start the client of Huawei Operation & Maintenance System, enter the correct user name and password, and then click Login. The login occasionally times out.

Possible Causes

The probable causes of the fault are as follows:

  • The network connection is interrupted.
  • The lmtserver module fails to run properly.
  • The security module fails to run properly.
  • The free disk space is insufficient.
  • A disk track is damaged.
  • The database connection is incorrect.
  • Authenticate the peer is enabled for the LMT, but the trust certificate is not configured for the LMT.
  • Authenticate the peer is enabled for the LMT, but the OMU certificate is still in the certificate revocation list.
  • Authenticate the peer is enabled for the OMU (through the OSS), but the certificate is not configured for the LMT.
  • The port (port 9101 or 11101) for logging in to the LMT is not enabled on the firewall.

Fault Diagnosis

Rectify the fault based on the error message returned by the system during the login.

Procedure

    Rectify the fault based on the different error messages.

    1. Rectify the fault based on the error message displayed during the login:

      • Failed to initialize the communication environment. Check that the communication security modes are consistent and the required services are running correctly: Go to 2.
      • Failed to communicate with the server. Please check if the network is connected or the service is running properly: Go to 7.
      • Failed to authenticate the ID certificate, or no algorithm matches the peer: Go to 38.
      • Others: Go to 42

    Check the configuration on the LMT.

    1. Check whether the IP address of Server is the same as the floating IP address of the OMU. For details on the IP address of Server, see Figure 6-20.

      Figure 6-20 Login interface (1)

      • Yes: Go to 5.
      • No: Go to 3.

    2. On the login interface, click the button on the right of Server, as shown in Figure 6-21. The Server Management dialog box is displayed, as shown in Figure 6-22. Configure the floating IP address of the OMU as the IP address of the server, or change the IP address of the server to the floating IP address of the OMU.

      Figure 6-21 Login interface (2)

      Figure 6-22 Server Management dialog box

    3. Log in to the client again, and check whether the login is successful.

      • Yes: No further action is required.
      • No: Go to 5.

    Check the network connection.

    1. On the PC, choose Start > Run, In the Run dialog box, type cmd, and press Enter to open the cmd.exe window.
    2. Run ping IP address. Here, IP address indicates the floating IP address of the OMU. Then, check whether the network connection between the PC and the OMU server is normal, that is, whether the output is consistent with that displayed in Figure 6-23.

      Figure 6-23 Output of the ping command

      • Yes: Go to 11.
      • No: Go to 7.

    3. Check whether the network cable of the PC is correctly connected.

      • Yes: Go to 9.
      • No: Go to 8.

    4. Contact the network administrator to make sure that the network cable is connected correctly.
    5. Check whether the IP address of the PC belongs to the same gateway as the floating IP address of the OMU.

      • Yes: Go to 11.
      • No: Go to 10.

    6. Contact the network administrator to make sure that the IP address of the PC belongs to the same gateway as the floating IP address of the OMU.
    7. Run telnet IP address Port number command in the cmd.exe window. (IP address indicates the floating IP address of the OMU and port number is 9101 or 11101.) Check whether the port is enabled on the server, as shown in Figure 6-24 and Figure 6-25.

      Figure 6-24 Success of running the telnet command

      Figure 6-25 Failure in running the telnet command

      • Yes: Go to 13.
      • No: Go to 12.
      NOTE:
      • 9101: Used for the LMT to set up connections with the OMU in ordinary mode.
      • 11101: Used for the LMT to set up connections with the OMU in safety mode.

      For the port information of the server, see OMU Communication Matrix.

    8. Contact the customer to enable the port on the firewall, and then log in to the client again. Then, check whether the login is successful.

      • Yes: No further action is required.
      • No: Go to 13.

    Check whether there are records that indicate IP addresses conflict.

    1. Select the OMU IP address and log in to PuTTY as user cgpexpert.
    2. Run su - root to switch to user root.
    3. Run QueryMirrorState and find the active OMU that is running in Active state.
    4. Log in the active OMU using PuTTY. After 5 minutes, check whether the information of IP address conflict of the active OMU is displayed, as shown in Figure 6-26.

      Figure 6-26 IP address conflict
      • Yes: Go to 17.
      • No: Go to 19.

    5. Contact the network administrator and check for fault based on the IP conflict information. Then, replan the floating IP addresses of the OMU.
    6. Use the new OMU floating IP address to log in to the client again. Check whether the login is successful.

      • Yes: No further action is required.
      • No: Go to 19.

    Check whether the lmtserver module is running properly.

    1. Log in to the PuTTY tool as user cgpexpert using the IP address of the active OMU.
    2. Run su - root to switch to user root.
    3. Run su - omu to switch to user omu, as shown in Figure 6-27.

      Figure 6-27 Switch user

    4. Run status | grep -i lmtserver to check whether the system displays running, as shown in Figure 6-28.

      Figure 6-28 Check status
      • Yes: Go to 25.
      • No: Go to 23.

    Start the lmtserver module manually.

    1. Run svc_adm -cmd startsvc lmtserver and pid lmtserver in turn to check whether the system displays running, as shown in Figure 6-29.

      Figure 6-29 Check lmtserver module status
      • Yes: Go to 24.
      • No: Go to 42.

    2. Log in to the client again, and check whether the login is successful.

      • Yes: No further action is required.
      • No: Go to 25.

    Check whether the security module is running properly.

    1. Log in to the PuTTY tool as user cgpexpert using the IP address of the active OMU.
    1. Run su - root to switch to user root.
    2. Run su - omu to switch to user omu.
    1. Run status | grep -i security to check whether the system displays running, as shown in Figure 6-30.

      Figure 6-30 Check status
      • Yes: Go to 31.
      • No: Go to 29.

    Start the security module manually.

    1. Run svc_adm -cmd startsvc security and pid security in turn to check whether the system displays running, as shown in Figure 6-31.

      Figure 6-31 Check security module status
      • Yes: Go to 30.
      • No: Go to 42.

    2. Log in to the client again, and check whether the login is successful.

      • Yes: No further action is required.
      • No: Go to 31.

    Check the disk space.

    1. Run su - root and enter the password of user root to switch to user root.
    2. Run df to check whether the disk usage is exactly 100%, as shown in Figure 6-32.

      Figure 6-32 Check the disk space
      • Yes: Go to 33.
      • No: Go to 34.

    3. Run cd /opt and du -h |grep -i [0-9]G > diskinfo.txt in turn, as shown in Figure 6-33 to record the disk usage, and then go to 43.

      Figure 6-33 Record the disk usage

    Check whether damaged disk tracks are available.

    1. Run badblocks -sv /dev/sda to check whether damaged disk tracks are available.

      • Yes: Go to 43.
      • No: Go to 35.

    Check the database.

    1. Run su omu to switch to user omu.
    2. Run dbopt -b db_status to check whether the output displays db_status :NORMAL, as shown in Figure 6-34.

      NOTE:

      During execution of dbopt, the system accesses the customer's database for obtaining the user password. Therefore, you must be authorized by the customer before using this command.

      Figure 6-34 Check the database
      • Yes: Go to 37.
      • No: Go to 42.

    3. Log in to the client again, and check whether the login is successful.

      • Yes: No further action is required.
      • No: Go to 42.

    Configure the certificate.

    1. Obtain the mapping identity certificate, trusted certificate, and revocation list from the administrator of the OSS that manages the NE. Configure the certificate for the LMT. For details, see Configuring a Digital Certificate for the OMU Client.
    2. Log in to the client again, and check whether the login is successful.

      • Yes: No further action is required.
      • No: Go to 40.

    Select SSL options on the LMT.

    1. Select TLSv1 for Protocol Version and Medium for Algorithm Intensity. For details about how to select SSL options, see Configuring the Secure Transmission Mode.
    2. Log in to the client again, and check whether the login is successful.

      • Yes: No further action is required.
      • No: Go to 42.

    Collect the log information, and contact technical support engineers.

    1. Collect the following logs depending on the troubleshooting progress:

      • Client logs: The client logs are stored in the Installation path of the client\omu\workspace1\client\tracefile directory. In addition, you can use the Log Information Collection tool on the LMT to collect logs about the LMT for fault location.

      • OMU server logs: Use the Information Collection Tool to collect items in Common fault analysis scenario.

    2. Contact Huawei technical support engineers to rectify the fault.

Related Information

None

Translation
Download
Updated: 2019-08-07

Document ID: EDOC1100059098

Views: 20404

Downloads: 12

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