NIC Teaming need to configure the Server after Windows Failover cluster configuration

Jayakumar D (EXT) / TELC 0 Reputation points
2025-09-24T16:39:57.7533333+00:00

Hi,

I am using HP ProLiant DL360 Gen10 Plus Server, Windows Server 2022 std has been installed and configure in Windows failover cluster 2 node based.

There is 4 Nic card 1 Gbps Speed currently using, 2 Nic only active and connected.

I Need to configure the NIC Teaming & Merge 4 Nic card in Teaming.

We Need your input. is there any issue after Windows failover cluster configure, NIC teaming configuration.

Windows for business | Windows Server | Storage high availability | Clustering and high availability
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Oliver Nguyen 1,400 Reputation points
    2025-09-24T17:43:08.0166667+00:00

    Hi Jayakumar,

    Open Server Manager > Local Server > NIC Teaming (currently showing as Disabled). Right-click one of the network adapters and select "Add to New Team". Select all four 1 Gbps NICs you want to include in the team and provide a team name.

    Recommended Team Settings:

    Configure the team with Switch Independent mode and Dynamic load balancing algorithm for optimal performance. Dynamic load balancing provides better throughput distribution across team members compared to other algorithms. Set the team to Active/Active mode rather than Active/Standby to utilize all four NICs simultaneously.

    After creating the NIC team, configure the cluster networks through Failover Cluster Manager. The teamed interface will appear as a single network adapter in cluster network settings. Assign appropriate roles such as "Allow cluster network communication" and "Allow clients to connect through this network". The teamed NICs can be effectively used for Live Migration traffic, providing increased bandwidth and fault tolerance. Configure the team as part of your Live Migration network in Hyper-V settings for improved VM migration performance.

    IP Address Assignment: Configure IP addresses on the logical teamed interface rather than individual NICs. The team presents itself as a single network adapter to the operating system, requiring only one IP configuration.

    HP-Specific Recommendations

    Use Windows Native Teaming:

    HP recommends using Windows Server native NIC teaming instead of HPE-specific teaming software for Gen10 servers. Windows native teaming provides better integration with failover clustering and is fully supported by Microsoft.

    LACP Compatibility: If your network switches support LACP (Link Aggregation Control Protocol), configure the team in LACP mode for optimal switch integration. However, Switch Independent mode works well if LACP is not available.

    =================================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.