Deployment Guide

32 ScaleIO/VxFlex OS IP Fabric Best Practice and Deployment Guide with OS10EE | version 1.0
5. On the Teaming and failover page, click lag1 and move it up to the Active uplinks section by
clicking the up arrow. Move Uplinks 1-4 down to the Unused uplinks section by clicking the down
arrow. Leave other settings at their defaults. The Teaming and failover page should look similar to
Figure 22 when complete.
Teaming and failover settings for LAGs
6. Click Next followed by Finish to apply settings.
Repeat steps 1-6 above for the ScaleIO-data01 port group, except select lag2 to move to the Active
Uplinks.
3.3.9 Add VMkernel adapters for MDM, SDS-SDC, and vMotion
To allow virtual machines to be moved between compute nodes a vMotion-enabled VMkernel is created. This
VMkernel is configured to use the vMotion port group on the default TCP/IP stack. A VMkernel interface is
also created to handle VxFlex OS storage traffic. The VMkernel is associated with the ScaleIO-data01 and
uses the default TCP/IP stack. No VMware specific services are enabled for storage traffic.
The procedure in this section, adds ScaleIO-data01, management, and vMotion VMkernel adapters (referred
to as VMkernel ports) to each ESXi host to allow for ScaleIO, management, and vMotion traffic.
Either assign IP addresses statically to VMkernel adapters upon creation or use DHCP. This guide uses
Static IP addresses.