L3 Network

An L3 network is a collection of network configurations for VM instances, including the IP range, gateway, DNS, and network services.
  • An IP range includes the start IP address, end IP address, netmask, and gateway. For example, specify the IP range from 172.20.12.2 to 172.20.12.255, set the netmask to 255.255.0.0, and set the gateway to 172.20.0.1. In addition, you can use a CIDR to specify an IP range, such as 192.168.1.0/24.
  • DNS provides DNS resolution services used for configuring VM networks.

Public Network

Generally, a public network is a type of network wherein anyone has access and through it can directly connect to the Internet. Due to a fact that the public network is a logical concept, you can also customize the public network when you cannot access the Internet. In addition, the public network can provide the network service in a vRouter network and a VPC network.
  • The public network can be used in the flat network environment to create VM instances.
  • The public network can be used in the vRouter network environment to create vRouters.
  • The public network can be used in the VPC network environment to create VPC vRouters.

System Network

A system network is a specific network used by a management node.
  • The system network can be used as a management network to deploy and set related resources, such as a host, primary storage, backup storage, and vRouter.
  • The system network can be used as a migration network to migrate VM instances.
  • Assume that your network resources are insufficient, and that you cannot use a management network separately. Then, the public network will act as the management network.
  • An independent system network can be used in a specific manner, such as managing the vRouter network.
  • The system network cannot be used to create regular VM instances.

Private Network

A private network is known as a business network or an access network. Generally, VM instances use the private network. The private network is specified as the network used by VM instances, and supports three network architecture models: flat network, vRouter network, and VPC network.

Specific Network Scenarios

  • Management Network
    A management network is a type of a system network, which can be used for managing and controlling the corresponding physical resources.
    • For example, when you access a host, a backup storage, a primary storage, and other resources that require an IP address, use the management network.
    • When you create vRouters or VPC vRouters, you need an IP address that can be interconnected between management networks in vRouters or VPC vRouters. With this IP address, you can deploy an agent and obtain messages returned by the agent.
  • Storage Network

    A storage network is the network specified by the shared storage. You can use the storage network to check the health state of a VM instance. We recommend that you plan for an independent storage network in advance to avoid potential risks.

  • VDI Network

    When you create clusters, you can specify CIDR for the VDI network. In the VDI scenario, the network traffics generated by the protocol communication between server side and client side use the VDI network. If you do not make any configuration to the VDI network, notice that the management network will be used by default.

  • Migration Network

    When you create clusters, you can specify CIDR for the migration network, which can be used for VM migrations. If you do not make any configuration to the migration network, notice that the management network will be used for VM migrations.

  • Image Synchronization Network
    An image synchronization network is the network that images can be synchronized among backup storages with the ImageStore type in the same management node.
    • If you have deployed an independent network for synchronizing images, you can specify CIDR for the image synchronization network.
    • If you do not make any configuration to the image synchronization network, the management network will be used by default.
    • If you set both source image store and target image store as the image synchronization network, only the target image store can take effect.
  • Data Network
    A data network is the network where data can transfer between a compute node and a backup storage.
    • If you use an independent data network, you can avoid network congestion, and improve the data transfer rate.
    • If you do not make any configuration to the data network, the management network will be used by default.
  • Backup Network
    ZStack provides backup services, which are add-on licensed features. A backup network is the network where you can back up your local VM instances, volumes, or databases to the local backup storage. Also, the backup network is the network where you can restore the local backup data from the local backup storage.
    • If you deploy an independent network for local backups, you can specify CIDR for the backup network.
    • If you use an independent network, you can avoid network congestion and improve the data transfer rate.
    • If you do not make any configuration to the backup network, note that the management network will be used for local backup by default.
    Note:

    Backup Service is a separate feature module. To use this feature, purchase both the Base License and the Plus License of Backup Service. The Plus License cannot be used independently.

  • Traffic Network

    A traffic network is the specified network of a port mirroring, which can be used to mirror the network traffic in the NIC to remote access. In addition, the traffic network cannot act as other networks, and cannot be used to create VM instances.

Notice

  • When you create VM instances, you can specify multiple networks. That is, you can specify multiple flat networks, vRouter networks, VPC networks, or a combination of flat networks, vRouter networks, and VPC networks.
  • We support multi-layer networks. In addition, the L2 networks of multi-layer networks can intercommunicate. Therefore, you need to pay a special attention to avoid the conflict of IP address spaces.
  • You can create multiple L3 networks by using an L2 network. If the L2 network is the HarewareVxlanNetwork type, the private network that you created can only support the flat network and other corresponding network services rather than vRouter network.