Binding an ENI

Last updated: 2019-11-05 15:31:34

PDF

ENI Overview

Elastic Network Interface (ENI) refers to the type of virtual network interfaces that can be bound to CVM instances in VPCs. An ENI can be migrated freely between CVM instances within the same VPC and AZ, helping you easily build high-availability clusters, implement low-cost failover, and manage networks in a more refined manner.
CLB instances can be bound to CVM and ENI, so that CVM and ENI can work as real servers. Specifically, a CLB instance communicates with the real server over the private network, and if multiple CVM instances and ENIs are bound to the CLB instance, access traffic will be forwarded to the private IPs of the CVM instances and ENIs.

The ENI binding feature of CLB is currently in beta test. If you want to use it, please submit a ticket for application.

Prerequisites

An ENI must be bound to a CVM instance first before it can be bound to a CLB instance. As a CLB instance only forwards traffic as a load balancer but does not process the business logic, the CVM instance, as a computing resource, is needed to process user requests. Please log in to the ENI Console to bind the required ENI to the CVM instance first.

Directions

  1. You need to configure a CLB listener first. For more information, see CLB Listener Overview.
  2. Click + on the left of the created listener to expand the domain names and URL paths, select the desired URL path, and view the bound real servers on the right of the listener.
  3. Click Bind and select the real server to be bound and configure the server port and weight in the pop-up window. You can select any CVM instance and ENI that can be bound to the CLB instance in the same VPC.
  4. The specific configuration after binding is as shown below: