vCenter CLI does not show uplink details of NSX managed distributed port group.

Products

• VMware NSX

Issue/Introduction

• While the active uplink ports are correctly reflected in the CLI output  for vCenter-managed Distributed Port Groups, the uplink details are not reported for Distributed Port Groups managed by NSX.
• vCenter managed distributed switch port group details (PowerCLI):

PS C:\> Get-VDPortgroup "DVS_name" | Get-VDUplinkTeamingPolicy

VDPortgroup LoadBalancingPolicy FailoverDetectionPolicy NotifySwitches EnableFailback ActiveUplinkPort
----------- ------------------- ----------------------- -------------- -------------- ----------------
DVS_name LoadBalanceSrcId LinkStatus True True {uplink1, upli...

• NSX-Manager managed port group details:

PS C:\> Get-VDPortgroup "DVS_name" | Get-VDUplinkTeamingPolicy

VDPortgroup LoadBalancingPolicy FailoverDetectionPolicy NotifySwitches EnableFailback ActiveUplinkPort
----------- ------------------- ----------------------- -------------- -------------- ----------------
DVS_name LoadBalanceSrcId LinkStatus True True {}

Environment

VMware NSX

Cause

This is an expected behavior. The teaming policies in vCenter and NSX are in different styles. NSX DVPG represents an NSX segment/logical switch and the teaming policy cannot be mapped between them.

In NSX, teaming policy is defined in the uplink profile and an uplink profile is applied on a *host*. In other words, the segment/logical switch on a single host shares the same teaming policy.

In the vCenter, teaming policy is applied to DVPG and DVPG spans across hosts. In other words, A DVPG has an identical teaming policy on all hosts.

Resolution

For NSX managed port groups, the teaming policy details needs to be retrieved directly from NSX.