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

FusionAccess V100R006C20 Cloud Classroom Solution Product Documentation 10 (Single-Classroom Scenarios)

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).
LiteAD Troubleshooting

LiteAD Troubleshooting

System Time Errors

Symptom

Perform the operations described in this topic to adjust the system time in any of the following scenarios:

  • All services will be temporarily interrupted during system time adjustment, but the VMs in use will not be affected.
  • If you adjust the system time to a point earlier than the current time, stop accepting services (for example, order and user review) submitted in the period between the new time point and the current time. For example, to change the system time from 00:00 to 23:00, stop accepting services from 23:00.
  • If you adjust the system time to a point earlier than the current time, historical backup files and log files in the system may be replaced.
  • If you adjust the system time to a point earlier than the current time, FusionAccess alarms may be cleared after the adjustment.
  • If you adjust the system time to a point earlier than the current time, operation logs and task logs on the FusionAccess Portal may be disordered.
Possible Causes
  • A cumulative departure occurs in the system time after the system runs for a long period because an external precision clock source is not deployed for the system.
  • The FusionManager system time is adjusted by mistake.
  • A cumulative departure occurs in the system time of a node of the FusionCompute or FusionAccess due to a misoperation.
  • A cumulative departure occurs in the system time of a node of the FusionCompute or FusionAccess due to system time synchronization failure.
  • If the time difference is less than or equal to 1 minute, directly adjust the system time of the FusionManager and FusionCompute. For details, see Step 28 and Step 29.
  • The adjusted system time cannot be earlier than the time when the license file is loaded.
Fault Diagnosis

Figure 3-96 shows the process for rectifying this fault.

Figure 3-96 Process for rectifying this fault
Procedure

Determine the time of starting the Active Directory (AD) group policy.

NOTE:

In the following operations, RSAT installed on Windows 7 is used as an example.

  1. Log in to the RSAT server using a domain administrator account.
  2. Choose Start > Administrative Tools > Group Policy Management.

    The Group Policy Management window is displayed.

  3. In the navigation tree, choose Forest > Domains. Then select the domain for which the time needs to be adjusted.

    Select the group policy object used to control Group policy refresh interval for computers and Group policy refresh interval for domain controllers. (The default object is Default Domain Policy.)

  4. Right-click the group policy object, and choose Edit from the shortcut menu.

    The Group Policy Management window is displayed.

  5. In the navigation tree, choose Computer Configuration > Policies > Administrative Templates > System > Group Policy.
  6. In the right pane, double-click Group policy refresh interval for computers to view the group policy refresh interval for computers.

    • If Group policy refresh interval for computers is set to Not Configured, the default value is used for the group policy refresh interval for computers.
    • If Group policy refresh interval for computers is set to Enabled, the group policy refresh interval for computers is the sum of the two parameter values (in minutes) displayed in the lower left corner.

  7. Double-click Group policy refresh interval for domain controllers to view the group policy refresh interval for domain controllers.

    • If Group policy refresh interval for domain controllers is set to Not Configured, the default value is used for the group policy refresh interval for domain controllers.
    • If Group policy refresh interval for domain controllers is set to Enabled, the group policy refresh interval for domain controllers is the sum of the two parameter values (in minutes) displayed in the lower left corner.

  8. Calculate the time of starting the AD group policy beforehand.

    Time of starting the AD group policy (in minutes) = Group policy refresh interval for computers x + Group policy refresh interval for domain controllers

    Group policy refresh interval for domain controllers = 5 minutes x (Number of domain controllers – 1)

    NOTE:

    The default group policy refresh interval for computers is 120 minutes, and the default group policy refresh interval for domain controllers is 5 minutes.

    Configure the AD group policy object and start the AD group policy.

    NOTE:

    You need to start the AD group policy N minutes ahead based on the adjusted time (N is calculated in Step 8).

  9. In the navigation tree in the Group Policy Management window, choose Forest > Domains and then the target domain name.
  10. Right-click Group Policy Objects, and choose New from the shortcut menu.

    The New GPO dialog box is displayed.

  11. Enter Windows time Service in the Name text box, and click OK.
  12. Right-click Windows time Service, and choose Edit from the shortcut menu.

    The Group Policy Management Editor window is displayed.

  13. Choose Computer Configuration > Policies > Administrative Templates > System > Windows Time Service.
  14. In the right pane, double-click Global Configuration Settings.
  15. On the Settings tab page, select Enabled.
  16. Modify the parameters as follows:

    • SpikeWatchPeriod: 1
    • MaxPollInterval: 6
    • MinPollInterval: 6
    • MaxNegPhaseCorrection: 4294967295
    • MaxPosPhaseCorrection: 4294967295
    • LargePhaseOffset: 50000000 (in decimal notation)

  17. Click OK.
  18. Exit the Group Policy Object Editor window, and drag the group policy object to the specified domain.

    "Do you want to link the GPOs that you have selected to this domain" is displayed.

  19. Click OK.
  20. Click the specified domain. On the Linked Group Policy Objects tab page, select Windows time Service and click to change its priority specified by Link Order to 1.

Back up system data and log files.

  1. Back up FusionManager data.

    For details, see Operation and Maintenance > Maintenance Management > Maintenance Management (Multi-Hypervisor and Private Cloud) > Backup and Restoration > FusionManager Backup and Restoration in FusionSphere V100R00xCxx Product Documentation (Server Virtualization,FusionCompute V100R00xCxx).

  2. Back up FusionCompute data.

    For details, see Operation and Maintenance > Maintenance Management > Maintenance Management (Multi-Hypervisor and Private Cloud) > Backup and Restoration > FusionCompute Backup and Recovery in FusionSphere V100R00xCxx Product Documentation (Server Virtualization,FusionCompute V100R00xCxx).

  3. Back up system log files.

    For details, see Collecting Logs.

View time configuration information.

  1. Log in to the FusionManager.
  2. Click System Management.

    The System Management page is displayed.

  3. Click Time Management.

    The Time Management page is displayed.

  4. View time configuration information.

Change the time of the FusionManager and FusionCompute.

  1. Change the time of the FusionManager.

    For details, see Fault Management > Troubleshooting > System Time Faults > System Time Faults in FusionSphere V100R00xCxx Product Documentation (Server Virtualization,FusionCompute V100R00xCxx).

  2. Change the time of the FusionCompute.

    Use the forcible time synchronization mode to change the time. For details, see Operation and Maintenance > Maintenance Management > SMaintenance Management in Single-Hypervisor Scenarios > Configuration Management > System Configuration > Synchronizing Time Forcibly in FusionSphere V100R00xCxx Product Documentation (Server Virtualization,FusionCompute V100R00xCxx).

Back up FusionAccess log files.

  1. Back up FusionAccess log files.

    For details, see Collecting Logs.

Change the FusionAccess time.
NOTE:

Wait for N minutes before performing the following operations to adjust the time. (N is calculated in 8.)

  1. Log in to the FusionAccess.
  2. Choose System > Time Management > Time Synchronization.

    The Time Synchronization page is displayed.

  3. Check whether time synchronization information is configured on this page.

  4. Configure time synchronization information.
  5. Click OK.
  6. Log in to the active and standby LiteAD servers as user root, and run the following command to restart the NTP service:

    service ntp restart

  7. Restart the active and standby LiteAD servers.
  8. Start the FusionAccess infrastructure servers in sequence.

    The startup sequence is as follows:

    1. AntiVirus and Patch servers

      The AntiVirus and Patch services are deployed together on the Windows server. You can restart all services by restarting these servers.

    2. TCM, AUS and Backup Server

      The TCM, AUS and Backup Server are deployed on the Linux server. You can run service ha restart to restart these services.

    3. Standby ITA, DB, HDC, WI, vAG, vLB, and LiteAD

      The standby ITA, DB, HDC, WI, vAG, vLB, and LiteAD are deployed on the Linux server. You can run service ha restart to restart these services.

    4. Active ITA, DB, HDC, WI, License, vAG, vLB, and LiteAD

      The active ITA, DB, HDC, WI, License, vAG, vLB, and LiteAD are deployed on the Linux server. You can run service ha restart to restart these services.

    Change the time of user VMs and thin clients (TCs).

  9. Wait for about 25 minutes. Then check whether the login to each user VM is successful.

    NOTE:

    After you change the AD time, user VMs will synchronize time with the AD in 6 to 25 minutes. (It takes user VMs 1 to 5 minutes to synchronize the time with the AD and 5 to 20 minutes to associate with the HDC.)

  10. Restart the user VMs to which users cannot log in to synchronize the time of the user VMs with the AD time.
  11. Ask users to change the TC time to enable the TC time to be consistent with the VM time. Then restart the TCs.

Verify the changes.

  1. View FusionAccess infrastructure server logs and ensure that the logs do not record any error information.
  2. Log in to the FusionAccess, and ensure that services can be successfully provisioned.
  3. Ensure that you can successfully log in to user VMs.

    NOTE:

    If the login to some user VMs fails, restart the VMs and ensure that the login is successful.

Delete or disable the new group policy object.

  1. Log in to the RSAT server using a domain administrator account.
  2. Choose Start > Administrative Tools > Group Policy Management.

    The Group Policy Management window is displayed.

  3. Press Enter.

    The Group Policy Management window is displayed.

  4. In the navigation tree, choose Forest > Domains, the target domain name, and then Group Policy Objects.
  5. Right-click Windows time Service, and choose Delete from the shortcut menu.

    A confirmation dialog box is displayed.

  6. Click OK to delete the new group policy object.

Clear the alarm manually.

  1. Log in to the FusionManager.
  2. Select Fault.

    The Fault page is displayed.

  3. Locate the row that contains the alarm to be cleared, and click in the Operation column to manually clear the alarm.

    A confirmation dialog box is displayed.

    NOTE:

    If the alarm clearance time is earlier than the alarm sending time after you change the time, the alarm cannot be automatically cleared and must be manually cleared.

  4. Click OK.

    The Fault page is displayed, and the alarm is cleared.

Related Information

None

DHCP Server Failure

Symptom

User virtual machines (VMs) cannot obtain IP addresses and therefore cannot be used. So you can not log into the VM.

Possible Causes

User virtual machines (VMs) cannot obtain IP addresses and therefore cannot be used.

Fault Diagnosis

Figure 3-97 shows the process for rectifying this fault.

Figure 3-97 Process for rectifying this fault
Procedure
  1. Rectify the network and service faults for the DHCP server.

    1. Log in to the active IT Adapter (ITA) server using a root account.
    2. Run the ping Service plane IP address for the DHCP server command to check whether the IP address is successfully pinged.
      • If yes, go to 1.f.
      • If no, go to 1.c.
    3. Locate and rectify the network fault.
    4. Locate and rectify DHCP configuration problems.

      The common problems are as follows:

      • There is no idle IP address in the IP address pool.
      • The DHCP server IP address in the subnet configuration is incorrect.
    5. Check whether you can create VMs on the FusionManager user interface (UI).
      • If yes, no further action is required.
      • If no, go to 1.f.
    6. Log in to the LiteAD server using a root account.
    7. Run the service dhcpd status
    8. Check whether the DHCP Server service is in the Running state, as shown in Figure 3-98.
      Figure 3-98 Checking the status of the DHCP Server service
    9. Run the startTools, choose Software > LiteAD > Configure LiteAD > Configure DHCP Service, as shown in Figure 3-99.
      Figure 3-99 Configure DHCP Service
    10. Set the following parameters as planned:
      • Start IP
      • End IP
      • Gateway IP
      • Mask Length
    11. Check whether you can create VMs on the FusionManager user interface (UI).
      • If yes, no further action is required.
      • If no, go to 1.l.
    12. Log in to the FusionCompute as user geadmin.
    13. Restart the DHCP server on the FusionCompute user interface (UI).
    14. Check whether you can create VMs on the FusionManager UI.
      • If yes, no further action is required.
      • If no, go to 2.a.

  2. Reinstall the system to recover the DHCP server.

    1. Reinstall the system to recover the DHCP server.
    2. Check whether you can create VMs on the FusionManager UI.

Related Information

None.

Translation
Download
Updated: 2019-04-25

Document ID: EDOC1100010651

Views: 26131

Downloads: 162

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