1/4
Sangfor HCI – Active/Active NICs connected to two independent Nexus switches without LACP/vPC

Newbie379943 Lv1  Posted 2026-Sep-16 21:12

Hi everyone,

I have a Sangfor HCI host with two physical NICs, and each NIC is connected to a different Cisco Nexus 3K switch.

The topology is:

                 Sangfor HCI Host
                ┌───────────────┐
                │                                    │
             NIC 1                            NIC 2
                │                                   │
                ▼                                  ▼
           Nexus A                        Nexus B

The two Nexus switches are completely independent without vPC.

I would like to have both NICs active simultaneously, similar to VMware NIC teaming, so that traffic can be distributed across both physical interfaces.

The goal is to have active/active NICs with two independent upstream switches, while maintaining redundancy and distributing traffic between the interfaces.

My questions are:

- Is it possible to configure the Sangfor host in active/active mode with the two NICs connected to completely independent Nexus switches?
- If so, which Sangfor mode should be used?
- Should I use Static Link Aggregation, or is there another configuration specifically designed for this scenario?
- What configuration should be used on the Nexus ports?
- Can the Nexus ports simply be configured as independent ports (no port-channel/LACP)?

The important constraint is that the two Nexus switches cannot be interconnected in any way.

I would appreciate any advice or examples from someone who has implemented Sangfor HCI with dual NICs connected to independent switches.

Thanks!

admin has solved this question and earned 10 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

Conclusion:
Yes, you can achieve active/active redundancy for an HCI host connected to two independent Nexus switches without using LACP. The correct Sangfor mode is Active-Backup for the aggregate interface, and the Nexus ports must be configured as independent access/trunk ports with no port-channel or LACP configuration. This is the supported configuration for connecting an HCI host to two independent switches for active/standby redundancy at the link level, which satisfies the requirement for dual-switch resilience without switch-side aggregation.

Configuration Steps:
1. Log in to the HCI console and navigate to Nodes → Physical Interfaces.
2. Click Add Multiple Aggregate Interfaces to create a new aggregate interface.
3. Select the two physical NICs that will connect to the two independent Nexus switches.
4. In the Load Balancing Mode settings, select Active-Backup.
5. Complete the interface configuration. In Active-Backup mode, one NIC acts as the primary link and the other as the standby link. Traffic flows through the primary NIC; if it fails, the standby NIC takes over automatically.
6. On the Nexus switches, configure the two connected ports as regular access or trunk ports according to your VLAN requirements. Do not configure port-channel, LACP, or any form of link aggregation on the switch side, as this mode does not require the peer switch to participate in an aggregation protocol.


Before You Start
-The aggregate interface can only select unused network interfaces. If a used interface needs to be added, it must first be released by switching its role to another interface.
- Active-Backup mode only supports the aggregation of two network interfaces. You cannot add a third NIC to this aggregate.- Optical and electrical interfaces do not support aggregation with each other. Both interfaces in the pair must be of the same type.
- Configuring an aggregate interface clears the original IP addresses and any VLAN configuration on the member interfaces. Plan to reconnect using the new aggregate interface after setup.
Notes
- The Active-Backup mode provides link-level redundancy. For true active/active load balancing across two independent switches, the HCI platform requires the switches to be configured in a stack or M-LAG arrangement, and the storage network would use the Standard Link Aggregation mode. The Link Aggregation with Two Switches mode is no longer supported for new deployments starting from HCI 6.7.0.
- When selecting the Active-Backup mode, traffic will prioritize the primary network port you designate during configuration.

If you want to know more details, please chat with Sangfor AI assistant - Solvia.

Is this answer helpful?
admin  Posted 2026-Sep-28 11:00
  
Conclusion:
Yes, you can achieve active/active redundancy for an HCI host connected to two independent Nexus switches without using LACP. The correct Sangfor mode is Active-Backup for the aggregate interface, and the Nexus ports must be configured as independent access/trunk ports with no port-channel or LACP configuration. This is the supported configuration for connecting an HCI host to two independent switches for active/standby redundancy at the link level, which satisfies the requirement for dual-switch resilience without switch-side aggregation.

Configuration Steps:
1. Log in to the HCI console and navigate to Nodes → Physical Interfaces.
2. Click Add Multiple Aggregate Interfaces to create a new aggregate interface.
3. Select the two physical NICs that will connect to the two independent Nexus switches.
4. In the Load Balancing Mode settings, select Active-Backup.
5. Complete the interface configuration. In Active-Backup mode, one NIC acts as the primary link and the other as the standby link. Traffic flows through the primary NIC; if it fails, the standby NIC takes over automatically.
6. On the Nexus switches, configure the two connected ports as regular access or trunk ports according to your VLAN requirements. Do not configure port-channel, LACP, or any form of link aggregation on the switch side, as this mode does not require the peer switch to participate in an aggregation protocol.


Before You Start
-The aggregate interface can only select unused network interfaces. If a used interface needs to be added, it must first be released by switching its role to another interface.
- Active-Backup mode only supports the aggregation of two network interfaces. You cannot add a third NIC to this aggregate.- Optical and electrical interfaces do not support aggregation with each other. Both interfaces in the pair must be of the same type.
- Configuring an aggregate interface clears the original IP addresses and any VLAN configuration on the member interfaces. Plan to reconnect using the new aggregate interface after setup.
Notes
- The Active-Backup mode provides link-level redundancy. For true active/active load balancing across two independent switches, the HCI platform requires the switches to be configured in a stack or M-LAG arrangement, and the storage network would use the Standard Link Aggregation mode. The Link Aggregation with Two Switches mode is no longer supported for new deployments starting from HCI 6.7.0.
- When selecting the Active-Backup mode, traffic will prioritize the primary network port you designate during configuration.

If you want to know more details, please chat with Sangfor AI assistant - Solvia.

I Can Help:

Change

Board Leaders

George ...

Weekly Sharers

George ...

Weekly Questioners