To ensure that interfaces are manageable and extensible, multiplexing of the following interfaces is not recommended: Management interfaces, VXLAN overlay network interfaces, VS storage network interfaces, and VM network interfaces. When interfaces are insufficient, it is recommended to configure multiplexing for the VM network interfaces and VXLAN interfaces. The following network interfaces are required: Two management interfaces, two storage network interfaces, two aggregate interfaces used for VXLAN and VM network interface multiplexing, and two DR transmission interfaces. The DR transmission interfaces are used to transmit backup data between the primary and secondary sites. The table below describes other precautions.
Type
Recommended Configuration
Precautions
Physical interface
Recommended: 6 * GE + 2 * 10GE
Networks slower than 1 Gbit/s are not allowed.
DR transmission interface
It is recommended to use dedicated DR transmission interfaces, which can reduce the traffic loads of other interfaces and facilitate interface management and extension.
If no dedicated interface is available, you can use management interface multiplexing. However, you need to consider whether the management interfaces can withstand the DR traffic.
Storage network
Aggregate two 10GE interfaces through Link Aggregation Control Protocol (LACP) and use Layer 4 load balancing.
10GE interfaces are required for building the storage network.
It is not allowed to disable link aggregation.
Management network
Aggregate two GE interfaces through LACP and use Layer 4 load balancing.
Deploy peering switches in stacking or M-LAG mode, and configure static interface aggregation.
The switches that provide cluster management interfaces and overlay network interfaces must support multicasting. Otherwise, clusters cannot be created.
A connectivity test uses ping packets. A connectivity test is passed when the ping succeeds, even if multicasting is not supported.
VM network interface and VXLAN interface multiplexing
1. Aggregate two GE interfaces through LACP and use Layer 4 load balancing for VM network interface and VXLAN interface multiplexing.
2. When the VM network interface traffic and VXLAN interface traffic are heavy, use two 10GE interfaces or use dedicated interfaces to forward VM network interface traffic and VXLAN interface traffic.
Deploy peering switches in stacking or M-LAG mode, and configure static interface aggregation.
The VXLAN network of the HCI must have the high performance mode enabled. The peering switch must have jumbo frames enabled and set to a value greater than 1600. Set jumbo frames to 2000 for a Sundray switch.
Switch
Disable STP for the switch interfaces or configure the ports that are connected to HCI as edge ports. Deploy the switches in stacking or M-LAG mode.
Deploying only one switch without redundant switches is not allowed.
IP address
It is recommended to use different network segments as the management, VXLAN, and VM network segments to avoid IP conflicts.
-
Connection between the primary and secondary sites
You need to consider whether the bandwidth of the connection between the primary and secondary sites is sufficient to complete backup data transmission within the expected RPO. For more information, see the DR Resource Estimation section.
{{ $t('index.defaultHeader.chromeBrowserTip') }}