how to manage virtual machine on FusionCompute V1R5C00

The alarm module verifies the license validity during the hours from 00:00 to 02:00 every day. This alarm is generated when the license file verification fails or the system fails to obtain the equipment serial number (ESN). This alarm is cleared when a valid license file is loaded to the system. Check whether the system can obtain the ESN successfully. On the FusionCompute, choose System > System Configuration > License Management and click Load License File. On the Load License File page, click Obtain ESN and check whether the system can obtain the ESN successfully. If yes, go to Step 2. If no, contact technical support. Check whether the device on which the VRM is deployed is replaced. Have the administrator check whether the device on which the VRM is deployed is replaced. If yes, obtain the new ESN and apply for a license based on the new ESN. For details about how to apply for a license, see the FusionCompute License Usage Guide. Visit Product Support > IT > FusionCloud > FusionSphere > FusionCompute to Obtain. If no, go to Step 3. Update the available license file. Check whether the license file is available. If yes, go to Step 5. If no, go to Step 4. Apply for a license. For details, see the FusionCompute License Usage Guide. visit http://support.huawei.com/enterprise, and choose Product Support > IT > FusionCloud > FusionSphere > FusionCompute to Obtain. Updating the License File. After 5 or 6 minutes, choose System > System Configuration > License Management and check whether the license information is correct and whether the alarm is cleared.

This alarm is generated when the system detects that the monitoring processing process pmcd has stopped or is faulty. This alarm is cleared when the pmcd process becomes normal. Identify the management IP address of the node for which the alarm is generated. On the FusionCompute portal, click Monitoring, and choose Alarm in the navigation tree on the left. On the Alarm page, locate the row that contains the alarm and click the name in the Alarm Object column. The Service and Management Node page is displayed. On the Service and Management Node page, view information about the management nodes and obtain the IP address of the node whose name is the same as that of Alarm Object in Step 1. Restart the process of the performance management center. Use PuTTY to log in to the node. Ensure that the management IP address and username gandalf are used to establish the connection. Run the following command and enter the password of user root to switch to user root: su - root Run the following command to restart the process: service pmcd restart NOTE: Restarting the process may cause temporary interruption of monitoring processing service. Run the following command to check the process status: service pmcd status Check whether the command output is as follows: Checking for pmcd: running If yes, go to Step 8. If no, go to Step 9. After 3 or 4 minutes, switch to the Alarm page and check whether the alarm is cleared.

This alarm is generated when the system detects that the performance monitoring process on management nodes has stopped or is faulty. This alarm is cleared when the performance monitoring process becomes normal. Identify the IP address of the object for which the alarm is generated. On the FusionCompute portal, click Monitoring, and choose Alarm in the navigation tree on the left. On the Alarm page, locate the row that contains the alarm and click the name in the Alarm Object column. The Service and Management Node page is displayed. On the Service and Management Node page, view information about the management nodes and obtain the IP address of the node whose name is the same as that of Alarm Object in Step 1. Restart the performance monitoring process on management nodes. Use PuTTY to log in to the node. Ensure that the management IP address and username gandalf are used to establish the connection. Run the following command and enter the password of user root to switch to user root: su - root Run the following command to restart the process: service pmad restart NOTE: Restarting the process may cause temporary interruption of the performance monitoring service. Run the following command to check the process status: service pmad status Check whether the command output is as follows: Checking for service pma running If yes, go to Step 8. If no, go to Step 9. After 3 or 4 minutes, switch to the Alarm page and check whether the alarm is cleared.

The system periodically detects the usage of available resources on management nodes. This alarm is generated when the ratio of used resources to available resources hits 95%. This alarm is cleared when the ratio is less than 95%. Confirm the IP address of the faulty node. On the FusionCompute portal, click Monitoring, and choose Alarm in the navigation tree on the left. On the Alarm page, locate the row that contains the alarm and click the name in the Alarm Object column. The Service and Management Node page is displayed. On the Service and Management Node page, view information about the management nodes and obtain the management IP address of the node whose name is the same as that of Alarm Object in Step 1. Rectify the fault. Use PuTTY to log in to the faulty node. Ensure that the management IP address and username gandalf are used to establish the connection. Run the following command and enter the password of user root to switch to user root: su - root Run the following command to query the inode usage of each disk: df -i Information similar to the following is displayed: vrm4050:~ # df -i Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sda1 655360 51954 603406 8% / devtmpfs 0 0 0 - /dev tmpfs 2036905 1 2036904 1% /dev/shm /dev/sda5 1245184 11 1245173 1% /drbd0 /dev/sda6 65280 11 65269 1% /drbd1 /dev/sda7 70416 11 70405 1% /drbd2 /dev/sda8 70416 11 70405 1% /drbd3 /dev/sda9 262144 11 262133 1% /swap /dev/sda10 58671104 3104 58668000 1% /var NOTE: Filesystem: specifies the name of a disk partition. Inodes: specifies the total number of inodes in a disk. IUsed: specifies the number of inodes used. IFree: specifies the number of free inodes. IUse%: specifies the usage of inodes. Mounted on: specifies the directory to which the disk is attached. Enter the directory that contains the alarm object, and delete the files that are unnecessary or that you have copied. NOTICE: File deletion is a high-risk operation. Therefore, ensure that the files to be deleted are not system files or important files involving service running. After 10 or 15 minutes, check whether the alarm is cleared.

The system periodically detects the logical disk usage of nodes. This alarm is generated when the logical disk usage hits 95%. This alarm is cleared when the logical disk usage is less than 95%. Confirm the IP address of the faulty node. On the FusionCompute portal, click Monitoring, and choose Alarm in the navigation tree on the left. On the Alarm page, locate the row that contains the alarm and click the name in the Alarm Object column. The Service and Management Node page is displayed. On the Service and Management Node page, view information about the management nodes and obtain the IP address of the node whose name is the same as that of Alarm Object in Step 1. Confirm and clear files in the directory that contains the logical disk for which the alarm is generated. Use PuTTY to log in to the faulty node. Ensure that the management IP address and username gandalf are used to establish the connection. Run the following command and enter the password of user root to switch to user root: su - root Query the directory that contains the disk for which the alarm is generated, and run the following command to view the usage of each disk directory: df -l Information similar to the following is displayed: VRM8810:~ # df -l Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 10317828 1572360 8221352 17% / devtmpfs 8147620 212 8147408 1% /dev tmpfs 8147620 0 8147620 0% /dev/shm /dev/sda6 1027768 17912 957648 2% /etc/galax /dev/sda10 880874308 204948 835923520 1% /extend /dev/sda8 1106800 34188 1016388 4% /opt/galax/upgrade /dev/mapper/vg_vrm-lv_gaussdb 18578172 870716 16763740 5% /opt/gaussdb /dev/sda5 18572112 392648 17236052 3% /var /dev/mapper/vg_vrm-lv_backup 30834692 176196 29092188 1% /var/backup NOTE: Filesystem: specifies the name of a disk partition. 1K-blocks: specifies the disk capacity. Used: specifies the used disk capacity. Available: specifies the available disk capacity. Use%: specifies the disk directory usage. Mounted on: specifies the directory to which the disk is attached. Enter the directory where the alarm object locates, and delete the files that are unnecessary or that you have copied. NOTICE: File deletion is a high-risk operation. Therefore, make sure that the files to be deleted are not those that are stored in the system directory or in the directory that contains important in-use services. After 10 or 15 minutes, check whether the alarm is cleared.