{{ $t('productDocDetail.guideClickSwitch') }}
{{ $t('productDocDetail.know') }}
{{ $t('productDocDetail.dontRemind') }}
6.11.3
{{sendMatomoQuery("Sangfor Cloud Platform (SCP)","Recommended Networking Configuration")}}

Recommended Networking Configuration

{{ $t('productDocDetail.updateTime') }}: 2025-12-31

Type

Recommended Configuration

Precautions

Physical interface

Recommended: 6 * GE + 2 * 10GE

Networks slower than 1 Gbit/s are not allowed.

Storage network

It is recommended to 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 at least two GE interfaces through LACP and use Layer 4 load balancing.

1. Deploy peering switches in stacking or M-LAG mode, and configure LACP aggregation.

2. The switches that provide cluster management interfaces and overlay network interfaces must support multicasting. Otherwise, clusters cannot be created.

3. A connectivity test uses ping packets. A connectivity test is passed when the ping succeeds, even if multicasting is not supported.

4. Do not enable IGMP Snooping.

VM network

Aggregate at least 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.

VXLAN

1. Aggregate at least two GE interfaces through LACP and use Layer 4 load balancing.

2. When network interfaces are insufficient, you can multiplex the VM network interface and VXLAN interface. When VM traffic and VXLAN traffic are heavy, aggregate two 10GE interfaces or use dedicated interfaces to forward VM traffic and VXLAN traffic.

1. Deploy peering switches in stacking or M-LAG mode, and configure LACP aggregation.

2. The VXLAN network of the HCI platform 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.

3. Do not enable IGMP Snooping.

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.

Different HCI interfaces cannot use IP addresses belonging to the same network segment.

Cable specifications

It is recommended to use a multimode optical fiber if the distance does not exceed 50 meters, and use a single-mode optical fiber if the distance exceeds 50 meters.

It is recommended to use twisted pairs of Category 5 or above.

Do not connect a single-mode optical fiber to a multimode module.

Do not connect a multimode optical fiber to a single-mode module.

Do not use twisted pairs of Categories 1 to 4.

Active-active networking

1. It is recommended to use bandwidth higher than 100 Mbps for communication between witness nodes and between the primary and secondary fault domains, with a network latency of 1 millisecond or lower. Network latency fluctuations within 5 milliseconds can be tolerated.

2. For datastores of stretched clusters, it is recommended to use 10 Gbit/s optical fiber connections between the primary and secondary fault domains, with a network latency of 1 millisecond or lower.

-

  1. Confirm whether the switch connected to the overlay network interface supports jumbo frames. If yes, it is recommended to enable the high performance mode of the overlay network interface by setting the MTU of the VXLAN interface to 1600. If not, do not enable the high performance mode of the overlay network interface. Otherwise, data cannot be exchanged between VMs.
  2. A connectivity test uses ping packets. A connectivity test is passed when the ping succeeds, even if multicasting is not supported.
  3. It is not recommended to multiplex the following types of communication interfaces: Management interface, VXLAN interface, virtual storage network interface, and edge. Before you configure multiplexing, check whether the NIC is listed in the list of compatible NICs. When you need to multiplex the edge and VXLAN interface due to insufficient network interfaces, it is recommended to prepare two management interfaces and two storage network interfaces, and aggregate two interfaces and multiplex the aggregate interface as the VXLAN interface and edge.
  4. Reinserting the NIC of a third-party server or HCI aServer may result in disordered network interfaces. To address this issue, use the latest aDeploy tool.