In a bridged networking environment, virtual IP addresses (VIPs) are
used to provide a group of network services such as elastic IP address (EIP), port
forwarding, load balancing, and IPsec tunnel. Packets will be sent to VIPs and then
routed to the VM networks.
The VIP created from a public network can be used to provide network services
such as EIP and load balancing for flat networks.
The VIP created from a public network can be used to provide network services,
such as EIP, port forwarding, load balancing, and IPsec tunnel, for vRouter
networks and VPC networks.
The VIP created from a VPC network can be used to provide load balancing
services for VPC networks.
The VIP created from a flat network can be used to provide network services,
such as EIP and load balancing, for flat networks.
The following is an example of providing the load balancing service by
using a VIP, as shown in Provide Load Balancing by Using VIP.Figure 1. Provide Load Balancing by Using VIP
Definitions related to VIP:
Public VIP: The VIP created from a public network. A public VIP can be created
manually, or created automatically by the Cloud after a vRouter is created.
A public VIP can provide network services, such as EIP and load
balancing, for flat networks. A public VIP can also provide network
services, such as EIP, port forwarding, load balancing, and IPsec
tunnel, for vRouter networks and VPC networks.
A public VIP can be simultaneously applied to services such as port
forwarding, load balancing, and IPsec tunnel, and supports multiple
instances of the same service type. Note that different types of
services cannot use the same port No.
A public VIP supports QoS, monitoring data, performance TOP 5,
performance analysis, alarm, and other features.
VPC VIP: The VIP created from a VPC network. A VPC VIP can only be created
manually.
A private VPC VIP can provide load balancing services for VPC
networks.
Currently, private VPC VIPs do not support QoS, monitoring data,
performance TOP 5, performance analysis, and alarm features.
Private VIP: The VIP created from a flat network. A private VIP can be created
manually, or created automatically by the Cloud after a vRouter is created.
A private VIP provides network services, such as EIP and load balancing,
for flat networks.
A private VIP supports QoS, monitoring data, performance TOP 5,
performance analysis, alarm, and other features.
Custom VIP: The VIP manually created by a user. Public VIPs, VPC VIPs, and
private VIPs can be created manually.
One custom public VIP is only applied to one EIP service instance.
Custom VIPs cannot be used across normal vRouters or VPC vRouters.
When you use the EIP, port forwarding, load balancing, or IPsec tunnel
services, you can select Create new IP to create
a new VIP, or you can select Use existing IP to
provide corresponding services.
System VIP: The VIP automatically created by the Cloud by using the L3 network
attached by a vRouter (a normal vRouter or VPC vRouter) after the vRouter is
successfully created. Both public VIPs and private VIPs can be created
automatically by the Cloud after a vRouter is created.
A system VIP has a one-to-one relationship with a vRouter or VPC
vRouter. Each time a vRouter attaches a public network, the Cloud will
automatically create a system VIP. In addition, the system VIP is the
same as the default IP address of the vRouter or VPC vRouter.
By default, the system VIPs created from public networks are used to
provide the source network address translation service.
When you use the EIP, port forwarding, load balancing, or IPsec tunnel
service, you can select Use existing IP to
provide corresponding services.
