PSOD Encountered for NSX prepared ESXi host where IPv6 is used on the GW configuration for Segments.

Products

• VMware NSX

Issue/Introduction

• NSX is installed with IPv6 configured on the Gateway for downlink Segments.
• PSOD occurs on ESXi host with back trace similar to:

  2025-03-07T08:31:33.820Z In(14) LogEFI: cpu100:54275078)ESC[45mESC[33;1mVMware ESXi 8.0.2 [Releasebuild-23305546 x86_64]ESC[0m
  2025-03-07T09:35:43.682Z In(14) LogEFI[2101393]: #PF Exception 14 in world 54275078:vmx-vcpu-0:c IP 0x4200261851dd addr 0x10
  2025-03-07T09:35:43.682Z In(14) LogEFI[2101393]: PTEs:0x140930e0027;0x19ecc7d6027;0x0;
  2025-03-07T09:35:43.682Z In(14) LogEFI[2101393]:
  2025-03-07T09:35:43.682Z In(14) LogEFI[2101393]: Module(s) involved in panic: [nsxt-vdrb-23382415 Version 1.0.0-0 RELEASEbuild-23382415] [nsxt-vdl2-23382415 Version 2.0.0-0 RELEASEbuild-23382415]
  2025-03-07T08:31:33.822Z In(14) LogEFI: cpu100:54275078)cr0=0x80010031 cr2=0x10 cr3=0x13aa0a82000 cr4=0x146768
  2025-03-07T08:31:33.822Z In(14) LogEFI: cpu100:54275078)FMS=06/6a/6 uCode=0xd0003e7
  2025-03-07T08:31:33.822Z In(14) LogEFI: cpu100:54275078)frame=0x453b7dd1b2a0 ip=0x4200261851dd err=0x0 rflags=0x10202
  2025-03-07T08:31:33.822Z In(14) LogEFI: cpu100:54275078)rax=0x0 rbx=0x432775804440 rcx=0x0
  2025-03-07T08:31:33.823Z In(14) LogEFI: cpu100:54275078)rdx=0x0 rbp=0x432775804638 rsi=0x43277581d658
  2025-03-07T08:31:33.823Z In(14) LogEFI: cpu100:54275078)rdi=0x43277581d658 r8=0x3e6a858c48cdd235 r9=0x100000000
  2025-03-07T08:31:33.823Z In(14) LogEFI: cpu100:54275078)r10=0x0 r11=0x810000 r12=0x2
  2025-03-07T08:31:33.823Z In(14) LogEFI: cpu100:54275078)r13=0x43277581d640 r14=0x43277581c840 r15=0x4326a2c90370
  2025-03-07T09:35:43.682Z In(14) LogEFI[2101393]: *PCPU100:54275078/vmx-vcpu-0
  2025-03-07T09:35:43.682Z In(14) LogEFI[2101393]: PCPU  0: SSSVUSVVVSVSSVVVSVSVUVVVVVVSSSVVVVSVVVSVVSVUVVVVVVVVSVSVVVVVSVVV
  2025-03-07T09:35:43.682Z In(14) LogEFI[2101393]: PCPU 64: UVUVVVUSVVSSSSVSVSSSVSSSVSVISSSSSSSSUVVVVSSVVVVSSSSUVVVSVSUVVSSV
  2025-03-07T08:31:33.825Z In(14) LogEFI: cpu100:54275078)Code start: 0x420024600000 VMK uptime: 126:00:45:41.423
  2025-03-07T08:31:33.825Z In(14) LogEFI: cpu100:54275078)0x453b7dd1b360:[0x4200261851dd]VdrGetLifByVniAndTypeLocked@(nsxt-vdrb-23382415)#<None>+0x225 stack: 0x4200261c8006
  2025-03-07T08:31:33.826Z In(14) LogEFI: cpu100:54275078)0x453b7dd1b3a0:[0x420026187370]VdrVMActivationCallback@(nsxt-vdrb-23382415)#<None>+0x75 stack: 0x453b7dd1b460
  2025-03-07T08:31:33.826Z In(14) LogEFI: cpu100:54275078)0x453b7dd1b3d0:[0x42002602ca5e][email protected]#1.1.8.0.23382415+0x8f stack: 0x0
  2025-03-07T08:31:33.833Z In(14) LogEFI: cpu100:54275078)base fs=0x0 gs=0x420059000000 Kgs=0x0

 

Environment

VMware NSX
VMware NSX-T Data Center

 

Cause

The issue occurs due to protected Neighbor Discovery entries for the Downlink not being cleared.

Resolution

This issue is resolved in VMware NSX 4.2.1, available at Broadcom downloads.

If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

 

Workaround

Remove the IPv6 configuration from the Segment Gateway configuration.