1.1 Symptom
The equipment room where the desktop cloud management system resides is powered off, which affects the VM login.
1.2 Troubleshooting Guideline
1. Identify the cause of system power-off, and ensure that power supply devices and air conditioners are running properly.
2. Power on the FusionCloud system.
1.3 Troubleshooting
Power on the FusionCloud devices one by one. Maximally ensure device security, and make sure that all services are running properly. FusionCloud power-on sequence: FusionCompute > FusionManager > FusionAccess.
1.3.1 Powering on FusionCompute
Powering on the cabinet.
1. Set the power switch on the power distribution unit (PDU) of the cabinet to ON.
2. Set the power switch on all switches to ON.
3. Power on the storage devices.
If a host is managing storage devices, power on the host after powering on the storage devices.
Powering on VRM nodes.
4. After powering on the storage system, press the power button of the host where the active and standby virtualization resource management (VRM) nodes are located.
l If the VRM node is a server, press the power button of the VRM server to power on it.
l If the VRM is a VM, the VRM VM starts after the host on which the VRM VM is deployed is powered on.
Powering on all hosts through FusionCompute
5. Log in to FusionCompute.
6. On FusionCompute, click Computing Pool.
The Compute Pool page is displayed.
7. In the navigation tree on the left, choose Site > ManagementCluster.
The hosts under the cluster are displayed.
8. Right-click Host and select Power on.
9. Power on all the powered-off hosts. For details, see step7 and step 8.
1.3.2 Powering on FusionManager
1. Log in to FusionCompute.
2. On FusionCompute, click VM and Template. The VM and Template page is displayed.
3. On the VM tab page, enter the FusionManager VM name and click Search. The search results are displayed.
4. In the row where the FusionManager VM is located, click Start.
A dialog box is displayed.
5. Click OK. A dialog box is displayed.
6. Click OK. The VM is powered on if its status changes to Running.
To update the VM status, click 
on
the top of the VM list.
7. Check whether FusionManager is deployed in active/standby mode.
If yes, go to Step 8.
If no, no further action is required.
8. Repeat the operations from step 1 to step 6 to power on the standby FusionManager node.
1.3.3 Powering on FusionAccess
Starting the infrastructure VMs.
1. Log in to FusionCompute.
2. Go to the VM and Template page, and click VM tab page.
Start FusionAccess infrastructure VMs in the following sequence:
l AD/DNS/DHCP
l GaussDB/WI/HDC/License
l ITA
l Loggetter/TCM/AntiVirus/Patch
l VAG/VLB
3. In the row of the target VM, choose Operation > Start.
4. Click OK twice.
5. Ensure that the status of each FusionAccess infrastructure VM is Running.
Desktop cloud services are restored after all infrastructure VMs start, which takes about 15 minutes.
Starting user VMs.
User VMs do not need to be started. When a user clicks a user VM on the WI login page, the user VM starts automatically.
1.3.4 Verifying Services
1. Log in to a user VM through the WI, and the user virtual desktop can be normally used.
2. On FusionCompute, choose Monitoring > Alarm > Alarms > Real-Time Alarms, and view the newly generated alarms.
Click corresponding alarms to view their details. Click alarm IDs and clear alarms according to the Alarm Help.
3. On FusionAccess, choose Alarm > System Alarm, and view the newly generated alarms.
Click corresponding alarms to view their detailed information. Click alarm IDs and clear alarms according to the Alarm Help.
