vRealize Network Insight 5.1/5.2/5.3 and 6.x limitations with vSphere 7.0, Project Pacific and NSX-T 3.0 with VDS 7.0
search cancel

vRealize Network Insight 5.1/5.2/5.3 and 6.x limitations with vSphere 7.0, Project Pacific and NSX-T 3.0 with VDS 7.0

book

Article ID: 324460

calendar_today

Updated On:

Products

VMware Aria Operations for Networks

Issue/Introduction

With the release of vSphere 7.0 and NSX-T 3.0, some vRNI features in the versions 5.1/5.2/5.3 and 6.x will stop from working due to Project Pacific and VDS 7.0.

Note: vSphere 7.0 without Project Pacific and NSX-T with N-VDS would continue to work without any known issue with vRNI 5.1/5.2.

Combinations where features in vRNI will be impacted:

vRNI 5.1/5.2/5.3 and 6.x + vCenter 7.0 + Project Pacific based Kubernetes clusters

vRNI 5.1/5.2/5.3 + NSX-T 3.0 with VDS 7.0
  • Harmless one-time error in vCenter when adding NSX-T 3.0 data source and enabling flows
  • VM underlay topology

  


Environment

VMware vRealize Network Insight 4.x
VMware vRealize Network Insight 5.x
VMware vRealize Network Insight 6.x

Resolution

  • Issue with VM underlay topology will be fixed in the upcoming version (July 2020 release)
  • Issue with Harmless one time error in vCenter will be fixed in future version (Sept 2020 release)
  • Project Pacific is a roadmap item for future vRNI releases
  • POD VM (vSphere Tanzu) are not fetched from vCenter 7.x onwards. This is on the road map for future vRNI releases