Updated on 2025-02-25 GMT+08:00

CloudDCN Subnet Overview

What Is a CloudDCN Subnet?

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.

Notes and Constraints

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: