Sangfor Community»Categories Cloud & Infrastructure Hyper Converged Infrastructure (HCI/aSV) Sangfor HCI Network Design (No virtual storage)

Sangfor HCI Network Design (No virtual storage)

views: 129 | comments: 2 | added to Favorites 0
Lights on | 提示:支持键盘翻页<-左 右->
    组图打开中,请稍候......
Created: Mar-07-2026 22:20

Summary:

Hello, I am planning to deploy Sangfor HCI in a traditional architecture. I will not use the built-in virtual storage of Sangfor. Instead, the storage will be provided from an external storage system ...

Reply

Muhammad Abid Posted Mar-08-2026 02:40
If you deploy Sangfor HCI with external storage via Fibre Channel (FC) and do not use the built-in distributed storage, then a dedicated Storage Network in Sangfor is not required. Storage traffic will go through FC HBA → FC Switch → Storage, not through the Ethernet NICs.

Recommended Network Design

2 × 10 Gbit Interfaces

Create an LACP bond using the two 10G ports.

Use this bond for Edge Network and Overlay Network (with VLAN separation).

These networks carry the highest traffic (VM traffic and external access).

4 × 1 Gbit Interfaces

Use one 1G NIC for the Management Network.

The remaining ports can be used for IPMI, monitoring, backup, or kept as spare.

Simple Layout
Network        Interface
Edge Network        10G Bond
Overlay Network        10G Bond
Management Network        1G NIC
Storage        Fibre Channel

✅ Conclusion:
Using LACP on the two 10G interfaces for Edge and Overlay networks and a 1G NIC for Management is a best-practice design. A Storage Network is not needed because storage connectivity is handled through Fibre Channel.





Muhammad Abid Posted Mar-09-2026 11:03
Yes, your configuration is correct for a nested or test environment in Sangfor HCI.

Using the same physical interface for both Edge and Overlay networks and separating them with VLANs is a supported approach. For example, configuring the Edge network on the main trunk interface and the Overlay network on a VLAN sub-interface (e.g., VLAN 103) is a valid design.

The Overlay network usually does not require a gateway, because it is mainly used for host-to-host communication through **VXLAN tunnels inside the cluster.

However, the Overlay VLAN must exist on the physical switch and be allowed on the trunk port connected to the host, since the underlay network still relies on that VLAN for transport between nodes.

In production environments, it is recommended to use bonded 10G interfaces (LACP) for better redundancy and performance.