Setup Guide

24 Dell EMC PowerEdge MX SmartFabric Configuration and Troubleshooting Guide
3.9 NIC teaming guidelines
While NIC teaming is not required, it is generally suggested for redundancy unless a specific implementation
recommends against it.
There are two main kinds of NIC teaming:
• Switch dependent: Also referred to as LACP, 802.3ad, or Dynamic Link Aggregation, this teaming
method uses the LACP protocol to understand the teaming topology. This teaming method provides
Active-Active teaming and requires the switch to support LACP teaming.
• Switch independent: This method uses the operating system and NIC device drivers on the server
to team the NICs. Each NIC vendor may provide slightly different implementations with different pros
and cons.
NIC Partitioning (NPAR) can impact how NIC teaming operates. Based on restrictions implemented by the
NIC vendors related to NIC partitioning, certain configurations will preclude certain types of teaming.
The following restrictions are in place for both Full Switch and SmartFabric modes:
• If NPAR is NOT in use, both Switch Dependent (LACP) and Switch Independent teaming methods
are supported
• If NPAR IS in use, only Switch Independent teaming methods are supported. Switch Dependent
teaming is NOT supported
If Switch Dependent (LACP) teaming is used, the following restrictions are in place:
• The iDRAC shared LAN on motherboard (LOM) feature can only be used if the “Failover” option on
the iDRAC is enabled
• If the host OS is Windows, the LACP timer MUST be set to “slow” (also referred to as “normal”)
a. Microsoft Windows 2012 R2: Instructions
b. Microsoft Windows 2016: Instructions
Refer to the network adapter or operating system documentation for detailed NIC teaming instructions.
NOTE: If using VMware ESXi and LACP, it is recommended to use VMware ESXi 6.7.0 Update 2.
NOTE: LACP Fast timer is not currently supported.
3.10 Identity pools
The PowerEdge MX7000 uses identity pools to manage the set of values that can be used as virtual identities
for discovered devices. The chassis controls the assignment of virtual identity values, selecting values for
individual deployments from pre-defined ranges of possible values. This allows the customer to control the set
of values which can be used for identities. The customer doesn’t have to enter all needed identity values with
every deployment request, or remember which values have or have not been used. Identity pools make
configuration deployment and migration much easier to manage.
Identity pools are used in conjunction with template deployment and profile operations. They provide sets of
values that can be used for virtual identity attributes for deployment. After a template is created, an identity
pool may be associated with it. Doing this directs the identity pool to get identity values whenever the