Create Subnet

1. Click the VPC name to enter the page of subnet list under it, and create the subnet within the VPC network range.

   • Available zone: Select the available zone where the subnet is located. It is recommended to deploy the business system in different available zones to improve the disaster recovery of the system. For more descriptions, please refer to Description on Available Zone.
   • Device type: General type, BBC special type (used to place BBC instances, white list visible).
   • CIDR: The CIDR block of the subnet is the subset of CIDR blocks of the VPC. If you create multiple subnets in the VPC, the CIDR blocks of the subnets cannot overlap. The allowed block size is between / 16 bit mask and / 29 bit mask.

   For example, when one VPC of "172.16.0.0/24" is created, if you want to create three subnets in the address space, the CIDR blocks are respectively:

   Subnet 1: 172.16.0.0/26, address space: 172.16.0.0--172.16.0.63;

   Subnet 2: 172.16.0. 192/26, address space: 172.16.0. 192 -- 172.16.0.255;

   Subnet 3: 172.16.0. 64/26, address space: 172.16.0. 64 -- 172.16.0.127;

   

2. Assign BCC instances to each subnet, and click the host number of the subnet (0 when no BCC instance is assigned) to enter the page of instance list.

3. Create a BCC instance, and enter the configuration information. For the details, please refer to Create BCC Instance.

   It is recommended to select the "Prepaid" purchase mode, and fill in the relevant configuration information.

4. Click "Next" to purchase an elastic IP.

5. Click "Next", confirm the order and pay to complete subscription.

   After an instance is created, you will receive a message to notify you of the information such as creation of the BCC instance, instance name, private network and public network IP, user name and available zone.

Up to this point, you create a VPC and subnet, and assign the associated BCC instance to the subnet. You can access your BCC example by SSH and the remote desktop. For the detailed operation process, please refer to Log in to BCC Instance.

Note:

• All subnets are connected by default.
• With instances bound to EIP in the subnet, if EIP route conflicts with NAT route after adding NAT route, EIP route will be preferred.
• If the created subnet overlaps with the IP address range of affiliated VPC routing entry, a pop-up box will appear; if you continue to create the subnet, the traffic will prioritize the subnet in case of routing conflict, rather than the peer.