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).
Maintenance Instructions

Maintenance Instructions

Critical Operations

Avoid the operations listed in Table 2-24 during the FusionAccess maintenance. These operations may result in serious impact on the system.

Table 2-24 Forbidden operations

Category

Risks

Service operations

Delete virtual desktops on FusionManager or FusionCompute.

User virtual desktops will be unavailable.

Deploy the Dynamic Host Configuration Protocol (DHCP) servers or domain name servers (DNSs) in the desktop cloud.

The DHCP and DNS servers conflict with the DHCP and DNS services running on FusionAccess, resulting in service failures.

Forcibly restart or shut down a VM when the VM operating system (OS) restarts normally, for example, the VM OS restarts during patch installation.

The VM may be damaged.

Mount Windows 7 or Windows Server 2008 system disks to a Windows 7 or Windows Server 2008 VM as user disks.

The system boot file may be damaged, which causes a blank screen.

Table 2-25 lists the operations that may affect FusionAccess reliability and security if improperly performed.

Table 2-25 Critical operations

Operation

Risks

Risk Level

Workaround

Check Item

Replace an infrastructure server.

Improper operations may cause service interruption.

▲▲▲

Back up data and then replace the server.

Check whether there are uncleared alarms after the replacement.

Modify group policies on the active directory (AD).

Improper operations may cause service interruption.

▲▲

Record the original configuration of the group policies. If a fault occurs, restore the original configuration.

Check whether VMs are accessible.

Create and associate VMs in batches on the IT adapter (ITA).

If a large number of batch operations are performed during the day, the ITA performance deteriorates and other services may become unavailable.

▲▲▲

  1. Create and associate VMs in batches during low-traffic hours.
  2. Ensure that resources are sufficient before creating and associating VMs in batches.

Check whether VMs are accessible.

On System > Initial Configuration of FusionAccess, perform operations, such as configuring the virtualization environment, domain/OU, and desktop components.

Improper operations may cause service interruption.

▲▲

Record the original configuration information. If a fault occurs, restore the original configuration.

Check whether VMs can be created successfully.

Manually delete VMs.

If a VM is deleted by mistake, data will be lost and services will be interrupted.

▲▲

Confirm the VM information before deleting a VM.

-

Recompose System Disk

Improper operations may result in the loss of user data in the system disk of a linked clone or VM.

▲▲▲

Recompose System Disk only when data loss is allowed.

-

Restore System Disk

Improper operations may result in the loss of user data in the system disk of a linked clone VM.

▲▲▲

Restore System Disk only when data loss is allowed.

-

Create scheduled tasks and select policies.

Improper operations may cause service interruption.

▲▲

Select policies based on service requirements.

Check whether scheduled tasks can be successfully performed.

Configure template types.

Service provisioning fails if the configured template type is not consistent with the required template type.

▲▲

Confirm the required template type and configure the template type correctly.

Check whether services can be provisioned properly.

Do not install Windows Server 2012 R2 SP1.

Security risks exist in infrastructure VMs if Windows Server 2012 R2 SP1 is not installed.

▲▲

Check whether Windows Server 2012 R2 SP1 has been installed on infrastructure VMs. If not, install it.

-

Adjust or change the clock source.

If the clock source is adjusted or changed, the time on VMs will change, which may cause service interruption.

▲▲

Adjust or change the clock source during low-traffic hours.

Observe the time difference after the clock source is adjusted or changed.

Update systems concurrently.

A large number of concurrent update operations exhaust CPU resources of servers and congest the storage and network, resulting in slow running of VMs, node restart, or storage faults.

▲▲▲

Update user VMs in different batches.

Check whether there are uncleared alarms.

Kill viruses concurrently.

A large number of concurrent antivirus operations exhaust CPU resources of servers and congest storage, resulting in slow running of VMs, node restart, or storage faults.

▲▲▲

Kill viruses during low-traffic hours.

Check whether there are uncleared alarms.

Concurrently start VMs at work.

If VMs are concurrently started at work, I/O storms are generated, and VMs run slowly.

▲▲

  1. Do not shut down VMs.
  2. Get VMs ready using scheduled tasks before employees come to the office.

Check whether there are uncleared alarms.

Play videos concurrently on office VMs.

Playing videos concurrently on office VMs exhausts CPU resources of servers and congests the network, resulting in slow running of VMs, disconnection from VMs, or VM connection failures.

▲▲

  1. Improve the specifications of VMs.
  2. Reduce the VM density on a server.

Check whether there are uncleared alarms.

Do not restart VMs for a long time.

Memory garbage exists after the OS runs for a long time, resulting in slow running of VMs.

Restart VMs every seven days at most.

-

Frequently switch over the active and standby GaussDBs.

The active and standby GaussDB databases may be damaged, and the data may be inconsistent or lost.

▲▲▲

  1. Reduce the active/standby GaussDB switchover frequency.
  2. During the switchover, do not perform operations such as creating or deleting VMs.

Check whether there are uncleared alarms.

DB exception alarms (1000029 Alarm About Two Active GaussDB Databases, 1001005 HDC Database Exception, and 1004001 Database Server Exception) exist during the GaussDB switchover.

The data in the active and standby GaussDB may be inconsistent and data may be lost.

▲▲▲

  1. DB exception alarms cannot exist during the GaussDB switchover.
  2. During the switchover, do not perform operations such as creating or deleting VMs.

Check whether there are uncleared alarms.

Terminal Management

Upgrading Clients

This section describes the software packages and reference documents to be obtained for upgrading TC clients and FusionAccess clients. For details about the version mapping, see the FusionAccess Desktop Solution V100R006C20SPC100 Version Mapping.

Upgrading the CloudClient on a teacher's TC

In cloud classroom scenarios, the CloudClient installed on teachers' TCs must meet the version requirements. If not, upgrade the Cloud Client.

  1. Open the CloudClient on a teacher's TC and log in to the teacher VM.
  2. If information shown in Figure 2-53 is displayed, click Download and then install the CloudClient.

    NOTE:

    If no such information is displayed, upgrade is not needed because the CloudClient is of the latest version.

    Figure 2-53 Upgrading the CloudClient

Upgrading the CloudClient on a student's TC

Table 2-26 lists the Sunniwell TC types supported by the desktop cloud solution and the software required for upgrading the TC client.

Table 2-26 Required Sunniwell TC client software

TC Type

Package

How to Obtain

Sunniwell Android TC ZT3200

Client_for_AndroidTC_ZT3200_vx.x.xxxxx.apk (Client_for_AndroidTC_ZT3200_vx.x.xxxxx.zip extracted from Client_for_AndroidTC_vx.x.xxxxx.zip)

Use the path provided in the version mapping table.

Table 2-27 lists files required for upgrading the Sunniwell TC client.

Table 2-27 Required files

File Type

File Name

How to Obtain

Sunniwell cloud client NMS usage guide

SWTMS_Administrator_Guide_Vx.x.pdf

For enterprise users, click here.

For telecom carrier users, click here.

Download and decompress the FusionAccess TC V100R001C00SPCxxx product documentation (in the decompressed ZT-TCM folder).

  1. Install the ZT3200 CloudClient by referring to in 4 File Management > Upload apk in the SWTMS_Administrator_Guide_Vx.x.pdf.
  2. Upgraded the ZT3200 CloudClient by referring to 2 Device Management > TC Upgrade in the SWTMS_Administrator_Guide_Vx.x.pdf.

Account Management

LiteAD Account Information Overview

Table 2-28 lists the common accounts of LiteAD. For other accounts of FusionAccess, see Account Management > FusionAccess Account Information Overview in the FusionAccessDesktop Solution V100R006C20 System Management Guide.

Table 2-28 LiteAD common accounts

Category

Account Description

Default Account

Account Rights

Domain administrator account

  • It is the domain administrator account. The account is created on the LiteAD server and configured on the FusionAccess Portal.
  • The account is used to monitor alarms for the LiteAD.

Username: set when this account is created, for example, vdesktop\vdsadmin.

Password: set when this account is created.

  • The account has all rights of the domain administrator.
  • The account is used to monitor alarms for the LiteAD.

Domain account

Account generated by the system automatically

  • Username: Administrator

    Account generated by the system automatically, which is disabled

  • Username: Guest

    Account generated by the system automatically, which is disabled

-

Service process account

Account used by a service process

  • Username: krbtgt

    This account is the one used when the Kerberos communication service is running. No password is set by default. Interaction login mode is not supported.

  • Username: dhcpd

    This account is the one used when the DHCP service is running. No password is set by default. Interaction login mode is not supported.

  • The krbtgt account has the permission of running the Kerberos communication service.
  • The dhcpd account has the permission of running the DHCP service.

Collecting Logs

Log Collection Solution
Solution Overview

Collect logs of FusionAccess components in a centralized manner, which gives convenience for system O&M personnel to obtain logs and send logs to log analyst, in case of system faults.

Log Collection Methods

The FusionAccess contains three types of components. Table 2-29 describes the log collection methods for the three types of components.

Table 2-29 Log collection methods

Component Type

Component Name

Log Collection Method

Auxiliary Tool

Linux infrastructure VM

ITA/HDC/WI/License/GaussDB/vAG/vLB/HA/InstallTools/AUS/Backup Server/LiteAD

  • FusionCare
  • WinSCP

User VM

User VM/GPU Render Server

Huawei vDesk

User terminal

TC/SC

TCM

Collecting Logs by Using Tools
Manually Collecting Infrastructure VM Logs Using WinSCP

This section describes how to manually collect the Linux infrastructure VM logs using WinSCP. For details about how to collect the Windows infrastructure VM logs, see Collecting Infrastructure VM Logs Using FusionCare.

NOTE:

File names listed in and Table 2-30 are examples. You need to collect all logs in the file directory of each component.

Table 2-30 Logs of infrastructure components

Component

Directory

File Name

Log Content

How to View

HDC

/var/FusionAccess/HDC

ha.log

Records the high availability (HA) status of the HDC.

  1. Use PuTTY to log in to the infrastructure VM as user gandalf.
  2. Run the following command to disable PuTTY logout on timeout:

    TMOUT=0

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

    su root

  4. Run the following command to create a directory for storing copied log files:

    mkdir directory for storing copied log files

    For example, run the following command to create the /var/FusionAccess/logdownload directory:

    mkdir /var/FusionAccess/logdownload

  5. Run the following command to copy log files to the directory created in 4:

    cp log file directory/log file nametarget directory of log files

    For example, run the following command to copy the xferlog under the /var/log directory to /var/FusionAccess/logdownload:

    cp /var/log/xferlog/var/FusionAccess/logdownload

    NOTE:

    If you want to copy all log files under a directory, change the log file name in the command to *.

  6. Run the following command to change the permission for the directory for storing log files:

    chmod -R 755 directory for storing copied log files

    If the directory for storing log files is /var/FusionAccess/logdownload, run the following command:

    chmod -R 755 /var/FusionAccess/logdownload

  7. Use WinSCP to log in to the infrastructure VM and copy the log files to a local computer.
  8. After the copy is complete, go back to the PuTTY page and run the following command to delete the directory for storing copied log files.

    rm -rf directory for storing copied log files

    If the directory for storing log files is /var/FusionAccess/logdownload, run the following command:

    rm -rf /var/FusionAccess/logdownload

/var/FusionAccess/HDC/hdc/HDC

hdc.log

Includes all module logs of the HDC.

/var/FusionAccess/HDC/tomcat

catalina.out, Catalina.Timestamp.log, host-manager.Timestamp.log, localhost.Timestamp.log, manager.Timestamp.log

Includes the information recorded by Tomcat.

/var/FusionAccess/HDC/backup

*.zip

Backs up the logs of HDC service modules.

WI

/var/FusionAccess/WI

ha.log

Records the HA status of the WI.

/var/FusionAccess/WI/wi/logs/log/VDESKTOP

webui.log

Records all the information related with WI services.

/var/FusionAccess/WI/wi/logs/backup

*.zip

Backs up the logs of WI service modules.

ITA

/var/FusionAccess/ITA

ha.log

Records the HA status of the ITA.

Install.log

Records the ITA installation process.

run.log

Includes the run logs of the ITA.

/var/FusionAccess/ITA/log/ALARM

alarm.log

Records alarm monitoring information.

/var/FusionAccess/ITA/log/AUDIT

audit.log

Functions as an audit log.

/var/FusionAccess/ITA/log/ITAC

itac.log

Functions as an ITAC log.

/var/FusionAccess/ITA/log/MONITOR

monitor.log

Records ITA monitoring and alarm information.

/var/FusionAccess/ITA/log/VDESKTOP

vDesktop.log

Records the core information about the ITA service process.

/var/FusionAccess/ITA/tomcat

*.log

Generated by Tomcat. Assists other logs.

/var/FusionAccess/ITA/backup

*.zip

Backs up log files.

License

/var/FusionAccess/License/log

license.log

Records the information about license service modules.

/var/FusionAccess/License/tomcat

  • catalina.out
  • Catalina.Timestamp.log
  • host-manager.Timestamp.log
  • localhost.Timestamp.log
  • manager.Timestamp.log

Includes the information recorded by Tomcat.

vAG

/var/FusionAccess/VNCGate/logs

gw*.log

Functions as a run log.

AUS

/var/FusionAccess/AUS

install.log

Includes the installation logs of the AUS.

run.log

Includes all module logs of the AUS.

/var/FusionAccess/AUS/logs

AUS.log

Includes the information recorded by Tomcat.

/var/FusionAccess/AUS/tomcat

  • catalina.out
  • Catalina.Timestamp.log
  • host-manager.Timestamp.log
  • localhost.Timestamp.log
  • manager.Timestamp.log

Includes the run logs of the AUS.

BackupServer

/var/log

xferlog

Includes the run logs of the Backup Server.

/var/log

vsftpd

/var/FusionAccess/BackupServer

-

InstallTools

/var/FusionAccess/InstallTools

install[Component name].log

Used for installing components.

uninstall[Component name].log

Used for uninstalling components.

forceUninstall[Component name].log

Used for forcibly uninstalling components.

HA

/var/FusionAccess/HA/GaussDB/halog

gaussdb_ha_timestamp.log

Used for the HA to monitor GaussDB status.

/var/FusionAccess/HA

configITA.log

Used for configuring ITA information.

dbalarm.log

Used for the HA to monitor databases and report database alarms.

hainstall.log

Used for installing the HA.

heartbeatalarm.log

Used for the HA to monitor server heartbeats and report server heartbeat alarms.

hamonitorcron.log

Used for the HA to monitor cron service status.

/var/FusionAccess/HA/ha/runlog

ha.log

Functions as a run log.

ha.log.timestamp.gz

Backs up the HA run log.

/var/FusionAccess/HA/ha/scriptlog

ha.log

Functions as a run log of the script monitored by the HA.

ha.log.timestamp.gz

Backs up the run log of the script monitored by the HA.

ha_monitor.log

Records HA monitoring information.

GaussDB

/var/FusionAccess/GaussDB

dbinstall.log, gaussdbinstall.log

Used for GaussDB installation.

dbconfig.log

Used for active/standby GaussDB configuration.

gaussdb-Timestamp.log

Records the information about GaussDB running.

gs_ctl-current.log

Records the information about gs_ctl that is used to run GaussDB.

gs_guc-current.log

Records the information about gs_guc that is used to run GaussDB.

BackupTools

/var/FusionAccess/BackupTools

backupToolInstall.log

Used for installing the BackupTools.

vdibackup.log

Functions as a run log of the BackupTools.

/opt/BackupTools/log

-

Functions as a backup log of the BackupTools.

LiteAD

/var/FusionAccess/LiteAD

install.log

Functions as an installation log of the LiteAD.

adtool.log

Functions as a configuration log file of the LiteAD.

log.samba

log.samba.old

log.wb-BUILTIN

log.wb-YOUR

log.winbindd-idmap

Functions as a run log of the LiteAD.

rsyncha.log

sambaha.log

dhcpha.log

ntpha.log

Functions as a status monitoring log of the LiteAD.

messages

warn

Functions as a system file of the LiteAD.

Collecting User VM Logs

This section describes how to use the user VM-integrated Huawei vDesk tool to obtain VM logs and quickly locate VM faults.

Procedure
  1. On the user VM, choose Start > All programs > Huawei FusionAccess > Huawei vDesk.

    The Huawei vDesk tool window is displayed.

  2. Click Common Tools, and then click Log Collection Tool.
  3. Obtain the log collection package as prompted by the displayed information.

    The collected user VM logs are stored in C:\HdpLog-[computer name].zip. Table 2-31 shows the log information generated after the log package is decompressed.

    Table 2-31 User VM log description

    Directory

    File Name

    Log Content

    \hdp-sdct-[YearMonthDate]-[HourMinute]\vmlog\

    servicestate.txt

    Indicates service information about the VM.

    hook.txt

    Indicates hook information about the 32-bit VM.

    hook64.txt

    Indicates hook information about the 64-bit VM.

    loadhook.txt

    Indicates whether a hook is loaded for the 32-bit VM.

    loadhook64.txt

    Indicates whether a hook is loaded for the 64-bit VM.

    hda.txt

    Indicates registry information about the 32-bit VM.

    hda64.txt

    Indicates registry information about the 64-bit VM.

    path.txt

    Indicates the environment variable.

    autorun.txt

    Indicates the startup item.

    hdpfs.txt

    Indicates file redirection information.

    softwarelist.txt

    Indicates the list of VM software.

    hardwareinfo.txt

    Indicates VM hardware information.

    \hdp-sdct-[YearMonthDate]-[HourMinute]\computer-config\

    etc-hosts.txt

    Contains the system host information, which is used to analyze host network problems.

    firewall.txt

    Contains the system firewall configuration information, which is used to analyze host network problems.

    ipconfig-all.txt

    Contains the system IP address configuration information, which is used to analyze host network problems.

    net-start.txt

    Contains the open port information of a system, which is used to analyze host network problems.

    netstat-an.txt

    Contains the system active port information, which is used to analyze host network problems.

    route-print.txt

    Contains the system route information, which is used to analyze host network problems.

    set.txt

    Contains the system environment variable information, which is used to analyze software compatibility problems.

    systeminfo.txt

    Contains the basic system information, which is used to analyze performance and software compatibility problems.

    tasklist-svc.txt

    tasklist-v.txt

    ver.txt

    Contains the operating system (OS) version information, which is used to assist with problem analysis.

    \hdp-sdct-[YearMonthDate]-[HourMinute]\TraceLog\Archive\

    TraceKernel_[YearMonthDate]-013518.log

    Contains the driver logs of all redirection modules (including communication, mouse, keyboard, monitor, audio, multimedia, and peripherals), which are used to analyze internal problems of modules.

    TraceLog_[YearMonthDate]-013518.log

    \hdp-sdct-[YearMonthDate]-[HourMinute]\TraceLog\

    TraceKernel_0.log

    Contains the historical backup files of driver logs of all redirection modules.

    TraceLog_0.log

    \hdp-sdct-[YearMonthDate]-[HourMinute]\vdm-config\

    policies-reg.txt

    Contains the information related to group policies in the registry, which is used to analyze software compatibility problems.

    win-authentication-reg.txt

    Contains the add-in configuration of Windows authentication modules in the registry, which is used to analyze automatic login problems.

    win-policies-reg.txt

    Contains the configuration related to Windows group policies in the registry, which is used to analyze software compatibility problems.

    win-winlogon-reg.txt

    Contains the system login configuration in the registry, which is used to analyze automatic login problems.

    \hdp-sdct-[YearMonthDate]-[HourMinute]\vdm-event-logs

    Application-log.evt

    Contains the Windows event logs, which are used to analyze system problems or compatibility problems.

    Security-log.evt

    System-log.evt

    \hdp-sdct-[YearMonthDate]-[HourMinute]\

    ginalog.txt

    Contains the operation logs of the GINA or CredentialProvider module, which are used to analyze internal problems of the module.

    hdp-sdct.log

    Contains the operation logs (summary) of log collection tools.

    hdp-sdct-contents.txt

    Contains the lists of information collected by log collection tools.

    hdp-sdct-full.log

    Contains the operation logs (details) of log collection tools.

    hdp-sdct-ver.txt

    Contains the software version information of log collection tools.

    run.log

    Contains the VM provisioning process logs, which are used to analyze VM provisioning problems.

    vdi.server.log

    Contains the operation logs (summary) of the MainService module, which are used to analyze connection problems.

    vdi.server.statistic

    Contains the operation logs (statistics) of the MainService module, which are used to analyze connection problems.

    vdi.server.trace

    Contains the operation logs (details) of the MainService module, which are used to analyze connection problems.

Collecting User Terminal Logs

This section describes how to collect the user terminal logs.

Procedure
NOTE:

The Centerm TCM is used as an example in the following operations.

  1. Log in to the Thin Client Manager (TCM) management program, and click the Log Extraction tab.

    If a PC is used as a software client (SC), directly obtain logs from C:\Hdp Log on the PC, and skip over the following operations:

  2. Select the applications named as HDP, select the client whose logs are to be collected, and click Executive Collection.

    NOTE:

    If no HDP applications exist, add the HDP application.

    Logs are collected as prompted.

  3. Click the Log Download tab, and click File Download.
  4. View the downloaded log files by using a text editor.
Collecting Logs Manually
Collecting Windows VM Logs

In scenarios where the tool cannot be used, you are advised to manually collect VM logs.

Table 2-32 describes log information about Windows user virtual machines (VMs).

Table 2-32 Windows VM logs (user VM)

Directory

File Name

Log Description

How to View

C:\Program Files\Huawei\HDPServer\

vdi.server.log vdi.server.log.*

Registration and login process logs

View the logs using a text editor.

C:\Program Files\Huawei\HDPServer\

gina.log

Graphical Identification and Authentication (GINA) logs

View the logs using a text editor.

C:\Program Files\Huawei\HDPServer\TraceLog

TraceLog-[time].etl

Service redirection logs (including communication, mouse, keyboard, audio, multimedia, and peripherals)

Convert the logs into text logs using ETConverter, and view the logs using a text editor.

C:\Program Files\Huawei\HDPServer\TraceLog

TraceKernel-[time].etl

Driver redirection logs (including communication, mouse, keyboard, audio, multimedia, and peripherals)

Convert the logs into text logs using ETConverter, and view the logs using a text editor.

C:\Program Files\Huawei\HDPServer\TraceLog\Archive

TraceLog-[time].etl.zip

Service redirection log archive (including communication, mouse, keyboard, audio, multimedia, and peripherals)

Convert the logs into text logs using ETConverter, and view the logs using a text editor.

C:\Program Files\Huawei\HDPServer\TraceLog\Archive

TraceKernel-[time].etl.zip

Driver redirection log archive (including communication, mouse, keyboard, audio, multimedia, and peripherals)

Convert the logs into text logs using ETConverter, and view the logs using a text editor.

C:\HdpLog\dump

*.dmp

Application exception logs

Analyze the logs using WinDbg.

Collecting Windows Terminal Logs
TC

Table 2-33 describes log information about the Windows thin client (TC).

Table 2-33 Windows TC logs

Directory

File Name

Log Description

How to View

C:\HdpLog\ClientLog

ClientLog-[session name]-[time].txt

Client program run logs

View the logs using a text editor.

C:\HdpLog\DumpLog

*.dmp

Application exception logs

Analyze the logs using WinDbg.

SC

Table 2-34 describes log information about the Windows software client (SC).

Table 2-34 Windows SC logs

Directory

File Name

Log Description

How to View

C:\HdpLog\ClientLog

ClientLog-[session name]-[time].txt

Client program run logs

View the logs using a text editor.

C:\HdpLog\DumpLog

*.dmp

Application exception logs

Analyze the logs using WinDbg.

Collecting Linux Terminal Logs
TC

Table 2-35 describes log information about the Linux thin client (TC).

Table 2-35 Linux TC logs

Directory

File Name

Log Description

How to View

/var/log/hdplog/clientlog or /usr/local/HDPClient/log/clientlog

ClientLog-[session name]-[time].txt

Client program run logs

View the logs using a text editor.

Translation
Download
Updated: 2019-04-25

Document ID: EDOC1100010651

Views: 26161

Downloads: 162

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