Capacity Expansion

Application Scenarios

When the cluster performance of iMaster NCE-Campus reaches the bottleneck, you can add nodes to improve the cluster performance.

Precautions and Constraints

• Only capacity expansion from a three-node cluster to a four-node cluster is supported.
• Capacity expansion cannot be performed if the cluster contains a faulty node.
• The NIC name, network segment, and network configuration of the node to be added must be the same as those of the existing nodes.
• The default route of the new node must be the same as that of the primary node, that is, the node where nv and sv are located.
• The configuration of the new node (such as the CPU, disk capacity, and memory) must be the same as or higher than that of the existing node.
• The server architecture of the new node is the same as that of the existing node.
• The operating system and encoding format of the new node must be the same as those of the existing node.
• Ensure that the PC where EasySuite is installed does not interfere with the service network.
• Before using EasySuite to install iMaster NCE-Campus, disable the hibernation function on the PC where EasySuite is installed.
• During capacity expansion, you need to log in to EasySuite and enter the IP address configured for logging in to the iMaster NCE-Campus node. Before capacity expansion, ensure that the IP address for logging in to the iMaster NCE-Campus node has been configured.
• The capacity expansion takes about 1 to 2 hours depending on the network scale and components. Ensure that the PC has sufficient electrical power and does not hibernate during the installation.
• If iMaster NCE-Campus has been interconnected with CampusInsight and capacity expansion is performed for iMaster NCE-Campus, the system administrator needs to log in to iMaster NCE-Campus and click Save on the System > System Management > SSO Configuration > CampusInsight page to enable alarm permissions. Otherwise, some alarm rules may fail to be created on CampusInsight.
• When VMs are planned on PMs, do not deploy two controller VMs or two FusionInsight VMs on the same PM.

Checking Before Capacity Expansion

• Run the uname -i command to check the server architecture. Ensure that the server architecture of the new node is the same as that of the existing node.

  uname -i 

• Run the fdisk -l command to check the disk capacity. Ensure that the disk capacity of the new node is not less than that of the existing node.

  fdisk -l

• Run the ifconfig command to check network configuration. Ensure that the NIC name, network segment, and network configuration of the new node are the same as those of the existing node.

  ifconfig

• Run the cat /etc/os-release command to check the operating system version. Ensure that the operating system of the new node is the same as that of the existing node.

  cat /etc/os-release

• Run the locale command to check the encoding format of the operating system. Ensure that the encoding format of the new node is the same as that of the existing node.

  locale

Preparations Before Capacity Expansion

1. Download EasySuite.
   • If you are a carrier user, log in to https://support.huawei.com/carrier, and search for iMaster NCE-Campus on the Software tab page. On the iMaster NCE-Campus page, select the desired version.
   • If you are an enterprise user, log in to https://support.huawei.com/enterprise, and search for iMaster NCE-Campus. On the iMaster NCE-Campus page, select the desired version.

2. Download packages for third-party tools.
   Table 3-107 Third-party applications

   No.	Name	Function	How to Obtain
   1	PuTTY	Used to log in to the server in SSH mode.	Log in to the PuTTY official website at https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html and download the latest version.
   2	FileZilla	Used to transfer files using SFTP.	Log in to the FileZilla official website at https://filezilla-project.org and download the latest version.

3. Obtain the iMaster NCE-Campus installation package, and decompress the packages to the var/software folder in the EasySuite directory.

   For details about how to obtain the software package, see Downloading Packages for Installation and Third-Party Tools in the Installation Guide.

4. Create a new node and install the OS.
   1. Configure RAID for the new server. For details, see section Configuring RAID Groups in the Installation Guide.
   2. Install the CNA software. For details, see section Installing the FusionCompute CNA in the Installation Guide.
   3. Add the CNA host to FusionCompute and configure related configurations. For details, see Configuring the FusionCompute in the Installation Guide.
   4. Create a VM and install an OS. For details, see Installing the OS in the Installation Guide.
   5. Configure the operating system. For details, see Configuring the OS in the Installation Guide.

Procedure

1. Create a node for capacity expansion and install an operating system on the node. For details, see Software Installation.
2. Log in to EasySuite.
   1. Go to the EasySuite decompression directory and double-click start.bat.

      In the browser that is automatically started within 1 minute, enter the IP address of the server where EasySuite resides (https://localhost:19090) and press Enter.

      • The priority from high to low of the browser that is automatically started by the system is as follows: Chrome > FireFox.
      • If "Access Denied" is displayed in the command prompt window, right-click start.bat and choose Run as administrator from the shortcut menu. If the browser fails to be started with other problems, rectify the fault based on the information displayed in the command prompt window, and then double-click start.bat again.
      • To stop EasySuite, double-click stop.bat in the EasySuite decompression directory.
   2. Enter the username and password, and click Log In.
      • Username: The default username is admin.
      • Password: Change the password upon your first login.

3. Perform capacity expansion operations.
   1. Click New Project on the Expansion tab page.

   2. Enter the project information, select One-Premise (Product Only) Expansion Solution from Configuration plan, and click OK.

   3. Confirm the project information, click Save, and click Next. The page for selecting a solution is displayed.

   4. Choose Product Configuration > Parameter Configuration from the navigation pane. Set Node Configuration and Login user Configuration, and decide whether to perform security hardening for the operating system. Click Save and Next.

      If security hardening has been performed on cluster nodes, select Yes for operating system security hardening. Otherwise, select No.

   5. Click Save. Choose Software packages from the navigation pane, and click Verification to verify the integrity of the capacity expansion package. After all checks are passed, click OK and Next.

      If is displayed in the verification result, the verification fails. Obtain a new installation package and verify it again.

   6. On the environment check page, click Start Check next to Offline check and Online check. After the checks are passed, click Next.

      If is displayed in the Check Result area, an error occurs during feature expansion. In this case, view the expansion details to locate the fault. After the fault is rectified, continue to expand features.

4. Click Start Expand.

   The capacity expansion takes about 1 to 2 hours depending on the network scale and components.

5. If the progress is 100% and no error message is displayed, the capacity expansion is successful.

Verifying Capacity Expansion

1. Log in to the management plane at https://IP address of the management plane:18102.
2. Choose Product > System Monitor from the main menu of the management plane.
3. On the System Monitoring page, ensure that all services are running properly, which indicates that iMaster NCE-Campus is successfully installed and commissioned.

Follow-up Procedure

• To ensure system information security, you are advised to delete the installation project in EasySuite after the capacity expansion is complete and the system is running properly.

Before deleting the project, click Export at the upper right corner on the HLD and LLD pages in EasySuite to download the HLD and LLD contents, and send them to the customer so that the customer can view the product specifications and installation and deployment information. Then, delete the local files in a timely manner.

1. Log in to EasySuite.
2. Choose Project Management from the main menu.
3. On the Project Management page, click in the Operation column of the desired project to delete the installation project.

   To save the disk space of the server, it is recommended that the software package uploaded to the OMP node during the installation be deleted.

4. Use PuTTY to log in to the OMP node as the sopuser user in SSH mode. Switch to ossadm user.
5. (Optional) Run the following command to delete the /opt/expansion folder:

   su - root
   Password: password of the root user
   # rm -r /opt/expansion

6. Run the following commands as the root user to hide the virtual memory information:

   swapoff -a
   sed -i 's,^[^#].*swap,#&,g' /etc/fstab

After capacity expansion, do not modify the installation directory. Otherwise, iMaster NCE-Campus cannot run properly or be uninstalled.

Application Scenarios

If new or value-added features are required for service expansion, you can use EasySuite to deploy value-added features, without reinstalling iMaster NCE-Campus.

Precautions and Constraints

• During feature expansion, you need to log in to EasySuite and enter the IP address configured for logging in to the iMaster NCE-Campus node. Before feature expansion, ensure that the IP address for logging in to the iMaster NCE-Campus node has been configured.
• The feature expansion takes about 1 to 2 hours depending on the network scale and components. Ensure that the PC has sufficient electrical power and does not hibernate during the installation.
• If the SD-WAN feature is deployed, tenants need to log in to iMaster NCE-Campus and switch the tunnel mode to EVPN so that the WAN-related menus are available on the web UI.

Preparations Before Feature Expansion

1. Download EasySuite.
   • If you are a carrier user, log in to https://support.huawei.com/carrier, and search for iMaster NCE-Campus on the Software tab page. On the iMaster NCE-Campus page, select the desired version.
   • If you are an enterprise user, log in to https://support.huawei.com/enterprise, and search for iMaster NCE-Campus. On the iMaster NCE-Campus page, select the desired version.

2. Download packages for third-party tools.
   Table 3-109 Third-party applications

   No.	Name	Function	How to Obtain
   1	PuTTY	Used to log in to the server in SSH mode.	Log in to the PuTTY official website at https://www.chiark.greenend.org.uk/~sgtatham/putty/download.html and download the latest version.
   2	FileZilla	Used to transfer files using SFTP.	Log in to the FileZilla official website at https://filezilla-project.org and download the latest version.

3. Obtain the iMaster NCE-Campus installation package, and save the packages to the var/software folder in the EasySuite directory.

   To deploy SecoManager, the NCE-SecoManager_xxx_for_Campus_x64.7z file and signature file NCE-SecoManager_xxx_for_Campus_x64.7z.cms and NCE-SecoManager_xxx_for_Campus_x64.7z.crl must be saved in the var/software directory.

4. (Optional) Create a node for capacity expansion and install an operating system on the node. For details, see Software Installation.

   If the existing cluster has only three nodes and requires the NCE-WAN feature, you need to add one cluster node.

Procedure

1. Log in to EasySuite.
   1. Go to the EasySuite decompression directory and double-click start.bat.

      In the browser that is automatically started within 1 minute, enter the IP address of the server where EasySuite resides (https://localhost:19090) and press Enter.

      • The priority from high to low of the browser that is automatically started by the system is as follows: Chrome > FireFox.
      • If "Access Denied" is displayed in the command prompt window, right-click start.bat and choose Run as administrator from the shortcut menu. If the browser fails to be started with other problems, rectify the fault based on the information displayed in the command prompt window, and then double-click start.bat again.
      • To stop EasySuite, double-click stop.bat in the EasySuite decompression directory.
   2. Enter the username and password, and click Log In.
      • Username: The default username is admin.
      • Password: Change the password upon your first login.

2. Deploy a new feature.
   1. Click New Project on the Expansion tab page.

   2. Enter the project information, select One-Premise Value-added Feature Expansion Solution or Public Cloud Value-added Feature Expansion Solution from Configuration plan, and click OK.

   3. Confirm the project information, click Save, and click Next. The page for selecting a solution is displayed.

   4. Choose Product Configuration > Parameter Configuration from the navigation pane. The feature expansion page is displayed. Set parameters, select the feature to be installed, and set parameters of the management plane.
      • If the SD-WAN feature does not need to be deployed or there are four or more nodes in the original cluster, select No expansion node.

      • If there are three nodes in the original cluster and the SD-WAN feature needs to be deployed, select Expand one node and set parameters of the new node.

        Enter the actual IP address of the active node for the Management plane master node. Do not enter the floating IP address of the management plane.

   5. Perform security hardening for the operating system.

      If a new node is added and security hardening has been performed on the existing cluster nodes, set Whether to perform security hardening to Yes. Otherwise, select No.

   6. Click Save. Choose Software packages from the navigation pane, and click Verification to verify the integrity of the capacity expansion package. After all checks are passed, click OK and Next.

      If is displayed in the verification result, the verification fails. Obtain a new installation package and verify it again.

   7. On the environment check page, click Start Check next to Offline check and Online check. After the checks are passed, click Next.

      If is displayed in the Check Result area, an error occurs during feature expansion. In this case, view the expansion details to locate the fault. After the fault is rectified, continue to expand features.

3. Click Start Expand.

   The capacity expansion takes about 1 to 2 hours depending on the network scale and components.

4. If the progress bar shows 100% and no error message is displayed, the selected features are deployed successfully.

Checking After Feature Expansion

1. Log in to the management plane at https://IP address of the management plane:18102.
2. Choose Application > Service Management > System Monitor from main menu of the management plane.
3. On the System Monitoring page, ensure that all services are running properly, which indicates that iMaster NCE-Campus is successfully installed and commissioned.

Follow-up Procedure

• To ensure system information security, you are advised to delete the installation project in EasySuite after the feature expansion is complete and the system is running properly.

Before deleting the project, click Export at the upper right corner on the HLD and LLD pages in EasySuite to download the HLD and LLD contents, and send them to the customer so that the customer can view the product specifications and installation and deployment information. Then, delete the local files in a timely manner.

1. Log in to EasySuite.
2. Choose Project Management from the main menu.
3. On the Project Management page, click in the Operation column of the desired project to delete the installation project.
   • To save the disk space of the server, it is recommended that the software package uploaded to the NMS node during the installation be deleted.
4. Use PuTTY to log in to the NMS node as the sopuser user in SSH mode. Switch to ossadm user.
5. (Optional) Run the following command to delete the /opt/expansion folder:

   su - root
   Password:              //password of the root user rm -r /opt/expansion

After feature expansion, do not modify the installation directory. Otherwise, iMaster NCE-Campus cannot run properly or be uninstalled.

Precautions and Constraints

• When FusionInsight and iMaster NCE-Campus are jointly deployed, capacity expansion of FusionInsight nodes is not supported.
• A maximum of two nodes are supported after capacity expansion.
• The operating system and its encoding format of the nodes to be added must be the same as those of the existing nodes.
• The disk name of the nodes to be added must be the same as that of the existing cluster nodes.
• The NIC names and number of NICs on the nodes to be added must be the same as those on the existing cluster nodes. The NICs of the same name must be in the same network segment and have reachable routes to each other. For example, eth0 on a node to be added must be in the same network segment as eth0 on an existing cluster node, and they have reachable routes to each other.
• The time zone and time of the nodes to be added must be the same as those of the existing cluster nodes. During capacity expansion, Network Time Protocol (NTP) is automatically set so that the nodes to be added synchronize the time settings from the primary management node.
• The host names of all nodes (including the nodes to be added and the existing cluster nodes) must be unique.
• During capacity expansion, ensure that the power supply and network are stable.

Checking Before Capacity Expansion

• Check the existing cluster.

  Log in to FusionInsight, check whether hosts and services are running properly, and locate the primary and secondary management nodes (the node marked with a solid star icon is the primary management node, and the node with a hollow star icon is the secondary management node).

• Check the host names and configure the mappings between the host names and IP addresses.

  The host names of all nodes (including the existing cluster nodes) must be unique.

  Log in to the operating system of a node to be added as the root user and add the mappings between the IP addresses and host names of other nodes (including the existing cluster nodes and other nodes to be added) in the /etc/hosts file.

  You do not need to add the mappings on the existing cluster nodes, as the mappings will be automatically added during capacity expansion.

• Run the uname -i command to check the server architecture. Ensure that the server architecture of the new node is the same as that of the existing node.

  uname -i 

• Run the fdisk -l command to check the disk capacity. Ensure that the disk capacity of the new node is not less than that of the existing node.

  fdisk -l

• Run the ifconfig command to check network configuration. Ensure that the NIC name, network segment, and network configuration of the new node are the same as those of the existing node.

  ifconfig

• Run the cat /etc/os-release command to check the operating system version. Ensure that the operating system of the new node is the same as that of the existing node.

  cat /etc/os-release

• Run the locale command to check the encoding format of the operating system. Ensure that the encoding format of the new node is the same as that of the existing node.

  locale

Preparations Before Capacity Expansion

1. Log in to new node as the root user.
2. Partition disks on each node.

   Ensure that the disk names of each node to be added is the same as those of an existing node.

   Before partitioning disks, ensure that a hard disk with a size greater than 1.8 TB is available on each node to be added. Run the lsblk command to check disk information. A disk with TYPE of disk and MOUNTPOINT left empty is an available disk on the node, for example, vdb in the following figure.

   1. Run the following command on each node to be added to create the /opt/tools directory.

      mkdir -p /opt/fi_tools

   2. Log in to a node in the original FusionInsight cluster.

      Log in to FusionInsight, click Host, view the node marked with a solid star icon (that is, the primary management node), and log in to the node using the CLI.

   3. Run the following commands to copy all files in /opt/fi_tools on the FusionInsight primary management node to each node to be added.

      cd /opt/fi_tools
      scp ./* root@10.247.65.116:/opt/fi_tools

      The IP address specified in the preceding commands is the IP address of a node to be added.

      Then log in to each node to be added and check whether the files are successfully copied.

      cd /opt/fi_tools && ll

   4. Partition disks on each node to be added.

      Log in to each node to be added as the root user and run the disk partition script.

      cd /opt/fi_tools/ && sh create_vol.sh "/dev/xxx"

      In the command output, xxx indicates the data disk with a size greater than 1.8 TB, for example, vdb.

      Run the df -h command to check whether the disk partitions are created successfully. If the command output contains five partitions marked in the red box as shown in the following figure, the disk partitions are created successfully.

      Perform the preceding steps on all nodes to be added.

3. Execute the preset script on each node to be added.
   1. Log in to each node to be added and execute the preset script.

      cd /opt/fi_tools/
      tar -zxvf FusionInsight_SetupTool_6.5.1.tar.gz
      cd /opt/fi_tools/FusionInsight_SetupTool/preset/
      sh preset.sh

      The following information indicates that the script is executed successfully.

Procedure

1. Log in to FusionInsight Manager.
2. Manually add hosts.
   1. Choose Cluster > Host from the main menu. Click Add, set Cluster to ControllerCluster, and click Next.

   2. Enter the IP address of the nodes to be added in IP Address/IP Address Segment. Separate multiple IP addresses with commas (,). Enter the password of the root user and click Find Host. After the host is found, you can view the host in the Start Discovery result. Ensure that the host name, IP address, and operating system are correct.

      After the host check is complete, click Next.

   3. (Optional) Set the rack name, which is /default/rack0, by default. To modify the rack name, select the host to be modified. If the rack name does not need to be set, click Next.

   4. On the Define Topology page, select HDFS(DN), Hbase(RS), Yarn(NM), and Kafka(Broker), and click Next.

   5. The Service Configuration page is displayed. In the capacity expansion scenario, do not modify any parameter. Ensure that the parameter values are the same as those in the original cluster. Click Next.

   6. On the Confirm page, verify that the node and service information is correct and click Submit.
   7. Wait for the tasks to complete.

Checking After Capacity Expansion

1. Log in to FusionInsight, click Cluster > Service, and click Table View to view the service status. After a new node is added, some services may transit to the Expired state.

2. Log in to FusionInsight Manager, choose Cluster > Dashboard, and click More > Restart Configuration-Expired Instances.

Context

You need to increase the disk capacity of the FusionInsight data partition in the following scenarios:

• The FusionInsight disk capacity may be insufficient with the increasing number of devices.
• An alarm indicating that the disk capacity is insufficient is displayed on FusionInsight Manager.

FusionInsight data partition. In the FusionCompute + EulerOS scenario, services are not affected during disk capacity expansion. In other scenarios, FusionInsight nodes need to be restarted during disk capacity expansion. During the restart, southbound and northbound services will be stopped for about 60 minutes.

Procedure

• To expand the disk capacity of a physical machine, perform the following steps:
  1. Add disks to a physical machine if there is no free disk available.
  2. Log in to the management plane and stop the services and databases of the iMaster NCE-Campus service plane. For details, see Stopping the Service Plane Databases and Stopping the Management Plane.
  3. Log in to FusionInsight Manager, click Cluster, and click Stop. In the displayed dialog box, enter the administrator password and click OK. In the displayed dialog box, click OK. After Operation Success is displayed, click OK to stop the FusionInsight cluster.
  4. Configure RAID. The RAID configuration performed in this step must be the same as that performed during FusionInsight installation. For details, see Configuring RAID Groups for the 2288H V5 Server.
  5. Log in to the FusionInsight node where disk capacity needs to be expanded as the omm user, switch to the root user, access the /opt/ fi_tools directory, and run the diskExpand.sh script file.

     If you cannot log in to the desired FusionInsight node as the omm user, try again as the sopuser user.

     The following parameters need to be specified in the diskExpand.sh script file:

     Drive letter of the disk to be added. You can run the fdisk -l command on the node to view the drive letter.

     Size of the disk to be added, in GB.

     su - root
     sh /opt/fi_tools/diskExpand.sh /dev/sdc 2000

  6. Log in to FusionInsight Manager as the admin user and start the FusionInsight cluster.
  7. Log in to the management plane and start the iMaster NCE-Campus service plane. For details, see Starting the Management Plane Service and Logging In to the Management Plane.
• To expand the disk capacity of a VM, perform the following steps:
  1. (Optional) Expand the disk capacity on the virtualization platform. For details, see Adding Storage Resources.
  2. Attach a disk to a VM on a virtualization platform. For details, see Attach the data disk to the FusionInsigh in Installing the OS.
  3. Log in to the FusionInsight node where disk capacity needs to be expanded as the omm user, switch to the root user, and run the fdisk -l command to check whether the new disk is successfully added. If the disk is added successfully according to the command output, go to 7. If not, go to 3.

     If you cannot log in to the desired FusionInsight node as the omm user, try again as the sopuser user.

  4. Log in to the management plane and stop the iMaster NCE-Campus service plane. For details, see Stopping the Service Plane Services.
  5. Log in to FusionInsight Manager, click Cluster, and click Stop. In the displayed dialog box, enter the administrator password and click OK. In the displayed dialog box, click OK. After Operation Success is displayed, click OK to stop the FusionInsight cluster.
  6. Restart the VM.
  7. Log in to the FusionInsight node as the omm user, switch to the root user, access the /opt/ fi_tools directory, and run the diskExpand.sh script file.

     The following parameters need to be specified in the diskExpand.sh script file:

     Drive letter of the disk to be added. You can run the fdisk -l command on the node to view the drive letter.

     Size of the disk to be added, in GB.

     su - root
     sh /opt/fi_tools/diskExpand.sh /dev/sdc 2000

  8. Log in to FusionInsight Manager as the admin user and start the FusionInsight cluster.
  9. Log in to the management plane and start the iMaster NCE-Campus service plane. For details, see Starting the Service Plane Databases.

Applicable Scenarios

In VM-based deployment scenarios, as the number of devices on a network increases, the number of devices managed by iMaster NCE-Campus may reach the upper limit. As such, insufficient VM performance may become the bottleneck for device management. In this case, you can expand CPU, memory, and disk capacities of VMs to improve the VM performance and ensure normal service running.

Precautions

• To expand CPU, memory, and disk capacities of a VM, you need to stop all iMaster NCE-Campus services and restart the VM. As a result, services will be interrupted for a short period of time. Therefore, ensure that services are not affected before performing capacity expansion.
• The number of CPU cores, number of cores per socket, memory size, and disk size can only be increased.
• It is recommended that the expanded CPU, memory, and disk capacities be the same on different nodes in a cluster.

• During capacity expansion, ensure that the power supply and network are stable.

Pre-configuration Tasks

If the storage space is about to be used up and you want to expand the disk capacity, install extra hard disks on the desired server and configure RAID.

• For details about how to configure RAID on a 2288H server, see Configuring RAID Groups.
• For details about how to configure RAID on a TaiShan server, see Configuring RAID.

After RAID is configured, perform the following operations to add storage resources for CNA nodes:

1. In the navigation tree on the left of FusionCompute, click . The Resource Pools page is displayed.
2. Choose ManagementCluster > CNA03 on the left. The host management page is displayed.
3. Choose Configuration > Storage > Storage Adapter, click Scan.

4. Click Storage Device and then Scan. When the scan is complete, the storage device will be displayed in the list.

   If the storage device is not found, see What Do I Do If Storage Device Detection Fails When Data Stores Are Added on FusionCompute?.

5. Click the Data Store tab. The Data Store page is displayed.

6. Click Add Data Store. Select the desired storage device, set Name, and select Virtualization from the Storage Mode drop-down list box.
7. Click OK. Wait until the task is complete.
8. Add the data disk storage of CNA01 and CNA02 by referring to 2 - 7.

Procedure

• The methods for expanding the CPU, memory, and disk capacities of FusionInsight VMs are the same as those for iMaster NCE-Campus VMs. Stop FusionInsight before performing capacity expansion for FusionInsight VMs. For details, see Stopping the FusionInsight. Start FusionInsight after the capacity expansion is complete. For details, see Starting the FusionInsight.
• If you want to expand the CPU, memory, and disk capacities of FusionInsight and iMaster NCE-Campus VMs at the same time, stop iMaster NCE-Campus and then FusionInsight before performing capacity expansion. After the capacity expansion is complete, start FusionInsight and then iMaster NCE-Campus.

1. Log in to the management plane, choose Product > System from the main menu, and choose Stop > Stop Service to stop all services.
2. Log in to FusionCompute web client.
3. Click on the left of the page to view resource pools. In the navigation pane, find the target VM and click the Configuration tab. The VM configuration page is displayed.

4. Choose CPU from the navigation pane, and increase the numbers of cores and cores per socket.

5. Choose Memory from the navigation pane and increase the memory size.

6. Choose Disk from the navigation pane, and click Adjust Capacity in the Operation column. In the Adjust Capacity window that is displayed, increase the disk capacity and click Save.

7. Choose More > Power > Restart to restart the VM.

8. After the VM is restarted, choose Product > System Monitoring from the main menu and choose Start > Start Service to start all services.
9. After all services are started, log in to iMaster NCE-Campus and check whether services are running properly.