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

Products

• VMware NSX

Issue/Introduction

Active uplink ports per distributed port group for vCenter managed distributed port group are correctly reflecting as compared to the distributed port group managed by NSX.

1. vCenter managed DPG :-

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

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

2. NSX-Manager managed DPG :-

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

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

Environment

VMware NSX-T Data Center

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 a NSX DVPG, we need to retrieve the teaming policy from the NSX side.