Sangfor Cloud Platform (SCP)

Enterprise Cloud Computing Platform Built on Business-Centric HCI.
{{ $t('productDocDetail.guideClickSwitch') }}
{{ $t('productDocDetail.know') }}
{{ $t('productDocDetail.dontRemind') }}
6.11.3
Sangfor Cloud Platform (SCP) {{ breadTitle }} Cluster Management Cluster Creation and Management Cluster Management HCI Cluster Management Add Physical Resources
{{sendMatomoQuery("Sangfor Cloud Platform (SCP)","Add Physical Resources")}}

Add Physical Resources

{{ $t('productDocDetail.updateTime') }}: 2025-12-18

Function Description:

Sangfor SCP supports the management of multiple HCI clusters and VMware clusters and realizes unified management of multiple resource pools through the SCP platform.

This section will Instruct the administrator to add the prepared physical resources to the SCP platform in a cluster and tag the storage resources.

Prerequisite

  1. Sangfor SCP and HCI resource pools or VMware resource pool networks are reachable.

Component

Port

Protocol

Purpose

VMware vCenter

443

TCP

Used for HCI to obtain virtual machine configuration information through the vCenter management interface, and to perform operations such as powering on/off, snapshots, etc

EXSI

902

TCP

Used for HCI to directly access the VMDK disk files on the ESXi host through the VDDK interface for data read/write and migration

Table: network requirement for SCP manages VMware

SCP manages HCI:

Port 443: Port for managing HCI cluster and deploy license

Port 4480: Port for web access to admin console of NFV

  1. According to the management and license plan, prepare sufficient license and license file.

Precautions:

  1. SCP supports managing different versions of HCI resource pools. For details of the hyper-converged versions that support management, please log in to Sangfor Community for inquiries. Refer to link.
  2. The SCP cloud computing platform supports managing different versions of VMware clusters. The supported VMware versions are as follows: VMware 5.0 、VMware 5.1、VMware 5.5、VMware 6.0、VMware 6.5. Versions after HCI 5.8.7 R1 support VMware 6.7. Refer to link.

Steps:

Step 1: Log in to SCP as an administrator and go to Resource Center > Resource Pools > New.

Step 2: In the new page fill in the following information, after that click Next.

Name: Define a name for the cluster that will be managed.

Description: The description for the cluster.

Type: there are 3 types of the cluster HCI (X86), HCI (ARM) and VMware select the type of based on your cluster. For HCI cluster you can login to HCI go to System > Upgrade to check the cluster type.

Management IP: the cluster IP of the HCI cluster.

Management IP Verification: Uncheck this option if the management IP address will be translated by a NAT rule.

Time Sync: After checking this option, the impacts are as follows.

  1. The cluster will synchronize its time with this platform, so do the VMs in the cluster that have vmTools installed and are configured to regularly synchronize guest time with node.
  2. During the time sync, if the difference between the node time and the guest time exceeds the threshold, the VM will encounter a sudden time change, affecting services. The difference threshold depends on the tinker panic parameter value in the NTP related settings. The default threshold for NTPv4 is 128 seconds.
  3. This feature applies only to HCI clusters of version 6.9.0 installed patches with time sync support and later versions.
  4. Please make sure that the SCP port for time sync is open, otherwise the time sync settings will not take effect.

Username: HCI super account admin.

Password: HCI super account admin’s password.

Port: Keep the default if you don't have any special requirements.

Licensing Mode: According to your plan select license mode.

Pool Type: Shared mode Indicates a resource pool available to multiple tenants.

Tenant Network Protection: Block some risky ports in tenant VPC.

After being enabled, a security baseline policy "Block risky ports that allow traffic from the Internet" will be automatically generated for the newly created subnets in this resource pool by tenants to reduce the tenant business exposure to the Internet and security risks.

To view the policy, please go to Router Settings > Access Control in the corresponding tenant VPC on the Topology page.

Step 3: Setting the storage tag. According to the actual situation of the cluster, different tags can be set for different storage volumes. The default includes high performance, performance, and capacity.

• High-performance storage: Strong read and write performance, used to create high-performance virtual machines, generally gives this tag to the SSD storage category.

• Performance storage: Strong read and write performance, but relatively aging, generally old storage.

• Capacity storage: Average read and write performance, but large capacity, high security, and high-cost performance.

Step 4: After confirming that the information is correct, click the OK button.