NVDS still appears due to the existence of a VM template after migration from NSX-T NVDS to CVDS.

Products

• VMware NSX
• VMware vCenter Server

Issue/Introduction

• There are dummy/orphaned opaque networks in vCenter with type "nsx.logicalswitch" after migration from NSX-T NVDS to CVDS.
• Orphan NVDS networks without attached hosts exist in vCenter inventory.
• In vSphere there are virtual machine templates created before migrating from NVDS to CVDS which have the NVDS networks attached:
  
  • Click on the portgroup in question, then select VMs and click on VM Templates to see the list of associated VM templates:
    
    

Cause

NVDS portgroups remain visible in vCenter due to existing VM templates, created prior to the NVDS to vDS migration, which still have these portgroups configured for their network adapters.

Resolution

This is a condition that may occur in a VMware NSX environment.

Workaround:

Convert the VM Template to VM, change vNIC network to new portgroup and finally convert the VM to VM Template:

• Right click on the VM Template in question and click on "Convert Template To Virtual Machine". Follow the wizard to complete the conversion.
• Right click on the VM and click on edit settings -> change the network in question to the new portgroup and click ok.
• Right click on the VM in question and click on "Convert to VM Template" to convert the VM back to VM Template.

 

Additional Information

Dummy opaque networks on VC with type "nsx.logicalswitch" after migration from NSX-T NVDS to CVDS due to snapshots.