ACOS networks consist of physical networks and virtual networks.
ACOS physical networks consist of physical devices interconnected through network cables, including physical network ports, physical switches, routers, and other physical devices.
ACOS virtual networks consist of the management plane and data plane.
The management plane is used to manage VDSs, system networks, and VM networks. Its management functions are mainly provided by the AOC virtual network management module.
VDS management
You can create a VDS on the AOC interface by associating one or more network ports of physical hosts. When multiple physical network ports are selected, you need to select a network port bonding mode to ensure high availability of the network ports. You can also use AOC to modify the VDS name, associated network ports, and network port bonding mode.
After a VDS is created, the corresponding VDS data plane instance (OVS bridge) is generated on the physical hosts associated with the VDS to forward network traffic between physical hosts.
System network management
You can create a system network on a VDS through the AOC interface and configure the IP address, subnet mask, VLAN ID, MTU, default route, static route, QoS, and other settings for the system network. The VDS where the system network resides must be associated with all physical hosts in the cluster.
VM network management
You can create a VM network on a VDS through the AOC interface. When creating a VM network, you can configure the VLAN ID and QoS policy for the VM network. When a VM network is assigned to a virtual NIC, the virtual NIC inherits the VLAN ID and QoS policy of the VM network.
The data plane is the entity that performs traffic forwarding, forwarding policy matching, and QoS rate limiting. The data plane is distributed on each ACOS node.
VDS data plane instance
A VDS creates a data plane instance (OVS bridge) on each associated physical node to execute the forwarding logic of the VDS. The OVS bridge provides communication capabilities between virtual machines on the node and connects the ACOS node to the external physical network by adding the physical network ports of the associated host to virtual ports on the OVS bridge.
System network instance
A system network is a system virtual network interface used by host system services. Each system network interface is an OVS internal port created on the OVS bridge. After an IP address, subnet mask, and other parameters are configured for the corresponding internal port, the system network can use the system network protocol stack to communicate with other nodes or services.
System networks support the following configuration parameters:
| System network type | IP | Subnet mask | VLAN ID | QoS | MTU | Gateway | Static route |
|---|---|---|---|---|---|---|---|
| Management network | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | X |
| Storage network | ✓ | ✓ | ✓ | ✓ | ✓ | X | X |
| Access network | ✓ | ✓ | ✓ | ✓ | ✓ | X | ✓ |
| Migration network | ✓ | ✓ | ✓ | ✓ | ✓ | X | X |
| Mirroring egress network | ✓ | ✓ | ✓ | ✓ | ✓ | X | ✓ |
VM network instance
A VM network is a logical concept. On the data plane, it corresponds to a VLAN port group configured on a virtual switch. When a virtual NIC of a virtual machine is associated with the corresponding VM network, the virtual NIC inherits the VLAN ID configured for the VM network. When a virtual port is created on the OVS bridge, the corresponding VLAN ID is set on the virtual port (Access type). When QoS is configured for a VM network, all virtual NICs added to the VM network share the bandwidth settings of the VM network QoS.
