Technology Encyclopedia Home >When a newly created elastic network card (i.e., secondary network card) is bound to a CVM instance, is the subnet to which the secondary network card belongs the same as the subnet to which the primary network card of the instance belongs?

When a newly created elastic network card (i.e., secondary network card) is bound to a CVM instance, is the subnet to which the secondary network card belongs the same as the subnet to which the primary network card of the instance belongs?

When a newly created elastic network card, also known as a secondary network card, is bound to a Cloud Virtual Machine (CVM) instance, it typically shares the same subnet as the primary network card of the instance. This is because the secondary network card is usually created within the same Virtual Private Cloud (VPC) and region as the primary network card, and thus inherits its subnet configuration.

For example, if the primary network card of a CVM instance is in the subnet 192.168.1.0/24, then a secondary network card created and bound to this instance will also be in the 192.168.1.0/24 subnet, unless specifically configured otherwise during its creation.

In the context of cloud services, such as those offered by Tencent Cloud, this behavior ensures seamless communication between the primary and secondary network cards and facilitates network management and security policies within the VPC.

If you need more advanced networking capabilities or want to customize your network configuration, Tencent Cloud offers a variety of networking services, including Virtual Private Cloud (VPC), Elastic Network Interface (ENI), and more, to meet your specific requirements.