No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionAccess V100R006C20 Cloud Classroom Solution Product Documentation 10 (Single-Classroom Scenarios)

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Rectifying Faults

Rectifying Faults

Rectifying FusionCompute Faults

Restoring the VRM VM OS
Scenario

This section describes how to rapidly restore services using the backup data when the VRM VM cannot be accessed.

Prerequisites
  • You have obtained the account and password for logging in to FusionCompute.
  • You have obtained the account and password for logging in to the VRM VM based on Table 3-10.
Software

You have obtained VRM VM template file FusionCompute V100R006C10_VRM.iso.

Procedure

Modifying the host configuration

  1. Use PuTTY to log in to the host where the faulty VRM VM resides.

    Ensure that the username gandalf and the management IP address are used for the login.

  2. Run the following command to switch to user root:

    su - root

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

    TMOUT=0

  1. Run the following command to modify the VRM monitoring configuration:

    cd /opt/galax/eucalyptus/usr/share/eucalyptus

    sh vrm_monitor.sh set

    The VRM monitoring configuration is successfully modified if the following information is displayed:

    set VM_RECOVER_TIME succeed.

Reinstalling the faulty VRM VM

  1. Log in to FusionCompute.
  2. Click VM and Template.
  3. In the navigation tree on the left, locate the VRM VM and click its name.
  4. Click Log In Using VNC to log in to the faulty VRM VM.
  5. Choose Hardware > CD/DVD-ROM drive > Mount Local CD/DVD-ROM Drive, and click OK.
  6. Mount the FusionCompute V100R006C10_VRM.iso file to the VM and deselect Restart the VM now to install the OS.
  7. Click OK.
  8. Use PuTTY to log in to the host housing the faulty VRM VM. Ensure that username gandalf and the management IP address are used for the login.
  1. Run the following command to switch to user root:

    su - root

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

    TMOUT=0

  1. Run the following command to set the faulty VRM VM to be booted from the CD/DVD ROM drive.

    /opt/galax/NCclient ncModifyBoot VRM VM ID cdrom

  2. Run the following command to forcibly restart the VRM VM:

    /opt/galax/NCclient ncRebootVM VRM VM ID 1

    For example, run the /opt/galax/NCclient ncRebootVM i-00000001 1 command.

  1. Reinstall the VRM VM. For details, see Fault Management > Troubleshooting > Appendix > Installing a VRM VM Using an ISO File in the FusionSphere V100R00xCxx Product Documentation (Server Virtualization,FusionCompute V100R00xCxx).

    NOTE:

    The version of the new VRM VM must be the same as that before the fault. Otherwise, reinstall the VRM VM or upgrade the VRM VM to the required version.

  1. After the installation is complete, click Unmount CD/DVD-ROM Drive.
  2. Click OK.

    The CD/DVD-ROM drive is unmounted from the VM.

Restoring the VRM VM specifications

  1. Use PuTTY to log in to the newly installed VRM node.

    Ensure that the username gandalf and the management IP address are used for the login.

  1. Run the following command and switch to user root by entering its password:

    su - root

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

    TMOUT=0

  3. Run the following command to switch to the /opt/galax/vrm/tomcat/script directory:

    cd /opt/galax/vrm/tomcat/script/

  4. Run the following command and select command parameter L to run the configuration script:

    sh modifyVrmNodeMemory.sh Command parameter

    Example: sh modifyVrmNodeMemory.sh L

    The command is successfully executed if the following information is displayed:

    modify vrm java heap success
    modify OM java heap success
    modify Portal java heap success
    modify gaussdb spec succes

  5. Run the following command to restart the node:

    reboot

Restoring the host configuration

  1. Use PuTTY to log in to the host where the VRM VM is located.

    Ensure that the username gandalf and the management IP address are used for the login.

  1. Run the following command and switch to user root by entering its password:

    su - root

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

    TMOUT=0

  3. Run the following command to restore the VRM monitoring configuration:

    cd /opt/galax/eucalyptus/usr/share/eucalyptus

    sh vrm_monitor.sh reset

    The VRM monitoring configuration is restored if the following information is displayed:

    reset VM_RECOVER_TIME succeed

Restoring VRM Data
Scenario

This section describes how to restore VRM node data of FusionCompute.

After an important operation, such as system upgrade or critical data modification, is performed for FusionCompute, you can roll back the system. The rollback requires data restoration.

Before you restore data, back up the data on the VRM node where an exception occurred or the operation did not achieve the expected result to ensure that lost data can be retrieved after the data restoration.

Prerequisites
  • You have obtained the account and password for logging in to FusionCompute.
  • You have obtained the account and password for logging in to the VRM VM based on Table 3-10.
Procedure
  1. Use WinSCP to copy backup file vrm.tar.gz from the local PC in 3.3.6.1-9 to the /home/GalaX8800 directory on the VRM node.
  2. Log in to the VRM VM using PuTTY and run the following command to switch to user root:

    su -root

  3. Run the following command to decompress the backup file:

    tar -xvzf vrm.tar.gz

  1. Log in to FusionCompute.
  2. View alarms in the Alarms area on the right:

    • If the alarm indicates that the VRM configuration file is damaged, go to Step 6.
    • If the alarm indicates that the VRM database file is damaged, go to Step 7.

  3. Run the following command to restore the configuration of the VRM node:

    restoreGeData -t DATA -f /home/GalaX8800/YYYY-MM-DD_sn/DATA/Backup file name

  1. Run the following command to restore the database data of the VRM node:

    restoreGeData -t DB -f /home/GalaX8800/YYYY-MM-DD_sn/DB/Backup file name

    If the following information is displayed, data is successfully restored:

    Congratulations! Your restore task ran successfully.

(Optional) Restoring the NIC Sequence of a Linux VM
Scenario

This section describes how to log in a VM, check the NIC configuration, and restore the NIC sequence if the NIC information displayed on FusionCompute is inconsistent.

Prerequisites
  • You have obtained the account and password for logging in to FusionCompute.
  • You have obtained the password for logging in to the Linux infrastructure VM.
Procedure
NOTE:

In this example, assume that two NICs eth0 and eth1 NICs are configured on the VM.

  1. Log in to FusionCompute.
  2. Click VM and Template.
  3. In the navigation tree on the left, locate the VRM VM and click its name.
  4. Click Log In Using VNC.
  5. Enter the VM account and password, and run the following command to delete a rule file whose name contains persistent and net from the network rule directory:

    rm /etc/udev/rules.d/XX-persistent-net.rules

  6. Run the following command to restart the VM:

    reboot

  7. Log in to the VM again using VNC, and run the following command to view the network configuration on the VM:

    ifconfig -a

  8. Check which pair of parameters are included in the configuration.

    • If eth0 and eth1 are included, no further action is required.
    • If eth0_rena and eth1_rena are included, go to 9.

  9. Run the following command to open the rule file whose name contains persistent and net in the network rule directory:

    vi /etc/udev/rules.d/XX-persistent-net.rules

  10. Press i to enter the editing mode.
  1. Replace eth0_rena and eth1_rena in the XX-persistent-net.rules file with eth0 and eth1, respectively.
  2. Press Esc and enter the following command to save the configuration and exit the vi editor:

    wq

  3. Run the following command to restart the VM:

    reboot

Rectifying FusionAccess Faults

Scenario

This section describes how to restore FusionAccess rapidly using backup data when a FusionAccess management VM is faulty or other exceptions occur.

Prerequisites
Procedure

Shutting down the faulty VM

  1. Log in to FusionCompute.
  2. Click VM and Template.
  3. In the navigation tree on the left, locate the faulty VM and click its name.
  4. Click Stop in the Operation column to stop the VM.

Configuring the backup VM

  1. In the navigation tree on the left, locate the backup VM in 3.3.6.2-13 and click its name.
  2. Click Start in the Operation column.
  3. Verify that the VM is in the Running state. Click Log In Using VNC and enter the account and password to log in to the backup VM.
  4. Run the following command to delete the NIC naming rule file:

    rm -f /etc/udev/rules.d/70-persistent-net.rules

  1. Run the following command to restart the VM:

    reboot

  2. Log in to the VM again using VNC, and run the following command to view the network configuration on the VM:

    ifconfig -a

  1. Run the following command. After the VM is started up, check whether the service status is normal, as shown in Figure 3-101.

    startTools

    Figure 3-101 Service status

  2. Use the original IP address to log in to FusionAccess. If the services are normal, the restoration is complete.

    If you cannot log in to FusionAccess using the original IP address, repeat Step 8 to Step 12 to configure the backup VM again.

(Optional) Configuring the backup of the teacher's VM

NOTE:

Perform the following operations if the teacher's VM is faulty.

  1. Repeat Step 1 to Step 4 to shut down the faulty teacher's VM.
  2. In the navigation tree on the left, locate the backup VM in 3.3.6.2-22 and click its name.
  3. Choose Hardware > Disk.
  4. In the row where the NIC resides, choose More > Modify Disk.
  5. In the window that is displayed, enter the MAC address of the old teacher's VM.
  6. Click OK.
  7. Click Start in the Operation column.
  8. Click Log In Using VNC and enter the account and password to log in to the backup VM.
  9. On the VM, click , enter the compmgmt.msc command, and press Enter.

    The Computer Management window is displayed.

  10. In the navigation pane on the left, choose Computer Management (Local) > System Tools > Local Users and Groups, and select Groups.
  11. In the right pane, right-click Administrator and choose Properties from the shortcut menu.

    The Administrator Properties window is displayed.

  12. Check whether the username is correctly displayed.

    • If yes, no further action is required.
    • If garbled characters like S-1-5-XXX are displayed, repeat Step 25 to Step 33.

  13. On the VM, click . Choose Control panel > System and Security > System.
  14. Click Change Settings.
  15. On the page that is displayed, click Change.
  16. On the page that is displayed, modify the belonging information.

    Set Workgroup to WORKGROUP.

  17. Click OK twice and enter the account and password of the domain administrator.
  18. Click OK to restart the VM.
  19. Log in to the VM again using the Administrator account.
  20. Repeat Step 25 to Step 27 to modify the belonging information on the Computer Name page.

    Select the domain and enter vdesktop.huawei.com.

  21. Click OK.

    The configuration is complete.

Translation
Download
Updated: 2019-04-25

Document ID: EDOC1100010651

Views: 26310

Downloads: 162

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next