1 Introduction
The POC tests are to verify whether Sangfor Subscription Cloud Platform can meet the relevant construction requirements of customers.
1.1 Objectives
To verify the following:
1. Sangfor Cloud Platform (SCP) login security and isolation for tenants and administrators.
2. SCP operations capabilities, including management of multi-level accounts, account authentication, and images.
3. SCP advanced features, including aSecurity, Application Center, disaster recovery, etc.
1.2 Key Information
|
Date and Time |
|
|
Location |
|
|
Personnel |
|
|
Phone Number |
|
1.3 Requirements
1. Before testing, carefully check the feature items to be tested and correspondingly delete the contents that do not need to be tested, and ensure that the testing environments have been prepared.
2. During testing, confirm the testing process and results with the customer one by one, and save the corresponding screenshots.
3. After testing, deliver the overall test report to the relevant personnel.
2 Preparations
2.1 Customer
|
Item |
Description |
|
Server Room |
Racks, trays, PDU power supplies, and appropriate network environments to ensure that tests can be performed properly. |
|
Servers |
Compliant servers if needed. |
2.2 Sangfor
|
Item |
Description |
|
Hardware and Software |
Servers, HCI and SCP software, needed templates, and so on. For details, refer to Section 2.3 Hardware and Software List. |
|
Confirmation of Customer’s Environments |
Ensure that the customer has prepared the appropriate testing environments and requirements according to the Environment Checklist. |
2.3 Hardware and Software List (Supplemental Devices)
|
No. |
Type |
Model |
Use |
Number |
Remarks |
|
1 |
Server |
W-2205 |
Hyper-Converged Infrastructure (HCI) Cluster Creation |
2 |
A supplemental device in a storage-computing splitting architecture. |
|
2 |
USB Flash Drive |
8 GB |
Disk Installation and Burning |
1 |
|
3 Environments
3.1 Topology
Four Gigabit Ethernet Layer 2 switches are required to connect six hosts in the following topology. Please connect the management switch to the switch connected to the edge-connected interface so that the management and business network segments can communicate with each other (or multiplex a Gigabit Ethernet switch that supports VLAN segregation and allows access to the management VLAN in the business VLAN).

3.2 IP Address Planning (Modified as Needed)
Please configure the host IP addresses and networks for the tests as follows:
|
Resource |
IP Type |
IPs/IP Range |
Netmask |
Remarks |
|
HCI Cluster 1 (Existing) |
Management Interface IP |
172.16.200.101-103 255.255.255.0 |
255.255.255.0 |
eth0. |
|
VXLAN IP |
10.10.10.1-g10 255.255.255.0 |
255.255.255.0 |
eth1-eth2. |
|
|
Storage Area Network IP |
100.100.100.1-10 255.255.255.0 |
255.255.255.0 |
eth3-eth4. |
|
|
Elastic IP Pool |
172.16.200.201-220 255.255.255.0 |
255.255.255.0 |
eth5. |
|
|
HCI Cluster 2 (Added) |
Management Interface IP |
172.16.200.111-113 255.255.255.0 |
255.255.255.0 |
eth0. |
|
VXLAN IP |
20.20.20.1-10 255.255.255.0 |
255.255.255.0 |
eth1-eth2. |
|
|
Storage Area Network IP |
200.200.200.1-10 255.255.255.0 |
255.255.255.0 |
eth3-eth4. |
|
|
Elastic IP Pool |
172.16.200.221-240 255.255.255.0 |
255.255.255.0 |
eth5. |
|
|
SCC (Deployed on HCI Cluster 2) |
Management interface IP |
172.16.200.200 255.255.255.0 |
255.255.255.0 |
|
|
Shared Service Elastic IP Pool |
200.200.20.10-200.200.20.100 255.255.255.0 |
255.255.255.0 |
For all resource pools. eth5. |
|
|
Shared Service Elastic IP Pool Gateway |
200.200.20.1 255.255.255.0 |
255.255.255.0 |
|
|
|
Shared Service IP |
200.200.20.1 255.255.255.0 |
255.255.255.0 |
|
|
|
Cloud Security Service Platform Management IP |
172.16.200.210 255.255.255.0 |
255.255.255.0 |
|
|
|
Cloud Security Service Platform Service IP |
200.200.20.210 255.255.255.0 |
255.255.255.0 |
|
|
|
Ethernet Switch |
Management Interface IP |
172.16.200.105-109 255.255.255.0 |
255.255.255.0 |
|
|
Network Plane |
Aggregation Mode |
Switch Interface Type |
Load Balancing Mode |
VLAN |
|
Management Network |
N/A |
access |
Manual Load Sharing Mode |
200 |
|
VXLAN Network |
Load Based on IP Addresses |
access |
Manual Load Sharing Mode |
201 |
|
Business Network |
N/A |
trunk |
Manual Load Sharing Mode |
N/A |
|
Storage Area Network |
Link Aggregation with Two Switches |
access |
Manual Load Sharing Mode |
202/203 |