The observations of Livetrace and Traceflow may be dropped by internal message channel issue

Products

• VMware NSX

Issue/Introduction

Symptoms:
In common case, missing observations will cause the sequence number to 999.

You could find this issue in nsx-syslog.log within  ESXi logs.

A typical log is : 
2021-11-25T13:35:43Z nsx-opsagent[2101136]: NSX 2101136 - [nsx@6876 comp="nsx-esx" subcomp="opsagent" s2comp="framework" tid="2101197" level="ERROR" errorCode="OPS00205"] DpLink /var/run/vmware/nsx-agent/nsxa_link: recv error, invalid DpMsg header, fragment: 0, type: 0, size: 17210

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware NSX-T Data Center
VMware NSX-T
VMware NSX-T Data Center 3.x

Cause

Some bytes of Livetrace or Traceflow observations are dropped in the transmission of ESXi inner component. This may caused by platform or the third party library. To avoid such issue, we will restart the message channel when found invalid message.

Resolution

The issue has been fixed starting on 3.1.5 onwards.

Workaround:
The issue could be recovered through re-create a new session(livetrace) and retrace(traceflow).

Product Versions: 
NSX 3.1.0 to NSX 3.1.4