ESXi host fails with PSOD on log bundle collection or command execution

Products

• VMware NSX

Issue/Introduction

Symptoms:

• NSX-T Data Center 2.4.1 environment
• Gateway or Router is configured
• Initiated ESXi host log bundle collection or executing net-vdr --fl command on CLI.
• Traffic generation tools are in-use or a large number of connections is going through logical routers.
• PSOD backtrace may be similar to this example.

0x451ad831b8c8:[0x41801cd0ba15]PanicvPanicInt@vmkernel#nover+0x439 stack: 0x0
0x451ad831b968:[0x41801cd0bc48]Panic_NoSave@vmkernel#nover+0x4d stack: 0x451ad831b9c8
0x451ad831b9c8:[0x41801cd54363]DLM_free@vmkernel#nover+0x6a8 stack: 0x4312cc193e30
0x451ad831b9e8:[0x41801cd51500]Heap_Free@vmkernel#nover+0x115 stack: 0x451ad831baa0
0x451ad831ba38:[0x41801dd2e1bd][email protected]#1.0.6.7+0x82 stack: 0x0
0x451ad831bb68:[0x41801cd2208b]VMKAPICharDevDevfsWrapIoctl@vmkernel#nover+0x74 stack: 0x418000000049

Note: PSOD refers to a Purple Screen of Death which is often associated with host crashes.

Environment

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

Cause

PSOD is caused by internal command execution failure.

Resolution

Upgrade to NSX-T 2.5.0.8