Virtualization Solution

Question

How do I log in to FusionCompute?

Answer

The supported browser versions are as follows: Internet Explorer 11, Firefox 67 to 69, and Google Chrome 75 to 77.

1. Access the FusionCompute login page at https://VRM node IP floating address:8443.

   The IP address of VRM is the management IP address configured on the VRM node. If the node is deployed in a cluster, the IP address is set to the floating IP address of the cluster. If the node is deployed in single-node mode, the IP address is set to the management IP address of the single node.

2. Enter the username and password. If the first login fails, enter the verification code, select User type and Login type, and click Login.

   Username: The initial username is admin.

   Password: Enter the actual password. For security purposes, change the password regularly and keep the new password confidential.

Question

How do I log in to a VM using VNC?

Answer

The supported browser versions are as follows: Internet Explorer 11, Firefox 67 to 69, and Google Chrome 75 to 77.

1. Log in to FusionCompute. For details, see How Do I Log In to FusionCompute?
2. Choose Resource Pools > Management Cluster > CNA_01 > Host name from the navigation pane.
3. Right-click the target host and choose Log In Using VNC from the shortcut menu.

Question

The following error message is displayed during the import of a VM template. How do I remove the error?

Answer

To remove the error, disable the pop-up blocker of the browser and add the VRM floating IP address of FusionCompute as an exception.

• Mozilla Firefox
  1. Choose Options > Content.
  2. Unselect the Turn on Pop-up Blocker check box.

  3. Add a permitted site address.

• Google Chrome
  1. Choose Settings > Show advanced settings > Privacy > Content settings > Pop-ups.
  2. Select Allow all sites to show pop-ups and click Manage exceptions.

  3. Add the desired site address.

• Internet Explorer
  1. Choose Internet Options > Privacy.
  2. Select the Turn on Pop-up Blocker check box.

  3. Click Settings.

  4. Add the desired IP address.

Question

What do I do if storage device detection fails when data stores are added on FusionCompute?

Answer

When the host uses local disks with residual LVM information, the host fails to detect storage devices that map to storage resources.

Check whether the undetected storage device is mapped to the host.

1. Ensure that user name gandalf and the management IP address are used to establish the connection through SSH.
2. Run the su root command to switch to the root user. The password is the one set during the CNA installation.

   # su root

3. Run the following command to disable user logout upon system timeout:

   # TMOUT=0

4. Check whether the undetected storage device serves as a shared disk.
   1. If the undetected storage device serves as a shared disk, go to 5
   2. If the undetected storage device does not serve as a shared disk, go to 9.
5. Determine which multipathing mode is used as the storage path of the shared disk.
   1. If universal multipathing is used, go to 6.
   2. If Huawei multipathing is used, go to 7.
6. Check whether the undetected storage device is mapped to the host.

   # multipath -ll 

   Information similar to the following is displayed:

   • Obtain the world wide name (WWN) of the undetected storage device based on its name, make a note of the WWN (for example, 6925805100a122002ae31e4e0000006e), and go to 8
   • If the undetected storage device is not mapped to the host, check whether the storage device is correctly configured.

     36925805100a122002ae31e4e0000006e dm-6 HUASY,S5600T
     size=20G features='1 queue_if_no_path' hwhandler='0' wp=rw
     `-+- policy='round-robin 0' prio=1 status=active
       |- 7:0:0:8  sdi  8:128  active ready running
       |- 8:0:0:8  sdq  65:0   active ready running
       |- 9:0:0:8  sdy  65:128 active ready running
       |- 10:0:0:8 sdag 66:0   active ready running
       |- 11:0:0:8 sdao 66:128 active ready running
       |- 12:0:0:8 sdaw 67:0   active ready running
       |- 13:0:0:8 sdbe 67:128 active ready running
       `- 14:0:0:8 sdbm 68:0   active ready running
     36925805100a1220006b8b70500000064 dm-4 HUASY,S5600T
     size=10G features='1 queue_if_no_path' hwhandler='0' wp=rw
     `-+- policy='round-robin 0' prio=1 status=active
       |- 7:0:0:2  sde  8:64   active ready running
       |- 8:0:0:2  sdm  8:192  active ready running
       |- 9:0:0:2  sdu  65:64  active ready running
       |- 10:0:0:2 sdac 65:192 active ready running
       |- 11:0:0:2 sdak 66:64  active ready running
       |- 12:0:0:2 sdas 66:192 active ready running
       |- 13:0:0:2 sdba 67:64  active ready running
       `- 14:0:0:2 sdbi 67:192 active ready running

7. Run the following command to check whether the undetected storage device is mapped to the host:

   # upadmin show vlun 

   Information similar to the following is displayed:

   1. Obtain the WWN of the undetected storage device based on its name, make a note of the WWN (value in the Lun WWN column), and go to 8.
   2. If the undetected storage device is not mapped to the host, check whether the storage device is correctly configured.

      ------------------------------------------------------------------------------------------------------------------------------------ 
      Vlun ID      Disk             Name                     Lun WWN                     Status Capacity Ctrl(Own/Work)        Array Name 
           0         sdc            LUN_019        6925805100a12200000af4ee00000012 Normal 500.00GB       0A/0A       SN_210235G6EAZ0B4000006 
           1         sdd            LUN_020        6925805100a12200000af53300000013        Normal 500.00GB       0B/0B       SN_210235G6EAZ0B4000006 
           2         sde          LUN004--test     6925805100a1220006b8b70500000064        Normal 10.00GB        0A/0A       SN_210235G6EAZ0B4000006 
           3         sdf       LUN_BRM_C02_03_002  6925805100a122000e8b90da00000075        Normal 20.00GB        0B/0B       SN_210235G6EAZ0B4000006 
           4         sdg           qr_lun004       6925805100a122000012d6a100000072        Normal 10.00GB        0A/0A       SN_210235G6EAZ0B4000006 
           5         sdh           qr_lun002       6925805100a122002ae4e1f60000006f        Normal 10.00GB        0A/0A       SN_210235G6EAZ0B4000006 
           6         sdi           qr_lun001       6925805100a122002ae31e4e0000006e        Normal 20.00GB        0A/0A       SN_210235G6EAZ0B4000006 
           7         sdj         qr_lun_r2_001     6925805100a122000171e05800000077        Normal 20.00GB        0A/0A       SN_210235G6EAZ0B4000006 
       ------------------------------------------------------------------------------------------------------------------------------------

   Check whether the disk has residual LVM information.

8. Run the following command to obtain the logical device name of the undetected storage device based on its WWN:

   #  ll /dev/disk/by-id | grep scsi-3 wwn

   In the following example, sdb is the logical device name of the undetected device whose WWN is 6925805100a12200000af4ee00000012.

   scsi-36925805100a12200000af4ee00000012 -> ../../sdb

   After this step is performed, go to 10

9. Run the following command to query storage device names, compare the storage device names in the command output with those detected by the FusionCompute CNA host, and find undetected storage devices.

   # ll /dev/disk/by-id | grep scsi-

   For example, the following storage device is displayed in the command output but not detected by the FusionCompute CNA host. The following command output shows that the undetected storage device's logical name is sdb:

   scsi-35000cca03c9e79da -> ../../sdb

   Logical device sda has 10 partitions. You only need to check whether sda10 is detected by the FusionCompute CNA host. You only need to check whether sda10 and sdb (for example, scsi-3610b5442bcc70001f3780f90650d1e0) are detected by comparing storage device names obtained using the command and those queried on the FusionCompute web client.

10. Run the following command to check whether the undetected device has PV information:

    # pvdisplay /dev/logical device name

    The following command output uses logical device name /sdb as an example to show that the device has PV information. In this case, go to 11.

      --- Physical volume --- 
      PV Name               /dev/sdb 
      VG Name               3  PV Size               931.51 GiB / not usable 1.71 MiB 
      Allocatable           yes 
      PE Size               4.00 MiB 
      Total PE              238467 
      Free PE               387 
      Allocated PE          238080 
      PV UUID               LZJQFe-lrRT-hvnc-81RN-Y2Dz-Dres-CkXVTc

11. Check whether the command output contains VG Name information, for example, VG Name 3.
    1. If the command output contains VG Name information, go to 12.
    2. If the command output does not contain VG Name information, go to 23.
12. Run the following command to obtain LV Name based on VG Name:

    # lvdisplay

    This command uses VG Name 3 as an example. When a VG name maps to multiple LV names, note down all LV names.

    Check whether the command output contains at least one LV name in format of /dev/VG/LV, for example, LV Name /dev/3/3.

    1. If the command output contains at least one LV name in the specified format, go to 13.
    2. If the command output does not contain any LV name in the specified format, go to 21.

        --- Logical volume --- 
         LV Name                /dev/3/3 VG Name                3 
         LV UUID                vizADs-wqLO-ct34-4gp5-LieF-HZ7s-Rza12a 
         LV Write Access        read/write 
         LV Status              available 
         # open                 1 
         LV Size                930.00 GiB 
         Current LE           238080 
         Segments               1 
         Allocation             inherit 
         Read ahead sectors     auto 
         - currently set to     1024 
         Block device           253:9

13. Run the following command to delete the LV based on the obtained LV name:

    # lvremove /dev/VG/LV

    For example, run the lvremove /dev/3/3 command.

    Check whether the command output contains Can't remove open logical volume.

    1. If the command output contains Can't remove open logical volume, go to 14.
    2. If the command output does not contain Can't remove open logical volume, go to 18. (Generally, the LV can be deleted.)
14. Run the following command to obtain the name of the storage device based on the logical device name:

    # ll /dev/disk/by-id/ | grep logical device name

    In the following example, scsi-36925805100a12200000af4ee00000012 is the name of the undetected device whose logical device name is sdb.

    lrwxrwxrwx 1 root root  9 Oct 10 16:10 scsi-36925805100a12200000af4ee00000012 -> ../../sdb 

15. On the FusionCompute web client, choose Computing. In the navigation pane on the left, choose Configuration > Data Storage to check whether the storage device has been added as a data store.
    1. If the storage device is not added as a data store, go to 16.
    2. If the storage device has been added as a data store, no further action is required.
16. Run the following command to change the LV status:

    # lvchange -an /dev/VG/LV

17. Run the following command to delete the LV:

    # lvremove /dev/VG/LV

18. Enter y as prompted and press Enter.
19. If the command output in 12 shows that the VG name maps to multiple LV names for the undetected device, you need to delete other LVs. Check whether all the other LVs are deleted.
    1. If all the other LVs are deleted, go to 21.
    2. If other LVs are not deleted, go to 20.
20. Repeat 13 to 19 to delete all the other LVs.
21. Run the following command to delete the VG:

    # vgremove VG

22. Enter y as prompted and press Enter.
23. Run the following command to delete the PV:

    # pvremove /dev/logical device name

24. On the FusionCompute web client, choose Computing. In the navigation pane on the left, select the target host, choose Configuration > Storage Resource, and click Scan. Check whether the device can be detected.
    1. If the device can be detected, go to 25.
25. Check whether other storage devices still cannot be detected.
    1. If other storage devices still cannot be detected, perform 1 to 25.
    2. If all storage devices are detected, no further action is required.

Question

The default memory space of VRM VMs is 5 GB. At most 4928 MB memory space can be used by the VRM service system, occupying 96.25% of the total memory space of the VRM. Therefore, alarms may be reported during service running. How do I adjust the memory of VRM VMs to ensure that sufficient memory resources are reserved and thereby reduce unnecessary alarms?

Answer

1. Adjust the memory of the active and standby VRM VMs.
   1. Log in to the FusionCompute management system, choose Resource Pools > ManagementCluster, and select the target VRM VM.
   2. Click the Configuration tab, click Hardware on the left, and adjust the VM memory.

   3. Log in to the active and standby VRM VMs and restart them.
      • Restarting VRM VMs will temporarily interrupt related services. Therefore, you are advised to restart the VMs when no services are performed.
      • The standby VM needs to be restarted before the active VM. The active VM can be restarted only after successful restart of the standby VM. To obtain information about the active and standby VRM VMs, choose System > System Configuration > Services and Management Nodes.
      • The default username and password are available in iMaster NCE-Campus Default Usernames and Passwords (Enterprise Network or Carrier). If you have not obtained the access permission of the document, see Help on the website to find out how to obtain it.

2. Update VRM VM information.
   1. Log in to the active VRM VM as the root user, and update the VM information.

      perl /opt/galax/vrm/tomcat/script/vrmWindowsInstall/bin/importVrmDb.pl -g -i ID of the active VRM VM

      perl /opt/galax/vrm/tomcat/script/vrmWindowsInstall/bin/importVrmDb.pl -g -i ID of the standby VRM VM

      The IDs of the active and standby VRM VMs can be obtained from the Summary > Details page under the corresponding VMs.

      For example, if the IDs of the active and standby VRM VMs are i-00000001 and i-00000002 respectively, you need to run the following commands to update the VM information:

      perl /opt/galax/vrm/tomcat/script/vrmWindowsInstall/bin/importVrmDb.pl -g -i i-00000001

      perl /opt/galax/vrm/tomcat/script/vrmWindowsInstall/bin/importVrmDb.pl -g -i i-00000002

   2. Copy the configuration files of the active and standby VRM VMs to the corresponding CNA nodes where the VMs are located.

      scp /home/ID of the active VRM VM.xml gandalf@IP address of the CNA node where the active VRM VM is located:/home/GalaX8800

      scp /home/ID of the standby VRM VM.xml gandalf@IP address of the CNA node where the standby VRM VM is located:/home/GalaX8800

      For example, if the IDs of the active and standby VRM VMs are i-00000001 and i-00000002 respectively, and the IP addresses of the CNA nodes where the active and standby VMs are located are 192.168.200.21 and 192.168.200.22 respectively, you need to run the following commands to copy the configuration files to the target nodes respectively:

      The IP addresses of the CNA nodes where the active and standby VRM VMs are located can be obtained on the Summary tab page under the corresponding VMs.

      scp /home/i-00000001.xml gandalf@192.168.200.21:/home/GalaX8800

      scp /home/i-00000002.xml gandalf@192.168.200.22:/home/GalaX8800

   3. Log in to the CNA node where the active VRM VM is located as the root user, and back up the VM configuration file stored on the CNA node.

      cp /etc/galax/eucalyptus/ID of the active VRM VM.xml /etc/galax/eucalyptus/ID of the active VRM VM.xml.bak

      The backup file can be used to restore the VRM VM to the state when the backup file is created if an error occurs in the VRM VM configuration.

   4. Copy the new configuration file of the VRM VM to the /etc/galax/eucalyptus/ directory.

      mv /home/GalaX8800/VM ID.xml /etc/galax/eucalyptus/

   5. Log in to the CNA node where the standby VRM VM is located as the root user, and back up the VM configuration file stored on the CNA node. Copy the new configuration file of the VRM VM to the /etc/galax/eucalyptus/ directory.

      For details, see 2.c to 2.d.

   6. Log in to the active VRM VM, and copy the configuration files of the active and standby VRM VMs to the /etc/galax/vm_xml/ directory.

      cp /home/ID of the active VRM VM.xml /etc/galax/vm_xml/

      cp /home/ID of the standby VRM VM.xml /etc/galax/vm_xml/

Scenarios

If no external clock source is deployed, configure the host accommodating the VRM VM or the physical server that has VRM installed as the NTP clock source. In this case, the system time on the target host or physical server must be accurate.

Prerequisites

You have obtained the passwords of users gandalf and root of the node to be configured as the NTP clock source.

Procedure

1. Log in to the operating system of the node.
   1. Use PuTTY to log in to the node that serves as the NTP clock source.

      Ensure that the management IP address and username gandalf are used to establish the connection.

   2. Run the following command and enter the password of the root user to switch to the root user:

      su - root

   3. Run the following command to disable user logout upon system timeout:

      TMOUT=0

2. Manually change the system time on a node.
   1. Check whether any external NTP clock source is configured for the node.
      • If yes, go to 2.b.
      • If no, go to 2.c.
   2. Run the following command to set the node as its own NTP clock source:

      perl /opt/galax/gms/common/config/configNtp.pl -ntpip 127.0.0.1 -cycle 6 -timezone Local time zone -force true

      For example, if the local time zone is Asia/Beijing and the node is a physical server that has VRM installed, run the following command:

      perl /opt/galax/gms/common/config/configNtp.pl -ntpip 127.0.0.1 -cycle 6 -timezone Asia/Beijing -force true

   3. Run the date command to check whether the current system time is accurate.
      • If yes, go to 2.h.
      • If no, go to 2.d.
   4. Run the required command to stop a corresponding process based on the node type.
      • If the node is a host, run the following command:

        perl /opt/galax/gms/common/config/restartCnaProcess.pl

      • If the node is a VRM node, run the following command:

        sh /opt/galax/gms/common/ha/stop_ha.sh

   5. Run the following command to rectify the system time of the node:

      date -s Current time

      The current time must be set in HH:MM:SS format.

      For example, if the current time is 16:20:15, run the following command:

      date -s 16:20:15

   6. Run the following command to synchronize the new time to the basic input/output system (BIOS) clock:

      /sbin/hwclock -w -u

   7. Run the required command to start a corresponding process based on the node type.
      • If the node is a host, run the following command:

        service monitord start

      • If the node is a VRM node, run the following command:

        service had start

   8. After 3 minutes, run the ntpq -p command.

      Information similar to the following is displayed:

      remote           refid      st t when poll reach   delay   offset  jitter 
      ============================================================================== 
      *LOCAL(0)        .LOCL.      5 l  58   64   377    0.000    0.000   0.001     

      If * is displayed on the left of LOCAL, the time service is running properly on the node. The node can be used as an NTP clock source.

      If * is not displayed, run the ntpq -p command five to ten minutes later again to check the time service running status.

Scenarios

On FusionCompute, configure a Domain Name Server (DNS) to resolve Network Time Protocol (NTP) server domain names.

Prerequisites

Conditions

• You have logged in to FusionCompute.
• The DNS server can communicate with the management IP address of each FusionCompute node properly.

Procedure

1. In the navigation pane, click .

   The System page is displayed.

2. Choose System > Connect To > DNS Server.

   The DNS Server page is displayed.

3. Enter the IP address of the DNS server.

   You can set two IP addresses for preferred and alternate DNS servers.

   The system uses the preferred DNS server to resolve domain names. If the preferred one is faulty, the alternate one is used.

   Ensure that the DNS server is available. Otherwise, the system may become abnormal.

4. Set DNS Test Domain Name.

   Used to test whether the DNS service is functioning properly. The test domain name must be an existing domain or sub-domain name on the DNS server in the www.your company.com format.

5. Click Test to test whether the configured DNS server IP addresses can be pinged.
6. Determine the subsequent operation based on the information displayed in the displayed dialog box.
   • If the configured DNS servers are correctly configured, go to 8.
   • If the configured DNS servers are not correctly configured, go to 7.
7. Modify the DNS parameters to ensure that the configured DNS server IP addresses are correct.
8. Click Save.

   A dialog box is displayed.

9. Click OK.

   The DNS server is configured in the system.

   You can select Clear All to delete the DNS server configuration.

If the configuration is deleted, the NTP server that uses the DNS server to resolve domain names is disconnected from the DNS server.

Question

When a user creates a VM running the EulerOS 2.5 operating system through FusionCompute 6.3.1, the GUI display is abnormal or the system displays a message indicating that the operating system of the VM is invalid.

The default username and password are available in iMaster NCE-Campus Default Usernames and Passwords (Enterprise Network or Carrier). If you have not obtained the access permission of the document, see Help on the website to find out how to obtain it.

Answer

1. Decompress the OS-CONFIG-kvm.zip file as the gandalf user and upload the decompressed file to the /home/GalaX8800/ directory on the active and standby VRM nodes.
2. Switch to the root user and modify the file permission.

   chown root:root /home/GalaX8800/OS-CONFIG-kvm.xml

3. Copy the file to the /opt/sia/GuestOSPlugIn/ directory.

   cp /home/GalaX8800/OS-CONFIG-kvm.xml /opt/sia/GuestOSPlugIn/

4. Restart the VRM service on the active VRM node.

   service vrmd restart

Question

How do I check the network adapter corresponding to a network port on the server?

Answer

1. Log in to the server as the root user.
2. Connect a network cable only to the network port to be checked.
3. Run the following command to check the mapping between the network port and network adapters:

   ethtool eth0

   If the following information is displayed, the network port corresponds to the eth0 network adapter. Otherwise, continue to test other network adapters.

   Link detected: yes