Virtual Machine loses network connectivity after vMotion due to port mirroring property failure

Products

• VMware vCenter Server

Issue/Introduction

A virtual machine loses network connectivity following a vMotion.

The vmkernel.log on the destination host records the following error messages:(example)

YYYY-MM-DDTHH:MM:SS Wa(180) vmkwarning: cpu60:15512743)WARNING: NetDVS: 3039: Failed to write critical property com.vmware.vswitch.port.mirrorSessions on port 9915, return :Not found.

Here, dvPort 9915 is the DVS Port ID, which also corresponds to the target virtual machine in the port mirroring session.

Environment

vCenter Server 8.x

VMware ESXi 8.x

Cause

The virtual machine is configured in a Distributed Virtual Switch (DVS) port mirroring session. During vMotion, the destination ESXi host fails to write the com.vmware.vswitch.port.mirrorSessions property to the distributed switch port. This failure causes the virtual machine's network port to remain disabled, resulting in a loss of network connectivity.

Resolution

Fix the problematic configuration (uplink) in the port mirror session. 

Navigation path: vSphere Client -> Networking -> vDS -> Settings -> Port Mirroring, refer to port <ID>(example :port 9915) to find the session, check uplink of  configuration

The issue disappears once an existing VMNIC is selected within the session.

Additional Information

This is an involved [Remote Mirroring Source] type port mirroring

Navigation path: vSphere Client -> Networking -> vDS -> Settings -> Port Mirroring -> Add -> Remote Mirroring Source, uplink setting is in Select destinations