Similar to a private IP, HAVIP can also be bound or unbound on the console. Binding a HAVIP refers to EIP operations. Please skip this section if you don't need public network communication.
- A HAVIP can only be bound with one EIP. If no EIP is available, first go to the EIP console to create one.
- If the HAVIP is not bound with a CVM instance, the EIP bound to this HAVIP will be in idle status and incur an idle fee. Please correctly configure HAVIP and bind it to instances by referring to the following cases:
- Building High Availability Primary/Secondary Cluster by Using HAVIP + Keepalived under Best Practice
- Creating a High-availability Database by Using HAVIP + Windows Server Failover Cluster under Best Practice
- Your public network business may be affected after unbinding the EIP. Please get ready in advance.
- After being unbound, the EIP will be idle and incur an idle fee. You can directly release unused EIPs to avoid costs.