Moving of NSX PortGroups to Subnet/Segment folders fails when enabling "Organize NSX Portgroups in vCenter folders" tab on the project
search cancel

Moving of NSX PortGroups to Subnet/Segment folders fails when enabling "Organize NSX Portgroups in vCenter folders" tab on the project

book

Article ID: 405696

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • NSX 4.2.1 infrastructure running VPCs.
  • "Organize NSX Portgroups in vCenter folders" tab on the project is enabled.

  • Below task will be seen on the vCenter

Task Name: Move entities
Target: <Network Folder>
The operation is not supported on the object. The distributed port group ####### cannot be moved because its associated VDS, #############, has not been specified to move it.

  • Below logs will be seen on NSX manager: /var/log/proton/nsxapi.log

2025-07-04T09:50:31.398Z WARN LogicalSwitchStateOperationScheduler1 LogicalSwitchFolderRealizationUtils 76814 SWITCHING [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="manager"] Failed to perform moveInto for Folder group-n#### and portGroups [dvportgroup-####] on VC #######-####-####-####-############
com.vmware.nsx.management.switching.common.exceptions.SwitchingException: null
        at com.vmware.nsx.management.switching.vc.VcFolderOperation.moveInto(VcFolderOperation.java:272) ~[?:?]
        at com.vmware.nsx.management.switching.sync.host.LogicalSwitchFolderRealizationUtils.movePortGroups(LogicalSwitchFolderRealizationUtils.java:797) ~[?:?]
        at com.vmware.nsx.management.switching.sync.host.LogicalSwitchFolderRealizationUtils.doPortGroupMovement(LogicalSwitchFolderRealizationUtils.java:709) ~[?:?]
        at com.vmware.nsx.management.switching.sync.host.LogicalSwitchHostSyncer.handleVcNsxPortGroupRequest_aroundBody0(LogicalSwitchHostSyncer.java:388) ~[?:?]
        at com.vmware.nsx.management.switching.sync.host.LogicalSwitchHostSyncer$AjcClosure1.run(LogicalSwitchHostSyncer.java:1) ~[?:?]
        at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149) ~[?:?]
        at com.vmware.nsx.management.metric.aspect.TimedAspect.timedMethodAdvice(TimedAspect.java:87) ~[?:?]
        at com.vmware.nsx.management.switching.sync.host.LogicalSwitchHostSyncer.handleVcNsxPortGroupRequest(LogicalSwitchHostSyncer.java:186) ~[?:?]
        at com.vmware.nsx.management.switching.sync.host.LogicalSwitchHostSyncer.run(LogicalSwitchHostSyncer.java:407) ~[?:?]
        at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) ~[?:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) ~[?:?]
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source) ~[?:?]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
        at java.lang.Thread.run(Unknown Source) ~[?:?]

  • This issue is purely cosmetic and will not impact the dataplane traffic.

Environment

VMware NSX

Cause

This is a known issue if the VDS lies within another NetworkFolder within the Datacenter, then movement of NSX PortGroups to Subnet/Segment folders fails.

Resolution

This is fixed in VMware NSX 4.2.2.1 and above

For workaround, please contact Broadcom Technical Support