Understanding NSX Uplink Profile Default Teaming Policy ?

[TryllZ]

Hi,

Can someone clarify how the Teaming policy works.

In the below image the Default Teaming is Load Balance Source, but there are 2 more entries with Failover.

In this case which will take precedence ?

I have checked and the Default Teaming cannot be skipped, it has to be added.

[Peter Neumann]

Default teaming is the one that will be used by your TEP interface(s) and all others that you list can be used in named uplink policy(policies) for anything else, like uplink VLANs for your T0 or any VLAN backed segment you wish to push through a specific interface.

[Alexander Schneider]

The setup above will create two Overlay TEP VMKs on your hosts or use two NICs of your Edges for Overlay traffic (Multi TEP) and loadbalance Overlay traffic.

As Peter said, the other entries then are for VLAN based stuff. If you don't define them, VLAN Segments for example will use the Default settings.

[TryllZ]

Thanks @Peter Neumann clarifying, and @Alexander Schneider for clarifying what I was about to ask..

[Steffen Richter]

Hi Touqeer,

Any uplink profile needs to have a default teaming policy.

This teaming policy is used for ALL segments by default on those Transport Nodes where this Uplink Profile is applied onto.

This default teaming policy is mandatory for ANY overlay segment on the corresponding Transport nodes and can NOT be changed for overlay segments. 

If you create additional named teaming policies in an uplink profile like you showed, you can enable those named teaming ppolicies in your Transport zone and then, only for VLAN segments, you can go to any VLAN segment of this connected Tranport Zone and change its unlink teaming policy away from the default teaming policy to one of your named teaming policies.

In designs we usually use this configuration for routing uplink segments for edges and similar, but the use cases are not limited to this.

Hope that helps!

BR

Steffen

[TryllZ]

Thanks @Steffan

For adding more into this, helps me understand it better..

[Lakshmikantha B D]

Hello Team,

The same vmnics (ex: vmnic0 and vmnic1) can be used for both overlay backed segments traffic and VLAN based traffic like vMotion, Management and vSAN ?

[Lakshmikantha B D]

Hi, 

Can we have same uplinks vmnic0 and vmnic1 for both overlay based traffic and VLAN based (Management , vMOtion, vSAN) traffic ?

[Paul Jamerson]

The Default Teaming policy in NSX takes effect unless a specific teaming policy is configured on a segment or segment profile. If multiple entries exist with Failover, the precedence is determined by the most specific policy applied. If no specific policy is defined, the Default Teaming (Load Balance Source in your case) is used.

[Steffen Richter]

Instructor "speaking" ;)

Default Teaming Policy - mandatory, controls how any Overlay Segment on the attached Transport Node functions; also, by default, controls how VLAN segments on the attached Transport Nodes do function

Named Teaming Policies - can (!) control, how VLAN segments do work on an attached Transport Node. For this to work, you need to create your Named Teaming Policies in your Uplink Profile (while properly naming them), attach those NTPs within a/your VLAN Transport Zones and then go to your VLAN segment within Networking, edit it and there will you see the additional attached NTPs, which will now enable you to configure a VLAN (!) segment to be for instance A/S, or S/A, or active without a standby uplink etc.

Overlay segments can NOT be controlled like this, They can only consume the Default Teaming Policy.

BR
Steffen