CloudDCN Subnet Overview

With CloudDCN subnets, you can connect your physical servers (iMetal servers) to an isolated, private, and high-performance cloud network.

When creating a VPC, you cannot create a CloudDCN subnet. You need to create a CloudDCN subnet in an existing VPC for deploying iMetal servers.

Note the following when using CloudDCN subnets:

The DHCP lease time is not supported.
The DNS server address cannot be changed.
Virtual IP addresses cannot be assigned.
IPv6 addresses cannot be assigned.
Each CloudDCN subnet comes with a default route table, which cannot be modified.
Physical servers in a CloudDCN subnet cannot be associated with security groups.
CloudDCN subnets cannot be shared.
CloudDCN subnets does not support multicast.
ECSs and BMSs cannot be created in CloudDCN subnets.
CloudDCN subnets do not support flow logs. This means flow logs of the iMetal server in the CloudDCN subnet cannot be collected.
CloudDCN subnets cannot be used as the frontend or backend subnet of load balancers.
If you want to add an iMetal server in a CloudDCN subnet as the backend server of a load balancer, note the following:
- When adding a backend server, you can only select IP as a Backend. For details, see Adding Backend Servers in a Different VPC from a Load Balancer.
- When an iMetal server is added as a backend server, Transfer Client IP Address will not work even if it is enabled.