Description

After the HDC service, it checks the heartbeat information from the APS server every 2 minutes. The heartbeat information includes the CPU usage, memory usage, disk usage, APS service status, and number of sessions. The HDC reports this alarm to the ITA when detecting that the memory usage of the APS server exceeds the alarm threshold (80% by default) for three consecutive times. This alarm is cleared when the memory usage is less than the threshold.

Attribute

Parameters

Impact on the System

The APS service is affected and may become abnormal.

Possible Causes

• A faulty APS server exists.
• The APS server has excessive sessions.
• The APS server is not restarted for a long time.
• The APS server has insufficient resources.

Procedure

Check whether a faulty APS server exists

1. Choose FusionAccess > Desktop > All Computers to check the application group to which the server belongs.
2. In Application Group in the navigation tree, find the information about the application group in Step 1.
3. Select the application group and click View VM.
4. Check other servers in the application group to see whether any unregistered server exists?
   • If yes, go to Step 5.
   • If no, go to Step 7.

5. See 2000006 APS Is Not Registered to register the APS server.
6. Observer for a period, for example, one week, and choose FusionManager > Monitoring or FusionAccess > Alarm to check whether the alarm exists.
   • If yes, go to Step 7.
   • If no, no further operation is required.

Check whether the APS server has excessive sessions

7. Choose FusionAccess > Desktop > All Computers to check the number of sessions of the server. Check whether the number of sessions is close to the threshold.
   • If yes, go to Step 8.
   • If no, go to Step 12.

8. Choose FusionAccess > Desktop > Policy Management > Published to check whether the AutoDisconnection policy is set (Automatic screen lock and Automatic disconnection are enabled) and applied to the application group.
   • If yes, go to Step 12.
   • If no, go to Step 9.

9. You are advised to enable the AutoDisconnection policy and enable the Automatic screen lock and Automatic disconnection functions, and apply these settings to the application group.
10. You are advised to restart the server in idle hours.
11. Observer for a period, for example, one week, and choose FusionManager > Monitoring or FusionAccess > Alarm to check whether the alarm exists.
    • If yes, go to Step 12.
    • If no, no further operation is required.

Check whether the APS server is not restarted for a long time

12. In FusionCompute, use an existing domain account in the environment to log in to the server for which the alarm is generated by VNC.
13. Right-click the start menu. (Use Windows Server 2012 an example.)
14. In the Run text box, enter cmd.
15. Run the systeminfo command and check System Boot Time in the command output.
16. Check whether the server runs for a long time, such as a week?
    • If yes, go to Step 17.
    • If no, go to Step 19.

17. You are advised to restart the server in idle hours.
18. Observer for a period, for example, one week, and choose FusionManager > Monitoring or FusionAccess > Alarm to check whether the alarm exists.
    • If yes, go to 19.
    • If no, no further operation is required.

Check whether the APS server has insufficient resources

19. Choose FusionAccess > Statistics > Performance Statistics to observer the servers in the application group to check whether the memory usage of the server is close to the threshold.
    • If yes, capacity expansion is recommended.
    • If no, contact technical support.

Related Information

None