An uplink profile defines policies for the links from hypervisor hosts to NSX-T Data Center logical switches or 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 Data Center 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.

Note:

NSX Edge VMs do allow for multiple uplinks if you create a separate N-VDS for each uplink, using a different VLAN for each. Each uplink needs a separate VLAN transport zone. This is to support a single NSX Edge node that connects to multiple TOR switches.

Prerequisites

  • Familiarize yourself with NSX Edge networking. See NSX Edge Networking Setup.

  • 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 Data Center uplink, but vmnic0 cannot. To do link teaming, you must have two unused physical links available, such as vmnic1 and vmnic2.

    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.

Procedure

  1. From a browser, log in with admin privileges to an NSX Manager at https://<nsx-manager-ip-address>.
  2. Select Fabric > Profiles > Uplink Profiles and click Add.
  3. Complete the uplink profile details.

    Option

    Description

    Name

    Enter an uplink profile name.

    Description

    Add an optional uplink profile description.

    LAGs

    (Optional) Link aggregation groups (LAGs) using Link Aggregation Control Protocol (LACP) for the transport network.

    Note:

    For LACP, multiple LAG is not supported on KVM hosts.

    Add a comma-separated list of active uplink names.

    Add a comma-separated list of standby uplink names. The active and standby uplink names you create can be any text to represent physical links. These uplink names are referenced later when you create transport nodes. The transport node UI/API allows you to specify which physical link corresponds to each named uplink.

    Teamings

    In the Teaming section, click Add and enter the details. 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.

    (Only ESXi hosts) You can define the following policies for a transport zone:

    • A Named teaming policy for every logical switch configured on the switch.

    • A Default teaming policy for the entire switch.

    Named teaming policy: A named teaming policy means that for every logical switch you can define a specific teaming policy mode and uplinks. This policy type gives you the flexibility to select uplinks depending on the bandwidth requirement.

    • If you define a named teaming policy, N-VDS uses that named teaming policy if it is specified by the attached transport zone and logical switch in the host.

    • If you do not define any named teaming policies, N-VDS uses the default teaming policy.

  4. Enter a Transport VLAN value.
  5. Enter the MTU value.

    The default value is 1600.

Results

In addition to the UI, you can also view the uplink profiles with the GET /api/v1/host-switch-profiles API call:

{
  "result_count": 2,
  "results": [
    {
      "resource_type": "UplinkHostSwitchProfile",
      "id": "16146a24-122b-4274-b5dd-98b635e4d52d",
      "display_name": "comp-uplink",
      "transport_vlan": 250,
      "teaming": {
        "active_list": [
          {
            "uplink_type": "PNIC",
            "uplink_name": "uplink-1"
          }
        ],
       	"standby_list" : [ { 
            "uplink_name" : "uplink-2", 
            "uplink_type" : "PNIC" 
         } ],
        "policy": "FAILOVER_ORDER"
      },
      "mtu": 1600,
      "_last_modified_time": 1457984399526,
      "_create_time": 1457984399526,
      "_last_modified_user": "admin",
      "_system_owned": false,
      "_create_user": "admin",
      "_revision": 0
    },
    {
      "resource_type": "UplinkHostSwitchProfile",
      "id": "c9e35cec-e9d9-4c51-b52e-17a5c1bd9a38",
      "display_name": "vlan-uplink",
      "transport_vlan": 100,
      "teaming": {
        "active_list": [
          {
            "uplink_type": "PNIC",
            "uplink_name": "uplink-1"
          }
        ],
        "standby_list": [],
        "policy": "FAILOVER_ORDER"
      },
      "named_teamings": [ 
         { 
          "active_list": [ 
         { 
          "uplink_type": "PNIC", 
          "uplink_name": "uplink-2" 
          } 
					    ], 
	       "standby_list": [ 
         { 
		        "uplink_type": "PNIC", 
          "uplink_name": "uplink-1" 
          } 
           ], 
        "policy": "FAILOVER_ORDER", 
         "name": "named teaming policy" 
             } 
            ]
						"mtu": 1600,
      "_last_modified_time": 1457984399574,
      "_create_time": 1457984399574,
      "_last_modified_user": "admin",
      "_system_owned": false,
      "_create_user": "admin",
      "_revision": 0
    }
  ]
}

What to do next

Create a transport zone. See Create Transport Zones.