H3C Workspace Cloud Desktop
Routing Inspection Guide

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Document version: 5W101-20240801

 

Contents

About routine inspection· 1

Restrictions and guidelines for routine inspection· 1

System security· 1

Data security· 1

Operation security· 1

Maintenance guidelines· 1

Inspection cycle and items· 2

Severity levels· 2

Inspection tools· 2

About inspection tools· 2

Restrictions and guidelines· 3

Applicable software versions· 3

Technical support 3

Routine inspection flow· 4

Performing a routine inspection· 5

Inspecting alarms· 5

Inspecting real-time alarms· 5

Inspecting VIP desktops alarms· 6

Inspecting gateway alarms· 7

Performing one-click inspection· 7

Performing inspection with the routing inspection tools· 11

Prerequisites· 11

Using the toolkit 12

 

About routine inspection

The purpose of routine inspections is to reduce system risks and ensure that the system can operate safely, stably, and reliably in the long term. This guide is intended for operations and maintenance engineers, and it primarily describes the inspection items and operating procedures for H3C Workspace products.

Restrictions and guidelines for routine inspection

System security

·     The system administrator must safeguard the management-level passwords and change the passwords regularly.

·     Strictly control the permissions of different user roles to ensure minimal permissions.

Data security

·     Regularly back up system data.

·     Data modification must be authorized and controlled.

·     Maintenance personnel must back up data and record changes before modifying data.

·     Maintenance personnel must record significant operations (such as primary/backup switchovers and system resets), carefully verify feasibility before operation, and perform appropriate data backups, emergency recovery, and security measures.

Operation security

·     Wear ESD wrist straps and ensure reliable grounding before performing hardware operations on devices.

·     Store the replaced hardware components in ESD bags.

Maintenance guidelines

·     Maintenance personnel must attach importance to routine maintenance, refer to the inspection recommendations in this manual, and regularly check and test devices while keeping records.

·     In case of difficult problems during the inspection process, first record all kinds of raw information in detail, and then contact H3C Support.

Inspection cycle and items

Perform routine inspections regularly, such as on a daily or weekly cycle, and use inspection tools in case of faults or major online issues.

Table 1 Recommended inspection cycle and items

Inspection cycle	Inspection items
Daily	Alarms
	One-click inspection
Weekly	Inspection tools

 

Severity levels

The severity level indicates the impact of each non-conforming item on the system or business during an inspection, helping maintenance personnel determine whether emergency handling is required. The severity level includes critical, major, and minor.

Table 2 Severity levels

Severity level	Description	Emergency handling
Critical	Urgent inspection items that have a high probability of causing abnormal core product functions, business interruption, or data loss, and require immediate rectification.	Yes
Major	Key inspection items that can potentially cause partial functional degradation of the product or pose risks such as business interruption and data loss, and require special attention and rectification.	No
Minor	Inspection items that do not pose risks such as business interruption or data loss, but their configuration and status do not meet optimal recommended requirements. The inspection items potentially lead to common faults and require handling according to the corresponding inspection item's instructions.	No

 

Inspection tools

About inspection tools

Space Console is becoming increasingly complex, with the addition of the ONEStor product for HCI deployment, posing various risks during operation. To ensure the correct operation of the platform, inspections of nodes are required after fault handling and changes. Manual inspections by operation and maintenance engineers are time-consuming, tedious, and prone to omissions or errors.

WorkspaceToolkit is an automated toolkit that aims to improve operational efficiency and promptly detect hidden problems in Space Console. It also reduces the complexity of manual inspections and avoids human errors.

Restrictions and guidelines

WorkspaceToolkit is currently limited to internal use only. To ensure the stable operation of customer businesses, email reminders will be sent every week for inspection items that have not passed and have not been rectified. You cannot cancel these reminders until the environment is rectified. Use with caution if you have concerns about this.

WorkspaceToolkit collects certain data from the site environment, such as hosts, VMs, and storage pools. If you are sensitive about this data, use the data anonymization function. When prompted with Will you collect all information: 1 (yes) or 0 (no), select 0 (no), and only inspection item checks will be performed.

Applicable software versions

All officially released E1xxx versions of Workspace support the inspection tools.

This document is intended for WorkspaceToolkit v2.8.10 and earlier versions.

Technical support

WorkspaceToolkit is a convenient automated inspection tool (currently available for free) and does not include any technical support services. In case of any tool-related issues during working hours (5 × 8), you can call the 400 hotline to address high-risk issues identified by the tool. However, the 400 hotline does not guarantee response times for problem resolution.

Routine inspection flow

Figure 1 Routine inspection flow

 

Table 3 Routine inspection tasks

Task	Description
Examine the software version	Log in to Space Console, click the arrow in the upper right corner, and select About from the expanded menu options.
Back up data	Log in to Space Console, click Back Up on the management data backup page.
Perform routine inspection and record the result	1.     ‍Use WorkspaceToolkit to inspect Space Console. 2.     Examine the inspection results. If an inspection item fails, check the inspection logs and reference the inspection report to confirm details about the failed inspection item.
Risks are detected	Contact H3C Support to troubleshoot potential issues and provide a product inspection report after resolving any problems. The reporting format is Site Name_H3C_VDI Product Inspection Report_Date.
No risks are detected	Provide a routine inspection report.

 

Performing a routine inspection

The images presented in this article are for illustrative purposes only. Please refer to the actual situation of the Workspace version for specific details.

Inspecting alarms

Inspecting real-time alarms

The real-time alarm function is used to display alarms generated by the system during the recent period, and it supports analyzing the cause of an alarm and providing recovery suggestions. For example, when a business VM fails during daily operation and maintenance, an operator can use the real-time alarm function to view the alarm information of the VM. After understanding the cause of the alarm and recovery suggestions, the operator can take measures to deal with the VM.

 

NOTE: By default, the refresh frequency of real-time alarm information is 10 seconds. At the refresh interval, the system automatically refreshes the real-time alarm list. If the refresh interval is too short, an operator might not have enough time to perform the confirmation operation. Therefore, to facilitate the operator's alarm confirmation operations, set the refresh interval appropriately.

 

1.     From the left navigation pane, select System > Alarms > Real-Time Alarms tab.

Figure 2 Real-time alarms

 

2.     Click an alarm message to view detailed alarm information. The system will display the cause and recovery suggestions of the alarm, and users can edit maintenance experience.

Figure 3 Alarm details

 

3.     Select the alarms you have processed, and then click Acknowledge.

Figure 4 Acknowledging alarms

 

Inspecting VIP desktops alarms

The VIP desktop alarm function is used to manage desktop alarm information that meets the VIP desktop alarm policy. For example, alarms are generated for the VIP desktop usage over 80%, the system disk usage over 80%, the memory usage over 80%, desktop shutdown, or desktop status exception. If the administrator enables alarm email notification, and a VIP desktop has an exception (such as abnormal status or resource overload), the administrator will receive real-time notification via email for timely monitoring.

Figure 5 VIP desktop alarms

 

Inspecting gateway alarms

The gateway alarm function is used to manage alarm information that meets the gateway alarm policy. For example, an alarm is generated when the gateway connection failure times reach the configured value within the set detection interval. If the administrator enables alarm email notification or alarm SMS notification, the gateway alarm will be notified to the administrator via email or SMS for timely monitoring.

Figure 6 Gateway alarms

 

Performing one-click inspection

The one-click inspection function of Space Console is used to check the following contents of the current system to help administrators quickly understand the operating status, performance, and potential risks of the VM environment. For indicators with abnormal detection results, the system will provide effective improvement suggestions to ensure the stable and reliable operation of the business system.

·     System inspection—Inspect the running status of Space Console resources and basic services.

·     Cloud desktop inspection—Check the status of cloud desktops and clients.

·     Compute resource inspection—Inspect the running status of virtual resources.

·     Storage resource inspection—Inspect storage resources, Space Console disk space, and user storage status.

·     Network resource inspection—Inspect the configuration and running status of physical networks and virtualization networks.

·     Desktop image inspection—Check the status of desktop images.

·     Stateful failover service inspection—Inspect the reliability of the stateful failover service.

To perform one-click inspection:

1.     Log in to Space Console. Click  in the top right corner of the page.

Figure 7 One-click inspection

 

2.     Select the check items, and then click Start. After completing the check, the system displays the check results and details for all check items by default.

Figure 8 Starting inspection

 

Table 4 Inspection items and severity levels

Category	Inspection item	Description
System	Back-End Service Component State	Checks the state of the resources and basic services of the Space Console
	Controller Service Component State
	Virtualization Service Component State
	Cloud Disk Service Component State
	Campus Space Service Component State
	Host Resource Alarms
	Critical Alarms
	Redis Service
	Host and HostAgent State
	CPU Overcommitment
	Memory Overcommitment
	Storage Overcommitment
	System Partition Usage
	NTP Settings
	System Data Backup Settings
	Alarm Notification Configuration State
	License Registration State
	Samba Service Component State
Scan Cloud Desktops	Cloud Desktop State	Checks cloud desktop and client state
	Client Version
	Student Client-Cloud Desktop Connection State
Compute	Compute Node State	Checks virtual resource running state
	CPU State
	Memory State
	DRS Configuration
	QXL State
	Course Graphics Card Configuration Check
	GlusterFS Replica Count Check
Storage	Teaching Scenario SSD Space and State	Checks storage resource state, state of the disk space on Space Console, and user storage state
	System Disk Cache State
	RAID Controller State
	Logical Disk State
	Physical Disk State
	Storage Usage State
	Image Pools State
	Upload/Download Temporary Directory State
	Upload Directory for Endpoint Image State
	Course Disk Path Check
	Disk Performance Check
Network	Cloud Desktop Network Deployment	Checks configuration and running states of physical and virtual networks
	Physical NIC State
	vPort State
	Network Service Process
	Packet Loss Info
	Host Route Check
	Aggregation State Check
	Network Connectivity Check
	Subnet Mask Consistency Check
	MTU Consistency Check
	Teaching Scenario Cloud Desktop Network
	Course MTU Check
Desktop Image Check	Desktop Image State
Stateful Failover Service Check	Database Shared Storage State	Checks availability of the stateful failover service
	Shared Storage Space Check

Figure 9 Inspection results

3.     To view the check results and details about abnormal check items, click the Abnormal tab.

4.     To view what is checked and recommended actions for a specific check item, click the item.

Figure 10 Abnormal check items

 

Performing inspection with the routing inspection tools

Prerequisites

Preparing login information

Prepare the following information in advance:

·     The management network IP address of the Space Console management node.

·     The root user's password.

·     An SSH login tool.

Downloading the toolkit

Download the latest WorkspaceToolkit package from the technical support FTP server. This tool is valid for three months from the release date. When running the tools, you can see the tool release time. If the validity period has expired, the tools will not work, and you will be prompted to download the latest version. If you have any questions, contact H3C Support.

Downloading and decompressing the toolkit

1.     Use the root account to upload the toolkit package to the primary management node from the command line.

2.     Execute tar -xvf WorkspaceToolkit-V2.4.tar.gz to decompress the package. This step uses version V2.4 as an example, as shown in the following figure.

Figure 11 Decompressing the WorkspaceToolkit package

 

Using the toolkit

Performing routing inspection

1.     Enter the directory where the toolkit package is extracted, for example, cd WorkspaceToolKit-V2.4/.

2.     Run WorkspaceToolkit, for example, execute sh WorkspaceToolKit.sh. The interface will prompt Will you collect all information: 1 (yes) or 0 (no). Enter 1 to collect all information in the site, or enter 0 to only perform inspection item checks. Then, the script will start running. After the script execution is complete, it will prompt Workspace Routine check successfully!.

Figure 12 Performing routine inspection

 

Examining the inspection results

1.     WorkspaceToolkit is run, it will prompt that the iservice package file will be saved in the /var/WorkspaceToolKit directory, for example, VDI_20220824102815.zip, as shown in the following figure.

Figure 13 Path for saving inspection results

 

2.     View the inspection log files stored in the /var/WorkspaceToolKit/log/check/ directory, such as iservice_log_20220824102815.zip. The log file contains the inspection results for each host and the logs of running the inspection tools on each host. It can be used to troubleshoot when the inspection tool execution fails.

Figure 14 Path for saving the inspection logs

 

3.     Log in to the primary management node from the command line, retrieve the zip file from the /var/WorkspaceToolKit directory, and save it to your local computer.

4.     Import the inspection log file to the iService website for parsing and obtain the inspection report.