VIP

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.

Create Custom IP

In the navigation pane of the ZStack Private Cloud UI, choose Network Service > VIP. On the Custom tab page, click Create VIP. On the displayed Create VIP page, set the following parameters:
  • Name: Enter a name for the VIP.
  • Description: Optional. Enter a description for the VIP.
  • Network: Select the network that provides a VIP.
    • 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.
  • IP Range: Optional. Specify an IP range. Note that an IPv4 public network allows you to select a normal IP range or an IP address pool.
  • Specify IP: Optional. Specify a VIP. If not specified, the Cloud will automatically assign a VIP.
  • Add VIP QoS: For public VIPs and private VIPs, you can set the VIP QoS to manage your network bandwidth. You can set the QoS directly when you create a custom VIP, or add QoS after you create a custom VIP.
    • Port: Optional. Specify the QoS policy for a port. Allowed port range: 1-65535. If not specified, the QoS policy applies to ports 1-65535.
      Note: You can set multiple QoS policies for the same public VIP or private VIP. The QoS policies without port settings have the lowest priority.
    • Upstream Bandwidth: Optional. Set the upper limit of the upstream bandwidth for the VIP. Unit: Mbps. If not specified, the upstream bandwidth will not be limited.
    • Downstream Bandwidth: Optional. Set the upper limit of the downstream bandwidth for the VIP. Unit: Mbps. If not specified, the downstream bandwidth will not be limited.
    Click OK to submit your settings, as shown in Figure 2.
    Figure 2. Add VIP QoS


    Then, you can click Add VIP QoS to add more QoS policies.
The following is an example of creating a public VIP, as shown in Figure 3. Click OK to finish creating the VIP.
Figure 3. Create VIP


VIP Operations

You can perform the following operations on a VIP:
  • Create VIP: Create a custom VIP. Note that system VIPs are created automatically by the Cloud.
  • Change name and description: Change the name and description of the VIP.
  • Change owner: Change the owner of the VIP.
  • Delete:
    • Custom VIP:
      • Deleting a custom VIP will also delete the services associated with the VIP.
      • Deleting a service of a custom VIP does not affect other services associated with the VIP.
    • System VIP:
      • Deleting a service of a system VIP does not affect other services associated with the VIP.
      • Deleting a normal vRouter or VPC vRouter will also delete all services associated with the corresponding system VIPs.
  • Add/Delete QoS: Add QoS to or delete QoS from a public VIP or private VIP to control the port traffic of the corresponding VIP. This operation can be performed on the QoS tab of the VIP details page.
    Note:
    • In a flat network scenario, a custom VIP can be used for EIP and load balancing services. Therefore, the QoS feature of a VIP can be applied to EIP and load balancing services.
    • In a vRouter network or VPC network scenario, a custom VIP can be used for EIP, port forwarding, load balancing, and IPsec tunnel services. Therefore, you can set QoS for custom VIPs that provide these four services.
    • A system VIP can be used for port forwarding, load balancing, and IPsec tunnel services. Therefore, you can set QoS for system VIPs that provide these three services.
    • Multiple QoS rules can be set for the same VIP. Note that the QoS rules without port configurations have the lowest priority.
    • Currently, both VPC private VIPs and IPv6 VIPs do not support QoS configurations. If you create a vRouter network by using a vRouter image with the VirtualRouter type, you cannot configure the VIP QoS.
  • Monitoring alarm: ZStack supports VIP alarms. After you create an alarm and add the corresponding metric items, the Cloud will automatically monitor multiple metric items associated with the VIP and send alarm messages via email, DingTalk, HTTP application, short message service, or Microsoft Teams.
  • Monitoring data: Provide real-time display of the network traffics and packets of the public VIP.
  • Audit: View related operations of the VIP.