Running the commands "esxcfg-vswitch -l" or "net-dvs -l" Throws an error " Listing Failed for DVSwitch: DvsPortset-0,Error : Unable toget the dvs name: Status(bad0007) = Bad parameter"

Products

• VMware vSphere ESXi

Issue/Introduction

• Host becomes unresponsive /  won't be reachable over the Network post the upgrade/patch-update.
• Unable to attach VMNICs/VMKs to DVS.
• Listing the DVS configurations using the commands "esxcfg-vswitch -l" or "net-dvs -l"
  would throws the error -
   "Listing Failed for DVSwitch: DvsPortset-0,Error : Unable toget the dvs name: Status(bad0007) = Bad parameter"
• You would see  logs similar to  below logged in vmkernel.log of the host 
  
  2025-03-13T17:22:30.350Z cpu81:2104465 opID=f5004b32)WARNING: NetDVS: 1850: Attempt to associate with DVS xx xx xx xx xx xx xx xx -xx xx xx xx xx xx xx xx with no proxy vswitch, port xxx (type 1)
2025-03-13T17:22:30.350Z cpu81:2104465 opID=f5004b32)WARNING: NetDVS: 903: Connect to DVS port xxx failed Not found
2025-03-13T17:22:30.350Z cpu81:2104465 opID=f5004b32)Net: 3374: DVS xx xx xx xx xx xx xx xx -xx xx xx xx xx xx xx xx port 0 not associated: Not found.
2025-03-13T17:22:30.350Z cpu81:2104465 opID=f5004b32)WARNING: Tcpip_Vmk: 1721: Could not open a port to xxx: Not found
2025-03-13T17:22:30.350Z cpu81:2104465 opID=f5004b32)WARNING: Tcpip_Vmk: 1349: Unable to attach vmk0 to xxx [error = 0xbad0003] 

Environment

• ESXi 7.x / ESXi 8.x.
• NSX 4.2.1

Cause

This is a known issue with DVS installed with NSX 4.2.1.

Resolution

• This issue is resolved in NSX 4.2.2.
• For a workaround ,open a support request with Broadcom. Ref Creating and managing Broadcom support cases