Solved

LACP Configuration with Nutanix (Server 2019 Hyper V)

  • 3 March 2021
  • 1 reply
  • 52 views

Badge

Hi Team,

I am planing to deploy Nutanix 3 node with Hyper V. so i want to know that intial deployment

can I use LACP on Switch Side.

please guide me LACP configuration for Nutanix side?

Environment:

  1. Network :
    1. IPMI
    2. Hyperviser Management Subnet - 10 G Port 1 and 2 -LACP
    3. Guest VM Subnet - 10 G Port 3 and 4 -LACP
    4. Guest VM Second Subnet - 1 G Port 1 and 2
    5. Two 10 G Switch
    6. Two 1 G Switch
icon

Best answer by Alona 8 March 2021, 06:10

Hi Muhammed,

For LACP you would need Switch Dependent mode with LACP setting. We recommend Hyper-V Port load balancing mode as it gives each VM a MAC address. You will need to configure physical switches with LACP to be able to use LACP on the hypervisor side.

Microsoft: NIC Teaming settings

Microsoft: Set-NetLbfoTeam (use Get-NetLbfoTeam to get the NetAdapterName)

Also, note that on Hyper-V 2019 LACP is not supported with SET (Switch Embedded Teaming).

As per the NICs grouping

  1. IPMI
  2. Hypervisor and CVM Subnet - 10 G Port 1 and 2 -LACP, externalswitch - created by default
  3. Guest VM Subnet - 10 G Port 3 and 4 -LACP - custom switch 0
  4. Guest VM Second Subnet - 1 G Port 1 and 2
  5. Two 10 G Switch
  6. Two 1 G Switch

The way I’d do this is I’d image the cluster with default switch configuration (i.e. one switch externalswitch with all interfaces there).

Then evict 1G ports from the aggregate/bond and configure LACP. Test.

Then create another switch (custom switch 0) and move the uplinks there. Test both custom switch 0 and externalswitch.

Create custom switch 1 with 1G uplinks in active/passive mode otherwise, you will have a loop on the switch.

View original

This topic has been closed for comments

1 reply

Userlevel 6
Badge +5

Hi Muhammed,

For LACP you would need Switch Dependent mode with LACP setting. We recommend Hyper-V Port load balancing mode as it gives each VM a MAC address. You will need to configure physical switches with LACP to be able to use LACP on the hypervisor side.

Microsoft: NIC Teaming settings

Microsoft: Set-NetLbfoTeam (use Get-NetLbfoTeam to get the NetAdapterName)

Also, note that on Hyper-V 2019 LACP is not supported with SET (Switch Embedded Teaming).

As per the NICs grouping

  1. IPMI
  2. Hypervisor and CVM Subnet - 10 G Port 1 and 2 -LACP, externalswitch - created by default
  3. Guest VM Subnet - 10 G Port 3 and 4 -LACP - custom switch 0
  4. Guest VM Second Subnet - 1 G Port 1 and 2
  5. Two 10 G Switch
  6. Two 1 G Switch

The way I’d do this is I’d image the cluster with default switch configuration (i.e. one switch externalswitch with all interfaces there).

Then evict 1G ports from the aggregate/bond and configure LACP. Test.

Then create another switch (custom switch 0) and move the uplinks there. Test both custom switch 0 and externalswitch.

Create custom switch 1 with 1G uplinks in active/passive mode otherwise, you will have a loop on the switch.