Supported networking changes

Contributors netapp-pcarriga netapp-dbagwell

After you deploy NetApp HCI, you can make limited changes to the default networking configuration. However, you must meet certain requirements for smooth operation and correct network detection. Not meeting these requirements will cause unexpected behavior and might prevent you from expanding compute and storage resources.

After you deploy your system, you can make the following changes to the default network configuration in VMware vSphere as dictated by your network requirements:

  • Change vSwitch names

  • Change port group names

  • Add and remove additional port groups

  • Change the vmnic interface failover order for any additional port groups you have added

When scaling H300E, H500E, H700E, H410C, H610C, and H615C compute nodes, NetApp HCI expects the existing compute cluster on the node to meet the following requirements:

  • A minimum of four vmk interfaces

  • One management vmk interface

  • One vmotion vmk interface

  • Two vmks on the same subnet with iSCSI bindings to the software iSCSI initiator

Note

Beginning with NetApp HCI 1.10, when you scale the cluster, NetApp HCI does not expect to meet the default node configurations.

After you change the default settings in VMware vSphere for one or more nodes in the existing compute cluster, the settings for the new node will align with the settings for the majority of the nodes in the cluster.

NetApp Deployment Engine default configurations

The NetApp Deployment Engine sets up default configurations for the compute hosts depending on the system and cable configuration.

H300E, H500E, H700E, and H410C compute nodes

The following is a six-interface configuration for H300E, H500E, H700E, and H410C nodes with VMware vSphere Distributed Switching (VDS). This configuration is only supported when used with VMware vSphere Distributed Switches, and requires VMware vSphere Enterprise Plus licensing.

Network function vmkernel vmnic (physical interface)

Management

vmk0

vmnic2 (Port A), vmnic3 (Port B)

iSCSI-A

vmk1

vmnic5 (Port E)

iSCSI-B

vmk2

vmnic1 (Port D)

vMotion

vmk3

vmnic4 (Port C), vmnic0 (Port F)

The following is a six-interface configuration with VMware vSphere Standard Switching (VSS). This configuration uses VMware vSphere Standard Switches (VSS).

Network function vmkernel vmnic (physical interface)

Management

vmk0

vmnic2 (Port A), vmnic3 (Port B)

iSCSI-A

vmk2

vmnic1 (Port E)

iSCSI-B

vmk3

vmnic5 (Port D)

vMotion

vmk1

vmnic4 (Port C), vmnic0 (Port F)

The following is a two-interface configuration. This configuration is only supported when used with VMware vSphere Distributed Switches (VDS), and requires VMware vSphere Enterprise Plus licensing.

Network function vmkernel vmnic (physical interface)

Management

vmk0

vmnic1 (Port D), vmnic5 (Port E)

iSCSI-A

vmk1

vmnic1 (Port E)

iSCSI-B

vmk2

vmnic5 (Port D)

vMotion

vmk3

vmnic1 (Port C), vmnic5 (Port F)

H610C compute nodes

This configuration for H610C nodes is only supported when used with VMware vSphere Distributed Switches (VDS), and requires VMware vSphere Enterprise Plus licensing.

Note Ports A and B are unused on the H610C.
Network function vmkernel vmnic (physical interface)

Management

vmk0

vmnic2 (Port C), vmnic3 (Port D)

iSCSI-A

vmk1

vmnic3 (Port D)

iSCSI-B

vmk2

vmnic2 (Port C)

vMotion

vmk3

vmnic2 (Port C), vmnic3 (Port D)

H615C compute nodes

This configuration for H615C nodes is only supported when used with VMware vSphere Distributed Switches (VDS), and requires VMware vSphere Enterprise Plus licensing.

Network function vmkernel vmnic (physical interface)

Management

vmk0

vmnic0 (Port A), vmnic1 (Port B)

iSCSI-A

vmk1

vmnic0 (Port B)

iSCSI-B

vmk2

vmnic1 (Port A)

vMotion

vmk3

vmnic0 (Port A), vmnic1 (Port B)