NSX-T 2.2 Uplink Profile

An uplink profile defines policies for the links

1. from Hypervisor hosts to NSX-T logical switches or 
2. from NSX Edge nodes to top-of-rack switches.

The settings defined by uplink profiles might include teaming policies, active/standby links, the transport VLAN ID, and the MTU setting.
Uplink profiles allow you to consistently configure identical capabilities for network adapters across multiple hosts or nodes. Uplink profiles are containers for the properties or capabilities that you want your network adapters to have. Instead of configuring individual properties or capabilities for each network adapter, you can specify the capabilities in uplink profiles, which you can then apply when you create NSX-T transport nodes.
Standby uplinks are not supported with VM/appliance-based NSX Edge. When you install NSX Edge as a virtual appliance, use the default uplink profile. For each uplink profile created for a VM-based NSX Edge, the profile must specify only one active uplink and no standby uplink.

Prerequisites

1. Each uplink in the uplink profile must correspond to an up and available physical link on your hypervisor host or on the NSX Edge node.For example, your hypervisor host has two physical links that are up: vmnic0 and vmnic1. Suppose vmnic0 is used for management and storage networks, while vmnic1 is unused. This might mean that vmnic1 can be used as an NSX-T uplink, but vmnic0 cannot. To do link teaming, you must have two unused physical links available, such as vmnic1 and vmnic2.
2. For an NSX Edge, tunnel endpoint and VLAN uplinks can use the same physical link. For example, vmnic0/eth0/em0 might be used for your management network and vmnic1/eth1/em1 might be used for your fp-ethX links.

When you install NSX Edge as a virtual appliance or VM, internal interfaces are created, called fp-ethX, where X is 0, 1, 2, and 3. These interfaces are allocated for uplinks to a top-of-rack (ToR) switches and for NSX-T overlay tunneling.

When you create the NSX Edge transport node, you can select fp-ethX interfaces to associate with the uplinks and the overlay tunnel. You can decide how to use the fp-ethX interfaces. 

How to Create Custom Uplink Profile
1. Login to NSX Manager UI

 
2.  Fabric > Profiles > Uplink Profils > Click on Add Button > Configure the required details > Add
LAG = For LACP, multiple LAG is not supported on KVM hosts.
Teaming = The teaming policy defines how the N-VDS uses its uplink for redundancy and traffic load balancing. There are two teaming policy modes to configure teaming policy:

Failover Order: An active uplink is specified along with an optional list of standby uplinks. If the active uplink fails, the next uplink in the standby list replaces the active uplink. No actual load balancing is performed with this option.

Load Balanced Source: A list of active uplinks is specified, and each interface on the transport node is pinned to one active uplink. This configuration allows use of several active uplinks at the same time.

Note:On KVM hosts, only failover order teaming policy is supported. Load balance source teaming policy is not supported.