Problem Description

The VM in the VPC expect to use the network segment starting with 11 to communicate with Physical Network, but the newly created VPC subnet in the SCP platform can only use the IP range starting with 192/172.16/10

Warning Information

Unable to manually create a VPC subnet with an IP range starting with 11 in a VPC

Effective troubleshooting steps

Part 1: Create a custom VPC subnet using commands in SCP

ssh -p 22345 root@SCP_IP Use SSH to access the SCP platform, -p SSH port, SCP_IP is the IP address of SCP

source /sf/bin/keystonerc_admin //List Tenant ID information

65196d2574fb48a18f3e52c8c08692a3 | sangfortest | //This is the Tenant ID. We will build a VPC subnet under this Tenant, so we will use this parameter in the next step.
a5a2d1ef81d84fc784adceea19a8ab0e | admin     //This is the admin ID

nebular network-list –project-id 65196d2574fb48a18f3e52c8c08692a3

The execution results are as follows:
id  f8674506-ac14-471d-a861-1dc7921d5d1f   //The next step uses this parameter as netdomain-id
az_id  0ae17b9f-084f-4692-98bd-6aa6aa4c45a5    //This parameter does not need to be used

nebular netdomain-subnet-create –netdomain-id f8674506-ac14-471d-a861-1dc7921d5d1f –name 'Return' –allocation-pools 11.12.12.2-11.12.12.250 –cidr 11.12.12.0/24 –gateway-ip 11.12.12.254 –enable-dhcp 1        –netdomain-id  is the execution result of the previous step

–name  VPC subnet name, such as [return]
–allocation-pools  Subnet address pool, set to 11.12.12.2-11.12.12.250
–cidr  cidr IP range, set to 11.12.12.0/24
–gateway-ip  Subnet gateway, here it is set to 11.12.12.254
–enable-dhcp  Enable DHCP for the subnet, 1 for enable

Part 2: Creating Direct Connection VPC
Manually add an enterprise dedicated line in the VPC subnet [Return] and set the VLANID to 112

Part 3: Manually modify the virtual Route (layer 3) configuration in the acloud virtual topology
Log in to acloud's Topology to view and modify it. You can see that the corresponding virtual Route (layer 3) DHCP pool is 11.12.15.1-254, and the Gateway points to 254 (Route (layer 3) interface address). Modify the Route (layer 3) DHCP address pool to 11.12.12.2-11.12.12.250 and Route (layer 3) interface address 11.12.12.1, gateway address 11.12.12.254 and other information as needed.

Root cause

VPC subnets currently do not support custom VPC subnet address ranges. In some scenarios, you need to define them yourself.

solution

Medium, the subnet meets the requirements as long as the subnet does not overlap with the external network.

Original Link

https://support.sangfor.com.cn/cases/list?product_id=36&type=1&category_id=19509&isOpen=true